[Date Prev][Date Next] [Thread Prev][Thread Next] [Date Index] [Thread Index]

RFC: Handling backports for d-i components



Hi folks,

You're receiving this mail because you're on debian-boot@ or you've got
something ACCEPTED into a backports suite; relevant packages seem to be
the following ones: debootstrap, di-netboot-assistant, and flash-kernel.

I think it's fair to say that an upload after dch --bpo is easily done,
but it annoys me a bit not to have the relevant commit and tag recorded
in git in a $suite-backports branch.

Could we please standardize on pushing those when uploading to
backports?

If that's fine with you people, we'll need a common way to handle the
'~' (which isn't allowed in git tags). Let's avoid reinventing the wheel
and let's standardize on the git-buildpackage approach?
| ./usr/lib/python2.7/dist-packages/gbp/deb/git.py:         return version.replace('~', '_').replace(':', '%')

which means e.g. 1.0.73_bpo8+1 for 1.0.73~bpo8+1 (upcoming debootstrap
upload).


Looking forward to your comments.

Mraw,
KiBi.

Attachment: signature.asc
Description: Digital signature


Reply to: