Processing control commands:
> severity 933684 serious
Bug #933684 [src:python-httptools] python-httptools: Please adjust for
http-parser 2.9
Severity set to 'serious' from 'important'
--
933684: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=933684
Debian Bug Tracking System
Contact ow...@b
Your message dated Mon, 05 Aug 2019 05:49:29 +
with message-id
and subject line Bug#933163: fixed in cyrus-imapd 3.0.11-1
has caused the Debian Bug report #933163,
regarding cyrus-imapd: Data loss possible when upgrading to buster
to be marked as done.
This means that you claim that the probl
Your message dated Mon, 05 Aug 2019 05:49:35 +
with message-id
and subject line Bug#933282: fixed in cysignals 1.8.1+ds-3
has caused the Debian Bug report #933282,
regarding BD on texlive-generic-extra which isn't build anymore and isn't in
bullseye
to be marked as done.
This means that you
Package: src:valinor
Version: 1.1.0-1
Severity: grave
Justification: renders package unusable
FAIL: testARMNoneEABIGDB (test.test_outputdir.TestCLIOutputDirectory)
--
Traceback (most recent call last):
File
"/tmp/autopkgtest-lx
Package: src:salt
Version: 2018.3.4+dfsg1-6
Severity: grave
Tags: security
Justification: user security hole
The new version of pyyaml no longer allows use of yaml.load() without a
loader being specifed. This raises a deprecation warning which has
caused and autopkgtest failure on this package.
Package: src:python-tablib
Version: 0.12.1-2
Severity: grave
Tags: security
Justification: user security hole
The new version of pyyaml no longer allows use of yaml.load() without a
loader being specifed. This raises a deprecation warning which has
caused and autopkgtest failure on this package.
Package: src:python-markdown
Version: 3.0.1-3
Severity: grave
Tags: security
Justification: user security hole
The new version of pyyaml no longer allows use of yaml.load() without a
loader being specifed. This raises a deprecation warning which has
caused and autopkgtest failure on this package.
Package: src:lava
Version: 2019.01-5
Severity: grave
Tags: security
Justification: user security hole
The new version of pyyaml no longer allows use of yaml.load() without a
loader being specifed. This raises a deprecation warning which has
caused and autopkgtest failure on this package. These a
Package: src:lavacli
Version: 0.9.7-1
Severity: grave
Tags: security
Justification: user security hole
The new version of pyyaml no longer allows use of yaml.load() without a
loader being specifed. This raises a deprecation warning which has
caused and autopkgtest failure on this package. These
Package: src:knot
Version: 2.7.6-2
Severity: grave
Tags: security
Justification: user security hole
The new version of pyyaml no longer allows use of yaml.load() without a
loader being specifed. This raises a deprecation warning which has
caused and autopkgtest failure on this package. These are
Processing commands for cont...@bugs.debian.org:
> severity 933592 serious
Bug #933592 [node-node-forge,node-jsonld,node-rdf-canonize] Webpack 4
transition: node-node-forge fail to build with webpack 4
Severity set to 'serious' from 'important'
> thanks
Stopping processing here.
Please contact m
Processing commands for cont...@bugs.debian.org:
> severity 933626 serious
Bug #933626 [node-trust-json-document] node-trust-json-document: build fails
with upcoming webpack 4
Severity set to 'serious' from 'important'
> thanks
Stopping processing here.
Please contact me if you need assistance.
Processing commands for cont...@bugs.debian.org:
> severity 933666 serious
Bug #933666 [leaflet-image] leaflet-image: fails to build with webpack 4
Severity set to 'serious' from 'important'
> thanks
Stopping processing here.
Please contact me if you need assistance.
--
933666: https://bugs.debi
Processing commands for cont...@bugs.debian.org:
> severity 933662 serious
Bug #933662 [node-matrix-js-sdk] node-matrix-js-sdk: build with webpack 4
failing
Severity set to 'serious' from 'important'
> thanks
Stopping processing here.
Please contact me if you need assistance.
--
933662: https:/
Processing control commands:
> affects -1 + src:apipkg src:betamax src:ccdproc src:chardet
Bug #933914 [python3-pytest] python3-pytest: pytest v4 breaks existing tests
Added indication that 933914 affects src:apipkg, src:betamax, src:ccdproc, and
src:chardet
> affects -1 + src:dask src:django-axe
Package: python3-pytest
Version: 4.6.4-1
Severity: serious
Justification: breaks autopkgtest tests
Control: affects -1 + src:apipkg src:betamax src:ccdproc src:chardet
Control: affects -1 + src:dask src:django-axes src:doit src:drms
Control: affects -1 + src:fiat src:mpi4py src:pandas src:pygalmesh
Hi Kenneth, Ian,
On Wed, Jul 31, 2019 at 08:45:54PM -0500, Kenneth Pronovici wrote:
> On Wed, Jul 31, 2019 at 10:46 AM Ian Jackson
> wrote:
> > > Otherwise, I will see if I can determine how well the package works
> > > without epydoc installed. If it works (i.e. doesn't blow up) and I
> > > don
I decided to NMU and uploaded a few days ago, so things are in good shape
now, I think. You can integrate my changes whenever you have time. Thanks
for confirming that your ok with the NMU. I was hoping you would be.
KEN
On Sun, 2019 Aug 4 03:20-04:00, Salvatore Bonaccorso wrote:
>
> Sure it might have been overlooked, but pinging the existing bug would
> have been less overhead to now as well start tracking this one as well
> adjusting metadata etc. But no worries.
Just so that I understand, there was an existin
Your message dated Sun, 04 Aug 2019 23:49:40 +
with message-id
and subject line Bug#933710: fixed in crosshurd 1.7.53
has caused the Debian Bug report #933710,
regarding crosshurd: fails to download any packages
to be marked as done.
This means that you claim that the problem has been dealt w
Processing control commands:
> tags -1 + pending
Bug #933710 [crosshurd] crosshurd: fails to download any packages
Added tag(s) pending.
--
933710: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=933710
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
Control: tags -1 + pending
Hello,
Wojciech Aniszewski, le ven. 02 août 2019 11:57:34 +0200, a ecrit:
>crosshurd breaks citing the lack of i386 architecture.
Yes.
> |N: Skipping acquire of configured file 'main/binary-hurd-i386/Packages'
> as repository 'http://httpredir.debian.org/debi
Processing control commands:
> severity -1 serious
Bug #933802 [man-db] /usr/bin/mandb: SIGSEGV, Segmentation fault on updating
database.
Severity set to 'serious' from 'important'
> tag -1 fixed-upstream
Bug #933802 [man-db] /usr/bin/mandb: SIGSEGV, Segmentation fault on updating
database.
Adde
Processing commands for cont...@bugs.debian.org:
> severity 933580 serious
Bug #933580 [debian-edu-config] etc/network/if-up.d/hostname causes loss of
dynamic v4 IP address
Severity set to 'serious' from 'important'
> thanks
Stopping processing here.
Please contact me if you need assistance.
--
Your message dated Sun, 04 Aug 2019 22:05:21 +
with message-id
and subject line Bug#933881: Removed package(s) from unstable
has caused the Debian Bug report #783936,
regarding FTBFS: build-depends on removed python-uno
to be marked as done.
This means that you claim that the problem has been
Your message dated Sun, 04 Aug 2019 20:44:57 +
with message-id
and subject line Bug#933496: fixed in libminini 1.2.a+ds-4
has caused the Debian Bug report #933496,
regarding libminini: doesn't ship needed headers files
to be marked as done.
This means that you claim that the problem has been
Source: zope2.13
Severity: serious
Should zope2.13 be removed?
- Unmaintained (last upload in 2014)
- FTBFS for a long time, missed two stable releases
Cheers,
Moritz
Source: percona-xtrabackup
Severity: serious
Should percona-xtrabackup be removed?
- Unmaintained (last maintainer upload in 2014)
- FTBFS with GCC 6 and later (#811896) and #917583
- Missed two stable releases because of that
- Broken with current Mariadb (#903043)
- Replacement exists (mariabac
Your message dated Sun, 04 Aug 2019 19:36:18 +
with message-id
and subject line Bug#933618: fixed in python-crypto 2.6.1-10
has caused the Debian Bug report #933618,
regarding python-crypto: Epydoc will be removed
to be marked as done.
This means that you claim that the problem has been dealt
Your message dated Sun, 4 Aug 2019 20:54:15 +0200
with message-id
and subject line Fixed
has caused the Debian Bug report #911688,
regarding willow FTBFS: ModuleNotFoundError: No module named 'cv2'
to be marked as done.
This means that you claim that the problem has been dealt with.
If this is n
For some strange reason page https://tracker.debian.org/pkg/mariadb-10.3
still says "Updating mariadb-10.3 introduces new bugs: #910902".
Do you Sandro have any ideas why that is?
Source: pygalmesh
Severity: important
Tags: moreinfo,unreproducible
Followup-For: Bug #933848
I'm quite confused by this bug report. pygalmesh is configured to
build using pybuild not cmake, and it does build that way without
cmake (whether built via 'fakeroot debian/rules binary' or
'dpkg-buildp
I just released v4.1.7 which contains the fix for this bug. Please package
it as you see fit.
Processing commands for cont...@bugs.debian.org:
> affects 933868 node-axios
Bug #933868 [grunt] grunt should look for tasks in /usr/share/nodejs as well
Added indication that 933868 affects node-axios
> thanks
Stopping processing here.
Please contact me if you need assistance.
--
933868: https:
Processing commands for cont...@bugs.debian.org:
> affects 933868 node-handlebars
Bug #933868 [grunt] grunt should look for tasks in /usr/share/nodejs as well
Added indication that 933868 affects node-handlebars
> thanks
Stopping processing here.
Please contact me if you need assistance.
--
9338
Package: grunt
version: 1.0.1-8
severity: grave
node-grunt-webpack and others now install in /usr/share/nodejs and this
patch ->
https://salsa.debian.org/js-team/grunt/blob/master/debian/patches/add-root-variable.patch
should be updated to handle the new path.
Package: adb
Version: 1:8.1.0+r23-5
Severity: grave
Justification: renders package unusable
Dear Maintainer,
the problem appears to be a regression between 9 (Stretch) and 10 (Buster) as
adb worked fine under Stretch and doesn't work anymore under Buster.
When I try to start 'adb' using 'adb de
Your message dated Sun, 04 Aug 2019 14:12:34 +
with message-id
and subject line Bug#930996: fixed in cloudkitty 8.0.0-4+deb10u1
has caused the Debian Bug report #930996,
regarding cloudkitty: FTBFS in buster (Can't resolve label reference for ORDER
BY / GROUP BY)
to be marked as done.
This m
Your message dated Sun, 04 Aug 2019 13:53:19 +
with message-id
and subject line Bug#933279: fixed in pytables 3.5.2-2
has caused the Debian Bug report #933279,
regarding pytables: BD on texlive-generic-extra which isn't build anymore and
isn't in bullseye
to be marked as done.
This means tha
Your message dated Sun, 04 Aug 2019 13:25:50 +
with message-id
and subject line Bug#933845: fixed in petsc 3.11.3+dfsg1-2
has caused the Debian Bug report #933845,
regarding libpmi-pmix-dev: MPI failure in dolfin tests
to be marked as done.
This means that you claim that the problem has been
Package: solr-jetty
Version: 3.6.2+dfsg-20
Severity: grave
Justification: renders package unusable
Hi Maintainers,
Jetty refuses to start SOLR due to a (probably) depreceated call in
/etc/solr/solr-jetty.xml:
Here is the relevant part from journalctl:
Aug 04 14:55:00 srv1
On 2019-08-04 19:19, Drew Parsons wrote:
Probably this is a clue: libdolfin.so should link to libpetsc.so. But
it is missing in the new libdolfin.so. That means pmix is not the
problem, so I'll close the bug against pmix once I can confirm.
CMake logs confirm the that petsc test fail link
Your message dated Sun, 04 Aug 2019 12:22:56 +
with message-id
and subject line Bug#884974: fixed in sdpa 7.3.11+dfsg-1.1
has caused the Debian Bug report #884974,
regarding sdpa: hardcoded mumps runtime dependency
to be marked as done.
This means that you claim that the problem has been deal
Your message dated Sun, 04 Aug 2019 19:32:29 +0800
with message-id <64264f585bb8c5b5e8a480981ea7d...@debian.org>
and subject line Re: Bug#933844: libpmi-pmix-dev: MPI failure in dolfin tests
has caused the Debian Bug report #933844,
regarding libpmi-pmix-dev: MPI failure in dolfin tests
to be marke
On 2019-08-04 19:04, Drew Parsons wrote:
I'm upgrading dolfin/fenics to 2019.1.0 alongside HYPRE 2.16.0, PETSc
3.11.3, pybind11 2.3.0. The tests of the libraries have passed, but
the build is failing badly with an MPI error:
Run C++ regressions tests (serial)
Test project /home/projects/fe
Source: pygalmesh
Version: 0.3.6-1
Severity: serious
1) pygalmesh FTBFS if cmake is installed. Actually the build succeeds, but the
resulting binary package is almost empty.
With cmake installed:
fakeroot debian/rules clean
dh clean --with python3 --buildsystem=pybuild
dh_auto_clean -O--buil
On 2019-08-04 19:17, Drew Parsons wrote:
On 2019-08-04 19:04, Drew Parsons wrote:
Probably this is a clue: libdolfin.so should link to libpetsc.so. But
it is missing in the new libdolfin.so. That means pmix is not the
problem, so I'll close this bug once I can confirm.
Yes, dolfin's cmak
Dear Michael!
Debian Bug Tracking System - 03.08.19, 19:15:08 CEST:
> Your message dated Sat, 03 Aug 2019 17:13:41 +
> with message-id
> and subject line Bug#933598: fixed in chromium 76.0.3809.87-2
> has caused the Debian Bug report #933598,
> regarding Most extensions now crash upon browser
On 2019-08-04 19:04, Drew Parsons wrote:
I'm upgrading dolfin/fenics to 2019.1.0 alongside HYPRE 2.16.0, PETSc
3.11.3, pybind11 2.3.0. The tests of the libraries have passed, but
the build is failing badly with an MPI error:
Run C++ regressions tests (serial)
Test project /home/projects/fe
Processing commands for cont...@bugs.debian.org:
> clone 933844 -1
Bug #933844 [libpmi-pmix-dev] libpmi-pmix-dev: MPI failure in dolfin tests
Bug 933844 cloned as bug 933845
> reassign -1 libpetsc-real3.11-dev
Bug #933845 [libpmi-pmix-dev] libpmi-pmix-dev: MPI failure in dolfin tests
Bug reassigne
Package: libpmi-pmix-dev
Version: 3.1.4~rc2-1
Severity: serious
Justification: breaks MPI client tests
Hi Alistair and Debian science,
I'm upgrading dolfin/fenics to 2019.1.0 alongside HYPRE 2.16.0, PETSc
3.11.3, pybind11 2.3.0. The tests of the libraries have passed, but
the build is failing ba
Processing commands for cont...@bugs.debian.org:
> tag 933835 + moreinfo
Bug #933835 [libreoffice] libreoffice not start with fatal exception signal 11
Added tag(s) moreinfo.
> tag 933835 + unreproducible
Bug #933835 [libreoffice] libreoffice not start with fatal exception signal 11
Added tag(s) u
Package: libreoffice
Version: 1:6.3.0~rc2-1
Severity: grave
Tags: a11y
Justification: renders package unusable
After normal upgradin a system from apt libre office wont start any more.
Program not start and when put libreoffoce at console there is info:
sanskryt@sauron:~$ libreoffice
Fatal exce
Control: retitle -1 ocaml-base-nox: missing Breaks+Replaces: ocaml-base (<<
4.08.0-4)
On 04/08/2019 05.48, Stéphane Glondu wrote:
>> Preparing to unpack .../ocaml-nox_4.08.0-3_amd64.deb ...
>> Unpacking ocaml-nox (4.08.0-3) over (4.05.0-11) ...
>> dpkg: error processing archive
>> /var/cac
Processing control commands:
> retitle -1 ocaml-base-nox: missing Breaks+Replaces: ocaml-base (<< 4.08.0-4)
Bug #933792 [ocaml-nox,ocaml-base-nox] ocaml-nox/ocaml-base-nox: missing
Breaks+Replaces: ocaml-base-nox/ocaml-nox (<< 4.08)
Changed Bug title to 'ocaml-base-nox: missing Breaks+Replaces: o
Processing control commands:
> tags 926895 + patch
Bug #926895 [src:libxslt] libxslt: CVE-2019-11068
Added tag(s) patch.
> tags 926895 + pending
Bug #926895 [src:libxslt] libxslt: CVE-2019-11068
Added tag(s) pending.
> tags 931320 + patch
Bug #931320 [src:libxslt] libxslt: CVE-2019-13118
Added tag
Control: tags 926895 + patch
Control: tags 926895 + pending
Control: tags 931320 + patch
Control: tags 931320 + pending
Control: tags 931321 + patch
Control: tags 931321 + pending
Control: tags 933743 + patch
Control: tags 933743 + pending
Dear maintainer,
I've prepared an NMU for libxslt (versi
Processing control commands:
> tags 926895 + patch
Bug #926895 [src:libxslt] libxslt: CVE-2019-11068
Ignoring request to alter tags of bug #926895 to the same tags previously set
> tags 926895 + pending
Bug #926895 [src:libxslt] libxslt: CVE-2019-11068
Ignoring request to alter tags of bug #926895
Processing control commands:
> tags 926895 + patch
Bug #926895 [src:libxslt] libxslt: CVE-2019-11068
Ignoring request to alter tags of bug #926895 to the same tags previously set
> tags 926895 + pending
Bug #926895 [src:libxslt] libxslt: CVE-2019-11068
Ignoring request to alter tags of bug #926895
Processing control commands:
> tags 926895 + patch
Bug #926895 [src:libxslt] libxslt: CVE-2019-11068
Ignoring request to alter tags of bug #926895 to the same tags previously set
> tags 926895 + pending
Bug #926895 [src:libxslt] libxslt: CVE-2019-11068
Ignoring request to alter tags of bug #926895
Hi Daniel,
On Sat, Aug 03, 2019 at 08:57:56PM -0400, Daniel Richard G. wrote:
> Hi Salvatore,
>
> On Sat, 2019 Aug 3 09:32-04:00, Salvatore Bonaccorso wrote:
> >
> > As you can see from the security-tracker btw, for all three there are
> > bugs filled already. So why a new bug for all three toge
61 matches
Mail list logo
