reopen 545366
thanks
dselect 1.15.4.1 (with dpkg 1.15.4.1) still does not distinguish
between new and old packages. This makes dselect mostly useless on
upgrades and completely useless on adding new repositories.
The only difference between 1.15.4 and 1.15.4.1 is that former marks
new and old
Version: 1.15.4.1
On Sun, 25 Oct 2009, Piotr Engelking wrote:
The only difference between 1.15.4 and 1.15.4.1 is that former marks
new and old packages as new, and the latter marks new and old packages
as old.
That's what we wanted. Closing this bug again. The fact that it doesn't
keep track
Raphael Hertzog hert...@debian.org:
The only difference between 1.15.4 and 1.15.4.1 is that former marks
new and old packages as new, and the latter marks new and old packages
as old.
That's what we wanted. Closing this bug again. The fact that it doesn't
keep track of new packages is
severity 545366 serious
thanks
On Tue, 08 Sep 2009, Petr Vandrovec wrote:
IMHO change should be reverted until old functionality can be
achieved through some other way - unless you can achieve such
functionality today.
I'd like to remind everybody that we're looking for someone to step up and
Yes please, revert that commit. dselect is currently unusable.
regards,
Domenico
-[ Domenico Andreoli, aka cavok
--[ http://www.dandreoli.com/gpgkey.asc
---[ 3A0F 2F80 F79C 678A 8936 4FEE 0677 9033 A20E BC50
--
To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org
with
Hi!
On Mon, 2009-09-07 at 09:43:37 +0200, Sven Joachim wrote:
On 2009-09-07 09:11 +0200, Raphael Hertzog wrote:
On Sun, 06 Sep 2009, Petr Vandrovec wrote:
Since today's update run dselect is completely confused and does not
remember which packages are new and which are old - it lists all
Guillem Jover napsal(a):
Hi!
This increases the status file, the parsing and processing time when
doing dependency resolutions and package iterations for everyone, and
just to be able to show new packages on dselect. The correct solution
here is not to revert the change, but to store the
On Sun, 06 Sep 2009, Petr Vandrovec wrote:
Since today's update run dselect is completely confused and does not
remember which packages are new and which are old - it lists all
available and not installed packages as new, again and again. And
not only that, it also marks some of them for
On 2009-09-07 09:11 +0200, Raphael Hertzog wrote:
On Sun, 06 Sep 2009, Petr Vandrovec wrote:
Since today's update run dselect is completely confused and does not
remember which packages are new and which are old - it lists all
available and not installed packages as new, again and again. And
Raphael Hertzog napsal(a):
On Sun, 06 Sep 2009, Petr Vandrovec wrote:
You can use git bisect to isolate the problem more precisely. My bet
would be on the code that auto-cleans up the status database, maybe it
applies by error on the available file as well and thus it believes
that all packages
Package: dselect
Version: 1.15.4
Since today's update run dselect is completely confused and does not
remember which packages are new and which are old - it lists all
available and not installed packages as new, again and again. And not
only that, it also marks some of them for installation
11 matches
Mail list logo
