[01:19] <jrwren> hello, i'm trying to backport the oneric netatalk package to natty and hopefully move both to 2.2.0 final, but it does not build on natty for me. it only builds on oneric. Any C dev care to take a look?
[02:16] <poolie> jrwren: pastebin the failure
[02:16] <poolie> please
[02:19] <jrwren> http://paste.mitechie.com/show/369/
[02:19] <jrwren> but I look at that c code and the array literal looks good and complete and matches the struct definition
[02:48] <poolie> huh
[02:48] <poolie> i'd guess it's a version incompatibility between the C file and whichever header provides that struct
[02:48] <poolie> or type
[04:53] <lifeless> slangasek: https://code.launchpad.net/~lifeless/ubuntu/oneiric/apt/bug-816606/+merge/70250
[04:53] <lifeless> hah, terrible parsing there ubottu
[05:16] <infinity> lifeless: Depending on a keyring seems like the wrong direction to go to fix that, no?
[05:17] <lifeless> infinity: I talked it over with slangasek a few days aback
[05:17] <lifeless> infinity: e.g. not calling it would be sensible too :) - or handling the error
[05:18] <lifeless> infinity: he suggested that as debian hard depend, hard depending was simpler and consistent.
[05:18] <lifeless> infinity: in this very channel
[05:18] <infinity> lifeless: Oh, I agree it's consistent, I also would call both "wrong".  But whatever, the keyring packages aren't huge.
[05:19] <lifeless> infinity: I'm more worried about apt-key failing if someone has no internets.
[05:19] <didrocks> good morning
[05:21] <StevenK> lifeless: Or living in NZ.
[05:21] <StevenK> Which is much the same thing.
[05:22] <infinity> lifeless: (Out of curiosity, what as actually failing without a keyring installed?)
[05:22] <infinity> s/as/is/
[05:23] <lifeless> infinity: apt post-inst
[05:23] <lifeless> infinity: e.g. in debootstrap
[05:23] <infinity> lifeless: apt's postinst has all the keyring ops guarded.
[05:24] <infinity> lifeless: Hence my question...
[05:24] <lifeless> infinity: and yet
[05:24] <lifeless> Setting up apt (0.8.15.4ubuntu2) ...
[05:24] <lifeless> ERROR: Can't find the archive-keyring
[05:24] <lifeless> Is the ubuntu-keyring package installed?
[05:24] <lifeless> dpkg: error processing apt (--configure):
[05:24] <lifeless>  subprocess installed post-installation script returned error exit status 1
[05:25] <infinity> lifeless: I'm looking at the postinst for 0.8.15.1ubuntu2, maybe someone removed the || true...
[05:26]  * infinity upgrades.
[05:26] <lifeless> remove the keyring first :P
[05:28] <infinity> Yeah, someone removed the || true...
[05:28] <infinity> Very confused.
[05:31] <infinity> Meh, whatever.  The dependency doesn't bug me that much.
[05:32] <lifeless> I'm happy to propose ||true instead
[05:35] <lifeless> I've requested a debdiff from https://launchpad.net/ubuntu/oneiric/+localpackagediffs?field.name_filter=apt&field.package_type=ignored&field.package_type-empty-marker=1
[05:35] <lifeless> to poke at the overall delta
[05:36] <infinity> Well, someone rewrote that part of postinst entirely and broke it...
[05:36] <infinity> There used to be a bit that tested for /etc/apt/trusted.gpg and copied /usr/share/apt/ubuntu-archive.gpg in place if you didn't have one.
[05:37] <infinity> And /usr/share/apt/ubuntu-archive.gpg is from apt, not a keyring package.
[05:37] <infinity> And then apt-key update was guarded with a true for extra paranoia, I guess.
[05:37] <infinity> Ultimately, if people want to use apt without keyrings, I imagine we should let 'em.
[05:39] <lifeless> what priority would you say the bug is ? (given it breaks debootstrapping ..)
[05:39] <infinity> The current issue?  high/critical.
[05:40] <infinity> And fixing it with a hard dependency to match Debian is more than fine for now.
[05:40] <infinity> I just don't want to lose focus on "maybe this should get a second look".
[05:40] <lifeless> I have to run out for a bit; the mp is up - I can't land (not core-dev)
[05:40] <infinity> I can do it after breakfast.
[05:40] <lifeless> awesome
[05:40] <lifeless> though, EWHATTZAREYOUMAD? occurs to me
[05:41] <infinity> I'm in Cambridge.
[05:41] <lifeless> oh cool
[05:41] <lifeless> verra nice, if you stay out of the hotels :P
[05:42] <infinity> It would be nicer if it was Cambridge proper, and not Cambourne.
[05:42] <infinity> But whatever.
[05:45] <RAOF> Which archive admin wants to be a hero and unbreak nvidia (among other binary drivers) by performing the sync requested by bug #811231?  Fabulous prizes await!
[05:46] <infinity> RAOF: Can you elaborate on the prizes?
[05:47] <RAOF> infinity: People stop bitching about nvidia being broken!
[05:47] <infinity> RAOF: They're not bitching to me, though...
[05:48] <StevenK> That can be fixed.
[05:48]  * infinity fires up the syncinator anyway.
[05:48] <RAOF> infinity: I can cause X to randomly hang for you, if you like :)
[05:50] <infinity> RAOF: Do it in a way that's both undetectably targetted at me and doesn't effect others, and I'll be impressed.
[06:05] <infinity> RAOF: Blacklist removed, sync away.
[06:09] <RAOF> Woot!
[07:38] <lifeless> infinity: thanks
[10:43] <jamespage> morning; please could an AA accept the NEW binary packages for stapler, activemq-protobuf, felix-shell-tui and activemq-activeio into oneiric - thanks
[12:41] <kelemengabor> hi, is there any evoution-indicator developer around who could take a look at bug 437963 ?
[12:50] <jrwren> poolie: the header that defines that struct is also part of netatalk. it builds on oneric, but not natty. its very strange.
[15:06] <seb128> ev: is usb-creator supposed to work in oneiric? out of raising and exception when formating usb sticks it fails to record the boot loader there
[15:06] <ev> it is supposed to work, yes
[15:06] <ev> bug please
[15:07] <seb128> ok
[15:07] <seb128> bug #806611 is the formating one
[15:07] <seb128> same error at least
[15:07] <seb128> ev: what info would be useful for the boot loader error?
[15:07] <seb128> let me try to see if it prints something on stdout to start
[15:07] <ev> ~/.cache/usbcreator.log if memory serves
[15:09] <seb128> ev: ok, thanks, that was helpful, it's an issue on my session
[15:09] <seb128> ev: DBusException: org.freedesktop.DBus.Python.dbus.exceptions.DBusException: com.ubuntu.USBCreator.Error.NotAuthorized
[15:09] <ev> ah
[15:09] <seb128> ev: which in fact is "the polkit service is not running"
[15:10] <ev> that'll do it :)
[15:10] <seb128> ev: thanks! ;-)
[15:10] <ev> sure thing
[15:17] <cnd> slangasek, do you know of news on the new arm build architecture?
[15:17] <cnd> how long before we can build armel packages in our ppas
[15:30] <ojap> hi, where is the best place to find someone who can help me fix my first bug in ubuntu?
[15:42] <and`> ojap, what's that about?
[15:45] <ojap> and`: looking to fix first bug in ubuntu and wondering whether there are any specific places where I can get guidance from an experienced developer
[15:46] <and`> ojap, I would suggest you to open a bug in Launchpad and provide there all the details
[15:46] <and`> ojap, if it's packaging-related, feel free to move to #ubuntu-motu
[15:48] <ojap> and`: I don't have a bug I want to report, I want to contribute code to existing bugs. Just wondering whether there is help available to guide me in finding suitable bugs, learning how to branch the code, etc.
[15:49] <and`> ojap, add your patches to the bug reports and they'll be reviewed and eventually uploaded.
[15:49] <jbicha> ojap: see http://harvest.ubuntu.com/
[15:49] <jbicha> and https://wiki.ubuntu.com/Bugs/HowToFix
[15:49] <and`> jbicha, thanks :)
[15:49] <jbicha> or http://developer.ubuntu.com/packaging/html/ but it's still a work-in-progress
[15:50] <jbicha> yes, please ask if you can't find anywhere to contribute, I'm sure we can find something you can do :-)
[15:54] <ojap> thanks, I have read those links before and they are great. At the moment I am just trying to find the right bug that is suitable and that I have a chance of understanding and fixing
[15:59] <ojap> jbicha: any suggestions before a beginner like me would be great, thanks
[16:00] <jbicha> ojap: how much of a programmer are you and what software do you like to use?
[16:06] <ojap> jbicha: i'm a student programmer and have fair experience with languages like java, c++ and web languages.
[16:07] <jpds> ojap: Find a program you like, and work from there.
[16:08] <jbicha> exactly, it's more rewarding to fix bugs in software you use
[16:08] <jbicha> either use harvest or just look at the launchpad bugs page for something interesting
[16:10] <jbicha> harvest lets you look for bitesize bugs which should be relatively simple to fix to get you started
[16:18] <ojap> jbicha: thanks, have been looking through harvest and launchpad, alot of the bugs in harvest already have people working on them and finding the right bug in launchpad can take time. i'll keep looking though
[16:19] <jbicha> ojap: I reported bug 820058 yesterday and it should be a very easy fix
[16:20] <jbicha> just to get you used to checking out the source code, finding where to fix it and then getting that fix into Ubuntu
[16:26] <ojap> jbicha: that looks really great, thanks.  how the will the source code appear on my machine? (sorry if that sounds stupid!)
[16:28] <jbicha> in this case I believe the correct source can be found at https://launchpad.net/ubiquity
[16:28] <jbicha> so you would run bzr branch lp:ubiquity to download the source
[16:29] <micahg> jbicha: I thought the slideshow is a separate source
[16:30] <jbicha> yes, sorry about that, try bzr branch lp:ubuntu/ubiquity-slideshow-ubuntu
[16:31] <ojap> no probs, thanks really useful
[16:34] <ojap> jbicha: thanks, seeing "Branched 35 revision(s)." in terminal - could I be a pain and ask for some guidance for the next couple of stages?
[16:38] <jbicha> well you've got the sourcecode right there, and it's plain text so you just look around for "Welcome to Ubuntu 11.04"
[16:39] <jbicha> rgrep is a shortcut but you don't need it
[16:39] <ojap> jbicha: yeah great, found the welcome.html - thanks again
[16:41] <jbicha> and then if you go back to the top directory of the source code, you can run dch -e to add a changelog entry describing
[16:41] <jbicha> what you did
[16:42] <jbicha> sorry, dch -i
[16:43] <jbicha> dch -i adds a new entry, dch -e edits the entry after you've already made it
[16:45] <ojap> jbicha: while I am changing the text, I'm guessing the pictures also be updated for oneiric?
[16:47] <jbicha> you don't have to worry about the pictures, they need to be updated but you'll want to talk to whoever did that for natty
[16:47] <jbicha> if you want to do that
[16:48] <jbicha> because we're the upstream for the slideshow, you need to make the sure that the version number is just 41 not the .0ubuntu1 stuff
[16:48] <jbicha> in the changelog which is actually stored in debian/changelog by the way
[16:49] <jbicha> actually contributing patches is kinda complicated, there's so many little things to understand, that's part of
[16:49] <jbicha> why the new packaging guide is being written
[16:51] <ojap> jbicha: ok, well I don't know who is responsible for the pictures, so I'll focus on the text. I presume I should also update the slideshows for the kubuntu, etc folders.?
[16:53] <jbicha> yes, if you look at https://code.launchpad.net/ubuntu/+source/ubiquity-slideshow-ubuntu you can look at the source code online and see who has been making changes to it
[16:56] <ojap> ok, seems Evan Dandrea  is responsible
[17:06] <micahg> what do we do with SRU requests for control file description changes?  in theory they could go in if we ever had an SRU for the package, but they don't really qualify on their own
[17:07] <ojap> jbicha: using the dch -i command and have updated changes, how do I get my text saved in the file?
[17:08] <jbicha> ojap: I think you're about ready for the "Committing the fix" stage of https://wiki.ubuntu.com/Bugs/HowToFix
[17:09] <jbicha> but you really need to do https://wiki.ubuntu.com/UbuntuDevelopment/GettingSetUp first if you haven't yet
[17:11] <ScottK> micahg: I'd mark them wontfix with a comment like that.
[17:11] <ojap> jbicha: yeah, completed the getting setup guide
[17:12] <micahg> ScottK: yeah, but then they get closed instead of being in a pending type of queue
[17:12] <ScottK> True.  There is no "Really unlikely to fix" state.
[17:12] <jbicha> ojap: ok then can you commit and push your changes?
[17:13] <ojap> jbicha: I presume that I don't need to test the fix before commit?
[17:13] <jbicha> ojap: you should do that too, I skipped that step because I'm not sure how to test it
[17:13] <micahg> ScottK: this is actually a situation where UDD could shine if we could get proper branches, we could stage a fix like this in case of an SRU
[17:13] <jbicha> bzr bd will build a Ubuntu package for you to install
[17:14] <ScottK> micahg: Perhaps.
[17:15] <jbicha> ojap:  just run ./test-slideshow.sh
[17:16] <ojap> jbicha: thanks again!
[17:27] <ojap> jbicha: thanks for your time and effort, greatly appreciated!
[17:30] <slangasek> cnd: no, I believe that's in IS's hands at this point
[17:30] <cnd> slangasek, ok, thanks
[17:30] <jbicha> ojap: one more thing, in your changelog line add (LP: #820058)
[17:30] <jbicha> this tells launchpad to automatically close the bug when the package is built & released
[17:31] <jbicha> you can debcommit and bzr push again
[17:33] <jbicha> then propose it for merging and subscribe ubuntu-sponsors to the merge request after you submit it
[17:34] <SpamapS> james_w: I have a question about package importing and diverged branches, if you have a moment.
[17:39] <ojap> jbicha: noticed on this page, https://code.launchpad.net/~ojap/ubuntu/oneiric/ubiquity-slideshow-ubuntu/fix-for-820058 the recent revisions does not have a clickable link to my launchpad account, do you know how I can fix this?
[17:43] <ojap> jbicha: found that I put a capital letter in the changelog, don't worry. thanks.
[17:44] <micahg> @pilot in
[18:34] <dpb_> Hello all, is there a policy in ubuntu that packages (during install) not prompt the user and instead just choose sane defaults.  Obviously, running some packages through dpkg-configure will trigger questions, but for the most part when upgrading or installing, I don't see them.  I know when I switched over from debian it was one of the things that stood out to me, but that was a while ago.
[18:44] <jbicha> dpb_: debian policy is ubuntu policy basically
[18:48] <maco> dpb_: i think there's a priority level set to debconf questions and we set a higher priority requirement
[18:49] <dpb_> jbicha, thx, I have heard that as well.
[18:50] <dpb_> maco: Thx, didn't even think about that... let me check into that.  Was there any official docs or decision on the higher policy setting?
[18:50] <jbicha> oh, I misunderstood your question, listen to maco instead
[18:51] <dpb_> jbicha: I wasn't really asking the question very well to begin with. :)
[18:51] <maco> jbicha: there *is* an ubuntu policy manual, btw. i kinda wish it was just a diff, but its actually a rewrite...it adds a "metapackages" Section for debian/control and a few other things like that
[18:51] <maco> dpb_: no idea, i think its been that way longer than ive been around here
[18:52] <dpb_> maco: gotcha. Yeah, I have been using ubuntu for a while and it's something i noticed pretty quickly.
[18:52] <maco> i didnt use debian til after i used ubuntu
[18:53] <ScottK> maco: Actually it is a diff.
[18:54] <maco> ScottK: where?
[18:54] <maco> http://people.canonical.com/~cjwatson/ubuntu-policy/policy.html/  <-- what im thinking of
[18:54] <ScottK> maco: diff debian-policy and ubuntu-policy
[18:54] <maco> *snort*
[18:54] <maco> i mean i think itd be nice if it was actually *displayed* as  diff
[18:55] <maco> "here's a short list of things we do differently:"
[18:57] <ScottK> I feel the same way about the packaging guide.
[18:57] <ScottK> That one is, unfortunately, a rewrite.
[19:00] <dpb_> maco: thx for that, let me get read and get back.  I apprecaite it.
[20:24] <micahg> @pilot out
[21:03] <Adsa> Can you check this out please http://alyshia.myvi.net/opportunity.html
[21:04] <Adsa> Can you check this out please http://alyshia.myvi.net/opportunity.html
[21:06] <broder> !ops
[21:06] <broder> (the link is spam)
[21:06] <Tm_T> he left already
[21:06]  * ajmitch isn't surprised 
[21:06] <broder> oh, didn't notice. bah
[21:06] <ajmitch> still useful to ban for if they try & spam again
[21:07] <Tm_T> well, most likely would try spam with other nick and ip
[21:07] <broder> hmm...is ubottu's list of channel ops up to date?
[21:08] <ion> Any IRC ops here?
[21:15] <Keybuk> (in case he comes back)
[21:18] <broder> thanks, Keybuk
[21:33] <ScottK> broder: I suspect it is.  You might talk with cjwatson when he's around about adding some more since several of the current ones aren't particularly active.
[21:34] <broder> ScottK: does #ubuntu-devel not fall under the irc council's jurisdiction?
[21:34] <ajmitch> that's a tricky one
[21:34] <ScottK> No.
[21:35] <ScottK> AFAIK, IRCC is welcome to help out on devel channels, but they don't run them the same way they do others.
[21:36] <JanC> IRC Council & Freenode Staff can act as ops here
[21:37] <JanC> but that's probably set as a backup
[21:37] <broder> i'm less concerned about ownership than i am about there being people to respond to issues
[21:38] <broder> if IRCC can act as ops, it seems like including them in ubottu's !ops factoid would be fine
[21:39] <JanC> broder: they aren't here necessarily, but you can contact them & Freenode staff in their own channels in case of emergency
[21:42] <JanC> broder: "/msg chanserv access #ubuntu-devel list" will show you the people with "ops" BTW
[21:42] <nhandler> IRCC and freenode staff generally only use their access in cases where named OPs are not present (or occassionally if the user in question is causing namespace/network issues).
[21:44] <JanC> nhandler: that's more or less what I mean by "in case of emergency"
[21:45] <JanC> (this case wasn't one)
[22:10] <lifeless> infinity: should I file a follow-on bug to the apt postinst, for the further discussion?
[22:33] <TheMuso> c
[22:50] <hallyn> udd problem - lp:ubuntu/maverick-updates/libvirt does not exist.  How can I get it created?
[22:50] <hallyn> (lp:ubuntu/lucid-updates/libvirt does exist)
[23:27] <james_w> SpamapS, I have plenty of moments for you, but I'm sprinting this week
[23:27] <james_w> SpamapS, perhaps drop me a mail?
[23:29] <SpamapS> james_w: will do
[23:40] <micahg> hallyn: file a bug against the UDD project?
[23:43] <hallyn> micahg: (looking)
[23:44] <hallyn> micahg: will do, thanks