[00:38] How come vim-full has been unsupported, or rather vim-common-gui, vim-runtime? [00:39] who can I bug about a nifty little program with nice packaging straight from the upstream source? [00:39] https://bugs.launchpad.net/ubuntu/+bug/145007 [00:39] Launchpad bug 145007 in ubuntu "[needs-packaging] anki" [Wishlist,Triaged] [00:41] Laibsch: usually "nice packaging" from upstream is a trap ;-) [00:41] jdong: What do you mean? [00:41] I think the package is indeed nicely packaged [00:41] And I am not upstream [00:42] if that is what you might be hinting at [00:42] Laibsch: no no, I was making a half-serious half-joking remark based on my experience with natively debianized packages [00:42] they're usually a stepping stone, but dont cover everythign that needs to be covered [00:43] I don't get it [00:43] What is the best way to get this accepted? [00:44] By uploading a candidate package to revu, and waiting until after Hardy has been released. We're in feature freeze now, so you'll need a good reason why this software should have an exception. [00:45] what RAOF said, a good first step is to get it onto REVU [00:45] but a major deadline (Feature Freeze) has been missed so the next chance to upload into Ubuntu would be the Hardy+1 release [00:46] ScottK, i've uploaded to mentors. and sent RFS's to debian-mentors@ and debian-multimedia@ [00:46] and now, i'm going to bed :) [00:47] Can somebody please add http://keyserver.ubuntu.com:11371/pks/lookup?search=0xB9D7E198&op=index to the REVU keys? [00:48] Laibsch: Add yourself to the ubuntu-universe-contributors group. [00:48] Fujitsu: Done three minutes ago [00:49] Laibsch: I'm syncing the keyring now. [00:49] Fujitsu: Cool, thanks [00:51] heya people [00:58] anki uploaded to revu === kiko is now known as kiko-zzz [01:03] Laibsch: We are paste feature freeze and so not taking new packages for Hardy. [01:04] ScottK: I am not shooting for hardy [01:04] or any particular release [01:04] Laibsch: OK then. [01:04] Just trying to get things moving [01:04] Fair enough, just didn't want you to end up disappointed. [01:04] Great. [01:05] no worries [01:05] Present rate : 13693 mW [01:05] oh Hardy how much leaner you be :) [01:05] seems like it's down a watt from Gutsy without much change to my config... [01:06] now to consider throttling my CPUs [01:06] how long before I can recover my PWW and log in? [01:06] PW [01:13] Laibsch: The sync just finished. [01:16] No REVU account for oe-devel@rolf.leggewie.biz exists yet. [01:18] Laibsch: probably uploaded too early [01:18] what do you mean too early? [01:18] I'd understate too late, but too early? [01:19] I'll run dput again, I guess [01:20] Laibsch: too early means that the keyring hadn't finished syncing when your upload arrived [01:20] hence it doesn't know who you are. [01:21] Laibsch: I see a rejected anki upload. [01:21] which is fixed by "dput -f revu *changes", right? [01:21] ^^^ done [01:21] Should be. [01:21] So I see. [01:22] rm *.upload [01:23] what is the name of the hardy+1 release? [01:23] I made the package for gutsy now, which is what I run [01:23] hardy+1 hasn't been named. [01:23] OK [01:23] Hence it being referred to as hardy+1 [01:24] Will I be able to get my login in a few minutes or does it usually take a bit longer [01:24] I am about to go to sleep [01:24] Should be happening in about 6 minutes. [01:26] I just learned from my ppa that the latest code does not build [01:27] The package now depends on sqlalchemy [01:27] well you've got plenty of time to figure all that out :) === macd_ is now known as macd [01:37] OK, so here it is http://revu.tauware.de/details.py?package=anki [01:41] Can somebody tell me why http://launchpadlibrarian.net/12093167/buildlog_ubuntu-gutsy-i386.anki_0.9.2-0ubuntu1_FAILEDTOBUILD.txt.gz does not fail due to unsatisfied build dependencies? [01:41] It really should since the version of python-sqlalchemy in gutsy is too old [01:42] the build fails later during compilations and it looks to me like python-sqlalchemy was never installed [01:42] That seems correct to me. Do you actually have a build-depend on python-sqlalchemy? [01:44] RAOF: Indeed, the build is correct [01:44] It looks like the package fails to declare the build dependency [01:44] I was fooled by the runtime dependency declaration [01:44] Heh. [01:49] Laibsch, see that's part of the reason why upstream's packaging isn't always reliable directly [01:49] little gotcha's like that :) [01:49] hi all! [01:49] superm1: Well, it could be worse [01:49] Dear Firefox, please render pages. [01:49] And the version has just been released [01:49] StevenK, nope [01:49] ...and because they ship a debian/ directory you need to repack the tarball, which is always annoying. [01:49] StevenK, especially not on ati hardware [01:49] 0.4.2 built fine straight out of the box [01:50] Laibsch: building fine and meeting Ubuntu/Debian archive inclusion guidelines are often two very different things [01:50] that combined with RAOF's comment about repacking comprise why I said earlier native debianized packages can be a trap [01:51] superm1: This is Gutsy, not Hardy [01:51] jdong: yes, I know about the difference between necessary and sufficient conditions [01:52] I still prefer having the debian dir than having to recreate it all on my own [01:52] I was/am unaware of the need to remove that debian dir from the source [01:57] hi Barry [01:57] Heya gang [01:58] Hi Jordan [02:01] Ah, the cheerful welcoming atmosphere on Debian irc channels just warms my heart :-) [02:02] as always [02:02] bddebian: well now that I am not sniping down potential sponsors as they walk in, you can be more relaxed in here ;-) [02:02] Heh [02:23] Ack, the new muine is building freakin' windows binaries [02:28] how so? [02:28] Dunno, I'm ending up with .dll and .exe files :) [02:29] well, you should get .dll's at least [02:29] bddebian: muine is mono [02:29] not sure about the .exe's [02:29] jelmer: I know but wtf [02:29] bddebian: so you should indeed get dll's and .exe's [02:29] bddebian: it's like that for all mono apps [02:29] Should I ship them? [02:29] yes [02:29] bddebian: it most likely won't work if you don't ;-) [02:29] you can invoke them by running "mono Muine.exe" [02:30] Ugh, fugly [02:30] though I believe muine comes with some wrapper script that does that for you [02:30] Yeah it has a /usr/bin/muine [02:30] jelmer: Actually, you can run them with "Muine.exe", as long as you've got binformat support. [02:30] bddebian: it's a lot like class files for java [02:30] RAOF: ah, right [02:31] Debian CLI policy states that you shouldn't install *.exe to bin, though. [02:31] The .exe isn't in bin [02:31] Then you're laughing. And should probably read the CLI policy anyway ;) [02:32] But bddebian doesn't laugh, he complains. [02:32] * StevenK hides [02:32] heh [02:33] Actually the damn thing is orphaned anyway and I seem to have run out of sponsors recently :-( [02:35] * RAOF throws bddebian at StevenK [02:35] * Fujitsu throws bddebian at NM. [02:36] and bddebian never returns [02:36] such are black holes :/ [02:36] bddebian: is it actually still alive upstream? I thought they stopped doing releases [02:42] Heh [02:42] jelmer: Dunno, there is a 0.8.8 release [02:42] Fujitsu: I'm sitting idly in NM :-) [02:43] My AM hasn't responded in about 3 months... [02:43] I don't have one :) [02:43] I think StevenK warned them about me :) [02:43] bddebian: if you're uploading muine to Debian, you may want to consider #debian-mono and the pkg-cli-apps team [02:43] *joining [02:45] bddebian:, Fujitsu, its things like this that make the desire for becoming a Debian maintainer for meat least, rather minimal. I have more luck working with package maintainer directly, and having them upload any changes etc. === zakame__ is now known as zakame [02:52] TheMuso: I hear ya [02:55] TheMuso: virtkey FFe confirmed [02:57] ScottK: Shit did isubscrbe the wrong team? Let me check. [02:57] ugh tyis keybord has to go [02:57] hehe [02:59] Is that one in Main? I didn't even look. [03:00] ScottK: Yes it is. [03:00] No I subscribed the right team. [03:02] heh, ScottK2's been promoted? [03:03] Then why the heck did I get bugmail... [03:03] * ScottK2 looks [03:03] pythoneers probably. [03:04] Yep. [03:04] Urgh. Sorry. [03:05] ScottK: heh thats ok. Thats why its good to sort bugmail for different teams into folders. :p [03:05] Or at least to actually read the bugmail all the way to the end. [03:05] Unconfirmed now. [03:06] sometimes I wish they'd put a one line at the *top* of the bugmail [03:07] LaserJock: That wouldn't hurt actually. [03:07] They already have binary package hint [03:07] I love the ones that just say I got it because ubuntu-server or some team is a direct subscriber of the bug, but say nothing about which package it involves. [03:07] TheMuso: Not always. [03:07] One could easily put the component in brackets or something similar after it. [03:08] ScottK2: heh fun [03:08] yeah, I get a lot that don't have much of anything, just flipping Importance or Status or maybe a new comment [03:09] My favorite LP mail I got recently was one letting me know that some team couldn't join LP mailing list beta testers because bugsquad is signed up for that team and I'm stuck as an indirect member of that due to MOTU/core-dev. [03:10] Nice. [03:15] hello === lamalex is now known as lamalex_1 === lamalex_1 is now known as lamalex [03:57] is there a masters of the multiverse/parters repos anywhere [03:57] or should i just submit my request/idea here? [03:58] ethana2: MOTU covers multiverse as well, but Canonical controls partner. [03:58] Canonical needs to parter with google to deliver Google earth, picasa, and sketchup.. [03:58] via apt [03:58] i would expect them to be considering that already [03:59] but in case they weren't, there's the idea [03:59] I don't believe any of the Canonical partner people are in here. [03:59] oh [03:59] could you direct me to the right place to submit this idea? [03:59] I have no idea. [04:00] ah [04:00] is there any problem with ubuntuwire? [04:00] i can't access it [04:00] Most of the developers you'll find here are interested in Free Software. [04:00] of course [04:00] nxvl: Yes. It's down. Dunno why or when it will come back. [04:00] nxvl: The primary server is currently down, and has been since the local root exploit. [04:01] root exploit? [04:01] Why it's not up yet I don't know, but imbrandon hasn't been around. [04:01] mmm [04:01] ohh [04:01] that thing with elevated local priviledges [04:01] That one. [04:01] is ubuntuwire a canonical server or a community one/ [04:01] ? [04:01] i remember everyone making a big deal about that [04:01] We do have another new server, but we don't have control over DNS or anything at this point. [04:01] nxvl: Communicty. Canonical has nothing to do with Ubuntuwire. [04:01] he isn't on the jabber also [04:02] mm so i can't ping Ng for that :S [04:02] ok, i will try to find imbrandon [04:02] thanks! [04:02] nxvl: UbuntuWire people are in #ubuntuwire. [04:02] Fujitsu: I wonder if we should just move forward until he turns up. I can server DNS from reliable commercial hosting for ubuntuwire.kitterman.com and whatever subdomains are needed. [04:03] ScottK2: We can't redelegate. [04:03] He holds the keys to the kingdom. [04:03] Oh. [04:03] I see. [04:03] Yeah as a place holder. [04:03] So at least we can move forward. [04:03] We're planning on making stratos master DNS eventually, rather than having a mess like we do now. [04:04] we ran into very similar issues with mythbuntu.org when he was MIA. only we were down for multiple weeks [04:05] I should have console access to orko, but the host is rejecting SSH for some unknown reason... === zakame__ is now known as zakame [04:50] Is it possible to do simple maths in a shell script to be run by dash? If so, whats the syntax? (I've forgotten.) [04:51] echo $((1 + 2)) [04:51] TheMuso: ^ [04:51] StevenK: I knew it was something like that, thanks. [05:16] lol [05:16] firefox3 blocks you from going to sites that have self signed certs? [05:17] You get to scramble through the preferences to hunt down the button to make an exception, yes. [05:18] you can do that now from the warning [05:18] that stinks [05:18] with beta3 [05:18] i rather have the dialog [05:19] pochu: Yeah. Do we have b3 in Universe yet? [05:19] RAOF: in main rather :) [05:19] Oh, of course. [05:21] how do I find the packages that all depend on a given package? [05:22] apt-cache rdepends [05:23] k thx [05:33] grrr, I don't understand why ldconfig finds a lib by ldd doesn't [05:34] s/by/but/ [05:35] It isn't in a standard location? [05:36] it's in /usr/lib/ [05:36] It's the wrong arch? [05:36] well, that could be [05:36] I'm running amd64 [05:37] I don't know how exactly that works though [05:37] Everyone loves dpkg multiarch! [05:37] Basically, 32bit stuff requires an entirely separate library stack. [05:38] (As does 64bit stuff, but that's kinda the native stack). [05:38] Even down to the C library. Fun, huh? [05:38] Totally. [05:38] ok, soo [05:38] I have a 32-bit app [05:38] so what do I need to do? [05:39] * LaserJock is starting to curse his bad eyesight in downloading the amd64 .iso [05:39] ia32-libs has a huge stack of 32bit libraries. If you've already got that installed, and your app wants something more... [05:39] You can file a bug against ia32-libs requesting that it gets added, and in the meantime you can download the i386 deb containing $LIB_OF_CHOICE, extract it, and put the .so into /usr/lib32. [05:39] it want's libmotif3 which is in Multiverse [05:40] ab [05:40] *ah [05:40] There's a script somewhere on the forums which automates this process. [05:41] *cough* 64-bit sucks *cough* [05:41] A proper multiarch dpkg would be fun. [05:42] LaserJock: Only really for 3rd party binaries. But that's a fairly large 'only'. [05:42] * RAOF goes to do the washing up. [05:42] exactly === boomer` is now known as boomer === lando_ is now known as lando [06:44] darn. i'll actually have to put in my own uvfe now. [06:46] heh [06:47] kinda sucks when you gotta play by the rules ;-) [06:48] yeah, i know. [06:49] * Hobbsee wonders what jockey-common is [06:49] Jockey is the new name for restricted-manager [06:49] oh [06:50] well, it doesn't upgrade well, that's for sure [06:50] Due to python-central? [06:50] yes [06:50] I think it's more python-central's fault [06:58] Good morning [06:58] hi; is there a way to have dput upload my .dsc and .diff.gz, but not the orig tarball? [06:59] tsmithe: try debuild -S -sd [06:59] tsmithe: if you don't do -sa it shouldn't [06:59] right, thanks. what do "-sa" and "-sd" do? "all" and "diff" or something? [07:01] tsmithe: -sa includes the original source, -sd doesn't. [07:01] tsmithe: man dpkg-buildpackage [07:01] tsmithe: man dpkg-buildpackage [07:02] ah, thanks :) [07:16] well, if anyone has time to upload http://revu.tauware.de/details.py?package=fluid-soundfont in accordance with bug 193496, i'd more more than grateful. presumably, as it's been through the two-advocation stage of revu previously, that shouldn't be necessary, and it's thus good to go. [07:16] Launchpad bug 193496 in ubuntu "Feature Freeze Exception for fluid-soundfont" [Undecided,Confirmed] https://launchpad.net/bugs/193496 [07:17] persia, ^ (since you did the previous upload) [07:39] If anybody's bored and looking for something to check out, I have a FFe request sitting at 193605 that needs someone to test the build. [07:47] How do folks write manpages? The only editor I can see is ManEdit, which depends on an outdated version of GTK. [07:49] good morning [07:49] db-keen: usually, by writing them in a different language (docbook, docbook xml, perldoc) and generating the manpages [07:51] morning dholbach [07:52] hey warp10 [07:54] good morning [08:05] When will qa.ubuntuwire.com be available again? [08:08] slytherin: No ETA at this stage. Our single point of failure has failed. [08:09] :-( [08:11] slytherin: what service from qa.uw.com are you missing? [08:11] geser: Usually I check FTBFS page [08:12] slytherin: let my rerun it locally and scp the output somewhere else [08:12] :-) [08:17] keescook: Are you likely to be around for the SRU/Security UDW session? [08:20] slytherin: http://members.ping.de/~mb/hardy_build_status.html [08:22] geser: thanks [08:46] Can anyone please test VCD plugin in gstreamer and report status. I just want to make sure that I am not the only one facing problem before filing bug upstream. === doko_ is now known as doko [08:55] slytherin: what happens? i don't have a vcd but maybe i can still help [08:57] slomo_: It simply doesn't play. Totem doesn't play because the support is disabled in totem I believe. I also tried gst-launch, didn't work either. [08:57] slytherin: this is in hardy? output of gst-launch-0.10 playbin uri=vcd://whatever_needs_to_be_there? [08:58] slomo_: Yes in hardy. I can not provide output right now. But I think I discussed this few days ago in #gstreamer. May be I have outout lurking around somewhere in pastebin. Let me find it [08:59] slytherin: i have a feeling that the vcd plugin is broken, let me take a closer look at the source ;) [09:01] slomo_: This is only partial output of - gst-launch-0.10 -v vcdsrc device=/dev/cdrom1 ! typefind ! fakesink - as suggested by __tim on #gstreamer. Do you want me to post the conversation somewhere? [09:01] slytherin: yes, that would be nice [09:04] hi all [09:04] anyone got packages for mspgcc ? [09:04] slomo_: http://pastebin.com/m5c536c1c As __tim suggested looks like cdxastrip is not yet ported. [09:06] slytherin: ok, file a upstream bug so it doesn't get lost, i'll ask tim for the status later when he's online [09:09] slomo_: But he is not a gstreamer developer right? AFAIK, he is thoggen developer who seems to have lot of insight in gstreamer code [09:10] slangasek: he's one of the core gstreamer developers [09:10] slangasek: sorry [09:10] slytherin: ^--- this was for you :) [09:11] slomo_: I didn't know that. :-) [09:12] slytherin: np :) [09:12] slomo_: By the way, cdxastrip is not even installed on hardy setup. Di I need to first make sure that it is not a installation problem? [09:13] slytherin: it's simply not ported to 0.10 yet, thus non-existing [09:13] slomo_: ah,ok then I will fiel a bug [09:13] slytherin: hm, it might be the same as cdxaparse though... not sure [09:13] I wonder how much effort is involved in porting [09:13] not much i guess [09:15] LucidFox: thanks for closing that bug === LucidFox is now known as LucidFox_away === \sh_away is now known as \sh [09:24] persia: I see that netbeans is in main, is that intended? [09:28] !mir [09:28] mir is Main Inclusion Report - see https://wiki.ubuntu.com/MainInclusionProcess for more information. [09:28] slytherin: That is what we call a Launchpad lack of feature. [09:29] :-) [09:30] slytherin: pitti just fixed that. [09:33] Ia m planning to file MIR for obex-data-server. How do I find if any binary has suid or sgid bit set? [10:02] superm1: ping? [10:09] slomo_: I'd say he's in bed now. [10:26] slytherin: Fujitsu: Thanks :) === wolfger_ is now known as wolfger [11:43] superm1: http://bugzilla.gnome.org/show_bug.cgi?id=516672 <--- so maybe we should support gmyth-upnp and package it? :) [11:43] Gnome bug 516672 in Plugins "gmyth upnp" [Enhancement,Unconfirmed] === Adri2000_ is now known as Adri2000 [12:28] ScottK: do i need to resend my mail as "Sarah Hobbs" for you to see it? [12:28] apparently i agreed - but my mail says that i didn't on some of the points. [12:28] Hobbsee: Try "Long Pointy Stick of DOOM" [12:29] oh. is that the idea. [12:39] heya people === \sh is now known as \sh_away [12:59] Hey [13:04] so, ${source:Version} and ${binary:Version} don't exist in Dapper... and I've already forgotten what those used to be.. was is source-Version? [13:04] Hobbsee: I took your mail as, it's not ideal, but I'm on vacation so whatever. Sorry if that was wrong. I think it should be discussed/decided for real at the next MOTU meeting. === Igorot_ is now known as Igorot [13:05] * ScottK will be AFK most of the day, so I'm not ignoring anyone. [13:05] ScottK: ...right. i agree with the idea - but i think that filing a bug for a bugfix only release isn't overly helpful [13:06] if it was an "i'm on vacation, so i really don't care", i wouldn't have replied at all [13:07] mtaylor: that's about right IIRC. There's a lintian warning for the old form. [13:08] broonie: yeah... I changed it to the new form because of that warning... but now I can't remember the old and google search for source:Version is not helpful :) [13:09] broonie: I guess it's time to go slog through old commit messages... [13:11] Hobbsee: around? [13:11] hellboy195: yes [13:11] Hobbsee: you are archive-admin right? [13:12] for some of it, yes [13:13] Hobbsee: would you mind queue 'ebug-http' again? It FTBFS for several times because of a broken libcatalyst-perl package (which is fixed now) [13:14] hellboy195: done [13:14] Hobbsee: thank you :) [13:14] hellboy195: give-backs are handled by build admins, but Hobbsee is also one [13:14] hellboy195: btw, you needed a buildd admin for that [13:14] you're welcome [13:14] ah true, sry ^^ [13:15] geser: and if you have time you could help me with another problem ;) [13:16] which one? [13:16] geser: I'm working on LP:#193649 but the problem is LP:#163603. I thought latest debian revision fixed it but no :( [13:17] ubotu: ?? show the links ! [13:17] bug 193649 bug 163603 [13:17] Launchpad bug 193649 in axiom "Merge axiom 20050901-10 from Debian(Unstable)" [Undecided,New] https://launchpad.net/bugs/193649 [13:17] Launchpad bug 163603 in axiom "FTBFS: axiom_20050901-9ubuntu1 on hardy/i386" [Medium,Confirmed] https://launchpad.net/bugs/163603 [13:17] soren: ah, thx :) [13:18] hellboy195: axiom can build now? [13:18] soren: no :( that's the problem [13:18] hellboy195: I've asked the Debian maintainer for help, but he hasn't responded. [13:18] (months ago) [13:18] https://edge.launchpad.net/ubuntu/hardy/+source/axiom/+builds show successfull builds [13:18] argh [13:19] geser: strange, but my pbuilder fails ... [13:19] geser: Yes, but that was back in feisty. [13:19] it's possible that it would fail now too if somebody tries to rebuild it [13:19] geser: it ftbfs now. [13:19] ah [13:20] I thought * Bug fix: "i386 build of axiom is missing all shlibs dependencies", from latest debian fixes it but no ... :( [13:23] hellboy195: boy can you reproduce the FTBFS with the last version from Debian? (in a pbuilder or similar) [13:24] geser: yep, I already reproduced it ;) [13:25] then try to find out why it the file is missing [13:26] ähm ok, I doub it that I'll find it but I'll try === \sh_away is now known as \sh [13:27] hellboy195: I usually login into the pbuilder and build it there to the point where it fails [13:28] geser: docs around for that? [13:28] and try then digging in Makefile to find the place where it should get build [13:29] mtaylor: If you look through the lintian warnign text... [13:30] hellboy195: I don't know of any, but it isn't difficult: pbuilder login, copy the source package from outside (or apt-get source it), unpack it, start building with dpkg-buildpackage -b (it will complain about missing build-depends so install them) [13:30] geser: k, thx. Will try it [13:31] if you add -nc to dpkg-buildpackage -b it will skip clean so it doesn't start from fresh every time you try to get further (saves time, especially here) [13:33] if you exit pbuilder all your changes are gone, so don't forget to save your changes outside [13:33] geser: well, it's the first time I'm doing that so I *will* make mistakes but nvm. I'm here to learn [13:40] tjaalton: does reverting intel to XAA affect video playback with compiz (IIRC xv didn't work when I tried that as an xorg.conf option some time ago in Hardy) [13:41] jdong: 965 uses EXA, so it shouldn't be a problem [13:41] jdong: could be that we'll end up using EXA for !965 too [13:42] tjaalton: well I have a 950 and I distintly remember setting XAA cause Xv+compiz to bork [13:42] currently I'm using EXA + greedy migration [13:42] which has worked well for me [13:42] anyway, I'll be able to tell you for sure once I apply the updates :) [13:43] jdong: heh, ok.. it's just a matter of dropping one patch to use EXA again [13:45] hellboy195: Thanks for taking on wxwidgets2.6. Good luck! [13:45] persia: I'll need it ^^ but if I have problem I can ping you? [13:45] *problems [13:46] hellboy195: hmm, axiom failed for me on amd64 because of an other reason as in the bug :( [13:46] hellboy195: There are a few of us who have looked into that package in the past: given our relative timezones, you'll likely do better to ask generally, but I'll answer if I'm around. [13:47] persia: k, thx [13:47] tjaalton: confirmed, XAA + Xv + Compiz is no good [13:47]