On Wed, Jun 30, 2004 at 09:51:05PM +0200, Andreas Tille wrote:
> On Wed, 30 Jun 2004, Colin Watson wrote:
>
> > > I'll check this but I doubt that this would help because even
> > > configure target might be too late.
> >
> > Do it in the clean target.
> But then the source tarball does not look l
On Wed, Jun 30, 2004 at 09:51:05PM +0200, Andreas Tille wrote:
> On Wed, 30 Jun 2004, Colin Watson wrote:
> > Do it in the clean target.
>
> But then the source tarball does not look like the source archive
> as checked out of CVS ...
I don't think this is a problem. CVS would contain debian/cont
On Wed, 30 Jun 2004, Otavio Salvador wrote:
> os> Did you looked at kernel-wedge package? this is used to build the
> os> kernel image for debian-installer and doesn't it right fine. This is
> os> called to build the needed files *before* you built the package.
>
> Another issues. Please check the
|| On Wed, 30 Jun 2004 13:25:52 -0300
|| Otavio Salvador <[EMAIL PROTECTED]> wrote:
|| On Wed, 30 Jun 2004 17:52:42 +0200 (CEST)
|| Andreas Tille <[EMAIL PROTECTED]> wrote:
at> On Wed, 30 Jun 2004, Jeroen van Wolffelaar wrote:
>>> > Is not possible build the control file in configure target, b
On Wed, 30 Jun 2004, Colin Watson wrote:
> > I'll check this but I doubt that this would help because even
> > configure target might be too late.
>
> Do it in the clean target.
But then the source tarball does not look like the source archive
as checked out of CVS ...
Kind regards
Andr
On Wed, Jun 30, 2004 at 05:48:05PM +0200, Andreas Tille wrote:
> On Wed, 30 Jun 2004, Otavio Salvador wrote:
> > Is not possible build the control file in configure target, before
> > the build?
>
> I'll check this but I doubt that this would help because even
> configure target might be too late
|| On Wed, 30 Jun 2004 17:52:42 +0200 (CEST)
|| Andreas Tille <[EMAIL PROTECTED]> wrote:
at> On Wed, 30 Jun 2004, Jeroen van Wolffelaar wrote:
>> > Is not possible build the control file in configure target, before the
>> > build?
>>
>> That won't help, since a source package should on rebuild
On Wed, 30 Jun 2004, Otavio Salvador wrote:
> Is not possible build the control file in configure target, before the build?
I'll check this but I doubt that this would help because even configure
target might be too late.
Kind regards
Andreas.
On Wed, 30 Jun 2004, Jeroen van Wolffelaar wrote:
> > Is not possible build the control file in configure target, before the
> > build?
>
> That won't help, since a source package should on rebuild not be
> functionally different, I don't see why it isn't possible to do stuff in
> the clean targ
On Wed, Jun 30, 2004 at 10:44:37AM -0300, Otavio Salvador wrote:
> || On Wed, 30 Jun 2004 13:19:26 +0200 (CEST)
> || Andreas Tille <[EMAIL PROTECTED]> wrote:
>
> at> On Wed, 30 Jun 2004, Jeroen van Wolffelaar wrote:
> >> Policy says the Binary: header should list all packages that _could_ be
> >>
|| On Wed, 30 Jun 2004 13:19:26 +0200 (CEST)
|| Andreas Tille <[EMAIL PROTECTED]> wrote:
at> On Wed, 30 Jun 2004, Jeroen van Wolffelaar wrote:
>> Policy says the Binary: header should list all packages that _could_ be
>> build (but not necessarily are, for example, the xfree86 source package
>> l
On Wed, 30 Jun 2004, Jeroen van Wolffelaar wrote:
> Policy says the Binary: header should list all packages that _could_ be
> build (but not necessarily are, for example, the xfree86 source package
> lists xserver-xfree86, but it isn't build on s390). So, you should make
> the clean target to put
On Wed, Jun 30, 2004 at 08:53:57AM +0200, Andreas Tille wrote:
> On Tue, 29 Jun 2004, Raphael Hertzog wrote:
>
> > dpkg-source -b should create this file AFAIK. I'm not sure where this
> > program is called however. I see a reference to it in dpkg-buildpackage
> > but that's all right now.
> You a
On Tue, 29 Jun 2004, Raphael Hertzog wrote:
> dpkg-source -b should create this file AFAIK. I'm not sure where this
> program is called however. I see a reference to it in dpkg-buildpackage
> but that's all right now.
You are right here and I found out that source tarball and .dsc file are
created
On Wed, Jun 30, 2004 at 12:00:28AM +0200, Jeroen van Wolffelaar wrote:
> On Tue, Jun 29, 2004 at 09:59:19AM +0200, Andreas Tille wrote:
> > On Tue, 29 Jun 2004, Raphael Hertzog wrote:
> > > Fix your package is the only thing I can say :
> > > $ apt-cache showsrc debian-med | grep ^Binary
> > > Bina
On Tue, Jun 29, 2004 at 09:59:19AM +0200, Andreas Tille wrote:
> On Tue, 29 Jun 2004, Raphael Hertzog wrote:
>
> > Fix your package is the only thing I can say :
> > $ apt-cache showsrc debian-med | grep ^Binary
> > Binary: med
> It seems that the reason is in the *.dsc file which does not contain
Quoting Andreas Tille:
> On Tue, 29 Jun 2004, Raphael Hertzog wrote:
>
> > Fix your package is the only thing I can say :
> > $ apt-cache showsrc debian-med | grep ^Binary
> > Binary: med
> It seems that the reason is in the *.dsc file which does not contain
> the right packages. The reason for t
On Tue, 29 Jun 2004, Raphael Hertzog wrote:
> Fix your package is the only thing I can say :
> $ apt-cache showsrc debian-med | grep ^Binary
> Binary: med
It seems that the reason is in the *.dsc file which does not contain
the right packages. The reason for this seems to be in the build process
Hi,
Quoting Andreas Tille:
> Hi,
>
> any reason why the binary packages from the debian-med source package are
> not listed correctly?
>
> http://packages.qa.debian.org/d/debian-med.html
>
> I wonder whether there might be more cases that only one binary package
> is detected when more than
Hi,
any reason why the binary packages from the debian-med source package are
not listed correctly?
http://packages.qa.debian.org/d/debian-med.html
I wonder whether there might be more cases that only one binary package
is detected when more than one are builded.
Kind regards
An
20 matches
Mail list logo
