[Bug 1716231] New: Review Request: python3-prettytable - Python
library to display tabular data in tables
by bugzilla@redhat.com
https://bugzilla.redhat.com/show_bug.cgi?id=1716231
Bug ID: 1716231
Summary: Review Request: python3-prettytable - Python library
to display tabular data in tables
Product: Fedora EPEL
Version: epel7
Hardware: All
OS: Linux
Status: NEW
Component: Package Review
Severity: medium
Assignee: nobody(a)fedoraproject.org
Reporter: redhat-bugzilla(a)linuxnetz.de
QA Contact: extras-qa(a)fedoraproject.org
CC: package-review(a)lists.fedoraproject.org
Target Milestone: ---
Classification: Fedora
Spec URL: https://labs.linuxnetz.de/bugzilla/python3-prettytable.spec
SRPM URL:
https://labs.linuxnetz.de/bugzilla/python3-prettytable-0.7.2-18.src.rpm
Description: PrettyTable is a simple Python library designed to make it quick
and easy to represent tabular data in visually appealing ASCII tables. It was
inspired by the ASCII tables used in the PostgreSQL shell psql. PrettyTable
allows for selection of which columns are to be printed, independent alignment
of columns (left or right justified or centred) and printing of "sub-tables" by
specifying a row range.
Fedora Account System Username: robert
Note: This package is only intended for EPEL 7, not for Fedora. The existing
python-prettytable package in Fedora can not be branched for EPEL 7, because a
same named source RPM package is part of RHEL. See also
https://fedoraproject.org/wiki/User:Bkabrda/EPEL7_Python3 for details. The
python3-prettytable EPEL package is mostly modelled like python-prettytable in
Fedora.
--
You are receiving this mail because:
You are on the CC list for the bug.
You are always notified about changes to this product and component
4 years, 9 months
[Bug 1447517] Review Request: ddcutil - control monitor settings
by bugzilla@redhat.com
https://bugzilla.redhat.com/show_bug.cgi?id=1447517
--- Comment #18 from sanford rockowitz <rockowitz(a)minsoft.com> ---
Actually, I was surprised to receive a message re this bug report. I stopped
receiving weekly notifications of inaction some time ago (IIRC at the time of
the f29 release), and assumed the request for sponsor was dead. I had sent a
sample review to the person who had offered to sponsor the package, annotated
with comments and questions as to how to deal with things where I disagreed
with fedora-review, e.g. the complaint about the hidden .build-id directory,
and hadn't heard back. I guess we both dropped the ball.
I have been following the Fedora developer list since the initial request for
sponsor, and it is apparent that being a Fedora packager is a major commitment.
My focus is on the upstream: fielding user questions and bug reports,
developing a GUI version and associated API, etc. I do maintain the Debian
version, which has become straightforward, but that's the extent of my official
downstream involvement. (Ubuntu picks up ddcutil from Debian, and openSuSE
picks it up because I use OBS for builds.) I'll continue to maintain a COPR
build, but for now that needs to be the extent of my Fedora efforts. Please
close the request for sponsor.
--
You are receiving this mail because:
You are on the CC list for the bug.
You are always notified about changes to this product and component
4 years, 9 months
[Bug 1447517] Review Request: ddcutil - control monitor settings
by bugzilla@redhat.com
https://bugzilla.redhat.com/show_bug.cgi?id=1447517
--- Comment #17 from sanford rockowitz <rockowitz(a)minsoft.com> ---
Re not installing a udev rule, unfortunately there is no single right thing to
do. There may already be rules in /etc/udev/rules.d that affect the /dev/i2c
devices (not all of which are necessarily for displays), and ddcutil should not
stomp over them. See http://www.ddcutil.com/i2c_permissions/ for a discussion.
A sample rules file is distributed in the package, and it is left to the user
to modify and install the file as necessary. Not great, but it's the best I
felt I could do without being the proverbial bull in the china shop.
If a rule affecting all /dev/i2c devices is to be installed automatically, it
seems to me it would be more appropriately located in package i2c-tools.
Note that command "ddcutil environment" examines the system environment,
particularly in regards to permissions, and suggests to the user what changes
they need to make to their environment.
--
You are receiving this mail because:
You are on the CC list for the bug.
You are always notified about changes to this product and component
4 years, 9 months