Re: libgnutls-deb0-28 missing from Debian repos
On Fri 13 Jul 2018 at 10:01:28 (+1000), Zenaan Harkness wrote:
> On Thu, Jul 12, 2018 at 08:24:35AM -0400, Greg Wooledge wrote:
> > On Thu, Jul 12, 2018 at 05:45:46AM +1000, Zenaan Harkness wrote:
> > > On Wed, Jul 11, 2018 at 08:30:51AM -0400, Greg Wooledge wrote:
> > > > On Wed, Jul 11, 2018 at 09:48:10PM +1000, Zenaan Harkness wrote:
> > > > > Why is this package missing from the repos, but installed in my
> > > > > stretch install?
> > > >
> > > > Because you upgraded from jessie. This lets you keep older shared
> > > > libraries or other packages as long as they don't conflict with anything
> > > > in stretch. And shared libs typically don't conflict with anything.
> > >
> > > Very interesting, thank you.
> > >
> > > How do I replace it with something stretch-supported, without having
> > > 130 paackages and 550MiB first removed?
> > >
> > > (Which seems necessary because it's breaking git clone with https
> > > URLs.)
> >
> > You're talking about the package "libgnutls-deb0-28" which is listed
> > in the Subject: header? I have no idea why that would be related to a
> > stretch version of git, or be causing any kind of problem.
>
> Yes. As per the link posted earlier in the thread to possibly help
> solve this problem:
>
> https://superuser.com/questions/1250527/git-clone-stopped-working
>
>
> > wooledg:~$ dpkg -s git | grep ^Depends:
> > Depends: libc6 (>= 2.16), libcurl3-gnutls (>= 7.16.2), libexpat1 (>= 2.0.1), libpcre3, zlib1g (>= 1:1.2.0), perl, liberror-perl, git-man (>> 1:2.11.0), git-man (<< 1:2.11.0-.)
> >
> > wooledg:~$ dpkg -s libcurl3-gnutls | grep ^Depends:
> > Depends: libc6 (>= 2.17), libcomerr2 (>= 1.01), libgnutls30 (>= 3.5.6), libgssapi-krb5-2 (>= 1.14+dfsg), libidn2-0 (>= 0.6), libk5crypto3 (>= 1.6.dfsg.2), libkrb5-3 (>= 1.6.dfsg.2), libldap-2.4-2 (>= 2.4.7), libnettle6, libnghttp2-14 (>= 1.12.0), libpsl5 (>= 0.13.0), librtmp1 (>= 2.4+20131018.git79459a2-3~), libssh2-1 (>= 1.7.0), zlib1g (>= 1:1.1.4)
> >
> > The stretch version of git depends (indirectly) on libgnutls30 and
> > that's what should be relevant here. Having libgnutls-deb0-28 installed
> > (or not installed) should not matter at all.
>
> Well as I highlighted in another email above in this thread, when I
> try to remove it, it wants to rip out over 100 packages and over 500
> MiB's of Debian software.
>
> I guess it's time to just re-install?
>
> Been quite a few years since I've had to reinstall Debian…
>
> Thanks for the ideas folks,
I don't understand why you have so many dependencies on
libgnutls-deb0-28 if you're running stretch. Doodling while I
downloaded the humongous video of today's Congress, I typed:
$ zgrep '\(libgnutls-deb0-28\)\|\(Package:\)' /home/debian/jessie/Packages.gz | \
grep -B1 Depends | grep Package | sort > /tmp/oldpacks
which yielded 223 lines. I then edited oldpacks to build the single line:
$ grep '\(Package: abiword$\)\|\(Package: [ … ] Package: xombrero$\)' \
/var/lib/apt/lists/ftp.us.debian.org_debian_dists_stretch_main_binary-amd64_Packages > \
/tmp/keptpacks
and that yielded 198 lines, which suggests that stretch contains
up-to-date versions of most of the packages that apt wanted to remove.
(Obviously I'm not taking account of dependencies on dependencies…)
Here's the list of 25 jessie packages not in stretch:
$ lines-in-a-not-b.py /tmp/oldpacks /tmp/keptpacks
Package: dsyslog
Package: dwb
Package: guile-gnutls
Package: gurlchecker
Package: ircd-ratbox
Package: jd
Package: libaqbanking34-plugins
Package: libavformat56
Package: libaws3.2.0
Package: libccrtp2
Package: libepc-1.0-3
Package: libepc-ui-1.0-3
Package: libgloox12
Package: libgnutls28-dbg
Package: libimobiledevice4
Package: libmailutils4
Package: libmicrohttpd10
Package: libopenconnect3
Package: libucommon6
Package: libvncclient0
Package: libvncserver0
Package: libwireshark5
Package: licq-plugin-jabber
Package: mutt-patched
Package: sflphone-daemon
$
Many of those will probably have package names that include the
version number, like libwireshark5→libwireshark8.
(If you get different results, it could be because my jessie
installations/lists are all i386 whereas for stretch they're amd64.)
Cheers,
David.
Reply to: