unofficial mirror of bug-guix@gnu.org 
 help / color / mirror / code / Atom feed
From: Christopher Baines <mail@cbaines.net>
To: Artyom Poptsov <poptsov.artyom@gmail.com>
Cc: 64872@debbugs.gnu.org
Subject: bug#64872: guix pull: po4a: build failed
Date: Wed, 26 Jul 2023 18:12:17 +0100	[thread overview]
Message-ID: <87zg3i61ff.fsf@cbaines.net> (raw)
In-Reply-To: <CAN9MppvQ=cy07wq61jZ4yDrHW=L4ZXssfqKwGjRLy0Ti9MSkYA@mail.gmail.com>

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


Artyom Poptsov <poptsov.artyom@gmail.com> writes:

> Huh, it seems that the problem not in "po4a" itself but in
> "texlive-hyphen-complete".
>
> When I try to access
>   https://www.tug.org/texlive/tags/texlive-2023.0/Master/texmf-dist//doc/generic/elhyphen
> I get 404 error.

Ok, well maybe try building
/gnu/store/g9xfx06xs21jnrsg7h42m5ggfg2zfdfg-texlive-hyphen-complete-66594-checkout.drv
and post the log.

Since quite recently, the subversion downloads should fallback to
talking to bordeaux.guix.gnu.org, which should be able to provide a nar
for this, even if you get a 404 from www.tug.org, but it would be good
to see if that is attempted.

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

  reply	other threads:[~2023-07-26 18:13 UTC|newest]

Thread overview: 11+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2023-07-26 13:57 bug#64872: guix pull: po4a: build failed Artyom Poptsov
2023-07-26 15:07 ` Christopher Baines
2023-07-26 16:15   ` Artyom Poptsov
2023-07-26 17:12     ` Christopher Baines [this message]
2023-07-28  9:02       ` bug#64872: guix pull: texlive-hyphen-complete: build failed (was: "guix pull: po4a: build failed") Artyom Poptsov
2023-07-28  9:42         ` Christopher Baines
2023-07-28 10:24           ` Artyom Poptsov
2023-07-28 10:29             ` Artyom Poptsov
2023-07-28 17:16               ` Christopher Baines
2023-08-04  7:01                 ` Artyom Poptsov
2023-08-13  8:04                   ` Christopher Baines

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=87zg3i61ff.fsf@cbaines.net \
    --to=mail@cbaines.net \
    --cc=64872@debbugs.gnu.org \
    --cc=poptsov.artyom@gmail.com \
    /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).