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#7569 - some thought about old repo pkgs
Attached to Project:
Arch Linux
Opened by Jens Adam (byte) - Thursday, 05 July 2007, 23:27 GMT
Last edited by Andreas Radke (AndyRTR) - Friday, 06 July 2007, 06:49 GMT
Opened by Jens Adam (byte) - Thursday, 05 July 2007, 23:27 GMT
Last edited by Andreas Radke (AndyRTR) - Friday, 06 July 2007, 06:49 GMT
|
DetailsI've just looked at the current and extra pkgs on the ftp server and there are quite a few pkgs that weren't recompiled in years:
current - 30 older than 2 years, 8 older than 4 years extra - 245 > 2 years and 30 > 4 years Should there be some sort of policy to periodically recompile older pkgs (and to bring their PKGBUILDs up to recent standards), or just wait for upstream updates/bug reports, aka "if it ain't broke, don't touch it"? |
This task depends upon
Closed by Andreas Radke (AndyRTR)
Friday, 06 July 2007, 06:49 GMT
Reason for closing: Deferred
Additional comments about closing: once we will have build servers we are able to recompile the whole distribution quick enough on major gcc/glibc changes. right now this is not possible.
Friday, 06 July 2007, 06:49 GMT
Reason for closing: Deferred
Additional comments about closing: once we will have build servers we are able to recompile the whole distribution quick enough on major gcc/glibc changes. right now this is not possible.