[00:22] <OvenWerks> Eickmeyer[m]: ok got that I will compare to liquorix when I get my PS.
[00:22] <OvenWerks> Eickmeyer[m]: having trouble with getting autojack to stop at session end.
[00:23] <OvenWerks> The session shutdown does not seem to send a SIGTERM to it.
[00:24] <OvenWerks> In fact it is not that jackdbus keeps running so much as autojack keeps running.
[00:47] <OvenWerks> I can manually send SIGTERM and get that to work (or SIGINT) but the session end does not seem to do so.
[01:31] <Eickmeyer[m]> So, I've got some more bad news: raysession, idjc, jack-mixer, and ardour have been removed from the repos for whatever reason. I've fixed raysession. idjc and jack-mixer look like bitrot/dependence on python 2. Still trying to figure out ardour.
[01:31] <Eickmeyer[m]> teward: Need a new upload of raysession, ready at lp:raysession
[01:31] <Eickmeyer[m]> (no changes rebuild)
[01:34] <OvenWerks> gtk2?
[01:34] <Eickmeyer[m]> No, GTK2 isn't removed. Python2 and Qt4 were removed.
[01:35] <Eickmeyer[m]> raysession had an old qt4 dep that I fixed.
[01:35] <OvenWerks> ardour's ./waf maybe then
[01:37] <Eickmeyer[m]> I don't know. I do know that nothing has been synced from debian regarding it. I might look at the packaging myself and figure out what dep is missing. I'm guessying a python2 thing, but not sure.
[01:39] <OvenWerks> last I heard there was someone working on changing it to py 3
[01:40] <Eickmeyer[m]> Well I hope it gets done soon then because if it doesn't, we're up a creek without a paddle.
[01:40] <OvenWerks> Maybe ubuntu is just not a good platform for  audio...
[01:40] <OvenWerks> (or any real work)
[01:40] <Eickmeyer[m]> I'm sure it's just a dependency issue, let's not overreact.
[01:40]  * OvenWerks is just being grumpy
[01:56] <OvenWerks> If the py 2 - 3 thing gets done for Ardour it will be A6
[01:56] <Eickmeyer[m]> How close are we to that? I don't want to ship an LTS without Ardour.
[01:56] <OvenWerks> not close enough.
[01:57] <OvenWerks> I don't know if it will be back portable to 5.12 either
[01:59] <OvenWerks> Someone from arch is working on it
[01:59] <OvenWerks> :) maybe use the arch package as upstream :)
[02:00] <Eickmeyer[m]> Possibly. Arch has a different way of packaging things.
[02:01] <OvenWerks> Two of them I think
[02:01] <OvenWerks> prebuilt and auto builds as part of install.
[02:03] <Eickmeyer[m]> The auto build as part of install is an AUR (Arch User Repository) thing. (Former Arch user here)
[02:03] <Eickmeyer[m]> AUR is unofficial.
[02:11] <Eickmeyer[m]> Either way, I might be able to reverse-engineer the packaging.
[02:34] <OvenWerks>  I would also miss idjc
[02:34] <Eickmeyer[m]> That project hasn't seen any light for nearly 3 years.
[02:36] <OvenWerks> That doen't on its own, make it broken
[02:37] <OvenWerks> I think it is the default studio software for Rivendel
[02:38] <Eickmeyer[m]> The inability to port to Python 3 after so many years makes it broken.
[02:53] <OvenWerks> the unwillingness of ubuntu to continue to support common still in use libs makes it broken.
[02:57] <OvenWerks> anyway, it is what it is.
[02:57] <Eickmeyer[m]> OvenWerks: Does this look like a port: https://github.com/M0Rf30/idjc
[02:58] <Eickmeyer[m]> OvenWerks: There's also this, but it looks a little old(er).
[02:58] <Eickmeyer[m]> https://github.com/radiocicletta/idjc-x
[03:01] <OvenWerks> The top one has all new file dates.
[03:01] <OvenWerks> interesting that it has gtk3 on python 2.7
[03:04] <Eickmeyer[m]> So, it's not python 3. That's the deal-breaker.
[03:06] <OvenWerks> but he has been working on in the pst two months. It does not use glade. It would be interesting to just run on py 3 and see where it breaks.
[03:06] <OvenWerks> if theres a  lot I don't have time though.
[03:13] <OvenWerks> the second link you have there: https://github.com/radiocicletta/idjc-x
[03:13] <OvenWerks> is python 3
[03:14] <OvenWerks> the original source forge page does have additions by the original author in 2019
[03:15]  * OvenWerks notes that there is new versions of software released in 2019 that have upgraded from qt3 to qt4... 
[03:16] <Eickmeyer[m]> Ok. So, if i take our source package and add the code from that git repo as a patch, we should be good to go.
[03:17] <OvenWerks> ya the purpose of that repo is to follow tghe original code with the only difference being py 3 instaed of py2
[03:17] <Eickmeyer[m]> Looks like all of the changes are in the python directory.
[03:18] <OvenWerks> so everytime there is a change to https://sourceforge.net/p/idjc/code/ci/master/tree/ then https://github.com/radiocicletta/idjc-x will change too.
[03:18] <Eickmeyer[m]> Well, I'm going to have to take the original code from salsa.
[03:19] <Eickmeyer[m]> Shouldn't be too hard.
[03:20] <OvenWerks> Ardour is probably more inportant.
[03:20] <OvenWerks> but maybe harder.
[03:21] <OvenWerks> Ardour is just the build system.... but what a build system
[03:56] <Eickmeyer[m]> Yeah. As I look at this, I may be doing it backwards for idjc. I should probably clone idjc-x and yeet the debian directory into it and make changes there.
[03:56] <Eickmeyer[m]> I was thinking a patch from the python3 directory, but it seems like there's too much tied to pygtk2.
[03:57] <Eickmeyer[m]> But yeah, I really should invest my energy into ardour at this point.
[03:58] <Eickmeyer[m]> Huh. Already being worked on: https://salsa.debian.org/multimedia-team/ardour
[03:58] <Eickmeyer[m]> Patched waf to use python3.
[04:02] <Eickmeyer[m]> OvenWerks: They just haven't thrown it into testing yet. I guess I'll pull it and at least have it ready to go for an upload, just in case.
[04:28] <Eickmeyer[m]> teward: When you get a chance, and because the upstream at Debian hasn't done anything yet, and it includes a patch that fixes some Ubiquity-related stuff for us, I have updated materia-gtk-theme. I'll need it uploaded. lp:~ubuntustudio-dev/ubuntustudio/+git/materia-gtk-theme
[04:29] <Eickmeyer[m]> (the Debian version is 4 versions behind)
[05:23] <OvenWerks> Huh, it looks like /etc/xdg/autostart/* is going to go away in favour of systemd --user
[05:24] <OvenWerks> (from gnomes home page... but maybe systemd will get rid of my problem)
[05:32] <OvenWerks> systemd may be generating modules from xdg/autostart on the fly anyway.
[05:32] <OvenWerks> (wrongly)
[06:19] <Eickmeyer[m]> Yeah, that makes sense.
[08:29] <astraljava> dax: Great, cheers! :)
[18:54] <teward> Eickmeyer[m]: what all needs uploaded?
[18:54] <teward> And in what priority?
[18:54] <teward> I see multiple pings so...
[18:56] <Eickmeyer[m]> teward: raysession, materia-gtk-theme, avldrums.lv2 so far.
[18:57] <Eickmeyer[m]> Might have ardour soon, but I'm having the worst trouble getting source to build.
[18:57] <Eickmeyer[m]> afk for a while...
[19:04] <teward> In that order of priority I will handle things
[19:04] <teward> Once i drag myself out of bed.
[21:30] <Eickmeyer[m]> teward: Should be simple for raysession as it's basically a no-changes rebuild against Qt5's language handler.
[21:31] <Eickmeyer[m]> materia is an update, but relatively trivial and just includes newer GTK support than the old one.
[21:31] <Eickmeyer[m]> avldrums.lv2 is the one that's new.
[21:34] <teward> rayssession in progress
[21:34] <teward> pushing that now
[21:34] <teward> materia is next on the list, link to its code since my scrollback is fubar?
[21:37] <teward> Eickmeyer[m]: i think there's a Lintian warning on materia, running a local sbuild first to confirm
[21:37] <Eickmeyer[m]> teward: Ok, I didn't see anything warning in the source, so that's news.
[21:39] <teward> W: materia-gtk-theme source: syntax-error-in-dep5-copyright line 64: Duplicate field copyright.  <--
[21:39] <teward> does't fail lintian, but it *does* throw a W: class in the lintian build
[21:39] <teward> NACK on materia as-is until the issue is fixed
[21:39] <teward> because dep5 is important :p
[21:40] <Eickmeyer[m]> Ok, that's not a huge issue. I probably did something stupid, I'll have that fixed shortly.
[21:40] <teward> huge issue, no.  but not compliant :)
[21:42] <teward> Eickmeyer[m]: did you repack avldrumps.lv2's tarball?
[21:42] <teward> because....
[21:42] <teward> pristine-tar says it can't find the orig to build
[21:42] <teward> which means I'm probably going to have to build the tarball manually
[21:42] <Eickmeyer[m]> I did. Hang on, it's possible I didn't pristine-tar it.
[21:42] <Eickmeyer[m]> (fixing Materia right now, just need to tag/push).
[21:43] <teward> ack
[21:43] <teward> *goes to eat foods*
[21:43] <Eickmeyer[m]> teward: Materia is now pushed.
[21:45] <Eickmeyer[m]> teward: Did you remember to re-clone avldrums.lv2?
[21:45] <teward> my packaging directory gets purged every week
[21:45] <Eickmeyer[m]> teward: Reason being, I had to redo the git repo as well.
[21:45] <teward> of all packages
[21:45] <teward> it's a fresh clone
[21:45] <Eickmeyer[m]> Ok.
[21:45] <teward> so unless your path changed
[21:46] <teward> i have a 'clean clone'
[21:47] <teward> though git could be at fault
[21:47] <teward> *redoes again*
[21:49] <Eickmeyer[m]> You did also checkout the pristine-tar branch, right?
[21:49] <teward> ok finally got it working
[21:49] <Eickmeyer[m]> Let me know because I'll re-push the pristine-tar branch if I have to.
[21:49] <teward> looks like my script i've been using to force this is expecting XZ'd files
[21:49] <teward> not gz
[21:49] <teward> which isn't uncommon now that upstream is using xz everywhere on Debian >.>
[21:50] <Eickmeyer[m]> Ok, good.
[21:50] <Eickmeyer[m]> ...
[21:51] <Eickmeyer[m]> Strange, my repack is a .gz.
[21:51] <Eickmeyer[m]> Oh... I see what you're saying. 🤦‍♂️
[21:52] <teward> because your repack is a gz and the script(s) I've been writing were relying on the default of XZ d'oh
[21:52] <teward> but yeah it's fine
[21:52] <teward> doesn't affect things long-term just an extra step of work
[21:52] <teward> unrelated
[21:52] <teward> i've called out doko for not marking that removal bug as affecting raysession
[21:52] <teward> which it does
[21:52] <teward> because now raysession has to go through NEW again
[21:59] <Eickmeyer[m]> teward: Same with idjc (which is a dead project as far as I can tell) and Ardour. Ardour is a key application for us, so it HAS to be included, but the removal bug never mentioned Ardour either. That one has me just about livid.
 is there a replacement?
[22:01] <Eickmeyer[m]> teward: Debian seems to have some stuff in the works in Salsa, but I can't count on that being ready in a month.
[22:03] <Eickmeyer[m]> teward001: Basically, they have patched WAF to be ported to Python3, but it's failing to build. Somebody put-in a merge request to fix that, so I'm going to borrow the code and see what happens locally.
[22:04] <teward> does anything else use ardour other than STudio?
[22:07] <Eickmeyer[m]> teward: It's not seeded by anyone else, if that's what you mean. It's a key application for the audio meta.
[22:08] <Eickmeyer[m]> teward: It's additonally an application that OvenWerks has actual code in.
[22:13] <teward> ok.  i can't say whether it should or shouldn't be accepted with a cherrypicked patch fix but check with the release team to see if they'd OK it when it gets uploaded.
[22:13] <teward> I don't see any issues with nitpicking a patch into the system for making it build proper, i've donet hat for nginx at times too but still
[22:20] <teward> Eickmeyer[m]: upload in progress (slow becuase 34M)
[22:20] <teward> for avldrumms
[22:21] <teward> materia also uploading
[22:23] <teward> materia accepted
[22:24] <teward> still uploading avldrums
[22:31] <Eickmeyer[m]> ok
[22:39] <Eickmeyer[m]> teward, OvenWerks : I got ardour to build with Python3, but it's pretty dirty. It spewed a bunch of lintian errors at me, most of which is waf related (no way around that, will have to be overrides for that part).
[22:39] <teward> > it's pretty dirty
[22:39] <teward> that's what she said.  *shot*
[22:39] <teward> sorry i couldn't help it, i needed a giggle :)
[22:45] <Eickmeyer[m]> Hahahaha
[23:39] <Eickmeyer[m]> teward: I'm getting python-depends-but-no-python-helper from lintian but have no idea how to fix it. Got any ideas?
[23:41] <teward> do you have a ${python:Depends} in the control file?  Or are you using PYthon 3 (${python3:Depends} is what you need)?
[23:41] <teward> either way you need to include the Python debhelper plugin probably in your rules calls 
[23:42] <teward> but i have to look up specifics, and i'm bleh.
[23:42] <Eickmeyer[m]> Right, it wants dh_python somewhere, but I have no idea where to call it.
[23:42] <Eickmeyer[m]> But yes, the control file has ${python:Depends} in it.
[23:42] <teward> OK so you need to drop the pytho ndepends and use python3:depends`dh $@ --with python3 ...`
[23:43] <teward> OK so you need to drop the pytho ndepends and use python3:depends *
[23:43] <teward> AND `dh $@ --with python3` and include dh-python3 in the builddeps I think
[23:43] <teward> but i haven't worked with that in a while.
[23:43] <teward> I need a nap >.>