DevHeads.net

Postings by Alexander Ploumistos

Taskotron test failures (dist.rpmlint)

Hello,

I've just submitted an update to cmpfit[0] for f28. The automated tests
show errors and warnings only on x86_64 and armv7hl[1] and the errors have
to do with the omission of ldconfig scriptlets. Aren't we supposed to get
rid of these for f28+?

The warnings are:
cmpfit-devel.armv7hl: W: no-documentation
cmpfit-devel.x86_64: W: only-non-binary-in-usr-lib
cmpfit-devel.x86_64: W: no-documentation
Is there any merit to them?

Upcoming gdouros-*-fonts license change and subsequent complications

Hello all,

I doubt most of you know or care about George Douros' family of fonts,
as almost all of them are quite niche.

Build fails on s390x - complains about missing /usr/lib64/lib*.so* file

Hello,

I submitted a package for review[0] about an hour ago and when I ran a
scratch build in koji[1] there was a failure with this message in
build.log:

error: File not found:
/builddir/build/BUILDROOT/molsketch-0.5.1-2.fc28.s390x/usr/lib64/lib*.so*

I had built previous versions of the same package successfully in the
past, with the last successful build either in late December or early
January.

package blocked for tag f27-updates-candidate

Hi,

I've been trying to build a new version of a package (scidavis) and it
fails on f27 every time with the message "FAILED: BuildError: package
scidavis is blocked for tag f27-updates-candidate".
<a href="https://koji.fedoraproject.org/koji/taskinfo?taskID=22657927" title="https://koji.fedoraproject.org/koji/taskinfo?taskID=22657927">https://koji.fedoraproject.org/koji/taskinfo?taskID=22657927</a>

Is this because of the Final freeze, or is there some other problem?

Updates for Firefox 57 beta

Hello,

Now that FESCo has ruled that "firefox 57beta is removed from f25/f26
updates-testing but stays in f27/rawhide", could we at least keep
getting new builds in koji for f25/f26? Judging by the feedback in
bodhi, the various threads here, rhbz and FESCo tickets, there is a
number of users who don't mind sticking with Firefox 57. Going back to
v56 would entail undoing a number of changes and dealing with possible
breakages, only to repeat the whole process in about a month.

Is there a seperate SOP for unblocking a package in koji?

Hello,

About a couple of weeks ago, I went through the new
adoption/unretirement procedure for scidavis and I also used
fedrepo-req-branch to request that f25, f26 and f27 branches be
created as well.

Combining repo/branch requests with POC changes for orphaned/retired packages

Hello all,

Until last week, I hadn't gone through the new process for requesting
repos and branches or unretiring and unorphaning packages and though I
had read the "WhatHappenedToPkgdb" page, none of the intricacies had
stuck.
After a previously orphaned and retired package got approved, I filed
a request for the repo, separate requests for each branch and after
another day of not being able to push into the remote, I realized that
I had to file a POC change request as well (my mistake, obviously).
A few days ago there was a thread here, where the reasoning behind not
automating repo creatio

Build failures on armv7hl with "No such file or directory"

Hello,

I have a package under review[0], that I realized had python scripting
support disabled, so I enabled it.

Is /usr/share/mimelnk used for anything any more?

While cleaning up an old spec file, I came across a desktop file,
containing MimeType information, which is to be placed under
/usr/share/mimelnk.

Review swaps

Hello,

I have a couple of packages waiting for review:

scidavis - Application for Scientific Data Analysis and Visualization
<a href="https://bugzilla.redhat.com/show_bug.cgi?id=1490054" title="https://bugzilla.redhat.com/show_bug.cgi?id=1490054">https://bugzilla.redhat.com/show_bug.cgi?id=1490054</a>

which depends on

liborigin3 - A library for reading OriginLab OPJ project files
<a href="https://bugzilla.redhat.com/show_bug.cgi?id=1490053" title="https://bugzilla.redhat.com/show_bug.cgi?id=1490053">https://bugzilla.redhat.com/show_bug.cgi?id=1490053</a>

Both of them have been in a copr for a while:
<a href="https://copr.fedorainfracloud.org/coprs/alexpl/scidavis/" title="https://copr.fedorainfracloud.org/coprs/alexpl/scidavis/">https://copr.fedorainfracloud.org/coprs/alexpl/scidavis/</a>

I'd appreciate it if any of the people I've done reviews for could
return the favor, but I wouldn't mind reviewing a couple more
packages.

Thanks!

Better to bundle a library or package different version than upstream?

Dear all,

About ten days ago I asked a question on this list, but I guess on one
hand it was too specific, while on the other it coincided with people
travelling to Flock or being on vacation. As I really want to get the
package in question back in Fedora, I will ask again and I will try to
be more abstract and concise. For anyone interested, there is a link
to the original post at the end of this message.

Package foo, which depends on library bar for importing a certain type
of files, was retired a couple of releases ago.

SciDAVis and liborigin3 vs liborigin & liborigin2 - bundle or obsolete?

Hello,

Since its retirement from Fedora, SciDAVis[0] has undergone
significant development and I think it is ready to be re-included in
our package collection. After a few months of private builds that I
distributed among co-workers and friends, I set up a copr[1] and I've
been keeping up with the upstream project.

SciDAVis comes with a bundled copy of liborigin[2], which the upstream
developers helped me unbundle. Its version has been bumped to 3.0.0
internally, although there hasn't been a 3.0.0 release yet.

f27 builds in COPR fail without logs

Hello,

For the past hour or so, I've been trying to rebuild my copr packages
for f27 and rawhide. While there were some hiccups with rawhide, e.g.
not finding mirrors to download packages, after resubmitting them a
couple of times, all builds were successful.

Default location for addons AppStream metadata has changed

Hello all,

Sometime ago, the default location of AppStream metadata for addons
(*.metainfo.xml files) changed from %{_datadir}/appdata/ to
%{_datadir}/metainfo/[0].

As far as I can tell that change went mostly unnoticed, given that
most of our packages still install addon metadata in
%{_datadir}/appdata/.

Unicode 10 support across releases

Hello all,

I am going to update the gdouros-symbola font to the newest version,
which contains Unicode 10 glyphs. I have kind of lost track of things,
so I would like to ask if there is a fedora release that shouldn't or
wouldn't make sense to get the update?

Thanks,
Alex

hotness tried to map X to an upstream project, but failed: "Could not determine backend for http://url/project/X"

Hello,

I've just received about a dozen of messages like the one mentioned in
the subject, accompanied with:

pkgdb_updater updated: upstream_url of X
<a href="https://admin.fedoraproject.org/pkgdb/package/X/" title="https://admin.fedoraproject.org/pkgdb/package/X/">https://admin.fedoraproject.org/pkgdb/package/X/</a>

for a number of gdouros-X-fonts that I updated recently and whose
upstream URL had changed.

I have not added these projects to anitya on purpose, because upstream
regularly restructures their website, the source packages do not
contain any version numbers, sometimes packages get updated silently
and the development takes place offline.
My solution for monitoring what upstream does was a

Regression: FileManager1 D-Bus service mix-up in F25 when multiple DEs are installed

desktop environments that come with a FileManager1 (and probably any
other identical) D-Bus service provider, at least when one of them is
GNOME. This might be considered an oversight on upstream's part, but
it causes troubles downstream and we should somehow deal with it.

A few days ago, I started a thread[1] here, about a problem on a
Fedora 25 machine with multiple DEs, where dolphin would take over
whenever I tried to open a desktop folder in GNOME.

File managers compete for desktop domination in F25

Hello all,

After upgrading a computer with multiple DEs to F25 from F23, folders
on GNOME's desktop are managed by dolphin, which runs daemonized and
cannot be killed, unless I also kill kded5 and kdeinit5. There was
already a similar bug about nemo replacing nautilus on the desktop
after a F24→F25 upgrade:

<a href="https://bugzilla.redhat.com/show_bug.cgi?id=1384788" title="https://bugzilla.redhat.com/show_bug.cgi?id=1384788">https://bugzilla.redhat.com/show_bug.cgi?id=1384788</a>

In both cases, our settings seem to be in order. Does anyone have any
clue as to which component (e.g.

liborigin FTBFS

Hello,

Yesterday I was notified that liborigin failed to build in rawhide:
<a href="https://bugzilla.redhat.com/show_bug.cgi?id=1307729" title="https://bugzilla.redhat.com/show_bug.cgi?id=1307729">https://bugzilla.redhat.com/show_bug.cgi?id=1307729</a>

For the past couple of days I've been away on a work trip and I won't
be back until the end of next week. Unless this failure messes someone
else's packages, would it be OK to ignore the error until then?

Best regards
Alex

bodhi: no email notifications for packages in pending state

Hello,

For the last couple of days I have been submitting updates (with fedpkg)
for some of my packages in all the branches. Currently they all appear as
pending in bodhi and I have not received any messages about them, even for
the ones that got positive karma.

Context menu icons in Gnome 3.16

Hi,
I'm messing with an old gtk+ program, that I think it's dead upstream
and I'm trying to see if I can resurrect it. Among other issues, it
should add some entries to nautilus' context menus (which it does) but
I can't get their icons to show. Then I noticed that I'm missing all
of my context menu icons, even though they are enabled in gsettings.
Is this a bug or a feature?

Naming packages when upstream uses dashes in the release version

Hello,

I have been working on a driver package from a hardware vendor and
besides some patches in the code, I am trying to bring the supplied
(messy) spec file close to our guidelines. (While most of the stuff in
the package relies on open source libraries and projects, there are
some files covered by a commercial license, so it will never be
included in fedora.)

What irks me the most, is that the version of the source package is
3.80-1 and this is reflected in the spec file macros (Version: 3.80,
Release 1), which are used extensively.

AppStream license code for public domain works

Hello everyone,

While writing metainfo files for a few fonts, I noticed that their
creator states on his website:

"Fonts and documents in this site are not pieces of property or
merchandise items; they carry no trademark, copyright, license or
other market tags; they are free for any use."

As far as I can tell, that makes them public domain. Is it the same as
CC0-1.0 or is there another license I should choose?

Captive portal detection on wired connections - bug or feature?

During the last hour, I got three pop-ups on my workstation (which is
connected over Ethernet) with blank windows and a title that read "Captive
portal".

non-responsive maintainer: Robin Sonefors aka ozamosi

Hello,

Does anyone have any other means of contacting Robin Sonefors besides
<a href="mailto: ... at flukkost dot nu"> ... at flukkost dot nu</a> and irc?
There are several open bugs (e.g.
<a href="https://bugzilla.redhat.com/show_bug.cgi?id=1197402" title="https://bugzilla.redhat.com/show_bug.cgi?id=1197402">https://bugzilla.redhat.com/show_bug.cgi?id=1197402</a>) that require his
attention, but I can not contact him.

Questions about font packaging, hinting and non-responsive maintainer process

Hello,

A few days ago I was fooling around with Unicode stuff and I noticed
that the Symbola font had been updated upstream, but not in Fedora, so
I decided to have a go at repackaging it and submitting the spec file
to the maintainer. Turns out it was more "fun" than I thought it would
be.

1. There are now 2 fonts, the usual Symbola.ttf plus another one,
Symbola_hint.ttf, which includes hinting instructions.

Which of the changes introduced in F21 might affect bash history?

Hello,

I have upgraded 3 systems to a nonproduct F21 and I have installed F21
to a couple of others using the x86_64 Live Workstation image. They
all suffer from intermittent losses of bash history. When the machines
are booted or rebooted, more than half the times, there are commands
missing from .bash_history files. It's not only that the previous
sessions have not been appended to the files, entire portions of the
files are wiped on occasion, e.g.

GNOME glitches in F21 - Should they be reported and against which components?

Hello,

A few days ago I upgraded my main workstation to F21 and I've noticed a few
annoying glitches, but I don't know if they are all worth reporting and
against which components they should be reported.

1. Window size and position:
While some applications start with their last window size and placement,
others do not; among them, most notable is firefox. It usually starts
maximized and then switches to something like a 7:2 ratio. When it is
maximized and then unmaximized, it never returns to its original size.

2.

Firefox Aurora in rawhide

Would it make sense to include Firefox Aurora / Developer Edition in
rawhide?

Ramblings and questions regarding Fedora, but stemming from gnome-software and desktop environments

I've been meaning to write this for a week, but I wanted to do some
research first. The more I read and thought on it, the issue became
broader, the subject line kept changing and this message starting looking
like an article. I will try to choose my words carefully; I do not intend
to offend anyone nor do I want to appear biased.

I hadn't used any graphical package manager on fedora for almost a decade
(yumex was the last one) because I had been burned too many times and I
don't trust them, but after doing a little work in the AppData area, I
thought I'd take a look at gnome-software.