-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1
iQIcBAEBCgAGBQJU2Un0AAoJEGn3kBcaIQmEETcQAMizf9YXhTD5CvQD4O/Ac+St
ZFbiNVbBE/zMjoOpL/EU0Lcfa/ydEUymZ2ovnWIc+olVz+2EIfLNAJ5eqAiZ6amy
0so3AlNyvrnIUOzMcp+G+igqfPIAJ6RC26JYsLEPATiQDpjuLMIkPGhPSxceaV14
dpyITs7KVlKwh3dYiNuXwDJveNP4QeN5VOLq4on5VoMaEBSZniTgEFyhwXhR5m2U
c2AUDaqHEmA6VJzMp8qJb5noJ8mAKDNCih4iE8+9TpQnbBOBlXMKV+RKvq2XwzT2
BfWe4bqLdrEOuwm7ByEsLMXZpapRkmqyh+CYXgIMzmSwhTuyZWPsB1CaulbFUJ1L
WWVPn4eJ9qxW7AoAa5qeNlVH+2dtVdw5m2OEtJrkDooRc0goIhsfIR6GDo6m+kqN
sxz5kmjNkELEEow+IyBLTA9Lzd4w0nM73ApePmPrJBzJQGp3ADoBqT1xUmsyxeHB
7Kkn65iXq23tN195Q+y35egsB4XPcGp5POrvFa2mXqpf4G0g+OgpEm0DgWJF4vbm
VafxqsMckYkhUmwCyYIVuiLDQbT65Ai1uQI5VPR2lhc0ziCei/QDLHT9iQRO8IyM
wH9QF16xYzDQdgrtHrL6SeY4WN4c/Zh4PyIxrxg7nAYqLVWo81rCutiUm5N5E2MX
x9Whpj4lVKY+EH+LI5Gv
=shVa
-----END PGP SIGNATURE-----
On 10/02/15 00:40, Martin Pitt wrote:
> Hey Matthias,
>
> Matthias Klose [2015-02-06 14:31 +0100]:
>> A test rebuild of Vivid Vervet was started this week for all
>> architectures, and is finished for the main component.
>>
>> Results can be found at
>>
>> http://people.ubuntuwire.org/~wgrant/rebuild-ftbfs-test/test-rebuild-20150202-vivid.html
>
> Thanks!
>
> This looks a bit confusing, though. E. g. the pygobject-2 "→ Log" link
> just points back to the same overview page, and the "i386 (F)" link
> leads to https://launchpad.net/ubuntu/+archive/test-rebuild-20150202/+build/6833261
> which has no build log at all. So while having an indication that a
> build failed is already useful, having the actual logs would be very
> helpful (and we did have them in the past).
>
> Were they removed because of the other test build that's currently
> going on?
A failed build without a log means that something went catastrophically
wrong, so there was no log that could be provided. Usually it means the
build took the builder down, or there was a network fault. In this case
there was a librarian glitch preventing the builder from downloading the
dsc.
I've retried the build.
