Your message dated Thu, 4 Feb 2016 16:36:58 +0100 with message-id <[email protected]> and subject line Re: Bug#802617: apt-transport-https: apt-get update: W: Size of file [...] is not what the server reported has caused the Debian Bug report #802617, regarding apt-transport-https: apt-get update: W: Size of file [...] is not what the server reported to be marked as done.
This means that you claim that the problem has been dealt with. If this is not the case it is now your responsibility to reopen the Bug report if necessary, and/or fix the problem forthwith. (NB: If you are a system administrator and have no idea what this message is talking about, this may indicate a serious mail system misconfiguration somewhere. Please contact [email protected] immediately.) -- 802617: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=802617 Debian Bug Tracking System Contact [email protected] with problems
--- Begin Message ---Package: apt-transport-https Version: 1.0.9.8.1 Severity: normal Dear Maintainer, I get an error while executing apt-get update: W: Size of file /var/lib/apt/lists/partial/github.com_XavierBerger_RPi-Monitor-deb_raw_master_repo_Packages.gz is not what the server reported 442 152 I use the repo from the project deb https://github.com XavierBerger/RPi-Monitor-deb/raw/master/repo/ on my RPi2 (Raspian Jessie). apt-transport-https is installed. Other users are reporting the same issue (https://github.com/XavierBerger/RPi-Monitor-deb/issues/6), however the developper says everything on github looks ok. It appeared (first time i believe) on my installation when I had to use https with github. - System Information: Distributor ID: Raspbian Description: Raspbian GNU/Linux 8.0 (jessie) Release: 8.0 Codename: jessie Architecture: armv7l Kernel: Linux 4.1.7-v7+ (SMP w/4 CPU cores; PREEMPT) Locale: LANG=de_CH.UTF-8, LC_CTYPE=de_CH.UTF-8 (charmap=UTF-8) Shell: /bin/sh linked to /bin/dash Init: systemd (via /run/systemd/system) Versions of packages apt-transport-https depends on: ii libapt-pkg4.12 1.0.9.8.1 ii libc6 2.19-18+deb8u1 ii libcurl3-gnutls 7.38.0-4+deb8u2 ii libgcc1 1:4.9.2-10 ii libstdc++6 4.9.2-10 apt-transport-https recommends no packages. apt-transport-https suggests no packages. -- no debconf information
--- End Message ---
--- Begin Message ---On Thu, Oct 22, 2015 at 03:31:17PM +0200, David Kalnischkies wrote: > Control: fixed -1 1.1~exp14 > > On Wed, Oct 21, 2015 at 08:29:19PM +0200, Julian Andres Klode wrote: > > On Wed, Oct 21, 2015 at 07:31:19PM +0200, Alex wrote: > > > I get an error while executing apt-get update: > > > > > > W: Size of file > > > /var/lib/apt/lists/partial/github.com_XavierBerger_RPi-Monitor-deb_raw_master_repo_Packages.gz > > > is not what the server reported 442 152 > > > > I cannot reproduce this with 1.1~exp14. > > Based on > $ git log origin/debian/experimental --not origin/debian/sid methods/https.cc > alone I would guess a2d40703e4a5590a689ace4466f92e590434944d and upwards are > responsible for it not happening anymore, but I remember also my own dive into > this area (27925d82dd0cbae74d48040363fe6f6c2bae5215) and the message comes > from > the acquire system, its not totally unlikely that there is more to be found… > so > there are probably a multitude of (incorrect) reasons why this message could > occur someone with a lot more time and passion for history digging (as in the > meantime the involved code is totally different) than I currently have needs > to > wade through all this. > > Or, we could just silence the warning. Its gone in newer releases as the place > it was printed is too late to have any positive impact… Nowadays http/https > know what size to expect and actively deny accepting more. Previously all the > system does was raising this rather unhelpful warning and proceed as if > nothing > happend. > > Note that the size the server reported isn't the size in the Release file, > that > would have been to easy, its the size of data the server claims to send to us, > so these values can happily disagree and verification later on can still pass > successfully (the only thing which is slightly off is the progress report as > its working with the wrong values). > > > Oh, and for the record: I have no clear opinion on what should be done about > it – I will leave that for the "history digging timelords" to decide. > Let's close this now that 1.1 and 1.2 hit unstable and testing. -- Julian Andres Klode - Debian Developer, Ubuntu Member See http://wiki.debian.org/JulianAndresKlode and http://jak-linux.org/. When replying, only quote what is necessary, and write each reply directly below the part(s) it pertains to (`inline'). Thank you.
--- End Message ---
