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 a member of Ubuntu Bugs, which is subscribed to Ubuntu. -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs