From: Tomas Volf <wolf@wolfsden.cz>
To: Hiep Pham <hiepph9@proton.me>
Cc: help-guix@gnu.org
Subject: Re: How to bump a package version locally?
Date: Fri, 20 Oct 2023 01:39:28 +0200 [thread overview]
Message-ID: <ZTG-MMhT879oBoz4@ws> (raw)
In-Reply-To: <c3f39e82-61b8-4480-9127-92d254623517@proton.me>
[-- Attachment #1: Type: text/plain, Size: 3448 bytes --]
On 2023-10-19 16:47:13 +0000, Hiep Pham wrote:
> On 10/18/23 21:00, wolf wrote:
> > On 2023-10-18 18:24:48 +0000, Hiep Pham wrote:
> >> Hi,
> >>
> >> I want to bump `jsonnet` version from 0.17.0 to 0.20.0 from the master
> >> branch of the `guix` repository. I edited the version in
> >> `gnu/packages/cpp.scm`:
> >>
> >> (define-public jsonnet
> >> (package
> >> (name "jsonnet")
> >> (version "0.20.0")
> >> [snip]
> >> ))
> > [trim]
> >>
> >> 2. Followed the contributing guide [1], I created a shell instead:
> >
> > I believe this is the preferred way.
> >
> >>
> >> guix shell -C -D guix git help2man strace
> >> ./bootstrap
> >> ./configure --localstatedir=/var
> >
> > I would recommend to use
> >
> > ./configure --localstatedir=/var --sysconfdir=/etc
> >
> > as described in the latest version of the manual:
> >
> > https://guix.gnu.org/manual/devel/en/html_node/Building-from-Git.html
> >
> > (notice the /devel/ in the path). Your version is from 1.4.0 version of the
> > manual and it has some limitations.
>
> Okay, so I followed exactly this, and ...
>
> >>
> >> This generated `pre-inst-env`, but `make` step failed with:
> >>
> >> ```
> >> MAKEINFO doc/guix.de.info
> >> contributing.de.texi:1659: @menu reference to nonexistent node
> >> `Configuring Git'
> >> contributing.de.texi:1660: @menu reference to nonexistent node `Sending
> >> a Patch Series'
> >> make[2]: *** [Makefile:5003: doc/guix.de.info] Error 1
> >> ```
> >
> > Yes, this happens when you try to build guix source using too old guix version.
> > So try to run `guix pull' first and then attempt to compile it again. It should
> > succeed.
>
>
> I ran `guix pull` but no luck for me. I still met the same error when I
> was running `make`:
What version of makeinfo is present? For me:
$ guix shell -D guix -- makeinfo --version
texi2any (GNU texinfo) 6.8
>
> ```
> contributing.de.texi:1659: @menu reference to nonexistent node
> `Configuring Git'
> contributing.de.texi:1660: @menu reference to nonexistent node `Sending
> a Patch Series'
> ```
>
> My `guix describe` (on my Fedora machine):
>
> ```
> guix c065da0
> repository URL: https://git.savannah.gnu.org/git/guix.git
> branch: master
> commit: c065da01ff956d3c2bdfc45a33d910e509a211d9
> ```
>
> c065da01ff956d3c2bdfc45a33d910e509a211d9 is the latest commit on Oct 19,
> 2023.
>
> And my `which guix` is:
>
> /home/[username]/.config/guix/current/bin/guix
I have to admit, I am unsure what the problem exactly is. Unless someone else
comes with a better idea, what you could try:
1. Clean up the git worktree (I use `git clean -xffd')
2. Do the whole process step-by-step again
3. Send here the full output (commands executed and their output); also include
both guix describe output and git commit of the guix repository you are on
Maybe there will be more ideas based on that. Sorry I cannot be of more use.
>
> >>
> >> So I was blocked to progress further :(
> >>
> >
> > After that the pre-inst-env should work.
> >
> >>
> >> [1] https://guix.gnu.org/manual/en/guix.html#Contributing
> >>
> >> --
> >> Hiep
> >>
> >>
> >
> > W.
> >
>
> --
> Hiep
>
>
>
W.
--
There are only two hard things in Computer Science:
cache invalidation, naming things and off-by-one errors.
[-- Attachment #2: signature.asc --]
[-- Type: application/pgp-signature, Size: 833 bytes --]
next prev parent reply other threads:[~2023-10-19 23:40 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-10-18 18:24 How to bump a package version locally? Hiep Pham
2023-10-18 19:00 ` wolf
2023-10-19 16:47 ` Hiep Pham
2023-10-19 23:39 ` Tomas Volf [this message]
2023-10-21 19:20 ` Hiep Pham
2023-10-20 13:15 ` Simon Tournier
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
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=ZTG-MMhT879oBoz4@ws \
--to=wolf@wolfsden.cz \
--cc=help-guix@gnu.org \
--cc=hiepph9@proton.me \
/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 external index
https://git.savannah.gnu.org/cgit/guix.git
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.