|
82
Scott Kitterman |
7
Vincent Bernat |
15
(6 rows)
Debian PaN is another team which might need extra discussion but I think
the intention is clear and Scott has raised his opinion before[2].
Kind regards
Andreas.
[1]
https://sal
On 2024-01-04 00:30, Alexandre Detiste wrote:
@Vincent: this one package "gtextfsm" is yours
do you green light an upload ?
Yes.
On 2023-09-13 09:29, Thomas Goirand wrote:
OpenStack networking-generic-switch needs 4.1.2, from last August, so
I'm about to upload that version to Experimental right away. Since you,
Vincent, is listed in the Maintainer: field, and the team is only listed
as Uploaders:, I was wondering if it
❦ 16 mai 2020 08:09 -04, Paul Tagliamonte:
>> > Would it be fair to say that your main objection is that Ubuntu has
>> > much higher popularity than Debian
>>
>> This is what I regret, indeed. It's been like that for many years, and
>> the trend isn't reversing. We should ask ourselves why. From
❦ 8 septembre 2019 00:04 +02, Thomas Goirand :
> As a consequence, and because it's becoming problematic to see Pyroute2
> removed from testing for me, I do believe that it is time this package
> joins the DPMT (ie: Debian Python Module Team). This way, you can
> continue to work on "your" packa
❦ 21 avril 2018 14:24 +0200, Nicolas Dandrimont :
>> I've got a bunch of bugs like this one:
>> bugs.debian.org/cgi-bin/bugreport.cgi?archive=yes&bug=896229
>>
>> I didn't see any discussion about this MBF.
>
> https://lists.debian.org/debian-devel/2018/04/msg00258.html and
> (longish) thread.
Hey!
I've got a bunch of bugs like this one:
bugs.debian.org/cgi-bin/bugreport.cgi?archive=yes&bug=896229
I didn't see any discussion about this MBF. I don't understand why some
packages get the python-pkg-resources dependency from dh-python, but
some (like this one) doesn't. Adding python-setup
❦ 9 février 2018 13:46 +0100, Ondrej Novy :
>- mass-commit change of d/control: Vcs-*
Is it needed? anonscm URL work (both Vcs fields use https) and it seems
a better idea to have service-independant URL.
--
Follow each decision as closely as possible with its associated action.
❦ 15 octobre 2017 10:12 +1100, Brian May :
>> pyasn1 is currently at version 0.1.9. The current version is
>> 0.3.7. There is a bug report asking for a new version:
>>
>> https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=872724
>>
>> Should a transition be opened for such a packet (this is not
Hello,
pyasn1 is currently at version 0.1.9. The current version is
0.3.7. There is a bug report asking for a new version:
https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=872724
Should a transition be opened for such a packet (this is not usual to
have transition for Python packages, but ther
❦ 5 juillet 2017 21:19 +1000, Brian May :
>> git-dpm: Calling merge-patched-into-debian first...
>> git-dpm: ERROR: cowardly refusing to update patched to already merged
>> version!. Use --allow-revert to override!
>
> Have you tried doing what it suggests, using the --allow-revert
> parameter
❦ 5 juillet 2017 13:27 +0200, Nikolaus Rath :
>> How to remove a patch with git-dpm?
>
> Look for "Removing existing patches" in git-dpm(1):
>
> $ git-dpm checkout-patched
> $ git rebase -i upstream-unstable
> $ git-dpm dch -- -i
That's totally similar to use "git reset --hard HEAD~1" (since
Hey!
How to remove a patch with git-dpm?
I have tried:
git-dpm c-p
git reset --hard HEAD~1
git-dpm u-p
And got:
git-dpm: Calling merge-patched-into-debian first...
git-dpm: ERROR: cowardly refusing to update patched to already merged version!.
Use --allow-revert to override!
I don't understa
❦ 2 avril 2017 09:45 +0100, Ghislain Vaillant :
>>> it's just a few lines down in the changelog:
>>> https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=829744 (it is kinda
>>> sad that there was no discussion with the python team from the lintian
>>> maintainer before accepting and merging it, e
❦ 2 avril 2017 10:21 +0100, Chris Lamb :
>> > On the current subject, I also agree we should not drop prematurely
>> > packages targeted to Python 2.
>
> The Lintian tag in question does not suggest maintainers should be
> removing existing Python 2 support from packages.
>
> It merely suggests
❦ 1 avril 2017 19:42 -0400, Sandro Tosi :
>> It's not at all clear where [1] came from. The lintian changelog [3] does
>> not
>> give a bug reference and I couldn't find a bug.
>
> it's just a few lines down in the changelog:
> https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=829744 (it is k
❦ 9 mars 2017 21:13 +1100, Brian May :
> The above also assumes that upstream==origin/upstream==latest
> upstream. Which means you need to have done a git pull recently on the
> upstream branch. Depending on the circumstances, using origin/upstream
> might be a better choice rather then upstrea
❦ 6 mars 2017 12:30 +1100, Brian May :
>> I'm hereby volunteering for such a sprint (if I hopefully make it to
>> Montreal). Hopefully, migrating from git-dpm to git-pq wont be as hard
>> as from SVN to Git.
>
> Great! The sooner (after the freeze) we can do this, the better
> IMHO. git-dpm
❦ 4 mars 2017 23:04 GMT, Scott Kitterman :
>> > This was not about isolated mistakes. We've all made those. I do
>> > not, however, think it's useful to rehash the details. I do think it
>> > is worth mentioning that since he's back in the team it wasn't without
>> > limit.
>>
>> He's back
❦ 4 mars 2017 15:04 GMT, Scott Kitterman :
> This was not about isolated mistakes. We've all made those. I do
> not, however, think it's useful to rehash the details. I do think it
> is worth mentioning that since he's back in the team it wasn't without
> limit.
He's back in the team becaus
❦ 3 mars 2017 21:42 -0800, Clint Byrum :
> One great thing about teams is they have many faces. Talk to me. Talk to
> Allison. Talk to others. We're here to make sure things flow smoothly
> for OpenStack and Debian, and if you have disagreements and don't want
> to fight, I get that. Maybe we c
❦ 11 octobre 2016 10:38 CEST, Ben Finney :
>> Reading
>> https://wiki.debian.org/Python/LibraryStyleGuide#Building_python_-dbg_packages,
>> there is some hints to this
>
> The introduction of ‘foo-dbgsym’ automatic generated packages makes me
> quite sure those instructions are obsolete. But per
❦ 23 septembre 2016 16:15 CEST, Thomas Goirand :
>> The "[Python-modules-team]" thing in the subject is probably enough to
>> break the DKIM signature.
>
> I don't believe DKIM signature is done on the header+body. If I'm not
> mistaking, it's done only in the body of the mail, because each SMTP
❦ 26 novembre 2015 21:33 +0100, Piotr Ożarowski :
>> No, that's not necessary as long as the orig tarball is already
>> present in the archive in another suite (which would be true for
>> backports, since the package is supposed to be derived from the
>> current version in testing).
>
> any poin
❦ 25 novembre 2015 00:00 +0100, Piotr Ożarowski :
>> > PS I'm getting all the emails from backports even if I wasn't the one
>> > who uploaded so this is official after all.
>>
>> This isn't new, and it's been discussed at large. Basically, we would
>> all like the BTS to have the feature to se
❦ 23 novembre 2015 09:20 +0100, Thomas Goirand :
> alabaster contextlib2 kazoo python-cachetools python-cffi python-cliff
> python-crank python-ddt python-docker python-eventlet python-git
> python-gitdb python-hypothesis python-ldap3 python-mock python-mysqldb
> python-pathlib python-repoze.who
❦ 20 octobre 2015 20:52 -0400, Barry Warsaw :
>>I'd remove this paragraph. Releases can be made via `git archive` and I did
>>that many times (assuming pristine-tar will still keep needed data to
>>regenerate exact same tarball). If you meant that we don't want to keep
>>complete upstream git h
❦ 2 octobre 2015 10:30 +0200, Piotr Ożarowski :
>> ❦ 2 octobre 2015 09:41 +0200, Piotr Ożarowski :
>>
>> > * removal¹ of packages (not person) from the team if there's no
>> > contribution in 3 months in a row and no other team wants to take over
>> > given package
>>
>> 3 months is qu
❦ 2 octobre 2015 09:41 +0200, Piotr Ożarowski :
> * removal¹ of packages (not person) from the team if there's no
> contribution in 3 months in a row and no other team wants to take over
> given package
3 months is quite short. I have packages that don't get updates that
often. This should
❦ 1 octobre 2015 18:48 -0400, Scott Kitterman :
> For the git migration, the people taking the time to do the work or pay
> attention to the work and provide feedback are driving what happens
> when.
It's not possible to give feedback or help when we don't know anything
about the migration.
❦ 30 septembre 2015 21:41 +0200, Thomas Goirand :
> Piotr decided to remove me from the Python team. Those who don't agree
> (especially admins) please voice your concern. It is my view that this
> is an over reaction and that it should be reverted.
I am a bit worried that the team is handled b
❦ 29 septembre 2015 23:05 +0200, Piotr Ożarowski :
>> Yes, let's discourage any new packages from manually migrating or starting
>> out
>> in git just until flag day. But I'm not sure it's worth removing DPMT on
>> existing repos just to add it back, hopefully RSN.
>
> we agreed to something -
❦ 7 août 2015 12:49 -0400, Scott Kitterman :
> I don't think we should just throw away all the work that's been done up to
> now.
So, what's the situation? Should we do something during this Debconf?
--
Program defensively.
- The Elements of Programming Style (Kernighan & Plauger
❦ 9 août 2015 13:46 +0200, Lennart Weller :
>> Everything looks good except the LICENSE.txt which is not here. It is in
>> fact called LICENSE upstream and it should be added to the manifest to
>> be present in the tarball. A note to upstream would be nice. Add a
>> comment to debian/copyright
❦ 6 août 2015 22:15 +0200, Lennart Weller :
>> I believe that we are still using SVN but maybe the switch to git will
>> be done during the next Debconf.
>>
>> Personnaly, I don't really care if a package is team-maintained or
>> not. It is better if it is and it will allow you to find another
❦ 4 août 2015 16:34 +0200, Lennart Weller :
> I currently have two ITPs open for python-apps, pgcli[0] and mycli[1]
> and one for a python-module, prompt_toolkit[2], on which both
> depend. There is also a wishlist bug[3] on python-sqlparse as both
> CLIs require a newer version.
I am interest
❦ 27 avril 2015 11:20 +0200, Julien Cristau :
>> I am also in favor of removing python-support. It doesn't have any
>> obvious bugs but having several helpers is confusing. pybuild + dh
>> should be used for most packages.
>
> pybuild+dh is entirely orthogonal to python-support. I guess you mea
❦ 26 avril 2015 18:26 +0200, Luca Falavigna :
> now that Jessie has been released, and there's the intention to
> provide more support for Python 3 (e.g. paultag's mail to d-d-a),
> would it be time to start kicking out python-support from Debian as
> well?
>
> According to lintian, there should
❦ 27 août 2014 18:11 -0700, Nikolaus Rath :
>> 2. Sometimes I make repeated mistakes when building a package; under
>> subversion I have to make a new commit for each one before testing.
>
> Why is that? I'm testing my uncommitted changes with
>
> svn-buildpackage --svn-ignore-new --svn-builder
❦ 19 août 2014 21:44 -0400, Barry Warsaw :
> * Switching branches makes my editor unhappy.
>
> Why is this a PITA? Because Emacs will notice that a file you're visiting in
> a buffer is changed and will prompt you reload it. I guess because
> checkout-patched deletes the debian directory and u
❦ 16 juillet 2014 11:06 +0200, Jean Baptiste Favre :
> My Alioth ID is jbfavre-guest.
>
> I would like to join DPMT, so that I could close ITP #754703, while
> learning packaging good practices.
Piotr told me yesterday that he already added you. Isn't that the case?
--
Make input easy to proof
❦ 13 juillet 2014 13:28 +0200, Jean Baptiste Favre :
> I packaged python-vertica module available here:
> https://github.com/uber/vertica-python
>
> Packaging work is available here:
> https://github.com/jbfavre/python-vertica
>
> I would like to get it integrated into Debian.
> I already have a
❦ 26 février 2014 19:54 CET, Jakub Wilk :
> 2) Don't install both to the same directory, but rather install each
> one to its own debian/$pkgname/.
I did go for this solution which was pretty simple. I added on the top
of my debian/rules:
#+BEGIN_SRC makefile
# Hack to ensure Python stuff to b
❦ 23 février 2014 03:26 CET, Jakub Wilk :
> /usr/bin/netaddr has "#! /usr/bin/python" shebang, as expected.
> But when I rebuilt the package from source, the binary ended up with
> "#! /usr/bin/python3" shebang.
This is not the first time I get this when I have both a Python 2.x and
a Python 3
[...]
Sandro has orphaned python-concurrent.futures:
http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=736714
Since it is team maintained, I don't think it really makes sense. Should
we just close the bug report and remove Sandro from the Uploaders field?
--
panic("Oh boy, that early out of memo
❦ 26 janvier 2014 02:49 CET, Thomas Goirand :
>>> > Modules managed by python-support are installed in another directory
>>> > which is added to the sys.path using the .pth mechanism.
>> https://www.debian.org/doc/packaging-manuals/python-policy/ch-python.html#s-paths
>
> Oh ok. Thanks! However,
❦ 16 novembre 2013 21:12 CET, Ben Finney :
>> You could just run the command specified in tox.ini, eg "python setup.py
>> test".
>
> Okay. I'll need to request upstream de-couple the test commands (there
> are several commands specified in ‘tox.ini’) from ‘tox’.
>
> Where should I direct upstre
❦ 16 novembre 2013 10:06 CET, Ben Finney :
> Alternatively, I don't really care about the special features of ‘tox’;
> I only want to run the test suite with the specific PYthon version. What
> can I do in the build environment to run the test suite as ‘tox’ would
> run it?
You could just run t
❦ 20 octobre 2013 14:09 CEST, Vincent Bernat :
> Has someone already packages something depending on CFFI?
>
> The verification phase of CFFI expects to be able to write a C file to
> /usr/lib/python2.7/dist-packages//__pycache__/. This could be
> triggered on postinst but
Hi!
Has someone already packages something depending on CFFI?
The verification phase of CFFI expects to be able to write a C file to
/usr/lib/python2.7/dist-packages//__pycache__/. This could be
triggered on postinst but maybe there is something better to do, like
some way to explain to CFFI that
❦ 8 octobre 2013 07:18 CEST, Andrey Rahmatullin :
>> Though probably writing in this bug would
>> have been more efficient than writing in the topic of the IRC channel?
> Yes, that's my only mistake.
> Though of course it's a fundamental problem with non-DD packages: I've
> made a package I fi
❦ 24 septembre 2013 10:15 CEST, Piotr Ożarowski :
>> ups, looks like I forgot to install/usr/share/dh-python/dist/*_fallback
>> files. Will be fixed in next dh-python upload
>
> for now, simply add python-crypto and python3-crypto to Build-Depends
> and dh_python* will find the right ones (you p
❦ 24 septembre 2013 09:59 CEST, Vincent Bernat :
>> Date: Monday, September 23, 2013 @ 22:25:40
>> Author: bernat
>> Revision: 25933
>>
>> Let ${pythonX:Depends} find the dependencies on its own.
>
> Hi!
>
> I have a little problem with pyth
❦ 24 septembre 2013 00:25 CEST, ber...@users.alioth.debian.org :
> Date: Monday, September 23, 2013 @ 22:25:40
> Author: bernat
> Revision: 25933
>
> Let ${pythonX:Depends} find the dependencies on its own.
Hi!
I have a little problem with python3:Depends. The dependency with
python3-cryp
❦ 2 août 2013 15:15 CEST, Piotr Ożarowski :
> dh-python is already in unstable \o/
While upgrading some of my packages, I have switched to pybuild and this
works well. In the SVN, there is "cerealizer" and "pycha".
However, about python2/python3 packages, I did also notice that I did
add Pyth
❦ 2 août 2013 16:36 CEST, Piotr Ożarowski :
>> Worse, it doesn't even try to parse Build-Depends. The relevant logic
>> appears to be:
>>
>> if [ -f /usr/share/dh-python/dh_python2 ] &&\
>> grep -q dh-python ./debian/control 2>/dev/null
>> then
>> exec /usr/share/dh-python/dh_python2 $@
❦ 21 juillet 2013 09:47 CEST, Luca Falavigna :
> 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
> [1], which shou
Hi!
I just converted a package to add a Python3 package. I expected this to
be as simple as:
1. Declaring the package in debian/control and add the appropriate
dependency stuff.
2. Use dh --with python2,python3 $@.
However, this is more tricky:
- dh_auto_build has to be overrided to also
❦ 22 février 2013 16:12 CET, Thomas Goirand :
>>> From a server in a data center in Seattle, it took me 90 seconds
>>> to download the packaging sources of python-eventlet. Compare
>>> this to the 4 seconds it takes me to clone python-warlock from
>>> Alioth, upstream source included !!!
>> your
❦ 4 février 2013 20:00 CET, Örjan Persson :
> I don't have the time to maintain my packages anymore. I just wanted to
> check with you guys first if you're interested in adopting the packages
> before I RFA them. The packages are python-setproctitle[1],
> python-greenlet[2] and python-gevent[3]
While I could
add the appropriate bits to each clean target in debian/rules, it seems
better to fix the problem either in dh_python2 or in setuptools. Any
thoughts?
--
Vincent Bernat ☯ http://vincent.bernat.im
Don't just echo the code with comments - make every comment count.
dbconfig-common). This will help
translators.
--
Vincent Bernat ☯ http://vincent.bernat.im
printk("What? oldfid != cii->c_fid. Call 911.\n");
2.4.3 linux/fs/coda/cnode.c
pgpl3T22DPB16.pgp
Description: PGP signature
ld check for VERBOSE variable before
using echo.
--
Vincent Bernat ☯ http://vincent.bernat.im
#if 0
2.2.16 /usr/src/linux/fs/buffer.c
pgpRVc6ievHkE.pgp
Description: PGP signature
On Tue, 18 Oct 2011 11:51:28 +0200, Ole Streicher wrote:
Dear lists,
I am working on a package (python-pywcs) that may include a
"nosetest"
which I want to run before installation.
For this, I put the following line into debian/rules (for debhelper):
override_dh_auto_test:
nosetest
handle some steps, like
dependencies (in ${python:Depends}) and install (keep only debug files).
--
Vincent Bernat ☯ http://vincent.bernat.im
/*
* Should be panic but... (Why are BSD people panic obsessed ??)
*/
2.0.38 /usr/src/linux/net/ipv4/ip_fw.c
pgpoIgYEalYER.pgp
Description: PGP signature
Hi!
Is this page up-to-date?
http://wiki.debian.org/Python/DbgBuilds
Does dh_python2 handle this part itself now?
--
Vincent Bernat ☯ http://vincent.bernat.im
Make input easy to proofread.
- The Elements of Programming Style (Kernighan & Plauger)
pgpB8brVrfl7W.pgp
Descrip
information to convey, but I'm not sure the warning
> actually does that very well.
> I guess fixing that should start with a bug report on reportbug. ;)
It seems that it is the BTS which declares python as a "dependency
package". Maybe this makes more sense for other
e
> Use advanced or expert mode, like Piotr does, and the problem will go
> away. :)
Thanks for the information. However, I still get the message with expert
mode. But I am allowed to choose "python".
--
Vincent Bernat ☯ http://vincent.bernat.im
Avoid multiple exits from loop
python2 manpages
stating to depends on cdbs (>= 0.4.90-1~). Since it is a native package,
this should be cdbs (>= 0.4.90~) (or cdbs (>= 0.4.90)).
--
Vincent Bernat ☯ http://vincent.bernat.im
Don't comment bad code - rewrite it.
- The Elements of Programming Style (Kernigha
need
> only a single line in debian/.links to do that.
Don't you need to remove jquery.js from your package as well?
--
Vincent Bernat ☯ http://www.luffy.cx
Use free-form input when possible.
- The Elements of Programming Style (Kernighan & Plauger)
pgpH48B6xGw7Q.pgp
Description: PGP signature
OoO La nuit ayant déjà recouvert d'encre ce jour du lundi 13 juin 2011,
vers 23:23, Nikolaus Rath disait :
> Ah, of course. This should be fixed as well now.
OK. Uploaded.
--
Vincent Bernat ☯ http://www.luffy.cx
Indent to show the logical structure of a program.
- The Ele
e of missing hooks for signature
> postprocessing.
> Discussion:
> https://bitbucket.org/birkenfeld/sphinx/issue/564
> Relevant changesets:
> https://bitbucket.org/birkenfeld/sphinx/changeset/de340a6098c7
> https://bitbucket.org/birkenfeld/sphinx/changeset/a8b0ef275438
> I also added a sphinx wishlist bug to backport this feature (Bug
> #630409).
OK to wait for Sphinx 1.1 (or for the resolution of bug #630409).
--
Vincent Bernat ☯ http://www.luffy.cx
/*
* For moronic filesystems that do not allow holes in file.
* We may have to extend the file.
*/
2.4.0-test2 /usr/src/linux/fs/buffer.c
pgpccofTDGA2W.pgp
Description: PGP signature
red, so I wanted to wait until the Sphinx 1.1 hits the archive.
> When that has happened, it's just a matter of uncommenting one line in
> debian/rules.
I was also a bit surprised that so many DD did agree to not rebuild the
documentation. I would prefer that the documentation is
to do?
I still need to review the package. Also ensure that you applied what
Jakub said in debian-mentors@.
--
Vincent Bernat ☯ http://www.luffy.cx
Use statement labels that mean something.
- The Elements of Programming Style (Kernighan & Plauger)
pgpVh9VEtPxzN.pgp
Description: PGP signature
th this but I take it as
some sort of implicit acknowledgment of dh_python2. Therefore, +1 for
only one helper in Wheezy.
--
Vincent Bernat ☯ http://www.luffy.cx
Use self-identifying input. Allow defaults. Echo both on output.
- The Elements of Programming Style (Kernighan & Plauger)
pgpNdPjRc9SRS.pgp
Description: PGP signature
package team
> maintained. Would that be preferred? My alioth login is
> nikratio-guest.
I can sponsor you. Please join the team. Piotr, could you add Nikolaus
to the team?
--
Vincent Bernat ☯ http://www.luffy.cx
Don't patch bad code - rewrite it.
- The
what the
story behind python-support and dh-python2 is. It seems that everything
was dealed in private. From my point of view, dh-python2 is here only
because python-central could not be deprecated by its author in favor of
python-support for political reasons. That does not help to adopt
OoO Lors de la soirée naissante du mardi 08 mars 2011, vers 18:56, Jakub
Wilk disait :
>> Breaks: python2.3-nevow (<< 0.7.0-1.1), python2.4-nevow (<< 0.7.0-1.1),
>> ${python:Breaks}
> Apparently dh_python2 doesn't cope with Breaks spanning across
> multiple physical lines. Yay for new and shiny
Hi!
Could someone look at "nevow" in the repository. I have upgraded it to
use dh_python2 (from python-central). However, the "Python-Version"
field in the binary package did disappear, ${python:Breaks} is expanded
to nothing and I have a new lintian warning.
debian/control (partial):
So
OoO En ce début d'après-midi nuageux du dimanche 06 mars 2011, vers
14:48, Sandro Tosi disait :
>> There was some discussions about switching from SVN to git. I don't
>> remember everything but a major blocker was that it is not possible to
>> checkout a subtree with git and managing
Hi!
There was some discussions about switching from SVN to git. I don't
remember everything but a major blocker was that it is not possible to
checkout a subtree with git and managing a lot of git repositories will
make it difficult to do global changes to the "global" repository.
There i
OoO En cette nuit nuageuse du mardi 01 mars 2011, vers 00:53, Piotr
Ożarowski disait :
> cdbs and dh doesn't support Python 3.X yet. I provided a patch for CDBS
> but it was rejected, dunno why.
I suppose that this is bug #604721. Why do you say this was rejected? It
just seems that the m
OoO En cette fin de matinée radieuse du mardi 22 février 2011, vers
11:51, Andrey Rahmatullin disait :
> Many Python modules ship unit tests which do not require module
> instalation or user interaction and so can be run automatically during the
> build time. They can be a very good QA tool,
OoO En cette matinée ensoleillée du lundi 21 février 2011, vers 09:29,
Piotr Ożarowski disait :
>> Is there anything else?
> There will be a quick guide for maintainers in dh_python2 manpage¹ after
> next upload, see also this² wiki page.
> [¹] http://deb.li/dhp2
> [²] http://wiki.debian.org/
Hi!
I am switching some packages to dh_python2. I am using CDBS. I don't
find much documentation on how to do the transition. Here is what I have
done:
1. Remove DEB_PYTHON_SYSTEM from debian/rules
2. Update Build-Depends:
cdbs (>= 0.4.90),
python (>= 2.6.5)
Is
Hello and happy new year!
Do you know any Python module that the author states as being licensed
under "Python license"? Since Python license is stated as a contract
between the licensee and the PSF, I wonder how to put that in
debian/copyright.
My problem is in python-cerealizer
OoO Vers la fin de l'après-midi du dimanche 21 novembre 2010, vers
16:37, Filippo Rusconi disait :
> OK, so I may test if the content of the PYTHONPATH variable is empty
> the way below, so that I can set the path in differenciated manners :
> ~~ start-script ~~~
> #!/bin/
OoO En ce début d'après-midi nuageux du mardi 31 août 2010, vers 14:56,
"Giacomo A. Catenazzi" disait :
>> I disagree, stuff written in C or Perl doesn't crash when the locale
>> is not set properly and neither should stuff written in Python.
> hmm.
> In C it is because the POSIX application us
OoO La nuit ayant déjà recouvert d'encre ce jour du dimanche 22 août
2010, vers 23:16, Floris Bruynooghe disait :
>> Perl spits out a lot of annoying warnings when using a non existing
>> locale. And it does this for any perl script.
>>
>> perl: warning: Setting locale failed.
>> perl:
OoO En cette matinée ensoleillée du dimanche 22 août 2010, vers 09:44,
Paul Wise disait :
>> I don't think this is a bug at all. I'd rather say it's an user error.
> I disagree, stuff written in C or Perl doesn't crash when the locale
> is not set properly and neither should stuff written in P
OoO Lors de la soirée naissante du mercredi 28 juillet 2010, vers 17:04,
je disais:
> Looks like the exaile[1] package is very out-of-date.
> I use debian and program in python for years and I think its time
> to me contribute somehow, and I would like to start with exaile.
> I tried to contact t
OoO Lors de la soirée naissante du mercredi 14 juillet 2010, vers 17:17,
Bernd Zeimetz disait :
I'm working on package that uses CDBS
>>
>>> That's not a very good choice.
>>
>> Why?
> Because cdbs is an unmaintainable beast of Makefiles. I'm not sure who is
> willing to keep the Python
OoO La nuit ayant déjà recouvert d'encre ce jour du dimanche 11 juillet
2010, vers 23:05, Jakub Wilk disait :
>> I'm working on package that uses CDBS
> That's not a very good choice.
Why?
--
printk("VFS: Busy inodes after unmount. "
"Self-destruct in 5 seconds. Have a nice day...\n
OoO En ce milieu de nuit étoilée du dimanche 06 juin 2010, vers 04:43,
Scott Kitterman disait :
> A couple of weeks ago, Jakub Wilk noticed this issue and prepared both a DD
> list of affected packages and the grep output that was used to detect
> potentially affected packages. I know some o
OoO Pendant le journal télévisé du lundi 17 mai 2010, vers 20:01, Jakub
Wilk disait :
> 19 packages uses syntax constructs specific to Python 2.5+ in their
> public modules but don't declare that minimum supported version is
> 2.5. I'm looking for volunteers to do MBF.
Out of curiosity, what
OoO En ce début d'après-midi ensoleillé du dimanche 28 février 2010,
vers 15:29, je disais:
> Well, I disagree. Python 2.6 is not the default. Packages are currently
> built with Python 2.5 and do not fail to build in a current pbuilder. We
> already had a bunch of bug reports about packa
OoO Vers la fin de l'après-midi du dimanche 28 février 2010, vers 16:46,
Josselin Mouette disait :
>> It would be far easier to let Python 2.6 be the default, then file (or
>> upgrade) serious bugs and solve them in a week or two.
> Yeah sure, let’s knowingly break dozens of packages by swit
OoO Pendant le journal télévisé du samedi 27 février 2010, vers 20:19,
Luca Falavigna disait :
> after some discussions on #debian-python, I'd like to propose
> increasing severity of Python 2.6 related bugs [1] to serious.
Well, I disagree. Python 2.6 is not the default. Packages are current
OoO Pendant le temps de midi du dimanche 24 janvier 2010, vers 12:58,
Steve Langasek disait :
>> > as you probably know, python2.6 has recently been added to supported
>> > Python version in unstable [1].
>> Why currently compiling a package which contains binary extensions only
>> build the
OoO Pendant le journal télévisé du samedi 23 janvier 2010, vers 20:15,
Luca Falavigna disait :
> as you probably know, python2.6 has recently been added to supported
> Python version in unstable [1].
Why currently compiling a package which contains binary extensions only
build them for python
1 - 100 of 159 matches
Mail list logo
