I need the following local use flags masked to remove asterisk-1.2.x from package.mask: Alpha: bri (zaptel and pri flag are already use.masked, this one uses the same packages) osp (osptoolkit is ~x86 only) HPPA: h323 (hppa is unsupported by the current versions of openh323 and pwlib ebuilds) osp (osptoolkit is ~x86 only) PPC, AMD64, SPARC: osp (osptoolkit is ~x86 only) thanks
CC'ed arch aliases
sparc done.
wouldn't be easyer test osptoolkit on ~arch?
Masked on alpha.
since osp is only available on x86, i masked it in base and only unmasked it for x86. removing amd64 and ppc, since these are done now
hppa done.
All archs have done their part. I think 1.2.X need to come out of p.mask, however bug #119625 states that 1.2.1 can no longer be downloaded, perhaps it should be removed? Also requesting a 1.2.3 ebuild please.
Make that a 1.2.4 request, it was just released. From asterisk.org: "2006-01-31 04:22 This update of Asterisk includes a fix for a significant memory leak in the expression parser that is present in all previous releases of Asterisk 1.2"
I have an ~amd64 system. I copied zaptel-1.2.3 to 1.2.4 and built the digest. (The new portage required me to rebuild prcrypt to get the digest to work. [ebuild R ] dev-python/pycrypto-2.0.1-r4 USE="-bindist -gmp -test" 0 kB) Zaptel 1.2.4 built OK: emerge --ask --verbose --deep zaptel These are the packages that would be merged, in order: Calculating dependencies... done! [ebuild R ] net-misc/zaptel-1.2.4 USE="-bri -devfs26 -ecaggressive -eckb1 -ecmark -ecmark2 -ecmark3 -ecmg2 -ecsteve -ecsteve2 -florz -rtc -ukcid -watchdog -zapnet -zapras" 0 kB Adding a USE flag for zaptel and rebuilding my asterisk worked also: emerge --ask --verbose --deep asterisk These are the packages that would be merged, in order: Calculating dependencies... done! [ebuild R ] net-misc/asterisk-1.0.10 USE="alsa gtk mysql speex zaptel -bri -debug -doc -hardened -minimal -mysqlfriends -postgres -pri -resperl -ukcid -vmdbmysql -vmdbpostgres" 0 kB
So is this slated to be unmasked so that 1.2.4 can be emerged?
asterisk 1.2.6 and zaptel 1.2.5 are out, and this is still masked. Any chances we get asterisk 1.2.x unmasked soon?
Also requesting removal from package.mask. The use.mask conditions noted have been satisfied according to the other posts here. I understand the purpose of masking unstable packages, but shouldn't there be some indication of WHY it was masked in the first place? Assuming it builds cleanly, why put it in package.mask? Isn't ~arch sufficient?
Well, I've given up on Gentoo/portage as far as asterisk goes. There hasn't been any noticeable activity on asterisk portage-wise for months. Asterisk and its related libraries have all been extremely stable for me, and trivial to install/upgrade from source. `make` `make install` ...has worked for me 100% of the time on Gentoo--don't even have to `./configure`!
There's an available overlay which is where they are working. http://svn.netdomination.org/gentoo-voip/ Not really sure why this stuff isn't going straight into Portage..
(In reply to comment #14) > There's an available overlay which is where they are working. > http://svn.netdomination.org/gentoo-voip/ Not really sure why this stuff isn't > going straight into Portage.. I went looking there and it isn't clear to me what the status is, looking at the unmask todo. Maybe the perfect is becoming the enemy of the OK? BTW, 1.2.7.1 was released on April 13, 2006.
all done
