[00:08] <ESphynx> Could this be turned on by default if running on nVidia hardware or something?
[00:09] <RAOF> Maybe.
[00:09] <RAOF> It's probably a performance drain, though.
[00:13] <ESphynx> RAOF: I'd rather have my text editor working at 60 frames a second than being unusable at 120 frames / second
[00:14] <RAOF> Yeah, but this doesn't apply to just your text editor :/
[00:14] <ESphynx> RAOF: It applies to all programs I run on this sytem.
[00:15] <ESphynx> i.e. on all systems using nVidia drivers, which is probably at least half of what I consider a usable machine
[00:15] <ESphynx> I'm all for a proper fix, but until then this ought to be enabled.
[02:52] <ESphynx> after the last dist-upgrade, I can't login with Gnome Flashback (No effects) anymore :S all black
[02:53] <ESphynx> or if installing ccsm could do that :S (Saucy)
[02:54] <jbicha> ESphynx: I believe that's bug 1217991
[02:55] <ESphynx> thanks jbicha...
[02:55] <ESphynx> and what I thought was a workaround isn't working half the time for my update bug
[02:58] <ESphynx> So the only DE that actually was usable for me is now b0rked.
[03:00] <jbicha> ESphynx: the bug description has an easy workaround but the bug will be fixed soon
[03:00] <ESphynx> jbicha: k. thanks. I really wish this Compiz bug was fixed though :S
[03:01] <ESphynx> then I could try to figure out what's up with my other resizing/maximizing bug in Unity :P
[03:02] <stgraber> jbicha: the fix is wrong, those session names don't exist
[03:03] <stgraber> jbicha: so I'll need to actually figure out what's wrong with flashback running under upstart before I can get it fixed. I'll try to take a look tomorrow.
[03:04] <ESphynx> stgraber: The fix works for me.
[03:04] <ESphynx> renaming the 2 to -flashback rather than -fallback
[03:06] <stgraber> ESphynx: sure it does, it's just not a fix
[03:06] <stgraber> ESphynx: renaming the entries is the exact same as removing them
[03:06] <stgraber> which means, disabling the feature
[03:07] <stgraber> what we want is for the feature to be enabled and working and for that upstart-xsession is perfectly correct, it's just something else down the line that's failing and needs debugging and fixing
[03:07] <jbicha> stgraber: thanks
[03:07] <ESphynx> But Gnome fallback is what seems to start for me?
[03:08] <stgraber> sure, just not under upstart
[03:08] <ESphynx> ah ok
[03:09] <stgraber> jbicha: I know it used to work but I probably tested this before the whole flashback rename. It looks like something is confused by the names not being consistent, but it's not obvious what since it's not hardcoded in any of the places I'd have expected. Anyway, should take me a few minutes to figure out and fix once I reproduce the problem here (won't do that just now but will do it first thing tomorrow).
[03:11] <ESphynx> thanks stgraber
[03:34] <Mirv> mitya57: thanks! I agree quickcontrols is needed / very useful to have.
[03:44] <superm1> Laney: i just noticed that you had done a few uploads to mythtv without pushing the changes upstream or pull requests to the packaging branch so they just got clobbered in my upload, can you please forward the patch upstream and do pull requests if you'll be uploading in the future?
[04:04] <smoser> anyone know where files listed at the end of https://i148673231.restricted.launchpadlibrarian.net/148673231/asobibi-installer-log-2013.08.29.txt?token=a6a5ce59d6d6f063bd4bf36e1805942a come from ?
[04:04] <smoser> /usr/lib/finish-install.d/60cleanup
[04:04] <smoser> /usr/lib/finish-install.d/90base-installer
[04:04] <smoser> /usr/lib/finish-install.d/10open-iscsi
[04:09] <infinity> smoser: base-installer and open-iscsi...
[04:10] <infinity> smoser: And.. Not sure where 60cleanup comes from, off the top of my head.
[04:11] <infinity> smoser: Oh, finish-install, oddly enough. :P
[04:12] <smoser> yeah. that was funny. i realized that too
[04:12] <smoser> thanks infinity . kind of hoped no one would see my question. with the answer so clearly there :)
[04:35] <pitti> Good morning
[04:35] <pitti> tyhicks: thanks for fixing the d-bus stderr issue!
[04:35] <tyhicks> pitti: no problem! :)
[04:36] <pitti> and bluez et al are happy
[04:40] <sarnold> \o/
[06:14] <FourDollars> There is no Patch Pilot now. :(
[06:57] <infinity> tvoss: Yo, WTF mate.
[06:57] <tvoss> infinity, ?
[06:57] <infinity> tvoss: Why is location-service pulling in some ruby doc generation business?
[06:57] <tvoss> infinity, we can get rid of that :)
[06:57] <tvoss> infinity, want me to do that?
[06:57] <infinity> tvoss: That seems like an odd choice for a Canonical project. :P
[06:57] <tvoss> infinity, heritage, will fix it. hang on
[06:57] <infinity> tvoss: If you can make with the getting rid of somehow, sure.
[06:58] <infinity> tvoss: Beats doing MIRs for a few dozen ruby gems.
[06:58] <tvoss> infinity, indeed ;) sorry for the confusion
[08:01] <Laney> superm1: I certainly did forward the logind patch
[08:01] <Laney> might have missed the packaging branch though, sorry
[08:07] <debfx> Whoopie: I've uploaded a new virtualbox package with your vnc extension patch
[09:14] <xnox> FourDollars: sup? need sponsoring? =)
[09:16] <FourDollars> xnox: Yes. https://bugs.launchpad.net/ubuntu/+source/pristine-tar/+bug/1218197
[09:17] <ESphynx> xnox: can we get 0.44.09 in next week since it's mostly a bugfix release? ;) I'm going to require some sleep at some point :(
[09:18] <ESphynx> xnox: The big thing about this release is fixing real annoyances/usability issues with Ubuntu & Mint's DEs :P
[09:18] <asac> ogra_: what happened to the builds? floodgating worked it seems :)
[09:18] <xnox> FourDollars: you do want to subscribe "~ubuntu-sponsors"  https://wiki.ubuntu.com/SponsorshipProcess such that it gets on the list to sponsor: http://reqorts.qa.ubuntu.com/reports/sponsoring/
[09:18] <asac> ogra_: err... moving to touch
[09:19] <FourDollars> xnox: I see. Thank you.
[09:21] <xnox> FourDollars: alternative to subscribing, you can do merge proposal. But you based on upstream branch, instead of lp:ubuntu/pristine-tar =/ so will not work.
[09:21] <xnox> FourDollars: and you are after an SRU?
[09:23] <FourDollars> xnox: I based on lp:ubuntu/precise/pristine-tar/ .
[09:24] <xnox> FourDollars: oh, ok. You did push branch to upstream project, $ bzr push lp:~/ubuntu/precise/pristine-tar/fix-lp-bug  is better & then one can click to create merge proposal against lp:ubuntu/precise/pristine-tar
[09:25] <FourDollars> xnox: Like lp:~fourdollars/ubuntu/precise/pristine-tar/fix-lp-bug-1218197 ?
[09:26] <xnox> FourDollars: yeap =)
[09:26] <FourDollars> xnox: OK.
[09:26] <tvoss> infinity, https://code.launchpad.net/~thomas-voss/location-service/remove-dep-on-ruby-ronn/+merge/182844
[09:26] <FourDollars> xnox: done.
[09:27] <infinity> tvoss: Looks reasonable to me.
[09:27] <tvoss> infinity, let's wait for ci to kick in and then top-approve
[09:29] <xnox> FourDollars: it looks like you didn't use "debcommit", or manually specify on $ bzr commit --fixes lp:NNNNNNN, thus the branch didn't get automatically linked to the bug report. Linked the new branch in.
[09:29] <xnox> FourDollars: ... and created merge proposal.
[09:30] <FourDollars> xnox: I do use "debcommit". @_@a
[09:30] <xnox> hm, strange.
[09:30] <FourDollars> xnox: It takes some time to sync. :)
[09:30] <FourDollars> xnox: Refresh the page now. You should see it.
[09:30] <xnox> maybe ;-)
[09:31] <xnox> but i did manually add bug report # on the page.
[09:32] <FourDollars> xnox: OK. Thank you for the guiding.
[09:56] <tvoss> infinity, jenkins is happy
[09:56] <tvoss> infinity, https://code.launchpad.net/~thomas-voss/location-service/remove-dep-on-ruby-ronn/+merge/182844
[10:00] <infinity> tvoss: Do you need an explicit ACK from me there, or are you good to go?
[10:00] <infinity> Oh, I guess I'm not in a team that was asked for a review anyway. :P
[10:01] <tvoss> infinity, hang on :)
[10:01] <tvoss> sil2100, Mirv lp:~thomas-voss/location-service/remove-dep-on-ruby-ronn
[10:02] <sil2100> tvoss: looking
[10:05] <Mirv> thanks
[10:24] <tvoss> infinity, the fix is top-approved
[10:25] <infinity> tvoss: I'm going to nod and pretend I know what that means, and assume it means "it'll be in the distro soon".
[10:25] <thotz> Question: Is it possible to add GIMP 2.8.6 to saucy. Could someone do that? It really would fix severial bugs see #1207734
[10:25] <tvoss> infinity, yup, that's all you need to know
[10:25] <thotz> https://bugs.launchpad.net/ubuntu/+source/gimp/+bug/1207734
[10:26] <seb128> thotz, I can have a look
[10:26] <infinity> thotz: You might want to poke jbicha when he's online, should be a trivial merge.
[10:26] <infinity> ... or seb128 can do it. :)
[10:26] <seb128> infinity, hey
[10:26] <seb128> infinity, can you review youker-assistant in saucy NEW for me?
[10:27] <seb128> infinity, I fixed some copyright issues/sponsored it for the UbuntuKylin guys, but since I did the upload I would prefer for another archive admin to review
[10:27] <thotz> thank you
[10:27] <seb128> infinity, they are eager to see it in apparently, it has been taking a while because of review feedback/things to fix
[10:27] <infinity> seb128: I'm running off to bed to attempt a nap, but if you don't find another victim, I can do it tomorrow.
[10:27] <seb128> infinity, thanks
[10:28] <thotz> should i contact jeremy?
[10:28] <seb128> infinity, have a good nap/night ;-)
[10:28] <seb128> thotz, no, I'm doing the gimp update
[10:30] <thotz> seb128: Thank you very much. I don't know if you have seen, I try go through the GIMP bugs.
[10:30] <seb128> thotz, thanks for helping there!
[10:33] <thotz> seb128, If I have some time I'm also trying to build development version from git, but I have no packaging experience. I have built yesterday GIMP 2.9 from GIMP... really promising :)
[10:35] <thotz> seb128, thank you too!
[10:43] <zyga> hi
[10:44] <zyga> current daily ubiquity installer seems broken, at least two things that I can see are affected: networking configs don't work (policykit rejects control attempts) and the top panel is sized incorrectly, being approximately 10x larger
[10:45] <xnox> zyga: both of which are filed bugs on ubiquity. The top panel is caused/assigned by/to larsu. The other one, missing proper logind integration
[10:45] <xnox> zyga: but maybe policykit policy also need changing.
[10:46] <rbasak> Is there a magic way to do a no change rebuild for a package that has no Ubuntu delta? Or do I need to do it manually, and then make sure to resync tha package manually again at some future date?
[10:46] <cjwatson> dch -R
[10:46] <cjwatson> That'll append build1 which doesn't inhibit autosyncs
[10:47] <rbasak> Ah, so the version number is special? I understand now. Thanks!
[10:47] <cjwatson> Yes.  The thing that inhibits autosync is the presence of the "ubuntu" substring in the version.
[10:48] <zyga> xnox: cool, so I won't go hunting or reporting them, thanks
[10:50] <ekarlso-> do I need to have my secret key on the machine I use for signing packages ?
[10:50] <cjwatson> Yes.
[10:51] <cjwatson> If you like, you can do the signing on a machine other than the one where you build the package, using either "debsign -r" or "debrsign" depending on the direction (see their manual pages).
[10:51] <rbasak> I use debsign -r to avoid this. But I must trust the machine I'm using, since I guess it could trojan some other thing to sign.
[11:16] <asac> ogra_: i think a script to show diffs on the packages file for two builds would be nice :)
[11:16] <asac> -> move touch
[11:16] <nemo> "You are running the upgrade over a remote ssh connection with a frontend that does not support this. Please try a text mode upgrade with 'do-release-upgrade'.
[11:16] <nemo> "
[11:16] <nemo> uh... since when?
[11:17] <nemo> ssh -Y headless-server  sudo update-manager, click yes on partial upgrade
[11:17] <nemo> first time I've ever seen that. someone change something?
[11:19] <zyga> "Warning: fake initctl called, doing nothing", after saucy install, does anyone know what that is?
[11:19] <nemo> "ERROR:root:upgrade over ssh not alllowed" grrrr why :(
[11:19]  * nemo greps
[11:20] <nemo> besides the typo
[11:22] <cjwatson> zyga: A broken install
[11:22] <cjwatson> zyga: If the installer finished properly it would have put the real initctl back
[11:22] <zyga> ah
[11:22] <zyga> yeah, the installer got stuck later and I just rebooted
[11:24] <nemo> # check if the frontend supports ssh upgrades (see lp: #322482)
[11:24] <nemo> hm
[11:25] <nemo> oh. yeesh.
[11:25] <nemo> that should just be a warning
[11:25] <nemo> I can bloody well make my own decision on this based on the stuff being upgraded
[11:25] <nemo> obv something that is going to screw w/ network will mess me up...
[11:26]  * nemo sighs and edits DistUpgradeController.py
[11:26] <nemo> I mean, seriously, for me to do this from a console would require a ridiculous amount of work
[11:27] <wgrant> xnox: You can't import a non-branch head using the ,branch= syntax.
[11:27] <nemo> the weird thing is it recommended I use curses UI, when as far as I can tell, the bug could possibly mess you up there too
[11:27] <wgrant> xnox: It has to be under refs/heads
[11:27] <xnox> wgrant: ack.
[11:29] <nemo> but, yeah, setting aside disagreeing w/ solution, logging.error("upgrade over ssh not alllowed")  has a typo in "allowed"
[11:32] <Mirv> any core-dev up for sponsoring? https://code.launchpad.net/~timo-jyrinki/ubuntu/saucy/qtpim-opensource-src/new_snapshot/+merge/182874 - built & tested
[11:32] <xnox> wgrant: sucks to be me =(
[11:33] <wgrant> xnox: Indeed :(
[11:34] <cjwatson> DistUpgradeViewText is in View.SupportSSH, so the curses UI ought to bypass this check
[11:35] <cjwatson> I think you can change it in DistUpgrade.cfg though
[11:36] <cjwatson> Fixed the typo in lp:ubuntu-release-upgrader
[11:38] <wgrant> ,branch=refs/dgit/sid works.
[11:42] <wgrant> xnox: Does that look right?
[11:43] <xnox> wgrant: nope. it imported HEAD.
[11:44] <xnox> wgrant: 191 should be the last commit on https://code.launchpad.net/~xnox/dgit/sid
[11:46] <wgrant> Oh, I am stupid.
[11:48] <nemo> cjwatson: yeah, I didn't want to use the curses UI, and given the launchpad issue, I don't see why the curses UI would help
[11:48] <nemo> cjwatson: looks like any remote connection would hit probs if eth0 was killed :)
[11:49] <nemo> cjwatson: setting that line to if false worked fine tho ;)
[11:49] <nemo> would have preferred it had been a warning
[11:52] <wgrant> xnox: The slashes need to be escaped as %2F, but somehow refs%2F causes the branch name to appear to be None. Investigated.
[11:55] <wgrant> s/ed/ing/
[12:01] <wgrant> xnox: A patch to make it work is trivial, but I need to think a bit about the implications
[12:01] <xnox> ok.
[12:04] <nemo> so. there's this script that was causing a rather misleading motd... /usr/lib/update-notifier/update-motd-fsck-at-reboot
[12:05] <nemo> reason it is misleading is it appears that if the last check was <1h ago, it won't even check the filesystem values
[12:05] <nemo> so I rebooted several times, thinking there was an issue
[12:05] <nemo> you'd think the script could also check uptime?
[12:06] <nemo> jrib: oh. and hi. I see you're here too :)
[12:07] <jrib> nemo: heh
[12:07] <jrib> nemo: I'd urge you to debug and file a bug ;)
[12:08] <nemo> well, I'd say the clear prob is if [ $(($stampt + 3600)) -lt $now ] || [ $stampt -gt $now ]; then
[12:08] <nemo> where stampt is stat -c %Y of the scary message
[12:14] <nemo> jrib: admittedly I don't know of a "nice" way to get the boot time...
[12:14] <nemo> apart from
[12:14] <nemo> date +%s -d "$(last | head -n 1 | awk '{print $5,$6,$7,$8}')"
[12:14] <nemo> which I just stitched together and seems pretty ugly
[12:14] <nemo> you'd thing it would be in sysctl or something...
[12:14] <nemo> I have no idea if that is even a locale specific format :-/
[12:15] <nemo> (the date string)
[12:15] <nemo> but anyway, assuming oh,  boott=$(date +%s -d "$(last | head -n 1 | awk '{print $5,$6,$7,$8}')")
[12:16] <nemo> then they should recheck if $boott gt $stamptt
[12:16] <nemo> ah well. whatev
[12:17] <nemo> hm. that's not even a nice use of last
[12:17] <nemo> I need a grep for reboot in there, and a skip of generation if it isn't.
[12:17] <nemo> something in sysctl would definitely be nicer. or maybe if ubuntu just wrote boot time to a file that its own script could check :)
[12:27] <seb128> mardy, hey, do you have an idea when you are going to have time for that shotwell patch update (asking because FF is today), do you want a bug report to track it?
[13:18] <pkern> So there's a patches.xml file on patches.ubuntu.com, but it redirects to people.ubntu.com/patches/.
[13:19] <pkern> Also: Are there patch files for Ubuntu releases as well?
[13:19] <cjwatson> That's ... huh
[13:20] <cjwatson> It's a permanent redirect from /patches which is apparently misfiring
[13:20] <cjwatson> I think I'll just comment it out, it's amazingly stale
[13:37] <superm1> Laney: hmm, I wonder why upstream missed it then.  Do you remember where you forwarded it?  I just filed a new bug with it (http://code.mythtv.org/trac/ticket/11794) that they set the milestone to before 0.27 releases, so we'll pull it back in the next upload
[13:38] <Laney> superm1: maybe a github project
[13:38] <cjwatson> pkern: The broken redirect is fixed now, thanks
[13:38] <cjwatson> Not sure about your other question
[13:38] <cjwatson> If you mean per-release patches, we normally only run merge-o-matic against the latest development series, so no
[13:39] <superm1> Laney: oh yeah i see it now.  They don't track pull requests as much as they should and prefer bugs for tracking stuff like that.  Thanks.
[14:05] <dobey> infinity: just dput ubuntuone-credentials 13.08-0ubuntu1. we'll see if it makes it to NEW
[14:25] <dobey> infinity: email i got said it's in new for saucy-proposed
[14:50] <seb128> cjwatson, slangasek: is somebody from foundation leading https://blueprints.launchpad.net/ubuntu/+spec/client-s-32v64-bit ? (it ended up in the client track but you guys probably have more background/opinions on the topic than us)
[14:50] <seb128> (that's in 15 minutes in client2)
[14:50] <cjwatson> I have to be in a different session, sorry
[14:51] <seb128> xnox, stgraber: ^?
[14:51] <xnox> seb128: i don't have any rights to start hangout.
[14:51] <slangasek> seb128: I can be there if I can get someone else to run the camera for the foundations session
[14:51] <seb128> xnox, the track hosts start the hangouts (e.g me for that one)
[14:52] <slangasek> seb128: do you want to trade tracks for next hour? :)
[14:52] <seb128> xnox, but I don't know enough about the topic to lead the session...
[14:52] <seb128> slangasek, I can host yours, sure
[14:52] <slangasek> ok, cool
[14:53] <seb128> slangasek, so I'm hosting the checkbox one and you take on the 32v64 bit, right?
[14:53] <slangasek> seb128: exactly
[14:53] <slangasek> thanks :)
[14:53] <seb128> slangasek, excellent, thank you!
[16:10] <stgraber> dpkg: error processing /var/cache/apt/archives/unity-webapps-common_2.4.16+13.10.20130829.2-0ubuntu1_all.deb (--unpack):
[16:10] <stgraber>  trying to overwrite '/usr/share/icons/hicolor/128x128/apps/ubuntuone-music.png', which is also in package unity-asset-pool 0.8.24daily13.06.10-0ubuntu1
[16:12] <stgraber> it's one of those auto-landed packages so I have no idea who to nag/blame about this...
[16:12] <ChrisTownsend> stgraber: Here's a start: https://code.launchpad.net/~abreu-alexandre/webapps-applications/add-default-apps/+merge/182646
[16:13] <stgraber> right, unfortunately robru doesn't appear to be around
[17:35] <pkern> cjwatson: Well, I solved my problem (where is file X used) by using Debian's codesearch, downloading all Ubuntu patches and grepping. ;)
[17:36] <cjwatson> Heh
[17:57] <xnox> pkern: jdstrand can run greps on full ubuntu unpacked trees. they do take some time though.
[17:58] <jdstrand> I'm not sure that should be advertised as a public resource :P
[17:58] <xnox> =)))))
[17:59] <jdstrand> it's all very manual-- I don't mind doing it as a favor, but it isn't something can just do. codesearch for Ubuntu would be nice
[17:59] <jdstrand> s/can just do/I can just do all the time/
[17:59] <xnox> jdstrand: Laney has a codesearch instance running in canonistack =) not sure how fully operational it is.
[18:00] <jdstrand> oh, that would be nice to poke at
[18:01] <sarnold> oh man, that'd be nice. I love debian's codesearch
[18:09] <cyphermox> @pilot in
[18:21] <sarnold> seb128: retracers seem dead again -- any chance of asking IS to monitor the cranky things to auto-restart when they wedge? :)
[18:26]  * dholbach hugs cyphermox
[18:26] <cyphermox> dholbach: hey, just trying to read the list is painful, so many pings about other stuff :)
[18:26] <dholbach> I know
[18:27] <dholbach> I did quite some sponsoring in the last days to get stuff in before feature freeze
[18:27] <dholbach> but during UDS it's a bit crazy admittedly
[18:27] <dholbach> I'll do the rest of my session tomorrow
[18:30] <pkern> xnox: Before I do that I set up a private instance of codesearch. -_-
[18:33] <pkern> jdstrand: How large is it?
[18:36] <jdstrand> pkern: I don't have a private instance of codesearch. I use debmirror to mirror all of lucid-saucy for amd64 and i386
[18:36] <pkern> jdstrand: I mean the unpacked tree.
[18:37] <jdstrand> pkern: I use scripts to unpack on the fly and then delete after the package is searched
[18:37] <jdstrand> pkern: so I don't unpack all the sources
[18:38] <jdstrand> (at the same time)
[18:38] <seb128> sarnold, talk to slangasek, he sort of suggested he was wanting to help keeping those running ;-)
[18:39] <slangasek> hnngh
[18:39] <slangasek> and no email notification of it hanging, eh
[18:39] <sarnold> slangasek: hello :) about those retracers...
[18:39] <slangasek> seb128: I also always forget what machine it's running on, remind me?
[18:39] <seb128> slangasek, porter-i386.c.c
[18:39] <seb128> I removed the lock
[18:40] <seb128> but I think it's hitting a bug it doesn't like
[18:40] <seb128> bug #1216901
[18:40] <slangasek> ok
[18:40] <seb128> the bt isn't very useful though :/
[18:41] <seb128> slangasek, do you want to have a look to the issue or should I just untag the bug so the retracer doesn't keep banging on it?
[18:41] <seb128> well, I guess we can untag & have a look as well
[18:41] <slangasek> seb128: I won't have time to look at it very quickly, so please untag it for now anyway
[18:41] <bdmurray> barry: the tracebacks in https://errors.ubuntu.com/problem/15bc0ab1791f275923e1d66575637a22e2b24b7d look suspcious to me - as in I wonder about the systems
[18:41] <seb128> doing
[18:49] <barry> bdmurray: that looks very suspicious.  it looks typical for a 3rd party extension module not checking a set exception somewhere
[19:02] <stgraber> barry, lool: should we schedule an hangout for after the closing plenary?
[19:03] <barry> stgraber: i'm available
[19:10] <lool> stgraber: ok
[19:14] <ekarlso-> "Source/binary (i.e. mixed) uploads are not allowed." how can I get dput to only select the source ?!
[19:15] <shadeslayer> ekarlso-: just run debuild -S -sa on the source
[19:16] <shadeslayer> or -sd if you just want to upload a package which already has the tar on launchpad
[19:16] <cjwatson> -sd is basically never necessary
[19:16] <cjwatson> but yeah, -S is the key bit
[19:17] <shadeslayer> cjwatson: oh, so -sa uploads the tar but launchpad is clever enough to not make a copy?
[19:17] <cjwatson> you can upload a duplicate orig.tar as long as it's identical
[19:17] <ekarlso-> I used the dpkg-buildpackage binary
[19:17] <cjwatson> I usually use debuild -S and only use -sa if needed
[19:18] <ekarlso-> is that the same thing
[19:18] <shadeslayer> cjwatson: aha I see
[19:18] <cjwatson> ekarlso-: Launchpad doesn't accept binary uploads, they have to be source-only.  No it isn't the same
[19:18] <cjwatson> You can use dpkg-buildpackage -S, though debuild -S is usually easier
[19:18] <cjwatson> (it's a slightly smarter wrapper)
[19:18] <ekarlso-> how can I have it not try to sign it ?
[19:18] <cjwatson> -uc -us
[19:18] <cjwatson> or just ignore the signing failures
[19:19] <cjwatson> you still have to sign it before uploading to LP of course
[19:19] <shadeslayer> ^^
[19:19] <ekarlso-> debuild -S -uc -us the ?
[19:19] <cjwatson> yeah
[19:19] <ekarlso-> what's Standards-Version ?
[19:20] <ekarlso-> my build fails on that now :p
[19:20] <cjwatson> see the Debian policy manual
[19:20] <cjwatson> http://www.debian.org/doc/debian-policy/
[19:20] <cjwatson> specifically http://www.debian.org/doc/debian-policy/ch-controlfields.html#s-f-Standards-Version
[19:20] <cjwatson> and http://www.debian.org/doc/debian-policy/ch-source.html#s-standardsversion
[19:20] <cjwatson> (the latter's a better reference, sorry)
[19:21] <ekarlso-> should it fail on 3.9.3 ?
[19:22] <cjwatson> 3.9.3 is fine
[19:23] <ekarlso-> mine fails telling me it is outdated..
[19:23] <cjwatson> that's not a failure
[19:23] <cjwatson> it's quite important to distinguish errors from warnings or informational messages ...
[19:23] <cjwatson> the current version is 3.9.4 but you should check the policy manual's upgrading checklist before blindly changing the number
[19:24] <cjwatson> the point is to remind people to check changes in policy
[19:24] <ekarlso-> cjwatson: how come ? ;)
[19:24] <cjwatson> because that's the point of standards-version - it's the latest version of the policy manual you've checked your package against
[19:24] <cjwatson> it isn't supposed to be a paperwork exercise in updating the number :)
[19:25] <cjwatson> if it's a little out of date, so be it, it's not a failure
[19:58] <stgraber> lool, barry: I'll invite the two of you to an hangout in the next 5min
[19:58] <lool> stgraber: ok
[20:02] <barry> sounds good
[20:08] <dobey> kenvandine: so where's the rum?
[20:22] <kenvandine> dobey, i could use some :)
[20:23] <dobey> heh
[20:24] <dobey> unfortunately i don't have any soda or ice
[20:25] <dobey> and a little too early, and air too dry inside, to drink it straight
[22:03] <ekarlso-> https://launchpadlibrarian.net/148814928/buildlog_ubuntu-precise-i386.cyassl_2.7.0-1_FAILEDTOBUILD.txt.gz < anyone help me on why that is failing ?
[22:03] <ekarlso-> it works when building locally
[22:09] <sarnold> ekarlso-: that looks like building an i386 binary on an amd64 host -- have you tried reproducing an i386 build on an amd64 host locally?
[22:24] <ekarlso-> sarnold: I the package should only be amd64...
[22:30] <sarnold> ekarlso-: aha. you may need to specify that in the control file..
[22:32] <ekarlso-> sarnold: how ?
[23:14] <YokoZar> slangasek: I uploaded all the relevant wine bits today :)
[23:17] <slangasek> YokoZar: hurrah
[23:17] <YokoZar> I couldn't find the wiki page about deleting packages, but I presume it's just "file bug, subscribe ubuntu-archive"
[23:18] <sarnold> ekarlso-: I believe the keyword is 'amd64', in this field: http://www.debian.org/doc/debian-policy/ch-controlfields.html#s-f-Architecture
[23:19] <slangasek> YokoZar: yes