[06:56] <ScottK> Ah.  So now we have an entire team dedicated to shoving Ubuntu Tweak into the archive.
[06:56] <micahg> ScottK: huh?
[06:57] <ScottK> http://ubuntumug.wordpress.com/2011/05/27/ubuntu-power-users-first-meeting/
[06:57] <ScottK> Apparently 'power user' turned out to be a synonym for, well I can't find a CoC compliant way to put what I think it's a synonym for with any specificity.
[06:58] <micahg> lol
[06:58]  * ScottK is glad tumbleweed took over reporting MOTU status for the release team.
[06:58] <micahg> orly, cool
[06:58] <ScottK> tumbleweed: Welcome.
[06:58] <ScottK> Yeah.
[06:58] <ScottK> He and Laney are on ubuntu-release now.
[08:45] <blackmoon-105> hi, in a -dev package there are only a .h file, or also binary files? (.a, .la, .so)
[08:51]  * tumbleweed gets home. Took an extended post-UDS UK detour
[08:57] <blackmoon-105> no one?
[08:57] <tumbleweed> http://www.netfort.gr.jp/~dancer/column/libpkg-guide/libpkg-guide.html
[08:57] <jmarsden> blackmoon-105: Binaries too... but why don't you try looking at one to find out?   dpkg -L glib2.0-dev    for example
[08:58] <tumbleweed> blackmoon-105: ^
[08:58] <tumbleweed> blackmoon-105: it's common to have .a files in -dev, and possibly .la, but please try to avoid .la in new packages
[09:02] <blackmoon-105> jmarsden: i've look in some packages and sometimes i've fount it and sometimes not. this is the reason because i've asked
[09:02] <blackmoon-105> tumbleweed: thanks for the link
[09:04] <tumbleweed> blackmoon-105: it's out of date, but still informative
[09:05] <blackmoon-105> tumbleweed: i'm re-package libopensc and i don't know if i must include the .la, .a, .so files in the -dev package or in the lib package
[09:07] <tumbleweed> blackmoon-105: see also this thread: http://lists.debian.org/debian-devel/2011/05/msg01003.html
[09:08] <blackmoon-105> tumbleweed: ok, thanks
[09:51] <evaluate> micahg, ping?
[09:54] <evaluate> micahg, I was curios as to what the status of #702316 was. I noticed you merged 1.4.0 from Debian, but the patch for natty hasn't yet been applied.
[18:30] <blackmoon-105> hi, i've made an updated opensc (0.12.10) deb package, available on my launchpad repo. there is a way for include it in a ubuntu repostories?
[18:31] <stlsaint> blackmoon-105: your package must get sponsored
[18:32] <stlsaint> blackmoon-105: https://wiki.ubuntu.com/SponsorshipProcess
[18:33] <tumbleweed> but more to the point, opensc is maintained in debian, we just modify the version we get from them, and we generally try to avoid unecessary diversion from debian
[18:33] <tumbleweed> have you spoken to the maintainer of the package in debian, to see if he needs / wants help with it?
[18:35] <stlsaint> blackmoon-105: ah yea you dont want to go messing with another maintainers package especially if its being maintained in debian
[18:36] <tumbleweed> well, we don't have maintainers in ubuntu, you can touch anything (although we ask the right people when possible)
[18:37] <stlsaint> tumbleweed: gotcha
[18:37] <tumbleweed> but we still try not to diverge from debian where possible. We don't have the manpower to maintain unecessary differences
[18:37] <blackmoon-105> stlsaint: the package is already in debian, but the software version is not updated with the version on opensc website
[18:38] <tumbleweed> blackmoon-105: and is there a particular reason why we need this new release now?
[18:39] <blackmoon-105> yes bacaus the latest version 0.12.x is the only version which can do working my smart card reader
[18:39] <tumbleweed> that sounds like a good reason to do something about it :) I still suggest poking the debian maintainer first, though
[18:40] <blackmoon-105> this smart card reader is used in italy for read the healt card
[18:40] <blackmoon-105> *health
[18:41] <blackmoon-105> tumbleweed: ok i'll try to send an email to the debian maintainer
[18:42] <broder> blackmoon-105: better would be filing a bug with the debian maintainer
[18:43] <blackmoon-105> debian have a bug page as here in launchpad?
[18:43] <blackmoon-105> broder: ^
[18:43] <broder> blackmoon-105: no, they use their own bugtracker
[18:43] <broder> https://bugs.debian.org
[18:44] <broder> but the easiest way to use it is to install reportbug
[18:44] <blackmoon-105> broder: ok, thank you
[20:40] <hrw> Laney, persia: can 'revu uploaders' group be dropped finally? it is listed as 'no longer necessary' but each 'ubuntu contributor' becames member of it.
[22:55] <stlsaint> im having a issue setting up apt-cacher-ng
[22:58] <jtaylor> what kind of issue?
[22:59] <stlsaint> jtaylor: i believe i have correctly configured but when i hit the import button on localhost:3142 it says no index file found
[22:59] <stlsaint> No index files detected. Unable to continue, cannot map files to internal locations.
[22:59] <jtaylor> to import at least one client must have updated
[23:00] <stlsaint> so i would need to configure my pbuilder to use apt-cacher-ng then update
[23:00] <jtaylor> or use your local machine
[23:00] <stlsaint> ah kk
[23:00] <jtaylor> -o Acquire::html::proxy=...
[23:02] <stlsaint> jtaylor: is there something specific i must do to pbuilders to use cache?
[23:03] <jtaylor> pbuilder has the --http-proxy option
[23:03] <stlsaint> i mean are they treated like clients and i must add the -hhtp command
[23:03] <jtaylor> or use the http_proxy env variable
[23:03] <jtaylor> the later is required for cowbuilder
[23:03] <stlsaint> kk, thats what i meant, ok sounds good, i will give it a go
[23:03] <jtaylor> or if you want it permantently for the rc
[23:07] <stlsaint> is it safe to move the pbuilderrc to /home/username/.pbuilderrc cause im tired of seeing the error that there is no .pbuilderrc everytime i run
[23:07] <jtaylor> should be no problem
[23:11] <stlsaint> wow so it seems i have no ~/.pbuilderrc
[23:11] <stlsaint> really im just upset at not knowing where it is
[23:21] <geser> pbuilder caches the downloaded debs by default, but I use apt-cacher-ng to have a common cache for my pbuilder and my normal system
[23:21] <stlsaint> geser: yea i noticed that as i was reading more and more
[23:23] <jtaylor> its also useful to cache for VM's
[23:25] <geser> I also had to use a proxy for my pbuilder as I use tmpfs for buildspace and pbuilder uses hard-links to get it's cache into the build environment which doesn't work cross-partition
[23:25] <stlsaint> will the apt-cacher-ng/_import folder automatically update as new packages go into the archives folder?
[23:26] <jtaylor> it will delete the packages it adds to the archive from the import folder
[23:26] <geser> I disabled the pbuilder cache as apt-cacher-ng does the caching already (no need to cache it twice)
[23:27] <geser> (using apt-cacher-ng as http_proxy in pbuilder)
[23:44] <stlsaint> jtaylor: question: i just made a new pbuilder for karmic, since it had to get new packages will those be added to apt-cacher-ng/_import folder or will i have to do manually?
[23:54] <stlsaint> exit