repoen 184354
thanks

I will reopen because the problem was fixed by removal of code, not as
option (as suggested by the reporter of the bug) and I intend to fix
this soon the right way.
No verification is not a sane approach 'cause this could lead to
repeated trips to the connected computer in case of failures.

I also found some cases where the md5sums might miss, but not due to a
lack of that info in the archive: I want to add a feature to be able
to do apt-get update (by using the connected computer) and found out
that apt-get -qq --print-uris will print 0 for the checksum for the
Packages files, so checking in this case would not be practical nor
correct.

Still I would like to see a case where the debs' md5sums are missing
within a apt-gettable repository.

--
Regards,
EddyP
=============================================
"Imagination is more important than knowledge" A.Einstein

Reply via email to