26 Jul
2021
26 Jul
'21
3:55 a.m.
Debian Bullseye is in deep freeze and scheduled for release 08/14.
Often I wait until after release but this happened to be a good weekend
for me to start testing Bullseye. The non-TDE parts went much smoother
than usual. The only minor difficulty thus far was switching routing
from Quagga to FRR.
I see there's a TDE Bullseye version in trinity-sb. However if I test
this I'd like to get back onto TDE stable as soon as possible.
Any thoughts please on if I try trinity-sb/bullseye how much time or
how difficult will it be to get back to TDE stable with Bullseye?
Thanks,
--Mike
26 Jul
26 Jul
5:59 a.m.
Anno domini 2021 Sun, 25 Jul 20:55:16 -0700
Mike Bird via tde-devels scripsit:
Debian Bullseye is in deep freeze and scheduled for
release 08/14.
Often I wait until after release but this happened to be a good weekend
for me to start testing Bullseye. The non-TDE parts went much smoother
than usual. The only minor difficulty thus far was switching routing
from Quagga to FRR.
I see there's a TDE Bullseye version in trinity-sb. However if I test
this I'd like to get back onto TDE stable as soon as possible.
Any thoughts please on if I try trinity-sb/bullseye how much time or
how difficult will it be to get back to TDE stable with Bullseye?
Thanks,
--Mike
____________________________________________________
tde-devels mailing list -- devels(a)trinitydesktop.org
To unsubscribe send an email to devels-leave(a)trinitydesktop.org
Web mail archive available at
https://mail.trinitydesktop.org/mailman3/hyperkitty/list/devels@trinitydesk…
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.
Nik
--
Please do not email me anything that you are not comfortable also sharing with the NSA,
CIA ...
8:46 a.m.
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
9:36 a.m.
On 2021/07/26 5:46:10 PM, Mike Bird via tde-devels wrote:
On Sun July 25 2021 22:59:04 Dr. Nikolaus Klepp
wrote:
Hi Mike,
I have been running TDE R14.1.0-dev on bullseye since the beginning of bullseye era, so no
issue there.
trinity-sb is a running stable release, that is R14.0.10 + all the changes made so far in
R14.0.x and that will end up
in R14.0.11. If you want to switch to trinity-sb, the best time to switch back to stable
is at the release of R14.0.11:
Slavek usually holds the build of trinity-sb for a while after each release to allow
people to effortlessly move back to
stable, since at that time the packages will be exactly the same. Just need to change your
apt source config.
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 ;-)
Cheers
Michele
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
____________________________________________________
tde-devels mailing list -- devels(a)trinitydesktop.org
To unsubscribe send an email to devels-leave(a)trinitydesktop.org
Web mail archive available at
https://mail.trinitydesktop.org/mailman3/hyperkitty/list/devels@trinitydesk…
1:28 p.m.
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
2:52 p.m.
Anno domini 2021 Mon, 26 Jul 06:28:17 -0700
Mike Bird via tde-devels scripsit:
On Mon July 26 2021 02:36:26 Michele Calgaro via
tde-devels 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?
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
____________________________________________________
tde-devels mailing list -- devels(a)trinitydesktop.org
To unsubscribe send an email to devels-leave(a)trinitydesktop.org
Web mail archive available at
https://mail.trinitydesktop.org/mailman3/hyperkitty/list/devels@trinitydesk…
--
Please do not email me anything that you are not comfortable also sharing with the NSA,
CIA ...
3:16 p.m.
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.
10:43 a.m.
On Monday 26 of July 2021 05:55:16 Mike Bird via tde-devels wrote:
Debian Bullseye is in deep freeze and scheduled for
release 08/14.
Often I wait until after release but this happened to be a good weekend
for me to start testing Bullseye. The non-TDE parts went much smoother
than usual. The only minor difficulty thus far was switching routing
from Quagga to FRR.
I see there's a TDE Bullseye version in trinity-sb. However if I test
this I'd like to get back onto TDE stable as soon as possible.
Any thoughts please on if I try trinity-sb/bullseye how much time or
how difficult will it be to get back to TDE stable with Bullseye?
Thanks,
--Mike
____________________________________________________
Hi Mike,
as mentioned in previous answers, there are several options. I'll try to
summarize options and plans:
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.
Cheers
--
Slávek
1:32 p.m.
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
1:52 p.m.
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.
Hi Mike,
re clang 7 --> clang 11 switch, the hassle for you should be none if you wait a little.
It just happens that I have just
switched my building environment from gcc to clang last week and I am currently ironing
out those few FTBFS that I have
come across, mostly caused by c++17 enforcement in clang 11. So by the time R14.0.11 is
out, TDE should be up and
running even if built with clang 11.
Cheers
Michele
1005
days inactive
1005
days old
9 comments
4 participants
participants (4)
-
Dr. Nikolaus Klepp -
Michele Calgaro -
Mike Bird -
Slávek Banko