Broken BAD_RECOMMENDATIONS support

Broken BAD_RECOMMENDATIONS support

[Otavio Salvador]

Hello,

It seems BAD_RECOMMENDATIONS support, in ipk, is broken.

I checked and the rootfs_ipk is writting the contents into the opkg's
status file however it seems opkg when starts to install the packages
it overwrites or ignores it. People at IRC confirmated that this also
happens to them and thus this is indeed broken.

Do someone know how I can debug opkg to see what's going on?

-- 
Otavio Salvador                             O.S. Systems
E-mail: otavio@ossystems.com.br  http://www.ossystems.com.br
Mobile: +55 53 9981-7854              http://projetos.ossystems.com.br

Re: Broken BAD_RECOMMENDATIONS support

[Phil Blundell]

On Mon, 2011-11-07 at 11:45 -0200, Otavio Salvador wrote:
> Hello,
> 
> It seems BAD_RECOMMENDATIONS support, in ipk, is broken.
> 
> I checked and the rootfs_ipk is writting the contents into the opkg's
> status file however it seems opkg when starts to install the packages
> it overwrites or ignores it. People at IRC confirmated that this also
> happens to them and thus this is indeed broken.
> 
> Do someone know how I can debug opkg to see what's going on?

You can add -V4 to ${ipkg_args} in package_install_internal_ipk() to get
more verbosity, though the output is not always especially illuminating.
It might be easiest to just hack the scripting so that it bails out at
that point and then run opkg-cl by hand under the debugger.

p.

Re: Broken BAD_RECOMMENDATIONS support

[Otavio Salvador]

On Mon, Nov 7, 2011 at 11:52, Phil Blundell <philb@gnu.org> wrote:
> On Mon, 2011-11-07 at 11:45 -0200, Otavio Salvador wrote:
>> Hello,
>>
>> It seems BAD_RECOMMENDATIONS support, in ipk, is broken.
>>
>> I checked and the rootfs_ipk is writting the contents into the opkg's
>> status file however it seems opkg when starts to install the packages
>> it overwrites or ignores it. People at IRC confirmated that this also
>> happens to them and thus this is indeed broken.
>>
>> Do someone know how I can debug opkg to see what's going on?
>
> You can add -V4 to ${ipkg_args} in package_install_internal_ipk() to get
> more verbosity, though the output is not always especially illuminating.
> It might be easiest to just hack the scripting so that it bails out at
> that point and then run opkg-cl by hand under the debugger.

Tracing the rootfs generation it proves to be opkg-cl rewritting status file.

Before the first 'opkg-cl install' the status file contains the
information about the bad recommendations but after it installs the
package_linguas, in package_install_internal_ipk then status has no
bad recommendated packages on it.

-- 
Otavio Salvador                             O.S. Systems
E-mail: otavio@ossystems.com.br  http://www.ossystems.com.br
Mobile: +55 53 9981-7854              http://projetos.ossystems.com.br