I've can reproducibly revert to 1.5 but all attempts to then follow the steps
to install 2.0 through up a popup
saying something to the effect that another version of icedove is running, kill
it or restart your system.
There's nothing to kill, a new x zsession doesn't work, a reboot doesn't work
Arnaud Fontaine wrote:
Are you planning a new stable release of pyme soon which will include
this patch ?
Well.. I do plan 0.7.1 release "any minute now" for the last half an
year. :-(
I want to figure out why do I still have problems with MinGW32 built
PyMe on Windows.
The problems boil
Igor Belyi wrote:
I'm still trying to find the right workaround for this. For now it
seems SWIG 1.3.28 is not good
version to use for pyme build.
I've got it! Here's a slightly better patch which should not break back
compatibility and does not use
undocumented features. I&#
OK, I've looked at it and I'm sorry to say I don't think this is the
right patch.
It seems to me that the patch disables gpgme.i's "const char *" typemap
definition by using
SWIG's bug of not reporting invalid syntax but silently ignoring it to
work around another SWIG
bug of the typemap causi
Package: usbmount
Version: 0.0.14
Followup-For: Bug #317022
Our friends in udev moved vol_id from /sbin into /lib/udev which results in
usbmount to not find it. I don't know in which version of udev this change
happen since I just started using usbmount. For now I just created sym.link
/sbin/vol_i
Sorry, I'm on LinuxWorld Expo this week and won't be able to look at
this until next week. If this switch appears just in 1.3.28 swig then
the change should be a little bit bigger for back compatibility.
Shortly, I greatly appreciate the patch - it gives me the right
direction where I need to l
Could you specified versions of SWIG, SSL, and gcc used?
Thanks,
Igor
--
To UNSUBSCRIBE, email to [EMAIL PROTECTED]
with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
Bastian Blank wrote:
On Wed, Jun 29, 2005 at 08:49:21AM -0400, Igor Belyi wrote:
Here's what I get with lvm2 2.01.04-5 tools:
# vgdisplay lvmg
[...]
Formatlvm1
[...]
So it is lvm1.
Do you need those 64K of metadata as well?
On related note,
Bastian Blank wrote:
On Tue, Jun 28, 2005 at 07:11:49PM -0400, Igor Belyi wrote:
Attached is the /etc/lvm/backup/lvmg config file for the group.
You forget one essential information: lvm1 or lvm2 metadata, otherwise
I'm only able to say: works for me.
Bastian
Here's
Package: lvm2
Version: 2.01.12-2
Followup-For: Bug #315339
Installing new lvm2 makes stripped VG unrecognizable.
Downgrading lvm2 back to 2.01.04-5 fixes the problem.
# vgdisplay lvmg
LV backup: inconsistent LE count 1832 != 3662
Internal error: LV segments corrupted in backup.
Volume group
10 matches
Mail list logo
