Hi all,
I'm Aymen, a comp-sci student studying in the UK. I'm looking to
contribute to fedora, and I'm interested in the releng team -- is there
a good way to get started? Thanks.
Kind regards,
Aymen
ryanlerch reported a new issue against the project: `releng` that you are following:
``
* Describe the issue
Just wondering if it is possible to update the PDC stage instance so the active fedora releases match more closely to current reality? At the moment, the most recent active fedora release on pdc.stg is f28.
This will help make the entire stg pipeline of koji, src, and bodhi more useful when testing pushing packages through the stg pipeline for development testing.
* When do you need this? (YYYY/MM/DD)
* When is this no longer needed or useful? (YYYY/MM/DD)
* If we cannot complete your request, what is the impact?
``
To reply, visit the link below or just reply to this email
https://pagure.io/releng/issue/8537
ryanlerch reported a new issue against the project: `releng` that you are following:
``
* Describe the issue
Just wondering if it is possible to update the branches on the src.stg instance to make the branches match more closely to current reality? At the moment, there is a f29 branch on src.stg, but no f30 branches.
This will help make the entire stg pipeline of koji, src, and bodhi more useful when testing pushing packages through the stg pipeline for development testing.
* When do you need this? (YYYY/MM/DD)
* When is this no longer needed or useful? (YYYY/MM/DD)
* If we cannot complete your request, what is the impact?
``
To reply, visit the link below or just reply to this email
https://pagure.io/releng/issue/8538
======================================
#fedora-meeting-2: RELENG (2019-07-18)
======================================
Meeting started by mboddu at 16:00:44 UTC. The full logs are available
athttps://meetbot.fedoraproject.org/fedora-meeting-2/2019-07-17/releng.2019…
.
Meeting summary
---------------
* init process (mboddu, 16:00:45)
* EPEL8 (mboddu, 16:02:03)
* Alternate Architecture Updates (mboddu, 16:22:15)
* LINK: https://koji.fedoraproject.org/koji/taskinfo?taskID=36293914
(nirik, 16:30:28)
* sharkcz will be doing some experiments to gather some facts on
ppc64le slowness and nirik will 4 builders on each p9 box and see if
it helps with any storage competition issue. (mboddu, 16:43:52)
* nirik will remove buildvm-ppc64le-01/02.ppc.fedoraproject.org
ppc64le builders from image channel and add 04,10,11 ppc64le
builders to image channel which makes 4 in image channel including
03 (mboddu, 16:47:09)
Meeting ended at 17:03:11 UTC.
Action Items
------------
Action Items, by person
-----------------------
* **UNASSIGNED**
* (none)
People Present (lines said)
---------------------------
* mboddu (65)
* nirik (55)
* sharkcz (29)
* smooge (7)
* zodbot (7)
* tyll (0)
* puiterwijk (0)
* masta (0)
* jednorozec (0)
* pbrobinson (0)
* dustymabe (0)
* ksinny (0)
Generated by `MeetBot`_ 0.1.4
.. _`MeetBot`: http://wiki.debian.org/MeetBot
jlebon reported a new issue against the project: `releng` that you are following:
``
Please sign FCOS release 30.20190716.1 artifacts and import the OSTree commit into the Fedora unified repo. S3 build dir path is `s3://fcos-builds/prod/streams/testing/builds/30.20190716.1`
You will find a `CHECKSUMS` file and a detached signature `CHECKSUMS.sig` at the root of the build dir. We will sign with a better key for this soon (or it will be implicitly signed once we move to fedora-messaging), but for now, I've signed it with [my personal key](https://keys.fedoraproject.org/pks/lookup?op=get&search=0x936F29E9519C….
Thanks!
``
To reply, visit the link below or just reply to this email
https://pagure.io/releng/issue/8539
pbrobinson reported a new issue against the project: `releng` that you are following:
``
https://fedoraproject.org/wiki/Changes/uEFIforARMv7
Change for uEFI on ARMv7. There will need to be a new version of oz deployed on aarch64 builder userd for building images to enable us to build ARMv7 images on those devices. I will co-ordinate with infra/rel-eng to deploy and test this on stage/prod infrastructure, and once deployed and tested will provide a PR with the pungi config changes (minor) to enable this in the nightly composes.
``
To reply, visit the link below or just reply to this email
https://pagure.io/releng/issue/7606
kevin reported a new issue against the project: `releng` that you are following:
``
https://docs.pagure.org/koji/plugins/#save-failed-tree-plugin
We would need to make sure we set filters right and that this correctly errors after a buildroot has been cleaned up by kojid.
Perhaps we could try it in staging for a bit.
``
To reply, visit the link below or just reply to this email
https://pagure.io/releng/issue/8243
emeryberger reported a new issue against the project: `releng` that you are following:
``
* Hoard has been orphaned; I am claiming it and taking it over. (I am the author and maintainer of Hoard.)
``
To reply, visit the link below or just reply to this email
https://pagure.io/releng/issue/7996
kevin reported a new issue against the project: `releng` that you are following:
``
These packages do not have git repos on pkgs02, but are active in pdc:
```
ERROR: /srv/git/repositories/rpms/R-gnomeGUI.git does not appear to be a directory
ERROR: /srv/git/repositories/rpms/actdiag.git does not appear to be a directory
ERROR: /srv/git/repositories/rpms/compat-ImageMagick6.9.3.git does not appear to be a directory
ERROR: /srv/git/repositories/rpms/gnome-cpufreq-applet.git does not appear to be a directory
ERROR: /srv/git/repositories/rpms/kf5-textwidgets.git does not appear to be a directory
ERROR: /srv/git/repositories/rpms/nwdiag.git does not appear to be a directory
ERROR: /srv/git/repositories/rpms/python-elementtree.git does not appear to be a directory
ERROR: /srv/git/repositories/rpms/repsurgeon.git does not appear to be a directory
ERROR: /srv/git/repositories/rpms/seqdiag.git does not appear to be a directory
ERROR: /srv/git/repositories/rpms/tetex-beamer.git does not appear to be a directory
ERROR: /srv/git/repositories/rpms/tetex-pgf.git does not appear to be a directory
ERROR: /srv/git/repositories/rpms/tetex-xcolor.git does not appear to be a directory
```
so, likely they should be marked eol in pdc and blocked in koji?
``
To reply, visit the link below or just reply to this email
https://pagure.io/releng/issue/8143