Processing control commands:
> tag -1 pending
Bug #943526 [node-typescript] node-tslib: directory vs. symlink conflict:
/usr/share/nodejs/tslib
Added tag(s) pending.
--
943526: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=943526
Debian Bug Tracking System
Contact ow...@bugs.debian.org
Control: tag -1 pending
Hello,
Bug #943526 in node-typescript 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 Mon, 04 Nov 2019 07:45:27 +
with message-id
and subject line Bug#944082: Removed package(s) from unstable
has caused the Debian Bug report #938556,
regarding sqlkit: Python2 removal in sid/bullseye
to be marked as done.
This means that you claim that the problem has been
Your message dated Mon, 04 Nov 2019 07:45:27 +
with message-id
and subject line Bug#944082: Removed package(s) from unstable
has caused the Debian Bug report #885470,
regarding sqlkit: Depends on unmaintained pygtk
to be marked as done.
This means that you claim that the problem has been
Your message dated Mon, 04 Nov 2019 07:44:58 +
with message-id
and subject line Bug#944080: Removed package(s) from unstable
has caused the Debian Bug report #936107,
regarding activity-log-manager: Python2 removal in sid/bullseye
to be marked as done.
This means that you claim that the
Your message dated Mon, 04 Nov 2019 07:44:58 +
with message-id
and subject line Bug#944080: Removed package(s) from unstable
has caused the Debian Bug report #942624,
regarding src:activity-log-manager: Maintainer email address not working
to be marked as done.
This means that you claim that
Your message dated Mon, 04 Nov 2019 07:44:58 +
with message-id
and subject line Bug#944080: Removed package(s) from unstable
has caused the Debian Bug report #885256,
regarding activity-log-manager: Depends on unmaintained pygtk
to be marked as done.
This means that you claim that the
Your message dated Mon, 04 Nov 2019 07:44:34 +
with message-id
and subject line Bug#944079: Removed package(s) from unstable
has caused the Debian Bug report #936443,
regarding driconf: Python2 removal in sid/bullseye
to be marked as done.
This means that you claim that the problem has been
Your message dated Mon, 04 Nov 2019 07:44:58 +
with message-id
and subject line Bug#944080: Removed package(s) from unstable
has caused the Debian Bug report #939103,
regarding activity-log-manager: Python2 removal in sid/bullseye -- drop
python-distutils-extra build dependency
to be marked
Your message dated Mon, 04 Nov 2019 07:44:34 +
with message-id
and subject line Bug#944079: Removed package(s) from unstable
has caused the Debian Bug report #885276,
regarding driconf: Depends on unmaintained pygtk
to be marked as done.
This means that you claim that the problem has been
Your message dated Mon, 04 Nov 2019 06:04:21 +
with message-id
and subject line Bug#942417: fixed in kmymoney 5.0.7-1
has caused the Debian Bug report #942417,
regarding Please update to 5.0.7 so KMyMoney can be built with AqBanking 6
to be marked as done.
This means that you claim that the
Your message dated Mon, 04 Nov 2019 02:41:08 +
with message-id
and subject line Bug#943516: fixed in valinor 1.1.4-2
has caused the Debian Bug report #943516,
regarding valinor: FTBFS and autopkgtest failure due to new version of
python-colorama
to be marked as done.
This means that you
Oops!!! Sorry, I reverted the change
Cheers,
Arias Emmanuel
@eamanu
http://eamanu.com
El dom., 3 de nov. de 2019 a la(s) 19:49, Drew Parsons
(dpars...@debian.org) escribió:
>
> On 2019-11-04 01:15, Emmanuel Arias wrote:
> > Hi,
> >
> > I've just prepare the new upstream release (for some reason
Processing commands for cont...@bugs.debian.org:
> reassign 943663 ftp.debian.org
Bug #943663 [src:pyviennacl] pyviennacl: should this package be removed?
Bug reassigned from package 'src:pyviennacl' to 'ftp.debian.org'.
Ignoring request to alter found versions of bug #943663 to the same values
On 2019-11-02 07:01:43, Mike Gabriel wrote:
> Hi Antoine,
>
> On Sa 02 Nov 2019 00:10:38 CET, anarcat wrote:
>
>> Control: tags 942114 + pending
>>
>> Dear maintainer,
>>
>> I've prepared an NMU for ganeti-instance-debootstrap (versioned as
>> 0.16-6.1) and
>> uploaded it to DELAYED/02. Please
Your message dated Sun, 03 Nov 2019 23:34:48 +
with message-id
and subject line Bug#942114: fixed in ganeti-instance-debootstrap 0.16-6.1
has caused the Debian Bug report #942114,
regarding cache fails to store capabilities correctly
to be marked as done.
This means that you claim that the
On 2019-11-04 01:15, Emmanuel Arias wrote:
Hi,
I've just prepare the new upstream release (for some reason
the upstream branch was not merge to master). [1]
Emmanuel, the work-in-progress is in the experimental branch. Push to
experimental first before pulling into master.
Drew
Processing commands for cont...@bugs.debian.org:
> tags 942417 + pending
Bug #942417 [src:kmymoney] Please update to 5.0.7 so KMyMoney can be built with
AqBanking 6
Added tag(s) pending.
> thanks
Stopping processing here.
Please contact me if you need assistance.
--
942417:
Your message dated Sun, 03 Nov 2019 22:23:21 +
with message-id
and subject line Bug#943960: fixed in python-livereload 2.6.1-3
has caused the Debian Bug report #943960,
regarding python-livereload autopkgtest depends on python-django which isn't
build from source anymore
to be marked as
Your message dated Sun, 03 Nov 2019 22:23:21 +
with message-id
and subject line Bug#937895: fixed in python-livereload 2.6.1-3
has caused the Debian Bug report #937895,
regarding python-livereload: Python2 removal in sid/bullseye
to be marked as done.
This means that you claim that the
Processing control commands:
> severity -1 serious
Bug #942417 [src:kmymoney] Please update to 5.0.7 so KMyMoney can be built with
AqBanking 6
Severity set to 'serious' from 'wishlist'
--
942417: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=942417
Debian Bug Tracking System
Contact
Your message dated Sun, 03 Nov 2019 20:45:37 +
with message-id
and subject line Bug#941522: fixed in gawk-doc 5.0.1-1
has caused the Debian Bug report #941522,
regarding gawk-doc: build-depend on texlive-plain-generic, not obsolete
texlive-generic-recommended
to be marked as done.
This
Did you investigate anything suggested in
https://forum.manjaro.org/t/computer-does-not-shut-down-because-of-mariadb/81565
?
Did you figure it out?
Processing control commands:
> found -1 tryton-proteus/5.0.4-1
Bug #944074 [src:tryton-proteus, src:tryton-modules-account-fr] tryton-proteus
breaks tryton-modules-account-fr autopkgtest: Doctest: scenario_fec.rst ... FAIL
Marked as found in versions tryton-proteus/5.0.4-1.
> found -1
Source: tryton-proteus, tryton-modules-account-fr
Control: found -1 tryton-proteus/5.0.4-1
Control: found -1 tryton-modules-account-fr/5.0.1-2
Severity: serious
Tags: sid bullseye
X-Debbugs-CC: debian...@lists.debian.org
User: debian...@lists.debian.org
Usertags: breaks needs-update
Dear
Source: tryton-proteus, tryton-modules-purchase-request
Control: found -1 tryton-proteus/5.0.4-1
Control: found -1 tryton-modules-purchase-request/5.0.2-2
Severity: serious
Tags: sid bullseye
X-Debbugs-CC: debian...@lists.debian.org
User: debian...@lists.debian.org
Usertags: breaks needs-update
Processing control commands:
> found -1 tryton-proteus/5.0.4-1
Bug #944073 [src:tryton-proteus, src:tryton-modules-purchase-request]
tryton-proteus breaks tryton-modules-purchase-request autopkgtest:
trytond.exceptions.UserError: ('UserError', ('Purchase requests are only
created by the
Source: tlsh
Version: 3.4.4+20151206-1.2
Severity: serious
X-Debbugs-CC: debian...@lists.debian.org, mo...@debian.org
User: debian...@lists.debian.org
Usertags: regression
Dear maintainers,
With a recent upload of tlsh the autopkgtest of tlsh fails in testing
when that autopkgtest is run with
Package: iwd
Version: 1.0-1
Severity: serious
This bug report was opened to temporarily prevent iwd 1.0 from migrating
to testing to give NetworkManager some time to catch up.
Regards,
Andreas Henriksson
Package: exim4-daemon-light
Version: 4.93~RC0-1
Severity: serious
Tags: ftbfs
Justification: fails to build from source (but built successfully in the past)
4.93~RC0-1 and later (including 4.93~RC1-2) FTBFS on mipsel, the binary
is built but broken.
/path/to/exim -C /dev/null -be '${if
Your message dated Sun, 03 Nov 2019 17:33:52 +
with message-id
and subject line Bug#943995: fixed in cu2qu 1.6.6-5
has caused the Debian Bug report #943995,
regarding cu2qu: missing python3-all-dev dependency (patch)
to be marked as done.
This means that you claim that the problem has been
The test failures are:
armhf: 86, probably all #924036
i386: 1, TestDFM_Approx.test_smoothed_measurement_disturbance out of
tolerance: suspect rounding error (x87 extra precision).
arm64, ppc64el, s390x: the same 3,
base.tests.test_penalized.TestPenalizedPoissonOraclePenalized2*: looks
Hi Simon, and all others,
First: thanks for all your work and energy putted in into resolving
this issue.
On Wed, Oct 30, 2019 at 03:04:26PM +, Simon McVittie wrote:
> On Wed, 30 Oct 2019 at 15:45:19 +0100, Gunnar Hjalmarsson wrote:
> > Seeing that you included quite a few patches in this
Hi,
I've just prepare the new upstream release (for some reason
the upstream branch was not merge to master). [1]
But is necessary some work with patches, are failing.
I can work on it tomorrow.
[1] https://salsa.debian.org/python-team/modules/dask
Cheers,
Arias Emmanuel
@eamanu
Processing commands for cont...@bugs.debian.org:
> forcemerge 942553 944038
Bug #942553 [gpsd] gpsd: does not ship a sysvinit script
Bug #944038 [gpsd] gpsd missing sysvinit script and breaks functionality on
upgrade
Severity set to 'wishlist' from 'serious'
Added tag(s) wontfix.
Merged 942553
Processing commands for cont...@bugs.debian.org:
> unmerge 926528
Bug #926528 [collectd] libgps changed API of gps_read
Ignoring request to unmerge a bug which is not merged with any others.
> thanks
Stopping processing here.
Please contact me if you need assistance.
--
926528:
Processing commands for cont...@bugs.debian.org:
> forcemerge 942553 926528
Bug #942553 [gpsd] gpsd: does not ship a sysvinit script
Unable to merge bugs because:
package of #926528 is 'collectd' not 'gpsd'
Failed to forcibly merge 942553: Did not alter merged bugs.
> thanks
Stopping processing
Hi,
> Justification: Breaks silently functionality on upgrade
not if you'd use the default init system.
> In my setup, gpsd is required to start at system boot with a sysv
> init.
That is not supported by the gpsd upstream anymore, all the
hotplugging/udev rules require systemd (which makes a
Your message dated Sun, 03 Nov 2019 14:41:29 +
with message-id
and subject line Bug#943812: fixed in sopt 3.0.1-9
has caused the Debian Bug report #943812,
regarding libsopt-dev: missing dependency on libopenmpi-dev
to be marked as done.
This means that you claim that the problem has been
Processing commands for cont...@bugs.debian.org:
> reassign 943468 src:php7.3 7.3.10-1
Bug #943468 [php7.3-fpm] php-fpm: CVE-2019-11043: Vulnerability in PHP-FPM
Could Lead to Remote Code Execution on nginx
Bug reassigned from package 'php7.3-fpm' to 'src:php7.3'.
Ignoring request to alter found
it looks to me that python-xarray 0.14 needs a newer dask version as well.
Processing control commands:
> forwarded -1 https://github.com/linbox-team/linbox/issues/238
Bug #944055 [src:linbox] linbox ftbfs on armhf, bus errors in the test suite
Set Bug forwarded-to-address to
'https://github.com/linbox-team/linbox/issues/238'.
--
944055:
Control: forwarded -1 https://github.com/linbox-team/linbox/issues/238
On Sun, Nov 3, 2019 at 8:57 AM Matthias Klose
mailto:d...@debian.org>> wrote:
linbox ftbfs on armhf, bus errors in the test suite, like
../build-aux/test-driver: line 107: 21585 Bus error "$@" >
$log_file 2>&1
Package: src:linbox
Version: 1.6.3-1
Severity: serious
Tags: sid bullseye
linbox ftbfs on armhf, bus errors in the test suite, like
../build-aux/test-driver: line 107: 21585 Bus error "$@" >
$log_file 2>&1
FAIL: test-smith-form-valence
the builders are now machines with 64bit
Package: python3-statsmodels
Version: 0.10.1-1
Control: fixed -1 0.9.0-6
Severity: serious
While making statsmodels clean up after its tests, I accidentally also
made it ignore failed tests.
Some tests did fail on at least ppc64el and s390x; I don't yet know if
these are actually a serious
Processing control commands:
> fixed -1 0.9.0-6
Bug #944054 [python3-statsmodels] statsmodels: ignored test failures on at
least ppc64el
Marked as fixed in versions statsmodels/0.9.0-6.
--
944054: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=944054
Debian Bug Tracking System
Contact
Control: tags -1 patch
Attached seems to work for me.
>From 1d55037aa0644b42c25f40caea708c90280ee140 Mon Sep 17 00:00:00 2001
From: Andreas Metzler
Date: Sun, 3 Nov 2019 06:45:49 +0100
Subject: [PATCH 1/2] Build with -DLOCAL_SCAN.
---
debian/changelog | 7 +++
debian/rules | 2 +-
2
Processing control commands:
> tags -1 patch
Bug #943571 [sa-exim] sa-exim: Does not work with exim 4.93
Added tag(s) patch.
--
943571: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=943571
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
Processing commands for cont...@bugs.debian.org:
> retitle 933832 enigmail: please package new version 2.1.x
Bug #933832 [enigmail] enigmail: please package new version 2.1
Changed Bug title to 'enigmail: please package new version 2.1.x' from
'enigmail: please package new version 2.1'.
> thanks
Processing commands for cont...@bugs.debian.org:
> retitle 933832 enigmail: please package new version 2.1
Bug #933832 [enigmail] Please package new version 2.1.2 into experimental
Changed Bug title to 'enigmail: please package new version 2.1' from 'Please
package new version 2.1.2 into
Control: reopen -1
Hi Ole,
On Fri, Nov 01, 2019 at 12:21:08PM +, Debian Bug Tracking System wrote:
>* Add libopenmpi-dev build dependency (Closes: #943812)
It's nice that you add a build dependency on libopenmpi-dev, but that's
unrelated to the bug #943812 at hand, which was about a
Processing control commands:
> reopen -1
Bug #943812 {Done: Ole Streicher } [libsopt-dev]
libsopt-dev: missing dependency on libopenmpi-dev
'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
Processing control commands:
> severity -1 serious
Bug #933832 [enigmail] Please package new version 2.1.2 into experimental
Severity set to 'serious' from 'wishlist'
> retitle: -1 enigmail: please package new version 2.1
Unknown command or malformed arguments to command.
--
933832:
Hi Paul,
I failed to reproduce this issue. Maybe we need to enable debug when compiling
for the tests so that we get a comprehensible stack trace.
I packaged the new upstream 2.0.6, so maybe this issue will disappear.
--
Cheers,
Abou Al Montacir
signature.asc
Description: This is a digitally
Your message dated Sun, 03 Nov 2019 10:33:56 +
with message-id
and subject line Bug#944024: fixed in cronie 1.5.5-2
has caused the Debian Bug report #944024,
regarding cronie: ships /usr/sbin/anacron
to be marked as done.
This means that you claim that the problem has been dealt with.
If
Control: tag -1 + confirmed pending
I've added a patch to functools to turn it into a namespace package,
thus avoiding the filename conflict. Going by __init__.py that seems to
have been intended upstream as well, but setup.py was missing some
statements to actually make it work that way.
Processing control commands:
> tag -1 + confirmed pending
Bug #943763 [python3-jaraco.itertools,python3-jaraco.functools]
python3-jaraco.itertools,python3-jaraco.functools: both ship
/usr/lib/python3/dist-packages/jaraco/__init__.py
Added tag(s) confirmed and pending.
--
943763:
Package: gpsd
Version: 3.19-2
Severity: Serious
Justification: Breaks silently functionality on upgrade
Hello,
after upgrading to version 3.19-2, I saw two effects (admittingly
after a while, but that makes it worse):
- the gpsd was not running anymore
- the init script is gone
In my setup,
Package: src:python-xarray
Version: 0.14.0-1
Severity: serious
Tags: sid bullseye
Despite the autopkg test regressions mentioned in #935455, python-xarray
migrated to testing due to a britney bug. In the autopkg test now 2313 test
cases fail. That's apparently also known upstream, and afaik
Your message dated Sun, 03 Nov 2019 07:31:24 +
with message-id
and subject line Bug#943982: Removed package(s) from unstable
has caused the Debian Bug report #937324,
regarding prey: Python2 removal in sid/bullseye
to be marked as done.
This means that you claim that the problem has been
Your message dated Sun, 03 Nov 2019 07:30:49 +
with message-id
and subject line Bug#943980: Removed package(s) from unstable
has caused the Debian Bug report #943230,
regarding pythoncad: Python2 removal in sid/bullseye
to be marked as done.
This means that you claim that the problem has
Your message dated Sun, 03 Nov 2019 07:29:12 +
with message-id
and subject line Bug#943971: Removed package(s) from unstable
has caused the Debian Bug report #938784,
regarding virtualbricks: Python2 removal in sid/bullseye
to be marked as done.
This means that you claim that the problem has
Your message dated Sun, 03 Nov 2019 07:30:26 +
with message-id
and subject line Bug#943977: Removed package(s) from unstable
has caused the Debian Bug report #936799,
regarding kiwi: Python2 removal in sid/bullseye
to be marked as done.
This means that you claim that the problem has been
Your message dated Sun, 03 Nov 2019 07:28:40 +
with message-id
and subject line Bug#943969: Removed package(s) from unstable
has caused the Debian Bug report #942977,
regarding disk-manager: Python2 removal in sid/bullseye
to be marked as done.
This means that you claim that the problem has
Your message dated Sun, 03 Nov 2019 07:32:09 +
with message-id
and subject line Bug#943983: Removed package(s) from unstable
has caused the Debian Bug report #936674,
regarding gtk-recordmydesktop: Python2 removal in sid/bullseye
to be marked as done.
This means that you claim that the
Your message dated Sun, 03 Nov 2019 07:29:35 +
with message-id
and subject line Bug#943973: Removed package(s) from unstable
has caused the Debian Bug report #942979,
regarding directoryassistant: Python2 removal in sid/bullseye
to be marked as done.
This means that you claim that the
Your message dated Sun, 03 Nov 2019 07:29:59 +
with message-id
and subject line Bug#943975: Removed package(s) from unstable
has caused the Debian Bug report #939114,
regarding tictactoe-ng: Python2 removal in sid/bullseye -- drop
python-distutils-extra build dependency
to be marked as done.
Your message dated Sun, 03 Nov 2019 07:33:28 +
with message-id
and subject line Bug#944010: Removed package(s) from unstable
has caused the Debian Bug report #897752,
regarding freefem3d: ftbfs with GCC-8
to be marked as done.
This means that you claim that the problem has been dealt with.
Your message dated Sun, 03 Nov 2019 07:29:35 +
with message-id
and subject line Bug#943973: Removed package(s) from unstable
has caused the Debian Bug report #885274,
regarding directoryassistant: Depends on unmaintained pygtk
to be marked as done.
This means that you claim that the problem
Your message dated Sun, 03 Nov 2019 07:31:24 +
with message-id
and subject line Bug#943982: Removed package(s) from unstable
has caused the Debian Bug report #885516,
regarding prey: Recommends unmaintained pygtk
to be marked as done.
This means that you claim that the problem has been dealt
Your message dated Sun, 03 Nov 2019 07:29:12 +
with message-id
and subject line Bug#943971: Removed package(s) from unstable
has caused the Debian Bug report #885494,
regarding virtualbricks: Depends on unmaintained pygtk
to be marked as done.
This means that you claim that the problem has
Your message dated Sun, 03 Nov 2019 07:32:09 +
with message-id
and subject line Bug#943983: Removed package(s) from unstable
has caused the Debian Bug report #885301,
regarding gtk-recordmydesktop: Depends on unmaintained pygtk
to be marked as done.
This means that you claim that the problem
Your message dated Sun, 03 Nov 2019 07:29:12 +
with message-id
and subject line Bug#943971: Removed package(s) from unstable
has caused the Debian Bug report #887878,
regarding virtualbricks: Don't recommend gksu
to be marked as done.
This means that you claim that the problem has been dealt
Your message dated Sun, 03 Nov 2019 07:33:28 +
with message-id
and subject line Bug#944010: Removed package(s) from unstable
has caused the Debian Bug report #921459,
regarding dead upstream - keep out of testing
to be marked as done.
This means that you claim that the problem has been dealt
Your message dated Sun, 03 Nov 2019 07:29:12 +
with message-id
and subject line Bug#943971: Removed package(s) from unstable
has caused the Debian Bug report #866491,
regarding virtualbricks: depends on obsolete python-imaging (replace with
python3-pil or python-pil)
to be marked as done.
Your message dated Sun, 03 Nov 2019 07:31:24 +
with message-id
and subject line Bug#943982: Removed package(s) from unstable
has caused the Debian Bug report #883269,
regarding Default curl_option '--compress' is invalid
to be marked as done.
This means that you claim that the problem has
Your message dated Sun, 03 Nov 2019 07:29:59 +
with message-id
and subject line Bug#943975: Removed package(s) from unstable
has caused the Debian Bug report #885487,
regarding tictactoe-ng: Depends on unmaintained pygtk
to be marked as done.
This means that you claim that the problem has
Your message dated Sun, 03 Nov 2019 07:28:18 +
with message-id
and subject line Bug#943958: Removed package(s) from unstable
has caused the Debian Bug report #874878,
regarding [freemat] Future Qt4 removal from Buster
to be marked as done.
This means that you claim that the problem has been
Your message dated Sun, 03 Nov 2019 07:30:49 +
with message-id
and subject line Bug#943980: Removed package(s) from unstable
has caused the Debian Bug report #885369,
regarding pythoncad: Depends on unmaintained pygtk
to be marked as done.
This means that you claim that the problem has been
Your message dated Sun, 03 Nov 2019 07:30:26 +
with message-id
and subject line Bug#943977: Removed package(s) from unstable
has caused the Debian Bug report #885378,
regarding kiwi: Depends on unmaintained pygtk
to be marked as done.
This means that you claim that the problem has been dealt
Your message dated Sun, 03 Nov 2019 07:28:40 +
with message-id
and subject line Bug#943969: Removed package(s) from unstable
has caused the Debian Bug report #885275,
regarding disk-manager: Depends on unmaintained pygtk
to be marked as done.
This means that you claim that the problem has
Processing commands for cont...@bugs.debian.org:
> forwarded 944030 g...@github.com:vincentbernat/jinja2-time.git
Bug #944030 [src:jinja2-time] jinja2-time: FTBFS in unstable
Set Bug forwarded-to-address to 'g...@github.com:vincentbernat/jinja2-time.git'.
> thanks
Stopping processing here.
Hi Dmitry,
On Sat, 02 Nov 2019 11:13:57 +1100 Dmitry Smirnov
wrote:
> Package: gitlab
> Version: 12.2.9-1
> Severity: serious
> Usertags: dfsg
>
>
> In most recent upload Utkarsh Gupta circumvented legitimate Lintian error
>
>
> E: gitlab source: source-is-missing
Processing commands for cont...@bugs.debian.org:
> forwarded 943987 https://gitlab.com/gitlab-org/gitlab/issues/35470
Bug #943987 [gitlab] non-free file in "debian/missing-sources"
Set Bug forwarded-to-address to
'https://gitlab.com/gitlab-org/gitlab/issues/35470'.
>
End of message, stopping
84 matches
Mail list logo
