Anonymous Login
2021-09-24 14:20 UTC

View Issue Details Jump to Notes ]
IDProjectCategoryView StatusLast Update
0001642OpenClonkWebsite - Automated Buildspublic2017-10-26 13:02
Assigned To 
Product Version 
Target Versiongit masterFixed in Version 
Summary0001642: In the release source tarball, all files are marked as executable
DescriptionOnly files that are actually executable should be marked as executable.
Steps To Reproducewget
tar tvf openclonk-7.0-src.tar.bz2
Additional Information
TagsNo tags attached.
Attached Files




Isilkor (developer)

Not my bug, the exported source tree ( is correct; somebody broke things when uploading to


Isilkor (developer)

Reminder sent to: Newton

Newton may have uploaded the tarball to


Newton (administrator)

Apparently Windows does add it when I touch the contents of the tar.

I do unpack and pack it again because I remove the Experimental.ocf, Tests.ocf etc. folders as I do not want them to turn up in
* Linux packages of the game (.deb, .rpm,...)
* the folder in which a (Linux) user decides to compile the game himself

That I do this manually is a temporary solution anyway. Couldn't the build system be extended to do this automatically? When is the source package on git archive created - is it already available when the release button is pushed?


Isilkor (developer)

> When is the source package on git archive created - is it already available when the release button is pushed?
It's created whenever somebody pushes a tag to the repository.


Newton (administrator)

...Which happens after the button has been pushed. So the release scripts have to create a source tar themself.


Isilkor (developer)

> Which happens after the button has been pushed.
Well if somebody releases before pushing a tag that's their own fault.


Newton (administrator)

That is beside the point, it is enough that it is possible and valid to do so (as it is described like this in the wiki) that makes it necessary that the release scripts have to create a source tar themselves.


Isilkor (developer)

Last edited: 2016-01-24 12:14

View 2 revisions

Ignoring the wiki, since you won't find anything there because there's no search function, let me quote the release tool for you:

Pre Release Checklist

Dont forget to increase the version number in Version.txt.
Run a Dry Release to make sure the generated files are correct. Dry Release Area
Create a tag for the release.

Emphasis mine.


Newton (administrator)

Last edited: 2016-01-24 13:37

View 2 revisions

My previous point holds. Anyway, the wiki article is here:

I corrected it.


Maikel (developer)

In the 6.0 series we explicitly decided to tag after the release has been done, in case something goes wrong. So now we change that?


Isilkor (developer)

"In case something goes wrong" doesn't really apply because we can do dry releases, which do the exact same thing as the real deal except updating the website.

-Issue History
Date Modified Username Field Change
2016-01-19 16:33 Luchs New Issue
2016-01-19 16:33 Luchs Status new => assigned
2016-01-19 16:33 Luchs Assigned To => Isilkor
2016-01-19 21:08 Isilkor Note Added: 0004827
2016-01-19 21:08 Isilkor Assigned To Isilkor =>
2016-01-19 21:08 Isilkor Status assigned => new
2016-01-23 19:43 Isilkor Note Added: 0004858
2016-01-24 10:56 Newton Note Added: 0004862
2016-01-24 10:57 Isilkor Note Added: 0004863
2016-01-24 11:15 Newton Note Added: 0004864
2016-01-24 11:22 Isilkor Note Added: 0004865
2016-01-24 12:02 Newton Note Added: 0004867
2016-01-24 12:14 Isilkor Note Added: 0004868
2016-01-24 12:14 Isilkor Note Edited: 0004868 View Revisions
2016-01-24 13:36 Newton Note Added: 0004869
2016-01-24 13:37 Newton Note Edited: 0004869 View Revisions
2016-01-24 13:48 Maikel Note Added: 0004870
2016-01-24 13:53 Isilkor Note Added: 0004871
2017-08-05 13:58 Maikel Target Version => 8.0
2017-10-26 13:02 Clonkonaut Target Version 8.0 => git master
+Issue History