Welcome, Guest. Please login or register.
Did you miss your activation email?

Author Topic:  A day for caution today  (Read 3591 times)

Offline dibl

  • siduction community member
  • Global Moderator
  • User
  • *****
  • Posts: 2.358
    • Land of the Buckeye
A day for caution today
« on: 2016/11/22, 13:28:37 »

Looks like turbulence in the repos today.  On my desktop:


Code: [Select]
The following packages will be REMOVED:
  build-essential debhelper dh-autoreconf dh-strip-nondeterminism equivs g++ g++-4.8 g++-4.9 g++-5 g++-6 libc6-dev libcups2-dev
  libcupsimage2-dev libexif-dev libexpat1-dev libglib2.0-dev libgphoto2-dev libjpeg-dev libjpeg62-turbo-dev libkf5khtml-dev
  libkf5kjs-dev libpci-dev libpcre3-dev libpng-dev libpython-dev libpython2.7-dev libpython3-dev libpython3.5-dev libsnmp-dev
  libstdc++-4.8-dev libstdc++-4.9-dev libstdc++-5-dev libstdc++-6-dev libtiff5-dev libtool libtool-bin python-dev python2.7-dev
  python3-dev python3.5-dev zlib1g-dev
The following NEW packages will be installed:
  libxtables12 linux-headers-4.8.10-towo.1-siduction-amd64 linux-image-4.8.10-towo.1-siduction-amd64
The following packages have been kept back:
  libc6
...


On my laptop, there were no removals so I went ahead with d-u.  It ended this way:


Code: [Select]
root@hp-350g:/home/don# apt-get -f install
Reading package lists... Done
Building dependency tree       
Reading state information... Done
Correcting dependencies... Done
The following additional packages will be installed:
 libxtables12
The following NEW packages will be installed:
 libxtables12
0 upgraded, 1 newly installed, 0 to remove and 48 not upgraded.
10 not fully installed or removed.
Need to get 0 B/75.1 kB of archives.
After this operation, 134 kB of additional disk space will be used.
Do you want to continue? [Y/n] 
(Reading database ... 217599 files and directories currently installed.)
Preparing to unpack .../libxtables12_1.6.0+snapshot20161117-2_amd64.deb ...
Unpacking libxtables12:amd64 (1.6.0+snapshot20161117-2) ...
dpkg: error processing archive /var/cache/apt/archives/libxtables12_1.6.0+snapshot20161
117-2_amd64.deb (--unpack):
trying to overwrite '/usr/lib/x86_64-linux-gnu/libxtables.so.12.0.0', which is also in
package libxtables11:amd64 1.6.0+snapshot20161117-1
dpkg-deb: error: subprocess paste was killed by signal (Broken pipe)
Errors were encountered while processing:
/var/cache/apt/archives/libxtables12_1.6.0+snapshot20161117-2_amd64.deb
E: Sub-process /usr/bin/dpkg returned an error code (1)


So, a good day for waiting.
System76 Oryx Pro, Intel Core i7-11800H, SSD 970 EVO Plus;  Asus ROG STRIX X299-E, Core i7-7740X, Nvidia GTX-1060, dual monitors, SSD 860 EVO

Offline drb

  • User
  • Posts: 165
Re: A day for caution today
« Reply #1 on: 2016/11/22, 14:16:02 »
Bug has been reported and  libxtables12_1.6.0+snapshot20161117-3 will fix it

Offline michaaa62

  • User
  • Posts: 299
Re: A day for caution today
« Reply #2 on: 2016/11/22, 16:35:58 »
Or you could remove iptables and libxtables11, then install iptables, which pulls libxtables12.

Offline dibl

  • siduction community member
  • Global Moderator
  • User
  • *****
  • Posts: 2.358
    • Land of the Buckeye
Re: A day for caution today
« Reply #3 on: 2016/11/22, 16:52:45 »
@michaaa62, yes, that is what I did to fix the laptop system.  But I wanted to warn others so they could avoid the problem.
System76 Oryx Pro, Intel Core i7-11800H, SSD 970 EVO Plus;  Asus ROG STRIX X299-E, Core i7-7740X, Nvidia GTX-1060, dual monitors, SSD 860 EVO

Offline seasons

  • User
  • Posts: 269
Re: A day for caution today
« Reply #4 on: 2016/11/22, 22:04:00 »
Also of note is that there is an update to libc6, so, as usual, multi-arch users will have to wait for updated 32-bit version to hit the mirrors, or there will be removals.

KrunchTime

  • Guest
Re: A day for caution today
« Reply #5 on: 2016/11/25, 00:35:31 »
libc6 being held automatically here today.

Offline seasons

  • User
  • Posts: 269
Re: A day for caution today
« Reply #6 on: 2016/11/25, 05:20:36 »
libc6 being held automatically here today.

Yes, it's not a simple matter of mirror sync as I originally thought. It's a bug that affects 32-bit build:
https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=845512