Hi Scott,
> > > The package doesn't look all that complicated. I can take a stab at
> > > trying
> > > to port it to Python 3. If I get it working, perhaps I can ask you to
> > > test
> > > it?
> >
> > that would be awesome! I can definitely do the testing.
>
> I submitted a merge request
Your message dated Thu, 05 Dec 2019 06:31:00 +
with message-id
and subject line Bug#945793: Removed package(s) from unstable
has caused the Debian Bug report #945644,
regarding gif2png: Python2 removal in sid/bullseye
to be marked as done.
This means that you claim that the problem has been
Your message dated Thu, 05 Dec 2019 06:31:00 +
with message-id
and subject line Bug#945793: Removed package(s) from unstable
has caused the Debian Bug report #930858,
regarding gif2png: "not expected to be able to deal with arbitrarily broken
input"
to be marked as done.
This means that you
Your message dated Thu, 05 Dec 2019 06:32:02 +
with message-id
and subject line Bug#946182: Removed package(s) from unstable
has caused the Debian Bug report #943039,
regarding disper: Python2 removal in sid/bullseye
to be marked as done.
This means that you claim that the problem has been
Your message dated Thu, 05 Dec 2019 06:32:02 +
with message-id
and subject line Bug#946182: Removed package(s) from unstable
has caused the Debian Bug report #844505,
regarding disper -S → Segmentation fault
to be marked as done.
This means that you claim that the problem has been dealt
Your message dated Thu, 05 Dec 2019 06:30:11 +
with message-id
and subject line Bug#945775: Removed package(s) from unstable
has caused the Debian Bug report #938188,
regarding python-sponge: Python2 removal in sid/bullseye
to be marked as done.
This means that you claim that the problem has
Your message dated Thu, 05 Dec 2019 06:29:20 +
with message-id
and subject line Bug#940232: Removed package(s) from unstable
has caused the Debian Bug report #922116,
regarding tulip - FTBFS - error: there are no arguments to 'memcpy' that depend
on a template parameter
to be marked as done.
Your message dated Thu, 05 Dec 2019 06:29:47 +
with message-id
and subject line Bug#945179: Removed package(s) from unstable
has caused the Debian Bug report #925689,
regarding gamera: ftbfs with GCC-9
to be marked as done.
This means that you claim that the problem has been dealt with.
If
Your message dated Thu, 05 Dec 2019 06:30:11 +
with message-id
and subject line Bug#945775: Removed package(s) from unstable
has caused the Debian Bug report #866470,
regarding python-sponge: depends on obsolete python-imaging (replace with
python3-pil or python-pil)
to be marked as done.
Your message dated Thu, 05 Dec 2019 06:29:20 +
with message-id
and subject line Bug#940232: Removed package(s) from unstable
has caused the Debian Bug report #853688,
regarding tulip: ftbfs with GCC-7
to be marked as done.
This means that you claim that the problem has been dealt with.
If
Your message dated Thu, 05 Dec 2019 06:29:20 +
with message-id
and subject line Bug#940232: Removed package(s) from unstable
has caused the Debian Bug report #938723,
regarding tulip: Python2 removal in sid/bullseye
to be marked as done.
This means that you claim that the problem has been
Your message dated Thu, 05 Dec 2019 06:27:34 +
with message-id
and subject line Bug#937420: Removed package(s) from unstable
has caused the Debian Bug report #937420,
regarding RM: pydhcplib -- removal triggered by the Python2 removal
to be marked as done.
This means that you claim that the
Your message dated Thu, 05 Dec 2019 06:28:03 +
with message-id
and subject line Bug#937476: Removed package(s) from unstable
has caused the Debian Bug report #937476,
regarding RM: pymappergui -- RoQA; dead upstream; unmaintained; low popcon;
blocking py2 removal
to be marked as done.
This
Your message dated Thu, 05 Dec 2019 06:26:17 +
with message-id
and subject line Bug#919039: Removed package(s) from unstable
has caused the Debian Bug report #945691,
regarding linuxbrew-wrapper: Python2 removal in sid/bullseye
to be marked as done.
This means that you claim that the problem
Your message dated Thu, 05 Dec 2019 06:27:14 +
with message-id
and subject line Bug#930143: Removed package(s) from unstable
has caused the Debian Bug report #938650,
regarding tessa: Python2 removal in sid/bullseye
to be marked as done.
This means that you claim that the problem has been
Your message dated Thu, 05 Dec 2019 06:23:48 +
with message-id
and subject line Bug#834337: Removed package(s) from unstable
has caused the Debian Bug report #938853,
regarding xnbd: Python2 removal in sid/bullseye
to be marked as done.
This means that you claim that the problem has been
Your message dated Thu, 05 Dec 2019 06:21:16 +
with message-id
and subject line Bug#574013: Removed package(s) from unstable
has caused the Debian Bug report #945650,
regarding ccontrol: Python2 removal in sid/bullseye
to be marked as done.
This means that you claim that the problem has been
Your message dated Thu, 05 Dec 2019 06:24:20 +
with message-id
and subject line Bug#836421: Removed package(s) from unstable
has caused the Debian Bug report #945671,
regarding fofix-dfsg: Python2 removal in sid/bullseye
to be marked as done.
This means that you claim that the problem has
Your message dated Thu, 05 Dec 2019 06:22:14 +
with message-id
and subject line Bug#814894: Removed package(s) from unstable
has caused the Debian Bug report #937044,
regarding mididings: Python2 removal in sid/bullseye
to be marked as done.
This means that you claim that the problem has
Your message dated Thu, 05 Dec 2019 06:21:46 +
with message-id
and subject line Bug#681042: Removed package(s) from unstable
has caused the Debian Bug report #945658,
regarding ladr: Python2 removal in sid/bullseye
to be marked as done.
This means that you claim that the problem has been
Your message dated Thu, 05 Dec 2019 06:21:16 +
with message-id
and subject line Bug#574013: Removed package(s) from unstable
has caused the Debian Bug report #885519,
regarding ccontrol: Recommends unmaintained pygtk
to be marked as done.
This means that you claim that the problem has been
Hi,
This extension seems to work with Python 3 after one import change:
-from MediaInfoDLL import *
+from MediaInfoDLL3 import *
After that, it also needs a dependency change from python-mediainfodll
to python3-mediainfodll.
Hi Moritz,
I started to work on qt5 port of SCIM. There is some remaining blocks.
I will work on it for another 10 days.
I want to postpone to deadline to Dec 15, if that does not drag the QT5
migration too much.
Thank you for your understanding!
Yours,
Benda
Processing control commands:
> severity -1 serious
Bug #936834 [src:ledger] ledger: Python2 removal in sid/bullseye
Severity set to 'serious' from 'normal'
--
936834: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=936834
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
Your message dated Wed, 04 Dec 2019 22:19:51 +
with message-id
and subject line Bug#938859: fixed in yade 2019.12~git~0~e74819ea-1~exp1
has caused the Debian Bug report #938859,
regarding yade: Python2 removal in sid/bullseye
to be marked as done.
This means that you claim that the problem
The control email got bounced before unarchiving, here are the details of new
findings.
- Mail original -
> unarchive 921220
> reopen 921220
> retitle 921220 xchat.desktop makes invalid use of %U, breaks at least
> lxqt and flwm
> affects 921220 + lxqt flwm
> severity 921220 grave
>
Processing commands for cont...@bugs.debian.org:
> tags 936886 + help
Bug #936886 [src:libktoblzcheck] libktoblzcheck: Python2 removal in sid/bullseye
Added tag(s) help.
> thanks
Stopping processing here.
Please contact me if you need assistance.
--
936886:
Status update:
I started working on removing the python 2 package, which turned out to
be more complicated than necessary. I had to rip out a broken chunk from
CMakeLists.txt that caused the build to fail when no Python interpreter
is installed. This made at least the build succeed again, but
Processing commands for cont...@bugs.debian.org:
> unarchive 921220
Bug #921220 {Done: Gianfranco Costamagna } [xchat]
xchat stops autoconnecting, complaining about "%U" and "host unknown", broken
.desktop entry ?
Unarchived Bug 921220
> reopen 921220
Bug #921220 {Done: Gianfranco Costamagna }
On Wed, 27 Nov 2019 17:17:32 +0100 Alf Gaida wrote:
> new mpv 0.30* don't play well with smplayer in sid - new 19.10.* will solve
> that problem.
>
> No action needed right now, will work on it.
Salsa shows as latest commit "prepare to upload" (of version 19.10.2).
Why hasn't it been uploaded
Source: fusionforge
Severity: serious
There hasn't been an upload since two years and fusionforge missed the last two
stable releases and has gathered five RC bugs at this point. Should it be
removed?
Cheers,
Moritz
Your message dated Wed, 04 Dec 2019 21:20:01 +
with message-id
and subject line Bug#945328: fixed in pyzmq 17.1.2-4
has caused the Debian Bug report #945328,
regarding pyzmq ftbfs in unstable
to be marked as done.
This means that you claim that the problem has been dealt with.
If this is not
On Sat, Aug 24, 2019 at 02:07:26AM -0400, Scott Kitterman wrote:
> On Mon, 15 Apr 2019 09:01:29 -0400 Scott Kitterman
> wrote:
> > Package: src:tumgreyspf
> > Version: 1.36-4.1
> > Severity: important
> >
> > Python2.7 will go out of upstream security support during the Bullseye
> > development
Source: knot-resolver
Version: 3.2.1-3
Severity: grave
Tags: security upstream
Hi,
The following vulnerability was published for knot-resolver.
CVE-2019-19331[0], but see [1] for more details.
If you fix the vulnerability please also make sure to include the
CVE (Common Vulnerabilities &
Package: lxcfs
Version: 2.0.7-1+deb9u1
Severity: grave
Here's lxc log:
lxc-start 20191204112931.787 INFO lxc_cgroup -
cgroups/cgroup.c:cgroup_init:68 - cgroup driver cgroupfs initing for debian-test
lxc-start 20191204112931.790 ERRORlxc_cgfs -
Your message dated Wed, 04 Dec 2019 20:50:59 +
with message-id
and subject line Bug#946021: fixed in qtpass 1.3.2-1
has caused the Debian Bug report #946021,
regarding qtpass: Invoking results in SegFault
to be marked as done.
This means that you claim that the problem has been dealt with.
On Wed, 4 Dec 2019, Florian Schlichting wrote:
The package doesn't look all that complicated. I can take a stab at trying
to port it to Python 3. If I get it working, perhaps I can ask you to test
it?
that would be awesome! I can definitely do the testing.
I submitted a merge request on
Your message dated Wed, 04 Dec 2019 18:53:51 +
with message-id
and subject line Bug#944821: fixed in popper.js 1.14.6+ds2-3
has caused the Debian Bug report #944821,
regarding Unhandled (and undocumented) directory to symlink (and vice versa)
change breaks on upgrade
to be marked as done.
Processing commands for cont...@bugs.debian.org:
> severity 918163 serious
Bug #918163 [xul-ext-sieve] Broken in Stretch
Severity set to 'serious' from 'grave'
> thanks
Stopping processing here.
Please contact me if you need assistance.
--
918163:
Control: tags -1 stretch
Control: tags -1 buster
Control: tags -1 sid
Control: severity - 1 serious
Hi, and once again this package isn't working anymore due the API change
for AddOns that are introduced by Thunderbird 68.x
Thunderbird now requires AddOns that are build as webextension.
So far
Processing control commands:
> tags -1 stretch
Bug #918163 [xul-ext-sieve] Broken in Stretch
Added tag(s) stretch.
> tags -1 buster
Bug #918163 [xul-ext-sieve] Broken in Stretch
Added tag(s) buster.
> tags -1 sid
Bug #918163 [xul-ext-sieve] Broken in Stretch
Added tag(s) sid.
> severity - 1
Processing control commands:
> tag -1 pending
Bug #944821 [src:popper.js] Unhandled (and undocumented) directory to symlink
(and vice versa) change breaks on upgrade
Added tag(s) pending.
--
944821: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=944821
Debian Bug Tracking System
Contact
Control: tag -1 pending
Hello,
Bug #944821 in popper.js 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, 04 Dec 2019 17:35:41 +
with message-id
and subject line Bug#944242: fixed in python-biopython 1.75+dfsg-1
has caused the Debian Bug report #944242,
regarding fix build & test issues with Python 3.8
to be marked as done.
This means that you claim that the problem has
Yes, ignore that one please.
That test has since been disabled (and replaced with a more robust one).
We eventually traced test_chapter_align_line_02819 failing on 32 bit
systems with a different overflow error:
https://github.com/biopython/biopython/pull/2297
Thanks,
Peter
On Wed, Dec 4,
Package: pyfai
Version: 0.18.0+dfsg1-3
Followup-For: Bug #945411
"pocl error: lt_dlopen("(null)") or lt_dlsym() failed with 'can't close
resident module'"
That suggests pocl is not yet built against python3.8
Package: pyfai
Followup-For: Bug #945411
On the other hand, python3-pyopencl is indeed built against python3.8.
So need to dig deeper.
Your message dated Wed, 04 Dec 2019 16:49:53 +
with message-id
and subject line Bug#946146: fixed in astlib 0.11.3-1
has caused the Debian Bug report #946146,
regarding Tests are failing
to be marked as done.
This means that you claim that the problem has been dealt with.
If this is not the
Hi Scott,
> The package doesn't look all that complicated. I can take a stab at trying
> to port it to Python 3. If I get it working, perhaps I can ask you to test
> it?
that would be awesome! I can definitely do the testing.
Florian
On Wed, Dec 04, 2019 at 01:55:26PM +, Peter Cock wrote:
> Good. If you are still missing Tests/Fasta/flowers.pro.gz that's odd,
> since it was in the official tar ball:
>
>
On Wed, 4 Dec 2019, Florian Schlichting wrote:
Do you have any plans to port gitso to Python 3?
If not, I will probably just convert this to an RM request as it seems gitso
is unmaintained upstream for many years.
I have in fact started to look into porting gitso to Python 3, but
haven't
Hi Scott,
> Do you have any plans to port gitso to Python 3?
>
> If not, I will probably just convert this to an RM request as it seems gitso
> is unmaintained upstream for many years.
I have in fact started to look into porting gitso to Python 3, but
haven't spent enough time on it to be able
Processing commands for cont...@bugs.debian.org:
> reassign 946161 src:dia
Bug #946161 [dia] dia: CVE-2019-19451: Endless loop on filenames with invalid
encoding can be used for denial-of-service
Bug reassigned from package 'dia' to 'src:dia'.
No longer marked as found in versions
Hi,
On Wed, 4 Dec 2019 at 16:03, Boyuan Yang wrote:
> I have no idea why the package would have to go through NEW. Removing package
> does not need to go throught NEW and it's much faster (usually needs only 1 or
> 2 days).
No, I’m talking about a compat package in darkslide. I still want it
to
在 2019-12-04三的 15:00 +0100，Andrej Shadura写道：
> Hi,
>
> On Tue, 3 Dec 2019 at 15:54, Boyuan Yang wrote:
> > Currently package landslide FTBFS in Sid. I noticed that it was just made
> > into
> > a compatibility package with nothing inside. This is unnecessary, plus
> > that
> > current setup
Your message dated Wed, 04 Dec 2019 14:55:43 +
with message-id
and subject line Bug#946061: fixed in landslide 1.1.3+0
has caused the Debian Bug report #946061,
regarding landslide: FTBFS; Package should be removed instead of being made
into compat pkg
to be marked as done.
This means that
Package: dia
Version: 0.97.3+git20160930-8.1
Severity: critical
Tags: security upstream
Justification: breaks the whole system
Dear Maintainer,
when GNOME Dia before 2019-11-27 is launched with a filename argument
that is not a valid codepoint in the current encoding, it enters an
endless loop,
Your message dated Wed, 04 Dec 2019 14:50:07 +
with message-id
and subject line Bug#946155: fixed in fscrypt 0.2.5-2
has caused the Debian Bug report #946155,
regarding libpam-fscrypt: PAM module config broken
to be marked as done.
This means that you claim that the problem has been dealt
Control: tag -1 pending
Hello,
Bug #946155 in fscrypt 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 #946155 [libpam-fscrypt] libpam-fscrypt: PAM module config broken
Added tag(s) pending.
--
946155: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=946155
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
Hi,
On Tue, 3 Dec 2019 at 15:54, Boyuan Yang wrote:
> Currently package landslide FTBFS in Sid. I noticed that it was just made into
> a compatibility package with nothing inside. This is unnecessary, plus that
> current setup actually fails to build from source.
>
> Since python-landslide has
Good. If you are still missing Tests/Fasta/flowers.pro.gz that's odd,
since it was in the official tar ball:
https://files.pythonhosted.org/packages/33/55/becf2b99556588d22b542f3412990bfc79b674e198d9bc58f7bbc333439e/biopython-1.75.tar.gz
Peter
On Tue, Dec 3, 2019 at 9:13 PM Andreas Tille
Processing commands for cont...@bugs.debian.org:
> notfound 944776 prepair/0.7.1-3+b2
Bug #944776 [src:prepair] FTBFS with CGAL 5.0
The source prepair and version 0.7.1-3+b2 do not appear to match any binary
packages
No longer marked as found in versions prepair/0.7.1-3+b2.
> found 944776
Hi Chris,
On Tue, Dec 03, 2019 at 09:25:42PM +0100, Chris Lamb wrote:
> Dear Salvatore,
>
> > > Security team, would you like an upload for stable?
> >
> > As far I can see this issue has been introduced around 2.1 where the
> > search support for view permissions and a read-only admin support
Alex Hofbauer wrote on 04/12/2019:
> Package: libpam-fscrypt
> Version: 0.2.4-2
> Severity: grave
> Justification: renders package unusable
>
> Hi!
>
> Apparently in the latest version (0.2.5-1) the path substitution was broken,
> resulting in "PAM_INSTALL_PATH" being used instead of the library
Your message dated Wed, 04 Dec 2019 12:34:39 +
with message-id
and subject line Bug#942235: fixed in dask 2.8.1+dfsg-0.1
has caused the Debian Bug report #942235,
regarding dask: autopkgtest needs update for new version of pytest
to be marked as done.
This means that you claim that the
Package: libpam-fscrypt
Version: 0.2.4-2
Severity: grave
Justification: renders package unusable
Hi!
Apparently in the latest version (0.2.5-1) the path substitution was broken,
resulting in "PAM_INSTALL_PATH" being used instead of the library name
"pam_fscrypt.so".
This killed decryption
Your message dated Wed, 04 Dec 2019 11:37:03 +
with message-id
and subject line Bug#935352: fixed in trimage 1.0.6-1
has caused the Debian Bug report #935352,
regarding trimage: Qt4 removal from Bullseye
to be marked as done.
This means that you claim that the problem has been dealt with.
If
Your message dated Wed, 04 Dec 2019 11:37:03 +
with message-id
and subject line Bug#938720: fixed in trimage 1.0.6-1
has caused the Debian Bug report #938720,
regarding trimage: Python2 removal in sid/bullseye
to be marked as done.
This means that you claim that the problem has been dealt
On Wed, Dec 04, 2019 at 09:55:00AM +0100, Kilian Valkhof wrote:
> Someone did it for me back in 2010 when it was first added as I didn't have
> the know-how. I think most of the configuration from then still works and I
> would be very grateful if someone could pick this up after we did the work
>
Your message dated Wed, 4 Dec 2019 14:21:46 +0300
with message-id
and subject line Closing the bug
has caused the Debian Bug report #936678,
regarding gumbo-parser: Python2 removal in sid/bullseye
to be marked as done.
This means that you claim that the problem has been dealt with.
If this is
Processing commands for cont...@bugs.debian.org:
> reassign 946146 python3-astlib 0.11.2-1
Bug #946146 [ginga] Tests are failing
Bug reassigned from package 'ginga' to 'python3-astlib'.
No longer marked as found in versions ginga/3.0.0-1.
Ignoring request to alter fixed versions of bug #946146 to
Processing commands for cont...@bugs.debian.org:
> severity 915504 serious
Bug #915504 [sbt] sbt: Fails to detect version of java
Severity set to 'serious' from 'grave'
> thanks
Stopping processing here.
Please contact me if you need assistance.
--
915504:
Your message dated Wed, 04 Dec 2019 18:30:18 +0800
with message-id <9d11a0458dc1234990ce84d94ae92c3927bc85f8.ca...@debian.org>
and subject line Re: SBT is uninstallable; depends on nonexistent packages
has caused the Debian Bug report #873341,
regarding SBT is uninstallable; depends on nonexistent
Processing commands for cont...@bugs.debian.org:
> tags 915504 + fixed-upstream
Bug #915504 [sbt] sbt: Fails to detect version of java
Added tag(s) fixed-upstream.
> forwarded 915504
>
Hi,
Made a mistake by sending this mail to 944353. This is where it belongs.
The issue described in this bug is fixed. However, after the update to
5.7.0-2, the new python3-paraview has no vtk dependencies (python3-
vtk7). Previously, paraview-python had dependencies on python-vtk6 and
Hi Stefan,
thanks a lot for your feedback.
On Tue, Dec 03, 2019 at 12:38:24PM -0800, Stefan van der Walt wrote:
> The problem here stems from an old version of Cython. My recommended
> approach would be to build from the git tag instead of the source tarball
> (i.e., the version without
Someone did it for me back in 2010 when it was first added as I didn't
have the know-how. I think most of the configuration from then still
works and I would be very grateful if someone could pick this up after
we did the work to migrate it to QT5 :)
Best,
Kilian
On 03-12-2019 22:52, Moritz
Your message dated Wed, 04 Dec 2019 08:47:40 +
with message-id
and subject line Bug#946004: fixed in satpy 0.16.1-5
has caused the Debian Bug report #946004,
regarding satpy: autopkgtest failures
to be marked as done.
This means that you claim that the problem has been dealt with.
If this is
79 matches
Mail list logo
