I'm trying to compile and pack on different architectures, but
after my first attempt I realized
that all Debian hosts are running Woody, not Sid.
Question: how and where do I build for Sid?
Has '+chroots' anything to do with it?
(Like bruckner: "woody Debian GNU/Linux (+chroots)")
I'm trying to compile and pack on different architectures, but
after my first attempt I realized
that all Debian hosts are running Woody, not Sid.
Question: how and where do I build for Sid?
Has '+chroots' anything to do with it?
(Like bruckner: "woody Debian GNU/Linux (+chroots)")
--
To UNSUB
I'm maintaining a package in non-free, which means that it will probably
never be compiled automatically (lowest priority).
So I need to do that myself. And I can find the available compile hosts
on http://db.debian.org/machines.cgi.
I usually builds my package using 'dpkg-buildpackage -rfakeroo
I'm maintaining a package in non-free, which means that it will probably
never be compiled automatically (lowest priority).
So I need to do that myself. And I can find the available compile hosts
on http://db.debian.org/machines.cgi.
I usually builds my package using 'dpkg-buildpackage -rfakeroo
I'm writing a general monitoring system (free of course :-) and
right now I've ten generated packages from it.
The main reason for separating them is the dependency-list, they
are slightly different for each package. Also, I want to give
the user the ability to just install the most necessary.
I'm writing a general monitoring system (free of course :-) and
right now I've ten generated packages from it.
The main reason for separating them is the dependency-list, they
are slightly different for each package. Also, I want to give
the user the ability to just install the most necessary.
In message <[EMAIL PROTECTED]> yo
u write:
> What I am wondering is, apart from a webapp (which can afford the overhead
> of scripting required to support inserting bits and bobs into webservers),
> what sort of packages need to put webserver-accessible pages up?
That's exactly what it is, a web
In message <[EMAIL PROTECTED]>
you write:
>
> Nooo. /usr/share/doc must be removable without any untoward
> effects on the operation of the system. /usr/share/ is the
> place to be, with an appropriate alias linking (probably)
> http://localhost// to /usr/share/.
Is there a standar
I've been searching the policy for guidance about cgi-scripts.
The only thing I find is that they should be placed in /usr/lib/cgi-bin.
But if there are several programs with short names that may
collide with other packages, is it ok to
put them in /usr/lib/cgi-bin/package-name/?
Or would that b
Lintian complains about .pm-files in /usr/lib/perl5, it wants
to have them in /usr/share/perl5, which normally is correct.
But if the perl-module has both binary and nonbinary files?
(I'm trying to remove any warnings for libio-pty-perl. :-)
Should all files for a perl module reside in the same
(I'm asking this because I want to be really sure that my key
still works after the current expire date, there has been a lot
of key-discussions, expiration date and such.)
My key is about to expire in a few months, is it
enough to update the expiration date and submit it to the key server?
Do
(I'm asking this because I want to be really sure that my key
still works after the current expire date, there has been a lot
of key-discussions, expiration date and such.)
My key is about to expire in a few months, is it
enough to update the expiration date and submit it to the key server?
Do
I'm curious about how the auto-builders work, somehow
I didn't find enough info about them, except for buildd
(http://buildd.debian.org/).
My question is: how do I make my packages available for
all architectures?
(Or at least, as many as possible. :-)
Should I do something or does the auto-bui
I'm writing a program that (for my conveniance) is split up
in several perl modules. These are put in my programs private
directory, /usr/lib/ham, because they might some day
interfere with other 'official' perl modules.
But lintian does not like this:
W: ham-server: executable-not-elf-or-scrip
I'm writing a program that (for my conveniance) is split up
in several perl modules. These are put in my programs private
directory, /usr/lib/ham, because they might some day
interfere with other 'official' perl modules.
But lintian does not like this:
W: ham-server: executable-not-elf-or-scri
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
Content-Type: text/plain; charset="iso-8859-1"
Content-ID: <[EMAIL PROTECTED]>
Content-Transfer-Encoding: quoted-printable
This is probably an ITP, but I didn't feel I was ready to
post to debian-devel yet and I'm also still waiting to become
a maint
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
Content-Type: text/plain; charset="iso-8859-1"
Content-ID: <[EMAIL PROTECTED]>
Content-Transfer-Encoding: quoted-printable
This is probably an ITP, but I didn't feel I was ready to
post to debian-devel yet and I'm also still waiting to become
a main
17 matches
Mail list logo
