DevHeads.net

Postings by =?ISO-8859-2?Q?Miroslav_Such=FD?=

Multi-arch support in Mock

Hi,
I just pushed into updates-testing new release of Mock (1.4.11). It has nice new feature:

$ sudo dnf install qemu-user-static # weak dependency
$ mock -r fedora-28-ppc64le --forcearch ppc64le shell

This will give you Fedora shell on different architecture. Emulated by QEMU. And of course you can build packages for
the different architectures this way.
You can do this for any architecture: aarch64, armhfp, ppc64, ppc64le, s390x.

People are asking me how much slower it is.

Change in Copr retention policy?

Hi,
I would like to open discussion about Copr retention policy change.

Right now we have:

This means that we still have repos for fedora-18-* and epel-5-*.

Is this reasonable? Or are we just wasting storage?

heads up: mock's fedora-29-x configs

I just released new `mock-core-configs` and there is a new feature.

It contains:

$ ls -l /etc/mock
...
lrwxrwxrwx. 1 root mock 26 May 2 09:13 fedora-29-aarch64.cfg -> fedora-rawhide-aarch64.cfg
lrwxrwxrwx. 1 root mock 25 May 2 09:13 fedora-29-armhfp.cfg -> fedora-rawhide-armhfp.cfg
lrwxrwxrwx. 1 root mock 23 May 2 09:13 fedora-29-i386.cfg -> fedora-rawhide-i386.cfg
lrwxrwxrwx. 1 root mock 24 May 2 09:13 fedora-29-ppc64.cfg -> fedora-rawhide-ppc64.cfg
lrwxrwxrwx. 1 root mock 26 May 2 09:13 fedora-29-ppc64le.cfg -> fedora-rawhide-ppc64le.cfg
lrwxrwxrwx.

Orphaning some Spacewalk packages

I am going to orphan some Spacewalk packages:
perl-Satcon
spacewalk-proxy-html
spacewalk-proxy-docs
spacewalk-config

They does not have sense to be in Fedora without additional Spacewalk packages. They live in Copr repos. But if anyone
want it, feel free to grab it.

Miroslav

Clean up your spec files

Hi,
I am sometimes reviewing spec files and I very often see common mistakes. I mean in packages which are already in
Fedora. For a long time and they have some dust from past times.

I am not going to file bug reports as those are not bugs. I will just point it here and leave it up to you to check your
spec files:

* Group: System Environment/Base

Please remove it. Group was intended for something (sort apps in menus), but it never actually worked. It was required
for EL5 packages. Since EL6 it can be omitted.

Orphaning some Spacewalk packages

I orphaned
rhnmd
This is Spacewalk package which is not developed any more.

And I orphaned
perl-Socket-MsgHdr
perl-Crypt-GeneratePassword
as I these are not used in Spacewalk as well.

Miroslav

Remove old GPG keys?

I just stumbled upon
<a href="https://unix.stackexchange.com/questions/400634/does-anyone-bother-to-remove-rpmkeys" title="https://unix.stackexchange.com/questions/400634/does-anyone-bother-to-remove-rpmkeys">https://unix.stackexchange.com/questions/400634/does-anyone-bother-to-re...</a>
with the nice link to:
<a href="https://blog.laimbock.com/2014/05/02/how-to-remove-an-imported-gpg-key-from-rpm/" title="https://blog.laimbock.com/2014/05/02/how-to-remove-an-imported-gpg-key-from-rpm/">https://blog.laimbock.com/2014/05/02/how-to-remove-an-imported-gpg-key-f...</a>
And I wonder: is it a good idea to keep old gpg keys in RPM db? Or should we automate the removal of old keys?

Mirek

Pagure token only 2 months?!

Hi,
I recently added new package to Fedora and went through the new process which uses:
fedrepo-req-branch
See
<a href="https://pagure.io/fedrepo_req/blob/master/f/README.md" title="https://pagure.io/fedrepo_req/blob/master/f/README.md">https://pagure.io/fedrepo_req/blob/master/f/README.md</a>
I have been surprised that you first need to configure this tool.

CI projects in Copr

Hi,
I am gathering informations about various use of CI with Copr. Do you use Copr for building packages for nightlies? For
building packages before pull request is merged? Do you have your set up described somewhere? What is the name of your
project?

Please let me know. Either here or via private reply.
It will help me to understand your use of Copr and to make Copr better.

Thanks in advance.

Miroslav Suchy

Orphaning several rubygem-* packages

Hi,
I just orphaned several packages:
rubygem-ttfunk
rubygem-xmlhash
rubygem-wirb
rubygem-unicode-display_width
rubygem-single_test
rubygem-ruby-rc4
rubygem-robotex
rubygem-rkerberos
rubygem-paint
rubygem-mobileesp_converted
rubygem-hoptoad_notifier
rubygem-foreman_api
rubygem-fast_xs
rubygem-Ascii85

I do not use them and I want to focus more on my other packages.
Feel free to grab them.

`best=1` in new Mock

Hi,
I just released new version of Mock. And I want to quote one important
change from the release notes so everyone is aware of it:

<a href="https://github.com/rpm-software-management/mock/wiki/Release-Notes-1.3.3" title="https://github.com/rpm-software-management/mock/wiki/Release-Notes-1.3.3">https://github.com/rpm-software-management/mock/wiki/Release-Notes-1.3.3</a>

All chroot (but rawhide) configs now contains best=1.
This way DNF will always try to install latest package. If its
dependence cannot be satisfied DNF will report an error.

F25 Server cloud image

I just wanted to download F25 Cloud image for OpenStack and was surprised that there is none. There is just Atomic image.
But Atomic use rpm-ostree for installing packages. There is no DNF. However I cannot find any module for rpm-ostree for
Ansible.

Am I missing something? What should I install nowdays when I am using Ansible for managing configuration?

Mock and Copr are failing for epel-*

Hi everybody.
Some of you noticed that Copr (and mock-1.2.19) is failing to initialize epel-* buildroots. It errors with incorrect gpg
signature for some package.
It is my fault.
Epel configs use Centos and Epel gpg keys. In the 1.2.19 release I used just Centos keys - even for the Epel repository.
Which results in the error.

I am preparing new release (1.2.20), which should land in bodhi in few minutes.

I am sorry for this error I made.

Improvements of Fedora Sponsorship process

I had the talk [1] about Fedora Sponsorship process at Flock. And we had
very interesting follow-up discussion.

We come up with several improvements, which should be easy to implement
and may improve the process a lot. I am posting it here so more people
can see that and join the discussion.

a) Sponsoree (who apply for package maintainer status) is required to
create Copr project and maintain the package there until he get the
package into Fedora. This should show his endurance to sponsors.

Unable to package lots of rubygems in Copr due missing license

Hi,
I started rebuilds of whole rubygems.org as RPM packages in Copr.
See:
<a href="https://copr.fedorainfracloud.org/coprs/g/rubygems/rubygems/" title="https://copr.fedorainfracloud.org/coprs/g/rubygems/rubygems/">https://copr.fedorainfracloud.org/coprs/g/rubygems/rubygems/</a>

However lots of gems cannot be imported due licensing problems.
Such gems fail with this dist-git log:
<a href="http://copr-dist-git.fedorainfracloud.org/per-task-logs/320374-f24.log" title="http://copr-dist-git.fedorainfracloud.org/per-task-logs/320374-f24.log">http://copr-dist-git.fedorainfracloud.org/per-task-logs/320374-f24.log</a>

And quoting from this link:

15 thousands python3-* packages for Fedora

Hi,
I just finished packaging of 15 634 python3-* packages for Fedora.
<a href="https://copr.fedorainfracloud.org/coprs/g/copr/PyPI3/" title="https://copr.fedorainfracloud.org/coprs/g/copr/PyPI3/">https://copr.fedorainfracloud.org/coprs/g/copr/PyPI3/</a>
You can click on Builds and Monitoring tab. But be aware that those
pages are HUGE (40MB) and they are loading and rendering several
minutes. Tab "Packages" is timeouting and this will be fixed in next
release.

I am now building python2-* packages too:
<a href="https://copr.fedorainfracloud.org/coprs/g/copr/PyPI2/" title="https://copr.fedorainfracloud.org/coprs/g/copr/PyPI2/">https://copr.fedorainfracloud.org/coprs/g/copr/PyPI2/</a>

This is only for rawhide and for statistic purposes, but there will be
more.

Some Copr projects shared the same GPG

Hi,
due to a bug in Copr code some projects shared a GPG key with some other Copr project.

We informed the owners of those projects and we resigned all packages in those projects
by new GPG key.

These projects were affected by one bug [1]:
@pdc/pdc-test
nb/keepassx

And these by another bug [2]:
@freeipa/freeipa-4-3-centos-7
agargiulo/git
alexrio/mutt-sidebar
alonid/jdk-1.8.0
azrdev/tinc-prerelease
barracks510/surface-pro-3-kernel
bradlaue/keepass
cialu/librosa
davidva/clementine-git
domcleal/foreman-rawhide
hno/electrum
jayaura/kernel-ck
jerboaa/openjdk-9-ub-sanitizer
johnp117/rxvt-unicode-

Planned Outage: Copr upgrade - 2016-05-05 08:00 UTC

There will be an outage starting at 2016-05-05 08:00 UTC, which will
last approximately 6 hours.

To convert UTC to your local time, take a look at
<a href="http://fedoraproject.org/wiki/Infrastructure/UTCHowto" title="http://fedoraproject.org/wiki/Infrastructure/UTCHowto">http://fedoraproject.org/wiki/Infrastructure/UTCHowto</a> or run:

date -d '2016-05-05 08:00 UTC'

Reason for outage: Upgrade all copr packages to newer version and reprovision copr-dist-git machine from RHEL 7 to
Fedora 23.

Affected Services:
copr.fedoraproject.org
copr-be.cloud.fedoraproject.org
copr-keygen.cloud.fedoraproject.org
copr-dist-git.cloud.fedoraproject.org

Services not listed are not affected by this outage.

Contact Information: ​​

Copr ppc builds are stopped temporary

We have temporary problems with ppc builders so I stopped ppc builds for
now.
This does not affect i386 and x86_64 queue.
I anticipate that tomorrow I may start it again.

Mirek Suchy

Failed builds in Copr

I am very sorry.

Today Lubos K. accidentally submitted 10k packages to Copr. I wanted to run one simple SQL query to set all those builds
as failed. Unfortunately I made big mistake - I forgot to add one column to 'where' condition. As result of this error
*all* builds were marked as failed. All builds of all projects.
Mea culpa, mea maxima.
Fortunately we have backup, so we restored the state of the builds from this backup. This backup is few hours old.

SLA of Copr and changes in future

We are discussing in Fedora Infrastructure about level of SLA of some
services. And mainly because of Copr. There are some other services e.g.
Jenkins, Taiga. However Copr is probably most popular. Copr service was
from begging meant as somehow beta version and did not pass all the
requirements Fedora Infrastructure team has for Fedora services.

So rather later than never - I would like to emphasize:

Copr is experimental service provided as a courtesy for the
community.

F24 chroots in Copr are available

Hi,
I just added
fedora-24-x86_64
fedora-24-i386
chroots to Copr. I automatically enabled those chroots for every project, which has fedora-rawhide-* enabled. And I
copied all build artifact from rawhide to fedora-24-* repository.

Ppc64le repositories are not available yet. I will enable it and send another email once it will be available.

P.S. we already discovered issue that old builds (~10+ months old) were not copied. If you need them, please submit it
manually.

copr-fe.cloud.fedoraproject.org is no more

Several of you reported expired certificate of
copr-fe.cloud.fedoraproject.org

This url was only used at very earlier stage of this project and now is
deprecated. It still exist albeit with expired certificate, but it will
be removed soon.
Please replace your bookmarks with either
copr.fedoraproject.org
or
copr.fedorainfracloud.org

The second one is preferred for now.

Miroslav Suchy

Planned Outage: Copr upgrade - 2016-02-11 08:00 UTC

There will be an outage starting at 2016-02-11 08:00 UTC, which will
last approximately 1 hour.

To convert UTC to your local time, take a look at
<a href="http://fedoraproject.org/wiki/Infrastructure/UTCHowto" title="http://fedoraproject.org/wiki/Infrastructure/UTCHowto">http://fedoraproject.org/wiki/Infrastructure/UTCHowto</a> or run:

date -d '2016-02-11 08:00 UTC'

Reason for outage: We need to reprovision Copr servers.

Affected Services: copr.fedoraproject.org
copr-be.cloud.fedoraproject.org copr-keygen.cloud.fedoraproject.org
copr-dist-git.cloud.fedoraproject.org

Services not listed are not affected by this outage.

Contact Information: ​​​ ... at redhat dot com

Ticket Link:
<a href="https://fedorahosted.org/fedora-infrastruc" title="https://fedorahosted.org/fedora-infrastruc">https://fedorahosted.org/fedora-infrastruc</a>

Copr GPG keys

Hi,
I just released new version of distribution-gpg-keys package:
<a href="https://bodhi.fedoraproject.org/updates/FEDORA-2016-1a7ed2ffe8" title="https://bodhi.fedoraproject.org/updates/FEDORA-2016-1a7ed2ffe8">https://bodhi.fedoraproject.org/updates/FEDORA-2016-1a7ed2ffe8</a>
It now includes GPG keys of all Copr projects. Thanks to clime for
writing the script which retrieve all those keys.

I plan to upgrade those data regularly. Although I'm still not sure what
will be the definition of 'regularly' yet. Probably every month.

Mirek

Planned Outage: Copr upgrade - 2016-01-19 20:00 UTC

Planned Outage: Copr upgrade - 2016-01-19 20:00 UTC

There will be an outage starting at 2016-01-19 20:00 UTC, which will last approximately 1 hours.

During the outage backend will stop processing new task and they will be queued in frontend and processed just after the
outage.

To convert UTC to your local time, take a look at <a href="http://fedoraproject.org/wiki/Infrastructure/UTCHowto" title="http://fedoraproject.org/wiki/Infrastructure/UTCHowto">http://fedoraproject.org/wiki/Infrastructure/UTCHowto</a> or run:

date -d '2016-01-19 20:00 UTC'

Reason for outage: Upgrading keygen machine to Fedora 23.

Affected Services: copr.fedoraproject.org copr-be.cloud.fedoraproject.org copr-keygen.cloud.fedoraproject.org

Serv

Planned Outage: Copr upgrade - 2016-01-04 08:00 UTC

Planned Outage: Copr upgrade - 2016-01-04 08:00 UTC

There will be an outage starting at 2016-01-04 08:00 UTC, which will last approximately 4 hours.

To convert UTC to your local time, take a look at <a href="http://fedoraproject.org/wiki/Infrastructure/UTCHowto" title="http://fedoraproject.org/wiki/Infrastructure/UTCHowto">http://fedoraproject.org/wiki/Infrastructure/UTCHowto</a> or run:

date -d 'YYYY-MM-DD HH:MM UTC'

Reason for outage: Upgrade of Copr backend and Copr frontend to Fedora 23.

Affected Services: copr.fedoraproject.org copr-be.cloud.fedoraproject.org

Services not listed are not affected by this outage.

Contact Information: <a href="mailto: ... at redhat dot com"> ... at redhat dot com</a>

Ticket Link: <a href="https://fedorahosted.org/fedora-infrastructure" title="https://fedorahosted.org/fedora-infrastructure">https://fedorahosted.org/fedora-infrastructure</a>

Planned Outage: Copr upgrade - 2015-11-30 08:00 UTC

Planned Outage: Copr upgrade - 2015-11-30 08:00 UTC

There will be an outage starting at 2015-11-30 08:00 UTC, which will last approximately 4 hours.

To convert UTC to your local time, take a look at <a href="http://fedoraproject.org/wiki/Infrastructure/UTCHowto" title="http://fedoraproject.org/wiki/Infrastructure/UTCHowto">http://fedoraproject.org/wiki/Infrastructure/UTCHowto</a> or run:

date -d 'YYYY-MM-DD HH:MM UTC'

Reason for outage:
Upgrade of Copr backend and Copr frontend to Fedora 23.

Affected Services:
copr.fedoraproject.org
copr-be.cloud.fedoraproject.org

Services not listed are not affected by this outage.

Contact Information: ​ ... at redhat dot com

Ticket Link:
<a href="https://fedorahosted.org/fedora-infrastructur" title="https://fedorahosted.org/fedora-infrastructur">https://fedorahosted.org/fedora-infrastructur</a>

COPR infrastructure issues caused build failures

Hi,

Throughout the day of November 24th, 2015 there have been multiple build
failures in COPR because of problems with the COPR infrastructure.
If your build failed with only a mockchain.log.gz file which contains
the following line:
"Failed to obtain srpm from dist-git", or something alike that, that was
caused by this
infrastructure issue.

We have just found and fixed the root cause of this problem, so any
builds from now on should be successful.
If you have any builds that failed and only produces a mockchain.log.gz,
please resubmit your build and it should go through correctly.

If you h

To distro-sync or not distro-sync?

I am trying to upgrade to F23 (I know still not finished but...)

In past I always done 'distro-sync'. Albeit with yum.

Now I tried:
dnf system-upgrade download --releasever=23 --distro-sync
dnf system-upgrade download --releasever=23 --distro-sync --best
dnf system-upgrade download --releasever=23 --distro-sync --best --allowerasing

And all of them fail. See below for full log.

On the other hand:
dnf system-upgrade download --releasever=23
succeed.

Actually most of the problem are caused by retired or obsoleted packages.