1. Forum
  2. Usenet
  3. LINUX.DEBIAN.BUGS.RC

  • Bug#1103468: dicod doesn't start properly.

    From Karine =?utf-8?B?Q3LDqXZlY8WTdXI=?=@21:1/5 to All on Fri Apr 18 00:10:03 2025
    Package: dicod
    Version: 2.12-2
    Severity: grave

    Hi,
    Dicod cannot start since version 2.12-1.
    Starting dicod with:
    $ dicod --stderr
    It printed: dicod: Error: /etc/dicod.conf:16.1-39: invalid include statement

    So, I change the line 16 from:
    #include /var/lib/dicod/dictorg-db.list
    to:
    #include </var/lib/dicod/dictorg-db.list>

    I tried to start dicod again:
    $ dicod --stderr
    it printed: dicod: Error: /var/lib/dicod/dictorg-db.list:8.1-60: invalid include statement

    in this file the line 8 is just a comment begining with #:
    # included from the dictd configuration file /etc/dicod.conf
    Apparently, the string "# included" is understood as an include
    statement when it should'nt be.

    So now, I added the strin "q " before "included":
    # q included from the dictd configuration file /etc/dicod.conf


    And finally dicod started with: systemctl start dicod.service

    It seems, there is something broken is the parser of the config file.
    While I found a workaround, it's a bit annoying.

    Cheers.
    --
    Karine

    --- SoupGate-Win32 v1.05
    * Origin: fsxNet Usenet Gateway (21:1/5)
  • From Debian Bug Tracking System@21:1/5 to All on Tue Apr 22 23:00:01 2025
    This is a multi-part message in MIME format...

    Your message dated Tue, 22 Apr 2025 20:49:22 +0000
    with message-id <E1u7KYU-009h6r-AB@fasolo.debian.org>
    and subject line Bug#1103468: fixed in dico 2.12-3
    has caused the Debian Bug report #1103468,
    regarding dicod doesn't start properly.
    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 owner@bugs.debian.org
    immediately.)


    --
    1103468: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1103468
    Debian Bug Tracking System
    Contact owner@bugs.debian.org with problems

    Received: (at submit) by bugs.debian.org; 17 Apr 2025 22:02:41 +0000 X-Spam-Checker-Version: SpamAssassin 3.4.6-bugs.debian.org_2005_01_02
    (2021-04-09) on buxtehude.debian.org
    X-Spam-Level:
    X-Spam-Status: No, score=-15.2 required=4.0 tests=BAYES_00,
    BODY_INCLUDES_PACKAGE,DKIM_SIGNED,DKIM_VALID,DKIM_VALID_AU,
    DKIM_VALID_EF,HAS_PACKAGE,SPF_HELO_PASS,SPF_PASS autolearn=ham
    autolearn_force=no version=3.4.6-bugs.debian.org_2005_01_02 X-Spam-Bayes: score:0.0000 Tokens: new, 27; hammy, 150; neutral, 47; spammy,
    0. spammytokens: hammytokens:0.000-+--systemctl, 0.000-+--UD:conf,
    0.000-+--dictd, 0.000-+--Severity, 0.000-+--UD:service
    Return-path: <enikar@gresille.org>
    Received: from mx2.gresille.org ([2001:912:410::77]:33591 helo=mouche.gresille.org)
    by buxtehude.debian.org with esmtps (TLS1.2:ECDHE_X25519__RSA_SHA512__AES_256_GCM:256)
    (Exim 4.94.2)