ssl3_get_record:wrong version number
by David Muse
I keep getting "ssl3_get_record:wrong version number" errors when I try to run "fedpkg build", usually during checkout. Searching the archives, it looks like the last time someone reported this, it was during a planned outage, but I don't see anything down on the fedora infrastructure status page. Is this error expected at the moment, or am I doing something wrong?
Thanks,
David
david.muse(a)firstworks.com
4 years, 3 months
Self Introduction: Breno B. Fernandes
by Breno Brand Fernandes
Hi all,
I am ~33 years old and I've been using (and working with?) Linux since I
was 16-ish.
I've been using Centos/RedHat/Fedora for a while and am now interested in
getting more involved.
I talk to some of you at #epel@freenode.
People are always very helpful and friendly.
I expect to consistently contribute to the Fedora community.
It is very nice to get to know such a community with so many brilliant
people.
- Breno
4 years, 3 months
Fedora 33 Self-Contained Change proposal: retire python34
by Ben Cotton
https://fedoraproject.org/wiki/Changes/RetirePython34
== Summary ==
The {{package|python34}} package will be retired without replacement
from [[Releases/33|Fedora 33]]. Python 3.4 has been End of Life since
March 2019 and was kept around only to test software targeting EPEL 6
and Debian 8 “Jessie”. The removal is aligned with EPEL 6 EOL and
happens after the EOL of Debian 8.
== Owner ==
* Name: [[User:Churchyard|Miro Hrončok]]
* Email: mhroncok(a)redhat.com
== Detailed Description ==
The {{package|python34}} package with the Python interpreter in
version 3.4 is kept in Fedora only to make it possible for Fedora
users to test their software against the Python version shipped in
EPEL 6 and EPEL 7. RHEL 7 now contains Python 3.6.
[https://wiki.debian.org/LTS Debian 8 “Jessie” is End of Life in
2020-06]. [[EPEL|The EPEL 6 End of Life is planned for 2020-11]]. This
roughly corresponds with the
[https://fedorapeople.org/groups/schedule/f-33/f-33-key-tasks.html
Fedora 33 release date]. Hence, we decided to retire (completely
remove) {{package|python34}} from Fedora 33, before it gets released.
== Benefit to Fedora ==
The maintenance of Python 3.4 was getting harder and harder every
year. The support for Python 3.4 has disappeared from pip and an older
version of pip has to be bundled in {{package|python34}}, while pip
bundles even more old libraries. Support from tox and virtualenv will
eventually disappear as well.
There is no direct benefit here, except that we don't want to maintain
it anymore and we don't think it's a good idea either.
Consider this change proposal a louder orphaning, except that we will
continue to maintain the package in older released and supported
Fedoras (31 and 32). If you wish to continue maintaining Python 3.4 in
Fedora, please [[SIGs/Python|speak to us]] first.
== Scope ==
* Proposal owners: Retire {{package|python34}}. Obsolete it from
{{package|fedora-obsolete-packages}} if it causes troubles on
upgrades. Make sure no Fedora package depends on it in any way (incl.
weak dependencies).
* 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)
* Trademark approval: N/A (not needed for this Change)
== Upgrade/compatibility impact ==
The package will no longer be available from the repositories, but it
may remain on existing installations. If it causes troubles on
upgrade, it needs to be obsoleted.
== How To Test ==
N/A (not a System Wide Change)
== User Experience ==
No more Python 3.4 to test user software on.
== Dependencies ==
N/A (not a System Wide Change)
== Contingency Plan ==
* Contingency mechanism: (What to do? Who will do it?) 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)
== Documentation ==
N/A (not a System Wide Change)
--
Ben Cotton
He / Him / His
Fedora Program Manager
Red Hat
TZ=America/Indiana/Indianapolis
4 years, 3 months
Fedora 33 Self-Contained Change proposal: retire python26
by Ben Cotton
https://fedoraproject.org/wiki/Changes/RetirePython26
== Summary ==
The {{package|python26}} package will be retired without replacement
from [[Releases/33|Fedora 33]]. Python 2.6 has been End of Life since
October 2013 and was kept around only to test software targeting
RHEL/EPEL 6. The removal is aligned with EPEL 6 EOL.
== Owner ==
* Name: [[User:Churchyard|Miro Hrončok]]
* Email: mhroncok(a)redhat.com
== Detailed Description ==
The {{package|python26}} package with the Python interpreter in
version 2.6 is kept in Fedora only to make it possible for Fedora
users to test their software against the Python version shipped in
RHEL 6.
[[EPEL|The EPEL 6 End of Life is planned for 2020-11]]. This roughly
corresponds with the
[https://fedorapeople.org/groups/schedule/f-33/f-33-key-tasks.html
Fedora 33 release date]. Hence, we decided to retire (completely
remove) {{package|python26}} from Fedora 33, before it gets released.
== Benefit to Fedora ==
The maintenance of Python 2.6 was getting harder and harder every
year. The support for Python 2.6 has disappeared from virtualenv, tox.
{{package|python26}} cannot be built against the new OpenSSL versions,
etc.
There is no direct benefit here, except that we don't want to maintain
it anymore and we don't think it's a good idea either.
Consider this change proposal a louder orphaning, except that we will
continue to maintain the package in older released and supported
Fedoras (31 and 32). If you wish to continue maintaining Python 2.6 in
Fedora, please [[SIGs/Python|speak to us]] first.
== Scope ==
* Proposal owners: Retire {{package|python26}}. Obsolete it from
{{package|fedora-obsolete-packages}} if it causes troubles on
upgrades. Make sure no Fedora package depends on it in any way (incl.
weak dependencies).
* 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)
* Trademark approval: N/A (not needed for this Change)
== Upgrade/compatibility impact ==
The package will no longer be available from the repositories, but it
may remain on existing installations. If it causes troubles on
upgrade, it needs to be obsoleted.
== How To Test ==
N/A (not a System Wide Change)
== User Experience ==
No more Python 2.6 to test user software on.
== Dependencies ==
N/A (not a System Wide Change)
== Contingency Plan ==
* Contingency mechanism: (What to do? Who will do it?) 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)
== Documentation ==
N/A
--
Ben Cotton
He / Him / His
Fedora Program Manager
Red Hat
TZ=America/Indiana/Indianapolis
4 years, 3 months
poppler soname bump in rawhide
by Marek Kasik
Hi,
I'm going to rebase poppler in rawhide to poppler-0.84.0 at the
beginning of next week.
There are several API changes and soname bump of the base library
libpoppler.so.*.
Here is scratch-build of poppler-0.84.0:
https://koji.fedoraproject.org/koji/taskinfo?taskID=40194709
Btw, if your package uses the unstable API (headers from poppler-devel),
could you consider to change it to use a stable API (glib, qt, C++)?
Also, if your package still uses qt4 frontend, try to use another one
since this was removed in upstream and we have it just as a backup
solution for the time being (and its maintaining costs time).
I'll backport/fix simple issues in the dependent packages and rebuild
them together with the rebase (e.g. the one with GlobalParams being
unique ptr now).
Regards
Marek
4 years, 3 months
Schedule for Mondays's FESCo Meeting (2020-01-06)
by Petr Šabata
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-01-06 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 =
F32 System-Wide Change: Ruby 2.7
https://pagure.io/fesco/issue/2308
APPROVED (+7, 0, -0)
F33 System-Wide Change: Python 3.9
https://pagure.io/fesco/issue/2299
APPROVED (+5, 0, -0)
Nonresponsive maintainer: Clément David (davidcl)
https://pagure.io/fesco/issue/2306
APPROVED (+0, 0, -0)
Acked by davidcl in the ticket.
F32 System-Wide Change: Stop shipping individual component libraries
in clang-libs package
https://pagure.io/fesco/issue/2305
APPROVED (+4, 0, -0)
F32 System-Wide Change: LLVM 10
https://pagure.io/fesco/issue/2304
APPROVED (+5, 0, -0)
Nonresponsive maintainer: Moez Roy (moezroy)
https://pagure.io/fesco/issue/2302
APPROVED (+5, 0, -0)
Nonresponsive maintainer: Anuj More (anujmore)
https://pagure.io/fesco/issue/2301
APPROVED (+4, 0, -0)
Packages and account for automated testing of the packager workflow with gating
https://pagure.io/fesco/issue/2300
APPROVED (+3, 0, -0)
= New business =
#topic #2303 F32 System-Wide Change: Drop Optical Media Release Criterion
https://pagure.io/fesco/issue/2303
= 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, 3 months
Fedora 32 System-Wide Change proposal: Enable fstrim.timer by default
by Ben Cotton
https://fedoraproject.org/wiki/Changes/EnableFSTrimTimer
== Summary ==
Enabling fstrim.timer will cause fstrim.service to execute weekly,
which in turn executes `/usr/sbin/fstrim --fstab --verbose --quiet`
== Owner ==
* Name: [[User:chrismurphy| Chris Murphy]]
* Email: bugzilla(a)colorremedies.com
== Detailed Description ==
Over time, some users experience slow downs in certain flash storage
devices. This might be alleviated by issuing a periodic fstrim command
to the mounted file system. Devices and file systems that don't
support fstrim are unaffected.
By enabling the existing fstrim.timer systemd unit file by default,
will cause weekly execution of the fstrim.service. This service acts
only on mounted filesystems listed in fstab. On supported hardware
(e.g. most SD Card, SSD, and NVMe drives), LVM thin provisioned
storage, and file systems (ext4, XFS, Btrfs, f2fs, but excluding
FAT16/32), fstrim will inform underlying physical storage device's
firmware about unused blocks. This hinting can make wear leveling and
block erasure more efficient.
The timer will execute Monday at 00:00 local time. If the system is
inactive at this time, it will be run immediately upon becoming active
again (upon wake from suspend, during or very soon after boot).
Some devices do not support "queued trim" and there may be a brief
(seconds) pause as the drive firmware acts upon command issuance. It's
expected most users won't notice this.
== Benefit to Fedora ==
This is an optimization to the storage stack, and may help improve
performance and wear leveling for some devices. On LVM thin
provisioned stacks, unused LV extents will be returned to the thin
pool, reducing the likelihood of pool exhaustion.
In a way, this is overdue on Fedora, as it's been the default behavior
on other distributions for a while (at least Ubuntu and openSUSE). At
least it has been well tested.
== Scope ==
* Proposal owners:<br>
Upon approval, submit a PR for fedora-release, modifying
90-default.preset to enable fstrim.timer
* Other developers:<br>
fstrim.timer is provided by util-linux, notify util-linux maintainer<br>
https://bugzilla.redhat.com/show_bug.cgi?id=1785041
* Release engineering: [https://pagure.io/releng/issues #9116]
* Policies and guidelines: N/A
* Trademark approval: N/A
== Upgrade/compatibility impact ==
fstrim.timer will be enabled on upgrade. An upgraded system should
exhibit the same behaviors as a clean installed system.
== How To Test ==
The low level function of systemd timers, fstrim.service, and fstrim
command are well understood and tested already, all Fedora needs to
test is that the timer is enabled following clean installation and
upgrades:<br><br>
Preliminaries:
* Clean install Fedora 32, any edition or spin; or
* Upgrade from Fedora 30 or Fedora 31, any edition or spin, to Fedora 32
Confirm:
* Run `sudo systemctl list-timers`
* Confirm `fstrim.timer` is listed under UNITS, and is next scheduled
for Monday 00:00:00
* Anytime following the listed NEXT date+time, run `sudo systemctl
status fstrim.timer`
Example, should apply in all cases:<br>
{{code|Dec 18 13:48:54 fmac.local systemd[1]: fstrim.service: Succeeded.}}
Full example on a device with an SSD and filesystem supporting trim:<br>
<pre>
$ sudo systemctl status fstrim.service
● fstrim.service - Discard unused blocks on filesystems from /etc/fstab
Loaded: loaded (/usr/lib/systemd/system/fstrim.service; static;
vendor preset: disabled)
Active: inactive (dead) since Wed 2019-12-18 13:48:54 MST; 15min ago
Docs: man:fstrim(8)
Process: 3870 ExecStart=/usr/sbin/fstrim --fstab --verbose --quiet
(code=exited, status=0/SUCCESS)
Main PID: 3870 (code=exited, status=0/SUCCESS)
CPU: 1.387s
Dec 18 13:48:48 fmac.local systemd[1]: Starting Discard unused blocks
on filesystems from /etc/fstab...
Dec 18 13:48:54 fmac.local fstrim[3870]: /: 32 GiB (34409328640 bytes)
trimmed on /dev/sda4
Dec 18 13:48:54 fmac.local systemd[1]: fstrim.service: Succeeded.
Dec 18 13:48:54 fmac.local systemd[1]: Started Discard unused blocks
on filesystems from /etc/fstab.
Dec 18 13:48:54 fmac.local systemd[1]: fstrim.service: Consumed 1.387s CPU time.
</pre>
<br>
Regardless of configuration, there should be no errors.
== User Experience ==
Most users will not notice the change. Some will notice improved
performance of flash storage devices, and more efficient use of thinly
provisioned storage.
This does not affect all storage. Only file systems listed in fstab
are affected.
If the user/admin wants fstrim to apply to all mounted file systems,
they should copy the original fstrim.service unit file, replacing
`--fstab` with `--all`, and use this modified unit file as a drop-in
service unit in /etc. See
https://www.freedesktop.org/software/systemd/man/systemd.unit.html
== Dependencies ==
None
== Contingency Plan ==
* Contingency mechanism: Owner will revert the change
* Contingency deadline: final freeze
* Blocks release? No
* Blocks product? No
== Documentation ==
man fstrim
== Release Notes ==
fstrim.timer is enabled by default, and runs fstrim.service weekly.
This service executes `/usr/sbin/fstrim --fstab --verbose --quiet` See
`man fstrim` for details.
--
Ben Cotton
He / Him / His
Fedora Program Manager
Red Hat
TZ=America/Indiana/Indianapolis
4 years, 3 months
Fedora 32 System-Wide Change proposal: Golang 1.14
by Ben Cotton
https://fedoraproject.org/wiki/Changes/golang1.14
== Summary ==
Rebase of Golang package to upcoming version 1.14 in Fedora 32,
including rebuild of all dependent packages(pre-release version of Go
will be used for rebuild, if released version will not be available at
the time of the mass rebuild).
== Owner ==
* Name: [[User:Jcajka| Jakub Čajka]]
* Email: jcajka(a)redhat.com
== Detailed Description ==
Rebase of Golang package to upcoming version 1.14 in Fedora 32. Golang
1.14 is schedule to be released in Feb 2020.
Due to current nature and state of Go packages, rebuild of dependent
package will be required to pick up the changes.
== Benefit to Fedora ==
Staying closely behind upstream by providing latest release of golang,
which includes performance improvements and improvements in support
for currently supported platforms among other bug fixes and new
features. For complete list of changes see upstream change notes at
https://tip.golang.org/doc/go1.14 . In result Fedora will be providing
solid development platform for Go language.
== Scope ==
* Proposal owners: Rebase golang package in f32, help with resolving
possible issues found during package rebuilds.
* Other developers: Fix possible issues, with help from golang maintainers.
* Release engineering: Rebuild of dependent packages as part of
planned mass-rebuild. Tracking ticket
https://pagure.io/releng/issue/9136
* Policies and guidelines: N/A
* Trademark approval: N/A
== Upgrade/compatibility impact ==
None
== How To Test ==
;0.
:a)Install golang 1.14 from rawhide and use it to build your
application(s)/package(s).
:b)Scratch build against rawhide.
;1.
:Your application/package built using golang 1.14 should work as expected.
== User Experience ==
None
== Dependencies ==
<pre>
dnf repoquery -q --releasever=rawhide --disablerepo='*'
--qf='%{name}' --enablerepo=fedora-source --enablerepo=updates-source
--enablerepo=updates-testing-source --archlist=src --whatrequires
'golang'
dnf repoquery -q --releasever=rawhide --disablerepo='*'
--qf='%{name}' --enablerepo=fedora-source --enablerepo=updates-source
--enablerepo=updates-testing-source --archlist=src --whatrequires
'compiler(go-compiler)'
dnf repoquery -q --releasever=rawhide --disablerepo='*'
--qf='%{name}' --enablerepo=fedora-source --enablerepo=updates-source
--enablerepo=updates-testing-source --archlist=src --whatrequires
'compiler(golang)'
dnf repoquery -q --releasever=rawhide --disablerepo='*'
--qf='%{name}' --enablerepo=fedora-source --enablerepo=updates-source
--enablerepo=updates-testing-source --archlist=src --whatrequires
'go-rpm-macros'
</pre>
<pre>
Omitted due to the number of packages listed ~1100.
</pre>
Not all of listed require re-build as they might not ship binaries
and/or do not use golang compiler during build, but only use Go rpm
macros that pull it in to every build root.
== Contingency Plan ==
* Contingency mechanism:Reverting to golang version 1.13.X if
significatnt issues are discovered.
* Contingency deadline: Beta Freeze(?)
* Blocks release? No
* Blocks product? No
== Documentation ==
https://tip.golang.org/doc/go1.14
--
Ben Cotton
He / Him / His
Fedora Program Manager
Red Hat
TZ=America/Indiana/Indianapolis
4 years, 3 months
wdune/white is available for fedora 32
by J. Scheurich
Hi,
After 13 months, wdune/white_dune is avaliable for fedora 32 8-)
I want to say thanks for anyońe, who gave tips, especially Petr Menšík
(the reviewer) and
Robert-André Mauchin (the sponsor).
so long
MUFTI
4 years, 3 months