sharkcz reported a new issue against the project: `releng` that you are following:
``
We have a problem with pixman update for F-28 (https://bodhi.fedoraproject.org/updates/FEDORA-2018-fc3904edc1). Bodhi is complaining with
````bodhi - 2018-05-03 03:01:46.192702 (karma: 0)
Bodhi is unable to request this update for stabilization: This critical path update has not yet been approved for pushing to the stable repository. It must first reach a karma of 2, consisting of 0 positive karma from proventesters, along with 2 additional karma from the community. Or, it must spend 14 days in testing without any negative feedback Additionally, it must pass automated tests.````
But the update has enough karma and there is no failed test-case.
CC @ajax
``
To reply, visit the link below or just reply to this email
https://pagure.io/releng/issue/7482
walters reported a new issue against the project: `releng` that you are following:
``
I'm at:
```
# rpm-ostree status
State: idle; auto updates disabled
Deployments:
● ostree://fedora-atomic:fedora/28/x86_64/workstation
Version: 28.1.1 (2018-04-25 05:39:47)
BaseCommit: ef3d3262fe9c62d20e18637d656943a285530363060696ece175f2313683003d
GPGSignature: Valid signature by 128CF232A9371991C8A65695E08E7E629DB62FB1
```
Yet looking at `ostree show --raw ef3d3262fe9c62d20e18637d656943a285530363060696ece175f2313683003d` I see: 'rpmostree.rpmmd-repos': <[{'id': <'repo-0'>, 'timestamp': <uint64 1524630543>}]>
Which looks to me like it's only pulling in the "GA" repository.
``
To reply, visit the link below or just reply to this email
https://pagure.io/releng/issue/7484
mohanboddu opened a new pull-request against the project: `pungi-fedora` that you are following:
``
Moving container-nightly.conf to container-nightly.sh
``
To reply, visit the link below or just reply to this email
https://pagure.io/pungi-fedora/pull-request/614
cverna reported a new issue against the project: `releng` that you are following:
``
Currently if you pull the fedora:latest image from registry.fp.o or docker.io you are getting a f27 base image. The latest tag should point to f28
``
To reply, visit the link below or just reply to this email
https://pagure.io/releng/issue/7479
======================================
#fedora-meeting-2: RELENG (2018-05-03)
======================================
Meeting started by mboddu at 17:00:20 UTC. The full logs are available
athttps://meetbot.fedoraproject.org/fedora-meeting-2/2018-05-03/releng.2018…
.
Meeting summary
---------------
* init process (mboddu, 17:00:21)
* Alternative Architectures updates (mboddu, 17:03:17)
* There is a new lorax build thats supposed to fix ppc64 and ppc64le
composes (mboddu, 17:07:30)
* #7482 bodhi - unable to request this update for stabilization
(mboddu, 17:12:42)
* LINK: https://pagure.io/releng/issue/7482 (mboddu, 17:12:48)
* mboddu updated the config and nirik will run the playbook to fix the
issue. (mboddu, 17:27:24)
* ACTION: mboddu will go through the policy and make necessary changes
to config and also will update the docs (mboddu, 17:28:08)
* Open Floor (mboddu, 17:32:46)
* LINK: https://bugzilla.redhat.com/show_bug.cgi?id=1574211 (nirik,
17:34:40)
Meeting ended at 18:08:15 UTC.
Action Items
------------
* mboddu will go through the policy and make necessary changes to config
and also will update the docs
Action Items, by person
-----------------------
* mboddu
* mboddu will go through the policy and make necessary changes to
config and also will update the docs
* **UNASSIGNED**
* (none)
People Present (lines said)
---------------------------
* mboddu (68)
* nirik (37)
* masta (19)
* sharkcz (13)
* zodbot (7)
* pbrobinson (3)
* puiterwijk (1)
* dustymabe (1)
* bowlofeggs (1)
* tyll (0)
* Kellin (0)
* pingou (0)
* dgilmore (0)
* maxamillion (0)
Generated by `MeetBot`_ 0.1.4
.. _`MeetBot`: http://wiki.debian.org/MeetBot
mohanboddu opened a new pull-request against the project: `releng` that you are following:
``
Adding +x permission to sync-latest-container-base-image.sh script
``
To reply, visit the link below or just reply to this email
https://pagure.io/releng/pull-request/7447
Dear all,
You are kindly invited to the meeting:
Fedora Release Engineering on 2018-05-03 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/
Hi Release Engineering,
As Fedora 28 released, we find that the URL for fedora-updates changed
in Fedora.
For Fedora 27 it looks like
http://dl.fedoraproject.org/pub/fedora/linux/updates/27/x86_64/
While for Fedora 28,
http://dl.fedoraproject.org/pub/fedora/linux/updates/28/Everything/x86_64/
And this was not mentioned in the wiki page
https://fedoraproject.org/wiki/Repositories
Now we've got feedback from users that they are now having problems
updating to Fedora 27. Checking his repo it shows he is using a baseurl
with the Fedora 27 format like
baseurl=https://mirrors.tuna.tsinghua.edu.cn/fedora/updates/$releasever/$basearch/
I checked with Mirror Admin list and Adrian told me mirrormanager is
working as expected. So now I am wondering do we have any way to
mitigate the problems for legacy users (people who using baseurl
pointing to their closest mirror) rather than asking them to change the
baseurl or point to metalink URL in repo config?
I totally understand for most of the people they should use metalink, but
now I need to see if there are ways to ease the upgrading experience for
baseurl users.
Thanks in advance!
--
Ziqian SUN (Zamir)
GPG : 1D86 6D4A 49CE 4BBD 72CF FCF5 D856 6E11 F2A0 525E
Want to know more about Fedora?
Visit https://fedoraproject.org/wiki/
Ready to contribute? See https://whatcanidoforfedora.org/