On Sun July 25 2021 22:59:04 Dr. Nikolaus Klepp wrote:

My linux boxes all run devuan/chimera + TDE 14.1. I don't think that you'll have a good day trying to switch back - I did that procedure once on days long gone by with lenny. It was a PITA. In the end, reinstalling would have been the better optinon.

Thanks Nik. I decided to do a test upgrade on a VPS instead.

Not sure exactly what is going on yet but it looks like I can have gcc-10 or TDE but not both. Might be a binutils thing, or maybe not.

Need some sleep now. I'll try to figure it out tomorrow.

--Mike

On Mon July 26 2021 02:36:26 Michele Calgaro via tde-devels wrote:

Re TDE and bin-utils, you may need an updated libr version if binutils was updated..... but in general TDE works fine in bullseye, even if you build with clang ;-)

Thank you Michele. The error was of course mine. In updating apt sources and apt pinning I had neglected one line which - because of a problem long ago - looked like this:

Pin: release o=trinitydesktop.org,v=10*

I have now changed it to the following and everything is much better.

Pin: release o=trinitydesktop.org,n=bullseye

--Mike

On Mon July 26 2021 07:52:24 Dr. Nikolaus Klepp wrote:

Aehm, why do you need to pin TDE? Isn't it sufficient to put one package on hold - if that's needed in the first place?

We sometimes need bits from backports, testing, oldstable, or experimental so we need to make sure we don't accidentally try to pull in newer versions of deps-14 that might not be compatible with TDE.

We also lock out systemd (except libsystemd0) (except we switch to libelogind0 with Bullseye).

And we arrange for libc not to be automatically downgraded(*).

--Mike

(*) I know downgrading isn't supported but we do in fact figure out a downgrade path and test it just in case we run into a show stopper on a live server upgrade that we missed during testing.

On Mon July 26 2021 03:43:18 Slávek Banko via tde-devels wrote:

1. Final release R14.0.11 is planned for the end of October 2021. So here

comes the primary question whether this is acceptable soon for you so that you could switch to PSB repository until then? After release R14.0.11 switching from PSB to stable will be simple - just make a change URL in "sources.list".

2. If it seems too late, there is a question whether it seems like a good

idea to consider build R14.0.10 packages when Bullseye will be finally released?

3. Here, the way would be to "mix the version of distribution". The key

package that causes a conflict when using Buster packages in Bullseye is the "libr0" package, which requires a specific version of the binutils. Because this package is very separate, you would be able to manually install this package for Bullseye from PSB. Unfortunately, there are several other conflicts (libilmbase23, libopenexr23) that require some other packages (tdelibs and some tdebase packages) for Bullsey from PSB. Some other conflicts can occur for some other packages - such as Kaffeine. So this way seems too complicated and with an uncertain result.

So now it is essential, what your opinion is for question 1.

Thank you Slávek. This helps enormously with planning.

For now I'm just going to have PSB on a VPS to keep an eye on compatability issues. In addition to Bullseye and TDE R14.0.11 I need to figure out how much hassle the jump from Clang 7 to Clang 11 is going to cause. So the end of October looks like a good date for me to aim for.

--Mike