Hi,

a) The version numbering rules provide for a '1:' prefix to be used to
deal with version numbering mistakes. A version number starting with
'1:' counts as higher than any without such a prefix; a '2:' counts as
higher than '1:', etc. So you could re-upload 2.10.08+ds-1 with version >number '1:2.10.08+ds-1' to supplant 2.11.01+ds-3. However the downside
to this approach is that you're forevermore committed to having that
prefix in the version numbering.

Don't do this.

Using am epoch has to be agreed on in the project, and for good reasons. First and foremost, the epoch is not encoded into the package file name, thus causing trouble when in the future you get to upload 1:2.11.01.

-nik

--- SoupGate-Win32 v1.05
* Origin: fsxNet Usenet Gateway (21:1/5)

Did we ever implement the "bump epoch should go to new queue"?

I would like to see packages going in some new queue, this way ftpmasters can check if the epoch bump was a mistake or not.
(and I can't just test by myself, I don't want to risk bumping epoch on my packages!)

G.






Il giovedì 29 febbraio 2024 alle ore 01:15:59 CET, Dominik George <[email protected]> ha scritto:





Hi,

a) The version numbering rules provide for a '1:' prefix to be used to
deal with version numbering mistakes. A version number starting with
'1:' counts as higher than any without such a prefix; a '2:' counts as
higher than '1:', etc. So you could re-upload 2.10.08+ds-1 with version >number '1:2.10.08+ds-1' to supplant 2.11.01+ds-3. However the downside
to this approach is that you're forevermore committed to having that
prefix in the version numbering.

Don't do this.

Using am epoch has to be agreed on in the project, and for good reasons. First and foremost, the epoch is not encoded into the package file name, thus causing trouble when in the future you get to upload 1:2.11.01.

-nik

--- SoupGate-Win32 v1.05
* Origin: fsxNet Usenet Gateway (21:1/5)

On Mon, Mar 04, 2024 at 12:09:26AM +0100, Hilmar Preu�e wrote:

On 29.02.24 00:42, Lyndon Brown wrote:

Hello,

b) Re-upload 2.10.08+ds-1 with a version number like '2.11.01+ds-3- really2.10.08+ds-1', such that it will count as a higher version number than the mistaken upload of 2.11.01+ds-3 and thus replace it in package upgrades. You'd then continue with this pattern for 2.10.x updates
until the eventual proper migration of 2.11 to unstable, at which point
you can simplify the version numbering back to '2'11.x'.

I'm sure you'll agree that option B would probably be preferable.

Yes, agreed. Currently I'm trying to find out how to reflect that downgrade in my gbp style git repository.

I try to build my source package by calling "gbp buildpackage --git-upstream-tree=upstream_2.10.08+ds", where "upstream_2.10.08+ds" is a new upstream branch containing the source code for version 2.10.08. It tries to build the binary package, which fails b/c the BD's are not fulfilled. However I just need the source package. How I can prevent from running "dpkg-buildpackage -us -uc -ui -i -I", I just need "dpkg-buildpackage <snip> -S".

Have you just tried passing through -S from gbp? As in "gbp buildpackage
-S"? It might not work if you have set a different builder like schroot,
but you can just pass --git-builder=debuild or similar in that case.

Hilmar
--
Testmail

--
Loren M. Lang
[email protected]
http://www.north-winds.org/


Public Key: http://www.north-winds.org/lorenl_pubkey.asc
Fingerprint: 7896 E099 9FC7 9F6C E0ED E103 222D F356 A57A 98FA

-----BEGIN PGP SIGNATURE-----

iHUEABEIAB0WIQT3wmbBr9cpdt12HlPMe9wUn2Md1wUCZeUfXQAKCRDMe9wUn2Md 15nKAQDr3vhS+wRTRqlgSAPnV52zDRxatPDq9qa5b39AkRyHGgD/WioJBuMVh+al b5SDMk6hHESLQ2ME8siQcvw4o0RnUzY=
=mz7Q
-----END PGP SIGNATURE-----

--- SoupGate-Win32 v1.05
* Origin: fsxNet Usenet Gateway (21:1/5)

PLEASE REMOVE ME FROM ALL LISTS!

I tried to remove myself. It didn't work.

I tried to contact the list admin. I did not get an answer.

I'M GONNA SPAM YOUR LISTS UNTIL YOU REMOVE ME!



On 05.03.24 23:30, Preuße, Hilmar wrote:

On 04.03.2024 02:09, Loren M. Lang wrote:

Hi,

Have you just tried passing through -S from gbp? As in "gbp
buildpackage -S"? It might not work if you have set a different
builder like schroot, but you can just pass --git-builder=debuild or
similar in that case.

Yes, I tried that option "-S", but it did not give me a source
package. However I found the suitable command line later in gbp-buildpackage(1):

gbp buildpackage --git-upstream-tree=upstream_2.10.08+ds --git-no-create-orig  --git-export-dir=/tmp --git-builder=/bin/true --git-no-pbuilder --git-no-purge

, which gives me a source tree in /tmp, which I can feed to "dpkg-buildpackage ... -S" to get a source package. I still fiddling
with the versioning scheme I have to use, but I guess I'll figure that
out myself.

Hilmar

--- SoupGate-Win32 v1.05
* Origin: fsxNet Usenet Gateway (21:1/5)