there is some interest (the interested people are BCC'ed) in packaging
The packaging request is tracked here: Bug 915043 - Package rust (lang)
There are two main parts to get the packaging done:
(a) Get rust to use our pre-build llvm
(b) Package the smaller dependencies
For (a) it is looking better than a year ago, according to my knowledge
all important patches are upstreamed into LLVM.
So the task is mainly to find the right compile switches and possibly some
patches to the build system to get Rust to build with our pre-build LLVM.
For (b) we have at least three submodules which should be packaged:
path = src/compiler-rt
url = https://github.com/rust-lang/compiler-rt.git
Not packaged yet
path = src/rt/hoedown
url = https://github.com/rust-lang/hoedown.git
Not packaged yet
path = src/jemalloc
url = https://github.com/rust-lang/jemalloc.git
The unpackaged modules need to get packaged, and for the packaged ones
the Rust build system needs updates to pickup the pre-build ones.
Due to time constraints I can currently not help with packaging, but I
can help review stuff as soon as there is something.
But there is so much interest in packaging Rust that there are maybe some
volunteers to drive the little tasks.
Fedora 22 Beta Release Announcement
The Fedora 22 Beta release for aarch64 and POWER secondary architecutres
has arrived, with a preview of the latest free and open source technology
under development. Take a peek inside!
What is the Beta release?
The Beta release contains all the exciting features of Fedora 22's
editions in a form that anyone can help test. This testing, guided by
the [Fedora QA team](https://fedoraproject.org/wiki/QA), helps us
target and identify bugs. When these bugs are fixed, we make a Beta
release available. A Beta release is meant to be feature complete and
bears a very strong resemblance to the third and final release.
The final release of Fedora 22 is expected in May.
We need your help to make Fedora 22 the best release yet, so please take
some time to download and try out the Beta and make sure the things that
are important to you are working. If you find a bug, please report
it – every bug you uncover (and/or help fix!) is a chance to improve
the experience for millions of Fedora users worldwide.
Together, we can make Fedora rock-solid. We have a culture of
coordinating new features and pushing fixes upstream as much as
feasible, and your feedback will help improve not only Fedora but Linux
and free software on the whole.
### Base platform
- Faster and better dependency management: yum has been replaced with
dnf as the default package manager. dnf has very similar command
line options and configuration files compared to yum but also has
several major internal changes including using libsolv in
coordination with friends from the openSUSE project for faster and
better dependency management. dnf-yum provides automatic redirection
from yum to dnf in the command line for compatibility. The classic
yum command line tool renamed to yum-deprecated as a transitional
step for tools still using it.
### Fedora 22 Server
Fedora 22 Server Edition brings several changes that will improve Fedora
for use as a server in your environment.
- Database Server Role: Fedora 21 introduced rolekit, a daemon for
Linux systems that provides a stable D-Bus interface to manage
deployment of server roles. The Fedora 22 release adds onto that
work with a database server role based on PostgreSQL.
- Cockpit Updates: The Cockpit Web-based management application has
been updated to the latest upstream release which adds many new
features as well as a modular design for adding new functionality.
- XFS as default filesystem. XFS scales better for servers and can
handle higher storage capacity and we have made it the default
filesystem for Fedora 22 server users. Other filesystems including
ext4 will continue to be supported and the ability to choose them
have been retained.
Issues and Details
This is an Beta release. As such, we expect that you may encounter bugs
or missing features. To report issues encountered during testing,
contact the Fedora QA team via the mailing list or in \#fedora-qa on
As testing progresses, common issues are tracked on the Common F22
The full release schedule is available on the Fedora wiki. The current
schedule calls for a final release in the end of May.
These dates are subject to change, pending any major bugs or issues
found during the testing process.
devel-announce mailing list
Following is the list of topics that will be discussed in the FPC
meeting Thursday at 2015-04-30 16:00 UTC in #fedora-meeting-1 on
Local time information (via. rktime):
2015-04-30 09:00 Thu US/Pacific PDT
2015-04-30 12:00 Thu US/Eastern EDT
2015-04-30 16:00 Thu UTC <-
2015-04-30 17:00 Thu Europe/London BST
2015-04-30 18:00 Thu Europe/Paris CEST
2015-04-30 18:00 Thu Europe/Berlin CEST
2015-04-30 21:30 Thu Asia/Calcutta IST
2015-05-01 00:00 Fri Asia/Singapore SGT
2015-05-01 00:00 Fri Asia/Hong_Kong HKT
2015-05-01 01:00 Fri Asia/Tokyo JST
2015-05-01 02:00 Fri Australia/Brisbane EST
Links to all tickets below can be found at:
= Followups =
#topic #281 New Python Macros for Easier Packaging
#topic #480 Packaging guidelines for consistent PKCS#11 usage
#topic #508 New GID for openstack-neutron
#topic #513 Use python -Es in shbang
#topic #524 static UID for ceph
= Open Floor =
For more complete details, please visit each individual ticket. The
report of the agenda items can be found at:
If you would like to add something to this agenda, you can reply to
this e-mail, file a new ticket at https://fedorahosted.org/fpc,
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.
I'm trying to give one of my packages (openldap) to another developer,
but the online tool keeps saying that "User is not in the packager
group", which I believe is not true, because he is in the same Fedora
groups as I am. Where can I report this?
Software Engineer, Red Hat