Re: strange problem compiling source rpms
Faheem Mitha <[EMAIL PROTECTED]> [2002-12-13 21:05:46 +]: > I see. But in that case the error message does seem rather misleading. > Why does it complain about not being able to make directories if it is > not trying to make them? (I haven't examined the internals of rpm). Since it is not a message that anyone working on the code normally ever sees. Therefore there is no itch to scratch and no one has fixed it yet. > I would have thought the only way there might be problems would be if > multiple users were to try to build rpms (as user) in /usr/src/rpm, > and then only if they were trying to build the same package. There > would then be problems with files with different permissions colliding > with each other. Is this correct? Yes, you have it right. But for a user to be able to make files in /usr/src they need to have added themself to the 'src' group. Many do. Many don't. In any case it is one more thing to need to remember. I prefer to work in my home directory. > I recently ran into this problem with kernel building, and I'm now > using /usr/local/src/login-name as a build area for packages (eg > kernel) that I am building myself on a multiuser system. I prefer > this to /home/replay-with-your-login-name-here/src/ Very good! Bob msg19067/pgp0.pgp Description: PGP signature
Re: strange problem compiling source rpms
On Fri, 13 Dec 2002 10:31:18 -0700, Bob Proulx <[EMAIL PROTECTED]> wrote: > > --mP3DRpeJDSE+ciuQ > Content-Type: text/plain; charset=us-ascii > Content-Disposition: inline > > Faheem Mitha <[EMAIL PROTECTED]> [2002-12-12 21:57:35 +]: >> > rpm is trying to mkdir /usr/src/rpm/SOURCES, of course this fails if >> > /usr/src/rpm does not exist. It's dumb code and a bad error message. > > Actually it does not try to make the directories. It just fails if > the directories are not premade. > >> Oh, I see. I thought something like install -d was the conventional >> way to do this. > > Inside of rpm it is a C program and it should make the directories > using C code. The 'install -d' is for makefiles which are shell > scripts. I see. But in that case the error message does seem rather misleading. Why does it complain about not being able to make directories if it is not trying to make them? (I haven't examined the internals of rpm). > If you are building rpms and want to do so in your home directory this > I suggest this. > > File $HOME/.rpmmacros: > %_topdir /home/replay-with-your-login-name-here/src/rpms > > Then make all of the directories it wants in ~/src/rpms/RPMS, etc. and > you can have a private build area. This is they way I build my own > rpms. No collisions with other processes in the shared /usr/src > area. I would have thought the only way there might be problems would be if multiple users were to try to build rpms (as user) in /usr/src/rpm, and then only if they were trying to build the same package. There would then be problems with files with different permissions colliding with each other. Is this correct? I recently ran into this problem with kernel building, and I'm now using /usr/local/src/login-name as a build area for packages (eg kernel) that I am building myself on a multiuser system. I prefer this to /home/replay-with-your-login-name-here/src/ Faheem. -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
Re: strange problem compiling source rpms
Faheem Mitha <[EMAIL PROTECTED]> [2002-12-12 21:57:35 +]: > > rpm is trying to mkdir /usr/src/rpm/SOURCES, of course this fails if > > /usr/src/rpm does not exist. It's dumb code and a bad error message. Actually it does not try to make the directories. It just fails if the directories are not premade. > Oh, I see. I thought something like install -d was the conventional > way to do this. Inside of rpm it is a C program and it should make the directories using C code. The 'install -d' is for makefiles which are shell scripts. If you are building rpms and want to do so in your home directory this I suggest this. File $HOME/.rpmmacros: %_topdir /home/replay-with-your-login-name-here/src/rpms Then make all of the directories it wants in ~/src/rpms/RPMS, etc. and you can have a private build area. This is they way I build my own rpms. No collisions with other processes in the shared /usr/src area. Bob msg18957/pgp0.pgp Description: PGP signature
Re: strange problem compiling source rpms
On Thu, 12 Dec 2002 14:37:58 -0500, Joey Hess <[EMAIL PROTECTED]> wrote: > Faheem Mitha wrote: >> No. Am I supposed to create it? Isn't this something that should be >> done automatically, by a postinst script of whatever? If I am supposed >> to create it, I think it should be documented. > > The directory is supposed to be included in the package but was left out > by mistake. I'm fixinig it now. Great, thanks. >> > Does the user running rpm have >> > permission to create it? (I suspect not to both) >> Um. Yes. It is root. (See the #?) Actually, even my user account >> (faheem) has permission to create directories in /usr/src. I've >> compiled kernels there as user. This is what is so puzzling about this >> error message. > > rpm is trying to mkdir /usr/src/rpm/SOURCES, of course this fails if > /usr/src/rpm does not exist. It's dumb code and a bad error message. Oh, I see. I thought something like install -d was the conventional way to do this. Faheem. -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
Re: strange problem compiling source rpms
Faheem Mitha wrote: > No. Am I supposed to create it? Isn't this something that should be > done automatically, by a postinst script of whatever? If I am supposed > to create it, I think it should be documented. The directory is supposed to be included in the package but was left out by mistake. I'm fixinig it now. > > Does the user running rpm have > > permission to create it? (I suspect not to both) > > Um. Yes. It is root. (See the #?) Actually, even my user account > (faheem) has permission to create directories in /usr/src. I've > compiled kernels there as user. This is what is so puzzling about this > error message. rpm is trying to mkdir /usr/src/rpm/SOURCES, of course this fails if /usr/src/rpm does not exist. It's dumb code and a bad error message. -- see shy jo msg18735/pgp0.pgp Description: PGP signature
Re: strange problem compiling source rpms
On Thu, 12 Dec 2002 00:10:46 -0500, Derrick 'dman' Hudson <[EMAIL PROTECTED]> wrote: > --hQiwHBbRI9kgIhsi > Content-Type: text/plain; charset=us-ascii > Content-Disposition: inline > Content-Transfer-Encoding: quoted-printable > > On Thu, Dec 12, 2002 at 03:37:37AM +, Faheem Mitha wrote: >| On Wed, 11 Dec 2002 15:53:27 -0800 (PST), nate <[EMAIL PROTECTED]= >> wrote: >| > Faheem Mitha said: > >| > after it's compiled it usually dumps a binary rpm somewhere in >| > /usr/src/rpms. >|=20 >| Yes, this is what should happen in theory. However, this does not work >| either, at least on the new computer. I get similar errors, ie.=20 >|=20 >| laplace:/home/faheem# rpm --rebuild plugger-4.0-17.src.rpm >| Installing plugger-4.0-17.src.rpm >| error: cannot create %sourcedir /usr/src/rpm/SOURCES > ^ > Back when I used redhat that was where it would unpack a source rpm > to. Does that directory exist? No. Am I supposed to create it? Isn't this something that should be done automatically, by a postinst script of whatever? If I am supposed to create it, I think it should be documented. > Does the user running rpm have > permission to create it? (I suspect not to both) Um. Yes. It is root. (See the #?) Actually, even my user account (faheem) has permission to create directories in /usr/src. I've compiled kernels there as user. This is what is so puzzling about this error message. Am I missing something here? In any case, I submitted a bug report to Joey Hess. If I am doing something wrong, he will presumably tell me. Note, I've tried this on another machine with the same result. Faheem. -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
Re: strange problem compiling source rpms
On Thu, Dec 12, 2002 at 03:37:37AM +, Faheem Mitha wrote: | On Wed, 11 Dec 2002 15:53:27 -0800 (PST), nate <[EMAIL PROTECTED]> wrote: | > Faheem Mitha said: | > after it's compiled it usually dumps a binary rpm somewhere in | > /usr/src/rpms. | | Yes, this is what should happen in theory. However, this does not work | either, at least on the new computer. I get similar errors, ie. | | laplace:/home/faheem# rpm --rebuild plugger-4.0-17.src.rpm | Installing plugger-4.0-17.src.rpm | error: cannot create %sourcedir /usr/src/rpm/SOURCES ^ Back when I used redhat that was where it would unpack a source rpm to. Does that directory exist? Does the user running rpm have permission to create it? (I suspect not to both) -D -- Micros~1 : For when quality, reliability and security just aren't that important! http://dman.ddts.net/~dman/ msg18588/pgp0.pgp Description: PGP signature
Re: strange problem compiling source rpms
On Wed, 11 Dec 2002 15:53:27 -0800 (PST), nate <[EMAIL PROTECTED]> wrote: > Faheem Mitha said: >> Dear People, > >> In case anyone is wondering, I am trying to install the src rpm in order >> to compile it, an operation I had earlier successfully done on my home >> computer. > > > I am no RPM expert but anytime I wanted to compile a source rpm I did > > rpm --rebuild filename.src.rpm > > its worked well for almost every package, is this not the right > way ? Yes, but before it can compile, it has to first install the source rpm. > after it's compiled it usually dumps a binary rpm somewhere in > /usr/src/rpms. Yes, this is what should happen in theory. However, this does not work either, at least on the new computer. I get similar errors, ie. laplace:/home/faheem# rpm --rebuild plugger-4.0-17.src.rpm Installing plugger-4.0-17.src.rpm error: cannot create %sourcedir /usr/src/rpm/SOURCES error: plugger-4.0-17.src.rpm cannot be installed It works fine on my home computer. I'll try this on another computer and see if I can reproduce this behaviour. Faheem. -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
Re: strange problem compiling source rpms
Faheem Mitha said: > Dear People, > In case anyone is wondering, I am trying to install the src rpm in order > to compile it, an operation I had earlier successfully done on my home > computer. I am no RPM expert but anytime I wanted to compile a source rpm I did rpm --rebuild filename.src.rpm its worked well for almost every package, is this not the right way ? after it's compiled it usually dumps a binary rpm somewhere in /usr/src/rpms. nate -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
strange problem compiling source rpms
Dear People, I recently tried to install a source rpm (as root) on a Debian system. I got laplace:/home/faheem# rpm -Uvh plugger-4.0-17.src.rpm error: cannot create %sourcedir /usr/src/rpm/SOURCES But this works on my home computer Chrestomanci:/home/faheem# rpm -Uvh plugger-4.0-6.src.rpm 1:plugger ### [100%] Ok, so they are not exactly the same version, but very similar. Can anyone explain what is going on? I'll been pulling my hair for a while trying to figure out why root cannot create /usr/src/rpm/SOURCES etc. Both laplace and my home computer Chrestomanci are supposedly tracking sarge, and have the exact same version of rpm. I see that I have the entire /usr/src/rpm directory hierachy installed on my system, and I am perfectly sure I did not create it myself. However, the rpm Debian package installation script does not seem to install it either, so it is a mystery how it got there. Did rpm simply create it as it needed it? In case anyone is wondering, I am trying to install the src rpm in order to compile it, an operation I had earlier successfully done on my home computer. Faheem. -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
Re: Source rpms
First install package rpm (by apt, dpkg, dselect, deity, whatever) Then rpm -bp just as if you were running RootHat. In fact, Debian's RPM is simply RootHat's with a few cosmetic changes. On Sat, 12 May 2001, Stephen J. Thompson wrote: >-BEGIN PGP SIGNED MESSAGE- >Hash: RIPEMD160 > >Hello all, > >Is there a way to extract source rpm's on a debian box? > >If so please could you state how? > >Thanks. > >Regards, > >Stephen. >-BEGIN PGP SIGNATURE- >Version: GnuPG v1.0.5 (GNU/Linux) >Comment: For info see http://www.gnupg.org > >iQIXAwUBOv0r/7qZwrUTrKD5FAPsIQgAhD0B0tdWi6cdStYXAH2QSlUNK1NG4fBm >lfQjjvjyfFsSjYgEWSOKRGoErB53viVTVyQm0T5YbhX3dGCKDVRVCk2kJ2G+iBW0 >Jw+RpmANuZ06sXkSZWCtVqJSnkEl2d5X8C2ysYYia9wGAvDFs6faEeSe+ypewoi+ >r+jb/EJslEiyz1tl0ZbgdD2L05XDpXv4+TR5q5z2H6nYGSeCoHUOZShR7r/4P/nM >WpKLxKvqkdbWiWs0rBvLy7UMKN6oA3xwTaXWIG6oRZMsp1+9BphI/2NhC4PPiTxG >taYh05kvEImUHD0v2RlAihpUoYpv2ZuzlS7kqkSmsoxcKl7BX4o/vggAks3n8iz/ >Fy/kRNQ9/cRdPPUx0p3WtDklQZhrBa+1iDe2BB8btZNfkjdHyMEqfMBQX7lmFizh >EypwGVJNNvkE0LQcOFFUrSddiSWnAu/6Oj/iipLZMMREXiJZmQSbpId+CY9I/KvL >8tJVweLrFsPam3YIz446uJKwy5KvvY8sdvk/8g3+JLZRoKw+TecI/C1kDxHATtVY >kZytoLVyaR9Iu4xevZRl00V//J9xNxDSRbtrDgSptsj1AX4LOgHfVpC1TKK9hS8h >QubXMNhXpUV29NEBb6RAxZcK8qOMCDcfvm9WED4dv0T+q8h8yEWYOg9IGLBzrKwm >oyhH1JGkaJeghw== >=vW/h >-END PGP SIGNATURE- > > > -- Customer: "I'm running Windows '98" Tech: "Yes." Customer: "My computer isn't working now." Tech: "Yes, you said that." Who is John Galt? [EMAIL PROTECTED], that's who!
Re: Source rpms
Hallo Stephen, * Stephen schrieb: > Hello all, > > Is there a way to extract source rpm's on a debian box? > > If so please could you state how? apt-get install rpm cpio rpm2cpio package.src.rpm| cpio --list rpm2cpio package.src.rpm| cpio --extract filename cya Waldemar -- It's naive to assume that just installing a firewall is going to protect you from all potential security threat. That assumption creates a false sense of security, and having a false sense of security is worse than having no security at all. -- Kevin Mitnick
Source rpms
-BEGIN PGP SIGNED MESSAGE- Hash: RIPEMD160 Hello all, Is there a way to extract source rpm's on a debian box? If so please could you state how? Thanks. Regards, Stephen. -BEGIN PGP SIGNATURE- Version: GnuPG v1.0.5 (GNU/Linux) Comment: For info see http://www.gnupg.org iQIXAwUBOv0r/7qZwrUTrKD5FAPsIQgAhD0B0tdWi6cdStYXAH2QSlUNK1NG4fBm lfQjjvjyfFsSjYgEWSOKRGoErB53viVTVyQm0T5YbhX3dGCKDVRVCk2kJ2G+iBW0 Jw+RpmANuZ06sXkSZWCtVqJSnkEl2d5X8C2ysYYia9wGAvDFs6faEeSe+ypewoi+ r+jb/EJslEiyz1tl0ZbgdD2L05XDpXv4+TR5q5z2H6nYGSeCoHUOZShR7r/4P/nM WpKLxKvqkdbWiWs0rBvLy7UMKN6oA3xwTaXWIG6oRZMsp1+9BphI/2NhC4PPiTxG taYh05kvEImUHD0v2RlAihpUoYpv2ZuzlS7kqkSmsoxcKl7BX4o/vggAks3n8iz/ Fy/kRNQ9/cRdPPUx0p3WtDklQZhrBa+1iDe2BB8btZNfkjdHyMEqfMBQX7lmFizh EypwGVJNNvkE0LQcOFFUrSddiSWnAu/6Oj/iipLZMMREXiJZmQSbpId+CY9I/KvL 8tJVweLrFsPam3YIz446uJKwy5KvvY8sdvk/8g3+JLZRoKw+TecI/C1kDxHATtVY kZytoLVyaR9Iu4xevZRl00V//J9xNxDSRbtrDgSptsj1AX4LOgHfVpC1TKK9hS8h QubXMNhXpUV29NEBb6RAxZcK8qOMCDcfvm9WED4dv0T+q8h8yEWYOg9IGLBzrKwm oyhH1JGkaJeghw== =vW/h -END PGP SIGNATURE-
