Remove debian folder

[Rossmaxx]

The debian folder was added as a part of 1.2 packaging and serves no purpose in master. The patches in the folder too are mostly obsolete as these fixes now landed on master. Also, these files should be handled by the distros and shouldn't belong here.

tagging @jasp00 for their opinion

[jasp00]

This is just my opinion:

The debian folder was used to include continuous integration in several environments (GCC, Clang) when Travis CI was available. It also carried copyright information for the whole project. Besides, it helped making good Debian packages, which seems to be a problem now (broken VST support).

I do not know the current state of LMMS, but I would keep these features (continuous integration, copyright information). I have a different point of view regarding cooperation with distros, but I am not an active developer, so this does not seem important.

[Rossmaxx]

Thanks for your insight @jasp00

The debian folder was used to include continuous integration in several environments (GCC, Clang) when Travis CI was available.

We do have CI through GitHub actions. We migrated away from travis and circle ci long ago.

It also carried copyright information for the whole project.

Don't we have a license.txt?

Besides, it helped making good Debian packages, which seems to be a problem now (broken VST support).

That issue was fixed recently by @tresf , if the fix fails, we still intend to fix it our side. We just don't need to carry technical debt from upstream.

I do not know the current state of LMMS

A lot has changed since you last left. If you need clarification, better to chat on discord as others too might add to the tidbits, as I'm relatively new and don't know some of the minor aspects which changed.

[tresf]

The debian folder was used to include continuous integration in several environments (GCC, Clang) when Travis CI was available.

We do have CI through GitHub actions. We migrated away from travis and circle ci long ago.

AFAIR, @jasp00 is referring to some specific patches to get compiles working properly with clang. I'm not sure how relevant they are now.

It also carried copyright information for the whole project.

Don't we have a license.txt?

@jasp00 had added exhaustive copyright information, including information for files that don't comply with GPL2. Since we bundle samples and projects that are under different licenses, this caused violation with GPL2 as developers cannot make changes and release these files in accordance with the GPL2. The goal is to move the project to CC0, which is GPL2 compatible. This project is ongoing and needs help: https://github.com/LMMS/assets?tab=readme-ov-file#assets

Besides, it helped making good Debian packages, which seems to be a problem now (broken VST support).

That issue was fixed recently by @tresf , if the fix fails, we still intend to fix it our side. We just don't need to carry technical debt from upstream.

I can't imagine these two issues are related but I'd be happy to help investigate in another thread if needed. @Rossmaxx is referring to this PR #7268.

I do not know the current state of LMMS

A lot has changed since you last left. If you need clarification, better to chat on discord as others too might add to the tidbits, as I'm relatively new and don't know some of the minor aspects which changed.

This is as good of a place to discuss as any. 🍻