Your message dated Tue, 06 Oct 2026 07:13:25 +0000 with message-id <[email protected]> and subject line Bug#1121731: Removed package(s) from unstable has caused the Debian Bug report #1064446, regarding confused by changing absolute pathname to be marked as done.
This means that you claim that the problem has been dealt with. If this is not the case it is now your responsibility to reopen the Bug report if necessary, and/or fix the problem forthwith. (NB: If you are a system administrator and have no idea what this message is talking about, this may indicate a serious mail system misconfiguration somewhere. Please contact [email protected] immediately.) -- 1064446: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1064446 Debian Bug Tracking System Contact [email protected] with problems
--- Begin Message ---Package: guile-2.2 Version: 2.2.7+1-6 Severity: normal The guile-2.2(1) command-line interface is documented to take the filename of a script to execute. Here's how well it resolves filenames: $ mkdir a $ cd a $ echo '(display "ok") (newline)' > ok.scm $ perl -e 'chdir ".."; while(1) { rename("a", "b"); rename("b", "a"); }' & [1] 390457 $ guile-2.2 --no-auto-compile ok.scm ok $ guile-2.2 --no-auto-compile ok.scm Backtrace: 0 (primitive-load "/home/zefram/tmp/g0/b/ok.scm") ERROR: In procedure primitive-load: In procedure open-file: No such file or directory: "/home/zefram/tmp/g0/b/ok.scm" $ guile-2.2 --no-auto-compile ok.scm Backtrace: 0 (primitive-load "/home/zefram/tmp/g0/a/ok.scm") ERROR: In procedure primitive-load: In procedure open-file: No such file or directory: "/home/zefram/tmp/g0/a/ok.scm" $ guile-2.2 --no-auto-compile ok.scm ;;; Stat of /home/zefram/tmp/g0/b/ok.scm failed: ;;; In procedure stat: No such file or directory: "/home/zefram/tmp/g0/b/ok.scm" ok $ guile-2.2 --no-auto-compile ok.scm ok Each time that I invoked guile-2.2(1), the filename "ok.scm" given on the command line unambiguously referred to an extant script file in the current directory. Some invocations successfully ran it, but others got confused. The confused invocations either entirely fail to run the script, or produce some extra stderr noise and then run the script. guile-2.2(1) is getting confused because the absolute pathname of the current directory is changing. It works out an absolute pathname for the specified script, and then tries to use that at a time when it may be stale. The manifestation of the bug varies from run to run because it is subject to this race condition. I use the --no-auto-compile option in my example in order to avoid the extra noise of guile's caching system. If caching is allowed to occur then similar results ensue, but there's extra stderr noise that doesn't indicate a real problem, and the situation is semantically a bit more complicated because of the caching. guile-2.2(1) shouldn't need to use an absolute pathname for the script file. The name given on the command line should be used; relative pathnames should work. -zefram
--- End Message ---
--- Begin Message ---Version: 2.2.7+1-9+rm Dear submitter, as the package guile-2.2 has just been removed from the Debian archive unstable we hereby close the associated bug reports. We are sorry that we couldn't deal with your issue properly. For details on the removal, please see https://bugs.debian.org/1121731 The version of this package that was in Debian prior to this removal can still be found using https://snapshot.debian.org/. Please note that the changes have been done on the master archive and will not propagate to any mirrors until the next dinstall run at the earliest. This message was generated automatically; if you believe that there is a problem with it please contact the archive administrators by mailing [email protected]. Debian distribution maintenance software pp. Thorsten Alteholz (the ftpmaster behind the curtain)
--- End Message ---
