Newbie question.... Sources is strange {Solved}

[MBantz]

Suddenly I get errors that there is no Source1 (if there are multiple sources (10+)), and if I rearrange so there is a source1 it complains it's not a tar file (and it is a textfile as it has always been)

Is it me or the transform to newer rpm system?

EDIT: Getting my negatives right

[Neal ManBear]

djohnston,
MBantz is one of our packagers.

MBantz,
Can you post the relevant section of your spec file, please?

[djohnston]

Whoah. My apologies. I should have checked what section this is in. I'll remove the post. Thanks, Neal.

[Neal ManBear]

Whoah. My apologies. I should have checked what section this is in. I'll remove the post. Thanks, Neal.

  It happens to all of us at times.

[MBantz]

Whoah. My apologies. I should have checked what section this is in. I'll remove the post. Thanks, Neal.

What was it about, now I'm curious :-)

Neal, I'll post the section when I'm back from work later today,

cheers,
MBantz

[Neal ManBear]

What was it about, now I'm curious :-)

djohnston hadn't noticed that this thread is in Packagers. He thought you were asking beginning user questions, rather than packager questions.

Neal, I'll post the section when I'm back from work later today,

cheers,
MBantz

Okay. I hope it is an excellent day!

[MBantz]

I got it now,

the code was:

Code: [Select]

Source0:   mythtv-%{version}.tar.xz
Source100: PACKAGE-LICENSING
Source101: mythbackend.sysconfig.in
Source102: mythbackend.init.in
Source103: mythbackend.logrotate.in
Source106: mythfrontend.png
Source107: mythfrontend.desktop
Source108: mythtv-setup.png
Source109: mythtv-setup.desktop
Source110: mysql.txt
Source402: PCLinux-build_myth-0.25.sh
Source404: movemyth
Source405: createdb
Source406: setwakeup
Source407: showlogs
Source408: checklogin
Source409: mythtv-setup
Source410: dialog_functions.sh
Source411: mythwelcome-wrap.sh

but this works:

Code: [Select]

Source0:   mythtv-%{version}.tar.xz
Source1: PACKAGE-LICENSING
Source101: mythbackend.sysconfig.in
Source102: mythbackend.init.in
Source103: mythbackend.logrotate.in

but I still wonder why it insists on having Source0 and Source1 as required fields and not only Source0....

well, sorted now, building mythtv 0.25 now :-)

cheers,
MBantz

[MBantz]

no, it does not:

Code: [Select]

Executing(%prep): /bin/sh -e /home/mbz/src/tmp/rpm-tmp.73598
+ umask 022
+ cd /home/mbz/src/rpm/BUILD
+ '[' 1 -eq 1 ']'
+ '[' 1 -eq 1 ']'
+ '[' 1 -eq 1 ']'
+ cd /home/mbz/src/rpm/BUILD
+ /bin/mkdir -p mythtv-0.25
+ cd mythtv-0.25
+ tar -xf /home/mbz/src/rpm/SOURCES/mythtv-0.25.tar.xz
+ tar -xf /home/mbz/src/rpm/SOURCES/PACKAGE-LICENSING
tar: This does not look like a tar archive
tar: Skipping to next header
tar: Exiting with failure status due to previous errors
error: Bad exit status from /home/mbz/src/tmp/rpm-tmp.73598 (%prep)


RPM build errors:
    Bad exit status from /home/mbz/src/tmp/rpm-tmp.73598 (%prep)



[gseaman]

Why so many source files and not one tar zipped file?

Galen

[Neal ManBear]

Try making the source numbers sequential -
Source0
Source1
Source2
and so on.

Jumping from Source1 to Source101 may be the problem.

[gseaman]

+ tar -xf /home/mbz/src/rpm/SOURCES/PACKAGE-LICENSING
tar: This does not look like a tar archive
tar: Skipping to next header
tar: Exiting with failure status due to previous errors
error: Bad exit status from /home/mbz/src/tmp/rpm-tmp.73598 (%prep)

This may be failing because it is expecting the source to be zipped.

Galen

[Neal ManBear]

As Galen says, create tar.xz archives of your sources and see if that does it.

[MBantz]

Before I take any measures, I just wonder why this has changed - and what the new syntax/style eventually is.

It has always been possible to refer to these files as %{SOURCE101} and so on - this spec (over 1000 lines long) then need heavy modifications.

I just wonder if it is an error I have made, or this is due to the transition to the updated RPM system?

[gseaman]

My suggestion is just a guess from the error message. It seems there is a lot of trial and error to find what works. I have only built one package since the rpm change and it seemed to work just fine, but it only have one zipped source file, so I don't know.

You can find out very quickly, just by zipping just the next file, and checking to see if the build fails at the same step, or continues and fails on the next file. If it fails on the same spot, then zipping the files will not likely be the solution.

Galen

[Neal ManBear]

I think it is due to the upgrade to the newer RPM. There seems to be some changes, like using rpmbuild -ba instead of rpm -ba. Any road, we may need to learn some new ways of doing things.