Re: Getting rid of "source file [...] newer than compiled" messages

[Katherine Cox-Buday]

Ricardo Wurmus <address@hidden> writes:

> Oh, well, that’s definitely not right.  Guix does not download
> individual files when fetching packages — it downloads archives that
> definitely do contain the .go files.  So the question is… where did they
> go once “guix pull” finished?

Yeah, I don't know! Mostly I'm trying to dig into this edge-case of
trying to get malformed packages back into a known state. I imagine that
will come up from time to time on users' machines, for various reasons.

> Does “guix gc --verify=repair,contents” (run as root) really not tell
> you anything useful?

Here is the output, verbatim:

#+BEGIN_EXAMPLE
  sudo guix gc --verify=repair,contents
  Password: 
  guile: warning: failed to install locale
  ;;; note: source file 
/gnu/store/cd6rjv3qhhghr59wpq4fksfr84d5dsdf-guix-module-union/share/guile/site/2.2/gcrypt/hash.scm
  ;;;       newer than compiled 
/gnu/store/cd6rjv3qhhghr59wpq4fksfr84d5dsdf-guix-module-union/lib/guile/2.2/site-ccache/gcrypt/hash.go
  ;;; note: source file 
/gnu/store/cd6rjv3qhhghr59wpq4fksfr84d5dsdf-guix-module-union/share/guile/site/2.2/gcrypt/common.scm
  ;;;       newer than compiled 
/gnu/store/cd6rjv3qhhghr59wpq4fksfr84d5dsdf-guix-module-union/lib/guile/2.2/site-ccache/gcrypt/common.go
  ;;; note: source file 
/gnu/store/cd6rjv3qhhghr59wpq4fksfr84d5dsdf-guix-module-union/share/guile/site/2.2/gcrypt/package-config.scm
  ;;;       newer than compiled 
/gnu/store/cd6rjv3qhhghr59wpq4fksfr84d5dsdf-guix-module-union/lib/guile/2.2/site-ccache/gcrypt/package-config.go
  ;;; note: source file 
/gnu/store/cd6rjv3qhhghr59wpq4fksfr84d5dsdf-guix-module-union/share/guile/site/2.2/gcrypt/utils.scm
  ;;;       newer than compiled 
/gnu/store/cd6rjv3qhhghr59wpq4fksfr84d5dsdf-guix-module-union/lib/guile/2.2/site-ccache/gcrypt/utils.go
  reading the store...
  checking path existence...
  checking hashes...

  Some deprecated features have been used.  Set the environment
  variable GUILE_WARN_DEPRECATED to "detailed" and rerun the
  program to get more information.  Set it to "no" to suppress
  this message.
#+END_EXAMPLE

So, unfortunately not :( And these messages continue. As a user, I would
have definitely expected this command to have found an issue.

-- 
Katherine