[00:01] <cjwatson> dtchen: please go ahead - my change to libsdl1.2 was just a rebuild, and I don't really want to merge it
[00:02] <dtchen> cjwatson: thanks
[00:09] <MTecknology> Amaranth: ya, idk how much
[03:20] <EagleScreen> hi
[03:21] <EagleScreen> debuild -S -sd always give me error
[03:21] <EagleScreen> see plEASE http://pastebin.com/d65b07399
[03:27] <RoAkSoAx> EagleScreen, I guess that you want to do: debuild -S -sa instead of debuild -S -sd
[03:28] <EagleScreen> may be, but it gives the same error
[03:28] <EagleScreen> i have tried with two completly different packages
[03:29] <ajmitch> do you have make installed?
[03:29] <ajmitch> or is ~/devel on a special filesystem?
[03:29] <EagleScreen> yes
[03:29] <EagleScreen> cheking it
[03:29] <EagleScreen> ohhh
[03:30] <ajmitch> mounted noexec?
[03:30] <EagleScreen> ~/devel is a link to a directory in a ntfs-3g partition
[03:30] <ajmitch> right, that could be problematic
[03:31] <ajmitch> I'm not sure of the state of NTFS stuff, whether it can be mounted exec (probably can), and if everything will work
[03:32] <dtchen> ok, who has a softmodem on HDA?
[03:33] <dtchen> i.e., has sl-modem-daemon or hsfmodem installed
[03:33] <ajmitch> hm
[03:33]  * dtchen squashes more PA bugs
[03:34] <ajmitch> not sure how my modem is hooked up in the laptop
[03:35] <ajmitch> looks to be HDA, though I don't have any dialup account to test with
[03:38] <EagleScreen> ok, now the problem is this other one http://pastebin.com/d2d71b131
[03:40] <ajmitch> ran sudo apt-get build-dep konversation?
[03:43] <EagleScreen> just the same error
[03:43] <EagleScreen> and is it really necessary to just build the source package?
[03:44] <ajmitch> when the source package needs certain packages to run its clean target in debian/rules, then yes
[03:44] <ajmitch> most often with things like quilt or dpatch
[03:44] <ScottK> EagleScreen: You need a newer pkg-kde-tools
[03:45] <ajmitch> thanks ScottK, I was about to suggest #kubuntu-devel would know more :)
[03:46] <EagleScreen> thanks ScottK, will check it
[03:46] <ScottK> EagleScreen: It's also a bug that the version require for pkg-kde-tools aren't specified properly in the package.
[03:47] <EagleScreen> 0.4.11uubntu7 is mine
[03:48] <ScottK> You need the one from lucid
[03:50] <EagleScreen> also debhelper from lucid :\
[03:51] <ScottK> I don't think so, but maybe
[03:53] <EagleScreen> yes it told me it
[03:54] <EagleScreen> thanks you guys
[03:54] <EagleScreen> see u tomorrow (may be)
[04:37] <MTecknology> What section would this fall under? https://edge.launchpad.net/ricoh-r5u87x
[04:45] <RAOF> MTecknology: Having a look at http://www.debian.org/doc/debian-policy/ch-archive.html#s-subsections suggests... video?  It's for webcams, which are about the video.
[04:46] <MTecknology> RAOF: thanks
[05:06] <MTecknology> I'm trying to bui;d this package but it wants the authors pgp key. I'm only packaging it for them. Where does debuild pick the email it's going to look for the pgp key of?
[05:06] <maco> MTecknology: $DEBEMAIL
[05:06] <maco> and i would assume that's package author...
[05:07] <maco> because its just for debian/changelog
[05:07] <maco> also $DEBFULLNAME
[05:09] <MTecknology> maco: thanks.. and for this? Enter passphrase: gpg: gpg-agent is not available in this session
[05:09] <maco> start gpg-agent
[05:09] <MTecknology> thanks :)
[05:09] <MTecknology> start: Unknown job: gpg-agent
[05:09] <MTecknology> seems to have signed fine anyway
[05:10] <jmarsden> MTecknology: You don't need the agent, it just avoids the need to repeatedly enter the passphrase for multiple signings
[05:10] <maco> MTecknology: oh its not an upstart job. i meant the verb "start" not the command start
[05:12] <MTecknology> thanks :)
[05:12] <MTecknology> this packaging thing doesn't seem as scary as it did 30min ago
[05:18] <maco> ^_^
[05:19] <MTecknology> Any ideas why this hates me? http://paste.ubuntu.com/337038/
[05:21] <MTecknology> debuild -S ran through w/o complaints
[05:21] <mrooney> I'm using a very simple debian/rules to invoke cdbs/pycentral, where can I start debugging if "python setup.py install" ships my package correctly in dist-packages symlinked to pyshared, but installing the generated deb doesn't create the package in dist-packages?
[05:22] <jmarsden> MTecknology: Well, obvious question... did you do a pbuilder create to set up that chroot earlier?
[05:22] <MTecknology> nope
[05:22] <jmarsden> Then that's why the error message says you need to do so.... :)
[05:22] <MTecknology> jmarsden: I'm trying to follow https://wiki.ubuntu.com/PackagingGuide/Basic
[05:23] <jmarsden> And it doesn't tell you to set up your pbuilder chroot before you use it????
[05:23] <MTecknology> jmarsden: this? https://wiki.ubuntu.com/DebootstrapChroot
[05:24] <jmarsden> MTecknology: More like https://wiki.ubuntu.com/PackagingGuide/Complete#The%20Personal%20Builder:%20pbuilder
[05:24] <ScottK> mrooney: Does your package declare with python versions the binary supports in X-B-Python-Version
[05:25] <jmarsden> You seem to be using a partial version of the Guide which lacks some info??  Not sure about that, I always use the Complete one :)
[05:25] <MTecknology> jmarsden: i  liked the word Basic in the title... :P
[05:26] <jmarsden> For me that is more a reminder of 10 PRINT "HELLO"   20 GOTO 10    "BASIC" :)
[05:26] <MTecknology> :P
[05:27] <MTecknology> jmarsden: so that creates a very minimal virtual environment that's clean for building packages?
[05:27] <maco> pbuilder!
[05:28] <MTecknology> maco: hurray!?
[05:28] <jmarsden> Yes.  See https://wiki.ubuntu.com/PbuilderHowto
[05:28] <maco> use it!
[05:28] <jmarsden> MTecknology: and after that see http://wiki.debian.org/PbuilderTricks
[05:29] <MTecknology> I wonder how long it'll take to setup the environment
[05:29] <jmarsden> MTecknology: It is a *very* helpful way to check that you have your dependency stuff correct before uploading packages to a PPA or to Ubuntu itself.
[05:30] <jmarsden> MTecknology: Minutes if you have a fast Internet connection.
[05:30] <MTecknology> we're throttled here
[05:30] <MTecknology> dakota state uni kinda sucks
[05:30] <jmarsden> I'm spoiled... 10Mbits/sec down from Verizon FIOS here :)
[05:31] <mrooney> ScottK: Hm, I think? http://bazaar.launchpad.net/~mrooney/wxbanker/packaging-0.6/annotate/head%3A/control
[05:31] <MTecknology> I think we're
[05:31] <mrooney> I'm honestly not 100% what ${python:Versions} means
[05:31] <MTecknology> I think we're 'supposed' to get 2Mbit down but the reality is ~60Kb/s 80% of the time
[05:32] <jmarsden> Ewww.  At 60kbits/sec creating a fresh chroot could take a while.
[05:32] <MTecknology> Ti's on I: Retrieving net-tools
[05:32] <MTecknology> It's*
[05:33] <jmarsden> I only notice that text if it fails to find something (usually a Debian sid one when that happens!).
[05:35] <jmarsden> Although right now Lucid is in a weird state (not for a base pbuilder, but X is all weird and broken if you update Lucid today).
[05:37] <ScottK> mrooney: That should be correct.  BTW, you don't need the <<3.0 in XS-Python-Versions.  Thats assumed.
[05:39] <mrooney> ScottK: oh okay, is that a generic major version assumption, or specific to python?
[05:40] <MTecknology> ok - so I got further - any idea what I screwed up on this time?
[05:40] <jmarsden> MTecknology: pastebin?
[05:40] <MTecknology> http://paste.ubuntu.com/337044/
[05:40] <MTecknology> sorry
[05:40] <jmarsden> I'm good but not *that* good :)
[05:41] <MTecknology> :P
[05:41] <jmarsden> Your package needs debhelper version 7 but you did not include it in your Build-Depends: line in debian/control, most likely.
[05:42] <ScottK> mrooney: specific to python
[05:44] <MTecknology> jmarsden: Build-Depends: debhelper (>= 7)
[05:44] <MTecknology> jmarsden: does my package actually need that or is it jsut an example?
[05:45] <jmarsden> If you have debian/compat containing the number 7, your package needs that (so they match).
[05:45] <mrooney> ScottK: okay. My previous release works fine, I've made more changes since then to setup.py than debian/ so I guess I should look there, but since it setup.py --install's fine, it seems logical to suspect my packaging
[05:45] <jmarsden> I can't tell whether your package truly uses debhelper 7 features without reading all of your debian/rules file...
[05:46] <MTecknology> jmarsden: http://paste.ubuntu.com/337047/
[05:48] <jmarsden> Doesn't look like it needs dh7 specifics to me, but if you are following the guide and it said you should create debian/compat with a 7 in it, then... you can stick with the guide.  You need some sort of Build-Depends: dephelper    obviously, the only question is whether you really need 7.
[05:48] <jmarsden> *debhelper
[05:48] <jmarsden> I'd just add it, for a first package.
[05:48] <MTecknology> actually the guide said 5
[05:49] <MTecknology> dh_make just defaulted to 7
[05:49] <jmarsden> Well, then you could make it 5 in both places if you want.
[05:49] <MTecknology> *debhelper ?
[05:49] <jmarsden> As opposed to dephelper which is what I typed earlier.
[05:49] <jmarsden> *foo usually means a type correction
[05:50] <jmarsden> *typo correction :)
[05:50] <jmarsden> if you see what I mean :)
[05:50] <MTecknology> ya
[05:50] <MTecknology> but I'm lost now..
[05:50] <MTecknology> Build-Depends: debhelper (>= 7)
[05:50] <jmarsden> Sure, just do it.
[05:50] <MTecknology> that's what dh_make made by default
[05:50] <MTecknology> Build-Depends: debhelper (>= 5)
[05:51] <jmarsden> Unless you need the package to build on older versions of Debian and Ubuntu, 7 is fine.
[05:51] <MTecknology> That's what the wiki says - but it's not regularly updated
[05:51] <MTecknology> ok
[05:51] <jmarsden> Exactly.
[05:51] <MTecknology> so what was the fail?
[05:52] <jmarsden> Oh sorry my bad... wait a second...
[05:53] <MTecknology> I need to run off really soon but I'm hoping I can have this finished soon enough :)
[05:53] <jmarsden> Make it Build-Depends: debhelper (>=7), pkg-config
[05:53] <MTecknology> with the help of smart people
[05:53] <jmarsden> Fail was that it didn't have pkg-config around
[05:54] <MTecknology> still fails
[05:55] <MTecknology> !info debhelper
[05:56] <jmarsden> MTecknology: pastebin the output again please, the output ffrom the latest attempt
[05:57] <MTecknology> http://paste.ubuntu.com/337050/
[05:57] <MTecknology> I'm going to run - back in 1min
[05:58] <jmarsden> OK... looks like you need to recheck all your dependencies more carefully...
[06:06] <MTecknology> jmarsden: I have no idea what I'm doing here....
[06:07] <stochastic> Hi all, I'm just curious what the best method is to fix Bug #235696 it's an upgrade request and the latest version was just added to Debian Unstable.  Should the universe uploaders be subscribed, or should a new request for a pull from debian be made?
[06:08] <jmarsden> MTecknology: You have to tell the system *all* the packages that your package depends on.  Not just one or two.
[06:08] <jmarsden> Except the really basic ones already in the pbuilder chroot, that is.
[06:08] <MTecknology> jmarsden: how can I see what it depends on?
[06:09] <jmarsden> You wrote the code... or you read the INSTALL file and see what they tell you it needs when you compile it by hand?
[06:09] <MTecknology> I didn't write the code
[06:09] <maco> MTecknology: by the way, regarding your download cap... maybe set up aptcacher-ng on a system on your lan so you only have to download packages once?
[06:09] <MTecknology> I'll check that though - thanks
[06:10] <MTecknology> maco: I don't have a spare system but thanks for the suggestion
[06:11] <MTecknology> jmarsden: I see it now - task for tomorrow
[06:11] <jmarsden> MTecknology: Then when you build it, it should have info on what libraries etc it needs around.  We can do it one at a time as the builds fail, but it will take a while...
[06:11] <jmarsden> OK.
[06:11] <MTecknology> jmarsden: maco: Thanks very much :)
[06:12] <MTecknology> This doesn't seem like a hard process; just not easy for a very beginner to figure out - which isn't all bad
[06:12] <MTecknology> alrighty - g'night all
[06:12] <jmarsden> Goodnight.
[06:14] <porthose> stochastic, wait for the package to migrate to debian testing, then change the bug to a sync request :)
[06:15] <stochastic> porthose, okay.  Thanks.
[06:17] <alkisg> Can I detect from my prerm script if the package is being purged or removed? http://www.debian.org/doc/debian-policy/ch-maintainerscripts.html#s-mscriptsinstact
[06:58] <dous> win2
[07:50] <mrooney> ScottK: wow, I figured it out but that was OBSCURE
[07:51] <mrooney> I created a trivial postinst, which apparently stopped pycentral from generating its own which was what was doing the linking
[07:52] <mrooney> how it is remotely discoverable that creating a postinst breaks your package is beyond me though, wow, it took me three days haha.
[07:55] <mrooney> Now I need to figure out how to have a postinst with pycentral, any tips? Is there some way to supply a script it runs after the autogenerated one?
[07:58] <Ancalagon> hi
[07:59] <Ancalagon> I'm already know bash scripting and VBA. Now I want to learn something else that help me to devel something for linux world. Some language that have the possibility to have GUI. Have you some suggestion? C? Java?
[08:00] <tsimpson> Ancalagon: C, C++ or python are a good start, you can use several cross-platform GUI toolkits with each of those
[08:00] <mrooney> Ancalagon: Python is pretty friendly to beginners, and Ubuntu uses it a fair amount.
[08:01] <alkisg> VBA is very similar to Gambas, but python would be better accepted by the community... C and Java are quite different from VBA
[08:01] <dholbach> good morning
[08:06] <alkisg> My sch-server package is installed on servers. On postinst, I want to expose some of the server's configuration files by using apache. So I'm creating an apache site and I'm making symlinks to some of the server's configuration files. My question is, where's a good place to put that site on the file system? /var/www/sch-server?
[08:08] <alkisg> (For example, I create a symlink /var/www/sch-server/firefox/user.js there that shows to /usr/lib/firefox-3.5.5/defaults/preferences/user.js)
[08:14] <slytherin> alkisg: yes /var/www, but why are you handling this in postinst?
[08:14] <alkisg> slytherin: thanks, how should I do it?
[08:15] <alkisg> E.g. /usr/lib/firefox-3.5.5/defaults/preferences/user.js could be in a different path depending on the firefox version
[08:16] <slytherin> alkisg: Why does your server need to have access to user.js form firefox?
[08:16] <alkisg> I want the sch-clients to be able to copy the settings from user.js that the server has (different package, installed on the clients)
[08:17] <alkisg> The server announces itself on the network using avahi, and the clients copy over whatever settings the teacher needs
[08:17] <Ancalagon> so I can choose between C, C++ or python.. hm.. ok. And those are all good for linux, isn't it?
[08:17] <alkisg> slytherin: I.e. public ssh+italc keys, firefox settings etc
[08:19] <slytherin> alkisg: hmm. I don't have better solution for this right now. But I still think postinst is not good idea.
[08:20] <alkisg> slytherin: I could do that from a script that the user runs after the installation, e.g. "sch-server-setup", would that be a better idea?
[08:20] <slytherin> Can't say. Haven't dealt with many server installations.
[08:20] <alkisg> Thank you :)
[08:49] <persia> alkisg: You might also just install the symlinks, rather than creating them at install time.  dh_link might help.
[08:53]  * Yagisan waves
[08:54] <alkisg> The problem is that some symlinks don't have fixed targets, e.g. I need code to find out where firefox keeps its user.js file :-/
[08:55] <alkisg> Thanks, need to go, bbl :)
[08:59]  * persia would have thought that most standard configuration file locations would be defined by the packaging that delivered them
[09:06] <mrooney> persia: hey, how's it going?
[09:07] <persia> mrooney: Alright.  For you?
[09:07] <mrooney> pretty good!
[09:08] <mrooney> but I ran into an dh_pycentral issue that has stumped me, are you familiar with it?
[09:08] <persia> No.  The install-time special handling of python modules remains opaque to me.
[09:08] <mrooney> alas.
[09:09] <mrooney> know any pros to point me to?
[09:11] <persia> There's usually some python folk around here: my recommendation would be to wait a bit for someone to catch the backscroll.
[09:14] <mrooney> sounds good, good (time of day) to you, I'm headed to bed
[09:15] <mrooney> I tried to look at your LP profile to see what time of day it actually is for you, but you seem to have played a humorous game with the map
[09:16] <persia> The timezone is correct, although the latitude is deliberately skewed.
[09:16] <persia> Have a good night.
[09:30] <POX> mrooney: use dh_pysupport
[09:30] <POX> /usr/share/doc/python-support/README.gz
[09:59] <persia> POX: Do I read that correctly that one just calls setup.py and adds dh_pysupport, and doesn't need to bother with python-specific files in debian or fields in debian/control?
[10:04] <POX> persia: you have to add python:Depends and external modules package needs in Depends
[10:05] <POX> (python:Depends will be replaced with interpreter / helpers dependencies only)
[10:05] <persia> That doesn't seem very tricky.  I just always got stuck on the special fields like XB-Python-Version and similar.
[10:06] <POX> if module doesn't work with all supported Python versions, you can use XS-Python-Version
[10:06] <POX> XB-P-V is used only in pycentral
[10:08] <persia> RIght, which gets back to the bit that was confusing me.  I'll just hope I mostly encounter the case where I don't have to worry about that :)
[10:19] <POX> persia: I recommend rules.tiny - it does the right thing for python modules and extensions (even for -dbg packages)
[10:19] <persia> POX: Really?  I've used rules.tiny for all the new packaging I've done for most of the past year, and that makes me suddenly unafraid to package python.
[10:38] <slytherin> Can anyone please translate the error in this bug - https://bugs.launchpad.net/bugs/493986 It appears to be Spanish.
[10:50] <persia> slytherin: loose gloss: unable to write the file because it's also in gstreamer0.10-lame (undeclared conflicts).  One way to get the right error messages is to grep for the string in the appropriate .po file for the affected package.
[10:51] <slytherin> persia: I guessed that meaning after reading the errors carefully. Anyway the bug is invalid because -lame package is not in repositories. So whether -ugly-multiverse overwrites file in that package is not our concern.
[10:57] <thekorn> hi,
[10:58] <thekorn> are there some easy ways, some helpers etc. to write manpages?
[11:01] <persia> thekorn: help2man is my favorite
[11:02] <thekorn> persia, wow, that's exactly what I was looking for, thanks
[11:03] <slytherin> I believe there is also docbook2man but then you need to be familiar with docbook first.
[11:04] <thekorn> it's event mentioned here: https://wiki.ubuntu.com/PackagingGuide/SupplementaryFiles  but I somehow skiped it
[11:04] <cornucopic> no LaTex to man ? :)
[11:04] <thekorn> rest2man would be cool ;)
[11:05] <persia> thekorn: That's tricky, but wsdl2man ought be easy enough to implement.
[11:06] <thekorn> ok, rst2man already exists, not sure how good it works
[11:07] <slytherin> my bad docbook2man expects file in SGML docbook format not XML docbook format.
[11:33] <jaldhar> is laserjock on this channel?  If so what times are good for talking to him?
[11:34] <persia> jaldhar: sometimes, but he's not on IRC so often these days.  He's in UTC-5, if that helps.  Email might be better, if only to schedule something.
[11:38] <jaldhar> persia: thanks.  This is about a package maintained by MOTU but which he touched last.  I'll email him
[11:38] <persia> jaldhar: Just ask here.  It might not be special.
[11:38] <persia> (most packages don't have specific maintainers)
[11:41] <jaldhar> well ok.  moodle is in pretty bad shape in Debian.  It's somewhat better in ubuntu (and several versions newer) but has not been contributed back.  The Debian moodle maintainers are totally unresponsive so I was wondering if laserjock or anyone here had any insight into what's going on.
[11:42] <jaldhar> i.e. have you tried contacting them and got stonewalled or is there some circumstance that prevents a Debian upload or what?
[11:47] <azeem> jaldhar: (i) I think none of the Debian moodle maintainers is a DD (or even a DM?) (ii) they (not sure whether that is Debian moodle or moodle upstream, which might overlap) are having a meeting apparently this week, see madduck's planet post about czech beer
[11:48] <persia> Ah.  That probably would benefit from direct discussion, but you might check the ML archives first (http://lists.debian.org/debian-edu/) or the Debian moodle bug reports.
[11:52] <thekorn> I've a question about packaging new packages: I would like to create two new packages, one package is depending on the other one. Is there some 'best practice' in revu or in needs-packaging bugs to indicate this dependancy
[11:53] <thekorn> to make sure they get attention in the correct order
[11:53] <jaldhar> azeem: oh ok I'll check that out.
[11:53] <persia> I don't think anyone other than the packager pays attention to needs-packaging bugs, except to track things (avoid duplicates, etc.)
[11:54] <persia> My recommendation would be to add a note in REVU on the depending package indicating which package it depends upon.
[11:54] <jaldhar> persia: I didn't think to check debian-edu but the bug reports paint a sorry picture
[11:55] <azeem> jaldhar: if you really want to help moodle in Debian, I suggest to talk to madduck, he might be the most accessible over IRC and can introduce you to Penny and Dan at least
[11:56] <jaldhar> azeem: my interest in moodle is solely to get it to stop blocking one of my packages from testing :-)  I'll talk to madduck
[12:05] <cornucopic> hey all. I am a total packaging newbie. I want to distribute Ubuntu/Debian packages for a pure Python module
[12:05] <cornucopic> What would be a good starting point ?
[12:06] <directhex> cornucopic, find a package with similar scope, and use its debian/ folder as a base
[12:06] <cornucopic> directhex, hm. Ok!
[12:42] <Yagisan> woo - I've now duplicated Bug #493575 on Ubuntu 8.04, Ubuntu 9.04 and Ubuntu 9.10
[13:32] <lfaraone> I'm trying to requestsync something, but on submit I get "E: Could not connect to fiordland.ubuntu.com:25: Connection refused (111)". Is it down for anybody else?
[13:38] <slytherin> lfaraone: I can telnet on SMTP port on that server. So not sure why it is giving you connection refused error.
[13:43] <ghostcube> lfaraone: maybe a greylisted ip ?
[13:43] <ghostcube> or even in blacklist ?
[13:43] <MTecknology> so for libglib2.0-0; whould I do Build-Depends libglib (>= 2) ?
[13:44] <lfaraone> ghostcube: possibly.
[13:44] <MTecknology> or maybe (>= 2.0) ?
[13:45] <dholbach> MTecknology: you need a real binary package name
[13:45] <dholbach> libglib2.0-dev it'd probably be
[13:46] <MTecknology> thanks
[13:53] <ghostcube> MTecknology: in the most control files inside a debian package is listet how the dependencies are written i think so
[13:53] <ghostcube> i start this point mostly if i do a package
[13:53] <MTecknology> ghostcube: listet?
[13:54] <ghostcube> you see how to call them
[13:54] <ghostcube> :)
[13:54] <MTecknology> you lost me right now :)
[13:54] <ghostcube> maybe lol
[13:55] <MTecknology> I'm still trying to build my first package
[13:55] <ghostcube> oh i know this :) not so far away from mine first
[13:55] <ghostcube> :D
[13:55] <ghostcube> but only for my own use never released any
[13:56] <MTecknology> I'll be releasing this
[13:57] <ghostcube> oh ok then i will shut up and dont tell u anything :) maybe better
[13:57] <ghostcube> hehe
[13:58] <MTecknology> this doesn't seem to work right...
[13:58] <MTecknology> I'll make a pastebin and see what you guys think in a second here...
[13:59] <MTecknology> http://paste.ubuntu.com/337251/
[14:00] <slytherin> MTecknology: What is not working right?
[14:00] <slytherin> I don't see any error there.
[14:00] <MTecknology> dpkg: error processing pbuilder-satisfydepends-dummy (--install):
[14:01] <MTecknology> slytherin: what causes that message?
[14:02] <slytherin> MTecknology: not an error even though the message looks that way.
[14:02] <MTecknology> oh.. i can ignore those?
[14:02] <slytherin> MTecknology: pbuilder creates a dummy package to force the installation of the build dependencies you have specified.
[14:02] <MTecknology> oh
[14:09] <slytherin> MTecknology: from your pastebin, it is clear that package was built properly.
[14:09] <MTecknology> slytherin: thanks
[14:10] <MTecknology> slytherin: I'm trying to figure out dput now and see if I will smile soon.. I'm getting this error though - No host ricoh found in config
[14:10] <MTecknology> I have [ricoh] in ~/.dput.fc
[14:11] <slytherin> MTecknology: I never used personalized config file for dput so can't help there.
[14:13] <bjsnider> siretart, there is a script in the ffmpeg-extra debian directory called readme.upstream-upgrade
[14:13] <bjsnider> siretart, it contains the following command: git clone git://git.debian.org/git/pkg-multimedia/ffmpeg-debian.git
[14:13] <alkisg> MTecknology: it's ~/.dput.cf , not fc
[14:13] <bjsnider> command doesn't work
[14:14] <bjsnider> wondered if it might need to be updated
[14:14] <MTecknology> alkisg: .. thanks :)
[14:14] <siretart`> bjsnider: yes, the git repository has been renamed from 'ffmpeg-debian.git' to 'ffmpeg.git'
[14:15] <MTecknology> alkisg: that makes it work :D
[14:15] <siretart`> bjsnider: I guess you want to upgrade to current trunk, yes?
[14:15] <bjsnider> yep
[14:15] <siretart`> bjsnider: have you seen the recent thread on ffmpeg-devel with "upgrade problems"
[14:15] <bjsnider> i thoguht it ws something like that
[14:16] <bjsnider> is there a similar repository for x264?
[14:16] <alkisg> MTecknology: nice, I hope it builds OK
[14:16] <bjsnider> there's no upgrade script
[14:16] <MTecknology> alkisg: me too, thanks :)
[14:16] <siretart`> bjsnider: given that, upgrading the system ffmpeg right now will instantly break nearly everying using ffmpeg
[14:16] <MTecknology> alkisg: if this builds ok, how hard is it to get it in the universe?
[14:16] <bjsnider> i see
[14:16] <siretart`> so spare your time, it currently doesn't make sense
[14:16] <bjsnider> well, that's inconvenient
[14:17] <alkisg> MTecknology: I've no idea, I'm just one step ahead of you ==> pretty new as well :)
[14:17] <MTecknology> alrighty :)
[14:18] <kecsap> hi all! I am new to contribute Ubuntu. I have a bug at launchpad with fix for a previous Ubuntu release and https://wiki.ubuntu.com/StableReleaseUpdates says to upload the fixed packages to the e.g. hardy-updates repository. How can I upload the new, fixed packages to this repo? I can not find any related wiki pages which describes the process. Can somebody point me to the right wiki page?
[14:19] <siretart`> bjsnider: indeed, it is.
[14:19] <siretart`> bjsnider: http://thread.gmane.org/gmane.comp.video.ffmpeg.devel/100196
[14:20] <randomaction> kecsap: you can't unless you are a Ubuntu developer. Use https://wiki.ubuntu.com/SponsorshipProcess
[14:21] <kecsap> randomaction: thanks!
[14:21] <MTecknology> alkisg: how long does a build normally take? I'm guessing most time is spent in the queue
[14:22] <alkisg> MTecknology: depends on the server load, I've seen from a few minutes up to many hours, when a new Ubuntu release is made...
[14:22] <MTecknology> alkisg: rejected
[14:22] <bjsnider> siretart, i'd be interested to know when that issue is resolved...
[14:22] <alkisg> MTecknology: see the build log
[14:22] <MTecknology> Unable to find distroseries: unstable
[14:23] <MTecknology> that was in the email i got
[14:23] <alkisg> Yeah you should have put "karmic" or something similar in the changelog, or upload to a specific series
[14:23] <MTecknology> oh...
[14:24] <MTecknology> I'll see if that helps :)
[14:24] <ogra> or lucid :)
[14:25] <MTecknology> how do I force it to upload again?
[14:25] <MTecknology> nvm..
[14:25] <slytherin> kecsap: You can attach appropriate debdiff to the bug and subscribe sponsors team
[14:26] <MTecknology> --force doesn't let me upload again
[14:27] <slytherin> MTecknology: where are you trying to upload?
[14:27] <MTecknology> lp
[14:27] <siretart`> bjsnider: yes, me as well.
[14:27] <slytherin> MTecknology: you mean your PPA?
[14:27] <MTecknology> ~ricoh-r5u87x-devs/ppa/ubuntu/
[14:27] <soren> MTecknology: What do you mean it doesn't let you upload again?
[14:28] <ogra> MTecknology, remove the .upload file
[14:28] <MTecknology> michael@panther:~/ubuntu-build$ dput ricoh ricoh-r5u87x_1.0-1_source.changes --force
[14:28] <MTecknology> Already uploaded to ricoh on ppa.launchpad.net
[14:28] <MTecknology> Doing nothing for ricoh-r5u87x_1.0-1_source.changes
[14:28] <MTecknology> oh
[14:28] <soren> dput --force ricoh ricoh-r5u87x_1.0-1_source.changes
[14:28] <soren> (move the --force)
[14:28] <slytherin> MTecknology: You can remove .upload file. But not sure if it will help.
[14:28] <soren> Err..
[14:28] <slytherin> AFAIK, LP does not allow reupload of same version even with --force. You need to increment version.
[14:28] <soren> Forget the "err..".
[14:29] <soren> slytherin: Not if the source package wasn't accepted.
[14:29] <alkisg> If my postinst fails, can I find the stderr output somewhere?
[14:29] <MTecknology> thanks :) - we'll see if it works this time
[14:29] <slytherin> soren: if the source package was not accepted then why would it be 'reupload'?
[14:30] <soren> MTecknology:  If your upload got rejected due to an invalid distro series, you can just fix that and upload again with the same version number.
[14:30] <soren> slytherin: Because dput doesn't know that it got rejected.
[14:30] <slytherin> Oh. I now understand what you mean.
[14:30] <soren> slytherin: dput uploads it. After while, soyuz looks at it and goes "what the heck is this?" and bounces it.
[14:30] <MTecknology> accepted :D
[14:33] <alkisg> If my postinst fails, can I find the stderr output somewhere?
[14:34] <soren> alkisg: How did you install the package?
[14:35] <alkisg> dpkg -i *.deb
[14:35] <soren> in that case the output should be right there on the console.
[14:35] <alkisg> ...and I didn't see any errors on the terminal
[14:35] <soren> Are you using debconf?
[14:35] <alkisg> No
[14:35] <soren> 15:35:27 < soren> in that case the output should be right there on the console.
[14:35] <soren> :)
[14:35] <alkisg> Thanks... Hmmm...
[14:36] <soren> What makes you think anything is sent to stderr?
[14:36] <slytherin> alkisg: see if you find any output in /var/log/dpkg.log
[14:36] <alkisg> slytherin: nope, nothing of interest there. soren: the package is now in a "configured files" state (iF)
[14:37] <alkisg> What's the correct way to retry to install it? dpkg-reconfigure doesn't cut it
[14:37] <soren> dpkg --configure -a
[14:37] <alkisg> Thanks
[14:37] <slytherin> alkisg: if there is nothing in console and nothing in dpkg log then how can you say that it failed.
[14:37] <slytherin> alkisg: wait, that will try o configure all the packages.
[14:38] <soren> dpkg.log shows what dpkg has done. Package state changes and such. Output from maintainer scripts never land in dpkg.log.
[14:38] <soren> slytherin: all packages that are not already configured.
[14:38] <soren> On a sound system, it will not do anything.
[14:38] <MTecknology> so- can I delete the upload file, change karmic to lucid in the name and upload it to build on lucid?
[14:38] <alkisg> I got this on the console: "the post-installation process returned 1" (or something like that)
[14:38] <slytherin> soren: my experience suggests otherwise.
[14:38] <MTecknology> for lucid*
[14:39] <alkisg> slytherin: so, is there another way to configure only that package?
[14:39] <slytherin> MTecknology: No. Now that it was accepted you will need to change version string.
[14:39] <slytherin> alkisg: dpkg-reconfigure is the way I usually do it.
[14:39] <MTecknology> slytherin: how should it change?
[14:40] <MTecknology> 1.0-2 instead of 1.0-1 ?
[14:41] <soren> alkisg: dpkg --configure name_of_package
[14:41] <soren> but -a really should be fine.
[14:41] <alkisg> slytherin: with `dpkg-reconfigure package` I'm getting "Package <package> is broken or not fully installed". Trying what soren said... :)
[14:41] <MTecknology> slytherin: or should I have the name lucid or karmic in the version string?
[14:41] <soren> dpkg-reconfigure is used to repeat the configuration step for packages that are already configured. This package is not ocnfigured.
[14:42] <slytherin> MTecknology: name of distro in string is better solution.
[14:43] <MTecknology> slytherin: 1.0-1-karmic and 1.0-1-lucid ?
[14:43] <MTecknology> granted I won't upload karmic for the version string
[14:44] <MTecknology> Is that how you would do it or would you suggest different?
[14:44] <soren> slytherin: It seems dpkg-reconfigure also has a -a optoin. That must be what you're thinking of. dpkg --configure -a is benign. It just takes the packages that are not yet configured and configures them.
[14:45] <slytherin> MTecknology: 1.0-1karmic1 and 1.0-1lucid1 etc.
[14:45] <MTecknology> thanks :)
[14:47] <MTecknology> slytherin: so 1.0-1 is the version and I'm uploading it for lucid for the 1st time; that's what that means?
[14:47] <alkisg> Nice, I got exactly what I wanted: my sch-client package failed to install because no server was around. :) (the server contains the ssh keys that the client should copy in order to be considered a "school client").
[14:47] <alkisg> But, is this a normal way to handle it? I.e. leave the sch-client package in an unconfigured state if the server isn't active when the sch-client package gets installed on the clients? (that's what I want, but is it a normal method?)
[14:49] <shriekout> http://revu.ubuntuwire.com/p/happytimer
[14:50] <shriekout> Please advised.
[14:50] <slytherin> MTecknology: yes, just note that this is for uploading to multiple distros in LP. Real life version differ from this.
[14:50] <shriekout> sorry...
[14:51] <shriekout> Please advise... :)
[14:51] <slytherin> alkisg: you can use gdebi to install packages. That way if dependencies are not satisfied it won't install the package instead of installing them in broken state.
[14:53] <MTecknology> slytherin: It automatically builds for all available architectures, right? amd64, i386, lpia
[14:53] <oojah> MTecknology: You don't necessarily need to rebuild/reupload for lucid. You can just copy the packages to different series on the ppa page.
[14:53] <MTecknology> oojah: oh.. sounds easier
[14:53] <oojah> It depends on what build deps you're using I believe. I'm not a motu.
[14:53] <Laney>  yes
[14:54] <oojah> So if the ABI of a dep changes from distro to distro you'll need to rebuild.
[14:54] <Laney> you can just copy sources though
[14:54] <Laney> and have them rebuild
[14:54] <Laney> or copy source+binary
[14:54] <slytherin> MTecknology: yes
[14:54] <alkisg> slytherin: thanks, it's not a package dependency problem, my postinst tries to download things from the local server using wget! I guess it's a little like the flash-plugin, which downloads stuff from the adobe site and fails if the network is down...
[14:55] <slytherin> alkisg: ideally that should be handled gracefully.
[14:55] <MTecknology> I feel a slight tickle :D
[14:55] <slytherin> alkisg: if the client does not have all the things it is supposed to download then user can always do --reconfigure
[14:55] <alkisg> slytherin: right, that's what I'm looking for. Downloading those files is essensial for the package, so what would be a graceful way to handle it?
[14:56] <alkisg> But I'd like the teacher to know in an obvious way that there's something wrong with his clients
[14:56] <alkisg> Simply "installed, not working, so reconfigure" isn't obvious enough for teachers... :-?
[14:57] <MTecknology> built on amd64 for both karmic and lucid now :D - now just need i386 and lpia for karmic
[14:58] <slytherin> alkisg: can't say, I am not a teacher. :-)
[14:58] <alkisg> Heh, thank you very much nonetheless :)
[14:59] <slytherin> alkisg: another option is to show the user a message to ask him if the files should be downloaded and that the client will not work without download.
[15:00] <alkisg> Ah, am I allowed to show a dialog? That would be nice :)
[15:00] <alkisg> Do I have to use debconf for that, or will zenity do?
[15:00] <alkisg> (or whiptail for console)
[15:00] <slytherin> alkisg: debconf would be ideal.
[15:01] <alkisg> Thanks, I'll try that
[15:01] <slytherin> alkisg: you can check b43-fwcutter package. It downloads certain files provided user approves it.
[15:02] <alkisg> Ty
[15:51] <bddebian> Heya gang
[15:51] <sebner> hhuhu bddebian :)
[15:52] <bddebian> Heya sebner
[16:01] <geser> Hi bddebian and sebner
[16:01] <bddebian> Heya geser
[16:02] <sebner> hoia geser :)
[17:20] <geser> dholbach: will the MC hold the 2nd meeting this month at the regular date? I've *very* strong doubts it
[17:21] <dholbach> geser: me too :)
[17:21] <dholbach> geser: somebody should send a mail saying so :)
[17:22] <geser> do we skip or move it to an other day?
[17:23] <dholbach> geser: I'd say just skip it
[17:24] <geser> ok, will send a mail then
[17:25] <dholbach> thanks a lot geser
[18:58] <skars> hi
[18:59] <skars> could someone help with nautilus?
[20:53] <highvoltage> any revu admins around?
[20:55] <ajmitch> yes
[20:55] <ajmitch> what do you need?
[21:01] <rjnienaber> okay, i've created a .deb file, what's the next step after that?
[21:03] <rjnienaber> getting it reviewed?
[21:07] <geser> !revu
[21:08] <rjnienaber> ta
[21:53] <MTecknology> How do I add a man page to a file?
[21:53] <MTecknology> to a package*
[21:54] <maco> is the manpage generated in the build process but simply not packaged, or does it not exist at all?
[21:54] <maco> what files get packaged are determined by the debian/*.install files
[21:56] <maco> MTecknology: ^
[21:56] <MTecknology> maco: I just made my first package today. It came from somebody elses code
[21:56] <maco> yay!
[21:56]  * maco hugs MTecknology
[21:56] <MTecknology> there is no .install file in debain/
[21:56] <MTecknology> thanks :)
[21:57] <MTecknology> there's emacsen-install.ex
[21:57] <oojah> I wonder if that's more or less common than someone packaging their own code as the first time :)
[21:57] <maco> probably less
[21:57]  * oojah agrees
[21:58] <maco> because a lot of packagers dont code
[21:58] <MTecknology> I write code and I'll probably package my own someday
[21:58] <MTecknology> but for now it's related to an open bug
[21:58] <oojah> MTecknology: *.ex files are example files and should be deleted if they aren't used.
[21:59] <maco> ooo thats what "ex" stands for! haha i just knew to get rid of them
[21:59] <oojah> ...
[21:59] <maco> <-- slow
[21:59] <oojah> I presume that's what they are, I can't say for sure.
[21:59] <maco> makes sense
[21:59] <oojah> I'm a biginner as well.
[21:59] <maco> i figured it was some templating thing
[22:00] <oojah> er, "beginner".
[22:00] <MTecknology> so mv manpage.1.ex manpage.1
[22:00] <oojah> MTecknology: Does a manpage actually exist?
[22:00] <MTecknology> no
[22:00] <maco> im a motu so theoretically i should know how some of this works :P
[22:01] <maco> and not be a beginner anymore
[22:01] <MTecknology> I'd like to make one for this package
[22:01] <maco> i have no idea how to write manpage syntax :-/
[22:02] <oojah> MTecknology: Right, in that case I believe you should create the manpage and then put it into the debian directory, like manpage.1.
[22:02] <oojah> maco: I write manpages in docbook format and translate them. Much easier and nicer.
[22:02] <MTecknology> will it be magically detected or do I need to make a .install?
[22:02] <maco> ah yeah, docbook is all xml niceness
[22:03] <oojah> MTecknology: You'll have to ask somebody else about the next bit, or check the guide, I'm not sure.
[22:03] <MTecknology> thanks
[22:03] <MTecknology> happily; somebody already used the package and said it works
[22:03] <MTecknology> now I just need to make a man page and get it put in the universe :P
[22:04] <oojah> MTecknology: Which package?
[22:04] <MTecknology> https://edge.launchpad.net/~ricoh-r5u87x-devs/+archive/ppa
[22:05] <oojah> Neat
[22:06] <MTecknology> I guess the camera firmware is also wiped on every startup
[22:06] <MTecknology> maybe I can make the user not even need to run sudo r5u87x-loader --reload
[22:06] <maco> gettin fancy?
[22:07] <MTecknology> this is for my use too so fancy is nice :)
[22:07] <MTecknology> then next week I'll become motu! :D
[22:07] <MTecknology> :P
[22:07] <postalchris> I need a reviewer for http://revu.ubuntuwire.com/p/cvc3 (the CVC3 theorem prover)
[22:07] <oojah> I just did a package with an init.d script in - turns out it was quite straightforward.
[22:08] <MTecknology> oojah: how do you do that?
[22:08] <MTecknology> I'll still want the man page but that could be nice
[22:09] <sbalneav> Humph.  Got a bit of a pickle.  I'm both upstream for sabayon, and the packager here in Ubuntu.  I'd been working on the next upstream release, 2.29.2, and was making the tarballs for testing using that nomenclature.  I now realize I should have tacked on a -prelease or the like.  Anyway, last act before release, I bump the news and readme files, and release on gnome.  So, I'm going to rebuild the package in my ppa using the ups
[22:10] <nigel_nb> oh hey maco :)
[22:12] <alkisg> sbalneav: your message was cut in half, in "So, I'm going to rebuild the package in my ppa using the ups"
[22:13] <maco> nigel_nb: ok so you have a patch that can cleanly apply, and you have $QUILT_PATCHES set to debian/patches ... thats the last thing we did right?
[22:14] <nigel_nb> maco: yep.
[22:14] <nigel_nb> first thing, how long are you gonna be around ;) ?
[22:14] <sbalneav> Hm
[22:14] <maco> nigel_nb: about an hour
[22:14] <sbalneav> Humph.  Got a bit of a pickle.  I'm both upstream for sabayon, and the packager here in Ubuntu.  I'd been working on the next upstream release, 2.29.2, and was making the tarballs for testing using that nomenclature.  I now realize I should have tacked on a -prelease or the like.  Anyway, last act before release, I bump the news and readme files, and release on gnome.  So, I'm going to rebuild the package in my ppa using the ups
[22:15] <nigel_nb> okay, and are you better now?
[22:15] <sbalneav> alkisg: That come through?
[22:15] <alkisg> Nope
[22:15] <maco> nigel_nb: yeah sure
[22:15] <sbalneav> foo
[22:15] <nigel_nb> :)
[22:15] <maco> nigel_nb: cd into the package but not into the debian/ directory
[22:15] <alkisg> sbalneav: send it in 2 parts :)
[22:15] <sbalneav> bbiab
[22:15] <nigel_nb> maco: okay, done
[22:16] <maco> nigel_nb: now we're gonna play with quilt
[22:16] <nigel_nb> maco: why do I have a feeling that its not exactly going to be a game ;)
[22:16] <maco> nigel_nb: quilt is a patch management system. when you type "quilt push" it applies the first patch in the debian/patches/series file. if you do "quilt push -a" it does them all in order
[22:16] <maco> nigel_nb: so "quilt push -a"
[22:17] <nigel_nb> maco: bah, not installed
[22:17] <maco> oh. right. install it
[22:17] <nigel_nb> maco: 50%
[22:18] <nigel_nb> No patch in series
[22:19] <maco> nigel_nb: oh right. that package doesnt have any patches yet
[22:19] <maco> nigel_nb: ok that was just theory for if there were patches already there :)
[22:19] <nigel_nb> maco: ah :)
[22:19] <maco> nigel_nb: quilt import ../whateveryourpatchisnamed
[22:19] <maco> guess what that does?
[22:20] <nigel_nb> copies to that folder
[22:20] <maco> and...?
[22:20] <nigel_nb> creates a rev?
[22:20] <maco> i think it adds it to the series file as well
[22:20] <nigel_nb> technically thats wat a rev is right?
[22:21] <nigel_nb> sorry, got used to bzr tooo much working with uclp
[22:21] <maco> hehe series is just a file listing what order to apply teh patches
[22:21] <nigel_nb> oh, so this file gets added as first :)
[22:21] <maco> so now "quilt refresh" should work i think (another "quilt push" before it might be necessary. not sure. been a while)
[22:22] <maco> right
[22:22] <nigel_nb> refresh was not enough
[22:22] <nigel_nb> did a push
[22:22] <nigel_nb> now at patch network.diff
[22:22] <maco> ok so then push followed by refresh i guess
[22:22] <nigel_nb> Refreshed patch network.diff
[22:22] <maco> great
[22:24] <maco> we're supposed to add tags to the top of diffs. this is the long explanation from debian http://dep.debian.net/deps/dep3/ which i havent yet read because ubuntu just switched to it, so uh...lets go read that
[22:25] <maco> ok so it looks like you want "# Bug-Ubuntu 12345" (whatever the bug number is we're working on. i forget now
[22:26] <nigel_nb> will get it
[22:27] <nigel_nb> ugg, my logs dont go that back
[22:27] <maco> it was on harvest. lemme look
[22:28] <postalchris>  I need a reviewer for http://revu.ubuntuwire.com/p/cvc3 (the CVC3 theorem prover)
[22:28] <nigel_nb> bug 351509
[22:30] <nigel_nb> maco: got it
[22:30] <maco> ah yay
[22:31] <nigel_nb> irc logs :)
[22:34] <maco> nigel_nb: so i think something like http://paste.ubuntu.com/337603/ is what you want for the patch tags, based on that webpage
[22:34] <maco> so just edit debian/patches/network.diff
[22:35] <nigel_nb> what does the other stand for?
[22:35] <maco> debian page says: In general, a user-created patch grabbed in a BTS should be categorized as “other”.
[22:35] <maco> so im just going with it
[22:36] <nigel_nb> okay
[22:36] <nigel_nb> it just needs to be commented?
[22:36] <maco> the webpage says its not necessary, so i guess not
[22:37] <maco> see what happens when you run "quilt pop -a ; quilt push -a"
[22:37] <nigel_nb> no i meant where do I put it?
[22:38] <maco> at the top of the debian/patches/network.diff
[22:39] <nigel_nb> its supposed to be green
[22:39] <nigel_nb> ?
[22:40] <nigel_nb> maco: I text added stays black, is that okay?
[22:40] <nigel_nb> s/I/The
[22:45] <maco> im not sure. ive never used debian's way of tagging before. its a recent switch, like i said before
[22:45] <maco> try it plain and see if quilt's happy with it, and if its not, put "# " in front of each of those lines
[22:46] <nigel_nb> okay
[22:46] <nigel_nb> maco: quilt is okay with it
[22:47] <nigel_nb> so we just removed the patch and reapplied, right?
[22:47] <maco> yep
[22:47] <maco> ok so now "dch -i" and give your package a changelog entry
[22:47] <maco> you'll want to say that you added that patch, what it's for, and the bug it closes. for the last bit (LP: #351509)  needs to be in your changelog entry
[22:50] <nigel_nb> "New patch, allows the user to specify which virtual network the built VM is connected to; LP: #351509" works?
[22:51] <maco> http://paste.ubuntu.com/337614/
[22:51] <maco> might need a linebreak in there somwhere if its too long. shouldnt go past 80char
[22:52] <maco> so that way you say exactly which patch you added
[22:52] <maco> and if you had more than one patch going in, you could say this patch did ___ and this patch did ___ and this other patch did ___
[22:52] <nigel_nb> is there a standard format?
[22:53] <maco> the way in the pastebin is how i normally see it when there's a patch being added
[22:53] <nigel_nb> oh okay :)
[22:53] <maco> so you list each patch with * and then list what each patch does under it and indented with a -
[22:54] <maco> and is your name and email address at the end of the changelog entry correct? if not, fix that
[22:54] <maco> you want it to be an email address that you use on launchpad
[22:54] <nigel_nb> it is
[22:54] <maco> so itll show up as one of your uploads on your launchpad page :)
[22:54] <nigel_nb> ah :)
[22:54] <nigel_nb> I use only 1 email, more spam, less complications
[22:55] <maco> and what version number does it say for the package version? the top line of the changelog
[22:55] <nigel_nb> oops
[22:55] <nigel_nb> closed the file
[22:55] <maco> it's debian/changelog
[22:55] <maco> just open it in a text editor
[22:55] <postalchris> I need a reviewer for http://revu.ubuntuwire.com/p/cvc3 (the CVC3 theorem prover)
[22:55] <nigel_nb> (0.11.3-0ubuntu2) karmic; urgency=low
[22:55] <maco> (dch -i is nice because it inserts the little template for it)
[22:56] <nigel_nb> I know from daniel's video
[22:56] <maco> everything goes through the development version first, so you want to change karmic to lucid
[22:56] <maco> oh right :)
[22:56] <nigel_nb> oh, wait a min
[22:56] <nigel_nb> I have to boot into vm and do the whole thing again?
[22:57] <maco> no
[22:57] <nigel_nb> okay, thats a relief
[22:57] <maco> you're just going to generate a source package now
[22:57] <maco> so "debuild -S"
[22:57] <nigel_nb> with debuild and I can say lucid
[22:57] <maco> though right
[22:57] <maco> rihgt
[22:58] <maco> and then you can run "debdiff vm-builder_0.11.3-0ubuntu1.dsc vm-builder_0.11.3-0ubuntu2.dsc > vm-builder_0.11.3-0ubuntu2.debdiff" to get a debdiff, which you then attach to the bug and subscribe ubuntu-universe-sponsors
[22:59] <nigel_nb> okay, hold on
[22:59] <maco> really, you should test building it in a pbuilder before attaching it to the bug, but generating a pbuilder takes longer than the time i have remaining before i leave for class, and ill test it anyway before i sponsor it
[22:59] <maco> (dont worry about subscribing sponsors in this case since ill take it)
[23:00] <nigel_nb> maco: :) you rock
[23:01] <nigel_nb> maco: got the debdiff
[23:01] <nigel_nb> attaching to bug
[23:02] <nigel_nb> any comments I should be adding?
[23:02] <maco> eh not really
[23:03] <nigel_nb> got used to doing it bugs :P
[23:04] <nigel_nb> maco: done :)
[23:04] <nigel_nb> yaay :)
[23:04] <maco> nigel_nb: ok. ill head to class now and upload it from there
[23:04] <maco> thank you for your contribution :)
[23:04] <nigel_nb> maco: thanks a lot for helping me learn
[23:04] <nigel_nb> though I have this package that I'd like to see added
[23:04] <nigel_nb> we'll talk about it later
[23:05] <nigel_nb> I need to get back to screencasts for user days ;)
[23:05] <maco> no problem :)
[23:32] <maco> nigel_nb: look at https://edge.launchpad.net/ubuntu/lucid
[23:32] <nigel_nb> maco: wow!
[23:32] <maco> :)
[23:33] <nigel_nb> maco: thank you :)
[23:33] <nigel_nb> if we ever are in the same city I'm buying dinner :P
[23:33] <maco> nigel_nb: see also https://edge.launchpad.net/~nigelbabu/+related-software
[23:35] <nigel_nb> maco: u built it and checked?
[23:35] <maco> nigel_nb: yeah it built here on i386 at least
[23:36] <nigel_nb> maco: ok, doesn't it get tested on launchpad?
[23:36] <dtchen> if by "tested" you mean "built", yes
[23:36] <maco> launchpad does the build that ends up in the archive
[23:36] <dtchen> so if it fails, your "test" fails
[23:36] <maco> uploading packages that dont build is bad form though
[23:37] <dtchen> it's also a really good idea to use puiparts on the pbuilt/sbuilt debs
[23:37] <dtchen> sigh, piuparts
[23:37] <maco> and dtchen can tell you about uploading packages that prevent everything else from building... ;)
[23:37] <maco> dtchen: this is what happens when you pronounce it the way you do!
[23:37] <dtchen> no, it's muscle memory thanks to dvora
[23:38] <maco> i and u are reversed on dvorak?
[23:38] <dtchen> huh? no.
[23:38] <dtchen> (what does that have to do with muscle memory?)
[23:38] <nigel_nb> oh, you use dvorak?
[23:38] <nigel_nb> dtchen: probably she's pulling your leg
[23:39] <dtchen> dvorak, colemak, qwerty, whatever's set in front of me
[23:39] <maco> you hit the i where you meant u and the u where you meant i....
[23:39] <dtchen> I keep omitting consonants
[23:39] <nigel_nb> i and u are vowels :P
[23:39] <dtchen> 'k' isn't
[23:39] <nigel_nb> no, but the comment had to with I and U ;)
[23:40] <dtchen> when you switch keymaps on-the-fly like I do, it can be interesting
[23:41] <nigel_nb> yea, probably :)
[23:41] <nigel_nb> I've never used anything apart from qwerty
[23:41] <nigel_nb> or seen
[23:52] <maco> nigel_nb: done building
[23:54] <nigel_nb> maco: where do I see that?
[23:54] <maco> nigel_nb: on the related software link for you, you can click on the package version number and itll show information about that upload
[23:54] <maco> itll take you to https://edge.launchpad.net/ubuntu/+source/vm-builder/0.11.3-0ubuntu2
[23:55] <nigel_nb> maco: so now its built for i386?
[23:56] <maco> yes, and its python, so thats the only platform on which it needs to build
[23:56] <nigel_nb> ah :)
[23:56] <nigel_nb> grr, I feel so shy
[23:56] <maco> aw, why?
[23:56] <maco> we're friendly here!
[23:56] <nigel_nb> oops
[23:56] <nigel_nb> wrong channel
[23:57] <nigel_nb> and you'll see why soon enough