Gentoo Websites Logo
Go to: Gentoo Home Documentation Forums Lists Bugs Planet Store Wiki Get Gentoo!
Bug 378967 - Please stabilize dev-util/gtk-doc-am-1.17 on ppc and other arch's to resolve circular dependency between gtk-doc-am, pkgconfig, and
Summary: Please stabilize dev-util/gtk-doc-am-1.17 on ppc and other arch's to resolve ...
Status: RESOLVED DUPLICATE of bug 369909
Alias: None
Product: Gentoo Linux
Classification: Unclassified
Component: [OLD] Keywording and Stabilization (show other bugs)
Hardware: PPC Linux
: Normal normal (vote)
Assignee: Gentoo Linux Gnome Desktop Team
URL:
Whiteboard:
Keywords: STABLEREQ
Depends on:
Blocks:
 
Reported: 2011-08-12 19:33 UTC by Ian Stakenvicius (RETIRED)
Modified: 2012-02-24 22:20 UTC (History)
0 users

See Also:
Package list:
Runtime testing required: ---

Attachments
Add an attachment (proposed patch, testcase, etc.)

Note You need to log in before you can comment on or make changes to this bug.
Description Ian Stakenvicius (RETIRED) gentoo-dev 2011-08-12 19:33:14 UTC 
on #gentoo a user with ACCEPT_KEYWORDS="ppc" ran into the following circular dependency:


 * Error: circular dependencies:

(dev-util/gtk-doc-am-1.16::gentoo, ebuild scheduled for merge) depends on
 (dev-util/pkgconfig-0.26::gentoo, ebuild scheduled for merge) (buildtime)
  (dev-libs/glib-2.28.6::gentoo, ebuild scheduled for merge) (buildtime)
   (dev-util/gtk-doc-am-1.16::gentoo, ebuild scheduled for merge) (buildtime)


..a discussion with 'leio' revealed that this dep issue is fixed in gtk-doc-am-1.17 , which has been stabilized on x86 and amd64 but not on other arches.  

I couldn't find a stabilization bug already for gtk-doc-am-1.17 so i'm filing this one.

Reproducible: Always
Comment 1 Ian Stakenvicius (RETIRED) gentoo-dev 2011-08-12 20:48:58 UTC 
Aha; apparently the original bug for this circular dependency issue is bug 368301 ...
Comment 2 Pacho Ramos gentoo-dev 2011-08-13 12:45:56 UTC 
Newer gtk-doc* stabilization is covered in bug 369909
Comment 3 Pacho Ramos gentoo-dev 2011-08-13 12:46:08 UTC 

*** This bug has been marked as a duplicate of bug 369909 ***