[01:01] <lynorian> I don't know if it was ever set up
 Simon closed the issue to do so
[01:37] -lugito:#lubuntu-devel- [T122: New Manual URL Design] wxl (Walter Lapchynski) commented on the task: https://phab.lubuntu.me/T122#2882
[01:40] -lugito:#lubuntu-devel- [T122: New Manual URL Design] teward (Thomas Ward) commented on the task: https://phab.lubuntu.me/T122#2883
[01:41] <teward> ... i need to learn how to silence that notice >.>
[01:41] <teward> wxl wxl23 give me the valid links
[01:41] <teward> i'll set up the redirects accordingly
[01:41] <teward> don't give me the info, can't act on it :P
 Uh I'm not sure what you're asking
[01:45] <teward> wxl23: all i see on the ticket and in here is "this link 404s"
[01:45] <teward> i need to know what you want it to POINT to to become a valid link :P
[01:45] <teward> if it's just supposed to work as is
[01:45] <teward> as in the files exist already
[01:45] <teward> then i did nothing to break it :P
[01:46] -lugito:#lubuntu-devel- [rMANUALdfc3a95ceaa9: Fix Wording] lynorian (Lyn Perrine) committed: https://phab.lubuntu.me/rMANUALdfc3a95ceaa9
 @wxl [<wxl> @lynorian @tsimonq2 it seems manual.l.m/lts is a 404. did we miss somethin …], We don't have an LTS manual published yet
 LXDE is retro at this point and it's stupid to publish LTS before it's published to stable
[02:14] <lynorian> agreed 20.04 stuff is in master https://manual.lubuntu.me/master/
[02:22] <kc2bez> @HmollerCl https://phab.lubuntu.me/P55 Before I upload here is the lintian run on update notifier.
[02:23] <kc2bez> Standards-version should probably get a bump and it looks like the description needs a bit of a tweak.
[03:31] -lugito:#lubuntu-devel- [rMANUAL31035d159e1e: Fix wording] lynorian (Lyn Perrine) committed: https://phab.lubuntu.me/rMANUAL31035d159e1e
[03:33] -lugito:#lubuntu-devel- [rMANUAL2cd12fe15e3a: Add other way to quit screengrab] lynorian (Lyn Perrine) committed: https://phab.lubuntu.me/rMANUAL2cd12fe15e3a
[03:43] -lugito:#lubuntu-devel- [rMANUAL4bfa2f2b8cd2: Add icon for ScreenGrab] lynorian (Lyn Perrine) committed: https://phab.lubuntu.me/rMANUAL4bfa2f2b8cd2
[03:52] -lugito:#lubuntu-devel- [rMANUAL372eda44270d: Add text to correct paragraph] lynorian (Lyn Perrine) committed: https://phab.lubuntu.me/rMANUAL372eda44270d
[04:13] -lugito:#lubuntu-devel- [rMANUALd6147f7d4053: Update qpdfview version for 20.04] lynorian (Lyn Perrine) committed: https://phab.lubuntu.me/rMANUALd6147f7d4053
[05:42] <guiverc> testing my backup strategy; I just nuked a 8tb array with a `dd` (I didn't read the hostname); can I use bazaar to redownload my push/commits? (testcases still in review stage)?  low-priority since O
[05:42] <guiverc> I'll have to rebuild box first
 One thing I noticed yesterday and confirmed today is: … If there is a swap partition already present on disk, the live usb uses it. But installer doesn't provide an option of erasing the whole disk unless you manually disable the swap partition. Only gives options of manual partitioning or replacing one. … Ideally it should al
 ^ @guiverc can you confirm this?
 Who else uses cala apart from us? I can check with their live usb too. If they have this issue or not.
 @The_LoudSpeaker [One thing I noticed yesterday and confirmed today is: … If there is a swap partit …], This could be important for people coming from lubuntu 18.04 and doing a fresh install of 20.04
[06:52] <guiverc> The_LoudSpeaker, that's a known issue (and I've hit my head on it many many times), but most my installs are over prior qa-installs; so no swap (swap file)
 Ack. Thanks!
[07:35] <guiverc> The_LoudSpeaker, also I'll be slow on testing; I wrongly nuked my primary server drive array, i ran `dd` without realizing I wasn't on localhost (`ssh`); verified my /dev in a different term to avoid scrolling :( -- i'm distracted currently trying to fix my mess
 @guiverc [<guiverc> The_LoudSpeaker, also I'll be slow on testing; I wrongly nuked my prim …], Ouch! 😮
[07:45]  * guiverc  should have learned though; idiot me wiped a hdd only a couple of months ago; so I got my warning on somethign that didn't matter
 @guiverc [<guiverc> The_LoudSpeaker, also I'll be slow on testing; I wrongly nuked my prim …], Ow.
 No worries. I got my test machine l back. Already testing focal on it.
 @The_LoudSpeaker [One thing I noticed yesterday and confirmed today is: … If there is a swap partit …], https://github.com/calamares/calamares/issues/860
 https://github.com/calamares/calamares/issues/1258#issuecomment-570931429 … Wow! wxl: how did you I was telling that exact thing?
 Are you spying on me? 🧐
 @kc2bez [https://github.com/calamares/calamares/issues/860], Nothing after 2018 on this. :/
 Nope, it works fine if you turn off all swap before you start the installation, you just have to remember to do that.
 @kc2bez [Nope, it works fine if you turn off all swap before you start the installation, …], Ideally it should provide that option and unmount swaps automatically.
 If that option is selected.
 I agree.
 There is a note in the manual page for it too https://manual.lubuntu.me/stable/1/1.3/installation.html
[11:08] -lugito:#lubuntu-devel- [T139: Ensure applications in Snap packages show up in the lxqt-panel menu] gsilvapt (Gustavo Silva) commented on the task: https://phab.lubuntu.me/T139#2884
 @wxl are you sure the metadata change is enough to fix this issue? I didn't have time to test but if that's the case then I would like to close the bug report I opened on LP
[14:09] -lugito:#lubuntu-devel- [T139: Ensure applications in Snap packages show up in the lxqt-panel menu] gsilvapt (Gustavo Silva) commented on the task: https://phab.lubuntu.me/T139#2886
[14:56] -lugito:#lubuntu-devel- [T139: Ensure applications in Snap packages show up in the lxqt-panel menu] The_LoudSpeaker (Raman Sarda) commented on the task: https://phab.lubuntu.me/T139#2887
 @lugito [<lugito>  3[  13T139: Ensure applications in Snap packages show up in the lxqt-p …], @gsilvapt
 Thanks, @The_LoudSpeaker. I'll try this when I have some time
 @guiverc [<guiverc> testing my backup strategy; I just nuked a 8tb array with a `dd` (I di …], Yep grab it from your account
 @gsilvapt [@wxl are you sure the metadata change is enough to fix this issue? I didn't have …], Yes tested so that PR is what we need.  Let me know if you need help testing
 @The_LoudSpeaker [Ideally it should provide that option and unmount swaps automatically.], Maybe we should make a custom job that warns the user
 @wxl: you around?
[19:29] <wxl> yep
 soooo. I downloaded the conflicted package of lxqt-globalkeys which was stuch in MoM
 fixed the errors.
 built using debuild -S
 and then dput ubuntu ../lxqt-globalkeys_0.13.1-1ubuntu1_source.changes
 did I do it correctly?
 or messed up?
 how do I check?
 I don't see anything new here: https://launchpad.net/ubuntu/+source/lxqt-globalkeys/
 anyone?
[19:35] <kc2bez> I would think you would get an email.
[19:35] <kc2bez> It should have rejected it.
[19:35] <kc2bez> current version is 0.14.1+git20190923-0ubuntu1
[19:36] <kc2bez> You tried to upload 0.13.1 something which is lower in versioning.
 oh yess
[19:37] <kc2bez> You should really push to phab first.
 can't find lxqt-globalkeys_0.14.3.orig.tar.xz in upload
 @kc2bez [<kc2bez> You should really push to phab first.], even for fixing packages that are stuck in MoM?
[19:44] <kc2bez> I would think yes, it needs to end up in there somehow.
 any idea how?
 @wxl:
[20:00] <wxl> well it needs to go to git
[20:01] <wxl> you can do that through arc but if you're sure of yourself, just git commit it
 the source downloaded from MoM doesn't have .git in it
[20:02] <wxl> well then don't get the source from MoM XD
 well. I have to fix what MoM can't soo..
 -\o/-
[20:03] <wxl> in other words, you do the whole merge yourself
 more briefly please?
 I am running `debuild -us -uc -tc` but it still says original source not included.
[20:04] <wxl> then you don't have the original source, obviously :)
 I do have the 0.14.3.orig.tar in ../
[20:06] <wxl> of course we could get around this whole git step if somehow we had something monitoring archive uploads and adding them to git. is that something we could do, @tsimonq2?
 I think that day I did have correctly compiled source (with original one) but I don't remember how I did it.
[20:16] <wxl> do you have it untarred?
[20:17] <wxl> you need to do that before debuilding
 same error
 also, why would I untar it? I am not even working on the original source na? I am in 0.14.3-1ubuntu1
 not in 0.14.3
[20:20] <wxl> i mean it is de*BUILD*
[20:21] <wxl> i don't think building the source package requires it, per se, but it might
 I am running debuild inside this: https://merges.ubuntu.com/l/lxqt-globalkeys/lxqt-globalkeys_0.14.3-1ubuntu1.src.tar.gz
 after fixing the conflicts
[20:22] <wxl> i've never bothered with mom personally so i'm not sure what to tell you
 @tsimonq2
 you know something?
[20:29] <wxl> i think you have the wrong source
[20:29] <wxl> i think that's the problem
[20:29] <wxl> there's no .tar https://merges.ubuntu.com/l/lxqt-globalkeys/
 https://merges.ubuntu.com/l/lxqt-globalkeys/lxqt-globalkeys_0.14.3.orig.tar.xz
 okay wxl: what would be the best way to get new upstream release of globalkeys?
 I am done trying with MoM
 The latest tar is on MoM report folder
 yeah. I downloaded that. fixed the errors. now how do I upload it correctly?
 @RikMills
 build the source
 ```This package has a Debian revision number but there does not seem to be … ````an appropriate original tar file or .orig directory in the parent directory; … (expected one of lxqt-globalkeys_0.14.3.orig.tar.gz, lxqt-globalkeys_0.14.3.orig.tar.bz2, … lxqt-globalkeys_0.14.3.orig.tar.lzma,  lxqt-globalkeys_0.14.3.orig.tar.xz or
 pressing y fails
 In the lxqt-globalkeys-0.14.3-1ubuntu1 folder … ../merge-buildpackage -d
 umm what?
 you did grab-merge, yes?
 nope
 I just downloaded  lxqt-globalkeys_0.14.3-1ubuntu1.src.tar.gz from mom, fixed errors, then downloaded https://merges.ubuntu.com/l/lxqt-globalkeys/lxqt-globalkeys_0.14.3.orig.tar.xz into ../ and ran debuild -S
 @The_LoudSpeaker [I just downloaded  lxqt-globalkeys_0.14.3-1ubuntu1.src.tar.gz from mom, fixed er …], this build without using original source. I get that mail of rejected.
[20:48] -lugito:#lubuntu-devel- [rMANUALdedec11558e9: IMprove wording] lynorian (Lyn Perrine) committed: https://phab.lubuntu.me/rMANUALdedec11558e9
[20:48] <wxl> https://wiki.ubuntu.com/UbuntuDevelopment/Merging
 if you fetch the merge with grab-merge you get scripts to build the source when you are done!
[20:48] <wxl> ah yes this is documented
[20:48] <wxl> Generate a new merged source package using the merge-buildpackage script. 
 where have you been all this time @RikMills !! me and wxl here need lessons from you.
 You will end up with something like this: https://launchpad.net/~rikmills/+archive/ubuntu/focal/+sourcepub/10912317/+listing-archive-extra
 (I couldn't be bothered to fill in the changelog....)
[20:49] <wxl> @RikMills given how kubuntu normally does things, when do you find yourself using mom at all???
 @wxl [<wxl> @RikMills given how kubuntu normally does things, when do you find yoursel …], I don't for the Kubuntu stuff much, but use it sometimes for other MOTU type things
 @wxl [<wxl> of course we could get around this whole git step if somehow we had someth …], It's a huge project
[20:53] <wxl> @tsimonq2 even an alert system would be nice, but stilll here's raman fixing a merge with mom and he'll be stuck trying to figure out how to get the changes in git
[21:02] <wxl> @The_LoudSpeaker barring some improvement, i guess once you get it all figured out you should make a document on how to deal with this kind of like we have https://phab.lubuntu.me/w/packaging/packaging_for_new_upstream_releases/
[21:02] <wxl> "automatic merges for lubuntu"
 sure.
 https://phab.lubuntu.me/P56
 https://phab.lubuntu.me/P57
 ^^ @RikMills
[21:16] <wxl> make them pubhlic
 should I do a `dpkg-source --commit`
 @wxl [<wxl> make them pubhlic], one sec.
 @The_LoudSpeaker [should I do a dpkg-source --commit], No
 @RikMills [No], then?
 @wxl [<wxl> make them pubhlic], done
 @The_LoudSpeaker [then?], Is that file in your debian packaging or the upstream source tar?
 upstream probably
 how do I check?
 Look in the upstream tarball
 However, it won't be in there. If it was, you wouldn't be getting the error
 It is not in 0.14.3.orig.tar
 remove it then try again then. the error is saying it should not be there
 successful\
 And fix the changelog!
[21:25] <wxl> https://github.com/lxqt/lxqt-globalkeys/blob/master/.translation-update
[21:25] <wxl> it's there
[21:25] <wxl> in other news, we have a new packageg coming it seems https://github.com/lxqt/lxqt-organizer
 @wxl [<wxl> it's there], ow. I deleted
 @The_LoudSpeaker [should I do a dpkg-source --commit], I should have done this
 now I have to do again everything?
 or can I add the file later from phab? I have the patch with info
 @The_LoudSpeaker [I should have done this], No
 oh yesh
 correct no
[21:29] <wxl> that file should have been there since 0.14.0
 coz it is there in on github master but not in the 0.14.3 source that we have. one sec I need to confirm something
 @wxl [<wxl> that file should have been there since 0.14.0], wait one min
[21:30] <wxl> https://github.com/lxqt/lxqt-globalkeys/tree/0.14.0
[21:30] <wxl> and it's not here https://github.com/lxqt/lxqt-globalkeys/tree/0.13.0
 I don't see it in https://github.com/lxqt/lxqt-globalkeys/releases/download/0.14.3/lxqt-globalkeys-0.14.3.tar.xz
[21:31] <wxl> THAT is weird
 @RikMills [And fix the changelog!], what exactly in changelog? release name? done.
 @wxl [<wxl> THAT is weird], I feel like yelling "Abbey Saale" to upstream but I am too tired at the moment
[21:32] <wxl> it's certainly not there
 @wxl [<wxl> THAT is weird], Not really. Not all repo .something files go in release tars
 @The_LoudSpeaker [what exactly in changelog? release name? done.], @RikMills
 @The_LoudSpeaker [@RikMills], What is your current changelog?
 one sec
 https://paste.ubuntu.com/p/ZxhjQjKnMs/
 ```lxqt-globalkeys (0.14.3-1ubuntu1) focal; urgency=low …   * Merge from Debian unstable. Remaining changes: …     - Change 1 …     - Change 2 …     - Change 3 …  -- Raman Sarda <theloudspeaker@lubuntu.me>  Thu, 17 Oct 2019 03:44:41 +0000```
 should be like that ^^^
 where the changes are those between the debian version and the merged version that you are keeping
 okay.
 Will do.
 while you are comparing the differences, you probably want to see if any of the remaining changes can be safely dropped
 `[ Ubuntu Merge-o-Matic ] …   * Merge from Debian unstable. Remaining changes: …    - Modified lxqt-globalkeys.install to include ubuntu specific changes. …    - new dependencies in control file. …    - Translations from debian.`
 ^ this okay?
 @RikMills [while you are comparing the differences, you probably want to see if any of the …], I do have an extra patch file by wxl which is not required now. I will drop that. Tho I think I would like to do that from phab side.
 @The_LoudSpeaker [I do have an extra patch file by wxl which is not required now. I will drop that …], it is not urgent as the patch is not in series file so can wait.
 @The_LoudSpeaker [^ this okay?], You might want to explain in a bit more detail. The point is that someone else coming along later and having to merge again, has a good idea of what you kept and why.
[21:42] <wxl> we have a patch not in series???? wth. in any case you should fix that presently.
 @The_LoudSpeaker [[ Ubuntu Merge-o-Matic ] …   * Merge from Debian unstable. Remaining changes: …    - …], oh yeah I need to remove mom's name.
 yup
 @wxl [<wxl> we have a patch not in series???? wth. in any case you should fix that pre …], your complete-config-file.patch
 @RikMills [You might want to explain in a bit more detail. The point is that someone else c …], okay.
[21:43] <wxl> https://phab.lubuntu.me/source/lxqt-globalkeys/browse/ubuntu%252Ffocal/debian/patches/series
 wtf! I willremove it
 I made the changes, changed the author in debian changelog. ran debuild -S it still doesn't include original source. `dpkg-buildpackage: info: binary and diff upload (original source NOT included)`
 @RikMills
 oh wait.
 what all do I suppl y with merge-buildpackage script? only key right?
 perhaps. I don't supply anything as my gpg agent is running
 yay! upload successful
[22:03] <wxl> and now you need to figure out how to get that patch into git and tag it XD
 one sec. I will do that.
 will cloning it from launchpad and then `git tag ubuntu/VERSION` work?
 I don't think so no.
 so how do I do it?
 I do see a branch named ubuntu/focal there
 I am not sure but you will need to change the origin. If you clone from launchpad your changes (by default) go to launchpad.
 so only git push origin ubuntu/focal then?
 no
 then what?
 you don't need to apply a tag to launchpad.
 you need to push it to phab.
 @kc2bez [you don't need to apply a tag to launchpad.], yeah I already see the tag there
 @kc2bez [you need to push it to phab.], how is that done?
 @wxl [<wxl> in other news, we have a new packageg coming it seems https://github.com/l …], njoice.
 *noice
 @wxl [<wxl> in other news, we have a new packageg coming it seems https://github.com/l …], that seems to be progressing nicely.
[22:14] <wxl> clone from phab; push to phab
 @wxl [<wxl> clone from phab; push to phab], thoda details please?
[22:14] <wxl> you're overthinking it bub
 well you said to tag it
 last step
[22:15] <wxl> git clone https://phab.lubuntu.me/source/lxqt-globalkeys.git
[22:15] <wxl> <make changes>
[22:15] <wxl> git push
 what changes exactly?
[22:15] <wxl> the changes you uploaded
 mean these? https://launchpadlibrarian.net/459429230/lxqt-globalkeys_0.14.1+git20190923-0ubuntu1_0.14.3-1ubuntu1.diff.gz
[22:17] <wxl> so i imagine somehow you'll have to turn your debdiff or whatever into a patch
 yeah that was what I was thinking just now
 @The_LoudSpeaker [mean these? https://launchpadlibrarian.net/459429230/lxqt-globalkeys_0.14.1+git2 …], I need to convert this.
[22:18] <wxl> right that's it
[22:20] <wxl> `git apply patch.diff` should do the trick, assuming you don't need to do any other mods
 but then if I already have changes in launchpad, shouldn't phab pull them automatically? They are currently in proposed packet. which I assume will go slowly into release one.
[22:20] <wxl> no
[22:20] <wxl> you don't have changes in launchpad
[22:20] <wxl> you have changes in the release archive
[22:20] <wxl> NOT the same
 changes made in phab go to release pocket directly na? it should also pull from there.
 @wxl [<wxl> NOT the same], oh behenchooo
[22:21] <wxl> changes made in phab go nowhere until they're uploaded
 whyyy!!
 @wxl [<wxl> changes made in phab go nowhere until they're uploaded], yeah I meant after uploading only
[22:21] <wxl> because @tsimonq2 says to make it automatic would be a "big project"
 @The_LoudSpeaker [whyyy!!], It allows for a review process before the upload.
 Also sponsorship
 @wxl [<wxl> because @tsimonq2 says to make it automatic would be a "big project"], you mean to say it is https://phab.lubuntu.me/macro/view/4/
 @kc2bez [It allows for a review process before the upload.], the whyy was for why phab doesn't pull automatically
[22:24] <wxl> i think it WOULD be good to have archive uploads sync to git
[22:24] <wxl> oppsite direction not so much XD
 This^
[22:29] <wxl> sorry i think you'll want `git apply -p1` while in the root (which should have the source untarred in it)
[22:30] <wxl> e.g. lxqt-globalkeys-0.14.3/debian/control would then make changes to debian/control
[22:30] <wxl> and lxqt-globalkeys-0.14.3/CHANGELOG would make changes to CHANGELOG
[22:30] <wxl> in case you're not familiar with `patch`, this follows the same behavior there
 p1?
[22:37] <wxl> yep
 @The_LoudSpeaker [mean these? https://launchpadlibrarian.net/459429230/lxqt-globalkeys_0.14.1+git2 …], the thing is, this is made from version 0.14.1+git20190923 to 0.14.3 but to apply any patch, I need to uscan —download-current -version and untar it. How do I get that for that +git version? uscan only takes from 0.14.3 o
 the patch should change that too
[22:40] <wxl> yeah but he would need the tarball first
[22:40] <wxl> since it makes changes to the initial one
 gotcha
 @wxl [<wxl> yeah but he would need the tarball first], exjhactly
[22:40] <wxl> --download-version <version>
[22:41] <wxl> or perhaps better --download-debversion <version>
 so I download and create one using github?
[22:41] <wxl> or maybe even --download-current-version
 @wxl [<wxl> or maybe even --download-current-version], all of then don't work
 ```ubuntu@focal-dev:~/globalkeys/lxqt-globalkeys$ uscan --download-current-version  … uscan warn: In debian/watch no matching hrefs for version 0.14.1+git20190923 in watch line …   https://github.com/lxqt/lxqt-globalkeys/releases .*/lxqt-globalkeys-([\d\.]+).tar.xz … ubuntu@focal-dev:~/globalkeys/lxqt-globalkeys$```
[22:41] <wxl> you tried?
[22:41] <wxl> dude
[22:41] <wxl> --download-current-version
[22:41] <wxl> is not the same as
[22:42] <wxl> --download-version <specify the version you want here>
 @wxl> --download-version <specify the version you want here [<wxl> --download-version <specify the version you want here>], I had tried that didn't work last time. will try again now
 if you change the version in the changelog then try current-version ?
 @kc2bez [if you change the version in the changelog then try current-version ?], patch doesn't apply then
[22:44] <wxl> he means change it long enough to get the tarball
[22:44] <wxl> it's called "cheating"
 right
 I like to call it "out of the box" thinking :P
 I got the tar ball of 0.14.3 by specifiing the version even now the patch doesn't apply
[22:45] <wxl> you don't want 0.14.3
[22:45] <wxl> you want 0.14.1+git20190923
 so change it back now that you have the tar
 @wxl [<wxl> you want 0.14.1+git20190923], ubuntu@focal-dev:~/globalkeys/lxqt-globalkeys$ uscan --download-version 0.14.1+git20190923 … uscan warn: In debian/watch no matching hrefs for version 0.14.1+git20190923 in watch line …   https://github.com/lxqt/lxqt-globalkeys/releases .*/lxqt-globalkeys-([\d\.]+).tar.xz
[22:47] <wxl> use --download-debversion
 same story
 what are you trying to do?
 to get the recently pushed changes into phab
 these: https://launchpadlibrarian.net/459429230/lxqt-globalkeys_0.14.1+git20190923-0ubuntu1_0.14.3-1ubuntu1.diff.gz
[22:49] <wxl> he needs the old tarball at this point
[22:49] <wxl> well
[22:49] <wxl> another option is this
 @wxl [<wxl> he needs the old tarball at this point], I think I should try to make one from github
 why would you need the old tarball?
[22:50] <wxl> since the source changes don't matter to phab, just remove all the changes that don't involve debian
[22:50] <wxl> then apply that
 then that is, I guess, simillar to what we do while updating on phab for new upstream releases
 is it?
[22:51] <wxl> yep
 tried that
 didn't work
[22:53] <wxl> what is "that?"
 what if, I shifted to a branch of 0.14.1-ubuntu-something on phab and then tried updating as if I was updating for new upstream release?
[22:53] <wxl> why not do what i said?
 @wxl [<wxl> what is "that?"], updating from that git one as if I am updating for new upstream release.
 ^
[22:54] <wxl> i wouldn't suggest it
[22:54] <wxl> do what i said: modify the diff
 also, someone remind me how we picked that git? I will directly go and pick from the commit of 0.14.3 release. will mark version as 0.14.3 instead of 0.14.3+gitsomething. will remove hassel from next time.
 @wxl [<wxl> do what i said: modify the diff], will try now.
 wait there are changes to cmakelists and translations if those are removed only one line in debian/lxqt-globalkeys.install remains
 really I should do it?
[22:57] <wxl> uh
[22:57] <wxl> so you made no changes to d/changelog?
 I mean between both versions only change to debian folder is that instal file. apart from changelog
[22:58] <wxl> i see changes to:
[22:58] <wxl> changelog
[22:58] <wxl> control
[22:58] <wxl> gbp.conf
[22:58] <wxl> patches/complete-config-file.patch
[22:58] <wxl> patches/series
[22:59] <wxl> i see no changes to the file you mentioned
 oh yesh I noticed now.
 but I did make changes to that install file while resolving conflicts
[23:00] <wxl> it's not in that diff
 hence the first point under extra changes in changelog
[23:02] <wxl> i see the changelog entry
[23:02] <wxl> i DON'T see the change to the file
[23:02] <wxl> grep the file yourself and see
 those were already on ubuntu side. not in debian one hence the failure in mom. I had kept the ubuntu one.
 remember we changed the location of installation of upstream config fille? that was the change
[23:08] <wxl> i hear what you're saying
[23:08] <wxl> but it's not there
 what you said works. But only changelog doesn't apply
 I will remove changelog also  from diff and write it by hand
 https://paste.ubuntu.com/p/sWrJCg2pJh/
[23:13] <wxl> inspect the diff in comparison to the changelog and see if you can figure it out
 I tried.
[23:13] <wxl> i'm at work so i can't do it for you but that's what needs to happen
 points to 247th line but that line seems fine in debian/changelog. Infact, it shouldn't touch it.
[23:14] <wxl> might be some whitespace or something
[23:15] <wxl> @@ -247,3 +313,4 @@
[23:15] <wxl> * Use lower-case for description.
[23:15] <wxl> why are there OLD changes to the changelog???????
 same question!!
[23:15] <wxl> ^ is that normal with mom, @RikMills ?
 @wxl [<wxl> * Use lower-case for description.], that line is laready there currently. should I just remove it from diff?
 woop! I am removing it. will add later if required. it is taking too long for this small thing. I have class at 8am.
 what should be the version number tho?
 1ubuntu1 is already used na?
 wxl: old?
 also I don't think I need those changes about translations now in changelog. not there in diff.
 @RikMills [wxl: old?], ?
[23:22] <wxl> @RikMills changes to the *past* history in the changelog
[23:22] <wxl> https://launchpadlibrarian.net/459429230/lxqt-globalkeys_0.14.1+git20190923-0ubuntu1_0.14.3-1ubuntu1.diff.gz
 0.14.3-1ubuntu1 is the one I put in that archive one. so I put 2 here?
[23:23] <wxl> e.g
[23:23] <wxl> @@ -39,6 +98,13 @@
[23:23] <wxl>  
[23:23] <wxl>   -- Simon Quigley <tsimonq2@ubuntu.com>  Sat, 26 Jan 2019 00:15:52 -0600
[23:23] <wxl>  
[23:23] <wxl> +lxqt-globalkeys (0.13.0-1) unstable; urgency=medium
[23:23] <wxl> +
[23:23] <wxl> +  * Cherry-picking new upstream version 0.13.0.
[23:23] <wxl> +  * Bumped build dependency liblxqt0-dev to >= 0.13.0~
[23:23] <wxl> +
[23:23] <wxl> + -- Alf Gaida <agaida@siduction.org>  Thu, 24 May 2018 21:23:58 +0200
[23:23] <wxl> +
[23:24] <wxl> so i'm a bit weirded out by that
 @wxl [<wxl> +  * Cherry-picking new upstream version 0.13.0.], we could have done this now. couldn't we?
[23:24] <wxl> however if you want to fix the "problem" if you look carefully at the plus signs you should see the issue:
[23:24] <wxl> @@ -247,3 +313,4 @@
[23:24] <wxl>    * Use lower-case for description.
[23:24] <wxl>  
[23:24] <wxl>   -- Andrew Lee (æŽå¥ç§‹) <ajqlee@debian.org>  Sun, 16 Aug 2015 02:18:03 +0800
[23:24] <wxl> +
 yeah this is the issue and I don't understand why!!
[23:24] <wxl> also i think there's a bit of whitespace after that .
 wxl: changelog gets merged as well. so it shows both history. that is what merging means
[23:25] <wxl> the last + adds an empty line
[23:25] <wxl> @RikMills okie dokie. it's just scary :)
 @wxl [<wxl> the last + adds an empty line], I removed that in the start, it says curropt patch. doesn't apply
 tell meee the version number!!!
[23:26] <wxl> we're merging 0.14.3-1 no?
[23:27] <wxl> and removing all the patches, right?
[23:27] <wxl> if so, 0.14.3-1
 yeah
 @wxl [<wxl> if so, 0.14.3-1], okay
[23:27] <wxl> remember 1ubuntu2 means 1 debian patch and 2 ubuntu patches
 still not applying
 ubuntu@focal-dev:~/globalkeys/lxqt-globalkeys$ git apply ~/lxqt-globalkeys_0.14.3-1.diff --ignore-whitespace  … error: patch failed: debian/control:11 … error: debian/control: patch does not apply … error: debian/gbp.conf: already exists in working directory … error: debian/patches/complete-config-file.patch: No such file or d
 tomorrow let us cherry pic the upstream commit of 0.14.3? okay?