[00:30] <lifeless> kees: around?
[01:21] <kees> lifeless: in and out, sup?
[01:21] <lifeless> mailed you
[01:21] <kees> okay
[02:33] <bcurtiswx> if i'm trying to start learning GTK+, what program(s) should I install ?
[02:34] <bcurtiswx> is there a good beginners guide out there?
[02:35] <bcurtiswx> nvm about what packages, got that
[02:48] <fagan> bcurtiswx: this isnt a channel for app development its for discussion on developing ubuntu itself
[02:48] <fagan> #ubuntu-app-devel is the one I think for that
[02:57] <bcurtiswx> fagan, muchas gracias
[02:58] <fagan> no problem
[03:43] <bbigras> Someone knows a tutorial to create a DEB when I got an install script provided with the sources?
[03:46] <fagan> bbigras: this isnt a support channel for app development in ubuntu its a channel for developing ubuntu
[03:47] <fagan> you should ask your question on #motu
[03:47] <fagan> or #ubuntu-motu maybe
[03:47] <fagan> I forget
[03:47] <micahg> bbigras: #ubuntu-packaging is more apropriate
[03:47] <fagan> its late
[03:47] <fagan> oh your right I forgot about that one
[03:48] <fagan> well I always asked for help in #motu because theres always someone around
[03:48] <bbigras> thanks but I thought ubuntu developement meant mostly packaging.
[03:49] <micahg> bbigras: yes, but this channel focuses on package in the archive in main or restricted
[03:49] <fagan> and development work going on
[03:49] <bbigras> I see, thanks!
[03:49] <fagan> features and bug fixes
[03:51] <fagan> its interesting how many people come here for development help though even though it says  (not support, not app development) in the title
[07:11] <dholbach> good morning
[08:15] <tjaalton> hum, netgen seems to be missing from lucid, though lp shows the binaries in https://edge.launchpad.net/ubuntu/+source/netgen
[08:16] <tjaalton> maybe it failed to build? the new version was released too late for lucid
[08:17] <tjaalton> I'll just grab it from testing/maverick
[08:18] <geser> tjaalton: FTBFS: https://blueprints.launchpad.net/ubuntu/+spec/foundations-lucid-supportable-binaries
[08:21] <geser> the version in lucid got uploaded in jaunty and as we couldn't build it anymore in lucid (FTBFS in a rebuild test) the binary debs got removed
[08:23] <tjaalton> geser: yeah, makes sense
[08:23] <tjaalton> just that the lp page is confusing then ;)
[08:30] <geser> the source is still in lucid just not the binary debs
[08:32] <tjaalton> yes, but lp shows both for lucid
[08:32] <tjaalton> but, lunch ->
[08:36] <geser> you have to look at the binary publication page: https://edge.launchpad.net/ubuntu/lucid/i386/netgen
[08:48] <wgrant> tjaalton: It shows that the binaries were built. It doesn't say they're published.
[08:54] <tjaalton> wgrant: that conflicts with the removal then
[08:56] <wgrant> tjaalton: Hm?
[09:01] <wgrant> tjaalton: They were still built. They were just removed later.
[09:06] <tjaalton> wgrant: that makes no sense? why were they removed then?
[09:10] <tjaalton> wgrant: my point is that lp should not show the debs if they were removed :)
[09:10] <geser> tjaalton: netgen 4.4-15 got uploaded to jaunty, and later copied (source+binary) to karmic and lucid. During lucid we noticed in a rebuild test that we can't build the package anymore and decided to not publish the binaries anymore (as we can't support them, e.g. security upload or SRU)
[09:11] <cjwatson> they were in the lucid *series* at some point, just not in the 10.04 *release*
[09:12] <geser> LP (or more the librarian) still have them (like other debs for superseded uploads), they just not published anymore (on archive.u.c)
[09:13] <tjaalton> and _that's_ confusing
[09:18] <cjwatson> it's probably best not to go through LP to find what's published in a given release unless you're pretty familiar with it.  you could just use rmadison
[09:20] <tkamppeter> when is the beta freeze supposed to end?
[09:20] <cjwatson> it's ended, just haven't quite reopened the archive yet.
[09:20] <cjwatson> in progress on that
[09:24] <cjwatson> I think I'd like to clear through binutils and eglibc first though
[09:24] <\sh> could someone release the NEW queue for maverick, pls? :)
[09:25] <raphink> \sh: don't you think there's enough packages already? :p
[09:25] <cjwatson> \sh: not the first priority
[09:25] <cjwatson> (yeesh, what is it with day-after-beta and are-we-there-yet?)
[09:26] <cjwatson> james_w`: hmm, I do hope the importer isn't going to get too badly confused with me accepting packages from unapproved during codehosting downtime
[09:26] <\sh> raphink, I'm just interested in one...so we can start testing maverick with FAI ;)
[09:26] <lifeless> cjwatson: does anyone other than pitti know enough about the apport retracers to say if they are fixed or not
[09:26] <raphink> \sh: I'm just kidding ;-)
[09:26] <cjwatson> lifeless: seb128
[09:26] <lifeless> seb128: ping
[09:26] <\sh> raphink, I know :)
[09:26] <seb128> hi
[09:27] <raphink> \sh: have you packaged (DC)² yet?
[09:27] <cjwatson> hm, let me see, those binutils and eglibc uploads don't look like they'll have a significant effect on other packages
[09:28] <seb128> cjwatson, hello
[09:28] <seb128> oh retracers
[09:28] <\sh> raphink, nope...I'm just busy with daily business...the rollout of lucid was postponed because of other urgend company tasks so right now I don't have the time to work fulltime on (DC)²
[09:28] <raphink> who uses these anyway
[09:28] <seb128> yeah, let me just remove the lock and see if they crash or run
[09:28] <raphink> :)
[09:30] <cjwatson> seb128: robert_ancell's folks uploads dropped the changes from version 0.1.14.1-0ubuntu2, which added two build-depends.  I therefore suspect that these uploads will fail to build.  Do you have a way of checking whether this was intentional?
[09:31] <cjwatson> (the dropped upload fixed bug 621423)
[09:31] <seb128> didrocks, ^
[09:31] <StevenK> Hah, I read that sentence the other way the first time
[09:31] <StevenK> "Wha, Robert's parents uploaded something?"
[09:31] <didrocks> seb128: ok, fixing it
[09:32] <seb128> didrocks, did you do an update for it in the ppa?
[09:32] <seb128> cjwatson, didrocks: we might just be able to sync on debian
[09:32] <seb128> they have the new version and this change I think
[09:32] <seb128> didrocks, ^ can you check?
[09:32] <seb128> didrocks, thanks
[09:32] <didrocks> seb128: let me see, upstream made a new revision for the ppa
[09:32] <didrocks> seb128: sure, checking
[09:35] <didrocks> seb128: yeah, they get the change, let me just build it and test it before acking on the sync
[09:40] <netepal> Can somebody guide me how can I contribute to ubuntu
[09:40] <cjwatson> http://wiki.ubuntu.com/ContributeToUbuntu has some notes
[09:40] <cjwatson> very much depends on your interests
[09:40] <netepal> which skill set is needed
[09:41] <cjwatson> all of them! :-)
[09:41] <netepal> meaning which languages are needed?
[09:41] <cjwatson> depending on what you want to do - see that page, it has lots of links
[09:41] <cjwatson> again, it depends
[09:41] <cjwatson> there's no one single language used in Ubuntu development
[09:41] <cjwatson> most of the core system is in C, C++, shell, Perl, Python, in no particular order
[09:42] <cjwatson> but the much more important thing is which language is used in the package(s) you want to work on.  I generally advise people to be flexible
[09:42] <netepal> ok then I can work in C/C++
[09:43] <netepal> are you also a contributor
[09:43] <cjwatson> yes
[09:45] <netepal> how do you contribute
[09:45] <cjwatson> I mainly work on the installer and the boot loader
[09:45] <netepal> ok! cool
[09:45] <didrocks> cjwatson: seems to work well. Can you sync folks from debian experimental? do you want a bug report for the request?
[09:46] <cjwatson> didrocks: I can, please file a bug for it
[09:51] <seb128> dpkg: ../../src/archives.c:809: tarobject: Assertion `r == stab.st_size' failed.
[09:52] <seb128> hum, not nice
[09:52] <cjwatson> do you have the .deb that produced that?
[09:52] <didrocks> cjwatson: when you have some time: bug #629351
[09:53] <seb128> cjwatson, not really, it's a retracer crash when installing gnome-applets
[09:54] <cjwatson> actually, that's kind of a "somebody seems to have changed this symlink between lstat and readlink" assertion
[09:54] <seb128> "Preparing to replace gnome-applets-data 2.30.0-3ubuntu2 (using .../gnome-applets-data_2.30.0-3ubuntu2_all.deb) ...
[09:54] <seb128> Unpacking replacement gnome-applets-data ...
[09:54] <seb128> dpkg: ../../src/archives.c:809: tarobject: Assertion `r == stab.st_size' failed.
[09:54] <seb128> "
[09:54] <cjwatson> or at least that's the way it looks to me
[09:55] <seb128> but retracers are special environments
[09:55] <cjwatson> if it's straceable that might help
[09:55] <cjwatson> quite
[09:56] <seb128> cjwatson, I've logged in and it's not happening with an apt-get install
[09:56] <G> is it just me or are others getting connection refused from launchpad?
[09:56] <seb128> cjwatson, I will ping you if I manage to reproduce it or get detail
[09:56] <G> (bazaar sorry)
[09:56] <seb128> G: the code hosting is down for upgrade
[09:56] <seb128> "Launchpad: Code hosting offline 8.00-9.30 UTC on Friday 3rd September"
[09:56] <G> oh just saw that
[09:56] <G> doh :)
[09:56] <G> seb128: thanks
[09:57]  * G whacks self
[09:58] <seb128> cjwatson, lifeless: bug #628688, retracers seem to work, thanks
[10:08] <soren> When is the unapproved queue going to be flushed?
[10:08] <soren> This week sometime?
[10:13] <lifeless> seb128: hi
[10:13] <seb128> hey
[10:13] <lifeless> is the retracer happier ?
[10:14] <lifeless> at least as far as talking with lp ?
[10:14] <didrocks> cjwatson: thanks a lot :)
[10:15] <seb128> retracers are happier yes
[10:15] <seb128> they manage to get the crash file and retrace it
[10:15] <lifeless> seb128: great
[10:15] <seb128> running it by hand worked but didn't untag it, so that could be a bug but that's not going to stop retracing
[10:16] <lifeless> seb128: we've put a bandaid in place to get access for you
[10:16] <seb128> we can untag the need-retracing by hand if required
[10:16] <seb128> thanks
[10:16] <lifeless> we're now working as hard as we can on the permanent solution, and we should be able to deploy it without downtime [other the the regular rollout process]
[10:16] <seb128> the lack of retracer started being an issue for maverick since it means crash bugs don't reach triagers
[10:17] <lifeless> yeah, it was an unintentional side effect of making private bug attachments... private
[10:17] <seb128> the bandaid seems to be enough to get the retracers running so no hurry from our side for other changes
[10:17] <lifeless> but all the short term options to address it are unpleasant
[10:17] <lifeless> the tagging thing is AFAIK unrelated
[10:17] <seb128> ok
[10:17] <lifeless> so please do investigate/file a bug
[10:17] <seb128> will do
[10:18] <seb128> thanks again for working on the issue
[10:19] <lifeless> no probs
[10:20] <lifeless> we're sorry it took so long to get the bandaid in place: there was some confusion involved
[10:36] <cjwatson> soren: I'm in the process of flushing it
[10:38] <cjwatson> argh, acronym frustration.  What does SDV stand for in the context of "Intel SDV" (i.e. some kind of development board)?
[10:39] <cjwatson> a friend tells me "software development vehicle"
[10:41] <soren> cjwatson: Cool, thank you!
[10:41]  * soren crosses stuff off his list
[11:20] <ogra> cjwatson, i bet mjg59 knows ;)
[11:26] <OdyX> tkamppeter: uh… I'm not the ghostscript maintainer; even not trough a team, so any update will be hard. You (or me) should get in contact with the real maintainers. Note by the way that Debian has had 6 releases since the Ubuntu "fork"
[11:34] <tkamppeter> OdyX, perhaps one could move GS maintainership from the current maintainer to you. You should ask him whether he would continue maintaining GS and then he would need to update it regularly, at least for upstream releases and a merge from Ubuntu before Debian Feature Freezes, or he could pass maintainership to you.
[11:34] <cjwatson> didrocks: gnome-control-center also dropped an Ubuntu change, this one 1:2.30.1-1ubuntu3 from maco.
[11:35] <cjwatson> didrocks: seems like some kind of process sanity check might be called for here?
[11:35] <cjwatson> the periods when archive admins will catch this kind of thing are pretty narrow.
[11:35] <didrocks> cjwatson: is it my upload?
[11:36] <cjwatson> didrocks: no, Robert's, but I assume he's asleep and seb128 redirected me to you earlier when I asked him :)
[11:36] <didrocks> hum, robert… yeah, I think we should discuss with him, he made some of those kind of issues recently :)
[11:36] <didrocks> cjwatson: ok, I'll fix that in some minutes, please reject the upload
[11:37] <didrocks> and talk with him
[11:37] <didrocks> thanks cjwatson and sorry for the noise!
[11:45] <ogra> can someone let linux-ti-omap4 out of the unapproved queue ?
[11:45] <cjwatson> working on the unapproved queue in general
[11:46] <cjwatson> I will get to it soon - doing it roughly in reverse upload order
[11:46] <cjwatson> er, upload order
[11:46] <ogra> ah, great, thanks
[11:49] <seb128> cjwatson, didrocks: I can check for that one, I redirected to didrocks before because I know he did some updates on the empathy stack yesterday
[11:49] <didrocks> seb128: thanks :)
[11:49] <seb128> I guess that one is a case of "somebody sponsored a change and didn't commit to the vcs"
[11:50] <cjwatson> ogra: this isn't an ABI bump?  gosh
[11:50] <ogra> its a version bump
[11:50] <ogra> 2.6.34 -> 2.6.35
[11:50] <ogra> (at least it should be)
[11:50] <cjwatson> so it is, I just can't read
[11:51] <cjwatson> accepted
[11:51] <ogra> thanks a lot
[11:57] <Valente> Hi everybody!
[11:58] <Valente> I would like to ask firstly if I can use this chat for solve problems
[12:00] <Valente> And if not which chat should I look for?
[12:04] <Valente> Hi! Could you tell me if I can use this chat for asking for help?
[12:04] <Hobbsee> #ubuntu
[12:59] <G> dholbach: hey, I've got a question for you reg Harvest when you've got a moment
[12:59] <dholbach> g: sure
[13:00] <G> dholbach: wrt the show all opportunities options (I know Permalink does it but I'm thinking of a way to tie everything else in), what would you say to using jquery to display it as an inline pop-up
[13:01] <G> (similar to how launchpad does some of the assign/linking UI)
[13:01] <dholbach> g: do you think you can file a bug about that and discuss it there - that'd be a good question for Dylan
[13:01] <dholbach> g: he's the ui mastermind :)
[13:01] <G> dholbach: ahhh right okay, will do :)
[13:02] <dholbach> thanks a bunch G
[13:02] <dholbach> G: I'll have a look at your merge proposal in a bit
[13:02] <G> dholbach: okay, I'll put the other one in (the change the text for the filtering)
[13:02] <dholbach> super
[13:03] <G> dholbach: is there a quick way to regenerate the pot files?
[13:03] <dholbach> G: ./manage.py update-template
[13:04] <G> dholbach: ohhhhhh
[13:04] <dholbach> G: (from ./opportunities/management/commands/update-template.py
[13:04] <dholbach> )
[13:04] <G> and here was me thinking taht was for templates etc
[13:04] <G> I'd tried everything but :)
[13:05] <G> I'll do that for my second merge proposal so it'll get picked up (the index translations are missing from the pot file)
[13:05] <dholbach> G: commented on your merge proposal
[13:06] <G> dholbach: oh thats a very good point :)
[13:07] <dholbach> :)
[13:07] <G> will get on that in a moment :)
[13:07] <dholbach> super
[13:09] <G> dholbach: tbh, I think it would be best to leave it as _lazy though so there is an obvious difference :)
[13:09]  * ogra wonders where doko is
[13:09] <dholbach> ogra: oo.o conference
[13:09] <ogra> bah
[13:09] <dholbach> G: hm, not sure
[13:10] <ogra> he should find someone there to fix armel builds :P
[13:11] <dholbach> G: "Always use lazy translations in Django models." - I think it's fine to call it _ there :)
[13:11] <dholbach> http://docs.djangoproject.com/en/dev/topics/i18n/internationalization/
[13:12] <G> dholbach: okay
[13:12] <dholbach> ROCK
[13:15] <cjwatson> \sh: fai accepted
[13:20] <\sh> cjwatson, thx a lot
[13:32] <dholbach> Q: merged, thanks
[13:42] <G> dholbach: no problem!
[13:56] <AnAnt> Hello, is there a way to detect wether the pulseaudio is the sound server in use ?
[13:58] <directhex> AnAnt, well, "aplay -L" gives a hint about it
[14:10] <AnAnt> directhex: thanks
[14:49] <kenvandine> cjwatson, how many people do we want to get to verify the twitter/oauth change for gwibber before putting it in -updates?
[14:49] <kenvandine> cjwatson, it has to be better than what is already there, since we know the version in lucid doesn't work at all for one of the 2 most popular services
[14:50] <cjwatson> oh, I was going to waive the aging period on that
[14:50] <cjwatson> remind me of the bug number?
[14:52] <kenvandine> bug 627565
[14:52] <kenvandine> i had at least 3 people that confirmed it in the ppa
[14:52] <kenvandine> and 1 for sure on the bug... and one that complained about the save button
[14:52] <kenvandine> so i assume it worked for him
[14:52] <kenvandine> we know the save button can be more obvious, not a new problem :)
[14:53] <bilalakhtar> kenvandine: add 1 more, I have also confirmed
[14:56] <cjwatson> kenvandine: what do the last three comments on bug 613420 indicate?
[14:56] <kenvandine> bilalakhtar, thx!
[14:56]  * kenvandine looks
[14:56] <cjwatson> kenvandine: and could somebody validate that bug 583316 is fixed in lucid-proposed?
[14:57] <kenvandine> cjwatson, bug 613420 is probably a case of him authorizing and not seeing the "Save" button
[14:58] <kenvandine> bilalakhtar, can you confirm bug 583316 ?
[14:58] <kenvandine> you should be able to open gwibber prefs and not see tr.im in the combobox
[15:14] <bilalakhtar> kenvandine: verified
[15:28] <seb128> dholbach, do you know who is working on example contents?
[15:28] <seb128> dholbach, ie bug #595248
[15:30] <dholbach> seb128, I was told the design team was working on it
[15:31] <seb128> dholbach, ok
[15:32] <slomo> cjwatson: hi :) could you sync gst-plugins-ugly0.10 0.10.16-1 from debian/experimental? there are no ubuntu changes and no ubuntu changes are necessary and it's in universe
[15:33] <cjwatson> it's really a lot easier with a bug, we have tools to process sync request bugs semi-automatically
[15:33] <cjwatson> but, done
[15:35] <slomo> cjohnston: thanks, i didn't know there are tools for this, sorry
[15:36] <ScottK> cjwatson: Would you please rescore glib2.0.  It just affects powerpc and should save us some FTBFS due to archive skew.
[15:37] <cjwatson> ScottK: done
[15:37] <cjwatson> dunno how much difference it will make - 13 mins vs. 12 mins according to the web interface :)
[15:37] <cjwatson> I think it was probably already first in the queue
[15:45] <ScottK> OK.  Thanks.
[15:48] <cjwatson> kenvandine: ok, aging period waived, copied
[15:48] <kenvandine> cjwatson, thx!
[15:49] <cjwatson> in future I don't suppose we could avoid waiting four months from the announcement of a service being turned off before arranging not to rely on it any more? ;-)
[15:50] <kenvandine> cjwatson, i wish... :/
[15:51] <kenvandine> cjwatson, until less than 2 weeks ago it was looking like we would have to drop twitter support all together... which would not have been popular
[15:52] <kenvandine> there was a great article on arstechnica yesterday about the whole ordeal :)
[15:53] <directhex> the one where segphault hacks the super secret official twitter oauth keys?
[15:54] <kenvandine> directhex, yeah... that was awesome
[15:54] <kenvandine> :)
[15:54] <kenvandine> they told us if we published the key anywhere in source it would be revoked
[15:55] <kenvandine> and they did revoke at least one for being committed to github
[15:57] <directhex> use theirs
[15:58] <kenvandine> directhex, i am sure it is just a matter of time before someone posts a website listing keys
[15:59] <kenvandine> they did extend the deadline twice because they hadn't found a solution for open source clients... but ultimately decided open source clients weren't important enough to delay any longer
[15:59] <kenvandine> sad...
[16:00] <cjwatson> kenvandine: ... lovely
[16:01] <kenvandine> finally compromised with us when we had a week left...
[16:02] <kenvandine> i just hope they don't retaliate against segphault's article by revoking our keys :)
[16:11] <dholbach> apachelogger, thanks!
[16:12] <apachelogger> dholbach: any time :)
[16:18] <smoser> cjwatson, just wanted to make sure you saw this, but I didn't see your response until just now.  see my comment https://bugs.launchpad.net/ubuntu/+source/eucalyptus/+bug/613463
[16:18] <smoser> as to why mtools and grub-rescue-pc files would not work.
[16:20] <cjwatson> smoser: you could extract the files from it and regenerate
[16:21] <smoser> well, yes, but then i still have to depend on xorriso, and i also have to know details about the internals of that image.
[16:21] <smoser> and what flags to send to xorriso and such.
[16:21] <cjwatson> I realise it isn't pretty but I'm not going to have time to change this for maverick now and I don't want to get that badly ouot of sync with Debian (and of course Debian is frozen)
[16:21] <smoser> yeah, i understand that.
[16:21] <smoser> right now, we just have a missing dependency in eucalyptus-nc.
[16:21] <cjwatson> also I'm not sure you in fact need xorriso
[16:22] <smoser> how else would i master the iso image ?
[16:22] <smoser> if you think doing that is loads cleaner, i'm willing to re-work it.
[16:22] <cjwatson> you said you were creating a boot floppy
[16:22] <smoser> yes.
[16:22] <smoser> oh.
[16:22] <smoser> i see, you're saying just grab the files from the iso and make a floppy that is not iso format
[16:23] <cjwatson> yeah
[16:23] <cjwatson> just treat it as a silly delivery mechanism
[16:23] <smoser> well, i wish i'd have seen your comment before. if you think that i should chase that, i will.
[16:24] <smoser> one other benefit of my usage of grub-mkimage is that i only include modules in the original floppy that are needed to load the secondary loader.
[16:24] <smoser> ie, don't need a bunch of filesystems for that.
[16:24] <smoser> and my images are not *tiny*.
[16:24] <smoser> but thats probably not a big deal.
[16:25] <smoser> if you think i should chase this i will. right now the only broken-ness is the missing dependency.
[16:28] <geser> looking for a core-dev to sponsor bug #625798
[16:29] <cjwatson> smoser: I think it's the most viable approach for maverick
[16:29] <cjwatson> for natty, the approach of splitting out -modules packages is fairly tempting
[16:30] <smoser> cjwatson, you think i should re-work to using the grub-rescue-pc ?
[16:30] <smoser> or you think we should just go with what we have now (lack of dependency)
[16:31] <cjwatson> smoser: if you have time to rework it on top of grub-rescue-pc, I think that would be good.  but I don't know what issues the lack of dependency is causing you
[16:37] <smoser> cjwatson, without root can i easily get files off a iso9660 filesystem ?
[16:37] <cjwatson> bsdtar
[16:37] <cjwatson> or isoinfo
[16:38] <smoser> isoinfo -x only does one file at a time, right ?
[16:38] <cjwatson> yeah.  bsdtar has more convenient syntax but is in universe (though I imagine that's changeable)
[16:38] <smoser> so i'd have to crawl its ls-lr output and pick them out.
[16:38] <cjwatson> I do exactly that in d-i
[16:38] <smoser> with isoinfo ?
[16:38] <smoser> wowl
[16:44] <cjwatson> yeah, painful
[16:57] <apw> if i have a file which i want to be installed by each kernel but that file only needs to exist once (this is a common udev rule) is there a sensible way to describe that?
[17:04] <smoser> cjwatson, should i just across the board run 'tolower' on isoinfo ls-lr output ?
[17:05] <smoser> or will it end up not mattering.
[17:05] <cjwatson> d-i doesn't bother
[17:05] <cjwatson> oh, you're forgetting an option
[17:05] <smoser> so in my recreated boot disk, though, it wont matter ?
[17:05] <cjwatson> use -R
[17:05] <smoser> ah
[17:06] <smoser> i tried -J
[17:06] <smoser> and it had no joliet extensions
[17:06] <cjwatson> you want the Rock Ridge stuff - RR => Unixish, Joliet => Windowsish
[17:06] <cjwatson> very very roughly
[17:06] <smoser> right
[17:22] <manjo> superm1, running late... I will be there around 1:00
[17:24] <jdstrand> jcastro: hey. so the security team has the ability to tweet and dent things. how can I get that hooked into planetubuntu?
[17:26] <jdstrand> jcastro: I should probably clarify, we have created a specific account for each that members of the security team can post to
[17:34] <smoser> cjwatson, if you are, http://bazaar.launchpad.net/~smoser/%2Bjunk/starter-junk/annotate/head%3A/iso-extract is what i came up with.
[18:15] <wookey> mvo: can I poke you about https://bugs.launchpad.net/ubuntu/+source/apt/+bug/620576 and https://bugs.launchpad.net/ubuntu/+source/apt/+bug/625042
[18:15] <wookey> this seems like pretty serious breakage to me
[18:16] <wookey> 625042 was OK in 0.7.26~exp12ubuntu3
[18:16] <wookey> 620576 was OK before 0.7.26~exp12ubuntu3
[18:17] <wookey> For the latter I'm not sure how it's supposed to work, so I'm not sure how it should best be fixed. Maybe the missing file should be put back, or maybe the code to copy it over is simply not longer needed
[18:18] <wookey> No-one will notice these bugs in normal use, but I still think they are significant. And hopefully easy to fix.
[18:37] <mvo> wookey: sure, let me have a look
[19:03] <ScottK> cjwatson: Would you please rescore kdebindings kdebase-workspace (only affects armel).
[21:20] <cjwatson> ScottK: done
[21:20] <ScottK> cjwatson: Thanks.
[21:21] <ScottK> That should accelerate when we're done by 8 - 10 hours.
[22:54] <achiang> hm, does anyone know what happened to xserver-xorg-input-keyboard / kbd in lucid? did the package just go away?
[22:55] <fagan> ask on #ubuntu-x
[22:55] <fagan> they would know
[22:55] <achiang> thx