[00:00] <TheMuso> Nice to know some people care about ports around here. :)
[00:01] <directhex> i care about ports
[00:02] <directhex> who wants to help fix media handling in moonlight on big endian arches. anyone?
[00:02] <TheMuso> directhex: Whats the problem exactly?
[00:03] <Riddell> I'm sure Microsoft would be happy to help :)
[00:03] <TheMuso> heh
[00:03] <directhex> TheMuso, some bug in the demuxer
[00:03] <TheMuso> ah
[00:04] <TheMuso> Count me out. :)
[00:06] <dtchen> TheMuso: what are some disadvantages of reverting PA's 0004_disable_autospawn.patch?
[00:06] <sistpoty> directhex: /me would probably spot endienass problems, as he's a cause of them in a number of own-written files *g*
[00:07] <TheMuso> dtchen: If people have pulseaudio installed on a {k,x,myth}(u)buntu install, and go to use an alsa app, it will start, and possibly cause them confusion when things don't behave as expected.
[00:07] <directhex> sistpoty, well, feel free to take a look. there's an open upstream bug... https://bugzilla.novell.com/show_bug.cgi?id=443688
[00:07] <TheMuso> dtchen: THats one off the top of my head.,
[00:07] <TheMuso> or if a user disables pulse for GNOME, but still has it installed, it will start anyway.
[00:08] <sistpoty> directhex: that bug isn't saying very much? any hint to a file?
[00:09] <dtchen> yeah, i was thinking of those, but i'm weighing those against the nonexistent stream/connection refused bugs
[00:09] <savvas> hm..
[00:09] <dtchen> ^ TheMuso
[00:09] <TheMuso> dtchen: Right.
[00:09] <savvas> realtek ethernet is not working in intrepid -11-generic, it worked fine in -9-generic - here's the diff: http://paste.ubuntu.com/117888/
[00:10] <dtchen> TheMuso: how do you feel about setting tsched=0 in default.pa for the next upload?
[00:10] <TheMuso> dtchen: Very strongly in fact.
[00:10] <TheMuso> savvas: What realtek chip exactly? I am using a realtek onboard device here with no issues.
[00:10] <dtchen> TheMuso: strongly opposed to or in favour of?
[00:10] <directhex> sistpoty, upstream would know more. at a guess, something in src/asf/
[00:10] <TheMuso> dtchen: Strongly in favour of.
[00:11] <sistpoty> directhex: /me downloads...
[00:11] <dtchen> TheMuso: ok
[00:12] <savvas> TheMuso: I'm helping out a user, here's the working set of lspci -nnv: http://paste.ubuntu.com/117874/
[00:14] <TheMuso> savvas: right thats not my chip./
[00:14] <TheMuso> dtchen: If you are on a role with the pulse branch, feel free to throw those changes in yours, and I'll just mergte and upload when I next get to the audio stack, which will be Monday at the earliest.
[00:14] <TheMuso> Since I am not currently working, I intend to spend time on other things that I care about as a community member.
[00:20] <TheMuso> Yay, now new kernels can be on ports disks.
[00:25] <dtchen> TheMuso: yep, already pushed to my branch, but i'm going to test the autospawn change more heavily before i commit it
[00:26] <TheMuso> dtchen: Sure.
[00:29] <sistpoty> directhex: sorry, can't help you right now... I just can't find any src/asf (or anything that might relate to it)
[00:30] <sistpoty> gn8 everyone
[02:18]  * calc thought xubuntu was supposed to be lighter weight than gnome but seems about the same with jaunty
[02:23] <TheMuso> calc: its XFCE 4.6, so theres a chance that some optimization has not yet been done.
[02:44] <calc> TheMuso: ah ok
[02:44] <calc> TheMuso: well both gnome and xfce seem to take ~ 280MB after boot
[02:44] <calc> TheMuso: i'm not sure if 280MB is high or low for them
[02:44] <TheMuso> Right
[02:45] <TheMuso> I thought you meant speed
[02:45] <calc> ah ok, i thought it used less memory as well, but maybe not
[02:45] <TheMuso> I don't know either.
[02:48] <TheMuso> ScottK: lol qt4-11 eventually built.
[02:49] <ScottK> TheMuso: Yeah.  Third time was the charm.
[02:49] <cody-somerville> ScottK, Sounds good (re: motu-release delegation for Xubuntu)
[02:49] <ScottK> OK.
[03:17] <TheMuso> This rt package needs to be refactored a lot, and since realtime is now in git, /c
[03:17] <TheMuso> woops wrong channel
[05:28] <ScottK> TheMuso: Congratulations again.  All ports arch in one upload.
[05:28] <ScottK> TheMuso: Have you considering getting linux-ports listed in p-a-s so it doesn't try to build on archs it's not relevant for?
[05:28] <TheMuso> ScottK: Yeah, I am pleased. I got meta uploaded too, so I can now go ahead and change ports disks.
[05:28] <TheMuso> ScottK: p-a-s?
[05:30] <TheMuso> ScottK: considering the main kernel is not listed as such, then I don't see the need.
[05:30] <TheMuso> ScottK: I.e the main kernel still is attempted on powerpc/sparc/ia64/hppa
[05:32] <ScottK> TheMuso: Packages-arch-specific.  It's not critical, but it always seemed cleaner to me not to build on archs it's not needed for.
[05:33] <TheMuso> ScottK: I agree. How does one get that changed?
[05:34] <ScottK> There is on packages arch specifc file that is used by both Debian and Ubuntu.  It's maintained in Debian.  I don't recall (as it changed recently) the specifics, but Phil Kern mailed ubuntu-devel about it.
[05:35] <TheMuso> Hrm ok.
[05:35] <ScottK> TheMuso: The old procedure was "Ask lamont."
[05:35] <TheMuso> heh right.
[05:35] <TheMuso> Its not much of a bother really.
[05:35] <TheMuso> And would be a problem if the mobile guys decided to throw a kernel or two to ports for arm.
[05:35] <TheMuso> but thats speculating.
[05:36] <TheMuso> or any other variant/arch in fact.
[05:37] <ScottK> True.
[05:37] <ScottK> I guess particularly since there may be a new port coming soonish.
[05:38] <ScottK> Someone messed up and mentioned it here the other day.
[05:38] <TheMuso> Right.
[05:50] <StevenK> ScottK: We might end up forking P-a-s, due to stuff
[05:51] <ScottK> StevenK: I'm aware of the stuff.  But until we do ....
[10:44] <bimal> i cannot access my bluetooth . can any one help me
[10:53] <iulian> bimal: Try #ubuntu.  This channel is not for support, it is for development only, see /topic.
[10:54] <iulian> If you use Jaunty, try #ubuntu+1.
[10:54] <bimal> sorry
[11:26] <geser> doko: Hi, what are the chances to see python-central 0.6.8 in jaunty? Some packages from universe are in DEPWAIT as they want python-central >= 0.6.8 and jaunty has only 0.6.7ubuntu1.
[11:47]  * sebner winks geser =)
[11:52]  * geser winks back to sebner
[12:09] <savvas> is the default security repository security.ubuntu.com or archive.ubuntu.com ?
[12:14] <jpds> security.
[12:17] <savvas> thanks :)
[12:17] <directhex> "yes"
[12:18] <savvas> jpds: I'm asking because in jaunty because the default uses archive.ubuntu.com
[12:19] <jpds> savvas: I thought security. was best to point at, because the users wouldn't have to want for the mirrors to update to get the fixes.
[12:20] <jpds> s/want/wait/
[12:20] <savvas> good point
[12:20] <Laney> savvas: security probably hasn't been opened for jaunty
[12:20] <Laney> since updates are just done in the main archive
[12:20] <Laney> it should be there after release I guess
[12:21] <savvas> ok :)
[12:24] <geser> http://security.ubuntu.com/ubuntu/dists/jaunty-security/ exists already but is of course still empty
[12:39] <mok0> Any archive-admins online?
[12:40]  * StevenK hides
[12:41] <mok0> StevenK: heh, I would much appreciate to get bug 326172 processed, as I have watch on 2 other packages in line after that
[12:41] <mok0> StevenK: (talking about jeuclid, and after that scitools)
[12:42] <StevenK> mok0: There are no clear indications of what the Ubuntu changes are, and that the Debian package has merged them
[12:42] <StevenK> mok0: Add that to the bug and I'll process the sync
[12:43] <mok0> StevenK: ok, I'll look at it right away
[12:53] <mok0> StevenK: hope my latest comment is satisfactory
[12:59] <StevenK> mok0: Done.
[13:30] <Mez> who runs the fridge nowadays? cause someones cocked up and put their own stuff in the Calendar :D
[13:30] <nhandler> Mez: Anyone can add events to the calendar now. It is a Google Calendar
[13:31] <nhandler> Where is the personal event?
[13:31] <Mez> nhandler: only if they're given access to add events ... :D
[13:31] <nhandler> Mez: Not true
[13:32] <nhandler> Mez: https://wiki.ubuntu.com/Fridge/Calendar
[13:32] <Mez> nhandler: 20/2 - "busy"
[13:32] <Mez> nhandler: I have only read access...
[13:33] <nhandler> I think I know what happened. Whoever added the Jaunty Weekly Release Meetings told gcal to "mark me as busy"
[13:33]  * Mez shrugs
[13:34] <Mez> nhandler: they've also changed the times that it was (it was originally the same times as the meeting, now changed to be different
[13:35] <jpds> Mez: Best talk to boredandblogging.
[13:36] <nhandler> You can also try pinging robbiew about it. I believe you can modify events that you add
[13:36] <geser> just noticed the descriptions for events have a google map link. It's really useful if you don't know where to find e.g. #ubuntu-meeting :)
[13:36] <jpds> ...who's not around at the moment.
[13:36] <nhandler> geser: That just got added in the most recent gcal update
[13:36] <Mez> jpds: yeah, I noticed
[13:54] <mok0> StevenK: thanks! Much appreciated!
[16:40] <btQuark> http://brainstorm.ubuntu.com/idea/16430/
[16:41] <btQuark> has someone already seen jan-steinhoffs driver or actually brought it to wokr?
[17:15] <LaserJock> anybody know of Ubuntu is likely to be a GSoC mentoring organization this year?
[17:15] <Mithrandir> I'd be surprised if it wasn't
[17:15] <LaserJock> it wasn't last year I don't think
[17:16] <Mithrandir> hm, indeed.
[17:16] <LaserJock> I've got 2 Edubuntu projects that I think would be perfect for it
[17:23] <ScottK> I'm pretty sure Kubuntu would have stuff too.
[17:38] <apw> pitti, ok pushed up a re-write of the suspend/resume apport support to  lp:~apw/apport/suspend-resume-pt3, this now includes a move to common messages for cli, gtk, and qt, to simplify internationlisation and has your other internationalisation concerns sorted i hope.
[20:54] <davidrod`> When I use network-manager on kde all the boxes are ghosted and it is broken.  When I use it on ubuntu it forgets my setting with a reboot.  I am sure that this is a bug
[20:56] <davidrod`> I wanted to change user to root but it won't let me.  I was thinking that there must be some permissions wrong, but on what files and where?  With BSD they tell you. With Ubuntu this is a mystery
[21:10] <ScottK> davidrod`: What release are you using?
[21:31] <davidrod`> Linux david-laptop 2.6.24-a21-generic #1 SMP Tue Oct 21 23:43:45 UTC 2008 i686 GNU/Linux
[21:35] <davidrod`> It is a pain because I have no other reason to move away from ubuntu right now.  Is there some hack I can perform to write my network details into a file?
[21:39] <ion_> 0) Is that really an Ubuntu kernel? I don’t remember there being an “a21” in the version field. I might be wrong, of course. 1) Can you try upgrading to a newer Ubuntu release? 2) You can use ifupdown instead of network-manager by configuring /etc/network/interfaces.
[21:40] <ScottK> davidrod`: Alternatively since you're using KDE, use KNetworkManager.
[21:41] <davidrod`> Linux david-laptop 2.6.24-21-generic #1 SMP Tue Oct 21 23:43:45 UTC 2008 i686 GNU/Linux
[22:04] <davidrod`>  I couldn't find any documentation about how to use WEP with ifup.  When I type knetworkmanager nothing happened.
[22:06] <davidrod`> Is there no readme file anyway in /usr
[22:18] <ScottK> davidrod`: KNetworkManager is part of the default kubuntu-desktop.  It should be a point-click thing.
[22:18] <ScottK> davidrod`: Also this is not a support channel so for further help you should probably ask in #kubuntu.
[22:32] <davidrod`> It has been critised with ubuntu that if it does not work out of the box, what then?  My wireless has been broken for months. There is no docs. no FAQ.  everything is aimed so low, that unless I have been developping the kernel for years I cannot find any middle ground.  I asked in #Ubuntu several times, over weeks and months.  In there they just shout "Try blackbox. NO. Fluxbox. EDuntu. Gnome. KDE. etc. etc.
[22:35] <ScottK> davidrod`: I can't tell you for sure.  It worked out of the box on Hardy for me.
[22:42] <shtylman_> davidrod: you don't use wep with ifup
[22:42] <shtylman_> davidrod: you use wep with iwconfig, ifup and down just bring up or tear down interfaces respectively
[22:43] <shtylman_> davidrod: chances are...if you can't find documentation on how to do something like that and google doesnlt help, you may be trying to pair the wrong two things and ask the question differently
[22:54] <davidrod`> well ifconfig wlan0 up does exactly the same?
[22:56] <davidrod`> I am thinking of abandonning ubuntu and going to Gentoo simply because of my wireless
[22:56] <shtylman_> davidrod: nope, iwconfig is for configuration
[22:57] <shtylman_> davidrod: ok, I mean...I think you should use what you like...but if you are abandoning ubuntu because stuff 'doesn't work out of the box' then gentoo really won't be right for you either
[22:59] <davidrod`> I don't want out of the box. I want to be able to set configuration files myself. On BSD each interface has it own file. Good idea. Manuals and FAQ explain what to do.  I hope Gentoo won't think that I am unable to type
[23:01] <shtylman_> davidrod: you can set configuration files all you want... I really don't see what your complaint is...and as stated before, its not development related so best ask in one of the support channels
[23:01] <ion_> interfaces(5)


[00:01] <fta> asac, http://paste.ubuntu.com/16300/
[08:17]  * asac getting coffee
[08:40] <[reed]> coffee is for the weak :p
[08:48] <asac> [reed]: indeed ;)
[09:38] <gnomefreak> i really really hate computers! i have to go out and spend money on my POS laptop
[10:44] <asac> POS?
[10:46] <gnomefreak> peice of shit
[10:46] <gnomefreak> piece even
[10:46] <gnomefreak> 256x256 is normal icon size?
[10:52] <gnomefreak> asac: do you remember the link i gave you for sunbird icon by chance?
[10:52]  * gnomefreak cant find it
[11:10] <asac> gnomefreak: which sunbird icon?
[11:11] <asac> (obviously i forgot :))
[11:11] <gnomefreak> the bird one
[11:11] <gnomefreak> bird holding calendart
[11:11] <gnomefreak> -t
[11:11] <asac> hmm .. .so  we still dont have that?
[11:12] <asac> thought it was already committed to bzr
[11:12] <gnomefreak> asac: oh might have been let me check
[11:13] <gnomefreak> ah looks like it was
[11:14] <asac> ok fine
[11:14] <asac> i think i copy it from the source tree to the final package
[11:14] <gnomefreak> do you want me to spin it and upload to mt PPA
[11:14] <asac> gnomefreak: why?
[11:14] <asac> 0.8 is in intrepid
[11:14] <gnomefreak> um no it isnt
[11:14] <asac> you can upload it as a backport to mt ...
[11:14] <asac> but i would suggest to upload it to -backports for real then
[11:14] <asac> get in touch with jdong
[11:14] <gnomefreak>  0.7+nobinonly-0ubuntu2 0
[11:14] <gnomefreak>         500 http://de.archive.ubuntu.com intrepid/universe Packages
[11:15] <gnomefreak> asac: i havent heard back frm him on anything yet
[11:15] <gnomefreak> its kind of getting old
[11:15] <asac> gnomefreak: sunbird 0.8 should already be in PPA
[11:15] <asac> isnt it?
[11:16] <gnomefreak> not with latest bzr update
[11:17] <asac> gnomefreak: ok uploading to intrepid
[11:17] <gnomefreak> - update debian/patches/bzXXX_calendar_missing_EXTRA_SCRIPTS_install.patch  this is in both bzr and PPA build
[11:17] <gnomefreak> asac: thanks
[11:17] <asac> gnomefreak: that is 0.8
[11:17] <asac>  lightning-sunbird - 0.8+nobinonly-0ubuntu0mt804     asac 2008-04-29  Published  Hardy  Web
[11:17] <asac> thats what is in PPA
[11:17] <asac> uploading that version to intrepid now
[11:18] <gnomefreak> yes but icon is still calendaer and that line is the only thing from changelogs that is same in bzr PPA
[11:18] <gnomefreak> after pushing to bzr you never rebuilt for PPA or didnt push it to PPA
[11:18] <asac> not sure
[11:18] <asac> maybe the icon is still missing
[11:18] <asac> well see
[11:19] <asac> uploading whatever i have in bzr here now
[11:19] <gnomefreak> i just installed the one from PPA
[11:20] <gnomefreak> be back in a minute or 3 time for a smoke and try to relax this ops council vs users is gettong old
[11:29] <armin76> bumb
[11:30] <asac> dump
[12:28] <asac> crimsun: there? about libflashsupport/PA in intrepid/hardy.
[12:31] <asac> crimsun: wonder what you did to fix this in intrepid.
[12:31] <asac> crimsun: what parts of it could be done for hardy?
[12:34] <gnomefreak> asac: hardys is done
[12:35] <gnomefreak> ready for backports but havent sen anyone to push
[12:35] <gnomefreak> gutsy is my concern since libflashsupport wasnt in repos until hardy
[12:36] <asac> he? what are you talking about?
[12:37] <asac> we need to do something in hardy-updates (not -backports)
[12:37] <asac> as the sound experience doesnt rock right now
[12:40] <gnomefreak> asac: cant add flash to updates
[12:41] <gnomefreak> AFAIK it doesnt fit requirments since it adds features
[12:42] <gnomefreak> asac: either way flash 10 is done let me know i can change the changelog a bit and it can go into updates but i see it more of a backport and when i asked crimsun about it he told me to go ahead and backport it
[12:47] <asac> gnomefreak: well. thats all a matter of priotization. if it fixes our pulseaudio issues its worth to pursue and look at it
[12:47] <gnomefreak> asac: http://pastebin.mozilla.org/449225 that is the updated changelog for flash 10 i left out bug number just because last i heard it will close bug even if in PPA
[12:47] <asac> my question to crimsun was to understand what is going on ... not if we can or want to do it
[12:47] <gnomefreak> asac: it does fix PA issues
[12:48] <gnomefreak> asac: the changelog has it in it see above pastebin
[12:48] <asac> gnomefreak: its in the changelog. i can read on my own. but changelog doesnt give a good rational - need more info -> thus the question ;)
[12:48] <gnomefreak> ah ok
[13:28] <gnomefreak> asac: do we support filezilla or is that someone else that supports it? im think as far as extension team
[13:40] <asac> what is filezilla?
[13:40] <asac> i think its not related to mozilla
[13:41] <asac> Depends: filezilla-common (= <IP_ADDRESS>-0ubuntu3), libc6 (>= 2.7-1), libgcc1 (>= 1:4.1.1-21), libgnutls13 (>= 2.0.4-0), libidn11 (>= 0.5.18), libstdc++6 (>= 4.1.1-21), libwxbase2.8-0 (>= <IP_ADDRESS>), libwxgtk2.8-0 (>= <IP_ADDRESS>)
[13:41] <asac> so no ... no mozilla
[13:41] <asac> none of our apps
[13:41] <gnomefreak> its an extension for either ff ot tb i thought
[13:41] <asac> nope
[13:42] <asac> look at pkg decription
[13:42] <gnomefreak> on never mind i was thinkgign of something else
[13:42] <gnomefreak> i just did
[13:42] <gnomefreak> its ftp i thought it was that tb one that deals with files
[13:42] <gnomefreak> let me get it i cant recall name off hand
[13:43] <gnomefreak> thunderbird-quickfile is it
[13:46] <asac> yes
[13:47] <asac> do we have that in the archive? otherwise we should add that to the to-package-extension list
[13:47] <asac> if it has a proper license
[13:48] <gnomefreak> yes we do
[13:48] <gnomefreak> its in universe IIRC
[13:48] <gnomefreak> 500 http://de.archive.ubuntu.com intrepid/universe Packages
[13:48] <gnomefreak> yep uni
[13:50] <gnomefreak> asac: before we take it for extensions team if you are wanting to might want to talk to maintainer Adrien
[13:50] <gnomefreak> ok ill be back later i have to go get parts for my laptop so maybe i can get it going today, just not sure what version i want to install on it
[15:09] <asac> cwong1: back from holiday?
[15:09] <asac> unfortunate timing ;)
[15:11] <asac> cwong1: so a quick status update: we have ffox RC1 in -proposed and its mostly ready. we need another day of testing because of a langpack update, but then its ready to go
[15:11] <asac> this means that we will break midbrowser unless we come up with a package by then
[15:12] <asac> if we get a release today, we can hold back ffox for one more day so midbrowser gets some basic proposed testing too
[15:12] <asac> if not, it just will tear apart :/
[15:12] <asac> well ... apt-get upgrade will hold the xulrunner upgrade back, but if you dist-upgrade you will get midbrowser removed from your system
[15:12] <asac> cwong1: ^^
[15:13] <asac> jimmy_: ^^
[15:46] <asac> bug 203019
[16:02] <fta2> hm, ppa are building for intrepid. at last
[16:10] <asac> bug 220263
[16:20] <asac> bug 231459
[17:24] <cwong1> asac: ping
[17:25] <asac> cwong1: hi!
[17:25] <cwong1> asac: I am back
[17:25] <asac> cwong1: great! i really missed you ;)
[17:26] <cwong1> asac: what do I need to do now?
[17:26] <asac> cwong1: QA the merge branch .... then merge that to master ... then plumber a release out of it in hardy branch
[17:27] <asac> rememberr to bump xulrunner-1.9 min versions for both build- and normal depends to >= 1.9~rc1
[17:27] <asac> cwong1: if you need a rc1 xulrunner-1.9 package to test get it from mozillateam PPA
[17:27] <asac> or hardy-proposed
[17:27] <cwong1> asac: OK I will work on it.
[17:27] <asac> maybe makes sense to get the hardy-proposed packages
[17:28] <asac> you can enabled hardy-proposed in system -> administration -> software sources on ubuntu :)
[17:28] <cwong1> what is the path to hardy-proposed?
[17:28] <asac> cwong1:
[17:28] <asac> deb http://de.archive.ubuntu.com/ubuntu/ hardy-proposed restricted main multiverse universe
[17:28] <asac> deb-src http://de.archive.ubuntu.com/ubuntu/ hardy-proposed restricted main multiverse universe
[17:28] <asac> those are the lines i am using
[17:28] <cwong1> ok
[17:28] <asac> you can replace the mirror as you like obviously
[17:28] <cwong1> I will work on it.
[17:28] <asac> cwong1: good.
[17:29] <asac> please do thorough QA because midbrowser wont have much time in -proposed left before the whole heap has to be pushed to -updates ;)
[17:29] <cwong1> ok
[17:30] <asac> cool
[17:55] <geser> Hello, I'm trying the firefox 3.0rc1 packages out from hardy-proposed. Has someone else display problems when visiting http://wiki.debian.org/? I'm on AMD64.
[18:08] <asac> geser: no. what kind of?
[18:13] <geser> asac: I opened a new tab: http://members.ping.de/~mb/Screenshot.png
[18:14] <geser> after switching to my irc client and back to FF and moving the mouse around: http://members.ping.de/~mb/Screenshot-1.png
[18:16] <geser> I've seen this till now only on wiki.debian.org
[18:17] <asac> geser: please paste your xorg.conf
[18:17] <asac> geser: and grep for Offscreen in Xorg.0.log
[18:17] <asac> maybe grep -i OffscreenPixma /var/log/Xorg.0.log
[18:19] <geser> asac: http://paste.ubuntu.com/16438/
[18:20] <geser> and http://paste.ubuntu.com/16439/ for the grep output
[18:36] <asac> hmm
[18:49] <asac> geser: could you look if you received any X11 driver or kernel driver updates from -proposed?
[18:49] <asac> is cairo a new version there?
[18:50] <asac> maybe double check using strace -f -eopen firefox that you dont pull in any /usr/local libs or something :)
[18:57] <geser> asac: libcairo2 and xserver-xorg-video-radeonhd are from hardy
[18:58] <geser> kernel is linux-image-2.6.24-17-generic from hardy-updates
[19:00] <geser> grepping the output from strace for /local/ shows only non-existing files
[19:03] <fta> lsof -p `pidof firefox`
[19:03] <fta> what cairo is loaded ?
[19:04] <jimmy_> asac: ping
[19:05] <geser> firefox 20298 michael  mem    REG              254,0   437784  517696 /usr/lib/libcairo.so.2.17.3
[19:05] <geser> firefox 20298 michael  mem    REG              254,0    44704  517295 /usr/lib/libpangocairo-1.0.so.0.2000.1
[19:07] <fta> seems correct
[19:19] <jimmy_> asac: u there?
[20:00] <jcastro> fta: know anybody tracking packaging Flock?
[20:38] <Jazzva> asac: Did you upload liferea merge? I can't remember if you were fine with the diffs, or did I need to provide something more...
[20:42] <asac> Jazzva: hmm
[20:42] <asac> cant remember either
[20:42] <asac> jimmy_: yes
[20:44] <Jazzva> asac: The last I remember is that you asked why I removed .po files from the debdiff. I was told on #ubuntu-motu that it's junk from MoM, and that no .po files should be left in the debdiff. I suppose it's because we use rosetta for translations management. All debdiffs I made for previous merges were with removed contents of .po files.
[20:45] <Jazzva> asac: So, I suppose that afaik  liferea-debian-ubuntunew-without-po.debdiff should be good. But, I'm not 100% sure, as I'm still learning :)
[20:45] <asac> Jazzva: yes, most likely. sorry. my bad. bug id?
[20:45] <Jazzva> asac: bug 228827
[20:46] <Jazzva> No problem. Thanks for the help :)
[20:49] <Jazzva> BTW, does anyone know if it's possible (and how) to disable bookmarks showing up ff3 smart bar? Looked through preferences, about:config, googled it, but no info found...
[20:53] <Some_Person> why is ff3rc1 not in backports?
[20:53] <asac> Some_Person: backports for what?
[20:53] <asac> gutsy?
[20:54] <Some_Person> hardy
[20:54] <Some_Person> its only in proposed
[20:54] <asac> Some_Person: for hardy it will be in -updates soon ... its currently getting thorough testing in -proposed
[20:54] <Some_Person> i hope so
[20:55] <asac> its not just firefox that needs testing in this transition... all the applications that use its rendering engine too and so on
[20:55] <asac> so better safe than sorry.
[20:55] <Some_Person> im tired of beta5, but i dont want to add proposed repos
[20:55] <Some_Person> i understand
[20:55] <asac> the post-final releases will be much easier and will roll more in time
[20:56] <Some_Person> the 2 unofficial repos for rc1 are broken
[20:56] <asac> going back to release on same day policy hopefully soonish
[20:56] <asac> Some_Person: please test the -proposed archive
[20:56] <asac> if not, dont complain if it breaks for you when it gets to -updates. :)
[20:56] <Some_Person> what about the other stuff in -proposed? isn't it supposed to be unstable?
[20:57] <asac> Some_Person: only things that are ment to go in as stable release updates (SRU) are permitted int
[20:57] <asac> and every package that gets into -proposed gets a quick look by an archive admin
[20:57] <asac> of course its not as stable as just -updates. but should be fairly stable
[20:57] <Some_Person> do you think its stable enough for production use?
[20:57] <asac> but again, as always: your risk
[20:58] <asac> Some_Person: depends ;)
[20:58] <asac> for me its rock solid on my production system
[20:58] <Some_Person> what about the other 100s of updates? are they safe to install?
[20:59] <asac> Some_Person: well ... if they were 100% safe to install, we would push them to -updates directly
[20:59] <asac> but -proposed has high bars :)
[20:59] <Some_Person> i understand that, but how likely are they to crash my system and break everything?
[20:59] <asac> Some_Person: nobody can answer that question
[21:00] <Some_Person> is it easy to revert if i try it?
[21:00] <asac> no ... downgrading is usually not easy.
[21:00] <asac> you can add -proposed to the sources.list
[21:01] <asac> then apt-get update
[21:01] <asac> and then just apt-get install firefox-3.0 and xulrunner-1.9
[21:01] <asac> that should select only the required packages
[21:01] <asac> then disable proposed again
[21:01] <asac> but well. its your decision ;)
[21:01] <asac> enough from me on this
[21:05] <Some_Person> i think i'll wait
[21:06] <Some_Person> thank you
[21:08] <asac> fair enough
[21:41] <asac> bug 223891
[21:49] <asac> jimmy_: did you disappear?
[21:50] <asac> :)
[21:50] <asac> still here for a short while
[22:00] <jimmy_> asac: u still here?
[22:01] <asac> jimmy_: sure
[22:01] <asac> battery is running low ... but probably have 30 minutes left :)
[22:02] <fta> asac, any comment on the new mozclient ?
[22:02] <asac> fta: you did uncommit the other thing right?
[22:02] <asac> hard for me to look at what changed :(
[22:02] <fta> yes
[22:02] <jimmy_> ok, i was going to get the xulrunner-rc1 from the hardy propose repository, but the repository only have builds for i386 and amd64, no lpia
[22:02] <asac> fta: why do you do that ;)?
[22:02] <jimmy_> i can't retrieve that in my target enviroment
[22:02] <asac> anyway. havent looked at the latest code.
[22:03] <fta> asac, full rewrite, so the previous commit was useless
[22:03] <asac> still its nice to have evolution
[22:03] <asac> ;)
[22:03] <asac> jimmy_: take the one from ~mozillateam PPA
[22:03] <asac> that has lpia afaict
[22:04] <asac> jimmy_: is there no -proposed on ports.ubuntu.com?
[22:04] <asac> jimmy_: https://edge.launchpad.net/ubuntu/hardy/+source/xulrunner-1.9/1.9~rc1+nobinonly-0ubuntu1~8.04.1
[22:04] <asac> its build on lpia there
[22:05] <fta> asac, sure but the diff was bigger that the src and not interesting
[22:06] <jimmy_> asac: i used the respository link you gave to carl earlier
[22:06] <asac> ok i see you are tough ;) let me pull --overwrite it
[22:06] <asac> fta: ^^
[22:06] <asac> jimmy_: yeah ... look at your sources.list
[22:06] <jimmy_> when i do a apt-get update, i get the following:
[22:06] <asac> use the same form for the host
[22:07] <jimmy_>   404 Not Found [IP: <IP_ADDRESS> 911]
[22:07] <jimmy_> Err http://de.archive.ubuntu.com hardy-proposed/main Packages
[22:07] <jimmy_>   404 Not Found [IP: <IP_ADDRESS> 911]
[22:07] <jimmy_> Hit http://archive.ubuntu.com hardy/multiverse Sources
[22:07] <asac> i think lpia is on ports.ubuntu.com
[22:07] <jimmy_> Err http://de.archive.ubuntu.com hardy-proposed/multiverse Packages
[22:07] <jimmy_>   404 Not Found [IP: <IP_ADDRESS> 911]
[22:07] <jimmy_> Err http://de.archive.ubuntu.com hardy-proposed/universe Packages
[22:07] <jimmy_>   404 Not Found [IP: <IP_ADDRESS> 911]
[22:07] <asac> yeah
[22:07] <jimmy_> Fetched 2075kB in 2min2s (16.9kB/s)
[22:07] <asac> use ports.ubuntu.com
[22:07] <jimmy_> W: Failed to fetch http://de.archive.ubuntu.com/ubuntu/dists/hardy-proposed/restricted/binary-lpia/Packages.gz  404 Not Found [IP: <IP_ADDRESS> 911]
[22:07] <jimmy_> W: Failed to fetch http://de.archive.ubuntu.com/ubuntu/dists/hardy-proposed/main/binary-lpia/Packages.gz  404 Not Found [IP: <IP_ADDRESS> 911]
[22:07] <asac> use ports.ubuntu.com
[22:07] <jimmy_> W: Failed to fetch http://de.archive.ubuntu.com/ubuntu/dists/hardy-proposed/multiverse/binary-lpia/Packages.gz  404 Not Found [IP: <IP_ADDRESS> 911]
[22:07] <asac> :-P
[22:07] <jimmy_> W: Failed to fetch http://de.archive.ubuntu.com/ubuntu/dists/hardy-proposed/universe/binary-lpia/Packages.gz  404 Not Found [IP: <IP_ADDRESS> 911]
[22:07] <jimmy_> asac: ok
[22:07] <asac> jimmy_: paste alarm ;) => paste.ubuntu.com
[22:07] <asac> !paste
[22:07] <asac> :-P
[22:08] <asac> ok let me know if ports.ubuntu.com works
[22:08] <jimmy_> trying now
[22:11] <jimmy_> asac: no, doesn't work, is it deb http://ports.ubuntu.com/ubuntu/ hardy-proposed restricted main multiverse universe?
[22:11] <asac> jimmy_: look at how the other lines look like
[22:11] <asac> the host part most likely is different
[22:12] <asac> just remove the ubunu/ part
[22:12] <asac> and you only need main for xulrunner
[22:12] <asac> not restricted multiverse universe
[22:12] <asac> keeping universe shouldnt hurt though
[22:13] <jimmy_> asac: ok
[22:14] <jimmy_> asac: i think it is downloading now :)
[22:14] <asac> jimmy_: great
[22:19] <cwong1> asac: Have you integrate Jimmy's propose fixes for download dir (XDG) and URL bar popup position into Xulrunner rc1?
[22:21] <asac> cwong1: no ... ill upload to mobile PPA
[22:21] <asac> actually i am not sure if i have received something final yet
[22:22] <asac> laste discussion i remember was about how to get XDG paths through XPCOM
[22:22] <cwong1> jimmy_:  you there?
[22:23] <asac> cwong1: thats what the bug is about :)
[22:23] <jimmy_> asac: i have the final code ready
[22:24] <cwong1> asac: can you review his code and see if they are ok. If so, please upload to mobile ppa.
[22:24] <jimmy_> asac: if u want to review it, i can paste in the pastebin for review
[22:24] <jimmy_> then i'll commit it, so  you can integrate it
[22:25] <asac> cwong1: well ... i'd rather bake that a bit on master first. hardy ppa is kind of production archive ... we should be careful about what goes there
[22:26] <asac> for now i will update PPA with the current patch ... to be safe
[22:26] <asac> we should try the new patch in RC2 PPA ... and in real ubuntu archive for final 1.9
[22:27] <asac> we start with RC2 in a few days. so not that much time in between
[22:27] <asac> jimmy_: please post a copy of the patch to th ebug
[22:27] <asac> as attachment
[22:27] <asac> its easier to review there than in moblin git
[22:27] <jimmy_> ok
[22:28] <cwong1> asac: so what do you want us to do once we verify the mibrowser-rc1 works with Xulrunner-rc1?
[22:31] <cwong1> asac: I know how to upload package to ubuntu mobile ppa but if you want me to upload the rc1 midrowser to other repo. please send me instruction.
[22:33] <jimmy_> asac: see https://bugs.launchpad.net/moblin-browser/+bug/217438 for the uploaded patch
[22:34] <asac> wait a minute have to swtich location
[22:38] <asac> cwong1: when rc1 works, merge it to master, then from there to hardy
[22:38] <asac> then QA the package
[22:38] <asac> if thats done let me know
[22:38] <asac> at best keep changelog at UNRELEASED
[22:38] <asac> i will then do the upload and send you the release patch
[22:38] <asac> so you can redo that on top
[22:41] <asac> cwong1: UNRELEASED means like:
[22:41] <asac> pulseaudio (0.9.10-1ubuntu1) UNRELEASED; urgency=low
[22:41] <cwong1> asac: ok.  Just to let you know that the hardy branch is not what I used to do my recent releases.  We have changed the release process about a month ago. But I will merge the changes to the hardy branch like you said.
[22:42] <asac> that would be awesoke
[22:42] <asac> who does the hardy branch now?
[22:42] <cwong1> It's Beta 2.  Couple months old.
[22:51] <jimmy_> asac: i just build the midbrowser again the xulrunner1.9rc1, the gconf seems to broken, is the gconf stuff integrated?
[23:04] <asac> cwong1: if hardy branch is abandoned then dont bother. thought itw as up to date
[23:04] <asac> i can just make the package without it
[23:05] <asac> but we should think about the future of that branch i guess then
[23:05] <asac> jimmy_: no its not in there
[23:05] <asac> jimmy_: if it works in the in-source xulrunner case
[23:05] <asac> and you havent committed your gconf improvements to master yet, i can sort it out for the package before i upload
[23:06] <jimmy_> asac: what do you mean by not commited to master yet? i thought the gconf stuff is in master already
[23:07] <asac> jimmy_: the original one yes. not your improvements
[23:07] <asac> err sorry
[23:07] <asac> i miscontexted this
[23:07] <asac> all is fine
[23:07] <asac> :)
[23:08] <jimmy_> asac: yeah, because i rechecked everything in after the improvements, so all are good
[23:09] <asac> jimmy_: well. its not perfect we have to move the gnome requiring code in a dynamic component and put that into xulrunner -gnome-support package
[23:09] <asac> but thats a different story
[23:10] <asac> so yes, thats my task i guess. unless you can move the gconf code to a separate directory and make a non-libxul component out of it ;)
[23:11] <jimmy_> asac: so are you going to checkin the patched xulrunner for us to test before commiting, or go ahead and commit the rc1 upgrade to master?  we can then create a package and have the QA test it
[23:12] <asac> jimmy_: sorry if you misunderstood. all i want in moblin is a merge of merge branch to master
[23:13] <asac> i will update the xulrunner package in PPA mobile
[23:13] <asac> and update the gconf patch in there
[23:13] <asac> if there are problems ill let you know and push the build somewhere for testing. but i dont think there should be any additional issues on top
[23:13] <jimmy_> asac: ok, we just want to do some kind of testing that the merge was good before we merge it
[23:14] <jimmy_> asac: i dun see any other issues so far
[23:47] <asac> jimmy_: ok good
[23:48] <asac> jimmy_: if you think that the merge is ok, send a mail. ill package it up tomorrow and steer it in tomorrow then
[23:48] <asac> but please give me an ack today ;)
[23:49] <jimmy_> asac: carl will merge that into master tomorrow
[23:59] <asac> cwong1: could you please merge today ... otherwise i cant upload until the day after tomorrow
[23:59] <asac> which would mean thu and would be really bad


[11:01] <mvo> jibel: just FYI, I'm currently working on substancially simplifiying the config required to setup the auto-upgrade-test profiles
[11:19] <jibel> mvo, ok thanks.
[11:19] <jibel> mvo, I moved the upgrade tests to wazn this morning
[11:20] <jibel> mvo, I'm doing a couple of manual run to check that everything is ok and will reenable the jenkins job after lunch
[11:21] <jibel> mvo, how was your flight back BTW ?
[11:29] <jibel> mvo, cool, it works. I'll add support for amd64 and deploy it on aldebaran
[12:09] <mvo> jibel: flight back was good, I managed to sleep quite a bit
[12:10] <mvo> jibel: I have amd64 support in trunk mostly ready, hope this message makes it to you in time for not duplicating effort
[12:10] <mvo> jibel: sorry for the slowness, I was a lunch
[12:20] <mvo> jibel: lp:update-manager trunk has a server-amd64 profile now
[12:27] <jibel> mvo, ah nice, I'll check it out, thanks
[13:14] <jibel> mvo, I think BaseImage should be set to SourceRelease instead of TargetRelease by default,
[13:15] <jibel> mvo, otherwise a lucid and an oneiric upgrade to precise will have the same baseimage, isn't it ?
[13:19] <mvo> jibel: yeah, indeed, sorry for that, fixed in bzr now
[13:29] <jibel> mvo, no problem.
[13:29] <jibel> mvo, it takes 3 min to test a server upgrade :)
[13:29] <jibel> mvo, I'll try with a tmpfs and see if it can go faster
[13:29] <mvo> jibel: can I get access to this machine as well please ;) ?


[07:05] <ara> good morning :)
[08:35] <jpds> ara: \o/ morning
[08:35] <ara> jpds: hey!
[08:36] <jpds> No videos of your karaokes have surfaced (yet).
[08:37] <jpds> Hmm: http://www.youtube.com/user/boredandblogging
[09:17] <ara> eeejay: hey! how was your trip back?
[10:04] <eeejay> hey ara :)
[10:05] <eeejay> ara: good, back in israel, packing, working, saying goodbye to everyone.
[10:05] <ara> hey eeejay :)
[10:05] <ara> eeejay: when are you leaving to US?
[10:05] <eeejay> ara: early thursday morning
[10:06] <ara> eeejay: wow, lots of travelling ;-)
[10:06] <eeejay> ara: yup :)
[10:06] <ara> eeejay: I am working on the pidgin branch, creating a common API for buddy and modifying the scripts
[10:06] <eeejay> ara: excellent! you know what i am thinking?
[10:06] <ara> eeejay: I hope to be able to commit something working later today
[10:07] <ara> eeejay: what are you thinking?
[10:07]  * ara is scared now
[10:07] <eeejay> ara: at uds i sat in IM session, and there is a decision to replace pidgin with empathy in karmic :)
[10:07] <eeejay> ara: and a good reason to be scared
[10:07] <ara> eeejay: hehehee
[10:08] <ara> eeejay: yes, I saw that decision as well
[10:08] <eeejay> ara: the good news is that we have the buddy code, which was the harder part
[10:08] <ara> eeejay: That's why I think this is the last thing I am going to work with pidgin by now
[10:08] <ara> eeejay: once the buddy api is working, bye, bye pidgin :D
[10:09] <ara> eeejay: also, it is very likely that banshee is going to replace rhythmbox in karmic
[10:09] <eeejay> ara: right. and more file moving.. we will move the buddy stuff out of pidgin to somewhere more general i guess?
[10:10] <eeejay> ara: hah, lucky we don't have a rhythmbox script, do we?
[10:10] <ara> eeejay: yes, to buddy.py and out of pidgin, I guess
[10:10] <ara> eeejay: yes :D
[10:13] <ara> eeejay: but yes, empathy automation is going to be more or less trivial, the worse part of these scripts is dealing with xmpp, msn, etc. libraries
[10:13] <ara> eeejay: and that's working (more or less.. .:P)
[10:15] <eeejay> ara: yeah, empathy uses telepathy, which is a solid and active upstream project, they might have some good unit tests on the actual transports that could be useful
[10:15]  * eeejay looks
[10:27] <eeejay> ara: interesting, i just learned that python-twisted has packages for all these protocols
[10:27] <eeejay> python-twisted-words
[10:28] <eeejay> hm, i guess next time.
[10:28] <ara> eeejay: :D
[10:29] <eeejay> ara: xmpp/msn/icq/aim/icq
[10:29] <eeejay> er, irc
[11:09] <ara> eeejay: running your suite as
[11:09] <ara> PYTHON_PATH=. ./bin/ubuntu-desktop-test -f pidgin/pidgin_messaging.xml
[11:09] <ara> should be enough to get the paths correctly, shouldn't it?
[11:09] <eeejay> yeah
[11:09] <eeejay> ara: and we need to fix the paths thing too
[11:11] <ara> eeejay: I get the following error http://paste.ubuntu.com/185544/
[11:12]  * eeejay tries
[11:14] <eeejay> ara: PYTHONPATH, not PYTHON_PATH :)
[11:19] <ara> eeejay: hehehe
[11:19] <ara> :D
[11:31] <eeejay> hi schwuksy
[11:31] <eeejay> schwuk: aren't you on holiday today?
[11:32] <eeejay> schwuk: could i peak at your checkbox/udt branch for inspiration?
[12:25] <eeejay> headed out for a bit
[12:40]  * ara -> lunch
[14:38] <cr3> hey dudes!
[15:20] <fader_> cr3: I guess the Spaniards let you out of the country after all?  We had bets on you causing an international incident and getting arrested.
[15:21] <cr3> fader_: I had to bribe them with the netbooks manjo gave me, which turns out well because that means less work for me
[15:21] <fader_> Everybody wins!
[17:38] <eeejay> hello, clowns


[15:30] <cpaelzer> here in a minute
[15:30] <ddstreet> o/
[15:31] <doko> hi
[15:31] <cpaelzer> #startmeeting Weekly Main Inclusion Requests status
[15:31] <meetingology> Meeting started Tue Dec  1 15:31:40 2020 UTC.  The chair is cpaelzer. Information about MeetBot at http://wiki.ubuntu.com/meetingology.
[15:31] <meetingology> Available commands: action commands idea info link nick
[15:31] <cpaelzer> ddstreet: doko: sarnold: jamespage: didrocks999 - hi
[15:32] <ddstreet> o/
[15:32] <cpaelzer> we had no past weeks action items, so let us skip that
[15:32] <sarnold> good morning
[15:32] <cpaelzer> also no new MIRs in our inbox
[15:32] <didrocks999> hey
[15:32] <cpaelzer> nor are there recent updates to incomplete MIRs
[15:32] <cpaelzer> what has some content thou is component mismatches
[15:33] <cpaelzer> #topic current component mismatches
[15:33] <cpaelzer> #link https://people.canonical.com/~ubuntu-archive/component-mismatches-proposed.svg
[15:33] <cpaelzer> #link https://people.canonical.com/~ubuntu-archive/component-mismatches.svg
[15:33] <cpaelzer> doko: postgresql-13 is ready to migrate except for perl - I think this could be promoted now in hirsute
[15:34] <cpaelzer> doko: what do you think and coudl you do that?
[15:34] <cpaelzer> related bug (to post updates) is https://bugs.launchpad.net/ubuntu/+source/postgresql-13/+bug/1902059
[15:35]  * cpaelzer is waiting a bit to let this topic conclude before starting the next one we see in mismatches
[15:35] <doko> sure. will do. please note that we also need postgresql-12 for the perl transition, afaics
[15:35] <cpaelzer> doko: PG-12 is intended to be removed
[15:35] <cpaelzer> doko: hence we didn't care for it
[15:35] <cpaelzer> doko: it is already out of Debian testing
[15:35] <cpaelzer> but I didn't track how many reverse dept we'd have left
[15:36] <doko> yes, we can remove it after perl mirates ...
[15:36] <cpaelzer> doko: should I analyze and file a removal for hirsute ?
[15:36] <cpaelzer> oh ok, so perl can migrate without postgresql-12 being either removed or fixed then?
[15:36] <doko> let's discuss this later, not MIR stuff
[15:36] <cpaelzer> ok WFM
[15:37] <cpaelzer> next MIR topic node-jquery->sizzle
[15:37] <sarnold> how did node-jquery get into main?
[15:37] <cpaelzer> exactly
[15:37] <cpaelzer> it is unsubscribed http://reqorts.qa.ubuntu.com/reports/m-r-package-team-mapping.html
[15:37] <cpaelzer> and if I read https://launchpad.net/ubuntu/+source/node-jquery/+publishinghistory correctly we'd have to ask vorlon
[15:37] <sarnold> I can't spot a bug
[15:37] <sarnold> https://bugs.launchpad.net/ubuntu/+source/node-jquery/+bugs?field.searchtext=&orderby=-importance&search=Search&field.status%3Alist=NEW&field.status%3Alist=OPINION&field.status%3Alist=INVALID&field.status%3Alist=WONTFIX&field.status%3Alist=EXPIRED&field.status%3Alist=CONFIRMED&field.status%3Alist=TRIAGED&field.status%3Alist=INPROGRESS&field.status%3Alist=FIXCOMMITTED&field.status%3Alist=FIXRELEASED
[15:37] <sarnold> &field.status%3Alist=INCOMPLETE_WITH_RESPONSE&field.status%3Alist=INCOMPLETE_WITHOUT_RESPONSE&assignee_option=any&field.assignee=&field.bug_reporter=&field.bug_commenter=&field.subscriber=&field.tag=&field.tags_combinator=ANY&field.status_upstream-empty-marker=1&field.has_cve.used=&field.omit_dupes.used=&field.omit_dupes=on&field.affects_me.used=&field.has_patch.used=&field.has_branches.used=&field
[15:37] <sarnold> .has_branches=on&field.has_no_branches.used=&field.has_no_branches=on&field.has_blueprints.used=&field.has_blueprints=on&field.has_no_blueprints.used=&field.has_no_blueprints=on
[15:37] <sarnold> wow
[15:38] <doko> in groovy
[15:39] <cpaelzer> it was promoted in groovy, but why is the question I guess (and once solved fixing up subscriptions to the pkg)
[15:39] <ItzSwirlz> having no bugs in a package thats been around for
[15:39] <ItzSwirlz> ~10 releases is kinda sus ngl
[15:39] <doko> anyway, I'll demote and see what breaks ...
[15:39] <cpaelzer> that is an option as well
[15:40] <sarnold> wfm :)
[15:40] <cpaelzer> if anything breaks you might ask vorlon in whatever the next foundation meeting is
[15:40] <cpaelzer> as he seems to have promoted it he might have extar context
[15:40] <cpaelzer> next mismatches are u-boot-menu and opensbi
[15:40] <cpaelzer> raspi related ?
[15:40] <sarnold> ItzSwirlz: especially since bugreporters surprisingly often just pick packages at random..
[15:41] <cpaelzer> or risc
[15:41] <cpaelzer> opensbi rings a risc bell to me
[15:43] <cpaelzer> commit 6e2571375f95c01bc26f912b1de20909b8f2e547
[15:43] <cpaelzer> Author: Dimitri John Ledkov<EMAIL_ADDRESS>[15:43] <cpaelzer> Date:   Wed Nov 25 13:37:08 2020 +0000
[15:43] <cpaelzer>     supported-cloud: add RISC-V packages
[15:43] <sarnold> given how new the riscv platform is it feels very early to me to be bringing in a 'supervisory binary interface'
[15:43] <cpaelzer> xnox: will there be MIRs filed for these since you added them to the seeds?
[15:44] <cpaelzer> next is ruby-defaults -> rubygems
[15:44] <doko> sarnold: do we have a chance to go without it?
[15:44] <doko> rubygems was in precise in main ...
[15:45] <doko> isn't this some split-out?
[15:45] <cpaelzer> yeah and mostly removed rom everything else
[15:45] <cpaelzer> it was onyl coming back to hirsute - and in Debian also is only in unstable
[15:46] <cpaelzer> my ping to solve this would go to kanashiro but he's not aroudn this week
[15:46] <doko> however rubygems-integration was in main
[15:46] <cpaelzer> the question is "re-promote on the base of the old MIR" https://bugs.launchpad.net/ubuntu/+source/gem2deb/+bug/894827 or do we need something else?
[15:47] <cpaelzer> It also has ~25 test issues in excuses
[15:47] <cpaelzer> so it won't move to -release even if promoted
[15:47] <sarnold> ouch
[15:47] <doko> well, lets wait
[15:47] <cpaelzer> agreed
[15:48] <cpaelzer> xnox: you can answer later about opensbi and u-boot-menu when you see the ping
[15:48] <cpaelzer> that concludes todays component mismatch oddities
[15:48] <cpaelzer> #topic Any other business?
[15:49] <didrocks999> nothing for me
[15:49] <doko> sarnold: discount status?
[15:49] <sarnold> doko: no movement, sorry
[15:49] <doko> sarnold: if the security-team would join +1 maitenance, you would see the pain and extra work that this causes :-(
[15:51] <cpaelzer> in general security reviews seem rather stuck recently, I gues overload is happening
[15:51] <cpaelzer> or reviews just happen on a lot of things not related to ine ...
[15:51] <cpaelzer> mine
[15:51] <cpaelzer> sarnold: can you carry the pain-FYI to the Team so everone is aware?
[15:52] <sarnold> not, you're very right; due to losing several staff members we're heavily oversubscribed, 'tis the season to use unused PTO, and of course there's been glorious training modules to complete
[15:52] <sarnold> cpaelzer: yes
[15:53] <cpaelzer> thanks
[15:53] <cpaelzer> let us clsoe the meeting for today then
[15:53] <cpaelzer> #endmeeting
[15:53] <meetingology> Meeting ended Tue Dec  1 15:53:39 2020 UTC.
[15:53] <meetingology> Minutes:        http://ubottu.com/meetingology/logs/ubuntu-meeting/2020/ubuntu-meeting.2020-12-01-15.31.moin.txt
[15:53] <cpaelzer> doko: where do you want to continue the discussion on postgresql-12 next steps?
[15:53] <sarnold> thanks cpaelzer, all
[15:53] <didrocks999> thanks!
[15:53] <doko> can do here
[15:53] <cpaelzer> ok
[15:54] <cpaelzer> so PG-12 is in excuses with a bunch of tests failing, we didn#t care for it as it is intended to be removed
[15:54] <cpaelzer> but I wanted to remove PG-12 when PG-13 moved into hirsute and is promoted
[15:54] <cpaelzer> that depends on perl atm
[15:54] <cpaelzer> what is the order of promotion/removal/other that you'd recommend
[15:54] <doko> -13 is not yet migrated
[15:55] <cpaelzer> yeah PG-13 depends on perl
[15:55] <cpaelzer> IÄve ensured it is otherwise ready
[15:55] <cpaelzer> so is the related postgresql-common v223
[15:55] <doko> omnidb ftbfs
[15:56] <cpaelzer> hmm, I can look for that
[15:56] <doko> pgpointcloud/armhf ftbfs
[15:56] <cpaelzer> should not be related
[15:56] <cpaelzer> does that need to be resolved for PG-13
[15:57] <cpaelzer> anyway I can take a look as well- b'cause why not
[15:57] <doko> and: Implicit dependency: perl postgresql-12 (not considered)
[15:57] <doko> for perl.
[15:57] <cpaelzer> hrm
[15:57] <doko> so perl won't migrate without -12
[15:57] <cpaelzer> so you are saying I need to get PG-12 working for PG-13 to migrate because perl links the two
[15:57] <cpaelzer> arrr
[15:58] <doko> yes
[15:58] <doko> sorry
[15:58] <cpaelzer> I love fixing proposed if I'm not doing it 24/7 - so yeah I'll look into all of those
[15:58] <cpaelzer> but maybe (only maybe) re'll remove PG-12 instead even before 13 migrates
[15:58] <cpaelzer> depends how easy/hard those fails are PG-12 has
[15:59] <doko> but then you need -13 in the release pocket ...
[15:59]  * cpaelzer sigh
[15:59] <cpaelzer> ok on it
[15:59] <cpaelzer> Then let me replace that with ... maybe test hints
[16:00] <cpaelzer> just so I have the feeling of a chance to get it resolved :-)
[16:00] <cpaelzer> Notes on PG related tasks taken and will look into them ...
[16:01] <cpaelzer> thanks doko for sorting out next steps for these!
[16:01] <doko> cpaelzer: yes, proposed a hint with the note that it will be removed anyway
[16:41] <luna_> Any kernel meeting today or still not?
[16:42] <luna_> also are you rebuilding the 5.9.11 kernels ?


[06:22] <mborzecki> morning
[06:57] <mup> PR snapd#11845 closed: tests/main/nfs-support: be robust against umount failures <Simple 😃> <Test Robustness> <Created by mardy> <Merged by mardy> <https://github.com/snapcore/snapd/pull/11845>
[08:17] <mup> PR snapd#11834 closed: o/snapstate: exclude services from refresh app awareness hard running check <Bug> <refresh app awareness> <Created by stolowski> <Merged by stolowski> <https://github.com/snapcore/snapd/pull/11834>
[09:18] <mup> PR snapd#11847 opened: tests/main/interfaces-browser-support: verify jupyter notebooks access <Simple 😃> <Created by bboozzoo> <https://github.com/snapcore/snapd/pull/11847>
[11:23] <mup> PR snapd#11178 closed: tests: increase the memory on test minimal-smoke with secboot disabled <Simple 😃> <Run nested> <Created by sergiocazzolato> <Merged by sergiocazzolato> <https://github.com/snapcore/snapd/pull/11178>
[11:28] <mup> PR snapd#11848 opened: tests: revert lxd change to support nested lxd launch <Created by sergiocazzolato> <https://github.com/snapcore/snapd/pull/11848>
[13:13] <mup> PR snapd#11824 closed: interfaces/browser-support: allow editing of Jupyter notebooks in browsers <Created by nteodosio> <Merged by sergiocazzolato> <https://github.com/snapcore/snapd/pull/11824>
[13:13] <mup> PR snapd#11847 closed: tests/main/interfaces-browser-support: verify jupyter notebooks access <Simple 😃> <Created by bboozzoo> <Merged by sergiocazzolato> <https://github.com/snapcore/snapd/pull/11847>
[14:33] <mup> PR snapcraft#3777 closed: parts: fix metadata extraction dirs <Created by cmatsuoka> <Merged by sergiusens> <https://github.com/snapcore/snapcraft/pull/3777>
[17:33] <tacomaster> I have a question about snaps. I have found online that snaps are immutable but is there any protection to the rest of the machine? The reason I ask is I am trying to run a server service on ubuntu server and trying to see if it would be better to use, a container or a snap for security reasons?
[17:34] <tacomaster> or would it be best to write an apparmor profile for that service?
[20:40] <mardy> tacomaster: hi! When you launch a snap, a container is created: not only AppArmor confines the process, but also we use seccomp, cgroups, and mount namespaces to isolate the snap from the rest of the machine
[20:41] <mardy> tacomaster: the more interface you connect in the snap, the more "holes" we drill in the container
[20:41] <mardy> *interfaces
[21:13] <ogra> tacomaster, adding to what mardy said, every single snap undergoes an autmatic review during upload. there are interfaces that are harmless (like "audio-playback") when your snap connects them, and there are more privileged ones (i.e. "network-setup-control") ... snaps that use the higher privileged ones need to pass a manual review by the security team ... if you look at the "store-requests" category at forum.snapcraft.io you cn find them all ...


[21:47] <Takyoji> Just added to the EFF website today: https://secure.eff.org/site/Advocacy?cmd=display&page=UserAction&id=451
[23:56]  * Obsidian1723 shutdown -h night all


[00:05] <cjwatson> stgraber: I did an updated precise build for you, in case you're still around
[00:15] <stgraber> cjwatson: ah cool, I'll give it a try
[00:15] <stgraber> now that I'm done banging my head against the wall trying to figure out how nih-dbus-tool does its magic :)
[00:27] <slangasek> stgraber: do you have a bug # handy for the "can't boot unsigned kernels" bug on your system?  I'd like to start digging into that with you too before .2
[00:28] <stgraber> hmm, I can't remember whether I filed a bit for that one or not, let me look at my recently filed bug list :)
[00:29] <stgraber> can't find one... I'll file a new one against shim so we can track that issue
[00:32] <stgraber> slangasek: bug 1087501
[00:32] <ubot2> Launchpad bug 1087501 in shim (Ubuntu) "Unable to boot unsigned kernel, boot freezes in shim call" [Undecided,New] https://launchpad.net/bugs/1087501
[00:32] <slangasek> ok
[00:33] <stgraber> slangasek: once I'm done testing the new precise image for Colin, I'll do another run of grub with debug=all and attach a picture to the bug. I doubt it's going to really help though as all that we'll see is that it's calling a function that the shim exports.
[00:33] <slangasek> yep
[00:34] <slangasek> so as a first step, I'd like to do a build of the new upstream version of shim, where mjg59 has entirely dropped the fallback code for calling the UEFI protocol
[00:34] <slangasek> (the same UEFI protocol that was popping up dialogs on signature failure)
[00:36] <stgraber> I've been playing with EFI a bit lately and I think I have a working .efi binary that when called will load my local PKI's certificate into the firmware, allowing me to sign my own binaries. That should help quite a bit.
[00:36] <stgraber> I know that in theory I can also just write new entries from Ubuntu while in setup mode but I haven't found a good tool for that yet (that just takes a standard SSL cert and loads it)
[00:38] <cjwatson> stgraber: debug=all> we already tried that at UDS and showed it just calling said function, indeed - I don't think it was useful for debugging this
[00:40] <slangasek> stgraber: yes, for debugging you definitely want to be using self-signed binaries :)
[00:40] <slangasek> (at least self-signed shim)
[00:41] <stgraber> slangasek: btw, is there any reason why /sys/firmware/efi/efivars is world readable but /sys/firmware/efi/vars is only root readable?
[00:42] <stgraber> found it a bit weird considering they export the exact same information just with different paths :)
[00:42] <slangasek> stgraber: ummm because the former is a mountpoint and I didn't think to change the defaults? :)
[00:43] <slangasek> it shouldn't be a security issue in practice, but maybe we do want to lock it down to be root-only by default
[00:43] <slangasek> can you file a bug report on mountall for this?
[00:44] <stgraber> will do once I'm back to my standard desktop (currently in the middle of the precise install)
[02:58] <stgraber> cjwatson: well, the good news is that grub is booting
[02:58] <stgraber> cjwatson: the bad news is that it has no menu and can't seem to find anything
[02:58] <stgraber> so I'm stuck in grub minimal
[03:10] <stgraber> and back to a working laptop, now let's see what was broken this time around :)
[03:12] <stgraber> cjwatson: so at first glance, my bet would be on the missing grub directory under /boot/efi/
[03:12] <stgraber> cjwatson: at the end of this install the EFI partition only contains two directories, EFI and LOST.DIR, no grub
[03:13] <stgraber> cjwatson: installer log: http://paste.ubuntu.com/1416091/
[03:15] <stgraber> cjwatson: btw, to make things simpler this time around I unplugged my internal ssd before the installation
[03:17] <stgraber> cjwatson: that may explain why my previous test had the grub directory present as the EFI boot partition was shared with the one from my raring system and therefore already had a grub directory.
[03:28] <stgraber> slangasek: efivars bug 1087546
[03:28] <ubot2> Launchpad bug 1087546 in mountall (Ubuntu) "efivars filesystem gives more access than the exists vars directory" [Undecided,New] https://launchpad.net/bugs/1087546
[05:00] <slangasek> stgraber: /boot/efi> secureboot doesn't get a grub directory, you get a monolithic grub .efi because it's not allowed to load unsigned code?
[05:02] <stgraber> slangasek: ah, ok, so I must have it on my laptop because grub-install has been running a few times without secureboot. So it's something else that's broken in the secureboot grub that's on the precise image
[05:06] <stgraber> so trying to boot the same disk in a VM (so I can slow it done and see what's going on), I'm seeing a bunch of "error: efidisk read error.", then drop in a minimal grub shell and that's all I get
[05:06] <stgraber> *down
[05:11] <slangasek> strange
[05:12] <slangasek> "efidisk read error" isn't anything I'm familiar with, I guess it could be a grub-specific error message when it tries to use the efi disk protocols
[05:12] <stgraber> yeah, and that VM isn't running with secureboot enabled, so it's not the firmware blocking access or anything like that
[05:13] <stgraber> and just to be 100% sure, I checked that the md5sum of /boot/efi/EFI/ubuntu/grubx64.efi matches that of /usr/lib/grub/x86_64-efi-signed/grubx64.efi.signed, so it's not some kind of random vfat corruption that happened at install time
[05:15] <stgraber> anyway, enough uefi fun for the evening, will wait for cjwatson to show up
[05:22] <ScottK> Looking at the SRUs in -proposed, I see that walinuxagent is fixing a private bug (bug  	#1077147).  It seems to me that any bug being dealt with in the SRU process ought to be public (if needed, support people could make a sanitized version of the bug for public consumption.)
[05:22] <slangasek> yes, I agree; this has been communicated in the past, but it needs to be repeated from time to time
[05:26]  * ScottK wonders if removing the upload from proposed would be an adequate form of 'communication'?
[05:26] <cjohnston> lol
[05:26]  * ScottK is not kidding.
[05:26] <slangasek> preferably telling the uploader why at the same time?
[05:26] <ScottK> Yes.  That too.
[05:26] <slangasek> then yeah
[05:26] <slangasek> it clearly can't be accepted as-is
[05:29] <ScottK> Additionally, it doesn't appear it was accepted into quantal by a member of ubuntu-sru
[05:29] <slangasek> sigh
[05:30] <slangasek> hmm, no, infinity accepted it
[05:30] <slangasek> (per the comment on the private bug)
[05:30] <ScottK> For precise
[05:30] <slangasek> oh
[05:30] <ScottK> https://bugs.launchpad.net/ubuntu/+source/walinuxagent/+bug/1079897/comments/11 indicates Dave Walker for quantal
[05:30] <ubot2> Launchpad bug 1079897 in walinuxagent (Ubuntu Quantal) "[SRU] walinuxagent mangles server identity and access on upgrade" [Critical,Fix committed]
[05:31] <ScottK> Since infinity accepted it for one release, maybe he'll take responsiblity for getting the bug unprivate ....
[06:17] <slangasek> man, I really don't feel like I'm accomplishing anything with these precise new queue approvals without queuebot to cheer me on
[06:35] <ScottK> OK, so removed walinuxagent and pinged the bug/uploaders.
[06:36] <ScottK> (to complete the record here for backscroll readers)
[09:34] <infinity> ScottK: Gah.  I could have sworn walinuxwhatever used to reference a public bug.
[09:35] <infinity> Err, it does.
[09:36] <infinity> ScottK: Oh, that was just a "new upstream" bug from a previous changelog entry.  I'm not sure that was worth removing for. :/
[09:37] <infinity> ScottK: I don't agree that asking people to revise their changelog to sanitize out dupe bugs is sane at all.
[09:37] <infinity> ScottK: It clearly was a dupe of an identical public bug, from the changelog.
[09:37] <xnox> ScottK: walinuxagent is a valid bug. And references public bugs. Also that SRU causes dataloss and rendering sertain machines unreachable.
[09:38] <xnox> ScottK: infinity: can we please revert removal?
[09:38] <infinity> xnox: You can't "revert" removal.
[09:38] <infinity> xnox: It'll need a new upload with a bumped version.
[09:38] <infinity> Oh, actually.  That might not be true.
[09:38] <xnox> infinity: it is scheduled "in 3h time or something?!"
[09:38] <infinity> We can copy from proposed to proposed to make it magically reappear.
[09:38] <xnox> =)))))
[09:39]  * infinity tries that.
[09:39] <xnox> ScottK: infinity: while the SRU procedure was not followed, it is best to speak with individual in question publically on u-d, instead of blindly removing packages from -updates.
[09:39] <infinity> xnox: The procedure was followed.
[09:39] <xnox> righ.
[09:40] <xnox> So why is ScottK removed both of them?
[09:40] <infinity> (It's just that the changelog references one private (dupe) bug).
[09:40]  * xnox thinks about grammar.
[09:40] <infinity> And I'm not editing the changelog and reuploading, when it's obvious that's the case.
[09:40] <infinity> xnox: That said, the procedure absolutely was NOT followed for Quantal. :P
[09:40] <infinity> xnox: I'm only restoring the one I accepted into precise.
[09:41] <xnox> infinity: the bug causes dataloss & renders machines unreachable. I'd want to see both packages restored asap.
[09:42] <infinity> xnox: That's no excuse for non-SRU members accepting SRUs.
[09:43] <xnox> Daviey: jamespage: ^^^^^^^ walinuxagent - Daviey, you shouldn't accept SRUs. (you can via AA rights, but you shouldn't due to not being SRU team member). And now walinuxagent is being removed from the updates pocket.
[09:43] <xnox> win \o/
[09:44] <xnox> infinity: what do you want to happen for quantal SRU to be re-published?
[09:46] <infinity> xnox: I want to wait until I discuss this with ScottK and slangasek tomorrow to grasp why it was such a monumentally big deal to have a changelog reference a private bug (when it was clearly a dupe, I know exactly why it's bad when it's not).
[09:48] <Daviey> xnox: This is something that has only been clarified recently.
[09:49] <infinity> Daviey: Uhm.  If "recently" means "before you were an archive admin", I agree.
[09:50] <Daviey> No.
[09:50] <infinity> ScottK / slangasek: I absolutely agree that SRUs shouldn't ref private bugs, but I also think that people reviewing these things should have the ability to read changelogs instead of blindly clicking on a list in a UI.
[09:51] <Daviey> infinity: erm, that isn't quite what happened.. And i'd appreciate a less sarky attitude please.
[09:52] <infinity> Daviey: What isn't what happened?
[09:53] <Daviey> infinity: you are shooting off comments, without facts.  It is inappropriate.
[09:53] <infinity> Daviey: Which comment lacks facts?
[09:54] <Daviey> infinity: Firstly, i was informed from an ~ubuntu-sru member that it was agreed at UDS before last that AA's could handle SRU's. Secondly, i checked with another member that it wouldn't cause upset.. and thirdly, "blindly clicking on a list in a UI." is just flippant.
[09:55] <Daviey> That is not what i did.
[09:55] <infinity> Daviey: That last comment had nothing to do with you, it had to do with people clicking bugs and noticing they're private and knee-jerking, rather than reading the changelog to see the ref.
[09:55] <Daviey> Oh, ok.  Apologies.
[09:57] <infinity> Anyhow, the first part is a twisting of the part where we had a conversation suggesting AA/SRU/Release should perhaps be merged (and then opted not), second, whoever you checked with was, well, wrong?  Third, this is all documented. :/
[09:58] <Daviey> infinity: I wasn't in the session i don't think.. But when a ~ubuntu-sru member tells you something like that, it seems reasonable.
[10:00] <Riddell> how do I put a block on migrating from proposed (for KDE SC)?
[10:09] <infinity> (base)adconrad@cthulhu:~/britney/hints-ubuntu$ cat kitterman
[10:09] <infinity> # Keep KDE SC 4.9.90 from migrating before we are ready
[10:09] <infinity> block kde4libs
[10:09] <infinity> Riddell: ^-- Like that one?
[10:10] <infinity> Riddell: (ScottK appears to be on the case)
[10:20] <Riddell> lovely
[10:30] <infinity> ScottK: So there's public record of this in the channel, Daviey and I have talked privately, and I'll be giving him some formal training, but there won't be any more SRU accepting by him until after that happens.
[11:32] <cjwatson> stgraber: For your VM test, make sure you have enough RAM.  I wasted a couple of hours a few weeks ago because I was running kvm with its default of 128MB, but UEFI/OVMF/whatever is too memory-hungry for that to work
[11:36] <cjwatson> Daviey: If you mean with me, since the conversation was in person I don't have a word-for-word record; but I believe I said that I thought it was acceptable for AAs to step in occasionally outside their usual line of work if other avenues had been exhausted
[11:36] <cjwatson> I don't think it should be a routine thing
[11:38] <Daviey> cjwatson: Actually, that wasn't you.. you were the followup.  The outcome of our conversation IIRC was that it was 'OK', but should really look to get in officially.. Which is what i did.
[11:38] <cjwatson> stgraber: What's in /boot/efi/EFI/ ?
[11:39] <cjwatson> (a.k.a. /EFI/ on the EFI System Partition)
[13:02] <jdstrand> infinity: hey, fyi, you mentioned a CC in the team status reminder, but there was no CC. I'll forward it along to my guy
[13:03] <infinity> jdstrand: SRSLY?
[13:03] <infinity> Cc<EMAIL_ADDRESS><EMAIL_ADDRESS><EMAIL_ADDRESS>[13:03] <infinity><EMAIL_ADDRESS><EMAIL_ADDRESS><EMAIL_ADDRESS>[13:03] <infinity><EMAIL_ADDRESS><EMAIL_ADDRESS><EMAIL_ADDRESS><EMAIL_ADDRESS>[13:03] <infinity> jdstrand: It was CCed, the header just got stripped off the lists copy.
[13:03] <jdstrand> oh, interesting
[13:04] <jdstrand> I didn't know the list would do that
[13:04] <jdstrand> infinity: ok, sorry for the noise :)
[13:41] <psivaa> cjwatson: i have attached ubiquity debug logs as asked in bug 1080701
[13:41] <ubot2> Launchpad bug 1080701 in ubiquity (Ubuntu Raring) "After 'Preparing to install Ubuntu' screen, raring installation hangs" [High,Confirmed] https://launchpad.net/bugs/1080701
[13:44] <cjwatson> psivaa: Thanks
[13:45] <cjwatson> xnox: ^- Do you think you could have a look at that, please?  I think you've touched this code most recently
[13:46] <xnox> cjwatson: ok. I will look into it later today.
[13:47] <psivaa> xnox: cjwatson: thanks
[13:52] <cjwatson> xnox: Thanks
[14:28] <stgraber> cjwatson: a single ubuntu directory containing shimx64.efi and grubx64.efi
[14:28] <stgraber> cjwatson: the VM had 2GB of RAM, so shouldn't be the problem and I get the same on baremetal with 16GB
[16:46] <slangasek> infinity: in the changelog I looked at, it was note a dupe: Backport new upstream version (LP: #1078074) from current development release including fix for critical issue during upgrade (LP: #1079897).
[16:46] <ubot2> Launchpad bug 1078074 in walinuxagent (Ubuntu Quantal) "[SRU] Update walinuxagent to version 1.1" [High,Triaged] https://launchpad.net/bugs/1078074
[16:46] <ubot2> Launchpad bug 1079897 in walinuxagent (Ubuntu Quantal) "[SRU] walinuxagent mangles server identity and access on upgrade" [Critical,Triaged] https://launchpad.net/bugs/1079897
[16:48] <slangasek> infinity: in this case I mentioned to ScottK I didn't mind if it was published with that particular bug reference present since the bug itself was nothing more than "New upstream release"
[16:48] <infinity> slangasek: That's not the private bug.
[16:48] <infinity> * New upstream version (LP: #1078074, #1077147).
[16:48] <ubot2> Launchpad bug 1078074 in walinuxagent (Ubuntu Quantal) "[SRU] Update walinuxagent to version 1.1" [High,Triaged] https://launchpad.net/bugs/1078074
[16:48] <infinity> ^-- The second one there is the private.
[16:49] <slangasek> infinity: ah, then apparently I got my wires completely crossed while looking at changelogs
[16:49] <infinity> https://launchpad.net/ubuntu/+source/walinuxagent/1.1-0ubuntu2~12.04.1
[16:49] <infinity> Had the top-referenced bug been private, I would have had the same grump.
[16:49] <slangasek> infinity: so I don't object to this SRU being resuscitated as-is
[16:50] <infinity> Check.
[16:50] <infinity> I'll review the Q one and copy it back in (I already did so for precise)
[16:50] <infinity> And I'm going to give Daviey some training $soon.
[17:58] <cjwatson> stgraber: I think the answer is going to be that I have to pair-debug this with you at a time when it's mutually convenient
[17:58] <cjwatson> stgraber: But today my head is full of cold and I don't think I'm in a useful state to do much about it
[17:59] <cjwatson> stgraber: So maybe Monday?  What kind of time do you start then?
[17:59] <cjwatson> the efidisk read error might be a consequence of a wrong bootstrap config file in the embedded memdisk
[17:59] <cjwatson> at any rate that's my best guess at the moment - but I'd have to stare at it
[18:11] <stgraber> cjwatson: Monday morning is pretty bad for me because of a bunch of meetings. I start at 14:00 UTC but have meetings between 15:00 and 16:00 and between 17:00 and 17:30
[18:17] <cjwatson> stgraber: ok, I think I'm actually free 16 to 17 - but maybe Tuesday then?
[18:19] <stgraber> cjwatson: I have nothing on Tuesday so that'd work a lot better :)
[19:06] <infinity> cjwatson: Oh, pursuant to an old conversation, here's a prime example of my subconscious need to (almost) fully-justify things without really thinking about it:
[19:06] <infinity> https://launchpadlibrarian.net/125129559/qemu_1.2.0.dfsg-4_source.changes
[19:06] <infinity> cjwatson: Extra sad, since that was just a test package I did for hallyn.
[19:26] <utlemming> infinity: on walinuxagent, I've cleared the private bug -- its now public
[19:27] <utlemming> infinity: all confidential information has been hidden.
[19:28] <infinity> utlemming: We decided that wasn't necessary in the end, but thanks anyway. :)
[19:29] <infinity> utlemming: I've recopied both SRUs to proposed (binaries and all, so if you'd previously done verification on them, that verification is still valid)
[19:29] <utlemming> inifinity: okay great...do we know when it will land?
[19:29] <infinity> Was all the verification done and ready to go?
[19:29] <infinity> If so, I can quickly run through the paperwork and do some releasy magic.
[19:30] <utlemming> infinity: yup. That was private tracking bug that we used for talking to MS. It really shouldn't have been referenced. But, yes, verification is done
[20:07] <slangasek> infinity: hmmm my copy of your mail to u-release includes 0 CC:s
[20:10] <infinity> slangasek: mailman strips the CC header.
[20:10] <infinity> slangasek: I assure you that people got the mail.
[20:10] <slangasek> wat
[20:11] <infinity> slangasek: (Or, so I've been told by $people)
[20:11] <slangasek> mailman has never, ever stripped cc:s for me before
[20:11] <slangasek> but ok, as long as you're sure people got the memo
[20:11] <infinity> slangasek: It did this time.  Perhaps because it tripped the "too many recpients" thing?  (which it did, I had to moderate it)
[20:11] <slangasek> right, that could be a special case
[20:19] <slangasek> stgraber: on iso.qa, I see that desktop and preinstalled are both "active" products for armhf+omap*.  Is this because the list is used for both the current release and the LTS point releases?
[20:19] <stgraber> slangasek: yep
[20:19] <slangasek> ok
[20:20] <stgraber> hmm, not that we do point release for armhf, do we?
[20:20] <stgraber> if we don't we can probably just disable preinstalled
[20:20] <slangasek> it doesn't appear that we did 12.04.1 for armhf
[20:21] <slangasek> except for ubuntu core
[20:22] <infinity> Yeah, we don't do point releases on those images.
[20:22] <ogra_> slangasek, hmm, i thought respinning armhf was undesired
[20:22] <infinity> ogra_: It is.  This is just the tracker that needs to learn that, the rest of us know. :)
[20:22] <ogra_> oh. ok
[20:28] <cjwatson> stgraber: though it occurs to me that I could build myself a grub image that thinks it's SB and refuses to load modules, even though it really isn't
[20:28] <cjwatson> I might have a go at that on Monday.  Not sure why I haven't tried that before
[20:30] <stgraber> cjwatson: oh, I may have forgotten to mention that SB or non-SB gives me the same thing, so if you have an EFI system, booting the signed binary should trigger the bug
[20:30] <slangasek> stgraber: so IIRC, the theory was that we would ditch the wiki manifest in favor of something that lives in the iso tracker; I cannot currently find any page in the ISO tracker that accurately shows me what we're expecting to release for raring.  Halp?
[20:34] <stgraber> slangasek: right, so we have a way of storing the manifest on the tracker, by going to a manifest page under the series tab in the admin. However the implementation has discussed at UDS had a flaw ;) we said we wouldn't need that list to be overridable per-milestone but we clearly do.
[20:34] <cjwatson> stgraber: no, I test-installed in OVMF before I gave it to you, so it's not that simple
[20:35] <med_> infinity, as I understand scrollback, walinuxagent is about to go "live" in precise-updates and quantal-updates?  Is there a timetable for that (ie, within 24 hours?)
[20:35] <cjwatson> it might be the memory allocation bug that Dell want me to fix, I guess ...
[20:35] <slangasek> stgraber: ehm, so, I was expecting this to be the manifest for the release
[20:35] <stgraber> cjwatson: I can send you a compressed disk image of my drive if you want? "sudo qemu-system-x86_64 -L . -hda /dev/sdc -m 2048" clearly gives me the same bug here as on metal
[20:35] <infinity> med_: Less, probably, I just need to stop multitasking and poke it.
[20:36] <cjwatson> stgraber: couldn't hurt ...
[20:36] <slangasek> stgraber: is the problem here that it's being used by nusakan to control the actual milestone publishing, and therefore needs to keep track of the differences?
[20:36] <med_> infinity, nod, thanks.
[20:37] <stgraber> slangasek: so the way it works currently is that you can set a milestone to be based on the manifest, in that case, whenever a daily that's pushed by nusakan is present in the manifest, it'll be automatically added to the milestone.
[20:37] <stgraber> slangasek: so if we had listed everything in the manifest for alpha-1, then all the products would have showed up in the alpha-1 milestone on the tracker
[20:38] <stgraber> slangasek: my current thought of a quick fix for this limitation is to add a disabled flag to those manifest entries, so that we can choose which are currently active and should be used when posting images
[20:38] <stgraber> that way we can add all the products and their contacts for the release and before a milestone, disable them all and only enable those that are participating
[22:12] <slangasek> stgraber: what about not automatically posting the images to the milestone?
[22:12] <slangasek> wouldn't require code changes, could be implemented immediately
[22:14] <stgraber> slangasek: well, I surely intend to lend the active/inactive flag way before the next milestone
[22:14] <stgraber> slangasek: so there's no problem populating the manifest already
[22:14] <stgraber> *land
[22:15] <infinity> *sigh*... Has anyone yelled at seb128 about breaking ubuntu-desktop?
[22:17] <slangasek> infinity: er?
[22:17] <infinity> http://people.canonical.com/~ubuntu-archive/testing/raring_probs.html
[22:18] <infinity> slangasek: Due to the im-switch -> im-config change without an MIR (or two).
[22:18] <slangasek> stgraber: ok, so... do we have the data somewhere, that can be used to repopulate this?
[22:18] <slangasek> infinity: britney allowed this?
[22:19] <stgraber> slangasek: nope because I don't think we actually asked th product leads what they're planning on releasing for raring. We can base it on quantal though and then ask everyone to check that it's correct
[22:19] <infinity> slangasek: Britney doesn't deal in components currently.
[22:19] <slangasek> stgraber: I think that's a good place to start then.  Can you do that easily?
[22:19] <stgraber> slangasek: yep
[22:21] <slangasek> stgraber: ok, then please do :)
[22:22] <slangasek> infinity: so, are you reverting language-selector?
[22:22] <infinity> slangasek: I suppose that's the way forward for the weekend.
[22:22] <infinity> slangasek: And the seeds, and ubuntu-meta.
[22:22] <infinity> Oh, maybe not meta.
[22:23] <infinity> Nope, meta hasn't been refreshed yet.
[22:23] <slangasek> yes, and we have a wiki page somewhere for tracking reverts, right?
[22:23] <infinity> But I'll revert the seed change.
[22:25] <infinity> We do.  Somewhere.
[22:25] <slangasek> https://wiki.ubuntu.com/UbuntuDevelopment/RevertLog, editing
[22:29] <slangasek> infinity: were there any bug reports for this?
[22:30] <infinity> slangasek: It just landed in the archive a few hours ago and Andy whined that upgrade was taking out ubuntu-desktop.
[22:30] <infinity> Let me go see if there's a bug report.
[22:30] <slangasek> infinity: well, if you're doing the reverting upload, please do that first :)
[22:30] <slangasek> we can find and fix bug reports after
[22:30] <infinity> Already done.
[22:31] <slangasek> ah, thanks
[22:31] <infinity> Might even build before the publisher.
[22:32] <infinity> Nothing new on language-selector, but heaven knows what other random packages it could have been filed on.
[22:33] <infinity> And my build beat the publisher.
[22:33] <infinity> Yay.
[22:35] <slangasek> no obvious bug reports that I can see
[22:35] <stgraber> slangasek: http://iso.qa.ubuntu.com/qatracker/series/32/manifest
[22:36] <infinity> Why do I keep ending up ad server amd64+mac?
[22:36] <infinity> I swear I fixed that in the wiki before.
[22:36] <stgraber> based on quantal's manifest and dropped armel products. I don't think I missed anything but that's a long list
[22:37] <stgraber> infinity: well, you didn't fix https://wiki.ubuntu.com/QuantalQuetzal/ReleaseManifest apparently ;)
[22:37] <infinity> (And I'm positive it's cause someone saw "mac" and saw I was on the hook for PPC, and extrapolated)
[22:37] <slangasek> heh
[22:37] <stgraber> I'm not even sure why we build a +mac server image to start with :)
[22:37] <infinity> We probably shouldn't.
[22:38] <infinity> Well, ideally, we shouldn't have to build any +mac images.
[22:38] <stgraber> yeah, would be nice to finally get the full hybrid images working and getting rid of +mac
[22:38] <stgraber> not sure how far cjwatson got on that though
[22:39] <infinity> Did he ever manage to kidnap a Mac from the kernel team?
[22:39] <slangasek> infinity: thanks for volunteering to hack the ISOs in your spare time!  Hardware is on its way
[22:39] <slangasek> ;)
[22:39] <infinity> AFAIK, he was blocking on having real hardware to debug with.
[22:39] <slangasek> no, actually the hardware is kidnapped in my direction
[22:39] <infinity> Ahh.
[22:39] <infinity> Plz fix.
[22:46]  * infinity emails the responsible parties.
[22:51] <infinity> Weird.  mailman is definitely munging CCs.
[22:51] <infinity> In my =Sent folder, I have "Cc<EMAIL_ADDRESS><EMAIL_ADDRESS>[22:51] <infinity> The mail from the list only has Gunnar.
[22:54] <slangasek> infinity: oh; correction, the macs are not kidnapped in my direction, they are sitting on my doorstep
[22:54]  * slangasek fixes this
[23:08] <xnox> slangasek: so you are joining the apple crowd =) I am sure ev & barry would give you a hug. (and doko & myself to some extend)
[23:08] <slangasek> xnox: I'm only here to kill off an ISO
[23:08] <slangasek> after that the hardware goes away again ;)
[23:10]  * ScottK cheers killing off an ISO.
[23:10]  * xnox can image slangasek using a separate tagged vlan for macs in a quarantine room, just in case they pollute the rest of machines.
[23:11] <stgraber> you don't need network access to test iso images
[23:11] <infinity> Nor a room.
[23:11] <slangasek> hahaha
[23:11] <infinity> In fact, I recommend testing ISOs on Macs in the middle of corn fields.
[23:11] <ScottK> Not unless there will be excessive public displays of affection otherwise (re the room)
[23:14] <infinity> ev: Say, how many iProducts do I need to send you to make the wubi-e2fsprogs-doesn't-support-ext4 thing go away?
[23:14] <infinity> xnox: Or, since you seem to have some perverse obsession with cross-building Win32 stuff, maybe I should be asking you. :P
[23:16] <xnox> infinity: yes, you should be asking me. Let's see if I can double this up together with fix 5-cross-compiles.
[23:18] <slangasek> you cannot
[23:18] <slangasek> :P
[23:18] <infinity> Wow, e2fsprogs still uses dh_movefiles.
[23:18] <slangasek> that's a work item for cross-compiling to /real/ platforms :)
[23:18] <infinity> slangasek: He may well be able to, e2fsprogs is broken in http://people.canonical.com/~cjwatson/cross/armhf/raring/
[23:18] <slangasek> hah
[23:18] <slangasek> ok fine
[23:19] <infinity> slangasek: If he fixes it for the armhf cross case, it might Just Work for a mingw32 target.
[23:19] <infinity> (might)
[23:19] <slangasek> the converse seems more likely
[23:19] <infinity> True.
[23:21] <xnox> hah =)
[23:22] <barry> you'll pry my mbp out of my hands when i get a 1440x900 ultrabook :)
[23:22] <infinity> barry: Will 1600x900 do?
[23:22] <slangasek> infinity: ok, this cc: issue is clearly something on your end, you said "hi guys" but have only one Cc :)
[23:23] <infinity> barry: The Carbon is definitely ultrabooky.  And pretty sexy.
[23:23] <barry> infinity: it just might
[23:23] <infinity> slangasek: I mentioned this half an hour ago.
[23:23] <barry> infinity: i basically want a macbook air that's not a mac :)
[23:23] <infinity> barry: The ThinkPad X1 Carbon is pretty much exactly that.
[23:24] <infinity> barry: With the bonus of being a less crap keyboard, and a sexier cover.
[23:24] <slangasek> infinity: ah yes, missed that
[23:24] <infinity> Also, a nipple.
[23:24] <xnox> there is also a new asus ultrabook which I didn't compare to thinkpad yet.
[23:24] <barry> infinity: i'll have to try to play with on.  my last thinkpad's keyboard killed my hands :/
[23:24] <slangasek> infinity: anyway, I have a hard time believing it's mailman
[23:25] <infinity> barry: Was that the classic ThinkPad keyboard they've shipped for the last decade, or the new chicklet ones?
[23:25] <xnox> barry: surprisingly X1's keyboard is similarish to the spread out mb keyboards.
[23:25] <barry> infinity: pre-chicklet
[23:25] <infinity> barry: Well, if you're using chicklet Macs, my personal opinion is that the Lenovo chiklets are much more pleasant.
[23:25] <infinity> barry: But YMMV.
[23:26] <barry> infinity: definitely something to investigate.  thanks.  (i'm up for refresh next month)
[23:26] <infinity> I'd probably buy a Carbon tomorrow if they shipped with more RAM.
[23:26] <infinity> 8G.  Bah.
[23:26] <barry> yeah.  air max is 8g but 512 ssd i think
[23:27] <infinity> That Carbon's SSD appears to top out at 256 on the web form.
[23:27] <infinity> Then again, I don't know why I need more local storage than that (I don't).
[23:28] <barry> multitrack audio!
[23:29]  * xnox is reminded of the "WE LOVE BARRRRRY" chants during NoNameYet band debut gig.
[23:29] <barry> oh gawd
[23:30] <barry> chanting the bass players name has killed universes
[23:30] <xnox> barry: was it recoreded?
[23:30] <barry> good question for pgraner
[23:32] <slangasek> xnox: the gig, or the death of universes?
[23:33] <barry> slangasek: you wouldn't be able to hear the latter.  it's at 1 x 10 ^ (-graham's number) hz
[23:35] <xnox> slangasek: former in flac, later in 3D video (I expect something no less exiting to hitchhickers guide to the galaxy style launching space ships into stars)


[01:16] <bnjmn> hi, does anyone know why there's no Ubuntu 11.04 Natty instance-store AMI in the us-east-1 region? I see it's available in other regions.
[01:25] <SpamapS> bnjmn: amd64 or i386 ?
[01:25] <SpamapS> $ ubuntu-cloudimg-query instance natty us-east-1 i386
[01:25] <SpamapS> ami-c15994a8
[01:26] <SpamapS> bnjmn: does look like amd64 is missing
[01:31] <bnjmn> sorry, yes I meant amd64
[01:32] <SpamapS> bnjmn: looks like they were updated yesterday..
[01:32] <SpamapS> bnjmn: http://cloud-images.ubuntu.com/natty/current/
[01:33] <SpamapS> bnjmn: ami-d87ba6b1
[01:33] <SpamapS> bnjmn: its possible the query tool is broken
[01:45] <bnjmn> yeah, in fact on cloud.ubuntu.com/ami/ it has ami-c0f7c5b4 as eu-west-1 natty amd64 instance-store but on that url, it's ami-b7cef7c3...


[05:24] <Kilos> o/
[11:05] <ebel> Hello. I am marked as one of the admins for the ubuntu-ie mailing list. And there's some spam. So there's a daily email with "X moderator requests waiting"
[11:05] <ebel> And I don't have the mailing list password, so I can't clear that queue
[11:05] <ebel> what can i do to get the mailing list password, or to clear that queue of moderator actions?
[11:47] <tsimonq2> ebel: go to #canonical-sysadmin and ask the vanguard for the password with proof that you own the team
[11:52] <ebel> OK, I've asked there. I'm not sure what "the vanguard" is. The only meaning I know is "advanced guard"...