DevHeads.net

Postings by Georg Sauthoff

koji build failure but no build.log

Hello,

a dependency of a package of mine lately failed to be rebuilt for Python
3.8/f32:

<a href="https://src.fedoraproject.org/rpms/python-asynctest/c/f7a6e498607f4635ec76c4759e8b51b3ea9367ab" title="https://src.fedoraproject.org/rpms/python-asynctest/c/f7a6e498607f4635ec76c4759e8b51b3ea9367ab">https://src.fedoraproject.org/rpms/python-asynctest/c/f7a6e498607f4635ec...</a>

The result on the build page
<a href="https://koji.fedoraproject.org/koji/taskinfo?taskID=37184775" title="https://koji.fedoraproject.org/koji/taskinfo?taskID=37184775">https://koji.fedoraproject.org/koji/taskinfo?taskID=37184775</a> reads:

But this build.log file isn't linked from that page.

How come?

Bug or feature?

Best regards
Georg

manpath.be, man page package checks/policy

Hello,

so I've created <a href="https://manpath.be" title="https://manpath.be">https://manpath.be</a> - a site that provides access to the
man pages of several distributions - including several Fedora and CentOS
versions.

See also its about page <a href="https://manpath.be/about" title="https://manpath.be/about">https://manpath.be/about</a> for some of its
features (e.g. permalinks, short links, reverse links ...).

While working on this project I noticed a few issues with the man pages
of Fedora packages:

Some packages include man pages auto-generated by doxygen. In my
experience, those man pages are usually pretty human un-readable and
thus quite useless.

Inconsistent dnf provides result

Hello,

I noticed a case where the `dnf provides` output is inconsistent.

Policy regarding redundant dependencies

Hello,

when packaging a C/C++ program, the rpm automatic dependency feature
usually works well for shared libraries.

That mean when program 'bar' needs libfoo-devel at build time it's
sufficient to add

BuildRequires: libfoo-devel

and I can omit

Requires: libfoo

because rpm automatically adds something like:

libfoo.so.1()(64bit)

Of course, I could still add a superfluous

Requires: libfoo

and then the resulting binary package would contain a redundant
dependency like this:

libfoo
libfoo.so.1()(64bit)

Has Fedora a policy against such redundant dependencies?

Be

Policy regarding service preset enabled (e.g. performance co-pilot)

Hello,

is there a policy regarding auto-enabling/disabling an installed systemd
service?

I'm asking because installing the dstat replacement[1] in Fedora 29
resulted in 3 additional always running systemd services[2] and 2 open
ports.

In contrast, after installing postgresql the postgresql systemd service
has vendor preset disabled (i.e.

dracut-sshd in fedora - ssh access to early cryptsetup/dracut shell

Hello,

so I wrote dracut-sshd - a dracut module that adds sshd to the
initramfs such that one is able to remotely access early
userspace for e.g.

zlib compress bit-identical output on different archs - goal or non-goal?

Hello,

during packaging of a new python-img2pdf version I noticed that 2
unit-test cases fail on aarch64.

This is caused by zlib.compress() yielding different output on aarch64
and x86-64. Which triggers the failure because the unit-test case just
compares the result after compression (it's a small PDF that contains a
compressed image - and that PDF is compared against a reference PDF).

I checked the aarch64 compress output and it's valid zlib data, i.e. I can
decompress it on both aarch64 and x86-64 and get the same decompression
result (i.e.

Announcement: python-asyncssh license change EPL1 to EPL2/GPLv2+

Hello,

fyi, with the update to the latest upstream version 1.14, the
python-asyncssh package (binary subpackage: python3-asyncssh) also
updated its license from 'EPL-1.0' to 'EPL-2.0 or GPLv2+' (a.k.a. as
EPL-2.0 with GPLv2+ secondary license clause).

See also:

- Package Description:
Python 3 library for asynchronous client and
server-side SSH communication.