Found the source RPM now what?

Monex · March 2, 2009, 8:33pm

Hi,

it is not necessary to install the source RPM. Just download it to a directory and then use unrpm to extract the contents as described here. To build the RPM I suggest to use suses build tool.

Hope this helps

mtmigs · March 5, 2009, 11:43am

The information I have received so far have been very helpful. Thank you and the others for all the help.

I have used the rpmbuild and have succeeded in building a new version with my added patch file. I makes the appropriate change to the atd program.

There is one more problem with the rpm I created. When it installs it creates two directories with permissions I need to change.

I found two places where these directories are specified. The Makefile has an entry in its “install” section that specifies the permissions. Then the at.spec file itself has these directories specified.

Well I added a section to my patch file to change the permissions in the “install” section of the Makefile. That did nothing.

Then I found the section in the at.spec file that also listed those two directories as needing to be created. I changed the permissions there also. That also did nothing.

These are the only two places I have found. I even looked in the programs of the at package to make sure they do not change it. They do not. In fact after installing the package I can manually change the permissions and they will remain changed.

Is there somewhere else used by the rpm install the specifies the required directories and their permissions?

malcolmlewis · March 5, 2009, 2:57pm

mtmigs:

Monex;1951723 Wrote:
> Hi,
>
> it is not necessary to install the source RPM. Just download it to a
> directory and then use unrpm to extract the contents as described
> ‘here’ (http://tinyurl.com/br4oxw). To build the RPM I suggest to use
> suses build tool.
>
> Hope this helps

The information I have received so far have been very helpful. Thank
you and the others for all the help.

I have used the rpmbuild and have succeeded in building a new version
with my added patch file. I makes the appropriate change to the atd
program.

There is one more problem with the rpm I created. When it installs it
creates two directories with permissions I need to change.

I found two places where these directories are specified. The Makefile
has an entry in its “install” section that specifies the permissions.
Then the at.spec file itself has these directories specified.

Well I added a section to my patch file to change the permissions in
the “install” section of the Makefile. That did nothing.

Then I found the section in the at.spec file that also listed those two
directories as needing to be created. I changed the permissions there
also. That also did nothing.

These are the only two places I have found. I even looked in the
programs of the at package to make sure they do not change it. They do
not. In fact after installing the package I can manually change the
permissions and they will remain changed.

Is there somewhere else used by the rpm install the specifies the
required directories and their permissions?

Hi
Use a chmod command at the end in the %install section and set the
%attr in the %files section.

–
Cheers Malcolm °¿° (Linux Counter #276890)
SUSE2.6.27.15-2-default
up 1 day 13:34, 1 user, load average: 0.24, 0.35, 0.28
GPU GeForce 6600 TE/6200 TE - Driver Version: 180.35

mtmigs · March 5, 2009, 7:16pm

I did set the %attr in the %files section but that did not seem to do anything. That was the second of the two locations I tried.

I tried putting the chmod at the end in the %install. That caused an error in the rpmbuild. So that does not work either. It seems that the %install is run during the rpmbuild, not when the package is actually installed (go figure) and at that point the directory does not exist. It is only later during the actual rpm install that the directory is created.

I would have thought changing the %attr in the %files section would have been the solution but it just seems to ignore it.

Any other ideas?