I've found the reason. I can fix it.

31.10.2016 21:36, Matwey V. Kornilov пишет:
> 
> I even can't understand how to bisect this better. 150 patches in rpm
> lead to many conflicts when begin rebased
> 
> 29.10.2016 20:40, Matwey V. Kornilov пишет:
>> I missed that Leap 42.2 has beta2 version. So, initially I've tested
>> with beta3 taken from Base:System and rebuild with Leap packages.
>> That explains.
>>
>>
>> 2016-10-29 17:50 GMT+03:00 Matwey V. Kornilov <[email protected]>:
>>> grub-2.02-beta2 is failing now:
>>>
>>> Loading linux.vmx...
>>> Loading initrd.vmx...
>>> data abort
>>> pc : [<9dea626c>]          lr : [<9dea930c>]
>>> reloc pc : [<7e75126c>]    lr : [<7e75430c>]
>>> sp : 9ef33e78  ip : 9de93528     fp : 9de55490
>>> r10: 9ded88b4  r9 : 9de554c0     r8 : 00000000
>>> r7 : 00000000  r6 : 00000004     r5 : 00000000  r4 : 9dea800c
>>> r3 : 00000000  r2 : 00000000     r1 : 00005440  r0 : 00000000
>>> Flags: nZCv  IRQs off  FIQs on  Mode SVC_32
>>> Resetting CPU ..
>>>
>>> whereas grub-2.02-beta3 works. I will try to figure out what is wrong...
>>>
>>> 2016-10-29 15:22 GMT+03:00 Andreas Färber <[email protected]>:
>>>> Hi,
>>>>
>>>> Am 29.10.2016 um 14:15 schrieb Matwey V. Kornilov:
>>>>> Now it builds without additional magic, grub2 is available for armv7l.
>>>>> I would like to have devel:ARM:Leap:42.2:Contrib:Beaglebone project to
>>>>> put JeOS-beaglebone here. What do you think?
>>>>
>>>> I would prefer not to create a Contrib project for boards that actually
>>>> run 42.2. Can't you just submit a JeOS package (without _link to
>>>> Factory) to openSUSE:Leap:42.2:Ports? Then Dirk can create links for
>>>> JeOS-beaglebone, JeOS-raspberrypi3 etc.
>>>>
>>>> Regards,
>>>> Andreas
>>>>
>>>> --
>>>> SUSE Linux GmbH, Maxfeldstr. 5, 90409 Nürnberg, Germany
>>>> GF: Felix Imendörffer, Jane Smithard, Graham Norton
>>>> HRB 21284 (AG Nürnberg)
>>>
>>>
>>>
>>> --
>>> With best regards,
>>> Matwey V. Kornilov
>>> http://blog.matwey.name
>>> xmpp://[email protected]
>>
>>
>>
> 
> 


-- 
To unsubscribe, e-mail: [email protected]
To contact the owner, e-mail: [email protected]

Reply via email to