Doing my usual daily update/upgrade, I just now encountered this:
The following packages have been kept back: kubuntu-default-settings-trinity
I presume it's some kind of metapackage and that it has no effect on the functioning of my system. It's the first error of this sort that I've seen in years, though, so I thought I'd pass it along. Am running R14.0.11. -- dep
Pictures: http://www.ipernity.com/doc/depscribe/album Column: https://ofb.biz/author/dep/
On Thursday 28 of October 2021 16:20:52 dep wrote:
Doing my usual daily update/upgrade, I just now encountered this:
The following packages have been kept back: kubuntu-default-settings-trinity
I presume it's some kind of metapackage and that it has no effect on the functioning of my system. It's the first error of this sort that I've seen in years, though, so I thought I'd pass it along. Am running R14.0.11. -- dep
Hi dep,
yes, kubuntu-default-settings-trinity is a metapackage. You can use TUI aptitude to verify why is the package in "kept back"? Are you using the aptitude/apt call with command "upgrade" or "full-upgrade"? You can verify whether when using a "full-upgrade" it will be ok?
Thanks!
Cheers
said Slávek Banko: | On Thursday 28 of October 2021 16:20:52 dep wrote: | > Doing my usual daily update/upgrade, I just now encountered this: | > | > The following packages have been kept back: | > kubuntu-default-settings-trinity | > | > I presume it's some kind of metapackage and that it has no effect on | > the functioning of my system. It's the first error of this sort that | > I've seen in years, though, so I thought I'd pass it along. Am running | > R14.0.11. -- | > dep | | Hi dep, | | yes, kubuntu-default-settings-trinity is a metapackage. You can use TUI | aptitude to verify why is the package in "kept back"? Are you using the | aptitude/apt call with command "upgrade" or "full-upgrade"? You can | verify whether when using a "full-upgrade" it will be ok?
I'd happily cut'n'paste the output here, but aptitude is not nice about that kind of thing, so a screenshot.
I haven't tried to force it because I like my system and am disinclined to break it, as forcing things has been known to do. I'm mostly puzzled as to why this has suddenly come to pass -- I've upgraded a whole lot of Linux and TDE since the last time I saw that particular error. -- dep
Pictures: http://www.ipernity.com/doc/depscribe/album Column: https://ofb.biz/author/dep/
On Thursday 28 of October 2021 17:19:53 dep wrote:
I'd happily cut'n'paste the output here, but aptitude is not nice about that kind of thing, so a screenshot.
I haven't tried to force it because I like my system and am disinclined to break it, as forcing things has been known to do. I'm mostly puzzled as to why this has suddenly come to pass -- I've upgraded a whole lot of Linux and TDE since the last time I saw that particular error.
When you move the cursor to a new version (4:14.0.11-0ubuntu20.04.0+0) and hit Enter on it, there should be to see which package gets into conflict.
Cheers
said Slávek Banko: | On Thursday 28 of October 2021 17:19:53 dep wrote: | > I'd happily cut'n'paste the output here, but aptitude is not nice | > about that kind of thing, so a screenshot. | > | > I haven't tried to force it because I like my system and am | > disinclined to break it, as forcing things has been known to do. I'm | > mostly puzzled as to why this has suddenly come to pass -- I've | > upgraded a whole lot of Linux and TDE since the last time I saw that | > particular error. | | When you move the cursor to a new version (4:14.0.11-0ubuntu20.04.0+0) | and hit Enter on it, there should be to see which package gets into | conflict.
I couldn't make much sense of it -- aptitude is a kind of secret-handshake application -- but I went ahead and forced the install and at this point, several hours later (though no reboot) nothing bad seems to have happened. -- dep
Pictures: http://www.ipernity.com/doc/depscribe/album Column: https://ofb.biz/author/dep/
On 2021-10-28 09:20:52 dep wrote:
From: dep dep@drippingwithirony.com To: TDE Users users@trinitydesktop.org
Doing my usual daily update/upgrade, I just now encountered this:
The following packages have been kept back: kubuntu-default-settings-trinity
I presume it's some kind of metapackage and that it has no effect on the functioning of my system. It's the first error of this sort that I've seen in years, though, so I thought I'd pass it along. Am running R14.0.11. --
The last announcement I've gotten says that R14.0.11 is "coming soon." Have I somehow missed another?
Leslie
On Thu October 28 2021 16:19:47 J Leslie Turriff wrote:
R14.0.11. --
The last announcement I've gotten says that R14.0.11 is "coming soon." Have I somehow missed another?
Hi Leslie,
Several of us are testing the R14.0.11 pre-release from trinity-sb. You could switch if you wish but it's so close to release that you might as well wait at most a few days before Slávek and the developers release it as the new stable TDE.
--Mike