 https://phab.lubuntu.me/P51
 ^ @tsimonq2 @kc2bez wxl:
 anyone else.
 also, did we miss standup again today?
 @The_LoudSpeaker [https://phab.lubuntu.me/P51], install the correct -dev package
 https://packages.ubuntu.com/search?suite=focal&arch=any&mode=exactfilename&searchon=contents&keywords=Qt5DBusConfig.cmake
 @The_LoudSpeaker [also, did we miss standup again today?], Yes. I was busy and lost track of it. Semester break maintenance happening here.
 @RikMills [https://packages.ubuntu.com/search?suite=focal&arch=any&mode=exactfilename&searc …], Thanks! I will do it tonight.
 I just left home.
 @RikMills [https://packages.ubuntu.com/search?suite=focal&arch=any&mode=exactfilename&searc …], This is a very helpful page. I should probably bookmark it.
 luguito is on vacation
 He needs a break.
 @tsimonq2 you free?
 @The_LoudSpeaker [@tsimonq2 you free?], Free but no computer
 What's up?
 `CMake Error at CMakeLists.txt:24 (find_package): …   By not providing "FindQt5LinguistTools.cmake" in CMAKE_MODULE_PATH this …   project has asked CMake to find a package configuration file provided by …   "Qt5LinguistTools", but CMake did not find one. …   Could not find a package configuration file provided by "Qt5LinguistT
 @RikMills [https://packages.ubuntu.com/search?suite=focal&arch=any&mode=exactfilename&searc …], ^
 Plug both of those cmake files in
 I installed qtbase5-dev
 And find the package
 Yeah, just search for the new ones
 I searched
 @RikMills [Yeah, just search for the new ones], Right. Once you add it as a build dep it should be fine
 https://packages.ubuntu.com/search?suite=focal&arch=any&mode=filename&searchon=contents&keywords=Qt5LinguistTools
 @The_LoudSpeaker [I searched], Both of them?
 @The_LoudSpeaker [https://packages.ubuntu.com/search?suite=focal&arch=any&mode=filename&searchon=c …], ^
 @The_LoudSpeaker [https://packages.ubuntu.com/search?suite=focal&arch=any&mode=filename&searchon=c …], Add the file extension and specifically put that it's a file in your query :)
 The fisrt one works: https://packages.ubuntu.com/search?searchon=contents&keywords=Qt5LinguistToolsConfig.cmake&mode=exactfilename&suite=focal&arch=any
 worked
 Thanks!
 To be claer, as said you need to search for the while filename: Qt5LinguistToolsConfig.cmake
 Yeah I did that
 or chnage the default search option to "packages that contain files whose names contain the keyword"
 have to install qttools5-dev
 133MB download :/
 @The_LoudSpeaker [133MB download :/], Convince your Uni to host an Ubuntu archive mirror
 @tsimonq2 [Convince your Uni to host an Ubuntu archive mirror], For them 2TB is too much
 can't get a 2TB storage for this
 but I am not in uni currently.
 This is a perfect example of something the Lubuntu funds would cover ;)
 Uni's 1.5GB bandwidth is enough if not for sophos. But thats a different story.
 @tsimonq2 [This is a perfect example of something the Lubuntu funds would cover ;)], ooooooooooh! ;)
 @The_LoudSpeaker [Uni's 1.5GB bandwidth is enough if not for sophos. But thats a different story.], problem is my own network provider. currently
 @The_LoudSpeaker [problem is my own network provider. currently], apt-cacher-ng
 That's some kind of proxy right?
 Yeah
 I will have to set it up.
 First task when I reach uni
 Cool
 I had something simillar set up for chroots before but removed later
 yay! after 4 more searches and installation of various libraries and packages cmake succesfully wrote the build files
 @The_LoudSpeaker [yay! after 4 more searches and installation of various libraries and packages cm …], apt build-dep PACKAGE
 Or similar
 I was installing what cmake logs asked me.
 That's why these builds are typically done in a clean environment. You may have a package installed on your system already which may be an optional flag and can change the output of a package as opposed to pure build dependencies on top of a base system which can provide insight into whether optional dependencies are necessary, prese
 https://paste.ubuntu.com/p/Z86N9Zy2Zj/
 I see only translation errors. cmake files are fixed I suppose.
 Check line 111
 *facepalms*
 Look up in the code the file and line number it's outputting and pastebin that line with five lines before and after for context
 @The_LoudSpeaker [I see only translation errors. cmake files are fixed I suppose.], Correct
 @tsimonq2 [Look up in the code the file and line number it's outputting and pastebin that l …], Five lines is typically safe
 Is this straight from upstream?
 yup!
 straight from the mom package
 @The_LoudSpeaker [straight from the mom package], Aha
 @tsimonq2 [Look up in the code the file and line number it's outputting and pastebin that l …], ^
 I'm willing to bet it's a merge conflict that you still need to resolve
 I also think so.
 I would personally do a recursive grep for ">>>" and "<<<" respectively, which should highlight where your merge conflicts are
 In translations, a good rule of thumb is to always favor Debian's variant
 I use ^W in nano for that
 @tsimonq2 [In translations, a good rule of thumb is to always favor Debian's variant], yeah I did that only
 ubuntu one was a bit incomplete
 like it is written in the file that it is incomplete
 I should have saved an example
 The next thing I would encourage you to do, once you're done and get this to build, is run `debuild -S -d` and run `debdiff <CURRENT DEBIAN VERSION>.dsc <NEW UBUNTU VERSION BASED ON TOP>.dsc` and manually inspect the diff. MoM can sometimes be stupid
 It's also a good way to figure out precisely what to document in the changelog
 @The_LoudSpeaker [ubuntu one was a bit incomplete], Makes sense
 @tsimonq2 [The next thing I would encourage you to do, once you're done and get this to bui …], okay
 @tsimonq2 [The next thing I would encourage you to do, once you're done and get this to bui …], At the end of the day, when we keep an Ubuntu delta, it's a good practice to get in the habit of always analyzing the current delta, partly for documentation reason but partly because if there's something we can send to Debian, we shou
 oh I acutally forgot to fix that file in line 111
 @tsimonq2 [At the end of the day, when we keep an Ubuntu delta, it's a good practice to get …], Cases where you should continue adding things to your new version include but are not limited to if Debian added changelog entries, if Debian has more translations (unless our base strings are different, which is rare but has happened 
 When you do merges from Debian, always always always completely document the remaining delta thoroughly in the changelog
 I can pull up an example if you'd like but it's fairly straightforward
 @The_LoudSpeaker [oh I acutally forgot to fix that file in line 111], No worries :)
 The reason why I've let others fill in with explanations of deltas and how to deal with them is because it's a fairly abstract concept that took me some time to fully comprehend myself
 It's one of those things that has become muscle memory to me and is difficult to teach
 @tsimonq2 [I can pull up an example if you'd like but it's fairly straightforward], example would be good.
 if you aren't busy ;)
 @The_LoudSpeaker [example would be good.], Sure, let me think of one
 @The_LoudSpeaker [example would be good.], https://launchpad.net/ubuntu/+source/sbuild/0.74.0-1ubuntu1
 I pulled that straight from my Core Developer application :)
 https://wiki.ubuntu.com/tsimonq2/Applications/CoreDeveloper
 noice.
 build succesful yayayay!
 `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 lxqt-
 I should create one ? from the current folder?
 https://paste.ubuntu.com/p/dnC597Tdm9/
 I have libx11-dev and xserver-xorg-input-libinput-dev installed
 ^^ @tsimonq2 wxl: @kc2bez
 @RikMills
 and others. any help appreciated.
 I think it is an issue with the control file.
 I will have to merge it correctly again afaik.
 Those two build depends were from the debian side but not on the ubuntu side. I kept the debian side when merging.
 @The_LoudSpeaker are you on eoan or focal?
 focal
 container
 I did modify the debian changelog accordingly
 nvm
 I forgot to place a "," between those two
 *facepalms*
 but still I need a source tar ball.
 can you show me the control file?
 for the tarball, you noeed to get the sourcecode
 running debsign failed now. 😶
 @HMollerCl [can you show me the control file?], one sec
 https://wiki.debian.org/Packaging/Intro?action=show&redirect=IntroDebianPackaging
 @The_LoudSpeaker [running debsign failed now. 😶], for ppa?
 for debuild -S -d
 @HMollerCl [can you show me the control file?], https://phab.lubuntu.me/P52
 @The_LoudSpeaker [https://phab.lubuntu.me/P52], you solved the ","?
 @HMollerCl [you solved the ","?], yup!
 @HMollerCl [for ppa?], using —no-sign doesn't give the error
 yes, signing is for signing .deb so you can upload to ppa
 when only want to build .de I use: debuild -us -uc -tc
 (-tc is postclean)
 okay. noted.
 to upload to a PPA, run debuild -S -d -sa -k[key]
 now running debdiff
 @HMollerCl [to upload to a PPA, run debuild -S -d -sa -k[key]], okay. this goes to saved messaged
 *messages
 I fetched the current debian version. dsc from mom page and I already have the just compiled current-ubuntu-version-on-top.dsc but I can't run debdiff
 @tsimonq2
 https://paste.ubuntu.com/p/fCXVKNRD3N/
 @teward001
 you need tar
 @HMollerCl [https://wiki.debian.org/Packaging/Intro?action=show&redirect=IntroDebianPackagin …], @The_LoudSpeaker see this
 for debdiff also?
 @HMollerCl [@The_LoudSpeaker see this], k.
 dpkg-source: error: cannot fstat file /home/ubuntu/lxqt-globalkeys_0.14.3.orig.tar.xz: No such file or directory
 it gives an error
 If debdiff is passed two source packages (.dsc files) it will compare the contents of the source packages. If the source packages differ only in Debian revision number (that is, the .orig.tar.gz files are the same in the two .dsc files), then interdiff(1) will be used to compare the two patch files if this program is available on th
 ^ from manpages
 got it running. downloaded resp orig.tar.xz , tar.xz.asc and a debian.tar.xz
 got a looong output. showing changes
 @tsimonq2 @teward001 next steps on how to upload this merged source?
 @The_LoudSpeaker [got a looong output. showing changes], meanwhile I will try to document this in debian changelog if something is not already present.