)" [Critical,Confirmed] https://launchpad.net/bugs/195369 [12:20] <\sh> I adjusted the bug actually [12:22] \sh: Now you just have to wait for either two ACK's or one not-for-us :) [12:23] <\sh> persia: well, not-for-us gives many angry users, including me ;) [12:23] \sh: "not-for-us" means not-for-motu-release, meaning not--a-FFe, meaning, "Just upload, already". [12:24] <\sh> persia: ah...;) I thought "not-for-us" means "no, we don't want this in" ;) [12:25] \sh: No, I've seen a couple FFe requests that were unsub'd as not-for-us because a member of motu-release didn't think they needed an exception. [12:28] fdr: As I'm sure that you've already read, just download the po to find the translation that you want. Then fix it either online or in the po and re-upload. [12:30] frenchy, mmm... thanks, but either I am missing something, or it takes particular privileges to re-upload the .po file... [12:31] Would I be wrong in assuming that getting a FFe for an "extra" would be easier than an "optional" or "recommended" priority? [12:32] fdr: well I can on my project ... let me try someone else's ... does the "Upload a file" option come up for you? [12:34] frenchy: Assuming the package has the correct Priority, likely, but it's really a matter of avoiding possible regressions or transitions, as there's not much time left for testing. [12:34] fdr: Yeah, LP can sometimes be a bit confusing. I subscribe to the Brownian motion theory of just start clicking till stuff works ... i.e. Click the "View Template & All Languages..." to get the upload link. [12:35] fdr: Go figure. [12:35] on dia, when I select the "translation" tab it says that the project is not set up to manage translations with launchpad, while when I can't find the page for language-pack-gnome-it [12:36] mmm I *hate* LP. It seems just to be trying to stand in my way and nothing more. [12:37] persia: Thanks again. Your continued effort amazes and inspires me. I'm sure that a lot of developers get caught in this pattern of minor bugs fixes that they want uploaded (80-20 rule). [12:39] fdr: I hear you. Somethings it does really well and I haven't really found a better alternative. [12:39] well, I did no real work with either, since I only reported some bugs, but I liked bugzilla much more :) [12:40] boo [12:40] frenchy: Yep. Personally, I tend to look at different packages after the freeze starts than I was chasing beforehand. There are lots of easy bugs and simple packaging tasks that need doing that often get missed because nobody is paying attention to some package. [12:40] * persia turns on all the lights [12:41] Hobbsee: boo who [12:42] Hobbsee: Don't worry .. that was a joke ... I laughed, so it hit its intended audience. [12:44] persia: Yeah, I'm now aware of the amount of work that you guys put in to hold this thing together. 3 Cheers for MOTU. I have enough trouble with one. [12:52] <\sh> Hobbsee: my dear release member :) could you provide your opinion to https://bugs.launchpad.net/bugs/195369 , please? :) thx :) [12:52] Launchpad bug 195369 in claws-mail-extra-plugins "[FF Exception] Please merge claws-mail-extra-plugins <3.3.0+dfsg-2> (universe) from Debian (

)" [Critical,Confirmed] [12:55] * Hobbsee is playing with shiny things, and is therefore distracted [12:55] <\sh> Hobbsee: diamonds? :) [12:57] https://launchpad.net/~joejaxx/+packages is looking sparse :( i need stuff to do lol [12:57] nope [13:07] joejaxx: There's about 200 packages that need maintainer mangling. There are about 750 patches that need review and new candidate revisions prepared. There's about 40,000 bugs available to be fixed. You might also look at the output of `apt-cache unmet -i`. Let me know if you run out again. [13:08] hi all === doko_ is now known as doko [13:23] Hi [13:25] I've been using the opensg libs I created for hardy, and I've just noticed that a couple of install dependencies have been missed off, whats the policy for fixing this? [13:25] File a bug, and attach a debdiff I assume [13:27] DaveMorris: Yes [13:28] how do you create a deb diff? [13:34] DaveMorris: debdiff oldversion.dsc newversion.dsc [13:44] who do I need to subscribe to get it fixed? [13:47] <\sh> ScottK: thx [13:48] No problem. [13:49] <\sh> ScottK: two acks are needed, right? [13:49] Yes [13:52] \sh: Approved. [13:56] ScottK once the bugs been fixed, who do I need to subscribe to it? [13:56] ubuntu-universe-sponsors [13:56] thnaks [13:56] * DaveMorris makes notes for next time :) [14:01] hi folks [14:07] ScottK, have you had time to cast an eye on bug 156100 ? [14:07] Launchpad bug 156100 in storm "[hardy] please upgrade storm to version 0.12" [Undecided,Incomplete] https://launchpad.net/bugs/156100 [14:08] ScottK: ah, you did [14:08] mok1: Did you see my comment? [14:08] I will go ahead and do the update, then [14:10] Hi folks; I'm pondering pushing gstreamermm (C++ bindings for GStreamer) which is a very new module to universe; I just pushed it to Debian experimental and thought it might be nice to have it in hardy for backports, third party devs etc. but would like to hear from you [14:10] ScottK: I will assign the bug to me, ok? [14:10] Sure. [14:12] lool: any reason, why it's not yet in unstable, but only in experimental? [14:13] sistpoty|work: Because we avoid publishing unstable API in Debian unstable in pkg-gnome/pkg-gstreamer [14:14] For example we don't publish the gtk or glib dev series in unstable because of this [14:14] lool: If it's not stable enough for unstalbe, it seems unlikely it'd be stable enough for us to drop in late in the release cycle. [14:14] lool: I guess it would be better to get it in hardy+1 then, and backport it to hardy from there, what do you think? [14:15] ScottK: Ok; I was wondering whether it was too late for this cycle too [14:15] lool: We are past Feature Freeze. It's need good justification. I think, without knowing a lot on the topic, it would likely be better to wait. [14:15] I think we tend to merge unstable apps and unstable which are going to stabilize before release, but as I can't tell for gstreamermm it might be best to wait after release [14:16] +libs [14:17] "we tend to merge unstable apps and unstable libs which are going to stabilize" [14:24] <\sh> Hobbsee: thx... [14:24] <\sh> elmargol: uploading [14:25] <\sh> ScottK: btw...the bug was the original merging bug, and I set it to me and confirmed it... === neversfelde_ is now known as neversfelde [14:31] \sh: we use bug states for state of an FFe, confirmed means "granted"... (and bugs being confirmed will hence not show up on the working list of motu-release) [14:36] <\sh> sistpoty|work: yepp...next time I reset the bugstates :) [14:36] :) === kdu1 is now known as kdub [14:37] persia: where do i get this grand list of non-mangled maintainer packages? [14:38] the funny thing is [14:39] i could probably write something up to fix all of those and build source packages for them [14:39] lol === dholbach_ is now known as dholbach [14:39] hello dholbach and zul [14:39] hello [14:40] heya [14:40] :) [14:40] hi dholbach and zul [14:41] hey sistpoty|work [14:41] sistpoty|work: awesome work on the library packaging session [14:42] thanks dholbach... w.o. slangasek it wouldn't have been that good however ;) [14:42] you guys rock, both :) [14:42] Hi [14:43] hi RainCT === asac_ is now known as asac [14:56] I need help to fix pychecker. Is there someone experienced in Python around ( ScottK )? [14:56] stani: just ask [14:57] The problem is that the test suite of pychecker supposes a python2.4 install, which leads to a FTBS. [14:58] stani: I once looked at pychecker [14:58] I am quite familiar with Python, but don't know how I can adapt the code so that all python 2.4 references are transferred to 2.5 [14:59] stani: but I don't know if patching the test output of pychecker with python2.5 is the correct way [14:59] Better would be that pychecker tests against the current python versions and that version numbers are not hard coded in the test suite. [15:01] changing the path in the test suite isn't hard, but I don't know if the other test failure are a regression or not [15:03] geser: I am willing to review and fix all the tests, if someone can explain me how the test suite works. Especially where the expected output is defined. [15:03] the development version of pychecker mentions support for python2.5 in its changelog but last I checked it, it failed in the test suite too [15:05] Some tests may be related to the python version number, other tests might be due to a bug in pychecker. Probably I can fix them, but I just need to know how the information I asked above. [15:05] stani: see test_input/ for the tests and test_expected/ for the results [15:05] heya [15:06] stani: debian/regression.sh is the script doing the tests [15:07] ok, geser, I'll start and will ask questions here if I get stuck. [15:08] geser: is there any information you still remember, from when you looked at pychecker? [15:12] Heya gang [15:13] <\sh> moins bddebian === mgallagh_ is now known as mattva91 [15:14] Hi \sh === mattva91 is now known as mattva01 [15:14] hi bddebian [15:16] Heya sistpoty|work [15:16] Hi bddebian [15:17] stani: not more than I already told you [15:17] bddebian: /me hopes to see ufoai in debian soon... strange enough, I downloaded it on the same day, before the thread started and am currently busy testing it *g* [15:18] Heya geser [15:18] sistpoty|work: Yeah, is it good? :) [15:19] bddebian: well, I *loved* the old ufo - enemy unknown, and ufoai is even better :) [15:27] ScottK: I've uploaded the diff.gz file for python-storm. Should I change bug status to New? [15:27] * mok1 wonders why LP doesn [15:27] ' do this by itself [15:29] sistpoty|work: I'll have to check it out. Though it sounds like there's going to be licensing issues and I HATE those :-( [15:30] bddebian: yeah... license issues in *data* files are a nightmare :( [15:30] geser: ok, fixed one test already ;-) [15:34] gpe-mixer has an unmetdep on gpe-icons >= 0.23 since Hardy ships gpe-icons 0.20-1.1. I was wondering if this could be worth to ask a FFe, since gpe-icons 0.25-1 (in sid) isn't changed so much and I would avoid to add an ubuntu1 delta to gpe-icons. [15:35] ("delta to gpe-mixer", of course) [15:35] Hi all. Where can I find information about debian/control fields supported by Ubuntu? [15:36] warp10: if it's an unmet dependency, sounds sane to me [15:37] sistpoty|work: good. I'll report a sync request soon, at a first look gpe-icons has just some minor changes [15:39] warp10: since it's an icons package, it also doesn't fall under FFe's imho but rather under ArtworkDeadline. ScottK, Hobbsee, TheMuso: agreed? [15:41] sistpoty|work: time for some questions about sensors-applet? [15:42] hellboy195: what's up? [15:43] sistpoty|work: as I see on the homepage currently there is only nvidia support. also ati support planned? [15:44] hellboy195: no idea... actually... maybe asking upstream? [15:45] sistpoty|work: ah thought you know it maybe .. :) nvm. and I should also ask upstream why the indicator for my graphics card is red though it's running at 47°? [15:46] sistpoty|work: if we consider it under ArtowrkDeadline it should be fine syncing it before UIF, shouldn't it? [15:46] hellboy195: yes, please ;) [15:46] warp10: yes [15:46] sistpoty|work: ^^ k, anyway. thx :) [15:46] np [15:54] afflux: ahoi ;) [15:54] morning hellboy195! :) [16:15] sistpoty|work: Since it's not Ubuntu artwork, but more general, I think it needs an FFe, but I don't see a problem with giving it. [16:21] ScottK: ok, makes sense [16:32] does anyone have any docs on syncing packages from Debian? I'd like to add ogre-plugins-cgprogrammanager to Universe to fix Bug #194686/Bug #195065 [16:32] Launchpad bug 194686 in funguloids "Error installing Funguloids: ogre-plugins-cgprogrammanager doesnt exist" [Undecided,New] https://launchpad.net/bugs/194686 [16:32] Launchpad bug 195065 in ubuntu "Please sync ogre-plugins-cgprogrammanager from debian unstable" [Undecided,New] https://launchpad.net/bugs/195065 [16:42] bobbo: You have to do some changes in the "Please sync..." bug and then subscribe ubuntu-universe-sponsors. If a MOTU thinks that the sync is OK he will change the status to confirmed and subscribe ubuntu-archive, and then an archive admin will do the sync [16:43] RainCT: what about the needed FFe? [16:45] bobbo: a sync request should look like this : a) bug title: "Please sync from Debian unstable (

)"; b) explain what the changes in Debian are and if there were any Ubuntu changes why they can be dropped (this isn't applicable in this case); c) include a rational about why it should be synced [16:46] and in this case as geser says you'll also need a Freeze Exception [16:46] jdong: can you comment on bug #195389 please? [16:46] Launchpad bug 195389 in deluge-torrent "Please sync deluge-torrent 0.5.8.4-1 (universe) from Debian unstable (main)" [Undecided,New] https://launchpad.net/bugs/195389 [16:49] RainCT: ok, im on it [16:51] geser: for the freeze exception, should contributors subscribe motu-release before u-u-s, or just subscribe u-u-s and let the sponsor subscribe motu-release? [16:53] RainCT: before to allow acking [16:54] Ok, ive fixed up the description, im guessing i subsribe motu-release now for the FFe? [16:54] * jdong grumbles at deluge's large diffstat [16:54] RainCT: I'd say motu-release and if the FFe got granted u-u-s (if it's still needed, perhaps the FFe counts as an ACK) [16:55] jpatrick, geser: thanks [16:56] bobbo: yes [16:56] jpatrick, RainCT: right thats the title/description updated and motu-release subscribed, anything else I need to do? [16:57] bobbo: wait :) [16:58] heh [17:00] RainCT, geser: well, at least for what I ack with the motu-release hat, I don't consider this necessarily an ACK for sponsoring (as I don't test-build the package) [17:01] sistpoty|work: commented... [17:01] jdong: thanks [17:02] sistpoty|work: though let the record show that's an ok with a grumble attached [17:02] :) [17:02] heh === bobbo is now known as bobbo[away] [17:04] sistpoty|work: doesn't the FFe needs a build log? [17:06] geser: yes, though I'm not too sure why (and looking at a build log and building it myself is still a difference (e.g. buildlog outdated)) [17:13] heya blueyed :P [17:13] Hi emgent :) === bobbo[away] is now known as bobbo [17:20] sistpoty|work: in bug #195065 you said you can only sync source packages, where do i get the source package? [17:20] Launchpad bug 195065 in ubuntu "Please sync ogre-plugins-cgprogrammanager 1.4.6-1 from debian unstable contrib" [Medium,Invalid] https://launchpad.net/bugs/195065 [17:20] sistpoty|work: wait, doesnt matter, found it [17:21] bobbo: apt-cache showsrc in an unstable chroot is what works for me... others than that there is also packages.debian.org/packagename with links [17:23] sistpoty|work: thanks, got the package and added it to the report [17:24] bobbo: also the necessary build log, diffstat and diff of upstream changelog? [17:24] sistpoty|work: not got that yet ;) [17:24] then please add it ;) [17:26] bobbo: see bug #192350 for an example [17:26] Launchpad bug 192350 in semantik "[Feature Freeze Exception] New upstream release" [Undecided,Fix released] https://launchpad.net/bugs/192350 [17:27] jpatrick: thanks :D [17:27] jpatrick, sistpoty|work: is the diffstat etc between the Debian Version and Current Ubuntu version? [17:28] bobbo: between the two releases [17:28] <\sh> DktrKranz: Re: bug #185513 -> the dh_strip in our sbuild chroot needs a fix...adding this to the amd64 part of debian/rules in wine doesn't help actually [17:28] Launchpad bug 185513 in wine "Wine packages overly large" [Undecided,New] https://launchpad.net/bugs/185513 [17:28] jpatrick: the package isnt in Ubuntu though... [17:29] bobbo: then no need I guess [17:29] bobbo: ogre-contrib is in hardy? [17:30] \sh, I tested only in i386 and it worked. I haven't any amd64 boxes to test it out. [17:30] <\sh> DktrKranz: on i386 it works without any problem :) [17:30] <\sh> DktrKranz: it's only on amd64 [17:30] sistpoty|work: it is but not building ogre-plugins-cgprogrammanager [17:31] so, it's just half-a-fix :) [17:31] bobbo: aha... because it obviously failed to build [17:31] * bobbo goes to check logs [17:31] bobbo: which could be related with that old changelog entry: " * Bootstrapping will be done manually." [17:31] \sh, anyway, main issue is segfaults. I tried to look at them, but got no useful details, even with dbgsym [17:32] <\sh> DktrKranz: it looks like that something is terribly wrong...when invoking wine from != a direct wine src tree dir [17:32] <\sh> DktrKranz: there are some messages on wine-devel ml... [17:32] bobbo: nope, looks like s.th. different is making problems: http://launchpadlibrarian.net/11901495/buildlog_ubuntu-hardy-i386.ogre-contrib_1.4.5-1_FAILEDTOBUILD.txt.gz [17:33] * bobbo never gets the easy bugs :/ [17:34] bobbo: there are none [17:34] \sh, so it's not just us... this is good and bad at the same time [17:34] heh :) [17:34] bobbo: start with merging ^^ [17:35] <\sh> DktrKranz: yeah... [17:35] bobbo: there is a nvidia-cg-installer in multiverse but it won't work on the buildds as it wants net access (for downloading) and the buildds have no net access [17:40] * bobbo is now yoyally confused over ogre-contrib bug :/ [17:40] s/yoyally/totally [17:48] bobbo: http://paste.ubuntu-nl.org/57358/ - it's missing a libraby [17:49] bobbo: the last version in Debian has "* Specify Build-Depends and Depends on nvidia-cg-toolkit (>= 2.0)" so it might work now [17:49] jpatrick, geser: so the original plan of merging in the current debian version might work? [17:52] how can i get pbuilder to use a hardy enviroment for building packages? I have changed the DISTRIBUTION= variable in /etc/pbuilderrc but it seems to still build under gutsy =/ [17:52] i am running gutsy btw [17:54] DRebellion: you sure it's not DIST=hardy? :) [17:55] jpatrick, from /etc/pbuilderrc: [17:55] # specifying the distribution forces the distribution on "pbuilder update" [17:55] DISTRIBUTION=hardy [17:55] DRebellion: hrmm, then I have my pbuilder set up differently [17:55] :( [17:56] DRebellion: did you 'reinit' pbuilder after changing the distribution? [17:56] HighN1, erm, no? [17:56] DRebellion: wait a sec... [17:57] DRebellion: sudo pbuilder update --distribution hardy --override-config [17:58] HighN1, i did that, but when i go to build a package it starts to download all of the gutsy packages again! [17:58] DRebellion: hm, how do you bulid your package? [17:58] HighN1, sudo pbuilder build --logfile ~/pbuilder3.log package.dsc [17:59] DRebellion: just a try: sudo pbuilder build --distribution hardy --logfile ~/pbuilder3.log package.dsc [18:00] sistpoty|work, jpatrick: What information do i need to add to the FFe/Sync request? [18:00] HighN1, i'll give that a shot. its just that i shouldn't have to specify on the cmd line every time right? [18:00] bobbo: the ones in the example I gave you [18:01] DRebellion: Right. I can't tell - I did it the other way - sudo pbulider login gives you a full chroot environment with a bash, there you can do the debuild manually. that works for me all the time... [18:01] jpatrick: ive lost the link (embarrased), can you send it again? [18:02] bobbo: https://launchpad.net/bugs/192350 [18:02] Launchpad bug 192350 in semantik "[Feature Freeze Exception] New upstream release" [Undecided,Fix released] [18:02] jpatrick: thank you! [18:03] * sistpoty|work heads home [18:03] cya [18:17] Hrm, still can't get this hardy pbuilder to work properly... could someone talk me through the steps to get a hardy pbuilder enviroment? HighN1? [18:18] jpatrick: that should be everything that needed up for Bug #195065 if you are interested [18:19] Launchpad bug 195065 in ubuntu "Please sync ogre-contrib (1.4.6-1) from debian unstable contrib" [Medium,New] https://launchpad.net/bugs/195065 [18:19] DRebellion: you might like to try pbuilder-dist from ubuntu-dev-tools, but I think that might mean you creating a new chroot. [18:20] james_w, that's not a problem, I only need the default (and only) chroot to be hardy. === HighN1 is now known as HighNo [18:23] DRebellion: hm, I did everything according to this wiki: https://wiki.ubuntu.com/PbuilderHowto [18:23] HighNo, same. [18:25] DRebellion: brb [18:26] DRebellion: pbuilder login --save-after-login [18:27] DRebellion: then edit /etc/apt/sources.list to say hard, then run update; dist-upgrade and log out [18:37] bobbo: see noresetto's comment on the bug :) [18:41] jpatrick: just got the email, checking it out now [18:58] slomo__, thanks for the upload [19:01] hi all [19:01] I'd like to mention THIS backport URGENTLY: https://bugs.launchpad.net/gutsy-backports/+bug/192751 [19:01] Launchpad bug 192751 in gutsy-backports "Backport of network game "pioneers"" [Undecided,New] [19:02] bmhm: what's urgent from it? [19:02] wow, pioneers is urgent, how far we've come [19:02] pochu_: I've been waiting for... weeks =) [19:02] pochu_: can't I provide MY packages? [19:02] I can provide gutsy amd64 and edgy x86 [19:03] no, you can't. packages are built in ubuntu buildds [19:03] I see. Anyway, thanks for the tipp regarding prevu. Wounderful tool. [19:03] Indeed. [19:06] bmhm: Once it's tested, set the bug to Triaged. I don't even look at New backports requests. [19:07] thanks ScottK [19:07] ScottK: What is "Triaged"? [19:08] In general terms it means that the bug has been evaluated and a root cause has been determined (it's ready for a developer to look at fixing) [19:08] We use it in backports to mean it's fully tested and ready to be looked at for approval. [19:09] I didn't see the option "Triaged" [19:09] So i picked confirmed instead [19:10] Confirmed is fine. [19:11] Triaged has some restrictions on it. I look at confirmed too. [19:17] fine === andrea-bs is now known as andrea-bs_ === andrea-bs_ is now known as andrea-bs [19:30] RainCT: ping [19:33] LaserJock: pong [19:33] RainCT: I had a chance to test pbuilder-dist [19:33] LaserJock: evil again? ;) [19:33] well, kidna [19:33] *kinda [19:33] I needed to fix something [19:34] LaserJock: ya? [19:34] RainCT: at the very bottom of the actual pbuilder command, it sets the aptconfdir [19:34] and the quoting is incorrect I believe [19:35] when I tried to do a pbuilder create it actually added a " to the path [19:35] so I just made that line: $( [ $ISDEBIAN != "False" ] || echo "--aptconfdir ${BASE_DIR}/etc/${DISTRIBUTION}/apt.conf/" ) \ [19:35] and it seemed to work fine after that [19:36] LaserJock: can you try if $( [ $ISDEBIAN != "False" ] || echo "--aptconfdir '${BASE_DIR}/etc/${DISTRIBUTION}/apt.conf/'" ) \ works, please? [19:36] LaserJock: I think it wouldn't work if the basedir contains spaces if it has no quotes at all [19:37] hmm [19:51] RainCT: no go, it still puts ' in the path [19:52] * RainCT is pondering if rewriting the damn think in Python might help :P [19:53] RainCT: it can't get worse :) [19:55] geser: quick question. I'm doing bug 195532 is bug 186130 really necessary? [19:55] Launchpad bug 195532 in libnxml "Merge libnxml 0.18.1-4 from Debian(Unstable)" [Undecided,New] https://launchpad.net/bugs/195532 [19:56] Launchpad bug 186130 in libnxml "libnxml needs a versioned build-dependency on cdbs" [Undecided,New] https://launchpad.net/bugs/186130 [19:57] RainCT: honestly, I think it could be much simpler as well [19:57] LaserJock: I'm adding the original script as pbuilder-dist-simple right now ;) [19:57] doing it in Python is an idea though [19:58] hellboy195: if you do the merge please also the second bug [19:58] * ScottK2 cheers simplicity [19:58] it seems like right now though it's too easy to break it [19:59] hellboy195: *fix the second bug [19:59] Indeed. I think I'll have a go at converting it to Python, that should make it much more robust [19:59] geser: so it's necessary though he has a gutsy machine and I suppose on hardy there aren't problems? [20:00] quit [20:01] hellboy195: on hardy it's no problem (else it would FTBFS), only when backporting [20:01] geser: . so I suppose cdbs (>= 0.4.5) [20:03] hellboy195: check the cdbs changelog when it was introduced [20:03] geser: k, thank you :) [20:03] hellboy195: cdbs (>= 0.4.49ubuntu5) [20:03] geser: ah. again thx :) [20:08] he [20:08] llo [20:12] does revu notice when the version number of an not yet approved package changed? [20:14] dsop: how do you mean? [20:15] LOL [20:15] the next version of ubuntu is called Intrepid Ibex ? [20:15] uhh, yeah, where have you been? ;-) [20:16] :P [20:16] hello LaserJock :) [20:16] hiya joejaxx [20:16] how's it going? [20:16] it is going well :D [20:18] hmm LaserJock my upload wsa rejected but i had revu upload rights two month ago [20:19] dsop: did you use the same name & address in the changelog entry? === calc_ is now known as calc [20:19] LaserJock: in the debian changelog, yes [20:20] dsop: you probably need to talk to a REVU admin [20:20] if it was two months ago that you last uploaded I'd think it'd be ok [20:26] ScottK: I uploaded a diff.gz to bug 156100 . [20:26] Launchpad bug 156100 in storm "[hardy] please upgrade storm to version 0.12" [Undecided,Incomplete] https://launchpad.net/bugs/156100 [20:29] dsop: what's your email? [20:29] RainCT: sn_@gmx.net [20:31] RainCT: i got Signer has no upload rights at all to this distribution. [20:33] dsop: are you sure you dput to revu? ;) [20:33] you're in the database [20:33] (if you just dput, it will go to the ubuntu archive) [20:33] argg [20:34] pochu_: okay, man i should read better the wiki nexttime [20:38] dsop: it once happened to me the other way round, I dput'ed to the archive instead of to revu ;) [20:38] pochu_: you're not the only one ;) [20:39] hehe - i guess one is a real motu only if you have done that at least once... [20:41] spawn new motumedia_member() [20:41] jdong: who's him? [20:41] looking for any :) [20:41] heh [20:41] or anyone else who knows what happened to xvidcap [20:41] * pochu_ hides from jdong ;) [20:42] * HighNo is out since he still uses feisty... [20:42] jdong: ah, so you aren't recluiting :) [20:42] pochu_: ha like I have the power to recruit ;-) [20:42] HighNo: that's old!! ;) [20:43] hmm FFe for a FTBFS'ed package since like Feisty. [20:43] shouldn't be hard to grant, right? [20:43] [20:44] pochu_: true, but it is still working. Updating would be nice but only 150MB free atm. Updating would require like 1GB... :-( [20:46] jdong: if it builds with the new version, I don't think so :P [20:46] Local variables: [20:46] mode: debian-changelog [20:46] End: [20:46] WTF is that stuff? [20:46] found it at the end of debian/changelog [20:47] I'm guessing some of marillat's editor cruft? [20:47] jdong: for emacs [20:47] man-di: is it supposed to be at the bottom of debian/changelog or should I snip it out? [20:47] if its there emacs uses that settings for that file [20:48] snip it - that should not be there [20:48] if its not there, it uses its default settings [20:48] hi, ive got a fix available for Bug #195196 but dnot know whether i should forward it to Debian or add the patch to the Ubuntu bug [20:48] Launchpad bug 195196 in graphmonkey "graphmonkey: Upgrade to new upstream release (1.7)" [Wishlist,Confirmed] https://launchpad.net/bugs/195196 [20:48] jdong: there are many many packages with this [20:48] man-di: so it's safe to leave in? [20:48] jdong: yes, doesnt hurt [20:48] man-di: there are? [20:48] HighNo: I have seen this a couple of times in Debian packages [20:49] ok, then I'll leave it in. I was concerned because *cough* vim puts it in syntax error red :) [20:50] jdong: vim is not optimal either [20:50] jdong: I guess vim is not debian compliant here :-) [20:50] lol here we go... :) [20:50] too many false positive errors for debian/control files [20:50] yeah vim does seem to be chicken little with that [20:51] please, is some of the motus willing to review gcutils? [21:02] urgh I made the most retarded upload ever [21:04] Does anybody else find that Thunderbird hangs when gnome-settings-daemon crashes? [21:04] Hi, I want to merge nspluginwrapper 0.9.91.5-2 from Debian. With the -1ubuntu1 version people suffer from crashes like bug 195170 . The problem is that I have no idea if new Debian revision fixes these issues. So merge or wait? [21:04] Launchpad bug 195170 in nspluginwrapper "npviewer.bin crashed with SIGSEGV in g_slice_free_chain_with_offset()" [Undecided,New] https://launchpad.net/bugs/195170 [21:05] Neither. Test. [21:06] Fujitsu: well, personally I don't usw nspluginwrapper. Maybe I find a person who is willing to test :) [21:06] *usw [21:06] *use [21:06] argh [21:12] RainCT: Thanks for sponsoring gcal. Regarding forwarding the changes to Debian, can I send them the Ubuntu debdiff or should I make a Debian version? [21:13] albert23: You're welcome :). You choose, the main thing is that they get the changes. [21:13] RainCT: OK, thank's, I will make a Debian version then [21:14] What does this mean: create all leading components of DEST except the last, then copy SOURCE to DEST [21:14] I don't get it [21:15] bug 175404 [21:15] Launchpad bug 175404 in ubuntu "[needs-packaging] Nemo" [Wishlist,In progress] https://launchpad.net/bugs/175404 [21:15] exactly [21:16] that is the one I am working on [21:22] Flare183: I think you need to describe your question more, I can't quite figure out what you're asking [21:24] LaserJock: ok on the Man page for Install it says that the "-D" syntax means this: create all leading components of DEST except the last, then copy SOURCE to DEST; What does that mean? [21:25] esp. the part about except the last [21:25] correction "except the last" [21:27] I guess it's just "create the directory structure, then copy" [21:30] LaserJock: ok thanks === n3xu|laptop is now known as nexu|laptop === nexu|laptop is now known as Lt`Sheppard === Lt`Sheppard is now known as `deadchip [21:50] whats the best way to take an existing package, add an init script to it and repackage? I've read a bit about dh init but I can't seem to discern howto use it, I've looked at a few packages that have init scripts, but they're pretty big can someone recommend a smaller package to peep out? [21:52] macd: look what's in /etc/init.d [21:52] Im not sure how that helps me use dh init? [21:52] macd: all you need is to put it in debian and call it .init [21:52] if its that simple I feel like a fool [21:53] thx :) [21:53] macd: you just call dh_init in debian/rrules and it takes care of it [21:53] dh_init is in the rules template, iirc [21:56] ok, another question, if a package exists, and the only thing it needs is an init script to add alot of functionality, is it better to just repackage with included script, or package the script seperate? [21:57] I should mention, it has an init script already, but this gives the ability to start one or more instances, so it really expands the existing one === neversfelde_ is now known as neversfelde === neversfelde_ is now known as neversfelde [23:04] slangasek: your sync bugmail always munges the title of the email to be [Bug #] Synced, would it be possible to have it not do that? [23:06] LaserJock: to what mail are you referring? [23:06] when you do syncs [23:06] I don't send mail when I do syncs [23:07] well, I'm assuming the script you use does [23:07] slangasek: but you add a comment to the sync bug which gets then mailed [23:07] take bug #195032 [23:07] Launchpad bug 195032 in starplot "Please sync starplot 0.95.4-3 from Debian(Unstable)" [Wishlist,Fix released] https://launchpad.net/bugs/195032 [23:07] that's the one I got today [23:07] yes, all I'm doing is adding comments to the bug in launchpad. If that generates mails with wrong subjects, I would think that's a LP issue? [23:08]