On Fri, 3 Feb 2017 01:55:10 -0800 Nye Liu wrote:
> Why is /lib/systemd/system/nfs-common.service being linked to /dev/null
> in debian/nfs-common.links?
Ignore. I see that statd, idmpad, and gssd have their own systemd units now.
Also a stupid question:
Why is /lib/systemd/system/nfs-common.service being linked to /dev/null
in debian/nfs-common.links?
It seems to prevent idmapd, statd, and gssd from being started if
systemd is used, unless you remove the link and forcibly "systemctl
enable nfs-common"
On Sat, 17 Dec 2016 04:54:21 +0100 =?UTF-8?Q?Rapha=c3=abl_Halimi?=
wrote:
> Please explain exactly in what way would my patch introduce
> *incompatible* changes. It's *trivial*, it only adds a single option,
> and a comment to hint that NFSv4 must be disabled in rpc.nfsd
Hi Andreas Henriksson,
Le 14/12/2016 à 08:21, Andreas Henriksson a écrit :
> Congrats on completely derailing a thread that for once was about
> proper mainenance and solving a bigger problem into becoming
> about your pet peeve. Please feel free to stop CCing me if you
> don't actually want my
On 15/12/16 11:44, Daniel Pocock wrote:
>
>
> On 14/12/16 23:41, Ben Hutchings wrote:
>> On Tue, 2016-12-13 at 20:55 +0100, Daniel Pocock wrote: [...]
>>> Thanks for providing this feedback
>>>
>>> I've done the following: - forked the upstream repository
>>
>> The existing packaging repos are
On 14/12/16 23:41, Ben Hutchings wrote:
> On Tue, 2016-12-13 at 20:55 +0100, Daniel Pocock wrote: [...]
>> Thanks for providing this feedback
>>
>> I've done the following: - forked the upstream repository
>
> The existing packaging repos are also based on the upstream git
> repo.
>
OK, I
On 15/12/16 09:50, Sven Geggus wrote:
> Daniel Pocock schrieb am Mittwoch, den 14. Dezember um 13:35 Uhr:
>
>> If the latest NFS / kernel combination in sid definitely won't work
>> without gss-proxy then you could open an RC bug against the nfs-utils
>> package on that basis.
>
> I assume,
Daniel Pocock schrieb am Mittwoch, den 14. Dezember um 13:35 Uhr:
> If the latest NFS / kernel combination in sid definitely won't work
> without gss-proxy then you could open an RC bug against the nfs-utils
> package on that basis.
I assume, that it does work (as it also works in stable), but
Sven Geggus writes:
> Daniel Pocock schrieb am Mittwoch, den 14. Dezember um 11:01 Uhr:
>
>> Would you consider uploading it or proposing it in mentors.debian.net?
>> Please also send details on the gss-proxy ITP bug.
>
> Robbie is the one with the ITP bug, not me :)
On Wed, 2016-12-14 at 09:38 +0100, Daniel Pocock wrote:
>
> On 14/12/16 08:24, Andreas Henriksson wrote:
> > On Wed, Dec 14, 2016 at 08:11:52AM +0100, Daniel Pocock wrote:
> > > I agree the loss of Debian packaging history is a concern, that is one
> > > reason I didn't clobber the existing
On Tue, 2016-12-13 at 20:55 +0100, Daniel Pocock wrote:
[...]
> Thanks for providing this feedback
>
> I've done the following:
> - forked the upstream repository
The existing packaging repos are also based on the upstream git repo.
> - created a debian/sid branch
> - copied debian/* from
On 14/12/16 12:12, Sven Geggus wrote:
> Daniel Pocock schrieb am Mittwoch, den 14. Dezember um 11:01 Uhr:
>
>> Would you consider uploading it or proposing it in mentors.debian.net?
>> Please also send details on the gss-proxy ITP bug.
>
> Robbie is the one with the ITP bug, not me :)
>
> I
Daniel Pocock schrieb am Mittwoch, den 14. Dezember um 11:01 Uhr:
> Would you consider uploading it or proposing it in mentors.debian.net?
> Please also send details on the gss-proxy ITP bug.
Robbie is the one with the ITP bug, not me :)
I just pushed my custom package data to github though:
On 14/12/16 10:31, Sven Geggus wrote:
> Daniel Pocock schrieb am Mittwoch, den 14. Dezember um 09:38 Uhr:
>
>> They stopped including rpc-svcgssd in the default build as of 1.3.2 and
>> recommended gssproxy[1] instead.
>
> Yes, gssproxy is a working drop-in replacement for rpc.svcgssd in case
Daniel Pocock schrieb am Mittwoch, den 14. Dezember um 09:38 Uhr:
> They stopped including rpc-svcgssd in the default build as of 1.3.2 and
> recommended gssproxy[1] instead.
Yes, gssproxy is a working drop-in replacement for rpc.svcgssd in case of
the nfs4-server use case.
Note, that they are
On 14/12/16 08:24, Andreas Henriksson wrote:
> On Wed, Dec 14, 2016 at 08:11:52AM +0100, Daniel Pocock wrote:
>> I agree the loss of Debian packaging history is a concern, that is one
>> reason I didn't clobber the existing repository and I wrote that we can
>> blow this away if there isn't
On Wed, Dec 14, 2016 at 08:11:52AM +0100, Daniel Pocock wrote:
>
>
> On 13/12/16 22:46, Andreas Henriksson wrote:
> > On Tue, Dec 13, 2016 at 08:55:34PM +0100, Daniel Pocock wrote:
> >> Hi Ben,
> >>
> >> Thanks for providing this feedback
> >>
> >> I've done the following:
> >> - forked the
Hello Raphaël Halimi,
Congrats on completely derailing a thread that for once was about
proper mainenance and solving a bigger problem into becoming
about your pet peeve. Please feel free to stop CCing me if you
don't actually want my feedback.
On Tue, Dec 13, 2016 at 11:01:19PM +0100, Raphaël
On 13/12/16 22:46, Andreas Henriksson wrote:
> On Tue, Dec 13, 2016 at 08:55:34PM +0100, Daniel Pocock wrote:
>> Hi Ben,
>>
>> Thanks for providing this feedback
>>
>> I've done the following:
>> - forked the upstream repository
>> - created a debian/sid branch
>> - copied debian/* from jessie
Le 13/12/2016 à 22:09, Andreas Henriksson a écrit :
> I would suggest tagging these both as wontfix. Adding even more options
> to the broken concept of /etc/default just adds to the maintenance burden
> of having to carry this over via the nfs-utils_env.sh bridge.
>
> Both
On Tue, Dec 13, 2016 at 08:55:34PM +0100, Daniel Pocock wrote:
> Hi Ben,
>
> Thanks for providing this feedback
>
> I've done the following:
> - forked the upstream repository
> - created a debian/sid branch
> - copied debian/* from jessie into that branch and committed
> - copied debian/* from
On Tue, Dec 13, 2016 at 09:52:10PM +0100, Daniel Pocock wrote:
>
>
> On 13/12/16 21:40, Raphaël Halimi wrote:
> > Le 13/12/2016 à 21:36, Daniel Pocock a écrit :
> >> Do you think you could investigate a little bit more and add
> >> details to the bug, maybe have a look in Fedora's repositories
On 13/12/16 21:40, Raphaël Halimi wrote:
> Le 13/12/2016 à 21:36, Daniel Pocock a écrit :
>> Do you think you could investigate a little bit more and add
>> details to the bug, maybe have a look in Fedora's repositories to
>> see if they have a way to do that or ask on debian-devel?
>
> I'm not
Le 13/12/2016 à 21:36, Daniel Pocock a écrit :
> Do you think you could investigate a little bit more and add details
> to the bug, maybe have a look in Fedora's repositories to see if they
> have a way to do that or ask on debian-devel?
I'm not sure I'm the right person for this job, I don't
On 13/12/16 21:21, Raphaël Halimi wrote:
> Hi guys,
>
> Sorry to intrude but, since you all seem eager to revive nfs
> packages (which I'm very happy about), could you please take a look
> at #539201 and include my patch ? It would allow to close both this
> bug and #738063, which are both
Hi guys,
Sorry to intrude but, since you all seem eager to revive nfs packages
(which I'm very happy about), could you please take a look at #539201
and include my patch ? It would allow to close both this bug and
#738063, which are both quite old.
(disclaimer : I don't know yet how to do the
On 12/12/16 21:05, Ben Hutchings wrote:
> On Mon, 2016-12-12 at 11:13 +0100, Salvatore Bonaccorso wrote:
>> Hi,
>>
>> On Mon, Dec 12, 2016 at 10:23:49AM +0100, Ferenc Wágner wrote:
> Daniel Pocock writes:
>>>
Could either of you comment on this bug? I saw your names
On Mon, 2016-12-12 at 11:13 +0100, Salvatore Bonaccorso wrote:
> Hi,
>
> On Mon, Dec 12, 2016 at 10:23:49AM +0100, Ferenc Wágner wrote:
> > > > Daniel Pocock writes:
> >
> > > Could either of you comment on this bug? I saw your names in the
> > > nfs-utils changelog. I've
Daniel Pocock writes:
> On 12/12/16 10:23, Ferenc Wágner wrote:
>
>> However, I also encountered serious problems deploying NFS (both client
>> and server side) under jessie, and I would agree to team up and help do
>> better for stretch.
>
> Can you tell us if all the
Hi,
On Mon, Dec 12, 2016 at 10:23:49AM +0100, Ferenc Wágner wrote:
> Daniel Pocock writes:
>
> > Could either of you comment on this bug? I saw your names in the
> > nfs-utils changelog. I've seen various problems with NFS under jessie
> > and I was hoping to help test if
On 12/12/16 10:23, Ferenc Wágner wrote:
> Daniel Pocock writes:
>
>> Could either of you comment on this bug? I saw your names in the
>> nfs-utils changelog. I've seen various problems with NFS under jessie
>> and I was hoping to help test if for stretch.
>
> Hi Daniel,
>
Daniel Pocock writes:
> Could either of you comment on this bug? I saw your names in the
> nfs-utils changelog. I've seen various problems with NFS under jessie
> and I was hoping to help test if for stretch.
Hi Daniel,
I'm not involved in the maintenance of nfs-utils,
Hi Salvatore, Ferenc,
Could either of you comment on this bug? I saw your names in the
nfs-utils changelog. I've seen various problems with NFS under jessie
and I was hoping to help test if for stretch.
https://bugs.debian.org/847681
Regards,
Daniel
On Sat, Dec 10, 2016 at 04:35:46PM +0100, Daniel Pocock wrote:
[...]
> I notice that Andreas made uploads to unstable in June and August 2016:
>
> http://metadata.ftp-master.debian.org/changelogs/main/n/nfs-utils/unstable_changelog
>
> while other developers have made unrelated changes in the
Package: nfs-utils
Version: 1:1.2.8-9.2
Severity: important
X-Debbugs-CC: andr...@fatal.se
I notice that Andreas made uploads to unstable in June and August 2016:
http://metadata.ftp-master.debian.org/changelogs/main/n/nfs-utils/unstable_changelog
while other developers have made unrelated
35 matches
Mail list logo