On 04/16/12 12:17, Daniel Hartwig wrote:
Hello
On 16 April 2012 11:09, dE .<de.tec...@gmail.com> wrote:
There's no specific pattern in which this happens, an aptitude run
just for searching a package may mark packages manually installed.
How did you determine that 'aptitude search' changed the state, rather
than 'update' or 'upgrade'?
It happened once, although I'm not sure... you can rule out this
possibility.
But if I aptitude full-upgrade, then before I enter the 'y' to proceed,
it's going to mark packages manually installed, as a result, next time I
run aptitude, blocks are made.
That sounds indeed strange.
There are quite some issues around loosing the mark-auto state, but
that's the first case where a simple search can be the reason.
Yes and, given that, the whole body of code involved needs to be carefully
checked. So, dE, please do not invest too much time trying to diagnose
this specific case as it should hopefully be picked up anyway.
It appears that Debian users don't care about the manually installed
packages -- there's no didicated way to see them, neither there's much
demand. You have to do all kinds of filtering to see them.
Unfortunately, this time I couldn't reproduce it at the upgrade, I've an
outdated Debian system (4.6) which I'll upgrade to see what happens.
Can you please tell me what do you need to upload to prove the bug?
Ideally the output of aptitude-create-state-bundle before the problem and
then the full typescript of commands needed to reproduce it. Given that
your system is since updated this may not be possible any more.
No it's not, there's a system which's not updated. I'll back it up and test.
As of the current time, aptitude update marks libxine1-xvdr as manually
installed. Attaching output of aptitude --simulate search '~i' | grep
--invert-match '^i A' before and after update. Check the diffs.
To be sure, did you run only 'aptitude update' before the search and not
also 'upgrade' or 'install'?
Note: the changelog shows that libxine1-xvdr was replaced by
libxine2-xvdr on 2012-02-03 â this may be significant here.
No search issues -- ignore them.
--
To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org
with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org
