Comment 1 Ryan Abel 2008-12-18 18:21:40 UTC

Are you absolutely certain that you removed the offending libc6-dev/dbg
packages?

(In reply to comment #1)
> Are you absolutely certain that you removed the offending libc6-dev/dbg
> packages?

I haven't removed libc6-dev, but since it can be upgraded (e.g. apt-get can
cope with it), why should it be removed?

Comment 3 Ryan Abel 2008-12-18 19:28:09 UTC

Dropping severity again based on comment #2.

I have also had a failure with installing this upgrade. I raised a bug
yesterday but for some reason it's disappeared from the system.

Following some clues in this bug (I didn't know how to get diagnostics last
time) I've re-tried the install and get the following error log:

hildon-application-manager 2.1.19.1
Closing 3 applications
        App:'MediaBox', Title:'MediaBox'
        App:'FBReader', Title:'FBReader - The Rights of Man'
        App:'Web', Title:'Web - Beermad's brewery detail: Dark Star'
-----
Upgrading osso-software-version-rx34 1:5.2008.43-7 to 1:5.2008.43-7
Setting up metalayer-crawler0 (1.3.19-2) ...
Starting Metalayer Crawler: metalayer-crawler0invoke-rc.d: initscript
metalayer-crawler0, action "start" failed.
dpkg: error processing metalayer-crawler0 (--configure):
 subprocess post-installation script returned error exit status 1
dpkg: dependency problems prevent configuration of osso-software-version-rx34:
 osso-software-version-rx34 depends on metalayer-crawler0 (= 1.3.19-2);
however:
  Package metalayer-crawler0 is not configured yet.
dpkg: error processing osso-software-version-rx34 (--configure):
 dependency problems - leaving unconfigured
Errors were encountered while processing:
 metalayer-crawler0
 osso-software-version-rx34
E: Sub-process /usr/bin/dpkg returned an error code (1)

(In reply to comment #4)

> dpkg: dependency problems prevent configuration of osso-software-version-rx34:
>  osso-software-version-rx34 depends on metalayer-crawler0 (= 1.3.19-2);
> however:
>   Package metalayer-crawler0 is not configured yet.
> dpkg: error processing osso-software-version-rx34 (--configure):
>  dependency problems - leaving unconfigured
> Errors were encountered while processing:
>  metalayer-crawler0
>  osso-software-version-rx34
> E: Sub-process /usr/bin/dpkg returned an error code (1)
> 

A little more information about this.
"/etc/init.d/metalayer-crawler0 start" from the command-line returns zero (even
when it's already running) so shouldn't be returning an error.

The version of metalayer-crawler0 which the error says is required appears to
actually be installed:

# apt-cache show metalayer-crawler0
Package: metalayer-crawler0
Priority: optional
Section: misc
Installed-Size: 96
Maintainer: Pekka Marjola <pekka.marjola@nokia.com>
Architecture: armel
Source: metalayer-crawler
Version: 1.3.19-2
Depends: libc6 (>= 2.5.0-1), libdbus-1-3 (>= 0.94), libdbus-glib-1-2 (>= 0.74),
libgconf2-6 (>= 2.13.5), libglib2.0-0 (>= 2.12.12-1osso10), libmetalayer0 (>=
1.3.11), libosso-gnomevfs2-0, libosso1 (>= 2.16)
Filename: ./metalayer-crawler0_1.3.19-2_armel.deb
Size: 13580
MD5sum: ebcc56b2dfcb29c9ead17371973c38af
Description: Metalayer Crawler Daemon
 Crawler is a program that is always running on the background.
 The purpose of the program is to collect information about
 the comings and goings of media files in the system. The
 metadata of media files is automatically extracted using
 libmetalayer for other applications to use.

/etc/init.d currently contains both metalayer-crawler0 and
metalayer-crawler0.dpkg-dist

Comment 6 Ryan Abel 2008-12-18 21:05:54 UTC

(In reply to comment #5)
> A little more information about this.
> "/etc/init.d/metalayer-crawler0 start" from the command-line returns zero (even
> when it's already running) so shouldn't be returning an error.
> 

This bug is related to libc6 and doesn't have anything to do with
metalayer-crawler. Please limit bugs to a single issue only. If you're having
any issues with metalayer-crawler, then please open a separate bug. :)

(In reply to comment #2)
> I haven't removed libc6-dev, but since it can be upgraded (e.g. apt-get can
> cope with it), why should it be removed?

Upgrade worked after removing libc6-dev, but:
1. This was a bit annoying, in particular because the libc6-dev dependencies
needed to be removed too (and everything reinstalled after the upgrade). This
could have been critical, e.g. if the dependencies were no longer available for
download. The Application manager should really have been able to upgrade
libc6-dev too.
2. The error message (saying libc6 was missing) is wrong.

Same bug for me. "apt-get remove libc6-dev" as root gives "Package libc6-dev is
not installed, so not removed".

Contrary to Vincent, "apt-cache show libc6" gives" gives

[...]
Package: libc6
Status_ install ok installed
Prority: required
Section: libs
Installed-size: 8720
[...]
Version: 2.5.0-1osso9
Replaces: ldso (<= 1.9.1-9), timezone, timezones, gconv-modules, libtricks,
netkit-rpc, netbase (<< 4.0)
Provides: glibc--
[... same as for Vincent]

Comment 9 Andre Klapper 2009-01-15 16:12:41 UTC

Yves: Did you succeed anyhow to install?

Comment 10 Andre Klapper 2009-03-26 19:00:42 UTC

(Confirming as per comment 8)

Comment 11 Andre Klapper 2009-05-26 12:00:04 UTC

So why is libc6-dev is installed and where does it come from?

I assume that you're mixing repositories and that libc6-dev comes from a
Chinook repo so this is an INVALID bug. Feedback very welcome.

(In reply to comment #11)
> So why is libc6-dev is installed and where does it come from?

I had installed it with apt-get. It comes from:
http://repository.maemo.org/pool/diablo/free/g/glibc/

> I assume that you're mixing repositories and that libc6-dev comes from a
> Chinook repo so this is an INVALID bug. Feedback very welcome.

I don't think the bug comes from libc6-dev. As you can see the install worked
with

  apt-get install osso-software-version-rx44 bluez-utils=3.28-0osso6

i.e. libc6-dev could be upgraded by apt-get. I think the bug is just triggered
as a *side effect* when libc6-dev is installed. I suspect incorrect logic in
the dependency tracking; and this was solved by adding bluez-utils=3.28-0osso6
to the apt-get command line.

Comment 13 Andre Klapper 2009-06-19 18:59:31 UTC

Hmm, I'm quite sure that this is a WONTFIX for Diablo, and for Fremantle we
will see...

Comment 14 Andre Klapper 2009-09-30 17:14:38 UTC

I'd like to know if anybody can still reproduce this in Maemo5.
I haven't been able so far.
Setting to "moreinfo", please add a comment once Maemo5/the N900 is available
and if you can still reproduce this. Thanks in advance!

As written this is a WONTFIX for Maemo4 unfortunately as Maemo4 is in
maintenance mode and Nokia will only provide bugfixes for critical issues if at
all.
For your interest the Mer project aims to provide a community backport of
Maemo5 for N8x0 devices. See http://wiki.maemo.org/Mer for more information.

Comment 15 Andre Klapper 2009-12-30 15:54:16 UTC

This report was filed against Maemo4 ("Diablo").
The N900 and Maemo5 ("Fremantle") have been available for some time now.

If you own an N900, we kindly ask you to retest this with Maemo5 if possible,
and update this report by describing whether this still happens and which exact
Maemo5 version you use (Settings > General > About product).

This is unfortunately a WONTFIX for Maemo4 as Maemo4 is in maintenance mode and
Nokia will only provide bugfixes for critical issues if at all, as Nokia
currently seems to concentrate on Maemo5 and future Maemo releases. Hence
without any status updates, this report will be closed within the next months.

Sorry that your issue could not be fixed for Maemo4. For your interest the Mer
project aims to provide a community backport of Maemo5 for 770/N8x0 devices.
See http://wiki.maemo.org/Mer for more information.

For Maemo4, I worked around this problem some time ago (by removing and
reinstalling some packages IIRC). I'll have my N900 in a few days (after
waiting for a couple of months). So, I'll see whether I have such problems on
it...

Comment 17 Andre Klapper 2010-02-04 11:08:18 UTC

(In reply to comment #16)
> I'll have my N900 in a few days. I'll see whether I have such problems on it

Hi, ever run into this again on the N900?

No, but I haven't installed development packages yet.

Comment 19 Andre Klapper 2010-03-10 21:29:03 UTC

Until more information about its status for Maemo5 is available, I'm resolving
the report as WONTFIX for Maemo4 (Diablo).
Please feel free to reopen this bug if you can still reproduce this in Maemo5.