Package: libcurl3-gnutls
Version: 7.26.0-1+wheezy3
Severity: important

Dear Maintainer,

after upgrading to the 7.1 release of Wheezy, I started to notice that apt-get
started to "not see" updated or completely new packages in our internal
repositories which are served over https. I started digging around and finally
added a comment [1] to bug #705648 which was fixed in the point release and
whose fix seems to cause the problem (since downgrading apt helps). However, as
I also noted in the comment, it seems that the underlying problem is in curl,
strictly speaking in the lack of a fix for #705783 ("CURLINFO_CONDITION_UNMET
is not resetted between requests") in Wheezy, since applying the patch to curl
in Wheezy also seems to fix the issue.

Unfortunately, I haven't found a good work around yet (I don't consider rolling
a custom version of curl or removing the package lists before updating them or
downgrading apt as good work arounds ;)). So, is there any chance that the fix
for #705783 will also be applied to the package in Wheezy?

Best regards
Manfred

[1] http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=705648#35

-- System Information:
Debian Release: 7.1
  APT prefers stable-updates
  APT policy: (500, 'stable-updates'), (500, 'stable')
Architecture: amd64 (x86_64)

Kernel: Linux 3.2.0-4-amd64 (SMP w/4 CPU cores)
Locale: LANG=de_CH.utf8, LC_CTYPE=de_CH.utf8 (charmap=UTF-8)
Shell: /bin/sh linked to /bin/dash

Versions of packages libcurl3-gnutls depends on:
ii  libc6              2.13-38
ii  libgcrypt11        1.5.0-5+deb7u1
ii  libgnutls26        2.12.20-7
ii  libgssapi-krb5-2   1.10.1+dfsg-5+deb7u1
ii  libidn11           1.25-2
ii  libldap-2.4-2      2.4.31-1+nmu2
ii  librtmp0           2.4+20111222.git4e06e21-1
ii  libssh2-1          1.4.2-1.1
ii  multiarch-support  2.13-38
ii  zlib1g             1:1.2.7.dfsg-13

Versions of packages libcurl3-gnutls recommends:
ii  ca-certificates  20130119

libcurl3-gnutls suggests no packages.

-- no debconf information


-- 
To UNSUBSCRIBE, email to [email protected]
with a subject of "unsubscribe". Trouble? Contact [email protected]

Reply via email to