[00:24] <MTecknology> I have an app that depends on the 'cal' command. is that in coreutils?
[00:24] <stgraber> stgraber@castiana:~$ dpkg -S /usr/bin/cal
[00:24] <stgraber> bsdmainutils: /usr/bin/cal
[00:25] <MTecknology> oh...
[00:25] <MTecknology> thanks
[00:25] <stgraber> np
[00:45] <MTecknology> yay.. only 16hr remaining on my build...
[00:45] <MTecknology> Would any of you be willing to check out the quality of my package?
[00:46] <lifeless> is it a nwe package or a patch ?
[00:46] <MTecknology> https://edge.launchpad.net/~mtecknology/+archive/testapps/+sourcepub/1007081/+listing-archive-extra
[00:46] <MTecknology> lifeless: new
[00:46] <kb9vqf> So, does MOTU take care of libaprutil?
[00:47] <lifeless> that will be ubuntu server/foundations
[00:47] <kb9vqf> Thanks
[00:51] <MTecknology> lifeless: my guess is that I don't really need to have bsdadminutils as a requirement for lal-cal, but without cal (provided by the package) the calendar is pretty garbled.
[00:52] <lifeless> MTecknology: so there are three levels of requirements
[00:52] <lifeless> must, should, could
[00:52] <lifeless> decide which this is
[00:52] <lifeless> then do one of
[00:52] <lifeless> depends, recommends, suggests
[00:52] <lifeless> to match
[00:52] <MTecknology> lifeless: lal-cal won't function without 'cal' but it also won't break and die (which maybe it should)
[00:53] <lifeless> I don't understand the difference
[00:53] <MTecknology> lifeless: It uses cal to build the calendar displayed
[00:53] <lifeless> yes
[00:54] <lifeless> but I don't understand the difference between 'won't function' and 'won't break'
[00:54] <lifeless> not functioning seems to be breaking, to me.
[00:54] <MTecknology> it'll display the clock, the calendar will drop down, but the calendar output will be very garbled because there's no valid input - it won't crash though and you can still use it for time
[00:55] <lifeless> does it look ok
[00:55] <lifeless> or does it look shit
[00:55] <MTecknology> shit
[00:55] <lifeless> if it looks shit, its not working right
[00:55] <MTecknology> should probably just have bsdadminutils as depends..
[00:55] <lifeless> precisely
[00:55] <MTecknology> which it already is :S
[00:56] <MTecknology> :D*
[00:59] <lifeless> MTecknology: remember that the purpose of package is to make the software work right
[00:59] <lifeless> weak dependencies are only useful so far as they preserve that goal
[00:59] <MTecknology> alrighty
[01:00] <MTecknology> lifeless: you see anything I did wrong?
[01:01] <lifeless> I haven't looked
[01:01] <MTecknology> oh
[01:01] <lifeless> for new packages, please use REVU
[01:01] <lifeless> it really helps
[01:03] <MTecknology> lifeless: how should I submit that? (2.0-0ubuntu1) lucid
[01:04] <lifeless> sure
[01:06] <MTecknology> lol...
[01:07] <MTecknology> lintian is complaining about not being able to check my standards version
[01:14] <MTecknology> What should a copyright look like on a source code file?
[01:30] <MTecknology> revu doesn't want to load for me..
[01:33] <ajmitch> MTecknology: loads for me
[01:33] <MTecknology> ajmitch: oh..
[01:34] <MTecknology> http://downforeveryoneorjustme.com/revu.ubuntuwire.com/ <-- this is telling me it's down too :S
[01:36] <ajmitch> it took a few seconds for me, so I'll see if there are some issues with it
[01:37] <ajmitch> try now?
[01:37] <MTecknology> woah errors :P
[01:37] <MTecknology> ya, much faster
[01:37] <MTecknology> ajmitch: thanks :)
[01:38] <lifeless> persia: how does one query 'who can upload X'
[01:38]  * ajmitch doesn't have time to check why, but too many DB connections open, I think
[01:42] <ajmitch> lifeless: I think edit_acl.py from http://bazaar.launchpad.net/~ubuntu-archive/ubuntu-archive-tools/trunk/annotate/head%3A/edit_acl.py can be used to list uploaders
[01:42] <ajmitch> I can't recall if it will list the uploaders for a particular package
[04:29] <AnAnt> Hello, can someone review http://revu.ubuntuwire.com/details.py?upid=8017 (it's a plymouth theme)
[05:12] <IntuitiveNipple> Am I correct in thinking that subscribing ubuntu-universe-sponsors is all I need to do to get attention for a FFe bug-fix debdiff for a universe package which was auto-imported from Debian?
[05:14] <AnAnt> IntuitiveNipple: https://wiki.ubuntu.com/FreezeExceptionProcess
[05:14] <AnAnt> IntuitiveNipple: for FFe, ubuntu-release should be subscribed
[05:15] <IntuitiveNipple> I did read that but its not entirely clear
[05:15] <IntuitiveNipple> it only talks about ubuntu-release in terms of the final week of development
[05:24] <crimsun> IntuitiveNipple: ubuntu-sponsors
[05:24] <crimsun> IntuitiveNipple: but, you could probably skip that step right now since you could just pass me the bug report #
[05:24] <IntuitiveNipple> ahhh, I subscribed ubuntu-universe-sponsors!
[05:25] <IntuitiveNipple> bug #546154
[05:28] <crimsun>   Uploading dmg2img_1.6.1-1ubuntu1_source.changes: done.
[05:28] <crimsun> Successfully uploaded packages.
[05:28] <crimsun> thanks for your contribution!
[05:29] <IntuitiveNipple> Many thanks! So, if I fix a universe package in the future, subscribe ubuntu-sponsors, not ubuntu-universe-sponsors?
[05:29] <crimsun> also, ubuntu-release isn't necessary at this time
[05:29] <crimsun> correct
[05:30] <IntuitiveNipple> ahh... it could be clearer on the Wiki ... I was worried about spamming the wrong teams
[06:20] <AnAnt> crimsun: how about LP #543679 ?
[06:21] <AnAnt> oh, I subscribed ubuntu-sponsors to it already
[06:22] <crimsun> AnAnt: sorry, I'm chasing a pulse bug ATM
[06:23] <AnAnt> ok
[06:59] <crimsun> ugh, that is one nasty bug.
[06:59] <crimsun> too bad there isn't an easy way to handle the surround/lfe/rear/center mess
[07:50] <Adri2000> jdstrand: you synced the blobby package some time ago (bug #537015), but it's been rejected from NEW :/ and I don't know why nor who did tha
[07:50] <Adri2000> +t
[08:01] <siretart> bdrung: just curious, is there going to be a eclipse-cdt for lucid?
[08:01] <siretart> or for the matter, for squeeze?
[08:19] <dholbach> good morning
[08:21] <ajmitch> morning dholbach
[08:52] <Daviey> A multiverse build failed, and i belive it was a hiccup with the buildd rather than an issue with package.  If i wanted a no change rebuild done, is it an AA or LP folk that i need to ask?
[08:58] <dholbach> Daviey: any Ubuntu developer
[08:58] <dholbach> Daviey: which package is it?
[08:58] <dholbach> or link to the failed build
[08:58] <dholbach> did you try to rebuild it locally? did that work?
[09:00] <Daviey> dholbach: It failed satisfying depends on amd64 only, but the depends in the archive are identical to i386.
[09:30] <bdrung> siretart: maybe
[09:44] <kecsap>  hi all! I would like to push some new softwares to the multiverse repository. Is it the right process is the reviewing through REVU?
[10:20] <siretart> kecsap: the right process is to find a sponsor. many reviewers find REVU helpful for reviewing package. What kind of new package do you propose for multiverse?
[10:23] <kecsap> siretart: I packaged a programming sdk for Sony AIBO robot dogs (contains: cross-compiler gcc/mips, newlib and binutils/Sony Open-R binaries/Urbi SDK for AIBO). https://bugs.launchpad.net/aiboplus/+bug/546402
[10:25] <siretart> kecsap: oh, that sounds like pretty complex pieces of software packages
[10:26] <siretart> kecsap: maybe a PPA is better suited for this?
[10:27] <kecsap> siretart: https://launchpad.net/~csaba-kertesz/+archive/aiboplus :)
[10:28] <kecsap> siretart: No, it is not that complex, because the Sony Open-R and the Urbi SDK is in binary form. Only the gcc/binutils/newlib is cross-compiled during package generation.
[10:30] <kecsap> siretart: with some small packaging/cmake/script knowledge, it is easy to understand.
[11:19] <directhex> StevenK, what're the chances of using your awesome archive-admin-day powers to allow the release-team-approved package with banshee ubuntu one music store support through NEW?
[11:20] <directhex> kecsap, does the license allow redistribution of those binaries?
[11:23] <kecsap> directhex, gcc/binutils/newlib is obviously ok, Open-R is freeware as stated in the source package, for Urbi parts, I contacted the Gostai who owns the software and their response was: "We have no problem
[11:23] <kecsap> for you to distribute them through a debian/ubuntu package as long as you
[11:23] <kecsap> provide the correct gostai and sony copyright infos."
[11:24] <directhex> morning jeff
[11:24] <jdub> hey :-)
[11:25] <jdub> YokoZar: given taht you last touched ia32-libs, can i bug you about #534197 ? :-)
[11:25] <jdub> oddly enough, directhex just reminded me about it (on twitter)
[11:25] <directhex> oh, hang on... you're suggesting ti dlopens the 32-bit lib if it's there?
[11:25] <jdub> directhex: yes
[11:26] <directhex> let me boot my laptop & test
[11:26] <jdub> directhex: now, that *might* just be AIR 2, but i'm pretty sure it's the case for the latest 1.5s as well
[11:28] <jdub> (btw, AIR2 appears to run significantly better on linux)
[11:28] <directhex> is it stable?
[11:29] <jdub> it is robust enough for tweetdeck at least
[11:29] <directhex> i don't think it works in 1.5.x btw
[11:29] <jdub> i do not know about stable (not an AIR developer)
[11:29] <directhex> i'm getting g-k-d issues, as i expected
[11:30] <jdub> how did you add the gk libs?
[11:30] <directhex> getlibs. i definitely have a gnome-keyring.so.0 in lib32
[11:30] <jdub> you should have...
[11:30] <jdub> jdub@sliver:~$ find /usr/lib32/ | grep keyring
[11:30] <jdub> /usr/lib32/libgnome-keyring.so.0
[11:30] <jdub> /usr/lib32/libgnome-keyring.so.0.1.1
[11:30] <directhex> yeah
[11:31] <directhex> installing the beta
[11:32] <wgrant> For anyone that's interested: Karmic PPAs now accept the 3.0 formats.
[11:32] <directhex> wgrant, really? awesome!
[11:33] <directhex> jdub, nope, still no worky for me. How odd.
[11:34] <jdub> directhex: i did a lot of cleaning between fail and success...
[11:35] <jdub> directhex: perhaps prior air config/install makes it continue to use the socket interface?
[11:35] <directhex> yes, wiping ~/.appdata seems to have done the trick
[11:35] <jdub> aha
[11:35] <jdub> wonder if that'll help with 1.5 too
[11:36] <directhex> i can try a downgrade
[11:38] <directhex> hm, yes. grr
[12:09] <nigelb> when I'm already an ubuntu member, does applying to contributing developer really required?
[12:16] <jdstrand> Adri2000: re blobby> that was a mistake which I have corrected
[12:47] <geser> nigelb: no, as it would give you only an additional badge on your LP page (contributing developer is for granting membership through development contributions)
[12:48] <nigelb> ah, so really, I can apply for MOTU when ready :)
[12:50] <geser> sure
[12:51] <nigelb> :)
[12:51] <geser> you can even apply for MOTU without membership, contributing developer is for those who want a little recognition for their contributions on the path to MOTU
[12:52] <nigelb> yes, the ones that can't apply to regional boards since all contributions are tech
[12:52] <hyperair> all contributions are international ;-)
[12:53] <nigelb> not about international, mostly regional boards tend to refer to dmb if all that a person has done is dev
[12:53] <hyperair> yeah i figured as much
[12:54] <nigelb> now to figure out why vlc build fails
[12:54] <hyperair> use the source ;-)
[12:55] <nigelb> I forgot to update chroot earlier, trying after update now
[13:06] <yofel> hi, I'm not sure if I'm right here but, would it be better to fix bug 546220 in lucid by merging the package from unstable with an FFE, or should we just patch the lucid package at this point?
[13:10] <geser> yofel: as this sounds like a new feature, you need a FFE in either case. once you got a FFe you can merge it.
[13:11] <yofel> makes sense, thx geser
[13:21] <hyperair> Laney: you're running lucid, right? could you check if hal ships an initscript? /etc/init/hal.conf for example
[13:52] <Laney> hyperair: i don't see anything
[13:53] <hyperair> Laney: i thought as much. this could be quite problematic.
[13:53] <Laney> why what's up
[13:53] <hyperair> Laney: banshee needs teh hal for any Dap detection
[13:53] <Laney> i thought it was ported to uwhatever
[13:53] <hyperair> wishful thinking >_>
[13:54] <hyperair> upstream doesn't like uwhatever, or is just procrastinating
[13:54] <Laney> :(
[13:57]  * hyperair sighs
[13:57] <hyperair> they can be really nice upstreams, and really difficult ones at times
[13:58] <geser> doesn't dbus start hal?
[14:15] <hyperair> geser: it's supposed to, but doesn't, apparently.
[14:36] <sebner> hyperair: hal is still in a useable state in the archive? lucky you, bad upstream!
[14:36] <hyperair> sebner: well help me convince upstream
[14:37] <sebner> hyperair: I don't want to start a flamewar :P
[14:37] <hyperair> sebner: if it gets things done, i don't mind =p
[14:37] <sebner> heh
[14:37] <sebner> hyperair: what are their reasons to wait with it?
[14:38] <hyperair> sebner: "because jcastro told us hal won't be completely removed until lucid+1, so we have time."
[14:38] <hyperair> sebner: or something like that
[14:38] <ScottK> KDE still needs HAL, so it's not going anywhere.
[14:38] <hyperair> hmm i see
[14:40] <jcastro> disclaimer: that quote of mine is from like 6 months ago
[14:41] <hyperair> jcastro: i'm not blaming you. i'm just quoting upstream. every time i try to push them towards dropping hal, that's what they tell me.
[14:42] <jcastro> I thought they had a hal-less branch somehwere that someone was working on?
[14:42] <jcastro> hyperair: I was under the impression that their hal migration would be done after 1.6
[14:43] <hyperair> jcastro: really? i hadn't heard anything about their uwhatever migration since the last short-term fix they issued.
[14:43] <jcastro> we should ask then
[14:44] <sebner> ScottK: pfff, KDE :P
[14:44] <hyperair> it seems lamalex is working on it
[14:44] <hyperair> i've poked him so let's see how that one is progressing
[14:44] <sebner> hyperair: doesn't fedora and others drop(ped) hal too? Only excusing for ubuntu sucks
[14:45] <hyperair> sebner: well. i have no idea.
[14:49] <jcastro> I suspect apps using hal will be around for a while
[14:49] <jcastro> but hey since we're talking about banshee, if someone wants to ack banshee-community-extensions in NEW so we can get the music store in banshee for lucid that would be swell
[14:56] <IntuitiveNipple> Could someone sponsor a -dbgsym fix I've added to the changes to dmg2img that dchen sponsored earlier today? bug #546108
[14:58] <hyperair> jcastro: actually i need to upload a second bce (one extra new package)
[14:58] <hyperair> it's waiting in debian's NEW queue as well
[14:58] <hyperair> i forgot to add that package previously
[14:59] <hyperair> directhex: should i upload -2ubuntu1 now or wait for debian to accept -2?
[15:01] <Laney> poke in #-ftp if you want to make it happen faster
[15:01] <directhex> hyperair, hm... 1ubuntu2 IMHO. shouldn't upload 2ubuntu1 until 2 is in, but let's not wait
[15:02] <hyperair> directhex: okay.
[15:03] <Laney> well
[15:03] <Laney> you can do -2~ubuntu1 if you want
[15:03] <Laney> I've done uploads like that before
[15:04] <directhex> Laney, well, we can't sync b-c-e as we have ubuntu delta
[15:04] <Laney> yeah I know, it just makes it clear where the changes are coming from
[15:06] <hyperair> nevermind, it will be for a very short time.
[15:07] <hyperair> 31st march, 1.6.0 appears
[15:07] <hyperair> this is temporary until then, to let us clear the NEW queue (and hopefully no new extensions have been added)
[15:07] <Laney> of both?
[15:07] <hyperair> Laney: yes.
[15:07] <Laney> sexy!
[15:08] <Laney> I might try and hack that f-spot proxy code into banshee
[15:08] <hyperair> cool beans
[15:08] <hyperair> please try getting it upstream.
[15:09] <hyperair> within the time frame
[15:09] <Laney> er
[15:09] <Laney> i didn't even consider distro patching
[15:09] <Laney> oh, dunno about that
[15:09] <hyperair> oh heh =p
[15:09] <hyperair> if you can't get it in within the time frame, then let's consider distro patching. this is a severe enough bug for that i think
[15:10] <Laney> backporting is different
[15:10] <Laney> we can do that for sure
[15:10]  * hyperair nods
[15:27] <pabelanger> morning all, I was looking to get some information about packaging a custom kernel into PPA.  Does anybody have any existing documentation?
[15:27]  * hyperair kicks networkmanager
[15:28]  * mok0 kicks networkmanager also
[15:28] <hyperair> imo networkmanager needs a Don't Roam checkbox.
[15:28] <mok0> hyperair: apt-get remove networkmanager
[15:28] <hyperair> when there are APs everywhere, NM likes roaming from one to the next one and the next one and the next one
[15:29] <hyperair> mok0: but ican't connect to WPA networks without it
[15:29] <mok0> hyperair: yeah that's a problem.
[15:29] <hyperair> honestly, NM roaming from one AP to another is a nice feature, but only if it works.
[15:29] <mok0> apt-get install networkmanager
[15:29] <hyperair> the WPA 4-way handshake thing doesn't work properly
[15:29] <hyperair> lol
[15:30] <hyperair> W: Unable to locate package networkmanager
[15:30] <hyperair> ;-)
[15:30] <mok0> hehe
[15:34] <hyperair> directhex: yay uploaded bce.
[15:34] <directhex> \o/
[15:35] <hyperair> so now let's look for a kindly archive admin =p
[16:55] <pabelanger> I was looking to get some information about packaging a custom kernel into PPA.  Does anybody have any existing documentation?  I'm looking to use the default linux package but modifiy it to only be my custom kernel (no the other 6).
[17:00] <ScottK> pabelanger: This isn't the channel for PPA questions.
[17:01] <nigelb> syncs requests are a bite delayed?
[17:01] <nigelb> got ack some time back, not yet sync'd, should I be worried?
[17:03] <ScottK> No
[17:08] <nigelb> :)
[17:12] <pabelanger> Let me re-phrase; I was looking to get some information about repacking a custom kernel. Is there any existing documentation?
[17:24] <ScottK> pabelanger: Kernel specific questions might go best in #ubuntu-kernel.  Packaging questions for PPAs are on topic in #ubuntu-packaging.
[17:35] <bdrung> nigelb: which bug?
[17:36] <nigelb> bdrung: bug 543139
[17:36] <bdrung> nigelb: don't worry; just wait
[17:37] <nigelb> bdrung: :)
[17:45] <Quintasan> jcastro: ping
[18:10] <jcastro> Quintasan: pong
[18:16] <Quintasan> jcastro: mind if I query you? I have some questions regarding bringing one of my parents to UDS
[18:18] <jcastro> sure
[18:18] <YokoZar> jdub: ok, adding libgnome-keyring should be easy
[18:19] <YokoZar> jdub: I'll try and make another upload when I get to "the office" (with real bandwidth)
[18:27] <cemc> help!
[18:28] <BlackZ> cemc: ?
[18:28] <cemc> http://pastebin.ubuntu.com/401298/
[18:28] <cemc> (64bit karmic host, 32bit lucid pbuilder, up-to-date)
[18:29] <cemc> I have no clue why it is looking in /lib32/
[18:29] <cemc> it's a 32bit pbuild, it shouldn't do that, imho
[18:29] <ScottK> cemc: Is this on Hardy?
[18:29] <cemc> no, Karmic host, Lucid pbuild
[18:29] <cemc> [03/25-202840] <cemc> (64bit karmic host, 32bit lucid pbuilder, up-to-date)
[18:30] <ScottK> Odd.  I built that package today on a 32bit karmic host and a 32 bit lucid pbuilder.
[18:30] <cemc> it's not the package
[18:30] <cemc> it's the pbuild
[18:30] <ScottK> I recall someone else had that problem, but I don't recall the solution.
[18:30] <cemc> it never worked for me, strangely...
[18:31] <cemc> the other pbuild images work like a charm, dapper, hardy, intrepid, jaunty, karmic, all of them
[18:31] <cemc> just this one won't, and just the 32bit one. the 64bit pbuild works too
[18:31] <cemc> I've rebuilt it twice
[18:32] <ScottK> I'd try moving your lucid 32bit chroot tarball aside and create a new one.
[18:32] <cemc> [03/25-203134] <cemc> I've rebuilt it twice (the tarball)
[18:32] <cemc> but I will try it again
[18:33] <ScottK> Oh.
[18:33] <ScottK> I thought you meant tried to build the package twice.
[18:34] <cemc> it's not the package methinks. it just tries to install the first dep and it fails to run dpkg because something is messed up in the chroot, I dunno...
[18:35] <ScottK> What happens if you do pbuilder login and install then?
[18:56] <cemc> ScottK: it seems to work...
[18:56] <ScottK> Odd.
[18:56] <ScottK> I'd just build it that way for now.  Not sure what the real solution is.
[19:54] <psusi> jdong: your post on the forums about dangerous commands says that rm -fr * will match ".." and delete things above this directory level... it will not... * does not match anything that starts with .
[19:54]  * psusi wonders why parts of that went bold
[20:00] <hyperair> indeed it won't. * only matches things that don't start with "."
[20:01] <hyperair> you'd have to do rm -rf * .* to get everything
[20:01] <hyperair> but .* will nicely hit . and .. as well so beware!
[20:01] <psusi> hehe
[20:34] <\sh> psusi, because * in your irc client means *BOLD*
[21:28] <Rhonda> Is the name for lucid+1 decided already?
[21:33] <geser> I haven't seen an announcement on the mailing list yet nor a blog post on planet (if I didn't miss anything)
[21:41] <zgreg> how about masturbating monkey?
[21:46] <\sh> I don't think that would represent ubuntu nicely...
[21:46] <RAOF> It should totally involve a Mongoose.
[21:48] <zgreg> \sh: oh come on, you don't know the linux hater's blog?
[21:49] <zgreg> \sh: http://linuxhaters.blogspot.com/2008/08/one-bug-report-to-rule-them-all.html
[21:49] <\sh> zgreg, I know that blog for sure ... but thinking about my company management..."Hey Boss, we are using now masturbatin monkey as new release" well, you know...
[21:50] <\sh> for joke ... not bad...for serious business...no ways...
[21:50] <zgreg> of course it's a joke :)
[21:52] <\sh> yeah..it's funny to read, but that's all
[22:03] <lfaraone> nhandler: would you be willing to review a FFe for bug 546139?
[22:03] <nhandler> lfaraone: Sure thing
[22:05] <nhandler> lfaraone: FYI, the changelog you attached isn't the upstream changelog
[22:05] <pepee> in lucid, aptitude keeps telling me that there's a conflict between fglrx and fglrx-kernel-source, xorg-driver-fglrx
[22:05] <pepee> is that the expected behavior?
[22:06] <nhandler> lfaraone: The Related branches link is also not working. Did you rename the branch?
[22:06] <pepee> (version: 2:8.721-0ubuntu5)
[22:16] <joaopinto> is anyone using eclipse+pydev ?
[22:18] <lfaraone> nhandler: sorry, I renamed it.
[22:18] <lfaraone> nhandler: refresh the page.
[22:18] <lfaraone> nhandler: https://code.edge.launchpad.net/~lfaraone/ubuntu/lucid/autokey/merge0.61.5-1ubuntu1
[22:21] <nhandler> lfaraone: Your changelog entry is a bit unclear. Is the only difference between the package and the debian package the transitional package? And can you attach a diff of the changes from Debian?
[22:22] <joaopinto> anyone involved on the eclipse packaging around ?
[22:23] <nhandler> joaopinto: You can try contacting bdrung^2
[22:23] <bdrung^2> joaopinto: it's me
[22:23] <bdrung^2> joaopinto: use eclipse 3.5.2-2ubuntu1
[22:24] <joaopinto> bdrung^2, eclipse plugins stopped working during alpha
[22:24] <joaopinto> the latest update didn't fix it
[22:25] <bdrung^2> they stopped working?
[22:25] <joaopinto> I had to switch to the upstream eclipse
[22:25] <joaopinto> yes, I was using eclipse+pydev
[22:25] <bdrung^2> i tested eclipse+pydev yesterday on lucid and it worked
[22:26] <joaopinto> after an upgrade it stopped recognizing the pydev projects
[22:26] <joaopinto> hum
[22:26] <bdrung^2> joaopinto: which version of eclipse do you have installed?
[22:26] <joaopinto> 3.5.2-2
[22:27] <bdrung^2> joaopinto: can you rename ~/.eclipse and install pydev again?
[22:27] <joaopinto> I tried that, with the previous version, i will try again
[22:30] <joaopinto> unable to install the plugin, it procudes an "invalid argument error"
[22:31] <joaopinto> Unable to connect to repository http://pydev.org/updates/content.xml
[22:31] <joaopinto> Argumento inválido
[22:31] <joaopinto>  == Invalid Argument
[22:32] <joaopinto> using the test connection with the main update site produces the same error
[22:34] <joaopinto> http://www.ubuntu-pics.de/bild/48928/problem_occurred__003_9w4Z04.png
[22:34] <bdrung^2> joaopinto: which openjdk version do you have installed?
[22:35] <joaopinto> /etc/alternatives/java -> /usr/lib/jvm/java-6-openjdk/jre/bin/java
[22:36] <bdrung^2> package version please
[22:37] <joaopinto> openjdk-6-jre-headless        6b18~pre3-0ubuntu1
[22:38] <joaopinto> eclipse from eclipse.org update site test runs fine
[22:40] <bdrung^2> then i have no clue. you can join #debian-java on OFTC and ask nthykier
[22:42] <joaopinto> oh, for that I should test it on debian first, too much effort, I'll keep with the zip version :P tks anyway
[22:43] <bdrung^2> joaopinto: we have a DOA team that works on the eclipse package for Debian _and_ Ubuntu. You don't have to test it on Debian first.
[22:44] <joaopinto> DOA ?
[22:44] <bdrung^2> Debian Orbital Alignment ;)
[22:45] <joaopinto> lol, ok
[22:58] <verwilst> hello, im trying to package something for my ppa
[22:58] <verwilst> but i get this when uploading with dput: dpkg-buildpackage: source only, diff-only upload (original source NOT included)
[22:59] <verwilst> after which i get an email saying "Files specified in DSC are broken or missing, skipping package unpack verification."
[22:59] <verwilst> the .orig.tar.gz
[22:59] <crimsun> did you pass -sa?
[22:59] <verwilst> no :$
[22:59] <verwilst> my other 2 packages went fine without -sa :)
[23:00] <crimsun> if the orig.tar.gz is in the archive, sure
[23:00] <crimsun> or orig.tar.bz2 or whatever
[23:01] <verwilst> crimsun, in the archive? the other packages were totally new as well?
[23:03] <crimsun> verwilst: need more detail.
[23:04] <verwilst> well crimsun, the -sa made the orig uploadable as well :)
[23:04] <verwilst> just don't really understand why that 1 package wouldn't include the orig tarball by default :)
[23:05] <verwilst> the build servers seem slower than last year btw :P
[23:05] <verwilst> accepted!!
[23:05] <verwilst> hooray!
[23:05] <verwilst> thanks crimsun :)
[23:21] <bdrung^2> verwilst: it depends on the debian version. the first revision of a new upstream version contains the source. the later not.
[23:22] <verwilst> bdrung^2, hm, ok :)