On Mon, 4 Apr 2005, Junichi Uekawa wrote:
Hi,
The new toolset(tentatively called dbs-ng while I'm developing it) supports
what I call pre-patched source.
Was this a April-fools joke, or do you have some code that we can look at?
While there is no code to look at, xen 2.0(in experimental)
unpack: some packages unpack the upstream tarball, some do patching
patch: some patch the source tree, some generate patch out of it.
2. A policy on what target to have for optional unpacking and patching,
and apply a recommendation that is enforced on etch/etch+1
That should probably
On Tue, Apr 12, 2005 at 10:29:10PM +0900, Junichi Uekawa wrote:
unpack: some packages unpack the upstream tarball, some do patching
patch: some patch the source tree, some generate patch out of it.
2. A policy on what target to have for optional unpacking and patching,
and apply a
Hi,
| I second suggestion given at #250202 and like to see unpacked and
| patched targets to hit Policy 4.8.
If so, it should be «unpack» and «patch» to match the build and
install targets.
Note that there are existing packages that use 'unpack' and 'patch'
targets for other
Scribit Lars Wirzenius dies 06/04/2005 hora 21:34:
I don't find it very sane to be forced to deliberately trigger
problems on the user's system to find bugs.
I assume the goal is to make it fail on the developer's system, on
build daemons, whenever random developers unpack the package
If it
Scribit Steve Greenland dies 06/04/2005 hora 17:37:
There's a long history of people relying on explicitly unspecified
behaviour, and then bitching when that behaviour changes.
For the sake of my curiosity again, could you point me some precise
examples?
Historically,
Nowhere man
--
[EMAIL
On Thu, Apr 07, 2005 at 10:22:15PM +0200, Pierre THIERRY wrote:
Scribit Steve Greenland dies 06/04/2005 hora 17:37:
There's a long history of people relying on explicitly unspecified
behaviour, and then bitching when that behaviour changes.
For the sake of my curiosity again, could you
On 07-Apr-05, 15:22 (CDT), Pierre THIERRY [EMAIL PROTECTED] wrote:
Scribit Steve Greenland dies 06/04/2005 hora 17:37:
There's a long history of people relying on explicitly unspecified
behaviour, and then bitching when that behaviour changes.
For the sake of my curiosity again, could
Scribit Steve Greenland dies 04/04/2005 hora 07:15:
- what problems do thsi random order could weed?
Unnoted dependencies that just happen to be fulfilled due to a
consistent (though arbitrary) application order. By applying in a
different order each time, you should trigger an error fairly
ke, 2005-04-06 kello 19:31 +0200, Pierre THIERRY kirjoitti:
Scribit Steve Greenland dies 04/04/2005 hora 07:15:
- what problems do thsi random order could weed?
Unnoted dependencies that just happen to be fulfilled due to a
consistent (though arbitrary) application order. By applying in a
On 06-Apr-05, 12:31 (CDT), Pierre THIERRY [EMAIL PROTECTED] wrote:
Urgh. Are you doing computer science or cooking? Couldn't the
application write somewhere the order of the patch that it just used?!
*I'm* not doing anything except postulating the reasoning behind a
deliberately random
Scribit Adam Heath dies 01/04/2005 hora 19:10:
Additionally, as a way to weed out other problems, any patches that
are leafs(ie, don't depend on anything) are applied in a random order.
For the sake of my curiosity:
- what problems do thsi random order could weed?
- won't it be more difficult
On 04-Apr-05, 02:48 (CDT), Pierre THIERRY [EMAIL PROTECTED] wrote:
Scribit Adam Heath dies 01/04/2005 hora 19:10:
Additionally, as a way to weed out other problems, any patches that
are leafs(ie, don't depend on anything) are applied in a random order.
For the sake of my curiosity:
-
Hi,
The new toolset(tentatively called dbs-ng while I'm developing it) supports
what I call pre-patched source.
Was this a April-fools joke, or do you have some code that we can look at?
However, the concept looks possible to implement, and
will fix most of the problems we have with handling
Hi,
| I second suggestion given at #250202 and like to see unpacked and
| patched targets to hit Policy 4.8.
If so, it should be «unpack» and «patch» to match the build and
install targets.
Note that there are existing packages that use 'unpack' and 'patch'
targets for other meanings.
On Sun, 27 Mar 2005, Lars Wirzenius wrote:
su, 2005-03-27 kello 09:01 +0200, George Danchev kirjoitti:
I second suggestion given at #250202 and like to see unpacked and
patched
targets to hit Policy 4.8.
I hear that Adam Heath (doogie for those on IRC) has been working on a
new source
* Steve Kowalik
| On Thu, 31 Mar 2005 08:54:01 +0200, Tollef Fog Heen uttered
| TTBOMK, he hasn't discussed this with the dpkg maintainer, nor has he
| made his code public.
|
| Er, Adam Heath has made plenty of uploads of dpkg, and is listed as an
| Uploader.
Yes, but (again, TTBOMK) he
On Thursday 31 March 2005 15:14, Tollef Fog Heen wrote:
* Steve Kowalik
| On Thu, 31 Mar 2005 08:54:01 +0200, Tollef Fog Heen uttered
|
| TTBOMK, he hasn't discussed this with the dpkg maintainer, nor has he
| made his code public.
|
| Er, Adam Heath has made plenty of uploads of dpkg,
On Thu, 2005-03-31 at 17:40 +1000, Steve Kowalik wrote:
On Thu, 31 Mar 2005 08:54:01 +0200, Tollef Fog Heen uttered
TTBOMK, he hasn't discussed this with the dpkg maintainer, nor has he
made his code public.
Er, Adam Heath has made plenty of uploads of dpkg,
Hasn't made any in the last
On Thu, 2005-03-31 at 15:49 +0300, George Danchev wrote:
On Thursday 31 March 2005 15:14, Tollef Fog Heen wrote:
* Steve Kowalik
| On Thu, 31 Mar 2005 08:54:01 +0200, Tollef Fog Heen uttered
|
| TTBOMK, he hasn't discussed this with the dpkg maintainer, nor has he
| made his code
* George Danchev
| I second suggestion given at #250202 and like to see unpacked and
| patched targets to hit Policy 4.8.
If so, it should be «unpack» and «patch» to match the build and
install targets.
--
Tollef Fog Heen,''`.
UNIX is
* Lars Wirzenius
| su, 2005-03-27 kello 09:01 +0200, George Danchev kirjoitti:
|
| I second suggestion given at #250202 and like to see unpacked
| and patched targets to hit Policy 4.8.
|
| I hear that Adam Heath (doogie for those on IRC) has been working on a
| new source package format that
On Thu, 31 Mar 2005 08:54:01 +0200, Tollef Fog Heen uttered
TTBOMK, he hasn't discussed this with the dpkg maintainer, nor has he
made his code public.
Er, Adam Heath has made plenty of uploads of dpkg, and is listed as an
Uploader.
Cheers,
--
Steve
I
[Darren Salt]
Back-porting to sarge using tools in sarge?
That doesn't sound so daunting. Anyone doing serious backporting will
need to start by backporting a few development tools, which is already
true from woody - sarge - viz. debhelper 4.
signature.asc
Description: Digital signature
On Saturday 26 March 2005 00:49, Junichi Uekawa wrote:
Hi,
Optional source patching is non-standard in Debian, and
I would like a standard interface to interact with Debian
source.
So would I. Which is why I filed #250202
I second suggestion given at #250202 and like to see
su, 2005-03-27 kello 09:01 +0200, George Danchev kirjoitti:
I second suggestion given at #250202 and like to see unpacked and patched
targets to hit Policy 4.8.
I hear that Adam Heath (doogie for those on IRC) has been working on a
new source package format that will make
On Sun, 27 Mar 2005, Lars Wirzenius wrote:
I hear that Adam Heath (doogie for those on IRC) has been working on a
new source package format that will make tarball-within-tarball sources
But we will only be able to see it (nevermind USE it) when hell freezes
over, which must be at etch+2 or
su, 2005-03-27 kello 07:49 -0300, Henrique de Moraes Holschuh kirjoitti:
On Sun, 27 Mar 2005, Lars Wirzenius wrote:
I hear that Adam Heath (doogie for those on IRC) has been working on a
new source package format that will make tarball-within-tarball sources
But we will only be able to see
On Sunday 27 March 2005 11:25, Lars Wirzenius wrote:
su, 2005-03-27 kello 09:01 +0200, George Danchev kirjoitti:
I second suggestion given at #250202 and like to see unpacked and
patched targets to hit Policy 4.8.
I hear that Adam Heath (doogie for those on IRC) has been working on a
new
Hi,
My plan is to have a source-repository of every single Debian package.
I consider it to be interesting in several ways including that of avoiding
symbol conflicts with shared library package, and finding out
what might be a scalable way to maintain such a large chunk of source code.
So
On Monday 28 March 2005 01:33, Junichi Uekawa wrote:
Hi,
Hello,
My plan is to have a source-repository of every single Debian package.
I consider it to be interesting in several ways including that of avoiding
symbol conflicts with shared library package, and finding out
what might be a
I demand that Lars Wirzenius may or may not have written...
su, 2005-03-27 kello 07:49 -0300, Henrique de Moraes Holschuh kirjoitti:
On Sun, 27 Mar 2005, Lars Wirzenius wrote:
I hear that Adam Heath (doogie for those on IRC) has been working on a
new source package format that will make
Hi,
I am planning to implement a script to obtain Debian source.
Is there anyone who has already done that ?
It is planned to have the following features:
1. wrapper to dpkg-source -x
2. heuristically parse debian/rules file to
extract and patch the Debian source as
dbs/dpatch
On Sat, Mar 26, 2005 at 06:54:19AM +0900, Junichi Uekawa wrote:
Optional source patching is non-standard in Debian, and
I would like a standard interface to interact with Debian
source.
So would I. Which is why I filed #250202.
Be sure to read the whole bug -- there's quite some discussion
Hi,
Optional source patching is non-standard in Debian, and
I would like a standard interface to interact with Debian
source.
So would I. Which is why I filed #250202
I have had a vague recollection that there was something
which had not been implemented yet; thanks for pointing it
35 matches
Mail list logo
