The message about Ceph [1] reminded me that we should probably make the
same notification for Eclipse Platform.
The Eclipse Platform upstream is in the process of dropping all support for
32bit arches.
The current state is that upstream are no longer building for 32bit arches
upstream for 4.10 (release 2018-12) onwards. I expect them to start
actively removing 32bit specific code in future releases.
You can read more about the decision on the upstream bug [2]
In Fedora, Eclipse 4.10 which I am building for Rawhide and F29 right now,
still builds for 32bit arches, but this will not last long. I expect in a
future release (4.11 or later) Eclipse will no longer build on x86/arm and
at that time I will no longer be able to support these architectures in
Fedora -- I expect to exclude those arches from Fedora builds.
If you depend on the ECJ batch compiler, this will continue to be available
on all arches as a noarch package. (It is packaged as a discrete SRPM and
has no build or runtime dependency on the Eclipse Platform itself.)
Regards,
Mat
[1]
https://lists.fedoraproject.org/archives/list/devel@lists.fedoraproject.org…
[2] https://bugs.eclipse.org/bugs/show_bug.cgi?id=526620
This outage is a replacement of an earlier one in December which had to be
cancelled.
There will be an outage starting at 2019-02-02 13:00 UTC,
which will last approximately 2 hours.
To convert UTC to your local time, take a look at
http://fedoraproject.org/wiki/Infrastructure/UTCHowto
or run:
date -d '2019-02-02 13:00UTC'
Reason for outage:
Various switches at the colocation are needing updates and reboots to get
latest firmware working. While the outage should not take the entire 2
hours, it is being blocked out in case there are problems which are not
realized and need backing out or other changes.
Affected Services:
dl.fedoraproject.org
all build services
most web services
copr and all other cloud services.
Ticket Link:
https://pagure.io/fedora-infrastructure/issue/7535
Please join #fedora-admin or #fedora-noc on irc.freenode.net
or add comments to the ticket for this outage above.
--
Stephen J Smoogen.
https://fedoraproject.org/wiki/Changes/Vagrant_2.2_with_QEMU_Session
== Summary ==
Upgrade to Vagrant 2.2, the latest stable version of Vagrant. Enable
QEMU Session by default.
== Owner ==
* Name: [[User:pvalena | Pavel Valena]], [[User:vondruch | Vit Ondruch]]
* Email: pvalena(a)redhat.com, vondruch(a)redhat.com
* Release notes owner:
== Detailed Description ==
Vagrant 2.2 is new upstream's major release, that includes many
features, improvements, and and bug fixes.
Using '''qemu:///session''' instead of '''qemu:///system''' Vagrant
will run unprivileged.
== Benefit to Fedora ==
* Enable QEMU Session by default. With this, there's no need for user
to input any password, or be present in some group. Everyone is able
to use Vagrant, regardless of group or other ACLs.
* Add host support for void linux
* Add support for VirtualBox 6.0
* Add command for uploading files to guest
== Scope ==
* Proposal owners:
** Finish packaging Vagrant 2.2. Current changes:
https://src.fedoraproject.org/rpms/vagrant/pull-request/17
** Finish packaging Vagrant-Libvirt plugin. Current changes:
https://src.fedoraproject.org/rpms/vagrant-libvirt/pull-request/3
** Work has been done in a Copr repository:
https://copr.fedorainfracloud.org/coprs/pvalena/vagrant/
* Other developers: N/A (not a System Wide Change)
* Release engineering: [https://pagure.io/releng/issues #8085]
** [[Fedora_Program_Management/ReleaseBlocking/Fedora{{FedoraVersionNumber|next}}|List
of deliverables]]: N/A (not a System Wide Change)
* Policies and guidelines: N/A (not a System Wide Change)
* Trademark approval: N/A (not needed for this Change)
== Upgrade/compatibility impact ==
Because of QEMU Session enabled by defailt, a failure occurs with if
Vagrantfile contains:
```
test_vm.vm.network :private_network, :ip => "172.16.0.2"
```
or similar.
Can be solved by setting `libvirt.qemu_use_session = false` in Vagrantfile.
== How To Test ==
* No special hardware is needed.
* Install Vagrant
* Run ```vagrant version```
* Use your Vagrantfiles or create new as before
* If something doesn't work as it should, let us know.
== User Experience ==
New features that come with Vagrant 2.2 will be available.
Users will not need to add themseles to any group, or have root ACLs
and input a password every time they use Vagrant.
== Dependencies ==
N/A (not a System Wide Change)
== Contingency Plan ==
* Contingency mechanism: 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)
* Blocks product? N/A (not a System Wide Change)
== Documentation ==
https://www.vagrantup.com/docs/
== Release Notes ==
https://github.com/hashicorp/vagrant/blob/master/CHANGELOG.md
--
Ben Cotton
Fedora Program Manager
TZ=America/Indiana/Indianapolis
This is your reminder that the software string freeze deadline is
Tuesday, 5 February 2019.
--
Ben Cotton
Fedora Program Manager
TZ=America/Indiana/Indianapolis
https://fedoraproject.org/wiki/Changes/MongoDB_Removal
== Summary ==
Fedora has determined that the Server Side Public Licensev1 (SSPL) is
not a Free Software License. Therefore, we need to drop MongoDB from
Fedora.
== Owner ==
* Name: [[User:panovotn| Patrik Novotný]]
<!-- Include you email address that you can be reached should people
want to contact you about helping with your change, status is
requested, or technical issues need to be resolved. If the change
proposal is owned by a SIG, please also add a primary contact person.
-->
* Email: panovotn(a)redhat.com
--
Ben Cotton
Fedora Program Manager
TZ=America/Indiana/Indianapolis
https://fedoraproject.org/wiki/Changes/ImprovedGrubMenu
== Summary ==
Improve the GRUB menu by only having the default boot option for each
installed operating system in the main menu, and the other options
into a sub-menu. This would better organize the boot options and lead
to an easier and seamless boot experience.
== Owner ==
* Name: [[User:Javierm|Javier Martinez Canillas]]
* Email: javierm(a)redhat.com
== Detailed Description ==
The current GRUB menu is confusing, specially when multiple operating
systems are installed. The Fedora boot entries are added first and
then the ones for the other installed operating systems.
The main menu contains all the boot entries for Fedora but only the
default boot entry for the other operating systems, the non-default
boot entries for the other installed operating systems are placed into
a per operating system sub-menu.
An example of how the GRUB menu currently looks can be found at
[https://javierm.fedorapeople.org/grub2/menu/fedora_menu.pnghttps://javierm.fedorapeople.org/grub2/menu/fedora_menu.png]
This can be improved by adding a sub-menu for the Fedora non-default
boot entries, as is already the case for the other installed operating
systems. This will make the boot entries for all the operating systems
consistent.
Another improvement would be to group all the default options for the
operating systems as one section, followed by another section that
groups all the sub-menus for the non-default options.
A tentative design made by Allan Day for the improved GRUB menu can be
found at [https://wiki.gnome.org/Design/OS/BootOptions#Tentative_Designhttps://wiki.gnome.org/Design/OS/BootOptions#Tentative_Design]
For Fedora, the boot option in the main menu will either be the
selected default boot entry or if no default was chosen, the latest
installed kernel. For the other installed operating systems, the boot
option in the main menu will be the latest kernel as found by GRUB's
os-prober script.
== Benefit to Fedora ==
Making the menu less confusing and with better organized boot options
will lead to a better user experience and make easier for users to
choose the operating systems to boot.
== Scope ==
* Proposal owners:
# Change GRUB to implement the changes as described in the "Detailed
Description" section.
# Make sure this is all properly documented in release-notes, etc.
* Other developers:
# Test and watch for regressions.
* Policies and guidelines: The policies and guidelines do not need to
be updated.
* Trademark approval: No changes needed.
== Upgrade/compatibility impact ==
The changes are in the grub.cfg file generated at install time by
Anaconda. Users can manually enable this after an upgrade by executing
gru2-mkconfig to regenerate their grub.cfg file.
== How To Test ==
# Single OS test
## Install Fedora in a VM.
## On boot the default boot option is in the main menu and the other
options (e.g: rescue boot option) are in a sub-menu.
# Multi boot test
## Install Fedora on a machine which other operating system installed.
## On boot the default boot options for the operating systems are in
the main menu and the other options in sub-menus.
== User Experience ==
A simpler and easier to understand GRUB boot menu. Choosing which
operating system to boot should be simpler and involve less steps.
== Dependencies ==
None
== Contingency Plan ==
* Contingency mechanism: Revert the GRUB changes.
* Contingency deadline: Beta Freeze
* Blocks release? No
* Blocks product? None
--
Ben Cotton
Fedora Program Manager
TZ=America/Indiana/Indianapolis
(Note this change was previously submitted for Fedora 29:
https://pagure.io/fesco/issue/2064)
https://fedoraproject.org/wiki/Changes/Retire_YUM_3
== Summary ==
Remove yum (v3) and all related packages from Fedora.
== Owner ==
* Name: [[User:mdomonko|Michal Domonkos]]
* Email: mdomonko(a)redhat.com
== Detailed Description ==
Remove packages from the distribution:
* createrepo
* yum
* yum-langpacks
* yum-utils
* yum-metadata-parser
* yum-updatesd
* python-urlgrabber
All these packages should no longer be used and all software using
them should be migrated to DNF.
Compatibility:
* Important packages such as yum, createrepo or yum-utils will be
provided/obsoleted by relevant packages from the dnf stack
* Important executables such yum, repoquery, createrepo, etc. will be
provided either as new executables or via symlinks
== Benefit to Fedora ==
Drop an old package manager that has no active upstream development.
Move existing users to DNF which that has active development.
Secondary benefit is reducing number of packages in Fedora that still
depend on Python 2.
== Scope ==
* Proposal owners: Remove packages from the distribution: createrepo,
yum, yum-langpacks, yum-utils, yum-metadata-parser, yum-updatesd,
python-urlgrabber
* Other developers: Either remove packages from the distribution or
switch them to DNF
* Release engineering: [https://pagure.io/releng/issue/7588 #7588]
* Policies and guidelines: N/A
* Trademark approval: N/A (not needed for this Change)
== Upgrade/compatibility impact ==
Any tool based on YUM 3 Python API will stop working. This applies on
any 3rd party software which won't be changed in Fedora as part of
this change.
CLI compatibility will be provided by DNF.
== How To Test ==
Repoclosure passes after dropping the packages.
== User Experience ==
There shouldn't be any impact on YUM users because the functionality
is provided by DNF already.
Users of tools listed in the Dependencies section shouldn't see any
difference if the migration to DNF is done properly.
== Dependencies ==
The list of source packages (SRPMs) that still depend on some of the
yum-related packages to be removed:
(see wiki page)
== Contingency Plan ==
* Contingency mechanism: Do not remove the packages in the current release.
* Contingency deadline: Beta Freeze
* Blocks release? No
* Blocks product? No
== Documentation ==
N/A
== Release Notes ==
Inform end-users about removing the YUM 3 stack and definitive migration to DNF.
--
Ben Cotton
Fedora Program Manager
TZ=America/Indiana/Indianapolis
https://fedoraproject.org/wiki/Changes/Fish_3.0
== Summary ==
Update [https://fishshell.com/ Fish] to 3.0.
== Owner ==
* Name: [[User:ignatenkobrain|Igor Gnatenko]]
* Email: ignatenkobrain(a)fedoraproject.org
== Detailed Description ==
Not only update it in F30 but also provide new version as opt-in for
F28 and F29.
== Benefit to Fedora ==
The new version of Fish has quite some number of bugfixes, features
and performance improvements.
== Scope ==
* Proposal owners: Put fish 3.0 into a module (that means it will be
available for F28 and F29) and mark it as default in Rawhide.
* Other developers: N/A (not a System Wide Change)
* Release engineering: [https://pagure.io/releng/issue/8077 #8077]
* Policies and guidelines: N/A (not a System Wide Change)
* Trademark approval: N/A (not needed for this Change)
== Upgrade/compatibility impact ==
* Process and job expansion has largely been removed. <code>%</code>
will no longer perform these expansions, except for <code>%self</code>
for the PID of the current shell. Additionally, job management
commands (<code>disown</code>, <code>wait</code>, <code>bg</code>,
<code>fg</code> and <code>kill</code>) will expand job specifiers
starting with <code>%</code>
([https://github.com/fish-shell/fish-shell/issues/4230 #4230],
[https://github.com/fish-shell/fish-shell/issues/1202 #1202]).
* <code>set x[1] x[2] a b</code>, to set multiple elements of an array
at once, is no longer valid syntax
([https://github.com/fish-shell/fish-shell/issues/4236 #4236]).
* A literal <code>{}</code> now expands to itself, rather than
nothing. This makes working with <code>find -exec</code> easier
([https://github.com/fish-shell/fish-shell/issues/1109 #1109],
[https://github.com/fish-shell/fish-shell/pull/4632 #4632]).
* Literally accessing a zero-index is now illegal syntax and is caught
by the parser ([https://github.com/fish-shell/fish-shell/issues/4862
#4862]). (fish indices start at 1)
* Successive commas in brace expansions are handled in less surprising
manner. For example, <code>{,,,}</code> expands to four empty strings
rather than an empty string, a comma and an empty string again
([https://github.com/fish-shell/fish-shell/issues/3002 #3002],
[https://github.com/fish-shell/fish-shell/pull/4632 #4632]).
* <code>for</code> loop control variables are no longer local to the
<code>for</code> block
([https://github.com/fish-shell/fish-shell/issues/1935 #1935]).
* Variables set in <code>if</code> and <code>while</code> conditions
are available outside the block
([https://github.com/fish-shell/fish-shell/issues/4820 #4820]).
* Local exported (<code>set -lx</code>) vars are now visible to
functions ([https://github.com/fish-shell/fish-shell/issues/1091
#1091]).
* The new <code>math</code> builtin (see below) does not support
logical expressions; <code>test</code> should be used instead
([https://github.com/fish-shell/fish-shell/issues/4777 #4777]).
* Range expansion will now behave sensibly when given a single
positive and negative index (<code>$foo[5..-1]</code> or
<code>$foo[-1..5]</code>), clamping to the last valid index without
changing direction if the list has fewer elements than expected.
* <code>read</code> now uses <code>-s</code> as short for
<code>--silent</code> (à la <code>bash</code>); <code>--shell</code>'s
abbreviation (formerly <code>-s</code>) is now <code>-S</code> instead
([https://github.com/fish-shell/fish-shell/issues/4490 #4490]).
* <code>cd</code> no longer resolves symlinks. fish now maintains a
virtual path, matching other shells
([https://github.com/fish-shell/fish-shell/issues/3350 #3350]).
* <code>source</code> now requires an explicit <code>-</code> as the
filename to read from the terminal
([https://github.com/fish-shell/fish-shell/issues/2633 #2633]).
* Arguments to <code>end</code> are now errors, instead of being
silently ignored.
* The names <code>argparse</code>, <code>read</code>,
<code>set</code>, <code>status</code>, <code>test</code> and
<code>[</code> are now reserved and not allowed as function names.
This prevents users unintentionally breaking stuff
([https://github.com/fish-shell/fish-shell/issues/3000 #3000]).
* The <code>fish_user_abbreviations</code> variable is no longer used;
abbreviations will be migrated to the new storage format
automatically.
* The <code>FISH_READ_BYTE_LIMIT</code> variable is now called
<code>fish_byte_limit</code>
([https://github.com/fish-shell/fish-shell/issues/4414 #4414]).
* Environment variables are no longer split into arrays based on the
record separator character on startup. Instead, variables are not
split, unless their name ends in PATH, in which case they are split on
colons ([https://github.com/fish-shell/fish-shell/issues/436 #436]).
* The <code>history</code> builtin's <code>--with-time</code> option
has been removed; this has been deprecated in favor of
<code>--show-time</code> since 2.7.0
([https://github.com/fish-shell/fish-shell/pull/4403 #4403]).
* The internal variables <code>__fish_datadir</code> and
<code>__fish_sysconfdir</code> are now known as
<code>__fish_data_dir</code> and <code>__fish_sysconf_dir</code>
respectively.
== How To Test ==
0. Make sure to have modular repositories enabled
1. Run dnf module install fish:3
2. Try out normal workload in fish
== User Experience ==
* fish now supports <code>&&</code> (like <code>and</code>),
<code>||</code> (like <code>or</code>), and <code>!</code> (like
<code>not</code>), for better migration from POSIX-compliant shells
([https://github.com/fish-shell/fish-shell/issues/4620 #4620]).
* fish may be started in private mode via <code>fish --private</code>.
Private mode fish sessions do not have access to the history file and
any commands evaluated in private mode are not persisted for future
sessions. A session variable <code>$fish_private_mode</code> can be
queried to detect private mode and adjust the behavior of scripts
accordingly to respect the user's wish for privacy.
* A new <code>wait</code> command for waiting on backgrounded
processes ([https://github.com/fish-shell/fish-shell/pull/4498
#4498]).
* <code>alias</code> has a new <code>--save</code> option to save the
generated function immediately
([https://github.com/fish-shell/fish-shell/pull/4878 #4878]).
* <code>funced</code> has a new <code>--save</code> option to
automatically save the edited function after successfully editing
([https://github.com/fish-shell/fish-shell/pull/4668 #4668]).
* <code>history search</code> supports globs for wildcard searching
([https://github.com/fish-shell/fish-shell/issues/3136 #3136]) and has
a new <code>--reverse</code> option to show entries from oldest to
newest ([https://github.com/fish-shell/fish-shell/pull/4375 #4375]).
* <code>set</code> has new <code>--append</code> and
<code>--prepend</code> options
([https://github.com/fish-shell/fish-shell/issues/1326 #1326]).
* <code>set</code> has a new <code>--show</code> option to show lots
of information about variables
([https://github.com/fish-shell/fish-shell/issues/4265 #4265]).
* <code>string match</code> with an empty pattern and
<code>--entire</code> in glob mode now matches everything instead of
nothing ([https://github.com/fish-shell/fish-shell/issues/4971
#4971]).
* <code>string split</code> supports a new <code>--no-empty</code>
option to exclude empty strings from the result
([https://github.com/fish-shell/fish-shell/pull/4779 #4779]).
* <code>string</code> has new subcommands <code>split0</code> and
<code>join0</code> for working with NUL-delimited output.
* <code>string</code> no longer stops processing text after NUL
characters ([https://github.com/fish-shell/fish-shell/issues/4605
#4605])
* <code>string escape</code> has a new <code>--style regex</code>
option for escaping strings to be matched literally in
<code>string</code> regex operations.
* <code>test</code> now supports floating point values in numeric comparisons.
* Pressing Ctrl-C while running a script now reliably terminates fish
([https://github.com/fish-shell/fish-shell/issues/5253 #5253]).
See https://fishshell.com/release_notes.html for more.
== Dependencies ==
N/A (not a System Wide Change)
== Contingency Plan ==
* Contingency mechanism: (What to do? Who will do it?) N/A
* Contingency deadline: N/A (not a System Wide Change)
== Documentation ==
https://fishshell.com/release_notes.html
--
Ben Cotton
Fedora Program Manager
TZ=America/Indiana/Indianapolis