Re: [X1 Tablet] Careful with dist-upgrade in unstable at the moment
On Thursday, 22 December 2022 09:16:50 CET Martin Steigerwald wrote: > I made an interesting experience regarding the current Qt transition: I > updated a ThinkPad X1 Gen 1 Tablet with "apt upgrade" yesterday. Did you manage to have your tablet fully functional in keyboard free mode? I've experimented with an old Portege Tablet and many applications couldn't be used without a keyboard or a mouse. I want to use the tablet as a reader and Okular couldn't be used without "mouse right click" or "keyboard control keys" which Maliit doesn't (didn't) have. Example: you can go to full screen mode but you can't leave it, because it would require a right click which I couldn't manage neither by touch nor by stylus. On the hardware side, everything was fully functional with pure Wayland install. I use GDM3 instead of SDDM because the latter still rely on X11/Xorg, when GDM3 can do without. Touch screen and stylus (plain Wacom) fully functional. But the applications were not ready to be used with tablet mode, specially Maliit, imo, which is fine to insert text but doesn't do keyboard shortcuts at all, which could atone for absence or right click. Touchscreen longpress-is- rightclick is on a per application basis, so you (did) have it with Dolphin, but not with Okular. Same goes for stylus button configuration. It was a few month ago so I'd be happy to hear how you solved it or if you stick with the physical keyboard. Note, integrated Firefox pdf reader, and FF generally, was what was best tuned for pure tablet mode use, but it was both not very stable at the time, and it was killing my fanless "Y"-series i5. I've tried Phosh: couldn't insert my password. Gnome: no better. Actually I did find some (old) extension of some Gnome keyboard that did provide control keys, but maybe it was not working with all applications, and also it was getting all Rube Goldberg, so I gave it back to the cupboard. But I'm still interested in an open source e-reader working with plain device as the portege, and I don't want to use outdated technologies like X11/Xorg, unmaintained for years when Wayland is doing great. Cheers, Chris > Ciao, >
Re: Careful with dist-upgrade in unstable at the moment
thanks to all!!! an "apt update -t sid" on my pc upgraded it to below: Operating System: Debian GNU/Linux KDE Plasma Version: 5.26.4 KDE Frameworks Version: 5.101.0 Qt Version: 5.15.7 Kernel Version: 6.1.0-0-amd64 (64-bit) Graphics Platform: X11 Processors: 4 × Intel® Core™ i5-4200U CPU @ 1.60GHz Memory: 7.2 GiB of RAM Graphics Processor: Mesa Intel® HD Graphics 4400 Manufacturer: Hewlett-Packard Product Name: HP ProBook 430 G1 System Version: A3009CD20303 Op do 22 dec. 2022 om 16:51 schreef Diederik de Haas : > On Thursday, 22 December 2022 14:31:38 CET Martin Steigerwald wrote: > > > On Wednesday, 21 December 2022 11:42:17 CET Diederik de Haas wrote: > > > > I think they above quoted script is absolutely horrific. > > > > > > I made that statement for 2 reasons: > > > 1) It tries do a dist-upgrade 'at all cost' (imo ofc) > > > 2) `dpkg --set-selection` completely messes up APT's 'database' wrt > > > manually and automatically installed packages ... which in turn > > > causes the need to full-/dist-upgrade. > > > > I made no statement at all about this script. So in case you were > > assuming that I somehow intended to justify it, > > That was not my intention. Sorry if I made it appear that way. > If I want to address an issue to someone personally, I'd put that person > in > the To: field, like I have done now. > > If I want to address the 'general public', I sent it to the list. > > The `dpkg --set-selection` command imo 'messes up' the packages state as > it > they all get marked as manually installed and therefor it was for me > related > to what I said above that in my previous mail. > -- Luc Castermans mailto:luc.casterm...@gmail.com
Re: Careful with dist-upgrade in unstable at the moment
On Thursday, 22 December 2022 14:31:38 CET Martin Steigerwald wrote: > > On Wednesday, 21 December 2022 11:42:17 CET Diederik de Haas wrote: > > > I think they above quoted script is absolutely horrific. > > > > I made that statement for 2 reasons: > > 1) It tries do a dist-upgrade 'at all cost' (imo ofc) > > 2) `dpkg --set-selection` completely messes up APT's 'database' wrt > > manually and automatically installed packages ... which in turn > > causes the need to full-/dist-upgrade. > > I made no statement at all about this script. So in case you were > assuming that I somehow intended to justify it, That was not my intention. Sorry if I made it appear that way. If I want to address an issue to someone personally, I'd put that person in the To: field, like I have done now. If I want to address the 'general public', I sent it to the list. The `dpkg --set-selection` command imo 'messes up' the packages state as it they all get marked as manually installed and therefor it was for me related to what I said above that in my previous mail. signature.asc Description: This is a digitally signed message part.
Re: Careful with dist-upgrade in unstable at the moment
On Thu, Dec 22, 2022 at 3:52 PM Sedat Dilek wrote: > I will wait for the APT updates normally published at 2:00 p.m. UTC > and decide - should arrive at 16:00 German local-time. > KInfoCenter says: Operating System: Debian GNU/Linux unstable KDE Plasma Version: 5.26.4 KDE Frameworks Version: 5.101.0 Qt Version: 5.15.7 Kernel Version: 6.0.0-6-amd64 (64-bit) Graphics Platform: Wayland -Sedat-
Re: Careful with dist-upgrade in unstable at the moment
On Thu, Dec 22, 2022 at 11:49 AM Martin Steigerwald wrote: > > Sedat Dilek - 22.12.22, 11:10:47 CET: > […] > > Can you boot into KDE version 5.26.4 with QT version 5.15.7 packages > > upgraded as of today? > > > > Do the KDE applications work as (you) expected? > > With "All fine there as well" I meant exactly that. > > I did not do much on the tablet. But I am working with my main laptop > just as usual and did not see any issues so far. > > This is no guarantee whether it works all fine for your set of packages > and your use case, but for mine it does so far. > I played with... root# dpkg --get-selections | grep hold [ EMPTY ] 1011 2022-12-22 15:35:46 RELEASE="unstable" ; LC_ALL=C apt upgrade -V -t $RELEASE 1012 2022-12-22 15:40:10 RELEASE="unstable" ; LC_ALL=C apt full-upgrade -V -t $RELEASE 1013 2022-12-22 15:40:20 RELEASE="unstable" ; LC_ALL=C apt-get upgrade -V -t $RELEASE 1014 2022-12-22 15:40:31 RELEASE="unstable" ; LC_ALL=C apt-get dist-upgrade -V -t $RELEASE ...all resulted in: [...] 146 upgraded, 0 newly installed, 0 to remove and 0 not upgraded. Need to get 110 MB/110 MB of archives. After this operation, 23.6 kB disk space will be freed. Do you want to continue? [Y/n] n Abort. No removal of installed KDE packages listed. I will wait for the APT updates normally published at 2:00 p.m. UTC and decide - should arrive at 16:00 German local-time. If something explodes I can jump to GNOME v43 Wayland... -Sedat- P.S.: INFO: In my APT config I have pinned (buildd-)unstable and (buildd-)experimental packages to 99.
Re: Careful with dist-upgrade in unstable at the moment
On Thu, Dec 22, 2022 at 03:32:38PM +0100, Sedat Dilek wrote: > BTW, I learned a lot by breaking my Debian-system :-). Absolutely. That's when one learns best. Just don't do it when you need the box, know how to fix it, and have backups. 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
Re: Careful with dist-upgrade in unstable at the moment
On Wed, Dec 21, 2022 at 12:01 PM Marc Haber wrote: [ ... ] > It's called unstable for a reason, it's supposed to be broken once in a > while. Exactly Marc. The transition period is sometimes hard to suffer and in the end you have to... accept + wait. BTW, I learned a lot by breaking my Debian-system :-). -Sedat-
Re: Careful with dist-upgrade in unstable at the moment
Diederik de Haas - 22.12.22, 13:26:47 CET: > On Thursday, 22 December 2022 09:16:50 CET Martin Steigerwald wrote: > > > I find it way easier to have apt reduce the problem riskless > > > first. > > > It's a shorter list of actions to review. > > > > Good argument. My argument is that in the usual situation trying > > "apt > > full-upgrade" first will save me one command. With "apt upgrade" I > > often enough would have to use "apt full-upgrade" afterwards. > > IMO that indicates that the 'state' of your packages could be > improved. I *rarely* have to do a full-upgrade to get things fully > upgraded. And when not all packages get upgraded, that usually means > something 'special' is going on, like now with the Qt transition. Well, I still thought about the "apt-get upgrade" scenario even though I use "apt upgrade" meanwhile. Often enough there are new packages to install. I did not really test how often I would have to use "apt full- upgrade" instead of "apt upgrade". It might be considerably less often due to apt installing new packages automatically. > On Wednesday, 21 December 2022 11:42:17 CET Diederik de Haas wrote: > > I think they above quoted script is absolutely horrific. > > I made that statement for 2 reasons: > 1) It tries do a dist-upgrade 'at all cost' (imo ofc) > 2) `dpkg --set-selection` completely messes up APT's 'database' wrt > manually and automatically installed packages ... which in turn > causes the need to full-/dist-upgrade. I made no statement at all about this script. So in case you were assuming that I somehow intended to justify it, I was not. Actually I did not even carefully read through it to see what it does. My statement was just about "upgrade" versus "full-upgrade". Best, -- Martin
Re: Careful with dist-upgrade in unstable at the moment
On Thursday, 22 December 2022 09:16:50 CET Martin Steigerwald wrote: > > I find it way easier to have apt reduce the problem riskless first. > > It's a shorter list of actions to review. > > Good argument. My argument is that in the usual situation trying "apt > full-upgrade" first will save me one command. With "apt upgrade" I often > enough would have to use "apt full-upgrade" afterwards. IMO that indicates that the 'state' of your packages could be improved. I *rarely* have to do a full-upgrade to get things fully upgraded. And when not all packages get upgraded, that usually means something 'special' is going on, like now with the Qt transition. On Wednesday, 21 December 2022 11:42:17 CET Diederik de Haas wrote: > I think they above quoted script is absolutely horrific. I made that statement for 2 reasons: 1) It tries do a dist-upgrade 'at all cost' (imo ofc) 2) `dpkg --set-selection` completely messes up APT's 'database' wrt manually and automatically installed packages ... which in turn causes the need to full-/dist-upgrade. Run the following command and mark as automatically installed all those you don't need to have marked as manually installed: $ aptitude search '?narrow(~i!~M~n^lib,!~essential!~prequired)' That command finds all packages which are marked as manually installed, have a name which starts with 'lib' and are not of priority essential or required. HTH signature.asc Description: This is a digitally signed message part.
Re: Careful with dist-upgrade in unstable at the moment
Martin Steigerwald - 22.12.22, 11:48:59 CET: > I did not do much on the tablet. But I am working with my main laptop > just as usual and did not see any issues so far. And for what I did on the tablet: no issues. Systray, KRunner fully available again. -- Martin
Re: Careful with dist-upgrade in unstable at the moment
Sedat Dilek - 22.12.22, 11:10:47 CET: > On Thu, Dec 22, 2022 at 10:53 AM Martin Steigerwald wrote: > > Martin Steigerwald - 22.12.22, 09:16:50 CET: […] > > > So I will just wait until a "full-upgrade" can run through fully > > > on this tablet and probably stay away from a "upgrade" on my > > > laptop as well for a few days. However I used "apt upgrade" to > > > upgrade my > > > > Well, which was possible today already. All issues I found are fixed > > by today's update. > > > > I also fully upgraded on my main laptop. All fine there as well. […] > Can you boot into KDE version 5.26.4 with QT version 5.15.7 packages > upgraded as of today? > > Do the KDE applications work as (you) expected? With "All fine there as well" I meant exactly that. I did not do much on the tablet. But I am working with my main laptop just as usual and did not see any issues so far. This is no guarantee whether it works all fine for your set of packages and your use case, but for mine it does so far. Thanks to the Qt/KDE package maintainers for the update!!! Best, -- Martin
Re: Careful with dist-upgrade in unstable at the moment
On Wed, Dec 21, 2022 at 11:10 PM Aurélien COUDERC wrote: > > Hi all, > > Le mercredi 21 décembre 2022, 21:37:45 CET Marc Haber a écrit : > > On Wed, Dec 21, 2022 at 12:50:45PM +0100, Martin Steigerwald wrote: > > > Marc Haber - 21.12.22, 12:00:39 CET: > > > > > Stop using *dist-*upgrade by DEFAULT. > > > > > > > > *AMEN* to that. > > > > > > I usually do "dist-upgrade", but then look carefully what it is about to > > > do. If I don't like that, I only to "upgrade". > > > > > > Of course one can argue it is safer to do it the other way around. > > > > P.S. dist-upgrade is as deprecated as it could be, it's not even in the > > man page any more > > That can be correct or incorrect depending on which manpage you’re looking > at. :) > dist-upgrade is an argument for apt-get while full-upgrade is for apt. > > I’d like to recommend using « apt upgrade » which has a slightly different > behaviour than apt-get : it will upgrade already installed packages but also > install new packages where necessary (which apt-get upgrade won’t do). > > This will leave full-upgrade with less things to do and for me to review. The > only remaining packages should have a note in their changelog about doing a > split, replacing another package or adding a Breaks/Replace condition. I > regularly check this when I see non obvious removals (and by obvious I really > only mean libfooN+1 replacing libfooN). > Hi Aurlien, In 2017 I told my co-worker that I will continue to use apt-get which I still do. IIRC these days the Debian upgrade manuals announced the usage of apt. It is a sort of satisfaction to read that apt behaves (in certain scenarios) differently. Yes, the man-page of apt-get lists "dist-upgrade". I remember the discussion about apt(-get) VS. aptitude in Debian and sidux forums. But that was 15 years ago. So, apps might change like time did. Thanks. Regards, -Sedat-
Re: Careful with dist-upgrade in unstable at the moment
On Thu, Dec 22, 2022 at 10:53 AM Martin Steigerwald wrote: > > Martin Steigerwald - 22.12.22, 09:16:50 CET: > > I made an interesting experience regarding the current Qt transition: > > I updated a ThinkPad X1 Gen 1 Tablet with "apt upgrade" yesterday. > > > > Parts of the Plasma desktop are still broken. Some part of systray > > misses some QML files, KRunner shows up as an empty pane without > > anything, the lock screen is not usable and several other issues. So > > it can still happen with just "apt upgrade" that you have an only > > partly usable system afterwards. Of course I'd argue that this is an > > issue with missing versioned dependencies. However it appears to me > > that it is quite different to completely get this right with a > > software stack of this complexity. > > > > So I will just wait until a "full-upgrade" can run through fully on > > this tablet and probably stay away from a "upgrade" on my laptop as > > well for a few days. However I used "apt upgrade" to upgrade my > > Well, which was possible today already. All issues I found are fixed by > today's update. > > I also fully upgraded on my main laptop. All fine there as well. > > So at least for the sets of packages I use, the update goes through > smoothly now. According to > > https://release.debian.org/transitions/html/qtbase-abi-5-15-7.html > > almost all packages are built for AMD64 already. > > > laptop earlier on the same day and have seen no such updates. The > > tablet has not been updated for a longer time, but that should not > > really make much of a difference. > > And that might have made *the* difference. Some KF5 related packages were > still at 5.90 on this tablet after the "apt upgrade" yesterday. Of > course these were more current version on my main laptop. > Hi Martin, I can confirm I see no REMOVALS of KF/KP/KG packages when I simulate an (dist-)upgrade. Can you boot into KDE version 5.26.4 with QT version 5.15.7 packages upgraded as of today? Do the KDE applications work as (you) expected? Thanks Regards, -Sedat- P.S.: I checked myself with apt VS. apt-get (upgrade and full-upgrade VS. dist-upgrade).
Re: Careful with dist-upgrade in unstable at the moment
Martin Steigerwald - 22.12.22, 09:16:50 CET: > I made an interesting experience regarding the current Qt transition: > I updated a ThinkPad X1 Gen 1 Tablet with "apt upgrade" yesterday. > > Parts of the Plasma desktop are still broken. Some part of systray > misses some QML files, KRunner shows up as an empty pane without > anything, the lock screen is not usable and several other issues. So > it can still happen with just "apt upgrade" that you have an only > partly usable system afterwards. Of course I'd argue that this is an > issue with missing versioned dependencies. However it appears to me > that it is quite different to completely get this right with a > software stack of this complexity. > > So I will just wait until a "full-upgrade" can run through fully on > this tablet and probably stay away from a "upgrade" on my laptop as > well for a few days. However I used "apt upgrade" to upgrade my Well, which was possible today already. All issues I found are fixed by today's update. I also fully upgraded on my main laptop. All fine there as well. So at least for the sets of packages I use, the update goes through smoothly now. According to https://release.debian.org/transitions/html/qtbase-abi-5-15-7.html almost all packages are built for AMD64 already. > laptop earlier on the same day and have seen no such updates. The > tablet has not been updated for a longer time, but that should not > really make much of a difference. And that might have made *the* difference. Some KF5 related packages were still at 5.90 on this tablet after the "apt upgrade" yesterday. Of course these were more current version on my main laptop. Ciao, -- Martin
Re: Careful with dist-upgrade in unstable at the moment
Aurélien COUDERC - 21.12.22, 23:10:14 CET: > I’d like to recommend using « apt upgrade » which has a slightly > different behaviour than apt-get : it will upgrade already installed > packages but also install new packages where necessary (which apt-get > upgrade won’t do). > > This will leave full-upgrade with less things to do and for me to > review. The only remaining packages should have a note in their > changelog about doing a split, replacing another package or adding a > Breaks/Replace condition. I regularly check this when I see non > obvious removals (and by obvious I really only mean libfooN+1 > replacing libfooN). Interesting. I did not know this difference in behavior between "apt" and "apt-get". Thank you, Aurélien Ciao, -- Martin
Re: Careful with dist-upgrade in unstable at the moment
Marc Haber - 21.12.22, 21:37:45 CET: > On Wed, Dec 21, 2022 at 12:50:45PM +0100, Martin Steigerwald wrote: > > Marc Haber - 21.12.22, 12:00:39 CET: > > > > Stop using *dist-*upgrade by DEFAULT. > > > > > > *AMEN* to that. > > > > I usually do "dist-upgrade", but then look carefully what it is > > about to do. If I don't like that, I only to "upgrade". > > > > Of course one can argue it is safer to do it the other way around. > > I find it way easier to have apt reduce the problem riskless first. > It's a shorter list of actions to review. Good argument. My argument is that in the usual situation trying "apt full-upgrade" first will save me one command. With "apt upgrade" I often enough would have to use "apt full-upgrade" afterwards. But more often "apt full-upgrade" just does its job. Even in Debian Unstable (or Devuan Ceres). I made an interesting experience regarding the current Qt transition: I updated a ThinkPad X1 Gen 1 Tablet with "apt upgrade" yesterday. Parts of the Plasma desktop are still broken. Some part of systray misses some QML files, KRunner shows up as an empty pane without anything, the lock screen is not usable and several other issues. So it can still happen with just "apt upgrade" that you have an only partly usable system afterwards. Of course I'd argue that this is an issue with missing versioned dependencies. However it appears to me that it is quite different to completely get this right with a software stack of this complexity. So I will just wait until a "full-upgrade" can run through fully on this tablet and probably stay away from a "upgrade" on my laptop as well for a few days. However I used "apt upgrade" to upgrade my laptop earlier on the same day and have seen no such updates. The tablet has not been updated for a longer time, but that should not really make much of a difference. Anyway, Qt transitions had been painful in the past. I still remember having not been able to login to a Plasma desktop for days to come. I installed MATE back then I think in order to have a working desktop. > P.S. dist-upgrade is as deprecated as it could be, it's not even in > the man page any more I know about full-upgrade. But actually do not care all that much as long as the other one still works. Habits. But right, publicly it would be better to write "full-upgrade". Ciao, -- Martin
Re: Careful with dist-upgrade in unstable at the moment
Hi all, Le mercredi 21 décembre 2022, 21:37:45 CET Marc Haber a écrit : > On Wed, Dec 21, 2022 at 12:50:45PM +0100, Martin Steigerwald wrote: > > Marc Haber - 21.12.22, 12:00:39 CET: > > > > Stop using *dist-*upgrade by DEFAULT. > > > > > > *AMEN* to that. > > > > I usually do "dist-upgrade", but then look carefully what it is about to > > do. If I don't like that, I only to "upgrade". > > > > Of course one can argue it is safer to do it the other way around. > > P.S. dist-upgrade is as deprecated as it could be, it's not even in the > man page any more That can be correct or incorrect depending on which manpage you’re looking at. :) dist-upgrade is an argument for apt-get while full-upgrade is for apt. I’d like to recommend using « apt upgrade » which has a slightly different behaviour than apt-get : it will upgrade already installed packages but also install new packages where necessary (which apt-get upgrade won’t do). This will leave full-upgrade with less things to do and for me to review. The only remaining packages should have a note in their changelog about doing a split, replacing another package or adding a Breaks/Replace condition. I regularly check this when I see non obvious removals (and by obvious I really only mean libfooN+1 replacing libfooN). Happy hacking, -- Aurélien
Re: Careful with dist-upgrade in unstable at the moment
On Wed, 21 Dec 2022 21:37:45 +0100 Marc Haber wrote: > > P.S. dist-upgrade is as deprecated as it could be, it's not even in > the man page any more > It's called "full-upgrade" in apt and aptitude, but it's still called "dist-upgrade" in apt-get, which still gets installed with the apt package.
Re: Careful with dist-upgrade in unstable at the moment
On Wed, Dec 21, 2022 at 12:50:45PM +0100, Martin Steigerwald wrote: > Marc Haber - 21.12.22, 12:00:39 CET: > > > Stop using *dist-*upgrade by DEFAULT. > > > > *AMEN* to that. > > I usually do "dist-upgrade", but then look carefully what it is about to > do. If I don't like that, I only to "upgrade". > > Of course one can argue it is safer to do it the other way around. I find it way easier to have apt reduce the problem riskless first. It's a shorter list of actions to review. Greetings Marc P.S. dist-upgrade is as deprecated as it could be, it's not even in the man page any more -- - 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
Re: Careful with dist-upgrade in unstable at the moment
Marc Haber - 21.12.22, 12:00:39 CET: > > Stop using *dist-*upgrade by DEFAULT. > > *AMEN* to that. I usually do "dist-upgrade", but then look carefully what it is about to do. If I don't like that, I only to "upgrade". Of course one can argue it is safer to do it the other way around. Ciao, -- Martin
Re: Careful with dist-upgrade in unstable at the moment
On Wed, Dec 21, 2022 at 11:42:17AM +0100, Diederik de Haas wrote:
> On Wednesday, 21 December 2022 11:01:07 CET Sedat Dilek wrote:
> > P.S.: If you are Debian/unstable AMD64 user and are experienced
> > enough, you can try on YOUR OWN RISK.
> >
> > To pass daily dist-upgrades I did the following:
> >
> > [ Set all QT v5.15.6 packages on hold ]
> > root# VER="5.15..6" ; for p in $( dpkg -l | grep $VER | awk '/^ii/
> > {print $2}' ) ; do echo "[ $p ]" ; echo "$p" "hold" | dpkg
> > --set-selections ; done
>
> I must be sounding like a broken record player (by now), but:
>
> Stop using *dist-*upgrade by DEFAULT.
*AMEN* to that.
> And apparently it's (also) needed to say that apt/apt-get/aptitude tells you
> what it's about to do. If it's telling you that it'll remove (almost) all of
> KDE and you don't want that, you can say 'No' and not go through with that.
>
> The normal/safe-upgrade is what you should be using by default and only when
> you want to force something, you'd do a dist-/full-upgrade and then you
> evaluate what it's about to do and when you think "Yes, that's what I want",
> then and only then you go through with it.
Yes. Do apt upgrade to get the easy changes, try it again after it
finished. If it still wants to change something, THEN try apt
full-upgrade AND look what apt is suggesting to do. Use your own
judgement whether to allow apt full-upgrade to do what it intends to do.
You may also apt install manually some packages that apt upgrade won't
touch to see what the problem is. In many cases, it's just the change
from libfooX to libfooX+1 with a handful of affected packages, so you
can allow it togo ahead, but sometimes it's something like the current
situation that would deinstall half of your system.
It's called unstable for a reason, it's supposed to be broken once in a
while.
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
Re: Careful with dist-upgrade in unstable at the moment
On Wednesday, 21 December 2022 11:01:07 CET Sedat Dilek wrote:
> P.S.: If you are Debian/unstable AMD64 user and are experienced
> enough, you can try on YOUR OWN RISK.
>
> To pass daily dist-upgrades I did the following:
>
> [ Set all QT v5.15.6 packages on hold ]
> root# VER="5.15..6" ; for p in $( dpkg -l | grep $VER | awk '/^ii/
> {print $2}' ) ; do echo "[ $p ]" ; echo "$p" "hold" | dpkg
> --set-selections ; done
I must be sounding like a broken record player (by now), but:
Stop using *dist-*upgrade by DEFAULT.
And apparently it's (also) needed to say that apt/apt-get/aptitude tells you
what it's about to do. If it's telling you that it'll remove (almost) all of
KDE and you don't want that, you can say 'No' and not go through with that.
The normal/safe-upgrade is what you should be using by default and only when
you want to force something, you'd do a dist-/full-upgrade and then you
evaluate what it's about to do and when you think "Yes, that's what I want",
then and only then you go through with it.
I think they above quoted script is absolutely horrific.
My 0.02
signature.asc
Description: This is a digitally signed message part.
Careful with dist-upgrade in unstable at the moment
Hi Martin,
thanks for the hint in things of QT version 5.15.7 transition.
This will require to rebuild KDE/Frameworks, KDE/Plasma and KDE/apps
(gears) and will take some time.
You can inform yourself about the transition status here:
Link: https://release.debian.org/transitions/html/qtbase-abi-5-15-7.html
Personally, I like to get informed by debian-kde maintainers or
mailing-list when the transition is over.
Kind regards,
-Sedat-
P.S.: If you are Debian/unstable AMD64 user and are experienced
enough, you can try on YOUR OWN RISK.
To pass daily dist-upgrades I did the following:
[ Set all QT v5.15.6 packages on hold ]
root# VER="5.15..6" ; for p in $( dpkg -l | grep $VER | awk '/^ii/
{print $2}' ) ; do echo "[ $p ]" ; echo "$p" "hold" | dpkg
--set-selections ; done
[ Archive packages on hold ]
root# dpkg --get-selections | grep hold > hold_2022-12-21.txt
[ Allow packages installation on (dist-)upgrade - e.g. when transition is over ]
root# for p in $( cat hold_2022-12-21.txt | awk '{print $1}' ) ; do
echo "[ $p ]" ; echo "$p" "install" | dpkg --set-selections ; do
[ Re-Hold packages if necessary ]
root# for p in $( cat hold_2022-12-21.txt | awk '{print $1}' ) ; do
echo "[ $p ]" ; echo "$p" "hold" | dpkg --set-selections ; do
Unfortunately, we have now the first re-build packages of
libkf5i18n5:amd64 from KDE/Framework coming to unstable.
So, you will need to put that on hold, too.
Otherwise packages will be removed - so BE CAREFUL.
-EOT-
Careful with dist-upgrade in unstable at the moment
Hi! Qt Transition ongoing. AFAIK that will be the intended version for next stable. On my system it would remove most of Plasma on a dist-upgrade. So give it some time if its similar on your setup. Best, -- Martin
