OK, I guessed on the .version file, and it appears I guessed wrong.
First, I looked at that tag in the trunk:
PWD = ~/dev/openafs/trunk]
pmo...@renegade$ git describe --abbrev=4 HEAD
BP--openafs-stable-1_6_x-174-g50920
Just for giggles, I tried this:
echo openafs-devel-1_5_77 > .version
and then I was able to at least build the srpm. However, when rebuilding
the srpm to get binary rpms:
+ /usr/bin/bzip2 -dc /var/tmp/rpm-root/SOURCES/openafs-UNKNOWN-doc.tar.bz2
+ tar -xf -
tar: Read 6144 bytes from -
+ STATUS=0
+ '[' 0 -ne 0 ']'
+ cd openafs-UNKNOWN
/var/tmp/rpm-tmp.73321: line 51: cd: openafs-UNKNOWN: No such file or
directory
error: Bad exit status from /var/tmp/rpm-tmp.73321 (%prep)
Working backwards, I see where the UNKNOWN comes from. When building the
srpm (which builds without errors):
efs...@madefsd01$ ./makesrpm.pl ../../../../openafs-1.5.77-src.tar.bz2
../../../../openafs-1.5.77-doc.tar.bz2
Building version UNKNOWN
So, I don't think my .version hack worked. What should have been the
contents of that file for the openefs-1.5.77-src.tar.* files that were
published? I guessed wrong... :-(
On Thu, Oct 7, 2010 at 2:15 PM, Derrick Brashear <[email protected]> wrote:
> On Thu, Oct 7, 2010 at 1:57 PM, Phillip Moore <[email protected]>
> wrote:
> > Where does this .version file belong, and what should the contents be?
> > I thought that if I just went ahead and ran makesrpm.pl, it would be
> > obvious, but it's not. After installing all the prerequisite rpms, I get
> > the following:
> > WARNING: No release notes provided. Using empty file
> > WARNING: No changelog provided. Using empty file
> > /bin/ls: /lib/modules/*/build/include/linux/version.h: No such file or
> > directory
> > unable to determine kernel version
> > sh: line 0: [: =: unary operator expected
> > /bin/ls: /lib/modules/*/build/include/linux/version.h: No such file or
> > directory
>
> you need to install the kernel-devel rpm for your kernel.
>
> > unable to determine kernel version
> > Now, this may very well be related to the missing .version, if I can find
> > out where that shell snippet is, but I'm not sure yet.
>
> it's not related.
>
> you need a file ".version" in the top level srcdir, same directory as
> e.g. configure.ac
> it should look like output from
> git describe --abbrev=4 HEAD
>
> e.g.
> openafs-devel-1_5_77
> at a tag point.
>
> > On Thu, Oct 7, 2010 at 1:15 PM, Andy Cobaugh <[email protected]> wrote:
> >>
> >> On 2010-10-07 at 13:07, Derrick Brashear ( [email protected] ) said:
> >>>
> >>> On Thu, Oct 7, 2010 at 1:05 PM, Phillip Moore <
> [email protected]>
> >>> wrote:
> >>>>
> >>>> I managed to automate setting up a multi-cell environment for testing
> >>>> purposes, but I'm using the binary RPMs for 1.4.12 which are available
> >>>> on
> >>>> openafs.org. There are numerous features in 1.5.* that want to use,
> so
> >>>> now
> >>>> I'm looking to rebuild all of this with 1.5.77, for which of course no
> >>>> binary rpms have been published yet.
> >>>> I figured that those aren't being put together entirely by hand, so I
> >>>> tried
> >>>> to find out how that are built. This documentation:
> >>>> http://wiki.openafs.org/AFSLore/HowToBuildOpenAFSFromSource/
> >>>> seems out of date, since it discusses cvs instead of git. It also
> only
> >>>> discusses creating a source rpm, and I'm looking to build the same set
> >>>> of
> >>>> binary rpms that are available for 1.4.12.
> >>>> Can anyone give me some more pointers on how the 1.4.12 rpms were put
> >>>> together?
> >>>
> >>> there's a makesrpm perl file we ship in src/packaging/RedHat. it takes
> >>> a few arguments, which include the src and doc tarballs for the
> >>> version you want, and will spit out an srpm. you then
> >>> rpmbuild -ba it. not much fuss.
> >>
> >> Should be noted that the current src tarball for 1.5.77 is missing the
> >> .version file. Should be obvious after looking at makesrpm.pl how this
> is
> >> used. We just extracted the src tarball, created the missing .version
> file,
> >> then tar'd it back up.
> >>
> >> On a related note: Will there be RPMs provided for 1.5.78 when it's
> >> released? Many of us that are wanting to help test 1.5 and get
> experience
> >> with it don't always have the time to build RPMs ourselves. Even SRPMs
> would
> >> be helpful.
> >>
> >> --andy
> >
>
>
>
> --
> Derrick
>
