May 2015 - rel-eng - Fedora Mailing-Lists

by Dennis Gilmore

The lightweight tag 'rawhide-stable' was updated to point to: bf9e7a8... hardlink the whole tree for now. when we fix mash drop back It previously pointed to: 5e2cf17... use new vagrant koji format options and add Cloud Vagrant b NOTE: People pulling from the repository will not get the new tag. For more information, please see: http://live.gnome.org/Git/Help/TagUpdates

8 years, 11 months

1
0
0 / 0

[releng] hardlink the whole tree for now. when we fix mash drop back to just doing drpms

by Dennis Gilmore

commit bf9e7a8624e8a4efcdf0de758083bc86df846725 Author: Dennis Gilmore <dennis(a)ausil.us> Date: Mon May 4 22:12:44 2015 -0500 hardlink the whole tree for now. when we fix mash drop back to just doing drpms Signed-off-by: Dennis Gilmore <dennis(a)ausil.us> scripts/build-functions.sh | 8 ++------ 1 files changed, 2 insertions(+), 6 deletions(-) --- diff --git a/scripts/build-functions.sh b/scripts/build-functions.sh index 86aae73..49f6252 100644 --- a/scripts/build-functions.sh +++ b/scripts/build-functions.sh @@ -119,13 +119,9 @@ send_fedmsg done mash.complete log "finished mash" log "starting hardlink" -# hardlink the noarch deltarpms between x86_64 and i386 -if [[ "${DIST}" == "branched" ]] -then +# hardlink the noarch deltarpms between all arches $MOCK -r $MOCKCONFIG --uniqueext=$DATE --chroot "hardlink -v -c ${MASHDIR}/$BRANCHED$EXPANDARCH" -else - $MOCK -r $MOCKCONFIG --uniqueext=$DATE --chroot "hardlink -v -c ${MASHDIR}/$BRANCHED$EXPANDARCH/*/os/drpms/" -fi +# $MOCK -r $MOCKCONFIG --uniqueext=$DATE --chroot "hardlink -v -c ${MASHDIR}/$BRANCHED$EXPANDARCH/*/os/drpms/" log "finished hardlink" log "starting repodiff"

8 years, 11 months

1
0
0 / 0

WhenIsGood - Scheduling a discussion around Fedora Projects Planning

by Adam Miller

Hello all, There was recently a discussion on the Fedora Rel-Eng list as the result of a Project Planning workflow[0]. As this was discussed further in irc it was decided that this is likely a conversation that should be had across more Fedora groups to see if there's a solution that we would all like to utilize. If we can all agree on a workflow and utility we'll hopefully remove the potential for duplicating efforts or requesting multiple solutions to the same problem be hosted by the Infrastructure team. In an attempt to not cross-post I am duplicating this post on the rel-eng, qa, infrastructure, docs, buildsys, and env-and-stacks mailing lists. I would like to request that if there are any discussions around this, please rely to the rel-eng list so we can consolidate the discussion. All interested parties please fill out the following WhenIsGood so that we can find a meeting time to discuss this. http://whenisgood.net/pip4kjd Thank you, -AdamM [0] - https://lists.fedoraproject.org/pipermail/rel-eng/2015-April/019806.html

8 years, 11 months

1
0
0 / 0

PATCH - First attempt to enable Atomic ISO compose in pungi-koj

by Adam Miller

I've added a handful of parameters here to mirror the command that's currently being done run-pungi.sh[0] The options can either be strings for single elements or lists for multiples in the pungi-koji config. ====== BEGIN Example config add_template = "/srv/pungi/spin-kickstarts/atomic-installer/lorax-configure-repo.tmpl" add_template_var = [ "ostree_osname=Fedora-Cloud_Atomic", "ostree_ref=fedora-atomic/f22/x86_64/docker-host", ] add_arch_template = "/srv/pungi/spin-kickstarts/atomic-installer/lorax-embed-repo.tmpl" add_arch_template_var = [ "ostree_repo=http://compose-x86-01.phx2.fedoraproject.org/compose/atomic/", "ostree_osname=Fedora-Cloud_Atomic", "ostree_ref=fedora-atomic/f22/x86_64/docker-host", ] ===== END Example config I look forward to feedback. -AdamM [0] - https://git.fedorahosted.org/cgit/releng/tree/scripts/run-pungi#n67 diff --git a/pungi/phases/buildinstall.py b/pungi/phases/buildinstall.py index 1a60607..cf32658 100644 --- a/pungi/phases/buildinstall.py +++ b/pungi/phases/buildinstall.py @@ -86,13 +86,19 @@ class BuildinstallPhase(PhaseBase): noupgrade = not self.compose.conf.get("buildinstall_upgrade_image", False) buildinstall_method = self.compose.conf["buildinstall_method"] + # These were added for the Atomic ISO Lorax compose + add_template = self.compose.conf.get("add_template", None) + add_template_var = self.compose.conf.get("add_template_var", None) + add_arch_template = self.compose.conf.get("add_arch_template", None) + add_arch_template_var = self.compose.conf.get("add_arch_template_var", None) + for arch in self.compose.get_arches(): repo_baseurl = self.compose.paths.work.arch_repo(arch) output_dir = self.compose.paths.work.buildinstall_dir(arch) volid = get_volid(self.compose, arch) if buildinstall_method == "lorax": - cmd = lorax.get_lorax_cmd(product, version, release, repo_baseurl, output_dir, is_final=self.compose.supported, buildarch=arch, volid=volid, nomacboot=True, noupgrade=noupgrade) + cmd = lorax.get_lorax_cmd(product, version, release, repo_baseurl, output_dir, is_final=self.compose.supported, buildarch=arch, volid=volid, nomacboot=True, noupgrade=noupgrade, add_template=add_template, add_template_var=add_template_var, add_arch_template=add_arch_template, add_template_var=add_template_var) elif buildinstall_method == "buildinstall": cmd = lorax.get_buildinstall_cmd(product, version, release, repo_baseurl, output_dir, is_final=self.compose.supported, buildarch=arch, volid=volid) else: diff --git a/pungi/wrappers/lorax.py b/pungi/wrappers/lorax.py index 80d7f9f..c462f7b 100644 --- a/pungi/wrappers/lorax.py +++ b/pungi/wrappers/lorax.py @@ -21,7 +21,40 @@ from kobo.shortcuts import force_list class LoraxWrapper(object): - def get_lorax_cmd(self, product, version, release, repo_baseurl, output_dir, variant=None, bugurl=None, nomacboot=False, noupgrade=False, is_final=False, buildarch=None, volid=None): + def _handle_optional_arg_type(self, f_arg, c_arg): + """ + _handle_optional_arg_type + private function to handle arguments to LoraxWrapper get_*_cmd + functions that can optionally be different types (such as string + or list). This effectively allows to repeat args to the commands + wrapped by LoraxWrapper. + + @param uknown type : f_arg + - Function argument that is passed to the get_*_cmd function. + + @param string: c_arg + - Command line argument to append to cmd + + @return list + - returns a list of strings to join with the cmd list in the get_*_cmd + functions + """ + + cmd_args = [] + + if type(f_arg) is list: + for item in f_arg: + cmd_args.append("%s=%s" % (c_arg, item)) + if type(f_arg) is str: + cmd_args.append("%s=%s" % (c_arg, item)) + else: + raise Exception( + f_arg, + "Incorrect type passed to LoraxWrapper for " % c_arg + ) + return cmd_args + + def get_lorax_cmd(self, product, version, release, repo_baseurl, output_dir, variant=None, bugurl=None, nomacboot=False, noupgrade=False, is_final=False, buildarch=None, volid=None, add_template=None, add_template_var=None, add_arch_template=None, add_arch_template_var=None): cmd = ["lorax"] cmd.append("--product=%s" % product) cmd.append("--version=%s" % version) @@ -53,6 +86,39 @@ class LoraxWrapper(object): if volid: cmd.append("--volid=%s" % volid) + if add_template: + cmd.extend( + self._handle_optional_arg_type(add_template, "--add-template") + ) + + if add_template_var: + cmd.extend( + self._handle_optional_arg_type( + add_template_var, "--add-template-var" + ) + ) + + if add_template_var: + cmd.extend( + self._handle_optional_arg_type( + add_template_var, "--add-template-var" + ) + ) + + if add_arch_template: + cmd.extend( + self._handle_optional_arg_type( + add_arch_template, "--add-arch-template" + ) + ) + + if add_arch_template_var: + cmd.extend( + self._handle_optional_arg_type( + add_arch_template_var, "--add-arch-template-var" + ) + ) + output_dir = os.path.abspath(output_dir) cmd.append(output_dir)

8 years, 11 months

2
4
0 / 0

[Fedocal] Reminder meeting : Fedora Release Engineering

by Dennis Gilmore

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

8 years, 11 months

2
1
0 / 0

New pkgdb-admin

by Pierre-Yves Chibon

Hi everyone, I just made a new release of packagedb-cli: 2.8.2, this contains a couple of changes to pkgdb-admin: * Add the `info` action to get a human readable description of what the action is * Check that the fedora-review flag is set to `+` when processing a new package request This second item is rather interesting and important, so if you are processing requests made in pkgdb, please update :) https://admin.fedoraproject.org/updates/packagedb-cli-2.8.2-1.fc20 https://admin.fedoraproject.org/updates/packagedb-cli-2.8.2-1.fc21 https://admin.fedoraproject.org/updates/packagedb-cli-2.8.2-1.fc22 https://admin.fedoraproject.org/updates/packagedb-cli-2.8.2-1.el6 https://admin.fedoraproject.org/updates/packagedb-cli-2.8.2-1.el7 Thanks, Pierre

8 years, 11 months

1
0
0 / 0

#6162: Schedule and coordinate mass rebuild for F23

by Fedora Release Engineering

#6162: Schedule and coordinate mass rebuild for F23 -----------------------------+------------------------ Reporter: jkurik | Owner: rel-eng@… Type: task | Status: new Milestone: Fedora 23 Alpha | Component: other Keywords: | Blocked By: Blocking: | -----------------------------+------------------------ Coordinate the packages that need to be rebuilt for F23. We try to have no more than one mass rebuild per cycle. So we need to list the things that need a mass rebuild and then schedule it to happen. Branching is no earlier than 2015-07-14, so mass rebuild should be done by 2015-06-16 (with 4 weeks clean up grace period). The main reason for mass rebuild is GCC5 change: https://fedoraproject.org/wiki/Changes/GCC5 For full Fedora 23 schedule see https://fedoraproject.org/wiki/Releases/23/Schedule -- Ticket URL: <https://fedorahosted.org/rel-eng/ticket/6162> Fedora Release Engineering <http://fedorahosted.org/rel-eng> Release Engineering for the Fedora Project

8 years, 11 months

1
3
0 / 0

Ngspice update

by Kenneth Brun Nielsen

Hi all, I want to use recent version of ngspice in Fedora 21. I created this thread, and was told to try your mail list http://forums.fedoraforum.org/showthread.php?t=304277 Any change to have the recent version of ngspice in the Fedora repo? Best regards, Kenneth

8 years, 12 months

2
1
0 / 0

#6144: Document the semantics of "comps"

by Fedora Release Engineering

#6144: Document the semantics of "comps" -----------------------------+------------------------ Reporter: rholy | Owner: rel-eng@… Type: defect | Status: new Milestone: Fedora 22 Final | Component: other Keywords: | Blocked By: Blocking: | -----------------------------+------------------------ We, as the developers of DNF, miss a document that describes what "comps" mean and how should package managers work with them. Until it is documented, we cannot handle DNF bugs related to "comps" properly since we don't know what is the expected behaviour. E.g. what does "mandatory" packages mean? Could a "comp" be installed without a mandatory package (since it seems that there is a common practice to do that in kickstart files; e.g. RHBZ 1131969 and RHBZ 1185408)? What should happen if a "comp" is installed and its mandatory package gets removed? What if multiple comps share the same mandatory packages? And so on... And please don't focus only on mandatory packages. If there is a piece of software that has to work with another one, the dependency has to be documented. Also another issue related to the mandatory packages comes to my mind. Since I understand "comps" as something that specifies which packages are the Fedora default (is true? can you document it?), what is the recommended approach to replace a default package (YUM) with a new default package (DNF) on all user systems? That is something that should be possible to be specified on the comps level IIUIC. Also it would be nice if there will be a way how to specify which packages are preferred over which ones since there are people that are convinced that Fedora e.g. prefers MariaDB over community-mysql so Fedora has to express it somehow. Anyway, we can discuss it once you finish the documentation. I just wanted to let you know about some use cases in case it would help you to design the semantics. It would be nice if you could fix it as soon as possible. (Actually, DNF uses "libcomps" to work with "comps" so in fact, we don't mind if it is documented on "comps.xml" level or on "libcomps" level but I assume that "libcomps" cannot be documented until "comps.xml" is documented anyway.) -- Ticket URL: <https://fedorahosted.org/rel-eng/ticket/6144> Fedora Release Engineering <http://fedorahosted.org/rel-eng> Release Engineering for the Fedora Project

8 years, 12 months

1
5
0 / 0

[DRAFT] Requesting Review of koji-shadow documentation Draft

by Adam Miller

Hello all, Recently a thread was started on the Infrastructure list about the state of the staging koji and what exactly we want that to look like in the future so it lends itself more as a place we can iterate on the tooling, test new things, etc[0]. This was spawned partially by a conversation on irc and in that conversation we discussed koji-shadow a bit and as the new person in the group I went in search of documentation for koji-shadow so that I could learn what it is, how it works and how it might be applicable. Much to my surprise there was none so I started to nag people for information (special thanks to pbrobinson, dgilmore, nirik, and sharkcz for humoring me). I've put together some Draft documentation on Koji-Shadow and would like some review from the group at large who I have no doubt collectively knows exponentially more than I on the subject matter. My hope is that once this is in good shape it can be linked to from the main Koji page in the Fedora wiki and/or formatted into a markup/markdown syntax that upstream koji prefers and can be submitted upstream. (That is if koji upstream hosts docs somewhere other than the Fedora Wiki, which I'm actually not sure about since I see links to the Fedora Wiki from the Koji Fedorahosted page) tl;dr - Please review for accuracy and fill in blanks where needed: https://fedoraproject.org/wiki/Koji/DraftKojiShadowHowTo Thank you, -AdamM [0] - https://lists.fedoraproject.org/pipermail/infrastructure/2015-April/01612...

8 years, 12 months

1
0
0 / 0

2024

2023

2022

2021

2020

2019

2018

2017

2016

2015

2014

2013

2012

2011

2010

2009

2008

rel-eng May 2015