Hi,
I am going to upload packages for the s390 architecture. There are still a
lot of packages which don't support s390 in config.sub and config.guess yet.
Is it necessary to write a bug report and do a source NMU for each of these
packages or is there a more generic approach?
--
Thanks,
Gerhard
On Tue, 15 May 2001, Sean 'Shaleh' Perry wrote:
> On 15-May-2001 Niall Young wrote:
> > I'm creating a bunch of custom task packages, mostly empty
> > with dependencies but a few will need to contain configs
> > and pre-filled debconf entries.
> >
> > It's not too clear from the NMG and the DDR o
On Tue, 15 May 2001, Sean 'Shaleh' Perry wrote:
> On 15-May-2001 Niall Young wrote:
> > I'm creating a bunch of custom task packages, mostly empty
> > with dependencies but a few will need to contain configs
> > and pre-filled debconf entries.
> >
> > It's not too clear from the NMG and the DDR
On 15-May-2001 Niall Young wrote:
> I'm creating a bunch of custom task packages, mostly empty
> with dependencies but a few will need to contain configs
> and pre-filled debconf entries.
>
> It's not too clear from the NMG and the DDR on how to do
> this. I can create empty task packages fine,
On 15-May-2001 Niall Young wrote:
> I'm creating a bunch of custom task packages, mostly empty
> with dependencies but a few will need to contain configs
> and pre-filled debconf entries.
>
> It's not too clear from the NMG and the DDR on how to do
> this. I can create empty task packages fine,
Javier Viñuales Gutiérrez wrote:
> [-- text/plain, encoding quoted-printable, 17 lines --]
>
> On mar, may 15, 2001 at 10:45:53 +0100, Julian Gilbey wrote:
>> No, you are right: all you need is docbook-to-man. See policy,
>> section 2.4.2 where this is explained in detail.
>
> Ok, I just readed
Javier Viñuales Gutiérrez wrote:
> [-- text/plain, encoding quoted-printable, 17 lines --]
>
> On mar, may 15, 2001 at 10:45:53 +0100, Julian Gilbey wrote:
>> No, you are right: all you need is docbook-to-man. See policy,
>> section 2.4.2 where this is explained in detail.
>
> Ok, I just readed
On mar, may 15, 2001 at 10:45:53 +0100, Julian Gilbey wrote:
> No, you are right: all you need is docbook-to-man. See policy,
> section 2.4.2 where this is explained in detail.
Ok, I just readed it. Could a version number omition of the Build-depends entry
for
docbook-to-man makes this bug (#975
On Tue, May 15, 2001 at 11:10:09AM +0200, Javier Vi?uales Guti?rrez wrote:
> Hello,
>
> I'm intending to fix a silly build-depends bug. I'd did it like this:
>
> Build-depends: [...], docbook-to-man
>
> It seems that it's needed more build-depends entries for man page
> generation, the bug is #9
Thus spoke Javier Vi?uales Gutiérrez <[EMAIL PROTECTED]> on 2001-05-15 11:10:09:
> Can anybody tell me anything about it please?, thank you.
IMHO, you should add docbook-to-man to the build-depends line, becasue
that package contains /usr/bin/docbook-to-man. The things
docbook-to-man depends on ar
Hello,
I'm intending to fix a silly build-depends bug. I'd did it like this:
Build-depends: [...], docbook-to-man
It seems that it's needed more build-depends entries for man page
generation, the bug is #97513 against hptalx package.
I thought that "Build-depends" calls his entries and his dep
On mar, may 15, 2001 at 10:45:53 +0100, Julian Gilbey wrote:
> No, you are right: all you need is docbook-to-man. See policy,
> section 2.4.2 where this is explained in detail.
Ok, I just readed it. Could a version number omition of the Build-depends entry for
docbook-to-man makes this bug (#975
On Tue, May 15, 2001 at 11:10:09AM +0200, Javier Vi?uales Guti?rrez wrote:
> Hello,
>
> I'm intending to fix a silly build-depends bug. I'd did it like this:
>
> Build-depends: [...], docbook-to-man
>
> It seems that it's needed more build-depends entries for man page
> generation, the bug is #
Hi,
Marc Haber writes:
> All three of these packages are quite large packages with a lot of
> framework. Actually, I was hoping that there is a package that
> simpily includes a kernel module, for example a network driver, that
> I could simply cannibalize for my e100 package.
You should probab
On Tue, 15 May 2001 07:40:10 +1200, Andrew McMillan
<[EMAIL PROTECTED]> wrote:
>It seems to me that the best packages to model on would be things like alsa,
>pcmcia
>and i2c which all have a source package (so that people can compile their own
>modules) and a modules package, with modules compiled
Thus spoke Javier Vi?uales Gutiérrez <[EMAIL PROTECTED]> on 2001-05-15 11:10:09:
> Can anybody tell me anything about it please?, thank you.
IMHO, you should add docbook-to-man to the build-depends line, becasue
that package contains /usr/bin/docbook-to-man. The things
docbook-to-man depends on a
Hello,
I'm intending to fix a silly build-depends bug. I'd did it like this:
Build-depends: [...], docbook-to-man
It seems that it's needed more build-depends entries for man page
generation, the bug is #97513 against hptalx package.
I thought that "Build-depends" calls his entries and his de
17 matches
Mail list logo
