[00:33] hi, im in the process of making my first deb package. The software im packing has no version, what version should i put? [00:38] samd: What software is it, is it taken from a revision control of some sort? [00:38] samd: Normally, one would use the date of the release as a stand-in version [00:39] arand: yes, its mjpg-streamer, it was taken from the svn repository because it was the only source i found, if i download the tar.gz package from them, they use "r150" as 'version' where 150 is the last commit [00:40] As an example I am using "lugaru-data_0~20110520.1+hge4354-1" for a game from mercurial (hg) with no versioning currently [00:41] arand: alright, sounds good, ill use the date [00:41] samd: So following that it would be "0~$date.1+svn150-1" or something to that effect [00:43] arand: sounds good, thank you very much, ill continue with the packing [00:43] arand: im following the guide from https://wiki.ubuntu.com/PackagingGuide/Basic [00:43] samd: Alternatively r150, I think that might just be your preference [00:45] arand: i tried that , but for some reason dh_make didnt recognized "r150" as a version, i might had it wrote wrong, but i changed the version to 1.0 just to see, and it worked. [00:46] dh_make might be a bit more strict there.. you can always change it afterwards in the changelog though [00:47] I meant 0~$date.1+r150-1 is also an alternative [00:47] arand: alright, , i think i will go and try with 0~$date.1+r150-1 [00:48] (replacing $date with the date of the commit, just to note) [00:48] yeah, something like YYYYMMDD i got that [00:49] no need to include both a date and a commit number. one of the two will suffice [00:50] oh ok [00:50] I'm not sure but I've had some discussions with debian folks who are of the opinion that the revision number is not relevant at all, I personally think it is though, even in the case of hashes, ah, there we go ^ :) [00:51] 0~YYYYMMDD-1 or 0~svn12-1 (or bzr) are both sensible versions [00:51] i see, what does the 0~ mean? [00:52] It allows for any kind of 0something to be a higher version than 0~something [00:52] revision number is not a good idea for git (where the number of revisions is variable), but svn, bzr and hg have monotonic revision numbers (within a single tree, in hg and bzr, assuming no rebasing or commit removal) [00:52] 0~ is smaller than 0 [00:53] i see [00:53] So basically, it means that you don't have to worry about upstream releasing a 0.0.0.0.0.1 version, it will always be greater than 0~ [00:54] got it [00:55] let me try to build the package , ill probably throw out more questions as i advance. thank you! [00:56] * tumbleweed is going to bed, enjoy :) === JackyAlcine is now known as Guest12458 === webjadmin is now known as JackyAlcine === Guest47276 is now known as Adri2000 [08:29] morning [08:29] (in before dholbach who isn't evne here!) [08:30] morning [08:30] Laney: he is at Dublin sprint, so … that might be the delay [08:31] vish: I am going to claim this as a victory nonetheless. :-) [08:31] :D [08:33] Laney: got a min for a PM? [08:34] yeah === _ruben_ is now known as _ruben === menesis1 is now known as menesis === kklimonda^ is now known as kklimonda === kklimonda is now known as Guest43465 === Guest43465 is now known as kklimonda^ === kklimonda^ is now known as kklimonda === Guest77389 is now known as baruchel === baruchel is now known as ilquette === ilquette is now known as zabul [16:57] I made a mistake in the spelling of a word in the dep-3 patch tagging guidelines. [16:57] Do I send a patch to debian or should I just leave it [16:58] the guidelines themselves? [16:58] one presumes debian package maintainers all read the patches they receive and edit if necessary [16:59] also, not much actulaly depends on having valid dep3 headers [16:59] assuming not, I'd just reply to the bug and point it out (if it's not archived) [17:01] Ok, I'll add a reply to the bug [17:13] \o/ DD replies back with thanks and he fixed it in git :-) [17:19] sweet === korn_ is now known as c_korn === ximion1 is now known as ximion === ximion1 is now known as ximion === yofel_ is now known as yofel === ximion is now known as ximion1 === hannesw_ is now known as hannesw