Re: updating debian 8 (jessie) stable to permanent testing - SOLVED?
Hi Lisi.
Just got your posting.
Yes I did find and read this (among other references).
It says:
"If you notice that some packages are not upgraded you should also try
apt-get dist-upgrade, but beware that this command will also install
or remove packages, so do check carefully all proposed actions before
proceeding."
I thought that means yes. (More than once)? (If so, how often)?
What packages should I "notice"? And I do think "check carefully all
proposed actions before proceeding" is a little nebulous, to say the
least.
I also find this (in the same reference document) might benefit from
some elaboration:
"To upgrade to testing, if you have already installed the stable
release, edit your /etc/apt/sources.list changing 'stable' (or the
current codename for stable) in the apt lines to 'testing' (or the
current code name for the next stable release). Additional changes in
that file might be required. "
BTW, what "Additional changes"?
It's not that simple. Years ago, I followed advice to upgrade to
testing by just "edit your /etc/apt/sources.list changing 'stable' (or
the current codename for stable) in the apt lines to 'testing' (or the
current code name for the next stable release".
The results were disastrous.
So again, perhaps some automated mechanism for upgrading might be
beneficial. Or at least some elaboration or amplification of the
documentation on this subject. And how about a simple guide to "this
is how you update to testing"?
Also, I can, and do, and did, use internet search engine(s) in doing
said research. (BTW, Google is NOT "your friend". But that's another
subject).
And the more I think about it, the more I stand behind my opinion that
upgrading is unnecessarily difficult and error-prone.
Whew! Now that that's out of the way, let me ask:
When (and why would you use full-upgrade, as opposed to dist-upgrade
(and how does aptitude figure into that)? I don't use aptitude, I'm
used to apt-get.
Thanks for your reply.
On 1/25/16, Francis Gerund <ranrund@gmail.com> wrote:
> What was I thinking? (I have some distractions going on right now).
>
> dist-upgrades?
>
> Of course. Earlier in this sequence I did ask, to track testing
> permanently, should I do:
>
> sudo apt-get --download-only dist-upgrade
> sudo apt-get dist-upgrade
>
> I presume that's what you meant. Is the answer yes, then? But if so,
> wouldn't that only have to be done once, followed by periodically
> doing:
>
> sudo apt-get update && apt-get upgrade
>
> ???
>
>
> On 1/25/16, Francis Gerund <ranrund@gmail.com> wrote:
>> Hi, Jochen.
>>
>> 1) You are correct. It should have been:
>>
>>>Then, I did:
>>
>>>sudo apt-get check
>>>sudo apt-get update
>>>sudo apt-get upgrade
>>>sudo clean
>>>sudo autoclean
>>>sudo autoremove
>>
>> My mistake. Sorry.
>>
>>
>> 2) Run dist-upgrades? No one mentioned that (to me), and I did not
>> know anything about that.
>>
>> Hopefully I can find some information on that.
>>
>> I thought that once I upgraded to testing, I would be much like stable
>> - just generally sudo apt-get update && apt-get upgrade, and check,
>> clean, autoclean, and autoremove from time to time.
>>
>>
>> 3) No, I don't want to make it easy to break my system, but I do
>> want/need to track testing. Stable is just too stale.
>>
>> I don't feel like testing, unstable, etc. should be only for the
>> nobles, and denied to the mere peasants (like me).
>>
>> I have read/heard all the warnings about system breakage. I do back
>> up my data. And I can reinstall if necessary.
>>
>> I have begun to suspect that the Debian "powers that be" deliberately
>> don't make upgrading to testing/unstable/experimental clear and easy,
>> in order to discourage people from doing it. Speculating upon the
>> reasons that might be is left as an exercise for the reader . . .
>>
>> ;-)
>>
>>
>> On 1/25/16, Jochen Spieker <ml@well-adjusted.de> wrote:
>>> Francis Gerund:
>>>>
>>>> Then, I did:
>>>>
>>>> sudo check
>>>> sudo update
>>>> sudo upgrade
>>>> clean
>>>> autoclean
>>>> autoremove
>>>
>>> What are these supposed to do? I suppose they are apt operations, but
>>> don't make us guess. Always quote the exact commands you are using.
>>>
>>>> But, should I now do:
>>>>
>>>> sudo apt-get --download-only dist-upgrade
>>>> sudo dist-upgrade
>>>
>>> If you want to track testing, you will need to run dist-upgrades from
>>> time to time. If you upgrade from stable without doing that, your
>>> upgrade is incomplete. You should know that if you want to run testing.
>>>
>>>> Which brings me to my final point. I honestly thought it was a
>>>> simple,easy question, that would relatively quickly receive a simple,
>>>> easy response. I was surprised that upgrading from stable to testing
>>>> is still not a simple, clear, idiot-proof operation. After all, this
>>>> is 2016 . . . right?
>>>
>>> Do you want to make it easy to break your system? Because that's what
>>> tracking testing or unstable can do. If you run anything but stable, you
>>> need a certain set of skills so that you are able to fix many problems
>>> yourself and report issues that are not only temporary and might affect
>>> other users.
>>>
>>> J.
>>> --
>>> I am getting worse rather than better.
>>> [Agree] [Disagree]
>>>
>>> <http://archive.slowlydownward.com/NODATA/data_enter2.html>
>>>
>>
>
Reply to: