[02:16] Happy new year! [02:17] Marcin Mikołajczak: agreed [05:57] hey @degville [10:56] Join [10:58] Hi All! [12:28] hi [13:31] Hi [13:38] hi [13:38] friends [13:46] hi [13:48] joined === d__ is now known as Guest98957 [15:13] hi popey [15:13] HAPPY NEW YEAR to all! [15:14] hi [15:14] :) [15:14] popey: I know it's festival time but when do you think the mentors will be a bit free? [15:15] Tomorrow i think everyone will be back to normal [15:15] popey: a question regarding snapcraft [15:15] ok [15:15] why is it available to be installed via both apt and snap [15:15] is there a difference? [15:16] yeah what's the difference? [15:16] nice question. i also need the answer [15:18] Good question! [15:18] popey: please remove this task as iso testing for upgrade lubuntu is closed now [15:18] At the start, snap couldn't do what snapcraft needed, so it was made as a deb initially. [15:18] Now that snaps (via classic and other things) can do everything snapcraft needs, there's not so much need for the deb. [15:19] The snap allows the snapcraft developers to push out new versions very rapidly. [15:19] Putting an updated deb out can take days, maybe a week or more. [15:20] ok noted. [15:20] So can we assume that installation via snap is better than via apt? [15:23] popey: please remove this task as iso testing for upgrade lubuntu is closed now [15:23] Run the Lubuntu upgrade tests and report your results [15:27] popey: in this case would it be good to let people know to install from snap instead from apt in the tutorials? [15:27] or it doesn't really matter much [15:27] I thought we did? [15:30] popey: if we do typo error in a command in Ubuntu terminal why does it not run the right command instead of suggesting the right command. For ex, if i type snapraft ubuntu says No command 'snapraft' found, did you mean: Command 'snapcraft' from package 'snapcraft' (universe) snapraft: command not found. Why does it not straightaway run snapcraft [15:32] popey: You did not :) [15:33] omairqazi: because it can't assume it knows what you want [15:33] it can guess [15:34] ok [15:35] who is simon quigley [15:36] tsimonq2 [15:37] and carla sella? [15:37] Ah wxl told me she is rarely online [15:38] ok thanks [15:44] popey: aren't there any cloud tasks? [15:45] Not currently [15:47] popey: New tasks on the way? [15:47] When everyone is back at work tomorrow, we should have more arriving. [15:51] popey: please take a look https://codein.withgoogle.com/dashboard/task-instances/4670650331430912/ [15:51] sure [15:51] :popey yay! [15:53] :popey are ther any other tasks you are the mentor of [15:53] *their [16:12] omairqazi: I just saw your message regarding undos in the terminal [16:13] I came across this some time ago :p https://github.com/nvbn/thefuck [16:13] you may like it [16:14] daniellimws: thanks! :) [16:32] hi has anyone tried the "Follow the electron snap creation tutorial" task? [16:37] ah I've got my problem solved [16:42] daniellimws: i did it. what was your problem [16:44] omairqazi: I got this https://pastebin.ubuntu.com/26300407/ [16:44] previously another problem I solved, but not this yet [16:46] wait can you link me to the electron snap [16:48] https://docs.snapcraft.io/build-snaps/electron [16:49] thanks [16:51] any screenshot of your terminal? [16:52] leave the screenshot [16:54] https://pastebin.ubuntu.com/26300407/ [16:54] omairqazi: ^ there's the full log [16:54] ya i see it [16:54] just 5 mins more [16:56] daniellimws: by the time i am running the command npm run dist please see if you have nodejs installed [16:57] daniellimws: curl -sL https://deb.nodesource.com/setup_8.x | sudo -E bash - [16:57] followed by sudo apt-get install -y nodejs [16:59] omairqazi: nope still same error [16:59] ok [16:59] let me see [17:03] I don't think its a nodejs version problem [17:03] could be more of a snapcraft related issue [17:03] similar but different from this https://bugs.launchpad.net/snapcraft/+bug/1656884 [17:03] Launchpad bug 1656884 in Snapcraft "Installation from source (git) error: snapcraft validation file is missing from installation path" [Medium, Fix Released] [17:04] daniellimws: i think i also had this problem try this sudo npm i -g npm [17:04] what does that do? [17:05] it upgrades npm :) [17:05] i fixed it by updating something [17:05] but i can't recall [17:06] by the time try this sudo npm i -g npm [17:08] omairqazi: still doesn't work [17:10] daniellimws: curl -sL https://deb.nodesource.com/setup_9.x | sudo -E bash - followed by sudo apt-get install -y nodejs [17:11] btw did you edit the snapcraft.yaml [17:11] nope there wasnt any [17:12] ok [17:13] daniellimws: lets do a fresh start [17:13] daniellimws: lets do a fresh start [17:14] mkdir a new folder [17:14] cd to that folder [17:14] git clone https://github.com/snapcraft-docs/electron-quick-start [17:26] daniellimws: can you send me the screenshot of your terminal of the commands you ran before npm run dist [17:32] daniellimws" there? [17:33] daniellimws: there? [17:33] I think I found the solution [17:33] did you run npm run install? [17:36] omairqazi: hi, sorry for the delay [17:36] I did npm install [17:36] I re-ran the whole thing on a different macine [17:36] machine [17:36] and it worked [17:36] magic [17:38] daniellimws: cool! [17:39] I told you to do a fresh start [17:39] because now i am having the same problem [17:39] but when i did the whole thing again it worked [17:40] still dont the real solution [17:40] which task to choose now [17:41] actually it could just be my machine having different versions of node or npm [17:41] ya [17:41] omg did someone say node? just do it in a vm. [17:41] hi wxl [17:42] why in a vm [17:42] because then your steps are repeatable [17:42] we were having some problems just because of different versions of node [17:42] wxl: can you help me [17:42] it's *SO EASY* to get your node ecosystem in a different state [17:43] i'm no node expert [17:43] i know i beat my head against the wall about something like this recently and it was maddening [17:43] that's why i said: start in a vm. you'll have a clean slate. [17:43] noted [17:43] thanks for the info [17:44] wxl: i was just snapping a nodejs app and found a problem [17:45] wxl: this task "Run the Lubuntu upgrade tests and report your results" is no longer in use [17:46] what do you mean? [17:46] wxl: See this Notice board Weekly upgrade testing build. This build is valid for a week, starting on 2017/12/22 at 21:00 UTC and finishing on 2017/12/29 at 21:00 UTC. Please use separate results for tests done on different hardware or day. [17:46] wxl: http://iso.qa.ubuntu.com/qatracker/milestones/384/builds/163339/testcases [17:47] feel free to just ignore that, at least for Lubuntu, omairqazi [17:48] wxl: but i cannot submit test results [17:48] ugh [17:48] let me see what i can do. this depends on other people, so it may take a while [17:49] ok [17:49] wxl: hi [17:49] can you suggest me a task wxl [17:49] wxl: could you please verify this answer, its for my task [17:49] wxl: https://askubuntu.com/questions/991043/snap-package-only-runs-when-root [17:49] omairqazi: did you do all the other Lubuntu thingies? [17:49] Nissaar: not a snapper, can't help. i'd consult your mentor. [17:50] i will say this: your formatting is terribly confusing [17:50] wxl oh i just forgot about alternate images [17:50] wxl: thx [17:51] i'd also wonder if it's necessary to cd home [17:52] maybe i'm wrong but again not a snapper [17:52] whose formatting, wxl? [17:52] omairqazi: Nissaar [17:52] oh [17:52] actually only when i used cd /home it worked without sudo [17:53] else im compelled to use sudo before pycharm-community [17:53] huh well that's interesting. i'd explain why that is. reference existing documentation. [17:53] i mean none of that makes sense to me, at least from the perspective of how, say, apt works [17:55] bye guys [17:55] omairqazi: are you starting this task for the first time? [17:55] time to sleep [17:55] (the upgrade one) [17:55] wxl: one question, I see that one of my bugs was marked as "Invalid" without any reason by a user who registered on 31st December 2017. Can I mark it again as "New"? [17:55] konrad11901: sure. i was waiting to see if you'd do that :) [17:56] konrad11901: might be good to put in a note about why you think that's the case [17:56] Ok :) [17:56] wxl yes [17:56] wxl but i did kubuntu tasks earlier [17:56] omairqazi: then go back to the start of the QA tracker and go in again. the build numbers have changed [17:58] wxl: by the way, are there plans for new testing tasks? I'll try to continue testing even without tasks (waiting for first alpha of Lubuntu 18.04 :) ), but making some new tasks would be great! [17:59] at the moment, no, konrad11901. we've got some stuff in the works but it's not there yet. more or less just business as usual until then [17:59] wxl can you link to a testsuite [18:00] i will check it tomorrow (according to IST) [18:00] omairqazi: i'd just go back to iso.qa.ubuntu.com and open up the Upgrade Lubuntu {i386,amd64} links and go from there. just in case it changes again [18:01] ok [18:03] wxl please reply on my task as my laptop's charger is not working [18:04] wxl got it [18:04] i can now submit test results [18:04] yay good job [18:04] wxl anyway thanks! [18:04] talk tomorrow my friend :) [18:04] have a great rest [18:04] wxl thanks [18:05] wxl i dont know what happened to my charger [18:05] wxl: if Simon has assigned this bug to himself, can I change the status to "In Progress"? [18:05] only 5% battery left [18:05] bye [18:05] bye [18:06] Bye! [18:07] konrad11901: if someone was working on it, yep. now there are two teams that have greater degrees of control over the bug status and i don't remember which ones you start out with. you won't be able to do ALL Of them, though. ping me or in #ubuntu-bugs should you ever need help [18:07] oh maybe i can make some bug triage tasks [18:10] wxl: you can :) [18:10] and thanks for explaining :) [18:10] np [18:11] there's wiki pages on the subject if you want to learn more but i'll probably summarize them in the task. hopefully i can get that done today [18:56] popey: new task for you to publish https://codein.withgoogle.com/dashboard/tasks/5680903613317120/preview/ [18:58] wxl: that last line about filing bugs upstream seems almost throw-away. Might require more detail? [18:59] wxl: might also be worth linking to an example "good" bug? [18:59] popey: yeah well i guess so. it's a bonus point thing after all :) [18:59] hah [18:59] popey: i could dig one up but the description makes it clear, i think. [21:49] hi evilnick, degville, pmatulis and davidcalle :D