Re: Stretch stable and jessie testing - repositories listed (new pkgs under freeze)

2017-02-10 Thread GiaThnYgeia
Brian:
> On Fri 10 Feb 2017 at 10:43:00 +, GiaThnYgeia wrote:
> 
> [We are are talking about some using the testing distribution].
> 
>> I did not upgrade this time, just left it where it is as "if it ain't
>> broke don't fix it" wondering why this is.  I think the uneasiness comes
>> from the feeling of not being able to revert things once they have been
>> broken.
> 
> You have volunteered to test testing; please take it seriously. You will
> have to upgrade sometime, if only to get to stable when it is released,

Yes, you are right and I am conscious of this obligation.  Only, with
the previous discussion on the same thread, I thought I may have done
something wrong and this was the consequence.  I did upgrade and with no
noticeable effects - yet!  I have noticed some partial slow down in the
booting routine lately, I don't know whether it is normal or not.
it seemed as it had been improved between jessie and stretch then seemed
slightly longer lately.  Not very significant of an issue.  I check and
carry upgrades twice daily lately.  I'm getting ready a second box where
I can have an equivalent built and test things 1-2 days ahead my main
box.  Down-time is expensive if work that pays the bills comes from a
single machine.

> Hello,
> Take a look at Synaptic Menu you can select a package and then go to >
Package > Force Version, you can only force one package at a time
> but, yes you can downgrade. I can down grade a couple hundred
> packages without much problem, depends on the user.

This is good to know if one can get back to synaptic after things fall
apart.  I have tried this once with a non debian package and worked once
but I had read somewhere that I couldn't or I shouldn't and took it as a
rule.  You are saying that one can go from a higher edition of debian
back to a lower edition, or are we talking about package versions within
the same edition?  Like if you dislike libreoffice5 and want to go back
to 4** I don't see how can this be done by synaptic, unless you remove 5
and download or apt-get a specific package from Libre.

> --
> Jimmy Johnson


Katrin



Re: Stretch stable and jessie testing - repositories listed (new pkgs under freeze)

2017-02-10 Thread Brian
On Fri 10 Feb 2017 at 10:43:00 +, GiaThnYgeia wrote:

[We are are talking about some using the testing distribution].

> I did not upgrade this time, just left it where it is as "if it ain't
> broke don't fix it" wondering why this is.  I think the uneasiness comes
> from the feeling of not being able to revert things once they have been
> broken.

You have volunteered to test testing; please take it seriously. You will
have to upgrade sometime, if only to get to stable when it is released,

[Snip]

> Breath deeply, exhale :)
> HTH??

The first hit on Google. :)

-- 
Brian.



Re: Stretch stable and jessie testing - repositories listed (new pkgs under freeze)

2017-02-10 Thread GiaThnYgeia


Greg Wooledge:
> On Fri, Feb 10, 2017 at 10:43:00AM +, GiaThnYgeia wrote:
>> If I understand the freeze process well (I think I
>> don't) why would updated packages appear today on the list?
> 
> The freeze means that only bug fixes go in.  No new upstream versions,
> unless it's a very special case.

Thank you, that makes perfect analog sense, to my binary thinking that
would have been a problem.

Katrin



Re: Stretch stable and jessie testing - repositories listed (new pkgs under freeze)

2017-02-10 Thread Greg Wooledge
On Fri, Feb 10, 2017 at 10:43:00AM +, GiaThnYgeia wrote:
> If I understand the freeze process well (I think I
> don't) why would updated packages appear today on the list?

The freeze means that only bug fixes go in.  No new upstream versions,
unless it's a very special case.



Re: Stretch stable and jessie testing - repositories listed (new pkgs under freeze)

2017-02-10 Thread GiaThnYgeia
Lisi Reisz:
>> In most cases documents simplify that stretch is testing,

Ok, got it, I think your post helps the archive.

I don't think I should open a new post/thread for one more
clarification.  If I understand the freeze process well (I think I
don't) why would updated packages appear today on the list?  Some about
linux-headers/image and all (important stuff for all stretch-ers). When
I replaced testing with stretch yesterday it found no needed updates.
Or are these final small modifications before the release that happen
while the freeze process is in effect?  Does the freeze strictly mean no
package transferring from sid to testing but specific tuning can be done
within the edition?  Meaning this update did not come from sid?

I did not upgrade this time, just left it where it is as "if it ain't
broke don't fix it" wondering why this is.  I think the uneasiness comes
from the feeling of not being able to revert things once they have been
broken.

> Ouch! No they don't.  Any documents that you have found that say exactly 
> that should be expunged from your mind, and they are certainly not 
> simplifying anything.  They are horribly confusing the issue.  Try to stick 
> to Debian documents (which any document saying exactly that certainly was 
> not).  As of 10/02/17 (British format - i.e. 10th February 2017) stretch is 
> testing.  But not for much longer.
> 
> Squeeze has been Testing, Stable, Old Stable, LTS and has now fallen off the 
> cliff.  (I.e. is archive only and unsupported.) 
> 
> Wheezy has been Testing - Stable - now Old Stable - then it will be LTS - 
> then 
> off the cliff.
> 
> Jessie has been Testing, is Stable, will soon be Old Stable.
> 
> Stretch is Testing, will soon be Stable.
> 
> What is now Sid will soon be Buster, but there will still be Sid, so that, 
> very briefly, Sid and Buster will be the same as each other.
> 
> You need to reread this.  Or read it if you haven't yet done so.
> https://lists.debian.org/msgid-search/20170209172439.GA9225@alum
> 
> HTH, finally,
> Lisi

Breath deeply, exhale :)
HTH??
I was referring to things I have occasionally seen on forums and debian
based distros which confuse the issue.  It is clear now, thanks to you.
I found a graph yesterday (I think it was in a link of the post you
suggest) showing the list of names in one column and old-stable, stable,
testing, unstable on the next explaining that when a release comes out
everything on the first column drops down a notch.
I think that sid being always unstable is what confuses the most of us
newbies.  It is a vicious thing that sid.