gitlab-ci: run make dist on debian target

cf. !68 (merged)

changed milestone to %4.0

added Component::Build system label

added 1 commit

• f2c80726 - gitlab-ci: run make dist on debian target

Compare with previous version

resolved all threads

added 1 commit

• 518fe451 - gitlab-ci: run make dist on debian target

Compare with previous version

Pipeline failed as expected, will be fixed when !68 (merged) is merged

added MRStatus::NotCompliant label

resolved all threads

added 2 commits

• 4d13639f - 1 commit from branch videolan:master
• 29369152 - gitlab-ci: run make dist on debian target

Compare with previous version

added MRStatus::Acceptable label and removed MRStatus::NotCompliant label

added MRStatus::Accepted label and removed MRStatus::Acceptable label

MR Acceptance result

This MergeRequest has been Accepted! Congratulations.

MR acceptance checks details:

• MR should be considered mergeable by Gitlab
• Last pipeline should be successful
• MergeRequest should have at least one external review and/or vote
• All threads should be resolved, and score >= 0
• MergeRequest should have no activity (threads/votes) for (24h/24h)

This message was automatically generated by homer-bot.

added 21 commits

• 29369152...800482fb - 20 commits from branch videolan:master
• 172eacd6 - gitlab-ci: run make dist on debian target

Compare with previous version

enabled an automatic merge when the pipeline for 172eacd6 succeeds

merged

I am surprised that this is not already done, TBH. But then again, unless we postpone the build system switch-over until after 4.0 is forked, this seems a bit late to the party.

make distcheck is a bit of an automake idiosynchrasy afterall. If it weren't for our automake legacy, we could just as well use git-archive instead of make dist and not worry about effectively tracking source files twice.