On Mon, Sep 16, 2013 at 4:05 AM, Steve Langasek wrote:
> On Sun, Sep 15, 2013 at 09:53:41PM +1000, Ben Finney wrote:
>> Lachlan 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 where Python is
>> installed
On Sun, Sep 15, 2013 at 1:47 PM, Lachlan wrote:
> i'm not an expert by any means but i fail to see how this is an issue?
>
> -Everyone wrote scripts for python 2.x using /usr/bin/python
> -With python3, scripts were written specifically for python3 using
> /usr/bin/python3
>
> When Debian eventual
On Sun, Sep 15, 2013 at 1:24 PM, anatoly techtonik wrote:
> On Sun, Sep 15, 2013 at 12:55 PM, anatoly techtonik
> wrote:
>> On Sat, Sep 14, 2013 at 7:25 PM, Scott Kitterman
>> wrote:
>>> The only suggestion I can make is that it's generally not that hard for n
On Sun, Sep 15, 2013 at 12:55 PM, anatoly techtonik wrote:
> On Sat, Sep 14, 2013 at 7:25 PM, Scott Kitterman 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
On Sat, Sep 14, 2013 at 7:25 PM, Scott Kitterman 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 debian-python-requ...@lists.debian.org
with
On Mon, Jul 22, 2013 at 1:34 PM, Luca Falavigna wrote:
> 2013/7/22 anatoly techtonik :
>> 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 in Python is
On Sun, Jul 21, 2013 at 10:47 AM, Luca Falavigna wrote:
> 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 gozerbot-plugins
>
On Fri, Oct 14, 2011 at 2:10 PM, W. Martin Borgert wrote:
> Quoting "anatoly techtonik" :
>
>> 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 part
On Fri, Oct 14, 2011 at 3:39 PM, W. Martin Borgert wrote:
> Quoting "anatoly techtonik" :
>>
>> On Fri, Oct 14, 2011 at 2:07 PM, W. Martin Borgert
>> wrote:
>
> ...
>>
>> The Python thing is to how to generate (and regenerate) these install
>&g
On Fri, Oct 14, 2011 at 2:07 PM, W. Martin Borgert wrote:
> Quoting "anatoly techtonik" :
>>
>> Nice. But how do you create these install files? Can stdeb tool help with
>> that?
>
> I don't know stdeb, but install files are easyly understood.
> See th
On Thu, Oct 13, 2011 at 10:55 PM, W. Martin Borgert 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 run
On Thu, Oct 13, 2011 at 9:20 PM, W. Martin Borgert wrote:
> Quoting "anatoly techtonik" :
>>
>> 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?
>
> Pr
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 sp
at, Jan 1, 2011 at 5:06 PM, anatoly techtonik 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.
&
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
Date: Tue, Dec 7, 2010 at 5:22 PM
Subject: Re: Build-Depends-Indep dependencies
To: Bernd Zeimetz
Hi
On Tue, Oct 26, 2010 at 3:10 PM, Bernd Zeimetz 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 in t
On Tue, Oct 26, 2010 at 3:10 PM, Bernd Zeimetz 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 in t
On Thu, Nov 18, 2010 at 8:28 PM, Sandro Tosi 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
http://mentors.debian.n
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
On Thu, Nov 18, 2010 at 8:28 PM, Sandro Tosi wrote:
> On Thu, Nov 18, 2010 at 19:10, anatoly techtonik 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
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, emai
On Mon, Nov 15, 2010 at 9:32 PM, Jonathan Wiltshire
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 co
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 debian-p
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
$ svn-bui
On Sun, Oct 31, 2010 at 5:19 PM, Andrey Rahmatullin 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
>> > have s
On Mon, Nov 8, 2010 at 11:32 PM, Christian Kastner 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 would be
On Mon, Nov 8, 2010 at 9:32 PM, Sandro Tosi wrote:
> Hi,
>
> On Mon, Nov 8, 2010 at 20:27, anatoly techtonik wrote:
>> Hi,
>>
>> I need access to PAPT SVN repository to make a patch. Does anybody know the
>> URL?
>
> $ svn ls
> svn://svn.debian.
Hi,
I need access to PAPT SVN repository to make a patch. Does anybody know the URL?
Thanks.
--
anatoly t.
--
To UNSUBSCRIBE, email to debian-python-requ...@lists.debian.org
with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org
Archive:
http://lists.debian.org/aanlktik
On Tue, Oct 26, 2010 at 7:18 PM, Bernd Zeimetz 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 my fin
On Tue, Oct 26, 2010 at 7:12 PM, Didier 'OdyX' Raboud wrote:
> anatoly techtonik wrote:
>
>> I know basics about Makefiles - I know that target is and what 4-space
>> indents from PEP-8 are unwelcome there. But Debian Policy tells that
>> debian/rules sho
On Tue, Oct 26, 2010 at 7:09 PM, Tristan Seligmann
wrote:
> On Tue, Oct 26, 2010 at 5:35 PM, anatoly techtonik
> wrote:
>> many places outdated (email-based bug-trackers, ML without search,
>
> FWIW: http://lists.debian.org/search.html
Cool. Why Python Application Team list
On Tue, Oct 26, 2010 at 3:10 PM, Bernd Zeimetz 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 packaging soft
On Tue, Oct 26, 2010 at 1:56 PM, Filippo Rusconi
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 Debian
> package prepara
On Tue, Oct 26, 2010 at 11:28 AM, Sandro Tosi wrote:
> On Tue, Oct 26, 2010 at 10:16, anatoly techtonik wrote:
>> On Tue, Oct 26, 2010 at 10:40 AM, Sandro Tosi wrote:
>>>> Sorry for the lame question, but I couldn't find an explanation of
>>>> difference b
On Tue, Oct 26, 2010 at 10:40 AM, Sandro Tosi 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 Policy - a
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 subject
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 UN
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 a
On Mon, Oct 25, 2010 at 8:47 PM, Chow Loong Jin wrote:
> On Tuesday 26,October,2010 01:45 AM, anatoly techtonik wrote:
>> What dfsg suffix in package version is for?
>> In trac-bitten to be exact.
>
> It means that the tarball was repacked to meet DFSG[1] requi
What dfsg suffix in package version is for?
In trac-bitten to be exact.
--
anatoly t.
--
To UNSUBSCRIBE, email to debian-python-requ...@lists.debian.org
with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org
Archive:
http://lists.debian.org/aanlkti=hbnxh64obf+2nrhd+kwxgn
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 cach
Hello,
The Alioth page lists wrong paths for SVN repositories:
https://alioth.debian.org/scm/?group_id=30714
--
anatoly t.
--
To UNSUBSCRIBE, email to debian-python-requ...@lists.debian.org
with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org
Archive:
http://lists.debi
2010/5/11 Piotr Ożarowski :
>
> 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 that troubles
On Tue, May 11, 2010 at 9:57 PM, Sandro Tosi 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 consensus f
2010/5/10 Piotr Ożarowski :
>
> 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 of "unsubscri
On Mon, May 10, 2010 at 2:23 PM, Piotr Ożarowski 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 10.04,
Backport
On Sat, May 8, 2010 at 11:51 AM, Emilio Pozuelo Monfort
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 there?
>
On Sat, May 8, 2010 at 1:58 PM, Jakub Wilk wrote:
> * anatoly techtonik , 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/debhel
One more thing for "Python Policy 2010." Status quo with examples.
Trac comes with jQuery suitable for this version of application. But
Debian policy dictates to remove duplicated code, so jQuery is
replaced with some other version rather than required. This creates
problems with plugins and Debia
On Tue, May 4, 2010 at 11:20 PM, Richard Darst 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 submissions.
>
> Per
On Tue, Apr 20, 2010 at 3:19 AM, Lino Mastrodomenico
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 a "modern operating
syst
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 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 id
On Tue, Dec 29, 2009 at 11:48 PM, Iustin Pop 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 about. They need
On Tue, Dec 29, 2009 at 6:10 PM, W. Martin Borgert 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 (they
> mig
On Tue, Dec 29, 2009 at 11:01 PM, W. Martin Borgert wrote:
> Quoting "anatoly techtonik" :
>>
>> python-support README [1] contains different instructions for
>> 'arch-all' and 'arch-any' packaged. How do I know which one is mine?
>
python-support README [1] contains different instructions for
'arch-all' and 'arch-any' packaged. How do I know which one is mine?
[1]
http://svn.debian.org/viewsvn/collab-maint/deb-maint/python-support/trunk/README
Thanks.
--
anatoly t.
--
To UNSUBSCRIBE, email to debian-python-requ...@list
On Mon, Dec 28, 2009 at 4:27 PM, W. Martin Borgert 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 "trac-admin depl
On Mon, Dec 28, 2009 at 3:34 AM, W. Martin Borgert wrote:
>
>> Now I still have
>> AccountManager named "urwid" in Trac Admin panel, but I do not even
>> want to repeat this awful SSH experience.
>
> I have the same problem (wrong Python package names as names of
> Trac plugins in the admin panel)
On Mon, Dec 28, 2009 at 3:29 AM, W. Martin Borgert wrote:
> Quoting "anatoly techtonik" :
>>
>> Then why can't you wait until upstream developers, whose product
>> bundles that library, confirm, validate, test and release fix for that
>> error in
On Sun, Dec 27, 2009 at 6:56 PM, W. Martin Borgert wrote:
>
>> 2. Thing to consider. When you create Environment and "deploy" it with
>> trac-admin (to generate fastcgi/mod_wsgi scripts) - copies of static
>> resources for web-server, including JavaScript won't be updated when
>> you fix your secu
On Sun, Dec 27, 2009 at 6:24 PM, W. Martin Borgert 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 level in template
On Sat, Dec 26, 2009 at 10:17 PM, Ben Finney wrote:
>
>> Quoting "anatoly techtonik" :
>> > Even if most users don't need them, tests greatly increase the value
>> > of bugreports and doesn't bloat python packages too much.
>>
>> Tru
On Sat, Dec 26, 2009 at 2:08 PM, Paul Wise 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 dependency in
On Sat, Dec 26, 2009 at 6:01 PM, W. Martin Borgert 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 jQuery (e.
On Sat, Dec 26, 2009 at 3:56 AM, Paul Wise 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
>>
>> Ho
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 jQuery<1.3 to trac package?
Tha
On Fri, Dec 25, 2009 at 6:01 PM, W. Martin Borgert wrote:
> Quoting "anatoly techtonik" :
>>
>> 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
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 Debianize
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 wrote:
> The Debian policy is software with source code: the DocBook source document.
It is not clear why GPL notice doesn't stay in the
On Sun, Dec 13, 2009 at 12:41 AM, Christoph Egger
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
On Sat, Dec 12, 2009 at 4:56 PM, Adam 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 Policy clear without a
On Sat, Dec 12, 2009 at 12:22 PM, Ben Finney wrote:
>
>> The policy is under GPL license which is kind of ridiculous to prevent
>> citing Debian Policy in private talks.
>
> Why is it ridiculous? Is it any more ridiculous to put a policy document
> under GPL than any other document?
It is in the
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 reaso
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 wrote:
> [ MFT: debian-pyt...@
2009/11/8 Jakub Wilk :
> 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
think that fit is a
On Wed, Nov 4, 2009 at 2:29 AM, Ben Finney 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 by the maintainer.
>
>
On Mon, Nov 2, 2009 at 2:27 PM, Scott Kitterman 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 approving mechanism
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 wrote:
> Hi,
>
> for some reasons I need lenny backports of python-django,
> python-webpy and trac. Some of the packages I don't need for
> "produc
On Fri, Sep 11, 2009 at 12:52 AM, W. Martin Borgert wrote:
> http://packages.qa.debian.org/t/trac.html states
> git://git.debian.org/git/pkg-trac/trac.git
>
> If you like, feel free to try your luck! I would just leave the
> git history in git and start with the latest packaged trac
> version, bu
On Thu, Sep 10, 2009 at 6:45 PM, W. Martin Borgert wrote:
> Quoting "Andres Salomon" :
>
> 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 - failed. I will now just start with
On Tue, Sep 8, 2009 at 1:00 PM, Steve Langasek 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.
>
> They're
On Mon, Sep 7, 2009 at 9:49 PM, Mikhail Gusarov 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 entirely.
>
> Is
On Tue, Sep 1, 2009 at 4:16 PM, Dmitrijs
Ledkovs 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
repository. In SVN you
ge at
http://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 :
> Le mardi 01 septembre 2009 à 13:53 +0300, anatoly techtonik a écrit :
>> Can anybody point me to the rep
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
On Fri, Aug 28, 2009 at 2:21 PM, Christoph
Egger wrote:
>
> As my packages have (following trac itself) a git history and the one
> I've ITA-ed has some HG history I'm interested in what the team thinks
> so I can decide if / what to move in.
If we are all Python developers to some degree a
On Fri, Aug 28, 2009 at 12:01 PM, Jan Dittberner wrote:
>
> I'm using trac and commithooks and would like to help with better
> Debian support for both.
>
There are many outstanding bugs without patches that are rather
critical to skip forever. Before moving Trac from one VCS to another
the first
On Fri, Aug 28, 2009 at 11:48 AM, W. Martin Borgert 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, python-docutils, gen
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 devel
On Thu, Jul 30, 2009 at 7:10 PM, Max Bowsher 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 inacces
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?
WBR,
--anatoly t.
--
To UNSUBSCRIBE, email to debian-python-requ...@lists.debian.org
with a subject o
92 matches
Mail list logo
