Bug#687779: release.debian.org: New NMU fixing #679966

2013-01-08 Thread Adam D. Barratt
On Tue, 2013-01-08 at 21:05 +0100, John Paul Adrian Glaubitz wrote: > On 01/08/2013 08:36 PM, Adam D. Barratt wrote: > > It's not really worth it just to fix that; if the package is in a VCS it > > would be worth adding there so it's included in any future uploads > > though. > > Ok, so version 93

Bug#687779: release.debian.org: New NMU fixing #679966

2013-01-08 Thread John Paul Adrian Glaubitz
On 01/08/2013 08:36 PM, Adam D. Barratt wrote: It's not really worth it just to fix that; if the package is in a VCS it would be worth adding there so it's included in any future uploads though. Ok, so version 93u+-1.2 is unblocked for migration from t-p-u to testing now? Cheers, Adrian --

Bug#687779: release.debian.org: New NMU fixing #679966

2013-01-08 Thread Adam D. Barratt
On Tue, 2013-01-08 at 20:14 +0100, John Paul Adrian Glaubitz wrote: > On 01/08/2013 08:13 PM, Adam D. Barratt wrote: > > Approved, thanks. fwiw, the description appears to be missing some words > > > > +Description: fix-cd-builtin > > + This patch integrates the changes from the upstream commit > >

Processed: Re: Bug#687779: release.debian.org: New NMU fixing #679966

2013-01-08 Thread Debian Bug Tracking System
Processing commands for cont...@bugs.debian.org: > retitle 687779 unblock: ksh/93u+-1.2 Bug #687779 [release.debian.org] unblock: ksh/93u+20120628-1 Changed Bug title to 'unblock: ksh/93u+-1.2' from 'unblock: ksh/93u+20120628-1' > thanks Stopping processing here. Please contact me if you need ass

Bug#687779: release.debian.org: New NMU fixing #679966

2013-01-08 Thread John Paul Adrian Glaubitz
retitle 687779 unblock: ksh/93u+-1.2 thanks On Mon, Jan 07, 2013 at 01:24:29PM +, Adam D. Barratt wrote: > >So, what do you suggest? New upstream version or patching the current > >version in unstable? > > Either would work for me. otoh, maybe I'm being too fussy - it just > feels a little wr

Bug#687779: release.debian.org: New NMU fixing #679966

2013-01-07 Thread John Paul Adrian Glaubitz
On Mon, Jan 07, 2013 at 01:24:29PM +, Adam D. Barratt wrote: > On 07.01.2013 13:19, John Paul Adrian Glaubitz wrote: > >On Mon, Jan 07, 2013 at 01:11:01PM +, Adam D. Barratt wrote: > >>I wasn't suggesting getting a new upstream version in to testing. > >>The fact that the fix for testing is

Bug#687779: release.debian.org: New NMU fixing #679966

2013-01-07 Thread Adam D. Barratt
On 07.01.2013 13:19, John Paul Adrian Glaubitz wrote: On Mon, Jan 07, 2013 at 01:11:01PM +, Adam D. Barratt wrote: I wasn't suggesting getting a new upstream version in to testing. The fact that the fix for testing is going via tpu doesn't change the wish to have it fixed in unstable first.

Bug#687779: release.debian.org: New NMU fixing #679966

2013-01-07 Thread John Paul Adrian Glaubitz
On Mon, Jan 07, 2013 at 01:11:01PM +, Adam D. Barratt wrote: > I wasn't suggesting getting a new upstream version in to testing. > The fact that the fix for testing is going via tpu doesn't change > the wish to have it fixed in unstable first. So, what do you suggest? New upstream version or p

Bug#687779: release.debian.org: New NMU fixing #679966

2013-01-07 Thread Adam D. Barratt
On 07.01.2013 13:03, John Paul Adrian Glaubitz wrote: On Sun, Jan 06, 2013 at 10:07:51PM +, Adam D. Barratt wrote: Thanks for the confirmation. In general, we prefer that the fixes are applied and verified in unstable first, as it's generally easier to fix up in the event of any issues. (I

Bug#687779: release.debian.org: New NMU fixing #679966

2013-01-07 Thread John Paul Adrian Glaubitz
On Sun, Jan 06, 2013 at 10:07:51PM +, Adam D. Barratt wrote: > On Wed, 2013-01-02 at 22:18 +0100, John Paul Adrian Glaubitz wrote: > > On Wed, Jan 02, 2013 at 09:05:37PM +, Adam D. Barratt wrote: > > > The version information for #679966 looks like it might have got broken > > > at some poi

Bug#687779: release.debian.org: New NMU fixing #679966

2013-01-06 Thread Adam D. Barratt
On Wed, 2013-01-02 at 22:18 +0100, John Paul Adrian Glaubitz wrote: > On Wed, Jan 02, 2013 at 09:05:37PM +, Adam D. Barratt wrote: > > The version information for #679966 looks like it might have got broken > > at some point; is the bug still present in the unstable package? > > Yes, the bug i

Bug#687779: release.debian.org: New NMU fixing #679966

2013-01-02 Thread John Paul Adrian Glaubitz
Hi Adam! On Wed, Jan 02, 2013 at 09:05:37PM +, Adam D. Barratt wrote: > For future reference, it's preferred if you post the debdiff and then > wait for an ack before uploading to tpu; I realise that dev-ref isn't > entirely helpful here (it's on the to-do list somewhere). Ok, I didn't know t

Bug#687779: release.debian.org: New NMU fixing #679966

2013-01-02 Thread Adam D. Barratt
On Wed, 2013-01-02 at 21:28 +0100, John Paul Adrian Glaubitz wrote: > I just created an updated ksh package for testing and uploaded > it as an NMU to t-p-u. I have verified my fix to work and the > built-in cd works now properly as it is using all upstream changes > addressing the problem while ig

Bug#687779: release.debian.org: New NMU fixing #679966

2013-01-02 Thread John Paul Adrian Glaubitz
Package: release.debian.org Followup-For: Bug #687779 User: release.debian@packages.debian.org Usertags: unblock Hi, I just created an updated ksh package for testing and uploaded it as an NMU to t-p-u. I have verified my fix to work and the built-in cd works now properly as it is using all u