Loading ...
Sorry, an error occurred while loading the content.
 

Re: [nslu2-linux] OpenSlug 2.7 beta -> 3.10 beta upgrade: ipkg says "nothing to be done"

Expand Messages
  • Martin Gingras
    Hi, I was unsuccessfull upgrading to 3.10 from 2.7 like many other people have reported... I had to do a full reinstall.... Mart
    Message 1 of 2 , Aug 30, 2006
      Hi,

      I was unsuccessfull upgrading to 3.10 from 2.7 like many other people
      have reported...
      I had to do a full reinstall....

      Mart

      On 8/29/06, thehagges <the_hagges@...> wrote:
      > I'm stuck...
      >
      > I attempted to follow the Wiki instructions to upgrade from OpenSlug
      > 2.7 beta to 3.10 beta. Everything SEEMED to go according to the Wiki
      > page (including the sh/mount/umount issues), but the reboot failed.
      >
      > On examination, I found that there was no /lib/modules/2.6.16
      > directory, and in fact, no 2.6.16 kernel ipkgs had been installed. In
      > fact, I don't believe that ANY 3.10 beta packages got installed,
      > though I'm not positive on this.
      >
      > The thing that I can't figure out is that:
      >
      > - Yes, I did change the feeds correctly in /etc/ipkg (and ran "ipkg
      > update"):
      >
      > Downloading
      > http://ipkg.nslu2-linux.org/feeds/slugos-bag/cross/3.10-beta/Packages.gz
      > Inflating
      > http://ipkg.nslu2-linux.org/feeds/slugos-bag/cross/3.10-beta/Packages.gz
      > Updated list of available packages in /var/lib/ipkg/cross
      > Downloading
      > http://ipkg.nslu2-linux.org/feeds/slugos-bag/native/3.10-beta/Packages.gz
      > Inflating
      > http://ipkg.nslu2-linux.org/feeds/slugos-bag/native/3.10-beta/Packages.gz
      > Updated list of available packages in /var/lib/ipkg/native
      >
      >
      > - Looking at /var/lib/ipkgs/[cross|native] shows them to be the 3.10
      > versions. Also, "ipkg list" shows the packages from the 3.10 feed.
      >
      > - Running "ipkg upgrade" returns "Nothing to be done", even though
      > "ipkg list_installed" shows only 2.7 beta packages (kernel
      > 2.6.12.2-r17.1, for examle).
      >
      >
      > Does this make any sense? Is there any reason why "ipkg upgrade"
      > would fail to upgrade when the installed packages are clearly lower
      > than the available packages?
      >
      > Hints, tips, pointers, advice, etc. gladly accepted. Thanks!
      >
      >
      >
      >
      >
      >
      > Yahoo! Groups Links
      >
      >
      >
      >
      >
      >
      >
      >
    Your message has been successfully submitted and would be delivered to recipients shortly.