Note: This is a beta release of Red Hat Bugzilla 5.0. The data contained within is a snapshot of the live data so any changes you make will not be reflected in the production Bugzilla. Also email is disabled so feel free to test any aspect of the site that you want. File any problems you find or give feedback here.
Bug 1691218 - too much output debug
Summary: too much output debug
Keywords:
Status: NEW
Alias: None
Product: Fedora
Classification: Fedora
Component: createrepo_c
Version: 29
Hardware: Unspecified
OS: Unspecified
unspecified
unspecified
Target Milestone: ---
Assignee: Tomas Mlcoch
QA Contact: Fedora Extras Quality Assurance
URL:
Whiteboard:
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2019-03-21 07:39 UTC by Remi Collet
Modified: 2019-12-17 15:51 UTC (History)
10 users (show)

Fixed In Version:
Doc Type: If docs needed, set a value
Doc Text:
Clone Of:
Environment:
Last Closed:


Attachments (Terms of Use)
output (deleted)
2019-03-21 07:39 UTC, Remi Collet
no flags Details

Description Remi Collet 2019-03-21 07:39:45 UTC
Created attachment 1546366 [details]
output

Since update to 0.12.2, createrepo_c generates tons of debug message.

Please revert to something useful as in previous version, or add command line option to set verbose level

Output example attached

Comment 1 Remi Collet 2019-03-21 08:16:17 UTC
Yes I have noticed the --quiet / --verbose options, so such output should obviously be in --verbose mode, keeping default output "minimal", as too much output will hide possible problems.

Comment 2 Remi Collet 2019-03-21 09:46:53 UTC
modifyrepo_c is also affected, but don't have any --quiet option :(

Comment 3 Paul Howarth 2019-03-21 11:43:22 UTC
This is now affecting F29 too.

Comment 4 amatej 2019-04-01 07:27:55 UTC
I believe there is a PR for this: https://github.com/rpm-software-management/createrepo_c/pull/141

Comment 5 Fedora Admin XMLRPC Client 2019-12-17 15:51:53 UTC
This package has changed maintainer in the Fedora.
Reassigning to the new maintainer of this component.


Note You need to log in before you can comment on or make changes to this bug.