Bug#890936: marked as done (golang-gopkg-ini.v1: FTBFS and Debci failure with golang-1.10-go)

2018-06-19 Thread Debian Bug Tracking System
Your message dated Wed, 20 Jun 2018 05:49:00 + with message-id and subject line Bug#890936: fixed in golang-gopkg-ini.v1 1.37.0-1 has caused the Debian Bug report #890936, regarding golang-gopkg-ini.v1: FTBFS and Debci failure with golang-1.10-go to be marked as done. This means that you

Bug#901893: marked as done (fortunes-debian-hints: FTBFS in buster/sid (hints-ar: No such file or directory))

2018-06-19 Thread Debian Bug Tracking System
Your message dated Wed, 20 Jun 2018 05:48:51 + with message-id and subject line Bug#901893: fixed in fortunes-debian-hints 2.01.2 has caused the Debian Bug report #901893, regarding fortunes-debian-hints: FTBFS in buster/sid (hints-ar: No such file or directory) to be marked as done. This

Bug#900051: libgnupg-interface-perl: t/get_public_keys.t fails with gnupg2/2.2.7-1

2018-06-19 Thread intrigeri
FWIW it's unlikely that I have time to work on this myself before DebCamp *but* if they've not been solved by then, fixing these regressions will be one of my top priorities at DebCamp (ideally with someone else).

Bug#839433: marked as done (golang-github-robfig-cron: FTBFS: dh_auto_test: go test -v -p 1 github.com/robfig/cron returned exit code 1)

2018-06-19 Thread Debian Bug Tracking System
Your message dated Wed, 20 Jun 2018 15:08:24 +1000 with message-id <117673582.yEeq6YN6Wx@deblab> and subject line Done: golang-github-robfig-cron: FTBFS: dh_auto_test: go test -v -p 1 github.com/robfig/cron returned exit code 1 has caused the Debian Bug report #839433, regarding

Processed: tagging 901884, tagging 901884 ...

2018-06-19 Thread Debian Bug Tracking System
Processing commands for cont...@bugs.debian.org: > tags 901884 - moreinfo Bug #901884 [cryptsetup-initramfs] [cryptsetup-initramfs] Unbootable system with MODULES=dep Removed tag(s) moreinfo. > tags 901884 + pending Bug #901884 [cryptsetup-initramfs] [cryptsetup-initramfs] Unbootable system

Bug#901897: git introduces new hazardous working-tree-encoding attribute

2018-06-19 Thread Jonathan Nieder
Hi Ian, My mail host appears to be blacklisted on your end: > There was a problem delivering your message to > ijack...@chiark.greenend.org.uk. See the technical details below, or > try resending in a few minutes. > > The response was: > 550 Blacklisted site `[74.125.83.53]' [Irritated] What is

Bug#901897: git introduces new hazardous working-tree-encoding attribute

2018-06-19 Thread Jonathan Nieder
severity 851679 wishlist tags 851679 + upstream clone 901897 -1 retitle -1 dgit fails autopkgtest: true/false are no valid working-tree-encodings reassign -1 dgit 5.0 retitle 901897 git needs Breaks against dgit versions without working-tree-encoding support block 901897 by -1 quit Hi Ian, Ian

Processed: Re: git introduces new hazardous working-tree-encoding attribute

2018-06-19 Thread Debian Bug Tracking System
Processing commands for cont...@bugs.debian.org: > severity 851679 wishlist Bug #851679 [git] Want way to disable all checkout-affecting gitattributes Severity set to 'wishlist' from 'normal' > tags 851679 + upstream Bug #851679 [git] Want way to disable all checkout-affecting gitattributes Added

Bug#897535: openafs: FTBFS: dh_auto_test: make -j1 test VERBOSE=1 returned exit code 2

2018-06-19 Thread Benjamin Kaduk
(ditto) On Wed, May 30, 2018 at 11:18:11AM -0500, Benjamin Kaduk wrote: > (resetting autoremoval timer) > > On Fri, May 11, 2018 at 12:44:01PM -0500, Benjamin Kaduk wrote: > > ping? > > > > I cannot reproduce locally either on bare metal or in schroot. > > > > -Ben > > > > On Fri, May 04,

Bug#901519: marked as done (gdcm: FTBFS: xsltApplySequenceConstructor: A potential infinite template recursion was detected.)

2018-06-19 Thread Debian Bug Tracking System
Your message dated Wed, 20 Jun 2018 00:04:11 + with message-id and subject line Bug#901519: fixed in gdcm 2.8.6-3 has caused the Debian Bug report #901519, regarding gdcm: FTBFS: xsltApplySequenceConstructor: A potential infinite template recursion was detected. to be marked as done. This

Bug#901519: marked as done (gdcm: FTBFS: xsltApplySequenceConstructor: A potential infinite template recursion was detected.)

2018-06-19 Thread Debian Bug Tracking System
Your message dated Tue, 19 Jun 2018 23:34:06 + with message-id and subject line Bug#901519: fixed in gdcm 2.8.6-3exp1python3 has caused the Debian Bug report #901519, regarding gdcm: FTBFS: xsltApplySequenceConstructor: A potential infinite template recursion was detected. to be marked as

Bug#901897: git introduces new hazardous working-tree-encoding attribute

2018-06-19 Thread Ian Jackson
Package: git Version: 1:2.18.0~rc2-1 Severity: serious Justification: breaks dgit test suite, breaks existing attempts not to corrupt data Firstly, apologies for filing this bug as RC. I wanted to prevent the new git migrating. It breaks the dgit autopkgtest. For reasons I don't understand,

Bug#901893: fortunes-debian-hints: FTBFS in buster/sid (hints-ar: No such file or directory)

2018-06-19 Thread Santiago Vila
Package: src:fortunes-debian-hints Version: 2.01.1 Severity: serious Dear maintainer: Since a few days, this package fails to build from source: Discard hints-ja (1 of 44 strings; only 2.27% translated; need 80%). Discard hints-pt (1 of 44 strings; only 2.27% translated; need 80%). Discard

Bug#901884: [cryptsetup-initramfs] Unbootable system with MODULES=dep

2018-06-19 Thread Guilhem Moulin
On Tue, 19 Jun 2018 at 23:52:45 +0200, Guilhem Moulin wrote: > Sorry, I meant between your backup initrd.img (presumably also compiled > with MODULES=dep) and the new, broken one. Alternatively, if you don't have this initrd around anymore, are you able to boot if you add the ‘xts’ module to the

Bug#901519: Bug #901519 in gdcm marked as pending

2018-06-19 Thread Gert Wollny
Control: tag -1 pending Hello, Bug #901519 in gdcm reported by you has been fixed in the Git repository and is awaiting an upload. You can see the commit message below, and you can check the diff of the fix at:

Processed: Bug #901519 in gdcm marked as pending

2018-06-19 Thread Debian Bug Tracking System
Processing control commands: > tag -1 pending Bug #901519 [src:gdcm] gdcm: FTBFS: xsltApplySequenceConstructor: A potential infinite template recursion was detected. Added tag(s) pending. -- 901519: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=901519 Debian Bug Tracking System Contact

Bug#901884: [cryptsetup-initramfs] Unbootable system with MODULES=dep

2018-06-19 Thread Guilhem Moulin
On Tue, 19 Jun 2018 at 23:00:29 +0200, Adrien CLERC wrote: > Le 19/06/2018 à 22:40, Guilhem Moulin a écrit : >> Could you run the following on both the broken and backup initrd and >> send the diff? >> >> lsinitramfs /path/to/initrd.img | grep ^lib/modules/ | sort > > See

Bug#901108: Bug #901108 in grr marked as pending

2018-06-19 Thread bengen
Control: tag -1 pending Hello, Bug #901108 in grr reported by you has been fixed in the Git repository and is awaiting an upload. You can see the commit message below, and you can check the diff of the fix at:

Processed: Bug #901108 in grr marked as pending

2018-06-19 Thread Debian Bug Tracking System
Processing control commands: > tag -1 pending Bug #901108 [src:grr] grr: FTBFS when built with dpkg-buildpackage -A Added tag(s) pending. -- 901108: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=901108 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems

Bug#901884: [pkg-cryptsetup-devel] Bug#901884: [cryptsetup-initramfs] Unbootable system with MODULES=dep

2018-06-19 Thread Adrien CLERC
Le 19/06/2018 à 23:06, Guilhem Moulin a écrit : > Just noticed what looks like a regression, I wonder if that's the same > problem. Does your system have AES-NI or similar, or are you using the > generic modules? What's the output of > > grep -A2 '^name *: *xts(aes)' /proc/crypto > # grep

Bug#901884: [cryptsetup-initramfs] Unbootable system with MODULES=dep

2018-06-19 Thread Adrien CLERC
Le 19/06/2018 à 22:40, Guilhem Moulin a écrit : > Could you run the following on both the broken and backup initrd and > send the diff? > > lsinitramfs /path/to/initrd.img | grep ^lib/modules/ | sort See initramfs_dep_vs_most.diff.gz. The dep output is not working, and the most output is

Bug#901884: [pkg-cryptsetup-devel] Bug#901884: [cryptsetup-initramfs] Unbootable system with MODULES=dep

2018-06-19 Thread Guilhem Moulin
On Tue, 19 Jun 2018 at 22:40:23 +0200, Guilhem Moulin wrote: > FWIW 2.0.3-2 was tested with MODULES=dep, too. I wonder how your system > differs from our test environments. Just noticed what looks like a regression, I wonder if that's the same problem. Does your system have AES-NI or similar,

Bug#901884: [cryptsetup-initramfs] Unbootable system with MODULES=dep

2018-06-19 Thread Guilhem Moulin
On Tue, 19 Jun 2018 at 21:39:06 +0200, Adrien CLERC wrote: > Fortunately, the previous one has still a valid initramfs, so I can boot > my system (many thanks for that backup system). > […] > Check that kernel supports aes-xts-plain64 cipher (check syslog for > more info). Could you run the

Processed: tagging 901884

2018-06-19 Thread Debian Bug Tracking System
Processing commands for cont...@bugs.debian.org: > tags 901884 + moreinfo Bug #901884 [cryptsetup-initramfs] [cryptsetup-initramfs] Unbootable system with MODULES=dep Added tag(s) moreinfo. > thanks Stopping processing here. Please contact me if you need assistance. -- 901884:

Bug#900051: libgnupg-interface-perl: t/get_public_keys.t fails with gnupg2/2.2.7-1

2018-06-19 Thread Niko Tyni
On Fri, May 25, 2018 at 05:06:21PM +0300, Niko Tyni wrote: > Control: severity -1 serious > > On Fri, May 25, 2018 at 11:05:58AM +0200, intrig...@debian.org wrote: > > Package: libgnupg-interface-perl > > Version: 0.52-9 > > Severity: important > > X-Debbugs-Cc: d...@debian.org > > > ci.d.n

Bug#901884: [cryptsetup-initramfs] Unbootable system with MODULES=dep

2018-06-19 Thread Adrien CLERC
Package: cryptsetup-initramfs Version: 2:2.0.3-2 Severity: critical --- Please enter the report below this line. --- Hi, I have a full disk-encryption set up with LUKS. After upgrading from 2.0.3-1 to 2.0.3-2 my last (and current) kernel is unbootable. Fortunately, the previous one has still a

Bug#901034: marked as done (libterm-readline-ttytter-perl: missing Breaks+Replaces: ttytter)

2018-06-19 Thread Debian Bug Tracking System
Your message dated Tue, 19 Jun 2018 18:49:32 + with message-id and subject line Bug#901034: fixed in libterm-readline-ttytter-perl 1.4-2 has caused the Debian Bug report #901034, regarding libterm-readline-ttytter-perl: missing Breaks+Replaces: ttytter to be marked as done. This means that

Bug#901878: glances: Fails to upgrade from 2.11.1-3 to 2.11.1-4: PID file not found ...

2018-06-19 Thread Axel Beckert
Package: glances Version: 2.11.1-4 Severity: serious Upgrading glances from 2.11.1-3 to 2.11.1-4 fails for me as follows: Setting up glances (2.11.1-4) ... Installing new version of config file /etc/init.d/glances ... [warn] Stopping Glances server: glances [] PID file not found ...

Bug#901877: cnvkit: FTBFS (No module named 'future')

2018-06-19 Thread Santiago Vila
Package: src:cnvkit Version: 0.9.3-1 Severity: serious Dear maintainer: This package fails to build from source: Traceback (most recent call last): File "../cnvkit.py", line 4, in from future import standard_library ModuleNotFoundError: No module named 'future' See:

Bug#870233: marked as done (smplayer: executes javascript code downloaded from insecure URL)

2018-06-19 Thread Debian Bug Tracking System
Your message dated Tue, 19 Jun 2018 18:22:38 + with message-id and subject line Bug#870233: fixed in smplayer 18.5.0~ds1-2 has caused the Debian Bug report #870233, regarding smplayer: executes javascript code downloaded from insecure URL to be marked as done. This means that you claim that

Bug#870233: Bug #870233 in smplayer marked as pending

2018-06-19 Thread siretart
Control: tag -1 pending Hello, Bug #870233 in smplayer reported by you has been fixed in the Git repository and is awaiting an upload. You can see the commit message below, and you can check the diff of the fix at:

Processed: Bug #870233 in smplayer marked as pending

2018-06-19 Thread Debian Bug Tracking System
Processing control commands: > tag -1 pending Bug #870233 [src:smplayer] smplayer: executes javascript code downloaded from insecure URL Added tag(s) pending. -- 870233: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=870233 Debian Bug Tracking System Contact ow...@bugs.debian.org with

Bug#718272: marked as done (upstream does not support stable releases (block migration to testing))

2018-06-19 Thread Debian Bug Tracking System
Your message dated Tue, 19 Jun 2018 19:21:09 +0200 with message-id <152942886931.8817.13979725455619503...@auryn.jones.dk> and subject line Re: Bug#718272: [Pkg-bitcoin-devel] Bug#718272: Bitcoin still not ready for stable release in Debian has caused the Debian Bug report #718272, regarding

Bug#718272: [Pkg-bitcoin-devel] Bug#718272: Bitcoin still not ready for stable release in Debian

2018-06-19 Thread Vincas Dargis
Any news after half a year? Why it's marked "fixed-upstream"?

Processed: fixed 895761 in 1.20.1-3

2018-06-19 Thread Debian Bug Tracking System
Processing commands for cont...@bugs.debian.org: > fixed 895761 1.20.1-3 Bug #895761 {Done: Jeff Breidenbach } [src:jhove] jhove: FTBFS with java 9 Marked as fixed in versions jhove/1.20.1-3. > thanks Stopping processing here. Please contact me if you need assistance. -- 895761:

Bug#849308:

2018-06-19 Thread Jason A. Donenfeld
To further summarize ongoing conversations: It appears that there many be another alternative, midway between the two extremes of stabilization on one hand and keeping this bug report open on the other. The idea is to ship WireGuard in stable-backports and in unstable, but not let this migrate to

Bug#895761: marked as done (jhove: FTBFS with java 9)

2018-06-19 Thread Debian Bug Tracking System
Your message dated Tue, 19 Jun 2018 09:08:37 -0700 with message-id and subject line jhove: FTBFS with java 9 has caused the Debian Bug report #895761, regarding jhove: FTBFS with java 9 to be marked as done. This means that you claim that the problem has been dealt with. If this is not the case

Bug#861546: marked as done (notary: FTBFS with latest golang-go.crypto)

2018-06-19 Thread Debian Bug Tracking System
Your message dated Tue, 19 Jun 2018 15:49:14 + with message-id and subject line Bug#861546: fixed in notary 0.6.1~ds1-1 has caused the Debian Bug report #861546, regarding notary: FTBFS with latest golang-go.crypto to be marked as done. This means that you claim that the problem has been

Bug#835782: marked as done (notary: FTBFS: dh_auto_build: go install -v -p 1 github.com/docker/notary github.com/docker/notary/client github.com/docker/notary/client/changelist github.com/docker/notar

2018-06-19 Thread Debian Bug Tracking System
Your message dated Tue, 19 Jun 2018 15:49:14 + with message-id and subject line Bug#835782: fixed in notary 0.6.1~ds1-1 has caused the Debian Bug report #835782, regarding notary: FTBFS: dh_auto_build: go install -v -p 1 github.com/docker/notary github.com/docker/notary/client

Processed: Re: freerdp2-shadow-x11 on startuo

2018-06-19 Thread Debian Bug Tracking System
Processing control commands: > severity -1 important Bug #886243 [freerdp2-shadow-x11] freerdp2-shadow-x11: SIGSEVs on start Severity set to 'important' from 'serious' > tags -1 moreinfo Bug #886243 [freerdp2-shadow-x11] freerdp2-shadow-x11: SIGSEVs on start Added tag(s) moreinfo. -- 886243:

Bug#886243: freerdp2-shadow-x11 on startuo

2018-06-19 Thread Mike Gabriel
Control: severity -1 important Control: tags -1 moreinfo Hi there, On Mon, 2 Apr 2018 13:18:21 +0200 =?UTF-8?Q?Holger_Schr=c3=b6der?= wrote: > Hi, > > > i have the same problem. > > > Greetings > >     Holger. Can you guys try again with the latest freerdp2 version in Debian testing? I

Bug#901863: crash 7.2.3 orig tarball does not ship gdb tarball

2018-06-19 Thread Thadeu Lima de Souza Cascardo
Package: crash Version: 7.2.3-2 Severity: serious After doing some work with using components to fix this, I realized that crash 7.2.1 didn't have the problem because the orig tarball included the gdb tarball. Funny thing is that I downloaded crash 7.2.3 from people.redhat.com/anderson and that

Bug#901859: libtcod ftbfs on ppc64el

2018-06-19 Thread Matthias Klose
Package: src:libtcod Version: 1.7.0+dfsg-1 Severity: serious Tags: sid buster libtcod ftbfs on ppc64el libtool: link: gcc -I./../../include -DNO_OPENGL -DNDEBUG -O2 -Wall -D_REENTRANT -I/usr/include/SDL2 -g -O2 -fdebug-prefix-map=/<>/libtcod-1.7.0+dfsg=. -fstack-protector-strong -Wformat

Bug#887687: libsmokeqt4-dev: broken symlinks and causes qt4-perl FTBFS

2018-06-19 Thread Lisandro Damián Nicanor Pérez Meyer
El jueves, 14 de junio de 2018 14:45:59 -03 Niko Tyni escribió: > On Fri, Jan 19, 2018 at 06:23:25AM +0200, Adrian Bunk wrote: > > Package: libsmokeqt4-dev > > Version: 4:4.14.3-1.2 > > Severity: serious > > Control: affects -1 src:qt4-perl > > > > qt4-perl FTBFS: > > > >

Bug#892742: rollup FTBFS with node-rollup-plugin-commonjs 9.0

2018-06-19 Thread Pirate Praveen
On Tue, 19 Jun 2018 16:16:15 +0530 Pirate Praveen wrote: > Latest version of rollup is 0.60.7 and it has already moved to > rollup-plugin-commonjs 9.x > > https://github.com/rollup/rollup/blob/6e004184ede79832e658c22983de439aa5c30462/package.json > Using node-rollup-plugin-typescript build

Bug#892742: rollup FTBFS with node-rollup-plugin-commonjs 9.0

2018-06-19 Thread Pirate Praveen
On Mon, 12 Mar 2018 18:41:36 +0530 Pirate Praveen wrote: > Package: src:node-rollup > Version: 0.50.0-1 Latest version of rollup is 0.60.7 and it has already moved to rollup-plugin-commonjs 9.x https://github.com/rollup/rollup/blob/6e004184ede79832e658c22983de439aa5c30462/package.json

Bug#901303: git-buildpackage: gbp import-orig --uscan skips unrelated files importing repacked tarball

2018-06-19 Thread Ian Jackson
Control: severity -1 normal Jonas, TBH I think the original `grave' severity for this bug was a bit inflated, even before it was investigated. (I have an interest in this because git-buildpackage is one a dependency of one of my packages.) For now I have refrained from merging this bug with

Processed: Re: git-buildpackage: gbp import-orig --uscan skips unrelated files importing repacked tarball

2018-06-19 Thread Debian Bug Tracking System
Processing control commands: > severity -1 normal Bug #901303 [git-buildpackage] git-buildpackage: gbp import-orig --uscan skips unrelated files importing repacked tarball Severity set to 'normal' from 'serious' -- 901303: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=901303 Debian Bug

Bug#891395: marked as done (libfabric1: improperly packaged library support files)

2018-06-19 Thread Roland Fehrenbacher
> "M" == Mehdi Dogguy writes: Hi Mehdi, M> Control: reopen -1 Hi Roland, M> If I am not mistaken, your last upload moves files across binary M> packages but doesn't add necessary Breaks/Replaces. In the M> current state, upgrades are broken because older libfabric1 and

Bug#897522: marked as done (golang-gopkg-libgit2-git2go.v26: FTBFS: dh_auto_test: cd obj-x86_64-linux-gnu && go test -vet=off -v -p 8 gopkg.in/libgit2/git2go.v26 returned exit code 1)

2018-06-19 Thread Debian Bug Tracking System
Your message dated Tue, 19 Jun 2018 10:00:12 + with message-id and subject line Bug#897522: fixed in golang-gopkg-libgit2-git2go.v27 0.27+git20180529.9abc050-1 has caused the Debian Bug report #897522, regarding golang-gopkg-libgit2-git2go.v26: FTBFS: dh_auto_test: cd obj-x86_64-linux-gnu

Bug#891395: marked as done (libfabric1: improperly packaged library support files)

2018-06-19 Thread Mehdi Dogguy
Control: reopen -1 Hi Roland, If I am not mistaken, your last upload moves files across binary packages but doesn't add necessary Breaks/Replaces. In the current state, upgrades are broken because older libfabric1 and newer libfabric-dev are not co-installable. Regards, -- Mehdi

Processed: Re: Bug#891395: marked as done (libfabric1: improperly packaged library support files)

2018-06-19 Thread Debian Bug Tracking System
Processing control commands: > reopen -1 Bug #891395 [libfabric1] libfabric1: improperly packaged library support files Bug 891395 is not marked as done; doing nothing. -- 891395: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=891395 Debian Bug Tracking System Contact ow...@bugs.debian.org

Processed: found 891395 libfabric/1.6.1-4

2018-06-19 Thread Debian Bug Tracking System
Processing commands for cont...@bugs.debian.org: > found 891395 libfabric/1.6.1-4 Bug #891395 {Done: Roland Fehrenbacher } [libfabric1] libfabric1: improperly packaged library support files Marked as found in versions libfabric/1.6.1-4; no longer marked as fixed in versions libfabric/1.6.1-4

Bug#901798: cantata: contains insecure mount.cifs wrapper, cantata-mounter

2018-06-19 Thread Simon McVittie
Control: retitle -1 cantata: contains insecure mount.cifs wrapper, cantata-mounter On Mon, 18 Jun 2018 at 22:11:55 +0200, Salvatore Bonaccorso wrote: > Unstable binary package has both > > /usr/share/dbus-1/system-services/mpd.cantata.mounter.service > > and > >

Processed: Re: Bug#901798: cantata: contains insecure mount.cifs wrapper, cantata-mounter

2018-06-19 Thread Debian Bug Tracking System
Processing control commands: > retitle -1 cantata: contains insecure mount.cifs wrapper, cantata-mounter Bug #901798 {Done: Stuart Prescott } [src:cantata] cantata: source contains insecure mount.cifs wrapper, cantata-mounter Changed Bug title to 'cantata: contains insecure mount.cifs wrapper,

Bug#891395: marked as done (libfabric1: improperly packaged library support files)

2018-06-19 Thread Debian Bug Tracking System
Your message dated Tue, 19 Jun 2018 08:49:45 + with message-id and subject line Bug#891395: fixed in libfabric 1.6.1-4 has caused the Debian Bug report #891395, regarding libfabric1: improperly packaged library support files to be marked as done. This means that you claim that the problem

Bug#882427: marked as done (manaplus FTBFS on ppc64el: test failure)

2018-06-19 Thread Debian Bug Tracking System
Your message dated Tue, 19 Jun 2018 08:25:43 + with message-id and subject line Bug#882427: fixed in manaplus 1.8.4.14-2 has caused the Debian Bug report #882427, regarding manaplus FTBFS on ppc64el: test failure to be marked as done. This means that you claim that the problem has been dealt

Bug#901526: Bug #901526 in python-django marked as pending

2018-06-19 Thread lamby
Control: tag -1 pending Hello, Bug #901526 in python-django reported by you has been fixed in the Git repository and is awaiting an upload. You can see the commit message below, and you can check the diff of the fix at:

Processed: Bug #901526 in python-django marked as pending

2018-06-19 Thread Debian Bug Tracking System
Processing control commands: > tag -1 pending Bug #901526 [src:python-django] python-django: FTBFS: FAIL: test_invalid (migrations.test_loader.PycLoaderTests) Added tag(s) pending. -- 901526: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=901526 Debian Bug Tracking System Contact

Bug#901835: radare2 ftbfs on i386 and mips*

2018-06-19 Thread Matthias Klose
Package: src:radare2 Version: 2.6.0+dfsg-1 Severity: serious Tags: sid buster make[3]: Leaving directory '/<>/radare2-2.6.0+dfsg/libr' make libr.so make[3]: Entering directory '/<>/radare2-2.6.0+dfsg/libr' make libr.so BUILD_MERGED=1 make[4]: Entering directory '/<>/radare2-2.6.0+dfsg/libr' gcc

Bug#901797: marked as done (python3.6-venv: can't create virtualenv due to ensurepip failing)

2018-06-19 Thread Debian Bug Tracking System
(v3.6) python3.6-minimal - Minimal subset of the Python language (version 3.6) python3.6-venv - Interactive high-level object-oriented language (pyvenv binary, v Closes: 901603 901797 Changes: python3.6 (3.6.6~rc1-3) unstable; urgency=medium . * Update to 20180619 from the 3.6 branch

Bug#901601: marked as done (python3-venv: Please remove python3-venv from archive)

2018-06-19 Thread Debian Bug Tracking System
ry, v Closes: 901603 901797 Changes: python3.6 (3.6.6~rc1-3) unstable; urgency=medium . * Update to 20180619 from the 3.6 branch. * Let ensurepip work with pip versions 9 or 10. Closes: #901797. * pdb(1): Fix pointer to HTML documentation. Closes: #901603. Checksums-Sha1: a4890ff1a678764790

Processed (with 1 error): forcibly merging 892539 901761

2018-06-19 Thread Debian Bug Tracking System
Processing commands for cont...@bugs.debian.org: > forcemerge 892539 901761 Bug #892539 [src:pdftk] pdftk: Depends on GCJ which is going away Unable to merge bugs because: package of #901761 is 'pdftk' not 'src:pdftk' Failed to forcibly merge 892539: Did not alter merged bugs. > thanks Stopping

Bug#900601: marked as done ([src:libantlr3c] Non free file : unicode)

2018-06-19 Thread Debian Bug Tracking System
Your message dated Tue, 19 Jun 2018 07:00:12 + with message-id and subject line Bug#900601: fixed in libantlr3c 3.4+dfsg-1 has caused the Debian Bug report #900601, regarding [src:libantlr3c] Non free file : unicode to be marked as done. This means that you claim that the problem has been

Bug#901542: marked as done (sreview: FTBFS: unable to load addon sysuser)

2018-06-19 Thread Debian Bug Tracking System
Your message dated Tue, 19 Jun 2018 06:51:02 + with message-id and subject line Bug#901542: fixed in sreview 0.3.1-2 has caused the Debian Bug report #901542, regarding sreview: FTBFS: unable to load addon sysuser to be marked as done. This means that you claim that the problem has been