How do I make apt-get install less noisy? Announcing the arrival of Valued Associate #679:...

Can a party unilaterally change candidates in preparation for a General election?

Closed form of recurrent arithmetic series summation

What do you call the main part of a joke?

When the Haste spell ends on a creature, do attackers have advantage against that creature?

Why are both D and D# fitting into my E minor key?

Why aren't air breathing engines used as small first stages

How come Sam didn't become Lord of Horn Hill?

Dating a Former Employee

Did MS DOS itself ever use blinking text?

2001: A Space Odyssey's use of the song "Daisy Bell" (Bicycle Built for Two); life imitates art or vice-versa?

Delete nth line from bottom

Why didn't Eitri join the fight?

How do I make this wiring inside cabinet safer? (Pic)

What does the "x" in "x86" represent?

Is it ethical to give a final exam after the professor has quit before teaching the remaining chapters of the course?

Using audio cues to encourage good posture

Withdrew £2800, but only £2000 shows as withdrawn on online banking; what are my obligations?

How do I stop a creek from eroding my steep embankment?

What causes the direction of lightning flashes?

Crossing US/Canada Border for less than 24 hours

Has negative voting ever been officially implemented in elections, or seriously proposed, or even studied?

Extracting terms with certain heads in a function

How could we fake a moon landing now?

Do I really need recursive chmod to restrict access to a folder?



How do I make apt-get install less noisy?



Announcing the arrival of Valued Associate #679: Cesar Manara
Planned maintenance scheduled April 17/18, 2019 at 00:00UTC (8:00pm US/Eastern)Automatically install apt packagesDEBIAN_FRONTEND environment variablePrevent extraneous formatting of apt outputCan not write log (Is /dev/pts mounted?) - openpty in Ubuntu-on-Windows?apt held packages, can't install packageHow do I install 32-bit libraries when they keep having uninstallable dependencies?Package management system corrupted. Cannot install or remove packages. U12.04LTSPostgreSQL 9.4 hangs during installation at “Removing obsolete dictionary files:”dependency error on libc6-amd64 even if it's already installedUbuntu 15.10 The installation or removal of a software package failedApt-get not working after attempting to install kde desktopUnmet dependencies issueHow to install ATLAS on Kubuntu 18.04(Bionic)apt-get Not Working (Again)





.everyoneloves__top-leaderboard:empty,.everyoneloves__mid-leaderboard:empty,.everyoneloves__bot-mid-leaderboard:empty{ margin-bottom:0;
}







119















If I use apt-get install -qq mono-devel, I expect it to be quiet except for errors, according to the help:



-qq No output except for errors


Instead I get:



Extracting templates from packages: 100%
Selecting previously unselected package binfmt-support.
(Reading database ... 84711 files and directories currently installed.)
Unpacking binfmt-support (from .../binfmt-support_2.0.8_i386.deb) ...
Selecting previously unselected package cli-common.
Unpacking cli-common (from .../cli-common_0.8.2_all.deb) ...
Selecting previously unselected package libgdiplus.
Unpacking libgdiplus (from .../libgdiplus_2.10-3_i386.deb) ...
Selecting previously unselected package libmono-2.0-1.
Unpacking libmono-2.0-1 (from .../libmono-2.0-1_2.10.8.1-1ubuntu2.2_i386.deb) ...
Selecting previously unselected package libmono-2.0-dev.
Unpacking libmono-2.0-dev (from .../libmono-2.0-dev_2.10.8.1-1ubuntu2.2_i386.deb) ...
Selecting previously unselected package libmono-corlib4.0-cil.
Unpacking libmono-corlib4.0-cil (from .../libmono-corlib4.0-cil_2.10.8.1-1ubuntu2.2_all.deb) ...
Selecting previously unselected package libmono-system-xml4.0-cil.
Unpacking libmono-system-xml4.0-cil (from .../libmono-system-xml4.


and more...



In fact, a couple hundred lines worth of output. This does not appear to match up with no output except for errors.



How do I actually get apt-get install to print out only when there are errors keeping it from installing?










share|improve this question

























  • Have you tried using -q=# where # is a quiet level? (It's in the manual.) You may want to raise a bug report against this.

    – Paddy Landau
    Feb 26 '13 at 9:26











  • @PaddyLandau I did indeed. I don't know why it's talking about selecting previously unselected package either or why that would be important, and I'm not sure if it's related to the state of the vms I'm running this on these on either, travis-ci. But the answer worked well.

    – jbtule
    Feb 26 '13 at 13:38











  • "Selecting previously unselected package" simply means that the package manager is including a package required to satisfy dependencies. As I previously wrote, you may want to raise a bug report about the --quiet option appearing not to be working correctly.

    – Paddy Landau
    Feb 26 '13 at 17:35











  • I'm unhappy to report that same symptom in Ubuntu 15.04 20150709.

    – Lloyd Dewolf
    Aug 7 '15 at 21:02











  • Looks like this relates to 2009 dpkg issue report: bugs.debian.org/cgi-bin/bugreport.cgi?bug=539617 .

    – Lloyd Dewolf
    Aug 7 '15 at 21:18


















119















If I use apt-get install -qq mono-devel, I expect it to be quiet except for errors, according to the help:



-qq No output except for errors


Instead I get:



Extracting templates from packages: 100%
Selecting previously unselected package binfmt-support.
(Reading database ... 84711 files and directories currently installed.)
Unpacking binfmt-support (from .../binfmt-support_2.0.8_i386.deb) ...
Selecting previously unselected package cli-common.
Unpacking cli-common (from .../cli-common_0.8.2_all.deb) ...
Selecting previously unselected package libgdiplus.
Unpacking libgdiplus (from .../libgdiplus_2.10-3_i386.deb) ...
Selecting previously unselected package libmono-2.0-1.
Unpacking libmono-2.0-1 (from .../libmono-2.0-1_2.10.8.1-1ubuntu2.2_i386.deb) ...
Selecting previously unselected package libmono-2.0-dev.
Unpacking libmono-2.0-dev (from .../libmono-2.0-dev_2.10.8.1-1ubuntu2.2_i386.deb) ...
Selecting previously unselected package libmono-corlib4.0-cil.
Unpacking libmono-corlib4.0-cil (from .../libmono-corlib4.0-cil_2.10.8.1-1ubuntu2.2_all.deb) ...
Selecting previously unselected package libmono-system-xml4.0-cil.
Unpacking libmono-system-xml4.0-cil (from .../libmono-system-xml4.


and more...



In fact, a couple hundred lines worth of output. This does not appear to match up with no output except for errors.



How do I actually get apt-get install to print out only when there are errors keeping it from installing?










share|improve this question

























  • Have you tried using -q=# where # is a quiet level? (It's in the manual.) You may want to raise a bug report against this.

    – Paddy Landau
    Feb 26 '13 at 9:26











  • @PaddyLandau I did indeed. I don't know why it's talking about selecting previously unselected package either or why that would be important, and I'm not sure if it's related to the state of the vms I'm running this on these on either, travis-ci. But the answer worked well.

    – jbtule
    Feb 26 '13 at 13:38











  • "Selecting previously unselected package" simply means that the package manager is including a package required to satisfy dependencies. As I previously wrote, you may want to raise a bug report about the --quiet option appearing not to be working correctly.

    – Paddy Landau
    Feb 26 '13 at 17:35











  • I'm unhappy to report that same symptom in Ubuntu 15.04 20150709.

    – Lloyd Dewolf
    Aug 7 '15 at 21:02











  • Looks like this relates to 2009 dpkg issue report: bugs.debian.org/cgi-bin/bugreport.cgi?bug=539617 .

    – Lloyd Dewolf
    Aug 7 '15 at 21:18














119












119








119


24






If I use apt-get install -qq mono-devel, I expect it to be quiet except for errors, according to the help:



-qq No output except for errors


Instead I get:



Extracting templates from packages: 100%
Selecting previously unselected package binfmt-support.
(Reading database ... 84711 files and directories currently installed.)
Unpacking binfmt-support (from .../binfmt-support_2.0.8_i386.deb) ...
Selecting previously unselected package cli-common.
Unpacking cli-common (from .../cli-common_0.8.2_all.deb) ...
Selecting previously unselected package libgdiplus.
Unpacking libgdiplus (from .../libgdiplus_2.10-3_i386.deb) ...
Selecting previously unselected package libmono-2.0-1.
Unpacking libmono-2.0-1 (from .../libmono-2.0-1_2.10.8.1-1ubuntu2.2_i386.deb) ...
Selecting previously unselected package libmono-2.0-dev.
Unpacking libmono-2.0-dev (from .../libmono-2.0-dev_2.10.8.1-1ubuntu2.2_i386.deb) ...
Selecting previously unselected package libmono-corlib4.0-cil.
Unpacking libmono-corlib4.0-cil (from .../libmono-corlib4.0-cil_2.10.8.1-1ubuntu2.2_all.deb) ...
Selecting previously unselected package libmono-system-xml4.0-cil.
Unpacking libmono-system-xml4.0-cil (from .../libmono-system-xml4.


and more...



In fact, a couple hundred lines worth of output. This does not appear to match up with no output except for errors.



How do I actually get apt-get install to print out only when there are errors keeping it from installing?










share|improve this question
















If I use apt-get install -qq mono-devel, I expect it to be quiet except for errors, according to the help:



-qq No output except for errors


Instead I get:



Extracting templates from packages: 100%
Selecting previously unselected package binfmt-support.
(Reading database ... 84711 files and directories currently installed.)
Unpacking binfmt-support (from .../binfmt-support_2.0.8_i386.deb) ...
Selecting previously unselected package cli-common.
Unpacking cli-common (from .../cli-common_0.8.2_all.deb) ...
Selecting previously unselected package libgdiplus.
Unpacking libgdiplus (from .../libgdiplus_2.10-3_i386.deb) ...
Selecting previously unselected package libmono-2.0-1.
Unpacking libmono-2.0-1 (from .../libmono-2.0-1_2.10.8.1-1ubuntu2.2_i386.deb) ...
Selecting previously unselected package libmono-2.0-dev.
Unpacking libmono-2.0-dev (from .../libmono-2.0-dev_2.10.8.1-1ubuntu2.2_i386.deb) ...
Selecting previously unselected package libmono-corlib4.0-cil.
Unpacking libmono-corlib4.0-cil (from .../libmono-corlib4.0-cil_2.10.8.1-1ubuntu2.2_all.deb) ...
Selecting previously unselected package libmono-system-xml4.0-cil.
Unpacking libmono-system-xml4.0-cil (from .../libmono-system-xml4.


and more...



In fact, a couple hundred lines worth of output. This does not appear to match up with no output except for errors.



How do I actually get apt-get install to print out only when there are errors keeping it from installing?







apt






share|improve this question















share|improve this question













share|improve this question




share|improve this question








edited Feb 20 '13 at 14:38







jbtule

















asked Feb 19 '13 at 13:48









jbtulejbtule

6952710




6952710













  • Have you tried using -q=# where # is a quiet level? (It's in the manual.) You may want to raise a bug report against this.

    – Paddy Landau
    Feb 26 '13 at 9:26











  • @PaddyLandau I did indeed. I don't know why it's talking about selecting previously unselected package either or why that would be important, and I'm not sure if it's related to the state of the vms I'm running this on these on either, travis-ci. But the answer worked well.

    – jbtule
    Feb 26 '13 at 13:38











  • "Selecting previously unselected package" simply means that the package manager is including a package required to satisfy dependencies. As I previously wrote, you may want to raise a bug report about the --quiet option appearing not to be working correctly.

    – Paddy Landau
    Feb 26 '13 at 17:35











  • I'm unhappy to report that same symptom in Ubuntu 15.04 20150709.

    – Lloyd Dewolf
    Aug 7 '15 at 21:02











  • Looks like this relates to 2009 dpkg issue report: bugs.debian.org/cgi-bin/bugreport.cgi?bug=539617 .

    – Lloyd Dewolf
    Aug 7 '15 at 21:18



















  • Have you tried using -q=# where # is a quiet level? (It's in the manual.) You may want to raise a bug report against this.

    – Paddy Landau
    Feb 26 '13 at 9:26











  • @PaddyLandau I did indeed. I don't know why it's talking about selecting previously unselected package either or why that would be important, and I'm not sure if it's related to the state of the vms I'm running this on these on either, travis-ci. But the answer worked well.

    – jbtule
    Feb 26 '13 at 13:38











  • "Selecting previously unselected package" simply means that the package manager is including a package required to satisfy dependencies. As I previously wrote, you may want to raise a bug report about the --quiet option appearing not to be working correctly.

    – Paddy Landau
    Feb 26 '13 at 17:35











  • I'm unhappy to report that same symptom in Ubuntu 15.04 20150709.

    – Lloyd Dewolf
    Aug 7 '15 at 21:02











  • Looks like this relates to 2009 dpkg issue report: bugs.debian.org/cgi-bin/bugreport.cgi?bug=539617 .

    – Lloyd Dewolf
    Aug 7 '15 at 21:18

















Have you tried using -q=# where # is a quiet level? (It's in the manual.) You may want to raise a bug report against this.

– Paddy Landau
Feb 26 '13 at 9:26





Have you tried using -q=# where # is a quiet level? (It's in the manual.) You may want to raise a bug report against this.

– Paddy Landau
Feb 26 '13 at 9:26













@PaddyLandau I did indeed. I don't know why it's talking about selecting previously unselected package either or why that would be important, and I'm not sure if it's related to the state of the vms I'm running this on these on either, travis-ci. But the answer worked well.

– jbtule
Feb 26 '13 at 13:38





@PaddyLandau I did indeed. I don't know why it's talking about selecting previously unselected package either or why that would be important, and I'm not sure if it's related to the state of the vms I'm running this on these on either, travis-ci. But the answer worked well.

– jbtule
Feb 26 '13 at 13:38













"Selecting previously unselected package" simply means that the package manager is including a package required to satisfy dependencies. As I previously wrote, you may want to raise a bug report about the --quiet option appearing not to be working correctly.

– Paddy Landau
Feb 26 '13 at 17:35





"Selecting previously unselected package" simply means that the package manager is including a package required to satisfy dependencies. As I previously wrote, you may want to raise a bug report about the --quiet option appearing not to be working correctly.

– Paddy Landau
Feb 26 '13 at 17:35













I'm unhappy to report that same symptom in Ubuntu 15.04 20150709.

– Lloyd Dewolf
Aug 7 '15 at 21:02





I'm unhappy to report that same symptom in Ubuntu 15.04 20150709.

– Lloyd Dewolf
Aug 7 '15 at 21:02













Looks like this relates to 2009 dpkg issue report: bugs.debian.org/cgi-bin/bugreport.cgi?bug=539617 .

– Lloyd Dewolf
Aug 7 '15 at 21:18





Looks like this relates to 2009 dpkg issue report: bugs.debian.org/cgi-bin/bugreport.cgi?bug=539617 .

– Lloyd Dewolf
Aug 7 '15 at 21:18










4 Answers
4






active

oldest

votes


















73














The man page for apt-get is as follows:



NAME
apt-get - APT package handling utility -- command-line interface

SYNOPSIS
apt-get [-asqdyfmubV] [-o=config_string] [-c=config_file] [-t=target_release]
[-a=architecture] {update | upgrade | dselect-upgrade | dist-upgrade |
install pkg [{=pkg_version_number | /target_release}]... | remove pkg... |
purge pkg... | source pkg [{=pkg_version_number | /target_release}]... |
build-dep pkg [{=pkg_version_number | /target_release}]... |
download pkg [{=pkg_version_number | /target_release}]... | check | clean |
autoclean | autoremove | {-v | --version} | {-h | --help}}


The -q or -qq flag should go before the command, like so:



apt-get -qq upgrade






share|improve this answer





















  • 2





    This is the correct answer! Any practical implementation needs to preserve prompts. Used correctly, -q absolutely works (no "animated" output) as well as -qq (no output except errors). Please upvote!

    – Charney Kaye
    Aug 19 '15 at 19:18






  • 22





    No, it doesn't work. Even with -qq before the install command I still get tons of junk everything from reading database to unpacking and setting up messages.

    – CrazyCasta
    Jun 20 '16 at 23:55






  • 2





    Well, I've tried sudo apt-get -qq -y install mercurial, sudo apt-get install -qq -y mercurial, sudo apt-get -qq install -qq -y mercurial and other variations involving even more q's (though I don't see any documentation that suggests this would work. I'm running Debian Jessie on google cloud btw (8). I've also tried Goetz's answer and it doesn't seem to work either. By doesn't seem to work I mean I don't notice a difference.

    – CrazyCasta
    Jun 22 '16 at 15:49






  • 3





    This is Ubuntu 16.04.1, running as a Docker container. My guess is that the messages are actually from dpkg, which is called by apt-get. The command is apt-get -qq update && apt-get -qq upgrade && apt-get -qq install build-essential. See gist.github.com/stefanlasiewski/…

    – Stefan Lasiewski
    Dec 8 '16 at 19:13








  • 3





    In Docker you have 2 alternatives: (1) run each command separately rather than with && joining them (might work, but it's not the "docker way") (2) redirect the output to /dev/null like in the other answer. Option 2 is probably your best bet while there is this bug.

    – Mike
    Dec 9 '16 at 8:44



















53














A simple redirection could do this. It's not exactly what you had in mind, I'm sure, but it sure as hell works :)



In short, just whack > /dev/null on the end of any command where you want to redirect all the stdout into nothingness. Things outputted on stderr will still show in the console.



$ sudo apt-get update > /dev/null
[sudo] password for oli:
$


No junk! And here's what happens if we're silly and break something:



$ apt-get cheese > /dev/null
E: Invalid operation cheese
$





share|improve this answer



















  • 7





    That's a bit of a problem if you get a prompt...

    – l0b0
    Feb 19 '13 at 16:44






  • 1





    If this is part a script, you wouldn't put a sudo in front of apt-get. You would just sudo when running the script instead.

    – Xion
    Feb 19 '13 at 16:49






  • 3





    @Oli If you're absolutely sure you're not going to make your system catch on fire, you could always sudo apt-get upgrade -qq --force-yes > /dev/null. -qq implies -y, as WulfHart said, and --force-yes makes it plow through just about anything.

    – JamesTheAwesomeDude
    Feb 26 '13 at 13:46






  • 2





    @Vorac No it's just redirecting stdout (seeing the errors is a desirable thing IMO).

    – Oli
    Mar 27 '13 at 13:34






  • 3





    This is not the answer to the question; it's a workaround.

    – Charney Kaye
    Aug 19 '15 at 19:19





















37














We faced the same problem. apt-get install -qq removes most of the outputs but annoying "(Reading database ..." still persist.



We took a look in the source of apt and discover that the output is produced by dpkg that was forked by apt. Then the source of dpkg shows that the annoying soutput is only issued when isatty(1) is true. This is only the case when the fork uses pty instead pipe. Back to apt, there is a undocumented configuration variable that allows to use pipe instead pty which then solve the problem:



apt-get install -qq -o=Dpkg::Use-Pty=0 <packages>


Expecting that can help others.






share|improve this answer



















  • 2





    Actually this is full correct answer. It's also allow to run apt-get with single -q and see some output and don't see annoying "Reading database"

    – valodzka
    Sep 30 '15 at 20:26











  • @valodzka Which ubuntu version are you on? On CircleCI (with Ubuntu 14.04) it steall reads (Reading database ... 625142 files and directories currently installed.).

    – koppor
    Jan 23 '16 at 12:25











  • I tested it on Debian 8

    – valodzka
    Jan 24 '16 at 7:11






  • 1





    I'm trying this on gcloud debian jessie (8) and I still get reading database lines and unpacking/setting up lines.

    – CrazyCasta
    Jun 21 '16 at 0:09






  • 2





    This answer does not work for Ubuntu 18.04.

    – Amedee Van Gasse
    May 10 '18 at 16:06



















0














As you can see here and here

You can do:



export DEBIAN_FRONTEND=noninteractive
apt-get -yq install [packagename]
export DEBIAN_FRONTEND=dialog


Or one line:



DEBIAN_FRONTEND=noninteractive apt-get -yq install [packagename]




share








New contributor




Mark is a new contributor to this site. Take care in asking for clarification, commenting, and answering.
Check out our Code of Conduct.





















    Your Answer








    StackExchange.ready(function() {
    var channelOptions = {
    tags: "".split(" "),
    id: "89"
    };
    initTagRenderer("".split(" "), "".split(" "), channelOptions);

    StackExchange.using("externalEditor", function() {
    // Have to fire editor after snippets, if snippets enabled
    if (StackExchange.settings.snippets.snippetsEnabled) {
    StackExchange.using("snippets", function() {
    createEditor();
    });
    }
    else {
    createEditor();
    }
    });

    function createEditor() {
    StackExchange.prepareEditor({
    heartbeatType: 'answer',
    autoActivateHeartbeat: false,
    convertImagesToLinks: true,
    noModals: true,
    showLowRepImageUploadWarning: true,
    reputationToPostImages: 10,
    bindNavPrevention: true,
    postfix: "",
    imageUploader: {
    brandingHtml: "Powered by u003ca class="icon-imgur-white" href="https://imgur.com/"u003eu003c/au003e",
    contentPolicyHtml: "User contributions licensed under u003ca href="https://creativecommons.org/licenses/by-sa/3.0/"u003ecc by-sa 3.0 with attribution requiredu003c/au003e u003ca href="https://stackoverflow.com/legal/content-policy"u003e(content policy)u003c/au003e",
    allowUrls: true
    },
    onDemand: true,
    discardSelector: ".discard-answer"
    ,immediatelyShowMarkdownHelp:true
    });


    }
    });














    draft saved

    draft discarded


















    StackExchange.ready(
    function () {
    StackExchange.openid.initPostLogin('.new-post-login', 'https%3a%2f%2faskubuntu.com%2fquestions%2f258219%2fhow-do-i-make-apt-get-install-less-noisy%23new-answer', 'question_page');
    }
    );

    Post as a guest















    Required, but never shown

























    4 Answers
    4






    active

    oldest

    votes








    4 Answers
    4






    active

    oldest

    votes









    active

    oldest

    votes






    active

    oldest

    votes









    73














    The man page for apt-get is as follows:



    NAME
    apt-get - APT package handling utility -- command-line interface

    SYNOPSIS
    apt-get [-asqdyfmubV] [-o=config_string] [-c=config_file] [-t=target_release]
    [-a=architecture] {update | upgrade | dselect-upgrade | dist-upgrade |
    install pkg [{=pkg_version_number | /target_release}]... | remove pkg... |
    purge pkg... | source pkg [{=pkg_version_number | /target_release}]... |
    build-dep pkg [{=pkg_version_number | /target_release}]... |
    download pkg [{=pkg_version_number | /target_release}]... | check | clean |
    autoclean | autoremove | {-v | --version} | {-h | --help}}


    The -q or -qq flag should go before the command, like so:



    apt-get -qq upgrade






    share|improve this answer





















    • 2





      This is the correct answer! Any practical implementation needs to preserve prompts. Used correctly, -q absolutely works (no "animated" output) as well as -qq (no output except errors). Please upvote!

      – Charney Kaye
      Aug 19 '15 at 19:18






    • 22





      No, it doesn't work. Even with -qq before the install command I still get tons of junk everything from reading database to unpacking and setting up messages.

      – CrazyCasta
      Jun 20 '16 at 23:55






    • 2





      Well, I've tried sudo apt-get -qq -y install mercurial, sudo apt-get install -qq -y mercurial, sudo apt-get -qq install -qq -y mercurial and other variations involving even more q's (though I don't see any documentation that suggests this would work. I'm running Debian Jessie on google cloud btw (8). I've also tried Goetz's answer and it doesn't seem to work either. By doesn't seem to work I mean I don't notice a difference.

      – CrazyCasta
      Jun 22 '16 at 15:49






    • 3





      This is Ubuntu 16.04.1, running as a Docker container. My guess is that the messages are actually from dpkg, which is called by apt-get. The command is apt-get -qq update && apt-get -qq upgrade && apt-get -qq install build-essential. See gist.github.com/stefanlasiewski/…

      – Stefan Lasiewski
      Dec 8 '16 at 19:13








    • 3





      In Docker you have 2 alternatives: (1) run each command separately rather than with && joining them (might work, but it's not the "docker way") (2) redirect the output to /dev/null like in the other answer. Option 2 is probably your best bet while there is this bug.

      – Mike
      Dec 9 '16 at 8:44
















    73














    The man page for apt-get is as follows:



    NAME
    apt-get - APT package handling utility -- command-line interface

    SYNOPSIS
    apt-get [-asqdyfmubV] [-o=config_string] [-c=config_file] [-t=target_release]
    [-a=architecture] {update | upgrade | dselect-upgrade | dist-upgrade |
    install pkg [{=pkg_version_number | /target_release}]... | remove pkg... |
    purge pkg... | source pkg [{=pkg_version_number | /target_release}]... |
    build-dep pkg [{=pkg_version_number | /target_release}]... |
    download pkg [{=pkg_version_number | /target_release}]... | check | clean |
    autoclean | autoremove | {-v | --version} | {-h | --help}}


    The -q or -qq flag should go before the command, like so:



    apt-get -qq upgrade






    share|improve this answer





















    • 2





      This is the correct answer! Any practical implementation needs to preserve prompts. Used correctly, -q absolutely works (no "animated" output) as well as -qq (no output except errors). Please upvote!

      – Charney Kaye
      Aug 19 '15 at 19:18






    • 22





      No, it doesn't work. Even with -qq before the install command I still get tons of junk everything from reading database to unpacking and setting up messages.

      – CrazyCasta
      Jun 20 '16 at 23:55






    • 2





      Well, I've tried sudo apt-get -qq -y install mercurial, sudo apt-get install -qq -y mercurial, sudo apt-get -qq install -qq -y mercurial and other variations involving even more q's (though I don't see any documentation that suggests this would work. I'm running Debian Jessie on google cloud btw (8). I've also tried Goetz's answer and it doesn't seem to work either. By doesn't seem to work I mean I don't notice a difference.

      – CrazyCasta
      Jun 22 '16 at 15:49






    • 3





      This is Ubuntu 16.04.1, running as a Docker container. My guess is that the messages are actually from dpkg, which is called by apt-get. The command is apt-get -qq update && apt-get -qq upgrade && apt-get -qq install build-essential. See gist.github.com/stefanlasiewski/…

      – Stefan Lasiewski
      Dec 8 '16 at 19:13








    • 3





      In Docker you have 2 alternatives: (1) run each command separately rather than with && joining them (might work, but it's not the "docker way") (2) redirect the output to /dev/null like in the other answer. Option 2 is probably your best bet while there is this bug.

      – Mike
      Dec 9 '16 at 8:44














    73












    73








    73







    The man page for apt-get is as follows:



    NAME
    apt-get - APT package handling utility -- command-line interface

    SYNOPSIS
    apt-get [-asqdyfmubV] [-o=config_string] [-c=config_file] [-t=target_release]
    [-a=architecture] {update | upgrade | dselect-upgrade | dist-upgrade |
    install pkg [{=pkg_version_number | /target_release}]... | remove pkg... |
    purge pkg... | source pkg [{=pkg_version_number | /target_release}]... |
    build-dep pkg [{=pkg_version_number | /target_release}]... |
    download pkg [{=pkg_version_number | /target_release}]... | check | clean |
    autoclean | autoremove | {-v | --version} | {-h | --help}}


    The -q or -qq flag should go before the command, like so:



    apt-get -qq upgrade






    share|improve this answer















    The man page for apt-get is as follows:



    NAME
    apt-get - APT package handling utility -- command-line interface

    SYNOPSIS
    apt-get [-asqdyfmubV] [-o=config_string] [-c=config_file] [-t=target_release]
    [-a=architecture] {update | upgrade | dselect-upgrade | dist-upgrade |
    install pkg [{=pkg_version_number | /target_release}]... | remove pkg... |
    purge pkg... | source pkg [{=pkg_version_number | /target_release}]... |
    build-dep pkg [{=pkg_version_number | /target_release}]... |
    download pkg [{=pkg_version_number | /target_release}]... | check | clean |
    autoclean | autoremove | {-v | --version} | {-h | --help}}


    The -q or -qq flag should go before the command, like so:



    apt-get -qq upgrade







    share|improve this answer














    share|improve this answer



    share|improve this answer








    edited Sep 24 '15 at 12:56









    muru

    1




    1










    answered Apr 27 '15 at 20:37









    MikeMike

    86476




    86476








    • 2





      This is the correct answer! Any practical implementation needs to preserve prompts. Used correctly, -q absolutely works (no "animated" output) as well as -qq (no output except errors). Please upvote!

      – Charney Kaye
      Aug 19 '15 at 19:18






    • 22





      No, it doesn't work. Even with -qq before the install command I still get tons of junk everything from reading database to unpacking and setting up messages.

      – CrazyCasta
      Jun 20 '16 at 23:55






    • 2





      Well, I've tried sudo apt-get -qq -y install mercurial, sudo apt-get install -qq -y mercurial, sudo apt-get -qq install -qq -y mercurial and other variations involving even more q's (though I don't see any documentation that suggests this would work. I'm running Debian Jessie on google cloud btw (8). I've also tried Goetz's answer and it doesn't seem to work either. By doesn't seem to work I mean I don't notice a difference.

      – CrazyCasta
      Jun 22 '16 at 15:49






    • 3





      This is Ubuntu 16.04.1, running as a Docker container. My guess is that the messages are actually from dpkg, which is called by apt-get. The command is apt-get -qq update && apt-get -qq upgrade && apt-get -qq install build-essential. See gist.github.com/stefanlasiewski/…

      – Stefan Lasiewski
      Dec 8 '16 at 19:13








    • 3





      In Docker you have 2 alternatives: (1) run each command separately rather than with && joining them (might work, but it's not the "docker way") (2) redirect the output to /dev/null like in the other answer. Option 2 is probably your best bet while there is this bug.

      – Mike
      Dec 9 '16 at 8:44














    • 2





      This is the correct answer! Any practical implementation needs to preserve prompts. Used correctly, -q absolutely works (no "animated" output) as well as -qq (no output except errors). Please upvote!

      – Charney Kaye
      Aug 19 '15 at 19:18






    • 22





      No, it doesn't work. Even with -qq before the install command I still get tons of junk everything from reading database to unpacking and setting up messages.

      – CrazyCasta
      Jun 20 '16 at 23:55






    • 2





      Well, I've tried sudo apt-get -qq -y install mercurial, sudo apt-get install -qq -y mercurial, sudo apt-get -qq install -qq -y mercurial and other variations involving even more q's (though I don't see any documentation that suggests this would work. I'm running Debian Jessie on google cloud btw (8). I've also tried Goetz's answer and it doesn't seem to work either. By doesn't seem to work I mean I don't notice a difference.

      – CrazyCasta
      Jun 22 '16 at 15:49






    • 3





      This is Ubuntu 16.04.1, running as a Docker container. My guess is that the messages are actually from dpkg, which is called by apt-get. The command is apt-get -qq update && apt-get -qq upgrade && apt-get -qq install build-essential. See gist.github.com/stefanlasiewski/…

      – Stefan Lasiewski
      Dec 8 '16 at 19:13








    • 3





      In Docker you have 2 alternatives: (1) run each command separately rather than with && joining them (might work, but it's not the "docker way") (2) redirect the output to /dev/null like in the other answer. Option 2 is probably your best bet while there is this bug.

      – Mike
      Dec 9 '16 at 8:44








    2




    2





    This is the correct answer! Any practical implementation needs to preserve prompts. Used correctly, -q absolutely works (no "animated" output) as well as -qq (no output except errors). Please upvote!

    – Charney Kaye
    Aug 19 '15 at 19:18





    This is the correct answer! Any practical implementation needs to preserve prompts. Used correctly, -q absolutely works (no "animated" output) as well as -qq (no output except errors). Please upvote!

    – Charney Kaye
    Aug 19 '15 at 19:18




    22




    22





    No, it doesn't work. Even with -qq before the install command I still get tons of junk everything from reading database to unpacking and setting up messages.

    – CrazyCasta
    Jun 20 '16 at 23:55





    No, it doesn't work. Even with -qq before the install command I still get tons of junk everything from reading database to unpacking and setting up messages.

    – CrazyCasta
    Jun 20 '16 at 23:55




    2




    2





    Well, I've tried sudo apt-get -qq -y install mercurial, sudo apt-get install -qq -y mercurial, sudo apt-get -qq install -qq -y mercurial and other variations involving even more q's (though I don't see any documentation that suggests this would work. I'm running Debian Jessie on google cloud btw (8). I've also tried Goetz's answer and it doesn't seem to work either. By doesn't seem to work I mean I don't notice a difference.

    – CrazyCasta
    Jun 22 '16 at 15:49





    Well, I've tried sudo apt-get -qq -y install mercurial, sudo apt-get install -qq -y mercurial, sudo apt-get -qq install -qq -y mercurial and other variations involving even more q's (though I don't see any documentation that suggests this would work. I'm running Debian Jessie on google cloud btw (8). I've also tried Goetz's answer and it doesn't seem to work either. By doesn't seem to work I mean I don't notice a difference.

    – CrazyCasta
    Jun 22 '16 at 15:49




    3




    3





    This is Ubuntu 16.04.1, running as a Docker container. My guess is that the messages are actually from dpkg, which is called by apt-get. The command is apt-get -qq update && apt-get -qq upgrade && apt-get -qq install build-essential. See gist.github.com/stefanlasiewski/…

    – Stefan Lasiewski
    Dec 8 '16 at 19:13







    This is Ubuntu 16.04.1, running as a Docker container. My guess is that the messages are actually from dpkg, which is called by apt-get. The command is apt-get -qq update && apt-get -qq upgrade && apt-get -qq install build-essential. See gist.github.com/stefanlasiewski/…

    – Stefan Lasiewski
    Dec 8 '16 at 19:13






    3




    3





    In Docker you have 2 alternatives: (1) run each command separately rather than with && joining them (might work, but it's not the "docker way") (2) redirect the output to /dev/null like in the other answer. Option 2 is probably your best bet while there is this bug.

    – Mike
    Dec 9 '16 at 8:44





    In Docker you have 2 alternatives: (1) run each command separately rather than with && joining them (might work, but it's not the "docker way") (2) redirect the output to /dev/null like in the other answer. Option 2 is probably your best bet while there is this bug.

    – Mike
    Dec 9 '16 at 8:44













    53














    A simple redirection could do this. It's not exactly what you had in mind, I'm sure, but it sure as hell works :)



    In short, just whack > /dev/null on the end of any command where you want to redirect all the stdout into nothingness. Things outputted on stderr will still show in the console.



    $ sudo apt-get update > /dev/null
    [sudo] password for oli:
    $


    No junk! And here's what happens if we're silly and break something:



    $ apt-get cheese > /dev/null
    E: Invalid operation cheese
    $





    share|improve this answer



















    • 7





      That's a bit of a problem if you get a prompt...

      – l0b0
      Feb 19 '13 at 16:44






    • 1





      If this is part a script, you wouldn't put a sudo in front of apt-get. You would just sudo when running the script instead.

      – Xion
      Feb 19 '13 at 16:49






    • 3





      @Oli If you're absolutely sure you're not going to make your system catch on fire, you could always sudo apt-get upgrade -qq --force-yes > /dev/null. -qq implies -y, as WulfHart said, and --force-yes makes it plow through just about anything.

      – JamesTheAwesomeDude
      Feb 26 '13 at 13:46






    • 2





      @Vorac No it's just redirecting stdout (seeing the errors is a desirable thing IMO).

      – Oli
      Mar 27 '13 at 13:34






    • 3





      This is not the answer to the question; it's a workaround.

      – Charney Kaye
      Aug 19 '15 at 19:19


















    53














    A simple redirection could do this. It's not exactly what you had in mind, I'm sure, but it sure as hell works :)



    In short, just whack > /dev/null on the end of any command where you want to redirect all the stdout into nothingness. Things outputted on stderr will still show in the console.



    $ sudo apt-get update > /dev/null
    [sudo] password for oli:
    $


    No junk! And here's what happens if we're silly and break something:



    $ apt-get cheese > /dev/null
    E: Invalid operation cheese
    $





    share|improve this answer



















    • 7





      That's a bit of a problem if you get a prompt...

      – l0b0
      Feb 19 '13 at 16:44






    • 1





      If this is part a script, you wouldn't put a sudo in front of apt-get. You would just sudo when running the script instead.

      – Xion
      Feb 19 '13 at 16:49






    • 3





      @Oli If you're absolutely sure you're not going to make your system catch on fire, you could always sudo apt-get upgrade -qq --force-yes > /dev/null. -qq implies -y, as WulfHart said, and --force-yes makes it plow through just about anything.

      – JamesTheAwesomeDude
      Feb 26 '13 at 13:46






    • 2





      @Vorac No it's just redirecting stdout (seeing the errors is a desirable thing IMO).

      – Oli
      Mar 27 '13 at 13:34






    • 3





      This is not the answer to the question; it's a workaround.

      – Charney Kaye
      Aug 19 '15 at 19:19
















    53












    53








    53







    A simple redirection could do this. It's not exactly what you had in mind, I'm sure, but it sure as hell works :)



    In short, just whack > /dev/null on the end of any command where you want to redirect all the stdout into nothingness. Things outputted on stderr will still show in the console.



    $ sudo apt-get update > /dev/null
    [sudo] password for oli:
    $


    No junk! And here's what happens if we're silly and break something:



    $ apt-get cheese > /dev/null
    E: Invalid operation cheese
    $





    share|improve this answer













    A simple redirection could do this. It's not exactly what you had in mind, I'm sure, but it sure as hell works :)



    In short, just whack > /dev/null on the end of any command where you want to redirect all the stdout into nothingness. Things outputted on stderr will still show in the console.



    $ sudo apt-get update > /dev/null
    [sudo] password for oli:
    $


    No junk! And here's what happens if we're silly and break something:



    $ apt-get cheese > /dev/null
    E: Invalid operation cheese
    $






    share|improve this answer












    share|improve this answer



    share|improve this answer










    answered Feb 19 '13 at 14:18









    OliOli

    225k90567768




    225k90567768








    • 7





      That's a bit of a problem if you get a prompt...

      – l0b0
      Feb 19 '13 at 16:44






    • 1





      If this is part a script, you wouldn't put a sudo in front of apt-get. You would just sudo when running the script instead.

      – Xion
      Feb 19 '13 at 16:49






    • 3





      @Oli If you're absolutely sure you're not going to make your system catch on fire, you could always sudo apt-get upgrade -qq --force-yes > /dev/null. -qq implies -y, as WulfHart said, and --force-yes makes it plow through just about anything.

      – JamesTheAwesomeDude
      Feb 26 '13 at 13:46






    • 2





      @Vorac No it's just redirecting stdout (seeing the errors is a desirable thing IMO).

      – Oli
      Mar 27 '13 at 13:34






    • 3





      This is not the answer to the question; it's a workaround.

      – Charney Kaye
      Aug 19 '15 at 19:19
















    • 7





      That's a bit of a problem if you get a prompt...

      – l0b0
      Feb 19 '13 at 16:44






    • 1





      If this is part a script, you wouldn't put a sudo in front of apt-get. You would just sudo when running the script instead.

      – Xion
      Feb 19 '13 at 16:49






    • 3





      @Oli If you're absolutely sure you're not going to make your system catch on fire, you could always sudo apt-get upgrade -qq --force-yes > /dev/null. -qq implies -y, as WulfHart said, and --force-yes makes it plow through just about anything.

      – JamesTheAwesomeDude
      Feb 26 '13 at 13:46






    • 2





      @Vorac No it's just redirecting stdout (seeing the errors is a desirable thing IMO).

      – Oli
      Mar 27 '13 at 13:34






    • 3





      This is not the answer to the question; it's a workaround.

      – Charney Kaye
      Aug 19 '15 at 19:19










    7




    7





    That's a bit of a problem if you get a prompt...

    – l0b0
    Feb 19 '13 at 16:44





    That's a bit of a problem if you get a prompt...

    – l0b0
    Feb 19 '13 at 16:44




    1




    1





    If this is part a script, you wouldn't put a sudo in front of apt-get. You would just sudo when running the script instead.

    – Xion
    Feb 19 '13 at 16:49





    If this is part a script, you wouldn't put a sudo in front of apt-get. You would just sudo when running the script instead.

    – Xion
    Feb 19 '13 at 16:49




    3




    3





    @Oli If you're absolutely sure you're not going to make your system catch on fire, you could always sudo apt-get upgrade -qq --force-yes > /dev/null. -qq implies -y, as WulfHart said, and --force-yes makes it plow through just about anything.

    – JamesTheAwesomeDude
    Feb 26 '13 at 13:46





    @Oli If you're absolutely sure you're not going to make your system catch on fire, you could always sudo apt-get upgrade -qq --force-yes > /dev/null. -qq implies -y, as WulfHart said, and --force-yes makes it plow through just about anything.

    – JamesTheAwesomeDude
    Feb 26 '13 at 13:46




    2




    2





    @Vorac No it's just redirecting stdout (seeing the errors is a desirable thing IMO).

    – Oli
    Mar 27 '13 at 13:34





    @Vorac No it's just redirecting stdout (seeing the errors is a desirable thing IMO).

    – Oli
    Mar 27 '13 at 13:34




    3




    3





    This is not the answer to the question; it's a workaround.

    – Charney Kaye
    Aug 19 '15 at 19:19







    This is not the answer to the question; it's a workaround.

    – Charney Kaye
    Aug 19 '15 at 19:19













    37














    We faced the same problem. apt-get install -qq removes most of the outputs but annoying "(Reading database ..." still persist.



    We took a look in the source of apt and discover that the output is produced by dpkg that was forked by apt. Then the source of dpkg shows that the annoying soutput is only issued when isatty(1) is true. This is only the case when the fork uses pty instead pipe. Back to apt, there is a undocumented configuration variable that allows to use pipe instead pty which then solve the problem:



    apt-get install -qq -o=Dpkg::Use-Pty=0 <packages>


    Expecting that can help others.






    share|improve this answer



















    • 2





      Actually this is full correct answer. It's also allow to run apt-get with single -q and see some output and don't see annoying "Reading database"

      – valodzka
      Sep 30 '15 at 20:26











    • @valodzka Which ubuntu version are you on? On CircleCI (with Ubuntu 14.04) it steall reads (Reading database ... 625142 files and directories currently installed.).

      – koppor
      Jan 23 '16 at 12:25











    • I tested it on Debian 8

      – valodzka
      Jan 24 '16 at 7:11






    • 1





      I'm trying this on gcloud debian jessie (8) and I still get reading database lines and unpacking/setting up lines.

      – CrazyCasta
      Jun 21 '16 at 0:09






    • 2





      This answer does not work for Ubuntu 18.04.

      – Amedee Van Gasse
      May 10 '18 at 16:06
















    37














    We faced the same problem. apt-get install -qq removes most of the outputs but annoying "(Reading database ..." still persist.



    We took a look in the source of apt and discover that the output is produced by dpkg that was forked by apt. Then the source of dpkg shows that the annoying soutput is only issued when isatty(1) is true. This is only the case when the fork uses pty instead pipe. Back to apt, there is a undocumented configuration variable that allows to use pipe instead pty which then solve the problem:



    apt-get install -qq -o=Dpkg::Use-Pty=0 <packages>


    Expecting that can help others.






    share|improve this answer



















    • 2





      Actually this is full correct answer. It's also allow to run apt-get with single -q and see some output and don't see annoying "Reading database"

      – valodzka
      Sep 30 '15 at 20:26











    • @valodzka Which ubuntu version are you on? On CircleCI (with Ubuntu 14.04) it steall reads (Reading database ... 625142 files and directories currently installed.).

      – koppor
      Jan 23 '16 at 12:25











    • I tested it on Debian 8

      – valodzka
      Jan 24 '16 at 7:11






    • 1





      I'm trying this on gcloud debian jessie (8) and I still get reading database lines and unpacking/setting up lines.

      – CrazyCasta
      Jun 21 '16 at 0:09






    • 2





      This answer does not work for Ubuntu 18.04.

      – Amedee Van Gasse
      May 10 '18 at 16:06














    37












    37








    37







    We faced the same problem. apt-get install -qq removes most of the outputs but annoying "(Reading database ..." still persist.



    We took a look in the source of apt and discover that the output is produced by dpkg that was forked by apt. Then the source of dpkg shows that the annoying soutput is only issued when isatty(1) is true. This is only the case when the fork uses pty instead pipe. Back to apt, there is a undocumented configuration variable that allows to use pipe instead pty which then solve the problem:



    apt-get install -qq -o=Dpkg::Use-Pty=0 <packages>


    Expecting that can help others.






    share|improve this answer













    We faced the same problem. apt-get install -qq removes most of the outputs but annoying "(Reading database ..." still persist.



    We took a look in the source of apt and discover that the output is produced by dpkg that was forked by apt. Then the source of dpkg shows that the annoying soutput is only issued when isatty(1) is true. This is only the case when the fork uses pty instead pipe. Back to apt, there is a undocumented configuration variable that allows to use pipe instead pty which then solve the problem:



    apt-get install -qq -o=Dpkg::Use-Pty=0 <packages>


    Expecting that can help others.







    share|improve this answer












    share|improve this answer



    share|improve this answer










    answered Sep 3 '15 at 14:11









    Philippe GoetzPhilippe Goetz

    38132




    38132








    • 2





      Actually this is full correct answer. It's also allow to run apt-get with single -q and see some output and don't see annoying "Reading database"

      – valodzka
      Sep 30 '15 at 20:26











    • @valodzka Which ubuntu version are you on? On CircleCI (with Ubuntu 14.04) it steall reads (Reading database ... 625142 files and directories currently installed.).

      – koppor
      Jan 23 '16 at 12:25











    • I tested it on Debian 8

      – valodzka
      Jan 24 '16 at 7:11






    • 1





      I'm trying this on gcloud debian jessie (8) and I still get reading database lines and unpacking/setting up lines.

      – CrazyCasta
      Jun 21 '16 at 0:09






    • 2





      This answer does not work for Ubuntu 18.04.

      – Amedee Van Gasse
      May 10 '18 at 16:06














    • 2





      Actually this is full correct answer. It's also allow to run apt-get with single -q and see some output and don't see annoying "Reading database"

      – valodzka
      Sep 30 '15 at 20:26











    • @valodzka Which ubuntu version are you on? On CircleCI (with Ubuntu 14.04) it steall reads (Reading database ... 625142 files and directories currently installed.).

      – koppor
      Jan 23 '16 at 12:25











    • I tested it on Debian 8

      – valodzka
      Jan 24 '16 at 7:11






    • 1





      I'm trying this on gcloud debian jessie (8) and I still get reading database lines and unpacking/setting up lines.

      – CrazyCasta
      Jun 21 '16 at 0:09






    • 2





      This answer does not work for Ubuntu 18.04.

      – Amedee Van Gasse
      May 10 '18 at 16:06








    2




    2





    Actually this is full correct answer. It's also allow to run apt-get with single -q and see some output and don't see annoying "Reading database"

    – valodzka
    Sep 30 '15 at 20:26





    Actually this is full correct answer. It's also allow to run apt-get with single -q and see some output and don't see annoying "Reading database"

    – valodzka
    Sep 30 '15 at 20:26













    @valodzka Which ubuntu version are you on? On CircleCI (with Ubuntu 14.04) it steall reads (Reading database ... 625142 files and directories currently installed.).

    – koppor
    Jan 23 '16 at 12:25





    @valodzka Which ubuntu version are you on? On CircleCI (with Ubuntu 14.04) it steall reads (Reading database ... 625142 files and directories currently installed.).

    – koppor
    Jan 23 '16 at 12:25













    I tested it on Debian 8

    – valodzka
    Jan 24 '16 at 7:11





    I tested it on Debian 8

    – valodzka
    Jan 24 '16 at 7:11




    1




    1





    I'm trying this on gcloud debian jessie (8) and I still get reading database lines and unpacking/setting up lines.

    – CrazyCasta
    Jun 21 '16 at 0:09





    I'm trying this on gcloud debian jessie (8) and I still get reading database lines and unpacking/setting up lines.

    – CrazyCasta
    Jun 21 '16 at 0:09




    2




    2





    This answer does not work for Ubuntu 18.04.

    – Amedee Van Gasse
    May 10 '18 at 16:06





    This answer does not work for Ubuntu 18.04.

    – Amedee Van Gasse
    May 10 '18 at 16:06











    0














    As you can see here and here

    You can do:



    export DEBIAN_FRONTEND=noninteractive
    apt-get -yq install [packagename]
    export DEBIAN_FRONTEND=dialog


    Or one line:



    DEBIAN_FRONTEND=noninteractive apt-get -yq install [packagename]




    share








    New contributor




    Mark is a new contributor to this site. Take care in asking for clarification, commenting, and answering.
    Check out our Code of Conduct.

























      0














      As you can see here and here

      You can do:



      export DEBIAN_FRONTEND=noninteractive
      apt-get -yq install [packagename]
      export DEBIAN_FRONTEND=dialog


      Or one line:



      DEBIAN_FRONTEND=noninteractive apt-get -yq install [packagename]




      share








      New contributor




      Mark is a new contributor to this site. Take care in asking for clarification, commenting, and answering.
      Check out our Code of Conduct.























        0












        0








        0







        As you can see here and here

        You can do:



        export DEBIAN_FRONTEND=noninteractive
        apt-get -yq install [packagename]
        export DEBIAN_FRONTEND=dialog


        Or one line:



        DEBIAN_FRONTEND=noninteractive apt-get -yq install [packagename]




        share








        New contributor




        Mark is a new contributor to this site. Take care in asking for clarification, commenting, and answering.
        Check out our Code of Conduct.










        As you can see here and here

        You can do:



        export DEBIAN_FRONTEND=noninteractive
        apt-get -yq install [packagename]
        export DEBIAN_FRONTEND=dialog


        Or one line:



        DEBIAN_FRONTEND=noninteractive apt-get -yq install [packagename]





        share








        New contributor




        Mark is a new contributor to this site. Take care in asking for clarification, commenting, and answering.
        Check out our Code of Conduct.








        share


        share






        New contributor




        Mark is a new contributor to this site. Take care in asking for clarification, commenting, and answering.
        Check out our Code of Conduct.









        answered 4 mins ago









        MarkMark

        1




        1




        New contributor




        Mark is a new contributor to this site. Take care in asking for clarification, commenting, and answering.
        Check out our Code of Conduct.





        New contributor





        Mark is a new contributor to this site. Take care in asking for clarification, commenting, and answering.
        Check out our Code of Conduct.






        Mark is a new contributor to this site. Take care in asking for clarification, commenting, and answering.
        Check out our Code of Conduct.






























            draft saved

            draft discarded




















































            Thanks for contributing an answer to Ask Ubuntu!


            • Please be sure to answer the question. Provide details and share your research!

            But avoid



            • Asking for help, clarification, or responding to other answers.

            • Making statements based on opinion; back them up with references or personal experience.


            To learn more, see our tips on writing great answers.




            draft saved


            draft discarded














            StackExchange.ready(
            function () {
            StackExchange.openid.initPostLogin('.new-post-login', 'https%3a%2f%2faskubuntu.com%2fquestions%2f258219%2fhow-do-i-make-apt-get-install-less-noisy%23new-answer', 'question_page');
            }
            );

            Post as a guest















            Required, but never shown





















































            Required, but never shown














            Required, but never shown












            Required, but never shown







            Required, but never shown

































            Required, but never shown














            Required, but never shown












            Required, but never shown







            Required, but never shown







            Popular posts from this blog

            Is there a lightweight tool to crop images quickly?Cropping Images using Command Line Tools OnlyHow to crop...

            List of shipwrecks in 1808...

            Unit packagekit.service is masked Announcing the arrival of Valued Associate #679: Cesar...