new version, new stuff: * support for mysql + postgresql database backends for voicemail * postgres support * asterisk-config patch for external plugins (like app_ldap and chan_bluetooth) * new version of chan_oh323 (-0.6.5, if i win the stkn vs. makefiles fight...) * new (lots of brainfarts fixed) version of the zaptel devfs on linux-2.6 patch (confirmed user-base: 1) * >maybe< the beginning (*sigh*) of running asterisk as non-root support * and maybe other nice stuff if i get the time for that... * new channel: #gentoo-voip @ irc.freenode.net
Created attachment 49698 [details, diff] diff for the current ebuild version (20050127)
Created attachment 49699 [details, diff] required patch (20050127)
Created attachment 49700 [details] app_ldap-0.8 ebuild
Created attachment 49701 [details, diff] asterisk-config patch for app_ldap
Created attachment 49702 [details] chan_bluetooth ebuild
Created attachment 49703 [details, diff] asterisk-config patch for chan_bluetooth
Created attachment 49879 [details] ebuild for app_iconv-0.8
Created attachment 49880 [details, diff] patch for app_iconv to use asterisk-config
Created attachment 49882 [details] py-asterisk-0.1a3 ebuild (Python bindings for asterisk) Doesn't depend on asterisk-config (should work with other versions)
Created attachment 49890 [details] ebuild for chan_capi-0.3.5 should work w/ all >=asterisk-1.0.0
Created attachment 49891 [details, diff] required patch for chan_capi ebuild
Created attachment 50604 [details] asterisk-chan-capi-0.3.5.ebuild Updated asterisk-chan-capi ebuild. This ebuild was originally imported from svn://gentoo.datacore.ch/read-only and was written by amir@datacore.ch. I added a CAPI kernel check and Stefans patch.
Created attachment 50605 [details] asterisk-chan-capi/ChangeLog Original Changelog from amir@datacore.ch
Created attachment 50608 [details] asterisk-chan-capi-0.3.5.ebuild The original stkn ebuild fails when building in a sandbox. Reinserted the sed line from amir ebuild.
> The original stkn ebuild fails when building in a sandbox. Reinserted the sed > line from amir ebuild. Where does it fail? (I doubt that was my ebuild) And btw. i won't accept the new ebuild in it's current state: 1) sed -i -e "s:^INSTALL_PREFIX=$:INSTALL_PREFIX=${D}:" Makefile unnecessary, make INSTALL_PREFIX=${D} ... does the trick 2) insinto /usr/lib/asterisk/modules emake DESTDIR=${D} install || die "Make install failed" insinto /etc/asterisk emake DESTDIR=${D} config || die "Make config failed" DESTDIR=${D} doesn't work, it's not used by the Makefile (and one make line with both targets would be enough too) insinto is wrong that's used with doins, for creating directories we have dodir and that is not necessary either (see patch)
Created attachment 50830 [details] asterisk-chan-capi-0.3.5.ebuild Yet another ebuild. Basically the same as stkn original with the capi kernel check. Yup, DESTDIR etc. from the amir ebuild was unnecessary, thats why it failed with sandbox (not stkn ebuild).
app_ldap-0.9.3 app_iconv-0.8 chan_bluetooth-0.0.1_pre2005021? are in cvs now
only thing left is py-asterisk
Created attachment 159674 [details] ebuild for py-asterisk-0.1_alpha2 Best regards,
Created attachment 159675 [details] ebuild for py-asterisk-0.1_alpha2 - corrected keywords
Created attachment 159676 [details] ebuild for py-asterisk-0.1_alpha2 - corrected keywords. Corrected Keywords.. sorry
Created attachment 160221 [details] py-asterisk-0.1_alpha2.ebuild Fixed
Created attachment 160223 [details] ebuild for py-asterisk-0.1_alpha2.ebuild Removed redundant inherit python
Reassigning back to herd since Stefan has been retired as a Gentoo Developer (#27693).
Jesus, are you still interested by this package ?
No one to take this bug ? If no one react, I will re-assign it to maintainer-wanted.
Assigning to maintainer-wanted
The latest release on project homepage is 0.1a3 which has been made 2004-10-06. There's following message on the homepage: "Are you a py-Asterisk user that would like to keep the project alive? I am presently unable to work much on py-Asterisk much due to work and life pressures in general. However, I would very much like to see py-Asterisk continue to track the current state of Asterisk, and be useful to the community as a whole. I have moved the project to Berlios in order to allow for easier participation from users and developers. Please contact the developer list if you would like access to this new project." Latest useful thread in project -dev mailing list: https://lists.berlios.de/pipermail/py-asterisk-dev/2009-April/thread.html. The last question has no answer. Last SVN commit: "Rev 173 - 2008-12-10 15:30:29 GMT * Create a new branch for César GarcÃa." There's no visible changes for almost a year, and no maintainter to address to. Zombie?
As per research by Arseny Solokha, this appears to be well and truly dead upstream. As such, I can not and will not package this for the portage tree.