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

Groups > linux.debian.user > #199069

Re: Repository Problem

From Greg Wooledge <wooledg@eeg.ccf.org>
Newsgroups linux.debian.user
Subject Re: Repository Problem
Date 2018-08-20 15:00 +0200
Message-ID <woRWN-6hk-1@gated-at.bofh.it> (permalink)
References <wnSie-3ST-1@gated-at.bofh.it> <wnT4B-4b2-3@gated-at.bofh.it> <wnUDn-5bS-5@gated-at.bofh.it>
Organization linux.* mail to news gateway

Show all headers | View raw

On Fri, Aug 17, 2018 at 10:32:39PM +0100, Brian wrote:
> On Fri 17 Aug 2018 at 21:49:53 +0200, john doe wrote:
> 
> > As an aside, you should consider using 'apt' and not 'apt-get'.
> 
> Why? What functional difference is there between 'apt-get upgrade' and
> 'apt-get install' and the apt equivalents?

I don't agree with john doe's assertion; I'm just answering the literal
question.

"apt upgrade" will install new packages, if necessary, to satisfy the
upgrade dependencies; "apt-get upgrade" will not.  This is quite visible
every time there's a new kernel ABI bump.

"apt upgrade" or "apt install ..." will remove the *.deb files that
it downloads into /var/cache/apt/archives on this particular run, but
not any pre-existing files there.  "apt-get" will not.

"apt" uses yellow text that is virtually unreadable on a white terminal
background.  "apt-get" does not; it doesn't use ANY colors.

Back to linux.debian.user | Previous | Next — Previous in thread | Next in thread | Find similar | Unroll thread

Thread

Repository Problem "Stephen P. Molnar" <s.molnar@sbcglobal.net> - 2018-08-17 21:10 +0200
  Re: Repository Problem Brian <ad44@cityscape.co.uk> - 2018-08-17 21:30 +0200
    Re: Repository Problem "Stephen P. Molnar" <s.molnar@sbcglobal.net> - 2018-08-17 21:40 +0200
      Re: Repository Problem Brian <ad44@cityscape.co.uk> - 2018-08-17 22:00 +0200
    Re: Repository Problem Roberto C. Sánchez <roberto@debian.org> - 2018-08-17 22:10 +0200
      Re: Repository Problem "Stephen P. Molnar" <s.molnar@sbcglobal.net> - 2018-08-17 23:30 +0200
  Re: Repository Problem john doe <johndoe65534@mail.com> - 2018-08-17 22:00 +0200
    Re: Repository Problem Brian <ad44@cityscape.co.uk> - 2018-08-17 23:40 +0200
      Re: Repository Problem Greg Wooledge <wooledg@eeg.ccf.org> - 2018-08-20 15:00 +0200
        Re: Repository Problem john doe <johndoe65534@mail.com> - 2018-08-20 15:30 +0200
  Re: Repository Problem David <bouncingcats@gmail.com> - 2018-08-18 12:20 +0200
    Re: Repository Problem Dan Ritter <dsr@randomstring.org> - 2018-08-18 16:30 +0200
      Re: Repository Problem "Stephen P. Molnar" <s.molnar@sbcglobal.net> - 2018-08-18 17:20 +0200
        Re: Repository Problem Reco <recoverym4n@gmail.com> - 2018-08-18 18:00 +0200
          Re: Repository Problem "Stephen P. Molnar" <s.molnar@sbcglobal.net> - 2018-08-18 19:50 +0200
            Re: Repository Problem Brian <ad44@cityscape.co.uk> - 2018-08-18 20:00 +0200
              Re: Repository Problem "Stephen P. Molnar" <s.molnar@sbcglobal.net> - 2018-08-18 21:00 +0200
                Re: Repository Problem Cindy-Sue Causey <butterflybytes@gmail.com> - 2018-08-19 03:40 +0200
                Re: Repository Problem mick crane <mick.crane@gmail.com> - 2018-08-19 06:00 +0200
                Re: Repository Problem "Stephen P. Molnar" <s.molnar@sbcglobal.net> - 2018-08-19 14:50 +0200
                Re: Repository Problem Freek de Kruijf <f.de.kruijf@gmail.com> - 2018-08-19 14:30 +0200
                Re: Repository Problem "Stephen P. Molnar" <s.molnar@sbcglobal.net> - 2018-08-19 14:50 +0200
            Re: Repository Problem Curt <curty@free.fr> - 2018-08-18 20:10 +0200
            Re: Repository Problem Reco <recoverym4n@gmail.com> - 2018-08-18 21:00 +0200

csiph-web