[Rpm-maint] Moving packages between environments using rpm

devzero2000 pinto.elia at gmail.com
Sun Aug 31 21:45:12 UTC 2008

Sorry for the long time passed  for the reply.

If you look at my reply  i had written about rpmrebuild (
http://rpmrebuild.sourceforge.net/) <http://rpmrebuild.sourceforge.net/%29>
not rpmbuild.


On Fri, Aug 22, 2008 at 2:57 AM, Tom Szczesny <tavmem at gmail.com> wrote:

> Either I was not clear in the problem statement  ... or I don't understand
> the solution that you recommend.
> I have reviewed the documentation on the rpmbuild command.  It appears that
> I need to apply the rpmbuild command to a SPECFILE or a TARBALL or a
> SOURCEPKG.   I have none of these.
> To restate the problem another way:  I have a binary package
> 'foo-version-x' that has already been installed on a machine-1 some time ago
> (automatically by the Fedora Package Manger).  To my knowlege, the actual
> rpm package for 'foo-version-x' was not saved anywhere (unless it is in the
> rpm database on machine-1).  Binary 'foo-version-x' is no longer available
> for automatic installation from the Fedora Package Manager.  I have binary
> 'foo-version-y' that has been installed on machine-2 at some later date
> (also automatically using the Fedora Package Manager).   'foo-version-y' may
> still be available (or maybe only 'foo-version-z' is now available).
> I wish to uninstall 'foo-version-y' from machine-2 and install the earlier
> 'foo-version-x' on machine-2.
> If rpmbuild can be used to extract the binary 'foo-version-x' from
> machine-1 in such a form that it can be installed on machine-2, what is the
> command syntax that I would use on machine-1 to perform this extract?  As
> far as I know, I do not have a SPECFILE, TARBALL or SOURCEPKG for
> 'foo-version-x' on machine 1 (unless it is stored somewhere in the rpm
> database).
> On Sat, Aug 16, 2008 at 1:10 PM, devzero2000 <pinto.elia at gmail.com> wrote:
>> On Sat, Aug 16, 2008 at 12:51 PM, Tom Szczesny <tavmem at gmail.com> wrote:
>>> I am having a problem with the aplus-fsf package in Fedora.  The package
>>> was working in 4 environments (F8/x86_64, F7/x86_64, F8/i686 and
>>> F7/i686.  aplus-fsf began having problems in 3 environments (F7/x86_64,
>>> F8/i686 and F7/i686) but continued to work in F8/x86_64.  No changes had
>>> been made to the aplus-fsf package in any of the environments, but several
>>> other packages had been updated.  (As an aside, updates to the
>>> NetworkManager package had been received but had failed to install
>>> in F8/x86_64 where aplus-fsf is still working.)
>>> I created new partitions and did fresh installs of F9/x86_64 and
>>> F9/i686:  aplus-fsf did not work in either one.   I created a new partition
>>> and did a fresh install of F8/x86_64:  aplus-fsf does not work there.  I now
>>> have two F8/x86_64 environments on the same machine, one in which aplus-fsf
>>> works, and one in which it does not.
>>> I have identified 17 packages that have different versions in the two
>>> environments.  I would like to take the package versions from the working
>>> environment and install them in the problem environment.
>>> Is there some RPM command that will extract a package from the rpm data
>>> base in the working environment to a file that can be transferred to the
>>> problem environment as a replacement?  I wish to do this package by package
>>> to check if there is a package/version that is affecting aplus-fsf.
>>> I am not sure to have undestood your problem, but rpmrebuild do exactly
>> what you have asked, it rebuild the source/binary rpm from
>> the rpmdb infos. From this you can extract the files with rpmcpio.
>> hth
>>> _______________________________________________
>>> Rpm-maint mailing list
>>> Rpm-maint at lists.rpm.org
>>> https://lists.rpm.org/mailman/listinfo/rpm-maint
> _______________________________________________
> Rpm-maint mailing list
> Rpm-maint at lists.rpm.org
> https://lists.rpm.org/mailman/listinfo/rpm-maint
-------------- next part --------------
An HTML attachment was scrubbed...
URL: http://lists.rpm.org/pipermail/rpm-maint/attachments/20080831/760bbf58/attachment-0001.htm 

More information about the Rpm-maint mailing list