Am Donnerstag, 19. Februar 2004 09:25 schrieb Jaap Eldering:
> Hello,

Jaap;


> I couldn't find the place to file a bug-report on the sourceforge website,
> so I mail to this list. If that's not the right way, could someone tell me
> how to report a bug?

This is one correct place.

Another is support request tracker.
http://sourceforge.net/tracker/?group_id=13751&atid=213751


> I found some small bugs in the libc207 and bash packages for bering-uclibc:
>
> In libc207.lrp in the package-list /var/lib/lrpkg/libc207.list there's some
> trailing whitespaces, which causes packages to not correctly backup.
> Another minor thing I changed is the line 'var/lib/lrpkg/libc207*' to
> 'var/lib/lrpkg/libc207.*' (include a dot).

I cannot confirm the trailing whitespaces.

> In bash.lrp (version 2.05b-5) the files /bin/bash and /bin/sh conflict with
> the symlinks in initrd.lrp, causing also incorrect backups. I solved this
> by moving the real bash shell to /usr/bin. Because when bash replaces ash
> as shell for executing the backup scripts, bash reports a message when the
> backup 'ticker' (/usr/sbin/ticker) gets killed by it's parent script.

You are right with symlink, backup works fine, it's just an cosmetical issue 
with ticker.

Anyway there have been too many reports about smaller problems with using bash 
as /bin/sh and broken scripts. I removed symlink today and committed into cvs 
a new bash.lrp. Pls download from viewcvs or Bering-uClibc packages page 
tomorrow (updates in cvs may take about 24 hrs to arrive there).

kp


-------------------------------------------------------
SF.Net is sponsored by: Speed Start Your Linux Apps Now.
Build and deploy apps & Web services for Linux with
a free DVD software kit from IBM. Click Now!
http://ads.osdn.com/?ad_id=1356&alloc_id=3438&op=click
------------------------------------------------------------------------
leaf-user mailing list: [EMAIL PROTECTED]
https://lists.sourceforge.net/lists/listinfo/leaf-user
SR FAQ: http://leaf-project.org/pub/doc/docmanager/docid_1891.html

Reply via email to