/srv/irclogs.ubuntu.com/2014/03/01/#ubuntu-devel.txt

tewardsarnold, for the most part, "upstream" for the nginx package in relation to Ubuntu is Debian00:00
tewardin relation to Debian, "upstream" is nginx.org00:00
tewardand nginx.org *has* their own packages00:00
tewardthey're  not as admin-friendly though00:00
tewardsarnold, i don't *mind* an Ubuntu delta for this addition of an extra binary that builds nginx.org-upstream-only modules.00:01
tewardit's not *that* bad of a delta for me to keep working00:01
sarnoldI expect the nginx.org packages are designed to work identically regardless if you're on debian, ubuntu, gentoo, arch, or centos, right? :) hehe00:01
tewardsince that's just adding a control entry and an extra ruleset for the modules00:01
teward"identically"?00:01
tewardprobably00:01
tewardbut "identically" is an obscure statement if you are including centos in that list00:02
tewardsince selinux can be evil there with ngixn00:02
tewardnginx*00:02
* teward kicks his keyboard from here to /dev/null and back00:02
sarnoldoh sure, but that's not nginx's job to sort out :) hehe00:02
teward:P00:02
tewardno, that's the centos people's job00:02
sarnoldbingo00:02
tewardit's also not "nginx"'s job to maintain the debian package00:02
tewardthat's mostly maintained by non-nginx-upstream people afaict00:02
tewardsarnold, do we have anywhere on the wiki where we can document these things about certain packages?00:04
sarnoldteward: not that I know of00:05
tewardif all else fails I'll make an "NginxInMain" page in my own namespace regarding this, but...00:05
tewardi want *somewhere* publicly listed the reasoning for this00:05
sarnoldteward: very good idea.00:05
tewardeven if I have to create a page for it in wiki.u.c00:05
tewardactually, how does one subscribe to notices for wiki edits in a given page/section of the wiki? (if you know)00:06
sarnoldhrm, the 'new starter' page just says "subscribe to these regexs", doesn't mention how to do it..00:08
sarnold.. and clicking 'subscribe' on the front page of wiki.ubuntu.com just hangs00:08
tewardso does logging in right now00:09
tewardmaybe someone should poke sysadmin about that?00:09
teward(laggggggggggg)00:09
sarnoldteward: hey, the wiki is responsive again00:20
sarnoldteward: once you're logged in you can click on your username, then notification, and add regexs as you need; or, you can subscribe to an individual page with the 'subscribe' link00:21
infinityteward: As I asked before, why do we need yet another ngingx binary, why not just drop the offending module(s) from -light and call it done?00:54
infinityThen if we just reverse the full|light depends for the 'nginx' metapackage, we can toss that in main too.00:55
infinitysarnold: ^00:55
infinityLooks like light only ships one third-party module, so that would seem the easiest course of action.00:56
sarnoldinfinity: I had considered suggesting that first, but -light is lacking UWSGI, spdy, and webdav; I figured the first two are mighty important, and the last one is perhaps convenient for someone..00:57
infinitysarnold: Oh.  So you want, basically, -full or -extras, minus third-party?00:58
infinity(Can modules not be distributed as DSOs, do they really need to be built in?  That would make this so much easier to deal with)00:59
sarnoldinfinity: sure, I didn't notice much difference among all the standard modules, but things felt -different- in the third-party modules.00:59
infinityThen you'd just have nginx-core and modules-extra modules-full modules-third-party...00:59
sarnoldinfinity: no idea there, but that would feel so much intuitive to me :)01:00
infinityMan, these really are all statically linked.01:01
infinityIck.01:01
infinitySo much ick.01:01
infinity"Nginx modules must be selected during compile, run-time selection of modules is not currently supported."01:02
infinity\o/01:02
infinityI guess we're stuck with the current state of affairs, then.01:02
infinityAt least the rules looks like it would take 30 seconds to hack to support more flavours.01:04
tewardinfinity, if you mean like apache does01:55
tewardthat's planned01:55
tewardbut not implemented01:55
teward(yet)01:55
tewardwhile on the topic of apache, it increases disk i/o crazily, which is why people kinda like nginx :p01:56
tewardand other servers (still)01:56
tewardbut meh01:56
* teward was busy and didn't see your messages until now01:56
tewardinfinity, it does take about 30 seconds to hack, but to match waht sarnold wants... i have to go poke the upstream package and get a list of what they compile in01:56
teward(nginx *has* an upstream package, but it's not as administrator friendly)01:57
tewardi'm also stuck on windows until tomorrow01:57
tewardso i can't do squat until then01:57
sarnoldteward: no no, don't bother with checking the nginx.org packages, that's too much work :)01:58
teward:P01:58
sarnoldteward: just disable the modules listed in the debian/control file as "third party modules" in a new binary package01:58
tewardsarnold, ... right...01:58
tewardsarnold, i still have to poke around to see if certain things're enabled or not :p01:58
* teward yawns01:58
tewardsarnold, what about the metapackage01:59
tewarddo we leave that in universe, or do we put nginx-core or w/e i name the new binary as the dependency on that01:59
tewardsince i know enoug hpeople use just `apt-get install nginx` and expect it to work01:59
sarnoldteward: very good question. If I interpret infinity's suggestion loosely, we'd put nginx-main (or whatever) first in the list, then put the nginx metapackage in main also. but I really don't want to break existing users who might have installed 'nginx' but rely upon features from nginx-full02:02
tewardsarnold, i was considering naming it nginx-core, because it's just the core packages.02:02
tewardsarnold, in theory, could we do nginx-core|nginx-full|nginx-light?02:02
sarnoldteward: ah, that's a good name.02:03
sarnoldteward: yeah02:03
tewardthat way it doesn't break already-installed nginx-full/nginx-light + nginx metapackage installs02:03
tewardbut on new ones forces the use of -core02:03
sarnoldI don't know what will happen on dist-upgrade.02:03
tewardwell, this is why sbuild exists02:03
tewardand my staging ppa02:03
sarnold:)02:03
tewardand the five other testing PPAs I have02:04
tewardoh that reminds me, note to self, update my trusty VM02:04
tewardsince that's WAY behind and needs poked upwards before i can test02:04
tewardsarnold, i'm probably gonna do two forms of testing...02:05
tewardthe first making sure that i put the rules in in such a way that i can get the -core one to build02:05
tewardbefore I even get to testing the metapackage02:06
sarnoldtell me about it, my testing trusty vm just downloaded 600 packages. sigh. :)02:06
teward(the packaging isn't exactly "neat" or "easy" here)02:06
tewardsarnold, eww.02:06
tewardsarnold, i might just nuke the VM I have now and install with the latest beta image or smth o.o02:06
tewardsarnold, what's the timeline for the MIR changes, though, in terms of freezes I need to be aware of?02:07
tewardI know feature freeze already happened, but...02:07
sarnoldteward: we'll need to ask for a feature freeze exception; the fact that i didn't finish the MIR review ought to help encourage the release team to grant an ffe -- afterall, everyone -wants- nginx in, and this isn't exactly adding new features, just a few build-rules fiddling.02:08
tewardsarnold, right...02:08
tewardsarnold, you're gonna have to support the debdiff then when we ask for an FFe for this MIR...02:08
tewardand note we got in 1.4.5 to trusty while you were reviewing 1.4.402:09
sarnoldteward: yeah, it seemed easier to continue where I was :)02:09
tewardso any debdiffs're gonna be based off of 1.4.502:09
sarnoldthough they had fixed the only bug I found. haha.02:09
tewardheh02:09
tewardsarnold, ooo i forgot about the rest of the packaging02:14
tewardsarnold, http://bazaar.launchpad.net/~ubuntu-branches/ubuntu/trusty/nginx/trusty/files/head:/debian/02:15
tewardsarnold, this is far more than just 30 seconds of work02:15
* teward points at the other files02:15
tewardsuch as install, preinst, postinst, etc.02:15
* teward has a headache already >.<02:15
sarnoldteward: definitely, it'd take me most of an afternoon before I think I'd have built packages to test. and I'm ususally too optimistic.02:16
tewardsarnold, you were expecting about a ~50 lines debdiff?  probably safer to say closer to ~500 lines02:16
tewardthat much harder to get an FFe, maybe?02:16
sarnoldteward: well, 75 lines. but I hope it's not too bad..02:16
tewardi'm exaggerating, with 50002:16
tewardbut still02:16
tewardit's not gonna be "small" like some security debdiffs or segfault debdiffs02:16
sarnold*nod*02:17
tewardit's substantially larger :/02:17
sarnoldI just finished doing some 'new library' debdiffs for apparmor; despite how much time it took, the changes were actually surprisingly small..02:17
tewardi'm probably gonna end up cloning the nginx-full stuff and just tweaking it.02:19
tewardrename things to nginx-core and such02:19
tewardtrim out stuff that doesn't apply, and what not02:19
infinitysarnold: dist-upgrade will be fine, it's an OR dep.02:20
infinitysarnold: Sort of the whole point of OR deps is to give the user choice.02:20
sarnoldinfinity: thanks02:20
sarnoldinfinity: well, okay, it feels a bit more obvious when you put it that way :)02:20
infinityteward: It should be tiny... Add a package to debian/control, a new configure stanza in rules, and copy the .install files.02:21
infinity(Well, okay, not "tiny", but obvious and small from a reviewability perspective)02:21
tewardinfinity, true.  my only concern is if, like, something bad happens and it ends up turning into a hack job02:22
tewardwhich it *shouldn't* if i base it off what already exists for -full02:23
tewardinfinity, the debdiff's gonna catch all the new .install, .pre* etc. files though02:23
infinityYeah, that's fine.02:23
tewardthat's what i mean by being "more than would normally be expected"02:23
tewardbut this is a project for tomorrow, i'm still stuck on this [WORDS REMOVED] Windows system.02:23
infinityI could just whip it up now. :P02:24
tewardinfinity, i'd like to put my name on the debdiff though :p02:25
tewardinfinity, besides, i need something to do tomorrow02:25
tewardrather than sit on my butt doing nothign02:25
tewardoh good this ISO's done downloading (finally, after 4 hours)02:27
* teward boots into Linux02:27
infinityteward: I'm kinda halfway done.  But you're welcome to have it when I am. :P02:27
infinityteward: http://paste.ubuntu.com/7013893/02:39
infinityteward: Merry Christmas, you get to write a changelog that doesn't suck. ;)02:39
infinitysarnold: ^-- That look like what you had in mind?02:39
sarnold"stuff and things" :) haha02:39
sarnoldteward: hey you were closer, 297 line debdiff02:40
sarnoldinfinity: ACK. looks great. :)02:42
infinitysarnold: Builds fine, debdiffs of the binaries look sane.02:47
tewardsarnold: infinity: yeah, that's about what I get, i'm test-building in sbuild before i make the debdiff uploaded with my name on it instead02:57
=== _salem is now known as salem_
tewardbecause I'm crazy paranoid02:57
tewardand i want to make sure it actually builds here too02:57
tewardsince i have two custom builds that'd be based off of this in a private apt repository on my network02:57
teward(so I need to know it builds :P)02:57
=== salem_ is now known as _salem
infinityteward: Did diff I gave you builds and produces sane binaries, already tested.  But do test again.02:58
infinityteward: And if your diff is significantly different from mine, I'd be curious why.02:58
infinity(Note, if you were tempted to reproduce the Breaks/Replaces bits, those are unnecessary, since that old version of -core never existed)02:59
tewardinfinity: yeah i did add that, but i can remove that from the debdiff before i submit it03:00
teward(it may be unnecessary, but i added it in because consistency)03:00
tewardthey look basically identical, save for the debian/changelog entry03:01
teward... note to self, don't let sbuild chroots go for weeks without updating >.>03:01
tewardinfinity: there will be minor differences, like, in the rules, I put the core build-dir after the existing config rules and builddir rules, and put it at the end of flavours.  i could easily switch them around to match your changes03:07
pranith__can someone point me how to create a package from source? I am trying to package gnu global which is here: https://code.launchpad.net/~bobby-prani/gnuglobal/global-6.203:08
pranith__I am following instructions here but getting errors: http://packaging.ubuntu.com/html/packaging-new-software.html03:09
tewardsarnold: infinity: Am I being too verbose in my changelog entry here?  http://paste.ubuntu.com/7013991/03:11
teward(opinions and suggestions welcome)03:11
darkxstpranith__, we are not mind readers, post logs of the failure ;)03:14
sarnoldteward: perhaps modify the nginx-core.* line to say which ones you copied from -- but looks good to me, thanks03:14
tewardsarnold: that one's easy :p03:14
pranith__darkxst, I created a branch of upstream source on launchpad and I am not seeing the source files in it...03:17
pranith__so when I try to compile it.. it is erroring out when applying the patches03:17
tewardsarnold: infinity: this look about right to ya?  http://paste.ubuntu.com/7014014/03:18
teward(that's the entire debdiff I have)03:18
Noskcajpranith__, Please link us a build log03:20
sarnoldteward: line 85 looks off, nginx-core-dbg Depends: on nginx-full, not nginx-core03:23
sarnoldteward: line 269 looks off, it does a cd $(BUILDDIR_full) instead of $(BUILDDIR_core)03:26
tewardsarnold: oops03:30
tewardsarnold: that it?03:31
sarnoldteward: it's all I spotted :)03:31
tewardsarnold: http://paste.ubuntu.com/7014046/ is the version that includes those fixes, if you'd like to go over it or have others go over it before i upload the .debdiff and attach to the MIR, feel free to.  :)03:32
sarnoldteward: both nginx-full and nginx-core have a Description that includes "(standard version)" -- it might be worth changing the nginx-core and nginx-core-dbg Descriptions to say "(core version)" so that apt-cache search nginx | grep ^nginx  will show a difference between the packages03:40
infinityteward: ubuntu2, not ubuntu1.1 ... And all the diffs between mine and yours look to be mistakes.03:41
* teward grumbles03:41
infinityhttp://paste.ubuntu.com/7014075/03:41
infinitySo, description issues, line-wrap issues, and whitespace issues.03:42
tewardyeah...03:42
tewardthat's probably a side effect of me being tired >.>03:42
infinitySmall mistakes, mind you, but I'm anal. :P03:45
tewardinfinity: the whitespace issue on the rules file i don't see03:45
tewardi think i actually *fixed* that...03:45
infinityteward: The diff you pasted has an extra tab there that doesn't need to be.03:46
infinityWhich doesn't break GNU make anyway, but meh.03:46
tewardahhh03:46
tewardinfinity: okay, see, if there is an extra tab in there, gedit can't find it.  http://paste.ubuntu.com/7014088/ doesn't seem to have that extra tab where your diff of the diffs says it should be03:50
* teward yawns03:50
tewardi should seriously probably go to bed >.>03:50
teward(and thanks for checking these things though)03:50
NoskcajCould someone please sponsor a few packages? The queue is now on 50 different things03:55
tewardinfinity: i do kinda want to get this uploaded, though, so hopefully there's nothing wrong with this debdiff (i've remade it enough xD)03:55
tewards/uploaded/debdiff uploaded to the Launchpad bug/03:55
infinityteward: That's missing the extra tab, but has an s/core/full/ bug.03:58
tewardgrrrr03:58
infinityteward: Do you need a sponsor for this?03:58
infinityhttp://paste.ubuntu.com/7014124/03:58
infinityIf so, I'll just fix the three issues there and upload.03:58
tewardinfinity: the procedure is upload to the Launchpad bug, get FFe (if nobody yells at the debdiff), then upload03:58
tewardunless you can also approve an FFe03:59
tewards/upload/find a sponsor to upload to trusty/03:59
infinityI can.03:59
infinityMy sponsoring would be tacitly approving the FFe at the same time. :P03:59
* Noskcaj directs infinity to bug 128293704:01
ubottubug 1282937 in xfburn (Ubuntu) "FFe: Please package xfburn 0.5.0" [Undecided,New] https://launchpad.net/bugs/128293704:01
tewardinfinity: http://paste.ubuntu.com/7014141/ is the latest iteration, please check04:01
tewardinfinity: and i will need a sponsor, I have yet to finish a PPU application and file it04:01
tewardbecause (1) lazy, (2) work, (3) [secret reasons]04:02
tewardinfinity: at least, i think that last iteration is right04:03
tewardit may not have copied right :/04:03
* teward yanws04:03
tewardbleh, i can't even type "yawns" right >.>04:03
infinityteward: That iteration's better, except for the space in control that's driving me nuts that I'll strip before I upload. :)04:04
tewardinfinity: heheh, the extra space in the control file is really irking you isn't it xD04:05
infinityYou have no idea.04:05
infinityAnyhow, if you're happy with this, I'll upload it.04:05
YokoZarinfinity: Were you the one I was supposed to poke ~ wine1.6 being stuck in proposed04:06
YokoZardue to britney not liking the cross-arch wine1.6 dependency04:06
tewardinfinity: lemme upload it to the launchpad bug04:06
tewardbecause i'm in on a temporary folder that'll get nuked after a while04:07
tewardso i want this debdiff to be visible there :P04:07
infinityYokoZar: Maybe.04:07
infinityteward: Oh, the MIR also mentions that this needs to be bumped to the lua version in main while we're at it.04:07
* infinity test builds with s/5.1/5.2/04:08
tewardinfinity: say what now?04:09
tewardinfinity: did I miss that?04:09
infinityteward: Yes.04:09
* infinity test builds with lua5.2.04:10
pranith__Noskcaj, I created a local branch from lp:global and added the necessary debian files04:11
pranith__when I try to give the command bzr builddeb ... it errors out saying not able to get orig-source04:12
tewardinfinity: if that works i'll bump the build-deps, but the lua dep is for the universe package :/04:12
tewardinfinity: and do let me know if it works, as i can add the change to the changelog and the debdiff04:15
infinityNope, it's going to need a patch, probably.04:15
pranith__where do I added the upstream source info so that bzr get-source-package does not fail?04:16
tewardinfinity: if and only if the Lua module, which is third party, works with 5.204:16
pranith__add*04:16
infinityteward: That sentence didn't make a whole lot of sense. :P04:16
pranith__or create a source tar ball from my current tree while packaging?04:17
tewardinfinity: you're right, i'm tired, it happens04:17
tewardinfinity: your "it's going to need a patch, probably" statement is throwing me off, which needs the patch, the nginx lua module? or something else?04:18
pranith__darkxst,04:20
pranith__?04:20
tewardinfinity: actually, I checked the upstream source for that module - https://github.com/chaoslawful/lua-nginx-module04:21
tewardinfinity: it doesn't support 5.2 yet.04:21
infinityWhere there's a will, there's a way.04:23
tewardinfinity: the only option to address that would be to disable the module, which means I think we can then drop the Lua build-dep04:23
infinityThat's hardly the only option. :)04:23
sarnoldhow bad is the breakage?04:23
tewardinfinity: if you've got a better option i'll take it :P04:25
tewardinfinity: i expect, though, that there'll be a FTBFS, and unless you can recode the module for 5.2, well...04:25
tewardthen there is no patch to fix it04:25
teward(yet)04:25
tewardokay, i can't stay up any more without running the risk of passing out over my keyboard, if you find a fix let me know, infinity, but use a privmsg, because otherwise I might miss it04:27
* teward is going to bed04:28
sarnoldwow, looks like lua5.2 dropped a -lot- of stuff: http://www.lua.org/manual/5.2/manual.html#804:28
sarnoldg'night teward, have a good weekend04:28
tewardis this channel logged on the irclogs?04:28
tewardif it is then i'll go digging tomorrow for any highlights i got :/04:29
teward... i answered my own question04:29
tewardg'night.04:29
Noskcajpranith__, Make the bzr branch with bzr branch lp:ubuntu/global04:57
infinityteward: Okay, I took a stab at porting it, but it's a more significant effort than I have time for tonight.04:58
infinityteward: Talk to me on Monday if you want some pointers, or nag upstream to fix it. :P04:58
=== ev_ is now known as ev
toclaxHi, I want contribute to ubuntu with code and repair packages but I don't know how start... someone could guide me?11:53
=== freeflying is now known as freeflying_away
=== freeflying_away is now known as freeflying
=== freeflying is now known as freeflying_away
=== Lutin is now known as Guest30483
tewardinfinity: upstream fixing it would be lovely, but I don't think they're even taking a stab at it yet based on their github17:21
tewardinfinity: i poked upstream for that lua module and they said they'd take a look at getting it ported to 5.2 today, or at least compatible.  I hope upstream knows what evil they're going to be facint18:30
Laneymlankhorst: Do you have some useful way to identify wine fixes? 1.6 broke an application for me vs. 1.4 which works again with 1.7.13 from the ppa19:16
NoskcajCan someone please review https://code.launchpad.net/~noskcaj/ubuntu/trusty/xfdesktop4/merge ? It fixes a bug with over 140 affected users19:40
rbasakinfinity, sarnold, teward: just reading scrollback. I'm interested to hear opinions (from upstream, maybe) about how useful the pieces that we'll have in main will be to end users. Will they all end up having to the bits in universe instead, and in that case, how useful is the MIR? I don't mean to imply one answer or another; I'm just asking the question.19:45
mlankhorstLaney: no, in general wine has weird cycles :\20:14
Laneyso it'd be good to get this fix, whatever it is, into 1.6 ...20:15
mlankhorstyeah but without a reverse regression test.. no idea20:16
mlankhorstmaybe wine appdb has information20:16
Laneynein20:17
mlankhorstdoesn't even say which wine version started working? in that case you're on your own :x20:17
jtaylorI also have a wine fix for 1.4 I'd like in but I'm very confused with the current status20:18
jtaylordo I stillm need to bother with 1.4?20:18
Laneytrusty has 1.6 now20:19
jtayloroh it migrated20:19
jtaylornice20:19
mlankhorstLaney: what application?20:20
jtaylorbut the 1.4 still is in the archive?20:20
Laneymlankhorst: http://appdb.winehq.org/objectManager.php?sClass=version&iId=2641020:22
mlankhorstso what broke?20:23
LaneyIt could launch the application but it'd just give me a dialog saying "YNAB has encountered a problem"20:26
Laneythere was a 'more details' button but it had 'null' for the stack trace so that's not very useful20:27
knoctedo the unity devs hang out here?20:30
mlankhorstyeah, installing wine1.6-dbg{,:i386} package might help20:30
mlankhorstbut it seems like it's using its internal handler which makes things harder20:31
mlankhorstis there anything useful in the console when it crashes?20:31
Laneythis dialog was internal to the application20:31
Laneyit was handling the crash somehow20:31
mlankhorstyeah, anything in the console window at the time of crash?20:31
Laneynothing useful20:31
Laneycan I downgrade back to 1.6?20:32
Laneyit did some 'upgrading .wine' thing20:32
mlankhorstno idea then, I would try to install older wine1.7 packages, find the first workng one20:32
mlankhorstyeah usuall20:32
mlankhorstusually*20:32
Laneygetting those is going to be a pain20:32
Laneyoh actually they're here https://launchpad.net/~ubuntu-wine/+archive/ppa/+packages?field.name_filter=&field.status_filter=superseded&field.series_filter=trusty20:32
mlankhorsttry the oldest one for saucy first20:35
mlankhorstthen you know how much of a pain it will be :p20:35
Laneylaunchpadlib is a beautiful thing20:42
Laneymlankhorst: bad news, 1.7.8 is the oldest available and it works20:51
mlankhorstfun20:57
Laneycan you give me 1.7.4 debs?20:58
Laneyor older20:58
albertsHi! Maybe someone here are able to help me regarding gtk? http://stackoverflow.com/questions/21969436/how-to-make-gtkplug-transparent-so-that-gtksocket-background-is-seen.21:01
knoctewhere's the source code of unity that checks the UBUNTU_MENUPROXY env var? https://launchpad.net/unity doesn't contain this check21:06
knoctealberts: I guess you would have better luck in irc.gnome.org/gtk+21:07
Noskcajdebfx, Is it worth packaging the latest steam bugfix release for trusty? Changes are at http://paste.ubuntu.com/7018443/21:20
Noskcajbdrung, Could you package python-versiontools for debian? It's needed to fix the gevent-socketio ftbfs in ubuntu (and should be a build-depend of gevent-socketio in debian)21:44
bdrungNoskcaj: yeah, i could do that. can you send me a reminder to benjamin.drung@profitbricks.com?21:48
knoctewhere's the source code of unity that checks the UBUNTU_MENUPROXY env var? neither https://launchpad.net/unity nor https://code.launchpad.net/~ubuntu-branches/ubuntu/trusty/indicator-appmenu/trusty contain this check21:49
mdeslaurknocte: http://bazaar.launchpad.net/~ubuntu-branches/ubuntu/trusty/unity-gtk-module/trusty/view/head:/src/main.c#L82621:59
knoctemdeslaur: great! thanks22:00
mdeslauryw22:00
=== jackson is now known as Guest95629
=== jono is now known as Guest92194
=== Guest95629 is now known as Noskcaj
tewardrbasak, I think some people rely on the third-party stuff, but rely on nginx-extras for that.  Ultimately, you may be right, people're going to use the bits in Universe over the stuff in Main.  Either way, I'll keep on maintaining it, but I think jcastro is gonna look like an idiot for saying it is likely to get into Main in his blog post (which has now ended up pretty much everywhere)23:26
tewardin the instance that we don't ahve something in main23:26
tewardinfinity, sarnold: ^23:26
stgraberwell, people shouldn't blog about a package getting moved into main until the MIR has actually been approved ;)23:30
tewardstgraber, tell that to jcastro23:31
tewardi think there's a log about it in the community team channel, where I called him out on that23:31

Generated by irclog2html.py 2.7 by Marius Gedminas - find it at mg.pov.lt!