[Gambas-user] Problems with "Make installation packages"
Carsten Olsen
carsten at ...500...
Thu Jun 24 16:15:26 CEST 2004
Hi Benoit
The required man for RPM plus RPMBUILD (from FC2)
Kind Regards
Carsten Olsen
On Thu, 2004-06-24 at 01:11, Benoit Minisini wrote:
> On Wednesday 23 June 2004 15:56, Carsten Olsen wrote:
> > Hi
> >
> > I have tried the new function "Make installation packages""Make
> > installation packages". I tried to build RPM to Redhat / Fedora (on a
> > Fedora Core 2 box) but I get this message in the make... dialog.
> >
> > Creating package for Redhat /Fedora.
> > Creating source package.
> > Creating .spec file.
> > Creating RPM packages.
> > The package build has failed.
> >
> > -ba: unknown option
> >
> > Kind regards
> > Carsten Olsen
>
> Can you send me the result of "man rpm" on your Fedora ?
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.gambas-basic.org/pipermail/user/attachments/20040624/057a1970/attachment.html>
-------------- next part --------------
RPMBUILD(8) Red Hat Linux RPMBUILD(8)
NNAAMMEE
rpmbuild - Build RPM Package(s)
SSYYNNOOPPSSIISS
BBUUIILLDDIINNGG PPAACCKKAAGGEESS::
rrppmmbbuuiilldd {--bbaa||--bbbb||--bbpp||--bbcc||--bbii||--bbll||--bbss} [rrppmmbbuuiilldd--ooppttiioonnss] _S_P_E_C_F_I_L_E _._._.
rrppmmbbuuiilldd {--ttaa||--ttbb||--ttpp||--ttcc||--ttii||--ttll||--ttss} [rrppmmbbuuiilldd--ooppttiioonnss] _T_A_R_B_A_L_L _._._.
rrppmmbbuuiilldd {----rreebbuuiilldd||----rreeccoommppiillee} _S_O_U_R_C_E_P_K_G _._._.
MMIISSCCEELLLLAANNEEOOUUSS::
rrppmmbbuuiilldd ----sshhoowwrrcc
rrppmmbbuuiilldd--ooppttiioonnss
[----bbuuiillddrroooott _D_I_R_E_C_T_O_R_Y] [----cclleeaann] [----nnoobbuuiilldd]
[----rrmmssoouurrccee] [----rrmmssppeecc] [----sshhoorrtt--cciirrccuuiitt] [----ssiiggnn]
[----ttaarrggeett _P_L_A_T_F_O_R_M]
DDEESSCCRRIIPPTTIIOONN
rrppmmbbuuiilldd is used to build both binary and source software packages. A
ppaacckkaaggee consists of an archive of files and meta-data used to install
and erase the archive files. The meta-data includes helper scripts,
file attributes, and descriptive information about the package. PPaacckk--
aaggeess come in two varieties: binary packages, used to encapsulate soft-
ware to be installed, and source packages, containing the source code
and recipe necessary to produce binary packages.
One of the following basic modes must be selected: BBuuiilldd PPaacckkaaggee, BBuuiilldd
PPaacckkaaggee ffrroomm TTaarrbbaallll, RReeccoommppiillee PPaacckkaaggee, SShhooww CCoonnffiigguurraattiioonn.
GGEENNEERRAALL OOPPTTIIOONNSS
These options can be used in all the different modes.
--??,, ----hheellpp
Print a longer usage message then normal.
----vveerrssiioonn
Print a single line containing the version number of rrppmm being
used.
----qquuiieett
Print as little as possible - normally only error messages will
be displayed.
--vv Print verbose information - normally routine progress messages
will be displayed.
--vvvv Print lots of ugly debugging information.
----rrccffiillee _F_I_L_E_L_I_S_T
Each of the files in the colon separated _F_I_L_E_L_I_S_T is read
sequentially by rrppmm for configuration information. Only the
first file in the list must exist, and tildes will be expanded
to the value of $$HHOOMMEE. The default _F_I_L_E_L_I_S_T is
_/_u_s_r_/_l_i_b_/_r_p_m_/_r_p_m_r_c:_/_u_s_r_/_l_i_b_/_r_p_m_/_r_e_d_-
_h_a_t_/_r_p_m_r_c:_/_e_t_c_/_r_p_m_r_c:_~_/_._r_p_m_r_c.
----ppiippee _C_M_D
Pipes the output of rrppmm to the command _C_M_D.
----ddbbppaatthh _D_I_R_E_C_T_O_R_Y
Use the database in _D_I_R_E_C_T_O_R_Y rather than the default path
_/_v_a_r_/_l_i_b_/_r_p_m
----rroooott _D_I_R_E_C_T_O_R_Y
Use the file system tree rooted at _D_I_R_E_C_T_O_R_Y for all operations.
Note that this means the database within _D_I_R_E_C_T_O_R_Y will be used
for dependency checks and any scriptlet(s) (e.g. %%ppoosstt if
installing, or %%pprreepp if building, a package) will be run after a
chroot(2) to _D_I_R_E_C_T_O_R_Y.
BBUUIILLDD OOPPTTIIOONNSS
The general form of an rpm build command is
rrppmmbbuuiilldd --bb_S_T_A_G_E||--tt_S_T_A_G_E [ rrppmmbbuuiilldd--ooppttiioonnss
] _F_I_L_E _._._.
The argument used is --bb if a spec file is being used to build the pack-
age and --tt if rrppmmbbuuiilldd should look inside of a (possibly compressed)
tar file for the spec file to use. After the first argument, the next
character (_S_T_A_G_E) specifies the stages of building and packaging to be
done and is one of:
--bbaa Build binary and source packages (after doing the %prep, %build,
and %install stages).
--bbbb Build a binary package (after doing the %prep, %build, and
%install stages).
--bbpp Executes the "%prep" stage from the spec file. Normally this
involves unpacking the sources and applying any patches.
--bbcc Do the "%build" stage from the spec file (after doing the %prep
stage). This generally involves the equivalent of a "make".
--bbii Do the "%install" stage from the spec file (after doing the
%prep and %build stages). This generally involves the equiva-
lent of a "make install".
--bbll Do a "list check". The "%files" section from the spec file is
macro expanded, and checks are made to verify that each file
exists.
--bbss Build just the source package.
The following options may also be used:
----bbuuiillddrroooott _D_I_R_E_C_T_O_R_Y
When building a package, override the BuildRoot tag with direc-
tory _D_I_R_E_C_T_O_R_Y.
----cclleeaann
Remove the build tree after the packages are made.
----nnoobbuuiilldd
Do not execute any build stages. Useful for testing out spec
files.
----rrmmssoouurrccee
Remove the sources after the build (may also be used standalone,
e.g. "rrppmmbbuuiilldd ----rrmmssoouurrccee ffoooo..ssppeecc").
----rrmmssppeecc
Remove the spec file after the build (may also be used stan-
dalone, eg. "rrppmmbbuuiilldd ----rrmmssppeecc ffoooo..ssppeecc").
----sshhoorrtt--cciirrccuuiitt
Skip straight to specified stage (i.e., skip all stages leading
up to the specified stage). Only valid with --bbcc and --bbii.
----ssiiggnn Embed a GPG signature in the package. This signature can be used
to verify the integrity and the origin of the package. See the
section on GPG SIGNATURES in rrppmm(8) for configuration details.
----ttaarrggeett _P_L_A_T_F_O_R_M
When building the package, interpret _P_L_A_T_F_O_R_M as aarrcchh--vveennddoorr--ooss
and set the macros %%__ttaarrggeett, %%__ttaarrggeett__ccppuu, and %%__ttaarrggeett__ooss
accordingly.
RREEBBUUIILLDD AANNDD RREECCOOMMPPIILLEE OOPPTTIIOONNSS
There are two other ways to invoke building with rpm:
rrppmmbbuuiilldd ----rreebbuuiilldd||----rreeccoommppiillee _S_O_U_R_C_E_P_K_G _._._.
When invoked this way, rrppmmbbuuiilldd installs the named source package, and
does a prep, compile and install. In addition, ----rreebbuuiilldd builds a new
binary package. When the build has completed, the build directory is
removed (as in ----cclleeaann) and the the sources and spec file for the pack-
age are removed.
SSHHOOWWRRCC
The command
rrppmmbbuuiilldd ----sshhoowwrrcc
shows the values rrppmmbbuuiilldd will use for all of the options are currently
set in _r_p_m_r_c and _m_a_c_r_o_s configuration file(s).
FFIILLEESS
rrppmmrrcc CCoonnffiigguurraattiioonn
_/_u_s_r_/_l_i_b_/_r_p_m_/_r_p_m_r_c
_/_u_s_r_/_l_i_b_/_r_p_m_/_r_e_d_h_a_t_/_r_p_m_r_c
_/_e_t_c_/_r_p_m_r_c
_~_/_._r_p_m_r_c
MMaaccrroo CCoonnffiigguurraattiioonn
_/_u_s_r_/_l_i_b_/_r_p_m_/_m_a_c_r_o_s
_/_u_s_r_/_l_i_b_/_r_p_m_/_r_e_d_h_a_t_/_m_a_c_r_o_s
_/_e_t_c_/_r_p_m_/_m_a_c_r_o_s
_~_/_._r_p_m_m_a_c_r_o_s
DDaattaabbaassee
_/_v_a_r_/_l_i_b_/_r_p_m_/_B_a_s_e_n_a_m_e_s
_/_v_a_r_/_l_i_b_/_r_p_m_/_C_o_n_f_l_i_c_t_n_a_m_e
_/_v_a_r_/_l_i_b_/_r_p_m_/_D_i_r_n_a_m_e_s
_/_v_a_r_/_l_i_b_/_r_p_m_/_F_i_l_e_m_d_5_s
_/_v_a_r_/_l_i_b_/_r_p_m_/_G_r_o_u_p
_/_v_a_r_/_l_i_b_/_r_p_m_/_I_n_s_t_a_l_l_t_i_d
_/_v_a_r_/_l_i_b_/_r_p_m_/_N_a_m_e
_/_v_a_r_/_l_i_b_/_r_p_m_/_P_a_c_k_a_g_e_s
_/_v_a_r_/_l_i_b_/_r_p_m_/_P_r_o_v_i_d_e_n_a_m_e
_/_v_a_r_/_l_i_b_/_r_p_m_/_P_r_o_v_i_d_e_v_e_r_s_i_o_n
_/_v_a_r_/_l_i_b_/_r_p_m_/_P_u_b_k_e_y_s
_/_v_a_r_/_l_i_b_/_r_p_m_/_R_e_m_o_v_e_d
_/_v_a_r_/_l_i_b_/_r_p_m_/_R_e_q_u_i_r_e_n_a_m_e
_/_v_a_r_/_l_i_b_/_r_p_m_/_R_e_q_u_i_r_e_v_e_r_s_i_o_n
_/_v_a_r_/_l_i_b_/_r_p_m_/_S_h_a_1_h_e_a_d_e_r
_/_v_a_r_/_l_i_b_/_r_p_m_/_S_i_g_m_d_5
_/_v_a_r_/_l_i_b_/_r_p_m_/_T_r_i_g_g_e_r_n_a_m_e
TTeemmppoorraarryy
_/_v_a_r_/_t_m_p_/_r_p_m_*
SSEEEE AALLSSOO
ppoopptt(3),
rrppmm22ccppiioo(8),
ggeennddiiffff(1),
rrppmm(8),
hhttttpp::////wwwwww..rrppmm..oorrgg// <<UURRLL::hhttttpp::////wwwwww..rrppmm..oorrgg//>>
AAUUTTHHOORRSS
Marc Ewing <marc at ...34...>
Jeff Johnson <jbj at ...34...>
Erik Troan <ewt at ...34...>
Red Hat, Inc. 09 June 2002 RPMBUILD(8)
-------------- next part --------------
RPM(8) Red Hat Linux RPM(8)
NNAAMMEE
rpm - RPM Package Manager
SSYYNNOOPPSSIISS
QQUUEERRYYIINNGG AANNDD VVEERRIIFFYYIINNGG PPAACCKKAAGGEESS::
rrppmm {--qq||----qquueerryy} [sseelleecctt--ooppttiioonnss] [qquueerryy--ooppttiioonnss]
rrppmm {--VV||----vveerriiffyy} [sseelleecctt--ooppttiioonnss] [vveerriiffyy--ooppttiioonnss]
rrppmm ----iimmppoorrtt _P_U_B_K_E_Y _._._.
rrppmm {--KK||----cchheecckkssiigg} [----nnoossiiggnnaattuurree] [----nnooddiiggeesstt]
_P_A_C_K_A_G_E___F_I_L_E _._._.
IINNSSTTAALLLLIINNGG,, UUPPGGRRAADDIINNGG,, AANNDD RREEMMOOVVIINNGG PPAACCKKAAGGEESS::
rrppmm {--ii||----iinnssttaallll} [iinnssttaallll--ooppttiioonnss] _P_A_C_K_A_G_E___F_I_L_E _._._.
rrppmm {--UU||----uuppggrraaddee} [iinnssttaallll--ooppttiioonnss] _P_A_C_K_A_G_E___F_I_L_E _._._.
rrppmm {--FF||----ffrreesshheenn} [iinnssttaallll--ooppttiioonnss] _P_A_C_K_A_G_E___F_I_L_E _._._.
rrppmm {--ee||----eerraassee} [----aallllmmaattcchheess] [----nnooddeeppss] [----nnoossccrriippttss]
[----nnoottrriiggggeerrss] [----rreeppaacckkaaggee] [----tteesstt] _P_A_C_K_A_G_E___N_A_M_E _._._.
MMIISSCCEELLLLAANNEEOOUUSS::
rrppmm {----iinniittddbb||----rreebbuuiillddddbb}
rrppmm {----aaddddssiiggnn||----rreessiiggnn} _P_A_C_K_A_G_E___F_I_L_E _._._.
rrppmm {----qquueerryyttaaggss||----sshhoowwrrcc}
rrppmm {----sseettppeerrmmss||----sseettuuggiiddss} _P_A_C_K_A_G_E___N_A_M_E _._._.
sseelleecctt--ooppttiioonnss
[_P_A_C_K_A_G_E___N_A_M_E] [--aa,,----aallll] [--ff,,----ffiillee _F_I_L_E]
[--gg,,----ggrroouupp _G_R_O_U_P] {--pp,,----ppaacckkaaggee _P_A_C_K_A_G_E___F_I_L_E]
[----ffiilleeiidd _M_D_5] [----hhddrriidd _S_H_A_1] [----ppkkggiidd _M_D_5] [----ttiidd _T_I_D]
[----qquueerryybbyynnuummbbeerr _H_D_R_N_U_M] [----ttrriiggggeerreeddbbyy _P_A_C_K_A_G_E___N_A_M_E]
[----wwhhaattpprroovviiddeess _C_A_P_A_B_I_L_I_T_Y] [----wwhhaattrreeqquuiirreess _C_A_P_A_B_I_L_I_T_Y]
qquueerryy--ooppttiioonnss
[----cchhaannggeelloogg] [--cc,,----ccoonnffiiggffiilleess] [--dd,,----ddooccffiilleess] [----dduummpp]
[----ffiilleessbbyyppkkgg] [--ii,,----iinnffoo] [----llaasstt] [--ll,,----lliisstt]
[----pprroovviiddeess] [----qqff,,----qquueerryyffoorrmmaatt _Q_U_E_R_Y_F_M_T]
[--RR,,----rreeqquuiirreess] [----ssccrriippttss] [--ss,,----ssttaattee]
[----ttrriiggggeerrss,,----ttrriiggggeerrssccrriippttss]
vveerriiffyy--ooppttiioonnss
[----nnooddeeppss] [----nnooffiilleess] [----nnoossccrriippttss]
[----nnooddiiggeesstt] [----nnoossiiggnnaattuurree]
[----nnoolliinnkkttoo] [----nnoommdd55] [----nnoossiizzee] [----nnoouusseerr]
[----nnooggrroouupp] [----nnoommttiimmee] [----nnoommooddee] [----nnoorrddeevv]
iinnssttaallll--ooppttiioonnss
[----aaiidd] [----aallllffiilleess] [----bbaaddrreelloocc] [----eexxcclluuddeeppaatthh _O_L_D_P_A_T_H]
[----eexxcclluuddeeddooccss] [----ffoorrccee] [--hh,,----hhaasshh]
[----iiggnnoorreessiizzee] [----iiggnnoorreeaarrcchh] [----iiggnnoorreeooss]
[----iinncclluuddeeddooccss] [----jjuussttddbb] [----nnooddeeppss]
[----nnooddiiggeesstt] [----nnoossiiggnnaattuurree] [----nnoossuuggggeesstt]
[----nnoooorrddeerr] [----nnoossccrriippttss] [----nnoottrriiggggeerrss]
[----oollddppaacckkaaggee] [----ppeerrcceenntt] [----pprreeffiixx _N_E_W_P_A_T_H]
[----rreellooccaattee _O_L_D_P_A_T_H==_N_E_W_P_A_T_H]
[----rreeppaacckkaaggee] [----rreeppllaacceeffiilleess] [----rreeppllaacceeppkkggss]
[----tteesstt]
DDEESSCCRRIIPPTTIIOONN
rrppmm is a powerful PPaacckkaaggee MMaannaaggeerr, which can be used to build, install,
query, verify, update, and erase individual software packages. A ppaacckk--
aaggee consists of an archive of files and meta-data used to install and
erase the archive files. The meta-data includes helper scripts, file
attributes, and descriptive information about the package. PPaacckkaaggeess
come in two varieties: binary packages, used to encapsulate software to
be installed, and source packages, containing the source code and
recipe necessary to produce binary packages.
One of the following basic modes must be selected: QQuueerryy, VVeerriiffyy, SSiigg--
nnaattuurree CChheecckk, IInnssttaallll//UUppggrraaddee//FFrreesshheenn, UUnniinnssttaallll, IInniittiiaalliizzee DDaattaabbaassee,
RReebbuuiilldd DDaattaabbaassee, RReessiiggnn, AAdddd SSiiggnnaattuurree, SSeett OOwwnneerrss//GGrroouuppss, SShhooww QQuueerryy--
ttaaggss, and SShhooww CCoonnffiigguurraattiioonn.
GGEENNEERRAALL OOPPTTIIOONNSS
These options can be used in all the different modes.
--??,, ----hheellpp
Print a longer usage message then normal.
----vveerrssiioonn
Print a single line containing the version number of rrppmm being
used.
----qquuiieett
Print as little as possible - normally only error messages will
be displayed.
--vv Print verbose information - normally routine progress messages
will be displayed.
--vvvv Print lots of ugly debugging information.
----rrccffiillee _F_I_L_E_L_I_S_T
Each of the files in the colon separated _F_I_L_E_L_I_S_T is read
sequentially by rrppmm for configuration information. Only the
first file in the list must exist, and tildes will be expanded
to the value of $$HHOOMMEE. The default _F_I_L_E_L_I_S_T is
_/_u_s_r_/_l_i_b_/_r_p_m_/_r_p_m_r_c:_/_u_s_r_/_l_i_b_/_r_p_m_/_r_e_d_-
_h_a_t_/_r_p_m_r_c:_/_e_t_c_/_r_p_m_r_c:_~_/_._r_p_m_r_c.
----ppiippee _C_M_D
Pipes the output of rrppmm to the command _C_M_D.
----ddbbppaatthh _D_I_R_E_C_T_O_R_Y
Use the database in _D_I_R_E_C_T_O_R_Y rather than the default path
_/_v_a_r_/_l_i_b_/_r_p_m
----rroooott _D_I_R_E_C_T_O_R_Y
Use the file system tree rooted at _D_I_R_E_C_T_O_R_Y for all operations.
Note that this means the database within _D_I_R_E_C_T_O_R_Y will be used
for dependency checks and any scriptlet(s) (e.g. %%ppoosstt if
installing, or %%pprreepp if building, a package) will be run after a
chroot(2) to _D_I_R_E_C_T_O_R_Y.
IINNSSTTAALLLL AANNDD UUPPGGRRAADDEE OOPPTTIIOONNSS
The general form of an rpm install command is
rrppmm {--ii||----iinnssttaallll} [iinnssttaallll--ooppttiioonnss] _P_A_C_K_A_G_E___F_I_L_E _._._.
This installs a new package.
The general form of an rpm upgrade command is
rrppmm {--UU||----uuppggrraaddee} [iinnssttaallll--ooppttiioonnss] _P_A_C_K_A_G_E___F_I_L_E _._._.
This upgrades or installs the package currently installed to a newer
version. This is the same as install, except all other version(s) of
the package are removed after the new package is installed.
rrppmm {--FF||----ffrreesshheenn} [iinnssttaallll--ooppttiioonnss] _P_A_C_K_A_G_E___F_I_L_E _._._.
This will upgrade packages, but only if an earlier version currently
exists. The _P_A_C_K_A_G_E___F_I_L_E may be specified as an ffttpp or hhttttpp URL, in
which case the package will be downloaded before being installed. See
FFTTPP//HHTTTTPP OOPPTTIIOONNSS for information on rrppmm?s internal ffttpp and hhttttpp client
support.
----aaiidd Add suggested packages to the transaction set when needed.
----aallllffiilleess
Installs or upgrades all the missingok files in the package,
regardless if they exist.
----bbaaddrreelloocc
Used with ----rreellooccaattee, permit relocations on all file paths, not
just those _O_L_D_P_A_T_H?s included in the binary package relocation
hint(s).
----eexxcclluuddeeppaatthh _O_L_D_P_A_T_H
Don?t install files whose name begins with _O_L_D_P_A_T_H.
----eexxcclluuddeeddooccss
Don?t install any files which are marked as documentation (which
includes man pages and texinfo documents).
----ffoorrccee
Same as using ----rreeppllaacceeppkkggss, ----rreeppllaacceeffiilleess, and ----oollddppaacckkaaggee.
--hh,, ----hhaasshh
Print 50 hash marks as the package archive is unpacked. Use
with --vv||----vveerrbboossee for a nicer display.
----iiggnnoorreessiizzee
Don?t check mount file systems for sufficient disk space before
installing this package.
----iiggnnoorreeaarrcchh
Allow installation or upgrading even if the architectures of the
binary package and host don?t match.
----iiggnnoorreeooss
Allow installation or upgrading even if the operating systems of
the binary package and host don?t match.
----iinncclluuddeeddooccss
Install documentation files. This is the default behavior.
----jjuussttddbb
Update only the database, not the filesystem.
----nnooddiiggeesstt
Don?t verify package or header digests when reading.
----nnoossiiggnnaattuurree
Don?t verify package or header signatures when reading.
----nnooddeeppss
Don?t do a dependency check before installing or upgrading a
package.
----nnoossuuggggeesstt
Don?t suggest package(s) that provide a missing dependency.
----nnoooorrddeerr
Don?t reorder the packages for an install. The list of packages
would normally be reordered to satisfy dependencies.
----nnoossccrriippttss
----nnoopprree
----nnooppoosstt
----nnoopprreeuunn
----nnooppoossttuunn
Don?t execute the scriptlet of the same name. The ----nnoossccrriippttss
option is equivalent to
----nnoopprree ----nnooppoosstt ----nnoopprreeuunn ----nnooppoossttuunn
and turns off the execution of the corresponding %%pprree, %%ppoosstt,
%%pprreeuunn, and %%ppoossttuunn scriptlet(s).
----nnoottrriiggggeerrss
----nnoottrriiggggeerriinn
----nnoottrriiggggeerruunn
----nnoottrriiggggeerrppoossttuunn
Don?t execute any trigger scriptlet of the named type. The
----nnoottrriiggggeerrss option is equivalent to
----nnoottrriiggggeerriinn ----nnoottrriiggggeerruunn ----nnoottrriiggggeerrppoossttuunn
and turns off execution of the corresponding %%ttrriiggggeerriinn, %%ttrriigg--
ggeerruunn, and %%ttrriiggggeerrppoossttuunn scriptlet(s).
----oollddppaacckkaaggee
Allow an upgrade to replace a newer package with an older one.
----ppeerrcceenntt
Print percentages as files are unpacked from the package
archive. This is intended to make rrppmm easy to run from other
tools.
----pprreeffiixx _N_E_W_P_A_T_H
For relocatable binary packages, translate all file paths that
start with the installation prefix in the package relocation
hint(s) to _N_E_W_P_A_T_H.
----rreellooccaattee _O_L_D_P_A_T_H==_N_E_W_P_A_T_H
For relocatable binary packages, translate all file paths that
start with _O_L_D_P_A_T_H in the package relocation hint(s) to _N_E_W_P_A_T_H.
This option can be used repeatedly if several _O_L_D_P_A_T_H?s in the
package are to be relocated.
----rreeppaacckkaaggee
Re-package the files before erasing. The previously installed
package will be named according to the macro %%__rreeppaacckk--
aaggee__nnaammee__ffmmtt and will be created in the directory named by the
macro %%__rreeppaacckkaaggee__ddiirr (default value is _/_v_a_r_/_s_p_o_o_l_/_r_e_p_a_c_k_a_g_e).
----rreeppllaacceeffiilleess
Install the packages even if they replace files from other,
already installed, packages.
----rreeppllaacceeppkkggss
Install the packages even if some of them are already installed
on this system.
----tteesstt Do not install the package, simply check for and report poten-
tial conflicts.
EERRAASSEE OOPPTTIIOONNSS
The general form of an rpm erase command is
rrppmm {--ee||----eerraassee} [----aallllmmaattcchheess] [----nnooddeeppss] [----nnoossccrriippttss] [----nnoottrriiggggeerrss]
[----rreeppaacckkaaggee] [----tteesstt] _P_A_C_K_A_G_E___N_A_M_E _._._.
The following options may also be used:
----aallllmmaattcchheess
Remove all versions of the package which match _P_A_C_K_A_G_E___N_A_M_E.
Normally an error is issued if _P_A_C_K_A_G_E___N_A_M_E matches multiple
packages.
----nnooddeeppss
Don?t check dependencies before uninstalling the packages.
----nnoossccrriippttss
----nnoopprreeuunn
----nnooppoossttuunn
Don?t execute the scriptlet of the same name. The ----nnoossccrriippttss
option during package erase is equivalent to
----nnoopprreeuunn ----nnooppoossttuunn
and turns off the execution of the corresponding %%pprreeuunn, and
%%ppoossttuunn scriptlet(s).
----nnoottrriiggggeerrss
----nnoottrriiggggeerruunn
----nnoottrriiggggeerrppoossttuunn
Don?t execute any trigger scriptlet of the named type. The
----nnoottrriiggggeerrss option is equivalent to
----nnoottrriiggggeerruunn ----nnoottrriiggggeerrppoossttuunn
and turns off execution of the corresponding %%ttrriiggggeerruunn, and
%%ttrriiggggeerrppoossttuunn scriptlet(s).
----rreeppaacckkaaggee
Re-package the files before erasing. The previously installed
package will be named according to the macro %%__rreeppaacckk--
aaggee__nnaammee__ffmmtt and will be created in the directory named by the
macro %%__rreeppaacckkaaggee__ddiirr (default value is _/_v_a_r_/_s_p_o_o_l_/_r_e_p_a_c_k_a_g_e).
----tteesstt Don?t really uninstall anything, just go through the motions.
Useful in conjunction with the --vvvv option for debugging.
QQUUEERRYY OOPPTTIIOONNSS
The general form of an rpm query command is
rrppmm {--qq||----qquueerryy} [sseelleecctt--ooppttiioonnss] [qquueerryy--ooppttiioonnss]
You may specify the format that package information should be printed
in. To do this, you use the
----qqff||----qquueerryyffoorrmmaatt _Q_U_E_R_Y_F_M_T
option, followed by the _Q_U_E_R_Y_F_M_T format string. Query formats are mod-
ified versions of the standard pprriinnttff((33)) formatting. The format is made
up of static strings (which may include standard C character escapes
for newlines, tabs, and other special characters) and pprriinnttff((33)) type
formatters. As rrppmm already knows the type to print, the type specifier
must be omitted however, and replaced by the name of the header tag to
be printed, enclosed by {{}} characters. Tag names are case insensitive,
and the leading RRPPMMTTAAGG__ portion of the tag name may be omitted as well.
Alternate output formats may be requested by following the tag with
::_t_y_p_e_t_a_g. Currently, the following types are supported:
::aarrmmoorr Wrap a public key in ASCII armor.
::bbaassee6644
Encode binary data using base64.
::ddaattee Use strftime(3) "%c" format.
::ddaayy Use strftime(3) "%a %b %d %Y" format.
::ddeeppffllaaggss
Format dependency flags.
::ffffllaaggss
Format file flags.
::hheexx Format in hexadecimal.
::ooccttaall Format in octal.
::ppeerrmmss Format file permissions.
::sshheessccaappee
Escape single quotes for use in a script.
::ttrriiggggeerrttyyppee
Display trigger suffix.
For example, to print only the names of the packages queried, you could
use %%{{NNAAMMEE}} as the format string. To print the packages name and dis-
tribution information in two columns, you could use %%--3300{{NNAAMMEE}}%%{{DDIISSTTRRII--
BBUUTTIIOONN}}. rrppmm will print a list of all of the tags it knows about when
it is invoked with the ----qquueerryyttaaggss argument.
There are two subsets of options for querying: package selection, and
information selection.
PPAACCKKAAGGEE SSEELLEECCTTIIOONN OOPPTTIIOONNSS::
_P_A_C_K_A_G_E___N_A_M_E
Query installed package named _P_A_C_K_A_G_E___N_A_M_E.
--aa,, ----aallll
Query all installed packages.
--ff,, ----ffiillee _F_I_L_E
Query package owning _F_I_L_E.
----ffiilleeiidd _M_D_5
Query package that contains a given file identifier, i.e. the
_M_D_5 digest of the file contents.
--gg,, ----ggrroouupp _G_R_O_U_P
Query packages with the group of _G_R_O_U_P.
----hhddrriidd _S_H_A_1
Query package that contains a given header identifier, i.e. the
_S_H_A_1 digest of the immutable header region.
--pp,, ----ppaacckkaaggee _P_A_C_K_A_G_E___F_I_L_E
Query an (uninstalled) package _P_A_C_K_A_G_E___F_I_L_E. The _P_A_C_K_A_G_E___F_I_L_E
may be specified as an ffttpp or hhttttpp style URL, in which case the
package header will be downloaded and queried. See FFTTPP//HHTTTTPP
OOPPTTIIOONNSS for information on rrppmm?s internal ffttpp and hhttttpp client
support. The _P_A_C_K_A_G_E___F_I_L_E argument(s), if not a binary package,
will be interpreted as an ASCII package manifest. Comments are
permitted, starting with a ?#?, and each line of a package mani-
fest file may include white space separated glob expressions,
including URL?s with remote glob expressions, that will be
expanded to paths that are substituted in place of the package
manifest as additional _P_A_C_K_A_G_E___F_I_L_E arguments to the query.
----ppkkggiidd _M_D_5
Query package that contains a given package identifier, i.e. the
_M_D_5 digest of the combined header and payload contents.
----qquueerryybbyynnuummbbeerr _H_D_R_N_U_M
Query the _H_D_R_N_U_Mth database entry directly; this is useful only
for debugging.
----ssppeeccffiillee _S_P_E_C_F_I_L_E
Parse and query _S_P_E_C_F_I_L_E as if it were a package. Although not
all the information (e.g. file lists) is available, this type of
query permits rpm to be used to extract information from spec
files without having to write a specfile parser.
----ttiidd _T_I_D
Query package(s) that have a given _T_I_D transaction identifier. A
unix time stamp is currently used as a transaction identifier.
All package(s) installed or erased within a single transaction
have a common identifier.
----ttrriiggggeerreeddbbyy _P_A_C_K_A_G_E___N_A_M_E
Query packages that are triggered by package(s) _P_A_C_K_A_G_E___N_A_M_E.
----wwhhaattpprroovviiddeess _C_A_P_A_B_I_L_I_T_Y
Query all packages that provide the _C_A_P_A_B_I_L_I_T_Y capability.
----wwhhaattrreeqquuiirreess _C_A_P_A_B_I_L_I_T_Y
Query all packages that requires _C_A_P_A_B_I_L_I_T_Y for proper function-
ing.
PPAACCKKAAGGEE QQUUEERRYY OOPPTTIIOONNSS::
----cchhaannggeelloogg
Display change information for the package.
--cc,, ----ccoonnffiiggffiilleess
List only configuration files (implies --ll).
--dd,, ----ddooccffiilleess
List only documentation files (implies --ll).
----dduummpp Dump file information as follows:
path size mtime md5sum mode owner group isconfig isdoc rdev symlink
This option must be used with at least one of --ll, --cc, --dd.
----ffiilleessbbyyppkkgg
List all the files in each selected package.
--ii,, ----iinnffoo
Display package information, including name, version, and
description. This uses the ----qquueerryyffoorrmmaatt if one was specified.
----llaasstt Orders the package listing by install time such that the latest
packages are at the top.
--ll,, ----lliisstt
List files in package.
----pprroovviiddeess
List capabilities this package provides.
--RR,, ----rreeqquuiirreess
List packages on which this package depends.
----ssccrriippttss
List the package specific scriptlet(s) that are used as part of
the installation and uninstallation processes.
--ss,, ----ssttaattee
Display the _s_t_a_t_e_s of files in the package (implies --ll). The
state of each file is one of _n_o_r_m_a_l, _n_o_t _i_n_s_t_a_l_l_e_d, or _r_e_p_l_a_c_e_d.
----ttrriiggggeerrss,, ----ttrriiggggeerrssccrriippttss
Display the trigger scripts, if any, which are contained in the
package.
VVEERRIIFFYY OOPPTTIIOONNSS
The general form of an rpm verify command is
rrppmm {--VV||----vveerriiffyy} [sseelleecctt--ooppttiioonnss] [vveerriiffyy--ooppttiioonnss]
Verifying a package compares information about the installed files in
the package with information about the files taken from the package
metadata stored in the rpm database. Among other things, verifying
compares the size, MD5 sum, permissions, type, owner and group of each
file. Any discrepancies are displayed. Files that were not installed
from the package, for example, documentation files excluded on instal-
lation using the "----eexxcclluuddeeddooccss" option, will be silently ignored.
The package selection options are the same as for package querying
(including package manifest files as arguments). Other options unique
to verify mode are:
----nnooddeeppss
Don?t verify dependencies of packages.
----nnooddiiggeesstt
Don?t verify package or header digests when reading.
----nnooffiilleess
Don?t verify any attributes of package files.
----nnoossccrriippttss
Don?t execute the %%vveerriiffyyssccrriipptt scriptlet (if any).
----nnoossiiggnnaattuurree
Don?t verify package or header signatures when reading.
----nnoolliinnkkttoo
----nnoommdd55
----nnoossiizzee
----nnoouusseerr
----nnooggrroouupp
----nnoommttiimmee
----nnoommooddee
----nnoorrddeevv
Don?t verify the corresponding file attribute.
The format of the output is a string of 8 characters, a possible
attribute marker:
cc %%ccoonnffiigg configuration file.
dd %%ddoocc documentation file.
gg %%gghhoosstt file (i.e. the file contents are not included in the package payload).
ll %%lliicceennssee license file.
rr %%rreeaaddmmee readme file.
from the package header, followed by the file name. Each of the 8
characters denotes the result of a comparison of attribute(s) of the
file to the value of those attribute(s) recorded in the database. A
single ".." (period) means the test passed, while a single "??" (question
mark) indicates the test could not be performed (e.g. file permissions
prevent reading). Otherwise, the (mnemonically emBBoldened) character
denotes failure of the corresponding ----vveerriiffyy test:
SS file SSize differs
MM MMode differs (includes permissions and file type)
55 MD55 sum differs
DD DDevice major/minor number mismatch
LL readLLink(2) path mismatch
UU UUser ownership differs
GG GGroup ownership differs
TT mTTime differs
DDIIGGIITTAALL SSIIGGNNAATTUURREE AANNDD DDIIGGEESSTT VVEERRIIFFIICCAATTIIOONN
The general forms of rpm digital signature commands are
rrppmm ----iimmppoorrtt _P_U_B_K_E_Y _._._.
rrppmm {----cchheecckkssiigg} [----nnoossiiggnnaattuurree] [----nnooddiiggeesstt]
_P_A_C_K_A_G_E___F_I_L_E _._._.
The ----cchheecckkssiigg option checks all the digests and signatures contained
in _P_A_C_K_A_G_E___F_I_L_E to ensure the integrity and origin of the package. Note
that signatures are now verified whenever a package is read, and
----cchheecckkssiigg is useful to verify all of the digests and signatures asso-
ciated with a package.
Digital signatures cannot be verified without a public key. An ASCII
armored public key can be added to the rrppmm database using ----iimmppoorrtt. An
imported public key is carried in a header, and key ring management is
performed exactly like package management. For example, all currently
imported public keys can be displayed by:
rrppmm --qqaa ggppgg--ppuubbkkeeyy**
Details about a specific public key, when imported, can be displayed by
querying. Here?s information about the Red Hat GPG/DSA key:
rrppmm --qqii ggppgg--ppuubbkkeeyy--ddbb4422aa6600ee
Finally, public keys can be erased after importing just like packages.
Here?s how to remove the Red Hat GPG/DSA key
rrppmm --ee ggppgg--ppuubbkkeeyy--ddbb4422aa6600ee
SSIIGGNNIINNGG AA PPAACCKKAAGGEE
rrppmm ----aaddddssiiggnn||----rreessiiggnn _P_A_C_K_A_G_E___F_I_L_E _._._.
Both of the ----aaddddssiiggnn and ----rreessiiggnn options generate and insert new sig-
natures for each package _P_A_C_K_A_G_E___F_I_L_E given, replacing any existing
signatures. There are two options for historical reasons, there is no
difference in behavior currently.
UUSSIINNGG GGPPGG TTOO SSIIGGNN PPAACCKKAAGGEESS
In order to sign packages using GPG, rrppmm must be configured to run GPG
and be able to find a key ring with the appropriate keys. By default,
rrppmm uses the same conventions as GPG to find key rings, namely the
$$GGNNUUPPGGHHOOMMEE environment variable. If your key rings are not located
where GPG expects them to be, you will need to configure the macro
%%__ggppgg__ppaatthh to be the location of the GPG key rings to use.
For compatibility with older versions of GPG, PGP, and rpm, only V3
OpenPGP signature packets should be configured. Either DSA or RSA ver-
ification algorithms can be used, but DSA is preferred.
If you want to be able to sign packages you create yourself, you also
need to create your own public and secret key pair (see the GPG man-
ual). You will also need to configure the rrppmm macros
%%__ssiiggnnaattuurree
The signature type. Right now only gpg and pgp are supported.
%%__ggppgg__nnaammee
The name of the "user" whose key you wish to use to sign your
packages.
For example, to be able to use GPG to sign packages as the user _"_J_o_h_n
_D_o_e _<_j_d_o_e_@...503...f_o_o_._c_o_m_>_" from the key rings located in _/_e_t_c_/_r_p_m_/_._g_p_g using
the executable _/_u_s_r_/_b_i_n_/_g_p_g you would include
%_signature gpg
%_gpg_path /etc/rpm/.gpg
%_gpg_name John Doe <jdoe at ...504...>
%_gpgbin /usr/bin/gpg
in a macro configuration file. Use _/_e_t_c_/_r_p_m_/_m_a_c_r_o_s for per-system con-
figuration and _~_/_._r_p_m_m_a_c_r_o_s for per-user configuration.
RREEBBUUIILLDD DDAATTAABBAASSEE OOPPTTIIOONNSS
The general form of an rpm rebuild database command is
rrppmm {----iinniittddbb||----rreebbuuiillddddbb} [--vv] [----ddbbppaatthh _D_I_R_E_C_T_O_R_Y] [----rroooott _D_I_R_E_C_T_O_R_Y]
Use ----iinniittddbb to create a new database, use ----rreebbuuiillddddbb to rebuild the
database indices from the installed package headers.
SSHHOOWWRRCC
The command
rrppmm ----sshhoowwrrcc
shows the values rrppmm will use for all of the options are currently set
in _r_p_m_r_c and _m_a_c_r_o_s configuration file(s).
FFTTPP//HHTTTTPP OOPPTTIIOONNSS
rrppmm can act as an FTP and/or HTTP client so that packages can be
queried or installed from the internet. Package files for install,
upgrade, and query operations may be specified as an ffttpp or hhttttpp style
URL:
ftp://USER:PASSWORD@...505...:PORT/path/to/package.rpm
If the ::PPAASSSSWWOORRDD portion is omitted, the password will be prompted for
(once per user/hostname pair). If both the user and password are omit-
ted, anonymous ffttpp is used. In all cases, passive (PASV) ffttpp transfers
are performed.
rrppmm allows the following options to be used with ftp URLs:
----ffttpppprrooxxyy _H_O_S_T
The host _H_O_S_T will be used as a proxy server for all ftp trans-
fers, which allows users to ftp through firewall machines which
use proxy systems. This option may also be specified by config-
uring the macro %%__ffttpppprrooxxyy.
----ffttppppoorrtt _P_O_R_T
The TCP _P_O_R_T number to use for the ftp connection on the proxy
ftp server instead of the default port. This option may also be
specified by configuring the macro %%__ffttppppoorrtt.
rrppmm allows the following options to be used with hhttttpp URLs:
----hhttttpppprrooxxyy _H_O_S_T
The host _H_O_S_T will be used as a proxy server for all hhttttpp trans-
fers. This option may also be specified by configuring the macro
%%__hhttttpppprrooxxyy.
----hhttttppppoorrtt _P_O_R_T
The TCP _P_O_R_T number to use for the hhttttpp connection on the proxy
http server instead of the default port. This option may also be
specified by configuring the macro %%__hhttttppppoorrtt.
LLEEGGAACCYY IISSSSUUEESS
EExxeeccuuttiinngg rrppmmbbuuiilldd
The build modes of rpm are now resident in the _/_u_s_r_/_b_i_n_/_r_p_m_b_u_i_l_d exe-
cutable. Although legacy compatibility provided by the popt aliases
below has been adequate, the compatibility is not perfect; hence build
mode compatibility through popt aliases is being removed from rpm.
Install the rrppmmbbuuiilldd package, and see rrppmmbbuuiilldd(8) for documentation of
all the rrppmm build modes previously documented here in rrppmm(8).
Add the following lines to _/_e_t_c_/_p_o_p_t if you wish to continue invoking
rrppmmbbuuiilldd from the rrppmm command line:
rpm exec --bp rpmb -bp
rpm exec --bc rpmb -bc
rpm exec --bi rpmb -bi
rpm exec --bl rpmb -bl
rpm exec --ba rpmb -ba
rpm exec --bb rpmb -bb
rpm exec --bs rpmb -bs
rpm exec --tp rpmb -tp
rpm exec --tc rpmb -tc
rpm exec --ti rpmb -ti
rpm exec --tl rpmb -tl
rpm exec --ta rpmb -ta
rpm exec --tb rpmb -tb
rpm exec --ts rpmb -ts
rpm exec --rebuild rpmb --rebuild
rpm exec --recompile rpmb --recompile
rpm exec --clean rpmb --clean
rpm exec --rmsource rpmb --rmsource
rpm exec --rmspec rpmb --rmspec
rpm exec --target rpmb --target
rpm exec --short-circuit rpmb --short-circuit
FFIILLEESS
rrppmmrrcc CCoonnffiigguurraattiioonn
_/_u_s_r_/_l_i_b_/_r_p_m_/_r_p_m_r_c
_/_u_s_r_/_l_i_b_/_r_p_m_/_r_e_d_h_a_t_/_r_p_m_r_c
_/_e_t_c_/_r_p_m_r_c
_~_/_._r_p_m_r_c
MMaaccrroo CCoonnffiigguurraattiioonn
_/_u_s_r_/_l_i_b_/_r_p_m_/_m_a_c_r_o_s
_/_u_s_r_/_l_i_b_/_r_p_m_/_r_e_d_h_a_t_/_m_a_c_r_o_s
_/_e_t_c_/_r_p_m_/_m_a_c_r_o_s
_~_/_._r_p_m_m_a_c_r_o_s
DDaattaabbaassee
_/_v_a_r_/_l_i_b_/_r_p_m_/_B_a_s_e_n_a_m_e_s
_/_v_a_r_/_l_i_b_/_r_p_m_/_C_o_n_f_l_i_c_t_n_a_m_e
_/_v_a_r_/_l_i_b_/_r_p_m_/_D_i_r_n_a_m_e_s
_/_v_a_r_/_l_i_b_/_r_p_m_/_F_i_l_e_m_d_5_s
_/_v_a_r_/_l_i_b_/_r_p_m_/_G_r_o_u_p
_/_v_a_r_/_l_i_b_/_r_p_m_/_I_n_s_t_a_l_l_t_i_d
_/_v_a_r_/_l_i_b_/_r_p_m_/_N_a_m_e
_/_v_a_r_/_l_i_b_/_r_p_m_/_P_a_c_k_a_g_e_s
_/_v_a_r_/_l_i_b_/_r_p_m_/_P_r_o_v_i_d_e_n_a_m_e
_/_v_a_r_/_l_i_b_/_r_p_m_/_P_r_o_v_i_d_e_v_e_r_s_i_o_n
_/_v_a_r_/_l_i_b_/_r_p_m_/_P_u_b_k_e_y_s
_/_v_a_r_/_l_i_b_/_r_p_m_/_R_e_m_o_v_e_d
_/_v_a_r_/_l_i_b_/_r_p_m_/_R_e_q_u_i_r_e_n_a_m_e
_/_v_a_r_/_l_i_b_/_r_p_m_/_R_e_q_u_i_r_e_v_e_r_s_i_o_n
_/_v_a_r_/_l_i_b_/_r_p_m_/_S_h_a_1_h_e_a_d_e_r
_/_v_a_r_/_l_i_b_/_r_p_m_/_S_i_g_m_d_5
_/_v_a_r_/_l_i_b_/_r_p_m_/_T_r_i_g_g_e_r_n_a_m_e
TTeemmppoorraarryy
_/_v_a_r_/_t_m_p_/_r_p_m_*
SSEEEE AALLSSOO
ppoopptt(3),
rrppmm22ccppiioo(8),
rrppmmbbuuiilldd(8),
hhttttpp::////wwwwww..rrppmm..oorrgg// <<UURRLL::hhttttpp::////wwwwww..rrppmm..oorrgg//>>
AAUUTTHHOORRSS
Marc Ewing <marc at ...34...>
Jeff Johnson <jbj at ...34...>
Erik Troan <ewt at ...34...>
Red Hat, Inc. 09 June 2002 RPM(8)
More information about the User
mailing list