Luigi Gangitano dijo [Tue, Apr 25, 2006 at 02:14:46PM +0200]:
>
> Il giorno 25/apr/06, alle ore 07:12, Norbert Tretkowski ha scritto:
> >>squid 3.0 is not yet 'stable'. Squid 2.5 is still the stable series.
> >
> >Why not just uploading squid 3.0 to experimental?
>
> Because it's not a short term
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
Il giorno 26/apr/06, alle ore 15:25, Joerg Jaspert ha scritto:
experimental is autobuild, thats no reason to not use it.
And you dont break the existing squid package in unstable/testing with
an upload to exp.
I think I wasn't clear when I explain
Il giorno 26/apr/06, alle ore 12:35, Eduard Bloch ha scritto:
How would that interact with running squid installations? Please
tell us
what the actuall constraints are instead of repeating "needs to stay
here, needs to stay there". I assume you want to:
- make a package name more clear to sh
On Wed, 26 Apr 2006, Robert Collins wrote:
> Wearing my upstream hat, I'd like to see squid3 packages that *do not*
> conflict or replace squid packages in a release.
>
> Squid3 has many features that are simply not available to squid 2.5, and
> I think parallel installs are really quite reasonabl
On 10636 March 1977, Luigi Gangitano wrote:
>> Upload to experimental, not as new source.
> Why not?
Just from what i read in the thread...
> Since I'd like to make squid3 easily available to all those that want
> to try the new features, without braking the existing squid package,
> unstable is
On Wed, 2006-04-26 at 12:42 +0200, Wouter Verhelst wrote:
> On Wed, Apr 26, 2006 at 11:13:32AM +0200, Luigi Gangitano wrote:
> > Squid 3 is not release ready. And with current plans should not
> > release with etch. So squid 2.5 needs to stay in unstable/testing at
> > least until etch is relea
#include
* Luigi Gangitano [Wed, Apr 26 2006, 12:21:52PM]:
> >>Squid 3 is not release ready. And with current plans should not
> >>release
> >>with etch.
> >
> >Upload to experimental, not as new source.
>
> Why not? Since I'd like to make squid3 easily available to all those
> that want to
On Wed, Apr 26, 2006 at 11:13:32AM +0200, Luigi Gangitano wrote:
> Squid 3 is not release ready. And with current plans should not
> release with etch. So squid 2.5 needs to stay in unstable/testing at
> least until etch is released and can be installed on production
> machines.
Well, then t
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
Hi Joerg,
Il giorno 26/apr/06, alle ore 12:06, Joerg Jaspert ha scritto:
On 10636 March 1977, Luigi Gangitano wrote:
I don't think people will install unstable on production
machines, so
don't see how that would be a problem.
Squid 3 is not relea
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
Il giorno 26/apr/06, alle ore 11:13, Christian Perrier ha scritto:
I don't think people will install unstable on production machines, so
don't see how that would be a problem.
Unstable, maybe not. Testing, well, I can bet a few beers (preferrably
On 10636 March 1977, Luigi Gangitano wrote:
>> I don't think people will install unstable on production machines, so
>> don't see how that would be a problem.
> Squid 3 is not release ready. And with current plans should not release
> with etch.
Upload to experimental, not as new source.
--
bye
> You're about to upload a separate squid3 package (to unstable) because
> you think people should continue to use squid 2.5 on production
> machines.
>
> I don't think people will install unstable on production machines, so
> don't see how that would be a problem.
Unstable, maybe not. Testing,
Il giorno 26/apr/06, alle ore 08:06, Wouter Verhelst ha scritto:
Would you really install unstable on your production machine?
No, and this is exactly my point.
Then I'm afraid I don't get your point.
You're about to upload a separate squid3 package (to unstable) because
you think people sh
On Wed, Apr 26, 2006 at 03:21:59AM +0200, Luigi Gangitano wrote:
> Il giorno 25/apr/06, alle ore 15:26, Wouter Verhelst ha scritto:
> >On Tue, Apr 25, 2006 at 02:19:12PM +0200, Luigi Gangitano wrote:
> >>Whould you really use your production machine to test some
> >>experimental software?
> >
> >Wo
Il giorno 25/apr/06, alle ore 15:26, Wouter Verhelst ha scritto:
On Tue, Apr 25, 2006 at 02:19:12PM +0200, Luigi Gangitano wrote:
Whould you really use your production machine to test some
experimental software?
Would you really install unstable on your production machine?
No, and this is ex
On Tue, Apr 25, 2006 at 02:19:12PM +0200, Luigi Gangitano wrote:
> Whould you really use your production machine to test some
> experimental software?
Would you really install unstable on your production machine?
--
Fun will now commence
-- Seven Of Nine, "Ashes to Ashes", stardate 53679.4
On Tue, Apr 25, 2006 at 02:14:46PM +0200, Luigi Gangitano wrote:
> Because it's not a short term package. It will be there for at least
> 6 months.
Just as a reference; Samba 4 is in exactly the same situation, and it is
handled in experimental.
/* Steinar */
--
Homepage: http://www.sesse.net/
Il giorno 25/apr/06, alle ore 07:12, Norbert Tretkowski ha scritto:
squid 3.0 is not yet 'stable'. Squid 2.5 is still the stable series.
Why not just uploading squid 3.0 to experimental?
Because it's not a short term package. It will be there for at least
6 months.
And experimental is no
Luigi Gangitano wrote on 25/04/2006 14:19:
>
> Il giorno 25/apr/06, alle ore 13:57, Sven Mueller ha scritto:
>>>Luigi Gangitano wrote on 25/04/2006 01:32:
>>>
So I'm packaging Squid-3.0 from new sources (using CDBS for the first
time, great!). The resulting packages will be named 'squid3,
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
Il giorno 25/apr/06, alle ore 13:57, Sven Mueller ha scritto:
Luigi Gangitano wrote on 25/04/2006 01:32:
So I'm packaging Squid-3.0 from new sources (using CDBS for the first
time, great!). The resulting packages will be named 'squid3, squid3-
com
Luigi Gangitano wrote on 25/04/2006 01:32:
> So I'm packaging Squid-3.0 from new sources (using CDBS for the first
> time, great!). The resulting packages will be named 'squid3, squid3-
> common, squid3-client, squid3-cgi' and will conflict with the
> existing squid packages.
Why do you conf
This one time, at band camp, Luigi Gangitano said:
>
> Il giorno 24/apr/06, alle ore 21:54, Stephen Gran ha scritto:
> >> This is the new development version, totally rewritten in C++
> >> with the
> >> latest features like ICAP added.
> >
> > Is a new source package really needed? Is there n
* Robert Collins wrote:
> On Mon, 2006-04-24 at 20:54 +0100, Stephen Gran wrote:
> > Is a new source package really needed? Is there no sensible
> > upgrade path? I had sort of hoped it could be as drop in and go as
> > most upgrades are, but perhaps not.
>
> Squid-3 will read the same config file
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
Il giorno 24/apr/06, alle ore 21:54, Stephen Gran ha scritto:
This is the new development version, totally rewritten in C++
with the
latest features like ICAP added.
Is a new source package really needed? Is there no sensible upgrade
path? I
This one time, at band camp, Robert Collins said:
> On Mon, 2006-04-24 at 20:54 +0100, Stephen Gran wrote:
> > This one time, at band camp, Luigi Gangitano said:
> > > * Package name: squid3
> > >
> > > This is the new development version, totally rewritten in C++ with the
> > > latest featu
On Mon, 2006-04-24 at 20:54 +0100, Stephen Gran wrote:
> This one time, at band camp, Luigi Gangitano said:
> > * Package name: squid3
> >
> > This is the Squid Internet Object Cache developed by the National
> > Laboratory for Applied Networking Research (NLANR) and Internet
> > volunteers
This one time, at band camp, Luigi Gangitano said:
> * Package name: squid3
>
> This is the Squid Internet Object Cache developed by the National
> Laboratory for Applied Networking Research (NLANR) and Internet
> volunteers. This software is freely available for anyone to use.
>
> This
Package: wnpp
Severity: wishlist
Owner: Luigi Gangitano <[EMAIL PROTECTED]>
* Package name: squid3
Version : 3.0-PRE3.20060422
Upstream Author : Henrik Nordstrom <[EMAIL PROTECTED]>
* URL : http://www.squid-cache.org
* License : GPL
Programming Lang: C++
Des
28 matches
Mail list logo
