• Keep wiki for Plasma 6 / Qt 6 upgrade information in sync

    From Hefee@21:1/5 to All on Mon Dec 30 14:33:44 2024
    Hey,

    it is great to see a lot useful information shared via this mailing list. To find all the quirks in upgrading to Plasma 6 / Qt 6.

    It would be great if all those knowledge is not only bound to this ml. Let's make sure that the wiki will be our primary knowledge pool regarding the quirks:

    https://wiki.debian.org/Plasma%206

    Btw. It is very easy to register an account to edit the page.

    Additional thx to all you already contributed to this wiki already.

    Regards,

    hefee

    -----BEGIN PGP SIGNATURE-----

    iQIzBAABCgAdFiEEOewRoCAWtykmSRoG462wCFBgVjYFAmdyoTgACgkQ462wCFBg VjbwHg//Z4avSJtGZzwWoXwiLCLI8C2Z1tjkRU+Udem3urCGWnomiCSgoZ3vLCHP XDb8jEmrvegvKmQePlmmwgsSNAyJAcMFoL52Bt3yjhjeIBUhjswlyzThqrsXihVj 56DzNYKiUNyXoDLKj/T/FP/HPn2Tt1bbgzoadoCURRds/UAE/Map9aH4XiYRSDSq 0T3X1FNZlcvhtdh0JUMDCLBX52qgZyyGqTYyPlq94iTARyLWKq0rkBgATtJwGs3O FMdotkRWdSNlHoitYZA0vuZXclWfG2/HArMhdHKkPEmLt3Jlni2bXtjtfu0NV+75 ZGDTLYpDcFNrHSZAHQPl5yE5DXnQUNKiLSVpgVCog6XRZm1hTrvwtvc4dt8U9H8V Xasw4nzSet/wzA/VZ+lgTZnX4av0R1Gft4gA/71OvvFyXXwJx2NW7xSEFzwhhtqu RP94nLQJn7fJBMh5k509b5Yf7rhaJ7kf3eBnLYlSNOeRcVQGghr6ZvqIYCJRGPfa CNA+HN2S6R8QrdRQeVHDJCBr1x7MqXMYav3adX19GAs2xYu4mXOVdCQwNCYwtupb biuSkyDHUUhsmUI7H5KA8Rci5M/wvuAZvX47QygiLhis7YZIVFO/o3gzPTF1e8tk 4pc67VXr7qERQoy40aQhO7o0X1kfFW5NMNlCtASG1JCUMhpAuEU=
    =Mxha
    -----END PGP SIGNATURE-----

    --- SoupGate-Win32 v1.05
    * Origin: fsxNet Usenet Gateway (21:1/5)
  • From Andrey Rakhmatullin@21:1/5 to Shai Berger on Tue Jan 7 13:10:01 2025
    On Tue, Jan 07, 2025 at 01:39:05PM +0200, Shai Berger wrote:
    Sharing my little "worry story" -- I used "apt upgrade" on testing (I
    never use full-upgrade)

    This is a user problem.

    --
    WBR, wRAR

    -----BEGIN PGP SIGNATURE-----

    iQJhBAABCgBLFiEEolIP6gqGcKZh3YxVM2L3AxpJkuEFAmd9F0otFIAAAAAAFQAP cGthLWFkZHJlc3NAZ251cGcub3Jnd3JhckBkZWJpYW4ub3JnAAoJEDNi9wMaSZLh IwQP/ifHOrDhJNVB/4m8CKPRUDyNOlkX0tL8b5NSVTvKdk1+jP5zj7f8zKOA6laB rWSU2zR7jO2MkxKnnybG5+aQgMEQuTnNgNAKM380jOe1jU2Y/JvKvhHif4ZOUFjd pgqLGKA+suQZFhELXetNhu8ZxOOkegIVTInUzNAJFjQWkRDJH335K+yPUYdCuZqx iCl/vsKlHTNlrfB9Q4Y0RHh3iv+J23tLgz99ttM4IEvZ2MvQjyoifHdbOq5D58JC fJ4ACbIlAwhUgkYIKQg7Y7ODZ8OQwrI8SqyHBIyZTpWq5MFuo+In9+f0giXHYnTK 7nE2RuGK22W8BXAto2IEUEeVc7VR6Va6jyylWkZn+YpcnStKsV//JjrjXtAzo+LX YWIfAvCqzpbBipplQX8FApSQdsM9yJioMlrrBh7aRydw1ZT2CIpKnWHRc2bxebFm nWD1xNCrLMcu2Ko1f3wyyUSKu78WX/9Q8DYzTRCmuJyu652GXRyB1q12lftgv4cQ bwAZMpM/CWtaMseEVsw+goXn2s8kWpwriEAyb3b7O76ifvjJoT4+vMDoy4t8olhZ KmNB6uoOBehRQ8+bqTeUjThu/kUSPwvQL+nmYBHtbs9Gn63gihB3XShwShfhecmw 4re2Xm0bNinY780p4Wo8vExqB1UxdDR3FjgoHXOE0hK+V/b9
    =SZwn
    -----END PGP SIGNATURE-----

    --- SoupGate-Win32 v1.05
    * Origin: fsxNet Usenet Gateway (21:1/5)
  • From Shai Berger@21:1/5 to Hefee on Tue Jan 7 12:50:01 2025
    Hi all,

    On Mon, 30 Dec 2024 14:33:44 +0100
    Hefee <hefee@debian.org> wrote:

    it is great to see a lot useful information shared via this mailing
    list. To find all the quirks in upgrading to Plasma 6 / Qt 6.

    It would be great if all those knowledge is not only bound to this
    ml. Let's make sure that the wiki will be our primary knowledge pool regarding the quirks:

    https://wiki.debian.org/Plasma%206


    Sharing my little "worry story" -- I used "apt upgrade" on testing (I
    never use full-upgrade) and it installed many packages, but apparently
    left many missing. But after that, "aptitude safe-upgrade" put things
    in order.

    Between the two upgrade commands, I got to a desktop with no shell,
    where even logging out doesn't work properly (although I did manage to
    run some programs by adding panels manually). I had to change to XFCE in
    order to run aptitude and fix it, as even konsole wasn't working.

    I usually use aptitude for upgrades, but in big transitions like this
    it has a tendency to choke, and then I resort to apt.

    I'm not sure if there's a general lesson in this that's fit for the
    Wiki. Maybe a list of packages to check for ("if your upgrade doesn't
    have x,y, and z then it is incomplete").

    Anyway, all seems well now.

    (I have signal-desktop installed from outside Debian, and it needed a
    manual quirk as well; does that fit there?)

    Thanks to packagers and developers for all their work, and thanks to
    members of this list for all the info,

    Shai.

    --- SoupGate-Win32 v1.05
    * Origin: fsxNet Usenet Gateway (21:1/5)
  • From Marc Haber@21:1/5 to Shai Berger on Tue Jan 7 13:50:01 2025
    On Tue, Jan 07, 2025 at 01:39:05PM +0200, Shai Berger wrote:
    Sharing my little "worry story" -- I used "apt upgrade" on testing (I
    never use full-upgrade) and it installed many packages, but apparently
    left many missing.

    And it also didnt remove many packages that needed removing for an
    orderly upgrade. That's how apt upgrade works. It is therefore my recommendation to use apt upgrade to to the part of the upgrade that is unlikely to breatk things, but then follow with apt full-upgrade to do
    actual transitions. Since, in testing and unstable, apt full-upgrade at
    the wrong time might uninstall half of your system, you need to look at
    that apt full-upgrade suggests doing before acknowledging the action. A preceding apt upgrade helps to keep apt full-upgrade's suggestions
    "short" and more easily to digest.

    During my upgrades to Plasma 6, I ended up twice with an active
    screenlocker that wouldn't unlock, and therfore had to kill the Plasma
    session and the apt run in it, followed by the usual clean up of dpkg --configure --all, apt -f install and apt upgrade. I therefore recommend
    this upgrade in an ssh session from another machine, inside screen, from
    the console or somehow else. It would be nice if we could sort that out
    before the release so that people going the non-recommended but common
    way of just running the upgrade in Konsole don't end up with having to
    recover.

    Greetings
    Marc

    -- ----------------------------------------------------------------------------- Marc Haber | "I don't trust Computers. They | Mailadresse im Header Leimen, Germany | lose things." Winona Ryder | Fon: *49 6224 1600402 Nordisch by Nature | How to make an American Quilt | Fax: *49 6224 1600421

    --- SoupGate-Win32 v1.05
    * Origin: fsxNet Usenet Gateway (21:1/5)
  • From =?ISO-8859-1?Q?Aur=E9lien_COUDERC?=@21:1/5 to All on Tue Jan 7 14:10:01 2025
    Le 7 janvier 2025 12:39:05 GMT+01:00, Shai Berger <shai@platonix.com> a écrit :
    Hi all,

    On Mon, 30 Dec 2024 14:33:44 +0100
    Hefee <hefee@debian.org> wrote:

    it is great to see a lot useful information shared via this mailing
    list. To find all the quirks in upgrading to Plasma 6 / Qt 6.

    It would be great if all those knowledge is not only bound to this
    ml. Let's make sure that the wiki will be our primary knowledge pool
    regarding the quirks:

    https://wiki.debian.org/Plasma%206


    Sharing my little "worry story" -- I used "apt upgrade" on testing (I
    never use full-upgrade) and it installed many packages, but apparently
    left many missing. But after that, "aptitude safe-upgrade" put things
    in order.

    The documented upgrade procedure has always been apt upgrade then apt full-upgrade.

    See : <https://www.debian.org/releases/stable/amd64/release-notes/ch-upgrading.en.html#minimal-upgrade>


    Happy hacking,
    --
    Aurélien

    --- SoupGate-Win32 v1.05
    * Origin: fsxNet Usenet Gateway (21:1/5)
  • From Luigi Toscano@21:1/5 to All on Tue Jan 7 19:50:01 2025
    Shai Berger ha scritto:

    Anyway, as noted, I was able to get to a working state without a full-upgrade. I checked now if `apt full-upgrade` suggests any more
    qt6/kf6 components, and there was only one (libqt6concurrent6, and that
    is not a real one either -- I just still have libqt6concurrent6t64).

    Please trust full-upgrade. In this case, please replace libqt6concurrent6t64 (which likely points to an older Qt version and it was removed from the archive) with libqt6concurrent6.


    Ciao
    --
    Luigi

    --- SoupGate-Win32 v1.05
    * Origin: fsxNet Usenet Gateway (21:1/5)
  • From Shai Berger@21:1/5 to libre@coucouf.fr on Tue Jan 7 19:40:01 2025
    Hi,

    On Tue, 07 Jan 2025 13:51:16 +0100
    Aurélien COUDERC <libre@coucouf.fr> wrote:


    The documented upgrade procedure has always been apt upgrade then apt full-upgrade.

    See : <https://www.debian.org/releases/stable/amd64/release-notes/ch-upgrading.en.html#minimal-upgrade>


    That page speaks of upgrading between stable releases of Debian. It
    makes sense to use the same procedure for a large transition in testing/unstable, but it's not obvious (at least to me).

    Anyway, as noted, I was able to get to a working state without a
    full-upgrade. I checked now if `apt full-upgrade` suggests any more
    qt6/kf6 components, and there was only one (libqt6concurrent6, and that
    is not a real one either -- I just still have libqt6concurrent6t64).

    Thanks again,
    Shai.

    --- SoupGate-Win32 v1.05
    * Origin: fsxNet Usenet Gateway (21:1/5)
  • From =?UTF-8?B?QXVyw6lsaWVu?= COUDERC@21:1/5 to All on Tue Jan 7 21:50:01 2025
    Le mardi 7 janvier 2025, 19:45:33 UTC+1 Luigi Toscano a écrit :
    Shai Berger ha scritto:

    Anyway, as noted, I was able to get to a working state without a full-upgrade. I checked now if `apt full-upgrade` suggests any more
    qt6/kf6 components, and there was only one (libqt6concurrent6, and that
    is not a real one either -- I just still have libqt6concurrent6t64).

    Please trust full-upgrade. In this case, please replace libqt6concurrent6t64 (which likely points to an older Qt version and it was removed from the archive) with libqt6concurrent6.

    Well… trust but *always* double check the list of packages to be removed. :) lib* libraries are almost always fine, other packages : for you to decide.

    You’re running something called « testing » or « unstable » for a reason. ;)


    Happy hacking,
    --
    Aurélien

    --- SoupGate-Win32 v1.05
    * Origin: fsxNet Usenet Gateway (21:1/5)