On Wed, 31 Jul 2019 at 21:51:38 -0500, Kenneth Pronovici wrote:
> This is still one of 20+ packages in the archive that depend on
> Epydoc.
For those receiving this message out of context with only a bug number
(for example via a Python team subscription on tracker.debian.org like I
did), the affe
Processing commands for cont...@bugs.debian.org:
> tags 932834 + sid bullseye experimental
Bug #932834 [src:python-apt] FTBFS: relocation R_X86_64_32 against symbol
`PyVersion_Type' can not be used when making a shared object; recompile with
-fPIC
Added tag(s) bullseye, experimental, and sid.
>
Your message dated Thu, 01 Aug 2019 06:49:32 +
with message-id
and subject line Bug#881555: fixed in python-csb 1.2.5+dfsg-4
has caused the Debian Bug report #881555,
regarding Epydoc will be removed
to be marked as done.
This means that you claim that the problem has been dealt with.
If this
Your message dated Thu, 01 Aug 2019 06:34:54 +
with message-id
and subject line Bug#933536: fixed in pygac 1.1.0-3
has caused the Debian Bug report #933536,
regarding FTBFS: PYGAC_CONFIG_FILE is not a file or does not exist
to be marked as done.
This means that you claim that the problem has
Source: hepmc3
Version: 3.1.1-1
Severity: serious
Tags: ftbfs
hepmc3 fails to build from source, because it unconditionally runs
dh_doxygen but lists doxygen in Build-Depends-Indep only. arch-only
builds are deemed to fail.
Helmut
Processing commands for cont...@bugs.debian.org:
> close 920844
Bug #920844 [src:node-react-audio-player] node-react-audio-player build depends
on node-react that is currently not in buster
Marked Bug as done
> thanks
Stopping processing here.
Please contact me if you need assistance.
--
920844
Processing commands for cont...@bugs.debian.org:
> fixed 914462 1.5.2-1
Bug #914462 {Done: Pirate Praveen }
[src:node-rollup-plugin-alias] node-rollup-plugin-alias: Fails to build,
unsatsifiable Build-Depends
Marked as fixed in versions node-rollup-plugin-alias/1.5.2-1.
> thanks
Stopping process
Processing commands for cont...@bugs.debian.org:
> close 914462
Bug #914462 [src:node-rollup-plugin-alias] node-rollup-plugin-alias: Fails to
build, unsatsifiable Build-Depends
Marked Bug as done
> thanks
Stopping processing here.
Please contact me if you need assistance.
--
914462: https://bug
OK, I think "removing the API doc" is a sufficient hint what should be done ...
On Thu, Aug 01, 2019 at 07:51:44AM +0200, Andreas Tille wrote:
> Hi Kenneth,
>
> if you provide a patch the package will be uploaded in less then 24
> hours. I'm fine without the API doc.
>
> Thanks for your coopera
Hi Kenneth,
if you provide a patch the package will be uploaded in less then 24
hours. I'm fine without the API doc.
Thanks for your cooperation
Andreas.
On Wed, Jul 31, 2019 at 09:51:38PM -0500, Kenneth Pronovici wrote:
> Hi,
>
> This is still one of 20+ packages in the archive that de
Processing commands for cont...@bugs.debian.org:
> affects 933536 + satpy
Bug #933536 [src:pygac] FTBFS: PYGAC_CONFIG_FILE is not a file or does not exist
Added indication that 933536 affects satpy
> thanks
Stopping processing here.
Please contact me if you need assistance.
--
933536: https://bu
Processing commands for cont...@bugs.debian.org:
> reassign 933536 src:pygac 1.1.0-2
Bug #933536 [src:satpy] FTBFS: PYGAC_CONFIG_FILE is not a file or does not exist
Bug reassigned from package 'src:satpy' to 'src:pygac'.
No longer marked as found in versions satpy/0.16.1-1.
Ignoring request to al
Simon McVittie writes:
> Control: reassign -1 libmutter-3-0 3.30.2-7
> Control: affects -1 gnome-shell
> Control: tags -1 + moreinfo
> Control: forwarded -1 https://gitlab.gnome.org/GNOME/mutter/merge_requests/538
>
> On Mon, 22 Jul 2019 at 08:18:09 +0200, Jörn Heissler wrote:
>> gnome-shell cras
On Wed, Jul 31, 2019, 23:11 Sandro Tosi wrote:
> Hello Kenneth,
>
> On Wed, Jul 31, 2019 at 10:36 PM Kenneth J. Pronovici
> wrote:
> > This is one of 20+ packages in the archive that still depend on Epydoc.
> I
> > have filed a bug with ftp.debian.org to have epydoc removed from
> unstable.
> >
Hello Kenneth,
On Wed, Jul 31, 2019 at 10:36 PM Kenneth J. Pronovici
wrote:
> This is one of 20+ packages in the archive that still depend on Epydoc. I
> have filed a bug with ftp.debian.org to have epydoc removed from unstable.
> Besides its lack of support for Python 3, epydoc has been complet
Hi,
This is still one of 20+ packages in the archive that depend on
Epydoc. I have filed a bug with ftp.debian.org to have epydoc removed
from unstable, and that can't proceed while this package still uses
epydoc as a build dependency. As a result, I have increased the
severity of this bug to se
Processing commands for cont...@bugs.debian.org:
> # Change all of the titles of these bugs; I'm no longer asking, I'm
> notifying that the package will be removed
Unknown command or malformed arguments to command.
> retitle 881544 Epydoc will be removed
Bug #881544 [src:dbf] dbf: Please migrate a
Source: pyinotify
Severity: serious
Justification: Policy 5.9.2
Hi,
This is one of 20+ packages in the archive that still depend on Epydoc. I
have filed a bug with ftp.debian.org to have epydoc removed from unstable.
Besides its lack of support for Python 3, epydoc has been completely
unsupporte
Your message dated Thu, 01 Aug 2019 02:38:40 +
with message-id
and subject line Bug#932584: fixed in pydoctor 16.3.0-2.1
has caused the Debian Bug report #932584,
regarding python-pydoctor: Epydoc will be removed
to be marked as done.
This means that you claim that the problem has been dealt
Package: python-txosc
Severity: serious
Justification: Policy 5.9.2
Hi,
This is one of 20+ packages in the archive that still depend on Epydoc. I
have filed a bug with ftp.debian.org to have epydoc removed from unstable.
Besides its lack of support for Python 3, epydoc has been completely
unsupp
Source: openvdb
Severity: serious
Justification: Policy 5.9.2
Hi,
This is one of 20+ packages in the archive that still depend on Epydoc. I
have filed a bug with ftp.debian.org to have epydoc removed from unstable.
Besides its lack of support for Python 3, epydoc has been completely
unsupported
Package: python-crypto
Version: 2.6.1-7
Severity: serious
Justification: Policy 5.9.2
Hi,
This is one of 20+ packages in the archive that still depend on Epydoc. I
have filed a bug with ftp.debian.org to have epydoc removed from unstable.
Besides its lack of support for Python 3, epydoc has been
Source: kiwi
Severity: serious
Justification: Policy 5.9.2
Hi,
This is one of 20+ packages in the archive that still depend on Epydoc. I
have filed a bug with ftp.debian.org to have epydoc removed from unstable.
Besides its lack of support for Python 3, epydoc has been completely
unsupported ups
Source: logilab-common
Severity: serious
Justification: Policy 5.9.2
Hi,
This is one of 20+ packages in the archive that still depend on Epydoc. I
have filed a bug with ftp.debian.org to have epydoc removed from unstable.
Besides its lack of support for Python 3, epydoc has been completely
unsup
Source: ldaptor
Severity: serious
Justification: Policy 5.9.2
Hi,
This is one of 20+ packages in the archive that still depend on Epydoc. I
have filed a bug with ftp.debian.org to have epydoc removed from unstable.
Besides its lack of support for Python 3, epydoc has been completely
unsupported
On Wed, Jul 31, 2019 at 10:46 AM Ian Jackson
wrote:
> > Otherwise, I will see if I can determine how well the package works
> > without epydoc installed. If it works (i.e. doesn't blow up) and I
> > don't hear back with other instructions, I will eventually NMU my
> > changes to remove the epydoc
In the update-command-not-found implementation here:
/usr/sbin/update-command-not-found
the following lines seem important:
command_files = glob.glob("/var/lib/apt/lists/*Contents*")
if len(command_files) > 0:
col = DbCreator(command_files)
col.create(db)
If I understan
On 2019-07-30 13:07, Andreas Beckmann wrote:
This can be 'fixed' (created) by running
apt-file update
manually. It will be 'fixed' automatically the next time
apt-get update
(or any equivalent way to update the apt package lists) is run.
For me, that does not help. I tried both "apt-file
Hi Alain,
> I upgraded from Stretch to Buster and sound completely disappeared.
> Removing Timidity fixed the problem but made me unable to use gnu
> solfege as it
> depends on timidity.
The sound is broken by timidity-daemon, not the timidity package
itself.
So you should try to install GNU Solf
Processing control commands:
> severity -1 serious
Bug #928993 [sdaps] sdaps: Please package the latest upstream version
Severity set to 'serious' from 'grave'
--
928993: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=928993
Debian Bug Tracking System
Contact ow...@bugs.debian.org with proble
Control: severity -1 serious
thanks
On Wed, Jul 31, 2019 at 05:25:38PM -0400, Boyuan Yang wrote:
> Control: severity -1 grave
>
> Since the new upload of zbar has already dropped the python2 binding,
> I'm raising the severity of this bug accordingly.
not accordingly, but oh well, thanks at leas
Processing control commands:
> severity -1 grave
Bug #928993 [sdaps] sdaps: Please package the latest upstream version
Severity set to 'grave' from 'important'
--
928993: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=928993
Debian Bug Tracking System
Contact ow...@bugs.debian.org with proble
Package: python3-bx
Version: 0.8.4-1
Severity: serious
User: debian...@lists.debian.org
Usertags: piuparts replaces-without-breaks
Hi,
during a test with piuparts and DOSE tools I noticed your package causes
removal of files that also belong to another package.
This is caused by using Replaces wi
Your message dated Wed, 31 Jul 2019 19:19:12 +
with message-id
and subject line Bug#932643: fixed in cryptsetup 2:2.2.0~rc1-2
has caused the Debian Bug report #932643,
regarding cryptsetup upgrade causes cryptsetup-initramfs autoremoval and boot
failure
to be marked as done.
This means that
Your message dated Wed, 31 Jul 2019 19:19:12 +
with message-id
and subject line Bug#933487: fixed in cryptsetup 2:2.2.0~rc1-2
has caused the Debian Bug report #933487,
regarding cryptsetup-run: missing Breaks+Replaces: cryptsetup (<< 2:2.2)
to be marked as done.
This means that you claim that
Your message dated Wed, 31 Jul 2019 19:08:30 +
with message-id
and subject line Bug#933242: fixed in python-slugify 3.0.3-1
has caused the Debian Bug report #933242,
regarding python-slugify: text-unicode still required dependency
to be marked as done.
This means that you claim that the probl
Processing commands for cont...@bugs.debian.org:
> clone 933280 -1 -2 -3 -4 -5 -6 -7 -8 -9 -10 -11
Bug #933280 [src:breathe] BD on texlive-generic-extra which isn't build anymore
and isn't in bullseye
Bug 933280 cloned as bugs 933581-933591
> reassign -1 python-networkx 2.2-1
Bug #933581 [src:bre
Processing commands for cont...@bugs.debian.org:
> tags 933525 + pending
Bug #933525 [monsterz] monsterz: fails to install: monsterz.postinst: 16:
cannot create /var/games/monsterz: Directory nonexistent
Added tag(s) pending.
> thanks
Stopping processing here.
Please contact me if you need assis
Kenneth Pronovici writes ("Epydoc and Pydoctor"):
> (I'm the maintainer for epydoc.)
Hi.
Thanks for the analysis which seems to make sense to me.
> Given that epydoc does not work properly in Python 3, and it's beyond
> my capabilities to fix it, there aren't too many options here. Either
> we
Processing control commands:
> fixed -1 2.19.6
Bug #91 [src:devscripts] devscripts: FTBFS in buster (failing tests)
Marked as fixed in versions devscripts/2.19.6.
--
91: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=91
Debian Bug Tracking System
Contact ow...@bugs.debian.org with
Followup-For: Bug #91
Control: fixed -1 2.19.6
I can reproduce the failure with 2.19.5 in buster, bullseye and sid,
but 2.19.6 compiles fine in these three distros.
Andreas
El Mon, Jul 29, 2019 at 02:46:14PM +0200, Agustin Martin deia:
> I am attaching a couple of files with current state of my experiments. I am
> also not fluent with python (that is why I did not adopt or sponsored this
> or any other python package), so my changes would definitely need review, if
>
Processing commands for cont...@bugs.debian.org:
> tags 932185 + experimental
Bug #932185 [auto-multiple-choice] auto-multiple-choice depends on cruft
package.
Added tag(s) experimental.
> tags 933020 + experimental
Bug #933020 [src:libvirt] libvirt ftbfs in unstable (configure fails)
Added tag(s
On Wed, 31 Jul 2019 at 11:52:20 +0200, Tobias Frost wrote:
> On Wed, Jul 31, 2019 at 10:05:18AM +0100, Simon McVittie wrote:
> > Assuming this didn't happen in buster, it might be a regression or
> > behaviour change in recent uploads of udisks2 or glib2.0.
>
> I assume the glib2.0 caused/triggere
Processing control commands:
> affects -1 src:python-scipy
Bug #933536 [src:satpy] FTBFS: PYGAC_CONFIG_FILE is not a file or does not exist
Added indication that 933536 affects src:python-scipy
--
933536: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=933536
Debian Bug Tracking System
Contact
Source: satpy
Version: 0.16.1-1
Severity: serious
Justification: FTBFS
Control: affects -1 src:python-scipy
satpy now FTBFS (and fails tests) because of the recent upgrade of
python3-pygac to 1.1.0-2.
test_basic_check_satpy (satpy.tests.test_config.TestCheckSatpy)
Test 'check_satpy' basic functio
Processing control commands:
> tags -1 bullseye
Bug #933529 {Done: Simon McVittie } [gnome-control-center]
gnome-control-center: segfaults on selecting Details -> Overview
(info-overview) panel
Added tag(s) bullseye.
--
933529: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=933529
Debian Bu
Control: tags -1 bullseye
On Wed, Jul 31, 2019 at 10:53:01AM +0100, Simon McVittie wrote:
> Control: forwarded -1
> https://gitlab.gnome.org/GNOME/gnome-control-center/issues/411
>
> On Wed, 31 Jul 2019 at 10:05:18 +0100, Simon McVittie wrote:
> > On Wed, 31 Jul 2019 at 10:46:37 +0200, Tobias Fr
Your message dated Wed, 31 Jul 2019 10:08:35 +
with message-id
and subject line Bug#933529: fixed in gnome-control-center 1:3.30.3-2
has caused the Debian Bug report #933529,
regarding gnome-control-center: segfaults on selecting Details -> Overview
(info-overview) panel
to be marked as done.
Processing control commands:
> tag -1 patch
Bug #842892 [libz3-jni] java.lang.UnsatisfiedLinkError: libz3java.so: undefined
symbol: Z3_solver_get_model
Added tag(s) patch.
--
842892: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=842892
Debian Bug Tracking System
Contact ow...@bugs.debian.or
Followup-For: Bug #842892
Control: tag -1 patch
Hi,
the attached patch should fix the wrong SONAME of libz3java.so.
Andreas
Followup-For: Bug #842892
now with patch ...
>From fb80ab10200c149e9dbb9ff6c043646782111a67 Mon Sep 17 00:00:00 2001
From: Andreas Beckmann
Date: Wed, 31 Jul 2019 09:53:48 +0200
Subject: [PATCH] do not set the SONAME of libz3java.so to libz3.so.4
---
debian/changelog | 6 ++
debian/rules
Your message dated Wed, 31 Jul 2019 10:59:56 +0100
with message-id <20190731095956.ga7...@espresso.pseudorandom.co.uk>
and subject line Re: Bug#933529: gnome-control-center: SEGVs immediatly
has caused the Debian Bug report #933529,
regarding gnome-control-center: segfaults on selecting Details ->
Control: forwarded -1
https://gitlab.gnome.org/GNOME/gnome-control-center/issues/411
On Wed, 31 Jul 2019 at 10:05:18 +0100, Simon McVittie wrote:
> On Wed, 31 Jul 2019 at 10:46:37 +0200, Tobias Frost wrote:
> > Suddenly gnome-control-center starts to immediatly segfaults on start.
>
> Based on y
On Wed, Jul 31, 2019 at 10:05:18AM +0100, Simon McVittie wrote:
Thanks Simon for your fast reply!
> Control: retitle -1 gnome-control-center: segfaults on selecting Details ->
> Overview (info-overview) panel
>
> On Wed, 31 Jul 2019 at 10:46:37 +0200, Tobias Frost wrote:
> > Suddenly gnome-cont
Processing control commands:
> forwarded -1 https://gitlab.gnome.org/GNOME/gnome-control-center/issues/411
Bug #933529 [gnome-control-center] gnome-control-center: segfaults on selecting
Details -> Overview (info-overview) panel
Set Bug forwarded-to-address to
'https://gitlab.gnome.org/GNOME/gno
Control: tag -1 pending
Hello,
Bug #933529 in gnome-control-center 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/gnome-team/gnome-control-center/commit/762088
Processing control commands:
> tag -1 pending
Bug #933529 [gnome-control-center] gnome-control-center: segfaults on selecting
Details -> Overview (info-overview) panel
Added tag(s) pending.
--
933529: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=933529
Debian Bug Tracking System
Contact ow
Your message dated Wed, 31 Jul 2019 09:50:13 +
with message-id
and subject line Bug#932544: fixed in s3ql 3.2+dfsg-2
has caused the Debian Bug report #932544,
regarding s3ql build-depends on cruft package
to be marked as done.
This means that you claim that the problem has been dealt with.
If
Processing commands for cont...@bugs.debian.org:
> found 924128 1.13.7+dfsg-1
Bug #924128 [prokka] prokka: creates world writable directory tree
/var/lib/prokka/*
Marked as found in versions prokka/1.13.7+dfsg-1.
> affects 884264 + fusionforge-plugin-authcas fusionforge-plugin-globalsearch
> fus
Control: retitle -1 gnome-control-center: segfaults on selecting Details ->
Overview (info-overview) panel
On Wed, 31 Jul 2019 at 10:46:37 +0200, Tobias Frost wrote:
> Suddenly gnome-control-center starts to immediatly segfaults on start.
Based on your backtrace, I can reproduce this from a work
Update: To get gnome-control-center starting again, this seems to help:
dconf reset -f /org/gnome/control-center/
But once as I click "Details" again, it starts crashing again and
again, until I dconf reset again.
I found this hint from:
https://bbs.archlinux.org/viewtopic.php?id=244792; They
Processing control commands:
> retitle -1 gnome-control-center: segfaults on selecting Details -> Overview
> (info-overview) panel
Bug #933529 [gnome-control-center] gnome-control-center: SEGVs immediatly
Changed Bug title to 'gnome-control-center: segfaults on selecting Details ->
Overview (inf
Your message dated Wed, 31 Jul 2019 08:58:00 +
with message-id
and subject line Bug#933488: fixed in node-uglifyjs-webpack-plugin 1.3.0-4
has caused the Debian Bug report #933488,
regarding webpack 4 production mode is broken: Error: Cannot find module
'worker-farm'
to be marked as done.
Thi
Your message dated Wed, 31 Jul 2019 08:58:31 +
with message-id
and subject line Bug#933488: fixed in node-webpack 4.7.0-2
has caused the Debian Bug report #933488,
regarding webpack 4 production mode is broken: Error: Cannot find module
'worker-farm'
to be marked as done.
This means that you
Package: gnome-control-center
Version: 1:3.30.3-1
Severity: grave
Suddenly gnome-control-center starts to immediatly segfaults on start.
This happens for me on 2 devices (of 2 tested).
One note about "suddenly": When that started to happen, it first
normally started and then crashed once I tried
Package: python3-os-faults
Version: 0.2.1-1
Severity: serious
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 release, thus the severity.
>Fr
Package: snakemake
Version: 5.5.3-1
Severity: serious
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 release, thus the severity.
>From the a
Package: monsterz
Version: 0.7.1-10
Severity: serious
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 release, thus the severity.
>From the a
Package: python-libpcap
Version: 0.6.4-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 release, thus th
Processing commands for cont...@bugs.debian.org:
> reassign 933488 node-uglifyjs-webpack-plugin
Bug #933488 [webpack] webpack 4 production mode is broken: Error: Cannot find
module 'worker-farm'
Bug reassigned from package 'webpack' to 'node-uglifyjs-webpack-plugin'.
No longer marked as found in
Processing commands for cont...@bugs.debian.org:
> found 933488 1.3.0-3
Bug #933488 [node-uglifyjs-webpack-plugin] webpack 4 production mode is broken:
Error: Cannot find module 'worker-farm'
Marked as found in versions node-uglifyjs-webpack-plugin/1.3.0-3.
> thanks
Stopping processing here.
Ple
Processing commands for cont...@bugs.debian.org:
> affects 933488 webpack
Bug #933488 [node-uglifyjs-webpack-plugin] webpack 4 production mode is broken:
Error: Cannot find module 'worker-farm'
Added indication that 933488 affects webpack
> thanks
Stopping processing here.
Please contact me if y
Le 31/07/2019 à 10:02, Pirate Praveen a écrit :
> $ apt-file list node-uglifyjs-webpack-plugin
> node-uglifyjs-webpack-plugin:
> /usr/lib/nodejs/uglifyjs-webpack-plugin/dist/index.js
> node-uglifyjs-webpack-plugin:
> /usr/lib/nodejs/uglifyjs-webpack-plugin/lib/post_install.js
> node-uglifyjs-webpac
Processing commands for cont...@bugs.debian.org:
> severity 933496 serious
Bug #933496 [src:libminini] libminini: doesn't ship needed headers files
Severity set to 'serious' from 'normal'
> thanks
Stopping processing here.
Please contact me if you need assistance.
--
933496: https://bugs.debian.
$ apt-file list node-uglifyjs-webpack-plugin
node-uglifyjs-webpack-plugin:
/usr/lib/nodejs/uglifyjs-webpack-plugin/dist/index.js
node-uglifyjs-webpack-plugin:
/usr/lib/nodejs/uglifyjs-webpack-plugin/lib/post_install.js
node-uglifyjs-webpack-plugin:
/usr/lib/nodejs/uglifyjs-webpack-plugin/packag
Source: git
Version: 1:2.23.0~rc0-1
Severity: serious
Tags: patch upstream ftbfs
Justification: fails to build from source
User: debian-s...@lists.debian.org
Usertags: s390x
Hello!
git currently fails to build from source on big-endian targets due to
testsuite failures [1].
The issue is already
77 matches
Mail list logo
