| View previous topic :: View next topic |
| Author |
Message |
Joseph_sys
Advocate
Joined: 08 Jun 2004
Posts: 2062
Location: Edmonton, AB
|
 Posted: Thu Oct 22, 2009 5:50 am Post subject: [solved] unmasking zaptel-1.4 |
 |
|
I'm trying to emerge zaptel-1.4 but can't seem to find where zaptel-1.4 is masked.
| Code: | emerge -pv =zaptel-1.4.4
These are the packages that would be merged, in order:
Calculating dependencies... done!
!!! All ebuilds that could satisfy "=net-misc/zaptel-1.4.4" have been masked.
!!! One of the following masked packages is required to complete your request:
- net-misc/zaptel-1.4.4 (masked by: missing keyword) |
in package.keywords:
net-misc/zaptel ~amd64
package.unmask
<net-misc/asterisk-1.6
net-misc/zaptel
I don't see zaptel-1.4 being masked in /usr/portage/profiles/package.mask
I'm trying to build zaptel with oslec: http://www.rowetel.com/ucasterisk/oslec.html#install
But I think DAHDI is replacing zaptel so should I just go with DAHDI?
I'm trying to install sangoma usbfxo unit: http://wiki.sangoma.com/sangoma-wanpipe-usbfxo
and according to their instruction, when I'll be running their setup: | Quote: | Setup will ask you for location of zaptel sources?
[By default Setup will look in /usr/src/zaptel] |
so at this point I don't know if it will work as installing from ebuild as the setup is looking for source file in /usr/src/zaptel and there will be nothing there.
Should I just go and compile from all asterisk, zaptel from source?
_________________
#Joseph
Last edited by Joseph_sys on Thu Oct 22, 2009 1:21 pm; edited 1 time in total |
|
| Back to top |
|
 |
Veldrin
Veteran
Joined: 27 Jul 2004
Posts: 1586
Location: Zurich, Switzerland
|
| Posted: Thu Oct 22, 2009 7:57 am Post subject: |
|
|
| Quote: | | - net-misc/zaptel-1.4.4 (masked by: missing keyword) |
Please read the output! and it says missing keyword, which means no keyword! (read this as reference)
put the following into /etc/portage/package.keyword
cheers
V. |
|
| Back to top |
|
|
Joseph_sys
Advocate
Joined: 08 Jun 2004
Posts: 2062
Location: Edmonton, AB
|
| Posted: Thu Oct 22, 2009 1:20 pm Post subject: |
|
|
[quote="Veldrin"] | Quote: | [snip]
put the following into /etc/portage/package.keyword
|
When was this "**" keyword introduced? :-/
"~amd" is the first thing I tried but it didn't work. Oh well, we always learn something new.
Thanks
_________________
#Joseph |
|
| Back to top |
|
|
Veldrin
Veteran
Joined: 27 Jul 2004
Posts: 1586
Location: Zurich, Switzerland
|
| Posted: Thu Oct 22, 2009 1:26 pm Post subject: |
|
|
It was introduced some time ago....
In the normal case, you only need a testing package (and ~arch keyword), and basically tell portage that using ~arch is a valid keyword to. But if a package has no keywords, ** tells portage to ignore the missing keyword, and install it anyway.
hope this clarifies things
V. |
|
| Back to top |
|
|
|
Portage & Programming
