Posts: 74
CGarces
Joined: 21 Apr 2013
#1
Hi!

I have made a sudo apt-get upgrade and 3 key packages has been updated

Code: Select all

$ sudo apt-get upgrade 
Leyendo lista de paquetes... Hecho
Creando árbol de dependencias       
Leyendo la información de estado... Hecho
Calculando la actualización... Listo
Se actualizarán los siguientes paquetes:
  extlinux syslinux syslinux-common
3 actualizados, 0 nuevos se instalarán, 0 para eliminar y 0 no actualizados.
Se necesita descargar 1.596 kB de archivos.
Se utilizarán 450 kB de espacio de disco adicional después de esta operación.
¿Desea continuar? [S/n] s
Des:1 http://softlibre.unizar.es/debian/ jessie/main syslinux amd64 3:6.03+dfsg-5+deb8u1 [188 kB]
Des:2 http://softlibre.unizar.es/debian/ jessie/main syslinux-common all 3:6.03+dfsg-5+deb8u1 [1.230 kB]
Des:3 http://softlibre.unizar.es/debian/ jessie/main extlinux amd64 3:6.03+dfsg-5+deb8u1 [179 kB]
Descargados 1.596 kB en 1s (858 kB/s)
Preconfigurando paquetes ...
Seleccionando el paquete extlinux previamente no seleccionado.
dpkg: considerando la desconfiguración de syslinux-common, ya que lo rompería la instalación de `extlinux' ...
dpkg: sí, se desconfigurará syslinux-common (roto por extlinux)
(Leyendo la base de datos ... 126106 ficheros o directorios instalados actualmente.)
Preparando para desempaquetar ...extlinux_3%3a6.03+dfsg-5+deb8u1_amd64.deb ...
Desconfigurando syslinux-common (2:4.05+dfsg-6+deb7u1) ...
Desempaquetando extlinux (3:6.03+dfsg-5+deb8u1) sobre (2:4.05+dfsg-6+deb7u1) ...
Seleccionando el paquete syslinux-common previamente no seleccionado.
dpkg: considerando la desconfiguración de syslinux, ya que lo rompería la instalación de `syslinux-common' ...
dpkg: sí, se desconfigurará syslinux (roto por syslinux-common)
Preparando para desempaquetar ...syslinux-common_3%3a6.03+dfsg-5+deb8u1_all.deb ...
Desconfigurando syslinux (2:4.05+dfsg-6+deb7u1) ...
Desempaquetando syslinux-common (3:6.03+dfsg-5+deb8u1) sobre (2:4.05+dfsg-6+deb7u1) ...
Seleccionando el paquete syslinux previamente no seleccionado.
Preparando para desempaquetar ...syslinux_3%3a6.03+dfsg-5+deb8u1_amd64.deb ...
Desempaquetando syslinux (3:6.03+dfsg-5+deb8u1) sobre (2:4.05+dfsg-6+deb7u1) ...
Procesando disparadores para man-db (2.7.0.2-5) ...
Configurando syslinux (3:6.03+dfsg-5+deb8u1) ...
Configurando syslinux-common (3:6.03+dfsg-5+deb8u1) ...
Configurando extlinux (3:6.03+dfsg-5+deb8u1) ...

This is a huge problem... why extlinux, syslinux, and syslinux-common has been updated from debian and not from
========= SCRAPER REMOVED AN EMBEDDED LINK HERE ===========
url was:"http://antix.daveserver.info"
linktext was:"http://antix.daveserver.info"
====================================
jessie/nosystemd ?

I think that I I not fix this issues my system will not boot.
This should downgrade to my previous versions...

Code: Select all

apt-get install extlinux=2:4.05+dfsg-6+deb7u1 syslinux=2:4.05+dfsg-6+deb7u1 syslinux-common=2:4.05+dfsg-6+deb7u1
I can't see my previous versions!

Code: Select all

root@antix1:etc/apt/sources.list.d# apt-cache showpkg extlinux
Package: extlinux
Versions: 
3:6.03+dfsg-5+deb8u1 (var/lib/apt/lists/softlibre.unizar.es_debian_dists_jessie_main_binary-amd64_Packages) (var/lib/dpkg/status)
 Description Language: 
                 File: var/lib/apt/lists/softlibre.unizar.es_debian_dists_jessie_main_binary-amd64_Packages
                  MD5: 414e5877200f459574bf4120db85ccc3
 Description Language: en
                 File: var/lib/apt/lists/softlibre.unizar.es_debian_dists_jessie_main_i18n_Translation-en
                  MD5: 414e5877200f459574bf4120db85ccc3
Any ideas?
Posts: 74
CGarces
Joined: 21 Apr 2013
#2
After reboot the system works fine. I'm not sure why.

Why the pagages extlinux syslinux syslinux-common are no longed pinned?
Posts: 1,308
BitJam
Joined: 31 Aug 2009
#3
Did you mention which version of antiX you are using? The recent versions use grub2 as the installed bootloader so those packages should have no effect on booting your system. Even if you were booting your installed system with extlinux, updating those packages should have NO EFFECT on booting your system.

Those packages will only affect new systems you make that use syslinux or extlinux as the bootloader. Uusally this is only live-usbs. Unless this is something new, the fundamental problem is that the sysliux devs goofed when they made an incompatible upgrade to version 6.xx. The 6.xx versions would not work with files from the earlier 4.xx versions and the 4.xx versions would not work with files from the 6.xx versions. So we had to pin these packages to the earlier versions until we had a chance to upgrade the files on our released isos. Then after we upgraded the files we had to unpin the packages. The syslinux devs created a nightmare and we dealt with it as best we could. They took an approach that was almost guaranteed to create as much breakage as possible.