=== lifeless_ is now known as lifeless [10:08] can someone take a look what happens with Debian Import? [10:31] what you mean? [10:32] geser: http://qa.ubuntuwire.org/multidistrotools/universe.html#outdatedinB [10:32] packages from Debian are not coming [10:33] ari-tczew: Debian Import is only semi-automatic. An archive admin has to run a script for it. [10:34] geser: so who is responsible to this script? [10:34] any archive admin? [10:34] yes [10:34] or more precisely the archive admin of the day [10:35] https://wiki.ubuntu.com/ArchiveAdministration has the rotation [10:37] heh, not works on weekend [11:26] https://launchpad.net/ubuntu/+source/pygobject/2.21.2-0ubuntu1/+build/1787577 [11:26] can somebody check this [11:26] 'failed to upload' [11:29] Hmm, odd. wgrant ↑. [11:32] jpds, dupondje: Ah, well, you see, this is what we call a rejection that makes absolutely no sense. [11:33] I suggest retrying the build. [11:36] I have no permission :) [11:37] dupondje: find a core-dev of your choice and let him give the package back to the buildd [11:38] dupondje: we need to finish prepare a fix for asterisk [11:38] or simply ignore the problem (as sparc is most likely to get abandoned for maverick) [11:40] i'll note it to seb128 when he's online :) [11:40] ari-tczew: ? [11:40] dupondje: do you forgot? you tried to fix security issue for asterisk in dapper [11:42] err right :) [11:42] had a buzzy week, my brain is in stand-by [11:42] :) [11:42] http://ubuntu.dupondje.be/asterisk3.debdiff this was the latest :p [11:43] dupondje: I know, I have this patch on my disk [11:43] we can continue review, but not now [11:43] wow.. 14 hours of uptime and my mem is idling at a cool 1 GB.... go go maverick! [11:45] most of it is xorg and quassel :P [12:01] why DebianImportFreeze is always before FeatureFreeze? can't we set DebianImportFreeze and FeatureFreeze in one time? === angelus85 is now known as angelus === angelus is now known as angelus85 [13:20] hello [13:23] I'm currently working on a package to have it reviewed and uploaded. But I do have a question. When using debuild, do I have to sign the source package or not? [13:26] Respawner: Signing the source is required [13:27] (for security purposes) [13:27] JontheEchidna: ok, thank you === bdrung__ is now known as bdrung === G is now known as Nigel [14:24] bdrung: it can be synced directly, see bug #596265 [14:24] Launchpad bug 596265 in freemind (Ubuntu) "Please sync freemind 0.9.0~rc7+dfsg-1 (universe) from debian unstable (main)" [Wishlist,New] https://launchpad.net/bugs/596265 [14:33] BlackZ: done and marked the other two bugs as duplicates [15:28] BlackZ: you have my endorsement now [15:29] bdrung: thanks! === highvolt1ge is now known as highvoltage [16:29] Respawner: It's required to upload it. If you are just using it locally, it doesn't need to be signed. [16:30] lucas: This coming Thursday is Debian Import Freeze for Maverick. Doing a rebuild test next weekend would be a good time I think. Would this be possible? [16:59] bdrung: thanks for very quick response! [17:00] I'd be really interested if someone can figure out the reason for https://launchpad.net/ubuntu/+source/dnsruby/1.47-1/+build/1764845 [17:00] The build-deps are perfectly installable in a local Maverick chroot. [17:01] ari-tczew: you're welcome. [17:06] ScottK: I wonder how you could resolve this as I can reproduce it. Digging a little more shows: ruby: Conflicts: rdoc [17:06] geser: Odd. I just apt-get build-dep and it installed. [17:07] hmm [17:07] rdoc didn't get pulled in for my test. [17:07] So that would explain why it installed. [17:07] ruby provides also rdoc [17:08] Ah, so it's an install sequence issue. [17:09] apt-get -s build-dep works for my too [17:09] s/my/me/ [17:09] Sounds like it's a matter of dropping the rdoc depends from pkg-ruby-tools. [17:09] http://people.canonical.com/~ubuntu-archive/NBS/rdoc [17:09] could perhaps also help [17:10] No doubt. [17:11] * ScottK looks at lucas to find out if Debian is doing this transition too? [17:12] only rails, right-aws and right-http-connection have a versioned build-dependency. And rails is only an alternative [17:13] once the real deb "rdoc" is gone it should work [17:13] Nice. [17:13] it's similar to the texlive 2009 transition in lucid where a stale deb blocked some packages to build [17:14] * ScottK wonders if there's an archive-admin with sufficient access around to kill it? [17:14] james_w maybe? [17:16] ScottK: I just confirmed that this would fix it. I edit the Packages file inside my pbuilder and droped the rdoc package and apt-get install the build-dependencies works again [17:16] Cool. [17:21] I'm fixing right-aws === yofel_ is now known as yofel [17:23] Looking at right-http-connection too. [17:24] It makes sense then that the two problematic packages aren't in Debian. [17:29] I guess dropping the version from rdoc (make the build dependency unversioned) is enough as even dapper has a newer rdoc [17:29] Heh. I didn't look at it that closely. I just made them like rails. [17:40] geser: I filed a bug to ask for rdoc to be removed. Thanks again for your analysis. [17:42] geser: you aren't a core developer? [17:42] ari-tczew: nope, only MOTU [17:44] geser: heh, I'm amazed, because I think that you're in DMB and you've a large knowledge [17:44] ari-tczew: he is just too lazy to apply :P [17:44] * sebner waves at geser :) [17:45] sebner: I think that it would be nice if I'll block some requests on you [17:45] * ScottK notes to sebner that there is precedent for filing a core-dev application on behalf of someone else. [17:46] ari-tczew: hmm? [17:46] ScottK: hahaha :D [17:46] No. It's true. [17:46] ScottK: really? O_o [17:46] Yes. That's how Hobbsee got core-dev. [17:47] * geser waves back at sebner [17:47] ScottK: well, you can't do anything as long as the person in question is strictly against it though I think?! You can force anything over someone [17:47] sebner: you've only 1 bug sponsored for me. I think that number should grow [17:48] No, but you can solve the lack of motivation to fill out the application problem. [17:48] ScottK: ah, good point [17:48] geser: are you too lazy? :P [17:48] ari-tczew: ah, heh. maybe ;D [17:49] sebner: one merge is remaining to universe. are you interested? [17:49] ari-tczew: hmm, why not. link [17:50] ari-tczew: there is no requirement for being a core-dev for being in the DMB; and having a certain level of knowledge doesn't force you to core-dev [17:50] ScottK: speaking about motivation, remember the core-dev application of sistpoty? ;) [17:51] Yes. [17:51] sebner: no, it's just that I don't see the need for myself for being a core-dev. For the occasional uploads to main I do, sponsoring is enough. [17:51] heh [17:52] That's it, it seems :) [17:52] sebner: can you wait 5 minutes? I have to update description in patch [17:52] ari-tczew: sure, I can't promise I'll look at it right now anyways [17:53] ScottK: speaking about Hobbsee, has she disappeared? :( [17:53] ScottK: wow, that was pretty bad englisch but you understand it anyways :P [17:54] sebner: Consult the channel Nick list. [17:54] her english wasn't good enough? [17:54] ScottK: well, haven't seen any activity/uploads from her and besides, [Hobbsee] idle 199:13:59 .. [17:55] sebner: So she's around, just quiet. [17:55] ari-tczew: nah, I wrote "has she disappeared" instead of "did she disappear" [17:55] sebner: do you miss the LPSOD™? [17:55] geser: definately :) [17:55] ari-tczew: The comment was on the quality of sebner's own English. [17:55] aha ok [17:55] ScottK: well, being around means something different /here imho [17:56] She does speak every now and then. [17:56] ScottK: oh, Ic. thx for the info [17:57] I ask of english level, because I want to know what about of my english level [17:57] it's good or not good [17:57] ari-tczew: no problems so far imho [17:58] geser: was it you who wrote there is a lack of LPSOD some days ago? :) [17:59] sebner: no, I didn't try to summon the LPSOD for a very long time [18:00] ari-tczew: it's good enough that I don't have any problems to understand you [18:00] hehe, well, I'm glad, because my comments on my application says, that I have more problems with english than packaging skill :P [18:02] hohohoho [18:02] Jun 15 14:01:52 * ScottK finds an insufficiency of longpointysticksofdoom lately. [18:02] logs ftw! :) [18:05] hi after installing the latest perl I get the following output E:Error, pkgProblemResolver::Resolve generated breaks, this may be caused by held packages.' on sudo apt-get install -f [18:05] hi coolbhavi, nice to meet you on IRC [18:06] hi ari-tczew [18:16] got it resolved through aptitude -f [18:38] slangasek: why did you merge iputils, ignoring my patch? [18:38] it's not fair [18:40] 2010-06-07 core branches merge-lp-591029 iputils lp:~ari-tczew/ubuntu/maverick/iputils/merge-lp-591029 [18:40] sebner: sorry, but now my patch now is useless ^^ [18:41] heh, kk [18:41] ari-tczew: I'm avoiding branches till maverick+1 anyways :P [18:42] sebner: I don't understand, why? [18:43] ari-tczew: still not working 100%, besides I have to make changes, then push, then debuild and upload to ubuntu. Still too troublesome for me [19:06] * geser warns of opening the buildlog for https://edge.launchpad.net/ubuntu/+source/mozart/1.4.0-5build1/+build/1776421 [19:07] geser: sparc is about to go away. Don't waste your time with it anyway. [19:09] I just noticed earlier that artigas (sparc buildd) seemed to got stuck on this build. And wondered now about the build log as I saw that it's building an other package again. [19:09] geser: woo, firefox froze xD [19:10] sebner: I warned you :D [19:10] geser: It would be the same if you told me: "no sweets before meal" :P [19:11] sebner: it's a 278MB build log compressed to 309 kB [19:11] geser: that's a nice compression algorythm then :D [19:11] gzip :) but highly redundant data [19:12] heh, true [19:12] ScottK: I know, I wait on wgrant updating qa.ubuntuwire.org so he can merge my branch for the FTBFS page dropping sparc [19:13] Oh, right. I forgot it was you that had done that. [19:53] hi everybody. my name is tobias and i would like to upload one of my applications to ppa, but so far i didn't figure out the proper way to package a qt-application (that obviously comes without a "configure"-script and no "make install" target). is there any documentation on how to correctly package a qt-application for ubuntu? [19:55] t0bias: PPA packaging is better discussed in #ubuntu-packaging [19:55] oh, ok, thank you! [20:17] ScottK: if a comment in the debian/changelog file is broken (I can't find the changes in the ubuntu package merging) I should drop it, shouldn't I? [20:18] ari-tczew: hrm, apparently because I failed to check the bug list for that package before working on it - sorry [20:19] ari-tczew: for some reason the bug page also doesn't show me a link to your branch? [20:19] er; because you've deleted the branch, I guess? [20:20] ari-tczew: I would be happy to review and merge your branch in place of mine if you want to re-publish it [20:21] slangasek: I've deleted the branch, because today I've updated the patch description [20:21] slangasek: so do I need to reupload and you'll merge it? [20:21] if you reupload it, I can merge it, yes [20:22] ok [20:22] wait 5 minur [20:22] minutes [20:24] slangasek: I prefer to use bzr as you saw, but what I can to do it, if you've uploaded your changes? [20:24] use debdiff instead bzr? [20:25] ari-tczew: I can uncommit the changes from bzr [20:25] slangasek: so what we will deal with it? [20:25] s/what/how [20:25] bzr please [20:26] just publish a branch based on revision 14 of the package branch [20:26] or 15, if you're satisfied with the upstream merge and don't want to redo it :) [20:29] slangasek: hmm, what do you think if I'll use my debian/changelog and patch for typo based on 18 revision? [20:29] ari-tczew: that's also ok [20:29] nice! then uploading [20:36] slangasek: done [20:44] ari-tczew: and package uploaded - thanks! [20:45] slangasek: thanks also! [20:46] * slangasek goes back to ripping dpatch out of aptitude === vish is now known as MrAcosta === MrAcosta is now known as vish [20:59] does anyone know what prevents nspluginwrapper 1.2 from being backported to hardy? (it has been backported everywhere else) [22:16] let's say there is a standard package P, and I have a patched version of it, with added features. And then I have a package B which uses some added feature of that P. Is there any way to express this dependency, using suitable versions. I want to avoid binding B to exact version of P. I would like to be able to upgrade (my patched) P without releasing B just to change the = dependency. [22:20] mmc: maybe make a P-patched package instead of changing P's version number? [22:21] and make P-patched Replace P, so that it will (I think) be automatically installed instead of P when someone wants to install B [22:21] quick question,can we rename upstream tarballs? [22:21] shadeslayer: yes, but only if you really can't do otherwise [22:21] actually [22:21] you *have* to rename it to add orig.tar.gz anyway [22:22] so more specifics, maybe? [22:24] Dear all how 2 install yahoo messanger [22:25] rehan: this is not really the place to ask this, try #ubuntu :) [22:37] Bachstelze: also upstream ships the source with their own debian/ can i safely delete it and start over as this will be a new package in the archives? === rehan is now known as MianRehan [22:52] shadeslayer: in this case it's recommended to first talk to upstream and see if they could remove the debian/ dir from their tarball [22:52] ptherwise you can move it away with get-orig-source I think, no need to repack it [23:14] is there a procedure of sorts to get new packages into ubuntu universe? [23:23] !newpackage | shadeslayer I guess here [23:23] shadeslayer I guess here: The packaging guide is at http://wiki.ubuntu.com/PackagingGuide - See https://wiki.ubuntu.com/UbuntuDevelopment/NewPackages for information on getting a package integrated into Ubuntu - Other developer resources are at https://wiki.ubuntu.com/UbuntuDevelopment - See also !backports [23:23] ok found it via google ;) [23:34] * shadeslayer wonders if someone is in the mood to advocate a revu package [23:34] http://revu.ubuntuwire.com/details.py?upid=8319 [23:35] apparle: \o