Postings by Jan Chaloupka

What branches are under Go pressure. Did we forget about epel7?


Since F17, golang started to get attention in Fedora distribution. Long
way was travelled since with currently activelly maintaining f22+ and
el6 branches. The number of Go projects packaged in Fedora grown to more
than 250 packages. The current effort is to keep in shape all activelly
managed branches including el6. As the Golang language is spreading
across new architectures, new challenges pop up. With 250 packages in
distribution we have a free source of Go source code to play with and
run various analysis on.

Help with testing current kubernetes for f23


it has been a while since kubernetes was pushed to f23 stable
repository. This is the first suitable build after more than half a year.

Any help with testing and adding positive karmas is appreciated. Update
is located here [1].

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


Golang packaging: now and the future

Hi guys,

at the moment there is approximately 250 packages shipping projects
written in go. In general, each project has its own set of dependencies
and provided import paths (golang packages). As usually each package has
four active branches. Thus, we are dealing with approximately 1000 spec
files, all potential candidates for rebases/updates and bug fixes. Each
update can break backward compatibility. Some projects may require
different commits of the same dependency.

What are the most hot packaging problems in the golang ecosystem?
- bundled vs. some links does not work


in section "Duplication of system libraries", both links to "No Bundled
Libraries<>" and
"Treatment Of Bundled Libraries" do not work.


new go-compilers package

Hi everyone,

I would like to introduce go-compilers packages.

- golang language is supported on primary and secondary architectures
- at the moment we have two compilers: golang and gcc-go
- on Fedora we have a partial support for debugging
- go-srpm-macros packages provides basic macros (go_arches,
golang_arches, gcc_go_arches, ...)
- f21, f22, f23, rawhide, el6 are supported. Fedora is primary, el6 is
almost 1:1 with fedora branches (e.g.

Packaging golang for secondary architectures, go-srpm-macros


at the moment golang packages are built only on primary architectures
(defined by %go_arches macro) due to golang compiler architecture
support. For secondary architectures gcc-go is available. In order to
provide an easy way for packagers to package golang projects for
secondary architectures as well, go-srpm-macros packages is introduced.
It provides basic macros that can be used within spec files. Currently
golang package ships /usr/lib/rpm/macros.d/macros.golang file, which
defines %gopath and %go_arches macros.

CI for kubernetes, docker, etcd and other atomic packages


at the moment kubernetes, docker, etcd and other atomic packages has no
CI testing in CentOS. The packages built for CentOS are taken from
Fedora's repositories. There is already an effort to create CI for
Fedora builds. Currently kubernetes has its own CI job which can be
taken as an template for other jobs for docker, etcd, etc. in Fedora.
The job among other things consists of a builder, i.e. script that can
be broken down into two parts: installation and testing. The
installation part takes care of installing, updating and downloading all
necessary builds.

Setting up fedmsg for centos


CentOS does not have any equivalent to fedmsg bus [1] at the moment.
What is it used for? Services (koji, pkgdb, ...) can send messages about
their state and result of tasks they run into the bus to notify other
service which can react accordingly. Thus creating a modular
infrastructure. E.g. koji send a message about finished build. Agent
read the message, trigger a jenkins job and run additional tests on the
build. Daily statistics about number of finished /failed builds can be
collected. Other application can have their own use cases. Example of
bus topology [4].

minimal requirements for subpackage named common


I have a package (kubernetes) which I would like to decompose into 2
subpackages A and B. Problem is A and B share some files and directories
so installing both of them on the same machine results in file
conflicts. Solution is to create the third package C, which provides all
those conflicting/shared files and directories (documentation, one
configuration file, etc.). So A and B both Requires C. So now both A and
B can be installed on the same machine (together with C).

My question is how should I name subpackage C?

stable pending builds, golang-googlecode-net f21


there has been a request to move golang-googlecode-net
package [1] into stable from 2014-10-17 14:18:36. Taskotron checks
passed. Now it is almost two weeks since that time. Moreover, builds for
this package can not be moved to buildroot-overrides.

Can someone take a look at it?

el6 builds failing


an hour ago I was able to build golang-github-mitchellh-mapstructure
package for el6:
<a href="" title=""></a>

Now it fails (some of my scratch builds):
<a href="" title=""></a>
<a href="" title=""></a>
<a href="" title=""></a>

Trying to scratch build another package (already build in el6 again):
<a href="" title=""></a>

With the same result = fail.