[Date Prev][Date Next] [Thread Prev][Thread Next] [Date Index] [Thread Index]

Bug#693069: RFS: rurple-ng -- learn programming in python with a robot



Hi Thomas,

(re-sending this mail, now with all Cc: people in Cc: plus adding the missing URL for [1])

On  Mi 09 Okt 2013 20:33:42 CEST, Thomas Koch wrote:

On Monday, September 30, 2013 04:34:47 PM Mike Gabriel wrote:
I can write a manpage if you insist.
I do insist. ;-)

Hi Mike,

I added a manpage:
http://mentors.debian.net/package/rurple-ng

Cool. Will take a look at it later (see below).

i did not yet write a watchfile because I did not yet find a suitable place to
place the upstream project. I pushed it to gitorious[1] but gitorious has no
site listing the tags of the project and thus I did not see how to write a
watchfile. And as much as I'd prefer the free software based gitorious site
over github it's so much lacking behind. It does not even have a bugtracker.

I can confirm this. I run a private Gitorious instance at Uni and that one has that feature available. Weird. Anyway, as you are upstream and downstream in one person now, this can be easily overviewed and you will know when upstream has a new release. So, forget about the watch file (for now).

If you want to use gitorious.org for other projects, nag them for the tag stuff in their WebUI. You will need it (or another Git hoster).

[1] https://gitorious.org/rurple-ng/rurple-ng/

I changed the versionnumber to 0.5+16 to indicate that I packed upstreams 0.5
version plus the last 16 commits to master. I'm sorry, I should have added a
new entry to debian/changelog instead of editing the first entry, but I
remember that this might cause trouble for first uploads to the archive
(missing orig tarball).

We got to get this fixed first:

The upstream version should be changed into

   0.5+git2013xxyy (the date you clone that upstream Git repos).

In /debian/changelog you then place the concrete commit hash you used for creating that orig tarball (see [1]).

The Debian revision will then of course be -1 and we upload indeed a new orig tarball (the one you snapshot from the used Git branch).

Please change your package (again, I am sorry) accordingly and then I will take a look at the rest.

Mike

[1] http://ftp-master.metadata.debian.org/changelogs//main/n/node-security/node-security_1.0.0~git20130515-1_changelog

(Note: in this example, the upstream Git was clone before the release of 1.0.0, in your case you cloned after the 0.5 release, so you replace ~git<date> by +git<date> in the upstream version...
--

mike gabriel aka sunweaver (Debian Developer)
fon: +49 (1520) 1976 148

GnuPG Fingerprint: 9BFB AEE8 6C0A A5FF BF22  0782 9AF4 6B30 2577 1B31
mail: sunweaver@debian.org, http://sunweavers.net

Attachment: Digitale_PGP_Signatur
Description: PGP signature

Attachment: binFpgljNbVmQ.bin
Description: =?utf-8?b?w5ZmZmVudGxpY2hlciA=?= =?utf-8?b?UEdQLVNjaGzDvHNzZWw=?=

Attachment: pgpBLYdka63pP.pgp
Description: Digitale PGP-Signatur


Reply to: