Your message dated Tue, 11 Apr 2017 05:49:00 +0000
with message-id <[email protected]>
and subject line Re: Bug#852395: unblock: gssproxy/0.5.1-2
has caused the Debian Bug report #852395,
regarding unblock: gssproxy/0.5.1-2
to be marked as done.
This means that you claim that the problem has been dealt with.
If this is not the case it is now your responsibility to reopen the
Bug report if necessary, and/or fix the problem forthwith.
(NB: If you are a system administrator and have no idea what this
message is talking about, this may indicate a serious mail system
misconfiguration somewhere. Please contact [email protected]
immediately.)
--
852395: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=852395
Debian Bug Tracking System
Contact [email protected] with problems
--- Begin Message ---
Package: release.debian.org
Severity: normal
User: [email protected]
Usertags: unblock
Please unblock package gssproxy
gssproxy has been 10 days in unstable, and allowing it to migrate will fix
bug#848306 (severity: important) in nfs-common. gssproxy is a new package in
unstable (so no debdiff is included), and would have made the freeze had I not
made a mistake documenting copyright.
Thanks.
unblock gssproxy/0.5.1-2
-- System Information:
Debian Release: 9.0
APT prefers testing-debug
APT policy: (600, 'testing-debug'), (600, 'testing'), (400,
'unstable-debug'), (400, 'unstable'), (200, 'experimental-debug'), (200,
'experimental')
Architecture: amd64 (x86_64)
Foreign Architectures: i386
Kernel: Linux 4.8.0-2-rt-amd64 (SMP w/4 CPU cores; PREEMPT)
Locale: LANG=en_US.UTF-8, LC_CTYPE=en_US.UTF-8 (charmap=UTF-8)
Shell: /bin/sh linked to /bin/dash
Init: sysvinit (via /sbin/init)
--- End Message ---
--- Begin Message ---
Robbie Harwood:
> Niels Thykier <[email protected]> writes:
>
>> Ok - as I understand it, what we are dealing with here is:
>>
>> * systemd: You can get gssproxy + NFS and it "just works(tm)" if
>> you install gssproxy. Otherwise you get svcgssd + NFS.
>> (This is how I understood Neil Brown)
>> * sysvinit: Business as usual either way.
>>
>>
>> So granting gssproxy will:
>>
>> * Provide systemd users with NFS + gssproxy if they opt-in to it
>> (by installing it)
>> * Provide sysvinit users gssproxy and if they want to use it with
>> NFS, they may have to tweak things themselves
>> * Not cause any issues for neither systemd users nor sysvinit users
>> just by installing it.
>> * enable users to get gssproxy which is not deprecated (unlike the
>> existing svcgssd)
>>
>> Is the above correct? And you are happy with gssproxy/0.5.1-2 as it is?
>
> That sounds right. And yes.
>
Ok, exception granted. gssproxy should migrate later today.
~Niels
--- End Message ---
