Bug#900045: mirrors: security.debian.org sometimes inaccessible via ipv6

Package: mirrors Tags: ipv6 Dear Maintainer, On ipv6 only machines, apt-get update sometimes fails, because security.debian.org sometimes redirects to prod.debian.fastly.net which has an advertised ipv6 address, but does not serve debian packages from that address. Peter C -- System

Bug#899036: libgit2 0.27 transition

On Mon, May 21, 2018 at 10:46:48PM +0530, Pirate Praveen wrote: > Control: clone -1 -2 > Control: reassign -2 libgit2-dev > Control: retitle -2 libgit2.pc requires openssl even though we use > mbedtls now > Control: found -2 0.27.0+dfsg.1-0.1 > > On Mon, 21 May 2018 22:33:43 +0530 Pirate Praveen

Bug#898566: transition: gdal

On 05/24/2018 09:44 PM, Sebastiaan Couwenberg wrote: > On 05/24/2018 06:26 PM, Emilio Pozuelo Monfort wrote: >> On 23/05/18 07:15, Sebastiaan Couwenberg wrote: >>> On 05/22/2018 10:19 PM, Emilio Pozuelo Monfort wrote: On 22/05/18 18:10, Sebastiaan Couwenberg wrote: > On 05/18/2018 02:49

Bug#899424: Cannot claim guest account

On Thu, May 24, 2018 12:06:09 +0200, Mattia Rizzolo wrote: > On Thu, May 24, 2018 at 06:55:20AM +0200, Xavier Guimard wrote: > > I'm DM for a long time (before alioth). I recently tried to associate > > my SSO account with my nm.debian.org identity: > > - find person returns only one entry > > -

Bug#900008: kid3 FTCBFS: multiple reasons

Could you please check if the cross build failure still exists with version 3.6.1? I implemented a workaround for the GetPrerequistes bug in response to bug report https://sourceforge.net/p/kid3/bugs/173/, so this should be fixed. Urs

Bug#899422:

Control: found -1 lvm2/2.02.111-2.2+deb8u1 Control: found -1 lvm2/2.02.176-4.1 -- The behavior with Jessie is the same as that with Stretch. So something changed between Wheezy and Jessie which doesn't allow reversing -lpcre and -lpthread.

Bug#899418:

Control: found -1 lvm2/2.02.168-2

Bug#900044: peruse: Failed to load the component from disk: QtQuick.Dialogs is not installed

Package: peruse Version: 1.2+dfsg-2 Severity: important Dear Maintainer, I installed peruse on buster with `apt install peruse`, and on my first attempt to run it I am greeted with a fantastic: Failed to load the component from disk. Reported error was:

Bug#899418:

Control: found -1 lvm2/2.02.111-2.2+deb8u1 Control: found -1 lvm2/2.02.176-4.1 -- Not sure whether bug needs to be reported as found for each version.

Bug#899430: appstream: recommends 'CC-0-1.0', but complains anyway if used. 'CC0-1.0' is fine.

2018-05-24 8:39 GMT+02:00 Andreas B. Mundt : > Package: appstream > Version: 0.12.0-3 > Severity: minor > > Dear Maintainer, > > when verifying a .metainfo.xml with > >appstreamcli validate .metainfo.xml > > I get the complain: > >… Please license the data under

Bug#900043: dt2dv.1: Some formatting fixes in the manual

Package: texlive-binaries Version: 2018.20180416.47457-3+b1 Severity: minor Tags: patch Dear Maintainer, * What led up to the situation? Warning from "groff": :60 (macro IR): only 1 argument, but more are expected Output is from: test-groff -b -e -mandoc -T utf8 -rF0 -t -w w -z

Bug#899422: bug exists since Wheezy

Control: found -1 lvm2/2.02.95-8 -- The bug exists in the source since Wheezy. From what I can tell, the targets dmsetup.static and lvm.static in tools/Makefile.in are the only ones that need to be modified. Depending on the source version the following fixes work: Wheezy: dmsetup.static and

Bug#900042: evince: AppArmor profile denies access to temporary directory

Package: evince Version: 3.28.2-1 Severity: normal -BEGIN PGP SIGNED MESSAGE- Hash: SHA512 I found this in my kernel log after apparmor-notify caught my attention, which I'm reporting because the profile is enforced by default. apparmor="DENIED" operation="open"

Bug#899392: darcs: FTBFS: unsatisfied build-deps: - libghc-graphviz-dev:amd64 (< 2999.19)

Please update darcs to build with graphviz 2999.20.0.0. On Wed, May 23, 2018 at 07:08:14PM +0200, Emilio Pozuelo Monfort wrote: > darcs can't be built anymore on sid: > > darcs build-depends on missing: > - libghc-graphviz-dev:amd64 (< 2999.19)

Bug#899785: exe-thumbnailer: Invalid maintainer address pkg-wine-pa...@lists.alioth.debian.org

Control: tags 899785 + pending Hello, This will be fixed in the next release (0.10.0-3), which is currently staged in Salsa at https://salsa.debian.org/jlu-guest/exe-thumbnailer (I've pinged my usual sponsor about it already) Best, James On 2018-05-24 12:43 AM, Christoph Biedl wrote: >

Bug#900041: RFS: impacket/0.9.15-5 [ITA]

Package: sponsorship-requests Severity: normal Dear mentors, I am looking for a sponsor for my package "impacket" * Package name: impacket Version : 0.9.15-5 Upstream Author : Alberto Solino * URL : https://pypi.org/project/impacket/ * License

Bug#900040: dpkg-trigger.1: Some formatting fixes in the manual

Package: dpkg Version: 1.19.0.5+b1 Severity: minor Tags: patch Dear Maintainer, * What led up to the situation? Warnings from "groff": :44 (macro BR): only 1 argument, but more are expected :62 (macro BR): only 1 argument, but more are expected :68 (macro BR): only 1 argument, but more

Bug#900039: freetype: Building with apt-build fails with error in /src/sfnt/ttcmap.c

Source: freetype Version: 2.8.1 Severity: serious Justification: fails to build from source (but built successfully in the past) Dear Maintainer, I initiated an adopted build of package in question with folowing commandline: apt-build -t testing --build-only install freetype All went fine,

Bug#900038: Fonts degraded

Package: josm Version: 0.0.svn13710+dfsg-1 Severity: important J> Ticket URL: J> Closed as duplicate of #12085.[[BR]]This a Debian package and using noto J> fonts which are know to have issues in low zoom. See #12085. I'd suggest J> to

Bug#900037: autopkgtest failure due to incorrect format

Package: node-abstract-leveldown Version: 2.4.1-1 Tags: patch autopkgtest is failing on this package due to the test requiring '"abstract-leveldown"' instead of 'abstract-leveldown'. I've attached a patch that fixes this issue. Alternatively, you can see my patch on Salsa:

Bug#900036: firmware-nonfree: Buster kernel needs updated (upstream) firmware versions

X-Debbugs-Cc: ge...@infradead.org Package: firmware-nonfree Version: 20170823-1 Severity: grave Tags: d-i Justification: renders package unusable The current firmware-nonfree package is out of date and does not include firmware files the drivers in the Buster kernel require. Specifically, the

Bug#899418:

Control: found -1 lvm2/2.02.95-8

Bug#900035: dpkg-split.1: Some formatting fixes in the manual

Package: dpkg Version: 1.19.0.5+b1 Severity: minor Tags: patch Dear Maintainer, * What led up to the situation? Warning from "groff": :148 (macro BR): only 1 argument, but more are expected :181 (macro BR): only 1 argument, but more are expected Output is from: test-groff -b -e -mandoc

Bug#899418: bug exists since Wheezy

Control: found -1 src:lvm2/2.02.95-8 -- I compiled the source from the Wheezy repo and ,as expected, the bug exists. Please fix soon since Wheezy LTS is ending this month. Thanks.

Bug#900034: libtickit: Please pass compiler flags to testsuite build

Package: libtickit Version: 0.2-3 Severity: minor Tags: patch User: ubuntu-de...@lists.ubuntu.com Usertags: origin-ubuntu cosmic ubuntu-patch Hi James, Thanks for the fix to bug #895268. We are carrying another additional patch in Ubuntu which I apparently failed to forward previously. The

Bug#900033: dpkg-deb.1: Some fixes in the manual

Package: dpkg Version: 1.19.0.5+b1 Severity: minor Tags: patch Dear Maintainer, * What led up to the situation? Warnings from "groff": :133 (macro IR): only 1 argument, but more are expected :210 (macro BR): only 1 argument, but more are expected :279 (macro BR): only 1 argument, but more

Bug#899318: virtualbox: FTBFS: vboxssdt-standard.hex:16:23: error: expected initializer before '-' token

On Thu, May 24, 2018 at 06:33:45AM +0900, Mattia Dongili wrote: > On Wed, May 23, 2018 at 02:56:55PM +0200, Gianfranco Costamagna wrote: > > control: reassign -1 src:acpica-unix > > control: found -1 20180508-1 > > control: affects -1 virtualbox > > > > On Tue, 22 May 2018 19:12:32 +0200 Emilio

Bug#900032: mocha: missing-copyright-file /usr/share/doc/mocha/copyright

Package: mocha Version: 4.1.0+ds1-1 Severity: serious Justification: Policy 12.5 Adequate reports: mocha: missing-copyright-file /usr/share/doc/mocha/copyright And adequate is right, as /usr/share/doc/mocha/ is empty. -- System Information: Debian Release: buster/sid APT prefers unreleased

Bug#899154: Acknowledgement (console switching broken on Polaris11 hardware with amdgpu.dc=1)

Aha! The problem goes away when upgrading to Xorg 1.20.

Bug#900031: linux-image-4.9.0-6-amd64: task blocked for more than 120 seconds

Package: src:linux Version: 4.9.88-1+deb9u1 Severity: important Dear Maintainer, Sorry, this may not be a complete bug report, but I am happy to supply you with required information in a timely manner. On 2018-5-8, I rebooted into 4.9.0-6, and observed various hangs since:

Bug#899176: mkdocs-bootstrap: Please update to version 0.2.0 that is compatible with mkdocs 0.17

Dmitry Shachnev writes: > mkdocs uses mkdocs-bootswatch if this theme is specified in mkdocs.yml file. > > None of the Debian packages currently use this, but third-party software > may use it, that’s why I added Breaks. > > It is not critical so I can remove this Breaks for

Bug#873081: Solution for this bug

Hi, Sorry for requesting support on a bug tracker, but I got affected by this too. Is there a guide on how to solve this corruption? Thank you, Alex

Bug#895020: Pre-configure desktop-autoloader appropriately for Debian Edu LTSP fat client

On Thu, May 24, 2018 at 09:40:12AM +, Mike Gabriel wrote: > @Wolfgang: did you get a chance to test desktop-autoloader with GNOME and > KDE? Both DEs tested now in a virtual world, both working ok; esp. speeds up KDE (otherwise uncredibly slow compared to Xfce). I figure desktop-autoloader

Bug#900030: RM: pyelliptic -- RoQA; orphaned, abandoned upstream, won't be ported to OpenSSL 1.1

Package: ftp.debian.org Severity: normal Package is orphaned for over a year, is RC-buggy for OpenSSL 1.1 and upstream stated it won't get ported (https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=882561#12) There's no reverse deps, so let's remove it. Cheers, Moritz

Bug#900009: libXm causes the GUI to crash

Hi Paul, I have installed libxm4-dbgsym_2.3.4-13_amd64.deb and the core dump back trace looks like below: Using host libthread_db library "/lib/x86_64-linux-gnu/libthread_db.so.1". Core was generated by `O.linux-x86_64/medm'. Program terminated with signal SIGABRT, Aborted. #0 __GI_raise

Bug#899152: FTBFS: ipmi.h:85:2: error: unknown type name 'selector_t'

Sorry for bringing in all of the old conversations into the bug. This looks like a openipmi bug to me. As Juhani mentioned to avoid the name space collisions openipmi introduced the following line selector.h #ifdef OPENIPMI_DEFINE_SELECTOR_T which is not defined earlier and it is not defined

Bug#899152: FTBFS: ipmi.h:85:2: error: unknown type name 'selector_t'

This looks like a bug to me. As Juhani mentioned to avoid the name space collisions openipmi introduced the following line selector.h #ifdef OPENIPMI_DEFINE_SELECTOR_T which is not defined earlier and it is not defined in openhpi. Instead of #ifdef they need to use #ifndef so that older code

Bug#887536: dh-make-perl depends on libemail-address-perl

On Thu, 24 May 2018 19:30:01 +, Damyan Ivanov wrote: > > I created patch with these changes, but I'm not sure if it is correct > > due to fact that I do not know what that code should do. So it would be > > needed to properly test these changes. > > > > Anyway, do you really need to parse

Bug#900029: yui-compressor: Change README.gz link to README.md

Package: yui-compressor Version: 2.4.8-2 Severity: minor Hello, yui-compressor manpage has a SEE_ALSO parapraph that points to /usr/share/doc/yui-compressor/README.gz but this file no more exists. Please change this link to /usr/share/doc/yui-compressor/README.md Regards, Xavier -- System

Bug#896577: mysql-workbench: FTBFS with GDAL 2.3.0 (-Werror=deprecated-declarations)

Control: severity -1 serious On 04/22/2018 05:00 PM, Bas Couwenberg wrote: > You may want to add -Wno-error=deprecated-declarations to the > buildflags, as per the attached patch, to work around this issue > until upstream has added compatibility with the new GDAL. > > The severity of the issue

Bug#900028: Acknowledgement (unbound: Fails to start)

I tried running it with strace(8) and got this: sendto(9, "<29>May 24 20:17:10 unbound: [10"..., 70, MSG_NOSIGNAL, NULL, 0) = 70 getpid()= 10144 getpid()= 10144 getrandom(0x7fff9321c450, 40, 0)= -1 ENOSYS (Function not

Bug#889027: quodlibet git is in salsa now

On Tue, May 22, 2018 at 08:59:26PM +0200, W. Martin Borgert wrote: > On 2018-04-23 23:55, W. Martin Borgert wrote: >> On 2018-04-22 12:48, Ondřej Kuzník wrote: >> > Would you be able to get the salsa repository created? >> >> https://salsa.debian.org/python-team/applications/quodlibet > > Would

Bug#900027: vlc: VLC doesn't parse arguments properly

Control: tags -1 + moreinfo On 2018-05-24 22:05:56, Cyrille wrote: > Package: src:vlc > Version: 3.0.2-1+b1 > Severity: normal > > Dear Maintainer, > > VLC doesn't parse arguments properly. > > How to reproduce? > > Create a shell script with the following content: > > #!/bin/sh > > # start

Bug#900028: unbound: Fails to start

Package: unbound Version: 1.7.1-1 Severity: important ** I'm reporting this on a different machine that on which it occurs. ** On several -- but not all -- of my kvm instances, unbound 1.7.1-1 fails to start. I tried manually invoking start-stop-daemon via: :; (start-stop-daemon --start

Bug#900025: Acknowledgement (/usr/lib/x86_64-linux-gnu/libm.so: invalid ELF header)

This is what I find on my box: /lib/i386-linux-gnu/libm.so.6: symbolic link to libm-2.27.so /lib/x86_64-linux-gnu/libm.so.6: symbolic link to libm-2.27.so /lib32/libm.so.6: symbolic link to libm-2.27.so /libx32/libm.so.6: symbolic link to libm-2.27.so

Bug#900027: vlc: VLC doesn't parse arguments properly

Package: src:vlc Version: 3.0.2-1+b1 Severity: normal Dear Maintainer, VLC doesn't parse arguments properly. How to reproduce? Create a shell script with the following content: #!/bin/sh # start VLC /usr/bin/cvlc -vvv \ screen:// :screen-fps=30 \ --canvas-width=1280

Bug#900026: knot-resolver: FTBFS on hurd-i386 due to missing MAXPATHLEN

Package: src:knot-resolver Control: forwarded -1 https://gitlab.labs.nic.cz/knot/knot-resolver/issues/347 Control: tags -1 + upstream help As noted in the upstream bug report, knot-resolver fails to build on hurd due to a missing definition of MAXPATHLEN: daemon/engine.c: In function

Bug#898566: transition: gdal

On 05/24/2018 06:26 PM, Emilio Pozuelo Monfort wrote: > On 23/05/18 07:15, Sebastiaan Couwenberg wrote: >> On 05/22/2018 10:19 PM, Emilio Pozuelo Monfort wrote: >>> On 22/05/18 18:10, Sebastiaan Couwenberg wrote: On 05/18/2018 02:49 PM, Emilio Pozuelo Monfort wrote: > On 13/05/18 18:48,

Bug#551400: [Pkg-pascal-devel] Bug#551400: fpc on kfreebsd-i386

Hi, On 15-04-18 12:02, Abou Al Montacir wrote: > It seems that kfreebasd-* resisted to the vague of architectures drop in > Debian and is still there. > > How shall we proceed with this ticket? I propose we close it and remove any left over patches we have (if any). We can always resurrect them

Bug#887536: dh-make-perl depends on libemail-address-perl

-=| Pali Rohár, 19.05.2018 18:18:03 +0200 |=- > On Saturday 19 May 2018 15:28:14 gregor herrmann wrote: > > On Wed, 17 Jan 2018 20:50:05 +0100, Pali Rohár wrote: > > > > > Hi! Package dh-make-perl depends on libemail-address-perl which is > > > vulnerable to CVE-2015-7686, see bug #868170.

Bug#898320: Some progress

I became beta tester on android side and got 1.9 but no chnage. Said to work with oreo. Compiled upstream git using debian build directory from official 1.3.0 : no change. But I noticed someting : 1) Linux PC do see Linux PC on the network (wired/wireless no matter), 2) android

Bug#900025: /usr/lib/x86_64-linux-gnu/libm.so: invalid ELF header

Package: libc6-dev Version: 2.27-3 Severity: normal Not sure if this should be filed against simple-scan. In that case feel free to reassign. simple-scan: common/utils.c 188: unable to load library libm.so: /usr/lib/x86_64-linux-gnu/libm.so: invalid ELF header Adn these are the contents of

Bug#900024: ccze FTCBFS: configure pollutes CC

Source: ccze Version: 0.2.1-4 Severity: minor Tags: upstream User: helmutg Usertags: rebootstrap ccze fails to cross build from source, because ./configure pollutes the CC variable right before checking for a compiler. The attached patch fixes that part, but doesn't make ccze cross buildable,

Bug#899355: ifupdown: Hotplugging IPoIB devices does not work

On Thu, May 24, 2018 at 06:16:46PM +0200, Benjamin Drung wrote: > Is there a reason not to bring up all the allow-hotplug VLANs related > to the physical device, i.e. bring up ib0. if `ifup --allow=hotplug > ib0` is called? Yes, it would change the behaviour of ifupdown, and I know for

Bug#897463: Processed: severity of 897463 is normal

On Thu, May 24, 2018 at 08:49:07PM +0200, Georg Faerber wrote: > Hope this helps, it does, thanks. "important" seems to be the better severity indeed. -- cheers, Holger signature.asc Description: PGP signature

Bug#900023: minisat2 should default to verbose build logs

Source: minisat2 Version: 1:2.2.1-5 Tags: patch User: helm...@debian.org Usertags: rebootstrap The minisat2 build hides compiler invocations by default. That breaks inspecting the build logs with blhc and it also makes diagnosing cross build failures unnecessarily hard. The attached patch makes

Bug#900022: stop shouldn't unconditionally fail if FLUSH_ON_STOP=0

Package: netfilter-persistent Version: 1.0.4+nmu2 Severity: normal Tags: patch Currently, if FLUSH_ON_STOP=0 then /usr/sbin/netfilter-persistent stop exits with code 1. Since systemd runs this on stopping netfilter-persistent, the unit goes into a failed state. That causes anything that depends

Bug#804858: --list-boots: Failed to determine boots: No data available

It is probably this systemd bug: https://github.com/systemd/systemd/issues/4088 Not clear from the issue nor from the pull request in which version is was finally fixed though.

Bug#899382: qt5-qmake: cross wrapper should supply PKG_CONFIG_EXECUTABLE

On Thu, May 24, 2018 at 06:03:54AM +0200, Helmut Grohne wrote: > > Our triplet-prefixed qmake is a wrapper that calls the native qmake with > > some arguments. If we configure qmake with prefixed pkg-config path, then > > the native qmake will call pkg-config corresponding to *its* (native) > >

Bug#900021: untex FTCBFS: uses the build architecture compiler

Source: untex Version: 1:1.2-6 Tags: patch User: helm...@debian.org Usertags: rebootstrap untex fails to cross build from source, because it uses the build architecture compiler as a makefile default $(CC). Including dpkg's buildtools.mk fixes that. Please consider applying the attached patch to

Bug#897463: Processed: severity of 897463 is normal

Hi, On 18-05-24 18:05:50, Holger Levsen wrote: > On Thu, May 24, 2018 at 05:33:06PM +, Debian Bug Tracking System wrote: > > > severity 897463 normal > > Bug #897463 [src:schleuder] schleuder: FTBFS: ERROR: Test "ruby2.5" failed: > > Failure/Error:

Bug#900020: intltool: create m4 folder when it doesn't exist

Package: intltool Version: 0.51.0-5 Severity: important Hi, some package/tarballs don't have the m4 dir created. With dh10 running autoreconf, intltoolize is running as well, and if there is no m4 folder already, the build fails. It's possible to add mkdir -p m4 as part of autoreconf, but it

Bug#900019: pokerth FTCBFS: hard codes the build architecture qmake

Source: pokerth Version: 1.1.1-7.1 Tags: patch upstream User: helm...@debian.org Usertags: rebootstrap pokerth fails to cross build from source, because the upstream build system hard codes the build architecture qmake rather than using $$QMAKE_QMAKE in a few places. The attached patch fixes them

Bug#897463: Processed: severity of 897463 is normal

On Thu, May 24, 2018 at 05:33:06PM +, Debian Bug Tracking System wrote: > > severity 897463 normal > Bug #897463 [src:schleuder] schleuder: FTBFS: ERROR: Test "ruby2.5" failed: > Failure/Error: expect(Mail::TestMailer.deliveries.length).to eq 1 > Severity set to 'normal' from 'serious'

Bug#899176: mkdocs-bootstrap: Please update to version 0.2.0 that is compatible with mkdocs 0.17

On Thu, May 24, 2018 at 08:33:47AM +1000, Brian May wrote: > > The fixed version won’t reach testing *first* because I have added > > Breaks: mkdocs-bootswatch (<< 0.5) to it. > > What is the reason for this? Does mkdocs still try to use > mkdocs-bootswatch if it is availabe? mkdocs uses

Bug#900016: scite FTCBFS: uses the build architecture toolchain

Thanks Helmut, I applied the patch in git. The change will be available with the next release kind regards -- Antonio Valentino

Bug#865758: closed by Miriam Ruiz <mir...@debian.org> (Bug#865758: fixed in xmlindent 0.2.17-5)

Control: reopen -1 On Tue, May 22, 2018 at 01:39:09PM +, Debian Bug Tracking System wrote: > - Allow substituting gcc. This part hasn't been applied. The Makefile still hard codes gcc. xmlindent still fails to cross build. Helmut

Bug#900015: missing pkg-config support is blocking switch to mbedTLS in libgit2

Control: retitle -1 libmbedtls-dev: add pkg-config support Control: severity -1 wishlist Control: tags -1 upstream Hi, On Thu, 24 May 2018 22:43:28 +0530 Pirate Praveen wrote: > Package: mbedtls-dev > version: 2.8.0-1 > Severity: important > Control: forwarded -1

Bug#900018: FTBFS with latest cmdliner

Package: opam Version: 1.2.2-6+b1 Severity: serious opam fails to build from source using latest cmdliner which was uploaded to Debian/Sid a few days ago: File "client/opamArg.ml", line 384, characters 25-29: Error: This expression has type ?docv:string -> (string -> ('a, [

Bug#899806: sysvinit: Invalid maintainer address pkg-sysvinit-de...@lists.alioth.debian.org

Christoph Biedl writes ("Bug#899806: sysvinit: Invalid maintainer address pkg-sysvinit-de...@lists.alioth.debian.org"): > pkg-sysvinit-de...@lists.alioth.debian.org used in the Maintainer: It turns out that I was subscribed to sysvinit via the package tracker, not via the alioth list which was

Bug#900017: fil-plugins FTCBFS: upstream build system hard codes build architecture compiler g++

Source: fil-plugins Version: 0.3.0-6 Tags: patch upstream User: helm...@debian.org Usertags: rebootstrap fil-plugins fails to cross build from source, because the uptsream build system hard codes the build architecture compiler g++. After making it substitutable, fil-plugins cross builds

Bug#899035: libgit2 0.27 transition

On Sat, 19 May 2018 10:37:53 +0530 Pirate Praveen wrote: On May 18, 2018 11:50:35 PM GMT+05:30, Simon McVittie wrote: >Have you tried building reverse-dependencies like gitg against the >new libgit2? I wanted to give a heads up earlier. I will

Bug#900016: scite FTCBFS: uses the build architecture toolchain

Source: scite Version: 4.0.5-1 Tags: patch User: helm...@debian.org Usertags: rebootstrap scite fails to cross build from source, because it uses the build architecture toolchain. debian/rules does not pass cross tools to make. The easiest way to fix that is to let dh_auto_build do it. Still that

Bug#900015: missing pkg-config support is blocking switch to mbedTLS in libgit2

Package: mbedtls-dev version: 2.8.0-1 Severity: important Control: forwarded -1 https://github.com/ARMmbed/mbedtls/issues/228 Control: block 899036 by -1 Control: block 899035 by -1 lbgit2 now supports using mbedTLS but missing pkg-config support for mbedTLS is causing builds of many reverse

Bug#900014: rradvd: /etc/radvd.conf syntax error, unexpected T_BAD_TOKEN, expecting '{'

Package: radvd Version: 2.15 Severity: grave Justification: renders package unusable Dear Maintainer, I configured the radvd deamon using the follwing configuration file : #/etc/radvd.conf interface enp0s8 { AdvManagedFlag on; AdvSendAdvert on; AdvAutonomous off;

Bug#891633: aolserver4: Should this package be removed?

Simon McVittie wrote: > Package: aolserver > Version: 4.5.1-18.1 > Severity: serious > Justification: network-facing service, appears unmaintained upstream > User: debian...@lists.debian.org > Usertags: proposed-removal > > Turning this into a proposed-removal bug. > > On Tue, 27 Feb 2018 at

Bug#900013: src:knot-resolver: FTBFS on kFreeBSD due to endianness issues

Package: src:knot-resolver Version: 2.3.0-1 Control: forwarded -1 https://gitlab.labs.nic.cz/knot/knot-resolver/issues/348 Control: tags -1 + upstream The debian kfreebsd-amd64 build daemon shows failure to link libknot.so:

Bug#900009: libXm causes the GUI to crash

Control: tags -1 moreinfo Hi Miroslaw, Thanks for reporting issue you encounter. On 24-05-18 17:42, Miroslaw Dach wrote: > Please see the core dump listing: Could you install libxm4-dbgsym (Maybe you need to add the achieve, see ¹) and generate the core dump again? Currently the dump is close

Bug#899036: libgit2 0.27 transition

On Mon, 21 May 2018 22:46:48 +0530 Pirate Praveen wrote: cloning and assigning to libgit2. Now with libgit2 fixed, we are hitting another issue, because mbedTLS does not support pkg-config (https://github.com/ARMmbed/mbedtls/issues/228). Package mbedtls was not found

Bug#830934: [Pkg-dns-devel] Bug#830934: Bug#830934: knot-resolver: FTBFS on kFreeBSD: mdb.c needs pthread extensions

Version: 1.1.0~git2016070600-3 On Wed 2016-07-13 09:29:14 +0200, Ondřej Surý wrote: > Thanks for the report, that's definitely error on my side, it should use > system lmdb and not the embedded one. the build-dep on liblmdb-dev was added in knot-resolver 1.1.0~git2016070600-3. --dkg

Bug#898534: RFS: ftp.app/0.6-2 [RC]

Peter Pentchev wrote: > So I just took a more careful look at /usr/share/GNUstep/debian/config.mk > and "optim" seems to be conditionally defined there. Yes, I moved this snippet into config.mk in order not to repeat it in every GNUstep package. Hence the explicit B-D on the gnustep-make version

Bug#898566: transition: gdal

Control: tags -1 confirmed On 23/05/18 07:15, Sebastiaan Couwenberg wrote: > On 05/22/2018 10:19 PM, Emilio Pozuelo Monfort wrote: >> On 22/05/18 18:10, Sebastiaan Couwenberg wrote: >>> On 05/18/2018 02:49 PM, Emilio Pozuelo Monfort wrote: On 13/05/18 18:48, Bas Couwenberg wrote: >

Bug#899189: nmu: unison_2.48.3-1

Control: tags -1 stretch On 20/05/18 16:17, Stéphane Glondu wrote: > Package: release.debian.org > Severity: normal > User: release.debian@packages.debian.org > Usertags: binnmu > > Hi, > > Currently, Unison in Stretch is compiled with OCaml 4.01.0 (at least > on i386), while OCaml in

Bug#900012: autopkgtest failure due to lack of nodejs test dependency

Package: d3-format Version: 1:1.0.2-1 Tags: patch autopkgtest was failing on this package due to a lack of a nodejs test dependency, which is "required" for the "require" test (Get it? Okay, I'll stop.). I've attached a patch which fixes this issue, as well as moves the test command into a file

Bug#900011: src:htsjdk: Fake bug to prevent migration to testing

Package: src:htsjdk Version: 2.14.3+dfsg-2 Severity: critical Justification: causes serious data loss This new version was uploaded to unstable to enable building of its new dependencies. It should not migrate to testing since it would break several dependant packages. Testing should simply

Bug#899355: ifupdown: Hotplugging IPoIB devices does not work

Am Donnerstag, den 24.05.2018, 15:26 +0200 schrieb Guus Sliepen: > On Wed, May 23, 2018 at 10:43:40AM +0200, Benjamin Drung wrote: > > > Using allow-hotplug for InfiniBand devices does not work. The > > devices are never > > brought up. > > > > Example /etc/network/interfaces: > > ``` > >

Bug#765936: qemu-system-common: please preserve setuid bit on /usr/lib/qemu/qemu-bridge-helper

Hi, On Fri, Mar 17, 2017 at 12:27:44PM +0100, Guido Günther wrote: > Hi, > On Tue, May 19, 2015 at 04:12:18PM +0200, Raphael Hertzog wrote: > > Hi, > > > > On Sun, 19 Oct 2014, Michael Tokarev wrote: > > > This configuration is unsupported, until proper security model is > > > implemented > > >

Bug#900010: autopkgtest failure due to lack of test dependencies

Package: browser-request Version: 0.3.3-1 Tags: patch autopkgtest was failing on this package because it doesn't include nodejs in the test environment. After adding nodejs, it also complains about a lack of XMLHttpRequest. I've attached a patch which fixes both of these issues. Alternatively,

Bug#818930: [Pkg-dns-devel] Bug#818930: knot-resolver: trust_anchors.config does not check its argument

Version: 2.3.0-1 On Mon 2016-03-21 20:03:08 +, Stephane Bortzmeyer wrote: > When calling: > > trust_anchors.config('/etc/knot-resolver/yeti-root.key') > > I discovered that Knot does not check that the file exists. If it > doesn't, there is no error and no warning, but Knot falls back to a >

Bug#877590: picard-tools updated, and ready?

On 05/24/2018 03:27 PM, Andreas Tille wrote: > On Thu, May 24, 2018 at 03:14:29PM +0200, Olivier Sallou wrote: >> >> On 05/24/2018 08:35 AM, Andreas Tille wrote: >>> Hi Olivier, >>> >> I can't upload to unstable as one of the deps (gkl) depends on htsjdk , >> and need a *recent* one (the

Bug#900009: libXm causes the GUI to crash

Package: libxm4 Version: 2.3.4-13 I have a GUI app which is based on motif. The GUI app compilation and linkage goes well on Debian Stretch. When I launch the GUI it opens properly but when I access menu widgets than the GUI crashes. Please see the core dump listing: #0 __GI_raise

Bug#857578: [Pkg-dns-devel] Bug#857578: knot-resolver: The package should not override blindly the config of trust anchors

Version: 2.1.0-1 On Mon 2017-03-13 18:33:42 -0400, Daniel Kahn Gillmor wrote: > fwiw, i agree with Stephane here, and would actually take it further: i > think it would be great to strip down both /etc/default/kresd and > /etc/knot-resolver/kresd.conf to the point where we don't ship either of >

Bug#900008: kid3 FTCBFS: multiple reasons

Source: kid3 Version: 3.5.1-1 Tags: patch User: helm...@debian.org Usertags: rebootstrap kid3 fails to cross build from source. The first reason is that it forces the the build architecture compiler with CMAKE_C_COMPILER and CMAKE_CXX_COMPILER. It's good that the packaging forwards the

Bug#900007: ITP: r-cran-sjplot -- GNU R data visualization for statistics in social science

Package: wnpp Severity: wishlist Owner: Andreas Tille * Package name: r-cran-sjplot Version : 2.4.1 Upstream Author : Daniel Lüdecke, Carsten Schwemmer * URL : https://cran.r-project.org/package=sjPlot * License : GPL-3 Programming Lang:

Bug#900006: Breaks gnome-boxes since it fails to initialize smartcard

Package: qemu-system-x86 Version: 1:2.12+dfsg-1+b1 Severity: normal Tags: patch Hi, gnome-boxes currently fails to start VMs like (gnome-boxes:20770): Boxes-WARNING **: 17:06:48.839: wizard.vala:267: Unable to start domain: internal error: process exited while connecting to monitor:

Bug#891838: Starting kresd services with wildcard doesn't work

Control: forwarded 891838 https://gitlab.labs.nic.cz/knot/knot-resolver/merge_requests/587 Hi Sakirnth-- On Thu 2018-03-01 12:41:34 +0100, Sakirnth Nagarasa wrote: > In my setup I use 4 instances of kresd@.service. The instances are > created with the following command: > > systemctl enable

Bug#899044: Oops: 0000 [#1] SMP in skb_release_data, openvswitch related

To: netdev, dev@openvswitch Cc: Eric Dumazet (author of ff04a771ad), debian bug Hi, As follow-up to my bug report at Debian [0], I'm trying to do bug triage and find out more. I'm not the expert here, but anything could help, and it's an opportunity to learn things. I'm observing the attached

Bug#900005: hwdata pnp.ids contains outdated data for LG

Package: hwdata Version: 0.290-1 Severity: minor Dear Maintainer, hwdata pnp.ids content is outdated compared to what's upstream. For instance GSM is still resolved as Goldstar despite that name not being in use since 1995. This leads to a confusing situation like displaying 'Goldstar' in Gnome

Bug#899152: FTBFS: ipmi.h:85:2: error: unknown type name 'selector_t'

Adam / Juhani, Thank you for sending this email. Looks like something changed in the compiler or the switches in the past one year. We have not touched the ipmi code in ages. Going to work on this today. Regards Mohan From: Juhani Numminen

Bug#899213: compiz: sistematically places new windows below existing ones

Le 24/05/2018 à 15:26, Giacomo Boffi a écrit : I have another experiment, where 1. I've started compiz redirecting both stdout and stderr to a file, that you can find in attachment; Thank you for the investigation. The log file contains some message concerning incorrect placement of windows

  1   2   3   4   5   6   7   8   >