Bug#497557: grokevt: Patch used in NMU 0.4.1-1.1 fixing bug#491430

2008-09-02 Thread Daniel Baumann
Jonas Smedegaard wrote: > Would be nice with a Git hook to auto-tag bugfixes as pending in > bugreports when mentioned as closed in a commit. absolutely. > I sure could use that in my many Git-based packages. me too, i just happen to not have found one, nor the time to make one myself. but shou

Bug#497557: grokevt: Patch used in NMU 0.4.1-1.1 fixing bug#491430

2008-09-02 Thread Jonas Smedegaard
-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 On Tue, Sep 02, 2008 at 06:26:40PM +0200, Daniel Baumann wrote: >Jonas Smedegaard wrote: >> No excuse for my wrong actions, but why was it fixed in VCS and then >> left for weeks without even a note in the bugreport about it? > >christophe fixed it in

Bug#497557: grokevt: Patch used in NMU 0.4.1-1.1 fixing bug#491430

2008-09-02 Thread Daniel Baumann
Jonas Smedegaard wrote: > No excuse for my wrong actions, but why was it fixed in VCS and then > left for weeks without even a note in the bugreport about it? christophe fixed it in time and asked me to upload (2008-08-04); however, i was at debconf (2008-08-01 - 2008-08-19) and the last 1.5 week

Bug#491430: marked as done (wrong configuration directory in /usr/share/python-support/grokevt/grokevt.p)

2008-09-02 Thread Debian Bug Tracking System
Your message dated Tue, 02 Sep 2008 15:47:04 + with message-id <[EMAIL PROTECTED]> and subject line Bug#491430: fixed in grokevt 0.4.1-2 has caused the Debian Bug report #491430, regarding wrong configuration directory in /usr/share/python-support/grokevt/grokevt.p to be marked as done. This

grokevt_0.4.1-2_i386.changes ACCEPTED

2008-09-02 Thread Debian Installer
Accepted: grokevt_0.4.1-2.diff.gz to pool/main/g/grokevt/grokevt_0.4.1-2.diff.gz grokevt_0.4.1-2.dsc to pool/main/g/grokevt/grokevt_0.4.1-2.dsc grokevt_0.4.1-2_all.deb to pool/main/g/grokevt/grokevt_0.4.1-2_all.deb Override entries for your package: grokevt_0.4.1-2.dsc - source utils groke

Processed: Re: Bug#497557: grokevt: Patch used in NMU 0.4.1-1.1 fixing bug#491430

2008-09-02 Thread Debian Bug Tracking System
Processing commands for [EMAIL PROTECTED]: > tags 497557 -patch Bug#497557: grokevt: Patch used in NMU 0.4.1-1.1 fixing bug#491430 Tags were: patch Tags removed: patch > severity 497557 wishlist Bug#497557: grokevt: Patch used in NMU 0.4.1-1.1 fixing bug#491430 Severity set to `wishlist' from `no

Bug#497557: grokevt: Patch used in NMU 0.4.1-1.1 fixing bug#491430

2008-09-02 Thread Daniel Baumann
tags 497557 -patch severity 497557 wishlist thanks Jonas Smedegaard wrote: > Attached is the patch used for my NMU released a moment ago to fix > bug#491430. apart from the wrong tagging/severity of the nmu-diff bug: best practise is that you first send the patch, wait a couple of hours to give t

Bug#497557: marked as done (grokevt: Patch used in NMU 0.4.1-1.1 fixing bug#491430)

2008-09-02 Thread Debian Bug Tracking System
Your message dated Tue, 02 Sep 2008 17:35:28 +0200 with message-id <[EMAIL PROTECTED]> and subject line Re: Bug#497557: grokevt: Patch used in NMU 0.4.1-1.1 fixing bug#491430 has caused the Debian Bug report #497557, regarding grokevt: Patch used in NMU 0.4.1-1.1 fixing bug#491430 to be marked as

Bug#491430: marked as done (wrong configuration directory in /usr/share/python-support/grokevt/grokevt.p)

2008-09-02 Thread Debian Bug Tracking System
Your message dated Tue, 02 Sep 2008 15:32:06 + with message-id <[EMAIL PROTECTED]> and subject line Bug#491430: fixed in grokevt 0.4.1-1.1 has caused the Debian Bug report #491430, regarding wrong configuration directory in /usr/share/python-support/grokevt/grokevt.p to be marked as done. Th

Processing of grokevt_0.4.1-2_i386.changes

2008-09-02 Thread Archive Administrator
grokevt_0.4.1-2_i386.changes uploaded successfully to localhost along with the files: grokevt_0.4.1-2.dsc grokevt_0.4.1-2.diff.gz grokevt_0.4.1-2_all.deb Greetings, Your Debian queue daemon ___ forensics-devel mailing list forensics-devel

grokevt_0.4.1-1.1_amd64.changes ACCEPTED

2008-09-02 Thread Debian Installer
Accepted: grokevt_0.4.1-1.1.diff.gz to pool/main/g/grokevt/grokevt_0.4.1-1.1.diff.gz grokevt_0.4.1-1.1.dsc to pool/main/g/grokevt/grokevt_0.4.1-1.1.dsc grokevt_0.4.1-1.1_all.deb to pool/main/g/grokevt/grokevt_0.4.1-1.1_all.deb Override entries for your package: grokevt_0.4.1-1.1.dsc - sour

Bug#497557: grokevt: Patch used in NMU 0.4.1-1.1 fixing bug#491430

2008-09-02 Thread Jonas Smedegaard
Package: grokevt Version: 0.4.1-1 Severity: normal Tags: patch Hi, Attached is the patch used for my NMU released a moment ago to fix bug#491430. - Jonas -- System Information: Debian Release: lenny/sid APT prefers unstable APT policy: (500, 'unstable') Architecture: amd64 (x86_64) Kerne

Processing of grokevt_0.4.1-1.1_amd64.changes

2008-09-02 Thread Archive Administrator
grokevt_0.4.1-1.1_amd64.changes uploaded successfully to localhost along with the files: grokevt_0.4.1-1.1.dsc grokevt_0.4.1-1.1.diff.gz grokevt_0.4.1-1.1_all.deb Greetings, Your Debian queue daemon ___ forensics-devel mailing list forens

Processed: wrong etc path renders package unusable

2008-09-02 Thread Debian Bug Tracking System
Processing commands for [EMAIL PROTECTED]: > severity 491430 grave Bug#491430: wrong configuration directory in /usr/share/python-support/grokevt/grokevt.p Severity set to `grave' from `important' > thanks Stopping processing here. Please contact me if you need assistance. Debian bug tracking

Bug#491430: wrong etc path renders package unusable

2008-09-02 Thread Jonas Smedegaard
-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 severity 491430 grave thanks Package is unusable when etc path is wrong, because the tools have no commandline option to override the hardcoded default path. - Jonas - -- * Jonas Smedegaard - idealist og Internet-arkitekt * Tlf.: +45 40843136 W