Bug 153959 - app-editors/katoob-0.5.5 version bump
|
Bug#:
153959
|
Product: Gentoo Linux
|
Version: unspecified
|
Platform: All
|
|
OS/Version: Linux
|
Status: RESOLVED
|
Severity: enhancement
|
Priority: P2
|
|
Resolution: FIXED
|
Assigned To: leonardop@gentoo.org
|
Reported By: pharon@gmail.com
|
|
Component: Ebuilds
|
|
|
URL:
|
|
Summary: app-editors/katoob-0.5.5 version bump
|
|
Keywords: EBUILD
|
|
Status Whiteboard:
|
|
Opened: 2006-11-03 12:01 0000
|
A new version of katoob that needs libgtksourceviewmm which is not in portage.
I submitted an ebuild for that here :
http://bugs.gentoo.org/show_bug.cgi?id=153958
and added it to the depends.
It is needed for the optional feature of syntax highlighting.
I've committed an ebuild for katoob-0.5.6.
Thanks for the contribution.
(In reply to comment #2)
> new ebuild with highlight useflag added which depeneds on libgtksourceviewmm.
Reopen, please check the keywording on dependencies...
app-editors/katoob-0.5.6: depends ~ppc: unsolvable selinux/ppc/ppc32/2006.1/G3,
solutions: [ >=dev-cpp/libgtksourceviewmm-0.2 ]
app-editors/katoob-0.5.6: depends ~ppc: unsolvable hardened/ppc, solutions: [
>=dev-cpp/libgtksourceviewmm-0.2 ]
app-editors/katoob-0.5.6: depends ~ppc: unsolvable
default-linux/ppc/ppc32/2006.1, solutions: [ >=dev-cpp/libgtksourceviewmm-0.2 ]
app-editors/katoob-0.5.6: depends ~ppc: unsolvable selinux/ppc/ppc32/2006.1/G4,
solutions: [ >=dev-cpp/libgtksourceviewmm-0.2 ]
app-editors/katoob-0.5.6: rdepends ~ppc: unsolvable
selinux/ppc/ppc32/2006.1/G3, solutions: [ >=dev-cpp/libgtksourceviewmm-0.2 ]
app-editors/katoob-0.5.6: rdepends ~ppc: unsolvable hardened/ppc, solutions: [
>=dev-cpp/libgtksourceviewmm-0.2 ]
app-editors/katoob-0.5.6: rdepends ~ppc: unsolvable
default-linux/ppc/ppc32/2006.1, solutions: [ >=dev-cpp/libgtksourceviewmm-0.2 ]
app-editors/katoob-0.5.6: rdepends ~ppc: unsolvable
selinux/ppc/ppc32/2006.1/G4, solutions: [ >=dev-cpp/libgtksourceviewmm-0.2 ]
I don't have ppc so I don't understand what is the problem. Please explain.
Thanks for the notice Jakub.
Just for reference, this seems like a recent bug in portage. repoman from both
portage-2.1.2_rc3-r6 and -r7 didn't report this. I had to go back to 2.1.1-r2
to see the error.