package repo sync mismatch.



  • Hey guys. Just trying to install tinc on the Omega and comming against a dependency issue. Weird thing is it's is asking for an older kernel. Is the default kernel a custom one?

    -- CUT --
    opkg install tinc
    Installing tinc (1.0.26-1) to root...
    Downloading http://downloads.openwrt.org/chaos_calmer/15.05/ar71xx/generic/packages/packages/tinc_1.0.26-1_ar71xx.ipk.
    Collected errors:

    • satisfy_dependencies_for: Cannot satisfy the following dependencies for tinc:
    • kernel (= 3.18.20-1-7bed08fa9c06eb8089e82c200340ec66) *
    • opkg_install_cmd: Cannot install package tinc.

    uname -a
    Linux Omega-xxxx 3.18.21 #1 Sat Oct 31 19:02:01 UTC 2015 mips GNU/Linux

    -- CUT --

    Should I point the Omega at a different repo?

    Cheers.


  • administrators

    Yea, several packages seem to depend on the 3.18.20 kernel.

    The kernel on the Omega is the same as the one in the OpenWRT Chaos Calmer 15.05 build so I'm not too sure why these issues are happening.

    We're working on our own packages repo that will take care of issues like this one, expect that in the coming weeks.
    In the meantime, maybe try different repos and see how they go?



  • Hmm there is something weird going on here because looking at the packages from https://downloads.openwrt.org/chaos_calmer/15.05/ar71xx/generic/packages/base/ the kernel package there is kernel_3.18.20-1. So of course none of the kernel dependant packages will work, and seeing as tun is missing from the 3.18.21 build the Omega came with that means no VPN of any sort.

    Can you investigate where this 3.18.21 kernel came from? Because it seems not to be the official OpenWRT repo.

    Cheers



  • @T-NT I think all the packages on their repo are just compiled for OpenWRT during their development branch. Then, just before they released CC, they decided to move the kernel to 3.18.21, but didn't have a chance to recompile all the packages yet...

    We should be doing a recompile of all the opkg packages on the current kernel after we release the console update this week.



  • Yeah.. seems to be sensible if you are going to pin to 15.05 better to use their kernel source and patch it only if needed for drivers and firmware. Thanks.


Log in to reply
 

Looks like your connection to Community was lost, please wait while we try to reconnect.