=== itnet7_ is now known as itnet7 === s9iper1_ is now known as s9iper1 [18:43] Hi, I want to nominate a patch for LTS review/test/update. The bug is https://bugs.launchpad.net/ubuntu/+source/virtualbox/+bug/1081307 [18:43] Launchpad bug 1081307 in virtualbox "virtualbox-dkms 4.1.12-dfsg-2ubuntu0.2: virtualbox kernel module failed to build [merge request]" [Undecided,Confirmed] [18:45] I updated the summary of the bug according to SRY [18:45] SRU* [19:00] !help [19:00] Please don't ask to ask a question, simply ask the question (all on ONE line and in the channel, so that others can read and follow it easily). If anyone knows the answer they will most likely reply. :-) See also !patience [19:00] !patience [19:00] Don't feel ignored and repeat your question quickly; if nobody knows your answer, nobody will answer you. While you wait, try searching https://help.ubuntu.com or http://ubuntuforums.org or http://askubuntu.com/ [19:01] *looks* [19:03] pranith, i can't do anything about it right now, but all I see is an attached patch to that bug. [19:04] not a code merge request, nor a debdiff. [19:04] unless I'm mistaken, its not SRU-ready [19:04] but i'm not on the SRU team [19:04] TheLordOfTime, How do I make a code merge request? A fixed package exists in ppa [19:04] that's not enough [19:04] pranith, the patch in the bug, that's what you used to fix it in the PPA right? [19:05] yes [19:05] * TheLordOfTime checks the patch [19:05] and forgive slow responsiveness, my internet's lagging todya ;P [19:06] yeah, you're missing DEP3 tagging on the patches too. [19:06] s/patches/patch. [19:06] TheLordOfTime, how do I generate a proper patch? [19:06] and how do I make it SRU-ready? [19:06] well the patch is right it just needs DEP3 headers. [19:07] pranith, you should probably talk to the SRU team not the bugsquad on this, the bug's already marked as needing fixed in quantal and precise, so there's not much more bugsquad can do [19:07] ah, how do I talk to the SRU team? :) [19:07] short of me creating and uploading a debdiff for that bug of course [19:08] which, while I"m more than happy to do, means you're waiting for 8 more hours [19:08] because I"m busyish with a client's campaign site today :P [19:08] I can try to generate the debdiff.... could you point me to any docs or how tos? [19:09] not while i'm on-site at a client's, i can't. [19:09] * TheLordOfTime pings bdmurray [19:09] ok [19:09] unless someone else from the SRU team is around :P === rsalveti_ is now known as rsalveti === Ursinha_ is now known as Ursinha [19:12] I'm busy with UDS at the moment but can look at it later today [19:12] bdmurray, they need guidance on how to fix i think [19:12] bdmurray, ther'es no merge request nor debdiff [19:12] and one of those is needed for SRUs, unless the SRU process changed and I missed a memo [19:13] pranith, just wait around, and bdmurray can help [19:13] * TheLordOfTime has to run right now [19:15] (also their patch is missing DEP3) [19:15] * TheLordOfTime seriously runs off now. [19:25] or not. [19:25] pranith, um, correct me if i'm wrong, please, but this bug is replicateable only under the Quantal kernel on Precise? [19:26] if i'm not mistaken, that's not a normal practice... [19:28] pranith, the test-case suggests changes that I don't normally see on every Precise system by a normal user. the test case suggests that you specifically can cause this to be replicated under the 3.5.x kernels on Precise. Precise has 3.2.x normally. [19:30] pranith, did you test whether including this patch will prevent it from working on 3.2.x kernels? [19:30] i.e. will it still run and operate normally. [19:35] pranith, also, I get a Fail to Build Source Package when I try and build the Precise version with that patch. [19:35] can't even create a source debian package, unless something on my end's broken, [19:38] TheLordOfTime, this is replicable in precise [19:38] but only under the 3.5.x kernel [19:38] ? [19:38] yes [19:38] then you didn't answer my question. [19:39] <TheLordOfTime> pranith, did you test whether including this patch will prevent it from working on 3.2.x kernels? [19:39] i.e. the kernels that ship WITH precise [19:39] and not the custom kernel., [19:39] I am using the patched package on both 3.2 and 3.5 kernels [19:39] without incident? [19:39] I do not see any issue [19:40] did you try to build the package from precise-updates after including the patch? [19:40] I'm running into issues when trying to build the source package, on a stock Precise system :P [19:41] TheLordOfTime, can you specify what the issue in compiling is? [19:42] i didn't say compiling [19:42] i misspoke [19:42] i meant creating the source package [19:42] so that I can upload it to my own build-tests PPA [19:43] ... eww... [19:43] i blame the fact that the dh clean line inclues "python_central"... [19:43] suggests something's missing. [19:44] TheLordOfTime, I am not sure of what the issue might be [19:44] i'm testing something [19:44] LOL now its breaking on dkms [19:44] * TheLordOfTime jumps to -packaging [20:34] Any raring python 2.x maintainers on? There was recently a fixed regression, but I want to confirm if I have found one myself. [20:36] whats the issue? [20:41] Maccer, ^ [20:45] jtaylor, TheLordOfTime: I have mintmenu on my system, which is a .py XFCE/GNOME2 applet. Since upgrading from 12.10 (quantal?) to raring, the script has stopped launching this gtk event that spawns the application you selected. The script itself has not changed in quite a while and received no update from raring, and is not frequently maintained anyways. [20:46] But I really suck at python, so it's hard for me to trace the error. But it's either the fact that applications won't launch because a gtk event is not called, or a process just won't launch. [20:46] probably more a (py)gtk issue than python [20:46] can you show the code? [20:48] jtaylor: https://github.com/linuxmint/mintmenu/tree/master/usr/lib/linuxmint/mintMenu << It's actually a pretty simple launcher. The applications plugin should be in plugins/applications.py [20:50] So far from the developers of mintmenu, this has not been tested on raring yet and that they're working on a different component and cannot test right now. [20:53] gtk is not really my field of expertise [20:54] is there a reasonably easy way to run it without installing mint? [20:55] if the devs are aware of it probably best to let them fix it [20:56] gtk2 is not really supported anymore ubuntu [20:56] jtaylor: It's okay, I'm going to talk to a few people. But you don't need to install mint, you just need to add their repository and install mintMenu plus a mint applet emulator on either KDE, XFCE, or GNOME. [20:57] Thanks though. :> [20:57] i think i'm going to agree with jtaylor on this part... [20:57] gtk2's not really supported much anymore [20:57] they replaced it with gtk3, right jtaylor? [20:57] a few libraries may still be in the archive [20:58] as we still have some unported apps [20:58] I don't know much about it [21:02] GTK2 is still widely used in XFCE and a few other working but unmaintained applications. I'd be surprised if they pulled GTK2 out of the repositories in raring, unless you mean they will just stop submitting patches? [21:03] by unsupported i think we mean not updated as much [21:03] Although XFCE is getting a GTK3 port over time. Speaking of GTK3, is the performance now comparable to GTK2? I haven't been in the GTK3 sphere very much. [21:03] Ah, okay. Because in Ubuntu 12 I believe GTK1 was pulled. [21:03] Or is it 11... [21:05] gtk 1 was dropped before lucid [21:05] hardy still has it [21:06] jtaylor, what's hardy's EOL again? [21:06] While not a problem, I needed to manually download the GTK1 debs just for this pesky PS1 emulator. [21:06] I think april [21:06] not long anymore at least [21:07] jtaylor, i'm surely hoping so, since I can Won't Fix a (self-adopted) bugs in the ZNC package the moment that Hardy EOLs. [21:07] s/bugs/bug/ [21:08] Is hardy basically what Debian 5.x stable was? [21:08] I'm poorly familiar with the release cycles of Ubuntu. [21:08] hardy was 8.04 [21:08] released april 2008 i think. [21:08] but i may be wrong [21:09] i only know the release cycle by heart from jaunty onwards [21:09] Oh, seems like people only use hardy for servers. Why? I'd use Squeeze instead. I understanding migration pains though. [21:09] hardy was my first version of ubuntu :) [21:09] i use Precise on my servers [21:09] s/Precise/LTSes only/ [21:10] hardy has 5 years support, squeeze only has 3 and came 2 years later [21:10] but this is not the right channel for this discussion [21:10] indeed. [21:10] that's true.