Bug#367281: dput: Please allow upload of upstream source for non -1 versions for backports.org
Hi Christian, thank you for your interest in dput and your bugreport. Christian Hammers wrote: When uploading to www.backports.org it would be quite handy to have a --with-orig that uploads the .orig.tar.gz file as well. I'm not quite sure I do understand your request: The question whether or not the orig.tar.gz is uploaded needs (in the current regime of archive software) to be addressed at the time of the generation of the .changes file. Can you explain in a little more detail how the option could be implemented in dput? Kind regards Thomas -- Thomas Viehmann, http://thomas.viehmann.net/ -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Bug#367281: dput: Please allow upload of upstream source for non -1 versions for backports.org
Hi On 2006-05-15 Thomas Viehmann wrote: Christian Hammers wrote: When uploading to www.backports.org it would be quite handy to have a --with-orig that uploads the .orig.tar.gz file as well. I'm not quite sure I do understand your request: The question whether or not the orig.tar.gz is uploaded needs (in the current regime of archive software) to be addressed at the time of the generation of the .changes file. Can you explain in a little more detail how the option could be implemented in dput? Normally the .orig.tar.gz is only uploaded with the -1 version and thus dpkg-buildpackage puts it only at this versions in the .changes file. When uploading to www.backports.org I never have -1 versions, there will be .0bpo1 for the code that I also uploaded to unstable as -1 so that somebody who upgrades from sarge to sarge+1 will upgrade automatically from the backported .0bpo1 to the newer -1 version. For these cases and those where people upload a backported package for the very first time at all with e.g. a -5bpo1 version, the orig.tar.gz has to be uploaded as well. I'm not sure about uploads to 'experimental'. If it's not the same buildd it might be necessary there, too. Same if people upload packages irregulary to other buildds like Debian GNU/FreeBSD maybe. It works for backports.org if I just upload the orig.tar.gz by ftp so the patch should be fairly easy :) bye, -christian- -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Bug#367281: dput: Please allow upload of upstream source for non -1 versions for backports.org
Hi On 2006-05-15 Thomas Viehmann wrote: I'd be happy to implement backports support (including the default config, though I'd prefer backports.org or backports instead of bpo as the name for the target). The following snipped could go to the default /etc/dput.conf then: [backports] fqdn = www2.backports.org incoming = / login = anonymous Christian Hammers wrote: Normally the .orig.tar.gz is only uploaded with the -1 version and thus dpkg-buildpackage puts it only at this versions in the .changes file. ... unless instructed to do differently by the option -sa. This is the usual (and AFAIK only) way to do this for the regular Debian queues when wanting sourceful uploads with version numbers not being the usual ones for source uploads. Oh right, then using -sa is much better as it allows checking the md5sum via the changes file. Maybe Norbert could put a hint on http://www.backports.org/contribute.html ? bye, -christian- -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Bug#367281: dput: Please allow upload of upstream source for non -1 versions for backports.org
Hi Christian, Norbert, (Norbert, I've CCed you. Could you shed some light on the rules for sourcefulness of uploads in backports.org?) I'd be happy to implement backports support (including the default config, though I'd prefer backports.org or backports instead of bpo as the name for the target). Christian Hammers wrote: Normally the .orig.tar.gz is only uploaded with the -1 version and thus dpkg-buildpackage puts it only at this versions in the .changes file. ... unless instructed to do differently by the option -sa. This is the usual (and AFAIK only) way to do this for the regular Debian queues when wanting sourceful uploads with version numbers not being the usual ones for source uploads. For these cases and those where people upload a backported package for the very first time at all with e.g. a -5bpo1 version, the orig.tar.gz has to be uploaded as well. But how is the upload verified when it's not included in the changes file? This could certainly be done via looking at the .dsc, but I'm not aware that this is implemented in DAK. I'd appreciate more info here. I'm not sure about uploads to 'experimental'. If it's not the same buildd it might be necessary there, too. Same if people upload packages irregulary to other buildds like Debian GNU/FreeBSD maybe. buildd uploads should never be sourceful, experimental is handled by DAK, so I'd expect it to follow the same rules as unstable. Kind regards T. -- Thomas Viehmann, http://thomas.viehmann.net/ -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Bug#367281: dput: Please allow upload of upstream source for non -1 versions for backports.org
Package: dput Version: 0.9.2.21 Severity: wishlist When uploading to www.backports.org it would be quite handy to have a --with-orig that uploads the .orig.tar.gz file as well. bye, -christian- -- System Information: Debian Release: testing/unstable APT prefers unstable APT policy: (500, 'unstable') Architecture: amd64 (x86_64) Shell: /bin/sh linked to /bin/bash Kernel: Linux 2.6.16-1-amd64-k8 Locale: [EMAIL PROTECTED], [EMAIL PROTECTED] (charmap=ISO-8859-15) (ignored: LC_ALL set to [EMAIL PROTECTED]) Versions of packages dput depends on: ii debconf [debconf-2.0] 1.5.1 Debian configuration management sy ii gnupg 1.4.3-1GNU privacy guard - a free PGP rep ii python2.3.5-5An interactive high-level object-o dput recommends no packages. -- debconf information excluded -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
