[00:53] <shaderslayer> any clue why this would happen https://launchpadlibrarian.net/208794199/buildlog_ubuntu-vivid-i386.shashlik_0-0ubuntu1~ppa1_BUILDING.txt.gz
[00:54] <shaderslayer> the package with the correct version is in the PPA
[01:08] <shaderslayer> cjwatson: ^^ any clue?
[01:11] <teward> shaderslayer: potentially because that version is superseded by the repositories, but I"m not an expert
[01:11] <teward> (1.4+svn... is greater than the version you specify, by default i think systems install NewestVersion?)
[01:11] <shaderslayer> surely the dep resolver can install the older version?
[01:12] <teward> as I said, i'm not an expert, that's just an initial look at it suggesting something like that
[01:13] <shaderslayer> right
[01:18] <shaderslayer> hm
[08:33] <hyperair> hey how do i change a decision to decline someone who tried to join a team?
[08:33]  * hyperair clicked the wrong button
[08:33]  * hyperair meant to accept the request
[08:34] <cjwatson> If you have the ability to do that, you should also be able to just add them to the team directly
[11:19] <irl> Hi, when a package on Launchpad that has come from Debian but has no changes in Ubuntu has a "Maintainer", what does that actually mean?
[11:19] <irl> https://launchpad.net/ubuntu/+source/direwolf lists some guy called Frank
[11:20] <irl> but the only time I've ever heard of Frank is the time he tried to link the debian-hams mailing list to his launchpad account.
[11:50] <cjwatson> irl: That's probably why it's linked to him; at the time when the most recent version of that package was imported, that was the account that debian-hams@lists.debian.org resolved to
[11:50] <irl> ah ok
[11:50] <irl> how do i undo this?
[11:51] <cjwatson> It would fix itself the next time a new version is imported
[11:52] <irl> ok. is it possible to create a Debian Hams group on launchpad to track bugs and stuff?
[11:52] <cjwatson> I'm just trying to work out whether it's possible to fix it in its current state without database surgery
[11:54] <cjwatson> You can create teams freely, sure.  Have a look through help.launchpad.net first to think about how you want to model whatever you're doing
[11:55] <cjwatson> Yeah, SourcePackageRelease isn't exported on the API, I think this would take database surgery to fix, which I'm loath to do unless we have to
[11:57] <irl> it's not massively important
[11:57] <irl> as long as it fixes when i do next upload
[11:57] <irl> i'm working on an upload for that package right now anyway
[12:00] <cjwatson> Yep, should do
[12:01] <irl> "To claim this team, enter one of the e-mail addresses it is associated with. (We are not showing you the list of addresses to protect Debian Hamradio Maintainers's privacy in case you don't run it.) We will e-mail that address to ask for confirmation. "
[12:01] <irl> that's a problem
[12:01] <irl> we can't have the mailing list being able to have control over the account
[12:01] <irl> as it's a public mailing list
[12:02] <cjwatson> Right, create a new team, don't reuse the existing ~debian-hams
[12:02] <irl> but then none of the packages would be associated with it?
[12:03] <cjwatson> So?  Maintainer is informational anyway :)
[12:03] <cjwatson> You can still subscribe another team to bugs on the package
[12:04] <irl> seems not very automated
[12:04] <cjwatson> Full automation via Debian uploads isn't likely to happen; it would be inappropriate for us to auto-subscribe Debian maintainers to Ubuntu bugs on their packages
[12:05] <cjwatson> Some people want it, some don't
[12:06] <cjwatson> It would certainly be possible to automate keeping the subscriptions in sync at your end with an API client if you wanted to do that
[12:06] <cjwatson> But this is a case where the desired outcome varies quite a bit so it's better to have the policy live outside of Launchpad
[12:06] <irl> i'll look into doing that at some point
[19:03] <shaderslayer> cjwatson: any news on the git tagging import