Postings by =?UTF-8?B?TWlybyBIcm9uxI1vaw==?=

License change: cura changed from AGPLv3+ to LGPLv3+

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

Finalizing Fedora's Switch to Python 3

Hello fellow Fedora contributors,

We've created a page on Fedora wiki [1] that's something like a Change

The document is called "Finalizing Fedora's Switch to Python 3" and it
describes steps needed in order to:

* Switch /usr/bin/python to Python 3 in cooperation with Python upstream.
* Switch `dnf install python-foo` to install python3-foo.
* Hopefully eventually get rid of Python 2.

This is all planned to line with the fact that Python 2 will be dead
upstream by 2020.

The first phase of the changes is planned for Fedora 30, which is pretty
far away today, but the pr

s390x build failures

I'm hitting weird s390x build failures.

Koji says (almost immediately):

URLError: <urlopen error [Errno 111] Connection refused>

See a build here:
<a href="" title=""></a>

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

I got similar failures for several hours now. It took a while before an
error, but now the error is almost immediate.

Am I doing anything wrong?

Heads up: Retiring DevAssistant


last bugfix release of DevAssisatnt [1] happened in September 2016, last
"major" release happened in April 2015. The project has not active
contributors, only me as a (very) low prio maintainer.

Users are experiencing problems with the assistants, as they are not
compatible with current Fedoras [2][3]. The test suite is broken [4] and
noone's going to fix that.

Given that, we are going to retire it from Fedora 26 and forward, as
this is clearly the "end of life" of DevAssistant.

Troubles with Python 3.6.1 in Fedora 26

There is and update of Python to 3.6.1 coming to Fedora 26 [1].
Due to a bug [2][3] tho following scenario might happen:

0. user has python3 3.6.0 and python3-foo-0.1-1
1. python3 3.6.1 is pushed to Fedora 26 stable
2. maintainer of python3-foo rebuilds the package to python3-foo-0.1-2
(this happens against python3 3.6.1) and pushes it to updates
3. user updates to python3-foo-0.1-2, but does not update python3
4. if the Python foo module meets certain conditions, it is broken

3D printing SIG

Hi Fedorains,

I was thinking about creating a 3D printing SIG in Fedora. Would anyone
be interested in that?


Orphaning perl-Lingua-EN-Numbers-Easy


perl-Lingua-EN-Numbers-Easy FTBFS in rawhide. [1]

While the fix seems trivial, I don not want to patch a (most probably)
dead upstream project that I don't need any more (I packaged it as a
dependency for something not needing it anymore).

* Latest upstream release is ~5 years old
* No other package requires this any more

If anybody want this package, feel free to take it. Otherwise I'm fine
with this being retired later.

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

Introducing Python 3.5 nightly builds for Fedora

Hi everybody, I'd like to introduce a new project of Slavek Kabrda and mine:

Copr repository with nightly builds of development version of Python 3.

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

How does it work?

Each night, at 00:01 CET/CEST, dgroc [1] is run and checks out if any of
the following upstream projects has some new commits in master/default

* cpython
* setuptools
* pip
* wheel

If so, it creates SRPM with code from that specific new commit and
builds it in the copr repository.

Request for help with slic3r crash

I really need help with fixing a crash in slic3r that bothers me for a
long time.

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

Steps to reproduce:

Run slic3r on F20 from this scratch build:

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

1) On Print setting tab, Advanced, Other, Threads enter value > 1 (such
as 2)
2) From File menu select Quick slice...
3) Select any (valid) STL* file
4) Observe the crash

* Get one here: <a href="" title=""></a>

Upstream cannot reprod

State of Python 3 as default in Fedora


I've just published a blogpost that summarizes what's going on with
Python 3 as default in Fedora.

You can find it here:

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

Feel free to post any comments on my blog or here on the mailing list(s).

AppData - how to properly handle them

I'm playing a bit with GNOME Software and I have questions about AppData

1) Should the package with foo.appdata.xml require some package that
owns /usr/share/appdata? (and do we have such package)

2) Should I run appdata-validate in %check?

3) Do we have guidelines for this?

Creating SRPM without rpmbuild

is tehre a way to create SRPM from sources + spec without rpmbuild?
Using tar or something?

I know the sources filenames and don't need to parse spec for it.

I need to prepare SRPM on machine where I have limited access and cannot
install rpmbuild. It's Debian based.

Thanks for any tips.

Building 3D printing packages for EPEL

recently, somebody mentioned the desire of having 3D printing tools in
RHEL. I am completly open to the idea of building my Fedora packages for
EPEL as well. However, I haven't done that yet.

Is there any automated tool, that would show me the stack of apckages
that need to be build for EPEL if I want package X?

I've approched the problem as LIFO, so simarrange is now building for
el6 brunch.

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

Thanks for any tips,

How long should last the "submitted for stable" phase in bodhi?

I've submitted some updates for stable >10 days ago and they are still
in testing.

For example
<a href=",perl-Role-Tiny-1.003002-1.fc20,perl-Moo-1.003001-2.fc20" title=",perl-Role-Tiny-1.003002-1.fc20,perl-Moo-1.003001-2.fc20"></a>

Is there something broken in the process? Is this done by human or an app?

Thanks for info.

Review swap: ultimaker2-marlin-firmware and gnome-colors-icon-theme

I'm offering to do one non-complex review for reviewing one of those

* Feel free to take both, I'll review two of yours :)


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

Ultimaker2 firmware for the 3D printer. (Dependency of new cura update.)


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

The GNOME-Colors is a project that aims to make the GNOME desktop as
elegant, consistent and colorful as possible.

The current goal is to allow full color customization of themes, icons,
GDM logins and splash screens.

Please help me test one use case in ReptierHost


I have an issue with one of my packages in F19.

Package: RepetierHost

Affected versions: 0.84, 0.90C-1, 0.90C-2

Test case:

1. Install and run RepetierHost
2. Load any STL file (in toolbar, use Load button) (e.g.
<a href="" title=""></a>)

I would like to become the owner of gnome-colors-icon-theme

according to [1] I should "Announce on devel which packages you would
like to become the owner of."

So that's it. BTW Was this really necessary?

The Review request is at [2].

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

ino - Desperately looking for a new maintainer (with an actual Arduino)

I've somehow managed to build and maintain a bit package ino.

The reason is simple - I need it as a BuildRequires for some other
package. However I don't have an Arduino and is very hard for me to test
the package in action and respond / solve the bugs related to it.

I don't want to orphan it (as it would break my stack), but if anyone
here has an Arduino and uses it - could you PLEASE take this package?

Thanks a lot,
Miro HronĨok

Rawhide Koji Errors (Requires: /sbin/ldconfig)

I believe there's something wrong in Koji Rawhide buildroot, as it
appears nothings provides /sbin/ldconfig.

DEBUG Error: Package: foo
DEBUG Requires: /sbin/ldconfig

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

Is this something known or intended?

Fedora Hosted Usability and Developer Experience

Hi all,
few days ago I was explaining to someone*, what the Developer Assistant
[0] is.

When I said something like: "...and you project is exported directly to
GitHub [1] if you want", the person I was talking to interrupted me and
asked an interesting question:

Why our own tools prefer a proprietary service, such as GitHub, over our
own infrastructure (Fedora

The answer is very easy: Because developers prefer GitHub over Fedora
Hosted and we want to target on the majority.

That leads us to other question: Why do developers prefer GitHub over
Fedora Hosted?

Of course no

3D printing packages group

as part of my F19 feature

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

I would like to create a group in comps.xml.

Patch for rawhide is attached, I want to add it primary to F19, but also
for older versions (18, 17). Is anyone against it?

Sorry for doing this after string freeze, could I please get an
exception? I haven't done that before and only today I've realized it
supposed to be before the freeze.

I would like to get this in so user can see this feature more clearly.

It means just adding two strings.

Thanks a lot.