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#27650 - ca-certificates-20111211-1 bug in net-install only.
Attached to Project:
Arch Linux
Opened by Martin Hertz (mhertz) - Wednesday, 21 December 2011, 03:45 GMT
Last edited by Florian Pritz (bluewind) - Sunday, 01 January 2012, 18:28 GMT
Opened by Martin Hertz (mhertz) - Wednesday, 21 December 2011, 03:45 GMT
Last edited by Florian Pritz (bluewind) - Sunday, 01 January 2012, 18:28 GMT
|
DetailsDescription:
In a fresh install of base goup from netinstall media, there's reported: "Installing ca-certificates... Error: Command failed to execute correctly." The resulting install then misses the file: /etc/ssl/crt/ca-certificates.crt, which can be generated by running post-install: 'update-ca-certificates --fresh', or reinstalling the package... The above mentioned command is set to run from the packages install-script, and it also seems like it has been run, since there's a bunch of symlinks under '/etc/ssl/cert/', but just the file: ca-certificates.crt isn't generated... There weren't anything more specific in /var/log/{pacman,aif}.log about this either... Thanks in advance! Additional info: * package version(s) * config and/or log files etc. Steps to reproduce: |
This task depends upon
the AIF/archiso involvement is fairly limited, aif just calls pacman --root /mnt/ --config /tmp/pacman.conf which points to a remote core repository (assuming that's what Martin enabled), and does `-Syu` <list of packages selected by user>. if something goes wrong during that part, it is likely to be something with postinst of ca-certificates which invokes commands which fail.
FS#27699I've just finished testing by installing arch64 into a vm and enabling [testing] repo additionally, and this time no errors reported during the install of ca-certificates and there were correctly generated the file: /etc/ssl/crt/ca-certificates.crt...
Thanks for your help, it's much appreciated!
CU, Martin.