[pkg-fso-maint] Probleme mit debian on freerunner install.sh
nomeata at debian.org
Fri Feb 27 17:48:38 UTC 2009
Am Freitag, den 27.02.2009, 18:29 +0100 schrieb Steffen Moeller:
> Joachim Breitner wrote:
> > Hi,
> > Am Freitag, den 27.02.2009, 14:40 +0100 schrieb Steffen Moeller:
> >> Joachim Breitner wrote:
> >> [...]
> >>> He first changed every occurance of --yes with --yes --force-yes, and
> >>> changed every occurance of that back to --yes (configurable with a
> >>> variable). This included this change:
> >>> - chroot $INST_DIR apt-get --yes --force-yes install pkg-fso-keyring
> >>> + chroot $INST_DIR apt-get $APT_OPTIONS install pkg-fso-keyring
> >>> but in this case, the --force-yes was there originally and for a reason.
> >> Right. And I am sorry for this.
> >> When we have that pkg-fso-keyring package signed by a Debian developer, the --force-yes
> >> could go, right?
> > No, you can’t sign individual packages, only repositories. I don’t think
> > that pkg-fso-keyring would be admitted to the main repository.
> > A cleaner solution would be to include the pkg-fso key (or it’s
> > fingerprint) in install.sh and feed it to apt-key before installing from
> > the pkg-fso repository.
> This sounds nice to me. Please be so kind to send me a signed email of yours of the key's
$ GNUPGHOME=/home/groups/pkg-fso/.gnupg gpg --fingerprint --list-keys
gpg: WARNING: unsafe ownership on homedir `/home/groups/pkg-fso/.gnupg'
pub 1024D/8E7B323B 2008-08-08 [expires: 2009-08-08]
Key fingerprint = 4C7A 4D93 9815 5A06 7FEA DA7D E2B9 DE6A 8E7B 323B
uid pkg-fso Archive Automatic Signing Key <pkg-fso-maint at lists.alioth.debian.org>
but if you want to add the key to install.sh, then instead of trying to
download it and check the fingerprint, use this snippet:
sudo apt-key add - <<__END__
-----BEGIN PGP PUBLIC KEY BLOCK-----
Version: GnuPG v1.4.6 (GNU/Linux)
-----END PGP PUBLIC KEY BLOCK-----
> >>> There were a few changes to the installer recently, and it seems they
> >>> were not completely tested. Not sure about the mount problem though,
> >>> without an error log.
> >> There was no run from scratch, which would have been good, but is somewhat tough because
> >> of the long run time....and since the /mnt/debian is not removed after the install, I
> >> would not have spotted that one.
> > So is there a bug now left in the script?
> I am not sure. I personally like it the way it is, but it would possibly be cleaner to
> remove INST_DIR if it has not been existing before. I'll add that.
But the installation works from scratch, without a /mnt/debian? Marcel,
did you re-install with a manually added /mnt/debian, or did it work the
second time even without an existing /mnt/debian
Joachim "nomeata" Breitner
nomeata at debian.org | ICQ# 74513189 | GPG-Keyid: 4743206C
JID: nomeata at joachim-breitner.de | http://people.debian.org/~nomeata
-------------- next part --------------
A non-text attachment was scrubbed...
Name: not available
Size: 197 bytes
Desc: Dies ist ein digital signierter Nachrichtenteil
Url : http://lists.alioth.debian.org/pipermail/pkg-fso-maint/attachments/20090227/5a5e6b6f/attachment-0001.pgp
More information about the pkg-fso-maint