[00:00] <mwhudson> i guess it's trying to display the unmerged revisions
[00:00] <Rhamphoryncus> which might be all of them..
[00:01] <Rhamphoryncus> maybe I should have deleted instead ;)
[00:01] <thumper> OMG
[00:02] <mwhudson> eh, there doesn't seem to be any limit on how many revisions we display...
[00:02] <thumper> ah, no
[00:02] <thumper> I didn't think of that
[00:03] <thumper> oops
[00:03] <thumper> Rhamphoryncus: my fault, sorry
[00:04] <Rhamphoryncus> thumper: no worries.  I'm good at breaking things.
[00:04] <thumper> mwhudson: have you filed a bug yet?
[00:04] <mwhudson> thumper: no
[00:04] <thumper> mwhudson: ok, I'll do it
[00:04] <mwhudson> cool
[00:05] <thumper> Rhamphoryncus: bug 257770
[00:06] <Rhamphoryncus> thanks
[00:20] <Rhamphoryncus> fwiw, that bug only has a minor effect on me.  All my work will be done in a different branch
[02:14] <Leefmc> Question: I am having trouble pushing to launchpad, and its the same trouble i had before. I can't quite remember the solution last time, but it had something to do with telling BZR my launchpad account name.. any thoughts?
[02:15] <Leefmc> Using the command mentioned on the project page.
[02:15] <Leefmc> push lp:blah
[02:16] <mwhudson> Leefmc: bzr launchpad-login <you>
[02:16] <Leefmc> mwhudson: Thank you. They need to fix that error heh, it makes zero sense :/
[02:17] <Leefmc> "bzr: ERROR: Transport operation not possible: http does not support mkdir()" heh
[02:17] <Leefmc> well, sense in the terms of needing to give your login info
[02:17] <mwhudson> Leefmc: it's fixed in bzr 1.4 and newer
[02:18] <mwhudson> it's just a shame that 1.3 is in hardy :/
[02:18] <Leefmc> mwhudson: IIRC, many launchpad's have repos dont they? I can probably just add a bzr release repo
[02:18] <mwhudson> you certainly can
[02:19] <mwhudson> Leefmc: https://edge.launchpad.net/~bzr/+archive
[02:20] <Leefmc> mwhudson: Heh, yea, some bit of info on what these errors mean would be helpful. I got an error when adding my login name. Something about ssh keys permanently being redirected to my launchpad account +sshkeys
[02:20] <mwhudson> um
[02:20] <mwhudson> i forget what that one means
[02:20] <Leefmc> mwhudson: Or rather, not what they mean, but why they are happening. (Ie, doing one thing and getting a rather oddly worded error seeming semi-unrelated) heh
[02:21] <mwhudson> if you paste the message into google you'll probably find out
[02:21] <mwhudson> and yeah, these crappy errors are bugs
[02:21] <mwhudson> (some of them are fixed bugs too)
[02:21] <Leefmc> mwhudson: Only so much of it though, hopefully its enough, since my account name is scattered through
[02:22] <Leefmc> mwhudson: Found it.
[02:23] <Leefmc> mwhudson: My name was capitalized, when all launchpad accounts are lowercase right? I think in the end it means the account name was wrong.
[02:23] <Leefmc> mwhudson: Horrible error for that name hah.
[02:24] <mwhudson> Leefmc: oh right, that rings a bell
[02:24] <mwhudson> yes, it's a bug
[02:24] <Leefmc> Ah. think my ssh key on launchpad is from my laptop
[02:24] <Leefmc> oops
[02:24] <Leefmc> mwhudson: https://bugs.launchpad.net/launchpad-bazaar/+bug/251008
[02:26]  * mwhudson does some stuff to the bug
[02:48] <Leefmc> mwhudson: When pushing to launchpad, from a working directory, does --use-existing-dir copy from my working dir? In other words, should i be uploading from the actual branch? Or is uploading from the working dir fine
[02:48] <Leefmc> mwhudson: Because i also need to supply a .bzr dir
[02:49] <Leefmc> And obviously, im not entirely sure what happens from the argument, but rather i was told to use it heh
[02:51] <Leefmc> I suppose i should be asking, what is the best practice? What _should_ i be doing? Because i could easily be doing it wrong, so forcing the dir may not be needed.
[03:32] <Hobbsee> will the wiki login stuff be fixed soon?
[03:32] <Hobbsee> or if not, is there a workaround?
[03:33] <Hobbsee> so that people can log in, adn do edits?
[03:33] <mwhudson> i don't think the problem is at the launchpad end, but i could be wrong
[03:34] <Hobbsee> where's the problem?
[03:34] <mwhudson> i don't know, i admit
[03:34] <Hobbsee> hm, seems the guy could log in, finally.
[03:34] <Hobbsee> would be nice to see it fixed, though.
[05:20] <barry> #python-dev
[05:22] <mwhudson> quick!  follow him!
[08:01] <doctormo> Rinchen: hello
[08:18] <BUGabundo_work> good morning
[08:19] <BUGabundo_work> I would like to call your attention to https://answers.launchpad.net/launchpad/+question/42139
[09:11] <mvo> what do I have to do to request ownership of "https://edge.launchpad.net/python-apt" ? the description is hugly inaccurate, I would like to fix that [I'm upstream of pyhton-apt]?
[09:22] <BjornT_> mvo: best to ask a question at https://answers.edge.launchpad.net/launchpad/+addquestion
[09:23] <BjornT_> i don't think anyone with permission to change the owner is around at the moment
[09:23] <mvo> thanks BjornT_!
[10:33] <klette> gmb: Are the blueprints reset when the import takes place, or can we start using them at once?
[10:33] <gmb> klette: The import doesn't touch blueprints, so you can start using it straight away.
[10:34] <klette> good shit :-)
[11:12] <BUGabundo_work> ola trmanco
[11:13] <trmanco> ola
[11:49] <wgrant> al-maisan: Will Signed-By only be shown if it and Changed-By differ?
[11:52] <al-maisan> wgrant: the fields are compared to the maintainer on an individual basis and are included in the email if they differ from the maintainer
[11:52] <al-maisan> wgrant: so, the short answer is: no :)
[11:52] <wgrant> al-maisan: I think it would make sense to omit Signed-By only when it matched Changed-By, but I guess Matt's opinion matters more!
[11:53] <al-maisan> wgrant: hmm, I see.
[11:53] <wgrant> Signed-By and Changed-By will normally be the same.
[11:53] <wgrant> Changed-By and Maintainer not so often.
[11:53] <persia> al-maisan: Is it not only the exceptional case that the Maintainer matches the Signed-By?  Also, what about the Uploaders: field?
[11:54] <al-maisan> persia: I am not sure about the 'Uploaders:' field, need to look it up first
[11:55] <wgrant> Also, can you clarify who is named at the end of the changelog?
[11:55] <benje> hi how we cancel an attachement before save change to send only message ?
[11:55] <wgrant> Matt's says Maintainer, but it should be Changed-By.
[11:55] <wgrant> benje: /win 8
[11:55] <persia> al-maisan: In cases where a package is team-maintained, Maintainer: is typically a mailing list, and Uploaders: lists the set of email addresses on which a match to Changed-By will be considered a "Maintainer Upload" in Debian.  If Ubuntu has the concept of Maintainers (something I personally doubt), this behaviour ought be preserved.
[11:56] <wgrant> Gah.
[11:56] <al-maisan> re. the Maintainer matching the Signed-By: in my limited experience they would differ most of the time.
[11:56] <bigjools> wgrant: I was wondering about that
[11:56] <wgrant> benje: Clear the attachment box, perhaps.
[11:56] <benje> wgrant, not working
[11:56] <wgrant> benje: Ah, Firefox 3?
[11:56] <benje> select nothing not working too wgrant
[11:56] <al-maisan> persia: thanks for the elaboration, will check whether we support that mechanism.
[11:56] <benje> yes
[11:56] <wgrant> benje: You probably have no choice but to refresh the page, copying the comment.
[11:56] <benje> doesn't work it keep it
[11:56] <benje> :/
[11:57] <benje> unlog relog :/
[11:57] <wgrant> benje: Ctrl+Shift+R might clear the fields.
[11:57] <benje> yes thanks wgrant ;)
[11:57] <wgrant> benje: np
[11:58] <wgrant> Apart from showing Signed-By too often and giving Maintainer instead of Changed-By in the attribution line, it looks like a much more pleasant format.
[12:00] <persia> By the way, which bug number are we discussion?  I appear not to be subscribed.
[12:00] <wgrant> persia: Bug #250820
[12:00] <persia> wgrant: Thanks.
[12:01] <al-maisan> wgrant: point taken. Will have another chat with Matt.
[12:02] <al-maisan> wgrant: what do you mean by "showing Signed-By too often"?
[12:03] <wgrant> al-maisan: In most cases, Signed-By will differ from Maintainer but will match Changed-By.
[12:03] <wgrant> al-maisan: Your changes apparently show it whenever it doesn't match Maintainer.
[12:03] <al-maisan> wgrant: gotcha!
[12:03] <wgrant> (also, showing Signed-By on SPR pages would be nice)
[12:04] <al-maisan> interesting..
[12:07] <persia> wgrant: Are you commenting about Signed-By/Changed-By in the bug or in email?  (alternately, I'd be happy to do so)
[12:07] <wgrant> persia: I'm a tad busy right now - feel free to.
[12:08] <persia> wgrant: OK.  Just didn't want to post your comments for all to see without your acquiescence :)
[12:12] <mdz> wgrant: it's a bit tricky, I think
[12:12] <mdz> because in some cases, the person who made the changes is Maintainer (e.g. Debian sync) and in others it is Changed-By
[12:12] <mdz> given that we're using something close to the changelog format, I think that gets confusing
[12:13] <mdz> I think it should be "author of the changes"
[12:14] <mdz> and Changed-By should be "person who effected the changes in Ubuntu"
[12:34] <wgrant> mdz: How do we know who made the changes?
[12:34] <persia> mdz: Using "author of the changes" makes even more sense than any of the available fields.
[12:34] <wgrant> mdz: All we have is the changed-by.
[12:34] <persia> wgrant: parse the changelog directly.
[12:35] <wgrant> Maintainer is likely to be wrong more than Changed-By is.
[12:35] <wgrant> (but yes, "author of the changes" would make more sense still)
[12:36] <persia> Does Signed-By as received by Soyuz for syncs match Signed-By in Debian?
[12:37]  * persia would think not, as the .changes is being mangled
[12:37] <mdz> wgrant: we have the person who wrote the changelog entry, the person who uploaded the package to Ubuntu, and the person who sponsored it (if any)
[12:38] <mdz> the person who wrote the changelog entry is close enough to the author of the changes
[12:38] <mdz> persia: I'm not even sure the .changes is signed in  that case; if so, it's probably by an automatic key
[12:38] <mdz> since syncs don't go through the normal upload process
[12:38] <persia> mdz: I believe it to be an automatic key.
[12:39] <persia> The point being that it becomes exceedingly unlikely, even for syncs, that Signed-By: matches the maintainer (or even author of the changes)
[12:39] <mdz> I think the cases are "X uploaded their own changes to Ubuntu", "X uploaded Y's changes to Ubuntu", and "X synced in Y's changes from Debian"
[12:39] <mdz> al-maisan: does that make sense?
[12:40] <persia> Right, but only in rare cases do any of those have any relation to Maintainer:
[12:40] <persia> (well, in the third case, Y is likely to be the maintainer, but that's not the information we are extracting)
[12:44] <wgrant> mdz: Do we have the person who wrote the changelog entry? Where do we get that?
[12:46] <mdz> wgrant: from the changelog?
[12:47] <mdz> wgrant: that's copied into Maintainer: in .changes typically
[12:47] <mdz> unless it's overridden
[12:48] <mdz> er, Changed-By
[12:48] <wgrant> Changed-By, you mean?
[12:48] <wgrant> Right.
[12:48] <wgrant> So the first two people that you mentioned above are the same person.
[12:48] <mdz> persia: correct
[12:48] <mdz> wgrant: which two?
[12:48] <mdz> oh, changelog author and uploader? yes, for the upload case
[12:48] <wgrant> "we have the person who wrote the changelog entry, the person who uploaded the package to Ubuntu, and the person who sponsored it (if any)"
[12:48] <mdz> no, for the sync case
[12:48] <wgrant> Right.
[12:48] <wgrant> True.
[12:49] <wgrant> Forgot about that.
[12:49] <mdz> I think it's clearer to think of the three cases I outlined with X and Y
[12:49] <wgrant> It is.
[12:49] <wgrant> So in the third we have three distinct people.
[12:49] <wgrant> The other two just two.
[12:49] <persia> For the sync case, there's still typically only two people that interest us, although they are a different two people.
[12:49] <persia> wgrant: Do we really care which archive-admin sync'd the package?
[12:50] <wgrant> persia: No, but we care who requested it.
[12:50] <persia> (or whether the automated key did it for the less complex syncs)
[12:50] <wgrant> For a sync, we have the Maintainer and Changed-By from Debian, but the Changed-By is currently replaced by the sync requestor.
[12:50] <__pok> Hi all. I'm a first-time bzr user: how do I get the "lp" URL aliases in place?
[12:50] <persia> Changed-By is typically set to requestor.  Do we care who approved it?  I'm not sure how we can get that into Signed-By,
[12:50] <persia> Also the archive admins sometimes set Changed-By to the requestor, and sometimes to the approver.
[12:50] <wgrant> persia: Right. That would be nice.
[12:51] <persia> __pok: bzr launchpad-login
[12:51] <__pok> could it be that I'm using the wrong version of bzr?
[12:52] <LarstiQ> persia: well, lp:foo also works, but with http instead of ssh
[12:52] <LarstiQ> __pok: what version are you using?
[12:52] <__pok> ahaa, it was from Debian Etch (read: ages old)
[12:54] <mdz> wgrant: I'll summarize in the bug
[12:54] <wgrant> mdz: Thanks.
[12:56] <mdz> wgrant: who requested it ends up in Changed-By
[13:01] <wgrant> mdz: Hm? Isnt't that what I said?
[13:01] <wgrant> -t
[13:01]  * al-maisan just came back from lunch ..
[13:02] <al-maisan> I am reading the screen log..
[13:05] <al-maisan> mdz: I understand Soyuz does not actually have the uploader of a package..
[13:06] <al-maisan> all we have is the maintainer, the changed-by and (if the changes file was signed) the signer
[14:01] <persia> al-maisan: Uploader == Signed-By except in cases where someone hijacked someone else's signed changes file.
[14:01] <persia> (but as it's anonymous FTP, it's safe to make that assumption)
[14:06] <al-maisan> persia: thanks for the clarification.
[14:31] <delcides> hi. I'd like to help the Ubuntu translation. How do I go about it ?
[14:39] <Ursinha> oh
[14:40] <Ursinha> people give up fast :P
[14:40] <trmanco> lol
[14:40] <beuno> anything over a minute is too much!
[14:40] <trmanco> they sure do :P
[14:41] <trmanco> time is money :P
[14:42] <Ursinha> trmanco, :)
[14:47] <persia> On the other hand, there are surely more informative fora than this for that question.
[15:12] <mdz> al-maisan: changed-by is the person who uploaded it, so you do have that
[15:12] <mdz> al-maisan: sorry, the terminology is a bit confusing
[15:12] <al-maisan> mdz: true.
[15:13] <mdz> al-maisan: usually the "uploader" is the person who prepared the .changes file
[15:13] <mdz> al-maisan: it may be actually uploaded to launchpad by someone else (who signs it on their behalf)
[15:13] <al-maisan> Ah, I see.
[15:13] <mdz> the fact that our workflow is different from Debian's but we share terminology is confusing sometimes
[15:14] <mdz> al-maisan: the .changes is a manifest for an update to a package (an "upload").  it contains both information about the package itself and about the upload process
[15:15] <al-maisan> mdz: that's understood .. I have looked at a few changes files in order to get an idea of the data involved
[15:16] <mdz> al-maisan: is there anything else I can help to clarify?
[15:17] <al-maisan> mdz: let me digest the information that was provided so far. I may ask you a few questions later.
[15:17] <al-maisan> mdz: Thanks very much!
[16:21] <bdmurray> I still can't moderate messages to the ubuntu-bugcontrol list due to OOPses
[16:45] <BjornT_> barry: can you give bdmurray a status update of the fix for the moderation oops?
[16:45] <barry> bdmurray: branch was approved, waiting for the db approval
[16:46] <bdmurray> barry: okay, thanks for letting me know!
[16:46] <barry> bdmurray: i'll update the bug
[16:47] <bdmurray> barry: I never submitted a bug that I know of ;)  If there is one could you subscribe me?
[16:47] <barry> bdmurray: bug 257352 -- what's your lp nick?
[16:50] <bdmurray> barry: 'brian-murray'
[16:51] <barry> bdmurray: cool, i've subscribed you
[16:54] <hacim> how do I checkout some code from launchpad?
[16:55] <hacim> I dont see the bzr URI anywhere on this page: https://code.launchpad.net/~pkg-sphinx/pkg-sphinx/trunk
[16:55] <hacim> "bzr branch lp:pkg-sphinx" is not valid
[16:55] <beuno> hacim, that should be valid
[16:55] <beuno> what version of bzr are you using?
[16:56] <hacim> beuno: oh, ok, i figured it wasn't a valid URI so it wouldn't resolve, I didn't realize the 'lp' would be an alias to an actual resolvable host
[16:56] <beuno> hacim, ah, yes. There's a launchpad plugin included by default that does all the necessary magic
[16:57] <kiko> lp: magic
[16:57] <kiko> beuno, thanks for the UI email. now I need to think about that. damn.
[16:58] <beuno> kiko, always happy to try and change people's plans around  :)
[17:09] <hacim> i do not like magic :)
[17:09] <hacim> adios
[18:05] <seb_kuzminsky> launchpad is not mirroring my bzr branch: https://code.launchpad.net/~seb-highlab/emc/5i20-stepgen-fix
[18:05] <seb_kuzminsky> the "KeyboardInterrupt" message seems suspect to me...  any ideas what's up here?
[18:13] <kiko-fud> seb_kuzminsky, let me check
[18:14] <kiko-fud> seb_kuzminsky, that's weird. abentley, rockstar: can you help him?
[18:15] <abentley> seb_kuzminsky, kiko-fud: KeyboardInterrupt is raised when no progress has been shown for a long time.
[18:15] <seb_kuzminsky> hm...
[18:15] <seb_kuzminsky> my cable modem uplink is too slow?  it's about 45 KB/s
[18:16] <seb_kuzminsky> or something's stallign somewhere
[18:16] <kiko-fud> that's like 1000x faster than mine :-(
[18:16] <rockstar> I'm trying to pull the original branch, and it seems stuck.
[18:16] <kiko-fud> trying too
[18:17] <abentley> kiko-fud: (We kill with SIGINT, which Python always handles by raising KeyboardInterrupt)
[18:17] <kiko-fud> abentley, yeah, a bit misleading -- I wonder if we could massage that when displaying it to the end-user?
[18:18] <seb_kuzminsky> i see two hosts downloading and both seem to be running fine
[18:18] <rockstar> Yea, and the slow net would definitely cause a problem.
[18:19] <rockstar> seb_kuzminsky, do you have other mirrored branches from this site that are on Launchpad?
[18:19] <seb_kuzminsky> a couple
[18:22] <kiko-fud> seb_kuzminsky, it's slow, but progressing
[18:22] <seb_kuzminsky> who you calling slow?  ;-)
[18:23] <seb_kuzminsky> i did do one sort of bogus thing with this branch...  i accidentally tried to push it to itself (typing in the wrong window)
[18:24] <seb_kuzminsky> if y'all's branch of it doesnt work i'll try removing it on my external webserver and pushing clean copy from the other machine
[18:25] <kiko-fud> seb_kuzminsky, ziz inzernet zing
[18:25] <rockstar> seb_kuzminsky, it's going, but your uplink connection is not great.  That's probably what causes the problem.
[18:26] <seb_kuzminsky> the other lp-mirrored branches hosted on the machine had no problems (upstream, upstream-2.2, and hostmot2)
[18:27] <seb_kuzminsky> there have been some http reqests for files that apache can't find:
[18:28] <seb_kuzminsky> /home/seb/public_html/bzr/emc2/5i20-stepgen-fix/.bzr/smart
[18:28] <seb_kuzminsky> /home/seb/public_html/bzr/emc2/5i20-stepgen-fix/.bzr/repository/format
[18:28] <seb_kuzminsky> /home/seb/public_html/bzr/emc2/.bzr/smart
[18:28] <kiko-fud> I think that's normal
[18:28] <seb_kuzminsky> that's it so far
[18:28] <kiko-fud> seb_kuzminsky, but http:// isn't the best way to serve bzr branches..
[18:28] <seb_kuzminsky> you guys thought it was slow before with just the two of you downloading, vostok just started another attempt
[18:29] <seb_kuzminsky> kiko-fud: it is if your users don't use bzr ;-)
[18:29] <rockstar> seb_kuzminsky, also, when branching, I get Format <RepositoryFormatKnit1> for http://highlab.com/%7Eseb/bzr/emc2/.bzr/ is deprecated - please use 'bzr upgrade' to get better performance
[18:29] <kiko-fud> go vostok go :)
[18:29] <kiko-fud> seb_kuzminsky, ah, please do upgrade to packs, it will be much faster
[18:30] <seb_kuzminsky> ok, will do
[18:30] <seb_kuzminsky> is that safe to do while people are branching?
[18:32] <kiko-fud> seb_kuzminsky, it might cause the branch operations to fail, but aprt from that it is safe
[18:35] <seb_kuzminsky> kiko-fud: ok i'll wait a bit
[19:00] <Rinchen> >> Come join the Launchpad dev meeting on #launchpad-meeting.  Everyone is welcome. Starts, now!
[19:02] <seb_kuzminsky> lp failed to branch again
[19:03] <seb_kuzminsky> upgrading my repo format now
[19:13] <DnaX> hi
[19:14] <DnaX> how can I upload a tarball on lunchpad?
[19:16] <kiko> DnaX, create a release, and upload the tarball into it
[19:16] <DnaX> kiko: thanks
[19:17] <DnaX> ah
[19:18] <DnaX> about vcs import, I would import another person's branch because developmen is still
[19:18] <DnaX> now this vcs import is failed
[19:20] <DnaX> https://code.edge.launchpad.net/~vcs-imports/ircp-tray/0.7.2
[19:21] <DnaX> I use only snapshot, I wouldn't edit sources
[19:22] <mwhudson> we can't import from :ext: $CVSROOTs currently
[19:22] <mwhudson> though there is this patch...
[19:22] <thumper> DnaX: the comment on the branch says: The path to the pserver contains "developername" and seems to require ssh authentication
[19:23]  * thumper didn't notice the ext
[19:23] <DnaX> seems...
[19:27] <DnaX> bye
[19:28] <mwhudson> another satisfied customer!
[20:10] <seb_kuzminsky> kiko, rockstar: i upgraded my repo to packs and it worked, thanks!
[20:10] <rockstar> seb_kuzminsky, great!
[20:12] <kiko> seb_kuzminsky, tell you, packs are the future (lifeless wink)
[20:13] <seb_kuzminsky> thanks again, launchpad rocks my world
[20:13] <seb_kuzminsky> bye!
[20:13] <kiko> cheers
[20:17] <Ursinha> it's so cool when people enjoy something you believe in
[20:17] <Ursinha> :)
[20:22] <Rinchen> meeting date change
[20:50] <krow> Any LP folks around?
[20:52] <beuno> krow, sure, hi
[20:53] <krow> beuno: This link is going tits up: http://bazaar.launchpad.net/~drizzle-developers/drizzle/development/revision/324
[20:53] <krow> beuno: Is something broken on reading revisions right now?
[20:53] <beuno> krow, not that we know of, but mysql branches tend to be large, and make the servers mad at them sometimes
[20:53] <beuno> mwhudson, ^
[20:54] <mwhudson> oh yay
[20:54]  * mwhudson bounces loggerhead
[20:54] <krow> beuno: That is drizzle though. I killed off all the mysql history in order to give us speedier branch times :)
[20:55] <mwhudson> krow: try now
[20:56] <mwhudson> krow: but be warned, your browser may not love you for it...
[20:57]  * mwhudson waits for ff to stop being grey
[20:58] <krow> mwhudson: And the magic 8 ball says....  loaded slowly, but did load.
[20:58] <mwhudson> it seems like it's a pretty big revision
[21:02] <krow> mwhudson: It worked though. Excellent.   We have a lot of refactoring to still do. I will be half tempted to start the tree all over again when we hit a point a bit further into the process.
[21:02] <krow> mwhudson: Thank you very much!
[21:02] <mwhudson> krow: hopefully stacked branches will result in less worries about history size
[21:02] <mwhudson> krow: np
[22:04] <Leftmost> So I'd like some opinions on the BSD licensing requirement for translations. I'm the upstream GNOME coordinator for my language and I'm unwilling to accept the licensing change. Does this mean that my upstream work is no longer usable in Ubuntu? It seems like that would be the case.
[22:28] <wgrant> bigjools: Did you mean to close #159304? It doesn't look rolled-out.
[22:30] <bigjools> wgrant: how can you tell?
[22:30] <wgrant> bigjools: I can still see signatures.
[22:30] <wgrant> (on old PPA uploads)
[23:28] <bdmurray> kiko-afk: are you really afk? ;)
[23:43] <tgm4883_laptop> looking for some team hierarchy guidence.  We have 2 teams (Mythbuntu and Mythbuntu-bugs) and were wondering whether the bug team should be in the Mythbuntu team, or if the Mythbuntu team should be a member of the bug team.  We don't want the bug team to have access to the ppa, code, etc.