[HEADS-UP] libevent 2.1.12 with a soname bump is coming to Rawhide

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

 



(maintainers of dependent packages in BCC)

Hi,

libevent will be rebased to 2.1.12 in Rawhide. The new version
includes a soname bump. Rebuilds of libevent and dependent packages
will happen in side tag 'f34-build-side-30069'.

Due to the nature of the dependency tree, we can't simply build all
dependent packages at the same time. We'll have to build in
batches. See my plan at the bottom of the email.

I'll reach out to individual maintainers when it's time to rebuild
their package. However, the new libevent is already built in the tag,
so if you own a package from the "Initial set", you don't have to wait
for me and you can start the rebuild right away using the following
command.

fedpkg build --target=f34-build-side-30069

I've performed test rebuilds of the dependent packages in COPR and it
went mostly well, so I don't expect any big issues. Some notable
things I found during the test rebuilds:
- some of the packages (libreswan, perl-Event-Lib, sems) fail to build
  for unrelated reasons. Unless these are fixed, they'll become
  uninstallable. I've notified their owners.
  - libreswan should hopefully get fixed soon by its own rebase
  - perl-Event-Lib will likely get orphaned
  - no response about sems
- I wasn't able to rebuild community-mysql, because for some reason,
  it fails to build in COPR (but builds fine in Koji). I guess we'll
  have to build this one with our fingers crossed.
- the new libevent breaks transmission slightly. Hopefully this will
  get fixed soon. Worst-case scenario, we'll temporarily revert the
  problematic libevent change, or come up with some temporary quick
  fix for transmission. Reported upstream:
  https://github.com/transmission/transmission/issues/1437
- due to a build dep loop, avahi will need to be bootstrapped
- I'm not sure if chromium really utilizes the system libevent - it
  seems to bundle it's own version. Nevertheless, it has BuildRequires
  for libevent-devel, so it's included in my list.
  
List of dependent packages:
- 389-ds-base
- addrwatch
- avahi
- ccnet
- chromium
- community-mysql
- coturn
- fragments
- fstrm
- gearmand
- getdns
- groonga
- icecat
- Io-language
- ladvd
- libasr
- libcouchbase
- libmemcached
- libreswan
- libverto
- links
- lldpd
- lua-event
- mediaconch
- memcached
- mpris-scrobbler
- nbd-runner
- netatalk
- nfs-utils
- nsd
- ntp
- ocproxy
- openmpi
- opensmtpd
- perl-Event-Lib
- pgbouncer
- php-pecl-event
- php-pecl-http
- php-pecl-memcached
- pmix
- qt5-qtwebengine
- remctl
- scanssh
- seafile
- sems
- sslsplit
- sstp-client
- suricata
- thrift
- tmate
- tmux
- tor
- transmission
- trickle
- unbound
- uwsgi
- zabbix

Here is my plan for the rebuild process. Note that the "After ... is
rebuilt" paragraphs can be executed in any order - just their
respective dependencies must be met.

Initial set:
- avahi - needs to be bootstrapped
- packages that I haven't been able to rebuild:
  - community-mysql, libreswan, perl-Event-Lib, sems
- other: addrwatch, ccnet, coturn, groonga, ladvd, libasr,
  libverto, links, lldpd, memcached, mpris-scrobbler, nbd-runner,
  nfs-utils, nsd, ntp, ocproxy, opensmtpd, pgbouncer, php-pecl-event,
  php-pecl-http, pmix, remctl, scanssh, seafile, sslsplit,
  sstp-client, suricata, tmate, tmux, trickle, unbound, uwsgi, zabbix

After avahi is rebuilt, we can rebuild:
389-ds-base, fragments, fstrm, icecat, libcouchbase, lua-event,
netatalk, qt5-qtwebengine, thrift, tor, transmission

After unbound and avahi is rebuilt, we can rebuild:
chromium, getdns

After memcached is rebuilt, we can rebuild:
libmemcached

After memcached and libmemcached is rebuilt, we can rebuild:
gearmand, Io-language, php-pecl-memcached

After qt5-qtwebengine is rebuilt, we can rebuild:
mediaconch

After pmix and avahi is rebuilt, we can rebuild:
openmpi

Best regards
Ondřej Lysoněk
_______________________________________________
devel mailing list -- devel@xxxxxxxxxxxxxxxxxxxxxxx
To unsubscribe send an email to devel-leave@xxxxxxxxxxxxxxxxxxxxxxx
Fedora Code of Conduct: https://docs.fedoraproject.org/en-US/project/code-of-conduct/
List Guidelines: https://fedoraproject.org/wiki/Mailing_list_guidelines
List Archives: https://lists.fedoraproject.org/archives/list/devel@xxxxxxxxxxxxxxxxxxxxxxx




[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]
[Index of Archives]     [Fedora Announce]     [Fedora Users]     [Fedora Kernel]     [Fedora Testing]     [Fedora Formulas]     [Fedora PHP Devel]     [Kernel Development]     [Fedora Legacy]     [Fedora Maintainers]     [Fedora Desktop]     [PAM]     [Red Hat Development]     [Gimp]     [Yosemite News]

  Powered by Linux