On Wed, Jul 2, 2008 at 5:48 PM, Martin Kelly <[EMAIL PROTECTED]> wrote: > I have no problem with joining DPMT; I at a student and during the school > year I often have very little time to maintain packages. If someone wants to > help me with this, I have no problem with it.
Great. I will help you with it. > I do have a question about your patch, however. Isn't this a strange way to > create a new release? Why would you add version information to the rules > file? Why not just follow the standard procedure here: > http://www.debian.org/doc/maint-guide/ch-update.en.html#s-newupstream-real > ? No, the version is there just to create an original tarball. Use it like this: [EMAIL PROTECTED]:~/debian/packages/python-gmpy$ ls debian [EMAIL PROTECTED]:~/debian/packages/python-gmpy$ debian/rules orig-tarball wget http://gmpy.googlecode.com/files/gmpy-1.03.zip; --2008-07-02 17:53:52-- http://gmpy.googlecode.com/files/gmpy-1.03.zip Resolving gmpy.googlecode.com... 64.233.187.82 Connecting to gmpy.googlecode.com|64.233.187.82|:80... connected. HTTP request sent, awaiting response... 200 OK Length: 86711 (85K) [application/x-zip] Saving to: `gmpy-1.03.zip' 100%[======================================>] 86,711 158K/s in 0.5s 2008-07-02 17:53:53 (158 KB/s) - `gmpy-1.03.zip' saved [86711/86711] unzip gmpy-1.03.zip Archive: gmpy-1.03.zip creating: gmpy-1.03/ creating: gmpy-1.03/doc/ inflating: gmpy-1.03/doc/gmpydoc.txt inflating: gmpy-1.03/doc/index.html inflating: gmpy-1.03/mac_build.txt inflating: gmpy-1.03/README inflating: gmpy-1.03/setes.py inflating: gmpy-1.03/setup.py creating: gmpy-1.03/src/ inflating: gmpy-1.03/src/gmpy.c inflating: gmpy-1.03/src/gmpy.h inflating: gmpy-1.03/src/pymemcompat.h inflating: gmpy-1.03/src/pysymbolicext.c creating: gmpy-1.03/test/ inflating: gmpy-1.03/test/gmpy_test.py inflating: gmpy-1.03/test/gmpy_test_cvr.py inflating: gmpy-1.03/test/gmpy_test_dec.py inflating: gmpy-1.03/test/gmpy_test_mpf.py inflating: gmpy-1.03/test/gmpy_test_mpq.py inflating: gmpy-1.03/test/gmpy_test_mpz.py inflating: gmpy-1.03/test/gmpy_test_rnd.py inflating: gmpy-1.03/test/gmpy_truediv.py inflating: gmpy-1.03/test/test_large.py inflating: gmpy-1.03/test/timing1.py inflating: gmpy-1.03/test/timing2.py inflating: gmpy-1.03/test/timing3.py inflating: gmpy-1.03/windows_build.txt tar czf python-gmpy_1.03.ds.orig.tar.gz gmpy-1.03 rm -rf gmpy-1.03 gmpy-1.03.zip [EMAIL PROTECTED]:~/debian/packages/python-gmpy$ ls debian python-gmpy_1.03.ds.orig.tar.gz [EMAIL PROTECTED]:~/debian/packages/python-gmpy$ As you can see, python-gmpy_1.03.ds.orig.tar.gz was created, that you can then use for upload. > I am new to maintaining and don't quite understand how this patch would be > used to create a new version. You agreed to use DPMT, so the best way is to: man svn-buildpackage i.e.: svn+ssh://[EMAIL PROTECTED]/svn/python-modules/packages/python-gmpy/trunk python-gmpy cd python-gmpy svn-buildpackage -b And that's it. You put the orig.tar.gz to ../tarballs. Feel free to ask if you have more questions. If no, is it ok if we upload it? Ondrej -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
