[Piotr Ożarowski, 2018-08-27]
> > rtupdate and postinst / prerm hooks for python3 packages currently call
> > py3{compile,clean} which only operates on cpython3.
> >
> > 5. Something else?
>
> modify these files and ship (renamed ones) in pypy3 package:
> err, you meant for python3-foo packages, so I guess option 3 is the best
> one.
err again (sorry, to many things at once), I meant option 4 (I can
change dh-python to generate additional checks for pypy{compile,clean})
--
GPG: 1D2F A898 58DA AF62 1786 2DF7 AEF6 F1A2 A745 7645
[Matthias Klose, 2018-09-25]
> > how about generating dependencies on python2.7 and moving
> > pycompile/pyclean there as well (this also solves pre-dependency issue)
> >
> >> - Not having a python package in bullseye (buster+1), but a
> >>python2 package doesn't point to any "default" anymor
> > err again (sorry, to many things at once), I meant option 4 (I can
> > change dh-python to generate additional checks for pypy{compile,clean})
>
> That'd be pypy3{compile,clean}
this is now available in dh-python 3.20180927. Only postinst files are
checking for pypy3compile, though. py3clean i
[Ole Streicher, 2018-09-28]
> For one of my packages (sunpy), I want to complete the switch to pybuild
> by removing the custom (and quite unperfect) dh_override_auto_test rule.
>
> Currently, I have the following lines in d/rules:
>
> override_dh_auto_test:
> python -m pytest sunpy -k "not
Control: tags -1 -help
Control: tags -1 patch
> I tried to fix the issue reported below by using
> dh_python3 --no-ext-rename
> (see [1]) but this has no effect and the resulting package just
> contains
well, --no-ext-rename should not be used for public modules (I cannot
imagine a single case
[PICCA Frederic-Emmanuel, 2018-10-12]
> to my opinion, the code is modify in place with 2to3.
> So the code on the source after the configuration is already converted to
> python3.
> And during the build process, with python2 the code is copied as it in the
> .pybuild place for python2
> with py
[Ole Streicher, 2018-10-20]
> W: python3-astropy: python-module-in-wrong-location
> usr/lib/python3.7/dist-packages/astropy/
> usr/lib/python3/dist-packages/astropy/
> W: python3-astropy: python-module-in-wrong-location
> usr/lib/python3.7/dist-packages/astropy/coordinates/
> usr/lib/python3/di
> Since I polished python-lzma I uploaded the package anyway with new
> Vcs fiels and other polishing stuff.
please don't remove -dbg packages, -dbgsym packages are useless for us, AFAICT
(python{,3}-foo-dbg packages contain modules for Python debug
interpreter, something that -dbgsym packages do
[Wookey, 2018-11-22]
> No advice on best way to start a python packaging template?
# apt install pypi2deb
$ py2dsp djangorestframework-filters
source package will be available in ./result/ (change it with --root)
you can add '--profile dpmt' if you want to maintain it inside DPMT
--
GPG: 1D2F A8
[Scott Kitterman, 2018-11-29]
> dh-python already doesn't use upstream version requirements when
> automatically
> extracting dependencies, so you have to check those yourself regardless of
> how
> you do it. This design decision was based on generally poor experiences with
> the accuracy of
[Daniele Tricoli, 2018-12-29]
> I'm already a member of DPMT (in the salsa group with my
> eriol-guest account), but now I have a DD account (eriol) and I would
> like to start using it.
congrats! :)
> Please add my DD account to DPMT group on salsa: vvidic
done :)
", line 1, in
> ImportError: No module named backports.functools_lru_cache
>
> If we add an __init__.py file under
>
> (unstable-amd64-sbuild)root@diffabs6:/usr/lib/python2.7/dist-packages/backports#
> touch __init__.py
I cannot reproduce it:
| (unstable-amd64-sbuild)
> Conceptually I think it's more relevant to override dh_auto_test. To make
> sure pytest will register the plugin one may tweak the $PYTHONPATH. That's
> the approach I followed in pytest-flask, see [1].
> [1]
> https://salsa.debian.org/python-team/modules/pytest-flask/blob/debian/master/debian/
> pkg_resources.DistributionNotFound: The 'easydev' distribution was not found
> and is required by the application
there are many ways to fix it (by creating egg-info data during build,
not only during install stage), but if upstream is updating __version__
in each version, then definitely the b
I added you to the team Andreas, sorry for the delay.
--
GPG: 1D2F A898 58DA AF62 1786 2DF7 AEF6 F1A2 A745 7645
[Ana Rodríguez López, 2019-03-17]
> I would like to upload Weblate (#796777). For that I have been working in
> some modules (social-auth-app-django, translation-finder, celery-batches)
> which are now being maintained by the DPMT. To continue with the remaining
> work I would like to join both the
[Daniel Manila, 2019-06-18]
> I would like to join PAPT because I am maintaining the weresync package
you're in. Sorry for taking it so long
--
GPG: 1D2F A898 58DA AF62 1786 2DF7 AEF6 F1A2 A745 7645
[William Grzybowski, 2019-06-26]
> That said I would like to contribute to DPMT, in special the python
> modules I am going to be using which many are asyncio related and some
> custom cython modules, including py-libzfs which now works with ZFS On
> Linux (soon to be official OpenZFS upstream).
w
[Louis-Philippe Véronneau, 2019-07-02]
> I would like to join the DPMT team.
welcome :)
--
GPG: 1D2F A898 58DA AF62 1786 2DF7 AEF6 F1A2 A745 7645
ort if possible).
DPMT / PAPT
===
No need to wait for a bug report. If you have a leaf package, remove it now.
If you're not a DD, do it in the git repo and ping Piotr.
[¹] Dimitri, Matthias, Piotr, Stefano, Thomas
[²]
https://lintian.debian.org/tags/missing-build-dependency-for-dh_-command.h
[PICCA Frederic-Emmanuel, 2019-09-28]
> Hello, I would like to know if there is an equivalent of
> cabal-debian[1] , which helps a lot maintaining haskell packages.
>
> I allow to do the initial packaging and also the upgrade of the
> packaging, by updating the Build-dependencies, etc...
sounds l
> Yes this is a known issue and we are currently waiting for an upload
> of dh-python to avoid automatic replacement of pylint by pylint3 when
> on python3 before pushing those changes further.
http://ftp.debian.org/debian/dists/unstable/main/Contents-amd64.gz
still contains pylint3 so I'm waiting
Hi,
Just to let you know: pypi.debian.net is now hosted on Infomaniak's
servers. Thanks to Thomas Goirand and other Infomaniak guys for setting
that up! (they sponsored lifetime free VPS! :)
I would also like to thank GPLHost for providing previous home for the
redirector for more than 4 years. T
[intrigeri, 2019-11-08]
> the PAPT umbrella; I'll co-maintain and sponsor; therefore, I need to
> join the PAPT.
>
> My Salsa handle is: intrigeri
>
> I've read
> https://salsa.debian.org/python-team/tools/python-modules/blob/master/policy.rst
> and I accept it.
welcome and sorry for the delay :
[Thomas Andrejak, 2019-11-24]
> Peter Wienemann
> proposed me to became a member of DPMT and I think this is a good idea !
>
> My salsa login is totol-guest
>
> I have read
> https://salsa.debian.org/python-team/tools/python-modules/blob/master/policy.rst
> and
> I accept it.
Welcome :)
--
GPG:
[Håvard Flaget Aasen, 2019-11-17]
> I wish to join the team. I don't bring any packages with me, but i intend to
> contribute to existing ones.
>
> I have read and accept the DPMT policy:
> https://salsa.debian.org/python-team/tools/python-modules/blob/master/policy.rst
>
> My salsa account is h
[Julian Gilbey, 2019-11-17]
> I currently maintain send2trash, and it was suggested to me by Sandro
> Tosi that I join the DPMT to team-maintain it. That sounds like an
> excellent idea to me!
>
> My salsa login is jdg
>
> I have read and accept the DPMT policy.
welcome and sorry for the delay
dist-packages/ is empty and there are .so files in
/usr/lib/python3/dist-packages/ and move them temporarily to
/usr/lib/python3.X/dist-packages/ (it knows which interpreter is used at
this point) and let dh_python3 rename them later
> Piotr, is this a bug in pybuild, or am I doing something w
FTR: I didn't change my mind. /usr/bin/python is still used outside
Debian packages, in /usr/local/bin scripts and applications and I
strongly disagree to touch it.
--
GPG: 1D2F A898 58DA AF62 1786 2DF7 AEF6 F1A2 A745 7645
[Zygmunt Krynicki, 2022-07-05]
> I'd like to join PAPT and DPMT to co-maintain west and several other Python
> packages related to or needed by the Zephyr project. I'm an old-timer, in a
> way, but I have not been very active in packaging before. I'm looking to
> improve my skills and actively main
sqlalchemy 2.X currently FTBFS due to a segmentation fault (3.11 and
3.12) somewhere in pysqlite:
[…]
test/orm/inheritance/test_assorted_poly.py::MultiOfTypeContainsEagerTest_joined::test_big_query[not_use_criteria-contains_eager]
PASSED
group.
[1] http://home.gna.org/gaupol/
http://debian.pox.one.pl/gaupol_0.4.0-1_all.deb
--
-=[ Piotr Ozarowski ]=-
-=[ http://www.ozarowski.pl ]=-
pgpfpxZZr67yQ.pgp
Description: PGP signature
old - there are 2 new
upstream versions. I'll ask author if he still wants to maintain it.
--
-=[ Piotr Ozarowski ]=-
-=[ http://www.ozarowski.pl ]=-
pgpA1XEImfCJn.pgp
Description: PGP signature
from: http://debian.pox.one.pl/
BTW: I have permission to take over from Seo Sanghyeon
--
-=[ Piotr Ozarowski ]=-
-=[ http://www.ozarowski.pl ]=-
pgpAlGbfoH9Hq.pgp
Description: PGP signature
n
> packaging, along the lines of [1].
done
Thanks for your comments!
--
-=[ Piotr Ozarowski ]=-
-=[ http://www.ozarowski.pl ]=-
pgpgSJHQgLTHB.pgp
Description: PGP signature
W: I have followed python-imaging package example and installed
C sources to /usr/include/python2.X/package/ directories. Is it obligatory
to include them? python-central seems to not use them and I don't see a
reason to include them, specially duplicating that files for every python
versi
-externally-managed parameter passed to
`setup.py install` or DEB_PYTHON_INSTALL_ARGS_ALL (CDBS)
* Egg's dirname's issue (python's/module's version in dirname)
--
-=[ Piotr Ozarowski ]=-
-=[ http://www.ozarowski.pl ]=-
pgpQfkJw9XNz9.pgp
Description: PGP signature
version will change? You will have to reupload
your package.
--
-=[ Piotr Ozarowski ]=-
-=[ http://www.ozarowski.pl ]=-
pgp8URMDc0ZFZ.pgp
Description: PGP signature
Graham Wilson ([EMAIL PROTECTED]):
> On Tue, Jun 13, 2006 at 11:22:27PM +0200, Piotr Ozarowski wrote:
> > What if default python version will change? You will have to reupload
> > your package.
>
> That would happen anyway for new Python releases, plus, my understanding
&
e to #!/usr/bin/python2.4),
will you upload new package just for him?
--
-=[ Piotr Ozarowski ]=-
-=[ http://www.ozarowski.pl ]=-
pgpqIbTlGHk8W.pgp
Description: PGP signature
es.
>
> comments ?
I think a better idea is to use Standards-Version as we did before
(version 3.8.0 should be released)
--
-=[ Piotr Ozarowski ]=-
-=[ http://www.ozarowski.pl ]=-
pgp4iiJXoK5ET.pgp
Description: PGP signature
Pierre Habouzit ([EMAIL PROTECTED]):
> Le jeu 15 juin 2006 10:50, Piotr Ozarowski a écrit :
> > I think a better idea is to use Standards-Version as we did before
> > (version 3.8.0 should be released)
>
> well the thing is there is no way to track all the packages that *h
of python and not python related packages.
>
> Thouth I think it's handy, but it's not more than a suggestion, I don't
> really care about that.
If you will be sure that _every_ package that should follow a subpolicy
will have such field, than ok. It's
5.8.8-6 Larry Wall's Practical Extraction
ii po-debconf 1.0.2 manage translated Debconf template
debhelper recommends no packages.
-- no debconf information
--
-=[ Piotr Ozarowski ]=-
-=[ http://www.ozarowski.pl ]=-
pgprx5Wnn6eJo.pgp
Description: PGP signature
severity 373853 wishlist
thanks
Raphael Hertzog ([EMAIL PROTECTED]):
> On Fri, 16 Jun 2006, Piotr Ozarowski wrote:
> > I have following line in debian/control (source section)
> > XS-Python-Version: >= 2.4
> >
> > and in generated *.substvars file:
> > pyth
der by hand
and remove it as soon as all external packages will depend on
python-foo only
--
-=[ Piotr Ozarowski ]=-
-=[ http://www.ozarowski.pl ]=-
pgpukOh5709tM.pgp
Description: PGP signature
lup package, but a python-flup package is not
> currently usable in Debian if it depends on python 2.4.
debhelper 5.0.37.1 had a bug and sometimes it generated python (>=2.4)
dependency (see [1]), 5.0.37.2 works fine
[1] http://lists.debian.org/debian-python/2006/06/msg00208.html
dependency (see [1]), 5.0.37.2 works fine
>
> Which is completely irrelevant when the OP specified that python-flub *does
> require* python 2.4 or later.
In this case - yes. My point is that it was possible to build a package
against unstable which depends on python (>= 2.4)
--
-=[
n't use
"version (>= version)" syntax.
For arch indep packages use just "all" or ">= 2.3"
For arch dep packages, you need to add "any" part
("any", "any, >=2.3", "any, >=2.3, <<2.5", ...)
--
-=[ Piotr Ozarowski ]=-
-=[ http://www.ozarowski.pl ]=-
pgpKo4gA5rdCS.pgp
Description: PGP signature
Piotr Ozarowski ([EMAIL PROTECTED]):
> For arch dep packages, you need to add "any" part
> ("any", "any, >=2.3", "any, >=2.3, <<2.5", ...)
heh, you need to add "any" to Architecture header, not to
XS-Python-Version of cou
ebian.pox.one.pl/sqlalchemy_0.2.4-0.1.dsc
gaupol is also available via collab-maint SVN repo (alioth)
and chardet is in python-modules repository (DPMT)
[1] http://lists.debian.org/debian-qa/2006/06/msg00088.html
--
-=[ Piotr Ozarowski ]=-
-=[ http://www.ozarowski.pl ]=-
pgpPVu6wc32YP.pgp
Piotr Ozarowski ([EMAIL PROTECTED]):
> I'm looking for sponsor for my 3 packages:
> * gaupol (python app., new upstream)
> * chardet (python module, not yet in Debian - more info below)
> * sqlalchemy (python module, second NMU - see [1] for more info)
gaupol and chardet are
Norbert Tretkowski ([EMAIL PROTECTED]):
> Speaking of libapache2-mod-python... can someone please take care of
> the transition of libapache2-mod-python to the new python policy?
I'll try to convert it
--
-=[ Piotr Ozarowski ]=-
-=[ http://www.ozarowski.pl ]=-
pgpFgI
1001 - 1055 of 1055 matches
Mail list logo