Re: List of Python 2 packages to be removed mid-November
> cicku > lilypond > (→ PY2) This one is a problem. A number of packages depend on it… Is anyone looking into this? > zbyszek > mpich > python2-mpich (→ PY2) Fixed by Miro. > python-blosc > (BuildRequires: python2-numpy → PY2) It was removed last year, just a stray build dep was remaining, fixed now by Miro. > python-music21 > python3-music21 (→ lilypond → PY2) Right, lilypond… > python-pypandoc > python2-pypandoc (→ PY2) It is used by python2-pyrtlsdr. Jaroslav, would you mind if I removed python2-pyrtlsdr now? > systemd-coredump-python > python2-systemd-coredump (→ PY2) Built now. Zbyszek ___ devel mailing list -- devel@lists.fedoraproject.org To unsubscribe send an email to devel-le...@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@lists.fedoraproject.org
Re: Minimization Objective report
On Thu, Oct 17, 2019 at 10:50 AM Miro Hrončok wrote: > On 16. 10. 19 20:14, Adam Samalik wrote:> == PostgreSQL == > > > > Started talking to the maintainers about removing systemd, python2, and > to > > consider skipping weak dependencies in the container use case. > > Thanks! Please keep mes looped in for the python2 thing. > Will do, thanks! > > -- > Miro Hrončok > -- > Phone: +420777974800 > IRC: mhroncok > ___ > devel mailing list -- devel@lists.fedoraproject.org > To unsubscribe send an email to devel-le...@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@lists.fedoraproject.org > -- Adam Šamalík --- Senior Software Engineer Red Hat ___ devel mailing list -- devel@lists.fedoraproject.org To unsubscribe send an email to devel-le...@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@lists.fedoraproject.org
Re: List of Python 2 packages to be removed mid-November
On Tue, Oct 29, 2019 at 04:24:02PM +0100, Miro Hrončok wrote: > ## What exactly is happening? > > The formal change proposal is here: > https://fedoraproject.org/wiki/Changes/RetirePython2 > > Packages requiring Python 2 will be removed starting November 15 (unless > they have an exception). > Components with all essential subpackages removed will be retired. > The removal will be (semi-)automated. > > Source package only BuildRequiring removed packages will fail to build, and > will be removed according to the regular FTBFS policy. > > https://docs.fedoraproject.org/en-US/fesco/Fails_to_build_from_source_Fails_to_install/ > > > ## The list > > Here is the package breakdown sorted by maintainers. > The list contains the shortest dependency path to Python 2. The arrow means > "depends on". > > The data is based on the latest rawhide compose, so it might be a bit out of > date. > > If you find a bogus dependency, such as a dependency that can be resolved in > a non-Python 2 way, please let us know, so we can blacklist it. I'm unclear from the text above just what is proposed to be removed - the entire RPM vs just the py2 sub-RPMs. > veillard > libxml2 > python2-libxml2 (→ PY2) In this case the libxml2.spec file builds all of the native library, py2 binding and py3 binding. Please do *NOT* remove the entire libxml2 package as this will kill the virtualization stack. Only the bits of specfile logic that build the py2 binding should be removed. Regards, Daniel -- |: https://berrange.com -o-https://www.flickr.com/photos/dberrange :| |: https://libvirt.org -o-https://fstop138.berrange.com :| |: https://entangle-photo.org-o-https://www.instagram.com/dberrange :| ___ devel mailing list -- devel@lists.fedoraproject.org To unsubscribe send an email to devel-le...@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@lists.fedoraproject.org
Re: List of Python 2 packages to be removed mid-November
HI! On Tue, Oct 29, 2019 at 4:25 PM Miro Hrončok wrote: > Dear maintainers, > here is a list of packages that (transitively, at build or run time) > require > Python 2 and have not yet got a FESCo exception to do so. > If you were bcced on this e-mail, it affects one or more of your packages. > > The default action will be to remove such packages mid-November. > > If this took you by surprise, don't panic. It's possible to change the > default. > Let us know and we'll work things out. > The mid-November deadline is not for removing *all* of Python 2, but for > getting > exceptions. > > [...] > > bruno >qgis > (BuildRequires: python2-sip-devel → PY2) > It seems there is a wrong dependency in the spec file: BuildRequires: sip-devel Shouldn't this be BuildRequires: python3-sip-devel? BR, Andrea ___ devel mailing list -- devel@lists.fedoraproject.org To unsubscribe send an email to devel-le...@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@lists.fedoraproject.org
Upgrade F30->F31 fails on speech-tools-libs
Error: Transaction test error: file /usr/lib64/libeststring.so.1.2 from install of speech-tools- libs-2.5-8.fc31.x86_64 conflicts with file from package festival- speechtools-libs-1.2.96-39.fc29.x86_64 OK, can we remove speech-tools-libs? [nbecker@nbecker2 ~]$ sudo dnf remove speech-tools-libs No match for argument: speech-tools-libs No packages marked for removal. Nope, it isn't installed. [nbecker@nbecker2 ~]$ sudo dnf remove festival-speechtools-libs Dependencies resolved. Package Architecture Version Repository Size Removing: festival-speechtools-libs x86_64 1.2.96-39.fc29 @fedora 3.7 M Removing dependent packages: festival-freebsoft-utils noarch 0.10-15.fc30 @fedora 121 k kdeaccessibility noarch 1:4.14.3-3.fc24 @@commandline 0 Removing unused dependencies: festival x86_64 1.96-39.fc29 @fedora 8.8 M festival-lib x86_64 1.96-39.fc29 @fedora 1.3 M festvox-slt-arctic-htsnoarch 0.20061229-39.fc29 @fedora 2.2 M jovie x86_64 17.08.3-6.fc30 @fedora 1.2 M jovie-libsx86_64 17.08.3-6.fc30 @fedora79 k kaccessible x86_64 17.08.3-4.fc30 @fedora 113 k kaccessible-libs x86_64 17.08.3-4.fc30 @fedora54 k kmag x86_64 18.12.2-1.fc30 @fedora 1.4 M kmousetoolx86_64 18.12.2-1.fc30 @fedora 593 k kmouthx86_64 18.12.2-1.fc30 @fedora 3.5 M libid3tag x86_64 0.15.1b-30.fc30 @fedora 165 k opusfile x86_64 0.11-2.fc30 @fedora 105 k sox x86_64 14.4.2.0-25.fc30 @fedora 1.4 M Transaction Summary Remove 16 Packages No, I don't really want to remove all of these. ___ devel mailing list -- devel@lists.fedoraproject.org To unsubscribe send an email to devel-le...@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@lists.fedoraproject.org
Re: Upgrade F30->F31 fails on speech-tools-libs
On Wed, Oct 30, 2019 at 10:44:39AM -, Neal Becker wrote: > Error: Transaction test error: > file /usr/lib64/libeststring.so.1.2 from install of speech-tools- > libs-2.5-8.fc31.x86_64 conflicts with file from package festival- > speechtools-libs-1.2.96-39.fc29.x86_64 https://bodhi.fedoraproject.org/updates/FEDORA-2019-cc9c0dd5a8 Please give karma. Zbyszek ___ devel mailing list -- devel@lists.fedoraproject.org To unsubscribe send an email to devel-le...@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@lists.fedoraproject.org
Re: Issues with the retrace service?
Dne 26. 10. 19 v 22:16 Frantisek Zatloukal napsal(a): > I think retrace service is running on RHEL 7.7 server and since we have zstd rpms in Fedora 31 [0], it won't work. I don't know what's the ETA for fix, I can ask on Tuesday, if there is any update on this issue. Right. The issue is zstd. Retrace-server uses Mock to install packages. Previously, Mock on RHEL7 was unable to install Fedora 31 because of zstd. This changed in Mock 1.4.20 [1], which hit stable in EPEL only 10 days ago [2]. We tested the retrace-server with the new Mock with retrace-server and we discovered another bug [3] in Mock which is not yet fixed. I want to fix it soon. At the same time, Michal Fabik from ABRT team is working on using Podman directly instead of Mock for retracing. This should be done soon as well. We need to finish one of those tasks. Until then, the retrace of F31+ will fail. [1] https://github.com/rpm-software-management/mock/wiki/Release-Notes-1.4.20 [2] https://bodhi.fedoraproject.org/updates/FEDORA-EPEL-2019-ddf315f3b1 [3] https://github.com/rpm-software-management/mock/issues/381 -- Miroslav Suchy, RHCA Red Hat, Associate Manager ABRT/Copr, #brno, #fedora-buildsys ___ devel mailing list -- devel@lists.fedoraproject.org To unsubscribe send an email to devel-le...@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@lists.fedoraproject.org
Re: Why Redhat and Fedora create rpms differently
Dne 25. 10. 19 v 16:20 Code Zombie napsal(a): I think it would be nice if the example apps were more realistic, e.g. considering dependencies, etc. There is many ways to do it. I can provide links to, at least, half dozen of other methods how to create rpm package. My favorite one is "how to create nosrc.rpm" packages [1]. Even in the Fedora, the mentioned methods are not the only ones. All those tutorial are meant to be simple. To be easy to understand. If you feel that some methods are complicated, then feel free to pick up the easier method. [1] https://developers.redhat.com/blog/2014/12/10/how-to-package-proprietary-software/ -- Miroslav Suchy, RHCA Red Hat, Associate Manager ABRT/Copr, #brno, #fedora-buildsys ___ devel mailing list -- devel@lists.fedoraproject.org To unsubscribe send an email to devel-le...@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@lists.fedoraproject.org
Re: List of Python 2 packages to be removed mid-November
On 30. 10. 19 11:39, Daniel P. Berrangé wrote: On Tue, Oct 29, 2019 at 04:24:02PM +0100, Miro Hrončok wrote: ## What exactly is happening? The formal change proposal is here: https://fedoraproject.org/wiki/Changes/RetirePython2 Packages requiring Python 2 will be removed starting November 15 (unless they have an exception). Components with all essential subpackages removed will be retired. The removal will be (semi-)automated. Source package only BuildRequiring removed packages will fail to build, and will be removed according to the regular FTBFS policy. https://docs.fedoraproject.org/en-US/fesco/Fails_to_build_from_source_Fails_to_install/ ## The list Here is the package breakdown sorted by maintainers. The list contains the shortest dependency path to Python 2. The arrow means "depends on". The data is based on the latest rawhide compose, so it might be a bit out of date. If you find a bogus dependency, such as a dependency that can be resolved in a non-Python 2 way, please let us know, so we can blacklist it. I'm unclear from the text above just what is proposed to be removed - the entire RPM vs just the py2 sub-RPMs. Just the listed subpackages. veillard libxml2 python2-libxml2 (→ PY2) In this case the libxml2.spec file builds all of the native library, py2 binding and py3 binding. Please do *NOT* remove the entire libxml2 package as this will kill the virtualization stack. Only the bits of specfile logic that build the py2 binding should be removed. That's the plan, sorry for not making it clear. -- Miro Hrončok -- Phone: +420777974800 IRC: mhroncok ___ devel mailing list -- devel@lists.fedoraproject.org To unsubscribe send an email to devel-le...@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@lists.fedoraproject.org
Re: Issues with the retrace service?
> Dne 26. 10. 19 v 22:16 Frantisek Zatloukal napsal(a): > > > I think retrace service is running on RHEL 7.7 server and since we have > > > zstd rpms in Fedora 31 [0], it won't work. I > > don't know what's the ETA for fix, I can ask on Tuesday, if there is any > > update on this issue. > > Right. The issue is zstd. Retrace-server uses Mock to install packages. > Previously, Mock on RHEL7 was unable to install > Fedora 31 because of zstd. This changed in Mock 1.4.20 [1], which hit stable > in EPEL only 10 days ago [2]. > We tested the retrace-server with the new Mock with retrace-server and we > discovered another bug [3] in Mock which is > not yet fixed. I want to fix it soon. > At the same time, Michal Fabik from ABRT team is working on using Podman > directly instead of Mock for retracing. This > should be done soon as well. > > We need to finish one of those tasks. Until then, the retrace of F31+ will > fail. Which is a slow and terrible user experience, yes changes like this take time but the sane thing to do would be to disable the retrace option and default to local processing until it's fixed. > [1] https://github.com/rpm-software-management/mock/wiki/Release-Notes-1.4.20 > [2] https://bodhi.fedoraproject.org/updates/FEDORA-EPEL-2019-ddf315f3b1 > [3] https://github.com/rpm-software-management/mock/issues/381 > > -- > Miroslav Suchy, RHCA > Red Hat, Associate Manager ABRT/Copr, #brno, #fedora-buildsys > ___ > devel mailing list -- devel@lists.fedoraproject.org > To unsubscribe send an email to devel-le...@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@lists.fedoraproject.org ___ devel mailing list -- devel@lists.fedoraproject.org To unsubscribe send an email to devel-le...@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@lists.fedoraproject.org
Java Package Orphanings
All, In the process of unorphaning resteasy, I picked up several other packages necessary to keep it alive. After trimming resteasy down, I was left with the following packages. - classmate (cc: lef) - cli-parser (cc: lef) - glassfish-gmbal - glassfish-management-api - glassifsh-pfl - grizzly - grizzly-npn - jackson-dataformat-xml (cc: lef, dchen) - jandex-maven-plugin (cc: lef) - java-oauth (cc: lef) - jboss-connector-1.6-api (cc: lef, gil) - jboss-jaspi-1.1-api (cc: lef) - jersey (cc: dchen, gwei3) - mimepull (cc: lef, java-sig) - mustache-java (cc: dchen, lef, mizdebsk) - netty3 (cc: lef, jerboaa) - picketbox (cc: lef, gil) - picketbox-commons (cc: lef, gil) - picketbox-xacml (cc: lef, gil) - rxjava (cc: rfenkhuber) - simple I intend to orphan them all on Friday unless someone else wants these packages. Thanks, - Alex ___ devel mailing list -- devel@lists.fedoraproject.org To unsubscribe send an email to devel-le...@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@lists.fedoraproject.org
Re: List of Python 2 packages to be removed mid-November
Andrea Musuruane wrote: > On Tue, Oct 29, 2019 at 4:25 PM Miro Hrončok wrote: >> bruno >>qgis >> (BuildRequires: python2-sip-devel → PY2) >> > > It seems there is a wrong dependency in the spec file: > > BuildRequires: sip-devel > > Shouldn't this be BuildRequires: python3-sip-devel? Yep, looks like it, I have pinged Volker Fröhlich (volter) on IRC. Kevin Kofler ___ devel mailing list -- devel@lists.fedoraproject.org To unsubscribe send an email to devel-le...@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@lists.fedoraproject.org
Re: List of Python 2 packages to be removed mid-November
Miro Hrončok writes: > defolos >pyxattr > python2-pyxattr (→ PY2) I will drop the python2 subpackage. > dodji >offlineimap > (→ PY2) Can we get an exception for this please? Afaik offlineimap is not ready for python3 yet and I'd hate it to disappear from Fedora. signature.asc Description: PGP signature ___ devel mailing list -- devel@lists.fedoraproject.org To unsubscribe send an email to devel-le...@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@lists.fedoraproject.org
Re: [Mindshare] Re: [Ambassadors] Re: FOSDEM
Since there are lot of people who are showing interest, may be someone should submit the request for a booth (probably who has done it before) before the deadline. We can figure out who can be the booth coordinator and stuff later on. On Mon, Oct 28, 2019 at 11:47 AM Brian (bex) Exelbierd wrote: > > > > On Mon, Oct 28, 2019 at 4:15 PM Mariana Balla > wrote: >> >> Hello everyone, >> >> I'd be happy to help with the Fedora booth at FOSDEM 2020. Other than the >> conference days, I can help with the preparations in advance (e.g. hotel >> logistics). >> >> >> Regarding the booth submission, I could help on that as well (if not been >> submitted yet). As far as I know the deadline is by the end of this week. > > > AFAIK the booth has NOT been submitted. > > regards, > > bex > >> >> Best, >> Mariana >> >> >> On Fri, Oct 25, 2019 at 1:03 PM Aleksandra Fedorova >> wrote: >>> >>> I created a wiki page for FOSDEM 2020 [1]. >>> >>> Feel free to contribute and add yourself to the attendees list. >>> >>> [1] https://fedoraproject.org/wiki/FOSDEM_2020 >>> >>> On Wed, Oct 16, 2019 at 6:24 PM Brian (bex) Exelbierd >>> wrote: >>> > >>> > Hi All, >>> > >>> > I haven't heard anyone mention FOSDEM yet. Booth applications are due >>> > soon and I'd like to see us coordinate again with our friends in CentOS. >>> > Is there anyone interested in owning this? If so, can you put together a >>> > proposal for Mindshare? >>> > >>> > regards, >>> > >>> > bex >>> > -- >>> > Brian "bex" Exelbierd (he/him/his) >>> > Fedora Community Action & Impact Coordinator >>> > @bexelbie | http://www.winglemeyer.org >>> > bexel...@redhat.com | b...@pobox.com >>> > ___ >>> > ambassadors mailing list -- ambassad...@lists.fedoraproject.org >>> > To unsubscribe send an email to ambassadors-le...@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/ambassad...@lists.fedoraproject.org >>> >>> >>> >>> -- >>> -- >>> Aleksandra Fedorova >>> bookwar >>> ___ >>> ambassadors mailing list -- ambassad...@lists.fedoraproject.org >>> To unsubscribe send an email to ambassadors-le...@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/ambassad...@lists.fedoraproject.org >> >> ___ >> Mindshare mailing list -- mindsh...@lists.fedoraproject.org >> To unsubscribe send an email to mindshare-le...@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/mindsh...@lists.fedoraproject.org > > -- > Brian "bex" Exelbierd (he/him/his) > Fedora Community Action & Impact Coordinator > @bexelbie | http://www.winglemeyer.org > bexel...@redhat.com | b...@pobox.com > ___ > devel mailing list -- devel@lists.fedoraproject.org > To unsubscribe send an email to devel-le...@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@lists.fedoraproject.org ___ devel mailing list -- devel@lists.fedoraproject.org To unsubscribe send an email to devel-le...@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@lists.fedoraproject.org
Re: List of Python 2 packages to be removed mid-November
On 30. 10. 19 14:47, Dan Čermák wrote: Miro Hrončok writes: defolos pyxattr python2-pyxattr (→ PY2) I will drop the python2 subpackage. Please coordinate that in https://bugzilla.redhat.com/show_bug.cgi?id=1738182 dodji offlineimap (→ PY2) Can we get an exception for this please? Afaik offlineimap is not ready for python3 yet and I'd hate it to disappear from Fedora. Please coordinate that in https://bugzilla.redhat.com/show_bug.cgi?id=1751496 -- Miro Hrončok -- Phone: +420777974800 IRC: mhroncok ___ devel mailing list -- devel@lists.fedoraproject.org To unsubscribe send an email to devel-le...@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@lists.fedoraproject.org
Official font
Hi all, I incidentally discovered today that, since quite recently, there's a Red Hat font [1]. And this led me to think about the popularity of the Ubuntu font, you know, and how nice would be to have a nice catchy official Fedora font integrated into the distro... I'm just thinking aloud, because I don't know anything about font design. But maybe someone picks up the gauntlet... ;-) [1] https://github.com/RedHatOfficial/RedHatFont Cheers, Iñaki ___ devel mailing list -- devel@lists.fedoraproject.org To unsubscribe send an email to devel-le...@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@lists.fedoraproject.org
Re: Official font
On Wed, 2019-10-30 at 16:58 +0100, Iñaki Ucar wrote: > Hi all, > > I incidentally discovered today that, since quite recently, there's a > Red Hat font [1]. And this led me to think about the popularity of > the > Ubuntu font, you know, and how nice would be to have a nice catchy > official Fedora font integrated into the distro... I'm just thinking > aloud, because I don't know anything about font design. But maybe > someone picks up the gauntlet... ;-) > > [1] https://github.com/RedHatOfficial/RedHatFont There is official Fedora font, used at least in the official Fedora presentation templates: https://fedoraproject.org/wiki/Presentations/Template Not sure how widely is it used elsewhere, but I certainly used that template few times. Regards, -- Jakub Jelen Senior Software Engineer Security Technologies Red Hat, Inc. ___ devel mailing list -- devel@lists.fedoraproject.org To unsubscribe send an email to devel-le...@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@lists.fedoraproject.org
Re: Official font
On Wed, 30 Oct 2019 at 11:59, Iñaki Ucar wrote: > > Hi all, > > I incidentally discovered today that, since quite recently, there's a > Red Hat font [1]. And this led me to think about the popularity of the > Ubuntu font, you know, and how nice would be to have a nice catchy > official Fedora font integrated into the distro... I'm just thinking > aloud, because I don't know anything about font design. But maybe > someone picks up the gauntlet... ;-) > Font designs are hard. You have multiple copyright and similar legal rights which you have to both deal with and contract out to. Font work comes up in waves.. the last wave was about 6 to 8 years ago when people were working on various fonts for Fedora.. but then it sort of hit a fallow time because it takes a continual effort of interested and knowledgeable participants. > [1] https://github.com/RedHatOfficial/RedHatFont > > Cheers, > Iñaki > ___ > devel mailing list -- devel@lists.fedoraproject.org > To unsubscribe send an email to devel-le...@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@lists.fedoraproject.org -- Stephen J Smoogen. ___ devel mailing list -- devel@lists.fedoraproject.org To unsubscribe send an email to devel-le...@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@lists.fedoraproject.org
Re: Official font
On Wed, 30 Oct 2019 at 17:42, Jakub Jelen wrote: > > On Wed, 2019-10-30 at 16:58 +0100, Iñaki Ucar wrote: > > Hi all, > > > > I incidentally discovered today that, since quite recently, there's a > > Red Hat font [1]. And this led me to think about the popularity of > > the > > Ubuntu font, you know, and how nice would be to have a nice catchy > > official Fedora font integrated into the distro... I'm just thinking > > aloud, because I don't know anything about font design. But maybe > > someone picks up the gauntlet... ;-) > > > > [1] https://github.com/RedHatOfficial/RedHatFont > > There is official Fedora font, used at least in the official Fedora > presentation templates: > > https://fedoraproject.org/wiki/Presentations/Template > > Not sure how widely is it used elsewhere, but I certainly used that > template few times. "Comfortaa is used for titles and Droid Sans is used for body text." Kind of, but not quite what the "Ubuntu family" of fonts means to Ubuntu, and what I had in mind. But I didn't know about this template either, thanks. Iñaki ___ devel mailing list -- devel@lists.fedoraproject.org To unsubscribe send an email to devel-le...@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@lists.fedoraproject.org
Review swap?
I could use a quick review for a new R package: R-Rhtslib https://bugzilla.redhat.com/show_bug.cgi?id=1767062 Can do a review or other packaging/legal/license favors in trade. Thanks, Tom ___ devel mailing list -- devel@lists.fedoraproject.org To unsubscribe send an email to devel-le...@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@lists.fedoraproject.org
Minimization Objective report
This is the Minimization Objective [0] update. Status: Discovery phase == Next phase approval == Next phase proposal [1] to be voted on by Council, starting tomorrow. Feedback still collected in the PR [2]. == Polkit and Mojzs == Finished investigation and send recommended changes to postgresql container and rpm team. - Investigated pokit ( .5 MB) and mozjs60 (30 MB) -- mozjs only needed for configurations -- Two major proposals in the past trying to fix the problem. --- Use duktape ( .7MB ) for javascript --- Use a different format but maintain compatibility -- Need to talk to fedora/rhel polkit maintainers -- fun fact: gentoo users, who had debug set, had 500M mozjs60 == Square 1 and Minimization == Looking at the recent Square 1 proposal [3], thinking if that should be included under the Minimization umbrella. == How to get involved == See if there is anything interesting to you on action plan [42], or reach out with something you think is useful but is missing there. Open a ticket in the tracker [43] or discuss in #fedora-devel on IRC. Cheers, Adam [0] Objective: https://docs.fedoraproject.org/en-US/minimization/ [1] Next phase proposal (post): https://communityblog.fedoraproject.org/extending-the-minimization-objective/ [2] Next phase proposal (PR): https://pagure.io/Fedora-Council/council-docs/pull-request/64 [3] Square 1 proposal: https://lists.fedoraproject.org/archives/list/devel@lists.fedoraproject.org/thread/2V4Q7P3KN6O52NOBLXFRCKHZ27ZATF2G/#2V4Q7P3KN6O52NOBLXFRCKHZ27ZATF2G [42] Action plan: https://docs.fedoraproject.org/en-US/minimization/action-plan/ [43] Issue tracker: https://pagure.io/minimization/issues -- Adam Šamalík --- Senior Software Engineer Red Hat ___ devel mailing list -- devel@lists.fedoraproject.org To unsubscribe send an email to devel-le...@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@lists.fedoraproject.org
Re: Review swap?
On Wed, Oct 30, 2019 at 1:17 PM Tom Callaway wrote: > > I could use a quick review for a new R package: R-Rhtslib > > https://bugzilla.redhat.com/show_bug.cgi?id=1767062 > > Can do a review or other packaging/legal/license favors in trade. I'll swap you for https://bugzilla.redhat.com/show_bug.cgi?id=1766771 ___ devel mailing list -- devel@lists.fedoraproject.org To unsubscribe send an email to devel-le...@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@lists.fedoraproject.org
Fedora 32 System-Wide Change proposal: Annobin Used By Bodhi
https://fedoraproject.org/wiki/Changes/ANNOBIN-used-by-bodhi
= Annobin Used By Bodhi =
== Summary ==
Use the annocheck program from the annobin package to produce an
analysis of the security hardening of a compiled package when
reviewing a Bodhi update.
== Owner ==
* Name: Nick Clifton [https://fedoraproject.org/wiki/User:Nickc]
* Email: ni...@redhat.com
== Detailed Description ==
The annobin package provides two components, a plugin for gcc that
records details about how a program was compiled and an analyser that
uses this information to produce a report on the security hardening
status of the compiled program. Currently the plugin is being used as
part of the build process for Fedora packages (when they are built
using gcc), but the analysing program is not being run. This proposal
is to have the analyser (called annocheck) run when creating
information for review by the Bodhi update process, possibly allowing
an update to be delayed until the security issues are addressed.
The analyser currently looks for the following items:
* Lazy binding must not have been enabled via the linker option "-z
lazy". Instead the @option{-z now} option must have been used.
* The program must not have a stack in an executable region of memory.
* The relocations for the GOT table must be read only.
* No program segment should have all three of the read, write and
execute permission bits set.
* There should be no relocations against executable code.
* The runpath information used to locate shared libraries at runtime
must only include directories rooted at /usr.
* The program must have been compiled with the
-fstack-protector-strong option enabled, and with -D_FORTIFY_SOURCE=2
specified. It must also have been compiled at at least optimisation
level 2.
* Dynamic executables must have a dynamic segment.
* Shared libraries must have been compiled with -fPIC or-fPIE but not -static.
* Dynamic executables must have been compiled with -fPIE and linked with -pie.
* Program which use exception handling must have been compiled with
-fexceptions enabled and with -D_GLIBCXX_ASSERTIONS specified.
* If available the -fstack-clash-protection must have been used.
* If available the -fcf-protection=full must have been used.
* For i686 binaries, the -mstackrealign option must have been specified.
* The program must have been compiled with the -D_FORTIFY_SOURCE=2
command line option specified.
* The program must have been compiled with at least -O2 optimisation enabled.
* The program must not have any relocations that are held in a writable section.
* For x86_64 binaries, check that -fcf-protection has been enabled.
Note - I do not know *how* to add a run of the annocheck program to
the Bodhi process. This change request is about asking that such a
thing be added.
== Benefit to Fedora ==
Establishing good security practices when building packages will help
Fedora remain a front running Linux distribution. By providing a way
to review the security hardening status of packages, this update will
help to ensure that these practices continue.
Note - the intention is that if this change is successful, and useful,
then a future change request would be made to include the security
checking as part of the actual package build process, and to have
packages fail to complete building if they do not pass the security
checks.
== Scope ==
* Proposal owners:
In theory there is very little that I can do personally. I do not
have the knowledge to change the Bodhi process myself, so I will have
to rely upon someone else to do that. I am familiar with the annobin
package however, so any changes that are needed to it I will be happy
to make.
* Other developers:
Add an invocation of the annocheck program to the Bodhi build approval
process and make its output available to reviewers.
Annocheck can be invoked simply as "annocheck " although
there are a set of command line options to extend and modify its
behaviour. Annocheck understands the rpm file format, as well as
shared and static libraries and executable binaries. It can also be
helpful to provide annocheck with access to the debug information for
a binary or rpm, if that has been placed into a separate file.
* Release engineering: https://pagure.io/fedora-ci/general/issue/78
No mass rebuild is required.
* Policies and guidelines:
It is desirable that the packaging guidelines be updated to describe
the security hardening features examined by annocheck. (If they are
not already mentioned in the guidelines).
* Trademark approval: N/A (not needed for this Change)
== Upgrade/compatibility impact ==
This change should have no effect on upgrading Fedora, nor should it
introduce any compatibility problems.
== How To Test ==
Submit a package for Bodhi review and see if the annocheck data is
added to the page.
No special hardware is needed for this test, but it might involve the
use of a dummy package or a dummy instance of Bodhi in order to test
the behaviour before
Fedora 32 System-Wide Change proposal: iptables-nft-default
https://fedoraproject.org/wiki/Changes/iptables-nft-default == Summary == Make iptables-nft the preferred iptables variant. == Owner == * Name: [[User:psutter| Phil Sutter]] * Email: psut...@redhat.com == Detailed Description == iptables-nft package provides alternative implementations of iptables, ip6tables, ebtables and arptables and associated save and restore commands. These use nftables internally while providing the same look'n'feel as the original tools. Users may choose between both implementations using alternatives tool. Upstream considers the traditional implementations legacy and therefore renamed the binaries adding '-legacy' suffix. In Fedora, same has been done to arptables and ebtables packages, namely renaming them to arptables-legacy and ebtables-legacy. Legacy iptables and ip6tables remain in iptables package, which in fact is the only one other packages depend upon. To change the status quo, two measures are planned: === Raise priority of nft-variants in alternatives === Currently, legacy variants are installed with priority 10 and nft variants with priority 5. This must be changed as otherwise installing iptables-legacy in a system with iptables-nft installed would change the active alternative (since they are in automatic mode by default). On the other hand, existing systems using legacy variants should not be changed by a system update. Therefore nft variants' priorities should be chosen to match legacy ones. === Rename iptables package === New name should be iptables-legacy which aligns with ebtables and arptables and reflects upstream status. To resolve dependencies, Provides: iptables statement will be added to iptables-nft package. This should automatically change the default variant to nft. == Benefit to Fedora == * RHEL8 ships nft-variants exclusively, make Fedora align with that by default while still providing the option to fall back to legacy tools. * New features and improvements are likely to hit nft-variants due to the possibility nftables backend allows for. Although at this point some legacy features (e.g. ebtables among match) are still missing, others are already there (like, e.g. xtables-monitor tool) or are being upstreamed right now (improved tool performance when dealing with large rulesets). == Scope == * Proposal owners: Changes are rather simple: Rename iptables package, add Provides: line to iptables-nft package, change priorities used when calling alternatives. * Other developers: N/A The changed tools may cause regressions among packages using them and it affects only new installations (or those manually switched over). So while no explicit effort is required from them, they should be made aware of the change so they take a possible regression in iptables into account, quickly test against legacy variant and file a ticket (or complain to the right person) if that fixes the problem. * Release engineering: [https://pagure.io/releng/issue/8934 #8934] * Policies and guidelines: No change required * Trademark approval: N/A (not needed for this Change) == Upgrade/compatibility impact == Due to the package rename and Provides: line, upgrades will pull in iptables-nft package. But due to the equal alternatives priorities, existing choices won't be changed and so existing installations shouldn't be harmed (apart from forced installation of iptables-nft package). Sadly, there are a few known issues, like e.g. missing support for ebtables broute table or among match and a few iptables targets/matches. Users depending on such features are advised to install iptables-legacy package and switch variants using alternatives. == How To Test == Any users of iptables/ebtables/arptables should switch to nft-variants using alternatives tool (if necessary) and check that everything works as before. Any issues should be reported despite the known compatibility issues described above since knowledge about who uses the missing features is valuable information for both up- and downstream. == User Experience == Ideally look'n'feel shouldn't change. Since iptables-nft does not need a lock file anymore, no problems with stale xtables-lock or parallel iptables calls in different mount namespaces are expected anymore. Given the changes currently being upstreamed, users dealing with large rulesets should see a performance increase when manipulating the ruleset (lower run-times of iptables or iptables-restore, packet processing speed should not really change). == Dependencies == Other packages depending on iptables: * NFStest * clatd * ctdb * fail2ban-server * firewalld * fwsnort * iptstate * libvirt-daemon-driver-network * libvirt-daemon-driver-nwfilter * moby-engine * nfacct * origin * podman * psad * python3-ipatests * ravada * rkt * shorewall * shorewall-init * shorewall-lite * shorewall6 * shorewall6-lite * sshuttle * sslsplit * ufw Since nft-variants are supposed to be drop-in replacements, no outside contribution is needed in order to perform this change. == C
Fedora 32 System-Wide Change proposal: Translation platform migration to Weblate
https://fedoraproject.org/wiki/Changes/Translation_platform_migration_to_Weblate
= Translation platform migration to Weblate =
== Summary ==
This migration was decided at Flock 2019 in Budapest, it is mandatory
as development and maintenance of Zanata — the previous translation
platform — ceased in 2018. More information are available here:
https://communityblog.fedoraproject.org/fedora-localization-platform-migrates-to-weblate/
Link to release process is to make sure the information is spread
across all dependent projects, including Documentation and Websites.
== Owner ==
* Owner: the [[L10N]] group (#fedora-i18n on freenode)
* Primary contact: [[User:jibecfed|Jean-Baptiste Holcroft]]
* Email:
[https://lists.fedoraproject.org/archives/list/tr...@lists.fedoraproject.org/
localization mailing list]
== Detailed Description ==
Make sure all existing Zanata project have been informed (upstream
ticket created) and that all priority packages have migrated.
We created a template for [[L10N_Move_to_Weblate/Message_for_upstream_project]].
The [https://fedora.zanata.org/version-group/view/PriorityPackages
list of priority packages is defined in Zanata], it contains websites,
anaconda, dnf and many others...
== Benefit to Fedora ==
First objective is to lower the risk of having no translation platform
if Zanata crashes.
Second objective is to provide a suited tool for localization
community to be part of our processes again:
* be closer to upstream activity by directly interacting with git repositories
** this also lower upstream requirements to interact with our
translation platform (no dependencies required as it interact with git
repos)
** this helps upstream to see localization contributions
** this allows translator to get notification when new strings
* be able to localize our documentation (we decided to make it
compatible with Weblate directly)
* the tool will [https://pagure.io/fedora-infrastructure/issue/8291
publish on Fedora messaging]
** allows community statistics
** allows badges creation
== Scope ==
* Proposal owners:
Open a ticket for each upstream project.
* Other developers:
answer the message for upstream project and eventually create
appropriate git repositories:
{{admon/important | Questions to answer by upstream
|{{:L10N_Move_to_Weblate/Message_for_upstream_project
* Release engineering: [https://pagure.io/releng/issue/8947 #8947]
* Policies and guidelines: N/A (not needed for this Change)
* Trademark approval: N/A (not needed for this Change)
== Upgrade/compatibility impact ==
N/A (this change impacts our processes, not our deliverable)
== How To Test ==
For projects using the translation platform: make sure translation
commits are part of the release included in Fedora 32.
Example for DNF:
* Open the DNF git repository
* Find folder containing localization file (usually the '''po''' folder)
* Look at commit history and search for, commits will start with:
"Translated using Weblate"
([https://github.com/mike-fabian/ibus-typing-booster/pull/57/commits/3ffccedc89436077890b08a566274316102b4577
example with French language on ibus typing booster]
== User Experience ==
No impact.
== Dependencies ==
N/A (not a System Wide Change)
== Contingency Plan ==
* Contingency mechanism: Localization team will keep using Zanata
* Blocks release? Yes, if websites and priority packages do not use
the new translation platform.
* Blocks product? Yes
== Documentation ==
[[L10N Move to Weblate]]
--
Ben Cotton
He / Him / His
Fedora Program Manager
Red Hat
TZ=America/Indiana/Indianapolis
___
devel mailing list -- devel@lists.fedoraproject.org
To unsubscribe send an email to devel-le...@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@lists.fedoraproject.org
Re: Fedora 32 System-Wide Change proposal: Annobin Used By Bodhi
Hey Nick,
Is this change about stopping any builds which do not pass annocheck
test from going to stable repository or just adding new check in
there? If latter, I don't think it qualifies as a system-wide change.
On Wed, Oct 30, 2019 at 10:05 PM Ben Cotton wrote:
>
> https://fedoraproject.org/wiki/Changes/ANNOBIN-used-by-bodhi
>
> = Annobin Used By Bodhi =
>
> == Summary ==
> Use the annocheck program from the annobin package to produce an
> analysis of the security hardening of a compiled package when
> reviewing a Bodhi update.
>
> == Owner ==
> * Name: Nick Clifton [https://fedoraproject.org/wiki/User:Nickc]
> * Email: ni...@redhat.com
>
> == Detailed Description ==
> The annobin package provides two components, a plugin for gcc that
> records details about how a program was compiled and an analyser that
> uses this information to produce a report on the security hardening
> status of the compiled program. Currently the plugin is being used as
> part of the build process for Fedora packages (when they are built
> using gcc), but the analysing program is not being run. This proposal
> is to have the analyser (called annocheck) run when creating
> information for review by the Bodhi update process, possibly allowing
> an update to be delayed until the security issues are addressed.
>
> The analyser currently looks for the following items:
>
> * Lazy binding must not have been enabled via the linker option "-z
> lazy". Instead the @option{-z now} option must have been used.
>
> * The program must not have a stack in an executable region of memory.
>
> * The relocations for the GOT table must be read only.
>
> * No program segment should have all three of the read, write and
> execute permission bits set.
>
> * There should be no relocations against executable code.
>
> * The runpath information used to locate shared libraries at runtime
> must only include directories rooted at /usr.
>
> * The program must have been compiled with the
> -fstack-protector-strong option enabled, and with -D_FORTIFY_SOURCE=2
> specified. It must also have been compiled at at least optimisation
> level 2.
>
> * Dynamic executables must have a dynamic segment.
>
> * Shared libraries must have been compiled with -fPIC or-fPIE but not -static.
>
> * Dynamic executables must have been compiled with -fPIE and linked with -pie.
>
> * Program which use exception handling must have been compiled with
> -fexceptions enabled and with -D_GLIBCXX_ASSERTIONS specified.
>
> * If available the -fstack-clash-protection must have been used.
>
> * If available the -fcf-protection=full must have been used.
>
> * For i686 binaries, the -mstackrealign option must have been specified.
>
> * The program must have been compiled with the -D_FORTIFY_SOURCE=2
> command line option specified.
>
> * The program must have been compiled with at least -O2 optimisation enabled.
>
> * The program must not have any relocations that are held in a writable
> section.
>
> * For x86_64 binaries, check that -fcf-protection has been enabled.
>
>
> Note - I do not know *how* to add a run of the annocheck program to
> the Bodhi process. This change request is about asking that such a
> thing be added.
>
> == Benefit to Fedora ==
>
> Establishing good security practices when building packages will help
> Fedora remain a front running Linux distribution. By providing a way
> to review the security hardening status of packages, this update will
> help to ensure that these practices continue.
>
> Note - the intention is that if this change is successful, and useful,
> then a future change request would be made to include the security
> checking as part of the actual package build process, and to have
> packages fail to complete building if they do not pass the security
> checks.
>
> == Scope ==
> * Proposal owners:
> In theory there is very little that I can do personally. I do not
> have the knowledge to change the Bodhi process myself, so I will have
> to rely upon someone else to do that. I am familiar with the annobin
> package however, so any changes that are needed to it I will be happy
> to make.
>
>
> * Other developers:
> Add an invocation of the annocheck program to the Bodhi build approval
> process and make its output available to reviewers.
> Annocheck can be invoked simply as "annocheck " although
> there are a set of command line options to extend and modify its
> behaviour. Annocheck understands the rpm file format, as well as
> shared and static libraries and executable binaries. It can also be
> helpful to provide annocheck with access to the debug information for
> a binary or rpm, if that has been placed into a separate file.
>
>
> * Release engineering: https://pagure.io/fedora-ci/general/issue/78
>
> No mass rebuild is required.
>
> * Policies and guidelines:
> It is desirable that the packaging guidelines be updated to describe
> the security hardening features examined by annocheck. (If they are
> not already mentioned in the guideli
Re: Fedora 32 System-Wide Change proposal: Annobin Used By Bodhi
On Wed, Oct 30, 2019 at 05:01:55PM -0400, Ben Cotton wrote: > Note - I do not know *how* to add a run of the annocheck program to > the Bodhi process. This change request is about asking that such a > thing be added. I think the best approach to this would be turn it into a test that can be run in the CI and used in the gating process. The result would be only indirectly visible in bodhi (as part of the test results). No special support would be added in bodhi. Essentially, you'd provide a standard test that various packages could use. Then it would be easier to override in specific packages to weed out false positives. Zbyszek ___ devel mailing list -- devel@lists.fedoraproject.org To unsubscribe send an email to devel-le...@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@lists.fedoraproject.org
Re: Official font
On 2019-10-30 9:54 a.m., Iñaki Ucar wrote: On Wed, 30 Oct 2019 at 17:42, Jakub Jelen wrote: On Wed, 2019-10-30 at 16:58 +0100, Iñaki Ucar wrote: Hi all, I incidentally discovered today that, since quite recently, there's a Red Hat font [1]. And this led me to think about the popularity of the Ubuntu font, you know, and how nice would be to have a nice catchy official Fedora font integrated into the distro... I'm just thinking aloud, because I don't know anything about font design. But maybe someone picks up the gauntlet... ;-) [1] https://github.com/RedHatOfficial/RedHatFont There is official Fedora font, used at least in the official Fedora presentation templates: https://fedoraproject.org/wiki/Presentations/Template Not sure how widely is it used elsewhere, but I certainly used that template few times. "Comfortaa is used for titles and Droid Sans is used for body text." Kind of, but not quite what the "Ubuntu family" of fonts means to Ubuntu, and what I had in mind. But I didn't know about this template either, thanks. Hello Iñaki, Comfortaa was the default in the past. Montserrat (already packaged in the repository) is the official fonts used by Design team. The linked template is outdated and on the way of revamp to use Montserrat [2]. Reference -- [1] https://apps.fedoraproject.org/packages/julietaula-montserrat-fonts [2] https://pagure.io/design/issue/629 -- Luya Tshimbalanga Fedora Design Team Fedora Design Suite maintainer ___ devel mailing list -- devel@lists.fedoraproject.org To unsubscribe send an email to devel-le...@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@lists.fedoraproject.org
Re: List of Python 2 packages to be removed mid-November
On 2019-10-29 11:39 p.m., Miro Hrončok wrote: On 30. 10. 19 6:52, Luya Tshimbalanga wrote: On 2019-10-29 8:24 a.m., Miro Hrončok wrote: luya scribus-generator (→ scribus → PY2) Already switched to python3 : https://apps.fedoraproject.org/packages/scribus-generator/sources/spec/ Unfortunately, scribus-generator depends on scribus, scribus depends on Python 2. If scribus doesn't have exception, it will be removed. If scribus gets removed, scribus-generator doesn't install and will be removed. Please, work with the scribus maintainer: https://bugzilla.redhat.com/show_bug.cgi?id=1738174 (Note that the previous maintainer haven't reply, it was orphaned, the new maintainer unoprhaned it, didn't reply. CCing here.) Thanks for the head ups. I was unaware Scribus was without maintainer at the time as I would gladly do the task should the current one fail to respond (I have COPR repository for both Scribus 1.5.5 and the snapshot release) -- Luya Tshimbalanga Fedora Design Team Fedora Design Suite maintainer ___ devel mailing list -- devel@lists.fedoraproject.org To unsubscribe send an email to devel-le...@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@lists.fedoraproject.org
Re: List of Python 2 packages to be removed mid-November
On Tue, 2019-10-29 at 16:24 +0100, Miro Hrončok wrote: > sergiomb >gdesklets > (→ PY2) Since you want drop python2-gnome ... >gflags > (BuildRequires: python2-setuptools → PY2) fixed >python-GeoIP > python2-GeoIP (→ PY2) python-GeoIP have also python3-GeoIP >python-gammu > python2-gammu (→ PY2) python-gammu have also python3-gammu These last two package are also available on epel 7 . I think we should add conditionals, with python 2 on epel 7 with python 3 on Fedora, but I'm too busy ATM . Thanks, -- Sérgio M. B. ___ devel mailing list -- devel@lists.fedoraproject.org To unsubscribe send an email to devel-le...@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@lists.fedoraproject.org
Re: Next F31 push?
On Fri, 2019-10-18 at 10:54 -0400, Matthew Miller wrote: > On Thu, Oct 17, 2019 at 11:02:51PM -0700, Adam Williamson wrote: > > We do tweak the release schedule every so often, right now the > > freeze > > periods are fairly long compared to the historical average. I do > > think > > that's given us a benefit in terms of how little slippage we've had > > for > > the last few releases, though; we could always consider freezing a > > bit > > later, but it might result in us slipping more... > > I'm in favor of continuing with the airlines' "this flight will take > three > hours -- wow, look, we're early again!" approach. Users and > downstreams > really appreciate the predictability. yeah , the marketing argument. So to not risk a (big) delay, why not test it ? whether we would have a big delay or not ? and freeze F31 again to get a really stable release, the F31.1 . Thanks, > -- > Matthew Miller > > Fedora Project Leader > ___ > devel mailing list -- devel@lists.fedoraproject.org > To unsubscribe send an email to devel-le...@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@lists.fedoraproject.org -- Sérgio M. B. ___ devel mailing list -- devel@lists.fedoraproject.org To unsubscribe send an email to devel-le...@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@lists.fedoraproject.org
Re: Fedora 32 System-Wide Change proposal: Annobin Used By Bodhi
Hi, Ben Cotton writes: > The annobin package provides two components, a plugin for gcc that > records details about how a program was compiled and an analyser that > uses this information to produce a report on the security hardening > status of the compiled program. Currently the plugin is being used as > part of the build process for Fedora packages (when they are built > using gcc), but the analysing program is not being run. This proposal > is to have the analyser (called annocheck) run when creating > information for review by the Bodhi update process, possibly allowing > an update to be delayed until the security issues are addressed. I currently run annocheck manually on my builds, so I am a fan of this change. But I think it's worth calling out one limitation: this currently mostly works with gcc. clang is a bit behind in implementing some of the features that annocheck looks at. With Fedora 30, annocheck would cleanly skip most of clang-produced binaries. With Fedora 31, clang seems to insert some of the meta-data that annocheck looks for, but doesn't quite implement to match the gcc standard. I have recently run into failures flagged by annocheck that I need to dig into on Fedora 31. > It is desirable that the packaging guidelines be updated to describe > the security hardening features examined by annocheck. (If they are > not already mentioned in the guidelines). https://docs.fedoraproject.org/en-US/packaging-guidelines/#_compiler_flags has some of this, but not all. It seems to me like annocheck is more strict than the current packaging guidelines. Thanks, Omair -- PGP Key: B157A9F0 (http://pgp.mit.edu/) Fingerprint = 9DB5 2F0B FD3E C239 E108 E7BD DF99 7AF8 B157 A9F0 ___ devel mailing list -- devel@lists.fedoraproject.org To unsubscribe send an email to devel-le...@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@lists.fedoraproject.org
Re: Next F31 push?
On Fri, Oct 18, 2019 at 4:05 PM Matthew Miller wrote: > > On Fri, Oct 18, 2019 at 09:13:22PM +0200, Kevin Kofler wrote: > > This would be a lot less of an issue if we were more actively promoting the > > respins that are already being done. > > Yeah, this is a Fedora Council goal -- we'd like for that SIG to easily be > able to make them in infrastructure, and then present them in a clear way. > > > I never install from GA images (except before the first respin, obviously) > > because it is just pointless to install an image just to have to upgrade > > half of the distro immediately afterwards. > > I usually use the netinstall image for basically the same reason. > I stopped using the netinstall image because it randomly installs kernel-debug instead of kernel due to us not fixing the bug with selecting kernel variants[1]. Starting from live media and upgrading avoids that problem... [1]: https://bugzilla.redhat.com/show_bug.cgi?id=1228897 ___ devel mailing list -- devel@lists.fedoraproject.org To unsubscribe send an email to devel-le...@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@lists.fedoraproject.org
[Test-Announce] Fedora 32 Rawhide 20191030.n.1 nightly compose nominated for testing
Announcing the creation of a new nightly release validation test event for Fedora 32 Rawhide 20191030.n.1. Please help run some tests for this nightly compose if you have time. For more information on nightly release validation testing, see: https://fedoraproject.org/wiki/QA:Release_validation_test_plan Test coverage information for the current release can be seen at: https://www.happyassassin.net/testcase_stats/32 You can see all results, find testing instructions and image download locations, and enter results on the Summary page: https://fedoraproject.org/wiki/Test_Results:Fedora_32_Rawhide_20191030.n.1_Summary The individual test result pages are: https://fedoraproject.org/wiki/Test_Results:Fedora_32_Rawhide_20191030.n.1_Installation https://fedoraproject.org/wiki/Test_Results:Fedora_32_Rawhide_20191030.n.1_Base https://fedoraproject.org/wiki/Test_Results:Fedora_32_Rawhide_20191030.n.1_Server https://fedoraproject.org/wiki/Test_Results:Fedora_32_Rawhide_20191030.n.1_Cloud https://fedoraproject.org/wiki/Test_Results:Fedora_32_Rawhide_20191030.n.1_Desktop https://fedoraproject.org/wiki/Test_Results:Fedora_32_Rawhide_20191030.n.1_Security_Lab Thank you for testing! -- Mail generated by relvalconsumer: https://pagure.io/fedora-qa/relvalconsumer ___ test-announce mailing list -- test-annou...@lists.fedoraproject.org To unsubscribe send an email to test-announce-le...@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/test-annou...@lists.fedoraproject.org ___ devel mailing list -- devel@lists.fedoraproject.org To unsubscribe send an email to devel-le...@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@lists.fedoraproject.org
Re: Upgrade F30->F31 fails on speech-tools-libs
On 10/30/19 3:44 AM, Neal Becker wrote: [nbecker@nbecker2 ~]$ sudo dnf remove festival-speechtools-libs Dependencies resolved. > Removing: festival-speechtools-libs x86_64 1.2.96-39.fc29 @fedora 3.7 M Removing dependent packages: festival-freebsoft-utils noarch 0.10-15.fc30 @fedora 121 k kdeaccessibility noarch 1:4.14.3-3.fc24 @@commandline 0 The above list are the only ones that are forced to remove. Removing unused dependencies: The rest are packages that have become leaves that nothing requires, so by default dnf will remove them as well. You can use the "--noautoremove" option to avoid that. ___ devel mailing list -- devel@lists.fedoraproject.org To unsubscribe send an email to devel-le...@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@lists.fedoraproject.org
Re: Upgrade F30->F31 fails on speech-tools-libs
On Wed, 2019-10-30 at 10:52 +, Zbigniew Jędrzejewski-Szmek wrote: > On Wed, Oct 30, 2019 at 10:44:39AM -, Neal Becker wrote: > > Error: Transaction test error: > > file /usr/lib64/libeststring.so.1.2 from install of speech-tools- > > libs-2.5-8.fc31.x86_64 conflicts with file from package festival- > > speechtools-libs-1.2.96-39.fc29.x86_64 > > https://bodhi.fedoraproject.org/updates/FEDORA-2019-cc9c0dd5a8 > > Please give karma. and also need this one [1] [1] https://bodhi.fedoraproject.org/updates/FEDORA-2019-50ec17744b > Zbyszek > ___ > devel mailing list -- devel@lists.fedoraproject.org > To unsubscribe send an email to devel-le...@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@lists.fedoraproject.org -- Sérgio M. B. ___ devel mailing list -- devel@lists.fedoraproject.org To unsubscribe send an email to devel-le...@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@lists.fedoraproject.org
Fedora-Rawhide-20191030.n.1 compose check report
No missing expected images. Compose FAILS proposed Rawhide gating check! 1 of 45 required tests failed, 2 results missing Unsatisfied gating requirements that could not be mapped to openQA tests: FAILED: compose.cloud.all MISSING: fedora.Workstation-boot-iso.x86_64.64bit - compose.install_default MISSING: fedora.Workstation-boot-iso.x86_64.uefi - compose.install_default Failed openQA tests: 6/153 (x86_64), 1/2 (arm) New failures (same test not failed in Fedora-Rawhide-20191028.n.0): ID: 478767 Test: x86_64 Silverblue-dvd_ostree-iso install_default_upload URL: https://openqa.fedoraproject.org/tests/478767 ID: 478769 Test: x86_64 Silverblue-dvd_ostree-iso install_default@uefi URL: https://openqa.fedoraproject.org/tests/478769 ID: 478847 Test: x86_64 universal install_arabic_language URL: https://openqa.fedoraproject.org/tests/478847 ID: 478850 Test: x86_64 universal install_pxeboot@uefi URL: https://openqa.fedoraproject.org/tests/478850 Old failures (same test failed in Fedora-Rawhide-20191028.n.0): ID: 478703 Test: x86_64 Server-dvd-iso modularity_tests URL: https://openqa.fedoraproject.org/tests/478703 ID: 478761 Test: x86_64 KDE-live-iso apps_startstop URL: https://openqa.fedoraproject.org/tests/478761 ID: 478765 Test: arm Minimal-raw_xz-raw.xz install_arm_image_deployment_upload URL: https://openqa.fedoraproject.org/tests/478765 Soft failed openQA tests: 77/153 (x86_64) (Tests completed, but using a workaround for a known bug) New soft failures (same test not soft failed in Fedora-Rawhide-20191028.n.0): ID: 478817 Test: x86_64 universal upgrade_2_desktop_64bit URL: https://openqa.fedoraproject.org/tests/478817 ID: 478820 Test: x86_64 universal upgrade_2_desktop_encrypted_64bit URL: https://openqa.fedoraproject.org/tests/478820 Old soft failures (same test soft failed in Fedora-Rawhide-20191028.n.0): ID: 478697 Test: x86_64 Server-boot-iso install_default URL: https://openqa.fedoraproject.org/tests/478697 ID: 478698 Test: x86_64 Server-boot-iso install_default@uefi URL: https://openqa.fedoraproject.org/tests/478698 ID: 478699 Test: x86_64 Server-dvd-iso install_default_upload URL: https://openqa.fedoraproject.org/tests/478699 ID: 478701 Test: x86_64 Server-dvd-iso install_default@uefi URL: https://openqa.fedoraproject.org/tests/478701 ID: 478712 Test: x86_64 Server-dvd-iso install_repository_hd_variation URL: https://openqa.fedoraproject.org/tests/478712 ID: 478714 Test: x86_64 Server-dvd-iso server_realmd_join_kickstart URL: https://openqa.fedoraproject.org/tests/478714 ID: 478722 Test: x86_64 Server-dvd-iso install_repository_nfs_variation URL: https://openqa.fedoraproject.org/tests/478722 ID: 478727 Test: x86_64 Server-dvd-iso install_updates_nfs URL: https://openqa.fedoraproject.org/tests/478727 ID: 478730 Test: x86_64 Server-dvd-iso install_repository_nfs_graphical URL: https://openqa.fedoraproject.org/tests/478730 ID: 478731 Test: x86_64 Server-dvd-iso install_repository_nfsiso_variation URL: https://openqa.fedoraproject.org/tests/478731 ID: 478732 Test: x86_64 Everything-boot-iso install_default URL: https://openqa.fedoraproject.org/tests/478732 ID: 478733 Test: x86_64 Everything-boot-iso install_default@uefi URL: https://openqa.fedoraproject.org/tests/478733 ID: 478742 Test: x86_64 Workstation-live-iso desktop_update_graphical URL: https://openqa.fedoraproject.org/tests/478742 ID: 478777 Test: x86_64 universal install_sata@uefi URL: https://openqa.fedoraproject.org/tests/478777 ID: 478778 Test: x86_64 universal install_multi URL: https://openqa.fedoraproject.org/tests/478778 ID: 478779 Test: x86_64 universal install_multi@uefi URL: https://openqa.fedoraproject.org/tests/478779 ID: 478780 Test: x86_64 universal install_simple_encrypted URL: https://openqa.fedoraproject.org/tests/478780 ID: 478781 Test: x86_64 universal install_simple_free_space URL: https://openqa.fedoraproject.org/tests/478781 ID: 478782 Test: x86_64 universal install_multi_empty URL: https://openqa.fedoraproject.org/tests/478782 ID: 478783 Test: x86_64 universal install_software_raid URL: https://openqa.fedoraproject.org/tests/478783 ID: 478784 Test: x86_64 universal install_delete_partial URL: https://openqa.fedoraproject.org/tests/478784 ID: 478785 Test: x86_64 universal install_blivet_no_swap URL: https://openqa.fedoraproject.org/tests/478785 ID: 478786 Test: x86_64 universal install_blivet_xfs URL: https://openqa.fedoraproject.org/tests/478786 ID: 478787 Test: x86_64 universal install_blivet_software_raid URL: https://openqa.fedoraproject.org/tests/478787 ID: 478788 Test: x86_64 universal install_kickstart_firewall_disabled URL: https://openqa.fedoraproject.org/tests/478788 ID: 478789 Test: x86_64 universal install_kickstart_firewall_configured URL: https://openqa.fedoraproject.org/tests/478789 ID: 478790 Test: x86_64 universal install_b
Fedora rawhide compose report: 20191030.n.1 changes
OLD: Fedora-Rawhide-20191028.n.0 NEW: Fedora-Rawhide-20191030.n.1 = SUMMARY = Added images:2 Dropped images: 2 Added packages: 27 Dropped packages:5 Upgraded packages: 240 Downgraded packages: 1 Size of added packages: 20.14 MiB Size of dropped packages:1.20 MiB Size of upgraded packages: 4.67 GiB Size of downgraded packages: 165.20 KiB Size change of upgraded packages: 55.46 MiB Size change of downgraded packages: 81.18 KiB = ADDED IMAGES = Image: LXQt raw-xz armhfp Path: Spins/armhfp/images/Fedora-LXQt-armhfp-Rawhide-20191030.n.1-sda.raw.xz Image: Silverblue dvd-ostree x86_64 Path: Silverblue/x86_64/iso/Fedora-Silverblue-ostree-x86_64-Rawhide-20191030.n.1.iso = DROPPED IMAGES = Image: Mate raw-xz armhfp Path: Spins/armhfp/images/Fedora-Mate-armhfp-Rawhide-20191028.n.0-sda.raw.xz Image: LXQt live x86_64 Path: Spins/x86_64/iso/Fedora-LXQt-Live-x86_64-Rawhide-20191028.n.0.iso = ADDED PACKAGES = Package: ant-1.10.5-3.module_f28+4207+d722d224 Summary: Java build tool RPMs:ant ant-antlr ant-apache-bcel ant-apache-bsf ant-apache-log4j ant-apache-oro ant-apache-regexp ant-apache-resolver ant-apache-xalan2 ant-commons-logging ant-commons-net ant-javamail ant-jdepend ant-jmf ant-jsch ant-junit ant-junit5 ant-lib ant-swing ant-testutil ant-xz Size:3.31 MiB Package: antlr-2.7.7-56.module_f28+3872+5b76729e Summary: ANother Tool for Language Recognition RPMs:antlr-C++-doc antlr-tool python2-antlr Size:7.05 MiB Package: apache-commons-net-3.6-3.module_f28+3872+5b76729e Summary: Internet protocol suite Java library RPMs:apache-commons-net Size:295.74 KiB Package: bcel-6.2-2.module_f28+3872+5b76729e Summary: Byte Code Engineering Library RPMs:bcel Size:616.56 KiB Package: bsf-2.4.0-30.module_f28+3872+5b76729e Summary: Bean Scripting Framework RPMs:bsf Size:108.47 KiB Package: did-0.14-2.fc32 Summary: What did you do last week, month, year? RPMs:did Size:114.89 KiB Package: hamcrest-1.3-23.module_f28+3872+5b76729e Summary: Library of matchers for building test expressions RPMs:hamcrest hamcrest-core Size:184.52 KiB Package: jakarta-oro-2.0.8-23.module_f28+3872+5b76729e Summary: Full regular expressions API RPMs:jakarta-oro Size:82.83 KiB Package: javamail-1.5.2-7.module_f28+3872+5b76729e Summary: Java Mail API RPMs:javamail Size:634.12 KiB Package: jdepend-2.9.1-18.module_f28+3872+5b76729e Summary: Java Design Quality Metrics RPMs:jdepend Size:182.45 KiB Package: jsch-0.1.54-7.module_f28+3872+5b76729e Summary: Pure Java implementation of SSH2 RPMs:jsch Size:267.29 KiB Package: junit-1:4.12-9.module_f28+3872+5b76729e Summary: Java regression test package RPMs:junit Size:298.69 KiB Package: junit5-5.4.0-1.module_f28+3873+06cd63fa Summary: Java regression testing framework RPMs:junit5 Size:716.15 KiB Package: jzlib-1.1.3-8.module_f28+3872+5b76729e Summary: Re-implementation of zlib in pure Java RPMs:jzlib Size:82.73 KiB Package: libacars-1.3.1-1.fc32 Summary: A library for decoding various ACARS message payloads RPMs:acars-examples libacars libacars-devel Size:1.51 MiB Package: libcorrect-0-1.20181010gitf5a28c7.fc32 Summary: C library for Convolutional codes and Reed-Solomon RPMs:libcorrect libcorrect-devel Size:226.87 KiB Package: log4j12-1.2.17-22.module_f28+3872+5b76729e Summary: Java logging package RPMs:log4j12 Size:459.45 KiB Package: opentest4j-1.1.1-1.module_f28+3873+06cd63fa Summary: Open Test Alliance for the JVM RPMs:opentest4j Size:22.92 KiB Package: python-django-health-check-3.11.0-1.fc32 Summary: Checks for various conditions and provides reports RPMs:python-django-health-check-doc python3-django-health-check Size:191.92 KiB Package: regexp-1:1.5-26.module_f28+3872+5b76729e Summary: Simple regular expressions API RPMs:regexp Size:51.76 KiB Package: univocity-parsers-2.5.5-5.module_f28+3873+06cd63fa Summary: Collection of parsers for Java RPMs:univocity-parsers Size:339.24 KiB Package: xalan-j2-2.7.1-38.module_f28+3872+5b76729e Summary: Java XSLT processor RPMs:xalan-j2 Size:1.89 MiB Package: xerces-j2-2.11.0-34.module_f28+3872+5b76729e Summary: Java XML parser RPMs:xerces-j2 Size:1.16 MiB Package: xml-commons-apis-1.4.01-25.module_f28+3872+5b76729e Summary: APIs for DOM, SAX, and JAXP RPMs:xml-commons-apis Size:233.12 KiB Package: xml-commons-resolver-1.2-26.module_f28+3872+5b76729e Summary: Resolver subproject of xml-commons RPMs:xml-commons-resolver Size:114.34 KiB Package: xz-java-1.8-2.module_f28+3872+5b76729e Summary: Java implementation of XZ data compression RPMs:xz-java Size:105.03 KiB Package: z-1.9-0.fc32 Summary: Maintains a jump-list of the directories you actually use RPMs:z Size:11.89 KiB = DROPPED PACKAGES = Package: glassfish-el-3.0.1-0.7.b08.module_f28+3939+dc18cd75
