Re: Plasma 5.24 coming to unstable
Just an observation to this. It was fixed for maximized windows, still did not work with normal windows. Today i switched from breeze decoration to materia and it works now Libor On St, 2022-03-02 at 13:47 +0100, Aurélien COUDERC wrote: > > > Dear Libor, > > Le 2 mars 2022 10:00:43 GMT+01:00, "Libor Klepáč" > a écrit : > > Thanks for your work and upload. > > > > Updated without problems and as heavy shade/unshade window user, I > > immediately hit this: > > > > https://bugs.kde.org/show_bug.cgi?id=450777 > > > > It will be tough, I shade my windows without thinking about it ;) > > I'm not using that feature but I can understand your frustration. :-) > > Feel free to comment on the upstream bug, to follow-up here and if a > patch gets merged upstream we can add it to the Debian package. > > We can even walk you through if you're interested in cherry picking > such a patch into the package yourself so it benefits everyone > (better on IRC than on a mailing list though). > > > Cheers, > -- > Aurélien >
Re: Plasma 5.24 coming to unstable
Hi, seems to be fixed in plasma 5.24.3 With regards, Libor On St, 2022-03-02 at 13:47 +0100, Aurélien COUDERC wrote: > > > Dear Libor, > > Le 2 mars 2022 10:00:43 GMT+01:00, "Libor Klepáč" > a écrit : > > Thanks for your work and upload. > > > > Updated without problems and as heavy shade/unshade window user, I > > immediately hit this: > > > > https://bugs.kde.org/show_bug.cgi?id=450777 > > > > It will be tough, I shade my windows without thinking about it ;) > > I'm not using that feature but I can understand your frustration. :-) > > Feel free to comment on the upstream bug, to follow-up here and if a > patch gets merged upstream we can add it to the Debian package. > > We can even walk you through if you're interested in cherry picking > such a patch into the package yourself so it benefits everyone > (better on IRC than on a mailing list though). > > > Cheers, > -- > Aurélien >
Re: Plasma 5.24 coming to unstable
Dear Libor, Le 2 mars 2022 10:00:43 GMT+01:00, "Libor Klepáč" a écrit : >Thanks for your work and upload. > >Updated without problems and as heavy shade/unshade window user, I >immediately hit this: > >https://bugs.kde.org/show_bug.cgi?id=450777 > >It will be tough, I shade my windows without thinking about it ;) I'm not using that feature but I can understand your frustration. :-) Feel free to comment on the upstream bug, to follow-up here and if a patch gets merged upstream we can add it to the Debian package. We can even walk you through if you're interested in cherry picking such a patch into the package yourself so it benefits everyone (better on IRC than on a mailing list though). Cheers, -- Aurélien
Re: Plasma 5.24 coming to unstable
Thanks for your work and upload. Updated without problems and as heavy shade/unshade window user, I immediately hit this: https://bugs.kde.org/show_bug.cgi?id=450777 It will be tough, I shade my windows without thinking about it ;) Libor On Ne, 2022-02-27 at 00:15 +0100, Patrick Franz wrote: > Hi all, > > we've just uploaded Plasma 5.24.2 to unstable. The first packages > should > be arriving in a couple of hours. > > As always, be careful when you upgrade and make sure that you upgrade > the entire Plasma stack at once to avoid mixing 5.23 and 5.24. > >
Re: Plasma 5.24 coming to unstable
bruno zanetti - 28.02.22, 15:15:14 CET: > Il giorno lun 28 feb 2022 alle ore 14:50 Miguel A. Vallejo > > ha scritto: > > The question is: > > > > Why is APT not smart enough to see that the proposed upgrade will > > fail? > > > > It always starts to install packages and at some point fails because > > some package needs another package with a specific version. Why does > > it not detect these cases after starting upgrading packages? It > > knows > > the versions available for every package so it should prevent these > > problems. > > > > Is it a bug or a missing APT feature? > > I think the problem in which you incurred is not related to an APT > bug or (missing) feature but rather a packaging bug ( > https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1006538) that has > been catched (and fixed) in sid. > After all this is just the purpose of sid. Yes. And really, to everyone who is complaining: Debian Sid is also called Debian Unstable. For a reason! Either be prepared to handle the occasional glitch – in this case the glitch could be handled by using the appropriate dpkg force option. Or don't use it. It is really as simple as that. Best. -- Martin
Re: Plasma 5.24 coming to unstable
Il giorno lun 28 feb 2022 alle ore 14:50 Miguel A. Vallejo ha scritto: > The question is: > > Why is APT not smart enough to see that the proposed upgrade will fail? > > It always starts to install packages and at some point fails because > some package needs another package with a specific version. Why does > it not detect these cases after starting upgrading packages? It knows > the versions available for every package so it should prevent these > problems. > > Is it a bug or a missing APT feature? > I think the problem in which you incurred is not related to an APT bug or (missing) feature but rather a packaging bug ( https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1006538) that has been catched (and fixed) in sid. After all this is just the purpose of sid. BZ
Re: Plasma 5.24 coming to unstable
Miguel A. Vallejo ha scritto: > The question is: > > Why is APT not smart enough to see that the proposed upgrade will fail? > No, it can't infer what humans think, unless the packages contain the information that their versions are strictly linked together. -- Luigi
Re: Plasma 5.24 coming to unstable
On 28/02/2022 13:50, Miguel A. Vallejo wrote: The question is: Why is APT not smart enough to see that the proposed upgrade will fail? It always starts to install packages and at some point fails because some package needs another package with a specific version. Why does it not detect these cases after starting upgrading packages? It knows the versions available for every package so it should prevent these problems. Is it a bug or a missing APT feature? I have never seen this behaviour in 20+ years of using Debian [15 of them with SID]. Closest thing I have seen is something about "broken packages" but that is before it starts to do any actual work. What is the message you getting when this happens? alexd
Re: Plasma 5.24 coming to unstable
The question is: Why is APT not smart enough to see that the proposed upgrade will fail? It always starts to install packages and at some point fails because some package needs another package with a specific version. Why does it not detect these cases after starting upgrading packages? It knows the versions available for every package so it should prevent these problems. Is it a bug or a missing APT feature?
Re: Plasma 5.24 coming to unstable
Hi Brad (and Erwan), * Brad Rogers [2022-02-27 20:22]: On Sun, 27 Feb 2022 16:47:25 +0100 Erwan David wrote: Hello Erwan, I know wether all plasma packages will upgrade or not ? Whenever I see a large number of plasma packages arrive in testing, I check versions. If they go from 5.14.something to 5.14.somethingelse, then I upgrade without too many worries. If the packages go from 5.14.something to 5.15.something, then I wait a day or two, to make sure everything has come through - in the mean time checking as best I can that there aren't any known issues (here, Debian packages, DDG search, etc). If packages were to go from 5.14.5 to 6.something, I'd again hold on a day or two to make sure everything's in sync. For doing these mega updates, everyone has his/her particular way of doing stuff, but some things can help quite a lot: 1. Try having a system installation with filesystem snapshots; thin snapshots work quite well. If everything becomes completely messed up you can easily revert to the initial state. This can be automated (e.g., before and after apt runs), and you can keep a few images with automatic rotation, just in case (consider snapper for this). 2. Try using aptitude interactively. This way all packages will end up in a consistent state; possible different forms of conflict resolution can be selected manually, you can also look/select different package versions, as also suggested installs. 3. After the major update is finished, you can check which packages did not yet upgrade to a target version number, with aptitude. These might not have migrated to testing yet. Just use something like: aptitude search '?narrow(~i,~V4.12)' aptitude search '?narrow(~i,~ncuda)' aptitude search '~V5.5' -F "%c %p %d %V" |sort |more If you feel safe, just update the packages that are identified (e.g., interactively again in aptitude). This way you'll be able to do a complete upgrade without waiting too long. Hope this can help. Regards, Nuno.
Re: Plasma 5.24 coming to unstable
On Sun, 27 Feb 2022 16:47:25 +0100 Erwan David wrote: Hello Erwan, >I know wether all plasma packages will upgrade or not ? Whenever I see a large number of plasma packages arrive in testing, I check versions. If they go from 5.14.something to 5.14.somethingelse, then I upgrade without too many worries. If the packages go from 5.14.something to 5.15.something, then I wait a day or two, to make sure everything has come through - in the mean time checking as best I can that there aren't any known issues (here, Debian packages, DDG search, etc). If packages were to go from 5.14.5 to 6.something, I'd again hold on a day or two to make sure everything's in sync. However, IME, there are fewer issues with migration to testing - the problems have usually been found in sid. If there *are* issues, there's quite often an announcement on this very list. Usually from Martin Steigerwald or Patrick Franz. Of course, things can still break, but it _is_ rare. Also, we the lucky users, get to keep all the pieces. :-) -- Regards _ / ) "The blindingly obvious is never immediately apparent" / _)rad "Is it only me that has a working delete key?" They take away our freedom in the name of liberty Suspect Device - Stiff Little Fingers pgpcavkjE2Z3p.pgp Description: OpenPGP digital signature
Re: Plasma 5.24 coming to unstable
On Sunday, 27 February 2022 16:41:28 CET Patrick Franz wrote: > > Thanks for the advice, but too late for me: my KDE is broken now. > > You should ideally warn one or two days before packages are uploaded. > > I disagree with having to give a warning 2 days in advance. If you run > unstable, you should read mailing-lists, hang around in IRC and/or > install apt-listbugs. On top of that, if you don't have the capacity to fix a broken Sid system, you shouldn't be running Sid. Running Sid is a great way to learn more about your system and if it breaks, figuring out how to fix it yourself is the most useful thing. If you need help, feel free to post your question(s) here and others may try to help. Packaged get uploaded to Sid all the time, so it should be fully expected and any announcement is courteous, but imo unneeded. signature.asc Description: This is a digitally signed message part.
Re: Plasma 5.24 coming to unstable
Le 27/02/2022 à 16:41, Patrick Franz a écrit : Hi, Thanks for the advice, but too late for me: my KDE is broken now. You should ideally warn one or two days before packages are uploaded. I'm sorry about the mistake I made in plasma-workspace, but it's fixed and Plasma 5.24 installs cleanly now. As for the advice, we've stated this multiple times to not mix versions. Plasma is quite the dependency hell and it's incredibly difficult to both get it right and prevent unintended consequences at the same time. I disagree with having to give a warning 2 days in advance. If you run unstable, you should read mailing-lists, hang around in IRC and/or install apt-listbugs. I use testing, but should be careful also (some pacakges do not go into testing as soon as the others). My question is always the same : How do I know wether all plasma packages will upgrade or not ? For the framework, I wait until I get the upgrade of plasma-framework package. But I do not know how to check that the upgrade will upgrade all installed plasma packages. Does someone have a trick for this ?
Re: Plasma 5.24 coming to unstable
tak so mücke! Op zo 27 feb. 2022 16:41 schreef Patrick Franz : > Hi, > > > Thanks for the advice, but too late for me: my KDE is broken now. > > You should ideally warn one or two days before packages are uploaded. > > I'm sorry about the mistake I made in plasma-workspace, but it's fixed > and Plasma 5.24 installs cleanly now. > > As for the advice, we've stated this multiple times to not mix versions. > Plasma is quite the dependency hell and it's incredibly difficult to > both get it right and prevent unintended consequences at the same time. > > I disagree with having to give a warning 2 days in advance. If you run > unstable, you should read mailing-lists, hang around in IRC and/or > install apt-listbugs. > > > -- > Med vänliga hälsningar > > Patrick Franz > > >
Re: Plasma 5.24 coming to unstable
Hi, > Thanks for the advice, but too late for me: my KDE is broken now. > You should ideally warn one or two days before packages are uploaded. I'm sorry about the mistake I made in plasma-workspace, but it's fixed and Plasma 5.24 installs cleanly now. As for the advice, we've stated this multiple times to not mix versions. Plasma is quite the dependency hell and it's incredibly difficult to both get it right and prevent unintended consequences at the same time. I disagree with having to give a warning 2 days in advance. If you run unstable, you should read mailing-lists, hang around in IRC and/or install apt-listbugs. -- Med vänliga hälsningar Patrick Franz
Re: Plasma 5.24 coming to unstable
Le dimanche 27 février 2022, 13:17:30 CET Miguel A. Vallejo a écrit : > Thanks for the advice, but too late for me: my KDE is broken now. > > You should ideally warn one or two days before packages are uploaded. > > > we've just uploaded Plasma 5.24.2 to unstable. The first packages should > > be arriving in a couple of hours. > > > > As always, be careful when you upgrade and make sure that you upgrade > > the entire Plasma stack at once to avoid mixing 5.23 and 5.24. @ Miguel https://github.com/teejee2008/timeshift
Re: Plasma 5.24 coming to unstable
Thanks for the advice, but too late for me: my KDE is broken now. You should ideally warn one or two days before packages are uploaded. > we've just uploaded Plasma 5.24.2 to unstable. The first packages should > be arriving in a couple of hours. > > As always, be careful when you upgrade and make sure that you upgrade > the entire Plasma stack at once to avoid mixing 5.23 and 5.24.
Plasma 5.24 coming to unstable
Hi all, we've just uploaded Plasma 5.24.2 to unstable. The first packages should be arriving in a couple of hours. As always, be careful when you upgrade and make sure that you upgrade the entire Plasma stack at once to avoid mixing 5.23 and 5.24. -- Med vänliga hälsningar Patrick Franz
