Groups | Search | Server Info | Keyboard shortcuts | Login | Register [http] [https] [nntp] [nntps]

Groups > linux.debian.kernel > #62627 > unrolled thread

Bug#846950: Please explain what broke nfs-utils for you (Debian Bug #846950)

Back to article view | Back to linux.debian.kernel

This discussion starts older than the indexed window; earlier articles aren't shown. The article labeled Started by below is the oldest one visible, not the original post.

Contents

  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

#62627 — Bug#846950: Please explain what broke nfs-utils for you (Debian Bug #846950)

[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

[toc] | [next] | [standalone]

#62630

Hi Gaudenz,

On Sun, Dec 2, 2018 at 5:39 AM Gaudenz Steinlin <gaudenz@debian.org> wrote:

> But you did not
> explain how this broke your installation in a way that you think
> this is release critical.

For privilege separation, I keep different keytabs in a directory
/etc/keytabs/. This is an alternative setup to keeping all keytabs in
a file /etc/krb.keytab. One of the scripts you ship
(/lib/systemd/system/rpc-svcgssd.service) requires

ConditionPathExists=/etc/krb5.keytab

That prevents rpc-svcgssd.service from running and any NFSv4 volumes
from being mounted. It breaks the essential function of the package.

> 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 am fan of systemd but still trying to understand its features. A
quick reference would be much appreciated.

> 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.

Together with #849942, this bug broke my installation on every package
update since I filed or amended the reports almost two years ago.

The developer guidelines for level 'grave' state: "makes the package
in question unusable or mostly so" [1]. I therefore disagree with your
reassignment.

I also would be happy to spend some time on this package. I promise I
won't just fix my own bugs. :)

Felix
--
GPG: F04D 1C22 02E2 FA0D 0188  54DA AC58 A94F 1161 8EE0

[1] https://www.debian.org/Bugs/Developer#severities

[toc] | [prev] | [standalone]

Back to top | Article view | linux.debian.kernel

csiph-web