Fedora 31 compose report: 20190923.n.0 changes
by Fedora Branched Report
OLD: Fedora-31-20190922.n.0
NEW: Fedora-31-20190923.n.0
===== SUMMARY =====
Added images: 9
Dropped images: 0
Added packages: 0
Dropped packages: 1
Upgraded packages: 0
Downgraded packages: 0
Size of added packages: 0 B
Size of dropped packages: 367.25 KiB
Size of upgraded packages: 0 B
Size of downgraded packages: 0 B
Size change of upgraded packages: 0 B
Size change of downgraded packages: 0 B
===== ADDED IMAGES =====
Image: Cloud_Base raw-xz s390x
Path: Cloud/s390x/images/Fedora-Cloud-Base-31-20190923.n.0.s390x.raw.xz
Image: Server dvd s390x
Path: Server/s390x/iso/Fedora-Server-dvd-s390x-31-20190923.n.0.iso
Image: Mate raw-xz armhfp
Path: Spins/armhfp/images/Fedora-Mate-armhfp-31-20190923.n.0-sda.raw.xz
Image: Cloud_Base vmdk s390x
Path: Cloud/s390x/images/Fedora-Cloud-Base-31-20190923.n.0.s390x.vmdk
Image: Server boot s390x
Path: Server/s390x/iso/Fedora-Server-netinst-s390x-31-20190923.n.0.iso
Image: Container_Minimal_Base docker s390x
Path: Container/s390x/images/Fedora-Container-Minimal-Base-31-20190923.n.0.s390x.tar.xz
Image: Cloud_Base qcow2 s390x
Path: Cloud/s390x/images/Fedora-Cloud-Base-31-20190923.n.0.s390x.qcow2
Image: Container_Base docker s390x
Path: Container/s390x/images/Fedora-Container-Base-31-20190923.n.0.s390x.tar.xz
Image: Everything boot s390x
Path: Everything/s390x/iso/Fedora-Everything-netinst-s390x-31-20190923.n.0.iso
===== DROPPED IMAGES =====
===== ADDED PACKAGES =====
===== DROPPED PACKAGES =====
Package: octave-nnet-0.1.13-17.fc31
Summary: A feed forward multi-layer neural network
RPMs: octave-nnet
Size: 367.25 KiB
===== UPGRADED PACKAGES =====
===== DOWNGRADED PACKAGES =====
4 years, 9 months
Orphaned a number of Eclipse pacakges
by Aleksandar Kurtakov
As eclipse module is the supported way to get eclipse now and there are a
number of FTBFS for me as a package I've just orphaned the following:
* eclipse-tm-terminal
* eclipse-swtbot
* cbi-plugins
* eclipse-dtp
* eclipse-ecf
* eclipse-eclemma
* eclipse-egit-github
* eclipse-linuxtools
* eclipse-moreunit
* eclipse-mylyn
* eclipse-mpc
* eclipse-pydev
* eclipse-packagekit
Most of them are leaf packages so can go freely - only critical parts if
one wants to keep eclipse srpm in is eclipse-ecf and cbi-plugins.
--
Alexander Kurtakov
Red Hat Eclipse Team
4 years, 9 months
aarch64 test systems implementation
by Dave Love
Are the aarch64 test systems running on real or emulated hardware? (Is
there a way to tell?)
I ask because I'm seeing bad numerical results from a test and would
like to know if I can eliminate qemu as a possible cause -- not that I
think that's likely.
4 years, 9 months
Orphaned tagsoup
by Miro Hrončok
tagsoup was maintained byt he Stewardship SIG and is no longer required by any
of our packages. I have orphaned it.
I don't know much about the package, but several other Java stuff requires it:
icedtea-web-0:1.8.2-3.fc31.src
icedtea-web-0:1.8.2-3.fc31.x86_64
javadocofflinesearch-0:2.2-9.fc31.noarch
javadocofflinesearch-0:2.2-9.fc31.src
xom-0:1.2.10-13.fc31.src
It was updated to the current 1.2.1 version in 2012 and upstream has either
moved or died.
--
Miro Hrončok
--
Phone: +420777974800
IRC: mhroncok
4 years, 9 months
Some Java packages in need of new permanent maintainer(s)
by Fabio Valentini
Hello packagers,
The Stewardship SIG is currently providing only bare-minimum
maintenance for some Java packages, and none of our packages depend on
them anymore.
So, we're looking for someone to take better care of them, preferably
someone who actively uses these packages or maintains a package that
depends on them.
The packages are:
- java-base64
- jboss-jstl-1.2-api
- jetty-version-maven-plugin
- stringtemplate4
- tagsoup
Directly dependent packages of java-base64:
- Java-WebSocket
- elasticsearch
- gherkin2-java
- java-vash
- java-xmlbuilder
- jets3t
- rescu
- smack
- sshj
Directly dependent packages of jboss-jstl-1.2-api:
- jboss-jsf-2.1-api
- jboss-jsf-2.2-api
Directly dependent packages of jetty-version-maven-plugin:
- jetty8
Directly dependent packages of stringtemplate4:
- antlr3
- antlr4
- eclipselink
- gs-collections
Directly dependent packages of tagsoup:
- icedtea-web
- javadocofflinesearch
- tika
- xom
If you received this email directly, you're a (co-)maintainer of one
of these packages, and would probably be best qualified to take care
of the package in question.
If you want to take one, some, or all of them off our hands, just fill
out the "package_adoption_request" template here, and we will transfer
the package to you. https://www.pagure.io/stewardship-sig/new_issue
If nobody claims the packages within the next two weeks, we will
orphan them again, setting them on their course towards retirement in
about two months.
Thanks,
Fabio (decathorpe), for the Stewardship SIG
4 years, 9 months
Upcoming change for adopting orphaned packages and anitya integration
by Pierre-Yves Chibon
Good Morning Everyone,
The Fedora Infrastructure team has been working on making changes to the way
orphaned packages are being adopted as well as the way to set the monitoring
status for the integration with anitya (ie: https://release-monitoring.org).
## Orphan packages
Currently if a package is orphaned there is no way to adopt it easily on
dist-git (https://src.fedoraproject.org). You need to open a ticket on the
releng issue tracker and wait for someone to process that ticket.
This is going to change, new versions of pagure-dist-git and pagure will offer a
button on the left hand side menu offering to adopt orphaned packages.
This is already live in staging, so you can see how it looks there, for example:
https://src.stg.fedoraproject.org/rpms/aasaver (you'll need to be logged in)
Note: if the package is retired, you will still have to go through a releng
ticket as it will need to be unblocked in koji.
## Anitya integration
Currently if you want to tweak the setting for the anitya integration, you need
to open a pull-request on the fedora-scm-requests project at
https://pagure.io/releng/fedora-scm-requests/
That git repo is pretty big and once your pull-request is finally open, you
still have to wait for someone to merge it.
This is also going to change, new versions of pagure and pagure-dist-git offer a
drop-down menu on the left hand side menu to see and adjust the monitoring
status of the project.
This is also live in staging and you can see an example of a project who has set
its monitoring status to "monitoring":
https://src.stg.fedoraproject.org/rpms/0ad
(The status in staging have been imported from the fedora-scm-requests repo)
## Feedback
Feel free to play with this in staging and let us know if there is anything that
isn't working as expected or that you would like to change before we push this
to production (post F31-beta freeze).
Once the new versions of pagure, pagure-dist-git, anitya and the-new-hotness
have been deployed to production we will send another announcement for the
change and work on getting the different documentations updated.
Looking forward to hear from you,
Michal and Pierre
- On behalf of the Fedora Infrastructure team
_______________________________________________
devel-announce mailing list -- devel-announce(a)lists.fedoraproject.org
To unsubscribe send an email to devel-announce-leave(a)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.fedora...
4 years, 9 months
