Fedora Release Engineering Meeting Summary for 2019-09-11
by Mohan Boddu
======================================
#fedora-meeting-2: RELENG (2019-09-12)
======================================
Meeting started by mboddu at 16:00:29 UTC. The full logs are available
athttps://meetbot.fedoraproject.org/fedora-meeting-2/2019-09-11/releng.20...
.
Meeting summary
---------------
* init process (mboddu, 16:00:30)
* LINK:
https://lists.fedoraproject.org/archives/list/rel-eng@lists.fedoraproject...
(dustymabe, 16:07:16)
* ACTION: mboddu will send an email to rel-eng@ list about not
forwarding the releng repo stuff and ask people to watch the repo
for email notifications and will disable the forwarding in the repo
settings (mboddu, 16:18:37)
* #8728 Add kalev to koji admins (mboddu, 16:19:40)
* LINK: https://pagure.io/releng/issue/8728 (mboddu, 16:19:45)
* ACTION: mboddu will add kalev as koji admin temporarily until we
have a new policy for regen-repo permission, mboddu will file a koji
ticket for it (mboddu, 16:30:35)
* rc1 is composing. :) (nirik, 16:31:41)
Meeting ended at 16:32:14 UTC.
Action Items
------------
* mboddu will send an email to rel-eng@ list about not forwarding the
releng repo stuff and ask people to watch the repo for email
notifications and will disable the forwarding in the repo settings
* mboddu will add kalev as koji admin temporarily until we have a new
policy for regen-repo permission, mboddu will file a koji ticket for
it
Action Items, by person
-----------------------
* kalev
* mboddu will add kalev as koji admin temporarily until we have a new
policy for regen-repo permission, mboddu will file a koji ticket for
it
* mboddu
* mboddu will send an email to rel-eng@ list about not forwarding the
releng repo stuff and ask people to watch the repo for email
notifications and will disable the forwarding in the repo settings
* mboddu will add kalev as koji admin temporarily until we have a new
policy for regen-repo permission, mboddu will file a koji ticket for
it
* **UNASSIGNED**
* (none)
People Present (lines said)
---------------------------
* mboddu (39)
* nirik (24)
* dustymabe (20)
* zodbot (7)
* kalev (1)
* sharkcz (1)
* jednorozec (0)
* pbrobinson (0)
* pingou (0)
* ksinny (0)
Generated by `MeetBot`_ 0.1.4
.. _`MeetBot`: http://wiki.debian.org/MeetBot
4 years, 7 months
[releng] Issue #8777: Unorphan several (java)packages
by Jakub Jelen
jjelen reported a new issue against the project: `releng` that you are following:
``
* Describe the issue
The time of threatening of retiring packages is again on so I will take few more to be able to build my application in Fedora:
* serp
* apache-rat
* simple-jndi
* velocity-tools
* apache-commons-jcs
* jsonp, portlet-2.0-api
* metadata-extractor2
* geronimo-jcdi-1.1-api
* jaxb2-maven-plugin
* libxslt
* sslext
* portals-pom
* geronimo-jcache
* apache-commons-fileupload
* hibernate-jpa-2.1-api
* hsqldb1
* jboss-jsf-2.2-api
* apache-commons-chain
* jboss-jsf-2.1-api
* json_simple
* openjpa
* apache-commons-jci
* bval
* httpunit
* struts
* geronimo-validation
* xmpcore
* python-which
* geronimo-jcdi-1.0-api
* When do you need this? (YYYY/MM/DD)
before package mass retiring (2019/09/16)
* When is this no longer needed or useful? (YYYY/MM/DD)
after package mass retiring (2019/09/16)
* If we cannot complete your request, what is the impact?
I will orhpan all the java packages I already took
``
To reply, visit the link below or just reply to this email
https://pagure.io/releng/issue/8777
4 years, 7 months
[releng] Issue #7662: Build once,
run everywhere seems to be pretty unsupported (modularity)
by Igor Gnatenko
ignatenkobrain reported a new issue against the project: `releng` that you are following:
``
* Describe the issue
Today we've encountered issue that if your modulemd contains something like
```yaml
- buildrequires:
platform: [f29]
requires:
platform: []
```
MBS doesn't tag it properly into f28-* because it checks for buildrequires and not for requires. Which is wrong: https://pagure.io/fm-orchestrator/issue/974
However, @puiterwijk mentioned that bodhi doesn't support this either because it would pick first tag instead of creating updates for multiple ones. It seems that bodhi would need to change some core parts for this.
I'm submitting this ticket just to make sure that work is scoped and if can't be completed before F29 bodhi activation point, could be workarounded.
* When do you need this? (YYYY/MM/DD)
F29 Bodhi activation point.
* When is this no longer needed or useful? (YYYY/MM/DD)
When modularity dies.
* If we cannot complete your request, what is the impact?
One of the main use-cases for modularity doesn't work.
``
To reply, visit the link below or just reply to this email
https://pagure.io/releng/issue/7662
4 years, 7 months