Hi,
Manuel A. Fernandez Montecelo wrote:
> Control: reopen -1
> Control: fixed -1 aptitude/0.7.7-1
Doing this is not really a good thing IMHO. That bug is fixed in
unstable and has a severity level (normal) which usually doesn't get
fixed in stable after the release anymore.
> >What bugs me is c
Control: reopen -1
Control: fixed -1 aptitude/0.7.7-1
2016-03-01 19:01 Christian Pernegger:
2016-03-01 18:53 GMT+01:00 Manuel A. Fernandez Montecelo
:
Perhaps. But in any case, even if the underlying problem was actually a
different one, if several people cannot reproduce it in 0.7.x and ther
2016-03-01 18:53 GMT+01:00 Manuel A. Fernandez Montecelo
:
> Perhaps. But in any case, even if the underlying problem was actually a
> different one, if several people cannot reproduce it in 0.7.x and there
> are reasonably indications that it was fixed, it means that it's
> probably fixed.
Agree
Hi,
2016-03-01 13:31 Christian Pernegger:
Hi,
I'm not so sure. For one, #570492 is ancient and for me at least the bug is
new in jessie.
Perhaps. But in any case, even if the underlying problem was actually a
different one, if several people cannot reproduce it in 0.7.x and there
are reason
Hi,
I'm not so sure. For one, #570492 is ancient and for me at least the bug is
new in jessie. Also it being fixed "in the 0.7 series" does not help jessie
users at all.
Regards,
Christian
2016-03-01 13:52 GMT+01:00 Manuel A. Fernandez Montecelo <
manuel.montez...@gmail.com>:
> Control: tags -1
Control: tags -1 - moreinfo
Control: close -1
2016-02-29 21:03 matthias.hinkfo...@uni-rostock.de:
[...]
I cannot reproduce this behaviour, when I become root before doing
the removal.
In the end, this looks to me to be
https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=570492
since it involves
Hi,
I enjoyed playing around with this bug.
My test setup involves google-mock as package, but I think this is
somewhat arbitrary. I chose google-mock, because no package depends
on it.
Setup:
jessie and wheezy in sources.list, amd64, package google-mock installed
1. start aptitude as a user
2.
> So a couple of more questions...
>
> Did you just dicover this recently
I did two fresh jessie-installs in the past two months, my first (my
other Debian boxes are still on wheezy or squeeze). Both new systems
exhibit this problem and have from the beginning, the older ones do
not.
Cheers,
C.
2016-02-23 18:31 Christian Pernegger:
Hello,
I cannot reproduce this behaviour.
Lucky you! I've since found out that I don't even have to quit and
restart aptitude for this to trigger:
mark package for purging, [g],[g] --> package is purged (as expected)
[g] again --> package shows up marked
Hello,
> I cannot reproduce this behaviour.
Lucky you! I've since found out that I don't even have to quit and
restart aptitude for this to trigger:
mark package for purging, [g],[g] --> package is purged (as expected)
[g] again --> package shows up marked for installation (instead of
nothing to
Control: tags -1 + moreinfo
Hi Christian,
2016-02-17 12:58 Christian Pernegger:
Package: aptitude
Version: 0.6.11-1+b1
Severity: normal
Dear Maintainer,
let's say I purge some packages and exit aptitude, then relaunch it
later and press [g]. The expected behaviour would be for aptitude to
re
Package: aptitude
Version: 0.6.11-1+b1
Severity: normal
Dear Maintainer,
let's say I purge some packages and exit aptitude, then relaunch it
later and press [g]. The expected behaviour would be for aptitude to
report there's nothing to do. Instead, all the packages purged in the
previous session
12 matches
Mail list logo
