[10:05] <marcel-admiraal> Hi. Can someone tell me if there is anything else I need to do to Bug #1010370 to complete it?
[10:05] <ubot2> Launchpad bug 1010370 in linux "BUG: unable to handle kernel paging request at ffff88025cd79068; RIP: 0010:[<ffffffff811631fe>] [<ffffffff811631fe>] kmem_cache_alloc_trace+0x5e/0x140" [Medium,Incomplete] https://launchpad.net/bugs/1010370
[10:09] <brendand> marcel-admiraal, i would say run the upstream for a few weeks and if it can't be reproduced you can assume the bug is gone
[10:13] <marcel-admiraal> How do we know that the problem is not in some change introduced between the upstream kernel and the kernel released by Ubuntu? In other words it's been fixed upstream or whether it never existed upstream?
[10:18] <marcel-admiraal> Sorry, I provided the wrong bug number: How do I get Bug #1013066 confirmed?
[10:19] <ubot2> Launchpad bug 1013066 in linux "WARNING: at /build/buildd/linux-3.2.0/fs/proc/generic.c:586 proc_register+0xbf/0x170()" [Medium,Incomplete] https://launchpad.net/bugs/1013066
[14:15] <ogra_> hggdh, hmm, so you had the impressin that you can install to a local partition on SD on a panda ? i wonder if we should just remove that text in the partitioner ... i dont think that ever worked
[14:24] <hjd> Question about when to use the tag "patch": I guess this is mainly to tag bugs which have an attachment, but I assume diffs in comments would be ok (bug 811849). What about a link to a patch (bug 690625), or a comment on the changes, ie. not a diff (bug 709901)?
[14:24] <ubot2> Launchpad bug 811849 in ripit "ripit 3.8.0 bug and patch" [Undecided,New] https://launchpad.net/bugs/811849
[14:24] <ubot2> Launchpad bug 690625 in driconf "driconf: DeprecationWarning with python 2.6" [Undecided,New] https://launchpad.net/bugs/690625
[14:25] <ubot2> Launchpad bug 709901 in lirc ""PATCH" to enable lirc over network" [Undecided,New] https://launchpad.net/bugs/709901
[14:31] <hggdh> ogra_: well, it did sort of work before
[14:31] <ogra_> i have never seen that working
[14:32] <ogra_> every time i tried that in the past to an SD card
[14:32] <ogra_> (we used to have live images in the very beginning of ubuntu-arm, it didnt work back then)
[14:32] <hggdh> this was the first time I had seen this message. Granted, it might have been there forever, but the install was never interrupted before
[14:33] <ogra_> well, it is there since we switched from preinstalled to live
[14:33] <hggdh> ah
[14:33] <ogra_> preinstalled doesnt show the partitioner at all
[14:33] <ogra_> so you wouldnt see it
[14:33] <hggdh> this is it, this is the first time I ran the live
[14:33] <ogra_> right
[14:33] <ogra_> i'm just wondering what we shoudl do
[14:34] <hggdh> this really makes it a bit more complex on the pandas
[14:34] <ogra_> well, we should just suppress that option
[14:34] <hggdh> we could try to set it to install to a different memory stick/usb device
[14:34] <ogra_> and only allow installs to USB
[14:34] <ogra_> thats what it does by default
[14:34] <ogra_> (if you have a USB key plugged in)
[14:35] <hggdh> on the live, right? Cuz on the preinstalled I never got it to really work
[14:35] <hggdh> and so I did not have a memstick plugged in
[14:35] <ogra_> preinstalled doesnt do anything with partitions
[14:35] <hggdh> humpf
[14:35] <ogra_> it just expands itself to the media it started from
[14:35] <hggdh> I will try again with the memstick plugged in
[14:35] <ogra_> great
[14:36] <hggdh> and this may well be the reason for the error 141
[14:36] <ogra_> that indeed doesnt solve the bug ... but i'll wait for cjwatson to discuss what we'll do with the issue
[14:36] <ogra_> the live install already takes 1h ...
[14:36] <hggdh> but an update on the wiki would be nice, ogra_
[14:36] <ogra_> if your target device is actually the same SD you run from that will become even longer
[14:37] <hggdh> ugh
[14:37] <ogra_> hggdh, yes, on my TODO as soon as i know the images work at all
[14:37] <hggdh> ack
[14:37] <ogra_> the arent in a condition that i want to actually have the masses test them
[15:54] <rbasak> Please could someone accept my nomination for Precise SRU in bug 850960?
[15:54] <ubot2> Launchpad bug 850960 in open-iscsi "iscsid tries to reconnect existing session at startup, failing to do so and hanging the system" [Undecided,Fix released] https://launchpad.net/bugs/850960
[16:09] <micahg> rbasak: done, looks simple enough
[16:09] <rbasak> micahg: thanks!
[16:49] <LoT> who do i need to poke to get a bug targetted against a specific release?
[16:49] <LoT> and should we invalid bugs against maverick?
[16:52] <bcurtiswx> LoT, maverick has reached EOL, so yes please invalidate them. Make sure to let tem know they can reopen if the experience the same bug in any future Ubuntu release
[16:53] <micahg> LoT: bug control can nominate, uploaders/drivers can approve
[16:57] <LoT> micahg: how often do drivers check?
[16:58] <LoT> i have stuff i've nominated against precise from three weeks ago and its not been checked.
[16:58] <micahg> LoT: not often, if you want something that you're working on, it's generally a good idea to just ask for it
[17:01] <LoT> micahg: as i've learned from working on security bugs in -hardened xD
[17:06] <LoT> Received: from enctcapp221.PA.LCL (172.19.222.35) by ENHBGHTS02.PA.LCL
[17:06] <LoT>  (206.224.21.43) with Microsoft SMTP Server (TLS) id 8.3.264.0; Tue, 17 Jul
[17:06] <LoT>  2012 12:50:48 -0400
[17:06] <LoT> Received: from psmtp.com (64.18.2.42) by mail01.state.pa.us (172.19.223.35)
[17:06] <LoT>  with Microsoft SMTP Server id 8.3.264.0; Tue, 17 Jul 2012 12:50:47 -0400
[17:06] <LoT> Received: from mail.s86.ru ([217.8.80.233]) by exprod7mx202.postini.com ([64.18.6.10]) with SMTP;	Tue, 17 Jul 2012 09:50:46 PDT
[17:06] <LoT> Received: by mail.s86.ru (Postfix, from userid 106)	id D0D46516B93; Tue, 17 Jul 2012 22:40:56 +0600 (YEKST)
[17:06] <LoT> X-Spam-Checker-Version: SpamAssassin 3.3.0 (2010-01-18) on mail.s86.ru
[17:06] <LoT> X-Spam-Level: *
[17:06] <LoT> X-Spam-Status: No, score=1.7 required=10.0 tests=ALL_TRUSTED,BAYES_50,
[17:06] <LoT> 	MISSING_DATE,MISSING_MID autolearn=no version=3.3.0
[17:06] <LoT> Received: from localhost (IGLD-84-229-233-117.inter.net.il [84.229.233.117])
[17:06] <LoT> 	by mail.s86.ru (Postfix) with ESMTPA id 4FA2B515F08	for
[17:06] <LoT>  <en-copaensnotifications@state.pa.us>; Tue, 17 Jul 2012 22:40:50 +0600
[17:06] <LoT>  (YEKST)
[17:06] <LoT> From: <redut@surguttel.ru>
[17:06] <LoT> To: <en-copaensnotifications@state.pa.us>
[17:06] <LoT> Subject: Part-time Operations Specialist Needed
[17:07] <LoT> bleh
[17:07] <LoT> i hate putty
[17:07] <LoT> but alas i dont have an alternative here
[17:07]  * penguin42 takes away LoT's paste key
[17:08] <LoT> thanks, but its a bug when i use alt-tab to get back to putty
[17:08] <LoT> i've already sent the bug to devs :P
[17:08] <LoT> and its only in windows
[17:08]  * LoT is stuck on windows
[17:08] <LoT> I CAN STILL TRIAGE BUGS!
[17:08] <penguin42> hmm
[17:09] <LoT> well, apparently, the guy who develops stackapplet wants me to notify him of bugs in that package o.O  seriously, how many people want me to help them track/triage ubuntu bugs for their packages...
[17:09] <LoT> bodhizazen wants me to track display-dhammapada too :/
[17:09] <penguin42> have they got their own bug trackers?
[17:09] <LoT> stackapplet has theirs on LP
[17:09] <LoT> display-dhammapada is...
[17:09] <LoT> um...
[17:09] <LoT> sort of on LP
[17:10] <LoT> (pending the updated package by bodhizazen being accepted in Debian)
[17:10] <LoT> problem is when its filed against $package (ubuntu)
[17:10] <LoT> then its bugcontrol/bugsquad territory :/
[17:10] <LoT> bleh
[17:11] <penguin42> LoT: Yeh that's OK, then just add it as an also-affecting...
[17:11] <LoT> you know what, i'm going to send emails about such requests to $junk automatically
[17:11] <LoT> since i already ahve 8 different packages i actively track
[17:11]  * LoT does not need a 9th
[17:12] <LoT> there, now my clipboard has "$null", so if i paste by this bug, it'll only say $null
[17:12] <LoT> :p
[17:14] <LoT> remind me to burn putty, by the way, when i'm back at home
[17:14]  * LoT is going to blacklist it in his systems
[18:18] <littlegirl> Hey there, LoT, are you at keys?
[18:20] <LoT> littlegirl: hm?
[18:20] <LoT> little bit busy with itsec stuff, but whats up
[18:20] <littlegirl> I'm finished and I wanted to show you the SRU before attaching it to make sure I did it right, but if you're busy it can wait. (:
[18:21] <LoT> littlegirl: i'm not that busy, just adding spam strings to an email filter
[18:21] <LoT> pastebin what you've got i'll take a look if you want
[18:21] <littlegirl> Oh, that's not nearly as exciting as my ever-growing bug. (:
[18:21] <littlegirl> http://paste.kde.org/519356/
[18:21] <LoT> littlegirl: nor is it as exciting as dealing with cascade server failure
[18:21] <littlegirl> I've got diffs of all the changes, and I'll be attaching those as well. (:
[18:21] <LoT> except i do not want that to happen again
[18:21]  * littlegirl nods at LoT
[18:21] <littlegirl> LOL
[18:22] <LoT> CASCADE SERVER FAILURE WILL BE MET WITH THE ALMIGHTY FORCE OF THE ITSEC EQUIVALENT OF THE BFG: THE EMP

[18:22] <littlegirl> If it makes you feel any better, when I was halfway through making all these changes and hadn't saved a text file I was keeping track of everything in yesterday, my cat sat on the power supply and managed to turn off the power to my computer yesterday. (:
[18:23] <LoT> littlegirl: think of the regression potential section as this:
[18:24] <LoT> the potential for this:
[18:24] <LoT> A regression is a bug introduced after an update. These kind of bugs are especially important because if something breaks that used to work it interferes with the workflows of software users. These can be more obvious and painful for users than bugs.
[18:24] <LoT> littlegirl: with a documentation-only change, i dont think there is a regression potential
[18:25] <littlegirl> Ooooh, that's not what this is. This was errors that were there all along, and managed to be in two releases and found their way partly into the development version.
[18:25] <hggdh> unless, of course, the new doc is rather wrong ;-)
[18:25] <LoT> the other info section about "This other thing should be a bug" might not be necessary either
[18:25] <LoT> hggdh: +1
[18:25] <LoT> littlegirl: no what i mean is
[18:25] <LoT> consider the "regression potential" as the potential for a bug to be caused by this update
[18:25] <LoT> if there is such a regression...
[18:25] <LoT> such as, say...
[18:25] <littlegirl> LoT: So should I just leave that part out? The https://wiki.ubuntu.com/StableReleaseUpdates#Procedure page gave me the impression that without it, this doesn't qualify, and maybe I shouldn't have done all those commits. (:
[18:26] <LoT> in php5.4, they changed the default phpfpm to use sockets instead of TCP
[18:26] <LoT> that may break other php packaged applications and configs by default
[18:26] <littlegirl> Ah, no such chance. I am perfect, and since I made the changes, nothing bad can happen.
[18:26] <LoT> that's a regression potential
[18:26]  * littlegirl waits for the sky to fall
[18:26] <LoT> but since that was requested in ubuntu and debian, they accepted that patch
[18:26]  * LoT wrote the patch
[18:26]  * littlegirl didn't use the patch
[18:27] <LoT> i meant for php5 :P
[18:27] <littlegirl> Well, I kind of did, but I did a lot more, too. (:
[18:27] <LoT> hggdh might be able to tell you if its good SRU stuff too
[18:27]  * LoT has to put these spam strings in otherwise the business will be spammed to death
[18:27] <littlegirl> Ah, okay. (:
[18:27] <littlegirl> Should I change anything in that? And do I attach it, or is that what I use as the comment in the bug report?
[18:28]  * littlegirl is sorry to be such a pest, but she is still learning. (:
[18:28] <LoT> :P
[18:28] <LoT> the sru stuff is added as a comment
[18:28] <LoT> and then we subscribe the sru team to review
[18:28] <LoT> but i'd recommend letting hggdh read over the stuff too
[18:28]  * LoT is but one person :P
[18:28] <littlegirl> Okay. (:
[18:28] <LoT> and is sometimes prone to mistakes :P
[18:29] <littlegirl> Hey there, hggdh, how would you like some fun and exciting reading? (:
[18:29] <hggdh> littlegirl: on it already :-)
[18:29]  * littlegirl is never prone to mistakes. Not once. Never. Honest. (:
[18:29] <hggdh> neither am I. Mistakes are usually introduced by an external entity, called the Murphy Ghost
[18:30] <littlegirl> Exactly! And they're either Not My Fault or Somebody Else's Problem. (:
[18:30]  * LoT installs "I Will Fail" mods onto littlegirl
[18:30] <LoT> okay, enough with my randomness :P
[18:31]  * littlegirl fails
[18:31] <LoT> *sigh*
[18:31] <LoT> seriously, the end of the work day doesnt come fast enough
[18:31] <littlegirl> Do you work at Canonical?
[18:31] <LoT> nope, i dont
[18:31]  * littlegirl would love to work at Canonical
[18:31]  * LoT cannot reveal who he is working for
[18:31] <LoT> uber-secret-stuff
[18:32]  * littlegirl uses a divining rod
[18:32] <littlegirl> I assumed all the developers worked for Canonical. (:
[18:32]  * LoT uses national security as a reason to take the divining rod
[18:32]  * littlegirl asks for a receipt
[18:32] <LoT> littlegirl: i'm not a developer.  :P
[18:33] <LoT> i'm a volunteer triager/bugcontroller
[18:33] <LoT> actually the part about bugcontrol's not true
[18:33] <littlegirl> Ah, same here. (:
[18:33] <LoT> i do that actively for the nginx package
[18:33] <LoT> as i'm part of their triaging team
[18:33] <littlegirl> But not all those things. I just play with documentation. (:
[18:33] <LoT> :p
[18:33] <hggdh> littlegirl: usually, documentation is not considered for SRU, unless it can drive an user to error
[18:34]  * littlegirl Googles nginx
[18:34] <LoT> !info ngixn
[18:34] <LoT> oops
[18:34] <LoT> forgot no bot here
[18:34] <hggdh> littlegirl: OTOH, we are talking about 12.04 LTS, which will be with us for 5 years
[18:34] <LoT> < ubottu> nginx (source: nginx): small, but very powerful and efficient web server and mail proxy.
[18:34] <LoT> hggdh: define:OTOH
[18:34] <littlegirl> hggdh: Yeah, I ran into that a couple of times yesterday. What happened is someone in the translation team made a wish for me to close out that bug, so I started on it and found other things that needed to happen (like fixing the validate.sh script and replacing the missing files, and it just snowballed. (:
[18:35] <hggdh> LoT: On The Other Hand
[18:35] <LoT> ah
[18:35] <LoT> :P
[18:35] <LoT> that's a new acronym i've never seen used :p
[18:35] <littlegirl> hggdh: True, for the Precise part. Although I suppose the Oneiric part of that bug probably would have qualified as Invalid.
[18:35] <littlegirl> Interesting about the server. (:
[18:36] <hggdh> littlegirl: yes, I would expect no SRU on that for Oneiric. Looks good, except for the 'regression potential' piece -- this is where you would describe the dangers
[18:36] <littlegirl> hggdh: I'm currently whipping the Quantal kubuntu-docs into shape, and will probably go back to the Precise ones and do the same to them once I'm finished, but each needs different stuff, so this will take a little while. (:
[18:37] <littlegirl> hggdh: What, exactly, should I say in the regression potential part?
[18:37] <hggdh> littlegirl: ah. In this case, please keep in mind that a SRU will only be considered after fixing the development version (Quantal as of now)
[18:38] <littlegirl> hggdh: All the fixes have been done on Oneiric, Precise, and Quantal. That bug is not present in any of the three. (:
[18:38]  * littlegirl wipes sweat off her brow
[18:38]  * LoT increases the temperature of the room by 15 degrees fahrenheit
[18:39] <littlegirl> I had *no* idea how large this bug was when I began. I thought I could do it in five minutes, and it turned into an all day saga. (:
[18:39] <hggdh> littlegirl: I am now confused: if the bug is not in Oneiric, Precise, and Quantal, what are you trying to fix?
[18:39]  * littlegirl grabs an ice pack
[18:39] <littlegirl> hggdh: It was until I committed all those fixes. (:
[18:39] <LoT> hggdh: the bug is in there, i think, the fixes have been commited to the code branches, afaict
[18:39] <littlegirl> hggdh: What I'm saying is that I've done the fix to everything, so the bug won't be carried forward.
[18:39] <hggdh> commiting the fixes does not resolve the bug. Having replacement packages does it
[18:40] <LoT> ^ this
[18:40] <littlegirl> Ah! I didn't know that. That's over my head. Who do we hand that to? (:
[18:40] <hggdh> so the bug still lives in Oneiric and Precise at least
[18:40] <LoT> littlegirl: someone who can build the package and create debdiffs for Quantal
[18:40] <LoT> but quantal's under pre-release freeze isnt it?
[18:40] <LoT> (i forget what freeze is what though)
[18:40] <littlegirl> Not that I know of. How do we find out?
[18:40] <hggdh> first of all the fixes for Quantal must be proposed, accepted, packages built & released
[18:41] <LoT> mhm
[18:41] <littlegirl> hggdh: Ah, that's not a problem. I'm fixing all the Quantal docs and those will be properly translated, built, etc., etc. by whoever does all that. It's just that I made sure those errors were removed from the Quantal docs as part of this bug fix.
[18:42] <LoT> once that's built and included it should be SRU'd
[18:42] <LoT> not before
[18:42] <littlegirl> I think Darkwing or Riddell or Jjesse handles the building and packaging of the docs for Quantal.
[18:42] <LoT> the changes have to exist in Quantal if applicable (and it does apply)
[18:42] <LoT> i just poked him via privmsg, he didnt respond yet
[18:42] <littlegirl> Ah, okay. Darn. What about the fact that I've already committed all those changes?
[18:43] <littlegirl> I'm totally new, and all I do is grammatical, punctuation, layout, and accuracy changes to the docs. (:
[18:43] <LoT> still needs to be built and included in Quantal
[18:43] <littlegirl> Yep!
[18:44] <hggdh> littlegirl: you committed the changes where?
[18:44] <littlegirl> To Launchpad. I made the changes to all the files that are listed in that paste that you were reading.
[18:44] <hggdh> under the applicable bzr branches for all source involved, right?
[18:44] <LoT> hggdh: committed to the bzr branch
[18:45] <littlegirl> Lines 84, 85, 88, 89, 92, and 93 contain links to the committed changes.
[18:45] <littlegirl> hggdh: Yep!
[18:45] <littlegirl> Each branch needed individual changes. Not all of them had the same issues.
[18:46] <littlegirl> But I did see that many of the issues in the bug were present in all three, so without these changes, they might have continued to invade the Kubuntu system documentation. (:
[18:49] <hggdh> littlegirl: cool. Then I strongly suggest you to follow up with darkwing, Riddell, or jjesse -- since they would most probably be the ones to accept the SRU anyways
[18:50] <littlegirl> hggdh: Okay, thanks, I guess I'll go in there and see if any of them are on and want to tackle it. (:
[18:52] <hjd> Do we have something akin to "How to file a sync request" for merges? Bug 995234 requests a newer version, Debian has 5.1 while Ubuntu has 4 with some ubuntu-specific changes so someone should take a look at whether it needs to be merged or whether it can be simply synced.
[18:52] <ubot2> Launchpad bug 995234 in collectd "When will collected version 5 be packaged up? " [Undecided,Confirmed] https://launchpad.net/bugs/995234
[18:54] <hjd> I'm mainly trying to find some instructions to link to. I could link to the ones for sync I guess, but I don't know whether that would be sufficient or if the Ubuntu-specific changes need to be merged in still.
[19:00] <littlegirl> Lot and hggdh: Is this a better regression statement? Regression should not be an issue with these fixes because they didn't reference versions of software or paths to files that might change at a later date.
[19:07] <hggdh> sounds good
[19:08] <littlegirl> Thanks for all your help. (:
[20:23] <hggdh> ogra_: still there? a Q on armadaxp
[23:59] <penguin42> heck, libwebkitgtk-1.0.0-dbgsym is 466MB!