DevHeads.net

Postings by Igor Gnatenko

Escaping macros in %changelog

Hash: SHA256

Hello everyone,

It seems that a lot of people have %file, %check, %build, %whatsoever in their
changelog section.

Is there any reason I should not go and automatically escape them?

%check → %%check
%build → %%build
%whatsoever → %%whatsoever

There might be valid use-cases, but I'm not sure if they really are:
%{_localstatedir}/ft/ → %%{_localstatedir}/ft/

Thoughts?

Packaging DSO symlinks

Hash: SHA256

Hello,

You might have seen that we are trying to eliminate /sbin/ldconfig from
scriptlets which would speedup installation / upgrade of packages
**significantly**.

One of cases Florian brought that in case of libcrypt/libcrypt-nss, libraries
didn't have symlinks, so if it would not call ldconfig in its scriptlet, then
any packages which depend on libcrypt.so would fail to execute.

In 99% (this number came just out of my head, not a real investigation) of
packages, we always package those symlinks.

So I'm going to push change to glibc which during build process executes
ldconf

Removal of systemd-units

Hash: SHA256

It's been 6 years since systemd-units package was merged to systemd, but
package maintainers still use it. EL7 has same guidelines as Fedora, so it is
safe to make it compliant with Guidelines even there. This is very safe change.

It's just 198 packages and we are just going to fix them for you in following
days.

Plan to remove libxml2-static

Hash: SHA256

Hello,

is anybody against of removal of libxml2-static package? It is not used by any
Fedora package.

Unannounced SONAME bump in tinyxml2

Hash: SHA256

<a href="https://src.fedoraproject.org/rpms/tinyxml2/c/3600750a8f1b0eaa6cab346496fd75a07" title="https://src.fedoraproject.org/rpms/tinyxml2/c/3600750a8f1b0eaa6cab346496fd75a07">https://src.fedoraproject.org/rpms/tinyxml2/c/3600750a8f1b0eaa6cab346496...</a>
ea749cb

Manging shebangs in Rawhide

Hash: SHA256

Hello,

I'm planning to merge PR[0] somewhere later this week.

rust-pest changes license from MPLv2.0 to MIT or ASL 2.0

Hash: SHA256

Thanks for attention.

EPEL support in "master" branch (aka speeding up Fedora development)

Hash: SHA256

Hello,

I know that many of you like to have just one branch which builds everywhere
(starting from el6), but this really slows down development of Fedora for many
years.

RFC: Dropping %{?_isa} hack

Hash: SHA256

Hello,

Does anybody know why we are still using %{?_isa} thing?

DNF/libsolv forcefully install 64bit package for any 32bit package in
transaction. So it is not possible to get 32bit package without 64bit
counterpart.

So then what's the reason of using %{?_isa}? Just some old cruft from yum era?
Can we drop it? Thoughts?

Please stop re-adding gtk-update-icon-cache scriptlets (for Fedora)

Hash: SHA256

Hello,

I'm working on removing all this cruft from all our packages (and creating
conditionals for all packages which have epel branch).

Unfortunately some maintainers adding them back with conditionals like:
%if 0%{?fedora} < 28 || 0%{?rhel} < 8

1. Those scriptlets are not needed since ~ F24 era
2.

Updates which are never pushed to stable

Hash: SHA256

Hello,

I noticed that for multiple release we have updates which stuck in bodhi for
many months until distro goes EOL.

I wonder if we should just auto-unpush updates which are in testing in 1(?)
month? Thoughts?

Removing old cruft, e.g. Provides: systemd-units (was Re: What to I have to do....)

Hash: SHA256

After reading all responses in thread which is mentioned in subject I think we
need to develop some policies / procedures how to deal with old cruft, for
example:

- - Requires: systemd-units
- - Requires: /bin/mktemp

Former has changed to systemd in guidelines X years ago (not sure when exactly,
before I did my first package which contains systemd units, so I would guess
something like 5-6 years ago).

Package naming question

Hash: SHA256

Hello,

I would like to hear opinion of other packagers about naming. We have
`parallel` utility implemented in Rust which is drop-in replacement for GNU
parallel. I was thinking how to name package and how people would expect it to
be named. So far options are:

* rust-parallel
* parallel-rust
* parallel-rs

I dislike first one because it is not ending up in completion while second and
third are quite good.

Thoughts?

Annobin Change is implemented

Hash: SHA256

Hello everyone,

as of now, Annobin[0] has been enabled in Rawhide. This is special plugin for
gcc so something might break due to it (but not expected). Don't hesitate to
open a bug in that case.

Just small heads up.

[0] <a href="https://fedoraproject.org/wiki/Changes/Annobin" title="https://fedoraproject.org/wiki/Changes/Annobin">https://fedoraproject.org/wiki/Changes/Annobin</a>

7 applications written in Rust are available in Rawhide

Hash: SHA256

* base100
<a href="https://github.com/AdamNiederer/base100" title="https://github.com/AdamNiederer/base100">https://github.com/AdamNiederer/base100</a>
Encode things into Emoji.

Base

Missing libwebm

Hash: SHA256

Hello,

is there any reason we don't have libwebm[0] packaged? I'm packaging
libopenglrecorder[1] which appears to bundle some parts of it.

[0]https://chromium.googlesource.com/webm/libwebm
[1]https://github.com/Benau/libopenglrecorder

rust-crc-core changes license from MIT to MIT or ASL 2.0

Hash: SHA256

Nothing really interesting, but sending as per our policies.

Weekend's replacement for limb (creating new repositories)

Hash: SHA256

Hello,

I think many people work on new packages during weekends, but it's not possible
to get any new repos[0] during weekend (right now there are 73 opened tickets
in fedora-scm-requests). Is there someone who could process tickets during the
weekends? Can I help with this myself?

[0]https://pagure.io/releng/fedora-scm-requests/issues

Removal of obsolete /bin/* Provides from coreutils

Hash: SHA256

Hello,

After removal[0] of other ancient Provides from coreutils, it is time[1] to
remove next legacy part, /bin/* Provides.

There are some number of packages still relying on them, I've fixed most of
them already, although there are some packages which need some special care
(including reporting to upstream).

RFC: -Wl,--as-needed by default

Hash: SHA256

Hello,

I'm interested why we still don't have this flag in our CFLAGS? It seems that
other distributions like openSUSE enable it by default and it helps in many
cases to avoid over-linking (for example, see thread about poppler).

Are there any reasons not to add it?

protobuf 3.4.1 is coming

Hash: SHA256

Hi everyone,

I'm going to build protobuf 3.4.1 in Rawhide later today and rebuild all
dependent packages. There are no incompatible changes as I can see.

Just sending heads-up.

Removed legacy provides from coreutils

Hash: SHA256

Yesterday we removed following Provides/Obsoletes from coreutils.
- - fileutils
- - sh-utils
- - stat
- - textutils
- - mktemp

First four never been separate packages (at least from what I can see
in dist-git), last one disappeared in fc10...

I've adjusted all 16 packages relying on those provides:
a2ps
amanda
autofs
foomatic
logwatch
netdump-server
nfs-utils
nordugrid-arc
nut
pcp
rhn-client-tools
rpmrebuild
samba
smartmontools
vzctl
xinetd

Also I found that some of those packages still use systemd-units..
Please switch to new way of doing systemd units packaging as per
guidel

libtimidity changes license from LGPLv2+ to LGPLv2+ or Artistic

Hash: SHA256

Upstream decided to dual-license project. Which is probably good

SDL2_image changes license from LGPLv2+ to LGPLv2+ and zlib

Hash: SHA256

Since 2.0.2, SVG support is included.. And as usual, in a bad way by
bundling some library with custom changes. Now it is nanosvg where
upstream never had any releases.

Replacing HAL policy (yes, in 2017)

Hash: SHA256

Hi everyone,

today I was using dfu-programmer to update my nitrokey storage firmware
and I found out that it is old version with some packaging bugs and
also it contains file "%{_datadir}/hal/fdi/information/20thirdparty/10-
dfu-programmer.fdi"..[0]

I've never seen HAL in my life (probably when I was just starting with
Linux) so my question is should I somehow write udev / policykit rule
for it or just drop it?

[0] <a href="https://github.com/dfu-programmer/dfu-programmer/blob/master/fedora" title="https://github.com/dfu-programmer/dfu-programmer/blob/master/fedora">https://github.com/dfu-programmer/dfu-programmer/blob/master/fedora</a>
/10-dfu-programmer.fdi

Cython 0.27.1 is coming!

Hash: SHA256

Hi everyone,

I'm going to update Cython to 0.27.1 (from 0.25.2) in F25+ now-ish.
No breakages expected, only bugfixes and improvements

GnuPG 2.2.0 and replacement of GnuPG1

Hash: SHA256

GnuPG 2.2.0 has --enable-gpg-is-gpg2 which would install compat symlink
from /usr/bin/gpg to /usr/bin/gpg2..

Is it time to retire gnupg (v1) ?

RFC: retiring yum

Hash: SHA256

So I think F28/F29 would be best time for retiring YUM. Right now DNF
should be already stable and provide same capabilities (or documented
that something will not be supported).

Hopefully infrastructure / rel-eng folks will finally add support for
rich dependencies[0] which would mean that yum will not work in Fedora
anyway, so..

Do you still have some critical missing functionality in DNF? And let
us know reasons why would you like to keep YUM available (hopefully
there are no)!

P.S.

Retirement of pygpgme is coming

Hash: SHA256

Hello,

pygpgme is dead since 2013, I've wrote and applied some patches to make
it to work with latest gnupg2/gpgme stack, but since March it FTBFS (so
I added `|| :` for tests). I'm planning to retire pygpgme from F27
right before branching.

libgit2 0.26.x is coming into Rawhide

Hash: SHA256

I'll be updating libgit2 stack to 0.26.x this weekend, there is only
one breaking change and looks like none from packages are affected.