unofficial mirror of guix-patches@gnu.org 
 help / color / mirror / code / Atom feed
From: Julien Lepiller <julien@lepiller.eu>
To: 51358@debbugs.gnu.org
Subject: [bug#51358] [PATCH] Getting rid of some ocaml4.07-* packages.
Date: Sat, 23 Oct 2021 19:52:12 +0200	[thread overview]
Message-ID: <20211023195212.4baaee5e@tachikoma.lepiller.eu> (raw)

Hi Guix! this small patch series is a step forward to removing ocaml4.07
packages. There are a few leaf packages that still depend on ocaml
4.07, and this series takes care of fftw3, by building it with our
latest ocaml package (4.11, even though 4.13 is out; wip...).

The last patch is a bit messy. I didn't want to change to much from it,
but its source is no longer available. When testing the patch, guix was
able to use disarchive to get the content from SWH, but after a GC, and
one day, I am no longer able to download the sources. I know of the new
place, should I use it instead?

Trying to use Disarchive to assemble
/gnu/store/jxqnv4y2gyccsfhlbf1n7s5vn1rqgvxc-ocaml-charinfo-width-1.1.0.tar.gz...
Assembling the directory ocaml4.07-charinfo-width-1.1.0 Downloading
/gnu/store/jxqnv4y2gyccsfhlbf1n7s5vn1rqgvxc-ocaml-charinfo-width-1.1.0.tar.gz
from Software Heritage... tar extraction failure 32512 Could not
resolve directory reference failed to download
"/gnu/store/jxqnv4y2gyccsfhlbf1n7s5vn1rqgvxc-ocaml-charinfo-width-1.1.0.tar.gz"
from "https://bitbucket.org/zandoye/charinfo_width/get/1.1.0.tar.gz"
builder for
`/gnu/store/hshfvzxby5cfwmd5fzn8w82pxj525xjr-ocaml-charinfo-width-1.1.0.tar.gz.drv'
failed to produce output path
`/gnu/store/jxqnv4y2gyccsfhlbf1n7s5vn1rqgvxc-ocaml-charinfo-width-1.1.0.tar.gz'




             reply	other threads:[~2021-10-23 17:53 UTC|newest]

Thread overview: 18+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2021-10-23 17:52 Julien Lepiller [this message]
2021-10-23 17:58 ` [bug#51358] [PATCH 1/4] gnu: Add ocaml-lacaml Julien Lepiller
2021-10-25 13:56   ` [bug#51358] [PATCH] Getting rid of some ocaml4.07-* packages zimoun
2021-10-25 22:05     ` Julien Lepiller
2021-10-25 22:06       ` [bug#51358] [PATCH 1/4] gnu: Add ocaml-lacaml Julien Lepiller
2021-10-27 13:39         ` [bug#51358] [PATCH] Getting rid of some ocaml4.07-* packages zimoun
2021-10-27 15:27           ` Julien Lepiller
2021-11-15 13:10             ` zimoun
2021-11-20 18:56               ` bug#51358: " Julien Lepiller
2021-11-22  9:14                 ` [bug#51358] " zimoun
2021-11-22 19:40                   ` Ricardo Wurmus
2021-10-25 22:06       ` [bug#51358] [PATCH 2/4] gnu: Add ocaml-fftw3 Julien Lepiller
2021-10-25 22:06       ` [bug#51358] [PATCH 3/4] gnu: Add ocaml-gsl Julien Lepiller
2021-10-25 22:06       ` [bug#51358] [PATCH 4/4] gnu: Add ocaml-charinfo-width Julien Lepiller
2021-11-15 12:45         ` zimoun
2021-10-23 17:58 ` [bug#51358] [PATCH 2/4] gnu: Add ocaml-fftw3 Julien Lepiller
2021-10-23 17:58 ` [bug#51358] [PATCH 3/4] gnu: Add ocaml-gsl Julien Lepiller
2021-10-23 17:58 ` [bug#51358] [PATCH 4/4] gnu: Add ocaml-charinfo-width Julien Lepiller

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=20211023195212.4baaee5e@tachikoma.lepiller.eu \
    --to=julien@lepiller.eu \
    --cc=51358@debbugs.gnu.org \
    /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).