Re: bug closed by $p4m mail?

2008-07-02 Thread Lars Wirzenius
to, 2008-07-03 kello 08:39 +0200, Johannes Wiedersich kirjoitti: > What is the proper way to get the s_p_a_m removed from the bts and to > reopen the bug? To contact the 'sender' of the spam mail as suggested by > the bts seems absurd. For removing the spam, see the link near the bottom of the bug

bug closed by $p4m mail?

2008-07-02 Thread Johannes Wiedersich
-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 Hi all! One of my bug reports appears to have been closed by a s_p_a_m mail: > #325588: kile crashes on auto-save, incurring data loss > > It has been closed by "Theron Landers" > <[EMAIL PROTECTED]> (reply to > [EMAIL PROTECTED]). > > Their expl

Re: Dpkg triggers and user experience, aka "How do I disable those triggers" side effect.

2008-07-02 Thread Lars Wirzenius
to, 2008-07-03 kello 08:24 +0200, Andreas Tille kirjoitti: > /me as a completely uneducated apt / aptitude user thinks: Triggers have > done more harm than good. I haven't been following trigger adoption very much, so I'm ignorant: what harm have triggers done? -- To UNSUBSCRIBE, email to [EMA

Re: Dpkg triggers and user experience, aka "How do I disable those triggers" side effect.

2008-07-02 Thread Andreas Tille
On Wed, 2 Jul 2008, Joey Hess wrote: #473461 But this bug ends with a question: What do you think? /me as a completely uneducated apt / aptitude user thinks: Triggers have done more harm than good. Please consider this as a stupid users opinion but I would not mention this "feature" as

Re: Bug#489059: ITP: mnemosyne-blog -- Maildir-to-blog compiler with XML templating and Python extensions

2008-07-02 Thread Ben Finney
Decklin Foster <[EMAIL PROTECTED]> writes: > I wrote this ages ago, and in the meantime another package was > renamed to "mnemosyne", so in the tradition of epiphany-browser (and > sup-mail, which I am presently packaging) I'm going with > "mnemosyne-blog" and renaming things out of the way approp

Bug#489059: ITP: mnemosyne-blog -- Maildir-to-blog compiler with XML templating and Python extensions

2008-07-02 Thread Decklin Foster
Package: wnpp Severity: wishlist Owner: Decklin Foster <[EMAIL PROTECTED]> * Package name: mnemosyne-blog Version : 0.9 Upstream Author : Decklin Foster <[EMAIL PROTECTED]> * URL : http://www.red-bean.com/~decklin/mnemosyne/ * License : ISC Programming Lang: P

Re: Not stopping daemons, where are we?

2008-07-02 Thread Hai Zaar
On Wed, Jul 2, 2008 at 8:30 PM, Marvin Renich <[EMAIL PROTECTED]> wrote: > * Bernd Eckenfels <[EMAIL PROTECTED]> [080701 20:45]: >> In article <[EMAIL PROTECTED]> you wrote: >> >> I mean the pending-write case is the most obvious. But what about resolver >> >> caches, VPNs and the like? >> > >> > W

Re: Dpkg triggers and user experience, aka "How do I disable those triggers" side effect.

2008-07-02 Thread Joey Hess
Tilo Schwarz wrote: > Actually, as "Joe User" (me ;-) I'm wondering, why I get during an update > of let's say 20 packages the triggers message for man-db and menu not > once at the end, but several times every few packages. I thought, the > idea is, to let the triggers to the work once during o

Re: Dpkg triggers and user experience, aka "How do I disable those triggers" side effect.

2008-07-02 Thread Tilo Schwarz
On Mon, 30 Jun 2008 15:27:55 +0200, Scott Kitterman <[EMAIL PROTECTED]> wrote: [...] From a "Joe User" perspective, I think delay rather misses the point. The reason for triggers is not to do stuff later, it's to consolidate processing so actions don't need to be done multiple times. A

Re: Not stopping daemons, where are we?

2008-07-02 Thread Joe Smith
"Marvin Renich" <[EMAIL PROTECTED]> wrote in message news:[EMAIL PROTECTED] * Bernd Eckenfels <[EMAIL PROTECTED]> [080701 20:45]: In article <[EMAIL PROTECTED]> you wrote: >> I mean the pending-write case is the most obvious. But what about >> resolver >> caches, VPNs and the like? > > What

Re: ITP: debian-backports-keyring -- GnuPG archive key of the backports.org repository

2008-07-02 Thread Francesco Poli
On Wed, 2 Jul 2008 00:13:06 -0700 Steve Langasek wrote: [...] > The real issue is not that you were posting without disclaimers. The real > issue is that you post to debian-legal with *content* that is inappropriate > *because* you are not a lawyer or a Debian developer. > > When someone posts t

Re: Not stopping daemons, where are we?

2008-07-02 Thread Marvin Renich
* Bernd Eckenfels <[EMAIL PROTECTED]> [080701 20:45]: > In article <[EMAIL PROTECTED]> you wrote: > >> I mean the pending-write case is the most obvious. But what about resolver > >> caches, VPNs and the like? > > > > What kind of data loss do you expect to arise from shutting down a VPN > > clien

Re: ITP: debian-backports-keyring -- GnuPG archive key of the backports.org repository

2008-07-02 Thread Mark Brown
On Wed, Jul 02, 2008 at 08:34:31PM +1000, Ben Finney wrote: > Steve Langasek <[EMAIL PROTECTED]> writes: > > The real issue is not that you [Francesco Poli] were posting without > > disclaimers. > The issue that led to those disclaimers was *exactly* that some > thought Francesco should make it c

Bug#488975: ITP: libdata-report-perl -- Framework for flexible reporting

2008-07-02 Thread Angel Abad (Ikusnet SLL)
Package: wnpp Severity: wishlist Owner: "Angel Abad (Ikusnet SLL)" <[EMAIL PROTECTED]> * Package name: libdata-report-perl Version : 0.06 Upstream Author : Johan Vromans <[EMAIL PROTECTED]> * URL : http://search.cpan.org/dist/Data-Report/ * License : (GPL, Arti

Re: ITP: debian-backports-keyring -- GnuPG archive key of the backports.org repository

2008-07-02 Thread Ben Finney
Reinhard Tartler <[EMAIL PROTECTED]> writes: > Walter Landry <[EMAIL PROTECTED]> writes: > > > [debian-legal] does not restrict itself to dispensing the > > decisions of the ftp-masters. > > Perhaps that should be fixed then. What would your proposed fix entail? Surely not divorcing the ftp-mas

Re: ITP: debian-backports-keyring -- GnuPG archive key of the backports.org repository

2008-07-02 Thread Reinhard Tartler
Walter Landry <[EMAIL PROTECTED]> writes: > Your [Steve Langasek's] complaint, on the other hand, is just as valid > or invalid whether Francesco is a Debian developer or not. However, > the description of the list says: > > debian-legal mailing list > Copyright, licensing and patent issues >

Re: ITP: debian-backports-keyring -- GnuPG archive key of the backports.org repository

2008-07-02 Thread Ben Finney
Steve Langasek <[EMAIL PROTECTED]> writes: > The real issue is not that you [Francesco Poli] were posting without > disclaimers. The issue that led to those disclaimers was *exactly* that some thought Francesco should make it clear he is not speaking officially. > When someone posts to debian-le

Re: ITP: debian-backports-keyring -- GnuPG archive key of the backports.org repository

2008-07-02 Thread Walter Landry
Steve Langasek <[EMAIL PROTECTED]> wrote: > On Mon, Jun 23, 2008 at 07:34:22PM +0200, Francesco Poli wrote: > > As a consequence I began adding the disclaimers to my messages, in > > order to explicitly remind readers about the above facts. > > > Now, you say that those disclaimers are a waste of

Re: ITP: debian-backports-keyring -- GnuPG archive key of the backports.org repository

2008-07-02 Thread Steve Langasek
On Mon, Jun 23, 2008 at 07:34:22PM +0200, Francesco Poli wrote: > On Mon, 23 Jun 2008 17:16:28 +0200 Joerg Jaspert wrote: > I *used* to think that those disclaimers are implicit in most cases. > But then, I was harshly accused of not making it clear enough that > I am neither a lawyer, nor a Debi

Re: Not stopping daemons, where are we?

2008-07-02 Thread Bernd Eckenfels
In article <[EMAIL PROTECTED]> you wrote: > Please explain why these third parties are doing something so braindead as > to rely on the VPN connection only ever disappearing gracefully. I am not talking about the third party, it could be an internal VPN, and yes it is braindead, welcome to the rea