Your message dated Fri, 10 Apr 2009 12:08:01 -0400
with message-id <1239379640-sup-...@gillespie.rupamsunyata.org>
and subject line Re: Bug#523011: Info received (diakonos: fails to start)
has caused the Debian Bug report #523011,
regarding diakonos: fails to start
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 ow...@bugs.debian.org
immediately.)


-- 
523011: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=523011
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Package: diakonos
Version: 0.8.8-1
Severity: grave
Justification: renders package unusable

I installed this package, closed my network connection, and then tried
to run it:

    $ diakonos
    grep: help/*: No such file or directory
    diakonos.conf not found in any of:
      .
      /home/decklin/.diakonos
    At least one configuration file must exist.
    Would you like to download one right now from the Diakonos repository? 
(y/n)n
    Terminating due to lack of configuration file.

...and it quits. (I'll assume the "help/*" bit is a separate bug.)
Just for illustration, here's what happens if I try to download the
file anyway:

    $ diakonos
    grep: help/*: No such file or directory
    diakonos.conf not found in any of:
      .
      /home/decklin/.diakonos
    At least one configuration file must exist.
    Would you like to download one right now from the Diakonos repository? 
(y/n)y
    Fetching configuration from v0.8.8...
    /usr/lib/ruby/1.8/net/http.rb:560:in `initialize': getaddrinfo: Temporary 
failure in name resolution (SocketError)
            from /usr/lib/ruby/1.8/net/http.rb:560:in `open'
            from /usr/lib/ruby/1.8/net/http.rb:560:in `connect'
            from /usr/lib/ruby/1.8/timeout.rb:53:in `timeout'
            from /usr/lib/ruby/1.8/timeout.rb:93:in `timeout'
            from /usr/lib/ruby/1.8/net/http.rb:560:in `connect'
            from /usr/lib/ruby/1.8/net/http.rb:553:in `do_start'
            from /usr/lib/ruby/1.8/net/http.rb:542:in `start'
            from /usr/lib/ruby/1.8/open-uri.rb:242:in `open_http'
            from /usr/lib/ruby/1.8/open-uri.rb:616:in `buffer_open'
            from /usr/lib/ruby/1.8/open-uri.rb:164:in `open_loop'
            from /usr/lib/ruby/1.8/open-uri.rb:162:in `catch'
            from /usr/lib/ruby/1.8/open-uri.rb:162:in `open_loop'
            from /usr/lib/ruby/1.8/open-uri.rb:132:in `open_uri'
            from /usr/lib/ruby/1.8/open-uri.rb:518:in `open'
            from /usr/lib/ruby/1.8/open-uri.rb:30:in `open'
            from /usr/lib/ruby/1.8/diakonos/config.rb:22:in `fetch_conf'
            from /usr/lib/ruby/1.8/diakonos/config.rb:70:in `loadConfiguration'
            from /usr/lib/ruby/1.8/diakonos.rb:122:in `initialize'
            from /usr/bin/diakonos:5:in `new'
            from /usr/bin/diakonos:5

This is totally nuts. The package includes a /etc/diakonos.conf, which
looks like a perfectly reasonable configuration file. The program
should use this file for defaults, then override them with any
settings in the user's personal dotfile, if that file exists, like
most *nix programs.

If it is impossible to implement that for now, then /etc/diakonos.conf
should silently be copied to ~/.diakonos on startup if the latter does
not exist. End-users should never have to pull "fresh" configuration
files from a development repository, even from a tag; they should use
the stable one shipped with the package.

(If I understand the goal of this package correctly, a sizable segment
of its target audience shouldn't be pestered about "configuring"
anything at all. I don't, however, feel it's as much of a problem if
users who *do* wish to configure their editor need to copy the whole
default file to their ~/.diakonos before tweaking it; they presumably
know what they're getting into.)

This does not only make the package unusable for one user if their
network is down, but also for everyone if the development host (I
assume it's fetching this directly from Github) has an outage for any
reason. The package should be self-contained (it already has the file
in question, anyway). So, I'm marking this as grave.

-- System Information:
Debian Release: squeeze/sid
  APT prefers unstable
  APT policy: (500, 'unstable'), (1, 'experimental')
Architecture: amd64 (x86_64)

Kernel: Linux 2.6.29 (SMP w/2 CPU cores; PREEMPT)
Locale: LANG=en_US.UTF-8, LC_CTYPE=en_US.UTF-8 (charmap=UTF-8)
Shell: /bin/sh linked to /bin/bash

Versions of packages diakonos depends on:
ii  ruby                          4.2        An interpreter of object-oriented 

diakonos recommends no packages.

diakonos suggests no packages.

-- no debconf information



--- End Message ---
--- Begin Message ---
This appears to be fixed in -4.
-- 
things change.
deck...@red-bean.com


--- End Message ---

Reply via email to