[gentoo-user] there are no ebuilds to satisfy =x11-libs/gtk+-2.24.19.

2013-10-22 Thread Joseph

I'm tryint to emerge: gtk+-2.24.19 on one of my x86
but I'm getting:
there are no ebuilds to satisfy =x11-libs/gtk+-2.24.19.

I've created manifest in:
ebuild /usr/local/portage/x11-libs/gtk+/gtk+-2.24.19.ebuild manifest
Appending /usr/local/portage to PORTDIR_OVERLAY...

Creating Manifest for /usr/local/portage/x11-libs/gtk+


package.keywords has:
=x11-libs/gtk+-2.24.19 ~x86

--
Joseph



Re: [gentoo-user] there are no ebuilds to satisfy =x11-libs/gtk+-2.24.19.

2013-10-22 Thread Bruce Hill
On Tue, Oct 22, 2013 at 09:36:46AM -0600, Joseph wrote:
 I'm tryint to emerge: gtk+-2.24.19 on one of my x86
 but I'm getting:
 there are no ebuilds to satisfy =x11-libs/gtk+-2.24.19.
 
 package.keywords has:
 =x11-libs/gtk+-2.24.19 ~x86

That version is no longer in portage:

mingdao@baruch ~ $ eshowkw x11-libs/gtk+
Keywords for x11-libs/gtk+:
   |   | u   |  
   | a a p s   | n   |  
   | l m   h i m m   p s   p   | u s | r
   | p d a p a 6 i p c 3   a x | s l | e
   | h 6 r p 6 8 p p 6 9 s r 8 | e o | p
   | a 4 m a 4 k s c 4 0 h c 6 | d t | o
---+---+-+---
1.2.10-r12 | + + + + + o ~ + + o + + + | o 1 | gentoo
---+---+-+---
   2.24.16 | o o o o o o o o o + o o o | o 2 | gentoo
[I]2.24.17 | + + + + + o ~ + + o + + + | o   | gentoo
   2.24.22 | ~ ~ ~ ~ ~ o ~ ~ ~ o ~ ~ ~ | o   | gentoo
---+---+-+---
  [I]3.4.4 | + + + + + o ~ + + + + + + | o 3 | gentoo
 3.6.3-r3  | ~ ~ + ~ ~ o ~ ~ ~ o ~ ~ ~ | o   | gentoo
 3.8.4 | ~ ~ ~ ~ ~ o ~ ~ ~ o ~ ~ ~ | #   | gentoo
 3.8.6 | ~ ~ ~ ~ ~ o ~ ~ ~ o ~ ~ ~ | o   | gentoo

By putting =category/package-atom in package.accept_keywords (not
package.keywords) you have limited it to that one single version and unstable
package.

Also, you need not put ~arch in package.accept_keywords because that file will
pull whatever the latest version is available for category/package.

Try changing your =x11-libs/gtk+-2.24.19 ~x86 to x11-libs/gtk+ and emerge
again.

Or, because you appear to have two separate issues here...

 I've created manifest in:
 ebuild /usr/local/portage/x11-libs/gtk+/gtk+-2.24.19.ebuild manifest
 Appending /usr/local/portage to PORTDIR_OVERLAY...
  Creating Manifest for /usr/local/portage/x11-libs/gtk+

Now, if you have created your own local overlay and ebuild, you need to also
provide the source and needed patches for x11-libs/gtk+-2.24.19
-- 
Happy Penguin Computers   ')
126 Fenco Drive   ( \
Tupelo, MS 38801   ^^
supp...@happypenguincomputers.com
662-269-2706 662-205-6424
http://happypenguincomputers.com/

A: Because it messes up the order in which people normally read text.
Q: Why is top-posting such a bad thing?
A: Top-posting.
Q: What is the most annoying thing in e-mail?

Don't top-post: http://en.wikipedia.org/wiki/Top_post#Top-posting



Re: [gentoo-user] there are no ebuilds to satisfy =x11-libs/gtk+-2.24.19.

2013-10-22 Thread Joseph

Thank Bruce,
My problem was that I was missing in make.conf
PORTDIR_OVERLAY=/usr/local/portage

This solved my problem.

--
Joseph


On 10/22/13 11:32, Bruce Hill wrote:

On Tue, Oct 22, 2013 at 09:36:46AM -0600, Joseph wrote:

I'm tryint to emerge: gtk+-2.24.19 on one of my x86
but I'm getting:
there are no ebuilds to satisfy =x11-libs/gtk+-2.24.19.

package.keywords has:
=x11-libs/gtk+-2.24.19 ~x86


That version is no longer in portage:

mingdao@baruch ~ $ eshowkw x11-libs/gtk+
Keywords for x11-libs/gtk+:
  |   | u   |
  | a a p s   | n   |
  | l m   h i m m   p s   p   | u s | r
  | p d a p a 6 i p c 3   a x | s l | e
  | h 6 r p 6 8 p p 6 9 s r 8 | e o | p
  | a 4 m a 4 k s c 4 0 h c 6 | d t | o
---+---+-+---
   1.2.10-r12 | + + + + + o ~ + + o + + + | o 1 | gentoo
---+---+-+---
  2.24.16 | o o o o o o o o o + o o o | o 2 | gentoo
[I]2.24.17 | + + + + + o ~ + + o + + + | o   | gentoo
  2.24.22 | ~ ~ ~ ~ ~ o ~ ~ ~ o ~ ~ ~ | o   | gentoo
---+---+-+---
 [I]3.4.4 | + + + + + o ~ + + + + + + | o 3 | gentoo
3.6.3-r3  | ~ ~ + ~ ~ o ~ ~ ~ o ~ ~ ~ | o   | gentoo
3.8.4 | ~ ~ ~ ~ ~ o ~ ~ ~ o ~ ~ ~ | #   | gentoo
3.8.6 | ~ ~ ~ ~ ~ o ~ ~ ~ o ~ ~ ~ | o   | gentoo

By putting =category/package-atom in package.accept_keywords (not
package.keywords) you have limited it to that one single version and unstable
package.

Also, you need not put ~arch in package.accept_keywords because that file will
pull whatever the latest version is available for category/package.

Try changing your =x11-libs/gtk+-2.24.19 ~x86 to x11-libs/gtk+ and emerge
again.

Or, because you appear to have two separate issues here...


I've created manifest in:
ebuild /usr/local/portage/x11-libs/gtk+/gtk+-2.24.19.ebuild manifest
Appending /usr/local/portage to PORTDIR_OVERLAY...
 Creating Manifest for /usr/local/portage/x11-libs/gtk+


Now, if you have created your own local overlay and ebuild, you need to also
provide the source and needed patches for x11-libs/gtk+-2.24.19
--
Happy Penguin Computers   ')
126 Fenco Drive   ( \
Tupelo, MS 38801   ^^
supp...@happypenguincomputers.com
662-269-2706 662-205-6424
http://happypenguincomputers.com/