On 2006-08-18 Manoj Srivastava <[EMAIL PROTECTED]> wrote: > The following message is a courtesy copy of an article > that has been posted to gmane.linux.debian.devel.dpkg.bugs as well.
Thanks for that courtesy. > On Thu, 17 Aug 2006 09:03:42 +0200, Andreas Metzler <[EMAIL PROTECTED]> said: [...] >> Hello, Do we require to be able to extraxt unstable's source >> packages with stable's dpkg? Why? There are no upgrade issues (As >> would be for bz2 parts in *binary* packages.). > Err, since we support partal binary upgrades, why should > partial source upgrades be denied? We are trying to reach a > community that uses free source -- so it makes sense to give as much > attention to people using sources as we do to people using the > binaries (the former usually tend to help out more). Hello, The only thing that was reliably working before the change and won't be reliably working after is dpkg-source -x ... which can be worked around with a simple tar -xzf and zcat | patch. Building unstable packages on stable does not work reliably, due to newer build-dependencies (including depending on newer dpkg-dev for binary:Version substitution variable). Due to patch systems like dpatch, quilt or cdbs even just working with the source package without any building involved can require additional unstable packages. I do agree that there is a difference between these cases and tar.bz2 support because it cannot be expressed in Build-Depends but imho it would really be worth to have this in etch. If we just put the extracting stuff in etch extracting packages from sid using bz2 will work on etch, however building them won't. So there is still breakage. The nicest thing would be to have support for building and extracting against .bz2 in etch but disallowing uploads using this feature to sid until etch has been released. cu andreas -- The 'Galactic Cleaning' policy undertaken by Emperor Zhark is a personal vision of the emperor's, and its inclusion in this work does not constitute tacit approval by the author or the publisher for any such projects, howsoever undertaken. (c) Jasper Ffforde -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
