unofficial mirror of bug-guix@gnu.org 
 help / color / mirror / code / Atom feed
From: Matthew James Kraai <kraai@ftbfs.org>
To: Josselin Poiret <dev@jpoiret.xyz>
Cc: Julien Lepiller <julien@lepiller.eu>, 62332-done@debbugs.gnu.org
Subject: bug#62332: error: java-eclipse-aether-Api: unbound variable
Date: Wed, 22 Mar 2023 05:19:27 -0700	[thread overview]
Message-ID: <ZBryT2wBeYXb9aVE@carlo> (raw)
In-Reply-To: <87sfdyq6jn.fsf@jpoiret.xyz>

Hi,

On Tue, Mar 21, 2023 at 07:54:20PM +0100, Josselin Poiret wrote:
> Julien Lepiller <julien@lepiller.eu> writes:
> 
> > How weird, I don't see it spelled like that in the repository (latest master). I don't see any recent change in the file either.
> >
> > Maybe there's an issue with your local checkout.
> > Guix has a checkout of the repository in one of the directories of ~/.cache/guix/checkouts. You should be able to locate it from its contents. What's the output of "git status" and "git diff"?
> >
> > If there's tome change, you could try "git checkout ." to reset the repo to its original state.
> 
> A stronger `git clean -dfv .` might be necessary to remove any stray
> files as well.

Thank you both for the suggestions.  The Guix checkout on my system is

~/.cache/guix/checkouts/pjmkglp4t7znuugeurpurzikxq3tnlaywmisyr27shj7apsnalwq

`git status` output

```
On branch master
Your branch is up to date with 'origin/master'.

nothing to commit, working tree clean
```

`git diff` didn't output anything.

`git clean -dfv .` said that `error: unknown switch `v'`, but after I
ran `git clean -dfx .`, `guix pull` succeeded!

-- 
Matt




      reply	other threads:[~2023-03-22 12:20 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2023-03-21 13:51 bug#62332: error: java-eclipse-aether-Api: unbound variable Matthew James Kraai
2023-03-21 17:03 ` Julien Lepiller
2023-03-21 18:54   ` Josselin Poiret via Bug reports for GNU Guix
2023-03-22 12:19     ` Matthew James Kraai [this message]

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=ZBryT2wBeYXb9aVE@carlo \
    --to=kraai@ftbfs.org \
    --cc=62332-done@debbugs.gnu.org \
    --cc=dev@jpoiret.xyz \
    --cc=julien@lepiller.eu \
    /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).