On Fri, Sep 13, 2019 at 05:16:30PM +0800, Drew Parsons wrote:
> Python maintainers, remember, check your reverse dependencies before
> dropping your python2 packages.
> Check each of
>
> build-rdeps python-yourmodule
> apt-rdepends -r python-yourmodule
>
> and confirm the package has rdeps=0
On Thu, Sep 12, 2019 at 08:30:20AM +0200, Thomas Goirand wrote:
> I wont comment on the relative import ambiguity problem, as Ghislain
> replied correctly. However, I do want to comment on 2to3.
>
> I generally recommend against using it, in the favor of other tools. For
> example, you can use six
On Thu, Sep 12, 2019 at 09:17:08AM +0200, Andreas Tille wrote:
> > > $ cycle
> > > Traceback (most recent call last):
> > > File "/usr/bin/cycle", line 12, in
> > > from dialogs import *
> > > File "/usr/share/cycle/dialogs.py", line 8, in
> > > from cal_year import cycle, Val
> > >
On Wed, Sep 11, 2019 at 04:12:34PM +0200, Andreas Tille wrote:
> Control: tags -1 help
>
> On Wed, Sep 11, 2019 at 09:33:54AM -0300, Antonio Terceiro wrote:
> > E: Sub-process /usr/bin/dpkg returned an error code (1)
> > ~[100]$ cycle
> > File "/usr/bin/cycle", line 29
> > if lang_find:
> >
On Thu, Sep 05, 2019 at 07:42:15PM +0200, Andreas Tille wrote:
> for some reason I do not understand are the dependencies of the
> binary package
>
> Depends: python3-numpy (>= 1:1.16.0~rc1), python3-numpy-abi9, python3:any,
> python:any
>
>
> How can I get rid of the python:any dependency?
You
Package: ftp.debian.org
Severity: normal
User: debian-python@lists.debian.org
Usertags: py2removal
Doesn't work with current Django. No new upstream versions in Debian
since the first upload in 2010. The homepage is dead.
--
WBR, wRAR
signature.asc
Description: PGP signature
Package: ftp.debian.org
Severity: normal
User: debian-python@lists.debian.org
Usertags: py2removal
The version in Debian is released in 2009, no upstream releases since
then.
The package doesn't work, according to its RC bugs.
--
WBR, wRAR
signature.asc
Description: PGP signature
Package: ftp.debian.org
Severity: normal
User: debian-python@lists.debian.org
Usertags: py2removal
Doesn't support modern Django and FTBFS because of that (#933146).
Popcon 20.
--
WBR, wRAR
signature.asc
Description: PGP signature
Package: ftp.debian.org
Severity: normal
User: debian-python@lists.debian.org
Usertags: py2removal
The package FTBFS (#918418).
Ships a Python 2 subpackage which can't be dropped because of that FTBFS.
Popcon 11.
--
WBR, wRAR
signature.asc
Description: PGP signature
Package: ftp.debian.org
Severity: normal
User: debian-python@lists.debian.org
Usertags: py2removal
Doesn't support modern Django and FTBFS because of that (#865293).
Ships a Python 2 subpackage which can't be dropped because of that FTBFS.
Popcon 15 and less.
--
WBR, wRAR
signature.asc
Descri
Package: ftp.debian.org
Severity: normal
User: debian-python@lists.debian.org
Usertags: py2removal
The upstream code doesn't support Python 3 and there is no ongoing effort
or even an upstream issue about this.
Popcon 491. This is probably caused by sagemath, which depends on it in
oldstable but
Package: ftp.debian.org
Severity: normal
User: debian-python@lists.debian.org
Usertags: py2removal
No upstream releases since 2007.
Popcon 46.
--
WBR, wRAR
signature.asc
Description: PGP signature
Package: ftp.debian.org
Severity: normal
User: debian-python@lists.debian.org
Usertags: py2removal
No upstream releases since 2009.
Popcon 41.
--
WBR, wRAR
signature.asc
Description: PGP signature
On Mon, Sep 02, 2019 at 04:43:40PM +0800, Drew Parsons wrote:
> Looks great, is plenty enough accurate for the task. It tells us it's more
> important to process live-task-standard than python-gnatpython-doc.
Not necessarily.
live-task-standard just depends on python, without any other python2 dep
Package: ftp.debian.org
Severity: normal
User: debian-python@lists.debian.org
Usertags: py2removal
No upstream releases since 2010.
Popcon is 19.
Reverse deps checked with dak rm -Rnb python-mocker
--
WBR, wRAR
signature.asc
Description: PGP signature
On Sat, Aug 31, 2019 at 07:10:43PM +0200, Raphael Hertzog wrote:
> Looking at the status of the packages in the team, it's quite clear that
> the team is MIA as a whole:
> https://qa.debian.org/developer.php?email=pkg-zope-develop...@lists.alioth.debian.org
>
> The only recent upload is from TANIG
On Sat, Aug 31, 2019 at 11:50:33AM -0400, Scott Kitterman wrote:
> > > I definitely think it will be helpful. Thanks for putting it together.
> > > It's the best thing I've seen yet for answering the question of what can
> > > we try to kill off now.
> > >
> > > Please keep it updated.
> >
> >
On Sat, Aug 31, 2019 at 10:20:32AM -0400, Scott Kitterman wrote:
> I definitely think it will be helpful. Thanks for putting it together. It's
> the best thing I've seen yet for answering the question of what can we try to
> kill off now.
>
> Please keep it updated.
Please note though that all
On Sat, Aug 31, 2019 at 11:33:54AM +0900, Norbert Preining wrote:
> here are two questions: one concerning adopting/updating mechanize and
> how to deal with rdepends, one concerning how to fix tests with special
> requirements in pybuild.
>
> For calibre and porting to python3, I need mechanize f
Package: ftp.debian.org
Severity: normal
User: debian-python@lists.debian.org
Usertag: py2removal
Depends and build-depends on python3-protorpc-standalone which is not
installable on Python 3.7, and on python-oauth2client which is dropped
from Debian.
Reverse deps checked with dak rm -Rn python-g
Package: ftp.debian.org
Severity: normal
User: debian-python@lists.debian.org
Usertag: py2removal
From the O bug (#906195): "If it is still RC buggy at the time of the
freeze, I'll ask for its removal from Debian."
The only reverse dep is python-googlecloudapis which has other problems
and isn't
Package: ftp.debian.org
Severity: normal
User: debian-python@lists.debian.org
Usertag: py2removal
Control: block -1 by 935073
Control: block -1 by 911171
According to #884616 (RC bug on python-visual) and #911171 (RC bug on
epigrass) it's broken and should not be used. Its only reverse dep is
epig
Package: ftp.debian.org
Severity: normal
User: debian-python@lists.debian.org
Usertag: py2removal
http://www.nullcube.com/software/pygdchart2.html (from the O bug) is dead.
No new releases in Debian since initial packaging in 2005.
The only reverse dep is rebuildd for which an RM bug was just file
Package: ftp.debian.org
Severity: normal
User: debian-python@lists.debian.org
Usertag: py2removal
Native package by a retired DD. Homepage gives 404. Last release in 2012.
Popcon 8.
Depends on several py2 packages.
Reverse deps checked with dak rm -Rnb rebuildd
--
WBR, wRAR
signature.asc
Desc
Package: ftp.debian.org
Severity: normal
User: debian-python@lists.debian.org
Usertag: py2removal
Source in Debian was first packaged in 1999.
Depends on cruft python-imaging.
Reverse deps checked with dak rm -Rnb python-htmlgen
--
WBR, wRAR
signature.asc
Description: PGP signature
On Mon, Aug 26, 2019 at 08:20:13AM +0200, Guðjón Guðjónsson wrote:
> > The correct procedure is running “gbp pq import” *before* importing a new
> > tarball. Then after importing you do “gbp pq rebase”.
> In fact I did do that.
Then you would get an error message when trying to do that second time.
On Sun, Aug 25, 2019 at 10:01:02PM +0200, Guðjón Guðjónsson wrote:
> > > Isn't this an error. Shouldn't it be git checkout?
> > > $ gbp checkout debian/master
> > Yes.
> You mean it should be git checkout?
Yes.
> > If you ran gbp pq import after importing the new tarball and it didn't say
> > "Pat
On Sun, Aug 25, 2019 at 09:40:16PM +0200, Guðjón Guðjónsson wrote:
> Isn't this an error. Shouldn't it be git checkout?
> $ gbp checkout debian/master
Yes.
> But I still find working with patch queues difficult especially with
> new upstream where the old patches don't apply correctly.
> I tried t
Package: ftp.debian.org
Severity: normal
User: debian-python@lists.debian.org
Usertag: py2removal
https://github.com/piranha/opster/ supports Python 3.
Popcon is 14.
Reverse deps checked with dak rm -Rnb python-opster
--
WBR, wRAR
signature.asc
Description: PGP signature
Package: ftp.debian.org
Severity: normal
User: debian-python@lists.debian.org
Usertag: py2removal
There is no upstream development at https://bitbucket.org/arjan/txosc since
2011.
Popcon is 6.
Reverse deps checked with dak rm -Rnb python-txosc
--
WBR, wRAR
signature.asc
Description: PGP sig
Package: ftp.debian.org
Severity: normal
User: debian-python@lists.debian.org
Usertag: py2removal
No upstream releases since 2008.
Popcon is 17.
Reverse deps checked with dak rm -Rnb python-unipath
--
WBR, wRAR
signature.asc
Description: PGP signature
Package: ftp.debian.org
Severity: normal
User: debian-python@lists.debian.org
Usertag: py2removal
The current upstream code claims to support Python 3.
Popcon is 14.
Reverse deps checked with dak rm -Rnb python-translitcodec
--
WBR, wRAR
signature.asc
Description: PGP signature
Package: ftp.debian.org
Severity: normal
User: debian-python@lists.debian.org
Usertag: py2removal
Latest upstream code supports Python 3. There is a Python 3 request bug,
#737790, 5.5 years old.
Popcon is 34.
Reverse deps checked with dak rm -Rnb python-xmlrunner
--
WBR, wRAR
signature.asc
D
Package: ftp.debian.org
Severity: normal
User: debian-python@lists.debian.org
Usertag: py2removal
The package is Python 2 only and depends on celery which is Python 3 only.
It also depends on libjs-twitter-bootstrap which will be removed too
(#908424). The upstream code supports Python 3.
Reverse
Package: ftp.debian.org
Severity: normal
User: debian-python@lists.debian.org
Usertag: py2removal
I couldn't find if the upstream source supports Python 3.
Reverse deps checked with dak rm -Rnb python-libavg
--
WBR, wRAR
signature.asc
Description: PGP signature
Package: ftp.debian.org
Severity: normal
User: debian-python@lists.debian.org
Usertag: py2removal
No upstream releases since the last packaged one in 2012.
python3-xcffib description says "This package is intended to be a (mostly)
drop-in replacement for xpyb. xpyb has an inactive upstream, sever
Package: ftp.debian.org
Severity: normal
User: debian-python@lists.debian.org
Usertag: py2removal
The latest upstream code at https://github.com/pearu/pyvtk seems to
support Python 3, but the Debian package contains code from 2007.
Reverse deps checked with dak rm -Rnb python-pyvtk
--
WBR, wRAR
Package: ftp.debian.org
Severity: normal
User: debian-python@lists.debian.org
Usertag: py2removal
Looks like it doesn't work at all in the current state.
Reverse deps checked with dak rm -Rn python-uniconvertor
--
WBR, wRAR
signature.asc
Description: PGP signature
Package: ftp.debian.org
Severity: normal
User: debian-python@lists.debian.org
Usertag: py2removal
Last release in 2009.
Reverse deps checked with dak rm -Rnb python-excelerator
--
WBR, wRAR
signature.asc
Description: PGP signature
Package: ftp.debian.org
Severity: normal
User: debian-python@lists.debian.org
Usertag: py2removal
There is some Py3 fork at https://github.com/tynn/PyAO
Reverse deps checked with dak rm -Rn pyao
--
WBR, wRAR
signature.asc
Description: PGP signature
Package: ftp.debian.org
Severity: normal
User: debian-python@lists.debian.org
Usertag: py2removal
Upstream Python 3 bugreport:
https://bitbucket.org/blais/optcomplete/issues/2/python3-compatibility
Reverse deps checked with dak rm -Rnb python-optcomplete
--
WBR, wRAR
signature.asc
Descriptio
Package: ftp.debian.org
Severity: normal
User: debian-python@lists.debian.org
Usertag: py2removal
Last upstream commit in 2012.
Reverse deps checked with dak rm -Rnb python-m2ext
--
WBR, wRAR
signature.asc
Description: PGP signature
Package: ftp.debian.org
Severity: normal
User: debian-python@lists.debian.org
Usertag: py2removal
Last release in 2003.
Reverse deps checked with dak rm -Rnb python-jabber
--
WBR, wRAR
signature.asc
Description: PGP signature
Package: ftp.debian.org
Severity: normal
User: debian-python@lists.debian.org
Usertag: py2removal
No upstream releases since 2009.
Reverse deps checked with dak rm -Rnb python-gpiv
--
WBR, wRAR
signature.asc
Description: PGP signature
On Wed, Jul 24, 2019 at 01:35:35AM +0200, Piotr Ożarowski wrote:
> During DebConf19 we¹ have tried to figure out how to manage Python 2 and PyPy
> module removal from Debian and below is our proposal.
> After discussing it on this mailing list we plan to send an email to
> debian-devel@l.d.o with a
On Thu, Aug 15, 2019 at 02:08:41PM +0200, Thomas Goirand wrote:
> Hi there!
>
> According to the daily graph I built here:
> http://py2graph.infomaniak.ch/py2.7.deps.svg
>
> we can work on Python 2 removal for the below packages. Note that I have
> *not* checked for reverse dependencies, please d
On Tue, Aug 13, 2019 at 11:05:33AM -0700, Joseph Herlant wrote:
> > Yes, this is the third email on this in the last month, previous two
> > didn't get any replies.
>
> Sorry I didn't mean to anger you or be disrespectful in any way. My
> apologies if I did.
I wasn't angered, the second of those w
On Tue, Aug 13, 2019 at 10:16:28AM -0700, Joseph Herlant wrote:
> While tidying up some packages before taking some time off I realized
> that some packages like django-tables had binary packages that took
> the convention of creating -doc packages using -doc (a
> very long time ago).
>
> The resu
On Tue, Aug 13, 2019 at 11:38:33AM +0100, peter green wrote:
> One package that stood out from the rest was python-monotonic.
> python-monotonic is maintained by the Debian openstack team, but it doesn't
> seem to be in any way openstack specific, nor does upstream seem to have
> dropped python2
Hello. While removing a py2 subpackage I noticed the following difference:
- in the old version -doc ships /usr/share/doc/python-foo/
- in the new version -doc ships /usr/share/doc/python-foo-doc/
During the new version build process, dh_installdocs complains about
main package auto-detection. You
On Fri, Jul 19, 2019 at 01:57:11PM -0400, Scott Talbert wrote:
> > > I'm running dh_python2 in a package on a non-standard directory path so it
> > > will handle byte compilation, etc. However, it seems to be removing empty
> > > directories from the directory tree. Is there any way to avoid this
On Fri, Jul 19, 2019 at 01:32:47PM -0400, Scott Talbert wrote:
> I'm running dh_python2 in a package on a non-standard directory path so it
> will handle byte compilation, etc. However, it seems to be removing empty
> directories from the directory tree. Is there any way to avoid this
> behavior?
On Tue, Jul 16, 2019 at 10:52:14AM -0400, Paul Tagliamonte wrote:
> I lost some of this thread - should we request a transition
> from the release team? I was looking for the list of blockers
> to dropping Python 2 and couldn't find anything except this
> thread (where we're still figuring out what
On Mon, Jul 08, 2019 at 07:16:01AM +, PICCA Frederic-Emmanuel wrote:
> it would be nice, if the python2 packages could be skipped in bulleye but not
> for backports in buster.
>
> Is it something which could be envision ?
Not in the main backports, maybe in -sloppy. And it will be hard or
imp
On Thu, Mar 21, 2019 at 10:09:22AM +, MARIE Alexandre wrote:
> override_dh_installdocs:
> ln -s /usr/share/javascript/mathjax/MathJax.js
> $(CURDIR)/doc/build/html/_static/MathJax.js
> find doc/build/html -name "*.html" -exec sed -i
> "s|https://cdn.mathjax.org/mathjax/latest/Ma
On Mon, Mar 18, 2019 at 03:20:24PM +, MARIE Alexandre wrote:
> gbp:error: Automatic merge failed.
You need to find why there are conflicts and fix them. Good first steps
are running gbp with --no-rollback and/or finding what upstream files are
modified in the master branch in the current state.
On Fri, Feb 22, 2019 at 02:15:43PM +, MARIE Alexandre wrote:
> Sorry, my mistake, the name of the package is python-xrayutilities !*
No such package in Debian either (and if it existed, my apt search command
would return it).
There is only an old RFP #723017.
This is not related to the topic of
Telling us the commands you used to get to this stage would be helpful, I
think. Right now it's only clear that the listed files are different in
the upstream and in the master branches, but dgit already told you that.
Also, what is the package name? "apt search xrayutilities" returns nothing
for m
On Thu, Feb 14, 2019 at 09:43:19PM +, llu...@autistici.org wrote:
> I changed the strategy to git revert and now I am able to build the package
> with the following commands:
>
> gbp clone g...@salsa.debian.org:python-team/applications/visualequation.git
> cd visualequation/
> uscan
> git reve
I have no idea about gbp-pq but I guess resetting just master is not
enough to fix that repo.
Please also note that force pushes are bad and deleting tags in published
repos doesn't really work so please don't do that, especially when the
problem is mainly with the unpublished pq branch and some f
Both your patches look very wrong. How did you make them? The patch
patching debian/changelog looks especially wrong.
--
WBR, wRAR
signature.asc
Description: PGP signature
On Sat, Jan 12, 2019 at 04:39:44PM +0100, Bastian Venthur wrote:
> >> The question is: if I drop Python2 support, what happens with the
> >> package names? Should I simply provide the python3-debianbts and
> >> drop python-debianbts, or shall I attempt some kind of migration
> >> to make the python
On Fri, Oct 19, 2018 at 11:17:31PM +0200, Jerome Kieffer wrote:
> > Salsa is only for official Debian packages. Are you going to update
> > python-rfoo in Debian?
>
> Well, I created the version which is in debian for a few years and yes,
> I would like to update it (with migration to python3, ...
On Fri, Oct 19, 2018 at 09:13:30PM +0200, Jerome Kieffer wrote:
> I am a python developer and from time-to-time I also build some
> packages. I recently re-built python-rfoo for the latest version and I
> was suggest to make the packaging on salsa. Does the Debian-Python
> community have recommenda
On Mon, Sep 10, 2018 at 04:33:21PM +0200, Andreas Tille wrote:
> Hi,
>
> looking at the bug log of scikit-learn[1] it seems to be a simple means to do
>
> --- a/debian/control
> +++ b/debian/control
> @@ -20,6 +20,7 @@ Build-Depends: debhelper (>= 9), dh-autoreconf,
> python3-pyte
On Wed, Aug 29, 2018 at 11:18:50PM -0300, eamanu15 wrote:
> When I build the package using gbp:
>
> *gbp buildpackage --git-upstream-tag="v%(version)s" --git-ignore-new*
>
> This create some other files/folder like this:
> build/
> debian/.debhelper/
> debian/debhelper-build-stamp
> debian/files
On Sun, Aug 26, 2018 at 08:59:21PM +0200, Andreas Tille wrote:
> I try to package porechop[1] but somehow it does not find its dynamic
> library. If I install the resulting package I get:
>
> $ porechop
> could not find cpp_functions.so - please reinstall
SO_FILE = 'cpp_functions.so'
SO_FILE_FU
On Sun, Jul 29, 2018 at 09:57:50PM +0530, Manas Kashyap wrote:
> Thats what i am saying , the previous author changed some files to upstream
What do you mean? How did they do that?
--
WBR, wRAR
signature.asc
Description: PGP signature
On Sun, Jul 29, 2018 at 09:40:44PM +0530, Manas Kashyap wrote:
> While building package i am encountering an error , as per my knowledge the
> changes are made and so they have to be a new patch for it , so should i
> create one or is there some other error , which i don't know .
> error is http://
On Wed, Jul 18, 2018 at 09:00:15AM -0400, Dean Serenevy wrote:
> Hello, I am a user of the python3-kivy package and just noticed that kivy is
> no longer listed in buster [1].
>
> Is help needed? (I am not a DD, but I am willing to test and submit packaging
> patches if it would help.)
https://b
On Mon, Jul 16, 2018 at 09:44:00AM +0200, Bastian Venthur wrote:
> sorry if this question has been asked before. What is the currently
> recommended way to make `python` point to `python3`? I'd like to have it set
> on a system default level if possible.
We don't recommend it so there is none AFAIK
On Wed, Jun 06, 2018 at 10:20:13PM +0530, shirish शिरीष wrote:
> Maybe it would have been better to say that right now python gives
>
> $ python --version
> Python 2.7.15
>
> To be more precise, I meant to know if 'Bullseye' i.e Debian 11 would
> have python 3.0 as default or not.
/usr/bin/pytho
On Wed, Jun 06, 2018 at 08:38:56PM +0530, shirish शिरीष wrote:
> I was just looking for documentation about what's keeping us from
> getting to python 3
Depends on your definition of "getting to python 3".
> I have also been trying to understand which packages/modules are
> remaining for python 3
On Mon, Jun 04, 2018 at 05:01:21PM -0400, Yaroslav Halchenko wrote:
> I would've expected some info or error message though
> (since I do request python3 explicitly in the call to dh),
I think pybuild doesn't care about --with python3
Maybe it could, though.
--
WBR, wRAR
signature.asc
Descripti
On Tue, Jun 05, 2018 at 12:11:21AM -0400, Scott Talbert wrote:
> Yes, I'm talking about the automatically generated -dbgsym packages that
> contain the /usr/lib/debug/.build-id/... files.
Have you read Scott's email?
--
WBR, wRAR
signature.asc
Description: PGP signature
On Mon, Jun 04, 2018 at 03:38:09PM -0400, Yaroslav Halchenko wrote:
> I am trying to make our DataLad package to be bi-python finally, but I
> cannot make pybuilder
It's "pybuild".
> neither populate python3-datalad package, nor
> to run tests (using nose) during the build against python3 (runs o
On Wed, Apr 25, 2018 at 10:00:51AM +0700, Nguyễn Hồng Quân wrote:
> Do you mean to use "
> python3.6_3.6.1-1.debian.tar.xz" (of 3.6.1) and change its number to
> "python3.6_3.6.4-4.debian.tar.xz" (of 3.6.4) and change its changelog
> content?
No, I meant to use the debian/ directory from that tar
On Wed, Apr 25, 2018 at 12:11:03AM +0700, Nguyễn Hồng Quân wrote:
> On Wed, Apr 25, 2018 at 12:05 AM, Andrey Rahmatullin
> wrote:
>
> >
> > How is this related to my suggestion?
> >
>
>
> Your suggestion is:
>
> "
>
> Adapt it from
On Wed, Apr 25, 2018 at 12:01:45AM +0700, Nguyễn Hồng Quân wrote:
> On Tue, Apr 24, 2018 at 11:45 PM, Andrey Rahmatullin wrote:
>
> > > > Adapt it from the 3.6.1 one?
> > > >
> > >
> > > Excuse me. What do you mean by "adapt"?
On Tue, Apr 24, 2018 at 10:07:03PM +0700, Nguyễn Hồng Quân wrote:
> So, I try to build Python as deb and use apt to install to my board. I was
> successful to do so with Python 3.6.1, using the .dsc file found on Debian
> buster repo. But since Python 3.6.4, the build script has changed
> drastica
On Tue, Apr 24, 2018 at 05:27:08PM +0700, Nguyễn Hồng Quân wrote:
> > It's not enough to backport the interpreter, all binary modules will need
> > to be recompiled too.
> >
>
> Why?
To be able to be imported in Python3.6.
--
WBR, wRAR
signature.asc
Description: PGP signature
On Tue, Apr 24, 2018 at 01:58:23PM +0700, Nguyễn Hồng Quân wrote:
> Could you please provide an official packaging script for Python 3.6 and
> Debian 9?
It's not enough to backport the interpreter, all binary modules will need
to be recompiled too.
--
WBR, wRAR
signature.asc
Description: PGP si
On Mon, Apr 09, 2018 at 01:01:20PM +0200, Andreas Tille wrote:
> > > As per [2] I added dh-python to the Build-Depends but it seems I would
> > > need python-minimal in addition to get /usr/bin/pyversions. For me it
> > > is a bit strange to realise that this basic functionality is not provided
>
On Mon, Apr 09, 2018 at 09:45:52AM +0200, Andreas Tille wrote:
> As per [2] I added dh-python to the Build-Depends but it seems I would
> need python-minimal in addition to get /usr/bin/pyversions. For me it
> is a bit strange to realise that this basic functionality is not provided
> by dh-python
On Wed, Mar 28, 2018 at 09:21:16AM -0400, Scott Talbert wrote:
> > > I've got a package where I need to pass an argument to setup.py as part of
> > > the build process. Is there a way to do this with dh_python2, ie, without
> > > using overrides?
> > dh_python2 doesn't call setup.py, the build sys
On Wed, Mar 28, 2018 at 09:00:13AM -0400, Scott Talbert wrote:
> I've got a package where I need to pass an argument to setup.py as part of
> the build process. Is there a way to do this with dh_python2, ie, without
> using overrides?
dh_python2 doesn't call setup.py, the build system (python_dist
On Fri, Mar 23, 2018 at 06:23:21PM +, Weatherby,Gerard wrote:
> My test debian/postinst is:
Debhelper config files without the subpackage package name apply to the
first subpackage and not to all subpackages as you apparently think.
--
WBR, wRAR
signature.asc
Description: PGP signature
On Sun, Feb 11, 2018 at 11:47:37PM +0100, Andreas Tille wrote:
> I'm pretty sure that will ring a bell for some Python3 programmer and I
> hope to be able to fix this quickly with your help to be able to easily
> provide the Python3 version in addition to Python2.
The package code does not support
On Tue, Jan 09, 2018 at 11:49:39AM +0100, Guðjón Guðjónsson wrote:
> Hi list
>
> I would like to close bug: #787300 <787...@bugs.debian.org>
>
> and ask for removal of pyqwt5 plus some more Qt4 only packages. But I
> cannot find
>
> info on how to ask for removal of package from the Debian distr
On Sun, Oct 01, 2017 at 06:38:03PM +0200, W. Martin Borgert wrote:
> PS: Is there maybe something broken with the quoting function of
> your MUA? I cannot differentiate between text written by you and
> quoted text. There is no '> ' or whatever...
That's how text parts of text+html mails often look
On Sun, Oct 01, 2017 at 04:52:55PM +0200, W. Martin Borgert wrote:
> I usually start to use software, when it arrives in Debian.
> Or I package it. If there is some snap or other third party
> package, I'm unsure how to work with it:
>
> How to install?
I expand the tarball to ~
> How to uninsta
On Tue, Aug 29, 2017 at 10:32:44AM +1000, Ben Finney wrote:
> > After the events of April, I've realized that I have a lot less time,
> > and to be frankly honest, motivation for contributing to Debian right
> > now. So I'm scaling back, but not retiring.
>
> (I don't know what “the events of Apri
On Thu, Aug 17, 2017 at 09:16:25AM +, PICCA Frederic-Emmanuel wrote:
> When it comes to python:Depends, I try to add the right entries in the
> setup.py
Isn't just adding the package names to Depends easier?
> I: dh_python2 pydist:220: Cannot find package that provides opengl. Please
> add p
On Fri, Aug 04, 2017 at 11:39:50AM +0200, Gudjon I. Gudjonsson wrote:
> Hi list
>
> I wanted to fix my terrible track record lately, fix bugs and update my
> packages
> but I ran into problems with sbuild on my package eric.
>
> dpkg-buildpackage -B fails with the following error message:
>
>
On Wed, Mar 22, 2017 at 11:15:06PM +0100, Ángel Luis wrote:
> I am trying to package |numpy 1.12.1| into deb package.
testing, unstable and jessie-backports contain 1.12.0.
If you really need 1.12.1 you should start with the existing package and
update it, not write all the packaging from scratch.
On Tue, Feb 07, 2017 at 08:50:02AM -0500, Thomas Nyberg wrote:
> I've been looking at the offlineimap package on my system (jessie), but in
> my case `/usr/bin/offlineimap` is _not_ a symlink. Also the python code is
> not installed to `/usr/share/offlineimap` and instead to
> `/usr/share/pyshared/
On Tue, Mar 15, 2016 at 11:20:12AM +0100, Matthias Klose wrote:
> I would like to come up with a recommendation that if a python module ships
> scripts, Python3 is used for these scripts, and the Python2 version of these
> scripts should be dropped (and python -m ...) should be used instead. An
>
On Wed, Jan 13, 2016 at 06:43:31PM +1100, Brian May wrote:
> Running virtualenv with interpreter /tmp/bbb/bin/python2
Huh?
> Using real prefix '/usr'
> New python executable in /tmp/virtual/bin/python2
> Also creating executable in /tmp/virtual/bin/python
> Installing setuptools, pip...done.
> bri
On Sat, Jan 02, 2016 at 08:18:13AM -0800, Ant Dude wrote:
> Again, I renamed the old requests directory for me to use pip again. :(
Why don't you just uninstall the package you've installed manually to
/usr/local? It seems to me you don't need it.
--
WBR, wRAR
signature.asc
Description: PGP sig
On Sun, Oct 25, 2015 at 12:39:44PM +0200, Onur Aslan wrote:
> > Nothing is invoking autoreconf unless you use --with autoreconf. Are you
> > saying that with pybuild this option has no effect?
>
> I am already using --with autoreconf but when I use:
>
> dh $@ --with autoreconf,python2,python3
101 - 200 of 236 matches
Mail list logo
