Commit f26e3a85 authored by Jonathan Dowland's avatar Jonathan Dowland

rework from 5.2+dfsg1 to 5.2

turns out we don't need to revert the DoomBSP code any more!
parent 8bea4f5a
crispy-doom (5.2+dfsg1-1) unstable; urgency=medium
crispy-doom (5.2-1) unstable; urgency=medium
* Initial packaging based on chocolate-doom.
Closes: #880972.
* dfsg-adjusted upstream source, see debian/copyright for details.
* We do not build or install the crispy-server program: it is identical
to, and designed to be compatible with, the pre-existing
chocolate-server.
* Lintian has two false positives (privacy-breach-generic), see
#902919 for details.
-- Jonathan Dowland <jmtd@debian.org> Tue, 03 Jul 2018 21:05:28 +0100
-- Jonathan Dowland <jmtd@debian.org> Thu, 05 Jul 2018 14:37:21 +0100
This diff is collapsed.
This diff is collapsed.
no_server.patch
correct_doc_license.patch
  • Hi @jmtd,

    is it really necessary to add a "source" file for a HTML page? Currently, this is really turning me down from getting seriously involved into packaging my own source port. Is there anything that I as the copyright holder can add to this text to make clear that it is not necessary to have the mediawiki "sources" packaged alongside?

    Thanks,

    Fabian

  • is it really necessary to add a "source" file for a HTML page?

    I'm afraid so. Lintian catches the missing source, and it is missing source, so it's an RC bug.

    Currently, this is really turning me down from getting seriously involved into packaging my own source port. Is there anything that I as the copyright holder can add to this text to make clear that it is not necessary to have the mediawiki "sources" packaged alongside?

    If the HTML was the preferred form for modification, then there'd be no need for anything else, but it isn't. If the HTML simply wasn't added to the tarball, the problem wouldn't be in Debian either.

    So yeah it's not fun, but at least I've done it, so you (nor anyone else) have had to.

  • So yeah it's not fun, but at least I've done it, so you (nor anyone else) have had to.

    I was going to package the 5.3 release and wondered if this was a necessary step. So, it seems like we have to keep this in sync for each new upstream version. :/

  • Solved! The Github project page with its README.md document is now the official homepage. The former "homepage" on the Choco wiki is now merely a stub with references to the actual homepage.

    https://github.com/fabiangreffrath/crispy-doom/commit/2a0590d7c3383069b635d93b57e2b3b1d4299ffd

Markdown is supported
0% or
You are about to add 0 people to the discussion. Proceed with caution.
Finish editing this message first!
Please register or to comment