Am 29.05.2010 12:28, schrieb Roman Kyrylych:
>> I think I'm not going to add it. The 'force' option introduces some very
>> weird behaviour from what I remember. As the rc2 package was only in
>> testing, it shouldn't be a big deal, testing users should know what
>> they're doing and upgrade manual
On 2010-05-28, Thomas Bächler wrote:
> Am 27.05.2010 23:08, schrieb Ray Kohler:
>> You need "force" option for cryptsetup because 1.1.1_rc2-1 sorts as
>> newer than 1.1.1-1:
>>
>> warning: cryptsetup: local (1.1.1_rc2-1) is newer than testing (1.1.1-1)
>>
>
> I think I'm not going to add it. The '
On Thu, May 27, 2010 at 1:38 PM, Thomas Bächler wrote:
> I put updated device-mapper/lvm2 2.02.66 and cryptsetup 1.1.1
> packages to testing.
>
> These packages enable udev synchronization to finally get rid of all
> race conditions related to udev rules. I also cleaned up the PKGBUILDs
> massivel
Am 27.05.2010 23:08, schrieb Ray Kohler:
> You need "force" option for cryptsetup because 1.1.1_rc2-1 sorts as
> newer than 1.1.1-1:
>
> warning: cryptsetup: local (1.1.1_rc2-1) is newer than testing (1.1.1-1)
>
I think I'm not going to add it. The 'force' option introduces some very
weird behav
On Thu, May 27, 2010 at 1:38 PM, Thomas Bächler wrote:
> I put updated device-mapper/lvm2 2.02.66 and cryptsetup 1.1.1
> packages to testing.
>
> These packages enable udev synchronization to finally get rid of all
> race conditions related to udev rules. I also cleaned up the PKGBUILDs
> massivel
I put updated device-mapper/lvm2 2.02.66 and cryptsetup 1.1.1
packages to testing.
These packages enable udev synchronization to finally get rid of all
race conditions related to udev rules. I also cleaned up the PKGBUILDs
massively and removed all static binaries and libraries from the packages.
6 matches
Mail list logo