On Tue, 2005-03-22 at 22:35 +0100, Michael van Elst wrote: > On Tue, Mar 22, 2005 at 09:13:42AM -0800, David M. Fetter wrote: > > I'm working on building a new binary repository out of the latest 2.3 > > release, but I'm coming across an issue with openssl. When I do an > > 'openpkg build -A -U' initially I get: > > > > openssl-0.9.7e-2.3.0 UPDATE openssl-0.9.7e-2.3.1 > > If you have 2.3.0 and 2.3.1 then you have the update packages in > your repository. In that case the first installation of openssl > should pick the update (i.e. 2.3.1). > > So what is 'initially' ? How did you install 2.3.0 ?
Initially, is just the first time I run it. Then the second it returns the next results. > > > Then when I execute 'openpkg build -A -U' a second time to make sure > > everything is updated properly, it comes back with: > > > > openssl-0.9.7e-2.3.1 UPDATE openssl-0.9.7e-2.3.0 > > This looks like 2.3.1 is no longer avaible in the repository. They are both there. > > Do you install directly from ftp.openpkg.org ? No, I rsync my own local copy of the src rpms, which then removes about 30 or so of them that we don't want available, then rebuild the src rpm index and run the build command. The local src rpm repository has the base SRC with PLUS and UPD as subdirectories. > > > Greetings, -- David M. Fetter - UNIX Systems Administrator Portland State University - www.oit.pdx.edu
signature.asc
Description: This is a digitally signed message part
