Bug#847681: packaging repository and sid diverging? Various fixes needed.
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 consensus about it.
>
> Yeah, but ever more importantly now is to not get stuck on details I guess.
>
It will not be too hard to switch back and forth between the two
approaches, so lets leave the final decision on that for another couple
of weeks.
The bigger issues:
- should it live in the kernel section on alioth (where only members of
that team can commit) or collab-maint (where any DD can commit)?
- should it continue to list the kernel packaging team as the
maintainer, or is there potentially another team suitable for it? Given
the server-side stuff is partly kernel code, there is a strong reason
for the kernel team to see all the bug reports
- does it actually work for more people? I only did basic tests of the
new 1.3.4 package with NFS 3 and a single client in a jessie system the
latest kernel from jessie-backports. Somebody should probably test the
package on a system running stretch or sid and also try the NFSv4 stuff.
- does anybody have time to fully review major upstream changes? These
are things I noticed:
Upstream now installs nfsdcltrack to /sbin - does the Debian kernel look
for it in that location too or does it want /usr/sbin/nfsdcltrack or was
that just a bug in the jessie package putting it in the wrong place?
They stopped including rpc-svcgssd in the default build as of 1.3.2 and
recommended gssproxy[1] instead. I added the flag to enable svcgssd to
debian/rules so the package remains similar to the previous one, but I
am not using svcgssd so I haven't checked any more closely. I notice
Robbie (added on CC) has an ITP[2] for gss-proxy, will it be in stretch?
They removed[3] gss_clnt_send_err and gss_destroy_creds - could anybody
be using those from scripts? I simply dropped them from the .install file
Can anybody review the Ubuntu patches for the systemd unit files against
the upstream changes? I tried to merge them and all the daemons I use
are running but maybe there is some subtle issue that I haven't noticed,
I don't work on systemd unit files every day.
Regards,
Daniel
1. https://fedorahosted.org/gss-proxy/
2. https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=838282
3. https://patchwork.kernel.org/patch/2985231/
Reply to: