rel-eng February 2016

rel-eng@lists.fedoraproject.org

9 participants
66 discussions

Re: #6159: Request to discuss Git workflow for rel-eng tooling
by Fedora Release Engineering 09 Feb '16

09 Feb '16

#6159: Request to discuss Git workflow for rel-eng tooling --------------------------+-------------------- Reporter: maxamillion | Owner: ausil Type: task | Status: closed Milestone: | Component: other Resolution: fixed | Keywords: Blocked By: | Blocking: --------------------------+-------------------- Changes (by acarter): * status: new => closed * resolution: => fixed -- Ticket URL: <https://fedorahosted.org/rel-eng/ticket/6159#comment:3> Fedora Release Engineering <http://fedorahosted.org/rel-eng> Release Engineering for the Fedora Project

1 0

Re: #6159: Request to discuss Git workflow for rel-eng tooling
by Fedora Release Engineering 09 Feb '16

09 Feb '16

#6159: Request to discuss Git workflow for rel-eng tooling --------------------------+------------------- Reporter: maxamillion | Owner: ausil Type: task | Status: new Milestone: | Component: other Resolution: | Keywords: Blocked By: | Blocking: --------------------------+------------------- Comment (by acarter): Proposal implemented for several tools already. Will continue to pursue this with others. -- Ticket URL: <https://fedorahosted.org/rel-eng/ticket/6159#comment:2> Fedora Release Engineering <http://fedorahosted.org/rel-eng> Release Engineering for the Fedora Project

1 0

Re: #6158: Request to discuss Rel-Eng Project Planning Proposal
by Fedora Release Engineering 09 Feb '16

09 Feb '16

#6158: Request to discuss Rel-Eng Project Planning Proposal --------------------------+----------------------- Reporter: maxamillion | Owner: rel-eng@… Type: task | Status: closed Milestone: | Component: other Resolution: fixed | Keywords: Blocked By: | Blocking: --------------------------+----------------------- Changes (by acarter): * status: new => closed * resolution: => fixed -- Ticket URL: <https://fedorahosted.org/rel-eng/ticket/6158#comment:3> Fedora Release Engineering <http://fedorahosted.org/rel-eng> Release Engineering for the Fedora Project

1 0

[Fedocal] Reminder meeting : Fedora Release Engineering
by Dennis Gilmore 07 Feb '16

07 Feb '16

Dear all, You are kindly invited to the meeting: Fedora Release Engineering on 2016-02-08 from 15:30:00 to 16:30:00 UTC At fedora-meeting-1(a)irc.freenode.net The meeting will be about: Fedora Release Engineering weekly meeting Source: https://apps.fedoraproject.org/calendar/meeting/2026/

1 0

Re: #6163: Request for review of mash patch
by Fedora Release Engineering 06 Feb '16

06 Feb '16

#6163: Request for review of mash patch --------------------------+----------------------- Reporter: ralph | Owner: rel-eng@… Type: enhancement | Status: closed Milestone: | Component: mash Resolution: fixed | Keywords: Blocked By: | Blocking: --------------------------+----------------------- Changes (by pbrobinson): * status: new => closed * resolution: => fixed Comment: I think we should as mash is now in pagure and if it's not reviewed and merged there should be a pull request submitted there anyway now as it's easier to track state there -- Ticket URL: <https://fedorahosted.org/rel-eng/ticket/6163#comment:4> Fedora Release Engineering <http://fedorahosted.org/rel-eng> Release Engineering for the Fedora Project

1 0

Re: #6158: Request to discuss Rel-Eng Project Planning Proposal
by Fedora Release Engineering 06 Feb '16

06 Feb '16

#6158: Request to discuss Rel-Eng Project Planning Proposal --------------------------+----------------------- Reporter: maxamillion | Owner: rel-eng@… Type: task | Status: new Milestone: | Component: other Resolution: | Keywords: Blocked By: | Blocking: --------------------------+----------------------- Comment (by acarter): Adam, can we close this out now or is this your subtle way of kicking me out? -- Ticket URL: <https://fedorahosted.org/rel-eng/ticket/6158#comment:2> Fedora Release Engineering <http://fedorahosted.org/rel-eng> Release Engineering for the Fedora Project

1 0

Re: #6163: Request for review of mash patch
by Fedora Release Engineering 05 Feb '16

05 Feb '16

#6163: Request for review of mash patch --------------------------+----------------------- Reporter: ralph | Owner: rel-eng@… Type: enhancement | Status: closed Milestone: | Component: mash Resolution: fixed | Keywords: Blocked By: | Blocking: --------------------------+----------------------- Comment (by lmacken): This was merged upstream in mash, and python-multilib supports configurable black/white lists as well. https://github.com/Zyzyx/python- multilib/blob/master/multilib/multilib.py -- Ticket URL: <https://fedorahosted.org/rel-eng/ticket/6163#comment:5> Fedora Release Engineering <http://fedorahosted.org/rel-eng> Release Engineering for the Fedora Project

1 0

Re: #6163: Request for review of mash patch
by Fedora Release Engineering 05 Feb '16

05 Feb '16

#6163: Request for review of mash patch --------------------------+----------------------- Reporter: ralph | Owner: rel-eng@… Type: enhancement | Status: new Milestone: | Component: mash Resolution: | Keywords: Blocked By: | Blocking: --------------------------+----------------------- Comment (by acarter): Ralph, looks like this patch was merged, can we close this out? -- Ticket URL: <https://fedorahosted.org/rel-eng/ticket/6163#comment:3> Fedora Release Engineering <http://fedorahosted.org/rel-eng> Release Engineering for the Fedora Project

1 0

#6343: stuck freecolor-0.9.3 update for f22
by Fedora Release Engineering 04 Feb '16

04 Feb '16

#6343: stuck freecolor-0.9.3 update for f22 -----------------------------+------------------------ Reporter: dfateyev | Owner: rel-eng@… Type: task | Status: new Milestone: Fedora 24 Alpha | Component: koji Keywords: | Blocked By: Blocking: | -----------------------------+------------------------ Yesterday, I got stuck update for freecolor-0.9.3 in f22. Initially I got "OSError: [Errno 30] Read-only file system: '/var/tmp/koji/tasks/1795'" https://koji.fedoraproject.org/koji/taskinfo?taskID=12691795 I resubmitted after a while, got it built, but this time got a tagging issue with the same error message: https://koji.fedoraproject.org/koji/taskinfo?taskID=12691907 Now, I can't (re)build it again since Koji reports it's already built. And I can't push it for update in Bodhi since it hasn't tagged properly. Please remove this build so I can make rebuild, or tag it so I can push the update. Thanks. -- Ticket URL: <https://fedorahosted.org/rel-eng/ticket/6343> Fedora Release Engineering <http://fedorahosted.org/rel-eng> Release Engineering for the Fedora Project

1 1

[releng] moved to https://pagure.io/releng/
by Dennis Gilmore 03 Feb '16

03 Feb '16

commit 798d910bfc3bf05ba81a60d91c056ce9c128d8f1 Author: Dennis Gilmore <dennis(a)ausil.us> Date: Wed Feb 3 10:17:02 2016 -0600 moved to https://pagure.io/releng/ Signed-off-by: Dennis Gilmore <dennis(a)ausil.us> README | 38 +- scripts/LICENSE | 272 ------ scripts/autosigner.py | 485 ----------- scripts/block_retired.py | 330 -------- scripts/branching/make-koji-release-tags | 46 - scripts/build-arm-images | 37 - scripts/build-cloud-images | 122 --- scripts/build-current.py | 258 ------ scripts/build-functions.sh | 262 ------ scripts/build-livecds | 36 - scripts/build-previous.py | 235 ------ scripts/build_composeinfo | 167 ---- scripts/buildbranched | 33 - scripts/buildepelbeta | 75 -- scripts/buildrawhide | 33 - scripts/check-latest-build.py | 99 --- scripts/check-testing-pre-GA.py | 61 -- scripts/check-upgrade-paths.py | 197 ----- scripts/check_epel_deps.py | 323 ------- scripts/check_epel_deps.sh | 10 - scripts/check_sigul.py | 76 -- scripts/clean-overrides.py | 82 -- scripts/cloud/fedora_ec2.py | 876 ------------------- scripts/cloud/test-fedora_ec2.py | 200 ----- scripts/cloud/upload-fedora-ebs.py | 236 ------ scripts/critpath.py | 195 ----- scripts/distcvs2distgit.py | 165 ---- scripts/fedora-torrent-ini.py | 106 --- scripts/fedretire | 77 -- scripts/find-bad-builds.py | 54 -- scripts/find-hidden-packages.py | 269 ------ scripts/find_FTBFS.py | 67 -- scripts/find_failures.py | 124 --- scripts/find_tagged_retired_epel_builds.py | 91 -- scripts/find_unblocked_orphans.py | 802 ------------------ scripts/get-critpath | 85 -- scripts/isolate-tag.py | 63 -- scripts/koji-build-srpm.py | 100 --- scripts/koji-cleanup-signed.py | 39 - scripts/koji-compare.py | 146 ---- scripts/koji-import.py | 163 ---- scripts/koji-reimport.py | 57 -- scripts/koji-stalk.py | 225 ----- scripts/make-updates | 76 -- scripts/makebleed | 26 - scripts/mashcompose | 71 -- scripts/mass-rebuild-special.py | 198 ----- scripts/mass-rebuild.py | 159 ---- scripts/mass-tag.py | 116 --- scripts/mass_rebuild_file_bugs.py | 156 ---- scripts/misc/ga-cleanup | 29 - scripts/misc/rebuild | 59 -- scripts/monitor_mash_log.py | 91 -- scripts/need-rebuild-gcc43.py | 74 -- scripts/need-rebuild.py | 142 ---- scripts/process-git-requests/process-git-requests | 937 --------------------- scripts/prune-tag.py | 106 --- scripts/pungify | 56 -- scripts/run-pungi | 261 ------ scripts/secondary-sync.py | 313 ------- scripts/sign_unsigned.py | 774 ----------------- scripts/sigulsign_unsigned.py | 611 -------------- scripts/spam-o-matic-epel7 | 257 ------ scripts/srpm-excluded-arch.py | 65 -- scripts/sync-blocked-primary.py | 99 --- scripts/sync-tagged-primary | 16 - scripts/sync-tagged-primary.py | 117 --- scripts/torrent-generator/foot.html | 34 - scripts/torrent-generator/foot.rss | 3 - scripts/torrent-generator/head.html | 42 - scripts/torrent-generator/head.rss | 11 - scripts/torrent-generator/torrent-generator | 189 ----- scripts/torrent-generator/torrent_generator.conf | 9 - scripts/update-critpath | 200 ----- scripts/upgradecheck/README | 5 - scripts/upgradecheck/upgradecheck.conf | 16 - scripts/upgradecheck/upgradecheck.py | 290 ------- 77 files changed, 1 insertions(+), 13024 deletions(-) --- diff --git a/README b/README index 0e81554..c89b007 100644 --- a/README +++ b/README @@ -1,37 +1 @@ -This is the Fedora Release Engineering GIT repo. Random stuff is tossed -here. - -Everything is copyrighted by the respective authors. You can use and -redistribute the code under the terms of version 2 or later of the -GNU Public License as published by the Free Software Foundation. - -To make licensing easier, license headers in the source files will be -a single line reference to Unique License Identifiers as defined by -the Linux Foundation's SPDX project [1]. For example, -in a source file the full "GPL v2.0 or later" header text will be -replaced by a single line: - - SPDX-License-Identifier: GPL-2.0+ - -the license terms of all files in the source tree should be defined -by such License Identifiers; in no case a file can contain more than -one such License Identifier list. - -If a "SPDX-License-Identifier:" line references more than one Unique -License Identifier, then this means that the respective file can be -used under the terms of either of these licenses, i. e. with - - SPDX-License-Identifier: GPL-2.0+ LGPL-2.1+ - -you can chose between GPL-2.0+ and LGPL-2.1+ licensing. - -We use the SPDX Unique License Identifiers here; these are available -at [2]. - -[1] http://spdx.org/ -[2] http://spdx.org/licenses/ - -Full name SPDX Identifier OSI Approved File name URI -======================================================================================================================================= -GNU General Public License v2.0 or later GPL-2.0+ Y gpl-2.0.txt http://www.gnu.org/licenses/gpl-2.0.txt -GNU Lesser General Public License v2.1 or later LGPL-2.1+ Y lgpl-2.1.txt http://www.gnu.org/licenses/old-licenses/lgpl-2.1.txt +Moved to pagure https://pagure.io/releng/

1 0

2026

2025

2024

2023

2022

2021

2020

2019

2018

2017

2016

2015

2014

2013

2012

2011

2010

2009

2008

rel-eng February 2016