Hello, I did a first round of mass recompiling of Packman packages for PowerPC. As I needed to modify sources heavily in a number of cases, these files are not (yet) integrated with the rest of the Packman website. All packages were built on SUSE Linux 10.1 factory as of the RC2 state. Y2pmbuild was used for building packages, so all my mistakes are reproducible :-) I have yet to implement secure installation sources ( http://en.opensuse.org/Secure_Installation_Sources ), so at the moment, you need to download packages you want to install and use plain old rpm. Ooops, I almost forgot it, the files are available at ftp://spike.fa.gau.hu/pub/pmppc101rc2/ Please let me know, if you have any problems with these packages! Bug me first, and not the original packager, as the problem might be PPC specific, and due to the fact, that I use y2pmbuild for everything instead of PackMan specific build scripts... Bye, CzP
On Friday 28 April 2006 3:26 am, Peter Czanik wrote:
Hello, I did a first round of mass recompiling of Packman packages for PowerPC. As I needed to modify sources heavily in a number of cases, these files are not (yet) integrated with the rest of the Packman website. All packages were built on SUSE Linux 10.1 factory as of the RC2 state. Y2pmbuild was used for building packages, so all my mistakes are reproducible :-) I have yet to implement secure installation sources ( http://en.opensuse.org/Secure_Installation_Sources ), so at the moment, you need to download packages you want to install and use plain old rpm. Ooops, I almost forgot it, the files are available at ftp://spike.fa.gau.hu/pub/pmppc101rc2/ Please let me know, if you have any problems with these packages! Bug me first, and not the original packager, as the problem might be PPC specific, and due to the fact, that I use y2pmbuild for everything instead of PackMan specific build scripts... Bye, CzP
THANK YOU!!!! Was that loud enough? Could you here me over there? Very much appreciated. Thank you, thank you, thank you, Stan
On Sat, Apr 29, 2006 at 03:42:34PM +0200, Duncan Mac-Vicar wrote:
On Friday 28 April 2006 10:26, Peter Czanik wrote:
I have yet to implement secure installation sources (
Feel free to contact me for any questions regarding that.
Perhaps this is also concerning the makeSUSEdvd problems with RC3. Already posted to the factory list. Transfered to bug 166011 There I see some info: <quote> - (once) create a GPG key for signing the modified source (or use an existing key) - adapt the packages file with "=Cks: SHA1 <sha1sum>" entries of the RPMs - add META and KEY entries to /content, see URL above - sign /content (gpg --detach-sign -a content) - create /content.key (the above public key used to sign /content) (gpg --export -a -u keyid > content.key) </quote> Is there anybody that can explain to me in babysteps on how to do that? I have never used gpg. So I suppose I do the following: `gpg --gen-key`, 5, 2048, 0, y, name and email, passphrase (Or must this be blank?), generate the key. I then have my key. Now what? houghi -- Nutze die Zeit. Sie ist das Kostbarste, was wir haben, denn es ist unwiederbringliche Lebenszeit. Leben ist aber mehr als Werk und Arbeit, und das Sein wichtiger als das Tun - Johannes Müller-Elmau
On Saturday 29 April 2006 16:20, houghi wrote:
Is there anybody that can explain to me in babysteps on how to do that? I have never used gpg. So I suppose I do the following: `gpg --gen-key`, 5, 2048, 0, y, name and email, passphrase (Or must this be blank?), generate the key. I then have my key.
you can use just gpg --gen-key or in KDE open kgpg and go to the Keys menu and select Generate Key Pair. and it will ask you all the required parameters like type of encryption, email, etc and the passprhase to protect the private key (dont forget that one) The key par will be stored by default in a keyring in ~/.gnupg , you can add more keys there too. content.key is an ASCII armored export of your public key. You can export it with the command line mentioned above, or again, use kgpg to export it from your key ring. content.asc is the detached signature produced by signing content with your private key. This can be done with the command line above, or kgpg: - Go to Configure Kpg -> Misc -> Applet & Menus - Enable Sign file service menu. - Now you can sign content file right clicking it in Konqueror. Cheers -- Duncan Mac-Vicar Prett SUSE LINUX Products GmbH, Maxfeldstr. 5, 90409 Nuernberg Tel: +49-911-74053-437 - duncan.mac-vicar@suse.de
Hello, Duncan Mac-Vicar írta:
On Friday 28 April 2006 10:26, Peter Czanik wrote:
I have yet to implement secure installation sources (
Feel free to contact me for any questions regarding that.
I read http://en.opensuse.org/Secure_Installation_Sources and with the latest factory it works now correctly. I have one more problem left: is there any way to avoid the warning messages about the untrusted key? Bye, CzP
On Fri, May 05, 2006 at 05:26:05PM +0200, Peter Czanik wrote:
Hello,
Duncan Mac-Vicar írta:
On Friday 28 April 2006 10:26, Peter Czanik wrote:
I have yet to implement secure installation sources (
Feel free to contact me for any questions regarding that.
I read http://en.opensuse.org/Secure_Installation_Sources and with the latest factory it works now correctly. I have one more problem left: is there any way to avoid the warning messages about the untrusted key? Bye, CzP
No. However it should be gone forever after the initial import. (?) Ciao, Marcus
participants (6)
-
Duncan Mac-Vicar -
Duncan Mac-Vicar Prett
-
houghi -
Marcus Meissner -
Peter Czanik -
S Glasoe