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#51865 - [systemd] Automatically GC queued device unit jobs upsteam
Attached to Project:
Arch Linux
Opened by Nick (whompy) - Thursday, 17 November 2016, 18:54 GMT
Last edited by Dave Reisner (falconindy) - Friday, 18 November 2016, 13:02 GMT
Opened by Nick (whompy) - Thursday, 17 November 2016, 18:54 GMT
Last edited by Dave Reisner (falconindy) - Friday, 18 November 2016, 13:02 GMT
|
DetailsDescription: Bug #1921 (https://github.com/systemd/systemd/issues/1921) in systemd was recently closed with an upstream fix (https://github.com/systemd/systemd/pull/4678). This basically covered a situation with a btrfs raid on encrypted block devices where a mount service would never complete. The patch fixes the issue by cleaning these orphaned services. Would it be possible to include this patch in the next systemd update in case a new upstream release isn't made for a while?
Additional info: * package version(s) * config and/or log files etc. Steps to reproduce: Boot with btrfs raid on encrypted block devices on any recent version of systemd. |
This task depends upon
Closed by Dave Reisner (falconindy)
Friday, 18 November 2016, 13:02 GMT
Reason for closing: Won't fix
Additional comments about closing: This will be included with v233.
Friday, 18 November 2016, 13:02 GMT
Reason for closing: Won't fix
Additional comments about closing: This will be included with v233.
Comment by Dave Reisner (falconindy) -
Friday, 18 November 2016, 12:27 GMT
Sorry, this won't happen. The "fix" is no less than 5-7 patches and makes intrusive changes to the state machine and dbus API. Most of the pull request applies cleanly to v232, but it's not impossible that this could introduce other bugs, and I figure given that issue 1921 just had its birthday 2 days ago, it'll be okay if this waits for release with v233.
Comment by Nick (whompy) -
Friday, 18 November 2016, 12:54 GMT
Okay. Thanks for the quick response! It's really more of an inconvenience anyway, so I definitely understand. Didn't catch quite how intrusive the patch set was.