Re: Question about changing versioning for TeX Live packages

[Development of GNU Guix and the GNU System distribution.]

Hello,

Simon Tournier  writes:

> Well, if I read correctly, there is:
>
>   guix/build-system/texlive.scm:
>
> (define %texlive-tag "texlive-2023.0")
> (define %texlive-revision 66594)
>
>   gnu/packages/texlive.scm:
>
> (define %texlive-date "20230313")
> (define %texlive-year (string-take %texlive-date 4))
>
>
> And the issue seems:
>
> (define-public texlive
>(package
> (name "texlive")
> (version %texlive-date)

This is the monolithic TeX Live, which is not modified, and is therefore
off topic.

> (define-public texlive-scripts
>   (package
> (name "texlive-scripts")
> (version (number->string %texlive-revision))
>
>
> Therefore, indeed it will be complicated to replace the ’version’ of
> ’texlive-scripts’ by something as ’2023’.
>
> But why not a ’version’ as something as ’texlive’?  Or just 2023XY?
> Where XY is something to determine as the month or something else.

Upstream uses version numbers such as "2024.2". I don't want to invent
another system.

> Are we speaking a change only for the package field ’version’?  Or is
> the discussion also about replacing the way to fetch from upstream?

I'm only changing the `version' field. For the record, "core-updates"
currently contains all TeX Live packages with their version switched to
"2024.2". In the worst case, maybe a notice in the guix news will be
sufficient.

Regards,
-- 
Nicolas Goaziou

Re: Value in adding Shepherd requirements to file-systems entries?

[Development of GNU Guix and the GNU System distribution.]

Hi Richard,

On Fri, Jun 07 2024, Richard Sent wrote:

> you are using avahi-daemon as a shepherd-requirements entry in your
> current code and not networking right?

Yes, here is my current stanza, which I adjusted after I received the
merged version of your patch:

--8<---cut here---start->8---
  (file-system
(device "wallace-server.local:/acct")
(mount-point "/acct")
(type "nfs")
(shepherd-requirements '(avahi-daemon)) ;resolve .local
;; (flags '(no-atime no-dev no-exec read-only))
;; (options "proto=tcp6,timeo=300,nolock")
(check? #f)
(mount-may-fail? #t)
(create-mount-point? #t))
--8<---cut here---end--->8---

I can use the the /etc/fstab manually with

mount /acct

> You could try invoking mount-file-system from (gnu build file-systems)
> directly to try and narrow down what exactly is breaking.

I have never used the Guix REPL.  Should I try that as the root user
immediately after booting?

Kind regards & thanks!
Felix