[01:52] <Eickmeyer[m]> OvenWerks: The good news is that Ardour will be heading back to the repos. teward and I fixed it.
[01:53] <Eickmeyer[m]> I'll try to figure out if idjc can be salvaged.
[02:43] <Eickmeyer[m]> Yeah, that's way over my head. I don't think I can get that one to patch properly.
 @Eickmeyer orrrrrrrrrr not
 Rejected: … File ardour_5.12.0-3ubuntu1.debian.tar.xz already exists in Primary Archive for Ubuntu, but uploaded version has different contents. See more information about this error in https://help.launchpad.net/Packaging/UploadErrors. … Files specified in DSC are broken or missing, skipping package unpack verification.
 sorry my mail died because my residential network exploded, I had to switch over to my business connection
 but yeah, I'm assuming you didn't version bump it
 so I'm going to version bump it
 which i'd have to do anyways thanks to doko's failures
 @Eickmeyer I've pushed the version change to the repo, can you tag it?
 assuming you do version tagging
 Yeah, I can.
 okay THAT looks better
 ```ardour (1:5.12.0-3ubuntu2) focal; urgency=medium …   * This upload does NOT include the changes introduced in 1:5.12.0-3ubuntu1 …     which is in focal-proposed due to those changes FTBFSing entirely and …     requiring the changes applied here in -3ubuntu2. …   * Update to waf 2.0.19, patch to build with python 3 …     * 0010-waf.pa
[03:56] <studiobot> tch updated by Erich Eickmeyer …     * 0020-fix-wscripts.patch by Erich Eickmeyer, …       code by David Runge (Ardour Developer) …     * 0025-point-to-custom-autowaf.patch by Erich Eickmeyer …       code by Robin Gareus (Ardour Developer) …     * 0028-Patch-waf-to-actually-build-install-properly.patch …       by Erich Eickmeyer, code by Robin Gare
[03:56] <studiobot> us (Ardour Developer) …   * Patch to build against fluidsynth 2 …     * 0027-fluidsynth2.patch by Andreas Müller …   * Drop wiimote support as recommended from upstream Ardour … Date: Fri, 24 Jan 2020 09:36:23 -0800 … Changed-By: Erich Eickmeyer <erich@ericheickmeyer.com> … Maintainer: Ubuntu Developers <ubuntu-devel-discuss@lists.ubuntu.com> … Sig
[03:56] <studiobot> ned-By: Thomas Ward <teward@thomas-ward.net> … https://launchpad.net/ubuntu/+source/ardour/1:5.12.0-3ubuntu2```
 Accepted
 Probably a result of doko uploading a version that fully FTBFS due to the python 3 thing. #shocker
 Uhhh... you comitted the removal of libs/ardour/config_text.cc and libs/ardour/revision.cc. That might cause problems.
 @teward001 ^
 😐
 okay that's a mistake
 i'll fix that
 git revert
 Yup.
 git revert then nitpick my changelog changes only
 :P
 please :)
 (including the note that it skipped -3ubuntu1 because that's a relevant note)
 (I did the git commit after the source build oops)
 Yeeep, but you're going to have to go 3ubuntu3 because you uploaded 3ubuntu2 and it was accepted.
 ... or we stage the changes for next upload
 -3ubuntu2 the removal of stuff was because of the sbuild run
 debuild run*
 Yeah, I know. I had to discard those changes EVERY time I ran debuild.
 Do you want to do the dirty work or should I?
 i've already reverted.
 Ok. I'll pull.
 just... tag it as -3ubuntu2 if you haven't already.
 then i'll pull and debuild -S it again.  The commit of the removal wasn't intentional
 but debuild *does* remove the files during source vuild run so
 Yeah, but we don't want to screw that up.
 or are you saying that removal is 'bad" because debuild removed them and we need -3ubuntu3 anyways?
 E:UNCLEAR
 well, the git revert reverted the removals so 😜
 the git commit was *after* I did the `debuild -S -sa` call
 sooooo
 that's probably the issue there
 Yeah, I'm not worried about it now, but I would be worried if something got angry about the files not being there to remove.
 You know, unexpected FTBFS and all due to two files not being able to be deleted.
 true, but the `clean` step is called anyways
 and it has `rm -f`
 which means whether it exists or not it won't error
 called during debuild -S and called during build time
 which is why it didn't FTBFS in local testing
 because it was already purged from the source package.
 https://git.launchpad.net/~ubuntustudio-dev/+git/ardour/tree/debian/rules#n96
 and line 98 under it
 there's several clean calls it seems
 Ah, I guess I didn't see that.
 yeah it has multiple nasty clean calls in here
 but the clean phase purges the config_text.cc and version.cc files anyways
 i agree committing that change is *bad*
 but sbuild *will* clean those files
 debuild*
 Right, but we shouldn't be modifying the source files directly. I guess that's probably the biggest objection.
 as i said that's why git revert is helpful
 again
 Yeeep.
 this was just a minor misstep which we can fix because we didn't tag anything yet
 Right.
 extract the changelog bits, revise changelog, commit JUST that
 tag after that
 problem solved
 Yep. So, are we uploading 3ubuntu2 or 3 ubuntu 3? I just want to know what we're doing so as to version properly.
 @teward001 ?
 Nevermind.
 @Eickmeyer [Yep. So, are we uploading 3ubuntu2 or 3 ubuntu 3? I just want to know what we're …], 3ubuntu2
 k
 because the .cc files would be removed anyways
 Right
 That's what occurred to me, hence the nevermind.
[18:30] <RikMills> Eickmeyer: did you seed scribus-ng? if so I think you can go back to scribus normal package now so we can get rid of the ng one
[18:34] <Eickmeyer[m]> RikMills: It's like you read my mind. I'm updating the seed now. haha
[18:35] <RikMills> :)
[18:35] <Eickmeyer[m]> Had to get some ardour stuff fixed in the meantime.
[18:35] <Eickmeyer[m]> That's all sorted now.
[18:35] <Eickmeyer[m]> Just didn't want to update the seed without ardour and raysession.
[18:44] <RikMills> all cool. I was poked by the debian maintainer as they thought it was seeded somewhere
[18:50] <Eickmeyer[m]> It was, is now not.
[19:17] <RikMills> :)