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#13024 - All recompilation problems..
Attached to Project:
Community Packages
Opened by kongokris 2 (nut543) - Wednesday, 28 January 2009, 18:33 GMT
Last edited by Allan McRae (Allan) - Friday, 30 January 2009, 03:45 GMT
Opened by kongokris 2 (nut543) - Wednesday, 28 January 2009, 18:33 GMT
Last edited by Allan McRae (Allan) - Friday, 30 January 2009, 03:45 GMT
|
DetailsHow do we avoid the frequent recompilation problems reported on the bugtracker?
Now i'm not totally up-to-date on how shared libraries work so i might be wrong but here's a suggestion: Mandate that packagers/maintainers need to compile these programs inside an environment which doesn't differ from say Community, extra and Core and one for Testing, extra and Core. Perhaps a VM or a chroot or whatever.. Important packages like a kernel etc would probably benefit from also be tested outside a VM i suppose. Or something entirely different! I sat it to high because if we could fix a lot of problems in one fellow swoop it would save a lot of time. |
This task depends upon
Comment by Allan McRae (Allan) -
Friday, 30 January 2009, 03:45 GMT
Most of these are due to library updates that require many packages to be rebuilt and some happen to be missed. People are already encouraged to build in a clean chroot.