Apt-get update sur smart en buster 10.4

Matériel Jeedom - Hardware La box JEEDOM SMART
#1

Bonjour,
Ce week end, j’ai reussi à mettre Buster sans encombres grace la migration automatisée mise en place par jeedom.
Maintenant je me pose une question concernant la version de buster installée. Actuellement j’ai la 10.4.
Peut on faire un Apt-get update et apt-get upgrade sans risque ?
J’ai essayé apt-get update et j’ai des erreurs que je trouve souvent dans l’installation des dépendances.
notamment l’erreur 502 bad gateway.

apt-get update
Hit:1 http://security.debian.org/debian-security buster/updates InRelease
Hit:2 http://ftp.uk.debian.org/debian buster InRelease                                                           
Hit:3 http://www.deb-multimedia.org buster InRelease                                                             
Get:4 http://ftp.uk.debian.org/debian buster-updates InRelease [51.9 kB]                                         
Hit:6 https://deb.nodesource.com/node_12.x buster InRelease                                            
Hit:7 https://oph.mdrjr.net/meveric all InRelease   
Hit:8 https://oph.mdrjr.net/meveric buster InRelease
Err:5 https://repo.jeedom.com/odroid stable InRelease                                                                                                              
  502  Bad Gateway [IP: 51.210.253.116 443]
Fetched 51.9 kB in 15s (3,388 B/s)
Reading package lists... Done
W: Failed to fetch http://repo.jeedom.com/odroid/dists/stable/InRelease  502  Bad Gateway [IP: 51.210.253.116 443]
W: Some index files failed to download. They have been ignored, or old ones used instead.

Merci pour votre aide

#2

Déjà apt-get est deprecié en buster
Ensuite c’est juste le repo jeedom qui dit qu’il n’y a rien…

#3

ok du coup on fait comment les Maj ? et fait il les faire ?
Merci

#4

Salut,
Je ne savais pas qu’il était déprécié.
Je continue mes sudo apt-get update … upgrade régulièrement

#5

apt au lieux de apt-get

#6

et sur la smart jeedom faut le faire ou pas ?
apt update ca donne ceci

apt update
Hit:2 http://ftp.uk.debian.org/debian buster InRelease                         
Get:3 http://security.debian.org/debian-security buster/updates InRelease [65.4 kB]
Hit:4 http://www.deb-multimedia.org buster InRelease                           
Hit:5 http://ftp.uk.debian.org/debian buster-updates InRelease                 
Hit:6 https://deb.nodesource.com/node_12.x buster InRelease                
Hit:7 https://oph.mdrjr.net/meveric all InRelease                          
Hit:8 https://oph.mdrjr.net/meveric buster InRelease
Err:1 https://repo.jeedom.com/odroid stable InRelease                          
  502  Bad Gateway [IP: 51.178.69.128 443]
Fetched 65.4 kB in 15s (4,280 B/s)
Reading package lists... Done
Building dependency tree       
Reading state information... Done
80 packages can be upgraded. Run 'apt list --upgradable' to see them.
W: Failed to fetch http://repo.jeedom.com/odroid/dists/stable/InRelease  502  Bad Gateway [IP: 51.178.69.128 443]
W: Some index files failed to download. They have been ignored, or old ones used instead.
#7

Bonjour,

D’après mes lectures sur le sujet, apt-get n’est pas déprécié mais apt fortement recommandé à la place car davantage user-friendly. Ce que je confirme :wink:

#8

Bon ben une journée utile, j’ai appris quelque chose.

#9

Le repo Jeedom est pas accessible .
Sur les autres repo qui eux le sont il y a 80 mises à jour dispo.

Après il peut y avoir débat si faire ou pas faire. Moi on m’a appris qu’il faut toujours faire les mises à jour.

#10

du coup faut juste attendre que jeedom valide pour mettre a jour c’est ca ?

#11

Aucune idée je n’ai pas de smart je suis en DIY.

Par contre si tu lances un apt upgrade il va mettre à jour 80 paquets.

#12

mais la dans l’etait si je fais apt upgrade il ne se passe rien c’est ca ?
je n’ai pas osé le faire :slight_smile:

#13

Si si il va se passer quelque chose. La mise à jour de 80 paquets. Qui viennent des autres dépôts.

Comme indiqué si tu lances apt list --upgradable tu vas avoir la liste des 80 mises à jour.

#14

je vais attendre alors que quelqu’un qui a une smart me dise que c’est possible de la faire

#15

À propos, tu avais déjà eu une réponse sur l’erreur du repo de Jeedom ici :

#16

oui la il ne se passait rien mais ca c’etait y a pas mal de temps sur stretch. sur stretch je fais les apt update et upgrade regulierement.

#17

Ben là pareil sous Buster alors change pas tes habitudes :wink:

#18

ok j’essaye ! merci !

#19

je pense que c’est ok par contre il m’a demandé plusieeurs fois un truc avec boot.ini :

File to patch: 
Skip this patch? [y] y
Skipping patch.
2 out of 2 hunks ignored
grep: /boot/boot.ini: No such file or directory
can't find file to patch at input line 5
Perhaps you used the wrong -p or --strip option?
The text leading up to this was:
--------------------------
|diff --git a/boot.ini b/boot.ini
|index 1bfe00b..97c5ba1 100755
|--- a/boot.ini
|+++ b/boot.ini
--------------------------
File to patch: 
Skip this patch? [y] y
Skipping patch.
2 out of 2 hunks ignored
grep: /boot/boot.ini: No such file or directory
can't find file to patch at input line 5
Perhaps you used the wrong -p or --strip option?
The text leading up to this was:
--------------------------
|diff --git a/boot.ini b/boot.ini
|index 97c5ba1..1fd71fc 100755
|--- a/boot.ini
|+++ b/boot.ini
--------------------------
File to patch: 
Skip this patch? [y] y
Skipping patch.
3 out of 3 hunks ignored
can't find file to patch at input line 5
Perhaps you used the wrong -p or --strip option?
The text leading up to this was:
--------------------------
|diff --git a/boot.ini b/boot.ini
|index 1fd71fc..c24642d 100755
|--- a/boot.ini
|+++ b/boot.ini
--------------------------
File to patch:  
Skip this patch? [y] y
Skipping patch.
1 out of 1 hunk ignored
can't find file to patch at input line 3
Perhaps you used the wrong -p or --strip option?
The text leading up to this was:
--------------------------
|--- ./boot.ini	2016-06-10 10:23:48.000000000 +0200
|+++ ./boot-20160608.ini	2016-06-10 10:17:32.000000000 +0200
--------------------------
File to patch: 
Skip this patch? [y] y
Skipping patch.
1 out of 1 hunk ignored
grep: /boot/boot.ini: No such file or directory
can't find file to patch at input line 5
Perhaps you used the wrong -p or --strip option?
The text leading up to this was:
--------------------------
|diff --git a/boot.ini b/boot.ini
|index c24642d..963b93e 100755
|--- a/boot.ini
|+++ b/boot.ini
--------------------------
File to patch: 
Skip this patch? [y] y
Skipping patch.
1 out of 1 hunk ignored
grep: /boot/boot.ini: No such file or directory
can't find file to patch at input line 5
Perhaps you used the wrong -p or --strip option?
The text leading up to this was:
--------------------------
|diff --git a/boot.ini b/boot.ini
|index d96826b..7a697ca 100755
|--- a/boot.ini
|+++ b/boot.ini
--------------------------
File to patch: 
Skip this patch? [y] y
Skipping patch.
1 out of 1 hunk ignored
grep: /boot/boot.ini: No such file or directory
can't find file to patch at input line 5
Perhaps you used the wrong -p or --strip option?
The text leading up to this was:
--------------------------
|diff --git a/boot.ini b/boot.ini
|index 7a697ca..4d6bcc2 100755
|--- a/boot.ini
|+++ b/boot.ini
--------------------------
File to patch: 
Skip this patch? [y] y
Skipping patch.
1 out of 1 hunk ignored
grep: /boot/boot.ini: No such file or directory
can't find file to patch at input line 3
Perhaps you used the wrong -p or --strip option?
The text leading up to this was:
--------------------------
|--- boot/boot-20160911-2.ini	2016-09-11 12:32:40.000000000 +0200
|+++ boot/boot.ini	2016-09-11 12:34:02.000000000 +0200
--------------------------
File to patch: 
Skip this patch? [y] y
Skipping patch.
1 out of 1 hunk ignored
grep: /boot/boot.ini: No such file or directory
can't find file to patch at input line 3
Perhaps you used the wrong -p or --strip option?
The text leading up to this was:
--------------------------
|--- a/boot.ini	2016-09-26 13:59:04.000000000 +0200
|+++ b/boot.ini	2016-09-26 14:39:44.000000000 +0200
--------------------------
File to patch: 
Skip this patch? [y] y
Skipping patch.
2 out of 2 hunks ignored
grep: /boot/boot.ini: No such file or directory
grep: /boot/boot.ini: No such file or directory
grep: /boot/boot.ini: No such file or directory
can't find file to patch at input line 3
Perhaps you used the wrong -p or --strip option?
The text leading up to this was:
--------------------------
|--- boot/boot.ini.bak-20161228	2016-12-28 22:08:52.000000000 +0100
|+++ boot/boot.ini	2016-12-28 22:09:52.000000000 +0100
--------------------------
File to patch: 
Skip this patch? [y] y
Skipping patch.
1 out of 1 hunk ignored
#20

Je l’ai fait sur ma Smart et aucun souci, j’ai eu environs aussi 80 paquets de mis à jour.