Hello,
of course, I wouldn't touch synaptic with a ten-foot pole.
But yesterday our user JohnML has informed us that synaptic and debian packagesearch cannot be started.
Besides of
the libept transition there is also a packaging issue in libept1.4.16:
The package doesn't contain the 4.x series of libept but has a 5.x content.
So you can't install libept1.5.0 because both packages have the same file libept.so.1.aptpkg5.0
root@sidbox:~# apt-get install libept1.5.0
Reading package lists... Done
Building dependency tree
Reading state information... Done
The following NEW packages will be installed:
libept1.5.0
0 upgraded, 1 newly installed, 0 to remove and 118 not upgraded.
Need to get 0 B/89.1 kB of archives.
After this operation, 271 kB of additional disk space will be used.
(Reading database ... 692027 files and directories currently installed.)
Preparing to unpack .../libept1.5.0_1.1+nmu2_amd64.deb ...
Unpacking libept1.5.0:amd64 (1.1+nmu2) ...
dpkg: error processing archive /var/cache/apt/archives/libept1.5.0_1.1+nmu2_amd64.deb (--unpack):
trying to overwrite '/usr/lib/x86_64-linux-gnu/libept.so.1.aptpkg5.0', which is also in package libept1.4.16:amd64 1.0.14+b2
Processing triggers for libc-bin (2.19-22) ...
Errors were encountered while processing:
/var/cache/apt/archives/libept1.5.0_1.1+nmu2_amd64.deb
E: Sub-process /usr/bin/dpkg returned an error code (1)
At least I was able to start packagesearch after creating a symlink:
~# ln -s /usr/lib/x86_64-linux-gnu/libept.so.1.aptpkg5.0 /usr/lib/x86_64-linux-gnu/libept.so.1.aptpkg4.16
Of course i can't promise for correctness.
A general advice: Don't break your system by using synaptic.
Take care and have fun!
greetings
musca