Bug 872 - eglibc-dbg dependencies
Summary: eglibc-dbg dependencies
Status: RESOLVED WORKSFORME
Alias: None
Product: OE-Core
Classification: Build System, Metadata & Runtime
Component: devtools / tool chain (show other bugs)
Version: 1.0
Hardware: x86 Multiple
: Low minor
Target Milestone: 1.1
Assignee: Nitin Kamble
QA Contact:
URL:
Whiteboard:
Depends on:
Blocks:
 
Reported: 2011-03-15 04:24 UTC by Qing He
Modified: 2011-08-23 13:46 UTC (History)
6 users (show)

See Also:
OS type for building Yocto: ---
Type of Regression: ---
Verified:
Documentation change: ---


Attachments

Note You need to log in before you can comment on or make changes to this bug.
Description Qing He 2011-03-15 04:24:48 UTC
When trying to install db-dbg in the target using zypper, some interesting dependency error is reported:

> # zypper install db-bin
> # zypper install db-dbg    # ignoring some libc6 installation issues (bug 803)
>
> Problem: nothing provides eglibc-binary-localedata-aa.dj-dbg
>    needed by eglibc-dbg-2.12-r13.x86_64

the locale "aa-dj" does exist, but the package name seems wrong, it should be "*-aa-dj.dbg", not "*-aa.dj-dbg"

And also, this particular package: eglibc-binary-localedata-aa-dj.dbg, doesn't exist on my build, per my understanding, all eglibc related debug symbols are collectively packaged as eglibc-dbg, so where is this ill-formed package dependency comes out?
Comment 1 Mark Hatle 2011-03-15 08:09:15 UTC
This is partially a duplicate of 821.  The Zypper issue is that it doesn't understand requirement "hints" yet.  So any requirement it sees becomes a hard required dependency -- so files that don't exist become failure.

The second issue (which is why I didn't close this bug) is that these invalid -dbg files are showing up within the package itself.  We should attempt to find and fix the package requirements and not include -dbg packages that are not likely to exist.
Comment 2 Nitin Kamble 2011-04-26 10:47:58 UTC
will wait for zypper issue get fixed, and then look into the eglibc depedency issue.
Comment 3 Nitin Kamble 2011-08-16 12:06:43 UTC
Qing,
   Is this issue still present? if yes how to reproduce it.
Comment 4 Mark Hatle 2011-08-17 08:39:17 UTC
Zypper has not been enhanced to know about the dependency hints at this point.

I believe the second issue still exists.  Being that many packages get hints for debug packages that simply don't exist.

To view the list, you should be able to run: "rpm -qp <package> --requires"

You will likely see a set of -dbg packages listed that don't exist.
Comment 5 Nitin Kamble 2011-08-19 09:10:15 UTC
I have not use zypper before, are you configuring a repository for zypper installation? can you give me detailed instructions to reproduce this issue.

Thanks,
Nitin
Comment 6 Nitin Kamble 2011-08-19 12:36:31 UTC
I just ttried this, and did not meet any issues from qemu machine. so seems like the issue is not present anymore. please confirm.

root@qemuppc:~# zypper install db-dbg-5.1.19-r3.ppc603e.rpm 
Loading repository data...
Reading installed packages...
Resolving package dependencies...

The following NEW package is going to be installed:
  db-dbg 

1 new package to install.
Overall download size: 3.9 MiB. After the operation, additional 11.4 MiB will 
be used.
Continue? [y/n/?] (y): y
Retrieving package db-dbg-5.1.19-r3.ppc603e (1/1), 3.9 MiB (11.4 MiB unpacked)
Retrieving package db-dbg-5.1.19-r3.ppc603e (1/1), 3.9 MiB (11.4 MiB unpacked)
Installing: db-dbg-5.1.19-r3 [done]
Comment 7 Nitin Kamble 2011-08-23 13:46:27 UTC
closing this bug as the issue is not present anymore.