[07:27] <alkisg> Hi, I'm trying to convert lp:sch-scripts from bzr to git. The bzr branch was lp:~ts.sch.gr/sch-scripts/trunk, but I was using `bzr pull lp:sch-scripts` to pull. For git, what's the correct origin command before pushing? `git remote add origin lp:~ts.sch.gr/sch-scripts/trunk` ?
[07:30] <alkisg> Hmm, I used this one and it worked: git remote add origin git+ssh://alkisg@git.launchpad.net/sch-scripts
[07:30] <alkisg> ...although I don't understand how it managed to use the correct group name, ts.sch.gr...
[07:33] <lmiccini> hello, anybody able to help with login issues? keep getting Error ID: OOPS-XXXX. thanks.
[08:29] <alkisg> I try to create a new git recipe but I get a bzr recipe instead!
[08:29] <alkisg> https://code.launchpad.net/~ts.sch.gr/sch-scripts/+git/sch-scripts/+ref/master/+new-recipe => I see "# git-build-recipe format 0.4 deb-version {debversion}~{revtime}", I click "Create Recipe" and then I get "# bzr-builder format 0.4 deb-version {debversion}~{revtime}"!!!
[08:30]  * alkisg tries that a third time...
[08:33] <alkisg> Yup, I don't think I'm doing anything wrong there
[08:33] <alkisg> I follow the steps to create a git recipe and I'm getting a bzr recipe instead
[08:33] <alkisg> Even the recipe contents change
[08:33]  * alkisg tries with a new recipe name, in case there's something wrong with launchpad cache...
[08:35] <alkisg> Nope, I still got a bzr recipe, https://code.launchpad.net/~ts.sch.gr/+recipe/sch-scripts-proposed-git
[08:36] <alkisg> It's a regression somewhere in launchpad, I was able to create git recipes in the past
[08:36] <alkisg> Help, please? :)
[09:48] <alkisg> Ah, the bug is that it thinks that lp:sch-scripts is bzr, while if I put the whole path, lp:~ts.sch.gr/sch-scripts/+git/sch-scripts, then it realizes it's git
[09:48] <alkisg> OK, it's a viable workaround until the bug is properly fixed
[09:51] <alkisg> It's a bit annoying that it rewrites lp:~ts.sch.gr/sch-scripts/+git/sch-scripts to lp:sch-scripts and then thinks it's bzr; so I have to remember to use the correct one every time I edit the recipe
[09:51] <cjwatson> lmiccini: We can help but only if you give us the actual OOPS ID.
[09:52] <cjwatson> alkisg: https://bugs.launchpad.net/launchpad/+bug/1623924
[09:52] <alkisg> Thank you cjwatson :)
[10:05] <lmiccini> Hi cjwatson here it is OOPS-4d2e29bd4815255869dea1f212d75b61 thank you very much
[10:19] <cjwatson> lmiccini: Thanks.  There'll be a delay, since I'm in meetings right now and then have a medical appointment
[10:20] <lmiccini> cjwatson: no worries. thanks for you help.
[14:49] <cjwatson> lmiccini: Hi, sorry for the delay.  You had an old account, and I guess you must have deleted your login.ubuntu.com account at some point and then tried to recreate it.  Do you want to keep your old Launchpad account name?
[14:52] <lmiccini> cjwatson: Hi. I'd like to keep lmiccini as userid if possible
[14:54] <cjwatson> Er
[14:54] <cjwatson> That's neither of your IDs
[16:39] <EchoFog> Hi there
[16:39] <EchoFog> Launchpad's bug report form seems to be broken: https://bugs.launchpad.net/ubuntu/+filebug/?no-redirect
[16:40] <EchoFog> When I try to submit a bug, I get this - Timeout error: Sorry, something just went wrong in Launchpad
[16:42] <EchoFog> Error ID: OOPS-de2c4f605598154d1fe1af3faf5977dc
[16:44] <dobey> EchoFog: you should not file a bug against ubuntu itself, but against the package in ubuntu with which you have an issue
[16:45] <EchoFog> the issue is not with a package but with the ubuntu 16.10 release itself
[16:46] <EchoFog> the root of the problem is that the lvm2 & grub-pc have been removed from the live installation image starting with 16.10 causing some configurations to fail
[16:47] <EchoFog> Everything worked fine up until 16.04
[16:48] <nacc> EchoFog: LP can have bugs and timeouts sometimes
[16:49] <EchoFog> I believe this is not a timeout issue because apparently dobey was able to see what I submitted
[16:49] <nacc> EchoFog: probably dobey was responding to the URL you used
[16:50] <EchoFog> Yeah, I guess that's possible. Although I've tried more than a couple times within last 12 hours - each time the same error
[16:52] <dobey> yeah, if you got a timeout, the bug wasn't reported i don't think
[16:52] <dobey> try reporting it against grub-pc or lvm2 instead
[16:53] <nacc> "Original error: QueryCanceledError('canceling statement due to statement timeout\n',)"
[16:53] <nacc> was the LP OOPs
[16:53] <EchoFog> but there really is not issue with those packages and it wouldn't be right
[16:54] <EchoFog> the issue is with the lubuntu release package (and most likely ubuntu too - I haven't checked)
[16:54] <nacc> EchoFog: lvm2 is specifically not seeded on lubuntu-live
[16:55] <nacc> but it is on the other -live images, i think
[16:55] <nacc>   ubuntu: daily-live.
[16:55] <nacc>   lubuntu: daily
[16:55] <EchoFog> any idea why it was removed? It was definitely included up until 16.04
[16:56] <nacc> EchoFog: you'd want to ask lubuntu
[16:56] <cjwatson> That timeout bug is something we suffer from periodically, but it generally goes away within about 10 minutes.  We haven't got to the bottom of it yet.
[16:56] <EchoFog> and it's so horribly broken on 16.10 that I'm surprised it hasn't been reported yet
[16:56] <nacc> EchoFog: grub-pc appears to be seeded
[16:57] <EchoFog> nacc: are you referring to 16.10 release or daily builds?
[16:57] <nacc> EchoFog: the daily -- i'm not sure if i can easily see what was seeded on the release ISO
[16:57] <cjwatson> For the purposes of this particular timeout bug, it doesn't make a difference what you're trying to report it against.
[16:59] <EchoFog> thanks, will keep trying launchpad form then
[17:00] <EchoFog> So this does appear to be lubuntu specific bug then. If lvm is seeded on other live builds but not lubuntu-live
[17:00] <dobey> EchoFog, nacc: both grub-pc and lvm2 are on the ISO for 16.10: http://releases.ubuntu.com/16.10/ubuntu-16.10-desktop-amd64.manifest
[17:00] <dobey> oh lubuntu? don't know about that. but then you should file a bug against lubuntu, not ubuntu :)
[17:00] <nacc> dobey: yeah, lubuntu :/
[17:00] <cjwatson> Lubuntu is a flavour of Ubuntu and its bugs are tracked in the ubuntu distribution on Launchpad.
[17:01] <nacc> yep
[17:01] <dobey> right https://launchpad.net/ubuntu/+source/lubuntu-meta
[17:02] <dobey> would be where seed bugs should go
[17:02] <cjwatson> indeed
[17:02] <EchoFog> sure enough, both packages are missing from http://cdimage.ubuntu.com/lubuntu/releases/16.10/release/lubuntu-16.10-desktop-amd64.manifest
[17:02] <dobey> EchoFog: ^^ you should file your bug against that package. hopefully the timeout has disappeared now
[17:07] <EchoFog> successfully submitted bug against lubuntu-meta. Thanks!
[20:34] <chiluk> is there a way to get e-mail notifications for all bugs that have a certain tag?
[20:40] <nacc> chiluk: i don't think so -- but that's based upon my reading of https://help.launchpad.net/Bugs/Subscriptions
[20:41] <chiluk> yeah .. that's the same conclusion I came to after reading that as well.
[20:48] <chiluk> thanks nacc
[21:17] <cjwatson> 21:11 <cjwatson> chiluk: You have to pick a target (project, distribution, etc.), but after that, go to the bugs page for the target (e.g. https://bugs.launchpad.net/ubuntu) -> Edit bug mail -> Add a subscription -> are added or changed
[21:17] <cjwatson>                  in any way (more options...) -> Bugs must match this filter (...) -> Tags
[21:17] <cjwatson> in case anyone else here was wondering
[21:18] <chiluk> ^nacc since you came to the same conclusion as I did earlier.
[21:19] <nacc> cjwatson: ah interesting
[21:20] <cjwatson> also API methods such as addBugSubscription and addBugSubscriptionFilter, though I've never tried doing anything that way
[21:21] <nacc> chiluk: thanks