Devuan bug report logs - #116
d1h stage fails on versions with an epoch

Reply or subscribe to this bug.

Toggle useless messages

Message #5 received at submit@bugs.devuan.org (full text, mbox, reply):

Package: d1h
Version: 0.2+4
Severity: normal


[~]$ d1h stage 2:4.5.8+dfsg-2+devuan1

[suites/ascii-proposed 4973c1aaf4] staging version 2:4.5.8+dfsg-2+devuan1
 1 file changed, 6 insertions(+)
fatal: '2:4.5.8+dfsg-2+devuan1' is not a valid tag name.


-- System Information:

Architecture: x86_64

Kernel: Linux 4.12.0+ (SMP w/6 CPU cores)
Locale: LANG=C, LC_CTYPE=C (charmap=ANSI_X3.4-1968)
Shell: /bin/sh linked to /bin/dash
Init: sysvinit (via /sbin/init)

Message #10 received at 116@bugs.devuan.org (full text, mbox, reply):

[Message part 1 (text/plain, inline)]

Hi Adam,

it seems more a git issue (git doesn't seem to like colons in tag
names). I might easily let d1h replace colons with "_" in tag names,
and issue a warnung, but we must be sure that we like this in general.

[signature.asc (application/pgp-signature, inline)]

Message #15 received at 116@bugs.devuan.org (full text, mbox, reply):

[Message part 1 (text/plain, inline)]

The problem is that git cannot create tags which contain ":". To make
my point more cleas: what we could do is to replace the ":" with a "_"
in the git tag, not in debian/changelog. So a command like:

  $ d1h stage 2:1.3.27+devuan1.7

would create a regular entry in debian/changelog with version number

  2:1.3.27+devuan1.7

but the associated git tag would be called

  2_1.3.27+devuan1.7

The only other option I see is to forget the epoch number in the git
tag (again, only in the git tag, not in debian/changelog).

To be honest, I would actually prefer the second solution (i.e.,
dropping the epoch in the git tag).

HND

KatolaZ

[signature.asc (application/pgp-signature, inline)]

Message #20 received at 116@bugs.devuan.org (full text, mbox, reply):

> From: KatolaZ <katolaz@freaknet.org>
> To: 116@bugs.devuan.org
> Subject: maybe git issue?

Note: the Debian BTS does not notify anyone but the maintainer for mails
received at 1234@bugs.d.o; you want 1234-submitter@bugs.d.o for this.

Yeah, I also used to make this mistake most of the time, and even now
occasionally make it as well.  I guess it'd be much better to default to
what most other bug trackers do, and mail the maintainer, uploaders and
everyone who commented on the bug in question.

But that's a separate issue.

> Hi Adam,
>
> it seems more a git issue (git doesn't seem to like colons in tag
> names). I might easily let d1h replace colons with "_" in tag names,
> and issue a warnung, but we must be sure that we like this in general.

I see that whatever workload the Samba repository uses (perhaps gbp which I
hate with a passion) uses bare '%' for colons.  Not URLish "%3A" but just
"%":

[~/pkg/samba](suites/ascii-proposed)$ git tag
debian/1%3.0.28a-2
debian/1%3.0.28a-3
debian/1%3.0.29-1
debian/1%3.0.30-1
debian/1%3.2.0_pre2-2
debian/1%3.2.0_rc1-1
debian/2%3.0.30-2
debian/2%3.0.30-3
[...]
upstream/3.0.24
upstream/3.0.27a
upstream/3.0.28
upstream/3.0.28a
upstream/3.0.29
[...]

-- 
⢀⣴⠾⠻⢶⣦⠀ 
⣾⠁⢠⠒⠀⣿⡁ A dumb species has no way to open a tuna can.
⢿⡄⠘⠷⠚⠋⠀ A smart species invents a can opener.
⠈⠳⣄⠀⠀⠀⠀ A master species delegates.

Message #25 received at 116@bugs.devuan.org (full text, mbox, reply):

[Message part 1 (text/plain, inline)]

On Sat, Jul 15, 2017 at 11:38:58PM +0200, Adam Borowski wrote:

[cut]

> 
> Note: the Debian BTS does not notify anyone but the maintainer for mails
> received at 1234@bugs.d.o; you want 1234-submitter@bugs.d.o for this.
>

Sorry! This should probably be better :)

[cut]

> 
> I see that whatever workload the Samba repository uses (perhaps gbp which I
> hate with a passion) uses bare '%' for colons.  Not URLish "%3A" but just
> "%":
> 
> [~/pkg/samba](suites/ascii-proposed)$ git tag
> debian/1%3.0.28a-2
> debian/1%3.0.28a-3
> debian/1%3.0.29-1

[cut]

Yes, using '%' seems a reasonable choice. I will implement this in the
upcoming new version of d1h.

HND

KatolaZ

[signature.asc (application/pgp-signature, inline)]

Message #32 received at 116-close@bugs.devuan.org (full text, mbox, reply):

close


fsr

Send a report that this bug log contains spam.