Re: Upgrading Jessie to Stretch

2017-03-28 Thread songbird
Michael Lange wrote:
...
> I believe that it is probably a good idea to dist-upgrade Jessie into an
> up-to-date state before starting the upgrade to Stretch, but it is
> certainly a good idea to do the intermediate steps of upgrading Squeeze
> to Wheezy first and then to Jessie before starting the upgrade to Stretch;
> with a direct upgrade Squeeze -> Stretch it is very likely (if not
> dead-sure) that you won't get far.

  jumping versions is usually not supported.

  i've tried it at times.  always have a spare
bootable partition or some other media which 
gives you net access so you can download any
new packages needed.  (but instead ... --->

  much easier to back things up you want to keep,
install from a debian installer image and then
restore what you want.

  if you have enough of a gap going back you may
want to upgrade underlying partition's file systems 
(ext2 to ext4 as just one example).


  songbird



Re: Upgrading Jessie to Stretch

2017-03-27 Thread Michael Lange
Hi,

On Mon, 27 Mar 2017 21:12:00 +
kAt  wrote:

> Is there a reason to update the current system and/or reboot with the
> updated kernel before jumping to a new system, or is everything set up
> in a way that once updated and upgraded into the target system the
> reboot will take you "up" there?
> 
> My experience has only been with various stages of Jessie into Stretch
> and I thought I risked doing this, I've had one failure which was
> probably due to an incorrect gfx-resolution adjustment, but in general
> it worked.  Like going from 8.2 or 8.5 disk installation straight into
> updated Stretch or Sid.  Let's say someone has a Debian 6 that hasn't
> been updated for a while, can they switch to testing or sid and update?

I believe that it is probably a good idea to dist-upgrade Jessie into an
up-to-date state before starting the upgrade to Stretch, but it is
certainly a good idea to do the intermediate steps of upgrading Squeeze
to Wheezy first and then to Jessie before starting the upgrade to Stretch;
with a direct upgrade Squeeze -> Stretch it is very likely (if not
dead-sure) that you won't get far.

Regards

Michael

.-.. .. ...- .   .-.. --- -. --.   .- -. -..   .--. .-. --- ... .--. . .-.

Humans do claim a great deal for that particular emotion (love).
-- Spock, "The Lights of Zetar", stardate 5725.6



Re: Upgrading Jessie to Stretch

2017-03-27 Thread kAt
Is there a reason to update the current system and/or reboot with the
updated kernel before jumping to a new system, or is everything set up
in a way that once updated and upgraded into the target system the
reboot will take you "up" there?

My experience has only been with various stages of Jessie into Stretch
and I thought I risked doing this, I've had one failure which was
probably due to an incorrect gfx-resolution adjustment, but in general
it worked.  Like going from 8.2 or 8.5 disk installation straight into
updated Stretch or Sid.  Let's say someone has a Debian 6 that hasn't
been updated for a while, can they switch to testing or sid and update?

cbannis...@slingshot.co.nz:
> On Sun, Mar 05, 2017 at 09:07:45AM -0500, songbird wrote:
>>   because i keep a second bootable partition a
>> few versions back i am a bit more brave/stupid
>> at times and just do the usual routine:
>>
>> =
>>
>>   $ apt-get update
>>   $ apt-get upgrade
>>
>>   # and then see what is held back before doing the
> 
> I suggest doing:
> 
> apt-get upgrade --with-new-pkgs
> 
> just before:
> 
>>   $ apt-get dist-upgrade
> 
> See:
> https://lists.debian.org/debian-user/2015/10/msg00279.html
> 
> :)
> 



Re: Upgrading Jessie to Stretch

2017-03-27 Thread Patrick Bartek
On Tue, 28 Mar 2017 04:54:17 +1300 cbannis...@slingshot.co.nz wrote:

> On Sun, Mar 05, 2017 at 09:07:45AM -0500, songbird wrote:
> >   because i keep a second bootable partition a
> > few versions back i am a bit more brave/stupid
> > at times and just do the usual routine:
> > 
> > =
> > 
> >   $ apt-get update
> >   $ apt-get upgrade
> > 
> >   # and then see what is held back before doing the
> 
> I suggest doing:
> 
> apt-get upgrade --with-new-pkgs
> 
> just before:
> 
> >   $ apt-get dist-upgrade
> 
> See:
> https://lists.debian.org/debian-user/2015/10/msg00279.html

I'd read the "Upgrades from Debian 8 (Jessie)" section in the Stretch
Release Notes first.  It's never as simple as changing to the new repos
and doing a dist-upgrade.

https://www.debian.org/releases/stretch/amd64/release-notes/

B



Re: Upgrading Jessie to Stretch

2017-03-27 Thread cbannister
On Sun, Mar 05, 2017 at 09:07:45AM -0500, songbird wrote:
>   because i keep a second bootable partition a
> few versions back i am a bit more brave/stupid
> at times and just do the usual routine:
> 
> =
> 
>   $ apt-get update
>   $ apt-get upgrade
> 
>   # and then see what is held back before doing the

I suggest doing:

apt-get upgrade --with-new-pkgs

just before:

>   $ apt-get dist-upgrade

See:
https://lists.debian.org/debian-user/2015/10/msg00279.html

:)

-- 
The media's the most powerful entity on earth. 
They have the power to make the innocent guilty 
and to make the guilty innocent, and that's power.
 -- Malcolm X



Re: Issues with KDE from Debian Stretch [was: Upgrading Jessie to Stretch]

2017-03-05 Thread Daniel Bareiro
Hi,

On 05/03/17 00:21, Daniel Bareiro wrote:

> Now I have some issues with KDE. I'm not sure if it have to do with the
> video driver, but when I open an application or interact with KDE, the
> image starts shaking and some areas turn black. Below a screenshot.
> 
> https://ibin.co/3ETGMDNvhA2G.png
> https://ibin.co/3ETGUxOa9reG.png
> 
> Thank you in advance for your help.

I think to have solved this.

In System Setting -> Hardware -> Display and Monitor -> Compositor, I
change the tearing prevention to "Full screen repaints".

Maybe this can be useful to someone else.


Kind regards,
Daniel



signature.asc
Description: OpenPGP digital signature


Re: Upgrading Jessie to Stretch

2017-03-05 Thread songbird
Lisi Reisz wrote:
> On Saturday 04 March 2017 22:16:49 Sven Joachim wrote:
>> Your best bet is probably to just try "apt-get dist-upgrade" and if that
>> does not work, file a bug against the upgrade-reports pseudopackage.
>
> As general advice to the nervous among us, does one 1) wait a bit; or 2) do a 
> fresh install and move data across?


 sometimes i check release docs and/or errata:

 https://www.debian.org/releases/stretch/i386/release-notes/
 
 produced via:

 https://anonscm.debian.org/viewvc/ddp/manuals/trunk/release-notes/


  i had the major changes go through so long ago 
that i don't even remember it happening (the blessing
of senility ?  :) )

  because i keep a second bootable partition a
few versions back i am a bit more brave/stupid
at times and just do the usual routine:

=

  $ apt-get update
  $ apt-get upgrade

  # and then see what is held back before doing the
  
  $ apt-get dist-upgrade

  # if the dist-upgrade reports a ton of changes i
  # might break it down into steps like doing the
  # kernel and basic tools first (by naming the
  # individual packages on the apt-get install)

  # once in a while during the past few months there
  # have been RC bugs files which made me hold some
  # packages for a few weeks to a month or so but 
  # eventually those were resolved and nothing has
  # popped up in the past few weeks.


# songbird



Re: Issues with KDE from Debian Stretch [was: Upgrading Jessie to Stretch]

2017-03-04 Thread Daniel Bareiro
Hi, Sven.

On 04/03/17 19:16, Sven Joachim wrote:

>> Given that Stretch is in the final freeze phase, I thought it was a good
>> idea to upgrade my desktop computer from Jessie to Stretch to start
>> getting used to using it.
>>
>> After updating to the latest version of stable and changing "jessie" to
>> "stretch" in sources.list, I started with the usual procedure: updating
>> APT and other utilities, to have available the improvements that have
>> been introduced.

> I'm not sure if this has actually been recommended for the last few
> releases, and for Stretch it is almost certainly a bad idea.

According to what I have documented in my Dokuwiki, it was that way used
for me to start the process of upgrading from Squeeze to Wheezy, and
from Wheezy to Jessie:


# aptitude update && aptitude dist-upgrade -V

(change "jessie" to "stretch" on /etc/apt/source.list)

# apt-get update
# apt-get install apt dpkg aptitude -V

(...)


And I had no problems on those occasions. But perhaps it is not
applicable this time.

>> # apt-get install apt dpkg aptitude -V
>>
>> But this seems to cause some VLC dependencies to break:
>>
>> 
>> Reading package lists... Done
>> Building dependency tree
>> Reading state information... Done
>> Some packages could not be installed. This may mean that you have
>> requested an impossible situation or if you are using the unstable
>> distribution that some required packages have not yet been created
>> or been moved out of Incoming.
>> The following information may help to resolve the situation:
>>
>> The following packages have unmet dependencies:
>>  libvlccore8 : Breaks: vlc (< 2.2.4-7~) but 2.2.4-1~deb8u1 is to be
>> installed
>>Breaks: vlc-nox (< 2.2.4-7~) but 2.2.4-1~deb8u1 is to be
>> installed
>> E: Error, pkgProblemResolver::Resolve generated breaks, this may be
>> caused by held packages.
>> 
>>
>> Did this happen to anyone else?

> Probably yes, because of the libstdc++6 transition[1,2] that required
> changing the package name of many C++ libraries and an unusually high
> amount of Breaks.
> 
> Your best bet is probably to just try "apt-get dist-upgrade" and if that
> does not work, file a bug against the upgrade-reports pseudopackage.
> 
> Good luck,
> Sven
> 
> 
> 1. https://lists.debian.org/debian-devel-announce/2015/07/msg0.html
> 2. https://lists.debian.org/debian-devel-announce/2015/08/msg2.html

Thanks for the references. Thanks also, Lisi, for your interest.

I've tried a different approach, starting with a minimal upgrade using
"apt-get upgrade -V", and then upgrading the kernel and udev. Finally a
complete upgrade with "apt-get dist-upgrade -V". On that way I can
upgrade without problems.

Now I have some issues with KDE. I'm not sure if it have to do with the
video driver, but when I open an application or interact with KDE, the
image starts shaking and some areas turn black. Below a screenshot.

https://ibin.co/3ETGMDNvhA2G.png
https://ibin.co/3ETGUxOa9reG.png

Thank you in advance for your help.


Kind regards,
Daniel




signature.asc
Description: OpenPGP digital signature


Re: Upgrading Jessie to Stretch

2017-03-04 Thread Lisi Reisz
On Saturday 04 March 2017 22:16:49 Sven Joachim wrote:
> Your best bet is probably to just try "apt-get dist-upgrade" and if that
> does not work, file a bug against the upgrade-reports pseudopackage.

As general advice to the nervous among us, does one 1) wait a bit; or 2) do a 
fresh install and move data across?

Lisi



Re: Upgrading Jessie to Stretch

2017-03-04 Thread Sven Joachim
On 2017-03-04 18:53 -0300, Daniel Bareiro wrote:

> Given that Stretch is in the final freeze phase, I thought it was a good
> idea to upgrade my desktop computer from Jessie to Stretch to start
> getting used to using it.
>
> After updating to the latest version of stable and changing "jessie" to
> "stretch" in sources.list, I started with the usual procedure: updating
> APT and other utilities, to have available the improvements that have
> been introduced.

I'm not sure if this has actually been recommended for the last few
releases, and for Stretch it is almost certainly a bad idea.

> # apt-get install apt dpkg aptitude -V
>
> But this seems to cause some VLC dependencies to break:
>
> 
> Reading package lists... Done
> Building dependency tree
> Reading state information... Done
> Some packages could not be installed. This may mean that you have
> requested an impossible situation or if you are using the unstable
> distribution that some required packages have not yet been created
> or been moved out of Incoming.
> The following information may help to resolve the situation:
>
> The following packages have unmet dependencies:
>  libvlccore8 : Breaks: vlc (< 2.2.4-7~) but 2.2.4-1~deb8u1 is to be
> installed
>Breaks: vlc-nox (< 2.2.4-7~) but 2.2.4-1~deb8u1 is to be
> installed
> E: Error, pkgProblemResolver::Resolve generated breaks, this may be
> caused by held packages.
> 
>
> Did this happen to anyone else?

Probably yes, because of the libstdc++6 transition[1,2] that required
changing the package name of many C++ libraries and an unusually high
amount of Breaks.

Your best bet is probably to just try "apt-get dist-upgrade" and if that
does not work, file a bug against the upgrade-reports pseudopackage.

Good luck,
Sven


1. https://lists.debian.org/debian-devel-announce/2015/07/msg0.html
2. https://lists.debian.org/debian-devel-announce/2015/08/msg2.html



Upgrading Jessie to Stretch

2017-03-04 Thread Daniel Bareiro
Hi all!

Given that Stretch is in the final freeze phase, I thought it was a good
idea to upgrade my desktop computer from Jessie to Stretch to start
getting used to using it.

After updating to the latest version of stable and changing "jessie" to
"stretch" in sources.list, I started with the usual procedure: updating
APT and other utilities, to have available the improvements that have
been introduced.

# apt-get install apt dpkg aptitude -V

But this seems to cause some VLC dependencies to break:


Reading package lists... Done
Building dependency tree
Reading state information... Done
Some packages could not be installed. This may mean that you have
requested an impossible situation or if you are using the unstable
distribution that some required packages have not yet been created
or been moved out of Incoming.
The following information may help to resolve the situation:

The following packages have unmet dependencies:
 libvlccore8 : Breaks: vlc (< 2.2.4-7~) but 2.2.4-1~deb8u1 is to be
installed
   Breaks: vlc-nox (< 2.2.4-7~) but 2.2.4-1~deb8u1 is to be
installed
E: Error, pkgProblemResolver::Resolve generated breaks, this may be
caused by held packages.


Did this happen to anyone else?


Thanks in advance.

Kind regards,
Daniel



signature.asc
Description: OpenPGP digital signature