On Sun, Jul 19, 2020 at 02:45:22AM -0400, Sandro Tosi wrote:
> On Sun, Jul 19, 2020 at 2:41 AM Adrian Bunk wrote:
> >
> > On Sun, Jul 19, 2020 at 02:33:33AM -0400, Sandro Tosi wrote:
> > > > Recommends: r-cran-testthat, python3 | python
> > > >
> > > > Non-default alternative looks OK to me.
> > >
Your message dated Sun, 19 Jul 2020 06:49:05 +
with message-id
and subject line Bug#965283: fixed in node-lodash 4.17.19+dfsg-1
has caused the Debian Bug report #965283,
regarding node-lodash: CVE-2020-8203
to be marked as done.
This means that you claim that the problem has been dealt with.
Processing commands for cont...@bugs.debian.org:
> fixed 965298 1.16.2-2.2
Bug #965298 [gst-plugins-bad1.0] gst-plugins-bad1.0 cannot be built in testing.
There is no source info for the package 'gst-plugins-bad1.0' at version
'1.16.2-2.2' with architecture ''
Unable to make a source version for
On Sun, Jul 19, 2020 at 2:41 AM Adrian Bunk wrote:
>
> On Sun, Jul 19, 2020 at 02:33:33AM -0400, Sandro Tosi wrote:
> > > Recommends: r-cran-testthat, python3 | python
> > >
> > > Non-default alternative looks OK to me.
> >
> > it doesnt really make much sense: either it needs python2 or python3;
On Sun, Jul 19, 2020 at 02:33:33AM -0400, Sandro Tosi wrote:
> > Recommends: r-cran-testthat, python3 | python
> >
> > Non-default alternative looks OK to me.
>
> it doesnt really make much sense: either it needs python2 or python3;
> if "| python" is not needed, it can be just easily dropped, and
Processing control commands:
> found -1 1.17.0-1
Bug #965305 [src:ruby-kramdown] ruby-kramdown: CVE-2020-14001
Marked as found in versions ruby-kramdown/1.17.0-1.
--
965305: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=965305
Debian Bug Tracking System
Contact ow...@bugs.debian.org with pro
Source: ruby-kramdown
Version: 1.17.0-4
Severity: grave
Tags: security upstream
Justification: user security hole
X-Debbugs-Cc: Debian Security Team
Control: found -1 1.17.0-1
Hi,
The following vulnerability was published for ruby-kramdown.
CVE-2020-14001[0]:
| The kramdown gem before 2.3.0 for
> Recommends: r-cran-testthat, python3 | python
>
> Non-default alternative looks OK to me.
it doesnt really make much sense: either it needs python2 or python3;
if "| python" is not needed, it can be just easily dropped, and avoid
the confusion it causes (special cases are not special enough)
--
Your message dated Sun, 19 Jul 2020 07:31:48 +0100
with message-id
and subject line Re: hyperkitty/django-mailman3: FTBFS: ValueError: max() arg
is an empty sequence
has caused the Debian Bug report #964632,
regarding hyperkitty: FTBFS: ValueError: max() arg is an empty sequence
to be marked as d
Your message dated Sun, 19 Jul 2020 07:31:48 +0100
with message-id
and subject line Re: hyperkitty/django-mailman3: FTBFS: ValueError: max() arg
is an empty sequence
has caused the Debian Bug report #964697,
regarding django-mailman3: FTBFS: ValueError: max() arg is an empty sequence
to be marked
On Sat, Jul 18, 2020 at 05:53:29PM -0400, Sandro Tosi wrote:
> Source: r-cran-findpython
> Version: 1.0.5-2
> Severity: normal
> Tags: sid bullseye
> User: debian-pyt...@lists.debian.org
> Usertags: py2removal
>
> Python2 becomes end-of-live upstream, and Debian aims to remove
> Python2 from the d
Package: opendht
Version: 0.6.6-1
Severity: serious
x-debbugs-cc: msgpac...@packages.debian.org
tags: ftbfs
opendht cannot currently be built in unstable, there are two issues.
Firstly, the build can't even be attempted on armel or mipsel because
the build-dependencies are unsatisfiable. The rea
Package: ocamlnet
Version: 4.1.6-1
Severity: serious
Tags: FTBFS
When binnmu'd for the nettle transition ocamlnet failed to build on most
architectures
(it succeeded on mipsel, mips64el and armel) with the following error.
make[1]: Leaving directory '/<>'
dh_dwz -a
dwz: debian/libocamlnet-o
Package: haskell-incremental-parser
Version: 0.4.0.2-1
Severity: serious
haskell-incremental-parser 0.4.0.2-1 added a build-dependency on
libghc-rank2classes-dev (>= 1.0)
however this package is only available on four out of the ten release
archictures.
Potential ways forward:
1. fix haskell-
Processing control commands:
> tag 835340 + patch
Bug #835340 [python-pymetar] python-pymetar: http://weather.noaa.gov/ no longer
available
Ignoring request to alter tags of bug #835340 to the same tags previously set
> tag 938076 + patch
Bug #938076 [src:python-pymetar] python-pymetar: Python2 r
Processing control commands:
> tag 835340 + patch
Bug #835340 [python-pymetar] python-pymetar: http://weather.noaa.gov/ no longer
available
Added tag(s) patch.
> tag 938076 + patch
Bug #938076 [src:python-pymetar] python-pymetar: Python2 removal in sid/bullseye
Added tag(s) patch.
--
835340: ht
Your message dated Sun, 19 Jul 2020 02:16:04 +0100
with message-id
and subject line re: gst-plugins-bad1.0: depend on cruft package libsrt-dev
has caused the Debian Bug report #962725,
regarding gst-plugins-bad1.0: depend on cruft package libsrt-dev
to be marked as done.
This means that you claim
Package: gst-plugins-bad1.0
Version: 1.16.2-2.1
Severity: serious
x-debbugs-cc: sramac...@debian.org, locutusofb...@debian.org
Neither version 1.16.2-2.1 (from bullseye) or version 1.16.2-2.2 (from sid) can
be built in testing.
1.16.2-2.1 cannot be built because libsrt-dev has been removed.
1.
Processing commands for cont...@bugs.debian.org:
> reassign 964879 libgnupg-interface-perl 1.00-1
Bug #964879 [src:request-tracker4] request-tracker4: FTBFS: broken by
libgnupg-interface-perl
Bug reassigned from package 'src:request-tracker4' to 'libgnupg-interface-perl'.
No longer marked as foun
Your message dated Sat, 18 Jul 2020 22:49:23 +
with message-id
and subject line Bug#950816: fixed in mpv 0.32.0-2
has caused the Debian Bug report #950816,
regarding mpv: unintended code execution vulnerability
to be marked as done.
This means that you claim that the problem has been dealt wi
Processing control commands:
> tag -1 pending
Bug #950816 [mpv] mpv: unintended code execution vulnerability
Added tag(s) pending.
--
950816: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=950816
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
Control: tag -1 pending
Hello,
Bug #950816 in mpv 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:
https://salsa.debian.org/multimedia-team/mpv/-/commit/3b52150eed39653c009ecf6474a5eccb7
Your message dated Sat, 18 Jul 2020 22:33:46 +
with message-id
and subject line Bug#963364: fixed in libocxl 1.1.0-1.1
has caused the Debian Bug report #963364,
regarding libocxl: FTBFS: Makefile:27: *** 'ocxl.h is non-existant or out of
date, Download from
http://git.kernel.org/cgit/linux/k
Processing commands for cont...@bugs.debian.org:
> # This is an automated script, part of the effort for the removal of Python 2
> from bullseye
> # * https://wiki.debian.org/Python/2Removal
> # * http://sandrotosi.me/debian/py2removal/index.html
> # See https://lists.debian.org/debian-devel-an
Control: reopen -1
This bug was closed, but the package has still some dependencies towards
Python2 packages, in details:
(binary:dh-virtualenv)Depends->python-virtualenv
Re-opening, so that they can be taken care of.
Processing control commands:
> reopen -1
Bug #942958 {Done: Jyrki Pulliainen } [src:dh-virtualenv]
dh-virtualenv: Python2 removal in sid/bullseye
Bug #936392 {Done: Jyrki Pulliainen } [src:dh-virtualenv]
dh-virtualenv: Python2 removal in sid/bullseye
'reopen' may be inappropriate when a bug has
Package: sssd-ad
Version: 2.3.0-2
Followup-For: Bug #965143
I might have a related issue with logins for AD accounts. I fixed
ndr_pull_security_ace to again correctly parse GPOs in the AD back end.
Without this fix, SSS_PAM_ACCT_MGMT fails for pam_sss, and users can not log
in. A symptom of the bu
Source: node-lodash
Version: 4.17.15+dfsg-2
Severity: grave
Tags: security upstream
Justification: user security hole
X-Debbugs-Cc: Debian Security Team
Hi,
The following vulnerability was published for node-lodash.
CVE-2020-8203[0]:
| Prototype pollution attack when using _.zipObjectDeep in lo
Processing commands for cont...@bugs.debian.org:
> severity 915837 serious
Bug #915837 [camping] camping: FTBFS with rails 5.2
Severity set to 'serious' from 'important'
> thanks
Stopping processing here.
Please contact me if you need assistance.
--
915837: https://bugs.debian.org/cgi-bin/bugrep
X-Debbugs-CC: debian-fo...@lists.debian.org m...@debian.org
On Thu, 16 Jul 2020 23:19:31 +0200 Andreas Beckmann
wrote:
> Package: afdko-bin
> Version: 3.4.0+dfsg1-2
> Severity: serious
>
> Preparing to unpack .../afdko-bin_3.4.0+dfsg1-2_amd64.deb ...
> Unpacking afdko-bin (3.4.0+dfsg1-2) ...
Your message dated Sat, 18 Jul 2020 19:33:34 +
with message-id
and subject line Bug#952044: fixed in ruby-browser 4.2.0-2
has caused the Debian Bug report #952044,
regarding ruby-browser: FTBFS: ERROR: Test "ruby2.7" failed: Invalid gemspec in
[browser.gemspec]: No such file or directory - gi
Processing control commands:
> tag -1 pending
Bug #952044 [src:ruby-browser] ruby-browser: FTBFS: ERROR: Test "ruby2.7"
failed: Invalid gemspec in [browser.gemspec]: No such file or directory - git
Added tag(s) pending.
--
952044: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=952044
Debian
Control: tag -1 pending
Hello,
Bug #952044 in ruby-browser 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:
https://salsa.debian.org/ruby-team/ruby-browser/-/commit/1230e31eccd2e17e4f331
Processing commands for cont...@bugs.debian.org:
> fixed 964873 1.7.4+dfsg1-1
Bug #964873 [src:consul] consul: FTBFS:
src/github.com/hashicorp/consul/agent/consul/server.go:467:29: cannot use
s.logger (type *log.Logger) as type hclog.Logger in assignment
Marked as fixed in versions consul/1.7.4+
Package: meson
Version: 0.55.0-2
Severity: serious
Tags: ftbfs
Control: affects -1 src:gjs src:iagno src:libpeas
I cannot judge whether this is a meson regression,
or existing bugs that just happened to work with
older meson.
https://tests.reproducible-builds.org/debian/rb-pkg/unstable/amd64/gj
Processing control commands:
> affects -1 src:gjs src:iagno src:libpeas
Bug #965278 [meson] meson 0.55.0 causes build failures
Added indication that 965278 affects src:gjs, src:iagno, and src:libpeas
--
965278: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=965278
Debian Bug Tracking System
C
Source: gnome-shell-xrdesktop
Version: 3.36.1-2
Severity: serious
Packages in main are only allowed to build depend on packages in main.
gnome-shell-xrdesktop build depends on libopenvr-dev
which is in contrib.
Processing commands for cont...@bugs.debian.org:
> retitle 964635 electrum: FTBFS: dpkg-source: error: failed to verify signature
Bug #964635 [src:electrum] electrum: FTBFS: dpkg-buildpackage: error:
dpkg-source -b . subprocess returned exit status 1
Changed Bug title to 'electrum: FTBFS: dpkg-so
Dear colleagues,
I made a mistake versioning Kodi packages in the unofficial repo.
Packages were versioned 19.0+git instead of 19.0~git so if there are other
people using my Github repo,
I advise removing Kodi with "apt autoremove kodi*" and re-installing it with
"apt update && apt install kodi"
Processing control commands:
> tags -1 help
Bug #952085 [src:ruby-invisible-captcha] ruby-invisible-captcha: FTBFS: ERROR:
Test "ruby2.5" failed: LoadError:
Added tag(s) help.
--
952085: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=952085
Debian Bug Tracking System
Contact ow...@bugs.debia
Control: tags -1 help
On Sun, 23 Feb 2020 08:45:32 +0100 Lucas Nussbaum
wrote:
> During a rebuild of all packages in sid, your package failed to build
> on amd64.
>
> Relevant part (hopefully):
> > LoadError:
> > cannot load such file -- rspec/rails
This looks like a failure started with ruby
Your message dated Sat, 18 Jul 2020 13:03:58 +
with message-id
and subject line Bug#964787: fixed in mrbayes 3.2.7a-3
has caused the Debian Bug report #964787,
regarding src:mrbayes: fails to migrate to testing for too long: unhandled RC
bug
to be marked as done.
This means that you claim th
Your message dated Sat, 18 Jul 2020 13:03:39 +
with message-id
and subject line Bug#961811: fixed in baresip 0.6.1-1.1
has caused the Debian Bug report #961811,
regarding baresip FTBFS with make 4.3
to be marked as done.
This means that you claim that the problem has been dealt with.
If this
Your message dated Sat, 18 Jul 2020 13:03:58 +
with message-id
and subject line Bug#958125: fixed in mrbayes 3.2.7a-3
has caused the Debian Bug report #958125,
regarding mrbayes: baseline violation on amd64 and i386
to be marked as done.
This means that you claim that the problem has been dea
On 17/07/2020 08:42, peter green wrote:
On 17/07/2020 06:40, Sebastian Ramacher wrote:
Hi
On 2020-07-17 00:02:17 +0100, peter green wrote:
(note: I am not the maintainer)
Sebastian Ramacher wrote:
I've prepared an NMU for baresip (versioned as 0.6.1-1.1) and
uploaded it to DELAYED/2.
While
Hey,
It took a bit of digging.
This is caused by an interaction between RT and GnuPG::Interface. I
believe that RT is using the GnuPG::Interface correctly.
GnuPG::Interface knows the version of the GPG binary being used, and
uses the --pinentry-mode argument if that is supported - which needs
gp
Your message dated Sat, 18 Jul 2020 12:34:32 +
with message-id
and subject line Bug#962881: fixed in postorius 1.3.2-2.1
has caused the Debian Bug report #962881,
regarding python3-django-postorius: should depend on fonts-font-awesome and/or
fonts-glyphicons-halflings (not fonts-glewlwyd)
to
Your message dated Sat, 18 Jul 2020 12:33:57 +
with message-id
and subject line Bug#962880: fixed in hyperkitty 1.3.2-1.1
has caused the Debian Bug report #962880,
regarding python3-django-hyperkitty: should depend on fonts-font-awesome and/or
fonts-glyphicons-halflings (not fonts-glewlwyd)
t
Your message dated Sat, 18 Jul 2020 12:05:07 +
with message-id
and subject line Bug#964685: fixed in libgphoto2 2.5.25-3
has caused the Debian Bug report #964685,
regarding libgphoto2: FTBFS: dpkg-gensymbols: error: some symbols or patterns
disappeared in the symbols file: see diff output bel
Your message dated Sat, 18 Jul 2020 11:30:08 +
with message-id
and subject line Bug#965013: fixed in quart 0.12.0-2
has caused the Debian Bug report #965013,
regarding quart FTBFS: no theme named 'pydata_sphinx_theme' found
to be marked as done.
This means that you claim that the problem has
Processing control commands:
> tags 962197 + pending
Bug #962197 [buildstream] buildstream: Event loop broken on Python 3.8
Added tag(s) pending.
> tags 962205 + patch
Bug #962205 [buildstream] buildstream: Missing dependency on bubblewrap
Added tag(s) patch.
> tags 962205 + pending
Bug #962205 [b
Processing control commands:
> tags 962197 + pending
Bug #962197 [buildstream] buildstream: Event loop broken on Python 3.8
Ignoring request to alter tags of bug #962197 to the same tags previously set
> tags 962205 + patch
Bug #962205 [buildstream] buildstream: Missing dependency on bubblewrap
Ig
Control: tags 962197 + pending
Control: tags 962205 + patch
Control: tags 962205 + pending
Dear maintainer,
I've prepared an NMU for buildstream (versioned as 1.4.3-0.1) and
uploaded it to DELAYED/15. Please feel free to tell me if I
should cancel it.
cu
Adrian
diff -Nru buildstream-1.4.1/builds
Processing commands for cont...@bugs.debian.org:
> notfound 965166 5.7.3
Bug #965166 [snmpd] snmpd privilege escalation
There is no source info for the package 'snmpd' at version '5.7.3' with
architecture ''
Unable to make a source version for version '5.7.3'
No longer marked as found in versions
54 matches
Mail list logo
