Hi, > It does involve creating a chroot, editing sources.list and running "apt > update"… if you already have a wheezy chroot, you can skip the first > step. > > If you file bugs (and demand fixes from volunteers), you should be > prepared to spend a few minutes to help those analysing+fixing the bug you > are interested in. You seem to have had time to write long emails…
I did *not* have time to write long emails. I just had to do to make you understand. That was necessary because you obviously did not understand that testing apt is completely out of scope (and, furthermore, the original requestor had already stated that apt fails - why should I waste time on verifying another apt install complains about the same wrong input?) I am happy to help with anything necessary - explaining the situation to you seemed to be necessary; verifying that there is more than one installation of apt that complains about invalid input was not. So, to cut this short: If I can do anything that helps with finding the cause for or fixing this bug, please let me know and I'll happily do. -nik -- PGP-Fingerprint: 3C9D 54A4 7575 C026 FB17 FD26 B79A 3C16 A0C4 F296 Dominik George · Mobil: +49-1520-1981389 Teckids e.V. · FrOSCon e.V. · OpenRheinRuhr e.V. Fellowship of the FSFE · Piratenpartei Deutschland Opencaching Deutschland e.V. · Debian Contributor LPIC-3 Linux Enterprise Professional (Security)
signature.asc
Description: This is a digitally signed message part.
