Hi Ted, On Sun, May 29, 2011 at 11:32:59PM +0200, Carsten Hey wrote: > > > nope. The process is that all problems ought to be fixed in unstable > > > first and then you send us a debdiff for a targetted upload to > > > stable-proposed-updates (diff against what's currently in stable), > > > we approve it and then you upload the result. We cannot cherry-pick > > > from testing. (However sometimes what's in s-p-u gets copied over > > > into testing if it's newer.) > > Well, what I uploaded into unstable was built in a stable chroot, so > > assuming it's approved it's just a matter of my uploading to > > stable-proposed-updates, right? (Or do you want to build the x86 > > binary packages from source?) We cannot use the unstable version verbatim for technical reasons. So I'd like to ask you to add a changelog entry with "Upload to proposed-updates." and a version like 1.41.12-4+squeeze1. It needs to be built in a stable chroot and you'd need to specify the stable version with "-v1.41.12-2" to debuild/ dpkg-buildpackage so that the right changelog entries are included in the .changes. I.e. please go ahead. We'll copy the +squeeze1 over into testing and unstable at point release time if it's newer. The deadline for the next point release is this weekend, though. I apologize for the delay in responding; we're tying up the lose ends for the point release currently and this was one of them, which was lingering around because we generally don't like touching core stuff with extensive changes. Kind regards and thanks for your efforts, Philipp Kern -- .''`. Philipp Kern Debian Developer : :' : http://philkern.de Stable Release Manager `. `' xmpp:phil@0x539.de Wanna-Build Admin `- finger pkern/key@db.debian.org
Attachment:
signature.asc
Description: Digital signature