Call for help contacting contributors
by Pierre-Yves Chibon
Dear all,
Packagers, members of the fedorabugs group and people having a 'watchbugzilla'
ACL in pkgdb must have a bugzilla account attached to the email they set in the
Fedora Account System (FAS).
This is mandatory to allow ACLs to be propagated from pkgdb to bugzilla, allowing
the right person to be made assignee or to be cc'ed on bug reports of packages.
There are currently a few users who are not following this rule and have not
been for quite a while, despite our attempts to contact them:
* jackprice, FAS email: jackprice -- outlook.com
watches 1 package
* vjancik, FAS email: viktor.vix.jancik -- gmail.com
co-maintains¹ 68 packages
watches 1 package
* mstuchli, FAS email: matej.stuchlik -- gmail.com
POC of 14 packages
co-maintains 18 packages
* ferbncode, FAS email: suyashgargsfam -- gmail.com
watches 2 packages
* jangernert, FAS email: janlukasgernert -- freenet.de
watches 1 package
If anyone knows how to reach to them and could either send them to us, the
Fedora infrastructure team, or directly ask them to create a bugzilla account
associated to the email they set in FAS, it would be highly appreciated.
If nothing changes in the coming days, we will drop their ACLs in pkgdb.
Thanks for your help and understanding,
Pierre
for the Fedora Infrastructure team
¹ This number includes packages on which the user may have `watch*` ACLs
8 years, 1 month
Fedora 24 Alpha for POWER
by Peter Robinson
The Fedora 24 Alpha for POWER is here, right on schedule for our planned June
final release. Download the prerelease from our Get Fedora site:
- Get Fedora 24 Alpha Workstation https://getfedora.org/en/workstation/
prerelease/
- Get Fedora 24 Alpha Server https://getfedora.org/en/server/prerelease/
- Get Fedora 24 Alpha Cloud https://getfedora.org/en/cloud/prerelease/
- Get Fedora 24 Alpha Spins https://spins.fedoraproject.org/prerelease
- Get Fedora 24 Alpha Labs https://labs.fedoraproject.org/prerelease
- Get Fedora 24 Alpha ARM https://arm.fedoraproject.org/prerelease
What is the Alpha release?
--------------------------
The Alpha release contains all the features of Fedora 24's editions in
a form that anyone can help test. This testing, guided by the Fedora
QA team, helps us target and identify bugs. When these bugs are fixed,
we make a Beta release available. A Beta release is code-complete and
bears a very strong resemblance to the third and final release. The
final release of Fedora 24 is expected in June.
If you take the time to download and try out the Alpha, you can check
and make sure the things that are important to YOU are working. Every
bug you find and report doesn't just help you, it improves the
experience of 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 we
can, and your feedback improves not only Fedora, but Linux and Free
software as a whole.
* https://fedoraproject.org/wiki/Releases/24/Schedule
* https://fedoraproject.org/wiki/How_to_file_a_bug_report
Fedora-Wide Changes
-------------------
Under the hood, glibc has moved to 2.23. The update includes better
performance, many bugfixes and improvements to POSIX compliance, and
additional locales. The new library is backwards compatible with the
version of glibc that was shipped in Fedora 23, and includes a number
of security and bug fixes.
We've also updated the system compiler to GCC 6 and rebuilt all
packages with that, providing greater code optimization and catching
programming errors which had slipped past previous compilers.
In ppc64/ppc64le golang 1.6 brings all the same golang functionality that
other architectures have enjoyed enabling all the features and apps
that are avaialble there such as docker.
Server
------
- FreeIPA 4.3 (Domain Controller role) is included in Fedora 24. This
version helps streamline installation of replicas by adding a
replica promotion method for new installs. A new topology plugin has
also been added that automatically manages new replication segment
creation. An effective replica topology visualization tool is also
available in the webUI.
- NodeJS 4 in now available for aarch64. Earlier versions of nodejs have
been available on primary architectures for some time. With nodejs4 we
now bring all the functionality to aarch64 too.
- More packages have been removed from the default Server edition to
make the footprint of the default installation smaller.
Cloud
-----
- For Fedora 24, we're working hard to make Fedora the best platform
for developing containers, from the base Fedora container images to
a full-featured PaaS to run and manage them.
- For both ppc64 and ppc64le we have qemu cloud images and add to it
docker base images to the release as well.
Issues and Details
------------------
This is an Alpha 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
Freenode.
As testing progresses, common issues are tracked on the Common F24 Bugs
page.
* https://fedoraproject.org/wiki/Common_F24_bugs
For tips on reporting a bug effectively, read "how to file a bug
report."
* https://fedoraproject.org/wiki/How_to_file_a_bug_report
Release Schedule
----------------
The full release schedule is available on the Fedora wiki:
* https://fedoraproject.org/wiki/Releases/24/Schedule
The current schedule calls for a beta release towards the beginning of May,
and
the final release in early June.
Be aware that these dates are development targets. Some projects release
on a set date regardless of feature completeness or bugs; others wait
until certain thresholds for functionality or testing are met. Fedora
uses a hybrid model, with milestones subject to adjustment. This allows
us to make releases with new features and newly-integrated and updated
upstream software while also retaining high quality.
_______________________________________________
devel-announce mailing list
devel-announce(a)lists.fedoraproject.org
http://lists.fedoraproject.org/admin/lists/devel-announce@lists.fedorapro...
8 years, 1 month
Fedora 24 Alpha for aarch64
by Peter Robinson
The Fedora 24 Alpha for aarch64 is here, right on schedule for our planned June
final release. Download the prerelease from our Get Fedora site:
- Get Fedora 24 Alpha Server
https://dl.fedoraproject.org/pub/fedora-secondary/releases/test/24_Alpha/...
https://fedoraproject.org/wiki/Architectures/AArch64/F24/Installation
What is the Alpha release?
--------------------------
The Alpha release contains all the features of Fedora 24's editions in
a form that anyone can help test. This testing, guided by the Fedora
QA team, helps us target and identify bugs. When these bugs are fixed,
we make a Beta release available. A Beta release is code-complete and
bears a very strong resemblance to the third and final release. The
final release of Fedora 24 is expected in June.
If you take the time to download and try out the Alpha, you can check
and make sure the things that are important to YOU are working. Every
bug you find and report doesn't just help you, it improves the
experience of 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 we
can, and your feedback improves not only Fedora, but Linux and Free
software as a whole.
* https://fedoraproject.org/wiki/Releases/24/Schedule
* https://fedoraproject.org/wiki/How_to_file_a_bug_report
Fedora-Wide Changes
-------------------
Under the hood, glibc has moved to 2.23. The update includes better
performance, many bugfixes and improvements to POSIX compliance, and
additional locales. The new library is backwards compatible with the
version of glibc that was shipped in Fedora 23, and includes a number
of security and bug fixes.
We've also updated the system compiler to GCC 6 and rebuilt all
packages with that, providing greater code optimization and catching
programming errors which had slipped past previous compilers.
In aarch64 golang 1.6 brings all the same golang functionality that
other architectures have enjoyed enabling all the features and apps
that are avaialble there such as docker.
Server
------
- FreeIPA 4.3 (Domain Controller role) is included in Fedora 24. This
version helps streamline installation of replicas by adding a
replica promotion method for new installs. A new topology plugin has
also been added that automatically manages new replication segment
creation. An effective replica topology visualization tool is also
available in the webUI.
- NodeJS 4 in now available for aarch64. Earlier versions of nodejs have
been available on primary architectures for some time. With nodejs4 we
now bring all the functionality to aarch64 too.
- More packages have been removed from the default Server edition to
make the footprint of the default installation smaller.
Cloud and Docker
----------------
Not quite ready for Alpha both qemu cloud images and docker images will
be appearing for nightly Fedora 24 aarch64 composes starting next week.
All the docker pieces are already in place in Fedora 24 Alpha. The last
pieces of the infrastructure to build the nightly docker images are
almost live into production. There will be appropriate announcements
when they go live.
Issues and Details
------------------
This is an Alpha 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
Freenode.
As testing progresses, common issues are tracked on the Common F24 Bugs
page.
* https://fedoraproject.org/wiki/Common_F24_bugs
For tips on reporting a bug effectively, read "how to file a bug
report."
* https://fedoraproject.org/wiki/How_to_file_a_bug_report
Release Schedule
----------------
The full release schedule is available on the Fedora wiki:
* https://fedoraproject.org/wiki/Releases/24/Schedule
The current schedule calls for a beta release towards the beginning of May,
and
the final release in early June.
Be aware that these dates are development targets. Some projects release
on a set date regardless of feature completeness or bugs; others wait
until certain thresholds for functionality or testing are met. Fedora
uses a hybrid model, with milestones subject to adjustment. This allows
us to make releases with new features and newly-integrated and updated
upstream software while also retaining high quality.
_______________________________________________
devel-announce mailing list
devel-announce(a)lists.fedoraproject.org
http://lists.fedoraproject.org/admin/lists/devel-announce@lists.fedorapro...
8 years, 1 month
Packages installing files to /etc/tmpfiles.d
by Ville Skyttä
The following packages in current rawhide install files to
/etc/tmpfiles.d. They should most likely be fixed to install those
files to /usr/lib/tmpfiles.d instead.
$ dnf -q repoquery --disablerepo=* --enablerepo=rawhide --qf=%{NAME}
"/etc/tmpfiles.d/*" | sort -u
389-dsgw
amplab-tachyon
anyterm
BackupPC
bip
Canna
condor
cyphesis
dspam
ebnetd-common
exim-clamav
fail2ban-server
firebird
freeradius
iguanaIR
lighttpd
logcheck
mesos
mirrormanager
monotone-server
nss-pam-ldapd
nut-client
opendkim
opendmarc
opendnssec
openpgpkey-milter
pam_ssh
polipo
puppet
shinken
slim
smokeping
smstools
sslogger-slogd
supervisor
trafficserver
vpnc
zoneminder
8 years, 1 month
[Modularity] Meeting summary
by White, Langdon
Please see below for the log/minutes of the first Modularity WG meeting.
Please note, not terribly awesome at zodbot, so, forgot to #info or
whatever that we would table the "what to do and by when" discussion
until after the "how to do stuff" discussion. We ran out of time, so
that will be on the agenda for next meeting.
Meeting summary
---------------
* roll call (langdon, 15:03:56)
* context setting (langdon, 15:07:12)
* LINK: https://fedoraproject.org/wiki/Modularization (langdon,
15:08:12)
* modularization wiki page (langdon, 15:08:19)
* LINK: https://fedoraproject.org/wiki/Modularity_Working_Group
(langdon, 15:08:38)
* modularity working group wiki page (langdon, 15:08:50)
* number of voting members (langdon, 15:12:47)
* number of voting members & term of service (langdon, 15:13:42)
* LINK: https://fedoraproject.org/wiki/Server/Governance_Charter
(sgallagh, 15:17:23)
* ACTION: langdon to modify wiki page to show proposed governance and
then send to mailing list for approval (langdon, 15:29:55)
* when should the meetings be (langdon, 15:30:36)
* AGREED: meeting time is weekly on thursdays at 15h UTC (langdon,
15:34:54)
* ACTION: langdon to update fedocal "correctly" (langdon, 15:35:11)
* what to deliver & when (langdon, 15:35:37)
* how to do stuff (langdon, 15:38:18)
* LINK: http://taiga.fedorainfracloud.org/project/langdon-modularity/
Modularity taiga board (sctw, 15:47:21)
* LINK: http://taiga.fedorainfracloud.org/ (langdon, 15:47:36)
* taiga deployment seems to work much better for you to go 1) login
once using fas; 2) ask someone to add you to modify the board/take
cards .. but pre-invite does not seem to work well (langdon,
15:56:07)
* AGREED: agile-y approach, using taiga, potentially modifiable by the
WG voting members (langdon, 15:58:03)
* ACTION: wg needs to write up the details of the approach (langdon,
15:58:21)
* ACTION: wg needs to solve how to demo (langdon, 15:58:44)
* to join the taiga project and take cards: 1) login in to taiga using
fas; 2) send email to langdon(a)fp.o with your *target* email address
for your me(a)fp.o acccount (langdon, 16:03:03)
* we have #fedora-modularization for discussion.. so please join us
there any time (langdon, 16:05:25)
Meeting ended at 16:07:28 UTC.
Action Items
------------
* langdon to modify wiki page to show proposed governance and then send
to mailing list for approval
* langdon to update fedocal "correctly"
* wg needs to write up the details of the approach
* wg needs to solve how to demo
Langdon
Modularity Objective Lead
8 years, 1 month
Checking signatures on package source tarballs
by David Woodhouse
Michael, you make a very good point at
https://blogs.gnome.org/mcatanzaro/2016/03/13/do-you-trust-this-package/
Our packaging guidelines really ought to mandate that *if* upstream
publishes GPG or PKCS#7/CMS signatures of source tarballs, then the
package *must* verify those signatures as part of %prep.
Do you want to put a draft together for approval by the packaging
committee?
It might be nice to provide some RPM macros to make that easier for
packagers.
I've had a go at doing this for OpenConnect, in
http://pkgs.fedoraproject.org/cgit/rpms/openconnect.git/commit/?id=ca61de...
It's a bit pointless there, since the tarballs tend to get uploaded to
Fedora from the same workstation I sign them on, sometimes *before*
they're uploaded to the FTP site. But it's still good practice, as you
rightly point out.
--
David Woodhouse Open Source Technology Centre
David.Woodhouse(a)intel.com Intel Corporation
8 years, 1 month
