Bug#935223: kcollectd removal

On Friday, August 30, 2019 12:53:35 AM EDT Antonio Russo wrote: > Hello, > > You recently requested the removal of kcollectd from unstable due to the use > of qt4. I've ported this to qt5, taken over upstream, and offered to adopt > the package [1]. > > Would it be possible for you to comment on

Bug#936095: sardana: Obsolete libs (Python 2) - Depends on to be removed packages

Source: sardana Version: 2.6.2+dfsg-1 Severity: serious Justification: Policy 2.5 It appears that upstream supports python3 [1]. Please either upgrade the package or have it removed. This is, indirectly, one of the few remaining packages blocking python-qt4 removal. We are also removing Qt4.

Bug#929786: origtargz does not download multiple tarballs

On Mon, 15 Jul 2019 21:33:47 +0530 Pirate Praveen wrote: > On Fri, 31 May 2019 16:25:17 +0500 Pirate Praveen > wrote: > > > > > > On Fri, May 31, 2019 at 3:12 PM, Mattia Rizzolo > > wrote: > > > user devscri...@packages.debian.org > > > usertags 929786 origtargz > > > tags 929786 moreinfo >

Bug#847621: mpi4py: FTBFS on !linux: tests fail in MPI_INIT

Source: mpi4py Followup-For: Bug #847621 Control: block -1 by 929975 mpi4py is now building on hurd. kfreebsd is held up by an endless loop between numpy and matplotlib, Bug #929975.

Bug#931949: transition: proj

On 8/28/19 6:05 AM, Sebastiaan Couwenberg wrote: > On 8/26/19 5:42 AM, Sebastiaan Couwenberg wrote: >> On 8/25/19 4:31 PM, Sebastiaan Couwenberg wrote: >>> On 8/25/19 3:22 PM, Jonathan Wiltshire wrote: On Fri, Jul 12, 2019 at 09:39:26PM +0200, Bas Couwenberg wrote: > For the Debian GIS

Bug#936060: rocksndiamonds lintian override for maintainer-script-should-not-use-recursive-chown-or-chmod reasoning is incorrect

Hi Stephen-- On Thu 2019-08-29 23:18:53 +0200, Stephen Kitt wrote: > Thanks for taking an interest in this, I’ve often wondered if I’d got my > analysis right... thanks for taking another look at this with me. > But all this happens inside $tempdir, which is root:root 700. If anyone can > race

Bug#936094: python3: Installing vdirsyncer or pygobject in a virtual environment results in a linker error

Package: python3 Version: 3.7.3-1 Severity: important Dear Maintainer, I noticed the same error while installing in a pristine virtual environment the python packages 'vdirsyncer' or 'pygobject' (I made a bug report to gnome for the later in case it matters:

Bug#936093: RM: libgeotiff-dfsg -- ROM; Obsolete, replaced by libgeotiff

Package: ftp.debian.org Severity: normal Please remove libgeotiff-dfsg from the archive, it's obsolete with the transition to PROJ 6 and replaced by libgeotiff. Kind Regards, Bas

Bug#935223: kcollectd removal

Hello, You recently requested the removal of kcollectd from unstable due to the use of qt4. I've ported this to qt5, taken over upstream, and offered to adopt the package [1]. Would it be possible for you to comment on the suitability of the packaging for inclusion in Debian? Since I've

Bug#936092: gcc-9 patches apply even less

Source: cross-gcc Version: 231 Severity: serious Tags: patch Control: block -1 by 928035 On top of #928035, there is another change in gcc-9 that makes the gcc-9 patches no longer apply. The attached patch resolves the relevant hunk. Please consider uploading a new version that works with the

Bug#927135: src:rekall: Please update to python3 version

control: block -1 by 936091 On Mon, 26 Aug 2019 11:02:23 +0200 Raphael Hertzog wrote: > Hi, > > On Sun, 25 Aug 2019, Scott Kitterman wrote: > > If you have lost interest in the package, please let me know so I can ask to > > have it removed. > > Don't remove rekall please. There's a new upstream

Bug#936091: aff4: please package new upstream release (needed by rekall), port to python3

Source: aff4 Severity: serious Hello, please package the new upstream release for aff4; according to https://github.com/google/aff4 the project has been split in the Python and C parts separately. aff4 (specificly `'pyaff4 >= 0.26, < 0.30'`) is required by the new upstream release of rekall.

Bug#811180: etckeeper: Please port it to python 3

On Mon 2016-01-25 18:20:11 +, Jelmer Vernooij wrote: > The bzr bits have to be python2 because bzr is python 2 only at the moment. > > Bzr is optional though. fwiw, i'd much rather see etckeeper shipping with python3 with bzr disabled at this point. or maybe whatever folks need it to work

Bug#913639: unclutter: change upstream to unclutter-xfixes

Hello, On Tue 13 Nov 2018 at 12:04PM +01, nfb wrote: > since unclutter seems very old (so old that it doesn't even have an > Homepage, but it must be referred to by a web.archive snapshot among > the other things), would you mind switching upstream location to > unclutter-xfixes[0] for an

Bug#932777: scotch: segfault in test_scotch_graph_order bump_b1.grf

Source: scotch Followup-For: Bug #932777 Control: retitle -1 scotch: 6.0.8 FTBFS: segfault in test_scotch_graph_order bump_b1.grf Control: forwarded -1 https://gforge.inria.fr/tracker/?func=detail_id=248=1079=21771 Scotch 6.0.8 fixed test_libmetis (upstream bug #21768). But bump_b1.grf causes

Bug#936090: xfce4-settings: scrollbar disappears, doesn't want to come back

Package: xfce4-settings Version: 4.14.1-1 Severity: normal Dear Maintainer, Suppose I go to the Appearance section, which has a nice long list of styles. If I drag the scrollbar thumb and then pause while holding the (left) mouse button down, the scrollbar disappears after about 3 seconds.

Bug#931311: libsixel: Multiple security issues (CVE-2018-19756 CVE-2018-19757 CVE-2018-19759 CVE-2018-19761 CVE-2018-19762 CVE-2018-19763)

On Wed, 7 Aug 2019 10:05:36 +0900 Takatsugu Nokubi wrote: > Finaly, I made these fix patches, but not uploaded yet. > https://salsa.debian.org/debian/libsixel/tree/master/debian/patches At least, all bugs reported as important are fixed now. I'm working to fix patches for stretch:

Bug#936088: Acknowledgement (libmurmurhash autopkg tests fail)

Control: tags -1 + patch patch at http://launchpadlibrarian.net/439524642/libmurmurhash_1.5-1_1.5-1ubuntu1.diff.gz

Bug#936080: iputils-arping: arping -D : false positives

On Fri, Aug 30, 2019 at 12:01:32AM +0200, Pierre Donis wrote: > I'm using dracut to build the initramfs to boot on an ISCSI root disk. > Line 125 of /usr/lib/dracut/modules.d/40network/ifup.sh : > > if ! arping -f -q -D -c 2 -I $netif $ip ; then > warn "Duplicate address detected for $ip

Bug#936089: nemo: Missing gir1.2-nemo-3.0 dependency

reassign 936089 cinnamon tags 936089 + pending thanks Hi Jethro, On Fri, 30 Aug 2019, Jethro Nederhof wrote: > ValueError: Namespace Nemo not available > > Manually installing the gir1.2-nemo-3.0 as per > https://github.com/linuxmint/cinnamon/issues/8203#issuecomment-449746265 > package fixes

Bug#936089: nemo: Missing gir1.2-nemo-3.0 dependency

Package: nemo Version: 4.0.6-1 Severity: normal Dear Maintainer, On upgrade to Cinnamon 4, settings no longer launch properly. Trying to run cinnamon-settings from a terminal results in the Python error: ValueError: Namespace Nemo not available Manually installing the gir1.2-nemo-3.0 as per

Bug#925129: ffcall failed to build mips64 R6 version due to Illegal instruction

Hi, In you reported a problem with the use of the 'jr $25' instruction on MIPS32R6. Thanks for this report. I've changed the code to use the new opcode (previously written as 'jal $0,$25') always, since this opcode is supported since the

Bug#936088: libmurmurhash autopkg tests fail

Package: src:libmurmurhash Version: 1.5-1 Severity: serious Tags: sid bullseye Apparently the package needs a rebuild at least, some tests don't work anymore. autopkgtest [22:47:58]: test run-unit-test: [--- /usr/bin/ld: /tmp/ccNY3NFj.o: in function `main':

Bug#935958: runit: Tools to help generating runscripts

Package: runit Version: 2.1.2-33rescan1 Followup-For: Bug #935958 > * please make scripts return != 0 in case of failure. `./fetch foo' >exiting with 0 is very confusing. I have updated the code[1], all script now return nonzero in case of failure. Also there is some improvement on the

Bug#936073: please have libffi6-dbgsym debug package

On 29.08.19 20:46, shirish शिरीष wrote: It would be nice to have libffi6-dbgsym instead of libffi6-dbg as lot of archive has moved to use -dbgsym as they give more info. while debugging. please could you quantify "as they give more info. while debugging"?

Bug#752604: xbmc: better logging with timestamps

Control: tags -1 + fixed-upstream Control: forwarded https://github.com/xbmc/xbmc/pull/15457 On Thu, Jun 26, 2014 at 10:42:01PM +0200, Bálint Réczey wrote: > OK, reopening it. I'm not sure if adding the date would be accepted by > upstream since there may plenty of scripts expecting only the time

Bug#936043: ITP: gitbatch -- Manage git repositories in one place

On Thu, 2019-08-29 at 13:28 +0200, Dawid Dziurla wrote: > Package: wnpp > Severity: wishlist > Owner: Dawid Dziurla > > * Package name: gitbatch > Version : 0.5.0-1 > Upstream Author : Ibrahim Serdar Acikgoz > * URL : https://github.com/isacikgoz/gitbatch > * License

Bug#936086: RFS: vtun/3.0.4-1 [ITA] -- virtual tunnel over TCP/IP networks

Package: sponsorship-requests Severity: normal Dear mentors, I am looking for a sponsor for my package "vtun" * Package name: vtun Version : 3.0.4-1 Upstream Author : Maxim Krasnyansky * URL : http://vtun.sourceforge.net/ * License : GPL-2+ * Vcs

Bug#911821: Add development packages

Please find a packaged development package in https://salsa.debian.org/debian/mtd-utils/merge_requests/1

Bug#936085: mpd: Can not disable mpd.service and mpd.socket as a user.

Package: mpd Version: 0.21.13-1 Severity: normal Dear Maintainer, Tried to disable mpd.service and mpd.socket, but can not disable them. mpd.service and mpd.socket, are currently enabled: $ systemctl --user is-enabled mpd.service enabled $ systemctl --user is-enabled mpd.socket enabled

Bug#936084: mpd: An mpd client can not connect to mpd on port 6600, when mpd.socket is active as a user.

Package: mpd Version: 0.21.13-1 Severity: normal Dear Maintainer, After upgrading mpd from 0.21.5-3 to 0.21.13-1. An mpd client could not connect to mpd on port 6600. Checked to make sure that mpd was still disabled system wide: # systemctl is-enabled mpd.service disabled # systemctl

Bug#933576: debhelper: dh_installman is terribly slow

On Wed, Aug 21, 2019 at 05:51:00PM +, Niels Thykier wrote: > Colin Watson: > > Does this make sense to you? If so, do you have any opinions on the > > interface? (I'm open to it being a new program rather than having to > > stuff even more complexity into man's command-line interface, which

Bug#936083: RM: gdm3 [s390x] -- NBS; uninstallable

Package: ftp.debian.org Severity: normal Please remove the s390x *binary* package gdm3 (only that one, not the rest of src:gdm3) from unstable and experimental. It is uninstallable on s390x due to gnome-shell not working (it fails build-time tests), and in any case a desktop environment that

Bug#936082: grub-efi-amd64-signed: Add probe module to available modules

Package: grub-efi-amd64-bin Version: 1+2.02+dfsg1+20 Severity: wishlist Dear Maintainer, I'm trying to use Debian-signed secure boot grub binaries with Super Grub2 Disk scripts. Many of the Super Grub2 Disk scripts make use of the probe command. It makes possible to identify partition uuid

Bug#935753: FATAL:memory_linux.cc Out of memory

control: tag -1 moreinfo On Sun, Aug 25, 2019 at 4:36 PM Dan Jacobson wrote: > Versions of packages chromium depends on: [...] > ii libatk1.0-0 2.33.3+really2.33.3-1 [...] > ii libc62.29-0experimental1 [...] > ii libjpeg62-turbo 1:2.0.2-1~exp2 Could you try this

Bug#935988: buster-pu: package reportbug/7.5.3~deb10u1

Followup-For: Bug #935988 Control: retitle -1 buster-pu: package reportbug/7.5.3~deb10u1 new debdiff for rebuilding the 7.5.3 maintainer upload for buster. Andreas diff -Nru reportbug-7.5.2/bin/reportbug reportbug-7.5.3~deb10u1/bin/reportbug --- reportbug-7.5.2/bin/reportbug 2019-02-01

Bug#933723: Bug#936003: libsbuild-perl: always cleans apt cache even if "$apt_clean = 0;" is in .sbuildrc

Hi, Le 29/08/2019 à 00:12, Johannes Schauer a écrit : > > Ah indeed -- please go ahead! > Thanks ! :) I've made a git patch (see attached file) to be applied on master of sbuild (tell me if I should make a Debian package patch (in debian/patches) instead :) ). It adds a new option

Bug#935308: messed up regex

On Thu, 2019-08-29 at 22:45 +0100, Adam D. Barratt wrote: > On Thu, 2019-08-29 at 23:20 +0200, Hans-Christoph Steiner wrote: > > Ok, this is embarrasing: after discussing that Debian version regex > > and > > the version scheme for proposed-updates, I failed to see that the > > regex > > was wrong

Bug#934591: Anki fails to start: ModuleNotFoundError: No module named 'PyQt5.sip'

severity 931798 normal thanks On Wed, Aug 21, 2019 at 09:39:52PM +0100, Julian Gilbey wrote: > On Wed, Aug 21, 2019 at 04:22:23PM +0200, Arnaldo Pirrone wrote: > > Hi, i do have python3-sip. > > Now the error is this: > > $ anki > > Traceback (most recent call last): > >   File "/usr/bin/anki",

Bug#936081: New upstream 0.7.0 available

Package: wlroots Severity: wishlist Any plans to upload 0.7.0? I'd like to see sway 1.2 in Debian. :) -- Martin Michlmayr https://www.cyrius.com/

Bug#874901: [GLE-devel] Probable fix for qgle seg faults with latest ghostscript versions

On Thu, Aug 29, 2019 at 10:55:28PM +0200, Francesco Poli wrote: > On Thu, 29 Aug 2019 22:14:04 +0200 Christian T. Steigies wrote: > > > Hi, > > On Fri, Aug 16, 2019 at 04:32:08PM +0100, Laurence Abbott via Glx-devel > > wrote: > > > I _think_ I have the fix for seg faults that occur when QGLE is

Bug#929493: totem crashes on startup due to protocol error bug report #929493

Package: totem Version: 3.32.0-2 Followup-For: Bug #929493 This bug still exists in 3.33.90-2. as noted witht he x11 token, this problem affects the ability to run totem when using wayland. I was puzzled as to why this bug was affecting our Debian based home entertainment system, but not any of

Bug#936080: iputils-arping: arping -D : false positives

Package: iputils-arping Version: 3:20190709-1 Severity: normal Dear Maintainer, I'm using dracut to build the initramfs to boot on an ISCSI root disk. Line 125 of /usr/lib/dracut/modules.d/40network/ifup.sh : if ! arping -f -q -D -c 2 -I $netif $ip ; then warn "Duplicate address detected

Bug#936016: meteo-qt crashes immediately

my bad, my first answer was wrong - should talk with the author cheers Alf

Bug#936030: ***UNCHECKED*** Bug#936030: /usr/bin/cloud-init: cloud-init 18.3 failed to detect network link type: cascading (datasource: OpenStack)

On 8/29/19 11:25 AM, sabrina-muel...@t-systems.com wrote: > [...] > # w3m -dump http://169.254.169.254/openstack/latest/network_data.json | > jq '' > > { > [...] >   "links": [ >     { >   "type": "cascading", Hi Sabrina, Could you explain a little bit more what is "cascading" network type?

Bug#875234: [writetype] Future Qt4 removal from Buster

Thanks!!! Miry El jue., 29 ago. 2019 a las 23:05, Moritz Mühlenhoff () escribió: > > On Thu, Aug 29, 2019 at 10:58:03PM +0200, Miriam Ruiz wrote: > > It's okay for me to remove it from the archive. I think it would be > > the best. As you say, it seems to be dead upstream. > > Ack, I've just

Bug#935308: messed up regex

On Thu, 2019-08-29 at 23:20 +0200, Hans-Christoph Steiner wrote: > Ok, this is embarrasing: after discussing that Debian version regex > and > the version scheme for proposed-updates, I failed to see that the > regex > was wrong (see https://bugs.debian.org/935938). Its fixed now in >

Bug#936007: stretch-pu: package libu2f-host/1.1.2-2+deb9u1

Control: tags -1 + confirmed On Thu, 2019-08-29 at 00:04 +0200, Nicolas Braud-Santoni wrote: > I would like to backport the fix for CVE-2019-9578 in the next point > release > for stretch. Please find enclosed the proposed debdiff. ++ /* the response has to be atleast 17 bytes, if it's

Bug#936016: meteo-qt crashes immediately

Nice finding, unfortunately you are right: >From bfe9ae4d25b914d5c2622042303ba09fa8060e80 Mon Sep 17 00:00:00 2001 From: Dimitrios Glentadakis Date: Mon, 6 May 2019 19:34:58 +0200 Subject: [PATCH] Fix crash when 6 days forceast is not available --- meteo_qt/meteo_qt.py | 4 1 file

Bug#933822: closed by Jan Dittberner (Bug#933822: fixed in virtualenvwrapper 4.8.4-1)

On 28/08/2019 09:12, Debian Bug Tracking System wrote: This is an automatic notification regarding your Bug report which was filed against the virtualenvwrapper package: #933822: virtualenvwrapper depends on cruft package python-stevedore Is there a reason that the fix was only uploaded to

Bug#935976: stretch-pu: package node-ws/1.1.0+ds1.e6ddaae4-3+deb9u1

Control: tags -1 + confirmed On Wed, 2019-08-28 at 17:29 +0200, Xavier Guimard wrote: > During buster release, we fixed CVE-2016-10542 for node-ws. The same > patch can be applied in Stretch. > Please go ahead. Regards, Adam

Bug#936079: python-ceilometerclient (build-)depends on cruft packages.

Package: python-ceilometerclient Version: 2.9.0-2 Severity: serious Tags: bullseye, sid The python-ceilometerclient binary package depends on and the python-ceilometerclient binary package build-depends on a number of python 2 binary packages that are no longer built by their corresponding

Bug#912498: freealchemist: Please migrate to python3-pygame

Control: tags -1 + patch Dear maintainer, I submitted a merge request for Python 3 support on salsa: https://salsa.debian.org/python-team/applications/freealchemist/merge_requests/1 Kind regards, Reiner signature.asc Description: PGP signature

Bug#935915: Same problem reported on ubuntu

https://bugs.launchpad.net/ubuntu/+source/apt-cacher-ng/+bug/1034392 The original bug was reported in 2012 but recent comments are from 2018 and 2019: Steve Dodd (anarchetic) wrote on 2018-07-07: #17

Bug#935015: datalad: please drop python-datalad (python 2 removal effort)

Found 935015 0.11.2-2 Thanks This bug also affects the version in testing.

Bug#935999: buster-pu: package libu2f-host/1.1.9-1+deb10u1

Control: tags -1 + confirmed On Wed, 2019-08-28 at 22:52 +0200, Nicolas Braud-Santoni wrote: > On Wed, Aug 28, 2019 at 10:29:02PM +0200, Nicolas Braud-Santoni > wrote: > > I would like to backport the following patches for libu2f-host to > > stretch: > > > > + Fix for CVE-2019-9578 (Closes:

Bug#936022: buster-pu: package osmpbf/1.3.3-11

Control: tags -1 + confirmed On Thu, 2019-08-29 at 10:15 +0200, Bas Couwenberg wrote: > To fix the PBF support in the osmpbf rdeps it needs to be rebuilt > with protobuf 3.6.1 as reported in #935990. > Please go ahead. Regards, Adam

Bug#935308: messed up regex

Ok, this is embarrasing: after discussing that Debian version regex and the version scheme for proposed-updates, I failed to see that the regex was wrong (see https://bugs.debian.org/935938). Its fixed now in 25.0.0+11+deb10u1. And hopefully I got the version right. Is this bug report enough,

Bug#936056: buster-pu: package sdl-image1.2/1.2.12-10+deb10u1

Control: tags -1 + confirmed On Thu, 2019-08-29 at 09:45 -0400, Hugo Lefeuvre wrote: > sdl-image1.2 is affected by a number of security issues in buster. > Impact is > quite minor, but it would still be nice to get them fixed. > Please go ahead. Regards, Adam

Bug#936051: stretch-pu: package sdl-image1.2/1.2.12-5+deb9u2

Control: tags -1 + confirmed On Thu, 2019-08-29 at 09:51 -0400, Hugo Lefeuvre wrote: > Small update: I forgot to close the bug report (#932755) and did not > mention > CVE-2019-5058 in debian/changelog. You can find an updated debdiff in > attachment. > Please go ahead. Regards, Adam

Bug#936060: rocksndiamonds lintian override for maintainer-script-should-not-use-recursive-chown-or-chmod reasoning is incorrect

Hi Daniel, Thanks for taking an interest in this, I’ve often wondered if I’d got my analysis right... On Thu, 29 Aug 2019 10:45:08 -0400, Daniel Kahn Gillmor wrote: > the lintian override says: > > # We recursively chown files to root:root after neutering their > # permissions, so the attacks

Bug#936078: RM: writetype -- RoQA; dead upstream, depends on qt4

Package: ftp.debian.org Severity: normal Please remove writetype. It's dead upstream and depends on Qt4, the maintainer (CCed) has acked the removal in #875234). Cheers, Moritz

Bug#875234: [writetype] Future Qt4 removal from Buster

On Thu, Aug 29, 2019 at 10:58:03PM +0200, Miriam Ruiz wrote: > It's okay for me to remove it from the archive. I think it would be > the best. As you say, it seems to be dead upstream. Ack, I've just filed a removal bug. Cheers, Moritz

Bug#701903: Issue incorrectly tagged fixed-upstream

Simon McVittie: > You mentioned Bugzilla #679622, but that looks like an unrelated bug > (which was also migrated to Gitlab, this time as GNOME/gimp#412). Right, copied the wrong link, sorry about that.

Bug#936077: RM: gns3 -- RoQA; unmaintained, depends on qt4

Package: ftp.debian.org Severity: normal Please remove gns3. It's unmaintained (last upload in 2014), is removed from testing since 15 months due to the old version being unusable (#784871) and depends on qt4, which is going away. Cheers, Moritz

Bug#935915: CPU load, kernel IP filters not a factor

CPU load - Not a factor, utilization is almost always less than 30% when tests are run. Nothing is running in the GUI, of the acng server, not even a browser. The out of tree module is the 'netatop' module which works inside atop and it hardly uses any cycles. The module is loaded and the netatop

Bug#936076: python3-numba: numba segfaults when run with python 3.7.4 at numba/_dynfunc.c:52

Package: python3-numba Version: 0.42.0-1 Severity: grave Tags: upstream Justification: renders package unusable Dear Maintainer, Attempting to run any numba code immediately segfaults when running with python 3.7.4. I found this upstream bug report. https://github.com/numba/numba/pull/4328

Bug#875234: [writetype] Future Qt4 removal from Buster

It's okay for me to remove it from the archive. I think it would be the best. As you say, it seems to be dead upstream. Greetings, Miry El jue., 29 ago. 2019 a las 22:42, Moritz Mühlenhoff () escribió: > > On Sat, Sep 09, 2017 at 11:12:40PM +0200, Lisandro Damián Nicanor Pérez Meyer > wrote: >

Bug#874901: [GLE-devel] Probable fix for qgle seg faults with latest ghostscript versions

On Thu, 29 Aug 2019 22:14:04 +0200 Christian T. Steigies wrote: > Hi, > On Fri, Aug 16, 2019 at 04:32:08PM +0100, Laurence Abbott via Glx-devel wrote: > > I _think_ I have the fix for seg faults that occur when QGLE is used with > > ghostscript 9.27 (the latest release). > > I applied Laurence's

Bug#932248: python*-acme and Certbot will break on November 1st

Any updates on this? Looking at server logs, I expect ~145K+ unique installations to be affected by this problem if it doesn’t get fixed.

Bug#875234: [writetype] Future Qt4 removal from Buster

On Sat, Sep 09, 2017 at 11:12:40PM +0200, Lisandro Damián Nicanor Pérez Meyer wrote: > Source: writetype > Version: 1.3.163-1 > Severity: wishlist > User: debian-qt-...@lists.debian.org > Usertags: qt4-removal > > > Hi! As you might know we the Qt/KDE team are preparing to remove Qt4 > as

Bug#936006: [Pkg-fonts-devel] Bug#936006: fonts-dejavu-core: Invalid rendering of 'ż' at serveral different sizes

Am Donnerstag, den 29.08.2019, 21:58 +0200 schrieb Łukasz Stelmach: > Done, however, I am not 100% sure github is the right place to do it. Thanks for that! Well, at least now it is at the attention of the upstream developers. Though, last commit from 2+ years ago doesn't really look promising...

Bug#925862: xbindkeys-config: ftbfs with GCC-9

Control: tags -1 + patch Dear maintainer, the attached patch fixes the FTBFS by moving the linked libraries to the end of the command line. Regards, Reiner --- xbindkeys-config-0.1.3.orig/debian/patches/gcc9.patch +++ xbindkeys-config-0.1.3/debian/patches/gcc9.patch @@ -0,0 +1,15 @@ +Author:

Bug#875250: [scim] Future Qt4 removal from Buster

On Sat, Sep 09, 2017 at 11:09:36PM +0200, Lisandro Damián Nicanor Pérez Meyer wrote: > Source: scim > > Hi! As you might know we the Qt/KDE team are preparing to remove Qt4 > as [announced] in: > > [announced] > > >

Bug#930446: popularity-contest: unable to submit report, impossible to debug

On Wed, 12 Jun 2019 22:52:59 +0200 Bill Allombert wrote: On Wed, Jun 12, 2019 at 09:46:58PM +0200, Stefan Fritsch wrote: > Package: popularity-contest > Version: 1.67 > Severity: normal > > Dear Maintainer, > > on several of my hosts, popularity-contest logs > > unable to submit report to

Bug#930363: faad2: fix build with gcc-9 [patch]

Am Donnerstag, den 29.08.2019, 09:54 -0400 schrieb Hugo Lefeuvre: > Ack, I'll NMU then. Good luck with the baby :) Thank you! \o/ - Fabian signature.asc Description: This is a digitally signed message part

Bug#875219: [unixodbc-gui-qt] Future Qt4 removal from Buster

On Sat, Sep 09, 2017 at 11:11:54PM +0200, Lisandro Damián Nicanor Pérez Meyer wrote: > Source: unixodbc-gui-qt > Version: 2.3.0-4 > Severity: wishlist > User: debian-qt-...@lists.debian.org > Usertags: qt4-removal > > > Hi! As you might know we the Qt/KDE team are preparing to remove Qt4 > as

Bug#936006: [Pkg-fonts-devel] Bug#936006: fonts-dejavu-core: Invalid rendering of 'ż' at serveral different sizes

Control: forwarded -1 https://github.com/dejavu-fonts/dejavu-fonts/issues/338 Fabian Greffrath writes: > Would you mind reporting this issue upstream, please? Done, however, I am not 100% sure github is the right place to do it. -- Było mi bardzo miło. ---

Bug#933578: Possible fix scanning with HP MFP that requires a plugin

I had quite some difficulty getting "hp-setup" to configure a HP Color LaserJet Pro MFP M277dw to allow scanning + "hp-toolbox" to allow scanning, status check, etc. on Debian 10. See: https://bugs.launchpad.net/ubuntu/+source/hplip/+bug/1430561/comments/39 I found several things which together

Bug#935133: [Pkg-openssl-devel] Bug#935133: Bug#935133: slow TLS handshake renders browsers and email client unusable

While I may be the first to report this to Debian bugs casual googling turns up other reports of this to the Internet at large. The good news is that the MTU workaround seems to be working as there has not been any TLS handshake issues since the workaround was applied. While I'm completely

Bug#936075: ITP: fortran-language-server -- Fortran Language Server for the Language Server Protocol

Package: wnpp Severity: wishlist Owner: Denis Danilov * Package name: fortran-language-server Version : 1.10.2 Upstream Author : Chris Hansen * URL : https://github.com/hansec/fortran-language-server * License : MIT Programming Lang: Python Description

Bug#925625: abr2gbr: ftbfs with GCC-9

Control: tags -1 + patch Dear maintainer, the attached patch fixes the FTBFS by moving the libs to the end of the command line. Regards, Reiner diff -Nru abr2gbr-1.0.2/debian/patches/gcc9.patch abr2gbr-1.0.2/debian/patches/gcc9.patch --- abr2gbr-1.0.2/debian/patches/gcc9.patch 1970-01-01

Bug#936074: irssi: CVE-2019-15717

Source: irssi Version: 1.2.1-1 Severity: important Tags: security upstream Control: found -1 1.2.0-2 Hi, The following vulnerability was published for irssi. CVE-2019-15717[0]: | Irssi 1.2.x before 1.2.2 has a use-after-free if the IRC server sends | a double CAP. If you fix the vulnerability

Bug#936073: please have libffi6-dbgsym debug package

Package: libffi6 Version: 3.2.1-9 Severity: normal Dear Maintainer, It would be nice to have libffi6-dbgsym instead of libffi6-dbg as lot of archive has moved to use -dbgsym as they give more info. while debugging. See https://wiki.debian.org/AutomaticDebugPackages for more info. -- System

Bug#935988: buster-pu: package reportbug/7.5.2+nmu1~deb10u1

On 29/08/2019 20.26, Adam D. Barratt wrote: > Will you be updating and/or reversioning the pu to reflect the > maintainer upload? Yes, updated pu is coming... The maintainer upload contained a few more bugfixes, but I think they all should go to buster as well. Unfortunately it's lacking a

Bug#875029: [lightdm] Future Qt4 removal from Buster

On Thu, Sep 21, 2017 at 03:36:38PM +0200, Yves-Alexis Perez wrote: > On Thu, 2017-09-21 at 00:09 +0800, Boyuan Yang wrote: > > I noticed that you are planning to remove Qt components of lightdm from > > Debian's lightdm. In fact, pkg-deepin team has a planned package that needs > > Qt5-based

Bug#935988: buster-pu: package reportbug/7.5.2+nmu1~deb10u1

On Wed, 2019-08-28 at 19:52 +0200, Andreas Beckmann wrote: > reportbug/buster does not know about buster being stable ... > > I've just uploaded a fix to unstable via DELAYED/2, so it should be > in > unstable before the weekend, still hoping for a maintainer upload. That happened. [...] > I'll

Bug#875087: [phonon-backend-gstreamer] Future Qt4 removal from Buster

On Sat, Sep 09, 2017 at 10:18:38PM +0200, Lisandro Damián Nicanor Pérez Meyer wrote: > Source: phonon-backend-gstreamer > Version: 4:4.9.0-1 > Severity: wishlist > User: debian-qt-...@lists.debian.org > Usertags: qt4-removal > > > Hi! As you might know we the Qt/KDE team are preparing to remove

Bug#935588: ceph 12.2.11+dfsg1-2.1+b1 flagged for acceptance

package release.debian.org tags 935588 = buster pending thanks Hi, The upload referenced by this bug report has been flagged for acceptance into the proposed-updates queue for Debian buster. Thanks for your contribution! Upload details == Package: ceph Version:

Bug#935588: gdb 8.2.1-2+b1 flagged for acceptance

package release.debian.org tags 935588 = buster pending thanks Hi, The upload referenced by this bug report has been flagged for acceptance into the proposed-updates queue for Debian buster. Thanks for your contribution! Upload details == Package: gdb Version: 8.2.1-2+b1

Bug#935588: gdb-mingw-w64 10.8+b2 flagged for acceptance

package release.debian.org tags 935588 = buster pending thanks Hi, The upload referenced by this bug report has been flagged for acceptance into the proposed-updates queue for Debian buster. Thanks for your contribution! Upload details == Package: gdb-mingw-w64 Version: 10.8+b2

Bug#920900: pkgdata in icu-devtools(63.2-2) pkg on deb10 stable still use icu-config

Dear Maintainer, As you confirm icu-config is now deprecated. But pkgdata in icu-devtools(63.2-2) on deb10 stable is still referring to icu-config : $ pkgdata -p bin_mkltfs -m static packagelist.txt sh: 1: icu-config: not found sh: 1: icu-config: not found pkgdata: icu-config: No icu-config

Bug#932361: [gnome flashback] gnome-desktop-flashback does not start

Control: reassign -1 linux-image-4.19.0-6-amd64-unsigned 4.19.67-1 Hi Joachim, On Thu, Aug 29, 2019 at 07:17:19PM +0200, Joachim Schmidt wrote: > Hi Dmitry, > > ~/.local/share/applications is empty > sometime I can start gnome-flashback but today there was a crash again (only > press of RESET

Bug#936072: RM: xflr5 -- RoQA; orphaned, depends on Qt4

Package: ftp.debian.org Severity: normal Please remove xflr5. The version in the archive is very old (released in 2013) and depends on Qt4. Recent releases do support Qt5, but noone stepped up to maintain it during the last 2.5 years, so let's remove it. Cheers, Moritz

Bug#892102: Need a core dump

The inetd daemon runs as a systemd service, but lately I've been getting the following message when it crashes with SIGABRT: systemd-coredump[15585]: Resource limits disable core dumping for process 13098 (inetd). How can the system be configured to allow a core dump to be taken? I have core

Bug#935977: RM: gnuplot [mipsel] -- ROM; FTBFS on deprecated platform (mipsel)

Hello Scott, thanks for explanation and sorry for misunderstanding. Yes I will try to fix thenFTBFSt, if it is possible. Regard Anton Am Mi., 28. Aug. 2019 um 23:48 Uhr schrieb Scott Kitterman : > > Mipsel is still a release architecture. It's mips that was dropped. Does > that change your

Bug#933330: Bug#903161: Same issue here; solution found

On Thu, Aug 29, 2019 at 01:08:32PM +0300, Timo Sirainen wrote: > On 29 Aug 2019, at 3.57, Josh Triplett wrote: > > > > On Wed, Aug 28, 2019 at 05:43:27PM -0700, Josh Triplett wrote: > >> So if the stats sockets don't exist at *all*, deliver won't complain. > >> > >> To disable those stats

Bug#701903: Issue incorrectly tagged fixed-upstream

Control: tags -1 - fixed-upstream Control: forwarded -1 https://gitlab.gnome.org/GNOME/gimp/issues/535 On Thu, 29 Aug 2019 at 17:15:00 +, segfault wrote: > This bug was tagged as fixed-upstream, but the upstream issue wasn't > actually fixed, it was merely moved to GitLab. > > The old

Bug#934457: installation in chroot failing with Unknown device "/dev/fuse": No such device

Hello, The issue is in the command: udevadm test --action -p $(udevadm info -q path -n /dev/fuse) the -p flag is being seen as a parameter to the --action flag, which is not a valid action. Per the udevadm man page: *-c*, *--action=**ACTION* Type of event to be triggered. Possible actions

Bug#701903: Issue incorrectly tagged fixed-upstream

This bug was tagged as fixed-upstream, but the upstream issue wasn't actually fixed, it was merely moved to GitLab. The old upstream issue: http://bugzilla.gnome.org/show_bug.cgi?id=679622 The new upstream issue (still open): https://gitlab.gnome.org/GNOME/gimp/issues/535

  1   2   3   >