Bug#867113: does not start as soon as server-ipv6 is set

Control: tags -1 + moreinfo Control: forwarded -1 https://community.openvpn.net/openvpn/ticket/911 On 04.07.2017 09:52, Marc Haber wrote: Hi Marc, > On Mon, Jul 03, 2017 at 11:39:58PM +0200, Marc Haber wrote: >> Jul 3 23:33:11 torres ovpn-server[5730]: /sbin/ip link set dev tun0 up mtu >>

Bug#866523: Duplicate systemd units

Package: openvpn Version: 2.4~rc1-1 Severity: important Since 2.4~rc1-1 the OpenVPN binary package ships two additional systemd units from upstream /lib/systemd/system/openvpn-client@.service /lib/systemd/system/openvpn-server@.service in addition to the ones that are Debian specific

Bug#828477: openvpn: FTBFS with openssl 1.1.0

Am 29.06.2017 um 06:31 schrieb Dr. Markus Waldeck: Hi Markus, > this topic should have gone directly to you: > > OpenSSL 1.1 support in OpenVPN > >> has been fixed in 2.4.3, but switching over is >> currently blocked by libpkcs11-helper1-dev depending on libssl1.0-dev >> (presumably because of

Bug#828477: openvpn: FTBFS with openssl 1.1.0

Control: blocks 828477 859555 On Sat, Jun 24, 2017 at 11:24:18AM +0200, Dr. Markus Waldeck wrote: Hi, > this defect will be fixed in OpenVPN 2.5. > > OpenVPN 2.5_git [git:master/0402c7faadf907d4] x86_64-pc-linux-gnu [SSL > (OpenSSL)] [EPOLL] [MH/PKTINFO] [AEAD] built on Jun 23 2017 > library

Bug#865555: RFA: openvpn -- virtual private network daemon

Control: retitle -1 ITA: openvpn -- virtual private network daemon On Fri, Jun 23, 2017 at 07:21:26AM +0200, Jörg Frings-Fürst wrote: > Alberto thanks for your work. > > Bernhard, I would also like to contribute as a co-maintainer. Okay then. git repo is already on collab-maint, but seems to

Bug#865480: openvpn: CVE-2017-7508 CVE-2017-7520 CVE-2017-7521

On Wed, Jun 21, 2017 at 09:56:14PM +0200, Salvatore Bonaccorso wrote: Hi, > Source: openvpn > Version: 2.3.4-1 > Severity: grave > Tags: security upstream > > Hi, > > the following vulnerabilities were published for openvpn. In light of the recent RFA bug on OpenVPN, has there any work been

Bug#865631: [pkg-ntp-maintainers] Bug#865631: ntp: Doesn't start

Hi, > Package: ntp > Version: 1:4.2.8p10+dfsg-5 > Severity: normal > > Dear Maintainer, > > Fail to upgrade or here start after a removal. > > Here is the apt-get output and then 'journalctl -xe' : > > Setting up ntp (1:4.2.8p10+dfsg-5) ... > Created symlink

Bug#865555: RFA: openvpn -- virtual private network daemon

On Thu, Jun 22, 2017 at 07:24:14PM +0200, Alberto Gonzalez Iniesta wrote: Hi, > Due to lack of time I request an adopter for the openvpn package. I'd be willing to co-maintain, but definitely not do it alone. Alberto, thanks a lot for the maintenance this far. Really appreciated. Bernhard

Bug#865285: [pkg-ntp-maintainers] Bug#865285: sntp: Cannot open KoD db file /var/db/ntp-kod: No such file or directory

Control: forcemerge -1 863873 Control: found 863873 1:4.2.8p10+dfsg-4 Am 20.06.2017 um 11:12 schrieb Laurent Bonnaud: Hi, > here is the problem: > > # sntp pool.ntp.org > sntp 4.2.8p10@1.3728-o (1) > kod_init_kod_db(): Cannot open KoD db file /var/db/ntp-kod: No such file or > directory >

Bug#422347: can't get ntpq without ntpd

Am 20.06.2017 um 03:33 schrieb Vincent Lefevre: > On 2017-06-19 23:55:04 +0200, Bernhard Schmidt wrote: >> Marking as wontfix since this is not going to be changed in stable >> releases. > > Most bugs are in that case, so "wontfix" is improper. What matters

Bug#801852: Promote libzeromq-perl to (at least) Recommends: field.

On Thu, Oct 15, 2015 at 10:11:07AM +, Mike Gabriel wrote: > We just found an issue with amavisd-status and amavis-service executables > missing ZMQ::LibZMQ3. > > """ > >root@office:/etc/amavis/conf.d# amavisd-status > >Perl modules ZMQ::LibZMQ3 or ZMQ::LibZMQ2 or ZeroMQ not available >

Bug#863906: AST-2017-004: Memory exhaustion on short SCCP packets

Package: src:asterisk Version: 1:13.0.0~dfsg-1 Severity: critical Tags: security Asterisk Project Security Advisory - AST-2017-004 Product Asterisk Summary Memory exhaustion on short SCCP packets

Bug#863902: AST-2017-003: Crash in PJSIP multi-part body parser

Package: src:pjproject Version: 2.5.5~dfsg-5 Severity: critical Tags: security patch The following security advisory was published by the Asterisk project for the pjproject third party library. A patch is available. Asterisk Project Security Advisory - AST-2017-003

Bug#863901: AST-2017-002: Buffer Overrun in PJSIP transaction layer

Package: src:pjproject Version: 2.5.5~dfsg-5 Severity: critical Tags: security patch The following security advisory has been announced by the Asterisk project for the third party pjproject library. A patch is available. Asterisk Project Security Advisory - AST-2017-002

Bug#863857: [pkg-ntp-maintainers] Bug#863857: $PIDFILE unset, so writes to a file called /-g

Control: tags -1 + confirmed pending experimental On 01.06.2017 06:07, 積丹尼 Dan Jacobson wrote: > Package: ntp > Version: 1:4.2.8p10+dfsg-3+exp2 > Severity: important > File: /usr/lib/ntp/ntp-systemd-wrapper > > Because $PIDFILE is never set, you end up writing the PIDFILE to a file > called

Bug#863873: sntp tries to write KoD db file to wrong path

Package: src:ntp Version: 1:4.2.8p10+dfsg-3+exp2 Severity: important sntp tries to write a KoD db file to the path /var/db/ntp-kod defined by upstream. This path does not exist (and must not exist on Debian, because it does not match policy). $ sntp ntp1.lrz.de sntp 4.2.8p10@1.3728-o (1)

Bug#854801: Network Manager, Stretch and ipv6

On Fri, May 26, 2017 at 06:58:03PM +0200, Julien Cristau wrote: > +rdisc6 maintainer > > > IMO we should change d-i/netcfg to just never install rdnssd. I guess > > that might negatively impact systems on ipv6-only networks that don't > > have any other means to pick up name servers, but that

Bug#637030: fixed in 4.2.8

Control: fixed -1 1:4.2.8p10+dfsg-1 Fixed somewhere in 4.2.8, at least the current Stretch version is not affected. signature.asc Description: Digital signature

Bug#854475: postfix: systemd needs postfix@.service to have "After=network.target"

Am 10.05.2017 um 17:46 schrieb Scott Kitterman: Hi Scott, >> I think network-online.target is unnecessary, as I'm not aware of any >> common postfix configurations that actually need network access to >> startup. At least the common case of postfix or SQL the connection is > > If you specify an

Bug#635752: [pkg-ntp-maintainers] Bug#635752: ntp: Please include systemd service file

On Mon, May 08, 2017 at 10:11:45PM +0200, Andreas Henriksson wrote: Hi, > I think it's much better to implement this logic natively in the daemon, > so please see attached patch. Please note that it's gotten basically no > testing at all, so review carefully. I really have to admit that

Bug#854475: postfix: systemd needs postfix@.service to have "After=network.target"

Am 08.05.2017 um 20:54 schrieb Scott Kitterman: Hi Scott, > In the postinst, if the debconf configuration is something other than none or > local, we create an override file with After=network-online.target, which is > what I think is needed in most of these cases. I did not add it to the >

Bug#854475: postfix: systemd needs postfix@.service to have "After=network.target"

Hi Andreas, Am 08.05.2017 um 19:15 schrieb Andreas Henriksson: > Hello Scott, Bernhard, > > On Sun, May 07, 2017 at 11:59:10PM -0400, Scott Kitterman wrote: >> On Sunday, May 07, 2017 10:55:58 PM Bernhard Schmidt wrote: >>> [...] >> postfix.service has Af

Bug#854475: postfix: systemd needs postfix@.service to have "After=network.target"

Am 08.05.2017 um 16:18 schrieb Michael Biebl: Hi, > I'm missing context here. Can you go into more detail please? What exactly is > the question here? Sorry. https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=854475 is about several issues with postfix being started before the network is up,

Bug#854475: postfix: systemd needs postfix@.service to have "After=network.target"

Am 08.05.2017 um 05:59 schrieb Scott Kitterman: > On Sunday, May 07, 2017 10:55:58 PM Bernhard Schmidt wrote: >> On Sat, Apr 15, 2017 at 11:42:37PM +0200, Marcus Jodorf wrote: >> >> Hi, >> >> is there anything I can do to get this fixed for Stretch? I can >&g

Bug#862026: unblock: ntp/1:4.2.8p10+dfsg-2 (pre-approval)

Control: tags -1 - moreinfo Hi, > Bernhard Schmidt: >> Package: release.debian.org >> Severity: normal >> User: release.debian@packages.debian.org >> Usertags: unblock >> >> Hi, >> >> I'd like to ask for a pre-approval to upload th

Bug#847440: pending

On Thu, Dec 15, 2016 at 11:18:47AM +, Thomas Hood wrote: Hi Thomas, > package resolvconf > tags 847440 pending > stop You set this to Pending almost five months ago, do you still plan to apply this for Stretch? Bernhard signature.asc Description: Digital signature

Bug#854475: postfix: systemd needs postfix@.service to have "After=network.target"

On Sat, Apr 15, 2017 at 11:42:37PM +0200, Marcus Jodorf wrote: Hi, is there anything I can do to get this fixed for Stretch? I can pretty reliably reproduce this issue with all my upgraded Stretch systems, neither of them can send mails after a reboot until Postfix is getting restarted An

Bug#862026: unblock: ntp/1:4.2.8p10+dfsg-2 (pre-approval)

* Support pool statement in ntpdate-debian (Closes: #854432, #823120) + * Point Vcs-* to pkg-ntp git repository + * Add Bernhard Schmidt to Uploaders + + -- Bernhard Schmidt <be...@debian.org> Sun, 07 May 2017 14:49:22 +0200 + ntp (1:4.2.8p10+dfsg-1) unstable; urgency=high * New upstream

Bug#823120: [pkg-ntp-maintainers] Bug#823120: Bug#823120: not fixed in the released version

On 04.05.2017 22:47, Kurt Roeckx wrote: Hi Kurt, >>> I was checking 1:4.2.8p10+dfsg-1 that should have fixed this. >> >> No, 1:4.2.8p10+dfsg-1+exp1 (in experimental) should have fixed this, it >> has not landed in sid yet (due to being in deep freeze etc) >>> >>> But still: >>> # apt-get install

Bug#823120: [pkg-ntp-maintainers] Bug#823120: not fixed in the released version

On Wed, May 03, 2017 at 09:51:27AM +0200, Christian Ehrhardt wrote: Hi, > I was checking 1:4.2.8p10+dfsg-1 that should have fixed this. No, 1:4.2.8p10+dfsg-1+exp1 (in experimental) should have fixed this, it has not landed in sid yet (due to being in deep freeze etc) > > But still: > # apt-get

Bug#859475: jessie-pu: package ndisc6/1.0.1-1+deb8u1

On Fri, Apr 28, 2017 at 05:45:17PM +0100, Adam D. Barratt wrote: Hi Adam, > On Tue, 2017-04-04 at 00:40 +0200, Bernhard Schmidt wrote: > > the package rdnssd (from src:ndisc6) provides a daemon that listens to IPv6 > > RA > > messages containing RDNSS (recursive DNS

Bug#861236: portaudio19 should build-depend on pkg-config

On 26.04.2017 13:37, Andrew Shadura wrote: Hi Andrew, > Source: portaudio19 > Version: 19+svn20140130-1 > Severity: important > Control: found -1 19.6.0-1 > > Dear Maintainer, > > Since portaudio19 package uses autoreconf, it should build-depend on > pkg-config package. Without that

Bug#860794: Please update DNSSEC trusted keys before ICANN key rollover event

Package: src:bind9 Severity: important Tags: patch upstream Hi, ICANN will roll the DNSSEC root zone KSK in October 2017. DNSSEC-enabled resolvers will then stop working unless they have the new key configured to be trusted (note that in the default configuration a running BIND will learn and

Bug#859911: RTP uses wrong source address

Package: asterisk Version: 1:13.14.0~dfsg-1 Severity: important On systems with several IP addresses (i.e. clusters or multihomed servers) the RTP media stream often uses another source IP address than the transport used. This should be fixable with the following upstream commits in 13.15.0

Bug#859910: AST-2017-001: Buffer overflow in CDR's set user

Package: src:asterisk Version: 1:13.0.0~dfsg-1 Severity: important Tags: security patch upstream See http://downloads.asterisk.org/pub/security/AST-2017-001.html Asterisk Project Security Advisory - AST-2017-001 ProductAsterisk

Bug#859475: jessie-pu: package ndisc6/1.0.1-1+deb8u1

isc6-1.0.1/debian/changelog ndisc6-1.0.1/debian/changelog --- ndisc6-1.0.1/debian/changelog +++ ndisc6-1.0.1/debian/changelog @@ -1,3 +1,10 @@ +ndisc6 (1.0.1-1+deb8u1) jessie; urgency=medium + + * Use upstream default merge hook when resolvconf is not available +(Closes: #767071) + + -- Bernha

Bug#787404: [pkg-ntp-maintainers] Bug#787404: ntp_intres.request: permission denied

On Mon, Apr 03, 2017 at 11:15:35PM +0200, Kurt Roeckx wrote: HI, > > I tried to reproduce this with current Jessie and the future Stretch > > release. As far as I can tell ntp handles this situation just fine. > > > > When ntpd starts up and cannot resolve the servers it logs > > > >

Bug#787404: ntp_intres.request: permission denied

Control: tags -1 + moreinfo unreproducible On Mon, Jun 01, 2015 at 09:16:05AM +0100, Klaus Ethgen wrote: > This is a successor of bug #571469. All is said there. NTP needs running > DNS when it starts. Please add $named to Required-Start in init script. > > Funny thing, reportbug does include

Bug#851096: update-leap tries to fetch https:// using a module without HTTPS support

Control: tag -1 + confirmed On Wed, Jan 11, 2017 at 06:23:58PM -0500, Anthony DeRobertis wrote: > Package: ntp > Version: 1:4.2.8p9+dfsg-2 > Severity: normal > File: /usr/bin/update-leap > > It seems update-leap is just broken, with the default options, because > it attempts to use File::Fetch

Bug#846224: ntp needs ruby for it's unit tests when building

On Tue, Nov 29, 2016 at 06:01:50AM -0500, Charles (Chas) Williams wrote: Hi, > Package: ntp > Version: 1:4.2.8p9+dfsg-2 > > ruby is used by ntp when running unit tests during its build > process. ruby should be listed as a build dependency in > debian/control Hrm, the unit test (make check)

Bug#763522: [Pkg-mutt-maintainers] Bug#763522: Bug#836254: Bug#836254: mutt: crashes when selecting private pgp key

On Wed, Mar 15, 2017 at 10:48:17PM +, Antonio Radici wrote: Hi Antonio, > the patch looks fine to me. if the bug is bumped to grave (and there are > reasons > to do so); I have done point updates in the past and it is straightforward, if > you have already opened the bug / done the upload

Bug#763522: Bug#836254: [Pkg-mutt-maintainers] Bug#836254: mutt: crashes when selecting private pgp key

eam I'm willing to do this on your behalf. Bernhard From bc6025525e37ffa82aad19840df3b915324506a6 Mon Sep 17 00:00:00 2001 From: Bernhard Schmidt <be...@debian.org> Date: Wed, 15 Mar 2017 21:29:53 +0100 Subject: [PATCH] Fix SIGSEGV selecting a GPG key Import patch from http://dev.mutt.org/hg/mutt/rev/5a86319adad0 asa u

Bug#855214: unblock: asterisk/1:13.14.0~dfsg-1 (pre-approval)

Control: tag -1 - moreinfo On Sun, Feb 26, 2017 at 05:14:45PM +, Jonathan Wiltshire wrote: Hi, > Control: tag -1 confirmed moreinfo > > On Wed, Feb 15, 2017 at 04:22:43PM +0100, Bernhard Schmidt wrote: > > I would like to request permission to update Asterisk in S

Bug#855342: RFH: ntp

On 23.02.2017 19:06, Kurt Roeckx wrote: > On Thu, Feb 23, 2017 at 01:33:09PM +0100, Bernhard Schmidt wrote: >> >> Will check what could be causing this. > > That has been fixed in an NMU, see #851803 Ah right, silly me. I've imported the NMU and added the missing tag

Bug#855342: RFH: ntp

On 21.02.2017 21:03, Kurt Roeckx wrote: Hi, > On Tue, Feb 21, 2017 at 02:10:09PM -0500, Peter Eisentraut wrote: >> On 2/19/17 07:01, Kurt Roeckx wrote: > I could really use some help with the ntp (network time protocol) > package. There have been various bugs filed, and I didn't have

Bug#853792: res_rtp_asterisk.c: Unable to allocate RTP socket: Address family not supported by protocol

Control: block 853792 by 855214 On Sun, Feb 19, 2017 at 07:42:54PM +1300, Grzegorz Ojrzanowski wrote: Hi, > On Tue, 14 Feb 2017 23:13:17 +0100 Bernhard Schmidt <be...@debian.org> > wrote: > > Could you please try 13.14.0 from experimental? You might need to enable

Bug#855598: src:ifupdown2: allow-hotplug behaves differently, not UPing interfaces

Package: src:ifupdown2 Version: 1.0~git20170114-1 Severity: important Dear Maintainer, it seems that ifupdown2 allow-hotplug keyword works significantly different from ifupdown allow-hotplug. In ifupdown, when a new network device appears, a udev trigger fires where ifquery checks whether there

Bug#855342: RFH: ntp

On Thu, Feb 16, 2017 at 11:48:49PM +0100, Kurt Roeckx wrote: Hi Kurt, > I could really use some help with the ntp (network time protocol) > package. There have been various bugs filed, and I didn't have the > time to properly look at them and deal with them. > > It's currently team maintained,

Bug#740998: Bug#854801: No network after netinst Stretch RC2

On 14.02.2017 00:43, Pierre Ynard wrote: Hi, >> in finish-install /e/n/i will never be properly populated for a wireless >> installation without network-manager, although I think ifupdown would be >> capable to do this (not tested, but have a look at >>

Bug#855214: unblock: asterisk/1:13.14.0~dfsg-1 (pre-approval)

Package: release.debian.org Severity: normal User: release.debian@packages.debian.org Usertags: unblock Hi, I would like to request permission to update Asterisk in Stretch to a new upstream release (13.13.2 to 13.14.0). This version has mostly bugfixes but only very minor new features.

Bug#853792: res_rtp_asterisk.c: Unable to allocate RTP socket: Address family not supported by protocol

On Wed, Feb 01, 2017 at 11:35:22AM +1300, Grzegorz Ojrzanowski wrote: > A bug was introduced in Asterisk 13.13.0 which was reported in > https://issues.asterisk.org/jira/browse/ASTERISK-26617 > and the fix will be included in next (13.13.2) asterisk release. Could you please try 13.14.0 from

Bug#740998: Bug#854801: No network after netinst Stretch RC2

Hi On 13.02.2017 18:24, Paul Schlüter wrote: > Am Montag, den 13.02.2017, 10:31 +0100 schrieb Bernhard Schmidt: >> @Paul: Can you share the installer log (/var/log/installer/syslog) and >> the content of your /etc/network/interfaces after installation? I'll try >> to get th

Bug#740998: Bug#854801: No network after netinst Stretch RC2

Hi, > > I've cc'd quite a number of folks/lists to make sure the netcfg part is > tackled sooner than later (plus a few others for information). > > Paul Schlüter (2017-02-10): >> * Packages network-manager-gnome (recommended by task-xfce-desktop) and >> net-tools were not

Bug#855014: src:asterisk: Asymetric RTP codec leads to one-way audio

Package: src:asterisk Version: 1:13.13.1~dfsg-4 Severity: important Tags: patch upstream Forwarded: https://issues.asterisk.org/jira/browse/ASTERISK-26603 Normal SIP behaviour is to use one RTP codec in both directions of a call. PJSIP has recently gained support for this, but it is incomplete

Bug#853927: debian-installer: Hang in os-prober in "dmsetup create -r osprober-linux-sda1"

Hi, >> The ~10 minute wait was not a timeout, I simply killed the process then. > > Yes, sure, I had assumed that. > >> I'm using RC2 netboot via PXE. > > Thanks for the confirmation we're still having a big issue here (which I > still have to reproduce)… FYI, we are using this preseed

Bug#853927: debian-installer: Hang in os-prober in "dmsetup create -r osprober-linux-sda1"

Am 10.02.2017 um 08:11 schrieb Cyril Brulebois: Hi Cyril, > Bernhard Schmidt <be...@debian.org> (2017-02-07): >> On Sat, Feb 04, 2017 at 02:32:40AM +0100, Cyril Brulebois wrote: >> I'm having the same problem with Stretch *RC2* and without Crypto >> >> ~

Bug#854680: Upstream bug + Patch

Control: forwarded -1 https://tickets.puppetlabs.com/browse/PUP-7129 Control: tags -1 patch

Bug#854680: service resource cannot be disabled, spews error messages

Source: puppet Version: 4.8.2-1 Severity: important Hi, please note that this is not a duplicate of #854487 (although related because my manifest tried to disable the puppet service). Puppet on Stretch spews an error message about a wrong invocation of dpkg --compare-version on stderr when

Bug#853927: debian-installer: Hang in os-prober in "dmsetup create -r osprober-linux-sda1"

On Sat, Feb 04, 2017 at 02:32:40AM +0100, Cyril Brulebois wrote: Hi, I'm having the same problem with Stretch *RC2* and without Crypto ~ # blkid /dev/mapper/sysvg-root:UUID="62e90454-25b4-4803-b9c3-8ea1337b919a" TYPE="ext4" /dev/sda1:

Bug#854415: unblock: ndisc6/1.0.3-3

-01 20:33:46.0 +0100 +++ ndisc6-1.0.3/debian/changelog 2017-02-01 11:00:55.0 +0100 @@ -1,3 +1,9 @@ +ndisc6 (1.0.3-3) unstable; urgency=medium + + * Import upstream fix to simplify rdnssd-merge-hook (Closes: #853281) + + -- Bernhard Schmidt <be...@debian.org> Wed, 01 Fe

Bug#851513: Build failing

On Tue, Jan 31, 2017 at 10:40:09PM +0100, Arnoud Dekker wrote: > I can confirm that packages built manually from > https://anonscm.debian.org/gitweb/?p=pkg-zfsonlinux/zfs.git and > https://anonscm.debian.org/gitweb/?p=pkg-zfsonlinux/spl.git , which include > fixes for this bug (thanks Aron!),

Bug#853267: Copies empty resolv.conf into chroot if resolvconf is in use

Source: postfix Version: 3.1.4-3 Severity: important Hi, my fairly standard Debian stretch installation that uses resolvconf with dns-* configuration lines in /etc/network/interfaces reproducibly does start a postfix instance at boot unable to deliver any mail to an external destination. Jan 30

Bug#846758: Supporting H.323 Stack in Stretch?

On Thu, Jan 19, 2017 at 12:33:44PM +0100, Joerg Dorchain wrote: Hi Joerg, > > > I don't see any new development in > > > http://t38modem.cvs.sourceforge.net/viewvc/t38modem/t38modem/ . So > > > unless someone steps up to fix #846758 I'm afraid we'll have to RM it > > > eventually. > > > >

Bug#851738: src:asterisk: SNMP support disabled

Package: src:asterisk Version: 1:13.13.1~dfsg-3 Severity: important Hi, Due to the messed up execution/timing of the OpenSSL 1.1.0 transition we had to disable SNMP support in Asterisk for now.

Bug#849804: /etc/init.d/asterisk debug unusable for continous output

On Sat, Jan 14, 2017 at 12:55:08PM +0100, Joerg Dorchain wrote: Hi Joerg, > > > I would like config parts containing personal access details > > > not to be part of the public bug tracker for avoiding security > > > breaches and direct monetary costs arrising from that, so I did > > > not sent

Bug#828082: bind9: FTBFS with openssl 1.1

Hi, > Your package is failing to build with openss 1.1: > checking for OpenSSL library... no > yes > checking for using OpenSSL for hash functions... no > [...] > checking for OpenSSL library... using OpenSSL from /usr/lib and /usr/include > checking whether linking with OpenSSL works... yes >

Bug#849804: /etc/init.d/asterisk debug unusable for continous output

On Sat, Dec 31, 2016 at 09:30:35AM +0100, Joerg Dorchain wrote: Hi Joerg, > following testing, after upgrading to asterisk 1:13.13.1~dfsg-2, > /etc/init.d/asterisk debug endlessly repeats the following screen > output rapidly: > ... > 09:22:39.015 rtp0x558b74e70 Mutex: thread timer is waiting

Bug#851240: open-vm-tools: Duplicate udev rule

Package: open-vm-tools Version: 2:10.1.0-4449150-1 Severity: minor Dear maintainer, starting with upstream version 10.1.0-4449150 (at least this is the upstream version in https://github.com/bzed/pkg-open-vm-tools/tree/master/open-vm-tools/udev) open-vm-tools now ship an udev rule setting the

Bug#789651: tacacs+: Incomplete systemd integration

On Tue, Jun 23, 2015 at 11:20:26AM +0800, laalaa wrote: Hi, > Package: tacacs+ > Version: 4.0.4.27a-1 > Severity: normal > > > Description: > > tacacs+ is missing 'is-enabled' systemd integration: > > # systemctl is-active tacacs_plus.service > active > > # systemctl enable

Bug#850084: jessie-pu: package asterisk/1:11.13.1~dfsg-2+deb8u2

On 05.01.2017 20:53, Adam D. Barratt wrote: > Control: tags -1 + confirmed > > On Wed, 2017-01-04 at 00:05 +0100, Bernhard Schmidt wrote: >> I would like to fix CVE-2016-9938 (Bug #847668) with the upcoming point >> release. >> The issue has been categorized no-dsa

Bug#850084: jessie-pu: package asterisk/1:11.13.1~dfsg-2+deb8u2

(1:11.13.1~dfsg-2+deb8u2) jessie; urgency=medium + + * AST-2016-009: non-printable ASCII chars treated as whitespace (CVE-2016-9938) +(Closes: #847668) + + -- Bernhard Schmidt <be...@debian.org> Tue, 03 Jan 2017 23:54:39 +0100 + asterisk (1:11.13.1~dfsg-2+deb8u1) jessie-security; u

Bug#849804: /etc/init.d/asterisk debug unusable for continous output

Control: forwarded -1 https://issues.asterisk.org/jira/browse/ASTERISK-26630 On Sun, Jan 01, 2017 at 12:09:58PM +0100, Joerg Dorchain wrote: Hi, > Downgrading these to 2.5.5~dfsg-3 from snapshot.debian.org indeed > helped the problem. So far, so easy. > > To keep me happy, I see some options.

Bug#571971: rdnssd: hook relies to non existant interface name

Control: tags -1 - moreinfo Control: tags -1 + upstream wontfix On Thu, Mar 04, 2010 at 05:37:51PM +0200, Rémi Denis-Courmont wrote: > tags 571971 + moreinfo > thanks > > Le dimanche 28 février 2010 19:13:33, vous avez écrit : > > Debian usualy uses resolvconf to add nameserver entries to

Bug#849804: /etc/init.d/asterisk debug unusable for continous output

On Sun, Jan 01, 2017 at 11:06:30AM +0100, Tzafrir Cohen wrote: Hi, > The messages comes from pjproject. The messages are relatively low > priority ones there. > > However just from reading the code I'm a bit lost. That message seems to > be at log priorty 6 in pjproject: >

Bug#793798: app_voicemail hangs up due to missing audio file

Control: reassign -1 asterisk-core-sounds Control: affects -1 asterisk Control: severity -1 important On Mon, Jul 27, 2015 at 10:14:56AM -0600, TheSin wrote: > Package: asterisk-voicemail > Version: 1:13.1.0~dfsg-1.1 > > Forwarding a voicemail cause the app to hangup due to missing sound file. >

Bug#684646: fails to receive BYE over TLS

Control: tags -1 +moreinfo On Sun, Aug 12, 2012 at 12:44:18PM +, Daniel Pocock wrote: > I am using v1.8.8. I've also tried to use 1.8.13 (the version in > wheezy) to see if that resolves the problem, but 1.8.13 has more severe > problems that prevent testing of the same TLS environment: >

Bug#847635: AST-2016-009: SIP header whitespace with proxy

Control: forcemerge 847668 -1 On Fri, Dec 09, 2016 at 11:30:27PM -0500, Dara Adib wrote: Hello Dara, > Package: asterisk > Version: 1:11.13.1~dfsg-2+deb8u1 > Severity: important > Tags: security patch > > https://security-tracker.debian.org/tracker/TEMP-000-5567B0 >

Bug#846583: cloud.debian.org: AWS Image should enable DHCPv6 client

On Thu, Dec 08, 2016 at 10:23:22PM -0800, Noah Meyerhans wrote: Hi Noah, > On Fri, Dec 02, 2016 at 12:25:44PM +0100, Bernhard Schmidt wrote: > > thanks for providing an AWS EC2 Image with Debian Jessie. > > > > AWS is now supporting IPv6 on EC2 instances, see &g

Bug#847316: RM: libzrtpcpp -- ROM; obsolete; RC-buggy

Package: ftp.debian.org Severity: normal Hi, please remove libzrtpcpp from sid. It has been RC-buggy for more than a year. The only former rdep has been RMed a while ago already. The upstream website has been abandoned and domain-squatted. I have asked within the team and all maintainers. The

Bug#828546: Building with OpenSSL 1.0.2 is sufficient for stretch

Control: severity -1 important On Sat, Nov 12, 2016 at 01:53:07PM +0200, Adrian Bunk wrote: Hi, > Not a perfect solution but sufficient for stretch is the patch below to > use OpenSSL 1.0.2 Thanks, I have just uploaded 3.3.0~test17-2.1 with that fix. Downgrading the bug for now. Bernhard

Bug#847014: python-pjproject: undefined symbol: pjmedia_endpt_create

Control: severity -1 important On Sun, Dec 04, 2016 at 11:03:26PM +0100, Roland Koebler wrote: Hi Roland, > Package: python-pjproject > Version: 2.5.5~dfsg-3 > Severity: grave > Justification: renders package unusable > > Dear Maintainer, > > python-pjproject is broken; when trying to use it,

Bug#846583: cloud.debian.org: AWS Image should enable DHCPv6 client

Package: cloud.debian.org Severity: minor User: cloud.debian@packages.debian.org Usertags: aws Hi, thanks for providing an AWS EC2 Image with Debian Jessie. AWS is now supporting IPv6 on EC2 instances, see

Bug#844869: isatapd: FTBFS: ip.h:85:8: error: redefinition of 'struct iphdr'

Hi Adrian, On Mon, Nov 21, 2016 at 04:58:34PM +0200, Adrian Bunk wrote: > On Sun, Nov 20, 2016 at 08:54:06PM +0100, Bernhard Schmidt wrote: > >... > > On Sat, Nov 19, 2016 at 07:43:42AM +0100, Lucas Nussbaum wrote: > >... > > > Relevant part (hopefully): >

Bug#844869: isatapd: FTBFS: ip.h:85:8: error: redefinition of 'struct iphdr'

Control: tags -1 confirmed On Sat, Nov 19, 2016 at 07:43:42AM +0100, Lucas Nussbaum wrote: Hi, > Source: isatapd > Version: 0.9.7-2 > Severity: serious > Tags: stretch sid > User: debian...@lists.debian.org > Usertags: qa-ftbfs-20161118 qa-ftbfs > Justification: FTBFS on amd64 > > Hi, > >

Bug#845144: asterisk console scrambles (or misinterprets) input

On Sun, Nov 20, 2016 at 09:20:29PM +0200, Tzafrir Cohen wrote: Hi, > This behaves even worse than I remembered it. > > It seems that there is a random unicode character (different at any > invocation) or-ed with the characters printed. I connected several times > and types 'abc', and got: > >

Bug#843654: Use Debian pjproject and libsrtp

On Sat, Nov 12, 2016 at 10:51:32PM +0100, Andrey Gursky wrote: > > For the record, pjproject is currently used by a single other package: > > asterisk. Upstream of asterisk recommends applying a set of their own > > patches: > > > >

Bug#842878: Asterisk crashes with pjproject 2.5.5

On Wed, Nov 09, 2016 at 08:47:42PM -0500, Gedalya wrote: Hi, > OK, confirmed. > The patch (r5401) works, we're back with the previous behavior: > > [Nov 9 20:43:33] ERROR[14871]: res_pjsip.c:2883 ast_sip_create_dialog_uac: > Could not create dialog to endpoint '' as URI '' is not

Bug#816042: Don't include in stretch

On Fri, Feb 26, 2016 at 10:31:43PM +0100, Moritz Muehlenhoff wrote: Hi Moritz, > Source: asterisk > Severity: serious > > asterisk hasn't seen a maintainer upload to unstable in 2015. It's > already excluded from testing due to an unrelated FTBFS bug. This > bug is used to ensure that it

Bug#842878: Asterisk crashes with pjproject 2.5.5

On Fri, Nov 04, 2016 at 11:02:03AM +0100, Bernhard Schmidt wrote: Hi, > > I decided to try this: I made a sid chroot, manually downgraded to > > libssl-dev 1.0.2j-1 from stretch, and built asterisk from the > > current packaging git head (ec0143a). I actually enabled

Bug#828240: asterisk: FTBFS with openssl 1.1.0

On Sun, Nov 06, 2016 at 04:39:03PM +0400, Stepan Golosunov wrote: Hi, > 06.11.2016 в 16:18:32 +0400 Stepan Golosunov написал: > > 03.11.2016 в 09:24:19 +0100 Bernhard Schmidt написал(а): > > > - Asterisk is doing some weird stuff with macros in > > > > >

Bug#842878: Asterisk crashes with pjproject 2.5.5

Control: forwarded -1 http://lists.pjsip.org/pipermail/pjsip_lists.pjsip.org/2016-November/019636.html On Thu, Nov 03, 2016 at 03:12:37PM -0400, Gedalya wrote: Hi, > > Confirmed. If you start Asterisk in the foreground you actually get an > > assertion > > > > asterisk:

Bug#842878: Asterisk crashes with pjproject 2.5.5

Control: tags -1 confirmed > > == Begin MixMonitor Recording PJSIP/trunk-vitelity-in- > > asterisk*CLI> > > Disconnected from Asterisk server > > Asterisk cleanly ending (0). > > Executing last minute cleanups > > > > That's all. Nothing in the log either. > > > > After going back to

Bug#828240: asterisk: FTBFS with openssl 1.1.0

Control: tags -1 help Hi, current state on this: - There is no progress visible in the upstream bugtracker, I have also not found anything in other distros (Fedora etc.) - switching to libssl1.0-dev does not work for now because the build-deps libc-client2007e-dev

Bug#828505: pjproject: FTBFS with openssl 1.1.0

Control: severity -1 important 2.5.5~dfsg-2 in unstable now builds against libssl1.0-dev. Unless upstream releases a fixed version in time for stretch we will keep it that way. Downgrading severity in accordance with the release team. signature.asc Description: Digital signature

Bug#842878: Asterisk crashes with pjproject 2.5.5

Control: reassign -1 src:pjproject 2.5.5~dfsg-1 Control: severity -1 grave Control: affects -1 src:asterisk On Tue, Nov 01, 2016 at 08:17:16PM -0400, Gedalya wrote: Hi, > Package: asterisk > Version: 1:13.11.2~dfsg-1 > > Hi, > > Not sure if this should be filed against asterisk or pjproject.

Bug#841910: uscan behaviour on multiple signatures

On Wed, Oct 26, 2016 at 06:08:28PM -0400, James McCoy wrote: Hi, > > IMHO this behaviour does not make any sense. You need to check the > > authenticity of any additional key upstream might use before adding it > > to the repo, > > Of course you do. Why wouldn't you verify the authenticity of

Bug#835166: libmyodbc: SIGFPE, Arithmetic exception in sqlchar_as_sqlwchar

Control: severity -1 grave Control: tags -1 sid stretch On Tue, Aug 23, 2016 at 10:30:05AM +0200, Michal Čihař wrote: Hi, > maybe I'm just doing something wrong (actually trying to use ODBC after > very long time), but I get SIGFPE when trying to use libmyodbc. > > Setup: > > - - the driver

Bug#828505: pjproject: FTBFS with openssl 1.1.0

Control: forwarded -1 https://trac.pjsip.org/repos/ticket/1932 Control: tags -1 help On Sun, Jun 26, 2016 at 12:23:43PM +0200, Kurt Roeckx wrote: Hi, > Source: pjproject > Version: 2.4.5~dfsg-4 > Severity: important > Control: block 827061 by -1 > > Hi, > > OpenSSL 1.1.0 is about to released.

Bug#841910: uscan behaviour on multiple signatures

Am 25.10.2016 um 16:07 schrieb Osamu Aoki: Hi Osamu, > This is very interesting report. I did not implement this feature so it > is a learning experience for me. Please be patient. > >> When there is one signature of a key not listed in >> debian/upstream/signing-key.asc a validation warning

Bug#841910: uscan behaviour on multiple signatures

Package: devscripts Version: 2.16.8 Severity: normal File: /usr/bin/uscan Hi, Asterisk upstream sources are signed by several keys, see for example http://downloads.asterisk.org/pub/telephony/asterisk/releases/asterisk-13.11.2.tar.gz

<    1   2   3   4   5   6   7   8   9   10   >