[02:22] <dhillon-v10> hi all, is it possible to adopt a debian package while running Ubuntu I don't think it is but please explain why or why not
[02:23] <bjsnider> you mean install?
[03:09] <bddebian> dhillon-v10: Anyone can adopt a package but you must test on Debian and sync to Ubuntu or you may have issues.
[03:10] <dhillon-v10> bddebian, can I make a debian chroot maybe, the instructions for adopting the package are * really * confusing so I was hoping for a simplified version of that
[03:11] <bddebian> Sure or pbuilder
[03:12] <dhillon-v10> bddebian, do you have like 5 minutes of time, I need some help on how to adopt a package
[03:12] <bddebian> If the package is orphaned it isn't too difficult.  Add your changelog entry stating you are adopting the package and close the O: bug.
[03:13] <bddebian> Of course you will need to find a Debian sponsor to upload it if you are not a DD.
[03:14] <dhillon-v10> bddebian, yah exactly its orphaned so then I change the maintainer field right and report that in the changelog as well, then ask one of my friends to upload the package and close the bug right :D
[03:15] <bddebian> Yep
[03:15] <dhillon-v10> bddebian, so what are the tasks that a maintainer has to do, I am not too good with packaging stuff
[03:16] <bddebian> Then why would you want to adopt it?
[03:17] <bddebian> Maintenance includes fixing bugs in the package, keeping it up to date with policy, new upstream releases, etc
[03:18] <dhillon-v10> bddebian, its something I work with a lot, docbook stuff, I mean I can package software, I have done so in the past but the fixing bugs part, I am unsure about that
[03:20] <bddebian> Well if it makes you feel any better, I'm a DD and I can't fix much. :)
[03:21] <dhillon-v10> bddebian, nice :D but you are probably like a million time better than me so I still feel dumb :)
[03:21] <bddebian> I'd take that bet. :)
[03:22] <dhillon-v10> bddebian, check this out its awesome: http://theoatmeal.com/comics/computers
[03:24] <bddebian> Heh, sounds familiar :)
[03:25] <dhillon-v10> bddebian, yup happens to me a lot, especially after having migrated to Ubuntu :D
[03:37] <ScottK> bddebian is a god and we have documentation to prove it.
[03:38] <ScottK> https://wiki.ubuntu.com/BddebianIsAGod
[03:39] <bddebian> bah
[03:39]  * bddebian runs away
[03:45] <dhillon-v10> bddebian, I am gonna be one of your fans as well :D you indeed are awesome, I asked the same question on #debian and their response was "no" just that "no"
[03:48] <bddebian> Well Debian isn't the most accepting of us n00bs unfortunately.
[03:48] <dhillon-v10> bddebian, alright one job done right: https://wiki.ubuntu.com/BddebianIsAGod now back to filing sync reports :D
[06:20] <wrapster> supposing i get an error saying ld: library -lmeta: not found.. how do i check in packages.ubuntu.com as to which pkg provides this meta lib?
[06:20] <wrapster> sorry I know its a basic question.. but when i tried searching for meta i could not find it.
[06:26] <fabrice_sp> wrapster, did yo utry with limeta?
[06:26] <fabrice_sp> libmeta, sorry
[06:27] <wrapster> fabrice_sp: no.. but i did find this.. "/usr/lib/cgi-bin/meta---->             	 	faqomatic" ..installed it but the make again fails so it cannot be that...
[06:27] <fabrice_sp> in a dev package
[06:28] <fabrice_sp> are you sure the package that provide libmeta is in Ubuntu?
[06:29] <wrapster> faqomatic
[06:29] <wrapster> hardy
[06:29] <wrapster> but guess thats not the one
[06:30] <fabrice_sp> no: the linker is looking for libmeta
[06:30] <fabrice_sp> -lmeta means link with libmeta
[06:30] <fabrice_sp> provided by a -dev package
[06:30] <wrapster> yeah.. got it... http://opensolaris.pastebin.ca/1723378
[06:30] <wrapster> may be this will help you beter
[06:35] <fabrice_sp> ni idea. sorry. Di you try googling?
[07:49] <dholbach> good morning
[07:51] <Quintasan> dholbach: hello
[07:52] <dholbach> hey quintasan
[09:40] <norax_> hi
[09:42] <norax_> There is a very outdated package in debian, I would like to package it for ubuntu despite that debian does not update it. It is a game (kq) so it is not very essential. Is it possible?
[10:04] <gaspa> norax_: yes, you can. did you try to contact Debian maintainers, though?
[10:05] <randomaction> norax_: are you aware of bug 325263?
[10:05] <norax_> no, it is the allegro team, not a person
[10:06] <norax_> yes. I wrote there
[10:06] <randomaction> so you have a package ready?
[10:07] <norax_> yes. I can rebuild it in lucid
[10:07] <norax_> it is now in karmic
[10:07] <gaspa> norax_: you can contact a team, as well :P even if it's not a person :D
[10:08] <norax_> well, I will write to them, and if I am not answered before the freezing I will try to upload to lucid
[10:08] <norax_> thanks
[10:09] <randomaction> after the freeze it will be harder to update a package in Ubuntu
[10:10] <gaspa> randomaction: too much haste :)
[10:15] <randomaction> I mean, I would request sponsorship [a couple of weeks] before FF
[10:32] <gaspa> randomaction: I agree, just that norax didn't see your message :P
[12:48] <mansa> i mean were are the list of bugs
[12:49] <mansa> were can i see the list of bugs
[12:49] <mansa> any one
[12:53] <randomaction> https://bugs.launchpad.net/ubuntu
[14:57] <cratylus> is debconf a commonly used system for configuring packages ?
[15:13] <bddebian> Heya gang
[15:14] <nhandler> Howdy bddebian
[15:15] <iulian> 'ey bddebian, nhandler.
[15:15] <bddebian> Heya nhandler, iulian
[15:38] <cratylus> for a source package's architecture, what's the difference between 'any'  and 'all' ?
[15:39] <wasabi_> That should be trivially discoverable by reading the debian packaging manual.
[15:40] <cratylus> wasabi_ yep, doing it now. guess i missed it
[15:40] <cratylus> gonna read more in depth
[15:41] <cratylus> found it. http://www.debian.org/doc/debian-policy/ch-controlfields.html#s-f-Architecture
[15:41] <cratylus> :)
[16:29] <sharms> can someone review this debdiff for me for lucid?  Its a long standing issue I finally figured out: https://bugs.launchpad.net/ubuntu/karmic/+source/ncpfs/+bug/328020
[16:36] <crimsun> sharms: ouch, looks kinda sick for karmic
[16:43] <sharms> yeah I couldnt get anyone to put the jaunty version in karmic
[16:43] <sharms> whatever change happened to gcc caused their i386 specific code to stop working
[16:44] <sharms> it stopped working for amd64 also, but I was able to fix the packed definitions which made that branch work
[16:44] <sharms> but the fixes didnt resolve the i386
[16:45] <sharms> good news is the debdiff I have there works for karmic also
[16:45] <sharms> I am not sure if there will even be a SRU for it as that is a rather complex process, but I am hoping for lucid we go out of the gate with it working
[16:45] <crimsun> well, I can help with SRU
[16:46] <crimsun> can you ifdef 0 around the relevant bits instead of removing? It'll be easier to view as a minimal debdiff
[16:46] <sharms> sure
[16:49] <RoAkSoAx> hey guys I'm wondering if merges.ubuntu.com is up-to-date or how long does it take to update a package in the list after it has been migrated to testing?
[17:02] <sharms> crimsun: ok compiled and tested on i386 and amd64 and attached debdiffs for karmic / lucid on lp #328020
[17:03] <randomaction> RoAkSoAx: it's really out of date
[17:04] <RoAkSoAx> randomaction, yeah... do you know who maintains the list?
[17:04] <RoAkSoAx> dholbach, ping
[17:05] <dholbach> RoAkSoAx: pong
[17:05] <randomaction> no I don't
[17:05] <RoAkSoAx> dholbach, who maintains the merges lists since it seems to be out of date :)
[17:05] <dholbach> RoAkSoAx: Keybuk probably?
[17:05] <RoAkSoAx> dholbach, awesome, thanks I'll ping him :)
[18:06] <crimsun> sharms: great, thanks. Sorry, am in a conf call but will push shortly.
[18:07] <maco> crimsun: pm?
[18:22] <EagleScreen> hi
[18:22] <EagleScreen> i am having troubles singing my packages at build the source package, some gpg or gog-agent issue, by the moment i have uninstalled gpg-agent
[18:26] <EagleScreen> okay i have fixed in DEBFULLNAME variable
[19:25] <EagleScreen> hi
[19:26] <EagleScreen> kdbg package depends on kde4libsca in karmic
[19:26] <EagleScreen> and amarok-kde3 depends on kde4libsca-kde3 from karmic kde3 ppa
[19:27] <EagleScreen> kde3 applications from kde3 ppa and karmic repo are incompatible
[19:29] <EagleScreen> therefore, i want to make my customized .deb package of kdbg, and I want to replace depends on kdelibs4ca by (kdelibs4ca | kdelibs4ca-kde3)
[19:30] <ScottK> EagleScreen: You can't (as I just said on #kubuntu-devel)
[20:30] <ari-tczew> I'm looking for Security Sponsors...
[20:32] <ScottK> ari-tczew: Look on #ubuntu-hardened
[20:52] <geser> ScottK: what about replacing the "lastest rebuild failures" in the topic to point to http://udd.debian.org/cgi-bin/ubuntu_ftbfs.cgi? as it's more up-to-date than the old archive rebuild
[20:53] <ScottK> geser: Sounds good.
[20:54] <ari-tczew> nice tool
[20:56] <abogani> Hi! Sorry to bother you! Anyone could review my fix for an FTBFS (https://code.launchpad.net/~abogani/ubuntu/lucid/gdb-avr/gdb-avr.fix-FTBFS/+merge/16509)? Thanks in advance!
[20:58]  * geser bookmarks https://code.edge.launchpad.net/~ubuntu-universe-sponsors/+activereviews to not forget looking at the review queue too
[21:01] <geser> abogani: looks good. I just need to figure out how the reviewing and sponsoring of merge proposals work in detail
[21:03] <abogani> geser: Thanks you're too kind.
[21:15] <lfaraone> Should a SRU patch be in debdiff format?
[21:16] <geser> ask the SRU people if they prefer a debdiff or a merge proposal
[21:16] <lfaraone> geser: merge proposal?
[21:17] <geser> get the bzr branch, do your changes, push it to your LP account, seek sponsorship
[21:17] <ScottK> lfaraone: I don't think there are any potential sponsors that don't know how to deal with a debdiff.  For merge proposals the set of potential sponsors is smaller.
[21:18] <lfaraone> ScottK: mk
[21:26] <lfaraone> ScottK: if I'm not in MOTU, do I need my SRU sponsored before subscribing ~ubuntu-sru?
[21:29] <pochu> lfaraone: the other way round IIRC. first get the SRU approved, then get sponsorship
[21:30] <lfaraone> pochu: okay.
[21:30] <lfaraone> jdong: ping. can you ACK bug 479131 so maco can upload it to -proposed?
[21:33] <abogani> Sorry for apparent stupid question: Who can sponsor a SRU of 3.3 MB in size?
[21:33] <ari-tczew> abogani: propably you did wrong debdiff
[21:33] <lfaraone> abogani: which bug?
[21:34] <lfaraone> (I second ari-tczew , that sounds like a bad debdiff)
[21:35] <abogani> lfaraone: bug 495383
[21:35] <ari-tczew> ;o
[21:38] <abogani> No suggestions for me? :-(
[21:39] <ari-tczew> nothing from be, because I don't touch packages called linux*
[21:40] <crimsun> lfaraone: it doesn't need to block on any one person
[21:42] <abogani> ari-tczew: Exactly for this reason since Intrepid, when linux-rt became an universe  package under MOTU's umbrella, I never found a way to update it (after release).
[21:44] <crimsun> abogani: looking in a sec (blocked on my web browser loading)
[21:50] <Quintasan> Can we now upload bzip2 tarballs or I still need to repack?
[21:52] <Laney> should work now
[21:52] <Laney> (with source format 3.0)
[21:52] <micahg> is source format 3 only for Lucid?
[22:06] <wgrant> micahg: Yes. We could enable it for karmic, though -- it might be handy for PPAs.
[22:06] <wgrant> And backports.
[22:09] <micahg> wgrant: I was thinking maybe for mozilla stuff, but if it's only back to karmic, that won't work...I guess we'll wait till 2011 :)
[22:10] <wgrant> micahg: Debian has backported the 3.0 patches to Lenny, but I can't really see us doing that to Hardy, although it would be very handy.
[22:11] <micahg> well, hardy and karmic end desktop support at the same time
[22:11] <wgrant> So they do.
[22:12] <wgrant> I guess it's possible that you could convince people to backport the necessary patches. But that's an #ubuntu-devel question. A scary one.
[22:15] <pochu> wgrant: lenny already supported them AFAIK... what have been backported are some late fixes
[22:16] <wgrant> pochu: Right.
[22:16] <wgrant> pochu: That's what I intended to convey, but I did not do it well.
[22:20] <Quintasan> hmm can anyone help me with watch file? what I have now is -> http://pastebin.com/f12f92790  the current package version is 0.11, and uscan --verbose output is -> http://pastebin.com/f49396814
[22:28] <asac> Lutin: there?
[22:28] <asac> did the syncs for the efl deps happen yet?
[22:29] <asac> let me know what needs to get poked
[22:35] <ari-tczew> Quintsan, please try http://dl.fefe.de/gatling-(.*).tar.bz2
[22:37] <Quintasan> ari-tczew: hmm, still no matching hrefs for watch line
[22:38] <geser> not sure, but doesn't uscan need some sort of index to look at?
[22:48] <Laney> geser: I'm still seeing that unicode error with requestsync (requestsync --lp -d unstable haskell-regex-compat)
[22:51] <geser> I see it too, but it's a different location now
[22:51] <Laney> yeah, at editing the report it seems
[22:52] <Laney> don't know much about python unicode
[23:04] <geser> Laney: Committed revision 548
[23:05] <Laney> \o
[23:05] <Laney> thanks!
[23:06] <geser> hope it works now (didn't try to file the sync request)
[23:06] <Laney> Oh, I tried that but with unicode() around it
[23:07] <Laney> Sync request filed as bug #499626: https://edge.launchpad.net/bugs/499626
[23:07]  * Laney hugs geser 
[23:09] <ari-tczew> I propose to include example for requestsync on wiki.ubuntu
[23:10] <Laney> it's a wiki, so you can make it so
[23:10] <ari-tczew> ok
[23:10] <Laney> (you think it is that hard to use?)
[23:10] <ari-tczew> nope :)
[23:11] <crimsun> it may be difficult for someone who hasn't used it
[23:11] <Lutin> asac: the sync actually happened, however due to some issues with new binary packages being promoted to main, it's been kind of a mess regarding the builds
[23:11] <crimsun> I keep forgetting how second-hand this stuff becomes
[23:11] <Lutin> asac: it's being sorted out, most of them are built now. probably needs a couple days to have all them built and accepted
[23:12] <Laney> I just looked at --help and it seemed alright, but of course I can't be objective
[23:12] <Laney> examples in the man page might be useful though
[23:12] <Laney> ari-tczew: ^^^
[23:12] <Laney> manpage is probably a better place than the wiki (or both)
[23:19] <ari-tczew> I don't use manpage
[23:20] <ScottK> ari-tczew: You should.
[23:21] <Laney> They are the canonical source of documentation (usually)
[23:24] <asac> Lutin: hmm. ok. do you have the package names involved at hand?
[23:27] <jibel> Hi, could anyone please review my latest fix for an FTBFS in karmic for bug  392143 ?
[23:28] <crimsun> jibel: where is the fix?
[23:29] <Lutin> asac: efreet edje and edbus still need building on armel and are in NEW on amd64/i386;
[23:29] <Lutin> asac: and elementary relies on edje, so give-backs will be needed as soon as edje is built for armel, and accepted on other archs
[23:30] <jibel> crimsun, last comment http://launchpadlibrarian.net/37104426/postgis_1.3.5-1ubuntu1.debdiff
[23:30] <crimsun> interesting, I see only comment #14
[23:30] <crimsun> reloading
[23:31] <jibel> crimsun, I'm not sure about the replacement of jikes by default-jdk in karmic.
[23:36] <ScottK> jibel: Since jikes no longer exists, there isn't a lot of choice.
[23:38] <asac> Lutin: great. thanks for your efforts. if you need anything let me know ;)
[23:38] <asac> Lutin: in review you complained about duplicated effort. what was that about?
[23:38] <asac> revu
[23:39] <Lutin> asac: oh, nothing major. just that I was asked to work on packaging something while someone was already working on it within canonical
[23:39] <asac> Lutin: n-l-efl?
[23:39] <Lutin> yup
[23:39] <asac> or even other packages?
[23:40] <Lutin> no, that one. but as I said, nothing major
[23:40] <asac> kk
[23:41] <asac> i must admit that i wasnt aware of that either ;)
[23:41] <asac> i thought jamie would package it
[23:41] <Lutin> heh :)
[23:41] <asac> but then mterry came up with a new version
[23:41] <Lutin> the package looks good though, apart from the couple remarks I made on revu
[23:42] <asac> yeah build depend version bump makes sense
[23:43] <ari-tczew> wrrrrrr
[23:43] <ari-tczew> I never learn about requestsync
[23:43] <ari-tczew> E: No credentials found for 'ubuntu-dev-tools', please see the manage-credentials manpage for help on how to create one for this consumer.
[23:44] <ari-tczew> from the command: $ requestsync --lp -d testing dosbox lucid 0.73+dfsg1-1
[23:44] <ajmitch> and did you look at the manage-credentials manpage?
[23:44] <ari-tczew> nope
[23:44] <Lutin> asac: well, not as much as the other one - it will hit the archive while a correct version of ecore is there. the non-existent dependency might be more of an issue
[23:44] <ari-tczew> why this didn't automatically?
[23:45] <geser> ajmitch: ari-tczew doesn't use manpages as he said
[23:45] <ajmitch> perhaps it needs more <blinks> tags
[23:45] <ajmitch> geser: that's unfortunate
[23:46] <jibel> ScottK, fine, I'm not familiar with java stuff.
[23:46] <jibel> ScottK, another question, if the previous upload to -proposed FTBFS, do I need to increase the ubuntu version by one for the new patch or leave the same as the previous upload ?
[23:46] <ScottK> jibel: Increase it.
[23:47] <geser> jibel: once a version number got accepted (successfully uploaded) you need to increase it
[23:48] <asac> Lutin: right
[23:48] <ari-tczew> ajmitch: ah, so do I need to create manage-credentials
[23:50] <geser> read the manpage, damn it
[23:50] <geser> there is even an example you can copy & paste for use with ubuntu-dev-tools
[23:50] <ScottK> james_w: When you're around, I'm trying to merge via bzr and getting some odd results.  My clamsmpt merge seems to have a stack of .svn dirs in it that neither Ubuntu nor Debian currently ship (IIRC, upstream left these in, in a previous release).
[23:50] <jibel> ScottK, geser, thanks.
[23:51] <Lutin> asac: gotta go to bed. if you need anything efl-related, feel free to ping me on IRC anytime
[23:51] <asac> Lutin: thanks. 'night
[23:51] <ari-tczew> what's launchpad mean about my private data?
[23:52] <ScottK> james_w: Unping.  I just wasn't looking hard enough.
[23:54] <ScottK> james_w: (sorry) reping: It looks like the upstream .svn are in our package, but not in the branch.
[23:54] <geser> ari-tczew: I think it's not about your private data, but more about private bugs, etc. to which you wouldn't have access if not logged in
[23:55] <Quintasan> What's with revu key?
[23:56] <geser> revu key? you mean the import of your gpg key into revu? it's done automatically on your first login (so go a login once before you upload your first package)
[23:58] <Quintasan> geser: nah, the key just changed, and I figured out that revu still doesn't accept source format 3.0