Search results

= Using the bodhi command-line interface = == Installing the client ==

...cker Hub. This change proposes that Fedora infrastructure is used to build the container instead. * Targeted release: 24

= Annobin Used By Bodhi = ...analysis of the security hardening of a compiled package when reviewing a Bodhi update.

Extend Koji with a new feature that allows users to generate yum repositories of signed RPMs. * Email: jgregusk with the usual red hat domain

Stop producing and distributing the Modular and Everything i686 repositories. * Targeted release: [[Releases/31| Fedora 31 ]]

...on out karma points for testing updates that you have currently installed. The typical workflow is as follows: ...r directly run fedora-easy-karma and test packages according to the update notes

...itted to a fedora-updates repository should not be automatically pushed to the stable repository when its karma threshold is reached. ...to be performed by different people from different teams. Please look at the ''Intermediate milestones'' section below.

The GHC Haskell compiler will be updated from major version 8.8 to 8.10, and Haskell packages will be updated from Stackage LTS 16 to LTS 18 versions.

= Additional buildroot to test x86-64 micro-architecture update = Create a dedicated buildroot to test packages built with x86-64 micro-architecture update.

...ntly targets end-users, however, this document may be updated periodically to target everyone. = What is Bodhi =

Note: meeting notes aren't regularly updated. ...org/wiki/ReleaseEngineering/ReleaseToolsMattDMPriorityNotes Matthew Miller notes] (representing RHEL, Council, etc)

...table rawhide as well as less work on the infrastructure and rel-eng teams to keep composes working. ...in two phases, at first only single package updates will be supported, in a second stage, we will add support for multi-packages updates.

...ke: Changes/Your_Change_Proposal_Name. This keeps all change proposals in the same namespace --> The GHC Haskell compiler will be updated from major version 8.6 to 8.8,

...table rawhide as well as less work on the infrastructure and rel-eng teams to keep composes working. ..., owners of all affected packages need to be included here. Alternatively, a SIG can be listed as an owner if it owns all affected packages.

= Make Fedora CoreOS a Fedora Edition = This change is to promote Fedora CoreOS to Edition status alongside Cloud, IoT, Server and Workstation.

...he Fedora brand, and if we want to see Fedora in use on the cloud, we need to step in and take responsibility for Fedora. ...: a process that creates Fedora EC2 images as a part of the regular Fedora release process, starting with Fedora 13.

Use this guide to determine to which category your proposed change belongs to. ...nges to isolated/leaf package without the impact on other packages/rest of the distribution

...systems to createrepo_c 1.0 and change repositories metadata settings <!-- The name of your change proposal --> = ...move all following releases to the new settings, while preserving most of the current settings for releases <= 40.

...ke: Changes/Your_Change_Proposal_Name. This keeps all change proposals in the same namespace --> = rpmautospec - removing release and changelog fields from spec files =

Use this guide to determine to which category your proposed change belongs to. ...nges to isolated/leaf package without the impact on other packages/rest of the distribution

...the standard format and templates improves the readability and quality of the pages. ...ugs'' keyword for the bug, and add a link to the Common Bugs page entry to the bug's ''Whiteboard'' field.

...probar/testar los paquetes acorde con las notas de actualización. (updates notes) You will be asked for every package installed from updates-testing to provide

Update the PHP stack in Fedora to the latest version 8.2.x ..., owners of all affected packages need to be included here. Alternatively, a SIG can be listed as an owner if it owns all affected packages.

Ongoing prioritization for release tools work from Matt Miller via bi-weekly sync. ...conversations with OpenShift team about deploying an OpenShift instance in the Fedora space & having more participation

Add the [https://github.com/juhp/fbrnch fbrnch] packager tool to Fedora. ...to be resolved. If the change proposal is owned by a SIG, please also add a primary contact person. -->

...er from major version 9.4 to 9.6 and Haskell packages from Stackage LTS 21 to LTS 22 versions. ..., owners of all affected packages need to be included here. Alternatively, a SIG can be listed as an owner if it owns all affected packages.

...ke: Changes/Your_Change_Proposal_Name. This keeps all change proposals in the same namespace --> This change is to enable package maintainers to build Flatpaks of their applications and make those Flatpaks available for

You will be asked for every package installed from updates-testing to provide for updates related to packages or builds that match any of the patterns.

The GHC Haskell compiler will be updated from minor version 8.10.5 to 8.10.7, and Haskell packages will be updated to Stackage LTS 18.28 minor versions.

Assorted information related to the Fedora Linux kernel. ...tiple major kernel versions throughout its life cycle. This wiki page used to list versions but it was frequently out of date.

...sion 9.2 to 9.4, and Haskell packages will be updated from Stackage LTS 20 to LTS 21 versions. ..., owners of all affected packages need to be included here. Alternatively, a SIG can be listed as an owner if it owns all affected packages.

You will be asked for every package installed from updates-testing to provide for updates related to packages or builds that match any of the patterns.

The GHC Haskell compiler will be updated from major version 8.10 to 9.2, and Haskell packages will be updated from Stackage LTS 18 to LTS 20 versions.

...all communication about no frozen rawhide now, and Alpha Freeze/branch in the future ...We should clarify why this process happens the way it does, and what led to this redesign.}}

= Modular Release = ...release, distribution, and update changes associated with and required for the [[Changes/Modular_Server]] and [[Changes/Host_and_Platform]] Changes.

...g them from happening again. When a new issue comes up, it should be added to this page. If you know of one not noted here, please do add it. ...sers. It's sorted in 'most recent first', so new issues should be added to the top.

Update Pyramid (package `python-pyramid` within Fedora) to latest major version. <!-- remove Category:ChangePageIncomplete and change it to Category:ChangeReadyForWrangler -->

Change how we build Flatpaks in Fedora to remove the dependency on modularity. Instead of using modules to rebuild Fedora packages with prefix=/app,

.... It is not a guide to using the Fedora package source control system: see the [[Package maintenance guide]] for that. ...for updates at various stages of the [[Fedora Release Life Cycle]], refer to [[Updates Policy]].

...ke: Changes/Your_Change_Proposal_Name. This keeps all change proposals in the same namespace --> Tooling changes to support the new way of branching for Fedora 27

<!-- All fields on this form are required to be accepted by FESCo. We also request that you maintain the same order of sections so that all of the feature pages are uniform. -->

<!-- All fields on this form are required to be accepted by FESCo. We also request that you maintain the same order of sections so that all of the feature pages are uniform. -->

== Notes == Main points of the policy

Use this guide to determine to which category your proposed change belongs to. ...nges to isolated/leaf package without the impact on other packages/rest of the distribution

...nge anything, change the original Feature page and it will be picked up in the next refresh. If not, ping jkurik. ...ing_Steering_Committee |Engineering Steering Committee]] for the Fedora 25 Release as System Wide Changes.

Update RPM to the [https://rpm.org/wiki/Releases/4.19.0 4.19] release. <!-- remove Category:ChangePageIncomplete and change it to Category:ChangeReadyForWrangler -->

...ke: Changes/Your_Change_Proposal_Name. This keeps all change proposals in the same namespace --> ...ke: Changes/Your_Change_Proposal_Name. This keeps all change proposals in the same namespace -->

...he "fiscal year" numeric naming is attached to the latest calendar year in the "fiscal year". Red Hat Fiscal Year 2013 (henceforth abbreviated as "FY13") In FY13, Red Hat hopes to hire people to fill the following full-time Fedora Engineering positions:

...nge anything, change the original Feature page and it will be picked up in the next refresh. If not, ping jkurik. ...ing_Steering_Committee |Engineering Steering Committee]] for the Fedora 27 Release as System Wide Changes.

= Layered Docker Image Build Service <!-- The name of your change proposal --> = Fedora currently ships a Docker base image, but Docker supports a layering concept.

Use this guide to determine to which category your proposed change belongs to. ...nges to isolated/leaf package without the impact on other packages/rest of the distribution

...ke: Changes/Your_Change_Proposal_Name. This keeps all change proposals in the same namespace --> = LLVM 17 <!-- The name of your change proposal --> =

...chemy are identified and, if necessary, steps are taken to ensure they use the correct major version package. <!-- remove Category:ChangePageIncomplete and change it to Category:ChangeReadyForWrangler -->

...ke: Changes/Your_Change_Proposal_Name. This keeps all change proposals in the same namespace --> = Retire Modularity <!-- The name of your change proposal --> =

Use this guide to determine to which category your proposed change belongs to. ...nges to isolated/leaf package without the impact on other packages/rest of the distribution

Allow on-demand side tags, and allow packagers to a) tag whatever rpms as build dependencies into those side tags, b) build pac ...viding a subset of Modularity features in an additive way (no influence on the way dependent packages are built or installed). It may also coexist with Mo

{{admon/tip | Guidance | For details on how to fill out this form, see the [https://docs.fedoraproject.org/en-US/program_management/changes_guide/ doc ...ke: Changes/Your_Change_Proposal_Name. This keeps all change proposals in the same namespace -->

...ke: Changes/Your_Change_Proposal_Name. This keeps all change proposals in the same namespace --> = LLVM 18 <!-- The name of your change proposal --> =

...[[How_to_create_a_GNU_Hello_RPM_package/zh-tw]] 教程，或是另一份更深入且有更多細節的 [[how to create an RPM package/zh-tw]]。 你的 koji 軟體包建置僅可以依賴 TARGET 散布版軟體庫中實際擁有的軟體包。因此，若你的軟體包依賴 Bodhi 尚未發行的新軟體包的話，你就無法使用 koji 為發行的散

Fedora Project welcomes you to the Fedora Weekly News(FWN): Issue 296<ref>http://fedoraproject.org/wiki/FWN/Is ...articular interest at any time; meantime if you interested in contributing to Fedora Weekly News, please see our 'join' page<ref>http://fedoraproject.org

...ke: Changes/Your_Change_Proposal_Name. This keeps all change proposals in the same namespace --> = Changes of defaults in createrepo_c-1.0.0 <!-- The name of your change proposal --> =

Unable to attend: : While suggestions keep coming, this '''really''' is the ''Last call'' for feedback on [[Fedora_14_QA_Retrospective]]

...ose components, or the open source packaging system used by the developers to publish them'' ...his, it is proposed to explicitly split the software assembly process into the following stages:

...058] Blocked on compose request for setup and generating torrents which is the remaining known rel eng work for this effort. ...style="background-color:yellow;" | At risk || Greenwave to give results on the gating criteria. || Investigation on implementing policy change.

...ke: Changes/Your_Change_Proposal_Name. This keeps all change proposals in the same namespace --> ...uld be in the Benefit to Fedora section below, and this part should answer the question "What?" rather than "Why?". -->

...ke: Changes/Your_Change_Proposal_Name. This keeps all change proposals in the same namespace --> Python 2 is reaching end of life, and the current maintainers would like to

= Rawhide synchronization for the GNU C Library = Make sure you have authenticated and meet the pre-requisites (see notes below).

= RPM-level auto release and changelog bumping = ...at-rpm-config will be updated so users of the auto framework get automated release and changelog bumping.

...ke: Changes/Your_Change_Proposal_Name. This keeps all change proposals in the same namespace --> = LLVM 19 <!-- The name of your change proposal --> =

Use this guide to determine to which category your proposed change belongs to. ...nges to isolated/leaf package without the impact on other packages/rest of the distribution

This page contains various Fedora presentations made by people in the Fedora project. ...organizes content for us using the table of contents. I'm commenting out the following hard-coded custom TOC for now. -->

...egration testing will be provided to Fedora packagers so that they can see the potential impact of their changes on RHEL development. ...disrupt the rest of Fedora. It will also aid us in future-proofing some of the spec file conditionals today that assume RHEL <= 8.

...r.C3.B6dinger.27s_Cat.29|Schrödinger's Cat]]), ambassadors discussed about the gift for their job. This gift is a "thank you" T-shirt.

...egration testing will be provided to Fedora packagers so that they can see the potential impact of their changes on RHEL development. ...disrupt the rest of Fedora. It will also aid us in future-proofing some of the spec file conditionals today that assume RHEL <= 8.

* Viking-Ice investigating adding an LXDE test day to the F-13 test day schedule * maxamillion investigating scheduling a XFCE test day to F-13 test day schedule

...SS). Our goal in this celebration is to educate the worldwide public about the benefits of using high quality FOSS in education, in government, at home, a ...agenda and timeline, but there are specific things that Fedora is helping to support this year.

...for it, unless otherwise instructed.'' Where appropriate, a reference to the current bug(s) in Bugzilla is included. == Release Notes ==

* [[How to create and use a Live CD/zh-cn|HOWTO 制作一张基于 Fedora 系统的定制版 LiveCD]] * [[How to create and use Live USB/zh-cn|HOWTO 创建并使用 Fedora 启动 U 盘]]

...TE - SEE [https://docs.fedoraproject.org/en-US/epel/ THE EPEL DOCS] FOR UP TO DATE INFORMATION.''' ...ect to create a repository of high-quality add-on packages that complement the Fedora-based Red Hat Enterprise Linux (RHEL) and its compatible spinoffs, s

You've heard me talk about it many times, but time is running out to voice yours concerns and suggestions about Fedora 13 Testing. Be heard at Last week, kparal asked the group whether there was interest in QA Summer of code projects. Feedback o

...led. For any support request, please reach translator mailing list or open a ticket there: https://pagure.io/fedora-l10n/tickets [[L10N/Translation Plat ** Ticket about public event at [[Flock]] to validate this migration plan: https://pagure.io/flock/issue/144

...for it, unless otherwise instructed.'' Where appropriate, a reference to the current bug(s) in Bugzilla is included. == Release Notes ==

# [adamw] - BugStatusWorkFlow - to file a ticket to get bodhi fixed #* https://fedorahosted.org/bodhi/ticket/320 is the ticket, lmacken will look into this

...case koji will do test builds on all the architectures the spec file says the package supports. ...e the spec file, use <code>rpmbuild --nodeps -bs SPECFILE</code> to create the new source RPM).

...ke: Changes/Your_Change_Proposal_Name. This keeps all change proposals in the same namespace --> = Python: Add -P to default shebangs <!-- The name of your change proposal --> =

...is using and end-of-life translation platform, and need to find a new tool to support our team activity. ...r a significant period, at least for a decade. It means we need to be able to reach stability continuity.

* current members of the 'qa' group ... apply to 'proventesters' * jlaska to follow-up w/ maxamillion after meeting

Find an idea you like? Want to propose your own? See our Getting Started Guide: http://groups.google.com/group/redhat-summer/web/gsoc-getting-started

...features when talking about the release, and to help drive content for the release, etc. ...nts are based in part on the [[Releases/27/ChangeSet|Change Set]] for this release.

* Viking-Ice write lxde tests and find a date for the test day ...ed.org/fedora-qa/ticket/46 ticket#46], agreed to move future discussion to the ticket

Unable to attend: == Release criteria updates ==

...ly a waiting game on our end but I also know we need to start planning out a Test day'' ** Will continue monitoring XFCE 4.8 schedule, and may choose to hold a test day even if it slips.

* ARM is clearly now a Big Important Thing * We will want to do some best-effort testing on it and try and work it into the validation process somehow for F17

...ts. Please see [https://fedoraproject.org/wiki/Changes/SwitchToDnf5 Switch to DNF5] for updated version of this change.}} = Make DNF5 The Default =

...ve|Ideas have already been coming in since F-13-Alpha. It's not too early to note QA issues you felt where handled '''well''', or could have been '''imp ...EAD infrastructure.git]), but promised to follow-up with ''fenris02' after the meeting

...bz|541645}} - PackageKit - System Update fails with PackageKit GUI ("Error getting ... *** jlaska to check with halfline for details

Unable to attend: ...test day is scheduled on 7th of April now, which collides with the GNOME3 release again

Unable to attend: # adamw and jlaska to propose artwork final release criteria

...for it, unless otherwise instructed.'' Where appropriate, a reference to the current bug(s) in Bugzilla is included. == Release Notes ==

...n un mantenedor de paquetes para el Proyecto Fedora. Esta guí­a te llevará a través de tu primera entrega de un paquete. ...roject.org/wiki/Packaging/Guidelines) y Los Lineamientos de Colocar Nombre a los Paquetes ("PackageNamingGuidelines":https://fedoraproject.org/wiki/Pack

...for it, unless otherwise instructed.'' Where appropriate, a reference to the current bug(s) in Bugzilla is included. == Release Notes ==

= Fedora Release Engineering Meeting :: Monday 2009-02-09 = * the createrepo stuff is already taken care of in createrepo, and in pungi upstr

* Viking-Ice investigating creating a test case for bug#530452 ... and adding to F12 install matrix ...is update. [[User:rhe]] and [[User:Kparal]] have adding their thoughts to the issue.

=== Fedora Classroom - Beginner's guide to getting involved - Paul Frields - Saturday, November 8, 2008 === ==== IRC Log of the Class ====

Find an idea you like? Want to propose your own? See the Getting Started Guide with GSoC: Further, last year accepted ideas from the Fedora Project can be found at [http://www.google-melange.com/gsoc/org/goog

Unable to attend: * Milestone missed due to...

# jlaska to migrate approved FAS 'qa' members into 'proventesters' # jlaska to request bodhi change to require 'proventesters' feedback for critpath

There's a ''discussion'' tab above.}} '''First see the [https://fedoraproject.org/wiki/Changes/InvokingTests#Terminology Terminogy

Unable to attend: # tflink to follow-up with cloud sig for test day recap

* [wwoods] - write a few more upgrade cases (encrypted root upgrade) *: Been doing a lot of upgrades this past week, but haven't documented them.

This page gathers all the ideas and pointers/references for the 2008 intern and Summer coding programs. ...ere you want to learn about or hack on, contact the people associated with the idea.'''

| colspan="2" | ---nirik has changed the topic to: Fedora IRC Classroom Fedora 11 Features with your teacher Jon Stanley ( jd | style="color: #42427e" | I think yum info will tell you that as long as the packname is unique across repos.

...for it, unless otherwise instructed.'' Where appropriate, a reference to the current bug(s) in Bugzilla is included. == Release Notes ==

...for it, unless otherwise instructed.'' Where appropriate, a reference to the current bug(s) in Bugzilla is included. == Release Notes ==

...for it, unless otherwise instructed.'' Where appropriate, a reference to the current bug(s) in Bugzilla is included. == Release Notes ==

Unable to attend: ..._process]] with information about how to handle FAS group requests without a corresponding ticket

...for it, unless otherwise instructed.'' Where appropriate, a reference to the current bug(s) in Bugzilla is included. With the alpha release of Fedora 12 comes the [[Common_F12_bugs]] page.

Welcome to Fedora Weekly News Issue 151 for the week ending November 9th, 2008. ...addition of LiveConnect to IcedTea; Artwork relays well-earned "Praise for the Solar Theme". Translation covers l10n work being done and SecurityAdvisorie

...k bugzilla guys to add a link from the bugzilla fields description page to the wiki page, for fedora ...}), waiting for bugzilla code update during next outage window for changes to go live

* [wwoods] - checking for a bug about an upgrade issue ** Performing a lot of upgrade tests and working w/ dwalsh to identify+resolve issues

# jlaska to add bugzilla shared query links to Common_Bugs wiki page #* beland added links to [[Common_F13_bugs]] page

| style="color: #407a40" | okay! let's talk about the Beta for a bit. ...een going on, and I've been trying to keep track of stuff reported against the Beta

...for it, unless otherwise instructed.'' Where appropriate, a reference to the current bug(s) in Bugzilla is included. == Release Notes ==

Unable to attend: # tflink looked into stale -pending tags and determine whether autoqa or bodhi bug ... good news, false alarm (see https://fedorahosted.org/pipermail/auto

...ly News Issue 227<ref>http://fedoraproject.org/wiki/FWN/Issue227</ref> for the week ending May 26, 2010. What follows are some highlights from this issue ...ng Project, with a status update on what students and their mentors are up to. Enjoy Fedora 227 and Fedora 13!

...[How_to_use_PreUpgrade]] and we've had several additional contributions to the troubleshooting section from [[User:Toshio]] and [[User:Mccann]]. ...is update. [[User:rhe]] and [[User:Kparal]] have adding their thoughts to the issue.

Release engineering Alpha candidate RC1 is available, Fedora QA will be responsible * Testing the alpha candidate -- [[QA:Fedora_12_Alpha_RC1_Install_Test_Results]]

...dora-townhall by the moderator (me!). Candidates will answer (and discuss) the questions there. ..." | To begin, I invite each candidate -- in alpha order by nick -- to give a 1-line intro.

...for it, unless otherwise instructed.'' Where appropriate, a reference to the current bug(s) in Bugzilla is included. == Release Notes ==

= FUDCon related posts to Fedora Planet = ...arket I just visited I can tell that there is enough fresh food to prepare a decent dinner myself.