Re: Erreur suite à un apt upgrade noyau 6.6.18

Le 12 février 2024 ajh-valmer a écrit : > Encore un qui n'a pas lu mon mail sans chercher plus loin que le bout > de ses yeux : >> xrandr --addmode VGA 1280x1024_60.00 >> xrandr --output VGA-0 --mode 1280x1024_60.00 : > Réponse : > xrandr: Failed to get size of gamma for output default > xrandr:

Re: Erreur suite à un apt upgrade noyau 6.6.18

https://www.youtube.com/watch?v=XAx46zIMPCY - Mail original - De: "ajh-valmer" À: debian-user-french@lists.debian.org Envoyé: Lundi 12 Février 2024 00:32:46 Objet: Re: Erreur suite à un apt upgrade noyau 6.6.18 On Sunday 11 February 2024 23:35:11 Bernard Schoenacker wrot

Re: Erreur suite à un apt upgrade noyau 6.6.18

On Sunday 11 February 2024 23:35:11 Bernard Schoenacker wrote: > Hallo Wache, C'est qui Wache ? > Voici encore une bonne nouvelle pour une personne qui n'a pas cherché > plus loin que le bout de son nez... > #script-xrandr.sh > xrandr --newmode "1280x1024_60.00" 108.88 1280 1360 1496 1712

Re: Erreur suite à un apt upgrade noyau 6.6.18

: debian-user-french@lists.debian.org Envoyé: Dimanche 11 Février 2024 18:21:10 Objet: Re: Erreur suite à un apt upgrade noyau 6.6.18 https://doc.ubuntu-fr.org/xrandr J'ai donc tenté ceci : # xrandr --addmode VGA 1280x1024_60.00 xrandr: Failed to get size of gamma for output default xrandr: cannot find ou

Re: Erreur suite à un apt upgrade noyau 6.6.18

https://doc.ubuntu-fr.org/xrandr J'ai donc tenté ceci : # xrandr --addmode VGA 1280x1024_60.00 xrandr: Failed to get size of gamma for output default xrandr: cannot find output "VGA" Pour les autres commandes, réponses toujours en erreur.

Re: Erreur suite à un apt upgrade noyau 6.6.18

On Tuesday 06 February 2024 12:50:21 Fabien Dubois wrote: > > apt upgrade : > > c'est le module Nvidia qui empêche l'installation du noyau 6.6.18. > > Mon pilote Nvidia 470 est celui pêché sur le dépôt free de Debian. > > Je n'ai jamais réussi à installer un pilote "

Re: Erreur suite à un apt upgrade

J'ai pu redémarrer Debian par le noyau 6.6.17. apt upgrade : Donc, c'est le module Nvidia qui empêche l'installation du noyau 6.6.18. Mon pilote Nvidia 470 est celui pêché sur le dépôt free de Debian. Je n'ai jamais réussi à installer un pilote "nouveau". /var/lib/dkms/nvidia

Re: Erreur suite à un apt upgrade

ia-tesla-470/470.223.02/build/make.log for > more information. J'ai pu redémarrer Debian par le noyau 6.6.17. apt upgrade : Donc, c'est le module Nvidia qui empêche l'installation du noyau 6.6.18. Mon pilote Nvidia 470 est celui pêché sur le dépôt free de Debian. Je n'ai jamais réussi à inst

Re: Erreur suite à un apt upgrade

Le 05/02/2024 à 22:29, Fabien Dubois a écrit : Bonsoir, sid, noyau 6.6.18, j'ai eu un souci similaire (avec le 470 aussi) . Les pilotes propriétaires nvidia semblent avoir subi une maj qui casse un peu tout, notamment la construction des modules. Pour ça, et d'autres raisons, je suis

Re: Erreur suite à un apt upgrade

Le 05/02/2024 à 18:33, ajh-valmer a écrit : Voici plus d'infos : env NV_VERBOSE=1 make -j4 modules KERNEL_UNAME=6.1.0-18-amd64.. (bad exit status: 2) Error! Bad return status for module build on kernel: 6.1.0-18-amd64 (x86_64) Consult

Re: Erreur suite à un apt upgrade

Voici plus d'infos : env NV_VERBOSE=1 make -j4 modules KERNEL_UNAME=6.1.0-18-amd64.. (bad exit status: 2) Error! Bad return status for module build on kernel: 6.1.0-18-amd64 (x86_64) Consult /var/lib/dkms/nvidia-tesla-470/470.223.02/build/make.log

Re: Erreur suite à un apt upgrade

Le 2024-02-05 18:22, ajh-valmer a écrit : C'est grave Docteur ? : Setting up openjdk-17-jre:amd64 (17.0.10+7-1~deb12u1) ... Errors were encountered while processing: linux-image-6.1.0-18-amd64 linux-image-amd64 linux-headers-6.1.0-18-amd64 linux-headers-amd64 E: Sub-process /usr/bin/dpkg

Erreur suite à un apt upgrade

C'est grave Docteur ? : Setting up openjdk-17-jre:amd64 (17.0.10+7-1~deb12u1) ... Errors were encountered while processing: linux-image-6.1.0-18-amd64 linux-image-amd64 linux-headers-6.1.0-18-amd64 linux-headers-amd64 E: Sub-process /usr/bin/dpkg returned an error code (1) Merci.

Re: apt upgrade can't find archive for virtualbox-7.0

On 23 Dec 2023 09:22 -0500, from s.mol...@sbcglobal.net (Stephen P. Molnar): >> If you don't want to run VirtualBox going forward, the easiest way >> might be to just `apt purge virtualbox-7.0`. > (base) comp@AbNormal:~$ sudo apt purge virtualbox-7.0 > [sudo] password for comp: > Reading package

Re: apt upgrade can't find archive for virtualbox-7.0; was: Synaptic Problem

... Done Reading state information... Done All packages are up to date. W: https://repo.skype.com/deb/dists/stable/InRelease: Key is stored in legacy trusted.gpg keyring (/etc/apt/trusted.gpg), see the DEPRECATION section in apt-key(8) for details. (base) comp@AbNormal:~$ sudo apt upgrade Reading

Re: apt upgrade can't find archive for virtualbox-7.0; was: Synaptic Problem

one > All packages are up to date. > W: https://repo.skype.com/deb/dists/stable/InRelease: Key is stored in > legacy trusted.gpg keyring (/etc/apt/trusted.gpg), see the DEPRECATION > section in apt-key(8) for details. > (base) comp@AbNormal:~$ sudo apt upgrade > Reading packa

Re: Fout tijdens apt upgrade

Cecil Westerhof writes: > Tijdens een apt upgrade krijg ik: > libdvd-pkg: Checking orig.tar integrity... > /usr/src/libdvd-pkg/libdvdcss_1.4.3.orig.tar.bz2: OK > libdvd-pkg: `apt-get check` failed, you may have broken packages. > Aborting... > > Als ik dan doe

Re: Fout tijdens apt upgrade

lezen. >> Maar dit is mijn probleem: >> Tijdens een apt upgrade krijg ik: >> libdvd-pkg: Checking orig.tar integrity... >> /usr/src/libdvd-pkg/libdvdcss_1.4.3.orig.tar.bz2: OK >> libdvd-pkg: `apt-get check` failed, you may have broken >&g

Re: Fout tijdens apt upgrade

On Sat, 02 Sep 2023 17:53:51 +0200 Cecil Westerhof wrote: > > En wat is 'dit probleem' ook al weer? > > Je zou natuurlijk even naar mijn oorspronkelijke bericht kunnen > kijken, of mijn reactie op je andere reactie kunnen lezen. > Maar dit is mijn probleem: > Tijdens

Re: Fout tijdens apt upgrade

On Sat, 02 Sep 2023 15:17:23 +0200 Cecil Westerhof wrote: > Firefox is on hold. Die wil ik standaard niet upgraden, daar als je > die upgrade terwijl firefox nog draait firefox crasht. > Al tientallen keren 'apt upgrade' gedraaid met firefox on hold zonder > dit probleem te hebben.

Re: Fout tijdens apt upgrade Added: libdvd-pkg’s postinst script is broken

Cecil Westerhof writes: > Tijdens een apt upgrade krijg ik: > libdvd-pkg: Checking orig.tar integrity... > /usr/src/libdvd-pkg/libdvdcss_1.4.3.orig.tar.bz2: OK > libdvd-pkg: `apt-get check` failed, you may have broken > packages. Aborting... libdvd-pkg’s

Re: Fout tijdens apt upgrade

t; Of wat volgens mij ook wel werkt is: >> > >> > apt install firefox-esr >> > >> > Maar ik ben geen apt guru, anderen hebben wellicht een fraaiere >> > oplossing >> >> Firefox is on hold. Die wil ik standaard niet upgraden, daar als je >

Re: Fout tijdens apt upgrade

ben geen apt guru, anderen hebben wellicht een fraaiere > > oplossing > > Firefox is on hold. Die wil ik standaard niet upgraden, daar als je > die upgrade terwijl firefox nog draait firefox crasht. > Al tientallen keren 'apt upgrade' gedraaid met firefox on hold zonder > dit probleem te hebben. > En wat is 'dit probleem' ook al weer? Bonusvraag: Wat is met het advies om `apt install -f` te doen gebeurd? Groeten Geert Stappers -- Silence is hard to parse

Re: Fout tijdens apt upgrade

t; apt install -f > > Of wat volgens mij ook wel werkt is: > > apt install firefox-esr > > Maar ik ben geen apt guru, anderen hebben wellicht een fraaiere > oplossing Firefox is on hold. Die wil ik standaard niet upgraden, daar als je die upgrade terwijl firefox nog draait firefox

Re: Fout tijdens apt upgrade

On Fri, 01 Sep 2023 22:17:34 +0200 Cecil Westerhof wrote: > > Wellicht een nieuwe dependency dat-ie wil installeren? Wat doet > > > > apt full-upgrade > > apt full-upgrade > Reading package lists... Done > Building dependency tree... Done > Reading state information... Done > Calculating

Re: Fout tijdens apt upgrade

Richard Lucassen writes: > On Fri, 01 Sep 2023 21:07:39 +0200 > Cecil Westerhof wrote: > >> Tijdens een apt upgrade krijg ik: >> libdvd-pkg: Checking orig.tar integrity... >> /usr/src/libdvd-pkg/libdvdcss_1.4.3.orig.tar.bz2: OK >> libdvd-pkg: `ap

Re: Fout tijdens apt upgrade

On Fri, 01 Sep 2023 21:07:39 +0200 Cecil Westerhof wrote: > Tijdens een apt upgrade krijg ik: > libdvd-pkg: Checking orig.tar integrity... > /usr/src/libdvd-pkg/libdvdcss_1.4.3.orig.tar.bz2: OK > libdvd-pkg: `apt-get check` failed, you may have broken packages. > Abort

Fout tijdens apt upgrade

Tijdens een apt upgrade krijg ik: libdvd-pkg: Checking orig.tar integrity... /usr/src/libdvd-pkg/libdvdcss_1.4.3.orig.tar.bz2: OK libdvd-pkg: `apt-get check` failed, you may have broken packages. Aborting... Als ik dan doe: apt-get check Dan krijg ik: Reading package lists

Re: apt upgrade in buster is confused

ble/amd64/release-notes/ch-upgrading.en.html because if you have, then I do not understand why you aren't following the documented steps, which are in part: # apt update # apt upgrade --without-new-pkgs # apt full-upgrade Cheers, Andy -- https://bitfolk.com/ -- No-nonsense VPS hosting

Re: apt upgrade in buster is confused

On Mon, 24 Jul 2023 13:35:49 -0700 Scott Edwards wrote: > https://paste.debian.net/1286823/ > > I just want to upgrade to stable, but I'm stuck here Stuck where? What instructions did you follow. Did you modify /etc/apt/sources.list? Did you run "apt update" before "

Re: apt upgrade in buster is confused

On Mon, Jul 24, 2023 at 4:36 PM Scott Edwards wrote: > > https://paste.debian.net/1286823/ > > I just want to upgrade to stable, but I'm stuck here Run 'apt-get update' first, and then 'apt-get upgrade'. If Apt-get fails, then try Aptitude. Aptitude has a better solver, and can often come up

apt upgrade in buster is confused

https://paste.debian.net/1286823/ I just want to upgrade to stable, but I'm stuck here

Re: problemas con apt upgrade

¿Qué intentaste instalar? JAP Instalé varios paquetes con la instalación limpia. No podría identificar un paquete en especial -- Marcelo E. Giordano /Contador Público/ *(2634) 4***17505** Pedro Molina 574· San Martín - Mendoza _c ontadorgiordano.com.ar_

Re: problemas con apt upgrade

Seguramente la solución pase por esperar a que saquen alguna actualización. Saludos, Gracias, esperaré

Re: problemas con apt upgrade

El 26/6/23 a las 17:11, Marcelo Eduardo Giordano escribió: Estimados: Se que este es un error basico pero no se solucionarlo. Instalé un paquete viejo imagino en Debian 12 y me sale esto que copio abajo. Gracias por la ayuda. Feliz con mi Debian 12 dpkg:error al procesar el paquete

Re: problemas con apt upgrade

Bienvenido a Debian El lun., 26 de junio de 2023 2:12 p. m., Marcelo Eduardo Giordano < contadorgiord...@gmail.com> escribió: > Estimados: Se que este es un error basico pero no se solucionarlo. Instalé > un paquete viejo imagino en Debian 12 y me sale esto que copio abajo. > > Gracias por la

problemas con apt upgrade

Estimados: Se que este es un error basico pero no se solucionarlo. Instalé un paquete viejo imagino en Debian 12 y me sale esto que copio abajo. Gracias por la ayuda. Feliz con mi Debian 12 dpkg:error al procesar el paquete ca-certificates-java (--configure): el subproceso instalado paquete

Re: Logout at apt upgrade

On Sat 03 Dec 2022 at 08:19:48 (+0100), Loïc Grenié wrote: > On Sat Dec, 3, 2022 at 04:03, David Wright wrote: > > Yes, hence my comment on potential interactions between different > > packages. The OP mentioned udev, but in their OP they talked about > > manually restarting systemd services. I

Re: Logout at apt upgrade

On Sat Dec, 3, 2022 at 04:03, David Wright wrote: > On Fri 02 Dec 2022 at 21:33:45 (-0500), The Wanderer wrote: > > > > FWIW: > > > > $ apt-cache policy udev > > udev: > > Installed: 252.1-1 > > Candidate: 252.1-1 > > Version table: > > *** 252.1-1 900 > > 900

Re: Logout at apt upgrade

On Fri 02 Dec 2022 at 21:33:45 (-0500), The Wanderer wrote: > > FWIW: > > $ apt-cache policy udev > udev: > Installed: 252.1-1 > Candidate: 252.1-1 > Version table: > *** 252.1-1 900 > 900 http://ftp.us.debian.org/debian testing/main amd64 Packages > 100

Re: Logout at apt upgrade

On 2022-12-02 at 21:04, David Wright wrote: > On Fri 02 Dec 2022 at 09:04:35 (+0100), Loïc Grenié wrote: > >> On Fri Dec 2 2022 at 04:31, David Wright wrote: >>> AFAICT udev was upgraded from 247.3-7 to 247.3-7+deb11u1 in early >>> September, so which distribution are /you/ running? >> >> %

Re: Logout at apt upgrade

On Fri 02 Dec 2022 at 09:04:35 (+0100), Loïc Grenié wrote: > On Fri Dec 2 2022 at 04:31, David Wright wrote: > > On Wed 30 Nov 2022 at 14:25:19 (+0100), Loïc Grenié wrote: > > > Happened once again. This time I think the culprit was udev (but I > > > cannot > > > be too sure). Among the

Re: Logout at apt upgrade

On Fri Dec 2 2022 at 04:31, David Wright wrote: > On Wed 30 Nov 2022 at 14:25:19 (+0100), Loïc Grenié wrote: > > Happened once again. This time I think the culprit was udev (but I > > cannot > > be too sure). Among the updated package nothing should have killed X: > > beyond udev there

Re: Logout at apt upgrade

On Wed 30 Nov 2022 at 14:25:19 (+0100), Loïc Grenié wrote: > Happened once again. This time I think the culprit was udev (but I > cannot > be too sure). Among the updated package nothing should have killed X: > beyond udev there was a bunch of libreoffice and related (not using right >

Re: Logout at apt upgrade

On Thu 01 Dec 2022 at 17:45:25 (-0700), Tom Dial wrote: > On 11/29/22 15:35, Loïc Grenié wrote: > >     Dear Debian users, > > > >     when I apt upgrade my system, I often (one every three, more > >   or less) find myself brutally logged out of the window system, &

Re: Logout at apt upgrade

Loïc Grenié wrote:     Dear Debian users,     when I apt upgrade my system, I often (one every three, more   or less) find myself brutally logged out of the window system,   with systemd services painfully restarting (or failing to restart).   The only way I can recover is usually

Re: Logout at apt upgrade

On 11/29/22 15:35, Loïc Grenié wrote:     Dear Debian users,     when I apt upgrade my system, I often (one every three, more   or less) find myself brutally logged out of the window system,   with systemd services painfully restarting (or failing to restart).   The only way I can

Re: Logout at apt upgrade

On Thu, Dec 01, 2022 at 12:34:35AM -0500, Stefan Monnier wrote: > >> The one application I do avoid upgrading while it's running is > >> Firefox, but that's mainly because it occasionally gives a new > >> startup screen after an upgrade, and I want to read what it says. > > > > I take the risk and

Re: Logout at apt upgrade

>> The one application I do avoid upgrading while it's running is >> Firefox, but that's mainly because it occasionally gives a new >> startup screen after an upgrade, and I want to read what it says. > > I take the risk and watch the thing going down in flames. I > admit that it gives me a

Re: Logout at apt upgrade

On Wed, Nov 30, 2022 at 02:36:57PM -0600, David Wright wrote: [...] > The only reasons I'd close down X are (a) a dist-upgrade from > oldstable to stable (and the like), That I do, too. > and (b) dpkg-reconfigure > console-setup and keyboard-configuration after I've been >

Re: Logout at apt upgrade

On Wed 30 Nov 2022 at 08:42:41 (+0100), to...@tuxteam.de wrote: > On Wed, Nov 30, 2022 at 12:36:43AM -0500, Felix Miata wrote: > > > I learned many many moons ago to not trust any update/upgrade process to not > > interfere with a running X session. I usually close apps I don't want data > >

Re: Logout at apt upgrade

upgrade will stall until I say yes or no when it asks if I want to restart exim and a second program that I can't remember. > Still, it never happened to me, and I dist-upgrade roughly once > a week. I run "apt-get upgrade". It will take me a few days to remember to do so, but I'll try

Re: Logout at apt upgrade

Happened once again. This time I think the culprit was udev (but I cannot be too sure). Among the updated package nothing should have killed X: beyond udev there was a bunch of libreoffice and related (not using right now), zathura (not using), not much more, at the very least, nothing

Re: Logout at apt upgrade

On Wed, Nov 30, 2022 at 06:16:04AM +0100, to...@tuxteam.de wrote: > FWIW it never happened to me. But: I'm on a pretty minimal system by > today's standards (X, Fvwm). The only application behaving strangely > after a dist-upgrade is... the browser, Firefix: "Ohmigod, something > funny happened,

Re: Logout at apt upgrade

On 11/30/22, to...@tuxteam.de wrote: > On Wed, Nov 30, 2022 at 12:44:49AM +0100, DdB wrote: >> Am 29.11.2022 um 23:35 schrieb Loïc Grenié: >> > when I apt upgrade my system, I often (one every three, more >> > or less) find myself brutally logg

Re: Logout at apt upgrade

Jeffrey Walton writes: > KDE works as expected. Yep. > God bless those who have stuck with GNOME after the change to GNOME3. > They have the tolerance of saints. I have to agree. I did get Gnome 3 to somewhere I kinda liked but when an updated wiped my customizations, it was time to say good

Re: Logout at apt upgrade

Thanks Tomas, and thanks to all those responded, On Wed, Nov 30, 2022 at 06:16, Tomas wrote: > On Wed, Nov 30, 2022 at 12:44:49AM +0100, DdB wrote: > > Am 29.11.2022 um 23:35 schrieb Loïc Grenié: > > > when I apt upgrade my system, I often (one every three, more >

Re: Logout at apt upgrade

On Wed, Nov 30, 2022 at 12:36:43AM -0500, Felix Miata wrote: [...] > What I have noticed in Debian that I do not at all like, is when I boot to > multi-user.target for the specific purpose of apt or apt-get upgrading, even > when > systemctl get-default returns multi-user.target, that if the DM

Re: Logout at apt upgrade

Loïc Grenié composed on 2022-11-29 23:35 (UTC+0100): > when I apt upgrade my system, I often (one every three, more > or less) find myself brutally logged out of the window system, > with systemd services painfully restarting (or failing to restart). > The only way I

Re: Logout at apt upgrade

On Wed, Nov 30, 2022 at 12:16 AM wrote: > > On Wed, Nov 30, 2022 at 12:44:49AM +0100, DdB wrote: > > Am 29.11.2022 um 23:35 schrieb Loïc Grenié: > > > when I apt upgrade my system, I often (one every three, more > > > or less) find myself brutally l

Re: Logout at apt upgrade

On Wed, Nov 30, 2022 at 12:44:49AM +0100, DdB wrote: > Am 29.11.2022 um 23:35 schrieb Loïc Grenié: > >     when I apt upgrade my system, I often (one every three, more > >   or less) find myself brutally logged out of the window system, > >   with systemd services painfully r

Re: Logout at apt upgrade

Am 29.11.2022 um 23:35 schrieb Loïc Grenié: >     when I apt upgrade my system, I often (one every three, more >   or less) find myself brutally logged out of the window system, >   with systemd services painfully restarting (or failing to restart). >   The only way I can recove

Logout at apt upgrade

Dear Debian users, when I apt upgrade my system, I often (one every three, more or less) find myself brutally logged out of the window system, with systemd services painfully restarting (or failing to restart). The only way I can recover is usually to reboot. I've tried

Re: does apt upgrade & full-upgrade packages from Security Updates (Debian Security Advisories (DSA))

On Sun, Nov 13, 2022 at 09:56:21AM +, jindam, vani wrote: > i have only deb http://deb.debian.org/debian bullseye main contrib non-free > in my sources.list. > > does apt upgrade & full-upgrade packages from Security Updates (Debian > Security Advisories (DSA))? &g

Re: does apt upgrade & full-upgrade packages from Security Updates (Debian Security Advisories (DSA))

On Sun, Nov 13, 2022 at 09:56:21AM +, jindam, vani wrote: > i have only deb http://deb.debian.org/debian bullseye main contrib non-free > in my sources.list. > > does apt upgrade & full-upgrade packages from Security Updates (Debian > Security Advisories (DSA))?

does apt upgrade & full-upgrade packages from Security Updates (Debian Security Advisories (DSA))

i have only deb http://deb.debian.org/debian bullseye main contrib non-free in my sources.list. does apt upgrade & full-upgrade packages from Security Updates (Debian Security Advisories (DSA))? which is correct? deb http://security.debian.org/debian-security bullseye-security main con

Re: Apt upgrade problem

On Sun, 16 Oct 2022 23:44:00 +0100 Mark Fletcher wrote: > "apt list --upgradable" shows a new version of the Amazon Workspaces > client, version 4.3.0.1766. It also shows that there is one more > version available. This may be a silly question, but have you checked with Amazon customer support?

Re: Apt upgrade problem

On Sun, 16 Oct 2022 23:44:00 +0100 Mark Fletcher wrote: > After "sudo apt update", the system informs me there is 1 package that can > be upgraded. > > "sudo apt upgrade" reports nothing to do, 0 packages upgraded, 0 newly > installed, 0 to remove and 0 n

Re: Apt upgrade problem

On Sun 16 Oct 2022 at 23:44:00 (+0100), Mark Fletcher wrote: > > Tonight I am seeing a behaviour pattern in my Debian Bullseye system that I > have not seen before. > > After "sudo apt update", the system informs me there is 1 package that can > be upgraded. >

Apt upgrade problem

Hi Tonight I am seeing a behaviour pattern in my Debian Bullseye system that I have not seen before. After "sudo apt update", the system informs me there is 1 package that can be upgraded. "sudo apt upgrade" reports nothing to do, 0 packages upgraded, 0 newly installe

Re: adding trouble on the trouble (using apt upgrade)

ps: sorry, on a Debian Sid system for sure. Le lun. 14 mars 2022 à 19:41, Patrice Duroux a écrit : > > Hi, > > Since some versions ago, apt/dpkg(?) is stopping its process (upgrade > here) whatever the packaging trouble it is facing. But in some cases, it > may leave the system more broken than

adding trouble on the trouble (using apt upgrade)

Hi, Since some versions ago, apt/dpkg(?) is stopping its process (upgrade here) whatever the packaging trouble it is facing. But in some cases, it may leave the system more broken than it would become just by 'skipping' the troubling package. For instance, in the upgrading transaction list were

Re: systemd[1]: Starting Daily apt upgrade and clean activities...

Hello, On Tue, Feb 08, 2022 at 02:25:35PM -0500, Lee wrote: > Apparently the syslog message > systemd[1]: Starting Daily apt upgrade and clean activities... > is caused by systemd / apt-daily.timer - correct? No, that one is from apt-daily-upgrade.timer: $ grep -r "upgrade a

Re: systemd[1]: Starting Daily apt upgrade and clean activities...

t news, and an 'apt upgrade' if necessary (that's where I find out just what's available), and everything's already there -- at least I think it is; the updating's real fast. Even when it's updating Firefox or the kernel. I do the same via SSH for the other machines on the net. -- Glenn E

Re: systemd[1]: Starting Daily apt upgrade and clean activities...

On Tue 08 Feb 2022 at 14:25:35 (-0500), Lee wrote: > Apparently the syslog message > systemd[1]: Starting Daily apt upgrade and clean activities... > is caused by systemd / apt-daily.timer - correct? > > # sudo systemctl status apt-daily.timer > ● apt-daily.timer - Daily apt d

Re: systemd[1]: Starting Daily apt upgrade and clean activities...

Lee wrote: > Apparently the syslog message > systemd[1]: Starting Daily apt upgrade and clean activities... > is caused by systemd / apt-daily.timer - correct? > > # sudo systemctl status apt-daily.timer > ● apt-daily.timer - Daily apt download activities > Loaded:

Re: systemd[1]: Starting Daily apt upgrade and clean activities...

On Tue, Feb 08, 2022 at 02:25:35PM -0500, Lee wrote: > Apparently the syslog message > systemd[1]: Starting Daily apt upgrade and clean activities... > is caused by systemd / apt-daily.timer - correct? > > # sudo systemctl status apt-daily.timer > ● apt-daily.timer -

systemd[1]: Starting Daily apt upgrade and clean activities...

Apparently the syslog message systemd[1]: Starting Daily apt upgrade and clean activities... is caused by systemd / apt-daily.timer - correct? # sudo systemctl status apt-daily.timer ● apt-daily.timer - Daily apt download activities Loaded: loaded (/lib/systemd/system/apt-daily.timer

Re: apt-upgrade (Bullseye) shows 1 pkg not upgraded

On Mon, 2021-08-30 at 21:53 +0300, Andrei POPESCU wrote: > On Ma, 10 aug 21, 13:32:09, Jim Popovitch wrote: > > How can I determine what the "1 not upgraded" package might be? > > > > > > ~$ apt-get update > > Hit:1 http://ftp.us.debian.org/debian bullseye InRelease > > Hit:2

Re: apt-upgrade (Bullseye) shows 1 pkg not upgraded

On Ma, 10 aug 21, 13:32:09, Jim Popovitch wrote: > How can I determine what the "1 not upgraded" package might be? > > > ~$ apt-get update > Hit:1 http://ftp.us.debian.org/debian bullseye InRelease > Hit:2 http://security.debian.org bullseye-security InRelease > Hit:3

Re: apt-upgrade (Bullseye) shows 1 pkg not upgraded

On 8/10/21, Jim Popovitch wrote: > On Tue, 2021-08-10 at 18:59 -0400, Greg Wooledge wrote: >> >> The OP claimed they have nothing pinned, but presented no evidence to >> support this claim. Perhaps they thought that because they didn't >> explicitly *pin* anything themselves, there must not be

Re: apt-upgrade (Bullseye) shows 1 pkg not upgraded

On Tue 10 Aug 2021 at 14:09:27 (-0400), Jim Popovitch wrote: > On Tue, 2021-08-10 at 14:00 -0400, Greg Wooledge wrote: > > On Tue, Aug 10, 2021 at 01:57:13PM -0400, Jim Popovitch wrote: > > > ~$ apt-get -sV full-upgrade > > > Reading package lists... Done > > > Building dependency tree... Done > >

Re: apt-upgrade (Bullseye) shows 1 pkg not upgraded

On Tue, 2021-08-10 at 18:59 -0400, Greg Wooledge wrote: > On Wed, Aug 11, 2021 at 08:27:03AM +1000, David wrote: > > On Wed, 11 Aug 2021 at 03:32, Jim Popovitch wrote: > > > > > apt-upgrade (Bullseye) shows 1 pkg not upgraded > > > > > How can I determine

Re: apt-upgrade (Bullseye) shows 1 pkg not upgraded

On Wed, Aug 11, 2021 at 08:27:03AM +1000, David wrote: > On Wed, 11 Aug 2021 at 03:32, Jim Popovitch wrote: > > > apt-upgrade (Bullseye) shows 1 pkg not upgraded > > > How can I determine what the "1 not upgraded" package might be? > > Hi, I dunno if thi

Re: apt-upgrade (Bullseye) shows 1 pkg not upgraded

On Wed, 11 Aug 2021 at 03:32, Jim Popovitch wrote: > apt-upgrade (Bullseye) shows 1 pkg not upgraded > How can I determine what the "1 not upgraded" package might be? Hi, I dunno if this message will be of any use, because other suggestions indicate that this might be due to

Re: apt-upgrade (Bullseye) shows 1 pkg not upgraded

Hello, If for example you have set up unattended-upgrades and installed apt- listbugs, then when unattended-upgrades runs, apt-listbugs automatically pins (-3) upgradable packages that are affected by bugs in order for them to be hold until a fix. They are automatically de-pinned when bugs

Re: apt-upgrade (Bullseye) shows 1 pkg not upgraded

On Tue, 2021-08-10 at 20:03 +0200, john doe wrote: > On 8/10/2021 7:57 PM, Jim Popovitch wrote: > > On Tue, 2021-08-10 at 19:49 +0200, john doe wrote: > > > On 8/10/2021 7:32 PM, Jim Popovitch wrote: > > > > How can I determine what the "1 not upgraded" package might be? > > > > > > > > > > > >

Re: apt-upgrade (Bullseye) shows 1 pkg not upgraded

On Tue, 2021-08-10 at 14:00 -0400, Greg Wooledge wrote: > On Tue, Aug 10, 2021 at 01:57:13PM -0400, Jim Popovitch wrote: > > ~$ apt-get -sV full-upgrade > > Reading package lists... Done > > Building dependency tree... Done > > Calculating upgrade... Done > > 0 upgraded, 0 newly installed, 0 to

Re: apt-upgrade (Bullseye) shows 1 pkg not upgraded

On 8/10/2021 7:57 PM, Jim Popovitch wrote: On Tue, 2021-08-10 at 19:49 +0200, john doe wrote: On 8/10/2021 7:32 PM, Jim Popovitch wrote: How can I determine what the "1 not upgraded" package might be? ~$ apt-get update Hit:1 http://ftp.us.debian.org/debian bullseye InRelease Hit:2

Re: apt-upgrade (Bullseye) shows 1 pkg not upgraded

On Tue, Aug 10, 2021 at 01:57:13PM -0400, Jim Popovitch wrote: > ~$ apt-get -sV full-upgrade > Reading package lists... Done > Building dependency tree... Done > Calculating upgrade... Done > 0 upgraded, 0 newly installed, 0 to remove and 1 not upgraded. Have you tried Google yet?

Re: apt-upgrade (Bullseye) shows 1 pkg not upgraded

On Tue, 2021-08-10 at 19:49 +0200, john doe wrote: > On 8/10/2021 7:32 PM, Jim Popovitch wrote: > > How can I determine what the "1 not upgraded" package might be? > > > > > > ~$ apt-get update > > Hit:1 http://ftp.us.debian.org/debian bullseye InRelease > > Hit:2 http://security.debian.org

Re: apt-upgrade (Bullseye) shows 1 pkg not upgraded

On 8/10/2021 7:32 PM, Jim Popovitch wrote: How can I determine what the "1 not upgraded" package might be? ~$ apt-get update Hit:1 http://ftp.us.debian.org/debian bullseye InRelease Hit:2 http://security.debian.org bullseye-security InRelease Hit:3 http://ftp.us.debian.org/debian

Re: apt-upgrade (Bullseye) shows 1 pkg not upgraded

On Tue, 2021-08-10 at 12:37 -0500, Lance Simmons wrote: > apt list --upgradeable :( ~$ apt list --upgradeable Listing... Done Thanks for suggesting that though. -Jim P.

Re: apt-upgrade (Bullseye) shows 1 pkg not upgraded

apt list --upgradeable On Aug 10 2021, at 12:32 pm, Jim Popovitch wrote: > How can I determine what the "1 not upgraded" package might be? > > > ~$ apt-get update > Hit:1 http://ftp.us.debian.org/debian bullseye InRelease > Hit:2 http://security.debian.org bullseye-security InRelease > Hit:3

apt-upgrade (Bullseye) shows 1 pkg not upgraded

How can I determine what the "1 not upgraded" package might be? ~$ apt-get update Hit:1 http://ftp.us.debian.org/debian bullseye InRelease Hit:2 http://security.debian.org bullseye-security InRelease Hit:3 http://ftp.us.debian.org/debian bullseye-updates InRelease Reading package lists... Done

Re: minimize daemon downtime for apt upgrade

On Thu, Apr 08, 2021 at 01:47:22PM -0600, Charles Curley wrote: > On Thu, 8 Apr 2021 10:46:06 -0500 > Matt Zagrabelny wrote: > > > If I wait for a few months to perform an "apt upgrade", many packages > > get upgraded. > > ... > > > Is there somet

Re: minimize daemon downtime for apt upgrade

On Thu, 8 Apr 2021 10:46:06 -0500 Matt Zagrabelny wrote: > If I wait for a few months to perform an "apt upgrade", many packages > get upgraded. ... > Is there something more elegant? As Dan Ritter already mentioned, you can configure a failover DHCP server, usually a goo

Re: minimize daemon downtime for apt upgrade

On Thu, 8 Apr 2021 10:46:06 -0500 Matt Zagrabelny wrote: > Greetings! > > Scenario: > > I have a Sid desktop computer that acts as a router for my home > network. > > If I wait for a few months to perform an "apt upgrade", many packages > get upgraded. >

Re: minimize daemon downtime for apt upgrade

On Thu, Apr 08, 2021 at 10:46:06AM -0500, Matt Zagrabelny wrote: > Greetings! > > Scenario: > > I have a Sid desktop computer that acts as a router for my home network. > > If I wait for a few months to perform an "apt upgrade", many packages get >

Re: minimize daemon downtime for apt upgrade

Matt Zagrabelny wrote: > I have a Sid desktop computer that acts as a router for my home network. I have a Stable mini-ITX "desktop" computer that acts as a router for my home network. > If I wait for a few months to perform an "apt upgrade", many packages get &

  1   2   3   >