DevHeads.net

Postings by Fabio Valentini

broken package needs attention: libgda

Hi,

The "libgda" package is quite broken in fedora, which is impacting
dependent programs.

- The last successful build of libgda was for the fedora 24 (!) mass
rebuild. No more recent builds succeeded, and the packages was reported as
FTBFS.
- Not even the latest version is packaged (5.2.2 instead of 5.2.4).

This is leading to problems in all current releases of fedora.

Intent to update granite to 5.0 (includes an soname bump)

Hi everybody,

The elementary project has recently released version 5.0 of their granite
toolkit extensions library, which includes an soname bump, and some
deprecated APIs were removed.

I intend to update the granite package in rawhide next week, and I am
fairly confident that this won't cause (m)any issues because I already
basically run CI builds of all currently packaged elementary projects on
fedora (in COPR), and I don't see any compatibility issues with the latest
granite snapshots.

Affected packages
According to a repoquery, the packages affected by this so

Valid use case for modularity or not?

Hi all,

I think I finally found a scenario where building some of my (and others')
packages as modules would be beneficial.

The situation is:

- The syncthing package has a lot of golang dependencies.
- Some of them are too old in fedora, even in fedora rawhide, and some of
them have not been touched in years.
- However, some other packages may depend on those older versions, or the
packagers don't have time to check for compatibility.

The idea for a solution I came up with:

- Build syncthing as a module.
- Add "syncthing" branches to all incompatible dependencies (I guess I have
to reques

rubygem-liquid update to 4.0.0

Hi all,

I am planning to update the rubygem-liquid package (which was orphaned, and
then taken by me) to the latest upstream release, 4.0.0.

This will break the current (really outdated) rubygem-jekyll package, which
depends on liquid < 4. I have reached out to rubygem-jekyll-owner (which
should be besser82) to help with bringing jekyll up-to-date (or to take
over maintaining the package, because it looks kind of abandoned) two weeks
ago (April 23), but I have not heard back since.

What is the procedure to follow here? I don't want to just push the update
and break stuff.

Fabio

fedora infrastructure problems?

Hi everybody,

Is anybody else experiencing problems with the fedora infrastructure right
now?

- I was barely able to build a package with koji due to src.fp.org errors
- fedmsg messages seem to be delayed up to 20 minutes
- I can't comment on issues on pagure.io right now
- fedpkg request-repo is hitting a timeout, but requests seem to get through
- git/fedpkg push hits "remote: sh:
/usr/lib/python2.7/site-packages/pagure/hooks/files/fedmsg_hook.py: No such
file or directory" error, and I don't get commit notifications for my repos
because of that

Fabio

What to do when test gating in bodhi fails (no test results found)?

Hi,

I've got two updates sitting in F26 and F27 updates-testing:

<a href="https://bodhi.fedoraproject.org/updates/FEDORA-2018-c455a245b0" title="https://bodhi.fedoraproject.org/updates/FEDORA-2018-c455a245b0">https://bodhi.fedoraproject.org/updates/FEDORA-2018-c455a245b0</a>
<a href="https://bodhi.fedoraproject.org/updates/FEDORA-2018-4d0e13ff51" title="https://bodhi.fedoraproject.org/updates/FEDORA-2018-4d0e13ff51">https://bodhi.fedoraproject.org/updates/FEDORA-2018-4d0e13ff51</a>

I can't push either of them to batched or stable (despite them being in
-testing for over 10 days now), because "no test results found".

Which is really annoying and the error message is ...

Spring cleaning my golang packages (orphaning now unused stuff)

Hi everybody,

I'm going to orphan some of my golang packages that were initially pulled
in by syncthing as dependencies, but have been dropped as dependencies
again (... don't ask. golang people produce dependencies like rabbits make
bunnies.).

Most of them are fairly low maintenance packages, with only a few commits
per year (if even that), and decent coverage with unit tests.

Trying out More Go Packaging: Bugs and Questions

Hi everybody,

I've been following the (long overdue) improvements concerning go packaging
in fedora, and since I saw that packages are starting to make use of the
new mechanisms, I wanted to finally check it out and started "converting"
one of my own (one of ~50) golang packages
(golang-github-AudriusButkevicius-cli).

unannounced soname bump: gnome-desktop3 / libgnome-desktop-3

FYI, the .so version of libgnome-desktop-3 was bumped from 12 to 17
with the build of gnome-desktop3-3.27.90-1.fc28 without previous
announcement.

Packages that will have to be rebuilt - if it hasn't happened already
(I didn't check individual changelogs, so no guarantee for correctness
or completeness of this list):

cheese-2:3.26.0-3.fc28.src
control-center-1:3.26.2-4.fc28.src
deepin-mutter-0:3.20.26-1.fc28.src
deepin-wm-0:1.9.21-2.fc28.src
eog-0:3.26.2-2.fc28.src
epiphany-1:3.27.1-3.fc28.src
evince-0:3.26.0-3.fc28.src
evolution-0:3.27.4-1.fc28.src
gnome-clocks-0:3.26.1-2.fc28.src
gnome-con

golang-github-chmduquesne-rollinghash license change (MIT -> MIT and BSD) with 3.0.0

The license changes from "MIT" to "MIT and BSD" as of the newly released
version 3.0.0, which has been built for rawhide and will make it to f27 and
f26 if no problems with dependent packages (syncthing) arise.

This has no real effect for fedora, since the changed license tag only
arises from a newly introduced BSD-licensed golang subpackage (the
rabinkarp64 algorithm), which is used nowhere yet - and all other parts of
the package remain MIT-licensed. So I'm just sending this notice as
required (<a href="https://fedoraproject.org/wiki/Licensing:Main#License_Changes" title="https://fedoraproject.org/wiki/Licensing:Main#License_Changes">https://fedoraproject.org/wiki/Licensing:Main#License_Changes</a>).

Fabio

How to handle broken dependencies in F27?

Hi,

I've got two packages (gala, wingpanel) that have broken dependencies in
F27 because of unfortunate timing:

1. GNOME 3.24 prerelease broke builds just in time for the mass rebuild,
2. upstream took a few days to come up with fixed support for GNOME 3.24,
3. I built fixed packages and they have been in rawhide and
f27-updates-testing for some time now,
4.

Any plans for completing the go 1.9 rebase (to stable 1.9)?

According to the Change for F27 [0], all golang packages have been rebuilt
against golang 1.9beta2. In the meantime, go 1.9 stable has been released
upstream (Aug. 24, 2017) [1].

I suspect that some of the issues I am having with go / my golang packages
in fedora would be fixed by the update to the final release, since upstream
test suites targeting go 1.9 stable in travis aren't hitting any of those
issues.

What's the plan for rebasing golang to the stable release?

pagure-over-dist-git: traceback in receive-hook when pushing to new repo

I've just pushed an import commit to my first repository that was created
with fedrepo_req on pagure, and I got the following traceback from the
remote when it obviously failed to run a post-receive hook:

remote: Traceback (most recent call last):
remote: File "./hooks/post-receive.default", line 19, in <module>
remote: import pagure # noqa: E402
remote: File "/usr/lib/python2.7/site-packages/pagure/__init__.py", line
60, in <module>
remote: APP.config.from_envvar('PAGURE_CONFIG')
remote: File "/usr/lib/python2.7/site-packages/flask/config.py", line
108, in from_envvar
remote:

fedpkg new-sources broken?

Right now, I can't build updates or new packages, because "fedpkg
new-sources" is getting stuck (for more than 15 minutes) without error
message (other than the bodhi deprecation warning) and it doesn't do
anything until I kill it ...

I can't pin down the exact date it stopped working (since I don't use it
every day), but I first noticed it yesterday after installing updates from
f26-updates-testing (although those updates probably didn't cause the bug,
because downgrading to f26 stable packages didn't help).

Am I the only one affected by this bug or has nobody else been building
packages?

Review Swaps: Simple golang packages (for syncthing)

Hi everybody,

I need somebody to take on the Review Requests of the only 3 golang
dependencies that are still blocking a syncthing package:

golang-github-cznic-zappy:
<a href="https://bugzilla.redhat.com/show_bug.cgi?id=1431743" title="https://bugzilla.redhat.com/show_bug.cgi?id=1431743">https://bugzilla.redhat.com/show_bug.cgi?id=1431743</a>
golang-github-cznic-lldb:
<a href="https://bugzilla.redhat.com/show_bug.cgi?id=1431745" title="https://bugzilla.redhat.com/show_bug.cgi?id=1431745">https://bugzilla.redhat.com/show_bug.cgi?id=1431745</a>
golang-github-cznic-ql: <a href="https://bugzilla.redhat.com/show_bug.cgi?id=1431748" title="https://bugzilla.redhat.com/show_bug.cgi?id=1431748">https://bugzilla.redhat.com/show_bug.cgi?id=1431748</a>

They need to be reviewed in that order (because dependencies).

Review Swaps: (mostly) very simple golang packages

Hi everybody,

I've been putting together package Review Requests for all the golang
package dependencies of syncthing (an open source file synchronization
service). Some of them have already been reviewed (thank you, Jan! I feel
much more confident about my golang packaging now), but there are still 16
packages left.

The packages are (mostly) very simple (standard golang specs generated by
gofed), and I've added explanatory comments where they differ from the
automatically generated gofed output for the repository in question.

becoming a co-maintainer of plank

Hello Wesley,

I am working on getting all the elementary apps and pantheon desktop
components into fedora and wondered if you could approve my ACL Requests
for becoming a co-maintaner of plank (since that package is obviously also
part of a Pantheon DE and ties in with the other packages I am maintaining
already, see <a href="https://admin.fedoraproject.org/pkgdb/packager/decathorpe/" title="https://admin.fedoraproject.org/pkgdb/packager/decathorpe/">https://admin.fedoraproject.org/pkgdb/packager/decathorpe/</a>).

Regards,
Fabio

becoming a co-maintainer of elementary-icon-theme

Hello Johannes,

I am working on getting all the elementary apps and pantheon desktop
components into fedora and wondered if you could approve my ACL Requests
for becoming a co-maintaner of elementary-icon-theme (since that package
obviously ties in with the other packages I am now maintaining, see
<a href="https://admin.fedoraproject.org/pkgdb/packager/decathorpe/" title="https://admin.fedoraproject.org/pkgdb/packager/decathorpe/">https://admin.fedoraproject.org/pkgdb/packager/decathorpe/</a>).

Regards,
Fabio

f25+: vala 0.34.x+ bug causing .vapi file generation for ALL CURRENT PACKAGE BUILDS to be possibly faulty

I has come to my attention that - since the update to vala from the
0.34.x series has made it into the fedora 25(+) repositories - every
package that generates .vapi files during build might have done so
incorrectly, because of the following bug, which is present in vala
releases up to 0.34.3 (also including 0.35.1), but has been fixed in
git:

Functions that have a return type of a fixed-size array were not
treated correctly - they instead are wrongly indicated to return the
base type of the respective array (the array qualifier "[]" is
missing).

I reported this bug at
<a href="https://bugzilla.redha" title="https://bugzilla.redha">https://bugzilla.redha</a>

Self Introduction: Fabio Valentini (decathorpe)

Here goes my introduction as a new (or aspiring) package maintainer for fedora.

I have been using fedora as my daily driver OS for some years now (I
think starting with f18 or f19).