Bug#910080: pyqt-qwt: not really future-proof with the python3 versions

Source: pyqt-qwt Version: 1.01.00-2 Severity: important Dear maintainer, while fixing #909732 (thank you for it!) you also introduced another, possibly even more important, bug. diff --git a/debian/python3-pyqt5.qwt.dirs b/debian/python3-pyqt5.qwt.dirs index

Bug#909412: transition: libpodofo

On Tue, Oct 02, 2018 at 04:46:11PM +0200, Emilio Pozuelo Monfort wrote: > Yes. That (openssl) is going to block other larger transitions from starting > as > well, so I'd rather have this one, which is small and doesn't conflict with > anything, ready to go in while openssl gets fixed. Thanks for

Bug#771514: openjfx: fxpackager missing files

Control: tags -1 + wontfix Control: close -1 Upstream no longer builds javapackager by default. The tool is likely to be moved elsewhere as part of JEP 343 [1]. For these reasons I'm tagging the bug as wontfix and closing it. [1] http://openjdk.java.net/jeps/343

Bug#910044: mmdebstrap: problem with sources.list-style mirror parameter handling

On Tue, Oct 02, 2018 at 10:13:42AM +0200, Johannes Schauer wrote: > Quoting Johannes Schauer (2018-10-02 04:23:54) > > > Another thing that I have stumbled upon is that providing a sources.list > > > on > > > stdin only works when no target directory is provided on the commandline, > > > i.e.

Bug#910087: nvidia-kernel-dkms: nvidia kernel module does not build against 4.18 kernel

On Tue, 2018-10-02 at 16:44 +0200, Markus Lindberg wrote: > Package: nvidia-kernel-dkms > Version: 384.130-1 > Severity: normal > > Dear Maintainer, > >     * What led up to the situation? > > I tried to install the nvidia-driver package. > >     * What exactly did you do (or not do) that was

Bug#908931: transition: gnat-8, Ada component of gcc-8

On 02/10/2018 15:37, Nicolas Boulenguez wrote: > The naive question at the end of the request was sincere. > What should I do exactly? > > Should I rebuild and reupload each package manually? > Or prepare lines like: > nmu adabrowse_4.0.3-9 . ANY . -m 'Reupload to unstable to complete the >

Bug#884328: nagios-plugins-contrib: check_running_kernel should use version sort

Hi, I have encountered this problem recently as well. The check compares the running kernel version with the wrong installed version. It seems to me the problem is created by not using version sort[0] with the result that in the original bug reporter's case 3.2.0-4-amd64 is seen as bigger than

Bug#909803: freeipa-client: depends chrony should be downgraded to recommends

severity 909803 serious thanks There does not seem to be any logic in the freeipa-client package to ensure a working time configuration after ntp is forced out in favor of chrony. This implies that a freeipa client may become unusable after upgrade once its clock has drifted far enough in the

Bug#910077: ITP: binoculars -- Surface X-ray diffraction 2D detector data reduction

Package: wnpp Severity: wishlist Owner: Picca Frédéric-Emmanuel * Package name: binoculars Version : 0.0.1 Upstream Author : Willem Onderwaater * URL : https://github.com/id03/binoculars * License : GPL-3+ Programming Lang: Python Description :

Bug#910072: RM: php7.1/7.1.20-1

Control: reopen -1 On Tue, Oct 02, 2018 at 02:07:20PM +0200, Ondřej Surý wrote: > I haven't decided yet if I want PHP 7.0 and 7.1 removed from unstable yet. > It’s most probably not a problem, but this bug report was intentionally > targeted on just testing. Well, why keep it? Unless you have

Bug#910087: nvidia-kernel-dkms: nvidia kernel module does not build against 4.18 kernel

Package: nvidia-kernel-dkms Version: 384.130-1 Severity: normal Dear Maintainer,    * What led up to the situation? I tried to install the nvidia-driver package.    * What exactly did you do (or not do) that was effective (or ineffective)? I ran the following command to install the

Bug#909412: transition: libpodofo

On 02/10/2018 16:07, Mattia Rizzolo wrote: > On Tue, Oct 02, 2018 at 09:50:15AM +0200, Emilio Pozuelo Monfort wrote: >> Please go ahead. > > Are you sure you want to go ahead even if this is going to get stuck in > unstable thanks to openssl 1.1.1 (as it will pick a versioned dependency > on

Bug#910075: Xorg crash

reassign 910075 evolution 3.30.1-1 retitle 910075 evolution crash on interact thanks Hi, after some more tests I think the crash comes from evolution. The crash comes when I interact with evolution, scroll through the list or switch to an other mail. So I reassign this bug to evolution. The

Bug#884635: transition: libupnp

Hello Marcelo, On 10/01/2018 11:33 PM, Marcelo Roberto Jimenez wrote: > If I can help further, please do contact me. I started to port gmrender-resurrect to 1.8, but I think there are a few code parts that won't work with 1.8, but that might also be me not understanding the data model

Bug#910062: torbrowser-launcher will not open URL argument

Control: tag -1 + wishlist Control: tag -1 + upstream Mikko Viinamäki: > Provided an URL argument it will not point tor browser to the URL > requested. Indeed. Can you please check if there's already an upstream feature request about this, and if not, create one? Thanks!

Bug#910072: RM: php7.1/7.1.20-1

On Tue, Oct 02, 2018 at 04:47:17PM +0200, Ondřej Surý wrote: > Control: close -1 [..] > > Let's go ahead with this removal then. > > Ack, agreed. That's confusing, you agreed with the removals (note that all of this bickering is happening in the 7.1 bug, while you probably cared about 7.0), but

Bug#909838: [Qa-jenkins-dev] Bug#909838: reproducible sometimes uses outdated package lists

control: severity -1 important thanks Hi Adrian, thanks for filing this bug report. On Sat, Sep 29, 2018 at 02:58:04PM +0300, Adrian Bunk wrote: > I've seen this specific issue (meson 0.48.0-1 still used) several > times in recent days, always on arm64. > > Holger mentioned that there have

Bug#910078: the bold capability does not work after sgr0

Package: libvte-2.91-0 Version: 0.54.0-1 Severity: normal Test case: echo "A$(tput bold)B$(tput sgr0)C$(tput bold)D$(tput sgr0)E" Expected results (verified with xterm and others): B and D are printed in bold (i.e. white, not grey). Actual results: only B is printed in bold. Something in my

Bug#910079: apt: fails to “download” local files saying it lacks permissions despite having them

Package: apt Version: 1.7.0~rc2 Severity: normal […] Fetched 72.8 MB in 20s (3591 kB/s) Reading package lists... Done N: Download is performed unsandboxed as root as file '/home/tglase/Projekte/DebTarent/dists/sid/InRelease' couldn't be accessed by user '_apt'. - pkgAcquire::Run (13: Permission

Bug#910086: e2fsprogs: Perhaps FS-cache makes crypted content accessable for others.

Package: e2fsprogs Version: 1.43.4-2 Severity: important Dear Maintainer, I believe FS-cache is breaking ext4 crypt. - enabled crypt for a folder by user1 - created a file1 with content inside this folder by user1 - allowed user2 to read and write into this folder (simple POSIX group or

Bug#881845: [Pkg-rust-maintainers] Bug#881845: Bug#881845: Bug#881845: Bug#881845: Bug#881845: Bug#881845: Bug#881845: rustc: FTBFS on mips*: test failures

On 10/2/18 4:53 PM, Sylvestre Ledru wrote: >> Can you open bug reports against llvm-toolchain-6.0 and llvm-toolchain-7 to >> make sure, the fix gets backported? > I would prefer that rustc uses llvm 7 instead of 6. What is the current progress with this upstream? I have not followed up on this

Bug#909841: fc-cache failure preventing dpkg configuration of libreoffice updates

Ran into this problem when the aptitude upgrade was interrupted yesterday. Trying 'dpkg --configure -a' resulted in the following: dpkg: dependency problems prevent configuration of libreoffice-core: libreoffice-core depends on fontconfig; however: Package fontconfig is not configured yet.

Bug#908681: fixed in sane-backends 1.0.27-2

On 10/02/2018 02:57 PM, Jeremy Bicha wrote: > See the full change: > > https://jff.email/cgit/sane-backends.git/commit/?id=c85be9f4 > Wow, that's quite an inappropriate changelog entry and commit message for that change. > Julien, what do you think about my earlier proposal: > >> Julien, would

Bug#908931: transition: gnat-8, Ada component of gcc-8

The naive question at the end of the request was sincere. What should I do exactly? Should I rebuild and reupload each package manually? Or prepare lines like: nmu adabrowse_4.0.3-9 . ANY . -m 'Reupload to unstable to complete the gnat-8 transition.' dw music123_16.4-3 . ANY . -m 'gnat

Bug#910085: ITP: gnukhata-core -- Free Accounting Software (Core Engine)

Package: wnpp Severity: wishlist Owner: Manas Kashyap X-Debbugs-CC: debian-de...@lists.debian.org * Package name: gnukhata-core Version : 5.25.0 Upstream Author : Krishnakant Mane * URL : http://gnukhata.in * License : GPL - 3 Programming Lang: Python

Bug#909412: transition: libpodofo

On Tue, Oct 02, 2018 at 09:50:15AM +0200, Emilio Pozuelo Monfort wrote: > Please go ahead. Are you sure you want to go ahead even if this is going to get stuck in unstable thanks to openssl 1.1.1 (as it will pick a versioned dependency on that). -- regards, Mattia

Bug#904302: That's a free software issue!

Anonymous writes ("Bug#904302: That's a free software issue!"): > If Debian want patches it has to support this process with tools. The > attitude Debian owns all source packages is wrong. Sharing source > packages among different vendors is more efficient. Different patch > series may be the best

Bug#910072: RM: php7.1/7.1.20-1

> On 2 Oct 2018, at 12:43, Mattia Rizzolo wrote: > > Control: reassign -1 ftp.debian.org > Control: retitle -1 RM: php7.1 -- RoM; obsolete php version > > On Tue, Oct 02, 2018 at 10:35:23AM +, Ondřej Surý wrote: >> Package: release.debian.org >> Severity: normal >> User:

Bug#910076: libtool: avoid the use of the dangerous, undocumented AC_TRY_EVAL macro, which generates binary data in config.log with dash

Control: tags -1 patch On 2018-10-02 13:46:23 +0200, Vincent Lefevre wrote: > I've seen in the autoconf source that AC_TRY_EVAL should not be used: > > # AC_TRY_EVAL(VARIABLE) > # - > # Evaluate $VARIABLE, which should be a valid shell command. > # The purpose of this macro

Bug#910082: molly-guard: Please ask for confirmation / list other user sessions

Package: molly-guard Version: 0.6.4 Severity: wishlist Dear Maintainer, *** Reporter, please consider answering these questions, where appropriate *** * What led up to the situation? Reboot triggered by a collegue A, while an other collegue B was loged in * What exactly did you do

Bug#892994: chromium 65.x issue with proxy

Hello, Just a note that I still have the same issue with Chromium 69.0.3497.92 Thanks, -- Pascal Obry / Magny Les Hameaux (78) The best way to travel is by means of imagination http://photos.obry.net http://www.obry.net gpg --keyserver keys.gnupg.net --recv-key F949BD3B

Bug#907491: closed by Paul Gevers (Re: goobook fails to authenticate)

On Mon, Oct 01, 2018 at 01:27PM, Sergio Mendoza wrote: > Hi Ilias, > > Today I performed a dist-upgrade and things are back to normal. goobook > runs fine as it should. Hope it doesn't go wrong again. Hi Sergio, Glad to hear that. This is expected, since the latest version of Goobook on

Bug#910084: caja gets glib warnings

Package: caja Version: 1.20.2-5 Severity: normal Dear Maintainer, Caja gets glib warnings - (caja:13511): GLib-GObject-WARNING **: 14:47:07.392: invalid (NULL) pointer instance (caja:13511): GLib-GObject-CRITICAL **: 14:47:07.392: g_signal_connect_data: assertion 'G_TYPE_CHECK_INSTANCE

Bug#906388: nipy: FTBFS in buster/sid (failing tests)

FWIW, two of the errors are caused by a bug in sympy which was fixed in 1.3 . I am preparing sympy 1.3 although didn't check yet if it would fix it in nipy tests (not clear why it wasn't triggered before) On Fri, 17 Aug 2018, Santiago Vila wrote: > Package: src:nipy > Version: 0.4.2-1 >

Bug#897091: lxc: New upstream version 3.0 LTS available

In debian unstable since kernel 4.18 creation of unprivileged containers does not work anymore. This is due to EPERM when opening /dev/null. See https://lists.linuxfoundation.org/pipermail/containers/2018-June/039176.html . A userspace solution have been implemented in LXC as of version 3.0.2 as

Bug#796180: libtool: generates binary data in config.log due to buggy escaping

Control: clone -1 -2 Control: reassign -2 libtool Control: retitle -2 libtool: avoid the use of the dangerous, undocumented AC_TRY_EVAL macro, which generates binary data in config.log with dash Control: forwarded -2 https://debbugs.gnu.org/cgi/bugreport.cgi?bug=21309 I've seen in the autoconf

Bug#910081: nm.debian.org: IntegrityError - duplicate key value violates unique constraint "keyring_key_fpr_key"

Package: nm.debian.org We are getting quite frequently these errors: Internal Server Error: /process/284 IntegrityError at /process/284 duplicate key value violates unique constraint "keyring_key_fpr_key" DETAIL: Key (fpr)=(884A52C4AC8ABB931D158FA840BFEE868B055D9A) already exists. Request

Bug#910083: fai-client: setting romountopt via "Use Default Values ( ${parameter:-word} )"

Package: fai-server Version: 5.3.6 Severity: wishlist Dear Maintainer, Please use ${parameter:-word} to export romountopt in /usr/sbin/fai for ex: export romountopt=${romountopt:-"-o async,noatime,nolock,ro,actimeo=1800"} we have to patch /usr/sbin/fai to set romountopt to something like

Bug#909849: evince: apparmor profile hardening

Control: user -1 pkg-apparmor-t...@lists.alioth.debian.org Control: usertags -1 + modify-profile On Sat, Sep 29, 2018 at 10:15 AM Jamie Strandboge wrote: > In Ubuntu, the attached patch was applied to achieve the following: > > * debian/apparmor-profile.abstraction, apparmor-profile: harden

Bug#909849: evince: apparmor profile hardening

On Tue, 02 Oct 2018, Jeremy Bicha wrote: > Control: user -1 pkg-apparmor-t...@lists.alioth.debian.org > Control: usertags -1 + modify-profile > > On Sat, Sep 29, 2018 at 10:15 AM Jamie Strandboge wrote: > > In Ubuntu, the attached patch was applied to achieve the following: > > > > *

Bug#910093: maven-compiler-plugin: tests fail due to hardcoded junit jar path and missing JAVA_HOME

Package: maven-compiler-plugin Version: 3.8.0-1 Severity: minor Dear Maintainer, Currently maven-compiler-plugin tests are failing due to 2 different reasons: 1. Some tests depend on JAVA_HOME being set 2. The junit jar file is hardcoded to version 3.8.1 Excerpt of the buildlog with the test

Bug#871473: logwatch: Logwatch email messages fail with vanilla exim4 install: message is too big (transport limit = 1)

Hi Peter, Am 08.08.17 um 11:41 schrieb Peter Collinson: > Alternative and better solution: I added --encode=base64 to > 00logwatch in cron.daily, after ensuring that libmime-tools-perl > was installed. Line wrapping is no longer a problem. the problem with the base64 option is

Bug#910088: python-pyperclip: please provide a backport of python-pyperclip

On Oct/02, Mattia Rizzolo wrote: > Could you please provide a stretch-backports of python-pyperclip? > > If you wish, I'm happy to build such backport myself. Yes, that will be fine: please do ! Cheers, --Seb

Bug#910100: libvidstab FTCBFS: passes -msse2

Source: libvidstab Version: 1.1.0-1 Severity: serious Justification: baseline violation on i386 Tags: patch libvidstab fails to cross build from source when built on amd64, because it passes -msse2 and e.g. an armel cross compiler does not like that flag. Looking at /proc/cpuinfo is not a good

Bug#850921: you could help with jgit perhaps ?

Dear Rudy, Just saw your response on https://bugs.debian.org/850921 . There is ongoing discussion on gradle bug https://bugs.debian.org/909905 . Maybe packaging a new jgit (if possible) may make it easier. You could join https://lists.debian.org/debian-java/ and also talk to people there.

Bug#891620: Transition of linphone

On 15/09/2018 12:06, Dr. Tobias Quathamer wrote: > Dear all, > > unfortunately, there's basically no progress in this bug report, as far > as I can tell. So I think that it's unlikely that kopete will be able to > build with libmediastreamer 2.16. > > Would it be an option to provide *both*

Bug#910090: SD card reader does not work any more

Package: src:linux Version: 4.18.8-1 Severity: minor Hi, since a few kernel versions (sorry, I don't know which one), SD cards put into the built-in reader of the ThinkPad T520 don't work any more. There is nothing happening in the kernel log when the card is inserted. Any information that I

Bug#910098: groovy: improve doc linking and add missing dependencies

Package: groovy Version: 2.4.15-3 Severity: normal Dear Maintainer, The groovy doc linking can be improved by adding a few docs that have been packaged in Debian. Also, the previous fix for the jre doc link was using a URI with a single slash, which although works is not the standard.

Bug#910099: lqa: please don't build-depend on python3-all-dev

Source: lqa Version: 20180702.0-1 Severity: normal Dear maintainer, I've noticed that your package lqa build-depends on python3-all-dev, whilst building only architecture-idependant packages. This is actively causing issues during Python3 transitions, as it causes people to waste their time in

Bug#881845: [Pkg-rust-maintainers] Bug#881845: Bug#881845: Bug#881845: Bug#881845: Bug#881845: Bug#881845: rustc: FTBFS on mips*: test failures

Hi YunQiang! On 10/2/18 4:48 PM, YunQiang Su wrote: > this problem has been fixed on upstream. > > https://reviews.llvm.org/rL336328 > > llvm-6 seems still have this problem, while I guess llvm 7 should be OK now. Can you open bug reports against llvm-toolchain-6.0 and llvm-toolchain-7 to make

Bug#909023: (no subject)

FWIW, Tails' infra runs stretch's git-annex 6.20170101-1+deb9u2 (and gitolite 2.3-1, if relevant), and I am hit by this bug when using sid's git-annex (6.20180913-1) as a client. I worked around it by downgrading to stretch's version for my client as well.

Bug#881845: [Pkg-rust-maintainers] Bug#881845: Bug#881845: Bug#881845: Bug#881845: Bug#881845: Bug#881845: rustc: FTBFS on mips*: test failures

this problem has been fixed on upstream. https://reviews.llvm.org/rL336328 llvm-6 seems still have this problem, while I guess llvm 7 should be OK now. YunQiang Su 于2018年9月27日周四 上午9:33写道： > > It is still about llvm+octeon problem. > > Maybe we can ask pin rustc on Loongson machines. > Ximin Luo

Bug#910072: RM: php7.1/7.1.20-1

Control: close -1 > Well, why keep it? I just wanted to have a little bit more time to think it through if that would have any impact. The sudden move made me think about it and it’s fine to remove them. > Unless you have any weird needs like helping to > prepare/stage stable or security

Bug#910086: correction / additional info

I can't reproduce my 8th step " = directory listing by user2 shows scrambled filenames - like expected". Now I'll see readable filenames as user2 as soon as user1 has decrypted. This I've not expected. Also it makes no difference if I store the key in sessions or users keyring. Mit

Bug#881845: [Pkg-rust-maintainers] Bug#881845: Bug#881845: Bug#881845: Bug#881845: Bug#881845: Bug#881845: Bug#881845: rustc: FTBFS on mips*: test failures

Le 02/10/2018 à 16:50, John Paul Adrian Glaubitz a écrit : > Hi YunQiang! > > On 10/2/18 4:48 PM, YunQiang Su wrote: >> this problem has been fixed on upstream. >> >> https://reviews.llvm.org/rL336328 >> >> llvm-6 seems still have this problem, while I guess llvm 7 should be OK now. > > Can you

Bug#910083: fai-client: setting romountopt via "Use Default Values ( ${parameter:-word} )"

> On Tue, 02 Oct 2018 15:56:14 +0200, Reiner Schulz > said: > Please use ${parameter:-word} to export romountopt in /usr/sbin/fai > for ex: > export romountopt=${romountopt:-"-o async,noatime,nolock,ro,actimeo=1800"} Thanks for this patch. It's now included. See

Bug#910087: nvidia-kernel-dkms: nvidia kernel module does not build against 4.18 kernel

On Tue, 02 Oct 2018 at 16:10 +0100, Luca Boccassi wrote: > 4.18 is not the kernel from Stretch. Either downgrade the kernel, or > upgrade the drivers to backports. Is installing nvidia-driver from stretch and the kernel from stretch-backports not supported? If I install the kernel from

Bug#910091: libsmbclient: rmdir on non-empty samba directory fails silently

Package: libsmbclient Version: 2:4.7.6+dfsg~ubuntu-0ubuntu2.2 Severity: important Dear Maintainer, the bug is caused by faulty samba servers running on debian stretch machines, but I don't have ssh access. So I report this bug from my client machine running Mint 19. The bug seems to be fixed

Bug#910094: black: please don't build-depend on python3-all-dev

Source: black Version: 18.9b0-1-1 Severity: normal Dear maintainer, I've noticed that your package black build-depends on python3-all-dev, whilst building only architecture-idependant packages. Actually, it build-depends on: python3 | python3-all | python3-dev | python3-all-dev which is

Bug#909949: RFS: android-platform-system-extras/8.1.0+r23-1 (experimental)

Thanks for the sponsor again, Roger! I did push the changes already, check . Or do you mean you want a dedicated merge request so you can leave comments their so that in a more

Bug#910098: groovy: improve doc linking and add missing dependencies

Please consider the attached patch. It includes one additional "fix" from the Ubuntu delta to get groovydoc to ignore a file which was causing groovydoc to output a NUL char to stdout, that in turn caused the archive builders to fail - something about the python script giving up due to the

Bug#910072: RM: php7.1/7.1.20-1

Control: reopen -1 > On 2 Oct 2018, at 17:05, Mattia Rizzolo wrote: > > On Tue, Oct 02, 2018 at 04:47:17PM +0200, Ondřej Surý wrote: >> Control: close -1 > [..] >>> Let's go ahead with this removal then. >> >> Ack, agreed. > > That's confusing, you agreed with the removals (note that all of

Bug#902582: (some kind of) transition: add python3.7 as a supported python3 version

On 23/09/2018 15:40, Andreas Beckmann wrote: > Followup-For: Bug #902582 > > Hi, > > the ben file is bad since it misses -dbg packages, the following should > work better: > > is_affected = .build-depends ~ /python3-all-dev/; > is_good = .depends ~ /python3 \(<< 3\.8\)/ | .depends ~ /python3.7/

Bug#910095: epoptes: please don't build-depend on python3-all-dev

Source: epoptes Version: 1.0.1-1 Severity: normal Dear maintainer, I've noticed that your package epoptes build-depends on python3-all-dev, whilst building only architecture-idependant packages. Actually, it build-depends on: python3 | python3-all | python3-dev | python3-all-dev which is

Bug#863511: Build now works

Hi, I saw that the build for version 0.39 now works : https://buildd.debian.org/status/fetch.php?pkg=numba=ppc64el=0.39.0-1=1533813201=0 Probably because llvm6.0 is now at level 6.0.1-2 . So I guess the bug can be closed in next Debian release. F. pgpWZYBegHayU.pgp Description: PGP signature

Bug#910096: revolt: please don't build-depend on python3-all-dev

Source: revolt Version: 0.0+git20170627.3f5112b-3 Severity: normal Dear maintainer, I've noticed that your package revolt build-depends on python3-all-dev, whilst building only architecture-idependant packages. Actually, it build-depends on: python3 | python3-all | python3-dev |

Bug#910093: maven-compiler-plugin: tests fail due to hardcoded junit jar path and missing JAVA_HOME

Please consider the attached patch. diff -Nru maven-compiler-plugin-3.8.0/debian/changelog maven-compiler-plugin-3.8.0/debian/changelog --- maven-compiler-plugin-3.8.0/debian/changelog 2018-07-30 09:26:41.0 +0200 +++ maven-compiler-plugin-3.8.0/debian/changelog 2018-09-21

Bug#910097: isdnutils hard codes various system header locations

Source: isdnutils Version: 1:3.25+dfsg1-9.1 Tags: patch upstream Control: block 798955 by -1 isdnutils hard codes various system header locations. As such it will fail to build against a non-glibc libc or against a glibc that fixes #798955. The attached patch removes the such assumptions and

Bug#906880: Also present on 4.18

Occurs with 4.18 also, specifically tested on: 4.18.0-0.bpo.1-amd64 #1 SMP Debian 4.18.6-1~bpo9+1 (2018-09-13) x86_64 GNU/Linux

Bug#881845: [Pkg-rust-maintainers] Bug#881845: Bug#881845: Bug#881845: Bug#881845: Bug#881845: Bug#881845: Bug#881845: Bug#881845: rustc: FTBFS on mips*: test failures

Le 02/10/2018 à 16:55, John Paul Adrian Glaubitz a écrit : > On 10/2/18 4:53 PM, Sylvestre Ledru wrote: >>> Can you open bug reports against llvm-toolchain-6.0 and llvm-toolchain-7 to >>> make sure, the fix gets backported? >> I would prefer that rustc uses llvm 7 instead of 6. > > What is the

Bug#910087: nvidia-kernel-dkms: nvidia kernel module does not build against 4.18 kernel

On Tue, 2018-10-02 at 15:23 +, Markus Lindberg wrote: > On Tue, 02 Oct 2018 at 16:10 +0100, Luca Boccassi wrote: > > 4.18 is not the kernel from Stretch. Either downgrade the kernel, > > or > > upgrade the drivers to backports. > > Is installing nvidia-driver from stretch and the kernel from

Bug#881845: [Pkg-rust-maintainers] Bug#881845: Bug#881845: Bug#881845: Bug#881845: Bug#881845: Bug#881845: Bug#881845: Bug#881845: rustc: FTBFS on mips*: test failures

On 02/10/2018 17:26, Sylvestre Ledru wrote: > Le 02/10/2018 à 16:55, John Paul Adrian Glaubitz a écrit : >> On 10/2/18 4:53 PM, Sylvestre Ledru wrote: Can you open bug reports against llvm-toolchain-6.0 and llvm-toolchain-7 to make sure, the fix gets backported? >>> I would prefer that

Bug#910088: python-pyperclip: please provide a backport of python-pyperclip

Source: python-pyperclip Dear maintainer, In persuit of updating the stretch-backports of jenkins-job-builder, I struct myself with a non-trivial tree of dependencies and I came to python-pyperclip. python-cliff >= 2.8.0 requires python-cmd2 >= 0.8.5 which in truns requires python-pyperclip >=

Bug#910089: cmd2: please provide a backport of cmd2

Source: cmd2 Control: block -1 by 910088 Dear maintainer, In persuit of updating the stretch-backports of jenkins-job-builder, I struck myself with a non-trivial tree of dependencies and I came to cmd2. python-cliff >= 2.8.0 requires python-cmd2 >= 0.8.5. Could you please provide a

Bug#910092: 2ping: please don't build-depend on python3-all-dev

Source: 2ping Version: 4.2-1 Severity: normal Dear maintainer, I've noticed that your package 2ping build-depends on python3-all-dev, whilst building only architecture-idependant packages. This is actively causing issues during Python3 transitions, as it causes people to waste their time in

Bug#904274: nodejs: Debian nodejs is not ABI-compatible with upstream nodejs

Package: nodejs Followup-For: Bug #904274 So if i still think clear about this, the practical thing we, debian maintainers, need to do, is follow https://github.com/nodejs/node/pull/22237/commits/e47d5c6ff9426074184d508c113c85fe93629b05 TLDR "make a custom NODE_MODULE_VERSION". However the

Bug#909842: stretch-pu: package libx11/2:1.6.4-3

Control: tags -1 + moreinfo d-i On Sat, 2018-09-29 at 14:24 +0200, Markus Koschany wrote: > I would like to update libx11 in Stretch because it is currently > affected by CVE-2018-14598, CVE-2018-14599 and CVE-2018-14600. The > security team marked all issues as no-dsa. Please find attached the >

Bug#907513: RM: mshr-demos -- ROM; no longer built; blocks transition

Package: ftp.debian.org Followup-For: Bug #907513 By the way, the fact that mshr-demos is blocking mshr seems to be a bug in britney2. mshr-demos is apparently not getting added to the autocruft list. Bug filed #909555.

Bug#906857: stretch-pu: package fuse/2.9.7-1+deb9u2

Gentle ping. On Sun, 2018-09-02 at 20:58 +0100, Adam D. Barratt wrote: > Control: tags -1 + moreinfo d-i > > On Sun, 2018-08-26 at 21:21 +0200, László Böszörményi wrote: > > On Sun, Aug 26, 2018 at 3:54 PM Adam D. Barratt > > wrote: > > > Control: tags -1 + confirmed > > > > > > On 2018-08-21

Bug#904732:

I am experiencing the same issue, following the instructions from: https://ci.debian.net/doc/file.MAINTAINERS.html Running: sudo debci setup

Bug#910106: linux-image-4.9.0-8-amd64: Ethernet device names reverted to old eth* naming scheme after latest security update

Package: src:linux Version: 4.9.110-3+deb9u5 Severity: important Dear Maintainer, * What led up to the situation? After latest security updates of two packages (linux-image-4.9.0-8-amd64 4.9.110-3+deb9u and linux-libc-dev 4.9.110-3+deb9u5) and subsequent system reboot some ethernet device

Bug#909974: backports.ssl-match-hostname should be removed for buster

Hi Matthias, Ivo, On Sun, 30 Sep 2018 22:59:26 +0200 Ivo De Decker wrote: > clone 869896 -1 > retitle -1 remove unneeded dependency on backports.ssl-match-hostname > block 869896 by -1 > clone -1 -2 -3 -4 -5 > reassign -1 libcloud > reassign -2 python-docker > reassign -3 websocket-client >

Bug#909000: Enigmail 2.0 needed in Stretch after Thunderbird 60 upload

On Mon 2018-09-17 15:44:03 -0400, Daniel Kahn Gillmor wrote: > * i subsequently discovered that the enigmail test suite was inadequate >for the Autocrypt Setup Message -- i'm currently working on fixing >that. (this is #908510) I'm happy to report that the enigmail test suite fully

Bug#904302: Whether vendor-specific patch series should be permitted in the archive

Hello, On Tue 02 Oct 2018 at 07:48PM +0200, Tollef Fog Heen wrote: > Given the entire decision has been delegated to us, I think we should, > yes. If we'd just been asked to decide on a matter of technical policy, > that would have been slightly different. I think that the wording of my

Bug#910074: linux-image-4.9.0-8-amd64: BTRFS data loss - kernel BUG at .../linux-4.9.110/fs/btrfs/ctree.c:3178

Hi Michael, On Tue, Oct 02, 2018 at 11:37:45AM +0100, Michael Firth wrote: > > After this, there was a file that was errored on the filesystem (as > reported by 'btrfs check'), and it seems BTRFS doesn't have any tools to > resolve the error. Deleting the file at the reported inode has cleared >

Bug#852931: closing this bug

Control: close -1 Hi, I'm closing this bug as the problem was caused by a user-supplied regex. Willi

Bug#910103: sane-backends: Support drivers in non-multiarch directory

Source: sane-backends Version: 1.0.27-2 X-Debbugs-CC: jbla...@debian.org I think the intent was for https://jff.email/cgit/sane-backends.git/tree/debian/patches/0125-multiarch_dll_search_path.patch to still support drivers installed to the non-multiarch directory but I believe it doesn't work.

Bug#909584: ITA rapid-photo-downloader

Am 1. Oktober 2018 22:51:26 MESZ schrieb "Antoine Beaupré" : >On 2018-09-26 10:03:16, Antoine Beaupré wrote: >> On 2018-09-26 13:50:09, Dr. Tobias Quathamer wrote: >>> If you'd like to have the package, I'll retract my ITA, of course. >> >> No - the reason I got involved is because I use the

Bug#910105: llvm-toolchain-5.0: stay out of testing

Source: llvm-toolchain-5.0 Severity: serious Hi, llvm-toolchain-5.0 is not in testing. Let's keep it that way. We should ship buster with llvm 6.0 and 7. Cheers, Emilio

Bug#910104: hypre: autopkgtest times out most of the times

Source: hypre Version: 2.14.0-3 X-Debbugs-CC: debian...@lists.debian.org User: debian...@lists.debian.org Usertags: timeout Dear maintainers, Since version 2.14.0-3 your package has an autopkgtest. That's great. However, of the runs so far (6 as of writing) your package timed out (after 2:47h) 4

Bug#907829: p4est: FTBFS on single CPU machines

On Sun, Sep 30, 2018 at 11:49:26PM +0300, Adrian Bunk wrote: > Noone disagrees that these are bugs. True, but you seem to consider them second-class FTBFS bugs. However, it is not "just a bug", which is how you seem to paint it. It is a FTBFS bug, possibly the worst kind of bug a package may

Bug#910110: aptitude: aptitude does not update libxapian30 during aptitude "self upgrade"

Package: aptitude Version: 0.8.11-3 Severity: important Tags: d-i Dear Maintainer, ** IMPORTANT ** current report was not created on affected system, so do not take into account "bugreport" automatic attached informations. ** /IMPORTANT ** Issue occure into a Debian Testing system. I've to

Bug#906643: transition: php7.3

Control: tags -1 confirmed Control: forwarded -1 https://release.debian.org/transitions/html/php7.3.html On 19/08/2018 08:49, Ondřej Surý wrote: > Package: release.debian.org > Severity: normal > User: release.debian@packages.debian.org > Usertags: transition > > Hi, > > with PHP

Bug#905889: transition: gdbm

On Tue, Oct 02, 2018 at 09:38:32AM +0200, Emilio Pozuelo Monfort wrote: > On 11/08/2018 09:40, Dmitry Bogatov wrote: > > Package: release.debian.org > > Severity: normal > > User: release.debian@packages.debian.org > > Usertags: transition > > > > Hello. According to [1] I request approval of

Bug#910107: pipenv: Bundles a large number of third-party libraries

Source: pipenv Version: 11.9.0-1 Severity: important X-Debbugs-CC: Bastian Venthur , ftpmas...@debian.org Hi, I just ACCEPTed pipenv from NEW but was wondering if you could fix it a) shipping a large number of third-party libraries in the source tarball but moreover b) installing (and using?)

Bug#910108: RFP: git-bug -- Distributed bug tracker embedded in Git

Package: wnpp Severity: wishlist * Package name: git-bug Version : 0.3.0 Upstream Author : Michael Muré * URL : https://github.com/MichaelMure/git-bug * License : GPL-3+ Programming Lang: Golang Description : Distributed bug tracker embedded in Git

Bug#910109: Subject: RFP: faircoin -- a digital currency that is powered by a cooperative grassroots movement

Package: wnpp Severity: wishlist * Package name: faircoin Version : 2.0.1 Upstream Author : Thomas König * URL : https://fair-coin.org/ * License : MIT/X Programming Lang: C Description : a digital currency that is powered by a cooperative grassroots

Bug#908712: linux-image-4.17.0-0.bpo.3-marvell: stretch-backports kernel 4.17 breaks QNAP TS-209

Hello, > I can try this weekend whether removing systemd makes a difference. > Installing sysvinit-core made no difference. I tried the older backports-kernels and the problem exists already with linux-image-4.12.0-0.bpo.2-marvell_4.12.13-1~bpo9+1_armel.deb.

Bug#910098: groovy: improve doc linking and add missing dependencies

Please consider this patch and disregard the old one. I have dropped the ignore rule - it does not even use the debian/docs.gradle file - and replaced the default-jdk-doc/api with default-jdk/api as previously discussed in bug #896439 (ie. do not use the -doc paths according to Debian Policy

Bug#910101: git-review: new upstream release

Package: git-review Version: 1.26.0-1 Severity: wishlist git-review 1.27 has been released[1]. Most notably, it uses the recommended refs/for/ syntax[2] instead of refs/publish/ to push changes for review[3]. I tried importing the new version using gbp-import-orig and building and it seems to

  1   2   3   >