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]
