GNU bug report logs - #52927
[PATCH] gnu: tup: Update to 0.7.11.

Previous Next

Package: guix-patches;

Reported by: Morgan.J.Smith <at> outlook.com

Date: Sat, 1 Jan 2022 04:46:02 UTC

Severity: normal

Tags: patch

Done: Morgan Smith <Morgan.J.Smith <at> outlook.com>

Bug is archived. No further changes may be made.

To add a comment to this bug, you must first unarchive it, by sending
a message to control AT debbugs.gnu.org, with unarchive 52927 in the body.
You can then email your comments to 52927 AT debbugs.gnu.org in the normal way.

Toggle the display of automated, internal messages from the tracker.

View this report as an mbox folder, status mbox, maintainer mbox


Report forwarded to guix-patches <at> gnu.org:
bug#52927; Package guix-patches. (Sat, 01 Jan 2022 04:46:02 GMT) Full text and rfc822 format available.

Acknowledgement sent to Morgan.J.Smith <at> outlook.com:
New bug report received and forwarded. Copy sent to guix-patches <at> gnu.org. (Sat, 01 Jan 2022 04:46:02 GMT) Full text and rfc822 format available.

Message #5 received at submit <at> debbugs.gnu.org (full text, mbox):

From: Morgan.J.Smith <at> outlook.com
To: guix-patches <at> gnu.org
Cc: Morgan Smith <Morgan.J.Smith <at> outlook.com>
Subject: [PATCH] gnu: tup: Update to 0.7.11.
Date: Fri, 31 Dec 2021 23:14:32 -0500
From: Morgan Smith <Morgan.J.Smith <at> outlook.com>

* gnu/packages/build-tools.scm (tup): Update to 0.7.11.
[phases]<configure,build>: Force it to use fuse instead of fuse3
---

There is probably a cleaner way to do that format thingy.  I just can't be asked to figure that out right now, sorry.  This package gave me to much grief to go the extra mile :P


Wanted to play with this as it seems cool but I kept getting this error when running it:

> setpgid: Operation not permitted
> tup error: Unable to set process group for tup's subprocesses.

So then I updated it to 0.7.11 (changed fuse to fuse-3), built it just fine, and got this error instead when running it:

> fuse: failed to exec fusermount3: No such file or directory

I tried pretty hard to fix it but I couldn't figure it out.  It's pretty darn cryptic.  I can't figure out where it's trying to call it from.  So I just built it with fuse instead of fuse3 and now everything works great.  No errors at all.

 gnu/packages/build-tools.scm | 9 +++++----
 1 file changed, 5 insertions(+), 4 deletions(-)

diff --git a/gnu/packages/build-tools.scm b/gnu/packages/build-tools.scm
index 9d3fd5171e..1838e9ce7a 100644
--- a/gnu/packages/build-tools.scm
+++ b/gnu/packages/build-tools.scm
@@ -409,14 +409,14 @@ (define-public premake5
 (define-public tup
   (package
     (name "tup")
-    (version "0.7.9")
+    (version "0.7.11")
     (source (origin
               (method url-fetch)
               (uri (string-append "http://gittup.org/tup/releases/tup-v"
                                   version ".tar.gz"))
               (sha256
                (base32
-                "0gnd2598xqgwihdkfkx7qn0q6p4n7npam1fy83mp7s04zwj99syc"))
+                "1157qfnhjakm3h07y7h38lrjw5650gkif34k30bnrsypmwl5xyzb"))
               (patches (search-patches "tup-unbundle-dependencies.patch"))
               (modules '((guix build utils)))
               (snippet
@@ -439,12 +439,13 @@ (define-public tup
                (("`git describe`") ,version))
              (with-output-to-file "tup.config"
                (lambda _
-                 (format #t "CONFIG_TUP_USE_SYSTEM_SQLITE=y~%")))
-             #t))
+                 ;; Use fuse instead of fuse3 (won't run with fuse3 for some reason)
+                 (format #t "CONFIG_TUP_USE_SYSTEM_SQLITE=y\nCONFIG_TUP_SERVER=fuse~%")))))
          (delete 'check)
          (replace 'build
            (lambda _
              ;; Based on bootstrap-nofuse.sh, but with a detour to patch-shebang.
+             (setenv "TUP_SERVER" "fuse") ;; Use fuse instead of fuse3
              (invoke "./build.sh")
              (invoke "./build/tup" "init")
              (invoke "./build/tup" "generate" "--verbose" "build-nofuse.sh")
-- 
2.34.0





Information forwarded to guix-patches <at> gnu.org:
bug#52927; Package guix-patches. (Sat, 01 Jan 2022 18:57:02 GMT) Full text and rfc822 format available.

Message #8 received at 52927 <at> debbugs.gnu.org (full text, mbox):

From: Morgan Smith <Morgan.J.Smith <at> outlook.com>
To: 52927 <at> debbugs.gnu.org
Subject: Re: bug#52927: [PATCH] gnu: tup: Update to 0.7.11.
Date: Sat, 01 Jan 2022 13:56:29 -0500
Morgan.J.Smith <at> outlook.com writes:
>> fuse: failed to exec fusermount3: No such file or directory

Well it has been a year so I thought I'd come back to this.  I figured
it out.  It needs to run fusermount from /run/setuid-programs because it
needs those permissions I guess.  So running this program depends on the
user's system configuration which I don't think is a good thing (and
probably translates badly on foreign distros.)

If I could get someone more knowledgeable then me to weigh in here that
would be great because I have no clue how to proceed.

If I install fuse-3 alongside tup built with fuse-3 then I get the
following error.  If fuse-3 is installed as a setuid program it works
perfectly.  The only reason everything currently works is because we
install fuse by default as a setuid program.

> fusermount3: mount failed: Operation not permitted




bug closed, send any further explanations to 52927 <at> debbugs.gnu.org and Morgan.J.Smith <at> outlook.com Request was from Morgan Smith <Morgan.J.Smith <at> outlook.com> to control <at> debbugs.gnu.org. (Wed, 14 Jun 2023 18:50:01 GMT) Full text and rfc822 format available.

bug archived. Request was from Debbugs Internal Request <help-debbugs <at> gnu.org> to internal_control <at> debbugs.gnu.org. (Thu, 13 Jul 2023 11:24:08 GMT) Full text and rfc822 format available.

This bug report was last modified 280 days ago.

Previous Next


GNU bug tracking system
Copyright (C) 1999 Darren O. Benham, 1997,2003 nCipher Corporation Ltd, 1994-97 Ian Jackson.