Travis, you said that it's a bad idea to pin to testing, especially
at this stage in the release. Other than testing being bad in
general (think: security updates), what's the problem here? If
I want testing, then I also want etch as soon as sarge is released.
Thus, I don't see how this is bad.
Am
also sprach Travis Crump <[EMAIL PROTECTED]> [2004.08.27.2213 +0200]:
> If testing is pinned to 500 and foo has a 'current pin' of
> 100[since foo's installed version is no longer in any archive it
> just has the 'default' installed pin], new version>old version and
> 500>100 so it gets upgraded. W
martin f krafft wrote:
folks,
i am too tired tonight to set up a testing environment for this.
plus, it's friday. so maybe someone Just Knows(tm).
if stable is pinned at 900 and testing at 500, and i manually pull
in foo from testing and then a new version of foo hits testing, what
happens?
what ab
On Fri, 27 Aug 2004 21:20:32 +0200
martin f krafft <[EMAIL PROTECTED]> wrote:
>folks,
>
>i am too tired tonight to set up a testing environment for this.
>plus, it's friday. so maybe someone Just Knows(tm).
>
>if stable is pinned at 900 and testing at 500, and i manually pull
>in foo from testing
folks,
i am too tired tonight to set up a testing environment for this.
plus, it's friday. so maybe someone Just Knows(tm).
if stable is pinned at 900 and testing at 500, and i manually pull
in foo from testing and then a new version of foo hits testing, what
happens?
what about when testing is
5 matches
Mail list logo
