Re: testing asterisk for Wheezy LTS
Oops, I forgot to mention that I am not subscribed to the mailing list. So please include me in CC for replies. > thanks alot for testing the package, I really appreciate it. > > On Thu, 28 Apr 2016, Gabriel Filion wrote: > >> https://people.debian.org/~alteholz/packages/wheezy-lts/asterisk/amd64/ >> >>however I've found a regression: manager connections (in my case >>established from localhost) are super slow and/or not responding at all. > > > ok, I uploaded a new package (with the same version), so if you don't > mind can you please test it again? Thanks for the update. I've downloaded the new packages and tested them and they seem to be working great. SIP/IAX2 are working fine and the management port is responding correctly this time. I've also tested the voicemail app and it's responding OK. signature.asc Description: OpenPGP digital signature
Re: Wheezy update of roundcube?
Hi there, On Mon, 02 May 2016 at 21:19:13 +0200, Markus Koschany wrote: > Would you like to take care of this yourself? Not replying in the name of team (however I'm the one who pushed for Roundcube in jessie-backports and who is trying to taking care of it there), unfortunately I don't have the time nor energy to take care of an oldstable version. That being said, I think packaging the Roundcube 1.0.x (stable) branch would be the easiest for Wheezy. https://github.com/roundcube/roundcubemail/releases/ Cheers, -- Guilhem. signature.asc Description: PGP signature
Wheezy update of roundcube?
Hello dear maintainer(s), the Debian LTS team would like to fix the security issues which are currently open in the Wheezy version of roundcube: https://security-tracker.debian.org/tracker/CVE-2016-4068 We know that roundcube is at least affected by CVE-2016-4068 in Wheezy but we are interested in your opinion too. Would you like to take care of this yourself? If yes, please follow the workflow we have defined here: https://wiki.debian.org/LTS/Development If that workflow is a burden to you, feel free to just prepare an updated source package and send it to debian-lts@lists.debian.org (via a debdiff, or with an URL pointing to the source package, or even with a pointer to your packaging repository), and the members of the LTS team will take care of the rest. Indicate clearly whether you have tested the updated package or not. If you don't want to take care of this update, it's not a problem, we will do our best with your package. Just let us know whether you would like to review and/or test the updated package before it gets released. Thank you very much. Markus Koschany, on behalf of the Debian LTS team. PS: A member of the LTS team might start working on this update at any point in time. You can verify whether someone is registered on this update in this file: https://anonscm.debian.org/viewvc/secure-testing/data/dla-needed.txt?view=markup
Re: Sending LTS changes to debian-lts-changes
Raphael Hertzog writes: > On Mon, 02 May 2016, Markus Koschany wrote: >> thank you for fixing the mirror bug. Moritz Mühlenhoff informed us on >> IRC that accepted mails for LTS uploads are still sent to dak AT >> security.debian.org. Can you filter those mails so that they are sent to >> debian-lts-changes instead and if possible also to >> dispatch _AT_ tracker.debian.org as Raphael had suggested? [1] > > Send them first only to debian-lts-changes@ as it might be that the > tracker gets them that way too. Now I already set both mail addresses. Should I change that to only debian-lts-changes@? Note that security.d.o doesn't sent mail to @packages.qa.d.o. > (That said dak needs a general cleanup to send mail to the new tracker > directly and stop relying on @packages.qa.debian.org, as nobody did > anything in response to > https://lists.debian.org/debian-devel-announce/2015/12/msg1.html) Should I just add dispatch@tracker.d.o to all suites where we sent out announcement mails for? And in that case stop sending mail to @packages.qa.d.o? And it looks like we also sometimes send mail to @packages.d.o. So many different choices :) Ansgar
Sending LTS changes to debian-lts-changes
Hi Ansgar, thank you for fixing the mirror bug. Moritz Mühlenhoff informed us on IRC that accepted mails for LTS uploads are still sent to dak AT security.debian.org. Can you filter those mails so that they are sent to debian-lts-changes instead and if possible also to dispatch _AT_ tracker.debian.org as Raphael had suggested? [1] Cheers, Markus [1] https://lists.debian.org/debian-lts/2016/04/msg00140.html signature.asc Description: OpenPGP digital signature
Re: Supporting libav in wheezy
Hi, have you asked the libav maintainers for support / feedback? They might not be able to do the work, but I could imagine they would help with hints and reviews or such… -- cheers, Holger signature.asc Description: Digital signature
Supporting libav in wheezy
Hello, On Sun, 13 Mar 2016, Brian May wrote: > > 2. Spend some time on investigating what it takes to backport > > libav from jessie to wheezy. 11.x is still supported by > > Looks like the SONAME has changed. Presumably this means anything > depending on libav will need to be rebuilt? There's also an alternate way to go forward... continue to support the current version with paid external help if needed. You might want to get in touch with https://libav.org/consulting/ and see if one of them would be willing to do this work. Sebastian Ramacher pointed us to this list when we seeked his opinion to see whether we could support vlc/libav in wheezy. We have 15% of the sponsors listing at least one of the binary packages built by libav in their package list. That's relatively close to Xen (17.4%) where we are going to spend money for external help. That said none of the customers expressed their reliance on this package when I asked on the private list while they were quick to respond for their need of Xen. I did not list this package explicitly in https://wiki.debian.org/LTS/TODO#Find_upstream_developers_who_are_willing_to_work_on_LTS_support but it's something that can we can consider for any package used by LTS sponsors if needed (and I did list vlc so its dependencies can be implicitly integrated as well). Cheers, -- Raphaël Hertzog ◈ Debian Developer Support Debian LTS: http://www.freexian.com/services/debian-lts.html Learn to master Debian: http://debian-handbook.info/get/
Looking for programmers handling security updates for Debian 7 LTS
Hello, the amount of sponsorship for Debian LTS[1] has increased over the last couple of months and a few paid contributors took a break, so we are still actively looking for Debian contributors wishing to be paid to provide security updates for Debian 7 Wheezy. Please see the announce I posted earlier this year: https://raphaelhertzog.com/2016/01/14/working-as-a-paid-lts-contributor/ And also the details on Freexian's website: https://www.freexian.com/services/debian-lts-details.html#join Please get in touch with me if you are interested. Cheers, [1] https://wiki.debian.org/LTS PS: I post this with my "Freexian manager" hat. I want to ensure that we have enough contributors to pay to spend all the sponsorship that Freexian is collecting (and thus to do all the security work that needs to happen). -- Raphaël Hertzog ◈ Freexian SARL ◈ Tel: +33 (0)6 88 21 35 47 http://www.freexian.com signature.asc Description: PGP signature
