gmnisrv: missing mime.types

  • Done
  • quality assurance status badge
Details
3 participants
  • Arun Isaac
  • Christopher Howard
  • Sarah Morgensen
Owner
unassigned
Submitted by
Christopher Howard
Severity
normal
C
C
Christopher Howard wrote on 26 Jun 2021 16:02
(name . Guix Bug Reports)(address . bug-guix@gnu.org)
19db4e71220fe0f8de97a8e9f522c4009f27f7f0.camel@librehacker.com
Hi, I am trying to use the gmnisrv service as described in the Guix
manual, using the default configuration:

(services
(append
(list (service gmnisrv-service-type)
(service openssh-service-type)
(service network-manager-service-type)
(service wpa-supplicant-service-type))
%base-services))

However, gmnisrv keeps dying with this error:

gmnisrv: src/mime.c:37: mime_init: Assertion `0' failed.
Unable to open MIME database for reading: No such file or directory
Is /etc/mime.types installed?

Is the gmnisrv package or service missing a dependency that is supposed to provide the mime.types file, or am I supposed to copy one from somewhere?

My system information:

christopher@galadriel ~$ neofetch --stdout
christopher@galadriel
---------------------
OS: Guix System b36267b1d96ac344d2b42c9822ce04b4c3117f85 x86_64
Host: OptiPlex 7010 01
Kernel: 5.12.13-gnu
Uptime: 24 mins
Packages: 51 (guix-system), 35 (guix-user)
Shell: bash 5.0.16
Terminal: /dev/pts/0
CPU: Intel i5-3570 (4) @ 3.800GHz
GPU: Intel HD Graphics
Memory: 93MiB / 15929MiB

--
Christopher Howard
S
S
Sarah Morgensen wrote on 23 Jul 2021 10:14
(name . Christopher Howard)(address . christopher@librehacker.com)(address . 49233@debbugs.gnu.org)
86a6mdqweo.fsf@mgsn.dev
Hello,

Christopher Howard <christopher@librehacker.com> writes:

Toggle quote (19 lines)
> Hi, I am trying to use the gmnisrv service as described in the Guix
> manual, using the default configuration:
>
> (services
> (append
> (list (service gmnisrv-service-type)
> (service openssh-service-type)
> (service network-manager-service-type)
> (service wpa-supplicant-service-type))
> %base-services))
>
> However, gmnisrv keeps dying with this error:
>
> gmnisrv: src/mime.c:37: mime_init: Assertion `0' failed.
> Unable to open MIME database for reading: No such file or directory
> Is /etc/mime.types installed?
>
> Is the gmnisrv package or service missing a dependency that is supposed to provide the mime.types file, or am I supposed to copy one from somewhere?

It turns out that the gmnisrv package was misconfigured so that it was
necessary to have /etc/mime.types present. I've submitted a patch at


to fix that (as well as not looking for /etc/gmnisrv.conf if present) if
you would like to test it before it makes it into master.

Toggle quote (17 lines)
>
> My system information:
>
> christopher@galadriel ~$ neofetch --stdout
> christopher@galadriel
> ---------------------
> OS: Guix System b36267b1d96ac344d2b42c9822ce04b4c3117f85 x86_64
> Host: OptiPlex 7010 01
> Kernel: 5.12.13-gnu
> Uptime: 24 mins
> Packages: 51 (guix-system), 35 (guix-user)
> Shell: bash 5.0.16
> Terminal: /dev/pts/0
> CPU: Intel i5-3570 (4) @ 3.800GHz
> GPU: Intel HD Graphics
> Memory: 93MiB / 15929MiB

--
Sarah
C
C
Christopher Howard wrote on 23 Jul 2021 18:41
(name . Sarah Morgensen)(address . iskarian@mgsn.dev)(address . 49233@debbugs.gnu.org)
efaa733e9df8cbaab0876106d47f89af77893444.camel@librehacker.com
Thank you. I am currently use agate, but I might give gmnisrv another
try after the patch makes it into master.

-----Original Message-----
From: Sarah Morgensen <iskarian@mgsn.dev>
To: Christopher Howard <christopher@librehacker.com>
Cc: 49233@debbugs.gnu.org
Subject: Re: bug#49233: gmnisrv: missing mime.types
Date: Fri, 23 Jul 2021 01:14:39 -0700

Hello,

Christopher Howard <christopher@librehacker.com> writes:

Toggle quote (21 lines)
> Hi, I am trying to use the gmnisrv service as described in the Guix
> manual, using the default configuration:
>
> (services
> (append
> (list (service gmnisrv-service-type)
> (service openssh-service-type)
> (service network-manager-service-type)
> (service wpa-supplicant-service-type))
> %base-services))
>
> However, gmnisrv keeps dying with this error:
>
> gmnisrv: src/mime.c:37: mime_init: Assertion `0' failed.
> Unable to open MIME database for reading: No such file or directory
> Is /etc/mime.types installed?
>
> Is the gmnisrv package or service missing a dependency that is
> supposed to provide the mime.types file, or am I supposed to copy one
> from somewhere?

It turns out that the gmnisrv package was misconfigured so that it was
necessary to have /etc/mime.types present. I've submitted a patch at


to fix that (as well as not looking for /etc/gmnisrv.conf if present)
if
you would like to test it before it makes it into master.

Toggle quote (16 lines)
> My system information:
>
> christopher@galadriel ~$ neofetch --stdout
> christopher@galadriel
> ---------------------
> OS: Guix System b36267b1d96ac344d2b42c9822ce04b4c3117f85 x86_64
> Host: OptiPlex 7010 01
> Kernel: 5.12.13-gnu
> Uptime: 24 mins
> Packages: 51 (guix-system), 35 (guix-user)
> Shell: bash 5.0.16
> Terminal: /dev/pts/0
> CPU: Intel i5-3570 (4) @ 3.800GHz
> GPU: Intel HD Graphics
> Memory: 93MiB / 15929MiB

--
Sarah
A
A
Arun Isaac wrote on 26 Jul 2021 23:21
(address . 49233-done@debbugs.gnu.org)
87y29sepq0.fsf@systemreboot.net
Hi,

I believe commits b459c39adb725822916a8e21ee250fb408d2e2f8 and
e17f063627f826b4dd0dda77ede48fc7a535414b address this issue. So, closing
this issue.

Thanks,
Arun
-----BEGIN PGP SIGNATURE-----

iQFPBAEBCAA5FiEEf3MDQ/Lwnzx3v3nTLiXui2GAK7MFAmD/J0cbHGFydW5pc2Fh
Y0BzeXN0ZW1yZWJvb3QubmV0AAoJEC4l7othgCuz4EkH+wWiK0YUL0FRH0INOXph
rSWFnRN/55DwFCNA0E66wxuol1tlit4vLt1Q0BQzUINbhMCqw7T8uHBosTIhpokC
15df3wO2NQNIfcpg5nFztFMAB5OHzSQeAF+5KQux0/avMfQEelctbt9K/qCjsZid
yymwT8VThqtkZAl/vZH9ZjH+OH3q++G0CkV2+JhDCXwDSX52h/O8u+iNZrONuL4i
VZ5WX5cr4CUNfMNToqcY4m1hj6odesdeFToGM7kKcMyq8dR24tV5l051tamexYlP
qLmNXtTDj18N0G/ZTSy2wGxuAPzqXHfBmMsg5c0YunmGn8VqiMyRMsWSfsi+HufJ
ehs=
=AoDx
-----END PGP SIGNATURE-----

Closed
?
Your comment

This issue is archived.

To comment on this conversation send an email to 49233@debbugs.gnu.org

To respond to this issue using the mumi CLI, first switch to it
mumi current 49233
Then, you may apply the latest patchset in this issue (with sign off)
mumi am -- -s
Or, compose a reply to this issue
mumi compose
Or, send patches to this issue
mumi send-email *.patch