On Sun, 2009-02-15 at 00:26 +0100, Philipp Thomas wrote:

On Sat, 14 Feb 2009 17:04:59 -0500, you wrote:

...

What is going on with the quality of openSUSE 11.1? It's not even possible to use Asterisk PBX!

Seems like you don't have a clue. Asterisk is *not* maintained by a Novell employee but by someone from the community. If that person hasn't yet maintained his package it's not the fault of Novell/SuSE and it also has nothing to do with the quality of openSUSE 11.1.

...

Bug reported here over 1 month ago with ZERO updates of any sort: https://bugzilla.novell.com/show_bug.cgi?id=465210

Have you looked at who the bugowner is? It was opensuse-communityscreening@forge.provo.novell.com, a mailinglist where anybody who wants to help screening bugs can subscribe. Again, this is voluntary community work and if no one reacts it's only the community you can blame.

...

Tried to compile from source, but it requires termcap-devel which is not a part of openSUSE 11.1 at all.

I checked the build logs of asterisk and some of the packages it needs and that are also part of network:telephony and it seems that at least zaptel needs to be modified because it installes in paths that aren't allowed anymore (binary in /sbin that needs libraries in /usr/lib). I guess the other failing packages fail for similiar reasons. This needs someone from the community (preferably the maintainer(s) of the package) to fix these packages. This is nothing Novell/SuSE can force.

All in all you're barking up the wrong tree. What you could do is write to the maintainers of network:telephony and politely ask if one of them could possibly fix the packages so that asterisk builds again.

Philipp

About clues... It's not the quality of 11.1, but asterisk itself. Asterisk _was_ maintained by SuSE First, it was included in the oss tree. Later, it moved to repo/network/telephony Now, for 11.1 only packages are in repo/home:/vitsoft. (due to build errors) SuSE (SLES9) use to be an official supported platform for the asterisk-bussines-edition, but they decided to drop it! One of problems with asterisk is the fast paste of their releases, and their stability of the code. When diving in their code, one doesn't become happy either. According to their own docu, it should run on any linux distro and even of other platforms like bsd. Previously one could just grep their tars and recompile the lot, and it simply worked. That isn't the case any more. Here (dahdi-startup-script) and there you find contrunctions like: default distro=redhat if !(some-condition) then distro=debian.... Obviously that doesn't work for us And the 1.4.23 tarbal gets you several pages of complilation errors.. On systems with hardware involved (zaptel, libpri) one have to stay at suse_10.3. Any upgrade will kill asterisk. If no zaptel/dahdi/pri hw-involved you can use the asterisk and asterisk16 packages. Eventhough at the http://software.opensuse.org/search you can get a one-click-installation of (asterisk) packages, I would seriously advise anyone to use anything important to you that is only available in any repo/home:/ area. Now you see it's there but tomorrow it doesn't have to be there, And it's build as that particular persons needs. No commitment regarding maintenance or quality And afaicr, bugzilla is only for official packages, not those from obs. hw -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org For additional commands, e-mail: opensuse+help@opensuse.org

On Mon, Feb 16, 2009 at 03:20, Dave Cotton wrote:

All versions of Asterisk 1.4 and 1.6.0 and even 1.6.1 have compiled and run on this X86_64 machine and also my other 32bit machines.

No termcap-devel is installed on any of them.

When I try to install the latest 1.4 version, I get the error "Configure: error: termcap support not found." Did you encounter this? -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org For additional commands, e-mail: opensuse+help@opensuse.org