Bonjour,
Le dimanche 25 février 2024, Hugues MORIN-TRENEULE a écrit...
> Néanmoins, il me reste un espace non utilisé en fin de disque.
> Quand j'aurai un moment, je rajouterai quelques giga sur / afin de ne plus
> me retrouver en difficulté par manque d'espace.
Je ne sais pas si
Bonjour
Désolé pour ce retour tardif.
Je vous confirme que tout est OK, mon système fonctionne normalement et je
n'ai pour l'heure rencontré aucun probleme.
Oui effectivement, les partitions sont complètement entremêlées et
réparties sur 3 partitions.
sda1 qui contient /
sda2 qui contient sda5
Le 17 février 2024 Alban Vidal a écrit :
> Pour éviter des soucis d'espace disque à l'avenir, je pense qu'il serait
> judicieux de redimensionner un peu les partitions, en en retirant un peu dans
> le /opt ou /home pour en mettre un peu plus sur la racine (/), 2 ou 3G par
> exemple.
Je pense que
Bonsoir Hugues,
Très bonne nouvelle !
Pour éviter des soucis d'espace disque à l'avenir, je pense qu'il serait
judicieux de redimensionner un peu les partitions, en en retirant un peu dans
le /opt ou /home pour en mettre un peu plus sur la racine (/), 2 ou 3G par
exemple.
Pour ce faire, le
Re bonjour
Je viens d'exécuter le apt full-upgrade.
Je pensais que ça allait prendre un peu de temps mais ça a été rapide, tous
les paquets étaient déjà à jour :)
J'ai redémarré et tout semble fonctionner.
J'ai effectué quelques mises a jour et preparé l'upgrade a la version
suivante comme
Salut
Merci Gilles pour ta confirmation
J'ai plus qu'a ... ;)
Bonne journée
Hugues
Le ven. 16 févr. 2024 à 18:56, Gilles Mocellin <
gilles.mocel...@nuagelibre.org> a écrit :
> Le vendredi 16 février 2024, 18:43:58 CET Hugues MORIN-TRENEULE a écrit :
> > Salut
> >
> > Merci pour tous ces
Le vendredi 16 février 2024, 18:43:58 CET Hugues MORIN-TRENEULE a écrit :
> Salut
>
> Merci pour tous ces conseils, je garde ça précieusement pour les prochains
> upgrade car j'ai l'intention d'upgrader jusqu'à la dernière version stable.
>
> Sinon, j'ai lancé le processus d'upgrade comme nous
écrivant, j'upgrade de bien de
> > Stretch à Buster ;-)
>
> Tant mieux ;)
> C'est toujours bon de préciser pour les futurs lecteurs !
>
>
> > Donc je récapitule pour voir si j'ai bien compris: - ps pour trouver
> > le PID d'apt - killall -9 "PID d'apt" - d
Le lundi 12 février 2024, 19:23:39 CET Hugues MORIN-TRENEULE a écrit :
> Salut
>
> Merci pour l'info
>
> Malheureusement même si j'entrevois de quoi tu parles, je ne sais pas trop
> comment faire en pratique.
>
> Donc si je comprends bien, maintenant que j'ai fait de la place, il faut
> que
On 13 Feb 2024 10:31, Hugues MORIN-TRENEULE wrote:
@zithro / Cyril: je me suis trompé en écrivant, j'upgrade de bien de
Stretch à Buster ;-)
Tant mieux ;)
C'est toujours bon de préciser pour les futurs lecteurs !
Donc je récapitule pour voir si j'ai bien compris: - ps pour trouver
le PID
Bonjour
Merci à tous pour votre aide :)
@zithro / Cyril: je me suis trompé en écrivant, j'upgrade de bien de
Stretch à Buster ;-)
Donc je récapitule pour voir si j'ai bien compris:
- ps pour trouver le PID d'apt
- killall -9 "PID d'apt"
- dpkg-reconfigure
- apt upgrade --withou
Le 12 février 2024 Hugues MORIN-TRENEULE a écrit :
> Avec le recul, aujourd'hui, je ne ferai que des partitions pour /home, /var
> et /opt.
/home et /opt il faut voir selon tes applis. Mais si /var est saturé ça
bloque tout le système à cause des logs qui ne peuvent plus se faire.
> Est ce que
On Mon, Feb 12, 2024 at 8:57 PM Gilles Mocellin
wrote:
>
> Le lundi 12 février 2024, 19:23:39 CET Hugues MORIN-TRENEULE a écrit :
> > Salut
> >
> > Merci pour l'info
> >
> > Malheureusement même si j'entrevois de quoi tu parles, je ne sais pas trop
> > comment faire en pratique.
> >
> > Donc
On 12 Feb 2024 08:00, Hugues MORIN-TRENEULE wrote:
Bonjour a tous
Je reviens vers vous car je ne sais pas comment m'y prendre pour réparer un
crash lors d'un apt full-upgrade lors d'un passage de Stretch a Bullseye.
Ca fonctionne peut-être, mais ce n'est pas la manière recommandée
On 12/02/2024 19:23:39, Hugues MORIN-TRENEULE wrote:
> Pour trouver le pid d'apt, c'est à l'aide de la commande ps?
> Et apres kill "n° de pid"
> Est ce qu'il y a autre chose a faire pour killer le processus d'apt?
Tu peux tuer un processus en utilisant son nom avec la commande killall, qui
Salut
Merci pour l'info
Malheureusement même si j'entrevois de quoi tu parles, je ne sais pas trop
comment faire en pratique.
Donc si je comprends bien, maintenant que j'ai fait de la place, il faut
que je relance la commande apt full-upgrade
Mais avant cela, je dois killer le pid de apt et
Salut
C'est un système qui à l'origine avait été installé en Wheezy ou Jessie et
que j'ai upgradé.
Je n'avais pas autant de connaissance que maintenant et il m'avait semblé
plus judicieux de faire une partition par montage.
Je me disais que ca serait surement plus simple de restaurer le système
Le 12 février 2024 Hugues MORIN-TRENEULE a écrit :
> J'ai effectivement vu ce message mais je n'en avais pas compris la raison.
> Néanmoins, au vue de df -TPh, je m’aperçois que ma partition racine et
> /boot son bien "chargées".
> Est ce que le problème pourrait provenir de la?
Le message
rdialement,
> Alban
>
>
> Le 12 février 2024 08:00:00 GMT+01:00, Hugues MORIN-TRENEULE <
> mor...@gmail.com> a écrit :
>
>> Bonjour a tous
>>
>>
>> Je reviens vers vous car je ne sais pas comment m'y prendre pour réparer
>> un crash lors d'
gues MORIN-TRENEULE
a écrit :
>Bonjour a tous
>
>
>Je reviens vers vous car je ne sais pas comment m'y prendre pour réparer un
>crash lors d'un apt full-upgrade lors d'un passage de Stretch a Bullseye.
>
>Il y a quelques temps vos conseils et explications mon permis de de mettre
Bonjour a tous
Je reviens vers vous car je ne sais pas comment m'y prendre pour réparer un
crash lors d'un apt full-upgrade lors d'un passage de Stretch a Bullseye.
Il y a quelques temps vos conseils et explications mon permis de de mettre
a jours mon Stretch afin de le préparer à l'upgrade
volatile n'a effectivement aucune utilité
(sur mon système).
J'ai ensuite checker les dépôt archive.debian. org afin de vérifier
s'il contenait des mises à jour mais il n'y en avait pas.
J'ai poursuivi avec les dépôts ELTS que cite Daniel en suivant la
procédure qu'il a donné.
Mon Stretch
Hello,
Il y a trop d'écart entre Stretch et Bookworm,
et des distributions Debian ne sont plus maintenues.
Dans ces conditions, si on a une partition /home séparée
de la partition système, mieux vaut faire une installation à neuf,
ça va très vite ~15Go.
> ...
> J'ai alors lancé dans la fou
ensuite checker les dépôt archive.debian. org afin de vérifier s'il
contenait des mises à jour mais il n'y en avait pas.
J'ai poursuivi avec les dépôts ELTS que cite Daniel en suivant la procédure
qu'il a donné.
Mon Stretch étant alors à jour j'ai commencé l'upgrade vers Buster.
La mise à niveau
Bonjour.
Depuis l'année dernière, Debian n'assure plus le support de Stretch (fin
du support LTS). Un support partiel reste possible via le projet
Extended Long Term Support (ELTS, https://wiki.debian.org/LTS/Extended ;
pour 5 ans, soit jusqu'au 2027-06-30). Il faut supprimer les dépôts
Bonjour
Merci à tous pour vos réponses et vos conseils, maintenant ... yapluka ;-)
Je vais faire des upgrade successif car je tiens a garder la configuration
de certains programme.
Concernant les dépôts "security" et "volatile", je ne sais quels sont les
paquets qui en dépendent.
Je vais
Le 29 août 2023 Hugues MORIN-TRENEULE a écrit :
> Concernant les dépôts "security" et "volatile", existe-t-il aussi des
> dépôts archive que je pourrai utiliser?
Le mieux est de les commenter durant les upgrade et de les rebrancher
seulement quand tout est stabilisé pour un ultime upgrade. C'est
Bonjour,
Le 2023-08-29 13:53, Hugues MORIN-TRENEULE a écrit :
Pour le dépot principal (http://ftp.fr.debian.org/debian/ stretch) ,
en cherchant, j'ai trouvé le depot archive Debian:
http://archive.debian.org/debian
Est ce que vous pourriez me confirmer qu'il me permettra de mettre les
paquets
Le Tue, 29 Aug 2023 13:53:13 +0200,
Hugues MORIN-TRENEULE a écrit :
> Pour le dépot principal (http://ftp.fr.debian.org/debian/ stretch) ,
> en cherchant, j'ai trouvé le depot archive Debian:
> http://archive.debian.org/debian
> Est ce que vous pourriez me confirmer qu'il me permett
Salut à tous
J'ai fait une boulette, je n'ai pas upgradé .
A force de me procrastiner l'upgrade d'une machine sous Stretch dont je me
sers occasionnellement, je me trouve un peu embêter aujourd'hui.
En voulant faire un petit check des mises à jour, je me suis aperçu que les
dépôts Stretch
Hi,
On Mon, May 15, 2023 at 08:11:50PM +0530, amit agari wrote:
> Has ebtables package been removed from Debian 9 stretch distribution?
stretch is EOL so the entire distribution has been "removed" to
archive.debian.org. But after putting archive.debian.org in your
/etc/apt/sou
On Mon 15 May 2023 at 20:11:50 (+0530), amit agari wrote:
> Has ebtables package been removed from Debian 9 stretch distribution?
http://archive.debian.org/debian/pool/main/e/ebtables/
appears to have ebtables_2.0.10.4-3.5+b1_amd64.deb
which is probably what you're looking for.
Cheers,
David.
Hi,
Has ebtables package been removed from Debian 9 stretch distribution?
Regards
On Thu, 27 Apr 2023, Greg Wooledge wrote:
On Thu, Apr 27, 2023 at 05:08:10PM +0800, justzx wrote:
Error message:
Ign:39 http://cdn-fastly.deb.debian.org/debian-security
stretch/updates/non-free Sources
Stretch (Debian 9) probably no longer has a debian-security repo, if
it was recently
On Thu, 27 Apr 2023 17:08:10 +0800
justzx wrote:
Hello justzx,
>W: The repository 'http://cdn-fastly.deb.debian.org/debian-current
>stretch-backports Release' does not have a Release file.
Usually means your url is malformed. The 404 errors later seem to
corroborate this.
See http
On Thu, Apr 27, 2023 at 05:08:10PM +0800, justzx wrote:
> Error message:
>
> Ign:39 http://cdn-fastly.deb.debian.org/debian-security
> stretch/updates/non-free Sources
Stretch (Debian 9) probably no longer has a debian-security repo, if
it was recently moved to the archive. Remo
Error message:
Ign:39 http://cdn-fastly.deb.debian.org/debian-security
stretch/updates/non-free Sources
Ign:40 http://cdn-fastly.deb.debian.org/debian-security
stretch/updates/contrib Sources
Ign:41 http://cdn-fastly.deb.debian.org/debian-security
stretch/updates/main amd64 Packages
Ign:42 http
On Sat, 15 Apr 2023 05:34:36 +0100 (BST)
Tim Woodall wrote:
> On Fri, 14 Apr 2023, Charles Curley wrote:
>
> [...]
> [...]
> [...]
> That page is out of date. On the LTS page itself:
>
> Debian 9 "Stretch"
>
> i386, amd64, armel, armhf
Charles Curley writes:
> On Fri, 14 Apr 2023 19:41:37 +0100
> Brian wrote:
>
>> I thought stretch is unsupported by Debian. Where did the update come
>> from?
>
> Stretch is oldoldstable, and under LTS support.
> https://www.debian.org/releases/
Actually LTS su
On Sat, 15 Apr 2023 at 04:24, Tim Woodall wrote:
> On Fri, 14 Apr 2023, Brian wrote:
> >>> I thought stretch is unsupported by Debian. Where did the update come
> >>> from?
> It's been moved to archive.debian.org. Just hasn't been deleted from the
> main rep
On Fri, 14 Apr 2023, Charles Curley wrote:
On Fri, 14 Apr 2023 19:41:37 +0100
Brian wrote:
I thought stretch is unsupported by Debian. Where did the update come
from?
Stretch is oldoldstable, and under LTS support.
https://www.debian.org/releases/
That page is out of date. On the LTS
On Fri, 14 Apr 2023, Brian wrote:
I thought stretch is unsupported by Debian. Where did the update come from?
It may or may not be supported, but it's still there AFAICT:
[DIR] binary-amd64/ 2021-08-14 07:43
[ ] Packages.gz 2020-07-18 10:409.2M
[ ] base-files_9.9
On Fri, 14 Apr 2023 19:41:37 +0100
Brian wrote:
> I thought stretch is unsupported by Debian. Where did the update come
> from?
Stretch is oldoldstable, and under LTS support.
https://www.debian.org/releases/
I would encourage the original poster to consider installing bullseye
rathe
On Fri, 14 Apr 2023 davidson wrote:
On Fri, 14 Apr 2023 Brian wrote:
On Fri 14 Apr 2023 at 18:48:06 +0200, Bernard wrote:
Hi to Everyone,
I am writing from my laptop on Ubuntu, but the problem I have is
with my Desktop running Debian Stretch.
Having unfortunately Okayed a proposal
On 2023-04-14 at 15:53, davidson wrote:
> On Fri, 14 Apr 2023 Brian wrote:
>
>> On Fri 14 Apr 2023 at 18:48:06 +0200, Bernard wrote:
>>
>>> Hi to Everyone,
>>>
>>> I am writing from my laptop on Ubuntu, but the problem I have is
>>> with m
On Fri, 14 Apr 2023 Brian wrote:
On Fri 14 Apr 2023 at 18:48:06 +0200, Bernard wrote:
Hi to Everyone,
I am writing from my laptop on Ubuntu, but the problem I have is
with my Desktop running Debian Stretch.
Having unfortunately Okayed a proposal for an update (which I
rarely do…), upon
On Fri 14 Apr 2023 at 19:41:37 (+0100), Brian wrote:
> On Fri 14 Apr 2023 at 18:48:06 +0200, Bernard wrote:
> > I am writing from my laptop on Ubuntu, but the problem I have is with my
> > Desktop running Debian Stretch.
> > Having unfortunately Okayed a proposal for an upda
Bernard wrote:
...
> How can I get back to my old system prior to this failed update ? What
> else can I do ?
>
> Thanks in advance for your help in restoring my system
take a look at the files in /var/log/apt
history should tell you what was updated last and you could
try to install a
Hi to Everyone,
I am writing from my laptop on Ubuntu, but the problem I have is with my
Desktop running Debian Stretch.
Having unfortunately Okayed a proposal for an update (which I rarely
do…), upon restarting the system fails to launch X server.
My /var/log/messages are available at
http
mattias:
> Ãr verkligen wine 5.1x det lägsta för stretch?
Enl.
https://packages.debian.org/search?keywords=wine=names=all=all
så har stretch v1.8.7, ska du ha 5.0.3 är den anpassad till bullseye.
> Går inte uppgradera då hälften av speglarna är döda
Finns det åtminstonde en
Jaja jag vet att stretch är tämligen gammaltMen har inget valÄr verkligen wine 5.1x det lägsta för stretch?Går inte uppgradera då hälften av speglarna är dödaMen går väll inte ta wine från debian 10 och köra in? Skickades från E-post för Windows
On 09/13/2022 08:28 AM, Roger Price wrote:
On Tue, 13 Sep 2022, Richard Owlett wrote:
It's been so long since I set up Debian I've forgotten how to set
timing for going into hibernation. It's currently set for a much to primare panel has
large a delay.
Where do I look for instructions and
On Tue, 13 Sep 2022, Richard Owlett wrote:
It's been so long since I set up Debian I've forgotten how to set timing for
going into hibernation. It's currently set for a much to large a delay.
Where do I look for instructions and descriptions?
I use Right Click on screen, and then
It's been so long since I set up Debian I've forgotten how to set timing
for going into hibernation. It's currently set for a much to large a delay.
Where do I look for instructions and descriptions?
TIA
ior a
la que trae Strecth (3.26).
LO 7.3.3.2 funciona sin problemas.
El bug (aunque más que un bug más bien es un nuevo requerimiento, pero
que debería estar indicado en alguna parte) lo he puesto aquí:
Bug 149813 - LibreOffice 7.3.4 not opening on Debian Stretch, requires
libnss3.so version 3
Hola,
Pues eso, que hoy finaliza el soporte extendido para Debian 9, que ya
no tendrá actualizaciones:
[SECURITY] [DLA 3067-1] Debian 9 Long Term Support reaching end-of-life
https://lists.debian.org/debian-lts-announce/2022/07/msg2.html
A quienes la estamos usando, nos toca actualizar a
On 4/05/22 18:57, Tixy wrote:
On Wed, 2022-05-04 at 00:44 +0300, IL Ka wrote:
Linux kernel is backward compatible. Linus calls it "we do not break
userspace".
That means _old_ applications should work on new kernel
There's also the issue of what config options the kernel is built with.
I'm
On Wed, 2022-05-04 at 00:44 +0300, IL Ka wrote:
> Linux kernel is backward compatible. Linus calls it "we do not break
> userspace".
> That means _old_ applications should work on new kernel
There's also the issue of what config options the kernel is built with.
I'm sure there's been at least
Linux kernel is backward compatible. Linus calls it "we do not break
userspace".
That means _old_ applications should work on new kernel
On Wed, May 4, 2022 at 12:40 AM Richard Hector
wrote:
> Hi all,
>
> For various reasons, I have some stretch LXC containers, on a buste
Hi all,
For various reasons, I have some stretch LXC containers, on a buster
host that I now need to upgrade. That will mean they end up running on
buster's 5.10 kernel.
Is that likely to be a problem?
If so, I guess I can leave the host on buster's kernel for the time
being, but that's
Thank you for the additional information you have supplied regarding
this Bug report.
This is an automatically generated reply to let you know your message
has been received.
Your message is being forwarded to the package maintainers and other
interested parties for their attention; they will
Hi,
for the reference, the issue is solved by this config below.
Ales
---
cat /etc/network/interfaces
auto lo
iface lo inet loopback
#auto ens3f0
#iface ens3f0 inet manual
#auto ens3f1
#iface ens3f1 inet manual
allow-hotplug ens3f0
iface ens3f0 inet manual
piorunz wrote:
...
> New install would change network interface name anyway.
net.ifnames=0 works for me in that regards.
songbird
On 2021-08-18, mick crane wrote:
>>
>> Not sure I see how that analogy applies.
>>
>> If the 'water' is the knowledge of upgrading Debian releases as present
>> in the official release notes, then the chemical analysis is the advice
>> on upgrading from this list? In that case, it seems the
On 20/08/2021 12:40, Greg Wooledge wrote:
This line of thought probably comes from Windows, when any hardware
change causes problems, drivers installation, it can refuse to boot,
etc. Not a problem on Debian :)
It can be. Any change to the hardware, or even the mobo firmware, can
cause PCI
On Fri, Aug 20, 2021 at 11:55:32AM +0100, piorunz wrote:
> On 19/08/2021 13:21, songbird wrote:
> > when i changed motherboards i figured it was worth a fresh
> > install
>
> This line of thought probably comes from Windows, when any hardware
> change causes problems, drivers installation, it can
On 19/08/2021 13:21, songbird wrote:
when i changed motherboards i figured it was worth a fresh
install
This line of thought probably comes from Windows, when any hardware
change causes problems, drivers installation, it can refuse to boot,
etc. Not a problem on Debian :)
Motherboard or even
songbird writes:
> Anssi Saari wrote:
> ...
>> And yes, the working upgrades are the reason I've stuck with Debian
>> since Hamm. My ever evolving desktop computer is on its second
>> installation now since I reinstalled when I switched to 64-bits
>> somewhere in the decade before last.
>
On 2021-08-18, Tixy wrote:
>>
>> With a normal system, a shortened version of the upgrade procedure
>> without the warnings and pre-checks and post-checks might be OK,
>> but this is *Gene*. We know he does not have normal systems.
>>
>> He needs *all* of the warnings.
>>
>
> I agree with all
rhkra...@gmail.com wrote:
...
> Aside: I have never (to the best of my recollection) done an upgrade from one
> version to the next, I install the new version on a clean disk (or new
> system)
> -- the only time I could envision doing an upgrade would be if stable became
> a
> rolling
Anssi Saari wrote:
...
> And yes, the working upgrades are the reason I've stuck with Debian
> since Hamm. My ever evolving desktop computer is on its second
> installation now since I reinstalled when I switched to 64-bits
> somewhere in the decade before last.
when i changed motherboards i
On 2021-08-17 7:21 p.m., Brian wrote:
> On Tue 17 Aug 2021 at 22:48:34 +, Andrew M.A. Cater wrote:
>
>> On Tue, Aug 17, 2021 at 11:05:44PM +0100, Brian wrote:
>>> On Tue 17 Aug 2021 at 16:54:54 -0400, Gene Heskett wrote:
>>>
>>>> Where do I f
Hi
On 2021-08-17 6:05 p.m., Brian wrote:
> On Tue 17 Aug 2021 at 16:54:54 -0400, Gene Heskett wrote:
>
>> Where do I find the recipe to update stretch to buster?
>
> What, in this helpful thread, do you find difficult to understand?
>
> You have a collection of im
On Wed, Aug 18, 2021 at 11:26:18AM -0500, David Wright wrote:
> On Wed 18 Aug 2021 at 07:39:26 (-0400), The Wanderer wrote:
> > On 2021-08-17 at 13:36, Brian wrote:
> > > On Tue 17 Aug 2021 at 16:00:57 +, Andrew M.A. Cater wrote:
> >
> > >> Do the update to Buster - take it as slow as you
On Wednesday 18 August 2021 08:05:43 Andrew M.A. Cater wrote:
> On Wed, Aug 18, 2021 at 09:12:24AM +0100, Tixy wrote:
> > On Wed, 2021-08-18 at 09:03 +0200, to...@tuxteam.de wrote:
> > > On Tue, Aug 17, 2021 at 10:01:32PM -0400, Greg Wooledge wrote:
> > > > On Tue, Aug 17, 2021 at 09:48:10PM
On Wed 18 Aug 2021 at 07:39:26 (-0400), The Wanderer wrote:
> On 2021-08-17 at 13:36, Brian wrote:
> > On Tue 17 Aug 2021 at 16:00:57 +, Andrew M.A. Cater wrote:
>
> >> Do the update to Buster - take it as slow as you need to. Bring it
> >> bang up to date.
> >>
> >> For the Buster to
rhkra...@gmail.com writes:
> But, if I did do an upgrade from one version to the next, it would not
> surprise me if I forgot to read the upgrade notes.
For me, the instructions for upgrading in the release notes are the only
way I know how to find out how to upgrade Debian from one release to
On Wednesday, August 18, 2021 07:39:26 AM The Wanderer wrote:
> On 2021-08-17 at 13:36, Brian wrote:
> > Of course! Do users not do this as a standard procedure? :)
>
> I don't - because I don't upgrade from one stable release to another; I
> track testing, continuously, throughout the
On Wed, Aug 18, 2021 at 09:12:24AM +0100, Tixy wrote:
> On Wed, 2021-08-18 at 09:03 +0200, to...@tuxteam.de wrote:
> > On Tue, Aug 17, 2021 at 10:01:32PM -0400, Greg Wooledge wrote:
> > > On Tue, Aug 17, 2021 at 09:48:10PM -0400, Gene Heskett wrote:
> > > > On Tuesday 17 August 2021 18:48:34
On 2021-08-17 at 13:36, Brian wrote:
> On Tue 17 Aug 2021 at 16:00:57 +, Andrew M.A. Cater wrote:
>> Do the update to Buster - take it as slow as you need to. Bring it
>> bang up to date.
>>
>> For the Buster to Bullseye -
>>
>> READ RELEASE NOTES :)
>
> Of course! Do users not do this as
d happen, and you appear not to have noticed, is
> that the definition of "oldstable" changed under your feet from
> "stretch" to "buster". So all of a sudden, you were 2588 packages out
> of date for your main repository.
What I interpreted Gene's statement abo
On 18/08/2021 07:57, to...@tuxteam.de wrote:
On Wed, Aug 18, 2021 at 01:53:16AM +0100, piorunz wrote:
Why are you repeating this?
Because Andrew is a nice person. Which I do appreciate highly.
Why shouldn't he? Why would you not want him to do?
Please see my other reply:
"> Amazing
On 2021-08-18 09:32, Tixy wrote:
On Wed, 2021-08-18 at 09:06 +0100, mick crane wrote:
On 2021-08-18 08:40, Tixy wrote:
> I agree with all of the above, but as the saying goes: 'you can lead a
> horse to water, but you can't make him drink'.
You can't blame a horse for wanting to see the
On 18/08/2021 08:40, Tixy wrote:
I agree with all of the above, but as the saying goes: 'you can lead a
horse to water, but you can't make him drink'.
Amazing analogy. Gene has been given plenty of water, but he keeps
coming back for more while not taking even one sip yet. He failed to
RTFM
On Tuesday 17 August 2021 18:48:34 Andrew M.A. Cater wrote:
> On Tue, Aug 17, 2021 at 11:05:44PM +0100, Brian wrote:
> > On Tue 17 Aug 2021 at 16:54:54 -0400, Gene Heskett wrote:
> > > Where do I find the recipe to update stretch to buster?
> >
> > What, in th
On Wed, 2021-08-18 at 09:06 +0100, mick crane wrote:
> On 2021-08-18 08:40, Tixy wrote:
>
> > I agree with all of the above, but as the saying goes: 'you can lead a
> > horse to water, but you can't make him drink'.
> You can't blame a horse for wanting to see the chemical analysis of the
>
On Wed, 2021-08-18 at 09:03 +0200, to...@tuxteam.de wrote:
> On Tue, Aug 17, 2021 at 10:01:32PM -0400, Greg Wooledge wrote:
> > On Tue, Aug 17, 2021 at 09:48:10PM -0400, Gene Heskett wrote:
> > > On Tuesday 17 August 2021 18:48:34 Andrew M.A. Cater wrote:
> > > > [an abridged version of the
On 2021-08-18 08:40, Tixy wrote:
I agree with all of the above, but as the saying goes: 'you can lead a
horse to water, but you can't make him drink'.
You can't blame a horse for wanting to see the chemical analysis of the
water and checking the vicinity for corpses.
mick
--
Key ID
On Tue, 2021-08-17 at 22:01 -0400, Greg Wooledge wrote:
> On Tue, Aug 17, 2021 at 09:48:10PM -0400, Gene Heskett wrote:
> > On Tuesday 17 August 2021 18:48:34 Andrew M.A. Cater wrote:
> > > [an abridged version of the release notes]
>
> > Thank you Andy, thats more of the recipe I need to follow.
On Tue, Aug 17, 2021 at 10:01:32PM -0400, Greg Wooledge wrote:
> On Tue, Aug 17, 2021 at 09:48:10PM -0400, Gene Heskett wrote:
> > On Tuesday 17 August 2021 18:48:34 Andrew M.A. Cater wrote:
> > > [an abridged version of the release notes]
>
> > Thank you Andy, thats more of the recipe I need to
On Wed, Aug 18, 2021 at 01:53:16AM +0100, piorunz wrote:
> On 17/08/2021 23:48, Andrew M.A. Cater wrote:
> >Gene,
> >
> >You have two upgrades to do.
> >
> >One from stretch -> buster. 9-10 That takes you from 2017 -> 2019.
> >
> >If you can
On Wed 18 Aug 2021 at 01:53:16 (+0100), piorunz wrote:
> On 17/08/2021 23:48, Andrew M.A. Cater wrote:
> > Gene,
> >
> > You have two upgrades to do.
> >
> > One from stretch -> buster. 9-10 That takes you from 2017 -> 2019.
> >
> > If you can
On Tue, Aug 17, 2021 at 09:48:10PM -0400, Gene Heskett wrote:
> On Tuesday 17 August 2021 18:48:34 Andrew M.A. Cater wrote:
> > [an abridged version of the release notes]
> Thank you Andy, thats more of the recipe I need to follow.
>
> Cheers, Gene Heskett
See, *this* is exactly what I tried to
Dan Ritter wrote:
...
> Tell us more about what you're doing, but also remember that you
> can't skip stable versions in an upgrade - you need to upgrade
> from stretch to buster, then to bullseye.
yes.
plus it is good to get rid of cruft if you don't need it so
i woul
On Tuesday 17 August 2021 18:48:34 Andrew M.A. Cater wrote:
> On Tue, Aug 17, 2021 at 11:05:44PM +0100, Brian wrote:
> > On Tue 17 Aug 2021 at 16:54:54 -0400, Gene Heskett wrote:
> > > Where do I find the recipe to update stretch to buster?
> >
> > What, in th
On Tue, Aug 17 2021 at 08:01:46 PM, Gene Heskett wrote:
> On Tuesday 17 August 2021 16:57:44 Greg Wooledge wrote:
>
>> On Tue, Aug 17, 2021 at 04:54:54PM -0400, Gene Heskett wrote:
>> > Where do I find the recipe to update stretch to buster?
>>
>> It's still at
&g
On Tuesday 17 August 2021 17:45:49 piorunz wrote:
> On 17/08/2021 21:57, Greg Wooledge wrote:
> > On Tue, Aug 17, 2021 at 04:54:54PM -0400, Gene Heskett wrote:
> >> Where do I find the recipe to update stretch to buster?
> >
> > It's still at
> > <https
On 17/08/2021 23:48, Andrew M.A. Cater wrote:
Gene,
You have two upgrades to do.
One from stretch -> buster. 9-10 That takes you from 2017 -> 2019.
If you can reduce your /etc/apt/sources.list by commenting out third party
repositories like Trinity, that will help.
Why are you rep
On Tuesday 17 August 2021 16:57:44 Greg Wooledge wrote:
> On Tue, Aug 17, 2021 at 04:54:54PM -0400, Gene Heskett wrote:
> > Where do I find the recipe to update stretch to buster?
>
> It's still at
> <https://www.debian.org/releases/buster/amd64/release-notes/>.
Thats fin
On Tue 17 Aug 2021 at 22:48:34 +, Andrew M.A. Cater wrote:
> On Tue, Aug 17, 2021 at 11:05:44PM +0100, Brian wrote:
> > On Tue 17 Aug 2021 at 16:54:54 -0400, Gene Heskett wrote:
> >
> > > Where do I find the recipe to update stretch to buster?
> >
> >
1 - 100 of 4398 matches
Mail list logo
