CentOS Errata and Security Advisory 2019:4205 Important
Upstream details at : https://access.redhat.com/errata/RHSA-2019:4205
The following updated files have been uploaded and are currently
syncing to the mirrors: ( sha256sum Filename )
i386:
0cc0551f89a664502e3e8caf219aa589efbd8b567e0a5b6f503d2ffe56f43e26 thunderbird-68.3.0-3.el6.centos.i686.rpm
x86_64:
1a150c3f18980ecc2cd797f0a40a630f88ecfd0eaad1214d9b479317f934515f thunderbird-68.3.0-3.el6.centos.x86_64.rpm
Source:
b0e17df5d12434a926c2bc87d5bd141cb601b74bdb67591043af0179236395e8 thunderbird-68.3.0-3.el6.centos.src.rpm
--
Johnny Hughes
CentOS Project { http://www.centos.org/ }
irc: hughesjr, #centos@irc.freenode.net
Twitter: @JohnnyCentOS
_______________________________________________
CentOS-announce mailing list
CentOS-announce@centos.org
https://lists.centos.org/mailman/listinfo/centos-announce
Tuesday, December 24, 2019
Monday, December 23, 2019
List of long term FTBFS packages to be retired in February
Dear maintainers.
Based on the latest fail to build from source policy, the following packages
will be retired from Fedora 32 approximately one week before branching (February
2020).
Policy:
https://docs.fedoraproject.org/en-US/fesco/Fails_to_build_from_source_Fails_to_install/
The packages in rawhide were not successfully built at least since Fedora 30.
This report is based on dist tags.
Packages collected via:
https://github.com/hroncok/fedora-report-ftbfs-retirements/blob/master/ftbfs-retirements.ipynb
If you see a package that was built, please let me know.
If you see a package that should be exempted from the process, please let me
know and we can work together to get a FESCo approval for that.
If you see a package that can be rebuilt, please do so.
Package (co)maintainers Latest build
================================================================================
elasticsearch hubbitus, jvanek, lbazan, Fedora 24
zbyszek
expresso jamielinux, nodejs-sig, Fedora 28
patches
libocrdma ocrdma Fedora 27
nuvola-app-google-calendar martinkg Fedora 29
nuvola-app-groove martinkg Fedora 28
nuvola-app-logitech-media- martinkg Fedora 29
server
nuvola-app-plex martinkg Fedora 29
nuvola-app-soundcloud martinkg Fedora 29
nuvola-app-yandex-music martinkg Fedora 29
shim-unsigned-aarch64 pjones Fedora 28
shim-unsigned-x64 pjones Fedora 28
The following packages require above mentioned packages:
Depending on: expresso (1)
nodejs-chrono (maintained by: jamielinux, nodejs-sig, tomh)
nodejs-chrono-1.0.5-10.fc31.src requires npm(expresso) = 0.9.2
Affected (co)maintainers
hubbitus: elasticsearch
jamielinux: expresso
jvanek: elasticsearch
lbazan: elasticsearch
martinkg: nuvola-app-logitech-media-server, nuvola-app-plex, nuvola-app-groove,
nuvola-app-google-calendar, nuvola-app-soundcloud, nuvola-app-yandex-music
nodejs-sig: expresso
ocrdma: libocrdma
patches: expresso
pjones: shim-unsigned-aarch64, shim-unsigned-x64
tomh: expresso
zbyszek: elasticsearch
--
Miro Hrončok
--
Phone: +420777974800
IRC: mhroncok
_______________________________________________
devel-announce mailing list -- devel-announce@lists.fedoraproject.org
To unsubscribe send an email to devel-announce-leave@lists.fedoraproject.org
Fedora Code of Conduct: https://docs.fedoraproject.org/en-US/project/code-of-conduct/
List Guidelines: https://fedoraproject.org/wiki/Mailing_list_guidelines
List Archives: https://lists.fedoraproject.org/archives/list/devel-announce@lists.fedoraproject.org
Based on the latest fail to build from source policy, the following packages
will be retired from Fedora 32 approximately one week before branching (February
2020).
Policy:
https://docs.fedoraproject.org/en-US/fesco/Fails_to_build_from_source_Fails_to_install/
The packages in rawhide were not successfully built at least since Fedora 30.
This report is based on dist tags.
Packages collected via:
https://github.com/hroncok/fedora-report-ftbfs-retirements/blob/master/ftbfs-retirements.ipynb
If you see a package that was built, please let me know.
If you see a package that should be exempted from the process, please let me
know and we can work together to get a FESCo approval for that.
If you see a package that can be rebuilt, please do so.
Package (co)maintainers Latest build
================================================================================
elasticsearch hubbitus, jvanek, lbazan, Fedora 24
zbyszek
expresso jamielinux, nodejs-sig, Fedora 28
patches
libocrdma ocrdma Fedora 27
nuvola-app-google-calendar martinkg Fedora 29
nuvola-app-groove martinkg Fedora 28
nuvola-app-logitech-media- martinkg Fedora 29
server
nuvola-app-plex martinkg Fedora 29
nuvola-app-soundcloud martinkg Fedora 29
nuvola-app-yandex-music martinkg Fedora 29
shim-unsigned-aarch64 pjones Fedora 28
shim-unsigned-x64 pjones Fedora 28
The following packages require above mentioned packages:
Depending on: expresso (1)
nodejs-chrono (maintained by: jamielinux, nodejs-sig, tomh)
nodejs-chrono-1.0.5-10.fc31.src requires npm(expresso) = 0.9.2
Affected (co)maintainers
hubbitus: elasticsearch
jamielinux: expresso
jvanek: elasticsearch
lbazan: elasticsearch
martinkg: nuvola-app-logitech-media-server, nuvola-app-plex, nuvola-app-groove,
nuvola-app-google-calendar, nuvola-app-soundcloud, nuvola-app-yandex-music
nodejs-sig: expresso
ocrdma: libocrdma
patches: expresso
pjones: shim-unsigned-aarch64, shim-unsigned-x64
tomh: expresso
zbyszek: elasticsearch
--
Miro Hrončok
--
Phone: +420777974800
IRC: mhroncok
_______________________________________________
devel-announce mailing list -- devel-announce@lists.fedoraproject.org
To unsubscribe send an email to devel-announce-leave@lists.fedoraproject.org
Fedora Code of Conduct: https://docs.fedoraproject.org/en-US/project/code-of-conduct/
List Guidelines: https://fedoraproject.org/wiki/Mailing_list_guidelines
List Archives: https://lists.fedoraproject.org/archives/list/devel-announce@lists.fedoraproject.org
Orphaned packages looking for new maintainers
The following packages are orphaned and will be retired when they
are orphaned for six weeks, unless someone adopts them. If you know for sure
that the package should be retired, please do so now with a proper reason:
https://fedoraproject.org/wiki/How_to_remove_a_package_at_end_of_life
Note: If you received this mail directly you (co)maintain one of the affected
packages or a package that depends on one. Please adopt the affected package or
retire your depending package to avoid broken dependencies, otherwise your
package will be retired when the affected package gets retired.
Request package ownership via the *Take* button in he left column on
https://src.fedoraproject.org/rpms/<pkgname>
Full report available at:
https://churchyard.fedorapeople.org/orphans-2019-12-23.txt
grep it for your FAS username and follow the dependency chain.
Package (co)maintainers Status Change
================================================================================
ExchangeIR orphan 5 weeks ago
MochiKit orphan 1 weeks ago
apache-logging-parent mizdebsk, orphan 5 weeks ago
apachetop orphan, robert 1 weeks ago
apt-cacher-ng orphan 5 weeks ago
archaius orphan 5 weeks ago
archmage lbazan, orphan 4 weeks ago
audit-viewer mitr, orphan 4 weeks ago
avalon-logkit jerboaa, mizdebsk, orphan 4 weeks ago
binclock lbalhar, orphan 1 weeks ago
buildnumber-maven-plugin orphan 4 weeks ago
camotics orphan 5 weeks ago
cduce orphan 5 weeks ago
clapham orphan 5 weeks ago
csstidy orphan 5 weeks ago
delve go-sig, orphan 5 weeks ago
dzen2 bstinson, dcantrel, fale, 3 weeks ago
lupinix, orphan
eclipse-anyedit eclipse-sig, orphan, swagiaal 5 weeks ago
eclipse-checkstyle akurtakov, eclipse-sig, orphan 5 weeks ago
eclipse-color-theme eclipse-sig, orphan 5 weeks ago
eclipse-dltk akurtakov, eclipse-sig, 5 weeks ago
kdaniel, orphan, rgrunber
eclipse-epic eclipse-sig, orphan 5 weeks ago
eclipse-m2e-antlr eclipse-sig, mizdebsk, orphan 5 weeks ago
eclipse-m2e-cxf eclipse-sig, mizdebsk, orphan 5 weeks ago
eclipse-m2e-maven-dependency- mizdebsk, orphan 5 weeks ago
plugin
eclipse-m2e-modello eclipse-sig, mizdebsk, orphan 5 weeks ago
eclipse-m2e-plexus eclipse-sig, mizdebsk, orphan 5 weeks ago
eclipse-m2e-sisu eclipse-sig, mizdebsk, orphan 5 weeks ago
eclipse-m2e-takari mizdebsk, orphan 5 weeks ago
eclipse-nls orphan 5 weeks ago
eclipse-pdt eclipse-sig, orphan 5 weeks ago
eclipse-quickrex eclipse-sig, orphan 5 weeks ago
eclipse-sgx orphan 5 weeks ago
exercism go-sig, orphan 0 weeks ago
fabric orphan 5 weeks ago
ferm orphan, slankes 5 weeks ago
giis orphan 5 weeks ago
gipfel orphan 5 weeks ago
glob2 cheese, orphan 5 weeks ago
glusterd2 kkeithle, orphan 5 weeks ago
gns3-gui orphan 5 weeks ago
gns3-net-converter orphan 5 weeks ago
gns3-server orphan 5 weeks ago
golang-github-10gen-openssl go-sig, jchaloup, mskalick, 5 weeks ago
orphan
golang-github-codahale- go-sig, orphan 0 weeks ago
aesnicheck
graphite-web jamielinux, orphan, piotrp 5 weeks ago
guestfs-browser orphan 5 weeks ago
hystrix orphan 4 weeks ago
i3-ipc cicku, fale, gchamoul, 3 weeks ago
lupinix, mpreisle, orphan
ike-scan orphan, pwouters 1 weeks ago
infinispan gil, orphan 3 weeks ago
ioprocess dougsland, nsoffer, orphan, 5 weeks ago
smizrahi
jackson mizdebsk, orphan 5 weeks ago
jandex orphan 5 weeks ago
jboss-transaction-1.1-api orphan 5 weeks ago
jdo-api gil, lef, moceap, orphan 5 weeks ago
jgraphx jerboaa, orphan 0 weeks ago
jhdf5 orphan, zbyszek 0 weeks ago
jogl2 orphan 5 weeks ago
jove orphan 5 weeks ago
libee mbartos, orphan 4 weeks ago
libgovirt orphan 5 weeks ago
libx86 jcpunk, orphan 5 weeks ago
lv2-abGate orphan 5 weeks ago
lv2-kn0ck0ut orphan 5 weeks ago
matio lupinix, orphan 0 weeks ago
maven-ant-plugin mizdebsk, orphan 2 weeks ago
maven-checkstyle-plugin lef, mizdebsk, orphan 5 weeks ago
maven-deploy-plugin orphan 4 weeks ago
maven-docck-plugin mizdebsk, orphan 2 weeks ago
maven-ear-plugin orphan 2 weeks ago
maven-eclipse-plugin orphan 5 weeks ago
maven-war-plugin mizdebsk, orphan 4 weeks ago
mcollective-qpid-plugin orphan, tdawson 1 weeks ago
memoryfilesystem orphan 4 weeks ago
multibit-commons orphan 5 weeks ago
multibit-hardware orphan 5 weeks ago
multithreadedtc orphan 2 weeks ago
nbtscan orphan 1 weeks ago
nesc cicku, orphan 2 weeks ago
ninvaders orphan 1 weeks ago
nm-tray lxqt-sig, orphan 5 weeks ago
nodejs-buffertools nodejs-sig, orphan 5 weeks ago
nodejs-compressible nodejs-sig, orphan, patches 5 weeks ago
nodejs-encodeurl nodejs-sig, orphan 5 weeks ago
nodejs-eyes nodejs-sig, orphan, patches 5 weeks ago
nodejs-finalhandler nodejs-sig, orphan 5 weeks ago
nodejs-method-override nodejs-sig, orphan, patches 5 weeks ago
nodejs-moment nodejs-sig, orphan, patches 5 weeks ago
nodejs-negotiator nodejs-sig, orphan, patches 5 weeks ago
nodejs-send nodejs-sig, orphan, patches 5 weeks ago
nodejs-stylus nodejs-sig, orphan, patches 5 weeks ago
nodejs-tilejson jamielinux, nodejs-sig, orphan 5 weeks ago
nodejs-tilelive jamielinux, nodejs-sig, orphan 5 weeks ago
ocaml-bin-prot orphan 5 weeks ago
ocaml-bisect orphan 5 weeks ago
ocaml-bitstring orphan 5 weeks ago
ocaml-deriving orphan 5 weeks ago
ocaml-json-static orphan 5 weeks ago
ocaml-mikmatch orphan 5 weeks ago
ocaml-openin orphan 5 weeks ago
ocaml-pa-monad orphan 5 weeks ago
ocaml-pgocaml orphan 5 weeks ago
ocaml-sexplib orphan 5 weeks ago
ocaml-type-conv orphan 5 weeks ago
ocamldsort orphan 5 weeks ago
ohc acaringi, hhorak, orphan 4 weeks ago
oyranos orphan 1 weeks ago
paulstretch orphan 5 weeks ago
perdition orphan 5 weeks ago
pscan orphan 1 weeks ago
python-alchimia orphan 5 weeks ago
python-cattrs orphan 5 weeks ago
python-dockerpty carlwgeorge, lsm5, orphan, 1 weeks ago
ttomecek
python-flask-classy orphan 3 weeks ago
python-flask-debugtoolbar orphan 3 weeks ago
python-fsmonitor orphan 3 weeks ago
python-gfm orphan 5 weeks ago
python-k8sclient orphan 5 weeks ago
python-mongoengine bowlofeggs, echevemaster, 3 weeks ago
orphan
python-nose-ignore-docstring orphan 4 weeks ago
python-sanic orphan 5 weeks ago
python-texttable carlwgeorge, orphan 1 weeks ago
python-virtkey orphan 1 weeks ago
python-zipstream orphan 5 weeks ago
qpid-proton orphan 0 weeks ago
resiprocate orphan 5 weeks ago
rgbds orphan 5 weeks ago
rubygem-awesome_spawn jstribny, orphan 2 weeks ago
rubygem-bootstrap-sass orphan 2 weeks ago
rubygem-charlock_holmes orphan 2 weeks ago
rubygem-omniauth orphan 1 weeks ago
rubygem-orm_adapter orphan 2 weeks ago
saxon dbhole, dchen, jjohnstn, 3 weeks ago
mbooth, orphan
scamper orphan 5 weeks ago
shed orphan 1 weeks ago
sonatype-plugins-parent mizdebsk, orphan 5 weeks ago
swt-chart orphan 5 weeks ago
tmuxinator orphan 1 weeks ago
trac-doxygen-plugin orphan 5 weeks ago
trac-xmlrpc-plugin orphan 5 weeks ago
vttest cicku, orphan 1 weeks ago
xml-stylebook mizdebsk, orphan 3 weeks ago
zookeeper ctubbsii, greghellings, 5 weeks ago
mluscon, orphan, skottler
The following packages require above mentioned packages:
See https://churchyard.fedorapeople.org/orphans-2019-12-23.txt
Grep it for your username and follow the dependency chain.
Affected (co)maintainers
abompard: qpid-proton
acaringi: ohc
agoode: matio
akurtakov: eclipse-dltk, buildnumber-maven-plugin, eclipse-checkstyle
arobinso: multithreadedtc
ausil: qpid-proton
berrange: libgovirt
bgilbert: matio
bkabrda: qpid-proton
bowlofeggs: qpid-proton, python-mongoengine
bstinson: dzen2
carlwgeorge: python-dockerpty, python-texttable
cheese: glob2
churchyard: nodejs-moment
cicku: vttest, i3-ipc, nesc
clalance: buildnumber-maven-plugin
cqi: qpid-proton
cquad: buildnumber-maven-plugin
crobinso: libgovirt
ctubbsii: zookeeper
cverna: qpid-proton
dbhole: saxon
dcantrel: dzen2
dchen: saxon
dgoodwin: qpid-proton
dmach: qpid-proton
dodji: qpid-proton
domcleal: buildnumber-maven-plugin
dominik: jackson
dougsland: ioprocess
dridi: vttest
echevemaster: python-mongoengine
eclipse-sig: eclipse-m2e-antlr, eclipse-checkstyle, eclipse-anyedit,
eclipse-dltk, eclipse-m2e-cxf, eclipse-m2e-modello, eclipse-m2e-sisu,
eclipse-quickrex, eclipse-m2e-plexus, eclipse-epic, eclipse-pdt, eclipse-color-theme
ellert: maven-deploy-plugin, maven-docck-plugin
elmarco: libgovirt
error: python-dockerpty, python-texttable
fab: vttest, avalon-logkit
fale: dzen2, i3-ipc
fidencio: libgovirt
frixxon: qpid-proton
frostyx: qpid-proton
fsimonce: jackson
fujiwara: qpid-proton
gchamoul: i3-ipc
ggillies: buildnumber-maven-plugin
gil: infinispan, jdo-api
go-sig: exercism, golang-github-10gen-openssl, delve,
golang-github-codahale-aesnicheck
greghellings: zookeeper
halfie: qpid-proton
hhorak: ohc
infra-sig: qpid-proton
ingvar: vttest
irina: qpid-proton
jackorp: buildnumber-maven-plugin
jamesturner246: matio, avalon-logkit, jogl2, saxon, jgraphx
jamielinux: nodejs-encodeurl, nodejs-finalhandler, graphite-web,
nodejs-tilelive, nodejs-eyes, nodejs-tilejson, nodejs-negotiator
jaruga: buildnumber-maven-plugin
jchaloup: golang-github-10gen-openssl
jcline: qpid-proton
jcpunk: libx86
jerboaa: avalon-logkit, jgraphx
jfearn: avalon-logkit
jjelen: buildnumber-maven-plugin, avalon-logkit
jjohnstn: saxon
jlieskov: qpid-proton
jortel: qpid-proton
jplesnik: qpid-proton
jsmith: nodejs-encodeurl, nodejs-finalhandler, nodejs-buffertools,
nodejs-moment, nodejs-eyes
jsteffan: vttest
jstribny: buildnumber-maven-plugin, rubygem-awesome_spawn
jvanek: buildnumber-maven-plugin
jvymazal: qpid-proton
kdaniel: eclipse-dltk, buildnumber-maven-plugin
kellin: qpid-proton
kevin: qpid-proton, vttest
kgiusti: qpid-proton
kkeithle: glusterd2
lbalhar: binclock
lbazan: archmage
leamas: qpid-proton
lef: jdo-api, maven-checkstyle-plugin, buildnumber-maven-plugin,
multithreadedtc, jandex
limb: matio
lkundrak: qpid-proton, buildnumber-maven-plugin
lsedlar: qpid-proton
lsm5: python-dockerpty, python-texttable
luhliarik: vttest
lupinix: dzen2, i3-ipc, matio
lxqt-sig: nm-tray
lzap: buildnumber-maven-plugin
maxamillion: qpid-proton
mbartos: libee
mbooth: saxon
mdarade: qpid-proton
mhlavink: vttest
mikem: qpid-proton
mikep: matio
mildew: qpid-proton
mitr: audit-viewer
mizdebsk: apache-logging-parent, maven-war-plugin, eclipse-m2e-antlr,
avalon-logkit, maven-ant-plugin, eclipse-m2e-cxf, eclipse-m2e-modello,
eclipse-m2e-sisu, eclipse-m2e-takari, eclipse-m2e-maven-dependency-plugin,
jackson, maven-checkstyle-plugin, xml-stylebook, maven-docck-plugin,
eclipse-m2e-plexus, sonatype-plugins-parent
mluscon: zookeeper
mmagr: buildnumber-maven-plugin
mmorsi: buildnumber-maven-plugin
moceap: jdo-api, avalon-logkit
mohanboddu: qpid-proton
mpreisle: i3-ipc
mskalick: golang-github-10gen-openssl, avalon-logkit
msrb: buildnumber-maven-plugin
neuro-sig: jhdf5, matio
ngompa: qpid-proton
nim: qpid-proton
nodejs-sig: nodejs-compressible, nodejs-encodeurl, nodejs-method-override,
nodejs-finalhandler, nodejs-stylus, nodejs-buffertools, nodejs-moment,
nodejs-send, nodejs-tilelive, nodejs-eyes, nodejs-tilejson, nodejs-negotiator
nsoffer: ioprocess
odubaj: jandex
onosek: qpid-proton
orion: qpid-proton, matio, avalon-logkit
panovotn: avalon-logkit
patches: nodejs-method-override, nodejs-compressible, nodejs-stylus,
nodejs-encodeurl, nodejs-finalhandler, nodejs-moment, nodejs-send, nodejs-eyes,
nodejs-negotiator
peter: avalon-logkit
pingou: qpid-proton
piotrp: graphite-web, nodejs-eyes
pmackinn: jdo-api
ppisar: qpid-proton
puiterwijk: qpid-proton
pvalena: buildnumber-maven-plugin
pwouters: ike-scan
python-sig: nodejs-moment
qwan: qpid-proton
ralph: qpid-proton
rgrunber: eclipse-dltk
rlandmann: avalon-logkit
robert: apachetop
romanofski: qpid-proton
rsroka: qpid-proton
ruben: vttest
ruby-packagers-sig: buildnumber-maven-plugin
s4504kr: avalon-logkit
sagitter: matio, avalon-logkit
santiago: qpid-proton
sbonazzo: buildnumber-maven-plugin
sgallagh: python-texttable
sinnykumari: qpid-proton
skottler: zookeeper, buildnumber-maven-plugin
slaanesh: matio
slankes: ferm
smizrahi: ioprocess
sochotni: qpid-proton
stahnma: buildnumber-maven-plugin
stevetraylen: buildnumber-maven-plugin
swagiaal: eclipse-anyedit
tagoh: qpid-proton
tc01: nodejs-eyes
tdawson: qpid-proton, buildnumber-maven-plugin, mcollective-qpid-plugin
terjeros: buildnumber-maven-plugin
teuf: libgovirt
tomh: nodejs-send, nodejs-eyes, nodejs-encodeurl, nodejs-finalhandler
tosykora: qpid-proton
tross: qpid-proton
ttomecek: qpid-proton, python-dockerpty, python-texttable
twaugh: qpid-proton
valtri: buildnumber-maven-plugin
victortoso: libgovirt
virtmaint-sig: libgovirt
volter: matio
vondruch: buildnumber-maven-plugin
vrutkovs: qpid-proton
wakko666: buildnumber-maven-plugin
wwoods: qpid-proton
xaeth: vttest
xiubli: qpid-proton
zbyszek: jhdf5
--
The script creating this output is run and developed by Fedora
Release Engineering. Please report issues at its pagure instance:
https://pagure.io/releng/
The sources of this script can be found at:
https://pagure.io/releng/blob/master/f/scripts/find_unblocked_orphans.py
_______________________________________________
devel-announce mailing list -- devel-announce@lists.fedoraproject.org
To unsubscribe send an email to devel-announce-leave@lists.fedoraproject.org
Fedora Code of Conduct: https://docs.fedoraproject.org/en-US/project/code-of-conduct/
List Guidelines: https://fedoraproject.org/wiki/Mailing_list_guidelines
List Archives: https://lists.fedoraproject.org/archives/list/devel-announce@lists.fedoraproject.org
are orphaned for six weeks, unless someone adopts them. If you know for sure
that the package should be retired, please do so now with a proper reason:
https://fedoraproject.org/wiki/How_to_remove_a_package_at_end_of_life
Note: If you received this mail directly you (co)maintain one of the affected
packages or a package that depends on one. Please adopt the affected package or
retire your depending package to avoid broken dependencies, otherwise your
package will be retired when the affected package gets retired.
Request package ownership via the *Take* button in he left column on
https://src.fedoraproject.org/rpms/<pkgname>
Full report available at:
https://churchyard.fedorapeople.org/orphans-2019-12-23.txt
grep it for your FAS username and follow the dependency chain.
Package (co)maintainers Status Change
================================================================================
ExchangeIR orphan 5 weeks ago
MochiKit orphan 1 weeks ago
apache-logging-parent mizdebsk, orphan 5 weeks ago
apachetop orphan, robert 1 weeks ago
apt-cacher-ng orphan 5 weeks ago
archaius orphan 5 weeks ago
archmage lbazan, orphan 4 weeks ago
audit-viewer mitr, orphan 4 weeks ago
avalon-logkit jerboaa, mizdebsk, orphan 4 weeks ago
binclock lbalhar, orphan 1 weeks ago
buildnumber-maven-plugin orphan 4 weeks ago
camotics orphan 5 weeks ago
cduce orphan 5 weeks ago
clapham orphan 5 weeks ago
csstidy orphan 5 weeks ago
delve go-sig, orphan 5 weeks ago
dzen2 bstinson, dcantrel, fale, 3 weeks ago
lupinix, orphan
eclipse-anyedit eclipse-sig, orphan, swagiaal 5 weeks ago
eclipse-checkstyle akurtakov, eclipse-sig, orphan 5 weeks ago
eclipse-color-theme eclipse-sig, orphan 5 weeks ago
eclipse-dltk akurtakov, eclipse-sig, 5 weeks ago
kdaniel, orphan, rgrunber
eclipse-epic eclipse-sig, orphan 5 weeks ago
eclipse-m2e-antlr eclipse-sig, mizdebsk, orphan 5 weeks ago
eclipse-m2e-cxf eclipse-sig, mizdebsk, orphan 5 weeks ago
eclipse-m2e-maven-dependency- mizdebsk, orphan 5 weeks ago
plugin
eclipse-m2e-modello eclipse-sig, mizdebsk, orphan 5 weeks ago
eclipse-m2e-plexus eclipse-sig, mizdebsk, orphan 5 weeks ago
eclipse-m2e-sisu eclipse-sig, mizdebsk, orphan 5 weeks ago
eclipse-m2e-takari mizdebsk, orphan 5 weeks ago
eclipse-nls orphan 5 weeks ago
eclipse-pdt eclipse-sig, orphan 5 weeks ago
eclipse-quickrex eclipse-sig, orphan 5 weeks ago
eclipse-sgx orphan 5 weeks ago
exercism go-sig, orphan 0 weeks ago
fabric orphan 5 weeks ago
ferm orphan, slankes 5 weeks ago
giis orphan 5 weeks ago
gipfel orphan 5 weeks ago
glob2 cheese, orphan 5 weeks ago
glusterd2 kkeithle, orphan 5 weeks ago
gns3-gui orphan 5 weeks ago
gns3-net-converter orphan 5 weeks ago
gns3-server orphan 5 weeks ago
golang-github-10gen-openssl go-sig, jchaloup, mskalick, 5 weeks ago
orphan
golang-github-codahale- go-sig, orphan 0 weeks ago
aesnicheck
graphite-web jamielinux, orphan, piotrp 5 weeks ago
guestfs-browser orphan 5 weeks ago
hystrix orphan 4 weeks ago
i3-ipc cicku, fale, gchamoul, 3 weeks ago
lupinix, mpreisle, orphan
ike-scan orphan, pwouters 1 weeks ago
infinispan gil, orphan 3 weeks ago
ioprocess dougsland, nsoffer, orphan, 5 weeks ago
smizrahi
jackson mizdebsk, orphan 5 weeks ago
jandex orphan 5 weeks ago
jboss-transaction-1.1-api orphan 5 weeks ago
jdo-api gil, lef, moceap, orphan 5 weeks ago
jgraphx jerboaa, orphan 0 weeks ago
jhdf5 orphan, zbyszek 0 weeks ago
jogl2 orphan 5 weeks ago
jove orphan 5 weeks ago
libee mbartos, orphan 4 weeks ago
libgovirt orphan 5 weeks ago
libx86 jcpunk, orphan 5 weeks ago
lv2-abGate orphan 5 weeks ago
lv2-kn0ck0ut orphan 5 weeks ago
matio lupinix, orphan 0 weeks ago
maven-ant-plugin mizdebsk, orphan 2 weeks ago
maven-checkstyle-plugin lef, mizdebsk, orphan 5 weeks ago
maven-deploy-plugin orphan 4 weeks ago
maven-docck-plugin mizdebsk, orphan 2 weeks ago
maven-ear-plugin orphan 2 weeks ago
maven-eclipse-plugin orphan 5 weeks ago
maven-war-plugin mizdebsk, orphan 4 weeks ago
mcollective-qpid-plugin orphan, tdawson 1 weeks ago
memoryfilesystem orphan 4 weeks ago
multibit-commons orphan 5 weeks ago
multibit-hardware orphan 5 weeks ago
multithreadedtc orphan 2 weeks ago
nbtscan orphan 1 weeks ago
nesc cicku, orphan 2 weeks ago
ninvaders orphan 1 weeks ago
nm-tray lxqt-sig, orphan 5 weeks ago
nodejs-buffertools nodejs-sig, orphan 5 weeks ago
nodejs-compressible nodejs-sig, orphan, patches 5 weeks ago
nodejs-encodeurl nodejs-sig, orphan 5 weeks ago
nodejs-eyes nodejs-sig, orphan, patches 5 weeks ago
nodejs-finalhandler nodejs-sig, orphan 5 weeks ago
nodejs-method-override nodejs-sig, orphan, patches 5 weeks ago
nodejs-moment nodejs-sig, orphan, patches 5 weeks ago
nodejs-negotiator nodejs-sig, orphan, patches 5 weeks ago
nodejs-send nodejs-sig, orphan, patches 5 weeks ago
nodejs-stylus nodejs-sig, orphan, patches 5 weeks ago
nodejs-tilejson jamielinux, nodejs-sig, orphan 5 weeks ago
nodejs-tilelive jamielinux, nodejs-sig, orphan 5 weeks ago
ocaml-bin-prot orphan 5 weeks ago
ocaml-bisect orphan 5 weeks ago
ocaml-bitstring orphan 5 weeks ago
ocaml-deriving orphan 5 weeks ago
ocaml-json-static orphan 5 weeks ago
ocaml-mikmatch orphan 5 weeks ago
ocaml-openin orphan 5 weeks ago
ocaml-pa-monad orphan 5 weeks ago
ocaml-pgocaml orphan 5 weeks ago
ocaml-sexplib orphan 5 weeks ago
ocaml-type-conv orphan 5 weeks ago
ocamldsort orphan 5 weeks ago
ohc acaringi, hhorak, orphan 4 weeks ago
oyranos orphan 1 weeks ago
paulstretch orphan 5 weeks ago
perdition orphan 5 weeks ago
pscan orphan 1 weeks ago
python-alchimia orphan 5 weeks ago
python-cattrs orphan 5 weeks ago
python-dockerpty carlwgeorge, lsm5, orphan, 1 weeks ago
ttomecek
python-flask-classy orphan 3 weeks ago
python-flask-debugtoolbar orphan 3 weeks ago
python-fsmonitor orphan 3 weeks ago
python-gfm orphan 5 weeks ago
python-k8sclient orphan 5 weeks ago
python-mongoengine bowlofeggs, echevemaster, 3 weeks ago
orphan
python-nose-ignore-docstring orphan 4 weeks ago
python-sanic orphan 5 weeks ago
python-texttable carlwgeorge, orphan 1 weeks ago
python-virtkey orphan 1 weeks ago
python-zipstream orphan 5 weeks ago
qpid-proton orphan 0 weeks ago
resiprocate orphan 5 weeks ago
rgbds orphan 5 weeks ago
rubygem-awesome_spawn jstribny, orphan 2 weeks ago
rubygem-bootstrap-sass orphan 2 weeks ago
rubygem-charlock_holmes orphan 2 weeks ago
rubygem-omniauth orphan 1 weeks ago
rubygem-orm_adapter orphan 2 weeks ago
saxon dbhole, dchen, jjohnstn, 3 weeks ago
mbooth, orphan
scamper orphan 5 weeks ago
shed orphan 1 weeks ago
sonatype-plugins-parent mizdebsk, orphan 5 weeks ago
swt-chart orphan 5 weeks ago
tmuxinator orphan 1 weeks ago
trac-doxygen-plugin orphan 5 weeks ago
trac-xmlrpc-plugin orphan 5 weeks ago
vttest cicku, orphan 1 weeks ago
xml-stylebook mizdebsk, orphan 3 weeks ago
zookeeper ctubbsii, greghellings, 5 weeks ago
mluscon, orphan, skottler
The following packages require above mentioned packages:
See https://churchyard.fedorapeople.org/orphans-2019-12-23.txt
Grep it for your username and follow the dependency chain.
Affected (co)maintainers
abompard: qpid-proton
acaringi: ohc
agoode: matio
akurtakov: eclipse-dltk, buildnumber-maven-plugin, eclipse-checkstyle
arobinso: multithreadedtc
ausil: qpid-proton
berrange: libgovirt
bgilbert: matio
bkabrda: qpid-proton
bowlofeggs: qpid-proton, python-mongoengine
bstinson: dzen2
carlwgeorge: python-dockerpty, python-texttable
cheese: glob2
churchyard: nodejs-moment
cicku: vttest, i3-ipc, nesc
clalance: buildnumber-maven-plugin
cqi: qpid-proton
cquad: buildnumber-maven-plugin
crobinso: libgovirt
ctubbsii: zookeeper
cverna: qpid-proton
dbhole: saxon
dcantrel: dzen2
dchen: saxon
dgoodwin: qpid-proton
dmach: qpid-proton
dodji: qpid-proton
domcleal: buildnumber-maven-plugin
dominik: jackson
dougsland: ioprocess
dridi: vttest
echevemaster: python-mongoengine
eclipse-sig: eclipse-m2e-antlr, eclipse-checkstyle, eclipse-anyedit,
eclipse-dltk, eclipse-m2e-cxf, eclipse-m2e-modello, eclipse-m2e-sisu,
eclipse-quickrex, eclipse-m2e-plexus, eclipse-epic, eclipse-pdt, eclipse-color-theme
ellert: maven-deploy-plugin, maven-docck-plugin
elmarco: libgovirt
error: python-dockerpty, python-texttable
fab: vttest, avalon-logkit
fale: dzen2, i3-ipc
fidencio: libgovirt
frixxon: qpid-proton
frostyx: qpid-proton
fsimonce: jackson
fujiwara: qpid-proton
gchamoul: i3-ipc
ggillies: buildnumber-maven-plugin
gil: infinispan, jdo-api
go-sig: exercism, golang-github-10gen-openssl, delve,
golang-github-codahale-aesnicheck
greghellings: zookeeper
halfie: qpid-proton
hhorak: ohc
infra-sig: qpid-proton
ingvar: vttest
irina: qpid-proton
jackorp: buildnumber-maven-plugin
jamesturner246: matio, avalon-logkit, jogl2, saxon, jgraphx
jamielinux: nodejs-encodeurl, nodejs-finalhandler, graphite-web,
nodejs-tilelive, nodejs-eyes, nodejs-tilejson, nodejs-negotiator
jaruga: buildnumber-maven-plugin
jchaloup: golang-github-10gen-openssl
jcline: qpid-proton
jcpunk: libx86
jerboaa: avalon-logkit, jgraphx
jfearn: avalon-logkit
jjelen: buildnumber-maven-plugin, avalon-logkit
jjohnstn: saxon
jlieskov: qpid-proton
jortel: qpid-proton
jplesnik: qpid-proton
jsmith: nodejs-encodeurl, nodejs-finalhandler, nodejs-buffertools,
nodejs-moment, nodejs-eyes
jsteffan: vttest
jstribny: buildnumber-maven-plugin, rubygem-awesome_spawn
jvanek: buildnumber-maven-plugin
jvymazal: qpid-proton
kdaniel: eclipse-dltk, buildnumber-maven-plugin
kellin: qpid-proton
kevin: qpid-proton, vttest
kgiusti: qpid-proton
kkeithle: glusterd2
lbalhar: binclock
lbazan: archmage
leamas: qpid-proton
lef: jdo-api, maven-checkstyle-plugin, buildnumber-maven-plugin,
multithreadedtc, jandex
limb: matio
lkundrak: qpid-proton, buildnumber-maven-plugin
lsedlar: qpid-proton
lsm5: python-dockerpty, python-texttable
luhliarik: vttest
lupinix: dzen2, i3-ipc, matio
lxqt-sig: nm-tray
lzap: buildnumber-maven-plugin
maxamillion: qpid-proton
mbartos: libee
mbooth: saxon
mdarade: qpid-proton
mhlavink: vttest
mikem: qpid-proton
mikep: matio
mildew: qpid-proton
mitr: audit-viewer
mizdebsk: apache-logging-parent, maven-war-plugin, eclipse-m2e-antlr,
avalon-logkit, maven-ant-plugin, eclipse-m2e-cxf, eclipse-m2e-modello,
eclipse-m2e-sisu, eclipse-m2e-takari, eclipse-m2e-maven-dependency-plugin,
jackson, maven-checkstyle-plugin, xml-stylebook, maven-docck-plugin,
eclipse-m2e-plexus, sonatype-plugins-parent
mluscon: zookeeper
mmagr: buildnumber-maven-plugin
mmorsi: buildnumber-maven-plugin
moceap: jdo-api, avalon-logkit
mohanboddu: qpid-proton
mpreisle: i3-ipc
mskalick: golang-github-10gen-openssl, avalon-logkit
msrb: buildnumber-maven-plugin
neuro-sig: jhdf5, matio
ngompa: qpid-proton
nim: qpid-proton
nodejs-sig: nodejs-compressible, nodejs-encodeurl, nodejs-method-override,
nodejs-finalhandler, nodejs-stylus, nodejs-buffertools, nodejs-moment,
nodejs-send, nodejs-tilelive, nodejs-eyes, nodejs-tilejson, nodejs-negotiator
nsoffer: ioprocess
odubaj: jandex
onosek: qpid-proton
orion: qpid-proton, matio, avalon-logkit
panovotn: avalon-logkit
patches: nodejs-method-override, nodejs-compressible, nodejs-stylus,
nodejs-encodeurl, nodejs-finalhandler, nodejs-moment, nodejs-send, nodejs-eyes,
nodejs-negotiator
peter: avalon-logkit
pingou: qpid-proton
piotrp: graphite-web, nodejs-eyes
pmackinn: jdo-api
ppisar: qpid-proton
puiterwijk: qpid-proton
pvalena: buildnumber-maven-plugin
pwouters: ike-scan
python-sig: nodejs-moment
qwan: qpid-proton
ralph: qpid-proton
rgrunber: eclipse-dltk
rlandmann: avalon-logkit
robert: apachetop
romanofski: qpid-proton
rsroka: qpid-proton
ruben: vttest
ruby-packagers-sig: buildnumber-maven-plugin
s4504kr: avalon-logkit
sagitter: matio, avalon-logkit
santiago: qpid-proton
sbonazzo: buildnumber-maven-plugin
sgallagh: python-texttable
sinnykumari: qpid-proton
skottler: zookeeper, buildnumber-maven-plugin
slaanesh: matio
slankes: ferm
smizrahi: ioprocess
sochotni: qpid-proton
stahnma: buildnumber-maven-plugin
stevetraylen: buildnumber-maven-plugin
swagiaal: eclipse-anyedit
tagoh: qpid-proton
tc01: nodejs-eyes
tdawson: qpid-proton, buildnumber-maven-plugin, mcollective-qpid-plugin
terjeros: buildnumber-maven-plugin
teuf: libgovirt
tomh: nodejs-send, nodejs-eyes, nodejs-encodeurl, nodejs-finalhandler
tosykora: qpid-proton
tross: qpid-proton
ttomecek: qpid-proton, python-dockerpty, python-texttable
twaugh: qpid-proton
valtri: buildnumber-maven-plugin
victortoso: libgovirt
virtmaint-sig: libgovirt
volter: matio
vondruch: buildnumber-maven-plugin
vrutkovs: qpid-proton
wakko666: buildnumber-maven-plugin
wwoods: qpid-proton
xaeth: vttest
xiubli: qpid-proton
zbyszek: jhdf5
--
The script creating this output is run and developed by Fedora
Release Engineering. Please report issues at its pagure instance:
https://pagure.io/releng/
The sources of this script can be found at:
https://pagure.io/releng/blob/master/f/scripts/find_unblocked_orphans.py
_______________________________________________
devel-announce mailing list -- devel-announce@lists.fedoraproject.org
To unsubscribe send an email to devel-announce-leave@lists.fedoraproject.org
Fedora Code of Conduct: https://docs.fedoraproject.org/en-US/project/code-of-conduct/
List Guidelines: https://fedoraproject.org/wiki/Mailing_list_guidelines
List Archives: https://lists.fedoraproject.org/archives/list/devel-announce@lists.fedoraproject.org
Friday, December 20, 2019
[arch-announce] Xorg cleanup requires manual intervention
In the process of [Xorg cleanup][1] the update requires manual
intervention when you hit this message:
:: installing xorgproto (2019.2-2) breaks dependency 'inputproto' required by lib32-libxi
:: installing xorgproto (2019.2-2) breaks dependency 'dmxproto' required by libdmx
:: installing xorgproto (2019.2-2) breaks dependency 'xf86dgaproto' required by libxxf86dga
when updating, use: `pacman -Rdd libdmx libxxf86dga && pacman -Syu` to perform the upgrade. After the update it will be safe to also remove
the "xorgproto" package.
[1]: https://bugs.archlinux.org/task/64892
URL: https://www.archlinux.org/news/xorg-cleanup-requires-manual-intervention/
_______________________________________________
arch-announce mailing list
arch-announce@archlinux.org
https://lists.archlinux.org/listinfo/arch-announce
intervention when you hit this message:
:: installing xorgproto (2019.2-2) breaks dependency 'inputproto' required by lib32-libxi
:: installing xorgproto (2019.2-2) breaks dependency 'dmxproto' required by libdmx
:: installing xorgproto (2019.2-2) breaks dependency 'xf86dgaproto' required by libxxf86dga
when updating, use: `pacman -Rdd libdmx libxxf86dga && pacman -Syu` to perform the upgrade. After the update it will be safe to also remove
the "xorgproto" package.
[1]: https://bugs.archlinux.org/task/64892
URL: https://www.archlinux.org/news/xorg-cleanup-requires-manual-intervention/
_______________________________________________
arch-announce mailing list
arch-announce@archlinux.org
https://lists.archlinux.org/listinfo/arch-announce
Thursday, December 19, 2019
Fedora 32 System-Wide Change proposal: Use update-alternatives for /usr/bin/cc and /usr/bin/c++
https://fedoraproject.org/wiki/Changes/Use-Update-Alternatives-For-usr-bin-cc
== Summary ==
Modify the gcc package so that the /usr/bin/cc and /usr/bin/c++
symlinks are managed by update-alternatives.
== Owner ==
* Name: [[User:tstellar| Tom Stellard]]
* Email: <tstellar@redhat.com>
== Detailed Description ==
The gcc package currently installs symlinks to /usr/bin/cc and
/usr/bin/c++ which point to /usr/bin/gcc and /usr/bin/g++
respectively. For this change, the gcc package will be modified so
that update-alternatives creates and manages these symlinks.
In addition to modifying the gcc package, the clang package will be
modified so that /usr/bin/clang and /usr/bin/clang++ can be used as
alternatives for /usr/bin/cc and /usr/bin/c++. The clang alternatives
will have a lower priority than the gcc alternatives, so that by
default, gcc will provide the /usr/bin/cc and /usr/bin/c++
implementations.
The clang package currently has a run-time dependency on gcc, so this
ensures that gcc will always provide the default implementation,
because it's impossible to install clang without gcc.
The only way users will be able to change the /usr/bin/cc or
/usr/bin/c++ implementations will be by explicitly using the
update-alternatives tool.
== Benefit to Fedora ==
Many build systems default to using /usr/bin/cc and /usr/bin/c++ as
the default C/C++ compilers. Being able to easily swap out these
implementation will provide a lot of flexibility within Fedora for
doing things like:
* Setting up alternative buildroots for testing.
* Installing a gcc wrapper script to /usr/bin/cc to help migrate
packages to new compiler flags or to capture statistics about compiler
usage.
* Letting users experiment easily with alternate compilers.
* Easily switch between system gcc and a development version of gcc.
== Scope ==
* Proposal owners: The proposal owner will implement the necessary
changes in the gcc and clang packages.
* Other developers: The gcc maintainers will be responsible for
reviewing and approving changes to the gcc package.
* Release engineering: (a check of an impact with Release Engineering is needed)
* Policies and guidelines: No policies or guidelines will need to be
updated as a result of this change.
* Trademark approval: N/A (not needed for this Change)
== Upgrade/compatibility impact ==
This change should not impact upgradeability.
== How To Test ==
CI tests will be added to the gcc package to ensure that /usr/bin/cc
and /usr/bin/c++ still point to /usr/bin/gcc and /usr/bin/g++ when
installed. There will also be a CI test added to the clang package to
ensure that /usr/bin/gcc and /usr/bin/g++ remain the default when
clang is installed.
== User Experience ==
This change will give users a much better way to experiment using
other compilers for their own development. They will be able to
easily switch between different compilers without having to modify
their projects build system or make non-standard changes to their
Fedora system.
== Dependencies ==
This change has no other dependencies besides the changes to the gcc
and clang packages.
== Contingency Plan ==
* Contingency mechanism: (What to do? Who will do it?) Proposal Owner
will revert changes made to gcc and clang packages and rebuild.
* Contingency deadline: If the changes are not complete by 2 weeks
before the mass rebuild, then we will consider postponing to the next
Fedora release and back out any changes that were made.
* Blocks release? No
* Blocks product? None
== Documentation ==
Release notes will be added for this change.
== Release Notes ==
The user /usr/bin/cc and /usr/bin/c++ symlinks are now managed by
update-alternatives. If you would like to change these symlinks to
point to another compiler, like clang, for example, you can use these
commands:
`update-alternatives --set cc /usr/bin/clang`
`update-alternatives --set c++ /usr/bin/clang++`
--
Ben Cotton
He / Him / His
Fedora Program Manager
Red Hat
TZ=America/Indiana/Indianapolis
_______________________________________________
devel-announce mailing list -- devel-announce@lists.fedoraproject.org
To unsubscribe send an email to devel-announce-leave@lists.fedoraproject.org
Fedora Code of Conduct: https://docs.fedoraproject.org/en-US/project/code-of-conduct/
List Guidelines: https://fedoraproject.org/wiki/Mailing_list_guidelines
List Archives: https://lists.fedoraproject.org/archives/list/devel-announce@lists.fedoraproject.org
== Summary ==
Modify the gcc package so that the /usr/bin/cc and /usr/bin/c++
symlinks are managed by update-alternatives.
== Owner ==
* Name: [[User:tstellar| Tom Stellard]]
* Email: <tstellar@redhat.com>
== Detailed Description ==
The gcc package currently installs symlinks to /usr/bin/cc and
/usr/bin/c++ which point to /usr/bin/gcc and /usr/bin/g++
respectively. For this change, the gcc package will be modified so
that update-alternatives creates and manages these symlinks.
In addition to modifying the gcc package, the clang package will be
modified so that /usr/bin/clang and /usr/bin/clang++ can be used as
alternatives for /usr/bin/cc and /usr/bin/c++. The clang alternatives
will have a lower priority than the gcc alternatives, so that by
default, gcc will provide the /usr/bin/cc and /usr/bin/c++
implementations.
The clang package currently has a run-time dependency on gcc, so this
ensures that gcc will always provide the default implementation,
because it's impossible to install clang without gcc.
The only way users will be able to change the /usr/bin/cc or
/usr/bin/c++ implementations will be by explicitly using the
update-alternatives tool.
== Benefit to Fedora ==
Many build systems default to using /usr/bin/cc and /usr/bin/c++ as
the default C/C++ compilers. Being able to easily swap out these
implementation will provide a lot of flexibility within Fedora for
doing things like:
* Setting up alternative buildroots for testing.
* Installing a gcc wrapper script to /usr/bin/cc to help migrate
packages to new compiler flags or to capture statistics about compiler
usage.
* Letting users experiment easily with alternate compilers.
* Easily switch between system gcc and a development version of gcc.
== Scope ==
* Proposal owners: The proposal owner will implement the necessary
changes in the gcc and clang packages.
* Other developers: The gcc maintainers will be responsible for
reviewing and approving changes to the gcc package.
* Release engineering: (a check of an impact with Release Engineering is needed)
* Policies and guidelines: No policies or guidelines will need to be
updated as a result of this change.
* Trademark approval: N/A (not needed for this Change)
== Upgrade/compatibility impact ==
This change should not impact upgradeability.
== How To Test ==
CI tests will be added to the gcc package to ensure that /usr/bin/cc
and /usr/bin/c++ still point to /usr/bin/gcc and /usr/bin/g++ when
installed. There will also be a CI test added to the clang package to
ensure that /usr/bin/gcc and /usr/bin/g++ remain the default when
clang is installed.
== User Experience ==
This change will give users a much better way to experiment using
other compilers for their own development. They will be able to
easily switch between different compilers without having to modify
their projects build system or make non-standard changes to their
Fedora system.
== Dependencies ==
This change has no other dependencies besides the changes to the gcc
and clang packages.
== Contingency Plan ==
* Contingency mechanism: (What to do? Who will do it?) Proposal Owner
will revert changes made to gcc and clang packages and rebuild.
* Contingency deadline: If the changes are not complete by 2 weeks
before the mass rebuild, then we will consider postponing to the next
Fedora release and back out any changes that were made.
* Blocks release? No
* Blocks product? None
== Documentation ==
Release notes will be added for this change.
== Release Notes ==
The user /usr/bin/cc and /usr/bin/c++ symlinks are now managed by
update-alternatives. If you would like to change these symlinks to
point to another compiler, like clang, for example, you can use these
commands:
`update-alternatives --set cc /usr/bin/clang`
`update-alternatives --set c++ /usr/bin/clang++`
--
Ben Cotton
He / Him / His
Fedora Program Manager
Red Hat
TZ=America/Indiana/Indianapolis
_______________________________________________
devel-announce mailing list -- devel-announce@lists.fedoraproject.org
To unsubscribe send an email to devel-announce-leave@lists.fedoraproject.org
Fedora Code of Conduct: https://docs.fedoraproject.org/en-US/project/code-of-conduct/
List Guidelines: https://fedoraproject.org/wiki/Mailing_list_guidelines
List Archives: https://lists.fedoraproject.org/archives/list/devel-announce@lists.fedoraproject.org
Fedora 32 System-Wide Change proposal: Enable fstrim.timer by default
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@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
_______________________________________________
devel-announce mailing list -- devel-announce@lists.fedoraproject.org
To unsubscribe send an email to devel-announce-leave@lists.fedoraproject.org
Fedora Code of Conduct: https://docs.fedoraproject.org/en-US/project/code-of-conduct/
List Guidelines: https://fedoraproject.org/wiki/Mailing_list_guidelines
List Archives: https://lists.fedoraproject.org/archives/list/devel-announce@lists.fedoraproject.org
== 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@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
_______________________________________________
devel-announce mailing list -- devel-announce@lists.fedoraproject.org
To unsubscribe send an email to devel-announce-leave@lists.fedoraproject.org
Fedora Code of Conduct: https://docs.fedoraproject.org/en-US/project/code-of-conduct/
List Guidelines: https://fedoraproject.org/wiki/Mailing_list_guidelines
List Archives: https://lists.fedoraproject.org/archives/list/devel-announce@lists.fedoraproject.org
Fedora 32 System-Wide Change proposal: LTO by default for package builds
https://fedoraproject.org/wiki/LTOByDefault
== Summary ==
This is a proposal to enable link time optimization (LTO) of packages
built with rpmbuild by default. It's an over-simplification, but
think of LTO as deferring analysis, optimization and code generation
until creation of an executable or dynamic shared object.
This is implemented by adding the option "-flto" the injected flags in
redhat-rpm-config. There will be a simple way for packages to opt-out
of LTO.
== Owner ==
* Name: Jeff Law
* Email: law@redhat.com
== Detailed Description ==
Programs built with rpmbuild and which honor flags injection via
redhat-rpm-config will be built with LTO by default. A simple opt-out
mechanism will be provided for packages which use features that are
not LTO compatible.
The LTO bytecode itself will not be distributed as it is not stable
from one GCC release to the next. This is enforced by stripping the
LTO bytecode from any installed .o/.a files. We'll use bits SuSE has
already written for redhat-rpm-config to implement this.
Minor changes are desirable to the %configure macro in
redhat-rpm-config to fix common code idioms used by autoconf generated
scripts which are compromised by the additional optimization enabled
by LTO. Minor updates to various packages will be needed to opt-out
of LTO or fix bugs exposed by LTO.
== Benefit to Fedora ==
The primary benefits of building with LTO enabled are smaller, faster
executables/DSOs. A secondary benefit is LTO allows deeper analysis
of package source code at compile time which can improve various GCC
diagnostics and thus improve our ability to catch bugs at compile time
such as uninitialized objects, buffer overflows, unterminated strings,
restrict violations, etc.
This change also brings us back on-par with SuSE who enabled LTO by
default for their free distribution earlier in 2019.
== Scope ==
* Proposal owners:
The primary change is to redhat-rpm-config to add LTO to the default
compile/link flags as well as a conditional which allows easy opt-out
on a package by package basis. Additionally the post-build scripts
need to strip the LTO bytecodes from any installed .o/.a files.
Additionally, we know there are many packages with configure scripts
that are compromised by LTO. I have tweaks to the %configure macro in
redhat-rpm-config which fixes the vast majority of these problems with
a few simple sed scripts on the generated output. Like the basic
support for injecting the LTO flags, this will require coordination
with the redhat-rpm-config maintainers. Packages which call configure
directly and have compromised tests will need a one line change to
their .spec files to fix their configure scripts.
Some packages will need to opt-out of using LTO at this time. The
most common case are packages that use symbol versioning or toplevel
ASM statements. While there is a new mechanism to make LTO work with
symbol versioning, I don't think any packages have been updated to use
that mechanism. This will require a one line change to 50-75 packages
(my script to find these is still running).
Finally, some packages will fail to build with LTO due to deeper
analysis for compile-time diagnostics catching programming mistakes
that have gone unnoticed until now. I'll obviously be working with
package maintainers on all of these issues.
Note that even though the changes are fairly well localized in
redhat-rpm-config and a small number of packages, the real scope of
this change is much larger since it affects all packages in the
distribution that are compiled with GCC and which honor the flags
injection by redhat-rpm-config.
* Other developers:
As I mentioned, I'm happy to contact package owners that need to
modify their packages and suggest how their package needs to be fixed.
As a multi-decade GCC developer, I'm particularly well suited to
describe LTO, its limitations and how LTO impacts the diagnostics from
GCC to any package owner that needs additional information.
I'm also capable and available to address any GCC issues that we may
arise as a result of this change. I don't expect much of the latter
as SuSE has already enabled this feature for their distribution and
thus weeded out most of the issues.
The highest level of coordination will be with the redhat-rpm-config
maintainers.
I will also be coordinating with the GDB team to address debugging
issues related to LTO. The most important issue is to ensure that we
can pass the GDB testsuite with and without the -flto option being
enabled. Failure to meet this goal would be considered a blocking
issue for LTO enablement.
I'm also already in contact with SuSE and Debian/Ununtu engineers to
discuss issues with gcc-10 with and without LTO.
We know there are some problems with debugging LTO code. I will be
working with the GDB team to identify these issues and fix them either
in the debugger or compiler as needed.
I have prototype code for the required redhat-rpm-config changes and
I'll coordinate with the redhat-rpm-config maintainer to get them into
the desired final form.
I also know every package that fails with LTO enabled. I'm still
categorizing those failures. Many will ultimately need to use the
opt-out mechanism because they use features that are not compatible
with LTO. I expect to have all this ready to go the first work week
of the new year. I will coordinate with package owners to either add
the opt-out markers or fix issues in the package as needed.
* Release engineering: (a check of an impact with Release Engineering is needed)
Aside from the redhat-rpm-config changes, I do not expect any work
from releng to be necessary. However, they need to be aware of the
change and who to contact in case of issues.
* Policies and guidelines: It would be useful to document how to
opt-out of LTO in the packaging guidelines.
* Trademark approval: N/A (not needed for this Change)
== Upgrade/compatibility impact ==
Should not affect compatibility. Stripping of the LTO bytecode is
critical to ensure there are not long term compatibility issues.
== How To Test ==
In the short term, I'm happy to expose a repository with a gcc-10
snapshot and updated redhat-rpm-config. Developers could then use
that repo to pick up gcc-10 and LTO optimizations for testing
purposes. I'm already doing this internally for x86_64 and exposing
it to the world would be trivial.
Given such a repository, another developer would merely use that repo
when building their package. No special hardware is needed. The most
useful testing is first to identify FTBFS issues and get them
proactively fixed. I'm happy to own that since I'm already doing that
for baseline gcc-10 issues as well as gcc-10 + LTO issues.
Doing the same testing on other architectures would definitely be
useful. I'd be particularly concerned about large packages on the
32bit architectures. I wouldn't be surprised if we find some packages
need to opt-out of LTO because they run out of memory at link/compile
time. I'm already in contact with some Debian maintainers who want
to do testing around this issue as they're investigating a similar
change for Debian.
I'm already building all of Fedora with the weekly gcc-10 snapshots
(including LTO builds starting the week of 12/15). This is primarily
to proactive find/address issues with the gcc-10 transition, but
verification of LTO state pretty much piggy backs for free on the
gcc-10 work.
== User Experience ==
In theory, the only noticeable difference to users would be smaller,
faster binaries and DSOs. However, a developer that uses rpmbuild to
build their own code may see their package fail to build if it's got
errors or uses certain features that do not work with LTO.
Users who try to debug Fedora shipped executables could notice
differences in the debugging experience.
== Dependencies ==
None expected beyond addressing FTBFS issues and coordination between
GCC and GDB teams on any debugging issues we find over the next few
weeks.
== Contingency Plan ==
* Contingency mechanism: Revert the LTO flags injection
* Contingency deadline: Beta freeze, but shooting for prior to mass
rebuilds starting
* Blocks release? No
* Blocks product? No
Most critically, if we don't address the GDB testsuite issue noted
above, our fallback position would be to simply disable the LTO
injection globally and re-evaluate for Fedora 33, similarly if we were
to find some show-stopping LTO issue.
Otherwise the plan is to analyze the remaining 100-125 package build
failures. These are likely a mixture of configure issues that can't
be trivially fixed via %configure, new diagnostics exposed by the
deeper analysis from LTO, and other small issues.
== Documentation ==
I would think we would want documentation on the opt-out method for RPM builds.
--
Ben Cotton
He / Him / His
Fedora Program Manager
Red Hat
TZ=America/Indiana/Indianapolis
_______________________________________________
devel-announce mailing list -- devel-announce@lists.fedoraproject.org
To unsubscribe send an email to devel-announce-leave@lists.fedoraproject.org
Fedora Code of Conduct: https://docs.fedoraproject.org/en-US/project/code-of-conduct/
List Guidelines: https://fedoraproject.org/wiki/Mailing_list_guidelines
List Archives: https://lists.fedoraproject.org/archives/list/devel-announce@lists.fedoraproject.org
== Summary ==
This is a proposal to enable link time optimization (LTO) of packages
built with rpmbuild by default. It's an over-simplification, but
think of LTO as deferring analysis, optimization and code generation
until creation of an executable or dynamic shared object.
This is implemented by adding the option "-flto" the injected flags in
redhat-rpm-config. There will be a simple way for packages to opt-out
of LTO.
== Owner ==
* Name: Jeff Law
* Email: law@redhat.com
== Detailed Description ==
Programs built with rpmbuild and which honor flags injection via
redhat-rpm-config will be built with LTO by default. A simple opt-out
mechanism will be provided for packages which use features that are
not LTO compatible.
The LTO bytecode itself will not be distributed as it is not stable
from one GCC release to the next. This is enforced by stripping the
LTO bytecode from any installed .o/.a files. We'll use bits SuSE has
already written for redhat-rpm-config to implement this.
Minor changes are desirable to the %configure macro in
redhat-rpm-config to fix common code idioms used by autoconf generated
scripts which are compromised by the additional optimization enabled
by LTO. Minor updates to various packages will be needed to opt-out
of LTO or fix bugs exposed by LTO.
== Benefit to Fedora ==
The primary benefits of building with LTO enabled are smaller, faster
executables/DSOs. A secondary benefit is LTO allows deeper analysis
of package source code at compile time which can improve various GCC
diagnostics and thus improve our ability to catch bugs at compile time
such as uninitialized objects, buffer overflows, unterminated strings,
restrict violations, etc.
This change also brings us back on-par with SuSE who enabled LTO by
default for their free distribution earlier in 2019.
== Scope ==
* Proposal owners:
The primary change is to redhat-rpm-config to add LTO to the default
compile/link flags as well as a conditional which allows easy opt-out
on a package by package basis. Additionally the post-build scripts
need to strip the LTO bytecodes from any installed .o/.a files.
Additionally, we know there are many packages with configure scripts
that are compromised by LTO. I have tweaks to the %configure macro in
redhat-rpm-config which fixes the vast majority of these problems with
a few simple sed scripts on the generated output. Like the basic
support for injecting the LTO flags, this will require coordination
with the redhat-rpm-config maintainers. Packages which call configure
directly and have compromised tests will need a one line change to
their .spec files to fix their configure scripts.
Some packages will need to opt-out of using LTO at this time. The
most common case are packages that use symbol versioning or toplevel
ASM statements. While there is a new mechanism to make LTO work with
symbol versioning, I don't think any packages have been updated to use
that mechanism. This will require a one line change to 50-75 packages
(my script to find these is still running).
Finally, some packages will fail to build with LTO due to deeper
analysis for compile-time diagnostics catching programming mistakes
that have gone unnoticed until now. I'll obviously be working with
package maintainers on all of these issues.
Note that even though the changes are fairly well localized in
redhat-rpm-config and a small number of packages, the real scope of
this change is much larger since it affects all packages in the
distribution that are compiled with GCC and which honor the flags
injection by redhat-rpm-config.
* Other developers:
As I mentioned, I'm happy to contact package owners that need to
modify their packages and suggest how their package needs to be fixed.
As a multi-decade GCC developer, I'm particularly well suited to
describe LTO, its limitations and how LTO impacts the diagnostics from
GCC to any package owner that needs additional information.
I'm also capable and available to address any GCC issues that we may
arise as a result of this change. I don't expect much of the latter
as SuSE has already enabled this feature for their distribution and
thus weeded out most of the issues.
The highest level of coordination will be with the redhat-rpm-config
maintainers.
I will also be coordinating with the GDB team to address debugging
issues related to LTO. The most important issue is to ensure that we
can pass the GDB testsuite with and without the -flto option being
enabled. Failure to meet this goal would be considered a blocking
issue for LTO enablement.
I'm also already in contact with SuSE and Debian/Ununtu engineers to
discuss issues with gcc-10 with and without LTO.
We know there are some problems with debugging LTO code. I will be
working with the GDB team to identify these issues and fix them either
in the debugger or compiler as needed.
I have prototype code for the required redhat-rpm-config changes and
I'll coordinate with the redhat-rpm-config maintainer to get them into
the desired final form.
I also know every package that fails with LTO enabled. I'm still
categorizing those failures. Many will ultimately need to use the
opt-out mechanism because they use features that are not compatible
with LTO. I expect to have all this ready to go the first work week
of the new year. I will coordinate with package owners to either add
the opt-out markers or fix issues in the package as needed.
* Release engineering: (a check of an impact with Release Engineering is needed)
Aside from the redhat-rpm-config changes, I do not expect any work
from releng to be necessary. However, they need to be aware of the
change and who to contact in case of issues.
* Policies and guidelines: It would be useful to document how to
opt-out of LTO in the packaging guidelines.
* Trademark approval: N/A (not needed for this Change)
== Upgrade/compatibility impact ==
Should not affect compatibility. Stripping of the LTO bytecode is
critical to ensure there are not long term compatibility issues.
== How To Test ==
In the short term, I'm happy to expose a repository with a gcc-10
snapshot and updated redhat-rpm-config. Developers could then use
that repo to pick up gcc-10 and LTO optimizations for testing
purposes. I'm already doing this internally for x86_64 and exposing
it to the world would be trivial.
Given such a repository, another developer would merely use that repo
when building their package. No special hardware is needed. The most
useful testing is first to identify FTBFS issues and get them
proactively fixed. I'm happy to own that since I'm already doing that
for baseline gcc-10 issues as well as gcc-10 + LTO issues.
Doing the same testing on other architectures would definitely be
useful. I'd be particularly concerned about large packages on the
32bit architectures. I wouldn't be surprised if we find some packages
need to opt-out of LTO because they run out of memory at link/compile
time. I'm already in contact with some Debian maintainers who want
to do testing around this issue as they're investigating a similar
change for Debian.
I'm already building all of Fedora with the weekly gcc-10 snapshots
(including LTO builds starting the week of 12/15). This is primarily
to proactive find/address issues with the gcc-10 transition, but
verification of LTO state pretty much piggy backs for free on the
gcc-10 work.
== User Experience ==
In theory, the only noticeable difference to users would be smaller,
faster binaries and DSOs. However, a developer that uses rpmbuild to
build their own code may see their package fail to build if it's got
errors or uses certain features that do not work with LTO.
Users who try to debug Fedora shipped executables could notice
differences in the debugging experience.
== Dependencies ==
None expected beyond addressing FTBFS issues and coordination between
GCC and GDB teams on any debugging issues we find over the next few
weeks.
== Contingency Plan ==
* Contingency mechanism: Revert the LTO flags injection
* Contingency deadline: Beta freeze, but shooting for prior to mass
rebuilds starting
* Blocks release? No
* Blocks product? No
Most critically, if we don't address the GDB testsuite issue noted
above, our fallback position would be to simply disable the LTO
injection globally and re-evaluate for Fedora 33, similarly if we were
to find some show-stopping LTO issue.
Otherwise the plan is to analyze the remaining 100-125 package build
failures. These are likely a mixture of configure issues that can't
be trivially fixed via %configure, new diagnostics exposed by the
deeper analysis from LTO, and other small issues.
== Documentation ==
I would think we would want documentation on the opt-out method for RPM builds.
--
Ben Cotton
He / Him / His
Fedora Program Manager
Red Hat
TZ=America/Indiana/Indianapolis
_______________________________________________
devel-announce mailing list -- devel-announce@lists.fedoraproject.org
To unsubscribe send an email to devel-announce-leave@lists.fedoraproject.org
Fedora Code of Conduct: https://docs.fedoraproject.org/en-US/project/code-of-conduct/
List Guidelines: https://fedoraproject.org/wiki/Mailing_list_guidelines
List Archives: https://lists.fedoraproject.org/archives/list/devel-announce@lists.fedoraproject.org
OpenBSD Errata: December 20th, 2019 (ripd)
Errata patches for ripd have been released for OpenBSD 6.5 and 6.6.
ripd(8) fails to validate authentication lengths.
Binary updates for the amd64, i386, and arm64 platforms are available via
the syspatch utility. Source code patches can be found on the respective
errata page:
https://www.openbsd.org/errata65.html
https://www.openbsd.org/errata66.html
ripd(8) fails to validate authentication lengths.
Binary updates for the amd64, i386, and arm64 platforms are available via
the syspatch utility. Source code patches can be found on the respective
errata page:
https://www.openbsd.org/errata65.html
https://www.openbsd.org/errata66.html
OpenBSD Errata: December 20th, 2019 (ftp)
Errata patches for ftp have been released for OpenBSD 6.5 and 6.6.
ftp(1) will follow remote redirects to local files.
Binary updates for the amd64, i386, and arm64 platforms are available via
the syspatch utility. Source code patches can be found on the respective
errata page:
https://www.openbsd.org/errata65.html
https://www.openbsd.org/errata66.html
ftp(1) will follow remote redirects to local files.
Binary updates for the amd64, i386, and arm64 platforms are available via
the syspatch utility. Source code patches can be found on the respective
errata page:
https://www.openbsd.org/errata65.html
https://www.openbsd.org/errata66.html
[announce] Next NYC*BUG: Jan 8th 2020 What is notqmail?
What is notqmail?, Amitai Schleier
*Chartbeat 826 Broadway, 6th Floor New York, NY 10003*
* NEW LOCATION! *
(Building above the Strand Bookstore)
What is notqmail?
It's not qmail. It's also not netqmail.
We all use email, so we all use email servers. notqmail is software for running an email server. Someday, if we do a good job, some of the many articles about how and why to run your own will recommend notqmail. notqmail is a community-driven fork of qmail, beginning where netqmail
left off: providing stable, compatible, small releases to which existing qmail users can safely update. notqmail also aims higher: developing an extensible, easily packaged, and increasingly useful modern mail server.
It's not qmail. It's also not netqmail.
We all use email, so we all use email servers. notqmail is software for running an email server. Someday, if we do a good job, some of the many articles about how and why to run your own will recommend notqmail. notqmail is a community-driven fork of qmail, beginning where netqmail
left off: providing stable, compatible, small releases to which existing qmail users can safely update. notqmail also aims higher: developing an extensible, easily packaged, and increasingly useful modern mail server.
Wednesday, December 18, 2019
[USN-4224-1] Django vulnerability
==========================================================================
Ubuntu Security Notice USN-4224-1
December 19, 2019
python-django vulnerability
==========================================================================
A security issue affects these releases of Ubuntu and its derivatives:
- Ubuntu 19.10
- Ubuntu 19.04
- Ubuntu 18.04 LTS
- Ubuntu 16.04 LTS
Summary:
Django accounts could be hijacked through password reset requests.
Software Description:
- python-django: High-level Python web development framework
Details:
Simon Charette discovered that the password reset functionality in
Django used a Unicode case insensitive query to retrieve accounts
associated with an email address. An attacker could possibly use this
to obtain password reset tokens and hijack accounts.
Update instructions:
The problem can be corrected by updating your system to the following
package versions:
Ubuntu 19.10:
python-django 1:1.11.22-1ubuntu1.1
python3-django 1:1.11.22-1ubuntu1.1
Ubuntu 19.04:
python-django 1:1.11.20-1ubuntu0.3
python3-django 1:1.11.20-1ubuntu0.3
Ubuntu 18.04 LTS:
python-django 1:1.11.11-1ubuntu1.6
python3-django 1:1.11.11-1ubuntu1.6
Ubuntu 16.04 LTS:
python-django 1.8.7-1ubuntu5.11
python3-django 1.8.7-1ubuntu5.11
In general, a standard system update will make all the necessary changes.
References:
https://usn.ubuntu.com/4224-1
CVE-2019-19844
Package Information:
https://launchpad.net/ubuntu/+source/python-django/1:1.11.22-1ubuntu1.1
https://launchpad.net/ubuntu/+source/python-django/1:1.11.20-1ubuntu0.3
https://launchpad.net/ubuntu/+source/python-django/1:1.11.11-1ubuntu1.6
https://launchpad.net/ubuntu/+source/python-django/1.8.7-1ubuntu5.11
Ubuntu Security Notice USN-4224-1
December 19, 2019
python-django vulnerability
==========================================================================
A security issue affects these releases of Ubuntu and its derivatives:
- Ubuntu 19.10
- Ubuntu 19.04
- Ubuntu 18.04 LTS
- Ubuntu 16.04 LTS
Summary:
Django accounts could be hijacked through password reset requests.
Software Description:
- python-django: High-level Python web development framework
Details:
Simon Charette discovered that the password reset functionality in
Django used a Unicode case insensitive query to retrieve accounts
associated with an email address. An attacker could possibly use this
to obtain password reset tokens and hijack accounts.
Update instructions:
The problem can be corrected by updating your system to the following
package versions:
Ubuntu 19.10:
python-django 1:1.11.22-1ubuntu1.1
python3-django 1:1.11.22-1ubuntu1.1
Ubuntu 19.04:
python-django 1:1.11.20-1ubuntu0.3
python3-django 1:1.11.20-1ubuntu0.3
Ubuntu 18.04 LTS:
python-django 1:1.11.11-1ubuntu1.6
python3-django 1:1.11.11-1ubuntu1.6
Ubuntu 16.04 LTS:
python-django 1.8.7-1ubuntu5.11
python3-django 1.8.7-1ubuntu5.11
In general, a standard system update will make all the necessary changes.
References:
https://usn.ubuntu.com/4224-1
CVE-2019-19844
Package Information:
https://launchpad.net/ubuntu/+source/python-django/1:1.11.22-1ubuntu1.1
https://launchpad.net/ubuntu/+source/python-django/1:1.11.20-1ubuntu0.3
https://launchpad.net/ubuntu/+source/python-django/1:1.11.11-1ubuntu1.6
https://launchpad.net/ubuntu/+source/python-django/1.8.7-1ubuntu5.11
Subscribe to:
Posts (Atom)