Bug#882640: Fwd: dm-zoned-tools uploaded to mentors.debian.net

Deleted the previous upload and uploaded the package again to get a clean the upload and fix the revision numbers. The original revision number implied it was built from upstream release 1.0.1 which was not correct. Fixed the various issues mentioned in previous package comments. -- Forwa

Bug#918192: No email notification of autopkgtest failure

Package: tracker.debian.org,debci https://wiki.debian.org/ContinuousIntegration/RegressionEmailInformation says autopkgtest failures trigger an automatic email. When theano recently started failing [0] (#918090), no such email was received, either to its maintainer list [1] or to me (subscrib

Bug#854324: lis debian package

Hi, meanwhile a newer version was released, and it moved here: http://phd-sid.ethz.ch/debian/lis/ Best,

Bug#911832: polyfill should be dropped

Hi Kunal, Le 04/01/2019 à 16:12, Kunal Mehta a écrit : > On 1/3/19 6:57 PM, David Prévot wrote: >> Le 04/01/2019 à 12:50, Kunal Mehta a écrit : >>> This patch adds overrides for all symfony/polyfill-* packages to >>> pkg-php-tools itself, so all packages will automatically use it and no >>> longer

Bug#899595: Invalid maintainer address pkg-xfce-de...@lists.alioth.debian.org

-BEGIN PGP SIGNED MESSAGE- Hash: SHA256 On Fri, 2019-01-04 at 08:39 +0900, Hideki Yamane wrote: > Hi, > > With Bugs search "Cleaner view", I've found those bugs are not closed > in unstable but are done in experimental. Hi, I am well aware of these, thanks. > Do you have a plan to pu

Bug#911285: Current version is incompatible with Thunderbird 60

On 03.01.19 23:35, Moritz Mühlenhoff wrote: The package wasn't updated for a year, shall we remove it? Probably, people can easily use the extension from Mozillas Addon Store. Cheers, Bastian -- Dr. Bastian Venthur http://venthur.de Debian Developer

Bug#918157: openmpi seems broken on 32 bits architectures

Control: user debian...@lists.debian.org Control: usertag -1 regression Hi In Ubuntu, the upload of openmpi 3.1.3-7 has caused numerous autopkgtest failures on i386 and armhf [1]. Some affected packages are: combblas; dune-grid, lammps, liggghts, petsc, ray and superlu-dist. I re-tried these te

Bug#917060: [Pkg-rust-maintainers] Bug#917060: rust-nix: Please update to latest upstream version for sparc64 fixes

Hi Paride! On 1/3/19 4:14 PM, Paride Legovini wrote: > The packaging is ready, but nix 0.12 build-depends on rust-libc >= > 0.2.44, so that package needs to be updated first. Thanks for the feedback. I have also updated rust-libc upstream to release 0.2.46. It would be useful to package the lates

Bug#918190: systemd: timesyncd stopped updating clock file after package update

Hi, the problem seems to be mixing two approaches in an incompatible way: 1) /var/lib/systemd/timesync can either be a directory (a) or a symlink to /var/lib/private/systemd/timesync (b) 2) systemd-timesyncd.service may either contain DynamicUser=yes (a) or not (b). 1a together with 2b should

Bug#917303: Request for help with MariaDB 10.3 / libdbd-mysql-perl packaging

Hello! The main problem is that DBD::mysql touches internal libmariadb.so structures which for obvious reasons do not have stable nor documented API. In DBD::MariaDB I replaced this code by usage of public Connector/C API. But for buggy Perl application this may cause incompatibility. Changes ar

Bug#917060: [Pkg-rust-maintainers] Bug#917060: rust-nix: Please update to latest upstream version for sparc64 fixes

X-Debbugs-CC: wolfg...@silbermayr.at John Paul Adrian Glaubitz wrote on 04/01/2019: > On 1/3/19 4:14 PM, Paride Legovini wrote: >> The packaging is ready, but nix 0.12 build-depends on rust-libc >= >> 0.2.44, so that package needs to be updated first. > > Thanks for the feedback. I have also upda

Bug#918142: linux-image-4.19.0-1-amd64: Can no longer disable the touchscreen module

makes no difference i cannot disable the touchscreen On Thu, 2019-01-03 at 20:15 +, Ben Hutchings wrote: > Control: tag -1 moreinfo > > On Thu, 2019-01-03 at 20:19 +0100, lauren wrote: > > Package: src:linux > > Version: 4.19.12-1 > > Severity: normal > > > > Dear Maintainer, > > > > *** R

Bug#918193: flash-kernel: add Seagate Blackarmor NAS220 to machine db

Package: flash-kernel Version: 3.96 Severity: wishlist Tags: patch Add database entry for the Seagate Blackarmor NAS220. More details and installation instructions may be found at https://github.com/hn/seagate-blackarmor-nas diff --git a/db/all.db b/db/all.db index 5b227a4..6197d08 100644 --- a

Bug#918190: systemd: timesyncd stopped updating clock file after package update

Hello, systemd-timesyncd.service in previous releases used DynamicUser=true. This will create a symlink /var/lib/systemd/timesync pointing at ../private/systemd/timesync and make sure it is properly owned by systemd-timesync:systemd-timesync This was reverted upstream in https://github.com/system

Bug#918194: Updating the syslog-ng-incubator Uploaders list

Source: syslog-ng-incubator Version: 0.6.2-1 Severity: minor User: m...@qa.debian.org Usertags: mia-teammaint Gergely Nagy has retired, so can't work on the syslog-ng-incubator package anymore (at least with this address). We are tracking their status in the MIA team and would like to ask you to

Bug#918195: Updating the edbrowse Uploaders list

Source: edbrowse Version: 3.7.4-3 Severity: minor User: m...@qa.debian.org Usertags: mia-teammaint Gergely Nagy has retired, so can't work on the edbrowse package anymore (at least with this address). We are tracking their status in the MIA team and would like to ask you to remove them from the

Bug#878121: Updates about BLAS64

Le mardi 18 décembre 2018 à 15:12 +, Mo Zhou a écrit : > On Tue, Dec 18, 2018 at 12:42:22PM +0100, Sébastien Villemot wrote: > > > BTW, what is the "-base" (in libopenblas-base) supposed to mean? > > > > I don't even remember what it means, but it is clearly a legacy from > > the past. Ideally

Bug#918103: ipv6: Consider sk_bound_dev_if when binding a socket to an address

Control: tags -1 + fixed-upstream pending patch Hi Ralf, On Thu, Jan 03, 2019 at 12:14:05PM +0100, Ralf Jung wrote: > Package: linux-image-4.18.0-0.bpo.3-amd64 > Version: 4.18.20-2~bpo9+1 > Severity: normal > Tags: upstream > > Dear Maintainer, > > I reported an upstream bug at >

Bug#917323: transition: gdal

On 03/01/2019 17:44, Sebastiaan Couwenberg wrote: > On 1/3/19 4:39 PM, Sebastiaan Couwenberg wrote: >> On 1/3/19 4:23 PM, Emilio Pozuelo Monfort wrote: >>> On 02/01/2019 21:10, Sebastiaan Couwenberg wrote: On 1/2/19 12:55 PM, Emilio Pozuelo Monfort wrote: > On 26/12/2018 08:46, Bas Couwenb

Bug#918196: vboxdrv: module verification failed: signature and/or required key missing - tainting kernel

Package: virtualbox-dkms Version: 5.2.22-dfsg-2 Severity: normal Dear Maintainer, dmesg shows these error messages: vboxdrv: loading out-of-tree module taints kernel. vboxdrv: module verification failed: signature and/or required key missing - tainting kernel as I experience a whole lot of prob

Bug#918190: systemd: timesyncd stopped updating clock file after package update

Am 04.01.19 um 10:23 schrieb Michael Biebl: > Hello, > > systemd-timesyncd.service in previous releases used DynamicUser=true. > This will create a symlink /var/lib/systemd/timesync pointing at > ../private/systemd/timesync and make sure it is properly owned by > systemd-timesync:systemd-timesync

Bug#824495: debian-policy: Source packages "can" declare relationships

Hello Ian, On Tue 20 Nov 2018 at 03:24pm GMT, Ian Jackson wrote: > Sean Whitton writes ("Bug#824495: debian-policy: Source packages "can" > declare relationships"): >> I still don't see how we can implement such new rules, though, because >> of the problem of how to determine whether we're makin

Bug#918197: Please, drop me from Uploaders

Source: twitter-bootstrap Severity: wishlist Please, drop me from d/control and d/copyright. I don’t even seem to have write access to the repository in order to do it myself. Regards David signature.asc Description: PGP signature

Bug#918029: transition: corosync

On 02/01/2019 15:21, Ferenc Wágner wrote: > Package: release.debian.org > Severity: normal > User: release.debian@packages.debian.org > Usertags: transition > > Hi, > > First of all, I'm sorry for inadvertently starting the Corosync > transition. It isn't a problematic one, though: please sc

Bug#917255: transition: yaml-cpp

On 27/12/2018 05:00, Simon Quigley wrote: > On 12/26/18 3:39 AM, Emilio Pozuelo Monfort wrote: >> On 24/12/2018 20:30, Simon Quigley wrote: >>> Package: release.debian.org >>> Severity: normal >>> User: release.debian@packages.debian.org >>> Usertags: transition >>> >>> Hello Release Team, >>>

Bug#915811: nmu: pocl_1.1-7

Hi Andreas, On 07/12/2018 01:21, Andreas Beckmann wrote: > Package: release.debian.org > Severity: normal > User: release.debian@packages.debian.org > Usertags: binnmu > > nmu pocl_1.1-7 . ANY . unstable . -m "Rebuild with latest gcc to collect > symbol updates." > > These rebuilds will fai

Bug#918157: pmix (was: openmpi) seems broken on 32 bits architectures

Control: reassign -1 libpmix2 3.1.0~rc2-1 Control: retitle -1 libpmix2 seems broken on 32 bits architectures On 2019-01-04 09:41, Graham Inggs wrote: Control: user debian...@lists.debian.org Control: usertag -1 regression Hi In Ubuntu, the upload of openmpi 3.1.3-7 has caused numerous autopkgt

Bug#917323: transition: gdal

On 1/4/19 10:36 AM, Emilio Pozuelo Monfort wrote: > On 03/01/2019 17:44, Sebastiaan Couwenberg wrote: >> On 1/3/19 4:39 PM, Sebastiaan Couwenberg wrote: >>> On 1/3/19 4:23 PM, Emilio Pozuelo Monfort wrote: On 02/01/2019 21:10, Sebastiaan Couwenberg wrote: > On 1/2/19 12:55 PM, Emilio Pozue

Bug#917323: transition: gdal

On 04/01/2019 10:57, Sebastiaan Couwenberg wrote: > On 1/4/19 10:36 AM, Emilio Pozuelo Monfort wrote: >> On 03/01/2019 17:44, Sebastiaan Couwenberg wrote: >>> On 1/3/19 4:39 PM, Sebastiaan Couwenberg wrote: On 1/3/19 4:23 PM, Emilio Pozuelo Monfort wrote: > On 02/01/2019 21:10, Sebastiaan

Bug#918199: RM: libxfcegui4 -- ROM; deprecated upstream, no reverse dependencies

Package: ftp.debian.org Severity: normal Hi, with the orage package out of the NEW queue, we don't have any package using libxfcegui4 in unstable anymore. Could you remove it? It's deprecated upstream and superseeded by libxfce4ui. Thansk in advance, -- Yves-Alexis

Bug#918198: qbittorrent-nox: Please add the relevant systemd .service file for us that want to run it as a daemon

Package: qbittorrent-nox Version: 4.1.5-1 Severity: wishlist Tags: upstream Dear Maintainer, Please add support for running qbittorrent-nox as a daemon, by adding a systemd serivice file as described here https://github.com/qbittorrent/qBittorrent/wiki/Setting-up-qBittorrent-on- Ubuntu-server-as

Bug#836236: prosody: doesn't try IPv4 when IPv6 fails

Hi Cyril, Can you please confirm that this error does not exist in the current version of prosody 0.11.1-1? Thanks, Victor Seva

Bug#836236: prosody: doesn't try IPv4 when IPv6 fails

Hi Victor, Victor Seva (2019-01-04): > Can you please confirm that this error does not exist in the current > version of prosody 0.11.1-1? I'm running stretch so I can't really confirm. I could try the 0.11.1-1~bpo9+1 backport but before that I would need to check what specific modules were depl

Bug#918200: astropy: autopkgtest fails with python-numpy (1:1.16.0~rc1-3)

Source: astropy Version: 3.0.5-1 Severity: normal Control: block 917323 by -1 Dear Maintainer, The autopkgtest for your package fail with python-numpy (1:1.16.0~rc1-3), this increased the required age of python-numpy which block the gdal transition. Please fix the autopkgtest of your package. K

Bug#918201: astropy-healpix: autopkgtest fails with python-numpy (1:1.16.0~rc1-3)

Source: astropy-healpix Version: 0.4-1 Severity: normal Control: block 917323 by -1 Dear Maintainer, The autopkgtest for your package fail with python-numpy (1:1.16.0~rc1-3), this increased the required age of python-numpy which blocks the gdal transition. Please fix the autopkgtest of your pack

Bug#918203: ccdproc: autopkgtest fails with python-numpy (1:1.16.0~rc1-3)

Source: ccdproc Version: 1.3.0-5 Severity: normal Control: block 917323 by -1 Dear Maintainer, The autopkgtest for your package fail with python-numpy (1:1.16.0~rc1-3), this increased the required age of python-numpy which blocks the gdal transition. Please fix the autopkgtest of your package.

Bug#898696: Similar problem with version 4:18.08.1

For me this behavior starts after upgrading to 4:18.08.1 Thanks for any help signature.asc Description: This is a digitally signed message part.

Bug#918202: caffe: autopkgtest fails with python-numpy (1:1.16.0~rc1-3)

Source: caffe Version: 1.0.0+git20180821.99bd997-21.0.0+git20180821.99bd997-2 Severity: normal Control: block 917323 by -1 Dear Maintainer, The autopkgtest for your package fail with python-numpy (1:1.16.0~rc1-3), this increased the required age of python-numpy which blocks the gdal transition.

Bug#918207: pyregion: autopkgtest fails with python-numpy (1:1.16.0~rc1-3)

Source: pyregion Version: 2.0-6 Severity: normal Control: block 917323 by -1 Dear Maintainer, The autopkgtest for your package fail with python-numpy (1:1.16.0~rc1-3), this increased the required age of python-numpy which blocks the gdal transition. Please fix the autopkgtest of your package. K

Bug#918204: dask: autopkgtest fails with python-numpy (1:1.16.0~rc1-3)

Source: dask Version: 1.0.0+dfsg-1 Severity: normal Control: block 917323 by -1 Dear Maintainer, The autopkgtest for your package fail with python-numpy (1:1.16.0~rc1-3), this increased the required age of python-numpy which blocks the gdal transition. Please fix the autopkgtest of your package.

Bug#918205: hipspy: autopkgtest fails with python-numpy (1:1.16.0~rc1-3)

Source: hipspy Version: 0.2-2 Severity: normal Control: block 917323 by -1 Dear Maintainer, The autopkgtest for your package fail with python-numpy (1:1.16.0~rc1-3), this increased the required age of python-numpy which blocks the gdal transition. Please fix the autopkgtest of your package. Kin

Bug#918206: pandas: autopkgtest fails with python-numpy (1:1.16.0~rc1-3)

Source: pandas Version: 0.23.3-1 Severity: normal Control: block 917323 by -1 Dear Maintainer, The autopkgtest for your package fail with python-numpy (1:1.16.0~rc1-3), this increased the required age of python-numpy which blocks the gdal transition. Please fix the autopkgtest of your package.

Bug#918209: pytables: autopkgtest fails with python-numpy (1:1.16.0~rc1-3)

Source: pytables Version: 3.4.4-1 Severity: normal Control: block 917323 by -1 Dear Maintainer, The autopkgtest for your package fail with python-numpy (1:1.16.0~rc1-3), this increased the required age of python-numpy which blocks the gdal transition. Please fix the autopkgtest of your package.

Bug#918208: pyscanfcs: autopkgtest fails with python-numpy (1:1.16.0~rc1-3)

Source: pyscanfcs Version: 0.3.2+ds-2 Severity: normal Control: block 917323 by -1 Dear Maintainer, The autopkgtest for your package fail with python-numpy (1:1.16.0~rc1-3), this increased the required age of python-numpy which blocks the gdal transition. Please fix the autopkgtest of your packa

Bug#918211: ovito: depends on obsolete libnetcdf11

Package: ovito Version: 2.8.1+dfsg2-5 Severity: normal Hello, in the current testing suite, ovito 2.8.1+dfsg2-5 depends on libnetcdf11, which is an old library, and conflicts with other software, e.g. the dependences of the grace package. The unstable version of ovito, 2.9.0+dfsg1-5, depe

Bug#918212: python-pbcore: autopkgtest fails with python-numpy (1:1.16.0~rc1-3)

Source: python-pbcore Version: 1.5.0+git20180606.43fcd9d+dfsg-2 Severity: normal Control: block 917323 by -1 Dear Maintainer, The autopkgtest for your package fail with python-numpy (1:1.16.0~rc1-3), this increased the required age of python-numpy which blocks the gdal transition. Please fix the

Bug#918213: python-skbio: autopkgtest fails with python-numpy (1:1.16.0~rc1-3)

Source: python-skbio Version: 0.5.5-1 Severity: normal Control: block 917323 by -1 Dear Maintainer, The autopkgtest for your package fail with python-numpy (1:1.16.0~rc1-3), this increased the required age of python-numpy which blocks the gdal transition. Please fix the autopkgtest of your packa

Bug#918210: python-astropy: autopkgtest fails with python-numpy (1:1.16.0~rc1-3)

Source: python-astropy Version: 2.0.9-1 Severity: normal Control: block 917323 by -1 Dear Maintainer, The autopkgtest for your package fail with python-numpy (1:1.16.0~rc1-3), this increased the required age of python-numpy which blocks the gdal transition. Please fix the autopkgtest of your pac

Bug#918214: python-xarray: autopkgtest fails with python-numpy (1:1.16.0~rc1-3)

Source: python-xarray Version: 0.11.0-3 Severity: normal Control: block 917323 by -1 Dear Maintainer, The autopkgtest for your package fail with python-numpy (1:1.16.0~rc1-3), this increased the required age of python-numpy which blocks the gdal transition. Please fix the autopkgtest of your pac

Bug#918216: sunpy: autopkgtest fails with python-numpy (1:1.16.0~rc1-3)

Source: sunpy Version: 0.9.5-1 Severity: normal Control: block 917323 by -1 Dear Maintainer, The autopkgtest for your package fail with python-numpy (1:1.16.0~rc1-3), this increased the required age of python-numpy which blocks the gdal transition. Please fix the autopkgtest of your package. Ki

Bug#918217: theano: autopkgtest fails with python-numpy (1:1.16.0~rc1-3)

Source: theano Version: 1.0.2+dfsg-1 Severity: normal Control: block 917323 by -1 Dear Maintainer, The autopkgtest for your package fail with python-numpy (1:1.16.0~rc1-3), this increased the required age of python-numpy which blocks the gdal transition. Please fix the autopkgtest of your packag

Bug#918215: skimage: autopkgtest fails with python-numpy (1:1.16.0~rc1-3)

Source: skimage Version: 0.14.1-2 Severity: normal Control: block 917323 by -1 Dear Maintainer, The autopkgtest for your package fail with python-numpy (1:1.16.0~rc1-3), this increased the required age of python-numpy which blocks the gdal transition. Please fix the autopkgtest of your package.

Bug#918190: systemd: timesyncd stopped updating clock file after package update

Hello, > Can you post the output of > ls -ld /var/lib/systemd/timesync > ls -la /var/lib/private/systemd/ root@mmm /h/pat# ls -ld /var/lib/systemd/timesync lrwxrwxrwx 1 root root 27 Jan 3 2018 /var/lib/systemd/timesync -> ../ private/systemd/timesync/ root@mmm /h/pat# ls -la /var/lib/private/

Bug#913550: shared-mime-info: Don't assume every *.key file is an Apple Keynote file

[Adding pkg-freedesktop-maintain...@lists.alioth.debian.org & po...@debian.org to CC] > Chris Lamb wrote: > > > A Tails user's OpenPGP armored public key (e.g. exported with "gpg -- > > armor --export $KEY_ID" is incorrectly recognised as "application/x- > > iwork-keynote-sffkey": > […] > > Ther

Bug#918218: Bug: symlinks does not work in a container with overlayFS

Package: symlinks Version: 1.4-3+b1 Hello Debian community, the symlinks command does not work as expected, if executed from a docker container containing overlay2 filesystem. No absolute symlinks are converted to relative ones, when executing symlinks -o -r -c -v dir1 How to reproduce: 1) Inst

Bug#918103: ipv6: Consider sk_bound_dev_if when binding a socket to an address

Hi, > On Thu, Jan 03, 2019 at 12:14:05PM +0100, Ralf Jung wrote: >> Package: linux-image-4.18.0-0.bpo.3-amd64 >> Version: 4.18.20-2~bpo9+1 >> Severity: normal >> Tags: upstream >> >> Dear Maintainer, >> >> I reported an upstream bug at >>

Bug#918103: ipv6: Consider sk_bound_dev_if when binding a socket to an address

Hi Ralf, On Fri, Jan 04, 2019 at 11:42:26AM +0100, Ralf Jung wrote: > Hi, > > > On Thu, Jan 03, 2019 at 12:14:05PM +0100, Ralf Jung wrote: > >> Package: linux-image-4.18.0-0.bpo.3-amd64 > >> Version: 4.18.20-2~bpo9+1 > >> Severity: normal > >> Tags: upstream > >> > >> Dear Maintainer, > >> > >> I

Bug#918103: ipv6: Consider sk_bound_dev_if when binding a socket to an address

Hi, > Once a version uploaded to sid, migrates to testing, it can be > prepared for stable-backports based on that. > > So what will need to happen here: upload of 4.19.13-2 to unstable > (actually possibly only >= 4.19.14-1 if we do not have pressure to > upload 4.19.13-2), then wait it migrates

Bug#918218: additional information

Severity: important Hi, sorry forgot to mention some additional information. Inside docker container: $ uname -a Linux 27046b6215ae 4.9.0-7-amd64 #1 SMP Debian 4.9.110-1 (2018-07-05) x86_64 GNU/Linux $ cat /etc/debian_version 9.5

Bug#911977: how do we correctly guess the VM name in autopkgtest?

Control: tag -1 + moreinfo Hi, On Fri, 26 Oct 2018 15:23:01 -0400 Antoine Beaupre wrote: > One of the nice things with the schroot backend is that it automatically > guesses which schroot to use based on internal sbuild logic. If I build a > stretch-security update, it will find my stretch chroo

Bug#918190: systemd: timesyncd stopped updating clock file after package update

Am 04.01.19 um 11:48 schrieb Patrick Häcker: > Hello, > >> Can you post the output of >> ls -ld /var/lib/systemd/timesync >> ls -la /var/lib/private/systemd/ > > root@mmm /h/pat# ls -ld /var/lib/systemd/timesync > lrwxrwxrwx 1 root root 27 Jan 3 2018 /var/lib/systemd/timesync -> ../ > private/

Bug#876060: vit's error messages makes its output blow up.

Package: vit Version: 1.2-4 Followup-For: Bug #876060 Dear all, The bug is rooted in the upstream version, where it has been reported [1] and solved [since 2] from the pre-release v1.3.beta1 [3]. Best regards. ~~ 1. https://github.com/scottkosty/vit/issues/153 2. https://github.com/scottkosty/

Bug#918190: systemd: timesyncd stopped updating clock file after package update

Am 04.01.19 um 12:22 schrieb Michael Biebl: > For completeness sake, can you also post the output of > stat /var/lib/systemd/timesync/clock Make that stat /var/lib/private/systemd/timesync/clock (I missed that you already deleted /var/lib/systemd/timesync/) -- Why is it that all of the instru

Bug#917859: vim FTBFS building for armel,armhf on arm64

On Thu, Jan 03, 2019 at 07:43:03AM -0500, James McCoy wrote: >On Wed, Jan 02, 2019 at 06:53:29PM +, Steve McIntyre wrote: >> >> amdahl is the arm64 porterbox, and I've just checked - it has armel >> and armhf schroots configured too. That should hopefully cover what >> you need - shout if you

Bug#909378: Re: Bug#909378: sbuild: sbuild-createchroot must not consider “lost+found” for non empty directory

Hi Daniel, On Sun, 23 Sep 2018 13:21:38 +0200 Johannes Schauer wrote: > Quoting Daniel Dehennin (2018-09-22 19:52:55) > > I'm trying to setup an LVM schroot but I got the following error: > > > > #+begin_src > > /srv/chroot/sid-amd64-sbuild is not empty at /usr/bin/sbuild-createchroot > > line

Bug#918219: nagios3-cgi: postinst script fails if supplied apache config has been deleted previously

Package: nagios3-cgi Version: 3.5.1.dfsg-2+deb8u1 Severity: important Dear Maintainer, *** Reporter, please consider answering these questions, where appropriate *** * What led up to the situation? Simply updating the system * What exactly did you do (or not do) that was effective (or

Bug#918220: securefs: Typo in debian/watch file

Source: securefs Version: 0.8.2+ds-3 Severity: minor Dear securefs maintainer, uscan reports error due to unrecognized option "repackasuffix=+ds". It is obviously a typo. Please consider fixing it in the next upload. Thanks! -- Regards, Boyuan Yang signature.asc Description: This is a digital

Bug#911979: fails on chown in autopkgtest-qemu backend

Hi, On Fri, 26 Oct 2018 15:33:32 -0400 Antoine Beaupre wrote: > I have tried to use the autopkgtest backend with the qemu server but it > completely failed to launch the build: > > [...] > > chown: invalid user: 'sbuild:sbuild' > E: Failed to set sbuild:sbuild ownership on /build > Failed to set

Bug#918221: ftp.debian.org: Please add aceept-with-bug to DAK process-new

Package: ftp.debian.org Severity: wishlist Hi! I was just discussing a REJECT with a FTP team member and he told me that currently DAK-process-new does not has the option to ACCEPT a package and file a bug against it. There are certain cases in which accepting a package with a bug makes sense,

Bug#845223: 0ad: Crashes on startup with cache.cpp(43): Assertion failed: "cache.Validate()"

Hello Cacatoes, I just uploaded 0ad version 0.0.23.1 to unstable. Can you check your problem is still present in this version? if the problem is still present I suggest you to add a comment on your upstream bug http://trac.wildfiregames.com/ticket/4360 to let them know the problem is not yet f

Bug#916889: [Pkg-privacy-maintainers] Bug#916889: onionshare: recommends torbrowser-launcher in contrib

Hi John! thank you for this report. John Scott: > Package: onionshare > Severity: minor > > The Policy Manual suggests that OnionShare shouldn't depend or > recommend torbrowser-launcher unless as an alternative to tor > because it's in main (assuming OnionShare 1.3+ works with that). Onionshar

Bug#918222: calamares-settings-debian: Typo in package description

Package: calamares-settings-debian Severity: minor Dear Maintainer, I noticed a typo in the calamares-settings-debian package description. Indeed, "genereic" should be spelled "generic". Thanks a lot for your work on calamares-setting-debian! Thomas -- System Information: Debian Release: 9.6

Bug#913003: already fixed

Control: fixed -1 2.0.6-1 Really add fixed version. signature.asc Description: OpenPGP digital signature

Bug#918138: qtox: Add AppArmor profile

Vincas Dargis 于2019年1月4日周五 上午2:36写道： > > Dear Maintainer, > > I'm happy to see that we now have qTox in Debian! Thanks to Maintainer! > > It would be even cooler to have it confined with AppArmor. qTox > maintains connections to various untrusted peers over the world, and so > it is important do r

Bug#918223: ioctl[SIOCSIWENCODEEXT]: Invalid argument

Package: wpasupplicant Version: 2:2.7-2 Severity: minor wpa_supplicant connects fine, however I always get these two warnings, with various hardware, always the same. # wpa_supplicant -D wext,nl80211 -dd -i $i -c $co -B wpa_driver_wext_set_key: alg=0 key_idx=4 set_tx=0 seq_len=0 key_len=0 ioctl[S

Bug#873341: SBT is uninstallable; depends on nonexistent packages

On Thu, 3 Jan 2019 13:03:42 +0100 Antonio Ospite wrote: > On Thu, 3 Jan 2019 11:45:29 +0100 > Emmanuel Bourg wrote: > [...] > > If someone wants to pick the ball the next steps are to: > > 1. build SBT 1.0 without the embedded libraries > > 2. build Scala 2.12 > > > > I was wondering if downgr

Bug#917174: davmail: FTBFS with libjackrabbit-java 2.18.0

> > unfortunately davmail fails to build from source with > > libjackrabbit-java 2.18.0. Long deprecated methods have been removed. > > Your package build-depends on a very old version of jackrabbit (2.4.3). This is too much work and I'm afraid if I do not get help I'll miss the 2019-02-12 - Soft-

Bug#918224: ITP: ruby-mini-mime: A lightweight mime type implementation

Package: wnpp Owner: Lucas Kanashiro Severity: wishlist X-Debbugs-CC: debian-de...@lists.debian.org * Package name    : ruby-mini-mime   Version : 1.0.1   Upstream Author : Discourse Construction Kit, Inc. * URL : https://github.com/discourse/mini_mime * License : Expa

Bug#864082: Next steps for a reproducible Fontconfig?

[Adding 864...@bugs.debian.org to CC] Dear fontconfig maintainers, I've just spent a coffee-or-two unpicking this to get the latest status and to load the history back into my brain. As a bit of background, I'm working on the Reproducible Builds effort and fontconfig — in its usual usage, or at

Bug#917687: [3dprinter-general] Bug#917687: cura-engine: FTBFS: ./obj-x86_64-linux-gnu/CMakeFiles/CMakeTmp/./obj-x86_64-linux-gnu/CMakeFiles/CMakeTmp/CheckSymbolExists.c:8: undefined reference to `pth

> Looks OK to me. Ok... So it turns out I made a stupid versioning mistake when preparing a fixed version of libpolyclipping. After fixing that and reinstalling the correct pkg-config file, I can build cura-engine again. I'll ask Petter to upload libpolyclipping-6.4.2-6 ASAP.

Bug#918225: pasystray: prefer GtkStatusIcon over Appindicator

Package: pasystray Version: 0.7.0-1 Severity: normal Tags: patch Current implementation of AppIndicator does not handle click events or modifiers. A middle click on the icon of pasystray is supposed to toggle mute, but this is not possible with the AppIndicator implementation. I filed a bug to App

Bug#918223: ioctl[SIOCSIWENCODEEXT]: Invalid argument

On Fri, 4 Jan 2019 at 13:12, 積丹尼 Dan Jacobson wrote: > > Package: wpasupplicant > Version: 2:2.7-2 > Severity: minor > > wpa_supplicant connects fine, however I always get these two warnings, > with various hardware, always the same. > # wpa_supplicant -D wext,nl80211 -dd -i $i -c $co -B > > wpa_d

Bug#917850: Fwd: Server Error (500) on nm.d.o

Hi, El lun., 31 de dic. de 2018 a la(s) 05:02, Jonathan McDowell ( nood...@earth.li) escribió: > On Sun, Dec 30, 2018 at 11:29:33PM -0300, eamanu15 wrote: > > I joined to NM and in my personal web I have on *pending *the next line: > > "This is a new entry that requires confirmation before Jan. 2

Bug#845223: 0ad: Crashes on startup with cache.cpp(43): Assertion failed: "cache.Validate()"

Hi Ludovic, This problem doesn't occur after a few tests (I think it has been fixed ages ago already). I posted back on their Trac. During my tests I experienced another similar issue but not the same error message. I believe it's a separate issue so I'll create another one if I can pinpoint it a

Bug#918026: ruby-sinatra-contrib: uninstallable; depends on versions not present in the archive

On Wed, Jan 02, 2019 at 10:58:15AM -0300, Antonio Terceiro wrote: > Package: ruby-sinatra-contrib > Version: 2.0.5-1 > Severity: serious > Justification: unsatisfiable dependencies > > # apt install ruby-sinatra-contrib > Reading package lists... Done > Building dependency tree > Reading state inf

Bug#918080: breeze-gtk: symlink /usr/share/themes/Breeze/{gtk-3.20,gtk-3.0}/

¡Hola Simon! El 2019-01-02 a las 21:25 -0600, Simon Quigley escribió: Package: breeze-gtk Severity: normal Version: 5.14.3-1 It was raised to my attention from LXQt users that the Breeze GTK theme cannot be used under LXQt as packaged. This is because the theme exists in /usr/share/themes/Bre

Bug#917174: davmail: FTBFS with libjackrabbit-java 2.18.0

Hello Alex, Am 04.01.19 um 13:16 schrieb Alexandre Rossi: >>> unfortunately davmail fails to build from source with >>> libjackrabbit-java 2.18.0. Long deprecated methods have been removed. >>> Your package build-depends on a very old version of jackrabbit (2.4.3). > > This is too much work and I

Bug#918226: gcc-snapshot.prerm yields error messages - incorrect paths?

Package: gcc-snapshot Version: 1:20190102-1 Severity: normal I can see the following error messages on upgrade or removal: find: ‘/usr/lib/gcc-snapshot/share/python’: No such file or directory find: ‘/usr/lib/gcc-snapshot/share/python’: No such file or directory They come from /var/lib/dpkg/info

Bug#916839: imagemagick: Silent ABI break in 6.9.10-11 on i386

Hi, On Thu, Dec 20, 2018 at 6:46 AM Bastien ROUCARIES wrote: > > On Wed, Dec 19, 2018 at 12:09 PM Balint Reczey > wrote: > > > > Package: imagemagick > > Version: 8:6.9.10.14+dfsg-1 > > Severity: grave > > Control: forwareded -1 https://github.com/ImageMagick/ImageMagick6/issues/31 > > Control:

Bug#917859: vim FTBFS building for armel,armhf on arm64

On Fri, Jan 04, 2019 at 11:34:04AM +, Steve McIntyre wrote: >On Thu, Jan 03, 2019 at 07:43:03AM -0500, James McCoy wrote: >>On Wed, Jan 02, 2019 at 06:53:29PM +, Steve McIntyre wrote: >>> >>> amdahl is the arm64 porterbox, and I've just checked - it has armel >>> and armhf schroots configu

Bug#918227: xtables-addons-common: GeoIPCountryCSV.zip ERROR 404: Not Found

Package: xtables-addons-common Version: 2.12-0.1 Severity: important Dear Maintainer, * What led up to the situation? Running periodically a script that calls /usr/lib/xtables-addons/xt_geoip_dl to update GeoIPv6.csv.gz and GeoIPCountryCSV.zip * What exactly did you do (or not do

Bug#918026: ruby-sinatra-contrib: uninstallable; depends on versions not present in the archive

On Fri, Jan 04, 2019 at 10:22:08AM -0300, Antonio Terceiro wrote: > On Wed, Jan 02, 2019 at 10:58:15AM -0300, Antonio Terceiro wrote: > > Package: ruby-sinatra-contrib > > Version: 2.0.5-1 > > Severity: serious > > Justification: unsatisfiable dependencies > > > > # apt install ruby-sinatra-contri

Bug#918228: thunderbird: GNOME keyring integration causes malfunction of fetching messages from server

Package: thunderbird Version: 1:60.4.0-1~deb9u1 Severity: normal Dear Maintainer, * After having installed Debian 9 and thunderbird on a "virgin" system and taking over the old user profile, I was unable to fetch mails from the server on the accounts both from me and my wife. Also, the process

Bug#902821: qa.debian.org: Asian (JP, CH) input impossible, when locale is not Asian (LANG=en_US, etc)

reassign 902821 installation-reports thanks Hi, Reassigning to installation-reports. Lucas

Bug#887681: python-tornado: FTBFS on hurd-i386: multiple test suite failures

Julien Puydt writes: > sorry it took so long to answer. Likewise. :-) > (2) is python-twisted test suite run during the build stage? If it > isn't, the build might be happy while in fact everything is broken. Yeah, that appears to be the issue; a closer look at https://buildd.debian.org/status

Bug#904083: Regression run_lintian calls lintian with a non existing filename

Control: tag -1 + moreinfo Control: severity -1 normal Hi, On Thu, 19 Jul 2018 13:08:02 +0200 Maximiliano Curia wrote: > With the new release of sbuild 0.77 (which moves the run_lintian call outside > of the build function), lintian receives the name of a no longer existing > changes file (as

Bug#870344: [Pkg-mozext-maintainers] Bug#870344: New upstream release supporting Firefox 57+

Hello Moritz, On Thu 03 Jan 2019 at 11:06pm +0100, Moritz Mühlenhoff wrote: > On Tue, Aug 01, 2017 at 10:02:39AM -0400, Sean Whitton wrote: >> Hello Damyan, >> >> On Tue, Aug 01, 2017 at 08:58:38AM +, Damyan Ivanov wrote: >> > When firefox hits unstable (probably towards the end of this year)

Bug#918185: fai - fcopy mode handling broken precedence

I guess my idea was that you set the default using the file-modes file and then can override it in a script using the cmdline option if you need different modes for the same file in different scripts. But it seems also reasonable to change this. So you like to change the precedence so that the cmd

Bug#829119: radicale does not commit to git

Package: radicale Followup-For: Bug #829119 Hi committing to git works here (radicale 2.1.11-2 and previous versions from experimental). python-dulwich / python3-dulwich is not needed anymore for this. $ grep hook /etc/radicale/config hook = ([ -d .git ] || git init) && ([ -e .gitignore ] || pri

Bug#918229: criu: FTBFS building for armhf on arm64

Package: src:criu Version: 3.8.1-1 Severity: important Hi! I've been doing a full rebuild of the Debian archive, building all source packages targeting armel and armhf using arm64 hardware. We are planning in future to move all of our 32-bit armel/armhf builds to using arm64 machines, so this reb

  1   2   3   4   >