Control: reassign -1 vtk7
Control: retitle -1 Don't drop some libvtkRendering* libraries
I don't think that this is a problem with gdcm, both camitk-imp and
camitk-config don't even list any gdcm library with ldd, but they both
list
libvtkRenderingFreeTypeFontConfig-7.1.so.7.1 => not found
Processing control commands:
> reassign -1 vtk7
Bug #911793 [src:gdcm] gdcm: ABI break
Bug reassigned from package 'src:gdcm' to 'vtk7'.
No longer marked as found in versions gdcm/2.8.7-2.
Ignoring request to alter fixed versions of bug #911793 to the same values
previously set
> retitle -1
On Sat, Nov 10, 2018 at 04:34:48PM +0100, Chris Hofstaedtler wrote:
> Hi everyone,
>
> thanks for reporting bugs against pdns in stretch.
> I intend to upload a new version to stretch to fix those bugs, but I
> cannot test all involved components personally. Please give this
> version a shot:
Package: photocollage
Version: 1.4.3-2
Severity: grave
Dear Maintainer,
I get the following error, when I try to start photocollage.
$ photocollage
Traceback (most recent call last):
File "/usr/bin/photocollage", line 21, in
from photocollage import gtkgui
File
Processing commands for cont...@bugs.debian.org:
> summary 911278 Package is no longer maintained; requested removal.
Summary recorded from message bug 911278 message
> thanks
Stopping processing here.
Please contact me if you need assistance.
--
911278:
Source: haskell-finite-field
Version: 0.8.0
Severity: serious
Justification: fails to build from source
This package is not part of LTS. Do we want to continue maintaining it?
If so, we will have to package singletons.
--
Ilias
Package: icingacli
Version: 2.6.1-1
Severity: grave
Justification: renders package unusable
Dear Maintainer,
an example:
icingacli --help
Fatal error: Uncaught ErrorException: "continue" targeting switch is equivalent
to "break". Did you mean to use "continue 2"? in
Hi,
pá 23. 11. 2018 v 13:21 odesílatel Ole Streicher
napsal:
> By reading the upstream changelog, I could not find a cause what should
> cause the incompatibility. Also, the logs now all contain a warning like
>
me either. :(
> /usr/lib/python2.7/dist-packages/_pytest/cacheprovider.py:58
>
Dear all
Thank to Paul for your answers about the autoremoval and explanation
about the ABI problem. It seems that Adrian Bunk's triage message in
909120 (added blocking bug(s) of 909120: 911793) did push the
autoremoval for another month (thanks to Adrian as well, as that's
exactly what is
Your message dated Fri, 23 Nov 2018 15:34:17 +
with message-id
and subject line Bug#914245: fixed in h5py 2.8.0-2
has caused the Debian Bug report #914245,
regarding h5py: FTBFS against hdf5 1.10.4 now in unstable
to be marked as done.
This means that you claim that the problem has been
Your message dated Fri, 23 Nov 2018 17:19:35 +
with message-id
and subject line Bug#913810: fixed in bzr 2.7.0+bzr6622-15
has caused the Debian Bug report #913810,
regarding bzr binary-all FTBFS: ERROR:
bzrlib.tests.blackbox.test_too_much.SFTPTestsAbsolute.test_push
to be marked as done.
Source: haskell-blogliterately
Version: 0.8.6.2-1
Severity: serious
Tags: upstream
Justification: fails to build from source (but built successfully in the past)
Forwarded: https://github.com/byorgey/BlogLiterately/issues/40
Fails to build with ghc-8.4.3 with the following error:
Richard,
gbonds is now 1 of the last 2 packages keeping rarian in Debian
Unstable. Do you think you'll be able to review these patches soon?
Thanks,
Jeremy Bicha
Processing commands for cont...@bugs.debian.org:
> limit source linux
Limiting to bugs with field 'source' containing at least one of 'linux'
Limit currently set to 'source':'linux'
> reassign 910348 src:linux 4.19~rc6-1~exp1
Bug #910348 {Done: Ben Hutchings } [linux-kbuild-4.19]
On 11/23/18 7:38 AM, Jeremy Bicha wrote:
> gbonds is now 1 of the last 2 packages keeping rarian in Debian
> Unstable. Do you think you'll be able to review these patches soon?
Yes. I've been busy with a new baby at home, but I intend to get to
these very soon.
--
Richard
Your message dated Fri, 23 Nov 2018 12:36:35 +
with message-id
and subject line Bug#914143: fixed in soundscaperenderer 0.5.0~dfsg-3
has caused the Debian Bug report #914143,
regarding soundscaperenderer FTBFS on armel/armhf
to be marked as done.
This means that you claim that the problem
Your message dated Fri, 23 Nov 2018 17:48:15 +0100
with message-id <20181123164815.GA13740@localhost>
and subject line bug fixed
has caused the Debian Bug report #914386,
regarding fritzing FTBFS: arch-only build
to be marked as done.
This means that you claim that the problem has been dealt
Processing control commands:
> severity -1 important
Bug #909637 [mmdebstrap] mmdebstrap: cannot install apt under fakechroot or
proot
Severity set to 'important' from 'grave'
--
909637: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=909637
Debian Bug Tracking System
Contact
Control: severity -1 important
On Wed, 26 Sep 2018 06:36:44 +0200 Johannes 'josch' Schauer
wrote:
> Apt uses 'mv' in its post inst. 'mv' from coreutils uses the renameat2
> systemcall. The renameat2 systemcall is not supported by fakechroot or
> proot.
downgrade severity to non-RC level
Source: node-rollup-plugin-alias
Version: 1.3.1-2
Severity: serious
Tags: ftbfs
X-Debbugs-CC: prav...@debian.org
node-rollup-plugin-alias can't build from source because it
Build-Depends on node-babel-preset-es2015-loose-rollup which is not in
Debian.
Thanks,
Jeremy Bicha
Source: maven-javadoc-plugin
Version: 3.0.1-1
Severity: serious
Tags: ftbfs
Some recent change in unstable makes maven-javadoc-plugin FTBFS:
https://tests.reproducible-builds.org/debian/history/maven-javadoc-plugin.html
tags 868551 + wontfix
thanks
Hi Adrian,
> > > … is too invasive for a stable update. The version in stable is a
> > > little outdated anyway, and the backport is recommended anyway…
[…]
> No disagreement from me.
Thanks. Tagging as wontfix accordingly.
Regards,
--
,''`.
: :' :
Processing commands for cont...@bugs.debian.org:
> tags 868551 + wontfix
Bug #868551 {Done: Chris Lamb } [src:redis] File conflict
between redis-server-dbgsym and redis-tools-dbgsym
Added tag(s) wontfix.
> thanks
Stopping processing here.
Please contact me if you need assistance.
--
868551:
Package: python-pytest
Version: 3.9.3-2
Severity: serious
Affects: python-astropy, python-ccdproc, astropy-healpix, python-drizzle
Dear maintainer,
many astronomy Python packages rely on pytest for build and CI tests.
The Python 2 tests are now broken with the new version of pytest, since
the
On Fri, Nov 23, 2018 at 11:41:10AM +0100, Mathieu Malaterre wrote:
> As you've noticed the ABI breakage occur in between two minor uploads
> -1 and -2. So I suspect this may confuse reader that bug be reported
> against src:gdcm, since obviously not a single line change could have
> occurred in
Processing commands for cont...@bugs.debian.org:
> clone 911371 -1
Bug #911371 [src:antlr4] antlr4: package v4.7.1 and include Cpp
libraries/headers
Bug 911371 cloned as bug 914434
894359 was blocked by: 911371
894359 was not blocking any bugs.
Added blocking bug(s) of 894359: 914434
902798 was
Control: tag -1 pending
Hello,
Bug #914062 in pyexiv2 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:
Processing control commands:
> tag -1 pending
Bug #914062 [src:pyexiv2] pyexiv2 FTBFS with boost 1.67
Added tag(s) pending.
--
914062: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=914062
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
Your message dated Fri, 23 Nov 2018 09:01:27 +0200
with message-id <8c28f96e-1775-1154-3136-6937298d5...@debian.org>
and subject line Fixed
has caused the Debian Bug report #914054,
regarding calamares FTBFS with boost 1.67
to be marked as done.
This means that you claim that the problem has been
Your message dated Fri, 23 Nov 2018 09:23:13 +
with message-id
and subject line Bug#914062: fixed in pyexiv2 0.3.2-9
has caused the Debian Bug report #914062,
regarding pyexiv2 FTBFS with boost 1.67
to be marked as done.
This means that you claim that the problem has been dealt with.
If this
Package: debhelper
Version: 11.5.2
Severity: serious
https://tests.reproducible-builds.org/debian/rb-pkg/unstable/amd64/apcupsd.html
...
dh clean --with autoreconf
dh_auto_clean
make V=1 -j16 clean
make[1]: Entering directory '/build/1st/apcupsd-3.14.14'
1find . -depth \
\( -name
Same problem here.
No more lightning after upgrading thunderbird to 1:60.3.0-1+b1
--
Pascal
Control: reassign -1 src:javahelper
Am 23.11.18 um 09:48 schrieb Matthias Klose:
> Package: src:libjide-oss-java
> Version: 3.7.4+dfsg-1
> Severity: serious
> Tags: sid buster
>
> Seen at
> https://bugs.launchpad.net/ubuntu/+source/starjava-ttools/+bug/1804773
>
> verified that a rebuild in
Processing control commands:
> reassign -1 src:javahelper
Bug #914417 [src:libjide-oss-java] libjide-oss-java package does not install a
jide-oss.jar file when built from source
Bug reassigned from package 'src:libjide-oss-java' to 'src:javahelper'.
Warning: Unknown package 'src:javahelper'
On Fri, Nov 23, 2018 at 12:04 PM Mattia Rizzolo wrote:
>
> On Fri, Nov 23, 2018 at 11:41:10AM +0100, Mathieu Malaterre wrote:
> > As you've noticed the ABI breakage occur in between two minor uploads
> > -1 and -2. So I suspect this may confuse reader that bug be reported
> > against src:gdcm,
Hi Ondrey,
newer astropy (>= 3.x) is limited to Python 3.x, and the problem appears
only with Python 2.7. The "python-astropy" package mentioned in the
Affects field of the bug is the stable (but supported) version 2.0.x,
which is (now) Python-2 only. The other packages mentioned there support
Processing commands for cont...@bugs.debian.org:
> reassign 914417 javahelper
Bug #914417 [src:javahelper] libjide-oss-java package does not install a
jide-oss.jar file when built from source
Warning: Unknown package 'src:javahelper'
Bug reassigned from package 'src:javahelper' to 'javahelper'.
Fixed
Please sponsor the upload of the updated package thawab.
Last changelog entry is:
thawab (4.1-1) unstable; urgency=medium
[ Shanavas M ]
* New upstream release
* Fix debian/patches/private-pkg.diff
[ أحمد المحمودي (Ahmed El-Mahmoudy) ]
* Change priority to optional
* Add
Processing control commands:
> reassign -1 src:gdcm 2.8.7-2
Bug #911793 [src:camitk] camitk: autopkgtest regression: Segmentation fault
Bug reassigned from package 'src:camitk' to 'src:gdcm'.
No longer marked as found in versions camitk/4.1.2-2.
Ignoring request to alter fixed versions of bug
On Fri, Nov 23, 2018 at 12:22:23PM +0100, Mathieu Malaterre wrote:
> > Also, before doing that somebody should check all the other binaries,
> > and verify they didn't change their ABI either.
>
> Which binaries ? Those build from src:gdcm ?
Yup. I didn't check libgdcm2.8, it should be checked.
Source: ruby-validate-url
Version: 1.0.2+git-1
Severity: serious
Tags: ftbfs
https://buildd.debian.org/status/fetch.php?pkg=ruby-validate-url=all=1.0.2%2Bgit-1=1542891743=0
...
┌──┐
│ Run tests for ruby2.5 from
Package: src:libjide-oss-java
Version: 3.7.4+dfsg-1
Severity: serious
Tags: sid buster
Seen at
https://bugs.launchpad.net/ubuntu/+source/starjava-ttools/+bug/1804773
verified that a rebuild in unstable doesn't include the unversioned jar symlink
either.
Processing commands for cont...@bugs.debian.org:
> close 914003 2.15.0-2
Bug #914003 [src:ruby-guard] ruby-guard FTBFS: test failure
Marked as fixed in versions ruby-guard/2.15.0-2.
Bug #914003 [src:ruby-guard] ruby-guard FTBFS: test failure
Marked Bug as done
> thanks
Stopping processing here.
> This is a diff of a .symbols file I generated from libvtkgdcm2.8
> versions 2.8.7-1 and 2.8.7-2.
Thanks Mattia for tracking this issue !
As you've noticed the ABI breakage occur in between two minor uploads
-1 and -2. So I suspect this may confuse reader that bug be reported
against src:gdcm,
As-Salaam Alaikum,
In order for thawab to get into Testing, we need to fix othman.
I believe othman's problem was that a source-only upload was done but
the package is non-free.
Please read this section and send the email. Please CC me on the email.
Hi Ole,
this looks like bug in astropy and other packages. They are just not
compatible with newer pytest.
For example astropy upstream uses pytest 3.9 and/or 3.10 for testing code,
see
https://github.com/astropy/astropy/commit/3e34e7c450ebd982978423d8774ef6953832f610
I tried to build simple
* Moritz Mühlenhoff [181123 14:09]:
> On Sat, Nov 10, 2018 at 04:34:48PM +0100, Chris Hofstaedtler wrote:
> > Hi everyone,
> >
> > thanks for reporting bugs against pdns in stretch.
> > I intend to upload a new version to stretch to fix those bugs, but I
> > cannot test all involved components
Dear Maintainer, hello Kinky Nekoboi,
just tried to reproduce this issue and there is really a crash.
In a minimal buster amd64 qemu VM,
with installed cantor and cantor-backend-sage packages.
Then follow these steps:
- start cantor
- select Sage backend
- enter in the field below the "Session
Package: gitlab-shell
Version: 8.3.3+dfsg-1
Severity: grave
Justification: renders package unusable
Doing a git push on a repository connected to gitlab, I receive this error:
BloudFire:repository maqui$ git push origin
/usr/share/gitlab-shell/bin/gitlab-shell:10:in `require_relative': cannot
Control: tags -1 upstream pending
This issue is caused by PHP 7.3, see:
https://bugs.php.net/bug.php?id=76753
I've added a patch to fix the issues in the icingaweb2 code, and a new
upload to unstable will follow shortly.
Kind Regards,
Bas
--
GPG Key ID: 4096R/6750F10AE88D4AF1
Fingerprint:
Processing control commands:
> tags -1 upstream pending
Bug #914457 [icingacli] icingacli: any command issued to icingacli rise an
exception
Added tag(s) upstream and pending.
--
914457: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=914457
Debian Bug Tracking System
Contact
Your message dated Fri, 23 Nov 2018 18:21:19 +
with message-id
and subject line Bug#914378: fixed in python-pygraphviz 1.5-1
has caused the Debian Bug report #914378,
regarding with Python 3.7: RuntimeError: generator raised StopIteration
to be marked as done.
This means that you claim that
Processing control commands:
> clone -1 -2
Bug #911793 [vtk7] Don't drop some libvtkRendering* libraries
Bug 911793 cloned as bug 914482
909120 was blocked by: 911793
909120 was not blocking any bugs.
Added blocking bug(s) of 909120: 914482
> reassign -2 src:gdcm 2.8.7-2
Bug #914482 [vtk7] Don't
Processing control commands:
> clone -1 -2
Bug #911793 [vtk7] Don't drop some libvtkRendering* libraries
Bug 911793 cloned as bug 914483
909120 was blocked by: 914482 911793
909120 was not blocking any bugs.
Added blocking bug(s) of 909120: 914483
> reassign -2 src:gdcm 2.8.7-2
Bug #914483 [vtk7]
Control: clone -1 -2
Control: reassign -2 src:gdcm 2.8.7-2
Control: retitle -2 gdcm: ABI break
Control: found -1 7.1.1+dfsg1-8
On Fri, Nov 23, 2018 at 01:44:26PM +0100, Gert Wollny wrote:
> Control: reassign -1 vtk7
> Control: retitle -1 Don't drop some libvtkRendering* libraries
>
> I don't
Am Freitag, den 23.11.2018, 20:14 +0100 schrieb Mattia Rizzolo:
> Hi,
>
> so, if you don't particularly mind, I'm happy to just take the least
> and fix all the involved packages here, so src:vtk7
I just uploaded vtk7, I knew where to look because I did the changes
that made the libraries go
I use linphone on stretch as my one and only telephone.
So far, I did not encounter this problem.
I suggest to downgrade this issue to "important",
because it seems to affect only few users.
Your message dated Fri, 23 Nov 2018 21:32:54 +
with message-id
and subject line Bug#908682: fixed in qemu 1:2.8+dfsg-6+deb9u5
has caused the Debian Bug report #908682,
regarding qemu: (CVE-2018-3639 SSB) qemu should be able to pass the ssbd cpu
flag
to be marked as done.
This means that you
Your message dated Fri, 23 Nov 2018 21:32:28 +
with message-id
and subject line Bug#911175: fixed in ghostscript 9.25~dfsg-0+deb9u1
has caused the Debian Bug report #911175,
regarding ghostscript: CVE-2018-18284: 1Policy operator gives access to
.forceput
to be marked as done.
This means
Package: libfclib0
Version: 3.0.0+dfsg-1
Severity: serious
Control: block 913837 by -1
Dear maintainer,
your source package has this:
Package: libfclib0
Architecture: any
Multi-Arch: same
Section: libs
Depends: ${misc:Depends},
${shlibs:Depends},
libhdf5-100,
Your message dated Fri, 23 Nov 2018 21:32:27 +
with message-id
and subject line Bug#909076: fixed in ghostscript 9.25~dfsg-0+deb9u1
has caused the Debian Bug report #909076,
regarding ghostscript: ps2ascii crashes: Error: /typecheck in --.bind--
to be marked as done.
This means that you
Your message dated Fri, 23 Nov 2018 21:32:54 +
with message-id
and subject line Bug#911469: fixed in qemu 1:2.8+dfsg-6+deb9u5
has caused the Debian Bug report #911469,
regarding qemu: CVE-2018-17963: net: ignore packets with large size
to be marked as done.
This means that you claim that the
Your message dated Fri, 23 Nov 2018 21:32:54 +
with message-id
and subject line Bug#911468: fixed in qemu 1:2.8+dfsg-6+deb9u5
has caused the Debian Bug report #911468,
regarding qemu: CVE-2018-17962: pcnet: integer overflow leads to buffer overflow
to be marked as done.
This means that you
Processing commands for cont...@bugs.debian.org:
> block 914450 by 914448
Bug #914450 [ftp.debian.org] RM: lucene2 -- ROM; Obsolete, no longer used
914450 was not blocked by any bugs.
914450 was not blocking any bugs.
Added blocking bug(s) of 914450: 914448
> block 914452 by 914448
Bug #914452
Hi,
so, if you don't particularly mind, I'm happy to just take the least and
fix all the involved packages here, so src:vtk7 and src:gdcm (and
rebuilding fw4spl). At the very least, I'm going to rename
libvtkgdcm2.8 to something else; thinking about libvtkgdcm2.8a
(libvtk7gdcm2.8 would be
Your message dated Fri, 23 Nov 2018 21:39:29 +
with message-id
and subject line Bug#911265: fixed in mosquitto 1.5.4-1
has caused the Debian Bug report #911265,
regarding mosquitto: CVE-2017-7654
to be marked as done.
This means that you claim that the problem has been dealt with.
If this is
Your message dated Fri, 23 Nov 2018 21:39:29 +
with message-id
and subject line Bug#911266: fixed in mosquitto 1.5.4-1
has caused the Debian Bug report #911266,
regarding mosquitto: CVE-2017-7653
to be marked as done.
This means that you claim that the problem has been dealt with.
If this is
Your message dated Fri, 23 Nov 2018 18:05:44 +
with message-id
and subject line Bug#914457: fixed in icingaweb2 2.6.2-2
has caused the Debian Bug report #914457,
regarding icingacli: any command issued to icingacli rise an exception
to be marked as done.
This means that you claim that the
Control: tag -1 pending
Hello,
Bug #914378 in python-pygraphviz 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:
Processing control commands:
> tag -1 pending
Bug #914378 [src:python-pygraphviz] with Python 3.7: RuntimeError: generator
raised StopIteration
Added tag(s) pending.
--
914378: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=914378
Debian Bug Tracking System
Contact ow...@bugs.debian.org
Control: tag -1 pending
Hello,
Bug #914420 in pytest 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:
Processing control commands:
> tag -1 pending
Bug #914420 [python-pytest] python-pytest: Breaks many Python 2 test suites
Added tag(s) pending.
--
914420: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=914420
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
Processing control commands:
> tag -1 pending
Bug #881565 [python3-acoustid] python-acoustid: incompatible with python3 (fix
availble upstream)
Bug #881566 [python3-acoustid] python-acoustid: incompatible/broken on Python 3
(fix available upstream)
Added tag(s) pending.
Added tag(s) pending.
Control: tag -1 pending
Hello,
Bug #881565 in pyacoustid 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:
Processing commands for cont...@bugs.debian.org:
> tags 913014 + patch
Bug #913014 [e3] e3 (all binaries): immediate segmentation fault
Added tag(s) patch.
> quit
Stopping processing here.
Please contact me if you need assistance.
--
913014:
Your message dated Fri, 23 Nov 2018 17:50:34 +
with message-id
and subject line Bug#914356: fixed in dlt-daemon 2.17.0-2
has caused the Debian Bug report #914356,
regarding dlt-daemon: FTBFS (ld: cannot find -lpthreads)
to be marked as done.
This means that you claim that the problem has
Hello,
Am Freitag, den 23.11.2018, 16:30 +0100 schrieb Emmanuel Promayon:
> Dear all
>
> Thank to Paul for your answers about the autoremoval and explanation
> about the ABI problem. It seems that Adrian Bunk's triage message in
> 909120 (added blocking bug(s) of 909120: 911793) did push the
Package: chromium
Version: 70.0.3538.67-2
Severity: serious
Justification: Policy 2.1
Chromium contains nonfree code from unrar, located at third_party/unrar.
Your message dated Fri, 23 Nov 2018 21:05:14 +
with message-id
and subject line Bug#914347: fixed in vtk7 7.1.1+dfsg1-10
has caused the Debian Bug report #914347,
regarding vtk7: FTBFS against python 3.7.1 (now the default for python3)
to be marked as done.
This means that you claim that the
Your message dated Fri, 23 Nov 2018 21:05:14 +
with message-id
and subject line Bug#911793: fixed in vtk7 7.1.1+dfsg1-10
has caused the Debian Bug report #911793,
regarding Don't drop some libvtkRendering* libraries
to be marked as done.
This means that you claim that the problem has been
Your message dated Fri, 23 Nov 2018 23:58:02 +
with message-id
and subject line Bug#881565: fixed in pyacoustid 1.1.5-1
has caused the Debian Bug report #881565,
regarding python-acoustid: incompatible with python3 (fix availble upstream)
to be marked as done.
This means that you claim that
Your message dated Fri, 23 Nov 2018 23:58:02 +
with message-id
and subject line Bug#881565: fixed in pyacoustid 1.1.5-1
has caused the Debian Bug report #881565,
regarding python-acoustid: incompatible/broken on Python 3 (fix available
upstream)
to be marked as done.
This means that you
Your message dated Fri, 23 Nov 2018 19:23:50 +
with message-id
and subject line Bug#914420: fixed in pytest 3.10.1-1
has caused the Debian Bug report #914420,
regarding python-pytest: Breaks many Python 2 test suites
to be marked as done.
This means that you claim that the problem has been
Processing control commands:
> block 913837 by -1
Bug #913837 [release.debian.org] transition: hdf5
913837 was not blocked by any bugs.
913837 was not blocking any bugs.
Added blocking bug(s) of 913837: 914493
--
913837: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=913837
914493:
Your message dated Fri, 23 Nov 2018 21:32:54 +
with message-id
and subject line Bug#910431: fixed in qemu 1:2.8+dfsg-6+deb9u5
has caused the Debian Bug report #910431,
regarding qemu: CVE-2018-10839: integer overflow leads to buffer overflow issue
to be marked as done.
This means that you
Your message dated Fri, 23 Nov 2018 21:33:35 +
with message-id
and subject line Bug#914262: fixed in xkeycaps 2.47-4.1+deb9u1
has caused the Debian Bug report #914262,
regarding Segfaults on "Write Output" if more than 8 keysyms per key are present
to be marked as done.
This means that you
Your message dated Fri, 23 Nov 2018 22:10:46 +
with message-id
and subject line Bug#899796: fixed in input-pad 1.0.3-2
has caused the Debian Bug report #899796,
regarding input-pad: Invalid maintainer address
pkg-ime-de...@lists.alioth.debian.org
to be marked as done.
This means that you
Hello Bastian,
Am 20.11.18 um 17:44 schrieb Bastian Neuburger:
> Hi,
>
>> I have however not yet tested what happens if you start thunderbird
>> aftter the upgrade and close it right away (i.e. not trying to sign
>> anything but also not entering the master password). I will try to test
>>
Your message dated Fri, 23 Nov 2018 19:50:49 +
with message-id
and subject line Bug#910348: fixed in linux 4.18.20-2
has caused the Debian Bug report #910348,
regarding linux-headers-4.19.0-rc6-amd64: File scripts/subarch.include is
missing
to be marked as done.
This means that you claim
Your message dated Fri, 23 Nov 2018 19:50:49 +
with message-id
and subject line Bug#910348: fixed in linux 4.18.20-2
has caused the Debian Bug report #910348,
regarding linux-headers-4.18.0-3-common: missing file referred in Makefile
to be marked as done.
This means that you claim that the
Package: src:linux
Version: 4.18.20-1
Severity: critical
Justification: breaks the whole system
Dear Maintainers,
linux-image-4.18.0-3-amd64 does not boot on this computer.
After grub shortly cursor is blinking upper left (when usually the initrd is
deflating and systemd starts).
After that
Your message dated Fri, 23 Nov 2018 21:38:22 +
with message-id
and subject line Bug#874962: fixed in knights 18.11.80-1
has caused the Debian Bug report #874962,
regarding [knights] Future Qt4 removal from Buster
to be marked as done.
This means that you claim that the problem has been dealt
Your message dated Sat, 24 Nov 2018 03:49:31 +
with message-id
and subject line Bug#908555: fixed in pydicom 1.2.1-1
has caused the Debian Bug report #908555,
regarding pydicom build depends on the removed python-gdcm
to be marked as done.
This means that you claim that the problem has been
93 matches
Mail list logo
