[00:53] <aeoril> In the following webpage there is a section entitled "bzr-builddeb" that tells me to install bzr-builddeb.  I do not have that installed, but I do have bzr-debbuild.  I just wanted ot make sure that was correct, and if so, see what to do about getting the wiki updated (I would be glad to do it, but need to know how):  https://wiki.ubuntu.com/SimpleSbuild#bzr-debuild
[00:53] <aeoril> darkxst sarnold ^
[00:54] <aeoril> (to see if bzr-debbuild is correct, not bzr-builddeb)
[00:56] <aeoril> also, it does not say how to install schroots for different versions - I am assuming for vivid, for instance, it would be "mk-sbuild vivid"?
[00:57] <aeoril> or, is are there other steps I need to do to make an schroot for other versions before that?
[01:06] <darkxst> aeoril, bzr-builddeb is correct
[01:06] <darkxst> easiest make to make schroots is with sbuild-launchpad-chroot
[01:06] <aeoril> darkxst ok, i thought so - should I e-mail the owner of that page to inform them it is mis-spelled?
[01:07] <darkxst> aeoril, no, that is something else
[01:08] <aeoril> darkxst what is something else?
[01:08] <aeoril> oh, youi said builddeb is correct, not debbuild ... sorry
[01:09] <darkxst> aeoril, they are 2 different tools
[01:09] <darkxst> by the looks of it
[01:11] <aeoril> darkxst yes, I understand now - I guess I need to install bzr-builddeb?  This is a fresh machine and I did not install any build or developer tools other than what were in the directions on that page.  Apparently, I was supposed to know to install bzr-builddeb - are there other things I am missing on a fresh machine for development?  is there a wiki to follow to get set up for building
[01:11] <aeoril> properly?  I am familiar with the BeginnerTeam wiki, but know that that team has not been active for quite some time
[01:12] <darkxst> aeoril, there is this http://packaging.ubuntu.com/html/getting-set-up.html
[01:13] <darkxst> but there is no definitive guide since they are multiple ways to do every step of packaging
[01:13] <aeoril> darkxst ok, I will follow that - I guess once I get everything set up correctly, I need to remake my schroot to reflect the changes in my machine?
[01:14] <darkxst> your schroot is isolated from your machine
[01:15] <aeoril> darkxst where did it pull its packages from?  I guess not my machine, but the "magic appropriate place on the web???"
[01:15] <darkxst> if you used sbuild-launchpad-chroot, it pulls an image off launchpad
[01:16] <darkxst> if you use mk-sbuild, I suspect it would use debbootstrap to make a minimal environment
[01:16] <darkxst> anyway gtg
[01:16] <aeoril> hmmmm ... on that wiki page, it just had me do 'mk-sbuild trusty'
[01:16] <aeoril> ok, thanks
[01:17] <darkxst> sbuild-launchpad-chroot, gives  you an schroot almost identical to the archive builders
[01:40] <aeoril> darkxst yes, I have used it now and will experiement - thanks!  I think this will really help!
[05:33] <pitti> Good morning
[05:33] <pitti> mitya57: it's already gone from private jenkins, the public one needs an RT to clean up
[06:13] <aeoril> I have set up schroots with sbuild-launchpad-chroot on a trusty 14.04.1 LTS machine.  After successfully running sbuild-launchpad-chroot create and and creating a local repo of ubiquity with "bzr branch lp:ubiquity" I ran the sbuild command to build for vivid from the ubiquity directory.  Unfortunately, it did not complete successfully and failed as follows:  http://paste.ubuntu.com/10367718
[06:13] <aeoril> /  The isntructions had a final parameter "<dsc>" I left off - not sure what to put there.  Any ideas why this is failing?
[06:13] <aeoril> darkxst sarnold ^
[06:20] <aeoril> Do I need to do the following first? "dch -i; update-maintainer; debuild -S"
[06:22] <darkxst> aeoril, yes build the sauce package, then pass that .dsc file to sbuild
[06:22] <darkxst> source even
[06:26] <aeoril> darkxst debuild -S failed with the same error as sbuild as well as the following:  "dpkg-buildpackage -rfakeroot -d -us -uc -S failed"
[06:27] <darkxst> aeoril, do you have pyflakes installed?
[06:27] <aeoril> I think ./test/run-pyflakes is failing
[06:27] <aeoril> oh, maybe not - just a minute
[06:39] <aeoril> darkxst ok, got past pyflakes and pep8 install and run, but failing here.  I don't understand why it is doing this since that directory does not appear to exist:  http://paste.ubuntu.com/10367924/
[06:45] <darkxst> aeoril, are you building from a bzr branch? use bzr builddeb -S if so
[06:45] <aeoril> darkxst yes, I am building from a bzr branch thanks
[06:51] <aeoril> darkxst well, it went a lot better, much more stuff happened, but I got an error that included the text "you may need to install the Debian::Debhelper::Sequence::d_i module" - I can give you the entire error if you need it
[06:51] <aeoril> dh: unable to load addon d-i: Can't locate Debian/Debhelper/Sequence/d_i.pm in @INC (you may need to install the Debian::Debhelper::Sequence::d_i module) ...
[06:51] <darkxst> aeoril, I am going to guess you are missing some debhelper tool
[06:52] <aeoril> darkxst yes, I figured that, but I don't know which one ...
[06:52] <darkxst> apt-get build-dep ubiquity (should hopefully get it)
[06:52] <darkxst> or try apt-file find d_i.pm
[06:53] <aeoril> darkxst hmmmm ... I thought the whole idea was to do this using sbuild in an schroot as close to the build environment on launchpad as possible?  I am confused as to exactly what I am accomplishing right now ...
[06:54] <darkxst> aeoril, some tools are required to build source packages (sbuild can't help there)
[06:55] <darkxst> sbuild is for building the binaries
[06:56] <aeoril> darkxst wouldn't it be better just to find the tools necessary to build the source packages, rather than getting *all* the build dependencies?  Wouldn't getting build dependencies gunck up my regular machine?
[06:56] <aeoril> (in other words, do your second suggestion?)
[07:02] <darkxst> aeoril, do whichever way you prefer
[07:04] <aeoril> darkxst I think everything built, but now I have a gpg error.  I thought I set up GPG right - is there a way to test it?:  http://paste.ubuntu.com/10368218/
[07:05] <darkxst> aeoril, you need to set a default key (or add your own changelog entry)
[07:05] <aeoril> darkxst oh, in .bashrc?
[07:06] <darkxst> aeoril, in ~/.gnupg/gpg.conf I think
[07:07] <dholbach> good morning
[07:07] <aeoril> darkxst this says to do it in .bashrc? https://help.ubuntu.com/community/GnuPrivacyGuardHowto (search for "default key")
[07:07] <aeoril> dholbach good morning :)
[07:07] <dholbach> hi aeoril
[07:08] <darkxst> aeoril, I imagine either would work
[08:05] <hyperair> so i've got a bluetooth mouse here that refuses to reconnect after going into powersave mode
[08:05] <hyperair> how do i debug this?
[08:18] <hyperair> hmm it keeps failing with bluetoothd[25955]: plugins/hciops.c:link_key_request() Matching key not found
[08:26] <mariel> darkxst thanks, everything is working now.  Setting the default gpg id in both .bashrc and .gpg.conf did not work - I had to add a new changelog entry for my new version
[09:03] <DrTobbe> Hi, I've been in Laos and I told people there that Ubuntu is very great because it tries to be available for everyone (disabled people, all languages, and so on). Then, I found out that Lao language is not correctly supported by the default-fonts in Ubuntu (for example Ubuntu or Sans). Shouldn't we/Ubuntu implement this to keep our/its promise?
[09:04] <DrTobbe> Or ... Who shold I talk to to tackle this problem?
[13:39] <pete-woods> cjwatson: hi! I was wondering if you might be able to help me figure out / tell me what commands I might use on my phone to install a click package into the preinstalled db at /usr/share/click/preinstalled/
[13:44] <cjwatson> pete-woods: Odd to do that on the phone rather than in a chroot elsewhere while preparing an image!
[13:44] <cjwatson> pete-woods: Should be something like "sudo click install --all-users --root=/usr/share/click/preinstalled foo.click"
[13:45] <pete-woods> cjwatson: yeah, just testing something out. thanks for the help!
[13:46] <cjwatson> np
[14:10] <caribou> Q: Am I wasting my time trying to fix FTBS 'à la' PlusOneMaintenance ?
[14:18] <rbasak> caribou: why do you ask?
[14:18] <rbasak> It's generally useful, assuming you send fixes upstream.
[14:18] <rbasak> Though I did find it generally unending and thankless, and didn't feel it made that much of an impact when I did it - particularly for packages in universe.
[14:18] <caribou> rbasak: because there doesn't seem to be any formal activity with the PlusOne Maintenance team anymore
[14:18] <rbasak> It did make my application for MOTU much more useful though :)
[14:19] <rbasak> s/useful/credible/ perhaps
[14:19] <caribou> rbasak: it is also partly my intent : get exposure for all sort of packaging problems to gain experience
[14:20] <caribou> rbasak: for instance, the deja-dup FTBS is peculiar as it does build as PPA and locally and not in the builder
[14:20] <rbasak> That certainly is useful for experience :)
[14:20] <rbasak> I think that doing universe FTBFSes helped me more than I thought at the time.
[14:23] <caribou> rbasak: so what should I do with this one ? open a bug & attach the debdiff ? branch & MP ?
[14:24] <caribou> rbasak: since I cannot upload myself
[14:24] <caribou> maybe mterry will want to sponsor it
[14:25] <mterry> caribou, rbasak: a deja-dup ftbfs?  fun.  Point me at bug and I'll try to get to it
[14:25] <caribou> mterry: oh, I fixed it
[14:25] <mterry> caribou, but you need a sponsor, right?
[14:25] <caribou> mterry: ok, I'll create the bug & attach the debdiff. Or maybe you prefer a branch
[14:26] <caribou> mterry: yep
[14:26] <mterry> caribou, either is fine, but don't bother with a branch if you already have a debdiff
[14:27] <caribou> mterry: hmm, it'll have to be a debdiff, there's an in-flight source modification into -proposed
[14:27] <caribou> matter of fact, this is what introduced the FTBS
[14:28] <caribou> Noskcaj: you have the deja-dup uploaded into -proposed
[14:30] <caribou> mterry: ok, I'll create a bug & attach the debdiff against the source in -proposed
[14:33] <rbasak> caribou: I'll leave you with mterry. Just FYI, when I was doing +1 and had a bunch of FTBFS fixes, rather than creating a branch I just stuck all the updated source packages online somewhere. Sponsors were happy to use that, rather than doing the busywork of creating a ton of bugs.
[14:34] <caribou> rbasak: good to kwow, thanks
[14:34] <rbasak> caribou: I guess the MP/bug debdiff workflow works better for actually putting things in the sponsorship queue though
[14:34] <rbasak> But if you have a sponsor lined up, they usually don't mind how they get the work.
[14:34] <caribou> rbasak: it always depend if the sponsor is already identified (as it is in the current case)
[14:34] <rbasak> Right
[14:35] <caribou> rbasak: i was just surprized by the difference of build behavior b/w local & the archive builder
[14:35] <rbasak> Ah.
[14:35] <rbasak> That surprised me too when I started.
[14:36] <caribou> rbasak: I did have a previous situation where it was a parallelism issue involved
[14:36] <rbasak> Apparently it's quite difficult to replicate the archive builder exactly, so most devs don't bother and it works in the majority of cases.
[14:36] <rbasak> In the odd cases where it doesn't, comparing the build logs can often identify the issue (I use meld)
[14:37] <rbasak> And when that still doesn't work, I get help here from the devs who are closer to the builders (generally archive admins, etc)
[14:37] <aeoril> darkxst I found two equivalent .deb files created by the ubiquity build (same name but different version as oem-config_2.21.13_all.deb and oem-config-gtk_2.21.13_all.deb) in the Ubuntu .iso for the livecd in the following directory:  pool/main/u/ubiquity Do I just replace those two package files with the ones I made with my compiled changes in the .iso then use that .iso to create a
[14:37] <aeoril> bootable live cd to test the install?
[14:37] <mterry> caribou, yeah I can take debdiff however you like, if you don't want to bother with bug
[14:37] <aeoril> or whoever knows
[14:38] <caribou> mterry: no worry, bug is done already, just doing a bit of description there
[14:40] <caribou> mterry: it's all there LP: #1424652
[14:48] <xnox> pitti: i love the typo you made re:mtab vs mountinfo "Yes, it arses it just fine"
[14:48] <xnox> vs parses =)
[14:48] <pitti> xnox: that was a case of SCNR indeed :)
[14:50] <xnox> pitti: so given the new enough util-linux with that toggle enabled, can the /etc/mtab symlink be dropped?
[14:50] <xnox> pitti: or is there anything else that reads it?
[14:50] <pitti> xnox: no, there's still lots of other things which look at that
[14:51] <xnox> pitti: name one
[14:51] <pitti> or, let's rather say, we don't know
[14:51] <xnox> udev, systemd, util-linux no longer do.....
[14:51] <pitti> we could drop it and see what happens, but that's not a good idea post-FF
[14:51] <pitti> indeed, any well-behaved program/script ought to parse /proc/self/mounts or the output of "mount"
[14:53] <pitti> http://codesearch.debian.net/results/%2Fetc%2Fmtab/page_0 has 186 pages, ugh
[14:55] <pitti> xnox: the last page has a few
[14:55] <pitti> http://codesearch.debian.net/results/%2Fetc%2Fmtab/page_185
[14:56] <pitti> xnox: so cleaning those up sounds like a nice vivid+1 project
[15:06] <xnox> where is KMTAB defined?!
[15:15] <xnox> nevermind non-linux codepath....
[15:16] <rbasak> infinity: FYI, a fix for percona-galera-3 !Intel FTBFS is in progress.
[15:17] <rbasak> Once done, I'll poke you to review all the binNEWs.
[15:17] <rbasak> And to process bug 1417328
[15:21] <xnox> pitti: glibc seems to be using /etc/mtab =(
[15:26] <Laney> second CfV sent to u-d-a@ if someone could moderate
[15:28] <pitti> Laney: done
[15:28] <Laney> cheers!
[15:31] <smoser> anyone else reported menus living in their windows title bar rather than the top unity panel?
[15:32] <Laney> that happened on purpose
[15:33] <smoser> oh. really
[15:33] <didrocks> smoser: http://www.webupd8.org/2015/02/locally-integrated-menus-lim-set-as.html
[15:33] <Laney> http://www.webupd8.org/2015/02/locally-integrated-menus-lim-set-as.html
[15:33] <Laney> DAMN!
[15:33] <didrocks> \o/
[15:33] <Laney> read my link, it's better
[15:33] <didrocks> coming from UK, so closer to you, obviously :)
[15:35] <smoser> Laney, thanks.
[15:35] <Laney> yw
[16:14] <mterry> caribou, uploaded, only change was adding bug number to changelog
[16:15] <caribou> mterry: oh right, I built the debdiff before opening the bug
[16:15] <caribou> mterry: thanks !
[16:15] <mterry> caribou, I'm curious why it fails in archive but not locally
[16:17] <caribou> mterry: couldn't figure it out either since appdata-validate still works but throw the DEPRECATED message
[16:17] <caribou> mterry: I'll be attentive to the next build
[16:23] <caribou> mterry: ok, I know why it worked locally : appdata-validate was not the reason it was failing
[16:23] <mterry> caribou, yeah, we need to pass --nonet
[16:23] <mterry> caribou, just saw the failure myself
[16:24] <mterry> caribou, I can do that myself real quick
[16:24] <caribou> mterry: ok, but I'd like to know what you changed. It'll outline why it didn't work on the builder to me
[16:27] <mterry> caribou, http://bazaar.launchpad.net/~ubuntu-desktop/deja-dup/ubuntu/revision/42
[16:28] <mterry> caribou, the validate tool was hitting network and couldn't, so it failed validation
[16:28] <caribou> mterry: ah, ok I get it
[16:29] <mterry> caribou, though I would have expected the PPA builds to fail then?
[16:29] <mterry> caribou, and I think that was a behavior difference in the tool too -- it didn't used to try to hit the network to test the screenshots in the file.  But they added a feature that does that I guess
[16:29] <caribou> mterry: me too, that's why I built both .3 & .4 in my PPA prior to going for sponsor
[16:29] <mterry> caribou, well...  maybe .5 will fail for some other reason  ;)
[16:37] <mterry> caribou, .5 worked on i386...  so that's good
[16:38] <caribou> mterry: good !
[16:41] <caribou> mterry: builds fine on amd64 as well
[16:42] <mterry> caribou, OK.  Chalk that up to mysterious network access in the PPA...?
[16:43] <mterry> caribou, it was hitting launchpad.net
[16:43] <mterry> caribou, maybe PPAs allow doing that because they sometimes pull from other PPAs
[16:43] <caribou> mterry: yes, most probably
[16:44] <cjwatson> Shouldn't be any difference.
[16:44] <caribou> mterry: & the previous behavior of appdata-validate changed as well
[16:44] <cjwatson> launchpad.net itself, or a subdomain?
[16:45] <mterry> cjwatson, https://launchpad.net
[16:46] <cjwatson> Other PPAs aren't on launchpad.net, neither the same physical host nor the same DNS name
[16:46] <cjwatson> So that's not the reason
[16:47] <cjwatson> And in any case the distinction is not likely to be PPA vs. Ubuntu, but non-virtual vs. virtual
[16:47] <cjwatson> And non-virtual builders build some specialised PPAs too
[16:48] <cjwatson> "url not found" hides some underlying error, so it's hard to say.
[16:52] <pitti> PSA: d-jenkins is unhappy again, so if you see a bunch of autopkgtest failurs which look weird, we're on it
[16:52] <pitti> Laney, Mirv, etc. ^
[16:53] <cjwatson> 91.189.89.30 - "10.122.37.20, 127.0.0.1" "launchpad.net:443" [23/Feb/2015:16:19:21 +0000] "GET /deja-dup/32/32.0/+download/screenshot-2.png HTTP/1.0" 302 526 9 0.105017185211 594 102 "Anonymous" "LibraryFileAlias:+index" "" "libappstream-glib"
[16:53] <cjwatson> I wonder why that's getting a 302
[16:53] <cjwatson> Oh, of course, 302 to the librarian
[16:55] <cjwatson> Then AFAICS the librarian never sees the redirected request.
[16:56] <cjwatson> But that's odd since buildds explicitly have librarian access.
[16:57] <pitti> infinity, cjwatson, wgrant: FYI, fisher03's apache hasn't responded in 2 days for ddeb retrieval; if that keeps being broken, we'll lose ddebs in 5 days
[16:58] <cjwatson> pitti: Needs infinity; wgrant and I can't help, but thanks for the heads-up
[16:59] <pitti> cjwatson: yeah, I figured; it was more an FYI for you
[17:02] <cjwatson> wgrant: Do you know if we have access to the specialised buildd DNS code, and if it's the same for non-virt buildds and scalingstack?  Surely it should be, but I can't see why the deja-dup thing above would have broken on non-virt builders but apparently not on scalingstack.
[17:11] <infinity> cjwatson: I'd be willing to bet scalingstack's DNS setup isn't the same, actually (and that should be fixed).
[17:11] <infinity> pitti: Looking.
[17:12] <infinity> [602822.116012] sd 0:0:0:0: rejecting I/O to offline device
[17:12] <infinity> ^-- qemu emulating real hardware a bit TOO well.
[17:13] <ogra_> just online it :P
[17:14] <cjwatson> infinity: I'm a little surprised that anyone would have bothered to do it differently.
[17:15] <cjwatson> There's a nagios test defined in canonical-is-openstack-deploy to the effect that hp.com returns NXDOMAIN.
[17:15] <cjwatson> So there's definitely something similar in spirit in place.
[17:15] <infinity> Hrm.  Curious.
[17:16] <infinity> Well, it's going to be a different view (or a different server entirely) because it's not the same subnet, or possibly even network, but yeah, you'd have expected it to be either a straight cargo-cult or wide open.
[17:17] <flexiondotorg> infinity, Do you have a sec?
[17:17] <cjwatson> It's the same server, according to puppet.
[17:17] <cjwatson> (salmonberry)
[17:17] <cjwatson> Oh, no, that's the puppeteer
[17:18] <infinity> flexiondotorg: Perhaps.
[17:18] <cjwatson> I think ... don't know this stuff very well
[17:18] <flexiondotorg> infinity, I'd just like to ask when it might be possible to try build Ubuntu MATE images?
[17:19] <infinity> flexiondotorg: Oh.  This week.  Maybe even today.  Let me wake up a bit and confer with cyphermox on what he believes the status of things are.
[17:19] <cjwatson> flexiondotorg: We can kick off another attempt any time.
[17:20] <infinity> flexiondotorg: Or, if Colin has context, what he said. :P
[17:20] <cjwatson> I mean, if the necessary packages are in place.
[17:20] <flexiondotorg> cjwatson, Another attempt?
[17:20] <flexiondotorg> Has it been tried before?
[17:20] <cjwatson> flexiondotorg: Yes.
[17:20] <flexiondotorg> cjwatson, I didn't know that.
[17:20] <cjwatson> It failed, fairly obscurely but I think you were known to be missing some packages at the time.
[17:21] <flexiondotorg> Are there some error logs I can look at? If there is stuff to be fixed I'll get stuck in.
[17:21] <cjwatson> http://people.canonical.com/~ubuntu-archive/cd-build-logs/ubuntu-mate/vivid/daily-live-20150220.log
[17:21] <flexiondotorg> Thanks.
[17:21] <cjwatson> But https://launchpadlibrarian.net/198284153/buildlog_ubuntu_vivid_amd64_ubuntu-mate_BUILDING.txt.gz doesn't really have much to go on.
[17:22] <infinity> That's not the most informative failure...
[17:23] <flexiondotorg> cjwatson, infinity Reading both logs.
[17:23] <flexiondotorg> Yeah, the first log I can't do anything with.
[17:23] <cjwatson> The first just links (indirectly) to the second.
[17:23] <infinity> I meant the livefs log wasn't informative. :P
[17:23] <cyphermox> right, that failure tells me nothing as to what might have gone wrong
[17:23] <infinity> The cdimage log is totally informative, just brief.
[17:23] <cjwatson> infinity: It's a bit opaque ...
[17:24] <infinity> cjwatson: "a bit".
[17:24] <cyphermox> next step for me was to ask you cjwatson or infinity for help
[17:24] <infinity> cjwatson: I think we're log past due cranking up the verbosity on live-build.
[17:24] <cjwatson> Wait.  Does the ubuntu-mate-core task actually exist?
[17:24] <infinity> cjwatson: As in, for the love of god, tell me what command you were trying to run.
[17:25] <cjwatson> Nobody ever changed ubuntu-archive-publishing to generate it ...
[17:25] <cyphermox> ah, that's something we didn't know about
[17:25]  * cjwatson fixes that
[17:26] <flexiondotorg> Thanks guys.
[17:26] <flexiondotorg> cyphermox, Hi 😃
[17:26] <cjwatson> Should be better in a couple of publisher cycles.
[17:27] <cyphermox> cjwatson: was that something we could change in a code branch or did that require special access?
[17:27] <flexiondotorg> cyphermox, mate-tweak and mate-menu are still in the Upload Queue.
[17:27] <cjwatson> cyphermox: lp:ubuntu-archive-publishing
[17:27] <cyphermox> flexiondotorg: that won't help
[17:27] <cyphermox> cjwatson: thanks
[17:27] <infinity> Yeah, I didn't have time to look at them on Friday, I'll poke today.
[17:27] <infinity> Oh, wait.  I looked a bit.
[17:27] <infinity> flexiondotorg: I had a copyright complaint about mate-menu. :P
[17:27] <cjwatson> https://code.launchpad.net/~acidburn0/+recipe/ubuntu-archive-publishing-daily  WTF
[17:27] <infinity> Copyright: *No copyright*
[17:27] <infinity> License: GPL-2+
[17:28] <infinity> ^-- That is literally impossible.
[17:28] <infinity> You can't have a copyright license and assert no copyright.  And "no copyright" is almost certainly a lie anyway.
[17:28] <infinity> Given that all creative works (in most jurisdictions) have copyright attached to them just by being created.
[17:29] <infinity> pitti: The fishers should be marginally less grumpy.
[17:29] <flexiondotorg> infinity, OK. That copyright stuff is what was recommended by the DD I am working with.
[17:30] <cyphermox> infinity: that may have rather meant that the file itself didn't have a copyright notice but there is COPYING there
[17:30] <pitti> infinity: cheers!
[17:30] <cyphermox> I thought there was a "assuming blah blah" line just below or in Comment: or something
[17:30] <infinity> cyphermox: I know exactly what it means, but it also won't do.
[17:31] <infinity> cyphermox: "I don't know who owns the copyright and who supposedly gave me the license to distribute" isn't a helpful license.
[17:31] <cyphermox> infinity: fortunately flexiondotorg here is supposed to be the upstream and able to explain
[17:31] <infinity> cyphermox: They're asserting the license is probably the one in COPYING (a fair assumption), but no copyright.
[17:31] <infinity> flexiondotorg: So, uhm... Who owns the copyright on those files? :P
[17:31] <cyphermox> oh
[17:32] <cyphermox> the copyright *owner*
[17:32] <infinity> Yes.
[17:32] <cyphermox> I see now
[17:32] <flexiondotorg> infinity, I forked another project. They did not provide copyright headers in all the sources.
[17:32] <infinity> A copyright license without provenance isn't a license.
[17:32] <cyphermox> infinity: of course not
[17:32] <infinity> flexiondotorg: Headers in all the files aren't necessary, but a statement of copyright ownership on the copyrightable bits is important.
[17:33] <infinity> flexiondotorg: Certainly, some of this junk is just glue and not subject to copyright anyway, but I see logos and such under this non-copyright, which won't do at all.
[17:33] <flexiondotorg> infinity, OK. One sec then.
[17:33] <flexiondotorg> Copyright: 2007-2014, Clement Lefebvre <root@linuxmint.com>
[17:33] <flexiondotorg>            2015, Martin Wimpress <code@ubuntu-mate.org>
[17:34] <flexiondotorg> That ^^^^^ is the suitable copyright. Given that it include the original author and myself (new upstream maintainer).
[17:34] <infinity> flexiondotorg: And that applies to, say, data/icons/mate-logo.svg ?
[17:34] <cyphermox> flexiondotorg: Clement is the person who designed the logos (for example) originally in the project you forked?
[17:34] <flexiondotorg> infinity, Do you want me to resubmit or can/will you make the required change?
[17:35] <infinity> flexiondotorg: If so, get someone to fix the copyright file to be sane in that regard (and perhaps also note correct copyrights in the upstream project too)
[17:35] <flexiondotorg> cyphermox, No, that particualr file was created by myself and Sam Hewitt.
[17:35] <flexiondotorg> infinity, Updating the upstream project won't happen. I've tried that already.
[17:35] <flexiondotorg> Not upstream
[17:35] <infinity> flexiondotorg: I mean your upstream project. ;)
[17:36] <infinity> flexiondotorg: Not the one you derived from.
[17:36] <flexiondotorg> infinity, Understood (eventually) 😃
[17:36] <flexiondotorg> OK, I will update the copyright now...
[17:36] <infinity> flexiondotorg: As in, you just said that data/icons/mate-logo.svg comes from you, not from your upstream, so "I don't know who owns the copyright" isn't even a factual answer. :)
[17:36] <infinity> flexiondotorg: So, yeah.  Please sort.  Make sure things are sanely attributed.
[17:37] <flexiondotorg> infinity, Like I say. That copyright file was prepared my the DD I'm working with.
[17:37] <infinity> flexiondotorg: I'll reject that one from the queue now, and expect a shinier version.  And I'll go review the other one.
[17:37] <infinity> flexiondotorg: Check.  Pass on my ire to him about the senselessness of "no copyright" then. :)
[17:40] <bdmurray> Riddell: can you have someone look at these PEP8 failures? http://pastebin.ubuntu.com/10375047/
[17:41] <Riddell> bdmurray: hmm? I was able to build and upload it from my laptop was I not?
[17:42] <bdmurray> Riddell: did you use bzr-buildpackage or debuild?
[17:42] <flexiondotorg> infinity, Would you accept this debian/copyright?
[17:42] <flexiondotorg> http://paste.ubuntu.com/10375062/
[17:45] <infinity> flexiondotorg: If it's factually correct.
[17:46] <infinity> flexiondotorg: I see no mention of Sam Hewitt in there, who you highlighted above, for instance.
[17:46] <flexiondotorg> I've just added that 😃
[17:46] <flexiondotorg> Files: data/icons/mate-logo.svg
[17:46] <flexiondotorg> Copyright: 2014, Sam Hewitt <hewittsamuel@gmail.com>
[17:46] <flexiondotorg> License: GPL-3+
[17:46] <Riddell> bdmurray: I think I used bzr-buildpackage, let me try again
[17:47] <infinity> flexiondotorg: 3+, not 2+ like everything else?  Whee.
[17:47] <flexiondotorg> infinity, Sam releases everything as GPL 3+.
[17:47] <flexiondotorg> I've include the GPL3+ license bioler plate too.
[17:48] <infinity> flexiondotorg: Kay.  So, that also means the PNG produced from it is 3+
[17:48] <infinity> flexiondotorg: But yes, that looks better. :)
[17:48] <flexiondotorg> infinity, Yes, the original artwork is GPL3+ licensed.
[17:48] <flexiondotorg> infinity, http://paste.ubuntu.com/10375144/
[17:49] <infinity> flexiondotorg: mate-tweak has the same problematic "no copyright" clause.
[17:49] <flexiondotorg> infinity, On it..
[17:50] <infinity> flexiondotorg: Oh, also, the copyright on COPYING isn't you (and, really, you shouldn't bother including it in the list of files at all).
[17:50] <infinity> Unless you'd like to pretend you wrote the GPL. ;)
[17:55] <Riddell> bdmurray: ok I can recreate it, do you know what all the problems are with all the "'from PyQt5.QtCore import *' used; unable to detect undefined names" messages? does it just not  like wildcard imports?
[17:55] <infinity> flexiondotorg: Oh, also, for future maintainability, it's MUCH simpler to collapse all those Clement/Martin copyrights down to "Files: *" and then just highlight the ones that differ.
[17:55] <infinity> flexiondotorg: Since having to adust the copyright file for every new added bit is painful and error-prone.
[17:56] <bdmurray> Riddell: yeah, it'd prefer from PyQt4 import QtCore instead of from PyQt5.QtCore import *
[17:56] <bdmurray> s/Qt4/Qt5/
[18:02] <cjwatson> https://www.python.org/dev/peps/pep-0008/ has reasoning on why wildcard imports should be avoided
[18:13] <flexiondotorg> infinity, Shall I update the original packaging request bugs and direct you to them?
[18:24] <Riddell> bdmurray: commited some fixes, let me know if that works or breaks
[18:28] <bdmurray> Riddell: looks good, thanks!
[18:33] <flexiondotorg> cyphermox, I've updated mate-menu and mate-tweak based on the feedback from infinity.
[18:33] <flexiondotorg> cyphermox, Can you upload them again?
[18:49] <cyphermox> flexiondotorg: sure
[18:50] <flexiondotorg> cyphermox, Thanks 😃
[19:46] <darkxst> aeoril, easiest way to test ubiquity is probably to boot a live session, update ubiquity with your packages, then run the installer
[19:46] <aeoril> darkxst what do you mean by "live session"?
[19:47] <aeoril> just boot from livecd?
[19:47] <darkxst> yes
[19:47] <darkxst> "try ubuntu"
[19:50] <aeoril> I do not have a thumb drive to boot with - can I somehow do it with just the .iso from cdimage.ubuntu.com?
[19:50] <aeoril> darkxst ^
[19:50] <aeoril> (I can always buy a small thumb drive for a few dollars though)
[19:51] <darkxst> aeoril, use a VM
[19:52] <aeoril> darkxst how do I get my ubizuity .debs into the live session though?
[19:53] <aeoril> I could always just add them directly onto the livecd with iso master ...
[19:53] <aeoril> ubiquity*
[19:53] <darkxst> aeoril, scp, or network share
[19:53] <darkxst> or ppa
[19:53] <darkxst> there is no need to remaster ISO to test
[19:55] <aeoril> darkxst actually, maybe adding to the iso would be easiest - it is just a copy/paste, save the iso then boot from it, I think
[19:55] <aeoril> the iso from cdimage.ubuntu.com
[19:56] <aeoril> iso master has a simple gui
[19:57] <darkxst> aeoril, you can't just copy package files into the ISO
[19:58] <stgraber> pitti: FYI, I've had someone report that the ureadahead upload broke the upgrade on their box as ureadahead would exit immediately on their box, leading to "start ureadahead" to fail
[19:58] <stgraber> not sure if that's a common/normal case for ureadahead (I thought it might be for ssds and other case where ureadahead can't work)
[19:58] <aeoril> darkxst I meant just to have them available after bootup, rather than scp or network share or ppa - don't I have access to the mounted .iso image from the live session?  I could use dpkg to install them into my live session from the .iso image (I assume it will be mounted as a cd?)
[19:59] <aeoril> darkxst but is scp is available, that would be very easy i guess - I guess the scp client is available default in the live session?
[20:00] <darkxst> it should be but if not, you can just install it
[20:01] <aeoril> darkxst I was just thinking I might have to set up ssh keys and such
[20:04] <darkxst> ssh can use passwords too (unless you have disabled them)
[20:04] <aeoril> ok, cool - that seems simplest then.  I will try this now.  Thanks.
[20:09] <aeoril> darkxst thanks for all the help - watching the sbuild go to work was amazing yesterday.  But, I had to make my own entry in changelog though to get around the gpg failure
[20:16] <flexiondotorg> cjwatson, What is the correct way to instruct the image build process to "--no-install-recommends"?
[20:19] <aeoril> darkxst there are a bunch of .deb files created from the build process - how do I know which one to use to install the package?
[20:19] <darkxst> install all except -dbg and -dev
[20:20] <aeoril> darkxst ok, that would be all of them then ...
[20:21] <infinity> flexiondotorg: You'd want to make your tasks not follow recommends in that case, though it's better if you can avoid having to do that.
[20:21] <infinity> flexiondotorg: What problem is recommends causing you?
[20:23] <aeoril> darkxst as an fyi, I found several places where icon names needed to be fixed - there was also a warning icon that needed to be renamed, not just the "finished" icon
[20:24] <aeoril> well, "info"
[20:27] <aeoril> darkxst I vaguely remember maybe that using the .dsc file will install them all appropriately?  Is that just my own fantasy?
[20:28] <aeoril> darkxst or is that just for source?
[20:29] <aeoril> darkxst nm, looked it up myself
[20:44] <aeoril> darkxst if I make a ppa, will "sudo apt-get install ..." automatically install all the .deb files for me that sbuild created?
[20:44] <aeoril> darkxst also, would that be a good way to attach the fix to the bug?
[20:45] <aeoril> (just reference the ppa?)
[20:45] <darkxst> aeoril, yes, but you don't use sbuild in that case
[20:45] <aeoril> darkxst would I build it with a recipe then?
[20:45] <darkxst> aeoril, no, create a branch on your launchpad page and link to the bug
[20:46] <darkxst> you can then create a merge proposal
[20:46] <aeoril> darkxst how would I build/test it though?
[20:46] <darkxst> you just did didnt you?
[20:46] <aeoril> no, not yet - apparently, I am slow ...
[20:48] <aeoril> darkxst you said I would not use sbuild ... so I thought there was some other way to build/test if i made a ppa - you mentioned installing it from a ppa to test from a live session
[20:48] <aeoril> earlier
[20:48] <ricotz_> bdmurray, hi, please test-install your uploads ;)
[20:50] <aeoril> darkxst so, now I am confused
[20:50] <aeoril> darkxst I was thinking I could do the whole process using a ppa or something
[20:52] <aeoril> darkxst you mentioned I could install my compiled ubiquity from a ppa - what exactly did you mean by that please?
[20:52] <darkxst> aeoril, you can use a ppa to test, but not to submit your changes for review
[20:53] <darkxst> aeoril, dput you package to a ppa, boot a livecd, install the ppa and update
[20:53] <darkxst> then run the installer
[20:54] <aeoril> darkxst ok, cool - what exactly do you mean by "install the ppa and update" please?
[20:54] <darkxst> apt-add-repository ppa:
[20:55] <bdmurray> ricotz_: Could you elaborate?
[20:56] <ricotz_> bdmurray, try to install https://launchpad.net/ubuntu/+source/ubuntu-release-upgrader/1:15.04.8
[20:56] <ricotz_> python3-distupgrade (1:15.04.8) wird eingerichtet ...
[20:56] <ricotz_>   File "/usr/lib/python3/dist-packages/DistUpgrade/DistUpgradeViewKDE.py", line 37
[20:56] <ricotz_>     from PyQt5.QtGui import QTextOption, QPixmap, QIcon,
[20:56] <ricotz_>                                ^
[20:56] <ricotz_> SyntaxError: trailing comma not allowed without surrounding parentheses
[20:57] <aeoril> then just apt-get update then apt-get upgrade? darkxst
[20:57] <darkxst> aeoril, yes
[20:57] <aeoril> and that will add all the necessary debs from the sbuild?
[20:57] <aeoril> (so it would not install -dev or -dbg?)
[20:57] <darkxst> aeoril, yes
[20:58] <aeoril> darkxst ok, I will do that then.  Thanks.
[21:14] <aeoril> darkxst I am going to dput the ppa with the following command line:  "dput ppa:aeoril/ubiquity-bug-1422113" However, do I do it from the directory where the .dsc file is, or from the package directory where the .deb files are?
[21:15] <darkxst> aeoril, dput uploads source packages
[21:16] <aeoril> oh, ok - so not from the bzr repo where the .deb files are, but one directory up where the .dsc is?
[21:16] <aeoril> (created by debuild?)
[21:16] <darkxst> aeoril, I'm sure you can work it out
[21:17] <aeoril> ok, thanks
[21:41] <dobey> http://pastebin.ubuntu.com/10378082/ <- i'm getting this trying to set up a vivid lxc. anyone know the best way to resolve this? :-/
[21:45] <sarnold> dobey: stgraber mentioned it to pitti perhaps two hours ago, perhaps one or the other knows a bugnumber for the ureadahead issue..
[21:45] <dobey> ah ok
[21:46] <dobey> i thought it was just me; i recall having this same problem forever ago when i set up a utopic lxc or with some sbuild chroot