[arch-dev-public] [core] abs build failures
For those that are interested, I occasionally do a complete rebuild of [core] as a bit of a check that updates have not broken anything. Here is a sumary of build failures for packages in [core]. Note that if a package from [core] is currently in [testing], that PKGBUILD was used instead. Source unavailable: FAIL: iproute2 FAIL: libcap FAIL: linux-api-headers FAIL: linux-firmware FAIL: man-pages FAIL: mdadm FAIL: module-init-tools FAIL: pcmciautils FAIL: ppl FAIL: run-parts FAIL: tzdata FAIL: usbutils Failure during package(): FAIL: e2fsprogs Failure during check(): FAIL: libarchive (occurs on alderaan but not locally for me - btrfs issue?) Allan
On Thu, Nov 10, 2011 at 8:52 AM, Allan McRae <allan@archlinux.org> wrote:
For those that are interested, I occasionally do a complete rebuild of [core] as a bit of a check that updates have not broken anything.
Here is a sumary of build failures for packages in [core]. Note that if a package from [core] is currently in [testing], that PKGBUILD was used instead.
Failure during package(): FAIL: e2fsprogs
Still works for me locally and in a chroot just a few days ago. Do you have a copy of the error? Ronald
On 10/11/11 23:31, Ronald van Haren wrote:
On Thu, Nov 10, 2011 at 8:52 AM, Allan McRae<allan@archlinux.org> wrote:
For those that are interested, I occasionally do a complete rebuild of [core] as a bit of a check that updates have not broken anything.
Here is a sumary of build failures for packages in [core]. Note that if a package from [core] is currently in [testing], that PKGBUILD was used instead.
Failure during package(): FAIL: e2fsprogs
Still works for me locally and in a chroot just a few days ago. Do you have a copy of the error?
No... and I can not replicate any more either. So let ignore that one...
Am 10.11.2011 08:52, schrieb Allan McRae:
Source unavailable: FAIL: linux-firmware
My bad, uploading the source now.
On Thu, Nov 10, 2011 at 1:52 AM, Allan McRae <allan@archlinux.org> wrote:
For those that are interested, I occasionally do a complete rebuild of [core] as a bit of a check that updates have not broken anything.
Failure during check(): FAIL: libarchive (occurs on alderaan but not locally for me - btrfs issue?)
Seeing the same; building on alderaan NOT in a chroot also completes successfully. Ionuț- is there an easy way to get into the chroot on alderaan and check things after the failure? Running the test program manually would at least give me logs and things needed to debug this. -Dan
On 11/10/2011 05:11 PM, Dan McGee wrote:
On Thu, Nov 10, 2011 at 1:52 AM, Allan McRae<allan@archlinux.org> wrote:
For those that are interested, I occasionally do a complete rebuild of [core] as a bit of a check that updates have not broken anything.
Failure during check(): FAIL: libarchive (occurs on alderaan but not locally for me - btrfs issue?)
Seeing the same; building on alderaan NOT in a chroot also completes successfully.
Ionuț- is there an easy way to get into the chroot on alderaan and check things after the failure? Running the test program manually would at least give me logs and things needed to debug this.
-Dan
i believe chroot can be used with sudo without password. -- Ionuț
On 11/11/11 01:11, Dan McGee wrote:
On Thu, Nov 10, 2011 at 1:52 AM, Allan McRae<allan@archlinux.org> wrote:
For those that are interested, I occasionally do a complete rebuild of [core] as a bit of a check that updates have not broken anything.
Failure during check(): FAIL: libarchive (occurs on alderaan but not locally for me - btrfs issue?)
Seeing the same; building on alderaan NOT in a chroot also completes successfully.
Ionuț- is there an easy way to get into the chroot on alderaan and check things after the failure? Running the test program manually would at least give me logs and things needed to debug this.
How I do it... sudo mkarchroot -r "bash" /var/tmp/archbuild/testing-x86_64/dan Allan
participants (5)
-
Allan McRae
-
Dan McGee
-
Ionut Biru
-
Ronald van Haren
-
Thomas Bächler