Lots of FailsToInstall on rawhide bugs
by Orion Poplawski
Folks -
I'm afraid the new FailsToInstall bugs may be a bit much for me.
Often it seems:
- There is already a FTBFS bug against the package which is the root
cause of the FTI.
- There was a soname bump in rawide and the builds didn't manage to
complete before the next rawhide compose. I know, people probably
should be using side tags, but it's the maintainers of the dependent
packages that are being harassed. And can't we even have a bit more
than a day to address these.
For released branches, sure go for it (although I would still argue
about checking for a FTBFS bug first). But can we back off a little bit
on rawhide?
- Orion
--
Orion Poplawski
Manager of NWRA Technical Systems 720-772-5637
NWRA, Boulder/CoRA Office FAX: 303-415-9702
3380 Mitchell Lane orion(a)nwra.com
Boulder, CO 80301 https://www.nwra.com/
4 years
Self-Introduction of Tanveer Salim and Notice on Implementation of
KangarooTwelve
by tsalim＠tutanota.com
Dear Fedora Community,
Hello! I am Tanveer Salim and am a Computer Engineering Student from Texas Tech University. I am currently writing a standard user-space implementation of KangarooTwelve. I contacted Gilles van Assche and he said he was interested in viewing my implementation after I finished the rough draft. I have let him know I intend to finish the first rough draft by June 1, 2020. And I do intend to submit the implementation of KangarooTwelve as a Fedora package. If anyone has any questions or comments about my attempt to implement KangarooTwelve please let me know.
Sincerely,
Tanveer Salim
4 years
Fwd: Re: late generation of assemble code
by Paul Dufresne
had forgotten to reply also to the list... doing it now:
[cut the part where it was suggested to make package that contains LLVM
Intermediate Representation bitcode rather than CPU specific assembler]
On 2020-05-29 1:01 a.m., John M. Harris Jr wrote:
> Paul,
> What benefit do you see in the overhead of LLVM IR, compared to standard
> packages?
John,
Where do you see overhead in the distribution of LLVM IR?
Advantages:
* more space on the hard disks of the servers, because they contains
repositories only for LLVM IR packages rather than one by supported
architectures
* less use of the CPU time of the servers because they don't optimize
code for specific CPUs
* very reduced cost for supporting more architectures, as code is
client-side generated
* faster code on clients with recent CPUs, because code is optimized for
them, and was not in the old way of doing because you had to distribute
for a common base CPU
* CPU specific code generation and optimizations can be done on idle
time of the clients... there is not much idle time of the servers
4 years
Schedule for Mondays's FESCo Meeting (2020-06-01)
by Zbigniew Jędrzejewski-Szmek
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-06-01 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 =
#2393 Nonresponsive maintainer: Martin Preisler mpreisle
https://pagure.io/fesco/issue/2393
ACCEPTED (+4, 0, 0)
#2392 Nonresponsive maintainer: Marek Mahut mmahut
https://pagure.io/fesco/issue/2392
ACCEPTED (+4, 0, 0)
#2389 Nonresponsive maintainer: Avesh Agarwal (avesh)
https://pagure.io/fesco/issue/2389
ACCEPTED (+4, 0, 0)
= Followups =
#2114 What is the scope of Modularity?
https://pagure.io/fesco/issue/2114
= New business =
= 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.
4 years
looking for scipy on python 3.8 (RISCV Fedora Release 32)
by Arun Sukumaran Latha
Hello All,
I was working on getting tensorflow compiled within the *RISCV *Fedora
environment.
I am using the latest release 32 build.
Currently I am unable to install the dependent library, scipy due to the
same not being available for python 3.8.1 which is currently installed.
*[riscv@fedora-riscv ~]$ sudo dnf install python3-scipyLast metadata
expiration check: 0:22:10 ago on Sat 16 May 2020 12:02:37 PM
EDT.Error: Problem: conflicting requests - nothing provides
libpython3.7m.so.1.0()(64bit) needed by
python3-scipy-1.1.0-3.0.riscv64.fc29.riscv64 - nothing provides
python(abi) = 3.7 needed by
python3-scipy-1.1.0-3.0.riscv64.fc29.riscv64(try to add '--skip-broken' to
skip uninstallable packages)*
*[riscv@fedora-riscv ~]$ cat /etc/redhat-releaseFedora release 32
(Rawhide)[riscv@fedora-riscv ~]$ python3 --versionPython 3.8.1*
Can you please let me know if we can have the same soon?
Regards,
Arun SL
4 years
unretiring llvm7.0
by Jens-Ulrik Petersen
In March llvm7.0 which had been orphaned for some reason, got retired.
Unfortunately I missed the warning mails that Miro sent here.
llvm7.0 is needed for aarch64 ghc:8.8,
and for ghc-8.8.3 planned for F33.
So I would like to unretire llvm7.0.
Thanks, Jens
4 years
CPE Weekly: 2020-05-31
by Aoife Moloney
---
title: CPE Weekly status email
tags: CPE Weekly, email
---
# CPE Weekly: 2020-05-31
Background:
The Community Platform Engineering group is the Red Hat team combining
IT and release engineering from Fedora and CentOS. Our goal is to keep
core servers and services running and maintained, build releases, and
other strategic tasks that need more dedicated time than volunteers
can give.
See our wiki page here for more
information:https://docs.fedoraproject.org/en-US/cpe/
## General Project Updates
Please check out our updated initiative timetable for briefing in new
projects to our team
here:https://docs.fedoraproject.org/en-US/cpe/time_tables/
*Note: Initiatives are large pieces of work that require a team of
people and weeks/months to complete. Please continue to open tickets
in the normal way for bugs, issues, etc.
Don't forget to view our taiga board to see the projects we are
currently working on, what we have scoped and whats in our backlog
https://tree.taiga.io/project/amoloney1-cpe-team-projects/kanban?epic=null
I also currently have weekly IRC office hours on #fedora-meeting-1 @
1300 - 1400 UTC and I will have a bi-weekly office hours on
Centos-meeting @ 1500 - 1600 UTC beginning June 9th also, with Rich
Bowen helping me set it up, thanks Rich :)
There is (usually) no agenda for these meetings and is an open floor,
so please feel free to stop by and chat casually, or about any
projects the CPE team are working on/working on next. The choice of
topic is completely yours :)
### Gitforge
Just a quick note to say this project has not made any more notable
progress. Our team have some very time-intensive projects currently in
flight, so our focus has been and will be on the completion of these
projects over the next few months. We are still using the gitlab
project tracker https://gitlab.com/gitlab-org/gitlab/-/issues/217350
to record issues/technical requirements, and thank you again for your
patience during this slower period of the project, it is very much
appreciated.
## Fedora Updates
### Data Centre Move
* A reduced services offering of Fedora will be in effect from June
8th until July 28th, est.
* This is to complete the final shipment of hardware from Phoenix to
Washington, so please be patient and understanding during this
timeframe as some services will be off and the rest, much slower.
* Kevin Fenzi has sent some details on service validation and a call
to arms to help us meet the June 15th deadline to have the reduced
Fedora operational, please read:
https://lists.fedoraproject.org/archives/list/infrastructure@lists.fedora...
* Details on what this move may mean for you can be found here
https://lists.fedoraproject.org/archives/list/devel-announce@lists.fedora...
### AAA Replacement
* Adding the ability to sign user agreements
* Adding the blog/website attribute for users
* Client library migration to python-freeipa 1.0.0.
### Mbbox
* Project Dashboard here https://github.com/fedora-infra/mbbox/projects/1
* Sprint 3 is done:
* Refactor molecule test suit to share test-cases
* Koji-hub and koji-builder SSL issues solved
* Sprint 4 is in progress
* Kojira CRD
* MBS Backend CRD (MBS doesn’t support fedora messaging)
* Staging environment
## CentOS Updates
### CentOS
* Post OCP4 cluster Installation tasks - storage, TLS cert/ IDP
configs, exploring operators that we can use.
* We have a public accessible ocp4 cluster
(https://console-openshift-console.apps.ocp.ci.centos.org/). We are on
the verge of figuring out subscriptions.
* Documentation: https://centosci.github.io/ocp4-docs/
* Linux 8.2 work is still with QA
### CentOS Stream
* The team are working on adding some 8.2 builds to Stream that failed
or did not make it into Stream for whatever reason.
As always, feedback is welcome, and we will continue to look at ways
to improve the delivery and readability of this weekly report.
Have a great weekend!
Aoife
Source: https://hackmd.io/8iV7PilARSG68Tqv8CzKOQ?view
--
Aoife Moloney
Product Owner
Community Platform Engineering Team
Red Hat EMEA
Communications House
Cork Road
Waterford
4 years
How to debug live CD image?
by Barry Scott
My desktop PC is happily running Fedora for years.
Its on Fedora 32 now. It also has Windows 10 dual
boot via Grub.
But I cannot boot a live CD image as it gets stuck
in "Monitoring of LVM2 mirrors, ...". This is not a
new problem I have seen this for a couple of Fedora
releases, but not reported it before.
I have tested with both the Workstation image and
the KDE spin image. Both get stuck at the same place.
How do I go about debugging what is going on?
Barry
4 years
PSA: pytest 5 now finally available in rawhide
by Miro Hrončok
Hello,
the pytest package (python3-pytest) has been updated to 5.4.2.
In case it gives you trouble, you can pin an older version:
BuildRrequires: %{py3_dist pytest} < 5
Or:
BuildRrequires: python3dist(pytest) < 5
That will give you the python3-pytest4 package (4.6.10 now), not parallely
installable with python3-pytest.
Note that the python3-pytest4 package is deprecated, but no removal date has
been set. Likely, it will get orphaned or retired when no important packages
need it.
The pytest 4.6.x series is still being occasionally released, but:
https://docs.pytest.org/en/latest/py27-py34-deprecation.html#maintenance-...
"From now on, the core team will no longer actively backport patches, but the
4.6.x branch will continue to exist so the community itself can contribute patches."
Side note: The Fedora 31/32 python3-pytest package does not provide
python3-pytest4, hence I recommend not to BuildRequire python3-pytest4 directly
by name, but using python3dist(pytest) or %py3_dist as in the examples above.
--
Miro Hrončok
--
Phone: +420777974800
IRC: mhroncok
4 years
