date:20171112

Re: how to install from binary

2017-11-12 Thread Thomas Sigurdsen

Hello, there has been a long thread recently clarifying a lot around
guix, builds and substitutions. Explore the thread for lots of clarifying
info:
https://lists.gnu.org/archive/html/help-guix/2017-11/msg9.html

But in short summary: Guix is a build from source system and the substitutes
are possible and sometime available because of the functional aspect. As I
understand it, the substitutes are often (and randomly) not available because
of difficulty of scheduling and storage on the build farm (hydra). So guix
will often build things, even if you want substitutes.

Take my word with a grain of salt. And Welcome!

  :)

On Sun, 12 Nov 2017 14:30:36 -0800
Mason Hock  wrote:

> Guix seems to be building everything from source, which can take a
> while. As per these instructions I tried
> 
> # cd [prefix]/share/guix/hydra.gnu.org.pub
> # guix archive --authorize < hydra.gnu.org.pub
> and got
> 
> guile: warning: failed to install locale
> warning: failed to install locale: Invalid argument
> 
> with no other output. I get that error almost every time I try to do
> something with Guix and it usually works anyway. Since I got no other
> errors I just kept going with
> 
> $ guix build emacs --dry-run
> 
> and got "The following derivations would be built:" so apparently it
> did not work.
> 
> During an installation I do see a lot of "updating list of substitutes"
> messages, but I also frequently see the word "build" and a lot of .c
> and .h files go by, which combined with the long installation time
> makes me doubt that it is actually downloading binaries from the
> substitutes and installing them.
>

how to install from binary

2017-11-12 Thread Mason Hock



Guix seems to be building everything from source, which can take a
while. As per these instructions I tried

# cd [prefix]/share/guix/hydra.gnu.org.pub
# guix archive --authorize < hydra.gnu.org.pub
and got

guile: warning: failed to install locale
warning: failed to install locale: Invalid argument

with no other output. I get that error almost every time I try to do
something with Guix and it usually works anyway. Since I got no other
errors I just kept going with

$ guix build emacs --dry-run

and got "The following derivations would be built:" so apparently it
did not work.

During an installation I do see a lot of "updating list of substitutes"
messages, but I also frequently see the word "build" and a lot of .c
and .h files go by, which combined with the long installation time
makes me doubt that it is actually downloading binaries from the
substitutes and installing them.

Re: error running emacs installed with guix

2017-11-12 Thread Adonay Felipe Nogueira

Indeed, I also experienced this issue...

Even starting Emacs with `-Q' option doesn't help.

Mason Hock  writes:

> I have installed emacs with Guix. When I try to run it I get
>
> Gtk-Message: Failed to load module "canberra-gtk-module"
> Gtk-Message: Failed to load module "topmenu-gtk-module"
>
> followed by many
>
> (emacs-25-3:7212): Gtk-WARNING **: Theme parsing error:*
>
> messages, and then
>
> GLib-GIO-Message: Using the 'memory' GSettings backend.  Your settings
> will not be saved or shared with other applications.
> Fatal error 6: Aborted
> Backtrace:
> /gnu/store/5jfh7wlrkc0lhrfdaijsjgz8w9bwqxvf-emacs-25.3/bin/emacs-
> 25.3[0x81393ec]
> /gnu/store/5jfh7wlrkc0lhrfdaijsjgz8w9bwqxvf-emacs-25.3/bin/emacs-
> 25.3[0x8121e63]
> /gnu/store/5jfh7wlrkc0lhrfdaijsjgz8w9bwqxvf-emacs-25.3/bin/emacs-
> 25.3[0x813947c]
> /gnu/store/5jfh7wlrkc0lhrfdaijsjgz8w9bwqxvf-emacs-25.3/bin/emacs-
> 25.3[0x8176e75]
> /gnu/store/5jfh7wlrkc0lhrfdaijsjgz8w9bwqxvf-emacs-25.3/bin/emacs-
> 25.3[0x8176e5d]
> /gnu/store/5jfh7wlrkc0lhrfdaijsjgz8w9bwqxvf-emacs-25.3/bin/emacs-
> 25.3[0x8176cce]
> /gnu/store/5jfh7wlrkc0lhrfdaijsjgz8w9bwqxvf-emacs-25.3/bin/emacs-
> 25.3[0x8176e5d]
> /gnu/store/5jfh7wlrkc0lhrfdaijsjgz8w9bwqxvf-emacs-25.3/bin/emacs-
> 25.3[0x8176c9e]
> /gnu/store/5jfh7wlrkc0lhrfdaijsjgz8w9bwqxvf-emacs-25.3/bin/emacs-
> 25.3[0x8176e5d]
> /gnu/store/5jfh7wlrkc0lhrfdaijsjgz8w9bwqxvf-emacs-25.3/bin/emacs-
> 25.3[0x8176e5d]
> /gnu/store/5jfh7wlrkc0lhrfdaijsjgz8w9bwqxvf-emacs-25.3/bin/emacs-
> 25.3[0x8176cce]
> /gnu/store/5jfh7wlrkc0lhrfdaijsjgz8w9bwqxvf-emacs-25.3/bin/emacs-
> 25.3[0x817705f]
> /gnu/store/5jfh7wlrkc0lhrfdaijsjgz8w9bwqxvf-emacs-25.3/bin/emacs-
> 25.3[0x8176e5d]
> /gnu/store/5jfh7wlrkc0lhrfdaijsjgz8w9bwqxvf-emacs-25.3/bin/emacs-
> 25.3[0x8176c9e]
> /gnu/store/5jfh7wlrkc0lhrfdaijsjgz8w9bwqxvf-emacs-25.3/bin/emacs-
> 25.3[0x8176e5d]
> /gnu/store/5jfh7wlrkc0lhrfdaijsjgz8w9bwqxvf-emacs-25.3/bin/emacs-
> 25.3[0x8176e5d]
> /gnu/store/5jfh7wlrkc0lhrfdaijsjgz8w9bwqxvf-emacs-25.3/bin/emacs-
> 25.3[0x8176c9e]
> /gnu/store/5jfh7wlrkc0lhrfdaijsjgz8w9bwqxvf-emacs-25.3/bin/emacs-
> 25.3[0x8176e5d]
> /gnu/store/5jfh7wlrkc0lhrfdaijsjgz8w9bwqxvf-emacs-25.3/bin/emacs-
> 25.3[0x8176e5d]
> /gnu/store/5jfh7wlrkc0lhrfdaijsjgz8w9bwqxvf-emacs-25.3/bin/emacs-
> 25.3[0x8176c9e]
> /gnu/store/5jfh7wlrkc0lhrfdaijsjgz8w9bwqxvf-emacs-25.3/bin/emacs-
> 25.3[0x8176e5d]
> /gnu/store/5jfh7wlrkc0lhrfdaijsjgz8w9bwqxvf-emacs-25.3/bin/emacs-
> 25.3[0x8176c9e]
> /gnu/store/5jfh7wlrkc0lhrfdaijsjgz8w9bwqxvf-emacs-25.3/bin/emacs-
> 25.3[0x8176e5d]
> /gnu/store/5jfh7wlrkc0lhrfdaijsjgz8w9bwqxvf-emacs-25.3/bin/emacs-
> 25.3[0x8176e5d]
> /gnu/store/5jfh7wlrkc0lhrfdaijsjgz8w9bwqxvf-emacs-25.3/bin/emacs-
> 25.3[0x8176c9e]
> /gnu/store/5jfh7wlrkc0lhrfdaijsjgz8w9bwqxvf-emacs-25.3/bin/emacs-
> 25.3[0x8176e5d]
> /gnu/store/5jfh7wlrkc0lhrfdaijsjgz8w9bwqxvf-emacs-25.3/bin/emacs-
> 25.3[0x8176e5d]
> /gnu/store/5jfh7wlrkc0lhrfdaijsjgz8w9bwqxvf-emacs-25.3/bin/emacs-
> 25.3[0x8176c9e]
> /gnu/store/5jfh7wlrkc0lhrfdaijsjgz8w9bwqxvf-emacs-25.3/bin/emacs-
> 25.3[0x8176e5d]
> /gnu/store/5jfh7wlrkc0lhrfdaijsjgz8w9bwqxvf-emacs-25.3/bin/emacs-
> 25.3[0x8176e5d]
> /gnu/store/5jfh7wlrkc0lhrfdaijsjgz8w9bwqxvf-emacs-25.3/bin/emacs-
> 25.3[0x8176c9e]
> /gnu/store/5jfh7wlrkc0lhrfdaijsjgz8w9bwqxvf-emacs-25.3/bin/emacs-
> 25.3[0x8176e5d]
> /gnu/store/5jfh7wlrkc0lhrfdaijsjgz8w9bwqxvf-emacs-25.3/bin/emacs-
> 25.3[0x8176cce]
> /gnu/store/5jfh7wlrkc0lhrfdaijsjgz8w9bwqxvf-emacs-25.3/bin/emacs-
> 25.3[0x817705f]
> /gnu/store/5jfh7wlrkc0lhrfdaijsjgz8w9bwqxvf-emacs-25.3/bin/emacs-
> 25.3[0x8176cce]
> /gnu/store/5jfh7wlrkc0lhrfdaijsjgz8w9bwqxvf-emacs-25.3/bin/emacs-
> 25.3[0x8176e5d]
> /gnu/store/5jfh7wlrkc0lhrfdaijsjgz8w9bwqxvf-emacs-25.3/bin/emacs-
> 25.3[0x817705f]
> /gnu/store/5jfh7wlrkc0lhrfdaijsjgz8w9bwqxvf-emacs-25.3/bin/emacs-
> 25.3[0x81770fd]
> /gnu/store/5jfh7wlrkc0lhrfdaijsjgz8w9bwqxvf-emacs-25.3/bin/emacs-
> 25.3[0x817841e]
> /gnu/store/5jfh7wlrkc0lhrfdaijsjgz8w9bwqxvf-emacs-25.3/bin/emacs-
> 25.3[0x8176e7f]
> /gnu/store/5jfh7wlrkc0lhrfdaijsjgz8w9bwqxvf-emacs-25.3/bin/emacs-
> 25.3[0x8176e5d]
> ...
> Aborted (core dumped)
>
>
> Does anyone know what to make of this?
>
> Thanks,
>
> Mason

-- 
- https://libreplanet.org/wiki/User:Adfeno
- Palestrante e consultor sobre /software/ livre (não confundir com
  gratis).
- "WhatsApp"? Ele não é livre. Por favor, veja formas de se comunicar
  instantaneamente comigo no endereço abaixo.
- Contato: https://libreplanet.org/wiki/User:Adfeno#vCard
- Arquivos comuns aceitos (apenas sem DRM): Corel Draw, Microsoft
  Office, MP3, MP4, WMA, WMV.
- Arquivos comuns aceitos e enviados: CSV, GNU Dia, GNU Emacs Org, GNU
  GIMP, Inkscape SVG, JPG, LibreOffice (padrão ODF), OGG, OPUS, PDF
  (apenas sem DRM), PNG, TXT, WEBM.

error running emacs installed with guix

2017-11-12 Thread Mason Hock

I have installed emacs with Guix. When I try to run it I get

Gtk-Message: Failed to load module "canberra-gtk-module"
Gtk-Message: Failed to load module "topmenu-gtk-module"

followed by many

(emacs-25-3:7212): Gtk-WARNING **: Theme parsing error:*

messages, and then

GLib-GIO-Message: Using the 'memory' GSettings backend.  Your settings
will not be saved or shared with other applications.
Fatal error 6: Aborted
Backtrace:
/gnu/store/5jfh7wlrkc0lhrfdaijsjgz8w9bwqxvf-emacs-25.3/bin/emacs-
25.3[0x81393ec]
/gnu/store/5jfh7wlrkc0lhrfdaijsjgz8w9bwqxvf-emacs-25.3/bin/emacs-
25.3[0x8121e63]
/gnu/store/5jfh7wlrkc0lhrfdaijsjgz8w9bwqxvf-emacs-25.3/bin/emacs-
25.3[0x813947c]
/gnu/store/5jfh7wlrkc0lhrfdaijsjgz8w9bwqxvf-emacs-25.3/bin/emacs-
25.3[0x8176e75]
/gnu/store/5jfh7wlrkc0lhrfdaijsjgz8w9bwqxvf-emacs-25.3/bin/emacs-
25.3[0x8176e5d]
/gnu/store/5jfh7wlrkc0lhrfdaijsjgz8w9bwqxvf-emacs-25.3/bin/emacs-
25.3[0x8176cce]
/gnu/store/5jfh7wlrkc0lhrfdaijsjgz8w9bwqxvf-emacs-25.3/bin/emacs-
25.3[0x8176e5d]
/gnu/store/5jfh7wlrkc0lhrfdaijsjgz8w9bwqxvf-emacs-25.3/bin/emacs-
25.3[0x8176c9e]
/gnu/store/5jfh7wlrkc0lhrfdaijsjgz8w9bwqxvf-emacs-25.3/bin/emacs-
25.3[0x8176e5d]
/gnu/store/5jfh7wlrkc0lhrfdaijsjgz8w9bwqxvf-emacs-25.3/bin/emacs-
25.3[0x8176e5d]
/gnu/store/5jfh7wlrkc0lhrfdaijsjgz8w9bwqxvf-emacs-25.3/bin/emacs-
25.3[0x8176cce]
/gnu/store/5jfh7wlrkc0lhrfdaijsjgz8w9bwqxvf-emacs-25.3/bin/emacs-
25.3[0x817705f]
/gnu/store/5jfh7wlrkc0lhrfdaijsjgz8w9bwqxvf-emacs-25.3/bin/emacs-
25.3[0x8176e5d]
/gnu/store/5jfh7wlrkc0lhrfdaijsjgz8w9bwqxvf-emacs-25.3/bin/emacs-
25.3[0x8176c9e]
/gnu/store/5jfh7wlrkc0lhrfdaijsjgz8w9bwqxvf-emacs-25.3/bin/emacs-
25.3[0x8176e5d]
/gnu/store/5jfh7wlrkc0lhrfdaijsjgz8w9bwqxvf-emacs-25.3/bin/emacs-
25.3[0x8176e5d]
/gnu/store/5jfh7wlrkc0lhrfdaijsjgz8w9bwqxvf-emacs-25.3/bin/emacs-
25.3[0x8176c9e]
/gnu/store/5jfh7wlrkc0lhrfdaijsjgz8w9bwqxvf-emacs-25.3/bin/emacs-
25.3[0x8176e5d]
/gnu/store/5jfh7wlrkc0lhrfdaijsjgz8w9bwqxvf-emacs-25.3/bin/emacs-
25.3[0x8176e5d]
/gnu/store/5jfh7wlrkc0lhrfdaijsjgz8w9bwqxvf-emacs-25.3/bin/emacs-
25.3[0x8176c9e]
/gnu/store/5jfh7wlrkc0lhrfdaijsjgz8w9bwqxvf-emacs-25.3/bin/emacs-
25.3[0x8176e5d]
/gnu/store/5jfh7wlrkc0lhrfdaijsjgz8w9bwqxvf-emacs-25.3/bin/emacs-
25.3[0x8176c9e]
/gnu/store/5jfh7wlrkc0lhrfdaijsjgz8w9bwqxvf-emacs-25.3/bin/emacs-
25.3[0x8176e5d]
/gnu/store/5jfh7wlrkc0lhrfdaijsjgz8w9bwqxvf-emacs-25.3/bin/emacs-
25.3[0x8176e5d]
/gnu/store/5jfh7wlrkc0lhrfdaijsjgz8w9bwqxvf-emacs-25.3/bin/emacs-
25.3[0x8176c9e]
/gnu/store/5jfh7wlrkc0lhrfdaijsjgz8w9bwqxvf-emacs-25.3/bin/emacs-
25.3[0x8176e5d]
/gnu/store/5jfh7wlrkc0lhrfdaijsjgz8w9bwqxvf-emacs-25.3/bin/emacs-
25.3[0x8176e5d]
/gnu/store/5jfh7wlrkc0lhrfdaijsjgz8w9bwqxvf-emacs-25.3/bin/emacs-
25.3[0x8176c9e]
/gnu/store/5jfh7wlrkc0lhrfdaijsjgz8w9bwqxvf-emacs-25.3/bin/emacs-
25.3[0x8176e5d]
/gnu/store/5jfh7wlrkc0lhrfdaijsjgz8w9bwqxvf-emacs-25.3/bin/emacs-
25.3[0x8176e5d]
/gnu/store/5jfh7wlrkc0lhrfdaijsjgz8w9bwqxvf-emacs-25.3/bin/emacs-
25.3[0x8176c9e]
/gnu/store/5jfh7wlrkc0lhrfdaijsjgz8w9bwqxvf-emacs-25.3/bin/emacs-
25.3[0x8176e5d]
/gnu/store/5jfh7wlrkc0lhrfdaijsjgz8w9bwqxvf-emacs-25.3/bin/emacs-
25.3[0x8176cce]
/gnu/store/5jfh7wlrkc0lhrfdaijsjgz8w9bwqxvf-emacs-25.3/bin/emacs-
25.3[0x817705f]
/gnu/store/5jfh7wlrkc0lhrfdaijsjgz8w9bwqxvf-emacs-25.3/bin/emacs-
25.3[0x8176cce]
/gnu/store/5jfh7wlrkc0lhrfdaijsjgz8w9bwqxvf-emacs-25.3/bin/emacs-
25.3[0x8176e5d]
/gnu/store/5jfh7wlrkc0lhrfdaijsjgz8w9bwqxvf-emacs-25.3/bin/emacs-
25.3[0x817705f]
/gnu/store/5jfh7wlrkc0lhrfdaijsjgz8w9bwqxvf-emacs-25.3/bin/emacs-
25.3[0x81770fd]
/gnu/store/5jfh7wlrkc0lhrfdaijsjgz8w9bwqxvf-emacs-25.3/bin/emacs-
25.3[0x817841e]
/gnu/store/5jfh7wlrkc0lhrfdaijsjgz8w9bwqxvf-emacs-25.3/bin/emacs-
25.3[0x8176e7f]
/gnu/store/5jfh7wlrkc0lhrfdaijsjgz8w9bwqxvf-emacs-25.3/bin/emacs-
25.3[0x8176e5d]
...
Aborted (core dumped)


Does anyone know what to make of this?

Thanks,

Mason

Re: Application Setup on Trisquel

2017-11-12 Thread Adonay Felipe Nogueira

An addendum: as was pointed out the default values for $XDG_DATA_HOME
and $XDG_DATA_DIRS are only assumed if these are unset.

Besides, in the short-term solution that suggests appending values to
$XDG_DATA_DIRS to the environment/shell's profile, I emphasize the need
to do it manually.

Solutions such as:

--8<---cut here---start->8---
[Additional value.]:${XDG_DATA_DIRS:+:}${XDG_DATA_DIRS}
--8<---cut here---end--->8---

Or even:

--8<---cut here---start->8---
if [ $XDG_DATA_DIRS ]
then
export XDG_DATA_DIRS="[Additional value.]:$XDG_DATA_DIRS"
else
export XDG_DATA_DIRS="[Additional value.]"
fi
--8<---cut here---end--->8---

... will both lead only to "[Additional value.]" inside $XDG_DATA_DIRS
--- because the Xsession.d scripts that set the foreign distro's value
for $XDG_DATA_DIRS are run *after* the environment/shell's profile is
read and as far as I can tell, before the user logs in the desktop
environemnt.

Adonay Felipe Nogueira  writes:

> I might have some information that might help understand how
> ${XDG_DATA_DIRS} interferes in case of GNU Guix in foreign distros.
>
> Reading the XDG Base Directory Specification ([1]):
>
> --8<---cut here---start->8---
> [...]
>
> * Basics
>
> The XDG Base Directory Specification is based on the following concepts:
>
> - There is a single base directory relative to which user-specific data
>   files should be written. This directory is defined by the environment
>   variable $XDG_DATA_HOME
>
>   [...]
>
> - There is a set of preference ordered base directories relative to
>   which data files should be searched. This set of directories is
>   defined by the environment variable $XDG_DATA_DIRS
>
>   [...]
>
> * Environment variables
>
> $XDG_DATA_HOME defines the base directory relative to which user
> specific data files should be stored. If $XDG_DATA_HOME is either not
> set or empty, a default equal to $HOME/.local/share should be used
>
> [...]
>
> $XDG_DATA_DIRS defines the preference-ordered set of base directories to
> search for data files in addition to the $XDG_DATA_HOME base
> directory. The directories in $XDG_DATA_DIRS should be seperated with a
> colon ':'.
>
> If $XDG_DATA_DIRS is either not set or empty, a value equal to
> /usr/local/share/:/usr/share/ should be used.
>
> [...]
>
> The order of base directories denotes their importance; the first
> directory listed is the most important. When the same information is
> defined in multiple places the information defined relative to the more
> important base directory takes precedent. The base directory defined by
> $XDG_DATA_HOME is considered more important than any of the base
> directories defined by $XDG_DATA_DIRS. The base directory defined by
> $XDG_CONFIG_HOME is considered more important than any of the base
> directories defined by $XDG_CONFIG_DIRS
>
> [...]
> --8<---cut here---end--->8---
>
>
> This, as far as I can understand means that $XDG_DATA_HOME (or assumed
> default value) is the user defined "data" directory. While
> $XDG_DATA_DIRS (or assumed default value) is a preference list that
> comes *after* $XDG_DATA_HOME. Inside the list, entries are sorted from
> "most preferred" to "last resort".
>
> The combination forms a preference queue, like so:
>
> XDG_DATA_HOME XDG_DATA_DIRS
>
> Where, if there are various values for the same information, the first
> appearance takes the lead, and the remaining conflicting values are
> discarded. The following quote taken from [1] contributes to this:
>
> --8<---cut here---start->8---
> [...]
>
> * Referencing this specification
>
> Other specifications may reference this specification by specifying the
> location of a data file as $XDG_DATA_DIRS/subdir/filename. This implies
> that:
>
> - Such file should be installed to $datadir/subdir/filename with
>   $datadir defaulting to /usr/share.
>
> - A user specific version of the data file may be created in
>   $XDG_DATA_HOME/subdir/filename, taking into account the default
>   value for $XDG_DATA_HOME if $XDG_DATA_HOME is not set.
>
> - Lookups of the data file should search for ./subdir/filename
>   relative to all base directories specified by $XDG_DATA_HOME and
>   $XDG_DATA_DIRS . If an environment variable is either not set or
>   empty, its default value as defined by this specification should be
>   used instead.
>
> [...]
>
> A specification that refers to $XDG_DATA_DIRS or $XDG_CONFIG_DIRS should
> define what the behaviour must be when a file is located under multiple
> base directories. It could, for example, define that only the file under
> the most important base directory should be used or, as another example,
> it could define rules for merging the information from the different
> files.
>
>

Re: Application Setup on Trisquel

2017-11-12 Thread Adonay Felipe Nogueira

I might have some information that might help understand how
${XDG_DATA_DIRS} interferes in case of GNU Guix in foreign distros.

Reading the XDG Base Directory Specification ([1]):

--8<---cut here---start->8---
[...]

* Basics

The XDG Base Directory Specification is based on the following concepts:

- There is a single base directory relative to which user-specific data
  files should be written. This directory is defined by the environment
  variable $XDG_DATA_HOME

  [...]

- There is a set of preference ordered base directories relative to
  which data files should be searched. This set of directories is
  defined by the environment variable $XDG_DATA_DIRS

  [...]

* Environment variables

$XDG_DATA_HOME defines the base directory relative to which user
specific data files should be stored. If $XDG_DATA_HOME is either not
set or empty, a default equal to $HOME/.local/share should be used

[...]

$XDG_DATA_DIRS defines the preference-ordered set of base directories to
search for data files in addition to the $XDG_DATA_HOME base
directory. The directories in $XDG_DATA_DIRS should be seperated with a
colon ':'.

If $XDG_DATA_DIRS is either not set or empty, a value equal to
/usr/local/share/:/usr/share/ should be used.

[...]

The order of base directories denotes their importance; the first
directory listed is the most important. When the same information is
defined in multiple places the information defined relative to the more
important base directory takes precedent. The base directory defined by
$XDG_DATA_HOME is considered more important than any of the base
directories defined by $XDG_DATA_DIRS. The base directory defined by
$XDG_CONFIG_HOME is considered more important than any of the base
directories defined by $XDG_CONFIG_DIRS

[...]
--8<---cut here---end--->8---

This, as far as I can understand means that $XDG_DATA_HOME (or assumed
default value) is the user defined "data" directory. While
$XDG_DATA_DIRS (or assumed default value) is a preference list that
comes *after* $XDG_DATA_HOME. Inside the list, entries are sorted from
"most preferred" to "last resort".

The combination forms a preference queue, like so:

XDG_DATA_HOME XDG_DATA_DIRS

Where, if there are various values for the same information, the first
appearance takes the lead, and the remaining conflicting values are
discarded. The following quote taken from [1] contributes to this:

--8<---cut here---start->8---
[...]

* Referencing this specification

Other specifications may reference this specification by specifying the
location of a data file as $XDG_DATA_DIRS/subdir/filename. This implies
that:

- Such file should be installed to $datadir/subdir/filename with
  $datadir defaulting to /usr/share.

- A user specific version of the data file may be created in
  $XDG_DATA_HOME/subdir/filename, taking into account the default
  value for $XDG_DATA_HOME if $XDG_DATA_HOME is not set.

- Lookups of the data file should search for ./subdir/filename
  relative to all base directories specified by $XDG_DATA_HOME and
  $XDG_DATA_DIRS . If an environment variable is either not set or
  empty, its default value as defined by this specification should be
  used instead.

[...]

A specification that refers to $XDG_DATA_DIRS or $XDG_CONFIG_DIRS should
define what the behaviour must be when a file is located under multiple
base directories. It could, for example, define that only the file under
the most important base directory should be used or, as another example,
it could define rules for merging the information from the different
files.

[...]
--8<---cut here---end--->8---

Note that from the last paragraph of the quote, one can see that each
project is responsible for dealing with cases where a file *with the
same relative path* is found in various entries in $XDG_DATA_DIRS (note
that we are not talking about $XDG_DATA_HOME here).

For example, suppose I have $XDG_DATA_DIRS *expanded* as follows:

/home/adfeno/.guix-profile/share:/usr/share

We see two entries here, and unfortunatelly, suppose I have two "gnome"
icon themes, one in each entry:

/home/adfeno/.guix-profile/share/icons/gnome
/usr/share/icons/gnome

Both have an "index.theme", so according to the Icon Theme Specification
([2]), the first (in "/home/adfeno/.guix-profile/share") should be used,
as according to [2]:

--8<---cut here---start->8---
[...]

In at least one of the theme directories there must be a file called
index.theme that describes the theme. The first index.theme found while
searching the base directories in order is used. This file describes the
general attributes of the theme. 

[...]
--8<---cut here---end--->8---

Also according to [2], a fallback theme called "hicolor" is assumed in
almost all cases and application authors should install at

Re: openssh installed, but ssh-daemon not starting

2017-11-12 Thread Marco van Hulten

David-

Op 10 nov 07:45 schreef Thompson, David:
> Marco wrote:
> > root@watson ~# herd start ssh-daemon
> > herd: service 'ssh-daemon' could not be found
> > ```
> >
> > Is there actually a service `ssh-daemon' belonging to the package
> > openssh?  
> 
> Services being installed upon package installation is one of those
> things you learn from other distros that needs to be "unlearned" when
> using GuixSD.  When you run `guix package` you are altering your own
> personal package profile, it doesn't alter the system in any way.
> Installing the openssh package as a user is a good way to get the
> openssh client available in your shell, but in order to get the
> openssh daemon running you'll need to add an expression like `(service
> openssh-service-type (openssh-configuration ...))` to your OS
> configuration file and run `guix system reconfigure`.  Make sure to
> import the (gnu services ssh) module otherwise you'll get undefined
> variable errors.

It now works with the (service openssh-service-type).  I did not change
the default configuration.  I feel a bit fuzzy about the exact keywords
used, sometimes services take only one keyword:

  (services (cons* (xfce-desktop-service)
   (service openssh-service-type)
   %desktop-services))

For XFCE we use a singlet, whereas for OpenSSH a pair is used.  Must
one use such a pair if there are (optionally) configuration parameters
to be defined for the respective service?

The syntax of the ssh module import at the top of my profile is a bit
different, but it seems to work (https://paste.debian.net/995301/).

I am starting to understand the generals of the system.

Thank you for the help!

-Marco

Re: Application Setup on Trisquel

2017-11-12 Thread Adonay Felipe Nogueira

For the case of themes not matching and buttoms not showing up, perhaps
one can try the suggestion I made to that same thread ([1]).

[1] 
.

Caleb Herbert  writes:

> I have a better way.  This did not work for me on Trisquel.
>
> My experience: Apps appeared in the main menu, but GNOME was not aware
> of them.  Icons were missing, Emacs would never show up in "Open With",
> and I couldn't launch Mumble from Run Application (Alt+F2).
>
> Solution:
> https://trisquel.info/en/forum/guix-trisquel#comment-122789
> (Thanks, ADFENO!)
>
> GNOME sees apps and icons now!
>
> Remaining hurdles:
>   * Buttons don't show up, themes don't match:
> https://lut.im/g7za20HA8Z/U8CWURMKf3X0a1GI.png
>   * Fcitx Mozc input method for Japanese does not work in Guix apps

-- 
- https://libreplanet.org/wiki/User:Adfeno
- Palestrante e consultor sobre /software/ livre (não confundir com
  gratis).
- "WhatsApp"? Ele não é livre. Por favor, veja formas de se comunicar
  instantaneamente comigo no endereço abaixo.
- Contato: https://libreplanet.org/wiki/User:Adfeno#vCard
- Arquivos comuns aceitos (apenas sem DRM): Corel Draw, Microsoft
  Office, MP3, MP4, WMA, WMV.
- Arquivos comuns aceitos e enviados: CSV, GNU Dia, GNU Emacs Org, GNU
  GIMP, Inkscape SVG, JPG, LibreOffice (padrão ODF), OGG, OPUS, PDF
  (apenas sem DRM), PNG, TXT, WEBM.

Re: successful installation, but problems updating

2017-11-12 Thread Chris Marusich

Hi Leo and George,

I've taken a stab at improving the "Substitutes" section.  Please let me
know if you have any concerns by replying to the patch email submission:

https://debbugs.gnu.org/cgi/bugreport.cgi?bug=29271

I think the existence of this email thread proves that the question of
"Are substitutes enabled by default?" does not have an obvious answer.
I also think that the existence of this email proves that the behavior
of the --fallback command is not obvious, so it requires a very careful
explanation in the manual to eliminate any risk of misinterpretation.

Please do not reply to this email with feedback on the patch series;
please respond to the patch email if you have feedback on the patch.

-- 
Chris


signature.asc
Description: PGP signature

Re: how to install from binary

how to install from binary

Re: error running emacs installed with guix

error running emacs installed with guix

Re: Application Setup on Trisquel

Re: Application Setup on Trisquel

Re: openssh installed, but ssh-daemon not starting

Re: Application Setup on Trisquel

Re: successful installation, but problems updating

9 matches

Site Navigation

Mail list logo

Footer information