[01:57] <Eickmeyer> OvenWerks: Oh crap, I meant Audacity, not Ardour. My bad.
[01:59]  * OvenWerks feels better
[02:00] <Eickmeyer> teward: vorlon seems to have fixed the digikam debacle.
[02:01] <OvenWerks> Audacity is generally usable with no external plugins, though plugins are nice to be able to use.
[02:03] <OvenWerks> Eickmeyer: that is why I did not question audacity being snapped when you were talking about that a few days ago.
[02:05] <Eickmeyer> OvenWerks: Yeah,  I dunno what I was thinking. In my mind I thought Audacity, and my fingers typed Ardour. Ardour is in no danger.
[02:09] <arraybolt3> Thank goodness. I heard Ardour and a red alarm in the back of my head started blaring in the background.
[02:20] <Eickmeyer> Yeah. We almost lost Ardour once before, and I fought tooth-and-nail for that one.
[14:16] <ThomasWard[m]> Eickmeyer: howd he do that?
[14:18] <Eickmeyer[m]> Thomas Ward: There's a vendor-provided qtav in the source code that I was unaware of. The build failure was due to a lack of CMakeLists.txt files inside the transalations directories, which I fixed by hacking the git snapshot archive.
[14:20] <Eickmeyer[m]> So, he mostly pointed me in the right direction.
[14:23] <ThomasWard[m]> ah
[14:24] <ThomasWard[m]> so you dirtied the git snapshot tree to fix it xD
[14:25] <Eickmeyer[m]> Not exactly. The translations aren't part of the git snapshot to begin with. There's a KDE tool that creates the git snapshot with the translations that was missing the CMakeLists.txt files for some reason, so I just fixed that part.
[14:26] <Eickmeyer[m]> So, it's an official snapshot, as far as KDE is concerned.
[14:27] <Eickmeyer[m]> Basically, if it's a raw snapshot, it's completely missing the translations.
[14:29] <Eickmeyer[m]> And while the translations aren't 100% perfect, I'd rather have some translations when beta freeze comes along than not.
[14:35] <ThomasWard[m]> makes sense
[14:35] <ThomasWard[m]> at least its fixed xD
[14:39] <Eickmeyer[m]> Yup!
[14:39] <Eickmeyer[m]> And we'll see how the Audacity snap does today during the .iso image build.
[16:03] <teward> Eickmeyer[m] if all goes well then it should "just work"
[16:05] <Eickmeyer> teward: Agreed. I've been working closely with Dani on this, and they've got it working pretty well. Seeding snaps can be finicky, though, as I found out with freeshow.
[16:05] <teward> heh
[16:06] <teward> by this point it shouldn't be that hard though :P
[16:06] <teward> just saying
[16:06] <teward> since there's already seeded snaps in Ubuntu Desktop and such
[16:07] <Eickmeyer> True. They had to drop the gtk2-common-themes requirement, and it still seemed to function correctly. The problem is that gtk2-common-themes can't be seeded because it doesn't have a base: declaration, not even on base: bare.
[16:08] <Eickmeyer> But gtk-common-themes, which is a newer, non-legacy snap, seems to fit the bill.
[16:38] <Eickmeyer> We just had a successful image build with the Audacity snap, and the latest digikam git snapshot just hit the release pocket! \o/


[19:22] <cyphermox> reynhout: you want to call the script from ubiquity/success_command
[19:23] <cyphermox> see the end of http://people.canonical.com/~mtrudel/preseed/crypto.cfg, there's an example script commented out.
[19:36] <reynhout> cyphermox: ok, so i just set the ubiquity/success_command string in a preseed config? that looks easy, thank you!
[19:38] <cyphermox> yeah, from there you should be able to call your script
[19:38] <cyphermox> might be easier than formatting it to fix in success_command.
[19:39] <reynhout> yeah, that makes sense. i also see "ubiquity/install/success_command" but that's not the right one to use? (desc says "Reticulating splines..." :)