Bug#854181: RFA: busybox --Tiny utilities for small and embedded systems

2017-08-10 Thread Richard Hecker
I have used busybox over the years and would enjoy keeping it current.  I can 
be the
sole maintainer or work with Michael Tokarev in some teaming arrangement.  I 
will email
Michael directly to assess his preferences.

Richard



Bug#482840: set6x86: Please add hurd-i386 arch

2011-04-15 Thread Richard Hecker
On Sat, Apr 09, 2011 at 01:14:27PM +0200, Samuel Thibault wrote:

...snip...
 
 Does anybody still have a cyrix box on which to try this?
 
My cyrix box has not been powered up in quite a while.  A lot of other
changes have come along with the new job.  Hopefully someone else will
be able to step up and help out in this instance.

Richard



-- 
To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org
with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org



Bug#503403: munin-node: Generates error messages when initializing plugins on install (and dpkg --purge too)

2008-10-25 Thread Richard Hecker
Package: munin-node
Version: 1.2.6-7
Severity: important

In previous months, munin-node was working so this might just be a symptom of
another problem introduced when I started to pull in some testing packages on
this stable system.  When I saw the error from my dpkg --purge attempts, I
felt compelled to send this report because an unclean purge could interfere
with the next install.

About a month ago, the munin data from this system stopped appearing on the
graphs.  I tried my typical apt-get install --reinstall munin-node response.
For some reason, no error messages show up during a --reinstall.  But if I
use dpkg --purge munin-node to clear the slate, on the next install I always
get the following error messages:

Setting up munin (1.2.6-7) ...
Setting up munin-node (1.2.6-7) ...
Initializing plugins..# There were some errors:
# Got junk from postgres_space_: DBI connect('','',...) failed: FATAL:  Ident 
authentication 
failed for user nobody at /usr/share/munin/plugins/postgres_space_ line 62
# Got junk from postgres_queries_: DBI connect('','',...) failed: FATAL:  Ident 
authentication failed for user nobody at 
/usr/share/munin/plugins/postgres_queries_ line 
98
# Got junk from postgres_block_read_: DBI connect('','',...) failed: FATAL:  
Ident 
authentication failed for user nobody at 
/usr/share/munin/plugins/postgres_block_read_ 
line 96
# Got junk from postgres_commits_: Use of uninitialized value $maybe_dbname in 
string eq at 
/usr/share/munin/plugins/postgres_commits_ line 111.
# Got junk from postgres_commits_: DBI connect('','',...) failed: FATAL:  Ident 
authentication failed for user nobody at 
/usr/share/munin/plugins/postgres_commits_ line 
130
done.
Starting Munin-Node: done.

It puzzles me why a --reinstall does not generate these error messages.  An
example of the --reinstall follows below:

Stopping Munin-Node: done.
Unpacking replacement munin-node ...
Processing triggers for man-db ...
Setting up munin (1.2.6-7) ...
Setting up munin-node (1.2.6-7) ...
Initializing new plugins..done.
Starting Munin-Node: done.

The errors on dpkg --purge are less consistent.  The initial attempts complained
about directories not being deleted and I manually deleted them.  Since I 
started
to type this message and have been cutting and pasting from another window, I am
unable to reproduce the errors I previously saw.  I was not rigorous in using a
script to return to the same pristine condition on each attempt.  It is possible
that the errors were related to some intermediate state where only some of the
directories were manually deleted.  I remember the error message talking about
post-removal issues but I cannot reproduce it to cut and paste into this email.

I wish I could be more helpful in this report, but perhaps it is sufficient to
start exploring why apt-get install --reinstall munin-node fails to generate
the error messages I find after the dpkg --purge munin-node.  If reportbug
does not supply enough information, I will gladly provide any more that you
request.  I should also let you know that I was previously installing and
purging all 3 packages (munin, munin-node, and munin-plugins-extra) with the
same results although this report was generated with 2 packages.

-- System Information:
Debian Release: lenny/sid
  APT prefers testing
  APT policy: (500, 'testing'), (500, 'stable')
Architecture: i386 (i686)

Kernel: Linux 2.6.24-1-686 (SMP w/2 CPU cores)
Locale: LANG=en_US, LC_CTYPE=en_US (charmap=ISO-8859-1)
Shell: /bin/sh linked to /bin/bash

Versions of packages munin-node depends on:
ii  adduser 3.110add and remove users and groups
ii  gawk1:3.1.5.dfsg-4.1 GNU awk, a pattern scanning and pr
ii  libnet-server-perl  0.97-1   An extensible, general perl server
ii  lsb-base3.2-20   Linux Standard Base 3.2 init scrip
ii  perl5.10.0-16Larry Wall's Practical Extraction 
ii  procps  1:3.2.7-8/proc file system utilities

Versions of packages munin-node recommends:
ii  libnet-snmp-perl  5.2.0-1Script SNMP connections

Versions of packages munin-node suggests:
ii  ethtool 6+20080227-1 display or change ethernet card se
ii  libdbd-pg-perl  2.8.7-1  Perl DBI driver for the PostgreSQL
ii  liblwp-useragent-determined 1.03-1   a LWP useragent that retries error
ii  libnet-irc-perl 0.75-8   IRC (Internet Relay Chat) interfac
ii  libwww-perl 5.813-1  WWW client/server library for Perl
ii  lm-sensors  1:3.0.2-1+b2 utilities to read temperature/volt
ii  munin   1.2.6-7  network-wide graphing framework (g
pn  munin-plugins-extra none   (no description available)
ii  mysql-client5.0.51a-15   MySQL database client (metapackage
ii  mysql-client-5.0 [mysql-cli 5.0.51a-15   MySQL database client binaries
ii  python 

Bug#482840: set6x86: Please add hurd-i386 arch

2008-05-30 Thread Richard Hecker
On Sun, May 25, 2008 at 02:04:49PM +0100, Samuel Thibault wrote:
 Package: set6x86
 Version: 1.5-14
 Severity: important
 
 Hello,
 
 set6x86 builds and seems to work fine on hurd-i386 (I don't have a cyrix
 processor to actually test). Could you please add hurd-i386 to the list
 of archs?
 
I will not be able to put a hurd partition on my cyrix box, but I see no
reason to prevent others from trying it.  This bug report can easily be
closed with such an addition, but the results could get interesting as
the cyrix special registers are tweaked under a hurd environment.

Richard



-- 
To UNSUBSCRIBE, email to [EMAIL PROTECTED]
with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]