=== teward[m] is now known as Guest1021
[18:32] <teward> Eickmeyer[m]: FYI: avldrums.lv2 was accepted in NEW.
[18:55] <RikMills> that means hydrogen can be replaced?
[19:21] <OvenWerks> RikMills: no.
[19:22] <OvenWerks> Hydrogen is a useful patern based sequencer all on it's own
[19:23] <RikMills> if its that useful, please package the Qt5 version
[19:24] <OvenWerks> avldrums is a drum synth plugin that does take the place of something like DrMr.lv2 and is a lighter alternative to drumgizmo for those with less computer resources.
[19:25] <OvenWerks> RikMills: why the hurry? There is still software that has just (in the past month or so) changed to QT 4
[19:25] <OvenWerks> (rivendell)
[19:25] <OvenWerks> Running way ahead of all the software does not seem like a great idea
[19:26] <RikMills> Qt4 is being removed from debian, and hopefullt 20.04
[19:26] <RikMills> *hopefully
[19:26] <OvenWerks> That did not answer the question
[19:30] <RikMills> I'm just going through the packages blocking Qt4 removal, that is all.
[19:31] <OvenWerks> That is not a justification for removing qt4
[19:31] <OvenWerks> So I guess the reason is "Cause we want to"
[19:32] <RikMills> The reason is we can't support it
[19:32] <OvenWerks> Eickmeyer[m]: ^^
[20:01] <RikMills> Qt5 should migrate on this britney run I hope
[20:01] <RikMills> ^ ignore. wrong room
[20:07] <Eickmeyer[m]> RikMills: The Qt5 version has already been packaged, though it's still "beta" and has been for yeeears. What's in Focal now is the Qt5 version.
[20:08] <Eickmeyer[m]> teward: I got the ping in #ubuntu-release.
[20:08] <OvenWerks> Eickmeyer[m]: good to know.
[20:09] <RikMills> Eickmeyer[m]: the Qt4 removal transition tracker disagrees
[20:09] <Eickmeyer[m]> My biggest objection is that it has a nag dialog that says "beta" which is very offputting to LTS users. But, oh well.
[20:09] <Eickmeyer[m]> RikMills: It's wrong. I checked it myself.
[20:10] <Eickmeyer[m]> Besides, that's a package we sync from Debian.
[20:10] <Eickmeyer[m]> Same with Ardour, but that was complete FTBFS which required my immediate attention.
[20:10] <RikMills> Eickmeyer[m]: this also disagrees https://launchpad.net/ubuntu/+source/hydrogen
[20:11] <Eickmeyer[m]> If Debian is removing it, then it'll get removed and we'll go to the version I packaged. However, that's not happening.
[20:11] <Eickmeyer[m]> RikMills: The implication is that it would require a complete rewrite of our installation test case, which I reeeealllly don't want to do.
[20:12] <RikMills> so transition tracker is correct
[20:15] <Eickmeyer[m]> RikMills: Yes, apparently the test I did was against the version I packaged. oops. HOWEVER, I have bugged the Hydrogen developers about this. I'm likely not to do anything about this until it gets closer to feature freeze as I want to give them as much time as possible.
[20:15] <Eickmeyer[m]> RikMills: I do NOT want to release beta software with a nag dialog.
[20:15] <Eickmeyer[m]> Especially in an LTS.
[20:15] <RikMills> I'm sure that can be removed or amended if needed
[20:16] <Eickmeyer[m]> I don't have the 1) bandwidth or 2) know-how to do that.
[20:16] <OvenWerks> Eickmeyer[m]: can be done as the old version plus git*?
[20:17] <Eickmeyer[m]> OvenWerks: No, it can't. The old version will not even build against Qt5.
[20:17] <Eickmeyer[m]> I tried.
[20:17] <RikMills> Eickmeyer[m]: regards debian... https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=874907
[20:17] <ubottu> Debian bug 874907 in src:hydrogen "[hydrogen] Future Qt4 removal from Buster" [Serious,Open]
[20:17] <RikMills> "Status update: Qt4 has now been droppped from testing, qt4 will be removed from unstable by end of February (along with the remaining rdeps (currently 15))."
[20:18] <OvenWerks> I mean can the new version be pulled as old version +git*
[20:18] <Eickmeyer[m]> OvenWerks: No, it doesn't work like that.
[20:18] <OvenWerks> k
[20:18] <Eickmeyer[m]> RikMills: I'm well aware of that thread.
[20:19] <Eickmeyer[m]> RikMills: I did this back in Nov3ember, it's the beta I speak of: https://code.launchpad.net/~ubuntustudio-dev/+git/hydrogen
[20:19] <Eickmeyer[m]> It's pretty much ready to go, but I reallyl don't want to put it in there with the beta nag.
[20:19] <RikMills> OvenWerks: they versioned the beta as 1.0.0-beta1
[20:20] <RikMills> Eickmeyer[m]: where is it?
[20:20] <Eickmeyer[m]> RikMills: Where is what? That's the git for what I packaged.
[20:21] <RikMills> Yes, or the ppa
[20:23] <Eickmeyer[m]> RikMills: Here's the issue I opened with them: https://github.com/hydrogen-music/hydrogen/issues/794
[20:23] <Eickmeyer[m]> RikMills: I appear to have deleted it from my PPA by mistake, I'll get it building again.
[20:24]  * RikMills subscribes
[20:29] <RikMills> data/hydrogen.default.conf:     <showDevelWarning>true</showDevelWarning>
[20:29] <RikMills> I guess set that to false via packaging, and the warning will go away?
[20:31] <RikMills> keeping the warning but changing the text would be problematic, as it appears to be a translated string
[20:36] <Eickmeyer[m]> I feel like I ran across that issue as well.
[20:37] <Eickmeyer[m]> If it can be disabled via that one string, I'm all for it RikMills .
[20:37] <Eickmeyer[m]> Shouldn't be hard to patch.
[20:37] <RikMills> exactly
[20:38] <RikMills> actually the DELEVOLOPERS notes in the source say exactly this
[20:38] <Eickmeyer[m]> I'm just leery of patching things because it invites the whole "We don't know what they've patched in Ubuntu so we don't support it" argument, even when I tell upstream that it's exactly the same as what they themselves have put in Debian. *cough**Ardour**cough*
[20:39] <RikMills> i.e. when they make a non beta release, they should change that config to false to get rid of the nag
[20:40] <RikMills> Eickmeyer[m]: https://community.kde.org/Kubuntu/Policies#Patching_.28.28NEW.29.29
[20:40] <RikMills> "Patches are evil." - apachelogger around 2009 
[20:40] <RikMills> except when they are not :)
[20:41] <RikMills> if we couldn't patch things, no Ubuntu release would ever make it out the door!
[20:47] <Eickmeyer[m]> RikMills: I'm working on some stuff I noticed, such as we'd rather have it building against jackd2 than jack1.
[20:48] <OvenWerks> Eickmeyer[m]: we don't have weakjack?
[20:49] <Eickmeyer[m]> OvenWerks: What's weakjack?
[20:49] <Eickmeyer[m]> (can't find a package name with that)
[20:49] <OvenWerks> another api that works with all the jacks
[20:49] <OvenWerks> I think it is another of RG's thing
[20:50] <Eickmeyer[m]> Well, apparently not. Switching out the build deps in the d/control file isn't that hard though.
[20:50] <OvenWerks> https://github.com/x42/weakjack
[20:51] <Eickmeyer[m]> And, of course, it's probably not building any sort of standard way, which means I'll have to patch the living junk out of it to get it to build, which means... yeah, not for an LTS.
[20:51] <OvenWerks>  :)
[20:51] <OvenWerks> Basically it is the the jack_lib.h file
[20:52] <Eickmeyer[m]> I see that. Really, that's all it is, but it's so much easier just to change-out the build dep.
[20:52] <OvenWerks> Nope it doesn't replace it goes inbetween... forget I mentioned it.
[21:03] <Eickmeyer[m]> RikMills: Building now in my PPA (https://launchpad.net/~eeickmeyer/+archive/ubuntu/ppa/+packages). I'll be out for a while to get my son from school, but I don't forsee any issues.
[21:03] <RikMills> Eickmeyer[m]: cool. I'll have a look later
[21:24] <Eickmeyer[m]> RikMills: Looks like a FTBFS due to the python issue. I'll look more when I get home.
[21:39] <RikMills> you have 3001-remove-nag-dialog.patch
[21:48] <Eickmeyer[m]> RikMills: Yes. I made that.
[21:49] <RikMills> :)