Re: console-setup_1.247_source.changes ACCEPTED into unstable

2026-04-16 Thread Holger Wansing
Hi,

Samuel Thibault  wrote (Wed, 15 Apr 2026 23:08:42 +0200):
> Holger Wansing, le mer. 15 avril 2026 22:57:05 +0200, a ecrit:
> > Holger Wansing  wrote (Wed, 01 Apr 2026 06:21:19 
> > +0200):
> > > Maybe it's enough to automatically generate a changelog entry, saying 
> > > 
> > > [Updated translations]
> > > *** Before uploading, please add data from
> > >  here!!! ***
> > 
> > I have changings tested in l10n-sync script, which adds such entries to
> > d/changelog now.
> > 
> > Resulting commits can be seen at
> > https://salsa.debian.org/installer-team/user-setup/-/commit/cd7ff65b63e82991182ff7f0f3a304fc5ce18f18
> > or
> > https://salsa.debian.org/installer-team/systemd-boot-installer/-/commit/dd713afc19c2fd2d02e847d8d60f1575f31cd78b
> > 
> > Any objections against this proposal?
> 
> 
> It's very welcome on my side, thanks!!

Just pushed to git.


Holger


-- 
Holger Wansing 
PGP-Fingerprint: 496A C6E8 1442 4B34 8508  3529 59F1 87CA 156E B076



Re: console-setup_1.247_source.changes ACCEPTED into unstable

2026-04-15 Thread Samuel Thibault
Holger Wansing, le mer. 15 avril 2026 22:57:05 +0200, a ecrit:
> Holger Wansing  wrote (Wed, 01 Apr 2026 06:21:19 +0200):
> > Maybe it's enough to automatically generate a changelog entry, saying 
> > 
> > [Updated translations]
> > *** Before uploading, please add data from
> >  here!!! ***
> 
> I have changings tested in l10n-sync script, which adds such entries to
> d/changelog now.
> 
> Resulting commits can be seen at
> https://salsa.debian.org/installer-team/user-setup/-/commit/cd7ff65b63e82991182ff7f0f3a304fc5ce18f18
> or
> https://salsa.debian.org/installer-team/systemd-boot-installer/-/commit/dd713afc19c2fd2d02e847d8d60f1575f31cd78b
> 
> Any objections against this proposal?


It's very welcome on my side, thanks!!

Samuel



Re: console-setup_1.247_source.changes ACCEPTED into unstable

2026-04-15 Thread Holger Wansing
Hi,

Holger Wansing  wrote (Wed, 01 Apr 2026 06:21:19 +0200):
> Maybe it's enough to automatically generate a changelog entry, saying 
> 
> [Updated translations]
> *** Before uploading, please add data from
>  here!!! ***

I have changings tested in l10n-sync script, which adds such entries to
d/changelog now.

Resulting commits can be seen at
https://salsa.debian.org/installer-team/user-setup/-/commit/cd7ff65b63e82991182ff7f0f3a304fc5ce18f18
or
https://salsa.debian.org/installer-team/systemd-boot-installer/-/commit/dd713afc19c2fd2d02e847d8d60f1575f31cd78b

Any objections against this proposal?


Holger




-- 
Holger Wansing 
PGP-Fingerprint: 496A C6E8 1442 4B34 8508  3529 59F1 87CA 156E B076



Re: console-setup_1.247_source.changes ACCEPTED into unstable

2026-03-31 Thread Holger Wansing
Hi Samuel,

Am 30. März 2026 22:16:15 MESZ schrieb Samuel Thibault :
>> The changelog for this upload seems to miss several entries for translation 
>> updates.
>
>Ah, I missed that indeed. Should the l10n-sync script perhaps
>automatically add the entry? I don't actually know how to get the
>authors of the changes.

There are some scripts at

which generate this file:


I think it's not trivial to generate those data within the l10n-sync script.
Maybe it's enough to automatically generate a changelog entry, saying 

[Updated translations]
*** Before uploading, please add data from
 here!!! ***

???


>> Moreover, the format of the tag is different from what we used before 
>> ("debian/1.247" vs. "1.247").
>
>Oh, I didn't realize that tag2upload wouldn't use the usual tag format.
>Perhaps there is a way to teach it, like we did for gbp.
>
>> Are there any drawbacks with this format change?
>
>We already have quite a few of those, so it's not a problem per se.
>
>> What's the plan for the future regarding tag format in d-i team?

At least we get warnings several times a day saying 
"warning: tag '1.247' is externally known as 'debian/1.247' "


Holger


-- 
Sent from /e/ OS on Fairphone3



Re: console-setup_1.247_source.changes ACCEPTED into unstable

2026-03-30 Thread Samuel Thibault
Holger Wansing, le lun. 30 mars 2026 22:06:44 +0200, a ecrit:
> Am 30. März 2026 21:48:38 MESZ schrieb Debian FTP Masters 
> :
> >-BEGIN PGP SIGNED MESSAGE-
> >Hash: SHA512
> >
> >Format: 1.8
> >Date: Mon, 30 Mar 2026 21:30:08 +0200
> >Source: console-setup
> >Architecture: source
> >Version: 1.247
> >Distribution: unstable
> >Urgency: medium
> >Maintainer: Debian Install System Team 
> >Changed-By: Samuel Thibault 
> >Changes:
> > console-setup (1.247) unstable; urgency=medium
> > .
> >   * Rebuild against xkb-data 2.47-1.
> 
> The changelog for this upload seems to miss several entries for translation 
> updates.

Ah, I missed that indeed. Should the l10n-sync script perhaps
automatically add the entry? I don't actually know how to get the
authors of the changes.

> Moreover, the format of the tag is different from what we used before 
> ("debian/1.247" vs. "1.247").

Oh, I didn't realize that tag2upload wouldn't use the usual tag format.
Perhaps there is a way to teach it, like we did for gbp.

> Are there any drawbacks with this format change?

We already have quite a few of those, so it's not a problem per se.

> What's the plan for the future regarding tag format in d-i team?

Samuel



Re: console-setup_1.247_source.changes ACCEPTED into unstable

2026-03-30 Thread Holger Wansing
Hi Samuel,

Am 30. März 2026 21:48:38 MESZ schrieb Debian FTP Masters 
:
>Thank you for your contribution to Debian.
>
>
>
>Accepted:
>
>-BEGIN PGP SIGNED MESSAGE-
>Hash: SHA512
>
>Format: 1.8
>Date: Mon, 30 Mar 2026 21:30:08 +0200
>Source: console-setup
>Architecture: source
>Version: 1.247
>Distribution: unstable
>Urgency: medium
>Maintainer: Debian Install System Team 
>Changed-By: Samuel Thibault 
>Changes:
> console-setup (1.247) unstable; urgency=medium
> .
>   * Rebuild against xkb-data 2.47-1.

The changelog for this upload seems to miss several entries for translation 
updates.

Maybe this is because of the use of tag2upload or not, don't know.

Moreover, the format of the tag is different from what we used before 
("debian/1.247" vs. "1.247").
Are there any drawbacks with this format change?
What's the plan for the future regarding tag format in d-i team?


Holger




-- 
Sent from /e/ OS on Fairphone3