First char of some bzip2 files are changed by apt-cacher-ng

Bug #234641 reported by Tim Boven
16
This bug affects 2 people
Affects Status Importance Assigned to Milestone
apt-cacher-ng (Ubuntu)
Invalid
Medium
Unassigned
Nominated for Jaunty by Skilly
Nominated for Karmic by Skilly
Nominated for Lucid by Skilly

Bug Description

Binary package hint: apt-cacher-ng

When running "apt-get update" I get some errors that bzip2 exited with exit code 2.

When downloading the files myself (Sources.bz2 or Packages.bz2) and comparing with files wich are downloaded through apt-cacher-ng I noticed that the first character is changed. The first character should be a "B" (which is typical for bzip-files) but in the file downloaded throught apt-cacher-ng the first char is something like "^@" when I viewed it in vi (when catted the char is invisible). When I changed this char to a "B" I could unpack the file.

I've also noticed I don't have this problem with all files, just with 6 of them. All the files I've checked are empty files.
 (why would they be empty?)

Revision history for this message
Eduard Bloch (edi-gmx) wrote :

Actually, I have seen similar problems appearing out of blue in the last weeks. Right now I am adding some user-friendly debug-reporting code, hopping to be able to track this problem down RSN.

^@ in vim is IIRC a NULL char which looks weird in this context :-(

Revision history for this message
Tim Boven (tim-boven-telenet) wrote : Re: [Bug 234641] Re: First char of some bzip2 files are changed by apt-cacher-ng

It's indeed something weird. If I can help (not programming but testing)
you can contact me.
Does apt-cacher-ng something special with the files it downloads? It
downloads them, caches them en uploads them to the clients but then I
don't see why the null-char is appearing? I think it's also weird that I
only have those problems with empty archives (at least those that I've
checked manually)

Tim

Eduard Bloch schreef:
> Actually, I have seen similar problems appearing out of blue in the last
> weeks. Right now I am adding some user-friendly debug-reporting code,
> hopping to be able to track this problem down RSN.
>
> ^@ in vim is IIRC a NULL char which looks weird in this context :-(
>
>

Revision history for this message
Eduard Bloch (edi-gmx) wrote : Re: [Bug 234641] Re: First char of some bzip2 files are changed by apt-cacher-ng

#include <hallo.h>

Can you provide the list of your mirrors in use (most likely from
/etc/apt-cacher-ng/backends_ubuntu) and the list of involved files?

grep bz2 /var/log/apt-cacher-ng/apt-cacher.log | tail -n100

Regards,
Eduard.

* Tim Boven [Wed, May 28 2008, 10:29:57AM]:
> It's indeed something weird. If I can help (not programming but testing)
> you can contact me.
> Does apt-cacher-ng something special with the files it downloads? It
> downloads them, caches them en uploads them to the clients but then I
> don't see why the null-char is appearing? I think it's also weird that I
> only have those problems with empty archives (at least those that I've
> checked manually)
>
> Tim
>
> Eduard Bloch schreef:
> > Actually, I have seen similar problems appearing out of blue in the last
> > weeks. Right now I am adding some user-friendly debug-reporting code,
> > hopping to be able to track this problem down RSN.
> >
> > ^@ in vim is IIRC a NULL char which looks weird in this context :-(
> >
> >
>
> --
> First char of some bzip2 files are changed by apt-cacher-ng
> https://bugs.launchpad.net/bugs/234641
> You received this bug notification because you are subscribed to apt-
> cacher-ng in ubuntu.

--
<hggh> zobel: ich habe gerade noch ein paket auf dak.ganneff geladen, kannst du
 das bitte hochladen?
<hggh> zobel: libfile-homedir-perl, wenn du zeit hast :)
<Myon> return $ENV{HOME}?

Revision history for this message
Tim Boven (tim-boven-telenet) wrote : Re: [Bug 234641] Re: First char of some bzip2 files are changed by apt-cacher-ng
Revision history for this message
Rolf Leggewie (r0lf) wrote :

Eduard, any comments on this one?

Revision history for this message
Eduard Bloch (edi-gmx) wrote :

Might be fixed with the changes in 0.2.2 or 0.2.6. I have not received grave user bug reports for about three months now.

Revision history for this message
Rolf Leggewie (r0lf) wrote :

Tim, can you provide a clear test case (preferred) or alternatively update to 0.2.2 from my PPA to see if you still experience this problem?

Revision history for this message
Rolf Leggewie (r0lf) wrote :

Tim, btw, what version of ubuntu and apt-cacher-ng are you using?

Revision history for this message
Skilly (michael-scheepers) wrote :

It seems this has now been identified and fixed in Debian: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=448092

Will this fix automatically migrate to ubuntu?

Revision history for this message
Daniel Hahler (blueyed) wrote :

I'm not sure, if it's the same as the Debian bug (http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=448092) really, which is about apt-cacher (without "-ng" after all).

Changed in apt-cacher-ng (Ubuntu):
status: New → Incomplete
importance: Undecided → Medium
Revision history for this message
Rolf Leggewie (r0lf) wrote :

Daniel, you set this to incomplete status. What is the question you are looking to see answered?

Revision history for this message
Eduard Bloch (edi-gmx) wrote :

apt-cacher-ng does not share any code with apt-cacher

Revision history for this message
Mattia Rizzolo (mapreri) wrote :

There have been many changes in Ubuntu since that time you reported the bug and your problem may have been fixed with some of the updates. It would help us a lot if you could test it on a currently supported Ubuntu version. When you test it and it is still an issue, kindly upload the updated logs by running apport-collect <bug #> and any other logs that are relevant for this particular issue.

Changed in apt-cacher-ng (Ubuntu):
status: Incomplete → New
status: New → Incomplete
Revision history for this message
Rolf Leggewie (r0lf) wrote :

We are closing this bug report because it lacks the information we need to investigate the problem, as described in the previous comments. Please reopen it if you can give us the missing information, and don't hesitate to submit bug reports in the future. To reopen the bug report you can click on the current status, under the Status column, and change the Status back to "New". Thanks again!

Changed in apt-cacher-ng (Ubuntu):
status: Incomplete → Invalid
To post a comment you must log in.
This report contains Public information  
Everyone can see this information.

Other bug subscribers

Bug attachments

Remote bug watches

Bug watches keep track of this bug in other bug trackers.