Bug#833035: linux-image-3.16.0-4-amd64: Keyspan USB serial adapter USA-49WLC failed to load firmware

On 07/31/2016 17:31, Ben Hutchings wrote: Control: retitle -1 linux-image-3.16.0-4-amd64: Keyspan USB serial adapter USA-49WLC failed to load firmware Control: tag -1 moreinfo On Sun, 2016-07-31 at 00:16 -0700, Chris Rhodin wrote: Subject: linux-image-3.16.0-4-amd64: Keyspan USB serial

Bug#833238: Do not set CONFIG_FAT_DEFAULT_IOCHARSET="utf8", use FAT_DEFAULT_UTF8 instead

Package: linux-image-4.6.0-1-amd64 Version: 4.6.4-1 Hello, The Debian kernel currently has CONFIG_FAT_DEFAULT_IOCHARSET="utf8" enabled. This is not recommended [1]: | config FAT_DEFAULT_IOCHARSET | string "Default iocharset for FAT" | depends on VFAT_FS | default "iso8859-1" |

Bug#822596: gdebi: depends on gksu which is deprecated (patch attached)

Hi, Attached is a patch proposal for moving gdebi from gksu to polycikit. Let me know if it needs adjustments. Thanks in advance for considering it. Regards, Julien Lavergne diff -Nru gdebi-0.9.5.7/data/com.ubuntu.pkexec.gdebi-gtk.policy

Bug#833237: RFS: node-es6-promise/3.2.2+ds-1 (ITP)

Package: sponsorship-requests Severity: wishlist Dear mentors, I am looking for a sponsor for my package "node-es6-promise" * Package name: node-es6-promise Version : 3.2.2+ds-1 Upstream Author : Yehuda Katz, Tom Dale, Stefan Penner and contributors (Conversion to ES6

Bug#832331: libqpol1: doesn't give adequate information when there are conflicting type rules

reassign 832331 libsepol1 2.5-1 thanks Le 02/08/16 à 03:26, Russell Coker a écrit : On Mon, 1 Aug 2016 11:03:38 PM Laurent Bigonville wrote: Are you sure it's lib*q*pol1 and not libsepol1? Codesearch seems to tell me it's the later:

Bug#833236: shotwell: Please install shotwell-settings-migrator and shotwell-video-thumbnailer in /usr/lib/shotwell

Package: shotwell Version: 0.22.1-1 Severity: normal Hi, In debian, private executables are usually installed in /usr/lib/ instead of /usr/lib or /usr/libexec (which doesn't exist in debian at all). Could you please install shotwell-settings-migrator and shotwell-video-thumbnailer in

Bug#773791: network-manager-strongswan: does not seem to support EAP_IDENTITY

Hello Julian, Please check if libstrongswan-extra-plugins and libcharon-extra-plugins are installed. This fixed the problem for me. Cheers, sebastian signature.asc Description: PGP signature

Bug#833234: openvpn-blacklist: Uses obsolete compressor for .deb data.tar member

Source: openvpn-blacklist Source-Version: 0.5 Severity: important User: debian-d...@lists.debian.org Usertags: dpkg-obsolete-deb-data-tar-compressor Hi! This source package builds one or more binary packages using the deprecated compressor bzip2. The default has been xz for a while now which

Bug#833235: libbitmask: Uses obsolete compressor for .deb data.tar member

Source: libbitmask Source-Version: 2.0-2 Severity: important User: debian-d...@lists.debian.org Usertags: dpkg-obsolete-deb-data-tar-compressor Hi! This source package builds one or more binary packages using the deprecated compressor bzip2. The default has been xz for a while now which should

Bug#833233: yapps2: Uses obsolete Source-Version substvar

Source: yapps2 Source-Version: 2.1.1-17.3 Severity: important User: debian-d...@lists.debian.org Usertags: dpkg-obsolete-source-version-substvar Hi! This source package uses the ${Source-Version} substvar variable deprecated since dpkg 1.13.19 in 2006-05-04. That upload also introduced the

Bug#833232: zfec: Uses obsolete compressor for .deb data.tar member

Source: zfec Source-Version: 1.4.5-2 Severity: important User: debian-d...@lists.debian.org Usertags: dpkg-obsolete-deb-data-tar-compressor Hi! This source package builds one or more binary packages using the deprecated compressor bzip2. The default has been xz for a while now which should

Bug#833231: initramfs-tools: during initramfs: "/init: line 1: logsave: not found" when e2fsprogs is not installed

Source: initramfs-tools Version: 0.125 Severity: normal Control: affects -1 e2fsprogs I have a minimal system with only btrfs filesystems, and e2fsprogs is not needed on it. It would be nice to be able to uninstall it. however, when i uninstall e2fsprogs and reboot into an initramfs built by

Bug#706264: Segmentation fault upon giving location

retitle 706264 location capability completely gone found 706264 0.5.12~wk2-exp1 thanks All I know is now location capability has been completely removed from midori. https://whereamirightnow.com/ cannot figure out where I am, and no permission dialog appears on the screen, nor in Preferences.

Bug#833229: libcpuset: Uses obsolete compressor for .deb data.tar member

Source: libcpuset Source-Version: 1.0-4 Severity: important User: debian-d...@lists.debian.org Usertags: dpkg-obsolete-deb-data-tar-compressor Hi! This source package builds one or more binary packages using the deprecated compressor bzip2. The default has been xz for a while now which should

Bug#833227: pastewebkit: Uses obsolete compressor for .deb data.tar member

Source: pastewebkit Source-Version: 1.0-7 Severity: important User: debian-d...@lists.debian.org Usertags: dpkg-obsolete-deb-data-tar-compressor Hi! This source package builds one or more binary packages using the deprecated compressor bzip2. The default has been xz for a while now which should

Bug#833228: pastescript: Uses obsolete compressor for .deb data.tar member

Source: pastescript Source-Version: 1.7.5-3 Severity: important User: debian-d...@lists.debian.org Usertags: dpkg-obsolete-deb-data-tar-compressor Hi! This source package builds one or more binary packages using the deprecated compressor bzip2. The default has been xz for a while now which

Bug#833230: mpack: Uses obsolete compressor for .deb data.tar member

Source: mpack Source-Version: 1.6-8 Severity: important User: debian-d...@lists.debian.org Usertags: dpkg-obsolete-deb-data-tar-compressor Hi! This source package builds one or more binary packages using the deprecated compressor bzip2. The default has been xz for a while now which should

Bug#833226: bsdmainutils: cal fails to accept formerly supported `-h` option

Package: bsdmainutils Version: 9.0.10 Severity: normal In versions up through Jessie, `cal` supported a `-h` option to turn off highlighting of the current day. In Stretch, `cal -h` results in a help message. Because there are likely many scripts that depend on `-h` to suppress highlighting,

Bug#833222: pinyin-database: Uses obsolete compressor for .deb data.tar member

Source: pinyin-database Source-Version: 1.2.99-3 Severity: important User: debian-d...@lists.debian.org Usertags: dpkg-obsolete-deb-data-tar-compressor Hi! This source package builds one or more binary packages using the deprecated compressor bzip2. The default has been xz for a while now which

Bug#833223: fretsonfire-songs-muldjord: Uses obsolete compressor for .deb data.tar member

Source: fretsonfire-songs-muldjord Source-Version: 2.dfsg-1 Severity: important User: debian-d...@lists.debian.org Usertags: dpkg-obsolete-deb-data-tar-compressor Hi! This source package builds one or more binary packages using the deprecated compressor bzip2. The default has been xz for a while

Bug#833189: redis-server: Update via apt or dpkg hangs

tags 833189 + unreproducible thanks > Needed to use 'killall dpkg' from a separate terminal to > recover Unfortunately, I can't reproduce this: $ wget http://snapshot.debian.org/archive/debian/20160728T163948Z/pool/main/r/redis/redis-server_3.2.1-4_amd64.deb $ wget

Bug#833224: perl-byacc: Uses obsolete compressor for .deb data.tar member

Source: perl-byacc Source-Version: 2.0-8 Severity: important User: debian-d...@lists.debian.org Usertags: dpkg-obsolete-deb-data-tar-compressor Hi! This source package builds one or more binary packages using the deprecated compressor bzip2. The default has been xz for a while now which should

Bug#833225: idle3-tools: Uses obsolete compressor for .deb data.tar member

Source: idle3-tools Source-Version: 0.9.1-1 Severity: important User: debian-d...@lists.debian.org Usertags: dpkg-obsolete-deb-data-tar-compressor Hi! This source package builds one or more binary packages using the deprecated compressor bzip2. The default has been xz for a while now which

Bug#833221: RFP: Linpac -- requesting a backport to Jessie and Wheezy

Package: wnpp Severity: normal This request is coming from the upstream developer (me)

Bug#833220: mention value of $k within for($k++){} vs. for(++$k){}

Package: perl-doc Version: 5.22.2-1 Severity: wishlist File: /usr/share/man/man1/perlop.1.gz The "Auto-increment and Auto-decrement" section of the perlop man page fails to address the value of $k within the following for loops: for($k++){} vs. for(++$k){}.

Bug#833219: pdfposter: Pdfposter produces blank output

Package: pdfposter Version: 0.6.0-2 Severity: important Tags: newcomer Dear Maintainer, pdfposter -m160x247mm -p594x420mm teste.pdf teste_1.pdf pdfposter -m160x247mm -p594x420mm malha.pdf malha_1.pdf The file teste.pdf was made in Libreoffice The file malha.pdf was made in LibreCad --

Bug#833218: markupsafe: Uses obsolete compressor for .deb data.tar member

Source: markupsafe Source-Version: 0.23-2 Severity: important User: debian-d...@lists.debian.org Usertags: dpkg-obsolete-deb-data-tar-compressor Hi! This source package builds one or more binary packages using the deprecated compressor bzip2. The default has been xz for a while now which should

Bug#833215: emacs24: Uses obsolete Source-Version substvar

Source: emacs24 Source-Version: 24.5+1-6 Severity: important User: debian-d...@lists.debian.org Usertags: dpkg-obsolete-source-version-substvar Hi! This source package uses the ${Source-Version} substvar variable deprecated since dpkg 1.13.19 in 2006-05-04. That upload also introduced the

Bug#833214: stl-manual: Uses obsolete compressor for .deb data.tar member

Source: stl-manual Source-Version: 3.30-13 Severity: important User: debian-d...@lists.debian.org Usertags: dpkg-obsolete-deb-data-tar-compressor Hi! This source package builds one or more binary packages using the deprecated compressor bzip2. The default has been xz for a while now which should

Bug#833217: pycryptopp: Uses obsolete compressor for .deb data.tar member

Source: pycryptopp Source-Version: 0.6.0.20120313-1 Severity: important User: debian-d...@lists.debian.org Usertags: dpkg-obsolete-deb-data-tar-compressor Hi! This source package builds one or more binary packages using the deprecated compressor bzip2. The default has been xz for a while now

Bug#833216: fluid-soundfont: Uses obsolete compressor for .deb data.tar member

Source: fluid-soundfont Source-Version: 3.1-5 Severity: important User: debian-d...@lists.debian.org Usertags: dpkg-obsolete-deb-data-tar-compressor Hi! This source package builds one or more binary packages using the deprecated compressor bzip2. The default has been xz for a while now which

Bug#833116: fgetty: Incorrect keystroke interpretation

Made some progress here! I haven't tried all your suggestions yet, but please see below. On Mon, Aug 01, 2016 at 10:06:49PM +0300, Dmitry Bogatov wrote: > > How insert this fancy letter "?"? I tried to `loadkeys es', but I > failed to locate this letter. My keyboard layout is Latin American

Bug#802231: jq: CVE-2015-8863

Hello Simon, Is there any possibility of shipping the patch for CVE-2015-8863 out of a release cycle? Upstream seems to be going through a period of idleness, but I'd really like to see the fix in. Thanks! -- Harlan Lieberman-Berg ~hlieberman

Bug#831211: ucommon: FTBFS with GCC 6: dh_makeshlibs: failing due to earlier errors

Hi Lucas, Jonas, twinkle has been marked for autoremoval from testing on 2016-08-27 due to this FTBFS. Building ucommon with GCC 6 instead of GCC 5 yields slight differences in the list of visible symbols. How should this bug be dealt with? Is it not simply a matter of waiting for GCC 6 to

Bug#833212: libevent: Uses obsolete compressor for .deb data.tar member

Source: libevent Source-Version: 2.0.21-stable-2 Severity: important User: debian-d...@lists.debian.org Usertags: dpkg-obsolete-deb-data-tar-compressor Hi! This source package builds one or more binary packages using the deprecated compressor bzip2. The default has been xz for a while now which

Bug#833211: dvd+rw-tools: Uses obsolete compressor for .deb data.tar member

Source: dvd+rw-tools Source-Version: 7.1-11 Severity: important User: debian-d...@lists.debian.org Usertags: dpkg-obsolete-deb-data-tar-compressor Hi! This source package builds one or more binary packages using the deprecated compressor bzip2. The default has been xz for a while now which

Bug#833210: bsd-finger: Uses obsolete compressor for .deb data.tar member

Source: bsd-finger Source-Version: 0.17-15 Severity: important User: debian-d...@lists.debian.org Usertags: dpkg-obsolete-deb-data-tar-compressor Hi! This source package builds one or more binary packages using the deprecated compressor bzip2. The default has been xz for a while now which should

Bug#833209: tessa: Uses obsolete Source-Version substvar

Source: tessa Source-Version: 0.3.1-6.1 Severity: important User: debian-d...@lists.debian.org Usertags: dpkg-obsolete-source-version-substvar Hi! This source package uses the ${Source-Version} substvar variable deprecated since dpkg 1.13.19 in 2006-05-04. That upload also introduced the

Bug#833206: osspsa: Uses obsolete Source-Version substvar

Source: osspsa Source-Version: 1.2.6-1 Severity: important User: debian-d...@lists.debian.org Usertags: dpkg-obsolete-source-version-substvar Hi! This source package uses the ${Source-Version} substvar variable deprecated since dpkg 1.13.19 in 2006-05-04. That upload also introduced the

Bug#833207: hylafax: Uses obsolete Source-Version substvar

Source: hylafax Source-Version: 3:6.0.6-6 Severity: important User: debian-d...@lists.debian.org Usertags: dpkg-obsolete-source-version-substvar Hi! This source package uses the ${Source-Version} substvar variable deprecated since dpkg 1.13.19 in 2006-05-04. That upload also introduced the

Bug#833208: clips: Uses obsolete Source-Version substvar

Source: clips Source-Version: 6.24-3+b1 Severity: important User: debian-d...@lists.debian.org Usertags: dpkg-obsolete-source-version-substvar Hi! This source package uses the ${Source-Version} substvar variable deprecated since dpkg 1.13.19 in 2006-05-04. That upload also introduced the

Bug#833025: dgit: quiltify smash strategy shouldn't fail when current patch queue fails to apply

Hello, On Mon, Aug 01, 2016 at 10:42:53AM +0100, Ian Jackson wrote: > Sean Whitton writes ("Bug#833025: dgit: quiltify smash strategy shouldn't > fail when current patch queue fails to apply"): > > I am the maintainer, but I think that there are use cases for a dgit > > quilt strategy that is

Bug#833203: dancer-xml: Uses obsolete Source-Version substvar

Source: dancer-xml Source-Version: 0.8.2.1-3 Severity: important User: debian-d...@lists.debian.org Usertags: dpkg-obsolete-source-version-substvar Hi! This source package uses the ${Source-Version} substvar variable deprecated since dpkg 1.13.19 in 2006-05-04. That upload also introduced the

Bug#833202: pygopherd: Uses obsolete Source-Version substvar

Source: pygopherd Source-Version: 2.0.18.4 Severity: important User: debian-d...@lists.debian.org Usertags: dpkg-obsolete-source-version-substvar Hi! This source package uses the ${Source-Version} substvar variable deprecated since dpkg 1.13.19 in 2006-05-04. That upload also introduced the

Bug#832880: Reproduced

Thanks, it looks like http://packages.debian.org/jessie/samba links to the wrong file list - despite the fact that http://packages.debian.org/jessie/samba covers the version in jessie-updates, the filelist links point to the contents in jessie itself, before updates. I've now removed the

Bug#833205: libcrypto++6: Assertion fails in cmac.cpp line 60

Package: libcrypto++6 Version: 5.6.3-6 Severity: important Tags: patch Dear Maintainer, The code in cmac.cpp CMAC_Base::Update() has an assertion that fails if a zero-length section is passed into it. Zero is meant to work: there's a guard for zero length just after the assertion. Swapping

Bug#833201: uclmmbase: Uses obsolete Source-Version substvar

Source: uclmmbase Source-Version: 1.2.16.0-1 Severity: important User: debian-d...@lists.debian.org Usertags: dpkg-obsolete-source-version-substvar Hi! This source package uses the ${Source-Version} substvar variable deprecated since dpkg 1.13.19 in 2006-05-04. That upload also introduced the

Bug#833204: routeplanner: Uses obsolete Source-Version substvar

Source: routeplanner Source-Version: 0.19+nmu1 Severity: important User: debian-d...@lists.debian.org Usertags: dpkg-obsolete-source-version-substvar Hi! This source package uses the ${Source-Version} substvar variable deprecated since dpkg 1.13.19 in 2006-05-04. That upload also introduced the

Bug#832331: libqpol1: doesn't give adequate information when there are conflicting type rules

On Mon, 1 Aug 2016 11:03:38 PM Laurent Bigonville wrote: > Are you sure it's lib*q*pol1 and not libsepol1? > > Codesearch seems to tell me it's the later: > > https://codesearch.debian.net/search?q=Conflicting+type+rules I'm not sure. Sorry for the low quality bug report. I'm busy working on

Bug#823393:

Hi Alexis, I've just prepared a new release of kdbg with your fixes, altough i'm a little curious about one particular diff reported[1]. Please have a look at line 196 of "./usr/share/doc/kdbg/changelog.gz" on [1]. There's also a problem with the name "​André Wöbbeking" and i'm not sure if your

Bug#832973: vile-filters: vile filter for mail broken

On Mon, Aug 01, 2016 at 04:22:37PM +1000, Brendan O'Dea wrote: > Out of curiosity, why does USE_LEXWRAP take an option? It doesn't appear to > do anything with it. Looking at the history, it turns out that my original idea was to use the parameter as part of the name for the actual yywrap

Bug#833200: firefox-esr: Please block evince-browser-plugin

Control: forwarded -1 https://bugzilla.mozilla.org/1092126 Here's an upstream bug that probably needs some prodding. Yes, it looks like Firefox explicitly does not support what the Evince browser plugin needs to do to support Epiphany (use GTK3). Thanks, Jeremy

Bug#833199: mffm-fftw: Uses obsolete Source-Version substvar

Source: mffm-fftw Source-Version: 1.7-3 Severity: important User: debian-d...@lists.debian.org Usertags: dpkg-obsolete-source-version-substvar Hi! This source package uses the ${Source-Version} substvar variable deprecated since dpkg 1.13.19 in 2006-05-04. That upload also introduced the

Bug#833200: firefox-esr: Please block evince-browser-plugin

Package: firefox-esr Version: 45.2.0esr-1 Debian's evince package in "testing" now ships evince-browser-plugin. epiphany-browser recommends it. However, if the plugin is used in Firefox, it will hang the browser. I can duplicate this in Ubuntu's Firefox which is GTK3 enabled so it's not just a

Bug#833197: libsigc++-1.2: Uses obsolete Source-Version substvar

Source: libsigc++-1.2 Source-Version: 1.2.7-2 Severity: important User: debian-d...@lists.debian.org Usertags: dpkg-obsolete-source-version-substvar Hi! This source package uses the ${Source-Version} substvar variable deprecated since dpkg 1.13.19 in 2006-05-04. That upload also introduced the

Bug#833198: libtcd: Uses obsolete Source-Version substvar

Source: libtcd Source-Version: 2.2.2-1 Severity: important User: debian-d...@lists.debian.org Usertags: dpkg-obsolete-source-version-substvar Hi! This source package uses the ${Source-Version} substvar variable deprecated since dpkg 1.13.19 in 2006-05-04. That upload also introduced the

Bug#833196: libpcl1: Uses obsolete Source-Version substvar

Source: libpcl1 Source-Version: 1.6-1 Severity: important User: debian-d...@lists.debian.org Usertags: dpkg-obsolete-source-version-substvar Hi! This source package uses the ${Source-Version} substvar variable deprecated since dpkg 1.13.19 in 2006-05-04. That upload also introduced the substvars

Bug#833194: libgconf-bridge: Uses obsolete Source-Version substvar

Source: libgconf-bridge Source-Version: 0.1-2.2 Severity: important User: debian-d...@lists.debian.org Usertags: dpkg-obsolete-source-version-substvar Hi! This source package uses the ${Source-Version} substvar variable deprecated since dpkg 1.13.19 in 2006-05-04. That upload also introduced the

Bug#833195: libident: Uses obsolete Source-Version substvar

Source: libident Source-Version: 0.22-3 Severity: important User: debian-d...@lists.debian.org Usertags: dpkg-obsolete-source-version-substvar Hi! This source package uses the ${Source-Version} substvar variable deprecated since dpkg 1.13.19 in 2006-05-04. That upload also introduced the

Bug#833193: RFS: chapel-minimal/1.13.1-1 [ITP]

Package: sponsorship-requests Severity: wishlist Dear mentors, I am looking for a sponsor for my package "chapel-minimal" * Package name: chapel-minimal Version : 1.13.1-1 Upstream Author : Ben Albrecht * URL : chapel.cray.com *

Bug#833192: Overwrites Message-Id when using "mutt -H" or Alt-e to resend (breaks patch mail threading)

Package: mutt Version: 1.6.2-1 Severity: normal When attempting to send a set of git patches recently, I noticed that the mails had broken threading. The mails had Message-Id, In-Reply-To, and References headers threading them together. However, mutt ignored the Message-Id header in the mails,

Bug#833191: offlineimap: Please add default value of sslcacertfile

Package: offlineimap Version: 6.6.1+dfsg1-2 Severity: wishlist As a bit of Debian integration, it would seem reasonable to add a default value for sslcacertfile (/etc/ssl/certs/ca-certificates.crt). -- System Information: Debian Release: stretch/sid APT prefers xenial-updates APT policy:

Bug#831039: Processed: moreinfo

It seems that it's a libav bug. If started like $ totem --gst-debug=6 the following output is produced: 0:00:05.212869886 17220 0x7fd284013b70 ERROR libav :0:: Invalid chars '.0' at the end of expression '1.0' 0:00:05.212878563 17220 0x7fd284013b70 ERROR libav

Bug#804180: NMU request

On Sun, 31 Jul 2016, Dima Kogan wrote: > Hi. > I prepared a remake=4.1 package. The sources live here: > https://github.com/dkogan/remake ho ho -- make source package (well -- make-dfsg) itself is still 1.0 format with all the patches in a single diff, without any fancy patch queuing in pkg

Bug#828241: atheme-services: FTBFS with openssl 1.1.0

On 2016-06-26 06:21:03, Kurt Roeckx wrote: > OpenSSL 1.1.0 is about to released. During a rebuild of all packages using > OpenSSL this package fail to build. A log of that build can be found at: >

Bug#833190: Please provide an option to not add X-getmail-retrieved-from-mailbox header

Package: getmail4 Severity: wishlist When getmail retrieves a mail, it unconditionally adds a header X-getmail-retrieved-from-mailbox with the name of the mailbox it retrieved the mail from. As far as I can tell, getmail doesn't have any option to avoid adding that header. I'd like to leave the

Bug#806654: libtool: FTBFS when built with dpkg-buildpackage -A

On Mon, 1 Aug 2016, Kurt Roeckx wrote: > Can you still reproduce the problem? I see you marked it as RC > now, but the buildds actually build it succesful. I raised to serious because I raised to serious all the bugs that were still open. Sorry if I answer your question by making another one:

Bug#833189: redis-server: Update via apt or dpkg hangs

Package: redis-server Version: 2:3.2.1-3 Severity: important Dear Maintainer, *** Reporter, please consider answering these questions, where appropriate *** * What led up to the situation? Normal apt full-upgrade including some Sid packages * What exactly did you do (or not do) that was

Bug#831244: [DRE-maint] Bug#831244: ruby-eventmachine: FTBFS: Build hangs minutes of inactivity

* Antonio Terceiro [160801 15:21]: > On Sun, Jul 31, 2016 at 10:21:39PM +0200, Christian Hofstaedtler wrote: > > * Lucas Nussbaum [160731 20:17]: > > > During a rebuild of all packages in sid, your package failed to build on > > > amd64. > > > > So I tried

Bug#825476: built later just fine

severity 825476 normal thanks 0.23.4+git4-g7eed8d8-2 built just fine in sid a few days back with libc6 2.23: https://buildd.debian.org/status/package.php?p=cython=unstable If fails to build against anything in experimental it must not be of 'serious' (rc) severity since experimental is not

Bug#833188: RFS: pam-u2f/1.0.4-0.3 [NMU]

Package: sponsorship-requests Severity: normal Dear mentors, I am looking for a sponsor for the package "pam-u2f" * Package name: pam-u2f Version : 1.0.4-0.3 Upstream Author : Yubico AG * URL : https://developers.yubico.com/pam-u2f/ * License :

Bug#832713: systemd: after "systemd (231-1) unstable" update systemd-jurnald.service fails to start

On Aug 1, 2016, at 2:40 PM, Felipe Sateler wrote: > On 28 July 2016 at 17:04, Michael Biebl wrote: >> Am 28.07.2016 um 22:50 schrieb Rick Thomas: >>> In the interest of having a working system, I reverted that machine to >>> systemd version 230-7.

Bug#833187: RFS: yuma123/2.8-1 [ITP] -- netconf/YANG toolchain

Package: sponsorship-requests Severity: wishlist Dear mentors, I am looking for a sponsor for my package "yuma123" * Package name: yuma123 Version : 2.8-1 Upstream Author : Vladimir Vassilev * URL :https://sourceforge.net/projects/yuma123

Bug#830645: (no subject)

tags +pending thanks working on it -- Yaroslav O. Halchenko Center for Open Neuroscience http://centerforopenneuroscience.org Dartmouth College, 419 Moore Hall, Hinman Box 6207, Hanover, NH 03755 Phone: +1 (603) 646-9834 Fax: +1 (603) 646-1419 WWW:

Bug#833186: locate: 'apt-get remove locate' does not remove '/etc/alternatives/locate'

Package: locate Severity: normal After running apt-get remove locate, the symbolic link and the binairy file remains in /etc/alternatives despite the package 'locate' being removed -- System Information: Debian Release: 8.5 APT prefers stable-updates APT policy: (500, 'stable-updates'),

Bug#827933: RFS: yabar/0.4.0-3 [ITP]

On 07/27/2016 03:28 AM, Sean Whitton wrote: > I can't sponsor the package, but I hope that the following review is > useful to you. Thanks for your very in-depth review, it is very helpful! > 1. You should install the examples to /usr/share/doc/yabar/examples, not > /usr/share/yabar/examples.

Bug#833105: RFS: vim-lastplace/3.0.2-1 [ITP]

Hi, On 01.08.2016 22:35, Gianfranco Costamagna wrote: > it is good, just called "3.0.2-2" > > please use -1 as versioning and dput -f on mentors until it gets accepted. > Ah ok, sorry. :-) I removed the package and uploaded it again as 3.0.2-1 . > last thing: how do I enable such extension?

Bug#832908: mongodb: CVE-2016-6494: world-readable .dbshell history file: LTS update and upgrade handling

Hi again I just realize that we need to change back the umask after the file is created. I'll update the patch tomorrow and send one that I know works. // Ola On Tue, Aug 2, 2016 at 12:13 AM, Ola Lundqvist wrote: > Hi all > > I have prepared a preliminary patch for wheezy. I

Bug#830750: photofloat: traceback on run

Control: severity -1 grave On 2016-07-11 00:38:38, Mark Eichin wrote: > (It looks like that's followed by release discussion, but just thought > I'd still add the "doesn't work out of the box" data point.) Right - PhotoFloat is in pretty bad shape, both in and outside Debian. There has been only

Bug#832908: mongodb: CVE-2016-6494: world-readable .dbshell history file: LTS update and upgrade handling

Hi all I have prepared a preliminary patch for wheezy. I have not yet been able to test it fully (it is building right now). It looks like attached. You may need to modify it for later versions. Please comment. The principles should be ok even if I may have made some stupid copy+paste mistake.

Bug#736548: monkeysign: Reports "key is expired, cannot sign" on non-expired key

On 2016-08-01 18:01:41, Jerome Charaoui wrote: > Le 2016-08-01 à 17:55, Antoine Beaupré a écrit : >> On 2016-07-16 18:57:10, Jerome Charaoui wrote: >>> Alas, the previous patch is insufficient as monkeysign halts on a >>> KEYEXPIRED error which occurs later on, probably when it's attempting to >>>

Bug#818977: removing or updating libmowgli?

On Tue, Jul 05, 2016 at 04:33:15PM +0200, Andrew Shadura wrote: > On 03/05/16 20:22, Antoine Beaupré wrote: > > This issue is now fixed. > > Yes, and I have uploaded 2.1.0 to Debian. Cool, thanks! > > However, to fix this in sid, we'll need to setup a transition for > > libmowgli. This seems

Bug#828641: FTBFS under Django 1.10

severity 828641 serious severity 828642 serious severity 828643 serious severity 828644 serious severity 828645 serious severity 828646 serious severity 828647 serious severity 828648 serious severity 828649 serious severity 828650 serious severity 828651 serious severity 828653 serious severity

Bug#736548: monkeysign: Reports "key is expired, cannot sign" on non-expired key

Le 2016-08-01 à 17:55, Antoine Beaupré a écrit : > On 2016-07-16 18:57:10, Jerome Charaoui wrote: >> Alas, the previous patch is insufficient as monkeysign halts on a >> KEYEXPIRED error which occurs later on, probably when it's attempting to >> cleanup uids. >> >> I'm pondering whether we should

Bug#736548: monkeysign: Reports "key is expired, cannot sign" on non-expired key

On 2016-07-16 18:57:10, Jerome Charaoui wrote: > Alas, the previous patch is insufficient as monkeysign halts on a > KEYEXPIRED error which occurs later on, probably when it's attempting to > cleanup uids. > > I'm pondering whether we should instead patch expect_pattern() to always > ignore

Bug#723763: monkeysign should not sign revoked uids

Control: tags -1 +moreinfo Could you provide unit tests coverage for this and verify that the tests pass after the patch is applied? Thanks! -- Never attribute to malice that which can be adequately explained by stupidity, but don't rule out malice. - Albert Einstein

Bug#833185: Udhcd not killed when DHCP_ENABLED is no

Package: udhcpd Version: 1:1.22.0-9+deb8u1 Severity: minor Udhcpd is running. I edit /etc/default/udhcpd to set DHCPD_ENABLED to no, then do /etc/init.d/udhcpd stop The scripts checks the value of DHCPD_ENABLED, and does nothing. Is this the expected behaviour? Shouldn't the stop action

Bug#806654: libtool: FTBFS when built with dpkg-buildpackage -A

On Mon, Jul 25, 2016 at 08:31:02PM +0200, Kurt Roeckx wrote: > On Mon, Jul 25, 2016 at 07:36:55PM +0200, Santiago Vila wrote: > > On Mon, 25 Jul 2016, Kurt Roeckx wrote: > > > > > The error you get is a testsuite failure. It outputs this to > > > stderr: > > > ERROR: ld.so: object

Bug#832713: systemd: after "systemd (231-1) unstable" update systemd-jurnald.service fails to start

On 28 July 2016 at 17:04, Michael Biebl wrote: > Am 28.07.2016 um 22:50 schrieb Rick Thomas: >> In the interest of having a working system, I reverted that machine to >> systemd version 230-7. Unsurprisingly, the problem went away. >> >> I’ll try re-installing 231-1 and

Bug#833156: [Pkg-openssl-devel] Bug#833156: Bug#833156: openssl: Please enable s390x asm optimisations

On 1 August 2016 at 20:38, Kurt Roeckx wrote: > On Mon, Aug 01, 2016 at 09:27:02PM +0200, Sebastian Andrzej Siewior wrote: >> control: fixed -1 1.1.0~pre5-5 >> control: found -1 1.0.2h-1 >> control: notfound -1 1.0.2g-1ubuntu4.1 >> >> On 2016-08-01 15:32:18 [+0100], Dimitri John

Bug#833156: [Pkg-openssl-devel] Bug#833156: openssl: Please enable s390x asm optimisations

On 1 August 2016 at 20:27, Sebastian Andrzej Siewior wrote: > control: fixed -1 1.1.0~pre5-5 > control: found -1 1.0.2h-1 > control: notfound -1 1.0.2g-1ubuntu4.1 > > On 2016-08-01 15:32:18 [+0100], Dimitri John Ledkov wrote: >> Version: 1.0.2g-1ubuntu4.1 > > since when

Bug#830729: [pkg-go] Bug#830729: Bug#830729: Bug#830729: golang-github-mitchellh-go-homedir: FTBFS: homedir_test.go:44: "/home/lamby" != "~"

On 2 Aug 2016, at 4:22 AM, Tianon Gravi wrote: > > On 31 July 2016 at 20:20, Potter, Tim (HPE Linux Support) > wrote: >> Patch attached to fix this, but it's a bit icky (and has been replaced by a >> shell out to call >> getent in a later version. >

Bug#832833: Pending fixes for bugs in the libtest-valgrind-perl package

tag 832833 + pending thanks Some bugs in the libtest-valgrind-perl package are closed in revision 48ca6875d27103ecbf1c04743a4d8b8716b46f39 in branch 'master' by gregor herrmann The full diff can be seen at

Bug#832833: libtest-valgrind-perl: FTBFS: Tests failures

On Mon, 01 Aug 2016 18:02:29 -0300, Vincent Pit (VPIT) wrote: > > > > then you might want > > > > to try giving a shot at the changes I pushed at : > > > > http://git.profvince.com/?p=perl/modules/Test-Valgrind.git;a=summary > > > > Ha! I finally found the time to play a bit, and applying

Bug#833184: icedove: apparmor profile for icedove denied on local mail

Package: icedove Version: 1:45.2.0-2 Severity: normal Dear Maintainer, *** Reporter, please consider answering these questions, where appropriate *** * What led up to the situation? use of icedove with apparmor * What exactly did you do (or not do) that was effective (or

Bug#830997: release.debian.org: Permission to consider dpkg-buildpackage -A bugs as RC

Greetings. I've finally raised to "serious" all the known bugs regarding "dpkg-buildpackage -A" that were still open. Thanks.

Bug#827411: piuparts: FTBFS on jessie: 'wheezy' != 'squeeze'

Hi Stefano, On Sat, Jul 30, 2016 at 06:39:28PM -0400, Stefano Rivera wrote: > Suggested solution attached. > Subject: [PATCH] Don't test the current Debian release status > Tracking that is distro-info-data's problem > def testConfStdDistroNames(self): > -

Bug#832833: libtest-valgrind-perl: FTBFS: Tests failures

Le 01/08/2016 à 16:18, gregor herrmann a écrit : Control: tag -1 + patch fixed-upstream On Sat, 30 Jul 2016 18:52:19 +0200, gregor herrmann wrote: Can you tell me the output of "valgrind --version" on your system? If, as I suspect, this output now ends with a full stop, Not really: %

Bug#833105: RFS: vim-lastplace/3.0.2-1 [ITP]

Hi, >yes, but it seems still sometime wrong it is good, just called "3.0.2-2" please use -1 as versioning and dput -f on mentors until it gets accepted. >we should be near :) last thing: how do I enable such extension? G.

Bug#832840: license-reconcile: FTBFS: dh_auto_test: perl Build test --verbose 1 returned exit code 255

On Mon, 01 Aug 2016 22:32:13 +0200, Jonas Smedegaard wrote: > > In general I think that license-reconcile needs an active maintainer, > > in cooperation with the moving underlying parts, or it needs to be > > removed. Doing emergency cleanups on each new failure is not > > sustainable. > >

  1   2   3   4   >