=== dk is now known as Guest9738
=== yofel_ is now known as yofel
[21:24] <thinkndev> guys, I've been running through the "package a new software" on the packaging guide.  I've managed to build the hello world deb file, and I ran lintian.
[21:25] <thinkndev> After making the fix, I wanted to run debuild -nc after cd-ing to hello/debian
[21:27] <thinkndev> and the cmdline fails to run debsign, meaning the debuild probably wasn't successful.  How do I debuild so that the fixes are committed?
[21:28] <jtaylor> if it tries to run debsign the build was successful
[21:28] <thinkndev> ah really?
[21:28] <jtaylor> what is the error message?
[21:30] <AmberJ> thinkndev, try 'debuild -nc -us -uc'
[21:30] <thinkndev> AmberJ, wouldn't that be debuilding from scratch?
[21:30] <thinkndev> but I think that'll work
[21:31] <AmberJ> The wiki article says 'debuild -us -uc' (the first time you run it)....  -us -uc means "do NOT sign packages".
[21:32] <thinkndev> ok
[21:32] <AmberJ> Then wiki page says to run "debuild -nc" second time (mind you, this time -us -uc are missing; so it prompts you that debsign failed)
[21:32] <AmberJ> -nc means "no clean" (iirc)
[21:32] <Laney> which page is this?
[21:33] <AmberJ> Laney, http://developer.ubuntu.com/packaging/html/packaging-new-software.html
[21:33] <thinkndev> ahh, following AmberJ's suggestion, no error message came out!
[21:34] <thinkndev> there is a slight logic error on the packaging guide after all.
[21:35] <AmberJ> I think http://developer.ubuntu.com/packaging/html/packaging-new-software.html#next-steps should say "debuild -nc -us -uc" (instead of "debuild -nc")
[21:35] <thinkndev> that's what I was thinking too.
[21:37] <thinkndev> jtaylor, the error messag was: running debsign failed.  it's probably because of the missing "-us -uc" for the debuild command.
[21:38] <jtaylor> thinkndev: no, debsign probably failed for a different reason (no key?) -us -uc just disables running it
[21:38] <Laney> http://developer.ubuntu.com/packaging/html/getting-set-up.html#create-your-gpg-key
[21:38] <jtaylor> but you don't need debsign unless you want to upload it
[21:38] <thinkndev> lol, yeah. the package page is but a tutorial.
[21:39] <thinkndev> I have a gpg key.
[21:39] <Laney> you need it if, for example, you want to upload to a ppa
[21:44] <Laney> https://code.launchpad.net/~laney/ubuntu-packaging-guide/new-software-no-sign/+merge/113834
[21:46] <thinkndev> can we manually edit the control file?
[21:47] <jtaylor> yes
[21:47] <jtaylor> everything in debian after a clean should be editable
[21:48] <Laney> in most cases you /must/ edit control
[21:48] <jtaylor> except maybe for old changelog entries, always add new ones there
[21:49] <thinkndev> why is it necessary to edit the Makefiles when ./configure won't do?
[21:49] <thinkndev> and how difficult is it for starters?
[21:49] <jtaylor> in general you won't have to edit makefiles often, only if they do not behave correctly
[21:51] <jtaylor> the makefiles are usually part of the application you are packaging, if there are issues you should ask the application writers for advice
[21:51] <thinkndev> awesome
[21:51] <jtaylor> debian/rules is a makefile, but with the packaging tools its very easy to use nowadays
=== em is now known as ninkasi
[21:54] <thinkndev> If lintian doesn't say anything about a .deb package, it means there aren't any errors it can find?
[21:55] <jtaylor> yes, but lintian is not perfect
[21:55] <Laney> you can activate more checks
=== ninkasi is now known as em
[21:56] <Laney> --pedantic --display-info --display-experimental
[21:58] <thinkndev> Ok, now that the package is ready, I need to see if this builds on a clean environment.  I wrote "bzr builddeb -S" only to receive "ERROR: Not a branch: home/<usr_name>"
[21:59] <jtaylor> you need to run that in a bzr checkout
[22:00] <thinkndev> what is a bzr checkout? and how do you run in it?  It seems that my home directory isn't a checkout
[22:00] <thinkndev> http://developer.ubuntu.com/packaging/html/packaging-new-software.html
[22:01] <jtaylor> ok with that guide you should have it all in bzr
[22:01] <jtaylor> you need to be in the package directory for that command to work
[22:02] <thinkndev> I'll make a note of that.
[22:03] <Laney> why does the guide mix debuild and bzr builddeb
[22:03] <Laney> ._.
[22:04] <jtaylor> yes, very confusing
[22:04] <thinkndev> precisely why I'm thrown off at this point in the guide
[22:04] <thinkndev> everything else flowed well.
[22:05] <Laney> so where it has "debuild" it should have "bzr bd --" imho
[22:05] <thinkndev> Laney, can you report this as a bug to package guide?
[22:06] <Laney> i'll just fix it
[22:06] <thinkndev> ahha, ok.
[22:07] <thinkndev> so with a complete hello .deb package ready, what must I do to prepare to run it in a chroot environment?
[22:09] <Laney> https://code.launchpad.net/~laney/ubuntu-packaging-guide/new-package-no-debuild/+merge/113835
[22:09] <Laney> to run it? log into the chroot and install the deb therein
[23:29] <thinkndev> guys, what does it mean if there are "items in queue"?
[23:29] <jtaylor> context?