Hello
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 maintain the small
subset of pa
Is there a way to use git but build with sbuild. I kind of don't want
to go back to pbuilder and IIRC git-buildpackage requires it.
On Tue, Mar 31, 2015 at 5:43 PM, Barry Warsaw wrote:
> On Mar 31, 2015, at 04:48 PM, Antoine Musso wrote:
>
>>I have only been introduced to git-buildpackage and usi
Barry the import script looks pretty cool.
Any chance to package it and bless it as the official conversion script?
Best regards
ZK
On Tue, Mar 31, 2015 at 3:57 PM, Barry Warsaw wrote:
> On Mar 31, 2015, at 01:14 PM, Balasankar C wrote:
>
>>One more doubt. Where are new packages uploaded to in
W dniu 31.03.2015 o 09:44, Balasankar C pisze:
Hi,
One more doubt. Where are new packages uploaded to in Python Modules
Team? Is there a git repo or should I upload to Debian Mentors? I am
asking this because, in Ruby team, the uploads usually happen to the
git repos created inside pkg-ruby-ex
On Fri, Sep 12, 2014 at 4:10 AM, Brian May
wrote:
> Obviously this is likely to fall out of date quickly. Apologies for any
> errors.
>
> I just wanted to try classify what is holding these bugs up.
>
>
> Bugs waiting for new Debian package:
>
> #755607 [i|+| ] [src:django-restricted-resource]
>
On Mon, Jun 2, 2014 at 10:51 PM, Barry Warsaw wrote:
> On Jun 02, 2014, at 04:43 PM, Donald Stufft wrote:
>
> >Sounds reasonable to me, the only “downside” is that virutalenv will
> default
> >to Python 3, which is probably not what most people want (however they
> >can do virtualenv -p python2).
I think you are quite welcome to join DPMT
https://wiki.debian.org/Teams/PythonModulesTeam/HowToJoin
Best regards
ZK
On Thu, Apr 24, 2014 at 6:34 PM, Daniel James wrote:
> Hello,
>
> I am a non-DD looking for sponsorship of (or any helpful hints about) my
> first upload to Debian: http://ment
Hi.
I'd like to add support for intersphinx [1] to a package I'm working
on [2]. The generated documentation should also include the
intersphinx meta-data so that other packages that build-depend on my
package can cross-reference documentation elements.
Are there any examples of intersphinx usage
pl.secure.launcher1 module so that it can be
> | executed directly with `python3 -m ...`. This is useful to generate
> | the plainbox-trusted-launcher-1.1 manual page with help2man
> |
> |Author: Zygmunt Krynicki
> |Bug: https://bugs.launchpad.net/checkbox/+bug/1255085
> |Last-Update: 20
le in #debian-python to answer any questions that you may have.
[1]
http://anonscm.debian.org/viewvc/python-modules/packages/plainbox/trunk/debian/
[2] https://github.com/zyga/debian.plainbox
Best regards
Zygmunt Krynicki
--
To UNSUBSCRIBE, email to debian-python-requ...@lists.debian.o
le in #debian-python to
answer any questions that you may have.
[1]
http://anonscm.debian.org/viewvc/python-modules/packages/plainbox/trunk/debian/
[2] https://github.com/zyga/debian.plainbox
Best regards
Zygmunt Krynicki
Hello again.
I've prepared 0.4~b1-2 with the following changes:
(the branch is still on github at https://github.com/zyga/debian.plainbox
On Tue, Nov 26, 2013 at 9:41 AM, Piotr Ożarowski wrote:
> [Zygmunt Krynicki, 2013-11-26]
> > > * "plainbox is a Simple replacement for
On Mon, Nov 25, 2013 at 11:22 PM, Zygmunt Krynicki <
zygmunt.kryni...@canonical.com> wrote:
> Hi.
>
> Thanks for the quick review!
>
>
> On Mon, Nov 25, 2013 at 9:24 PM, Piotr Ożarowski wrote:
>
>> > [1] https://github.com/zyga/debian.plainbox
>>
>>
On Mon, Nov 25, 2013 at 8:44 PM, Piotr Ożarowski wrote:
> Cześć,
>
>
Cześć
> [Zygmunt Krynicki, 2013-11-25]
> > I'm writing to to you as the upstream for pybuild.
> >
> > I'm trying to use pybuild to split a simple upstream python3-only project
> >
Hi.
Thanks for the quick review!
On Mon, Nov 25, 2013 at 9:24 PM, Piotr Ożarowski wrote:
> > [1] https://github.com/zyga/debian.plainbox
>
> * -doc package is empty,
>
Odd, it wasn't when I was building it, I must have broken something before
the final packaging commit.
> * debian/copyright
Hi.
I'd like to join the Debian python modules team.
My goal is to maintain a set of packages related to PlainBox [1] I have
prepared packaging for Ubuntu 14.04 and I'd like to prepare one for Debian
as well.
My alioth username is zyga-guest.
Best regards
Zygmunt Krynicki
Hi Piotr.
I'm writing to to you as the upstream for pybuild.
I'm trying to use pybuild to split a simple upstream python3-only project
into a number of smaller packages. I'm having problems trying to force the
main executable to move away from the python3-foo library package into the
foo "main" p
Hi
I had a look at their tox.ini and IMHO you won't be able to reproduce that
with plain setuptools alone. You'd have to see what the test is doing to
see what I mean. They are testing multiple variants of the build as well
(without and with native extensions). It might be possible to test
everyth
;d tab-tab until I get to see some set of choices and the dash
gives it a nice visual separation.
Best regards
Zygmunt Krynicki
distro
We care more about users than developers. Python developers can use
virtualenv and pip on Debian like any other Python development env.
Is this codified anywhere? That Debian project puts the needs of the
users above the needs of users that also happen to develop software?
Your secon
W dniu śro, wrz 18, 2013 o 10:57 ,nadawca Tshepang Lekhonkhobe
napisał:
On Wed, Sep 18, 2013 at 3:36 PM, Paul Tagliamonte
wrote:
4) Python modules from dpkg are borderline useless for
developers. We
package modules so that apps can use them, not so that people
can
develop w
W dniu 15.06.2011 03:28, Ben Finney pisze:
If we are talking from a perspective of upstream developers that
also maintain their packages then I would *love* to see setup.py
sdist-test and would use it each day.
;-)
How would a putative ‘sdist_test’ differ from ‘test’? Why is this an
argument
W dniu 15.06.2011 02:46, Jakub Wilk pisze:
* Zygmunt Krynicki , 2011-06-15, 01:03:
In a setup.py world:
$ python setup.py build_sphinx
This is all fine and pretty (thanks to python).
Only if you are happy that your extension modules are built in-place. :/
I did not use extension modules
W dniu 15.06.2011 02:28, Yaroslav Halchenko pisze:
On Wed, 15 Jun 2011, Zygmunt Krynicki wrote:
That's different. IHMO you ask for make dist-check AFAIR (my
automake-foo is getting old). Testing installed stuff is often
harder and not supported as we don't want to include tests in t
W dniu 15.06.2011 02:13, Ben Finney pisze:
$ python setup.py test
I would also like this to become the de-facto standard. Can we somehow
make it happen? (debian policy, python something?)3.3).
AFAICT it *is* the de facto standard. Perhaps you mean that you want it
to be the de jure standard
W dniu 15.06.2011 01:06, Yaroslav Halchenko pisze:
ideally I would like to see the helper which would allow (or even by
default would do) to invoke test batteries against just installed (i.e.
python setup.py install) version of the modules: in my experience it
helped to avoid various issues of
W dniu 15.06.2011 00:04, Barry Warsaw pisze:
On Jun 14, 2011, at 05:53 PM, Zygmunt Krynicki wrote:
Can please we have standardized hooks to build sphinx documentation and run
setup.py test tests?
I'd like to see the packaging folks address this. Eric is subscribed to this
list an
W dniu 14.06.2011 16:45, Barry Warsaw pisze:
I want to be a conduit between Debian and upstream, so please, I encourage
everyone who has concrete issues that can help the Debian story, to raise them
here. Python is a big ship so it takes time to steer, but as I hope I've
shown with PEP 3147 and
of the first plugins that AFAIK was
created was one that creates proper packaging for python+distutils.
I'm CCing upstream author (James Westby) perhaps he would be interested
to know more about this.
Best regards
Zygmunt Krynicki
--
To UNSUBSCRIBE, email to debian-python-requ...@lis
ll be provided shortly after testing.
You can get the tarball from [1], source code from [2], package in
bzr-builddeb format in [3]
I look forward to all comments and contributions.
Best regards
Zygmunt Krynicki
[1]: http://pypi.python.org/pypi/django-debian/0.1
[2]: lp:django-debian
[3
Data: I like to differentiate between data supporting the package and
data that belongs to the sysadmin/site. IMO the former belongs in /var
somewhere and the latter at a path chosen by the sysadmin. I don't
think this is gotten right by much software, including by all database
packages.
How do
31 matches
Mail list logo
