/srv/irclogs.ubuntu.com/2017/03/10/#launchpad.txt

=== chihchun_afk is now known as chihchun
=== gpo is now known as gpolitis
alkisgHi, 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:27
alkisgHmm, I used this one and it worked: git remote add origin git+ssh://alkisg@git.launchpad.net/sch-scripts07:30
alkisg...although I don't understand how it managed to use the correct group name, ts.sch.gr...07:30
lmiccinihello, anybody able to help with login issues? keep getting Error ID: OOPS-XXXX. thanks.07:33
ubot5https://oops.canonical.com/?oopsid=OOPS-XXXX07:33
alkisgI try to create a new git recipe but I get a bzr recipe instead!08:29
alkisghttps://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:29
* alkisg tries that a third time...08:30
alkisgYup, I don't think I'm doing anything wrong there08:33
alkisgI follow the steps to create a git recipe and I'm getting a bzr recipe instead08:33
alkisgEven the recipe contents change08:33
* alkisg tries with a new recipe name, in case there's something wrong with launchpad cache...08:33
alkisgNope, I still got a bzr recipe, https://code.launchpad.net/~ts.sch.gr/+recipe/sch-scripts-proposed-git08:35
alkisgIt's a regression somewhere in launchpad, I was able to create git recipes in the past08:36
alkisgHelp, please? :)08:36
alkisgAh, 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 git09:48
alkisgOK, it's a viable workaround until the bug is properly fixed09:48
alkisgIt'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 recipe09:51
cjwatsonlmiccini: We can help but only if you give us the actual OOPS ID.09:51
cjwatsonalkisg: https://bugs.launchpad.net/launchpad/+bug/162392409:52
ubot5Ubuntu bug 1623924 in Launchpad itself "Source package recipes prefer Bazaar when lp:$foo alias is VCS-ambiguous" [High,Triaged]09:52
alkisgThank you cjwatson :)09:52
lmicciniHi cjwatson here it is OOPS-4d2e29bd4815255869dea1f212d75b61 thank you very much10:05
ubot5https://oops.canonical.com/?oopsid=OOPS-4d2e29bd4815255869dea1f212d75b6110:05
cjwatsonlmiccini: Thanks.  There'll be a delay, since I'm in meetings right now and then have a medical appointment10:19
lmiccinicjwatson: no worries. thanks for you help.10:20
=== chihchun is now known as chihchun_afk
cjwatsonlmiccini: 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:49
lmiccinicjwatson: Hi. I'd like to keep lmiccini as userid if possible14:52
cjwatsonEr14:54
cjwatsonThat's neither of your IDs14:54
=== chihchun_afk is now known as chihchun
EchoFogHi there16:39
EchoFogLaunchpad's bug report form seems to be broken: https://bugs.launchpad.net/ubuntu/+filebug/?no-redirect16:39
EchoFogWhen I try to submit a bug, I get this - Timeout error: Sorry, something just went wrong in Launchpad16:40
EchoFogError ID: OOPS-de2c4f605598154d1fe1af3faf5977dc16:42
ubot5https://oops.canonical.com/?oopsid=OOPS-de2c4f605598154d1fe1af3faf5977dc16:42
dobeyEchoFog: you should not file a bug against ubuntu itself, but against the package in ubuntu with which you have an issue16:44
EchoFogthe issue is not with a package but with the ubuntu 16.10 release itself16:45
EchoFogthe 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 fail16:46
EchoFogEverything worked fine up until 16.0416:47
naccEchoFog: LP can have bugs and timeouts sometimes16:48
EchoFogI believe this is not a timeout issue because apparently dobey was able to see what I submitted16:49
naccEchoFog: probably dobey was responding to the URL you used16:49
EchoFogYeah, I guess that's possible. Although I've tried more than a couple times within last 12 hours - each time the same error16:50
dobeyyeah, if you got a timeout, the bug wasn't reported i don't think16:52
dobeytry reporting it against grub-pc or lvm2 instead16:52
nacc"Original error: QueryCanceledError('canceling statement due to statement timeout\n',)"16:53
naccwas the LP OOPs16:53
EchoFogbut there really is not issue with those packages and it wouldn't be right16:53
EchoFogthe issue is with the lubuntu release package (and most likely ubuntu too - I haven't checked)16:54
naccEchoFog: lvm2 is specifically not seeded on lubuntu-live16:54
naccbut it is on the other -live images, i think16:55
nacc  ubuntu: daily-live.16:55
nacc  lubuntu: daily16:55
EchoFogany idea why it was removed? It was definitely included up until 16.0416:55
naccEchoFog: you'd want to ask lubuntu16:56
cjwatsonThat 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
EchoFogand it's so horribly broken on 16.10 that I'm surprised it hasn't been reported yet16:56
naccEchoFog: grub-pc appears to be seeded16:56
EchoFognacc: are you referring to 16.10 release or daily builds?16:57
naccEchoFog: the daily -- i'm not sure if i can easily see what was seeded on the release ISO16:57
cjwatsonFor the purposes of this particular timeout bug, it doesn't make a difference what you're trying to report it against.16:57
EchoFogthanks, will keep trying launchpad form then16:59
EchoFogSo this does appear to be lubuntu specific bug then. If lvm is seeded on other live builds but not lubuntu-live17:00
dobeyEchoFog, nacc: both grub-pc and lvm2 are on the ISO for 16.10: http://releases.ubuntu.com/16.10/ubuntu-16.10-desktop-amd64.manifest17:00
dobeyoh lubuntu? don't know about that. but then you should file a bug against lubuntu, not ubuntu :)17:00
naccdobey: yeah, lubuntu :/17:00
cjwatsonLubuntu is a flavour of Ubuntu and its bugs are tracked in the ubuntu distribution on Launchpad.17:00
naccyep17:01
dobeyright https://launchpad.net/ubuntu/+source/lubuntu-meta17:01
dobeywould be where seed bugs should go17:02
cjwatsonindeed17:02
EchoFogsure enough, both packages are missing from http://cdimage.ubuntu.com/lubuntu/releases/16.10/release/lubuntu-16.10-desktop-amd64.manifest17:02
dobeyEchoFog: ^^ you should file your bug against that package. hopefully the timeout has disappeared now17:02
EchoFogsuccessfully submitted bug against lubuntu-meta. Thanks!17:07
=== chihchun_afk is now known as chihchun
chilukis there a way to get e-mail notifications for all bugs that have a certain tag?20:34
naccchiluk: i don't think so -- but that's based upon my reading of https://help.launchpad.net/Bugs/Subscriptions20:40
chilukyeah .. that's the same conclusion I came to after reading that as well.20:41
chilukthanks nacc20:48
cjwatson21: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 changed21:17
cjwatson                 in any way (more options...) -> Bugs must match this filter (...) -> Tags21:17
cjwatsonin case anyone else here was wondering21:17
chiluk^nacc since you came to the same conclusion as I did earlier.21:18
nacccjwatson: ah interesting21:19
cjwatsonalso API methods such as addBugSubscription and addBugSubscriptionFilter, though I've never tried doing anything that way21:20
naccchiluk: thanks21:21

Generated by irclog2html.py 2.7 by Marius Gedminas - find it at mg.pov.lt!