Summary: | dependency on gtk-doc should be increased from >=1.13 to >=1.15-r2 | ||
---|---|---|---|
Product: | Gentoo Linux | Reporter: | Imran Sher Rafique <imran> |
Component: | [OLD] GNOME | Assignee: | Gentoo Linux Gnome Desktop Team <gnome> |
Status: | RESOLVED FIXED | ||
Severity: | normal | ||
Priority: | Normal | ||
Version: | unspecified | ||
Hardware: | All | ||
OS: | Linux | ||
Whiteboard: | |||
Package list: | Runtime testing required: | --- |
Description
Imran Sher Rafique
2011-04-12 02:09:52 UTC
>=gtk-doc-1.15 is already the oldest version you can find in tree so
(In reply to comment #1) > >=gtk-doc-1.15 is already the oldest version you can find in tree so Err, so what ... If glib is upgraded, and the currently installed gtk-doc is 1.13, then because of the outdated $DEPEND, gtk-doc won't be upgraded, and building of glib will fail. So either 1) folks can google for the error msgs from the failed glib build, find bug 334489, see that it was an issue with gtk-doc which was fixed in 1.15-r2, and then *manually* upgrade gtk-doc or 2) fix the outdated $DEPEND in glib, and emerge will automatically upgrade gtk-doc if necessary. Not trying to sound patronising or anything, but is this a serious discussion? (ie: is this not something which is ordinarily fixed?). I honestly assumed that someone just forgot to grep for gtk-doc in the DEPEND block for current ebuilds, when gtk-doc-1.15-r2 was added. (In reply to comment #2) > I honestly assumed that > someone just forgot to grep for gtk-doc in the DEPEND block for current > ebuilds, when gtk-doc-1.15-r2 was added. Needing to update all DEPENDs from all ebuilds to 1.15-r2 doesn't look viable to me :-| (In reply to comment #3) > Needing to update all DEPENDs from all ebuilds to 1.15-r2 doesn't look viable > to me :-| Ok, if gentoo devs don't want to fix any existing ebuilds with updated $DEPEND-ency info, then at least a note should be added to each pkg which is affected, so that *future* ebuilds will take note of the changed dep. Perhaps a 'FutureChanges' file to go along with the existing 'ChangeLog'. Otherwise, these required changes seem to slip through the cracks. Currently you have a number of glib ebuilds which were added to the tree *AFTER* the fixed gtk-doc-1.15-r2, but which still have the wrong $DEPEND info (hence this bug). Knowingly keeping a tree with known broken dependency info just seems, strange ... Maybe we could add a blocker of broken gtk-doc versions to gnome metas... :-/ + 05 Jun 2011; Pacho Ramos <pacho@gentoo.org> glib-1.2.10-r5.ebuild, + -files/glib-2.24-punt-python-check.patch, + -files/glib-2.26.1-gsettings-read.patch, + -files/glib-2.26.1-locked-message.patch, -glib-2.28.5.ebuild, + glib-2.28.7.ebuild: + Block broken gtk-doc versions that causes problems like bug #363213. Remove + old. Make repoman happier with glib-1. + |