[22:37] can anyone enable arm for this ppa? https://answers.launchpad.net/launchpad/+question/273048 [22:38] sergio-br2: Done. [22:39] thanks [23:41] Noob question: Happy to RTFM if I could find it. Have launchpad mirroring github, separate bzr debian repo. Daily builds not autobuilding without a manual update of changelog in bzr debian repo. ANy way to automate this? [23:43] Dev manages github, I maintain launchpad and bzr debian. Is there something dev needs to do at github end to make it work? [23:46] Now searching answers.launchpad, which I'd never seen until the header p[rovided here. [23:50] caraka: Can you link to the recipe? [23:51] https://code.launchpad.net/~caraka/+recipe/gridcoin-daily [23:51] Thanks [23:52] caraka: https://code.launchpad.net/~gridcoin/+archive/ubuntu/gridcoin-daily/+recipebuild/1005659 [23:52] If you look at the upload log you'll see the problem. [23:52] INFO File gridcoinresearch_3.5.1.7-r162~ubuntu14.04.1.tar.gz already exists in gridcoin-daily, but uploaded version has different contents. See more information about this error in https://help.launchpad.net/Packaging/UploadErrors. [23:52] From your recipe: [23:52] # bzr-builder format 0.3 deb-version {debupstream}-r{revno:packaging} [23:53] So the recipe build will build a version string from the latest upstream version in debian/changelog, plus the revno of the packaging branch. [23:53] That will break if the upstream branch (lp:gridcoin) changes without the packaging branch also changing -- the version number won't change. [23:54] makes sense [23:54] You probably want a version template something like {debupstream}+r{revno}-0ppa1+r{revno:packaging} [23:54] The r{revno} being the important bit here. [23:54] and as there is no changelog in the upstream (github), this cause the error? [23:55] Well, sort of. [23:55] Even if the upstream repo did have debian/changelog, it would still fail to upload unless they changed the upstream version in the changelog on every commit. [23:56] Ok, I'm not entirely clear how this syntax change will fix it, but I'm more than happy to give it a go [23:56] The thing to remember is that package versions must be unique, so any change to one of the components of the package must change the version. And your current version template doesn't include anything about lp:gridcoin, so it will cause a conflict whenever lp:gridcoin changes. [23:56] Ahh. [23:56] Adding "r{revno}" to the template includes the revno of lp:gridcoin, fixing the issue. [23:57] bingo. I think I'm following tyou now [23:57] so currently, the {debupstream} is an empty thing, i.e.not cvoming from github as Ii presumed [23:58] as I presumed [23:58] {debupstream} is replaced with the upstream version (everything before the last "-") in debian/changelog. [23:58] Which will be from the packaging branch in this case. [23:59] very good. Where can I read up on this syntax, so I learn this rather than ape your good advice? [23:59] best time to study is when prob solving