Dear maintainers.
Based on the current fail to build from source policy, the following packages
should be retired from Fedora 39 approximately one week before branching.
5 weekly reminders are required, hence the retirement will happen
approximately in 2 weeks, i.e. around 2023-08-01.
Policy:
https://docs.fedoraproject.org/en-US/fesco/Fails_to_build_from_source_Fai...
The packages in rawhide were not successfully built at least since Fedora 36.
This report is based on dist tags.
Packages collected via:
https://github.com/hroncok/fedora-report-ftbfs-retirements/blob/master/ft...
If you see a package that was built, please let me know.
If you see a package that should be exempted from the process,
please let me know and we can work together to get a FESCo approval for that.
If you see a package that can be rebuilt, please do so.
Package (co)maintainers
================================================================================
DecodeIR leamas
apache-commons-fileupload jerboaa, jjelen, mizdebsk, spike
avarice lucilanga
burp cicku, kaptk2
clang12 tstellar
cvise mpolacek
emacs-common-ess alexlan, jamatos
fasttext kenhys
glibc32 codonell, fweimer, jakub, mcermak
golang-github-burntsushi-xgbutil eclipseo, go-sig
golang-github-chifflier-nfqueue fab, go-sig
golang-github-cupcake-rdb eclipseo, go-sig
golang-github-d5-tengo-2 fab, go-sig
golang-github-docker-slim eclipseo, go-sig
golang-github-facebookarchive-inject agerstmayr, go-sig, mgoodwin, nathans
golang-github-facebookarchive-structtag agerstmayr, go-sig, mgoodwin, nathans
golang-github-facebookgo-clock eclipseo, go-sig
golang-github-facebookgo-ensure dcavalca, go-sig
golang-github-facebookgo-httpdown go-sig, orphan
golang-github-facebookgo-stack dcavalca, go-sig
golang-github-facebookgo-stats go-sig, orphan
golang-github-fonts-dejavu go-sig, orphan
golang-github-ghemawat-stream eclipseo, go-sig
golang-github-google-tspi go-sig, orphan
golang-github-gorp-3 dcavalca, go-sig
golang-github-haproxytech-models bdperkin, go-sig
golang-github-influxdata-tdigest go-sig, orphan
golang-github-jackc-pgproto3 eclipseo, go-sig
golang-github-jackc-pgservicefile eclipseo, go-sig
golang-github-michaeltjones-walk go-sig, orphan
golang-github-nkovacs-streamquote eclipseo, go-sig
golang-github-phpdave11-gofpdi go-sig, orphan
golang-github-powerman-check eclipseo, go-sig
golang-github-quay-clair-3 eclipseo, go-sig
golang-github-remind101-migrate eclipseo, go-sig
golang-github-tj-buffer go-sig, orphan
golang-github-vmihailenco-msgpack go-sig, orphan
golang-github-vmware-vmw-guestinfo eclipseo, go-sig
golang-github-wsxiaoys-terminal go-sig, orphan
golang-github-x-cray-logrus-prefixed-formatter dcavalca, go-sig
golang-github-zmap-zlint eclipseo, go-sig
golang-github-zmap-zlint-2 go-sig, orphan
golang-go4 eclipseo, go-sig, jchaloup
golang-gopkg-redis-2 go-sig, orphan
golang-gopkg-retry-1 eclipseo, go-sig
golang-gopkg-seborama-govcr-2 go-sig, qulogic
golang-gopkg-sourcemap-1 eclipseo, go-sig, jchaloup
golang-gvisor eclipseo, elmarco, go-sig
golang-k8s-legacy-cloud-providers go-sig, orphan
golang-rsc-qr go-sig, qulogic
golang-sigs-k8s-kustomize dcavalca, go-sig
golang-vitess eclipseo, go-sig
hibernate-jpa-2.1-api jjelen
httping fab
jblas zbyszek
libffi3.1 codonell
libifp konradm
log4c stevetraylen, valtri
mongo-cxx-driver hhorak, mmuzila
mspdebug till
multican jnovy
nom-tam-fits gil, lupinix, zbyszek
opentracker cicku, lbazan
procinfo-ng fab
racket dbenoit
rubygem-rspec-collection_matchers pvalena
serp jjelen
sispmctl jirka, reanimator
spew jonathanspw
telepathy-qt jgrulich, jreznik, kde-sig, rdieter
usbsoftrock lucilanga
xml-maven-plugin mbooth, mizdebsk
xmpcore jjelen
This one has a long long list of deps which will break if it is
retired and there is a pull-req here fixing the FTBFS:
Are there any objections against solving it with the rebase to
a newer git snapshot (it already is a git snapshot) ?
If not then I'll use my proven-packager rights to get this
pull-request merge and close the FTBFS bug.
Mikolaj any objections against merging the pull-request ?
Miro can you hold of on retiring xmvn-connector-ivy please ?
Regards,
Hans