January 2019 - rel-eng - Fedora mailing-lists

[releng] Issue #8062: Grant admin rights for koji
by Tomáš Hrčka 21 Jan '19

21 Jan '19

humaton reported a new issue against the project: `releng` that you are following: `` * Describe the issue I need permissions to do my releng related work * When do you need this? (YYYY/MM/DD) ASAP my FAS account: humaton `` To reply, visit the link below or just reply to this email https://pagure.io/releng/issue/8062

2 2

[releng] Issue #8047: source metatdata is empty
by Lubomír Sedlář 21 Jan '19

21 Jan '19

lsedlar reported a new issue against the project: `releng` that you are following: `` As discussed in this thread: https://lists.fedoraproject.org/archives/list/devel@lists.fedoraproject.org… Originally filed as pungi#1111. The source repo is indeed empty and primary xml claims there are 0 packages. However I don't see how this could be an issue with Pungi, given that the updates compose looks different to that and is very much not empty. https://kojipkgs.fedoraproject.org/compose/updates/Fedora-29-updates-201901… The 20190109.2 is also correct. I don't know what exactly happens to the compose once it finishes and how it gets to mirrors. I think it's either a problem in Bodhi or some sync script that's causing the data to go missing. CC @nbecker `` To reply, visit the link below or just reply to this email https://pagure.io/releng/issue/8047

4 4

[releng] Issue #8031: Need +1: policy change re. module default stream changes & Fedora Changes
by Adam Samalik 21 Jan '19

21 Jan '19

asamalik reported a new issue against the project: `releng` that you are following: `` * Describe the issue The Modularity WG is changing the policy regarding module default stream changes & Fedora Changes. It is a minor policy change that doesn't require any changes in code. I'd like to get a formal +1 from RelEng and FESCo on the change before publishing it. The summary would be: "Instead of rigidly requiring a Fedora Change for all module default stream changes, we are relaxing the policy to 'submitting a Fedora Change based on packager's best judgement'. We are also restricting changes to major Fedora releases. This makes it more consistent with how we handle major changes in traditional packages." For more details, please see the current policy [1] (please note it's described quite "efficiently"), the new policy approved by the Modularity WG [2], and optionally a set of scenarios covering module default stream changes [3]. [1] https://docs.fedoraproject.org/en-US/modularity/making-modules/managing-def… [2] https://tree.taiga.io/project/modularity-wg/us/77 [3] https://pagure.io/modularity/working-documents/blob/master/f/lifecycles-upg… * When do you need this? (YYYY/MM/DD) No date. * When is this no longer needed or useful? (YYYY/MM/DD) No date. * If we cannot complete your request, what is the impact? Packagers would continue to be required to submit a Fedora change for every module default stream change, even in cases one wouldn't be submitted in a similar change introduced by traditional packages — making the workflows between the two delivery methods (trad packages & modules) inconsistent. `` To reply, visit the link below or just reply to this email https://pagure.io/releng/issue/8031

2 4

[releng] Issue #8044: Set default stream and profiles for avocado in rawhide
by Merlin Mathesius 21 Jan '19

21 Jan '19

merlinm reported a new issue against the project: `releng` that you are following: `` Please set the default stream (`stable`) and profiles (`default`) for the `avocado` module in rawhide. PR: https://pagure.io/releng/fedora-module-defaults/pull-request/41 Note: This change will also allow retirement of the non-modular avocado packages. * Describe the issue The "avocado" module currently has no default stream or profiles set. * When do you need this? (YYYY/MM/DD) 2019/01/30 * When is this no longer needed or useful? (YYYY/MM/DD) N/A * If we cannot complete your request, what is the impact? * "avocado" modular packages cannot be installed unless the user first manually enables a module stream. * Users wishing to install the "avocado" module manually need to explicitly specify the "default" profile. * Non-modular "avocado" packages cannot be retired as requested by [BZ#1660921](https://bugzilla.redhat.com/show_bug.cgi?id=1660921) `` To reply, visit the link below or just reply to this email https://pagure.io/releng/issue/8044

2 3

eInvoice Notification - 17 January 2019
by Ben Cotton 17 Jan '19

17 Jan '19

Dear Customer, Attached is the last invoice. Thanks in anticipation. Ben Cotton bcotton(a)redhat.com If you or your employer do not consent to Internet e-mail for messages of this kind, please advise the sender.

1 0

[Fedocal] Reminder meeting : Fedora Release Engineering
by mohanboddu＠fedoraproject.org 17 Jan '19

17 Jan '19

Dear all, You are kindly invited to the meeting: Fedora Release Engineering on 2019-01-17 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/9274/

1 0

[releng] Issue #8048: Add fedora-packages to f29-infra tag in Koji
by Mikolaj Izdebski 13 Jan '19

13 Jan '19

mizdebsk reported a new issue against the project: `releng` that you are following: `` Please add package `fedora-packages` to `f29-infra`. Package owner can be set to @cverna. This package is required to deploy [Fedora Packages](https://apps.fedoraproject.org/packages) application in Fedora Infrastructure. koji add-pkg --owner cverna f29-infra fedora-packages `` To reply, visit the link below or just reply to this email https://pagure.io/releng/issue/8048

2 2

RelEng schedule tasks
by Ben Cotton 11 Jan '19

11 Jan '19

I am beginning to prepare the schedule for Fedora 31. One thing I want to do is to make sure it still accurately reflects the work of different teams within Fedora. Please look at the tasks on your team's schedule [1] and discuss them in your team. Let me know if there are tasks that should be added, removed, or modified. You can email me directly or file an issue in Pagure[2]. I ask that you please provide feedback by Friday, 18 January, although I will be able to incorporate changes after that. [1] https://fedorapeople.org/groups/schedule/f-30/f-30-releng-tasks.html [2] https://pagure.io/fedora-project-schedule/issues -- Ben Cotton Fedora Program Manager TZ=America/Indiana/Indianapolis

1 0

[releng] Issue #8045: Requesting ownership of python-tenacity
by Christopher Brown 10 Jan '19

10 Jan '19

snecker reported a new issue against the project: `releng` that you are following: `` * Describe the issue python-tenacity has been orphaned and I requested commit access in https://pagure.io/fesco/issue/2045 * When do you need this? (YYYY/MM/DD) No rush. * When is this no longer needed or useful? (YYYY/MM/DD) n/a * If we cannot complete your request, what is the impact? Cannot maintain package. `` To reply, visit the link below or just reply to this email https://pagure.io/releng/issue/8045

2 2

[release] pungi 4.1.32
by Lubomír Sedlář 10 Jan '19

10 Jan '19

Hello everyone, a new version of Pungi is available! The 4.1.32 build is ready to be used. There are updates waiting in Bodhi to go to updates-testing. Ideally you should use the 4.1.32-3.fcX build. This is a minor bug-fix release. The old pungi command has been updated to use createrepo_c for creating repos and productmd for generating metadata. There have been a few tweaks and improvements to documentation. It is now possible to configure rootfs size for lorax for traditionall installer, not just the one based on ostree. Refer to the documentation [0] for details on what configuration options are available. [0] https://docs.pagure.org/pungi/index.html If you encounter problems or need general help, stop by #fedora-releng IRC channel or file issues in Pagure. Happy composing! Lubomír

1 0

[Fedocal] Reminder meeting : Fedora Release Engineering
by mohanboddu＠fedoraproject.org 10 Jan '19

10 Jan '19

Dear all, You are kindly invited to the meeting: Fedora Release Engineering on 2019-01-10 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/9274/

1 0

[releng] Issue #8042: pague is using python2 again?
by Zbigniew Jędrzejewski-Szmek 09 Jan '19

09 Jan '19

zbyszek reported a new issue against the project: `releng` that you are following: `` * Describe the issue ```console zbyszek@krowka ~/fedora/catfish (git)-[master] % git push Total 0 (delta 0), reused 0 (delta 0) remote: Emitting a message to the fedmsg bus. remote: * Publishing information for 1 commits remote: Traceback (most recent call last): remote: File "/usr/lib/python2.7/site-packages/pagure/hooks/__init__.py", line 394, in run_project_hooks remote: changes=changes, remote: File "/usr/lib/python2.7/site-packages/pagure/hooks/__init__.py", line 111, in runhook remote: changes=changes, remote: File "/usr/lib/python2.7/site-packages/pagure/hooks/default.py", line 279, in post_receive remote: session, project, repodir, username, refname, commits, forced remote: File "/usr/lib/python2.7/site-packages/pagure/hooks/default.py", line 72, in send_notifications remote: name = pagure.lib.git.get_author(rev, repodir) remote: File "/usr/lib/python2.7/site-packages/pagure/lib/git.py", line 1317, in get_author remote: ["log", "-1", '--pretty=format:"%an"', commit], abspath remote: File "/usr/lib/python2.7/site-packages/pagure/lib/git.py", line 1261, in read_git_lines remote: args, abspath, keepends=keepends, **kw remote: File "/usr/lib/python2.7/site-packages/pagure/lib/git.py", line 1246, in read_git_output remote: **kw remote: File "/usr/lib/python2.7/site-packages/pagure/lib/git.py", line 1227, in read_output remote: out = out.rstrip("\n\r") remote: UnicodeDecodeError: 'ascii' codec can't decode byte 0xc4 in position 10: ordinal not in range(128) remote: Sending to redis to log activity and send commit notification emails To ssh://pkgs.fedoraproject.org/rpms/catfish 8600b4d40a..c470bd56d4 master -> master ``` This seems to be a regression, I think I reported something like this in the past. `` To reply, visit the link below or just reply to this email https://pagure.io/releng/issue/8042

2 5

[releng] Issue #8043: Container base image release 2019-01-09
by Clement Verna 09 Jan '19

09 Jan '19

cverna reported a new issue against the project: `releng` that you are following: `` * Describe the issue Could we release the container base image for f29. Thanks * 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/8043

2 3

[releng] Issue #8039: Unretired python-s3transfer
by Charalampos Stratakis 09 Jan '19

09 Jan '19

cstratak reported a new issue against the project: `releng` that you are following: `` Name of the package: python-s3transfer Branches required for unretirement: F30 Name of the new maintainer: cstratak This package is a dependency of python-boto3 and it was orphaned quite recently. `` To reply, visit the link below or just reply to this email https://pagure.io/releng/issue/8039

3 3

[releng] Issue #8022: Unretire nodejs-has-unicode
by Tom Hughes 09 Jan '19

09 Jan '19

tomh reported a new issue against the project: `releng` that you are following: `` * Name of the package? nodejs-has-unicode * FAS username of the new maintainer? tomh * Branches that you need it to be unretired for? master * Package re-review BZ URL? Retired for less than two weeks so no re-review required. `` To reply, visit the link below or just reply to this email https://pagure.io/releng/issue/8022

2 2

[releng] Issue #8021: Unretire python-s3transfer
by Igor Gnatenko 09 Jan '19

09 Jan '19

ignatenkobrain reported a new issue against the project: `releng` that you are following: `` ## Name of the package? `python-s3transfer` ## FAS username of the new maintainer? @ignatenkobrain ## Branches that you need it to be unretired for? * `master` ## Package re-review BZ URL? https://bugzilla.redhat.com/show_bug.cgi?id=1662344 ## Any extra information? `python3-boto3` is broken due to missing s3transfer from repositories. `` To reply, visit the link below or just reply to this email https://pagure.io/releng/issue/8021

2 2

[releng] Issue #8041: epel6-infra tag requires autosign permission
by Mikolaj Izdebski 09 Jan '19

09 Jan '19

mizdebsk reported a new issue against the project: `releng` that you are following: `` * Describe the issue epel6-infra Koji tag requires autosign permission, while other infra tags require infra permission. Please fix epel6-infra tag to require infra permission instead of autosign. Related to: #7910, #7431 * When do you need this? (YYYY/MM/DD) Earliest convenience * When is this no longer needed or useful? (YYYY/MM/DD) N/A * If we cannot complete your request, what is the impact? Fedora Infrastructure members will not be able to deploy their builds into production. `` To reply, visit the link below or just reply to this email https://pagure.io/releng/issue/8041

2 4

[releng] Issue #8040: Take ownership of pygtk2
by Gwyn Ciesla 09 Jan '19

09 Jan '19

limb reported a new issue against the project: `releng` that you are following: `` To prevent retirement, needed for several packages. `` To reply, visit the link below or just reply to this email https://pagure.io/releng/issue/8040

3 3

Fedora Atomic Host Two Week Release Announcement: 29.20190107.0
by noreply＠fedoraproject.org 08 Jan '19

08 Jan '19

2 1

[releng] Issue #8038: Claim orphaned python-characteristc
by Ralph Bean 08 Jan '19

08 Jan '19

ralph reported a new issue against the project: `releng` that you are following: `` https://src.fedoraproject.org/rpms/python-characteristic is orphaned. Can I be the new owner? `` To reply, visit the link below or just reply to this email https://pagure.io/releng/issue/8038

1 2

[releng] Issue #8036: Please review https://fedoraproject.org/wiki/Changes/Reset-locale-if-not-available
by Zbigniew Jędrzejewski-Szmek 08 Jan '19

08 Jan '19

zbyszek reported a new issue against the project: `releng` that you are following: `` n/t `` To reply, visit the link below or just reply to this email https://pagure.io/releng/issue/8036

2 2

[releng] Issue #8037: 20170107: Release Fedora 29 Atomic Host
by Michael Nguyen 08 Jan '19

08 Jan '19

mnguyen 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-29 -r 29 --pungi-compose-id Fedora-29-updates-20190107.0 ``` Note: We won't need to use options --compose-basedir and --first-release from this release onward. `` To reply, visit the link below or just reply to this email https://pagure.io/releng/issue/8037

3 3

[pungi-fedora] PR #681: Upate container config to use the new ks name
by Clement Verna 07 Jan '19

07 Jan '19

cverna opened a new pull-request against the project: `pungi-fedora` that you are following: `` Upate container config to use the new ks name `` To reply, visit the link below or just reply to this email https://pagure.io/pungi-fedora/pull-request/681

3 5

[releng] Issue #8028: [System-wide change] Switch default cryptsetup metadata format to LUKS2
by Ondrej Kozina 07 Jan '19

07 Jan '19

okozina reported a new issue against the project: `releng` that you are following: `` * Describe the issue The change switches Fedora system default metadata format for full disk encryption from LUKS1 to LUKS2. It mostly involves cryptsetup package and Anaconda installer so that both creates new LUKS2 containers by default. * When do you need this? Before the Fedora 30 beta freeze happens. * When is this no longer needed or useful? After the completion deadline of system-wide changes for Fedora 30. * If we cannot complete your request, what is the impact? Fedora would stick with LUKS1 format as a default for FDE. Note: (will add link to Change proposal shortly...) `` To reply, visit the link below or just reply to this email https://pagure.io/releng/issue/8028

2 2

[releng] Issue #8027: Change impact: Python extension flags reduction
by Miro Hrončok 07 Jan '19

07 Jan '19

churchyard reported a new issue against the project: `releng` that you are following: `` * Describe the issue Hi, there is a change proposal at https://fedoraproject.org/wiki/Changes/Python_Extension_Flags We see no impact for releng, but I'm opening this ticket as requested by the process. This should not affect Fedora packages. No rebuilds are needed. If we break the 65 packages that can in theory break and revert the change to fix them, we can rebuild the affected packages using our provenpackager powers. * When do you need this? I don't need anything. * When is this no longer needed or useful? This was never usefull :D * If we cannot complete your request, what is the impact? Nothing happens. `` To reply, visit the link below or just reply to this email https://pagure.io/releng/issue/8027

2 2

[releng] Issue #8033: Access request: fedora-module-defaults repo
by Stephen Gallagher 07 Jan '19

07 Jan '19

sgallagh reported a new issue against the project: `releng` that you are following: `` * Describe the issue I want to update the CI setup for this repository so that it is more flexible (such as being able to update the CI setup via merged PR rather than requiring admin access). * When do you need this? (YYYY/MM/DD) As soon as possible. * When is this no longer needed or useful? (YYYY/MM/DD) Once the improvement patches are merged to master. * If we cannot complete your request, what is the impact? The CI will remain limited (and also running on an EOL Fedora 27 VM in CentOS CI). `` To reply, visit the link below or just reply to this email https://pagure.io/releng/issue/8033

2 4

[releng] Issue #8024: [System-wide change] Flicker Free Boot
by Hans de Goede 07 Jan '19

07 Jan '19

jwrdegoede reported a new issue against the project: `releng` that you are following: `` The goal of this issue is to let releng know about the "Flicker Free Boot" change planned for F30 and to coordinate any rel-eng related issues regarding this change. ATM I don't see anything in this change which specifically involves rel-eng. Also see: https://fedoraproject.org/wiki/Changes/HiddenGrubMenu `` To reply, visit the link below or just reply to this email https://pagure.io/releng/issue/8024

2 2

[releng] Issue #8003: Change: DeepinDE
by Ziqian SUN (Zamir) 07 Jan '19

07 Jan '19

zsun reported a new issue against the project: `releng` that you are following: `` * Describe the issue We are planning a self-contained change to bring DeepinDE into Fedora https://fedoraproject.org/wiki/Changes/DeepinDE We don't expect any affect to non-deepin packages. Most of the related packages are listed [here](https://github.com/FZUG/deepin-desktop/wiki/Deepin-Desktop-Environmen… and the build status can be checked in [koschei](https://apps.fedoraproject.org/koschei/groups/mosquito/deepin-sig). * When do you need this? (YYYY/MM/DD) N/A, this is a general ticket for the change. `` To reply, visit the link below or just reply to this email https://pagure.io/releng/issue/8003

2 8

[releng] Issue #8032: Cannot push to mingw-uriparser
by Sandro Mani 07 Jan '19

07 Jan '19

smani reported a new issue against the project: `releng` that you are following: `` Following happens when attempting to push to mingw-uriparser (re-cloned via fedpkg clone to be sure, origin is `ssh://smani@pkgs.fedoraproject.org/rpms/mingw-uriparser`): $ git push Enumerating objects: 9, done. Counting objects: 100% (9/9), done. Delta compression using up to 8 threads Compressing objects: 100% (5/5), done. Writing objects: 100% (5/5), 597 bytes | 597.00 KiB/s, done. Total 5 (delta 2), reused 0 (delta 0) remote: Traceback (most recent call last): remote: File "hooks/pre-receive", line 36, in <module> remote: run_hook_file(hooktype) remote: File "/usr/lib/python2.7/site-packages/pagure/hooks/__init__.py", line 545, in run_hook_file remote: pull_request, remote: File "/usr/lib/python2.7/site-packages/pagure/hooks/__init__.py", line 321, in run_project_hooks remote: authbackend = get_git_auth_helper() remote: File "/usr/lib/python2.7/site-packages/pagure/lib/git_auth.py", line 76, in get_git_auth_helper remote: cls = classes[backend].load() remote: File "/usr/lib/python2.7/site-packages/pkg_resources.py", line 2260, in load remote: entry = __import__(self.module_name, globals(),globals(), ['__name__']) remote: File "/usr/lib/python2.7/site-packages/dist_git_auth.py", line 32, in <module> remote: from pagure.lib import model, get_user remote: ImportError: cannot import name get_user To ssh://pkgs.fedoraproject.org/rpms/mingw-uriparser I was able to successfully push to two other repos just before. `` To reply, visit the link below or just reply to this email https://pagure.io/releng/issue/8032

2 3

[releng] Issue #6967: new mock and systemd-nspawn
by Kevin Fenzi 05 Jan '19

05 Jan '19

kevin added a new comment to an issue you are following: `` Status update: All the builders are moved to the current mock (with old-chroot), except for all the armv7 builders (they are stalled due to https://bugzilla.redhat.com/show_bug.cgi?id=1576593 ) `` To reply, visit the link below or just reply to this email https://pagure.io/releng/issue/6967

1 0

[releng] Issue #7173: Orphan all of jcapik's packages
by Randy Barlow 05 Jan '19

05 Jan '19

bowlofeggs reported a new issue against the project: `releng` that you are following: `` FESCo has voted to orphan all of @jcapik's packages: https://pagure.io/fesco/issue/1786 `` To reply, visit the link below or just reply to this email https://pagure.io/releng/issue/7173

14 24

[releng] Issue #8029: Block infomas-asl from f30
by Miro Hrončok 05 Jan '19

05 Jan '19

churchyard reported a new issue against the project: `releng` that you are following: `` * Describe the issue [infomas-asl](https://src.fedoraproject.org/rpms/infomas-asl) was never imported and built. it was [retired](https://src.fedoraproject.org/rpms/infomas-asl/c/09c507084e623dd2d… 3 months ago, but is not blocked from Koji. * When do you need this? Any time si good. * When is this no longer needed or useful? If unretired. * If we cannot complete your request, what is the impact? It will be listed in the "orphaned packages to be retired" e-mails forever. Thanks `` To reply, visit the link below or just reply to this email https://pagure.io/releng/issue/8029

2 2

[pungi-fedora] Issue #679: zchunk metadata is missing zdicts
by Jonathan Dieter 03 Jan '19

03 Jan '19

jdieter reported a new issue against the project: `pungi-fedora` that you are following: `` First off, thanks so much for turning on the zchunk metadata creation in createrepo_c. It looks like it's working fine, but the zchunk files are extremely large because they're missing the zdicts available in fedora-repo-zdicts. This is either because fedora-repo-zdicts isn't installed or because my patch in #678 is wrong. The correct path for the zdicts should be /usr/share/fedora-repo-zdicts/f30 or /usr/share/fedora-repo-zdicts/rawhide. If fedora-repo-zdicts isn't installed on the systems running creatrepo_c, can we please install it? If the problem is that %(pkgset_koji_tag) doesn't resolve to 'f30' or 'rawhide', then my patch is wrong, and I'd love some guidance on what variable would be a better choice. Thanks again for enabling zchunk metadata generation! `` To reply, visit the link below or just reply to this email https://pagure.io/pungi-fedora/issue/679

3 7

Proposal : Use OSBS to build the fedora container base image
by Clement Verna 03 Jan '19

03 Jan '19

Hi all, I would like to get feedbacks on the following proposal. Use OSBS to build the fedora container base image, indeed OSBS has the capability to build a base container image using a kickstart file. To do this OSBS needs a Dockerfile, a kickstart file and an image-build.conf file stored in dist-git, then OSBS will trigger an ImageFactory task in Koji in order to build to base image and then it will build the base container based on the artifacts built in Koji. Here a the few advantages I see in moving forward with this proposal : - Use of a single dist-git repo for the base image, allowing use of fedora-ci. - Using OSBS will allow us to make use of bodhi updates to release new versions of the image - OSBS deals with multi-arches (we currently use a custom script in releng to build manifest list) - Does not requires releng to run a script to release the images Before I start looking at the implementation details, I would appreciate feedbacks. Thanks Clément

5 6

[Fedocal] Reminder meeting : Fedora Release Engineering
by mohanboddu＠fedoraproject.org 03 Jan '19

03 Jan '19

Dear all, You are kindly invited to the meeting: Fedora Release Engineering on 2019-01-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/9274/

1 0

[releng] Issue #8019: Take ownership of torbrowser-launcher
by Gwyn Ciesla 02 Jan '19

02 Jan '19

limb reported a new issue against the project: `releng` that you are following: `` I was added as admin and then the package was orphaned. https://lists.fedoraproject.org/archives/list/devel@lists.fedoraproject.org… `` To reply, visit the link below or just reply to this email https://pagure.io/releng/issue/8019

2 2

2026

2025

2024

2023

2022

2021

2020

2019

2018

2017

2016

2015

2014

2013

2012

2011

2010

2009

2008

rel-eng January 2019