New debhelper update
Hi,
I've uploaded a NMU 5.0.37.3 in DELAYED/1-day fixing several issues
concerning dh_python:
* Update of dh_python
- when buidling for a non-standard Python version, generate more
reasonable Depends like "python (>= X.Y) | pythonX.Y"
Closes: #375576
- fix handling of private extensions. Closes: #375948
- fix parsing of XS-Python-Version, it didn't work if only fixed versions
were listed in XS-Python-Version.
- fix use of unitialized value. Closes: #374776
- fix typos in POD documentation. Closes: #375936
Please find attached the cumulative patch of the last 3 uploads (5.0.37 ->
5.0.37.3).
You can also find a copy of the package here:
http://people.debian.org/~hertzog/python/
http://people.debian.org/~hertzog/python/debhelper_5.0.37.3_all.deb
http://people.debian.org/~hertzog/python/debhelper_5.0.37.3.dsc
Dear debian-python readers, please test this updated dh_python
and report any problem to me.
Cheers,
--
Raphaël Hertzog
Premier livre français sur Debian GNU/Linux :
http://www.ouaza.com/livre/admin-debian/
diff -Nru debhelper-5.0.37/debian/changelog debhelper-5.0.37.3/debian/changelog
--- debhelper-5.0.37/debian/changelog 2006-06-12 03:33:28.0 +0200
+++ debhelper-5.0.37.3/debian/changelog 2006-07-10 13:27:50.0 +0200
@@ -1,3 +1,52 @@
+debhelper (5.0.37.3) unstable; urgency=low
+
+ * Non-maintainer upload.
+ * Update of dh_python
+- when buidling for a non-standard Python version, generate more
+ reasonable Depends like "python (>= X.Y) | pythonX.Y"
+ Closes: #375576
+- fix handling of private extensions. Closes: #375948
+- fix parsing of XS-Python-Version, it didn't work if only fixed versions
+ were listed in XS-Python-Version.
+- fix use of unitialized value. Closes: #374776
+- fix typos in POD documentation. Closes: #375936
+
+ -- Raphael Hertzog <[EMAIL PROTECTED]> Mon, 10 Jul 2006 13:20:06 +0200
+
+debhelper (5.0.37.2) unstable; urgency=low
+
+ * Non-maintainer upload.
+ * Update of dh_python
+- vastly refactored, easier to understand, and the difference
+ between old policy and new policy is easier to grasp
+- it supports an -X option which can be used to not scan some files
+- uses debian/pyversions as reference source of information for
+ dependencies but also parse the XS-Python-Version header as fallback.
+- ${python:Versions}'s default value is XS-Python-Version's value
+ instead of "all" when the package doesn't depend on a
+ specific python version. Closes: #373853
+- always generate ${python:Provides} and leave the responsibility to the
+ maintainer to not use ${python:Provides} if he doesn't want the
+ provides.
+- uses debian/pycompat or DH_PYCOMPAT as reference field to run in new
+ policy mode. The presence of XS-Python-Version will also trigger the
+ new policy mode (this is for short-term compatibility, it may be removed
in
+ the not too-distant future).
+ DH_PYCOMPAT=1 is the default mode and is compatible to the old policy.
+ DH_PYCOMPAT=2 is the new mode and is compatible with the new policy.
+ * Use "grep ^Version:" instead of "grep Version:" on the output of
+dpkg-parsechangelog since the above changelog entry matched "Version:" and
+thus made the build fail.
+
+ -- Raphael Hertzog <[EMAIL PROTECTED]> Sat, 17 Jun 2006 20:44:29 +0200
+
+debhelper (5.0.37.1) unstable; urgency=low
+
+ * Non-maintainer upload.
+ * Integrate the new dh_python implementing the new Python policy. Closes:
#370833
+
+ -- Raphael Hertzog <[EMAIL PROTECTED]> Mon, 12 Jun 2006 08:58:22 +0200
+
debhelper (5.0.37) unstable; urgency=low
* dh_installmodules: depmod -a is no longer run during boot, so if a module
diff -Nru debhelper-5.0.37/debian/rules debhelper-5.0.37.3/debian/rules
--- debhelper-5.0.37/debian/rules 2006-06-03 23:06:41.0 +0200
+++ debhelper-5.0.37.3/debian/rules 2006-06-19 18:31:06.0 +0200
@@ -26,7 +26,7 @@
}'
# Figure out the `current debhelper version.
-VERSION=$(shell expr "`dpkg-parsechangelog |grep Version:`" : '.*Version:
\(.*\)')
+VERSION=$(shell expr "`dpkg-parsechangelog |grep ^Version:`" : '.*Version:
\(.*\)')
PERLLIBDIR=$(shell perl -MConfig -e 'print $$Config{vendorlib}')
diff -Nru debhelper-5.0.37/dh_python debhelper-5.0.37.3/dh_python
--- debhelper-5.0.37/dh_python 2006-04-24 22:09:12.0 +0200
+++ debhelper-5.0.37.3/dh_python2006-07-10 14:14:53.0 +0200
@@ -12,7 +12,7 @@
=head1 SYNOPSIS
-B [S>] [B<-n>] [B<-V> I] [S>]
+B [S>] [B<-n>] [B<-X>I] [B<-V>
I] [S>]
=head1 DESCRIPTION
@@ -21,7 +21,40 @@
will also add a postinst and a prerm script if required.
The program will look at python scripts and modules in your package, and
-will use this information to generate a dependency on python, with the
+will use this information to generate adequate dependencies. Additionally,
+it will also use
Re: What GUI lib to choose: GTK, TK, WX, QT, other?
Hi On Sun, 9 Jul 2006 00:13:11 +0200 "Sandro Tosi" <[EMAIL PROTECTED]> wrote: > I'm almost new to python and I'm even almost sure that this could be > not the right place where ask this, but we do have in common the > interest in Debian and the interest in Python, so I'll do the same... > :)) > > Since I would use python for some new projects, and I'd like to have > them graphical, I'm wondering what is the best gui to choose. > > I've seen that tk would be the easier (but even a bit unpretty) to > embrace, wx would be the more portable, etc. I was in very similar situation three years ago. I decided to use wxWidgets and now I thing about rewrite using something less problematic (probably Gtk). Maybe I just hit too much corner cases, but wxWidgets brought me too much pain and workarounds in my code. -- Michal Čihař | http://cihar.com | http://blog.cihar.com -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
Bug#375936: Info received (New debhelper update)
Thank you for the additional information you have supplied regarding this problem report. It has been forwarded to the package maintainer(s) and to other interested parties to accompany the original report. Your message has been sent to the package maintainer(s): Joey Hess <[EMAIL PROTECTED]> If you wish to continue to submit further information on your problem, please send it to [EMAIL PROTECTED], as before. Please do not reply to the address at the top of this message, unless you wish to report a problem with the Bug-tracking system. Debian bug tracking system administrator (administrator, Debian Bugs database)
Bug#374776: Info received (New debhelper update)
Thank you for the additional information you have supplied regarding this problem report. It has been forwarded to the package maintainer(s) and to other interested parties to accompany the original report. Your message has been sent to the package maintainer(s): Joey Hess <[EMAIL PROTECTED]> If you wish to continue to submit further information on your problem, please send it to [EMAIL PROTECTED], as before. Please do not reply to the address at the top of this message, unless you wish to report a problem with the Bug-tracking system. Debian bug tracking system administrator (administrator, Debian Bugs database)
Bug#375948: Info received (New debhelper update)
Thank you for the additional information you have supplied regarding this problem report. It has been forwarded to the package maintainer(s) and to other interested parties to accompany the original report. Your message has been sent to the package maintainer(s): Joey Hess <[EMAIL PROTECTED]> If you wish to continue to submit further information on your problem, please send it to [EMAIL PROTECTED], as before. Please do not reply to the address at the top of this message, unless you wish to report a problem with the Bug-tracking system. Debian bug tracking system administrator (administrator, Debian Bugs database)
Bug#375576: Info received (New debhelper update)
Thank you for the additional information you have supplied regarding this problem report. It has been forwarded to the package maintainer(s) and to other interested parties to accompany the original report. Your message has been sent to the package maintainer(s): Joey Hess <[EMAIL PROTECTED]> If you wish to continue to submit further information on your problem, please send it to [EMAIL PROTECTED], as before. Please do not reply to the address at the top of this message, unless you wish to report a problem with the Bug-tracking system. Debian bug tracking system administrator (administrator, Debian Bugs database)
Python-Qwt
Hi I have been spending my time recently on packaging python-qwt for Debian. I am very interested in getting it into the distribution. Is there anyone that might be willing to help me. The packages can be found at. http://mve035.mc2.chalmers.se/~gudjon/debian/pyqwt4/ I did compile the packages against python-numpy 0.9.8 that is still not in the Debian distribution but on its way. Any suggestions on how to solve that issue are welcome. Thanks for any help Gudjon -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
Re: What GUI lib to choose: GTK, TK, WX, QT, other?
-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 Michal Čihař wrote: > Hi > > On Sun, 9 Jul 2006 00:13:11 +0200 "Sandro Tosi" > <[EMAIL PROTECTED]> wrote: > >> I'm almost new to python and I'm even almost sure that this >> could be not the right place where ask this, but we do have in >> common the interest in Debian and the interest in Python, so >> I'll do the same... :)) >> >> Since I would use python for some new projects, and I'd like to >> have them graphical, I'm wondering what is the best gui to >> choose. >> >> I've seen that tk would be the easier (but even a bit unpretty) >> to embrace, wx would be the more portable, etc. > > I was in very similar situation three years ago. I decided to use > wxWidgets and now I thing about rewrite using something less > problematic (probably Gtk). Maybe I just hit too much corner > cases, but wxWidgets brought me too much pain and workarounds in > my code. Do you remember any examples? - -- Ron Johnson, Jr. Jefferson LA USA Is "common sense" really valid? For example, it is "common sense" to white-power racists that whites are superior to blacks, and that those with brown skins are mud people. However, that "common sense" is obviously wrong. -BEGIN PGP SIGNATURE- Version: GnuPG v1.4.3 (GNU/Linux) Comment: Using GnuPG with Mozilla - http://enigmail.mozdev.org iD8DBQFEsnUkS9HxQb37XmcRAnETAJ4wyOiCW+0hdZa0JvCENhty4pp4AACgulJb lqsQtzepUx4sZCoT3IruUr8= =vHvo -END PGP SIGNATURE- -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
Re: Python-Qwt
On Mon, Jul 10, 2006 at 05:02:42PM +0200, Gudjon I. Gudjonsson wrote: > Hi >I have been spending my time recently on packaging python-qwt for > Debian. I am very interested in getting it into the distribution. Is > there anyone that might be willing to help me. The packages can be > found at. > http://mve035.mc2.chalmers.se/~gudjon/debian/pyqwt4/ > I did compile the packages against python-numpy 0.9.8 that is still not in > the Debian distribution but on its way. Any suggestions on how to solve > that issue are welcome. numpy is coming to Debian. It is currently in the NEW queue, waiting for the ftp-master's approval, so you just need to wait a little bit for the package to hit the archive. Thanks for packaging Qwt. -- Alexandre Fayolle LOGILAB, Paris (France) Formations Python, Zope, Plone, Debian: http://www.logilab.fr/formations Développement logiciel sur mesure: http://www.logilab.fr/services Informatique scientifique: http://www.logilab.fr/science signature.asc Description: Digital signature
Re: What GUI lib to choose: GTK, TK, WX, QT, other?
On Mon, 10 Jul 2006 10:41:24 -0500
Ron Johnson <[EMAIL PROTECTED]> wrote:
> Do you remember any examples?
Segfault while passing unicode string [1], various renames over versions
[2] (I know those were devel versions, but that time it was only
working choice for vendors who didn't want Gtk 1), no way to make
buttons in correct order of buttons in dialog for both Gtk and Win (to
match platform usual order).
Some problems can be solved by supporting only one version with one
build options like BitPim does ("Note that you must use version 2.6.3.2
and you must use the Unicode version."), but I prefer my application to
work also on a bit older systems (eg. up to Fedora Core 4 they
didn't have unicode enabled build in distro, I'm not sure about FC 5)...
1.
https://sourceforge.net/tracker/?func=detail&aid=855297&group_id=9863&atid=109863
2. http://gonzui.cihar.com/markup/wammu-0.13/Wammu/Editor.py#l22
--
Michal Čihař | http://cihar.com | http://blog.cihar.com
--
To UNSUBSCRIBE, email to [EMAIL PROTECTED]
with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
Bug#377680: pyro: Does not follow the new python policy
Package: pyro Version: 3.5-1 Severity: important Tags: patch Hi Cédric, The pyro package currently does not follow the new Python policy (http://wiki.debian.org/DebianPython/NewPolicy), but strangely no bug has been filed against it so far. The attached patch fixes this, as well as the multiple python version bug which has been reported on pyro (it just lacks an entry to close this bug in debian/changelog). The migration was done using python-central. Unless you strongly oppose, I will probably upload the updated package tomorrow. A bientôt, -- System Information: Debian Release: testing/unstable APT prefers unstable APT policy: (500, 'unstable') Architecture: i386 (i686) Shell: /bin/sh linked to /bin/bash Kernel: Linux 2.6.17-1-686 Locale: [EMAIL PROTECTED], [EMAIL PROTECTED] (charmap=ISO-8859-15) Versions of packages pyro depends on: ii python2.3.5-11 An interactive high-level object-o pyro recommends no packages. pyro_3.5-1.1.diff.gz Description: Binary data
