Hello, after a walk through the tools/src directory and sometime to search
the whole internet,
I found these files are from third party which have no copyright disclaimer:
DeKDic.exe, KSDrip.exe: binary without source, should be of course removed,
upstream
of stardict said they're useful and
Crashes for me too
seems to be random crashes whilst viewing various websites.
Hope the log attached means something to someone who can solve the problem.
Sent with [ProtonMail](https://protonmail.com) Secure Email.
crash log
Description: Binary data
Hi all,
I do see the plan of bup as shared in
https://github.com/bup/bup/commit/b49607da4c0403bc1903caf2abd9640b03baff12
and subsequent commits. Dunno how hard it would be for someone who
already has used bup for the move from python2 to python3 especially
with backups.
--
Regards,
Processing commands for cont...@bugs.debian.org:
> reopen 945911
Bug #945911 {Done: Julian Andres Klode } [apt] only send
credentials over https by default
Bug reopened
Ignoring request to alter fixed versions of bug #945911 to the same values
previously set
>
End of message, stopping
Your message dated Fri, 13 Dec 2019 05:19:11 +
with message-id
and subject line Bug#944249: fixed in gnuplot-mode 1:0.7.0-2014-12-31-2
has caused the Debian Bug report #944249,
regarding gnuplot-mode does not work with emacs26
to be marked as done.
This means that you claim that the problem
I am too busy to chase this all up, I am afraid.
On 07.12.19 09:04, Andreas Tille wrote:
Hi,
I just removed mgltools-pmv from debian-med metapackages to prepare its
removal. I realised that autodocktools depends mgltools-pmv so this has
to go as well. Since there is no sign that this 2.5
Processing commands for cont...@bugs.debian.org:
> severity 938346 serious
Bug #938346 [src:regina-normal] regina-normal: Python2 removal in sid/bullseye
Severity set to 'serious' from 'normal'
> thanks
Stopping processing here.
Please contact me if you need assistance.
--
938346:
Processing commands for cont...@bugs.debian.org:
> severity 936910 serious
Bug #936910 [src:librcsb-core-wrapper] librcsb-core-wrapper: Python2 removal in
sid/bullseye
Severity set to 'serious' from 'normal'
> thanks
Stopping processing here.
Please contact me if you need assistance.
--
Processing commands for cont...@bugs.debian.org:
> severity 937435 serious
Bug #937435 [src:pyexiv2] pyexiv2: Python2 removal in sid/bullseye
Severity set to 'serious' from 'normal'
> thanks
Stopping processing here.
Please contact me if you need assistance.
--
937435:
Your message dated Thu, 12 Dec 2019 17:16:21 -0500
with message-id
and subject line Re: pygccxml: Python2 removal in sid/bullseye
has caused the Debian Bug report #937443,
regarding pygccxml: Python2 removal in sid/bullseye
to be marked as done.
This means that you claim that the problem has
Your message dated Thu, 12 Dec 2019 22:04:33 +
with message-id
and subject line Bug#946614: fixed in keystone 2:16.0.0-5
has caused the Debian Bug report #946614,
regarding keystone: CVE-2019-19687
to be marked as done.
This means that you claim that the problem has been dealt with.
If this
Processing control commands:
> tag -1 pending
Bug #946614 [src:keystone] keystone: CVE-2019-19687
Added tag(s) pending.
--
946614: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=946614
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
Control: tag -1 pending
Hello,
Bug #946614 in keystone 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:
On Thu, 12 Dec 2019, Andreas Tille wrote:
That hint was helpful anyway and I get further now. I think now the
problem is to convince scons to install in $(CURDIR)/debian/tmp which
seems to try rather /usr/share/pdb2pqr directly:
Looks like the debian/rules file is specifying
Hi Thomas!
On Thu, Dec 12, 2019 at 10:13:25PM +0100, Thomas Goirand wrote:
> On 12/11/19 11:10 PM, Salvatore Bonaccorso wrote:
> > Source: keystone
> > Version: 2:16.0.0-4
> > Severity: grave
> > Tags: security upstream
> > Forwarded: https://bugs.launchpad.net/keystone/+bug/1855080
> >
> > Hi,
Processing commands for cont...@bugs.debian.org:
> retitle 946653 spamassassin: CVE-2019-12420: specially crafted messages can
> exhaust system resources resulting in a denial of service
Bug #946653 [spamassassin] spamassassin: specially crafted messages can exhaust
system resources resulting
Processing commands for cont...@bugs.debian.org:
> found 946653 3.4.2-1~deb9u1
Bug #946653 [spamassassin] spamassassin: specially crafted messages can exhaust
system resources resulting in a denial of service
Marked as found in versions spamassassin/3.4.2-1~deb9u1.
> thanks
Stopping processing
Processing commands for cont...@bugs.debian.org:
> fixed 946653 3.4.3~rc6-1
Bug #946653 [spamassassin] spamassassin: specially crafted messages can exhaust
system resources resulting in a denial of service
There is no source info for the package 'spamassassin' at version '3.4.3~rc6-1'
with
Processing commands for cont...@bugs.debian.org:
> found 946652 3.4.2-1~deb9u1
Bug #946652 [spamassassin] spamassassin arbitrary code execution via malicious
sa-update servers
Marked as found in versions spamassassin/3.4.2-1~deb9u1.
> thanks
Stopping processing here.
Please contact me if you
Processing commands for cont...@bugs.debian.org:
> fixed 946652 3.4.3~rc6-1
Bug #946652 [spamassassin] spamassassin arbitrary code execution via malicious
sa-update servers
There is no source info for the package 'spamassassin' at version '3.4.3~rc6-1'
with architecture ''
Unable to make a
On Thu, Dec 12, 2019 at 03:49:13PM -0500, Scott Talbert wrote:
> >
> > That hint was helpful anyway and I get further now. I think now the
> > problem is to convince scons to install in $(CURDIR)/debian/tmp which
> > seems to try rather /usr/share/pdb2pqr directly:
>
> Looks like the
On 12/11/19 11:10 PM, Salvatore Bonaccorso wrote:
> Source: keystone
> Version: 2:16.0.0-4
> Severity: grave
> Tags: security upstream
> Forwarded: https://bugs.launchpad.net/keystone/+bug/1855080
>
> Hi,
>
> The following vulnerability was published for keystone.
>
> CVE-2019-19687[0]:
> |
Package: spamassassin
Version: 3.4.2-1
Severity: grave
Tags: upstream fixed-upstream pending security
Per upstream's 3.4.3 release announcement:
Apache SpamAssassin 3.4.3 was recently released [1], and fixes an issue
of security note where a message can be crafted in a way to use
excessive
Your message dated Thu, 12 Dec 2019 22:03:13 +0100
with message-id <9e3ee8e6-e325-a07a-ed5b-d171d1431...@debian.org>
and subject line Re: Bug#946630: openstack-cluster-installer-agent: syntax error
has caused the Debian Bug report #946630,
regarding openstack-cluster-installer-agent: syntax error
Package: spamassassin
Version: 3.4.2-1
Severity: grave
Tags: security upstream fixed-upstream pending
Per upstream's release announcement:
Apache SpamAssassin 3.4.3 was recently released [1], and fixes an issue
of security note where nefarious CF files can be configured to run
system commands
On Thu, 12 Dec 2019, Andreas Tille wrote:
On Thu, 12 Dec 2019, Andreas Tille wrote:
I don't see any Python3 changes in that repository. Did you push your
changes?
Argh, its pushed now.
Anyway, the problem is likely in CopySubAction in site_scons/site_init.py.
On line 111, the file
On Thu, 12 Dec 2019 11:09:51 +0100 =?UTF-8?Q?Holger_Schr=c3=b6der?= <
holgi@gmx.de> wrote:
> Hi.
>
> Same problem here. The reason is the patch 07_default-tab-title.patch. I
> rebuilt Tilix without this patch and everything works again.
>
> Holger...
>
As a quick fix:
1. in file
Your message dated Thu, 12 Dec 2019 20:40:48 +
with message-id
and subject line Bug#942686: fixed in python-apsw 3.30.1-r1-1
has caused the Debian Bug report #942686,
regarding fix the installation of 3.8 extensions
to be marked as done.
This means that you claim that the problem has been
Hi Scott,
On Thu, Dec 12, 2019 at 11:31:09AM -0500, Scott Talbert wrote:
> On Thu, 12 Dec 2019, Andreas Tille wrote:
>
> I don't see any Python3 changes in that repository. Did you push your
> changes?
Argh, its pushed now.
> Anyway, the problem is likely in CopySubAction in
Package: chromium
Version: 79.0.3945.79-1
Severity: grave
Too bad.
It was good while it lasted.
But this new version today... within a few minutes...
Received signal 11 SEGV_MAPERR
#22 0x564ff676a0c6
#23 0x564ff3c983e5 ChromeMain
#24 0x7f94706cfbbb __libc_start_main
#25
Your message dated Thu, 12 Dec 2019 19:19:14 +
with message-id
and subject line Bug#946639: fixed in iwd 1.2-2
has caused the Debian Bug report #946639,
regarding iwd 1.2-1 is crashing making WiFi access impossible
to be marked as done.
This means that you claim that the problem has been
Your message dated Thu, 12 Dec 2019 18:51:19 +
with message-id
and subject line Bug#946532: fixed in uranium 3.3.0-2
has caused the Debian Bug report #946532,
regarding uranium: build depends on cruft package
to be marked as done.
This means that you claim that the problem has been dealt
On Dec 11, Aurelien Jarno wrote:
> On 2019-12-11 17:54, Marco d'Itri wrote:
> > On Dec 11, Thorsten Glaser wrote:
> >
> > > Thankfully, I had a root session in a chroot open and used
> > > the program, statically linked, from http://koltsoff.com/pub/getroot/
> > > to recover access outside the
Hello.
The fix in 2018-7 was incomplete, even with some NMUs and rebuilds.
Please ignore this request.
Sorry for the noise.
> > Rename libgpr.(a|so) to libgnatprj because the grpc source owns them.
> your reverse dependencies [...] don't find the now removed library files
This upload was an error. I am going to revert the changes and let
libgpr3-dev conflict with libgprc-dev.
The libgpr->libgnatprj renaming is
Your message dated Thu, 12 Dec 2019 18:06:19 +
with message-id
and subject line Bug#946597: fixed in python-apt 1.9.2
has caused the Debian Bug report #946597,
regarding python-apt: security regression in 1.9.1
to be marked as done.
This means that you claim that the problem has been dealt
Your message dated Thu, 12 Dec 2019 18:04:45 +
with message-id
and subject line Bug#936164: fixed in auto-07p 0.9.2+dfsg-1
has caused the Debian Bug report #936164,
regarding auto-07p: Python2 removal in sid/bullseye
to be marked as done.
This means that you claim that the problem has been
Your message dated Thu, 12 Dec 2019 17:34:40 +
with message-id
and subject line Bug#946532: fixed in uranium 3.3.0-1.1
has caused the Debian Bug report #946532,
regarding uranium: build depends on cruft package
to be marked as done.
This means that you claim that the problem has been dealt
Control: tags -1 + upstream fixed-upstream patch
Dear Maintainer,
I tried to have a look at this crash
and I guess I found something.
The "Code:" sequence points to src/scan.c:1706.
There it seems like variable sr got a null pointer
and therefore the assignment crashes.
(gdb) list
Processing control commands:
> tags -1 + upstream fixed-upstream patch
Bug #946639 [iwd] iwd 1.2-1 is crashing making WiFi access impossible
Added tag(s) fixed-upstream, patch, and upstream.
--
946639: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=946639
Debian Bug Tracking System
Contact
(Forgot to attach some more debugging details.)
From submitter
Dec 12 09:40:11 lambda kernel: [55486.381334] iwd[202645]: segfault at 38 ip
55b1995e2056 sp 7ffc966c5360 error 6 in iwd[55b1995c4000+84000]
Dec 12 09:40:11 lambda kernel: [55486.381374] Code: 48 83 c4 20 e9 58 fe ff ff
0f
On 12/12/2019 15.31, Andreas Beckmann wrote:
> This could be
> related to pocl being rebuilt for the hwloc 1->2 transition.
hwloc is a red herring, it already occurred with the old one
Andreas
On 12/12/2019 16.33, Graham Inggs wrote:
> On 2019/12/12 16:25, Andreas Beckmann wrote:
>> I can reproduce the error in the silx tests in sid. This could be
>> related to pocl being rebuilt for the hwloc 1->2 transition.
>
> Silx's autopkgtests started failing in unstable on 2019-11-15 [1].
>
adding the pyopenssl dependency, I have the next errors:
=== FAILURES ===
test_list_cg_by_src_net_domain
driver =
def test_list_cg_by_src_net_domain(driver):
nd =
Your message dated Thu, 12 Dec 2019 16:49:53 +
with message-id
and subject line Bug#946626: fixed in minia 3.2.1+git20191130.5b131b9-1
has caused the Debian Bug report #946626,
regarding minia ftbfs with libgatbcore3
to be marked as done.
This means that you claim that the problem has been
Package: stardict
Followup-For: Bug #911207
Hi,
Commented in the MR on salsa.d.o.
Best regards,
-Andrew
On Thu, 12 Dec 2019, Andreas Tille wrote:
Control: tags -1 help
Hi,
it seems pdb2pqr is orphaned upstream. However, it seems to be worth
keeping inside Debian thus I tried my luck to port it to Python3 in
Git[1]. Unfortunately the build runs into
scons: Building targets ...
Hi Paul,
looking at the debci results[1] I see that the test is passing 10 tests
in a row since 2019-10-29 05:19:47 UTC. Do you agree that we can at
least lower severity of this bug to something else than "serious". I
need to admit that also do not know what to do here as Olivier said in
his
Processing control commands:
> tags -1 help
Bug #937262 [src:pdb2pqr] pdb2pqr: Python2 removal in sid/bullseye
Added tag(s) help.
--
937262: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=937262
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
Control: tags -1 help
Hi,
it seems pdb2pqr is orphaned upstream. However, it seems to be worth
keeping inside Debian thus I tried my luck to port it to Python3 in
Git[1]. Unfortunately the build runs into
scons: Building targets ...
CopySubAction("pdb2pqr.py", "pdb2pqr.py.in")
On 2019/12/12 16:25, Andreas Beckmann wrote:
I can reproduce the error in the silx tests in sid. This could be
related to pocl being rebuilt for the hwloc 1->2 transition.
Silx's autopkgtests started failing in unstable on 2019-11-15 [1].
Pocl was binNMU'd for hwloc15 on 2019-11-27 [2].
[1]
Dear Nicolas,
On Sat, 30 Nov 2019 12:04:09 + Nicolas Boulenguez
wrote:
> gprbuild (2018-7) unstable; urgency=medium
> .
>* Rename libgpr.(a|so) to libgnatprj because the grpc source owns them.
> Closes: #945197. Previous libgnatprj*-dev own libgnatprj.(a|so), but
> Depend:
Package: iwd
Version: 1.2-1
Severity: grave
Justification: renders package unusable
Dear Maintainer,
I upgraded my Debian testing system to the latest version of Bullseye,
and I was completely unable to connect to wireless. In the logs, I see
that iwd is crashing:
Dec 12 09:40:11 lambda
Your message dated Thu, 12 Dec 2019 15:00:13 +
with message-id
and subject line Bug#932543: fixed in python-pbcommand
1.1.1+git20191122.ec024c3-1
has caused the Debian Bug report #932543,
regarding Please switch to Python 3
to be marked as done.
This means that you claim that the problem
Your message dated Thu, 12 Dec 2019 14:43:22 +
with message-id
and subject line Bug#945338: fixed in petsc 3.11.4+dfsg1-4
has caused the Debian Bug report #945338,
regarding libpetsc3.11-dev-examples: postinst uses /usr/share/doc content
(Policy 12.3):
Your message dated Thu, 12 Dec 2019 14:40:58 +
with message-id
and subject line Bug#945840: fixed in ledger 3.1.3-1
has caused the Debian Bug report #945840,
regarding /usr/bin/ledger: error while loading shared libraries:
libboost_python27.so.1.67.0: cannot open shared object file: No such
Your message dated Thu, 12 Dec 2019 14:40:58 +
with message-id
and subject line Bug#945840: fixed in ledger 3.1.3-1
has caused the Debian Bug report #945840,
regarding Broken by boost dropping Python 2 support
to be marked as done.
This means that you claim that the problem has been dealt
Followup-For: Bug #946582
I can reproduce the error in the silx tests in sid. This could be
related to pocl being rebuilt for the hwloc 1->2 transition.
I'm trying to get a minimal pyopencl testcase from the silx maintainers
(#946422).
Andreas
> > https://salsa.debian.org/python-team/modules/matplotlib/commit/b343a4fcf363853002b509d022dde143691f099a
> >
> >
> > drop Qt4 from depends; Closes: #941527
> >
Followup-For: Bug #946422
Hi,
I can reproduce the error in the silx tests in sid. This could be
related to pocl being rebuilt for the hwloc 1->2 transition.
This looks like it should be reproducible with just pyopencl.
Can you minimize the failing test to a simple script using pyopencl
only?
Processing commands for cont...@bugs.debian.org:
> tags 936450 + experimental
Bug #936450 {Done: Yaroslav Halchenko } [src:duecredit]
duecredit: Python2 removal in sid/bullseye
Added tag(s) experimental.
> found 946583 1.3-9
Bug #946583 [pocl] silx: autopkgtest regression: pocl error
Bug #946582
Processing commands for cont...@bugs.debian.org:
> severity 942182 grave
Bug #942182 [keepalived] keepalived: gets stuck when receive queue of the raw
socket fills up, fixed upstream in 2.0.12
Severity set to 'grave' from 'important'
> thanks
Stopping processing here.
Please contact me if you
Control: tag -1 pending
Hello,
Bug #915834 in irqbalance 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 #915834 [irqbalance] Breaks SSH connections, listens on \0
Added tag(s) pending.
--
915834: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=915834
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
Processing control commands:
> tag -1 pending
Bug #946597 [python-apt] python-apt: security regression in 1.9.1
Added tag(s) pending.
--
946597: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=946597
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
Control: tag -1 pending
Hello,
Bug #946597 in python-apt 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:
> severity -1 serious
Bug #946040 [pytest-pylint] Build fails with the new pylint version
Severity set to 'serious' from 'normal'
--
946040: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=946040
Debian Bug Tracking System
Contact ow...@bugs.debian.org with
Processing control commands:
> fixed -1 0.7.2-1
Bug #946465 [librust-rand+alloc-dev] librust-rand+alloc-dev: does not find
upgrade path from buster to bullseye
Marked as fixed in versions rust-rand/0.7.2-1.
--
946465: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=946465
Debian Bug Tracking
Control: fixed -1 0.7.2-1
Hi Wolfgang,
On 12/12/2019 13.13, Wolfgang Silbermayr wrote:
> On 12/9/19 3:38 PM, Andreas Beckmann wrote:
>> during a test with piuparts I noticed your package fails to upgrade from
>> 'buster'.
>> It installed fine in 'buster', then the upgrade to 'bullseye' fails.
>
On 12/9/19 3:38 PM, Andreas Beckmann wrote:
> Package: librust-rand+alloc-dev
> Version: 0.6.4-2
> Severity: serious
> User: debian...@lists.debian.org
> Usertags: piuparts
>
> Hi,
>
> during a test with piuparts I noticed your package fails to upgrade from
> 'buster'.
> It installed fine in
severity 943495 important
thanks
On Fri, 25 Oct 2019 15:30:10 +0200 Matthias Klose wrote:
>
> fix building with a new compiler warning when building for python3.8.
>
>
http://launchpadlibrarian.net/448395331/setools_4.2.2-1build1_4.2.2-1ubuntu1.diff.gz
>
>
I'm not too sure why this is RC.
Processing commands for cont...@bugs.debian.org:
> severity 943495 important
Bug #943495 [src:setools] fix building with a new compiler warning when
building for python3.8
Severity set to 'important' from 'serious'
> thanks
Stopping processing here.
Please contact me if you need assistance.
--
Your message dated Thu, 12 Dec 2019 11:49:19 +
with message-id
and subject line Bug#936899: fixed in libpam-mklocaluser 0.16
has caused the Debian Bug report #936899,
regarding libpam-mklocaluser: Python2 removal in sid/bullseye
to be marked as done.
This means that you claim that the
Package: src:libcloud
Version: 2.5.0-1
Severity: serious
Tags: sid bullseye
libcloud autopkg tests failing. Missing test dependency. Please run the autopkg
tests before uploading.
= test session starts ==
platform linux -- Python 3.7.5,
Processing control commands:
> tag -1 pending
Bug #936899 [src:libpam-mklocaluser] libpam-mklocaluser: Python2 removal in
sid/bullseye
Added tag(s) pending.
--
936899: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=936899
Debian Bug Tracking System
Contact ow...@bugs.debian.org with
Control: tag -1 pending
Hello,
Bug #936899 in libpam-mklocaluser 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: libkate
Version: 0.4.1-10
Severity: serious
X-Debbugs-CC: debian...@lists.debian.org
User: debian...@lists.debian.org
Usertags: regression
Dear maintainers,
With a recent upload of libkate the autopkgtest of libkate fails in
testing when that autopkgtest is run with the binary packages
Source: openstack-cluster-installer
Version: 21
Severity: grave
Justification: makes the package unusable
The agent contains the following on line 29:
ETH_SPEED=$(( $(lshw -class network 2>/dev/null -json | jq '.[] |
select(.serial|test("'${MAC_ADDR}'")) | .capacity') / 100))
The
Hi.
Same problem here. The reason is the patch 07_default-tab-title.patch. I
rebuilt Tilix without this patch and everything works again.
Holger...
Processing commands for cont...@bugs.debian.org:
> severity 946609 serious
Bug #946609 [resolvconf] resolvconf: broken init script: "/run/resolvconf is
neither a directory nor a symbolic link"
Severity set to 'serious' from 'normal'
> tags 946609 + pending
Bug #946609 [resolvconf] resolvconf:
Package: tilix
Version: 1.9.3-3
Severity: grave
Justification: renders package unusable
hey,
after latest upgrade to version 1.9.3-3, tilix won't start..
there was a post-install message during upgrade :
...
Processing triggers for libglib2.0-0:amd64 (2.62.3-2) ...
Processing control commands:
> severity -1 serious
Bug #935455 [src:python-xarray] python-xarray: autopkgtest regression:
test_dask fails
Severity set to 'serious' from 'normal'
--
935455: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=935455
Debian Bug Tracking System
Contact
Hi Sandro!
On Mon, Nov 25, 2019 at 12:52:56AM +, Sandro Tosi wrote:
> Control: tag -1 pending
>
> Hello,
>
> Bug #941527 in matplotlib 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
Source: minia
Version: 3.2.1-1
Severity: serious
Justification: ftbfs
Tags: ftbfs sid bullseye
Dear maintainer,
Your package is part of the libgatbcore3 transition. I tried to binNMU
your package but it fails to build from source. Please have a look.
On top of that, the latest version of your
Hi Till,
it's been a while since we last met. I hope you're doing well.
> I have done several fixes on cups-filters upstream now, please try a
> current GIT
> snapshot of cups-filters.
Just tried and don't really see a difference:
Thu Dec 12 09:50:50 2019 Unable to get PPD file for B...: The
Processing control commands:
> reassign -1 ftp.debian.org
Bug #855494 [mgltools-pmv] mgltools-pmv: runPmv does not start
Bug reassigned from package 'mgltools-pmv' to 'ftp.debian.org'.
No longer marked as found in versions mgltools-pmv/1.5.7-1.
Ignoring request to alter fixed versions of bug
Control: reassign -1 ftp.debian.org
Control: retitle -1 ROM: Please remove package mgltools-pmv
As the discussion below and the bug log shows: mgltools-pmv does not
start and nobody seems to have a clue to make it work.
Kind regards, Andreas.
On Mon, Jan 01, 2018 at 09:21:33PM +0100, Andreas
Your message dated Thu, 12 Dec 2019 08:35:21 +
with message-id
and subject line Bug#946539: fixed in predictprotein 1.1.09-2
has caused the Debian Bug report #946539,
regarding predictprotein: depends on removed transitional package blast2
to be marked as done.
This means that you claim that
Hi Rebecca,
On Sat, 7 Dec 2019 06:43:15 + peter green wrote:
> > Should the package attempt to clean this up (and if so is there a better
> > method than unconditionally deleting those directories), or is
> > permanently leaving this behind (to become more and more obsolete, and
> >
Hey,
Guillem Jover schrob:
> Actually, and this is something I've had pending raising for a long
> time, I don't understand that two s-s-d invocations pattern in stop
> which seems a bit pointless TBH? The --retry should make s-s-d wait
> for the child to exit, or terminate it forcibly.
I think
Source: scipy
Version: 1.3.3-2
X-Debbugs-CC: debian...@lists.debian.org
Severity: serious
User: debian...@lists.debian.org
Usertags: timeout flaky
Dear maintainers,
Your package has an autopkgtest, great. However, I noticed that it
regularly fails without very clear changes. On top of that, very
Processing commands for cont...@bugs.debian.org:
> fixed 940919 19.10.2~ds0-1
Bug #940919 [python3-cxx-dev] python3-cxx-dev: removal of python3-cxx-dev makes
files disappear from python-cxx-dev
There is no source info for the package 'python3-cxx-dev' at version
'19.10.2~ds0-1' with
Source: python-scipy
Version: 1.2.2-7
X-Debbugs-CC: debian...@lists.debian.org
Severity: serious
User: debian...@lists.debian.org
Usertags: timeout flaky
Dear maintainers,
Your package has an autopkgtest, great. However, I noticed that it
regularly fails without very clear changes. On top of
93 matches
Mail list logo
