Need help with asterisk?

[Bernhard Schmidt]

On Sat, Oct 08, 2016 at 05:25:46PM +0200, Jonas Smedegaard wrote:

Hi Jonas,

> > I saw that asterisk is currently not in testing and the latest upload 
> > to unstable 40 days ago didn't even build on any architecture. Do you 
> > need any help packaging asterisk?
> >
> > I like freeswitch better myself, but my employer is using Asterisk as 
> > PBX and I would be in need of an Asterisk 13 anyway (for pjsip).
> >
> > I'm not sure how much I can help to fix #816042 though, since that bug 
> > has been filed even more largely unhandled security problems have been 
> > found.
> 
> Help would indeed be much appreciated!
> 
> It seems we are currently effectively 2 maintainers involved with 
> Asterisk, none of us able to catch up with the work needed for that 
> package: Tzafrir understands the code and packaging structure best, but 
> can silent for long stretches of time.  I can juggle patches and 
> packaging but not write C code, and also am bad¹ at being in 
> dialogue with the release team.

Funny, I cannot really write C code either (at least I would not want to
have to run it anywhere), but I can do packaging and debugging just
fine. Hope we'll manage and find someone. Maybe we should file a RFH bug
on Asterisk?

> Best would be if you can try look into squashing security-related bugs 
> in stable and oldstable.  Or I could could prepare that and you can take 
> the dialogue with the release team to get permission for releasing it.

I'll have a look at the one open security issue in stable, maybe I can
wrap something up that fixes AST-2016-007. Never dealt with the security
team either. Which brings me to

> You can also familiarize yourself with the way packaging is done, and 
> try update to newer upstream release.  But then please experiment 
> locally only at first, without pushing your changes without coordinating 
> first: I have an update in the works, not yet pushed because of issues I 
> haven't solved yet.  You might very well do a better hob than me - if we 
> are multiple persons interested in updating upstream code then let's 
> *both* share here on the list before pushing that.

because the current version in sid is also affected by AST-2016-007. I'm
fine with coordinating updates with you, can you share your current work
(and the problems you are having) somewhere, possibly a seperate git
branch? 

> How does that sound?  Did you have another appreach in mind?

Nopes, just fine.

> NB! If not already subscribed to the list then please do. :-)

Done.

Bernhard
-------------- next part --------------
A non-text attachment was scrubbed...
Name: signature.asc
Type: application/pgp-signature
Size: 819 bytes
Desc: Digital signature
URL: <http://lists.alioth.debian.org/pipermail/pkg-voip-maintainers/attachments/20161008/0d4a94b8/attachment.sig>