Opened 14 years ago
Closed 14 years ago
#87 closed defect (fixed)
pbsrc content should be put in SOURCES directory when building RPMs
Reported by: | Nicolas Doualot | Owned by: | Bruno Cornec |
---|---|---|---|
Priority: | major | Milestone: | 0.11.1 |
Component: | pb | Version: | 0.10.1 |
Keywords: | Cc: |
Description
Right now, the pbsrc content is in the SPECS folder
rpmbuild fails to found those referenced files:
error: Bad file: /home/ndo/lighttpd/build/SOURCES/logo-hpintel.jpg.all: No such file or directory error: Bad file: /home/ndo/lighttpd/build/SOURCES/lighttpd.sh.rhel: No such file or directory error: Bad file: /home/ndo/lighttpd/build/SOURCES/lighttpd.run.rhel: No such file or directory error: Bad file: /home/ndo/lighttpd/build/SOURCES/lighttpd.conf.all: No such file or directory error: Bad file: /home/ndo/lighttpd/build/SOURCES/index.html.tmpl.all: No such file or directory RPM build errors: Bad file: /home/ndo/lighttpd/build/SOURCES/logo-hpintel.jpg.all: No such file or directory Bad file: /home/ndo/lighttpd/build/SOURCES/lighttpd.sh.rhel: No such file or directory Bad file: /home/ndo/lighttpd/build/SOURCES/lighttpd.run.rhel: No such file or directory Bad file: /home/ndo/lighttpd/build/SOURCES/lighttpd.conf.all: No such file or directory Bad file: /home/ndo/lighttpd/build/SOURCES/index.html.tmpl.all: No such file or directory
Change History (6)
follow-up: 2 comment:1 by , 14 years ago
Milestone: | → 0.10.2 |
---|---|
Status: | new → assigned |
follow-up: 3 comment:2 by , 14 years ago
Replying to bruno:
In fact when using pbsrc, the spec file is modified to generate Source1, Source2, ... entries in order to point to these additional sources.
This works fine after the r1218 commit, but thinks doesn't work well for the source rpm.
What pb could do automatically, is move at build time all the files found under the pbsrc dir under pbconf to SOURCES for rpm build. Wold that be ok for you ?
This what I meant with this bug report.
I don't know if it is a task for ProjectBuilder or for the packager to put the files under SOURCES for the src.rpm creation.
Remains to see what to do for other types of build...
comment:3 by , 14 years ago
Replying to ndoualot:
Replying to bruno:
What pb could do automatically, is move at build time all the files found under the pbsrc dir under pbconf to SOURCES for rpm build. Wold that be ok for you ?
This what I meant with this bug report.
Ok, we're on the same page then :-)
I don't know if it is a task for ProjectBuilder or for the packager to put the files under SOURCES for the src.rpm creation.
Well, as pb does the .spec modification, it seems important to me that it also put the sources at the right place, which is not difficult as it know where they are and where to put them. Will work on a patch for that.
Remains to see what to do for other types of build...
Still true.
comment:4 by , 14 years ago
- Fixed in rev [1219]. This requires to update pb in the VM|RM|VE in order to work correctly (with setupvm|rm|ve).
As you have the correct infra in place, please test it and report again your findings.
comment:6 by , 14 years ago
Resolution: | → fixed |
---|---|
Status: | assigned → closed |
In fact when using pbsrc, the spec file is modified to generate Source1, Source2, ... entries in order to point to these additional sources.
What pb could do automatically, is move at build time all the files found under the pbsrc dir under pbconf to SOURCES for rpm build. Wold that be ok for you ?
Remains to see what to do for other types of build...