[00:50] <kees> archive-admins: can someone please deNEW the linux-* binaries in hardy-security?
[00:50] <kees> (linux, l-r-m, l-b-m, l-u-m)
[00:51] <kees> slangasek: ^^
[01:06] <kees> cjwatson: ^^
[01:09] <slangasek> kees: poking
[01:09] <kees> slangasek: cool, thanks.
[01:12] <lifeless> pitti: thanks for doing the amd64 port
[01:13] <lifeless> pitti: by the time I actually hit sydney I couldn't put two characters adjacent to each other; I figured it was going to be about as trivial as it was
[04:11] <calc> anyone else having problems with the gnome calendar locking up panel completely anytime you click on it, in hardy-updates?
[04:13] <superm1> try turning off the temperature grabbing
[04:17] <calc> superm1: how do you actually turn it off?
[04:17] <calc> superm1: it only has options to change if it is displayed afaict
[04:18] <superm1> well i've had the freezes you talked about, and i unchecked the weather and pulled out the extra locations i didnt need
[04:18] <superm1> well that temperature
[04:18] <superm1> turned off both
[04:18] <superm1> and then it didn't pull the data or freeze anymore
[04:18] <calc> oh ok, i will try removing the locations, i already have the other options disabled
[04:19] <calc> hmm turning off the other locations didn't help either :-]
[04:19] <calc> er :-\
[04:25] <superm1> well i guess i just got lucky then :(
[04:25] <superm1> it was really annoying before though, so i fell your pain
[04:33] <calc> anyone happen to know how to set the username for svn ssh?
[04:34] <persia> calc: ~/.ssh/config : it's the same as setting a username for any other ssh service.
[04:34] <pwnguin> isn't it just svn+ssh://username@url
[04:34] <calc> ah ok
[04:35] <persia> pwnguin: Well, if you like to type your username that often :)
[04:35] <pwnguin> persia: well, i have a eclipse etc set up svn
[04:35] <pwnguin> if i need a username at all
[06:06] <pitti> Good morning
[06:06] <pitti> lifeless: you're welcome; thanks for digging this patch out, it's highly useful
[06:07] <ajmitch> hi pitti
[06:10] <Hobbsee> pitti!
[06:19] <pwnguin> ok, thats bizarre. firefox doesn't offer a subscription icon for planet.kernel.org
[06:20] <pwnguin> donno if it's ff or the site's fault, but still kinda silly
[06:28] <Treenaks> pwnguin: maybe they forgot to add a <link rel="alternative">
[06:30] <pwnguin> Treenaks: if you know how such stuff works and care, maybe send the site maintainer a hint ;)
[06:31] <Treenaks> pwnguin: http://www.petefreitag.com/item/384.cfm
[06:31] <Treenaks> you send them that :)
[06:32] <pwnguin> it seems like something planet outta do on its own
[07:11] <EvanCarroll> Can anyone help me confirm a bug?
[07:11] <EvanCarroll> ssh-add -D && gnome-terminal --hide-menubar --full-screen -e "ssh host-with-passkey"
[07:12] <EvanCarroll> please replace host-with-passkey with an ssh box ip or name that uses keyauth
[07:12] <EvanCarroll> I think this bug exists in hardy you might have to jump to a tty and kill gnome-ask-ssh
[07:12] <EvanCarroll> I think this bug exists in hardy you might have to jump to a tty and kill gnome-ssh-askpass
[07:12] <EvanCarroll> gnome-keyring-ask*
[07:55] <paulproteus> kees, ping?  (sort of an emergency)
[07:58] <dholbach> good morning
[08:06] <thekorn> hey dholbach!
[08:06] <dholbach> hi thekorn
[08:07] <munckfish> Hi, I want to get a the ps3-kboot sources into the bazaar supermirror. I'm not motu/core, I presume am I going to have to get someone with perms to push the first version for me?
[08:08] <mdke> cjwatson: please could you poke through my email to ubuntu-devel-announce when you get the chance
[08:08] <TheMuso> munckfish: What bazaar super mirror are you referring to?
[08:09] <munckfish> I'm trying to follow this https://wiki.ubuntu.com/BzrMaintainerHowto
[08:09] <munckfish> I'd like to get our packaging stuff up there so it's easy to share changes
[08:09] <munckfish> TheMuso: particularly now you've offered to help build stuff for us
[08:09] <TheMuso> munckfish: Right. Is there already a bzr branch for ps3kboot or whatever its called?
[08:10] <munckfish> There's no product registered (I just did that)
[08:10] <munckfish> I'll look and see if a branch exists
[08:10] <TheMuso> munckfish: If there is not, you can create a branch under the newly registered product. You can make it writable only by yourself, or the ps3-dev team.
[08:11] <munckfish> under the product not the team (like it says in that tut)
[08:11] <munckfish> ok
[08:11] <munckfish> TheMuso: could you join the ubuntu-ps3-dev team on LP?
[08:12] <TheMuso> munckfish: If you would like me to, ok.
[08:12] <munckfish> I think that would have benefits
[08:12] <munckfish> in terms of permissions etc
[08:12] <TheMuso> Ok done waiting for your ACK.
[08:13] <munckfish> TheMuso: ok will do.
[08:13] <munckfish> There is no existing branch
[08:13] <TheMuso> Ok, so create a new one.
[08:13] <munckfish> Ok I'll upload the first version under the product
[08:14] <munckfish> TheMuso: Ok I need to leave for work. Thanks for you help, I'll cont. with this later
[08:29] <TheMuso> munckfish: No problem.
[09:11] <Mithrandir> cjwatson: is it possible to set expiry dates for SSH keys?
[09:27] <saispo> BenC: ping ?
[09:29] <saispo> no one from the kernel team ? i can't clone from the git repository...
[09:36] <soren> saispo: Which url are you using?
[09:36] <saispo> soren: git-clone git://kernel.ubuntu.com/ubuntu.hardy.git ubuntu-hardy
[09:37] <soren> It's git://kernel.ubuntu.com/ubuntu/ubuntu.hardy.git
[09:37] <saispo> yes, excuse me but same error...
[09:37] <soren> Did you mistype or is the documentation wrong somewhere?
[09:37] <saispo> Initialized empty Git repository in /home/jsoyer/local/csm/git/ubuntu-hardy/.git/
[09:37] <soren> Oh. Hehh..
[09:37] <saispo> fatal: The remote end hung up unexpectedly
[09:37] <saispo> fetch-pack from 'git://kernel.ubuntu.com/ubuntu/ubuntu.hardy.git' failed.
[09:38] <soren> It's git://kernel.ubuntu.com/ubuntu/ubuntu-hardy.git
[09:38] <soren> Again: Did you mistype or is the documentation wrong somewhere?
[09:38] <saispo> i get the command on the gitweb
[09:38] <soren> Where exactly?
[09:39] <saispo> http://kernel.ubuntu.com/git
[09:39] <soren> _exactly_? :) I don't see that url anywhere on that page.
[09:40] <saispo> on the top
[09:40] <saispo> To clone one of these projects, use "git-clone git://kernel.ubuntu.com/<project>" or "git-clone http://kernel.ubuntu.com/git-repos/<project>".
[09:40] <soren> You seem to be missing the point.. Does it say "kernel.ubuntu.com/ubuntu.hardy.git" anywhere?
[09:41] <soren> if you just mistyped, that's fine. If the documentation is wrong somewhere, though, we need to fix that.
[09:43] <saispo> i don't see where i make a mistake... :)
[09:43] <soren> It's git://kernel.ubuntu.com/ubuntu/ubuntu-hardy.git
[09:43] <saispo> git-clone git://kernel.ubuntu.com/ubuntu/ubuntu.hardy ubuntu-hardy and git-clone git://kernel.ubuntu.com/ubuntu/ubuntu.hardy.git ubuntu-hardy give me the same result...
[09:43] <saispo> yes i'm agree with you :)
[09:43] <soren> No, you don't. :)
[09:44] <soren>                                            ^^
[09:44] <saispo> this two commandes does not work :)
[09:44] <soren> Look...
[09:44] <soren> Take the url  I sent you and use that.
[09:44] <soren> Copy'n'paste style.
[09:44] <saispo> yes
[09:44] <saispo> and don't work...
[09:44] <saispo> i have : fatal: The remote end hung up unexpectedly
[09:44] <soren> Replace ubuntu.hardy with ubuntu-hardy.
[09:45] <soren> Copy and paste ftw.
[09:45] <saispo> oh excuse me...
[09:45] <soren> Now... Did you mistype or is the documentation wrong somewhere?
[09:45] <saispo> i must open my eyes widely next times !!!!
[09:45] <saispo> mistyped, big excuse...
[09:46] <saispo> thanks soren
[09:46] <saispo> and excuse me :)
[09:46] <soren> np
[09:59] <cjwatson> mdke: done
[09:59] <arthur-> pitti: I answered your mail for initscripts, sorry for the delay
[10:00] <cjwatson> Mithrandir: I don't think so, no
[10:00] <cjwatson> TheMuso: "supermirror" is an old term for what's now called the Launchpad codehosting service
[10:00] <TheMuso> cjwatson: ah.
[10:01] <cjwatson> I've edited BzrMaintainerHowto accordingly
[10:23] <pitti> arthur-: oh, thanks!
[10:42] <pitti> seb128: any luck with gthumb?
[10:42] <Riddell> pitti: can I move kde4libs -proposed to -updates?  bug 218138
[10:43] <pitti> Riddell: looks good, I tagged it v-done
[10:43] <pitti> Riddell: doing
[10:44] <seb128> pitti: I did comment on the bug yesterday
[10:44] <seb128> pitti: no?
[10:44] <pitti> seb128: I don't see it in bug 153572?
[10:44] <seb128> ahhh
[10:44] <seb128> you pointed an another bug number
[10:44] <pitti> seb128: ah, right, because I suck
[10:44] <seb128> the one about the set timestamp to the exif data value
[10:45] <pitti> I forgot to mention above bug in the changelog, sorry
[10:45] <seb128> and I commented on this one
[10:45] <pitti> seb128: right; nevermind me
[10:45]  * pitti hugs seb128
[10:45] <pitti> Riddell: done
[10:45]  * seb128 hugs pitti
[10:45] <seb128> pitti: otherwise the new version works fine, I can add a comment about that on the new version bug if you want
[10:45] <pitti> seb128: nah, that's ok
[10:45] <seb128> alright
[10:45] <Riddell> pitti: thanks
[10:46] <munckfish> arthur-: I notice you're maintainer of libspe2 in debian, are you going to be looking after that package in Ubuntu too? (btw sorry hear about your rugby accident hope you're ok)
[11:18] <pitti> mvo: is bug 225900 already fixed in the intrepid version, or does it need an upload?
[11:19] <mvo> pitti: let me check
[11:19] <geser> pitti: should pkg-create-dbgsyms be able to handle "export DH_COMPAT := 2" in debian/rules? Currently it assumes compat level 1 because of the : before the =
[11:21] <pitti> geser: ah, indeed
[11:21] <pitti> if grep -q '^[[:space:]]*\(export[[:space:]]*\)\?DH_COMPAT[[:space:]]*=[[:space:]]*[2-9]\>' debian/rules; then
[11:21] <pitti> geser: so *= should become *:?=
[11:22] <geser> more *:\?= but yes
[11:22] <pitti> geser: is that the recent debian/tmp -> no such dir FTBFS?
[11:22] <geser> yes
[11:22] <pitti> ah, thanks for tracking this down!
[11:22] <geser> should I file a bug for it?
[11:23] <pitti> geser: I'll add a test case, fix, and upload
[11:23] <pitti> geser: if you want; but I'll fix it right now
[11:24] <geser> if you fix it right now then I don't see the need to file a bug for it
[11:25] <pitti> exactly
[11:25] <pitti> ok, can reproduce here in the test suite
[11:26] <mvo> pitti: I'm uploading chillispot now, it is not fixed in intrepid yet and then sent the patch to debian
[11:26]  * pitti hugs mvo, thanks
[11:29] <seb128> mvo: apt is on crack in intrepid, it really wants to install recommends ;-)
[11:29] <mvo> seb128: indeed :)
[11:29] <pitti> seb128: yohoo!
[11:29] <seb128> mvo: sudo apt-get remove evolution; sudo apt-get dist-upgrade
[11:29]  * mvo runs away for lunch before seb can catch him
[11:29] <seb128> it wants to reinstall evolution because some other packages recommends it
[11:29] <pitti> oh, even for metapackages?
[11:30] <seb128> pitti: not really "yohoo" no, users should be able to remove evolution which is a standard package if they want to
[11:30] <seb128> I'm not sure to understand the logic
[11:30] <pitti> sure, for that particular issue; but I mean in general
[11:30] <seb128> I would expect recommends to be trigger when installing a new package, not all the time
[11:30] <mvo> seb128: I have a look after lunch, I'm not sure why its dragged in, generally it should not re-add it (might be a bug or something strange)
[11:30] <pitti> that's true
[11:30] <seb128> pitti: yeah, just some cleaning to do now ;-)
[11:31] <seb128> mvo: ok, let me know if you need extra informations, I just tried and the guy is right
[11:31] <seb128> sudo apt-get remove evolution on intrepid and sudo apt-get dist-upgrade wants to reinstall it
[11:31] <mvo> seb128: do you have a bugnumer for this?
[11:32] <seb128> mvo: bug #236360
[11:33] <seb128> mvo: I'm reassigning to apt since apt-get dist-upgrade has a similar behaviour
[11:36] <seb128> mvo: hum, this lunch things is actually a good idea ;-)
[11:37] <pitti> apachelogger_: rejecting your kopete-plugin-thinklight; please reupload with a LP # bug reference in the changelog; thanks!
[11:38] <apachelogger_> aye
[11:38] <pitti> mvo: likewise for notification-daemon
[11:40] <geser> pitti: could you give at quick look at bug #236298 and tell me if I missed something or if it's complete?
[11:41] <pitti> geser: looks great, thanks!
[11:45] <pitti> geser: p-c-d tested and uploaded; thanks!
[11:48] <pitti> doko: does Debian know about the tzdata java patch/
[11:48] <pitti> ?
[11:48] <pitti> I didn't see it in the BTS
[11:50] <doko> pitti: yes, aurelian knows
[11:50] <ogra> lool, if you say you dont see crashes with libflashsupport, is that on i386 or amd64 ? (note that the latter uses nspluginwrapper, that might hide the actual crashes)
[11:58] <lool> ogra: it's on i386 and amd64
[11:59] <lool> ogra: I'm using a custom install of libflashsupport on Debian/i386 (1.0~2219-1) and 1.9-0ubuntu1 on Ubuntu/amd64
[12:06] <ogra> hmm
[12:06] <ogra> but no ubuntu i386 there
[12:07] <Keybuk> sabdfl: so, about ye olde tech board? :)
[12:16] <sistpoty|work> hm... any chance we could get a fix for bug 193323 into the point release?
[12:17] <mvo> pitti: thanks and sorry for the forgotten LP number
[12:17] <pitti> mvo: no problem; I'm just anal about this, since absent bug # make SRUs a pain
[12:18] <mvo> rightly so
[12:37] <Mez> Hmm .... Why is Evince saying that it's Microsoft word?
[12:38] <Riddell> lool:
[12:38] <Mez> nvm - it's the document
[12:38] <Riddell> lool, pitti: bug 127985, accept or reject for gutsy?
[12:41] <pochu> soren: hi :) gtk-vnc is dep-waiting on a universe package (for the scaling support I think), could you look into it? https://edge.launchpad.net/ubuntu/+source/gtk-vnc/0.3.6-2
[12:42] <pochu> soren: otherwise we can remove the scaling support, but that wouldn't be cool ;)
[12:43] <geser> Mez: check the title property of your pdf
[12:44] <Mez> geser, I did - It'd be nice for evince to show a prefix though (or a suffix) to show that it isnt MS Word
[12:44] <soren> Mez: "Not Microsoft Word - Microsoft Word - Financial report 2007"
[12:45] <soren> Sounds great!
[12:45] <soren> pochu: So... Feel like writing an MIR? :)
[12:47] <pochu> soren: not really, I'm terribly busy with uni and exams :(
[12:52] <soren> pochu: Ok, no worries. Maybe I can pursuade someone else to do it. I'm a bit busy, too :/
[13:05] <mvo> seb128: I can reproduce the apt thing, I'm on it
[13:17] <seb128> mvo: cool
[13:21] <geser> pitti: could you please remove "gproftpd" again and blacklist it this time? I got synced to intrepid again and intrepid has now a lower version than hardy, see https://edge.launchpad.net/ubuntu/+source/gproftpd
[13:22] <jdstrand> cjwatson: hi! I finally got around to using your irssi-notify scripts and it's working great! :)
[13:26] <pitti> Riddell: I don't think it's worth the risk for a mere FTBFS; it should be fixed if there's an actual fix
[13:27] <pitti> geser: urgh, how can this happen...
[13:27] <\sh> scripts are evil...they are created by humans ,-)
[13:28] <pitti> Source: gadmin-proftpd
[13:28] <pitti> geser: ^ ah, because it's not built from that source any more
[13:29] <geser> pitti: gproftpd got renamed to gadmin-proftpd, so you removed the old source package but Debian has it still and it got autosynced again
[13:30] <pitti> geser: done; thanks!
[13:32] <\sh> and now I have to check if our changes are in debian or fix it again
[13:33] <wgrant> x/win 10
[13:33] <wgrant> Gahhh.
[13:33] <lool> pitti: The bug is also missing lpia binaries; this would be fixed
[13:33] <pitti> lool: which bug?
[13:33] <lool> Riddell: pitti told me it wasn't worth it but would be included if there's something additional to fix
[13:34] <lool> pitti: The libgtk2-perl NBS
[13:34] <pitti> lool: oh, I see; if you need that package, it would be worth it, yes
[13:35] <lool> As already discussed, we don't need it /anymore/; technically you can still run image-creator and build gusty images in one of the configs, and they miss this binary
[13:35] <lool> But hopefully nobody does that anymore
[13:38] <seb128> does anybody here read japanese?
[13:38] <ScottK> persia: ^^^
[13:38] <dholbach> seb128: persia might be able to :)
[13:38] <seb128> see current comment on bug #209520, it indicates that a japanese blog indicates that some of the samba issues in hardy are due to -Wl,-Bsymbolic
[13:39] <seb128> opinion from toolchain and samba guys would also be welcome
[13:41] <zul> seb128: I think there is already a bug open about the -Bsymbolic flags
[13:42] <zul> seb128: I also found a fix for #217137 as well
[13:43] <seb128> zul: do you plan to sru it?
[13:43] <zul> seb128: im in the middle of patching it now
[13:43] <seb128> cool
[13:44] <zul> but for the -Bsymbolic one I think you might slangasek's opinon as well
[13:46] <pitti> Keybuk: can you please have a quick look at https://wiki.ubuntu.com/DesktopTeam/Specs/Intrepid/DevicePermissions ? Please search for "Scott"
[13:47] <pitti> Keybuk: I'd like to write down why the hardy changes for the fingerprint reader can be dropped (and do so in hal, to get rid of a patch which didn't get accepted upstream)
[13:49] <persia> seb128: My apologies, but the limitations of my Japanese combined with my limited understanding of library symbols conspire to block my understanding.  I'll try to either catch Hatena on IRC or get someone to help translate later, and get back to you.
[13:50] <Keybuk> pitti: Epiphany's search is broken today :-(
[13:50] <Keybuk> pitti: btw, do we care about saned?
[13:51] <pitti> Keybuk: ^ for the pending merge of sane-backends?
[13:51] <pitti> I haven't made up my mind yet, TBH (too much other stuff to do)
[13:51] <Keybuk> just in general
[13:51] <pitti> Keybuk: seems quite heavy for a corner use case, though
[13:51] <Keybuk> it needs a sane user/group
[13:51] <pitti> (picking up network scanners, etc; sounds like something avahi should handle)
[13:51] <seb128> persia: thanks, did you spot any reference to a launchpad bug in the blog text?
[13:51] <Keybuk> and it's not run out of the box anyway
[13:51] <pitti> Keybuk: I think it is run now in Debian sid
[13:52] <Keybuk> really?  urgh
[13:52] <persia> seb128: Yes, but not the specific bug.
[13:52] <seb128> ok, thanks
[13:52] <Keybuk> pitti: Fingerprint readers
[13:52] <calc> anyone know about the gnome calendar crashing when you select it issue in hardy-updates?
[13:52] <pitti> Keybuk: nothing we couldn't disable again, I just didn't consider it urgent to re-merge so far
[13:52]  * calc hasn't tried tracking down a bug number yet
[13:52] <Keybuk> The current HAL patch and rules are to allow ordinary users to use the fingerprint reader device
[13:52]  * ogra listens up hearing fingerprint readers 
[13:52] <Keybuk> and thus authenticate and capture fingerprints
[13:52] <Keybuk> which is wrong
[13:52] <ogra> is there a fix for mine ?
[13:53]  * calc doesn't know which desktop team member is in charge of that now
[13:53] <Keybuk> use of the fingerprint reader device should be a privileged operation
[13:53] <pitti> Keybuk: that was merely a workaround so that gnome-screensaver could use it, wasn't it?
[13:53] <Keybuk> and both the registration of new fingerprints, and authentication of existing ones, should be done in the same manner as passwords
[13:53] <Keybuk> basicaly, yeah
[13:53] <Keybuk> the proper fix is that the pam_fprint module should have a chkpwd like helper it can call when it needs to
[13:54] <persia> seb128: I'm pretty sure it's bug 234901
[13:55] <Keybuk> actually
[13:55] <Keybuk> fprint shouldn't be done by PAM at all
[13:55] <Keybuk> because fingerprints are not suitable for authentication
[13:55] <Keybuk> they are simply suitable for identification
[13:56] <soren> What's the difference?
[13:56] <Keybuk> the right way it should work is that swiping your fingerprint should be equivalent to a fast user switch
[13:56] <Keybuk> swiping your fingerprint at gdm equivalent to entering your username
[13:56] <Keybuk> if you have no password, that would be sufficient
[13:56] <Keybuk> but if you have a password, then you should also be asked for it
[13:56] <pitti> soren: you can tell who the fingerprint belongs to, but you can't tell whether it's actually the right person which presents it
[13:56] <Keybuk> soren: identification is something that is unique to you
[13:56] <Keybuk> soren: authentication is something that is secret to you
[13:57] <seb128> persia: indeed seems to be the issue, thanks again
[13:57] <Keybuk> a fingerprint is a suitable medium to identify someone
[13:57] <soren> Hm...
[13:57] <pitti> soren: "I want to buy that shiny laptop with Soren's credit card"
[13:57] <Keybuk> if it's swiped, then it's probably them
[13:57] <Keybuk> or someone who's obtained their finger ;)
[13:57] <seb128> slangasek: could you look at bug #234901?
[13:57] <Keybuk> but it's not suitable to authenticate someone
[13:57] <Keybuk> since fingerprints are not secret
[13:57] <persia> seb128: Anytime.  There's a lot of coders here, and I like to see their work shared :)
[13:57] <Keybuk> in fact, using a fingerprint for authentication is morally equivalent to writing your password down on every single surface you touch
[13:58] <pitti> soren: the CCC recently published the fingerprint of our Minster of the Interior :)
[13:58] <Keybuk> pitti: that's a good example
[13:58] <soren> pitti: Heheh :)
[13:58] <Keybuk> the Credit Card (well, it's number) is unique to soren
[13:58] <Keybuk> so it identifies him
[13:58] <Keybuk> and his PIN number is secret to soren
[13:58] <Keybuk> so it authenticates him
[13:58] <pitti> soren: (in case you don't know, he has gone crazy and wants to turn Germany into an even worse surveillance country)
[13:58] <soren> Right, ok. Got it.
[13:59] <Keybuk> the right way to do fingerprint support is definitely as an alternative to entering your username
[14:00] <pitti> Keybuk: ok, spec updated, set to "Review" state; anything else that I need to do about it now?
[14:00] <pitti> like, getting it ack'ed by someone else than you first, or so?
[14:01] <Keybuk> no, probably not ;)
[14:01] <Keybuk> can you propose it as an intrepid release goal
[14:01] <pitti> sure
[14:01] <pitti> I set myself as an assignee, too
[14:02] <pitti> uid=1000(martin) gid=1000(martin) Gruppen=4(adm),40(src),107(fuse),109(lpadmin),115(admin),1000(martin)
[14:02] <pitti> that's already not too bad any more
[14:02] <pitti> fuse will go away, too, teh rest more or less needs to stay for now
[14:03] <pitti> lpadmin is the only thing that should eventually go away, AFAICS
[14:05] <Keybuk> what's src?
[14:05] <Keybuk> is that one of your own?
[14:05] <persia> Gives write access to /usr/src
[14:05] <jdstrand> zul: can you approve the 'nominate for release' for bug #235912 ?
[14:06] <pitti> jdstrand, zul: ^ done
[14:06] <jdstrand> pitti: thanks!
[14:06] <zul> pitti: thanks
[14:07] <pitti> Keybuk: as persia said; /usr/src is 2775 root:src
[14:07] <pitti> Keybuk: it's not a standard group
[14:43] <sabdfl> Keybuk: taipei time
[14:44] <Keybuk> sabdfl: ah, how long until my tech board membership expires there? :p
[14:44] <sabdfl> everything happens faster here ;-)
[14:44] <ogra> heh
[14:46] <Keybuk> ah, the anti-spain
[14:47] <sabdfl> Keybuk: fixed!
[14:48] <ion_> Funny, both of my intrepid boxes refuse to reboot or shutdown. /me goes to bugs.launchpad.net
[14:50] <emgent> heya
[14:51] <afflux> asac: can you please explain why you closed bug 131793? It was confirmed and I can't find any reason why it should be invalid.
[15:06] <slangasek> seb128: 234901> had seen it, it made me whimper.  I don't think it's related to bug #209520, but is SRU material nonetheless.
[15:08] <seb128> slangasek: right, the bug is clearly a gvfs issue, I pointed it because it seems to be a good sru candidate
[15:08] <StevenK> slangasek: Can you peer at the debdiff I just uploaded to bug 195260 when you have a moment?
[15:10] <slangasek> StevenK: er, looks straightforward, but I'm not sure on what level you're asking me to peer at it - it's a universe package, so motu-sru should approve it
[15:11] <StevenK> Ah ha. To high a level.
[15:11] <StevenK> slangasek: Would you mind unsubscribing ubuntu-sru, then? :-)
[15:12] <slangasek> right, done :)
[15:12] <StevenK> slangasek: Thanks
[15:21] <guysoft422> hey all, does anyone know here what html is opened when running: yelp ghelp:about-ubuntu
[15:29] <saispo> BenC: ping ?
[15:36] <sistpoty|work> slangasek: can you approve bug #193323 and accept the package into -proposed?
[15:37] <jdstrand> pitti: if a package is in -updates in soyuz, will I need to have it deNEWed in -security like in dak?
[15:37] <jdstrand> pitti: hi btw :)
[15:39] <Riddell> jdstrand: uploads to -proposed will get stuck in unapproved
[15:39] <Riddell> they shouldn't when moving from -proposed to -updates
[15:39] <BenC> saispo: pong
[15:41] <jdstrand> Riddell: well, I had a bit of an odd case here where all this clamav stuff was added to -updates. I was then asked to get it into -security (usually its the other way around). So, I had to have a few packages deNEWed in dak, and was wondering if I needed to do the some thing in soyuz
[15:41] <Riddell> BenC: what is linux-ports?
[15:43] <pitti> jdstrand: yes
[15:43] <pitti> jdstrand: unless it is already present in dak, too, obviously
[15:43] <jdstrand> pitti: no, it wasn't
[15:43] <pitti> jdstrand: then you need elmo (cjwatson is AFK today)
[15:44] <jdstrand> pitti: dak is all set now
[15:44] <jdstrand> pitti: I pushed to soyuz a minute ago
[15:44] <jdstrand> pitti: so it's just the soyuz bits I was asking about
[15:45] <pitti> jdstrand: if the same package name already exists in soyuz, it's fine
[15:45] <jdstrand> pitti: perhaps specifics would help here
[15:46] <jdstrand> pitti: clamav had a micro version update for dapper, feisty and gutsy
[15:46] <jdstrand> pitti: pyclamd is a new package for feisty and gutsy, but happens to exist in -updates right now
[15:47] <jdstrand> pitti: does anything special have to happen with clamav or pyclamd in soyuz? both needed to be deNEWed in dak
[15:48] <pitti> jdstrand: no, they should just go straight through
[15:48] <jdstrand> pitti: ok cool-- thanks :)
[15:48] <pitti>    pyclamd | 0.1.1-0ubuntu1~dapper1 | dapper-backports/universe | source
[15:48] <pitti> python-pyclamd | 0.1.1-0ubuntu1~dapper1 | dapper-backports/universe | all
[15:48] <BenC> Riddell: It's the kernel source for non-supported architectures (IOW, anything not x86/x86_64 right now)
[15:48] <jdstrand> pitti: I didn't do anything with pyclamd for dapper
[15:49] <pitti> jdstrand: well, at least overrides for dapper automatically apply to all the pockets; I *think* that holds true for the reverse direction, too
[15:49] <pitti> jdstrand: anyway, if it does land in NEW, just ping Riddell, seb128, or me
[15:49] <jdstrand> pitti: ok
[15:49] <Riddell> BenC: and i386 is non-supported?
[15:53] <ogra> Riddell, its supposed to go to universe if i understood that right in prague
[15:53] <ogra> -i386 vs -generic
[15:53] <seb128> anybody using hardy-updates on amd64 who could get a stacktrace for bug #236025?
[15:54] <seb128> the retracers are broken but that could give informations for bug #236171 which annoys several users
[15:58] <saispo> BenC: i found the error :) it's about compiling lum under hardy for xen and alsa
[15:58] <saispo> i fixed, it's ok :)
[15:58] <pitti> BenC, mvo: I updated https://wiki.ubuntu.com/IntrepidImprovedLinuxMeta with the current discussion I had with mvo
[15:59] <ogra> seb128, is the gdm-signal bianry supposed to work in any way ?
[16:00] <jdstrand> Riddell: well, looks like clamav and pyclamd did end up in NEW. Can you deNEW them for feisty and gutsy?
[16:01] <seb128> ogra: it used to work, I didn't try for a while
[16:01] <ogra> seems it doesnt anymore
[16:02] <Riddell> ok
[16:02] <Riddell> jdstrand: accepted
[16:03] <jdstrand> Riddell: thanks! I have a feeling clamav on dapper will also need it, but it isn't showing up yet
[16:04] <seb128> ogra: that will most likely go away or need to be rewritten when we update to the new gdm anyway
[16:05] <ogra> seb128, right, i just suggested it to someone in -mobile who tries to write a custom logout dialog not using gnome-session ... and we found it just exists silently
[16:05] <Riddell> jdstrand: although there does seem to be a 16 week old linux-meta in there..
[16:05] <ogra> *exits
[16:05] <jdstrand> yeah, I just noticed that...
[16:06] <Riddell> jdstrand: any idea if that should be accepted or rejected?
[16:06] <jdstrand> Riddell: I'm checking
[16:10] <ogra> seb128, hmm, the strace looks like its simply sending the wrong string http://paste.ubuntu.com/16599/
[16:12] <bdmurray> pitti: did slangasek's e-mail clear up my intent with the proposed-pkg tag?
[16:15] <jdstrand> Riddell: it should be accepted
[16:16] <Riddell> jdstrand: ok, doing
[16:16] <jdstrand> Riddell: thanks
[16:16] <Riddell> done
[16:17] <ScottK> jdstrand: Dapper shouldn't need it.
[16:17] <seb128> ogra: right
[16:18] <jdstrand> ScottK: nope it doesn't, just showed up as published
[16:22]  * ScottK basks in the (momentary) warm glow of having the same clamav version in all supported releases.
[16:22] <jdstrand> ScottK: take it in while you still can :)
[16:23] <jdstrand> ScottK: good work!
[16:23] <ScottK> Thanks.
[16:23] <slangasek> zul: is bug #217137 fixed already in intrepid (samba 3.0.30)?
[16:23] <zul> slangasek: I believe it is
[16:24] <slangasek> care to mark it as such in LP? :)
[16:24] <zul> slangasek: I can do that :)
[16:24] <zul> slangasek: MoM has samba-3.2 do we want that as well?
[16:24] <slangasek> er, no
[16:24] <slangasek> 3.2 is only in experimental right now
[16:25] <slangasek> and there are some licensing hang-ups with it
[16:25] <zul> ah ok
[16:30] <ion_> mvo: There are three suggested changes here: 0) rm -f to avoid an error message when there are no files matching the pattern, 1) no need to specify python versions to search for, just look up /usr/bin/python*, 2) use aptitude safe-upgrade instead of apt-get dist-upgrade, since it’s more intelligent in tricky situations. Feel free to discard any of them if they are not worthy. :-) http://heh.fi/tmp/recovery-mode-dpkg-2.patch
[16:32] <kirkland> cjwatson: hey colin, got your note about using bzr instead of debdiff---that's fine by me, i'm happy to comply.  question, though, as this is the second time i've hit this in a week....  how do i tell before hand whether a maintainer is going to prefer debdiffs or bzr branches?
[16:32] <jdstrand> zul: fyi: http://packages.debian.org/changelogs/pool/main/s/samba/samba_3.0.30-2/changelog (see changelog entry for 2:3.0.30-2)
[16:33] <kirkland> cjwatson: something equivalent to "whatpatch" might be helpful...  "whatsourcecontrol" or the like
[16:33] <kirkland> cjwatson: does such a beast exist?
[16:33] <slangasek> kirkland: if the package correctly uses the Vcs-* fields in debian/control, then apt-get source will give you a notice
[16:33] <slangasek> e.g.:
[16:33] <slangasek> NOTICE: 'grub' packaging is maintained in the 'Bzr' version control system at:
[16:33] <slangasek> https://code.launchpad.net/~ubuntu-core-dev/grub/ubuntu
[16:33] <slangasek> Please use:
[16:33] <slangasek> bzr get https://code.launchpad.net/~ubuntu-core-dev/grub/ubuntu
[16:33] <slangasek> to retrieve the latest (possible unreleased) updates to the package.
[16:33] <kirkland> slangasek: oh, cool, i'll look for that
[16:34] <kirkland> slangasek: i very nearly asked you this question after the grub work i did last week ;-)
[16:34] <slangasek> :)
[16:34] <Riddell> soren: E: virt-goodies: python-script-but-no-python-dep ./usr/bin/vmware2libvirt
[16:34] <slangasek> there's also 'debcheckout', which you can use to check the package out of bzr directly
[16:35] <Riddell> soren: accepted, but that should probably be fixed
[16:38] <slangasek> sistpoty|work: bug #193323> always a little disturbing to see debdiffs where a patches/series file is added and no other build-dep machinery is needed...
[16:39] <slangasek> (which in this case is a variant on reasons I hate simple-patchsys, #27: you can never tell by looking at the debdiff whether the maintainer has added a patch right)
[16:40] <Riddell> slangasek: how do other patch systems let you tell?
[16:40] <ion_> mvo: Sorry, i decided that aptitude safe-upgrade handles what apt-get -f install does too soon. It doesn’t in all situations. Patch updated.
[16:41] <slangasek> Riddell: if you're using quilt or dpatch, there's some sort of patch list that you register the patch with; if the debdiff shows that the new patch is /added/ to that file, you can have a reasonable level of confidence that the patch system was in working order beforehand
[16:41] <slangasek> Riddell: but if you only see the addition of a patch in a debdiff, without any series file, it's impossible to determine whether this is because the package uses simple-patchsys, or the uploader forgot to add the patch to the series file, or the uploader forgot to configure the package to use a patch system at all...
[16:45] <sistpoty|work> slangasek: actually quilt was there before... so I just used that (and actually had some troubles with it... I prefer plain patches in .diff.gz myself)
[16:45] <mvo> ion_: thanks, I have a look
[16:45] <slangasek> sistpoty|work: right, I know quilt was there because I know that's how the X Strike Force packages are maintained - it was still disturbing to see that this was the only patch in the series until I remembered that :)
[16:45] <sistpoty|work> slangasek: thanks for accepting it :)
[16:46] <sistpoty|work> slangasek: no, it's not the only patch actually, there was another one there before ;)
[16:46] <slangasek> oh, there was?  Hmm, the diff is misleading then
[16:46] <slangasek> (it doesn't show the other line as context)
[16:47] <sistpoty|work> indeed, that's quite strange
[16:49] <siretart> sistpoty|work: as I mentioned in the bug report, the testpackage did work on my laptop using qemu!
[16:49] <sistpoty|work> siretart: yes, I saw that... and it worked in FAUmachine for me :)
[16:50] <ion_> mvo: And... Patch updated once again :-P. I dpkg --unpacked a package that had an uninstalled dependency. I initially tried just aptitude -f install, but it offered to remove the package that had been partially installed instead of satisfying the dependency. So i put apt-get -f install to the patch. Now i found out that aptitude --safe-resolver -f install handles it as expected, installing the dependency and finishing the install of the package.
[16:51] <slangasek> seb128: should gnome-games-data 2.22.2.1 be copied from hardy-proposed to intrepid? (fixes bug #221781)
[16:51] <siretart> it would be interesting to know if the dexconf quirk can be removed with that patch
[16:51] <slangasek> siretart: intrepid-only, please ;)
[16:52] <siretart> bryce: do you agree to remove the dexconf quirk for the cirrus driver now that bug #193323 has been fixed in intrepid?
[16:53] <siretart> bryce: at least on probation ;)
[16:53] <seb128> slangasek: yes please
[16:54] <stgraber> mvo: someone just reported bug 237111 that breaks gutsy => hardy upgrades when italc is installed
[16:54] <seb128> slangasek: I though that was already copied
[16:55] <stgraber> mvo: what's the best way to fix that ? (other than asking the user to remove the package and reinstall it afterwards to avoid the conflict)
[16:55] <slangasek> seb128: evidently not, but I'll take care of it :)
[16:56] <mvo> stgraber: checking
[16:57] <slangasek> pitti: what do you like to do in a case like bug #221781, where a bug is fixed by a package in -proposed, but that wasn't known at time of upload so the bug number isn't in the changelog?
[17:22] <mvo> stgraber: that looks like a missing "Replace: italic-master (<< $version-where-file-was-moved)" in itallc-client
[17:22] <mvo> stgraber: we should do a sru for this. people running the release-upgrader are not affected because we run with --force-overwrite here
[17:23] <stgraber> mvo: hmm, so he was doing a manual dist-upgrade ...
[17:24] <stgraber> mvo: doing Replace: italc-master (<< x.y.z) will let dist-upgrade overwrite then install it ? because we can't just drop italc-master
[17:24] <mvo> stgraber: yes, it means that italc-client is allowed to overwrite files of the italc-master package (if version << x.y.z is installed)
[17:25] <mvo> stgraber: let me know if I can help further, but it should be safe to use the hardy version for the << (best is of course the exact version where the file was moved)
[17:27]  * Surfer33 Visit http://www.FakeMagazineCover.com (upload pic make mag) - http://www.SillyWebcam.com (play with webcam online) - http://www.Is-A-Jerk.com (insulter/anon email) - http://www.ComedySearchEngine.com (fun) - http://www.BodySwitcher.com (put your face on funny body) - http://www.MedChecker.com (health) - http://www.Canuckster.com (Canada eh) - http://www.Nerdful.com (geeks)
[17:27] <Hobbsee> sigh
[17:28] <mkrufky> that's frac'd up -- isn't this channel registered?  you should require ops rights to change the topic
[17:29] <Hobbsee> mkrufky: it's registered.
[17:29] <mkrufky> you can restrict topic changes to ops
[17:29] <Hobbsee> i know
[17:29] <mkrufky> k
[17:30] <Seeker`> /mode #ubuntu-devel +t
[17:30] <Hobbsee> however, it's rarely abused, and non-ops tend to change it more often.
[17:30] <mkrufky> gotcha
[17:31] <ogra> and we have ops to change it back while immediately caring for the cause of the prob as well ;)
[17:31] <ogra> thanks Hobbsee
[17:32] <Hobbsee> np
[17:32] <Hobbsee> ogra: nah, i can't kline.
[17:32] <Hobbsee> although, killing all java clients is an option...
[17:33] <Hobbsee> will try that.  it looks like a proper IP, not a proxy.
[17:33] <mkrufky> oof... twcny is all dynamic IPs
[17:33] <mkrufky> that guy will have a new IP tomorrow, and somebody ELSE will be banned
[17:33] <mkrufky> (thats my isp, too)
[17:34] <Hobbsee> actually, it's stayed constant in his last 3 hits (over a couple of mins)
[17:35] <Hobbsee> so he's not power cycling or so.
[17:35]  * calc wonders if forcing people to register nicks to join a channel would help, and make registering nicks require real email address, etc
[17:36] <mkrufky> registered to change a topic is reasonable
[17:36] <persia> calc: I'd not like that for when I am testing something in an image, and don't want to put a password, yet wish to speak here.
[17:36] <Hobbsee> calc: possibly, although i've got a preference of blocking all anonymisers
[17:36] <mkrufky> but registered to join a channel may be a bit much
[17:36] <Hobbsee> calc: and the latter is enforced, now
[17:37] <persia> Hobbsee: Well, kinda.  There are still ways around it, but they are harder to reach.
[17:37] <Hobbsee> persia: yeah, true.
[17:46] <slangasek> calc: we should just make spamming a capital crime, that's all
[17:47] <Hobbsee> slangasek++
[17:55] <calc> slangasek: heh yea :)
[17:55] <calc> just send them to texas and we'll get rid of them ;-)
[17:55] <slangasek> \o/
[18:00] <bryce> siretart: sure, if the underlying problem is confirmed as fixed, I'd love to remove the dexconf quirk
[18:14] <bryce> siretart: there's actually several qemu quirks in dexconf, and I'm not certain which can be removed
[18:15] <bryce> siretart: it is specifying the driver, the depth, the horizzync/vertrefresh, and the resolutions
[18:15] <greg-g> for an SRU which is in -proposed, should I write a "works for me" comment on the bug regarding the SRU? (eg: bug 235805 )
[18:16] <greg-g> I've been using the package for 3 days now
[18:20] <bryce> siretart: I've commented on bug 193323 about what needs tested.  There'll need to be a new bug report filed.
[18:21] <ogra> greg-g, positive comments usually help with SRUs, yes
[18:24] <sbeattie> greg-g: yes, please write a works for comment, it's useful if you can briefly characterize how you've been using the software
[18:24] <sbeattie> err a wroks for me comment.
[18:24]  * sbeattie gives up on typing today
[18:26] <greg-g> thanks ogra/sbeattie
[18:32] <gmargo> What mailing list has info about kernel updates?  Today a new linux-source package came out (2.6.24-18.32) but no corresponding linux-image packages, except the -debug versions.  I can't find the mailing list archive that might talk about this.
[18:38] <asac> afflux: you can reproduce? do you use the instructions in the bug?
[19:03] <zul> slangasek: mind coming to the server-team meeting tomorrow I put openldap on the agenda
[19:03] <slangasek> zul: what time is it?
[19:04] <zul> slangasek: 15:00 UTC I believe mathiaz correct me if Im wrong
[19:04] <afflux> asac: not sure if it's still possible, but the last time I checked it worked (as mentioned in the last two comments in the bug)
[19:05] <slangasek> zul: well, assuming we're still on the same schedule for the platform team meeting, then yes, I mind doing anything at 1500 UTC tomorrow :)
[19:06] <zul> slangasek: :)
[19:08] <afflux> asac: right, I can't reproduce it anymore with firefox 3.0~rc1+nobinonly-0ubuntu0.8.04.1.
[19:09] <slangasek> zul: so, trying to confirm with cjwatson on that point; if I can make it I will
[19:09] <zul> slangasek: ok great thanks..
[19:09] <ogra> slangasek, ah. you were on holiday last meeting, right ?
[19:10] <ogra> we rotated
[19:10] <slangasek> ogra: correct; I've poked the IRC log, it just says that cjwatson will send mail about it
[19:10] <ogra> right
[19:10] <slangasek> not that the time was confirmed changed, or am I overlooking something important later in the log?
[19:11] <ogra> well the US and asia people that were there all said it would be ok
[19:11] <ogra> i'd have counted that as confirmation
[19:35] <saivann> ScottK : ping
[19:36] <ScottK> Pong
[19:36] <ScottK> saivann: ^^
[19:38] <saivann> ScottK : Concerning bug 230350, you said "I think you'd be better off to call it 0.4.0.2-3build1 and not change anything
[19:38] <saivann> but debian/changelog." I agree about the first part, but I still think that we should "merge" the debian packages since there is a lot of updates in the packaging, like you can see in the last patch that I attached
[19:38] <ScottK> saivann: My suggestion is use the Debian package, not ours as the basis for "only changing the changelog".
[19:38] <saivann> ScottK : What would you think about keeping the current patch, but change the changelog entry for 0.4.0.2-3build1
[19:39] <slangasek> hmm, does update-manager use sudo for authentication in hardy?
[19:39] <slangasek> (IIRC it does)
[19:39] <ScottK> Less the maintainer change I think that adds up to what I suggested.
[19:40] <saivann> ScottK : Ok then we agree, my current debdiff is the differences between the debian package and our current package. All I would need to change is the version (0.4.0.2-3build1)
[19:40] <ScottK> And drop the maintainer change.
[19:41] <saivann> ScottK : And set the status to invalid for bug 230350?
[19:41] <ScottK> saivann: Yes.
[19:41] <saivann> ScottK : Thank you
[20:01] <siretart> bryce: see my follow up on bug #237164. none of the quirks discussed here are actually working with qemu
[20:03] <sistpoty> siretart: heh, looks like we simultanously commented on the dexconf quirks bug *g*
[20:03] <siretart> sistpoty: oh,  nice :)
[20:04] <siretart> sistpoty: as for bug status: it should be 'confirmed' since it is a genuie issue. if you want to express that it is valid, then 'triaged' is meant for that
[20:05] <sistpoty> siretart: ah... I guess I'm not too used to the triaged status yet
[20:06] <siretart> sistpoty: we had quite some discussion about the bugstatus 'confirmed' at UDS. kiko suggested to just remove it from launchpad because there is so much confusion about it
[20:06] <norsetto> I would just remove triaged ...
[20:07] <siretart> sistpoty: see https://wiki.ubuntu.com/Bugs/Status for the status definition
[20:07] <siretart> norsetto: as long as 'confirmed' becomes restricted to developers, I wouldn't mind
[20:08] <norsetto> siretart: thats even better then
[20:12] <saivann> ScottK : If you have few minutes to review, here's the new fake sync : bug 235387
[20:12] <ScottK> saivann: I'm busy with $WORK currently, so just go with the normal sponsorship process.
[20:13] <saivann> ScottK : Ok thanks again
[20:13] <ScottK> No problem.
[20:26] <joshwaitzkin> hi, I'm searching for a contributor (not with money but with knowledge) for my open source application, it's written in C and is a cd drive utility. More details here: http://odman.sourceforge.net/
[20:28] <knix> oss spam
[20:30] <andrew_sayers> joshwaitzkin: wouldn't it be better to contribute to a project like setcd?
[20:31] <joshwaitzkin> andrew_sayers, I can't work on my app, and to work with other apps. too
[20:31] <joshwaitzkin> because I have no time :(
[20:32] <andrew_sayers> My point is, your app seems to overlap considerably with that one.
[20:34] <andrew_sayers> If you merge your work into that, you can contribute more productively and be more likely to get your work reviewed.
[20:44] <kantor> hi, I'm searching for a contributor (not with money but with knowledge) for my open source application, it's written in C and is a cd drive utility. More details here: http://odman.sourceforge.net/
[20:51] <iGama> Hy all
[20:52] <iGama> where can i find info about the packages in the Proposed repository?
[20:52] <slangasek> what info are you looking for?
[20:53] <iGama> like the Samaba package, for example
[20:53] <iGama> *Samba
[20:53] <iGama> whats the changes on it? why new package
[20:53] <iGama> the description on the update manager gave me nothing
[20:54] <iGama> its more about curiosity
[20:54] <slangasek> the 'description of update' pull-down will retrieve the full changelog for the update
[20:54] <iGama> theres nothing on it
[20:54] <iGama> its says " Not available"
[20:55] <slangasek> hmm, possibly the changelog for that particular update isn't published yet to the changelog server because of how recent it is
[20:55] <iGama> true
[20:56] <iGama> but isnt there a place where it says what packages are going in the rep?
[20:56] <slangasek> well, https://lists.ubuntu.com/archives/hardy-changes/2008-June/
[20:57] <iGama> that can help :) thanks
[21:01] <geser> pitti: are the buildds chroot broken again?
[21:02] <pitti> geser: eek?
[21:02] <geser> WARNING: The following essential packages will be removed.
[21:02] <geser> This should NOT be done unless you know exactly what you are doing!
[21:02] <geser>   sysvutils
[21:02] <geser> http://launchpadlibrarian.net/14967445/buildlog_ubuntu-intrepid-i386.libfile-sync-perl_0.09-4build1_CHROOTWAIT.txt.gz and others
[21:02] <pitti> geser: oh, that might even be my fault; it was renamed to sysvinit-utils
[21:03] <pitti> and sysvutils is now a transitional package
[21:04] <pitti> I didn't see that when upgrading with dpkg -i *.deb
[21:04]  * pitti checks
[21:09] <pitti> geser: ah, I think I got it; fixing
[21:14]  * pitti already feels infinity's wrath
[21:16] <pitti> geser: fix uploaded; but it might not actually build, due to said problem :/
[21:17] <jonathan_> Greetings.  I am new to Linux development (switching from .NET programming.)  I presume I am in the right place?
[21:18] <slangasek> um... per the channel /topic, no, you aren't :)
[21:18] <mterry> jonathan_: This is more for specifically-Ubuntu work, not general Linux programming
[21:18] <pwnguin> development OF ubuntu, not ON ubuntu ;)
[21:18] <jonathan_> Ah, thanks.  Thought someday I hope to join your ranks.  :-D
[21:19] <pwnguin> though I do wish there was a channel or community for the latter -- then someone might fix eclipse ;)
[21:19] <jonathan_> Yeah, I lament the fact that AVR32 Studio is built on Eclipse.
[21:21] <pwnguin> lets be clear -- eclipse is far better than any embedded IDE before it. but this is all "off-topic"
[21:21] <ScottK> jonathan_: Eclipse is in Universe, so #ubuntu-motu would be a better channel to discuss improving it for Ubuntu.
[21:22] <norsetto> scottk: masochist
[21:23]  * ScottK is a core-dev now.  I'll leave him to dedicated MOTU such as yourself. ;-)
[21:23] <pwnguin> well then lets bring it back to main: where's the C++ ide in main?
[21:24] <bryce> siretart: posted some debs to validate with; I can upload the xorg changes to intrepid once someone can do a quick smoke test
[21:26] <pwnguin> we have vim, emacs and... ed?
[21:32] <sistpoty> bryce: if I grab a daily and install the new x11-common inside the livefs, and then do a gdm restart, will that trigger the x autodetection, or will that pick up remains of the previous xorg.conf?
[21:35] <bryce> sistpoty: after installing in the livefs, run `sudo dexconf`and that should regenerate the xorg.conf
[21:35] <bryce> heh s/should/will/
[21:35] <sistpoty> bryce: ok, thanks. will do a test tomorrow at work ;)
[21:35] <bryce> awesome, thanks
[21:36] <kirkland> evand: ping
[21:37] <kirkland> evand: I have drafted a Blueprint and a Spec for the SwapfileAtInstallation item.  I'm hoping you'll give it a review?
[21:37] <kirkland> cjwatson: you too :-)
[21:37] <kirkland> evand: cjwatson: https://blueprints.edge.launchpad.net/ubuntu/+spec/swapfile-in-the-installer -> https://wiki.ubuntu.com/SwapfileAtInstallation
[21:42] <evand> kirkland: will do
[21:43] <pwnguin> kirkland: is swapfile really just as fast as swap partition?
[21:43] <kirkland> evand: thanks, i'll send an email
[21:43] <evand> kirkland: FWIW, Python is not available in d-i.
[21:43] <evand> ok
[21:43] <pwnguin> im not sure it really matters, but i donno, sometimes baldfaced assertions are wrong
[21:43] <kirkland> pwnguin: supposedly, yes, in Linux 2.6.* kernels
[21:44] <kirkland> evand: okay, i'll make that just shell
[21:44] <kirkland> pwnguin: i linked that statement to an lkml post
[21:44] <kirkland> pwnguin: i'll try to find something more authoritative, perhaps benchmarks
[21:45] <pwnguin> kirkland: thats what im saying. he just says its so.
[21:45] <pwnguin> cool
[21:45] <kirkland> evand: python removed
[21:47] <kirkland> pwnguin: how about http://lkml.org/lkml/2005/7/7/326 from akpm ?
[21:48] <pwnguin> kirkland: so the kernel wont grow swapfiles automatically?
[21:50] <kirkland> pwnguin: don't think so...  you dd some amount of disk space to a file, and mkswap to format it, and swapon to tell the kernel about it
[21:50] <kirkland> pwnguin: i'll have to do some test/research to see if it can use sparse files
[21:50] <kirkland> pwnguin: my gut says "no", but i've been surprised before ;-)
[21:50] <pwnguin> the mail specifically said no, so unless it changed
[21:50] <kirkland> pwnguin: right, mail is from 2005
[21:57] <kirkland> pwnguin: part of what I'm suggesting are a couple of simple, command line userspace tools to do the swapfile resizing, and as those are verified for correctness and stability, potentially creating a userspace daemon to handle the auto resizing
[22:00] <pwnguin> kirkland: alright. just thinking about some fun I had where i needed to resize swap for hibernate
[22:00] <kirkland> pwnguin: right, well hibernate is one of the "outstanding issues" ....
[22:01] <kirkland> pwnguin: ubuntu doesn't yet support hibernate-to-swapfile
[22:01] <kirkland> pwnguin: that's a related item that needs to be solved
[22:01] <kirkland> pwnguin: see Bug #83325, where BenC says that the kernel pieces are there, we just need the userspace bits
[22:02] <kirkland> BenC: speaking of, ping....
[22:03] <Burgundavia> mdke: you around?
[22:14] <BenC> kirkland: Hey...userspace bits are mostly done there, except the crash program to extract a stripped dump file for apport usage
[22:14] <BenC> kirkland: what else was there?
[22:15] <mdke> Burgundavia: i am now
[22:16] <kirkland> BenC: oh, i was going to modify the description/title of the bug report https://bugs.edge.launchpad.net/ubuntu/+source/initramfs-tools/+bug/83325
[22:16] <kirkland> BenC: I think it's actually *hibernate*, rather than *suspend* that's broken
[22:16] <kirkland> BenC: I thought I'd run that by you first, though
[22:22] <snikker> hi, someones can tell me if the repositories for edgy are broken?
[22:25] <snikker> no one?
[22:28] <Burgundavia> snikker: in what sense?
[22:28] <slangasek> snikker: I can tell you that edgy is end-of-lifed; it hasn't been dropped from the archive centrally, but given that there's no longer any security support for it, it would be a good idea to upgrade
[22:30] <snikker> Burgundavia: i'm unable to install from universe.... unable to get http://archive.ubuntu.com/ubuntu/pool/universe/m/mingw32/mingw32_3.4.5.20060117.1-1_i386.deb  404 Not Found [IP: 91.189.88.31 80]
[22:31] <snikker> slangasek: yes i know... i've got edgy in chroot for testing...
[22:33] <geser> looks like it vanished from the archive, it isn't listed in LP also anymore
[22:35] <snikker> geser: so there are no way to install anything?
[22:36] <geser> no, unless you find a mirror which has the needed files
[22:36] <ScottK> launchpad's purging policy has gotten rather more agressive than it used to be ...
[22:36] <Burgundavia> snikker: why do you need edgy? why are you not upgrading?
[22:37] <geser> snikker: you can also dig in LP to download each needed deb manually (they are still there)
[22:38] <snikker> Burgundavia: it's an old chroot that i use to test application, compile and so on... but maybe it's time to update... My real ubuntu version is hardy
[22:39] <snikker> geser: in launchpad? ok i try... thank you
[22:40] <geser> snikker: e.g. https://edge.launchpad.net/ubuntu/edgy/i386/mingw32/3.4.5.20060117.1-1 for the mingw32 deb
[22:41] <snikker> geser: great! thank you!
[22:41] <soren> What the..
[22:44] <soren> infinity: I presume you're aware of the massive chroot problems on the buildd's?
[22:44] <soren> infinity: E.g. https://edge.launchpad.net/ubuntu/+source/laptop-detect/0.13.6ubuntu1
[22:46] <infinity> soren: I'm not entirely sure I want to blame the buildds on upstart suddenly wanting to be removed...
[22:47]  * infinity wonders WTF is going on there...
[22:47] <geser> sysvinit got renamed
[22:48] <geser> pitti uploaded already a fixed package but it needs handholding now to get build
[22:49] <infinity> *sigh*
[22:49] <infinity> On it.
[22:49] <LaserJock> anybody happen to know offhand if packages in -proposed can be removed?
[22:50] <LaserJock> I assume they can be but I'm not positive
[22:50] <infinity> LaserJock: Yes.
[22:50] <LaserJock> infinity: thanks
[23:29] <infinity> soren: Thanks for the heads-up, BTW.  Should be all better (and I'll give-back all the chroot-wait packages) shortly.
[23:40] <cody-somerville> Changelogs for security packages should really be pushed to the changelog server immediately so people can see they are security updates
[23:41] <cody-somerville> s/security packages/security uploads
[23:49] <kees> there's a bug open somewhere for that
[23:49] <kees> aptitude changelog is handy for avoiding that, though
[23:51] <bryce> ogasawara: could you take a look at lp #213191?  He mentions that he can't ssh into the box, so I suspect it may be a kernel hang rather than X.
[23:51]  * bryce waves to kees
[23:51] <soren> infinity: Lovely. Thanks for fixing!
[23:52] <infinity> soren: Well, this all depends on drescher waking the hell up and finishing its publisher run.
[23:52] <infinity> soren: But we can pretend it's fixed...
[23:52] <soren> That's what I'm doing.
[23:52] <infinity> Good man.
[23:52] <kees> hi bryce :)
[23:56] <emgent> morning people :)