Bug#848287: python-testing.mysqld: (build-)depends on mysql-{client,server}

On 01/01/17 12:49, Dominik George wrote: > Hi, > >> You should have kept me in Cc if you wanted me to see your reply and have a >> chance to reply. > > sorry, I just cannot remember that the Debian BTS does not automatically > notify the submitter ☹. > > So, I have several problems: > > * I

Bug#837167: RFS: aiscm/0.6.2-2

You have override_dh_makeshlibs: # NOOP to prevent debuild from invoking ldconfig Debuild doesn't invoke ldconfig. If it's done to avoid adding an ldconfig trigger you should explain that and explain why it is added because it's not clear why do you need manual actions here. -- WBR, wRAR

Bug#704303: violates Debian Policy 2.3 Copyright considerations

Note that since Policy 3.9.9 MPL should be in common-licenses. -- WBR, wRAR signature.asc Description: PGP signature

Bug#848287: python-testing.mysqld: (build-)depends on mysql-{client,server}

Hi, > You should have kept me in Cc if you wanted me to see your reply and have a > chance to reply. sorry, I just cannot remember that the Debian BTS does not automatically notify the submitter ☹. So, I have several problems: * I cannot find the formal transition for this. * I cannot see

Bug#847015: RFS: debdelta/0.55+nmu1 [RC] [NMU]

Hi Tobi, It's strange, but the BTS didn't forward me your message. I believe Andrea was X-Debbugs-CCed in my original RFS message. I'll keep the things you've pointed out in mind in the future. Anyway, I think Andrea has become active in the RC bug, so it has made this RFS unnecessary. Should

Bug#849584: Please review proposed service file change

Hi Scott, On Fri, 30 Dec 2016, Scott Kitterman wrote: > Since you provided the original postfix service file, would you please review > the proposed change in the cc'ed bug: > > https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=849584 > > and let us know what you think about the change. It

Bug#845034: initramfs-tools: please ensure initrd images are reproducible

Hi Ben, > initramfs-tools: please ensure initrd images are reproducible Thanks for the review; updated patch attached. > Control: block -1 with 804063 [..] > I'd much prefer to add a versioned dependency on the new cpio (when > available) than to probe for it ar run-time The new cpio is now

Bug#737167: xfonts-wqy: prompting due to modified conffiles which were not modified by the user

Control: fixed -1 1.0.0~rc1-1 On Sun, Jan 01, 2017 at 01:14:24AM -0800, Paul Hardy wrote: > Did that upload fix this bug, and the bug just wasn't marked as closed? Just do the test and it is okay in version 1.0.0~rc1-1. Thanks for the reminder. -- ChangZhuo Chen (陳昌倬)

Bug#804063: cpio: New upstream release 2.12 available

tags 804063 + pending thanks Chris Lamb wrote: > Just having issues compiling the mingw part Fixed! Uploading now… Regards, -- ,''`. : :' : Chris Lamb `. `'` la...@debian.org / chris-lamb.co.uk `-

Bug#849417: [Pkg-nagios-devel] Bug#849417: nagios-nrpe-server: segfault during SSL negotiation with older NRPE 2.15 plugin

tags 849417 - unreproducible moreinfo tags 849417 + upstream forwarded 849417 https://github.com/NagiosEnterprises/nrpe/issues/91 thanks Hi Adam, Thanks for the additional debugging. I've now been able to reproduce the issue on a Debian unstable VM, and have forwarded the issue upstream. On

Bug#849849: rabbitmq-server: CVE-2016-9877

Source: rabbitmq-server Version: 3.6.5-1 Severity: grave Tags: upstream security Justification: user security hole Hi, the following vulnerability was published for rabbitmq-server. CVE-2016-9877[0]: | An issue was discovered in Pivotal RabbitMQ 3.x before 3.5.8 and 3.6.x | before 3.6.6 and

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

On Sun, Jan 01, 2017 at 11:22:25AM +0100, Bernhard Schmidt 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#828607: closing 828607

wf...@niif.hu (Ferenc Wágner) writes: > Niels Thykier writes: > >> Ferenc Wágner: >> >>> Thanks for re-closing this bug. Could you please help me understand why >>> xml-security-c 1.7.3-4 hasn't migrated to testing yet, even though >>>

Bug#849848: blhc: Architecture independent packages shouldn't log compiler commands

Package: blhc Severity: normal Dear Maintainer, https://qa.debian.org/bls/bytag/I-no-compiler-commands.html says: Possible issues this might hint at: * A package being Architecture: all, though it only contains architecture independent data. which I don't get. The very point of

Bug#849843: libyaml-libyaml-perl: [PATCH] lazy load B::Deparse for big speedup

Hello Eric, Thanks for your patch. I have forwarded it upstream at https://github.com/ingydotnet/yaml-libyaml-pm/issues/52 Regards, Salvatore

Bug#848559: zeroinstall-injector: Don't recommend python3-aptdaemon.pkcompat

On 18 December 2016 at 11:52, Jeremy Bicha wrote: > Package: zeroinstall-injector > Version: 2.12-2 > Severity: important > > Please don't recommend python3-aptdaemon.pkcompat. aptdaemon has been > removed from Debian and we don't want an obsolete recommends to keep > it

Bug#805857: Does not do a SRV lookup, tries A/AAAA record instead

[ Just another sendxmpp user ] martin f krafft wrote... > If a SRV record is present, this should lead the way to the server > for an address, not the A/ records of the domain. Ouch, in my opinion this justifies a higher priority. After digging in the sources of libnet-xmpp-perl (where

Bug#849838: firefox: Fix broken hppa build support

Hi Dave! On 01/01/2017 02:33 AM, John David Anglin wrote: > The attached patch fixes the compile issues and includes the comment that I > had. My icedove > build still isn't complete yet but it's well past the point where the compile > breakage occurred. I don't think it makes much sense to

Bug#840132: xrdp-sesman.service sometimes fails to start on boot

Hi, > One thing possibly interesting about both systems is that they are both > kvm hosts. After each system reaches network.target, the dependency for > starting xrdp in systemd, quite a bit of subsequent network > configuration takes place: So why is network.target reached, then? This seems

Bug#849847: base: fails to lock screen

Package: base Severity: important Dear Maintainer, The lock screen does not activate when I logout or turn the pc on. I hv also set the screen to lock automatically after 30 seconds, but nothing happens. even pressing Ctrl+Alt+L at desktop is unable to lock the screen. -- System

Bug#849467: jessie-pu: package hplip/3.14.6-1+deb8u1

Le samedi, 31 décembre 2016, 17.10:09 h CET Adam D. Barratt a écrit : > Control: tags -1 + confirmed > > On Tue, 2016-12-27 at 14:18 +0100, Didier 'OdyX' Raboud wrote: > > I'd like to get CVE-2015-0839 fixed in jessie, it's a no-DSA issue, and > > security team members suggested to get it fixed

Bug#600543: ctrl-k in emacs23 crashes xrdp

Control: tags -1 + moreinfo Hi, can you please check with 0.9.1, both with the xorgxrdp and VNC backends? Cheers, Nik -- PGP-Fingerprint: 3C9D 54A4 7575 C026 FB17 FD26 B79A 3C16 A0C4 F296 Dominik George · Hundeshagenstr. 26 · 53225 Bonn Mobile: +49-1520-1981389 ·

Bug#600912: xrdp: Problem with Ctrl+AltGR+KEY combinations on German keyboard

Control: tags -1 + moreinfo Hi, can you please check this with 0.9.1, both with xorgxrdp and VNC as backend? Cheers, Nik -- PGP-Fingerprint: 3C9D 54A4 7575 C026 FB17 FD26 B79A 3C16 A0C4 F296 Dominik George · Hundeshagenstr. 26 · 53225 Bonn Mobile: +49-1520-1981389 ·

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

On Sun, Jan 01, 2017 at 11:06:30AM +0100, Tzafrir Cohen wrote: > On Sat, Dec 31, 2016 at 09:30:35AM +0100, Joerg Dorchain wrote: > > Package: asterisk > > Version: 1:13.13.1~dfsg-2 > > > > Hello, > > > > following testing, after upgrading to asterisk 1:13.13.1~dfsg-2, > > /etc/init.d/asterisk

Bug#716554: [Mayhem] Bug report on xrdp: xrdp-chansrv crashes with exit status 139

Control: tags -1 + moreinfo > re-running it in a fresh debian unstable installation. > > The attachment [1] contains a testcase (under ./crash) crashing the > program. It ensures that you can easily reproduce the bug. Additionally, > under ./crash_info/, we include more information about the

Bug#710089: xrdp: Should handle PAM conversation() callback in sesman

Control: tags -1 + moreinfo Hi Petter, > When using xrdp together with the libpam-mklocaluser, to create a local > user with a local home directory when the user log in for the first > time, xrdp/sesman fail to show the message passed back from the PAM > module using the PAM conversation()

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#849342: [xrdp] xrdp-sesman: Fails to start Xorg

Control: tags -1 + moreinfo Hi Ben, > Dec 25 15:49:14 lear xrdp-sesman[15632]: (15632)(-148605184)[INFO ] Xorg :10 > -auth .Xauthority -config xrdp/xorg.conf -noreset -nolisten tcp Can you please try running this exact command manually as the same user? Cheers, Nik -- PGP-Fingerprint: 3C9D

Bug#849846: logrotate: Add support for systemd timers

Source: logrotate Version: 3.8.7-2 Severity: wishlist Tags: patch Hi, the attached patch backports the systemd timer and service units from upstream version 3.11.0 and adds a check to the cron script to only run on non-systemd systems. -- Package-specific info: Contents of /etc/logrotate.d

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

Hi, On Sat, Dec 31, 2016 at 09:30:35AM +0100, Joerg Dorchain wrote: > Package: asterisk > Version: 1:13.13.1~dfsg-2 > > Hello, > > following testing, after upgrading to asterisk 1:13.13.1~dfsg-2, > /etc/init.d/asterisk debug endlessly repeats the following screen > output rapidly: > ... >

Bug#849845: dirmngr: Can't resolve keyserver hostname anymore

Package: dirmngr Version: 2.1.17-2 Severity: important Hi! since the upgrade to 2.1.17 (not sure if it's in -1 or -2), my dirmngr is unusable. Any network operation triggers: can't connect to 'hkps.pool.sks-keyservers.net': no IP address for host ... almost immediately, i.e. resolver-timeout

Bug#844578: logrotate: Upstream has moved to GitHub

Package: logrotate Version: 3.8.7-2 Followup-For: Bug #844578 Hi, the attached patch updates the watch file to check github for new releases. -- Package-specific info: Contents of /etc/logrotate.d total 20 -rw-r--r-- 1 root root 173 Apr 5 2016 apt -rw-r--r-- 1 root root 79 Mar 5 2016

Bug#849631: dnscrypt-proxy

Hallo Eric after a complete purge of dnscrypt-proxy files and a reinstall of version 1.8.1-4 it appears to be working correctly. I have only needed to alter the : etc/dnscrypt-proxy/dnscrypt-proxy.conf to change to my preferred  DNSCRYPT_PROXY_RESOLVER_NAME= thanks for your help Peter

Bug#568094: Processed: Re: Bug#568094: fwvm-crystal: clock freezes after sleep

On Sun, 27 Jan 2013 12:17:24 +0100 Vincent Bernat wrote: > reassign 568094 fvwm > retitle 568094 fvwm: periodic tasks in a module won't work after sleep > thanks > > Hi! > > The clock is a FVWM script swallowed into a fvwm button. There is no way > that every script should

Bug#737167: xfonts-wqy: prompting due to modified conffiles which were not modified by the user

This RC bug from 2014 reports packaging problems with configuration files. In 2015, ChangZhuo Chen uploaded a new version with suffix "rc1-1" having the changelog entry "Fix wrong configuration file." See the changelog entry excerpted below: --start changelog

Bug#784286: dirmngr keyserver should default to hkps://hkps.pool.sks-keyservers.net

Hi Daniel, that's fixed in 2.1.16, right? The upstream changelog reads: 2016-11-17 Daniel Kahn Gillmor dirmngr: Use a default keyserver if none is explicitly set. Cheers, -- intrigeri

Bug#816249: debian-policy: C.2.4 does not reflect current practises

Russ Allbery: > Niels Thykier writes: > >> The section C.2.4 seems to be a bit outdated. Quote: > >> """ >> [...] >> """ > >> However, the default used by debhelper is "debian/", which covers >> up to 99% of all packages. > > Thanks for pointing this out. The

Bug#845173: Cannot handle new debs with data component XZ compressed in parallel

Il 21/11/2016 04:27, Carlos Maddela ha scritto: > Ever since dpkg 1.18.14 or 1.18.15 was released there haven't been too > many usable debdeltas available for download. The reason being that debs > that have their data component compressed in XZ format are now being > done so in parallel, which

Bug#849844: RFS: manpages-zh/1.6.0-1

Package: sponsorship-requests Severity: normal X-Debbugs-CC: chinese-develop...@lists.alioth.debian.org Dear mentors and chinese-developer folks, I am looking for a sponsor for my package "manpages-zh". * Package name: manpages-zh Version : 1.6.0-1 Upstream Author : Boyuan

Bug#849631: dnscrypt-proxy

Hallo Eric I am seeing the same:dnscrypt-proxy.service: Failed   with result 'start-limit-hit'. after update to Version: 1.8.1-4 I notice the change in the files list from :

Bug#849578: task-xfce-desktop: Why you use the vlc player in the task-xfce-desktop meta package?

Quoting Jürgen Göricke (juergengoeri...@smart-mail.de): > Dear Maintainer, > > see all the dependencies from package vlc in Debian Sid. > > https://packages.debian.org/sid/vlc > > http://paste.debian.net/905778 > > Vlc needs Qt dependencies by default. > > What is the problem with parole to

Bug#849843: libyaml-libyaml-perl: [PATCH] lazy load B::Deparse for big speedup

Package: libyaml-libyaml-perl Version: 0.63-1 Severity: normal Tags: patch upstream This speeds up startup time dramatically and is noticeable with small scripts on my weak hardware where loading B::Deparse takes a significant amount of time. Lazy loading it helps for the common case when I do

Bug#849841: [src:linux] bpfcc-tools don't work on 4.8 signed kernels

On Sun, 2017-01-01 at 09:24 +0800, Liang Guo wrote: > Package: src:linux > Version: linux-image-4.8.0-2-amd64 > Severity: serious > I don't think this severity is justified, when the regular kernels work fine with it. > Hi, I found bpfcc-tools don't work on linux-image-4.8.0-2-amd64 and  >

<    1   2   3