[08:00] <darkxst> I have ubuntu-gnome-bugs team set as bug supervisor team for ubuntu-gnome project, however members of this team can't access private bugs in the project, is this intended behavious
[08:01] <darkxst> I'm pretty certain it did used to work in the past
[08:06] <cjwatson> darkxst: Check https://launchpad.net/ubuntu-gnome/+sharing
[08:11] <darkxst> cjwatson, that shows me that user can only see his own private bugs
[08:12] <darkxst> cjwatson, bruce pieterson is a member of the bug supervisor team, and should be able to see all private bugs?
[08:12] <darkxst> or are you saying I have to manually set this on each user?
[08:20] <cjwatson> William might correct me, but I don't think bug supervisor implies sharing private bugs.  But on +sharing you can share all private bugs with that whole team.
[08:21] <cjwatson> (and private security, I guess)
[08:25] <darkxst> cjwatson, oh ok
[08:26] <darkxst> cjwatson, except, teams do seem to appear on the sharing page?
[10:28] <wgrant> darkxst: As Colin says, bug supvervisors can't implicitly see privatebugs -- they can only set importance etc.
[10:28] <wgrant> Until 2012 they were subscribed to new private bugs in some configurations, but +sharing replaces that functionality.
[10:31] <darkxst> wgrant, ok, but is ther some way to set that? given teams don't appear to show on the sharing page
[10:32] <cjwatson> darkxst: "Share with someone" and then you can pick a team
[10:32] <darkxst> cjwatson, ok
[10:32] <cjwatson> It's a javascript-only operation I think
[10:33] <cjwatson> So if you have stuff disabled in your browser I guess that might explain why you didn't notice it?
[10:34] <darkxst> cjwatson, me that won't take ubuntu-gnome-bugs, but it will accept our other teams
[10:35] <darkxst> s/me/meh/
[10:36] <cjwatson> darkxst: really?  works for me with a different project on qastaging
[10:36] <cjwatson> and ubuntu-gnome-bugs is an exclusive team (restricted), so it should work
[10:37] <darkxst> I cannot add ubuntu-gnome-bugs to ubuntu-gnome sharing page
[10:37] <cjwatson> screenshot?
[10:37] <darkxst> cjwatson, it just says "No items matched "ubuntu-gnome-bugs"
[10:38] <darkxst> I can get a screenshot if you really, but need dinner first
[10:39] <cjwatson> darkxst: http://people.canonical.com/~cjwatson/tmp/ubuntu-gnome-bugs.png
[10:40] <darkxst> cjwatson, can you try on ubuntu-gnome project? be back in half or so
[10:41] <cjwatson> Huh, indeed ...
[10:47] <cjwatson> darkxst: Oh, that's because ubuntu-gnome-bugs already has stuff shared with it
[10:47] <cjwatson> darkxst: this is all somewhat unhelpful UI, sorry, but if you go to https://launchpad.net/ubuntu-gnome/+sharing?orderby=&memo=[%22Tariq%22%2C%20%22tariq-abusheikh%22]&start=1275 then search for ubuntu-gnome-bugs and use the + icon there, you should be able to sort it out
[10:56] <darkxst> cjwatson, ok that should be sorted now, but why does it take some foo link to get teams showing up on the sharing page!
[10:56] <cjwatson> darkxst: well, I found that by paging through the list until I found ubuntu-gnome-bugs
[10:56] <cjwatson> darkxst: but this is certainly bug-worthy, it's pretty confusing
[10:57] <darkxst> ok, maybe I just missed it, it a simple filter would help, alot!
[10:57] <cjwatson> indeed
[11:07] <darkxst> cjwatson, just double checked, when I directly go via the +sharing link there are no entries starting with U
[11:09] <cjwatson> darkxst: https://launchpad.net/ubuntu-gnome/+sharing and press Next 17 times
[11:09] <cjwatson> it's sorted A-Z then a-z it seems
[11:09] <cjwatson> definitely there but this is undoubtedly a pain
[11:10] <darkxst> cjwatson, oj that would do it, I pressed last, and then back until I got U
[11:10] <cjwatson> you perhaps got to u rather than U
[11:10] <darkxst> cjwatson, yes, aparently u, is after U
[11:10] <cjwatson> and it's sorted by displayname rather than name
[11:11] <cjwatson> (which is arguable)
[11:11] <cjwatson> I tend to prefer sorting this kind of thing by name
[11:11] <darkxst> and I wouldnt care, if there was a filter ;)
[11:12] <cjwatson> quite
[11:14] <darkxst> you want me to file a bug? or are you on it?
[11:15] <cjwatson> please file a bug, I'm firefighting something else
[11:21] <darkxst> cjwatson, bug 1481717, its short, I'm hungry and gone now
[11:22] <cjwatson> darkxst: thanks
[11:49] <djjeff> https://launchpadlibrarian.net/211257553/buildlog_ubuntu-trusty-amd64.obs-studio_0.11.1-197~trusty_BUILDING.txt.gz
[11:56] <cjwatson> djjeff: that implies that your build-dependencies can't all be concurrently installed; probably something broken in that PPA
[11:56] <cjwatson> or its dependencies
[12:02] <cjwatson> djjeff: this build was nearly a month ago though, and things look installable now.  Have you considered just retrying?
[12:03] <djjeff> its not my PPA its obs-studio
[12:04] <dobey> you should contact the owner of the PPA if you have a problem with the contents of a PPA
[12:04] <cjwatson> djjeff: generally you should do ... what dobey just said; but I've retried those builds for you
[12:04] <djjeff> thank you
[12:05] <cjwatson> djjeff: ... and they still fail.  Please contact the maintainer of the PPA.
[12:05] <djjeff> they have their channel on Quakenet #obsproject
[12:05] <cjwatson> OK, feel free to ask there, but we aren't going to :)
[12:05] <cjwatson> There are a *lot* of PPAs hosted on Launchpad, we don't take responsibility for all of them building cleanly
[12:06] <djjeff> is there a new build log?
[12:06] <cjwatson> A maintainer of the PPA can come to us for help if there's something that they can't fix that seems to be an infrastructure problem
[12:06] <djjeff> does it fail because of qtbase5-dev ?
[12:06] <dobey> (or for the version of ubuntu you might use)
[12:06] <cjwatson> Yes, but it's basically the same.  https://launchpad.net/~obsproject/+archive/ubuntu/obs-studio/+build/7637229
[12:06] <cjwatson> I don't know why it's failing, somebody will have to track it down
[12:07] <cjwatson> apt doesn't give very helpful error messages when something deep in the stack is uninstallable
[12:07] <dobey> if it's for wily, and depends on wily-proposed, and you're building c++ stuff, there is a very high probability of failure at the moment, due to gcc-5 transition
[12:07] <cjwatson> dobey: this isn't wily, please don't introduce confusion
[12:14] <djjeff> faruton on quakenet is the maintainer of this PPA
[12:15] <cjwatson> djjeff: don't tell us, ask them
[12:15] <djjeff> annoying they do not use freenode
[12:15] <dobey> comlpain to them about it, not us :)
[12:15] <cjwatson> they'll have got mail notifications of the failure too
[12:16] <djjeff> I have spent almost 1 hour in their channel on quakenet and gotten nowhere
[12:17] <djjeff> it builds for utopic and vivid just fine
[12:17] <djjeff> why would trusty be any diff
[12:18] <cjwatson> I don't know, could be something in their PPA, could be something in the other random PPA they depend on, could be that build-dependencies need to be subtly different in trusty for some reason
[12:18] <cjwatson> they are welcome to come to us if they can't work it out, but we can't fix their builds for them
[12:19] <cjwatson> certainly not without their involvement
[12:22] <cjwatson> if they come to us I would be happy to discuss the problem with them and help figure it out
[12:37] <cjwatson> djjeff: The reason is mysterious, but changing "libgl-dev" to "libgl1-mesa-dev | libgl-dev" in Build-Depends is good practice anyway, and appears to fix this problem
[12:37] <cjwatson> djjeff: Please pass that on to the PPA maintainer
[12:37] <djjeff> did it build?
[12:38] <cjwatson> djjeff: It fixed the build-dependency installation in my local test rig.  I cannot apply it to that PPA myself
[12:39] <cjwatson> djjeff: That's why I'm asking you to pass it on to the PPA maintainer, since apparently you have contact with them
[12:39] <djjeff> hardly
[12:39] <cjwatson> More than I do
[12:39] <djjeff> as i said they are in #obsproject on quakenet
[12:39] <cjwatson> I've given you the exact fix to apply
[12:40] <cjwatson> You're apparently already there, you could just copy and paste what I'm saying
[12:40] <cjwatson> Otherwise I'm done
[12:40] <djjeff> I have
[12:41] <cjwatson> OK, so that should be good once they apply that change then
[12:41] <djjeff> I may just reply to his thread of obsproject forums
[12:42] <cjwatson> Thanks for passing that on
[12:43] <djjeff> replying directly to
[12:43] <djjeff> https://obsproject.com/forum/threads/ubuntu-14-04-14-10-15-04-ppa-installation-instructions.16495/
[12:43] <dobey> patience is the key. or self-directed problem solving.
[12:43] <djjeff> cjwatson: do you have a working .deb on your local test rig?
[12:44] <cjwatson> djjeff: no, I didn't run it through that far, and didn't particularly want to run untrusted code on this test rig since it isn't properly sandboxed
[12:44] <djjeff> untrusted? is it not open source?
[12:44] <cjwatson> that doesn't make it trusted
[12:44] <cjwatson> anyone can upload anything at all to a PPA
[12:45] <djjeff> can I create a PPA for myself?
[12:45] <cjwatson> sure
[12:45] <djjeff> that would be awesome!
[12:45] <cjwatson> https://help.launchpad.net/Packaging/PPA
[12:47] <cjwatson> I mean, you can trust what you like, obviously, but I hope you'll respect me being cautious about running stuff without proper sandboxing on my laptop with close-to-superuser privileges on Launchpad and Ubuntu :)
[12:48] <djjeff> your test rig is not sandboxed?
[12:48] <djjeff> heh
[12:48] <wgrant> darkxst, cjwatson: Ah, yes, I'm not sure why the person picker on +sharing doesn't just pretend you clicked the (+) icon next to the person if it's already in the list.
[12:49] <cjwatson> djjeff: I could put more effort into making it so, but it wasn't necessary for just testing out the build-dependency bits.
[12:57] <djjeff> ok cjwatson I created a thread and quoted you in it
[12:57] <djjeff> https://obsproject.com/forum/threads/obs-studio-14-04-trusty-lts-launchpad-ppa.34271/
[12:58] <djjeff> oh its awaiting moderation
[12:58] <cjwatson> thanks.
[14:03] <djjeff> the PPA maintainer is online now
[14:04] <djjeff> he was confused that you can use "or" in build depends
[14:05] <dobey> djjeff: you don't need to inform us of the general ongoings of a different channel on a different network. :)
[14:05] <djjeff> no clue why he wont just join here
[14:05] <djjeff> its his PPA not mine
[14:06] <cjwatson> are they deconfused now?
[14:06] <djjeff> I hope so.... I really want this to be dealt with so I can go on with my day
[14:06] <djjeff> and maybe get some sleep soon
[14:07] <djjeff> I might just turn on netflix and crawl into bed I am exhausted now
[14:07] <cjwatson> generally speaking, when build-depending on a virtual package (as libgl-dev is), it's a good idea to specify a preferred "real" alternative
[14:08] <cjwatson> so libgl1-mesa-dev | libgl-dev says "preferably libgl1-mesa-dev, but in a pinch, anything that provides libgl-dev will do"
[14:08] <cjwatson> I haven't worked out why that unconfuses apt in this case, but like I say, it's a good idea anyway
[14:11] <dobey> cjwatson: was something else pulling in part of the lts-utopic or lts-vivid xorg stack? i think those create some dependency confusion with the virtual packages; i had some issues there when installing the lts-utopic stack on my trusty machine for runtime.
[14:11] <cjwatson> I don't think so, but it's possible
[14:11] <cjwatson> I didn't keep the log
[14:12] <cjwatson> faruton: hi, thanks for joining.  I'm not sure how much was relayed to you?
[14:12] <faruton> Yeah, everything pertinent I believe.  Appreciate the help regarding this
[14:13] <cjwatson> dobey: it's certainly possible that apt went in that direction by default and needed prompting
[14:13] <cjwatson> it tends not to backtrack, because things get NP-complete that way
[14:15] <djjeff> ok he joined now I can /part and get on with my day thanks again cjwatson for your help
[14:15] <faruton> Apparently I was too stubborn to actually just ask about this issue, rather than declare 14.04 unfit and shove it under the carpet.  Waiting on jenkins to finish the release
[14:15] <faruton> Thanks jeff
[14:32] <cjwatson> faruton: heh, easy to do.  It wasn't an obvious problem
[15:36] <faruton> cjwatson: That appears to have fixed it, thanks!
[15:36] <cjwatson> faruton: excellent
[21:15] <mwhudson> how do you use ubuntu-archive-tools/copy-package to copy from proposed?
[21:15] <cjwatson> mwhudson: --from-suite foo-proposed
[21:22] <mwhudson> cjwatson: thanks
[21:25] <mwhudson> oh and --to-suite=foo for a ppa