Bug#959075: Still not working on Debian testing

On Fri, 3 Jul 2020 11:15:30 +0200 richard lucassen wrote: > Ok, two remaining cometic issues in 2.11 than :-) Sounds like the issue is fixed then, marked it as fixed. > # ifup bond0 > /etc/network/if-pre-up.d/ifenslave: 39: echo: echo: I/O error > /etc/network/if-pre-up.d/ifenslave: 39: echo:

Bug#963971: [Pkg-samba-maint] Bug#963971: samba-libs: libndr.so.0 gone from latest version, breaks sssd-ad-common dependency

clone 963971 -1 tag 963971 + upstream tag -1 + upstream fixed-upstream patch reassign -1 sssd-ad-common Le lun. 29 juin 2020 à 14:48, Michael Stone a écrit : > > Package: samba-libs > Version: 2:4.12.3+dfsg-2 > Severity: critical > Justification: breaks the whole system > > The new samba-libs

Bug#919619: [Pkg-utopia-maintainers] Bug#919619: NM 1.24.0 now has basic support for hidden networks with iwd backend

On Sat, Jul 04, 2020 at 12:42:57AM +0200, Michael Biebl wrote: > Am 04.07.20 um 00:16 schrieb Jonas Smedegaard: > > Then how about _not_ recommend iwd but just lower from depending on > > wpasupplicant to only recommending it. Because that's what it is: > > Recommended for all except special

Bug#964238: Please package 0.17.2

Package: wnpp Severity: wishlist Owner: Alexandre Viau Hello! Would you please upload 0.17.2? It looks like Syncthing needs a newer version of quic-go. Cheers, -- Alexandre Viau av...@debian.org signature.asc Description: OpenPGP digital signature

Bug#964234: dpkg-source: Considers missing symlink targets directory traversals

Control: reassign -1 dpkg-dev Control: retitle -1 dpkg-source: Considers missing symlink targets directory traversals Control: found -1 1.20.0 On Sat, 2020-07-04 at 01:20:18 +0200, Andreas Beckmann wrote: > Source: dpkg,firmware-nonfree > Version: 20190717-2 > Severity: serious > Tags: ftbfs >

Bug#964111: dpkg-source: False positive 'points outside source root'

On Fri, 2020-07-03 at 05:27:46 -0700, Felix Lechner wrote: > Why did you lower the severity instead of releasing a fix? As explained, because the severity seemed off. Also because there are still other regressions being dealt with… > If version 1.20.3 progresses to testing, Lintian loses its

Bug#964111: dpkg-source: False positive 'points outside source root'

Hi! On Fri, 2020-07-03 at 14:12:10 +, Holger Levsen wrote: > not sure if this is the same bug or just a similar one: Yeah, related, but not entirely the same. > [...] > dpkg-source: info: extracting munin in munin-2.0.63 > dpkg-source: info: unpacking munin_2.0.63.orig.tar.gz > dpkg-source:

Bug#964237: subversion-tools: svn-hot-backup does not work with python 3

Package: subversion-tools Version: 1.14.0-1 Severity: normal Tags: patch There are a couple of bugs in the svn-hot-backup script, probably related to the upgrade to python 3 See patch below: --- svn-hot-backup 2020-06-03 19:21:57.0 -0700 +++ /usr/bin/svn-hot-backup 2020-07-03

Bug#964233: ifupdown: interfaces man page wrong example for /etc/network/interfaces

Package: ifupdown Version: 0.8.35 Severity: normal In /usr/share/man/man5/interfaces.5.gz the following example is giving for auto eth0 allow-hotplug eth1 iface eth0 inet dhcp iface eth0 inet6 auto iface eth1 inet static address 192.168.1.2/24

Bug#964177: chromium: high cpu load and frequent crashes

On Fri, Jul 3, 2020 at 3:39 AM Alexis Huxley wrote: > I've got Debian 10 and apply nightly updates as they become > available. I was running chromium version 80.0.3987.162 but > that was upgraded to 83.0.4103.116 a couple of nights ago. Since > then CPU load at page load time is very high, the

Bug#940017: crypto-policies: Incomplete debian/copyright?

On Wednesday, September 11, 2019 4:03:59 AM EDT Chris Lamb wrote: > I just ACCEPTed minder from NEW but noticed it was missing attribution > for at least Tomáš Mráz. This bug is against crypto-policies, but it appears you accepted minder too the same day. Did you mean to file this against

Bug#964236: php-redis: After upgrade to php-redis (5.3.0+4.3.0-1), php-fpm crash

Package: php-redis Version: After upgrade to php-redis (5.3.0+4.3.0-1), php-fpm crash Severity: normal Dear Maintainer, After upgrade to php-redis (5.3.0+4.3.0-1), php-fpm crash. traps: php-fpm7.4[198823] general protection fault ip:55da0ea4c634 sp:7ffc14657008 error:0 in

Bug#964214: libdebhelper-perl: dh_auto_configure cannot do out-of-tree builds for qmake buildsystem

severity 964214 wishlist tags 964214 + help thanks Hi Niels, >Interesting. I am not sure out of source builds have ever been >supported by qmake (at least not correctly at any rate). If you know >how to do it, then I am happy to look at fixing it. this is my first contact with qmake either,

Bug#964025: berusky2: New upstream release

I just realized that readme-debian-mode added my name to README.Debian, because I removed an entry. You can change/remove that if you wish. -- Hi! I'm a .signature virus! Copy me into your ~/.signature to help me sprea= d! I prefer to send and receive mail

Bug#714454: ITP: polyphone -- soundfont editor (.sf2 format 2.01 and 2.04)

tags 714454 + pending thanks Dixi quod… >Packaging status: repository at >https://evolvis.org/plugins/scmgit/cgi-bin/gitweb.cgi?p=alioth/polyphone.git;a=summary Updated. >We’re currently held up by some licencing issues: > >• https://github.com/davy7125/polyphone/issues/105 (showstopper, >

Bug#964234: dpkg,firmware-nonfree: cannot unpack: dpkg-source: error: pathname 'firmware-nonfree-20190717/debian/config/libertas/sd8688_helper.bin' points outside source root

Hi Andreas, > dpkg-source: error: pathname > points outside source root Maybe the same as Bug#964111? Kind regards Felix Lechner

Bug#964235: Patch for error in bsdgames Trek that prevents visual command from working under some circumstances

Package: bsdgames Version: 2.17-28 Severity: normal Dear Debian maintainers, I was playing the old Trek game from the Debian bsdgames package, and I've identified a bug. I've patched it on my system, and the patch solves the problem. I sent a merge request to Debian Salsa about 6 months ago

Bug#778750: theme still broken, problem with directory structure and symlink

Hi Ivan Sergio, On Fr 03 Jul 2020 18:41:19 CEST, Ivan Sergio Borgonovo wrote: I've just read more carefully your follow up: The theming folder in /etc/ also needs to be moved a bit: /etc/horde/themes-available.d/default -> /etc/horde/themes-available.d/default/horde OK, it was on

Bug#778750: theme still broken, problem with directory structure and symlink

On Fr 03 Jul 2020 18:41:19 CEST, Ivan Sergio Borgonovo wrote: I've just read more carefully your follow up: The theming folder in /etc/ also needs to be moved a bit: /etc/horde/themes-available.d/default -> /etc/horde/themes-available.d/default/horde OK, it was on purpose... but it

Bug#778750: theme still broken, problem with directory structure and symlink

Hi, thanks for testing the upgrade. Sorry that it failed again. Let's see... On Fr 03 Jul 2020 18:29:40 CEST, Ivan Sergio Borgonovo wrote: I just safe-upgraded some stuff and I came across 2 different problems: 1) dpkg: warning: unable to delete old directory

Bug#964234: dpkg,firmware-nonfree: cannot unpack: dpkg-source: error: pathname 'firmware-nonfree-20190717/debian/config/libertas/sd8688_helper.bin' points outside source root

Source: dpkg,firmware-nonfree Version: 20190717-2 Severity: serious Tags: ftbfs Justification: fails to build from source Control: found -1 20190717-2 Control: found -1 1.20.3 Hi, src:firmware-nonfree fails to unpack in sid with latest dpkg: dpkg-source: info: extracting firmware-nonfree in

Bug#964187: cryptsetup: takes one minute to unlock the disk with a passphrase

On Sat, 04 Jul 2020 at 00:54:53 +0200, Vincent Lefevre wrote: > I suppose that's > > wait_for_dropbear() { > […] > } > > Couldn't it also check whether the user has typed the passphrase, > and quit in this case? That would introduce back the race condition described in #943459.

Bug#964200: apt-listbugs: transient frozen string error

On Fri, 03 Jul 2020 18:40:09 +0200 Christoph Anton Mitterer wrote: > On Fri, 2020-07-03 at 18:08 +0200, Francesco Poli wrote: [...] > > What is "en_DE.UTF-8", exactly? [...] > > Could this non-existent locale maybe confuse the ruby-unicode > > library? > > No it is existent... it's just my own

Bug#964208: wsjtx: FTBFS without internet access

Hi Niko, On Fri, Jul 03, 2020 at 07:47:21PM +0300, Niko Tyni wrote: > Source: wsjtx > Version: 2.2.1+repack-1 > Severity: serious > Tags: ftbfs > > This package fails to build on a system without internet access. > I suppose it's xsltproc calling out for external resources or something > like

Bug#964187: cryptsetup: takes one minute to unlock the disk with a passphrase

On 2020-07-04 00:30:04 +0200, Guilhem Moulin wrote: > On Sat, 04 Jul 2020 at 00:18:59 +0200, Vincent Lefevre wrote: > > Note that /usr/share/doc/dropbear-initramfs/README.initramfs > > says at the end: > > > > This is non-blocking for the startup process, so when you are at the > > console you

Bug#919619: [Pkg-utopia-maintainers] Bug#919619: NM 1.24.0 now has basic support for hidden networks with iwd backend

Am 04.07.20 um 00:16 schrieb Jonas Smedegaard: > Then how about _not_ recommend iwd but just lower from depending on > wpasupplicant to only recommending it. Because that's what it is: > Recommended for all except special situations. For now... Right? Hm, no. That's exactly the situation I

Bug#963996: /usr/bin/unzip: Bomb detection fails with out of memory error when extracting bzip2-compressed files

I researched this a bit more and found that Mark Adler patched this in his fork. See and .

Bug#963939: lintian: breakout-link wrongly reported against jar files

Control: tags -1 - pending Hi Chris, On Fri, Jul 3, 2020 at 1:02 PM Chris Lamb wrote: > > Please go ahead. https://salsa.debian.org/lintian/lintian/-/commit/8016b7d681f5b1e5a1864ac7d88da4c29fc73af7 I'll try to remember to reopen if you release before this is resolved. Kind regards Felix

Bug#964187: cryptsetup: takes one minute to unlock the disk with a passphrase

Control: reassign -1 dropbear-initramfs 2020.79-1 Control: retitle -1 dropbear-initramfs: init-bottom blocks for 1 minute when there is no link Control: severity -1 normal On Sat, 04 Jul 2020 at 00:18:59 +0200, Vincent Lefevre wrote: > Note that /usr/share/doc/dropbear-initramfs/README.initramfs

Bug#964215: libwolfssl-dev: #warning "For timing resistance / side-channel attack prevention consider using harden options"

Hi Thorsten, On Fri, Jul 3, 2020 at 3:26 PM Thorsten Glaser wrote: > > Whoa, I didn’t mean you had to upload, right today, just for that ☻ > but thanks anyway. wolfSSL is seeing an increase in popularity. By uploading, I hoped to avoid additional uncertainty about the compatibility mode. Kind

Bug#963824: No crash with wayland

For what it's worth: If I run sway/wayland, the bug doesn't happen. -- Markus Grunwald https://www.the-grue.de/~markus/markus_grunwald.gpg

Bug#961792: balsa: needs to set expected server identity (for CVE-2020-13645)

Version: 2.6.1-1 Control: notfound 961792 2.5.6-2 Control: notfound 961792 2.4.12-3+b1 On Thu 2020-06-25 10:18:54 +0100, Simon McVittie wrote: > On Fri, 29 May 2020 at 11:24:06 +0100, Simon McVittie wrote: >> If I'm reading https://gitlab.gnome.org/GNOME/glib-networking/-/issues/135 >> and

Bug#964215: libwolfssl-dev: #warning "For timing resistance / side-channel attack prevention consider using harden options"

Dixi quod… >Might wish to keep it open until there’s sufficient documentation >in the package itself. If you disagree, close it, no complains. Whoa, I didn’t mean you had to upload, right today, just for that ☻ but thanks anyway. Good night, //mirabilos -- 15:41⎜ Somebody write a testsuite for

Bug#964187: cryptsetup: takes one minute to unlock the disk with a passphrase

On 2020-07-03 16:12:49 +0200, Guilhem Moulin wrote: > On Fri, 03 Jul 2020 at 12:53:17 +0200, Vincent Lefevre wrote: > > I don't know really where the problem comes from, but it now takes > > one minute to unlock the disk of my laptop with a passphrase. Well, > > I'm not sure whether this comes

Bug#964214: libdebhelper-perl: dh_auto_configure cannot do out-of-tree builds for qmake buildsystem

Thorsten Glaser: > Package: libdebhelper-perl > Version: 13.1 > Severity: normal > > Apparently, dh7 fails to tell qmake the location of the source directory > when attempting an out-of-tree build: > > > […] > > > The qmake invocation syntax error message is somewhat misleading, > but looking

Bug#919619: NM 1.24.0 now has basic support for hidden networks with iwd backend

Quoting Michael Biebl (2020-07-03 21:50:36) > Hi, > > On Tue, 26 May 2020 13:10:27 +0200 Andreas Henriksson > wrote: > > Just wanted to drop a comment about the iwd status in NM. > > NM has since 1.24.0, which is now in testing/unstable, basic > > support for connecting to a hidden network using

Bug#961195: transition: glibc

On 2020-06-04 14:08, Matthias Klose wrote: > On 6/4/20 2:05 PM, Aurelien Jarno wrote: > > On 2020-06-04 13:06, Matthias Klose wrote: > >> On 5/21/20 11:39 AM, Aurelien Jarno wrote: > >>> Package: release.debian.org > >>> Severity: normal > >>> User: release.debian@packages.debian.org > >>>

Bug#964230: debhelper: dh_missing conflicts with global --sourcedir option

Thorsten Glaser: > Package: debhelper > Version: 13.1 > Severity: important > > Something for debhelper compat 14 ;-) > > I’m packaging a piece of s…oftware whose main buildsystem entry > is in a subdirectory so I’m using --sourcedir=thatsubdir in the > call to dh7. > > The build then fails

Bug#929272: nmap-common: executable distributed in nmap-common detected as malware

* Samuel Henrique: > Looking at nmap changelog, it seems like this issue has been going > back and forth[0] and had stabilized after some point (I guess that's > when most AV vendors added the signature), this means that any changes > in the compilation might trigger the issue again. > > Hilko,

Bug#964232: ITP: fairy-stockfish -- chess variant engine derived from Stockfish, including Shogi and XiangQi support

Package: wnpp Severity: wishlist Owner: Yann Dirson * Package name: fairy-stockfish Version : 11.1 Upstream Author : Fabian Fichter (unknown email) * URL : https://github.com/ianfab/Fairy-Stockfish * License : GPLv3+ Programming Lang: C++ Description :

Bug#964231: faketime: FTBFS with glibc 2.31 due to ftime deprecation

Package: faketime Version: 0.9.7-3 Severity: important Tags: patch upstream faketime fails to build from source with glibc 2.31: | gcc -c -std=gnu99 -Wall -DFAKE_STAT -Werror -Wextra timetest.c | ./testframe.sh functests | # Begin Test Suites in functests | | # Begin

Bug#322694: www.debian.org: Missing link to hd-media/boot.img.gz

Control: tags -1 + pending Marvin Stark wrote (12 Aug 2005 10:38:35 +0200): > I'am missing the link to hd-media/boot.img.gz in the tutorial howto boot > debian from a > USB-Memory-Stick(http://www.debian.org/releases/stable/i386/ch04s04.html.de). > It would be nice if you include the link to

Bug#961676: 5.6 kernel crashes host when using VFIO on KVM guests

Done some more digging. I can boot my macos vm using QXL instead of a passthrough GPU, even if i passthrough the USB device (not pci controller). So its definitely only passing through PCI devices like graphics cards that breaks things. So this works in qemu terms: -usb -device

Bug#900739: crashing in toke.c, keyword plugin pointer is left pointing to an XS module that's been unloaded

Thanks. The fix hasn't been integrated into the 5.24 maint branch so any data we can have about it being battle tested is valuable. Dominic. On Thu, Jul 02, 2020 at 05:04:10PM -0700, Dean Hamstead wrote: > We have been running it in prod since before the ticket was raised in > debian. We were

Bug#964177: Also affects testing/sid

found 964177 83.0.4103.116-2 thanks Upgraded chromium and its dependencies to testing and segfaults/crashes remain. -- Boyd Stephen Smith Jr. ,= ,-_-. =. b...@iguanasuicide.net ((_/)o o(\_)) ICQ: 514984 YM/AIM: DaTwinkDaddy `-'(. .)`-'

Bug#779736: Note on manpage

If you could add a note about this to the manpage, I'd appreciate that Thanks! -Calum

Bug#964230: debhelper: dh_missing conflicts with global --sourcedir option

On Fri, 3 Jul 2020, Thorsten Glaser wrote: > Of course, dh_missing’s --sourcedir cannot be renamed within > a compat level. But it should, for the next one. Others, like dh_install, also misuse --sourcedir. bye, //mirabilos -- «MyISAM tables -will- get corrupted eventually. This is a fact of

Bug#964016: js8call: New Upstream Available

Re: Dave Hibberd > I'm happy to prepare an update on salsa, if no one has any objections! Fine with me. Thanks, Christoph

Bug#964230: debhelper: dh_missing conflicts with global --sourcedir option

Package: debhelper Version: 13.1 Severity: important Something for debhelper compat 14 ;-) I’m packaging a piece of s…oftware whose main buildsystem entry is in a subdirectory so I’m using --sourcedir=thatsubdir in the call to dh7. The build then fails because dh_missing complains about every

Bug#964229: purelibc: FTBFS with glibc 2.31 (conflicting gettimeofday prototype)

Source: purelibc Version: 0.4.1-2 Severity: important Tags: patch upstream purelibc fails to build from source with glibc 2.31: | /bin/bash ./libtool --tag=CC --mode=compile gcc -DHAVE_CONFIG_H -I. -Wdate-time -D_FORTIFY_SOURCE=2 -g -ggdb -D_GNU_SOURCE -g -Wall -O0 -c -o

Bug#963887: UDD: 'duck' importer broken since 2020-05-25

Re: Baptiste BEAUPLAT > >> Maybe you could add that to vcswatch? > > The main differences between vcswatch and duck.d.n are: > > - history: duck used to keep 6 runs for each package, reporting only > after 3 failures. vcswatch only keeps the last run. vcswatch could be improved by not notifying

Bug#964228: buster-pu: package nmap/7.70+dfsg1-6+deb10u1

Package: release.debian.org Severity: normal Tags: buster User: release.debian@packages.debian.org Usertags: pu A backported upstream patch [0] is required to fix #940284 [1] on nmap; Bug title: autogeneration of ssl key in ssl server mode of ncat is broken The issue itself is well described

Bug#964218: [Pkg-javascript-devel] Bug#964218: node-yarnpkg: autopkgtest fails with node-uuid 8.2 from experimental - "Cannot read property 'v4' of undefined"

Updating that dependency is already in upsream's TODO list https://github.com/yarnpkg/yarn/issues/6829 .. but they seem to lag on updating dependencies. I guess it would require fixing against this breaking change: https://github.com/uuidjs/uuid/blob/master/CHANGELOG.md#-breaking-changes and

Bug#964227: datefudge: FTBFS with glibc 2.31 (conflicting gettimeofday prototype)

Package: datefudge Version: 1.23 Severity: important Tags: patch upstream datefudge fails to build from source with glibc 2.31 | gcc -Wdate-time -D_FORTIFY_SOURCE=2 -g -O2 -fdebug-prefix-map=/<>=. -fstack-protector-strong -Wformat -Werror=format-security -Wall -Wextra -D_REENTRANT -fpic -c -o

Bug#964226: mandos: 1.8.11-1

Source: mandos Version: 1.8.11-1 Severity: important Tags: patch upstream mandos fails to build from source with glibc 2.31: | g++ -Wdate-time -D_FORTIFY_SOURCE=2 -g -O2 -fdebug-prefix-map=/<>=. -fstack-protector-strong -Wformat -Werror=format-security -fPIC -c -D_GNU_SOURCE

Bug#964225: log4cpp: FTBFS with glibc 2.31 (uses removed stime function)

Source: log4cpp Version: 1.1.3-1 Severity: important Tags: patch upstream log4cpp fails to build from source with glibc 2.31: | g++ -DHAVE_CONFIG_H -I. -I../include -I../include -I../src -Wdate-time -D_FORTIFY_SOURCE=2 -g -O2 -fdebug-prefix-map=/<>=. -fstack-protector-strong -Wformat

Bug#964224: package new upstream snapshot from mob

Source: tcc Severity: wishlist -BEGIN PGP SIGNED MESSAGE- Hash: SHA256 I've found many bugs and quirks are fixed upstream at https://repo.or.cz/w/tinycc.git It's very actively maintained and endorsed by the now-inactive author [1]. tcc is also of interest for bootstrappable builds. They

Bug#964223: linuxtv-dvb-apps: FTBFS with glibc 2.31 (uses removed stime function)

Source: linuxtv-dvb-apps Version: 1.1.1+rev1500-1.2 Severity: important Tags: patch upstream linuxtv-dvb-apps fails to build from source with glibc 2.31: | CC dvbdate | dvbdate.c: In function ‘set_time’: | dvbdate.c:312:6: warning: implicit declaration of function ‘stime’; did you mean ‘ctime’?

Bug#964222: Upstream is dead, please use the new maintained fork

Package: src:clj-yaml-clojure Version: 0.4.0-1 Hi! Upstream is dead, please use the new maintained fork for this package: https://github.com/clj-commons/clj-yaml Cheers, -- ⢀⣴⠾⠻⢶⣦⠀ ⣾⠁⢠⠒⠀⣿⡁ Louis-Philippe Véronneau ⢿⡄⠘⠷⠚⠋ po...@debian.org / veronneau.org ⠈⠳⣄ signature.asc

Bug#953986: nmap-mac-prefixes outdated

Hello Carsten, Thanks for the report, I looked into it and confirmed that this file gets updated with each release of nmap, is there any specific problem you're having with it? Regards, -- Samuel Henrique

Bug#964221: googletest: meson support

Source: googletest Version: 1.10.0-3 googletest is weirdly special in that it is supposed to be compiled together with the project that is being tested, using the same flags. As such it ships with source files and not just a shared library that can be imported using pkg-config. Right now it

Bug#964220: vdr: FTBFS with glibc 2.31 (uses removed stime function)

Source: vdr Version: 2.4.1-4 Severity: important Tags: patch upstream Dear maintainer, vdr fail to build from source with glibc 2.31: | g++ -Wdate-time -D_FORTIFY_SOURCE=2 -g -O2 -fdebug-prefix-map=/<>=. -fstack-protector-strong -Wformat -Werror=format-security -fPIC -c -D_GNU_SOURCE

Bug#929272: nmap-common: executable distributed in nmap-common detected as malware

I just realized I accidentally triggered this issue because I enabled some hardening flags for this executable on the last upload (in testing and sid right now): https://salsa.debian.org/pkg-security-team/nmap/-/commit/e8002cd93757bb8e579821da032beac10245dd05 This change caused the binary to end

Bug#963939: lintian: breakout-link wrongly reported against jar files

Felix Lechner wrote: > > I don't think this warning applies to architecture independent jar files. > > After speaking with others about these links, I am not sure our > existing fix is appropriate. I think it should be reverted until we > hear from Emmanuel. Please go ahead. Regards, --

Bug#964188: chromium: crashes & system crashes after security update to v83

Package: chromium Version: 83.0.4103.116-1~deb10u1 Followup-For: Bug #964188 Dear Maintainer, Had to downgrade from version 83.0.4103.116-1~deb10u1 back to version 80.0.3987.162-1~deb10u1. Initially highly frequent Chromium crashes, hanging & very slowed down. Now it's causing system to crash.

Bug#964215: libwolfssl-dev: #warning "For timing resistance / side-channel attack prevention consider using harden options"

severity 964215 wishlist retitle 964215 libwolfssl-dev: no in-package documentation about necessary extra steps thanks Felix Lechner dixit: >> I did consult the Debian-packaged README, but it >> had no such thing, > >The instructions for the OpenSSL layer are not Debian-specific, but I >will

Bug#919619: NM 1.24.0 now has basic support for hidden networks with iwd backend

Hi, On Tue, 26 May 2020 13:10:27 +0200 Andreas Henriksson wrote: > Just wanted to drop a comment about the iwd status in NM. > NM has since 1.24.0, which is now in testing/unstable, basic > support for connecting to a hidden network using the iwd backend. > > There are still many minor bugs

Bug#963939: lintian: breakout-link wrongly reported against jar files

Hi Chris, > I don't think this warning applies to architecture independent jar files. After speaking with others about these links, I am not sure our existing fix is appropriate. I think it should be reverted until we hear from Emmanuel. Kind regards Felix Lechner

Bug#964215: libwolfssl-dev: #warning "For timing resistance / side-channel attack prevention consider using harden options"

Hi Thorsten, On Fri, Jul 3, 2020 at 12:14 PM Thorsten Glaser wrote: > > I did consult the Debian-packaged README, but it > had no such thing, The instructions for the OpenSSL layer are not Debian-specific, but I will add a note to the README.Debian to bridge the documentation gap. > and the

Bug#964167: Chromium heavily loads the processor and crashes

Another one here, same bug as of this morning after the upgrade to 83. Very high CPU load, even for loading a page like Craigslist. Very clunky response times all around. No crashes yet.

Bug#942754: ITP: volatility3 -- advanced memory forensics framework

retitle 942754 RFS: volatility3 -- advanced memory forensics framework noowner 942754 stop The volatility3 project needs some unlicensed and giant files. I am not sure if it is DFSG. I am dropping it. Eriberto

Bug#947684: ITP: treezy -- Swiss army knife for working with directory and file trees

retitle 947684 RFS: treezy -- Swiss army knife for working with directory and file trees noowner 947684 stop The treezy project didn't take off. I am converting my ITP to an RFS. Eriberto

Bug#964215: libwolfssl-dev: #warning "For timing resistance / side-channel attack prevention consider using harden options"

Felix Lechner dixit: >Did you '#include ' in each file before using the >OpenSSL compatibility headers as described in the instructions? [1] No, of course not. I did consult the Debian-packaged README, but it had no such thing, and the code compiles without it. Why, if this file is so

Bug#964218: node-yarnpkg: autopkgtest fails with node-uuid 8.2 from experimental - "Cannot read property 'v4' of undefined"

Package: node-yarnpkg Version: 1.22.4-3 Severity: important Full build log is attached. This was run in a clean and uptodate lxc container using salsa.debian.org/ruby-team/meta/build script. autopkgtest [18:26:50]: version 5.10 autopkgtest [18:26:50]: host ilvala2; command line:

Bug#963703: gnutls28 3.5.8-5+deb9u5 flagged for acceptance

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

Bug#963614: nfs-utils 1.3.4-2.1+deb9u1 flagged for acceptance

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

Bug#963693: libexif 0.6.21-2+deb9u4 flagged for acceptance

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

Bug#964215: libwolfssl-dev: #warning "For timing resistance / side-channel attack prevention consider using harden options"

Hi Thorsten, On Fri, Jul 3, 2020 at 11:21 AM Thorsten Glaser wrote: > > Just using the library (as OpenSSL drop-in for licence compliance > in Debian terms) produces the following warning: Did you '#include ' in each file before using the OpenSSL compatibility headers as described in the

Bug#964185: freetype2.pc depends on libbrotlidec.pc without a dependency on the libbrotli-dev package

On Fri, 03 Jul 2020 18:45:07 +0900 Mike Hommey wrote: .. > Arguably, freetype2.pc shouldn't depend on libbrotlidec.pc except with a > Required.private, assuming one doesn't actually need to include > libbrotli headers or link against libbrotli library (presumably, that's > the case). The thing

Bug#963205: Next round

Hi Thomas On 2020-07-03 09:47:34 +0200, Thomas Orgis wrote: > I made a new snapshot now. The old one still had a conflict of off_t > and lfs_alias_t in the suffix-less prototype. I hope this does it! > > https://mpg123.org/snapshot > > Verify? Build on both amd64 and i386 and the

Bug#964215: libwolfssl-dev: #warning "For timing resistance / side-channel attack prevention consider using harden options"

Package: libwolfssl-dev Version: 4.4.0+dfsg-5 Severity: normal Just using the library (as OpenSSL drop-in for licence compliance in Debian terms) produces the following warning: In file included from /usr/include/wolfssl/openssl/bn.h:33, from

Bug#963548: Apparently resolved in 83.0.4103.106-2

On Wed, 1 Jul 2020 18:09:10 -0400 Felipe Sologuren wrote: > Hello, >Today I had 81.0.4044.92-1 installed, update ffmpeg: amd64 (7: 4.2.2-1 + > b1, 7: 4.3-2) and the error appeared. >After updating Chrome to 83.0.4103.106-2, the problem disappeared. > Thank you. Hello, Sorry, chromium

Bug#930374: node-url-parse 1.0.5-2+deb9u1 flagged for acceptance

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

Bug#912531: exiv2 0.25-3.1+deb9u2 flagged for acceptance

package release.debian.org tags 912531 = stretch pending thanks Hi, The upload referenced by this bug report has been flagged for acceptance into the proposed-updates queue for Debian stretch. Thanks for your contribution! Upload details == Package: exiv2 Version: 0.25-3.1+deb9u2

Bug#962234: perl 5.24.1-3+deb9u7 flagged for acceptance

package release.debian.org tags 962234 = stretch pending thanks Hi, The upload referenced by this bug report has been flagged for acceptance into the proposed-updates queue for Debian stretch. Thanks for your contribution! Upload details == Package: perl Version: 5.24.1-3+deb9u7

Bug#964214: libdebhelper-perl: dh_auto_configure cannot do out-of-tree builds for qmake buildsystem

Package: libdebhelper-perl Version: 13.1 Severity: normal Apparently, dh7 fails to tell qmake the location of the source directory when attempting an out-of-tree build: […] dpkg-source: info: building polyphone in polyphone_2.2.0+dfsg0-1.dsc debian/rules binary dh binary --sourcedir=sources -B

Bug#964177: Me Too!

I am also affected by these segfaults since about 24 hours ago. Can't confirm duplicate of 964167 -- I am not experiencing generally higher CPU load. Please let me know if there is any more information I can provide. -- Boyd Stephen Smith Jr. ,= ,-_-. =.

Bug#964213: [Pkg-javascript-devel] Bug#964213: nodejs: FTBFS without internet access

Le ven. 3 juil. 2020 à 19:09, Niko Tyni a écrit : > Source: nodejs > Version: 12.18.1~dfsg-1 > Severity: serious > Tags: ftbfs > > This package fails to build on a system without internet access. > > From the build log: > > not ok 430 parallel/test-dns-setserver-when-querying > --- >

Bug#861182: RFS ete

On Fri, Jul 03, 2020 at 05:10:32PM +0300, mer...@debian.org wrote: > On 2020-07-03 13:50, zhao feng wrote: > > Thanks for your help. I can build the package on buster and bullyseye. > > Which distribution do you use? I find the version of softwares like > > python is quite new. > > The package

Bug#964182: linux-image-5.7.0-1-amd64: more on wifi support

Package: src:linux Version: 5.7.6-1 Followup-For: Bug #964182 Interestingly I booted with both wifi automatic connection and an ethernet cable pluged-in and the system could connect to the AP. -- Package-specific info: ** Version: Linux version 5.7.0-1-amd64

Bug#961377: raspi3-firmware: recent stable update causes non-booting systems

Thorsten Glaser dijo [Fri, Jul 03, 2020 at 04:28:37PM +]: > Gunnar Wolf, Sun, 24 May 2020 16:03:04 -0500: > > >I will try to build+test+upload this in the next couple of days. > > $ rmadison -u qa raspi3-firmware > raspi3-firmware | 1.20161123-2 | stretch/non-free | source, arm64 >

Bug#861182: RFS ete

Hi, On Tue, Jun 30, 2020 at 12:01:59PM +0300, mer...@debian.org wrote: > On 2020-06-30 11:56, zhao feng wrote: > > To access further information about this package, please visit the > > following URL: > > > > https://mentors.debian.net/package/ete I'd love to sponsor any package that is

Bug#964213: nodejs: FTBFS without internet access

Source: nodejs Version: 12.18.1~dfsg-1 Severity: serious Tags: ftbfs This package fails to build on a system without internet access. >From the build log: not ok 430 parallel/test-dns-setserver-when-querying --- duration_ms: 0.137 severity: fail exitcode: 1 stack: |-

Bug#964212: net-cpp: FTBFS without internet access

Source: net-cpp Version: 2.2.1+dfsg1-4 Severity: serious Tags: ftbfs This package fails to build on a system without internet access. It looks like the build hangs in "http_streaming_client_test". >From the build log: Running tests... /usr/bin/ctest --force-new-ctest-process -j1 Test

Bug#964211: octave-instrument-control: FTBFS without internet access

Source: octave-instrument-control Version: 0.5.0-1 Severity: serious Tags: ftbfs This package fails to build on a system without internet access. >From the build log (hopefully I spotted the relevant part): [src/tcp/tcp_timeout.cc] > /<>/src/tcp/tcp_timeout.cc * test addr =

Bug#964209: python-blessed: FTBFS without internet access

Source: python-blessed Version: 1.17.6-1 Severity: serious Tags: ftbfs This package fails to build on a system without internet access. >From the build log: Traceback (most recent call last): File "/usr/lib/python3/dist-packages/sphinx/cmd/build.py", line 272, in build_main app =

Bug#964210: octave-nan: FTBFS without internet access

Source: octave-nan Version: 3.4.5-2 Severity: serious Tags: ftbfs This package fails to build on a system without internet access. >From the build log: [inst/load_fisheriris.m] > /<>/inst/load_fisheriris.m * test load_fisheriris assert(all(size(meas)==[150,4]))

Bug#964208: wsjtx: FTBFS without internet access

Source: wsjtx Version: 2.2.1+repack-1 Severity: serious Tags: ftbfs This package fails to build on a system without internet access. I suppose it's xsltproc calling out for external resources or something like that. This is probably the cause for the 2.2.2+repack-1 armhf build failure too; I

Bug#964207: node-node-rest-client: autopkgtest fails with node-uuid 8.2 in experimental

Package: node-node-rest-client Version: 2.5.0-4 Severity: important This package's autopkgtest failed with node-uuid 8.2 in experimental with error Error [ERR_PACKAGE_PATH_NOT_EXPORTED]: Package subpath './v1' is not defined by "exports" in /usr/share/nodejs/uuid/package.json Full

Bug#778750: theme still broken, problem with directory structure and symlink

I've just read more carefully your follow up: The theming folder in /etc/ also needs to be moved a bit: /etc/horde/themes-available.d/default -> /etc/horde/themes-available.d/default/horde OK, it was on purpose... but it seems it's not working, at least here. I'm going to try to do some

  1   2   >