Mailinglist Archive: opensuse-bugs (4664 mails)

< Previous Next >
[Bug 575096] system locks are not handled in chroot
  • From: bugzilla_noreply@xxxxxxxxxx
  • Date: Tue, 2 Feb 2010 14:52:09 +0000
  • Message-id: <20100202145209.8BD2924551B@xxxxxxxxxxxxxxxxxxxxxx>
http://bugzilla.novell.com/show_bug.cgi?id=575096

http://bugzilla.novell.com/show_bug.cgi?id=575096#c3


Michael Andres <ma@xxxxxxxxxx> changed:

What |Removed |Added
----------------------------------------------------------------------------
CC| |ma@xxxxxxxxxx

--- Comment #3 from Michael Andres <ma@xxxxxxxxxx> 2010-02-02 14:52:09 UTC ---
No.

Either --root can be applied to all the zypp components you create (e.g.
ZyppFactory), or applications can announce the --root at the very beginning, so
zypp is able to create default components with the right paths per default.

For Uwe's usecase I added $ZYPP_LOCKFILE_ROOT, so he's able to pass zyppers
--root via the environment to libzypp. So we did not need to change zypper now.


For the future I'd like to further enhance zypp::misc::defaultLoadSystem to
provide easy startup procedures and access to the zypp components. Something
similar is already available in the test/tools environment, where we can more
or less transparently operate on either a real system or a solver testcase.
Would be nice if at the end you can run e.g. 'zypper dup' on a solver testcase.

--
Configure bugmail: http://bugzilla.novell.com/userprefs.cgi?tab=email
------- You are receiving this mail because: -------
You are on the CC list for the bug.

< Previous Next >
This Thread
  • No further messages