unofficial mirror of bug-guix@gnu.org 
 help / color / mirror / code / Atom feed
From: "Dr. Arne Babenhauserheide" <arne_bab@web.de>
To: Maxime Devos <maximedevos@telenet.be>
Cc: 53204@debbugs.gnu.org
Subject: bug#53204: [patch] font-cns11643: Open_Data hash changed
Date: Wed, 12 Jan 2022 12:41:42 +0100	[thread overview]
Message-ID: <87v8ypdvp0.fsf@web.de> (raw)
In-Reply-To: <b259b0327cdb8f64cc03ad4368948b9890ad27b8.camel@telenet.be>

[-- Attachment #1: Type: text/plain, Size: 680 bytes --]


Maxime Devos <maximedevos@telenet.be> writes:

> Given that Open_Data.zip has a history of being modified in-place,
> maybe it would be a good idea to use the Internet Archive Machine instead?

That sounds good, yes.

> Latest version current in the archive: 
> https://web.archive.org/web/20211004150815/http://www.cns11643.gov.tw/AIDB/Open_Data.zip
>
> On <https://web.archive.org/save/http://www.cns11643.gov.tw/AIDB/Open_Data.zip>,
> I requested a fresh archival, but it will take some time to complete.

Thank you! 

Will you get an info when it’s done?

Best wishes,
Arne
-- 
Unpolitisch sein
heißt politisch sein,
ohne es zu merken.
draketo.de

[-- Attachment #2: signature.asc --]
[-- Type: application/pgp-signature, Size: 1125 bytes --]

  parent reply	other threads:[~2022-01-12 12:06 UTC|newest]

Thread overview: 11+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2022-01-12  8:54 bug#53204: [patch] font-cns11643: Open_Data hash changed Dr. Arne Babenhauserheide
2022-01-12 10:45 ` Maxime Devos
2022-01-12 11:13   ` Maxime Devos
2022-01-12 11:41   ` Dr. Arne Babenhauserheide [this message]
2022-01-12 12:18     ` Maxime Devos
2022-01-31  1:59 ` bug#53204: [patch] font-cns11643: ... unzip error Brendan Tildesley
2022-01-31  9:18   ` Maxime Devos
2022-01-31 11:23     ` Brendan Tildesley
2022-01-31 12:35       ` Maxime Devos
2022-02-01  1:23         ` Brendan Tildesley
2022-10-09  6:38 ` bug#53204: [patch] font-cns11643: Open_Data hash changed Brendan Tildesley

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

  List information: https://guix.gnu.org/

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=87v8ypdvp0.fsf@web.de \
    --to=arne_bab@web.de \
    --cc=53204@debbugs.gnu.org \
    --cc=maximedevos@telenet.be \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
Code repositories for project(s) associated with this public inbox

	https://git.savannah.gnu.org/cgit/guix.git

This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).