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#56533 - Should not build from git when released packages are available
Attached to Project:
Arch Linux
Opened by Mike Sharov (msharov) - Friday, 01 December 2017, 21:06 GMT
Last edited by Doug Newgard (Scimmia) - Friday, 01 December 2017, 23:58 GMT
Opened by Mike Sharov (msharov) - Friday, 01 December 2017, 21:06 GMT
Last edited by Doug Newgard (Scimmia) - Friday, 01 December 2017, 23:58 GMT
|
DetailsSome packages, such as gcc and firefox, currently build by cloning the bleeding edge repository and selecting some commit from it. Both gcc and firefox release source tarballs for each version, and those should be used instead. The current state of affairs makes it impossible to compile an older version of the package. It also requires unnecessarily downloading the entire project repository instead of just the version being compiled. This not only takes forever, but can take a substatial bite from our ISP data caps.
|
This task depends upon
Comment by loqs (loqs) -
Friday, 01 December 2017, 22:48 GMT
How does it make it impossible to compile an older version of the package?
Comment by Mike Sharov (msharov) -
Friday, 01 December 2017, 23:44 GMT
By not locking to a specific version. I tried to compile firefox 55, but makepkg pulled in the mercurial main branch, which apparently was 57 and failed.