From Fedora Project Wiki

(Created page with "== Goal == The goal is to rebuild every single Fedora package, regardless of content, before the Fedora 27 Feature Freeze Change Deadline. == Driving Features == * [[Changes/...")
 
 
(One intermediate revision by the same user not shown)
Line 1: Line 1:
== Goal ==
+
= Mohan Boddu =
The goal is to rebuild every single Fedora package, regardless of
 
content, before the Fedora 27 Feature Freeze Change Deadline.
 
  
== Driving Features ==
+
{{Template:Userpage/Infobox2
* [[Changes/golang1.9| golang 1.9 ]]
+
|REAL-NAME=Mohan Boddu
* [[Changes/ParallelInstallableDebuginfo| Parallel Installable Debuginfo ]]
+
|FAS-NAME=mohanboddu
* [[Changes/RPM-4.14| RPM 4.14 ]]
+
|HOME=Nashua, NH
* [[Changes/SubpackageAndSourceDebuginfo| Subpackage And Source Debuginfo ]]
+
|IRC=mboddu
 +
|irc-channels= #fedora-admin, #fedora-releng
 +
|pmail=mboddu@bhujji.com
 +
|homepage=http://bhujji.com/
 +
}}
  
== Schedule ==
+
== About Me ==
Given the changes required for the above features and the given
 
schedules, Release Engineering will be ready to start scripted rebuilds
 
on Tuesday, July 25th.  All automated rebuilds should be finished prior to the Feature Freeze.
 
Any clean-up manual rebuilds should be finished prior to the Bodhi Enablement Deadline.
 
  
== Scripts ==
+
Currently working as Release Engineer for Fedora.
Release Engineering has created two scripts.  One is to initiate the builds, and the other is to query for items still needing to be built.
 
 
 
=== Build Initiation ===
 
The rebuild [https://pagure.io/releng/blob/master/f/scripts/mass-rebuild.py script] works in the following way:
 
 
 
  Generate a list of all packages in f27
 
  Loop through each package:
 
    Query if a build has already been attempted/completed since koji changes went live.
 
    If so, move to next package
 
    If not, check out git
 
    rpmdev-bumpspec
 
    fedpkg commit -cp
 
    fedpkg (background) build
 
    Move on to next package
 
 
 
Each step will have some error catching and logging so that people
 
can clean up the various failures for whatever reasons.  The builds will
 
be background builds, which will allow other builds done to take higher
 
priority when a builder has a free slot.  However maintainers should
 
take care when doing this so that the background build won't take
 
'latest' precedent when it finishes.  Asking rel-eng to kill the
 
scripted build will typically be enough.
 
 
 
=== Build Tagging ===
 
Once the rebuild script has finished, another [https://pagure.io/releng/blob/master/f/scripts/mass-tag.py script] will run to tag the builds into f27.  This script will check that a newer build hasn't been done or started in f27 since the scripted rebuild was submitted.  This will protect against the scripted rebuild overriding an even newer build done while the scripted rebuild was waiting in the background.
 
 
 
=== Status Query ===
 
Release Engineering has developed a [https://pagure.io/releng/blob/master/f/scripts/need-rebuild.py script] to query f27
 
and report on packages that have yet to be rebuilt.  Results of these
 
queries will be delivered to various places, yet to be determined,
 
broken down by maintainer for easier discovery of work needed.
 
 
 
== Maintainer Actions ==
 
* Maintainers can help this effort by ensuring '''rpmdev-bumpspec''' correctly bumps your package's spec files.
 
* Maintainers should ensure that their packages currently build from source.
 
* Maintainers should ensure that there are no unwanted changes committed to git but not built yet.
 
 
 
== Frequently Asked Questions ==
 
=== When will my own build "count" for the rebuild? ===
 
After the last piece needed for the mass rebuild a rpm build was put into place, a build done by a maintainer will "count" toward the rebuild. 2017-07-25 20:27:50 is the UTC time that builds count from
 
 
 
=== Will the rebuilds be ordered? ===
 
Currently there is no plan to logically order the rebuilds based on deps.  The ordering will be alphanumerical based on package name.  There are no planned ABI/soname changes that would require logical build ordering.  Further, all the builds will be kept in a special tag (f27-rebuild) until the whole run is done, and then they will be tagged into f27 in one shot to minimize the shuffle of buildroot contents during the rebuilds.
 
 
 
 
 
== Feedback ==
 
 
 
Questions/comments/concerns should be directed to [https://lists.fedoraproject.org/mailman/listinfo/devel], or #fedora-releng on freenode IRC.
 

Latest revision as of 20:05, 8 September 2017

Mohan Boddu

Mohan Boddu
[[Image:{{{image}}}|center|250px|Mohan Boddu]]
Fedora Information
FAS name: mohanboddu
Fedora email: mohanboddu@fedoraproject.org
IRC nick: mboddu
IRC channels: #fedora-admin, #fedora-releng
Fedorapeople page: https://mohanboddu.fedorapeople.org
Badges (96)
Horcrux Involvement Crypto Badger Bona Fide Baby Badger Paranoid Panda Maestro Crypto Panda If you build it... (Koji Success I) Speak Up! You can call me "Patches" (SCM I) White Rabbit Secretary General Junior Badger (Badger I) Macaron (Cookie I) Take this and call me in the morning What goes around comes around (Karma I) Is this thing on? (Updates-Testing I) Like a Rock (Updates-Stable I) Binary Star Junior Editor Chocolate Chip (Cookie II) If you build it... (Koji Success II) What goes around comes around (Karma II) You can call me "Patches" (SCM II) In Search of the Bull (Tester I) What goes up... (Koji Failure I) Associate Badger (Badger 1.5) Is this thing on? (Updates-Testing II) What goes around comes around (Karma III) Like a Rock (Updates-Stable II) If you build it... (Koji Success III) You can call me "Patches" (SCM III) Black and White (Cookie III) Associate Editor Helping Hand Let Me Introduce Myself Override, you say? Discovery of the Footprints (Tester II) What goes around comes around (Karma IV) Pizzelle (Cookie IV) Embryo Top 500 Flock 2018 Attendee Fedora 29 Change Accepted Let's do lunch! Rollercoaster Restaurant Senior Badger (Badger II) What goes up... (Koji Failure II) Perceiving the Bull (Tester III) Is this thing on? (Updates-Testing III) Catching the Bull (Tester IV) DevConf 2019 Attendee Proven Packager Mugshot It's a Cake Thing You can call me "Patches" (SCM IV) FOSDEM 2019 Attendee Long Life to Pagure (Pagure I) Taming the Bull (Tester V) Long Life to Pagure (Pagure IV) Long Life to Pagure (Pagure II) FOSDEM 2020 Attendee Long Life to Pagure (Pagure III) Long Life to Pagure (Pagure VI) Trust me, I know what I am doing Flock 2019 Attendee What goes up... (Koji Failure III) You’re on a boat! Long Life to Pagure (Pagure V) DevConf.cz 2020 Attendee Readiness Senior Editor Rainbow (Cookie V) If you build it... (Koji Success IV) Like a Rock (Updates-Stable III) I Voted: Fedora 33 Fedora 34 Change Accepted nest-attendee-2020 White Hat What goes up... (Koji Failure IV) All your $arch are belong to us (Koji Success V) Hindenburg (Koji Failure V) Community Survey Taker I FOSDEM 2021 Attendee Tadpole Egg Tadpole with Legs United Packages of Fedora Corporate Drone The Last Argument of Kings Nest Attendee 2021 Fedora Mentor Summit 2022 Museum Visitor Lets have a party Fedora 35 DevConf.cz 2022 Attendee
 

About Me

Currently working as Release Engineer for Fedora.