Please read this before reporting a bug:
https://wiki.archlinux.org/title/Bug_reporting_guidelines
Do NOT report bugs when a package is just outdated, or it is in the AUR. Use the 'flag out of date' link on the package page, or the Mailing List.
REPEAT: Do NOT report bugs for outdated packages!
https://wiki.archlinux.org/title/Bug_reporting_guidelines
Do NOT report bugs when a package is just outdated, or it is in the AUR. Use the 'flag out of date' link on the package page, or the Mailing List.
REPEAT: Do NOT report bugs for outdated packages!
FS#36654 - [devtools] Can't build bzr packages using devtools
Attached to Project:
Arch Linux
Opened by Maxime Gauduin (Alucryd) - Saturday, 24 August 2013, 11:59 GMT
Last edited by Pierre Schmitz (Pierre) - Saturday, 02 November 2013, 22:10 GMT
Opened by Maxime Gauduin (Alucryd) - Saturday, 24 August 2013, 11:59 GMT
Last edited by Pierre Schmitz (Pierre) - Saturday, 02 November 2013, 22:10 GMT
|
DetailsTrying to build a bzr package using devtools in a clean chroot will fail because bzr does not have write permissions in /srcdest.
Example when trying to build granite-bzr: ==> Retrieving sources... ==> Validating source files with sha256sums... granite ... Skipped ==> Extracting sources... -> Creating working copy of granite bzr repo... No handlers could be found for logger "bzr" bzr: ERROR: Cannot lock LockDir(file:///srcdest/granite/.bzr/branch/lock): Transport error: [Errno 30] Read-only file system: '/srcdest/granite/.bzr/branch/lock/6kef89w7x4.tmp' [Errno 30] Read-only file system: '/srcdest/granite/.bzr/branch/lock/6kef89w7x4.tmp' ==> ERROR: Failure while creating working copy of granite bzr repo Aborting... ==> ERROR: Build failed, check /var/lib/archbuild/extra-x86_64/alucryd/build What would be the best approach for this: running bzr as root or making /srcdest rw? |
This task depends upon
A good package to test is e.g. grub, which can be build using the usual makepkg, but not with makechrootpkg, after this patch, makechrootpkg works as well.