Hello,
looging at the sources, seems that this problem is caused by releasing cache
file lock before and calling
apt_reload_cache(p->get_progress().unsafe_get_ref(), true);
after the dpkg-reconfigure command is executed. This is apparently to
allow changes to be done by dpkg-reconfigure.
Could this be solved either by saving the changes prior to releasing lock,
or only by reloading status database?
--
Matus UHLAR - fantomas, uh...@fantomas.sk ; http://www.fantomas.sk/
Warning: I wish NOT to receive e-mail advertising to this address.
Varovanie: na tuto adresu chcem NEDOSTAVAT akukolvek reklamnu postu.
Fucking windows! Bring Bill Gates! (Southpark the movie)
--
To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org
with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org
