=== thomi is now known as thomi|lunch === nesthib` is now known as nesthib === thomi|lunch is now known as thomi === tasdomas_afk is now known as tasdomas [08:32] hi folks [08:33] I'm getting some builds failure on my PPA, which I can't reproduce locally: [08:33] https://launchpadlibrarian.net/145214967/buildlog_ubuntu-precise-amd64.stockfish_3.0.0%2Bgit20130508-2pmjdebruijn1~precise_FAILEDTOBUILD.txt.gz [08:33] it's basically a backported package, with no real changes... so this probably builds fine on the Debian build farm as well [13:17] pmjdebru1jn: is the part where it fails, trying to connect to external network sites? [13:17] I don't think so [13:18] at least I have no reason to think that [13:18] I'd have to take a closer look locally of course [13:18] from what I can tell [13:18] it's an optimization step [13:18] where code is executed and benchmarked [13:18] to determine compiler options [13:18] (which I guess may not be the best idea for package build anyhow) [13:19] well, whatever it is doing, is hanging [13:26] so it's killed for inactivity? [13:27] yes [13:28] I'll have a closer look then [13:28] thanks [13:33] I need some help on versioning [13:34] Upstream has development versions on odd-numbered versions and stable versions on even-numbered versions [13:34] can you give concrete examples [13:34] Flightgear/Simgear/fgfs-base [13:34] I mean with version numbers [13:35] and why would odd/even versioning be a problem for you? [13:35] 2.11 is development version, and 2.12 is stable (well, to be released, version) [13:35] (typically that's type convenient) [13:35] it's not the odd/even thing [13:35] ok, what's the issue then:) [13:35] s/type/quite/ [13:35] :) [13:36] when a stable version is about to be released, they branch off from the trunk, create the 2.12 branch, and update the versioning in the application itself to be 2.12, but it's a prerelease [13:36] sort of like beta or rc [13:36] there aren't official idenitifiers except for the git revision [13:36] that's a process problem, not a version problem exactly [13:37] but hopefully they also bump the trunk version at the same time [13:37] trunk gets bumped up to next development version [13:38] well [13:38] you can use ~ [13:38] so what's the problem? [13:38] my idea was to use something like 2.12.0~