improve and expand submit text, use 00.00 as a sample UUID

This commit is contained in:
Landon Curt Noll committed 2025-03-03 13:06:43 -08:00
1 parent ba28bd7988
commit 0aff81f35e
5 files changed
+107 -65

No files matched your search

+7 -7
View File
@@ -2135,13 +2135,13 @@ However, you may wish to manually validate the tarball. The tool that does this
is <code>txzchk</code>.</p> is <code>txzchk</code>.</p>
<p>If you wish to validate the tarball without running the <code>mkiocccentry(1)</code> tool, <p>If you wish to validate the tarball without running the <code>mkiocccentry(1)</code> tool,
for instance the tarball for instance the tarball
<code>submit.12345678-1234-4321-abcd-1234567890ab-2.1720636351.txz</code> you can, after <code>submit.00000000-0000-4000-0000-000000000000-2.1720636351.txz</code> you can, after
installing the tools, do:</p> installing the tools, do:</p>
<pre><code> txzchk submit.12345678-1234-4321-abcd-1234567890ab-2.1720636351.txz</code></pre> <pre><code> txzchk submit.00000000-0000-4000-0000-000000000000-2.1720636351.txz</code></pre>
<p>Assuming that the tarball exists and is valid, you should see no output.</p> <p>Assuming that the tarball exists and is valid, you should see no output.</p>
<p>If you wish to see the contents, for instance like <code>mkiocccentry(1)</code> does, you <p>If you wish to see the contents, for instance like <code>mkiocccentry(1)</code> does, you
could do:</p> could do:</p>
<pre><code> txzchk -v 1 submit.12345678-1234-4321-abcd-1234567890ab-2.1720636351.txz</code></pre> <pre><code> txzchk -v 1 submit.00000000-0000-4000-0000-000000000000-2.1720636351.txz</code></pre>
<p>As the <a href="next/guidelines.html#txzchk">guidelines state</a>, it is beyond the scope <p>As the <a href="next/guidelines.html#txzchk">guidelines state</a>, it is beyond the scope
of this document to discuss the many tests that <code>txzchk(1)</code> runs; if you must of this document to discuss the many tests that <code>txzchk(1)</code> runs; if you must
know we refer you to the <a href="https://github.com/ioccc-src/mkiocccentry/blob/master/txzchk.c">source know we refer you to the <a href="https://github.com/ioccc-src/mkiocccentry/blob/master/txzchk.c">source
@@ -2158,10 +2158,10 @@ of your submission.</p>
<p>Rather than <code>mkiocccentry</code> running this tool manually, <code>txzchk</code>’s algorithm uses <p>Rather than <code>mkiocccentry</code> running this tool manually, <code>txzchk</code>’s algorithm uses
the output of this tool. If you wish to validate your tarball filename manually, the output of this tool. If you wish to validate your tarball filename manually,
you can do so. For instance:</p> you can do so. For instance:</p>
<pre><code> fnamchk submit.12345678-1234-4321-abcd-1234567890ab-2.1720636351.txz</code></pre> <pre><code> fnamchk submit.00000000-0000-4000-0000-000000000000-2.1720636351.txz</code></pre>
<p>Assuming everything is OK, it would show:</p> <p>Assuming everything is OK, it would show:</p>
<blockquote> <blockquote>
<p><code>12345678-1234-4321-abcd-1234567890ab-2</code></p> <p><code>00000000-0000-4000-0000-000000000000-2</code></p>
</blockquote> </blockquote>
<p>See also the <p>See also the
FAQ on “<a href="#txzchk">validating your submission tarball</a>” FAQ on “<a href="#txzchk">validating your submission tarball</a>”
@@ -2198,9 +2198,9 @@ two JSON files, <code>.auth.json</code> and <code>.info.json</code> as well as t
the judges <strong>ONLY</strong>; use of this option to validate your submission puts you at the judges <strong>ONLY</strong>; use of this option to validate your submission puts you at
a great risk of violating <a href="next/rules.html#rule17">Rule 17</a>!).</p> a great risk of violating <a href="next/rules.html#rule17">Rule 17</a>!).</p>
<p>As an example, if your submission directory is <p>As an example, if your submission directory is
<code>12345678-1234-4321-abcd-1234567890ab-0/</code> then you should run the following <code>00000000-0000-4000-0000-000000000000-3/</code> then you should run the following
command:</p> command:</p>
<pre><code> chkentry 12345678-1234-4321-abcd-1234567890ab-0</code></pre> <pre><code> chkentry 00000000-0000-4000-0000-000000000000-3</code></pre>
<p>If there is a <a href="https://www.json.org/json-en.html">JSON</a> issue detected by the <p>If there is a <a href="https://www.json.org/json-en.html">JSON</a> issue detected by the
<code>jparse(3)</code> API (i.e. it is not valid JSON) it is an error and <code>chkentry(1)</code> <code>jparse(3)</code> API (i.e. it is not valid JSON) it is an error and <code>chkentry(1)</code>
will report this, exiting with a non-zero exit code. If the parsing is OK (i.e. will report this, exiting with a non-zero exit code. If the parsing is OK (i.e.
+7 -7
View File
@@ -2003,11 +2003,11 @@ is `txzchk`.
If you wish to validate the tarball without running the `mkiocccentry(1)` tool, If you wish to validate the tarball without running the `mkiocccentry(1)` tool,
for instance the tarball for instance the tarball
`submit.12345678-1234-4321-abcd-1234567890ab-2.1720636351.txz` you can, after `submit.00000000-0000-4000-0000-000000000000-2.1720636351.txz` you can, after
installing the tools, do: installing the tools, do:
``` <!---sh--> ``` <!---sh-->
txzchk submit.12345678-1234-4321-abcd-1234567890ab-2.1720636351.txz txzchk submit.00000000-0000-4000-0000-000000000000-2.1720636351.txz
``` ```
Assuming that the tarball exists and is valid, you should see no output. Assuming that the tarball exists and is valid, you should see no output.
@@ -2016,7 +2016,7 @@ If you wish to see the contents, for instance like `mkiocccentry(1)` does, you
could do: could do:
``` <!---sh--> ``` <!---sh-->
txzchk -v 1 submit.12345678-1234-4321-abcd-1234567890ab-2.1720636351.txz txzchk -v 1 submit.00000000-0000-4000-0000-000000000000-2.1720636351.txz
``` ```
As the [guidelines state](next/guidelines.html#txzchk), it is beyond the scope As the [guidelines state](next/guidelines.html#txzchk), it is beyond the scope
@@ -2042,12 +2042,12 @@ the output of this tool. If you wish to validate your tarball filename manually,
you can do so. For instance: you can do so. For instance:
``` <!---sh--> ``` <!---sh-->
fnamchk submit.12345678-1234-4321-abcd-1234567890ab-2.1720636351.txz fnamchk submit.00000000-0000-4000-0000-000000000000-2.1720636351.txz
``` ```
Assuming everything is OK, it would show: Assuming everything is OK, it would show:
> `12345678-1234-4321-abcd-1234567890ab-2` > `00000000-0000-4000-0000-000000000000-2`
See also the See also the
FAQ on "[validating your submission tarball](#txzchk)" FAQ on "[validating your submission tarball](#txzchk)"
@@ -2093,12 +2093,12 @@ the judges **ONLY**; use of this option to validate your submission puts you at
a great risk of violating [Rule 17](next/rules.html#rule17)!). a great risk of violating [Rule 17](next/rules.html#rule17)!).
As an example, if your submission directory is As an example, if your submission directory is
`12345678-1234-4321-abcd-1234567890ab-0/` then you should run the following `00000000-0000-4000-0000-000000000000-3/` then you should run the following
command: command:
``` <!---sh--> ``` <!---sh-->
chkentry 12345678-1234-4321-abcd-1234567890ab-0 chkentry 00000000-0000-4000-0000-000000000000-3
``` ```
If there is a [JSON](https://www.json.org/json-en.html) issue detected by the If there is a [JSON](https://www.json.org/json-en.html) issue detected by the
+39 -22
View File
@@ -424,7 +424,7 @@
<!-- START: this line starts content for HTML phase 21 by: bin/pandoc-wrapper.sh via bin/md2html.sh --> <!-- START: this line starts content for HTML phase 21 by: bin/pandoc-wrapper.sh via bin/md2html.sh -->
<!-- BEFORE: 1st line of markdown file: next/submit.md --> <!-- BEFORE: 1st line of markdown file: next/submit.md -->
<h1 id="how-to-upload-your-submission-to-the-ioccc">How to upload your submission to the IOCCC</h1> <p>Use mkiocccentry to rebuild# How to upload your submission to the IOCCC</p>
<p><strong>IMPORTANT NOTE</strong>: The <a href="https://submit.ioccc.org">IOCCC submit server</a> <p><strong>IMPORTANT NOTE</strong>: The <a href="https://submit.ioccc.org">IOCCC submit server</a>
is only ready for submissions is only ready for submissions
<strong>ONLY WHEN THE CONTEST IS <a href="../faq.html#open">open</a></strong>.</p> <strong>ONLY WHEN THE CONTEST IS <a href="../faq.html#open">open</a></strong>.</p>
@@ -462,14 +462,14 @@ select that slot.</p>
of:</p> of:</p>
<blockquote> <blockquote>
<p>IMPORTANT: Upload only XZ compressed tarballs whose filename is:</p> <p>IMPORTANT: Upload only XZ compressed tarballs whose filename is:</p>
<p><code>submit.7ec754d4-8670-421a-a1b6-7dd3dc5f215e-SLOT.TIMESTAMP.txz</code></p> <p><code>submit.00000000-0000-4000-0000-000000000000-SLOT.TIMESTAMP.txz</code></p>
<p>where <code>SLOT</code> is a slot number, and <code>TIMESTAMP</code> is the build time as a <a href="https://unixtime.org/">Unix <p>where <code>SLOT</code> is a slot number, and <code>TIMESTAMP</code> is the build time as a <a href="https://unixtime.org/">Unix
timestamp</a>.</p> timestamp</a>.</p>
<p>We highly recommend that you use <code>mkiocccentry(1)</code> to create your submit file as <p>We highly recommend that you use <code>mkiocccentry(1)</code> to create your submit file as
it must pass the <code>txzchk(1)</code> sanity checks, and when the uncompressed tarball is it must pass the <code>txzchk(1)</code> sanity checks, and when the uncompressed tarball is
untarred, the resulting directory must pass <code>chkentry(1)</code>.</p> untarred, the resulting directory must pass <code>chkentry(1)</code>.</p>
</blockquote> </blockquote>
<p><strong>NOTE</strong>: the <code>7ec754d4-8670-421a-a1b6-7dd3dc5f215e</code> is your UUID. <strong>MAKE SURE <p><strong>NOTE</strong>: the <code>00000000-0000-4000-0000-000000000000</code> is your UUID. <strong>MAKE SURE
YOU CHANGE IT TO YOUR UUID</strong>!</p> YOU CHANGE IT TO YOUR UUID</strong>!</p>
<p><strong>NOTE</strong>: the <code>SLOT</code> and <code>TIMESTAMP</code> <strong>in the filename</strong> are generated based on <p><strong>NOTE</strong>: the <code>SLOT</code> and <code>TIMESTAMP</code> <strong>in the filename</strong> are generated based on
your input in <code>mkiocccentry(1)</code>.</p> your input in <code>mkiocccentry(1)</code>.</p>
@@ -483,11 +483,11 @@ file in the file selection pop-up in your browser.</p>
the file selection step.</p> the file selection step.</p>
<p>When it’s uploaded it should say something like:</p> <p>When it’s uploaded it should say something like:</p>
<blockquote> <blockquote>
<p>• Uploaded file: <code>submit.9971ada4-b6ae-427d-a7ec-e67a30362cdb-0.1740838915.txz</code></p> <p>• Uploaded file: submit.00000000-0000-4000-0000-000000000000-5.1740838915.txz</p>
</blockquote> </blockquote>
<p>And in the slot it will give you important details like:</p> <p>And in the slot it will give you important details like:</p>
<ul> <ul>
<li>the status of the submission (on upload it will say: <code>"uploaded file into slot"</code>).</li> <li>the status of the submission</li>
<li>the filename, which will be in the correct format, assuming you used <li>the filename, which will be in the correct format, assuming you used
<code>mkiocccentry(1)</code> which is <strong>HIGHLY</strong> recommended so that you do not break <a href="rules.html#rule17">Rule <code>mkiocccentry(1)</code> which is <strong>HIGHLY</strong> recommended so that you do not break <a href="rules.html#rule17">Rule
17</a>!</li> 17</a>!</li>
@@ -496,12 +496,11 @@ tarball listing).</li>
<li>the upload date.</li> <li>the upload date.</li>
<li>the SHA256 hash of the file.</li> <li>the SHA256 hash of the file.</li>
</ul> </ul>
<p>Again the <code>7ec754d4-8670-421a-a1b6-7dd3dc5f215e</code> is your UUID, the <code>SLOT</code> is the <p>Again the <code>00000000-0000-4000-0000-000000000000</code> is your UUID, the <code>SLOT</code> is the
slot number and <code>TIMESTAMP</code> is the build time as a <a href="https://unixtime.org/">Unix slot number and <code>TIMESTAMP</code> is the build time as a <a href="https://unixtime.org/">Unix
timestamp</a>.</p> timestamp</a>.</p>
<p>Now if you’re done, log out.</p> <p>Now if you’re done, log out.</p>
<p>If, on the other hand,, you upload a file that is too big you will see something <p>If, on the other hand, you upload a file that is too big you will see something like:</p>
like:</p>
<blockquote> <blockquote>
<p>The file size of N exceeds the maximum size of 3999971.</p> <p>The file size of N exceeds the maximum size of 3999971.</p>
</blockquote> </blockquote>
@@ -511,30 +510,48 @@ like:</p>
</blockquote> </blockquote>
<p>And if you see something like:</p> <p>And if you see something like:</p>
<blockquote> <blockquote>
<p>Filename for slot: 0 must match this regular expression: <code>^submit.dd3d30c2-d8d0-4506-adcd-d4e029147f39-0\.[1-9][0-9] {9,}\.txz$</code></p> <p>Filename for slot: <code>5</code> must match this regular expression: <code>^submit\.00000000-0000-4000-0000-000000000000-5\.[1-9][0-9]{9,}\.txz</code></p>
</blockquote> </blockquote>
<p>where <code>0</code> is the slot and <code>dd3d30c2-d8d0-4506-adcd-d4e029147f39-01</code> is the UUID <p>You uploaded the wrong filename into a slot.</p>
then you <strong>MUST</strong> upload a properly named XZ compressed tarball, <strong>MAKING SURE</strong> you <p>For example, for the user <code>00000000-0000-4000-0000-000000000000</code>, slot <code>5</code>, a valid filename to upload would be:</p>
package it with <code>mkiocccentry</code>!</p>
<p>If later on you log in and see something like:</p>
<blockquote> <blockquote>
<p><strong>Status: server slot error code: 1! Use mkiocccentry to rebuild and resubmit to <p>submit.00000000-0000-4000-0000-000000000000-5.1740838915.txz</p>
this slot.</strong></p>
</blockquote> </blockquote>
<p>or:</p> <p>where <code>1740838915</code> is a timestamp created by the <code>mkiocccentry(1)</code> tool.</p>
<p>You <strong>MUST</strong> upload a properly named XZ compressed tarball, <strong>MAKING SURE</strong> you
package it with <code>mkiocccentry</code>!</p>
<p>If, however, the slot status shows:</p>
<blockquote>
<p><strong>Status: file successfully uploaded into slot.</strong></p>
</blockquote>
<p>Then you are successfully uploaded a file into the slot.</p>
<p>At this point you may upload another submission file into a different slot, or you’re done, log out.</p>
<p><strong>Please note:</strong> The status page will <strong>NOT</strong> auto-refresh. After you are uploaded a file into a slot, <strong>DO NOT RELOAD</strong>
the page as this may cause your browser to needlessly reload the same file to the same slot.</p>
<p>After you fir finished uploading submissions into slots, please logout.
To see any status updates, you should logout and log back in later.</p>
<h2 id="checking-on-the-status-of-your-submission">Checking on the status of your submission</h2>
<p>You may check on the status of your submission later on, after you logout by logging back in an looking at the slot status.</p>
<p><strong>Please note:</strong> The status page will <strong>NOT</strong> auto-refresh.</p>
<p>When the system begins to process your file (which could be an hour or two later), you might see:</p>
<blockquote>
<p><strong>Status: file fetched. The format test is pending.</strong></p>
</blockquote>
<p>After the format test is complete, if you see an error such as:</p>
<blockquote> <blockquote>
<p><strong>Status: submit file failed the txzchk test! Use mkiocccentry to rebuild and resubmit to this slot.</strong></p> <p><strong>Status: submit file failed the txzchk test! Use mkiocccentry to rebuild and resubmit to this slot.</strong></p>
</blockquote> </blockquote>
<p>… or <strong>ANY OTHER ERROR</strong> then you <strong>MUST FIX</strong> your submission, repackage your <p>Or:</p>
<blockquote>
<p><strong>Status: submit file failed the chkentry test! Use mkiocccentry to rebuild and resubmit to this slot.</strong></p>
</blockquote>
<p>… or <strong>ANY</strong> other error then you <strong>MUST FIX</strong> your submission, repackage your
tarball with <code>mkiocccentry</code> and upload to the same slot again! If you do not fix tarball with <code>mkiocccentry</code> and upload to the same slot again! If you do not fix
this your submission <strong>WILL BE REJECTED</strong> for violating <a href="rules.html#rule17">Rule this your submission <strong>WILL BE REJECTED</strong> for violating <a href="rules.html#rule17">Rule
17</a>!</p> 17</a>!</p>
<p>After the submission deadline is reached, you can log in to check the status of <p>If the format test went well, then you will see:</p>
your submissions. This is what it will say when the judges have verified
that your tarball / submission has been validated (NOT judged), by <code>txzchk(1)</code>
and <code>chkentry(1)</code>:</p>
<blockquote> <blockquote>
<p><strong>Status: the format of this submission has been validated.</strong></p> <p><strong>Status: submit file received by the IOCCC judges. Passed both txzchk and chkentry tests.</strong></p>
</blockquote> </blockquote>
<p><strong>IMPORTANT</strong>: this does <strong>NOT</strong> mean that your submission does not violate the <p><strong>IMPORTANT</strong>: this does <strong>NOT</strong> mean that your submission does not violate the
rules or that everything is OK once the tarball is extracted; it simply means rules or that everything is OK once the tarball is extracted; it simply means
+48 -23
View File
@@ -1,4 +1,4 @@
# How to upload your submission to the IOCCC Use mkiocccentry to rebuild# How to upload your submission to the IOCCC
**IMPORTANT NOTE**: The [IOCCC submit server](https://submit.ioccc.org) **IMPORTANT NOTE**: The [IOCCC submit server](https://submit.ioccc.org)
is only ready for submissions is only ready for submissions
@@ -49,7 +49,7 @@ of:
> IMPORTANT: Upload only XZ compressed tarballs whose filename is: > IMPORTANT: Upload only XZ compressed tarballs whose filename is:
> >
> `submit.7ec754d4-8670-421a-a1b6-7dd3dc5f215e-SLOT.TIMESTAMP.txz` > `submit.00000000-0000-4000-0000-000000000000-SLOT.TIMESTAMP.txz`
> >
> where `SLOT` is a slot number, and `TIMESTAMP` is the build time as a [Unix > where `SLOT` is a slot number, and `TIMESTAMP` is the build time as a [Unix
timestamp](https://unixtime.org/). timestamp](https://unixtime.org/).
@@ -58,7 +58,7 @@ timestamp](https://unixtime.org/).
it must pass the `txzchk(1)` sanity checks, and when the uncompressed tarball is it must pass the `txzchk(1)` sanity checks, and when the uncompressed tarball is
untarred, the resulting directory must pass `chkentry(1)`. untarred, the resulting directory must pass `chkentry(1)`.
**NOTE**: the `7ec754d4-8670-421a-a1b6-7dd3dc5f215e` is your UUID. **MAKE SURE **NOTE**: the `00000000-0000-4000-0000-000000000000` is your UUID. **MAKE SURE
YOU CHANGE IT TO YOUR UUID**! YOU CHANGE IT TO YOUR UUID**!
**NOTE**: the `SLOT` and `TIMESTAMP` **in the filename** are generated based on **NOTE**: the `SLOT` and `TIMESTAMP` **in the filename** are generated based on
@@ -80,12 +80,11 @@ the file selection step.
When it's uploaded it should say something like: When it's uploaded it should say something like:
> • Uploaded file: `submit.9971ada4-b6ae-427d-a7ec-e67a30362cdb-0.1740838915.txz` > • Uploaded file: submit.00000000-0000-4000-0000-000000000000-5.1740838915.txz
And in the slot it will give you important details like: And in the slot it will give you important details like:
- the status of the submission (on upload it will say: `"uploaded file into - the status of the submission
slot"`).
- the filename, which will be in the correct format, assuming you used - the filename, which will be in the correct format, assuming you used
`mkiocccentry(1)` which is **HIGHLY** recommended so that you do not break [Rule `mkiocccentry(1)` which is **HIGHLY** recommended so that you do not break [Rule
17](rules.html#rule17)! 17](rules.html#rule17)!
@@ -94,14 +93,13 @@ tarball listing).
- the upload date. - the upload date.
- the SHA256 hash of the file. - the SHA256 hash of the file.
Again the `7ec754d4-8670-421a-a1b6-7dd3dc5f215e` is your UUID, the `SLOT` is the Again the `00000000-0000-4000-0000-000000000000` is your UUID, the `SLOT` is the
slot number and `TIMESTAMP` is the build time as a [Unix slot number and `TIMESTAMP` is the build time as a [Unix
timestamp](https://unixtime.org/). timestamp](https://unixtime.org/).
Now if you're done, log out. Now if you're done, log out.
If, on the other hand,, you upload a file that is too big you will see something If, on the other hand, you upload a file that is too big you will see something like:
like:
> The file size of N exceeds the maximum size of 3999971. > The file size of N exceeds the maximum size of 3999971.
@@ -111,33 +109,60 @@ And if you try uploading an empty file you'll instead see:
And if you see something like: And if you see something like:
> Filename for slot: 0 must match this regular expression: `^submit.dd3d30c2-d8d0-4506-adcd-d4e029147f39-0\.[1-9][0-9] > Filename for slot: `5` must match this regular expression: `^submit\.00000000-0000-4000-0000-000000000000-5\.[1-9][0-9]{9,}\.txz`
{9,}\.txz$`
where `0` is the slot and `dd3d30c2-d8d0-4506-adcd-d4e029147f39-01` is the UUID You uploaded the wrong filename into a slot.
then you **MUST** upload a properly named XZ compressed tarball, **MAKING SURE** you
For example, for the user `00000000-0000-4000-0000-000000000000`, slot `5`, a valid filename to upload would be:
> submit.00000000-0000-4000-0000-000000000000-5.1740838915.txz
where `1740838915` is a timestamp created by the `mkiocccentry(1)` tool.
You **MUST** upload a properly named XZ compressed tarball, **MAKING SURE** you
package it with `mkiocccentry`! package it with `mkiocccentry`!
If later on you log in and see something like: If, however, the slot status shows:
> **Status: server slot error code: 1! Use mkiocccentry to rebuild and resubmit to > **Status: file successfully uploaded into slot.**
this slot.**
or: Then you are successfully uploaded a file into the slot.
At this point you may upload another submission file into a different slot, or you're done, log out.
**Please note:** The status page will **NOT** auto-refresh. After you are uploaded a file into a slot, **DO NOT RELOAD**
the page as this may cause your browser to needlessly reload the same file to the same slot.
After you fir finished uploading submissions into slots, please logout.
To see any status updates, you should logout and log back in later.
## Checking on the status of your submission
You may check on the status of your submission later on, after you logout by logging back in an looking at the slot status.
**Please note:** The status page will **NOT** auto-refresh.
When the system begins to process your file (which could be an hour or two later), you might see:
> **Status: file fetched. The format test is pending.**
After the format test is complete, if you see an error such as:
> **Status: submit file failed the txzchk test! Use mkiocccentry to rebuild and resubmit to this slot.** > **Status: submit file failed the txzchk test! Use mkiocccentry to rebuild and resubmit to this slot.**
... or **ANY OTHER ERROR** then you **MUST FIX** your submission, repackage your Or:
> **Status: submit file failed the chkentry test! Use mkiocccentry to rebuild and resubmit to this slot.**
... or **ANY** other error then you **MUST FIX** your submission, repackage your
tarball with `mkiocccentry` and upload to the same slot again! If you do not fix tarball with `mkiocccentry` and upload to the same slot again! If you do not fix
this your submission **WILL BE REJECTED** for violating [Rule this your submission **WILL BE REJECTED** for violating [Rule
17](rules.html#rule17)! 17](rules.html#rule17)!
After the submission deadline is reached, you can log in to check the status of If the format test went well, then you will see:
your submissions. This is what it will say when the judges have verified
that your tarball / submission has been validated (NOT judged), by `txzchk(1)`
and `chkentry(1)`:
> **Status: the format of this submission has been validated.** > **Status: submit file received by the IOCCC judges. Passed both txzchk and chkentry tests.**
**IMPORTANT**: this does **NOT** mean that your submission does not violate the **IMPORTANT**: this does **NOT** mean that your submission does not violate the
rules or that everything is OK once the tarball is extracted; it simply means rules or that everything is OK once the tarball is extracted; it simply means
+6 -6
View File
@@ -14794,7 +14794,7 @@
</url> </url>
<url> <url>
<loc>https://www.ioccc.org/author/John_Dalbec.json</loc> <loc>https://www.ioccc.org/author/John_Dalbec.json</loc>
<lastmod>2025-01-10T06:06:40+00:00</lastmod> <lastmod>2025-03-03T20:50:17+00:00</lastmod>
</url> </url>
<url> <url>
<loc>https://www.ioccc.org/author/John_Tromp.json</loc> <loc>https://www.ioccc.org/author/John_Tromp.json</loc>
@@ -15070,7 +15070,7 @@
</url> </url>
<url> <url>
<loc>https://www.ioccc.org/authors.html</loc> <loc>https://www.ioccc.org/authors.html</loc>
<lastmod>2025-01-30T20:14:05+00:00</lastmod> <lastmod>2025-03-03T20:50:17+00:00</lastmod>
</url> </url>
<url> <url>
<loc>https://www.ioccc.org/author/Sjoerd_Mullender.json</loc> <loc>https://www.ioccc.org/author/Sjoerd_Mullender.json</loc>
@@ -15414,11 +15414,11 @@
</url> </url>
<url> <url>
<loc>https://www.ioccc.org/faq.html</loc> <loc>https://www.ioccc.org/faq.html</loc>
<lastmod>2025-03-02T21:52:21+00:00</lastmod> <lastmod>2025-03-03T20:50:17+00:00</lastmod>
</url> </url>
<url> <url>
<loc>https://www.ioccc.org/faq.md</loc> <loc>https://www.ioccc.org/faq.md</loc>
<lastmod>2025-03-02T21:48:49+00:00</lastmod> <lastmod>2025-03-03T20:50:17+00:00</lastmod>
</url> </url>
<url> <url>
<loc>https://www.ioccc.org/inc/index.html</loc> <loc>https://www.ioccc.org/inc/index.html</loc>
@@ -15450,11 +15450,11 @@
</url> </url>
<url> <url>
<loc>https://www.ioccc.org/location.html</loc> <loc>https://www.ioccc.org/location.html</loc>
<lastmod>2025-02-13T00:27:53+00:00</lastmod> <lastmod>2025-03-03T21:02:38+00:00</lastmod>
</url> </url>
<url> <url>
<loc>https://www.ioccc.org/Makefile</loc> <loc>https://www.ioccc.org/Makefile</loc>
<lastmod>2025-03-01T21:03:38+00:00</lastmod> <lastmod>2025-03-03T20:50:17+00:00</lastmod>
</url> </url>
<url> <url>
<loc>https://www.ioccc.org/news.html</loc> <loc>https://www.ioccc.org/news.html</loc>