You can ignore *MRPM-137*, it's unrelated. I have verified that I get the
same error as you on Ubuntu Server. With out debugging it in detail I'm
quite sure it's the *org.codehaus.mojo.unix:unix-rpm* library that fails to
parse the output of *rpm -qlvp <RPM>. *
*
*
I rewrote the Integration Tests to only use groovy + rpm and not depend on
unix-rpm. Applying that patch http://jira.codehaus.org/browse/MRPM-141 all
tests passes also on Debian based distros.

// Rickard


On Tue, Jun 25, 2013 at 10:20 PM, Rickard von Essen <
rickard.von.es...@gmail.com> wrote:

> Hi,
>
> I hade planed to do some work on the rpm plug. But currently I'm pulling
> two jobs so it hade to wait a while.
>
> I think http://jira.codehaus.org/browse/MRPM-137 might fix the IT for
> you. I use vagrant to verify that everything works in CentOS while
> developing on OS X. I attach my Vagrantfile.
>
> Happy hacking!
>
> // Rickard
>
>
> On Tue, Jun 25, 2013 at 8:07 PM, Baptiste MATHUS <bmat...@batmat.net>wrote:
>
>> That's exactly what I was trying to do :).
>> The thing is, I thought afterwards, I haven't an rpm-based system. I'm
>> running kubuntu. So I installed rpm through apt-get. I don't if this is
>> known to have issues.
>>
>> FYI, in fact, I fear things aren't going to run totally smoothly since
>> I'm already running into an IT failure (rpm-1):
>> " post-build script did not succeed. /usr/myusr/app/bin/filter.txt does
>> not exist "
>>
>> I'm gonna have to dig a bit here. If necessary, I guess I'll install some
>> VM running RH or do it from some machine at work, but I'm not yet even sure
>> the IT wouldn't fail there too.
>>
>> Cheers
>>
>>
>>
>> 2013/6/25 Mirko Friedenhagen <mfriedenha...@gmail.com>
>>
>>> Hello Baptiste,
>>>
>>> I think it would be great you made the release-manager. I would suggest
>>> a SNAPSHOT deploy of the trunk with the fix and Daniels confirmation, that
>>> the fix worked for him before, though.
>>>
>>> Regards Mirko
>>> --
>>> Sent from my mobile
>>> On Jun 25, 2013 6:11 PM, "Baptiste Mathus" <bmat...@gmail.com> wrote:
>>>
>>>> Hi,
>>>>
>>>> No timeline. But though I personally dont use this plugin, if nobody
>>>> steps up/objects I can do it those days.
>>>> If the bug is already fixed, that seems quite an easy task to provide
>>>> users satisfaction.
>>>>
>>>> WDYT?
>>>>
>>>> Cheers
>>>> Le 25 juin 2013 17:54, "Daniel Lipofsky" <dlipof...@gmail.com> a
>>>> écrit :
>>>>
>>>>> 2.1-alpha-2 was released Aug 2012, and I know there is at least 1 bug
>>>>> fix since then that I am interested in, so I was wondering if there is a
>>>>> timeline for this.
>>>>>
>>>>> Thanks,
>>>>>  Dan
>>>>>
>>>>
>>
>>
>> --
>> Baptiste <Batmat> MATHUS - http://batmat.net
>> Sauvez un arbre,
>> Mangez un castor !
>>
>
>

Reply via email to