[00:00] tseliot: is there a download of it anywhere ? [00:00] tacone: I haven't released it yet. It parses the man page of xorg and generates an xml file [00:00] tacone: no, not yet but I hope to release it soon [00:01] tseliot: does it perform the reverse conversion as well ? [00:01] tacone: no, it doesn't [00:01] tseliot: if it's just one file, you could just pastebin it somewhere [00:02] tacone: I have to find it first [00:03] tseliot: if it's too much effort nevermind, I'll wait. [00:04] tacone: my computer is a mess and it's a bit late now. I promise to find it and upload it ASAP [00:05] tseliot: np, it was just out of curiosity. I'll wait :) === Kopfgeldjaeger is now known as Kopfi|offline === superm1 is now known as superm1|away [00:49] nxvl: remember to remove update debian maintainer bla bla bla in changelog [00:51] emgent: where? [00:52] emgent: if you are refering to terminator, it's change it was made in this revision, shouldn't it go there? [00:53] nxvl: not if i remember ubuntu-devel policy, but dont worry :) [00:53] emgent: mmm, then update-maintainer should be changed [00:53] (as in script) [01:05] it was changed [01:06] though possibly reverted; I haven't followed too closely [01:33] 'night everyone [01:55] thanks RainCT [02:00] RainCT: RE clamav: Just unsub UUS and wait for Debian to apply it. [02:02] ScottK: do you have any time to help clamav in Debian? [02:02] was it in fact you that offered? [02:02] james_w: There's a new pkg_clamav team. I'm on it. [02:02] good to hear [02:03] I'd like it if some more Ubuntu people would join me there and we could maintain a common repo. === superm1|away is now known as superm1 [02:14] alo motu's [02:23] I'm looking to enhance ubuntu-vm-builder. what channel do you recommend I start discussions on? [02:25] I'd guess either #ubuntu-server, or #ubuntu-devel [02:26] ty. [02:27] I'm looking to add functionality to ubuntu-vm-builder so you can specify MAC addresses at build time. It's feature I had to make extra utils to implement in my workplace [02:27] It feels like an essential thing :) [02:34] Can anyone please spare a few minutes to please give me a REVU on this upload? http://revu.ubuntuwire.com/details.py?package=lucidlife much thanks! [03:46] hi guys [03:47] i think theres something wrong with REVU atm, if you try to view this package http://revu.ubuntuwire.com/details.py?package=google-gadgets it gives python errors, but if you go directly to an older upload ID of the same package (http://revu.ubuntuwire.com/details.py?upid=3475) it works fine... any ideas? [06:20] ScottK-laptop: around? [06:20] nxvl: It's late there (and moreso for you, no?) [06:21] yep [06:21] we have almost the same tz [06:21] but he use to be here until late [06:21] :P [06:21] meh not that late on the east coast [06:21] yeah i was gonna say i've seen him around 1 or 2 hours past now [06:22] It's already today there, which counts as late in my book. It should clearly be a day earlier. [06:22] haha [06:23] :P [06:23] persia: yeah, you live in the other side of the world [06:23] It's the sunny side :p [06:23] 14 hours difference [06:25] persia: it;s summer there, doesn't it? [06:26] nxvl: That's the unfortunate side effect of it being the sunny side. [06:26] heh [06:27] yeah, geeks don't like sun often [06:27] :P [06:28] I like the sun, it's just the heat that bothers me. If there was an environment where it was always sunny, yet never above about 30 C, I'd be very happy there. [06:28] persia: then come to peru [06:28] The new machine house in Dubai looks interesting: lots of piped sun, and systemic air conditioning. [06:29] nxvl: It's not always sunny there. Look up. [06:29] 30 C on summer (and that's really hot) and 22 on winter [06:29] persia: Piura is ALWAYS sunny and it's between 28 and 33 C all year [06:30] nxvl: It's sunny right now? [06:30] no, it's night right now [06:30] See. [06:30] :D [06:30] mm. freeze is coming === superm1 is now known as superm1|away [06:30] buw i've been there last week and it was sunny (at day) [06:30] stefanlsd: yep, one more day [06:31] it already smells like FF, things are going funnier and my head is about to blow up [06:31] :D [06:31] stefanlsd: [06:32] RAOF: hihi [06:32] stefanlsd: You should feel free to subscribe u-u-s whenever you think your package is done. If we never had to make comments, we'd just let everyone upload. [06:32] :) [06:33] making comments is fun [06:33] :D [06:33] RAOF: hehe. kk. will sub it again. and hopefully its ok this time. [06:33] stefanlsd: don't quit, just keep trying, that way you will learn more [06:33] I've been reading this http://mako.cc/writing/to_fork_or_not_to_fork.html. pretty interesting. makes me wanna get more involved with debian [06:34] Debian is not so fun as it seems [06:34] heya gang [06:34] good morning [06:34] Debian has the huge disadvantage that I can't upload packages to it :) [06:34] good $WhateverTimeIsInYourTimezon [06:34] :D [06:35] debian development is just a bunch of individual works [06:35] some of them collective, but just some of them [06:35] not an open community as ubuntu one [06:35] mm. should be much easier to get dd status there if youre already a MOTU here [06:35] Yeah. It would probably take 5 years instead of 10 :P [06:35] heh [06:36] stefanlsd: don't be so sure [06:36] stefanlsd: NM process involves more than just technical stuf [06:36] stuff* [06:38] in fact you need to be well versed with policies and licenses, philosophy etc [06:38] heh [06:38] maybe i'll just go to work [06:39] sigh [06:39] heh [06:40] cya guys later :) [06:40] hi [06:41] tuxmaniac: AND, the most important part, be a zealot :D [06:41] :p [06:41] good morning [06:41] dholbach: gutten tag [06:42] nxvl: Guten Morgen! [06:42] oh yeah! Morgen [06:42] :P [06:42] :-) [06:42] hi do you know much about the moon [06:42] i don't speak german since 2001 when i finished the school [06:42] :P [06:42] nxvl: ask me about my Spanish - although I never learned it anywhere :) [06:43] I'm pondering starting to learn it though [06:43] dholbach: heh, i wasn't able to speak anything but german at school [06:43] ugh... poor you :) [06:43] dholbach: then only courses i have in different languages was Spanish and English [06:44] even math, biologi and physics was in german [06:44] (inclusing sports) [06:44] including* [06:44] dholbach: yeah, germans grammar isn't easy for a non german speaker :P [06:45] I pity everyone starting to learn german - although I'm sure there are languages that are much worse :) [06:45] dholbach: chinesse to name one [06:45] no.. [06:45] is the grammar worse? [06:46] Chinese grammar is super simple [06:46] basically almost non-existing [06:46] you just need to get a hang of the different tones [06:46] yeah, but listening and pronoucing is hell [06:46] they just scream [06:46] naaaah [06:46] it's not that bad :) [06:47] what i found the hardest of german is to have, not only he and she, but it, and actually use it [06:47] not to mention all the irregular flexation of words [06:48] * nxvl still remember 1st grade der = blue, die = red, das = yellow [06:48] s/words/verbs [06:48] hey ScottK, you floating around? [06:48] meh, I failed every language class I ever took [06:48] gilligan__: and saying a completely and logical sentense in ONE word [06:48] :P [06:48] nxvl, eh? "der blue" ? [06:48] der in german is he [06:49] "der" is "the" :) [06:49] so they use colors so you know which object is what [06:49] well yeah [06:49] ah [06:49] but male "the" [06:49] and die is female "the" [06:50] and das is neutral "the" [06:50] dholbach: and you actually use the 3 of them [06:50] that's hell [06:51] so guys... how does https://wiki.ubuntu.com/UbuntuDeveloperWeek look? [06:51] * dholbach is fairly happy with the sessions offered [06:51] i want to give a talk :( [06:51] hey people, is there a way to get harvest list a specific set of softwre packages? [06:52] not the pkg=xxx,yyyy way. [06:52] tuxmaniac: but? [06:52] but depending on a category or team? [06:52] talking about harvest [06:52] who did the Ubuntu packaging videos? [06:52] dholbach: it would be usefull to have the header all the time [06:52] nxvl: there's a bug about it, bdrung worked on anchors for packages [06:52] dholbach: from the middle to the bottom, you don't know which bug number represts what [06:52] but it's still not merged because of some other problems [06:52] like MOTu Science subscribed packages or whose packages fall under Category="electronics" and stuff? [06:52] nxvl: I know [06:53] dholbach: i have a workaround on my ppa, but i never finished it [06:53] tuxmaniac: what is the launchpad team name? [06:53] err [06:53] motuscinece [06:53] on my bzr [06:53] motuscience [06:53] dholbach: you will do packaging 101 in just 1 hour this time? [06:53] oh, separate fixing bugs [06:53] tuxmaniac: there's a small script at https://lists.ubuntu.com/archives/ubuntu-devel/2008-August/026118.html [06:53] understood [06:54] tuxmaniac: if you run python bla.py motuscience it will give you a harvest URL for that team [06:54] it's not perfect, but bobbo is working on a different solution [06:54] i love slangasek talk! [06:54] it's a funny name [06:54] and we're looking into using seeds to split up the packages [06:55] NCommander: I did, if you mean the ones on youtube.com/ubuntudevelopers [06:55] dholbach oh let me check [06:55] NCommander: english ones dholbach and spanish one me [06:55] dholbach, ah, so that's what you look like :-) [06:56] I have longer hair now [06:56] dholbach: i love UbuntuDeveloperWeek schedule [06:57] looks better than the last one [06:57] nxvl: I uploaded a few pictures from the India trip: http://picasaweb.google.com/daniel.holbach/India [06:57] and i'm surprised to see so many people i don't know [06:57] and I'm still writing the blog entry about the trip [06:57] * NCommander can see dholbach with a mullet for some reason ... [06:57] I know... I suck [06:57] mullet? [06:57] is there a simple command to compile a source package into binary packages (deb)? [06:57] lol [06:57] dholbach: and i uploaded almost all pictures from disney: http://flickr.com/photos/nxvl/sets/72157606957145935/ [06:57] emet: install devscripts and run debuild -us -uc [06:58] * tuxmaniac quickly clicks on that Indian photo link [06:58] I dunno why, but I do [06:58] and dholbach .. my goodness, the url returned is too big. I have to scroll back to get the complete one on terminator ;) [06:58] tuxmaniac: tinyurl.com :) [06:59] tuxmaniac: http://tinyurl.com/6l7x9b [07:00] \o/ another terminator user [07:00] :D [07:00] what is terminator? [07:00] nxvl: terminator rocks [07:00] tuxmaniac: yes it does [07:00] besides a future killing machine [07:00] * dholbach needs tabs and alt+1, alt+2, alt+3 tab switching to be happy :) [07:00] NCommander: apt-cache show terminator [07:00] dholbach: terminator HAS tabs [07:00] I know [07:01] but no alt+1 alt+2 alt+3 tab switching [07:01] like in gnome-terminal [07:01] would it work on Xubuntu? [07:01] dholbach: cool thanks. [07:01] NCommander: yep [07:01] probably [07:01] NCommander: I don't see why it wouldn't [07:01] * NCommander installs [07:01] dholbach: file a bug [07:02] Ok, what's the wow feature from gnome-terminal [07:02] I've opened a few tabs, but its not quite doing it for me (yet) [07:02] and suddenly I found it [07:03] * NCommander changes his default X terminal [07:03] NCommander: I think what people like best about it is that they can split the terminals horizontally/vertically [07:03] yeah [07:03] Just discovered it [07:03] I was using GNOME terminal in place of xfce4-temrinal [07:03] Now terminator is MY terminal [07:03] * NCommander joins the Launchpad group [07:03] :D [07:04] \o/ [07:04] more terminator users [07:04] dholbach, thank you it works :) [07:04] more bugs and pain for me [07:04] \o/ [07:04] Where is a list of keystrokes? [07:04] NCommander: man terminator [07:04] NCommander: mand terminator_config [07:04] emet: party on! [07:04] s/mand/man [07:04] :D [07:05] Ctrl-Shift-0 doesn't work for me [07:05] might need a newer version? [07:06] I use intrepid [07:06] Its in the man page [07:06] NCommander: it's o not 0 [07:06] ok [07:06] Oh, O! [07:06] I think I'm in love [07:06] NCommander: yep [07:06] It's like when I first started X11 and discovered multiple xterms ... [07:06] ^.^; [07:07] * NCommander joins the Terminator Users LP grou [07:07] NCommander: and when the type in multiple terminals feature come out you will be more in love with it [07:07] it is a terminator users group? [07:07] THere is one [07:07] https://edge.launchpad.net/~terminator-users [07:07] NCommander: you also Cntrl+Drag&Drop to re-order your terminals [07:07] wow [07:08] didn't knew it [07:08] heh [07:08] I also found ubuntu-smokers tonight [07:08] (added after I stumbled upon canonical-smokers) [07:09] monkeys! -> http://picasaweb.google.com/daniel.holbach/India/photo#5238129819067956546 [07:09] For some horrible reason, I want to file a blueprint against ubuntu-smokers "12 step plan to quitting" [07:10] BTW, anyone here xubuntu users? [07:10] nxvl: there were lots and lots and lots of them in Shimla :) [07:10] really? [07:10] walking on the streets? [07:10] yeah [07:11] wooho [07:12] Less that 24 hours until the freeze [07:13] NCommander: the nightmare starts [07:13] ... [07:13] Damn it [07:13] "The Nightmare Begins - Final Fantasy VII Soundtrack" [07:13] My laptop is achieving sentience [07:14] dholbach: btw, the other day i was talking with persia and we come to the point that i'm the only latin american MOTU, or you know other? [07:15] nxvl: it very much looks like it [07:15] * nxvl felt lonely after that conversation [07:15] oh [07:15] nxvl, it could be worse [07:15] them [07:15] * nxvl feels oficialy lonely [07:15] nxvl: I'm sure you can get a bunch of other people involved! :) [07:15] dholbach: yep, i get invited to latinoware this year to give a talk [07:15] dholbach: i will try to wash some peoples mind [07:15] :D [07:16] nice [07:16] i think they are going to invite jono also [07:16] Install plan 9 on their machines, and when they beg you to remove it, install Ubuntu ;-) [07:16] they needed an ubuntu keynote speaker [07:17] bug 260158 is "fix released" but harvest lists it as an opportunity. I am not getting it. [07:17] Launchpad bug 260158 in gabedit "[ftbfs] 2.1.8-2 falils to build on intrepid pbuilder" [Undecided,Fix released] https://launchpad.net/bugs/260158 [07:17] so i told them about jono and to forget about mark [07:17] :P [07:17] tuxmaniac, I think there is a lag before harvest updates [07:17] yup [07:17] there is [07:17] NCommander: hm? [07:17] more than 12- 15 hrs? [07:17] what kind of lag you mean? [07:17] ah - that [07:18] dholbach: you close a bug in launchpad and it doesn't update harvest automagically, or it does? [07:18] it's not actually a lag in harvest, but in the script that generates the .csv list of bugs, that harvest downloads [07:18] it's a harvest-data 'bug' [07:18] dholbach: yeah, but considering that script as part of harvest, it is [07:18] I don't know how harvest works so can't say specifically [07:19] harvest checks the list of .csv urls every hour and checks if there were changes made to those .csv files [07:19] also, not a bug, just how things work [07:19] you can't have up to date data on such a tool [07:19] http://daniel.holba.ch/harvest and http://daniel.holba.ch/harvest/doc should have more info [07:19] dholbach: every hour. but this bug was closed 12 hrs back almost [07:20] tuxmaniac: + the time that it takes to create/update the /cvs [07:20] .cvs* [07:20] tuxmaniac: in this case it's bdmurray's script that spits out a .csv file somewhere, that harvest downloads, puts into a database, then generates HTML from [07:21] oh ok. interesting [07:21] so we need to blame bdmurray [07:21] :D [07:21] harvest has no understanding of bugs, duplicates, patches and so on [07:21] I wanted to keep that kind of logic out of the code to make it easier :) [07:22] dholbach: oh, btw, it will be interesting to make a video about how/where to find things to fix (ie. harvest, MoM, ubuntuwire, etc...) [07:22] and how they work [07:22] yes, it would [07:23] but as always time is a problem [07:23] :( [07:23] it'd be nice to have all this information in harvest [07:23] or wiki [07:23] MoM should spit out a .csv file too [07:24] and be updated [07:24] :D [07:24] woohoo i've just find that terminator has a search bar [07:24] \o/ [07:24] i always wanted that [07:24] and i call myself a terminator developer [07:24] :( [07:25] *falls over* [07:25] nxvl, it could be worse [07:25] YOu could be a Vista developer [07:25] yep [07:26] * nxvl runs screaming [07:26] rofl [07:26] nxvl, are there any important packages that needs work befor ethe freeze date? [07:26] (aka, can I do some more good stuff?) [07:26] geser: there? need to discuss libjboss-cache stuff [07:27] NCommander: mmm you can make some ufw integration [07:27] ufw? [07:27] NCommander: https://wiki.ubuntu.com/ServerTeam/Roadmap#UFW Package Integration [07:27] link? [07:27] NCommander: https://wiki.ubuntu.com/UbuntuFirewall#Integrating UFW with Packages [07:27] whats UFW? [07:27] Oh [07:28] Ubuntu firewall [07:28] Uncomplicated Firewall [07:28] or Ubuntu Firewall [07:28] or U* Firewall [07:28] It is certainly not Ubuntu Firewall [07:28] (replace * with whatever makes sense for you) [07:28] Unconfigured? [07:28] * NCommander ducks for cover [07:29] can you just check if there are any glaring mistakes on http://daniel.holba.ch/blog/?p=189 [07:29] ? [07:29] i think oficial name now is Uncomplicated [07:29] dholbach, checking [07:30] dholbach, if you want to host something about Xubuntu, I am your man ;-) [07:30] dholbach: The Ubuntu Developer Week is designed to give you an overview of what’s going on in the Ubuntu Developer week [07:30] NCommander: unfortunately the schedule is all set right now - but if you were available as a backup that'd be awesome [07:30] dholbach: doesn't make much sense [07:31] nxvl: eh? [07:31] nxvl: a yes :) [07:31] dholbach, I assume my notice to fill in comes five minutes after the start date of a class ;-) [07:31] i think last 'week' should be 'world' [07:31] s/week/world [07:31] or something [07:31] heh === emma_ is now known as emma [07:31] :D [07:31] meta-events! [07:31] at UDW find out what UDW is about! [07:32] * NCommander falls over [07:32] During the freeze, I'm likely going to be dedicating a good chunk of time to backports testing [07:32] Its a good month to flush out the queue [07:33] stretching legs & kicking out power cord is not a good thing [07:33] ajmitch, better then the dog takes a leak on your surge protector [07:33] Then again, I think that was probably the most effective house breaking ever [07:33] thankfully I don't have a dog to do that [07:34] * NCommander should start a poll on the most common original Linux used by UDs [07:34] I see a lot of Red Hat, but relatively few people start off as Debian as their first distro ever [07:35] Just as a completely non-scienific poll, what varient of Ubuntu are the devs running [07:35] (I'm kinda curious of Kubuntu or regular Ubuntu is more popular these days) [07:38] dholbach: why we are not having the ask Mark session? is he busy? [07:38] nxvl: we have "ask Matt"! [07:39] dholbach: we should have ask jono [07:39] that would be SO fun [07:39] people use to make funny questions to jono all the time [07:39] and worst if popey is aroun [07:39] around [07:39] nxvl: Did we have that once? [07:39] Didn't* [07:39] jpds: yeah, don't read the logs [07:40] jpds, what happened? [07:41] dholbach: other than the s/week/world thing it's good [07:41] (or at least it looks good) [07:41] NCommander: Can't remember. [07:41] thanks nxvl and thanks for digging [07:41] :D [07:41] jpds, out of curosity, do you use kubuntu/ubuntu/xubuntu? [07:42] (or other) [07:42] NCommander: ubuntu. [07:42] whenever you want [07:42] dholbach: this UDW looks awesome [07:42] I'm trying to figure out what people find so appealing about kubuntu [07:42] dholbach: there are a lot of sessions i want to see [07:42] yeah, same here [07:42] more than the half [07:42] I've tried it, but KDE never seems to work quite as seemlessly as Ubuntu, and I have to wonder if I'm maybe missing here [07:43] dholbach: i'm also surprised with the amount of new people giving sessions [07:43] that's right - we have lots of great people :) [07:44] yes [07:44] is good to see so many people don't being afraid and jumping in into new things [07:45] Yup, I agree with nxvl [07:46] which forums would be the first for the UDW announce? [07:46] kubuntu-desktop is uninstallable :-/ [07:46] "community cafe" and "intrepid ibex testing"? [07:46] dunno [07:46] don't know the forums [07:46] ok [07:46] * dholbach will put it on those two [07:46] time to sleep [07:47] read you later [07:47] sleep tight nxvl! [07:47] and have a nice day/sleep tight [07:47] dholbach: thank you! have a nice day! [07:47] gracias :) [08:01] morning :) [08:02] hi didrocks [08:02] Ubuntu Developer Week announced! :) [08:02] dholbach: !!! [08:02] seems like everybody is pretty happy with the offered sessions :) [08:05] dholbach: they look great indeed [08:09] oh noes, udu! [08:09] er, udw! [08:09] Hobbsee: it's been a while since UDU :) [08:09] dholbach: that's true. that's before my time :P [08:10] dholbach, UDU? [08:10] * dholbach still remembers the H U G E key signing party there [08:10] Ubuntu Developer U? [08:10] everyone line up... [08:10] NCommander: Ubuntu Down Under [08:10] sounds like fun [08:10] and don't touch mako's passport :) [08:10] Where is this all being done? [08:11] it was the UDS in Sydney [08:11] in 2005 [08:11] I mean this UDW? [08:11] Or is it just all online [08:11] NCommander: https://wiki.ubuntu.com/UbuntuDeveloperWeek/JoiningIn#ubuntu [08:11] oops [08:11] UDW is online, UDS isn't [08:11] NCommander: https://wiki.ubuntu.com/UbuntuDeveloperWeek/JoiningIn [08:12] I'll join in [08:12] Even in the basic classes, you can learn neat tricks [08:12] absolutely [08:13] * Hobbsee wonders who will get sacrificed to the ubuntu gods, in the sessions. [08:14] you [08:14] i won't be there, so it won't be me [08:14] or if i am, i wont be for much of it, and i won't be paying much attention. [08:14] <\sh> Hobbsee: bug #244261 isn't resolved ... it crashes with the same output and I really think it has to do with the sound stuff [08:14] Launchpad bug 244261 in recordmydesktop "Locking assertion failure libxcb-xlib.so.0 xcb_xlib_unlock" [Undecided,Confirmed] https://launchpad.net/bugs/244261 [08:14] morning Hobbsee [08:15] hey NCommander [08:15] how goes it? [08:15] Hobbsee: you'd be there more than me [08:16] even if I wanted to be involved, I live in the wrong timezone [08:16] well, i'll be writing parts of a compiler, and such [08:16] trivial tasks [08:16] Hobbsee, what are you doing O_o? [08:16] you should have that done soon enough [08:17] NCommander: assignments. [08:17] You get to write compilers in your uni classes? [08:17] Damn, your uni 0wns mine [08:17] ajmitch: heh. i would have, if i was actually *here* this weekend. [08:17] NCommander: in programming languages, yes. [08:17] fun [08:17] The most I ever did was write the start of an assembler [08:18] Hobbsee, luck be to you though, if your writing a C compiler, god help you on the grammer rules [08:18] \sh: interesting. [08:18] NCommander: heh. fortunately not - it's a calender language. [08:18] Oh good [08:18] some compiler theory isn't that unusual in a lot of CS schools [08:18] \sh: i did that on the basis of "upstream says it's fixed, so it probably is" [08:18] <\sh> Hobbsee: fun part, recording mono sound works...and doesn't crash, recording two channels -> same output [08:18] Our CS program believes in Java only [08:19] CS at the uni I went to is switching from java to python for its introductory courses [08:19] Which is why I promptly left when I came to the conclusion that most professors have no idea what the real world needs [08:19] I don't mind if they teach java or require it [08:19] ajmitch: Mine is switching from C to Python. [08:19] but they do a lot of C after that [08:19] Mine was straight java [08:19] And then C in later years, of course. [08:19] I think you get MIPS assembler in your fourth year [08:19] And Java for one subject. [08:19] But no C AFAIK [08:19] How can they avoid C!? [08:19] They should teach C first IMHO [08:20] Using a garbage collected language is a horrible learning tool [08:20] Teaching C to non-programmers is stupid. [08:20] Because it teachs all the wrong lessons [08:20] The CS program here is a joke I found [08:20] All theory, no praticial [08:20] We do have a computer enginneering tech class which is what IMHO, CS should be, but its too heavy on the hardware side for me to enjoy [08:21] I personally believe though that using garbage collected languages as a learning tool is a joke [08:22] Get people not to depend on GC()s, or else they'll never learn to apperiate the full consequence of bad code. [08:22] i know first year rocket scientists at southampton were given some C [08:22] and my wife picked up some C from her MUD days [08:22] like I said, its a joke here [08:22] The local LUGS users know more then the graduates [08:22] (five of them are people who left the CS major for the same reason I did) [08:23] at least in practical skills [08:23] most CS degrees i know of start with "easy" languages then move down to lower level things, rather than the reverse [08:24] my degree was mostly java based, possibly because they could teach principles and data structures and algorithm design without needing to do nearly as much unrelated groundwork first [08:24] our java classes was programming 101 [08:24] And I mean like actual 101 [08:25] You know, this is a statement, you print text like this, meet objects, etc. [08:25] About the only thing I got out of two quarters of that class was a crash course in generics since JDK 5 was released over winter break :-) [08:25] i prefer the top-down approach these days. i think a beginner will learn more overall starting with ubuntu & ending on LFS rather than the reverse [08:26] No, I understand what you mean [08:26] directhex: That is my thinking. [08:26] A friend of mine told me the following [08:26] "If your going to write code, use smart data structures and stupid code" [08:27] within reason [08:27] Of course :-) [08:27] My big issue with my uni's CS courses is that data structures weren't taught until the second year [08:27] NCommander: You can't teach data structures with no groundwork [08:28] iirc first year CS students at my alma mater write a basic kernel in first year now [08:28] when i was there we had to design our own malloc [08:28] I learned C from a Wrox book that taught basic structures [08:28] I dunno [08:29] I find in general a CS degree is somewhat overrated [08:29] well, i don't specifically use what i l;earnt on my degree to do my job [08:29] i use what i learnt in my spare time during those 3 years [08:30] Sure, thats how its supposed to work [08:30] but that's not to say those years weren't valuable at some level [08:30] I just find that most CS students seem to lack the ability to think criticially [08:30] ALthough I think thats a department issue here [08:30] s/CS // [08:30] Vs. an actual CS issue [08:30] Ok [08:30] POint taken [08:30] you wouldn't believe some of the dunces here doing postgrad degrees [08:30] Oh yeah [08:31] I would [08:31] I work ITS helpdesk [08:31] Had to help a postgrad install Office cause the autoplay didn't kick in [08:31] This was a CS postgrad [08:31] So, you would believe some of the dunces teaching postgrad courses, too? [08:31] i mean phd students at the world's premier university who don't understand elevators [08:31] How do people like that not wash out is beyond me o_o; [08:31] *literally* didn't understand elevators. the guy's an inorganic chemist [08:32] *hits head* [08:32] How. [08:32] Ugh [08:32] That just hurts my brain [08:32] he's very special that one [08:33] At some point, I think I came to the conclusion that a BS was a very expensive piece of TP that told employeers that someone can sit for four years and not get in trouble [08:33] we also had the guy who spent 3 days organising a meeting, then on the day of the meeting, sends an email asking if he can arrange a meeting, as if he was on some drug-fuelled bender for those 3 days & didn't know they'd happened [08:33] I changed after my second year from Information Tech (after leaving CS) to Criminal Justice and I haven't looked back [08:33] I'm actually learning things and enjoying myself [08:34] i was sick of my degree by the time i got to third year. too much education makes one feel ill [08:35] Well, two years of CJ [08:35] And I totally love it [08:35] I'll keep doing tech stuff though Ubuntu and such [08:35] And if I can get an employeer who realizes CS degrees aren't really all that important [08:36] Otherwise, I plan to go on and become a sheriff up in Alaska [08:36] http://img.thedailywtf.com/images/200808/errord/orangefull.png #spot the problem [08:37] ahaha [08:37] I already saw this [08:37] I'm a moderator on the daily wtf :-) [08:37] Urgh MFD. [08:38] NCommander, that's cheating! [08:38] directhex, they've updated the image [08:38] Now its got the thedailywtf next to the NSFW item [08:39] Haha [08:39] NSFW is a bit of a generalization [08:39] And the dozens upon dozens of comments saying that... [08:39] if you work for gawker media's porn review blog, for example, i'm pretty sure it's not nsfw [08:39] ... [08:39] Or if you work from home.. [08:40] Relatively speaking [08:40] directhex: I suspect that that's a fairly rare position. [08:40] bobbo: here ? [08:40] What soren said :-P [08:40] soren: depends on who else works from home :) [08:40] wgrant, sadly so :'( [08:40] Haha [08:40] I don't think I want MyFirstSexTeacher however popping up on my employors desktop [08:40] jml: Point :) [08:40] Oh no, attack of the Canonical people! [08:40] Incoming! [08:40] wgrant: You forgot "evil". [08:41] :) [08:41] nyargh, we come to exploit your community-driven off-topic conversations [08:41] soren: Please wait while I grab that blog post with its creative insults. [08:41] we will harness the power of off-topicness to RULE THE WORLD [08:42] Quickly, we must all go to #canonical and flood the place with ontopic stuff [08:42] jml: Or at least power a small city. [08:42] The future of #ubuntu-motu depends on it! [08:42] less babble, more main sponsorship, canonical people. [08:42] NCommander: I'm not sure there's any such thing. [08:42] soren: heh heh [08:42] NCommander: ontopic stuff in #canonical that is. I'm not denying the existence of the channel itself. [08:42] also, find me some packing tape so i can mail this hard disk to SGI [08:42] It's a pity non-sense isn't a viable power source [08:42] hey [08:43] The random bouts of insanity in thise room could power the world [08:43] That I cannot deny. [08:43] I mean, a few weeks ago, we had someone trying to make Ubuntu Developer trading cards [08:43] awesome idea [08:44] it made slangasek go WTF [08:44] so the AGPLv3 license issue seems to be resolved [08:44] mjg59, i choose you! [08:44] Arc_: [citation needed] [08:44] * NCommander uses a FTBFS against didrocks [08:44] er directhex [08:44] wgrant: Mark Shuttleworth in an email to the community council, technical council, and myself: [08:44] Whats really sad is if we put our heads together, we could probably make a viable game [08:44] trading cards, pokemon cards, same difference [08:44] "My view is that the AGPLv3 is a free license and I would have no reservations about supporting the main / universe inclusion of an AGPLv3 package." [08:45] The goal is to be the first to release, and you have packages, bugs, blueprints, translations, FTBFS, and random events [08:45] Well, he would say that. [08:45] But he might well be correct. [08:45] given that the community council also has one of the AGPLv3 co-authors on it.. [08:45] so I return to ask what the process is [08:46] wgrant: Was this what you were looking for: "triblodyte bricordion nickerbook" [08:46] soren: That's the one. [08:46] What's the story with the AGPLv3? [08:46] It's creative; I'll give him that. [08:46] wgrant: Now, if we could somehow harness the power of the pointlessness of that discussion, we'd be close to world domination already. [08:47] NCommander: the AGPLv3 is identical to the GPLv3 except section 13, which it adds the requirement that if you host an online app (ie, a webapp, game server, etc) that's modified from what has been distributed, you must offer to all users your changes [08:47] soren: But Canonical is evil! [08:47] its to close the "ASP Loophole" in the GPL [08:47] right, I"m aware of that [08:47] what's debian-legal's take on AGPLv3? [08:47] Debian bug #495721 [08:47] Debian bug 495721 in ftp.debian.org "ftp.debian.org: Is AGPLv3 DFSG-free?" [Wishlist,Open] http://bugs.debian.org/495721 [08:47] directhex: the consensus seems to be that AGPLv3 is DFSG-nonfree [08:47] Oh, there is dispute on if it is a free (DFSG) license? [08:47] NCommander: Correct. [08:48] At first glance, it seems to pass the d-legal evilness tests [08:48] which is why I sent an email to the Ubuntu councils, since Ubuntu tends to be more sane when it comes to license freeness [08:48] but reading this [08:48] I don't know [08:48] Whether we are more sane is debatable. [08:48] I don't like the AGPL because it feels in many ways impratical [08:48] wgrant, sanity is not part of Ubuntu [08:49] In my mind it is non-free. [08:49] At least, its not synced from Debian [08:49] As I can't safely modify it. [08:49] NCommander: the issue is not whether anyone likes it or not, projects are using it, and people are voting through their use or non-use of it [08:49] RMS is correct that the ASP loophole is valid [08:49] hm, i wonder if my details are part of that "server ebayed contains millions of bank details" news story [08:49] much like the BSD vs GPL issue, we could argue it for years, but in the end it's code released under the licenses that the philosophy is worked out [08:50] i should ask andy to grep for me [08:50] But I think there is a point where even he's decided to push idealogy far ahead of everything else [08:50] NCommander: I agree fully. [08:50] Having had an opprtunity to briefly meet with RMS [08:50] NCommander: ? :) [08:50] He's right on a lot of issues, but he has the stance of no-surrender, no giving up [08:50] NCommander: I don't believe RMS was the force behind the AGPLv3, it was several FSF board members and lawyers with the SFLC [08:50] I'm not aware [08:50] Arc_: There is a significant practical problem with the AGPL. It's not like BSD vs. GPL. [08:50] GPL doesn't restrict use. [08:51] Actually, RMS blessed the AGPL [08:51] wgrant: let's not get back into that discussion. [08:51] When I was a FSF Savannah admin, we were told to explicately allow AGPL apps [08:51] Arc_: It is core to the issue. [08:51] NCommander: yes he did, but he was not the force driving it [08:51] Normally, we only accept packages that are license compatible with the GPL current revision [08:51] wgrant: I am not here to debate licenses. I am here asking for information on how packages get included in Ubuntu [08:52] Well, until the issue is disputed [08:52] Arc_: Upon entry you mentioned the AGPL issue. [08:52] Shove it into Multiverse [08:52] And packages don't enter Ubuntu unless their license is fine. [08:52] the package in question is not, nor will, be in the Debian repository [08:52] wgrant, AGPL is acceptable for multiverse [08:52] Nor do they enter Ubuntu a day before FF. [08:52] Oh, thats true ;-) [08:52] NCommander: the issue seems to have already been resolved, AGPLv3 is acceptable for universe. [08:53] * directhex grumbles about having failed to get mono-basic into debian before ubuntu ff [08:53] ugh [08:53] Nor do they hopefully enter Ubuntu if somebody asserts that it will not be in Debian without good reason. [08:53] That's going to be rather interesting if Debian says its not [08:53] let me put it this way; if the package in question had to go into multiverse, we would not submit it for inclusion in any repository but only offer it on our website [08:53] cause that means now non-free packages from Debian may enter universe [08:53] Arc_: I believe a chance exists that Mark is not impartial in this matter. [08:53] NCommander: welcome to reality, they already are. [08:54] wgrant, what was marks relationship to AGPL? [08:54] NCommander: He suggested that it be used by Launchpad. [08:54] Ubuntu has considered the GNU FDL a free license and included packages into universe/main which debian includes in non-free [08:54] .... [08:54] ew [08:54] I thought I hated LP being closed [08:54] But that's just plain ugly [08:54] when did FDL start being free? [08:55] FDL? [08:55] guys, please. I'm here asking about packaging, not licensing. [08:55] Free Documentation License. [08:55] the documentation license with invariant sections [08:55] Which isn't so free. [08:55] I thought the FDL was free as long as there were no invarient sections [08:56] if i can say "this documentation is free, except all the sections are invariant" kinda goes against freedom [08:56] Is it me or all *ubuntu* ML seems to be down (devel, motu, intrepid-changes) ? Or nobody's working ? :) [08:56] what is the difference between Main and Universe, in terms of the process packages get to be included in each [08:56] didrocks: We're all busy debating the merits of the AGPL :P [08:56] wgrant: I see that :) [08:56] is there a better channel for me to ask about Ubuntu package policy? [08:56] Arc_, nothing enters main directly, it goes into universe, and if it needs to be supported by Canonical, you file an MIR to make it go to Main [08:56] Arc_: Packages almost always enter universe first, They may then get promoted. [08:57] Arc_, normally, its here. [08:57] But we're debating the AGPL at the moment [08:57] Arc_, main inclusion needs a damn good reason and/or sexual favours in the right places [08:57] didrocks: Keep it family friendly... [08:57] Gah. [08:57] that was a visual I didn't need [08:57] directhex: ^^ [08:57] then again, we were talking about that NSFW site before [08:57] debating the AGPL would be better in a channel like #FSF would it not? [08:57] ice cream, then. everyone loves ice cream. [08:57] this is Ubuntu specific [08:57] wgrant: twice this morning :) [08:57] Techinically we could chat about this in -devel [08:58] didrocks: So I noticed. [08:58] As I've been told MOTU doesn't make policy, the technical council and community council does. [08:58] not regarding licensing, at least [08:58] The community council doesn't make policy unless we can't decide on something [08:58] considering i've been directhex since the mid 1990s, i blame didrocks [08:58] In a matter like this, I believe it would be inappropriate for them to hand down a judgement without further discussion. [08:58] whenever I see directhex, I think of directx [08:58] Particularly given what has happened in Debian. [08:58] wgrant, what happened in Debian? [08:59] directhex: I am didrocks from 1998 only, sorry :p [08:59] NCommander, yes, that was the idea. directx was new and hip when i picked the pseudonym [08:59] Well, the license is ambiguous, and a has a use restriction. [08:59] Obviously you never programmed against it [08:59] wgrant, I find the AGPL to be worse then the damn adversing clause [08:59] NCommander, no, because i would have been about twelve at the time [08:59] And its so freaking vague [08:59] NCommander, and far too busy discovering internet porn [09:00] NCommander: Correct. [09:00] wait, family friendly. gah [09:00] Fail [09:00] wgrant: that is your opinion. not everyone agrees with your assessment. use restriction would violate software freedom #0 and, if commonly held, would have never been released. [09:00] sorry. [09:00] wgrant: can you just confirm that you didn't received any email from those ml from the last 8 hours? [09:00] Is there any mechanism where the TB can be overruled? [09:00] NCommander: sabdfl. [09:00] NCommander, isn't that what the "dictator" part means? [09:00] I don't believe we've had an official ruling yet, have we? [09:01] It sounds like Mark though has a vested interest [09:01] There are other members of the CC and TB. [09:01] And we've heard nothing official from anybody at all. [09:01] they've been discussing it for days [09:01] Let us not jump to conclusions about official decisions. [09:01] But what's the fun of speculation then wgrant ;-) [09:01] bah. does anyone have any parcel tape i can borrow? [09:02] directhex, if you live in Rochester .... [09:02] Based on the few chats I've had on the AGPL [09:02] didrocks: I've received many emails on intrepid-changes over the past several hours. [09:02] you know I came on here before asking about this, and left without answers because the people here then, too, were more interested in license banter [09:02] The last being some 37 minutes ago. [09:02] I won't be suprised if the developer community had a massive backlash if AGPL was deemed to meet DFSG for Ubuntu [09:02] Arc_: You did bring up the licensing issue. [09:03] And it is an issue. [09:03] And people wish to discuss it, so it shall be discussed. [09:03] forget I mentioned the AGPLv3 [09:03] I'm asking about package policy [09:03] What's the actual question? [09:04] ok so everything goes into Universe first, and it goes through the reve website to do so [09:04] Strictly speaking, it doesn't have to go through REVU [09:04] yes, unless the licence says it's unsuitable for universe. [09:04] NCommander: it usually, does. [09:05] * NCommander has has one package enter universe without passing through REVU [09:05] Hobbsee: if the license is unsuitable for universe, we would not have it included at all, but rather only offer it for download from our site [09:05] Arc_: Why not include it in multiverse? [09:05] Arc_, if it was unsuitable for universe, it can simply be placed in multiverse [09:05] Arc_: you asked a general question, i answered it :) [09:05] because that would be false advertising as proprietary software [09:05] * Hobbsee blinks [09:05] * NCommander double-takes [09:05] vlc isn't proprietary. mplayer isn't proprietary. [09:06] There are GPL-pieces of softare in multiverse [09:06] I'd put it at the majority actually [09:06] Those are just two examples of things that are in multiverse for other reasons that source Freeness. [09:06] I was told that multiverse == nonfree [09:06] Arc_, no, multiverse is non-free, contrib, doesn't meet DFSG [09:06] It also includes things that have usage restrictions. [09:06] Arc_: correct, but nonfree != propriatory, all the time. [09:07] Such as patents, or soon AGPL's clause 13, I hope. [09:07] the usage restrictions, etc, ... make it nonfree - but not proprietory. [09:07] multiverse is unsuitable for Main, correct? [09:07] Arc_, yes [09:07] Correct. [09:07] THere is restricted, but someone has to litterialy die to get a package to go there [09:07] then there is no point in inclusion [09:07] restricted is multiverse for main [09:07] But most packages are unsuitable for main. [09:07] Arc_: Huh? [09:07] why the heck do you want your package to go into main [09:07] The vast majority do not leave multiverse [09:07] Arc_: So there's no point having it at all if it can't go into main!? [09:07] NCommander: to get it installed by default, usually. [09:08] Hobbsee, the CDs are so full that we're getting to the point we need to prune them back [09:08] that is not what I was implying, but I'm not feeling a great deal of patience right now to explain [09:08] NCommander: don't tell me about cd sizes. i'm part of the release team... [09:08] NCommander, mono will shrink for ubuntu+2 [09:08] NCommander: They have been for years. [09:08] We should just remove mono from the CDs [09:08] Problem solved for another year [09:08] :-) [09:08] * NCommander runs [09:08] NCommander: :) [09:08] * directhex drops an altix on NCommander [09:08] Arc_, I'm an Xubuntu developer. Our distributions main piece of software Xfce is completely in universe [09:09] NCommander: YOU MEAN WE SHOULD REMOVE MONO BECAUSE IT IS MY NOVELL? [09:09] TEH PATENTZ! O NOEZ! [09:09] NCommander: I did not mean "there's no point if it can't enter main". [09:09] oh dear. [09:09] * Hobbsee has already dealt with one of them today. [09:09] Haha [09:09] speaking of proprietary, we (= the OpenVAS project) have prepared packages to replace the nessus server packages (OpenVAS is the still-GPL fork of Nessus) [09:09] Actually, I was just suggsting mono's removal cause its a little overkill to have both java and mono in the default install if only one or two apps depend on the later [09:09] Didn't Nessus already change name? [09:10] (although I think there is a non-free Xfce package) [09:10] is there any chance the packages could make it into intrepid? [09:10] Arc_: What precisely did you mean? [09:10] mwiegand, if its in universe already [09:10] seriously though. mono's dependency chain should shrink a good 25%+ post-intrepid [09:10] ok so how long does REVU typically take, given a situation where the packaging is well done and prepared by upstream, and what alternatives to REVU are available [09:10] StevenK: no, Nessus is still Nessus [09:10] Arc_, we haven't have a REVU day this cycle [09:10] It won't be included until intrepid+1 [09:10] NCommander, which java is in the default install? [09:10] (novemberish) [09:10] Arc_: Well, Intrepid closes tomorrow. [09:10] "REVU day"? [09:10] I thin jre6 [09:11] NCommander, so that's about twice the size of mono, then? which apps use it? [09:11] Arc_, roughly speaking, unless a miracle happens, and you can get 2 advocations within the next 24 hours [09:11] And we find that upstream packaging is often problematic. [09:11] Its not going to see a release this time around [09:11] we're not looking at Intrepid, we're looking at 9.04 [09:11] (this is a generalisation; yours might be fine) [09:11] Yeah [09:11] intrepid+1 == 9.04 [09:11] The alternative to REVU is Debian. [09:12] mentors isn't extactly happy these days [09:12] we're nowhere near ready for 1.0-beta3 release, currently our trunk still has known multicore segfault issues and several thousands of lines of code remaining to be refactored before that'll be resolved [09:12] they're dealing with their queue issues [09:12] NCommander: the client packages have already replaced nessusclient in intrepid, the server packages are in the Debian NEW queue [09:12] so right now in intrepid there is the openvas-client, but the nessusd as well [09:13] ok so REVU and Debian are the only ways to get a package included in universe? [09:13] mwiegand, so all the packages are in universe/intrepid right now? [09:13] Arc_, if its part of a CDDS, it can also be synced into Ubuntu [09:13] Arc_: Pretty much. [09:13] what is CDDS [09:13] NCommander: Debatable. [09:13] er, CDS [09:13] And rare. [09:13] And frowned upon. [09:13] I asked, and I got a yes [09:13] But yeah, its really rare [09:14] I've not seen that acronym or project name before [09:14] CDS = CUstom Debian Distribution [09:14] Er [09:14] ... [09:14] NCommander: You mean CDD? [09:14] Yeah [09:14] Christ, I'm out of it [09:14] NCommander: from OpenVAS only -client and libopenvas [09:14] Are packages accepted into debian more easily then through REVU into ubuntu? - generall speaking... [09:14] dear DHL, please make the "email address" box bigger than the "surname" box. love directhex [09:14] stefanlsd, with a decent sponsor [09:14] mwiegand, it might be worth granting a feature freeze exception once they pass the Debian NEW queue [09:15] Debian isn't an option for us, so I'm guessing REVU is the only path [09:15] Replacing non-free with free is always a good thing [09:15] NCommander: so should I file a needs-packaging bug for the remaining components? [09:15] mwiegand, wait, I thought the components were already packaged [09:15] Arc_: has it actually been REJECTed from the Debian NEW queue? [09:15] now the MOTU-games group has defuncted, is there a MOTU-python group active? or is there another path to get inclusion? [09:15] NCommander: they are, just not in ubuntu [09:16] Arc_: The groups are not particularly relevant. [09:16] james_w: we have respectfully asked not to be included in Debian, and our request has been honored. [09:16] Oh, ok, submitted to Debian I assume mwiegand? [09:16] Arc_: why did you ask? [09:16] NCommander: so I'm unsure as to what we have to do in order to get it into ubuntu [09:16] Deliberately not being included in Debian seems very... strange. [09:16] wgrant: well a Python-based 3d game engine isn't going to appeal to every MOTU member, I'm assuming [09:16] james_w: ask what? [09:17] Arc_: ask not to be included in Debian? [09:17] NCommander: see http://ftp-master.debian.org/new/openvas-server_1.0.1-1.html and http://ftp-master.debian.org/new/openvas-plugins_1.0.2-1.html [09:17] mwiegand, well, wait for it to go through the NEW queue, and enter unstable/experimental [09:17] mwiegand: you can file a "sync" request once it's out of NEW [09:17] If we're still in soft freeze, I recommend then you file the sync request, and then ask for a https://wiki.ubuntu.com/FreezeExceptionProcess [09:17] james_w: answering that question would risk diverting from my current line of questioning, I can answer in private if you'd like. [09:17] mwiegand: for Intrepid they will need a freeze exception unless it makes it out today. [09:17] moring everyone [09:18] hey james_w ! [09:18] Arc_: sure [09:18] hey huats [09:18] james_w, replacing a non-free with a free package (which appears to be based off the same codebase) should be ground for a FFE [09:18] NCommander: I agree, but I have no say in the matter [09:18] REVU requires 2 MOTU members to do a code review, if I read the website correctly - this code review is several thousand lines of an obscure Python/C hybrid language [09:19] Er [09:19] james_w: I don't know, I have to talk with our Debian packagers about that [09:19] Its not a code review [09:19] it's a packaging review, not a code review [09:19] lintian cleanness, valid debian/rules, etc [09:19] then why only provide a source package? [09:19] mwiegand, wait for the package to leave NEW, then talk to cody-somerville, he can tell you if a freeze exception will be done [09:19] mwiegand: it's not likely to, but as long as it makes it out within the next couple of weeks you should be ok. [09:20] mwiegand: the sooner the better though, so I hope it doesn't get REJECTed. [09:20] Arc_, REVU only accepts source packages by design, not much point to allowing binaries uploads which may or may not be built from valid source packages [09:20] thanks, that sounds good [09:20] The main archive only accepts them so all packages are built in a clean-room environment [09:20] NCommander: who builds them, then? [09:20] mwiegand: assuming you get the freeze exception that is. [09:20] Arc_, automatic build daemons [09:20] Same as Debian [09:20] (although DDs can do binary uploads to Debian directly) [09:20] I'm not familiar with that process. [09:21] Roughly speaking [09:21] When you package something for debian/ubuntu [09:21] NCommander: Unless you're blocked :-P [09:21] Typing debuild -B generates binary packages [09:21] are we suppost to add a special script to inform debuild how to do this? [09:21] No ... [09:22] Arc_, you need to review the basics of packaging [09:22] debian/rules [09:22] james_w, yes, it does [09:22] The buildds generate these in a clean chroot'ed environment to make sure that packages can be built from source and to make sure no binary package has been meddled with [09:22] HAHAHAHAHA, i'm sure nobody's made that joke before. i'm a comic genius i am [09:22] directhex: yes, yes you are :-) [09:22] NCommander: I'm asking how it knows how to build from source. I know how Portage does it, for example, as I've been a Gentoo packager in the past [09:23] Arc_, ok, ebuild == debian/rules file [09:23] Arc_: you didn't /msg me to explain your reasoning for asking not to be in Debian. [09:23] the rules file is a makefile with a set of targets that explain how to configure, patch (if necessary), and build it [09:23] Arc_, because there's not much else to do with a dsc/diff.gz/orig.tar.gz combo [09:23] I've built a few Ubuntu packages before (binary only) for configuration for our computer recycling program [09:23] ANd then stages into a proper holding directory, and then uses debhelper to build the deb [09:23] james_w: hold on a sec [09:23] Arc_: if you don't explain it then it sounds like you are being hostile to Debian, which won't win you any friends in Ubuntu [09:24] While sometimes getting a package into Debian can be a pain, its for the good of both Debian, and Ubuntu (and Ubuntu descendants), that stuff goes upstream [09:24] I have (attempted to) submit things back to Debian [09:24] although slangasek took off screaming when he saw upstream shipped a debian folder [09:24] NCommander, which is why most of my packaging goes into debian, and i just hang out here to harass people for merges/syncs of my work [09:25] I have too many issues finding sponsors [09:25] Once I get DD-ship [09:25] I am strongly opposed to keeping things out of Debian. [09:25] james_w: I will talk to you in a moment. [09:25] Which should be soon, then everything I do will be going into debian [09:25] then synced to Ubuntu [09:25] NCommander: so the debian/rules file is included in the source package? [09:25] No [09:25] Ok [09:25] a Debian source package is three things [09:25] a .orig.tar.gz, which is simply an unchanged* tarball [09:26] NCommander, thankfully, debian-mono is an active team with multiple sponsors, including an ubuntu dev for that end of things [09:26] * - there are rare cases where this tarball must be repackaged, but outside the scope of discusion [09:26] .diff.gz - this is a giant diff file that is applied the original source to create the debian/ folder [09:26] NCommander: I'm assuming either a bz2->gz conversion or .orig.tar.bz2 is acceptable [09:26] NCommander: Along with other Debian changes [09:26] Arc_, yes, and pretty common [09:26] Arc_, In debian it is, but ATM, Ubuntu still rejects .bz2/lzma [09:26] Arc_: Usually, bunzip and gzip -9c [09:27] It can also contain source patches, but this is frowned upon in favor of a proper patching system [09:27] and a .dsc which is just a descriptive file [09:27] the .dsc contains the build rules? [09:27] No [09:27] I told you, the debian/rules file does [09:27] Ok [09:28] the diff file is applied to the original source [09:28] That creates the debian folder and everything in it [09:28] where does the debian/rules file get included? in the diff? [09:28] yes [09:28] in the diff, yes [09:28] ok. [09:28] other important debian/* files go into the diff, like changelog and control [09:28] Every debian package has five files min. [09:28] now a pointed and odd question; in order to build from source, an additional package is needed that is not a -dev of a normal package [09:29] after that it's just a "python setup.py install" [09:29] That's fine [09:29] Just add it under Build-Depends [09:29] is that additional build package a dependency of the source package? [09:29] Arc_, if it's in the archive, that's absolutely fine [09:29] Arc_, build dependencies are defined in debian/control [09:29] ok [09:29] Hi! Is an apt wizards here? I'd like to know how apt chooses which real package to install if a virtual package is required as a dependency. [09:29] AH. debian is the directory, yes I've seen that. ok. things are clicking now. [09:30] Arc_, rules are sorta like ebuilds on steriods [09:30] control is the part of an ebuild file that defines what binary packages are created, and the metadata [09:30] Changelog is extactly what it sounds like [09:30] My problem is that installing linux-headers installs and old version of the headers package (for a kernel which is not even installed). [09:30] Arc_: have a look at the following - there are some nice guides there. https://wiki.ubuntu.com/MOTU/GettingStarted [09:31] Arc_, grab the source to the Debian hello package [09:31] Its a pretty clear cut example on how you can do it [09:31] flohack, which package exactly? [09:31] Pyrex 0.9.6.1 seems to be available. only concern I have there is Pyrex versioning is extremely unstable, and what builds with one version may not build with a later version [09:31] flohack: apt-cache policy can help distill what will be picked to be installed [09:31] er, 0.9.6.4 [09:31] Arc_, again, thats fine [09:31] Arc_, I assume pyrex generates a library? [09:32] Pyrex pre-processes our source language into .c [09:32] directhex: I installed dkms, which depends on linux-headers and linux-headers-2.6.24-16-generic got installed instead of linux-headers-2.6.24-19-generic [09:32] Arc_, build-depends can define version number requirements [09:32] I think he was referring to packages built by Pyrex [09:32] flohack, i'm showing no sign of a linux-headers at all [09:32] it's a convience language to make writing Python modules more sane [09:32] heh [09:33] flohack: linux-headers-2.6.24-16-generic is in hardy, linux-headers-2.6.24-19-generic is in -updates [09:33] directhex: ?? Sorry? [09:33] Arc_, is it a problem with the source that pyrex accepts changes with each minor release, or just building pyrex itself? [09:33] we're in the process of replacing it but that'll be at least beta-4. we're the largest package, by a long shot, using Pyrex. [09:33] flohack, jms@osc-franzibald:~$ apt-cache policy linux-headers | grep Candidate [09:33] Candidate: (none) [09:33] StevenK: I enabled automatic upgrades, may that have something to do with it? [09:34] we've hit the glass ceiling on what it can do and had to ask Pyrex's author to extend or fix many things to continue working on it, his code isn't very easy for others to work with [09:34] Ouch [09:34] You reminded me of gcl :-) [09:34] directhex: I get the same (none), what does that mean? [09:34] Its probably the only package in Debian who has a 70MB diff file ;-) [09:34] Arc_, a build-depends looks like this: "Build-Depends: debhelper (>= 5.0.0), dpkg-dev (>= 1.13.19)". you can say "i depend on foo version of bar package. [09:34] NCommander, OOo? [09:34] directhex: awesome. ok. [09:34] flohack, it means no linux-headers package exists [09:35] directhex: And then you FTBFS when a new version of the package is uploaded... [09:35] directhex, OOo's diff file isn't four times the size of OOo [09:35] wgrant, yes! [09:35] NCommander, oh, erm, true [09:35] directhex: But aptitude show linux-headers shows it [09:35] ok so we build a source package and it can be built automatically. we upload the source and binary package to our website, and send the source package to REVU [09:35] directhex: doesn't it indicate that linux-headers is pure-virtual? [09:36] StevenK: How can I tell apt to consider packages from -updates [09:36] flohack, ah, right. PROVIDES. purely virtual. [09:36] "we" being upstream - what's the timeline or process involved in getting it into universe from there [09:36] StevenK: -updates are in sources.list for main and restricted [09:36] Arc_: a couple of months unless you can get people interested [09:36] flohack: If -updates is enabled, it should just work [09:36] Arc_: longer if no-one wants to review it [09:36] james_w: that comes back to my question of if there's a MOTU-Python team [09:37] hi everyone [09:37] Arc_: there is sort of one, yes. [09:37] % apt-cache policy linux-headers-generic | grep Candidate [09:37] Candidate: 2.6.24.19.21 [09:37] flohack: ^ [09:37] StevenK: According to policy, linux-headers-2.6.24-16-generic is only in hardy/main, but linux-headers-2.6.24-19-generic is in hardy-updates/main and hardy-security/main [09:37] should we be talking to the people in that team now? [09:37] I don't think so [09:38] Arc_: Restricting your audience seems counter-productive. [09:38] StevenK: But dkms cannot depend on linux-headers-generic, because I may have linux-image-server installed [09:38] There's little point going to MOTU sub-teams, as they don't really exist. [09:38] I'm not talking about restricting audience, just talking to the people most likely to be interested in reviewing the package [09:38] flohack: Sure [09:39] StevenK: I just don't get why linux-headers does not install the latest version, though it is avaiable, and linux-headers-generic would choose it [09:39] I'd say get it on REVU and then ask for reviewers here, that's your best chance of finding someone interested [09:39] or on the mailing list even [09:39] ok [09:39] flohack: I suspect that it is because linux-headers can't tell which flavour you want. [09:40] now I've been told a few times about this cutoff time for 8.10; does this mean that new packages only get added to the next release, or can they be added to previous/current releases? [09:40] wgrant: But it chose the correct flavour (-generic), just the wrong version [09:40] flohack: Oh. [09:40] That's odd. [09:40] Arc_: only to the next release, but you can request a backport once it is in [09:40] Arc_: only to the next. [09:40] wgrant: And it essentially breaks dkms [09:41] ok so we'll need it on our download page regardless then [09:41] or if it's zomgimportant, you may be able to get a feature freeze exception for it [09:41] But it's not zomgimportant, and it's non-free, so chances are slim. [09:42] so... sponsoring [09:42] * dholbach dives in [09:42] wgrant: since your opinion is not universally held and of a contraversial subject, it'd seem prudent to say "I believe it's non-free" rather than stating it as fact. [09:43] we're in beta, and will be for the next few months up until our API freeze, but we have Ubuntu users asking for compile/install help all the time [09:44] Do we know why a controversial licensing decision is being discussed in private by the CC and TB? This feels wrong. [09:45] so it doesn't turn inot a flamewar? [09:45] Perhaps, but it needs discussion. [09:45] and because consensus will never be reached on the subject [09:45] wgrant: it has been discussed, in the larger community, for almost a year since the license's release [09:45] Arc_: "the larger community"? [09:45] the free software community. [09:46] And further ideas why linux-headers seems to be broken? [09:46] Any [09:46] the free software community don't make decisions on DFSG freeness [09:46] no, apparently random people who happen to be subscribed to debian-legal do, but I digress. [09:47] whilst you can argue the toss for a long time, the line gets drawn in the sand at some point. and that line may differ for different people [09:47] in any case [09:48] ok so by the policies that exist, we will not be included in any Ubuntu repository until at least 8.04, correct? [09:48] s/8/9/ [09:48] ah yes, sorry. 9.04 [09:48] so this answers my question as to the need for us to offer the Ubuntu packages directly from our download page [09:49] once included, how are version bumps handled? [09:49] Arc_: consider a PPA instead of a download page [09:49] PPA? [09:50] Arc_: Personal Package Archive [09:50] Arc_: see www.launchpad.net [09:50] Consider that using PPAs encourages users to remove their security. [09:51] ... ok, is there a way to allow Ubuntu users an uncomplicated way to click on a link on a website to get the package? [09:51] wgrant: How do you figure a PPA is less secure than a download page on an arbitrary website? [09:51] or what advantage is there to a PPA over a direct .deb download? [09:51] Flannel: Personal apt repositories can be signed. [09:51] HTTPS can be used for non-apt downloads. [09:51] Plus non-apt downloads are harder to exploit, as they don't automatically update. [09:52] Arc_, version bumps require updated packages to be submitted to the appropriate places, see the MOTU guide on the ubuntu wiki [09:52] Arc_, as for 1-click, only for in-repository things [09:52] wgrant: PPAs don't do the whole key thing? Thats a rather poor implementation. [09:52] what is the process for a user to add a PPA? [09:53] Arc_, have a launchpad.net account, click a button. done. [09:53] so the user would need to have a launchpad account to add a PPA? [09:53] I mean, add an existing PPA to their system [09:54] Flannel: Correct. This is a severe problem. I can just poison somebody's DNS server and execute my code. [09:54] Arc_: No, anybody can add them easily. [09:54] ... [09:54] ara, oh, that. click a couple of places. essentially a line needs adding to /etc/sources.list* by hook or by crook [09:54] Arc_: One needs a Launchpad account to *create* a PPA, not to use one. [09:54] I'm trying to understand this process. I've seen .deb packages, in that they launch the package installer that requests verification and it's done, so that's easy enough [09:54] Arc_: You, as the publisher of the sofware need an launchpad account. You create a PPA, upload your package and provide the user with the URL to the PPA [09:55] Arc_, the most common cited methods are running a wget line in a terminal to add it to the right place, there's a clicky interface to add repositories too [09:55] https://launchpad.net/~banshee-team/+archive contains some sample instructions [09:55] is there a way, akin to the package installer, to allow the user to click a link on a website to add a PPA? [09:55] Arc_: No, that would be a horrible security risk. [09:56] ok so what is the most GUI way for them to do that? [09:56] Arc_, not in ubuntu. other distros do it. [09:56] System->Administration->Software Sources, click a button the name of which I forget, and enter the line shown on +archive. [09:57] wgrant: it's all a security risk, with it not being audited. [09:57] and in the repositories. [09:57] wgrant: so, take the most convenient option? [09:58] ok so this is less convient than clicking on a .deb download [09:58] Arc_: But it allows you to push updates as well. [09:59] Arc_, yes. but it DOES mean the user gets alerted to updates [09:59] that's true [09:59] with luck beta4 will get into 9.04 anyways [09:59] btw, how would that work - having the package in two repositories [09:59] Arc_: You could simply write a wrapper script which the user can execute. But please provide the link to the PPA as well, so security concious users can add it manually [09:59] nevermind that was a stupid question. [09:59] The top version wins. [10:00] the PPA wouldn't apply to 9.04 in any event [10:00] ok. [10:03] I assume that the technical board then decides what gets from universe -> main, if we went that route [10:03] no, the main inclusion team does that. [10:04] and the release managers decide if the applications get on the cds. [10:04] on what basis is that decision made? [10:04] so, both teams. [10:04] why would you get included in main? no offence, but i see absolutely no way a python 3d engine is useful for ubuntu main, and worth admin overhead for canonical to support [10:04] The TB's powers aren't often invoked. [10:04] directhex: Precisely my thinking. [10:04] Arc_: what canonical wants to support, and what gets put on one or more of the cds / dvd's / etc, afaik. [10:04] because for regular, home users, games, and especially educational software, is important. [10:05] And what rdepends does it have? [10:05] Arc_: how big is it? [10:05] Hobbsee: given that most of the deps are already included with Gnome, not very. [10:05] Arc_: "not very" is not a quantitative answer? [10:05] Arc_: *r*depends. Reverse depends. [10:05] a few megs [10:06] That's huge. [10:06] * Hobbsee wonders what would get thrown off the cd, to add a 3d gaming engine. [10:06] plus games, i guess. [10:06] openoffice. ;) [10:06] I'm not suggesting CD inclusion. [10:06] laga: usually, people want an office suite. [10:06] Arc_: then why do you want it in main? [10:06] Arc_, so why are you suggesting main? [10:06] Arc_, other than cd inclusion, main has no real benefits for users [10:07] directhex: commercial support, too. [10:07] I can assure you that Canonical won't want to commercially support Joe Random's 3D game for 3 years. [10:07] Hobbsee, for some random 3d engine? [10:07] dholbach: did you ping me? [10:07] wgrant, not even joe random's game. the engine for joe random's game. [10:07] directhex: probably not, but i was answering in the general case. [10:07] directhex: The only reason that the engine would be there would be if a game was there. [10:07] bdrung: not that I know of - we were talking about harvest and I spoke about the branch you're working on [10:08] Arc_: Why not simply follow the process. Get it added to universe. Properly maintain it for at least one cycle. Then create a main inclusion report, if people are convinced that it is essential package then it will be moved to main [10:08] slytherin the diplomat [10:08] slytherin: I'm not saying otherwise, just asking questions and getting harsh feedback to my questions [10:08] dholbach: this channel was highlighted, but the log only contains 500 lines, so i did not know what that was. [10:09] we're in beta, the only games we have are a few in our examples/ directory, so this is all very speculative, but our aims are a lot higher than serving one game. [10:09] bdrung: yeah... people are talking a lot in here ;-) [10:10] we have a non-profit corporation formed and putting through 501(c)(3) paperwork around this project, there's nothing small about what we're doing. [10:10] Arc_: cool, good luck. [10:10] hopefully there will be some good games, which you can get, along with the gaming engine, in universe for intrepid+1 [10:11] dholbach: yes. ;) if i would try to follow up, i would sitting here till tonight with reading [10:11] Hobbsee: and the firefox plugin for it as well, yes. [10:11] (or multiverse, if it's deemed non-free due to the requirements) [10:11] Arc_, nobody's criticizing your project, but we're failing to understand why you need inclusion in main. what do you perceive as the benefit? [10:11] directhex: isn't it all hypothetical questioning? surely the archive admins should deal in the licencing questions first, else it will be moot. [10:11] we'll not be included in multiverse. [10:12] Why not!? [10:12] It's better being in multiverse than not being anywhere. [10:12] wgrant: developer's choice? [10:12] wgrant: it's a legitimate choice... [10:12] Hobbsee: Yes, but I am interested in the rationale. [10:12] it's poor marketing [10:12] I see main as tools critical to the functioning of an Ubuntu system. So if universe / multiverse applications are not there - the system should still function. [10:13] stefanlsd: that's the idea, yes. [10:13] i see main as what goes on the CD [10:13] and frankly, a 3d game with art assets won't fit [10:13] dholbach: did you reviewed my branch? [10:13] directhex: it is more than that, though. it might get onto the dvd, for eg. [10:13] bdrung: no, sorry [10:13] There's plenty of main that isn't on the CD. [10:14] bdrung: does the handler work now? [10:14] we are an extremely pro-software freedom project. we explicitally leave out rendering features that are not implemented on free software drivers, we use only patent-clear algos and codecs, etc [10:14] stefanlsd: newly-installed systems contain only stuff from main, and function fine [10:14] RAOF, how much of it as a result of build-deps and the like though? [10:14] directhex: you are missing details. it does not matter if a game is included, the firefox plugin may be. [10:14] Arc_: not if it depends on the game itself, it won't. [10:14] Main _used_ to be the set of all things officially supported by Canonical, but isn't anymore. [10:14] Arc_: Im still not sure what you have against universe or multiverse? [10:14] Arc_: or build depends, as it'll never build. [10:14] "we'll not be included in multiverse" - if you're a free software project, there's nothing you can do about that ;) [10:14] this engine aims to provide a free alternative for macromedia flash, for online 3d gaming, which is one of the main reasons we upgraded to the AGPLv3 [10:15] Arc_: Just curious, I missed the point where you mentioned the name of your non-profit, engine, game... [10:15] dholbach: it should. it some configuration thing here. your branch has the same issue. so i assume that did not break something [10:15] dktrkranz is busy triaging the sponsoring queue as well - nice :) [10:15] stefanlsd: I have nothing against universe. [10:15] flohack, http://www.pysoy.org/wiki/License [10:15] flohack: PySoy [10:15] Cheers [10:15] bdrung: I'll review a few packages now, then check out the harvest changes again [10:15] bdrung: (Feature Freeze soon) [10:16] Arc_, okay, the browser plugin thing makes a little more sense [10:16] dholbach: i know. i have to check 214 files for their licenses. [10:16] * didrocks hopes strongly someone will see its bitesize change on the sponsor list one day (last one before removing an NBS) ^^ [10:16] Arc_, here's the thing though. what use is a browser plugin on a cd - if you have the internets to use the plugin, you have the internets to install the package from universe ;) [10:16] bdrung: enjoy :-/ [10:17] dholbach: but rl tasks are also in the queue [10:17] directhex: this is vaporware talk, we have parts of the mozilla plugin in place in our repository (py-mplug as it was previously called), mostly from a previous GSoC project, and we have a lot of work towards integrating, but it's far from finished [10:17] * Hobbsee notes that nothing in main can depend, or build depend, on anything from universe either. [10:17] which might cause trouble, if you do eventually try to get parts of it into main. [10:17] Arc_, so for now, the first thing to worry about is making a quality source package, followed by filing for inclusion in universe [10:17] but that is our goal, and the browser plugin *in the current technical direction* depends on the engine itself, rather than duplicating it, even though it doesn't execute downloaded Python code for security reasons. [10:17] Hobbsee, tell me about it :/ [10:18] directhex: heh :) [10:18] Hobbsee, on a related note, you don't have the awesome power to ack a merge do you? [10:18] directhex: well no, first thing is getting beta3 out the door, but the source package will be part of that process. [10:18] directhex: i have most powers :P [10:18] directhex: it's a question of whether i'll use them, and the current answer is no (i'm about to head out) [10:18] :'( [10:19] well, merge bug at https://bugs.launchpad.net/ubuntu/+source/monodoc/+bug/256853 [10:19] Launchpad bug 256853 in monodoc "[merge request] Please merge monodoc 1.9-1.2 from Debian Unstable" [Undecided,Confirmed] [10:19] at least i can scroll up & use it to bug you later [10:19] directhex: I never said inclusion on the CD was a goal, I can only imagine the sort of politics that go into that. Firefox could, however, be setup to automatically grab the engine and the plugin when it hits a site that requires it [10:19] Arc_: That can be done regardless of component. [10:19] Arc_, yes, but i think that actually supports universe/multiverse [10:19] See Flash, for example. [10:19] I understand. [10:20] Arc_, i think it's an ubufox enhancement to install plugins from packages rather than from mozilla.com search [10:20] it would take me a long time to explain the entire situation and our plans to your satisfaction, all I'm doing now is gathering more information though not trying to convince you of anything [10:20] directhex: *nod* good to know [10:21] Arc_, assuming i'm remembering the specifics correctly, then you'd simply file a bug against ubufox with a patch to add your package name to the mimetype->package mapping [10:21] does ubufox currently support protocol->package mapping as well? [10:22] there's a debate over which method is preferable [10:22] Defining one's own protocol sounds like a bad idea. [10:22] i don't know enough about ubufox [10:23] RainCT, Laney: Changes made to ubuntu-dev-tools and pull-lp-source - please make sure that everything works OK. [10:23] it's a jono! [10:23] wgrant: we already are developing our own protocol, it's essential. it will work via ICE/UDP, initiated either through XMPP (if running a local game) or HTML (if running from a remote server) [10:24] the plugin mechanisms are far from decided on, I'm just asking :-) [10:26] in the engine model, the only difference between local and remote execution is where the Python MainThread is running; instead of changes being made directly in memory, they're sent as action/state events over the network, just as a remote server keeps client states in sync [10:27] dholbach: aah. thanks for sponsoring gpa. i've been trying to get that right for like a month! [10:28] anytime :) [10:29] * directhex waves his little monodoc flag again. zee patch is only wafer thin! [10:34] something I'm still confused about, if not a code review what is the REVU process for? [10:34] Arc_: Package review. [10:35] Arc_, bad packages damage systems [10:35] ok [10:35] Arc_, one bad "rm -f" in prerm and boom, lots of angry users [10:36] ha, still no sandbox in apt-get eh? [10:38] how do you sandbox making changes to your system? [10:38] chroot? [10:38] Gentoo does this [10:39] portage "installs", with all package scripts and such, then tests these against what's currently installed and only then (safely) merges [10:40] https://wiki.ubuntu.com/UbuntuDevelopment/UsingDevelopmentReleases [10:41] Arc_: Packages need to be able to execute arbitrary commands. That cannot be sandboxed. [10:42] * directhex sandboxes "ldconfig" [10:43] And if I can get a package onto your machine in the first place, I can get my code onto your machine inside the package, not just in the maintainer scripts. [10:43] it's not about security, just safety [10:45] even with sandboxing, problems can occur [10:45] if a prerm keeps failing due to poor programming, how do you remove a package? [10:47] what do you mean? [10:49] prerm is executed before removign a package - e.g. disabling an apache module before removign it. prerm fails, so the package manager stops [10:49] now, how do you remove that package? [10:49] AFAIK, Gentoo doesn't have the same concept of a prerm [10:50] Gentoo records which files were added, along with hashes to ensure the files were not overwritten (ie, a manual compile/install of a later version), and just deletes them [10:51] So does dpkg. [10:51] leaving it to the user to add things to config files to make them work, and remember to remove them afterwards [10:51] But it might need to perform other actions to fully remove, or stop the server before removal, or removing the user's root filesystem just to be nasty... [10:51] dpkg handles adding/removing distinct config files, sure, but there are loads of cases more complex than just "rm" [10:52] ok [10:57] warp10, WOOO, I LOVE PITTI! [10:58] NCommander: WE TOO!!! :P [10:59] Yet another LP icon [11:00] NCommander: :D [11:00] I just want that MOTU icon [11:00] Then life will be good [11:01] NCommander: Not core-dev? :-P [11:01] NCommander: or worse, depending on the point of view :) [11:01] Not yet [11:01] Well, after the archive split [11:01] I'll be able to upload to xubuntu and universe/multiverse (if I have MOTU) [11:02] so core-dev can wait until I've been here long enough to prove I'm not going to break the archive [11:02] Were you planning on? :-) [11:02] Not intentionally [11:03] Some day, I shall become an archive admin, and then I can finally rest (for two minutes until the NEW queue gets flooded) [11:04] dholbach: handler.py works correct. activate_opportunity and deactivate_opportunity did not update the files in data/packages because they did not have write access [11:05] ah ok [11:06] dholbach: there should be a log entry in logs/* if writing a file fails [11:06] bdrung: sounds good [11:09] lol [11:09] hum... who is allowed to archive packages on REVU? [11:10] hey guys, is there a way to get warned on comments on REVU ? [11:10] or a rss feed ? [11:10] dholbach: MOTU should be able to do it. [11:10] jpds: should there be a link on the mainpage? [11:10] jpds: or on the package page? [11:11] the "actions" column is empty in my case [11:11] and I'm logged in [11:11] dholbach: did you merged accounts? [11:11] DktrKranz: merge two launchpad accounts? [11:11] REVU accounts. I see your "old" one only [11:11] dholbach: "Merge REVU Accounts " at the top of the index page. [11:12] ahh ok [11:12] once you are logged in, click on "merge revu accounts" and you're in :) [11:12] nice [11:12] thanks guys! :) [11:12] you're welcome :) [11:13] dholbach: please inform me before you review my branch [11:13] bdrung: will do [11:14] DktrKranz: you're busy reviewing now :) [11:14] I just did a bunch myself [11:15] and we're slowly gaining ground again :) [11:16] dholbach: I did some this morning, I plan to have a couple in time before FF. I hope archive-admins will process syncs, so queue will go down again [11:18] yeah [11:18] I see there are some advocated packages on REVU too, they deserves a review [11:18] NCommander: I'm around now. [11:19] ScottK, cool. I'm now being tortmented with an FTBFS that occurs on i386/amd64, but not lpia or hppa [11:19] (wrap your brain around that one) [11:19] 106 packages in the queue, nice to see they reduced so much in five days :) [11:21] NCommander: I got one that's on lpia, but not any other arch and it seems to be an arch specific change to configure causes one piece of the package not to get built. [11:21] No, it builds on lpia/hppa [11:22] Fails on amd64/i386 [11:22] LIke I said, wrap your brain around that one [11:22] Right. Mine's kind of the opposite. [11:22] yeah [11:22] But you expect hppa to fail [11:22] NCommander, does it include any arch-specific code for i386/amd64 which is just *wrong*, versus generic code which works? [11:23] and spam your inbox [11:23] directhex, well, if mysql does, then I'm going to loose my mind === dholbach_ is now known as dholbach [11:28] dholbach: Yaay! No slots available. Well done. [11:28] directhex, how goes mono-basic? [11:28] thanks Iulian - luckily it was not only my doing :) [11:29] NCommander, the package is in good shape, and the apparent "correct" behaviour is include bootstrap binaries but document in debian/copyright and ensure those binaries never get packaged [11:29] dholbach: Heh, rock! [11:30] NCommander, mentor's having problems submitting to sid though. [11:30] I noticed [11:30] I've sent two archive admins running and screaming trying to find a sponsor for Debian [11:30] er wait [11:31] oh [11:31] I thought ScottK was an archive admin for some reason [11:31] er [11:31] StevenK, [11:32] NCommander, mono-basic is ready for inclusion. the timing is just poor, with lenny and intrepid freezes. [11:32] YOu still have 24 hours for intrepid [11:32] Upload upload upload! [11:32] NCommander, i think i'll upload a copy to my PPA. i have people asking for it [11:33] StevenK, could you do me a favor and help review mono-basic on REVU? [11:33] NCommander: Less than 24 hours. [11:33] bah [11:33] i think the revu one needs a little updating. let me check [11:33] I need to call in a second favor then [11:34] Iulian: Not necessarily, the exact time of the freeze is rather nebulous. [11:34] who else have fixed random FTBFS before in the past [11:34] ScottK: Oh, I thought its 00:00 UTC. [11:34] DktrKranz, care to review a packge on REVU? [11:35] cody-somerville, otherwise, can you please do it to me as a favor? [11:35] directhex, hopefully someone I pinged will help you :-) [11:36] tacone: pong === bobbo_ is now known as bobbo [11:37] bobbo: re-ping [11:37] NCommander, i'll upload a newer revision [11:37] hey tacone [11:37] directhex, I hope someone answers, but mono scares people mor ethan codeblocks [11:37] bobbo: https://code.launchpad.net/~bobbo/+junk/uploads where's the cronjob ? [11:38] tacone: cronjob? [11:38] uhm. ok. bad wording. where's the code that does inserts in mysql ? [11:39] tacone: I havent got round to writing that bit yet :) [11:39] w00t [11:39] tacone: I just use phpmyadmin at the moment, but I really should write an add upload page [11:39] I crashed a PPA builder [11:39] https://edge.launchpad.net/+builds [11:39] omg [11:40] bobbo: ok, I see. you may be interested in utu then. [11:40] NCommander, what's the right version number to apply to an unreleased debian package? 0ubuntu1, or Xubuntu1 or X-1ubuntu1? [11:40] http://thc.emanuele-gentili.com/utu.php here there's some code that parses the mailing list to find out uploads. [11:41] tacone: ah yeah, its awesome [11:41] tacone: cant find any source though, must ask emgent if he is releasing it [11:41] 0ubuntu1 [11:41] awesome perphaps is too much, but it's nice enough, yes. [11:41] When the Debian version hits, the sync will clobber it [11:42] bobbo: I'll ask emgent, but maybe I have it somewhere. I'll take a look [11:42] tacone: cool, thanks :) [11:48] found the code. [11:48] there's not license on it. I'll ask emgent as a pure formality then send you the code. [11:49] tacone: sure, thanks alot :D [11:50] bobbo: neverming :) I plan to reuse your code as well :-) [11:52] hi folks [11:52] NCommander, okay, Debian-approved if-svn-buildpackage-dealt-with-changed-orig-dot-tar-dot-gz-files-properly-i'd-be-in-sid-right-now upload: http://revu.ubuntuwire.com/details.py?upid=3550 [11:53] NCommander, if that goes in, ubuntu gets a "complete" mono stack for intrepid. monodoc and monotools still await merge acks for it to be up-to-date as well as complete, but better than nothing [11:54] Hey there, I have a question: how are .desktop files with Type=Directory supposed to work? [11:56] Hey sistpoty [11:57] hi Iulian [12:13] Anyone have an EEE pc? [12:13] ScottK: was thinking bout getting one... [12:14] Well we've got a package that needs reviewing before feature freeze and it'd be nice to know if it works. Please hurry. [12:14] ScottK: heh. let me try find a supplier [12:15] RainCT: what do you think about bug #247157? [12:15] Launchpad bug 247157 in ubuntu-dev-tools "dget/dgetlp should have ca-certificates in their Recommends field." [Undecided,New] https://launchpad.net/bugs/247157 [12:24] ScottK: I have one at home.. [12:27] Treenaks: Can you build and test a package for us? [12:28] ScottK: tonight (CEST), yes [12:28] ScottK: you could ask popey as well, he has a stack of Eee [12:28] Treenaks: Please try out the eee-applet that's on REVU currently. [12:31] ScottK: I'll be home in ~6 hours, I'll try to remember [12:33] Treenaks: Great. I should be around. [12:43] hello ScottK [12:43] :) [12:55] hello huats [12:56] devfil: I still don't understand what your README.source on the gtk-kde4 package means? [12:56] ScottK: I dropped it [12:58] devfil: It's still there in the latest one I grabbed from REVU. [12:58] ScottK: are you sure? http://revu.ubuntuwire.com/revu1-incoming/gtk-kde4-0808261730/gtk-kde4-0.8~b1/debian/ [13:00] devfil: My bad. [13:01] That's what I get for unpacking the new source on top of the old one. [13:01] Sorry for the disturbance. [13:08] hi all [13:08] are there a article to made a diff of a package aleady archived? === ember_ is now known as ember [13:15] dholbach: now my harvest branch is ready for merge [13:24] NCommander: which one? === jsg123 is now known as jsgotangco [13:29] thanks guys, I set up our PPA and we'll get our other devs who have committed to maintaining the Ubuntu packages to join [13:30] https://launchpad.net/~pysoy [13:30] Arc_, it's a good place for you to try out things without being committed to the ubuntu release schedule [13:31] yea I agree [13:31] do you know how to add hardy, or to upload to this? [13:32] the most immediate thing I can think of is adding a -dev package that just resolves dependencies for svn builders [13:32] Arc_, you upload packages to your ppa using "dput", right? well, either specify in your dput target (as specified in ~/.dput.cf) an incoming folder with a specific dist in the name, OR specify a generic one and make sure you have a correct first line in your debian/changelog [13:33] ok [13:33] Arc_, so EITHER my dput.cf specifies "incoming = ~directhex/ubuntu/hardy/" and i use that dput target, OR my dput.cf specifies "incoming = ~directhex/ubuntu/" and my package upload's debian/changelog starts with "pkgname (1.0-1) hardy; urgency=low" [13:34] ok [13:34] would pysoy-dev be an appropriate package name that's just a metapackage for resolving dependencies? [13:35] and if so, what version should I choose, given that it's after 1.0-beta2 and before 1.0-beta3? [13:35] Arc_: if you package pysoy then they can use "apt-get build-dep" to install the needed packages [13:36] Arc_, packaging dependencies happen automatically, based on the build-depends of your debian/control [13:36] for now, I'm just looking for a "metapackage" so building from svn doesn't involve manually selecting a dozen+ -dev packages [13:37] Arc_, "apt-get build-dep pkgname" [13:37] Arc_, build-dep pulls in all a package's build-depends === calimer-- is now known as calimer [13:37] oh, what I mean is the package wouldn't actually contain any code [13:38] Arc_, i know what a metapackage is for, but you don't make a metapackage purely for self-referential building on debbuntu [13:38] I don't understand [13:39] I'm just talking about something for now in this PPA to make things easier for the next month or two [13:39] Arc_, then look at Equivs [13:40] and the "ubuntu-meta" source package as a practical implementation of it [13:40] ok [13:41] do you have a URL for version evaluation? [13:41] Arc_: apt-get build-deps will work from your PPA too as long as they have the source (deb-src) repository in /etc/apt/sources.list. You could also provide a target in debian/rules to grab from svn so it's all done via normal package management. [13:41] I guess all that's really needed is for the version to evaluate to less than 1.0-beta3 but it'd be good if it was after 1.0-beta2 [13:42] Arc_, i believe the recommended way to deal with betas is with ~ [13:42] ScottK: is there a way to do that for automatic "svn sync"'s for developers? [13:42] Arc_, i.e. since you want 1.0 beta 3 to be older than 1.0, you need to use ~, e.g. 1.0-1~beta3 is superceded by 1.0-1 [13:43] Arc_: Sure. write a get-svn-source target in debian/rules (analgous to get-orig-source that is often used when there's no usable upstream tarball). [13:43] Arc_, and then, since you want to work on a PPA, you should append ~ppaN to the end, to make sure your PPA version is overridden by the archive vetrsion if it's higher, so that would be 1.0-1~beta3~ppa1 === asac_ is now known as asac [13:44] directhex: but here's the real challenge, we're not talking beta3, we're talking pre-beta3 SVN revision XXX [13:44] Arc_, and (i bet you're loving this) since you don't want to be in debian, technically you can't use -1 in your version name, you're targeting ubuntu so the correct first version for your ppa is (don't choke) 1.0~beta3-0ubuntu1~ppa1. i think [13:45] Arc_, well, svn is easy, you can just use rNNNNN in your version number [13:45] 1.0~beta3~svnXXX-0ubuntu1~ppa1 [13:45] yeah, what james_w said [13:45] and there are worse numbers to have, trust me [13:45] but when beta3 is released, it should evaluate as being a greater version than the svn before it [13:45] would that do it? [13:46] flash plugin version 10.0.1.218+10.0.0.525ubuntu1~hardy1+really9.0.124.0ubuntu2 for example sucks a bit [13:46] 1.0~beta3 > 1.0~beta3~svnXXX [13:46] Arc_, ~ lowers the version, so... what james_w said [13:46] gotcha [13:46] ~ sorts lower than '' [13:46] so, who wants to advocate mono-basic on revu? [13:46] is svnXXX the convention or rXXX [13:46] go on, everyone loves visual basic.net [13:47] Arc_, i've seen both [13:47] ok [13:48] Arc_, just promise me you won't do the most boneheaded thing i've seen, and use git hashes [13:48] and "ppa1" is a convention refering to the first PPA that packages it? [13:48] I promise ;-) when we're ready to go git, we won't be doing trunk revisions anymore in any case [13:48] Arc_, typically, you want the last bit of a package version number to be something you "control". if the package is on your ppa, then you need the freedom to increment the package version whilst keeping the rest the same [13:48] Arc_: Yes. [13:49] Arc_, "ppa" is the common, if flawed, thing most people add to the end. [13:49] gotcha. [13:49] directhex: Why do you say flawed? [13:49] Arc_, like i said, the main desire is to make sure that if you manage to get 1.0~beta3~svnXXX-0ubuntu1 added to ubuntu "proper", it replaces 1.0~beta3~svnXXX-0ubuntu1~ppa1, hence using the ~ [13:50] ScottK, 1.0-1~hardy1 lower than 1.0-1~ppa1 [13:50] Right. [13:50] Good point. [13:50] Actually I usually use ~hardy1~ppa1 if I'm targeting something other than the developmental release. [13:50] so this would be valid; 1.0~beta3~r1348-0ubuntu1~ppa [13:51] It would be valid, but directhex makes a good point. [13:51] ScottK, it'll remain flawed until queer quetzal [13:51] what is the -0ubuntu1? [13:51] I understand ubuntu means its ubuntu-specific, not debian [13:51] but 0 and 1 around it? [13:51] Arc_: I'd recommend 1.0~beta3~r1348-0ubuntu1~hardy1~ppa1 if you're building for Hardy. [13:52] Arc_: 0 is the Debian revision and 1 the Ubuntu revision [13:52] Arc_: The 0 makes sure it's less than the first Debian revision and the 1 is the Ubuntu revision number. [13:52] Arc_, ubuntu package versions reflect their place in the debian heirarchy. the first debian version of something is 1.0-1, so if ubuntu's package is based on that one, it becomes 1.0-1ubuntu1. if it's based on a pre-debian (or never-debian) package, it's 0ubuntu12 [13:52] 1 [13:52] ok [13:53] ScottK, we could add some "+" to that to make it more exciting, surely? [13:53] ScottK, i mean, four tildes? a bit one-sided [13:53] OK [13:53] Arc_, unfortunately, you just happen to have picked every single "non-simple" case for versioning your package at once [13:54] ScottK, prepend 0.99+! [13:54] 1.0~beta2+r1348-0ubuntu1~hardy1~ppa1 if you prefer. [13:54] directhex: Not all of them. [13:54] I like that better actually [13:54] ScottK, okay, no reverts. most of them [13:54] what does the 1 at the end of ppa represent? [13:54] Arc_, your first revision [13:55] Why is the hardy1 coming first? [13:55] Arc_, if you mess up the packaging, but the software is the same, then you increment that number [13:55] That's your revision number so you can increment that if you need to fix something with another upload. [13:55] wgrant: so that backports work [13:55] wgrant, cheap workaround to ScottK, 1.0-1~hardy1 lower than 1.0-1~ppa1 [13:55] i find appending ~dhx1 easier ;) [13:55] ok then why hardy1? [13:55] directhex: Which isn't so great if you want to backport to Dapper. [13:56] ScottK-laptop, fortunately, i only put things in my PPA ineligible for official backporting anyway [13:56] I mean why the 1 at the end of hardy? [13:56] ScottK-laptop, and my dapper repo is frozen [13:57] Arc_, the first "official" backport to hardy would have ~hardy1, which could be incremented if that official backport were updated [13:57] Arc_, so the idea is trying to work out where you want to slot in [13:57] ok [13:58] Arc_, if you want to guarantee being replaced by newer packages in the main distro, you need your version to be "older" than anything potentially official, whilst still replacing genuinely older versions [13:58] you get used to it [13:59] so why not hardy0? [13:59] or go mad and work on visual basic things. one or t'other. [13:59] since its not an official backport [14:00] and isn't that redundant with the archive version in any event? [14:02] Riddell: Filed as Bug 261840. I'll send mail to kubuntu-devel asking for feedback. [14:02] Launchpad bug 261840 in ubuntu "Please pocket copy KDE 3.5.10 from hardy-backports to hardy-updates" [Undecided,New] https://launchpad.net/bugs/261840 [14:02] there are three* places a given package can be available, excluding a PPA. if we say 1.0 is in the main repository for intrepid, then 1.2 is in the main repository for jilted jackalope, then 1.2 can only end up available in intrepid via the backports repo, updates repo, or a ppa (and you won't be in updates without good reason). the version that comes in via backports/updates needs to be older than the version in jilted jackalope, [14:02] to ensure it's replaced if you upgrade your distro [14:03] oops. Wrong channel. [14:03] Arc_, so i actually think you're right about using hardy0 instead of hardy1 in your ppa version, since you're not "based on" hardy1 [14:03] [OT] Any idea whom I should contact for enabling my @ubuntu.com email alias? [14:04] Since hardy1 would be the first backport, as long as it's lower than that, it doesn't matter by how much. [14:04] tuxmaniac: I think that's done automatically [14:04] Arc_, in the event that the base software is the same version (1.2 in the example), you need to try and aim your package at the right place - either higher or lower than potential backports, but always lower than the next "full" release [14:05] ScottK, i think hardy0 is a better convention to teach for PPAs. since it's NOT based on hardy1, i don't think hardy1 should be in the name. see what i mean? [14:05] i know it doesn't "matter", but it seems like more justified practice [14:06] By that rationale it should be ubuntu0 too. [14:08] depends if you're also the packager, i suppose [14:08] hmm. 1.0~beta2+r1348-0ubuntu0~hardy0+ppa1 [14:09] because then a PPA "based on" a main version will superscede it correct? [14:11] Arc_, buggered if i know, i got lost halfway through [14:11] ;) [14:11] heh ok [14:13] essentially it's all guesswork until a version enters the archive [14:13] got it [14:14] and there's no "official" rule on PPA numbering, especially given how much some people dislike them for assorted reasons. so if you're aiming to get 1.0-foo-bar-baz-boz into the archive, until that point, just use 0.99-1 in your ppa and say screw it. [14:14] (don't quote me on that) [14:15] well since our deps change it's good to have the rXXXX in there [14:16] well, version it how you like, just try not to get a headache [14:16] yea that format is easy enough to follow [14:17] i think though that "1.0~beta2+r1348-0ubuntu0~hardy0+ppa1" is indeed a perfectly valid way to number the absolute first version of a dvn revision of a beta of a package, which is first appearing in a PPA [14:21] rofl [14:21] alright. [14:22] last question, the mention of svn downloading/building for the source [14:23] dholbach: do you know what the jokosher-0.10/debian/jokosher.sh is for in the diff of the 0.10 package? [14:24] can a specific revision be specified with get-svn-source? [14:24] the source repository is http://svn.pysoy.org/trunk/pysoy thats easy enough [14:25] Arc_, yes. you write get-svn-source yourself - it's a target in debian/rules makefile [14:25] Arc_, so you can even be smart, and make it parse the revision to download frmo debian.changelog [14:25] debian/changelog [14:25] let me find a simple example [14:29] man, can't find one. we use it for get-orig-source, but that's ftp based. [14:29] just to clarify, with the PPA added as a source, "apt-get build-dep pysoy" would just compile all the dependencies, and "apt-get source pysoy" would build the deps *and* download the source to ./ right? [14:30] it wouldn't buil dthe deps. [14:30] it would download the source. [14:30] and s/compile/download and install/, yes. [14:30] I'd imagine it'd take a url but the revision # is the unknown [14:31] Arc_, "apt-get build-dep pysoy" will install all the packages listed in the Build-Depends: line of your pysoy source package's debian/control [14:31] ok so if you want both the deps and the source, both commands would have to be executed? [14:31] Arc_, "apt-get source pysoy" will download & extract the source package into the current folder [14:31] Arc_, so both steps needed, yes [14:32] Hobbsee, you're back! [14:32] yea and that would mean the equiv of "svn co http://svn.pysoy.org/trunk/pysoy" [14:32] complete with .svn directories? [14:32] directhex: yes, but i'm tired, and i'm unlikely to be able to type my passprhase... [14:33] Hobbsee: should we help you? :) [14:33] geser: yes. SPONSOR PACKAGES! NOW! SPONSORSHIP QUEUE! [14:33] geser: REPORT FOR DUTY IMMEDIATELY! [14:34] Hobbsee: too tired for an archive admin task as well? [14:34] Adri2000: much [14:34] ok :( [14:35] so nobody feels like an ack for my monodoc merge in main? no? [14:35] geser: does [14:35] how about some nice stress-free advocation on mono-basic in revu. everyone loves visual basic. [14:35] Hobbsee: since when can I ack merges in main? [14:35] directhex: do you know a URL where get-svn-source is documented? [14:36] Arc_: there is nothing to document, it it whatever you want it to be :) [14:36] Hobbsee: and I don't have time either as I need to learn for two exams this week (tomorrow and Friday) [14:36] I don't understand [14:37] Arc_, debian/rules is a makefile. technically, it can do whatever you would want a makefile to do [14:37] oh [14:37] so what activates get-svn-source vs get-orig-source? [14:39] Arc_, i don't think (someone else may correct me) either is explicitly called by anything automatic [14:39] Arc_, you can use them yourself, for convenience, to make collaborative work easier [14:39] Arc_: the name get-orig-source is a convention [14:39] s/is a/is just a/ [14:40] ok so what does "apt-get source pysoy" do in that case? [14:40] Arc_: download the source from the Ubuntu archive [14:40] (that is, the .dsc, .diff.gz and .orig.tar.gz) [14:40] Arc_, downloads pysoy.dsc, pysoy.diff.gz, and pysoy.orig.gz, from the ubuntu archive (or ppa) [14:40] Hobbsee: Use gnupg-agent [14:41] ok so whats the point of specifying get-svn-source? [14:41] Arc_, get-orig-source is a popular convention for allowing you to generate (or download) the orig.tar.gz [14:42] RainCT: Actually apt-get source downloads the highest version listed in any deb-src repo, Ubuntu official or not. [14:42] "allowing you"? [14:42] do you mean allowing you, outside the context of apt-get, or allowing you to specify an apt-get command to do this all automatically [14:42] Arc_, essentially, outside the context of apt-get [14:42] Arc_: The idea would be to have a target in debian/rules so you can make -f debian/rules get-svn-source and have it all magically arrive ready to use. [14:43] Arc_: it has nothing to do with apt-get. it's just to get a new .orig.tar.gz when there's a new upstream version/revision [14:43] Arc_, as an example, for working on mono-basic packaging, mono-basic packaging work is stored in svn. mono-basic upstream is in a zip file on an ftp server [14:43] ScottK-laptop: well, yea [14:43] Arc_, i check out the mono-basic tree from svn, run debian/rules get-orig-source, and it generates a mono-basic orig.tar.gz for me [14:43] RainCT: Since he's talking about a PPA, it's relevant. [14:43] Arc_, i unpack it, add the debian/ folder in, and run debuild -S -sa. that generates the dsc and diff.gz against the orig.tar.gz [14:44] ok so this really doesn't save time since it still requires pre-tarring the source code [14:44] Arc_: use get-svn-version if you need to get a version (from upstream) which you want to upload into the archive (or ppa) and "apt-get source" later to download it from the archive [14:44] Arc_: The point is to write a target in rules to automate all that for you. [14:44] Arc_, it saves packaging time, since it means your get-orig-source can do that work for you === x-spec-t is now known as Spec [14:45] Arc_, so you can make your debian/rules work out the svn revision you want based on the changelog, and check it out, clean it, and compress it into an orig.tar.gz ready for use in the archive [14:46] Arc_, it makes updating your packages much easier [14:47] Arc_, the thing about dpkg packages is all three* files relating to a package need to come from the same place. you can't have a source package without the source [14:47] trust me, dealing with NOSRC packages on suse sucks [14:52] tacone: You here? [14:52] tacone: I got an error when upgrading to the latest memaker [14:52] yes here [14:52] pastebin it [14:52] am doing [14:53] http://paste.ubuntu.com/40915/ [14:53] ?!?. [14:53] my patch doesn't get applied ? possible ? [14:53] let me see [14:53] Did you test install the package you uploaded? [14:53] sure I did [14:54] weird [14:54] on a clean wm [14:54] not weird, is about python versions [14:54] * Laney nods [14:54] you have something different from the standard. the problem was known and patched [14:54] laszlok: will check in a bit and let you know [14:54] I adapted the patch. let me check and correct. [14:55] This is a very dirty environment ;) [14:55] My installation has been dist-upgraded through loads of revisions [14:55] releases* [14:55] that's why you have an old python [14:55] probs [14:55] as for me, I proposed to depend on a newer python. upstream never tested with old python, this I am sure [14:56] Daviey or superm1|away: Why did you make every single Ubuntu developer a member of Mythbuntu (and thus get mail they really don't care about)? [14:57] ScottK: Jonathan Patrick Davies → MOTU → Ubuntu Development Team → Ubuntu Development Team (bugmail catching gateway) → Mythbuntu [14:58] ScottK: I blame the gateway, and thus RainCT. [14:58] I was coming to that. [14:58] But why period. [14:59] tacone: Just bumping XS-Python-Version fixes it [14:59] geser: there? few questions about libjboss-cache [14:59] * Laney eyes whoever put All in the first place [14:59] sure [14:59] RainCT: What the heck is this ubuntu-dev-without-bugmail thing and why wasn't it discussed? [15:00] Laney: nice, but it would fail anyway with older python versions [15:00] so we either depend on python2.5 or get the patch applied [15:00] patch: ls debian/patches/001* [15:01] ScottK: you get mythbuntu mail? :S [15:01] tacone: Changing XS-Python-Version gets the right deps in [15:01] Depends: python (<< 2.6), python (>= 2.5), [15:01] (but why isn't that patch applied? that would seem to be the right fix) [15:02] ScottK: ubuntu-dev was added as a member of mythbuntu so that it can commit to its branches (many packages are maintained in bzr barnches owned by mythbuntu) [15:02] RainCT: http://paste.ubuntu.com/40919/ [15:02] Laney: https://bugs.launchpad.net/ubuntu/+source/memaker/+bug/214401 [15:02] Launchpad bug 214401 in memaker "Installation of 0.9.4-0ubuntu1 failed" [Undecided,In progress] [15:02] ScottK: but we created ubuntu-dev-without-bugmail which is supposed to catch all the mail (sending it to its contact address) [15:02] Laney: that's the thing, I am loooking to understand why it doesn't get applied [15:02] It doesn't [15:02] geser: Fixing current package is too much work. Even after that I am not sure what all reverse-build-depends will need to be modified. [15:02] 1. I can update it to 2.1.1 version with very minimal fixing required changes. But then should I change source package and binary package names from *cache1 to *cache2? [15:03] RainCT: I get "New Mailing List for Mythbuntu Bug Team" and I bet I'll get the merge request mails too. [15:03] ScottK, jpds: seems like only bugmail is catched, but not other info mails [15:03] Laney: I can confirm it doesn't get applied :( [15:03] slytherin: did the API change? [15:03] tacone: Is this the only 2.4 problem? Will the package work apart from this issue? [15:03] RainCT: Please can we think this stuff through BEFORE we start spamming every single Ubuntu developer. [15:04] Do you know why it wasn't applied upstream? [15:04] Laney: yes it does. I had no problem with that. [15:04] RainCT: Please undo whatever it is you have done, figure it out, and then try again. [15:04] geser: I couldn't find any direct statement about API change. [15:05] beh.. this will need changes in Launchpad then.. [15:05] tacone: I'd better get back to work, but I'll have a look later if you don't figure it out [15:05] Seeya [15:05] thank you [15:05] slytherin: is the new version a drop-in replacment? if yes, keep -cache1 [15:06] Oh, DktrKranz: Do you think the nanoweb problem you mentioned is a blocker? I'd like to have the php4 deps in for potential backporting if you don't mind. It doesn't cause a problem for Intrepid. [15:06] Bye! [15:06] slytherin: what about the reverse-build-dependencies? do they build/work with the new version? [15:06] RainCT: I will actively object to being classified as a member of a Mythbuntu team. I'm not involved in the project. === jsg123 is now known as greeneggsnospam [15:06] dholbach: also it looks like the import from debian used the control file from 0.2. In 0.9 we dropped dependencies for python-alsaaudio, librsvg2-common, python-gnome2, and changed gstreamer0.10-gnomevfs to recommended package [15:06] * RainCT writes a mail to ubuntu-devel [15:06] geser: Drop in replacement - it should be. I haven't tested reverse-build-depends. I don't have a package ready yet. I just checked if it compiles with whatever packages are available currently. [15:07] RainCT: Which should have been done BEFORE. [15:07] laszlok: will check into that as well [15:07] * laszlok hugs dholbach [15:08] * highvoltage hugs dholbach too (just randomly) [15:08] :-) [15:08] slytherin: ok, what about FF in a few hours? sounds like it would be best to file a FF exception so you don't need to hurry with packaging it [15:08] * dholbach hugs y'all [15:08] * directhex STILL awaits mono-basic love & hugs [15:09] feature freeze fills me with fear and sadness! [15:09] geser: I should have a package ready within 2 hours when I go home. That is about 5 hours from now. [15:10] emgent`: /qui [15:10] ups [15:10] :P [15:11] geser: What I can do meanwhile is still work on current package and make it build, irrespective of how many class files are built. So we can proceed with our build rounds. === jsg123 is now known as greeneggsnospam [15:13] geser: And that reminds me, some java files are not present in 2.1.1. So yes it is an API change. I will change source and binary package names and have a new changelog, is that fine? [15:14] slytherin: yes, in that case it's better to rename it [15:15] but I'm not sure if it needs a full review through REVU or still counts as a new version update [15:16] I'm trying to package a new library. I created the skeleton using dh_make (adapted the necessary bits following the PackagingGuide). Then I created the package using debuild (it compiles and installs to debian/tmp), but the resulting .deb files do not contain anything. I have checked the *.dirs and *.install files and they are fine. Can someone please lend me a hand? [15:16] geser: that we can discuss once I have package ready and I have tested the reverse-build-depends [15:17] slytherin: http://builder.ubuntuwire.com:9998/dist/intrepid/arch/i386/failed has some *-java packages failing to (re)build if you're looking for work :) [15:18] geser: will take a look [15:19] pfft, java. when there's lovely things like visual basic to work on? [15:22] Anyone with some packaging experience around (strange question on MOTU...)? [15:23] flohack: Just ask your question... [15:23] Repost: I'm trying to package a new library. I created the skeleton using dh_make (adapted the necessary bits following the PackagingGuide). Then I created the package using debuild (it compiles and installs to debian/tmp), but the resulting .deb files do not contain anything. I have checked the *.dirs and *.install files and they are fine. Can someone please lend me a hand? === Czessi_ is now known as Czessi [15:28] geser: packages that build-depend on kaffee are failing. Will have to see how many of them are important and then migrate them to openjdk [15:28] Can I debug debuild somehow? I'd like to know which files it tries to copy into which .deb package [15:29] ...and why they are not copied [15:29] flohack: can you pastebin your .install file? also you can debug building with export DV_VERBOSE=1 in debian/rules [15:29] sistpoty|work: Ok, give me a sec... [15:32] http://pastebin.com/m75b8f2be [15:32] flohack: heh, you've commented out the dh_install call, which will actually install everything listed in .install files ;) [15:33] sistpoty|work: THANKS! I'll give it a spin [15:33] sistpoty|work: I just assumed that everything which is not specially commented in the skeleton is optional [15:35] sistpoty|work: Ok that looks good, it complains about missing files in usr/include [15:35] flohack: was just coming to that [15:35] flohack: if my memory serves me, you'll need to list the full path relative to the source package dir in install files [15:35] flohack: which then would be debian/tmp/usr/include etc. [15:35] sistpoty|work: That would be debian/tmp/usr/include/* then [15:36] sistpoty|work: lol [15:36] flohack: unless you use --sourcedir=debian/tmp (or s.th. like that, just check the dh_install manpage) === nand_ is now known as nand [15:37] sistpoty|work: Ok, I'll have a look! [15:38] ScottK, jpds: send [15:38] s/d/t/ [15:38] http://patch-tracking.debian.net/ new tools from debian \o/ [15:45] RainCT: Answered. === Kopfi|offline is now known as Kopfgeldjaeger [15:48] sistpoty|work: Works just fine now, thanks once again! [15:48] your welcome;) [15:49] Is it possible to use the GNU Free Documentation License for manpages that we submit to Ubuntu? [15:49] ryanakca: Yes, but why? [15:50] ScottK: well, what license should I stick it under? [15:50] ryanakca: It's much simpler to use the license used by the thing it's a man page for. [15:50] ScottK: ok, thanks [15:51] jdstrand_: can you take a look at http://revu.ubuntuwire.com/details.py?package=gui-ufw ? it is the package of a GUI for ufw [15:51] is there any reason that could provoke a patch being not applied to just 1 of the files or just on the first file ? (I have 2 files in total) [15:52] Was it not applied or did it fail to apply? [15:53] half-ly applied. only to 1 of two files. also seems to work right when applying by hand in hardy. [15:53] tacone: Also check and make sure you don't have a case where the same change for one file is inadvertently in the .diff.gz as a direct change and the patch isn't getting applied at all. [15:54] ScottK: one of the two files get patched. [15:54] I guessed I shuold get a warning otherwise? shuoldn't I ' [15:54] ? [15:54] RIght. That or one of the files is patched via a direct change in .diff.gz and the actual patch isn't used. [15:56] ok, here's the big news. dpatch apply-all seems not to work the same way in hardy and intrepid. [15:56] is your 00list valid? [15:57] directhex: guess so. on my host computer I get everything ok. in intrepid dpatch apply-all gives no error messages but applies only half of the patch [15:58] if any of you has a hardy box or vm or chroot to download the source package of memaker-1.0.1, try to dpatch apply-all inside the working tree, then "grep class Memaker/ -Ri" and pastebin the result. [16:03] devfil_: I can, but not today [16:03] jdstrand_: tomorrow? the feature freeze will be tomorrow... [16:05] devfil_: the feature freeze is 00:00 UTC tomorrow, or in 8 hours [16:05] devfil_: I have too much to do for FF to get to it today [16:06] jdstrand_: ok, np [16:06] devfil_: I'd be happy to look at it another time though, otherwise try to get another revu person [16:07] jdstrand_: yea, sure [16:10] Heya folks [16:12] sistpoty|work: May I bug you once more? Now I have the problem, that the installed shared library does not work when being linked to with -lfb. I have to add the libfb dependencies too (-lnet -lpcap). I can remember that I had this problem a few years ago, but I can't remember how to resolve it. Google hasn't got an answer either. [16:12] hi bddebian [16:12] Heya bddebian. [16:12] Hi sistpoty|work, Iulian [16:13] so, anyone feel like giving mono-basic revu some love then? [16:13] flohack: it there a pkg-config file or similar? you could use that, to determine ldflags for the library [16:14] sistpoty|work: Ahh...ok so the pkg-config is responsible for pulling in required libs. But shouldn't the linker know that by itself? === superm1|away is now known as superm1 [16:14] flohack: yes, it is... the linker can't know this when you try to link statically (as I assume you're doing) [16:15] devfil_: commented [16:16] sistpoty|work: Ok thanks...I'll dive into pkg-config. There isn't a dh_* command to create the necessary file automagically, is there? [16:17] flohack: no, you'll need to create such a file by hand [16:17] sistpoty|work: Cheers! [16:17] ScottK, I didn't. RainCT had put together a gateway so that ubuntu developers could commit to the trees when sponsorship was needed and such [16:17] superm1: Someone had to add that team to Mythbuntu [16:18] congratulations Laney [16:18] ScottK, the gateway was supposed to catch any mail? Is it not? [16:19] No. [16:19] superm1: bugmail yes, but not other notifications (like the announcement of the new mythbuntu mailing lists) :( [16:19] RainCT: mhh, I'm not sure about somethings [16:19] oh yikes [16:19] okay well for now i'll take it out then until this is sorted [16:19] superm1: can you remove the team from mythbuntu until there's something decided on ubuntu-devel? (I can't find how to do it myself) [16:19] Laney: Congratulations! [16:20] RainCT, okay should be done [16:21] superm1: Thanks. [16:23] devfil_: like? [16:23] ScottK: the perl spamassassin/clamav MIRs are done [16:23] RainCT: - I’d call the binary package "ufw-gtk" instead of "gufw", to make it more discoverable and so that it’s more obvious what it is. [16:24] then what about firestarter? [16:24] ScottK: you, or anyone else, wouldn't have a moment to look at bug #261462 ? [16:24] Launchpad bug 261462 in ldapscripts "New ldapscripts Version" [Undecided,New] https://launchpad.net/bugs/261462 [16:25] err would have a moment? [16:25] RainCT: and the most other things seems me only aesthetics [16:28] devfil_: does gufw do anything which you can't do with plain ufw? [16:28] devfil_: and yes, I've only looked at the diff.. but aesthetics are important :) [16:29] devfil_: err, not everything. the debian/copyright issue for instance would be a rejection [16:29] RainCT: no, but this is no reason to call the package in a different way from upstream don't you think? [16:30] s/this/there/ [16:30] devfil_: if so, why do you call the tarball gui-ufw instead of gufw? [16:31] RainCT: because upstream calls the source dir gui-ufw [16:31] and also it is the name of the project [16:31] devfil_: ah, evil upstream :P [16:31] but the apps is called gufw [16:33] devfil_: anyway, I still think ufw-gtk is a better name (as you can do 'apt-get install ufw' and you find it), but n the other side, it could be confusing for users who directly search for 'gufw', so feel free to ignore this point :) [16:33] devfil_: (generally, always when I say "I'd" or stuff like that on a review it's just a suggestion) [16:35] Laney: congratulations :) [16:35] RainCT: I think there may be a competing project called ufw-gtk, but I am not sure [16:37] jdstrand_: uhm.. if so, they should do some decent SEO :P [16:40] I'm not involved with either project, but I've tried to make them aware of each other === ember_ is now known as ember [16:50] persia: I'm not sure if I understand your last mail [16:50] sistpoty|work: Cheers! [16:51] cheers flohack [16:51] Laney: found it out. wrong patch. [16:51] RainCT: Which part? [16:51] persia: "As long as members of the team maintaining the package have an accurate tree ready for upload (or follow the more typical (and more widely documented) practice of attaching the debdiff to a bug), there ought be no issues sponsoring the update in the regular manner" [16:51] RainCT: If someone prepared something that's ready to go into the archive, there's no need for write access to sponsor it. [16:53] persia: so option 4 of those I listed on my first mail? [16:54] RainCT: Well, some of that. I'm against any upload which doesn't mirror the repo, as I discussed in my first mail. [16:55] It's very much not ideal that the repo is out of date, and in my opinion, it's very much not ideal that someone upload something that can break a flavour without discussion with the flavour maintainers. [16:55] I'm a *huge* fan of collaborative development, and think MOTU ought upload anything either not modified in Ubuntu or maintained by MOTU. [16:56] That said, there are some pockets of packages related to flavours that can have a vast impact on the flavour, and with which an arbitrary MOTU may not have familiarity: the change in the Maintainer field accurately represents this, and ought be respected. [16:57] If you'd asked me about non-flavour packages, I'd not be so opposed, and would think it only appropriate that ubuntu-dev have rights to modify the repo. [16:57] Personally, I think the repo is a convenience. The (pun intended) canonical source for the package, is the Ubuntu repository. [16:58] ScottK-laptop: I can agree with that, but still think MOTU ought respect flavour-specific packages, especially core packages for a given flavour. [16:58] Agreed. [16:58] persia: So what you mean is that changes to mythbuntu packages (and in general packages which have a Maintainer different to the MOTU Team and have Vcs- fields set) should be done through branch merge requests instead of u-u-s? [16:59] If a given MOTU happens to be interested in the flavour, they ought join the $(flavour)-dev group. [16:59] Yes. [16:59] RainCT: I don't think that's what he said. [16:59] RainCT: No. Whether it's branch merge or UUS or what have you doesn't matter. It should be done in coordination with the developers for the flavour. [17:00] When I find something in UUS for a flavour with which I'm not involved, I contact the flavour developers to confirm. I've only had one case where I wasn't told "Go Ahead", and the flavour devs then fixed the issues and uploaded. [17:00] And recognize that not all MOTU are interested manipulating $VCS as part of sponsoring, so a $VCS oriented sponsorship request will reduce your target audience. [17:01] ScottK-laptop: Yes, but completely orthogonal to the point at hand: that I'm not a mythbuntu-dev. [17:01] I that I agree with you [17:02] persia: Yes, but there was also a comment about 'or pull from the branch for sponsorship' that I was responding to. [17:02] persia: but that http://paste.ubuntu.com/40945/plain/ seems like a contradiction to me so I still don't understand your position in relation to sponsoring :/ [17:02] ScottK-laptop: That's not the documented procedure for UUS, but some people do it. I'm not going to complain if it works for them, and I'm not going to tell anyone they must pull from a branch. [17:03] I'm also not going to update the UUS documentation to indicate that one ought pull from a branch. [17:03] RainCT: Another point (unrelated to what persia is trying to discuss now) is that if the Mtyhbuntu icon is on my LP profile, people will, reasonably assume I have something to do with Mythbuntu and that's wrong. [17:03] RainCT: The repo should be up to date for an upload prior to it being sponsored. Anything else is simply not correct. [17:04] ScottK-laptop: but it's another icon for the collection! :P [17:04] ScottK-laptop: yes, that indeed a problem which I hadn't thought of until you first mentioned it [17:04] Mind you, Mythbuntu is cool, and if I had an extra couple days each week, I'd like to be involved, but it's simply not the case now. [17:04] sistpoty|work: I'm not an active collector. [17:04] heh [17:05] sistpoty|work: I like emblems. I want more emblems, but I want them for stuff I actually do. [17:06] persia: Well, so if stuff can be uploaded going through u-u-s, but only if it is in the branch, we are back to the start. [17:07] persia: where people should file branch merge requests for the mythbuntu team to handle them, and if the guy who handles the request isn't a MOTU either he or the original contributor ask u-u-s to upload it [17:08] RainCT: Right. We shouldn't be accepting random updates to flavour-specific packages that have not been approved by any members of the $(flavour)-dev team. [17:09] That said, I don't know of any flavours (excepting possibly gobuntu) that don't have active enough development teams that this can be done in a timely manner. [17:09] ... unless $(flavor)-dev team has a policy otherwise (not that the do/should, but the option is there). [17:10] persia: (I though Gobuntu doesn't exist anymore?) [17:10] persia: so that behaviour should be documented on the wiki (after proposing it on -devel) [17:11] RainCT: gobuntu-meta was in the archives last I looked, but yes, I believe it's inactive. [17:12] I also think it doesn't need special discussion: the Maintainer is not MOTU either explicitly or implicitly. Why should MOTU be changing the package? [17:12] (p.u.c doesn't show gobuntu-meta being in intrepid) [17:13] persia: because it is in universe, and unless told otherwise new contributors only know that universe -> u-u-s, main -> u-m-s [17:14] New revision azureus_3.1.1.0-3ubuntu2 seeking sponsor. Bug 261879. lifeless, persia: it contains the fix we've been talking about on -java. Comments? jdong: ping :) [17:14] Launchpad bug 261879 in azureus "Candidate revision azureus_3.1.1.0-3ubuntu2" [Undecided,Confirmed] https://launchpad.net/bugs/261879 [17:14] RainCT: Sure. I don't see why they need to be especially informed. Like I said, I've only once had any response from a flavour development team other than "Go Ahead". Generally, someone refreshes the branch from the upload, or so I presume. [17:15] ma10: looking [17:15] (packing today to go back to school) [17:15] lemme boot up my VMs [17:16] I'm packing too! My study abroad year is finished.. :( Going back home [17:17] ma10: I hate that never-ending feeling like I forgot something [17:18] Don't tell me about it.. But this time i just have to empty the flat [17:19] ma10: that makes life easy. I stayed back at home for the summer so there's stuff *all around* here that I could've forgotten [17:20] ma10: have you tried submitting the multiuser workaround/fix upstream too? [17:20] jdong: just remember your pc and underwear, you'll be allright :) [17:20] I'd be curious what they have to say [17:21] oh i had quite a discussion with them [17:21] they fail to admit it's a real issue [17:21] ma10: lovely. [17:22] because there should be one user per machine with one instance running (good for network performance) [17:22] azureus upstream is fun at times. Plus they REALLY love Ubuntu (not) [17:22] i managed to dodge that point [17:23] anyway i think this fix is too much of a hack for them, they should reduce code duplication first, as lifeless was suggesting [17:24] ma10: indeed. At any rate, the fix is quite important for us as multiuser support and cross-user security are essential pieces of what Ubuntu is. [17:24] that's how i see it [17:25] persia: so.. contributors subscribe u-u-s providing a debdiff (and perhaps also a branch) and the MOTU who looks at the debdiff pings a mythbuntu member for him to merge it into the branch, and after that mythbuntu guy says 'OK' upload it? [17:25] *uploads [17:26] \o/ [17:27] RainCT: That might be one example of a workflow. I suspect the majority of those who contribute to mythbuntu directly and propose things for upload will already be mythbuntu-dev, which makes some of that a no-op. [17:27] At least my experience was that it was rare for someone not a member of the $(flavour)-dev team to be fiddling with a core flavour-specific package. [17:32] * RainCT doesn't see why we would want such stuff on u-u-s then as it makes more sense to ask a mythbuntu dev directly, but doesn't feel like continuing the discussion :P [17:35] thanks RainCT, Iulian and james_w (and jpds and dholbach)! Also thanks persia for the taste of power. It felt good [17:36] Laney: Just a taste to get you excited :) [17:36] jdong: thanks! [17:37] haha [17:37] * dholbach hugs laney [17:38] RainCT: If the mythbuntu-dev is also MOTU, then it doesn't. [17:39] I think a lot of this goes away after the archive reorg. [17:39] ScottK-laptop: in the evening I'll present you my first MIR try ^^ [17:40] sebner: Best hurry as sommer is going wild. [17:40] ScottK-laptop: Sure, I'll try [17:42] hi! can anybody help with second +1 for http://revu.ubuntuwire.com/details.py?package=libnb-platform-java please? [17:43] huge thanks to dholbach for the first one [17:43] it's probably worth mentioning that it's "an update" of the existing libnb-platform7-java [17:44] which makes the review more straight-forward [17:44] and it'S required for the new netbeans :) [17:44] yes, exactly:) [17:44] anyone know where I can find libstdc++-libc6.2-2.so.3 [17:48] dholbach: If it's an update, why can't you just upload it? [17:49] ScottK-laptop: it's a new source package [17:49] OK. [17:50] or rather upstream rename... you know what I mean [17:50] anyway... I call it a day now - see you guys tomorrow! [17:51] dholbach: If it's a rename, I think one MOTU is enough. [17:54] ScottK-laptop: won't there be any problems with archive admins [17:54] better stick to the rules - in any case, I need to rush off now and my intrepid machine is already shutdown [17:55] Juli_: No. That's a MOTU rule, not a hard archive requirement. [17:55] thanks in advance - see you tomorrow :) [17:56] * sistpoty|work also calls it a day and heads home... cya [17:58] * persia looks at libnb-platform-java [17:59] persia: thanks! so only netbeans itself will be a headache after platform is uploaded [17:59] Juli_: And that's in a bug, right? [18:00] hey, is it possible to create a debian driver package for the kernel so that it doesn't break between security updates to the kernel? I've manually modified the linux-image-2.6.24-19-generic_2.6.24-19.41_i386.deb package (added drivers, bumped minor version number), but this obviously will break after security updates [18:00] persia: yes https://bugs.launchpad.net/ubuntu/+source/netbeans/+bug/253016 [18:00] Launchpad bug 253016 in netbeans "New upstream version (6.1) for netbeans" [Undecided,Confirmed] [18:01] TomaszD, https://help.ubuntu.com/community/Kernel/DkmsDriverPackage [18:01] so is it possible to create a package that will just throw some .so files into the kernel tree, without it breaking? [18:02] TomaszD, DKMS will recompile them when you rev the kernel more or less [18:03] superm1, great, that was so obvious that I didn't think about dkms, wonder if it'll work [18:03] Note that this ought only be used in cases where the driver is for a device that is typically installed in an environment suitable for compilation. [18:03] TomaszD, as long as you craft your dkms.conf properly, it should be able to to the trick for you [18:03] Moving everything to DKMS would be bad. [18:03] the impression i got was this is a local solution for TomaszD [18:04] Well, I'd argue there are cases where it's appropriate to use DKMS in the archives as well, just not for everything. [18:04] well, not local, it's for MSI Wind users in general, it will eventually be released into the wild [18:04] TomaszD, well the proper route to go is to try to get these into SRU's [18:05] so that future kernels will include them and then you won't need the DKMS built packages anymore [18:05] TomaszD: MSI Wind is one of the examples where you might not want DKMS, as that's a fairly underpowered machine. [18:05] Mind you, the new ones are nicer, but still. [18:05] and set a flag in the dkms.conf to stop using/building when you're on that newer kernel [18:06] SRU would be a good idea I guess [18:06] congrats Laney! Keep up the good work. [18:06] TomaszD, so if these are NEW drivers that don't conflict with anything that shouldn't be too troublesome. if they are large changes to existing drivers then that can cause complications [18:07] no, these are compeltely separate drivers [18:07] Realtek 8187SE [18:07] WLAN [18:07] TomaszD, then i would try to factor them into the LUM packages and submit a patch to the kernel team's mailing list to add them [18:08] TomaszD, and until that package is released do a dkms package that includes binary and source of the modules [18:08] dang it I have to look up every SRU and LUM thing you throw at me [18:08] :] [18:09] TomaszD, lum == linux-ubuntu-modules. it's the package that contains modules that are not upstream yet [18:09] ahh === persia_ is now known as persia [18:11] Someone can take a look at http://revu.ubuntuwire.com/details.py?package=gui-ufw ? [18:11] devfil_: Wouldn't ufw-gtk be a better name? [18:11] jpds: Read the scrollback. [18:12] Yay for evil upstreams. [18:14] scrollback? [18:15] lukehasnoname: irclogs.ubuntu.com [18:15] mm === devfil_ is now known as devfil [18:18] jpds, a better name would be ubuntu-firewall, ufw-gtk is good for nerds only :] [18:22] TomaszD, ubuntu: linux for big fat nerds? [18:22] * directhex jumps up & down & pokes people over: mono-basic on revu; monodoc 1.9 main merge [18:23] didrocks, not quite the target audience Ubuntu is aiming at, they're all using gentoo ;] [18:23] I kid, I kid [18:23] TomaszD, cool kids dropped gentoo when it sold out & went mainstream. now they all run Arch [18:24] real men use LSB. Let's stop this now. [18:24] *LFS [18:24] LSD? [18:24] :] [18:25] TomaszD: 3 times today someone hilight me here for directhex ^^ [18:25] didrocks, sorry matey... http://www.googlefight.com/index.php?lang=en_GB&word1=directhex&word2=didrocks [18:27] And for extra points, NM should stop disconnecting me today :) [18:28] for even more points, all my outstanding merge & sync requests should magically happen. and mono-basic gets the required approvals on revu [18:28] but sometimes, persia, life just isn't fair :( [18:29] directhex: before feature freeze? ;) [18:29] laga, well, YES! [18:29] directhex: If they are all in the queue, and they would otherwise violate feature freeze, chances are high they will be looked at in the next few hours. No promises on them getting approved. [18:30] time to prepare another mythtv upload.. [18:30] directhex: In the meantime, if you'd like to help with the 40 packages above, it may favorably incline various MOTU towards you, including those in some of the leadership positions :) [18:30] which 40? i only just got home [18:31] i guess i could look at some, too, to prepare for my UUC application. [18:32] directhex: Visit http://qa.ubuntuwire.com/bugs/rcbugs/ : everything with a new upstream ought get checked, as it will make the life of the SRU and SWAT teams easier if intrepid & lenny share the same version, and the current packages are likely to be RC buggy in intrepid. [18:33] laga: That'd be great. Thanks. [18:33] dang, i need some caffeine... [18:34] persia: what am i supposed to do? check the new upstream to see if the bugs are fixedß [18:34] laga: That, and also whether introducing the new Debian changes (through a merge or sync) would cause significant disruption to intrepid development. [18:35] If the package is an edge packages (no rdepends or reverse build-depends), it's exceedingly likely it is best updated. [18:35] If there are reverse dependencies, it needs a little more investigation. [18:35] persia: what about extra points for uqm upload? :P [18:36] Claim the package here, and ask any questions you have. There are a few of us who tend to chase as much as possible pre-FF, and we'd be happy to help (as we need your help to get it done in time) [18:36] sebner: No extra points for that: it's on my list of things to definitely do tonight though. [18:36] * persia has a shorter, targeted list today [18:36] persia: \o/ [18:37] i'll look at i810switch. looks like a fun package [18:37] sebner: You like new stuff. Want to check the 40 RCbug new-upstream packages? [18:38] laga: Remember to check the LP bugs also: it may be that someone already requested the sync or merge, and it's just waiting for sponsoring. [18:38] persia: are they more important as the non-new grave bugs? [18:38] sebner: You owe me a MIR before you do fun stuff. [18:38] ScottK-laptop: of course. Though I file sync requests besides :P [18:39] sebner: Yes, because they need to get done in the next several hours. The non-new upstream grave bugs can be fixed over the weekend. [18:39] ScottK-laptop: Is FF also the deadline for MIRs ? [18:39] persia: Bah, you should have asked me ealier. I'm not harry potter to do loads of magic in few hours -.- [18:40] sebner: It's been there for weeks. I just got anxious now. I know you know about RCbugs :p [18:40] :) [18:40] persia: It's not a hard, hard deadline, but yes. [18:41] persia: Sure but I focus on the grave ones and there a lot aren't new upstream ones [18:41] ScottK-laptop: From a motu-release perspective, do you think it's more important to chase the MIRs, or the RCbugs with new upstreams? [18:41] how do I know what package system uses any package ?? [18:42] sebner: No, only 5. You can have those, if you like? [18:42] leonel: Generally reading debian/control and debian/rules will advise you. Most of the time, debian/control ought be sufficient. For many packages, even the .dsc alone is sufficient. [18:42] persia: We'll see. First I have to do some other stuff, then finish the MIR for ScottK-laptop and then when I don't fall asleep I grab some new upstream versions [18:43] thanks persia [18:43] sebner: No sleep until midnight UTC. That's the deadline. [18:43] persia: I would if I wouldn't have a (summer) job -.- [18:44] typical. the one package i've got experience with, sebner's already on [18:44] Well, I suppose. It's just the two days a year that this happens. [18:44] superm1: btw, can mythtv be used for free? [18:44] btw, what do i do if i think a package is suitable for merging/syncing? file a bug? [18:44] RainCT, define free... [18:44] directhex: Be more agressive: fix the bugs before anyone else has a chance :) [18:44] superm1: € [18:44] RainCT, yes it can depending on your locale and data availability [18:45] directhex: which one? midori? [18:45] sebner, nini [18:45] directhex: ah ^^ [18:45] persia: lol, that's a good motivation xD [18:45] sebner, i had to patch around its funny behaviour in my tangerine mods in my repo [18:46] laga: Yes, file a merge/sync bug, and subscribe the sponsors queue. For a merge bug, be sure to attach the debdiff before subscribing the sponsors. [18:46] ok [18:46] slytherin! [18:46] persia: hi [18:46] directhex: funny behaviour? [18:47] slytherin: You feel like looking at merges/syncs to ensure we match Debian for the Java packages, right? [18:47] (upstream versions) [18:47] persia: though I'm sure "sebner on it" is even more readable then "Sync requested" :P [18:47] We've 493 minutes to review, and get everything requested [18:47] yes, I will be able to this over weekend. is that fine? [18:47] sebner, .INI file comment character is ";", tangerine uses ";" as its separator for multiple paths [18:48] sebner: I tend to put in bug numbers, for ease of reference by others, rather than just "persia on it" [18:48] persia: Nearly nobody uses them. and if you click on the package you'll see the bug report anyways so nvm [18:49] sebner: Well, some people do, but yes, not that many people. I still try to be helpful. [18:49] persia: I appreciate [18:56] ScottK-laptop: Launchpad to go Open Source by next OSCon ;) [18:56] sebner: You're reading the news, aren't you? [18:56] persia: yes, why? [18:56] sebner: Get to work. [18:56] lol xD [18:57] sebner: Aren't you supposed to be doing an MIR and some RCbugs? If you're out of those, I can find you more stuff that needs doing: all new packages or new upstreams. [18:57] sebner: If that helps reduce the parochialism of the developers, then I think I think it'll be a big win. If not, not so much. [18:58] persia: ScottK-laptop: Don't worry. I'm already a slave of sebner. :P [18:59] am i supposed to request syncs even if the RC bug doesnt affect ubuntu? [19:00] laga: Your call. For edge packages, I tend to do that anyway, especially where Ubuntu has a chance of matching a Debian stable release, but if there are a lot of rdepends, it's not the best thing, as it introduces instability into Ubuntu. [19:00] If you want a real opinion, ask ScottK or another member of motu-release. [19:01] okay. i810switch doesnt has rdepends and the diff is just a macbook fix.. who uses i810switch these days? [19:01] * laga goes to request a sync anywaysd [19:02] laga: The three users will all thank you :) [19:02] persia: will be back in 5-10 minutes [19:03] persia: so. here you have a new upstream sync bug #261939 --> but don't tell ScottK :P [19:03] Launchpad bug 261939 in kaya "Please sync kaya 0.4.2-3 from Debian(Unstable)" [Undecided,New] https://launchpad.net/bugs/261939 [19:03] ScottK-laptop: just a joke. now working on your MIR :) [19:04] sebner: I'll be silent on the matter, but that solves 2 RC bugs with a single sync :) [19:05] persia: Die you bad bugs, die! :) [19:05] sebner: That's the attitude :) [19:05] persia: does a MIR also kill RC bugs? ^^ [19:06] sebner: Sometimes. [19:07] :) [19:07] * sebner back to work [19:07] Harvest is cool! It makes it easy for people to identify bugs fixed upstream (Debian or the devel) and get a syn throu or closing issues after verifying and testing. Cool! [19:07] * tuxmaniac closed 2 bugs like that now :-) [19:08] tuxmaniac: Indeed. It's an excellent resource. On the other hand, today we're focusing on bugfixes that need to be in place pre-FF, as we've only 472 minutes left, and harvest doesn't know any better. Best to review quickly and see what's fixed in Debian or fixed Upstream that would require an FFe to be included, and concentrate on those. [19:09] yay, my first sync bug evar [19:10] persia: I'm wonderin since new upstream versions won't get into the archive in 472 and they'll need a FF Exception. like it was in hardy cycle!?! [19:10] Anyone know why Bug #259300 was marked invalid? seems like it would fix a RC bug.... [19:10] Launchpad bug 259300 in motion "Please sync motion 3.2.9-5 (universe) from Debian unstable (main)" [Wishlist,Invalid] https://launchpad.net/bugs/259300 [19:11] sebner: If they aren't approved within 470 minutes, yes. The archive-admins often pull the syncs post FF (by a few hours) without bothering about FF, as long as the syncs were approved in time. [19:11] asomething: Looking [19:12] persia: Really? I thought it was different in hardy cycle [19:12] the RC bug: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=487568 [19:12] Debian bug 487568 in motion "After upgrade from 3.2.9-3 to 3.2.9-4 Motion doesn't work anymore" [Grave,Closed] [19:12] sebner: Nope. We've always done it that way. [19:12] Iulian: See asomething's question about motion? [19:13] persia: kk, so my brain is playing a trick on me (as usual) :) [19:13] persia: yes. I am checking all Science packages for any such pending syncs [19:14] haha. [19:14] * Save the world from masturbating monkeys (closes: #496409) [19:15] * persia grumbles about source pacakges that can only be built in intrepid [19:15] persia: Still don't have a intrepid chroot? [19:16] sebner: I've currently 7 of them. I just didn't happen to be in one when trying to build one of the sources. [19:16] ah ^^ [19:17] persia: btw, you maybe should also focus on forcing u-u-s to process your forced sync/merge requests in time. :) [19:18] sebner: Indeed. The three areas I'm concentrating on right now are UUS, REVU, and multidistrotools for the Debian team to which I belong. [19:18] I can only run a limited number of simultaneous builds, or I'd be pushing more. [19:19] Speaking of REVU, we've 4 packages with one advocate. Anyone want to be the second advocate? [19:19] persia: that is already pretty nice, just don't forget that many contributors aren't MOTUs and need sponsors(not only you) :) [19:19] sebner: Indeed. More sponsoring tonight would be a good thing. Let's flood the buildds! [19:20] persia: I suppose u-u-s is already flooded? ^^ [19:20] Someone can take a look at http://revu.ubuntuwire.com/details.py?package=gui-ufw ? === emma_ is now known as emma [19:20] persia: find an archive admin to process the open syncs requests and the buildds get flooded [19:20] sebner: Indeed, but keeping it flooded is the best means to get the buildds flooded. [19:21] geser: I'm not so worried about that: I suspect we've enough merges and updates to do a fair bit of harm. [19:21] archive-admin processing of NEW might help as well. [19:21] hopefully none of them is on holiday xD [19:22] sebner: Doesn't matter. archive-admins check the date of subscription, and will push stuff post-FF as long as it was forwarded to them (and valid) pre-FF. [19:22] ah cool [19:22] so FLOOOOOOOOOOOD [19:22] Should all be caught up by Monday or Tuesday, but it might take that long. [19:24] * sebner is already looking forward at filing FFe bugs ^^ (though not that many. /me learned from hardy cycle) [19:24] persia: What kind of setup do I need to do to use requestsync email interface? [19:25] slytherin: I never checked how this piece of software is working xD [19:25] slytherin: No idea. I used requestsync once, and decided that it was harder for me than doing it manually. [19:25] checked = understood [19:25] persia: +1 [19:26] devfil: advocated [19:27] RainCT: I've fixed the "allows" problem [19:27] Five. Five packages on REVU seeking a second advocate. Who's up for some? [19:27] Ok, can anyone tell me where can I find LP cookie in my firefox profile? [19:28] RainCT: can you readvocate it when I've upload the new version? [19:28] persia: I'm wondering that revu packages are still importatn [19:28] *important [19:28] devfil: sure === emgent` is now known as emgent [19:29] hello [19:29] sebner: anything containing the string "mythbuntu" (not kidding) [19:29] emgent: \o/ [19:29] Laney: congrats :) [19:29] laga: I see [19:29] heya sebner :) [19:29] Laney: congratulations from me too [19:29] slytherin: '~/.lpcookie.txt', '~/.mozilla/*/*/cookies.sqlite', '~/.mozilla/*/*/cookies.txt' [19:29] sebner: No idea. I've not reviewed them all. People with important packages should be complaining about now. [19:30] emgent: want to help flood u-u-s or better the build machines? [19:30] lol no today sebner :) [19:30] LP COOKIES! \o/ [19:31] emgent: surely today [19:31] jpds: oh you can remove my account in your server. thanks [19:31] persia: convert him! [19:31] emgent: It's the day before FF. We need your help to process everything that would otherwise be an FFe in the UUS queue. [19:31] emgent: OK; done. [19:31] ha! [19:31] sebner: i cant, i should go out [19:31] emgent: dito :P [19:31] persia: yeah i know :| [19:31] emgent: Please? There's only 449 minutes left until the deadline. [19:32] persia: tomorrow i will go out (Amsterdam) [19:32] Why does installing devscripts install exim? I thought that was fixed a while back. [19:32] emgent: Yes, but it's FF! [19:33] persia: eh. I know, but i should go out! persia you can try to talk with my girlfriend, if you like.. [19:33] Im looking forward to dev week! [19:33] RainCT: I was looking for instruction to copy it from firefox profile to ~/.lpcookie.txt. Anyway, I found that I have done it already at some point of time. [19:34] see you later people, good work. [19:34] slytherin: have a look at prepareLaunchpadCookie() in ubuntu-dev-tool's common.py [19:34] emgent: Just 5 sync requests? [19:34] RainCT: ok [19:34] devfil: still uploading? [19:35] RainCT: it will appear at 20:40 [19:35] persia: uhm, i'm back in ~3hours i will try to give my little help [19:35] but now i have to go out :( [19:35] emgent: Excellent. See you then. Thanks. [19:35] persia: see you later [19:36] devfil: it isn't on REVU (on the server, I mean) [19:36] ScottK-laptop: I think I finished the MIR. do you check it now and I fix your complains or later and I can start killing bugs? [19:36] RainCT: I've uploaded it [19:36] ah now [19:37] RainCT: http://revu.ubuntuwire.com/details.py?package=gui-ufw [19:37] devfil: yep, advocated [19:39] sebner: Sure. What bug? [19:39] ScottK-laptop: bug #261946 [19:39] Launchpad bug 261946 in libtext-glob-perl "MIR for libtext-glob-perl" [Undecided,New] https://launchpad.net/bugs/261946 [19:40] sebner: Looking [19:41] persia: debian changelogs page is pretty slow these day. our fault? [19:41] sebner: Might well be. [19:42] persia: Should I tell you bug number one by one or all at once? [19:42] * persia hopes so, as this would indicate that *lots* of people were looking at pre-FF stuff [19:42] bug 220268 is fixed upstream. But no patch is attached in the bug tracker for us to have a look. Is it worth digging such issues and bypassing upstream release cycle and getting it fixed in ubuntu? [19:42] Launchpad bug 220268 in gnumeric "gnumeric crashes when formatting dates to mmmmm or mmmmm-yy" [Undecided,Confirmed] https://launchpad.net/bugs/220268 [19:43] I mean there are atleast 2 more such patches that upstream has "fix released" for gnumeric but not released an offocial version. [19:43] slytherin: Subscribe the sponsors queue, and add the uus-fre-ff-810 tag [19:43] persia: ok [19:43] Err. uus-pre-ff-810 [19:43] sebner: the page is indeed slow [19:43] if we port these patches we have the possiblity of clsoing couple of bugs [19:43] any suggestions? [19:44] slytherin: luckily not the news page :) [19:44] tuxmaniac: Has upstream actually done a release that includes the fixes, or are the fixes just in VCS? [19:45] just in VCS [19:45] persia: you have the time in your head. how many minutes left? [19:45] tuxmaniac: Feature changes, or just bugfixes? [19:45] sebner: 375 or so. [19:45] persia: but they have closed the issue. one solves a crash and two minor bugfixes [19:46] tuxmaniac: We'll want to backport the fixes later then. Keep looking for stuff that needs to go pre-FF. [19:46] persia: k, thx [19:46] Hi. Can somebody please review/advocate tvbrowser? should be fine by now: http://revu.ubuntuwire.com/details.py?package=tvbrowser [19:46] persia: aah ok [19:46] sebner: Actually, rather 315 or so. I can't do math right now. [19:46] blueyed: I just started looking at it :) [19:47] RainCT: awesome! :) [19:47] sebner: Looks good. Thanks. [19:47] ScottK-laptop: np. I'm just sad I didn't discover that ealier. I just did 1 and Asommer is working on it like hell :( [19:48] blueyed: is it a KDE application? [19:48] RainCT: java [19:49] blueyed: right.. so for all desktop environments? [19:49] persia: And when I start complaining here that no one sponsors me? (1-2 hours before FF)? ^^ [19:49] RainCT: yes [19:49] sebner: Don't. You'll get sponsored. [19:49] blueyed: I'd change the Name in the .desktop file then to be more descriptive [19:49] (or if you don't, complaining won't help) [19:50] persia: I'm just answering for "worst case" :P [19:50] *asking xD [19:51] persia: bah, I always thought a u-u-c has VIP rights :P [19:51] sebner: Regardless, the sponsors are likely agressively chasing the queue looking for FF stuff. As long as you have the pre-FF tag, you'll get sponsored if the sponsors have the ability to sponsor it in time. [19:51] No. Why? [19:51] persia: *joke* [19:51] better we get back to work ^^ [19:52] blueyed: does it need some special hardware / subscription to some service / etc? if not, the priority should be optinal [19:53] *"optional" [19:53] RainCT: for example? IMHO it does not matter for the user which DE it is for really. [19:53] looks like maxima needs a merge badly. Debian bug 474909 lists a whole lot of bug fixes. [19:53] Debian bug 474909 in maxima "maxima: FTBFS: /bin/sh: ./maxima: No such file or directory" [Serious,Closed] http://bugs.debian.org/474909 [19:53] blueyed: KDE displays the GenericName or something like that below the Name, that's why I asked if it if for KDE [19:53] RainCT: it does not need some special HW/subscription [19:54] blueyed: for GNOME/XFCE it is recommended (in the HIG, iirc) to have a descriptive name, like most applications preinstalled in Ubuntu do ("Firefox Web Browser", and so on) [19:54] blueyed: use the full URL in vcs-bzr [19:56] blueyed: Overview.txt is uninteresting to the user [19:57] RainCT: . I think it fits "extra", according to the desc: "This contains all packages that [...], or are only likely to be useful if you already know what they are or have specialized requirements." [19:58] blueyed: because of what? [19:59] blueyed: are all channels it knows about german or something like that? (if so I'm happy with extra) [19:59] RainCT: I'm fine with "optional", too - if you still think it fits better. [20:00] blueyed: no, just tell me the rationale :) [20:00] ..not sure.. they are already "going international", so.. [20:00] ScottK-laptop: Commented [20:00] * RainCT is wondering wheter the priority has any real importance.. [20:00] RainCT: nothing more than above.. /me, too. [20:00] RainCT: I will change it to optional. [20:01] Iulian: Thanks. [20:02] core dev ScottK-laptop :), is the priority used for anything useful? [20:03] RainCT: base packages? [20:03] jpds: beside that [20:04] RainCT: Not in Ubuntu. [20:04] RainCT: But you may as well get it right. [20:05] ScottK-laptop: and in Debian? higher priority = first to be build or something like that? [20:05] RainCT: do you think GenericName in the desktop file should get improved? [20:05] blueyed: no, it's fine :) [20:07] RainCT: so a new upload is coming. changes at: http://bazaar.launchpad.net/aunchpad.net/~blueyed/tvbrowser/ubuntu [20:07] No. Not exactly. More what the primary was to get something done. As an example, their default MTA is Exim. All other MTAs are priority Extra as a result. [20:08] In theoty you can install all of optional and not get any confilcts. [20:08] ScottK-laptop: Ah. Thanks for the info. [20:09] RainCT: fixed url is: http://bazaar.launchpad.net/~blueyed/tvbrowser/ubuntu [20:09] blueyed: OK. /me is test-building [20:11] how can I haXX0r debian/rules that gcc doesn't treat warnings as errors? [20:12] blueyed: lintian is still unhappy.. output pasted on REVU [20:12] sebner: look for -Werror in debian/rules or the Makefiles [20:13] geser: thanks :) [20:17] blueyed: I'll advocate once everything I said is fixed [20:17] So I find myself reverting to my pre-broadband browsing habit of clicking on something, moving on to another browswer window, and then coming back to it later on Launchpad. [20:18] So I have a new motto for them: [20:18] Launchpad: For when you're nostalgic about dial-up. [20:18] Yeah. It could be a lot faster, especially today. [20:19] i find some debian boxes slower. [20:21] geser: well I had to edit the configure script =) what was now the discussion about patch-systems? ^^ [20:26] gah, i cant remove comments on http://qa.ubuntuwire.com/bugs/rcbugs/ [20:26] laga: Known bug. Harass ajmitch if you really want something done about it. [20:27] ajmitch: consider yourself harassed - i can't delete comments on qa.ubuntuwire.com/bugs/ [20:28] alright, not gonna merge qemu now, i need to prepare a mythtv upload [20:29] ScottK-laptop: How is UMS re: FF stuff? [20:30] UMS is one acroynm too many for me for today? [20:31] blueyed: woot. Just tried out TV-Browser, nice :) (I prefer tvmovie.de, though) [20:31] ScottK-laptop: Heh. OK. Not likely stuff that worries me much, but I thought there might be a heap of last-minute stuff. [20:32] persia: What is UMS? [20:34] Ubuntu-Main-Sponsors [20:35] My apologies: I thought you were ignoring that acronym specifically, rather than having forgotten the definition. [20:37] No problem. [20:37] Dunno. I haven't had much time to look. [20:38] Anyone feel like doing a gnurobots merge? [20:38] ScottK-laptop: isn't that a *long-known* bug on ubuntuwire? [20:39] Yes, but still unfixed. [20:39] My memory is that the reason the bug is there is that a spider deleted all the comments one day. [20:39] How about a tuxtype merge? [20:39] ^^ [20:40] debian packages site isn't loading for me :( :( :( [20:40] R.I.P [20:40] yeah, seemed borked here too [20:40] Which site? packages.qa.debian.org? [20:41] pretty everything ^^ [20:41] What data do you need? There's probably another way to get it. [20:41] persia: debian changelog site xD ... why merge gnurobots ... sync? [20:42] sebner: apt-get source in a sid chroot, and I haven't investigated whether the Ubuntu changes may be dropped. [20:42] persia: there isn't an ubuntu change. just a rebuild. but before it was on autosync [20:43] sebner: Great. Now that you've investigated, would you like to file the bug? [20:43] persia: xD you are playing tricks :P Sure, I'll testbuild and file the bug then [20:44] Don't forget tuxtype :) [20:44] haha [20:44] -.- [20:44] ok ok. I'm taking it as well [20:44] Thank you. [20:45] persia: np, just wondering that gnurobots isn't on the RC list [20:46] sebner: it's not RC. [20:46] persia: a app you like? ^^ [20:47] Never used it. [20:47] Just on one of my lists. [20:48] persia: and now I have to work on your list so you have time to upload uqm? ^^ ^^ ^^ [20:48] sebner: I just finished downloading the source, and will be reviewing the patch momentarily. [20:49] persia: I don't believe you until I see it uploaded :P [20:49] sebner: You don't have to believe me if you don't like. [20:49] Laney: Can you shed any light on the status of bug #229136? [20:49] Launchpad bug 229136 in extremetuxracer "Please merge extremetuxracer 0.4-1 (universe) from Debian unstable (main)." [Undecided,Incomplete] https://launchpad.net/bugs/229136 [20:50] smarter: Maybe you have an idea? [20:51] persia: I'm still waiting for the Debian Maintainer to do something [20:52] I filled a bug with a patch to merge my changes to his package, but he never answered [20:52] smarter: Well, if it doesn't happen in the next 249 minutes, it's not going to happen for intrepid. Would you like to prepare a debdiff? [20:52] I may try [20:52] smarter: Good luck, and thanks. [20:53] This stuff is a bit old, I may have forgotten how it worked (: [20:53] * smarter grabs his own patch and try to see what it does [20:53] sebner: You could have told me someone else figured out the uqm packaging :) [20:54] persia: hmm? the git one? [20:54] persia: do you have the u-u-s with tag link around? [20:54] sebner: Indeed. Anyway, it's not really an issue: less work for me :) [20:54] RainCT: No, but I'll dig it out. [20:54] persia: ^^ [20:55] persia: don't worry, I'll search it myself then [20:56] https://bugs.launchpad.net/%7Eubuntu-universe-sponsors/+bugs?field.searchtext=&orderby=-importance&assignee_option=any&field.assignee=&field.bug_reporter=&field.bug_supervisor=&field.bug_commenter=&field.subscriber=&field.status_upstream-empty-marker=1&field.omit_dupes.used=&field.omit_dupes=on&field.has_patch.used=&field.has_cve.used=&field.tag=uus-pre-ff-810&field.tags_combinator=ANY&search=Search [20:56] 15 bugs currently on the list. [20:56] thanks [20:57] That first one - Gpa I did. Its been uploaded into intrepid and i've submitted the patches to debian. [20:57] (and some of those are SRU or Debian, so I'm not sure exactly why they are there) [20:58] stefanlsd_: ok, unsubscribed u-u-s [20:58] Am I still here? [20:58] persia: yep [20:58] Excellent :) [20:58] persia: tuxtype = main? [20:59] sebner: Apparently so. [20:59] ok. the next one with zaptel is also mine. heh. https://bugs.launchpad.net/ubuntu/+source/zaptel/+bug/64059 [20:59] Launchpad bug 64059 in zaptel "Wrong device-names in udev - Unable to open master device '/dev/zap/ctl'" [Low,In progress] [20:59] persia: /me hides [21:00] sebner: Don't let main scare you: it's probably a useful update, or it wouldn't have happened so close to the Debian freeze. [21:01] persia: ^^, kk [21:01] * RainCT is working on the sugar one [21:01] i think the problem with this is coming in that people are using asterisk with zaptel and asterisk is looking for /dev/zap/* with group asterisk, and its we have it as dialout. I think thats correct and probably something we wont fix [21:02] (although I'm tempted to reject it :P) [21:03] persia: I hope the contributors are doing a good job otherwise the reviewers will go wild xD [21:04] sebner: Just to check, have you been adding the uus-pre-ff-810 tag on all the stuff that needs to get applied in the next 236 minutes? [21:04] Can we unsub u-u-s from 64059. i think its ok [21:04] bug #64059 [21:04] Launchpad bug 64059 in zaptel "Wrong device-names in udev - Unable to open master device '/dev/zap/ctl'" [Low,In progress] https://launchpad.net/bugs/64059 [21:05] persia: ah. Didn't know that this exist xD but not needed for normal sync bugs I suppose!? [21:05] * nxvl dances [21:06] sebner: Anything that includes a new upstream or a new feature needs that tag if you expect the sponsors to get to it before feature freeze (as announced by DktrKranz some days ago) [21:06] persia: as I said, "normal" sync bugs (no new upstream) don't need it right? That are most of mine :) [21:07] nxvl! Welcome to the last-minute rush against feature freeze. We've 234 minutes to merge/sync/update/patch everything that might otherwise require a freeze exception. [21:07] UUS needs you. MoM needs you. RCbugs needs you. mdt needs you :) [21:07] persia: what about "We need you" [21:07] sebner: No, a sync without a new upstream doesn't need it, unless that includes some significant feature additionl. [21:08] persia: it smells like FF, things are going funnier and brains going to blow up! [21:08] sebner: We always need nxvl, but today those four things need him especially. [21:08] nxvl: Yep. 232 minutes left. Get cracking! [21:08] FF doesn't block FTBFS patches, right? [21:08] nxvl: We want you for the US Army .. ehm for FF bug hunting! ^^ [21:09] No, but good luck getting them sponsored right now :) [21:09] :-) [21:09] persia: i will find a table, i'm at the university right now and my class has been canceled [21:10] nxvl: Excellent. [21:10] * persia is rubbing hands vigorously [21:11] * RainCT leaves the sugar sync for someone else :P [21:11] persia: tag is "uus-pre-ff-810" ? [21:12] sebner: Yes. [21:12] kk [21:13] mok0: \o/ [21:13] hattory: Are you about? Do you have time to discussion bug #250186 ? [21:13] Launchpad bug 250186 in gl-117 "Please merge gl-117_1.3.2-2 (universe) from Debian unstable" [Wishlist,Incomplete] https://launchpad.net/bugs/250186 [21:14] nhandler: Maybe you have insight? [21:14] mok0: Join the team. We're currently trying to crush https://bugs.launchpad.net/%7Eubuntu-universe-sponsors/+bugs?field.searchtext=&orderby=-importance&assignee_option=any&field.assignee=&field.bug_reporter=&field.bug_supervisor=&field.bug_commenter=&field.subscriber=&field.status_upstream-empty-marker=1&field.omit_dupes.used=&field.omit_dupes=on&field.has_patch.used=&field.has_cve.used=&field.tag=uus-pre-ff-810&field.tags_combinator=ANY&searc [21:14] h=Search [21:14] Except the URL works better if it's not hit by a buffer :) [21:15] * mok0 looks at the probably longest url ever seen [21:15] mok0: Also, anything else you can find that needs to beat FeatureFreeze, needs to be pushed in the next 225 minutes. [21:15] * ScottK-laptop hands persia http://tinyurl.com/ [21:15] persia: I am on the team [21:15] http://tinyurl.com/ubuntu810 [21:16] Bah. It's really just https://bugs.launchpad.net/%7Eubuntu-universe-sponsors/+bugs?field.tag=uus-pre-ff-810&field.tags_combinator=ANY&search=Search [21:16] that new custom alias thing is nice :) [21:16] persia: I was about to upload the linux-rt stuff at REVU [21:16] mok0: Excellent choice :) [21:16] persia: debdiff here: http://ks33313.kimsufi.com/~smarter/pkg/extremetuxracer_0.4-1ubuntu1.debdiff :) [21:16] persia: I cannot test it though [21:16] smarter: Stick it in the bug, and I'll pull, and run a test build. [21:16] You'll fix it if it's broken? [21:17] ready for blowing brain! [21:17] ScottK-laptop: Launchpad may be slow, but packages.debian.org is way worse :P [21:17] okay [21:17] persia: I'll try [21:17] party on! [21:17] persia: I also added a fix to bug #237830 [21:17] Launchpad bug 237830 in extremetuxracer "package planetpenguin-racer-gimp-dev None [modified: /var/lib/dpkg/info/planetpenguin-racer-gimp-dev.list] failed to install/upgrade: trying to overwrite `/usr/share/gimp/2.0/palettes/PPRacer---Default.gpl', which is also in package extremetuxracer-gimp-dev" [High,In progress] https://launchpad.net/bugs/237830 [21:17] what are we working at? [21:17] sponsoring queue? [21:17] RainCT: Use packages.qa.debian.org : it gets fewer hits, and tends to contain more useful links. [21:18] nxvl: There's 17 bugs in the sponsors queue that really need to be hit: https://bugs.launchpad.net/%7Eubuntu-universe-sponsors/+bugs?field.tag=uus-pre-ff-810&field.tags_combinator=ANY&search=Search [21:18] nxvl: It's also REVU day [21:18] ScottK: I will probably need an FF exception for the eee-applet [21:18] persia: subscribing mighty u-m-s O_o ^^ [21:18] persia: Emmet Day, remember? ;) [21:19] nxvl: http://qa.ubuntuwire.com/bugs/rcbugs/ lists some new upstreams, and we might want to push them. [21:19] persia: debdiff attached to bug 229136 [21:19] Launchpad bug 229136 in extremetuxracer "Please merge extremetuxracer 0.4-1 (universe) from Debian unstable (main)." [Undecided,Incomplete] https://launchpad.net/bugs/229136 [21:19] persia: i think sync are out [21:19] packages.qa.debian.org works, thanks :) [21:19] bug #229136 [21:19] RainCT: Not "Emmet" Day. No. [21:19] persia: since we need an archive admin for that [21:19] nxvl: Additionally, anything on MoM or mdt that would break FF but wants an update is fair game. [21:19] persia: hehe [21:20] nxvl: syncs aren't out. We just need to get them approved and subscribed to the archive admins in the next 220 minutes. [21:20] * Adri2000 notes that DaD nicely shows new upstream releases with bold red :) [21:20] what's mdt? [21:20] Adri2000: Excellent point. [21:20] Anything in RED on DaD ought get a look, especially as Debian is near frozen, so updates are only likely where required. [21:21] mdt is http://qa.ubuntuwire.com/multidistrotools/ : http://qa.ubuntuwire.com/multidistrotools/universe.html is probably the link most interesting to us. [21:21] * smarter bbl [21:21] persia, what are those "changelog.intrepid" and "changelog.historical" in linux-rt? [21:22] persia: hey, you uploaded uqm. wuhu \o/ [21:22] mok0: From what I understand, changelog.historical is from the kernel when it was all together, and changelog.intrepid is for the new linux-rt kernel package. [21:23] kernel packaging is rather frustratingly confusing, as it pulls in stuff from all over the place, and doesn't actually have any source. [21:23] sebner: I did say I would, didn't I? [21:23] sebner: Also, you got a special exception, as it didn't need to be uploaded today. [21:27] Did my connection drop again? [21:27] No. Hurrah! [21:29] Only 1 package left in "advocated packages", if there's someone up to it, please have a look. I already advocated it. [21:34] back [21:34] mok0: The other three may be archived? [21:34] emgent: norsetto \o/ [21:34] heya norsetto [21:34] emgent: Excellent :) [21:34] hi gents and ladies [21:34] norsetto: Welcome back :) [21:35] norsetto: 205 minutes left until FeatureFreeze :) [21:35] norsetto: hide or persia is going crazy :P [21:35] persia: :) [21:35] too late xD [21:35] now, rock'n'roll [21:36] * norsetto gets his defrosters ready [21:36] persia: did you saw. uqm amd64 build has a chroot problem. *give back* [21:36] norsetto: https://bugs.launchpad.net/%7Eubuntu-universe-sponsors/+bugs?field.tag=uus-pre-ff-810&field.tags_combinator=ANY&search=Search is the key link to keep empty, although it keeps getting more. [21:37] There's stuff on REVU, and DaD is highlighting any obvious FF-breaking merges in RED. [21:38] sebner: What's the URL to the build? [21:38] persia: http://launchpadlibrarian.net/17122329/buildlog_ubuntu-intrepid-amd64.uqm_0.6.2.dfsg-8ubuntu1_CHROOTWAIT.txt.gz [21:38] persia: I see there is some kind of very subtle hints you are trying to pass which is apparently lost on me [21:39] sebner: No, the link to the page that has that link. [21:39] persia: hehe. true https://edge.launchpad.net/ubuntu/+source/uqm/0.6.2.dfsg-8ubuntu1/+build/702471 [21:40] norsetto: Essentially, we've 201 minutes to sponsor everything that would otherwise require an FFe, and to get any new packages we want from REVU, or updated sources from Debian. [21:41] persia: oh, I apparently lost my ability to speack English [21:42] persia: seriously though, I'm off to bed, was a long day today for me [21:42] norsetto: Basta leggere [21:42] Ah, too bad. We could use your help. Sleep well. [21:44] err looked at wxwidgets, but can't find 2.8.8.1 [21:44] norsetto: nighty [21:44] devfil: Any ideas? [21:44] persia: let me read [21:45] night norsetto [21:45] night everybody [21:45] sebner: uqm given back [21:46] persia: wxwidgets2.8 2.8.8.1? [21:46] devfil: Yep. mok0 can't find it. [21:46] https://bugs.edge.launchpad.net/ubuntu/+source/wxwidgets2.8/+bug/251260 [21:46] Launchpad bug 251260 in wxwidgets2.8 "Please upgrade wxwidgets2.8 to 2.8.8.1 version." [Wishlist,Confirmed] [21:46] persia: :) /me is now going back to work and filing sync bugs \o/ [21:47] Excellent. Only 194 minutes left. [21:47] mok0: wxpython.org [21:47] you also can use get-orig-source provided with the package (best solution) [21:47] devfil: yes, I looked there [21:47] mok0: I'm archiving the three packages fully advocated on REVU. You've uploaded, right? [21:48] persia: yes [21:48] mok0: Thanks for the confirmation. Uploaded. [21:49] * persia gets distracted by real life and disappears for ~15 minutes [21:49] is someone else already looking at rsplib? [21:54] RainCT: not to my knowledge [21:55] mok0: uhm.. why do all descriptions in debian/control start by an empty line? [21:55] and is there a needs-packaging bug for it? [21:56] mok0: have you found the tarball? [21:57] devfil: no [21:57] devfil: I am trying to get the source package [21:58] mok0: you can use the actual intrepid package to download the new tarball [21:58] (found the needs-packaging bug) [21:58] just change the version on debian/rules and use get-orig-source [22:01] RainCT: Not in my experience. [22:01] Debian BTS is definitely faster. [22:01] mok0: I think the packaging is fine. [22:01] mok0: If you want me to advocate it and we can test later, that's fine. === Czessi_ is now known as Czessi [22:03] ScottK: ok, I will advocate it then [22:04] mok0: Since you uploaded it, it's automatically advocated by you. [22:05] mok0: I added advocation, so you can upload it. [22:05] mok0: Did you see I uploaded your other one? [22:06] ScottK: yes, I did, thanks a lot [22:06] mok0: I'm pbuilding rsplib.. will upload it if it build fine :) [22:07] *builds [22:08] ScottK: I uploaded the eee thingie. [22:09] ScottK: Thinking of getting the 901 when it appears in Denmark :-) [22:10] persia: have you testbuilt extremetuxracer yet? [22:10] 'cause it's already 11 PM here and I'll soon be off to bed [22:12] smarter: Not yet. I'll probably be another 30 minutes or so before I get to it. [22:12] 'kay [22:13] Anyone else have a gap sooner to help smarter be able to go to bed earlier? [22:13] :) [22:16] persia: http://launchpadlibrarian.net/17124866/buildlog_ubuntu-intrepid-amd64.pgbouncer_1.1.2-1ubuntu1_CHROOTWAIT.txt.gz === stefanlsd_ is now known as stefanlsd [22:17] emgent: What's the page that links that? [22:17] https://launchpad.net/ubuntu/+source/pgbouncer/1.1.2-1ubuntu1 [22:17] chroot problem in amd64 build box [22:20] dev week is gonna be great [22:23] stefanlsd: :) [22:24] So this is the end of new stuff in Intrepid? [22:25] ok, sorry to do this, but would someone be willing to sponsor a package update for me? [22:25] my usual sponsor is not here right now [22:25] http://people.ubuntu.com/~jamesw/packages/bzr-builddeb-2.0/bzr-builddeb_2.0~0ubuntu1.dsc [22:26] the packaging changes are trivial (debian/changelog, debian/NEWS, debian/copyright) [22:26] I've tested building, installing and using. [22:26] and I'm the upstream author. [22:29] RainCT: Did you take a look at rsplib? [22:29] mok0: thanks for uploading my two packages [22:30] james_w: they were important packages to get into ii [22:33] james_w: looking forward to play with them myself :-) [22:34] yeah, it could make our tools much more robust, and then some cool stuff may grow out of it. [22:35] mok0: thanks from me for gui-ufw [22:36] devfil: anything that makes ufw easier for users :-) === ScottK2 is now known as ScottK-laptop [22:37] mok0: I have discovered it reading brainstorm, it is really requested [22:38] devfil: cool. I don't spend much time reading brainstorm myself [22:39] some ideas are really interesting [22:40] devfil: I agree [22:41] mok0: yep, build fine.. uploading now [22:41] devfil: ubuntuforums and brainstorm make Ubuntu very special for users [22:41] RainCT: great, thx [22:42] mok0: I don't read much ubuntuforums, but I spend hours reading brainstorm [22:42] We have to make a big effort in the next cycle dedicated to REVU [22:43] persia: you're on it now? :) [22:43] smarter: Apparently my estimate was a little off. I'm waiting for a build to finish, but it's next in the queue. [22:43] I have the feeling that many REVU contributors are pretty frustrated [22:44] I have the feeling that nearly all REVU contributors are frustrated. We didn't really do much REVU this cycle, and it shows. [22:44] persia: ok, thanks [22:44] i prefer to work directly on debian versus revu. but the lenny freeze has bitten me [22:45] persia: btw, nixternal said that I can take over the coordinator pos. I've to mail -motu somewhen but I'm not sure if makes sense now with the freeze [22:45] directhex: +1 [22:45] I cannot support any plan to increase REVU efforts. [22:45] Why not just have people go to Debian? [22:45] hence mono-basic in revu. i'd rather it hit sid [22:46] RainCT: Most of the coordinator work over the freeze period involves cleaning up the old "Needs Work" packages and setting expectations properly for the next release. [22:46] I'd be happy if you want REVU Coordinator: I was afraid it would be me again next cycle :) [22:47] persia: if I want a package that I've uploaded in debian (but now in NEW) in ubuntu, do you suggest me to upload it now on REVU (is a really simple) or to request a freeze exception later? [22:47] persia: alright, I'll write a mail within the next days then :) [22:47] devfil: IF you think you can get two advocates in the next 133 minutes, upload to REVU. Otherwise, it's better to seek a freeze exception. [22:49] persia: it is a simple gtk gui for virtualbox and doesn't have problems at all [22:50] persia: Since it's been uploaded to Debian, I think one is enough. [22:50] maybe the best solution is to upload it now as it is not important to require a freeze exception [22:50] devfil: Freeze exceptions for New packages are very hard to get. [22:50] Can someone please try clicking on "google-gadget" on REVU? [22:50] I get a strange error [22:51] ScottK-laptop: I know, this is why I'm uploading it [22:51] ScottK-laptop: In that case, I would expect you to advocate based on it being in Debian NEW, to state your point :) But yes, otherwise I agree. [22:51] http://revu.ubuntuwire.com/details.py?package=google-gadgets [22:52] RainCT: ^^ Any ideas? [22:52] persia: Sync's of new packages from Debian don't take two sponsors. Only one. The fact that the mechanics might have to be a little unorthodox doesn't change that IMO. [22:52] I wonder if I add a custom error handler that tells people to upload to sid instead. [22:52] ScottK-laptop: It's not a package in Debian. [22:53] It's package that's been uploaded to Debian. A very fine distinction. [22:53] ScottK-laptop: I understand your point. On the other hand, I think it's easy enough to reflect that without changing the system. [22:53] Right. [22:53] ScottK-laptop: So whoever reviews the package can probably ask here and say "It's also in NEW", and get someone to ACK with little fuss. [22:54] (especially if the first person promises to upload) [22:54] Yes. [22:54] I'll be glad to if I'm around. [22:55] mok0: does the package have a changelog? :P [22:57] RainCT: you mean the google one? [22:57] RainCT: I can't get to it [22:58] yep. just fiex it [22:58] *fixed [22:58] mok0: the orig.tar.gz was missing for some reason and so dpkg-source -x wasn't executed [23:02] ScottK-laptop, persia: http://revu.ubuntuwire.com/details.py?package=vboxgtk [23:02] * ScottK-laptop looks [23:03] devfil: You have a comment. [23:04] ScottK-laptop: I removed also all papt stuff and changed the manpage "for the Ubuntu project" [23:04] for the horde! [23:04] devfil: Say that in a comment. [23:04] RainCT: thanks. Unfortunately the problems with that package are not yet fixed :-( [23:05] smarter: Why change from CDBS to non-CDBS? [23:05] persia: to match Debian [23:05] Oh. Am I looking at a debdiff from Ubuntu to new Ubuntu? [23:05] Can you attach a debdiff of your merge against Debian? [23:05] good idea, sorry ^^ [23:07] ScottK-laptop: replied [23:10] persia: debdiff uploaded [23:10] smarter: recollecting [23:13] ScottK-laptop: if you want a diff between Debian debian dir and Ubuntu debian dir let me know [23:13] * ScottK-laptop does svn up on his local copy of the papt repo. [23:14] ok [23:17] good night [23:18] devfil: debian/virtualbox-gtk is in Debian, but not your Ubuntu package. [23:18] mono-basic_1.9+dfsg-2_i386.changes uploaded successfully to localhost [23:18] Your Debian queue daemon [23:19] ScottK-laptop: it shoudn't be there [23:20] devfil: It's in the tagged copy of the debian/dir in the papt repo. [23:21] 100 minutes to go. Sponsors: not much left! [23:22] ScottK-laptop: uhm, maybe I forgot to remove it from svn, but as you can see in the install file it is not installed [23:24] ScottK-laptop: http://svn.debian.org/wsvn/python-apps/packages/vboxgtk/trunk/debian/install?op=diff&rev=1659&sc=1 [23:26] ScottK-laptop: substituted by http://svn.debian.org/wsvn/python-apps/packages/vboxgtk/trunk/debian/links?op=diff&rev=1659&sc=1 [23:28] smarter: Looks clean. Pushing. [23:28] persia: great [23:28] good night everybody [23:28] smarter: Sleep well, and thanks for staying up to look at this. [23:29] bonsoir smarter [23:29] hasta luego jpds [23:31] * jpds closes some ubuntu-dev-tools bugs before heading off himself. [23:31] devfil: Who sponsored it in Debian? [23:31] ScottK-laptop: POX [23:31] OK. [23:32] POX_ should apply for MOTU so he can advocate. [23:32] https://bugs.launchpad.net/%7Eubuntu-universe-sponsors/+bugs?field.tag=uus-pre-ff-810&field.tags_combinator=ANY&search=Search now has 18 bugs. Let's get them done in the next 88 minutes :) [23:32] gh... my wxwidgets2.8! [23:33] I know I don't have a build system capable of building that one :( [23:33] persia: the build logs are available on my ppa [23:33] mok0 has done wxwidgets before. [23:33] only them [23:34] devfil: Yes, but I only upload that which I can build (except when I make mistakes). Maybe I'm too conservative, but that's how I do it. [23:35] persia: yes, however I think that wxwidgets2.8 can get the freeze exception, 2.8.8.1 is a bugfixonly release [23:36] devfil: Advocated. [23:36] devfil: Sure, but if we can get it in now, it's less work for the motu-release team later, as we know we want it. [23:36] ScottK-laptop: Based on your previous assertion, if I ACK it also, will you upload? [23:36] Gah! Why does http://pastebin.com/f5b960558 run configure-stamp twice? [23:37] persia: Sure. [23:37] persia: uhm... it needs 48 minutes on ppa if I remember right to build, what do you think? [23:37] RAOF: configure is PHONY [23:37] RAOF, configure is what azeem said [23:37] RAOF: build should probably depend on configure-stamp [23:37] devfil: What's the REVU URL? [23:37] azeem: but configure-stamp isn't. [23:38] persia: it is a bug https://bugs.edge.launchpad.net/ubuntu/+source/wxwidgets2.8/+bug/251260 [23:38] Launchpad bug 251260 in wxwidgets2.8 "Please upgrade wxwidgets2.8 to 2.8.8.1 version." [Wishlist,Confirmed] [23:38] RAOF: well, my gut feeling; I can't cite the make manual chapter now :-/ [23:38] persia: or are you talking about vboxgtk? [23:38] or blame dh7 [23:38] I can't blame dh7; it never calls configure :) [23:39] phony has configure (which runs configure-stamp) and build (which runs configure which runs configure-stamp), no? [23:40] RAOF: hrm, could be a phony patch target imported from dpatch as well [23:40] or something like that [23:40] or maybe i'm just lost [23:40] Yes. So, build calls configure, which checks for configure-stamp; it doesn't exist, so configure-stamp is called. Then install calls build which calls configure which checks for configure-stamp which now exists [23:40] RAOF: however, it's outdated, as configure is PHONY [23:40] AIUI [23:41] devfil: vboxgtk [23:41] persia: http://revu.ubuntuwire.com/details.py?package=vboxgtk [23:41] (or whatever package was in Debian NEW) === superm1 is now known as superm1|away [23:41] That's the one. [23:42] ScottK-laptop: It's all yours. [23:43] RAOF: also consider running make -d -f debian/rules build or something [23:43] persia, ScottK-laptop: thanks also for this [23:43] devfil and persia: Uploaded. I'll archive it too. [23:46] Subject: mono-basic_1.9+dfsg-2_i386.changes is NEW [23:47] Only 74 minutes left, and still 18 bugs needing sponsoring. Does anyone else have free build cycles? [23:47] azeem: Aha. patch is phony, so always gets rebuild, triggering a rebuild of configure-stamp! [23:48] persia: I can test build if that is what you are after [23:48] persia: I'm uploading wxwidgets2.8 to my PPA [23:48] persia: I understand if that doesn't get you to where you want to be [23:48] james_w: Well, yes, but really I want sponsors to build the source, test the result, sign, and upload. I'm not sure how much you can help with that. [23:48] devfil: Doesn't help me, but might help someone else. [23:49] persia: not really, I'd only be weeding things out. [23:50] james_w: Well, if you've time and want to look at https://bugs.launchpad.net/%7Eubuntu-universe-sponsors/+bugs?field.tag=uus-pre-ff-810&field.tags_combinator=ANY&search=Search and see if you can find anything that isn't realy to go, that could be helpful. Even better if you can make sure it is ready to go before a sponsor gets to it. [23:50] persia: I'll do what I can [23:50] james_w: 8 of them are sync requests, which are probably the easiest place to start. [23:51] persia, does that mean whatever is not tagged uus-pre-ff-810 won't make it into intrepid? [23:51] * persia wants more processors and more memory and more minutes :) [23:51] * Laney screams [23:51] * ScottK-laptop considers that the only way to stop getting mail list invites for indirect subscriptions is to deactivate himself from ubuntu-dev. [23:52] jelmer: No. It means that the sponsors aren't reviewing things without that tag during the next 69 minutes, and anything that doesn't get uploaded in that time needs a Feature Freeze exception. [23:52] Laney: Why? [23:52] * devfil thinks that persia want to stop the time [23:52] Oh no worries, just got to make a small change [23:53] FF paranoia [23:53] Laney: Remember that you can still fix bugs post FF, just not introduce features. [23:53] persia: Yes, it's a package update [23:53] as in new version [23:53] althought the original sponsorship request was a couple of days ago, so I guess it'll be fine anyways [23:53] Yeah, that needs to happen right this moment, and if it takes you a while to do, you'll be too late. [23:54] Which bug? [23:54] bug #261158 [23:54] Launchpad bug 261158 in nanoweb "Please update nanoweb to 2.2.9" [Wishlist,Incomplete] https://launchpad.net/bugs/261158 [23:54] persia, ah, ok [23:54] (personally I'd leave the php4 alternatives in) [23:55] php4 is dead, and we want it that way. [23:55] * jelmer looks forward to filing 7 ff exceptions [23:55] php4 is dead, references to it ought to be dropped wherever feasible [23:55] Is it supported in any releases currently? [23:56] It's in Dapper, but it's not supported upstream, and unlikely to be well maintained in Dapper as a result. [23:56] But php5 is also in dapper... [23:56] * Laney removes [23:56] security support for php4 has stopped [23:56] Laney: Yeah, you need to update, push the new debdiff, and set the status to something better. [23:56] (from upstream) [23:56] I'll do it now, easy change [23:56] ajmitch: Indeed. [23:57] ajmitch: Want to help clear the queue? [23:57] Oh, and Good Morning :) [23:57] persia: for what? [23:57] * ajmitch is at work, been organising hardware upgrades & annoying out-of-hours work [23:58] ajmitch: FeatureFreeze is in 62 minutes, so we're trying to get everything listed at https://bugs.launchpad.net/%7Eubuntu-universe-sponsors/+bugs?field.tag=uus-pre-ff-810&field.tags_combinator=ANY&search=Search sponsored beforehand. [23:58] Oh, well, if you're busy at work, then maybe not so much :( [23:58] yeah [23:58] and I don't have an updated intrepid pbuilder [23:59] And you live down the wrong end of narrow tubes