Interesting, thanks Mathias for the update.
@Julian - I think this means you have to tackle that from apt itself then? (or at least find out via which path it triggers the issue now). How far are you in regard to comment #9 number 3 atm - can you take it into apt itself already?
Interesting, thanks Mathias for the update.
@Julian - I think this means you have to tackle that from apt itself then? (or at least find out via which path it triggers the issue now).
How far are you in regard to comment #9 number 3 atm - can you take it into apt itself already?