[00:01] <sagaci> just mute the audio if you do
[01:38] <soc> hi
[01:38] <soc> anyone from the openjdk ppa online?
[01:38] <soc> i already tried it pn ubuntu-java, but there isn't to much happening in that channel
[01:39] <soc> there is a probelm with all the openjdk-7-* packages
[01:39] <soc> the "conflicts" version is bigger than the version of the deb itself
[01:39] <soc> and is therefore not installable
[02:27] <mase_wk> hey guys, i am trying to build a debian package using dpkg-deb -b dir however it complains that there is no DEBIAN/control file....there is a debian/control file however and all of the examples on packaging so far have indicated that the dir should be /debian not DEBIAN
[02:27] <mase_wk> the package builds with sbuilder ok
[03:20] <TheMuso> c
[06:34] <Rcart> hello. For a python CLI program, it's enough just to add 'python' to the Build-Depends and Depends ({python:Depends}) fields in debian/control file?
[07:25] <udienz> Rcart, not sure, but namy package put python-minimal
[07:28] <Rcart> udienz: i was watching the emesene control file, and just put 'python' in the Build-Depends and '{python: Depends}' in the Depends field
[08:42] <dholbach> good morning
[10:05] <ari-tczew> dholbach: I changed natty to UNRELEASED because this one wasn't uploaded to archive.
[10:07] <dholbach> ari-tczew, ah ok
[10:08] <ari-tczew> ScottK: ping
[10:22] <iulian> Morning dholbach.  Did you manage to wake up? :)
[10:40] <dholbach> iulian, somehow I did, yes - after 11h of sleep I'm still tired
[10:42] <ari-tczew> dholbach: This had to be a really good party
[10:42] <dholbach> ari-tczew, it was jetlag, not the party :)
[10:43] <ari-tczew> dholbach: aaaaaaaaa
[10:53] <iulian> dholbach: Heh, yea, I know the feeling.
[10:55] <dholbach> iulian, I'm back home again, the sun's shining, all's good - so I'm not complaining :)
[11:03] <iulian> dholbach: Uh, I miss the sun.  It has been raining here for a few days now.  It's horrible when I have to go out.
[11:03] <iulian> dholbach: Also, it's veyr windy, so brollies are useless.
[11:04] <Laney> I swear Orlando was the last time I saw sun
[11:04] <dholbach> iulian, luckily it didn't rain too much wherever I was
[11:05] <mok0> We have sun... sorta
[11:06]  * Laney weeps at ghc6
[11:06] <Laney> please, please just build on armel :'(
[11:06] <mok0> Laney, you need to be tough. Gcc doesn't respect a man who cries
[11:07] <iulian> Good point. :)
[12:10] <ricotz> coolbhavi, hello
[12:11] <coolbhavi> ricotz, I am on it just back from outside :) just 5 minutes
[12:11] <coolbhavi> :)
[12:11] <ricotz> coolbhavi, alright, no worries
[12:11] <ari-tczew> !patience | ricotz
[12:12] <ricotz> coolbhavi, could you also look at the libgcrypt11 merge?
[12:12] <coolbhavi> ricotz, m not a core dev so no
[12:12] <ari-tczew> ricotz: once I had a situation, when I taken one merge and contributor had to wait 3 days for my response since status In Progress
[12:13] <ari-tczew> ricotz: I'll look, I had a quick review this one in Friday
[12:13] <ricotz> coolbhavi, ok, but you merged it the last time, i also asked cjwatson and he also declined to look at it :(
[12:14] <udienz> thanks coolbhavi and ari-tczew
[12:14] <ricotz> ari-tczew, ok, feel free to look at it, thanks
[12:14] <coolbhavi> ricotz, no problems my merges are always free to take
[12:16] <ricotz> coolbhavi, ok
[12:18] <ari-tczew> coolbhavi: I'm interested in your merges in main :>
[12:18] <coolbhavi> ari-tczew, as I said my merges are free to take mate anytime
[12:31] <ari-tczew> ricotz: do you looking for free merges?
[12:33] <udienz> ricotz, bug 692457, feel free to take it. i will looking others
[12:34] <ari-tczew> ricotz, udienz: in universe we have some packages commented as 'Feel free to take'
[12:34] <ari-tczew> I encourage to get them.
[12:35] <ricotz> ari-tczew, udienz , actually i am not really looking for merges, libgcrypt11 just came into my way
[12:37] <ari-tczew> ricotz: ok understood.
[12:38] <ricotz> ari-tczew, sorry
[13:36] <ari-tczew> ricotz: I reviewed your patch.
[13:49] <bdrung> dholbach: the .css files on http://reports.qa.ubuntu.com/reports/sponsoring/ are whitelisted now for easylist in adblock-plus
[14:32] <ari-tczew> siretart: ping
[14:41] <ScottK> ari-tczew: pong
[14:45] <ari-tczew> ScottK: I have a proposed fix for FTBFS on armel and sparc in lucid. could you test it on your machine?
[14:46] <ScottK> ari-tczew: I wouldn't worry about sparc, but I can probably test armel.
[14:46] <ScottK> ari-tczew: Sparc in lucid doesn't run so there's no point in worrying about it at all.
[14:47] <ari-tczew> ScottK: the change should works for both
[14:47] <ScottK> OK.  Where's the diff?
[14:50] <ari-tczew> ScottK: http://people.ubuntu.com/~ari-tczew/clementine/fix_ftbfs_on_armel_lucid.debdiff
[14:50] <ari-tczew> ScottK: If it will built succeful, you could also upload it :)
[14:51] <ScottK> ari-tczew: Why is this a correct fix?
[14:51] <ari-tczew> or no, I'm rushing on other topic
[14:51] <ari-tczew> ScottK: upstream proposed.
[14:51] <ScottK> But it's not needed on Maverick or Natty?
[14:52] <ari-tczew> ScottK: maverick and natty built armel fine
[14:52] <ScottK> BTW, it'll be a bit as I have to create a Lucid chroot.
[14:52] <ScottK> Right, so why is Lucid different?
[14:52] <ari-tczew> ScottK: toolchain is different
[16:25] <bcurtiswx_> Whats the proper patch editing technique with quilt
[16:25] <bcurtiswx_> push the patch to be edited to top
[16:25] <bcurtiswx_> then quilt edit (file)
[16:25] <bcurtiswx_> then quilt refresh
[16:25] <bcurtiswx_> anything else?
[16:28] <tumbleweed> bcurtiswx_: http://dep.debian.net/deps/dep3/
[16:32] <bcurtiswx_> tumbleweed, i don't see how that answers my question.. sorry
[16:33] <Bachstelze> bcurtiswx_: yes
[16:34] <bcurtiswx_> Bachstelze, so yes means thats all.. or what else is there?
[16:35] <Bachstelze> that should do
[16:36] <Bachstelze> unless you're modifying a file that is not yet in the patch, then you would do a quilt add
[16:36] <tumbleweed> Bachstelze: quilt edit will add it for you if necessary
[16:38] <bdrung> tumbleweed: i am looking at the byteprefix man page. it's what i wanted. thanks. some things can be improved. 1) the three options can have some examples. e.g. like on https://wiki.ubuntu.com/UnitsPolicy
[16:40] <bcurtiswx_> Bachstelze, the file was in the patch already but it doesn't seem like it got added.. hmm
[18:08] <ScottK> ari-tczew: Still fails: http://paste.ubuntu.com/555132/
[18:37] <highvoltage> the last version of calibre uploaded to natty is 0.7.32+dfsg-1build1
[18:38] <highvoltage> what should the next upload version be? 0.7.32+dfsg-1build2?
[18:45] <geser> highvoltage: is it a rebuild or did you change something?
[18:45] <highvoltage> geser: made a change to a .desktop file
[18:46] <ebroder> highvoltage: if you made an actual change, it should be 0.7.32+dfsg-1ubuntu1
[18:46] <geser> then 0.7.32+dfsg-1ubuntu1 (-build2 would be in the non-change rebuild case)
[18:46] <ebroder> -NbuildM should only be used if there are no changes from the debian version
[18:46] <ebroder> (the autosync infrastructure considers -NbuildM as being unchanged from debian)
[18:47] <highvoltage> thanks, it didn't feel right without a 1ubuntu1 in there, but 0.7.32+dfsg-1build1-1ubuntu1 didn't look right either :)
[18:58] <bdrung> tumbleweed: got my reply?
[19:14] <tumbleweed> bdrung: was just having supper
[19:15] <bdrung> tumbleweed: and i will have lunch in a few minutes. ;)
[19:15] <tumbleweed> on holiday?
[19:16] <bdrung> tumbleweed: my plan after lunch is to write a README, merge your man page (after addressing the points), and release 0.1
[19:16] <bdrung> tumbleweed: no
[19:17] <bdrung> tumbleweed: why did you thought that?
[19:17] <tumbleweed> I thought we were in the same timezone
[19:18] <bdrung> we are, but i eat to unusual times. ;)
[19:19] <xteejx> Hi all. How do I edit the control file of an already-packaged .deb file to remove the version dependencies?
[19:19] <tumbleweed> bdrung: aah hacker time :)
[19:19] <bdrung> lunch at night, breakfast in the evening...
[19:20] <bdrung> xteejx: why not take the source, edit debian/control, and rebuild the package?
[19:20] <xteejx> I don't have the source, but really need the pkg to work
[19:20] <xteejx> It's not in Ubuntu
[19:20] <tumbleweed> xteejx: how sure are you that it'll work without those dependancies?
[19:20] <xteejx> I'm not at all, but it's worth a try
[19:21] <tumbleweed> dpkg --force-depends ?
[19:21] <xteejx> I only want to remove the strict version restrictions so that it will install
[19:21] <bdrung> xteejx: or extract the deb file, edit DEBIAN/control, and pack again (IIRC with dpkg-source)
[19:21] <bdrung> time for lunch. :)
[19:22] <xteejx> Hmm, the --force-depends option allowed the pkg to install, so will still need to install the deps
[19:24] <xteejx> tumbleweed: I think that's worked, thank you :)
[19:25] <tumbleweed> xteejx: my pleasure for helping you break your system :P
[19:25] <xteejx> tumbleweed:  lmao, actually I'm trying to do a NAND flash of an HTC Kaiser to rid it of windows CE and stick android on it :)
[19:25] <xteejx> so it's a little more complex than you might think ;)
[19:32] <highvoltage> so an update to 0.7.38+dfsg-2 would become 0.7.38+dfsg-2ubuntu1 right?
[19:34] <micahg> highvoltage: in Natty, yes
[19:34] <micahg> highvoltage: are you fixing the calibre FTBFS?
[19:34] <highvoltage> micahg: no, I was just about to find out that it has an FTBFS :)
[19:34] <micahg> highvoltage: should only be on arm
[20:03] <highvoltage> maco: around? I have some gally questions
[20:06] <maco> highvoltage: yep
[20:06] <maco> highvoltage: if its about natty, i know it doesnt work. a step in the build is failing
[20:27] <highvoltage> maco: if I install gally, it also installs python-kde4 that depends on quite a lot of KDE stuff (like kde-pim, aconadi, etc) in Edubuntu that we don't really need there, do you have any suggestions for that? if those depends moved to recommends we could choose to not install those extra packages at build time
[20:27] <highvoltage> maco: but I'm not sure if that would really be appropriate for that package
[20:30] <maco> highvoltage: id ask riddell
[20:31] <maco> highvoltage: though at the moment, i think we should hold off on gally til 11.10
[20:31] <JontheEchidna> I don't think gally would run without python-kde4 present
[20:31] <maco> not enough lessons to make it worth incuding
[20:31] <maco> JontheEchidna: i think it was about the things python-kde4 depends on
[20:32] <JontheEchidna> so it's more about what python-kde4 depends on?
[20:33] <maco> JontheEchidna: yeah. it has a huge depends list.... 37 things
[20:33] <JontheEchidna> It's a monolithic package containing bindings for every single kde library.
[20:34] <maco> most are libraries though. do the libraries depend on their matching apps for some reason?
[20:34] <JontheEchidna> Splitting it up would be quite a project, and we'd want to do that in concert in debian
[20:35] <JontheEchidna> which apps are being installed?
[20:36]  * maco looks at highvoltage for answer
[20:36] <ebroder> JontheEchidna: +1 for splitting up python-kde4 and python-qt4 :)
[20:38] <highvoltage> JontheEchidna: some kdepim stuff, akonadi, and other stuff (I have no idea what libknewstuff is :p)
[20:38] <JontheEchidna> both kdepim and akonadi have both libraries and apps
[20:38] <highvoltage> (sorry my boss is pesting me to update my timesheet for last week so work)
[20:39] <JontheEchidna> libknewstuff is part of kdelibs, which used to be all one monolithic package kdelibs5
[20:39] <JontheEchidna> so it's really not too much more than would have been installed a few releases ago, it just looks like more since it is split up further :P
[20:41] <JontheEchidna> but, yeah.  A split at the python-kde4 level would be required to remedy this issue
[20:47] <highvoltage> JontheEchidna: indeed. that would be ideal really.
[20:58] <bdrung> tumbleweed: "this style uses base units 2 with SI prefixes" this is not 100% correct. the K prefix differs from SI
[21:01] <maco> highvoltage: libknewstuff is something im planning on using to make it so gally can offer to download lesson packs from the net
[21:01] <maco> ya know....once there are lesson packs
[21:03] <tumbleweed> bdrung: r36
[21:03] <highvoltage> maco: heh
[21:03] <bdrung> tumbleweed: it's still "kB" for historic -> "KB"
[21:04] <highvoltage> maco: but there are at least some lessons available right now aren't there?
[21:04] <tumbleweed> bdrung: I can't parse that
[21:04] <bdrung> tumbleweed: historic: "1 KB = 1 024 bytes.", not "1 kB = 1 024 bytes."
[21:04] <maco> highvoltage: a couple ASL ones. someone had volunteered to work on dutch ones but disappeared :-/ atm we have a list of lessons we'd like to have (so there's some direction, not just "sign some words in front of a camera") but...
[21:05] <tumbleweed> bdrung: oh I see
[21:05] <highvoltage> maco: if there are even just a few I'd ideally like to keep it in edubuntu for this release, assuming it runs again in time :)
[21:06] <maco> highvoltage: i'll fix the not building ness by feature freeze ;-) ive just been busy with exams then moving then job hunting, now packing to move again and apartment hunting...
[21:06] <bdrung> tumbleweed: to point 1) yes, i want more. at least giga should fit without wrapping at 80 chars
[21:07] <maco> a few weeks helping mum since she had knee surgery... busy!
[21:08]  * bcurtiswx waves at ms maco
[21:08] <maco> hi bcurtiswx
[21:09] <bcurtiswx> maco, how's the home life?
[21:09]  * maco points at the word busy
[21:09] <highvoltage> maco: yay, cool.
[21:10] <bcurtiswx> maco, sounds just soo much fun.  Well I wish ya the best on your soon to be transition :)
[21:10] <maco> dear online banking: not everything has to be a servlet. you can list the "stuff you can redeem points for" with good ol' html
[21:15] <micahg> maco: think of network overhead as another banking fee
[22:03] <bdrung> tumbleweed: can you review my current README: http://paste.debian.net/104909/ ?
[22:09] <tumbleweed> bdrung: s/setup/set up/ when it's a verb. "libkibi is a library for byte prefixes. It's designed for formatting bytes." - neither of those actually describes what the library does (format sizes for display)
[22:09] <tumbleweed> bdrung: "The
[22:10] <tumbleweed> (whoops) ... byte prefixes are used depending on the user preferences." <- clumsy. I'd use something like "The user can configure a preferred prefix style."
[22:10] <bdrung> yes, that sounds better
[22:12] <tumbleweed> Input Functions could probably use some brief explanation too. That's all I can see.
[22:12] <bdrung> tumbleweed: http://paste.debian.net/104910/
[22:12] <bdrung> tumbleweed: yes, i was interrupted by your branch :)
[22:13] <tumbleweed> "formatting bytes" still doesn't quite sound right, "sizes in bytes" ?
[22:14] <bdrung> -> formatting sizes in bytes
[22:14] <tumbleweed> yeah. oh another one: "format sizes for outputting them" -> "format sizes for output"
[22:16] <bdrung> tumbleweed: http://paste.debian.net/104911/
[22:18] <tumbleweed> "These functions can be used for converting bytes into the unit in which the user could edit them" <- don't understand that. "user could edit them" ? Also "converting bytes"? Sounds like converting raw data
[22:19] <bdrung> tumbleweed: example: a user wants to set a bandwith limit in transmission in "kB/s" or "KiB/s". the size needs to be converted from bytes into kB/KiB and then back again.
[22:21] <bdrung> tumbleweed: one last this with the man page: "(1 K = 10^3 = 1 000) and base 2 (1 K = 2^10 = 1 024)". to what does the "1K" refer to? shouldn't the first "1K" be a small "1k"?
[22:22] <tumbleweed> "for converting between sizes with units (for example to allow a user to edit a value in KB/s)"?
[22:23] <tumbleweed> I was just using k as an example of order of magnitude (first order), yes having the first one bing a "k" probably makes sense
[22:25] <bdrung> tumbleweed: dropping the "1k =" would be ok too. "base 10 (10^3 = 1000) and base 2 (2^10 = 1024).
[22:25] <bdrung> "
[22:25] <tumbleweed> I think it's clearer to keep it
[22:25] <bdrung> k
[22:25] <tumbleweed> heh
[22:26] <bdrung> the word "k" is overloaded :)
[22:30] <bdrung> tumbleweed: http://paste.debian.net/104916/
[22:32] <tumbleweed> bdrung: LGTM
[22:32] <bdrung> tumbleweed: did i forget something that should be in the readme?
[22:33] <tumbleweed> maybe one sentance about the lincence?
[22:39] <bdrung> tumbleweed: http://paste.debian.net/104917/
[22:39] <bdrung> with new "Developing libkibi" section
[22:42] <tumbleweed> LGTM
[22:43] <bdrung> tumbleweed: man page merged. thanks.
[22:47] <tumbleweed> np
[22:51] <bdrung> tumbleweed: pushed. is there something left that i should do before the release?
[22:53] <tumbleweed> bdrung: can't think of anything. BTW how do you intend to handle the byteprefix manpage? separate -doc package?
[22:53] <bdrung> tumbleweed: i put it into libkibi0
[22:53] <tumbleweed> that would then conflict if you had an ABI bump
[22:54] <bdrung> right. so i have to add a -doc package
[22:54] <tumbleweed> I guess so, I don't know how this is usually done
[22:55] <bdrung> tumbleweed: should libkibi0 recommend the -doc package?
[22:56] <tumbleweed> yeah, that sounsd good
[23:01] <bdrung> tumbleweed: what do you think about naming it libkibi-man instead of libkibi-doc (the latter could be false judged as library documentation for the programmer)
[23:04] <tumbleweed> bdrung: sounds good, and I see gss does that
[23:04] <tumbleweed> (oh whoops, that *is* API)
[23:09] <ari-tczew> ScottK: have you got an idea how to fix it?
[23:09] <bdrung> tumbleweed: can you review lp:~libkibi-dev/libkibi/packaging ?
[23:19] <tumbleweed> bdrung: I'd add a .bzr-builddeb so it knows the package uses merge mode. debian/copyright needs a new entry :). -dbg package?
[23:20] <tumbleweed> bdrung: looks like I broke something: "config.status: error: cannot find input file: `doc/Makefile.in'"
[23:20] <bdrung> tumbleweed: you have to run "make dist" to create the source tarball. merging the bzr branch doesn't work.
[23:25] <bdrung> tumbleweed: pushed. should i really add a -dbg package?
[23:25] <tumbleweed> bdrung: ah, thanks. Debian doesn't have ddebs (yet?), so I normally do them.
[23:26] <cody-somerville> Is a watchfile considered important enough these days to maintain a delta against Debian? I know there was a big push to add watch files a year or two ago.
[23:27] <micahg> cody-somerville: I suggest adding it and then using submittodebian
[23:28] <bdrung> cody-somerville: I think that it can be dropped if you file a bug against the debian package.
[23:28]  * tumbleweed would probably not sponsor an upload that just added a watchfile
[23:29] <cody-somerville> Yea. I'm thinking I'd accept the sync request instead of insisting they prepare an upload - especially since the watchfile wasn't even in the list of the remaining changes against Debian.
[23:30] <tumbleweed> yeah, (but obviously get it filed :)
[23:31] <micahg> ah, yeah, actually, there's no reason, AFAICT, there's no tool using just the Ubuntu watch files
[23:32] <bdrung> micahg: uscan?
[23:32] <micahg> bdrung: I meant that has a report
[23:32] <tumbleweed> micahg: doesn't LP now display "new upstream version" messages on source package pages?
[23:33] <bdrung> tumbleweed: pushed with -dbg package.
[23:33] <micahg> tumbleweed: is that based on the watch file or on the actual upstream in LP
[23:34] <bdrung> micahg: i assume that it's based on the actual upstream in LP
[23:36] <tumbleweed> aah right. There is of course UEHS
[23:37] <bdrung> tumbleweed: ready to release or did you find anything?
[23:38] <micahg> tumbleweed: right, which I was thinking of before, but AFAICT, that's for Ubuntu specific stuff
[23:39] <tumbleweed> bdrung: no issues I can see. ACK.
[23:39] <bdrung> tumbleweed: should i install the README file?
[23:40] <tumbleweed> bdrung: possibly in -dev, you don't have any other API documentation besides the header
[23:40] <tumbleweed> micahg: yeah