On Wed, Jul 11, 2018 at 3:42 PM Joe wrote:
> For a version upgrade, yes, this is Standard Operational Practice. The
> main reasoning is that the upgrade has been tested in that way i.e.
> from the final version of everything in the old distribution, and has
> not been tested from earlier software
Nicholas Geovanis:
> On Tue, Jul 10, 2018 at 3:01 PM Jochen Spieker wrote:
>>
>> There should not be that many changes, but I generally would only
>> upgrade to a newer release when the current system is up-to-date with
>> regards to its current version.
>
> I'm trying to understand your recomme
On Wed, 11 Jul 2018 11:18:48 -0500
Nicholas Geovanis wrote:
> On Tue, Jul 10, 2018 at 3:01 PM Jochen Spieker
> wrote:
> >
> > There should not be that many changes, but I generally would only
> > upgrade to a newer release when the current system is up-to-date
> > with regards to its current ver
On Wed, Jul 11, 2018 at 06:12:45PM +0200, sgarrulo wrote:
> Situation like "yeah, I'll upgrade my terminal because it's harmless", and
> then
> it stops working because I did not upgrade also lib-foo-bar-baz which is used
> by my terminal.
That exact situation would be a bug, and should be report
On Tue, 2018-07-10 at 22:00 +0200, Jochen Spieker wrote:
> sgarrulo:
> >
> > I had an installation of debian stable (stretch) which was fully upgraded
> > something
> > like a couple of months ago. Then I passed it to testing (buster).
>
> There should not be that many changes, but I generally w
On Tue, 2018-07-10 at 16:29 +0200, Hans wrote:
> Please also note, tzhat there is a difference, between using apt (apt-get)
> and
> aptitude.
>
> The way, I prefewr, is using apt-get upgrade (which installs only newer
> packages, and let the problematic ones uninstalled), then using apt-get ful
On Tue, Jul 10, 2018 at 3:01 PM Jochen Spieker wrote:
>
> There should not be that many changes, but I generally would only
> upgrade to a newer release when the current system is up-to-date with
> regards to its current version.
I'm trying to understand your recommendation. It seems you advise t
On Tue, 2018-07-10 at 10:13 -0400, The Wanderer wrote:
> If I were experiencing a similar situation, what I'd do is try to
> simultaneously install both one of the packages that triggers the
> cascade and one or more of the packages which the cascade wants to
> remove, and keep adding packages to t
On Tue, 2018-07-10 at 14:08 +0100, Joe wrote:
>
> What I do is to temporarily switch from upgrade-system to Synaptic. It
> is relatively quick to select a few innocent-looking packages from the
> big list, and check that they go through without a problem. After a few
> tries, you can see where the
sgarrulo:
>
> I had an installation of debian stable (stretch) which was fully upgraded
> something
> like a couple of months ago. Then I passed it to testing (buster).
There should not be that many changes, but I generally would only
upgrade to a newer release when the current system is up-to-da
Please also note, tzhat there is a difference, between using apt (apt-get) and
aptitude.
The way, I prefewr, is using apt-get upgrade (which installs only newer
packages, and let the problematic ones uninstalled), then using apt-get full-
upgrade.
When there are packages deinstalled, reinstall
On 2018-07-10 at 06:55, sgarrulo wrote:
> Hello everyone!
> I had an installation of debian stable (stretch) which was fully
> upgraded something like a couple of months ago. Then I passed it to
> testing (buster).
>
> Now I'm facing this situation:
> * 5031 installed packages
> * 1292 upgradabl
On Tue, Jul 10, 2018 at 09:39:44AM -0400, Cindy-Sue Causey wrote:
>
> Hi.. Been there, done that, filed a bug, got fussed at, vented here at
> Debian-User. Moral of the Story: I don't file ANY BUGS anymore. I
> spend that time advocating important subjects related to #Life
> instead. lol!
>
Sadly
On 7/10/18, sgarrulo wrote:
> Hello everyone!
> I had an installation of debian stable (stretch) which was fully upgraded
> something
> like a couple of months ago. Then I passed it to testing (buster).
>
> Now I'm facing this situation:
> * 5031 installed packages
> * 1292 upgradable packages
>
>
On Tue, 10 Jul 2018 12:55:26 +0200
sgarrulo wrote:
> Hello everyone!
> I had an installation of debian stable (stretch) which was fully
> upgraded something like a couple of months ago. Then I passed it to
> testing (buster).
>
> Now I'm facing this situation:
> * 5031 installed packages
> * 129
Hello everyone!
I had an installation of debian stable (stretch) which was fully upgraded
something
like a couple of months ago. Then I passed it to testing (buster).
Now I'm facing this situation:
* 5031 installed packages
* 1292 upgradable packages
If I do a normal upgrade, 676 packages are to
16 matches
Mail list logo
