F21 System Wide Change: Fedora 21 Make 4.0 Update
by Jaroslav Reznik
= Proposed System Wide Change: Fedora 21 Make 4.0 Update =
https://fedoraproject.org/wiki/Changes/F21Make40
Change owner(s): Patsy Franklin <pfrankli(a)redhat.com>
This change brings Make 4.0 to Fedora 21.
== Detailed Description ==
The purpose of this update is to synchronize Fedora with the most recent Make
release.
Several new features, new command line options, new variables, and bug fixes
have been implemented in Make 4.0.
Improved error reporting may result in log file differences. If a recipe
fails, the makefile name and linenumber of the recipe are shown.
There is one backwards-incompatibility regarding the use of .POSIX. Make 4.0
will adhere to POSIX requirements for backshlash/newline handling. See the
link included under Documentation for more details.
A new subpackage make-devel will be created containing gnumake.h,a new file
containing externally-visible content.
== Scope ==
* Proposal owners:
** Rebase to make-4.0
** 6 patches need to be updated to work with new sources
** 14 patches will be removed as they are already supported by the make-4.0
rebase
** make.spec will be updated
** local build and test (already completed for glibc and gcc)
** patch created and submitted
** build
* Other developers: There are some minor error message changes that may show
up as log file differences.
If a package's makefile requires a specific version of make, the makefiles may
need editing to include make 4.0.
* Release engineering: There will be a new subpackage make-devel.
* Policies and guidelines: N/A
9 years, 11 months
F21 System Wide Change: SCL
by Jaroslav Reznik
= Proposed System Wide Change: SCL =
https://fedoraproject.org/wiki/Changes/SCL
Change owner(s): Marcela Mašláňová <mmaslano(a)redhat.com>
SCL - Software Collections - are popular packaging format above rpm. Let's
enable them for Fedora. More details on upstream page [1].
== Detailed Description ==
My first draft [2] is obsoleted by current state of SCL, Copr... I would keep
the SCL workflow simple as possible.
Playground repo
1. Build SCL in Copr
2. Add SCL into Playground repo
Fedora main repo
0. Build SCL in Copr (or use existing SCL)
1. Do standard package review
2. Upload packages into git - specific branch based on Fedora version and name
of collection. For stable repo we must be able to replicate builds from git
repo, which Fedora own.
3. Build SCL in koji or magically add SCL builds from Copr (depends on
preference of releng)
SCL living on Copr can be good candidates for inclusion in Fedora. Maintainer
of such SCL must be able create Change proposal for his collection. Review of
packages in the collection should depend on repository (Playground - almost no
rules, Fedora - standard guidelines).
== Scope ==
* Proposal owners:
0. Approve SCL guidelines by FPC
1. Include one collection into Fedora Playground repository or into main
Fedora repository (probably the one wanted by Cloud WG). It might be this one
rebuild for Fedora [3]. Updates of some gems or addition of other gems might
be needed. Review by Cloud projects is needed.
* Other developers: If SCL is in Fedora, maybe some other project can use it
for their work.
* Release engineering: Magically add SCLs builds into compose or set up koji
for SCLs.
* Policies and guidelines:
https://fedorahosted.org/fpc/ticket/339
https://fedoraproject.org/wiki/User:Toshio/SCL_Guidelines_%28draft%29
[1] https://www.softwarecollections.org/en/
[2] https://fedoraproject.org/wiki/User:Mmaslano/SCLinFedora
[3] http://copr.fedoraproject.org/coprs/rhscl/ruby193/
9 years, 11 months
F21 System Wide Change: The securetty file is empty by default
by Jaroslav Reznik
= Proposed System Wide Change: The securetty file is empty by default =
https://fedoraproject.org/wiki/Changes/securetty_file_is_empty_by_default
Change owner(s): quickbooks <quickbooks.office(a)gmail.com>
The securetty file is empty by default
There's on-going discussion for this Change on the devel list.
https://lists.fedoraproject.org/pipermail/devel/2014-April/197344.html
== Detailed Description ==
Per: [1] it states:
=== Method ===
Disabling root access via any console device (tty).
=== Description ===
An empty /etc/securetty file prevents root login on any devices attached to
the computer.
=== Effects ===
Prevents access to the root account via the console or the network. The
following programs are '''prevented''' from accessing the root account: login,
gdm, kdm, xdm, Other network services that open a tty
=== Does Not Affect ===
Programs that do not log in as root, but perform administrative tasks through
setuid or other mechanisms.
The following programs are not prevented from accessing the root account: su,
sudo, ssh, scp, sftp
=== More Details ===
To further limit access to the root account, administrators can disable root
logins at the console by editing the /etc/securetty file. This file lists all
devices the root user is allowed to log into. If the file does not exist at
all, the root user can log in through any communication device on the system,
whether via the console or a raw network interface. This is dangerous, because
a user can log in to his machine as root via Telnet, which transmits the
password in plain text over the network. By default, Fedora's /etc/securetty
file only allows the root user to log in at the console physically attached to
the machine. To prevent root from logging in, remove the contents of this file
by typing the following command: echo > /etc/securetty
Warning: A blank /etc/securetty file does not prevent the root user from
logging in remotely using the OpenSSH suite of tools because the console is
not opened until after authentication.
== Scope ==
* Proposal owners: implement the change
* Other developers: None
* Release engineering: None
* Policies and guidelines: The Security Document mentioned above will need to
be updated.
[1] https://docs.fedoraproject.org/en-US/Fedora/19/html/Security_Guide/chap-S...
9 years, 11 months
F21 System Wide Change: Cockpit Management Console
by Jaroslav Reznik
= Proposed System Wide Change: Cockpit Management Console =
https://fedoraproject.org/wiki/Changes/CockpitManagementConsole
Change owner(s): Stephen Gallagher <sgallagh(a)fedoraproject.org>, Marius
Vollmer, Stef Walter
The Fedora Server Product will ship the Cockpit Project as available by
default, providing an approachable tool for system management.
== Detailed Description ==
Cockpit is a server manager that makes it easy to administer your GNU/Linux
servers via a web browser.
* Easy to use
Cockpit is perfect for new sysadmins, allowing them to easily perform simple
tasks such as storage administration, inspecting journals and starting and
stopping services.
* No interference
Jumping between the terminal and the web tool is no problem. A service started
via Cockpit can be stopped via the terminal. Likewise, if an error occurs in
the terminal, it can be seen in the Cockpit journal interface.
* Multi-server
You can monitor and administer several servers at the same time.
== Scope ==
Inclusion of Cockpit as part of the default (not necessarily minimal) install
set for Fedora Server
* Proposal owners:
** Support for a modular architecture
** Improved network management
* Other developers: N/A
* Release engineering: Inclusion of cockpit into comps.xml
* Policies and guidelines: N/A
Special Requests: Cockpit would like to request an additional 2-4 weeks on the
Fedora 21 schedule to ensure completion of the core functionality.
9 years, 11 months
F21 Self Contained Change: Jenkins
by Jaroslav Reznik
= Proposed Self Contained Change: Jenkins =
https://fedoraproject.org/wiki/Changes/Jenkins
Change owner(s): Michal Srb <msrb(a)redhat.com>
Jenkins is an open source continuous integration tool written in Java.
== Detailed Description ==
Jenkins provides continuous integration services for software development. It
is a server-based system. Builds can be started by various means, including
being triggered by commit in a version control system, scheduling via a cron-
like mechanism, building when other builds have completed, and by requesting a
specific build URL.
== Scope ==
* Proposal owners: All necessary Jenkins dependencies should be already in
Fedora. Jenkins needs mainly testing and bugfixing.
* Other developers: N/A (not a System Wide Change)
* Release engineering: N/A (not a System Wide Change)
* Policies and guidelines: N/A (not a System Wide Change)
9 years, 11 months
F21 System Wide Change: TCL/TK 8.6
by Jaroslav Reznik
= Proposed System Wide Change: TCL/TK 8.6 =
https://fedoraproject.org/wiki/Changes/f21tcl86
Change owner(s): Jaroslav Škarvada <jskarvad(a)redhat.com>
Update tcl/tk from 8.5 to 8.6 in Fedora 21.
== Detailed Description ==
Latest stable TCL/TK is version 8.6.1, currently there is version 8.5.13 in
Fedora. The aim of this change is to update the TCL/TK to latest stable
upstream release.
== Scope ==
* Proposal owners: Update spec file and build in koji (scratch builds /
private branch already exists), see RHBZ #889201 for details.
* Other developers: Cca. 60 other packages need to be revised, updated,
patched or rebuild (most patches already exist), see RHBZ #889201 for details.
* Release engineering: Tag creation, re-tagging, (tag f21-tcl already
exists), see RHBZ #889201 for details.
* Policies and guidelines: Probably no policy, guideline change needed.
9 years, 11 months
F21 Self Contained Change: Docker Container Image
by Jaroslav Reznik
= Proposed Self Contained Change: Docker Container Image =
https://fedoraproject.org/wiki/Changes/Docker_Container_Image
Change owner(s): Lokesh Mandvekar <lsm5(a)fedoraproject.org>, Dennis Gilmore
<dennis(a)ausil.us>
This is Fedora running inside Docker. Currently, there are non-official images
in the docker index, but we'd like them to really come out of release
engineering.
== Detailed Description ==
The public docker registry [1] hosts many fedora images [2] including an
unprefixed (semi-official) image [3]. However, this image doesn't have rel-eng
approval which would be required for a fully official image.
== Scope ==
* Proposal owners: The proposal owner needs to build the image tarballs with
the official kickstart scripts and make them available to docker's stackbrew
repo, which is used by the Docker maintainers to build unprefixed images.
Release Engineering approval/intervention would be needed at some point
(details still TBD)
* Other developers: N/A (not a System Wide Change)
* Release engineering: Official Release Engineering image approval. Process
still TBD.
* Policies and guidelines: N/A (not a System Wide Change)
[1] http://index.docker.io/
[2] https://index.docker.io/search?q=fedora
[3] https://index.docker.io/_/fedora/
9 years, 11 months
F21 Self Contained Change: Big Data Cloud Image
by Jaroslav Reznik
= Proposed Self Contained Change: Big Data Cloud Image =
https://fedoraproject.org/wiki/Changes/Big_Data_Cloud_Image
Change owner(s): Julien Eid <jeid64(a)gmail.com >, Haïkel Guémar
<karlthered_gmail_com >
Fedora Cloud agreed to make a base image plus several tailored to specific
purposes. This is one of the tailored ones, produced in collaboration with the
Big Data SIG.
== Detailed Description ==
Fedora Cloud agreed to make a base image plus several tailored to specific
purposes. This is one of the tailored ones, produced in collaboration with the
Big Data SIG.
== Scope ==
* Proposal owners: The developers must get a kickstart ready for a big data
image that has the Hadoop ecosystem installed and configured for changes that
distributed big data servers typically need. The developers may also if time
is permitting work on a second big data image centering around the Apache
Mesos ecosystem. The change does not affect large part of the distribution and
does not block or affect other parts of the distribution.
* Other developers: N/A (not a System Wide Change)
* Release engineering: not a System Wide Change, but there will be a new image
for release engineering to produce and handle.
* Policies and guidelines: N/A (not a System Wide Change)
9 years, 11 months
F21 System Wide Change: BerkeleyDB 6
by Jaroslav Reznik
= Proposed System Wide Change: BerkeleyDB 6 =
https://fedoraproject.org/wiki/Changes/BerkeleyDB_6
Change owner(s): Jan Staněk <jstanek(a)redhat.com>
Add BerkeleyDB v. 6, which changed license from previous releases (GPLv2+ to
AGPLv3+), to Fedora while keeping the older version for packages which cannot
use BerkeleyDB with the new license.
== Detailed Description ==
The BerkeleyDB, used between others by rpm [1], changed license between
versions 5.* and 6.* to AGPLv3+ from GPLv2+. As those two licenses are not
compatible, packages using the BerkeleyDB either has to change its license to
AGPLv3+ compatible, keep on using the older BerkeleyDB or use another DB
entirely.
Target of this change is to create new set of packages from current libdb [2],
which contains the v5 version, and keep it alongside the latest BerkeleyDB.
== Scope ==
* Proposal owners: Create new set of packages and introduce proper versioning
in order to not confuse the dynamic linker.
* Other developers: Packages dependent on libdb would have to specify which
version they want to use (specify version in the spec Requires: field).
Rebuilds of dependent packages will be necessary.
* Release engineering: None
* Policies and guidelines: None
[1] https://apps.fedoraproject.org/packages/rpm
[2] https://apps.fedoraproject.org/packages/libdb
9 years, 11 months
F21 Self Contained Change: Apache Pig
by Jaroslav Reznik
= Proposed Self Contained Change: Apache Pig =
https://fedoraproject.org/wiki/Changes/ApachePig
Change owner(s): Peter MacKinnon <pmackinn(a)redhat.com>
Apache Pig [1] is a data analysis tool built on top of Apache Hadoop.
== Detailed Description ==
Apache Pig is a platform for analysing large data sets that consists of a
high-level language for expressing data analysis programs, coupled with
infrastructure for evaluating these programs. The salient property of Pig
programs is that their structure is amenable to substantial parallelization,
which in turns enables them to handle very large data sets.
== Scope ==
* Proposal owners: The Pig [2] package has been accepted into Fedora and
provides all the functionality from the upstream release with the exception of
jython (version) and parquet (unpackaged) support.
* Other developers: N/A (not a System Wide Change)
* Release engineering: N/A (not a System Wide Change)
* Policies and guidelines: N/A (not a System Wide Change)
[1] http://pig.apache.org/
[2] http://pkgs.fedoraproject.org/cgit/pig.git
9 years, 11 months