[00:18] <Ademan> is there a reasonable way (maybe through dbus) 1. when the screensaver goes active/the screen is locked and 2. when the user is prompted for their password? (I want to run some intense stuff during idle time, and disable it as soon as the user is prompted for their password, as it causes significant keyboard latency)
[00:25] <Ademan> Hrm  AuthenticationRequestBegin exists, but only on org.gnome.ScreenSaver, is there no freedesktop interface?
[01:44] <c_korn> how can I tell ant to take openjdk-7-jdk for compiling (which I installed) and not to use openjdk-6 (JAVA_HOME=usr/lib/jvm/java-6-openjdk-i386/jre).
[01:53] <c_korn> ok, need to build-conflict on openjdk-6-jre-lib
[07:29] <spec4d> I'm trying to get involved with Ubuntu development. Is there anything I should be reading to get started besides this wiki? http://packaging.ubuntu.com/html/
[07:54] <Noskcaj> spec4d, depends on how you want to help
[07:55] <Noskcaj> That's just packaging, and it's not particularly complete
[08:31] <spec4d> well I've been trying to fix a bug with Ubuntu Software Center, but I can't even get that to compile for me to test the patch I wrote. I'm not really tied to any piece of software or project in Ubuntu at the moment. I'm just trying to get used to the process and contibute.
[08:40] <Noskcaj> ok. A few questions. 1. what bug? 2. what version of ubuntu are you one? 3. Are there any specific packages you'd like to help with?
[08:41] <spec4d> https://bugs.launchpad.net/ubuntu/+source/software-center/+bug/1107824
[08:41] <spec4d> ^easy stuff, but like I said I'm more concerned with just learning the process (for the moment)
[08:41] <spec4d> I'm on 13.10
[08:42] <darkxst> spec4d, how are you building the USC package?
[08:43] <darkxst> also development of patches etc, should be done against the current devel series (i.e trusty)
[08:43] <spec4d> of course :)
[08:45] <spec4d> I've been trying to follow this. I got as far as the "testing the fix" section, but I don't know enough about USC bzr, pbuilder and dpkg to get it to compile. http://packaging.ubuntu.com/html/fixing-a-bug-example.html
[08:46] <spec4d> I tried following the sources readme and that did not help either
[08:47] <Noskcaj> Use "pbuilder-dist trusty amd64 create" to make a schroot, the "debuild -S" and "pbuilder-dist trusty amd64 build" to build it
[08:49] <spec4d> Thanks I'll look into that. I'm used to using vbox in windows development, but I don't have that much experience with chroots.
[08:50] <spec4d> The funny thing about programming is that the first part of the learning curve always looks like a cliff :)
[08:50] <spec4d> But I have a CS degree so I'm used to that
[08:50] <Noskcaj> spec4d, in the most basic form, a chroot is a temporary VM for building stuff in. one command and then it works then removes itself
[08:51] <Noskcaj> and you're right. That's sorta why i still don't know any actual programming languages
[08:52] <spec4d> I geuss I know what you mean. I don't know python, but that didn't stop me from writing this patch. lol
[09:04] <darkxst> Noskcaj, don't spread lies :) a chroot is nothing like a VM
[09:05] <Noskcaj> darkxst, it's still a decent explaination
[09:06] <spec4d> Lol. I installed Crouton once on a chromebook so I already know the diff
[09:06] <darkxst> and pbuilder is not really your typical chroot
[09:06] <spec4d> But that was my only real experience with it
[09:09] <Noskcaj> for -weather:  many icons are under a non-DFSG-compliant license
[09:09] <Noskcaj> woops, wrong channel
[09:09] <Noskcaj> darkxst, ^
[09:13] <darkxst> Noskcaj, what license?
[09:16] <Noskcaj> darkxst, I'll look into it tomorrow, that was just my reply from debian
[09:41] <spec4d> dpkg-source: error: aborting due to unexpected upstream changes, see /tmp/software-center_13.05-0ubuntu4.diff.8WQK7Z
[09:42] <spec4d> ??? Does that mean the source on my machine isn't latest
[09:49] <darkxst> spec4d, that means the .orig tarball is probably messed up
[10:04] <spec4d> I think what happened is BZR branched the 13.10 source instead of 14.04 and it's complaining about it not being latest. Does that make any sense?
[10:21] <spec4d> Wait. Where am I supoused to grab source from. "bzr branch ubuntu:software-center" gives me an out of date copy. Should I be grabbing it using " bzr branch lp:software-center"
[10:21] <spec4d> ?
[10:40] <infinity> spec4d: If the Ubuntu branch is out of sync with the archive, what you want is "pull-lp-source software-center"
[10:40] <infinity> Since the archive is authoritative.
[11:00] <spec4d> Thanks infinity. That looks like it will work.
[18:44] <Logan_> Hi Jackson.
[19:16] <Noskcaj> oh, hey Logan_
[19:16] <Noskcaj> i really need to pay more attention to irc
[19:16] <Logan_> Or be pinged by "Jackson."
[19:16] <Logan_> Because I often ping people with their real names. Just to be anarchist or something.
[19:18] <Noskcaj> fixed
[19:19] <Unit193> Logan_: Ping me? ;)
[19:20] <Logan_> Hi Unit. :P
[19:20] <Unit193> Eww.
[20:04] <LBo> I'm creating a package  (my first). The program that I'm packaging creates two (empty) files on runtime. These files are not included in the source. I would like them to be installed with the package so the two files get removed when the package does
[20:04] <LBo> I could add two `touch` commands in debian/rules
[20:05] <LBo> Or I could add an extra patch to debian/patches which creates the two empty files
[20:05] <Noskcaj> LBo, You can use a postrm script to make that unnecessary, or maybe make a blank file the us dh_install to put it where it's needed
[20:06] <LBo> Noskcaj: where should I store those blank files?
[20:06] <LBo> Is there a directory in debian/ where I can store such files?
[20:06] <Noskcaj> debian/FILENAME
[20:07] <Noskcaj> Although a postrm is probably the best solution
[20:07] <LBo> ok
[20:07] <LBo> And then use packagename.install to copy them to the right location?
[20:07] <LBo> debian/packagename.install
[20:08] <infinity> postrm is the right place to remove them.
[20:08] <infinity> If they're generated at runtime, that is.
[20:08] <infinity> They shouldn't be included or installed in the package at all.
[20:09] <infinity> LBo: Also, what are these files?
[20:09] <infinity> If they're being written, but in a read-only location (ie: anywhere in /usr), there's still something very wrong happening.
[20:09] <LBo> infinity: It's a config file that is not included with the source but the program makes an empty file the first time it is ran
[20:09] <infinity> So, it's in /etc?
[20:10] <LBo> Yes
[20:10] <infinity> You might want to ship a sane skeleton file, then.
[20:10] <LBo> Yeah, that seems nice
[20:10] <LBo> With some comments in it and an example
[20:11] <LBo> I can store the skeleton file in debian/?
[20:11] <infinity> For bonus points, I'd also patch out the part of the upstream source that thinks it's a good idea to write to /etc at runtime.
[20:11] <LBo> OK
[20:11] <infinity> Yeah, you can toss it in debian/foo.conf.example or something, and then install it.
[20:11] <LBo> infinity: awesome, thanks
[21:17] <arun> guys is this command correct sudo apt-ftparchive packages main | gzip -9c > dists/quantal/restricted/binary-i386/Packages.gz  ??
[21:32] <xnox> arun: sudo is lost at pipe, and you are indexing /main/ directory and then call the result /restricted/
[21:32] <arun> xnox: oh thank dude. I fixed it xD
[22:47] <LBo> I'm having some troubles when building a source package from my package (https://github.com/LeonB/linux-malware-detect/tree/master)
[22:47] <LBo> Building the binary works fine
[22:48] <LBo> When I build the source package I get error messages when applying the debian/patches/
[22:50] <LBo> These are the messages I get: http://paste.ubuntu.com/6864226/
[22:51] <LBo> I've got a hunch the patches get applied twice?
[22:56] <darkxst> LBo, looks like you need to refresh the patch, patches with 'fuzz' are not allowed.
[22:56] <LBo> OK. What is fuzz?
[22:57] <darkxst> it is basically telling you the hunk was applied, but patch is not sure that its correct
[23:01] <jtaylor> LBo: are the patches accidentally applied in the orig tarball=
[23:04] <LBo> jtaylor: could be that the error is in that direction
[23:04] <LBo> I'm building from a git repository and not a tarball
[23:04] <jtaylor> or its just a different snapshot
[23:05] <jtaylor> its a bit weird it partially applies
[23:07] <LBo> jtaylor: I cloned the repository from github in another directory and now it worked...
[23:08] <LBo> So some kind of crap I did with my local repo I think
[23:15] <LBo> jtaylor: Jay, it worked! https://launchpad.net/~leon-tim-online/+archive/linux-malware-detect
[23:15] <LBo> Thanks!
[23:41] <mwhudson> uh, is there a good reason for me having a file /etc/modprobe.d/intel_11n_disable.conf ?
[23:41] <lifeless> n being broken?
[23:41] <lifeless> it might not be anymore, but it was for a while
[23:42] <RAOF> For what it's worth, I *don't* have that blacklist on trusty.
[23:43] <mwhudson> yeah, i'm sort of hoping that it was created when i installed quantal or whatever version i first installed
[23:43] <mwhudson> i hope it isn't broken now because my internet is now faster than g :)
[23:44] <mwhudson> (is there some way i can tell which version i installed vs. upgrades?)
[23:47] <mwhudson> hm, probably oneiric
[23:52] <TJ-> mwhudson: Yes, you likely created to work around the Intel iwl4965 802.11n suffering lots of dropped packets
[23:52] <RAOF> mwhudson: Yes, there's clearly some way, because apport has originally-installed-release data.
[23:55] <RAOF> mwhudson: Also, that file doesn't appear in any supported Ubuntu release. Presumably we failed to remove it on upgrade at some point.
[23:56] <mwhudson> RAOF: i may have created it myself at some point i suppose
[23:56] <mwhudson> have no recollection of that though
[23:56] <RAOF> Plausibly.
[23:56] <RAOF> Anyway, enjoy your order of magnitude more wireless bandwidth!