Yeah, it does that when it thinks it has "better" information in the
package feed databases.
If you go to the ipkg/opkg feed configuration file directory, and just
rename the feed config files to something that ipkg/opkg doesn't
recognize, that'll disable the feeds effectively. You can then install
using "./<filename>
ipkg/opkg can't resolve dependencies, so you'll have to install those
manually in advance...
Don't forget to rename the feed config files back again when you're done.
-Mike (mwester)
tlhackque wrote:
> I tried ./ as well as the absolute path to the package. ipkg still tries to download the v2 pkg specified by the feed instead of using the file...
>
> I don't have this problem when I build a newer version of a package; I have private versions of bind, dhcp, openssl that all use the file when I specify it.
>
> The strange behavior seems to be unique to the down-rev kit.
>
> --- In nslu2-linux@
>
>> You can try "ipkg install ./freeradius_
>>
>> For building optware/nslu2 (unslung) toolchain, it's probably easier just use latest make/crosstool.
>>
>> Cheers,
>>
>> -Brian
>>
>> --- In nslu2-linux@
>>
>>>
>>> Thanks for the clues. I built the package - details below.
>>>
>>> But ipkg now refuses to install it! If I say:
>>> $ ipkg install freeradius_1.
>>> ipkg starts downloading the 2.0.5-2 package from the unslung/cross feed!
>>>
>>> I've tried -force-downgrade, even -f /dev/null. But (as demonstrated with strace) ipkg goes and reads the /etc/ipkg feed files & then downloads the 2.0.5-2 package.
>>>
>>> I note that this package has a 'recommends' for freeradius-doc; putting that kit in the same directory doesn't help.
>>>
>>> The only way to persuade it to use the file specified on the command line is to
>>> $ mv /etc/ipkg /etc/ipkg-x; ipkg install freeradius_1.
>>>
>>> This seems excessively hard - if I explicitly specify a file, that's what I want.
>>>
>>> Is there an option that I'm missing? If not this seems like a (moderately serious) bug.
>>>
>>> Other thoughts?
>>>
>>> Thanks.
>>>
>>> T
>>>
>>> Here's what it took to build this package - I'll make a wiki HOWTO when I've dug out of the current crisis...meantime, perhaps this will help someone else.
>>>
>>> $ svn co https://svn.
>>> $ svn log make/freeradius.
>>> # r8749 is the rev that upgraded from 1.1.7
>>> $ svn up -r8748 <-- We want the rev BEFORE the upgrading commit!
>>> $ cd optware; make <platform>-target
>>> $ cd <platform>; make directories toolchain ipkg-utils
>>>
>>> Build fails because crosstool 0.38 isn't available.
>>> Visit http://kegel.
>>>
>>> Edit optware/make/
>>>
>>> $ make toolchain ipkg-utils
>>> Ignore lots of glib doesn't build unoptimized errors...
>>>
>>> $ make freeradius
>>>
>>> Depends on openssl, site is down. Modify optware/make/
>>>
>>> OPENSSL_SITE=http://www.mirrorse
>>>
>>> Depends on mysql - for some reason, the kit downloads into '.' rather than 'downloads/'
>>>
>>> $ mv mysql downloads/
>>> $ make freeradius
>>>
>>> Curses! ncurses-5.6.
>>>
>>> $ make mysql
>>>
>>> $ make freeradius
>>> $ make freeradius-ipk
>>>
>>> and freeradius_1.
>>>
>>> --- In nslu2-linux@
>>>
>>>> Optware package changes are all recorded in subversion.
>>>>
>>>> 1) Follow the instruction on
>>>> http://www.nslu2-
>>>> to get optware subversion checkout;
>>>>
>>>> 2) Then do "svn log make/freeradius.
>>>>
>>>> 3) You'd want to "turn back the clock"
>>>> The command probably is "svn up -r8749"
>>>>
>>>> 4) Build toolchain, and try to build the package
>>>>
>>>> I think I've noticed that in order to build unslung toolchain, you'd need host gcc 3.x
>>>>
>>>> Good luck,
>>>>
>>>> -Brian
>>>>
>>>> --- In nslu2-linux@
>>>>
>>>>> I'm rebuilding an unslung system from a disk failure, looking for freeradius 1.1.7-2 - not quite ready to update to freeradius V2 - which is the current feed.
>>>>>
>>>>> Is the old .ipk file available somewhere? If not, is there a way to build it from the source repository?
>>>>>
>>>>> It would be good to have a HOWTO that describes how to get the build system to to build a specific version of any package - if someone can give me the necessary clues, I'll be happy to add to the wiki.
>>>>>
>>>>> Thanks.
>>>>>
>>>>>
>
>
>
>
> ------------
>
> Yahoo! Groups Links
>
>
>
>
>
No comments:
Post a Comment