Your message dated Mon, 24 Mar 2008 14:16:09 +0100 with message-id <200803241416.11473.thijs@debian.org> and subject line recent versions give correct error has caused the Debian Bug report #216434, regarding busybox: ln reports wrong error 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.) -- 216434: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=216434 Debian Bug Tracking System Contact owner@bugs.debian.org with problems
--- Begin Message ---
- To: Debian Bug Tracking System <submit@bugs.debian.org>
- Subject: busybox: ln reports wrong error
- From: Goswin Brederlow <brederlo@informatik.uni-tuebingen.de>
- Date: Sat, 18 Oct 2003 20:22:09 +0200
- Message-id: <E1AAviM-0006zO-00@dual>
Package: busybox Version: 1:0.60.5-2 Severity: normal When linking a non existing file busybox ln will report the target missind and not the source: mrvn@dual:~% ln /bla/foo /foo ln: accessing `/bla/foo': No such file or directory mrvn@dual:~% busybox ln /bla/foo /foo ln: /foo: No such file or directory MfG Goswin -- System Information: Debian Release: testing/unstable Architecture: i386 Kernel: Linux dual 2.4.21-ac4 #1 SMP Sat Jul 5 17:53:13 CEST 2003 i686 Locale: LANG=C, LC_CTYPE=de_DE Versions of packages busybox depends on: ii libc6 2.3.2-4 GNU C Library: Shared libraries an -- no debconf information
--- End Message ---
--- Begin Message ---
- To: 216434-done@bugs.debian.org
- Subject: recent versions give correct error
- From: Thijs Kinkhorst <thijs@debian.org>
- Date: Mon, 24 Mar 2008 14:16:09 +0100
- Message-id: <200803241416.11473.thijs@debian.org>
Version: 1:1.9.2-1 Hi, I've tested this against recent versions of busybox like the one currently in unstable, and these give the correct error. I therefore consider the issue solved, thanks for reporting it. ThijsAttachment: pgpf0uVbskOGu.pgp
Description: PGP signature
--- End Message ---