#79 closed defect (fixed)
tools/svn2build fails on CentOS 4.4 x86_64
Reported by: | Tadej Janež | Owned by: | Bruno Cornec |
---|---|---|---|
Priority: | normal | Milestone: | 2.2.0 |
Component: | mondo | Version: | 2.0.9 |
Severity: | normal | Keywords: | |
Cc: | andree@… |
Description
I wanted to build mondorescue stable branch from svn today, but it failed with the following messages:
[rpmbuilder@samson mondorescue]$ svn checkout svn://svn.mondorescue.org/mondorescue/branches/stable Checked out revision 866. [rpmbuilder@samson mondorescue]$ stable/tools/svn2build cat: /home/rpmbuilder/mondo/svn/branches/stable/mondo/VERSION: No such file or directory stable/tools/svn2build: line 35: cd: /home/rpmbuilder/mondo/svn: No such file or directory cat: branches/stable/mondo-doc/VERSION: No such file or directory Management of mondo-doc -1 (rev 866) svn: 'branches/stable' is not a working copy stable/tools/svn2build: line 43: mondo-doc-/REVISION: No such file or directory Generating SVN log file ... stable/tools/svn2build: line 45: mondo-doc-/svn.log: No such file or directory Generating build files for mandrake (10.1) Unable to build the RPM specfile for this distro. Please report to authors [rpmbuilder@samson mondorescue]$
I know CentOS 4.4 isn't directly supported, however, it is just a respin of RHEL 4, so I think it should work with RHEL 4 specfiles.
I'm really eager to test new versions of mondorescue leading up to the 2.2.0 release.
Change History (6)
comment:1 by , 17 years ago
Milestone: | → 2.2.0 |
---|---|
Status: | new → assigned |
comment:2 by , 17 years ago
Cc: | added |
---|---|
Resolution: | → fixed |
Status: | assigned → closed |
Should be fixed in rev [872]
Please provide feedback.
Andree if you could also test it for your Debain env, that would be great.
comment:3 by , 17 years ago
Groovy!
Looks like I have to amend the andree's Stuff page because things work now out of the box. ;-)
Cheers, Andree
comment:4 by , 17 years ago
I'm very happy with that feedback ;-)
Now we can continue to work more easily to merge the remaining differences concerning your Debian packages. Would you like to put your specificities under the SVN in each distributions/debian directory in order for us to keep track of that, and prepare an upstream integration post 2.2.0 ?
Bruno.
comment:5 by , 17 years ago
Hi!
I'm very happy with the progress regarding this issue, nice job!
However, I still have problems building packages for testing the latest svn version of mondo.
I checked out the latest svn revision and run 'svn2build mindi mindi-busybox mondo', but it complained that mondo-doc should be built first.
Then I run 'svn2build mondo-doc' but it failed because I don't have the necessary devel packages for some documentation tools. But now I could run 'svn2build mindi mindi-busybox mondo', but this would only build mindi. I had to separately run 'svn2build mindi-busybox' and 'svn2build mondo' to get all three packages in delivery/stable-1 directory:
[rpmbuilder@samson stable-1]$ pwd /home/rpmbuilder/source/delivery/stable-1 [rpmbuilder@samson stable-1]$ ls mindi-busybox-1.2.1.tar.bz2 mindi-stable.tar.bz2 mondo-stable.tar.bz2 mindi-busybox-1.2.1.tar.gz mindi-stable.tar.gz mondo-stable.tar.gz [rpmbuilder@samson stable-1]$
Now, I tried to build the packages with: 'build2pkg' but it failed with:
Working on stable-1 Working under %(echo Using gzip files (redhat) Generating mondo-doc RPMS tar: /home/rpmbuilder/source/mondorescue/stable/./tools/../../../delivery/stable-1/mondo-doc-[1-9st]*.tar.gz: Cannot open: No such file or directory tar: Error is not recoverable: exiting now tar: Child returned status 2 tar: mondo-doc-[1/distributions/redhat-/mondo-doc.spec: Not found in archive tar: Error exit delayed from previous errors mv: cannot stat `mondo-doc-[1/distributions/redhat-/mondo-doc.spec': No such file or directory error: failed to stat /home/rpmbuilder/source/mondorescue/stable/%(echo/SPECS/mondo-doc.spec: No such file or directory No rpmlint found, please install it Using gzip files (redhat) Generating mindi RPMS tar: mindi-stable/distributions/redhat-/mindi.spec: Not found in archive tar: Error exit delayed from previous errors mv: cannot stat `mindi-stable/distributions/redhat-/mindi.spec': No such file or directory error: failed to stat /home/rpmbuilder/source/mondorescue/stable/%(echo/SPECS/mindi.spec: No such file or directory No rpmlint found, please install it Using gzip files (redhat) Generating mindi-busybox RPMS tar: mindi-busybox-1.2.1/distributions/redhat-/mindi-busybox.spec: Not found in archive tar: Error exit delayed from previous errors mv: cannot stat `mindi-busybox-1.2.1/distributions/redhat-/mindi-busybox.spec': No such file or directory error: failed to stat /home/rpmbuilder/source/mondorescue/stable/%(echo/SPECS/mindi-busybox.spec: No such file or directory No rpmlint found, please install it Using gzip files (redhat) Generating mondo RPMS tar: mondo-stable/distributions/redhat-/mondo.spec: Not found in archive tar: Error exit delayed from previous errors mv: cannot stat `mondo-stable/distributions/redhat-/mondo.spec': No such file or directory error: failed to stat /home/rpmbuilder/source/mondorescue/stable/%(echo/SPECS/mondo.spec: No such file or directory No rpmlint found, please install it Packages handled : %(echo/RPMS/noarch/mondo-doc-[1-9st]*-1.rh.noarch.rpm %(echo/RPMS/x86_64/mindi-stable-1.rh.x86_64.rpm %(echo/RPMS/x86_64/mindi-busybox-1.2.1-1.rh.x86_64.rpm %(echo/RPMS/x86_64/mondo-stable-1.rh.x86_64.rpm Installing RPMS as root Password: -bash: -c: line 0: syntax error near unexpected token `(' -bash: -c: line 0: ` rpm -Uvh --force %(echo/RPMS/noarch/mondo-doc-[1-9st]*-1.rh.noarch.rpm %(echo/RPMS/x86_64/mindi-stable-1.rh.x86_64.rpm %(echo/RPMS/x86_64/mindi-busybox-1.2.1-1.rh.x86_64.rpm %(echo/RPMS/x86_64/mondo-stable-1.rh.x86_64.rpm'
I would like to build the packages from stable branch to test the upcoming version of mondo, but I haven't been successful yet.
Should I open a new ticket for dealing with this build2pkg issue post mondo 2.2.0?
Best regards, Tadej
comment:6 by , 17 years ago
Indeed, mondo-doc has always to be built first as it creates files used by the other packages. You should solve your issues with this one first.
I think I've fixed the issues you were seeing in the latest rev [884] So if you still have an issue after 2.2.0 is out (running now), feel free to open a new bug report with same level of details.
I don't think it's a problem with CentOS, but rathre with the environment. Andree has made some feedback on it at AndreesStuff
I'll have a look to remove as much as possible dependencies linked to my environement so that you can also use it.