Control: tags -1 + pending
On Wed, 2016-01-27 at 22:21 +, Adam D. Barratt wrote:
> Control: tags -1 + confirmed
>
> On Tue, 2016-01-26 at 15:28 -0800, Tianon Gravi wrote:
> > Due to some kind of mistake in my amd64 build environment (details being
> > tracked down in #812566) the amd64 build
Control: tags -1 + confirmed
On Tue, 2016-01-26 at 15:28 -0800, Tianon Gravi wrote:
> Due to some kind of mistake in my amd64 build environment (details being
> tracked down in #812566) the amd64 build of pam_1.1.8-3.1+deb8u1 is the
> only one that got the intended man page update, but this causes
On 26 January 2016 at 22:05, Adam D. Barratt wrote:
> Is it just the manpage that's the issue? i.e. do the packages published
> as part of the point release include the actual security fix?
Yeah, it's just the manpage that's the issue. Still using #812566 to
track down the _exact_ details, but t
On Wed, 2016-01-27 at 05:48 +, Adam D. Barratt wrote:
> Control: tags -1 + jessie
>
> On Tue, 2016-01-26 at 15:28 -0800, Tianon Gravi wrote:
> > Due to some kind of mistake in my amd64 build environment (details being
> > tracked down in #812566) the amd64 build of pam_1.1.8-3.1+deb8u1 is the
Control: tags -1 + jessie
On Tue, 2016-01-26 at 15:28 -0800, Tianon Gravi wrote:
> Due to some kind of mistake in my amd64 build environment (details being
> tracked down in #812566) the amd64 build of pam_1.1.8-3.1+deb8u1 is the
> only one that got the intended man page update, but this causes
>
Package: release.debian.org
User: release.debian@packages.debian.org
Usertags: binnmu
Severity: normal
Due to some kind of mistake in my amd64 build environment (details being
tracked down in #812566) the amd64 build of pam_1.1.8-3.1+deb8u1 is the
only one that got the intended man page update
6 matches
Mail list logo
