Processing commands for cont...@bugs.debian.org:
> tags 947579 + ftbfs
Bug #947579 [src:rlvm] FTBFS with scons 3.1.2-1
Added tag(s) ftbfs.
> thanks
Stopping processing here.
Please contact me if you need assistance.
--
947579: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=947579
Debian Bug
Processing commands for cont...@bugs.debian.org:
> tags 947560 + ftbfs
Bug #947560 [src:ffmpeg2theora] FTBFS with scons 3.1.2-1
Added tag(s) ftbfs.
> thanks
Stopping processing here.
Please contact me if you need assistance.
--
947560: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=947560
Processing commands for cont...@bugs.debian.org:
> tags 947567 + ftbfs
Bug #947567 [src:libnxt] FTBFS with scons 3.1.2-1
Added tag(s) ftbfs.
> thanks
Stopping processing here.
Please contact me if you need assistance.
--
947567: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=947567
Debian
I can confirm the same issue on my side. I have not attempted any
workarounds but reading online this seems to be related to changes
some Kernel symbol changes.
http://rglinuxtech.com/?p=2614
The reading also has a patch in there which might help.
Your message dated Wed, 29 Jan 2020 07:49:34 +
with message-id
and subject line Bug#936844: fixed in libbde 20190102-1.1
has caused the Debian Bug report #936844,
regarding libbde: Python2 removal in sid/bullseye
to be marked as done.
This means that you claim that the problem has been dealt
Your message dated Wed, 29 Jan 2020 07:49:25 +
with message-id
and subject line Bug#949975: fixed in coq 8.9.1-5
has caused the Debian Bug report #949975,
regarding coq,coqide: both ship /usr/bin/coqidetop{,.opt}
to be marked as done.
This means that you claim that the problem has been dealt
Hi,
See the same here, I wonder how this version could slip through Q
Since the package is unbuildable and thereby renders useless to
everyone I suggest raising severity to grave.
--
Hilsen/Regards
Michael Rasmussen
Get my public GnuPG keys:
michael rasmussen cc
Source: mixxx
Version: 2.0.0~dfsg-7
Severity: serious
The package builds with -msse2, but SSE (or MMX) are not part
of the baseline of the i386 port.
Your message dated Wed, 29 Jan 2020 08:20:00 +0200
with message-id
and subject line r-cran-rlang: autopkgtest regression
has caused the Debian Bug report #949658,
regarding r-cran-rlang: autopkgtest regression
to be marked as done.
This means that you claim that the problem has been dealt with.
Your message dated Wed, 29 Jan 2020 08:15:38 +0200
with message-id
and subject line r-cran-parameters: autopkgtest regression
has caused the Debian Bug report #949659,
regarding r-cran-parameters: autopkgtest regression
to be marked as done.
This means that you claim that the problem has been
Processing control commands:
> tags -1 +fixed-upstream
Bug #945701 [src:mock] mock: Python2 removal in sid/bullseye
Added tag(s) fixed-upstream.
--
945701: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=945701
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
Control: tags -1 +fixed-upstream
On Wed, 27 Nov 2019 23:58:50 + Sandro Tosi wrote:
> Source: mock
> Version: 1.3.2-2
> Severity: normal
> Tags: sid bullseye
> User: debian-pyt...@lists.debian.org
> Usertags: py2removal
it looks like the latest upstream release, 1.4.21-1, contains python3
Le 28/01/2020 à 22:31, Adrian Bunk a écrit :
> Source: node-chrome-trace-event
> Version: 1.0.0-1
> Severity: serious
> Tags: ftbfs bullseye sid
>
> https://tests.reproducible-builds.org/debian/rb-pkg/unstable/amd64/node-chrome-trace-event.html
>
> ...
>debian/rules override_dh_auto_build
>
Your message dated Wed, 29 Jan 2020 05:34:09 +
with message-id
and subject line Bug#950088: fixed in node-rollup-plugin-string 3.0.0-3
has caused the Debian Bug report #950088,
regarding node-rollup-plugin-string: missing build dependency on
node-rollup-plugin-buble
to be marked as done.
Your message dated Wed, 29 Jan 2020 06:33:23 +0100
with message-id <24803083.LKmzBDn3bR@thyrus>
and subject line Exiv2 bug fixed in 0.27
has caused the Debian Bug report #915134,
regarding exiv2: CVE-2018-19607
to be marked as done.
This means that you claim that the problem has been dealt with.
Source: nvidia-graphics-drivers
Version: 435.21-3
Severity: serious
Justification: makes the package in question unusable or mostly so
Dear Maintainer,
The upgrade of nvidia-kernel-dkms failed due to building the module for
5.4.0-3-amd64 failing:
Building initial module for 5.4.0-3-amd64
Package: src:pyside2
Version: 5.13.2-2.2
Severity: serious
Tags: sid bullseye
[...]
Running process in directory /home/packages/tmp/p/pyside2-5.13.2: command
/usr/bin/patchelf --set-rpath $ORIGIN/
Your message dated Wed, 29 Jan 2020 05:00:34 +
with message-id
and subject line Bug#949993: Removed package(s) from unstable
has caused the Debian Bug report #949832,
regarding src:python-publicsuffix: Should not be released with Bullseye
to be marked as done.
This means that you claim that
Package: src:pyside2
Version: 5.13.2-2.2
Severity: serious
Tags: sid bullseye
https://ci.debian.net/packages/p/pyside2/
[...]
autopkgtest [09:55:16]: summary
command1 FAIL non-zero exit status 127
command2 FAIL non-zero exit status 127
command3
Package: src:pyside2
Version: 5.14.0-1~exp1
Severity: serious
Tags: sid bullseye
[...]
(gui) [3295ms] Writing log files...
[ESC[0;32mOKESC[0m]
(gui) [3327ms] Running Source generator...
qt.shiboken: (gui) There's no user provided way (conversion rule, argument
removal, custom code, etc) to handle
Processing control commands:
> tags -1 +fixed-upstream
Bug #936806 [src:koji] koji: Python2 removal in sid/bullseye
Ignoring request to alter tags of bug #936806 to the same tags previously set
--
936806: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=936806
Debian Bug Tracking System
Control: tags -1 +fixed-upstream
On Fri, 30 Aug 2019 09:57:23 + Holger Levsen wrote:
> On Fri, Aug 30, 2019 at 07:22:19AM +, Matthias Klose wrote:
> > Package: src:koji
> > Version: 1.16.2-1
> [...]
> > Your package either build-depends, depends on Python2, or uses Python2
> > in the
Processing commands for cont...@bugs.debian.org:
> user release.debian@packages.debian.org
Setting user to release.debian@packages.debian.org (was a...@debian.org).
> usertags 949039 piuparts
There were no usertags set.
Usertags are now: piuparts.
> usertags 942135 piuparts
There were no
Processing commands for cont...@bugs.debian.org:
> reassign 950056 python3.8
Bug #950056 [src:python-bleach] python-bleach FTBFS: test failures with Python
3.7.6 and 3.8.1
Bug reassigned from package 'src:python-bleach' to 'python3.8'.
No longer marked as found in versions python-bleach/3.1.0-2.
pygts is dead upstream and the C parts of the code will need a bit of work to
port them to Python 3. This package does have a reasonable popcon (281) but
it's hard to see the porting work happening.
The package needs to go through NEW either with an added python3-gts binary
package or if
Processing control commands:
> found -1 6.0.2p1-2
Bug #950121 [opensmtpd] opensmtpd: Major vulnerabilities in opensmtpd resulting
in RCE and DOS
Marked as found in versions opensmtpd/6.0.2p1-2.
> fixed -1 6.6.2p1-1
Bug #950121 [opensmtpd] opensmtpd: Major vulnerabilities in opensmtpd resulting
Control: found -1 6.0.2p1-2
Control: fixed -1 6.6.2p1-1
This has already been fixed in unstable. I am preparing updates for
oldstable and stable.
—RAK
--
|)|/ Ryan Kavanagh | GPG: 4E46 9519 ED67 7734 268F
|\|\ https://rak.ac | BD95 8F7B F8FC 4A11 C97A
signature.asc
Processing commands for cont...@bugs.debian.org:
> fixed 950121 6.6.2p1-1
Bug #950121 [opensmtpd] opensmtpd: Major vulnerabilities in opensmtpd resulting
in RCE and DOS
Marked as fixed in versions opensmtpd/6.6.2p1-1.
> thanks
Stopping processing here.
Please contact me if you need assistance.
Processing commands for cont...@bugs.debian.org:
> tags 947570 + fixed-upstream
Bug #947570 [src:mypaint] FTBFS with scons 3.1.2-1
Added tag(s) fixed-upstream.
> thanks
Stopping processing here.
Please contact me if you need assistance.
--
947570:
>From the OpenBSD security advisory
>Errata patches for OpenSMTPD have been released for OpenBSD 6.5 and 6.6.
>
>smtpd can crash on opportunistic TLS downgrade, causing a denial of service.
>
>Binary updates for the amd64, i386, and arm64 platforms are available via
>the syspatch utility. Source
Package: opensmtpd
Version: 6.6.1p1-5~bpo10+1
Severity: critical
Tags: security upstream
Justification: root security hole
Dear Maintainer,
Opensmtpd 6.6.1 has 2 critical vulnerabilities, including one that results in a
remote root arbitray code execution
see
Processing commands for cont...@bugs.debian.org:
> tags 950116 + patch
Bug #950116 [gplaycli] gplaycli: KeyError: 'docId' --or-- 'Item not found.'
Added tag(s) patch.
> thanks
Stopping processing here.
Please contact me if you need assistance.
--
950116:
tags 950116 + patch
thanks
Find below a patch extracted from commit
719793f65a1ae4e91a12fc49d510095f6bf45e0b
which at least fixes the docId issue.
The “Item not found” issue might be because the shitty DB Navigator äpp
requires Android 5 (and thus is unusable anyway)… but with the nonexistent
Your message dated Tue, 28 Jan 2020 23:35:37 +
with message-id
and subject line Bug#938006: fixed in python-pattern 2.6+git20180818-2
has caused the Debian Bug report #938006,
regarding python-pattern: Python2 removal in sid/bullseye
to be marked as done.
This means that you claim that the
Your message dated Tue, 28 Jan 2020 23:35:37 +
with message-id
and subject line Bug#946760: fixed in python-pattern 2.6+git20180818-2
has caused the Debian Bug report #946760,
regarding python-pattern: needs a source-only upload.
to be marked as done.
This means that you claim that the
Processing commands for cont...@bugs.debian.org:
> forwarded 950112 https://github.com/matlink/gplaycli/issues/237
Bug #950112 [gplaycli] gplaycli: 502 Bad Gateway, does not work at all
Set Bug forwarded-to-address to
'https://github.com/matlink/gplaycli/issues/237'.
> forwarded 950114
Dixi quod…
>[ERROR] Unknown error:
>502 Bad Gateway
It’s apparently possible to work around this error by
getting a Google account, logging in, creating an
application password, then putting that password and
the eMail address used as login, as well as token=False,
into
Package: gplaycli
Version: 3.26+dfsg-1
Severity: grave
Justification: renders package unusable
Similar to #950114, downloading (getting the ID from the gplay
website) does not work:
$ gplaycli -pvd com.musescore.playerlite
[INFO] GPlayCli version 3.26 [Python3.7.6]
[INFO] Configuration file is
Package: gplaycli
Version: 3.26+dfsg-1
Severity: grave
Justification: renders package unusable
After generating an application password and putting it into
/etc/gplaycli/gplaycli.conf (see below) to work around #950112
things still don’t work:
$ gplaycli -s musescore
Traceback (most recent call
Processing control commands:
> affects -1 + libdynamicedt3d-dev
Bug #950110 [liboctomap-dev,liboctovis-dev,octomap-tools,octovis]
liboctomap-dev,...: unhandled symlink to directory conversion:
/usr/share/doc/PACKAGE
Added indication that 950110 affects libdynamicedt3d-dev
--
950110:
Followup-For: Bug #950110
Control: affects -1 + libdynamicedt3d-dev
0m24.8s ERROR: FAIL: silently overwrites files via directory symlinks:
/usr/share/doc/libdynamicedt3d-dev/changelog.Debian.gz
(libdynamicedt3d-dev:amd64) !=
/usr/share/doc/libdynamicedt3d1.8/changelog.Debian.gz
Package: gplaycli
Version: 3.26+dfsg-1
Severity: grave
Justification: renders package unusable
After installation, gplaycli --help works (but please do add
a manual page), but nothing else:
$ gplaycli -s musescore
cache file does not exists or is corrupted
Unknown error:
502 Bad Gateway
502
Package: libvigraimpex-doc
Version: 1.11.1+dfsg-6
Severity: serious
User: debian...@lists.debian.org
Usertags: piuparts
Hi,
an upgrade test with piuparts revealed that your package installs files
over existing symlinks and possibly overwrites files owned by other
packages. This usually means an
Package: liboctomap-dev,liboctovis-dev,octomap-tools,octovis
Version: 1.9.3+dfsg-1
Severity: serious
User: debian...@lists.debian.org
Usertags: piuparts
Hi,
an upgrade test with piuparts revealed that your package installs files
over existing symlinks and possibly overwrites files owned by other
Processing commands for cont...@bugs.debian.org:
> tags 936483 + fixed-upstream
Bug #936483 [src:enki-aseba] enki-aseba: Python2 removal in sid/bullseye
Added tag(s) fixed-upstream.
> thanks
Stopping processing here.
Please contact me if you need assistance.
--
936483:
Your message dated Tue, 28 Jan 2020 23:28:14 +0100
with message-id <3985202.6kK0O7tDP2@thyrus>
and subject line Exiv2 bug fixed in 0.27
has caused the Debian Bug report #876948,
regarding FTBFS: fails to configure due to change in gcc -dumpversion output
to be marked as done.
This means that you
Processing commands for cont...@bugs.debian.org:
> forwarded 936483 https://github.com/enki-community/enki/issues/8
Bug #936483 [src:enki-aseba] enki-aseba: Python2 removal in sid/bullseye
Set Bug forwarded-to-address to
'https://github.com/enki-community/enki/issues/8'.
> thanks
Stopping
Package: r-cran-dt
Version: 0.11+dfsg-1
Severity: serious
User: debian...@lists.debian.org
Usertags: piuparts
Hi,
an upgrade test with piuparts revealed that your package installs files
over existing symlinks and possibly overwrites files owned by other
packages. This usually means an old
Your message dated Tue, 28 Jan 2020 23:18:39 +0100
with message-id <4053006.7PYGpGPFRf@thyrus>
and subject line Exiv2 bug fixed in 0.27
has caused the Debian Bug report #69,
regarding exiv2: CVE-2017-14857
to be marked as done.
This means that you claim that the problem has been dealt with.
Your message dated Tue, 28 Jan 2020 23:18:39 +0100
with message-id <4053006.7PYGpGPFRf@thyrus>
and subject line Exiv2 bug fixed in 0.27
has caused the Debian Bug report #74,
regarding exiv2: CVE-2017-11553
to be marked as done.
This means that you claim that the problem has been dealt with.
Your message dated Tue, 28 Jan 2020 23:18:39 +0100
with message-id <4053006.7PYGpGPFRf@thyrus>
and subject line Exiv2 bug fixed in 0.27
has caused the Debian Bug report #73,
regarding exiv2: CVE-2017-12955
to be marked as done.
This means that you claim that the problem has been dealt with.
Your message dated Tue, 28 Jan 2020 23:18:39 +0100
with message-id <4053006.7PYGpGPFRf@thyrus>
and subject line Exiv2 bug fixed in 0.27
has caused the Debian Bug report #903763,
regarding exiv2: CVE-2018-14046
to be marked as done.
This means that you claim that the problem has been dealt with.
Your message dated Tue, 28 Jan 2020 23:18:39 +0100
with message-id <4053006.7PYGpGPFRf@thyrus>
and subject line Exiv2 bug fixed in 0.27
has caused the Debian Bug report #62,
regarding exiv2: CVE-2018-5772
to be marked as done.
This means that you claim that the problem has been dealt with.
If
Your message dated Tue, 28 Jan 2020 23:18:39 +0100
with message-id <4053006.7PYGpGPFRf@thyrus>
and subject line Exiv2 bug fixed in 0.27
has caused the Debian Bug report #64,
regarding exiv2: CVE-2017-1000126
to be marked as done.
This means that you claim that the problem has been dealt with.
Your message dated Tue, 28 Jan 2020 23:18:39 +0100
with message-id <4053006.7PYGpGPFRf@thyrus>
and subject line Exiv2 bug fixed in 0.27
has caused the Debian Bug report #894179,
regarding exiv2: CVE-2018-8977
to be marked as done.
This means that you claim that the problem has been dealt with.
If
Your message dated Tue, 28 Jan 2020 23:18:39 +0100
with message-id <4053006.7PYGpGPFRf@thyrus>
and subject line Exiv2 bug fixed in 0.27
has caused the Debian Bug report #63,
regarding exiv2: CVE-2017-1000127
to be marked as done.
This means that you claim that the problem has been dealt with.
Your message dated Tue, 28 Jan 2020 23:18:39 +0100
with message-id <4053006.7PYGpGPFRf@thyrus>
and subject line Exiv2 bug fixed in 0.27
has caused the Debian Bug report #912828,
regarding exiv2: CVE-2018-18915
to be marked as done.
This means that you claim that the problem has been dealt with.
Your message dated Tue, 28 Jan 2020 23:18:39 +0100
with message-id <4053006.7PYGpGPFRf@thyrus>
and subject line Exiv2 bug fixed in 0.27
has caused the Debian Bug report #66,
regarding exiv2: CVE-2017-14863
to be marked as done.
This means that you claim that the problem has been dealt with.
Your message dated Tue, 28 Jan 2020 23:18:39 +0100
with message-id <4053006.7PYGpGPFRf@thyrus>
and subject line Exiv2 bug fixed in 0.27
has caused the Debian Bug report #72,
regarding exiv2: CVE-2017-12956
to be marked as done.
This means that you claim that the problem has been dealt with.
Your message dated Tue, 28 Jan 2020 23:18:39 +0100
with message-id <4053006.7PYGpGPFRf@thyrus>
and subject line Exiv2 bug fixed in 0.27
has caused the Debian Bug report #67,
regarding exiv2: CVE-2017-14860
to be marked as done.
This means that you claim that the problem has been dealt with.
Your message dated Tue, 28 Jan 2020 23:18:39 +0100
with message-id <4053006.7PYGpGPFRf@thyrus>
and subject line Exiv2 bug fixed in 0.27
has caused the Debian Bug report #880027,
regarding exiv2: CVE-2017-14861: stack-overflow vulnerability in
Exiv2::Internal::stringFormat[abi:cxx11] (in
Your message dated Tue, 28 Jan 2020 23:18:39 +0100
with message-id <4053006.7PYGpGPFRf@thyrus>
and subject line Exiv2 bug fixed in 0.27
has caused the Debian Bug report #65,
regarding exiv2: CVE-2017-14865
to be marked as done.
This means that you claim that the problem has been dealt with.
Your message dated Tue, 28 Jan 2020 23:22:50 +0100
with message-id <3437808.VheC7TtmtP@thyrus>
and subject line Finally fixed with latest exiv2 upload
has caused the Debian Bug report #870873,
regarding exiv2: FTBFS: some symbols or patterns disappeared in the symbols file
to be marked as done.
Your message dated Tue, 28 Jan 2020 23:18:39 +0100
with message-id <4053006.7PYGpGPFRf@thyrus>
and subject line Exiv2 bug fixed in 0.27
has caused the Debian Bug report #880015,
regarding exiv2: CVE-2017-14866
to be marked as done.
This means that you claim that the problem has been dealt with.
Your message dated Tue, 28 Jan 2020 23:18:39 +0100
with message-id <4053006.7PYGpGPFRf@thyrus>
and subject line Exiv2 bug fixed in 0.27
has caused the Debian Bug report #876242,
regarding exiv2: CVE-2017-12957
to be marked as done.
This means that you claim that the problem has been dealt with.
Package: ruby-kramdown
Version: 1.17.0-3
Severity: serious
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA512
The package no longer ships the kramdown-1.17.0.gemspec file. Thus packages
using e.g. gem2deb-test-runner --check-dependencies will fail here. For example
jekyll's dependencies cannot
Package: tdiary-mode
Version: 5.1.0-1
Severity: serious
User: debian...@lists.debian.org
Usertags: piuparts
Hi,
during a test with piuparts I noticed your package fails to upgrade from
'stretch'.
It installed fine in 'buster', then the upgrade to 'bullseye' fails.
>From the attached log (scroll
Processing commands for cont...@bugs.debian.org:
> tags 948970 + bullseye sid
Bug #948970 [src:fonts-freefont] The build isn't compatible with python3
Added tag(s) sid and bullseye.
> thanks
Stopping processing here.
Please contact me if you need assistance.
--
948970:
Source: fonts-lemonada
Version: 4.004+git20190612-1
Severity: serious
Tags: ftbfs
https://tests.reproducible-builds.org/debian/rb-pkg/unstable/amd64/fonts-lemonada.html
...
debian/rules override_dh_auto_build
make[1]: Entering directory '/build/1st/fonts-lemonada-4.004+git20190612'
fontmake
Source: fonts-oldstandard
Version: 2.2really-3
Severity: serious
Tags: ftbfs bullseye sid
https://tests.reproducible-builds.org/debian/rb-pkg/unstable/amd64/fonts-oldstandard.html
...
fontforge -script ost-generate.py
Copyright (c) 2000-2019. See AUTHORS for Contributors.
License GPLv3+: GNU
Processing control commands:
> tags -1 patch
Bug #950101 [python-xarray-doc] python-xarray-doc: FTBFS with new ipython
Added tag(s) patch.
--
950101: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=950101
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
Package: python-xarray-doc
Version: 0.14.1-2
Severity: serious
Control: tags -1 patch
ipython_directive examples are executed at build time. xarray has some
examples that fail without optional dependencies Debian doesn't have
(e.g. h5netcdf) and/or downloaded data. This used to put the error
Processing commands for cont...@bugs.debian.org:
> reassign 948970 src:fonts-freefont 20120503-9
Bug #948970 [fonts-freefont] The build isn't compatible with python3
Bug reassigned from package 'fonts-freefont' to 'src:fonts-freefont'.
No longer marked as found in versions 20120503-9.
Ignoring
Source: fonts-inter
Version: 3.11-1
Severity: serious
Tags: ftbfs
https://tests.reproducible-builds.org/debian/rb-pkg/unstable/amd64/fonts-inter.html
...
debian/rules override_dh_auto_build
make[1]: Entering directory '/build/1st/fonts-inter-3.11'
fontmake -i -o otf -g src/Inter.glyphs
Package: python-patsy-doc
Version: 0.5.1-0.2
Severity: serious
Control: tags -1 patch
Some examples in patsy's spline-regression.rst raise exceptions when
executed (at documentation build time). Such exceptions used to appear
in the documentation output, but in ipython_directive 7.x they
Processing control commands:
> tags -1 patch
Bug #950098 [python-patsy-doc] patsy: exceptions in documentation, FTBFS with
new ipython
Added tag(s) patch.
--
950098: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=950098
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
Your message dated Tue, 28 Jan 2020 21:53:12 +
with message-id
and subject line Bug#950030: fixed in python-pyfaidx 0.5.8-2
has caused the Debian Bug report #950030,
regarding python-pyfaidx FTBFS: bgzip not found
to be marked as done.
This means that you claim that the problem has been
Followup-For: Bug #946470
Control: found -1 1:6.4.0~rc3-1
Control: affects -1 + libreoffice-l10n-kmr
Hi Rene,
there are still a few left when upgrading from testing (1:6.3.4-2) to
sid (1:6.4.0~rc3-1):
0m37.5s ERROR: FAIL: silently overwrites files via directory symlinks:
Processing control commands:
> found -1 1:6.4.0~rc3-1
Bug #946470 {Done: Rene Engelhard } [libreoffice-l10n-de]
libreoffice-l10n-de: unhandled symlink to directory conversion:
/usr/share/doc/PACKAGE
Marked as found in versions libreoffice/1:6.4.0~rc3-1 and reopened.
> affects -1 +
Processing commands for cont...@bugs.debian.org:
> forwarded 62 https://github.com/Exiv2/exiv2/issues/216
Bug #62 [src:exiv2] exiv2: CVE-2018-5772
Set Bug forwarded-to-address to 'https://github.com/Exiv2/exiv2/issues/216'.
> tags 62 + fixed-upstream
Bug #62 [src:exiv2] exiv2:
Package: libblasr-dev
Version: 5.3.3+dfsg-3
Severity: serious
User: debian...@lists.debian.org
Usertags: piuparts
Hi,
during a test with piuparts I noticed your package fails to upgrade from
'testing'.
It installed fine in 'testing', then the upgrade to 'sid' fails
because it tries to overwrite
Source: ipywidgets
Version: 6.0.0-6
Severity: serious
Tags: ftbfs
https://tests.reproducible-builds.org/debian/rb-pkg/unstable/amd64/ipywidgets.html
...
rm -rf "fakewebpack/widgetsnbextension" && mkdir -p
"fakewebpack/widgetsnbextension" && ./fakewebpack-generate.py
Source: node-base64url
Version: 3.0.1-2
Severity: serious
Tags: ftbfs bullseye sid
https://tests.reproducible-builds.org/debian/rb-pkg/unstable/amd64/node-base64url.html
...
debian/rules override_dh_auto_build
make[1]: Entering directory '/build/1st/node-base64url-3.0.1'
pandoc --from
Source: node-prop-types
Version: 15.6.0+ds-3
Severity: serious
Tags: ftbfs
https://tests.reproducible-builds.org/debian/rb-pkg/unstable/amd64/node-prop-types.html
...
debian/rules override_dh_auto_build
make[1]: Entering directory '/build/1st/node-prop-types-15.6.0+ds'
webpack --config
Source: gcc-mingw-w64
Version: 22~exp2
Severity: serious
User: debian...@lists.debian.org
Usertags: piuparts
Control: affects -1 + gcc-mingw-w64-x86-64 gfortran-mingw-w64-x86-64
g++-mingw-w64-x86-64 gobjc-mingw-w64-x86-64 gobjc++-mingw-w64-x86-64
gnat-mingw-w64-x86-64
Control: affects -1 +
Processing control commands:
> affects -1 + gcc-mingw-w64-x86-64 gfortran-mingw-w64-x86-64
> g++-mingw-w64-x86-64 gobjc-mingw-w64-x86-64 gobjc++-mingw-w64-x86-64
> gnat-mingw-w64-x86-64
Bug #950090 [src:gcc-mingw-w64] gcc-mingw-w64: unhandled symlink to directory
conversion:
Source: node-chrome-trace-event
Version: 1.0.0-1
Severity: serious
Tags: ftbfs bullseye sid
https://tests.reproducible-builds.org/debian/rb-pkg/unstable/amd64/node-chrome-trace-event.html
...
debian/rules override_dh_auto_build
make[1]: Entering directory
Source: node-rollup-plugin-string
Version: 3.0.0-2
Severity: serious
Tags: ftbfs
https://tests.reproducible-builds.org/debian/rb-pkg/unstable/amd64/node-rollup-plugin-string.html
...
debian/rules override_dh_auto_build
make[1]: Entering directory '/build/1st/node-rollup-plugin-string-3.0.0'
Package: python-statsmodels-doc
Severity: serious
Control: tags -1 patch
(only tested in 0.11, but believed to exist earlier)
Some documentation examples (e.g. contrasts.rst) fail in a Debian build
because they need to download data.
This has been the case for some time, but only became an
Processing control commands:
> tags -1 patch
Bug #950087 [python-statsmodels-doc] statsmodels: FTBFS with new ipython
Added tag(s) patch.
--
950087: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=950087
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
> According to DAK there is an rdepend that needs to be addressed:
>
> Checking reverse dependencies...
> # Broken Build-Depends:
> foolscap: python-txsocksx
>
> Dependency problem found.
ok i see what happened here: the dependency chain is:
python-txsocksx -> foolscap -> tahoe-lafs
both
Your message dated Tue, 28 Jan 2020 20:42:09 +
with message-id
and subject line Bug#949677: fixed in mesa 19.3.3-1
has caused the Debian Bug report #949677,
regarding mesa breaks build of kcrash, konsole and libkscreen as tested in
autopkgtest migration setup
to be marked as done.
This
Package: vim-tlib
Version: 1.27-1
Severity: serious
User: debian...@lists.debian.org
Usertags: piuparts
Hi,
during a test with piuparts I noticed your package modifies files it has
shipped.
>From the attached log (scroll to the bottom...):
0m24.4s ERROR: FAIL: debsums reports modifications
Package: kwartz-client
Version: 1.4-5
Severity: serious
User: debian...@lists.debian.org
Usertags: piuparts
Hi,
during a test with piuparts I noticed your package modifies conffiles.
This is forbidden by the policy, see
https://www.debian.org/doc/debian-policy/ch-files.html#configuration-files
Processing control commands:
> affects -1 + debian-cloud-images-packages
Bug #950079 [grub-cloud-amd64] grub-cloud-amd64: prompting due to modified
conffiles which were not modified by the user: /etc/default/grub
Added indication that 950079 affects debian-cloud-images-packages
--
950079:
Package: grub-cloud-amd64
Version: 0.0.5
Severity: serious
User: debian...@lists.debian.org
Usertags: piuparts
Control: affects -1 + debian-cloud-images-packages
Hi,
during a test with piuparts I noticed your package failed the piuparts
upgrade test because dpkg detected a conffile as being
Package: ovirt-guest-agent
Version: 1.0.15.dfsg-1
Severity: serious
Tags: sid bullseye
User: debian...@lists.debian.org
Usertags: piuparts
Hi,
during a test with piuparts I noticed your package failed to install. As
per definition of the release team this makes the package too buggy for
a
Processing control commands:
> tags 949081 + patch
Bug #949081 [src:wget2] wget2 FTBFS: makeinfo: command not found
Added tag(s) patch.
> tags 949081 + pending
Bug #949081 [src:wget2] wget2 FTBFS: makeinfo: command not found
Added tag(s) pending.
--
949081:
Control: tags 949081 + patch
Control: tags 949081 + pending
Dear maintainer,
I've prepared an NMU for wget2 (versioned as 1.99.1-2.1) and
uploaded it to DELAYED/7. Please feel free to tell me if I
should delay it longer.
Regards.
diff -Nru wget2-1.99.1/debian/changelog
Your message dated Tue, 28 Jan 2020 19:49:46 +
with message-id
and subject line Bug#950053: fixed in pysal 2.1.0-1
has caused the Debian Bug report #950053,
regarding pysal FTBFS: test failures
to be marked as done.
This means that you claim that the problem has been dealt with.
If this is
1 - 100 of 169 matches
Mail list logo
