Bug#373265: Please update to new python policy
One word, Piotr: patience. Just today, I get two emails regarding a change in policy, and no more than a few hours later, you tell me that if I don't move my ass, I'll be NMU'ed. Did it ever occur to you, Piotr, that after seeing these emails, I might have actually been working on the package. Already added to the debian/changelog is a succinct "Thanks" for the broken patch you sent in for "366759: Egg support", which included a nice little BASH'ism and an unnecessary bumping of dependencies for CDBS. Now, you tell me you're going to NMU my package: "If you don't respond soon I'll start to prepade a NMU for this weekend (see mentioned mails for details)". Class, I tell you. Pure class. You have energy, which can be beneficial. Now, you need a little tact and patience. Why don't you sit back for a while and let me digest the new information before making a decision about how to handle the new packaging requirements. If you had taken a different approach, I wouldn't be so put-off with you right now. -- Chad Walstrom <[EMAIL PROTECTED]> http://www.wookimus.net/ assert(expired(knowledge)); /* core dump */ -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
Bug#373265: Please update to new python policy
Piotr Ozarowski <[EMAIL PROTECTED]> wrote: > If you don't respond soon I'll start to prepade a NMU for this > weekend (see mentioned mails for details) How kind of you. -- Chad Walstrom <[EMAIL PROTECTED]> http://www.wookimus.net/ assert(expired(knowledge)); /* core dump */ -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
Bug#373265: Please update to new python policy
severity 373265 important thanks On Wed, Jun 14, 2006 at 01:10:08AM +0200, Piotr Ozarowski wrote: > Package: python-cheetah > Version: 1.0-1 > Severity: serious It is not correct to claim that this is a severity: serious issue. Packages that complied with the previous python policy have not become instantly buggy under the new one; if they have, that's a bug in the new python policy. Nor are the packages currently uninstallable in unstable. The announced NMU plan still applies. -- Steve Langasek Give me a lever long enough and a Free OS Debian Developer to set it on, and I can move the world. [EMAIL PROTECTED] http://www.debian.org/ -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
Bug#373265: Please update to new python policy
Package: python-cheetah Version: 1.0-1 Severity: serious Please update your package to new python policy, you can find more info about it in these mails: http://lists.debian.org/debian-devel-announce/2006/06/msg8.html http://lists.debian.org/debian-devel-announce/2006/06/msg9.html If you don't respond soon I'll start to prepade a NMU for this weekend (see mentioned mails for details) -- System Information: Debian Release: testing/unstable APT prefers unstable APT policy: (500, 'unstable'), (1, 'experimental') Architecture: i386 (i686) Shell: /bin/sh linked to /bin/bash Kernel: Linux 2.6.16.12-grsec Locale: LANG=pl_PL, LC_CTYPE=pl_PL (charmap=ISO-8859-2) Versions of packages python-cheetah depends on: ii python2.3-cheetah 1.0-1 text-based template engine and Pyt python-cheetah recommends no packages. -- no debconf information -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]