[14:57] <juergh> how can I download a source package from a private PPA? I can authenticate and get the published sources using archive.getPublishedSources but can't figure out how to actually download the bits.
[15:14] <nacc> juergh: i believe the URLs are a bit hidde, but https://launchpad.net/~USER/+archive/ubuntu/PPA_NAME/+files/FILENAME
[15:14] <nacc> juergh: you get the filenames from the API call you did
[15:25] <juergh> nacc, thanks but how do I download the files? I can construct the URL which works in a browser but if I do a simple urllib2.urlopen on that URL I get a 404 error. Which makes me think I need to either a) do some auth with urllib or b) us a launchpadlib helper/method.
[15:27] <nacc> juergh: i'm trying to get this fixed urgently, as our snap is busted, but git-ubuntu has an importppa function that will take a PPA and import it to git
[15:27] <nacc> juergh: the implementation is https://git.launchpad.net/usd-importer/tree/gitubuntu/importppa.py
[16:13] <kwmonroe> yo cjwatson, i setup my env like you suggested yesterday (ufw deny outgoing bits except those through my auth proxy).  i still can't figure out why lp builders return 403 while my local setup works.  could you do me a favor and grep for proxy hits to maven.org from the last hour?  here's an example succesful hit for my local build while the lp builders 403:  http://paste.ubuntu.com/25587006/
[16:17] <cjwatson> kwmonroe: It looks like you aren't always sending the username to the proxy
[16:17] <cjwatson> snap-proxy/squid/access.log:<IP_ADDRESS> - - [21/Sep/2017:15:36:52 +0000] "HEAD http://repo.apache.maven.org/maven2/xmlenc/xmlenc/0.52/xmlenc-0.52.jar HTTP/1.1" 403 457 "-" "Apache Ivy/2.2.0" TCP_DENIED:HIER_NONE
[16:18] <cjwatson> compare and contrast a working hit from the same build:
[16:18] <cjwatson> snap-proxy/squid/access.log:<IP_ADDRESS> - SNAPBUILD-83382-1506007468 [21/Sep/2017:15:36:40 +0000] "GET http://repo.apache.maven.org/maven2/xmlenc/xmlenc/0.52/xmlenc-0.52.pom HTTP/1.1" 200 1422 "-" "Wget/1.17.1 (linux-gnu)" TCP_MISS:HIER_DIRECT
[16:19] <kwmonroe> yeah cjwatson - that 2nd one works because that's me doing a wget to make sure i'm not crazy:  https://github.com/juju-solutions/snap-pig/blob/master/snap/snapcraft.yaml#L209
[16:20] <kwmonroe> so i'm guessing there's something about ant that isn't passing along the proxy config correctly.  still, i'm troubled by not being able to repro in my local squid env.  it's rather painful to commit / cross fingers / request lp builds.
[16:23] <cjwatson> (you can see SNAPBUILD-83382-1506007468 passed as http.proxyUser in your build)
[16:23] <cjwatson> so I guess something in the insinnards of maven loses that sometimes)
[16:23] <cjwatson>  like I say, Java 's HTTP stack by default only does anything with authed proxies if you specifically set up a java.net.Authenticator
[16:23] <cjwatson> sorry, extreme lag
[16:23] <cjwatson> I banged my head against this in ant for quite a while and I'm afraid I gave up
[16:23] <cjwatson> I suspect https://code.launchpad.net/~cjwatson/launchpad-buildd/local-snap-proxy/+merge/322545 is the only sane answer
[16:25] <kwmonroe> heh, roger that cjwatson -- i appreciate the help and digging through those logs!
[17:41] <iliv> hey guys
[21:26] <alai> hi, could someone please help on launchpadlib?
[21:26] <alai> i'm getting the uncorrect date
[21:27] <alai> for bug 1705594, task.date_fix_committed returns 2017-09-19 which is not correct
[21:28] <alai> it is incomplete and the fix_commited date should be None
[21:41] <cjwatson> alai: those attributes are pretty weird; can you just use a different approach, like the bug activity collection?
[21:42] <cjwatson> alai: please file a bug against Launchpad itself about the odd data in this case, though
[21:42] <cjwatson> (it's not launchpadlib's fault - that's just a thin layer talking to the webservice)
[22:06] <alai> cjwatson, https://bugs.launchpad.net/launchpad/+bug/1718795
[22:14] <cjwatson> thanks


[00:18] <slangasek> superm1: do you recall how it is that mythbuntu liveCD builds get their task lists?
[00:18] <slangasek> I don't seem to be able to persuade the buildds to put grub-pc in the livefs
[00:58] <mathiaz> cjwatson: are you subscribed to partman-auto-raid bugs?
[00:59] <slangasek> https://bugs.launchpad.net/ubuntu/+source/partman-auto-raid/+bug/385754 -> "also notified" -- nope
[01:01] <mathiaz> slangasek: right - so I don't think cjwatson is notified
[01:01] <slangasek> appears not
[01:18] <superm1> slangasek, they were via meta packages i thought
[01:19] <superm1> is grub-pc not working in just mythbuntu disks, or all?
[01:19] <superm1> we're the only one that does meta packages though, tasks pulled in too much because of the order of dependency resolution
[01:19] <slangasek> superm1: it was missing from all the disks; now I've got it included everywhere but mythbuntu
[01:19] <superm1> slangasek, interesting...
[01:19] <superm1> it should come as a recommend to ubiquity
[01:20] <slangasek> I guess it's possible that mythbuntu is only getting grub at all because it's a Recommends: of linux-image, and that's being resolved first and satisfies ubiquity's recommends
[01:21] <superm1> why is grub still a recommends of the kernel anyway though?
[01:21] <superm1> is that just some legacy thing?
[01:22] <sharms> can someone point me to documentation on what is different about lpia vs. i386?  Ie if I want to compile a package for it, its just extra gcc flags right?
[01:24] <superm1> UNR looks to be built the same way as mythbuntu - without a task but instead a meta.  is it having the same problems?
[01:26] <slangasek> superm1: no, UNR is fine
[01:27] <slangasek> superm1: the bootloader is a recommends of a kernel because that's the correct relationship; the wrong bootloader is recommended because we didn't even notice until today that grub-pc wasn't on the CD at all... :)
[01:27] <slangasek> (it was working for people, but only with network available at install time)
[01:27] <superm1> hmm i see
[01:28] <superm1> considering the kernel is installed before ubiquity for the cases, i'm perplexed how any of the other builds dtrt then
[01:30] <superm1> oh - it looks like for some reason in the standard ubuntu build grub actually gets removed in favor of grub-pc though http://people.ubuntu.com/~ubuntu-archive/livefs-build-logs/karmic/ubuntu/20090610.1/livecd-20090610.1-i386.out
[01:30] <slangasek> superm1: because grub-pc is explicitly part of the task
[01:31] <slangasek> hrmm, removed?  so grub-pc does conflict with grub now?
[01:31] <superm1> it always has
[01:31] <slangasek> hmm, ok
[01:31] <superm1> which task is it explicitly part of for standard? I looked through ubuntu.karmic's seeds, and didn't see it mentioned in anything but dvd
[01:32] <slangasek> pitti: I'm sure you'll see this in your highly efficient email processing anyway :), but I've followed up to bug #201114 - I basically can't reproduce the problem at this point
[01:32] <slangasek> superm1: platform.karmic
[01:32] <slangasek> superm1: the boot seed
[01:33] <superm1> ah. i wonder if by using meta's for mythbuntu we don't properly inherit things from the boot seed then even though we have an include platform.karmic
[01:35] <slangasek> I'm not sure, but I definitely don't see any mythbuntu metapackages that depend on grub, which was already part of said seed
[01:35] <slangasek> so there is a disconnect somewhere
[01:49] <superm1> slangasek, i'm rather perplexed on where the disconnect is myself, but i suspect that it's probably something related to us not using tasks.  for now, would adding it to ship-live do the trick?
[01:49] <superm1> and as a long term plan, try to get things switched to using tasks so weird disconnects like this don't happen
[01:50] <slangasek> if you want to add it to ship-live, that would do it, yes
[01:54] <TheMuso> asac: Ok, bluetooth audio with pulse for the most part works. I have a headset that can do stereo playback, or headset/microphone mode, i.e the 2 different audio profiles. With the gnome-volume-control-pulse applet, I can't switch between the profiles yet, but I can move a stream to the headset.
[01:54] <TheMuso> asac: I still have to use pavucontrol to adjust the profile for the bluetooth headset, but its only a matter of fixing up the gnome volume pulse applet UI to deal with profiles, which afaik is coming anyway.
[01:55] <TheMuso> asac: SO there is in fact not much to do in this area.
[01:57] <superm1> slangasek, okay so i've added it to ship-live, so i'd expect Next build to be OKish
[01:58] <slangasek> superm1: that'll be mythbuntu-meta 0.39?
[01:58] <superm1> slangasek, i dont think i need to do a new meta to adjust ship-live
[01:58] <superm1> isn't that part pulled in by ubuntu-cdimage?
[01:59] <slangasek> superm1: nope, it's pulled in via livecd-rootfs, which is what pulls in the meta packages :)
[02:00] <superm1> well are we talking about the same thing though? i'm not saying the live seed which is used to build mythbuntu-live meta package, i'm saying the ship-live cd that builds the on-cd-repo
[02:00] <slangasek> oh
[02:00] <slangasek> you're putting it on the CD but not in the livefs, right
[02:00] <superm1> right at least for now, until i can sort out the tasks problem
[02:01] <slangasek> that can work
[02:01] <superm1> we've got the space for it still at least
[02:01] <slangasek> in that case, building now
[02:01] <superm1> cool thx
[02:13] <slangasek> superm1: ah, nope, doesn't work because germinate sees grub-pc already in the live seed, so thinks it doesn't need to duplicate it in ship-live :)
[02:13] <slangasek> superm1: so it'd need a meta respin here
 okay, i'll fire up the machine with the meta source and respin
[03:01] <GNUix> quick question with this whole paper cut idea and the CDROM eject stuff.  "I can't eject my CDROM" .. "Well have can you unmount the volume in the command line?" "WTF is mount what.. you sicko!"
 It already works like that.
[03:03] <GNUix> StevenK: Yes, but you also get "unmount" which is correct, apparently this is confusing people
[03:06] <superm1> slangasek, okay 0.39 is in and should have it
[03:06] <persia> GNUix, Well, there exist cases where one wishes to unmount without ejecting.  Should we make this deliberately hard?
[03:09] <GNUix> persia: Let me clarify.. I think the way things work right now are fine. What I don't want it all the terminology being changed on my desktop because some people are confused by mount/unmount
[03:10] <TheMuso> Don't forget that if nothing is accessing the CD/DVD drive, you can press the button on the drive and the disk will eject.
[03:11] <persia> GNUix, You don't have an "eject" option?
[03:11] <persia> Or perhaps I misunderstand.  Where is this proposal?
[03:12] <GNUix> persia: nevermind.. I was refering to a blog post that mentioned this idea of 'paper cut' type bugs to fix small stuff supported by the big C .. one of the ideas is to remove the unmount option from removable media because 'umount' is tech speak..
[03:13] <persia> Oh, just in a blog post.  Probably better to note use cases that break this in a comment in the post.
[03:14] <GNUix> persia: well its not just a blog post, its 'officially' supported and there are bugs in launchpad for this stuff.
[03:15] <persia> Commenting in the bugs is the best way to present reasons why something oughtn't be done for those things where there are bugs filed.  I'm unsure what you mean by "officially supported".
[03:19] <ScottK> 100 paper cuts is a spec for Karmic.
[03:20] <persia> Are each of the paper cuts being identified in the spec?
[03:20] <StevenK> I don't believe so
[03:21] <persia> I'm not sure I understand the point of having a spec in that case, but OK.
[03:21] <StevenK> I don't think unmount actually meets the definition of a paper cut, either
[03:21] <persia> Anyway, I still maintain that if there are bugs being filed about changes that would break some use cases, it's a good idea to identify the use cases to be broken in those bugs.
[03:27] <nixternal> pitti: I have ported apport-qt to apport-kde for better integration into the Kubuntu desktop - I have pushed it to lp:~nixternal/apport/apport-kde
[03:27] <superm1> nixternal, i think generally a merge request is better than an IRC ping so it's not easily overlooked :)
[03:27] <nixternal> that is there as well
[03:28] <superm1> okay, cool
[04:07] <Vantrax|Work> I have a query about newer kernels being added to the 8.04 repositories
[05:14] <macvr> hi all... has anyone used the e4defrag?
[06:22] <superm1> slangasek, looking at http://people.ubuntu.com/~ubuntu-archive/livefs-build-logs/karmic/mythbuntu/ it seems that the livefs wasn't even attempted since the new ISO was made. is the livefs still on autopilot, or does it need the magic prod that only slangasek can provide :)?
[06:34] <dholbach> good morning
[07:15] <nixternal> w00t, tied in apport-qt and easily changeable with apport-kde in all KDE ... Help->Report Bug... menus...hold on to your socks LP, the bug reports will be a coming :)
[07:15] <nixternal> KDE will be a bit happier that people aren't filing Kubuntu bugs on KDE Bugzilla now :)
[07:17] <persia> nixternal, So you can now do the "report a problem" menu items?
[07:17] <nixternal> persia: yes
[07:17] <persia> Excellent :)
[07:17] <slangasek> superm1: we're in the "manual builds only" milestone zone, sorry - building one now
[07:17] <nixternal> all KDE apps will be able to do that now :)
[07:17] <nixternal> as long as they are utiling the KHelpMenu class
[07:17] <nixternal> which everything in kde* for us does
[07:18] <slangasek> superm1: though I'm far from the only person who can trigger the builds; the release team set has more than one member :)
[07:19] <lizthegrey> what's the procedure for recruiting people to test backports and/or declaring a backport sufficiently tested to go into backports?
[07:22] <persia> lizthegrey, There's no set procedure.  If the bug doesn't get enough, posting to one's blog, adding a request in the forums, trolling in #ubuntu, microblogging, etc. may work.
[07:23] <mneptok> persia: don't forget PayPal
[07:23] <persia> Extra points if you can help extend the team of backport testers to test all the backport candidates.
[07:23] <StevenK> slangasek: ITYM, -cdimage ?
[07:23] <persia> mneptok, PayPal is for *after* you have identified the potential recruits.  Payment before presentation of the request is underhanded at best.
[07:24] <slangasek> StevenK: well, perhaps - I wasn't presuming that -cdimage members who aren't on the release team would feel comfortable respinning on their own :)
[07:24] <lizthegrey> persia: hah.  okay :)
[07:24] <StevenK> slangasek: Hehe
[07:24] <lizthegrey> is it customary to provide binary packages for testers to install or to point them at prevu?  I'm worried about asking too much of people to Just Trust Me (tm)?
[07:24] <lizthegrey> the package in question is sudo, so...
[07:25] <persia> I'm not on the backports team, but my memory of the answer to the question in the past is that the intiial backport testers are encouraged to use prevu (or similar tools) for testing.
[07:26] <lizthegrey> yeah, I built my packages using prevu :)
[07:26] <persia> I suspect that's more an attempt to limit testing to people who can recover after breaking their system than an actual requirement, but I don't know the actual policy.
[07:27] <lizthegrey> ah.
[07:28] <pitti> Good morning
[07:28] <lizthegrey> I'll gpg sign the binaries, so since I'm relatively plugged into the WOT people can go after me with pitchforks should things not be on the up and up :)
[07:28] <StevenK> Morning pitti
[07:29] <lizthegrey> bug in question is https://bugs.launchpad.net/hardy-backports/+bug/384100 in case one is curious :) - I'm trying to get sudo 1.7.0 from karmic backported to dapper and hardy since being able to #include a sudoers file fragment is a lot easier/more scalable than mangling the sudoers file programatically :)
[07:30] <pitti> nixternal: oh, nice! will take a look at it
[07:31] <pitti> hey StevenK
[07:31] <pitti> slangasek: right, saw your reply; nice to hear
[07:32] <slangasek> pitti: well - have I reached the right conclusion? :)
[07:32] <slangasek> maybe there's still a bug but we've misdiagnosed?
[07:32] <pitti> slangasek: I'll check it in a minute, when I get to that mail
[07:32] <slangasek> okie
[07:39] <slytherin> Does anyone have any idea about this error when trying to setup texlive-base - dpkg-trigger: dpkg-trigger must be called from a maintainer script (or with a --by-package option)
[07:39] <soren> Using dpkg-reconfigure?
[07:40] <soren> slytherin: ^
[07:40] <slytherin> soren: the problem is occurring on powerpc buildd. I haven't tried local build yet.
[07:41] <soren> If so, it's bug 198421
[07:41] <soren> slytherin: Ah. Then I don't know.
[07:42] <slytherin> perhaps kees has any idea. He is the latest uploader of texlive-base.
[07:42] <TheMuso> slytherin: I think that bug was fixed. I retried a build the other day that had something similar, and the build worked, so I'd suggest try to update.
[07:43] <slytherin> TheMuso: The bug is with latest package as well AFAIK. I will still try rebuild and report back.
[07:51] <slytherin> TheMuso: build still failing with same error. The package in question is tuxguitar.
[07:52] <TheMuso> slytherin: hrm ok hang on a sec.
[07:52] <TheMuso> slytherin: is this on the buildds?
[07:54] <slytherin> TheMuso: yes, powerpc buildd. I didn't find time to try a local build.
[07:54] <TheMuso> ok
[08:07] <TheMuso> slytherin: This is very weird, as its building for me locally. I guess since my local mirror hasn't been updated, there is no new breakage...
[08:08] <slytherin> TheMuso: I will try building locally time with fully updated karmic chroot and report back.
[08:08] <TheMuso> ok
[08:09] <pitti> slangasek: nack, apt-get install language-support-de still pulls in openoffice.org-common openoffice.org-core
[08:10]  * pitti investigates
[08:13] <pitti> slangasek: ah, it's -thesaurus
[08:16] <pitti> slangasek: bug updated
[08:57] <pitti> evand1: hm, does usb-creator work for you? I just wrote the current karmic desktop amd64, and when booting it just drops me into initramfs, with lots of "cannot find image on /dev/sr0"
[08:57] <evand1> pitti: yikes, checking now
[08:58]  * pitti tests in kvm
[09:11] <pitti> evand1: .iso works in kvm, so I think it's not generally broken
[09:15] <evand> okay
[09:32] <pitti> geser: argh, seems that the recent pkg-create-dbgsym whitespace fix broke things: http://launchpadlibrarian.net/27762179/buildlog_ubuntu-karmic-i386.dictd_1.11.1%2Bdfsg-2_FAILEDTOBUILD.txt.gz
[09:37] <pitti> geser: I'll write test cases for bug 384597 and the new breakage
[09:38] <cjwatson> slytherin: that's been on my list to look at, but it's completely non-obvious ...
[09:39] <cjwatson> slytherin: it's unlikely to be texlive-base's fault, and the code in dpkg *looks* ok
[09:43] <slytherin> cjwatson: right. Unfortunately I didn't find time since we last discussed this issue. I will try to find time sometime this week.
[10:16] <pitti> tkamppeter: hm, seems I can't find your patch on http://bugs.debian.org/cgi-bin/pkgreport.cgi?src=poppler, which bug was that?
[10:22] <seb128> pitti: what patch are you looking for? I sponsored some poppler changes a week ago
[10:22] <seb128> ie bug #335397
[10:22] <seb128> bug #382379
[10:22] <seb128> pitti: ^
[10:23] <pitti> seb128: I know, I thought Till already created a Debian bug for it
[10:23] <seb128> ok ignore me then that was in case the information was useful ;-)
[10:23] <pitti> but nevermind, it's fixed upstream; it'll land there eventually, and until then I do a small hack in cups
[10:23]  * pitti hugs seb128, merci
[10:23]  * seb128 hugs pitti
[10:30] <Keybuk> cjwatson: you remember I was asking how to declare an extern array in a header file?
[10:30] <Keybuk> I remember why I didn't think that was correct, now
[10:30] <Keybuk> tests/com.netsplit.Nih.Test_object.h:23: error: array ‘my_interfaces’ assumed to have one element
[10:33] <Keybuk> looks like it has to be explicitly extern
[10:34] <cjwatson> Keybuk: explicitly extern is what I said, I think
[10:36] <Keybuk> yeah it was
[10:36] <Keybuk> sorry, I was attempting to confirm what you said in a strange way :p
[10:36] <cjwatson> ah :)
[10:43] <pitti> lool: any chance to upload current poppler 0.11.0 to Debian? Otherwise I have to jump through some hoops in cups
[10:44] <pitti> tkamppeter: ^ you bumped libpoppler-dev to >= 0.11 for the new pdf filter
[10:46] <ogra> pitti, he's travelling this week, i doubt he has much time for package maintenance work
[10:46] <pitti> oh, ok
[10:46] <ogra> (or much connection)
[10:58] <Keybuk> cjwatson: I'd assumed since it was in an extern "C" { ... } block, that'd be enough
[10:58] <Keybuk> but, of course, that's C++ :p
[11:08] <tkamppeter> pitti, I did this for the addition of the pdftoopvp filter which I did last week.
[11:09] <tkamppeter> pitti: ^ the libpoppler-dev >= 0.11 dependency
[11:10] <pitti> tkamppeter: I know
[11:10] <pitti> I'll mail you shortly with some details
[11:11] <tkamppeter> pitti, is lool the Debian maintainer of Poppler?
[11:11] <pitti> tkamppeter: yes (one of them)
[11:11] <seb128> debian doesn't track unstable series though
[11:12] <seb128> ie they don't use 0.11
[11:12] <seb128> not sure if that makes a different for what you want to do
[11:13] <pitti> oh, I see
[11:13] <pitti> tkamppeter: how urgent is it to get the pdftoopvp filter?
[11:16] <tkamppeter> pitti, I simply got the filter from the upstream developer Koji Otani from OpenPrinting Japan. Japanese printer manufacturers, like Canon for example, want to have this filter.
[11:16] <pitti> tkamppeter: so if 0.12 doesn't get released soon, we have to do another dynamic check at build time
[11:16] <pitti> but for now I just disable it, in order to get the fixed cups to debian/ubuntu ASAP
[11:17] <tkamppeter> Poppler 0.11.0 has API additions developed by Otani to make the pdftoopvp filter possible
[11:17] <tkamppeter> So 0.11 is a development series, like an odd-numbered kernel?
[11:18] <seb128> similar to GNOME naming scheme
[11:18] <tkamppeter> pitti, can we perhaps make this filter Ubuntu-only for the case that 0.12 does not make it into Debian before our FF?
[11:19] <pitti> tkamppeter: yes, see above
[11:19] <pitti> but I'd really like to upload -3 right now
[11:19] <pitti> tkamppeter: you have mail now
[11:21] <tkamppeter> OK. Thanks.
[11:21] <tkamppeter> Is lool on vacation?
[11:21] <seb128> pitti: new poppler stable will be in one month apparently
[11:21] <seb128> or that's the schedule they work on
[11:21] <persia> tkamppeter, Earlier backscroll said he was travelling, but didn't specify purpose.
[11:21] <pitti> cool, that should fit
[11:22] <seb128> tkamppeter: no, but he's in the US this week I think
[11:31] <ogra> asac, about bug 385325, will TB beta be in karmic in time ?
[11:31] <ogra> s/beta/3/
[11:36] <asac> ogra: we had this discussion with NCommander in #ubuntu-mozillateam
[11:36] <asac> ogra: i wouldn't count on it. upstreawm has no strict commitment
[11:36] <asac> ogra: so i told him how to do a proper debug build and we can check what we can do for tbird 2. but most likely its more than one patch
[11:38] <pitti> cjwatson: what was the tool again to display X.org resource usage? (for memleaks, etc.)
[11:39] <ogra> xrestop ?
[11:46] <Ampelbein> cjwatson: hi. now that gpsd is built on sparc, could you retry the viking build at https://edge.launchpad.net/ubuntu/+source/viking/0.9.8-2/+build/1068859 ? thanks.
[11:48] <tkamppeter> pitti, Otani has also provided two patches for Poppler 0.10.x to make it supporting pdftoopvp.
[11:49] <tkamppeter> pitti: One is to make Poppler build. It is simple, around 10 lines. The other is to add color management support. Could be an alternative approach for Debian.
[11:49] <pitti> tkamppeter: right, let's talk to lool when he's back
[11:55] <cjwatson> pitti: xrestop was indeed the one I mentioned a while back
[11:55] <pitti> seb128: ^ might help you to check memleak
[11:55] <pitti> cjwatson: thanks!
[11:56] <seb128> ok
[11:56] <cjwatson> Ampelbein: done
[11:56] <seb128> brb
[12:23] <Chipzz> http://git.gnome.org/cgit/evolution-data-server/commit/?id=d17494da8ebaba8673a581f256efc8a1d41e1e40
[12:23] <Chipzz> *grin*
[12:36] <ivoks> Chipzz: lol
[13:07] <james_w> how are you supposed to update debian/applied-patches/ when doing a merge?
[13:08] <seb128> james_w: patch -p<n> < change?
[13:08] <james_w> seb128: apply them again?
[13:08] <seb128> again?
[13:09] <seb128> the idea is to have the patches in the debian directory for things not using a patch system, ie having changes in the diff.gz
[13:09] <seb128> it makes easier to know the changesets
[13:09] <james_w> yeah
[13:09] <seb128> or rather a copy of the patches applied to the diff.gz
[13:09] <james_w> but now I've just merged with Debian
[13:09] <james_w> so the patches there are out of date
[13:10] <seb128> well update those with the changes you applied
[13:10] <james_w> yes
[13:10] <james_w> but how?
[13:10] <seb128> or clean those if some are not applied in the new version
[13:10] <seb128> diff -u file.debian file.ubuntu?
[13:10] <james_w> that assumes they are separated by file though
[13:10] <seb128> no, that assume you have a logical order
[13:10] <seb128> you start from debian
[13:10] <seb128> reapply a changeset
[13:11] <seb128> diff and put that in a patch
[13:11] <seb128> copy the dir and reiterate
[13:11] <seb128> ie
[13:11] <seb128> source
[13:12] <seb128> cp -R source source.debian, work in source to apply the first changeset you work on, diff -Nur source.debian source, copy the patch
[13:12] <seb128> and iterate that way for each successive change?
[13:12] <james_w> well, I'd rather have 3-way merge, and not have to do all that by hand, so I think I'll just delete them all
[13:13] <seb128> *shrug*
[13:13] <seb128> which means next time we have no idea of the logical changesets
[13:13] <james_w> well, the aim would be that next time there are no changes
[13:14] <james_w> and I'll make bzr branches anyway
[13:15] <persia> I think the best strategy here depends on the class of package.  For those packages where we *always* carry a change (e.g. branding, menu cleanup, launchpad integration) it makes sense to logically differentiate the patches, even if this makes merging different, because that way we can easily reapply the stuff that always needs to be applied.
[13:16] <persia> For those packages where we *can* be in sync with Debian, keeping track of all that is just overhead, because we ought to get the right stuff into Debian anyway.
[13:16] <ion_> liw: So... :-)
[13:16] <liw> ion_, still digging, but I'm seeing light at the end of the tunnel already
[13:16] <ion_> :-)
[13:17] <ion_> Already got the amulet of Yendor from the bottom?
[13:17] <asac> james_w: so where can i find your latest daily build tools?
[13:17] <liw> that would be a reference to the game I played for an hour without realizing it had more than one level
[13:17] <james_w> asac: bzr-builder on launchpad
[13:17]  * asac checks that
[13:17] <asac> thx
[13:18] <ion_> Heh
[13:35] <cjwatson> sbeattie: I can't manage to reproduce bug 250400; simply unsetting HOME and running make-ssl-cert in the same way as ssl-cert.postinst runs it doesn't seem to be sufficient. Obviously this is holding me up from uploading a fix. I don't suppose you might have a moment to see if you can reproduce it?
[13:44]  * macvr wonders if any dev is working on a gui for sound the equalizer ...
[15:03] <wip> still many problems with the RT-kernel
[15:05] <persia> Indeed.  It doesn't even boot properly.  Of course, if I didn't already know that, your report wouldn't be helpful in that format, but you've already left :)
[15:06] <ogra> heh
[15:06] <ogra> he does that once a week
[15:06] <ogra> i wonder if its a script :P
[15:08] <persia> Hard to say.  I suspect -rt would be more likely to work if there had been more communication earlier.
[15:09] <ogra> or at all :)
[15:09] <ogra> beyond a guy joining here once a week, saying a sentence and signing off .... post-release :)
[15:10] <persia> Oh, that was about jaunty?  I thought it was about karmic.  The jaunty -rt worked the last time I tried it (although that may have been a late alpha, rather than a beta).
[15:11] <ogra> well, the last times i saw him here he complained about jaunty rt
[15:11] <ogra> always signing off immediately after that :)
[15:11] <mterry> slangasek: OK, so I'm going to look into getting rid of acpi-support's ac.d and battery.d unless you cry foul
[15:11] <persia> Right.  Internet Relay Microblogging.
[15:11] <ogra> heh
[15:16] <superm1> slangasek, i'm still frazzled, that meta package now explicitly calls out grub-pc, but the livefs still came out with grub and grub-common
[15:17] <superm1> slangasek, oh wait, nvm, grub-common is there and grub-pc is, not normal grub. so it's right this time
[15:26] <robbiew> james_w: ping
[15:26] <james_w> hey robbiew
[15:27] <robbiew> james_w: are u still waiting on feedback on the kerneloops stuff?
[15:27] <james_w> robbiew: yeah, I'm interested if my idea is the right way to go about it
[15:28] <james_w> well, firstly if indirecting through apport is the right thing to do
[15:28] <james_w> and then if that's the right way to do it
[15:28] <robbiew> james_w: FWIW, I think so, but cjwatson is probably a better person to ask :P
[15:28] <robbiew> technically speaking
[15:28] <james_w> there's no real rush though
[15:28] <robbiew> okay
[15:28] <cjwatson> it's open in my browser, in my queue of stuff to review
[15:28] <robbiew> james:w: just didn't want you blocked on a response from me
[15:29] <james_w> thanks
[15:29] <robbiew> heh...my browser queue got so long, firefox crashed...that is when I had to split the blueprints based on priority :P
[15:29] <cjwatson> I'm just trying to get my own specs written before reviewing everyone else's, plank in one's own eye etc. :-)
[15:29] <james_w> heh
[15:40] <alex-weej> about 3 nights ago Apport did some serious email spammage removing coredumps from bug reports -- anyone know what that was all about?
[15:40] <alex-weej> actually it was 2 nights ago
[15:42] <seb128> alex-weej: it was about removding coredumps from duplicates
[15:42] <seb128> alex-weej: they take space and can contain sensible informations
[15:44] <alex-weej> ah ok
[15:44] <alex-weej> (you mean sensitive btw :P)
[15:55] <directhex> alex-weej, both!
[15:55] <alex-weej> ;)
[16:24] <tkamppeter> seb128, about bug 258421
[16:25] <tkamppeter> seb128, saw your last comment now, thanks.
[16:27] <kees> whoa.  vte corrupted "N" (upper-case n)
[16:34] <sbeattie> cjwatson: re bug 250400 I have a vague recollection of being unable to reproduce it as well.
[16:34] <sbeattie> but I'll give it another go.
[17:45] <cjwatson> cking: can you get us anything more on bug 385916? we can't do anything with it as it stands. If you can reproduce it, the files we actually need from the running installer are /var/log/syslog and /var/log/partman
[17:47] <cking> cjwatson: I will reproduce it and attach the appropriate logs
[17:47] <cjwatson> thanks
[17:48] <cking> it's kind of hard to know what to attach. Maybe next time I tar up all of /var/log..
[17:48] <cjwatson> in general, for installer bugs we only need /var/log/syslog /var/log/partman and possibly /var/log/installer/debug
[17:48] <cjwatson> everything else is duplicated or useless
[17:49] <cjwatson> to a first approximation anyway
[17:49] <cking> OK. Will note that down.
[17:49] <cjwatson> shame apport failed, could be the filesystem is a bit busted
[17:49] <cking> I'm worried it's due to re-sizing an already existing ext4 fs
[17:54] <cjwatson> cking: you said it was near the end though, wouldn't that be after partitioning?
[17:55] <cjwatson> or was that not what you meant?
[17:55] <cking> oh yes. I didn't think that through
[17:56] <cjwatson> well, depends what you meant by "end" I guess :)
[17:56] <cjwatson> could be 385995 although I'm surprised at that causing ubiquity to blow up like that rather than display a "help me" dialog
[17:57] <cjwatson> oh, actually it might
[18:10] <cking> ..reproducing this is taking sometime.. hopefully done in 10 more mins
[18:19] <cking> bother.. did not reproduce it that time. Trying again.
[18:35] <slytherin> cjwatson: tuxguitar builds fine locally. So the texlive-base issue that causes FTBFS for tuxguitar is surely powerpc buildd problem.
[19:00] <mterry> apw: Can you give me some pointers on how pm-powersave is supposed to be called with our new devicekit-power overlords?  I gather it used to be called by gnome-power-manager?
[19:03] <apw> mterry, i though pre devicekit that gnome-power-manager sends out dbus requests, which hal picks up and runs the pm-* stuff
[19:03] <apw> not sure how that is changed by devicekit
[19:03] <mterry> apw: Correct
[19:04] <mterry> apw: OK.  Current g-p-m seems to no longer call anything similar.  Trying to trace it down.
[19:04] <mterry> apw: I'm assuming that pm-utils still has a place in this new scheme?
[19:05] <apw> as i understand things it is still called to suspend stuff, right now devkit isn't passing in the quirks i believe
[19:10] <mterry> apw: Yeah, OK.  There are analogous Suspend and Hibernate calls in dk-p that call pm-suspend and pm-hibernate.  Just seems that SetPowerSave is missing.  I'll ask upstream what the intention is
[19:10] <ion_> The open source driver for my new laptop’s WLAN adapter doesn’t support this model, but is still able to upload the firmware to it. The proprietary driver “works”, but seems unable to upload the firmware. rc.local: modprobe (free driver), modprobe -r (free driver), modprobe (evil driver), and i can has networking. :-D
[19:13]  * hyperair claps. now, did we really need to know that?
[19:21] <sbeattie> cjwatson: commented on bug 250400, I managed to reproduce manually.
[19:25] <cking> cjwatson: log files attached to bug report
[19:56] <mterry> slangasek: ping about power management when you get the chance.  I'm curious if pm-utils is an accepted part of the new world order, or if we want to move all of its power.d scripts to be some part of udev
[19:56] <slangasek> mterry: yes, pm-utils isn't supposed to go away
[19:57] <tkamppeter> pitti, can you have a look at bug 385606?
[19:57] <tkamppeter> pitti, seems that ghostscript-cups needs to be added to one of the seeds, so that it gets pulled into updates of both desktop and server.
[19:57] <mterry> slangasek: OK, cool.  So, do you happen to know much about devicekit-power and its lack of calling pm-powersave?  It's not in the dbus API.  Thinking we'll have to call pm-powersave in acpi-support now
[19:58] <slangasek> mterry: we definitely shouldn't be calling it in acpi-support, which is slated for execution.  You might want to check with pitti about where it's supposed to wind up
[19:59] <mterry> slangasek: Well.  OK.  Where are the bits of acpi-support that are 'methods of last resort' when a power-manager isn't running slated to end up?
[20:00] <slangasek> mterry: when we get to the point that those are the only thing left, we should be able to unseed acpid and acpi-support from the desktop
[20:00] <slangasek> arguably there should be some console-friendly power manager to replace them, that also hooks in via devicekit
[20:00] <slangasek> but I don't know that anyone's working on this
[20:00] <mterry> slangasek: Agree, but I'm not writing it.  :)
[20:01] <pitti> mterry: hm, sounds worth an upstream bug report, I think
[20:01] <pitti> mterry: it sounds like something dk-power could handle, but I'm not 100% sure
[20:02] <mterry> pitti: Yeah.  I was going to ask the mailing list.  There's the fear that it might be intentional and dk-p won't do it.  I need upstream clarification
[20:02] <pitti> mterry: devkit-devel@ is a great place to ask, too
[20:02] <pitti> mterry: I'm not a DK guru yet myself, I'm afraid
[20:03]  * pitti -> off again
[20:03] <mterry> slangasek: We can drop it from the seed once the user is never left w/o a manager.  I assume that means when we switch to new GDM?
[20:03] <slangasek> mterry: yeah, I suppose so
[20:04] <slangasek> (right, GDM, argh)
[20:04] <tkamppeter> pitti, you are aware that if you make cups depending on ghostscript-cups, you create a circular dependency?
[20:05] <pitti> tkamppeter: eww, why does ghostscript-cups depend on cups? that sounds backwards
[20:05] <infinity> pitti: Because it's useless without it, I'd assume?
[20:06] <pitti> *shrug* /me demotes to Recommends
[20:06] <tkamppeter> ghostscript-cups provides PPD files, so it updates PPDs of existing queues. For updating PPDs of existing queues cups and cups-client are required.
[20:06] <infinity> pitti: Not that circular deps in such low priority packages are a huge deal.  dpkg will just randomly unroll the loop.
[20:07] <pitti> yeah, but still..
[20:08] <pitti> I still think it's more logical for cups depends: ghostscript-cups and ghostscript-cups recommends: cups
[20:08] <infinity> pitti: If it actually calls cups bits, it kinda needs to be a dependency, policy-wise.
[20:09] <tkamppeter> pitti, but what happens than on a distro upgrade (or any update where both cups and ghostscript-cups get updated)? Will the CUPS daemon be running when the postinst script of ghostscript-cups is run?
[20:10] <infinity> Oh eww, if they need to be configured in a specific order, then you can't have a loop. :/
[20:10] <pitti> tkamppeter: yes, with the dependencies being this way around
[20:11] <infinity> pitti: Which way around?
[20:11] <pitti> g-cups depends: cups
[20:11] <pitti> and cups recommends: g-cups
[20:11] <infinity> pitti: Ahh, you wrote it the other way above.
[20:11] <pitti> cups' postinst doesn't do anything magic wrt. detection, so that should be fine
[20:11] <pitti> infinity: right, it would seem more logical the other way round
[20:11] <tkamppeter> pitti, CUPS itself does not need ghostscript-cups, if you have only PostScript printers and/or printers using Foomatic, you do not need ghostscript-cups.
[20:12] <pitti> but the other drivers also use this order
[20:12] <pitti> tkamppeter: okay, so recommends makes sense
[20:12] <pitti> similar to cups-driver-gutenprint
[20:13] <tkamppeter> So I would then rather add a "Depends: ghostscript-cups" to all CUPS Raster drivers, currently splix, gutenprint, and hplip-cups.
[20:14] <tkamppeter> The reporter of bug 385606 most probably uses splix, and so the dependency in splix wiull pull ghostscript-cups for him.
[20:14] <tkamppeter> pitti, so put a Recommends: into cups, leave ghostscript-cups alone, and I add a Depends: to the CUPS raster drivers.
[20:17] <tkamppeter> pitti, for updates the default-installed CUPS Raster drivers will pull ghostscript-cups then ...
[20:29] <mterry> slangasek: What's the deal with Debian's and Ubuntu's versions of acpi-support?
[20:30] <ogra> they should die die die ?
[20:31] <mterry> :)  I mean, they seem different?  Are they downstream from us?
[20:32] <ogra> no, slangasek reworked most of it in jaunty ...
[20:33] <ogra> we once were upstream (mjg59 was upstream ... he moved to RH and the package upstream moved to debian ...)
[20:33] <ogra> iirc
[20:41] <slangasek> mterry: they're not a very participitory downstream.
[20:57] <cjwatson> sbeattie: thanks!
[22:28] <calc> shtylman: good job! just saw your post to ooo-build :)
[22:36] <shtylman> calc: thanks...yea...I hit a wall and needed someone with a bit more installation experience...once they figure that out I can finish up the last few details
[22:38] <calc> shtylman: ok :)
[22:39] <calc> shtylman: i need to get the oxygen icon set integrated soon as well, maybe by the time i have time to do the next upload both will be ready :)
[22:39] <shtylman> calc: that would be cool
[22:39] <shtylman> calc: do you have a fixed day for that...I can try to aim to get this work done by then...(other things aside)
[22:44] <calc> shtylman: no just whenever after alpha 2, preferably before alpha 3
[22:44] <calc> rickspencer3: hi
[22:45] <shtylman> k
[22:49] <rickspencer3> calc: hi
[23:53] <XCP> hi. fresh install of ubuntu 9.04 here. and update-motd runs every 10 minutes on my computer. how ridiculous is this? is this intended?
[23:56] <ryanakca> XCP: Just a stab in the dark, but could it be to update the MOTD to include ``X updates available, Y security updates available"?
[23:57] <XCP> ryanakca: cat /etc/motd does not reveal this kind of information. it does not seem to have any variable part at all.
[23:58] <persia> That shouldn't have to run every 10 minutes.
[23:58] <directhex> how about every 11?
[23:58] <XCP> the reason why I brought this up in the devel channel is because maybe it's something that has been forgotten and could be fixed.
[23:58] <persia> XCP, /etc/motd is just output.
[23:58] <geser> isn't update-motd responsible for the updates?


[01:46] <verrueckter> hay
[01:58] <bonafide> Hi, is anyone up? I've a quite particular question on how to redirect Mixxx-Master-Output to the internal Microphone.
[01:59] <bonafide> I've already outlined the problem here, in the ubuntu- and mixxx-irc. the latter sent me here.
[01:59] <bonafide> http://www.mixxx.org/forums/viewtopic.php?f=3&t=6098&p=21265#p21265
[02:29] <fibz_> have you tried the patchbay in qjackctl ?
[02:30] <fibz_> there is also #opensourcemusicians
[02:31] <bonafide> no, i dont use jack since im on ubuntu 12.04. i just tried asking you guys for the expertise. im looking for a cure on alsa-level if thats possible.
[02:32] <bonafide> okay. ill try it there. thank you.
[02:32] <bonafide> but if you know about sound in linux id highly appreciate your help and document it in my forum.
[02:32] <bonafide> i really want to get into linux audio production.
[02:43] <bonafide> @fibz_ not?
[02:47] <fibz_> i'm not familiar with Mixx but i have a feeling qjackctl's patchbay will let you pipe the audio from mixx to microphone
[02:49] <bonafide> how bad can jack (qjackctl is a jack utensil i suppose) mess up my configuration?
[02:50] <fibz_> i haven't had any problems with combining it with pulse and alsa
[02:52] <bonafide> cool! but still: i use a bluetooth audio sink. this is said to cause serious trouble with jack.
[02:52] <bonafide> (or the other way around...)
[03:07] <bonafide> thank you
[11:40] <bonafide> Hi, how do I route Mixxx' Master-Output to the internal microphone?
[14:24] <holstein> bonafide: i use JACK
[14:24] <holstein> but, routing the ouput of something to a mic wont work
[14:52] <holstein> maybe you are trying to use a mic with mixxx.. that would be much more likely
[14:52] <holstein> or, maybe you are trying to route audio to a mic ouput as if you had more channels on an internal device
[14:52] <holstein> that wont work either, unless the hardware were to support that, and had multiple channels out
[15:19] <bonafide> holstein: I have a bluetooth adapter for the master output and an internal soundcard for headphones, maybe it works with an external soundcard?
[15:19] <holstein> bonafide: no.. it works with bluetooth
[15:19] <holstein> bonafide: alsa will support it as best it can.. and JACK will show routing options
[15:20] <holstein> bonafide: but, trying to route sound output to a mic is not correct
[15:20] <holstein> i feel i am either misunderstanding you, or not getting the full story
[15:20] <holstein> feel free to just back up and state exactly what you are trying to do
[15:22] <bonafide> holstein: hm. i want to do djing in mixxx while simoutanously streaming it to a flash-application the browser like soundcloud-live-recording or a videochat.
[15:22] <bonafide> i outlined it here: http://www.mixxx.org/forums/viewtopic.php?f=1&t=6108&p=21274#p21274
[15:22] <holstein> bonafide: i would remove the flash from teh equation
[15:23] <holstein> one thing i might do, since i have a bunch of hardware laying about is.. build a streaming appliance
[15:23] <holstein> then, route to that analog for streaming
[15:23] <holstein> the streaming appliance wouldnt be running JACK
[15:23] <holstein> i would then just use mixx normally on one machine, with the mic running for VO
[15:24] <holstein> then, take a cable and route all of that via an analog connection to the streaming appliance
[15:24] <holstein> otherwise, to do it with one machine, i would want to test streaming independently.. using the pulse-jack dbus
[15:24] <holstein> then, i would just route a mic to mixxx and get that streaming
[15:25] <holstein> *then* introduce whatever bluetooth equipment
[15:25] <holstein> otherwise, you are troubleshooting many many things at once.. and none of the equipment has likely promised JACK, linux or pulseaudio support
[15:26] <mlpug> I guess one does not even see mic as input in jack
[15:26] <mlpug> I mean output
[15:26] <holstein> shouldnt
[15:26] <bonafide> analog connection = mixxx-machines-output via cable to the microphone in of the streaming-machine?
[15:27] <bonafide> like this, holstein?
[15:27] <holstein> bonafide: i suggest this because its a work around i used with my firewire device years ago
[15:27] <holstein> bonafide: i used a seperate machine running only pulseaudio and BUTT to stream to icecast.. then, an analog cable from my audio rig from my firewire device
[15:28] <bonafide> sound decent.
[15:28] <bonafide> i didnt expect it so be so much trouble
[15:28] <holstein> bonafide: ?
[15:28] <holstein> bonafide: does the hardware promise you linux support?
[15:29] <holstein> bonafide: if not, then you are accepting the support role yourself.. and its not always trivial
[15:29] <holstein> bonafide: there are *many* ways to do what you are suggesting. but, you will not be able to route audio outputs to microphones
[15:30] <holstein> for me, it was a matter of simplicity.. i didnt need JACK running to stream, so i didnt use it
[15:30] <bonafide> holstein: thank you a lot for your help.  the idea with the second machine is very good.  i'd like to have a clean setup as well and will rather go for this one than for the one with jack.
[15:31] <bonafide> holstein: the hardware is of course not labeled "linux support".
[15:32] <bonafide> holstein: when i started the thread, I thought someone will come up with a simple command for alsa. didnt want to discredit your solution.
[15:32] <holstein> bonafide: there is no solutino to routing audio to microphones
[15:32] <holstein> bonafide: you just cant do it
[15:32] <holstein> if i were going to do what you are doing, i might not use JACK at all
[15:33] <holstein> i might just setup a mixer.. route whatever sources to that i want (ipods, phones, tapedecks, whatever) and my microphone.. then, route that to the streaming appliance
[15:34] <holstein> if i dont want to record the audio, i try and not bring it in, or route it through the computer
[15:36] <holstein> I'd like to stream my Mixxxes to various Applications like the the browser (soundcloud recording, videochat) or Skype.
[15:36] <holstein> ^ you would use the included pulse-jack dbus
[15:36] <holstein> pulseaudio shows up as send and recieve.. you route what you like to it
[15:36] <holstein> So. How do I redirect my Master-Output from Mixxx to the Microphone?
[15:36] <holstein> ^ you dont
[15:37] <holstein> and, you shouldnt need to
[15:37] <holstein> you are asking "how to get the audio into the browser?".. not send the audio to a mic
[15:37] <holstein> and, the way you would do that is with the pulsejack dbus
[15:37] <holstein> but, i would expect issues with flash, and suggest a streaming appliance still
[15:38] <holstein> though, im not sure i would use mixxx or jack at all..
[15:38] <holstein> feel free and check with #opensourcesmusicians
[15:40] <bonafide> these are some very nice thoughts. thank you. i think ill just use the hardware workaround. jack is to much of a risk for me.
[15:41] <holstein> bonafide: i really think its ideal not to use it, if its not required
[15:41] <holstein> bonafide: not that JACK isnt awesome :)
[15:41] <holstein> i love it and use it a lot, but if its overhead isnt required...
[15:43] <bonafide> I'm quite new to linux-audio. I think, Ill use JACK in a different setup in the future (ardour x jack x mixxx x and some nice hardware parts) but for now im fine with the workaround.
[15:44] <bonafide> holstein
[15:44] <bonafide> thanks a lot.
[15:44] <bonafide> are you here frequently?
[15:44] <holstein> bonafide: sure.. anytime!
[15:44] <holstein> i try and be logged here all the time
[15:44] <bonafide> ill come back and tell you about my experience in building it.
[15:44] <bonafide> and share it as well in the mixxx forum.
[15:44] <holstein> bonafide: please do let us know.. and if you need other options/suggestions
[15:45] <bonafide> i certainly will. really. heartfelt thanks from me again. passing on this kind of knowledge is so important.
[15:45] <bonafide> <3
[15:45] <bonafide> see you in a bit
[17:53] <em> any word on when the 14.04 beta will be available?    I've got a couple of machines I want to upgrade asap
[17:54] <holstein> em: the 14 is 2014.. the .04 is april
[17:54] <holstein> !14.04
[17:55] <holstein> em: ubuntu releases, or at least has agreed to release so far, a release every 6 months
[17:55] <holstein> with an LTS (long term support) release every 2 years
[17:55] <holstein> !lts
[17:55] <holstein> 14.04 will be an LTS
[17:56] <em> any idea why the volume control for 12.10 was NEVER FIXED???   besides being annoying as all hell  it makes ubuntu  look really bad,  I can't/won't  put new users on it because of that.  and now users are getting these really annoying warnings about 13.04 being end-of-life-you-must-upgrade...
[17:56] <holstein> em: nothing is "broken" here, friend
[17:56] <holstein> 12.10 is EOL
[17:56] <holstein> !12.10
[17:56] <holstein> lol
[17:56] <holstein> its eol now
[17:57] <em> hlostein please do not answer any of my questions you have already established yourself as a person who DOES NOT KNOW WHAT THEY ARE TALKING ABOUT
[17:57] <holstein> em: 13.04 is EOL as well
[17:57] <holstein> em: they are factually end of life, friend
[17:57] <holstein> !volunteers | em
[17:57] <em> duh no sh***shutup and let an intelligentt person talk
[17:57] <cfhowlett> em - respectfully suggest you dial down the attitude immediately
[17:59] <holstein> em: i do apologize that you seem to be experiencing some issues thare you are finding frustrating, but i assue you, im only stating facts
[17:59] <holstein> em: 13.04 *is* end of life
[17:59] <holstein> those "annoying" messages are notifications to the same effect..
[18:00] <em> facts that are completly irrelevant to the question being asked!!!!    is English a foriegn language for you???  becausee you seem t have severe problems with comprehension
[18:00] <holstein> em: the reason the volume control wasnt "Fixed" in 12.10 is likely becuse it wasnt broken, friend
[18:00] <holstein> em: its likely just an issue with alsa and the support of your particular device
[18:01] <holstein> but, if you would like to speack constructively about current support, i would be glad to help
[18:01] <holstein> speak*
[18:02] <em> oops... correction...  when I said 12.10 I meant 13.10  but anyone who is knowledgeable would have realiszed that i was talking about the very blatently broken volume control in 13.10 because that is the only version where this problem exists
[18:02] <holstein> em: what is the  specific issue?
[18:08] <holstein> i would try and isolate if its an issue with the drivers (alsa) and or kernel version supporting the hardare, rather than the volume control being broken
[18:09] <holstein> either one warrants a bug report.. and thats where i would start.. a bug report relating to my specific hardware case
[18:11] <holstein> either creating one for finding an existing one.. upstream as well, if possible
[18:19] <em> @holstein  you dont know the difference between a virtual box and a hardware computer....   you also dont seem to know when the 2014 beta is going to be released, you also dont seem to know anything about the very broken volume control in 13.10   so why are you insisting on providing useless non-answers?
[18:20] <cfhowlett> em, support and questions about 14.04 belong in #ubuntu+1
[18:20] <em> @holstein  have you ever actually run 13.10???   I am betting that the answer is no....   because if you had run it then you would know what I am talking about without having to ask.
[18:20] <holstein> em: https://wiki.ubuntu.com/TrustyTahr/ReleaseSchedule
[18:21] <holstein> ^ that should give you all the dates you need for 14.04
[18:21] <em> cfhowlett   thatnks  I will try there
[18:21] <em> holstein THANK YOU   for succeeding in being helpful
[18:22] <holstein> em: sure.. i just dropped "ubuntu 13.10 release schedule" in a search window
[18:22] <holstein> em: what specifically is the issue with your sound control in 13.10? since i dont seem to have the same issues
[18:22] <em> okay, fine, but the ubuntu STUDIO does not always track the main release
[18:23] <holstein> ubuntustudio *is* ubuntu.. we only skip one milestone AFAIK
[18:24] <em> the problem with the sound control in 13.10 is that the volume control widget/applet on the panel is not clickable and does not function
[18:25] <holstein> you can go upstream with that, since its not related to ubuntustuduio specificially
[18:26] <holstein> em: if you share your audio hardware specs, id be glad to help search for a bug, as i stated above, for your specific hardware
[18:27] <em> fine...  but there are already a zillion people who have seen it and no doubt reported it.   I even seem to recall that it was mentioned in the release notes.  there is no point in me duplicating that effort.
[18:28] <em> it's been broken on every computer Ive tried it on....  multiple different hardware
[18:29] <em> it's even broken inside of virtualbox....
[18:29] <holstein> !bug | em
[18:29] <holstein> em: just file, and share the link, and i'll follow up and confirm it
[18:31] <em> @holstein,  tell me about yourself, how do you fit in to the eco system?  what sort of follow up are you capable of doing on a bug report?
[18:32] <em> what is your area of knowledge?
[18:32] <holstein> em: its a community, friend. i would be able to confirm the results, and report on  the bug.. i could share on the publically accessible email list and ask for assistance
[18:32] <holstein> em: its a process outlined above that has nothing to do with me
[18:33] <holstein> em: as the link i gave before states, i a volunteer here.. you are welcome to do what you like.. go upstream, go to the devel channel or list
[18:34] <holstein> em: i will assist you getting whatever you need.. thats what i do..
[18:34] <em> yes, that's what I thought, in other words you are like a friendly puppy, all excited about being friendly and helping out, but not actually knowing anything useful.
[18:35] <holstein> em: you are free to search whatever you like or need on me, friend
[18:35] <cfhowlett> em a simple "No thank you" would have sufficed.
[18:35] <holstein> em: i will get you assistance.. if the volume control is broken, you will outline the process, and i will confirm it, and look upstream as needed for asssistance
[18:36] <holstein> em: i assure you, i am not a code contributor.. if you are, or are interested in helping us with code, that would be much appreciated
[18:37] <em> thanks, but I really just wanted to find out when the beta is being released
[18:37] <em> bye
[18:37] <holstein> em: good luck.. just don spread FUDD
[18:37] <cfhowlett> !beer|holstein,
[18:38] <holstein> drag.. now that guy is saying the volume control is broken.. still
[18:38] <holstein> whatever...
[18:38] <holstein> cfhowlett: rough ;)
[18:38] <cfhowlett> holstein, you're a better man than I am.  Thanks for setting the example in the face of - whatever that was.
[18:39] <holstein> cfhowlett: i think its mostly just tech support issues.. folks dont think of this as community support.. its tech support, which is frustrating, typically
[18:40] <holstein> in actually, we have a community here that one could join and fix what they like.. but whatever
[18:40] <cfhowlett> holstein, granted but still no excuse for abuse or a**holery


[00:55] <amgad> i have a nexus 7 grouper..
[00:56] <amgad> is there any manually way to install Ubuntu touch on it ?
[02:59] <kirk_> Anyone know if it is possible to run ubuntu-touch style UI desktop or server?
[06:36] <popey> Anyone seen a bug for http://imgur.com/Vxqtkkl that yet?
[06:37] <lotuspsychje> not me
[06:38] <lotuspsychje> popey: could it be your providers side?
[06:38] <popey> uh
[06:38] <popey> I'm talking about the giant icon
[06:38] <lotuspsychje> mine says proximus + network triangle
[06:38] <popey> we have had a few people report it here
[06:38] <popey> the gigantic H
[06:38] <lotuspsychje> yes i see it
[06:39] <lotuspsychje> shouldnt that show your providers name?
[06:39] <popey> no
[06:39] <popey> its H for HSDPA
[06:40] <Stskeeps> popey: well, at least you're acutely aware what speeds you might get :P
[06:41] <popey>  😃
[06:50] <popey> http://popey.com/~alan/screenshots/device-2016-05-30-075036.png is what it should look like
[06:53]  * duflu is reminded much work is required to make Unity8 look as nice as Unity7 at low DPI
[07:46] <mardy> dpm: hi! I need some help with developer.ubuntu.com, please ping me when you have a minute
[07:46] <dpm> mardy, sure, how can I help?
[07:46] <mardy> dpm: our guide has been deleted :-(
[07:46] <mardy> dpm: title was "Online Accounts guide - 15.04.1 and newer"
[07:47] <dpm> let me see...
[07:47] <mardy> dpm: I see it in the list of "recover deleted pages", I see it was deleted on November 2nd
[07:47] <mardy> dpm: but I don't know how to recover it
[07:52] <dpm> mardy, let me follow up on e-mail
[07:53] <mardy> dpm: ok
[08:05] <davidcalle> mardy: is that different from https://developer.ubuntu.com/en/phone/platform/guides/online-accounts-developer-guide/
[08:07] <mardy> davidcalle: quite a bit
[08:07] <davidcalle> mardy: ok
[08:07] <mardy> davidcalle: http://webcache.googleusercontent.com/search?q=cache:Zi7lUs9XY2IJ:https://developer.ubuntu.com/en/online-accounts-guide-15041/%3Fcp%3Dclose&num=1&hl=en&strip=0&vwsrc=0
[08:11] <mardy> davidcalle: you can see that this page has another link for Online Accounts between parentheses, but it seems to be broken: https://developer.ubuntu.com/en/phone/platform/guides/
[08:11] <davidcalle> mardy:  is the cached content correct? Not sure what happened to the page, I'm going to ask IS for logs.
[08:11] <mardy> davidcalle: let me double check
[08:12] <mardy> davidcalle: I don't have the source, I created the page directly on d.u.c, so I believe that the cached page is the best thing I have right now
[08:13] <davidcalle> mardy: should this guide replace the one that's still published ^
[08:14] <mardy> davidcalle: I'd say so, yes
[08:30] <davidcalle> mardy: fixed, sorry about that.
[08:30] <davidcalle> dpm: ^
[08:31] <dpm> great, thanks davidcalle - did you figure out what the issue was?
[08:32] <mardy> davidcalle: thanks a lot! Did you recover the page, or did you copy the contents from the cache?
[08:32] <davidcalle> dpm: not yet
[08:32] <davidcalle> mardy: cache
[08:33] <mardy> ouch :-)
[08:34] <davidcalle> mardy: well, it exists for a reason :
[08:34] <davidcalle> :p*
[08:37] <dpm> thanks davidcalle for being creative, that at least got us back the page in no time while we're figuring out the issue :)
[08:37] <davidcalle> mardy, dpm, actually, I haven't tried to recover, I have a list of page updates (similar to https://developer.ubuntu.com/translations-dashboard/)  that I checked to see if there was an edit more recent than the latest cache, there wasn't.
[08:38] <dpm> ok, cool, so we've indeed lost no edits
[09:43] <crs___> it would be nice if the filemanager could receive .vcf files from the content hub. right now i can only select the messegaing app and dekko.
[09:43] <crs___> but i dont want to send the file. i want to save it, thats all
[09:48] <popey> i guess in theory the file manager could receive any kind of file to save it
[09:48] <popey> s/could/should/
[09:49] <crs___> but why doesn't it ?
[09:50] <popey> good question :)
[09:50] <crs___> i think it really should accept any file :)
[09:52] <crs___> there is also another small thng that annoys me since my first day with ut. that is, that the right edge gesture includes the app launcher. the app launcher has its very own gesture (left edge swipe).
[09:53] <CedArctic> Hello :)
[09:53] <CedArctic> I am trying to port UT to the Xperia Z3
[09:53] <CedArctic> and I have some questions
[09:54] <CedArctic> About the device tree, what branch should I use Lollipop? And also can I use the CyanogenMod device trees or should I go for AOSP?
[09:54] <crs___> so now you basically have 4 ways to get to the launcher. i think that is a waste of precious shortcuts
[09:55] <crs___> and also, especially for short right edge swipe. the app launcher always gets in your way
[09:58] <crs___> CedArctic: once i tried to port to lenovo z1. i failed because i couldn't geht the binary blobs to work with ut
[09:59] <CedArctic> Hmm I haven't gotten there I am still downloading the sources
[09:59] <crs___> CedArctic: the binary blobs were compiled for android 5.1 while ut is based on 4.something
[10:00] <CedArctic> Hmm I do have official kitkat builds
[10:01] <crs___> then i think you should extract the blobs from kitkat and maybe you will have more luck than i had
[10:02] <CedArctic> OK will do
[10:02] <crs___> there is also a project called ubports, they are working on a 5.1 based ubuntu touch. i dont know how much progress they made
[10:03] <CedArctic> Interesting
[10:04] <crs___> good luck ;) you will notice that it is almost impossible to get help with porting ;)
[10:06] <CedArctic> Yeah...  I would like to find a ubuntu smartphone, do you know where I can find it ?? it's strange every website is out of stock...
[14:19] <CedArctic> You could check out swappa for a used one
[14:20] <yakaar> do you know if BQ stopped the production ?? it's strange...
[14:22] <ogra_> https://store.bq.com/en/ubuntu-edition-e-4-5/
[14:23] <ogra_> https://store.bq.com/en/ubuntu-edition-e5/
[14:23] <ogra_> ah, the latter is out of stock (temporary i guess)
[15:05] <Jarlath> I don't see a bug for the app-store not completing installations on unity8 desktop here: bugs.launchpad.net/ubuntu/+source/unity8
[15:05] <Jarlath> Should I go ahead and file a bug?
[15:05] <ogra_> you mean on a PC ?
[15:11] <Jarlath> ogra_: yes
[15:11] <Jarlath> 16.04
[15:12] <Jarlath> Unless I haven't purged the ppa correctly, I believe I can log in to a U8 desktop session :)
[15:16] <Jarlath> Going to try a reboot actually, I think the last time I ran a ppa-purge I noticed the difference after a reboot.
[16:14] <taiebot> Hi all am i the only one having this bug with the browser app?  When i type in the search bar there is some history suggestion. With a header (website name and below the address) well most of the time they do not match between each other. the address being the right one
[16:35] <brunch875> I've never had that happen to me
[17:11] <brunch875> There's something I absolutely love about utouch and that's pulling out the emoji keyboard as a "language"
[17:12] <brunch875> I wonder if it's possible to get such layout on the desktop too
[17:12] <brunch875> so that I don't have to memorize all the unicodes and ctrl-shift-u
[17:26] <brunch875> Uh oh!!!! On calendar trying to sync with google calendar after I changed gmail's password: "Blah blah key is invalid. Reauthenticate?" Yes → Phone soft-reboots
[17:27] <brunch875> Retried again; phone crashes again
[17:51] <mimecar> hi
[17:55] <saavento> hi mimecar
[17:55] <mimecar> good evening saavento
[18:06] <mariogrip> mhall119: ping
[18:23] <popey> brunch875: ahh! I have seen that too, I think i filed a bug
[18:23] <popey> brunch875: let me find it
[18:24] <brunch875> oooh great popey! I did just run ubuntu-bug and was launching the browser to file it
[18:24] <popey> brunch875: bug 1578601
[18:24] <popey> brunch875: it seems you have a way to reproduce it, by changing password, please add that detail
[18:25] <brunch875> neato
[18:25] <brunch875> I found an even easier way
[18:25] <brunch875> just revoke access from google accounts
[18:27] <brunch875> popey, by the way: where did you get the crash dump from? It'll be handy to add it to posterior bugs
[18:29] <popey> from /var/crash
[18:29] <popey> also, once your crashes have been uploaded, you can see them if you go to system settings -> security & privacy
[18:29] <popey> there's a button which launches web browser with a special errors.ubuntu.com url
[18:30] <popey> adb shell or ssh to the phone, grab that url from "ps aux | grep webbrowser" and you can browse it on your desktop
[18:30] <popey> handy for seeing all your own crashes
[18:32] <brunch875> cheers!
[18:38] <brunch875> Well, it seems I could edit your bug, so I just added the means to reproduce it there :P
[18:39] <brunch875> changing password would work too, but it's a pain in the ass since you can't change the password back because "it was used recently"
[19:50] <zub> I can't install ubuntu-sdk-15.04 click chroot. Has anybody tried recently? I think there are deps broken in the repo.
[21:00] <zub> so it seems Im hitting https://bugs.launchpad.net/ubuntu/+source/oxide-qt/+bug/1543215
[21:08] <DPR_> have a problem with ubuntu desktop not touch.
[21:08] <DPR_> Am i in the right place?
[21:09] <DPR_> ???
[21:11] <k1l> DPR_: no. for ubuntu desktop better ask in #ubuntu


[00:00] <Silverlion> good night every one!
[07:54] <dholbach> good morning
[13:24] <akgraner> Hi all I won't be able to write summaries until tonight sometime - so if someone else can take a stab at it that would be great
[13:24] <akgraner> pleia2, I'm ok with publishing Wed if we need to so we don't rush and miss something
[18:25] <pleia2> akgraner: wednesday sounds good
[18:25] <pleia2> I'll finish gathering news today
[18:25] <akgraner> pleia2, great - then let's plan on that
[18:25] <akgraner> I'm catching up with work today
[19:01] <bkerensa> hmm
[19:01] <bkerensa> I can write some summaries
[19:01] <bkerensa> akgraner: still needed?
[19:01] <akgraner> bkerensa, thanks - just take a look at the gdoc
[19:02] <bkerensa> k
[19:02] <akgraner> pleia2, will be adding more links throughout the day - I won't get to write any summaries until tomorrow sometime - pleia2 and I both were at SCALE all weekend
[19:03] <pleia2> was pretty impossible to do anything on the hotel wifi :)
[19:03] <akgraner> nods
[19:39] <pleia2> bkerensa: just added dev news to the doc, wanna write a summary for that one? :)
[19:39] <bkerensa> yes well... assuming my other summaries passed muster?
[19:40] <pleia2> I didn't actually read them, I'm sure they're fine, we do editorial review anyway if you're worried
[21:36] <pleia2> MrChrisDruif: can you update the doc for the flavor meetings (I updated for xubuntu, no meeting)
[21:38] <MrChrisDruif> pleia2; will do
[21:51] <MrChrisDruif> pleia2; did we ever get any notice from mythbuntu? I can't remember, not find any meeting links
[21:52] <pleia2> I don't know, sorry :\
[21:52] <MrChrisDruif> nor*
[21:53] <MrChrisDruif> Alright, then I think all the links are up-to-date
[22:27] <Silverlion> good evening everyone
[23:01] <MrChrisDruif> Aloha Silverlion
[23:01] <Silverlion> MrChrisDruif : hoi
[23:06] <akgraner> Thanks y'all - pleia2 I'll review stuff in the morning
[23:06] <pleia2> thanks akgraner
[23:07] <pleia2> I think I'm done adding links
[23:07] <Silverlion> hey pleia2 and akgraner
[23:07] <akgraner> hey Silverlion
[23:08] <pleia2> MrChrisDruif: thanks for updating the links
[23:08] <Silverlion> akgraner : got a min to talk?
[23:08] <MrChrisDruif> pleia2; no problem
[23:08]  * pleia2 back to work
[23:09] <akgraner> Silverlion, I'm sorry not right this second - I'm finishing something for work then cooking dinner
[23:10] <Silverlion> akgraner : well not important ;)
[23:10] <akgraner> I'll come back after dinner and see if you are still on though
[23:10] <akgraner> I was at SCALE all weekend and a little behind - sorry
[23:10] <Silverlion> akgraner : most definetly not as i am facing 1am in the morning and need to sleep
[23:11] <akgraner> ok get some sleep - I'll ping you tomorrow at a decent time
[23:14] <Silverlion> akgraner : copy that... have a good one
[23:44] <bkerensa> =o
[23:54] <MrChrisDruif> bkerensa; ?


[10:07] <lotuspsychje> good morning
[15:40] <frechdachs69> is there already a beta network install image for 20.04 ?
[15:40] <lotuspsychje> frechdachs69: 20.04 is still in development phase, see the topic for the dates schedule
[15:41] <frechdachs69> I know; I have installed it inside my VirtualBox VM
[15:41] <frechdachs69> via desktop image
[15:41] <lotuspsychje> oh you want a netinstall iso?
[15:41] <frechdachs69> yes
[15:42] <frechdachs69> to develop a preseed installation
[15:42] <lotuspsychje> didnt test that yet myself
[15:42] <lotuspsychje> im also testing desktop
[15:44] <mason> frechdachs69: there's a traditional server install image
[15:44] <mason> frechdachs69: http://cdimage.ubuntu.com/ubuntu-server/daily/current/focal-server-amd64.iso.zsync
[15:45] <frechdachs69> okay, I've found http://archive.ubuntu.com/ubuntu/dists/focal/main/installer-amd64/current/images/netboot/
[15:45] <frechdachs69> although not advertised it already exists
[15:49] <lotuspsychje> i know devs working hard on the server installer, expect new features
[15:51] <mason> frechdachs69: Oh! Thought you just meant net install. Nifty. Thanks for the link.
[16:46] <notguest96> Focal latest update doesn't seem to install properly
[17:22] <mason> notguest96: Which image?
[17:29] <notguest96> 20.04 mason
[17:31] <mason> notguest96: Desktop? Server? Netboot since that's there now?
[17:33] <notguest96> laptop mason
[17:34] <mason> notguest96: That'd probably be the desktop ISO then. What did it do wrong?
[17:38] <notguest96> Whenever my screen goes to lockscreen and I try to unlock it
[17:39] <notguest96> The screen just freezes and lags out mason
[17:39] <mason> notguest96: When you're there, can you switch to a virtual console and back?
[17:40] <notguest96> Virtual console?
[17:41] <notguest96> Ohh
[17:41] <notguest96> Well I think I can run it
[17:42] <notguest96> But it doesn't entirely logs me out, just give me a purple screen and back to the lockscreen. The only solution i have found is to fully restart
[17:42] <notguest96> Or click on my Icon and enter my password and then enter the laptop
[17:46] <mason> notguest96: Ah, you might be able to see logs showing what's happening.
[17:46] <notguest96> how do I see it?
[17:46] <notguest96> mason:
[17:48] <mason> notguest96: Read /var/log/auth.log and see if there are any errors or auth denials, look at /var/log/Xorg.0.log and see if there's anything unusual, see if there's anything unusual is dmesg output. Those three will cover a lot.
[17:49] <notguest96> Ok thanks you