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

2020-07-05 Thread Vincent Lefevre
On 2020-07-04 01:07:15 +0200, Guilhem Moulin wrote: > 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

Bug#964253: libbluray: Include list_titles and bdsplice utilities

2020-07-05 Thread Vasyl Gello
Sebastian, Maybe it is good idea to rename that tool upstream to bd_list_titles. Jean-Baptiste, what do you think of it? If you are fine with it, please make a new tag as usual :) --  Vasyl Gello == Certified SolidWorks Expert Mob.:+380 (98) 465

Bug#964293: hubicfuse: error while loading libssl.so.1.0.0

2020-07-05 Thread Stephen Kitt
Hi, On Sun, 05 Jul 2020 11:42:08 +0200, rpnpif wrote: > The command hubicfuse /mnt/hubic -o noauto_cache,sync_read > get the result : > hubicfuse: error while loading shared libraries: libssl.so.1.0.0: cannot > open shared object file: No such file or directory > > but libssl1.1 was needed.

Bug#964251: libreoffice-common: needs Breaks+Replaces against openclipart-libreoffice

2020-07-05 Thread Rene Engelhard
Hi, Am 04.07.20 um 18:53 schrieb Rene Engelhard: >> openclipart-libreoffice will probably need updates as well to no longer >> ship these files (or rename them), it's probably easiest if you fix and >> upload that QA maintained package, too. > > No. I don't care, actually :-) That's why it is QA

Bug#964294: mlpack FTBFS: dh_missing: error: missing files, aborting

2020-07-05 Thread Adrian Bunk
Source: mlpack Version: 3.3.2-1 Severity: serious Tags: ftbfs https://buildd.debian.org/status/package.php?p=mlpack ... dh_missing -a -O--buildsystem=cmake -O--max-parallel=1 dh_missing: warning: usr/lib/x86_64-linux-gnu/cmake/mlpack/mlpack-targets-none.cmake exists in debian/tmp but is not

Bug#962653: davical: diff for NMU version 1.1.9.3-1.1

2020-07-05 Thread Adrian Bunk
Control: tags 962653 + patch Control: tags 962653 + pending Dear maintainer, I've prepared an NMU for davical (versioned as 1.1.9.3-1.1) and uploaded it to DELAYED/3. Please feel free to tell me if I should cancel it. cu Adrian diff -Nru davical-1.1.9.3/debian/changelog

Bug#964293: hubicfuse: error while loading libssl.so.1.0.0

2020-07-05 Thread rpnpif
Package: hubicfuse Version: 3.0.0-1 Severity: grave Justification: renders package unusable Dear Maintainer, The command hubicfuse /mnt/hubic -o noauto_cache,sync_read get the result : hubicfuse: error while loading shared libraries: libssl.so.1.0.0: cannot open shared object file: No such file

Bug#964253: libbluray: Include list_titles and bdsplice utilities

2020-07-05 Thread sramacher
Hi Nils, Vasyl, On 2020-07-05 09:30:26 +, Vasyl Gello wrote: > Control: block -1 by 964242 > Control: owner -1 ! > > Hi Nils, > > I am building the fix locally, however please note that ANY clean-room build > (be it pbuilder / cowbuilder / sbuild) targeting unstable will end up failing >

Bug#954195: fix for the issue

2020-07-05 Thread navaneeth
As it says in the error, the problem is with the object `manager` being `None`. I was able to bypass this issue by adding an `if` case to check whether `manager` is `None` or not. With that, `gnome-music` runs.

Bug#955971: Not hiding problems

2020-07-05 Thread Geert Stappers
On Sun, Jul 05, 2020 at 09:41:45AM +0200, Teus Benschop wrote: > > We could be doing nothing just now and leave the bug number as it is. > > We also could, say, write patches, that either disable the dependency on > dbus-glib. > > Or perhaps there's other ways to deal with it. > > What do you

Bug#964253: libbluray: Include list_titles and bdsplice utilities

2020-07-05 Thread Vasyl Gello
Control: block -1 by 964242 Control: owner -1 ! Hi Nils, I am building the fix locally, however please note that ANY clean-room build (be it pbuilder / cowbuilder / sbuild) targeting unstable will end up failing to resolve a broken dependency of bsdmainutils on bsdextrautils (Bug #964242). To

Bug#959075: Still not working on Debian testing

2020-07-05 Thread richard lucassen
On Sun, 05 Jul 2020 09:58:46 +0800 Paul Wise wrote: > On Sat, 2020-07-04 at 18:08 +0200, richard lucassen wrote: > > > Rereading it, I don't know if this issue was present in 2.9 or > > earlier. I just noticed it while testing the new version. > > Would you mind downgrading to 2.9 and testing

Bug#959075: Still not working on Debian testing

2020-07-05 Thread richard lucassen
On Sun, 05 Jul 2020 09:58:46 +0800 Paul Wise wrote: > > Rereading it, I don't know if this issue was present in 2.9 or > > earlier. I just noticed it while testing the new version. > > Would you mind downgrading to 2.9 and testing it? > You can install it from Debian buster or snapshot.d.o No

Bug#963205: Next round

2020-07-05 Thread Thomas Orgis
Great. I released 1.26.2 now so that the package here can be updated. pgpXAEbLMdip3.pgp Description: Firma digital OpenPGP

Bug#931785: release-notes: bullseye: security suite renamed to bullseye-security (from buster/updates)

2020-07-05 Thread Andrei POPESCU
On Mi, 10 iul 19, 13:16:27, Ansgar Burchardt wrote: > Package: release-notes > Severity: normal > > For bullseye, the security suite is now named bullseye-security > instead of buster/updates and users should adapt their sources.list > accordingly when upgrading. > > People should probably use

Bug#956033: RFS: idseq-bench [ITP]

2020-07-05 Thread Sao I Kuan
On Sun, Jul 5, 2020 at 12:24 AM Andreas Tille wrote: > > Hi Sao, > > On Sat, Jul 04, 2020 at 04:26:36PM +0900, Sao I Kuan wrote: > > Hi, > > > > I'm looking for a sponsor for the package: > > * idseq-bench (#956033) > > > > The package is on: > >

Bug#964292: goldencheetah FTBFS: some qt incompatibility

2020-07-05 Thread Helmut Grohne
Source: goldencheetah Version: 1:3.5~DEV1903-1 Severity: serious Tags: ftbfs goldencheetah fails to build from source in unstable. The relevant failure is: | In file included from Metrics/PowerProfile.cpp:20: | Metrics/PowerProfile.h:77:37: error: field ‘values’ has incomplete type ‘QMap >’ |

Bug#964289: systemd-container: armhf countainer cannot be started on amd64 host

2020-07-05 Thread Michael Biebl
Am 05.07.20 um 07:48 schrieb Ryutaroh Matsumoto: > Package: systemd-container > Version: 245.6-1 > Severity: normal > > Dear Maintainer, > > I installed > # dpkg-query -W | grep qemu-user-static > qemu-user-static 1:5.0-5 > > Then I built a root directory as > > # mmdebstrap

Bug#964291: stretch-pu: package mariadb-10.1 10.1.45-0+deb9u1

2020-07-05 Thread Otto Kekäläinen
For unstable the plan is to upload MariaDB 10.5 soon, and therefore uploads of MariaDB 10.3 are already discontinued. Since we already have MariaDB 10.4 in Debian experimental, it is not even possible to do any uploads of MariaDB 10.3 because of triggering the NEW queue and version

Bug#723698: Your comment at fotomuseum.ch

2020-07-05 Thread verify
Dear Рowerful high authority redirеct dоfоllоw seо link building: https://coupemoi.la/akqWs Thank you for your recent response to the Fotomuseum blog. Please click on the link below to verify your email address and authorize your comment on the fotomuseum.ch site. This allows us to discourage

Bug#955971: [pkg-crosswire-devel] Processed: reopen

2020-07-05 Thread Teus Benschop
On Sun, 5 Jul 2020 at 08:57, Geert Stappers wrote: > On Sun, Jul 05, 2020 at 08:17:23AM +0200, Teus Benschop wrote: > > > Question to the Debian developers: > > Should we just disable the dbus functionality in Xiphos? > > > What Debian Developers do: > * Find a way to enable full functionality

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

2020-07-05 Thread Chris Lamb
Hi John Scott, > 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

Bug#964291: stretch-pu: package mariadb-10.1 10.1.45-0+deb9u1

2020-07-05 Thread Adam D. Barratt
On Sun, 2020-07-05 at 09:59 +0300, Otto Kekäläinen wrote: > mariadb-10.1 (10.1.45-0+deb9u1) stretch; urgency=high > > * SECURITY UPDATE: New upstream version 10.1.45. Includes fixes for > the > following security vulnerabilities: > - CVE-2020-2752 > - CVE-2020-2812 > -

Bug#964291: stretch-pu: package mariadb-10.1 10.1.45-0+deb9u1

2020-07-05 Thread Otto Kekäläinen
Control: tags -1 -moreinfo > Tagging your bug "moreinfo" means that it's not ready for processing by > SRM. Is that what you intended? Thanks for a quick response. I just copied the previous stable update email I've sent without realizing that it wasn't directly suited. Sorry for the mistakes.

Bug#961370: pv: ETA is wildly off when transfer rate changes

2020-07-05 Thread lemonsqueeze
Cool, looking forward to next pv release =) I was thinking, it seems most command line tools which display ETA like wget for example exhibit very simple behavior by default: ETA is displayed every second and average rate used to compute it is simply average rate during last second (hence wild ETA

Bug#964291: stretch-pu: package mariadb-10.1 10.1.45-0+deb9u1

2020-07-05 Thread Adam D. Barratt
Control: severity -1 normal On Sun, 2020-07-05 at 09:59 +0300, Otto Kekäläinen wrote: > Package: release.debian.org > Severity: serious No. p-u bugs (and basically all release.d.o bugs) are (still) normal at most. Please don't inflate severity like that. It may be RC for your individual package,

Bug#964290: lintian: FP missing-build-dependency-for-dh-addon gir => gobject-introspection

2020-07-05 Thread Felix Lechner
Package: lintian Severity: normal Submitter: Paul Gevers X-Debbugs-CC: elb...@debian.org Hi Paul, It's a bug. I filed this report on your behalf. I will be on top of it after I resolve something time sensitive early this week. Thank you for your patience! Kind regards Felix Lechner * * *

Bug#955971: [pkg-crosswire-devel] Processed: reopen

2020-07-05 Thread Teus Benschop
It was closed because the changelog of the new upload had this bug number, whereas it should have been another bug number to close. So yes, it's correct to reopen this bug again. It was forwarded upstream. Question to the Debian developers: Should we just disable the dbus functionality in

<    1   2   3