[00:00] if a bug in a build depend that causes a FTBFS is fixed, how is a retry for building triggered? (https://launchpad.net/ubuntu/jaunty/+source/lazarus/0.9.26-2) [00:01] just by cron? new upload? manual triggering? [00:03] Elbrus: MOTUs or core-devs can retry builds, depending on the component [00:04] hello Elbrus [00:04] Elbrus: when fpc is built and published everywhere I will retry that [00:06] james_w: ok, thanks [00:06] Laney: thanks for the explanation, I expected so much. [00:07] james_w: could you also retry building winff after lazarus is built? [00:08] Elbrus: sure [00:10] james_w: thanks, that's my first packaging effort in debian. Would really like to see it work in Ubuntu (although I will propose some Ubuntu related changes after it builds) [00:39] hi i was going to merge drscheme but the package is a dummy package (my terminology) all it does is install plt-scheme [00:41] serialorder: ok, do you have a more specific question? [00:41] i was thinking that rather than merging this it would make more sense to modify plt-scheme and add a Provides: drscheme rather than actually keeping this package [00:42] hi serialorder. a dummy packages is slightly different to a Provides: so it might be that way for a reason [00:43] serialorder: I think you'd want a transitional bin:drscheme package generated from src:plt-scheme that provides an upgrade path [00:43] One is that it is possible to Build-Depend on a dummy package. The other is that it allows you to transition users from one to the other [00:43] as crimsun says though, it doesn't have to be a whole separate source packge [00:43] diverging from Debian on this might be more effort than it is worth though [00:45] ok [00:45] thought I would ask since literally all this package has is a debian directory [00:55] would someone mind taking a look at this bug to verify if what I suggest makes sense or not [00:55] https://bugs.launchpad.net/ubuntu/+source/imagemagick/+bug/301618 [00:55] Ubuntu bug 301618 in imagemagick "imagemagick merged from Debian experimental has broken packaging" [High,Triaged] [00:55] it probably doesn't though =( [00:57] serialorder: I think that'd be one aspect of it, but also every package the build-dep on the old -dev package would have to be changed to build-dep on the appropriate new package. [00:58] So I'd say it makes sense, but is not complete. [00:58] so there is no way to make it so that it wouldn't break the other packages [00:59] that makes sense [00:59] man that sucks [01:19] anyone know how to make my software copy itself to a directory on deb install? [01:27] what a long, long, painful, and excruciating task I am undertaking :) [01:27] making an initial attempt at documenting debian/copyright if using bundled media stack from HandBrake [01:40] Hi. Has someone time to review dvdstyler (http://revu.ubuntuwire.com/details.py?package=dvdstyler)? Thanks in advance! [02:14] DktrKranz: I see you just uploaded uiflite. [02:14] DktrKranz: I hadn't noticed that until after I gave it a review. [02:14] ScottK-laptop, yes. just now [02:15] DktrKranz: Since the packaging is under the GPL, debian/copyright needs to point to GPL. [02:15] I was about to comment to that effect when I saw your comment. [02:16] DktrKranz: Would you please fix that and upload and -0ubuntu2? [02:16] I added it before upload [02:16] DktrKranz: Excellent. [02:16] Nevermind then. [02:16] * DktrKranz checks [02:18] * ScottK-laptop looks at iptux [02:19] ScottK-laptop, no. I noticed it but I forgot to actually put it. I'll reupload it with the fixed debian/copyright (no need to do -0ubuntu2, IIRC it's legal to have two NEW packages with the same versioning, given that the former is rejected properly) [02:21] DktrKranz: Great. I've seen the wrong one get rejected before. I think it's safer to make it ubuntu2, but up to you. [02:21] "HandBrake also includes the ffmpeg project. It is under a metric fsckton of licenses. Go RTFM to figure out the authors and licensing terms" [02:21] ^H^H^H^H^H^H^H^H^H^H^H [02:24] If a program doesn't link to libfoo, does libfoo-dev need to be in build-depends? [02:27] ryanakca: it shouldn't [02:28] james_w: *nod*, thanks [02:30] Hobbsee, StevenK, I just reuploaded uiflite 2.2.1-0ubuntu1 to Jaunty NEW, mind rejecting the older one? Thanks. === fabrice_sp_ is now known as fabrice_sp === woody86_ is now known as woody86 [03:37] has anyone seen http://translate.sourceforge.net/doc/api/ packaged anywhere? [04:10] Hello, i'm moving http://revu.ubuntuwire.com/details.py?package=mbpurple to cdbs [04:11] but the build always failed because the options from makefile.mk is not complete [04:52] ok, I found the solution. please review my package on http://revu.ubuntuwire.com/details.py?package=mbpurple [05:39] ha VICTORY, pwned the handbrake auto-fetcher. [05:39] at the same time, I award myself the nastiest repack of the year award. [06:14] (gone) [06:19] Hobbsee: Really? === RAOF_ is now known as RAOF [06:19] RAOF: well, the one to be rejected is [06:20] RAOF: I was looking for you, actually. How can I tell gnome-do that i want to connect to a machine via ssh console by default, not open it's root by ssh? [06:27] Um... [06:28] So, I presume Do is offering to open it's root by SSH because you've got a GNOME bookmark/mount set up. [06:28] Do you have the SSH plugin loaded for Do, and have a .ssh/config file which defines the host? [06:28] Hobbsee: ^^ [06:29] RAOF: it's in .ssh/config [06:29] and the latter, yes [06:29] help review http://revu.ubuntuwire.com/details.py?package=iptux, a new version uploaded(fix copyright information), thanks. [06:32] Hobbsee: Then after selecting the host in the first pane, you want to tab over and select "Connect with SSH" in the second pane. [06:32] After doing that a number of times, the relevance engine will pick it up and it'll become the default action. [06:32] ah [06:32] for each ssh host, or? [06:32] For all SSH hosts, yes. [06:33] The relevance engine isn't quite cool enough to do per-item action relevance at this point, I think. [06:33] no, as in, do i need to do it a number of times for each ssh host, or it's a global count? [06:33] ah, right. [06:34] hurrah! [06:34] That fixed it, thanks! [06:34] Do becomes much more useful once you know how to use it. [06:35] We obviously need to make it easier to discover _how_ to use it :) [06:37] well, i thought it might have been something like that. [06:37] as that's how the t9 dictionary handles [06:37] but i'm surethat wasn't 10 times [06:38] and because repeatedly switching it every once in a while wasn't seeming to do it - i presume it needs to be in the same session? [06:38] It _should_ be remembered across sessions. [06:39] * Hobbsee thought she would have used gnome-do more than 10 times for ssh, connecting to it [06:39] * Hobbsee hasn't managed to trigger it, without consciously launching 10 versions of it [06:41] I find it won't remember "Connect with SSH" as the default [06:42] I always have to go "ant" "ssh" [06:42] *shudder* how beautiful. [06:42] Possibly because you also "open" stuff a lot? The relevance isn't per-item, and the SSH hosts I think are one of the worst-case behaviours. [06:43] RAOF: i don't, though. [06:43] did you know when you statically link something against ffmpeg, faac, faad, libmp4v2, mpeg4ip, and dca, that the resulting binary is 9.3MB? [06:43] the more you know! [06:43] help review http://revu.ubuntuwire.com/details.py?package=iptux, a new version uploaded(fix copyright information), thanks. [06:43] RAOF: But I don't [06:43] RAOF: I use Do to run things and connect via ssh [06:45] Then maybe there's a bug somewhere. You're right, I need to "off" "ssh", too. [07:04] help review http://revu.ubuntuwire.com/details.py?package=iptux, a new version uploaded(fix copyright information), thanks. [07:05] lidaobing: You're probably pinging a little bit too frequently; it's unlikely to help. [07:05] woah. do you *really* need to try every 5 lines? [07:06] RAOF, 20 minutes one time, maybe too frequently, I will waiting for more time from now. [07:06] Hi. A merge request with debdiff should be in Confirmed or New when subscribing u-s-u ? [07:07] (it's for bug #285674) [07:07] Launchpad bug 285674 in hugin "[Merge request]Please merge Hugin 0.7.0-1 from Debian Experimental" [Wishlist,New] https://launchpad.net/bugs/285674 [07:07] fabrice_sp: either, afaik. [07:07] Hobbsee: ok. And sync request also? [07:07] fabrice_sp: confirmed. [07:07] fabrice_sp: requestsync --help is quite useful, FYI [07:08] ok. Could I update the wiki page with that information? https://wiki.ubuntu.com/SyncRequestProcess [07:08] Hobbsee: thanks. Will check! :-) [07:08] Right. Mono 2.0 transition for GNOME Do + Plugins done. Let's see if I can't wrangle a dkms package out of nouveau's kernel modules. [07:08] hmmm. it does the sponsorship automatically now. Cool! [07:10] fabrice_sp: er, I lie [07:10] fabrice_sp: and that requestsync needs an update, on that page. [07:11] fabrice_sp: not sure on merges, i don't think i'ts specified, but if you need sponsorship for hte sync, it gets set as new (as the sponsor confirms it, then the archive person closes it) [07:12] Hobbsee: ok. So the best thing is to let it as new. I was just wondering if having a debdiff would needs a special status or not. [07:13] fabrice_sp: Not that I know of. [07:13] fabrice_sp: a debdiff counts as a patch, so tick "this is a patch" button [07:13] but apart from that, no, afaik. [07:14] Hobbsee: ok. Will check I marked it as patch then. Thank you! [07:14] fabrice_sp: you're welcome! [08:00] hi everyone [08:05] gralco: hi [08:06] Hey gralco, slytherin. [08:07] iulian: hi [08:14] Well, that's pretty easy. [08:15] Urgh. Almost. [08:19] I (almost) win! [09:07] good meuning [11:55] hi [11:56] hi [12:08] please review http://revu.ubuntuwire.com/details.py?package=mbpurple === nenolod is now known as moogle [12:26] willwill: typo in debian/control. it should read "it only supports" instead of "it only support" [12:26] willwill: does the debhelper level need to be so higH? (7) [12:26] laga: thank you, I copied that from upstream [12:27] laga: I don't use debhelper on my latest upload [12:27] willwill: is debian/compat needed then? [12:28] i'm not sure about that, i'm not a MOTU [12:28] i wonder if you need to have the real names of the upstream authors. i don't know what the policy says about that [12:30] laga: I also have dpkg-genchanges: failure: cannot read files list file: No such file or directory error in pbuilder [12:31] whs: and you're telling me this because...? [12:31] laga: I need help to fix tht [12:33] whs: it's better to ask everyone in the room, not just a specific person. you should also provide more information, eg what package you're trying to build and more log files (in a pastebin) [12:34] sorry === whs is now known as willwill [12:35] my pbuilder log: http://pastebin.com/m62c06897 [12:48] How do I apply all patches of a package but without building it, so that I can create another patch? [12:50] Pupeno: Depends on the patch system in use [12:50] Ok, I have reuploaded: http://revu.ubuntuwire.com/details.py?package=mbpurple [12:54] willwill: debian/rules patch seems to work. [12:54] on http://revu.ubuntuwire.com/ near the dsss package there si a package(+) icon, what does it mean? [12:55] if i click it shows revu error [12:55] http://paste.ubuntu.com/78028/ [12:56] willwill: your rules file looks wrong / weird? See https://help.ubuntu.com/ubuntu/packagingguide/C/basic-cdbs.html ? [12:56] Hobbsee: upstream does not use autotools [12:57] ah [12:57] willwill: Just because they don't use autotools doesn't make CDBS unsuitable [12:58] StevenK: my latest upload uses makefile class from cdbs [13:03] help review http://revu.ubuntuwire.com/details.py?package=iptux, a new version uploaded(fix copyright information), thanks. [13:05] hi, i've two binaries that shares the sahttp://www.google.com/search?q=http%3A%2F%2Fgdcgnu.sourceforge.net%2FSOURCES%2F&ie=UTF-8&oe=UTF-8me manpage. should i do a link [13:05] oops [13:05] sorr [13:05] sooory === gouki_ is now known as gouki [13:41] how can i check is my gnupg key is enabled to upload on revu? [13:42] *if my [13:45] goshawk: Is your key on Launchpad? [13:50] yes [13:50] nhandler: i upload on ppa [13:50] and it works [13:50] but i uploaded on revu [13:51] yesterday [13:51] goshawk: Have you logged into REVU yet? [13:51] and i don't see the update of my package [13:51] no [13:51] wait [13:51] i'll login [13:51] The GPG keys are synced when you login. So if you haven't logged in yet, REVU will NOT have your key, and will reject uploads from you [13:52] nhandler: yep, i dind't login [13:52] from when i changed the key [13:52] :) [13:53] yes it's there now [13:53] thanks nhandler [13:53] :) [13:53] You're welcome goshawk [13:59] Hello there. When I try to SVN update with RapidSVN, I am asked for my RSA key password. How can I ommit this? [14:00] Actually, I am asked for my login password. I text input box says: Enter your login password to unlocl default keyring. The default keyring was not unlocked at login so you must unlock it now. [14:01] And it waits for my login password. I don't want to do that every time. How can I disable it? [14:01] * A text input box [14:01] * to unlock the [14:04] So, any help, please? [14:19] DktrKranz : i've update my package that you had previously advocated....i correct the .desktop file ;) ( http://revu.ubuntuwire.com/details.py?package=sqliteman ) [14:24] Test for demo purpose at ubuntu-party: bug 303404 [14:24] Launchpad bug 303404 in rhythmbox "last.fm: selecting multiple songs produces a download error" [Undecided,Confirmed] https://launchpad.net/bugs/303404 [14:25] ubottu: thank you [14:25] You're welcome! But keep in mind I'm just a bot ;-) === Knightlust is now known as Igorot [14:42] i've a binary that uses the same manpage of another binary [14:42] how can i make an ln -s using cdbs? [14:43] ln -s $(DESTDIR)/usr/share/man/man1/drebuild.1 drerun.1 [14:43] if i do something like this during install:: [14:43] it gives error [14:43] cuz /usr/share/man doesn't exist yet [14:44] it might work better in binary-post-install/package:: [14:45] but $(DESTDIR)/usr/ probably doesn't exist [14:45] um no, it will, sorry [14:46] goshawk: im not an expert but.... what if you do ln -s $(DESTDIR)/usr/share/man/man1/drebuild.1 $(DESDIR)/usr/share/man/man1/drerun.1 ? [14:46] ok [14:46] eMerzh: i chrooted on it [14:47] /usr/share does not exist [14:47] james_w: following your words [14:47] did you switch to the other target? [15:08] Hi. Could anyone please review new app request? Bug #281982 [15:08] Launchpad bug 281982 in ubuntu "[needs-packaging] ipwatchd" [Undecided,New] https://launchpad.net/bugs/281982 [15:10] jariq: your best bet is to submit the package to REVU. There are weekly reviewing sessions, and if you go on IRC that day, you are likely to succeed [15:10] !revu [15:10] REVU is a web-based tool to give people who have worked on Ubuntu packages a chance to "put their packages out there" for other people to look at and comment on in a structured manner. See https://wiki.ubuntu.com/MOTU/Packages/REVU [15:11] actually i am looking for someone who could be able to create package [15:11] jariq: Ah :-) [15:11] that could be submited to revu [15:12] jariq: don't you want to get your feet wet? [15:13] i tried to create package by myself but it was very time consuming [15:13] jariq: in practice, the only way is to do it yourself. [15:13] jariq: just come here and ask [15:13] jariq: it _is_ time consuming [15:14] but not for anyone experienced right? [15:14] jariq: the trick is to become experienced [15:14] jariq: to be honest, to get help, you have to show that you are willing to do work yourself [15:15] i wrote that app :) [15:15] jariq: cool [15:15] i did my job [15:15] jariq: not quite :-) [15:15] jariq: what is your problem [15:15] and i am looking for someone who could create a package [15:15] with packaging I mean :-) [15:16] jariq: is it the tools? [15:16] i tried few times [15:16] jariq: the debian/ dir? [15:16] but as i wrote earlier it is very time consuming [15:16] jariq: It will take you an hour or so [15:17] i spent about six hours without any effect [15:17] jariq: what did you do? [15:17] read manual :) [15:17] jariq: Ah, ok. So now you are ready to do the work [15:18] jariq: basically, you need a debian/ dir with 5 files in it [15:18] i do not feel that way [15:18] jariq: Let me give you a hint: that is not the right attitude here [15:18] ok go on [15:19] jariq: you have a tar ball with your app ? [15:19] yes [15:19] jariq: unpack it somewhere in a work directory [15:20] got it [15:20] jariq: you have a Makefile or autotools system? [15:20] Makefile [15:21] jariq: Fine. cd to the top level of your app [15:21] jariq: mkdir debian [15:22] got it [15:22] jariq: cd debian [15:23] jariq: this is where you need to work to create the package [15:23] ok [15:23] jariq: first we make the rules file [15:24] jariq: 2 secs [15:24] is there any example file or should i create empty one? [15:24] jariq: let's create an empty one [15:26] jariq: first line of rules: [15:26] #!/usr/bin/make -f [15:26] 2nd line: [15:27] include /usr/share/cdbs/1/rules/debhelper.mk [15:27] 3rd and last: [15:27] include /usr/share/cdbs/1/class/makefile.mk [15:28] jariq: got that? [15:29] yes [15:29] jariq: what is the copyright of your package? [15:29] but file /usr/share/cdbs/1/class/makefile.mk does not exist on my hdd [15:29] i installed debhelper package [15:30] is there anything else i need to install ? [15:30] jariq: ah yes. apt-get install cdbs [15:30] debhelper [15:30] ok got it [15:30] license is gnu gpl v2 [15:30] jariq: what is the copyright of your package? [15:33] ah ok good [15:33] jariq: now we make the copyright file, in debian/ still [15:34] 1st line [15:34] Format-Specification: http://wiki.debian.org/Proposals/CopyrightFormat [15:34] 2nd line [15:35] Upstream-Name: IPwatchD [15:35] 3rd line [15:35] Upstream-Maintainer: (you) [15:36] 4: [15:36] Upstream-Source: (url of where to get your tarball) [15:36] got that? [15:36] yes [15:36] that was the header section of debian/copyright [15:37] ok [15:37] jariq: now comes as many Files: sections as is necessary to fully describe the copyright of all files. I think this might be sufficient: [15:37] Files: * [15:38] Copyright: Copyright 2008, (your-name) [15:38] License: GPL [15:39] should i put blank line between header and this text ? [15:39] Yeah why not [15:39] jariq: so, you should have 3 lines for the Files: section [15:39] if someone has free time, can please have a look at: http://revu.ubuntuwire.com/details.py?package=dsss [15:40] ? [15:40] thanks [15:40] so anything else is needed in this file? [15:41] jariq: after the License: GPL line, you need the short GPL clause, see here: http://pastebin.com/f798b947d [15:41] jariq: and that finishes the copyright line [15:43] jariq: got that? [15:43] yeas [15:43] jariq: ready to go on? [15:43] yeap [15:43] next file: compat. [15:44] jariq: echo 6 > compat [15:44] that's it [15:44] jariq: 2 files to go [15:44] goshawk: please don't update the chagelog every upload [15:45] goshawk: it should ONLY state the launchpad "needs-packaging"-bug and the patches you do (if present) [15:45] jariq: now we will create the changelog file [15:45] handschuh: sorry i didn't know [15:45] jariq: which is used to collect the history of your package [15:46] jariq: it has a strict format [15:46] ok [15:46] 1st line: [15:46] handschuh: ok i'll do it [15:46] goshawk: no problem, as you have patches, make sure you explain them in the changelog [15:46] yes i've 2 patches [15:46] so i should add them on changelog [15:46] jariq: ah, what is the version of ipwatchip [15:47] 1.1.1 [15:47] ok [15:47] first line [15:47] goshawk: yes. also take a look at http://revu.ubuntuwire.com/report.py/legal?upid=4145 [15:47] ipwatchd (1.1.1-0buntu1) jaunty; urgency=low [15:48] jariq: next line empty [15:48] ok [15:48] jariq: 3rd line [15:49] * First packaged (LP: #281982) [15:49] handschuh: opening link [15:49] (substitute with a space :-) [15:49] did it [15:49] jariq: next line empty [15:49] jariq: last line: [15:50] -- Jariq Lastname [15:50] handschuh: Digital Mars and Gregor Richards [15:50] handschuh: they are in debian/copyright if i'm not wrong [15:50] jariq: followed by the output of date -R [15:50] s/1.1.1-0buntu1/1.1.1-0ubuntu1/g [15:51] I need help with something.... My package needs the user to give it the mysql root password. But I don't know how to make my package ask for that during install. Can someone help? [15:51] goshawk: yes but there are some files without licensing and the licensing is not recognized [15:51] handschuh: what should i do? [15:51] goshawk: you might have to talk to upstream to let this fix [15:52] jariq: got that? [15:52] yes [15:52] jariq: great. Last file, control [15:52] first line: [15:53] Source: ipwatchd [15:53] handschuh: are you refferring to some files like: http://revu.ubuntuwire.com/report.py/legal?upid=4145 ? [15:53] jariq: [15:53] 2nd line [15:53] wait [15:53] sorru [15:53] Section: utils [15:53] jariq: 3rd [15:54] goshawk: yes [15:54] Priority: optional [15:54] handschuh: /var/revu/revu1-incoming/dsss-0811291639/dsss-0.78/rebuild/nprocs.h: *No copyright* UNKNOWN [15:54] jariq: 4th [15:54] ? [15:54] jariq: Maintainer: Ubuntu MOTU Developers [15:55] jariq: 5th line [15:55] goshawk: some files have no valid license information an this has bo be fixed by upstream [15:55] jariq: XSBC-Original-Maintainer: Jariq Lastname [15:56] jariq: 6th line [15:56] handschuh: ok what else to fix? [15:56] Standards-Version: 3.8.0 [15:56] jariq: next line empty [15:56] jariq: OK that was the header of debian/control [15:56] got it [15:57] goshawk: debian/copyright [15:57] jariq: after that, there are N sections each describing a binary package. I think you just need 1 [15:57] goshawk: change the "ist was downloaded from" url to http://svn.dsource.org/projects/dsss/downloads [15:57] mok0, and where should i specify dependencies? [15:58] handschuh: ok [15:58] jariq: that goes in the header, after a Build-Depends: tag [15:58] jariq: I skipped that for now [15:58] goshawk: debian/control: under the source-section, add a "Homepage" field [15:58] ok no problem [15:58] jariq: but in fact you need to put: [15:59] Build-Depends: cdbs, debhelper (>= 6) [15:59] jariq: and probably more, but that will be an exercise for you :-) [15:59] goshawk: you have some additional files outside of the debian directory which is not allowed [16:00] handschuh: i don't understand, can you give me an example? [16:00] mok0, Build-Depends goes into control file? [16:00] jariq: Yes, in the header section [16:00] goshawk: a, Im sorry, my bad; never mind [16:00] handschuh: :) yes [16:00] mok0, ok put it there and will add all other dependencies later [16:00] handschuh: it happens [16:00] jariq: great [16:00] mok0, what should i put after header section? [16:01] jariq, 1 (or more) empty line [16:01] mok0, ok [16:01] jariq: let's make the last few lines now [16:01] mok0, ok go on [16:01] jariq: Package: ipwatchd [16:01] jariq: Architecture: any [16:02] goshawk: otherwise it looks fine to me ... but it is very likely that someone else finds other issues [16:02] handschuh: ok [16:02] let me fix [16:02] the things you said [16:03] jariq: next line [16:03] jariq: Depends: ${shlibs:Depends} [16:03] jariq: that is shlibs Depends [16:03] mok0, with space? [16:03] jariq: no [16:04] jariq: sorry [16:04] mok0, ok [16:04] jariq: finally, the description [16:05] jariq: Description: simple daemon using libpcap to detect IP conflicts [16:05] mok0, got it [16:05] jariq: The long descriptions follows that, indented by 1 space [16:06] handschuh: thanks [16:06] jariq: I suggest you use the bit from the LP bug [16:06] jariq: 2nd paragraph [16:06] mok0, intended like license in copyright file [16:06] jariq: oh, we forgot something in the header of debian/control [16:06] jariq: exactly [16:07] jariq: Homepage: http://ipwatchd.sourceforge.net/ [16:08] jariq: you are basically done. (Disclaimer: this is a skeleton, you will probably need to modify & expand) [16:08] jariq: now try to build the package [16:09] jariq: cd .. [16:09] handschuh: last thing [16:09] jariq: fakeroot debian/rules build [16:09] handschuh: about the copyright issue [16:09] goshawk: yes ... contact upstream and ask them to fix this [16:10] handschuh: should i advice upstream for every file in http://revu.ubuntuwire.com/report.py/legal?upid=4145 or just the files like: /var/revu/revu1-incoming/dsss-0811291639/dsss-0.78/rebuild/gnuc.c: *No copyright* UNKNOWN ? [16:10] goshawk: the best might be all files, but the No Copyright files are the worst [16:11] mok0, /usr/bin/fakeroot: 166: debian/rules: Permission denied [16:11] jariq: yes, ok, you know what to do? Hint: it needs x mode [16:11] handschuh: can you show how do they should be? [16:11] handschuh: so i can create a patch [16:12] and submit upstream :) [16:12] mok0, just control file or all files in debian folder? [16:12] jariq: actually, only rules [16:12] mok0, yes rules sorry [16:13] goshawk: yes that might be the best [16:13] handschuh: yes, but i don't know how should be look like, can you show me a good written one? [16:13] i've to go [16:13] write here [16:14] and i'll follow your guidelines [16:14] ok [16:14] bye [16:14] goshawk: you can look at the end of the gpl and find a template [16:15] mok0, it ends up wiht debian/rules: 2: include: not found [16:15] debian/rules: 3: include: not found [16:16] jariq: did you install the cdbs package? [16:16] mok0, yes /usr/share/cdbs/1/rules/debhelper.mk and /usr/share/cdbs/1/rules/debhelper.mk exist [16:16] jariq: hmm... [16:16] mok0, maybe these files include some others that are missing [16:17] jariq: yes... maybe [16:18] jariq: on of the files must be /usr/share/cdbs/1/class/makefile.mk [16:18] s/on/on [16:18] s/on/one [16:18] jariq: (you listed the same file twice) [16:18] mok0, my control file has following contents [16:19] #!/usr/bin/make -f [16:19] include /usr/share/cdbs/1/rules/debhelper.mk [16:19] include /usr/share/cdbs/1/class/makefile.mk [16:19] jariq: that's rules, yes? [16:19] mok0, yes [16:20] jariq: you have debhelper installed? [16:21] mok0, debhelper is already the newest version. [16:21] jariq: can you pastebin debian/rules? [16:22] mok0, i had a space before first line, my mistake sorry [16:22] heh [16:23] mok0, now it executed without errors [16:23] jariq: cool [16:23] jariq: is it compiling your program? [16:24] mok0, it already finished [16:24] mok0, without errors [16:24] jariq: :-) [16:24] jarriq, next ste [16:24] step [16:24] fakeroot debian/rules binary [16:25] jariq: (this is "manual" building) [16:25] jariq: step by step [16:25] mok0, finished successfuly with one warning: warning, `debian/ipwatchd/DEBIAN/control' contains user-defined field `Original-Maintainer' [16:25] jariq: yeah it always does that [16:26] mok0, ok what is the next step? [16:26] jariq: it may have generated a package in ../ [16:26] ls ../*deb [16:26] wow === Tweenaks is now known as Treenaks [16:27] mok0, it is there ../ipwatchd_1.1.1-0buntu1_i386.deb [16:27] jariq: you can use "less" to view the contents of the package [16:28] mok0, gr8 but there is one problem [16:29] mok0, package does not contain all files that are installed when I run "make install" on my Makefile [16:29] mok0, maybe I know where the problem is [16:30] mok0, i'll try to rebuild [16:30] jariq: yes I thought so [16:31] jariq: it may have something to do with what your Makefile does [16:32] jariq: the debian build system installs into the debian/tmp directory [16:33] jariq: (a temporary directory) [16:34] jariq: then it moves files from the debian/tmp directory into a package specific directory debian/ipwatchd/usr/... etc [16:34] jariq: and the package is constructed from that [16:35] mok0, about my Makefile, is there anything special (like some Makefile target) that to build the package successfuly ? [16:36] jariq: uhm, I can't remember to tell you the truth... You may need to install into: $(DESTDIR)/usr/bin and so on [16:36] mok0, aha [16:37] mok0, where can i find info about that? [16:37] jariq: let me think [16:37] mok0, because I suspect that my Makefile does not follow some rules [16:37] jariq: probably [16:37] jariq: try the DESTDIR thing. [16:38] mok0, any example? [16:38] jariq: that may be sufficient. People who install from your tarball wont notice, because DESTDIR will not be set [16:38] jariq: install -m 755 ipwatchd $(DESTDIR)/sbin [16:39] jariq: (I guess that is where daemons go, perhaps /usr/sbin) [16:39] mok0, Makefile can be viewed at https://ipwatchd.svn.sourceforge.net/svnroot/ipwatchd/current/src/Makefile [16:40] jariq: ah, yes, it needs a bit of work [16:40] mok0, so for example i should modify "install" target.. line "cp ipwatchd /usr/local/sbin" to "cp ipwatchd $(DESTDIR)/usr/local/sbin" ??? [16:40] jariq: substitute "/usr/local" with "$(prefix) [16:41] jariq: or perhaps $(DESTDIR)$(prefix) [16:42] mok0, ok i am working on it [16:42] jariq: you can set prefix at the top of Makefile [16:42] jariq: it will be overridden by cdbs [16:46] mok0, i modified install target of my Makefile [16:47] mok0, but it did not help, binary files are not included in package [16:48] jariq: can you carry out the fakeroot debian/rules clean step, please? [16:48] mok0, debhelper is using install target or any else? [16:49] jariq: Let's find out [16:49] jdong: I need to ask you stuff about azureus. You there? [16:49] mok0, clean step done successfuly [16:49] jariq: now build again [16:50] jariq: and go into debian/ and see what is there [16:51] mok0, i executed "fakeroot debian/rules build" and just one file was added into debian directory "stamp-makefile-build" [16:52] jariq: ok ,sounds right. Now try the same with fakeroot.... install [16:53] mok0, make: *** No rule to make target `install'. Stop. [16:53] jariq: uhm... hang on [16:54] jariq: try the fakeroot .... etc... binary step [16:55] mok0, same result [16:55] mok0, created package does not contain program files [16:55] jariq: what's in debian/ now? [16:56] mok0, [16:56] mok0, changelog compat control copyright files ipwatchd rules stamp-makefile-build [16:56] jariq: check debian/ipwatchd/ [16:56] jariq: ls -R or something [16:58] mok0, there are some generated files like docs [16:58] jariq: that's a start :-) [16:58] mok0, but none of them is created by my makefile [16:59] mok0, I suggest to recapitulate [16:59] jariq: Let me check something [16:59] jariq: 1 minute [16:59] mok0, ok [17:01] jariq: Perhaps the install target is never called by cdbs [17:01] mok0, it is possible [17:02] jariq: but there's a neat way around it [17:02] mok0, to call it when make without target is called ? [17:02] jariq: where are the compiled files in your directory tree? [17:03] in the same directory where source files [17:03] jariq: We can just copy the files from your tree to the right place in debian/ipwatchd [17:03] mok0, ok i will try that but i suggest short recapitulation [17:03] jariq: ... and that is done in a file called debian/.install [17:03] jariq: ok [17:04] mok0, so i unpack source into lets say /home/jariq/test [17:04] ok [17:04] mok0, than create /home/jariq/test/debian/ with those 5 files [17:05] jariq: yes (but you've done it now :-)) [17:05] mok0, source files does not have to be in /home/jariq/test/src/ ? [17:05] jariq: that's up to the upstream [17:05] (=you in this case) [17:06] mok0, so than i change working directory to /home/jariq/test [17:06] jariq: In fact, all you need is a Makefile that will build the app(s) somehow [17:06] yes [17:06] mok0, and run fakeroot debian/rules build and fakeroot debian/rules binary [17:07] jariq: well, those are the "debugging" steps [17:07] jariq: normally, you just call "debuild" [17:07] mok0, okey but after build and binary there should be whole package ready [17:08] jariq: yes [17:08] jariq: to upload to revu, you need to build a _source_ package [17:08] jariq: and that consists of 3 files [17:09] jariq: but you probably know that [17:09] jariq: let's try making the debian/ipwatchd.install file [17:10] mok0, ok [17:10] jariq: let's just test it first, with only 1 line in it [17:11] jariq: relative to the topdir, where is ipwatchd built? [17:11] jariq: ./ipwatchd perhaps? [17:12] mok0, i executed "fakeroot debian/rules clean" [17:12] fine [17:12] mok0, so what should be next step "fakeroot debian/rules build" ? [17:13] jariq: see question above [17:13] jariq: relative to the topdir, where is ipwatchd built? [17:14] mok0, i am in directory where ipwatchd is built [17:14] jariq: ... which is? [17:14] topdir? [17:14] yes [17:14] jariq: great. Now first line of debian/ipwatchd.install: [17:15] ./ipwatchd /usr/sbin/ [17:15] got it [17:16] jariq: that's it, now try building "binary" and see if ipwatchd makes it into the package [17:17] yes it is there [17:17] jariq: yay [17:17] mok0, i suppose i should add all relevant files to debian/ipwatchd.install [17:17] jariq: now you know what to do :-) [17:17] jariq: exactly. [17:17] jariq: just one hint more [17:18] jariq: .install is a generic install [17:18] jariq: there are some specialized install files as well, for example for manpages [17:18] jariq: they are more intelligent [17:19] jariq: so, try putting your manpage in a new file ipwatchd.manpages [17:19] jariq: in debian of course [17:19] jariq: and the rest in ipwatchd.install [17:19] mok0, ok working on that [17:20] jariq: now you have 7 files in debian/ [17:20] jariq: (I think) [17:21] mok0, ok i'll skip manpages for now [17:21] jariq: ok [17:24] mok0, but using ipwatchd.install is not very flexible [17:24] jariq: what do you mean? [17:24] mok0, i mean u cannot change prefix [17:25] mok0, or it is just relative? [17:25] jariq: you don't need to. It just has to install things in the right place according to Debian policy [17:25] mok0, ok [17:26] mok0, so now after build and binary package is fine [17:26] jariq: congrats [17:26] jariq: before I leave, let's build a source package [17:26] mok0, thanks a lot [17:26] mok0, you've been very helpful [17:26] jariq: my pleasure [17:26] jariq: Use debuild -S -sa to build source package [17:26] mok0, and source package can be submited to revu [17:27] jariq: Yes [17:27] jariq: you use "dput" utility, and send the *_source.changes file [17:27] jariq: which pulls the other files along [17:28] jariq: but you need a copy of your tarball in topdir/.. [17:28] jariq: and you have to name it: ipwatchd_1.1.1.orig.tar.gz [17:29] mok0, well building of source package failed [17:29] jariq: what's the problem? [17:30] dpkg-source: failure: create ipwatchd_1.1.1-0buntu1.dsc: Permission denied [17:30] dpkg-source: building ipwatchd in ipwatchd_1.1.1-0buntu1.dsc [17:30] debuild: fatal error at line 1247: [17:30] dpkg-source -b _work failed [17:31] jariq: you don't have permission to write in .. (?) [17:31] mok0, does this need root privileges ? [17:31] jariq: no [17:31] jariq: only if you are attempting to write in / ;-) [17:31] mok0, my mistake [17:32] mok0, i run it as root before and it cannot overwrite files [17:32] jariq: ah [17:32] jariq: that's why we have the "fakeroot" command === fta_ is now known as fta [17:32] jariq: it fakes root for an ordinary user when building packages [17:32] mok0, it attempts to sing the package [17:33] mok0, i have gpg key but it is protected by pass [17:33] jariq: it should ask you for the pass [17:33] mok0, it did not, showed "gpg: [stdin]: clearsign failed: secret key not available" instead [17:33] jariq: hmm, [17:34] jariq: just to get pass this point for now, try debuild -S -sa -uc -us [17:34] mok0, it looks like it was successful [17:35] jariq: yes, but you wont be able to upload an unsigned package, so you need to work that other problem out [17:35] jariq: let's see what files were created [17:35] jariq: you should have a *.diff.gz file [17:36] jariq: a *dsc file and a *changes file [17:36] mok0, ipwatchd_1.1.1-0buntu1.dsc ipwatchd_1.1.1-0buntu1_source.changes ipwatchd_1.1.1-0buntu1.dsc.asc ipwatchd_1.1.1-0buntu1.tar.gz ipwatchd_1.1.1-0buntu1_source.build [17:36] mok0, these files were created [17:37] * mok0 wonders why you have the ipwatchd_1.1.1-0buntu1.tar.gz file... [17:37] :) [17:37] jariq: you need a ipwatchd_1.1.1.orig.tar.gz [17:38] jariq: which is just a copy of your upstream tarball (the one you unpackged 2 hrs ago) [17:38] mok0, i skipped that warning [17:38] jariq: naughty boy [17:40] jariq: when you have the orig.tar.gz file, cd into topdir and build source package again [17:40] jariq: we need to see a file called ipwatchd_1.1.1-0buntu1.diff.gz [17:44] mok0, i put *orig* file there [17:44] jariq: great [17:44] mok0, and resulting files are ipwatchd_1.1.1-0buntu1.dsc ipwatchd_1.1.1-0buntu1_i386.deb ipwatchd_1.1.1-0buntu1_source.build ipwatchd_1.1.1-0buntu1_source.changes ipwatchd_1.1.1-0buntu1.tar.gz [17:44] so no diff file again [17:45] jariq: you didn't repackage the tarball to contain debian/ did you? [17:45] jariq: because you shouldn't do that [17:46] no [17:46] jariq: what files are listed in .dsc ? [17:47] mok0, dcd87f2d3ee0fadc0a0f0a83476bbce1 58213 ipwatchd_1.1.1-0buntu1.tar.gz [17:47] mok0, i'll fix this later i will change directory structure anyway [17:47] jariq: hmm. please try to rm or mv that tar.gz file. [17:47] mok0, so when i finaly get that diff file [17:48] mok0, that would be a file that should be submitted to revu ? [17:48] jariq: when you get the diff.gz file, check to see that it contains all files in debian/ that you created [17:48] jariq: the "source package" consists of 3 files: the orig.tar.gz, the diff.gz and the .dsc file. [17:49] jariq: all those are described in the _source.changes file, with MD5 sums so that is the file you pass to "dput" [17:51] mok0, ok thanks a lot [17:51] jariq: you're welcome :-) [17:51] mok0, i will try to do my best to get it there [17:51] jariq: I'm sure you will succeed. But, please be patient. [17:52] jariq: come here next friday, that is REVU day and you can ask to have the package reviewed [17:52] mok0, i am sure that all files and other stuff have its reason but this process is too complicated to start [17:52] jariq: I know [17:52] mok0, ok next friday.. whole day? [17:53] jariq: but now might be a good time to read the Ubuntu Packaging Guide... it's a hands on approach [17:53] jariq: yes, in fact it starts UTC-11 and goes on to UTC+12 [17:54] mok0, i read it before but i hope will understand more now :) [17:54] jariq: I think you will [17:54] mok0, one more thing [17:54] mok0, that bug on launchpad should i change it somehow ? assign to me or something [17:55] jariq: yes, that would be a good idea. And set it to "In progress" [17:55] mok0, ok thanks a lot again for your help [17:55] jariq: We referenced that bug in debian/changelog, so when your package gets uploaded, it will be closed automatically [17:56] jariq: good luck with your package! [17:56] jariq: when you become experienced, you can help someone else :-) [17:57] mok0, sure :) if that day comes [17:57] jariq: See you later! [17:57] c ya [18:23] * directhex completes his annual charity good deed [18:26] directhex: removal requests require sponsorship you know? [18:28] james_w, hm, do they? [18:28] yup [18:28] just came across stetic, I'll check it out now [18:28] any more that should be looked over? [18:29] i think that's our only removal. let me check the wiki [18:30] ftpmaster has acted on it already - http://bugs.debian.org/507126 - but pitti suggested I should file a separate ubuntu removal anyway, just to be sure [18:30] sure, there's no great problem with it [18:31] just wanted to make sure you knew [18:31] i'll know for next time :) [19:10] If I need to patch a file controlled by another package, how do I do this??? [19:12] quentusrex, which file? [20:12] hmmm [20:20] directhex: how does this look? http://paste.ubuntu.com/78128/ [20:43] james_w, offhand it looks perfect :) [20:43] james_w, does a test compile agree with my analysis? [20:45] Dear HandBrake buildsys: If a library 35 seconds into the build failed, please don't continue building for 45 minutes and then tell me that. Thanks, bye. [20:46] jdong: hahaha [20:46] btw [20:46] survey of the day [20:46] jdong: and 45 minutes after the library FTBS, you noticed how ccache would have been a good idea [20:47] if a package provides a file which is also provided by dpkg would you just create a conflict field or rename the binary to something else? :P [20:48] SUNWjoejaxx: haha conflict dpkg!!! [20:48] jdong: yes sir! :D [20:48] :P [20:48] jdong, i have a $20k proprietary app with the same problem [20:48] SUNWjoejaxx: I'm in a much nastier dilemma right now. [20:49] handbrake currently pumps out these horrendous 10MB binaries [20:49] actually 2x10MB [20:49] jdong: oh? [20:49] oh wow [20:49] handbrake is pretty junky, but popular amongst users [20:49] SUNWjoejaxx: upstream uses a fairly patched up media stack and very specific mp4v2, etc. [20:49] so... I'd rather not basically fork the project by hacking it to build against system libs [20:49] yeah [20:49] so I'm just gonna admit defeat and bundle upstream libs [20:49] I dont' want another upstream that hates our guts (looks at azureus-gcj) [20:50] lol [20:50] but at the same time, debian/copyright looks like it's gonna be like 20 pages. [20:50] mpeg4ip alone is like 10 pages [20:50] jdong, this proprietary app is 99.9% fortran, and uses a single c lib for helper application. it takes about an hour to build on 4 cores of 1.6ghz itanium. if the c lib compile fails, it still spends an hour on the fortran, then fails on the final linker step [20:50] but the build system (its own one) cannot bail or resume - it always starts from scratch [20:50] directhex: haha same here [20:50] lol fortran :) [20:51] and the c lib fails due to use of POSIX defines removed in 1992 :) [20:51] they use some weird jam+make+autoconf [20:51] and the makefile for bundled libs builds 1-by-1 in serial but doesn't fail until all have been attempted to be built [20:53] Hi guys, I've just uploaded cifer (a multipurpose classical cryptanalysis and code-breaking tool) to revu: http://revu.ubuntuwire.com/details.py?package=cifer . Does anybody have a bit of free time to take a look? Thanks. [20:53] jdong: i am still wondering if a conflict is enough though [20:53] jdong: or the right way [20:55] SUNWjoejaxx: I'd recommend renaming the file [20:55] I somehow think the idea of conflicting dpkg won't be appreciated :D [20:55] jdong: same here hahahaha [20:57] is there anything in policy against using bzip2 compression instead of gzip if there's a significant filesize benefit? === dmb_ is now known as dmb [21:20] Can somebody of the MOTUs comment on my last comment in bug 275688: https://bugs.launchpad.net/ubuntu/+source/fpc/+bug/275688/comments/41 [21:20] Launchpad bug 275688 in fpc "License issue: please sync fpc 2.2.2-4 (universe) from Debian unstable (main)" [High,Confirmed] https://launchpad.net/bugs/275688 [21:20] Ubuntu bug 275688 in fpc "License issue: please sync fpc 2.2.2-4 (universe) from Debian unstable (main)" [High,Confirmed] [21:20] Basically I want to now if I am on the right track [21:20] jdong: is there any suggested way of renaming binaries during install: build in debian/rules? an mv seems hackish [21:21] anyway, Debian has removed all old versions of fpc from their archives [21:21] SUNWjoejaxx: I'd use a mv in the install target. [21:21] but maybe we can keep fpc in with backporting. [21:23] jdong: yeah that is what i did but it seems hackish haha [21:24] too bad there is no such thing as dh_rename [21:24] directhex: It's the /etc/php5/cli/php.ini [21:24] i think i would feel better [21:24] lol [21:24] \sh: why isn't Leonov in the WhoUsesBzr page? :) [21:25] quentusrex, i don't know whether there's a specific way of handling that file. there might be. is there a php team you can ask? [21:25] quentusrex: Don't patch the php.ini, just add what you need under /etc/php5/conf.d/ [21:26] jmarsden: would that override the upload_max_filesize? I need it changed from 2M to 20M [21:26] I don't know... I think it will. Try it and see? [21:27] Also, how does apt-get handle package updates? do I have to manually specify the what should change? or will it handle what has changed? [21:28] quentusrex: Your question makes no sense to me. apt-get installs packages... it doesn't let you say "install this bit of the package only..."? [21:28] \sh: oh, it is :) [21:28] jmarsden, no, it DOES ask you about config files [21:29] jmarsden, assuming some criteria are met, etc [21:29] I mean, if I have a script that adds a user, and a group, etc. And the user installs my package. Then I have to change some of the documentation. Will it try to add the user and group during the update? [21:29] Not if your script checks whether that user/group alraedy exist before it adds them :) [21:30] jmarsden: the reason I use that as an example, is I have a script that modifies a mysql table. I don't want that part run during an update. Only an install.... [21:31] So if the person installs mypackage-0.2 the script is run. But if they are updating from mypackage-0.1 to 0.2, then it shouldn't run... [21:31] There is a way to test for that... but I forget what it is... read the docs on what dpkg really does during an update... [21:32] ok [21:33] I wish there was more clear documentation on how to package software... [21:33] Either I've completely missed something... or there is a steep learning curve for packaging software... [21:35] quentusrex: It's steep, but not vertical :) [21:35] quentusrex: /me thinks the latter is treu [21:35] :) [21:35] s/treu/true [21:37] What's the best way of simulating the launchpad build process on my dev box? Using pbuilder and plogin? Am I remembering that correctly? [21:37] Is it possible to use apt-get install on a local package? === xxx__ is now known as _iron [21:37] awmcclain: https://wiki.ubuntu.com/PbuilderHowto [21:38] quentusrex: There is a way to build a repostiory locally... there's something in an ubuntu wiki page. [21:38] jmarsden: thank you [21:38] ! [21:38] I have a package I'm trying to test and it has dependancies... [21:38] * Elbrus uses pdebuild (depends on pbuilder) but had to resort to sbuild the other day for one package... [21:39] quentusrex: quentusrex Yes, if you set up a local repo. Maybe just use dpkg -i to install it? [21:39] I use dpkg -i to install it, but dpkg won't download and install the dependancies... [21:40] quentusrex: example of building your own repo: http://blogs.cae.tntech.edu/mwr/2007/05/28/my-own-private-debian-repository/ [21:41] but dpkg -i should take dependancies into account, right? [21:41] it gives me errors... [21:41] which are? [21:41] saying that the packages aren't installed. [21:41] !pastebin [21:41] pastebin is a service to post multiple-lined texts so you don't flood the channel. The Ubuntu pastebin is at http://paste.ubuntu.com (make sure you give us the URL for your paste - see also the channel topic) [21:42] I'll have to try again to get the errors... Thank goodness for a virtualized testing server... [21:43] Elbrus: dpkg does NOT handle dependencies [21:43] quentusrex: Take a look at pbuilder too. [21:43] oops [21:44] Depending on what you are doing, apt-get build-dep can sometimes help [21:44] pbuilder is useful, but I am trying to install it on an actual usable machine. [21:44] I'm testing fuctionality at this stage. [21:44] quentusrex: Ah. Sorry. [21:44] nhandler: can build-dep handle a local file rather than a file in the repo? [21:45] quentusrex: The file was never in the repos? [21:45] not yet... [21:45] Sorry for the n00b question, but it's been a while since I've done package maintenance. Pbuilder automatically fetches the packages in Build-Depends*, right? That's what I'm trying to test. [21:45] Another option is to use a PPA. Upload the package, add the entry to your sources.list, and then install it using apt [21:45] I'm going to be the first to 'hopefully' put it there... [21:45] awmcclain: Yes [21:45] Yes it does awmcclain [21:45] nhandler: that could work... [21:46] nhandler: Can't you apt-get install the package after dpkg -i fails due to dependencies? [21:46] I seem to remember doing that. [21:46] awmcclain: You can. But I'm not sure what quentusrex is trying to test [21:47] I don't think he wants to manually apt-get each dependeny [21:47] One last thing... is it still the best route to get a package into debian, then port to ubuntu? [21:48] Best, as long as time is not critical, I'd say [21:48] Heh. So I've seen. Thank you all. === cr3_ is now known as cr3 [22:03] nhandler: Oh, no, from what I've seen (though I haven't tested in a while), is that apt will get your dependencies for you on a botched dpkg -i. [22:04] awmcclain: apt won't do it automatically. dpkg will complain about you not having the dependencies installed. You can then use apt to install them (manually) [22:05] Each dependency individually? [22:06] awmcclain: Yes. However, now that I think about it, I think gdebi might be able to fetch the dependencies automatically for you if they are missing (but I'm not positive) [22:06] you can usually try to run apt-get -f install [22:12] Oh boo. http://paste.ubuntu.com/78157/ [23:20] Ah ha. the pbuilder conf is broken in the ubuntu package. [23:26] Can someone check some warnings for me? https://launchpad.net/+builds/lansones [23:26] Does that look 'broken' [23:28] Not to me. The build environment will download the build dependencies IIRC [23:29] thanks awmcclain it's my first... I'm all kinds of nervous.... [23:30] quentusrex: Oh, it'll break somewhere else. Then you just need to make changes and reupload. ;) [23:30] quentusrex: Are you testing in pbuilder before you upload? [23:37] awmcclain: I'm building it with my actual system. and that works. [23:37] yay it worked. [23:37] quentusrex: Right, but that would only be a useful test the first time (in terms of dependencies), unless you remove all the build-deps and dependencies after each build. [23:37] :) [23:38] awmcclain: I do.. I have a snapshot of a virtual server that I use for test building. [23:38] quentusrex: Perfect. [23:40] I'll be working on getting a better build framework setup, but for now I just need it to work... [23:43] awmcclain: someone sent earlier how to setup an apt mirror. I think I'll need to do that... [23:44] quentusrex: There's a link on https://wiki.kubuntu.org/PbuilderHowto === ScottK-laptop is now known as ScottK2 [23:56] awmcclain: is there a way to automatically increment the changelog? [23:57] quentusrex: For what... a different distribution or a different build version? [23:58] different build version [23:58] I need to fix a bug... and update the changelog... [23:59] quentusrex: man debchange