Gentoo Websites Logo
Go to: Gentoo Home Documentation Forums Lists Bugs Planet Store Wiki Get Gentoo!
Bug 285614 - emerge --fetchonly --quiet is too verbose
Summary: emerge --fetchonly --quiet is too verbose
Status: RESOLVED FIXED
Alias: None
Product: Portage Development
Classification: Unclassified
Component: Core - Interface (emerge) (show other bugs)
Hardware: All Linux
: High minor
Assignee: Portage team
URL:
Whiteboard:
Keywords: InVCS
Depends on:
Blocks: 377365 785484
  Show dependency tree
 
Reported: 2009-09-19 18:52 UTC by Darren Smith
Modified: 2021-07-05 01:37 UTC (History)
0 users

See Also:
Package list:
Runtime testing required: ---


Attachments

Note You need to log in before you can comment on or make changes to this bug.
Description Darren Smith 2009-09-19 18:52:10 UTC
I have a cronjob that after syncing fetches new packages. The problem is that it often (not always) outputs a lot of download gibberish.

I'm using the following:
/usr/bin/emerge --update --deep --with-bdeps=y --reinstall changed-use --quiet --fetchonly world

I have the following features set:
FEATURES="severe strict parallel-fetch userfetch"

This is an example of what I get:
>>> Fetching (1 of 10) media-libs/tiff-3.9.1
--2009-09-19 08:01:01--  http://gentoo.osuosl.org/distfiles/tiff-3.9.1.tar.gz
Resolving gentoo.osuosl.org... 64.50.236.52
Connecting to gentoo.osuosl.org|64.50.236.52|:80... connected.
HTTP request sent, awaiting response... 200 OK
Length: 1410331 (1.3M) [application/x-gzip]
Saving to: `/usr/portage/distfiles/tiff-3.9.1.tar.gz'

     0K .......... .......... .......... .......... ..........  3%  231K 6s
    50K .......... .......... .......... .......... ..........  7%  309K 5s
   100K .......... .......... .......... .......... .......... 10%  313K 4s
   150K .......... .......... .......... .......... .......... 14%  309K 4s
   200K .......... .......... .......... .......... .......... 18%  313K 4s
   250K .......... .......... .......... .......... .......... 21%  309K 4s
   300K .......... .......... .......... .......... .......... 25%  305K 3s
   350K .......... .......... .......... .......... .......... 29%  317K 3s
   400K .......... .......... .......... .......... .......... 32%  306K 3s
   450K .......... .......... .......... .......... .......... 36%  317K 3s
   500K .......... .......... .......... .......... .......... 39%  306K 3s
   550K .......... .......... .......... .......... .......... 43%  317K 3s
   600K .......... .......... .......... .......... .......... 47%  306K 2s
   650K .......... .......... .......... .......... .......... 50%  317K 2s
   700K .......... .......... .......... .......... .......... 54%  305K 2s
   750K .......... .......... .......... .......... .......... 58%  309K 2s
   800K .......... .......... .......... .......... .......... 61%  313K 2s
   850K .......... .......... .......... .......... .......... 65%  309K 2s
   900K .......... .......... .......... .......... .......... 68%  313K 1s
   950K .......... .......... .......... .......... .......... 72%  309K 1s
  1000K .......... .......... .......... .......... .......... 76%  313K 1s
  1050K .......... .......... .......... .......... .......... 79%  309K 1s
  1100K .......... .......... .......... .......... .......... 83%  313K 1s
  1150K .......... .......... .......... .......... .......... 87%  310K 1s
  1200K .......... .......... .......... .......... .......... 90%  126K 0s
  1250K .......... .......... .......... .......... .......... 94%  478K 0s
  1300K .......... .......... .......... .......... .......... 98%  719K 0s
  1350K .......... .......... .......                         100% 79.7M=4.5s

2009-09-19 08:01:06 (307 KB/s) - `/usr/portage/distfiles/tiff-3.9.1.tar.gz' saved [1410331/1410331]

I'm ok with the ">>> Fetching" line, but the rest should be eliminated when using --quiet. Sometimes, I only get the fetching lines. My guess is that it has to do with either the parallel-fetch or userfetch feature.

Reproducible: Always
Comment 1 Zac Medico gentoo-dev 2009-09-19 22:39:09 UTC
I guess we can redirect the fetcher output to /var/log/emerge-fetch.log.
Comment 2 Darren Smith 2009-09-20 11:53:56 UTC
(In reply to comment #1)
> I guess we can redirect the fetcher output to /var/log/emerge-fetch.log.

That would be fine with me. Thanks!
Comment 3 James Stevenson 2021-05-13 10:07:26 UTC
I've created a PR with a fix for this bug. It was approved yesterday.

https://github.com/gentoo/portage/pull/707
Comment 4 Larry the Git Cow gentoo-dev 2021-05-16 22:29:11 UTC
The bug has been referenced in the following commit(s):

https://gitweb.gentoo.org/proj/portage.git/commit/?id=e26a08896f098ff93530efcd2d77d60d2eff0257

commit e26a08896f098ff93530efcd2d77d60d2eff0257
Author:     James Stevenson <james.al.stevenson@gmail.com>
AuthorDate: 2021-05-16 10:58:13 +0000
Commit:     Zac Medico <zmedico@gentoo.org>
CommitDate: 2021-05-16 22:27:15 +0000

    emerge --fetchonly --quiet: use emerge-fetch.log when writable (bug 285614)
    
    Closes: https://github.com/gentoo/portage/pull/707
    Bug: https://bugs.gentoo.org/285614
    Signed-off-by: James Stevenson <james.al.stevenson@gmail.com>
    Signed-off-by: Zac Medico <zmedico@gentoo.org>

 lib/_emerge/EbuildBuild.py | 25 +++++++++++++++++++++----
 lib/_emerge/Scheduler.py   |  4 ++--
 2 files changed, 23 insertions(+), 6 deletions(-)