Arch Linux

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!
Tasklist

FS#45402 - [systemd] upgrade does not update systemd-boot

Attached to Project: Arch Linux
Opened by Federico (nierro) - Sunday, 21 June 2015, 08:53 GMT
Last edited by Dave Reisner (falconindy) - Monday, 22 June 2015, 17:40 GMT
Task Type Feature Request
Category Packages: Core
Status Closed
Assigned To Thomas Bächler (brain0)
Evangelos Foutras (foutrelis)
Dave Reisner (falconindy)
Architecture All
Severity Low
Priority Normal
Reported Version
Due in Version Undecided
Due Date Undecided
Percent Complete 100%
Votes 2
Private No

Details

Description:
After upgrade to systemd 221 (and after a reboot), i noticed systemd-boot was still at 220. So i manually issue a "bootctl update", and after a reboot it is now at v221.
Shouldn't systemd.install script provide a systemd-update function?

Additional info:
* systemd 221-1

This task depends upon

Closed by  Dave Reisner (falconindy)
Monday, 22 June 2015, 17:40 GMT
Reason for closing:  Won't implement
Comment by Federico (nierro) - Sunday, 21 June 2015, 08:53 GMT
I meant *systemd-boot update function
Comment by Dave Reisner (falconindy) - Monday, 22 June 2015, 17:16 GMT
Since usage of systemd-boot is optional with the package, I don't see a compelling reason to run 'bootctl update' automatically. I don't trust that 'bootctl update' won't do something nasty (bugs) and wrongly mess with someone's non-gummiboot bootloader.
Comment by Federico (nierro) - Monday, 22 June 2015, 17:40 GMT
You're right, i didn't think about that.
Well i'll issue a 'bootctl update' manually after every systemd upgrade then :)
Thanks for your time!

Loading...