Dear Maintainer,

The login logo still points to:
/usr/share/images/vendor-logos/logo-text-version-64.png
which is "debian 12".

That file is owned by the "desktop-base" package.

The login logo should not be "debian 12" any more, it should be only "debian".

A quick workaround would be to point the logo to:
/usr/share/images/vendor-logos/logo-64.png
which is only the Debian logo without text nor version.

Best,
Amr

Please file a bug against desktop-base instead.

Thank you,
Jeremy Bícha

Control: reassign -1 desktop-base 13.0.0~pre1
Control: retitle -1 desktop-base: logo-text-version* should not include major version number in testing/unstable
Control: tags -1 + trixie sid

There's no need to file a separate bug, we can reassign this one.

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.

(I removed similar version numbering from background images as part of
13.0.0~pre1.)

    smcv

Control: tags -1 + patch

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. I've proposed a merge request at
<https://salsa.debian.org/debian-desktop-team/desktop-base/-/merge_requests/8>
which implements that.

Unfortunately, logo-text.svg is currently rendered as blank (transparent)
by librsvg (and therefore rsvg-convert), so the logo-text-${size}.png
shipped by desktop-base are also blank. I opened a separate librsvg bug
(#1086987). I was able to work around this by copying the content of
logo-text-version.svg and then deleting the version number, and that change
is also included in the MR linked above.

    smcv

Control: tags -1 = forky sid

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