Orphaned packages looking for new maintainers
by Miro Hrončok
The following packages are orphaned and will be retired when they
are orphaned for six weeks, unless someone adopts them. If you know for sure
that the package should be retired, please do so now with a proper reason:
https://fedoraproject.org/wiki/How_to_remove_a_package_at_end_of_life
Note: If you received this mail directly you (co)maintain one of the affected
packages or a package that depends on one. Please adopt the affected package or
retire your depending package to avoid broken dependencies, otherwise your
package will be retired when the affected package gets retired.
Request package ownership via the *Take* button in he left column on
https://src.fedoraproject.org/rpms/<pkgname>
Full report available at:
https://churchyard.fedorapeople.org/orphans-2020-09-21.txt
grep it for your FAS username and follow the dependency chain.
For human readable dependency chains, see https://packager.fedorainfracloud.org/
For all orphaned packages, see https://packager.fedorainfracloud.org/orphan
Package (co)maintainers Status Change
================================================================================
apache-commons-dbcp mizdebsk, orphan 5 weeks ago
fedora-icon-theme orphan 2 weeks ago
freight orphan 2 weeks ago
geronimo-parent-poms jjelen, mizdebsk, orphan 4 weeks ago
golang-github-mholt- orphan 3 weeks ago
certmagic-0.9
jboss-interceptors-1.2-api orphan 1 weeks ago
joda-time mizdebsk, orphan 5 weeks ago
jvnet-parent mizdebsk, orphan 4 weeks ago
log4j12 mizdebsk, orphan 1 weeks ago
marble-widget orphan, rdieter 3 weeks ago
nodejs-babel-code-frame orphan 2 weeks ago
nodejs-base orphan 2 weeks ago
nodejs-bcrypt nodejs-sig, orphan 2 weeks ago
nodejs-body-parser orphan 2 weeks ago
nodejs-bufferutil nodejs-sig, orphan 2 weeks ago
nodejs-cache-base orphan 2 weeks ago
nodejs-call-matcher orphan 2 weeks ago
nodejs-cross-spawn nodejs-sig, orphan 2 weeks ago
nodejs-cross-spawn-async nodejs-sig, orphan 2 weeks ago
nodejs-css-stringify nodejs-sig, orphan, patches 4 weeks ago
nodejs-css-tree orphan 4 weeks ago
nodejs-doctrine galileo, nodejs-sig, orphan, 2 weeks ago
vjancik
nodejs-espower-location- orphan 4 weeks ago
detector
nodejs-esrecurse nodejs-sig, orphan 2 weeks ago
nodejs-faucet orphan 2 weeks ago
nodejs-fs-dot-notify orphan 2 weeks ago
nodejs-gauge nodejs-sig, orphan 2 weeks ago
nodejs-global-prefix nodejs-sig, orphan 2 weeks ago
nodejs-grunt nodejs-sig, orphan, patches, 4 weeks ago
piotrp
nodejs-grunt-legacy-util nodejs-sig, orphan, patches, 2 weeks ago
piotrp
nodejs-http-signature nodejs-sig, orphan, patches 1 weeks ago
nodejs-jsonm nodejs-sig, orphan 2 weeks ago
nodejs-jsonstream nodejs-sig, orphan 2 weeks ago
nodejs-markdown-it-testgen nodejs-sig, orphan 2 weeks ago
nodejs-node-static nodejs-sig, orphan, tdawson 1 weeks ago
nodejs-nopt nodejs-sig, orphan, patches 1 weeks ago
nodejs-option-cache orphan 2 weeks ago
nodejs-raw-body nodejs-sig, orphan, patches 2 weeks ago
nodejs-rechoir nodejs-sig, orphan 2 weeks ago
nodejs-require-yaml nodejs-sig, orphan 2 weeks ago
nodejs-rfile orphan 2 weeks ago
nodejs-rollup-plugin-commonjs orphan 2 weeks ago
nodejs-rollup-plugin-node- orphan 2 weeks ago
resolve
nodejs-snapdragon orphan 4 weeks ago
nodejs-socket-dot-io-parser orphan 2 weeks ago
nodejs-tap-mocha-reporter nodejs-sig, orphan 2 weeks ago
nodejs-tap-parser nodejs-sig, orphan 2 weeks ago
plexus-ant-factory mizdebsk, orphan 3 weeks ago
plexus-component-factories-pom mizdebsk, orphan 3 weeks ago
python-jose orphan 1 weeks ago
python-kaptan bowlofeggs, jcline, orphan 5 weeks ago
python-libtmux orphan 5 weeks ago
python-zope-configuration infra-sig, orphan, tdabasin 2 weeks ago
relaxngDatatype dbhole, mizdebsk, orphan 3 weeks ago
relaxngcc orphan 3 weeks ago
rmic-maven-plugin mizdebsk, orphan 5 weeks ago
rubygem-delayed_job orphan 4 weeks ago
rubygem- orphan 4 weeks ago
delayed_job_active_record
rubygem-erubis orphan 0 weeks ago
rubygem-jgrep lkundrak, orphan, stevetraylen 2 weeks ago
rubygem-org-ruby orphan 4 weeks ago
rubygem-paint orphan 2 weeks ago
rubygem-rkerberos orphan 2 weeks ago
rubygem-rubypants orphan 4 weeks ago
rubygem-sigdump orphan 5 weeks ago
rubygem-wirb orphan 2 weeks ago
sonatype-oss-parent mizdebsk, orphan 4 weeks ago
umlgraph orphan 2 weeks ago
vdr-skinsoppalusikka orphan 0 weeks ago
winetricks orphan, raphgro, tc01 0 weeks ago
The following packages require above mentioned packages:
Report too long, see the full version at
https://churchyard.fedorapeople.org/orphans-2020-09-21.txt
See dependency chains of your packages at https://packager.fedorainfracloud.org/
See all orphaned packages at https://packager.fedorainfracloud.org/orphan
Affected (co)maintainers (either directly or via packages' dependencies):
abompard: python-zope-configuration
abradshaw: rubygem-erubis
amahdal: rubygem-erubis
anishpatil: nodejs-css-stringify
asrob: rubygem-erubis
athoscr: rubygem-erubis
besser82: rubygem-erubis
bowlofeggs: python-kaptan
brandfbb: rubygem-erubis
chrisw: rubygem-erubis
churchyard: rubygem-erubis
cicku: rubygem-erubis
ckyriakidou: rubygem-erubis
clime: nodejs-nopt, nodejs-grunt-legacy-util, nodejs-grunt
coolsvap: log4j12, geronimo-parent-poms
copr-sig: nodejs-nopt, nodejs-grunt-legacy-util, nodejs-grunt
cottsay: rubygem-erubis
cqi: python-jose
dbhole: relaxngDatatype
dcallagh: nodejs-css-stringify
decathorpe: rubygem-erubis
dfateyev: rubygem-erubis
djbw: rubygem-erubis
djuran: log4j12
dturecek: nodejs-nopt, nodejs-grunt-legacy-util, nodejs-grunt
evgeni: rubygem-erubis
fab: rubygem-erubis, nodejs-css-stringify, nodejs-rechoir
fale: rubygem-erubis
fnasser: log4j12
frostyx: nodejs-nopt, nodejs-grunt-legacy-util, nodejs-grunt
galileo: nodejs-doctrine
gchamoul: rubygem-erubis
germano: rubygem-erubis
gil: log4j12, geronimo-parent-poms
hguemar: rubygem-erubis
hobbes1069: rubygem-erubis
honzaf: rubygem-erubis
ignatenkobrain: python-kaptan, rubygem-erubis, python-libtmux
infra-sig: python-zope-configuration
irina: rubygem-erubis
jaruga: rubygem-erubis
jcline: python-kaptan
jdeluyck: nodejs-rechoir
jhli: rubygem-erubis
jhrozek: rubygem-erubis
jjames: jvnet-parent
jjelen: jboss-interceptors-1.2-api, geronimo-parent-poms, jvnet-parent,
apache-commons-dbcp, log4j12
jpokorny: rubygem-erubis, relaxngDatatype
jskarvad: rubygem-erubis
jsmith: nodejs-cross-spawn, nodejs-global-prefix, nodejs-snapdragon,
nodejs-grunt-legacy-util, nodejs-css-stringify, nodejs-rechoir,
nodejs-cross-spawn-async, nodejs-cache-base, nodejs-rollup-plugin-node-resolve,
nodejs-css-tree, nodejs-nopt, nodejs-base, nodejs-grunt
jstanek: rubygem-erubis
jussilehtola: rubygem-erubis
keitellf: rubygem-erubis
lef: jvnet-parent
lkundrak: rubygem-jgrep
luya: nodejs-css-tree
maha: rubygem-erubis
mizdebsk: sonatype-oss-parent, joda-time, rmic-maven-plugin,
geronimo-parent-poms, relaxngDatatype, jvnet-parent,
plexus-component-factories-pom, apache-commons-dbcp, plexus-ant-factory, log4j12
mmorsi: joda-time, rubygem-erubis
moceap: log4j12, geronimo-parent-poms
mojavelinux: rubygem-erubis
mso: fedora-icon-theme
msuchy: nodejs-nopt, nodejs-grunt-legacy-util, nodejs-grunt
neuro-sig: sonatype-oss-parent
ngompa: rubygem-erubis
niveusluna: rubygem-erubis
nodejs-sig: nodejs-gauge, nodejs-jsonstream, nodejs-rechoir, nodejs-css-tree,
nodejs-tap-parser, nodejs-jsonm, nodejs-require-yaml, nodejs-grunt-legacy-util,
nodejs-bufferutil, nodejs-node-static, nodejs-cross-spawn, nodejs-esrecurse,
nodejs-global-prefix, nodejs-snapdragon, nodejs-cross-spawn-async,
nodejs-tap-mocha-reporter, nodejs-bcrypt, nodejs-http-signature, nodejs-nopt,
nodejs-doctrine, nodejs-css-stringify, nodejs-grunt, nodejs-markdown-it-testgen,
nodejs-raw-body
nonamedotc: rubygem-erubis
olysonek: rubygem-erubis
patches: nodejs-grunt-legacy-util, nodejs-css-stringify, nodejs-rechoir,
nodejs-http-signature, nodejs-nopt, nodejs-grunt, nodejs-raw-body
pbrobinson: rubygem-erubis
pcahyna: rubygem-erubis
piotrp: nodejs-jsonstream, nodejs-grunt-legacy-util, nodejs-css-stringify,
nodejs-nopt, nodejs-grunt
pknirsch: rubygem-erubis
ppisar: rubygem-erubis
praiskup: nodejs-nopt, nodejs-grunt-legacy-util, nodejs-grunt
pstodulk: rubygem-erubis
raphgro: winetricks
rdieter: marble-widget
ruby-packagers-sig: rubygem-erubis
rust-sig: rubygem-erubis
sagitter: nodejs-rechoir
salimma: rubygem-erubis
sandeen: rubygem-erubis
sdgathman: nodejs-nopt, sonatype-oss-parent
sdyroff: rubygem-erubis
sergiomb: nodejs-css-stringify
simo: rubygem-erubis
skisela: rubygem-erubis
snecker: rubygem-erubis
spike: log4j12, geronimo-parent-poms
spontsle: rubygem-erubis
stevetraylen: rubygem-jgrep
stingray: rubygem-erubis
tc01: winetricks, relaxngDatatype, nodejs-grunt-legacy-util,
nodejs-css-stringify, nodejs-bufferutil, nodejs-nopt, nodejs-body-parser,
nodejs-grunt, jvnet-parent, nodejs-raw-body
tdabasin: python-zope-configuration
tdawson: nodejs-node-static
thias: rubygem-erubis
thm: rubygem-erubis
tmz: rubygem-erubis
tross: rubygem-erubis
valtri: rubygem-erubis
vishalv: rubygem-erubis
vjancik: nodejs-doctrine, nodejs-css-stringify
vondruch: rubygem-erubis
xavierb: nodejs-nopt, nodejs-grunt-legacy-util, nodejs-grunt
xenithorb: rubygem-erubis
zbyszek: sonatype-oss-parent
zvetlik: nodejs-css-stringify
--
The script creating this output is run and developed by Fedora
Release Engineering. Please report issues at its pagure instance:
https://pagure.io/releng/
The sources of this script can be found at:
https://pagure.io/releng/blob/master/f/scripts/find_unblocked_orphans.py
3 years, 8 months
Fedora 33 compose report: 20200921.n.0 changes
by Fedora Rawhide Report
OLD: Fedora-33-20200920.n.0
NEW: Fedora-33-20200921.n.0
===== SUMMARY =====
Added images: 0
Dropped images: 5
Added packages: 0
Dropped packages: 0
Upgraded packages: 0
Downgraded packages: 0
Size of added packages: 0 B
Size of dropped packages: 0 B
Size of upgraded packages: 0 B
Size of downgraded packages: 0 B
Size change of upgraded packages: 0 B
Size change of downgraded packages: 0 B
===== ADDED IMAGES =====
===== DROPPED IMAGES =====
Image: Minimal raw-xz aarch64
Path: Spins/aarch64/images/Fedora-Minimal-33-20200920.n.0.aarch64.raw.xz
Image: SoaS raw-xz armhfp
Path: Spins/armhfp/images/Fedora-SoaS-armhfp-33-20200920.n.0-sda.raw.xz
Image: Container_Minimal_Base docker aarch64
Path: Container/aarch64/images/Fedora-Container-Minimal-Base-33-20200920.n.0.aarch64.tar.xz
Image: Xfce raw-xz aarch64
Path: Spins/aarch64/images/Fedora-Xfce-33-20200920.n.0.aarch64.raw.xz
Image: Container_Base docker aarch64
Path: Container/aarch64/images/Fedora-Container-Base-33-20200920.n.0.aarch64.tar.xz
===== ADDED PACKAGES =====
===== DROPPED PACKAGES =====
===== UPGRADED PACKAGES =====
===== DOWNGRADED PACKAGES =====
3 years, 8 months
Conflicting build-ids in chromium and chromium-freeworld
by Marcin Zajączkowski
Hi. There is an ongoing problem with conflicting build-ids in chromium
and chromium-freeworld [1][2]:
> Error: Transaction test error:
> file /usr/lib/.build-id/61/91aba223f60784c4a2fb95cdedcedc97217e5b from install of chromium-freeworld-85.0.4183.102-1.fc32.x86_64 conflicts with file from package chromium-85.0.4183.102-1.fc32.x86_64
> file /usr/lib/.build-id/82/5827dc3adff19282b7b337b044b381e2f226ee from install of chromium-freeworld-85.0.4183.102-1.fc32.x86_64 conflicts with file from package chromium-85.0.4183.102-1.fc32.x86_64
> file /usr/lib/.build-id/c1/a0a2a071572e46f4b3800bbb0f7ba217b42df7 from install of chromium-freeworld-85.0.4183.102-1.fc32.x86_64 conflicts with file from package chromium-85.0.4183.102-1.fc32.x86_64
> file /usr/lib/.build-id/cc/2a382a1ab1ec74354adf012ad958a17f880f88 from install of chromium-freeworld-85.0.4183.102-1.fc32.x86_64 conflicts with file from package chromium-85.0.4183.102-1.fc32.x86_64
> file /usr/lib/.build-id/d9/1c0feec7526201e135457e3a7f4ff4e4aebfea from install of chromium-freeworld-85.0.4183.102-1.fc32.x86_64 conflicts with file from package chromium-85.0.4183.102-1.fc32.x86_64
There is no clear idea why it happens, but my assumption is that due to
the fact of building with the same source code (with similar patches),
some generated shared libraries are the same which generates conflict(s).
The quick look at the algorithm for build-id generation [3] doesn't
answer my question what exactly is taken into account for their
generation and more precisely is there is way to add some "fuzz" (having
different buildroots doesn't help) to distinguish those libraries.
To wrap up:
1. Is there a better way to deal with the aforementioned build-id
conflicts than disable their generation on one side (with "%global
_build_id_links none")?
2. Maybe my assumption about the same generated shared libraries is
wrong and there is something else what can be done to fix the root problem?
[1] - https://bugzilla.redhat.com/show_bug.cgi?id=1869037
[2] - https://bugzilla.rpmfusion.org/show_bug.cgi?id=5743
[3] -
https://github.com/rpm-software-management/rpm/blob/505fe16f863f83637c957...
[4] - https://bugzilla.rpmfusion.org/show_bug.cgi?id=5758
Marcin
P.S. There are cases where it would be best to have those two packages
installed simultaneously [4].
--
https://blog.solidsoft.pl/ - Working code is not enough
3 years, 8 months
Fedora EOL wrt new dist-git branches (and my confusion)
by Miro Hrončok
Hello,
As many of you know, Fedora has an EOL policy that roughly tl;drs to:
"Fedora N goes to End of Life 4 weeks after Fedora N+2 Final Release (GA)."
https://fedoraproject.org/wiki/Fedora_Release_Life_Cycle
The document also says:
> Branches for new packages in the SCM are not allowed for distribution X after
> the Fedora X+2 release and new builds are no longer allowed.
https://fedoraproject.org/wiki/Fedora_Release_Life_Cycle#End_of_Life_.28E...
I've recently discovered that for 10+ years, this was interpreted as:
1. at release of Fedora N+2, new dist-git branches for N are no longer allowed
2. 4 weeks later, Fedora N is EOL
https://pagure.io/releng/issue/9759#comment-687136
When I was told this, I found it very surprising. Mostly because we usually only
ever announce the actual EOL deadline and I've never seen an announcement that
says: "From now on, no new packages for Fedora N are possible."
But also because it doesn't really make sense to me. I can imagine a case when a
bug in Fedora N can be fixed by adding a new package (for example when we
accidentally introduce a new dependency) and I don't understand why this should
not be possible between Fedora N+2 release and Fedora N EOL. Understandably many
packagers might decide to WONTFIX at that point ("It's going EOL in couple weeks
anyway"), but if they choose to fix, we should allow them to do so.
Similarly, before Fedora N is EOL, it is considered supported, and a need to
introduce a new package to a supported Fedora version IMHO is valid, regardless
of the approaching EOL.
So, my question is: Should we fix the document to describe the long standing
practice more understandably, or should we change the practice to allow new
dist-git branches until the actual EOL?
--
Miro Hrončok
--
Phone: +420777974800
IRC: mhroncok
3 years, 8 months
Orphaning "vtun"
by Gabriel L. Somlo
The functionality offered by the vtun package has been completely
subsumed by openssh, since at least with version 8.0. I've switched
to using openssh, and no longer have the need and resources to take
care of vtun.
Free to a good home, or ready for retirement.
Thanks,
--Gabriel
3 years, 8 months
[HEADS-UP] libevent 2.1.12 with a soname bump is coming to Rawhide
by Ondřej Lysoněk
(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
3 years, 8 months