Bug#1086954: desktop-base: logo-text-version* should not include major version number in testing/unstable
Simon McVittie <[email protected]> Sun, 11 May 2025 10:56:19 +0100
| Newsgroups | gmane.linux.debian.devel.desktop |
|---|---|
| Message-ID | <aCB0Q0BHMHeu-K4Z__23860.3721418016$1746957446$gmane$org@remnant.pseudorandom.co.uk> |
Control: tags -1 = forky sid
On Thu, 07 Nov 2024 at 18:13:40 +0000, Simon McVittie wrote:
>On Thu, 07 Nov 2024 at 16:08:44 +0000, Simon McVittie wrote:
>> All logos matching
>> /usr/share/desktop-base/debian-logos/logo-text-version*
>> currently contain a "12" left over from the Debian 12 release. I think
>> they should have no specific version number for most of the
>> testing/unstable release cycle, gain a version number around the time of
>> the Debian 13 freeze, and then lose their version number again shortly
>> after the Debian 13 release.
>
>A simple way to implement that would be to make logo-text-version* into
>symlinks to logo-text* during the development cycle, and undo that around
>the time of the freeze.
Now that we're in the Debian 13 freeze, the logo-text-version* files
correctly contain a "13", so there is no appropriate action to be taken
on this until the forky development cycle opens. Removing patch and
trixie tags accordingly.
I've opened a draft MR
https://salsa.debian.org/debian-desktop-team/desktop-base/-/merge_requests/10
with a change that I think would be a good approach to this at the
beginning of the forky cycle.
smcv