Groups | Search | Server Info | Keyboard shortcuts | Login | Register [http] [https] [nntp] [nntps]
Groups > linux.debian.kernel > #62627
| From | Gaudenz Steinlin <gaudenz@debian.org> |
|---|---|
| Newsgroups | linux.debian.bugs.dist, linux.debian.kernel |
| Subject | Bug#846950: Please explain what broke nfs-utils for you (Debian Bug #846950) |
| Date | 2018-12-02 14:40 +0100 |
| Message-ID | <x0A8x-38n-3@gated-at.bofh.it> (permalink) |
| References | <sKGAp-nV-1@gated-at.bofh.it> |
| Organization | linux.* mail to news gateway |
Cross-posted to 2 groups.
[Multipart message — attachments visible in raw view] - view raw
Control: severity -1 normal Hi Felix I was working through the list of release critical bugs on nfs-utils and looked at this bug report: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=846950 where you increased the severity to "grave" some time ago. But you did not explain how this broke your installation in a way that you think this is release critical. I agree that supporting all variables and possible configuration variants that are supported by the sysvinit scripts on systemd is a worthwile goal. I don't think this in itself is a release critical bug. You can always use systemd native methods like drop-in configuration snippets to achieve your goal. I'm downgrading the severity again at the moment, please feel free to upgrade again with an explanation how this actually breaks your system in a way that is not just a misconfiguration. Gaudenz -- PGP: 836E 4F81 EFBB ADA7 0852 79BF A97A 7702 BAF9 1EF5
Back to linux.debian.kernel | Previous | Next — Next in thread | Find similar | Unroll thread
Bug#846950: Please explain what broke nfs-utils for you (Debian Bug #846950) Gaudenz Steinlin <gaudenz@debian.org> - 2018-12-02 14:40 +0100 Bug#846950: Please explain what broke nfs-utils for you (Debian Bug #846950) Felix Lechner <felix.lechner@lease-up.com> - 2018-12-02 18:10 +0100
csiph-web