[11:45] how long since I run a dput to upload a source.changes to a PPA until I see some indication in launchpad.net that it's going to build it? [11:45] hey hey, btw === JanC is now known as Guest83568 === JanC_ is now known as JanC [16:35] aleksander0m: minutes at most; but also see https://help.launchpad.net/Packaging/UploadErrors#The_upload_appears_to_work_but_I_don.27t_get_any_email_about_it [19:08] cjwatson, ok, so something went wrong because after some hours it's not there and also I didn't get any email back [19:17] cjwatson, ah, there, I used the wrong key to sign [21:26] So we have a package that we're trying to build from git master, but since git commit hashes are "random", we're seeing random upload fails because Debian is confused and doesn't understand version numbers. [21:26] see e.g. https://code.launchpad.net/~endlessm/+archive/ubuntu/soma/+recipebuild/1147426 [21:26] INFO Upload was rejected: [21:26] INFO eos-shard_1.3-1~39d5065~ubuntu15.10.1.dsc: Version older than that in the archive. 1.3-1~39d5065~ubuntu15.10.1 <= 1.3-1~e8e22bd~ubuntu15.10.1 [21:26] How can we fix this so that we have packages built from git? [21:40] "because Debian is confused and doesn't understand version numbers" is hardly a valid assessment [21:42] You might consider a version string incorporating `git describe`, which includes a numeric counter for just this sort of case [21:45] Oh, you're talking about recipe builds [21:45] https://help.launchpad.net/Packaging/SourceBuilds/Recipes then [21:49] Thanks, I'll look at it. [21:50] It is confusing and sometimes frustrating when stuff like this comes up. [23:03] Jasper: git doesn't understand version numbers. commit hashes are not version numbers. [23:04] Jasper: use the bzr revno, or use a datestamp