Re: Distro upgrade
On Jo, 19 dec 13, 18:39:07, John Hasler wrote: > > There is no need for him to "track" Jessie once he has upgraded enough > to run his program. Just read the security list and upgrade individual > packages as needed. This smells like dependency hell. Kind regards, Andrei -- http://wiki.debian.org/FAQsFromDebianUser Offtopic discussions among Debian users and developers: http://lists.alioth.debian.org/mailman/listinfo/d-community-offtopic http://nuvreauspam.ro/gpg-transition.txt signature.asc Description: Digital signature
Re: Distro upgrade
On Jo, 19 dec 13, 10:23:35, John Hasler wrote: > Read and follow the release notes and you'll be ok. For Jessie? They don't exist yet. Kind regards, Andrei -- http://wiki.debian.org/FAQsFromDebianUser Offtopic discussions among Debian users and developers: http://lists.alioth.debian.org/mailman/listinfo/d-community-offtopic http://nuvreauspam.ro/gpg-transition.txt signature.asc Description: Digital signature
Re: Distro upgrade
On 12/20/2013 10:56 AM, John Hasler wrote: > Verde Denim writes: >> Is it possible for me to upgrade glibc/libffi to the Jessie release >> and leave everything else in Wheezy? > Upgrading glibc and libffi will force the upgrade of packages that depend > on specific versions of those libraries. Use 'apt-get -s' to see what > would happen. John Didn't get as much as I thought... Mostly libcurl, gpg, and xserver references. I wouldn't think I'd need to update sources to run this. Is there something more I'm missing? (I can post the list of packages since it's not overly long if that would help). -- Regards Jack Boston Tea Party, Coercive Acts, Powder Alarm, Revolution Lessons (Mistakes) not learned are bound to be repeated. -- To UNSUBSCRIBE, email to debian-user-requ...@lists.debian.org with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org Archive: http://lists.debian.org/52b4d984.8070...@gmail.com
Re: Distro upgrade
On Friday 20 December 2013 15:24:41 Verde Denim wrote: > Is > it possible for me to upgrade glibc/libffi to the Jessie release > and leave everything else in Wheezy? Have you looked at wheezy-backports? http://backports.debian.org/ http://packages.debian.org/search?keywords=glibc I see that you probably have looked, but have included this for the archives. Lisi. -- To UNSUBSCRIBE, email to debian-user-requ...@lists.debian.org with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org Archive: http://lists.debian.org/201312201613.37113.lisi.re...@gmail.com
Re: Distro upgrade
Verde Denim writes: > Is it possible for me to upgrade glibc/libffi to the Jessie release > and leave everything else in Wheezy? Upgrading glibc and libffi will force the upgrade of packages that depend on specific versions of those libraries. Use 'apt-get -s' to see what would happen. -- John Hasler jhas...@newsguy.com Elmwood, WI USA -- To UNSUBSCRIBE, email to debian-user-requ...@lists.debian.org with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org Archive: http://lists.debian.org/87mwjvcy91@thumper.dhh.gt.org
Re: Distro upgrade
On 12/19/2013 07:39 PM, John Hasler wrote: > Bob Proulx writes: >> Jessie is at least a year from release. There are still major changes >> planned for it. I expect Jessie to go through some cyclic stability, >> instability, stability, instability before it releases at least a year >> from now. > There is no need for him to "track" Jessie once he has upgraded enough > to run his program. Just read the security list and upgrade individual > packages as needed. > > In fact, it might make the most sense for him to upgrade only the > dependencies of his program while leaving everything else alone. Thanks, John. That does make some sense. The effected packages are libffi and glibc. Apparently the version of glibc in Wheezy is 2.11 and what the hopper package wants is 2.14/2.15. I did see where some newer distros were going to eglibc, which makes this a bit more confusing. Is it possible for me to upgrade glibc/libffi to the Jessie release and leave everything else in Wheezy? -- Regards Jack Boston Tea Party, Coercive Acts, Powder Alarm, Revolution Lessons (Mistakes) not learned are bound to be repeated. -- To UNSUBSCRIBE, email to debian-user-requ...@lists.debian.org with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org Archive: http://lists.debian.org/52b46139.7040...@gmail.com
Re: Distro upgrade
Bob Proulx writes: > Jessie is at least a year from release. There are still major changes > planned for it. I expect Jessie to go through some cyclic stability, > instability, stability, instability before it releases at least a year > from now. There is no need for him to "track" Jessie once he has upgraded enough to run his program. Just read the security list and upgrade individual packages as needed. In fact, it might make the most sense for him to upgrade only the dependencies of his program while leaving everything else alone. -- John Hasler jhas...@newsguy.com Elmwood, WI USA -- To UNSUBSCRIBE, email to debian-user-requ...@lists.debian.org with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org Archive: http://lists.debian.org/87vbykcq50@thumper.dhh.gt.org
Re: Distro upgrade
Verde Denim wrote: > Stan Hoeppner wrote: > > Why take any chances? Install/run Jessie and the application in a > > virtual machine. > > Thanks for the reply. I thought of that, but the package I'm after is an > integral part of my test platform for assessing mobile code. I really do > need to have it in the toolbox. The question is how accessible does the tool need to be to be considered in your toolbox? > Maybe a more pertinent question is - how stable is Jessie at this > point... Jessie is at least a year from release. There are still major changes planned for it. I expect Jessie to go through some cyclic stability, instability, stability, instability before it releases at least a year from now. > If the basics of a workstation platform are workable, I might take a > chance on upgrading. I think it is pretty good at this moment. But if your question is what will it be like next week then that is a much harder question to answer. Predicting the future is easy. Predicting the future correctly is quite a bit harder. :-) > I also thought of the 'safer' path in building a vm, adding each app > to see how it goes and determine what needs to be 'tweaked' as I go, > and finally, building a physical system from the virtual one > (assuming VirtualBox allows this to occur on a solid state > drive). The dist-upgrade would be the shorter path, but I don't want > to clobber an entire environment in an effort to save myself some > work. The VM is a good suggestion. But heavy. It would be a complete different system. That would put everything at arms length. I like using chroots for things like you are suggesting. It is a different set of work but I suggest setting up a Jessie chroot on your system. It is lighter than a full VM. Then run your dissassembler from the chroot. https://wiki.debian.org/chroot You can even run X GUI programs from the chroot with a little bit of initial setup. A lot of people use 'schroot' to make this easier. Look into schroot for a hint on how to do this. Bob signature.asc Description: Digital signature
Re: Distro upgrade
Verde Denim writes:
> ...is there more control I can exercise over the updating of the
> distro other than 'apt-get dist-upgrade' ?
First do 'apt-get upgrade'. This will do everything that can be done
without any removals or installation of new packages. It may suffice to
get you to the point where you can install the package you need. Do not
proceed until this command runs without error ("Some packages have not
been upgraded" is not an error). Then do 'apt-get -s dist-upgrade' and
study the proposed list of changes. You may want to implement some of
them one at a time. Then do 'apt-get dist-upgrade'. If you use Gnome
expect trouble.
--
John Hasler
jhas...@newsguy.com
Elmwood, WI USA
--
To UNSUBSCRIBE, email to debian-user-requ...@lists.debian.org
with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org
Archive: http://lists.debian.org/874n64ep5a@thumper.dhh.gt.org
Re: Distro upgrade
On 12/19/2013 11:23 AM, John Hasler wrote: > Read and follow the release notes and you'll be ok. John Thanks for the reply. If you're suggesting the release notes for Jessie, I agree that they should be reviewed. Aside from reviewing these notes, is there more control I can exercise over the updating of the distro other than 'apt-get dist-upgrade' ? -- Regards Jack Boston Tea Party, Coercive Acts, Powder Alarm, Revolution Lessons (Mistakes) not learned are bound to be repeated. -- To UNSUBSCRIBE, email to debian-user-requ...@lists.debian.org with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org Archive: http://lists.debian.org/52b3203b.70...@gmail.com
Re: Distro upgrade
On 12/19/2013 11:07 AM, Stan Hoeppner wrote: > On 12/19/2013 9:54 AM, Verde Denim wrote: >> Just checking in to get a consensus - >> >> I'm running a (very stable) Debian workstation with Wheezy that has a >> lot of development/testing applications installed. I tried an install of >> hopper disassembler that threw errors concerning GLIBC and libffi so I >> contacted the package maintainers who told me that they setup an >> environment with Debian Jessie and the package works as expected. I'd >> like to work with this package, but am a curious to know if upgrading >> the release from Wheezy to Jessie might cause other issues with the >> large number of packages already running well. Any input, as always, is >> greatly appreciated. > Why take any chances? Install/run Jessie and the application in a > virtual machine. > Stan Thanks for the reply. I thought of that, but the package I'm after is an integral part of my test platform for assessing mobile code. I really do need to have it in the toolbox. Maybe a more pertinent question is - how stable is Jessie at this point... If the basics of a workstation platform are workable, I might take a chance on upgrading. I also thought of the 'safer' path in building a vm, adding each app to see how it goes and determine what needs to be 'tweaked' as I go, and finally, building a physical system from the virtual one (assuming VirtualBox allows this to occur on a solid state drive). The dist-upgrade would be the shorter path, but I don't want to clobber an entire environment in an effort to save myself some work. -- Regards Jack Boston Tea Party, Coercive Acts, Powder Alarm, Revolution Lessons (Mistakes) not learned are bound to be repeated. -- To UNSUBSCRIBE, email to debian-user-requ...@lists.debian.org with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org Archive: http://lists.debian.org/52b31f4e.6050...@gmail.com
Re: Distro upgrade
Read and follow the release notes and you'll be ok. -- John Hasler jhas...@newsguy.com Elmwood, WI USA -- To UNSUBSCRIBE, email to debian-user-requ...@lists.debian.org with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org Archive: http://lists.debian.org/87bo0cernc@thumper.dhh.gt.org
Re: Distro upgrade
On 12/19/2013 9:54 AM, Verde Denim wrote: > Just checking in to get a consensus - > > I'm running a (very stable) Debian workstation with Wheezy that has a > lot of development/testing applications installed. I tried an install of > hopper disassembler that threw errors concerning GLIBC and libffi so I > contacted the package maintainers who told me that they setup an > environment with Debian Jessie and the package works as expected. I'd > like to work with this package, but am a curious to know if upgrading > the release from Wheezy to Jessie might cause other issues with the > large number of packages already running well. Any input, as always, is > greatly appreciated. Why take any chances? Install/run Jessie and the application in a virtual machine. -- Stan -- To UNSUBSCRIBE, email to debian-user-requ...@lists.debian.org with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org Archive: http://lists.debian.org/52b319d1.4070...@hardwarefreak.com
