I'm pretty sure I don't know how this relates to 4645, but I have a gut feeling that there is a link somewhere. Perceived Problem 1: we have hal, usdisks 1 and 2 pushing and shoving each other in the scramble to manage fixed and removable storage. Perceived Problem 2: a manifestation of this we have both seen in connection with trying to use urpmi after a fresh install. I have to say that I think my first guess was wrong; this is probably unrelated to udisks (1) because with only udisks2 installed, the error message can only have come from a udisks2-related script or binary. Actual Problem 3: I do not know what tools are thought to be essential for managing storage devices and I don't know why urpmi should be trying to use one when all I am trying to do is get a mirror list from t'internet.
So I suppose the only point of similarity is that we both got the same error message from two different setups. Richard On 25/02/2012, Juergen Harms <[email protected]> wrote: > Re the udisk problem > > I see a little bit clearer: it looks as if udisk2 > > - does not work when I chroot (as it happens) from a Mageia 1 system > into cauldron (beta1) > > - does work flawlessly when I boot into the cauldron system; but this > cauldron system is really a minimum system, no desktop, no gtk (I want > to use it to clarify a BuildRequires problem): it only gives me a > command-line console, chroot would be much more comfortable (having > filesystems mounted on both systems and having all the comfort of guis > for editing and consulting documents on the base system). > > I guess (can somebody confirm, please), that it must be possible to do > unrestricted urpmi with chroot (both DVD and remote repositories) and > that this is probably a plain bug: udisk2 does not work with chroot. I > had done a first try (before I came to this clear working hypothesis) > and had installed - udisk (udisk2? I do not remember) - to no avail. But > that had, trying what-if stuff, gone a little out of hand, and I now > started on a new minimum system. > > I just tried to do a chroot into my old Mageia 1 Alpha file-system - > which is a full install, with desktop and all and which runs OK: same > udisk error message there, hence probably not a problem specific to > minimum installs. > > All this is quite time-consuming, booting all over the place, remaking > systems, I am a little bit frustrated. But, before crying "bug" I should > still repeat the entire thing once more. > > How does this relate to bugzilla #4645 - do you want to have this > discussion there? > > Juergen >
