Re: Upgrading systemd may silently break your Unstable/Sid system!

2024-07-28 Thread David Wright
On Sun 28 Jul 2024 at 09:45:44 (-0500), allan wrote: > I've run Sid exclusively for years; the last time I broke it badly > enough to justify a reinstall was in 2013 and that was for not paying > attention during an upgrade :) > > My heartburn is I would have expected to see this change in a > ch

Re: Upgrading systemd may silently break your Unstable/Sid system!; was: systemd may silently break your system!

2024-07-28 Thread David Wright
On Mon 29 Jul 2024 at 09:23:16 (+0700), Max Nikulin wrote: > On 28/07/2024 20:08, Erwan David wrote: > > I also have a 99-systcl.conf which is a copy of the former /etc/sysctl.conf > > When you are going to replace a file provided by a package, check if > it is a configuration file at first (e.g.

Re: Upgrading systemd may silently break your Unstable/Sid system!; was: systemd may silently break your system!

2024-07-28 Thread Max Nikulin
On 28/07/2024 20:08, Erwan David wrote: I also have a 99-systcl.conf which is a copy of the former /etc/sysctl.conf When you are going to replace a file provided by a package, check if it is a configuration file at first (e.g. dpkg -s). Despite most of files in /etc/ are marked as configurati

Re: Upgrading systemd may silently break your Unstable/Sid system!

2024-07-28 Thread Vincent Lefevre
On 2024-07-28 20:01:35 -0400, Greg Wooledge wrote: > In the interests of posting something *useful*, here's a timeline. > As I understand it, here's what's happened so far: > > 2024-06-23: bug #1074156 filed against package procps > procps: Depend or Recommend linux-sysctl-defaults > Bug f

Re: Upgrading systemd may silently break your Unstable/Sid system!

2024-07-28 Thread Greg Wooledge
On Mon, Jul 29, 2024 at 01:13:10 +0200, Vincent Lefevre wrote: > On 2024-07-28 14:13:09 +, Michael Kjörling wrote: > > And posting on debian-user with a bombastic Subject line which implies > > that this is a widespread issue when it really only seems to exist in > > Unstable is, quite frankly,

Re: Upgrading systemd may silently break your Unstable/Sid system!

2024-07-28 Thread Vincent Lefevre
On 2024-07-28 14:13:09 +, Michael Kjörling wrote: > And posting on debian-user with a bombastic Subject line which implies > that this is a widespread issue when it really only seems to exist in > Unstable is, quite frankly, in my opinion at best dishonest. No, the breakage was done *on purpos

Re: Upgrading systemd may silently break your Unstable/Sid system!

2024-07-28 Thread allan
I've run Sid exclusively for years; the last time I broke it badly enough to justify a reinstall was in 2013 and that was for not paying attention during an upgrade :) My heartburn is I would have expected to see this change in a changelog and apt-listchanges didn't say a word about this. As far

Re: Upgrading systemd may silently break your Unstable/Sid system!

2024-07-28 Thread The Wanderer
On 2024-07-28 at 10:13, Michael Kjörling wrote: > On 28 Jul 2024 15:08 +0200, from er...@rail.eu.org (Erwan David): >> Le 28/07/2024 à 14:28, allan a écrit : >>> I would agree with you *if* the change had been publicized. >> >> [...] But in my view it is a bug to remove something else than the >>

Re: Upgrading systemd may silently break your Unstable/Sid system!

2024-07-28 Thread Michael Kjörling
On 28 Jul 2024 15:08 +0200, from er...@rail.eu.org (Erwan David): > Le 28/07/2024 à 14:28, allan a écrit : >> I would agree with you *if* the change had been publicized. > > [...] But in my view it is a bug to remove something else than > the symlink even with the same name At the risk of repeati

Re: Upgrading systemd may silently break your Unstable/Sid system!; was: systemd may silently break your system!

2024-07-28 Thread Erwan David
Le 28/07/2024 à 14:28, allan a écrit : I would agree with you *if* the change had been publicized. I found the 99-sysctl.conf symlink accidentally. I removed the symlink and moved sysctl.conf to 99-sysctl.conf since the original config was not being read. This turned out to be a lousy idea sin

Re: Upgrading systemd may silently break your Unstable/Sid system!; was: systemd may silently break your system!

2024-07-28 Thread allan
I would agree with you *if* the change had been publicized. I found the 99-sysctl.conf symlink accidentally. I removed the symlink and moved sysctl.conf to 99-sysctl.conf since the original config was not being read. This turned out to be a lousy idea since the symlink was removed with the next

Re: Upgrading systemd may silently break your Unstable/Sid system!; was: systemd may silently break your system!

2024-07-28 Thread Michael Kjörling
On 28 Jul 2024 04:25 +0200, from vinc...@vinc17.net (Vincent Lefevre): >> A conffile is user-managed, so any changes you make to a conffile must >> be respected by the package. It can't just overwrite your changes, or >> restore a conffile if you've deleted it. > > This is rather poor design, bec

Re: Upgrading Buster LTS (10) to Bookworm (current stable) concerns

2024-06-17 Thread Jeffrey Walton
On Mon, Jun 17, 2024 at 3:38 AM Nick Sal wrote: > > I plan to upgrade a server running Buster to Bookworm. > Server is running: {web,mail} servers, mysql and postregre, docker, ssh, > ldap, ferm (firewall), and few other non-critical services. > > I'd like to appeal to your experience for a coupl

Re: Upgrading Buster LTS (10) to Bookworm (current stable) concerns

2024-06-17 Thread Michael Kjörling
On 17 Jun 2024 03:41 +, from specialrou...@proton.me (Nick Sal): > 1) Should I upgrade in two steps from Buster to Bullseye > (oldstable), and then to Bookworm? Or should I go directly from > Buster to Bookworm in one step? > The upgrade will be done by changing sources.list NEVER skip major

Re: Upgrading binary: nginx

2021-10-02 Thread Reco
Hi. On Sat, Oct 02, 2021 at 12:03:36PM +0200, pk wrote: > I got this message when installing nginx-light today. What does it > mean and where does it come from? I could not grep it in the > nginx-light .deb. It's the usual nginx behaviour on restart. Instead of shutting down nginx complet

Re: Upgrading buster => bullseye. Canonicalization of /var/log/journal.

2021-10-02 Thread Andrei POPESCU
On Mi, 29 sep 21, 07:05:37, pe...@easthope.ca wrote: > From: Greg Wooledge > Date: Tue, 28 Sep 2021 13:41:05 -0400 > > What does it look like? > > > > ls -ld / /var /var/log /var/log/journal > > root@joule:/# ls -ld / /var /var/log > drwxr-xr-x 18 peter peter 4096 Sep 27 18:00 / > drwxr-

Re: Upgrading buster => bullseye. Canonicalization of /var/log/journal.

2021-10-01 Thread Kushal Kumaran
On Wed, Sep 29 2021 at 10:35:35 PM, David Wright wrote: > On Wed 29 Sep 2021 at 16:46:14 (-0400), Greg Wooledge wrote: >> On Wed, Sep 29, 2021 at 07:05:37AM -0700, pe...@easthope.ca wrote: >> > From: Greg Wooledge >> > Date: Tue, 28 Sep 2021 13:41:05 -0400 >> > > What does it look like?

Re: Upgrading buster => bullseye. Canonicalization of /var/log/journal.

2021-09-30 Thread Greg Wooledge
On Wed, Sep 29, 2021 at 10:35:35PM -0500, David Wright wrote: > Would it be sensible for the message to actually mention ownership, > or can it apply to very different circumstances (beyond permissions, > that is)? I've failed to find any other cause, but see a lot of > people messing up their owne

Re: Upgrading buster => bullseye. Canonicalization of /var/log/journal.

2021-09-29 Thread Nils
>From my experience gnome-disks automatically chowns / to the executing user >when creating a filesystem. But I don't think Peter did that. I'd rather say it's been caused by some installation script, those are usually buggy when it comes to file ownership. Peter, did you install anything via a .

Re: Upgrading buster => bullseye. Canonicalization of /var/log/journal.

2021-09-29 Thread David Wright
On Wed 29 Sep 2021 at 16:46:14 (-0400), Greg Wooledge wrote: > On Wed, Sep 29, 2021 at 07:05:37AM -0700, pe...@easthope.ca wrote: > > From: Greg Wooledge > > Date: Tue, 28 Sep 2021 13:41:05 -0400 > > > What does it look like? > > > > > > ls -ld / /var /var/log /var/log/journal > > > > ro

Re: Upgrading buster => bullseye. Canonicalization of /var/log/journal.

2021-09-29 Thread Charles Curley
On Wed, 29 Sep 2021 08:01:00 -0700 pe...@easthope.ca wrote: > root@joule:~# cat /etc/apt/sources.list > #deb http://mirror.it.ubc.ca/debian/ bullseye main > deb http://mirror.it.ubc.ca/debian/ bullseye main contrib non-free > deb-src http://mirror.it.ubc.ca/debian/ bullseye main contrib non-fr

Re: Upgrading buster => bullseye. Canonicalization of /var/log/journal. APPEARS SOLVED.

2021-09-29 Thread Greg Wooledge
On Wed, Sep 29, 2021 at 02:35:10PM -0700, pe...@easthope.ca wrote: > I can't explain why / was owned by me. According to the above it > happened in the release upgrade two days ago. No, that's not what that timestamp says. The timestamp in "ls -ld" is the modification time (mtime) on the direct

Re: Upgrading buster => bullseye. Canonicalization of /var/log/journal. APPEARS SOLVED.

2021-09-29 Thread peter
From: Nils Date: Tue, 28 Sep 2021 17:16:30 + > Are you sure you still need these journals? I don't know. > ... my way to work around it would be to just delete those logs. Did that and rebooted. System behaviour unchanged. APPARENT SOLUTION root@joule:/home/peter# ls -ld / /var

Re: Upgrading buster => bullseye. Canonicalization of /var/log/journal.

2021-09-29 Thread Greg Wooledge
On Wed, Sep 29, 2021 at 07:05:37AM -0700, pe...@easthope.ca wrote: > From: Greg Wooledge > Date: Tue, 28 Sep 2021 13:41:05 -0400 > > What does it look like? > > > > ls -ld / /var /var/log /var/log/journal > > root@joule:/# ls -ld / /var /var/log > drwxr-xr-x 18 peter peter 4096 Sep 27 18

Re: Upgrading buster => bullseye. Canonicalization of /var/log/journal.

2021-09-29 Thread peter
From: Nils Date: Tue, 28 Sep 2021 17:16:30 + > Are you sure you still need these journals? I don't know. > ... my way to work around it would be to just delete those logs. Did that and rebooted. System behaviour is unchanged. plymouth-label was the last package reported unconfigu

Re: Upgrading buster => bullseye. Canonicalization of /var/log/journal.

2021-09-29 Thread peter
From: Greg Wooledge Date: Tue, 28 Sep 2021 13:41:05 -0400 > What does it look like? > > ls -ld / /var /var/log /var/log/journal root@joule:/# ls -ld / /var /var/log drwxr-xr-x 18 peter peter 4096 Sep 27 18:00 / drwxr-xr-x 11 root root 4096 Nov 3 2020 /var drwxr-xr-x 10 root root 40

Re: Upgrading buster => bullseye. Canonicalization of /var/log/journal.

2021-09-28 Thread Greg Wooledge
On Tue, Sep 28, 2021 at 06:33:52PM +, Andrew M.A. Cater wrote: > On Tue, Sep 28, 2021 at 08:55:59AM -0700, pe...@easthope.ca wrote: > > Errors were encountered while processing: > > systemd > > libpam-systemd:i386 > > policykit-1 > > policykit-1-gnome > > plymouth > > mate-polkit:i386 > >

Re: Upgrading buster => bullseye. Canonicalization of /var/log/journal.

2021-09-28 Thread Andrew M.A. Cater
On Tue, Sep 28, 2021 at 08:55:59AM -0700, pe...@easthope.ca wrote: > Hi, > Here the upgrade was completed except for the problem indicated in the > following transcript. > > This page appears relevant. > https://manpages.debian.org/stretch/systemd/systemd-journald.service.8.en.html > > /var/log/

Re: Upgrading buster => bullseye. Canonicalization of /var/log/journal.

2021-09-28 Thread Greg Wooledge
On Tue, Sep 28, 2021 at 08:55:59AM -0700, pe...@easthope.ca wrote: > Hi, > Here the upgrade was completed except for the problem indicated in the > following transcript. > > This page appears relevant. > https://manpages.debian.org/stretch/systemd/systemd-journald.service.8.en.html > > /var/log/

Re: Upgrading buster => bullseye. Canonicalization of /var/log/journal.

2021-09-28 Thread Nils
Hi, Are you sure you still need these journals? Might be some nasty bug and my way to work around it would be to just delete those logs. I mean, it's kind of a hacky solution but I'm absolutely sure this allows the upgrade to continue. Hope it's a viable solution to you, Tuxifan Am 28. Septembe

Re: upgrading and stuff

2021-09-27 Thread Roy J. Tellason, Sr.
On Sunday 26 September 2021 01:59:05 pm Andrew M.A. Cater wrote: > Follow the clues form the blog below: > > https://economictheoryblog.com/2015/11/08/how-to-enable-gui-root-login-in-debian-8/ > > Edit /etc/gdm3/daemon.conf and add > > AllowRoot=true under [security] > > Then edit /etc/pam.d/g

Re: upgrading and stuff

2021-09-26 Thread Andrew M.A. Cater
On Sun, Sep 26, 2021 at 01:03:26PM -0400, Roy J. Tellason, Sr. wrote: > On Saturday 25 September 2021 06:36:34 pm Dan Ritter wrote: > > If the system will not let you login as root from the graphical > > display manager, it's the GDM's fault. It may be a configurable > > option in its /etc/whatever

Re: upgrading and stuff

2021-09-26 Thread Brian
On Sun 26 Sep 2021 at 13:03:26 -0400, Roy J. Tellason, Sr. wrote: > On Saturday 25 September 2021 06:36:34 pm Dan Ritter wrote: > > If the system will not let you login as root from the graphical > > display manager, it's the GDM's fault. It may be a configurable > > option in its /etc/whateverdm.

Re: upgrading and stuff

2021-09-26 Thread Andrew M.A. Cater
On Sun, Sep 26, 2021 at 12:48:37PM -0400, Roy J. Tellason, Sr. wrote: Hi Roy, > On Saturday 25 September 2021 06:08:23 pm Andy Smith wrote: > > The release of the three newer stable versions of Debian seems to have > > happened without you noticing. > > Life has handed me a whole mess of thing

Re: upgrading and stuff

2021-09-26 Thread Roy J. Tellason, Sr.
On Saturday 25 September 2021 06:36:34 pm Dan Ritter wrote: > If the system will not let you login as root from the graphical > display manager, it's the GDM's fault. It may be a configurable > option in its /etc/whateverdm. If not, you can always replace a > recalcitrant GDM with original xdm, whi

Re: upgrading and stuff

2021-09-26 Thread Roy J. Tellason, Sr.
On Saturday 25 September 2021 06:08:23 pm Andy Smith wrote: > The release of the three newer stable versions of Debian seems to have > happened without you noticing. Life has handed me a whole mess of things to deal with over the past year or two... > If you remain subscribed to this mailing l

Re: upgrading and stuff

2021-09-26 Thread Andrei POPESCU
On Sb, 25 sep 21, 22:08:23, Andy Smith wrote: > > On Sat, Sep 25, 2021 at 05:07:46PM -0400, Roy J. Tellason, Sr. wrote: > > > The only thing that works there is to log in as a regular user, > > and then use the su command to get there. A bit of a pain. Where > > in the software is this controll

Re: upgrading and stuff

2021-09-26 Thread Tim Woodall
On Sat, 25 Sep 2021, Andy Smith wrote: Hi, On Sat, Sep 25, 2021 at 06:22:17PM -0400, songbird wrote: Roy J. Tellason, Sr. wrote: [Upgrading from Debian 8.11] don't waste any more time trying to upgrade from a version that ancient. I've done 8 to 10 (by way of 9) on ten different machin

Re: upgrading and stuff

2021-09-25 Thread Andy Smith
Hi, On Sat, Sep 25, 2021 at 06:22:17PM -0400, songbird wrote: > Roy J. Tellason, Sr. wrote: [Upgrading from Debian 8.11] > don't waste any more time trying to upgrade from a version that > ancient. I've done 8 to 10 (by way of 9) on ten different machines in the year preceding the 11 release

Re: upgrading and stuff

2021-09-25 Thread Dan Ritter
Roy J. Tellason, Sr. wrote: > Lots of differences! systemd instead of init, grub instead of LILO, and > probably many more than I'd want to list here. As it turns out, these are just the defaults. > I haven't been paying a whole lot of attention to upgrades. Mostly > it's been a matter of r

Re: upgrading and stuff

2021-09-25 Thread songbird
Roy J. Tellason, Sr. wrote: ... > For whatever it's worth, I have no problems with a text-based login screen > and then typing startx once I've logged in, which is pretty typical of my > Slackware installations anyhow. The copy of Slackware that's running my > server machine doesn't even have

Re: upgrading and stuff

2021-09-25 Thread Andy Smith
Hi Roy, On Sat, Sep 25, 2021 at 05:07:46PM -0400, Roy J. Tellason, Sr. wrote: > I haven't been paying a whole lot of attention to upgrades. > Mostly it's been a matter of running synaptic package manager from > time to time, and that's about it. Except that lately it doesn't > seem to be finding

Re: Upgrading to Bullseye?

2021-05-27 Thread Cindy Sue Causey
On 5/27/21, Greg Wooledge wrote: > On Thu, May 27, 2021 at 08:30:16AM -0700, latincom wrote: >> Thank you >> >> Here is the mistake: >> >> deb http://security.debian.org/debian-security bullseye-security main >> contrib non-free >> >> deb http://security.debian.org/debian-security buster/updates m

Re: Upgrading to Bullseye?

2021-05-27 Thread latincom
> On Thu, May 27, 2021 at 05:45:33AM -0700, latin...@vcn.bc.ca wrote: >> Hello list >> >> can somebody help with the correct sources.lst Bullseye please? > > How do yours look at the moment? > > Cheers > - t > deb http://deb.debian.org/debian/ buster main non-free contrib # deb-src http://deb.deb

Re: Upgrading to Bullseye?

2021-05-27 Thread Greg Wooledge
On Thu, May 27, 2021 at 08:30:16AM -0700, latincom wrote: > Thank you > > Here is the mistake: > > deb http://security.debian.org/debian-security bullseye-security main > contrib non-free > > deb http://security.debian.org/debian-security buster/updates main contrib > non-free Yes, the format f

Re: Upgrading to Bullseye?

2021-05-27 Thread latincom
Thank you Here is the mistake: deb http://security.debian.org/debian-security bullseye-security main contrib non-free deb http://security.debian.org/debian-security buster/updates main contrib non-free

Re: Upgrading to Bullseye?

2021-05-27 Thread tomas
On Thu, May 27, 2021 at 09:32:08AM -0400, Kenneth Parker wrote: [...] > > You may also need to add bullseye-backports later, but you can worry > > about those later, if you need them. > > > > I only use Backports, if needed for a particular product. AFAIK, by default backports have a lower prio

Re: Upgrading to Bullseye?

2021-05-27 Thread Peter Ehlert
On 5/27/21 5:45 AM, latin...@vcn.bc.ca wrote: Hello list can somebody help with the correct sources.lst Bullseye please? that's kinda complicated, as the others have already said 1. I suggest you review this, lots of info https://wiki.debian.org/DebianTesting 2. probably a fresh install

Re: Upgrading to Bullseye?

2021-05-27 Thread Kenneth Parker
On Thu, May 27, 2021, 9:12 AM Greg Wooledge wrote: > On Thu, May 27, 2021 at 05:45:33AM -0700, latin...@vcn.bc.ca wrote: > > Hello list > > > > can somebody help with the correct sources.lst Bullseye please? > > There are several correct answers, depending on what you want. > > If you intend to *

Re: Upgrading to Bullseye?

2021-05-27 Thread tomas
On Thu, May 27, 2021 at 05:45:33AM -0700, latin...@vcn.bc.ca wrote: > Hello list > > can somebody help with the correct sources.lst Bullseye please? How do yours look at the moment? Cheers - t signature.asc Description: Digital signature

Re: Upgrading to Bullseye?

2021-05-27 Thread Greg Wooledge
On Thu, May 27, 2021 at 05:45:33AM -0700, latin...@vcn.bc.ca wrote: > Hello list > > can somebody help with the correct sources.lst Bullseye please? There are several correct answers, depending on what you want. If you intend to *stay* on bullseye when it becomes stable, then I would go with: d

Re: upgrading firefox-esr from 78.6 to 78.9 results in non-working firefox

2021-04-12 Thread Eric S Fraga
On Sunday, 11 Apr 2021 at 12:05, Andrew M.A. Cater wrote: > As suggested elsewhere: Testing is currently frozen, relatively few changes > happening. If this is a computer you rely on absolutely, you might want to > make sure that all the entries in your /etc/apt/sources.list point to bullseye > at

Re: upgrading firefox-esr from 78.6 to 78.9 results in non-working firefox

2021-04-11 Thread Andrew M.A. Cater
On Sun, Apr 11, 2021 at 01:48:09PM +0200, Erwan David wrote: > Le 11/04/2021 à 13:33, Eric S Fraga a écrit : > > On Saturday, 10 Apr 2021 at 13:18, David Wright wrote: > >> "my system (mostly Debian testing)" > > For clarity, it's testing but has a couple of packages from elsewhere > > (MS Team

Re: upgrading firefox-esr from 78.6 to 78.9 results in non-working firefox

2021-04-11 Thread Erwan David
Le 11/04/2021 à 13:33, Eric S Fraga a écrit : > On Saturday, 10 Apr 2021 at 13:18, David Wright wrote: >> "my system (mostly Debian testing)" > For clarity, it's testing but has a couple of packages from elsewhere > (MS Teams, Zoom) due to the fun times we are in... For some reason, my > compu

Re: upgrading firefox-esr from 78.6 to 78.9 results in non-working firefox

2021-04-11 Thread Eric S Fraga
On Saturday, 10 Apr 2021 at 13:08, David Wright wrote: > My reaction upon reading this is that perhaps you should change your > priorities slightly. Yes, I understand where you are coming from. I do follow security advisories and upgrade specific packages. I do periodically upgrade all packages,

Re: upgrading firefox-esr from 78.6 to 78.9 results in non-working firefox

2021-04-11 Thread Eric S Fraga
On Saturday, 10 Apr 2021 at 10:05, David Christensen wrote: > When I want to upgrade, re-install, or install packages, I start with > 'apt-get update'. Yes, did that. > I would have done 'apt-get upgrade ...' instead of 'apt install > ...'. I then reboot. Not sure if you are saying to upgrade a

Re: upgrading firefox-esr from 78.6 to 78.9 results in non-working firefox

2021-04-11 Thread Eric S Fraga
On Saturday, 10 Apr 2021 at 13:18, David Wright wrote: > "my system (mostly Debian testing)" For clarity, it's testing but has a couple of packages from elsewhere (MS Teams, Zoom) due to the fun times we are in... For some reason, my computer seems to think I am running bullseye/sid (contents

Re: upgrading firefox-esr from 78.6 to 78.9 results in non-working firefox

2021-04-11 Thread Eric S Fraga
On Saturday, 10 Apr 2021 at 14:21, Linux-Fan wrote: > Did you try to completely stop all of the previous version's processes? Yes, I had quit firefox and also added 'pkill firefox-esr' for good measure. I will try upgrading firefox-esr again and make triply sure everything is gone before starting

Re: upgrading firefox-esr from 78.6 to 78.9 results in non-working firefox

2021-04-10 Thread Greg Wooledge
On Sat, Apr 10, 2021 at 10:05:23AM -0700, David Christensen wrote: > I have not figured out the difference between apt(8) and apt-get(8). It > looks like the former uses the latter as a back-end (?). Not quite. They both use the same libraries to do the actual work, but one does not actually exe

Re: upgrading firefox-esr from 78.6 to 78.9 results in non-working firefox

2021-04-10 Thread David Wright
On Sat 10 Apr 2021 at 10:05:23 (-0700), David Christensen wrote: > On 4/10/21 4:59 AM, Eric S Fraga wrote: > > > ... I did 'apt update' and 'apt install firefox-esr' to upgrade from > > version 78.6 to version 78.9. > > I have not figured out the difference between apt(8) and apt-get(8). > It loo

Re: upgrading firefox-esr from 78.6 to 78.9 results in non-working firefox

2021-04-10 Thread David Wright
On Sat 10 Apr 2021 at 12:59:12 (+0100), Eric S Fraga wrote: > > I don't frequently upgrade if my system (mostly Debian testing) is > working but my bank told me that my browser was out of date and I needed > to upgrade. > > So, I did 'apt update' and 'apt install firefox-esr' to upgrade from > ve

Re: upgrading firefox-esr from 78.6 to 78.9 results in non-working firefox

2021-04-10 Thread David Christensen
On 4/10/21 4:59 AM, Eric S Fraga wrote: ... I did 'apt update' and 'apt install firefox-esr' to upgrade from version 78.6 to version 78.9. I have not figured out the difference between apt(8) and apt-get(8). It looks like the former uses the latter as a back-end (?). I use apt-get(8).

Re: upgrading firefox-esr from 78.6 to 78.9 results in non-working firefox

2021-04-10 Thread tomas
On Sat, Apr 10, 2021 at 02:21:13PM +0200, Linux-Fan wrote: [...] > Did you try to completely stop all of the previous version's processes? > > With new Firefox updates I frequently observe that the already > running old version "disintegrates" [...] Very polite way to put it :) Yes, that's my

Re: upgrading firefox-esr from 78.6 to 78.9 results in non-working firefox

2021-04-10 Thread Linux-Fan
Eric S Fraga writes: Hello all, I don't frequently upgrade if my system (mostly Debian testing) is working but my bank told me that my browser was out of date and I needed to upgrade. So, I did 'apt update' and 'apt install firefox-esr' to upgrade from version 78.6 to version 78.9. Start up t

Re: Upgrading python3.8 from 3.8.3-1 to 3.8.4~rc1-1 breaks xpra

2020-07-24 Thread S. Dash
Thanks Jörg snapshot.debian.org was a great help! Though I had trouble with apt to deal with the downgrade with depedencies, aptitude's interactive UI helped a lot. As for the xpra issue, it seemed to be something about xpra itself. I just found xpra was somehow not in the repo anymore. https:

Re: Upgrading python3.8 from 3.8.3-1 to 3.8.4~rc1-1 breaks xpra

2020-07-15 Thread Jörg-Volker Peetz
S. Dash wrote on 15/07/2020 10:02: > 2. > > Apart from this issue, I just realized that I was unable to downgrade to 3.8.3 > if I had not cached the deb files. All mirror sites I could find were all > updated to have only 3.8.4~rc1-1. Is there an archive that keeps older > versions? > Yes, ther

Re: upgrading only Emacs in LTS

2019-11-08 Thread 황병희
Sivaram Neelakantan writes: > I'd like to upgrade Emacs to the 26.x series and only that and it's > dependencies. Is there a way to do that? A search on the web showed > some confusing instructions. Below are, hopefully, enough information > for any suggestions. > > user1@DESKTOP:~$ cat /etc/

Re: upgrading only Emacs in LTS

2019-11-07 Thread Henning Follmann
On Thu, Nov 07, 2019 at 10:39:41PM +0530, Sivaram Neelakantan wrote: > > I'd like to upgrade Emacs to the 26.x series and only that and it's > dependencies. Is there a way to do that? A search on the web showed > some confusing instructions. Below are, hopefully, enough information > for any su

Re: Upgrading from Debian 9 to Debian 10, binary format confusion

2019-10-22 Thread David
On Tue, 22 Oct 2019 at 18:14, John Conover wrote: > > I installed debian-live-10.1.0-amd64-xfce.iso from > https://cdimage.debian.org/debian-cd/current-live/amd64/iso-hybrid/ > > Programs compiled on Debian 9, Amd64, fail to execute, with a wrong > binary format error.[1] If you don't provide the

Re: Upgrading point release from 10 to 10.1

2019-09-20 Thread Gene Heskett
On Friday 20 September 2019 12:42:16 deloptes wrote: > Gene Heskett wrote: > > I have to play Sam Elliot here, John, reminding us that it took a > > special kind of stupid to elect what we did elect in the last poll. > > But Gene, it was not hard given the alternative. I still think it is > the le

Re: Upgrading point release from 10 to 10.1

2019-09-20 Thread deloptes
Gene Heskett wrote: > I have to play Sam Elliot here, John, reminding us that it took a special > kind of stupid to elect what we did elect in the last poll. But Gene, it was not hard given the alternative. I still think it is the less evil what you and we got :| In fact I can't remember when wa

Re: Upgrading point release from 10 to 10.1

2019-09-20 Thread Renato Gallo
ident. - Original Message - From: "Gene Heskett" To: "debian-user" Sent: Friday, September 20, 2019 3:18:48 PM Subject: Re: Upgrading point release from 10 to 10.1 On Thursday 19 September 2019 13:47:30 John Hasler wrote: > Fred writes: > > Do we have our lying idiot, ba

Re: Upgrading point release from 10 to 10.1

2019-09-20 Thread Gene Heskett
On Thursday 19 September 2019 13:47:30 John Hasler wrote: > Fred writes: > > Do we have our lying idiot, bag of crap, fake President to thank for > > making that much worse? > > This comes from the loons on the other side. Trump & Co have their > own set of stupidities. I have to play Sam Elliot

Re: Upgrading point release from 10 to 10.1

2019-09-19 Thread John Hasler
Wrong thread. Sorry. -- John Hasler jhas...@newsguy.com Elmwood, WI USA

Re: Upgrading point release from 10 to 10.1

2019-09-19 Thread John Hasler
Fred writes: > Do we have our lying idiot, bag of crap, fake President to thank for > making that much worse? This comes from the loons on the other side. Trump & Co have their own set of stupidities. -- John Hasler jhas...@newsguy.com Elmwood, WI USA

Re: Upgrading point release from 10 to 10.1

2019-09-19 Thread Mindaugas Celiesius
> I upgraded to Debian 10.0 (from 9) a few days ago, and I just tried to > upgrade to 10.1 (sudo apt-get update, sudo apt-get upgrade, sudo apt-get > dist-upgrade), but it doesn't upgrade to 10.1 (lsb_release -a still lists > 10). What am I missing? > > And it is normal that the word InRelea

Re: Upgrading point release from 10 to 10.1

2019-09-19 Thread Greg Wooledge
On Thu, Sep 19, 2019 at 04:14:37PM +, D&P Dimov wrote: > I upgraded to Debian 10.0 (from 9) a few days ago, and I just tried to > upgrade to 10.1 (sudo apt-get update, sudo apt-get upgrade, sudo apt-get > dist-upgrade), but it doesn't upgrade to 10.1 (lsb_release -a still lists > 10). What a

Re: Upgrading from Stretch to Buster with docker 3rd party installed

2019-07-29 Thread Linux-Fan
James Allsopp writes: Hi, I was going to upgrade to Buster, but I've got docker installed  and am running a container as an ldap server. Consequently I don't want to get rid of it, but the install guide I read suggested removing all 3rd-party repositories before starting. This is the cur

Re: Upgrading from Stretch to Buster with docker 3rd party installed

2019-07-29 Thread Judah Richardson
I upgraded just fine with 3rd party repositories enabled. What you might want to do is ensure the repositories match the Debian version you're upgrading to. Typically repositories that do different builds for different Debian versions put the version in the repository URL. So check whether any suc

Re: Upgrading to Buster but keeping Postgresql-9.6

2019-07-11 Thread Clemens Eisserer
Hi Phil, > Thanks Richard, that looks like the best solution. They even > have a mailing list. I have have really enjoyed using docker for such issues - mix&match useland as you like it - without interfering with you "main" distribution and without any performance overhead. Br, Clemens Br, Cle

Re: Upgrading to Buster but keeping Postgresql-9.6

2019-07-10 Thread Phil Endecott
Richard Hector wrote: Another option is to switch to using the pgdg repo for 9.6: https://wiki.postgresql.org/wiki/Apt Thanks Richard, that looks like the best solution. They even have a mailing list. Cheers, Phil.

Re: Upgrading to Buster but keeping Postgresql-9.6

2019-07-09 Thread Teemu Likonen
Phil Endecott [2019-07-08T22:24:17+01] wrote: > Indeed, not upgrading to Buster is a possibility. Also upgrading > PostgreSQL to version 11 is a possibility. I think I understand the > issues with each of those options, but I don't have a good > understanding of the issues with trying to keep pg-9

Re: Upgrading to Buster but keeping Postgresql-9.6

2019-07-09 Thread Andrei POPESCU
On Lu, 08 iul 19, 22:24:17, Phil Endecott wrote: > Andrei POPESCU wrote: > > > > Is upgrading to buster a necessity? Stretch will be supported by Debian > > for one more year and probably some more by the LTS effort. > > Indeed, not upgrading to Buster is a possibility. Also upgrading PostgreSQL

Re: Upgrading to Buster but keeping Postgresql-9.6

2019-07-08 Thread Richard Hector
On 9/07/19 9:24 AM, Phil Endecott wrote: > Andrei POPESCU wrote: >> On Lu, 08 iul 19, 20:02:36, Phil Endecott wrote: >>> Dear Experts, >>> >>> Does anyone have any advice about the possibility of upgrading >>> systems from Stretch to Buster, but keeping Postgresql-9.6 for >>> the time being? >> >>

Re: Upgrading to Buster but keeping Postgresql-9.6

2019-07-08 Thread Phil Endecott
Andrei POPESCU wrote: On Lu, 08 iul 19, 20:02:36, Phil Endecott wrote: Dear Experts, Does anyone have any advice about the possibility of upgrading systems from Stretch to Buster, but keeping Postgresql-9.6 for the time being? Is upgrading to buster a necessity? Stretch will be supported by D

Re: Upgrading to Buster but keeping Postgresql-9.6

2019-07-08 Thread Andrei POPESCU
On Lu, 08 iul 19, 20:02:36, Phil Endecott wrote: > Dear Experts, > > Does anyone have any advice about the possibility of upgrading > systems from Stretch to Buster, but keeping Postgresql-9.6 for > the time being? Is upgrading to buster a necessity? Stretch will be supported by Debian for one m

Re: Upgrading to Buster but keeping Postgresql-9.6

2019-07-08 Thread Jochen Spieker
Phil Endecott: > > Does anyone have any advice about the possibility of upgrading > systems from Stretch to Buster, but keeping Postgresql-9.6 for > the time being? With previous Debian releases you always had to migrate your cluster to the new Postgres version manually. The new packages are inst

Re: Upgrading with a low data cap

2018-10-17 Thread Dan Ritter
On Wed, Oct 17, 2018 at 10:10:01AM -0500, John Hasler wrote: > Richard Owlett writes: > > Quoting webopedia.com, "A local-area network (LAN) is a computer > > network that spans a relatively small area." The sticking point is an > > unstated assumption - a LAN connects two *OR MORE* computers. I w

Re: Upgrading with a low data cap

2018-10-17 Thread John Hasler
Richard Owlett writes: > Quoting webopedia.com, "A local-area network (LAN) is a computer > network that spans a relatively small area." The sticking point is an > unstated assumption - a LAN connects two *OR MORE* computers. I wish > to connect *EXACTLY* two computers {for which an RS232 null mod

Re: Upgrading with a low data cap

2018-10-17 Thread Richard Owlett
On 10/15/2018 04:09 AM, David wrote: On Sun, 14 Oct 2018 at 23:01, Richard Owlett wrote: I have no desire nor need for a traditional LAN. Wanting to transfer or share data between machines, while simultaneously declaring the above, appears inconsistent. I don't know what a "traditional LAN"

Re: Upgrading with a low data cap

2018-10-15 Thread Gene Heskett
On Monday 15 October 2018 10:45:54 Dan Purgert wrote: > Gene Heskett wrote: > > On Monday 15 October 2018 05:09:05 David wrote: > > [...] > > And the best of both worlds is had buy investing in a good router, > > useing to to Native Address Translation between the dhcp supplied > > address your >

Re: Upgrading with a low data cap

2018-10-15 Thread Dan Purgert
Gene Heskett wrote: > On Monday 15 October 2018 05:09:05 David wrote: > [...] > And the best of both worlds is had buy investing in a good router, useing > to to Native Address Translation between the dhcp supplied address your NAT = "Network Address Translation" ;) > ISP gives the router when

Re: Upgrading with a low data cap

2018-10-15 Thread Gene Heskett
On Monday 15 October 2018 05:09:05 David wrote: > On Sun, 14 Oct 2018 at 23:01, Richard Owlett wrote: > > I have no desire nor need for a traditional LAN. > As a somewhat senior to Richard, one thing I've learned in a lng carrear in electronics is that life is a lot simpler if you use the

Re: Upgrading with a low data cap

2018-10-15 Thread Richard Owlett
On 10/15/2018 04:09 AM, David wrote: On Sun, 14 Oct 2018 at 23:01, Richard Owlett wrote: I have no desire nor need for a traditional LAN. Wanting to transfer or share data between machines, while simultaneously declaring the above, appears inconsistent. [ *MASSIVE* snip] Thank you for your

Re: Upgrading with a low data cap

2018-10-15 Thread David
On Sun, 14 Oct 2018 at 23:01, Richard Owlett wrote: > > I have no desire nor need for a traditional LAN. Wanting to transfer or share data between machines, while simultaneously declaring the above, appears inconsistent. I don't know what a "traditional LAN" is, so I wonder what you mean by thos

Re: Upgrading with a low data cap

2018-10-14 Thread Richard Owlett
On 10/10/2018 08:01 AM, Alexandre Rossi wrote: Hi, Something just brought to mind apt-offline. The introductory paragraph in the man page states: apt-offline brings offline package management functionality to Debian based system. It can be used to download packages and its dependencies to be i

Re: Upgrading with a low data cap

2018-10-14 Thread Richard Owlett
On 10/10/2018 02:53 AM, Curt wrote: On 2018-10-09, Gene Heskett wrote: It's about time some invented a WiFi device which plugs into a USB port. Not needed, you can buy such a dongle from netgear for at least half a decade or longer. I was out of ports on the 4 port in the shop, so I I inte

Re: Upgrading with a low data cap

2018-10-10 Thread songbird
mick crane wrote: >songbird wrote: ... >> i used to take the USB stick to the library to download >> big packages when needing updates. glad i haven't had to >> do that in a while, but i still have a relatively slow >> connection (about 10M/minute) compared to many, but it's >> much better than

Re: Upgrading with a low data cap

2018-10-10 Thread Gene Heskett
On Wednesday 10 October 2018 11:18:46 David Wright wrote: > On Wed 10 Oct 2018 at 10:52:10 (-0400), Gene Heskett wrote: > > On Wednesday 10 October 2018 09:58:22 rhkra...@gmail.com wrote: > > > On Tuesday, October 09, 2018 04:01:49 PM Gene Heskett wrote: > > > > On Tuesday 09 October 2018 12:20:25

Re: Upgrading with a low data cap

2018-10-10 Thread David Wright
On Wed 10 Oct 2018 at 10:52:10 (-0400), Gene Heskett wrote: > On Wednesday 10 October 2018 09:58:22 rhkra...@gmail.com wrote: > > On Tuesday, October 09, 2018 04:01:49 PM Gene Heskett wrote: > > > On Tuesday 09 October 2018 12:20:25 Brian wrote: > > > > It's about time some invented a WiFi device w

  1   2   3   4   5   6   7   8   9   10   >