On 8/16/21 3:55 AM, Michele Calgaro wrote:
On 2021/08/16 12:36:08 AM, Edward wrote:
On 8/15/21 10:15 AM, Edward wrote:
Debian has released version 11, bullseye. Should the current TDE (buster) packages work with bullseye until the packages are updated?
Thanks.
Confirming the TDE desktop (buster) came up fine, after upgrading Debian to bullseye.
Hi Edward, you could use PSB packages for bullseye ;-) so you also get rolling updates of the changes that will go into the next release.
Hi Michele,
Thank you for this information.
I went this route and added the lines to apt/etc/sources.list. Apt successfully retrieved and installed the R14.0.11-pre packages and it also resolved the binutils issue. The first desktop is working perfectly. I will do the same on my other desktop.
The original 'buster' entries for 14.0.10 were left as they were in the sources.list file.
Ed
-- Linux. A Continual Learning Experience.
TDE: R14.0.11-pre - Debian: 11 (amd64)
On 8/16/21 8:42 AM, Edward wrote:
On 8/16/21 3:55 AM, Michele Calgaro wrote:
On 2021/08/16 12:36:08 AM, Edward wrote:
On 8/15/21 10:15 AM, Edward wrote:
Debian has released version 11, bullseye. Should the current TDE (buster) packages work with bullseye until the packages are updated?
Thanks.
Confirming the TDE desktop (buster) came up fine, after upgrading Debian to bullseye.
Hi Edward, you could use PSB packages for bullseye ;-) so you also get rolling updates of the changes that will go into the next release.
Hi Michele,
Thank you for this information.
I went this route and added the lines to apt/etc/sources.list. Apt successfully retrieved and installed the R14.0.11-pre packages and it also resolved the binutils issue. The first desktop is working perfectly. I will do the same on my other desktop.
The original 'buster' entries for 14.0.10 were left as they were in the sources.list file.
Performed same upgrade on my other desktop. System came up perfectly after reboot and it resolved the binutils issue on this desktop as well. Both systems fully upgraded.
-- Linux. A Continual Learning Experience.
Trinity Desktop Environment: 14.0.11-pre - Debian: 11 (amd64)
On Monday 16 August 2021 16.30:38 Edward wrote:
Performed same upgrade on my other desktop. System came up perfectly after reboot and it resolved the binutils issue on this desktop as well. Both systems fully upgraded.
Other story here: total disaster. No error while upgrading, but then no DM (dpkg-reconfigure returns "broken or partially installed" for everything) and no network access either (apparently, the upgrade killed/removed WICD and setup nothing...).
I'll probably have to do as usual, clean install and complete setup - this will have to wait.
Thierry
On 8/16/21 3:01 PM, Thierry de Coulon wrote:
On Monday 16 August 2021 16.30:38 Edward wrote:
Performed same upgrade on my other desktop. System came up perfectly after reboot and it resolved the binutils issue on this desktop as well. Both systems fully upgraded.
Other story here: total disaster. No error while upgrading, but then no DM (dpkg-reconfigure returns "broken or partially installed" for everything) and no network access either (apparently, the upgrade killed/removed WICD and setup nothing...).
I'll probably have to do as usual, clean install and complete setup - this will have to wait.
Here, it indicated binutils was' broken', as it would not install binutils-common and one other package. During the upgrade process to install TDE 14.0.11-pre, binutils-common and the other package then became marked for an upgrade, they successfully installed and binutils is no longer 'broken'.
Several years back, I had Debian (I think it was version 8) installed on a laptop and recall having a terrible time getting the WiFi to work, WICD was used.
-- Linux. A Continual Learning Experience.
TDE: R14.0.11-pre - Debian: 11 (amd64)
Thierry de Coulon composed on 2021-08-16 21:01 (UTC+0200):
Other story here: total disaster. No error while upgrading, but then no DM (dpkg-reconfigure returns "broken or partially installed" for everything) and no network access either (apparently, the upgrade killed/removed WICD and setup nothing...).
I'll probably have to do as usual, clean install and complete setup - this will have to wait.
I've been converting my Tumbleweed and 15.3 installations, all of which use static IP wired ethernet, over to using systemd-networkd in recent months. After reading this, I decided to try the same on a freshly upgraded Bullseye. What I did:
1-# systemctl list-unit-files | grep net to ensure systemd-networkd.service systemd-network-generator.service systemd-networkd-wait-online.service systemd-networkd.socket existed.
2-deleted /etc/network/interfaces
3-deleted /etc/udev/rules.d/70-persistent-net.rules
4-ensured a valid regular file /etc/resolv.conf existed
5-created /etc/systemd/network/eth0.network containing (IPs changed to # for security): [Match] Name=eth0
[Network] Address=###.###.###.###/24 DNS=###.###.###.### 1.1.1.1 1.0.0.1 Gateway=###.###.###.### IPv6AcceptRA=no LinkLocalAddressing=no
6-verified systemd-resolved.service was disabled
7-rebooted to find network working normally.
I have no idea where routing information is configured or coming from in this configuration.
Felix Miata wrote:
I have no idea where routing information is configured or coming from in this configuration.
From the address notation Address=###.###.###.###/24
the /24 provides the routing as well. You specify the Gwateway and the subnet. This is sufficient to configure the default route.
-
deloptes -
Edward -
Felix Miata -
Thierry de Coulon