Bug#971001: Please support caching packages outside the chroot

Quoting Josh Triplett (2020-09-26 06:28:18) > mmdebstrap seems to re-download packages every time it runs. I'd love to have > a way to cache those packages, so that it can run substantially faster the > second and subsequent times. Do one thing and do it well. I'm sure you are aware of

Bug#970196: Getting the same at my end and also in archlinux

Hi all, Have got the same bug at my end. Also see similar report in archlinux as well - https://bugs.archlinux.org/task/67978 1. Sandbox: unsupported fd-relative fstatat(32, "", 0x7FFE49DBD7B0, 4096) Sandbox: seccomp sandbox violation: pid 75078, tid 75078, syscall 262, args 32 140293624582910

Bug#971002: extlinux does not support ext4 with inline_data

Package: extlinux Version: 3:6.04~git20190206.bf6db5b4+dfsg1-3 Severity: normal X-Debbugs-Cc: j...@joshtriplett.org extlinux cannot seem to handle ext4 files or directories whose data is stored inline in the inode (with the `inline_data` option). It's possible to work around this, by ensuring

Bug#970196:

-- Regards, Shirish Agarwal शिरीष अग्रवाल My quotes in this email licensed under CC 3.0 http://creativecommons.org/licenses/by-nc/3.0/ http://flossexperiences.wordpress.com E493 D466 6D67 59F5 1FD0 930F 870E 9A5B 5869 609C

Bug#970966: python-cartopy: autopkgtest must be marked superficial

Control: tags -1 pending On 9/26/20 1:06 AM, Sudip Mukherjee wrote: > On closer look, it looks like you have a different problem with autopkgtest. > You have a test script which is called "python3", but you are doing > "Test-Command: python3", so that is not executing your test script but > is

Bug#971001: Please support caching packages outside the chroot

Package: mmdebstrap Version: 0.7.1-1 Severity: wishlist X-Debbugs-Cc: j...@joshtriplett.org mmdebstrap seems to re-download packages every time it runs. I'd love to have a way to cache those packages, so that it can run substantially faster the second and subsequent times. -- System Information:

Bug#971000: linux-image-5.8.0-2-amd64: Periodic networking failure with recent kernels in Testing

Package: src:linux Version: 5.8.10-1 Severity: important Dear Maintainer, I've been experiencing periodic random network controller failures on recent kernels in Testing. This started happening possibly around the 5.6 kernel release, and wasn't happening sometime before that. The system is

Bug#960831: about RFS: yiyantang

 Control: tags 960831 - moreinfo Hi Tobias Frost,  I'm the maintainer of the package yiyantang , so I use NMU to upload that is inappropiate before. I'd uploaded the new version yiyangtang package on mentors[1], please help to review again. yiyantang is very old package, It's upstream is not

Bug#970818: mrpt: FTBFS on mipse64el: E: Build killed with signal TERM after 150 minutes of inactivity

Hi Sebastian (cc: Scott): On Fri, Sep 25, 2020 at 10:50 PM Sebastian Ramacher wrote: > Reducing the optimization level on mips64el might help to reduce the > compile time. Alternatively, if possible, one could split the source > files into smaller ones. Hmmm... great idea! In fact, there was

Bug#970999: buster-pu: package glances/3.1.0-1+deb10u1

Package: release.debian.org Severity: normal Tags: buster User: release.debian@packages.debian.org Usertags: pu Dear Stable release team, Currently, the glances version in buster listen 0.0.0.0 by default. For more info please see[1] The debdiff attached brings patch to fix it. Regards

Bug#970818: mrpt: FTBFS on mipse64el: E: Build killed with signal TERM after 150 minutes of inactivity

On Sat, 26 Sep 2020, José Luis Blanco-Claraco wrote: On Fri, Sep 25, 2020 at 10:50 PM Sebastian Ramacher wrote: Reducing the optimization level on mips64el might help to reduce the compile time. Alternatively, if possible, one could split the source files into smaller ones. Hmmm... great

Bug#970998: okular forgets bookmarks when switching tabs

Package: okular Version: 4:20.08.1-1 Bookmarks disappear from the Bookmarks menu for the current file whenever you open another file or switch to another tab. The bookmarks return if you reload the PDF, but disappear again as soon as you switch to another tab. How to reproduce/verify: 1. open

Bug#970997: RFS: cinnamon-dev-tools/4.6.0-1 [ITP] -- Tools for Cinnamon Developers

Package: sponsorship-requests Severity: wishlist Tags: patch Dear mentors, I am looking for a sponsor for my package "cinnamon-dev-tools": * Package name: cinnamon-dev-tools Version : 4.6.0-1 Upstream Author : Joshua Peisach * URL :

Bug#592519: initramfs-tools: COMPRESS option should be more flexible

On Fri, 2020-09-25 at 14:19 -0300, Rogério Brito wrote: > Package: initramfs-tools > Version: 0.139 > Followup-For: Bug #592519 > X-Debbugs-Cc: b...@debian.org, m...@debian.org, debian-ker...@lists.debian.org > > > Hi. > > In a similar vein to what was reported by Roger Shimizu, it takes ages

Bug#964125: calibre: Please switch from sip4 to sip5

On Fri, 25 Sep 2020, Dmitry Shachnev wrote: > Yes. I am again sorry for this disruptive change, but it had to happen > sooner or later. No problem, incidentally calibre 5.0 was released the same day and already uploaded (5.0.1), so breakage was minimal. Thanks for your work! Norbert --

Bug#970936: ITP: ruby-azure-storage -- Official Ruby client library to consume Azure Storage services

Package: wnppSeverity: wishlistOwner: Abraham Raji X-Debbugs-CC: debian-de...@lists.debian.org* Package name    : ruby-azure-storage  Version : 0.15.0.preview  Upstream Author : Copyright 2015 Microsoft Corporation * URL : https://rubygems.org/gems/azure-storage* License 

Bug#970995: darkmint-gtk-theme: does not define @text_view_bg named colour

Source: darkmint-gtk-theme Version: 2.0.0-2 Severity: important Tags: upstream GTK 3.24.22 introduced a new named colour, @text_view_bg, which the vte terminal library has started to rely on, causing misrendering in themes that do not define it (see

Bug#970993: dark-gtk-themes: does not define @text_view_bg named colour

Source: dark-gtk-themes Version: 0-2 Severity: important Tags: upstream GTK 3.24.22 introduced a new named colour, @text_view_bg, which the vte terminal library has started to rely on, causing misrendering in themes that do not define it (see ).

Bug#970994: darkcold-gtk-theme: does not define @text_view_bg named colour

Source: darkcold-gtk-theme Version: 5.0.0-2 Severity: important Tags: upstream GTK 3.24.22 introduced a new named colour, @text_view_bg, which the vte terminal library has started to rely on, causing misrendering in themes that do not define it (see

Bug#970991: blackbird-gtk-theme: does not define @text_view_bg named colour

Package: blackbird-gtk-theme Version: 0.4+20171213-2 Severity: important Tags: upstream GTK 3.24.22 introduced a new named colour, @text_view_bg, which the vte terminal library has started to rely on, causing misrendering in themes that do not define it (see

Bug#970992: bluebird-gtk-theme: does not define @text_view_bg named colour

Package: bluebird-gtk-theme Version: 1.3-1 Severity: important Tags: upstream GTK 3.24.22 introduced a new named colour, @text_view_bg, which the vte terminal library has started to rely on, causing misrendering in themes that do not define it (see

Bug#970990: clearlooks-phenix-theme: does not define @text_view_bg named colour

Package: clearlooks-phenix-theme Version: 7.0.1-3 Severity: important Tags: upstream GTK 3.24.22 introduced a new named colour, @text_view_bg, which the vte terminal library has started to rely on, causing misrendering in themes that do not define it (see

Bug#970988: arc-theme: does not define @text_view_bg named colour

Package: arc-theme Version: 20200819-1 Severity: important Tags: upstream GTK 3.24.22 introduced a new named colour, @text_view_bg, which the vte terminal library has started to rely on, causing misrendering in themes that do not define it (see ).

Bug#970989: breeze-gtk-theme: does not define @text_view_bg named colour

Package: breeze-gtk-theme Version: 5.17.5-2 Severity: important Tags: upstream GTK 3.24.22 introduced a new named colour, @text_view_bg, which the vte terminal library has started to rely on, causing misrendering in themes that do not define it (see

Bug#970987: greybird-gtk-theme: does not define @text_view_bg named colour

Package: greybird-gtk-theme Version: 3.22.10-1 Severity: important Tags: upstream GTK 3.24.22 introduced a new named colour, @text_view_bg, which the vte terminal library has started to rely on, causing misrendering in themes that do not define it (see

Bug#970986: materia-gtk-theme: does not define @text_view_bg named colour

Package: materia-gtk-theme Version: 20200320-0.1 Severity: important Tags: upstream GTK 3.24.22 introduced a new named colour, @text_view_bg, which the vte terminal library has started to rely on, causing misrendering in themes that do not define it (see

Bug#933110: pkg-components: No upstream maintainer ⇒ unsuitable for Bullseye

On Thu, 20 Aug 2020 11:23:42 +0200, intrigeri wrote: > Simon McVittie (2020-08-20): > >> I'll file bugs against all reverse-dependencies to alert their > >> maintainer about this situation. > > Should the bugs against rdeps be escalated to serious at this point, > > potentially triggering

Bug#970985: adapta-gtk-theme: does not define @text_view_bg named colour

Package: adapta-gtk-theme Version: 3.95.0.11-2 Severity: important Tags: upstream GTK 3.24.22 introduced a new named colour, @text_view_bg, which the vte terminal library has started to rely on, causing misrendering in themes that do not define it (see

Bug#970984: linux-image-5.8.0-2-amd64: Please replace console scrollback

Package: src:linux Version: 5.8.10-1 Severity: normal X-Debbugs-Cc: Asher Gordon Dear Maintainer, After upgrading to linux-image-5.8.0-2, I noticed that scrollback is no longer available in the console. A quick look at the changelog ('apt changelog linux-image-amd64') indicates that this was

Bug#970983: sugar-themes: does not define @text_view_bg named colour

Package: sugar-themes Version: 0.117-1 Severity: important Tags: upstream GTK 3.24.22 introduced a new named colour, @text_view_bg, which the vte terminal library has started to rely on, causing misrendering in themes that do not define it (see ).

Bug#970982: ukui-themes: does not define @text_view_bg named colour

Package: ukui-themes Version: 1.4.0-1 Severity: important Tags: upstream GTK 3.24.22 introduced a new named colour, @text_view_bg, which the vte terminal library has started to rely on, causing misrendering in themes that do not define it (see ).

Bug#970981: mate-themes: does not define @text_view_bg named colour

Package: mate-themes Version: 3.22.21-1 Severity: important Tags: upstream GTK 3.24.22 introduced a new named colour, @text_view_bg, which the vte terminal library has started to rely on, causing misrendering in themes that do not define it (see ).

Bug#970980: numix-gtk-theme: does not define @text_view_bg named colour

Package: numix-gtk-theme Version: 2.6.7-5 Severity: important Tags: upstream GTK 3.24.22 introduced a new named colour, @text_view_bg, which the vte terminal library has started to rely on, causing misrendering in themes that do not define it (see

Bug#970979: find uses of update-alternatives in maintainer scripts

Package: lintian Version: 2.95.0 Severity: wishlist X-Debbugs-Cc: nthyk...@debian.org Recent versions of lintian have a mechanism for installing alternatives that does not involve modifying maintainer scripts. (https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=45614) It would be useful if

Bug#970978: RFS: streamlink/1.6.0+dfsg-1 -- CLI for extracting video streams from various websites to a video player

Le 26/09/2020 à 00:43, Alexis Murzeau a écrit : > Package: sponsorship-requests > Severity: normal > > Dear mentors, > > I am looking for a sponsor for my package "streamlink" for a new > upstream version 1.6.0. > > [...]> > Changes since the last upload to unstable: > streamlink (1.6.0+dfsg-1)

Bug#970966: python-cartopy: autopkgtest must be marked superficial

Hi, On closer look, it looks like you have a different problem with autopkgtest. You have a test script which is called "python3", but you are doing "Test-Command: python3", so that is not executing your test script but is executing "/usr/bin/python3". Please modify your "debian/tests/control"

Bug#844025: sslscan: static build

On Fri, 11 Nov 2016 22:38:31 +0100 Stefan Pietsch wrote: > sslscan in Debian unstable does not support SSLv2 and v3. sslscan just re-entered Debian, could you re-check this? -- bye, pabs https://wiki.debian.org/PaulWise signature.asc Description: This is a digitally signed message part

Bug#964484: RM: aewm -- RoQA; orphaned; dead upstream; ftbfs with gcc-10; alternatives exist

HI Chris, On Fri, Sep 25, 2020 at 10:58 AM Chris Hofstaedtler wrote: > > Apparently people do maintain aewm somehow, but they really > should step up as Maintainer: then. I do not have any specific interest in aewm and I don't use it also. It just came up in my udd query as it had a RC bug.

Bug#970978: RFS: streamlink/1.6.0+dfsg-1 -- CLI for extracting video streams from various websites to a video player

Package: sponsorship-requests Severity: normal Dear mentors, I am looking for a sponsor for my package "streamlink" for a new upstream version 1.6.0. * Package name: streamlink Version : 1.6.0+dfsg-1 Upstream Author : Streamlink Team * URL :

Bug#970977: tilda: shell doesn't launch

Package: tilda Version: 1.5.2-1 Severity: important Dear Maintainer, A recent upgrade in the last few days broke tilda in testing, at least on my end. When launching tilda the shell doesn't show up, there's only a blinking cursor in the top left. The menu and configuration options are

Bug#970944: ITP: libsejda-commons-java -- common classes for PDFsam and Sejda

Package: wnpp Severity: wishlist Owner: Markus Koschany X-Debbugs-Cc: debian-de...@lists.debian.org * Package name: libsejda-commons-java Version : 1.1.4 Upstream Author : Sober Lemur S.a.s. di Vacondio Andrea * URL : https://github.com/torakiki/sejda-commons *

Bug#970933: geary: autopkgtest regression: Expected: geary: 3.38.0.1 Got: geary: 3.38.0

On Fri, 25 Sep 2020 at 21:31:02 +0200, Paul Gevers wrote: > autopkgtest [06:10:02]: test version: [--- > Expected: geary: 3.38.0.1 > Got: geary: 3.38.0 > autopkgtest [06:10:03]: test version: ---] This appears to be because the upstream tarball is

Bug#970762: in package pciutils marked as pending

Hi! On Fri, 2020-09-25 at 20:44:54 +0200, Daniel Leidert wrote: > Control: reopen 970762 > > Am Mittwoch, den 23.09.2020, 03:13 +0200 schrieb Guillem Jover: > > --- > > commit c2c28549a513b93898d8c49f6eb8cefc1670a1e2 > > Author: Guillem Jover > > Date: Wed Sep 23 03:00:35 2020 +0200 > > > >

Bug#970927: Subject: 'mono' returns an 'Unhandled Exception'

Package: mono Version: 6.8.0.105+dsfg-2 Maintainers: Debian Mono Group Attempting to run a mono application on command line returns: Unhandled Exception: System.IO.FileNotFoundException: Could not load file or assembly 'System.Windows.Forms, Version=4.0.0.0, Culture=neutral,

Bug#968335: kernel hangs on linux-image-4.19.0-10-amd64

I have also seen a number of systems hang after upgrading to this kernel version. It appears to happen when the system has docker containers running, possibly related to the virtual ethernet devices. On some systems, I can trigger the bug within an hour or two of uptime. Rolling back to

Bug#970943: googletest: Please package post-2020-09-20 Git snapshot

Source: googletest Version: 1.10.0-3 Per the current googletest readme [1], googletest has abandoned numbered releases. Since the last numbered release, upstream has added support for a few useful features, notably the `GTEST_ALLOW_UNINSTANTIATED_PARAMETERIZED_TEST` macro. Would you be willing to

Bug#970941: f2fs-tools: CVE-2020-6070

Source: f2fs-tools Version: 1.11.0-1.1 Severity: grave Tags: security upstream X-Debbugs-Cc: car...@debian.org, Debian Security Team Hi, The following vulnerability was published for f2fs-tools. CVE-2020-6070[0]: | An exploitable code execution vulnerability exists in the file system |

Bug#970744: ben: please provide machine-parseable version of transition status

On 2020-09-24 15:39:30 +0200, Stéphane Glondu wrote: > Le 23/09/2020 à 20:52, Sebastian Ramacher a écrit : > >>> thanks for maintaining ben. In additiona to the HTML output, it would be > >>> great to have the same information as machine-parseable file. With such > >>> a file one could feed other

Bug#970942: nikwi FTCBFS: builds for the build architecture

Source: nikwi Version: 0.0.20120213-4 Tags: patch User: debian-cr...@lists.debian.org Usertags: ftcbfs nikwi fails to cross build from source, because it does not pass cross tools to make. The easiest way of doing so - using dh_auto_build - does not suffice though as it doesn't pass LD. The LD

Bug#970818: mrpt: FTBFS on mipse64el: E: Build killed with signal TERM after 150 minutes of inactivity

On 2020-09-25 07:58:56 +0200, José Luis Blanco-Claraco wrote: > Thanks for reporting, Sebastian! > > Although, I'm not sure how to proceed in this case... it compiled in > the past but it looks like the builder machine entered into swapping > (?) this time. Reducing the optimization level on

Bug#970940: qemu: CVE-2020-25743

Source: qemu Version: 1:5.1+dfsg-4 Severity: important Tags: security upstream Forwarded: https://lists.nongnu.org/archive/html/qemu-devel/2020-09/msg01568.html X-Debbugs-Cc: car...@debian.org, Debian Security Team Hi, The following vulnerability was published for qemu. CVE-2020-25743[0]: |

Bug#970939: qemu: CVE-2020-25741

Source: qemu Version: 1:5.1+dfsg-4 Severity: important Tags: security upstream Forwarded: https://lists.nongnu.org/archive/html/qemu-devel/2020-09/msg07779.html X-Debbugs-Cc: car...@debian.org, Debian Security Team Hi, The following vulnerability was published for qemu. CVE-2020-25741[0]:

Bug#970938: ruby-gon: CVE-2020-25739

Source: ruby-gon Version: 6.3.2-1 Severity: important Tags: security upstream X-Debbugs-Cc: car...@debian.org, Debian Security Team Hi, The following vulnerability was published for ruby-gon. CVE-2020-25739[0]: | An issue was discovered in the gon gem before gon-6.4.0 for Ruby. | MultiJson

Bug#958910: debci: 'debci setup -a armhf' fails to set up an lxc container on an amd64 host

Hello Antonio, I have no issue with containers of the native amd64 architecture of my system. Setting up and using a i386 container also works flawlessly. I have been using them even before trying to setup a container of a foreign architecture. I seem to have a general issue to setup containers

Bug#970937: qemu: CVE-2020-17380

Source: qemu Version: 1:5.1+dfsg-4 Severity: important Tags: security upstream Forwarded: https://lists.nongnu.org/archive/html/qemu-devel/2020-09/msg01175.html X-Debbugs-Cc: car...@debian.org, Debian Security Team Hi, The following vulnerability was published for qemu. CVE-2020-17380[0]: |

Bug#821207: [nagios-plugins-contrib] check_smtp_send fails when sending with --tls

Hi there, This bug is still present and it's annoying that we can't use the plugin with tls connections because of it. There hasn't been any movement upstream for 8 years now unfortunately. But, thanks to Jan's input, I've tried a simple workaround of just commenting out all of the calls to the

Bug#970935: glib-networking breaks libsoup2.4 autopkgtest: libsoup-2.4/ssl-test.test (Child process killed by signal 5)

Source: glib-networking, libsoup2.4 Control: found -1 glib-networking/2.66.0-1 Control: found -1 libsoup2.4/2.70.0-1 Severity: serious Tags: sid bullseye X-Debbugs-CC: debian...@lists.debian.org User: debian...@lists.debian.org Usertags: breaks needs-update Dear maintainer(s), With a recent

Bug#970934: Please either change or document 0700 permissions on partial directories

Package: apt Version: 2.1.10 Severity: normal X-Debbugs-Cc: j...@joshtriplett.org apt creates /var/cache/apt/archives/partial and /var/lib/apt/lists/partial with mode 0700. An old changelog entry from 2014 mentions doing so, but I haven't found any explanation why these directories couldn't be

Bug#970933: geary: autopkgtest regression: Expected: geary: 3.38.0.1 Got: geary: 3.38.0

Source: geary Version: 3.38.0.1-3 X-Debbugs-CC: debian...@lists.debian.org Severity: serious User: debian...@lists.debian.org Usertags: regression Dear maintainer(s), With a recent upload of geary the autopkgtest of geary fails in testing when that autopkgtest is run with the binary packages of

Bug#970932: ruby-oauth: CVE-2016-11086

Source: ruby-oauth Version: 0.5.4-1 Severity: important Tags: security upstream Forwarded: https://github.com/oauth-xx/oauth-ruby/issues/137 X-Debbugs-Cc: car...@debian.org, Debian Security Team Hi, The following vulnerability was published for ruby-oauth. CVE-2016-11086[0]: |

Bug#966200: closed by Timo Aaltonen (Re: [Pkg-freeipa-devel] Bug#966200: CVE-2020-1722)

Hi, > this was fixed, dunno why the bug wasn't closed automatically Doesn't look the upload hit the archive afaics. At least neither https://tracker.debian.org/pkg/freeipa nor snapshots.d.o knows about the 4.8.8-1 upload. Regards, Salvatore

Bug#905068: ITP: dqlite -- High-availability SQLite with Raft consensus

Control: owner 905068 ! Make it right.

Bug#905068: ITP: dqlite -- High-availability SQLite with Raft consensus

Control: retitle 905068 ITP: dqlite -- High-availability SQLite with Raft consensus Control: owner 905068 ! Going to upload it soon and plan to maintain it in the long run. Clément acknowledged the ITP takeover.

Bug#970762: in package pciutils marked as pending

Control: reopen 970762 Am Mittwoch, den 23.09.2020, 03:13 +0200 schrieb Guillem Jover: [..] > --- > commit c2c28549a513b93898d8c49f6eb8cefc1670a1e2 > Author: Guillem Jover > Date: Wed Sep 23 03:00:35 2020 +0200 > > Force the hardlink for the backup pci.ids database in update-pciids >

Bug#966985: Bug#970410: src:html5lib: fails to migrate to testing for too long: autopkgtest regressions

Hi Sandro, On 24-09-2020 17:21, Sandro Tosi wrote: >> Thank you for the recent upload. Unfortunately, your package still can't >> migrate because it causes a FTBFS/autopkgtest regression in >> python-bleach (hence in CC). >> >>> This bug will trigger auto-removal when appropriate. As with all new

Bug#970398: xfwm4: Since 4.14.5-1 I get a garbled desktop

Dear Maintainer, * Elimar Riesebieter [2020-09-15 18:35 +0200]: > Package: xfwm4 > Version: 4.14.5-1 > Severity: important > Tags: patch I've build 4.14.5-2 as proposed from Unit 193 privately on irc and these three patches are fixing my issue. I assume they are the last commits of the

Bug#970931: dacs FTCBFS: configures for the build architecture

Source: dacs Version: 1.4.40-2 Tags: patch User: debian-cr...@lists.debian.org Usertags: ftcbfs dacs fails to cross build from source, because it does not pass --host to configure. The easiest way of fixing that - using dh_auto_configure - does not work here, because the configure script does not

Bug#970930: gnome-shell-extension-panel-osd FTCBFS: configures for the build architecture

Source: gnome-shell-extension-panel-osd Version: 1.0.46.g28656ac-2 Tags: patch User: debian-cr...@lists.debian.org Usertags: ftcbfs gnome-shell-extension-panel-osd fails to cross build from source, because it configures for the build architecture. It actually configures twice: Once via autogen.sh

Bug#970929: libnfc-bin: nfc-mfclassic only writes first 16bytes of each sector

Package: libnfc-bin Version: 1.8.0-2 Severity: important Dear Maintainer, nfc-mfclassic does not write anything beside the first 16 bytes of each sector. All other blocks are empty (0x00) and keys are not written either. No errors are output neither on read nor write. (the cards work just fine

Bug#970928: firefox: please run js regression test suite at build-time

Package: firefox Version: 81.0-2 Severity: wishlist It would be useful if firefox (but not -esr) ran the upstream test suite for SpiderMonkey (js) on buildds, ideally with failures causing FTBFS. Otherwise, the GNOME team (which needs to repackage -esr versions of mozjs for gjs, on a cycle that

Bug#965046: PATCH

The upstream fix can be found at https://gitlab.kitware.com/cmake/cmake/-/merge_requests/5258/diffs

Bug#970926: Package: dokuwiki Upstream released new version.

Package: dokuwiki Version: 0.0.20180422.a-2 (Release 2018-04-22c “Greebo”) Upstream release : Release 2020-07-29 “Hogfather” ChangeLog : https://www.dokuwiki.org/changes Thank you -- Ketan Patel Cell : (816)277-9917

Bug#970925: hexchat: underscore-character glaphs doesn't appear in hexchat chat widget

Package: hexchat Version: 2.14.3-3 Severity: normal X-Debbugs-Cc: osma...@gmail.com Dear Maintainer, * What led up to the situation? sending something contains underscore character (_) in hexchat, with any font (only in chat widget , the rest of application UI is not effected) *

Bug#592519: initramfs-tools: COMPRESS option should be more flexible

Package: initramfs-tools Version: 0.139 Followup-For: Bug #592519 X-Debbugs-Cc: b...@debian.org, m...@debian.org, debian-ker...@lists.debian.org Hi. In a similar vein to what was reported by Roger Shimizu, it takes ages to compress with xz on an armel system with only 128MB of RAM. By default,

Bug#970812: closed by Daniel Echeverri (Re: Bug#970812: glances: systemd service starting unrestricted listener on 0.0.0.0:61209 by default)

Hi Salvatore! El jue., 24 de sep. de 2020 a la(s) 23:24, Salvatore Bonaccorso ( car...@debian.org) escribió: > Hi Daniel, > > > Hi! > > > > El mié., 23 de sep. de 2020 a la(s) 12:54, compositiv GmbH ( > > i...@compositiv.com) escribió: > > > > > Package: glances > > > Version: 3.1.0-1 > > >

Bug#970924: please upgrade pcmanfm to version 1.3.1-3

Package: pcmanfm Version: 1.3.1-1+b1 Currently pcmanfm in Bullseye is at version 1.3.1-1, which contains a bug causing: "a stop job is running" for 90s during shutdown. This happens, when logging out with shutdown from LXDE. Apparently this behaviour has been fixed with version 1.3.1-3. Thanks

Bug#944738: [Openjdk] Bug#944738: jlink: Hash of module differs to expected hash recorded in java.base

* Julian Gilbey: > On Fri, Sep 25, 2020 at 06:22:33PM +0200, Florian Weimer wrote: >> * tony mancill: >> >> > I had already prepared the NMU for openjdk-15 - building first without >> > the patch and then with it so I could test with both - so I will go >> > ahead and upload that package today.

Bug#944738: [Openjdk] Bug#944738: jlink: Hash of module differs to expected hash recorded in java.base

On Fri, Sep 25, 2020 at 06:22:33PM +0200, Florian Weimer wrote: > * tony mancill: > > > I had already prepared the NMU for openjdk-15 - building first without > > the patch and then with it so I could test with both - so I will go > > ahead and upload that package today. > > There's also an

Bug#970911: gnome-screenshot: does not start: undefined symbol: hdy_init

Hello, Indeed I had a copy in /usr/local/ that I don't remember installing. Sorry for this bug report. Michel Le Bihan Le vendredi 25 septembre 2020 à 13:01 +0100, Simon McVittie a écrit : > Control: tags -1 + moreinfo unreproducible > > On Fri, 25 Sep 2020 at 13:02:20 +0200, Michel Le Bihan

Bug#970420: python dependencies now uninstallable

Matthias Klose wrote: > there are *no* packages in testing depending on python. Well there are so many people that run on unstable and for them a considerable number of packages became uninstallable (respectively python2 won't upgrade anymore, thus potentially lacking any security updates added

Bug#959815: When are maintscript entries obsolete?

What would be a good way to determine that a maintscript entry is obsolete? One way I can think of is to look at prior-version and see if at least that version is present in $COMPAT_RELEASE (e.g. oldstable). Do you have suggestions as to what to do for lines where prior-version is not present? We

Bug#944738: [Openjdk] Bug#944738: jlink: Hash of module differs to expected hash recorded in java.base

* tony mancill: > I had already prepared the NMU for openjdk-15 - building first without > the patch and then with it so I could test with both - so I will go > ahead and upload that package today. There's also an upstream change to honor SOURCE_DATE_EPOCH: commit

Bug#970923: libwolfssl-dev: not multiarch compatible

Package: libwolfssl-dev Version: 4.5.0+dfsg-2 wolfssl-dev is marked as "Multi-Arch: same" but includes the options.h for wolfssl any cyassl which differs over the architectures. One difference can be eliminated by passing --enable-base64encode on configuration. The other one is the

Bug#970520: wesnoth: Crash on starting wesnoth - stack smash detected

The game can be started with the following command: $ wesnoth --nocache I'm not a Wesnoth player, so I don't know if all work correctly after it start. Ciao Davide

Bug#970922: wolfssl-dev: not multiarch compatible

Package: wolfssl-dev Version: 4.5.0+dfsg-2 wolfssl-dev is marked as "Multi-Arch: same" but includes the options.h for wolfssl any cyassl which differs over the architectures. One difference can be eliminated by passing --enable-base64encode on configuration. The other one is the HAVE___UINT128_T

Bug#970921: error: PyCapsule_GetPointer called with incorrect name

Package: calibre Version: 4.99.12+dfsg+really4.23.0-1 Severity: grave Justification: renders package unusable Dear Maintainer, calibre fails to start with this error: ``` Traceback (most recent call last): File "/usr/bin/calibre", line 20, in sys.exit(calibre()) File

Bug#950198: Fixing build with jami_20191214.1.07edb5e

Alexandre Viau writes: > Hello! > > Thank you very much for helping! > Cheers! > > It looks like you made your changes alongside updates to the upstream > source. > > Sadly I won't merge any changes to the upstream sources. I'll handle > these myself with git-buildpackage. > Indeed. I now

Bug#970920: lintian: spurious no-dh-sequencer with build profile conditionals

Package: lintian Version: 2.95.0 Severity: normal lintian fails to recognize this debian/rules construct as use of the dh sequencer: %: ifeq ($(DEB_BUILD_PROFILE),stage1) dh $@ -Npackage-doc else dh $@ endif This functionally equivalent construct *is* recognized: DH_OPTIONS =

Bug#934809: opus 1.3.1 available

Control: tags -1 + pending On Wed, Sep 16, 2020 at 09:40:31PM +0300, Dmitry Shachnev wrote: > I can confirm that opus 1.3.1 builds fine without any packaging changes, > and there are no new Lintian warnings. > > Will you mind if I NMU it? I have just uploaded the NMU to DELAYED/1. The only

Bug#944738: [Openjdk] Bug#944738: jlink: Hash of module differs to expected hash recorded in java.base

On Fri, Sep 25, 2020 at 03:51:38PM +0100, Julian Gilbey wrote: > On Thu, Sep 24, 2020 at 05:21:46PM -0700, tony mancill wrote: > > On Thu, Sep 24, 2020 at 10:52:50AM +0100, Julian Gilbey wrote: > > > Great, and there's a bug report #944738 > > >

Bug#970911: gnome-screenshot: does not start: undefined symbol: hdy_init

Package: gnome-screenshot Version: 3.38.0-1 Severity: grave Justification: renders package unusable Hello, When trying to launch gnome-screenshot, I get this error: michel@debian:~$ gnome-screenshot --interactive gnome-screenshot: symbol lookup error: gnome-screenshot: undefined symbol:

Bug#950198: Fixing build with jami_20191214.1.07edb5e

Hello! Thank you very much for helping! It looks like you made your changes alongside updates to the upstream source. Sadly I won't merge any changes to the upstream sources. I'll handle these myself with git-buildpackage. Can you please submit your opendht changes again, this time only

Bug#944738: [Openjdk] Bug#944738: jlink: Hash of module differs to expected hash recorded in java.base

On Thu, Sep 24, 2020 at 05:21:46PM -0700, tony mancill wrote: > On Thu, Sep 24, 2020 at 10:52:50AM +0100, Julian Gilbey wrote: > > Great, and there's a bug report #944738 > > (https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=944738) for > > openjdk-11; I haven't checked if there are bugs reported

Bug#964125: calibre: Please switch from sip4 to sip5

Hi Norbert! On Fri, Sep 25, 2020 at 11:26:25AM +0900, Norbert Preining wrote: > Hi Dmitry, > > > And this is done now. PyQt5 in unstable now uses SIP 5. > > Is this also the reason why calibre is now broken? Yes. I am again sorry for this disruptive change, but it had to happen sooner or later.

Bug#970895: duecredit: new upstream release available

On Fri, 25 Sep 2020, Yaroslav Halchenko wrote: > I see that in april of this year I looked into updating the package, it > needed rnc2rng. I have packaged it. And it is in Debian now: > python3-rnc2rng FTR, uploaded rnc2rng 2.6.4 and now waiting for it to appear since citeproc 0.5.1 needs >=

Bug#969717: libgl1-mesa-dri: Champions of Regnum display deteriorates after libgl1-mesa-dri upgrade to 20.1.7-1

So I just tried with the version 20.2.x from experimental. Things are even worse : the game crashes at once after login credentials have been entered (segfault). I do not get the welcome screen where you can choose which one of your character you want to play. With sid version and other

Bug#970895: duecredit: new upstream release available

On 2020-09-25 21:19, Yaroslav Halchenko wrote: On Fri, 25 Sep 2020, Drew Parsons wrote: Source: duecredit Severity: normal I'm getting problems running tests for mdanalysis with some broken citations generated by duecredit, see https://github.com/MDAnalysis/mdanalysis/issues/2954 yikes,

Bug#950198: Fixing build with jami_20191214.1.07edb5e

Hello Alexandre, all, I recently joined the Jami team at SFL, and I'm also the newly-appointed GNU (co)maintainer for Jami. I would like to help improve the situation with the Jami package in the official Debian repositories however I can. I think the first step would be getting more recent

Bug#970912: Fails to upgrade: version `NCURSES6_TINFO_6.2.current' not found (required by /lib/x86_64-linux-gnu/libncurses.so.6)

Control: reassign -1 cowdancer Control: forcemerge 970555 -1 On 2020-09-25 13:28 +0200, Michael Biebl wrote: > Package: libncurses6 > Version: 6.2+20200918-1 > Severity: serious > > Today I tried to upgrade my cowbuilder chroots. > This failed with the following error message: > > Preparing to

Bug#970768: torbrowser-launcher: error while checking version number after TorBrowser 10.0 release

On Thu, Sep 24, 2020 at 1:49 PM Lev Lamberov wrote: > > I've installed torbrowser-launcher from experimental and can confirm > that it works properly for me. Thanks for you work on it! Dear Lev, Thanks for your confirmation! I uploaded -14 to unstable and buster-backports. So for debian it

  1   2   >