[00:15] <lifeless> hmm
[00:15] <lifeless> anyone know when dh added the '--without' option ?
[00:16] <lifeless> Trying to do a backport of subunit to hardy & getting an error about that
[00:18] <micahg> lifeless: 7.2.9
[00:20] <micahg> lifeless: which is karmic and later
[00:21] <lifeless> arhh - thanks
[05:04] <MTecknology> I just tried to package for the latest openbox but it'll only build for i386
[05:04] <MTecknology> https://edge.launchpad.net/~mtecknology/+archive/ppa/+packages
[05:05] <MTecknology> oh......
[05:06] <wgrant> It's arch-indep?
[05:06] <wgrant> Hm, no.
[05:06] <wgrant> It's arch: i386.
[05:06] <wgrant> == wrong
[05:06] <MTecknology> ya, I just changed that to any
[05:06] <MTecknology> !info openbox lucid
[05:07] <matti> ;]
[05:09] <MTecknology> maybe this will work right now :)
[05:10] <MTecknology> waiting for the new build to start now..
[05:11] <MTecknology> rejected...
[05:11] <MTecknology> apparently it lacks common sense for >
[05:11] <MTecknology> :P
[05:12] <wgrant> ?
[05:13] <MTecknology> I changed from 3.4.9-ppa0 to 3.4.9-1ubuntu1
[05:13] <MTecknology> I deleted the ppa0 one
[05:14] <MTecknology> I'm trying to upload it again
[05:39] <MTecknology> What's going on with this? https://edge.launchpad.net/~mtecknology/+archive/ppa/+packages
[05:39] <MTecknology> "Dependency wait"
[05:43] <MTecknology> eh... I'll just bug somebody to get 3.4.9 into 10.04
[05:54] <wgrant> MTecknology: Did you just manually retry that?
[05:55] <wgrant> And on what did it depwait?
[05:55] <MTecknology> I didn't knwo I could check that..
[05:55] <wgrant> The email will probably tell you, and so does the page (until it's retried).
[05:55] <wgrant> Did you retry it?
[05:56] <wgrant> I wonder if it was retried automatically in error.
[05:56] <MTecknology> no; no email either; but i wound up deleting it
[05:56] <wgrant> Oh, right, no email for depwait.
[05:56] <wgrant> But did you retry it or not
[05:56] <wgrant> ?
[05:57] <MTecknology> no
[05:57] <wgrant> So there is a bug :(
[05:57] <MTecknology> I broke something :D
[05:58] <wgrant> Oh, no, I was just looking at the wrong build.
[05:59] <wgrant> xlibs-dev hasn't existed for a Long Time.
[05:59] <MTecknology> I'll try to pull the current version and look at the debian/* files and compare
[05:59] <MTecknology> I was trying to build from what they already had
[05:59] <MTecknology> git clone git://git.icculus.org/mikachu/openbox openbox
[06:03] <MTecknology> wgrant: this is weird... I was doing apt-get source openbox and apparently there's this too - svn://svn.debian.org/svn/collab-maint/deb-maint/openbox
[06:03] <wgrant> MTecknology: Is that weird?
[06:04] <MTecknology> wgrant: well - they use git..
[06:04] <MTecknology> wgrant: as far as their wiki sayd
[06:04] <MTecknology> says*
[06:05] <wgrant> MTecknology: Upstream might use git now, but the Debian package use(s|d) svn.
[06:05] <wgrant> Not an uncommon situation.
[06:06] <MTecknology> ok; I'll just try to make this work using git
[06:06] <MTecknology> I know git is upstream
[06:08] <MTecknology> I was told the fix I'm after is in git
[06:11] <MTecknology> wgrant: I'm thinking I might need to try out dh_make even though most of the stuff is already there .. idk
[06:13] <MTecknology> wgrant: app_version-karmic0; is that the right format?
[06:14] <wgrant> MTecknology: That does not match any of the commonly accepted version conventions. Have a look around at packages, PPAs and documentation.
[06:15] <MTecknology> wgrant: I'm probably too tired to be doing this if I'm not finding any of that :P
[06:16] <ScottK> Probably.
[06:16] <MTecknology> 0ubuntu1
[06:16] <MTecknology> I see that one
[06:16] <ScottK> that's for the archive, not for PPAs
[06:16] <MTecknology> I was looking at https://edge.launchpad.net/~doctormo/+archive/ppa
[06:17] <MTecknology> I saw app_version-ppa0 earlier
[06:17] <ScottK> He's not an Ubuntu developer, so consider the source.
[06:17] <MTecknology> true
[06:17] <MTecknology> I'd like to make sure this gets into 10.04; but that comes later; for now I just use -ppa0 ?
[06:18] <ScottK> No.
[06:18] <MTecknology> I'
[06:18] <MTecknology> I'll look around more
[06:19] <crimsun> foo_1.0-0ubuntu1~ppa1, foo_1.0-0ubuntu1~mktecknology1; foo_1.0-0ubuntu1+ppa1; foo_1.0-0ubuntu2~ppa1
[06:20] <crimsun> each of those has a specific use
[06:20] <crimsun> the first set (delimited by semicolon) is for a PPA version not yet in Ubuntu proper
[06:21] <crimsun> the second set is for a PPA version newer than what's in Ubuntu proper that you wish to denote is explicitly based on 1.0-0ubuntu1
[06:21] <crimsun> the third set is for a PPA version newer than what's in Ubuntu proper that you wish to denote may not be based on what will be in the next Ubuntu version
[06:21] <crimsun> and, of course, there are variations
[06:22] <crimsun> the importance of proper versioning is that you don't want override the next version in Ubuntu proper
[06:22] <MTecknology> how do I see how it's named in Ubuntu?
[06:22] <MTecknology> openbox-3.4.7.2
[06:23] <crimsun> rmadison
[06:23] <crimsun> so, rmadison -uubuntu openbox
[06:23] <crimsun> (you can omit -uubuntu for sufficiently new versions of rmadison)
[06:23] <crimsun> likewise, -uqa for what's in Debian
[06:23] <MTecknology> lucid = 3.4.7.2-5
[06:24] <crimsun> make sure you pass source package names to rmadison (or at least be aware that you should read the corresponding 'source' output line)
[06:24] <MTecknology> hardy has the ubuntu word in it - 3.4.6.1-0ubuntu2
[06:25] <crimsun> namely, you can pass binary package names to rmadison, but the output can be confusing unless you're fairly familiar with the packaging (e.g., linux, linux-meta{
[06:25] <crimsun> )*
[06:25] <MTecknology> otherwise it goes -2, -3, -4, -5
[06:25] <MTecknology> I hope to be familiar enough with it someday
[06:27] <MTecknology> so openbox_3.4.9.0-0+ppa1 ?
[06:27] <crimsun> what's the actual upstream version?
[06:27] <MTecknology>    openbox |  3.4.7.2-5 | lucid/universe | source, amd64, i386
[06:27] <MTecknology> oh..
[06:27] <MTecknology> 3.9.4
[06:28] <MTecknology> 3.4.9 **
[06:28] <crimsun> so, it's a good idea to get 3.9.4 into Debian unstable
[06:28] <crimsun> 3.4.9, then
[06:28] <crimsun> since sid only has 3.4.8
[06:29] <MTecknology> packaging is the same isn't it? I just need to submit to that other place
[06:29] <crimsun> (a somewhat Ubuntu-centric dev would use 3.4.9-0ubuntu1~foo1, but again, getting it into Debian sid is the better choice)
[06:29] <MTecknology> http://mentors.debian.net/
[06:30] <crimsun> yes, mentors
[06:30] <crimsun> anyhoo, offline for toodles
[06:30] <MTecknology> which is why it lacks the ubuntu1 part?
[06:31] <MTecknology> ok, thanks - I'll try to package it with openbox_3.4.9-0+ppa1
[06:32] <MTecknology> or s/0/1/ ..?
[06:32] <wgrant> Is it derived from the first Debian version of 3.4.9?
[06:33] <MTecknology> not afaik
[06:33] <wgrant> Then -1+* would be a lie.
[06:33] <MTecknology> debian doesn't have 3.4.9
[06:33] <MTecknology> -0+* would be honest then?
[06:34] <wgrant> Yes.
[06:34] <MTecknology> that's the people telling me arrays should start at 1 :P
[06:39] <MTecknology> wgrant: so after I build iti I should rename karmic to lenny and submit to debian mentors?
[06:40] <wgrant> MTecknology: If you want to submit it to Debian mentors, yes.
[06:40] <MTecknology> thanks
[06:42] <ScottK> You'll want to follw the Debian scheme for revision numbering on mentors though.
[06:44] <MTecknology> ScottK: it looks like that means just omittint the +* for this
[06:49] <MTecknology> this doesn't look like a good package to practice on...
[08:07] <LLStarks> hi.
[08:07] <LLStarks> why is adobe-flashplugin used for restricted extras instead of flashplugin-installer?
[10:39] <surfzoid> Hi
[10:39] <surfzoid> on the web, is there deb pkg of mono more recent than the 2.4 ?
[10:40] <surfzoid> directhex: you are the Mono expert :-) ?
[10:40] <ikonia> if there is why would you want it ?
[10:42] <surfzoid> ikonia: weired question, but, because i m developper and want to folow some bug fix, new feature and so one, also at least if there isn't one i plane to build one throug open suse build service
[10:42] <ikonia> if it's outside the ubuntu repo's it doesn't seem with it as it won't be packaged for ubuntu, so your testing may not be valid
[10:43] <ikonia> eg: you test it , it works, ubuntu package it slightly different (patches etc) and your testing is void
[10:43] <surfzoid> so once time is the ubuntu mono pkg more recent than the old 2.4 ?
[10:44]  * surfzoid is there
[10:44] <ikonia> surfzoid: is it in the repo ?
[10:44] <surfzoid> ikonia: is there a way to contribute in packaging or the actual maintener of Mono pkg work on it ?
[10:45] <surfzoid> yes in the repo = 2.4
[10:45] <ikonia> surfzoid: so then the version in the repo is the latest version
[10:45] <ikonia> (assuming you're checking all the repos)
[10:45] <surfzoid> 2.4 is pretty old
[10:45] <ikonia> surfzoid: what version of ubuntu ?
[10:45] <surfzoid> ikonia: 9.10 , but i m new in ubuntu word, perhap s i miss an repo
[10:46] <ikonia> surfzoid: also - you're in the right place to contribute, lots of guys in here are part of the packaging world
[10:46] <surfzoid> ikonia: so how to process, i already have my own ubutu repo, but is not "oficial"
[10:46] <ikonia> ikonia: if you go to "system->administration->software sources" you can see what repos you have
[10:47] <ikonia> surfzoid: I guess it depends where the package you want to update is, (what repo)
[10:47] <surfzoid> ikonia: my repo live at opensuse OBS
[10:48] <ikonia> errrrr I mean what ubuntu repo the package you want to update is in
[10:50] <surfzoid> ikonia: i'm not sur it could help since is in french, but here it is my repo http://picpaste.com/pics/Capture-3.1261306191.png
[10:50] <surfzoid> i will look for mono source
[10:52] <surfzoid> ikonia: mono is from this repo : http://picpaste.com/pics/Capture-4.1261306333.png
[10:53] <ikonia> !info mono-runtime
[10:53] <ikonia> surfzoid: ok - so it's in the core main repo
[10:53] <surfzoid> !info mono
[10:53] <ikonia> surfzoid: you'd have to get a launcpad.net account and contribute to the package that way, it's developers will be in #ubuntu-devel
[10:54] <surfzoid> hum i have reqested a build pkg of my softwares at lauchpad so my account is enought ?
[10:55] <ikonia> I'd gues s so
[10:55] <ikonia> oops, guess so
[10:55] <surfzoid> so after i build the pkg somewhere and mail directly to the actual maintener ?
[10:56] <ikonia> log an update request and link your package to it
[10:56] <ikonia> (the one in your ubuntu branch) talk the maintainers, most are really gratful for help, speak to directhex also, he's put in a lot of effort for mono and ubuntu / debian
[10:56] <surfzoid> like the !info, there is an query to know the actual guy who package mono ?
[10:56] <surfzoid> oki
[10:57] <ikonia> surfzoid: it's normally not one guy (but can be) if you log a bug/upgrade against in launchpad it will contact the maintainers
[11:00] <surfzoid> damed i m logged at LP, but it is where i post new bug !!
[11:03] <surfzoid> ikonia: i m complety unable to find how to post a new bug !! https://bugs.launchpad.net/ubuntu/+bug/443398
[11:04] <ikonia> surfzoid: if there is an existing bug - add to it
[11:04] <surfzoid> i used the search engine but no result
[11:04] <surfzoid> so i guess i need to add, but where ?!! it is amazing to have a so complicated system !
[11:05] <ikonia> then log a new bug,
[11:05] <ikonia> why did you post that bug (443398) if it's not the bug you're interested in
[11:06] <surfzoid> that s what i try ,and finally find a link from my old bug, but from home page if you click on "bug" there isn t link to report a new one !!
[11:06] <surfzoid> iko see date of the bug please
[11:06] <ikonia> I don't need to see the date of the bug
[11:08] <surfzoid> ikonia: "why did you post that bug (443398) if it's not the bug you're interested in" because we spoke about an Mono release today and the old 443398 is an MonoOSC bug for release of my software, so yes , see the dates !!
[11:08] <ikonia> why ???
[11:09] <ikonia> it's either the bug you want to update, or it's not
[11:09] <ikonia> in which case log a new one
[11:10] <surfzoid> comon, of course not : bug 443398 = MonoOSC/MonoOBSFramework, the new bug we are speaking = Mono Framework
[11:10] <ikonia> ????
[11:11] <ikonia> either update the bug if you feel it's relevant, or log a new bug that is what you need/want
[11:11] <surfzoid> Finaly i will not report a release query, ubuntu is really to mutch complicated for me, i will simply and badly duplicate efort by building Mono in my OBS repo !!
[11:11] <ikonia> a release query, ???
[11:12] <ikonia> you don't want a query, you want it updated, so to get it updated you need to log a bug/feature request
[11:12] <surfzoid> i know my english is poor, but realy at this level
[11:12] <ikonia> I don't understand why that is a problem
[11:16] <surfzoid> release/update query/log okidoki !!
[11:16] <surfzoid> same thing
[11:17] <ikonia> ???
[13:01] <geser> dktrkranz: re debian bug #560758: this it not due the LP debian mirror being out-of-sync (as no --lp switch got used) but due to rmadison now listing several "source" lines and the requestsync code not using the most recent one (I found it now too and looking into it)
[13:20] <dktrkranz> geser: mmh, that's probably the real issue, I checked on some packages and I was unable to reproduce anymore, maybe I was just unlucky to pick those with a single source entry
[13:34] <adhorden> inside a package is there any way to stop it from building the documentation? I am building and packaging a cross compiler based on gcc-4.4.2 but I do not need the docs, so was curious if you can stop this in the configure arguments
[13:36] <geser> depends on upstream's configure script
[13:38] <adhorden> geser, the upstream package is gcc-core-4.4.2 and I just apply a patch to build a cross compiler, I am guessing the GCC configure script does not allow you to disable building of docs
[13:39] <adhorden> I just have an rm -rf /usr/man in my rules but i though there might be a better solution
[14:19] <surfzoid> so i m trying to build an ubuntu pkg with the folowing dsc : http://pastebin.com/d71362a67
[14:20] <surfzoid> but i already get the folowing error
[14:20] <surfzoid> dpkg-source: error: Files field contains bad line `c87d9fdb04a3233cd89512dbf816cc5a mono-2.6.1.tar.gz'
[14:20] <surfzoid> i really don't see what is wrong in format or other !
[14:21] <surfzoid> anybody have an clue ?
[14:22] <ari-tczew> surfzoid, are you trying to build changed by you package? or original package?
[14:23] <surfzoid> changed by me after calculate again the md5
[14:24] <surfzoid> ari-tczew: ^
[14:27] <surfzoid> ok
[14:27] <ari-tczew> it looks like you did change in orig tarball
[14:28] <ari-tczew> btw. why this is not .orig.tar.gz ?
[14:31] <surfzoid> ari-tczew: no clue ?
[14:32] <ari-tczew> surfzoid, do you want to update mono to 2.6.1 version?
[14:32] <ari-tczew> it would be nice to report bug @ bugs.debian.org
[14:32] <geser> surfzoid: where did you got this .dsc? the Files line looks broken
[14:33] <surfzoid> yes 2.6.1, i got it from 2.4 one
[14:33] <geser> you constructed this .dsc by hand?
[14:33] <ari-tczew> if you did all changes what are needs by 2.6.1, you must put "debuild -us -uc"
[14:34] <ari-tczew> if built will fine, get debuild -S
[14:34] <surfzoid> geser: i modify it by hand yes
[14:34] <ari-tczew> lol
[14:35] <surfzoid> !!
[14:36] <geser> why? why not used the tools intended for it?
[14:36] <surfzoid> hum, which one ?
[14:37] <surfzoid> geser: i m more rpm and just discover the deb world
[14:37] <ari-tczew> surfzoid, maybe you should read some articles on wiki.ubuntu.com ?
[14:37] <geser> debuild -S or dpkg-buildpackage -S
[14:38] <surfzoid> some gui exist for those command line tools ?
[14:40] <geser> I don't know any
[14:53] <surfzoid> finaly damed, the problem was only "-" rather "_" !!
[14:55] <ari-tczew> surfzoid, great, but please don't handly changing dsc file in future, just use debuild ;-D
[14:57] <surfzoid> yes now i know, the puzle sound like really more easy
[14:58] <surfzoid> in fact, if you have existing source, the only stuff is to change the log and debuild do all the stuf :-)
[15:18] <surfzoid> hum using the tool give me new error : http://pastebin.com/d52de1cc3
[15:19] <surfzoid> i did something wrong or foprget something ?
[15:21] <surfzoid> the funny is if i go in my source dir and do the autogen.sh all is okay
[15:21] <ari-tczew> myabe someone is wrong with debian/rules?
[15:21] <ari-tczew> maybe
[15:22] <ari-tczew> I guess you should add autoconf patch
[15:22] <surfzoid> hum where it is ?
[15:22] <ari-tczew> create folder, unpack there .orig.tar.gz
[15:22] <ari-tczew> and copy unpacked folder
[15:23] <surfzoid> where
[15:23] <ari-tczew> lol, are you in folder with mono, right?
[15:23] <ari-tczew> here is *.orig.tar.gz right?
[15:24] <surfzoid> yes
[15:25] <ari-tczew> so, for example please create folder, e.g. call it "diff", so put in console: mkdir diff
[15:25] <ari-tczew> then unpack *.orig.tar.gz with mono in diff folder
[15:26] <ari-tczew> if you have unpacked orig.tar.gz, please copy it, because you need 2 folders for compare
[15:27] <ari-tczew> in efects you should have in diff folder e.g. mono-2.6.1 and mono-2.6.1 (copy)
[15:27] <surfzoid> oki now i see better you would like i compare the 2 dir
[15:27] <ari-tczew> are you understand
[15:27] <ari-tczew> yes, compare two dirs
[15:28] <ari-tczew> in one dir you need to run command: autoconf
[15:28] <ari-tczew> then go back and compare these dirs
[15:28] <ari-tczew> cd .. && diff -pruN dir1 dir2 > autoconf.patch
[15:30] <surfzoid> sorry i said a mistake, i don't have an orig tarball
[15:30] <ari-tczew> just I saw in your pastebin
[15:31] <ari-tczew> ehh surfzoid, you must rename to .orig.tar.gz
[15:31] <ari-tczew> so, e.g.: mv mono_2.6.1.tar.gz mono_2.6.1.orig.tar.gz
[15:31] <surfzoid> ha oki
[15:33] <surfzoid> at the same time i see other posible mistake of the tool, my source dir is "mono-2.6.1" but the tool make an "mono_2.6.1.tar.gz" with inside "mono-2.6.1" so "_" vs "-" will make trouble ?
[15:33] <ari-tczew> source dir is ok
[15:34] <ari-tczew> continue work ...
[15:34] <surfzoid> if i rename to .orig.tar.gz i must change that also in the dsc file ?
[15:34] <ari-tczew> LOL don't change handly dsc file !
[15:34] <ari-tczew> dsc will change by debuild
[15:34] <ari-tczew> automatically
[15:35] <surfzoid> hum weird pointer :-)
[15:37] <adhorden> do not change the dsc by hand, use debuild
[15:38] <surfzoid> on a side debian is stric , really amazing stric, and it permit this lol
[15:45] <surfzoid> very long to build this 35 Mega of sources :D
[15:48] <surfzoid> ari-tczew: i have followed you by renaming to orig.tar.gz, but of course ! :
[15:48] <surfzoid> dpkg-source: error: cannot fstat file /usr/src/packages/SOURCES/mono_2.6.1.tar.gz: No such file or directory
[15:50] <surfzoid> it confuse me to have checsum of file name with only tar.gz, but use an orig.tar.gz rather
[16:02] <surfzoid> ari-tczew: oki, you was right, i know understand, renaming in ori.tar.gz, but lunch the tool in mono-2.6.1 dir, detect the new origi.tar.gz and adjust the dsc file :-)
[16:03] <ari-tczew> exactly
[16:03] <surfzoid> i just forget the step to rerun the tool :-)
[16:03] <ari-tczew> as you see themselve surfzoid, changing dsc file is no sense
[16:04] <ari-tczew> surfzoid, do you have patch autoconf ?
[16:05] <surfzoid> no yet, now i have clean many thing, i would like to check again before
[16:53] <directhex> oh lord
[16:53] <directhex> anyone uploads a new mono to ubuntu, heads will roll. FYI.
[16:54] <sebnerr> directhex: uhuhuhu \o/ .. what happened?
[16:54] <Laney> nobody would ever sponsor it
[16:55] <sebnerr> Laney: archive admin wise?
[16:57] <surfzoid>  directhex : you mean, a new release of mono is now available in ubuntu 9.10 ?
[16:57] <sebnerr> surfzoid: 9.10 is frozen and security upload only
[16:58] <surfzoid> sebnerr there isn't something like backport ?
[16:58] <sebnerr> surfzoid: yeah but hardly used (for mono)
[16:59] <directhex> anything with lots of rdepends is effectively blacklisted from being backported
[16:59] <directhex> things like new gcc releases or new python releases or new mono releases have too high a risk of breaking existing apps
[16:59] <joaopinto> directhex, you became afraid ? :)
[17:00] <surfzoid> yes, on other side you should upgrade one day :-)
[17:00] <sebnerr> directhex: what about the sponsoring stuff? No auto-sync for 2.4.3? I'll choose 2.6 though, poor meebey
[17:00] <surfzoid> 2.7
[17:00]  * Laney is confused
[17:00] <sebnerr> surfzoid: ?? there is no 2.7
[17:01] <surfzoid> sebnerr mono -V
[17:01] <surfzoid> Mono JIT compiler version 2.7 (
[17:01] <sebnerr> surfzoid: trunk then?
[17:01] <surfzoid> yep :-)
[17:02] <sebnerr> surfzoid: we're talking about ubuntu versions ;)
[17:02] <directhex> sebner, 2.4.3 should sync in at some point. but we're making changes to stuff which will cause breakage, and that transition really needs to be completed
[17:02] <sebnerr> Laney: what's no with that: No one will sponsor it?
[17:02] <directhex> sebner, i'd rather get it finished in debian then have the whole lot come into ubuntu in one go
[17:02] <sebnerr> directhex: ah the -cil stuff?
[17:02] <directhex> sebner, right
[17:02] <directhex> sebner, and getting rid of /usr/bin/csc
[17:03] <sebnerr> directhex: isn't everything with mono-csc already?
[17:03] <directhex> not everything.
[17:03] <sebnerr> kk
[17:03] <directhex> it all *needs* to be done though
[17:04] <sebnerr> directhex: I doubt meebey targets 2.6 for lucid?
[17:04] <directhex> i'm still waiting on meebey to give me the goahead to break stuff like gtk#
[17:04] <directhex> sebner, meebey intends to taregt 2.4.x for squeeze (march freeze) with 2.6 in experimental
[17:04] <sebnerr> so, ubuntu too. Ic
[17:04] <directhex> sebner, 2.4.x is upstream's LTS branch
[17:08] <directhex> surfzoid, 2.6 will likely appear in a PPA in january. probably
[17:08] <surfzoid> thanks, but i m trying now to build it at OBS :-)
[17:09] <surfzoid> i just have an compile error
[17:09] <sebnerr> directhex: does meebey already know what changes with 2.6? Anything important to mind?
[17:09] <directhex> sebner, 4.0 classlib
[17:10] <sebnerr> directhex: that means?
[17:10] <directhex> not sure yet. it means *something* though. new corlib, new compiler, etc
[17:10] <surfzoid> directhex: have you got few minutes to help : https://build.opensuse.org/package/show?package=Mono&project=home%3Asurfzoid%3ADebianUbuntu%3AMono    ?
[17:11] <surfzoid> please :-)
[17:13] <sebnerr> directhex: uhh, I smell another transition + breakage :P
[17:14] <directhex> sebner, if everything uses mono-devel and -cil-dev packages, then it should be rebuild-only
[17:14] <directhex> surfzoid, looks like your .install files need massaging. there's only 99 of them to tweak. chop chop.
[17:14] <sebnerr> directhex: heh, we'll see
[17:14] <directhex> dh_install: libmono-c5-1.0-cil missing files (debian/tmp/usr/lib/mono/gac/Mono.C5/1.0.*/), aborting
[17:16] <surfzoid> directhex: the build of the deb is different of ./autogen.sh && make && make install ??
[17:18] <surfzoid> directhex: you mean, i need to change all the 99 files one by one, ?
[17:20] <surfzoid> the problem is more here , no : ERROR: ld.so: object 'libfakeroot-sysv.so' from LD_PRELOAD cannot be preloaded: ignored.
[17:20] <directhex> surfzoid, you certainly need to change libmono-c5-1.0-cil.install since that's where it's bailing out
[17:20] <directhex> surfzoid, no, libfakeroot messages aren't real errors & should be ignored.
[17:20] <surfzoid> and the .so missing is not so important ?
[17:20] <surfzoid> oki
[17:21] <surfzoid> directhex: libmono-c5-1.0-cil.install is a file generated or provided by mono source ?
[17:22] <directhex> surfzoid, it's in debian/ along with 188 other files/folders which make up the mono source package
[17:24] <directhex> closer to 229 including patches etc
[17:26] <surfzoid> directhex: not sur, but, in Mono2.6 the Net1.0 stuff was dropped ?
[17:32] <directhex> i thought that was happening in 2.8 not 2.6
[17:32] <directhex> but i could be wrong
[17:33] <surfzoid> directhex: in fact i m complety sure it is dropped in 2.7
[17:33] <sebnerr> directhex: sounds familiar
[17:33] <surfzoid> i had the problem last week with the trunk version
[18:18] <bjsnider> siretart, ping
[18:39] <cratylus> is there a place, either in ubuntu or debian where one can filter the list of packages to see which source format their in (either command line or on the web somewhere). i'm trying to find examples of 3.0 (quilt) formatted packages to study
[18:59] <MTecknology> cratylus: now there's different formats I need to learn? :(
[19:01] <cratylus> MTecknology, tell me about it. apparently there's a new craze every now and then
[19:01] <cratylus> you don't HAVE to change formats as the others are supported, though
[19:02] <MTecknology> cratylus: I'm just learning basics when I have a little spare time; I'll get it eventually
[19:03] <cratylus> MTecknology, i'm in the same boat right now. so many docs to read!
[19:09] <joaopinto> I coudn't find much documentation about debsrcr3.0 either, the best resource I could find was man dpkg-source
[19:11] <cratylus> joaopinto, yep, i'm basically using that and Hertzog's doc. along with apt-get source for such packages whose debian/source/format file has "3.0 (quilt)" as it's content
[19:11] <cratylus> found a few so far
[19:16] <crimsun> I remember there are some posts on planet Debian about it
[19:17] <crimsun> a few people have blogged about "converting" to it
[19:29] <cratylus> it's still just getting started with 466 packages to date: http://upsilon.cc/~zack/stuff/dpkg-v3/
[20:09] <cratylus> i think i found the answer to my earlier question about seeing which packages have that format. seems the ultimate debian database has a format field one can query: http://udd.debian.org/schema/udd.html#public.view.all-sources
[20:16] <tritium> I'm trying to use requestsync to request the syncing of ng-spice-rework (20-1) from Debian testing.  I'm sshed into my server, performed the manage-credentials step, but am now geting an error "Could not find cookie file for Launchpad...", and so on.  Must I ssh -X and run firefox graphically to complete the requestsync?
[20:17] <ScottK> tritium: Or use the email option
[20:17] <ScottK> tritium: Or copy the cookie from another box
[20:19] <tritium> ScottK: the email option, meaning don't use the "--lp" switch?  I've tried that.
[20:20] <ScottK> Yes.  That shouldn't need the cookie
[20:20] <geser> tritium: which ubuntu-dev-tools version do you have installed on your server?
[20:21] <tritium> geser: 0.72, on a jaunty box
[20:27] <tritium> geser: any ideas?
[20:27] <geser> looking at the code from this version
[20:27] <tritium> Thanks.
[20:29] <tritium> Let me try copying ~/.cache/lp_credentials/ubuntu-dev-tools-write_public.txt to ~/.lpcookie.txt.
[20:29] <geser> this version still used the firefox cookie at some places
[20:31] <tritium> Well, I can wait until I get home in January.
[20:32] <geser> .lpcookie.txt is the LP cookie from firefox
[20:33] <tritium> No luck with that.
[20:33] <geser> if it doesn't exist, it tries to find it in cookies.sqlite or cookies.txt from firefox
[20:34] <geser> try copying it from your desktop and placing in a location matching ~/.mozilla/*/*/cookies.sqlite
[20:35] <geser> requestsync (or more precisely a module from u-d-t) should extract it from there and store it in ~/.lpcookie.txt for future use
[20:37] <tritium> Try copying ~/.cache/lp_credentials/ubuntu-dev-tools-write_public.txt to ~/.mozilla/*/*/cookies.sqlite?
[20:38] <geser> no, your firefox cookie database
[20:39] <geser> scp ~/.mozilla/*/*/cookie.sqlite server:~/.mozilla/foo/bar/cookies.sqlite
[20:39] <tritium> Oh, I see.  Well, I'm on my wife's MacBook.  Let me see if that works.
[20:41] <geser> or wherever the firefox cookie database is for you
[20:41] <tritium> geser: perhaps I'll just file a bug on Launchpad, following https://wiki.ubuntu.com/SyncRequestProcess.
[20:42] <tritium> I appreciate your help trying to get it working.
[20:42] <geser> that's also a way (if it's easier for you)
[20:46] <tritium> OK, I'm getting somewhere.  Now it's not complaining about the cookie, just about $DEBEMAIL.
[20:46] <geser> export DEBEMAIL="your@mail.address"
[20:46] <tritium> yep, thanks
[20:47] <tritium> It appears to possibly be working...
[20:50] <tritium> except that my gnupg key is on my desktop, whichs is turned off, not this server
[20:50] <tritium> Oh well, thanks for your help!
[20:51] <tritium> Have a good day, geser.
[20:51] <geser> have you tried "requestsync --lp ..." to file it directly into LP and not mail it?
[20:52] <tritium> Earlier, but not since fixing the cookie issue.  Let me try again.  Thanks for the reminder.
[20:53] <tritium> Sweet!  Thanks, geser.
[20:54] <tritium> Filed as bug 498871
[20:54] <crimsun> geser: thanks for fixing requestsync
[20:55] <tritium> Sweet tool!
[20:55] <tritium> Hello, crimsun.
[20:57] <crimsun> hi, tritium
[20:58] <tritium> crimsun: I'm out here in your neck of the woods, enjoying all this snow.
[20:59] <crimsun> ah, whereabouts?
[21:00] <tritium> Loudon County, VA
[21:00] <tritium> ~15 minutes from Dulles airport.
[21:01] <crimsun> ouch
[21:01] <crimsun> yeah, it has been pretty nice
[21:01] <crimsun> I'm in town until Christmas Day (on assignment afterward)
[21:02] <tritium> Ah, really?
[21:02] <tritium> Are you far from the 20152 zip code?
[21:02] <crimsun> I'm [living] in DC presently
[21:03] <tritium> Ah, ok.  I knew you were in the general area.
[21:13] <bddebian> Hey wait, crimsun is crimsun again?
[21:13] <ScottK> Apparently
[21:13] <ScottK> tritium: I'm kind of NW of DC and west of Baltimore.  Not so far away either.
[21:14] <tritium> ScottK: wow!  :)
[21:16] <tritium> ScottK: snowed in?
[21:16] <ScottK> Yep.
[21:16] <ScottK> Driveway is shoveled, but the street isn't plowed yet.
[21:16] <ScottK> I've heard the plows on the nearest main road, so there's hope.
[21:16] <tritium> We arrived from NM just in time on Thursday night (early Friday morning, technically).
[21:17] <tritium> I did a fair amount of shoveling this morning.
[21:17] <tritium> Hey there, bddebian!
[21:17]  * ScottK is waiting for the Ibuprofen to kick in.
[21:18] <tritium> What ails you?
[21:18] <ScottK> Back pain from the shovelling.
[21:19] <tritium> Ah, but of course.
[21:21] <crimsun> a few people from my complex cleared our street
[21:21] <crimsun> I feel like an old man now
[21:27] <bddebian> Hi tritium
[21:28] <bddebian> Pfft, you guys don't know the meaning of old.. :)
[21:28] <crimsun> does anyone else see abysmal response time for rmadison -uubuntu queries?
[21:28] <crimsun> bah, and as soon as I say that, it returns immediately
[21:29] <bddebian> heh
[21:30] <ScottK> crimsun: Routinetly
[21:32]  * dhillon-v10 says UBUNTU IS AWESOME, especially PPA's
[21:32] <ScottK> dhillon-v10: PPAs aren't Ubuntu
[21:32] <dhillon-v10> ScottK, lol, but the build process it sooo easy
[21:33] <dhillon-v10> ScottK, and people can easily install .deb
[21:33] <ScottK> Yes, but those aren't part of Ubuntu.
[21:33] <ScottK> They are built ON Ubuntu, but not part of it.
[21:33] <dhillon-v10> ScottK, okay :D that was very precise
[21:34] <dhillon-v10> ScottK, hey I know you, you are that person who made merge-o-matic website right
[21:34] <ScottK> Nope.
[21:34] <ScottK> That was Keybuk
[21:34] <dhillon-v10> ScottK, ahh, I saw your last name so :D
[21:34] <dhillon-v10> * irc nick
[21:39] <dhillon-v10> ScottK, hey what happens to a package that has symlinks. Does it build differently from others or is it just rejected from the build queue
[21:39] <crimsun> what do you mean by "has symlinks"?
[21:41] <tritium> Daddy duty calls.  Talk to you later!
[21:42] <crimsun> bye
[21:49] <quidnunc> Is there a way to look up the information for a given GPG key ID?
[21:49] <crimsun> as in "use a keyserver"?
[21:49] <LLStarks> why is adobe-flashplugin used for restricted extras instead of flashplugin-installer?
[21:50] <crimsun> because it's the blessed package.
[21:50] <quidnunc> crimsun: Sorry? I assume it is listed on keyserver.ubuntu.com but I don't know how to go from key ID -> metainfo
[21:51] <crimsun> quidnunc: depending if you've imported it locally, you can query using gnupg
[21:51] <geser> quidnunc: what kind of meta-info are you looking for?
[21:51] <quidnunc> geser: I want to know who it belongs to.
[21:52] <quidnunc> crimsun: I'm trying to decide whether I should import it. The first question was, "Who's is it".
[21:52] <geser> quidnunc: either import the key into your keyring or use the web-interface of some keyservers, e.g. http://pgpkeys.pca.dfn.de/
[21:52] <geser> many other keyservers have a web interface too
[21:53] <quidnunc> keyserver.ubuntu.com does not seem to.
[21:53] <geser> yes, it does too (if you know the port)
[21:53] <geser> http://keyserver.ubuntu.com:11371/
[21:54] <quidnunc> geser: thanks
[21:55] <quidnunc> geser: Can you search by key ID? I'm not getting any results.
[21:55] <geser> sure, I does it regularly, prefix it with "0x"
[21:56] <quidnunc> geser: Thanks that worked.
[21:57] <quidnunc> The info for my key is blank. What is the policy for signing sources uploaded to archive.ubuntu.com?
[21:58] <geser> your gpg key must be attached to your LP account
[21:59] <quidnunc> geser: How can I find that out for 21B2133D?
[22:00] <geser> open your LP page and look at the "OpenPGP keys" field
[22:03] <quidnunc> geser: That's for my keys. This is not my key.
[22:03] <geser> ah
[22:04] <quidnunc> Anyway, never mind. I'm not going to import it into my keyring. I'll trust the integrity.
[22:05] <Laney> I just googled for "ubuntu keyserver" and there it was
[22:05] <Laney> oh you alredy got it :)
[22:05] <ajmitch> actually searching on google for 'gpg 21B2133D' showed me whose key it is
[22:07] <quidnunc> ajmitch: Does it? Maybe I don't understand how to read that page. Is it Steve's?
[22:07] <ajmitch> yes, it looks to be a subkey of his
[22:08] <quidnunc> ajmitch: Alright thanks.
[22:08] <geser> quidnunc: you can also look at the signature a key has and decide on the amount of signatures, signatures from "trusted" persons, etc. if you trust this key or not
[22:11] <geser> from a LP point-of-view any dev could create new gpg key (without any other signatures besides the self-signature), attach it to his LP account and use this key for signing uploads
[22:11] <David-T> um.... anyone could create any number of keys and sign their own key with them... amount of signatures is not a very useful indicator
[22:12] <wgrant> David-T: Right, you need to trust the signatures. That's the OpenPGP trust model.
[22:38] <dhillon-v10> guys I have a real quick question: https://bugs.launchpad.net/ubuntu/+bug/486903 there is already a .deb on the bluej website so what should I do there
[22:39] <RAOF> dhillon-v10: Check out their source package; it may be a good start.
[22:40] <dhillon-v10> RAOF, so what happens to the bug report, should I package it again from the source and make a new .deb for ubunut
[22:40] <siretart> bjsnider: really short pong
[22:41] <RAOF> dhillon-v10: You can't upload binary packages to Ubuntu, so unless they _also_ have a source package for download (this is not the same as their program source), you'll need to package it independently.
[22:41] <dhillon-v10> RAOF, alright thanks so this would just be another regular package rihgt
[22:41] <dhillon-v10> *right
[22:41] <RAOF> dhillon-v10: Or, contact them & collaborate on brining their source package up to archive standards; it's almost certainly going to be missing some policy nicities.
[22:42] <RAOF> Yes.  It's going to be just a regular package.
[22:42] <dhillon-v10> RAOF, thanks :D
[22:45] <dhillon-v10> RAOF, alright so what happens after the I package, where should I upload it ? REVU ?
[22:49] <bjsnider> siretart, have yet another question about mplayer. somebody wrote me asking if it could play wmapro files. should the karmic version be able to?
[23:24] <jcastro> RAOF: ping!