Bug#919929: python-scipy: autopkgtest fails (Re: bug#919929)

On 2019-03-10 03:51, Paul Gevers wrote: Hi Drew, On 08-03-2019 03:08, Drew Parsons wrote: On 2019-03-07 20:46, Paul Gevers wrote: If you upload now, your package will not migrate to testing before the full freeze becomes effective so it would need an unblock. If you want to fix this issue

Bug#924047: FTBFS: package don't build successful after new GCC version

Am 10.03.19 um 05:39 schrieb أحمد المحمودي: > I'd rather remove the symbols file. That's the last option in my eyes as it's a step backwards and is absolutely not needed as I fixed the problem already. The main problem with the symbols is that the symbols are simply not versioned and that's an

Bug#924184: no help for download template?

Package: lxc Version: 1:3.1.0+really3.0.3-5 Running lxc-create -t download -- --help I had expected to get usage information about the download template, but instead I got a huge list of images. Next it showed Distribution: and got unresponsive. Exit with ^C or ^D. Apparently

Bug#924183: postfix: Trust anchor files (tafile=) in TLS policy break secure level email delivery

Package: postfix Version: 3.4.1-1 Severity: important Tags: patch Hi, I have entries like this: [domain.tld]:587secure tafile=/etc/ssl/certs/Lets-Encrypt-Authority-X3.pem … in the file referenced by: smtp_tls_policy_maps = hash:/etc/postfix/tls_policy This worked just fine until

Bug#924182: [pre-approval] unblock: julia/1.0.3+dfsg-5

Package: release.debian.org Severity: normal User: release.debian@packages.debian.org Usertags: unblock This is a pre-approval for unblocking julia 1.0.3+dfsg-5, which follows the unblock request for llvm-toolchain-6.0 (= 1:6.0.1-11). The difference between julia/testing and

Bug#924181: unblock: llvm-toolchain-6.0/1:6.0.1-11

Package: release.debian.org Severity: normal User: release.debian@packages.debian.org Usertags: unblock Please unblock package llvm-toolchain-6.0 -- Summary -- * Remove 'Multi-Arch: same' in libclang (Closes: #874248) * Cherry-pick various llvm fixes for Julia (Closes: #919628) * Rebase

Bug#924180: file-roller: Trims files extracted from iso images

Package: file-roller Version: 3.30.1-2 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)? I tried to extract files

Bug#924027: unblock: extsmail/2.2-4

On Sat, 9 Mar 2019 15:43:51 + Jonathan Wiltshire wrote: > Control: tag -1 moreinfo > > Hi, > > On Fri, Mar 08, 2019 at 02:40:48PM +0100, Olivier Girondel wrote: > > Please unblock extsmail. > > > > I uploaded a new version of extsmail, which reset the package's > > transition countdown,

Bug#917738: patch

tag 917738 + patch thanks Hi, here's a patch for bug #917738 that I extracted from upstream. Description: remove WebServiceException Origin: upstream, https://github.com/OpenHFT/Chronicle-Threads/commit/bb1d4edfc7a783ebdc7c58bfc2f278f665e2539e#diff-e5af304c7efa4fec7930553b2fab754b Index:

Bug#924139: www.debian.org: migrate from python to python3

On Sat, Mar 09 2019, Cyril Brulebois wrote: > ...snip... > point, as Python 2 is on the way out. Well i'm not position to resolve it. However that is very very very dangerous i think. Anyhow, it is interesting PR, to me. Sincerely, Byung-Hee. -- Still i'm waiting for Debian 11 --

Bug#924047: FTBFS: package don't build successful after new GCC version

On Fri, Mar 08, 2019 at 09:43:17PM +0100, Carsten Schoenert wrote: > the systemc package is currently failing to build from source basically > related due a newer GCC version and changed symbols introduced by the > newer GCC. > > I've fixed the reason of the FTBFS by modifying and adopting the >

Bug#922647: Info received (Bug#922647: systemd --user no longer running)

On Sat, Mar 09, 2019 at 08:25:50PM +0100, Michael Biebl wrote: > [bringing Steve, our pam maintainer, into the loop] > Hi Steve, > the following looks like an issue in pam-auth-update and similar to > https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=923362 > Any idea what might be going wrong

Bug#924179: Package: installation-reports

Package: installation-reports Boot method: DVD Image version: https://cdimage.debian.org/cdimage/unofficial/non-free/cd-including-firmware/weekly-builds/amd64/iso-dvd/firmware-testing-amd64-DVD-1.iso Date: 2019-03-10 noon (AU) Machine: Desktop Processor: Ryzen 3 2200G/Vega 8 Memory: 2x4gb ddr4

Bug#924177: RFS: blastem/0.6.3-1 -- Fast and accurate Genesis emulator

Package: sponsorship-requests Severity: normal Dear mentors, I am looking for a sponsor for my package "blastem" * Package name: blastem Version : 0.6.3-1 Upstream Author : Michael Pavone * URL : https://www.retrodev.com/blastem * License : GPL-3+

Bug#924176: apt-dater: broken symlink: /usr/share/doc/apt-dater/README -> README.md

Package: apt-dater Version: 1.0.4-1 Severity: normal User: debian...@lists.debian.org Usertags: piuparts Hi, during a test with piuparts I noticed your package ships (or creates) a broken symlink. >From the attached log (scroll to the bottom...): 0m22.7s ERROR: FAIL: Broken symlinks:

Bug#924178: python-paramiko: DeprecationWarning about EllipticCurvePublicNumbers when using duplicity

Package: python-paramiko Version: 2.4.2-0.1 Severity: normal Forwarded: https://github.com/paramiko/paramiko/issues/1369 I see the following in my duplicity cronjob logs: /usr/lib/python2.7/dist-packages/paramiko/kex_ecdh_nist.py:39: CryptographyDeprecationWarning: encode_point has been

Bug#924175: android-sdk: broken symlink: /usr/lib/android-sdk/tools/bin/screenshot2 -> ../../../../bin/screenshot2

Package: android-sdk Version: 25.0.0+10 Severity: important User: debian...@lists.debian.org Usertags: piuparts Hi, during a test with piuparts I noticed your package ships (or creates) a broken symlink. >From the attached log (scroll to the bottom...): 1m20.7s ERROR: FAIL: Broken symlinks:

Bug#924174: ruby-rails-assets-perfect-scrollbar: broken symlink: /usr/share/ruby-rails-assets-perfect-scrollbar/app/assets/javascripts/perfect-scrollbar.js -> ../../../../javascript/utatti-perfect-scr

Package: ruby-rails-assets-perfect-scrollbar Version: 1.4.0-1 Severity: serious User: debian...@lists.debian.org Usertags: piuparts Hi, during a test with piuparts I noticed your package ships (or creates) a broken symlink. >From the attached log (scroll to the bottom...): 1m13.4s ERROR: FAIL:

Bug#924129: debian-installer: Kernel for armhf for stretch unbootable

On 2019-03-09, Vagrant Cascadian wrote: > On 2019-03-09, Cyril Brulebois wrote: >> Peter Lebbing (2019-03-09): >>> Debian kernel bug #922478 renders armhf systems unbootable. This bug was >>> fixed, but the debian-installer images still use (I presume) kernel >>> version 4.9.144-3, the unbootable

Bug#924173: nmu: sphinxbase_0.8+5prealpha+1-3

Package: release.debian.org Severity: normal User: release.debian@packages.debian.org Usertags: binnmu nmu sphinxbase_0.8+5prealpha+1-3 . ANY . unstable . -m "Rebuild with dh-python 3.20190307 (#920037)" dw sphinxbase_0.8+5prealpha+1-3 . ANY . unstable . -m "dh-python (>= 3.20190307)"

Bug#924172: www.debian.org: differences under english/ between builds in stretch and buster

Package: www.debian.org Severity: normal User: www.debian@packages.debian.org Usertags: scripts Hi, While working on rebuilding the website within stretch and buster, I've noticed the following. This is a curated summary based on diffing a stretch build tree and a buster build tree, after

Bug#908514: [rt.cpan.org #127094] possible duplicate, doubts about the patch and the original code

On Fri, Dec 28, 2018 at 10:12:15PM +0100, joy wrote: > * https://forum.mikrotik.com/viewtopic.php?t=91863 from 2014 > > Even if all those devices have not been RFC-compliant JFTR I had approached MikroTik about their issue, provided a test case and tested a beta, and now with RouterOS 6.44

Bug#924171: libdictzip-java: broken symlinks: /usr/share/doc/libdictzip-java/api/jquery/jquery-ui.* -> ../../../../javascript/jquery-ui/jquery-ui.*

Package: libdictzip-java Version: 0.8.2-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 symlink. >From the attached log (scroll to the bottom...): 0m16.1s ERROR: FAIL: Broken symlinks:

Bug#924170: kytos-sphinx-theme-common: broken symlinks: /usr/share/kytos_sphinx_theme/kytos/static/{bootstrap,js}

Package: kytos-sphinx-theme-common Version: 0.0.1+dfsg-1 Severity: normal User: debian...@lists.debian.org Usertags: piuparts Hi, during a test with piuparts I noticed your package ships (or creates) a broken symlink. >From the attached log (scroll to the bottom...): 0m17.0s ERROR: FAIL:

Bug#885759: Use /var/run as a statedir, and not /var/run/slurm-llnl

Hi Met, thank you for this bug report. On Fri, Mar 01, 2019 at 12:48:20AM +0100, n...@sucha.eu wrote: > What happened is that config files (slurm.conf, slurmdbd.conf) still > contain pid paths in /run/slurm-llnl/. Note: not /var/run/slurm-llnl/ but > /run/slurm-llnl in my case. The intention was

Bug#924166: debram: broken symlink: /usr/share/doc/debram/HISTORY.gz -> ../debram-data/HISTORY.gz

Good notice. I believe that you are right. I don't suppose that this bug is important enough to bother the release managers about, since the package in question is used by almost no one, but if not before the release this bug should be addressed after. Thank you for the notice. I appreciate it. I

Bug#639937: Don't tell people to use jigdo

OK I let it run, and indeed now it is getting packages from snapshot.debian.org/archive/ ... at rate 24.3KB/s... So nevermind, instead of $ jigdo-lite http://cdimage.debian.org/cdimage/weekly-builds/amd64/jigdo-cd/debian-testing-amd64-netinst.jigdo and selecting a local Taiwan mirror, I'll just

Bug#924169: libdvd-pkg: requires /var/lib to be 'exec'

Package: libdvd-pkg Version: 1.4.0-1-2 Severity: normal Dear Maintainer, *** /tmp/bug_report_libdvd-pkg.txt package : libdvd-pkg * first attempts : # dpkg-reconfigure libdvd-pkg Can't exec "/var/lib/dpkg/info/libdvd-pkg.config": Permission non accordée at /usr/share/perl/5.24/IPC/Open3.pm line

Bug#821006: make_systemd_links() does not resolve symlinks

On Thu, 14 Apr 2016 15:44:02 +0200 Michael Biebl wrote: > Package: init-system-helpers > Version: 1.29 > Severity: normal > File: /usr/sbin/update-rc.d > > If a package ships a native service file, like NetworkManager.service, > and a static symlink, like network-manager.service, > update-rc.d

Bug#924168: jetty9: broken symlink: /usr/share/jetty9/lib/apache-jsp/jdt-core.jar -> ../../../java/ecj.jar

Package: jetty9 Version: 9.4.15-1 Severity: important User: debian...@lists.debian.org Usertags: piuparts Hi, during a test with piuparts I noticed your package ships (or creates) a broken symlink. >From the attached log (scroll to the bottom...): 0m34.1s ERROR: FAIL: Broken symlinks:

Bug#892357: deb-systemd-invoke: if one unit is forbidden by policy-rc.d, all requested units are skipped

Hi Colin, sorry for the late reply Am 08.03.18 um 13:49 schrieb Colin Watson: > Package: init-system-helpers > Version: 1.51 > Severity: normal > > dh_systemd_start generates a deb-systemd-invoke command listing all the > binary package's units. For snapd in Ubuntu, for example, this looks >

Bug#924167: gap-openmath: broken symlink: /usr/share/doc/gap-openmath/README.cds -> ../../gap/pkg/openmath/cds/README

Package: gap-openmath Version: 11.4.2+ds-3 Severity: normal User: debian...@lists.debian.org Usertags: piuparts Hi, during a test with piuparts I noticed your package ships (or creates) a broken symlink. >From the attached log (scroll to the bottom...): 1m11.9s ERROR: FAIL: Broken symlinks:

Bug#924138: unblock: libnet-duo-perl/1.02-1

Control: tag -1 -moreinfo Jonathan Wiltshire writes: > On Sat, Mar 09, 2019 at 12:44:59PM -0800, Russ Allbery wrote: >> * Upload 1.02-1 to unstable and have you unblock that for propagation to >> testing as a regular package update? This is a leaf package, so I'm >> pretty confident that

Bug#918965: adequate tells about broken-symlink in quassel-data

On Sun, 10 Mar 2019 00:52:35 +0100 Andreas Beckmann wrote: > On Fri, 15 Feb 2019 12:52:13 -0500 Scott Kitterman > wrote: > > See the package Suggests. This is intentional. > > There is no package in sid that ships a mpris-quassel binary. Thanks. Looks like I got it mixed up with inxi. I

Bug#639937: Don't tell people to use jigdo

Also when jigdo-lite is asking us questions, it can first mention "don't worry about 404s"

Bug#924166: debram: broken symlink: /usr/share/doc/debram/HISTORY.gz -> ../debram-data/HISTORY.gz

Package: debram Version: 2.1.0 Severity: normal User: debian...@lists.debian.org Usertags: piuparts Control: affects -1 + debram-data Hi, during a test with piuparts I noticed your package ships (or creates) a broken symlink. >From the attached log (scroll to the bottom...): 0m19.7s ERROR:

Bug#639937: Don't tell people to use jigdo

SM> You don't show to the end of the log. Jigdo will switch to grabbing SM> missing files from snapshot.d.o once it has finished with all the SM> files it can find on the mirrors you've told it about. GREAT: BUT: The user will start seeing these 404s interspersed with the 200s and think: "Yup,

Bug#872635: util-linux: FTBFS on armel: test failure

I have had a look at this as part of the Cambridge BSP 2019-03-09 I am able to reproduce this 'bug', on multiple architectures the following is copy/paste from buster on my AMD64 laptop :-p Simply running the test by hand Assuming you have a working / reliable resolver / untainted cache then

Bug#924165: node-xmlhttprequest: broken symlink: /usr/lib/nodejs/xmlhttprequest/index.js -> XMLHttpRequest.js

Package: node-xmlhttprequest Version: 1.8.0-1 Severity: serious User: debian...@lists.debian.org Usertags: piuparts Hi, during a test with piuparts I noticed your package ships (or creates) a broken symlink. >From the attached log (scroll to the bottom...): 0m23.7s ERROR: FAIL: Broken

Bug#924164: Don't say use Jigdo

Package: www.debian.org On https://www.debian.org/CD/jigdo-cd : See my comment at the end of bug #639937. Jigdo will not build 100% correct CDs due to the index files often not being in 100% sync. So please don't recommend it as a way to download Debian CDs. Else one will take such CD to some

Bug#924163: node-libnpx: broken symlink: /usr/lib/nodejs/libnpx/node_modules/npm -> ../../npm

Package: node-libnpx Version: 10.2.0+repack-1 Severity: important User: debian...@lists.debian.org Usertags: piuparts Hi, during a test with piuparts I noticed your package ships (or creates) a broken symlink. >From the attached log (scroll to the bottom...): 0m27.1s ERROR: FAIL: Broken

Bug#639937: Don't tell people to use jigdo

Hi Dan, On Sun, Mar 10, 2019 at 07:52:22AM +0800, 積丹尼 Dan Jacobson wrote: >So jigdo will build defective CDs with missing files, >that one will only discover when one tries to use them? > >Some files will be present, others missing? > >--2019-03-10 07:45:52--

Bug#918965: adequate tells about broken-symlink in quassel-data

On Fri, 15 Feb 2019 12:52:13 -0500 Scott Kitterman wrote: > See the package Suggests. This is intentional. There is no package in sid that ships a mpris-quassel binary. Andreas

Bug#919843: lirc-doc: broken symlinks: /usr/share/doc/lirc/lirc.org/* -> /build/lirc-rOeUaU/lirc-0.10.1/debian/tmp/usr/share/doc/lirc/*

Control: tag -1 + patch pending Dear maintainer, On Sun, Jan 20, 2019 at 04:57:04AM +0100, Andreas Beckmann wrote: > during a test with piuparts I noticed your package ships (or creates) > a broken symlink. Given the lack of answer, I prepared a fixed version, and performed a NMU to DELAYED/3,

Bug#639937: Don't tell people to use jigdo

So jigdo will build defective CDs with missing files, that one will only discover when one tries to use them? Some files will be present, others missing? --2019-03-10 07:45:52--

Bug#922370: libreoffice: Libreoffice duplicated global menu on plasma desktop

Hi !! Sorry for the delay. I was not notified by your answer. The problem still persists. I tried to install a flatpak but the same occurs. > Does the presence of libreoffice-kde5 make a difference (which is > in 6.1.x bascially a disguiseed gtk3 with a kde5 file picker)? I see > below you have

Bug#924162: libodb-api-dev: broken symlinks: /usr/lib//lib{odbemos,odb,Odbmigrator}.so -> lib{odbemos,odb,Odbmigrator}.0d

Package: libodb-api-dev Version: 0.18.1-4 Severity: serious User: debian...@lists.debian.org Usertags: piuparts Hi, during a test with piuparts I noticed your package ships (or creates) a broken symlink. >From the attached log (scroll to the bottom...): 0m45.0s ERROR: FAIL: Broken symlinks:

Bug#924161: unblock: lirc/0.10.1-5.1

Package: release.debian.org Severity: normal User: release.debian@packages.debian.org Usertags: unblock Control: block 919843 by -1 -BEGIN PGP SIGNED MESSAGE- Hash: SHA512 Dear release team, Please unblock package lirc, as I fixed an RC bug. Note that the upload was to DELAYED/3, as

Bug#865999: [exiv2] Please package exiv2 0.26

On Tue, 26 Sep 2017 17:56:57 +0200 Raphael Hertzog wrote: > Except that version 0.26 is vulnerable to multiple security issues which > are currently not present in earlier versions [...] Raphaël, what makes you sure that these CVEs are not present in earlier versions (e.g. in 0.25 currently in

Bug#924160: libjs-markdown-it-html5-embed: broken symlinks: /usr/share/doc/libjs-markdown-it-html5-embed/*.HISTORY.md -> node_modules/*/HISTORY.md

Package: libjs-markdown-it-html5-embed Version: 1.0.0+ds-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 symlink. >From the attached log (scroll to the bottom...): 0m17.6s ERROR: FAIL:

Bug#914006: exiv2: Please package version 0.27

It looks like I forgot one grave bug: #62 (CVE-2018-5772) But that's also fixed in 0.27.0. -richy. -- Richard B. Kreckel

Bug#915706: 9.6.0 DVD and XFCE CD for mipsel are actually netinst

Control: reassign -1 cdimage.debian.org Control: severity -1 important On Thu, Dec 06, 2018 at 05:54:51PM +0800, seam...@debian.org wrote: >Package: debian-installer >Severity: serious > >I tried "debian-9.6.0-mipsel-xfce-CD-1.iso" and >"debian-9.6.0-mipsel-DVD-1.iso" on QEMU and found that both

Bug#924159: android-libcutils-dev: broken symlink: /usr/include/android/cutils/android_filesystem_config.h -> ../private/android_filesystem_config.h

Package: android-libcutils-dev Version: 1:8.1.0+r23-4 Severity: serious User: debian...@lists.debian.org Usertags: piuparts Hi, during a test with piuparts I noticed your package ships (or creates) a broken symlink. >From the attached log (scroll to the bottom...): 0m19.7s ERROR: FAIL: Broken

Bug#686895: initscripts: /forcefsck: fsck -f undefined (e2fsck-ism)

On Sat, 9 Mar 2019, Pierre Ynard wrote: > /fastboot and /forcefsck are created by `shutdown -f` and `shutdown -F` Oh, I didn’t know that, I just sudo touch them as used to on Unix. > the shutdown binary, it could create /forcefsck or /run/forcefsck, which /run is a tmpfs. > would then be

Bug#914006: exiv2: Please package version 0.27

On Sun, 18 Nov 2018 06:47:43 -0500 Jeremy Bicha wrote: > There is a new exiv2 0.27 RC2 tarball release. Could you look into > whether it fixes the security issues from 0.26 and would be acceptable > for unstable? I just went through all Debian bug reports associated with CVEs. As far as I can

Bug#924158: lirc shoud byte-compile its Python modules in postinst

Source: lirc Version: 0.10.1-5 Severity: normal -BEGIN PGP SIGNED MESSAGE- Hash: SHA512 Dear maintainer, Per the Debian Python policy [0], lirc should be automatically byte-compiling its installed Python modules. I'm not sure why it's not done automatically by dh-python in your

Bug#863601: systemd-notify doesn't work because of race condition

Control: forwarded -1 https://github.com/systemd/systemd/issues/2739 On Thu, 1 Jun 2017 17:50:27 +0200 Michael Biebl wrote: > On Mon, 29 May 2017 09:20:52 +0200 > =?UTF-8?B?0JDQvdC00YDQtdC5INCU0L7RhtC10L3QutC+?= > wrote: > > Package: systemd > > Version: 232 > > > > I used unit-file with

Bug#924120: Say "netinst multi-arch CD images"

Well all I know is we think they must be in contrast to the other items listed. > "HW" == Holger Wansing writes: HW> Hi, HW> 積丹尼 Dan Jacobson wrote: >> Package: www.debian.org >> >> On https://www.debian.org/devel/debian-installer/ >> After "Current daily snapshots" say >> "netinst

Bug#924155: icewm-common: broken symlink: /usr/share/doc/icewm-common/FAQ/index.html -> IceWM-FAQ.html

Package: icewm-common Version: 1.4.3.0~pre-20181030-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 symlink. >From the attached log (scroll to the bottom...): 0m42.9s ERROR: FAIL: Broken

Bug#912445: RM: openhft-chronicle-threads/1.1.6-1

Control: clone -1 -2 Control: reassign -2 release.debian.org Control: tags -2 = buster Control: retitle -2 RM: RM: openhft-chronicle-threads/1.1.6-1 On Wed, 31 Oct 2018 18:33:17 +0200 Adrian Bunk wrote: > Source: openhft-chronicle-threads > Version: 1.1.6-1 > Severity: serious > Tags: ftbfs

Bug#893498: RM: openhft-chronicle-wire/1.1.13-1

Control: clone -1 -2 Control: reassign -2 release.debian.org Control: tags -2 = buster Control: retitle -2 RM: openhft-chronicle-wire/1.1.13-1 Please remove openhft-chronicle-wire from testing, I don’t see any chance of us properly solving this for Buster. -- Cheers, Andrej

Bug#915678: gcc-x86-64-linux-gnux32: broken symlink: /usr/share/doc/gcc-x86_64-linux-gnux32 -> cpp-x86_64-linux-gnux32 (gcc-x86-64-linux-gnux32)

Followup-For: Bug #915678 Control: found -1 4:8.3.0-1 Control: found -1 g++-x86-64-linux-gnux32/4:8.3.0-1 Control: affects -1 + g++-x86-64-linux-gnux32 Hi, this invalid symlink is still present in some packages: 0m28.0s ERROR: FAIL: Broken symlinks: /usr/share/doc/g++-x86_64-linux-gnux32 ->

Bug#867590: networkd removes statically set default route when RA expires

Hi Marc On Fri, 07 Jul 2017 17:52:04 +0200 Marc Haber wrote: > Package: systemd > Version: 232-25 > Severity: normal > Tags: ipv6 > > Hi, > > I do have a system with systemd-networkd. IPv6AcceptRA is set to 1, > which is not strictly needed, but I can easily dream up a use case > where this is

Bug#888222: systemd: invalid mount order of btrfs subvolumes after apt upgrade and reboot

Control: tags -1 + moreinfo On Fri, 16 Nov 2018 00:52:56 +0100 Michael Biebl wrote: > Hi > > On Tue, 23 Jan 2018 19:39:29 -0500 "LeJacq, Jean Pierre" > wrote: > > Package: systemd > > Version: 236-3~bpo9+1 This version is rather old, could you please try with v241 and report back Regards,

Bug#920234: systemd: insufficient log options when there is a bad /etc/crypttab entry

On Wed, 23 Jan 2019 11:42:57 +1100 Russell Coker wrote: > Package: systemd > Version: 240-4 > Severity: normal > > When I have a bogus /etc/crypttab entry (for example when converting an > encrypted laptop to a virtual machine that's not encrypted) the boot process > hangs for 90 seconds for no

Bug#920446: tries to rename VLAN interface

Hi Marc On Fri, 25 Jan 2019 17:10:55 +0100 Marc Haber wrote: > Package: systemd > Version: 240-4 > Severity: normal > File: systemd-networkd > > Hi, > > On my desktop computer, I run some VMs and am using systemd-networkd. > The machine has its 'own' network untagged on the ethernet and the VM

Bug#924154: swi-prolog-x: broken symlink: /usr/lib/swi-prolog/xpce.rc -> xpce/pl/xpce.rc

Package: swi-prolog-x Version: 8.0.2+dfsg-1 Severity: important User: debian...@lists.debian.org Usertags: piuparts Hi, during a test with piuparts I noticed your package ships (or creates) a broken symlink. >From the attached log (scroll to the bottom...): 1m11.7s ERROR: FAIL: Broken

Bug#924153: novnc: broken symlink: /usr/share/novnc/include/web-socket-js-project/swfobject.js -> ../../../javascript/swfobject/swfobject.js

Package: novnc Version: 1:1.0.0-1 Severity: important User: debian...@lists.debian.org Usertags: piuparts Hi, during a test with piuparts I noticed your package ships (or creates) a broken symlink. >From the attached log (scroll to the bottom...): 0m33.6s ERROR: FAIL: Broken symlinks:

Bug#924129: debian-installer: Kernel for armhf for stretch unbootable

On 2019-03-09, Cyril Brulebois wrote: > Peter Lebbing (2019-03-09): >> Debian kernel bug #922478 renders armhf systems unbootable. This bug was >> fixed, but the debian-installer images still use (I presume) kernel >> version 4.9.144-3, the unbootable version. I noticed this today while >> trying

Bug#924152: node-cacache: broken symlink: /usr/share/doc/node-cacache/figgy-pudding.CHANGELOG.md -> ../figgy-pudding/CHANGELOG.md

Package: node-cacache Version: 11.3.2-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 symlink. >From the attached log (scroll to the bottom...): 0m22.3s ERROR: FAIL: Broken symlinks:

Bug#923037: Acknowledgement (Please package new upstream version 2.5.x, or from git)

I needed to use a newer version of this library myself. I didn't have time to do a proper update but I did manage to produce a thing that builds. It is Really Not Very Good. But I thought I would share the horrible thing I did anyway. It can be found here:

Bug#924151: grub2-common: wrong grub.cfg for efi boot and fully encrypted disk

Package: grub2-common Version: 2.02+dfsg1-11 Severity: grave Dear Maintainer, I'm unsure about the severity, so feel free to adjust it. But it did make my system unbootable twice already, and as its a setup one can get directly from within debian-installer, it would be nice if it can be fixed

Bug#923678: [Pkg-javascript-devel] Bug#923678: libjs-leaflet-markercluster: not a transitional package for apt

control: reassign -1 ftp.debian.org control: retitle -1 libjs-leaflet-markercluster: section field out of sync Quoting Thorsten Glaser (2019-03-03 19:21:42) > When removing the libjs-leaflet-markercluster “transitional” package, > apt also clears the new one for removal: [...] > This is because

Bug#923674: systemd: test-stat-util fails with SIGABRT when /dev/random is bind-mounted from /dev/urandom

> from those references: > "You should consider adding more entropy rather than compromising your > system." > or > "One simple way (which I don't really suggest)" Oh, sure, and maybe also "only do it if you know what you are doing". I'm using sbuild, and the bind-mount is only performed in the

Bug#882473: ruby-httpclient FTBFS and Debci failure: test_verification_without_httpclient fails

Hi, > ruby-httpclient FTBFS and Debci failure: test_verification_without_httpclient > fails This is likely another OpenSSL 1.1 incompatibility wrt. SHA1 signatures. Regards, -- ,''`. : :' : Chris Lamb `. `'` la...@debian.org / chris-lamb.co.uk `-

Bug#924138: unblock: libnet-duo-perl/1.02-1

Control: tag -1 moreinfo Hi, On Sat, Mar 09, 2019 at 12:44:59PM -0800, Russ Allbery wrote: > * Upload 1.02-1 to unstable and have you unblock that for propagation to > testing as a regular package update? This is a leaf package, so I'm > pretty confident that this should be safe, but it has

Bug#918309: sphinxcontrib-programoutput: Please update to v0.13 that is compatible with Sphinx 1.8

tags 918309 + pending patch thanks I've uploaded sphinxcontrib-programoutput 0.11-3.1 to DELAYED/5: sphinxcontrib-programoutput (0.11-3.1) unstable; urgency=medium * Non-maintainer upload. * Fix FTBFS with Sphinx 1.8 by backporting patch from upstream. (Closes: #918309) The

Bug#923674: systemd: test-stat-util fails with SIGABRT when /dev/random is bind-mounted from /dev/urandom

Am 09.03.19 um 23:20 schrieb Santiago Vila: > On Sat, Mar 09, 2019 at 11:08:15PM +0100, Michael Biebl wrote: >> Am 09.03.19 um 23:00 schrieb Santiago Vila: >>> The reason I would still consider this as a bug (with whatever severity >>> you like) is that symlinking /dev/random to /dev/urandom is a

Bug#890075: ruby-http ftbfs (test failures with 2.5)

notfound 890075 3.3.0-2 thanks Emanuele Rocca wrote: > Note that the bug is not reproducible with ruby-http 3.3.0-2 as tests > have been disabled Therefore marking in the BTS to match. Regards, -- ,''`. : :' : Chris Lamb `. `'` la...@debian.org  chris-lamb.co.uk

Bug#923674: systemd: FTBFS (failing tests)

Am 09.03.19 um 22:43 schrieb Michael Biebl: > Am 09.03.19 um 22:27 schrieb Santiago Vila: >> On Sat, Mar 09, 2019 at 09:59:16PM +0100, Michael Biebl wrote: >>> Am 09.03.19 um 21:50 schrieb Michael Biebl: Am 09.03.19 um 21:00 schrieb Santiago Vila: > to which I also add these two lines:

Bug#924129: debian-installer: Kernel for armhf for stretch unbootable

Hi Peter, Peter Lebbing (2019-03-09): > Package: debian-installer > Version: 20170615+deb9u5+b2 > Severity: grave > Justification: renders package unusable > > Dear maintainers, > > Debian kernel bug #922478 renders armhf systems unbootable. This bug was > fixed, but the debian-installer

Bug#924128: prokka: creates world writable directory tree /var/lib/prokka/*

Control: severity -1 normal On Sat, Mar 09, 2019 at 08:24:46PM +0100, Andreas Beckmann wrote: > > during a test with piuparts I noticed your package creates a world > writable directory tree. > > >From the attached log (scroll to the bottom...): > > 0m49.9s ERROR: Command failed (status=1):

Bug#923674: systemd: test-stat-util fails with SIGABRT when /dev/random is bind-mounted from /dev/urandom

I confirm that dropping the /dev/urandom line from /etc/schroot/default/fstab makes the package to build again. Now I fear that crypto packages with random-intensive test suites start to FTBFS again... Thanks.

Bug#918309: sphinxcontrib-programoutput: Please update to v0.13 that is compatible with Sphinx 1.8

tags 918309 + patch thanks Patch attached. Regards, -- ,''`. : :' : Chris Lamb `. `'` la...@debian.org / chris-lamb.co.uk `- diff --git a/src/sphinxcontrib/programoutput/__init__.py b/src/sphinxcontrib/programoutput/__init__.py index 7eb1c5d..824c045 100644

Bug#923637: Bug#923637: 923637 is pending

Hi Andrius, thanks a lot for the fix. On Sat, Mar 09, 2019 at 07:37:19PM +0200, Andrius Merkys wrote: > It must be an overlook. I will fix it today/tomorrow. Please don't. > On Sat, 9 Mar 2019, 19:26 Olivier Sallou, wrote: > > > there is a remaining warning: > > > > W: libffindex0:

Bug#923674: systemd: test-stat-util fails with SIGABRT when /dev/random is bind-mounted from /dev/urandom

On Sat, Mar 09, 2019 at 11:08:15PM +0100, Michael Biebl wrote: > Am 09.03.19 um 23:00 schrieb Santiago Vila: > > The reason I would still consider this as a bug (with whatever severity > > you like) is that symlinking /dev/random to /dev/urandom is a common > > workaround for lack of entropy,

Bug#913765: RM: leafpad -- GTK+ based simple text editor

Control: reassign -1 release.debian.org Control: retitle -1 RM: leafpad -- GTK+ based simple text editor On Thu, 10 Jan 2019 14:31:56 +0100 Andrej Shadura wrote: > On Wed, 14 Nov 2018 22:44:08 +0100 krystal wrote: > > This needs love or it will die. Needs to be updated to use gtk3, has at > >

Bug#924150: stretch-pu: package libdate-holidays-de-perl/1.9-1+deb9u3

Package: release.debian.org Severity: normal Tags: stretch User: release.debian@packages.debian.org Usertags: pu As I wrote in #902042: > FWIW, there are currently no further plans to change holidays in > Germany, so this is hopefully the last update for a long time. This did not hold. So

Bug#923674: systemd: test-stat-util fails with SIGABRT when /dev/random is bind-mounted from /dev/urandom

Am 09.03.19 um 23:00 schrieb Santiago Vila: > The reason I would still consider this as a bug (with whatever severity > you like) is that symlinking /dev/random to /dev/urandom is a common > workaround for lack of entropy, which in turn has traditionally been a > common problem for anybody who

Bug#924147: geeqie-common: Please add Multi-Arch: foreign

retitle 924147 geeqie-common: Please add Multi-Arch: foreign thanks Ups. I used an old request as a template and missed to fixup the Subject. Cheers Elrond

Bug#878590: systemd: jessie to stretch upgrade resulted in eth0 being given a new style predictable name (enp1s9)

Hi Phil On Sat, 14 Oct 2017 21:56:40 +0100 Philip Hands wrote: > Package: systemd > Version: 232-25+deb9u1 > Severity: important > > Hi, > > After upgrading to Stretch, the system came up with its NIC named as > enp1s9, and thus had no working network (since eth0 was configured > in

Bug#923481: alpine: replies lose In-Reply-To and References headers

Howdy, As I understand it, this is not a regression in alpine but a difference in how pine and alpine function, correct? ~Unit 193 Unit193 @ freenode Unit193 @ OFTC

Bug#923674: systemd: test-stat-util fails with SIGABRT when /dev/random is bind-mounted from /dev/urandom

retitle 923674 systemd: test-stat-util fails with SIGABRT when /dev/random is bind-mounted from /dev/urandom severity 923674 normal thanks Sorry for this false positive. I think this retitle reflects much better the issue. The reason I would still consider this as a bug (with whatever severity

Bug#924148: unblock: python-dmidecode/3.12.2-9

Package: release.debian.org Severity: normal User: release.debian@packages.debian.org Usertags: unblock Please unblock package python-dmidecode this reverts completely the attempt to migrate to use symlinks for the doc directory of the -dbg packages; i've wasted enough time on something that

Bug#686895: initscripts: /forcefsck: fsck -f undefined (e2fsck-ism)

> > As you convincingly remarked below, we may want honor `test -f /forcecheck' > > for every filesystem, whose `fsck' supports `-f' option. As far as I > > follow the thread, it is: > > > > ext2 ext3 ext4 reiserfs > > Interesting that acceptance of that parameter is so low. fsck.minix

Bug#924149: RFP: py-spy -- sampling profiler for Python programs

Package: wnpp Severity: wishlist * Package name: py-spy Version : 0.1.10 Upstream Author : Ben Frederickson * URL : https://github.com/benfred/py-spy * License : GPLv3 Programming Lang: Rust Description : sampling profiler for Python programs Py-Spy

Bug#923674: systemd: FTBFS (failing tests)

Am 09.03.19 um 22:27 schrieb Santiago Vila: > On Sat, Mar 09, 2019 at 09:59:16PM +0100, Michael Biebl wrote: >> Am 09.03.19 um 21:50 schrieb Michael Biebl: >>> Am 09.03.19 um 21:00 schrieb Santiago Vila: to which I also add these two lines: >>> ..> /dev/urandom/dev/random none

Bug#924147: gnucash-common: Please add Multi-Arch: foreign

Package: geeqie-common Version: 1:1.4+git20190121-2 Severity: wishlist User: multiarch-de...@lists.alioth.debian.org Usertags: multiarch Hi, It looks like geeqie-common offers an architecture independent (data level) interface to its users. Would you mind setting it to Multi-Arch: foreign? It's

Bug#712023: initscripts: wait for child to exit during shutdown/reboot

tags 712023 moreinfo thanks > I have made a script to readout the vm's that are running and save > there state one by one. This takes some time. At the beginning no vm > was saved right. I did some tunning with the scripts and have now 5-10 > sec's before the other vboxservices are terminated. So

Bug#923674: systemd: FTBFS (failing tests)

On Sat, Mar 09, 2019 at 09:59:16PM +0100, Michael Biebl wrote: > Am 09.03.19 um 21:50 schrieb Michael Biebl: > > Am 09.03.19 um 21:00 schrieb Santiago Vila: > >> to which I also add these two lines: > > ..> /dev/urandom/dev/random nonerw,bind 0 0 > > > > This might very

  1   2   3   4   >