Hi,
This is on hppa, base-config 1.04 (built myself), debconf 0.9.64.
I'm doing an unstable install, and /root/dbootstrap_settings ends up
containing SUITE='sid' as expected. base-config was trying to use
stable, so I editted 00dbootstrap_settings to run with -x rather than
-e to see what was
On Tue, Jun 12, 2001 at 09:04:10PM +0100, Richard Hirst wrote:
This is on hppa, base-config 1.04 (built myself), debconf 0.9.64.
I'm doing an unstable install, and /root/dbootstrap_settings ends up
containing SUITE='sid' as expected. base-config was trying to use
stable, so I editted
I guess the correct solution is to make dbootstrap write unstable
instead of sid, but I don't know how to handle slink and potato.
Suggestions?
Here is an idea:
slink and sid will never change, their proper names are just that, slink and
sid. Once woody is released someone installing potato
On Tue, Jun 12, 2001 at 02:30:36PM -0600, Matt Kraai wrote:
On Tue, Jun 12, 2001 at 09:04:10PM +0100, Richard Hirst wrote:
This is on hppa, base-config 1.04 (built myself), debconf 0.9.64.
I'm doing an unstable install, and /root/dbootstrap_settings ends up
containing SUITE='sid' as
Matt Kraai wrote:
Argh. This is my fault. When I added support for preserving the
suite information, I didn't think to update the different
possibilities for apt-get/distribution. As a temporary
workaround, you can manually edit /target/root/dbootstrap_settings
to set SUITE to unstable
David Whedon wrote:
slink and sid will never change, their proper names are just that, slink and
sid.
I would argue that their proper names are 2.1 and unstable.
Once woody is released someone installing potato will also want that name
to not change, it will just stay 'potato'.
Or 2.2
If
This will certianly work, but I still don't understand why that code is
so fond of the release names, when with a simple change to debootstrap, it
The code is fond of release names because :
1 - that's what debootstrap wanted
2 - that is a common way of talking about releases, which is
David Whedon wrote:
I don't have strong feelings, and in fact I had to bend over backwards to make
the volatile stable, testing names work in a somewhat sane way. So do we want de
bootstrap to accept 2.1/2.3/2.3 as well as slink/potato/woody ? Perhaps 3 symli
nks in
8 matches
Mail list logo
