Re: upgrade debian + postfix/dovecot

On Thu, 2024-12-26 at 13:52 -0600, John Hasler wrote: > Thomas Anderson writes: > > Almost all the applications I use are non-debian (postfix, dovecot, > > apache, mysql, etc..) > > Why? All of those are in Debian. If you were using the Debian packages > upgrading would be easy. To nitpick, I do

Re: upgrade debian + postfix/dovecot

On 27/12/2024 02:41, Thomas Anderson wrote: I did get them from Debian sources, so I should be good. "Chapter 4. Upgrades from Debian 11 (bullseye)" from "Release Notes for Debian 12 (bookworm)" suggests

Re: upgrade debian + postfix/dovecot

Thomas Anderson writes: > Almost all the applications I use are non-debian (postfix, dovecot, > apache, mysql, etc..) Why? All of those are in Debian. If you were using the Debian packages upgrading would be easy. -- John Hasler j...@sugarbit.com Elmwood, WI USA

Re: upgrade debian + postfix/dovecot

Thanks Andy! I did get them from Debian sources, so I should be good. Per your advice, I will go through and read about changes, and see what I need to be mindful of. Of course, I will backup everything first. =) Thanks for clarifying the part about remove "non-debian source" software, which

Re: upgrade debian + postfix/dovecot

Hi, On Thu, Dec 26, 2024 at 07:39:23PM +0100, Thomas Anderson wrote: > I have been delayed with upgrading my debian distro, and want to upgrade to > 12. According to the documentation, I should remove all non-debian > applications first, before upgrading. Almost all the applications I use are > no

Re: upgrade to bookworm causes breakage

David Christensen wrote: ... > I understand that in-place upgrading a FOSS computer over many years is > a source of pride for many people. I tried that, and it did not work > out for me. Since then, I have invested myself in fresh installs, > minimal sysadmin changes, thorough documentation,

Re: upgrade to bookworm causes breakage

On Mon, 19 Aug 2024 at 22:51, Bob Mroczka wrote: > I attempted to upgrade my system from debian 11 to 12 following the > instructions provided at > https://www.cyberciti.biz/faq/update-upgrade-debian-11-to-debian-12-bookworm. Hi, For a better version of: "How to upgrade Debian 11 to Debian 12

Re: upgrade to bookworm causes breakage

On Mon 19 Aug 2024 at 20:26:35 (-0400), Gary Dale wrote: > On 2024-08-19 19:24, Mike wrote: > > Bob Mroczka wrote: > > > I attempted to upgrade my system from debian 11 to 12 following the > > > instructions provided at > > > https://www.cyberciti.biz/faq/update-upgrade-debian-11-to-debian-12-bookw

Re: upgrade to bookworm causes breakage

On 8/19/24 15:33, Bob Mroczka wrote: Hello, I attempted to upgrade my system from debian 11 to 12 following the instructions provided at https://www.cyberciti.biz/faq/update-upgrade-debian-11-to-debian-12-bookworm. I got to the point of executing the command at step 6 to do sudo apt full-upgrade

Re: upgrade to bookworm causes breakage

On Mon, Aug 19, 2024 at 9:56 PM Bob Mroczka wrote: > > Hello, > > I attempted to upgrade my system from debian 11 to 12 following the > instructions provided at > https://www.cyberciti.biz/faq/update-upgrade-debian-11-to-debian-12-bookworm. In the future, you should probably follow a Debian gui

Re: upgrade to bookworm causes breakage

On 2024-08-19 19:24, Mike wrote: Bob Mroczka wrote: I attempted to upgrade my system from debian 11 to 12 following the instructions provided at https://www.cyberciti.biz/faq/update-upgrade-debian-11-to-debian-12-bookworm. In the future, consider using https://www.debian.org/release/stable/ and

Re: upgrade to bookworm causes breakage

Bob Mroczka wrote: > I attempted to upgrade my system from debian 11 to 12 following the > instructions provided at > https://www.cyberciti.biz/faq/update-upgrade-debian-11-to-debian-12-bookworm. In the future, consider using https://www.debian.org/release/stable/ and such. cyberciti.biz usually

Re: upgrade to bookworm causes breakage

On Mon, Aug 19, 2024 at 17:33:13 -0500, Bob Mroczka wrote: > I attempted to upgrade my system from debian 11 to 12 following the > instructions provided at > https://www.cyberciti.biz/faq/update-upgrade-debian-11-to-debian-12-bookworm. I'm not going to read that web site. I'll just assume it's co

Re: rec recording, Re: Upgrade to Bookworm, now GNOME keyring dies …

* On 2024 21 Feb 12:42 -0600, David Wright wrote: > On Mon 19 Feb 2024 at 13:26:17 (-0600), Nate Bargmann wrote: > > > > After seeing this twice this morning I recalled that I have a cron entry > > to kill the 'rec' program. This was to break up audio files into hourly > > segments when recording

rec recording, Re: Upgrade to Bookworm, now GNOME keyring dies …

On Mon 19 Feb 2024 at 13:26:17 (-0600), Nate Bargmann wrote: > > After seeing this twice this morning I recalled that I have a cron entry > to kill the 'rec' program. This was to break up audio files into hourly > segments when recording an amateur radio event. This was the cron > command: > >

Re: Upgrade to Bookworm, now GNOME keyring dies--no access to stored SSH key passwords

Well, it appears like most things in life this one was self inflicted. 🤬 Yesterday I was working on another project and to verify something was occurring the 'strace' utility was recommended. It dawned on me that this could help me get a clue as to what was happening to the gnome-keyring-daemon.

Re: Upgrade to 12.3 fails due to missing nvidia firmware package

On 2023-12-06 17:20:16, Sven Joachim wrote: Maintainer uploads to (old)stable are staged in proposed-updates, so you would have to enable bookworm-proposed-updates to install the new version of firmware-nvidia-gsp. I missed the non-free-firmware for bookworm-updates and bookworm-proposed-upda

Re: Upgrade to 12.3 fails due to missing nvidia firmware package

On 2023-12-06 15:24 +0100, Harald Dunkel wrote: > I have tried to upgrade to 12.3, but apparently the dependencies > of the new nvidia-kernel-dkms version cannot be fulfilled. > firmware-nvidia-gsp (= 525.147.05) is missing. I tried several > repositories. Note that Debian 12.3 has not been relea

Re: Upgrade to 12.3 fails due to missing nvidia firmware package

On Wed, Dec 06, 2023 at 04:45:41PM +0100, Harald Dunkel wrote: > On 2023-12-06 15:55:58, Michael Kjörling wrote: > > > > Which ones? > > > > ftp.de.debian.org > ftp2.de.debian.org > deb.debian.org > > > That package is in the non-free-firmware component; are you bringing > > that in? > > > > h

Re: Upgrade to 12.3 fails due to missing nvidia firmware package

On 2023-12-06 15:55:58, Michael Kjörling wrote: Which ones? ftp.de.debian.org ftp2.de.debian.org deb.debian.org That package is in the non-free-firmware component; are you bringing that in? https://packages.debian.org/bookworm/firmware-nvidia-gsp There is still the old version 525.125.0

Re: Upgrade to 12.3 fails due to missing nvidia firmware package

On 6 Dec 2023 15:24 +0100, from harald.dun...@aixigo.com (Harald Dunkel): > I have tried to upgrade to 12.3, but apparently the dependencies > of the new nvidia-kernel-dkms version cannot be fulfilled. > firmware-nvidia-gsp (= 525.147.05) is missing. I tried several > repositories. Which ones? Th

Re: Upgrade my distribution

On Thu, Nov 16, 2023 at 09:09:08PM +, Michael Kjörling wrote: > On 16 Nov 2023 14:27 -0600, from willitc9...@gmail.com (William Torrez Corea): > > I have Debian 11 bullseye. I want have Debian 12 "bookworm" > > > > I execute the command: > > > > apt-get update > >> apt upgrade > >> apt dist-u

Re: Upgrade my distribution

William Torrez Corea writes: > How can I upgrade my distribution? > I have Debian 11 bullseye. I want have Debian 12 "bookworm" The release notes answer this in depth. https://www.debian.org/releases/bookworm/amd64/release-notes/ch-upgrading.en.html Ralf

Re: Upgrade my distribution

On 16 Nov 2023 14:27 -0600, from willitc9...@gmail.com (William Torrez Corea): > I have Debian 11 bullseye. I want have Debian 12 "bookworm" > > I execute the command: > > apt-get update >> apt upgrade >> apt dist-upgrade > > But I don't get any change in my distribution. In addition to what ha

Re: Upgrade my distribution

William Torrez Corea wrote: > *How can I upgrade my distribution?* > I have Debian 11 bullseye. I want have Debian 12 "bookworm" > > I execute the command: > > apt-get update > > apt upgrade > > apt dist-upgrade Step 0 is to change your /etc/apt/sources.list and anything in /etc/apt/sources.lis

Re: Upgrade my distribution

William Torrez Corea composed on 2023-11-16 14:27 (UTC-0600): > *How can I upgrade my distribution?* > I have Debian 11 bullseye. I want have Debian 12 "bookworm" > I execute the command: > apt-get update >> apt upgrade >> apt dist-upgrade > But I don't get any change in my distribution. You m

Re: Upgrade my distribution

On 16 Nov 2023, at 20:28, William Torrez Corea wrote:How can I upgrade my distribution?I have Debian 11 bullseye. I want have Debian 12 "bookworm"I execute the command:apt-get update apt upgrade apt dist-upgrade But I don't get any change in my distribution. Hi William,https://www.debian.org/rel

Re: upgrade to bookworm broke ssh x11 forwarding

On Mon, Nov 13, 2023 at 11:10:17AM +0100, Vincent Lefevre wrote: [...] > This is what I've done for my old laptop, but the dropbear package > is *not* needed for that! You just need the dropbear-initramfs > package [...] Aha -- now I know the full story. Thanks, Vincent (and all the other smart

Re: upgrade to bookworm broke ssh x11 forwarding

On 2023-11-10 15:32:53 +, fxkl4...@protonmail.com wrote: > On Fri, 10 Nov 2023, Vincent Lefevre wrote: > > > On 2023-11-10 10:57:21 +0100, Michael wrote: > >> On Thursday, 9 November 2023 19:08:25 CET, Greg Wooledge wrote: > >>> No, this is not a normal phenomenon for bookworm upgrades. I've

Re: upgrade to bookworm broke ssh x11 forwarding

On Fri, Nov 10, 2023 at 01:01:28PM -0500, Dan Ritter wrote: > to...@tuxteam.de wrote: [...] > > Wait a minute: dropbear is supposed to run in the initramfs, while > > sshd will be active afterwards, after pivot-root and all that, right? > > > > Then I don't quite get why they should collide at

Re: upgrade to bookworm broke ssh x11 forwarding

to...@tuxteam.de wrote: > On Fri, Nov 10, 2023 at 03:32:53PM +, fxkl4...@protonmail.com wrote: > > On Fri, 10 Nov 2023, Vincent Lefevre wrote: > > > > > On 2023-11-10 10:57:21 +0100, Michael wrote: > > >> On Thursday, 9 November 2023 19:08:25 CET, Greg Wooledge wrote: > > >>> No, this is not

Re: upgrade to bookworm broke ssh x11 forwarding

On Fri, Nov 10, 2023 at 03:32:53PM +, fxkl4...@protonmail.com wrote: > On Fri, 10 Nov 2023, Vincent Lefevre wrote: > > > On 2023-11-10 10:57:21 +0100, Michael wrote: > >> On Thursday, 9 November 2023 19:08:25 CET, Greg Wooledge wrote: > >>> No, this is not a normal phenomenon for bookworm upgr

Re: upgrade to bookworm broke ssh x11 forwarding

On Fri 10 Nov 2023 at 15:32:53 (+), fxkl4...@protonmail.com wrote: > On Fri, 10 Nov 2023, Vincent Lefevre wrote: > > > On 2023-11-10 10:57:21 +0100, Michael wrote: > >> On Thursday, 9 November 2023 19:08:25 CET, Greg Wooledge wrote: > >>> No, this is not a normal phenomenon for bookworm upgrad

Re: upgrade to bookworm broke ssh x11 forwarding

On Fri, 10 Nov 2023, Vincent Lefevre wrote: > On 2023-11-10 10:57:21 +0100, Michael wrote: >> On Thursday, 9 November 2023 19:08:25 CET, Greg Wooledge wrote: >>> No, this is not a normal phenomenon for bookworm upgrades. I've never >>> heard of it happening to anyone before. >> >> i disagree. i h

Re: upgrade to bookworm broke ssh x11 forwarding

On 2023-11-10 10:57:21 +0100, Michael wrote: > On Thursday, 9 November 2023 19:08:25 CET, Greg Wooledge wrote: > > No, this is not a normal phenomenon for bookworm upgrades. I've never > > heard of it happening to anyone before. > > i disagree. i had the same problem b/c i also had dropbear insta

Re: upgrade to bookworm broke ssh x11 forwarding

On Thursday, 9 November 2023 19:08:25 CET, Greg Wooledge wrote: No, this is not a normal phenomenon for bookworm upgrades. I've never heard of it happening to anyone before. i disagree. i had the same problem b/c i also had dropbear installed. for some reason the dropbear daemon is started f

Re: upgrade to bookworm broke ssh x11 forwarding

On Thu, Nov 9, 2023 at 6:16 PM wrote: > > On Thu, 9 Nov 2023, Jeffrey Walton wrote: > > > On Thu, Nov 9, 2023 at 11:43 AM Greg Wooledge wrote: > >> > >> On Thu, Nov 09, 2023 at 03:01:29PM +, fxkl4...@protonmail.com wrote: > >>> i upgraded from bullseye to bookworm with no problems > >>> when

Re: upgrade to bookworm broke ssh x11 forwarding

On Thu, 9 Nov 2023, Jeffrey Walton wrote: > On Thu, Nov 9, 2023 at 11:43 AM Greg Wooledge wrote: >> >> On Thu, Nov 09, 2023 at 03:01:29PM +, fxkl4...@protonmail.com wrote: >>> i upgraded from bullseye to bookworm with no problems >>> when i try ssh with -X/-Y to the bookworm machine x11 forwa

Re: upgrade to bookworm broke ssh x11 forwarding

On Thu, 9 Nov 2023, Greg Wooledge wrote: > On Thu, Nov 09, 2023 at 04:59:32PM +, fxkl4...@protonmail.com wrote: >> now it makes a bit more sense >> sshd isn't running >> for some reason the upgrade switched to dropbear >> is this a new thing for bookworm >> is there a reason i shouldn't disabl

Re: upgrade to bookworm broke ssh x11 forwarding

On Thu, Nov 9, 2023 at 11:43 AM Greg Wooledge wrote: > > On Thu, Nov 09, 2023 at 03:01:29PM +, fxkl4...@protonmail.com wrote: > > i upgraded from bullseye to bookworm with no problems > > when i try ssh with -X/-Y to the bookworm machine x11 forwarding fails > > > > debug1: Requesting X11 forw

Re: upgrade to bookworm broke ssh x11 forwarding

On Thu, Nov 09, 2023 at 04:59:32PM +, fxkl4...@protonmail.com wrote: > now it makes a bit more sense > sshd isn't running > for some reason the upgrade switched to dropbear > is this a new thing for bookworm > is there a reason i shouldn't disable dropbear and use sshd No, this is not a normal

Re: upgrade to bookworm broke ssh x11 forwarding

On Thu, 9 Nov 2023, fxkl4...@protonmail.com wrote: > On Thu, 9 Nov 2023, Greg Wooledge wrote: > >> On Thu, Nov 09, 2023 at 03:01:29PM +, fxkl4...@protonmail.com wrote: >>> i upgraded from bullseye to bookworm with no problems >>> when i try ssh with -X/-Y to the bookworm machine x11 forwarding

Re: upgrade to bookworm broke ssh x11 forwarding

On Thu, 9 Nov 2023, Greg Wooledge wrote: > On Thu, Nov 09, 2023 at 03:01:29PM +, fxkl4...@protonmail.com wrote: >> i upgraded from bullseye to bookworm with no problems >> when i try ssh with -X/-Y to the bookworm machine x11 forwarding fails >> >> debug1: Requesting X11 forwarding with authen

Re: upgrade to bookworm broke ssh x11 forwarding

On Thu, Nov 09, 2023 at 03:01:29PM +, fxkl4...@protonmail.com wrote: > i upgraded from bullseye to bookworm with no problems > when i try ssh with -X/-Y to the bookworm machine x11 forwarding fails > > debug1: Requesting X11 forwarding with authentication spoofing. > debug1: Sending environmen

Re: upgrade from bullseye to bookworm strangely fails

On Sat, Nov 04, 2023 at 04:46:25AM -0400, John Covici wrote: > Hi. So, I am trying to upgrade a server I have in the cloud from > bullseye to bookworm and it fails with the following message: > Setting up libgcc-s1:amd64 (12.2.0-14) ... > Setting up libc6:amd64 (2.36-9+deb12u3) ... > /usr/bin/perl

Re: Upgrade to Bookworm, now GNOME keyring dies--no access to stored SSH key passwords

* On 2023 14 Aug 21:29 -0500, Max Nikulin wrote: > On 14/08/2023 07:30, Nate Bargmann wrote: > > Now, while typing this email all keyring PIDs have vanished! > > It may be a way to minimize RAM usage. I don't think so. It has been persistent in the past in Buster and Bullseye with GNOME and is p

Re: upgrade to bookworm broke phpmyadmin

On 8/24/23 07:53, Stefan Monnier wrote: So, given that I purged everything and re-installed and it still didn't work, is this indeed a packaging error? I've been running Debian for well over 25 years (I started with a pre-release before buzz was released) and I don't remember anything that didn

Re: upgrade to bookworm broke phpmyadmin

> So, given that I purged everything and re-installed and it still didn't > work, is this indeed a packaging error? I've been running Debian for well > over 25 years (I started with a pre-release before buzz was released) and > I don't remember anything that didn't work after installing. I don't k

Re: upgrade to bookworm broke phpmyadmin

On 8/23/23 18:14, Dan Ritter wrote: Rick Macdonald wrote: Silly me though, I see I didn't actually describe the failure when I try to connect to localhost/phpmyadmin. The browser just opens and shows the text of the file /usr/share/phpmyadmin/index.php. Is this a clue? That generally means that

Re: upgrade to bookworm broke phpmyadmin

On 8/23/23 11:03, Michael Kjörling wrote: I don't use roundcube any more. Would it help to uninstall it? Although, at the moment I have only php5.6 and php8.2 installed. I'm guessing the bookworm upgrade removed php7.x. I imagine that uninstalling roundcube won't do anything either way. Howev

Re: upgrade to bookworm broke phpmyadmin

On 23 Aug 2023 10:52 -0600, from rickm...@shaw.ca (Rick Macdonald): > # dpkg -l php php8.2 phpmyadmin > Desired=Unknown/Install/Remove/Purge/Hold > | > Status=Not/Inst/Conf-files/Unpacked/halF-conf/Half-inst/trig-aWait/Trig-pend > |/ Err?=(none)/Reinst-required (Status,Err: uppercase=bad) > ||/ Nam

Re: upgrade to bookworm broke phpmyadmin

On 8/22/23 03:08, Michael Kjörling wrote: On 21 Aug 2023 20:00 -0600, fromrickm...@shaw.ca (Rick Macdonald): # dpkg-reconfigure phpmyadmin Determining localhost credentials from /etc/mysql/debian.cnf: succeeded. dbconfig-common: writing config to /etc/dbconfig-common/phpmyadmin.conf dbconfig-c

Re: upgrade to bookworm broke phpmyadmin

On 21 Aug 2023 20:00 -0600, from rickm...@shaw.ca (Rick Macdonald): >> # dpkg-reconfigure phpmyadmin >> Determining localhost credentials from /etc/mysql/debian.cnf: succeeded. >> dbconfig-common: writing config to /etc/dbconfig-common/phpmyadmin.conf >> dbconfig-common: flushing administrative pas

Re: Upgrade to Bookworm, now GNOME keyring dies--no access to stored SSH key passwords

On 14/08/2023 07:30, Nate Bargmann wrote: I have been using the GNOME keyring applet to manage the SSH public key passwords I use as it prompts to save passwords and then lets me SSH to other hosts without out a password prompt. I do not know how it is arranged in Gnome, but I hope my observati

Re: Upgrade to Debian 11 and still have the same problems.

On Mon 17 Jul 2023 at 10:58:43 (-0400), Default User wrote: > On Sun, 2023-07-16 at 17:21 -0400, Maureen L Thomas wrote: > > So I have been snooping around the system and found this message in > > the lshw command: > >  *-generic DISABLED > >  description: Wireless interface > >  product: RTL8821CE

Re: Upgrade to Debian 11 and still have the same problems.

On 17/07/2023 15:58, Default User wrote: On Sun, 2023-07-16 at 17:21 -0400, Maureen L Thomas wrote: So I have been snooping around the system and found this message in the lshw command:  *-generic DISABLED  description: Wireless interface  product: RTL8821CE 802.11ac PCIe Wireless Network Ada

Re: Upgrade to Debian 11 and still have the same problems.

On Sun, 2023-07-16 at 17:21 -0400, Maureen L Thomas wrote: > So I have been snooping around the system and found this message in > the lshw command: >  *-generic DISABLED >  description: Wireless interface >  product: RTL8821CE 802.11ac PCIe Wireless Network Adapter >  vendor: Realtek Semiconductor

Re: Upgrade to Debian 11 and still have the same problems.

On Sun, Jul 16, 2023 at 5:22 PM Maureen L Thomas wrote: > > So I have been snooping around the system and found this message in the lshw > command: > > *-generic DISABLED > > description: Wireless interface > > product: RTL8821CE 802.11ac PCIe Wireless Network Adapter > > vendor: Realtek Semicond

Re: Upgrade to Debian 11 and still have the same problems.

On Sun 16 Jul 2023 at 17:21:37 (-0400), Maureen L Thomas wrote: > So I have been snooping around the system and found this message in > the lshw command: > > *-generic DISABLED > description: Wireless interface > product: RTL8821CE 802.11ac PCIe Wireless Network Adapter > vendor: Realtek Semicondu

Re: Upgrade to Bookworm upon release, but now using backported kernel on Bullseye

On Mon 20 Mar 2023 at 10:37:01 -0400, Default User wrote: > Hi. > > I currently run Bullseye Stable using: > linux-image-6.0.0-0.deb11.6-amd64 6.0.12-1~bpo11+1 amd64 Linux 6.0 for > 64-bit PCs (signed) kernel. > > I plan to upgrade to Bookworm Stable shortly after release. Will I need to > do

Re: Upgrade issue with Debian 9 -> 10

On 7/5/22 04:36, Miroslav Skoric wrote: On 7/3/22 7:51 PM, David Christensen wrote: On 7/3/22 02:31, Miroslav Skoric wrote: Yesterday I attempted to upgrade Compaq Presario CQ56 laptop to buster. I followed instructions in 'Chapter 4. Upgrades from Debian 9 (stretch)', so all went well with

Re: Upgrade issue with Debian 9 -> 10

El mar, 5 jul 2022 a las 8:39, Miroslav Skoric () escribió: > > On 7/5/22 9:37 AM, Tom Dial wrote: > > > > Post the output from > > > > # fdisk -l (or $ sudo fdisk -l) > > # vgdisplay -v (or $ sudo vgdisplay -v) > > > > Here it is: > > # fdisk -l > Disk /dev/sda: 298.1 GiB, 320072933376 bytes, 6251

Re: Upgrade issue with Debian 9 -> 10

On 7/5/22 9:37 AM, Tom Dial wrote: Post the output from # fdisk -l (or $ sudo fdisk -l) # vgdisplay -v (or $ sudo vgdisplay -v) Here it is: # fdisk -l Disk /dev/sda: 298.1 GiB, 320072933376 bytes, 625142448 sectors Disk model: Hitachi HTS54323 Units: sectors of 1 * 512 = 512 bytes Sector si

Re: Upgrade issue with Debian 9 -> 10

On 7/3/22 7:51 PM, David Christensen wrote: On 7/3/22 02:31, Miroslav Skoric wrote: Hi all, Yesterday I attempted to upgrade Compaq Presario CQ56 laptop to buster. I followed instructions in 'Chapter 4. Upgrades from Debian 9 (stretch)', so all went well with a minimal upgrade (apt-get upgrad

Re: Upgrade issue with Debian 9 -> 10

On 7/3/22 4:28 PM, Miroslav Skoric wrote: Haven't tried that, but something else already helped: While it was idling with fsck in tty1, I went to tty2 and entered: apt --fix-broken install   ... and it did/resumed full upgrade. (Interestingly, this time it did not complain about no space in /

Re: Upgrade issue with Debian 9 -> 10

On 7/3/22 08:28, Miroslav Skoric wrote: ... Haven't tried that, but something else already helped: While it was idling with fsck in tty1, I went to tty2 and entered: apt --fix-broken install   ... and it did/resumed full upgrade. (Interestingly, this time it did not complain about no spa

Re: Upgrade issue with Debian 9 -> 10

On 7/3/22 02:31, Miroslav Skoric wrote: Hi all, Yesterday I attempted to upgrade Compaq Presario CQ56 laptop to buster. I followed instructions in 'Chapter 4. Upgrades from Debian 9 (stretch)', so all went well with a minimal upgrade (apt-get upgrade). When it finished, I went to the main par

Re: Upgrade issue with Debian 9 -> 10

On 7/3/22 1:17 PM, Andrew M.A. Cater wrote: Ctrl-Alt-F2 brings tty2 from where I can log in, then sudo etc. df -h shows that filesystem /dev/mapper/localhost-root (mounted on /) is 99% used, and /dev/mapper/localhost-usr (mounted on /usr) is 100% used. Apt tends to store files in /var - it's

Re: Upgrade issue with Debian 9 -> 10

On Sun, Jul 03, 2022 at 11:31:40AM +0200, Miroslav Skoric wrote: > Hi all, > > Yesterday I attempted to upgrade Compaq Presario CQ56 laptop to buster. I > followed instructions in 'Chapter 4. Upgrades from Debian 9 (stretch)', so > all went well with a minimal upgrade (apt-get upgrade). When it fi

Re: Upgrade from Buster to Bullsye: what to do about source.list for buster-backports

On Wed, Mar 30, 2022 at 19:00 Greg Wooledge wrote: > On Wed, Mar 30, 2022 at 06:53:26PM -0500, Tom Browder wrote: > > I've been following the update guide and only have one apt source.list > left > > to handle: buster-backports: Thanks so much, Greg! -Tom

Re: Upgrade from Buster to Bullsye: what to do about source.list for buster-backports

On Wed, Mar 30, 2022 at 06:53:26PM -0500, Tom Browder wrote: > I've been following the update guide and only have one apt source.list left > to handle: buster-backports: > > Do I change it to bullseye-backports or just comment the line out? Comment it out, and only add bullseye-backports (later)

Re: upgrade - packages have been kept back

On Sb, 11 dec 21, 01:54:12, teamas...@mad-hatters-teatime.teanet.org wrote: > On Fri, 10 Dec 2021 23:57:44 +0100 > Andrei POPESCU wrote: > > > On Vi, 10 dec 21, 23:39:30, teamas...@mad-hatters-teatime.teanet.org > > wrote: > > > > > > in 2 things i am pretty sure, my first mail only john doe rea

Re: upgrade - packages have been kept back

On Fri, 10 Dec 2021 23:57:44 +0100 Andrei POPESCU wrote: > On Vi, 10 dec 21, 23:39:30, teamas...@mad-hatters-teatime.teanet.org > wrote: > > > > in 2 things i am pretty sure, my first mail only john doe read > > completely, and a dist-upgrade will not work with this > > non-standard-debian. >

Re: upgrade - packages have been kept back

On Vi, 10 dec 21, 23:39:30, teamas...@mad-hatters-teatime.teanet.org wrote: > > in 2 things i am pretty sure, my first mail only john doe read > completely, and a dist-upgrade will not work with this > non-standard-debian. Based on the limited information you provided in your mail `apt-get dist-u

Re: upgrade - packages have been kept back

On Fri, 10 Dec 2021 17:41:47 + (GMT) Tim Woodall wrote: > On Fri, 10 Dec 2021, teamas...@mad-hatters-teatime.teanet.org wrote: > > > On Thu, 9 Dec 2021 23:09:34 + > > "Andrew M.A. Cater" wrote: > > > >> On Thu, Dec 09, 2021 at 11:58:33PM +0100, > >> teamas...@mad-hatters-teatime.teane

Re: upgrade - packages have been kept back

On Fri, 10 Dec 2021, teamas...@mad-hatters-teatime.teanet.org wrote: On Thu, 9 Dec 2021 23:09:34 + "Andrew M.A. Cater" wrote: On Thu, Dec 09, 2021 at 11:58:33PM +0100, teamas...@mad-hatters-teatime.teanet.org wrote: hey, i have not been using debian for long and not sure how to proceed h

Re: upgrade - packages have been kept back

On Fri, 10 Dec 2021 09:15:40 +0100 john doe wrote: > On 12/10/2021 9:04 AM, teamas...@mad-hatters-teatime.teanet.org wrote: > > On Thu, 9 Dec 2021 23:09:34 + > > "Andrew M.A. Cater" wrote: > > > >> On Thu, Dec 09, 2021 at 11:58:33PM +0100, > >> teamas...@mad-hatters-teatime.teanet.org wrot

Re: upgrade - packages have been kept back

Hi. On Fri, Dec 10, 2021 at 09:04:25AM +0100, teamas...@mad-hatters-teatime.teanet.org wrote: > On Thu, 9 Dec 2021 23:09:34 + > "Andrew M.A. Cater" wrote: > > > On Thu, Dec 09, 2021 at 11:58:33PM +0100, > > teamas...@mad-hatters-teatime.teanet.org wrote: > > > hey, > > > i have not

Re: upgrade - packages have been kept back

On 12/10/2021 9:04 AM, teamas...@mad-hatters-teatime.teanet.org wrote: On Thu, 9 Dec 2021 23:09:34 + "Andrew M.A. Cater" wrote: On Thu, Dec 09, 2021 at 11:58:33PM +0100, teamas...@mad-hatters-teatime.teanet.org wrote: hey, i have not been using debian for long and not sure how to proceed

Re: upgrade - packages have been kept back

On Thu, 9 Dec 2021 23:09:34 + "Andrew M.A. Cater" wrote: > On Thu, Dec 09, 2021 at 11:58:33PM +0100, > teamas...@mad-hatters-teatime.teanet.org wrote: > > hey, > > i have not been using debian for long and not sure how to proceed > > here. is a: > > apt-get upgrade linux-image-amd64 > > the r

Re: upgrade - packages have been kept back

On Thu, Dec 09, 2021 at 11:58:33PM +0100, teamas...@mad-hatters-teatime.teanet.org wrote: > root@saira:~# apt-get upgrade > Reading package lists... Done > Building dependency tree > Reading state information... Done > Calculating upgrade... Done > The following packages have been kept back

Re: upgrade - packages have been kept back

On Thu, Dec 09, 2021 at 11:58:33PM +0100, teamas...@mad-hatters-teatime.teanet.org wrote: > hey, > i have not been using debian for long and not sure how to proceed here. > is a: > apt-get upgrade linux-image-amd64 > the right way? > ty, jens. apt-get update ; apt-get upgrade [You need to pull i

Re: Upgrade testing to unstable but debian_version and os-release not changing to sid

On 17/08/2021 15:50, David Wright wrote: > On Tue 17 Aug 2021 at 10:46:49 (+0100), Peter Hillier-Brook wrote: >> On 17/08/2021 02:21, Robbi Nespu wrote: >>> I have been using debian testing (bullseye) for 1 year (plus) and I want >>> to use sid as my daily driver. >>> >>> I change source.list to si

Re: Upgrade testing to unstable but debian_version and os-release not changing to sid

On Tue 17 Aug 2021 at 10:46:49 (+0100), Peter Hillier-Brook wrote: > On 17/08/2021 02:21, Robbi Nespu wrote: > > I have been using debian testing (bullseye) for 1 year (plus) and I want > > to use sid as my daily driver. > > > > I change source.list to sid > >     $ cat /etc/apt/sources.list > >  

Re: Upgrade testing to unstable but debian_version and os-release not changing to sid

On 17/08/2021 02:21, Robbi Nespu wrote: > I have been using debian testing (bullseye) for 1 year (plus) and I want > to use sid as my daily driver. > > I change source.list to sid >     $ cat /etc/apt/sources.list >     deb http://ftp.jp.debian.org/debian/ sid main contrib non-free >     deb-src h

Re: Upgrade testing to unstable but debian_version and os-release not changing to sid

That great knowing it nothing wrong.. well then I just wait, since it nothing much and my source.list is correct -- Robbi Nespu D311 B5FF EEE6 0BE8 9C91 FA9E 0C81 FA30 3B3A 80BA https://robbinespu.gitlab.io | https://mstdn.social/@robbinespu

Re: Upgrade testing to unstable but debian_version and os-release not changing to sid

On Mon 16 Aug 2021 at 21:47:08 (-0400), Greg Wooledge wrote: > On Tue, Aug 17, 2021 at 09:21:52AM +0800, Robbi Nespu wrote: > > $ cat /etc/debian_version > > 11.0 > > > > $ cat /etc/os-release > > PRETTY_NAME="Debian GNU/Linux 11 (bullseye)" > > NAME="Debian GNU/Linux" > >

Re: Upgrade testing to unstable but debian_version and os-release not changing to sid

On Tue, Aug 17, 2021 at 09:21:52AM +0800, Robbi Nespu wrote: > $ cat /etc/debian_version > 11.0 > > $ cat /etc/os-release > PRETTY_NAME="Debian GNU/Linux 11 (bullseye)" > NAME="Debian GNU/Linux" > VERSION_ID="11" > VERSION="11 (bullseye)" > VERSION_CODENAME=bullseye

Re: Upgrade from buster........

On Sun, 15 Aug 2021 10:32:01 -0400 Greg Informed me about Re: Upgrade from buster > On Sun, Aug 15, 2021 at 02:34:59PM +1000, Charlie wrote: > > But didn't upgrade because of failure running > > /usr/sbin/apt-listbugs apt > > I'm w

Re: Upgrade from buster........

On Sun, Aug 15, 2021 at 02:34:59PM +1000, Charlie wrote: > But didn't upgrade because of failure running > /usr/sbin/apt-listbugs apt I'm wondering if the failures of apt-listbugs are related to the failure of the bugs.debian.org web site. It's gotta be related, right? In your particular case, t

Re: Upgrade problems?

Adding this up here as a quick read: If this was installation via debs, I'm out of the conversation. If it was about untarring [zipped files] and you can repeatedly reproduce the issue now that you have seen this, PLEASE don't share the package name(s) publicly. They could be... dissected and then

Re: Upgrade problems?

On 7/21/21, Tixy wrote: > On Wed, 2021-07-21 at 12:04 -0400, Frank McCormick wrote: >> On 2021-07-21 10:52 a.m., Kushal Kumaran wrote: >> >> frank@fedora ~$ stat / >>File: / >>Size: 4096Blocks: 8 IO Block: 4096 directory >> Device: 806h/2054d Inode: 2 Li

Re: Upgrade problems?

On 7/21/21 12:24 PM, Greg Wooledge wrote: On Wed, Jul 21, 2021 at 12:04:13PM -0400, Frank McCormick wrote: frank@fedora ~$ stat /   File: /   Size: 4096    Blocks: 8  IO Block: 4096 directory Device: 806h/2054d  Inode: 2   Links: 18 Access: (0555/dr-xr-xr-x)  Uid

Re: Upgrade problems?

On Wed, Jul 21, 2021, 12:57 PM Greg Wooledge wrote: > On Wed, Jul 21, 2021 at 12:39:49PM -0400, Kenneth Parker wrote: > > > > Access: (0555/dr-xr-xr-x) Uid: (0/root) Gid: ( 1000/ frank) > > > Actually, access 555 means everyone can Read and Execute, but nobody can > > Update. > > > > R

Re: Upgrade problems?

On Wed, Jul 21, 2021 at 12:39:49PM -0400, Kenneth Parker wrote: > > Access: (0555/dr-xr-xr-x) Uid: (0/root) Gid: ( 1000/ frank) > Actually, access 555 means everyone can Read and Execute, but nobody can > Update. > > Root usually overrides that, which could explain why it still works.

Re: Upgrade problems?

On Wed, Jul 21, 2021, 12:12 PM Frank McCormick wrote: > On 2021-07-21 10:52 a.m., Kushal Kumaran wrote: > > > On Wed, Jul 21 2021 at 09:26:41 AM, Frank McCormick < > debianl...@videotron.ca> wrote: > >> Got a bunch of strange errors during this morning upgrade of Bullseye. > >> > >> > >> Setting

Re: Upgrade problems?

On Wed, 2021-07-21 at 12:04 -0400, Frank McCormick wrote: > On 2021-07-21 10:52 a.m., Kushal Kumaran wrote: > > > On Wed, Jul 21 2021 at 09:26:41 AM, Frank McCormick > > wrote: > > > Got a bunch of strange errors during this morning upgrade of Bullseye. > > > > > > > > > Setting up systemd (24

Re: Upgrade problems?

On Wed, Jul 21, 2021 at 12:04:13PM -0400, Frank McCormick wrote: > frank@fedora ~$ stat / >   File: / >   Size: 4096    Blocks: 8  IO Block: 4096 directory > Device: 806h/2054d  Inode: 2   Links: 18 > Access: (0555/dr-xr-xr-x)  Uid: (    0/    root)   Gid: ( 1000/ frank)

Re: Upgrade problems?

On 2021-07-21 10:52 a.m., Kushal Kumaran wrote: On Wed, Jul 21 2021 at 09:26:41 AM, Frank McCormick wrote: Got a bunch of strange errors during this morning upgrade of Bullseye. Setting up systemd (247.3-6) ... Detected unsafe path transition / → /run during canonicalization of /run. Detect

Re: Upgrade problems?

On Wed, Jul 21 2021 at 09:26:41 AM, Frank McCormick wrote: > Got a bunch of strange errors during this morning upgrade of Bullseye. > > > Setting up systemd (247.3-6) ... Detected unsafe path transition / → > /run during canonicalization of /run. Detected unsafe path transition > / → /run during

  1   2   3   4   5   6   7   8   9   10   >