[03:58] <len-dt> ailo, fun fun. Also, take a look at the conversation I had on #ubuntustudio. with newagepunk/DataJuggler. How has he installed that is different from what we tested?
[05:01] <len-dt> Is it just a strange keyboard language setup?
[05:10] <ailo> len-dt: I'm pretty sure he didn't choose the correct keyboard layout
[05:10] <ailo> Let me check about the audio group for amd64
[05:12] <ailo> len-dt: groups works for me
[05:14] <len-dt> Well he says he has the wrong KB for the language
[05:15] <ailo> When you choose keyboard layout, you also need to specify the exact layout. There are usually multiple for each language
[05:15] <ailo> For example, Swedish has about 5 or more
[05:16] <ailo> Most are for language minorities
[08:59] <smartboyhw> knome: I'm wondering: Why isn't there a "Get involved" section in ubuntustudio.org?
[09:01] <knome> smartboyhw, i don't know. i'm not managing the content
[09:03] <smartboyhw> knome: Then who is? I thought you manage the website...:)
[09:03] <knome> i only helped create the website style
[09:03] <smartboyhw> Oh, sorry, knome...
[09:04] <knome> https://launchpad.net/~ubuntustudio-website
[09:05] <smartboyhw> OK, that's weird, I will ask someone later then. Thanks knome
[09:06] <knome> no problem
[09:17] <smartboyhw> BTW, why isn't there a "Upgrade Ubuntu Studio" in the ISO QA Tracker? astraljava please fix it.
[10:01] <astraljava> smartboyhw: It wasn't supported before due to the DE change. For 12.10, we could enable it again, but we won't for precise.
[10:02] <smartboyhw> astraljava: Thanks, but what do you mean by DE change?
[10:02] <astraljava> Desktop environment, previously we had GNOME 2, now it's XFCE.
[10:03] <smartboyhw> Oh, so now since it's more stable, I think we can add it to 12.10
[10:04] <astraljava> Well, it's possible. The question is do we support it.
[10:04] <smartboyhw> astraljava: Why not?
[10:09] <astraljava> I'm not 100% up-to-date on all changes in the project-related packages, we'd have to start testing it and make sure all transitions are in place. Granted, gut-feel suggests there aren't that huge changes this cycle, but I'm not overly confident before I get enough results. If you have time, please run it a few times, with a mixed application set.
[10:09] <smartboyhw> OK
[10:19] <smartboyhw> astraljava: Can you help the problem in #ubuntustudio for a bit for Jonny1?
[11:17] <smartboyhw> astraljava: Ignore the previous message, no need now.
[11:52] <smartboyhw> scott-work: Why isn't there a "Get involved" section in ubuntustudio.org? I asked knome, he said it's other's job to manage the content
[11:52] <scott-work> smartboyhw: there are probably several reasons for this, which i will share
[11:52] <scott-work> smartboyhw: but what information would you put there?
[11:53] <smartboyhw> No, just wondering there should be one... Maybe info on dev and testing and documentation?
[11:54] <scott-work> we have talked about putting something there but sometimes it becomes difficult to actually accomplish something when you can't agree or define exactly what must be done
[11:55] <scott-work> maybe we should start by defining the problem:
[11:55] <scott-work> "users do not have an easy or informative way to learn about contributing to ubuntu studio"
[11:55] <scott-work> perhaps?
[11:56] <scott-work> could we add to the statement or change it to be more accurate? take something away?
[11:57] <scott-work> smartboyhw: oh, just to help you understand his position - kn.ome is the lead for the xubuntu team, which ubuntu studio shares many of the programs, and has graciously helped ubuntu studio with the web development, he's not really responsible for it though
[11:58] <smartboyhw> Wow.....
[11:58] <smartboyhw> I agree with the problem definition
[11:59] <scott-work> it is harder than it looks :P
[11:59] <scott-work> i agree with you that something probably needs to be done
[12:00] <scott-work> i think it is obvious we need something there to help people transition to contributing to ubuntu studio, but defining _what_ is was became very difficult
[12:00] <scott-work> however, smartboyhw, if you want to think about it and through out some ideas...well, that would be very, very helpful
[12:01] <smartboyhw> So where can I spit out those ideas on?
[12:01] <smartboyhw> ;)
[12:04] <scott-work> the mailing list is a good place that is transparent and easily accessed
[12:04] <smartboyhw> OK, I will write a email to it.
[12:04] <scott-work> smartboyhw: how are you doing on the documentation for ailo?
[12:07] <smartboyhw> scott-work: Still need some time, I'm a bit busy these days
[12:07] <smartboyhw> ;)
[12:09] <scott-work> smartboyhw: can i ask that you finish the documentation _befure_ you start other tasks?
[12:09] <smartboyhw> OK
[12:09] <smartboyhw> Just wondering!
[12:09] <scott-work> this isn't to pick on you, this is a common issue with all of us :P
[12:10] <scott-work> _everything_ is far too interesting to complete anything before moving on to the shiny, new, exciting next item ;)
[12:10] <scott-work> happens to me as well
[12:11] <smartboyhw> !
[12:14] <smartboyhw> scott-work: kidding, but will there be any changes to the 12.04.1 image now?
[12:15] <smartboyhw> BTW, since I'm busy these days, I will install 12.04.1, then continue to work on the documentation.
[12:33] <scott-work> smartboyhw: i am not aware of any changes for 12.04.1
[12:34] <smartboyhw> Thanks scott-work
[12:34] <scott-work> it would have been nice to have an updated lowlatency kernel for 12.04.1 though
[12:35] <scott-work> *sigh* but i guess that is partly my fault for not talking to apw instead of waiting on him
[12:35] <smartboyhw> scott-work: ...
[12:35] <scott-work> which reminds me...thanks astraljava for sending out an email for the ISO testing
[12:35] <scott-work> smartboyhw: yes?
[12:36] <smartboyhw> scott-work: ... means *sigh* for me:)
[13:13] <smartboyhw> astraljava: Status report on upgrading: Upgrading from 12.04 to 12.10, will tell you the results later
[13:26] <len-dt> ailo, scott-work I am just looking at the docs for module-jackdbus-detect. They are very sparce :) but it is possible to have the bridge default to no auto connect.
[13:27] <smartboyhw> len-dt: You happy with 12.04.1?
[13:27] <len-dt> I am going to test this
[13:27] <smartboyhw> Well, you tested it already, didn't you?
[13:27] <len-dt> smartboyhw, I am as happy as i can get. It would have been nice to use 12.10 as LTS
[13:28] <len-dt> the testing is about pulse.
[13:28] <smartboyhw> len-dt: I agree about 12.10 being LTS
[13:29] <len-dt> However, the next LTS... if there are no big changes in DE, should be really nice
[13:30] <smartboyhw> len-dt: Memory problem: I forgot what is DE
[13:30] <len-dt> Desktop Environmet
[13:30] <len-dt> In this case xfce
[13:30] <smartboyhw> Ah, yeah, let's see will there be an update on Xfce
[13:31] <len-dt> 12.04 has xfce4.8 and 12.10 has xfce4.10
[13:31] <astraljava> For the next LTS, we _might_ get full GTK3 port. :D
[13:32] <len-dt> There are a number of fixes I like in 4.10. The theme still needs a few tweaks
[13:32] <smartboyhw> astraljava: You're back! Also, next LTS: +`
[13:32] <smartboyhw> *+1
[13:32] <len-dt> astraljava, I figured out how to add things to the xfce settings manager BTW
[13:33] <astraljava> len-dt: Oh cool! Do tell, I'll read the backlog later, must leave the office now.
[13:33] <smartboyhw> len-dt: Congrats
[13:34] <len-dt> astraljava, very simple just set the categories right
[13:34] <astraljava> scott-work: Next time you see an email stuck in the queue due to that too many recipients message, leave it there, I'll look into it more carefully.
[13:34] <len-dt> astraljava, in the desktop file
[13:34] <smartboyhw> :)
[13:34] <astraljava> scott-work: Any news from apw re: -lowlatency refresh on precise? We're running out of time soon.
[13:43] <scott-work> astraljava: sent apw pm about it
[14:12] <len-dt> ailo, I would suggest adding to your controls starting pulse with no pa-jack bridge auto connect.
[14:35] <smartboyhw> astraljava: Upgrade from 12.04 to 12.10 succeeded for me:)
[14:38] <ailo> len-dt: I've been thinking about that. Also, looking at a simple jack control.
[14:38] <ailo> For connections, I'd use patchage
[14:39] <ailo> len-dt: I might not get that much done before 12.10 though
[14:40] <len-dt> ailo, to have pa-jack not auto connect the file /etc/pulse/default.pa has a line: load-module module-jackdbus-detect
[14:41] <len-dt> change that to: load-module module-jackdbus-detect connect=no
[14:42] <ailo> len-dt: Ok. I'll save that somewhere :)
[14:42] <smartboyhw> ;)
[14:46] <ailo> Saved in resources for -controls. I'm actually planning on making it as Debian friendly as possible. Was thinking about a name for it: pro-audio-controls
[14:46] <smartboyhw> ailo: I like that name:)
[14:46] <ailo> While the version for Ubuntu Studio would still be called ubuntustudio-controls
[14:47] <ailo> smartboyhw: Did you already post at the mentors list?
[14:47] <smartboyhw> ailo: What do you mean?
[14:47] <ailo> smartboyhw: About the package you wanted to upload
[14:47] <smartboyhw> ailo: I need to recommit, will take some time
[16:00] <smartboyhw> Well, bye for now!
[16:14] <ailo> I'm participating in a little IT course, involving php among other things for a couple of weeks. Old PC's. Was allowed to install ubuntu on one.
[16:15] <ailo> UI performance was terrible, so I installed awesome
[16:15] <ailo> And it was awesome
[16:16] <ailo> I takes something like 30MB of RAM
[16:46] <ailo> No, sorry. 6MB
[22:28] <len-dt> ailo, the user having trouble with audio group at install printed a dvd from the iso and it was ok.
[22:30] <len-dt> The use that failed to put the user in the audio group was writing the ISO to a USB stick in windows. using Universal-USB-Installer-<IP_ADDRESS>. This is the program suggested by the ubuntu how to page.


[15:45] <mpiano> ebarretto: Hi, sorry to bother again. I was doing the final checks to start using OVALs instead of cvescan databases, but I noticed that recent cves, for example https://ubuntu.com/security/CVE-2021-4034, are missing from https://security-metadata.canonical.com/oval/com.ubuntu.xenial.cve.oval.xml.bz2 .
[15:45] <mpiano> Am I missing something? Do the OVAL files only include a certain set of CVEs? Cause I would have imagined the data to be the same I can get from https://ubuntu.com/security/cves?q=&package=&priority=&version=xenial&status=released&offset=0
[15:45] <ebarretto> mpiano, let me check
[15:55] <ebarretto> mpiano, so xenial cve oval, differently from xenial usn oval, doesn't include yet ESM data. This is something that I've been working on lately.
[16:00] <mpiano> ebarretto, oh, that's a bit sad, pretty much full circle to not having up to date data feed for xenial 😅.
[16:00] <mpiano> Is there any ETA for having ESM data included in the CVE-indexed OVAL?
[16:04] <ebarretto> mpiano, we do have a deadline to get those changes merged but it is still ~2 months away. What I can do for you in the meantime is to get the json for xenial and trusty working in the meantime, while we work on getting the OVAL ready. I will probably ask as well for some feedback from you on the OVAL when it is ready
[16:11] <mpiano> ebarretto: Ok, thank you very much. I'm not very present on IRC, but feel free to reach out to<EMAIL_ADDRESS>for any feedback.
[17:36] <ebarretto> mpiano, xenial and trusty json should be there now
[17:38] <mpiano> ebarretto, they are indeed ❤  Thank you very much again for this, have a great weekend.
[17:38] <ebarretto> you too!
[17:43] <grimmware> ebarretto: you are the hero we don't deserve, thank you so much dude!
[17:44] <ebarretto> grimmware, glad to help :)
[17:44] <grimmware> ebarretto: I'm usually idling on IRC in one form or another and I work with mpiano on this stuff too, if there's anything we can do to help you lot out with testing this stuff out then hit us up
[17:46] <ebarretto> grimmware, thanks, I will appreciate if you could run some tests when time comes :)
[17:47] <grimmware> yeah man totally!


[04:38] <nvrpunk> Laney: evolution-ews breaks evolution entirely on a fresh install.  It just causes it to hang
[04:38] <nvrpunk> in utopic
[04:41] <nvrpunk> I would submit a bug report but the fact it hangs doesn't cause apport to do anything
[04:49] <pitti> Good morning
[04:51] <nvrpunk> morning
[07:15] <dholbach> good morning
[07:24] <sladen> guten morgen alle
[09:41] <Saviq> Mirv, do you know if we have a custom backend for QNetworkAccessManager or are we using upstream directly?
[09:43] <Saviq> Mirv, on another topic, any reason why Qt includes are installed in multiarch dirs?
[09:43] <Mirv> Saviq: check the network usage with Wellark
[09:44] <Saviq> Wellark, when around, do you know if we have something custom for backing QNetworkAccessManager, or are we using upstream direct?
[09:45] <Mirv> Saviq: the includes were migrated to multiarch during 5.3.0 in Debian, and we followed. without that it was not possible to properly multi-arch dev packages (even though we did it anyway earlier)
[09:47] <Mirv> if you diff between different archs, there are a small handful of differences if I recall correctly
[09:47] <Saviq> Mirv, well, sure, I'm not saying -dev should be arch: all (they never are are they)
[09:47] <Saviq> Mirv, just that I've never seen any includes to live in multi-arch dirs
[09:48] <Saviq> but sure, you know what you're doing of course
[09:48] <Saviq> was trying to get qmake to x-build over the weekend... that was one thing (qmake using incorrect include dir)
[09:49] <Saviq> ln helped here, but then qmake couldn't find the qt modules :/
[09:49] <Saviq> looks like mkspecs are not good enough to support multi-arch x-building yet
[09:56] <Mirv> Saviq: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=734677 has the background. our earlier multiarching came as part of arm64 work, but I knew it broke policies so I didn't try to put that to Debian
[09:56] <Saviq> Mirv, thanks!
[09:57] <Mirv> Saviq: yeah, x-build still doesn't seem trivial with Qt (qmake) :(
[09:58] <Saviq> Mirv, indeed, right now it feels like we'd need cross-qmake- for every arch combination out there, really not good
[10:51] <Mirv> Saviq: btw feel free to keep https://wiki.ubuntu.com/Touch/CrossCompile maintained nevertheless, especially with examples that would work right now on utopic.
[10:52] <Mirv> I tried it last week when I was asked about it, and failed with everything I tried (either the chain of deps not multi-arch, or some other failure when compiling eg qtbase or qtdeclarative)
[10:52] <Saviq> Mirv, https://bugs.launchpad.net/ubuntu/+source/mir/+bug/1353855
[10:53] <Saviq> Mirv, no one seems to care really
[10:53] <Mirv> Saviq: yeah I had the same with qtdecl that defined 4.8, but after fixing that and it started building, it failed very early anyhow
[10:54] <Saviq> Mirv, what build system?
[10:54] <Saviq> Mirv, with cmake and no 4.9 dep stuff's x-building fine for me?
[10:54] <Saviq> Mirv, also that page seems to duplicate a lot of https://wiki.ubuntu.com/SimpleSbuild
[10:55] <Mirv> Saviq: qtdeclarative, so qmake. I tried also camera-app (cmake) but that apparently had problematic dependencies.
[10:55] <Saviq> Mirv, so yeah, qmake is just a no-no
[10:55] <Saviq> Mirv, anything cmake (without an explicit 4.9 dep) should work
[10:55]  * Saviq tries camera-app
[10:56] <Mirv> Saviq: that /Touch/ page must be better since you're mentioned there :) but so it seems, I'll do some interlinking at least
[10:56] <Saviq> Mirv, I ~wrote the SimpleSbuild one though :D
[10:57] <Mirv> oh, that's a hard choice then :)
[10:59] <Saviq> Mirv, camera-app seems to x-build just fine here, the only big problem I know of is the 4.9 dep, otherwise anything cmake should build
[10:59] <Saviq> aaah wait
[10:59] <Saviq> --host=armhf helps to actually x-build...
[11:00] <Saviq> Mirv, camera-app's just missing :any for the python3 build-dep
[11:00] <Saviq> or :native, but that's not supported everywhere yet
[11:02] <Saviq> some other packaging tweaks needed apparently
[11:04] <Saviq> ah, it's querying qmake...
[11:04] <shadeslayer_> is anyone able to access Jenkins via the public interface?
[11:06] <Mirv> Saviq: yes, I added the :any there, I think after that I didn't figure out the next step. would there be some other easier example package?
[11:06] <Saviq> Mirv, it's querying qmake for QT_INSTALL_QML
[11:06] <Saviq> Mirv, which can't work for x-building
[11:07] <Saviq> simple fix, will have a branch in a mo
[11:20] <Saviq> Mirv, https://code.launchpad.net/~saviq/camera-app/x-build/+merge/232878
[11:20] <Mirv> Saviq: thanks, I'll try that
[11:21] <Saviq> Mirv, there's more changes than necessary (the move from qt5/qml to camera-app, could very well use the original one, but it didn't make sense)
[12:22] <Mirv> Saviq: nice to have a working example, now I can leave that sbuild config around and use every now and then
[12:22] <Saviq> Mirv, cool
[13:46] <pete-woods> I've just done a dist-upgrade on my utopic install, and I no-longer get to the lightdm login screen
[13:47] <pete-woods> I just get to a TTY with errors very similar to the following: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=756247
[13:47] <pete-woods> (they are perhaps unrelated, as I don't usually check the terminal output on boot)
[13:48] <pete-woods> Failed to start unit<EMAIL_ADDRESS>Unknown unit<EMAIL_ADDRESS>[13:48] <pete-woods> is pretty much the error
[15:16] <shadeslayer_> dholbach: ping
[15:17] <dholbach> shadeslayer_, pong
[15:18] <shadeslayer_> dholbach: did anything happen wrt the Canonical legal thing wrt derivatives and stuff
[15:18] <shadeslayer_> I haven't heard back about that in ages
[15:20] <dholbach> shadeslayer_, is this about the changes discussed with the SFLC?
[15:21] <pitti> smoser`: hey Scott, how are you?
[15:22] <pitti> smoser`: so we tracked down a complete juju-local failure through an LXC template problem down to https://cloud-images.ubuntu.com/query/trusty/server/released-dl.current.txt not having a certificate that wget accepts
[15:22] <pitti> smoser`: any idea about that?
[15:22] <pitti> smoser`: for bug https://cloud-images.ubuntu.com/query/trusty/server/released-dl.current.txt
[15:22] <pitti> erk; for bug 1363832
[15:24] <shadeslayer_> dholbach: yes
[15:24] <pitti> smoser`: wgetting that works in trusty, but fails in utopic, apparently it got stricter?
[15:24] <dholbach> shadeslayer_, thanks for the ping - I'll send a mail out to legal again and let you know as soon as I hear back
[15:25] <shadeslayer_> dholbach: cheers
[15:25] <dholbach> shadeslayer_, mail sent
[15:25] <shadeslayer_> Thx
[15:37] <pitti> smoser`: ok, followed up again with some more info
[15:40] <shadeslayer_> does Canonical run a relay SMTP server for ubuntu btw?I wanted to write some scripts that sends out emails, and was wondering if there was a server I could utilize
[15:42] <flexiondotorg> I've got a teeny tiny (but of real importance to me) merge proposal pending. Could someone take a look at it please? https://code.launchpad.net/~ubuntu-mate-dev/ubuntu/utopic/policykit-desktop-privileges/mate-fixes/+merge/230610
[15:43] <flexiondotorg> Here is the corresponding bug report - https://code.launchpad.net/~ubuntu-mate-dev/ubuntu/utopic/policykit-desktop-privileges/mate-fixes/+merge/230610
[15:47] <mitya57> flexiondotorg: I don't have rights to upload that, but why are you not using the Freedesktop standard interface for datetime?
[15:47] <infinity> shadeslayer_: We only run an SMTP relay for Canonical employees (well, for people with accounts on our network, which is basically the same set), nothing wide open for Ubuntu.
[15:47] <shadeslayer_> infinity: okie
[15:48] <infinity> shadeslayer_: I suppose a starttls-authed relay that authenticated aainst SSO and only allowed ubuntu.com users to use it might not be a bad idea, but I'm not sure if it's ever been suggested an rejected, or just not really thought about at all.
[15:49] <flexiondotorg> mitya57, I am using what is define by the MATE desktop.
[15:49] <shadeslayer_> infinity: I see, do you reckon it would be a good idea to suggest it? I wanted to write scripts to email patch authors to add dep3 headers to their patches
[15:49] <infinity> shadeslayer_: (More traditional in our old skool "we want to pretend the internet isn't changing" UNIX admin world to just send mail from our own servers, so perhaps none of us really thought of the need. :P)
[15:50] <shadeslayer_> and I'd rather not run my own smtp server
[15:50] <shadeslayer_> infinity: hehe
[15:50] <mitya57> flexiondotorg: they should really adopt to 2014 realities ;)
[15:50] <infinity> shadeslayer_: Couldn't hurt to file an RT on rt.ubuntu.com and ask if it's feasible and something Canonical IS would be willing to cobble together.
[15:50] <shadeslayer_> ack
[15:50] <infinity> shadeslayer_: The worst you can get is a "no", which is no worse than today.
[15:50] <shadeslayer_> yeah
[15:51] <flexiondotorg> mitya57, Well, that is happening. I'll raise that upstream but this is how is in MATE 1.8. I'll progress the change for MATE 1.10.
[16:27] <saiarcot895> Hi all, is there any place to float a proposal to change a package? I'm considering making a change to the qt4-x11 package.
[16:28] <ogra_> file a bug on launchpad and attach a patch
[16:28] <ogra_> then developers can take a look
[16:30] <saiarcot895> thanks, ogra_
[17:09] <ScottK> saiarcot895: Also it should be discussed upstream unless it's just a change to the packaging.
[17:10] <saiarcot895> ScottK: that might be a good idea, considering I'm planning a change to a typedef used in OpenGL ES cases
[17:10] <ScottK> Definitely.
[17:44] <apachelogger> stgraber: do you know of any issues with lxc-start-ephemeral and unprivileged containers? in particular the container seems to fail to start because of permission problems
[17:46] <apachelogger> stgraber: http://paste.ubuntu.com/8208189/
[19:58] <saiarcot895> If a package was present in precise and utopic but not in trusty, and the package was backported to trusty, would it still go in the trusty-backports section or the trusty section?
[20:17] <mlankhorst> yes
[21:48] <hallyn> wgrant: say, your t440s, does it have the 45W slim charging brick, or the 65W brick?
[21:49] <hallyn> i'm wondering whether the 65W one is overpowring my mobo (once in awhile it shuts off when i plug it in, and won't turn back on for awhile)
[22:49] <TJ-> hallyn: PSUs won't supply more power than the circuit draws; As long as the wattage of the PSU is sufficient for the maximum current draw of the system, any excess ability probably means the PSU will last longer since it doesn't operate so close to its maximum rating
[23:17] <hallyn> TJ-: hm.  that's too bad.
[23:17] <hallyn> i'd rather replace the brick than send the laptop in
[23:18] <TJ-> hallyn: Does the power plug have a central 'data' pin?
[23:19] <hallyn> it has a central pin
[23:22] <TJ-> If it is anything like some infamous Dells, sometimes the very thin data wire in the power cable gets broken by repeated flexing. When that happens the PC can't get the power rating from the PSU. On some systems, that is enough for the firmware to decide to shutdown the PC entirely
[23:23] <TJ-> hallyn: On the Dells, the more common issue was the power socket on the PC would flex slightly as the power connector was pushed home. Over time that caused a broken track on the PCB which broken the data link too... required a new power socket PCB or clever soldering :)
[23:25] <hallyn> the first time it happened there was a smell of burning wire coming from near the 6cell batt, and it wouldn't start until the nxt morning
[23:25] <hallyn> basically the more i let the batteries discharge the more likely it is to get finicky.
[23:25] <TJ-> hallyn: That doesn't sound good! Replace the battery, it sounds like a cell has overheated
[23:25] <hallyn> (it's only a few weeks old)
[23:25] <hallyn> the battery wasn't what smelled, though,
[23:26] <hallyn> hm, i forget which side it was on though
[23:26] <hallyn> and i don't know offhand where the 3cell is
[23:27] <hallyn> stil yeah, maybe it's the 6cell, as the last two times it started up fine whe ni pulled it out.
[23:27] <hallyn> i'll have to experiment some more
[23:27] <TJ-> hallyn: You've certainly got a relatively serious power issue there. Will the system start without a battery attached?
[23:27] <hallyn> dunno - the 3 cell isn't (meant to be :) removable
[23:27] <TJ-> if the charge controller detects problems it'll refuse to power the system, for safety
[23:30] <Unit193> There's been an NMU for http://bugs.debian.org/759528, can that be sync'd?
[23:48] <hallyn> desrt|pdx: (if you're around) so systemd-shim currently listens to org.freedesktop.systemd1.Manager.  To make it listen to org.freedesktop.systemd1.Scope do I need to use a subtree, or is there a simpler way?
[23:56] <hallyn> or is it supposed to be safe to call g_dbus_connection_register_object twice


[00:49] <coz_> hey guys... sometimes... as in at this moment  clean install of lucid  ...firefox bookmarks scroll extreemely slowly
[00:49] <coz_> any solutions to this?  I know its nvidia
[12:27] <tjaalton> bryceh: "BEL"?
[23:17] <trinikrono> hey guys i can use some help to triage some xserver-xorg-video-intel bugs


[00:00] <mup> Bug #1755043 changed: MAAS first run config should give an example with multiple forwarders <MAAS:New> <https://launchpad.net/bugs/1755043>
[00:12] <mup> Bug #1755043 opened: MAAS first run config should give an example with multiple forwarders <MAAS:New> <https://launchpad.net/bugs/1755043>
[01:39] <mup> Bug #1755060 opened: [2.3] Cannot download multiple test results with API/CLI client <cpe-onsite> <MAAS:New> <https://launchpad.net/bugs/1755060>


[01:08] <dtchen> calc: not necessary at this point; we've already narrowed it down. In short, alsa-kernel and alsa-lib are broken for all cards. Fix is in progress.
[01:09] <dtchen> calc: it seems disabling PREEMPT and HZ=1000 in our kernel config makes the bug easier to trigger, so we should thank the kernel team for that
[02:07] <cactaur> Hey everyone! I'm caught in a dilemma. I installed Intrepid and experienced a crippling (for me) bug which renders me unable to use my Desktop's internet. I did work on a bug report, which there hasn't been much activity on recently, but I'm not sure how much longer I can go without internet on my Desktop. So, I'm planning on reinstalling Hardy, but that would mean that I can no longer work on that particular bug. Does anyone have ideas on ho
[02:07] <cactaur> w I can get internet on my Desktop and at the same time be able to supply the bug report with needed information, cause that's one bug I really want squashed (though I can't program).
[02:07] <maco> dual boot?
[02:10] <cactaur> Hmm.... that would work, but is there another way? Cause then I think I'll have issues trying to unify the two if the bug is squashed.
[02:11] <maco> well is it a driver bug?
[02:11] <hggdh> cactaur, at least give us the bug #
[02:11] <maco> i wonder if just booting different kernels would work
[02:11] <cactaur> https://bugs.launchpad.net/ubuntu/+source/linux/+bug/293424
[02:11] <maco> what?
[02:11] <maco> i cannot duplicate that bug
[02:12] <maco> i have an iwl3945 laptop that i used with wep while i was at my parents'
[02:12] <cactaur> maco: Did you use a passphrase?
[02:12] <maco> and...actually it worked even with network manager, now that i think about it. it used to only work from the command line
[02:13] <maco> and it showing a different value after youve entered it when you tell it to show the stored key is normal. in any chipset, nm keeps showing the hash of the key instead of the real key
[02:13] <cactaur> maco: Actually, I was kinda confused with it, cause I'm experiencing the same symptoms with an entirely different chipset. So, I wasn't sure whether to comment on it, or just file a new bug.
[02:13] <maco> i was using a hex thing
[02:14] <maco> are you able to connect if you just use the command line?
[02:15] <cactaur> maco: No, dhclient gets a DHCPREQUEST, but ignores it (see the link to the forum post on my comment for the output)
[02:15] <maco> though i may have already been running jaunty by that point...
[02:15] <maco> on hardy i had to use the command line for wep. in jaunty it works fine even with NM. not sure about itrepid
[02:15] <maco> forum post...
[02:15] <maco> looking
[02:20] <calc> dtchen: great... i think :)
[05:41] <dholbach> good morning
[06:59] <thekorn> good morning
[07:38] <YoBoY> hi
[07:38] <YoBoY> bug 334596 -> wishlist
[07:40] <dholbach> YoBoY: that's a request for getting a new version uploaded - not suitable for brainstorm
[07:40] <YoBoY> arf ^^"
[07:40] <YoBoY> what i have to put for things like this?
[07:43] <dholbach> I'm taking care of this one
[07:43] <YoBoY> ok tanks :)
[07:44] <YoBoY> lol, 3 comments ? xD you need coffee ^^
[07:50] <YoBoY> bug 334563 -> wishlist
[07:59] <savvas> hey, why is "needs-upstream-report" tag kubuntu-specific ?
[08:00] <savvas> it could be used for ubuntu as well, there are a lot of bugs that are practically begging to be forwarded upstream
[08:04] <YoBoY> bug 334479 -> invalid
[08:07] <dholbach> savvas: I don't see why the tag should be used at all - we can simply open en empty upstream task
[08:08] <dholbach> savvas: and can query it from the advanced bug page
[08:08] <persia> I think the use of the tag predates the wide definition of upstream projects.
[08:08] <dholbach> persia: I think tags came after upstream tasks in LP :)
[08:08] <savvas> dholbach: could you give me an example query link in launchpad?
[08:08] <dholbach> savvas: hang on
[08:08] <savvas> thanks :)
[08:09] <persia> dholbach, No, after definitions.  We now have most of the upstream projects defined, but that wasn't always true.  That said, I could well be mistaken.
[08:10] <dholbach> savvas: on the advanced bug page it's "Show bugs that need to be forwarded to an upstream bug tracker "
[08:11] <dholbach> savvas: https://bugs.launchpad.net/ubuntu/+bugs?field.status_upstream-empty-marker=1
[08:11] <dholbach> all Ubuntu bugs with an empty upstream task
[08:12] <savvas> that's amazing! thanks :D
[08:12] <savvas> let me reply to my own email :P
[08:12] <dholbach> :)
[08:24] <savvas> "Displaying first 80 comments.  View all 1005 comments or add a comment. " :P
[08:38] <savvas> mvo: hey, the patch for bug 190907 is working correctly! just tested it in greek - the other user probably didn't do something correctly
[08:39] <mvo> savvas: thanks for confirming!
[08:39] <mvo> savvas: after alpha-5 I will merge it
[08:39] <savvas> great, thanks :)
[08:40] <savvas> 09:38:55 < savvas> mvo: hey, the patch for bug 190907 is working correctly! just tested it in greek - the other  user probably didn't do something correctly
[08:40] <savvas> oops
[08:40] <savvas> sorry
[08:40] <mvo> np
[13:01] <kaushal> hi
[13:02] <kaushal> I am looking out for a Bug which is relevant with tomcat application server which does not log in Catalina.out file in Ubuntu Server 8.04
[14:55] <bddebian> Boo
[15:12] <patanachai> Hi
[15:13] <patanachai> Should bug #334669 > invalid ?
[15:15] <hggdh> patanachai, ask the reporter if he has more details -- what was updated, etc. It is possible that some critical components were upgraded, and an inconsistent state reached... so yes, it is a candidate for INVALID
[15:15] <hggdh> patanachai, but first ask for more details
[15:15] <patanachai> thanks
[15:16] <hggdh> welcome. Thank you for helping.
[15:45] <Laibsch> Hi
[15:45] <Laibsch> Did anybody else ever experience high WLAN load resulting in a drifting mouse? -> bug 334957
[15:46] <Laibsch> If it wasn't so annoying, it'd be one of the more funny bugs
[15:50] <IntuitiveNipple> shared interrupts issue maybe?
[15:54] <Laibsch> IntuitiveNipple: BIOS?
[15:54] <Laibsch> Where do I look
[15:55] <IntuitiveNipple> Start with cat /proc/interrupts and also look in the dmesg or kern.log to determine what interrupts the hardware is assigned
[16:02] <Laibsch> thanks
[16:10] <Laibsch> IntuitiveNipple: Seems like indeed they are using the same interrupt
[16:10] <Laibsch> I'll reboot in a little while and see if I can change something in the BIOS
[16:11] <Laibsch> In case that is not possible, is there anything on the software side that could be improved?
[16:11] <IntuitiveNipple> Laibsch: Sharing interrupts isn't bad, but in some circumstances drivers can get confused
[16:11] <IntuitiveNipple> Laibsch: Does /cat/interrupts show an unusually larger number of interrupts for their shared IRQ # ?
[16:12] <Laibsch> I added the output to the bug
[16:12] <Laibsch> unfortunately, the tabs were collapsed to single white space and thus the output isn't cleanly formatted
[16:12] <Laibsch> The information is there, though
[16:13] <Laibsch> IntuitiveNipple: is what you are asking for the second column, 1897568 in this case?
[16:13] <Laibsch> Not sure if that would be high or not.
[16:14] <IntuitiveNipple> what kind of mouse is it?
[16:16] <hggdh> Laibsch, this is the interrupt count since the last reboot
[16:17] <hggdh> sort of high, yes, unless the system has been up for quite a long time (think weeks or months)
[16:18] <IntuitiveNipple> It looks like almost everything wants to share #11
[16:18] <Laibsch> $ uptime
[16:18] <Laibsch>  01:18:30 up 21:11,  5 users,  load average: 2.49, 1.17, 0.88
[16:18] <Laibsch> yes, everything is on #11, more or less
[16:22] <Laibsch> IntuitiveNipple: It is a USB mouse from Logitech, I think the name is MX310, that is what is says on the underside
[16:26] <IntuitiveNipple> Laibsch: OK, nothing ultra high resolution then
[16:27] <IntuitiveNipple> It does look as if somehow the input driver is seeing spurious interrupts. I've seen it before on both Windows and Linux.
[16:27] <Laibsch> Alright, what I should do now?
[16:28] <Laibsch> To resolve the situation for me, I'll see if I can do something in the BIOS
[16:28] <Laibsch> to get the mouse onto another interrupt
[16:28] <Laibsch> But what about the bug report.  I wonder if there is some information I could provide that would help improve the driver.
[17:39] <Kaushal> hi
[17:40] <Kaushal> Good Afternoon everyone
[17:45] <hggdh> cheers
[17:47] <Kaushal> hggdh, I was looking for a Bug which i dont recollect the Bug ID which was regarding no logging in Catalina.out file of tomcat application server
[17:47] <Kaushal> I think its being closed
[17:47] <Kaushal> is the issue fixed ?
[17:48] <hggdh> Kaushal, did you try LP advanced searc (and make sure you select also the closed stati)
[17:48] <Kaushal> hggdh, i could not locate it in http://bugs.launchpad.net
[17:49] <Kaushal> I have also used the Advanced search too
[17:51] <hggdh> hold on
[17:52] <Kaushal> sure
[17:52] <hggdh> you opened it agaisnt which package?
[17:53] <Kaushal> Ubuntu 8.04
[17:53] <hggdh> give me some possible search terms
[17:54] <Kaushal> no logging in catalina.out file
[17:56] <YoBoY> Kaushal: have you commented this bug?
[17:57] <Kaushal> YoBoY, i have not commented on that Bug
[17:58] <Kaushal> Actually I am looking out for that Bug which i wanted to discuss with my Engg team
[17:59] <YoBoY> not one of these ? https://bugs.launchpad.net/ubuntu/+bugs?field.searchtext=Catalina&orderby=-importance&search=Search&field.status%3Alist=NEW&field.status%3Alist=INCOMPLETE_WITH_RESPONSE&field.status%3Alist=INCOMPLETE_WITHOUT_RESPONSE&field.status%3Alist=CONFIRMED&field.status%3Alist=TRIAGED&field.status%3Alist=INPROGRESS&field.status%3Alist=FIXCOMMITTED&field.assignee=&field.bug_reporter=&field.omit_dupes=on&field.has_patch=&fi
[17:59] <YoBoY> eld.has_no_package=
[17:59] <hggdh> but you opened it
[17:59] <YoBoY> (arg sorry)
[18:00] <hggdh> Kaushal,  what is you userid on LP?
[18:01] <Kaushal> hggdh, i dont think so i have one
[18:01] <hggdh> if you do not have a LP Id, you cannot open a bug there...
[18:02] <Kaushal> hggdh,Let me explain it briefly
[18:03] <Kaushal> I have installed Ubuntu 8.04 Server and installed tomcat on it using apt-get
[18:04] <Kaushal> so when i uploaded my WAR into it, i could not see any logging in Tomcat Catalina.out file
[18:05] <hggdh> but you did not open a bug
[18:05] <Kaushal> nope
[18:05] <Kaushal> I saw a similar Bug being opened by someone else
[18:05] <Kaushal> but now i am not able to trace that Bug ID
[18:06] <Kaushal> so wanted to know is that Bug resolved
[18:07] <hggdh> ah
[18:08] <hggdh> well, we are even more limited than you there... we know less than you on this particular issue.  YoBoY's search is pretty much what I found also
[18:08] <Kaushal> ok
[18:10] <Kaushal> hggdh, so is it difficult to get that Bug ?
[18:12] <hggdh> given what you told us, this is as far as we can get
[18:13] <IntuitiveNipple> Kaushal: Have you looked in /var/log/syslog ?
[18:13] <Kaushal> IntuitiveNipple, yes
[18:13] <IntuitiveNipple> nothing there from Tomcat?
[18:14] <Kaushal> nothing
[18:14] <IntuitiveNipple> which version of tomcat is it?
[18:14] <Kaushal> tomcat 5.5.25
[18:16] <Kaushal> IntuitiveNipple, is it https://bugs.launchpad.net/ubuntu/+source/tomcat5.5/+bug/303058
[18:16] <Kaushal> ?
[18:18] <IntuitiveNipple> I was going to suggest that one to you... you tell me :)
[18:18] <IntuitiveNipple> I was just looking at a Hardy installation to see what is there. No file in /var/log/tomcat5.5/
[18:19] <Kaushal> IntuitiveNipple, is there a workaround for https://bugs.launchpad.net/ubuntu/+source/tomcat5.5/+bug/303058
[18:20] <IntuitiveNipple> Kaushal: I don't know. You might want to check /etc/tomcat5.5/logging.properties
[18:23] <IntuitiveNipple> Are you using the standard sever.xml?
[18:24] <Kaushal> IntuitiveNipple, yeah
[18:25] <IntuitiveNipple> OK. Have you started Tomcat manually at a console and looked at what it reports for clues?
[18:25] <Kaushal> nope
[18:26] <Kaushal> How can i start manually >
[18:26] <Kaushal> ?
[18:30] <IntuitiveNipple> I don't have it installed here on Jaunty, but I've chroot-ed to the Hardy install to see what it does. The most obvious thing is in the /etc/init.d/tomcat5.5 script where it starts it and sets SYSLOG for console output: "$DAEMON -user "$TOMCAT5_USER" -cp "$JSVC_CLASSPATH" -outfile SYSLOG -errfile SYSLOG  -pidfile "$CATALINA_PID" $JAVA_OPTS "$BOOTSTRAP_CLASS"
[18:32] <IntuitiveNipple> The reason is, according to both the man-page and "start-stop-daemon --help" -outfile -errfile don't exist
[18:33] <Kaushal> ok
[18:33] <IntuitiveNipple> Have you tried the solution suggested in #277508 ?
[18:34] <Kaushal> IntuitiveNipple, great
[18:34] <Kaushal> I would use that workaround
[18:34] <Kaushal> IntuitiveNipple, Thanks a Lot
[18:35] <thekorn> hi bdmurray, can you please renew my membership in bughelper-dev
[18:35] <Kaushal> IntuitiveNipple, you said <IntuitiveNipple> The reason is, according to both the man-page and "start-stop-daemon --help" -outfile -errfile don't exist
[18:35] <Kaushal> what did you searched for the man page
[18:35] <IntuitiveNipple> Kaushal: Yes, I'm not convinced those options exist since I can't find any other uses of them either, but I wondered if you're tried #277508 suggestion?
[18:35] <Kaushal> Just curious to know
[18:36] <IntuitiveNipple> Kaushal: man start-top-daemon
[18:36] <IntuitiveNipple> Kaushal: or start-stop-daemon --help
[18:36] <IntuitiveNipple> Kaushal: I'd always trust the program over the man-page since man-pages can and do get out-of-date
[18:37] <IntuitiveNipple> Kaushal: My bet is that init.d/ script was designed to work across several different Linux distributions, and the one it was tested on, a different start-stop-daemon is used that does accept -outfile -errfile
[18:38] <Kaushal> IntuitiveNipple, ok
[18:40] <Kaushal> IntuitiveNipple, so it should work if i use #277508
[18:40] <Kaushal> right
[18:40] <bdmurray> thekorn: you are an admin of the team ;-)
[18:41] <thekorn> bdmurray, right, but I can't renew my own membership
[18:41] <IntuitiveNipple> Kaushal: *only* if start-stop-daemon supports -outfile and -errfile
[18:41] <bdmurray> that's weird
[18:42] <thekorn> that's launchpad ;)
[18:43] <IntuitiveNipple> Kaushal: Which JVM are you using to host tomcat?
[18:43] <Kaushal> IntuitiveNipple, I am using sun-java5-jdk
[18:43] <IntuitiveNipple> I've installed tomcat5.5 on Jaunty here and it is logging to syslog, but I noticed in its /etc/init.d/tomcat5.5 it says "# juli LogManager disabled if running under gij (see bug #395167)" - and the logging is set by default to use apache juli
[18:44] <Kaushal> IntuitiveNipple, start-stop-daemon doesnot support -outfile or -errfile
[18:44] <IntuitiveNipple> Kaushal: lol ignore me about -outfile.... I just noticed it uses /usr/bin/jsvc as the DAEMON !! :*blush*
[18:45] <Kaushal> It wont work
[18:45] <IntuitiveNipple> That'll teach me to read the init script clearly
[18:46] <IntuitiveNipple> Kaushal: jsvc.exec[1779]: 26-Feb-2009 18:41:39 org.apache.coyote.http11.Http11BaseProtocol init INFO: Initializing Coyote HTTP/1.1 on http-8180
[18:50] <Kaushal> IntuitiveNipple, so that suggestion wont work
[18:50] <Kaushal> right ?
[18:50] <IntuitiveNipple> It *might* now I realised it uses jsvc
[18:58] <Kaushal> IntuitiveNipple, where do i seek help for this issue ?
[18:58] <IntuitiveNipple> You should post a new bug report and describe the versions and what precisely you are doing and assign it to the tomcat package so the package maintainers get pinged
[18:59] <Kaushal> great
[19:11] <savvas> can someone set bug 267513 as Triaged please?
[19:21] <hggdh> savvas, done. I thought you would be able to do it yourself...
[19:24] <salty-horse> hi. using jaunty, /var/log/messages shows a usb device is connected, but nautilus doesn't mount it (set the correct options in nautilus's preferences). any ideas?
[19:24] <savvas> hggdh: I didn't apply to be a bug triager :)
[19:25] <savvas> not yet that is :P
[19:56] <hggdh> heh
[20:32]  * bcurtiswx waves to room
[20:32]  * Ienorand waves back
[21:38] <bcurtiswx> seb128: was my response alright in the rhythmbox bug? or should I have gone about that differently? j/w
[21:39] <seb128> bcurtiswx: bug number? I look to 60 rhythmbox bugs or so today and didn't pay attention to the submitter nicknames
[21:39] <seb128> look -> looked
[21:39] <bcurtiswx> seb128: bug #335062
[21:39] <seb128> bcurtiswx: yes, it's good!
[21:39] <seb128> that's the right stock reply for such bugs ;-)
[21:40] <bcurtiswx> seb128: ok thx, always trying to learn wherever i ca n
[21:40] <bcurtiswx> can*


[10:05] <ddaa> Yeay
[10:05] <lifeless> poolie sends apologies
[10:06] <ddaa> Let's start
[10:06] <ddaa> MEETING STARTS
[10:07] <ddaa> sorry being late, just came back home, jetlag and stuff
[10:07] <ddaa> == Agenda ==
[10:07] <ddaa> Next meeting Monday 4 December, 09:00-09:45 UTC.
[10:07] <ddaa>  * production status
[10:07] <ddaa>  * naming convention [SteveA]
[10:07] <ddaa>  * status reports
[10:08] <ddaa> == Roll call ==
[10:08] <ddaa> _thumper_ is on leave until start of December.
[10:08] <ddaa> lifeless says: poolie sends apologies
[10:08] <SteveA> morning
[10:08] <ddaa> jamesh: ping
[10:08] <ddaa> spiv: pin
[10:08] <jamesh> hi
[10:09] <SteveA> the pin is mightier than the sword
[10:09] <spiv> I'm here.
[10:09] <ddaa> There was a kiwi woman at the hostel... I figured out that .nz people "spin time" :)
[10:10] <ddaa> okay 'vrybody in there
[10:10] <ddaa> == Production status ==
[10:10] <ddaa> New rollouts or production problems.
[10:10] <SteveA> ddaa: there is a bar/restaurant place call Bazar just down the road from me
[10:10] <SteveA> http://www.specialnite.com/venues/location/the_pijp/bazar/
[10:11] <ddaa> SteveA, the one you recommended to me for a stay in Rotterdam?
[10:11] <SteveA> on the subject of new rollouts, when can we expect the smartserver to run on the supermirror?
[10:11] <ddaa> So, anything of notice happened in the past two weeks or so in production?
[10:11] <SteveA> and also the viewcvs kinda stuff?
[10:11] <ddaa> Is there anything in production in need of firefighting?
[10:12] <lifeless> SteveA: so there is a wsgi module for it. AFAIK its just a matter of configuration now.
[10:12] <lifeless> spiv: is that right ?
[10:12] <spiv> lifeless: Partly ;)
[10:12] <lifeless> spiv: for the http side that is
[10:13] <spiv> lifeless: where "configuration" includes "make it work with the different directory layout on disk"
[10:13] <SteveA> I'd like us to have a meeting (not this one) to determine exactly what needs doing so that we can have the smartserver runing on the supermirror
[10:13] <SteveA> and who is going to do it and when
[10:13] <SteveA> right after this here meeting works for me
[10:13] <spiv> Which is possibly taken care of by the apache magic already, but I don't know exactly how that hooks together yet.
[10:13] <ddaa> spiv has review meeting just after this one AFAIK
[10:14] <SteveA> true.  so do i
[10:14] <lifeless> spiv: if we can pass the path in to the vfs - the chroot transport should be all we need. just command line glue
[10:14] <spiv> Also, there's an issue that the admins don't like mod_fastcgi, so the magic to hook up WSGI with something else (probably mod_python) needs to be figured out.
[10:14] <lifeless> spiv: they dont ?
[10:15] <jamesh> they won't run fastcgi, but they'd run Bazaar code within apache?
[10:15] <spiv> lifeless: there's a non-free fastcgi thing for a apache, or a free one that sucks, apparently.
[10:15] <spiv> I spoke to elmo about it briefly at allhands.
[10:15] <lifeless> how badly does it suck? I mean, is it worth more dev time to reimplement something that exists..
[10:16] <spiv> Well, there's lots of existing modules for connection WSGI to stuff, including, I believe, mod_python stuff, so it's not something we'd have to implement ourselves.
[10:17] <spiv> It's also likely we'll want mod_python on the supermirror eventually as a better way to do the URL rewriting that mod_rewrite + a huge periodic dump file from the database.
[10:17] <SteveA> or just run it as a twisted daemon?
[10:17] <jamesh> mod_python basically means allowing the code to do whatever apache can, which is why I was surprised the admins would prefer that
[10:17] <SteveA> jamesh: it's a freeness issue I think
[10:18] <ddaa> spiv: that sounds like a useful cleanup, but the mod_rewrite problem has not been a problem so far.   I'm getting confused.  I want to explain what I want out of this.
[10:19] <SteveA> What I want is a set of numbered list items on a wiki page that lays out all the steps from where we are now, to having the supermirror running the smartserver.  If there are parts that need investigation then that item says
[10:19] <SteveA> "investigate [foo]  to determine whether [bar] "
[10:20] <SteveA> spiv: I'd like you to be responsible for writing this
[10:20] <spiv> SteveA: ok.
[10:20] <spiv> I think that's a good idea.
[10:20] <ddaa> spiv: today after review meeting might be late for you. What about meeting tomorrow? Who else than you, SteveA and I needs to be present?
[10:20] <SteveA> then next time I ask "how is this going", you'll be able to say "did A then B, and the result of investigating [foo]  was [bar] "
[10:21] <SteveA> ddaa: I think we don't need the meeting, if spiv writes the doc.
[10:21] <spiv> I'll write the doc within 24 hours, put it on the wiki, and post to the list about it.
[10:21] <SteveA> thank you spiv
[10:21] <ddaa> ACTION: spiv writes supermirror-smart-server plan
[10:21] <spiv> I think discussion about it can probably be done adequately by email.  If it turns out to be a messier than expected discussion, we can look at scheduling a meeting.
[10:22] <SteveA> I'd like the same for viewcvs-style support, at some point
[10:22] <ddaa> spiv: ++
[10:23] <ddaa> SteveA: let's talk this week about what we'd like Tim to work on next month. The bzrweb integration could be one of those items.
[10:23] <ddaa> Moving on.
[10:24] <ddaa> == Naming convention ==
[10:24] <ddaa>  * Use a naming convention for branches to be hidden/removed (Steve Alexander)
[10:25] <SteveA> a bzr / supermirror user asked for a branch of his to be removed
[10:25] <SteveA> or hidden
[10:25] <SteveA> as it was just an experiement
[10:25] <SteveA> I spoke with him, and found out that he wanted it hidden just for aesthetic reasons
[10:25] <SteveA> that is, no problems with illegal data or anything
[10:25] <SteveA> I explained we can't easily do that right now
[10:26] <SteveA> he said okay, and suggested that we use a naming convention for branches that are to be hidden
[10:26] <SteveA> so that people can use this now, and they get hidden when we have support in the code
[10:26] <SteveA> maybe branch--hidden or something
[10:26] <ddaa> mh... double dash...
[10:26] <lifeless> I dont understand why we dont just use branch status
[10:27] <jamesh> hiding obsolete branches by default?
[10:27] <lifeless> right
[10:27] <lifeless> with a 'show all' page to show them
[10:27] <spiv> Also "merged" branches.
[10:27] <ddaa> lifeless: because we want to represent a "deleted" state, for branches that should eventually be garbage collected
[10:27] <lifeless> I feel quite uncomfortable with the idea of conflating 'hide branches' and 'name'
[10:28] <ddaa> which is different from merged/abandoned, which should appear in the "show all branches" listing even when we have branch deletion support
[10:28] <lifeless> ddaa: so add a state for that. One new entry in the dbschema, called 'to be deleted'.
[10:28] <ddaa> which is awkyard since it's not clear whenever we will actually support it
[10:28] <SteveA> I think we should use the name for this, unless the software will support it reasonably soon, conflation or no conflation
[10:28] <ddaa> also it's more work than just agreeing on a naming convention
[10:29] <jamesh> if we have a  "to be deleted" state, people might expect the branch to stop being published.  Is that the intent?
[10:29] <SteveA> the name is something users can change today, and the conflation is not harmful in the long term.  it just goes away.
[10:29] <SteveA> becauase the branches do
[10:29] <ddaa> I think I already used something like "status=obsolete name=<foo>-deleted[-N] "
[10:29] <spiv> SteveA: We already have a status field with values like "obsolete" and "merged".  Why not make the proposed UI changes use that?
[10:29] <SteveA> spiv: we can.  if it is done *soon*
[10:29] <ddaa> I like SteveA's suggestion
[10:30] <ddaa> I think I understand the issue, and I'll reply to the questions by email today.
[10:30] <SteveA> I want to avoid us leaving this gap on account of a feature that won't be ready soon.  So, if soon, great.  If not soon, workaround.
[10:31] <ddaa> workaround sounds better to me right now, it's less commitment and avoids raising expectations, and having more stub features in the UI.
[10:31] <ddaa> Shall we move on?
[10:32] <ddaa> == Status reports ==
[10:32] <ddaa>  * spiv: supermirror-smart-server.
[10:32] <ddaa>  * jamesh: spec-branches.
[10:32] <ddaa>  * ddaa: python import.
[10:32] <jamesh> spec-branches is still in the queue
[10:33] <ddaa> python import: up and running since all-hands
[10:33] <ddaa>  * ddaa: pyrex.
[10:33] <spiv> The status of supermirror-smart-server is probably best addressed by the wiki page I've promised to write shortly.
[10:33] <ddaa> Dunno if SteveA has reviewed the pyrex branch, or if their status has changed somehow.
[10:34] <spiv> So I'll skip that for now, if that's alright.
[10:34] <ddaa> spiv: that's alright, it's been discussed enough at the beginning of the meeting.
[10:34] <SteveA> so, the pyrex thing is ddaa's experimental new svn bindings, focused on what we need
[10:34] <SteveA> is that right?
[10:35] <ddaa> SteveA: that's right
[10:35] <SteveA> how complete is the pyrex stuff for what we need?
[10:35] <ddaa> Not complete yet. Includes removal of dep on native swig bindings.
[10:36] <ddaa> Now, the prereq have been merged to allow the work to start on using svn_ra API for the critical code paths.
[10:37] <SteveA> what is svn_ra
[10:37] <SteveA> ?
[10:37] <SteveA> what do you want to do with this branch?
[10:37] <ddaa> Which will allow very substantial improvements in efficiency. But I'd like feedback on the proof-of-concept code that's already pending review.
[10:37] <ddaa> svn_ra is the low-level "talk with svn over the wire" API
[10:37] <jamesh> ra == repository access
[10:39] <ddaa> goals: simplify the code (only one entry point to libsvn, thin bindings), more flexibility (allow access to all libsvn functionality), more efficient (allow using functionality not available with pysvn)
[10:39] <ddaa> ultimately, the problem is that all all python-libsvn bindings suck in one way or another
[10:40] <ddaa> and the svn import code has reached the point where that's become the next roadblock.
[10:41] <SteveA> what problems are we seeing that are blocked by shoddy bindings?
[10:41] <ddaa> using svn_ra allows to use a single session in the critical loop, which cuts down on round-trip and connection count
[10:41] <ddaa> SteveA: imports failing because of connection errors in the middle of the import
[10:42] <ddaa> current code involves literally thousands of connections (sequential) for even moderately sized imports
[10:42] <ddaa> makes it slow
[10:42] <ddaa> makes it unreliable
[10:42] <ddaa> and put uncessary load on community resources
[10:42] <SteveA> ok.
[10:43] <SteveA> lifeless: what would you suggest to do with ddaa's branch next?
[10:43] <lifeless> SteveA: its currently in the review queue, with you as the reviewer.
[10:44] <lifeless> I dont really get the question I think. Surely we want to achieve two things
[10:44] <SteveA> I'm not really qualified to review it
[10:45] <lifeless> 1) demonstrate that this is a solid, reliable way forward. I.e. check that callbacks work properly, and that the apr memory pool stuff is managed well
[10:45] <lifeless> 2) start using it.
[10:45] <lifeless> I would ask for the same thing you asked spiv to do - a list of whats needed to achieve these two things.
[10:46] <SteveA> thank you lifeless
[10:46] <SteveA> I agree with your points
[10:46] <SteveA> in addition, for point 1, this is a new binding that we'll be maintaining
[10:47] <SteveA> so we should have a good sense that it is a better way to proceed than maintaining existing bindings
[10:47] <lifeless> the existing bindings are both hard to maintain
[10:47] <SteveA> questions like, has the upstream for any of the bindings improved things since we last looked?
[10:47] <lifeless> I vouch for them being difficult
[10:48] <ddaa> meeting time ended: jamesh, spiv, you can go and workrave
[10:48] <SteveA> ddaa: I think you should do some more management of the meeting
[10:48] <SteveA> simply announcing that the time is ended is not good meeting management
[10:49] <ddaa> well, anyway all theh points have been adressed
[10:49] <ddaa> we can continue to talk about the svn bindings
[10:49] <ddaa> jelmer has posted some improvements to the upstream swig bindings
[10:49] <SteveA> lifeless: ok, so someone competent to do so needs to review it for the points you listed
[10:49] <ddaa> it's in the svn 1.5 branch and backported in edgy
[10:50] <ddaa> however, the swig bindings are not reliably maintained upstream
[10:50] <SteveA> also, is there value in this being released as open source if we do decide to go with it, to get other contributions?
[10:50] <lifeless> I think so.
[10:50] <ddaa> the pyrex bindings will be released as they are part of cscvs
[10:50] <ddaa> and releasing cscvs is something I want to do before the end of the year
[10:50] <SteveA> ddaa: the pyrex bindings exist as your private experiment.  they are not part of cscvs at this point
[10:51] <ddaa> SteveA: well, assuming they get merged, of course
[10:51] <SteveA> one of the points of this review process is to decide whether we switch to them
[10:51] <lifeless> it doesn't make a lot of sense to me for the bindings to be part of cscvs
[10:51] <ddaa> makes sense to me, as they are very focused on what cscvs needs
[10:51] <ddaa> to keep them as simple as possible
[10:51] <ddaa> no more exposed functionality than necessary
[10:51] <ddaa> so, no more bugs than necessary
[10:52] <SteveA> it's an API binding
[10:52] <SteveA> adding new API to it won't create bugs in the rest, I think
[10:53] <ddaa> I see them more as a glue. Generic libsvn bindings is... complicated, it's not a nice-and-simple API
[10:53] <SteveA> if there's a point in releasing it, it's so that people get interested in it, perhaps to extend it, and reduce our maintenance burden
[10:53] <spiv> It's a clearly independent module in terms of functionality.  If nothing else, keeping them seperate will make it easier for the community to contribute to them.
[10:53] <SteveA> trying to enforce a false limit on its scope will not help people get interested in it
[10:54] <spiv> A small, fairly simple set of pyrex files is much less scary to a potential contributor than those files + all of cscvs, which is pretty hairy in parts.
[10:54] <ddaa> I do not think there is intrinsic value in getting people interested in them. If there was actual interest in the python community for effective libsvn bindings, we would not have to roll our own.
[10:54] <spiv> And similarly, a contributor to cscvs might be scared by the false impression they have to learn pyrex or compile stuff to hack on cscvs.
[10:56] <ddaa> spiv: right, it would be good to clean up the cscvs packaging to have clear modules and extension points. The overall design is okay, but the execution is not quite there in terms of practical modularity.
[10:56] <spiv> I think we should try fairly hard to be a good open source citizen, providing reasonably neatly packaged source, rather than just a messy, tangled dump.  We will damage the goodwill we generate by releasing source if we do it in a community-hostile way.
[10:57] <SteveA> ok
[10:57] <ddaa> some truth in that. That's why I want to keep this release low-key.
[10:57] <ddaa> It's just there for people who have expressed a desire to help already.
[10:57] <SteveA> who will review ddaa's pyrex stuff?  someone who knows about how svn bindings need to work.
[10:58] <jamesh> spiv:a separately packaged binding only really makes sense if things other than cscvs will use it
[10:59] <jamesh> if the aim of the binding is just "as much of libsvn as cscvs needs", then it doesn't really have a separate target audience
[10:59] <ddaa> jamesh: ++
[10:59] <ddaa> Also, the code might be independent in terms of  functionality, but there's value in keeping it couple in terms of design for KISS compliance.
[11:00] <jamesh> plus, if the binding is "as much of libsvn as cscvs needs", then you may need to update the two in lockstep anyway
[11:00] <lifeless> I have to run another meeting now
[11:00] <lifeless> I suggest that spiv or jamesh review the code forits pyrexstyle.
[11:00] <jamesh> which makes separate packages less useful
[11:00] <lifeless> I have done some  pyrex too, so in a pinch I can review it.
[11:01] <lifeless> for the svn style, me/spiv/jamesh can review it I suspect.
[11:01] <spiv> I know some pyrex, and some high-level svn, but not svn API.
[11:01] <lifeless> use of svn API should not be reviewed in this regard I think
[11:01] <lifeless> thats ddaa's problem :)
[11:02] <ddaa> yeah, anyway current code is mostly bug-for-bug compatible
[11:02] <ddaa> I just want guidance on coding standard, code organisation, etc.


[12:30]  * abogani waves all
[12:30] <abogani> I have just updated -lowlatency and -realtime kernels.


[10:55] <theDoomLord> Please, what happened with the Jordanian team, I am waiting for centuries, I told you the problem two years ago and every time i ask you tell me to wait, 6 months ago stopped to respond to me


[07:06] <hateball> I am having an annoying issue I can't quite pinpoint. I am running Kubuntu 23.04 with Wayland. It appears that if I let the monitor go into powersave and wake back up again it seems to break hardware acceleration in xwayland apps eg Steam + any games launched. I have to restart the entire desktop session to restore performance. I am using mainline kernel 6.2 and and MESA from oibaf ppa because otherwise my Ryzen 7700x and Radeon 7900 XTX do not work.
[07:24] <hateball> Maybe this is specific to Steam... as Chrome is also running under xwayland and it behaves as it should
[07:30] <tomreyn> or maybe chrome doesn't use HW acceleration
[07:34] <hateball> Yes well I am reading bugreports about that as well, except sometimes it *does* work
[07:34] <hateball> And then both the Steam client itself as well as the games launched behave properly
[07:36] <hateball> If I have Steam maximized behind another window, the mouse cursor will still be choppy when moving in eg Quassel. But if I minimize Steam to the tray then the issue goes away.
[07:37] <hateball> I don't mind that too much, the big annoyance is having to restart the entire session and hope Steam behaves next time, in case I want to play a game
[08:16] <tomreyn> hateball: since you have two GPUs there, one internal anod another dedicated one, you could also consider installing windows in a VM for gaming and using that with KVMFR / Looking Glass
[08:16] <hateball> :|
[08:16] <hateball> Thanks, but no.
[08:17] <hateball> Also I only have one dGPU, Ryzen 7700x is the CPU :)
[08:27] <tomreyn> yes, you have one iGPU and one dGPU
[08:28] <tomreyn> 7700x includes an internal GPU, which would be sufficient to run Ubuntu on, and then you could do the gaming on the dedicated one which you'd passthru to the VM (at least while you're gaming)
[08:30] <hateball> Yeah that's fair enough, however I have no desire to use Windows at all
[08:30] <hateball> Under pure X11 Steam seems to behave but then everything else is a worse experience
[08:37] <hateball> I was thinking if it would be possible to run a separate xserver on another tty and just have steam running there, but I am sure that unless I run it as a different user it'll cause all sorts of breakage with the primary wayland/xwayland session
[08:38] <hateball> Also I don't feel like doing all sorts of workarounds just because of one crappy app


[02:20] <gnomefreak> asac: if your around, i know its a bit early for you to be here, however what standards on FTBFS would be upstream problem as opposed to local bug? [reed] if your here please feel free to give me some guide on how to tell upstream FTB or our FTB
[02:40] <asac> gnomefreak: depends
[02:41] <asac> gnomefreak: we should ensure its not a problem on our side before asking upstream to look into it
[02:41] <gnomefreak> asac: if iget time tomorrow i will try again
[02:52] <gnomefreak> ok grabbinb latest daily and going to bed im tired and cranky as hell
[07:06] <kaushal> hi
[07:06] <kaushal> when is Firefox 3.0.9 going to be added in Ubuntu 8.04 repository ?
[07:41] <kaushal> checking in again for my query :)
[09:00] <kaushal> hi again
[09:00] <kaushal> reposting my query here again, when is Firefox 3.0.9 going to be added in Ubuntu 8.04 repository ?
[09:28] <ghindo> kaushal: When it's added to the other Ubuntu repositories? :p
[09:28] <ghindo> kaushal: Probably not too long.  When was it released?
[09:33] <kaushal> http://www.mozilla.org/security/announce/2009/mfsa2009-14.html
[12:39] <directhex> guys, how do i go about debugging a plugin?
[12:40] <asac> directhex: plugin != extension
[12:40] <asac> what do you mean ;)
[12:40] <asac> kaushal: we wait 24h before releasing security updates
[12:40] <asac> kaushal: in that way we dont run into regressions and let mozilla catch them for us
[12:40] <directhex> asac, i said plugin!
[12:41] <asac> directhex: you never know ;)
[12:41] <asac> directhex: i guess you know that there is no general answer to that question, right?
[12:42] <directhex> asac, how do i set a breakpoint on a plugin with "firefox -g", since the plugin and its symbols aren't loaded until FF has been run?
[12:43] <asac> directhex: usually setting breakpoints up-front works
[12:43] <asac> directhex: if your plugin spawns a new process you need to tell gdb to follow that
[12:47] <directhex> 0x00007fdd8b7275a4 in MoonWindowGtk::InitializeFullScreen (this=Cannot access memory at address 0x7ffeffffffc8
[12:47] <directhex> ) at window-gtk.cpp:50
[12:47] <directhex> 50		GdkWindow *gdk = parent->GetGdkWindow ();
[12:47] <directhex> that's the best i've got from it so far
[12:52] <directhex> ooh, i got a breakpoint to break
[12:53] <directhex> hm, what a big backtrace
[12:55] <kaushal> asac: Thanks :)
[12:55] <directhex> http://pastebin.ca/1399539
[12:56] <kaushal> asac: I didnot understand about this line < asac> kaushal: in that way we dont run into regressions and let mozilla catch them for us
[12:56] <kaushal> give me examples :)
[12:56] <asac> kaushal: from time to time mozilla - after doing weeks of QA and stuff - release and suddenly something is broken
[12:56] <asac> thats a regression
[12:56] <asac> the worst regressions are usually detected quite quickly
[12:57] <asac> so waiting 24h is enough
[12:57] <asac> we released at the same minute in the past, but at some point there was a data loss regression
[12:57] <asac> and mozilla has a heavy weight QA process
[12:57] <asac> (which is good)
[12:57] <asac> so it took a couple of days again
[12:57] <asac> and we were not supposed to release a quick fix to our users without waiting for them
[12:58] <asac> thats why i dont release at the same time anymore and let them catch the bugs for us ... so i dont have to sit a week on a patch that would fix our users suffering, but not being allowed to distribute that
[12:58] <asac> (because of trademark stuff)
[13:00] <asac> kaushal: hope that explains it
[13:01] <kaushal> asac: awesome much appreciated :)
[13:01] <kaushal> asac: great and Thank you
[13:03] <asac> directhex: ;)
[13:03] <directhex> hm?
[13:03] <asac> directhex: referred to "what a big backtradce"
[13:03] <asac> directhex: so all figured?
[13:04] <kaushal> asac: we as in means "ubuntu" right ?
[13:04] <kaushal> or canonical ?
[13:05] <asac> kaushal: what part are you referring to?
[13:05] <kaushal> 17:10 #ubuntu-mozillateam: < asac> kaushal: we wait 24h before releasing security updates
[13:05] <asac> kaushal: thats ubuntu ... yeah
[13:05] <directhex> asac, working with upstream
[13:06] <asac> kaushal: but thats also kind of canonical ;)
[14:25] <directhex> asac, upstream reckons it's an ubuntu problem of some kind, and i reckon they're right.
[14:26] <directhex> asac, the problem doesn't occur with the .xpi download of the plugin
[15:22] <asac> directhex: thats not really much info you are giving ;)
[15:23] <directhex> giving it as i get it!
[16:11] <asac> directhex: you didn't tell me what the bug is about at all :)
[16:12] <directhex> asac, moonlight-plugin-mozilla causes browser crashing if you try to display a full-screen video (test site is http://videoshow.vertigo.com)
[16:12] <directhex> asac, happens with packages but not upstream .xpi, so it's something ubuntuish causing issues
[16:13] <asac> directhex: moonlight is in the archive?
[16:13] <directhex> asac, sure
[16:13] <asac> so they do stupid plugin guessing and dont trigger ubufox
[16:13] <asac> stupid folks
[16:13] <directhex> hm? who does?
[16:13] <asac> the website
[16:14] <asac> it should just display the embed/object thing
[16:14] <asac> and dont use a detection kit
[16:14] <directhex> ah. detection kitting is part of upstream Silverlight.js
[16:14] <asac> which is stupid
[16:14] <asac> ;)
[16:14] <directhex> i.e. blame microsoft for lack of plugin finder in msie for breaking it for everyone else ;)
[16:14] <asac> anyway. whats the package called then?
[16:14] <directhex> moonlight-plugin-mozilla, source package moon
[16:15] <asac> directhex: ok. installling. did you add our plugin meta data to control? (i think remember that you did that)
[16:15] <directhex> asac, yes, i don't know how correct it is of course :)
[16:17] <asac> yeah. we need the anti-plugin-detection-kit ;)
[16:19] <directhex> i'm testing in a 32-bit vm to see if it's 64-bit-related
[16:19] <asac> good idea
[16:19] <directhex> it is indeed a 64-bit problem
[16:20] <asac> good. so its upstream!!!
[16:21] <directhex> or a regression someplace else ;)
[16:31] <directhex> hm, possible fix from upstream. etsting...
[21:00] <jdhore1> Is there a estimated ETA for Firefox 3.0.9 hitting Hardy's repos?
[21:42] <directhex> asac, in case you were curious, upstream bug located & just dpatched. i'll SRU it for jaunty
[22:41] <asac> directhex: showing patch would entertain me ;)
[22:41] <asac> jdhore1: we release 24h after mozilla for various reasons
[22:41] <asac> so any minute
[22:41] <directhex> asac, http://svn.debian.org/viewsvn/pkg-mono/moon/trunk/debian/patches/moon_fix_gdk_pointer_size.dpatch?revision=3966&view=markup
[22:42] <asac> heh
[22:42] <asac> so undefined prototype somewhere?
[22:48] <directhex> something like that. gtk-2.0/gtk/gdktypes.h defines GdkNativeWindow as either gpointer or guint32 depending on whether GDK_NATIVE_WINDOW_POINTER is defined
[22:49] <directhex> GDK_NATIVE_WINDOW_POINTER is defined in moonlight.h depending on whether GLIB_SIZEOF_VOID_P is 8 (as it is on 64-bit platforms)
[22:50] <directhex> and GLIB_SIZEOF_VOID_P comes from glib.h
[22:50] <directhex> so... include glib.h then moonlight.h, and sizeof(GdkNativeWindow) is 8, otherwise it's 4
[22:51] <directhex> a fixed plugin will be landing in incoming.debian.org within minutes
[23:15] <asac> directhex: will you do a SRU for jaunty?
[23:15] <directhex> asac, need to do the paperwork, but yes, it's very much my intention
[23:37] <directhex> [ ]	moon_1.0.1-3.dsc	22-Apr-2009 22:32 	1.5K
[23:37] <BUGabundo> asac: hi
[23:37] <BUGabundo> asac: how to rebuild fontconfig cache?
[23:38] <asac> BUGabundo: fc-cache --system-only
[23:38] <asac> at least i think
[23:39] <asac> usually you dont need to do that, right?
[23:40] <BUGabundo> yeah
[23:40] <BUGabundo> but a user seems to have a corrupted cache
[23:40] <BUGabundo> http://img513.imageshack.us/img513/8053/capturaecra6.png
[23:41] <directhex> asac, assuming for a second that a silverlight site isn't using browser detection (it's true, some don't), would the moon package be picked up by ubufox as-is? or is extra work needed for the metadata i added to debian/control to be seen?
[23:41] <asac> directhex: havent checked.
[23:41] <asac> i would suggest to do a test site
[23:42] <asac> directhex: but form looking at control it looks right
[23:43] <directhex> asac, how does ubufox do the searches, i.e. where is the data it searches?
[23:44] <asac> directhex: what is a typical moonlight extension?
[23:44] <asac> file extension i mean
[23:44] <asac> .moon?
[23:44] <asac> err sl ;)
[23:45] <directhex> asac, erm..... for SL1? .js
[23:46] <asac> directhex: http://people.ubuntu.com/~asac/pfs/test/3_triplecontent.html
[23:46] <asac> directhex: unfortunately i have no file so you have to click on the tools -> manage content plugins
[23:46] <asac> and have to select search
[23:47] <asac> for silverlight mimetype
[23:47] <asac> thats what you would get if there would be real content with file
[23:48] <asac> description seems to be quite long
[23:49] <directhex> asac, patches welcome
[23:49] <asac> heh
[23:49] <directhex> asac, if it helps, i'll look at some dummy SL content for your page
[23:50] <asac> directhex: you sure you can use silverlight in the description?
[23:51] <asac> e.g. trademark
[23:51] <directhex> ehm... i'll look into that
[23:52] <asac> Xb-Npp-Description: The GNU SWF Player (http://www.gnu.org/software/gnash/)
[23:53] <asac> anyway. i think its ok except maybe the silverlight name
[23:53] <asac> ubufox should line break at some point
[23:56] <directhex> <object type="application/x-silverlight"
[23:56] <directhex> 	data="data:application/x-silverlight,"
[23:56] <directhex>        width="240"
[23:56] <directhex>        height="197"></object>
[23:56] <directhex> works for me. give it a punt
[23:57] <directhex> i extracted the actions taken by Silverlight.js when it inserts the <object> into the DOM
[23:57] <directhex> that cut-down version seems valid


[23:15] <xnox> wgrant, may i have something like http://qa.ubuntuwire.com/ftbfs/s390x.html but with xenial-release pocket only (no proposed) cause i really need to see what's left to be built in -release pocket, ignoring the piles of broken things in proposed =)
[23:16] <wgrant> xnox: That's not really possible.
[23:16] <xnox> wgrant, ok. fair enough.
[23:16] <wgrant> xnox: Not all builds exist for release.
[23:16] <wgrant> So you'd have to correlate builds in both pockets against sources published in release.
[23:16] <xnox> .... right.
[23:17] <wgrant> I might see how much work it is.
[23:23] <xnox> wgrant, whilst incomplete, I think s390x.getBuildRecords(build_state='Failed to build', pocket='Release') is a good start for me.
[23:24] <xnox> or not. there are more of those than in ftbfs report.
[23:27] <wgrant> xnox: That's very incomplete.
[23:28] <wgrant> Anything that's been uploaded since we created s390x will have the build in -proposed instead.
[23:29] <xnox> right, failed in -proposed, and migrated with the proposed build-record, cause it was not a regression.
[23:30] <xnox> i could do html parsing surgery with sed on s390x.html page ;-) and just remove full rows that mention proposed, without mentioning release line.
[23:30] <xnox> maybe tomorrow
[23:30] <xnox> good night


[17:04] <IdleOne> http://loco.ubuntu.com/events/ubuntu-ca/2585/detail More release parties in Ontario.
[17:07] <IdleOne> Job offer: http://www.koumbit.org/en/articles/job-offer-web-developer
[18:49] <cyphermox> IdleOne: so you organizing our release party?
[18:49] <cyphermox> :)
[18:49] <IdleOne> nope
[18:50] <cyphermox> boo


[14:20] <Bill_> Help
[14:21] <Bill_> Trying to update Ubuntu and its telling me your Ubuntu release is not supported anymore
[14:24] <elacheche> Bill_: You're looking in the wrong channel.. Try to ask in #ubuntu here is the support of issues arround loco teams