Groups | Search | Server Info | Keyboard shortcuts | Login | Register [http] [https] [nntp] [nntps]

Groups > linux.debian.user > #158125 > unrolled thread

Re: Jessie update notes?

Back to article view | Back to linux.debian.user

This discussion starts older than the indexed window; earlier articles aren't shown. The article labeled Started by below is the oldest one visible, not the original post.

Contents

  Re: Jessie update notes? Cindy-Sue Causey <butterflybytes@gmail.com> - 2015-09-21 18:10 +0200
    Re: Jessie update notes? Lisi Reisz <lisi.reisz@gmail.com> - 2015-09-21 18:20 +0200
      CORRECTION Re: Jessie update notes? Lisi Reisz <lisi.reisz@gmail.com> - 2015-09-21 19:00 +0200

#158125 — Re: Jessie update notes?

On 9/10/15, Hannu Virtanen <hannu_markus_virtanen@yahoo.com> wrote:
> With 'wheezy' I got always notes when updates were available.
>
> What should I do to get 'Jessie' checking every day, if updates are
> available?


I've read all the other helpful feedback you received. Are you
interested in taking control of the process manually via terminal? I
learned a COOL command that was originally shared by *Bob* who
coincidentally responded to this thread.

Am sharing here in case it's of interest to anyone checking out your
thread. The package you download is "apt-show-versions".

If you then run "apt-get update" and next "apt-show-versions -u", you
receive output of any packages that need upgrading. If there's no
output, everything in your system is current. There are other flags
(options) you can run, but so far that "-u" is all I've ever needed.

You have to run both commands each time. "apt-show-versions" performs
its package version comparison walk through our systems based on both
what is sitting on our systems and what our personal *_CHOICE_* of
repositories is offering at any given second. BUT.. That doesn't
happen magically/automatically, it's triggered manually in this case.
The only way that happens is if we run "apt-get update" first to keep
that command's associated files current, as well.

If that method collides with the method you're using and/or seeking,
my apologies. It's the only way I do this now. I LOVE IT, I love the
total control it FEELS LIKE it gives me. *grin*

Cindy :)

PS For the curious, the update related files are found in: /var/lib/apt/lists/

If there's anything sitting still in the "partial" directory, it
shouldn't be there. You'll only see something blip through there at a
rate that's reflective of your Internet connection speed. If you run
update one more time and something is still sitting incomplete under
"partial", wouldn't hurt to nose around to find out why it's still
there. The answer can be as simple as Internet connectivity problems
not letting temporary, dynamically named partial files complete their
download process..

-- 
Cindy-Sue Causey
Talking Rock, Pickens County, Georgia, USA

* runs with plastic sporks *

[toc] | [next] | [standalone]

#158127

On Monday 21 September 2015 16:59:40 Cindy-Sue Causey wrote:
> I've read all the other helpful feedback you received. Are you
> interested in taking control of the process manually via terminal? I
> learned a COOL command that was originally shared by *Bob* who
> coincidentally responded to this thread.
>
> Am sharing here in case it's of interest to anyone checking out your
> thread. The package you download is "apt-show-versions".
>
> If you then run "apt-get update" and next "apt-show-versions -u", you
> receive output of any packages that need upgrading. If there's no
> output, everything in your system is current. There are other flags
> (options) you can run, but so far that "-u" is all I've ever needed.
>
> You have to run both commands each time. "apt-show-versions" performs
> its package version comparison walk through our systems based on both
> what is sitting on our systems and what our personal *_CHOICE_* of
> repositories is offering at any given second. BUT.. That doesn't
> happen magically/automatically, it's triggered manually in this case.
> The only way that happens is if we run "apt-get update" first to keep
> that command's associated files current, as well.

Alternatively, you can just do "aptitude update", and it will tell you what 
upgrades are available when it has finished updating. ;-)  If it doesn't tell 
you, it means that there aren't any.

Lisi

[toc] | [prev] | [next] | [standalone]

#158133 — CORRECTION Re: Jessie update notes?

On Monday 21 September 2015 17:16:54 Lisi Reisz wrote:
> On Monday 21 September 2015 16:59:40 Cindy-Sue Causey wrote:
> > I've read all the other helpful feedback you received. Are you
> > interested in taking control of the process manually via terminal? I
> > learned a COOL command that was originally shared by *Bob* who
> > coincidentally responded to this thread.
> >
> > Am sharing here in case it's of interest to anyone checking out your
> > thread. The package you download is "apt-show-versions".
> >
> > If you then run "apt-get update" and next "apt-show-versions -u", you
> > receive output of any packages that need upgrading. If there's no
> > output, everything in your system is current. There are other flags
> > (options) you can run, but so far that "-u" is all I've ever needed.
> >
> > You have to run both commands each time. "apt-show-versions" performs
> > its package version comparison walk through our systems based on both
> > what is sitting on our systems and what our personal *_CHOICE_* of
> > repositories is offering at any given second. BUT.. That doesn't
> > happen magically/automatically, it's triggered manually in this case.
> > The only way that happens is if we run "apt-get update" first to keep
> > that command's associated files current, as well.
>
> Alternatively, you can just do "aptitude update", and it will tell you 

> <what >

<that>
sorry, typo.
Lisi
> upgrades are available when it has finished updating. ;-)  If it doesn't
> tell you, it means that there aren't any.
>
> Lisi

[toc] | [prev] | [standalone]

Back to top | Article view | linux.debian.user

csiph-web