Bug#917141: isc-dhcp-client: error in syslog: nslcd: request denied by validnames option

Package: isc-dhcp-client Version: 4.3.5-3+deb9u1 Severity: minor dhclient seems to request a username from nslcd with a wildcard "*". This is denied by nslcd. Every time dhclient is runs, the following is in syslog: Dec 23 07:48:50 dhclient[1183]: DHCPREQUEST of 81.16.33.27 on eth0 to

Bug#917140: cyrus-sasl2: NMU changes dropped?

Source: cyrus-sasl2 Version: 2.1.27~rc8-1 Severity: normal Dear Maintainer, It looks like NMU changelogs (and possibly the associated changes) from -3 and -3.1 may have been dropped in the last upload. The BTS version tracking also now thinks the associated bugs are not fixed in unstable,

Bug#917139: Do not ignore unmounting of "/run/mount" and "/run/media" in "/etc/init.d/umountfs"

-BEGIN PGP SIGNED MESSAGE- Hash: SHA256 Package: initscripts Version: 2.93-1 In "/etc/init.d/umountfs" line 28, everything under "/run/*" is not unmounted when shutting down or rebooting the system, and this includes "/run/mount" and "/run/media". Also it is not uncommon to symlink

Bug#912091: closed by Jonas Smedegaard (Bug#912091: fixed in netatalk 2.2.6-2)

Control: reopen -1 On Sat, Dec 22, 2018 at 06:39:19PM +, Debian Bug Tracking System wrote: >* Add patch 106 > to fix detect Berkeley DB installed in multiarch location. > Closes: Bug#912091. Thanks to Helmut Grohne. Patching the source does not help when you don't build from

Bug#914955: Uploading soon test-kitchen and ruby-mixlib-install

On 12/23/18, Mathieu Parent wrote: > Ok. Will take it over. Should I take mixlib-install too? Yes, please.

Bug#917138: nagios4: CVE-2018-18245

Source: nagios4 Version: 4.3.4-2 Severity: important Tags: patch security upstream Hi, The following vulnerability was published for nagios4. CVE-2018-18245[0]: | Nagios Core 4.4.2 has XSS via the alert summary reports of plugin | results, as demonstrated by a SCRIPT element delivered by a

Bug#917136: (no subject)

This bug is related to https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=917124 My layout is as follows: sda8:00 465.8G 0 disk ├─sda1 8:1040M 0 part /boot/efi ├─sda2 8:20 128G 0 part │

Bug#917137: sphinxsearch FTCBFS: mysql_config does not work

Source: sphinxsearch Version: 2.2.11-2 Severity: normal Tags: patch upstream User: helm...@debian.org Usertags: rebootstrap Control: block -1 by 917135 sphinxsearch fails to cross build from source, because it fails detecting mysql using mysql_config. During cross compilation, mysql_config does

Bug#917129: slapd-smbk5pwd: crashes when enabling krb5

Control: reassign -1 libsasl2-2 2.1.27~rc8-1 Control: affects -1 slapd-smbk5pwd Dear cyrus-sasl2 maintainers, The latest version of libsasl2-2 seems to have gained dependencies on MIT Kerberos libraries. This breaks slapd-smbk5pwd, which links with Heimdal libraries (directly) and libsasl

Bug#917135: libmariadb-dev: missing Depends: libssl-dev

Package: libmaridb-dev Version: 1:10.3.11-1 Severity: serious Justification: missing dependency $ pkg-config --libs mariadb -lmariadb -lpthread -lz -ldl -lm -lssl -lcrypto $ dpkg -l libssl-dev dpkg-query: no packages found matching libssl-dev $ Given that mariadb.pc lists -lssl, it must Depends:

Bug#917129: slapd-smbk5pwd: crashes when enabling krb5

Thread 3 "slapd" hit Breakpoint 1, 0x7741a1c0 in krb5_init_context () from /usr/lib/x86_64-linux-gnu/libkrb5.so.3 (gdb) bt #0 0x7741a1c0 in krb5_init_context () from /usr/lib/x86_64-linux-gnu/libkrb5.so.3 #1 0x768e486c in smbk5pwd_modules_init (pi=) at

Bug#917134: opencl-c-headers: Prototype for clCreateFromGLBuffer should use cl_int, not int for error return

Package: opencl-c-headers Version: 2.1-1 Severity: minor Tags: upstream Hi, the signature for clCreateFromGLBuffer in uses "int *" for error return, while the specification uses "cl_int *". These are usually the same type, so minor. Simon -- System Information: Debian Release: 9.6 APT

Bug#323615: Propose to NMU debarchiver

Hello Ola, On Sat, Dec 22, 2018 at 11:15:14PM +0100, Ola Lundqvist wrote: > A check question here. Are you really referring to icoutils here? Not > debarchiver? No, sorry, copy and paste error, I meant debarchiver. > If you have a patch file, please send it to me and I'll release an updated >

Bug#917072: mmm-mode: fails to byte-compile with emacs-26

Alexander Zangerl writes: > i've nuked that dud patch and now everything incl. mmm-sample byte-compiles > fine on e26 in a fresh sid chroot, so i'm about to upload 0.5.7-3; > that'll invalidate your delayed nmu. > Sounds good to me. d

Bug#917072: mmm-mode: fails to byte-compile with emacs-26

On Sat, 22 Dec 2018 16:34:29 +0900, David Bremner writes: >I'm not quite sure whether this is a bug in emacs 26 or in mmm-mode, i found the issue, and it's a bug/mistake in mmm-mode; somehow or other i ended up adding the following, very dud, patch in version 0.5.7-2: +;; emacs >= 25 has no more

Bug#906235: library documentation not included; HTML docs not well-formed

close 906235 close 906238 thanks > The HTML files included in the package are not well-formed and > do not include a header. This is because the docs are to be served via godoc only, as explained in the package description. I guess that description was there when I filed this, but I missed

Bug#917133: openmpi: weird rm -f errors on upgrade

Source: openmpi Version: 3.1.3-6 Severity: critical Justification: causes serious data loss Hi. On upgrading from 3.1.3-5 I get these: Unpacking libopenmpi3:amd64 (3.1.3-6) over (3.1.3-5) ... rm: cannot remove '/usr/lib/x86_64-linux-gnu/fortran/gfortran-8#': No such file or directory rm:

Bug#917132: Do not compress favicon.ico file

Package: golang-1.11-doc Version: 1.11.2-2 Severity: minor The file: /usr/share/doc/golang-1.11-doc/favicon.ico.gz should not compressed, so that godoc can serve it. (After fixing that, the symlink at /usr/lib/go-1.11/favicon.ico.gz should be updated as well.) -d

Bug#917131: ITP: golang-github-alecthomas-kong -- command-line parser for Go

Package: wnpp Severity: wishlist Owner: Anthony Fok * Package name: golang-github-alecthomas-kong Version : 0.1.15-1 Upstream Author : Alec Thomas * URL : https://github.com/alecthomas/kong * License : Expat, see https://github.com/alecthomas/kong/issues/28

Bug#917074: Correction

Hi I checked it. Those packages must not be removed. - Tommi On 22.12.2018 15:47, Scott Kitterman wrote: On Saturday, December 22, 2018 11:59:26 AM Tommi Höynälänmaa wrote: I probably misinterpreted the results of command "apt-cache rdepends". Please ignore the request to remove

Bug#917126: Bug#874003: Nautilus does not launch applications

Control: forwarded -1 https://phab.enlightenment.org/T7521 Control: tags -1 patch On Sat, Dec 22, 2018 at 11:41:20PM +, Simon McVittie wrote: > While researching this in codesearch.debian.net I found that e17 > (Enlightenment) still sets the user-preferred file manager by setting > it as an

Bug#917130: crashs at start

Package: gimp Version: 2.10.8-1 Severity: grave Gimp crashes at startup. GNU Image Manipulation Program version 2.10.8 git-describe: GIMP_2_10_6-294-ga967e8d2c2 C compiler: Using built-in specs. COLLECT_GCC=gcc

Bug#917067: [pkg-cryptsetup-devel] Bug#917067: cryptsetup-bin: Opening a LUKS image which resides inside of the /home/ partition

On Sun, 23 Dec 2018 at 01:30:15 +0100, Mikhail Morfikov wrote: > On 22/12/2018 16:48, Guilhem Moulin wrote: >> Disk images, key files, and detached headers can reside on arbitrarily >> complicated file systems and block device stack, and setting up these >> stacks to make the files available prior

Bug#914897: tech-ctte: Should debootstrap disable merged /usr by default?

Hi, On Sun, 23 Dec 2018 00:36:52 + Simon McVittie wrote: > To be completely clear about the decision that Ian asked the technical > committee to overrule: > > In all debootstrap versions since 1.0.102, merged /usr is the default (for > all variants except --variant=buildd). This means that

Bug#523780:

Bug#917124: systemd: local-fs.target fails with result 'dependency'

Control: retitle -1 lvm2 logical volumes are not properly initialized Am 23.12.18 um 01:38 schrieb Ben Caradoc-Davies: >> Can you provide a verbose debug log as requested in my previous reply? > > "journalctl -alb" output attached to my previous email. Please let me > know if you require Ok,

Bug#917124: systemd: local-fs.target fails with result 'dependency'

Hi, Michael Biebl wrote: > Am 23.12.18 um 01:28 schrieb Ben Caradoc-Davies: > > Dec 23 13:07:52 ripley lvm2-activation-generator: lvmconfig failed > > Dec 23 13:07:52 ripley lvm2-activation-generator: Activation generator > > failed. > > Dec 23 13:07:52 ripley systemd[376]: > >

Bug#917072: mmm-mode: fails to byte-compile with emacs-26

On Sat, 22 Dec 2018 16:34:29 +0900, David Bremner writes: >I'm not quite sure whether this is a bug in emacs 26 or in mmm-mode, >but in any case it seems the file mmm-sample.el doesn't really need to >be byte compiled. weird. i'll try to experiment a bit with mmm-sample, see if i can narrow this

Bug#917129: slapd-smbk5pwd: crashes when enabling krb5

Package: slapd-smbk5pwd Version: 2.4.46+dfsg-5 Severity: important # ldapmodify -H ldapi:// -Y EXTERNAL << eof > dn: olcOverlay=smbk5pwd,olcDatabase={1}mdb,cn=config > changetype: add > objectClass: olcSmbK5PwdConfig > olcSmbK5PwdEnable: krb5 > eof SASL/EXTERNAL authentication started SASL

Bug#899269:

Bug#916905: RFS: Jerry (Chess GUI) /3.1-0 -- looking for sponsor

On Fri, Dec 21, 2018 at 08:45:40PM +, Dominik Klein wrote: > thanks very much for your feedback. > > I've filed an ITP under #917027. > > Moreover I've > - changed the icon to a png, since the problem is likely that not all > window manager are able to display .ico > - changed changelog to

Bug#917128: udev 240 breaks network interface naming

Package: udev Version: 240-1 Severity: important After upgrading from 239-15 to 240-1 or higher my network setup breaks. The breakage is similar to the last one I reported (bug #904198) though different in detail. This times all my vlan-devices on a physical device netint are first renamed to

Bug#917124: systemd: local-fs.target fails with result 'dependency'

On 23/12/2018 13:43, Michael Biebl wrote: Am 23.12.18 um 01:38 schrieb Ben Caradoc-Davies: On 23/12/2018 13:11, Michael Biebl wrote: Am 23.12.18 um 00:58 schrieb Ben Caradoc-Davies: Failure was seen with linux-image-4.19.0-1-amd64 4.19.9-1. (Needed to boot an 4.18.0-3-amd64 initramfs to get a

Bug#908216: btrfs blocked for more than 120 seconds

Package: src:linux Version: 4.18.20-2~bpo9+1 Severity: important This problem was so bad with 4.18.6-1~bpo9+1 that I had to revert to 4.17.0. When saw that 4.18.20 was out, I wanted to give it a try. Big mistake. Please fix this problem, already. Dec 22 18:14:11 vhost004 kernel: INFO: task

Bug#914897: tech-ctte: Should debootstrap disable merged /usr by default?

On Dec 23, Simon McVittie wrote: > An alternative to the usrmerge package might be to do this transition > in an initramfs hook or something similar, which would guarantee that > nothing else is concurrently altering /usr or the directories that are > meant to be merged into it. FWIW I tried

Bug#917124: systemd: local-fs.target fails with result 'dependency'

On 23/12/2018 13:40, Michael Biebl wrote: Am 23.12.18 um 01:28 schrieb Ben Caradoc-Davies: Dec 23 13:07:52 ripley lvm2-activation-generator: lvmconfig failed Dec 23 13:07:52 ripley lvm2-activation-generator: Activation generator failed. Dec 23 13:07:52 ripley systemd[376]:

Bug#917124: systemd: local-fs.target fails with result 'dependency'

Am 23.12.18 um 01:28 schrieb Ben Caradoc-Davies: > Dec 23 13:07:52 ripley lvm2-activation-generator: lvmconfig failed > Dec 23 13:07:52 ripley lvm2-activation-generator: Activation generator failed. > Dec 23 13:07:52 ripley systemd[376]: > /lib/systemd/system-generators/lvm2-activation-generator

Bug#917124: systemd: local-fs.target fails with result 'dependency'

Am 23.12.18 um 01:38 schrieb Ben Caradoc-Davies: > On 23/12/2018 13:11, Michael Biebl wrote: >> Am 23.12.18 um 00:58 schrieb Ben Caradoc-Davies: >>> Failure was seen with linux-image-4.19.0-1-amd64 4.19.9-1. (Needed to >>> boot an 4.18.0-3-amd64 initramfs to get a working system.) >> So 4.18 works

Bug#690412: Please auto-detect changed SSL certificates

Hi, If you consider the scope of this bug to be limited to only reloading XMPP TLS certificates on SIGHUP then this fixed since Prosody 0.10.0, see . -- Regards, Kim "Zash" Alvefur

Bug#842634: Bug#851877: fails every time

On Sat, Oct 06, 2018 at 11:38:59PM +0200, Santiago Vila wrote: > On Mon, 15 May 2017, Adam Borowski wrote: > > > > Looking at /etc/hosts within the schroot, I see: > > > 127.0.0.1 localhost > > > 127.0.0.1 localhost ip6-localhost ip6-loopback > > > 172.28.17.11abel.debian.org abel

Bug#917124: systemd: local-fs.target fails with result 'dependency'

On 23/12/2018 13:11, Michael Biebl wrote: Am 23.12.18 um 00:58 schrieb Ben Caradoc-Davies: Failure was seen with linux-image-4.19.0-1-amd64 4.19.9-1. (Needed to boot an 4.18.0-3-amd64 initramfs to get a working system.) So 4.18 works and 4.19 fails? No, 239-15 works with either kernel, and

Bug#914897: tech-ctte: Should debootstrap disable merged /usr by default?

To be completely clear about the decision that Ian asked the technical committee to overrule: In all debootstrap versions since 1.0.102, merged /usr is the default (for all variants except --variant=buildd). This means that new installations of Debian buster using debian-installer will have

Bug#917067: [pkg-cryptsetup-devel] Bug#917067: cryptsetup-bin: Opening a LUKS image which resides inside of the /home/ partition

On 22/12/2018 16:48, Guilhem Moulin wrote: > Disk images, key files, and detached headers can reside on arbitrarily > complicated file systems and block device stack, and setting up these > stacks to make the files available prior to unlocking is really not the > job of our initramfs boot scripts.

Bug#914897: debootstrap, buster: Please disabled merged /usr by default

On Mon, 03 Dec 2018 at 17:45:11 +0100, Svante Signell wrote: > On Sun, 2018-12-02 at 21:04 +0100, Marc Haber wrote: > > moving hundreds of megabytes from /usr to / over time. > > This solution was proposed by GNU/Hurd several years ago, and was scrapped due > to not being big enough player in the

Bug#917122: systemd can not start without name_to_handle_at option

Hi I believe it can be found here https://github.com/systemd/systemd/pull/5499 On Sat, 22 Dec 2018 at 23:47, Michael Biebl wrote: > Control: tags -1 + moreinfo > > Am 23.12.18 um 00:29 schrieb Vladimir Tiukhtin: > > Docker limits this system call be default. However RedHat image is > > running

Bug#916415: nocache broken with glibc 2.28: several programs just hang in call to futex(..., FUTEX_WAIT_PRIVATE, 2, NULL)

control: reassign -1 nocache control: tag -1 + patch On 2018-12-14 07:44, Aurelien Jarno wrote: > control: forwarded -1 https://github.com/Feh/nocache/issues/34 > > On 2018-12-14 13:33, Paul Wise wrote: > > Package: nocache/1.0-1,libc6/2.28-2 > > Severity: critical > > Justification: breaks

Bug#914897: tech-ctte: Should debootstrap disable merged /usr by default?

On Wed, 05 Dec 2018 at 14:03:19 +0100, Svante Signell wrote: > How about this case: > > - Make as default non merged-/usr for all buildds. This has been done: I sent patches, which have been applied. (This is actually implemented in two different places, either of which would have been

Bug#917124: systemd: local-fs.target fails with result 'dependency'

Am 23.12.18 um 00:58 schrieb Ben Caradoc-Davies: > Failure was seen with linux-image-4.19.0-1-amd64 4.19.9-1. (Needed to > boot an 4.18.0-3-amd64 initramfs to get a working system.) So 4.18 works and 4.19 fails? > Attached photo shows console after failure. Plymouth LUKS passphrase > entry has

Bug#917120: lintian: Lintianrc should contain valid configuration

Hi Salvo, > No error message, just that the comment at the top of the file states > that var assignments should have no spaces, and then all the example > assignments have spaces. I don't see any reference to spaces being illegal in this file. Please could you copy-paste what you are seeing? I'm

Bug#917127: grep: new upstream release brings performance improvements to some situations

Package: grep Version: 3.1-3 Severity: wishlist grep 3.2 brings performance improvements to some situations (and bug fixes): An over-30x performance improvement when many 'or'd expressions share a common prefix, thanks to improvements in gnulib's dfa.c, by Norihiro Tanaka. See gnulib

Bug#917122: systemd can not start without name_to_handle_at option

Control: tags -1 + moreinfo Am 23.12.18 um 00:29 schrieb Vladimir Tiukhtin: > Docker limits this system call be default. However RedHat image is > running correctly which means that they have back ported a patch for > systemd from upstream which resolves this problem on systemd side. Can > you

Bug#917124: systemd: local-fs.target fails with result 'dependency'

control: tags -1 + moreinfo Am 23.12.18 um 00:35 schrieb Ben Caradoc-Davies: > Package: systemd > Version: 240-1 > Severity: critical > Justification: breaks the whole system > > Dear Maintainer, > > after upgrade to systemd 240-1, local-fs.target fails with result > 'dependency', > causing

Bug#874003: Nautilus does not launch applications

Control: retitle -1 setting a handler for x-scheme-handler/file pseudo-MIME-type results in GLib applications sending all files to it Control: clone -1 -2 -3 Control: reassign -1 libglib2.0-0 2.53.6-1 Control: affects -1 nautilus Control: block -1 by -2 Control: reassign -2 exo-utils 0.6.2-5

Bug#917098: dpkg -l 'w*' displays 'un' packages

Hi! On Sat, 2018-12-22 at 17:31:31 +0200, Alexandros Prekates wrote: > Package: dpkg > Version: 1.18.25 > Severity: normal > In a new installed system with Debian 9.6 > > $ dpkg -l > > will list only packages with 'ii' state and a couple of 'rc'. > > But if i run: > > $ dpkg -l w*(or

Bug#917120: lintian: Lintianrc should contain valid configuration

No error message, just that the comment at the top of the file states that var assignments should have no spaces, and then all the example assignments have spaces. Unless I am misinterpreting the meaning of the comment, but the example syntax there has no spaces. Il giorno dom 23 dic 2018 alle

Bug#917121: firmware-iwlwifi: gabrielel...@hotmail.com

Package: firmware-iwlwifi Version: 20180825+dfsg-1 Severity: normal Dear Maintainer, *** Reporter, please consider answering these questions, where appropriate *** * What led up to the situation? * What exactly did you do (or not do) that was effective (or ineffective)? * What was

Bug#917123: firmware-iwlwifi: slow wifi conection(download speed)

Package: firmware-iwlwifi Version: 20180825+dfsg-1 Severity: normal Dear Maintainer, *** Reporter, please consider answering these questions, where appropriate *** * What led up to the situation? * What exactly did you do (or not do) that was effective (or ineffective)? * What was

Bug#917122: systemd can not start without name_to_handle_at option

Package: systemd Version: 232-25+deb9u6 Running Debian Stretch in docker container results in Failed to determine whether /sys is a mount point: Operation not permitted Failed to determine whether /proc is a mount point: Operation not permitted Failed to determine whether /dev is a mount point:

Bug#917120: lintian: Lintianrc should contain valid configuration

tags 917120 + moreinfo thanks Hi Salvo, > According to the comments at the beginning of the file, /etc/lintianrc uses > shell syntax (it gets sourced I presume). Hm? It's not shell, it's parsed with: https://salsa.debian.org/lintian/lintian/blob/master/commands/lintian.pm#L1240 > It would

Bug#916620: python-mailmanclient-doc: broken symlinks: /usr/share/doc/python-mailmanclient/{rst,index.html}

Le dimanche 16 décembre 2018 à 18:15:59+0100, Andreas Beckmann a écrit : > Package: python-mailmanclient-doc > Version: 3.2.0-2 > Severity: normal > User: debian...@lists.debian.org > Usertags: piuparts > > Hi, > > during a test with piuparts I noticed your package ships (or creates) > a broken

Bug#916909: 0ad game fails to start

Control: reassign -1 libnvtt2 2.1.0-git20160229+dfsg-2~exp1 Control: retitle -1 libnvtt2/experimental: nvtt::InputOptions::setTextureLayout(nvtt::TextureType, int, int, int) removed without SONAME bump Control: severity -1 serious On Thu, 20 Dec 2018 at 18:50:52 +0300, scdes...@yandex.ru wrote:

Bug#917037: ITP: python3-zeroconf -- Pure Python implementation of multicast DNS service discovery (Python3)

On Fri, 21 Dec 2018 at 21:59:46 +0100, Ruben Undheim wrote: > python-zeroconf already exists in the Debian archive. However, upstream has > dropped support for Python 2, and there are reverse dependencies in Debian > which depend on the Python 2 package. This makes it necessary with a separate >

Bug#917120: lintian: Lintianrc should contain valid configuration

Package: lintian Version: 2.5.117 Severity: wishlist Dear Maintainer, According to the comments at the beginning of the file, /etc/lintianrc uses shell syntax (it gets sourced I presume). However all the later commented example options do not use said valid syntax. It would be better if people

Bug#917119: [Qa-jenkins-dev] Bug#917119: jenkins.debian.org: Lintian test jobs have not run since 21st November 2018

Control: owner -1 ! On Sat, Dec 22, 2018 at 10:30:41PM +, Chris Lamb wrote: > Any pointers on why https://jenkins.debian.net/job/lintian- > tests_sid/ has not run in ~1 mo ? > no idea, no I know what's going on, I'm very sorry for not noticying this earlier (as somebody

Bug#916101: mailman3: uses a hard-coded and mismatched api_key in mailman-hyperkitty.cfg

Le lundi 10 décembre 2018 à 08:12:21+, Sampo Sorsa a écrit : > Source: mailman3 > > Dear Maintainer, > > mailman-hyperkitty.cfg [1] contains: > > api_key: SecretArchiverAPIKey > > mailman3-web postinst however, checks for this api_key and generates a random > one if it has not been

Bug#917119: jenkins.debian.org: Lintian test jobs have not run since 21st November 2018

Package: jenkins.debian.org Severity: normal Hey, Any pointers on why https://jenkins.debian.net/job/lintian- tests_sid/ has not run in ~1 mo ? no idea, no other lintian jobs have run? No, https://jenkins.debian.net/job/lintian-tests_buster/ (for

Bug#917066: libqbscore1.12: log-level debug causes segfault

On Sat, 22 Dec 2018 at 18:25, Dmitry Shachnev wrote: [snip] > The patch author is Christian Kandeler, the upstream Qbs developer. > So he should push the patch, not Wookey. oh, my bad! Sorry Wookey! -- Lisandro Damián Nicanor Pérez Meyer http://perezmeyer.com.ar/

Bug#901246: closed by Bernhard Schmidt (Re: linphone-nogtk depends on X and OpenGL)

Am 20.12.18 um 09:31 schrieb Pali Rohár: Hi Pali, >> This was indeed quite bad in 3.6.1 which was present in stretch. >> >> In 3.12 the situation has improved a lot. It is not perfect yet, since >> linphone depends on libmediastreamer-voip10, which in turn depends on a >> lot of media libraries

Bug#914607: Re-adding python-dfwinreg

Control: tag -1 pending I have just uploaded dfwinreg/20181214-2 to DELAYED/10 -- it will have to wait for python-dtfabric and python3-dtfabric to reach unstable. Cheers, -Hilko

Bug#917082: openscenegraph depends and build-depends on cruft packages

Hi, Em sáb, 22 de dez de 2018 às 11:33, peter green escreveu: > > package: openscenegraph > version: 3.2.2+dfsg1-2 > severity: serious > > libopenscenegraph100v5 depends on libcoin80-5 and the openscenegraph source > package bulid-depends on libcoin80-dev. These packages are no longer built by

Bug#323615: Propose to NMU debarchiver

Hi Helge A check question here. Are you really referring to icoutils here? Not debarchiver? If you have a patch file, please send it to me and I'll release an updated version with the examples section included. Best regards // Ola On Wed, 19 Dec 2018 at 17:42, Helge Kreutzmann wrote: > To:

Bug#859667: libundead: FTBFS on armhf and ppc64el: tests fail

Hi, the package builds only for amd64 and i386. I wonder if it makes sense to simply restrict the architectures and close this bug. Kind regards Andreas. -- http://fam-tille.de

Bug#833401: debian-policy: virtual packages: dbus-session-bus, default-dbus-session-bus

On Fri, 07 Dec 2018 19:26:50 -0700, Sean Whitton wrote: > Thanks. Seeking seconds: > > diff --git a/virtual-package-names-list.yaml b/virtual-package-names-list.yaml > index ab2662e..f7626ef 100644 > --- a/virtual-package-names-list.yaml > +++ b/virtual-package-names-list.yaml > @@ -106,6

Bug#850156: Patch implementing CTTE decision

On Sat, 17 Nov 2018 09:14:52 -0700, Sean Whitton wrote: > Seeking seconds: > > diff --git a/policy/ch-source.rst b/policy/ch-source.rst > index 3c6c9d5..821010f 100644 > --- a/policy/ch-source.rst > +++ b/policy/ch-source.rst > @@ -787,6 +787,13 @@ according to this convention, the C source code

Bug#914955: Uploading soon test-kitchen and ruby-mixlib-install

Le samedi 22 décembre 2018, Hleb Valoshka <375...@gmail.com> a écrit : > On 12/22/18, Mathieu Parent wrote: >> 23 days have passed since those ITS. i will upload to DELAYED/7 now. >> >> All the changes are on salsa. > > Hi Mathieu, > > Could you takeover maintenance for test-kitchen? I don't use

Bug#917118: ITP: python-mbed-ls -- module listing mbed-enabled devices connected to host

Package: wnpp Owner: Nick Morrott Severity: wishlist X-Debbugs-CC: debian-de...@lists.debian.org, debian-pyt...@lists.debian.org * Package name: python-mbed-ls Version : 1.6.2 Upstream Author : Przemyslaw Wirkus * URL : https://github.com/ARMmbed/mbed-ls * License

Bug#915419: debdiff for 915692, 915419

Control: tags -1 pending On Wed, 19 Dec 2018 16:39:17 +0100 Luca Boccassi wrote: > Dear Maintainer, >  > In order to allow the DPDK 17.11 -> 18.11 transition to happen [1], I > intend to upload a source NMU fixing 915692 and 915419 (debdiff > attached) either at the end of this week or at the

Bug#917066: libqbscore1.12: log-level debug causes segfault

On Sat, Dec 22, 2018 at 06:18:05PM -0300, Lisandro Damián Nicanor Pérez Meyer wrote: > Disclaimer: I *think* that QBS works as with Qt: normal Qt workflow > expects the patch writer to submit the change to Qt's gerrit instance > due to the CLA. Qt submodule maintainers shouldn't get patches from

Bug#917066: libqbscore1.12: log-level debug causes segfault

Hi Wookey! On Sat, 22 Dec 2018 at 18:06, Wookey wrote: > > On 2018-12-22 21:56 +0300, Dmitry Shachnev wrote: > > Hi Wookey! > > > > On Sat, Dec 22, 2018 at 03:06:21AM +, Wookey wrote: > > > Enabling --log-level debug (or using --more-verbose) (in the build of > > > dewalls) causes the build

Bug#917116: Buster: Salt Depends: python3-tornado (< 5) but 5.1.1-2 is to be installed

Package: salt-common Dear team, While installing salt-minion, I wasn't able to, because salt-common depends on python3-tornado (< 5) but Buster does 5.1.1-2. Will a simple rebuild solve the issue? Or is there more to do? Thanks, -- Frans van Berckel Media Engineer / Linux Master LinkedIn:

Bug#917117: grub-efi-amd64-signed: doesn't mount cryptodisk

Package: grub-efi-amd64-bin Version: 1+2.02+dfsg1+9 Severity: critical Dear Maintainer, I'm running a UEFI system. I have GRUB_ENABLE_CRYPTODISK=y in my /etc/default/grub. Ever since 2.02+dfsg1+6, each GRUB2 update removes cryptomount call from /boot/efi/EFI/debian/grub.cfg, and thus breaks

Bug#916779: libc6-armhf-cross: strerror(-3) sets errno to ENOMEM

control: clone 916779 -1 control: reassign -1 gcc-8 control: retitle -1 gcc-8: --fno-math-errno causes GCC to consider that malloc does not set errno control: submitted -1 https://gcc.gnu.org/bugzilla/show_bug.cgi?id=88576 On 2018-12-22 13:37, Aurelien Jarno wrote: > This is not what happens,

Bug#917066: libqbscore1.12: log-level debug causes segfault

On 2018-12-22 21:56 +0300, Dmitry Shachnev wrote: > Hi Wookey! > > On Sat, Dec 22, 2018 at 03:06:21AM +, Wookey wrote: > > Enabling --log-level debug (or using --more-verbose) (in the build of > > dewalls) causes the build to fail with a segfault. > > > > This has been discussed upstream and

Bug#917114: ansible: crashes when trying to read vault variables

Package: ansible Version: 2.7.5+dfsg-1 Severity: normal Dear Maintainer, Using testing, Ansible crashes when trying to read vault variables. I see this issue since Ansible 2.6 at least. For example, I have a playbook I run with: ansible-playbook -i host.ini -bkK --vault-id @prompt main.yml

Bug#917042: dtfabric: Wrong name

Control: tag -1 patch Dear maintainer, I have uploaded a fixed package to DELAYED/10; please feel free to reschedule or cancel my upload as you see fit. The patches I applied to my local git clone are attached to this mail. Cheers, -Hilko >From 89bc2d6ac0cf92c65ef015b239928b54b0ae9270 Mon Sep

Bug#916779: libc6-armhf-cross: strerror(-3) sets errno to ENOMEM

On 2018-12-22 19:42, Tim Rühsen wrote: > On 22.12.18 16:56, Aurelien Jarno wrote: > > The problem is that qemu-arm does not provide a heap to the program, so > > glibc fails to alloc memory through brk. This causes malloc to switch to > > mmap based memory allocation, and this also sets errno to

Bug#917093: matplotlib2 breaks graphlan autopkgtest

Andreas, On Sat, Dec 22, 2018 at 3:45 PM Andreas Tille wrote: > I'd like to forward a bug report against the Debian packaged graphlan. did you even check the error log? it's almost 100% an issue with Debian matplotlib (which i'll look at it in the comings days) -- Sandro "morph" Tosi My

Bug#917093: matplotlib2 breaks graphlan autopkgtest

Control: tags -1 help Control: tags -1 upstream Control: forwarded -1 Nicola Segata Hi Nicola, I'd like to forward a bug report against the Debian packaged graphlan. (I admit I have not found a way to report issues publicly on bitbucket.) The packaged code is identical with tag 1.1.3 (Commit

Bug#917113: libraw: CVE-2018-20363

Source: libraw Version: 0.19.1-1 Severity: important Tags: security upstream Forwarded: https://github.com/LibRaw/LibRaw/issues/193 Hi, The following vulnerability was published for libraw. CVE-2018-20363[0]: | LibRaw::raw2image in libraw_cxx.cpp in LibRaw 0.19.1 has a NULL pointer |

Bug#878832: tbb: FTBFS on hppa: rml::pool_* undefined

The problem is "arch" is not defined for hppa in linux.inc. Regards, Dave Anglin -- John David Anglin dave.ang...@bell.net --- ./build/linux.inc.save 2014-11-17 22:21:52.674304007 -0500 +++ ./build/linux.inc 2014-11-17 22:25:35.916722257 -0500 @@ -70,6 +70,9 @@ ifeq

Bug#917112: libraw: CVE-2018-20364

Source: libraw Version: 0.19.1-1 Severity: important Tags: security upstream Forwarded: https://github.com/LibRaw/LibRaw/issues/194 Hi, The following vulnerability was published for libraw. CVE-2018-20364[0]: | LibRaw::copy_bayer in libraw_cxx.cpp in LibRaw 0.19.1 has a NULL | pointer

Bug#915407: ping

Hi! Could you please either take this patch or propose a different approach? I have received no feedback other than a brief unconclusive remark on IRC. The clock for Buster is ticking; to get any testing we'd need to act soon. Not only this approach has been proposed by one of systemd maintainers

Bug#917111: libraw: CVE-2018-20365

Source: libraw Version: 0.19.1-1 Severity: important Tags: security upstream Forwarded: https://github.com/LibRaw/LibRaw/issues/195 Hi, The following vulnerability was published for libraw. CVE-2018-20365[0]: | LibRaw::raw2image() in libraw_cxx.cpp has a heap-based buffer overflow. If you fix

Bug#917110: ITP: satpy -- Python package for earth-observing satellite data processing

Package: wnpp Severity: wishlist Owner: Antonio Valentino * Package name: satpy Version : 0.10.0 Upstream Author : The Pytroll Team * URL : https://github.com/pytroll/satpy * License : GPL-3+ Description : Python package for earth-observing satellite

Bug#917109: opensc: Rutoken ECP card not work after upgrade

Package: opensc Version: 0.16.0-3+deb9u1 Severity: normal After upgrading opensc-0.16.0-3, opensc-pkcs11-0.16.0-3 to opensc-0.16.0-3+deb9u1, opensc-pkcs11-0.16.0-3+deb9u1 "Rutoken ECP" token not work: $ pkcs11-tool -L Available slots: Slot 0 (0x0): Aktiv Rutoken ECP 00 00 token state:

Bug#870396: [Pkg-alsa-devel] Bug#870396: alsa-lib: fix SIGSEGV on x32 (and a minor typo in the testsuite)

(For alsa-de...@alsa-project.org I’ve attached the diffs this eMail thread has been about, with hope you will apply them in the next upstream release.) Elimar Riesebieter dixit: >it seems that you are an exclusive user of the x32 port ;-) Please If you actually read that thread you’d know I’m

Bug#886112: (no subject)

I also ran into this problem, after selectively upgrading calendarserver only. If it helps, I narrowed the fix on my system to upgrading python-sqlparse from version 0.1.13-2 (the version I had installed when encountering the error) to 0.2.4-1 (the current version in testing and unstable). It's

Bug#914129: not iptables related, it's docker that needs updating

See the bug opened against the package docker.io: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=911808 (I'm not sure if these two bugs should be merged, as I'm not so familiar with the BTS)   Arnaud

Bug#913723: please confirm that dictionaries should move to section localization

Hi Guillem, Quoting Guillem Jover (2018-12-22 18:58:04) > On Sun, 2018-12-02 at 15:48:53 +0100, Jonas Smedegaard wrote: > > Quoting Guillem Jover (2018-12-02 15:17:02) > > > On Sun, 2018-11-18 at 05:44:42 -0500, Chris Lamb wrote: > > > > Could you propose a patch that would fix this to your > >

Bug#911808: upstream bug

On Fri, 09 Nov 2018 18:41:18 -0500 Jason Woofenden wrote: > Hi Maintainer, > > I found the upstream bug forthe "chain 'DNAT' does not exist" bug: > > https://github.com/moby/moby/issues/38099 > > WORKAROUND: > update-alternatives --config iptables > choose iptables-legacy > > -- > Jason > >

  1   2   >