Libre RISC-V Mailing list Archives (accessible via public-inbox)
 help / color / Atom feed
From: Luke Kenneth Casson Leighton <lkcl@lkcl.net>
To: Libre-RISCV General Development <libre-riscv-dev@lists.libre-riscv.org>
Subject: Re: [libre-riscv-dev] dns entries for talos server & server maintenance
Date: Sat, 23 May 2020 03:46:31 +0100
Message-ID: <CAPweEDwpbYJq=vQD=Djv1JDCpaH9cR=2C+C5cXm1dQANSiwmOQ@mail.gmail.com> (raw)
In-Reply-To: <CAC2bXD6KYBJeMEX+R+B76zH=Tp1VyOdUv7d4hPZR7Mon=c9eKg@mail.gmail.com>

On Saturday, May 23, 2020, Jacob Lifshay <programmerjake@gmail.com> wrote:

> On Fri, May 22, 2020 at 4:02 PM Luke Kenneth Casson Leighton
> <lkcl@lkcl.net> wrote:
> >
> > just logged in: yes it's definitely running debian/testing: *really* -
> > don't ever do an "apt-get dist-upgrade" or any form of automated
> > upgrade on a debian/testing system, ever.
>
> Ok, sorry. I saw stable in the apt lists and assumed it was on debian
> stable.


the list is amalgamated, including from /etc/apt/sources.list.d so it is
necessary to really really pay attention and read every line.

the way debian works is that unless apt pinning is active, the highest
lexicographically named version of a package is picked.

so with stable *and* testing in the list, and no apt pin preferences file,
testing gets picked... unless a testing package has not been built.




>
> Also, the debian security source isn't working for some reason
> (missing file? got a 404), so that source didn't work.


either it doesn't actually exist or it is spelled wrong.



>
> So, the list of changes is in /var/log/apt/term.log I think.
> >
> > the only thing that should ever be done on a debian/testing system is
> > to see if an "apt-get install {package}" will try to replace, upgrade
> > or remove any packages, to TERMINATE that and CAREFULLY review the
> > list of package alterations.
> >
> > given that this is a shared server that is also a critical resource,
> > that process involves consulting everyone who may be affected, ok?
>
> Ok.
>
> Jacob
>
> _______________________________________________
> libre-riscv-dev mailing list
> libre-riscv-dev@lists.libre-riscv.org
> http://lists.libre-riscv.org/mailman/listinfo/libre-riscv-dev
>


-- 
---
crowd-funded eco-conscious hardware: https://www.crowdsupply.com/eoma68
_______________________________________________
libre-riscv-dev mailing list
libre-riscv-dev@lists.libre-riscv.org
http://lists.libre-riscv.org/mailman/listinfo/libre-riscv-dev

      reply index

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2020-05-22 21:21 Jacob Lifshay
2020-05-22 22:54 ` Luke Kenneth Casson Leighton
2020-05-22 23:01   ` Luke Kenneth Casson Leighton
2020-05-22 23:06     ` Luke Kenneth Casson Leighton
2020-05-23  1:08     ` Jacob Lifshay
2020-05-23  2:46       ` Luke Kenneth Casson Leighton [this message]

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to='CAPweEDwpbYJq=vQD=Djv1JDCpaH9cR=2C+C5cXm1dQANSiwmOQ@mail.gmail.com' \
    --to=lkcl@lkcl.net \
    --cc=libre-riscv-dev@lists.libre-riscv.org \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link

Libre RISC-V Mailing list Archives (accessible via public-inbox)

Archives are clonable: git clone --mirror https://inbox.libre-soc.org/libre-riscv-dev

Example config snippet for mirrors


AGPL code for this site: git clone https://public-inbox.org/public-inbox.git