On Mon, May 11, 2009 at 08:34:54PM +0200, Petr Pudlak wrote:
On Mon, May 11, 2009 at 03:11:22PM +0200, Filippo Rusconi wrote:
It is a pity to have a Debian Policy so well documented, to point
package-making learners to that Policy and then have non-conformant
builders.
In fact,
On Tue, May 05, 2009 at 07:13:23PM +0200, Julien Cristau wrote:
arch-specific builds run 'debian/rules build $rootcmd
debian/rules binary-arch' (where rootcmd is fakeroot or sudo). They
can't do anything else, because the build-arch target is (still) not
required.
Sure they can:
On Mon, May 11, 2009 at 13:46:30 +0200, Lionel Elie Mamane wrote:
No, policy is very clear on that: if you call the build target, you
_must_ satisfy Build-Depends-Indep and Build-Conflicts-Indep:
And policy is clearly not followed by any actual practice on this point.
So that's as much a bug
On Mon, May 11, 2009 at 02:11:18PM +0200, Julien Cristau wrote:
On Mon, May 11, 2009 at 13:46:30 +0200, Lionel Elie Mamane wrote:
No, policy is very clear on that: if you call the build target, you
_must_ satisfy Build-Depends-Indep and Build-Conflicts-Indep:
And policy is clearly not
Filippo Rusconi wrote:
On Mon, May 11, 2009 at 02:11:18PM +0200, Julien Cristau wrote:
On Mon, May 11, 2009 at 13:46:30 +0200, Lionel Elie Mamane wrote:
No, policy is very clear on that: if you call the build target, you
_must_ satisfy Build-Depends-Indep and Build-Conflicts-Indep:
And
On Mon, May 11, 2009 at 03:52:07PM +0200, Giacomo A. Catenazzi wrote:
Filippo Rusconi wrote:
On Mon, May 11, 2009 at 02:11:18PM +0200, Julien Cristau wrote:
On Mon, May 11, 2009 at 13:46:30 +0200, Lionel Elie Mamane wrote:
No, policy is very clear on that: if you call the build target, you
On Mon, 2009-05-11 at 15:11 +0200, Filippo Rusconi wrote:
On Mon, May 11, 2009 at 02:11:18PM +0200, Julien Cristau wrote:
On Mon, May 11, 2009 at 13:46:30 +0200, Lionel Elie Mamane wrote:
No, policy is very clear on that: if you call the build target, you
_must_ satisfy
On Mon, May 11, 2009 at 03:11:22PM +0200, Filippo Rusconi wrote:
On Mon, May 11, 2009 at 02:11:18PM +0200, Julien Cristau wrote:
On Mon, May 11, 2009 at 13:46:30 +0200, Lionel Elie Mamane wrote:
No, policy is very clear on that: if you call the build target, you
_must_ satisfy
Hi,
thanks for valuable comments, now it makes more sense to me. The problem was
that my 'build:' target is dependent on build-arch and build-indep targets (as
generated by dh_make when I started with the project). When pbuilder invokes
'debian/rules build', both these targets are called.
I
Petr Pudlak d...@pudlak.name writes:
Now I'm just concerned about (violating) Debian Policy (Sect. 4.9). It states
that the 'build:' target is mandatory. Should I leave 'build:' commented out,
possibly violating the policy, or perhaps include it just empty, removing its
dependencies on
Hi, I was trying to attend a reported bug (#521918) of a recently uploaded
package 'eprover', but unfortunately I didn't know what to do about it. I've
already asked on debian-mentors, but nobody replied.
The problem is that if pbuilder is invoked with --binary-arch, it still tries
to build the
On Tue, May 5, 2009 at 19:01:41 +0200, Petr Pudlak wrote:
Hi, I was trying to attend a reported bug (#521918) of a recently uploaded
package 'eprover', but unfortunately I didn't know what to do about it. I've
already asked on debian-mentors, but nobody replied.
The problem is that if
Hello,
On Tue, 05 May 2009, Petr Pudlak wrote:
The problem is that if pbuilder is invoked with --binary-arch, it still tries
to build the whole project, including the documentation (indep). It looks to
me as if the problem
is with pbuilder (or with the tools it's invoking), but of course the
13 matches
Mail list logo
