Source: lintian-brush
Version: 0.56
Severity: serious
Hello, looks like the new lintian removed one renamed tag in its latest version:
* Remove data/override/renamed-tags; they are defined in the tag
declarations now.
autopkgtest for lintian-brush/0.56: amd64: Regression ♻ , arm64:
On Fri, Jan 31, 2020 at 11:47:40AM +0100, Gianfranco Costamagna wrote:
> Source: lintian-brush
> Version: 0.56
> Severity: serious
>
> Hello, looks like the new lintian removed one renamed tag in its latest
> version:
> * Remove data/override/renamed-tags; they are defined in the tag
>
Your message dated Fri, 31 Jan 2020 11:19:10 +
with message-id
and subject line Bug#936617: fixed in git-publish 1.6.0-1
has caused the Debian Bug report #936617,
regarding git-publish: Python2 removal in sid/bullseye
to be marked as done.
This means that you claim that the problem has been
Your message dated Fri, 31 Jan 2020 11:49:25 +
with message-id
and subject line Bug#950321: fixed in lintian-brush 0.57
has caused the Debian Bug report #950321,
regarding lintian-brush: test failures with new lintian 2.48.0
to be marked as done.
This means that you claim that the problem
Your message dated Fri, 31 Jan 2020 12:04:20 +
with message-id
and subject line Bug#933642: fixed in devscripts 2.20.1
has caused the Debian Bug report #933642,
regarding devscripts: leaves multiple test/uscan/server.py processes running
after build
to be marked as done.
This means that you
Your message dated Fri, 31 Jan 2020 10:50:17 +
with message-id
and subject line Bug#938184: fixed in python-socksipychain 2.1.0-2
has caused the Debian Bug report #938184,
regarding python-socksipychain: Python2 removal in sid/bullseye
to be marked as done.
This means that you claim that the
Your message dated Fri, 31 Jan 2020 10:50:17 +
with message-id
and subject line Bug#948930: fixed in python-socksipychain 2.1.0-2
has caused the Debian Bug report #948930,
regarding python-socksipychain: autopkgtest regression: No module named
sockschain
to be marked as done.
This means
Your message dated Fri, 31 Jan 2020 10:50:17 +
with message-id
and subject line Bug#947812: fixed in python-socksipychain 2.1.0-2
has caused the Debian Bug report #947812,
regarding python3-socksipychain: missing Breaks+Replaces: python-socksipychain
to be marked as done.
This means that you
Your message dated Fri, 31 Jan 2020 12:04:20 +
with message-id
and subject line Bug#933642: fixed in devscripts 2.20.1
has caused the Debian Bug report #933642,
regarding src:devscripts: Rebuild hangs
to be marked as done.
This means that you claim that the problem has been dealt with.
If
Your message dated Fri, 31 Jan 2020 12:04:21 +
with message-id
and subject line Bug#945267: fixed in devscripts 2.20.1
has caused the Debian Bug report #945267,
regarding FTBFS: FAIL: test_pylint (devscripts.test.test_pylint.PylintTestCase)
to be marked as done.
This means that you claim
Your message dated Fri, 31 Jan 2020 10:04:16 +
with message-id
and subject line Bug#950262: fixed in python-cryptography 2.8-2
has caused the Debian Bug report #950262,
regarding version not update in autopkg test dependencies
to be marked as done.
This means that you claim that the problem
Dear Olivier,
On 24-01-2020 19:51, Debian Bug Tracking System wrote:
> Changes:
> lebiniou (3.40-1) unstable; urgency=low
[]
>* debian/tests/control: Fix Test-Command. (Closes: #947367)
How is ^^ going to fix a regression in the autopkgtest of lebinou-data?
the test command of lebinou
Source: libsvm
Version: 3.24+ds-2
X-Debbugs-CC: debian...@lists.debian.org
Severity: serious
User: debian...@lists.debian.org
Usertags: fails-always
Dear maintainers,
With a recent upload of libsvm you added an autopkgtest to libsvm,
great. However, it fails. I copied some of the output at the
On Fri, Jan 31, 2020 at 03:50:57AM +0100, Philippe Mathieu-Daudé wrote:
> On Thu, Jan 30, 2020 at 3:27 PM Jelmer Vernooij wrote:
> >
> > It looks like this package has been ported to Python 3, but has not
> > yet been uploaded. The last changelog entry on salsa
> >
Control: tag -1 pending
On 31.01.20 11:33, Paul Gevers wrote:
> Source: libsvm
> Version: 3.24+ds-2
> X-Debbugs-CC: debian...@lists.debian.org
> Severity: serious
> User: debian...@lists.debian.org
> Usertags: fails-always
>
> Dear maintainers,
>
> With a recent upload of libsvm you added an
Processing control commands:
> tag -1 pending
Bug #950317 [src:libsvm] libsvm: autopkgtest regression: test depends on
non-existing package svm-tools
Added tag(s) pending.
--
950317: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=950317
Debian Bug Tracking System
Contact
Processing commands for cont...@bugs.debian.org:
> limit source nipy
Limiting to bugs with field 'source' containing at least one of 'nipy'
Limit currently set to 'source':'nipy'
> tags 937143 + pending
Bug #937143 [src:nipy] nipy: Python2 removal in sid/bullseye
Added tag(s) pending.
> thanks
Hi,
the update to 1.6.8 fixes a somewhat serious bug that causes some
server-to-server mirroring setups (including mine …) to fail (without a
reasonable error message, to boot).
Thus I'd recommend not to delay the upload.
--
-- Matthias Urlichs
<>
signature.asc
Description: OpenPGP digital
Your message dated Fri, 31 Jan 2020 13:00:20 +
with message-id
and subject line Bug#937143: fixed in nipy 0.4.2-2.1
has caused the Debian Bug report #937143,
regarding nipy: Python2 removal in sid/bullseye
to be marked as done.
This means that you claim that the problem has been dealt with.
Your message dated Fri, 31 Jan 2020 13:00:27 +
with message-id
and subject line Bug#938892: fixed in zookeeper 3.4.13-4
has caused the Debian Bug report #938892,
regarding zookeeper: Python2 removal in sid/bullseye
to be marked as done.
This means that you claim that the problem has been
Processing control commands:
> severity -1 normal
Bug #950311 [src:fastqc] fastqc: autopkgtest regression: debhelper bump moved
files to different location
Severity set to 'normal' from 'serious'
> retitle -1 fastqc: FAIL strings in output - what does this mean?
Bug #950311 [src:fastqc] fastqc:
Control: severity -1 normal
Control: retitle -1 fastqc: FAIL strings in output - what does this mean?
Hi,
while I have uploaded a fixed autopkgtest which is now passing
I have not closed this bug. The log in testing[1] says:
...
+ gunzip example.fastq.gz
+ /usr/bin/fastqc example.fastq
Started
Source: nomacs
Version: 3.12.0+dfsg-2
Severity: serious
X-Debbugs-CC: s...@debian.org
Justification: ftbfs
Tags: ftbfs sid bullseye
Control: block 944396 by -1
Control: block 948638 by -1
Dear maintainer,
exiv2 started a transition and I scheduled binNMUs. However, your
package failed. Please
Processing control commands:
> block 944396 by -1
Bug #944396 [release.debian.org] transition: exiv2
944396 was blocked by: 950172 950171 950170 950169
944396 was not blocking any bugs.
Added blocking bug(s) of 944396: 950310
> block 948638 by -1
Bug #948638 [release.debian.org] transition:
Source: fastqc
Version: 0.11.9+dfsg-1
X-Debbugs-CC: debian...@lists.debian.org
Severity: serious
User: debian...@lists.debian.org
Usertags: regression
Dear maintainers,
With a recent upload of fastqc the autopkgtest of fastqc fails in
testing when that autopkgtest is run with the binary packages
Il giorno gio 30 gen 2020 alle ore 19:38 Michael Biebl
ha scritto:
>
>
> So you do have gsettings-desktop-schemas installed?
> Then I'm out of ideas why you get the crash.
> Maybe /usr/share/glib-2.0/schemas/gschemas.compiled is corrupt or not
> up-to-date. Dunno.
>
>
Yet installed ... Thanks
Processing control commands:
> severity -1 normal
Bug #949385 [cacti] cacti: Cacti fails under PHP-FPM
Severity set to 'normal' from 'grave'
> retitle -1 cacti doesn't work with php-7.4
Bug #949385 [cacti] cacti: Cacti fails under PHP-FPM
Changed Bug title to 'cacti doesn't work with php-7.4'
Control: severity -1 normal
Control: retitle -1 cacti doesn't work with php-7.4
Hi Adam,
On 31-01-2020 04:15, Adam Thompson wrote:
> The reason we’re running php-7.4 is because I screwed up; I enabled the
> entire backports repo instead of selecting individual packages from it
I still don't
Source: debci
Version: 2.7
Severity: serious
User: debian...@lists.debian.org
Usertags: regression
Dear maintainers,
With a recent upload of debci the autopkgtest of debci fails in testing
when that autopkgtest is run with the binary packages of debci from
unstable. It passes when run with only
Control: tags -1 + patch
Dear maintainer,
The attached patches port the build system to Python 3. The package seems to
build OK using them but I don't know enough about this package to test them
further and there are no autopkgtest tests to verify that the package is OK.
regards
Stuart
--
Processing control commands:
> tags -1 + patch
Bug #937144 [src:nipype] nipype: Python2 removal in sid/bullseye
Added tag(s) patch.
--
937144: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=937144
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
Source: python-pbcore
Version: 1.7.1+git20191121.7947eb7+dfsg-3
Severity: serious
Control: block 946602 with -1
Hi,
pyxb has been requested to be removed (#946602):
On Wed, 11 Dec 2019 18:11:57 +0100 Michael Fladischer
wrote:
> pyxb has two RC bugs and does not work with Python 3.8. It has
Processing control commands:
> block 946602 with -1
Bug #946602 [ftp.debian.org] RM: pyxb -- ROM; RC-buggy; abandoned upstream
946602 was not blocked by any bugs.
946602 was not blocking any bugs.
Added blocking bug(s) of 946602: 950336
--
946602:
Source: rust-num-traits
Version: 0.2.11-1
Severity: serious
Tags: ftbfs
Justification: fails to build from source (but built successfully in the past)
Control: block 949798 with -1
Hi,
rust-num-traits FTBFS on mipsel and mips64el:
Processing control commands:
> block 949798 with -1
Bug #949798 [ftp.debian.org] RM: rust-rand-0.5 -- ROM; No longer used by any
other package
949798 was not blocked by any bugs.
949798 was not blocking any bugs.
Added blocking bug(s) of 949798: 950337
--
949798:
Processing control commands:
> block 902180 with -1
Bug #902180 [ftp.debian.org] RM: golang-github-docker-engine-api -- ROM;
obsolete
902180 was blocked by: 950343
902180 was not blocking any bugs.
Added blocking bug(s) of 902180: 950345
--
902180:
Your message dated Fri, 31 Jan 2020 15:19:24 +
with message-id
and subject line Bug#950036: fixed in python-bashate 0.6.0-4
has caused the Debian Bug report #950036,
regarding python-bashate FTBFS: Can't exec "pyversions": No such file or
directory
to be marked as done.
This means that you
Processing control commands:
> block 902180 with -1
Bug #902180 [ftp.debian.org] RM: golang-github-docker-engine-api -- ROM;
obsolete
902180 was not blocked by any bugs.
902180 was not blocking any bugs.
Added blocking bug(s) of 902180: 950343
--
902180:
Processing commands for cont...@bugs.debian.org:
> severity 948555 normal
Bug #948555 [ftp.debian.org] RM: python-soappy -- RoQA; python2-only; leaf
package; upstream suggests to use 'suds'; better alternatives exist
Severity set to 'normal' from 'serious'
> severity 950133 important
Bug #950133
Control: tag -1 pending
Hello,
Bug #949027 in node-srs 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 #949027 [src:node-srs] node-srs: uses old python to build
Added tag(s) pending.
--
949027: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=949027
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
Package: kubectx
Version: 0.6.3-2
Severity: serious
Control: block 950247 with -1
Hi,
the kubernetes package has been requested to be removed (#950247), but
kubectx still build-depends on it.
Please find a solution.
Andreas
Processing control commands:
> block 950247 with -1
Bug #950247 [ftp.debian.org] RM: kubernetes -- RoQA; Unmaintained and RC buggy
950247 was not blocked by any bugs.
950247 was not blocking any bugs.
Added blocking bug(s) of 950247: 950341
--
950247:
X-Debbugs-Cc: kilob...@angband.pl, Gürkan Myczko
Source: powder
Source-Version: 118+dfsg1-2
Severity: serious
The maintainer address is invalid, see below.
Ansgar
Forwarded Message
This message was created automatically by mail delivery software.
>
> A message that you sent
Source: volatility
Severity: serious
Hello,
this is a temporary RC bug to prevent volatility to get into testing, see
https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=938797#46 for maintainer's
ack.
this can be closed when volatility3 (python3 port of volatility) has been
packaged and
Source: golang-github-aanand-compose-file
Version: 0.0~git20161122.0.a3e5876-1
Severity: serious
Tags: sid bullseye
Control: block 902180 with -1
Hi,
the src:golang-github-docker-engine-api package has been requested to be
removed, but golang-github-aanand-compose-file still build-depends on
Your message dated Fri, 31 Jan 2020 16:20:15 +
with message-id
and subject line Bug#950336: fixed in python-pbcore
1.7.1+git20200129.c55621e+dfsg-1
has caused the Debian Bug report #950336,
regarding python-pbcore: build-depends on python3-pyxb which has been requested
to be removed
to be
Your message dated Fri, 31 Jan 2020 16:20:58 +
with message-id
and subject line Bug#947208: fixed in youtube-dl 2020.01.24-0.1
has caused the Debian Bug report #947208,
regarding youtube-dl 2019.11.28 is available
to be marked as done.
This means that you claim that the problem has been
Dear maintainer,
That first set of patches was obviously misdirected... sorry.
The attached patches port nipype to Python 3 and stop making a Python 2
module.
However:
* I can't successfully build the package due to the debian/patches/
deb_git_hash. If I leave that in then dpkg-source cannot
Processing control commands:
> tag -1 pending
Bug #950048 [src:python-os-xenapi] python-os-xenapi FTBFS: Can't exec
"pyversions"
Added tag(s) pending.
--
950048: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=950048
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
Control: tag -1 pending
Hello,
Bug #950048 in python-os-xenapi 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:
Control: tag -1 pending
Hello,
Bug #950047 in python-glareclient 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 #950047 [src:python-glareclient] python-glareclient FTBFS: Can't exec
"pyversions"
Added tag(s) pending.
--
950047: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=950047
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
Processing commands for cont...@bugs.debian.org:
> severity 949693 important
Bug #949693 [php-guzzlehttp-psr7] Missing autoload.php
Severity set to 'important' from 'serious'
> thanks
Stopping processing here.
Please contact me if you need assistance.
--
949693:
severity 949693 important
thanks
The code’s there, and not every user uses the autoloader.
Forcing other unaffected packages out of testing for this
is a bit overkill.
bye,
//mirabilos
--
Thorsten Glaser (Gründungsmitglied)
Teckids e.V. — Digitale Freiheit mit Jugend und Bildung
Processing control commands:
> tag -1 pending
Bug #950044 [src:python-seamicroclient] python-seamicroclient FTBFS:
testr-python3 not found
Added tag(s) pending.
--
950044: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=950044
Debian Bug Tracking System
Contact ow...@bugs.debian.org with
Control: tag -1 pending
Hello,
Bug #950044 in python-seamicroclient 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:
Your message dated Fri, 31 Jan 2020 15:50:24 +
with message-id
and subject line Bug#950047: fixed in python-glareclient 0.5.3-5
has caused the Debian Bug report #950047,
regarding python-glareclient FTBFS: Can't exec "pyversions"
to be marked as done.
This means that you claim that the
Your message dated Fri, 31 Jan 2020 15:50:40 +
with message-id
and subject line Bug#950048: fixed in python-os-xenapi 0.3.4-3
has caused the Debian Bug report #950048,
regarding python-os-xenapi FTBFS: Can't exec "pyversions"
to be marked as done.
This means that you claim that the problem
Your message dated Fri, 31 Jan 2020 15:50:50 +
with message-id
and subject line Bug#950044: fixed in python-seamicroclient
0.4.0+2016.05.20.git.40ee44c664-3
has caused the Debian Bug report #950044,
regarding python-seamicroclient FTBFS: testr-python3 not found
to be marked as done.
This
Your message dated Fri, 31 Jan 2020 15:50:57 +
with message-id
and subject line Bug#950046: fixed in python-sphinx-feature-classification
0.3.2-3
has caused the Debian Bug report #950046,
regarding python-sphinx-feature-classification FTBFS: unable to load addon
python2
to be marked as
Hi Olivier,
On 31-01-2020 15:07, Olivier Girondel wrote:
> This should have been fixed in a recent upload of lebiniou-data-3.40:
>
> https://sources.debian.org/src/lebiniou-data/3.40-1/debian/tests/control/
>
> But if tests still fail, feel free to reopen.
Is lebiniou-data used for anything
Your message dated Fri, 31 Jan 2020 16:35:42 +
with message-id
and subject line Bug#877496: fixed in sexplib310 1:0.13.0-1
has caused the Debian Bug report #877496,
regarding sexplib310 FTBFS: Error: This expression has type Obj.t but an
expression was expected of type extension_constructor
On 1/31/20 11:04 AM, Paul Gevers wrote:
> Dear Olivier,
>
> On 24-01-2020 19:51, Debian Bug Tracking System wrote:
>> Changes:
>> lebiniou (3.40-1) unstable; urgency=low
>
> []
>
>>* debian/tests/control: Fix Test-Command. (Closes: #947367)
>
> How is ^^ going to fix a regression in
Processing control commands:
> tag -1 pending
Bug #950036 [src:python-bashate] python-bashate FTBFS: Can't exec "pyversions":
No such file or directory
Added tag(s) pending.
--
950036: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=950036
Debian Bug Tracking System
Contact
Control: tag -1 pending
Hello,
Bug #950036 in python-bashate 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:
Source: docker-swarm
Version: 1.2.5+dfsg-2
Severity: serious
Control: block 902180 with -1
Hi,
the src:golang-github-docker-engine-api package has been requested to be
removed, but docker-swarm still build-depends on
golang-github-docker-engine-api-dev.
Please find a solution.
Andreas
Hi, Andreas.
Andreas Tille writes:
> I think that's just a matter of setting $HOME to something sensible and
> is probably less than 10min work for you. Could you please take over
> from here?
Thanks for calling this report to my attention; I don't follow
debian-med-packaging as a whole, and
Your message dated Fri, 31 Jan 2020 17:37:38 +
with message-id
and subject line Bug#938469: fixed in serpent 1.30-1
has caused the Debian Bug report #938469,
regarding serpent: Python2 removal in sid/bullseye
to be marked as done.
This means that you claim that the problem has been dealt
On 31/01/20 19:22, Gianfranco Costamagna wrote:
> Source: python-netaddr
> Version: 0.7.19-2
> Severity: serious
> Tags: patch
>
> Hello, please update the build dependency from python (scheduled for removal)
> to python-all, to fix the future/ongoing transition.
>
> ---
Processing control commands:
> tags -1 +confirmed -moreinfo
Bug #950309 [release.debian.org] stretch-pu: package mariadb-10.1
10.1.44-0+deb9u1
Added tag(s) confirmed.
Bug #950309 [release.debian.org] stretch-pu: package mariadb-10.1
10.1.44-0+deb9u1
Removed tag(s) moreinfo.
> severity -1 normal
Control: tags -1 +confirmed -moreinfo
Control: severity -1 normal
On Fri, 2020-01-31 at 10:32 +0200, Otto Kekäläinen wrote:
> Package: release.debian.org
> Severity: serious
Nope.
> Tags: stretch, moreinfo
Filing the request with "moreinfo" is an interesting choice. :-)
> User:
On Fri, Jan 31, 2020 at 1:06 PM Marek Marczykowski-Górecki
wrote:
>
> On Thu, Jan 30, 2020 at 05:40:55PM -0800, Mike Miller wrote:
> > On Thu, Jan 30, 2020 at 01:36:33 -0500, Sandro Tosi wrote:
> > > yep i came across all of them starting from python-lzma -- do you know
> > > what's the status of
On Thu, Jan 30, 2020 at 05:40:55PM -0800, Mike Miller wrote:
> On Thu, Jan 30, 2020 at 01:36:33 -0500, Sandro Tosi wrote:
> > yep i came across all of them starting from python-lzma -- do you know
> > what's the status of the "RedHat infrastructure" in debian? many (if
> > not all) of those tools
Your message dated Fri, 31 Jan 2020 17:23:23 +
with message-id
and subject line Bug#948299: fixed in osc-plugins-dput 20200114+git05dae35-1
has caused the Debian Bug report #948299,
regarding osc-plugins-dput: Doesn't work with Python 3 version of osc
to be marked as done.
This means that
Source: python-netaddr
Version: 0.7.19-2
Severity: serious
Tags: patch
Hello, please update the build dependency from python (scheduled for removal)
to python-all, to fix the future/ongoing transition.
--- python-netaddr-0.7.19/debian/control2020-01-29 15:37:58.0
+0100
+++
On Fri, Jan 31, 2020 at 2:27 PM Sandro Tosi wrote:
>
> On Fri, Jan 31, 2020 at 1:06 PM Marek Marczykowski-Górecki
> wrote:
> >
> > On Thu, Jan 30, 2020 at 05:40:55PM -0800, Mike Miller wrote:
> > > On Thu, Jan 30, 2020 at 01:36:33 -0500, Sandro Tosi wrote:
> > > > yep i came across all of them
Processing commands for cont...@bugs.debian.org:
> tags 938758 + fixed-upstream
Bug #938758 [src:urlgrabber] urlgrabber: Python2 removal in sid/bullseye
Ignoring request to alter tags of bug #938758 to the same tags previously set
> thanks
Stopping processing here.
Please contact me if you need
Hi,
On Fri, Jan 31, 2020 at 10:59:05PM +0200, Adrian Bunk wrote:
> Source: radare2
> Severity: grave
> Tags: security
>
> It is understandable (and normal for most software) that upstream
> is not able or willing to provide security support for the old
> version shipped in stable distribution
Source: apertium-en-es
Version: 0.8.0~r57502-4
Severity: serious
Tags: ftbfs bullseye sid
https://tests.reproducible-builds.org/debian/rb-pkg/unstable/amd64/apertium-en-es.html
...
apertium-preprocess-transfer apertium-en-es.en-es.t2x en-es.t2x.bin
Warning (785): Paths to rule 5 blocked by rule
Source: apertium-eu-es
Version: 0.3.3~r56159-3
Severity: serious
Tags: ftbfs bullseye sid
https://tests.reproducible-builds.org/debian/rb-pkg/unstable/amd64/apertium-eu-es.html
...
apertium-preprocess-transfer apertium-eu-es.eu-es.t2x eu-es.t2x.bin
main@standard 69 144
Warning (3802): Paths to
Processing control commands:
> reassign -1 python3-sphinx-astropy
Bug #949464 [src:gwcs] the gwcs build accesses the network during the build
Bug reassigned from package 'src:gwcs' to 'python3-sphinx-astropy'.
No longer marked as found in versions gwcs/0.12.0-3.
Ignoring request to alter fixed
Source: apertium-eu-en
Version: 0.3.1~r56205-2
Severity: serious
Tags: ftbfs bullseye sid
https://tests.reproducible-builds.org/debian/rb-pkg/unstable/amd64/apertium-eu-en.html
...
apertium-gen-modes modes.xml
apertium-preprocess-transfer apertium-eu-en.eu-en.t1x eu-en.t1x.bin
Warning (3830):
Control: reassign -1 python3-sphinx-astropy
Control: tags -1 patch
(untested)
(If reading this in the bug, see
https://lists.debian.org/debian-mentors/2020/01/msg00295.html.)
An intersphinx_mapping can specify multiple alternatives for where to
find the inventory referred to, and these can
Source: apertium-cy-en
Version: 0.1.1~r57554-4
Severity: serious
Tags: ftbfs bullseye sid
https://tests.reproducible-builds.org/debian/rb-pkg/unstable/amd64/apertium-cy-en.html
...
apertium-validate-transfer apertium-cy-en.cy-en.t1x
apertium-preprocess-transfer apertium-cy-en.cy-en.t1x
Source: apertium-eo-fr
Version: 0.9.0~r57551-2
Severity: serious
Tags: ftbfs bullseye sid
https://tests.reproducible-builds.org/debian/rb-pkg/unstable/amd64/apertium-eo-fr.html
...
Warning (31015): Paths to rule 319 blocked by rule 281.
Warning (31015): Paths to rule 319 blocked by rule 281.
Source: apertium-br-fr
Version: 0.5.0~r61325-3
Severity: serious
Tags: ftbfs bullseye sid
https://tests.reproducible-builds.org/debian/rb-pkg/unstable/amd64/apertium-br-fr.html
...
apertium-validate-dictionary apertium-br-fr.post-fr.dix
lt-comp lr apertium-br-fr.post-fr.dix br-fr.autopgen.bin
Source: apertium-mk-en
Version: 0.1.1~r57554-2
Severity: serious
Tags: ftbfs bullseye sid
https://tests.reproducible-builds.org/debian/rb-pkg/unstable/amd64/apertium-mk-en.html
...
make -j16
make[1]: Entering directory '/build/1st/apertium-mk-en-0.1.1~r57554'
apertium-validate-dictionary
Hi Aaron,
On Fri, Jan 31, 2020 at 02:40:41PM -0500, Aaron M. Ucko wrote:
> > I think that's just a matter of setting $HOME to something sensible and
> > is probably less than 10min work for you. Could you please take over
> > from here?
>
> Thanks for calling this report to my attention; I
Processing commands for cont...@bugs.debian.org:
> tags 947005 + fixed-upstream
Bug #947005 [src:nethack] nethack: CVE-2019-19905: buffer overflow when parsing
config files
Added tag(s) fixed-upstream.
> thanks
Stopping processing here.
Please contact me if you need assistance.
--
947005:
Processing commands for cont...@bugs.debian.org:
> forwarded 948128 https://github.com/pulb/mailnag-gnome-shell/pull/58
Bug #948128 [src:gnome-shell-mailnag] gnome-shell-mailnag FTBFS: vala error:
syntax error, invalid array parameter declaration
Set Bug forwarded-to-address to
Your message dated Fri, 31 Jan 2020 15:42:46 -0500
with message-id <7147ddf5e60fde9a1d6a4c703e5ee6e4345fd885.ca...@debian.org>
and subject line Re: Bug#950103: fonts-lemonada FTBFS: KeyError: "glyph 'M'
already exists"
has caused the Debian Bug report #950103,
regarding fonts-lemonada FTBFS:
Source: apertium-es-pt
Version: 1.1.5+svn~57507-4
Severity: serious
Tags: ftbfs bullseye sid
https://tests.reproducible-builds.org/debian/rb-pkg/unstable/amd64/apertium-es-pt.html
...
lt-comp lr apertium-es-pt.post-es.dix pt-es.autopgen.bin
apertium-gen-modes modes.xml
Source: apertium-isl-eng
Version: 0.1.0~r66083-2
Severity: serious
Tags: ftbfs bullseye sid
https://tests.reproducible-builds.org/debian/rb-pkg/unstable/amd64/apertium-isl-eng.html
...
xsltproc lexchoicebil.xsl apertium-isl-eng.isl-eng.dix >
.deps/apertium-isl-eng.isl-eng.dix
Source: apertium-id-ms
Version: 0.1.1~r57551-2
Severity: serious
Tags: ftbfs bullseye sid
https://tests.reproducible-builds.org/debian/rb-pkg/unstable/amd64/apertium-id-ms.html
...
make -j16
make[1]: Entering directory '/build/1st/apertium-id-ms-0.1.1~r57551'
make all-am
make[2]: Entering
Your message dated Fri, 31 Jan 2020 23:08:11 +
with message-id
and subject line Bug#950362: fixed in python-netaddr 0.7.19-3
has caused the Debian Bug report #950362,
regarding python-netaddr: needs adjustment for python-all
to be marked as done.
This means that you claim that the problem
On Fri, Jan 03, 2020 at 12:23:34AM +, Samuel Henrique wrote:
> As said by upstream at:
> https://github.com/aircrack-ng/aircrack-ng/pull/2087
>
> The issue is fixed in git and there' s gonna be a new release soon.
>
> Sending this mail to reset the auto-rm clock so we can wait for the new
>
Source: radare2
Severity: grave
Tags: security
It is understandable (and normal for most software) that upstream
is not able or willing to provide security support for the old
version shipped in stable distribution releases.
But below seems to be upstream actively encouraging exploiting
the
Source: apertium-es-ast
Version: 1.1.0~r51165-2
Severity: serious
Tags: ftbfs bullseye sid
https://tests.reproducible-builds.org/debian/rb-pkg/unstable/amd64/apertium-es-ast.html
...
make all-am
make[2]: Entering directory '/build/1st/apertium-es-ast-1.1.0~r51165'
apertium-validate-dictionary
On Fri, Jan 31, 2020 at 10:10:38PM +0100, Salvatore Bonaccorso wrote:
> Hi,
>
> On Fri, Jan 31, 2020 at 10:59:05PM +0200, Adrian Bunk wrote:
> > Source: radare2
> > Severity: grave
> > Tags: security
> >
> > It is understandable (and normal for most software) that upstream
> > is not able or
1 - 100 of 118 matches
Mail list logo
