Finally…
… after the 10th iteration it built. Go and grab notify-osd - 0.9.14-0ubuntu1~ppa10 here.
I got a lot of feedback and help-advise from people over the last two days. Huge thanks for that! I tried it all, but what only worked in the end for me was this:
- (fix the autotools problems, thanks again njpatel)
- (verify they work locally)
- (commit those to notify-osd trunk)
- bzr branch lp:~ubuntu-desktop/notify-osd/ubuntu
- bzr branch lp:notify-osd
- cd ubuntu
- bzr merge ../notify-osd
- bzr commit
- autoreconf
- ./autogen.sh
- dch -i
- dpkg-buildpackage -S -sa
- cd ..
- dput my-ppa notify-osd_0.9.14-0ubuntu1~ppa10_source.changes
Also I had to get pbuilder up and running again to speed up those iteration cycles. That also took some time, to remember its usage and research the web for hints how to make best use of it.
- pbuilder –create –distribution karmic (this takes ages)
- sudo pbuilder –build notify-osd_0.9.14-0ubuntu1~ppa10.dsc
I think I should rename /var/cache/pbuilder/base.tgz to /var/cache/pbuilder/base-karmic.tgz and symlink it to base.tgz. Because in the future I will probably forget to do:
- sudo pbuilder –login
- (in the created chroot environment)
- lsb_release -a
… to figure out what pbuilder distro-environment I’m I have. Then I also should remember this before using pbuilder again, to be on the save side:
- sudo pbuilder –update
… and not be surprised if stuff which builds locally, will not build on the PPA-buildservers. Hm… that killed the symlink of course *sigh*.
My productivity goes out the window, when I have to do a release. Initially I assumed a realease means testing trunk, giving it a tag in bzr, creating tarballs with “make dist” and uploading them to launchpad. Then you get a “Just upload it to a PPA”. Well that little sentence turned out to be 2 days of overtime work. I wish I was a bit more like seb128, mvo or pitti, so “Just upload it to a PPA” really is just work for 30 minutes or so.
June 21st, 2009 at 11:50 am
You Linux developers really have it hard. On Windows I just hit the F5 key. Welcome to 1990!
June 21st, 2009 at 12:06 pm
Spare us your mendacious pity, please! I’m not talking about local compilation of a program. This is software-release managment. I’ve talked about getting software into the hands of interested users and/or testers, so they don’t have to go through that process. Going through this in the end gives me a deployed program/packages that runs on netbooks, desktops, laptops on numerous architectures (x86, amd64, lpia, sparc, powerpc etc.) But still thanks for stopping by and telling me how awesome the Window platform is.
June 21st, 2009 at 2:09 pm
I see you’re a little short on patience right now, but “mendacious pity” is a little bit harsh.
It’s more likely to be just simple ignorance.
Regards, Rob
June 21st, 2009 at 4:15 pm
Hey, thanks for going through all the trouble. I really appreciate the effort that you and others put in to pushing software out to whiners like me
Cheers!
June 21st, 2009 at 4:32 pm
@MacSlow: Oh, so I should have mentioned copying of the executable as well. It runs on all distributions of Windows, too!
June 21st, 2009 at 5:01 pm
Love your changelog:
notify-osd (0.9.14-0ubuntu1~ppa10) karmic; urgency=low
* test the shit again
June 21st, 2009 at 5:03 pm
Hey, MacSlow,
look into using pbuilder-dist in ubuntu-dev-tools. It’ll help you avoid the pbuilder-multiple-distribution-confusion thing:
http://manpages.ubuntu.com/manpages/karmic/en/man1/pbuilder-dist.1.html
(Also, your comment form is very difficult to use, here. If you get the captcha wrong, it clears the form, and seems to arbitrarily display a second “Submit Comment” button, above the captcha form…)
June 22nd, 2009 at 11:18 pm
@Mac’s Paine: Sure, hooray for static linking… not!