Bug#500990: marked as done (libdb-dev: Dependency issues triggered by (full-)upgrade for libdb*-dev)
Your message dated Mon, 28 Mar 2011 18:41:28 +0200
with message-id <AANLkTimhbKqHgM-kVO6Wycx=hqA361Ma1sA95ubSycj9@mail.gmail.com>
and subject line Bug#500990: libdb-dev: Dependency issues triggered by (full-)upgrade for libdb*-dev
has caused the Debian Bug report #500990,
regarding libdb-dev: Dependency issues triggered by (full-)upgrade for libdb*-dev
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 firstname.lastname@example.org
Debian Bug Tracking System
Contact email@example.com with problems
--- Begin Message ---
- To: Debian Bug Tracking System <firstname.lastname@example.org>
- Subject: libdb-dev: Dependency issues triggered by (full-)upgrade for libdb*-dev
- From: David Ayers <email@example.com>
- Date: Fri, 03 Oct 2008 10:28:35 +0200
- Message-id: <firstname.lastname@example.org>
During my daily full-upgrade I was informed:
Reading package lists... Done
Building dependency tree
Reading state information... Done
Reading extended state information
Initializing package states... Done
Reading task descriptions... Done
The following packages are BROKEN:
The following NEW packages will be installed:
The following packages will be upgraded:
apt-show-versions ffmpeg ffmpeg-dbg ffmpeg-doc gettext gettext-base
libavcodec51 libavdevice52 libavformat52 libavutil49 libdb4.6
13 packages upgraded, 1 newly installed, 0 to remove and 1 not upgraded.
Need to get 28.9MB of archives. After unpacking 1798kB will be used.
The following packages have unmet dependencies:
libdb-dev: Depends: libdb4.6 (= 4.6.21-8) but is to be installed.
The following actions will resolve these dependencies:
Upgrade the following packages:
libdb-dev [4.6.21-8 (now) -> 184.108.40.206 (testing)]
Score is 60
Accept this solution? [Y/n/q/?]
It seems that a new libdb-dev package depending on 4.6.21-11 should be made
available at the same time as libdb4.6-dev is installed... or maybe the
correct solution would be to have libdb4.6-dev provide libdb-dev?
Yet I'm still confused wrt 220.127.116.11... if that would resolve the issue, why
doesn't a full-upgrade simply install it (as it seems it shouldn't affect
other packages)? But I suppose I'm missing something.
[I don't know much about packaging... I'm just trying to give clues.]
Possibly related reports:
PS: I wasn't sure whether I should append to one of the reports above, since
last time I appended to a bug I thought was related, I was told to avoid
cluttering old reports and leave it up to the maintainers to decide whether
to merge reports or not. So sorry for any inconvenience caused by opening a
-- System Information:
Debian Release: lenny/sid
APT prefers testing
APT policy: (500, 'testing')
Architecture: i386 (i686)
Kernel: Linux 2.6.26-1-686 (SMP w/1 CPU core)
Locale: LANG=de_AT.UTF-8, LC_CTYPE=de_AT.UTF-8 (charmap=UTF-8)
Shell: /bin/sh linked to /bin/bash
Versions of packages libdb-dev depends on:
ii libdb4.6 4.6.21-8 Berkeley v4.6 Database Libraries [
libdb-dev recommends no packages.
Versions of packages libdb-dev suggests:
pn db4.6-doc <none> (no description available)
-- no debconf information
--- End Message ---
--- Begin Message ---
- To: email@example.com, David Ayers <firstname.lastname@example.org>
- Subject: Bug#500990: libdb-dev: Dependency issues triggered by (full-)upgrade for libdb*-dev
- From: Ondřej Surý <email@example.com>
- Date: Mon, 28 Mar 2011 18:41:28 +0200
- Message-id: <AANLkTimhbKqHgM-kVO6Wycx=hqA361Ma1sA95ubSycj9@mail.gmail.com>
I am taking over the db* packages and I am doing little cleanup. I see
that the problem itself wasn't in the libdb-dev itself, but in the
interdependencies with apache2-threaded-dev, so I guess it's safe to
close this bug report. Feel free to reopen if you disagree.
Ondřej Surý <firstname.lastname@example.org>
--- End Message ---