Your message dated Sat, 13 Feb 2021 13:22:12 +0000
with message-id <[email protected]>
and subject line Bug#949400: Removed package(s) from unstable
has caused the Debian Bug report #734311,
regarding guild assumes too much about guile config
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.)


-- 
734311: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=734311
Debian Bug Tracking System
Contact [email protected] with problems
--- Begin Message ---
Package: guile-2.0-libs
Version: 2.0.9+1-1
Severity: minor

/usr/bin/guild from guile-2.0-libs begins with some shell code that by
default passes the main Scheme program to /usr/bin/guile.  The main
program then relies on a bunch of libraries that are part of the
guile-2.0-libs package and which are installed under /usr/share/guile/2.0,
hence made available specifically to guile-2.0.  If /usr/bin/guile, which
is controlled by the alternatives system, doesn't refer to guile-2.0,
guild is liable to fail:

$ namei /usr/bin/guile
f: /usr/bin/guile
 d /
 d usr
 d bin
 l guile -> /etc/alternatives/guile
   d /
   d etc
   d alternatives
   l guile -> /usr/bin/guile-1.8
     d /
     d usr
     d bin
     - guile-1.8
$ /usr/bin/guild list
ERROR: no code for module (ice-9 command-line)

guild should (by default, at least) invoke /usr/bin/guile-2.0, rather
than /usr/bin/guile.  This implies that the package containing guild
ought to declare a dependency on the guile-2.0 package, but that poses
a bit of a problem, as the guile-2.0 package declares a dependency on
guile-2.0-libs, which is what contains guild.  Perhaps guild ought to
be in a separate package from the libraries.

The immediate workaround for this problem is to run guild with
GUILE=/usr/bin/guile-2.0 in the environment.  While this configurability
is handy right now in working around the bug, it doesn't seem a good
idea for guild to accept such advice from the environment.  Presumably
$GUILE, if set, would normally point to the user's preferred guile,
which, like /usr/bin/guile, is not necessarily the one that guild needs.
As guild specifically needs guile-2.0, and it knows that if guile-2.0 is
available then it'll specifically be available as /usr/bin/guile-2.0, it
would seem more sensible for guild to unconditionally and unconfigurably
use /usr/bin/guile-2.0.

-zefram

--- End Message ---
--- Begin Message ---
Version: 2.0.13+1-5.4+rm

Dear submitter,

as the package guile-2.0 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/949400

The version of this package that was in Debian prior to this removal
can still be found using http://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.
Joerg Jaspert (the ftpmaster behind the curtain)

--- End Message ---

Reply via email to