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.
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.
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".
Hilmar
--
Testmail
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
Sysop: | Keyop |
---|---|
Location: | Huddersfield, West Yorkshire, UK |
Users: | 307 |
Nodes: | 16 (2 / 14) |
Uptime: | 38:00:18 |
Calls: | 6,910 |
Files: | 12,376 |
Messages: | 5,428,827 |