dustymabe reported a new issue against the project: `releng` that you are following:
``
You should be able to do it with this command:
```
python push-two-week-atomic.py -k fedora-27 -r 27 --pungi-compose-id Fedora-Atomic-27-20180117.1 --ostree-pungi-compose-id Fedora-27-updates-20180117.0
```
``
To reply, visit the link below or just reply to this email
https://pagure.io/releng/issue/7272
======================================
#fedora-meeting-2: RELENG (2018-01-18)
======================================
Meeting started by mboddu at 17:11:39 UTC. The full logs are available
athttps://meetbot.fedoraproject.org/fedora-meeting-2/2018-01-18/releng.2018…
.
Meeting summary
---------------
* init process (mboddu, 17:11:39)
* #7227 [RFE] Add new repositories for modular[-updates[-testing]]
(mboddu, 17:17:39)
* LINK: https://pagure.io/releng/issue/7227 (mboddu, 17:17:45)
* We got different info from mattdm and contyk. mboddu will update the
ticket and ask them to agree on one option. (mboddu, 17:24:11)
* #7097 Automate the process of reviewing and merging PRs on
releng/fedora-scm-requests (mboddu, 17:26:06)
* LINK: https://pagure.io/releng/issue/7097 (mboddu, 17:26:16)
* #6984 create a unified ostree repo for fedora 27 and beyond (mboddu,
17:28:51)
* LINK: https://pagure.io/releng/issue/6984 (mboddu, 17:28:58)
* Unified repo work is done for f28 and beyond, SOP's are still work
in progress. (mboddu, 17:35:36)
* Alternate Architecture Updates (mboddu, 17:35:59)
* Except for power architecture everything seems to be working fine.
(mboddu, 17:40:51)
* Everything is fine in the alternate architecture world and power got
fixed with lorax update (mboddu, 17:42:46)
* Open Floor (mboddu, 17:42:53)
* To monitor bodhi pushes, please have a look at
https://pagure.io/releng/pull-request/7274 as there will no more
lock files (mboddu, 17:44:40)
Meeting ended at 17:46:37 UTC.
Action Items
------------
Action Items, by person
-----------------------
* **UNASSIGNED**
* (none)
People Present (lines said)
---------------------------
* mboddu (46)
* dgilmore (14)
* puiterwijk (11)
* dustymabe (9)
* zodbot (8)
* bowlofeggs (6)
* sharkcz (4)
* masta (2)
* nirik (1)
* tyll (0)
* Kellin (0)
* pbrobinson (0)
* pingou (0)
* maxamillion (0)
mohanboddu opened a new pull-request against the project: `releng` that you are following:
``
Mass Rebuild Doc Update
``
To reply, visit the link below or just reply to this email
https://pagure.io/releng/pull-request/7270
Dear all,
You are kindly invited to the meeting:
Fedora Release Engineering on 2018-01-18 from 17:00:00 to 18:00:00 UTC
At fedora-meeting-2(a)irc.freenode.net
The meeting will be about:
Fedora Release Engineering weekly meeting
Source: https://apps.fedoraproject.org/calendar/meeting/8666/
dustymabe opened a new pull-request against the project: `pungi-fedora` that you are following:
``
container: use the compose locations url for updates
``
To reply, visit the link below or just reply to this email
https://pagure.io/pungi-fedora/pull-request/497
adamwill reported a new issue against the project: `releng` that you are following:
``
https://kojipkgs.fedoraproject.org/compose/cd/ is rather interesting. As you can see, the last successful compose there is from April 2017, `FACD-Rawhide-20170406.n.8`. However, if you look in https://kojipkgs.fedoraproject.org/compose/cd/logs/ , you can see that something seems to be constantly trying to build a new one, and constantly failing for exactly the same reason. Every 15 minutes, a new log directory shows up, and it always has a file `x86_64/koji-task.log` - like [this one](https://kojipkgs.fedoraproject.org/compose/cd/logs/20180116-01-15/x86_… - with this content:
AuthError: unable to obtain a session
So...has this been failing every 15 minutes for the last 9 months? If so, someone should probably look into that. :)
@mohanboddu
``
To reply, visit the link below or just reply to this email
https://pagure.io/releng/issue/7269
adamwill reported a new issue against the project: `releng` that you are following:
``
There are 8 old Atomic nightly composes lying around in https://kojipkgs.fedoraproject.org/compose/ , these:
Fedora-Atomic-26-20170715.0
Fedora-Atomic-26-20170716.0
Fedora-Atomic-26-20170717.0
Fedora-Atomic-26-20170718.0
Fedora-Atomic-26-20170719.0
Fedora-Atomic-26-20170720.0
Fedora-Atomic-26-20170724.0
Fedora-Atomic-26-20170725.0
I don't think there's any reason they need to exist any more. There were actually composes with identical compose IDs in https://kojipkgs.fedoraproject.org/compose/twoweek/ at one point, but those were garbage collected. These ones never were. They can probably just be wiped.
@mohanboddu
``
To reply, visit the link below or just reply to this email
https://pagure.io/releng/issue/7267