Your message dated Fri, 15 Sep 2006 16:22:29 -0600
with message-id <[EMAIL PROTECTED]>
and subject line [DSELECT] failed to install some dependencies
has caused the attached Bug report 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 I am
talking about this indicates a serious mail system misconfiguration
somewhere. Please contact me immediately.)
Debian bug tracking system administrator
(administrator, Debian Bugs database)
--- Begin Message ---
Package: dselect
Version: 1.10.4
Severity: important
-- System Information
Debian Release: 3.0
Architecture: i386
Kernel: Linux link 2.4.20-mm #1 Tue Feb 24 17:47:00 EST 2004 i586
Locale: LANG=C, LC_CTYPE=C
Versions of packages dselect depends on:
ii libc6 2.2.5-11.2 GNU C Library: Shared libraries an
ii libncurses5 5.2.20020112a-7 Shared libraries for terminal hand
ii libstdc++2.10-glibc2.2 1:2.95.4-11woody1 The GNU stdc++ library
Hi,
I just did a dist-upgrade (woody to sarge) in July '04.
module-init-tools was not upgraded, though I certainly had it installed.
Infact, if you check the sarge Packages file you'll find it's marked "Optional"
HOWEVER,
Description: tools for managing Linux kernel modules
This package contains a set of programs for loading, inserting, and
removing kernel modules for Linux (versions 2.5.48 and above). It serves
the same function that the "modutils" package serves for Linux 2.4.
AND
/sbin/insmod
/sbin/update-modules
/sbin/rmmod
/sbin/modprobe
/sbin/depmod
/sbin/modinfo
/bin/lsmod
...
Obviously, you'd have to be Bill Gates Jr. to think this package is optional.
It isn't optional. Say it is, and we have an arguement to settle.
I did install this from dselect:
Package: kernel-image-2.6.6-1-k7
Depends: initrd-tools (>= 0.1.63), coreutils | fileutils (>= 4.0), module-init-t
ools (>= 0.9.13)
So, again, not only did I do a "apt-get upgrade" and "apt-get dist-upgrade"
but I did a dselect and picked the kernel. Still no module-init-tools.
I only found out by reading the "now famous" post-holloween.txt that (really
should have come with) the 2.6 kernel series.
In general I had many problems with things which were supposed to be installed
not getting installed.
Many many more problems with packages which did not have all their
dependancies marked (or? as above they were somehow skipped?)
Many many more problems with packages which did not install correctly.
I can only surmise that while jilting me as a potential maintainer that
debian.org has allowed uneducated monkeys great privelages with sarge.
Thanks,
John D. Hendrickson
[EMAIL PROTECTED]
[EMAIL PROTECTED]
--- End Message ---
--- Begin Message ---
Hi,
This does not appear to be a dselect bug...
"not only did I do a "apt-get upgrade" and "apt-get dist-upgrade"
but I did a dselect and picked the kernel. Still no module-init-tools."
...but was more likely a packaging problem/idiosyncrasy with the
original Woody -> Sarge upgrade path.
Also considering that packaging of kernels has changed substantially
(dependency relationships have been reworked), the upgrade path the
problem was reported with no longer exists (Sarge has seen releases
since the original one), and no more information was ever provided
(there is no clue as to what the trigger was and probably never will
be), it seems appropriate to close this report.
- Bruce
--- End Message ---
