Bug#943986: wrong shared linkage position of mv's library dependency

2019-11-06 Thread Michael Stone
On Tue, Nov 05, 2019 at 11:40:02PM +0100, David Frey wrote: On Mon, Nov 04, 2019 at 08:17:33AM -0500, Michael Stone wrote: On Sat, Nov 02, 2019 at 12:51:41AM +0100, David Frey wrote: > cp and mv have a runtime linkage to libacl and libattr which are > installed in /usr/lib/x86_64-linux-gnu/. >

Bug#943986: wrong shared linkage position of mv's library dependency

2019-11-05 Thread David Frey
On Mon, Nov 04, 2019 at 08:17:33AM -0500, Michael Stone wrote: > On Sat, Nov 02, 2019 at 12:51:41AM +0100, David Frey wrote: > > cp and mv have a runtime linkage to libacl and libattr which are > > installed in /usr/lib/x86_64-linux-gnu/. > > > > This means that a single-user booted system

Bug#943986: wrong shared linkage position of mv's library dependency

2019-11-01 Thread David Frey
Package: coreutils Version: 8.30-3 Severity: serious cp and mv have a runtime linkage to libacl and libattr which are installed in /usr/lib/x86_64-linux-gnu/. This means that a single-user booted system without mounted /usr, is not able to cp or mv files! Either the dependancy should be