On Mon, Sep 16, 2013 at 4:05 AM, Steve Langasek vor...@debian.org wrote:
On Sun, Sep 15, 2013 at 09:53:41PM +1000, Ben Finney wrote:
Lachlan lachlan...@gmail.com writes:
i'm not an expert by any means but i fail to see how this is an issue?
In short: Debian is not the only Unix-like system
On Sat, Sep 14, 2013 at 7:25 PM, Scott Kitterman deb...@kitterman.com wrote:
The only suggestion I can make is that it's generally not that hard for new
code to make it work for both python2.7 and python3.3.
I do not agree.
--
anatoly t.
--
To UNSUBSCRIBE, email to
On Sun, Sep 15, 2013 at 12:55 PM, anatoly techtonik techto...@gmail.com wrote:
On Sat, Sep 14, 2013 at 7:25 PM, Scott Kitterman deb...@kitterman.com wrote:
The only suggestion I can make is that it's generally not that hard for new
code to make it work for both python2.7 and python3.3.
I do
On Sun, Sep 15, 2013 at 1:24 PM, anatoly techtonik techto...@gmail.com wrote:
On Sun, Sep 15, 2013 at 12:55 PM, anatoly techtonik techto...@gmail.com
wrote:
On Sat, Sep 14, 2013 at 7:25 PM, Scott Kitterman deb...@kitterman.com
wrote:
The only suggestion I can make is that it's generally
On Sun, Jul 21, 2013 at 10:47 AM, Luca Falavigna dktrkr...@debian.orgwrote:
Hi!
Just to let you know about some good news regarding the deprecated
python helpers.
python-central has just been removed from unstable, as you can see in
[0]. The only package still using python-central is
On Mon, Jul 22, 2013 at 1:34 PM, Luca Falavigna dktrkr...@debian.org wrote:
2013/7/22 anatoly techtonik techto...@gmail.com:
Does that mean that helper to build Python packages is finally rewritten in
Python?
Unrelated, but yes:
To me the fact that replacement for dh_python is written
On Fri, Oct 14, 2011 at 2:10 PM, W. Martin Borgert deba...@debian.orgwrote:
Quoting anatoly techtonik techto...@gmail.com:
What does this testing implies? If there is a reference document on
testing - somebody else may do this. This doc should exists even just
to tell which parts can
On Thu, Oct 13, 2011 at 9:20 PM, W. Martin Borgert deba...@debian.org wrote:
Quoting anatoly techtonik techto...@gmail.com:
It's 9 months since the patch to upgrade trac-bitten was committed to
Debian repository and it's not packaged yet. Can anybody release it?
Problem is: I can't
On Thu, Oct 13, 2011 at 10:55 PM, W. Martin Borgert deba...@debian.org wrote:
On 2011-10-13 21:31, anatoly techtonik wrote:
There is a long standing bug in trac-bitten [1] to make a spin off a
bitten-slave package from the same source that will include just slave
client for running builds
:06 PM, anatoly techtonik techto...@gmail.com wrote:
Hi,
I've sent a patch to trac-bitten package. It was committed into Python
application team repository. What should I do now to make the package
released?
Please, CC.
--
anatoly t.
--
To UNSUBSCRIBE, email to debian-python-requ
There is a long standing bug in trac-bitten [1] to make a spin off a
bitten-slave package from the same source that will include just slave
client for running builds, which is independent of Trac [2]. Usually,
you can build bitten-slave with:
python setup.py --without-master install
But how to
Hi,
Can anybody apply this patch to trac-bitten? Seems like everybody who
could do this are busy.
Thanks.
--
anatoly t.
-- Forwarded message --
From: anatoly techtonik techto...@gmail.com
Date: Tue, Dec 7, 2010 at 5:22 PM
Subject: Re: Build-Depends-Indep dependencies
On Tue, Oct 26, 2010 at 3:10 PM, Bernd Zeimetz b...@debian.org wrote:
Even though the policy doesn't explain what Build-Depends-Indep is, it
says that Build-Depends-Indep should be present for these Makefile
targets:
build, build-indep, binary, and binary-indep
But there are no such targets
On Tue, Oct 26, 2010 at 3:10 PM, Bernd Zeimetz b...@debian.org wrote:
Even though the policy doesn't explain what Build-Depends-Indep is, it
says that Build-Depends-Indep should be present for these Makefile
targets:
build, build-indep, binary, and binary-indep
But there are no such targets
On Thu, Nov 18, 2010 at 8:28 PM, Sandro Tosi mo...@debian.org wrote:
What is the further process to get this in Lenny backports?
first you got to upload to experimental (since a beta it's not the
best version to have in unstable at this stage of the release),
I've uploaded it to
Hi,
I use pbuilder environment on lenny to test new trac-bitten with
piuparts, but the process fails with the broken symlinks error in
python-support:
$ sudo piuparts -p trac-bitten_0.6b3-1_all.deb -d lenny
...
Setting up libjs-jquery (1.2.6-2) ...
Setting up trac (0.11.1-2.1) ...
Setting
Hi,
Here is the patch to release new beta version of Bitten.
What is the further process to get this in Lenny backports?
P.S. Check out instructions on using pbuilder with svn-buildpackage.
http://wiki.debian.org/Teams/PythonAppsPackagingTeam/HowToPBuilder
--
anatoly t.
--
To UNSUBSCRIBE,
On Thu, Nov 18, 2010 at 8:28 PM, Sandro Tosi mo...@debian.org wrote:
On Thu, Nov 18, 2010 at 19:10, anatoly techtonik techto...@gmail.com wrote:
Here is the patch to release new beta version of Bitten.
here where? :)
Oops. Fixed. =)
What is the further process to get this in Lenny backports
Hi,
Why not to choose consistent naming scheme for Python groups?
Like PMPT and PAPT or DPMT and DPAT?
Maybe also PCPT Python Core Packaging Team or DPCT?
BTW, what are differences in packaging between Application and Module
- any FAQ links?
--
anatoly t.
--
To UNSUBSCRIBE, email to
On Mon, Nov 15, 2010 at 9:32 PM, Jonathan Wiltshire
deb...@jwiltshire.org.uk wrote:
On Mon, Nov 15, 2010 at 08:29:30PM +0200, anatoly techtonik wrote:
Why not to choose consistent naming scheme for Python groups?
Like PMPT and PAPT or DPMT and DPAT?
Presently they're not easily confused
On Mon, Nov 8, 2010 at 11:32 PM, Christian Kastner deb...@kvr.at wrote:
Having recently looked at packaging a Java library for the first time, I
found the sample packages[1] provided by the Java team immensely helpful
in getting started:
[1] http://pkg-java.alioth.debian.org/examples/
It
On Sun, Oct 31, 2010 at 5:19 PM, Andrey Rahmatullin w...@wrar.name wrote:
On Fri, Oct 29, 2010 at 08:19:36PM +0200, Tshepang Lekhonkhobe wrote:
I have a lot of packaging experience for ALT Linux and some experience
with Python programming, but no experience with Debian Python packaging (I
Hi,
How to build package in chroot environment (I guess that's pbuilder)?
I don't want to install build garbage on production server with
Debian instance, so I am trying to use pbuilder as described at
http://www.netfort.gr.jp/~dancer/software/pbuilder-doc/pbuilder-doc.html#id538126
$
On Mon, Nov 8, 2010 at 9:32 PM, Sandro Tosi mo...@debian.org wrote:
Hi,
On Mon, Nov 8, 2010 at 20:27, anatoly techtonik techto...@gmail.com wrote:
Hi,
I need access to PAPT SVN repository to make a patch. Does anybody know the
URL?
$ svn ls
svn://svn.debian.org/svn/python-modules
On Tue, Oct 26, 2010 at 7:18 PM, Bernd Zeimetz b...@debian.org wrote:
Of course you are still welcome to update packages, please send the
according
patches to me and I'll apply them.
Ok. I can send you patch right away, but I failed to understand what
Build-Depends-Indep need. Mind correcting
Sorry for the lame question, but I couldn't find an explanation of
difference between Build-Depends and Build-Depends-Indep in Debian
manuals. Can anybody explain when Build-Depends-Indep is required?
--
anatoly t.
--
To UNSUBSCRIBE, email to debian-python-requ...@lists.debian.org
with a
On Tue, Oct 26, 2010 at 10:40 AM, Sandro Tosi mo...@debian.org wrote:
Sorry for the lame question, but I couldn't find an explanation of
difference between Build-Depends and Build-Depends-Indep in Debian
manuals. Can anybody explain when Build-Depends-Indep is required?
look it up on Debian
On Tue, Oct 26, 2010 at 11:28 AM, Sandro Tosi mo...@debian.org wrote:
On Tue, Oct 26, 2010 at 10:16, anatoly techtonik techto...@gmail.com wrote:
On Tue, Oct 26, 2010 at 10:40 AM, Sandro Tosi mo...@debian.org wrote:
Sorry for the lame question, but I couldn't find an explanation of
difference
On Tue, Oct 26, 2010 at 1:56 PM, Filippo Rusconi
rusconi-deb...@laposte.net wrote:
in fact, I understand that you are mainly asking for general packaging
practice details. Have you looked at
http://www.debian.org/doc/maint-guide/
which does a fairly good job at explaining the basics of
On Tue, Oct 26, 2010 at 3:10 PM, Bernd Zeimetz b...@debian.org wrote:
I don't mind that beginners in packaging have write access to our
repositories,
assuming that they're willing to learn the necessary details during their work
within the team. But as you're neither willing to learn how
Got it. Thanks. One last question:
Can I upload the new version of a package what doesn't contain any
upstream changes?
I want to see how added debian/watch is picked up by various package
management tools.
--
anatoly t.
--
To UNSUBSCRIBE, email to debian-python-requ...@lists.debian.org
with
What is the point in the PAPT ML that is full of spam?
http://lists.alioth.debian.org/pipermail/python-apps-team/2010-October/thread.html
Should it be moved from Alioth to lists.debian.org or just redirected here?
http://lists.debian.org/debian-python/2010/10/threads.html
--
anatoly t.
--
To
Hi,
When you commit changes to SVN, the post-commit hook fails with error.
Sendingdebian\changelog
Sendingdebian\control
Adding debian\watch
Transmitting file data ...
Committed revision 6210.
Warning: post-commit hook failed (exit code 13) with output:
Error opening
On Sat, May 8, 2010 at 1:58 PM, Jakub Wilk jw...@debian.org wrote:
* anatoly techtonik techto...@gmail.com, 2010-05-08, 07:16:
Cover stdeb (anything else?), the reasons (if any) political and
technical, why it (or anything else) can not be used instead
unpythonic and unfamiliar make/debhelper
On Sat, May 8, 2010 at 11:51 AM, Emilio Pozuelo Monfort
po...@debian.org wrote:
\ 80kb of duplicated
code (even 8Mb) doesn't worth wasted time for troubleshooting in 2010.
It may be a reason for security, but why not just let packages
register their used version in Debian registry and track it
On Mon, May 10, 2010 at 2:23 PM, Piotr Ożarowski pi...@debian.org wrote:
Why I think derivatives should not add new versions?
* because it's mostly chasing numbers - I'm pretty sure there are not
more than 10 packages that require Python = 2.6 and are not easy to
port to 2.5 in Ubuntu
2010/5/10 Piotr Ożarowski pi...@debian.org:
I had to explain many times (mostly to Pylons users) why packages not
touched by Ubuntu developers are not working on Ubuntu, I know the pain.
Why...?
--
anatoly t.
--
To UNSUBSCRIBE, email to debian-python-requ...@lists.debian.org
with a subject
On Tue, May 11, 2010 at 9:57 PM, Sandro Tosi mo...@debian.org wrote:
Indeed, that's what we expect from the python maintainer:
- understand what changes between to major release
- prepare a draft for the transition, checking packages that brake
(reporting bugs and hopefully patches)
- get
2010/5/11 Piotr Ożarowski pi...@debian.org:
Why am I mentioning Ubuntu at all? Because all decisions about Python in
Debian are made there.
Do you still want me to answer your questions or is it clear already why
I am acting as an asshole?
I can't see an asshole action so fat. The thing
On Tue, May 4, 2010 at 11:20 PM, Richard Darst r...@zgib.net wrote:
I was looking through the talks submitted to DebConf, and noticed
there weren't very many Python related talks. Given the amount there
is to discuss related to Python in Debian, it would be great to see
some more
On Tue, Apr 20, 2010 at 3:19 AM, Lino Mastrodomenico
l.mastrodomen...@gmail.com wrote:
Given how much work is required to change the default Python, does it
make sense to just skip Python 2.6 and use 2.7 as the default Python
version in Squeeze?
Does that mean that Debian could then be called
There is a bug report to track the issue at http://bugs.debian.org/562963
I've created patch for Trac 0.11, but because I work on Windows and
Debian toolchain doesn't work on this system, it is impossible to make
a package with updated patches to test right now.
However, I'll be more than happy if
On Tue, Dec 29, 2009 at 11:48 PM, Iustin Pop iu...@k1024.org wrote:
People who are creating/maintaining packages should start by reading the
general packaging documentation, which explains these.
Python package maintainers do not need to learn all that irrelevant C
stuff they have no idea
On Tue, Dec 29, 2009 at 11:48 PM, Iustin Pop iu...@k1024.org wrote:
People who are creating/maintaining packages should start by reading
the general packaging documentation, which explains these.
Python package maintainers do not need to learn all that irrelevant C
stuff they have no
On Mon, Dec 28, 2009 at 4:27 PM, W. Martin Borgert deba...@debian.org wrote:
Then we should also patch trac-admin deploy command so that it
create symlinks to static resources instead of copies to update user
environments to latest jQuery automaically.
I don't remember, I ever used
On Tue, Dec 29, 2009 at 11:01 PM, W. Martin Borgert deba...@debian.org wrote:
Quoting anatoly techtonik techto...@gmail.com:
python-support README [1] contains different instructions for
'arch-all' and 'arch-any' packaged. How do I know which one is mine?
all: Package works on all
On Tue, Dec 29, 2009 at 6:10 PM, W. Martin Borgert deba...@debian.org wrote:
There is an open bug report anyway, that suggests and
trac-admin upgrade to be done automatically on every
upgrade of Trac. This is technically too difficult to solve,
because one never knows which environments exist
On Sat, Dec 26, 2009 at 6:01 PM, W. Martin Borgert deba...@debian.org wrote:
I don't feel like I
want to check if they are compatible next time I'd like to use one.
15kBytes doesn't worth wasted hours.
The issue is not 15 kB, but the problems Debian would have if an
error must be fixed in
On Sat, Dec 26, 2009 at 2:08 PM, Paul Wise p...@debian.org wrote:
Upstream Trac is shipped with jQuery it needs while leaving Genshi and
other libraries as dependencies. Debian specific patch removes jQuery
from Trac distribution even though it contributes only 2% to package
size. This
On Sat, Dec 26, 2009 at 10:17 PM, Ben Finney ben+deb...@benfinney.id.au wrote:
Quoting anatoly techtonik techto...@gmail.com:
Even if most users don't need them, tests greatly increase the value
of bugreports and doesn't bloat python packages too much.
True. What do other people think
On Sun, Dec 27, 2009 at 6:24 PM, W. Martin Borgert deba...@debian.org wrote:
It would be helpful, if you could state the exact problems you
had because of the newer jQuery.
Not 100% sure it was only jQuery (can't test this right now) but, for
example, I could not drill down beneath the first
On Sat, Dec 26, 2009 at 3:56 AM, Paul Wise p...@debian.org wrote:
Trac 0.11 ships with jQuery 1.2.6
However, Debian patches remove this file in favor of libjs-jquery
package which contains version 1.3.x
This breaks plugins for Trac 0.11 that rely on 1.2.x jQuery features
removed in 1.3.x
Hello,
I'm having some troubles with trac-accountmanager package and want to
execute its unit tests to see if they could catch anything unusual,
but it appeared that they were stripped from the package.
Python policy is silent about unit tests. Should they be stripped? Or
should they be
On Fri, Dec 25, 2009 at 6:01 PM, W. Martin Borgert deba...@debian.org wrote:
Quoting anatoly techtonik techto...@gmail.com:
Python policy is silent about unit tests. Should they be stripped? Or
should they be Debianized or left as-is?
Just my opinion: Unit tests should be in the source
Hello,
Trac 0.11 ships with jQuery 1.2.6
However, Debian patches remove this file in favor of libjs-jquery
package which contains version 1.3.x
This breaks plugins for Trac 0.11 that rely on 1.2.x jQuery features
removed in 1.3.x
How to properly add dependency for jQuery1.3 to trac package?
On Sun, Dec 13, 2009 at 12:41 AM, Christoph Egger
christoph.eg...@gmx.de wrote:
anatoly techtonik schrieb:
Questions like Debian Python Policy is all about GPL. Do I have to
release my Python package under GPL?. Most people (as you clearly
expressed) don't care, so upstream maintainers would
Given that people are tired of discussing things they've already
decided for themselves I CC this to debian-legal.
On Sun, Dec 13, 2009 at 11:11 AM, Ben Finney ben+deb...@benfinney.id.au wrote:
The Debian policy is software with source code: the DocBook source document.
It is not clear why GPL
Hello,
The policy is under GPL license which is kind of ridiculous to prevent
citing Debian Policy in private talks. I imagine people discussing
those folks at Debian. Have you heard - they've changed you-know-what
to make packaging easier. =)
Is there any license that more clearly states reason
On Sat, Dec 12, 2009 at 4:56 PM, Adam adam.schmalho...@gmx.de wrote:
This is a topic for debian-legal not debian-pyhton. Discuss it with them
(after looking at the archive), as they are the experts. If there are
problems (= results) that can be brought here again.
The point is to make Python
Hello,
Now I wish I could find time to write de-facto packaging tutorial in
wiki to see how the patched policy and original policy is going to
solve this real-world problem.
Thanks for collaboration.
--
anatoly t.
On Tue, Dec 8, 2009 at 10:24 PM, Loïc Minier l...@dooz.org wrote:
[ MFT:
2009/11/8 Jakub Wilk uba...@users.sf.net:
I am going to file a few dozens of bugs against packages that are embedding
copies of Python modules; more specifically:
Do you mean that all these packages need to stick to the stable
standard version of some Module available in Debian? I personally
On Wed, Nov 4, 2009 at 2:29 AM, Ben Finney ben+deb...@benfinney.id.au wrote:
(I am reading this to mean “the reference version of the Debian Python
policy is in the python-defaults package”.)
Okay. Clearly one way for this to improve would be for some of those bug
reports to be responded to
On Mon, Nov 2, 2009 at 2:27 PM, Scott Kitterman deb...@kitterman.com wrote:
I'm not aware of any ongoing work. I would be willing to help work on such
a thing, but we currently lack a good mechanism for developing/approving
such a policy.
With clear policy and precise goal you won't need
Trac for sure. Is there any _short_ howto about Debian backports for
Python folks?
--anatoly t.
On Mon, Sep 21, 2009 at 2:54 AM, W. Martin Borgert deba...@debian.org wrote:
Hi,
for some reasons I need lenny backports of python-django,
python-webpy and trac. Some of the packages I don't
On Thu, Sep 10, 2009 at 6:45 PM, W. Martin Borgert deba...@debian.org wrote:
Quoting Andres Salomon dilin...@collabora.co.uk:
Yes, trac will be maintained in the Python Application Packaging Team.
I already tried to copy the git history to the PAPT svn, but - lacking
any experience with git -
On Mon, Sep 7, 2009 at 9:49 PM, Mikhail Gusarovdotted...@dottedmag.net wrote:
Twas brillig at 11:37:50 07.09.2009 UTC-07 when vor...@debian.org did gyre
and gimble:
SL They were part of the design that came out of the python packaging
SL BoF in DebConf 6 that you then proceeded to ignore
On Tue, Sep 8, 2009 at 1:00 PM, Steve Langasekvor...@debian.org wrote:
Twas brillig at 02:42:09 08.09.2009 UTC-07 when vor...@debian.org did gyre
and gimble:
SL Spare me your ignorant preaching and go read the mailing list
SL archives.
Mailing list archives are not documentation.
Hello,
Can anybody point me to the repository location of python-support package?
Thanks.
--anatoly t.
--
To UNSUBSCRIBE, email to debian-python-requ...@lists.debian.org
with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
://packages.qa.debian.org/p/python-support.html are all broken.
Added link to python-support README to http://wiki.debian.org/DebianPythonFAQ
Ciao,
--anatoly t.
2009/9/1 Josselin Mouette j...@debian.org:
Le mardi 01 septembre 2009 à 13:53 +0300, anatoly techtonik a écrit :
Can anybody point me to the repository
On Tue, Sep 1, 2009 at 4:16 PM, Dmitrijs
Ledkovsdmitrij.led...@gmail.com wrote:
Recently I have discovered some very nice features of hg that make it
attractive:
Mercurial Queues are awesome, but there is one major drawback in
Mercurial comparing to SVN - it is impossible to clone a subtree of
On Fri, Aug 28, 2009 at 11:48 AM, W. Martin Borgertdeba...@debian.org wrote:
I wonder, how people feel about moving Trac from its own team
to a larger, more active team, i.e. Debian Python Modules Team,
which already has some of tracs dependencies, i.e.
libapache2-mod-python, mod-wsgi,
Hello, Piotr.
In short - your post is long. Brain is limited. Better place an
overview in wiki and discuss in parts.
Before discussing your proposal I would really appreciate if somebody
from insiders could describe situation in Debian Python in all
possible detail including the history of
On Thu, Jul 30, 2009 at 7:10 PM, Max Bowsherm...@f2s.com wrote:
anatoly techtonik wrote:
Hello,
Can anybody tell what happens with existing Python modules when a new
Python version is deployed on the system?
Are they recompiled or reinstalled or left inaccessible in this version?
Debian
73 matches
Mail list logo
