=== tsimonq2 changed the topic of #lubuntu-devel to: Lubuntu QA/Development | Wiki: https://wiki.ubuntu.com/Lubuntu/QA | Support: #lubuntu | Offtopic Chat: #lubuntu-offtopic | Now Testing: Yakkety Yak Alpha 2 milestone due 28 July | Upcoming: https://wiki.ubuntu.com/Lubuntu/ReleaseSchedules [00:01] * tsimonq2 runs [00:01] wxl: that's four [00:01] :O [00:31] debian bug 614907 [00:31] Debian bug 614907 in tech-ctte "node: name conflicts with node.js interpreter" [Serious,Open] http://bugs.debian.org/614907 [09:16] hi [09:17] tsimonq2, try a debdiff, you can use the ubuntu pastebin if you want [09:17] alright [09:17] gilir: does that mean you would like me to make a debian/changelog entry or leave it? [09:17] tsimonq2, leave it for now [09:18] gilir: alright :) [09:20] gilir: grr, can't do debdiff [09:22] tsimonq2, why ? [09:22] gilir: has to be two different files and when I build lubuntu-meta, one overrides the other [09:23] gilir: I'm really surprised this isn't maintained under a VCS :) [09:23] tsimonq2, it's actually [09:23] gilir: oh? where? [09:23] tsimonq2, you are not looking at the right location [09:24] tsimonq2, https://code.launchpad.net/~lubuntu-dev/ubuntu-seeds/lubuntu.yakkety [09:25] tsimonq2, the last change is what you want to do [09:25] gilir: oh okay [09:25] gilir: thanks [09:25] tsimonq2, after that, you need to wait 10 ~ 15 min [09:26] tsimonq2, after, try to do ./update inside the lubuntu-meta package [09:26] alright [09:27] gilir: then what? [09:27] lubuntu-meta itselft is not under VCS, because it's populated by the seed [09:27] tsimonq2, you will see after the ./update :-) [09:31] I wonder is bug 1591851 relevent now as we are talking about the seed as maybe xfs is not included in the desktop images for lubuntu but it works for ubuntu-mate ? [09:31] bug 1591851 in ubiquity (Ubuntu) "The creation of a BTRFS or XFS partition fails during install of Lubuntu Daily Live image" [Undecided,Confirmed] https://launchpad.net/bugs/1591851 [09:34] gilir: there aren't going to be any mroe respins for Alpha 2, you're probably safe making the Lubuntu Software Center removal now [09:35] lynorian, fixed sometimes ago, you can check the manifest for thsi type of bugs : http://cdimage.ubuntu.com/lubuntu/daily-live/current/yakkety-desktop-i386.manifest [09:35] tsimonq2, ok thanks [11:41] gilir: cute-updates is *just* an updater, not a Software Center [12:38] tsimonq2, yes, I don't know if he worked on a software-center somewhere else [12:39] gilir: alright :) [12:39] gilir: I got your email [14:57] tsimonq2: o/ [15:00] sudodus: hello :) [15:00] sudodus: how are you? [15:00] I'm fine, how are you :-) [15:01] great :) [15:01] tsimonq2: Are you ready to go ahead with mkusb and git? [15:01] sudodus: sure :) [15:02] I suggest that you start ... [15:02] great [15:03] where is your code now? [15:03] I have it in my computer (talking about the code, that is changed since you edited the git branches) [15:05] part of it is also uploaded to ppa:mkusb/unstable (the bash scripts and help files), but maybe not the control files [15:05] alright, let's do this [15:05] My current version is 11.0.1 [15:05] have you cloned https://github.com/tsimonq2/mkusb.git locally? [15:06] I have done nothing with git, nothing at all. [15:06] alright [15:06] sudodus: is it installed? [15:06] (only read your tutorial mail) [15:07] sudodus: do the following in your terminal: git clone https://github.com/tsimonq2/mkusb.git && mkusb [15:07] yes [15:08] the program git is installed [15:08] alright [15:09] sudodus: can you do that above command? [15:09] well. mkusb want to be run with the command 'sudo -H mkusb' [15:10] where was it unpacked? [15:10] sudodus: you talking about the git source? [15:11] OK in my home directory, but I don't want it there. Let me change the location ... [15:11] alright [15:12] now an mkusb directory is located in my 'data' partition in a separate drive [15:12] alright, cd into that [15:13] done [15:13] cool, so this is where you should store and work on your actual source code [15:13] OK [15:14] sudodus: apply all of your changes that you made in 11.0.1 and copy everything over to this directory *except* for the debian dir [15:14] I'll try with rsync ... [15:17] done [15:18] alright, run git status [15:18] it should show that there are changes, right? [15:19] yes [15:19] so now you can do "git add *" to track all the changes [15:20] this is so Git knows to pay attention to them [15:20] I should remove the files q.txt, show-q (because they are 'local' help files) [15:20] alright [15:21] now there are 2 changed files 3 removed files and 2 new files (comparing my mkusb directory and the git) [15:22] sudodus: do those changes look correct? [15:22] "git add * [15:22] did you change two files, remove 3 files, and add 2 new files? [15:23] git status says the same after git add * [15:23] well it's fine [15:23] but did you make those changes from the code you had in the stable PPA to now? [15:24] (if you want to look at the diff, "git diff --cached") [15:24] I corrected the command, and now it worked [15:24] the changes are green and the removals are red, if that tells you something [15:25] sudodus: well like I said, look at the git diff --cached and see if you made all of those changes [15:25] what do you mean how? I edited with geany :-P [15:26] sudodus: is the directory up-to-date with how you want it for 11.0.1 ? [15:26] that's what I want to know [15:28] sudodus: if they are, git commit -am "Released mkusb 11.0.1" [15:28] The differences were entered into less and I could browse them. [15:29] yep [15:29] those are the changes that will be applied by committing if you choose [15:30] let us try that - (there were so many changes, that I cannot easily see if everything is OK) [15:30] According to rsync it should be OK locally, if that is what you mean [15:31] yep [15:31] that's what I meant [15:33] Have you changed anything in these files (excluding those in the debian directory)? [15:33] nope [15:34] sudodus: all I did was remove the debian/ directory [15:35] Are we ready to sync the git with this local directory now? Or was it done already by what we did? [15:35] did you commit? [15:36] no, I have not used any command containing 'commit' [15:36] git commit -am "Released mkusb 11.0.1" [15:37] sudodus: so basically, when you used rsync, you had to tell git to pay attention to them (git add *), then now, you have to put them in the repo [15:37] done [15:37] I used rsync locally - not to the git [15:38] sudodus: could you create an account here and let me know what your username is? [15:39] what do you mean by 'here'? I have an account at Launchpad, which is used to upload to ppa:mkusb. Is that what you mean? [15:40] whops I'm sorry https://github.com/join [15:40] OK, I'll do it ... [15:41] *whoops [15:44] 1 Completed. 2 Choose your plan (what is that)? [15:44] sudodus: free [15:44] or skip if possible [15:44] trying to skip [15:45] sudodus: wait, just keep it at the default bullet point [15:45] sudodus: "Unlimited public repositories for free." [15:46] I am at 'Read the guide' and 'Start a project' now, so I guess successful [15:46] great! :) [15:46] sudodus: what's your username? [15:46] sudodus [15:47] alright [15:47] Should I try to log in now - in that case where? [15:47] hold on now [15:47] sudodus: accept the invite https://github.com/tsimonq2/mkusb/invitations [15:48] email verified [15:48] invite accepted? [15:49] I have accepted the invitation [15:49] great :) [15:49] sudodus: go back to your terminal in that directory and type: git push origin master [15:49] "You now have access to the tsimonq2/mkusb repository." [15:50] \o/ [15:50] sudodus: do what I said above :) [15:50] sudodus: then type in your GitHub username and password [15:51] I seems to work. [15:51] great :) [15:51] there we go! look at https://github.com/tsimonq2/mkusb [15:51] To https://github.com/tsimonq2/mkusb.git [15:51] d06b214..e63a7db master -> master [15:51] sudodus: that's your commit https://github.com/tsimonq2/mkusb/commit/e63a7dbf82175a60784e92d656852240ea7c05a9 [15:52] sudodus: GitHub has a GUI that shows all of your changes in between commits [15:52] it's pretty awesome :D [15:53] I see my three hands avatar too. So I seem to be in :-) [15:54] sudodus: so, do you understand that process? when you want to make a change, edit the source code in that directory, and when you have done something worth noting, git add *, git commit -am "DESCRIBE WHAT YOU JUST DID", git push origin master [15:55] tsimonq2: did you do any testing of the 16.04.1 amd64 desktop iso at all? [15:55] Well, at my age, the brain is not as fast as it used to be ;-) I think I can go back and look at the log (in the hexchat window) and learn the details [15:56] teward: did *I* ? [15:56] teward: why? [15:56] sudodus: great, let's move on to the next step :) [15:56] tsimonq2: "install ubuntu" from the start boot screen on the ISO fails, spins forever at "A start job is running..." with no limit [15:56] have to "Try Lubuntu" first [15:56] then install from the live env. [15:56] hrm [15:57] sudodus: did you see that when testing? ^ [15:58] teward: what image? and did you check the MD5? [15:58] double checking now, but amd64 desktop ISO [15:58] standby (E:SLOWSYSTEMS) [15:58] teward: and a start job on what process? [15:58] I do not always test 'Install', but sometime do it via 'Try ...', and that works. So I'm not sure, but I think it works. [15:59] tsimonq2: you need to listen a little better. [15:59] teward: how so? [15:59] nevermind i fubar'd my thought process [15:59] stupid IRC [15:59] anyways [15:59] it says a start job is running for "Starting Lubuntu Installer" [15:59] never loads the GUI [16:00] :O [16:00] checking MD5 now standby [16:01] sums check out [16:01] running "Try Lubuntu" first seems to work, lets see if that's the case with this reboot [16:01] teward: sudodus is reponsible here, he tested it and marked it as good to go :P [16:01] teward: and I can't always double-check everything [16:01] true [16:02] tsimonq2: i haven't checked in on testing so no clue who does what tests :p [16:02] and it works once booted, but not with the pure "Install Lubuntu" option from boot screen [16:02] *shrugs* [16:02] teward: just checked the tracker and it was sudodus who did amd64 desktop [16:02] teward: file a bug in ubiquity please [16:02] i want to test the original 16.04 iso first [16:03] if it happens there too i'll blame the VM [16:03] if not then i'll blame the image and file a bug [16:03] fair enough :P [16:03] I'm creating a USB boot drive with xenial-desktop-amd64.iso (the released version) [16:03] of Lubuntu [16:03] sudodus: anyways, let me show you how to properly release, not just edit and commit, if you are ready? [16:04] Yes [16:04] sudodus: git tag 11.0.1 [16:04] sudodus: that creates the appropriate tag [16:05] sudodus: then: git push --tags origin master [16:05] sudodus: as long as you have committed, that will set up a release [16:06] let me know when that's done [16:06] 'Install Lubuntu' works for me :-) [16:07] sudodus: bare metal or VM? [16:07] bare metal, my Toshiba laptop with Intel i5 and the built in Intel graphics [16:08] Total 0 (delta 0), reused 0 (delta 0) [16:08] To https://github.com/tsimonq2/mkusb.git [16:08] sudodus: perfect! :) [16:09] * [new tag] 11.0.1 -> 11.0.1 [16:09] sudodus: you can also now write release notes here: https://github.com/tsimonq2/mkusb/releases/new?tag=11.0.1 [16:09] So this was a 'dummy' job just repeating what was done, or was it doing something new? [16:10] sudodus: I got there by selecting Releases -> 11.0.1 -> Edit tag [16:10] sudodus: no this is for real [16:10] sudodus: so write up the release, what did you do? :D [16:10] sudodus: (basically describe what you told me in a recent email) [16:10] I see. What kind of release notes. Something like here: [16:11] https://help.ubuntu.com/community/mkusb/v11 [16:11] sudodus: perfect! in fact, I would just put a link to those [16:13] I pressed the button :-P [16:14] sudodus: so after you did that step (creating the tag, pushing the tag, and setting the release notes) let me know so I can update the Debian package [16:14] sudodus: but now let me show you how to update the PPA package [16:14] Can you inspect it and verify, that I got it right? [16:14] ok, hold on [16:15] sudodus: notice this here :) https://github.com/tsimonq2/mkusb/releases [16:15] sudodus: it's big and it has a link to a zip and a tar :D [16:15] sudodus: iirc you can also set like beta releases and such if you want them [16:16] sudodus: but otherwise, looks good :) [16:16] Ok [16:16] ready to move on now? [16:17] hrm, interesting, it worked fine now... [16:17] took four boots to 'work fine' :/ [16:17] *shrugs* [16:17] I think there is more to do now - to make it really separated, so that the compiled code is separate and not included in the package for the version, that should be proposed for an official repository. [16:19] sudodus: well if you just let me know what parts are nonfree, I'll remove those in the debian branch [16:19] sudodus: but for right now, you should update your PPA :) [16:20] sudodus: git remote add launchpad git+ssh://git.launchpad.net/mkusb <-- that's a one-time command [16:21] sudodus: then: git checkout -b ppa (remove the -b in the future) [16:21] sudodus: after that: git pull launchpad ppa [16:21] sudodus: then do the usual changes that update the Debian package, dch -i etc. [16:22] let me know when that's done [16:22] usb-pack-efi with usb-pack_sdir/usb-pack_efi.tar.gz, and it should be removed from the control file. There is also debian/usb-pack-efi.install [16:23] as described in the attached file 'todo.txt' in a mail to you [16:23] ahh yes I remember, sorry [16:24] I can update the ppa now ... [16:25] The authenticity of host 'git.launchpad.net (162.213.33.96)' can't be established. [16:26] RSA key fingerprint is SHA256:UNOzlP66WpDuEo34Wgs8mewypV0UzqHLsIFoqwe8dYo. [16:26] is this the usual sftp checkpoint? [16:26] yes I think it's fine [16:28] There is a problem. I am not logged in as sudodus. Is there a way to remote log in a 'sudodus@something' instead of just 'something'? [16:29] and default to my current user id? [16:29] git remote remove launchpad && git remote add launchpad git+ssh://sudodus@git.launchpad.net/mkusb [16:31] That command was accepted without any feedback. [16:31] it shouldn't have any feedback, it's fine [16:31] sudodus: now try again [16:31] try what [16:31] (try the step you were on before again) [16:32] sudodus: where were you at? [16:32] do you mean 'git remote remove launchpad && git remote add launchpad git+ssh://sudodus@git.launchpad.net/mkusb' [16:32] or some step further back? [16:32] further [16:33] please be more specific! [16:33] where were you before 'git remote remove launchpad && git remote add launchpad git+ssh://sudodus@git.launchpad.net/mkusb' ? [16:34] in the bash history I can see these commands (wait for a few lines) [16:35] git push origin master [16:35] git tag 11.0.1 [16:35] git push --tags origin master [16:35] git remote add launchpad git+ssh://git.launchpad.net/mkusb # which should be replaced by [16:36] git remote add launchpad git+ssh://sudodus@git.launchpad.net/mkusb [16:37] git checkout -b ppa # I seem to have run this one but before the correct command with sudodus explicit [16:37] git pull launchpad ppa # I seem to have run this one but before the correct command with sudodus explicit [16:37] Should I repeat these two last commands? [16:38] no, it's fine [16:38] sudodus: try: git branch [16:38] it shows that you are in the PPA branch, correct? [16:38] master [16:39] * ppa [16:39] giid [16:39] *good [16:39] sudodus: now do dch -i and whatever else to update the PPA to 11.0.1 [16:39] (in the debian/ directory) [16:40] like splitting the two packages, etc. [16:40] locally I guess [16:40] yep [16:40] sudodus: all of this is local unless you git pull/push [16:42] You mean in my old location, where I have the debian directory, or should I create a new debian directory? [16:43] I guess it is wise to create a new directory and not mess with the old one [16:43] no no no [16:43] keep the one you have [16:44] sudodus: restore it from the other directory, restore your edits [16:44] The one that belongs to the directory, where I can upload directly to the ppa? [16:44] yep [16:44] sudodus: this is sorta uploading to the PPA [16:45] sudodus: except the stable one instead of unstable [16:45] OK, but I don't want to destroy what is working. I'll make a copy. [16:47] sudodus: well all you have to do is copy the debian/ directory from the unstable PPA to this directory, it will be fine, just edit accordingly [16:47] or maybe if you want to get the debian tar from the stable PPA and update that, that would be good too [16:48] sudodus: just infd a way to update your PPA with this release [16:48] *find [16:49] I am ready for dch now (have not used the -i option before), is it OK with my previous commands? [16:49] yeah totally [16:52] dch done. [16:53] What next? Do you mean I should edit the control file now, or just use the same files again, now only prepare for uploading with [16:53] debuild -S [16:54] cd .. [16:54] sudodus: use the files you got from GitHub, prepare it as you would a normal release with the files you have [16:54] dput ppa:mkusb/unstable mkusb_1... [16:55] What files from github? [16:56] the files you already have merged [16:56] it's fine [16:57] You wanted me to have a separate debian directory. Should I point the debian files across the filesystem to the current files in my new mkusb directory? [16:58] I could also create links (maybe even hard links) to avoid pointing acreoss the filesystem [16:58] across [16:59] I'm working in Debian now [17:00] I'll handle Debian [17:00] (until I have a stable workflow) [17:00] In that case we can say that I'm ready with the 'source files'. Only the control file etc in the debian directory may need editing. [17:00] I'm waiting for you ... [17:01] so wait [17:01] let's get on the same page here [17:01] you have the PPA branch locally and merged with 11.0.1 [17:01] you just merged the code [17:01] now you need to update the debian files [17:01] you just have to update the debian files to release, like you would normally do [17:02] imagine you just edited the code [17:03] Then I will normally only edit only one file in the debian directory, the changelog file (via dch). The other files in debian remain the same for long periods. [17:03] alright [17:04] wxl: are we clear to release? [17:05] tsimonq2: ummmm i already say your release annnouncement [17:05] s/say/saw/ [17:05] wxl: that was global dude [17:05] :D [17:05] yeah but if we're good globally, we're good [17:06] wxl: gtreat, you jsut said to check with you :) [17:06] *great [17:06] *just [17:06] typically before global announcement, but all good [17:06] sudodus: give me a minute, I have to release [17:06] tsimonq2: release what software? [17:06] sudodus: Yakkety Yak Alpha 2 [17:06] sudodus: 16.04.2 [17:06] argh [17:06] * tsimonq2 kicks wxl [17:06] s/04/10/ [17:06] :P [17:09] tsimonq2: I thought yakkety alpha2 is already released ... [17:09] sudodus: globally, but he waited on the lubuntu announcement [17:09] I see [17:11] sudodus: when you are done with the changelog, don't do anything with Git, just get me the debian/changelog file in a pastebin. I made a big mistake when giving you instructions that I'm gonna fix myself. [17:11] sudodus: and please, feel free to publish to the PPA :D [17:21] I sent changelog.gz via email [17:24] Do you mean to continue publishing in the future like I did before, but now via git? Or do you mean now? In that case with what command? I usually upload to the unstable ppa, and after some testing copy it to the stable one 'ppa:mkusb/ppa' [17:24] sudodus: I'll tell you later, I'm really sorry, I have to go [17:25] OK, please suggest a new time via mail. [17:30] sudodus: alright will do, o/ [17:31] o/ [21:09] tsimonq2: let's talk about getting https on the website