Dear all, many thanks to all who you have reported or contributed, the --force-yes is no longer needed.
Best, Steffen P: Writing hosts P: Writing resolv.conf I: Basic Debian system installed Configuring APT * Creating /etc/apt/sources.list * Install APT recommends by default: false * learning public key for pkg-fso-keyring OK * Updating APT database Get:1 http://ftp2.de.debian.org unstable Release.gpg [189B] Get:2 http://ftp2.de.debian.org experimental Release.gpg [189B] Get:3 http://pkg-fso.alioth.debian.org unstable Release.gpg [189B] Get:4 http://pkg-fso.alioth.debian.org unstable Release [3027B] Get:5 http://ftp2.de.debian.org unstable Release [66.5kB] Get:6 http://ftp2.de.debian.org experimental Release [65.4kB] Get:7 http://pkg-fso.alioth.debian.org unstable/main Packages [18.7kB] Get:8 http://ftp2.de.debian.org unstable/main Packages [7209kB] Get:9 http://ftp2.de.debian.org experimental/main Packages [686kB] Fetched 8050kB in 38s (211kB/s) Reading package lists... Done * Installing pkg-fso keyring Reading package lists... Done Building dependency tree Reading state information... Done The following NEW packages will be installed: pkg-fso-keyring 0 upgraded, 1 newly installed, 0 to remove and 0 not upgraded. Need to get 2800B of archives. After this operation, 49.2kB of additional disk space will be used. Get:1 http://pkg-fso.alioth.debian.org unstable/main pkg-fso-keyring 2008.09.27 [2800B] Joachim Breitner wrote: > Hi, > > 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 >> fingerprint. > > $ GNUPGHOME=/home/groups/pkg-fso/.gnupg gpg --fingerprint --list-keys > gpg: WARNING: unsafe ownership on homedir `/home/groups/pkg-fso/.gnupg' > /home/groups/pkg-fso/.gnupg/pubring.gpg > --------------------------------------- > 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 > <[email protected]> > > 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) > > mQGiBEicYhYRBACvesYUC+rkRpp0j/PTEimmuPkZqjLuRnpXqlCXV9Y1TZxvPmFl > TwoeBHYoh3Uipbj0WypAJ3N989OQPiPo+lyrPNscRYc9+H/k7Q47Oc0ms23EQSWX > AdnuhRezNF98cW/bmykVO9uZo+OjA501R9SCrMkhkbuifB57OMdXA0o67wCg0NWM > EOAqQ/DCoo9Nqnb5sWotwisD/15dgunBY1BCyz8o7Ky1gn+Cel3LfNaqCIHwgCNf > oxdAzHViNHMJa13Hab/nBY1GPpfJ3VIvLNs309JTDoKnYFvUkinvt+OJcY4z/3XN > yloHhUoFBOSuZUy/xqB5PVrlQYJ07WKQHOkjvcp5LCH7pTLjCu8ih+YIIr4uipNl > ZjBwA/9bCGQysO4xaHCR+qEZcQ1J4tW2A1g6Kr8p2CHxvGVCCQW7hhIRVIVGXF83 > EViOVobmG8RHZFpAJzdsrJ/jkYBZp62wCs1DTljxLdMfY9vlKzpui3RSPv10fdPX > t2iPG4Qc9Qm2H6LkWDfSJx6FLzDKrcj8tmbLTpr+fdJZtehudLRNcGtnLWZzbyBB > cmNoaXZlIEF1dG9tYXRpYyBTaWduaW5nIEtleSA8cGtnLWZzby1tYWludEBsaXN0 > cy5hbGlvdGguZGViaWFuLm9yZz6IZgQTEQIAJgUCSJxiFgIbAwUJAeEzgAYLCQgH > AwIEFQIIAwQWAgMBAh4BAheAAAoJEOK53mqOezI7vToAnR+D4n8UEyBKHPc5mqVc > KlzsMB1qAKCNHBbdoCuo/b9ZRdbj0d3zCKGOQA== > =MfK3 > -----END PGP PUBLIC KEY BLOCK----- > __END__ > >>>>> 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 > > Greetings, > Joachim > > > ------------------------------------------------------------------------ > > _______________________________________________ > pkg-fso-maint mailing list > [email protected] > http://lists.alioth.debian.org/mailman/listinfo/pkg-fso-maint _______________________________________________ pkg-fso-maint mailing list [email protected] http://lists.alioth.debian.org/mailman/listinfo/pkg-fso-maint
