Your message dated Thu, 05 Sep 2019 04:49:09 +
with message-id
and subject line Bug#930762: fixed in pybigwig 0.3.17-1
has caused the Debian Bug report #930762,
regarding pybigwig: autopkgtest fails because it tests non-existing
python-pybigwig
to be marked as done.
This means that you
Control: tag -1 pending
Hello,
Bug #930762 in pybigwig 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 #930762 [pybigwig] pybigwig: autopkgtest fails because it tests
non-existing python-pybigwig
Added tag(s) pending.
--
930762: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=930762
Debian Bug Tracking System
Contact ow...@bugs.debian.org with
Package: python3-websockify,websockify
Version: 0.8.0+dfsg1-14
Severity: serious
Upgrading websockify from 0.8.0+dfsg1-10 to 0.8.0+dfsg1-14 fails for me
as follows when its new dependency python3-websockify is unpacked:
Preparing to unpack .../websockify_0.8.0+dfsg1-14_armhf.deb ...
Unpacking
Processing commands for cont...@bugs.debian.org:
> reassign 935657 src:calendarserver
Bug #935657 [calendarserver] Please port and switch this package to Python 3 or
remove it from Debian
Bug reassigned from package 'calendarserver' to 'src:calendarserver'.
No longer marked as found in versions
Processing control commands:
> severity -1 serious
Bug #894519 [src:python-gtkglext1] python-gtkglext1: Intent to remove from
Debian
Severity set to 'serious' from 'important'
--
894519: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=894519
Debian Bug Tracking System
Contact
Package: node-js-beautify
Version: 1.7.5+repack-1
Severity: grave
Justification: renders package unusable
Dear Maintainer,
after installing css-beautify refuses to run with the following error:
internal/modules/cjs/loader.js:670
throw err;
^
Error: Cannot find module 'config-chain'
Processing control commands:
> tag -1 pending
Bug #899241 [mustang-plug] Amplifier detected by source from program developer
but not by Debian package.
Added tag(s) pending.
--
899241: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=899241
Debian Bug Tracking System
Contact
Control: tag -1 pending
Hello,
Bug #899241 in mustang-plug 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 Wed, 4 Sep 2019 22:56:56 +0200
with message-id <20190904205656.gb8...@reiner-h.de>
and subject line Re: lix: ftbfs with GCC-9
has caused the Debian Bug report #925769,
regarding lix: ftbfs with GCC-9
to be marked as done.
This means that you claim that the problem has been
Thanks for reporting.
I see warnings of this kind:
< Warning message:
< In CPL_crs_from_proj4string(x) :
< GDAL Message 1: +init=epsg: syntax is deprecated. It might
return a CRS with a non-EPSG compliant axis order.
but not the errors you get with +init=epsg: ; this is with PROJ
Control: tag -1 pending
Hello,
Bug #939129 in php-horde-imap-client 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 #939129 [php-horde-imap-client] Charset incorrectly omitted from SORT
command
Added tag(s) pending.
--
939129: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=939129
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
Processing commands for cont...@bugs.debian.org:
> close 937858 1.2.0-1
Bug #937858 [src:python-jsonpath-rw-ext] python-jsonpath-rw-ext: Python2
removal in sid/bullseye
Marked as fixed in versions python-jsonpath-rw-ext/1.2.0-1.
Bug #937858 [src:python-jsonpath-rw-ext] python-jsonpath-rw-ext:
This one can be closed now, right? See
https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=931825
(which really looks like the same bug to me - and it has been closed).
best
-- Andreas Rönnquist
gus...@debian.org
Processing control commands:
> severity -1 serious
Bug #938642 [src:telepathy-python] telepathy-python: Python2 removal in
sid/bullseye
Severity set to 'serious' from 'normal'
> affects -1 python-jarabe sugar-browse-activity sugar-imageviewer-activity
> sugar-memorize-activity
Processing commands for cont...@bugs.debian.org:
> severity 936229 serious
Bug #936229 [src:bootstrap-vz] bootstrap-vz: Python2 removal in sid/bullseye
Severity set to 'serious' from 'normal'
> thanks
Stopping processing here.
Please contact me if you need assistance.
--
936229:
Your message dated Wed, 04 Sep 2019 17:33:58 +
with message-id
and subject line Bug#925688: fixed in fwupdate 12-6
has caused the Debian Bug report #925688,
regarding fwupdate: ftbfs with GCC-9
to be marked as done.
This means that you claim that the problem has been dealt with.
If this is
Am Mi., 4. Sept. 2019 um 18:05 Uhr schrieb Matthias Klose :
>
> On 04.09.19 18:01, Matthias Klumpp wrote:
> > Am Mi., 4. Sept. 2019 um 18:00 Uhr schrieb Matthias Klose :
> >>
> >> Package: src:ldc
> >> Version: 1:1.17.0-1
> >> Severity: serious
> >> Tags: sid bullseye
> >>
> >> looks like gdmd
The 435 driver seems to work perfectly fine. Thank you very much!
Am Mi., 4. Sept. 2019 um 18:00 Uhr schrieb Matthias Klose :
>
> Package: src:ldc
> Version: 1:1.17.0-1
> Severity: serious
> Tags: sid bullseye
>
> looks like gdmd isn't available, and according to the changelog gdc should be
> used for the bootstrap?
Man you're quick ^^
gdmd is currently stuck
Package: src:ldc
Version: 1:1.17.0-1
Severity: serious
Tags: sid bullseye
looks like gdmd isn't available, and according to the changelog gdc should be
used for the bootstrap?
Source: sagemath
Severity: serious
Version: 8.8-1
Hello, looks like sagemath depends on path.py and python-snowballstemmer, both
of them removed in unstable and cruft packages.
Can you please update your dependencies to avoid them, or switch to the Python3
version of the binding?
thanks
On 04/09/2019 17.15, Niklas Schmidt wrote:
> I tried rebooting with an older kernel to reinstall the driver, which
> did not work. I also tried unplugging my second monitor and deleting the
> xorg.conf file. This didn't help either. I have resorted to using the legacy
> 390 driver for
Package: nvidia-driver
Version: 430.40-2
Severity: grave
Justification: renders package unusable
Dear Maintainer,
* What led up to the situation?
I upgraded the nvidia-driver package (version 418) to the newer version
430.40-2
* What was the outcome of this action?
Package: sddm
Version: 0.18.0-1
Severity: grave
Tags: upstream
Justification: renders package unusable
Quoting the upstream bug report:
"sddm-greeter needs execution rights at
/var/lib/sddm/.cache/sddm-greeter/qmlcache/*.qmlc.
krunner needs execution at
Your message dated Wed, 04 Sep 2019 14:39:07 +
with message-id
and subject line Bug#939399: fixed in libgeotiff 1.5.1-2
has caused the Debian Bug report #939399,
regarding libgeotiff FTBFS in bullseye (possiblly armhf specific), test
discrepancies.
to be marked as done.
This means that you
Control: tags -1 upstream
Control: forwarded -1 Edzer Pebesma
Hi Edzer,
since the upgrade to proj (6.1.1-1) the autopkgtest for sf fails:
$ LC_ALL=C.UTF-8 R --no-save < testthat.R
R version 3.6.1 (2019-07-05) -- "Action of the Toes"
Copyright (C) 2019 The R Foundation for Statistical
Processing control commands:
> tags -1 upstream
Bug #939002 [src:r-cran-sf] r-cran-sf: autopkgtest failure prevents testing
migration
Added tag(s) upstream.
> forwarded -1 Edzer Pebesma
Bug #939002 [src:r-cran-sf] r-cran-sf: autopkgtest failure prevents testing
migration
Set Bug
Processing commands for cont...@bugs.debian.org:
> reassign 939399 src:libgeotiff
Bug #939399 [libgeotiff\] libgeotiff FTBFS in bullseye (possiblly armhf
specific), test discrepancies.
Warning: Unknown package 'libgeotiff\'
Bug reassigned from package 'libgeotiff\' to 'src:libgeotiff'.
No longer
Processing control commands:
> tags -1 pending
Bug #939399 [libgeotiff\] libgeotiff FTBFS in bullseye (possiblly armhf
specific), test discrepancies.
Warning: Unknown package 'libgeotiff\'
Added tag(s) pending.
Warning: Unknown package 'libgeotiff\'
> forwarded -1
Control: tags -1 pending
Control: forwarded -1 https://github.com/OSGeo/libgeotiff/issues/22
On 9/4/19 3:38 PM, Peter Michael Green wrote:
>> diff testlistgeo_out with testlistgeo_out.dist
>> --- testlistgeo_out 2019-09-04 06:58:26.979704475 +
>> +++ ../test/testlistgeo_out.dist
Hi,
from my tests the test works with gcc-8 and fails now with gcc-9.
With gcc-9 and O1, the test passes and fails with O2.
I expanded the options (c++ -S) added by O2 compared to O1 in gcc-9 to compile
qd_test.cpp and got :
-falign-functions
-falign-jumps
-falign-labels
-falign-loops
package: libgeotiff\
version: 1.5.1-1
severity: serious
tags: bullseye
Hi, libgeotiff just failed to build in raspbian bullseye with the
following message.
Running ../test/testlistgeo using ../bin/listgeo:
Source: node-elliptic
Version: 6.5.0~dfsg-1
Tags: patch
Severity: serious
Forwarded: https://github.com/indutny/elliptic/pull/193
Hello, looks like the testsuite now fails because "hello" is not an hex
string...
the following patch seems to fix it (I'm not sure if there is a better approach
to
Processing control commands:
> fixed -1 8.8-1
Bug #925820 [src:sagemath] sagemath: ftbfs with GCC-9
Marked as fixed in versions sagemath/8.8-1.
> close -1
Bug #925820 [src:sagemath] sagemath: ftbfs with GCC-9
Marked Bug as done
--
925820: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=925820
control: fixed -1 8.8-1
control: close -1
On Wed, 27 Mar 2019 19:47:55 + Matthias Klose wrote:
> Package: src:sagemath
> Version: 8.6-6
> Severity: normal
> Tags: sid bullseye
> User: debian-...@lists.debian.org
> Usertags: ftbfs-gcc-9
>
> Please keep this issue open in the bug tracker for
Hi,
I read the discussion, but since this software is very young, it's
fixing bugs. Since the last message, version 0.1.8 is here, and it is
quite stable now.
Is there any feedback on recent versions?
Have a nice day,
Adrien
Hello Roger,
>Backports team won't complain if the package is in testing.
>And I think release team won't complain now since it's not in freezing stage.
>
>Lack of upstream support usually means we won't have it in stable.
>But if user decide to use backports by their own choice, they should
Your message dated Wed, 04 Sep 2019 10:20:08 +
with message-id
and subject line Bug#939308: fixed in gkrellm2-cpufreq 0.6.4-6
has caused the Debian Bug report #939308,
regarding gkrellm2-cpufreq_0.6.4-5_mips64el.changes REJECTED
to be marked as done.
This means that you claim that the
Source: fswatch
Version: 1.14.0+repack-9
Severity: serious
Hello, looks like dpkg-gensymbols is sad everywhere according to Debian logs
https://buildd.debian.org/status/package.php?p=fswatch=unstable
I don't think exporting such c++ symbols is a good idea, specially because they
change between
> Based on a conversation with Muammar, I created a Salsa repository under
> the Games Team and my updates are in that repository. I don't believe
> Muammar has had an opportunity to review my commits but, barring any
> requested changes, I believe that this package is ready for upload.
>
> I am
Package: citadel-server
Version: 917-2+b1
Severity: grave
Justification: renders package unusable
Dear Maintainer,
The installation could only be done after I manually removed Exim. I
also removed Apache, which might not have been necessary.
The Citadel server hangs directly after it is
Your message dated Wed, 04 Sep 2019 09:22:53 +
with message-id
and subject line Bug#939356: Removed package(s) from unstable
has caused the Debian Bug report #874809,
regarding [alsoft-conf] Future Qt4 removal from Buster
to be marked as done.
This means that you claim that the problem has
Your message dated Wed, 04 Sep 2019 09:20:38 +
with message-id
and subject line Bug#939350: Removed package(s) from unstable
has caused the Debian Bug report #933146,
regarding FTBFS, not Django 2.2 ready
to be marked as done.
This means that you claim that the problem has been dealt with.
Your message dated Wed, 04 Sep 2019 09:21:02 +
with message-id
and subject line Bug#939351: Removed package(s) from unstable
has caused the Debian Bug report #755586,
regarding django-app-plugins: Please ensure it works with Django 1.7
to be marked as done.
This means that you claim that the
Your message dated Wed, 04 Sep 2019 09:21:02 +
with message-id
and subject line Bug#939351: Removed package(s) from unstable
has caused the Debian Bug report #896259,
regarding python-django-app-plugins: app_plugins fails to import
to be marked as done.
This means that you claim that the
Your message dated Wed, 04 Sep 2019 09:21:36 +
with message-id
and subject line Bug#939352: Removed package(s) from unstable
has caused the Debian Bug report #755605,
regarding django-threaded-multihost: Please ensure it works with Django 1.7
to be marked as done.
This means that you claim
Your message dated Wed, 04 Sep 2019 09:20:15 +
with message-id
and subject line Bug#939349: Removed package(s) from unstable
has caused the Debian Bug report #918418,
regarding django-prometheus FTBFS: test failures
to be marked as done.
This means that you claim that the problem has been
Your message dated Wed, 04 Sep 2019 09:17:33 +
with message-id
and subject line Bug#939335: Removed package(s) from unstable
has caused the Debian Bug report #896224,
regarding python-pyrax: pyrax fails to import
to be marked as done.
This means that you claim that the problem has been dealt
Your message dated Wed, 04 Sep 2019 09:17:33 +
with message-id
and subject line Bug#939335: Removed package(s) from unstable
has caused the Debian Bug report #882095,
regarding python-pyrax FTBFS: test failures
to be marked as done.
This means that you claim that the problem has been dealt
Your message dated Wed, 04 Sep 2019 09:19:49 +
with message-id
and subject line Bug#939348: Removed package(s) from unstable
has caused the Debian Bug report #865293,
regarding djangocms-admin-style FTBFS with Django 1.11
to be marked as done.
This means that you claim that the problem has
Package: dub
Version: 1.16.0-1
Severity: serious
Tags: sid bullseye
dub depends on the unavailable package default-d-compiler. Maybe that one should
be built from the dh-dlang source. If you touch that package, please add the
package for all the mips* targets as well, now built by gcc-9/gdc-9.
Your message dated Wed, 04 Sep 2019 09:05:44 +
with message-id
and subject line Bug#935877: fixed in ccdproc 2.0.0-1
has caused the Debian Bug report #935877,
regarding ccdproc: FTBFS with pytest 4.6
to be marked as done.
This means that you claim that the problem has been dealt with.
If
Your message dated Wed, 04 Sep 2019 07:22:07 +
with message-id
and subject line Bug#935339: fixed in ruby-svg-graph 1.0.5-4
has caused the Debian Bug report #935339,
regarding ruby-svg-graph: depends on ancient 'parsedate' Ruby core library
to be marked as done.
This means that you claim
Processing commands for cont...@bugs.debian.org:
> unarchive 893554
Bug #893554 {Done: Adrian Bunk } [src:range-v3] range-v3 FTBFS
Unarchived Bug 893554
> retitle 893554 FTBFS with GCC 7.3.0 (error: no matching function for call to
> 'initializer_list(const volatile std::initializer_list&)')
Bug
Processing commands for cont...@bugs.debian.org:
> tags 893554 ftbfs
Failed to alter tags of Bug 893554: Not altering archived bugs; see unarchive.
> retitle 893554 FTBFS with GCC 7.3.0 (error: no matching function for call to
> 'initializer_list(const volatile std::initializer_list&)')
Failed
57 matches
Mail list logo
