Gentoo Websites Logo
Go to: Gentoo Home Documentation Forums Lists Bugs Planet Store Wiki Get Gentoo!

Bug 416837

Summary: Request upgrade of media-gfx/argyllcms to 1.3.7
Product: Gentoo Linux Reporter: Michael Mol <mikemol>
Component: Current packagesAssignee: Andreas K. Hüttel <dilfridge>
Status: RESOLVED DUPLICATE    
Severity: enhancement CC: xmw
Priority: Normal    
Version: unspecified   
Hardware: All   
OS: Linux   
Whiteboard:
Package list:
Runtime testing required: ---

Description Michael Mol 2012-05-21 01:49:40 UTC
Latest in portage is 1.3.5. 1.3.6 adds support for the Spyder4 (which is what I need). 1.3.7 fixes a regression introduced in 1.3.6.

Reproducible: Always
Comment 1 Mike Gilbert gentoo-dev 2012-05-21 01:56:14 UTC
Um... upgrade what to 1.3.7?
Comment 2 Michael Mol 2012-05-21 02:04:32 UTC
Whups. I could have sworn I'd included the package name. Fixed.
Comment 3 Michael Weber (RETIRED) gentoo-dev 2012-05-21 02:11:14 UTC
Hi,

version 1.4.0 is in the tree, but it's not jet been marked stable.

Andreas, any objections against adding arches for an stable request?

Michael
Comment 4 Michael Mol 2012-05-21 02:12:16 UTC
My bad. My cron'd eix-sync must have missed. -.-
Comment 5 Michael Weber (RETIRED) gentoo-dev 2012-05-21 02:17:04 UTC
Bug 416781 already stabilizes version 1.4.0.

@Michael: Being in tree does not mean stable-in-tree. You have to add stable keywords for version 1.4.0 if you really want to have it installed (or wait for mentionen bug to hit your arch).

If you're unfamiliar with keywording, take a look at http://www.gentoo.org/doc/en/handbook/handbook-amd64.xml?part=3&chap=3 please.
Comment 6 Michael Weber (RETIRED) gentoo-dev 2012-05-21 02:17:29 UTC

*** This bug has been marked as a duplicate of bug 16781 ***
Comment 7 Michael Weber (RETIRED) gentoo-dev 2012-05-21 02:17:41 UTC

*** This bug has been marked as a duplicate of bug 416781 ***
Comment 8 Michael Mol 2012-05-21 02:18:18 UTC
@Michael, no, the problem really was that I apparently hadn't synced my portage tree in a while.

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