Groups > linux.debian.user > #200354

Re: Unstable update ridiculousness

From	Default User <hunguponcontent@gmail.com>
Newsgroups	linux.debian.user
Subject	Re: Unstable update ridiculousness
Date	2018-09-20 22:00 +0200
Message-ID	<wAdhf-7k3-7@gated-at.bofh.it> (permalink)
References	(1 earlier) <wzVDH-5Ca-3@gated-at.bofh.it> <wzVNn-5F3-3@gated-at.bofh.it> <wA1g5-xf-3@gated-at.bofh.it> <wA72a-3Ro-5@gated-at.bofh.it> <wA7vb-40B-1@gated-at.bofh.it>
Organization	linux.* mail to news gateway

Show all headers | View raw

[Multipart message — attachments visible in raw view] - view raw

>
>
>
Hi guys. Thank you for your replies.

Please note that I am really not familiar with either cron or (especially)
with package pinning.

Using advice given, using apt-listings and aptitude full-update, l was able
to update everything except the 3 packages in question, which are now
"pinned", with a priority of 3000.

I do have both cron and anacron installed, but have never used or done
anything to configure them. Note: the computer in question is not on 24/7,
but is normally on part of every day. Thus anacron, per the apt-listbugs
man page.

If I understand correctly, a cron job has been created automatically, which
will check each day automatically, and automatically in-pin the packages in
question when they are eligible for upgrade. Is this correct?

If not, will I have to manually delete the cron job in question and/or
manually edit/delete the package pinning, once the packages in question
have been upgraded?

Finally, how can I verify that said cron job was created and enabled
(correctly)?

Thread

Unstable update ridiculousness Default User <hunguponcontent@gmail.com> - 2018-09-20 03:00 +0200
  Re: Unstable update ridiculousness John Hasler <jhasler@newsguy.com> - 2018-09-20 03:10 +0200
    Re: Unstable update ridiculousness Default User <hunguponcontent@gmail.com> - 2018-09-20 03:20 +0200
      Re: Unstable update ridiculousness didier gaumet <didier.gaumet@gmail.com> - 2018-09-20 09:10 +0200
        Re: Unstable update ridiculousness John Hasler <jhasler@newsguy.com> - 2018-09-20 15:20 +0200
          Re: Unstable update ridiculousness Roberto C. Sánchez <roberto@debian.org> - 2018-09-20 15:50 +0200
            Re: Unstable update ridiculousness Default User <hunguponcontent@gmail.com> - 2018-09-20 22:00 +0200
              Re: Unstable update ridiculousness Ben Caradoc-Davies <ben@transient.nz> - 2018-09-21 00:40 +0200
                Re: Unstable update ridiculousness Default User <hunguponcontent@gmail.com> - 2018-09-21 07:10 +0200
      Re: Unstable update ridiculousness Joe <joe@jretrading.com> - 2018-09-20 10:00 +0200
  Re: Unstable update ridiculousness Ben Caradoc-Davies <ben@transient.nz> - 2018-09-20 03:30 +0200
    Re: Unstable update ridiculousness Joe <joe@jretrading.com> - 2018-09-20 10:10 +0200

csiph-web