Postings by Praveen Kumar

Orphaning python-grapefruit


I am not consuming that package and not able to update it. Time which
i can dedicate to Fedora side is dropped for me now and I am not even
sure how long it would be the case so I hope `python-grapefruit` will
find an another package maintainer.

Package orphaned (python-flask-wtf, python-html5lib, gnome-pie, transgui)


I am not able to maintain some of the packages and now ready to take
by a different package maintainer.

- python-flask-wtf
- python-html5lib
- gnome-pie
- transgui

Docker daemon not respecting the insecure registry which is part of /etc/containers/registry.conf


I spun up a fresh centos-7.5 VM on Digital ocean and tried to do oc
cluster up which require to have insecure registry ``
when I am trying to add this in the /etc/containers/registry.conf this
is not picked up by docker daemon even after restart:(

I can see we have `/run/containers/registries.conf` as env file in the
`/usr/lib/systemd/system/docker.service` which even not present on the
system :(

Not sure where we messed up or I made some mistake here.

# rpm -qa | grep docker

Pulling docker images from fails because of certs


I think with the recent change in the package from
python-rhsm-certificates to subscription-manager-rhsm-certificates
doesn't provide the docker registry certs for and user not able to pull any images from

docker and podman packages should be part of virt7-container-common-candidate or extra repos.


I can see docker packages are part of
virt7-container-common-candidate[0] and also extra[1] repo same with
podman but on the virt repo side docker packages are not updated to
latest version and for podman extra repo doesn't have latest packages.
It becomes really confusing what repo to chose when installing those
packages and if we include both repos then there is conflict:(

[0] <a href="" title=""></a>
[1] <a href="" title=""></a>

Transaction couldn't start:
10:06:29 file /usr/libexec/cni/bri

Latest podman installation broken in CentOS


Looks like there might be issue with spec file of the podman for
CentOS because of wrongly put the "Requires" version for *conmon* but
this is what I am getting now when trying to install podman :(

$ sudo yum install podman
--> Finished Dependency Resolution
Error: Package: podman-0.5.3-7.gitc54b423.el7.x86_64
Requires: conmon >= 2:1.10.0-3.gitb0f6d98
Installed: conmon-1.11.0-1.git55a3daa.el7.x86_64
conmon = 1.11.0-1.git55a3daa.el7
You could try using --skip-broken to work a

LIS vs hyperv-daemons for Centos


Past 2 days we are trying to debug why our live centos images[0] is
not working with hyperV and facing issue similar to [1]. After reading
I was confuse that should we need to add Linux Integration Services
(LIS) also during our live images creation or hyperv-daemons would be
enough for us[2]. I tried to include hyperv-daemons package and even
kvpd service running but still communication not happening from the

Atomic Developer Bundle 2.3.0 released

We are pleased to release the Atomic Developer Bundle 2.3.0 through
CentOS Atomic SIG.

Atomic Developer Bundle consists of a Vagrant-box and couple of
Vagrant plugins.

Major release number bump is lower than beta for html5lib module.


Recently Dan filled bug[0] against html5lib[1] module about new
upstream release but upstream put major version 0.999 which is lower
that it's beta version 1.0b3.

Now If I update spec file according to upstream release version should
yum able to identify that 0.999 > 1.0b3? or should I go ahead and make
change as Dan suggested to use version 1.0b3-0.999?

[0] <a href="" title=""></a>
[1] <a href="" title=""></a>

Python Package Review Swap

Hi folks,

python-jenkinsapi [0] up for review.

[0] <a href="" title=""></a>

Review request of python-modargs package

Hi folks,

Can someone review (Formal/Assign) of python-modargs package.

BZ: <a href="" title=""></a>

Thanks in advance.

Handle sonames


I am working on to package python-pylibmc [0], Please tell me how to handle
soname for this package.

<a href="" title=""></a>
[1] <a href="" title=""></a>

Thanks and Regards
Praveen Kumar
<a href="" title=""></a>

Regarding Funnel packaging


I am planning to package funnel[0], a software for online submissions
and voting of talks as part of the FUDCon India effort but I am not
familiar with the structure of wsgi. Can someone please give me
guidance on how to package this source.

[0] <a href="" title=""></a>

Thanks and Regards
Praveen Kumar
<a href="" title=""></a>
<a href="" title=""></a>

Handling lamson


I am planning to package funnel, a software for online submissions and
voting of talks as part of the FUDCon India effort. One if its
dependencies is flask-mail[0] and in turn, lamson[1] is a dependency
for it which was already in Fedora briefly but now it's orphaned due
to some resistance from upstream. Without packaging lamson, we cannot
package many modules that are dependent on it. Debian[2], Ubuntu and
others distros have however packaged it already. What is the best way

Problem with noarch package


I made a spec file for torrent-search source and then I build it using
koji [0] and it successfully build but package is noarch and I used
hard coding (/usr/lib) instead of macro.

G15Tools Packaging

On fedora package wish-list this package is listed. I tried to compile
its source after installing all its dependencies but its showing me
error during make

# make
make all-recursive
make[1]: Entering directory `/home/daredevil/g15tools/trunk/G15Tools++'
Making all in src
make[2]: Entering directory `/home/daredevil/g15tools/trunk/G15Tools++/src'
/bin/sh ../libtool --tag=CXX --mode=compile g++ -DHAVE_CONFIG_H -I.
-I.. -g -O2 -MT G15Canvas.lo -MD -MP -MF .deps/G15Canvas.Tpo -c -o
G15Canvas.lo G15Canvas.cpp
libtool: compile: g++ -DHAVE_CONFIG_H -I. -I..