Libretime: Cut a new release that includes fix for "300k empty playlists" bug

Created on 6 Mar 2019  路  16Comments  路  Source: LibreTime/libretime

Now that https://github.com/LibreTime/libretime/issues/411 (and https://github.com/LibreTime/libretime/issues/743) is resolved, can we cut a new release? Our radio server is having this issue on a daily basis, and we've even catered to the workarounds, so we're not sure what's going on. It'd be great to dpkg -i a new libretime deb that solves this issue!

bug

All 16 comments

So the debian packages are built by @paddatrapper and @hairmare has been the one to cut every release so far, so feedback from both of the would be essential for this to move forward.

I would like to get Buster support in, but that isn't crucial considering it isn't released yet. When a new release is made, I'll update the packages

Awesomeeeeee, thank you @paddatrapper! @Robbt, can we cut a new release? Happy to help if I can throw in hands :raised_hands:

Before we cut a new release I want to do some more testing to make sure that the database updates don't need to correspond to the release version to be automatically deployed. Also I'd rather not do the release without @hairmare unless he isn't able to for some reason.

If you just want to fix this problem, the easiest thing to do is just make sure that you don't have any autoloading playlist enabled with None selected as the playlist. Sorry about this bug and hopefully we can get a new version out. I'm not sure how installing a deb on top of a working install would work either.

@Robbt, how's the testing going? Thanks so much for doing this!

I have not gotten around to testing this. I was at the FSF LibrePlanet conference over the weekend and I'm just working on getting situated. I'll try to prioritize this. I got a lot of inspiration for how we can move forward with LibreTime in general.

++ to @Robbt , thanks for your dedicated work on this. Will be happy to test a new release for this fix. I've put in my own workarounds, but they are quite sloppy.
Truly respect your dedication to this project!

We are planning on releasing alpha.7 once the two PRs listed in milestone 8 are merged. #781 just requires testing and #784 can be merged once #781 has landed

So #781 has been closed because it wasn't the right approach and I haven't been able to duplicate the bug it was attempting to fix. I would like my bug fix in #802 to be merged but then we can push the release w/ updated information.

I've merged #802, just need to update the release notes

(which I am busy doing at the moment)

Ohh I just did that. Sorry.

I also added a contributors section where we list the various users who contributed PRs to this release.

No worries, I have merged the changes I made into yours.

Released :tada: deb packaging will follow in the next day or so

This thread has been automatically locked since there has not been any recent activity after it was closed. Please open a new issue for related bugs.
Please chat to us on discourse or ask for help on our chat if you have any questions or need further assistance with this issue.

Was this page helpful?
0 / 5 - 0 ratings