Google Groups no longer supports new Usenet posts or subscriptions. Historical content remains viewable.
Dismiss
Bug#1035535: Debian 11 -> 12: manual "apt install" needed to update some packages (vkd3d, appindicator, wx)
1 view
Skip to first unread message
Paul Gevers
Jun 4, 2023, 5:30:05 AM6/4/23
to
reassign
Hi,
First of all, thanks for reporting issues you experience and sorry it
took a while to reply.
On 05-05-2023 04:27, kolA...@kolahilft.de wrote:
> But "apt dist-upgrade" didn't upgrade some packages.
Did you follow the upgrade procedure as outlined in the release notes,
or is $(apt dist-upgrade) all you ran? It has happened before that apt
can't figure out an upgrade path in one go, but when ran twice it does
(the bullseye release notes had something on a particular known problem
IIRC).
> So I had to do it
> manually. Should it be that way?
Ideally not, no.
> apt install \
> vkd3d-compiler/bookworm \
> libvkd3d-dev/bookworm \
> libvkd3d-dev:i386/bookworm \
> libappindicator1/bookworm
>
> By this the vkd3d packages where upgraded to bookworm and
> libappindicator1 was replaced with libayatana-appindicator1 and
> libayatana-indicator7.
Hmm.
> I also had wx3.0-headers installed.
> And I had to install the new +version manually.
>
> apt install wx3.2-headers
>
>
> Maybe related:
> My "apt dist-upgrade" from Debian 11 to 12 ended with an error.
> See here:
> https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=994081#32
Was this before or after the issue you pointed out above? I assume apt
already told you before this error it wouldn't upgrade everything,
right? Did you retry running $(apt dist-upgrade) again after this error?
Paul
Hi,
First of all, thanks for reporting issues you experience and sorry it
took a while to reply.
On 05-05-2023 04:27, kolA...@kolahilft.de wrote:
> But "apt dist-upgrade" didn't upgrade some packages.
Did you follow the upgrade procedure as outlined in the release notes,
or is $(apt dist-upgrade) all you ran? It has happened before that apt
can't figure out an upgrade path in one go, but when ran twice it does
(the bullseye release notes had something on a particular known problem
IIRC).
> So I had to do it
> manually. Should it be that way?
Ideally not, no.
> apt install \
> vkd3d-compiler/bookworm \
> libvkd3d-dev/bookworm \
> libvkd3d-dev:i386/bookworm \
> libappindicator1/bookworm
>
> By this the vkd3d packages where upgraded to bookworm and
> libappindicator1 was replaced with libayatana-appindicator1 and
> libayatana-indicator7.
Hmm.
> I also had wx3.0-headers installed.
> And I had to install the new +version manually.
>
> apt install wx3.2-headers
>
>
> Maybe related:
> My "apt dist-upgrade" from Debian 11 to 12 ended with an error.
> See here:
> https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=994081#32
Was this before or after the issue you pointed out above? I assume apt
already told you before this error it wouldn't upgrade everything,
right? Did you retry running $(apt dist-upgrade) again after this error?
Paul
Paul Gevers
Jun 16, 2023, 4:40:06 PM6/16/23
to
Control: reassign -1 src:wxwidgets3.2
Hi,
On 16-06-2023 22:11, kolA...@kolahilft.de wrote:
> I tried to reproduce the problems with:
> https://cloud.debian.org/images/cloud/bullseye/20230601-1398/debian-11-nocloud-amd64-20230601-1398.qcow2
>
>
> Looks like libappindicator1 may has been a leftover from Debian-10.
> -> my fault
>
> And the vkd3d problem seems to be caused by the vkd3d-compiler package
> from the WineHQ apt repo.
> https://wiki.winehq.org/Debian
> -> probably a fault of the WineHQ repo
>
> Only problem left is wx3.0-headers not being upgraded to wx3.2-headers.
> As said, I tested using the debian-11-nocloud-amd64-20230601-1398.qcow2
> image. Just these steps:
> apt install wx3.0-headers
> # update /etc/apt/sources.list
> apt clean
> apt update
> apt full-upgrade
> And wx3.0-headers/oldstable is still installed.
> Running apt full-upgrade again doesn't upgrade the package either.
If nothing depends on the headers, I'm not surprised. wx3.0-headers has
nothing in the archive providing it, so it's OK that it stays if nothing
conflicts with it; see section 4.8 [1] in the release notes how to
remove obsolete packages.
Although I now somehow doubt that there's anything wrong, I like the
maintainers of wxwidgets3.2 to double check (hence reassigning). The bug
can be closed if this is intended behavior.
Paul
[1]
https://www.debian.org/releases/bookworm/amd64/release-notes/ch-upgrading.en.html#obsolete
Hi,
On 16-06-2023 22:11, kolA...@kolahilft.de wrote:
> I tried to reproduce the problems with:
> https://cloud.debian.org/images/cloud/bullseye/20230601-1398/debian-11-nocloud-amd64-20230601-1398.qcow2
>
>
> Looks like libappindicator1 may has been a leftover from Debian-10.
> -> my fault
>
> And the vkd3d problem seems to be caused by the vkd3d-compiler package
> from the WineHQ apt repo.
> https://wiki.winehq.org/Debian
> -> probably a fault of the WineHQ repo
>
> Only problem left is wx3.0-headers not being upgraded to wx3.2-headers.
> As said, I tested using the debian-11-nocloud-amd64-20230601-1398.qcow2
> image. Just these steps:
> apt install wx3.0-headers
> # update /etc/apt/sources.list
> apt clean
> apt update
> apt full-upgrade
> And wx3.0-headers/oldstable is still installed.
> Running apt full-upgrade again doesn't upgrade the package either.
If nothing depends on the headers, I'm not surprised. wx3.0-headers has
nothing in the archive providing it, so it's OK that it stays if nothing
conflicts with it; see section 4.8 [1] in the release notes how to
remove obsolete packages.
Although I now somehow doubt that there's anything wrong, I like the
maintainers of wxwidgets3.2 to double check (hence reassigning). The bug
can be closed if this is intended behavior.
Paul
[1]
https://www.debian.org/releases/bookworm/amd64/release-notes/ch-upgrading.en.html#obsolete
0 new messages