Hi Ha
On Fri, 10 Jun 2011 07:24:38 +0200, Harald Dunkel ha...@afaics.de wrote:
...
It's kind of like asking for walls separate from your house.
Its more like keeping the basement stable, while building new
walls on top of it.
Yes, it's exactly like that -- and you're just like the sort
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
On 06/07/11 00:59, Russ Allbery wrote:
Harald Dunkel ha...@afaics.de writes:
Not exactly. I would like to get a stable build and runtime environment
for the packages in main/testing.
Yes, that's what I'm saying doesn't actually exist. There
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
On 06/10/11 07:24, Harald Dunkel wrote:
I do not see that. All packages were available at build time in
the right version. Where should this broken dependency come from,
unless you are ignoring dependencies on promoting packages from
unstable to
On Sun, 05 Jun 2011 at 08:29:03 +0200, Harald Dunkel wrote:
All these APIs and dynamic libraries are meant to provide backward
compatibility.
You're asking for forward compatibility, though: making applications in
testing/main limit themselves to only doing things which already worked in
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
On 06/06/11 07:06, Russ Allbery wrote:
I still think this whole conversation is based on a false premise. I
think the original request originated from a belief that there is some
separable part of core Debian which could be held stable, and that
Harald Dunkel ha...@afaics.de writes:
On 06/06/11 07:06, Russ Allbery wrote:
I still think this whole conversation is based on a false premise. I
think the original request originated from a belief that there is some
separable part of core Debian which could be held stable, and that
keeping
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
Hi Neil,
On 06/04/11 19:01, Neil Williams wrote:
Testing compatibility is the larger problem. Automated tests can only
go so far. Dependencies are one thing, bugs which arise because one
setup is using a version which has already been replaced
On Sun, 2011-06-05 at 08:29 +0200, Harald Dunkel wrote:
Hi Neil,
On 06/04/11 19:01, Neil Williams wrote:
Testing compatibility is the larger problem. Automated tests can only
go so far. Dependencies are one thing, bugs which arise because one
setup is using a version which has already
On Sat, Jun 04, 2011 at 05:07:26PM +0200, Harald Dunkel wrote:
About the package set dependencies: The core package sets would be
self contained, i.e. they would not depend upon packages outside of
their own core set. The new main/testing repository would be meant
to work with both
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
On 06/05/11 13:17, Tshepang Lekhonkhobe wrote:
On Sun, 2011-06-05 at 08:29 +0200, Harald Dunkel wrote:
Understood. If you reduce the number of packages to be released by
focusing on a core package set with 1000 or 1500 packages instead
of +3,
* Harald Dunkel ha...@afaics.de [110605 18:02]:
Only core/stable should be released. The rest comes from
main/testing.
I cannot speak for others, but I don't wait 3 years. I do
regular updates/upgrades to include the most recent security
and bug fixes. We've scheduled regular maintenance
On Sun, 05 Jun 2011 08:29:03 +0200, Harald Dunkel ha...@afaics.de wrote:
...
My virtualization servers themselves were running testing, too, but
since Squeeze has been released testing is changing rapidly. Currently
I cannot rely upon testing for server installations.
So use stable + backports
Hi,
Philip Hands p...@hands.com writes:
On Sun, 05 Jun 2011 08:29:03 +0200, Harald Dunkel ha...@afaics.de wrote:
Your pipe-dream of an effortless, stable, and up to date system is just
that -- pick any two.
I personally prefer stable system with unstable chroot. This gives me
best of both
On Sun, 2011-06-05 at 18:02 +0200, Harald Dunkel wrote:
I cannot speak for others, but I don't wait 3 years. I do
regular updates/upgrades to include the most recent security
and bug fixes. We've scheduled regular maintenance weekends
every 3 months for this. Important updates are installed
On Sun, 05 Jun 2011 18:02:14 +0200, Harald Dunkel wrote:
Debian already classifies packages in different priorities, to
be used today when package updates are pushed into testing, for
example.
You appear to have confused package priority and upload urgency.
Testing migration is affected by
Le dimanche 05 juin 2011 à 18:02 +0200, Harald Dunkel a écrit :
I understand that splitting main into core/stable and
main/testing would be a deep cut. Surely I do not expect it
to happen within the next few weeks or months. Just think
about it.
What you do not understand is how presumptuous
On Sat, Jun 4, 2011 at 2:54 PM, Harald Dunkel wrote:
On 06/04/11 07:56, Paul Wise wrote:
Sounds like you are looking for backports.debian.org?
Backports for Squeeze contains just about 400 package,
Hmm, I'm getting the impression that what you want is a
squeeze-backports-auto suite that
Paul Wise p...@debian.org writes:
On Sat, Jun 4, 2011 at 2:54 PM, Harald Dunkel wrote:
On 06/04/11 07:56, Paul Wise wrote:
Sounds like you are looking for backports.debian.org?
Backports for Squeeze contains just about 400 package,
Hmm, I'm getting the impression that what you want is a
On Sat, June 4, 2011 07:45, Harald Dunkel wrote:
Having 3+ packages within a single main repository is
pretty bulky. Would it be possible to distinguish between
the core Debian and main somehow?
I don't want to keep anybody out. I just would like to use
the core packages of Debian
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
On 06/04/11 07:56, Paul Wise wrote:
Sounds like you are looking for backports.debian.org?
Backports for Squeeze contains just about 400 package,
AFIACS.
Regards
Harri
-BEGIN PGP SIGNATURE-
Version: GnuPG v1.4.11 (GNU/Linux)
Comment:
On Sat, Jun 4, 2011 at 2:54 PM, Harald Dunkel ha...@afaics.de wrote:
Backports for Squeeze contains just about 400 package,
AFIACS.
Yep, if you want more you should either build (and upload) them
yourself or talk to the maintainers of the ones you want and get them
to build and upload them.
Harald Dunkel ha...@afaics.de writes:
I don't want to keep anybody out. I just would like to use the core
packages of Debian release xyz (all the essential packages, for example)
together with more up-to-date packages in testing (kernel drivers,
development tools, eye candy, games, etc).
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
On 06/04/11 09:05, Paul Wise wrote:
Alternatively you might want to install from testing directly. Not
everything from testing is installable on stable, which is where
backports comes in.
Installing testing for the whole system is no option. The
On Sb, 04 iun 11, 10:12:42, Harald Dunkel wrote:
I would prefer if Debian distinguishes between core and main instead.
This means splitting the current main repository.
In the new system the main/testing packages should be _guaranteed_
to work together with the most recent core/stable
On Sat, 04 Jun 2011 07:45:36 +0200
Harald Dunkel ha...@afaics.de wrote:
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
Hi folks,
Having 3+ packages within a single main repository is
pretty bulky. Would it be possible to distinguish between
the core Debian and main somehow?
The
On Sat, 04 Jun 2011 10:12:42 +0200
Harald Dunkel ha...@afaics.de wrote:
Installing testing for the whole system is no option. The base
system (the core packages) should be provided by the most recent
release. I don't want to get an unbootable system.
You are more likely to get a problematic
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
On 06/04/11 07:26, Andrei POPESCU wrote:
This is one of those recurrent discussions coming up on debian-devel. It
is my impression (as a lurker) that most Debian Developers do not want
to have second-class packages and it is a feature that all
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
Hi Neil,
On 06/04/11 12:36, Neil Williams wrote:
On Sat, 04 Jun 2011 10:12:42 +0200
Harald Dunkel ha...@afaics.de wrote:
Installing testing for the whole system is no option. The base
system (the core packages) should be provided by the most
On Sat, Jun 04, 2011 at 05:07:26PM +0200, Harald Dunkel wrote:
About the package set dependencies: The core package sets would be
self contained, i.e. they would not depend upon packages outside of
their own core set. The new main/testing repository would be meant
to work with both
On Sat, 04 Jun 2011 17:07:26 +0200
Harald Dunkel ha...@afaics.de wrote:
On 06/04/11 12:36, Neil Williams wrote:
On Sat, 04 Jun 2011 10:12:42 +0200
Harald Dunkel ha...@afaics.de wrote:
Installing testing for the whole system is no option. The base
system (the core packages) should be
On Sat, 2011-06-04 at 08:54 +0200, Harald Dunkel wrote:
On 06/04/11 07:56, Paul Wise wrote:
Sounds like you are looking for backports.debian.org?
Backports for Squeeze contains just about 400 package,
AFIACS.
Would this be good enough for you if there were thousands of packages
instead?
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
Hi folks,
Having 3+ packages within a single main repository is
pretty bulky. Would it be possible to distinguish between
the core Debian and main somehow?
I don't want to keep anybody out. I just would like to use
the core packages of Debian
Sounds like you are looking for backports.debian.org?
--
bye,
pabs
http://wiki.debian.org/PaulWise
--
To UNSUBSCRIBE, email to debian-devel-requ...@lists.debian.org
with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Archive:
33 matches
Mail list logo
