HEllo all,
I'm running SolydK and Devuan. These last month I've been updating regularely without trouble. SolyK being a rolling distribution, I expected some probems with Debian 9 being released so I was not really surprised that the last update announced removing lots of things - including TDE.
However, when I tried updating Devuan (which is still Jessie based AFAIK) I get the same result: no update without removing TDE!
Not that I *need* to update, but what's the problem? Any idea?
Thierry
On Saturday 24 of June 2017 07:03:18 Thierry de Coulon wrote:
HEllo all,
I'm running SolydK and Devuan. These last month I've been updating regularely without trouble. SolyK being a rolling distribution, I expected some probems with Debian 9 being released so I was not really surprised that the last update announced removing lots of things - including TDE.
However, when I tried updating Devuan (which is still Jessie based AFAIK) I get the same result: no update without removing TDE!
Not that I *need* to update, but what's the problem? Any idea?
Thierry
Are you sure SolydK is rolling distribution? How do I read the wiki: SolydXK, originally based on Debian testing, since January 2015 is built on Debian Stable. There are also Community Editions, not officially tested nor supported by the SolydXK team. Examples are the SolydXK Enthusiast’s Edition - versions of SolydX and SolydK that follow Debian testing.
The news page then mentions the change of the apt repository for updating from Jessie to Stretch: https://solydxk.com/update-getting-ready-for-stretch/
Devuan 1.0 (Jessie) is definitely based on Jessie and can be used with TDE for Jessie. Devuan 2.0 (Ascii) is based on Stretch and can be used with TDE for Stretch (in Preliminary Stable Builds repository). I have now tested TDE in both Ascii and Ceres and do not seem to be in conflict.
Did you get all apt lists properly?
Cheers
On Saturday 24 June 2017 16.29:33 Slávek Banko wrote:
Are you sure SolydK is rolling distribution?
Maybe that's not the exact description, but from what they explain there is no "jessie" edition and there will be no "stretch" version. AUtomatic update is supposed to bring us from 8.x to 9.0
Devuan 1.0 (Jessie) is definitely based on Jessie and can be used with TDE for Jessie.
But using synaptic or aptitude to update packages now says it's going to remove TDE (same behaviour in SolydK and Devuan; this is *new*, until now it worked with no problem).
Did you get all apt lists properly?
I changed nothing and did and apt-get update before looking for package updates.
I can imagine something is foul in my lists, but they were OK on tuesday and they were no more on friday, without any change.
Cheers
thanks,
Thierry
On 06/24/2017 01:19 PM, Thierry de Coulon wrote:
Maybe that's not the exact description, but from what they explain there is no "jessie" edition and there will be no "stretch" version. AUtomatic update is supposed to bring us from 8.x to 9.0 [...] But using synaptic or aptitude to update packages now says it's going to remove TDE
In your attached jpg, tde-trinity and tdemultimedia-trinity are only metapackages; it's not going to remove all of Trinity. But if you're upgrading the OS from jessie to stretch, you'll have to upgrade Trinity from jessie to stretch also. I don't know whether Trinity for jessie will work on stretch.
On Saturday 24 June 2017 22.44:17 Dan Youngquist wrote:
In your attached jpg, tde-trinity and tdemultimedia-trinity are only metapackages; it's not going to remove all of Trinity.
Thanks. That idea had come to my mind also.
But if you're upgrading the OS from jessie to stretch, you'll have to upgrade Trinity from jessie to stretch also. I don't know whether Trinity for jessie will work on stretch.
When I have time, I'll do a complete backup and try, at least on Devuan. For Stretch, Ill wait a little and probably only upgrade when TDE is ready for Debian 9.0
Thierry
On Sat, 24 Jun 2017 22:19:48 +0200 Thierry de Coulon tdecoulon@gmail.com wrote:
On Saturday 24 June 2017 16.29:33 Slávek Banko wrote:
Are you sure SolydK is rolling distribution?
Maybe that's not the exact description, but from what they explain there is no "jessie" edition and there will be no "stretch" version. AUtomatic update is supposed to bring us from 8.x to 9.0
Devuan 1.0 (Jessie) is definitely based on Jessie and can be used with TDE for Jessie.
But using synaptic or aptitude to update packages now says it's going to remove TDE (same behaviour in SolydK and Devuan; this is *new*, until now it worked with no problem).
Did you get all apt lists properly?
I changed nothing and did and apt-get update before looking for package updates.
I can imagine something is foul in my lists, but they were OK on tuesday and they were no more on friday, without any change.
The choice of packages to remove are very interesting. Something sound related is clearly breaking (also its not going to remove trinity DE, only some sound related apps from trinity). Start aptitude and find what package actually breaks everything, i suspect you have some 3-rd party/selfcomplited sound related package installed.
On Saturday 24 June 2017 23.26:08 Nick Koretsky wrote:
The choice of packages to remove are very interesting. Something sound related is clearly breaking (also its not going to remove trinity DE, only some sound related apps from trinity). Start aptitude and find what package actually breaks everything, i suspect you have some 3-rd party/selfcomplited sound related package installed.
You are right. However, I'm not used to aptitude. apt-get -f returns "0 to remove". What should I do? Let aptitude upgrade and remove?
Seems aptitude purge needs to be told which package. should I purge libasound2-plugins:386?
Regards,
Thierry
On Sun, 25 Jun 2017 09:46:32 +0200 Thierry de Coulon tdecoulon@gmail.com wrote:
On Saturday 24 June 2017 23.26:08 Nick Koretsky wrote:
The choice of packages to remove are very interesting. Something sound related is clearly breaking (also its not going to remove trinity DE, only some sound related apps from trinity). Start aptitude and find what package actually breaks everything, i suspect you have some 3-rd party/selfcomplited sound related package installed.
You are right. However, I'm not used to aptitude. apt-get -f returns "0 to remove". What should I do? Let aptitude upgrade and remove?
Seems aptitude purge needs to be told which package. should I purge libasound2-plugins:386?
From the screenshots: libasound2-plugins and libasound2-plugins:386 must be of the same version, but you have have one from dmo repository. In aptitude, force them to the same version.
On Sunday 25 June 2017 16.17:23 Nick Koretsky wrote:
From the screenshots: libasound2-plugins and libasound2-plugins:386 must be of the same version, but you have have one from dmo repository. In aptitude, force them to the same version.
Sound good, but I', afraid I don't know how to do that. I've read man aptitude, but seen no clue. Something with -t ?
I guess I would manage to remove the *:i386 files. Would that do?
I obviously have a lot to learn about aptitude.
Thanks,
Thierry
On Sun, 25 Jun 2017 17:14:05 +0200 Thierry de Coulon tcoulon@decoulon.ch wrote:
From the screenshots: libasound2-plugins and libasound2-plugins:386 must be of the same version, but you have have one from dmo repository. In aptitude, force them to the same version.
Sound good, but I', afraid I don't know how to do that. I've read man aptitude, but seen no clue. Something with -t ?
In an interface mode, just find a correct version and press "+", then when the are no broken packages press "g"to apply.
I guess I would manage to remove the *:i386 files. Would that do?
I obviously have a lot to learn about aptitude.
If you use any non-main repositories for debian-based sysytem (like dmo, backports, ppas, etc) you HAVE to learn how to use aptitude, because you will eventually run into a situation where apt upgrade suggest removing half system.
On 06/25/2017 07:55 AM, Nick Koretsky wrote:
On Sun, 25 Jun 2017 17:14:05 +0200 Thierry de Coulon tcoulon@decoulon.ch wrote:
From the screenshots: libasound2-plugins and libasound2-plugins:386 must be of the same version, but you have have one from dmo repository. In aptitude, force them to the same version.
Sound good, but I', afraid I don't know how to do that. I've read man aptitude, but seen no clue. Something with -t ?
In an interface mode, just find a correct version and press "+", then when the are no broken packages press "g"to apply.
I guess I would manage to remove the *:i386 files. Would that do?
I obviously have a lot to learn about aptitude.
If you use any non-main repositories for debian-based sysytem (like dmo, backports, ppas, etc) you HAVE to learn how to use aptitude, because you will eventually run into a situation where apt upgrade suggest removing half system.
One option that I found useful when installing from cli, "-s" or apt-get -s intall xxx will run through the install process without installing any packages.
I have stopped using dmo repos, eventualy something breaks, esp when I compile something..a needed library depends is the wrong version
greg
On Monday 26 June 2017 07.19:19 Greg Madden wrote:
One option that I found useful when installing from cli, "-s" or apt-get -s intall xxx will run through the install process without installing any packages.
Yes, it prevents deleting things but does not tell you how to prevent it...
I have stopped using dmo repos, eventualy something breaks, esp when I compile something..a needed library depends is the wrong version
Probably right. Unfortunately the "strictly free" option of Debian is one thing I don't always follow
greg
Anyway, as far, my results are as follow:
Trying to correct the situation with aptitude failed (probably my fault) and resulted in the removal of many things (but not TDE itself). I restored my backup of end of may on my system partition and updated: worked. So I must have screwed things up some time this month.
Same try in Devuan resulted in TDE removal. After that it was impossible to reinstall it (unsatisfied dependancies). So there too I restored but the update problems remain. I'll have to look further, but as Devuan went from RC2 to 1.0, I don't know if you can just "update" from the first to the second. No production system anyway so I probably better install new and clean.
Thanks for all the help,
Thierry
-
Dan Youngquist -
Greg Madden -
Nick Koretsky -
Slávek Banko -
Thierry de Coulon -
Thierry de Coulon