Alternative buildroot as a development tool
by Aleksandra Fedorova
Hi, all,
This topic goes along the lines of Matthew’s Operating System Factory
discussion[1], but with a slightly different angle. It also is the
generalization of the Change we have proposed recently [2]
So let me start with the problem:
In Fedora now we have a well known and established process of how to
deal with updates that bring new content through packages. There are
ways to package new content side by side with the old one, to perform
a non-disruptive testing, iterate and upgrade.
What I think is missing is the way to safely iterate on the process,
which happens after the content is packaged. Examples are: changes to
buildroot configuration as in [2], changes in comps files, for example
required for Minimization Objective [3], changes in compose building
process, changes in Mass Rebuild and so on.
For such changes we have to use an all-or-nothing approach, which
means we either implement the change too early or postpone it for too
long.
To add flexibility to the Fedora process, I’d like to propose the
concept of alternative buildroots.
------
Note: The naming is hard here, and while I tend to call it
“buildroot”, it actually needs to be called “alternative everything,
except the srpms”.
I think we shouldn’t use the word “variant”, “spin”, “flavour” or
something like that to describe it, as it is strictly the shared
development playground linked to the latest Fedora Rawhide state and
focused on the build and compose process. It is definitely not the
alternative Fedora. It shouldn’t have releases on its own, it has no
branches in the source code and it doesn’t target end-users.
------
The good thing is that, with the distributed CI approach we have
implemented, we are ready to consume the feedback from such
alternative setups in a non-blocking but informative way. I think we
can extend our use of CI machinery so that it simplifies the
development process for everyone, removing redundant heads-ups but
increasing the targeted collaboration in places where it is actually
needed.
### Use cases ###
The first example of such a buildroot is provided by the CPU baseline
testing [1].
There will be more, since we may want to work on comps files for
Minimization Objective.
There is also one particularly important case of the RHEL bootstrap:
RHEL tries hard to inherit as much as possible from Fedora, but since
both Fedora and RHEL have historically different build and compose
configurations, it is often problematic to deal with dependency and
build issues which arise from it. To the point that RHEL sometimes
just can’t use Fedora as an origin, and needs to find its way around.
The alternative buildroot targeting CentOS and RHEL would provide an
open shared development environment. There we can work on converging
the RHEL process to Fedora, and also on improving Fedora process with
things, which RHEL and CentOS have discovered.
### Proposal ###
This idea doesn’t quite fit into the Fedora Changes framework, as
there is no actual change to Fedora. And we don't even have a concept
of an Infrastructure Change at this point.
But there are several items one can think about:
1) Though as I said above the “buildroot” term is slightly misleading
but it is a start. And the change [2] is a first step, the prototype,
which goes into that direction. Its main focus is the compiler
parameters rather than anything else.
2) The second part of the proposal is to setup a CentOS/RHEL-targeting
buildroot and compose, with a focus on comps, dependency chains and
compose differences. Which I think overlaps in a certain way with the
Minimization Objective.
3) And the third part is to generally develop the alternative
buildroot as a concept. It should be our toolbox item, something
similar to the alternative architectures approach. So that it can be
requested by anyone based on the existence of a SIG or working group,
which would own and maintain it.
[1] https://lists.fedoraproject.org/archives/list/devel@lists.fedoraproject.o...
[2] https://lists.fedoraproject.org/archives/list/devel@lists.fedoraproject.o...
[3] https://lists.fedoraproject.org/archives/list/devel@lists.fedoraproject.o...
--
Aleksandra Fedorova
bookwar
4 years, 4 months
Effort to remove libdb
by Filip Janus
Hi all,
as you maybe know the BerkeleyDB 6.x has a more restrictive license than
the previous versions (AGPLv3 vs. LGPLv2), and due to that many projects
cannot use it.
Few years ago there was an effort to reduce the number of dependent
packages on BerkeleyDB(libdb). And nowadays situation seems to be almost
the same. Here is
the link with packages dependent on libdb[1] from previous effort, which is
truthful for nowadays situation. As a member of the database team which is
responsible for libdb, I would like to know your opinions on this problem,
because many components have many specific cases where is libdb used.
Nowadays we would like to remove libdb from Fedora as soon as possible, in
the best case from Fedora 33. But I am afraid, that it isn't real.
I have discussed this issue with my colleagues and we propose an approach.
We found that the biggest problem would occur in updating components from
versions that support libdb to versions without this support. Here could
arise problems of inconsistency.
Our approach assumes to convert old libdb databases to other supported
database format in each package related to this libdb issue. Result would
be Fedora without libdb.
I know that this approach probably isn't perfect.
Therefore I would like to ask for Your opinions, suggestions and every
problem clarification.
Thank you very much for any help. I welcome every opinion.
[1]
https://fedoraproject.org/w/index.php?title=User:Pkubat/Draft_-_Removing_...
Fiip Januš - Red Hat Associate Developer Engineer - Databases Team
4 years, 4 months
Fedora 32 Self-Contained Change proposal: Python3-rdiff-backup
by Ben Cotton
https://fedoraproject.org/wiki/Changes/Python3-rdiff-backup
== Summary ==
rdiff-backup is a python based backup tool. While development stopped
for many years, it's now resumed upstream and a python3 port has been
(almost) completed. Unfortunately, the python2 and python3 versions
will not interoperate, although backups made with either version are
compatible. Because of this we want to push the new python3 based
rdiff-backup to all supported releases when Fedora 32 is released.
== Owner ==
* Name: [[User:Kevin| Kevin Fenzi]] and [[User:FrankCrawford| Frank Crawford]]
== Detailed Description ==
We want to move to the upstream supported python3 version, but we want
to make sure people with mixed infrastructures are able to upgrade all
their hosts with the new version so they continue to interoperate, as
there are numerous incompatibilities between the python2 and python3
program implementation, such as default string types and pickle
definitions.
Like most backup programs, it is a long term commitment by the user
and the end of life of python2 has forced a migration to a python3 for
the code. This will allow rdiff-backup repositories to continue to be
used going forward.
== Benefit to Fedora ==
Old, no longer maintained python2 version will be replaced with new
2.0.0 python3 version.
This update will also allow a number of locally maintained patches to
be dropped as they have now been incorporated into the revitalised
upstream project.
This is also a major upgrade to this backup software and is the
primary Linux distribution of the current developer, and will put
Fedora in a good position to introduce new features going forward.
== Scope ==
* Proposal owners:
# Test beta releases via rawhide and COPR (completed for first beta
release, planned for upcoming beta releases).
# Gather feedback from this testing (in progress).
# Wait for final 2.0.0 release. This is planned for Feb 2020.
# Once f32 is out, push EPEL and older stable releases as well (due to
compatibility issues).
* Other developers: N/A (not a System Wide Change)
* Policies and guidelines: N/A
* Trademark approval: N/A (not needed for this Change)
== Upgrade/compatibility impact ==
Previous Python2 versions are not interoperable with the new Python3
version, when used for remote operation, however, the actual backups
are compatible between the two. This does require that all hosts used
for remote operations are upgraded at the same time to continue to
perform remote operations.
== How To Test ==
N/A (not a System Wide Change)
== User Experience ==
rdiff-backup will stop working in Fedora with the retirement of
python2 and users will need to move to a new backup setup.
== Documentation ==
N/A (not a System Wide Change)
== Release Notes ==
Existing backups are compatible between older (v1.2.8/v1.3.x) and new
(v2.0.0) versions of rdiff-backup, however, remote operations are not
and require all hosts to use either the python2 (i.e. v1.2.8/v1.3.x)
or python3 (v2.0.0) version. However, as python2 is now end-of-life,
there is no further development on the older version and all future
patches will be performed on the python3 version.
--
Ben Cotton
He / Him / His
Fedora Program Manager
Red Hat
TZ=America/Indiana/Indianapolis
4 years, 4 months
Fedora 32 Self-Contained Change proposal: Update Haskell packages to
Stackage LTS 14
by Ben Cotton
https://fedoraproject.org/wiki/Changes/Haskell_Stackage_LTS_14
== Summary ==
Haskell libraries and packages will be updated from Stackage LTS 13 to
the new versions in Stackage LTS 14.
== Owner ==
* Name: [[User:Petersen| Jens Petersen]]
* Email: <petersen(a)redhat.com>
* Name: [[Haskell_SIG| Haskell SIG]]
* Email: <haskell(a)lists.fedoraproject.org>
== Detailed Description ==
The Haskell packages in Stackage LTS provide a consistent tested set
of package versions that are known to build together.
Fedora only has a small subset of the (2000+) Haskell packages in
Stackage, plus a few packages only found in the upstream Hackage
repository.
This Change involves updating the Fedora Haskell packages based on
Stackage LTS 13 in F31 to the newer versions found in LTS 14.
There is no version change to the ghc Haskell compiler, which will
remain at 8.6.5.
== Benefit to Fedora ==
Fedora users and developers will benefit by having the latest stable
set of Haskell packages available.
== Scope ==
* Proposal owners:
** Haskell packages with version from LTS 13 will be updated to LTS 14
** Haskell packages not in LTS or Stackage Nightly will be updated to
the latest possible version from Hackage.
** Haskell packages to be built in a `f32-ghc` sidetag in Koji.
** Complete all the builds and required rebuilds due to dependency bumps
* Other developers: N/A (not a System Wide Change)
* Release engineering: [https://pagure.io/releng/issue/9177 #9177]
** Create Koji sidetag
** Push all the built packages from the sidetag to Rawhide.
* Policies and guidelines: N/A (not a System Wide Change)
* Trademark approval: N/A (not needed for this Change)
== Upgrade/compatibility impact ==
N/A (not a System Wide Change)
== How To Test ==
* `# dnf install ghc-*-devel`
== User Experience ==
Latest stable Haskell packages will be available to users.
== Dependencies ==
N/A (not a System Wide Change)
== Contingency Plan ==
* Contingency mechanism: (What to do? Who will do it?) N/A (not a
System Wide Change)
* Contingency deadline: N/A (not a System Wide Change)
* Blocks release? N/A (not a System Wide Change)
== Documentation ==
https://www.stackage.org/lts-14 (note not all LTS packages are
included in Fedora)
--
Ben Cotton
He / Him / His
Fedora Program Manager
Red Hat
TZ=America/Indiana/Indianapolis
4 years, 4 months
Schedule for Mondays's FESCo Meeting (2020-01-20)
by David Cantrell
Following is the list of topics that will be discussed in the
FESCo meeting Monday at 15:00UTC in #fedora-meeting-1 on
irc.freenode.net.
To convert UTC to your local time, take a look at
http://fedoraproject.org/wiki/UTCHowto
or run:
date -d '2020-01-20 15:00 UTC'
Links to all issues to be discussed can be found at:
https://pagure.io/fesco/report/meeting_agenda
= Discussed and Voted in the Ticket =
Delay beginning of F32 Mass Rebuild
https://pagure.io/fesco/issue/2326
APPROVED (+7, 0, -0)
F33 System-Wide Change: Binutils 2.34
https://pagure.io/fesco/issue/2322
APPROVED (+5, 0, -0)
F32 Self-Contained Change: Mono 6.6
https://pagure.io/fesco/issue/2321
APPROVED (+4, 0, -0)
F32 System-Wide Change: Systemd presets for user units
https://pagure.io/fesco/issue/2319
APPROVED (+6, 1, -0)
F32 System-Wide Change: Restart services at end of rpm transaction
https://pagure.io/fesco/issue/2318
APPROVED (+4, 1, -0)
F32 System-Wide Change: golang 1.14
https://pagure.io/fesco/issue/2317
APPROVED (+6, 0, -0)
F32 System-Wide Change: GCC 10
https://pagure.io/fesco/issue/2316
APPROVED (+6, 0, -0)
F32 System-Wide Change: Move fonts language Provides to Langpacks
https://pagure.io/fesco/issue/2315
APPROVED (+4, 0, -0)
F32 System-Wide Change: Adopting sysusers.d format
https://pagure.io/fesco/issue/2314
APPROVED (+4, 1, -0)
Nonresponsive maintainer: dborkmann
https://pagure.io/fesco/issue/2313
APPROVED (+4, 0, -0)
= New business =
#topic F32 System-Wide Change: Enable EarlyOOM - https://fedoraproject.org/wiki/Changes/EnableEarlyoom
https://pagure.io/fesco/issue/2320
= Open Floor =
For more complete details, please visit each individual
issue. The report of the agenda items can be found at
https://pagure.io/fesco/report/meeting_agenda
If you would like to add something to this agenda, you can
reply to this e-mail, file a new issue at
https://pagure.io/fesco, e-mail me directly, or bring it
up at the end of the meeting, during the open floor topic. Note
that added topics may be deferred until the following meeting.
--
David Cantrell <dcantrell(a)redhat.com>
Red Hat, Inc. | Boston, MA | EST5EDT
4 years, 4 months
annobin will be temporarily disabled in rawhide
by Florian Weimer
I'm disabling annobin temporarily so that the GCC 10 transition in the
buildroot will hopefully be a bit smoother than usual. Packages built
during the temporary change will hopefully be rebuilt during the mass
rebuild.
Thanks,
Florian
4 years, 4 months
Self Introduction: Javier Blanco
by Javier Blanco
Hi all,
My name is Javier and I am Spaniard. I have been using Linux for more than 15 years (10 at a professional level). I have worked mainly as a System Engineer and Database (Oracle/MySQL) Engineer for many years in a few IT companies in Spain and the US.
I am contributing fedora since 2017 when started with the package translation, but now is time for being more involved and I would like to continue packaging software.
Here is my LinkedIn profile if you are curious: https://www.linkedin.com/in/jblancom/
My nickname on Fedora project is "jblanco".
Public SSH key is in my FAS and PGP Key will be soon.
Have a good gone!!
4 years, 4 months
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-01-20.txt
grep it for your FAS username and follow the dependency chain.
Package (co)maintainers Status Change
===============================================================================
MochiKit orphan 5 weeks ago
exciting marcindulak, orphan 0 weeks ago
htmlcleaner besser82, marcindulak, orphan 0 weeks ago
jboss-transaction-1.2-api orphan 1 weeks ago
jettison mizdebsk, orphan 1 weeks ago
jetty-artifact-remote-resources mizdebsk, orphan 1 weeks ago
jetty-assembly-descriptors mizdebsk, orphan 1 weeks ago
jetty-test-policy mizdebsk, orphan 1 weeks ago
mcollective-qpid-plugin orphan, tdawson 5 weeks ago
ninvaders orphan 5 weeks ago
oyranos orphan 5 weeks ago
python-dockerpty lsm5, orphan, ttomecek 5 weeks ago
python-slacker orphan, python-sig, raphgro 1 weeks ago
python-virtkey orphan 5 weeks ago
qpid-proton orphan 4 weeks ago
rubygem-faker orphan 3 weeks ago
rubygem-omniauth orphan 5 weeks ago
shed orphan 5 weeks ago
slack-cleaner orphan 1 weeks ago
sound-theme-acoustic orphan 3 weeks ago
swingx orphan 2 weeks ago
tmuxinator orphan 5 weeks ago
tudu orphan 3 weeks ago
vttest cicku, orphan 5 weeks ago
The following packages require above mentioned packages:
Also available at:
https://churchyard.fedorapeople.org/orphans-2020-01-20.txt
Depending on: python-dockerpty (1), status change: 2019-12-10 (5 weeks ago)
docker-compose (maintained by: error, lsm5, ttomecek)
docker-compose-1.24.1-3.fc32.noarch requires python3-dockerpty =
0.4.1-17.fc32, python3.8dist(dockerpty) = 0.4.1
docker-compose-1.24.1-3.fc32.src requires python3-dockerpty = 0.4.1-17.fc32
Depending on: python-slacker (1), status change: 2020-01-10 (1 weeks ago)
slack-cleaner (maintained by: orphan)
python3-slack_cleaner-0.6.0-3.fc32.noarch requires python3-slacker =
0.13.0-3.fc32, python3.8dist(slacker) = 0.13
slack-cleaner-0.6.0-3.fc32.src requires python3-slacker = 0.13.0-3.fc32
Depending on: qpid-proton (24), status change: 2019-12-20 (4 weeks ago)
python-pyngus (maintained by: irina, kgiusti)
python-pyngus-2.3.0-4.fc32.src requires python3-qpid-proton = 0.29.0-1.fc32
python3-pyngus-2.3.0-4.fc32.noarch requires python3-qpid-proton =
0.29.0-1.fc32, python3.8dist(python-qpid-proton) = 0.29
gofer (maintained by: jortel)
python3-gofer-proton-3.0.0-0.5.fc32.noarch requires python3-qpid-proton =
0.29.0-1.fc32
koji (maintained by: ausil, bowlofeggs, kevin, mikem, puiterwijk)
python3-koji-hub-plugins-1.19.1-2.fc32.noarch requires python3-qpid-proton =
0.29.0-1.fc32
qpid-dispatch (maintained by: irina, tross)
qpid-dispatch-1.9.0-2.fc32.src requires python3-qpid-proton = 0.29.0-1.fc32,
qpid-proton-c-devel = 0.29.0-1.fc32
qpid-dispatch-router-1.9.0-2.fc32.x86_64 requires
libqpid-proton-core.so.10()(64bit), libqpid-proton-proactor.so.1()(64bit),
python3-qpid-proton = 0.29.0-1.fc32, qpid-proton-c(x86-64) = 0.29.0-1.fc32
qpid-dispatch-tools-1.9.0-2.fc32.noarch requires python3-qpid-proton =
0.29.0-1.fc32
rsyslog (maintained by: jlieskov, jvymazal, lkundrak, mdarade, mildew, rsroka,
tosykora)
rsyslog-8.1911.0-1.fc32.src requires qpid-proton-c-devel = 0.29.0-1.fc32
rsyslog-omamqp1-8.1911.0-1.fc32.x86_64 requires libqpid-proton.so.11()(64bit)
rubygem-qpid_proton (maintained by: irina)
rubygem-qpid_proton-0.29.0-1.fc32.src requires qpid-proton-c-devel = 0.29.0-1.fc32
rubygem-qpid_proton-0.29.0-1.fc32.x86_64 requires
libqpid-proton.so.11()(64bit), qpid-proton-c = 0.29.0-1.fc32
cmake-fedora (maintained by: fujiwara)
cmake-fedora-2.9.3-5.fc31.noarch requires fedora-packager = 0.6.0.2-6.fc31,
koji = 1.19.1-2.fc32
cmake-fedora-2.9.3-5.fc31.src requires koji = 1.19.1-2.fc32
fedora-packager (maintained by: kellin, mohanboddu)
fedora-packager-0.6.0.2-6.fc31.noarch requires koji = 1.19.1-2.fc32
fedpkg (maintained by: cqi, lsedlar, onosek)
fedpkg-1.37-10.fc32.noarch requires fedora-packager = 0.6.0.2-6.fc31, koji =
1.19.1-2.fc32
libabigail (maintained by: dodji, sinnykumari)
libabigail-fedora-1.6-2.fc31.x86_64 requires koji = 1.19.1-2.fc32
perl-Fedora-Rebuild (maintained by: jplesnik, ppisar)
perl-Fedora-Rebuild-0.12.1-18.fc31.noarch requires koji = 1.19.1-2.fc32
pungi (maintained by: dmach, lsedlar, maxamillion, tdawson, wwoods)
pungi-4.1.41-4.fc32.noarch requires koji = 1.19.1-2.fc32
atomic-reactor (maintained by: bkabrda, cverna, maxamillion, ttomecek, twaugh,
vrutkovs)
python3-atomic-reactor-koji-1.6.47-1.fc32.noarch requires koji = 1.19.1-2.fc32
bodhi (maintained by: bowlofeggs, infra-sig, jcline)
python3-bodhi-client-4.1.0-5.fc32.noarch requires /usr/bin/koji
python-robosignatory (maintained by: abompard, ralph)
python3-robosignatory-0.6.0-1.fc32.noarch requires koji = 1.19.1-2.fc32
rpmgrill (maintained by: halfie, romanofski, santiago)
rpmgrill-0.34-3.fc31.noarch requires koji = 1.19.1-2.fc32
ursa-major (maintained by: cqi, qwan)
ursa-major-0.3.1-4.fc32.noarch requires koji = 1.19.1-2.fc32
google-compute-engine-tools (maintained by: ngompa)
google-compute-engine-tools-2.8.12-5.fc32.noarch requires rsyslog =
8.1911.0-1.fc32
nbd-runner (maintained by: xiubli)
nbd-runner-0.5.3-1.fc32.x86_64 requires rsyslog = 8.1911.0-1.fc32
R2spec (maintained by: pingou)
R2spec-5.0.0-1.fc32.noarch requires fedora-packager = 0.6.0.2-6.fc31
fedora-review (maintained by: leamas, maxamillion, ngompa, pingou, sochotni)
fedora-review-0.7.4-1.fc32.noarch requires fedora-packager = 0.6.0.2-6.fc31
fontpackages (maintained by: frixxon, nim, tagoh)
fontpackages-tools-1.44-25.fc31.noarch requires fedora-packager = 0.6.0.2-6.fc31
oct2spec (maintained by: orion)
oct2spec-1.1-3.fc32.noarch requires fedora-packager = 0.6.0.2-6.fc31
tito (maintained by: dgoodwin, frostyx, maxamillion)
tito-0.6.12-2.fc32.noarch requires fedora-packager = 0.6.0.2-6.fc31
Too many dependencies for qpid-proton, not all listed here
Depending on: vttest (6), status change: 2019-12-10 (5 weeks ago)
varnish (maintained by: ingvar, luhliarik)
varnish-6.3.1-1.fc32.src requires vttest = 20190710-2.fc31
collectd (maintained by: fab, kevin, mhlavink, ruben, xaeth)
collectd-varnish-5.9.2-1.fc32.x86_64 requires libvarnishapi.so.2()(64bit),
libvarnishapi.so.2(LIBVARNISHAPI_2.0)(64bit)
varnish-modules (maintained by: dridi, ingvar, luhliarik)
varnish-modules-0.15.0-7.fc32.src requires varnish = 6.3.1-1.fc32
varnish-modules-0.15.0-7.fc32.x86_64 requires libvarnishapi.so.2()(64bit),
libvarnishapi.so.2(LIBVARNISHAPI_2.0)(64bit), varnish = 6.3.1-1.fc32
vmod-querystring (maintained by: dridi)
vmod-querystring-2.0.1-2.fc31.src requires varnish = 6.3.1-1.fc32
vmod-querystring-2.0.1-2.fc31.x86_64 requires varnish = 6.3.1-1.fc32
vmod-uuid (maintained by: ingvar)
vmod-uuid-1.6-5.fc32.src requires varnish = 6.3.1-1.fc32
vmod-uuid-1.6-5.fc32.x86_64 requires libvarnishapi.so.2()(64bit),
libvarnishapi.so.2(LIBVARNISHAPI_2.0)(64bit), varnish(x86-64) = 6.3.1-1.fc32
python-bucky (maintained by: jsteffan)
python3-bucky-2.3.0-8.fc32.noarch requires collectd = 5.9.2-1.fc32
Affected (co)maintainers
abompard: qpid-proton
ausil: qpid-proton
besser82: htmlcleaner
bkabrda: qpid-proton
bowlofeggs: qpid-proton
cicku: vttest
cqi: qpid-proton
cverna: qpid-proton
dgoodwin: qpid-proton
dmach: qpid-proton
dodji: qpid-proton
dridi: vttest
error: python-dockerpty
fab: vttest
frixxon: qpid-proton
frostyx: qpid-proton
fujiwara: qpid-proton
halfie: qpid-proton
infra-sig: qpid-proton
ingvar: vttest
irina: qpid-proton
jcline: qpid-proton
jlieskov: qpid-proton
jortel: qpid-proton
jplesnik: qpid-proton
jsteffan: vttest
jvymazal: qpid-proton
kellin: qpid-proton
kevin: qpid-proton, vttest
kgiusti: qpid-proton
leamas: qpid-proton
lkundrak: qpid-proton
lsedlar: qpid-proton
lsm5: python-dockerpty
luhliarik: vttest
marcindulak: htmlcleaner, exciting
maxamillion: qpid-proton
mdarade: qpid-proton
mhlavink: vttest
mikem: qpid-proton
mildew: qpid-proton
mizdebsk: jettison, jetty-assembly-descriptors, jetty-test-policy,
jetty-artifact-remote-resources
mohanboddu: qpid-proton
ngompa: qpid-proton
nim: qpid-proton
onosek: qpid-proton
orion: qpid-proton
pingou: qpid-proton
ppisar: qpid-proton
puiterwijk: qpid-proton
python-sig: python-slacker
qwan: qpid-proton
ralph: qpid-proton
raphgro: python-slacker
romanofski: qpid-proton
rsroka: qpid-proton
ruben: vttest
santiago: qpid-proton
sinnykumari: qpid-proton
sochotni: qpid-proton
tagoh: qpid-proton
tdawson: qpid-proton, mcollective-qpid-plugin
tosykora: qpid-proton
tross: qpid-proton
ttomecek: python-dockerpty, qpid-proton
twaugh: qpid-proton
vrutkovs: qpid-proton
wwoods: qpid-proton
xaeth: vttest
xiubli: qpid-proton
--
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
4 years, 4 months
List of long term FTBFS packages to be retired in February
by Miro Hrončok
Dear maintainers.
Based on the latest fail to build from source policy, the following packages
will be retired from Fedora 32 approximately one week before branching (February
2020).
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 30.
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 Latest build
================================================================================
elasticsearch hubbitus, jvanek, lbazan, Fedora 24
zbyszek
expresso jamielinux, nodejs-sig, Fedora 28
patches
libocrdma ocrdma Fedora 27
nuvola-app-google-calendar martinkg Fedora 29
nuvola-app-groove martinkg Fedora 28
nuvola-app-logitech-media- martinkg Fedora 29
server
nuvola-app-plex martinkg Fedora 29
nuvola-app-soundcloud martinkg Fedora 29
nuvola-app-yandex-music martinkg Fedora 29
shim-unsigned-aarch64 pjones Fedora 28
shim-unsigned-x64 pjones Fedora 28
The following packages require above mentioned packages:
Depending on: expresso (1)
nodejs-chrono (maintained by: jamielinux, nodejs-sig, tomh)
nodejs-chrono-1.0.5-10.fc31.src requires npm(expresso) = 0.9.2
Affected (co)maintainers
hubbitus: elasticsearch
jamielinux: expresso
jvanek: elasticsearch
lbazan: elasticsearch
martinkg: nuvola-app-soundcloud, nuvola-app-logitech-media-server,
nuvola-app-yandex-music, nuvola-app-groove, nuvola-app-google-calendar,
nuvola-app-plex
nodejs-sig: expresso
ocrdma: libocrdma
patches: expresso
pjones: shim-unsigned-aarch64, shim-unsigned-x64
tomh: expresso
zbyszek: elasticsearch
--
Miro Hrončok
--
Phone: +420777974800
IRC: mhroncok
4 years, 4 months
