[Date Prev][Date Next] [Thread Prev][Thread Next] [Date Index] [Thread Index]

Bug#122860: marked as done (busybox: cp -a breaks hard links)

Your message dated Mon, 24 Mar 2008 13:13:05 +0100
with message-id <200803241313.07294.thijs@debian.org>
and subject line fixed upstream around 6 years ago
has caused the Debian Bug report #122860,
regarding busybox: cp -a breaks hard links
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.)


-- 
122860: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=122860
Debian Bug Tracking System
Contact owner@bugs.debian.org with problems
--- Begin Message --- 
Package: busybox
Version: 1:0.60.2-1
Severity: normal

 busybox cp -a breaks hard links.  It used to preserve them!  It also
 had one module that could perform the job of both "cp" and "mv".
 What happened to "cp_mv.c"?  It was codewise smaller than the current
 version, and preserved hard links.

 I realize that "(tar cf - .) | (cd dest && tar xf -)" will preserve
 hard links, and that ancient Unix "cp" did not necessarily do so...
 But both GNU and BSD "cp" do preserve hard links, so I would expect
 busybox "cp" to also do so.


-- System Information
Debian Release: testing/unstable
Architecture: i386
Kernel: Linux juniper 2.4.14-xfs-juniper #1 SMP Thu Dec 6 15:16:23 PST 2001 i686
Locale: LANG=C, LC_CTYPE=C

Versions of packages busybox depends on:
ii  libc6                         2.2.4-6    GNU C Library: Shared libraries an

--- End Message ---
--- Begin Message --- 
Hi,

Matt's patch has been merged upstream around six years ago, I'm therefore 
closing this bug for all versions.


Thijs

Attachment: pgpXOye11QwAP.pgp
Description: PGP signature


--- End Message ---
Reply to: