> I've not checked other architectures but it obviously makes sense to do
> so as a next step.
Here's the diff from amd64 to more arches: (so it unfortunately looks
like something more than just a temporary hiccup on i386)
--- amd64/usr/share/man/man8/pam_exec.8 2016-01-06 17:28:46.0
On 24 January 2016 at 23:55, Tianon Gravi wrote:
> (which clearly patches the pam_exec.8 source file)
... and by that I mean it patches the .xml file, not the bare .8 file
(why both are included in the orig from upstream is beyond me) -- if
the root of the issue is that the
On 24 January 2016 at 23:55, Tianon Gravi wrote:
> I'm attempting a build for i386 locally right now, but I'm not sure
> where to turn next after that to debug this mismatch further.
$ dget -d
http://httpredir.debian.org/debian/pool/main/p/pam/pam_1.1.8-3.1+deb8u1.dsc
Package: libpam-modules
Version: 1.1.8-3.1+deb8u1
Severity: important
Dear Maintainer,
The update for pam in Jessie (1.1.8-3.1+deb8u1) introduces differences in
files in a Multi-Arch: same package. The man pages pam_exec.8.gz and
pam_unix.8.gz contain different information.
Unpacking and
On Mon, 25 Jan 2016 15:37:29 +1100 Stuart Prescott wrote:
> The update for pam in Jessie (1.1.8-3.1+deb8u1) introduces differences in
> files in a Multi-Arch: same package. The man pages pam_exec.8.gz and
> pam_unix.8.gz contain different information.
I've downloaded the debs
5 matches
Mail list logo