Your message dated Tue, 28 Jan 2014 17:08:56 +0000
with message-id
<CAPQ4b8=ZG0T2SOFe=5vryg2fzavdbkh1xc+rw3h1bx_m2rh...@mail.gmail.com>
and subject line aptitude: PreDepends dependencies not selected for new version
of coreutils
has caused the Debian Bug report #209414,
regarding aptitude: PreDepends dependencies not selected for new version of
coreutils
to be marked as done.
This means that you claim that the problem has been dealt with.
If this is not the case it is now your responsibility to reopen the
Bug report if necessary, and/or fix the problem forthwith.
(NB: If you are a system administrator and have no idea what this
message is talking about, this may indicate a serious mail system
misconfiguration somewhere. Please contact [email protected]
immediately.)
--
209414: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=209414
Debian Bug Tracking System
Contact [email protected] with problems
--- Begin Message ---
Package: aptitude
Version: 0.2.11.1-2
Severity: normal
I did an update on 9/9 that results in coreutils wanting to upgrade from
5.0-5 to 5.0.90-3. The new coreutils has two packages it PreDepends on:
libacl1, and libattr1. These packages aren't selected, but without
selecting them, coreutils is broken.
It seems like these two packages should be selected so that the
coreutils upgrade isn't flagged as broken.
-- System Information
Debian Release: 3.0
Architecture: i386
Kernel: Linux tiamat 2.4.21-1-686 #2 Mon Jun 16 22:13:09 EST 2003 i686
Locale: LANG=C, LC_CTYPE=C
Versions of packages aptitude depends on:
ii apt [libapt-pkg-libc6. 0.5.4 Advanced front-end for dpkg
ii libc6 2.3.1-16 GNU C Library: Shared libraries an
ii libncurses5 5.3.20030719-1 Shared libraries for terminal hand
ii libsigc++0 1.0.4-3 Type-safe Signal Framework for C++
ii libstdc++2.10-glibc2.2 1:2.95.4-11woody1 The GNU stdc++ library
--- End Message ---
--- Begin Message ---
tags 209414 + unreproducible
stop
Hi,
The versions of coreutils are not even present in snapshots, and the
versions of the libraries involved not mentioned, so very difficult to
reproduce as explained. There are no mentions to this in the
changelog of coreutils of the versions involved or in the archived or
unarchived bugs of aptitude and coreutils.
This happened with an ancient version of aptitude, many internals have
changed since then for sure. So I tried an alternative method
instead.
I devised the following test to try to verify if this happens now:
1) I downgraded coreutils (random choice) to 8.13
2) created fake package _20-1 pre-depending on coreutils >=8~ and installed it
3) created _20-2, depending on coreutils >= 8.21~ (the current in
unstable), and a local repository for it, then "aptitude update"
Now the test is to hit "+" on the fake package to see if it marks both
for upgrades and installs both successfully, or marks them as broken
somehow, or there is any other problem.
4) + and then g results in:
--\ Packages to be upgraded (2)
iu U fake 20-1 20-2
iu coreutils -370 kB 8.13-3.5 8.21-1
5) both install successfully
So I think that it is more or less clear that at least the basic case
of upgrading pre-dependencies along with the package works well and as
expected with the current version, and whatever was the reason is not
happening now (again, at least in basic cases). So I am closing the
bug report now.
Cheers.
--
Manuel A. Fernandez Montecelo <[email protected]>
--- End Message ---
_______________________________________________
Aptitude-devel mailing list
[email protected]
http://lists.alioth.debian.org/cgi-bin/mailman/listinfo/aptitude-devel
