rust-users — Help, feature requests and annoucements

Re: [Rust-users] rust rpm problem

[Depankar N. <dn...@wi...>]

Michael D. Hirsch wrote:

>On Thursday 24 April 2003 03:09 pm, Depankar Neogi wrote:
>  
>
>>-----Original Message-----
>>From:	Michael D. Hirsch [mailto:mh...@nu...]
>>Sent:	Thu 4/24/2003 2:45 PM
>>To:	Depankar Neogi; rus...@li...
>>Cc:
>>Subject:	Re: [Rust-users] rust rpm problem
>>
>>On Thursday 24 April 2003 02:22 pm, Depankar Neogi wrote:
>>    
>>
>>>Hi -
>>>I am having a weird behavior while trying to create an rpm where for
>>>two files, the sizes are changing. Even if I moved the files to
>>>another dir and created the rpm, still the file size changes in the
>>>rpm. For example -
>>>The original file size is 1450408 for /usr/sbin/dhcpd.
>>>The new file size in the rpm is 623186 for /usr/sbin/dhcpd.
>>>
>>>When I install the rpm, the file size is 623K though the original was
>>>1450K.
>>>
>>>If I manually created the rpm, using rpm -bb -r ...., my flle sizes do
>>>not change and I get the original size.
>>>
>>>I would like to use RUST to build my rpms. This is the first time I
>>>faced such a problem. I have built other rpms and even in this rpm,
>>>the other file sizes are unchanged.
>>>
>>>Any help is appreciated.
>>>      
>>>
>>Two questions.  First, does the new file still work?
>>
>>Second, what is the output of "file /usr/sbin/dhcpd"  on the two
>>versions of the file?
>>
>>I think that rpm (or rust, I'm not sure) may be stripping the file to
>>make it smaller.  There is probably an option in rpm to turn off that
>>behavior.
>>
>>Michael
>>
>>
>>
>>1. The new file does not work.
>>2. Original - file dhcpd
>>dhcpd: ELF 32-bit LSB executable, Intel 80386, version 1, dynamically
>>linked (uses shared libs), not stripped
>>
>># ls -l dhcpd
>>-rwxr-xr-x    1 root     root      1450408 Apr 14 20:25 dhcpd
>>
>>From rpm -
>>$ file dhcpd
>>dhcpd: ELF 32-bit LSB executable, Intel 80386, version 1, dynamically
>>linked (uses shared libs), not stripped $ ls -l dhcpd
>>-rwxr-xr-x    1 root     root       623186 Apr 23 07:39 dhcpd
>>    
>>
>
>That's pretty weird.  I guess my hypothesis was wrong.
>
>Have you looked to see if the file is just being truncated? 
>
>It can't be just the file size--I've used crust (the back-end for rust) for 
>much larger files.
>
>Michael
>  
>
Mike,
I too have used rust to build fairly large rpms. In fact one of my rpm 
is more than 30MB,
and some of the files are much larger.
However, this problem did stump me a bit. I have to look deeper and see 
why this is
happening. I will let you know if I can figure this one out.

thanks,
Depankar

Re: [Rust-users] rust rpm problem

[Michael D. H. <mh...@nu...>]

On Thursday 24 April 2003 03:09 pm, Depankar Neogi wrote:
> -----Original Message-----
> From:	Michael D. Hirsch [mailto:mh...@nu...]
> Sent:	Thu 4/24/2003 2:45 PM
> To:	Depankar Neogi; rus...@li...
> Cc:
> Subject:	Re: [Rust-users] rust rpm problem
>
> On Thursday 24 April 2003 02:22 pm, Depankar Neogi wrote:
> > Hi -
> > I am having a weird behavior while trying to create an rpm where for
> > two files, the sizes are changing. Even if I moved the files to
> > another dir and created the rpm, still the file size changes in the
> > rpm. For example -
> > The original file size is 1450408 for /usr/sbin/dhcpd.
> > The new file size in the rpm is 623186 for /usr/sbin/dhcpd.
> >
> > When I install the rpm, the file size is 623K though the original was
> > 1450K.
> >
> > If I manually created the rpm, using rpm -bb -r ...., my flle sizes do
> > not change and I get the original size.
> >
> > I would like to use RUST to build my rpms. This is the first time I
> > faced such a problem. I have built other rpms and even in this rpm,
> > the other file sizes are unchanged.
> >
> > Any help is appreciated.
>
> Two questions.  First, does the new file still work?
>
> Second, what is the output of "file /usr/sbin/dhcpd"  on the two
> versions of the file?
>
> I think that rpm (or rust, I'm not sure) may be stripping the file to
> make it smaller.  There is probably an option in rpm to turn off that
> behavior.
>
> Michael
>
>
>
> 1. The new file does not work.
> 2. Original - file dhcpd
> dhcpd: ELF 32-bit LSB executable, Intel 80386, version 1, dynamically
> linked (uses shared libs), not stripped
>
> # ls -l dhcpd
> -rwxr-xr-x    1 root     root      1450408 Apr 14 20:25 dhcpd
>
> From rpm -
> $ file dhcpd
> dhcpd: ELF 32-bit LSB executable, Intel 80386, version 1, dynamically
> linked (uses shared libs), not stripped $ ls -l dhcpd
> -rwxr-xr-x    1 root     root       623186 Apr 23 07:39 dhcpd

That's pretty weird.  I guess my hypothesis was wrong.

Have you looked to see if the file is just being truncated? 

It can't be just the file size--I've used crust (the back-end for rust) for 
much larger files.

Michael

RE: [Rust-users] rust rpm problem

[Depankar N. <dn...@wi...>]

-----Original Message-----
From:	Michael D. Hirsch [mailto:mh...@nu...]
Sent:	Thu 4/24/2003 2:45 PM
To:	Depankar Neogi; rus...@li...
Cc:=09
Subject:	Re: [Rust-users] rust rpm problem
On Thursday 24 April 2003 02:22 pm, Depankar Neogi wrote:
> Hi -
> I am having a weird behavior while trying to create an rpm where for =
two
> files, the sizes are changing. Even if I moved the files to another =
dir
> and created the rpm, still the file size changes in the rpm. For =
example
> -
> The original file size is 1450408 for /usr/sbin/dhcpd.
> The new file size in the rpm is 623186 for /usr/sbin/dhcpd.
>
> When I install the rpm, the file size is 623K though the original was
> 1450K.
>
> If I manually created the rpm, using rpm -bb -r ...., my flle sizes do
> not change and I get the original size.
>
> I would like to use RUST to build my rpms. This is the first time I
> faced such a problem. I have built other rpms and even in this rpm, =
the
> other file sizes are unchanged.
>
> Any help is appreciated.

Two questions.  First, does the new file still work?

Second, what is the output of "file /usr/sbin/dhcpd"  on the two =
versions=20
of the file?

I think that rpm (or rust, I'm not sure) may be stripping the file to =
make=20
it smaller.  There is probably an option in rpm to turn off that =
behavior.

Michael



1. The new file does not work.
2. Original - file dhcpd
dhcpd: ELF 32-bit LSB executable, Intel 80386, version 1, dynamically =
linked (uses shared libs), not stripped

# ls -l dhcpd
-rwxr-xr-x    1 root     root      1450408 Apr 14 20:25 dhcpd

From rpm -
$ file dhcpd
dhcpd: ELF 32-bit LSB executable, Intel 80386, version 1, dynamically =
linked (uses shared libs), not stripped
$ ls -l dhcpd
-rwxr-xr-x    1 root     root       623186 Apr 23 07:39 dhcpd

-Depankar

Re: [Rust-users] rust rpm problem

[Michael D. H. <mh...@nu...>]

On Thursday 24 April 2003 02:22 pm, Depankar Neogi wrote:
> Hi -
> I am having a weird behavior while trying to create an rpm where for two
> files, the sizes are changing. Even if I moved the files to another dir
> and created the rpm, still the file size changes in the rpm. For example
> -
> The original file size is 1450408 for /usr/sbin/dhcpd.
> The new file size in the rpm is 623186 for /usr/sbin/dhcpd.
>
> When I install the rpm, the file size is 623K though the original was
> 1450K.
>
> If I manually created the rpm, using rpm -bb -r ...., my flle sizes do
> not change and I get the original size.
>
> I would like to use RUST to build my rpms. This is the first time I
> faced such a problem. I have built other rpms and even in this rpm, the
> other file sizes are unchanged.
>
> Any help is appreciated.

Two questions.  First, does the new file still work?

Second, what is the output of "file /usr/sbin/dhcpd"  on the two versions 
of the file?

I think that rpm (or rust, I'm not sure) may be stripping the file to make 
it smaller.  There is probably an option in rpm to turn off that behavior.

Michael

[Rust-users] rust rpm problem

[Depankar N. <dn...@wi...>]

Hi -
I am having a weird behavior while trying to create an rpm where for two files, the sizes are changing. Even if I moved the files to another dir and created the rpm, still the file size changes in the rpm.
For example -
The original file size is 1450408 for /usr/sbin/dhcpd.
The new file size in the rpm is 623186 for /usr/sbin/dhcpd.

When I install the rpm, the file size is 623K though the original was 1450K.

If I manually created the rpm, using rpm -bb -r ...., my flle sizes do not change and I get the original size.

I would like to use RUST to build my rpms. This is the first time I faced such a problem. I have built other rpms and even in this rpm, the other file sizes are unchanged.

Any help is appreciated.

thanks,
Depankar

Re: [Rust-users] makeRPM.sh problems

[Michael D. H. <mh...@nu...>]

Here are som patches I sent to Pat back in June.  I've been using crust 
with these patches extensively since then with no problems.  

rust.diff was the first addition I made to rust to support the Vendor tag 
in RPM.  I have since added a bunch of additional supported tags like 
Obsoletes.  I don't have the patches made right now but I'll put it on my 
task list.  Although it is named rust.diff I think it is only a patch for 
crust, the rust back-end.

crust.diff and makeRPM.diff will provide you with the ability to have an 
unlimited number of files in your RPM which should fix your problem.  The 
problem was that crust was passing all the filenames on the command line 
to makeRPM.sh.  Since the filenames are already in the spec file, I just 
changed makeRPM.sh to pull them out of the spec file.

Pat, any chance you'll have some time soon for a new release?

Michael



On Monday 10 March 2003 04:40 am, Michiels Olivier wrote:
> Hi,
> I'm trying without success to use crust in order to build some rpms.
> I've followed the documentation but I still have some problems when I'm
> using the --makerpm option. The makeRPM.sh shell script gives an error:
> line 35: [: too many arguments. and no rpms are created.
> What is wrong ? I've installed the last rpm version of rust.
>
> Thanks,
> Michiels Olivier

[Rust-users] makeRPM.sh problems

[Michiels O. <oli...@ub...>]

Hi,
I'm trying without success to use crust in order to build some rpms. I've 
followed the documentation but I still have some problems when I'm using the 
--makerpm option. The makeRPM.sh shell script gives an error: line 35: [: too 
many arguments. and no rpms are created.
What is wrong ? I've installed the last rpm version of rust.

Thanks,
Michiels Olivier
-- 
-------------------------------------------
Michiels Olivier
Senior Development Engineer
GlobalSign
http://www.globalsign.net
-------------------------------------------

Re: [Rust-users] cannot compile on redhat 8.0

[Pat D <pd...@ps...>]

Hello,

On Tue, 2002-12-31 at 10:35, hsu wrote:
> I cannot compile the src rpm on redhat 8.0. At first it cannot find the
> /uar/share/automake folder then after I make a soft link from
> automake-1.6 to automake, it complains it cannot run config.sub, which
> exits under automake.

Yes, RUST is in need of a review and refactoring... I am just now
putting the finishing touches on the latest release of another project
(the VOCP voice messaging system, http://www.VOCPsystem.com) and it's
eating up a lot of my time.

However, my next stop is RUST - I want to add some new functionalities
and fix a few issues, including this one. =20

I shall be making an announcement to the mailing list and on the site
when I get it done.

Thanks for the bug report.

Regards,
--=20
Pat Deegan,
http://www.psychogenic.com/
PGP: http://www.keyserver.net 0x03F86A50

[Rust-users] cannot compile on redhat 8.0

[hsu <hs...@ce...>]

I cannot compile the src rpm on redhat 8.0. At first it cannot find the
/uar/share/automake folder then after I make a soft link from
automake-1.6 to automake, it complains it cannot run config.sub, which
exits under automake.

[Rust-users] Problem with rpm depend version

[Francis S. <fr...@oz...>]

Hi I've just built my first rpm using rust/crust, but when I try to
install it I get 

error: failed dependencies:
	perl-base >= 5.800 is needed by AutoDia-1.2-1.2  
where as it should be >= 5.8.0, how do I solve this.

NB: I used the sandbox method with make install to build this.

Re: [Rust-users] Trying to Build KDE 3.1 RPMs

[Pat D <pd...@ps...>]

Greetings,

Anthony Abby wrote:

>  When I tried to build the RPM however I got the
> following error:  ERROR: Mismatched md5 sum options.  No files added,
> aborting.
>
> Not sure what this is supposed to mean exactly..... can anyone offer any
> help?
>

Yeah.  When you use rust or (the command line rust, 'crust') to 
initialize a 'newroot' you can use to chroot to, you select whether or 
not you wish to use md5sums.

They are used to compare existing binaries - in cases where your install 
may overwrite any files that were copied over to the chroot home. 
Without the md5sum, rust won't be able to tell if a file was overwritten 
- it will therefore only include new files and directories in the rpm.

If you're using the rust GUI, you can select whether to use md5sums 
using the New Root-> Use md5 sum check box.  If you're using crust, then 
there is a --nomd5 switch to turn them off.  The important thing is to 
either use or not use md5sums for both the initialization and the rpm 
creation.

I know that the fact that the default behavior (with or without md5s) 
differ is a little weird but it's basically because I figured you 
wouldn't need the md5s when you're just drag&drop creating an rpm and 
they really slow things down.

Let me know if you have any other questions.

HTH,

--
Pat Deegan,
http://www.psychogenic.com/
"We have found and closed the thing you watch us with."

[Rust-users] Trying to Build KDE 3.1 RPMs

[Anthony A. <ant...@ap...>]

I downloaded Rust yesterday and finally got around to trying to build my
first RPMs this morning.  Ran into an error though.

Specifically I'm trying to build an rpm for arts-1.0.7 for KDE 3.1 on my
Redhat 7.3 system.  When I tried to build the RPM however I got the
following error:  ERROR: Mismatched md5 sum options.  No files added,
aborting.

Not sure what this is supposed to mean exactly..... can anyone offer any
help?

Thx!
Anthony

[Rust-users] makerpm.sh - too many parameters

[<mar...@sb...>]

Hi,

First, this is very cool. I don't have to learn about how to build RPMs. And I thought I was 
going to have to. Phew.

I've got a query - I'm attempting to make an RPM of our samba install. Everything appears to 
work, the RPM contains all the files I expect it to.

Early on in the script ( it's all going past too fast for me to see - I think it's happening when 
we make the SRPM ), makerpm.sh gives an error - too many parameters.

I'm familiar with this error, it's to do with the shell running out of space to hold the results of a 
file glob.

Now the request:

Either - would it be possible to fix this within makerpm.sh ( I'm not convinced it is ).
Or - would someone tell me how to (a) expand the space the shell has available to build the 
file list (b) how I might determine how much space I ought to set aside?

Martin Whinnery
Assistant Network Manager
South Birmingham College

[Rust-users] Rust on Solaris 8

[Gary G. <mr...@ya...>]

Hello
  I'm using Solaris 8, SPARC, with Ximian GNOME. I
sucessfuly compiled the latest version of Rust. Both
the GUI and command line executables work, but I have
one issue. When I issue, crust --chroot
/home/gary/newroot, command nothing happens. It stays
in the same shell, and path.

Does anyone know how to fix this issue?

Thanks,
Gary

=====
--------------
Gary

__________________________________________________
Do You Yahoo!?
Send FREE Valentine eCards with Yahoo! Greetings!
http://greetings.yahoo.com

[Rust-users] Re: Rust Mailing List

[Pat D. <pd...@ps...>]

tba...@cd... wrote:
> 
> Hello,
> 
> I have tried to join the RUST mailing list, however the confirmation reply does not seem to get returned to your administrator.

BLAST!  I've been having problems with the mailing list since the start, will look into it...

> I was wondering if there is any capability in the Rust software to be able to install the RPM in a relitive directory as selected by the USER, ie; Prefix:

Not at this point, however there's been a lot of discussion about just that on
the rpm mailing list recently and I've been thinking about it... shouldn't be very
hard to implement, I'll be looking doing it when I get back home, this weekend.

> Also is there a capability to have the capability to create an icon on 
> installation, such as your rpm for the rust program itself does?

Yes.  It also should be rather easy to automate... of course you can always do it
manually, by creating the file and having it installed in the right place.  Check
the rust-X.X-X/desktop/rust.* files in the source to see how I did it.

HTH,
Pat Deegan.

-- 
For further information, consult your pineal gland.

[Rust-users] Re: Problem, apparently, in generating RPMs with man

[Ben P. <be...@re...>]

* P@ <pa...@ps...> [011015 11:51]:                                      
> >                                                                             
> > i.e.:                                                                       
> >                                                                             
> >     File not found:                                                         
> > /home/benp/rust/var/tmp/util-linux/usr/share/man/man1/write.1               
> >     File not found:                                                         
/home/benp/rust/var/tmp/util-linux/usr/share/man/man5/nfs.5                     
> >     File not found:                                                         
> > /home/benp/rust/var/tmp/util-linux/usr/share/man/man5/fstab.5               
> > Is this a known problem?                                                    
>                                                                               
> Yeah, I've seen this before.  The problem is that rpm is automagically        
> compressing these files (eg turning fstab.5 into fstab.5.gz) - after          
generating                                                                      
> the list of files to include in the RPM.  I can think of 2 solutions:         
>                                                                               
> 1) manually gzip the files before creating the RPM (this will not inhibit them
> from being used as man pages), with something like                            
>       gzip -9 /home/benp/rust/var/tmp/util-linux/usr/share/man/*/*            
>                                                                               
> 2) Find a way to stop rpm compressing the files when creating the RPM. You can
> try this:                                                                     
> As root, edit /usr/local/rust/makeRPM.sh go to line 148 and find:             
>                                                                               
>       echo "%_topdir $TOPDIR" > $RPMMACROS                                    
>       echo "%buildroot %{_topdir}/var/tmp/$PACKNAME" >> $RPMMACROS            
>                                                                               
> Add the line line:                                                            
>       echo "%__os_install_post /usr/lib/rpm/brp-strip" >> $RPMMACROS          
                                                                                
Option number two seems to work like a charm!  Thanks for your help (and        
again for these great tools!                                                    
                                                                                
Ben                                                                             

[Rust-users] Re: Problem, apparently, in generating RPMs with man

[P@ <pa...@ps...>]

Hello!

be...@re... wrote:
> Hello.
> 
> Thanks so much for rust and crust!  It's a very cool package!

Thanks!  With your input, I'll try to keep making it better :)

> 
[snip]

>  Then I run rust and select the sandbox (using md5).
> I fill in the details in 'Package' Preferences field and try to generate
> the RPM.  Everything seems to go just fine, but the process always bombs
> out with problems finding man pages.
>
> i.e.:
> 
>     File not found:
> /home/benp/rust/var/tmp/util-linux/usr/share/man/man1/write.1
>     File not found: /home/benp/rust/var/tmp/util-linux/usr/share/man/man5/nfs.5
>     File not found:
> /home/benp/rust/var/tmp/util-linux/usr/share/man/man5/fstab.5
> Is this a known problem?

Yeah, I've seen this before.  The problem is that rpm is automagically 
compressing these files (eg turning fstab.5 into fstab.5.gz) - after generating
the list of files to include in the RPM.  I can think of 2 solutions:

1) manually gzip the files before creating the RPM (this will not inhibit them
from being used as man pages), with something like
	gzip -9 /home/benp/rust/var/tmp/util-linux/usr/share/man/*/*

2) Find a way to stop rpm compressing the files when creating the RPM. You can
try this:
As root, edit /usr/local/rust/makeRPM.sh go to line 148 and find:

	echo "%_topdir $TOPDIR" > $RPMMACROS
	echo "%buildroot %{_topdir}/var/tmp/$PACKNAME" >> $RPMMACROS

Add the line line:
	echo "%__os_install_post /usr/lib/rpm/brp-strip" >> $RPMMACROS

This /should/ strip the installed programs but not compress the man pages.
I have yet to test this, let me know how it works out if you try it...

HTH
Pat Deegan.


-- 
For further information, consult your pineal gland.

[Rust-users] (no subject)

[Mondesir, R. <rap...@tf...>]

[Rust-users] RUST 0.1.6 Released!

[Pat D. <rus...@ps...>]

I am happy to announce that RUST, wich allows you to create RPM in an
intuitive manner, has been released and was made available through the
www.rusthq.com website hosted at sourceforge.

RUST is both a drag & drop RPM generation GUI, and a "sandboxing"
toolkit that allows you to do software installations within a chrooted
environment, and automatically create RPMs from arbitrary source code,
without ever seeing a spec file. The sandbox is also practical for
testing software installations, or verifying the actions of untrusted
program installations.

You may get a copy from the site at
http://www.rusthq.com/download.html

Enjoy!
Pat Deegan