[14:26] <JJ> I have following scenario with studio: 1. Firefox and youtube works 2. Start LMMS (uses Jack) 3. Close LMMS 4. Try youtube and it does not work anymore. Is it supposed to work like this??
[23:44] <studio-user> join
[23:58] <studio-user> cbwolfubuntu where are you?


[00:07] <geser> I don't have a simple solution at hand
[00:08] <geser> you probably need some repository software and use this repository inside pbuilder (or use a PPA)
[00:09] <bcurtiswx> geser: ok so if i upload the successful package to PPA, when it comes time to upload the new ones.. how do I tell THAT to use my repository?
[00:10] <RAOF> bcurtiswx: I recently discovered that if you're using pbuilder-dist, it'll bind mount & add a /var/cache/archive to your sources.list in the chroot.
[00:10] <bcurtiswx> RAOF: i see this, but it still didn't recognize my updated package
[00:11] <RAOF> Did you make a Packages.gz file, and update the pbuilder?
[00:11] <geser> you can use your PPA with the backported packages in your pbuilder (and your PPA will automatically use your packages from your PPA to build later uploads)
[00:11] <RAOF> So if you copy the .debs you want to /var/cache/archive/lucid, then build the Packages.gz (running apt-ftparchive packages lucid/ | gzip -9 lucid/Packages.gz should do it), pbuilder-dist will pick them up.
[00:12] <bcurtiswx> RAOF: im backporting these to karmic so instead would it be /var/cache/archive/karmic  ?
[00:13] <RAOF> Yes.
[00:14] <bcurtiswx> RAOF: im guessing Packages.gz is really like empathy*.gz or telepathy-glib*.gz .. right?
[00:14] <RAOF> No, Packages.gz is the file that lists all the packages in the archive.
[00:14] <bcurtiswx> pbuilder makes a karmic-base.gz
[00:14] <RAOF> Yeah, but that's a whole karmic system, zipped up.
[00:15] <RAOF> This is different; you're making a repository.
[00:15] <bcurtiswx> RAOF: ok
[00:15] <RAOF> pbuilder won't pick up random .debs from anywhere; it'll only grab them from a repository.
[01:23] <bcurtiswx> to have pbuilder-dist save what I do in the login  ... how do i?
[01:29] <RAOF> pbuilder-dist lucid login --save-after-login
[02:25] <Nitsuga> hello
[02:25] <Nitsuga> i think there is a problem with the main Ubuntu mirror
[02:26] <Nitsuga> it's impossible to download libmysqlclient16 because of a 403 error
[02:26] <Nitsuga> W: Failed to fetch http://archive.ubuntu.com/ubuntu/pool/main/m/mysql-cluster-7.0/libmysqlclient16_7.0.9-1_amd64.deb
[02:26] <Nitsuga>   403  Forbidden [IP: <IP_ADDRESS> 80]
[02:26] <Nitsuga> it here the right place to report that?
[02:27] <Pici> Nitsuga: Theres an issue with the package, the permissions were changed on the repo so that people do not inadvertantly upgrade to a broken package.
[02:27] <Nitsuga> ohh  I see...
[02:28] <Nitsuga> ok thank you
[02:28] <Pici> Sure, np
[02:52] <paissad> i'm getting overbooked ... actually the software i was packaging uses much other software during the build (softwares that have their own license/copyright ... but fortunately they are totally free & source code available ) .... i'm afraid of the huge work http://code.google.com/p/ps3mediaserver/source/browse/#svn/trunk/ps3mediaserver/lib
[02:53] <paissad> the package i'm working on uses all these .jar & .zip files .... ^^
[02:54] <paissad> i've been packaging this soft for almost 3 weeks & i just don't know if  can continue the work to split each software in it's own .deb package
[02:55] <paissad> i feel so fucked :( !
[02:55] <maco2> paissad: watch your language, please
[02:55] <paissad> sorry :)
[03:11] <bcurtiswx> anyone know why Rejected:empathy_2.29.90-0ubuntu2~bcurtiswx.dsc: format '3.0 (quilt)' is not permitted in karmic.
[03:11] <bcurtiswx> how i may fix this?
[03:11] <micahg> bcurtiswx: drop source format 3 :)
[03:11] <bcurtiswx> micahg: where is it defined?
[03:11] <micahg> debian/source/format
[03:12] <bcurtiswx> so to get rid of it..??
[03:12] <micahg> yeah, you can delete the file
[03:12] <micahg> for karmic
[03:12] <micahg> bcurtiswx: if you don't have an .orig.tar.gz, you might have to make one
[03:18] <bcurtiswx> micahg: http://paste.ubuntu.com/378095/
[03:18] <bcurtiswx> i removed the format file
[03:18] <bcurtiswx> and it then gave me that error
[03:19] <micahg> bcurtiswx: was quilt dropped from the package?
[03:19] <bcurtiswx> idk
[03:19] <micahg> bcurtiswx: is there still a debian/patches dir?
[03:20] <bcurtiswx> yes
[03:20] <micahg> k
[03:20] <micahg> idk
[03:20] <bcurtiswx> :'(
[03:22]  * micahg had simple cases
[03:22] <bcurtiswx> anyone else know what i should do?
[03:24]  * bcurtiswx pokes room
[03:28] <bcurtiswx> http://paste.ubuntu.com/378095/  anyone?
[03:31] <bcurtiswx> micahg: is there another format of quilt I can try??
[03:31] <bcurtiswx> or another format ?
[03:35] <bcurtiswx> is there a place I can go to find out?  this is the place as far as i know
[03:38] <bcurtiswx> JontheEchidna: you've seen my problem before.. any suggestions?
[03:39] <micahg> bcurtiswx: this is the right place
[03:40] <JontheEchidna> hmm, I don't really touch gnomish things. maybe you have the wrong person?
[03:40] <bcurtiswx> JontheEchidna: you've seen format '3.0 (quilt)' is not permitted in karmic
[03:40] <bcurtiswx> do you know how to avoid that ?
[03:40] <micahg> bcurtiswx: the answer to that is return to source format 1
[03:41] <bcurtiswx> bug #522381 is what i'm looking at
[03:41] <JontheEchidna> yes, you cannot use source format 3 in karmic
[03:41] <JontheEchidna> ah
[03:41] <JontheEchidna> Riddell thought I wanted a straight no-changes backport
[03:41] <JontheEchidna> and missed my debdiff
[03:41] <JontheEchidna> where I ported the package back to source format 1
[03:41] <suji11> when will be the freezing date for lucid?
[03:42] <JontheEchidna> I'm not a gnome expert, but popping all the patches and removing the .pc dir may fix your issue
[03:42] <bcurtiswx> sorry to be newbie.. but how would i "pop" all the patches
[03:42] <micahg> suji11: feature freeze is thursday
[03:42] <JontheEchidna> quilt pop -a
[03:42] <JontheEchidna> unapplies them all, basically
[03:43] <JontheEchidna> then you'll want to port it back to using quilt.mk or whatever empathy was using before source format 3.0
[03:44] <JontheEchidna> might not hurt to look in bzr for what changes were made to convert empathy to 3.0, and then reverse those
[03:44] <suji11> micahg: tomorrow? they add the packages from revu.ubuntuwire.com ?
[03:45] <bcurtiswx> JontheEchidna: ok thx
[03:45] <micahg> suji11: not necessaril
[03:45] <micahg> y
[03:46] <hyperair> suji11: tomorrow we stop accepting new packages from revu.
[03:52] <suji11> hyperair: oh! my package iok is in revu. but it is not advocated yet. but one person will advocate in one or two days need another one for advocate.
[03:52] <suji11> http://revu.ubuntuwire.com/p/iok
[03:53] <suji11> then my package won't come in lucid?
[03:53] <hyperair> suji11: i'd take a look at it, but my upload privs haven't arrived =\
[03:53] <hyperair> it won't appear in lucid unless another MOTU gives you your second advocate and uploads it before FF
[03:57] <suji11> hyperair: ok, will you advocate this package?
[04:00] <hyperair> suji11: i can't until my advocating/upload privs appear.
[04:01]  * hyperair pokes persia
[04:01] <hyperair> technical glitches still going on?
[04:02] <nigelb> how to i apply a git patch to something versioned in bzr?
[04:02] <nigelb> trying to use the upstream patch to the source maintained in LP
[04:03] <suji11> hyperair: what?
[04:04] <hyperair> suji11: i became a MOTU 12 hours ago. my privileges haven't activated yet.
[04:04] <hyperair> nigelb: patch -p1 -i
[04:04] <nigelb> hyperair: ah, the -i
[04:04] <hyperair> nigelb: without the -i, you'd use < patch
[04:04] <suji11> hyperair: ok , can i ask persia about advocating my package?
[04:05] <nigelb> hyperair: then I'm running into the same trouble
[04:05] <nigelb> I'm getting "patch unexpectedly ends in middle of line"
[04:05] <nigelb> does patch have trouble with blank lines?
[04:05] <hyperair> suji11: well i'm not sure he likes to be pinged randomly for advocating a package. i'm pinging him because he was the one who told me about there being some technical glitch some hours ago
[04:06] <hyperair> nigelb: it might.
[04:06] <nigelb> hyperair: work around is to remove the extra lines or to not use patch command?
[04:06] <hyperair> nigelb: the patch was probably malformed to begin with if you're getting issues like that.
[04:06] <suji11> hyperair: ok ok. i just ping him, hope he will help:)
[04:07] <hyperair> nigelb: i had some issues regarding a patch attached via email once. dunno what happened
[04:07] <nigelb> hyperair: was posted by upstream dev
[04:07] <hyperair> nigelb: link?
[04:07] <hyperair> nigelb: you could remove the last chunk of the patch, and hand-apply it.
[04:07] <nigelb> https://bugzilla.gnome.org/show_bug.cgi?id=605694
[04:08] <hyperair> nigelb: http://bugzilla-attachments.gnome.org/attachment.cgi?id=152824 this one?
[04:08] <nigelb> yep
[04:09] <hyperair> nigelb: did you save it, or did you copy paste it into a text editor?
[04:09] <nigelb> save it
[04:09]  * hyperair tries
[04:09] <hyperair> er where's the source tree i should be poking?
[04:10] <nigelb> hyperair: https://code.launchpad.net/~ubuntu-branches/ubuntu/lucid/gnome-media/lucid
[04:10] <nigelb> you have to branch the code
[04:10] <hyperair> nigelb: could you try this: http://stackoverflow.com/questions/1987784/patch-patch-unexpectedly-ends-in-middle-of-line
[04:10] <hyperair> basically echo >> patch
[04:11] <hyperair> the patch is missing a trailing new line
[04:11] <hyperair> which is strange, because git always puts a trailing new line.
[04:11] <hyperair> it must have been truncated by BGO
[04:12] <suji11> persia: Need advocate my package here http://revu.ubuntuwire.com/p/iok .
[04:13] <nigelb> lemme try again
[04:17] <lightnin> Please check out this package. 100000 kids need to learn to program so we can breed the next generation of FOSS champions. http://revu.ubuntuwire.com/p/scratch
[04:39] <lightnin> Anyone around? I have some questions about my package.
[04:41] <suji11> lightnin: hi
[04:42] <lightnin> suji11: Greetings! I'm trying to get a package into multiverse in time for feature freeze. Can you take a look and advise? http://revu.ubuntuwire.com/p/scratch
[04:47] <suji11> lightnin: sorry, i'm not a MOTU. Just look the description of your package, looks nice. And am also upload my package in revu http://revu.ubuntuwire.com/p/iok . it's also waiting for advocate.
[04:47] <lightnin> suji11: Ah, thanks for looking! Nice to speak with someone anyway. :)
[04:48] <suji11> lightnin: :)
[04:48] <nigelb> suji11, lightnin: Can you try after say 8 hours or so?  Europe and US would be awake and you'd have better luck here
[04:49] <suji11> nigelb: ok, thanks for this information :)
[04:49] <lightnin> nigelb: Thanks for advice! Any tips on how to get help from MOTUs this late in the game?
[04:50] <nigelb> nope.  I dont really upload to revu, so I dont have much clue about that
[04:50] <nigelb> I mostly apply downstream patches and the likes
[04:50] <lightnin> nigelb: Ah, thanks all the same.
[04:50] <micahg> lightnin: be patient :)
[04:51] <lightnin> suji11: Cool software you have there! I think scratch may support indic - do you see it here? http://info.scratch.mit.edu/Languages
[04:52] <lightnin> micahg: I'll certainly try! We'd just very much like to get into multiverse for Lucid. Lots of schools running Ubuntu have asked for this.
[04:53] <micahg> lightnin: you might want to poke the edubuntu devs then
[04:54] <lightnin> micahg: Ah, where would I find them? Sorry - very new to this sort of thing.
[04:54]  * micahg checks
[04:55] <suji11> lightnin: I would like to translate the scratch in Tamil. What are the steps should i follow for that?
[04:59] <lightnin> suji11: Wonderful! This page describes how: http://info.scratch.mit.edu/Translation . But first, you can install Scratch from the ppa: https://launchpad.net/~scratch
[05:01] <lightnin> suji11: Also, I think this project was made by a child who speaks Tamil? http://scratch.mit.edu/projects/ks00007/812597
[05:02] <lightnin> suji11: That's an example of a project made with the free programming language for kids I'm trying to get into Multiverse:Scratch. Once you have Scratch installed, you can download this project and view and remix the source code.
[05:02] <suji11> lightnin: ok
[05:13] <fabrice_sp> rhpot1991, it seems that there is a new upstream version for hdhomerun-config-gui
[05:25] <superm1> fabrice_sp, i thought the changes were only for non-linux platforms though
[05:26] <fabrice_sp> superm1, could be: I've not been able to find any upstream changelog :-/
[05:27] <superm1> fabrice_sp, http://www.silicondust.com/downloads/hdhomerun_software_changelog
[05:27] <fabrice_sp> it seems I haven't searched enought :-D
[05:29] <fabrice_sp> superm1, so what is your recommendation? Upload 20100121? (I assume this is the tested version)
[05:30] <superm1> fabrice_sp, i'd say upload what's on revu.  it's what's been tested and verified working.  no need to go and needlessly go and pull a new version in especially if there is nothing relevant to hit before FF in the new version
[05:31] <fabrice_sp> ok: you confirmed what I thought
[05:32] <fabrice_sp> uploaded
[05:32] <superm1> rhpot1991, ^
[05:33] <rhpot1991> thanks fabrice_sp and superm1
[05:34] <fabrice_sp> thank to you ;-)
[07:40] <abogani> Hi All, I have just converted my package to '3.0 (quilt)' dpkg format and now REVU say me that "Warning! This package could not be extracted; there's no browsable directory for it on REVU. ". Anyone already know what is the problem? I should come back to '1.0' ? Thanks in advance!
[07:43] <lifeless> REVU doesn't do3.0 yet AFAIK
[07:43] <lifeless> its  alittle out of date
[07:44] <abogani> lifeless: First of all thanks! Now what I should do?
[07:44] <abogani> return to '1.0'?
[07:46] <RAOF> abogani: You can ignore that warning; people can easily just download your source package from revu.
[07:47] <abogani> RAOF, lifeless: Ok. Thanks and sorry for disturb.
[07:50] <RAOF> That's fine.  You don't learn if you don't ask.
[08:28] <dholbach> good morning
[08:35] <suji11> dholbach: Good morning...
[08:35] <dholbach> hi suji11
[08:36] <suji11> dholbach: my package is here http://revu.ubuntuwire.com/p/iok need advocate for that.
[08:42] <suji11> dholbach: will you?
[08:42] <dholbach> suji11: I have a bunch of other stuff to do right now, I'm sorry
[08:43] <suji11> dholbach: ok
[08:45] <oojah> quadrispro: Thanks very much for advocating.
[08:45] <suji11> Anyone here will advocate my package http://revu.ubuntuwire.com/p/iok ?
[08:46] <quadrispro> oojah, thanks for making Ubuntu better :)
[08:48] <oojah> :)
[08:52] <eagles0513875> dholbach: that one repo is still off line its like day 4 or 5. whether im on the  main server or us server or local mirror this one server still is giving me an error 403
[08:53] <eagles0513875> seems like there is an error with one of the canonical servers i just did a who is on teh ip and the origin is the uk
[08:53] <dholbach> eagles0513875: did you do a "apt-get update"?
[08:53] <eagles0513875> dholbach: ya
[08:54] <dholbach> youhttps://wiki.ubuntu.com/Mirrors#Communication
[08:54] <dholbach> oops
[08:54] <dholbach> https://wiki.ubuntu.com/Mirrors#Communication
[08:54] <eagles0513875> dholbach: this isnt a mirror this is a main canonical server
[08:54] <eagles0513875> if you give me a min i can paste u the who is
[08:55] <dholbach> eagles0513875: please read that wiki page
[08:55] <dholbach> it tells you who to get in touch with
[08:55] <dholbach> I can't fix any mirror or help with it
[08:55] <eagles0513875> ok thanks
[09:03] <suji11> Anyone around?
[09:05] <quadrispro> suji11, reviewed and advocated
[09:07] <suji11> quadrispro: Thanks a lot :)
[09:08] <suji11> quadrispro: Have one more advocate to get this in lucid?
[09:09] <slytherin> Any python experts here?
[09:10] <quadrispro> suji11, you can wait for andrew
[09:11] <suji11> quadrispro: ok, but tomorrow is the feature freeze , so only
[09:21] <eagles0513875> slytherin: kinda offtopic for this channel unless its for an app u want revued
[10:36] <ia> hello. could anyone tell me, please, good link to some [debian/ubuntu] wiki page about debian 3.0 format packaging (except http://wiki.debian.org/Projects/DebSrc3.0)? I guess, that somewhere should be such detailed information, as howto's and recipes about how to build [debV3.0] packages, how to select compression (for example, if i want to use lzma instead tar.gz), etc.
[10:41] <randomaction> ia: another source of information is `man dpkg-source`, "source package formats" section
[10:42] <randomaction> building is done as usual
[10:43] <randomaction> compression is selected by -Z
[10:52] <ia> randomaction: thanks. looks like i've got it. But if i build package via pbuilder, which the best way to pass compression option into pbuilder environment? (i guess, via dsc file/debuild somehow)
[10:53] <randomaction> if you use pbuilder, you should already have a source package
[12:58] <dupondje> What do we need to do with bugs in launchpad that are talking about a bug in a ppa ? Should this be marked as invalid ?
[13:03] <randomaction> generally yes, though if it an upstream bug it can be reassigned to upstream project, and it can be valid if it's applicable to a version in official archives
[13:05] <sindhudweep> I'm trying to fix a debian/watch file, and it seems as though uscan is picking up directory permissions, uid, gid as well as the version number. This is over ftp
[13:05] <sindhudweep> am I missing something obvious?
[13:06] <sindhudweep> http://pastebin.com/m308614de
[13:07] <geser> dupondje: have you a concrete example?
[13:08] <dupondje> https://bugs.launchpad.net/ubuntu/+source/gnome-do/+bug/388626
[13:08] <geser> as some teams might use PPA for staging and want to have such bugs filed
[13:08] <dupondje> Install the package from the PPA on Jaunty. Open the app and while typing, the application crashes. ...
[13:11] <geser> bah, that bug doesn't even mention which PPA got used :(
[13:12] <dupondje> but its not that if its from ppa, its invalid ?
[13:12] <dupondje> its sometimes valid ? ;)
[13:13] <geser> as the "Gnome Do Core Team" has a PPA with gnome-do as is "also notified" to this bug, I'd ask them if they want/care about such bugs before setting those bugs as invalid
[13:14] <dupondje> anyway it could be set to incomplete and ask which ppa got used right ?
[13:14] <geser> yes, that at least
[13:15] <dupondje> done :D
[13:16] <randomaction> sindhudweep: can you paste the watch file?
[13:17] <geser> RAOF: do you know if the "Gnome Do Core Team/Q Core Team" cares about bugs filed against PPA packages?
[13:17] <sindhudweep> sure
[13:17] <sindhudweep> randomaction: http://pastebin.com/m6b3c1f45
[13:23] <slytherin> sindhudweep: I don't think you should give brackets for the directory name matching expression.
[13:24] <sindhudweep> bah i posted the wrong version of the watch file
[13:24] <sindhudweep> just a second
[13:26] <sindhudweep> slytherin: randomaction: http://pastebin.com/m9b1d0da this is the watch file giving me the error
[13:26] <sindhudweep> the watch file i posted before was me fumbling trying to fix it
[13:27] <slytherin> What error does it give?
[13:27] <sindhudweep> dpkg: version 'drwxr-xr-x    2 1003     1003         4096 May 07  2006 0.7.1' has bad syntax: version string has embedded spaces
[13:27] <sindhudweep> it's reading the directory permissions, uid, gid, size and timestamp
[13:27] <sindhudweep> from ftp!
[13:28] <randomaction> I get no error when I drop it into debian/ of gnash package: http://pastebin.com/m1cf4d7c2
[13:28] <sindhudweep> so it seems the ftp lib/client used by uscan is returning more information in the filename and the (.*) is matching everything
[13:29] <randomaction> (but no files found as well, strangely)
[13:30] <sindhudweep> randomaction: http://pastebin.com/m308614de
[13:30] <c_korn> can someone please enqueue scilab again ? build just takes a while. see the last comment. it took 6.5h on Debian: https://bugs.launchpad.net/ubuntu/+source/scilab/+bug/511864
[13:30] <sindhudweep> i see all versions from 0.7.1 - 0.8.7
[13:30] <sindhudweep> just with extra information :(
[13:32] <slytherin> sindhudweep: Do you want hard answer or easy answer?
[13:32] <sindhudweep> hard answers are welcome :D
[13:33] <sindhudweep> but i can go with the easy one too.
[13:33] <slytherin> sindhudweep: man uscan. It contains example for this scenario.
[13:33] <Laibsch> hello
[13:33] <slytherin> sindhudweep: Let me know when you want easy answer.
[13:33] <slytherin> Laibsch: Hi
[13:33] <sindhudweep> slytherin: thanks, will do if i need it
[13:34] <lightnin> Greetings! I'm trying to get a package into multiverse in time for feature freeze. Can someone please take a look and advise? http://revu.ubuntuwire.com/p/scratch
[13:37] <shadeslayer> i dont need : include /usr/share/pkg-kde-tools/makefiles/1/cdbs/kde.mk
[13:37] <shadeslayer> if i dont have any patches right?
[13:39] <slytherin> shadeslayer: kde.mk is not for patches. And AFAIK, its use is not recommended these days.
[13:39] <dupondje> when menu.lst doesn't update after a kernel upgrade with aptitude ... this is a bug in kernel ? :)
[13:39] <shadeslayer> slytherin: oh ok
[13:40] <slytherin> shadeslayer: You may want to confirm second statement on #kubuntu-devel
[13:40] <shadeslayer> dupondje: mm... maybe aptitude too
[13:40] <slytherin> dupondje: what do you mean by update? Was there a new kernel installation?
[13:40] <dupondje> a kernel update indeed ..
[13:40] <dupondje> having this on karmic
[13:41] <dupondje> update-grub doesn't seem to be triggered
[13:41] <shadeslayer> dupondje: with 2.6.31-20-generic ?
[13:41] <dupondje> shadeslayer: not a specific version it seems, just all :(
[13:41] <shadeslayer> dupondje: 0_o
[13:41] <dupondje> but I use grub1
[13:41] <dupondje> guess there it went wrong :)
[13:42] <slytherin> dupondje: never saw that kind of bug. But I would call it grub bug than kernel bug.
[13:42] <sindhudweep> slytherin: thanks again. as usual RTFM works wonders :D
[13:42] <slytherin> sindhudweep: Welcome.
[13:42] <dupondje> slytherin: its not a kernel bug, but more a 'linux' package bug? as the update should trigger the update-grub ?
[13:42] <dupondje> just running update-grub works without problems
[13:43] <slytherin> dupondje: May be it is getting triggered but there is some problem with update of menu.lst
[13:43] <dupondje> well what does it trigger ? update-grub ?
[13:49] <slytherin> yes, AFAIK.
[14:00] <shadeslayer> slytherin: any idea what these warnings mean? : http://pastebin.ca/1799980
[14:01] <shadeslayer> slytherin: also is it necessary to set the debhelper version to 7?
[14:01] <slytherin> shadeslayer: not unless you are using the new format for rules file.
[14:01] <slytherin> shadeslayer: paste your rules file somewhere and I will tell you
[14:02] <shadeslayer> slytherin: http://pastebin.com/f177f7c6d
[14:02] <slytherin> shadeslayer: please note the number in compat file should match with debhelper version specified.
[14:02] <slytherin> shadeslayer: you don't seem to be using debhelper 7 specific features.
[14:03] <shadeslayer> slytherin: so i can ignore it right?
[14:03] <slytherin> shadeslayer: You should fix it.
[14:03] <shadeslayer> ok
[14:03] <slytherin> check what is version specified in compat
[14:03] <shadeslayer> slytherin: 7
[14:04] <slytherin> shadeslayer: change it to 5
[14:04] <slytherin> also specify the version in build-depends in debian/control file
[14:05] <shadeslayer> slytherin: ok and one more thing,what if i change the debhelper version to 7 in the control?
[14:05] <slytherin> shadeslayer: that is fine as well
[14:06] <shadeslayer> slytherin: ok..
[14:06] <slytherin> shadeslayer: But you are not really using 7 features.
[14:06] <Rhonda> slytherin: That would give the same warning. ;)
[14:07] <Rhonda> shadeslayer: The issue is that you seem to have a Build-Depends: debhelper without any (>= X) after it.
[14:07] <slytherin> shadeslayer: Also the version you have specified in changelog is wrong. It should be of the format X-YubuntuZ
[14:07] <Rhonda> shadeslayer: That X should be the same number than the one in debian/compat, or at least not lower.
[14:07] <Rhonda> And if you use dh_prep in your rules file you need >= 7
[14:08] <Rhonda> About bad-distribution-in-changes-file, I expect you used either Debian's lintian, or an outdated version.
[14:09] <slytherin> Rhonda: He is probably building package on karmic and hence outdated version
[14:09] <shadeslayer> slytherin: ok,and what about the other warnings?
[14:09] <Rhonda> unknown-field-in-dsc also hints that he's using the Debian lintian …
[14:09] <shadeslayer> ping shadeslayer
[14:09] <Rhonda> slytherin: Would the karmic lintian also complain about Original-Maintainer? I don't think so. :)
[14:09] <shadeslayer> oh
[14:09] <slytherin> Rhonda: you are right. :-)
[14:09]  * Rhonda does the happy dance.
[14:10] <slytherin> shadeslayer: quilt-build-dep-but-no-series-file - You are not using any patches but you have quilt as build dependency.
[14:10] <shadeslayer> Rhonda: yeah that happens with karmic ...
[14:10] <shadeslayer> slytherin: ok,i forgot to remove that too
[14:10] <slytherin> shadeslayer: and make sure the version in debian/changelog is correct.
[14:10] <slytherin> is this a native package?
[14:11] <shadeslayer> slytherin: nope
[14:11] <shadeslayer> (im actually doing this after 3 weeks... so ive forgotten a few things :P )
[14:11] <Rhonda> shadeslayer: dpkg -l lintian - what version do you get?
[14:12] <shadeslayer> Rhonda: http://pastebin.com/f3ff270ad
[14:12] <Rhonda> If it isn't a native package the version should have a dash in it.
[14:12] <shadeslayer> Rhonda: 0.3.92-0ubuntu1~karmic1+ppa2
[14:13] <Rhonda> That gives a changes file as rekonq_0.3.92_source.changes? That's strange
[14:14] <shadeslayer> Rhonda: no no... im saying i renamed the version to that
[14:16] <shadeslayer> ok everything looks fine now :D
[14:24] <dupondje> shadeslayer: http://packages.ubuntu.com/karmic/grub depends on grub-common, but grub-common is for grub2 ?!
[14:25] <lbrinkma> zul: what's the status of libmysqlclient #521815 ?
[14:25] <shadeslayer> dupondje: um actually im having problems of my own
[14:25] <shadeslayer> will talk later
[14:25] <zul> lbrinkma: its being worked on hopefully we will have a fix soon
[14:25] <dupondje> or somebody else ? :)
[14:25] <lbrinkma> zul: before FF?
[14:26] <zul> lbrinkma: hopefully
[14:27] <lbrinkma> zul: ok, thanks. It's very important to fix that before FF.
[14:28] <zul> lbrinkma: yes i know no
[14:28] <zul> lbrinkma: yes i know np even
[14:35] <rhpot1991> anyone have any idea why I'm getting forbidden on: http://us.archive.ubuntu.com/ubuntu/pool/main/m/mysql-cluster-7.0/libmysqlclient16_7.0.9-1_amd64.deb
[14:39] <geser> yes
[14:40] <lightnin> Hello - can anyone help answer a question about package version numbers? http://revu.ubuntuwire.com/p/scratch
[14:40] <lightnin> I'm told this is not quite right, but not sure how to fix...
[14:40] <geser> it's on purpose not let the this package spread
[14:41] <kklimonda> geser: what's wrong with it?
[14:42] <geser> "hostile" package takeover from mysql-cluster-7.0
[14:43] <dupondje> ok found it, had a kernel-img.conf file, which set to not update bootloader ...
[14:46] <rhpot1991> geser: well my pbuilder is failing on it as a dependency issue, anything I can do about it?
[14:47] <geser> wait, till it's resolved (the main archive is still affected too)
[14:47] <rhpot1991> geser: ok good enough, thanks
[14:49] <lightnin> How to indicate multiverse in control file? Section: multiverse/devel ?
[14:50] <geser> you don't, it's set when accepted into the archive
[14:53] <lightnin> geser: Ah, thanks! So what should my Section: field say if I'm trying to get into multiverse?
[14:59] <dupondje> shadeslayer: I had a kernel-img.conf in /etc. This disabled configuring the bootloader @ update
[14:59] <dupondje> should work now :D
[15:00] <shadeslayer> dupondje: ohhh.. thats new
[15:05] <dupondje> dunno what that file was doing there :) the system is running since dapper or so :p
[15:05] <slytherin> lightnin: Simply devel. The archive admin who accepts the package will put it into multiverse
[15:06] <slytherin> lightnin: Why is the package oging to multiverse by the way?
[15:06] <lightnin> slytherin: Thanks! We don't include quite all of the source, because the application interfaces with our website, which acts as a repository for Scratch projects.
[15:07] <lightnin> slytherin: so Section:devel ?  I was just learning (I think) that that line should refer to education or games...Maybe I indicate devel elsewhere?
[15:07] <slytherin> lightnin: I don't think that will cause it to go to multiverse (as long as the source needed to build the package itself is included).
[15:08] <slytherin> lightnin: Got to go. Hopefully someone else will provide answer.
[15:08] <lightnin> slytherin: Well, it's tricky. Scratch is actually a made in squeak.. thanks for your help!
[15:12] <lightnin> Uh, how do you view another source packages control file?
[15:22] <hyperair> how many more hours to FF?
[15:25] <lightnin> Can someone help me understand package versioning? I seem to have gotten myself in a bit of a pickle..
[15:26] <hyperair> lightnin: what's up?
[15:26] <shadeslayer> lightnin: whats the problem?
[15:26] <shadeslayer> hehe.. :)
[15:26] <ari-tczew> hyperair: 7,5 h ?
[15:26] <hyperair> ari-tczew: what's 7,5?
[15:26] <hyperair> er 7.5?
[15:26] <lightnin> shadeslayer: Not too sure - people say it's off, but don't recommend a precise fix. http://revu.ubuntuwire.com/p/scratch
[15:26] <hyperair> damn weird localized decimal points
[15:27] <hyperair> still got time, i suppose. else i'd have to start requesting freeze exceptions.
[15:27] <ari-tczew> hyperair: hours to Ffe :>
[15:27] <hyperair> ari-tczew: sorry, my floating point parser segfaulted earlier.
[15:28] <ari-tczew> ah
[15:28] <shadeslayer> lightnin: youve named the version as app-XubuntuY right
[15:29]  * hyperair pings persia about upload privs
[15:30] <lightnin> shadeslayer:Nope... we first worked with a debian developer, but never ended up submitting to debian. But the package version is now: scratch (1.4.0.debian.20)
[15:31] <ari-tczew> what's the different between white and red versions? http://people.ubuntuwire.com/~lucas/merges.html
[15:31] <ari-tczew> is new upstream versions in red?
[15:31] <hyperair> lightnin: is that a native package?
[15:32] <randomaction> ari-tczew: yes
[15:33] <lightnin> hyperair: sorry, not sure what that means - very new to this whole process. It's never been part of debian, although I think it corresponds to debian packaging standards.
[15:36] <hyperair> lightnin: http://wiki.debian.org/DebianMentorsFaq <-- look for difference between a native and non-native package on this page
[15:46] <lightnin> hyperair: Thanks! Totally non-native .
[15:46] <hyperair> lightnin: non-native packages need a -<packaging revision> suffix
[15:47] <hyperair> e.g. 1.4.0-1, or 1.4.0-0ubuntu1
[15:47] <hyperair> what is your tarball called?
[15:50] <lightnin> scratch_1.4.0.debian.19.tar.gz
[15:50] <lightnin> hyperair:http://revu.ubuntuwire.com/p/scratch
[15:52] <ivoks_doing_mirs> dholbach: do you have power to override new packages in lucid?
[15:52] <dholbach> ivoks_doing_mirs: no
[15:52] <ivoks_doing_mirs> universe, of course
[15:52] <ivoks_doing_mirs> dholbach: ok
[15:53] <dholbach> I'm not part of ~ubuntu-archive
[15:53] <ivoks_doing_mirs> ok
[15:53] <sebner> ivoks_doing_mirs: ask in #ubuntu-devel
[15:53] <hyperair> lightnin: why do you have such a strange version?
[15:53] <BlackZ> can somebody review/advocate this package: http://revu.ubuntuwire.com/p/autotrash ? thanks
[15:54] <hyperair> lightnin: and that's a native package you're having there.
[15:54] <hyperair> lightnin: where is your orig.tar.gz?
[15:54] <lightnin> hyperair:Well, it has to do with the long history of making this package, which has involved help from various different people....
[15:55] <hyperair> lightnin: that doesn't change the fact that it's a native package when it shouldn't be.
[15:55] <hyperair> lightnin: fix your version. what is the upstream version?
[15:56] <lightnin> hyperair: Ah, yes, sounds correct. Well, there are no other linux versions - and the package actually runs on squeak. So I suppose the upstream version is 1.4.0 . How can we change this to non-native?
[15:57] <shadeslayer> i guess this more of a builder problem than a package problem : http://launchpadlibrarian.net/39306253/buildlog_ubuntu-lucid-amd64.rekonq_0.3.92-0ubuntu1%2Blucid1%2Bppa2_CHROOTWAIT.txt.gz ?
[15:59] <hyperair> lightnin: where is the upstream tarball?
[16:00] <lightnin> Not sure that exists.... All source is hosted here: https://www.assembla.com/spaces/scratchonlinux/trac_subversion_tool
[16:00] <hyperair> i see. it's a snapshot.
[16:00] <hyperair> then make an orig tarball.
[16:00] <hyperair> the orig tarball should not have debian directory
[16:01] <hyperair> and since it's a snapshot, it should probably contain the revision number in it
[16:01] <randomaction> shadeslayer: yes, the build will be retried automatically
[16:01] <hyperair> something like 1.4.0~svn<revno>
[16:03] <lightnin> hyperair: Ok... that's probably beyond my abilities... Very new to this whole process and I essentially inherited the package.  I guess I'll give it a go though. :)
[16:03] <persia> hyperair: I can't personally do anything about them: I'm hoping that will be sorted soon.
[16:03] <hyperair> persia: okay, i'll wait then. i'll just get my syncs sponsored in the meantime.
[16:04] <hyperair> sebner: just a gentle reminder, FF is in a few hours ;-)
[16:04] <persia> hyperair: Sorry about that.  Unfortunately, it takes a TB person right now :(
[16:04] <hyperair> ah i see.
[16:04] <hyperair> it's fine.
[16:04] <sebner> hyperair: no problem. archive-admins are already subscribed so it doesn't matter when FF is
[16:04] <randomaction> persia: can remaining members of motu-council add hyperair?
[16:05] <hyperair> sebner: thanks.
[16:05] <sebner> hyperair: np, anything else that needs sponsoring?
[16:05] <hyperair> sebner: nothing, i think.
[16:05] <sebner> kk
[16:05] <hyperair> sebner: thanks =)
[16:06] <sebner> hyperair: It's enough to thank me once ^^ really no big deal ;)
[16:06] <hyperair> oh i already thanked you before? whoops =p
[16:07] <persia> randomaction: I thikn so, except none of them happen to be members of the DMB, so while it technically works, I'm not sure of the governance parameters involved.
[16:07] <persia> (although I'll not complain if someone just does it)
[16:08] <mok0> Just installed KDE4.4... wow
[16:09] <james_w> congratulations hyperair
[16:09] <hyperair> james_w: thanks =)
[16:17] <sebner> RAOF: uhh, first docky tarball. Just in time :P (nah I guess it will conflict with -do)?
[16:25] <bcurtiswx_> anyone know how I can get around empathy 2.29.90 using quilt 3.0 in a karmic launchpad PPA upload? is there a specific way I need to edit the debian/sources/format file ?
[16:30] <lightnin> hyperair:  I think it should probably stay native for this go around - main goal for compatibility is debian / ubuntu. Do I need to change versioning to be ok as native package?
[16:31] <hyperair> no, it should *not* be native.
[16:31] <hyperair> *nothing* should be native unless there is a very good reason for it.
[16:32] <shadeslayer> any ideas as to why : https://launchpad.net/~rohangarg/+archive/kde-extra/+build/1514104
[16:32] <shadeslayer> all other packages built fine 0_o
[16:32] <randomaction> bcurtiswx: you need to delete debian/source/format (or change it to "1.0") and reimplement any 3.0 features used in the package
[16:34] <hyperair> lightnin: i don't think there is a chance of getting your package in for lucid. there aren't any advocates yet, featurefreeze is in a few hours, and your package is not quite uploadable in this condition.
[16:34] <bcurtiswx_> randomaction: how would I reinplement and 3.0 features used in the package
[16:34] <bcurtiswx_> s/reinplement/reimplement
[16:34] <bcurtiswx_> s/and/any
[16:34] <bcurtiswx_> wow not in the typing groove today
[16:34] <shadeslayer> any ideas on my problme guys?
[16:35] <shadeslayer> *problem
[16:36] <randomaction> bcurtiswx_: it depends on which are used (patch system? replacement of binary files? non-tar.gz tarball? overriding of debian/ directory?)
[16:36] <lightnin> hyperair: Alas - we do have one almost advocate (highvoltage) that just took a look - I've added their changes in. Seems like the versioning is the last issue?
[16:37] <hyperair> lightnin: almost advocate? hmm
[16:37] <hyperair> =\
[16:37] <lightnin> hyperair: I only say so because a lot of schools that run Linux have asked for it to be included...
[16:37] <lightnin> I'll see if he is really ready to sign on... :)
[16:38] <bcurtiswx_> randomaction: there is a debian/patches directory.. so would that assume patch system ?
[16:38] <randomaction> yes, for that you need to build-depend on quilt and amend debian/rules to use it
[16:40] <bcurtiswx_> randomaction: may i PM you?
[16:40] <randomaction> bcurtiswx_: yes
[16:43] <hyperair> lightnin: well i haven't actually taken a look at the rest of the package, but please get the versioning right. it isn't hard. just generate a proper tarball out of pristine svn sources (svn export, tar -czf) and amend the version in debian/changelog to use <upstreamversion>-0ubuntu1
[16:44] <hyperair> where <upstreamversion> is from scratch_<upstreamversion>.orig.tar.gz
[16:46] <lightnin> hyperair: Ah, thanks for the ray of hope! I'll give it a go.
[16:53] <persia> hyperair: If you're reviewing stuff, I'll set you as a reviewer in REVU right now (no need to wait for TB)
[16:53] <hyperair> persia: oh cool. that'll help.
[16:53] <persia> hyperair: Done.
[16:53] <hyperair> persia: thanks.
[16:53] <persia> hyperair: Only 7 hours left though :)
[16:54] <hyperair> persia: i know :-)
[16:54] <hyperair> persia: i can provide advocates, but i can't upload, right?
[16:54] <persia> hyperair: Right, but if you're the second advocate, just make noise here, and someone will probably upload.
[16:55] <hyperair> persia: okay
[16:55] <persia> You *should* be MOTU already, except for a technical glitch.
[17:08] <persia> cody-somerville: Are you merging pyneighborhood for lucid?  Debian has a new upstream.
[17:08] <persia> ttx: Are you merging xmlbeans for lucid?  Debian has a new upstream
[17:09] <persia> RainCT: Are you merging zeitgeist for lucid?  Debian has a new upstream
[17:10]  * persia also points at https://merges.ubuntu.com/universe.html for lots of other packages that might benefit from a merge in the next few hours (those three aren't there)
[17:11] <RainCT> persia: I tried to file sync requests for zeitgeist and gnome-activity-journal 10 minutes ago but it looks like the mails were send wrong..
[17:11] <RainCT> Trying to figure out how to use "manage-credentials" to use requestsync with launchpadlib now
[17:11] <persia> RainCT: Sorry then: my source is older than that, but glad to hear you're on it.
[17:12] <randomaction> hmm, there's new claws-mail...
[17:14] <RainCT> persia: Oh, there's no reason to apologize. Thanks for the reminder :)
[17:15] <persia> I mostly wanted to highlight the ones on the manual list, as these tend to be annoying and fussy.
[17:15] <persia> So if someone was blocked on time, maybe someone else could help.
[17:16] <persia> The regular merges are easier (although it's worth trying to push them in the next 6:45, or it requires an FFe
[18:59] <ttx> persia: not planning to
[18:59] <persia> ttx: Is the new upstream something we want for lucid, or something we specifically don't want, or do you just not have time?
[19:00] <\sh> what? 153 outstanding merges?
[19:00] <persia> \sh: And we have 300 minutes to at least review all the ones where the upstream version differs.
[19:00] <ttx> persia: something I don't have the time to determine if I specifically don't want it
[19:00] <\sh> persia: I thought 18th 23:59 and all around the world?
[19:04] <\sh> anyone with insight about xulrunner merge? :)
[19:05] <ari-tczew> wrrrr, pbuilder failed because: E: Failed to fetch http://pl.archive.ubuntu.com/ubuntu/pool/main/p/python2.6/python2.6_2.6.4-5ubuntu1_i386.deb: 404  Not Found
[19:06] <randomaction> ari-tczew: update your pbuilder
[19:06] <ari-tczew> sudo pbuilder update has been done 5x !!!
[19:06] <ari-tczew> there is -6ubuntu1 how can I force pbuilder to use new debian revision?
[19:07] <geser> it should happen automatically if it is uptodate
[19:07] <geser> pbuilder is only some scripts around a chroot
[19:07] <persia> \sh: My memory from the last discussion about freeze times was slangasek saying 0:00 UTC on the day of the freeze.
[19:08] <\sh> oh fck
[19:08] <ari-tczew> f_cking tool, failed just before FF :-/
[19:09] <\sh> I mean, I can try to do some more merges right now until my esx is migrated...but all the syncs which will the result of it...#fail :(
[19:10] <ari-tczew> I'm ready to do 2 merges, but my pbuilder isn't ready
[19:12] <geser> ari-tczew: no error message during the update?
[19:13] <ari-tczew> geser: w8, I'll check again
[19:15] <ari-tczew> geser:
[19:15] <BlackZ> I get this error when I run "debuild -S": http://paste.ubuntu.com/378551/ what's wrong? debian/rules file: http://paste.ubuntu.com/378552/
[19:15] <ari-tczew> After this operation, 7791kB of additional disk space will be used.
[19:15] <ari-tczew> E: Could not perform immediate configuration on 'udev'.Please see man 5 apt.conf under APT::Immediate-Configure for details. (2)
[19:15] <randomaction> I had this error today, fixed it by reinstalling udev
[19:16] <randomaction> btw, all builds are failing now because of it
[19:16] <geser> ari-tczew: that explains why your pbuilder doesn't update, known problem, mvo is on it
[19:17] <persia> Rumour has it that rebuilding the chroot also fixes this, if one can't wait.
[19:17] <geser> BlackZ: looks like your setup.py doesn't support clean
[19:18] <BlackZ> geser: I'm just packaging it, so how to solve? should I contact the upstream author?
[19:20] <geser> BlackZ: I haven't looked yet at dh 7, but try to figure how to "disable" the calling of setup.py clean if your package doesn't support/need it
[19:20] <persia> Add an empty override_dh_auto_clean: rule
[19:21] <persia> for extra points, agressively populate debian/clean to delete all the stuff built on build.
[19:22] <BlackZ> persia: ok, I'll try, thanks.
[19:22] <persia> (to test, do a local build, and then run debian/rules clean, and compare that directory state with that of a freshly unpacked source after running debian/rules clean)
[19:23] <geser> ari-tczew: "sudo pbuilder login --save-after-login", "apt-get update", "apt-get install udev", "apt-get upgrade", "exit"
[19:24] <lightnin> When exactly is feature freeze?
[19:24] <randomaction> lightnin: in 4h 36min
[19:25] <lightnin> Anyone have a minute to look at some code, and advise on changes?
[19:25] <persia> lightnin: What sort of code?  Also, best to ask a question about it and provide a link.  Nobody is likely to volunteer.
[19:26] <persia> (whereas several people may look, and a subset of them may have comments)
[19:26] <lightnin> persia: thanks! It's here: http://revu.ubuntuwire.com/p/scratch I've been trying to convert this format to conform with versioning standards, but I'm getting stuck in several places.
[19:27] <persia> What's the first place you get stuck?
[19:27]  * persia can lecture, but it may not be as useful as a Q&A session
[19:28] <lightnin> I'm told I need to fix versioning, and that the package should be changed to be "non-native"
[19:28] <persia> OK.
[19:28] <lightnin> But I'm not sure how that directory structure will change the way the rules / etc. files work.
[19:28] <persia> It won't.
[19:29] <persia> So, do you have an unpacked source, and a tarball?
[19:29] <lightnin> So: If I tar up the original source directory (called scratch), what will unpack it? Must I add that to rules as well?
[19:29] <lightnin> That's not how things were originally laid our unfortunately.
[19:29] <persia> OK.  Let's start at the beginning then.  Is there a tarball available from upstream?
[19:31] <lightnin> Not really. This would be our first "official" linux release. The source code is actually in Squeak, so it runs on an interpreter. All the (up to date) code for the entire package is here: https://www.assembla.com/spaces/scratchonlinux/trac_subversion_tool
[19:31] <persia> Ah, so you *are* upstream, and you want to do an official release?
[19:32] <nixternal> persia: what is the tool that allows me to manually merge from say debian experimental into ubuntu? been a long time since I had to do this because MoM or UDD didn't have the latest experimental from debian
[19:32] <lightnin> Yep. It's us. We just want it to be easily available for kids who use ubuntu.
[19:32] <lightnin> http://scratch.mit.edu/
[19:33] <lightnin> Can get code really quick to see structure with: svn checkout http://my-svn.assembla.com/svn/scratchonlinux
[19:33] <persia> nixternal: set PACKAGE, then `sensible-browser https://launchpad.net/ubuntu/+source/$(PACKAGE)/+filebug?no-redirect`
[19:34] <persia> lightnin: OK.  I usually advise application developers to release some tarball that can be compiled/used for linux as a separate object, and call that the "release".  This makes a single common file that all distributions can use.
[19:35] <nixternal> persia: not exactly what I was looking for...there used to be a script that would do what MoM does, but locally, and I can't remember the name of it
[19:35] <persia> lightnin: So, you'd create this with svn export, perhaps something like `make release` if there are release-time scripts you want to run (often there are none the first time), and then just tar czf
[19:36] <persia> nixternal: I don't know of anything.  There might be a pull-experimental-source (or it would be trivial to construct), but I usually just grab sources and merge manually when I merge manually.
[19:36] <lightnin> That svn actually contains *all* files to make debian package... so I need to rearrange so that I call debuild -S -sa -I in a directory that contains my source tarball, and the debian directory with control files?
[19:37] <nixternal> yeah, I hate doing the manual merge that way, especially with the changelog
[19:37] <persia> lightnin: You don't need to rearrange anything.  We usually recommend that application developers keep debian/ in a separate branch, but it doesn't matter that much.
[19:38] <persia> lightnin: The important bit at the first stage is to have some tarball (preferably ${PROGRAM_NAME}-${VERSION}.tar.gz ) stored at the upstream homepage or other location (launchpad, sourceforge, etc.)
[19:39] <bdrung> fabrice_sp: can you have a look at http://revu.ubuntuwire.com/details.py?upid=7874 ?
[19:40] <persia> bdrung: You need to use -sa for every push to REVU.  I've run get-orig-source, and am just finishing builds of that now to post a review.
[19:40] <persia> (although the get-orig-source bit cost an extra hour or so, unfortunately)
[19:41] <lightnin> persia:I think I'm too new to all this. It's probably gauche to offer money for help at this stage, eh?
[19:41] <persia> lightnin: I always accept money for help, but I think that you're close enough not to need enough help to be worth money.
[19:42] <persia> lightnin: I'll go over stuff in a bit more depth in a /query, and I suspect your next upload will sort everything.
[19:42] <lightnin> persia: Doesn't feel that close to me. :) But thanks for the vote of confidence.
[19:43] <bdrung> persia: why -sa every time when the orig.tar does not change?
[19:43] <bdrung> (and the source tarball is not small)
[19:43] <persia> bdrung: Because the easiest way to implement support in REVU for allowing the source tarball to be fixed when it was wrong was to create a new layered subdirectory for each upload separately :)
[19:43] <persia> But anyway, I have the tarball locally, so unless I find lots of reasons to reject, you shouldn't need to repush to REVU.
[19:45] <bdrung> persia: then REVU should be enhanced to grab the source from the previous upload and check the md5sum ;)
[19:46] <persia> bdrung: Sounds good.  Please file a bug and a patch :)
[19:46]  * persia isn't a REVU hacker, but knows the usual response
[19:46] <persia> bdrung: Actually, even just the bug is useful, in case someone has time.
[19:47] <bdrung> persia: where to file it?
[19:49] <ari-tczew> geser: thanks, it works!
[19:49] <persia> bdrung: launchpad.net/revu/+filebug
[19:52] <SevenMachines> hi, can i just check if theres been anything odd going on with the build farm today?  specifically the, could not perform immediate configuration on 'udev' build errors. seems to have affected a few uploads and ppa builds today for a few people
[19:52] <persia> SevenMachines: Yes.  There is an upgrade bug in lucid.  Wait, force-reinstall udev, or rebuild your chroots.
[19:53] <persia> (one of these things is likely being done to the buildd chroots)
[19:54] <SevenMachines> persia: thanks, these are failed uploads to the main archive, will they need to be re-uploaded i take it then?
[19:54] <persia> SevenMachines: They can just be given back.
[19:54] <randomaction> they're going to be retried automatically
[19:55] <persia> SevenMachines: For a PPA, you can probably do that yourself.  For the main archive, someone else will catch it.
[19:55] <\sh> oh well...I give up about the merges...next run will be fun I think
[19:55] <SevenMachines> thanks, i dont wont to bother someone to upload again if its automatic :)
[19:56] <\sh> looks like I need to order another hp c7000 with full fledged bl465c components and build my own LP
[19:56] <randomaction> or am I mistaken and someone has to request the rebuild?
[19:58] <\sh> and when I'm looking on the sponsors queue...cleaned it up as far as I could, and now it's full again...
[19:58] <ScottK> randomaction: Someone has to request it.  The open question is will it be one mass request or done on a package by package basis.
[19:59] <\sh> ScottK: when I see the ammount of pkgs...I would say one mass request and we are done
[19:59] <ScottK> \sh: My guess is it'll be mass give back for Main and Universe is on it's own, but that's a guess.
[19:59] <ari-tczew> please sponsor this merge before FF bug 523357 thanks !
[20:00] <\sh> ScottK: oh well
[20:00] <ScottK> We'll see.
[20:01] <\sh> ScottK: I really do want to see our merges list down to 30 or so...it's really a mess
[20:02] <ScottK> I imagine so.  I've had almost no time lately.
[20:03] <\sh> ScottK: /me neither...I tried to deal with merges with my name tag...but it looks like we have really a problem with people doing merges, but not coming back for the next cycle...
[20:03]  * ScottK agrees
[20:04] <ScottK> One of the process consequences of late DIF is that there's very little time between DIF and FF.  Since DIF is when merges are traditionally considered fair game, not much can get done.
[20:04] <\sh> and regarding our tight schedule for this release, the "merges are open for everyone after DIF" doesn't work out properly
[20:05] <\sh> you took the words out of my mouth :)
[20:05] <SevenMachines> excuse me if this is an obvious one, but merges stop on the 25th then?
[20:06] <\sh> nope..today 23:59:59
[20:06] <SevenMachines> ah! :)
[20:07] <fabrice_sp> bdrung, looking
[20:07] <ScottK> SevenMachines: Only ones that bring in new features.  Bug fix merges can go on.
[20:08] <SevenMachines> ScottK: where the merge only closes bugs is ok, otherwise the bug fix portion is taken and added to the current ubuntu version?
[20:09] <ScottK> SevenMachines: Generally this means no merges that bring in new upstream versions (without a feature freeze exception) unless the new version is bugfix only.
[20:11] <ari-tczew> does autosync will run today? 190 packages are outdated between squeeze
[20:11] <SevenMachines> ok, i think i see, thanks
[20:11] <\sh> ari-tczew: DIF was on the 11th..now it's only on manual
[20:12] <ari-tczew> ah ok thnx
[20:17] <persia> Um, merges *don't* stop today.  It's just the last day to merge any *new upstream* versions without a freeze exception.
[20:17] <persia> So, if there's a merge pending that doesn't contain a new upstream, please skip it in favour of one that does (especially where the new upstream is useful or interesting)
[20:18] <persia> Merges don't stop ever, although after BetaFreeze, there needs to be a good reason for the merge (as with any upload).
[20:19]  * persia usually tries to schedule time to do merges for RCbugs right up until ReleaseFreeze
[20:21] <SevenMachines> persia: i think that was where i was confused, thinking merging was over and porting fixes into existing ubuntu versions was preferred instead. i think i've seen the light now
[20:22] <SevenMachines> though it probably means i should learn to do merges properly in the next week or two :)
[20:23] <persia> SevenMachines: Indeed, as sponsors tend to get more critical, and are more likely to say "Um, no.  That doesn't include any useful bugfixes: go fix a useful bug"
[20:23] <\sh> persia: http://qa.ubuntuwire.com/multidistrotools/universe.html#outdatedandlocalinB does multidistrotools have the possibility to graph "different in squeeze and lucid with local changes + new upstream only?"
[20:24] <randomaction> \sh: http://people.ubuntuwire.com/~lucas/merges.html , red entries
[20:25] <persia> \sh: I don't know, actually.  I suspect it needs a patch to do so.
[20:25] <\sh> randomaction: thx...
[20:25] <\sh> but to see this...it's still a lot of crap to do...especially file FFEs
[20:26] <ari-tczew> lucas's script should fetching how many packages/merges are outdated
[20:27] <ari-tczew> lol @
[20:27] <ari-tczew> $ update-maintainer
[20:27] <ari-tczew> The original maintainer for this package is: Ubuntu MOTU Developers<EMAIL_ADDRESS>[20:27] <ari-tczew> Resetting as<EMAIL_ADDRESS>[20:28] <ScottK> "I'm not doing my merges, go ahead" seems to have worked out reasonably well for me.  No new upstreams on my list to do.
[20:29] <jpds> ari-tczew: Reading the source, that's what it's suppose to do.
[20:30] <ari-tczew> ScottK: are you bored? new upstream version by merge: Bug 523375
[20:30] <ScottK> ari-tczew: No.  I'm very busy with $WORK.  Just pausing a moment to check.
[20:31] <persia> ScottK: I have historically found "I don't care if anyone does my merges" to work even better, because it doesn't block one from doing them if one happens to bump into them for some other reason.
[20:31] <\sh> ok...my esx is migrated...
[20:32] <fabrice_sp> a package I just uploaded FTBFS with a "Chroot problem" on buildd. (http://launchpadlibrarian.net/39318658/buildlog_ubuntu-lucid-i386.ebox-services_1.5-0ubuntu1_CHROOTWAIT.txt.gz) is it a known pb?
[20:32] <jpds> fabrice_sp: Yes.
[20:33] <bdrung> persia: do you found anything that can delay the upload of yofrankie?
[20:33] <fabrice_sp> jpds, ok. Will the rebuild happen alone, or I'll have to retry them?
[20:33] <fabrice_sp> (when chroot is fixed, I mean)
[20:34] <jpds> No idea.
[20:35] <bdrung> fabrice_sp: thanks for checking
[20:35] <ivoks> i vote for FF postpone cause of broken PPA :D
[20:35] <fabrice_sp> bdrung, yw ;-) (and thanks for the get-orig-source target :-D )
[20:36] <bdrung> fabrice_sp: hopefully i can drop it soon ;)
[20:36] <ari-tczew> [ new upstream @ merge ] Bug 523357 please sponsor it ;-) thanks!
[20:36]  * fabrice_sp is busy with ebox* packages
[20:40] <fabrice_sp> \o/ for yofrankie :-)
[20:43] <bcurtiswx_> if backporting packages needed for empathy lucid are now requiring gdm... should I just stop?
[20:44] <bcurtiswx_> empathy 2.29.90 but for karmic..
[20:45] <highvoltage> hi, anyone wiling to review some packages? as far as I can tell they're in great shape so they just need one more advocate (nixternal perhaps if you're around and able at this time?)
[20:46] <highvoltage> http://revu.ubuntuwire.com/details.py?upid=7859 and http://revu.ubuntuwire.com/details.py?upid=7854 and http://revu.ubuntuwire.com/details.py?upid=7853
[20:46] <sebner> bcurtiswx: I'm just wondering why you want to backport a beta version
[20:47] <bcurtiswx_> sebner: play around with in karmic.. if it is futile i will stop.. but this also gets me learning the backporting process
[20:47] <sebner> heh
[20:48] <bcurtiswx_> im doing this mainly to learn backporting and checking to make sure it all works in the end..
[20:49] <bcurtiswx_> sebner: am I being stupid?
[20:49] <sebner> bcurtiswx: hmm, I'm not familiar with empathy I'm sorry
[20:49] <bcurtiswx_> sebner: irregardless of package.. is this the wrong way to go about learning?
[20:50] <sebner> bcurtiswx: dunno, have you read the backporting docs?
[20:50] <bcurtiswx_> yup
[20:55] <blueyed> glib-gettext in Ubuntu is what?
[20:55] <blueyed> (mortadelo autogen.sh tells me to install it)
[20:57] <sebner> bcurtiswx: I guess you are doing stuff right then, it's just some packages are quite easy to backport and some are ... difficult
[20:58] <bcurtiswx_> sebner: im assuming empathy hasn't been backported for testing because its proving on the very difficult end.. which im ok with.. because i'm learning the backporting process while I'm working through all the depends.. etc..
[20:59] <sebner> :)
[20:59] <ari-tczew> sebner: got time for sponsoring?
[21:00] <sebner> ari-tczew: you are quite impatient ;) anyways, guess you can through your stuff at me
[21:08] <matttbe> Hello ! I'm part of the Cairo-Dock team (with fabounet). We want to update Cairo-Dock and its plug-ins in Lucid repositories. We already have open 2 bugs for these 2 packages but without any anwser. We have pushed our modifications on 2 other branches and we have done a merge proposal. I think that it only need a little verification
[21:08] <matttbe> => https://bugs.launchpad.net/ubuntu/+source/cairo-dock/+bug/521534
[21:08] <matttbe> => https://bugs.launchpad.net/ubuntu/+source/cairo-dock-plug-ins/+bug/521536
[21:08] <BlackZ> matttbe: I'll look at them later
[21:09] <ari-tczew> tic-tok tic-tok aaaaaaaaaaaaaaaaaa FF is coming, make me crazy
[21:09] <matttbe> great ! Thanks for your help !
[21:09] <BlackZ> matttbe: you're welcome
[21:10] <matttbe> BlackZ, "later" means "before the FF?" :)
[21:10] <BlackZ> matttbe: few minutes, I'm a bit busy right now
[21:10] <matttbe> ok, no problem ;)
[21:18] <BlackZ> matttbe: ok, I'm on them
[21:18] <matttbe> great, thanks !
[21:20] <matttbe> if you want, we (fabounet and me) are also on this channel #cairo-dock
[21:24] <ari-tczew> new usptream bug 414247
[21:25] <ari-tczew> superm1: ping
[21:26] <superm1> yes?
[21:29] <ari-tczew> superm1: could you review this package? bug 414247
[21:29] <superm1> ari-tczew, i'd just subscribe u-u-s
[21:29] <superm1> i wont be able to for a bit
[21:31] <ari-tczew> superm1: but you are an hmm 'main' uploader of firmware-addon-dell
[21:31] <superm1> ari-tczew, but in ubuntu anyone can upload
[21:31] <superm1> it's okay if someone else does
[21:32] <ari-tczew> superm1: ok
[21:37] <\sh> superm1: you subscribed u-r-t not u-u-s
[21:37] <superm1> what'd i do?
[21:38] <\sh> superm1: sorry..I just read: you did subscribe u-u-s ;)
[21:38] <superm1> maybe ari-tczew did something like that, i didnt do anything
[21:38] <\sh> if someone tells me what it does? universe can be done
[21:43] <\sh> oh well...doesn't build anyways
[21:43] <\sh> site-packages instead of dist-packages
[21:45] <\sh> superm1: if you see ari tell him that his pkg ftbfs because of the mentioned above reason...commented on the bug
[21:45]  * \sh really has to leave the office now...
[22:00] <persia> Are logfiles supposed to be deleted on purge?  I thought we kept them around.
[22:05] <highvoltage> YokoZar, ogra: any of you perhaps up to review a few packages?
[22:05] <YokoZar> highvoltage: busy atm
[22:05] <persia> highvoltage: What do you need reviewed?
[22:06]  * persia is hip-deep in reviewing right now, but willing to help if something is critical
[22:07] <highvoltage> persia: awesome, I hear you can go at least up to your neck: it's these three packages from mhall119: http://revu.ubuntuwire.com/u/mhall119
[22:07] <highvoltage> persia: it would be nice if you can, but if you can't get to it, then no pressure
[22:09] <persia> highvoltage: What sort of build-times do they require?  I'm mostly CPU-bound right now.
[22:10] <highvoltage> persia: very little, they are small and nothing besides the packages themselves need to be built
[22:11] <persia> highvoltage: OK.  I'll add them to queue.  I can do the visual & copyright faster, if you want to prep them by leaving comments based on build (both all-arch and one-arch) and lintian runs (I use -iIEv --pedantic, and ignore some of the messages)
[22:11]  * persia is not certain that the builds will complete, based on the current pending build queue, but will try
[22:15] <persia> highvoltage: You don't happen to know about log files and purge, do you?
[22:15] <EzraR> persia: you wouldnt happen to be reviewing mangler would you ;)
[22:16] <persia> EzraR: It's not on my current list.  I'll put it in the queue, but chances are decidedly weak.
[22:18] <highvoltage> persia: no, sorry
[22:19] <persia> Anyway, found a different complete blocker in the package that had that issue, meaning I could just tell the uploader to check policy about the logs :)
[22:20] <highvoltage> persia: all I know is that when you use --purge it should remove log files, but I'm sure you already know that too :)
[22:20]  * persia is down to 10 packages and 100 minutes, and senses that this will be insufficient
[22:20] <persia> highvoltage: Actually, that was the part I was unsure about :)
[22:22] <highvoltage> persia: if you want to refer him to a web page you can point him to section 10.8 on http://www.debian.org/doc/debian-policy/ch-files.html
[22:23] <persia> highvoltage: That's more for me: the package was correct (and I wasn't sure).
[22:23] <highvoltage> ah ok
[22:34] <RoAkSoAx> at what time is FF
[22:34] <RoAkSoAx> ?
[22:34] <james_w> RoAkSoAx: 90 minutes
[22:35] <RoAkSoAx> james_w, ooh we are almost there. Thanks for the tip :)
[22:37] <RAOF> Would anyone like a review swap?  I'll trade a lintian-clean Docky for someone's pet package :)
[22:38] <persia> RAOF: Please just grab some of the ones in the pre-advocated queue.
[22:38] <persia> Anything without at least one advocate at this point isn't likely to make it.
[22:38] <RAOF> Yeah.
[22:39]  * persia is happy to look at docky, but probably won't get to it in time, already having a list of one-advocate packages built locally and needing comment
[22:39] <persia> bdruYou should have uploaded yofrankie already :)
[22:39] <persia> Hrm.  tab fail : maybe sleeping?
[22:39] <sebner> persia: yeah, already in NEW since nearly 1 hour
[22:41] <persia> Then just failed to get noted on REVU (or I'm behind)
[22:42] <quadrispro> ehya guys, campcaster is on REVU and it needs an ACK
[22:42] <quadrispro> http://revu.ubuntuwire.com/p/campcaster
[22:42] <persia> quadrispro: RAOF is trading for docky, if you're quick :)
[22:42] <quadrispro> of course
[22:43] <sebner> quadrispro: I'll take a look at it
[22:45]  * persia wishes there was a way to know in advance when a package would get rejected, so as not to waste CPU cycles and eyeball time :(
[22:46] <highvoltage> heh
[22:46] <quadrispro> persia, eh eh, it would be great :)
[22:46] <persia> Grr.  I didn't update my system in the past few hours, and pull-revu-source suddenly doesn't work for me!
[22:46] <highvoltage> persia: what package is this that's violently pillaging your system resources?
[22:47] <persia> highvoltage: I'm still running test builds for the set of one-advocate stuff I grabbed a few hours ago (parallel builds for with-arch-any and without-arch-any), but the real killer seems to be the new upstream of musecore.
[22:49] <persia> Since it contains a new soundfont, and since we only have one right now, this will double the number of choices available for creating MIDI soundtracks from free sources (which helps for games, musicians, etc.), but it's very large.
[22:49] <persia> (and has been linking (in parallel) for the last hour or so.
[22:49] <highvoltage> ah yes, totally worth the cpu cycles sacrifice!
[22:50] <persia> Yeah, but I knew about this earlier, and shouldn't have put off the build :)
[22:50] <persia> (I didn't know it took so long to build, just that it *must* make FF)
[22:51] <highvoltage> small packages that just contain a few pieces of artwork shouldn't be too hard to get by feature freeze exception should they?
[22:53] <persia> I think those are bound by UI FReeze.
[23:04] <highvoltage> persia: maco2 is going to help with the reviewing of mhall119's packages. so you can take them off your fork :)
[23:04] <persia> highvoltage: Cool!
[23:05] <persia> fabrice_sp: apologies for the terse comment, but you understand :)
[23:07] <RAOF> Lex79: I've reviewed colibri; I'd be willing to advocate & upload if you can commit to resolving the comments I've made.
[23:13]  * persia waits harder on the dvisvgm, frescobaldi, and libbrowserlauncher2-java builds, and hopes musecore finishes in time.
[23:14] <quadrispro> g'night guys
[23:14] <quadrispro> sebner, thanks!
[23:14] <sebner> quadrispro: welcome, gn8
[23:15] <persia> quadrispro: Just one or two more reviews before you go?
[23:15] <persia> Ah :(
[23:21] <sebner> persia: I uploaded ccsript but I changed the versionsnumber back to -0ubuntu1
[23:22] <RAOF> Hm.  ccscript seems to be missing a license statement for cmodel.sh; it's not LGPL-3
[23:22] <persia> RAOF: Ah, in debian/copyright?  I perhaps got overexcited about the correct statement releasing rights in the file :(
[23:23] <RAOF> persia: Right.
[23:23] <persia> RAOF: One could perhaps argue it's LGPL-3 + exception?
[23:23] <persia> But yeah, that deserves to be fixed.  Sorry for missing it.
[23:23] <RAOF> I guess in the same way that MIT is LGPL-3 + exception, maybe :)
[23:24]  * persia is *so* tired of "This file is public domain" that a properly worded rights release gets automatic bonuses
[23:24] <persia> heh :)
[23:24] <RAOF> Heh.
[23:26] <RAOF> JontheEchidna: I see that you've beaten me to deciding to advocate & upload colibri.
[23:27] <persia> randomaction: sorry for the terse comment (but you understand)
[23:27] <sebner> persia: RAOF should I unarchive it and ask a archive-admin to nuke it?
[23:28] <JontheEchidna> RAOF: since those were your only niggles, I assumed that I was the second ack
[23:28] <persia> LucidFox: sorry for the terse comment (but you understand)
[23:30] <RAOF> JontheEchidna: Pretty much, yeah.  The package can still have a watch file, just with a comment as to why a watchfile won't work :)
[23:30] <JontheEchidna> ah, yeah. never thought about it that way
[23:31] <JontheEchidna> luckily upstream is a canonical dev, so we shouldn't have much trouble getting the binary install location correct
[23:32] <cyphermox> persia, thanks for advocating congruity, but it got in through Debian already, with the changes you suggested. I've just archived it -- I thought it already had been.
[23:32] <sebner> persia: RAOF should I unarchive it and ask a archive-admin to nuke it?
[23:33] <sebner> ccscript?
[23:33] <RAOF> sebner: Maybe the archive admins won't notice? :).  I think you should unarchive + nuke, yes.
[23:34] <persia> cyphermox: Please ask for archiving if you catch things like that :)  Saves me build cycles, which gets more goodies in the archive :)
[23:34] <persia> why nuke?
[23:34] <sebner> RAOF: mind fixing it?
[23:34] <cyphermox> persia, yeah, sorry. it should have been archive long, long ago, and another I was working on around the same time was, so I got confused
[23:35] <RAOF> sebner: The debian/copyright?  Ok.
[23:35] <sebner> RAOF: great
[23:35] <sebner> RAOF: what about the icon thing in docky we spoke about in -cli?
[23:36] <persia> cyphermox: It happens.
[23:37] <RAOF> sebner: It is a packaging problem; it seems I've got the icons installed locally, so I didn't notice.
[23:37] <sebner> RAOF: kk, if you can fix it within the next 20 minutes I'm glad
[23:38] <RAOF> Test buliding now; should be fixed in... 4 minutes :)
[23:38] <sebner> great
[23:40]  * persia grumbles about people not keeping REVU up-to-date, having discovered that yet another review was pointless because it was already uploaded.  At least commenting would be nice
[23:41] <lifeless> persia: isn't that a REVU bug ('does not notice archive uploads') ?
[23:41] <persia> OK.  Which of qimo-*, and kfritz doesn't have a second reviewer?
[23:42] <persia> lifeless: Well, kinda.  It does notice sometimes.
[23:42] <RAOF> sebner: You uploaded ccscript as -0ubuntu1?  Can I grab your source package to add a new changelog entry?
[23:42] <persia> RAOF: Can't you download from NEW?
[23:42] <RAOF> I could, yes.
[23:43] <lifeless> persia: so when doesn't it discover?
[23:44] <fabounet> Hi,
[23:44] <fabounet> what about the Cairo-Dock-plug-ins package ?
[23:44] <fabounet> Is there any way to know the progress ?
[23:44] <persia> lifeless: I'm not sure.  I know only a little about the code (I am one of the biggest REVU *users* but haven't even looked at the code)
[23:45] <sebner> RAOF: you have to get it nuked from NEW but yes go ahead
[23:45] <persia> fabounet: Check comments on REVU, check NEW.
[23:45] <persia> sebner: Why does it need to be nuked from NEW?
[23:45] <persia> sebner: A new upload (with a higher version) will supercede the version in NEW>
[23:45] <persia> (Soyuz is smart that way)
[23:46] <james_w> can't you even upload the same version again?
[23:46] <fabounet> hmm, does it mean it's already integrated ?
[23:46] <persia> lifeless: The most common case seems to be when it gets into the archive after it goes to REVU, but there hasn't been any upload or comment since.  I think the DB only gets updated per-package when something happens to the package.
[23:47] <RAOF> sebner: Not just bump the version & upload as normal?
[23:47] <lifeless> ah
[23:47] <persia> james_w: Can you?  I thought NEW blocked that.
[23:47] <lifeless> persia: so, we just need something to watch the archive feed
[23:47] <james_w> you can if it is rejected at least
[23:47] <persia> lifeless: Perhaps.  RainCT or NCommander could probably explain better (they seem to have been the last two most recently active REVU Hackers)
[23:47] <james_w> give it a go :-)
[23:47] <persia> james_w: I thought that only worked for rejected.  Care to reject ccscript?
[23:48] <RAOF> I've already bumped the version and uploaded; if you'd prefer to have -0ubuntu1, reject them & I'll unbump & upload.
[23:48] <sebner> RAOF: ah I just thought archive-admins only like 0ubuntu1
[23:48] <ScottK> You can upload the same version again only if it's in Source New.
[23:49] <ScottK> If it's binary New, then the version has been used.
[23:49] <sebner> hhu ScottK
[23:49] <sebner> RAOF: is docky fixed now?
[23:49] <fabounet> Is there a page we can see the progress of a package ?
[23:49] <fabounet> the launchpad bug is only marked as "on progress"
[23:49] <RAOF> sebner: yes.
[23:49] <persia> ScottK: Thanks for the clarification.
[23:49] <sebner> RAOF: I'll upload then
[23:49] <james_w> done
[23:49] <sebner> persia: mind sponsoring a merge for me? (I just have a debdiff, no bug on LP ,..)
[23:49] <sebner> persia: it's for main
[23:49] <highvoltage> persia: maco2 isn't added as a reviewer yet on revu. any chance that you could add her now?
[23:51] <persia> highvoltage: No chances at all: done :)
[23:52] <highvoltage> persia: hehe
[23:52] <sebner> RAOF: uploaded :)
[23:52] <RAOF> sebner: Ta muchly.
[23:53] <sebner> RAOF: np
[23:53] <persia> Anyone else have a half-advocated package they need done?  Of those left, any still unclaimed?
[23:54] <persia> (mind you, these need to be packages that build *instantly* :)
[23:55] <sebner> persia: https://bugs.edge.launchpad.net/ubuntu/+source/jinja2/+bug/523540 *please* :=)
[23:55] <sebner> persia: builds ;)
[23:55] <persia> sebner: What do you want me to do with that?
[23:55] <sebner> persia: sponsor (into main)
[23:56] <persia> sebner: I can't.
[23:56] <persia> LP lies about my membership in core-dv
[23:56] <sebner> persia: ohh
[23:56] <sebner> james_w: are you free for it?
[23:56] <james_w> 'fraid not
[23:57]  * sebner looks for a core-dev sponsoring an easy merge
[23:57] <persia> sebner: You know that there are more core-devs in -devel, right?
[23:58] <sebner> persia: sure, 2 minutes left are making me nervous :P
[23:58] <persia> heh.
[23:58] <persia> I doubt it *can* be done in 2 minutes.
[23:58] <persia> I think we're done for lucid.
[23:58] <sebner> persia: pff, as long as somebody starts with it archive admins are fine :P
[23:58] <persia> heh.
[23:59] <sebner> persia: where are all the core-devs when you need one!


[03:30] <walterrr> Hi, is anyone around who can confirm what I think is a bug?  Should be quick.
[04:09] <walterrr> maybe later, bye
[17:21] <njin> hallo fellows, is possible to make public bug 1062007 . thanks in advance
[17:30] <jtaylor> done
[21:00] <dlentz> anyone familiar with SRU's care to look this over for me? bug 1060813
[21:00] <ubot2> Launchpad bug 1060813 in youtube-dl "[SRU, precise] Current version (2012.02.27) doesn't work anymore" [Undecided,Confirmed] https://launchpad.net/bugs/1060813
[21:01] <dlentz> is simply saying, "newer upstream version needed" sufficient or do i have to literally create a patch?
[21:02] <jtaylor> you could request a backport from quantal
[21:02] <jtaylor> that is the usual route for new versions
[21:02] <jtaylor> but in this case it might make sense to backport the thing to precise-updates
[21:02] <micahg> well, I was wondering if youtube-dl should have an MRE since the old versions just don't work
[21:03] <jtaylor> mre?
[21:03] <micahg> !mre | jtaylor
[21:03] <ubot2> Factoid 'mre' not found
[21:03] <micahg> gah
[21:03] <jtaylor> :)
[21:03] <micahg> microreleaseexception
[21:03] <micahg> https://wiki.ubuntu.com/StableReleaseUpdates/MicroReleaseExceptions
[21:03] <jtaylor> that makes sense
[21:04] <jtaylor> though I'd prefer to remove it :) it will just break again in a mont
[21:04] <micahg> jtaylor: well, with an MRE, we can just keep updating (but someone has to be interested)
[21:05] <dlentz> i doubt a project as small (and legally questionable) as youtube-dl will qualify for MRE
[21:06] <jtaylor> how does one go about getting an mre?
[21:06] <micahg> proposal to tech board
[21:06] <jtaylor> in my experience subscribing -sru does seldom get an anwser
[21:07] <dlentz> maybe i should just package the new version in a PPA
[21:07] <micahg> but I'mnot sure if Debian is considering releasing with it or not: http://packages.qa.debian.org/y/youtube-dl.html
[21:07] <jtaylor> there is a second youtube downloader in the archive
[21:07] <jtaylor> which is broken even in quantal
[21:08] <jtaylor> minitube
[21:08] <jtaylor> thats gone from debian
[21:08] <dlentz> jtaylor, that's what i was afraid of (seldom answer)
[21:10] <micahg> personally, I think these things should just live in backports and devel
[21:11] <dlentz> precise is an lts though, so i'm going to attempt packaging it in my mediahacks ppa
[21:11]  * dlentz fires up VM
[21:12] <micahg> dlentz: just request  a backport once it gets in quantal (whichever version you want)
[21:12] <dlentz> micahg, you think that's a better bet?
[21:13] <micahg> dlentz: well, backports is enabled by default in precise, so it'll show up in software center for people (this is pretty off topic at this point and should probably move to -motu)
[21:14] <dlentz> micahg, thanks for the help and redirection
[21:36] <dlentz> well, could we at least mark bug 1060813 as triaged/high?
[21:36] <ubot2> Launchpad bug 1060813 in youtube-dl "[SRU, precise] Current version (2012.02.27) doesn't work anymore" [Undecided,Confirmed] https://launchpad.net/bugs/1060813
[21:36] <dlentz> pretty please with sprinkles on top?
[21:37] <jtaylor> it won't make much difference
[21:37] <dlentz> it will help me feel good
[21:38] <dlentz> :P
[21:38] <micahg> dlentz: done
[21:38] <dlentz> thanks
[21:39] <micahg> dlentz: now someone needs to get a package into the sponsorship queue :)
[21:39] <micahg> subscribing SRU is worthless unless you're not sure they'd approve an update and need advise, they review in queue now
[21:39] <micahg> (well, worthless until it's uploaded)
[21:40] <dlentz> ah, that's not in the wiki
[21:40] <jtaylor> yes the wiki is a bit misleading in respect of subscribing -sru
[21:41] <micahg> it should say it after upload now
[21:41] <micahg> oh, hrm, yeah, it's wrong
[21:41] <micahg> I thought I fixed that
[21:42] <jtaylor> is subscribing even required? aren't they working over the upload queue?
[21:42] <micahg> yeah, I did, but I think people got upset, so I reverted