Bug#432893: Possible patch for 432893

2007-09-12 Thread brian m. carlson
On Thu, Sep 13, 2007 at 01:18:14AM +0200, Kurt Roeckx wrote: > > You're right, this seems to be rather confusing. I think what it's > trying to say is if abort-remove fails, set to Failed-Config, else keep > the (Installed) state. It should probably also keep the other states. > > You could als

Bug#432893: Possible patch for 432893

2007-09-12 Thread Kurt Roeckx
On Wed, Sep 12, 2007 at 10:21:11PM +, brian m. carlson wrote: > On Wed, Sep 12, 2007 at 11:27:27PM +0200, Kurt Roeckx wrote: > > On Wed, Sep 12, 2007 at 08:59:37PM +, brian m. carlson wrote: > > > package dpkg > > > tags 432893 + patch > > > kthxbye > > > > > > Attached is a patch that *sh

Bug#432893: Possible patch for 432893

2007-09-12 Thread brian m. carlson
On Wed, Sep 12, 2007 at 11:27:27PM +0200, Kurt Roeckx wrote: > On Wed, Sep 12, 2007 at 08:59:37PM +, brian m. carlson wrote: > > package dpkg > > tags 432893 + patch > > kthxbye > > > > Attached is a patch that *should* fix this bug. It simply restores the > > previous state of a package when

Bug#432893: Possible patch for 432893

2007-09-12 Thread Kurt Roeckx
On Wed, Sep 12, 2007 at 08:59:37PM +, brian m. carlson wrote: > package dpkg > tags 432893 + patch > kthxbye > > Attached is a patch that *should* fix this bug. It simply restores the > previous state of a package when a removal fails, instead of simply > setting it to installed. Preliminary

Processed: Possible patch for 432893

2007-09-12 Thread Debian Bug Tracking System
Processing commands for [EMAIL PROTECTED]: > package dpkg Ignoring bugs not assigned to: dpkg > tags 432893 + patch Bug#432893: dpkg: Failed install followed by failed remove results in installed state There were no tags set. Tags added: patch > kthxbye Stopping processing here. Please contact

Bug#432893: Possible patch for 432893

2007-09-12 Thread brian m. carlson
package dpkg tags 432893 + patch kthxbye Attached is a patch that *should* fix this bug. It simply restores the previous state of a package when a removal fails, instead of simply setting it to installed. Preliminary testing seems to confirm that this works. A changelog entry is also included.

Bug#441904: dpkg: [update-alternatives]: Please add a machine-readable variant of --display

2007-09-12 Thread Frank Küster
Raphael Hertzog <[EMAIL PROTECTED]> wrote: >> This showed up in #438551, and we fixed it by prepending LC_ALL=C to our >> call to u-a, but it would be nice if there was an interface to query >> update-alternative's status with respect to a particular alternative. >> Something which doesn't change

Processed: forcibly merging 323911 440956

2007-09-12 Thread Debian Bug Tracking System
Processing commands for [EMAIL PROTECTED]: > # Automatically generated email from bts, devscripts version 2.10.8 > forcemerge 323911 440956 Bug#323911: dpkg-dev: [manual] dpkg-buildpackage: Please clarify -i option explanation Bug#440956: dpkg: dpkg-source [manual] Clarify text of options -i Forc

Processed: Re: Bug#441958: locales: 'EOF on stdin at conffile prompt' on noninteractive update

2007-09-12 Thread Debian Bug Tracking System
Processing commands for [EMAIL PROTECTED]: > reassign 441958 dpkg Bug#441958: locales: 'EOF on stdin at conffile prompt' on noninteractive update Bug reassigned from package `locales' to `dpkg'. > thanks Stopping processing here. Please contact me if you need assistance. Debian bug tracking sys

Bug#441904: dpkg: [update-alternatives]: Please add a machine-readable variant of --display

2007-09-12 Thread Raphael Hertzog
Hi, On Mon, 10 Sep 2007, Frank Küster wrote: > We had to fix some older alternatives breakage from a package we took > over, and used update-alternatives --display to see whether we needed to > do anything. Unfortunately, > > # [EMAIL PROTECTED] update-alternatives --display xdvi.bin > xdvi.bin

Bug#432893: Processed: severity of 432893 is important

2007-09-12 Thread Raphael Hertzog
Hi, On Tue, 11 Sep 2007, Filipus Klutiero wrote: > I don't see why I should not change the severity of a report against a > package I'm not maintaining if the severity looks incorrect and the > maintainance team didn't state anything about the severity. If you were > basing that on something, plea