[00:05] bobbo: giving the key explicitly worked [00:08] schakrava: good :) [00:10] bobbo: my computer is acting very strange. brb. reboot [00:19] ScottK, ping [00:20] bobbo: here is the pastebin: http://pastebin.ubuntu.com/36691/ [00:21] bobbo: i mean debdiff [00:22] schakrava: cool, I have to go to bed now, but it looks good (only a few little things would need changed) [00:23] bobbo: thanks. have a good night! [00:23] schakrava: I'll have a proper look tomorrow [00:23] bobbo: sure thing. [00:29] hello all I am trying to figure out how best to send a font change upstream [00:33] effie_jayx: Were you able to migrate the change from the .ttf itself to the source? [00:34] good night [00:37] *cry* I miss doing MOTU work.... internships suck.... [00:38] jdong: MOTU work misses doing you as well. [00:39] persia, I got soruce files to it but I am unable to build the package [00:40] persia, I was directed to https://launchpad.net/ubuntutitle [00:40] jdong, in order to ease your pain, i'd let you REVU http://revu.ubuntuwire.com/details.py?package=mythstream-parser-youtube ;) [00:41] effie_jayx: What happens when you try to build the package? [00:41] to send "it" upstream... I am guessing I can send my sdiff (diff file between FontForge Source files ) [00:41] persia, fails to buid since it has a binary in it ... (the ttf file) [00:41] effie_jayx: The binary is modified by debian/rules clean? [00:42] persia, nope [00:42] effie_jayx: RIght. Apply the *source* changes to the package, and build that. Send the source patch upstream. [00:42] persia, the binary is there... and it complains stating ... "Irrepresentable changes in the ttf" [00:42] effie_jayx: RIght. The ttf should only be changed at build time, not at packaging time. [00:43] ok [00:43] persia, learning curve... you are mean [00:44] effie_jayx: Sorry. Not my intention to be mean. My intention is to help, but I've never edited a font, so what I can suggest is limited. [00:44] persia, no worries... nice way to get back to MOTU work [00:45] persia, funny thing is that the font source won't work... since I doubt it gets generated at build time [00:46] What is the license for the font? [00:48] persia, SIL OPEN FONT LICENSE Version 1.1 [00:49] * persia goes to read that, not being familiar [00:51] effie_jayx: Seems sual-licensed under OFL and GPL. If we select OFL, we can't patch it in Ubuntu (cannot distribute modified versions under the same name), so let's choose GPL. [00:52] If we choose GPL, we have to distribute source matching the binaries, and modify the source when we want to change it, so we'd need to build the binary from the source. [00:53] Looking at the packaging though, it doesn't seem like we build the binaries from the source. [00:53] I'd suggest complaining to upstream, and perhaps opening a bug to demote to multiverse. [00:54] Alternately, fix the build system so it does build the binary from the source. [00:54] (which may clobber the existing binary, but I've not much sympathy) [00:59] persia, ok, Not an easy fix, But I am up for it [00:59] persia, heck I already spent hours on the actual font, I might as well carry it on [01:00] effie_jayx: You always seem to get the ones that look easy, but aren't really. You are to be commended on actually fixing most of them. [01:01] persia, I made sure I closed all open bugs for missing glyphs... [01:01] so people will be happy that some glyphs will be available [01:02] persia, how do I complain to upstream... the launchpad project does not have contact, [01:03] effie_jayx: It does have a list of "Most active people". You might try chasing them. [01:03] persia, right... cool thanks for your words.. I shall get working then [01:10] persia, I am currently sending an email to the top contributors and also I am workin on a package with binaries on it... using uuencode and uudecode [01:10] effie_jayx: uuencode and uudecode fun! luck with ti! [01:10] it* [01:11] nxvl, heh... I hope you are not being ironical ... :S [01:11] :P [01:11] effie_jayx: don't bet [01:11] effie_jayx: uuencode / uudecode doesn't allow distribution under either the OPL or the GPL though. [01:11] For OPL, either we need to not modify, or we need to change the name. For GPL, we need to ship a working source. [01:11] persia, hw do they get the ttf in the pacakge then [01:11] effie_jayx: if you want, you can check apache, i added some icons to it and decode them on debian/rules [01:12] effie_jayx: so you can use it as an example [01:12] effie_jayx: They are upstream: they don't have to comply with the license. [01:12] persia: i did it for some icons on apache [01:12] (Well, for a sufficiently large project, this ceases to be true, as coordination between contributors to not comply becomes more complicated than compliance) [01:13] persia, What should I ask upstream then to change license and demote the package to multiverse? [01:13] or rather suggest [01:13] nxvl: Yes, but for icons it is arguable that GIF is one of the "preferred forms for modification", as there are plenty of GIF editors. For this font, it's fairly clear that Ubuntu-Title.sfd is supposed to be the source. [01:14] oh [01:14] he's encoding a font [01:14] now i get it [01:20] persia, what is the point in demoting the package to multiverse [01:20] ? [01:20] apart from letting us work with it [01:22] effie_jayx: Demoting to universe would let us use OPL, so while we couldn't patch, we could push binary patches through upstream. Having it in universe means the font neds to be built at build time. [01:22] Err. Demoting to *multiverse* [01:23] persia, mind If I cc you on the email ? [01:23] effie_jayx: You could, but I doubt I have much to contribute. [01:24] persia, your insights on packaging? since this package needs a bit of more neatness [01:26] effie_jayx: I guess: to me it seems to be more about licensing than packaging. Anyway, send a copy my way, and I might comment on the response. [01:26] thanks persia [01:29] persia, I have just generated a dsc without modifying the binary and be able to generate a pack [01:31] a patch between the new and the old.. that should commit a fix and push for action upstream [01:31] while the email sorts the package issue [01:32] effie_jayx: I don't understand exactly what you mean, but I doubt upstream can use a binary patch to the ttf either, as then they might have issues modifying it. [01:32] persia, you can generate sfdiff out of the two files [01:33] effie_jayx: Hmm. Maybe then. [01:33] I still think they have some source file from which they work. [01:36] persia, you mean it is not Ubuntu-Title.sdf? [01:36] .sfd [01:37] effie_jayx: No idea. Can you generate Ubuntu-Title.ttf from Ubuntu-Title.sfd? If so, then just put that generation in debian/rules, and you're all set. [01:40] persia, I'll find out [01:41] foxxtrot: if the setup.py file is using the standard setup-tools module, then --prefix should work [01:41] I'll run tests of both [01:41] have you uploaded the package to revu? [01:43] I've barely started the debhelper process. [01:43] I do have a different package to upload to revu though, I've only put it in my PPA so far (my wife and a co-worker of hers needed the package sooner) [01:44] Of course, the PPA stuff is targetting hardy, I should target intrepid with anything pointed at revu, yes? [01:48] And anything I upload to REVU should list it's Section as universe/sub-section right? [01:49] Target intrepid, yes. Using universe/ as a prefix, no. [01:51] Thanks [01:51] hi all. [01:51] how much time needs to a package be compile in archive? [01:54] k0p: Between 1 minute and 60 hours, depending on the complexity of the package. Note also that sometimes there is a queue, so the build may not start for a while. [01:55] hmm sure. [01:55] and how I can know about that? [01:56] k0p: e.g. https://launchpad.net/ubuntu/intrepid/+builds [01:57] * persia notices that https://launchpad.net/ubuntu/intrepid/+builds?build_text=&build_state=pending is empty, and encourages lots of uploads. [01:58] persia, https://launchpad.net/ubuntu/+source/umit/0.9.5-0ubuntu1/+build/687956 [01:58] should it be on archive ? [01:58] Does REVU use that build queue? [01:58] foxxtrot: Packages on REVU are not autobuilt. [01:58] ah [01:59] How long does it take a package uploaded to REVU using dput to show up on the REVU site? [01:59] I think the list is refreshed every 5 minutes foxxtrot [01:59] k0p: It waits on binary NEW : https://launchpad.net/ubuntu/intrepid/+queue [01:59] ok [02:00] I swear this packaging guide is going to drive me insane [02:01] persia, thanks [02:01] how much of the packaging guide do i need to fully understand before i can go and try to start getting mentored and start helping out? [02:01] JasonSpradlin82: None of it. [02:01] persia: oh [02:02] persia: i'm getting to understand more and more of it, but it takes a long time, because its not exactly intuitive to those unfamiliar with the basics [02:02] More specifically, you'll want to understand the basics of Debian format packaging, which may also be gleaned from examination of some sample packages. You'll also need a willingness to learn, and to research anything on which you are unsure. You may find that much of what you end up discovering that way is also in the Packaging Guide. [02:03] yeah... i tend to learn better by DOING or by being taught in an environment wwhere I can ask questions... one cannot ask questions of the packaging guide [02:03] Yes, it's not very intuitive. Personally, I found it easiest to work with small modifications to packages to build familiarity. Closing small bugs is a good way to do this, and gives you exposure to a variety of packages. [02:04] I personally found following the New Maintainer guide's example and disassembling the hello package to help a lot [02:04] Damn, I may not be able to package this very easily. Some of the code is in a 'questionable' licensing state [02:06] If it contains any code not licensed under an OSI-style license it has to go into the multiverse, right? [02:06] foxxtrot: It has often been said that debian/copyright is the hardest part of packaging [02:06] Well, all but this one .so are GPL [02:07] But the non-GPL code only has a copyright associated with it. I'm going to need to email Swofford and figure out the licensing for this code. [02:07] Since the package seems to depend on this .so it builds [02:43] jdong, in order to ease your pain, i'd let you REVU http://revu.ubuntuwire.com/details.py?package=mythstream-parser-youtube ;) [02:43] bah, sorry [02:43] If you are a MOTU and are bored right now have I got a deal for you. To help ease your boredness, I'll let you REVU my package http://revu.ubuntuwire.com/details.py?package=mythstream-parser-youtube I've made the requested changes from the last REVU and am ready for another. This offer valid while supplies last. [02:48] Holy [02:48] I just got a AM [02:48] *an [02:48] * NCommander faints [02:49] tgm4883_laptop: lol I had to review some heart attack-inducing code at work today, so I think I'll take a break before I burst a vessel somewhere :D [02:50] tgm4883_laptop: though I'm CONFIDENT your code will be better than what I've seen today [02:50] heh, take a break then. I didn't mean to ping you about it twice ;) [02:50] hope so, i've had 2 REVU's on it already and fixed many things ;) === zookoafk is now known as zooko === RoAkSoAx_ is now known as RoAkSoAx === zooko is now known as zookofamtime [03:17] effie_jayx: Pong [04:19] ScottK, I meant to ask you about ttf-Ubuntu-title, I have made some changes to fix some bugs but I can't seem to package them due to binary changes. I saw you were a past contributor- I thought you could help with some pointers [04:20] effie_jayx: No. Sorry. I think I helped a bit with some packaging questions, but don't recall much about the package. [04:21] ScottK, right... thanks [04:25] ScottK, the issue is that the ttf is a binary that does not get generated by the source in the pacakge.. due to licencing uuecode and uudecode cannot be used. and I am figuring out a way to build the ttf from source. I have contacted upstream about it and I am holding on to a reponse === kc8tad is now known as rrittenhouse === RoAkSoAx_ is now known as RoAkSoAx [06:16] If you are a MOTU and are bored right now have I got a deal for you. To help ease your boredness, I'll let you REVU my package http://revu.ubuntuwire.com/details.py?package=mythstream-parser-youtube I've made the requested changes from the last REVU and am ready for another. This offer valid while supplies last. [06:16] :) [06:38] can someone plese have a loof at the .dff.gz for bug 255224 and sponsor after review? [06:38] Launchpad bug 255224 in gnusim8085 "New Upstream Release 1.3.4" [Undecided,Confirmed] https://launchpad.net/bugs/255224 [06:43] good morning [06:43] good evening ;) [06:50] tac-plus is not in the repository, was in there back in the gusty days [06:50] anyone able to fix this? or i need to compile my own? [07:07] Hey guys. I nominated high priority bug 248055 for SRU a month ago and it's still sitting there for nomination. Have I followed the correct process so far? Is someone able to give the bug a bump? It's an easy fix (essentially a backport). [07:07] Launchpad bug 248055 in gtk-gnutella "gtk-gnutella cannot connect to newer network - ancient version detected" [High,Triaged] https://launchpad.net/bugs/248055 [07:09] does anybody know if Bhavi Shankar is on IRC every now and then? [07:09] hi Koon [07:09] hello Daniel ! [07:26] dholbach: he is [07:26] dholbach: he often turns up for MOTU school as well if I remember correctly. [07:26] I think he's "coolbhavi" here, right? [07:26] dholbach: he's coolbhavi, usually found in -in [07:27] what's he done now? [07:27] I was just looking for him [07:27] Hew: It looks good to me, but the solution is very much not clear. Have you considered requesting a backport of the new version? [07:27] ahh. try -in [07:28] * Hobbsee goes back to trying to figure out this hell-spawned subject list. [07:28] persia: I read somewhere that if a backport is to fix a bug, then it should be done as a SRU [07:28] persia: I assume the fix is just a backport, but to *-updates [07:28] Hew: Yes, that is true, although in this case, I think both routes make sense. [07:29] persia: What action should I take? Request a backport as well as the SRU? [07:29] I'm not sure I like the idea of an upstream-forced upgrade because of declared incompatibility. Also, to move forward, your bug needs someone to look at preparing a patch that does the right thing (whatever the right thing might be). [07:29] persia: It's broken _because_ it's the old version, that's the problem. I don't think it's something that a patch to the old version can fix [07:30] Hew: Yes, which makes it extra complicated. bugfixes should go through SRU, but the new version surely has other changes. [07:30] I suspect the complication is part of the delay. [07:30] indeed [07:30] Does anyone other than Hew use gtk-gnutella? [07:31] persia: I'm on Intrepid myself now so it's not even a problem for me anymore, but the longer it goes on, the more people appear on that bug report. [07:31] Hew: Understood. I'm just hoping someone else with experience with the software might have an opinion. [07:31] When I was on Hardy though, I tested the Intrepid package and it was all fine. [07:31] yep [07:32] persia: I think its a mistake to put more consideration into an SRU than the aggregate consideration done over a release cycle [07:32] * RAOF wasn't aware that the gnutella network still _existed_. [07:32] persia: because it makes the SRU have a higher bar than the next release does, and thats silly. [07:32] lifeless: Do you want to upload the new version to hardy? [07:32] I have a critical data loss bug to fix first [07:32] just making an observation [07:34] my opinion is that, by "backporting" as a SRU, there will be a far greater benefit (everyone has a working client) compared to the risk of regression. [07:34] Anyone from MOTU SRU about? If Hew pushes the intrepid gtk-gnutella to hardy, woudl that be approved? [07:36] We should probably collect a list of these "only the latest version works" packages; I remember some discussion about Tor along similar lines. [07:38] Some of the games are that way too: openarena, tremulous, nexuiz (note that one *can* run the old server, but that it's hard to find them on the net) [07:39] If you are a MOTU and are bored right now have I got a deal for you. To help ease your boredness, I'll let you REVU my package http://revu.ubuntuwire.com/details.py?package=mythstream-parser-youtube I've made the requested changes from the last REVU and am ready for another. This offer valid while supplies last. [07:53] * Hew just found two questions on answers.launchpad about the bug as well.. [07:55] anyone have information on Kickstart compatibility on Ubuntu here? the wiki page seems very very old and outdated. If someone could give me poitners to that will be very helpful. [07:56] not sure whether this is right channel to ask. [07:59] tuxmaniac: Not really the right forum, but depending on your requirements, FAI and debian installer preseeding may also be interesting. [07:59] I thought kickstart was still supported [07:59] tuxmaniac: it probably hasn't been updated because it hasn't needed one [08:00] ok thanks. [08:04] debian preseeding page seems to be having quite a lot of info. thanks persia [08:05] tuxmaniac: Note that lifeless could well be perfectly correct: kickstart might just work as documented there. [08:05] ok [08:30] Good morning. === rulus_ is now known as rulus [09:16] morning everyone [09:16] huats: hi [09:16] hey mister sylvaing [09:16] :) === dholbach_ is now known as dholbach [10:18] is there a display problem with the http://revu.ubuntuwire.com website? [10:19] there are no packages in the "needs review" and many many in the "advocated packages" category [10:19] silwol: Indeed, and those in "Advocated" don't seem to have records of advocation. [10:20] moin [10:21] Uh oh [10:22] damn it [10:22] RainCT broke it [10:22] I should be able to revert one revision [10:28] silwol, ignore it for now, it looks like we're experiencing some mild db corruption [10:28] no problem for now, just wanted to make sure you know about the problem [11:10] TheMuso: are you around ? [11:13] any motu-sru around? [11:13] bigon: +1 for me :) === lamego is now known as joaopinto === RainCT_ is now known as RainCT [11:33] When do we need to use provides/conflicts/replaces ? [11:47] Syntux: Provides when something meets a (possibly virtual) dependency. Conflicts when there is a file name in common between two packages (note that policy mandates it work in essentially the same way: cf. /usr/lib/sendmail), replaces when one package should overwrite files from another package. [11:48] The most common case is when you have multiple binaries from a single source, and move some files between them. The package getting new files then Conflicts with older version of the package that gave it the files, and also replaces it so as not to confuse dpkg. [11:49] persia, I'm using them with stardict english arabic dictionary because I'm going to package another english arabic dictionary for stardict provided from different source, would that make it correct us ? [11:50] ping nijaba [11:50] Syntux: Is there a reason you can't install them in parallel, with slightly different file names? Users might want to compare both results. [11:50] persia, different licenses [11:51] persia, we only have one GNU dictionary, two CC dictionaries but they are not general dictionaries but economic and politics i guess [11:52] and the last one is free from babylon but they didn't mention the license but it's freely available in babylon format easily converted to stardict format [11:52] Syntux: Sure, but is there a reason they should not all be installed, assuming the licensing is sorted? [11:53] persia, the two general didn't work together when installed [11:53] Syntux: Why not? [11:54] persia, no idea why [11:54] Syntux: That'd be the fist thing to investigate, before fussing with Conflicts/Replaces/Provides [11:56] persia, hmm but this isn't my game, I mean I don't know how to investigate why it's happening === zookofamtime is now known as zooko [11:58] persia, although they work just fine when both installed but one is disabled. [12:03] Syntux: You might check the error messages, etc. [12:03] ok [12:03] another question [12:04] * persia is in a meeting, and hopes someone else can answer [12:04] babylon english-arabic dictionary is freely available http://www.babylon.com/define/98/English-Arabic-Dictionary.html but they didn't mention any license [12:04] argh freenode [12:12] Syntux: it must have a license to be included in the distribution [12:14] mok0, and by putting them online for free download that doesn't mean it fits under any license ? [12:15] no, just because you can freely download it, doesn't mean that you can also distribute it [12:15] mok0, what if we converted its format into something else? does that make it ours? [12:15] Syntux: no [12:16] Syntux: you need to get in contact with babylon [12:17] Syntux: check what the DFSG says [12:17] mok0, what if someone else converted it and I just packaged what he converted? do I have to track the second level? [12:18] Syntux: yes, you can't do that, it will violate the originators copyright [12:19] I studied law for two years and we do not track 2nd source in money laundry cases but we do in licenses, interesting :D [12:19] Okie, I will put contacting babylon on my todo and will only package the GNU dictionary for now [12:19] Syntux: :-) hehe [12:20] Syntux: the rule-of-thumb is that there _must_ be a license, and that license must conform to the DFSG [12:21] Syntux: Several times, I [12:21] I [12:21] mok0, yeah I understand but the thing is, babylong dictionary itself is free and its dictionaries are free too [12:21] I've had to contact upstream to get them to clarify their license [12:21] although there is no license but we should make use of such enormous free efforts [12:22] mok0, great, can you give me an example of what should I ask them about ? [12:22] Syntux: Unless there is an explicit license that allows us to distribute, it doesn't matter that it's free... [12:23] Syntux: Ask them to include a license in a file with the dictionary source (which has to be editable, btw) [12:24] I still can't get it because naturally no one can own the words [12:24] why does the dictionary source have to be editable? if it's to live in multiverse it shouldn't matter. [12:24] although it'd be better if it was editable [12:24] it's like licensing the bible or holy quran [12:24] laga: It has to be in "preferred modifiable form" [12:25] Syntux: well, in contrast to the two works of art you refer to, these guidelines make sense [12:25] ;-) [12:26] Syntux: Actually, it is possible to copyright collections of things (ie, the result of putting a certain collection together is coptyrightable) [12:26] ok, I'm going to create a software and license both books and then the whole world should "Show me the money" [12:26] :d [12:26] I'd also point out that in the UK there is crown copyright on the KJV bible. [12:27] humans! [12:27] * mok0 wonders if God/Allah don't have copyright... [12:28] Any Python folk know how I can urllib2.urlopen("https://edge.launchpad.net/~ubuntu-dev").read() - and check if the text: "You are not a member of this team" is in the page source? [12:28] not sure if God/Allah have a copyright but he have a database for sure :D [12:28] Syntux: lol [12:29] and some secret agents spying on us [12:29] jpds: Can't you just set up a regexp using the re module? [12:29] jpds: Sounds like you just want something along the lines of 'if "you are not a member of this team" in urllib.whatever' :) [12:29] "You are not a member of this team" in obj.read(), if you don't mind being inefficient [12:29] which is against our privacy! [12:29] mok0: I tried that, I think my regex didn't work. [12:30] jpds: so... make it work? [12:30] mok0: I've tried, that's why I'm asking. [12:30] jpds: show us the code (pastebin) [12:30] the new API doesnt have team membership status ? [12:31] mok0: Seems I removed it experimenting.. [12:32] jpds: ah [12:33] jpds: Syntux is right, you should check out the new LP API [12:33] jpds: it may do what you want [12:34] OK, I'll check it out. [12:34] or I'd awk it. [12:38] mok0, for gnu dictionary sections should be free/text ? [12:41] Damn it, the reason the above failed was because the page had: "You must log in to join or leave this team". [12:41] hi folks. can someone please look into bug 255224 and sponsor? thanks in advance [12:41] Launchpad bug 255224 in gnusim8085 "New Upstream Release 1.3.4" [Undecided,Confirmed] https://launchpad.net/bugs/255224 [12:43] Syntux: I don't know [12:43] Syntux: I think they have to be free as in free speech [12:46] they are [12:46] with gnu license [12:46] editable format [12:46] what else do you want? haa? [12:46] Syntux: sounds about right [12:47] Hah. I win! gnome-main-menu builds again. [12:47] Syntux: check the writeup for the gnu dictionary app [12:47] Now I simply need to resist the urge to pull in more functionality from SVN while I'm pulling in patches to make it build. [12:47] Syntux: they might actually not care about the dictionary [12:47] I'm trying to find list of section in ubuntu to see which fits most [12:48] Syntux: but Debian/Ubuntu want the license to follow the DFSG [12:48] RAOF, if you torture the package it will build. [12:48] mok0, babylon case closed, I sent them an email and I wont bother packaging their dictionaries before hearing from them [12:49] Hm. It seems build != work :) [12:49] Syntux: great [12:49] mok0, now I'm talking about arabeyes gnu dictionary available in dictd format and someone converted it into stardict and I'm packaging it [12:50] there is no text section but translation but they mean something else by translation [12:50] Syntux: OK, sounds good. I don't know the last thing about dictionary formats, though [12:51] it's free/text neyahahahaha [12:54] * Syntux wonders when he'll have 10mbs [12:59] persia, I got a reply from upstream. they are meging some changes and they will fix the font. [13:00] RAOF: What are you doing to the poor menus? [13:00] effie_jayx: Excellent news indeed. Will they also fix the packaging, or do we need to move it to multiverse? [13:01] (or can we fix the packaging to be GPL?) [13:02] persia, they are first fixing the font, aparently they have 7 different branches. they will not move the package to multiverse since it is of canonical maintenance. first they merge and they will build a better package for it... [13:02] basically they said... thanks kid, we got it covered [13:03] * persia doesn't think Canonical gets a special pass for licensing, and hopes they fix it. [13:04] persia, If they don't, in a years time I'll rant :D [13:05] persia, how come the ubuntu-title isn't usable in many languanges... it is in the ubuntu promise... [13:05] heh [13:05] persia, you are right ... some luck I have with bugs [13:05] effie_jayx: Just upstream didn't fix that. Wasn't it in universe anyway? [13:07] jelmer: ping [13:07] jelmer: can bzr-upload on REVU be archived? [13:07] persia, it is universe === RainCT is now known as RainCT_ [13:10] persia: Do you know what the direct config.sub changes in jabberd2 are for (you uploaded *ubuntu3 in january)? [13:11] Kopfgeldjaeger: Err, no. Let me check to see if I have any of that information accessibly offline. [13:12] persia: what do u do for a living... out of interest === nhandler_ is now known as nhandler [13:14] stefanlsd: I'm currently mostly a developer. I've had lots of different jobs though, although mostly in technology. [13:15] persia: oh ok. employed or self employed? [13:15] stefanlsd: Employed. [13:16] persia: oh ok. cool. just you're so active and busy here, so i was just wondering [13:16] * stefanlsd tells canonical to employ persia fulltime [13:16] I have unlimited access to IRC at work. [13:17] * broonie is on IRC for work purposes :) [13:18] stefanlsd: Also, I'm in UTC+9, so you're usually about in my evenings, which likely impacts your perception. [13:18] oh ok. that would also explain it. [13:26] question: is there a netbook channel? [13:27] elkbuntu: you could try #ubuntu-mobile *shrug* [13:28] Kopfgeldjaeger: Sorry, I know nothing about that package: I only rebuilt it for NBS, but didn't look at it. [13:28] ok [13:29] yeah... i was thinking something more aimed at eeepcs, not phones === thunderstruck is now known as gnomefreak [13:39] Ubuntu Mobile isn't for phones. Hardy only has MID support (very small laptops, small tablets, etc.). Intrepid may have subnotebook support, if the right package set can be assembled. [13:50] persia: subnotebook = eee-class? [13:52] Treenaks: Yep. If you look at intrepid, you'll notice two meta packages: ubuntu-mid for the very small devices (4-6" screen, although there are some 3.5" devices it might work with), and ubuntu-mobile for the next larger (7-9" screens). 10"+ are likely candidates for ubuntu-desktop [13:52] persia: Do we have the all clear to copy gtk-gnutella from Intrepid to hardy-proposed? bug 248055 [13:52] Launchpad bug 248055 in gtk-gnutella "gtk-gnutella cannot connect to newer network - ancient version detected" [High,Triaged] https://launchpad.net/bugs/248055 [13:52] persia: well, that assumes the hardware works [13:52] * wgrant raises the alarm. [13:52] Hew: No idea. Did you hear from anyone in motu-sru? [13:53] persia: nope [13:53] Copying from Intrepid sounds bad. [13:53] Treenaks: How do you mean? (and maybe #ubuntu-mobile is a better place) [13:53] wgrant: Check out bug 248055, would be great to have extra eyes on it [13:53] Launchpad bug 248055 in gtk-gnutella "gtk-gnutella cannot connect to newer network - ancient version detected" [High,Triaged] https://launchpad.net/bugs/248055 [13:54] * RainCT is thinking about if it would be good to have a 'ubuntu-packaging' metapackage which would pull in (as recommends) all the packages listed in the PackagingGuide [13:55] RainCT: why? [13:55] * persia already has too many packages pulled by ubuntu-dev-tools [13:57] persia: 'Tis my fault, I'm afraid: http://bazaar.launchpad.net/~ubuntu-dev/ubuntu-dev-tools/trunk/changes [13:58] jpds: I'd be very happy if you could add sbuild as an alternative to pbuilder, especially given the presence of the mk-sbuild-lv binary. === apachelogger_ is now known as apachelogger [14:06] persia: I shall look into it. [14:11] It looks like $package ships with an old version of a file and I need to libtoolize --force --copy before it builds successfully. Is this OK? [14:12] 6/14 [14:12] (oops) [14:18] http://apu.debconf.org:8000/Salon_del_mar.ogv.m3u [14:22] Hobbsee: A "buildd" script is now in ubuntu-dev-tools trunk, and it does all the mozilla cookie extraction for you. FYI. [14:22] jpds: woot! [14:22] :) [14:25] jpds: and you're missing a nose [14:26] RainCT: :~> [14:26] strange nose :) [14:27] :Ձ( [14:27] directhex: is that a Debian nose? [14:27] ooh, this one works well. :ᐊ) [14:39] Heya gang [14:49] * jpds uploads new ubuntu-dev-tools package. [14:52] * emgent clap clap clap [14:56] can some non-MOTU verify on REVU if he sees an Archive/Unarchive option on the details.py page for his packages but not on those from others? [14:57] (just look if it's there, no need to try it out as it doesn't do anything yet it you are not a MOTU) [14:58] jpds: you're spamming my mailbox :) [14:59] I can see an Unarchive option [14:59] RainCT: Use proper mail filters. [14:59] Kopfgeldjaeger: and is the package archived? [14:59] for mine [14:59] * slytherin wonders why we are still stuck at grub version 1 in Ubuntu. What happened to grub 2. [14:59] yep [15:00] slytherin: Needs more testing. [15:00] jpds: what's the point of subscribing to diffs if I filter them out afterwards? xD [15:00] Kopfgeldjaeger: great, thanks for checking :) [15:00] RainCT: You can later review them to understand the changes. [15:00] no problem ;) [15:01] persia: what kind of testing. [15:01] persia: well, but for that I can also do a bzr diff -rXX..YY [15:01] RainCT: I am able to archive one of my own packages on REVU too [15:01] that with the mailbox spaming was a positive comment, btw [15:01] * jpds hugs RainCT. [15:02] slytherin: http://www.gnu.org/software/grub/grub-2-faq.en.html #2 [15:02] thanks, nhandler. no more testing needed for now [15:03] persia: It works well on i386 at least. But I will wait if people think it needs to stabilize. [15:04] slytherin: Considering that the vast majority of new 9386 compatible hardware is really amd64 or lpia, I'm not sure that's sufficient. On the other hand, November is soon: might be worth proposing for intrepid+1 [15:05] hmm === superm1 is now known as superm1|away [15:09] jpds: does requestsync also check if a MOTU requests a sync for a main package? as this also requires sponsorship [15:10] geser: Err, I'll fix that with next upload. [15:31] don't suppose anyone from the ruby area is awake ? [15:34] is it me only or the ubuntu wiki is down ? [15:34] raphink: here it works [15:35] hmmmm [15:35]