[01:25] <guiverc[m]> thanks kc2bez for noticing & dealing ^ with copyright issue... I'd not checked !
 "arraybolt3: Merged. One-line..." <- Are you talking about in the lintian-overrides file? For some reason, no matter how hard I tried, I could not get it to accept the file if I put the comment first (kept complaining about a malformed file)! Maybe I was doing something else wrong and just thought it was the comment.
[03:30] <arraybolt3[m]> Anyway, glad it works!
[03:30] <arraybolt3[m]> OK, I should probably get back to fighting with the symbols. I'm going to do this manually once. Then I'm going to make a program to do it for me forever after. (That's my hope, anyway.)
[04:13] <arraybolt3[m]> Wow. I just spent so long patching the symbols file, only to realize I had put the 32-bit symbols where the 64-bit ones went and vice versa...
[04:44] <tsimonq2> Lmk how it goes :)
[04:45]  * arraybolt3[m] wants out of the world of _ZNK2Fm3Job10metaObjectEv@Base
[04:47] <tsimonq2> lmao
[04:47] <tsimonq2> What does that even translate to after c++filt?
[04:48] <arraybolt3[m]> _ZTVSt23
[04:48] <arraybolt3[m]> (OK, not really, I'll find out in just a sec)
[04:48] <arraybolt3[m]> FINALLY! That was the last symbol. Nice to be back in the world of English.
[04:49] <arraybolt3[m]> Simon Quigley (Developer): _ZNK2Fm3Job10metaObjectEv = Fm::Job::metaObject() const
[04:49] <arraybolt3[m]> (I just grabbed some random symbol for comedic value.)
[04:49] <tsimonq2> You get er?
[04:49] <arraybolt3[m]> Can I just say neither one is very human-readable?
[04:49] <arraybolt3[m]> Yeah, I think I got it.
[04:50] <arraybolt3[m]> Here's hoping it passes an sbuild. Maybe we should submit a pkgkde-symbolshelper patch so it doesn't make us go through this misery again.
[04:50] <arraybolt3[m]> (This was actually fun, I'm trying to be silly here.)
[04:51] <arraybolt3[m]> (Talking about "misery", I mean.)
[04:52] <arraybolt3[m]> We accept humorous Git commit messages, right? I just named my latest commit "Defeated Symbol the Great"
 there is one in the manul of "remove colon"
[04:58] <arraybolt3[m]> @lynorian I can't tell you how many times I've had to do "(edit: typo)" on Reddit. (I have an alt account I use a lot, so you probably won't see it on my u/ArrayBolt3, but I have to do that a lot.)
[04:58] <arraybolt3[m]> Simon Quigley (Developer): Well, sbuild finished and didn't scream at me about symbols, so I think I got it! Now to wrestle with everything else Lintian is mad about.
[05:00] <arraybolt3[m]> Then I'll do one more PPA upload, and if that works, I'll finally be ready to PR and move on to the next package.
 "We accept humorous Git commit..." <- I'm Simon Quigley and I approve this commit message >:P
 "Then I'll do one more PPA upload..." <- Sweeet
[05:21] <arraybolt3[m]> Simon Quigley (Developer): Any progress on the DVD player installer screen for l'GNU/Hurd?
[05:35] <tsimonq2> LMAO 
[05:35] <tsimonq2> Not yet 
[05:42] <arraybolt3[m]> Alright! No symbol errors on all five architectures, PR incoming.
[05:45] <arraybolt3[m]> Simon Quigley (Developer): https://github.com/lubuntu-team/libfm-qt-packaging/pull/1
[07:11] <arraybolt3[m]> Simon Quigley (Developer): Hey, if you're there, I've hit a bit of a roadblock in lxqt-themes.
[07:14] <arraybolt3[m]> My current source is here: https://github.com/ArrayBolt3/lxqt-themes-packaging/tree/backports/jammy
[07:15] <arraybolt3[m]> Every time I try to do an sbuild, it appears to be working normally, and then I get an endless (or at least seemingly endless) stream of messages that all say "INFO: pkgstripfiles: waiting for lock (lxqt-system-theme) ..."
[07:15] <arraybolt3[m]> The last thing I did was seriously overhaul the lxqt-themes.install file, so I'm guessing that's where the problem is, but I can't see anything in particular wrong in there.
 "Simon Quigley (Developer): https..." <- Comment added
 "Every time I try to do an sbuild..." <- How long are you waiting? Can take up to 30 mins. Perhaps set `DH_VERBOSE = 1` in `debian/rules`
[07:51] <arraybolt3[m]> tsimonq2: Not that long, that's for sure. I'll try again and let it go.
[08:13] <arraybolt3[m]> What do you know, waiting worked!
[08:14] <arraybolt3[m]> (I'm going through the comments and preparing to fix my earlier work on libfm-qt also.)
[08:17] <arraybolt3[m]> Simon Quigley (Developer): Shoot. You know how you were talking about the c++filt checking of symbols? Guess what I got:
[08:17] <arraybolt3[m]> Fm::FolderConfig::getStringList(char const*, unsigned int*)
[08:17] <arraybolt3[m]> Versus:
[08:17] <arraybolt3[m]> Fm::FolderConfig::getStringList(char const*, unsigned long*)
[08:18] <arraybolt3[m]> Simon Quigley (Developer): I believe the character that marked the difference between int* and long* was marked {size_t} when the subst tag was still there. From what I know of programming, I know int and long may not jive together, but from what I know of pointers, int* on 32-bit and long* on 64-bit may indeed be reasonable. You know way more C++ than me, thoughts?
[08:25] <arraybolt3[m]> Alright, I pushed a lot of fixes, but since I still don't know how to proceed with the symbols, it's not yet done.
[08:29] <arraybolt3[m]> Bah, and I forgot to deal with the copyright stuff.
 "Every time I try to do an sbuild..." <- Ah, you found png optimization hell. Wait until build artwork. 
[09:20] <arraybolt3[m]> Glad to know it was at least doing something.
[09:20] <kc2bez[m]> * Ah, you found png optimization hell. Wait until you build artwork. 
[09:20] <kc2bez[m]> It feels like forever 
 "Simon Quigley (Developer): I..." <- I'll consider this my fault for being vague... that sounds reasonable but it's just the first step. You see how you're excluding three arches on one line and only including two on the other?
[16:46] <tsimonq2> riscv64 will fail on new symbols
[16:49] <tsimonq2> arraybolt3 @arraybolt3:matrix.org: backports is fine to run wrap-and-sort, I was talking about the archive, the main one we don't control :)
[16:56] <tsimonq2> And comment added.
 "I'll consider this my fault..." <- Ah. I was just taking vorlon's word for it that those were the right symbol tags to use, but you're right. pkgkde-symbolshelper probably got confused due to the lack of riscv64 symbols in my patches, and so put excludes where they didn't go (many of the symbols were tagged (arch=!riscv64|subst)). The only way I can really see to do this right is to get a riscv64 compile... so how do I
[19:10] <arraybolt3[m]> do that, or what is the best way forward?
[19:11] <arraybolt3[m]> (And the fact that the symbols were tagged like that to begin with probably means vorlon figured that the !riscv64 was right and so included that in the tags he told me about.)
[19:17] <arraybolt3[m]> Is there some way to cross-compile for riscv64 with sbuild?
 "Is there some way to cross-..." <- Very likely yes
 "Ah. I was just taking vorlon's..." <- He's great :) just read the backlog
 arraybolt: you can qemu system compile in a riscv emulated env without direct crossbuild.  i'll get the dependency info you will need to install
 its also slow as sin but solves the crossbuild chaos/headaches
 if you want me to riscv testbuild let me know i have riscv sbuild envs via qemu
 you'll need to build the arch specific sbuild chroot but you also need to adjust your apt-cacher to properly reach to ports.ubuntu.com
 because other than i386 and amd64 all those other archs are on ports not the main archive