Your message dated Sat, 21 Mar 2020 05:55:41 +
with message-id
and subject line Bug#954377: Removed package(s) from unstable
has caused the Debian Bug report #938582,
regarding sugar-base: Python2 removal in sid/bullseye
to be marked as done.
This means that you claim that the problem has
Your message dated Sat, 21 Mar 2020 05:55:41 +
with message-id
and subject line Bug#954377: Removed package(s) from unstable
has caused the Debian Bug report #885527,
regarding sugar-base: Build-Depends on unmaintained pygtk
to be marked as done.
This means that you claim that the problem
Your message dated Sat, 21 Mar 2020 05:53:40 +
with message-id
and subject line Bug#954359: Removed package(s) from unstable
has caused the Debian Bug report #929575,
regarding simpleid: Not compatible with PHP 7
to be marked as done.
This means that you claim that the problem has been dealt
Your message dated Sat, 21 Mar 2020 05:47:43 +
with message-id
and subject line Bug#953828: Removed package(s) from unstable
has caused the Debian Bug report #937132,
regarding nevow: Python2 removal in sid/bullseye
to be marked as done.
This means that you claim that the problem has been
Your message dated Sat, 21 Mar 2020 05:47:05 +
with message-id
and subject line Bug#953820: Removed package(s) from unstable
has caused the Debian Bug report #936544,
regarding foolscap: Python2 removal in sid/bullseye
to be marked as done.
This means that you claim that the problem has been
Your message dated Sat, 21 Mar 2020 05:46:20 +
with message-id
and subject line Bug#953807: Removed package(s) from unstable
has caused the Debian Bug report #938660,
regarding tftpy: Python2 removal in sid/bullseye
to be marked as done.
This means that you claim that the problem has been
Your message dated Sat, 21 Mar 2020 05:47:35 +
with message-id
and subject line Bug#953828: Removed package(s) from unstable
has caused the Debian Bug report #953828,
regarding RM: nevow -- RoQA; python2-only; no python3 port available; no rdeps;
popcon rapidly dropping
to be marked as done.
Your message dated Sat, 21 Mar 2020 05:47:00 +
with message-id
and subject line Bug#953820: Removed package(s) from unstable
has caused the Debian Bug report #953820,
regarding RM: foolscap -- RoQA; python2-only; no python3 port available yet;
leaf package (considering testing, in unstable
Your message dated Sat, 21 Mar 2020 05:46:12 +
with message-id
and subject line Bug#953807: Removed package(s) from unstable
has caused the Debian Bug report #953807,
regarding RM: tftpy -- RoQA; python2-only; python3 version is non-free; no
rdeps; low popcon
to be marked as done.
This
Your message dated Sat, 21 Mar 2020 05:48:24 +
with message-id
and subject line Bug#953850: Removed package(s) from unstable
has caused the Debian Bug report #953850,
regarding RM: tinywm -- RoQA; python2-only; last upstream releas ein 2005, last
upload 2012; leaf package; last rdep of
Dear all,
I was able to side-step this one a bit as I was able to download all
the experimental versions of pytside2 binaries except
python3-pyside2uic which is still at 5.13.2-2.2 and hence unable to
install freecad.
$ sudo aptitude install freecad-python3
The following NEW packages will be
This patch appears to at least allow mcron to build against guile-3.0-dev.
diff --git a/configure.ac b/configure.ac
index 764ea03..881d8d3 100644
--- a/configure.ac
+++ b/configure.ac
@@ -48,7 +48,7 @@ AC_PROG_AWK
AC_PROG_EGREP
AM_PROG_CC_C_O
-PKG_CHECK_MODULES(GUILE, guile-2.0)
> python-fixture (the binary) is gone, therefore we have #952130 and
> #952127. I've been reluctant to remove Py2 support from these, because
> unittest2 needs it, and this would break a lot of packages (including,
> indirectly, stuff like sphinx, pytest, etc.).
you can remove them when
Hi,
python-fixture (the binary) is gone, therefore we have #952130 and
#952127. I've been reluctant to remove Py2 support from these, because
unittest2 needs it, and this would break a lot of packages (including,
indirectly, stuff like sphinx, pytest, etc.).
What is it that the team suggests at
On 2/29/20 8:58 AM, Nikolai Lusan wrote:
Hi Nikolai,
> Sorry I haven't gotten back to you yet. I have a number of projects
> on the go, and since this is only impacting a small number of users
> on my home system it has fallen lower on my priority list - I was
> also trying to find solutions
On 2020-03-20 23:41:59, Moritz Mühlenhoff wrote:
> On Sat, Nov 09, 2019 at 06:11:46PM -0500, Antoine Beaupré wrote:
>> There was a 3 year old "python 3" branch sitting around in the repo that
>> I revived by merging in the latest code.
>>
>> Tests still fail (the test suite hangs on py2 and fails
On Sat, Nov 09, 2019 at 06:11:46PM -0500, Antoine Beaupré wrote:
> There was a 3 year old "python 3" branch sitting around in the repo that
> I revived by merging in the latest code.
>
> Tests still fail (the test suite hangs on py2 and fails on py3), but at
> least there's some work done. A
Your message dated Fri, 20 Mar 2020 22:36:22 +
with message-id
and subject line Bug#950210: fixed in python-opcua 0.98.9-1
has caused the Debian Bug report #950210,
regarding autopkg test failure with python3.8
to be marked as done.
This means that you claim that the problem has been dealt
Your message dated Fri, 20 Mar 2020 22:25:27 +
with message-id
and subject line Bug#925857: fixed in wireless-tools 30~pre9-13.1
has caused the Debian Bug report #925857,
regarding wireless-tools: ftbfs with GCC-9
to be marked as done.
This means that you claim that the problem has been
Your message dated Fri, 20 Mar 2020 22:21:32 +
with message-id
and subject line Bug#954297: Removed package(s) from unstable
has caused the Debian Bug report #954238,
regarding libperlspeak-perl: CVE-2020-10674
to be marked as done.
This means that you claim that the problem has been dealt
Your message dated Fri, 20 Mar 2020 22:22:15 +
with message-id
and subject line Bug#902323: Removed package(s) from unstable
has caused the Debian Bug report #938003,
regarding python-pathlib: Python2 removal in sid/bullseye
to be marked as done.
This means that you claim that the problem
Processing commands for cont...@bugs.debian.org:
> tags 954276 + upstream
Bug #954276 [cloud-init] cloud-init - RuntimeError: dictionary keys changed
during iteration
Added tag(s) upstream.
> forwarded 954276 https://bugs.launchpad.net/cloud-init/+bug/1868327
Bug #954276 [cloud-init] cloud-init
Processing commands for cont...@bugs.debian.org:
> tags 954371 + upstream
Bug #954371 [libio-socket-ssl-perl] libio-socket-ssl-perl: FTBFS since openssl
1.1.1e
Added tag(s) upstream.
> thanks
Stopping processing here.
Please contact me if you need assistance.
--
954371:
Processing commands for cont...@bugs.debian.org:
> forwarded 954371 https://github.com/noxxi/p5-io-socket-ssl/issues/93
Bug #954371 [libio-socket-ssl-perl] libio-socket-ssl-perl: FTBFS since openssl
1.1.1e
Set Bug forwarded-to-address to
'https://github.com/noxxi/p5-io-socket-ssl/issues/93'.
>
Source: golang-github-buger-jsonparser
Version: 0.0~git20170705.0.9addec9-2
Severity: grave
Tags: security upstream
Forwarded: https://github.com/buger/jsonparser/issues/188
Hi,
The following vulnerability was published for
golang-github-buger-jsonparser. The severity might be indeed
overrated,
Processing commands for cont...@bugs.debian.org:
> affects 937166 - python-appdirs
Bug #937166 [src:nuitka] nuitka: Python2 removal in sid/bullseye
Removed indication that 937166 affects
> thanks
Stopping processing here.
Please contact me if you need assistance.
--
937166:
On Sat, 22 Feb 2020 10:54:23 +0100 Kay Hayen wrote:
> Hello,
>
> this is not explained in the FAQ, but the way I have done it is like this
> (in build-depends, removed irrelevant parts):
>
>python (>= 2.6.6-2) | base-files (>= 11),
>python-all-dbg (>= 2.6.6-2) |
Package: libio-socket-ssl-perl
Version: 2.067-1
Severity: serious
The package FTBFS since openssl has been updated to 1.1.1e because the
testsuite fails. The failure is due to commit db943f43a60d ("Detect EOF
while reading in libssl") [0] in openssl. There an issue ticket [1]
which introduced the
Processing commands for cont...@bugs.debian.org:
> severity 953032 critical
Bug #953032 [x11-xkb-utils] xkbcomp: Internal error: Could not resolve keysym
XF86FullScreen
Severity set to 'critical' from 'normal'
> thanks
Stopping processing here.
Please contact me if you need assistance.
--
Hi,
it looks like this [1] is the corresponding commit to fix this
vulnerability.
regards,
Philip
[1]
https://github.com/horde/Data/commit/78ad0c2390176cdde7260a271bc6ddd86f4c9c0e
Processing control commands:
> fixed -1 1.3.5-1
Bug #954369 [src:pajeng] src:pajeng: fails to migrate to testing for too long
Marked as fixed in versions pajeng/1.3.5-1.
--
954369: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=954369
Debian Bug Tracking System
Contact ow...@bugs.debian.org
Source: pajeng
Version: 1.3.4-3
Severity: serious
Control: fixed -1 1.3.5-1
Tags: sid bullseye
User: release.debian@packages.debian.org
Usertags: out-of-sync
Dear maintainer(s),
As recently announced [1], the Release Team now considers packages that
are out-of-sync between testing and
Processing control commands:
> fixed -1 17.1-2
Bug #954368 [src:haskell-mode] src:haskell-mode: fails to migrate to testing
for too long
Marked as fixed in versions haskell-mode/17.1-2.
--
954368: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=954368
Debian Bug Tracking System
Contact
Source: openvswitch
Version: 2.11.0+2019.06.25+git.9ebe795035+ds1-7
Severity: serious
Control: fixed -1 2.11.0+2019.06.25+git.9ebe795035+ds1-8
Tags: sid bullseye
User: release.debian@packages.debian.org
Usertags: out-of-sync
Dear maintainer(s),
As recently announced [1], the Release Team now
Source: haskell-mode
Version: 16.1-8
Severity: serious
Control: fixed -1 17.1-2
Tags: sid bullseye
User: release.debian@packages.debian.org
Usertags: out-of-sync
Dear maintainer(s),
As recently announced [1], the Release Team now considers packages that
are out-of-sync between testing and
Processing control commands:
> fixed -1 2.11.0+2019.06.25+git.9ebe795035+ds1-8
Bug #954367 [src:openvswitch] src:openvswitch: fails to migrate to testing for
too long
Marked as fixed in versions openvswitch/2.11.0+2019.06.25+git.9ebe795035+ds1-8.
--
954367:
Hi Scott,
On Fri, Mar 20, 2020 at 01:57:25PM -0400, Scott Kitterman wrote:
> On Thursday, March 19, 2020 6:24:22 PM EDT Salvatore Bonaccorso wrote:
> > Hi Scott,
> >
> > On Thu, Mar 19, 2020 at 12:20:25AM -0400, Scott Kitterman wrote:
> > > Upstream's 3.1.2 release had just the security fix in
Package: cramfsswap
Version: 1.4.1-1.1
Severity: normal
Tags: patch
Dear maintainer,
I've prepared an NMU for cramfsswap (versioned as 1.4.1-1.2) and
uploaded it to DELAYED/XX. Please feel free to tell me if I
should delay it longer.
Regards.
Håvard
diff -Nru cramfsswap-1.4.1/debian/changelog
Processing control commands:
> tags -1 patch
Bug #944365 [src:frama-c] FTBFS with OCaml 4.08.1 (implementation/interface
mismatch)
Added tag(s) patch.
--
944365: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=944365
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
On Thursday, March 19, 2020 6:24:22 PM EDT Salvatore Bonaccorso wrote:
> Hi Scott,
>
> On Thu, Mar 19, 2020 at 12:20:25AM -0400, Scott Kitterman wrote:
> > Upstream's 3.1.2 release had just the security fix in it. I propose
> > updating buster with it (I put 3.1.3 in unstable, but it had
A work around for now is to install by hand
apt install python3-scipy
reassign -1 silx
thanks
Package: pymca
Version: 5.4.3+dfsg-1
Severity: grave
Justification: renders package unusable
Dear Maintainer,
I installed "pymca" on a debian 10 system, this draggs the dependencies:
* python3-pymca5
* python3-silx
The package python3-silx apparently requires python3-scipy, the graphical user
Processing control commands:
> severity -1 important
Bug #954336 [pkg-js-tools] pkg-js-tools: Please adjust Severity values in tag
declarations
Severity set to 'important' from 'grave'
--
954336: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=954336
Debian Bug Tracking System
Contact
Control: severity -1 important
Lowering severity since lintian part is not the main part of pkg-js-tools
Processing control commands:
> tag -1 pending
Bug #954336 [pkg-js-tools] pkg-js-tools: Please adjust Severity values in tag
declarations
Added tag(s) pending.
--
954336: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=954336
Debian Bug Tracking System
Contact ow...@bugs.debian.org with
Control: tag -1 pending
Hello,
Bug #954336 in pkg-js-tools 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:
Once kotlin is in Debian, then we can use newer upstream versions, which
support the latest JDK.
Your message dated Fri, 20 Mar 2020 16:53:08 +
with message-id
and subject line Bug#954153: fixed in python-virtualenv 20.0.10-1
has caused the Debian Bug report #954153,
regarding src:python-virtualenv: Please drop python-virtualenv tests
to be marked as done.
This means that you claim that
Your message dated Fri, 20 Mar 2020 16:34:34 +
with message-id
and subject line Bug#953177: fixed in aspell-pa 0.01-1-6.1
has caused the Debian Bug report #953177,
regarding src:aspell-pa: fails to migrate to testing for too long
to be marked as done.
This means that you claim that the
Hey Holger!
On Fri, Mar 20, 2020 at 01:35:24PM +0100, Holger Wansing wrote:
>Steve McIntyre wrote:
>>
>> Hmmm. Can you try wiping the partition table in between tests?
>
>I already tried that on wednesday, with no success.
>
>However, today it does the trick! Success!
>Curious, but installation
Your message dated Fri, 20 Mar 2020 16:06:43 +
with message-id
and subject line Bug#954323: fixed in libreoffice 1:6.4.2-2
has caused the Debian Bug report #954323,
regarding libreoffice-common 6.4.2 breaks older versions
to be marked as done.
This means that you claim that the problem has
Processing commands for cont...@bugs.debian.org:
> reassign 952975 ibus-gtk3
Bug #952975 [debian-i18n] Subject: debian-i18n: gtk-3 in bullseye does not seem
to support XIM input.
Bug reassigned from package 'debian-i18n' to 'ibus-gtk3'.
Ignoring request to alter found versions of bug #952975 to
Your message dated Fri, 20 Mar 2020 15:34:22 +
with message-id
and subject line Bug#953174: fixed in aspell-mr 0.10-10.1
has caused the Debian Bug report #953174,
regarding src:aspell-mr: fails to migrate to testing for too long
to be marked as done.
This means that you claim that the
Processing commands for cont...@bugs.debian.org:
> close 953344
Bug #953344 [src:colord] src:colord: fails to migrate to testing for too long
Marked Bug as done
> thanks
Stopping processing here.
Please contact me if you need assistance.
--
953344:
Processing commands for cont...@bugs.debian.org:
> severity 942910 serious
Bug #942910 [src:automake-1.15] automake-1.15: Python2 removal in sid/bullseye
Severity set to 'serious' from 'important'
> thanks
Stopping processing here.
Please contact me if you need assistance.
--
942910:
Processing commands for cont...@bugs.debian.org:
> severity 942928 serious
Bug #942928 [src:automake-1.16] automake-1.16: Python2 removal in sid/bullseye
Severity set to 'serious' from 'important'
> thanks
Stopping processing here.
Please contact me if you need assistance.
--
942928:
Your message dated Fri, 20 Mar 2020 15:06:37 +
with message-id
and subject line Bug#954331: fixed in pkg-perl-tools 0.59
has caused the Debian Bug report #954331,
regarding pkg-perl-tools: Please adjust Severity values in tag declarations
to be marked as done.
This means that you claim that
Control: tag -1 pending
Hello,
Bug #954323 in libreoffice 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 #954323 [libreoffice-common] libreoffice-common 6.4.2 breaks older versions
Added tag(s) pending.
--
954323: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=954323
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
Your message dated Fri, 20 Mar 2020 15:06:04 +
with message-id
and subject line Bug#953550: fixed in mailutils 1:3.7-2.1
has caused the Debian Bug report #953550,
regarding mailutils: FTBFS with Python 3.8: undefined reference
to be marked as done.
This means that you claim that the problem
Your message dated Fri, 20 Mar 2020 14:44:08 +
with message-id
and subject line Bug#951899: fixed in ldns 1.7.0-4.1
has caused the Debian Bug report #951899,
regarding ldns FTBFS with swig 4.0.1
to be marked as done.
This means that you claim that the problem has been dealt with.
If this is
Control: tag -1 pending
Hello,
Bug #954331 in pkg-perl-tools 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 #954331 [pkg-perl-tools] pkg-perl-tools: Please adjust Severity values in
tag declarations
Added tag(s) pending.
--
954331: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=954331
Debian Bug Tracking System
Contact ow...@bugs.debian.org with
Processing commands for cont...@bugs.debian.org:
> reassign 953850 ftp.debian.org
Bug #953850 [tinywm] tinywm: should this package be removed?
Bug reassigned from package 'tinywm' to 'ftp.debian.org'.
No longer marked as found in versions tinywm/1.3-9.
Ignoring request to alter fixed versions of
Processing commands for cont...@bugs.debian.org:
> reassign 954336 pkg-js-tools
Bug #954336 [pkg-perl-tools] pkg-js-tools: Please adjust Severity values in tag
declarations
Bug reassigned from package 'pkg-perl-tools' to 'pkg-js-tools'.
Ignoring request to alter found versions of bug #954336 to
Hello,
I'm attaching an updated cpu-load patch, based on 0.69-1; it enables
nodelay() for the duration of keyboardsetup() only – keyboard setup
still takes 100% CPU but at least it works, and normal view behaves as
with the current patch.
Regards,
nabijaczleweli
Description:
TODO: Put a short
Processing commands for cont...@bugs.debian.org:
> block 949187 with 951901
Bug #949187 [release.debian.org] transition: python3.8
949187 was blocked by: 952217 953940 950210 953969 950221 950847 953549 953550
948416 950842 951944 950147 953966 950858 953968 953970 953316 950861 953016
951899
Processing commands for cont...@bugs.debian.org:
> retitle 954331 pkg-perl-tools: Please adjust Severity values in tag
> declarations
Bug #954331 [pkg-perl-tools] lintian: coercion for "original_severity" failed:
Unknown tag severity minor
Changed Bug title to 'pkg-perl-tools: Please adjust
Processing commands for cont...@bugs.debian.org:
> clone 954331 -1
Bug #954331 [pkg-perl-tools] lintian: coercion for "original_severity" failed:
Unknown tag severity minor
Bug 954331 cloned as bug 954336
> reassign -1 pkg-perl-tools
Bug #954336 [pkg-perl-tools] lintian: coercion for
Hi,
Steve McIntyre wrote:
> On Thu, Mar 19, 2020 at 12:42:48PM +0100, Holger Wansing wrote:
> >Hi,
> >
> >Steve McIntyre wrote:
> >> On Thu, Mar 19, 2020 at 09:26:25AM +0100, Holger Wansing wrote:
> >> >Hi,
> >> >
> >> >Steve McIntyre wrote:
> >> >> One silly question: what media are you using
Control: reassign -1 pkg-perl-tools
Hi,
> Jonas Smedegaard wrote:
>
> Upgrading to version 2.58.0 of lintian renders it totally unusable:
That is not correct. Lintian just fails to work with pkg-perl-tools.
> Lintian::Tag::Info::original_severity(Lintian::Tag::Info=HASH(0x565295307a18),
>
Processing control commands:
> reassign -1 pkg-perl-tools
Bug #954331 [lintian] lintian: coercion for "original_severity" failed: Unknown
tag severity minor
Bug reassigned from package 'lintian' to 'pkg-perl-tools'.
No longer marked as found in versions lintian/2.58.0.
Ignoring request to alter
Package: lintian
Version: 2.58.0
Severity: grave
Justification: renders package unusable
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA512
Upgrading to version 2.58.0 of lintian renders it totally unusable:
$ lintian *_amd64.changes --no-tag-display-limit
coercion for "original_severity" failed:
Processing commands for cont...@bugs.debian.org:
> forcemerge 951843 951706
Bug #951843 [src:gdspy] explicit build dependency on python3.7
Bug #951706 [src:gdspy] gdspy hard-codes python3.7, without depending on it
Added tag(s) patch.
Merged 951706 951843
> retitle 951706 gdspy build depends on
Processing commands for cont...@bugs.debian.org:
> tags 954291 + pending
Bug #954291 [libvirt-daemon-system-sysv] libvirt-daemon-system-sysv: upgrading
kills VMs
Added tag(s) pending.
> thanks
Stopping processing here.
Please contact me if you need assistance.
--
954291:
Your message dated Fri, 20 Mar 2020 11:00:11 +
with message-id
and subject line Bug#951829: fixed in openvdb 7.0.0-1
has caused the Debian Bug report #951829,
regarding replace python3-all-dev with python3.7-dev
to be marked as done.
This means that you claim that the problem has been dealt
Your message dated Fri, 20 Mar 2020 11:00:12 +
with message-id
and subject line Bug#938306: fixed in pyxid 1.0-3
has caused the Debian Bug report #938306,
regarding pyxid: Python2 removal in sid/bullseye
to be marked as done.
This means that you claim that the problem has been dealt with.
If
Your message dated Fri, 20 Mar 2020 11:00:12 +
with message-id
and subject line Bug#937491: fixed in pynn 0.9.5-1
has caused the Debian Bug report #937491,
regarding pynn: Python2 removal in sid/bullseye
to be marked as done.
This means that you claim that the problem has been dealt with.
If
Processing commands for cont...@bugs.debian.org:
> forwarded 950840 https://github.com/lxc/lxc-templates/issues/28
Bug #950840 [lxc-templates] English India selected during installation breaks
locale in lxc
Set Bug forwarded-to-address to
'https://github.com/lxc/lxc-templates/issues/28'.
>
Processing commands for cont...@bugs.debian.org:
> tags 950840 + upstream
Bug #950840 [lxc-templates] English India selected during installation breaks
locale in lxc
Added tag(s) upstream.
> thanks
Stopping processing here.
Please contact me if you need assistance.
--
950840:
Processing control commands:
> reopen -1
Bug #936667 {Done: Laszlo Boszormenyi (GCS) } [src:grpc] grpc:
Python2 removal in sid/bullseye
'reopen' may be inappropriate when a bug has been closed with a version;
all fixed versions will be cleared, and you may need to re-add them.
Bug reopened
No
Control: reopen -1
On Fri, 20 Mar 2020 11:31:17 +0300 Dmitry Shachnev wrote:
> Control: severity -1 serious
>
> On Fri, Mar 13, 2020 at 09:24:45PM -0400, Sandro Tosi wrote:
> > Hey Laszlo,
> >
> > > Format: 1.8
> > > Date: Wed, 23 Oct 2019 05:45:37 +
> > > Source: grpc
> > > Binary:
Processing commands for cont...@bugs.debian.org:
> severity 954323 serious
Bug #954323 [libreoffice-common] libreoffice-common: Update to 1:6.4.2-1
renders libreoffice-writer unusable
Severity set to 'serious' from 'grave'
> retitle 954323 libreoffice-common 6.4.2 breaks older versions
Bug
severity 954323 serious
retitle 954323 libreoffice-common 6.4.2 breaks older versions
found 954323 1:6.4.2~rc1-1
thanks
Am 20. März 2020 09:17:51 MEZ schrieb Ara Keary :
>Package: libreoffice-common
>Version: 1:6.4.2-1
>Severity: grave
>Justification: renders package unusable
Sigh.
>. or the
On 20.3.2020 10.18, Stefan Fritsch wrote:
> Package: libgl1-mesa-dri
> Version: 20.0.2-1
> Followup-For: Bug #954311
>
>
> With this mesa version, there are severe drawing artifacts with the kde
> konsole terminal emulator that makes it unusable. I also see problems
> when marking text in
Processing commands for cont...@bugs.debian.org:
> severity 954311 grave
Bug #954311 [libglx-mesa0] libglx-mesa0: Rare problems of drawn stripes.
Severity set to 'grave' from 'important'
> thanks
Stopping processing here.
Please contact me if you need assistance.
--
954311:
Processing commands for cont...@bugs.debian.org:
> retitle 954311 libglx-mesa0: Drawing artifacts make some programs unusable
Bug #954311 [libglx-mesa0] libglx-mesa0: Rare problems of drawn stripes.
Changed Bug title to 'libglx-mesa0: Drawing artifacts make some programs
unusable' from
Your message dated Fri, 20 Mar 2020 08:37:55 +
with message-id
and subject line Bug#950381: fixed in apertium-eu-en 0.3.1~r56205-3
has caused the Debian Bug report #950381,
regarding apertium-eu-en FTBFS with apertium 3.6.1
to be marked as done.
This means that you claim that the problem has
Hi,
On Thu, Mar 19, 2020 at 08:18:04PM +0100, Thorsten Glaser wrote:
> Package: libvirt-daemon-system-sysv
> Version: 6.0.0-3
> Severity: critical
> Justification: causes serious data loss
>
> Just a regular dist-upgrade doing this:
>
>
> Unpacking libvirt-daemon-system-sysv (6.0.0-3) over
Processing control commands:
> severity -1 serious
Bug #936667 {Done: Laszlo Boszormenyi (GCS) } [src:grpc] grpc:
Python2 removal in sid/bullseye
Severity set to 'serious' from 'normal'
--
936667: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=936667
Debian Bug Tracking System
Contact
Package: libreoffice-common
Version: 1:6.4.2-1
Severity: grave
Justification: renders package unusable
Dear maintainers,
updating libreoffice-common to 1:6.4.2-1 renders libreoffice-writer unusable:
when opening an existing file
. either the document is declared as to be restored, but
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA256
On Thu, 2020-03-19 at 18:39 +0100, Andreas Henriksson wrote:
> There doesn't seem to have been any movement since your comment on the
> upstream bug report. The xfce4-notes-plugin is now the only remaining
> package in unstable that still depends on
Your message dated Fri, 20 Mar 2020 07:34:26 +
with message-id
and subject line Bug#950153: fixed in apertium-es-ro 0.7.3~r57551-4
has caused the Debian Bug report #950153,
regarding apertium-es-ro FTBFS with apertium 3.6.1
to be marked as done.
This means that you claim that the problem has
Your message dated Fri, 20 Mar 2020 06:34:53 +
with message-id
and subject line Bug#950379: fixed in apertium-es-ast 1.1.0~r51165-3
has caused the Debian Bug report #950379,
regarding apertium-es-ast FTBFS with apertium 3.6.1
to be marked as done.
This means that you claim that the problem
94 matches
Mail list logo
