1 |
On Wed, Jun 18, 2008 at 11:48:19PM +0200, Florian Philipp wrote: |
2 |
> On Wed, 18 Jun 2008 22:01:03 +0100 |
3 |
> Matt Harrison <iwasinnamuknow@×××××××××.com> wrote: |
4 |
> |
5 |
> > On Wed, Jun 18, 2008 at 10:46:25PM +0200, Florian Philipp wrote: |
6 |
> > > Which versions are you using, to which shall they be updated and on |
7 |
> > > which arch are you? Knowing emerge --info and your profile might |
8 |
> > > also help. |
9 |
> > |
10 |
> > Thanks for the reply. |
11 |
> > |
12 |
> > Ok, versions in use: |
13 |
> > |
14 |
> > lvm2-2.02.10 |
15 |
> > mdadm-2.6.4-r1 |
16 |
> > udev-104-r12 |
17 |
> > |
18 |
> > I've masked updates to an versions after those above. Emerge wants to |
19 |
> > upgrade to the following: |
20 |
> > |
21 |
> > lvm2-2.02.28-r2 |
22 |
> > udev-119 |
23 |
> > |
24 |
> |
25 |
> udev-104 ?! That's not even in the portage tree any longer, right? |
26 |
|
27 |
Quite possibly, its installed from the 2007.0 stage3 tarball. |
28 |
|
29 |
And in reply to Alan's post, no I'm not (intentionally) useing BL2. Nothing is |
30 |
marked unstable on this machine with the example of a ruby module i quite like. |
31 |
|
32 |
This was the problem before, if I let emerge upgrade mdadm and lvm2, its starts |
33 |
trying to run BL2 initscripts and complaining that I'm not using BL2. |
34 |
|
35 |
> In any case: Opening a bug might help you faster than we could. The only |
36 |
> advice I can give you is to upgrade udev first so you know which |
37 |
> package really has the bug and then to try newer versions of lvm, I'd |
38 |
> try 2.02.36 which is marked stable for amd64 (I guess, you're on x86?). |
39 |
|
40 |
Yes I'm on x86. I've got a few other amd64 systems that does have any problems, |
41 |
but I'm installing a test machine now with a layout as close to this problem |
42 |
system as possible. I'll try upgrading udev, then lvm2 and see if I can break |
43 |
it as well. |
44 |
|
45 |
As I say its annoying because obviously I'm about the only one with this problem. |
46 |
I didn't think my setup was that peculiar :P |
47 |
|
48 |
I'll look into a bug report as soon as I can pin down which package is causing the |
49 |
real probs. |
50 |
|
51 |
Thanks |