I recently went through the the same thing on RiPi2, needed apt-get update ; apt-get dist-upgrade
I'm not sure the original apt designers envisioned all the firmware blobs required by these ARM processors which seem to require a lot of synchronized changes. I'm looking forward to testing the new bone101 stuff , hopefully I can get to it this week end. Had a weird problem with the RiPi2 after the upgrade -- it wouldn't boot headless (no mouse/keyboard/monitor) unless a USB hub was plugged it and it was picky about which of my three cheap hubs worked :( Talk about a troubleshooting nightmare and lots of cussing and wasted time, but its working great now. Needing the hub is not a total waste as it makes a good power supply for my Adafruit Fona cellular module that gives a backup path for text alerts from my BBW IOT application that is continuously evolving. On Wednesday, August 10, 2016 at 5:30:45 PM UTC-5, William Hermans wrote: > > BUT, if that version update grows a new dependency, then 'update' >> locks that package version, till you run "apt-get dist-upgrade".. >> > > ah, ok, I'll give that a shot. > > It has in the past always been my understanding that dis-upgrade was for > upgrading to a new, or "different" Debian. e.g. Wheezy, or Jessie to > "testing", or "unstable", or in the most recent Wheezy to Jessie. > > On Wed, Aug 10, 2016 at 2:06 PM, Robert Nelson <robert...@gmail.com > <javascript:>> wrote: > >> On Wed, Aug 10, 2016 at 3:58 PM, William Hermans <yyr...@gmail.com >> <javascript:>> wrote: >> > Ug, so we'd for all intents and purposes be installing sid of wheezy >> > packages on our Jessie images ? Not a clean result in that case, which >> is >> > not a complaint. But instead and observation to just not use apt-get >> > upgrade. >> >> Everything is built in a Jessie sbuild, nothing is getting cross >> installed.. >> >> The issue, is with how apt's update works:: >> >> "apt-get update" updates packages when a new version is available. >> >> BUT, if that version update grows a new dependency, then 'update' >> locks that package version, till you run "apt-get dist-upgrade"... >> >> There is a new example coming shortly.. >> >> ti wl18xx firmware package, used by the bbgw: >> >> >> https://github.com/rcn-ee/repos/tree/master/bb-wl18xx-firmware/suite/jessie/debian >> >> it's calling a ti tool "calibrator" >> >> >> https://github.com/rcn-ee/repos/blob/master/bb-wl18xx-firmware/suite/jessie/debian/bb-wl18xx-wlan0#L51 >> >> I need to package this tool, as currently i'm building in the image >> builder: >> >> >> https://github.com/RobertCNelson/omap-image-builder/blob/master/target/chroot/beagleboard.org-jessie.sh#L342-L352 >> >> when i finally package this "ti-calibrator", i'll add a dependicy to >> bb-wl18xx-firmware's control file.. >> >> Then you'll have to: >> >> sudo apt-get update ; sudo apt-get dist-upgrade >> >> Just, to update: bb-wl18xx-firmware >> >> Regards, >> >> -- >> Robert Nelson >> https://rcn-ee.com/ >> >> -- >> For more options, visit http://beagleboard.org/discuss >> --- >> You received this message because you are subscribed to the Google Groups >> "BeagleBoard" group. >> To unsubscribe from this group and stop receiving emails from it, send an >> email to beagleboard...@googlegroups.com <javascript:>. >> To view this discussion on the web visit >> https://groups.google.com/d/msgid/beagleboard/CAOCHtYhFXBDJUE%2BnJ3ZxyRkKXeB9EsCQz0VvYEa4cLxJBEo64g%40mail.gmail.com >> . >> For more options, visit https://groups.google.com/d/optout. >> > > -- For more options, visit http://beagleboard.org/discuss --- You received this message because you are subscribed to the Google Groups "BeagleBoard" group. To unsubscribe from this group and stop receiving emails from it, send an email to beagleboard+unsubscr...@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/beagleboard/5561c0bb-9022-4c08-a1ed-93278a1a8607%40googlegroups.com. For more options, visit https://groups.google.com/d/optout.
