Changeset 1629


Ignore:
Timestamp:
Sep 8, 2010, 10:09:17 PM (11 years ago)
Author:
ezyang
Message:
Add more suggestions for fixing patches.
File:
1 edited

Legend:

Unmodified
Added
Removed
  • branches/fc13-dev/server/doc/upgrade-tips

    r1617 r1629  
    6464are covered in 'package-build-howto', but a new Fedora release tends
    6565to also result in somewhat rarer situations.
     66
     67As you finish building packages, you'll want to place them somewhere
     68so they don't get blown away on a successive mock build.  ~/mock-local
     69is a good choice.  The Mock RPMs will be created in:
     70
     71    /var/lib/mock/$MOCK_ENV/result/
    6672
    6773Here are some of the common troubles you'll have to deal with:
     
    131137    The error message will be from within a schroot that Mock is using.
    132138    As a result, it's not immediately obvious where the files live.
    133     There are two approaches you can take:
    134139
    135     Find the schroot: XXX to write
     140    The easiest approach is to use rpmbuild to manually reapply the
     141    patches.
    136142
    137     Manually patch the source dist: Tarballs for the original source can
    138     be found in ~/rpmbuild/SOURCES, and then you can manually apply the
    139     failing patches and debug from there.
     143        rpmbuild -bp path/to/foo.spec
     144
     145    If this fails complaining about a dependency, you should install
     146    the dependency and add it to the Makefile.
     147
     148    Once you've fixed the patch, you can rerun rpmbuild after running
     149
     150        make setup
     151
     152    (This is useful if you can't do a full make due to another mock
     153    process running.)
    140154
    1411554. "Officializing" everything
Note: See TracChangeset for help on using the changeset viewer.