Processing of plasma-desktop_5.24.2-1_source.changes
/plasma-desktop_5.24.2-1_source.changes couldn't be processed for 48 hours and is now deleted All files it mentions are also removed: plasma-desktop_5.24.2-1.dsc, plasma-desktop_5.24.2.orig.tar.xz, plasma-desktop_5.24.2.orig.tar.xz.asc, plasma-desktop_5.24.2-1.debian.tar.xz, plasma-desktop_5.24.2-1_source.buildinfo Greetings, Your Debian queue daemon (running on host usper.debian.org)
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?
