Re: Bug#703633: debchange --bpo writes bpo60 in debian/changelog as version in wheezy
Gerfried Fuchs <firstname.lastname@example.org> wrote:
> Also, I'm not 100% convinced that wheezy should ship with dch doing
> backports to wheezy. This somehow doesn't make that much sense to me.
> Having dch in unstable (and then jessie) produce wheezy-backports and
> ~bpo70 as default is fine and correct, but having a wheezy environment
> produce that I'm not totally convinced. I rather expect developers to
> use either testing or unstable for their developing environment and thus
> it is enough to have the next release version of dch/devscripts produce
you are saying that Debian developers are (should be) using unstable
anyway. Which is a strong argument for having dch --bpo generate
wheezy-backports, however this seems to be be to rather irelevant when
deciding how wheezy's "dch --bpo" should behave. (Unless you are arguing
for removal of this option, since nobody was using it on stable. ;-)
OTOH I am pretty sure that the majority of people using wheezy's "dch
--bpo" functionality will be generating backports for wheezy itself
and not for oldstable.
`What a good friend you are to him, Dr. Maturin. His other friends are
so grateful to you.'
`I sew his ears on from time to time, sure'