Hi,
Thanks for the advice!
On 3/29/23 3:04 PM, Andreas Tille wrote:
Hi Benjamin,
Am Tue, Mar 28, 2023 at 07:04:52AM +0200 schrieb Pierre Gruet:
Probably you wouold like to do something as in
https://sources.debian.org/src/gedit-plugins/44.1-2/debian/watch/?hl=2#L2
for the gedit-plugins package? This was found by typing "path:debian/watch
beta" in the search field of sources.debian.org. There are other packages
which you could check there.
ACK.
I tried a few things, but haven't figured this out yet. I see there is
versionmangle, dversionmangle, and uversionmangle. I see that we want
the debian version to be 4.0~beta2, not 4.0-beta2 (i.e. with a tilde).
I will try again later.
Secondly, I suppose that any new version would need to go into
experimental, since we are in a hard freeze? I would like to start
working on packaging for version 4 now, since some things have changed
and I'd like to figure out how to deal with them now.
Yes, uploading to experimental is the right thing to do right now :)
I'm wondering whether any beta versions should go to experimental in
general. The fact that upstream marks it as beta is usually a sign that
the code is not for end users production systems. I wrote a couple of
watch files that do not even report any alpha/beta versions as new
version.
I am the upstream :-) I understand the reasoning though. I don't think
you should package all betas, but in this case (i.e. for version
4.0-beta2), as the upstream I feel like its the right thing to do.
I could relabel this as version 4.0, but I would prefer not to, since
there are some features that I want to add before I label this as 4.0.
Perhaps this does not matter, since it would be uploaded to experimental
anyway.
-BenRI
Kind regards
Andreas.
