Bug 790130 - Inconsistent indenting on `repo content` command
Summary: Inconsistent indenting on `repo content` command
Keywords:
Status: CLOSED NOTABUG
Alias: None
Product: Pulp
Classification: Retired
Component: user-experience
Version: unspecified
Hardware: Unspecified
OS: Unspecified
unspecified
unspecified
Target Milestone: ---
: ---
Assignee: Todd Sanders
QA Contact: Preethi Thomas
URL:
Whiteboard:
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2012-02-13 17:55 UTC by Jay Dobies
Modified: 2013-09-27 13:56 UTC (History)
2 users (show)

Fixed In Version:
Doc Type: Bug Fix
Doc Text:
Clone Of:
Environment:
Last Closed: 2013-09-27 13:56:14 UTC


Attachments (Terms of Use)

Description Jay Dobies 2012-02-13 17:55:59 UTC
Obviously this is a low priority, but when doing a repo content call the package list isn't indented but the "none" for errata and files is.



[jdob@pulp1 ~]$ pulp-admin repo content --id pulp-f16
+------------------------------------------+
            Contents of pulp-f16
+------------------------------------------+

Packages in pulp-f16: 

pulp-consumer-0.0.266-1.fc16.noarch.rpm
gofer-package-0.65-1.fc16.noarch.rpm
pulp-selinux-server-0.0.266-1.fc16.noarch.rpm
python-isodate-0.4.4-4.pulp.fc16.noarch.rpm
python-webpy-0.32-8.fc16.noarch.rpm
mod_wsgi-3.3-3.pulp.fc16.x86_64.rpm
pulp-client-lib-0.0.266-1.fc16.noarch.rpm
python-oauth2-1.5.170-2.pulp.fc16.noarch.rpm
python-gofer-0.65-1.fc16.noarch.rpm
pulp-0.0.266-1.fc16.noarch.rpm
pulp-admin-0.0.266-1.fc16.noarch.rpm
mod_wsgi-debuginfo-3.3-3.pulp.fc16.x86_64.rpm
python-qpid-0.7.946106-1.fc16.noarch.rpm
python-rhsm-0.96.4-1.fc16.noarch.rpm
gofer-0.65-1.fc16.noarch.rpm
m2crypto-0.21.1.pulp-7.fc16.x86_64.rpm
pulp-common-0.0.266-1.fc16.noarch.rpm
grinder-0.0.136-1.fc16.noarch.rpm
pulp-cds-0.0.266-1.fc16.noarch.rpm
m2crypto-debuginfo-0.21.1.pulp-7.fc16.x86_64.rpm

Errata in pulp-f16: 

 none

Files in pulp-f16: 

 none

Comment 86 Michael Hrivnak 2013-09-27 13:56:14 UTC
This is all completely different now, so I'm closing the bug.


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