[02:27] <rww> Hello! Can someone mark https://bugs.launchpad.net/ubuntu/+source/software-center/+bug/606452 as Triaged and Medium or High (I'm not sure which) for me?
[02:28] <ubot2> Launchpad bug 606452 in software-center (Ubuntu) "software-center crash on load, UnboundLocalError in _get_channels (affects: 3) (dups: 1) (heat: 20)" [Undecided,New]
[03:00] <nigelb> rww: best way is to find the bug that got it into proposed in the first place
[03:00]  * nigelb goes to find it
[03:01] <rww> nigelb: changelog says "* softwarecenter/view/viewswitcher.py:  - remove specal cases for partner now that soyuz LP: #552560 is fixed (LP: #604693)
[03:01] <rww> which sounds supiciously relevant
[03:02] <nigelb> aha
[03:02] <nigelb> bug 604693
[03:02] <ubot2> Launchpad bug 604693 in software-center (Ubuntu Lucid) (and 1 other project) "Partner repository now appears twice in navigation pane (affects: 1) (heat: 10)" [Undecided,Fix committed] https://launchpad.net/bugs/604693
[03:03] <nigelb> rww: go say the bug there and also add "verification-failed" tag to it
[03:03] <nigelb> the qa team tracks those bugs specifically, quicker action if you comment there
[03:04] <rww> nigelb: alright. Should I leave the verification-needed tag alone, or remove it?
[03:05] <nigelb> I think you can remove it.  Its supposed to be changed I think.
[03:05] <nigelb> !sru
[03:05] <ubot2> Stable Release Update information is at http://wiki.ubuntu.com/StableReleaseUpdates
[03:05] <nigelb> aha, there's the page :)
[03:06] <nigelb> rww: did that fix hit -updates?
[03:06] <rww> nigelb: nope, it's still in proposed
[03:06] <nigelb> thankfully
[03:07] <rww> looks like I need to hit Nominate for release on 606452 as well, according to that page
[03:07] <nigelb> rww: the old one?
[03:08] <nigelb> ah, yes
[03:08] <nigelb> I need to set importance to crtical
[03:12] <nigelb> oh wait, I tink the importance is only when it hits -updates :)
[03:18] <rww> I have no idea, bug importance confuses me :). It should be set Triaged though, right?
[03:18] <kermiac> nigelb: AFAIK as long as you change the tag to "verification-failed"  it shouldn't hit -lucid updates
[03:18] <nigelb> kermiac: yeah :)
[03:19] <nigelb> rww: the one you filed about failure?
[03:19] <rww> I didn't file it, but yeah
[03:19] <nigelb> set to confirmed and I'll set it as triaged
[03:21] <rww> done
[03:23] <nigelb> Done :)
[03:26] <stanley_robertso> hi all
[03:29] <rww> nigelb: awesome, thanks for your help :)
[03:30] <nigelb> rww: no problem.  thanks for helping out testing :)
[07:31] <nUboon2Age> duanedesign: ping
[07:31] <duanedesign> hello nUboon2Age
[07:33] <nUboon2Age> hey duanedesign i see you are connected to the 100 papercuts project.  I'm wondering about user experience bugs that are larger than 100 papercuts.  How are they handled?
[07:36] <nUboon2Age> My understanding is that Mark Shuttleworth has set the vision for the user experience to be right up there with the Mac.  So when there are user experience bugs, how are they written up?  Are there examples I could look at?
[07:36] <duanedesign> nUboon2Age: I got drafted to do that forum post because I am forum staff. You might want to ask vish or someone in #ayatana
[07:37] <nUboon2Age> duanedesign: what is ayatana?
[07:38] <duanedesign> nUboon2Age: https://wiki.ubuntu.com/Ayatana
[07:39] <nUboon2Age> hmmm... it looks like that might be just the thing i'm looking for... duanedesign, thanks.
[07:39] <duanedesign> nUboon2Age: here are some bugs associated with the project https://bugs.launchpad.net/ayatana
[07:40] <duanedesign> nUboon2Age: np :)
[07:41] <nUboon2Age> duanedesign: if they aren't quite the right group, they may know who would be... thanks. :)
[10:09] <yofel> morning
[10:53] <stanley_robertso> hi all
[13:49] <stanley_robertso> hi all
[17:28] <stanley_robertso> hi cyphermox
[17:48] <cyphermox> hi stanley_robertso
[18:56] <vish> sense: hey , what do we do with https://launchpad.net/~steven-fowlerjr , he has his info in the lp page which seems fine however ,there is no irc nick..
[18:57] <vish> do we reject or.. just approve for the mentoring..?
[18:57] <sense> vish: Ask him to fill in his IRC nick and let him stand on pending for a little longer.
[18:58] <vish> sense: hmm , i have used up all my "contact this user" privileges for today.. and he has no public id.. can you contact him?
[18:58] <sense> I'll contact him.
[18:58] <vish> neat!
[18:59] <stanley_robertso> hi vish
[18:59] <vish> stanley_robertso:  o/
[18:59] <stanley_robertso> howz it going virtuald
[19:00] <stanley_robertso> sorry.. i was referring vish .. not virtuald
[19:00] <sense> contacted!
[19:16] <nigelb> vish: maybe we should set, show email publically for mentorship candidates
[19:16] <nigelb> it gets a bit difficult if the admins are not able to get in touch
[19:20] <stlsaint> vish: ping
[19:21] <vish> stlsaint: hey , just caught me in time ;) i tried to catch you here , but couldnt find you
[19:21] <stlsaint> vish: i thought my mentor situation was hashed out??
[19:22] <vish> stlsaint: hmm , well we didnt have mentors and now we have them , but we need to know what time you will be available to assign you a mentor..
[19:23] <stlsaint> vish: i was under the impression that ddecator was going to be my mentor??
[19:23] <stlsaint> vish: after the one he has now assimilates to membership
[19:23] <vish> stlsaint: if he wants to, then there is no prob :)
[19:24] <vish> stlsaint: but still if you had a time listed there , we could have assigned another mentor right now..
[19:24]  * vish just assigned 6 students to a mentors..
[19:24] <vish> not the same mentor of course ;p
[19:25] <stlsaint> vish: tbh i know jack squat about UTC!
[19:26] <vish> stlsaint: hmm , time converter ? http://www.thetimezoneconverter.com/
[19:26]  * holstein updated availalbility on wiki :)
[19:26] <holstein> mikeh789 = holstein
[19:26] <yofel> UTC: open a terminal and type 'date -u' ?
[19:26] <nigelb> yofel: +1
[19:29] <vish> yofel: that gives present time and then we have to calculate a whole more.. converters allow us to be more lazy \o/
[19:29] <yofel> you just need to know the offset to your local time..
[19:30] <holstein> vish: i got my approval email just now... thanks
[19:30] <vish> holstein: np..
[19:35] <vish> yofel: well , offsetting the local time can confuse the best of us > https://wiki.ubuntu.com/BugSquad/Mentors?action=info
[19:35] <vish> nigelb: ;p
[19:36] <nigelb> vish: that was dst turning off/on thing
[19:36] <yofel> :D
[19:37] <stlsaint> vish: i am fine with waiting on ddecator but i will still update my wiki
[19:37] <vish> stlsaint: sure.. neat!
[19:38] <vish> oh boy!  ddecator sure has a lot of fans ;)
[19:41] <nigelb> vish: LOL, wats up?
[19:42] <yofel> vish: open a fanclub for him on LP :P
[19:44] <vish>  yeah , probably ddecator-poachers !
[19:44] <stlsaint> vish: not so much a fan of him but he knows that i had previous issues with bug squad so im holding him responsible for this go round ;)
[19:45] <vish> stlsaint: :D
[19:49] <penguin42> is the way to mark something as a papercut to do a 'Also affects project' ?
[19:51] <vish> penguin42: yup
[19:53] <penguin42> Ta
[19:54] <vish> stlsaint: but you gotta have applied for the mentoring team if you want ddecator too.. if you are not in the queue , then someone else might grab him :D
[19:58] <stlsaint> vish: i just applied for the wrong bugsquad...i just did the general bugsquad team on lp
[19:58] <stlsaint> vish: i have since joined the mentorship one but will that effect anything by joining the regular bugsquad one?
[19:59] <vish> stlsaint: nope , wont affect
[21:01] <LinuxGuy2009> Is there a PPA for the system wide EQ on Lucid? Is that project still ongoing?
[21:27] <penguin42> anyone know where I report minor issues on the launchpad.net website - just something that could improve on the hekp
[21:28] <yofel> usually file a bug at https://bugs.launchpad.net/launchpad , you can ask in #launchpad too first
[21:30]  * penguin42 has managed to cook his 1st ppa and I thought I should post things that would have avoided the things I found confusing
[21:30] <yofel> penguin42: wait, what's the problem?
[21:32] <yofel> penguin42: if it's about ppas better directly file it against soyuz https://bugs.edge.launchpad.net/soyuz/
[21:32] <penguin42> yofel: OK, 1st one is that on https://help.launchpad.net/Packaging/PPA  it implies that your key is generated as soon as you activate your ppa - and I was waiting for it, thinking I would actually need to sign stuff with it; but it should say it's only generated you upload your 1st ppa
[21:33] <yofel> ah right (I was following in -packaging more or less)
[21:33] <penguin42> which shadeslayer was kind enough to set me right upon
[21:36] <yofel> ah right, actually it only shows it if you have packages in the ppa IIRC, if you delete all packages it'll be hidden again
[21:36] <yofel> not sure where to file a bug about the help page though..
[21:36] <yofel> maybe just file it against 'launchpad' after all
[21:36] <penguin42> I'll file it on bugs.launchpad, someone can always bounce it elsewhere
[21:37] <yofel> wgrant: ^
[22:33] <plugwash> while updating a lucid chroot I got "start: Unable to connect to Upstart: Failed to connect to socket /com/ubuntu/upstart: Connection refused". I have a policy-rc,d in place which is supposed to stop anything getting started/stopped in the chroot
[22:33] <plugwash> sorry it's a maverick chroot not a lucid one
[22:34] <plugwash> is this a bug or is there something else that needs to be done these days to prevent package updates in a chroot from attempting to start/stop stuff?
[22:35] <kklimonda> plugwash: may be bug 430224
[22:35] <ubot2> Launchpad bug 430224 in upstart (Ubuntu Karmic) (and 3 other projects) "init: support chroots (affects: 13) (dups: 1) (heat: 213)" [Medium,Won't fix] https://launchpad.net/bugs/430224
[23:00] <^arky^> hi vish
[23:08] <^arky^> vish,  Is there any bug relating to subtitle fonts in ubuntu,


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