Displaying 17 results from an estimated 17 matches for "guix".
Did you mean:
gui
2020 Feb 20
3
Test failure on ARM: backtrace_append
Hi,
I am a packager in Guix and user of dovecot on an ARM server (armhf). The Guix package fails to build because of a test error (see the last lines of the full build log: https://ci.guix.gnu.org/log/f5if2qb5rsqag3a6jy5vga1l9hm9pkj0-dovecot-2.3.9.3). As the name suggests, this is dovecot 2.3.9.3, the latest version. Previous...
2023 Dec 21
1
9.6p1 test suite help
Hi OpenSSH,
I'm working on updating Guix's openssh package definition to the latest
release. So far, I have only changed the version (and checksum) and left
the build/test/install recipe the same. However, the test suite now fails.
I could use some pointers to find out what exactly is going wrong with the
failing test or how to fi...
2020 Feb 20
2
Test failure on ARM: backtrace_append
Le 20 f?vrier 2020 12:58:52 GMT-05:00, Aki Tuomi <aki.tuomi at open-xchange.com> a ?crit :
>
>> On 20/02/2020 18:56 Julien Lepiller <julien at lepiller.eu> wrote:
>>
>>
>> Hi,
>>
>> I am a packager in Guix and user of dovecot on an ARM server (armhf).
>The Guix package fails to build because of a test error (see the last
>lines of the full build log:
>https://ci.guix.gnu.org/log/f5if2qb5rsqag3a6jy5vga1l9hm9pkj0-dovecot-2.3.9.3).
>As the name suggests, this is dovecot 2.3.9.3, the latest v...
2024 Apr 23
3
[Bug 3682] New: incorrectly thinks that -fzero-call-used-regs should work
https://bugzilla.mindrot.org/show_bug.cgi?id=3682
Bug ID: 3682
Summary: incorrectly thinks that -fzero-call-used-regs should
work
Product: Portable OpenSSH
Version: 9.7p1
Hardware: ARM
OS: Linux
Status: NEW
Severity: normal
Priority: P5
Component: Build system
2020 Feb 20
2
Test failure on ARM: backtrace_append
...8:52 GMT-05:00, Aki Tuomi
><aki.tuomi at open-xchange.com> a ?crit :
>> >
>> >> On 20/02/2020 18:56 Julien Lepiller <julien at lepiller.eu> wrote:
>> >>
>> >>
>> >> Hi,
>> >>
>> >> I am a packager in Guix and user of dovecot on an ARM server
>(armhf).
>> >The Guix package fails to build because of a test error (see the
>last
>> >lines of the full build log:
>>
>>https://ci.guix.gnu.org/log/f5if2qb5rsqag3a6jy5vga1l9hm9pkj0-dovecot-2.3.9.3).
>> >As the name...
2020 Feb 21
0
Test failure on ARM: backtrace_append
...> wrote:
</div>
<div>
>> >>
</div>
<div>
>> >>
</div>
<div>
>> >> Hi,
</div>
<div>
>> >>
</div>
<div>
>> >> I am a packager in Guix and user of dovecot on an ARM server
</div>
<div>
>(armhf).
</div>
<div>
>> >The Guix package fails to build because of a test error (see the
</div>
<div>
>last
</div>
<div>
>> >lines of...
2020 Feb 20
0
Test failure on ARM: backtrace_append
> On 20/02/2020 18:56 Julien Lepiller <julien at lepiller.eu> wrote:
>
>
> Hi,
>
> I am a packager in Guix and user of dovecot on an ARM server (armhf). The Guix package fails to build because of a test error (see the last lines of the full build log: https://ci.guix.gnu.org/log/f5if2qb5rsqag3a6jy5vga1l9hm9pkj0-dovecot-2.3.9.3). As the name suggests, this is dovecot 2.3.9.3, the latest version. Previous...
2020 Feb 20
0
Test failure on ARM: backtrace_append
...;
> Le 20 f?vrier 2020 12:58:52 GMT-05:00, Aki Tuomi <aki.tuomi at open-xchange.com> a ?crit :
> >
> >> On 20/02/2020 18:56 Julien Lepiller <julien at lepiller.eu> wrote:
> >>
> >>
> >> Hi,
> >>
> >> I am a packager in Guix and user of dovecot on an ARM server (armhf).
> >The Guix package fails to build because of a test error (see the last
> >lines of the full build log:
> >https://ci.guix.gnu.org/log/f5if2qb5rsqag3a6jy5vga1l9hm9pkj0-dovecot-2.3.9.3).
> >As the name suggests, this is dovecot 2...
2023 Dec 21
1
9.6p1 test suite help
On Thu, 21 Dec 2023 at 15:52, Jack Hill <jackhill at jackhill.us> wrote:
[...]
> /tmp/guix-build-openssh-9.6p1.drv-0/openssh-9.6p1/regress/ssh-rsa already exists.
> Overwrite (y/n)? ssh-keygen for ssh-rsa failed
The regression tests do this to regenerate the keys if either the
keygen binary has changed:
for t in ${SSH_KEYTYPES}; do
# generate user key
if [ ! -f $OBJ/...
2020 Mar 30
2
IMAP error
Hi,
I am trying to setup a dovecot server on my laptop to serve my emails to
emacs gnus. The emails are pulled from the mail server using isync into
particular directories. I am using a Guix system.
The dovecot service is running. I can telnet into it with:
telnet localhost 143
Trying 127.0.0.1...
Connected to localhost.
Escape character is '^]'.
* OK [CAPABILITY IMAP4rev1 SASL-IR LOGIN-REFERRALS ID ENABLE IDLE LITERAL+
STARTTLS AUTH=PLAIN] Dovecot ready.
However if I then d...
2020 Feb 21
1
Test failure on ARM: backtrace_append
...200 (EET),
Aki Tuomi <aki.tuomi at open-xchange.com> a ?crit :
> Thank you,
>
> as I don't have arm at hand, can you provide
>
> gdb .test-lib core
> bt full
>
> output?
> ---
> Aki Tuomi
>
There you are (sorry for the long file names, that's how guix works,
it's expected):
[New LWP 21501]
Core was generated by `./test-lib'.
Program terminated with signal SIGSEGV, Segmentation fault.
#0 0xb6e24d30 in strchr () from
/gnu/store/n7c20pjm6q1xq1gqjqzzys1yk9fy7n1k-glibc-2.29/lib/libc.so.6
(gdb) bt full
#0 0xb6e24d30 in strchr () from
/gnu/s...
2024 Jan 10
1
Sys.which() caching path to `which`
...## hopefully configure found [/usr]/bin/which
> which <- "@WHICH@"
> if (!nzchar(which)) {
> warning("'which' was not found on this platform")
This poses a problem for the Spack package manager and software
distribution. In Spack, like in Nix, Guix, and GoboLinux, packages live
under their own path prefixes, which look like the following:
>> /opt/spack/opt/spack/linux-ubuntu18.04-x86_64_v3/gcc-7.5.0/r-4.3.0-eqteloqhjzix6ta373ruzt5imvvbcesc
Unfortunately, Spack packages are expected to get relocated, changing
the path prefix and invali...
2020 Mar 30
0
IMAP error
...;>
<div>
Hi,
</div>
<div>
<br>
</div>
<div>
I am trying to setup a dovecot server on my laptop to serve my emails to emacs gnus. The emails are pulled from the mail server using isync into particular directories. I am using a Guix system.
</div>
<div>
<br>
</div>
<div>
The dovecot service is running. I can telnet into it with:
</div>
<div>
<br>
</div>
<div>
telnet localhost 143
</div>
<div>...
2004 Aug 06
1
does IceCast & listeners logging
...st to modify the logging in IceCast ?) to notify the beginning
and the end of a listener's session.
I'm talking about using IceCast for commercial purposes. I think that method would be more efficient when you have to convince an
announcer that you have a precise measure of your audience !
Guix
--- >8 ----
List archives: http://www.xiph.org/archives/
icecast project homepage: http://www.icecast.org/
To unsubscribe from this list, send a message to 'icecast-dev-request@xiph.org'
containing only the word 'unsubscribe' in the body. No subject is needed.
Unsubscribe mess...
2024 Jan 10
0
Sys.which() caching path to `which`
...trying to get packages to not hard-code or cache paths, but that typically only applies to the package library location, not to system tools.
Cheers,
Simon
> On Jan 11, 2024, at 10:36 AM, Harmen Stoppels <me at harmenstoppels.nl> wrote:
>
> For context: I don't think Nix and Guix have to relocate anything, cause I think they require absolute paths like /nix/store where all binaries go. Spack on the other hand can install packages w/o sudo to a location of choice, e.g. ~/spack/opt/spack. That's why we have to patch binaries.
>
> However, Spack's relocation stu...
2024 Sep 28
3
when installing packages for R on Linux, is it better to use my distro's package manager, or install.packages()?
I'm running R (currently 4.4.1) on Linux Mint
> sessionInfo()
R version 4.4.1 (2024-06-14)
Platform: x86_64-pc-linux-gnu
Running under: Linux Mint 20.3
...truncated...
To install a new R package, is it better to use Linux Mint's pacakge
manager (e.g. synaptic, apt-get, or similar), or to install it within R
with install.packages("some_new_package")?
I've done both over
2018 Apr 23
4
R 3.5.0 fails its regression test suite on Linux/x86_64
Hi,
I just tried to upgrade Nixpkgs to R 3.5.0, but unfortunately the new
version fails its regression test suite. We configure the build using
the flags "--without-recommended-packages", in case that's relevant. You
can see a complete build log with all relevant information at [1].
Anyway, the test failures look like this:
| make[3]: Entering directory