On Sat, Feb 24, 2001 at 08:46:18PM +0100, Josip Rodin wrote:
On Sat, Feb 24, 2001 at 01:43:38PM +, Patrick Caulfield wrote:
I've taken one of my packages (dnet-common) and turned its only binary into a
shell script so that the package is now architecture independant.
If I just
I have a package which can be build both on potato and on woody,
but the resulting binary package for woody won't install on potato.
Vica-versa, I don't know - just assume that it won't install either.
Now I want to create two separate binary packages, or rather, I would
like to create two
On Tue, Feb 27, 2001 at 11:45:08AM +, Julian Gilbey wrote:
On Tue, Feb 27, 2001 at 12:15:16PM +0100, Peter van Rossum wrote:
I have a package which can be build both on potato and on woody,
but the resulting binary package for woody won't install on potato.
Vica-versa, I don't know -
On Tue, Feb 27, 2001 at 01:58:07AM -1000, Brian Russo wrote:
On Tue, Feb 27, 2001 at 12:49:55PM +0100, Peter van Rossum wrote:
On Tue, Feb 27, 2001 at 11:45:08AM +, Julian Gilbey wrote:
But anyway, that's not the problem. I don't need the binary package to
work both on potato and on
On Tue, Feb 27, 2001 at 01:34:07PM +0100, Peter van Rossum wrote:
Yes, of course, and that is what I did. But the actual question was:
how do I get dpkg-buildpackage to give the potato version a different
*name*? Just renaming the files gives problems with the signature on
the .changes/.dsc
On Tue, 27 Feb 2001, Peter van Rossum wrote:
Yes, of course, and that is what I did. But the actual question was:
how do I get dpkg-buildpackage to give the potato version a different
*name*? Just renaming the files gives problems with the signature on
the .changes/.dsc files.
If you're
On Tue, Feb 27, 2001 at 01:56:29PM +0100, Ove Kaaven wrote:
If you're just going to put these on the webpage, why would you even need
the .changes file? (And the .dsc is only for the source package, so you
don't need that for the potato build either)
I'd put the potato and woody build in
On Tue, 27 Feb 2001, Peter van Rossum wrote:
On Tue, Feb 27, 2001 at 01:56:29PM +0100, Ove Kaaven wrote:
If you're just going to put these on the webpage, why would you even need
the .changes file? (And the .dsc is only for the source package, so you
don't need that for the potato build
Greetings!
Ben Collins [EMAIL PROTECTED] writes:
On Thu, Dec 07, 2000 at 12:14:53PM -0500, Camm Maguire wrote:
Greetings, and thank you so much for this helpful information!
1) I notice you reference 'apic'. Do you happen to know to what that
refers? The ones I recognize are
On Tue, Feb 27, 2001 at 12:21:25PM -0500, Camm Maguire wrote:
I'm getting around to this now, and had a question: What is the flag
that indicates SSE2 (I take it xmm - SSE1). I've looked through the
kernel source, and cannot find it.
arch/i386/kernel/setup.c get_cpuinfo()
The flags are
On Tue, 27 Feb 2001, Peter S Galbraith wrote:
In fact, make _sure_ you don't allow access to a signed .changes
file on an unofficial web page because that would allow anybody
to upload it to Debian. It's signed after all.
Are the Debian upload queues not all password-protected? If they
Hi,
I have packaged xgospel, probably the best client for playing Go on
the Internet Go Server IGS, and put the sources into
deb-src http://samiel.theorie.physik.uni-muenchen.de/debian sid main
If you run the appropriate combination of system and platform, you can
also use the binary packages
On Tue, 27 Feb 2001, Peter van Rossum wrote:
I tried `dpkg-buildpackage -b -apotato_i386 -rfakeroot' on potato after
I first build the package with `dpkg-buildpackage -rfakeroot' on woody.
Potato may not be a different architecture than woody, but it was the
closest thing I could find. This
I will sponsor this, assuming it looks good (looking over it now).
Britton Kerin
__
GNU GPL: "The Source will be with you... always."
On 27 Feb 2001, Jens Schmalzing wrote:
Hi,
I have packaged xgospel, probably the best client for playing Go on
the Internet Go Server IGS, and put the
On Sat, Feb 24, 2001 at 08:46:18PM +0100, Josip Rodin wrote:
On Sat, Feb 24, 2001 at 01:43:38PM +, Patrick Caulfield wrote:
I've taken one of my packages (dnet-common) and turned its only binary into
a
shell script so that the package is now architecture independant.
If I just
On Tue, Feb 27, 2001 at 02:20:15AM +0100, Eric Van Buggenhaut wrote:
So, ...
Is it OK if I include /var/lib/crafty in debian/conffiles ? Do I have to
include every file or just /var/lib/crafty/* ?
No, it isn't at all. Any configuration files MUST reside in /etc.
These are not configuration
I have a package which can be build both on potato and on woody,
but the resulting binary package for woody won't install on potato.
Vica-versa, I don't know - just assume that it won't install either.
Now I want to create two separate binary packages, or rather, I would
like to create two
On Tue, Feb 27, 2001 at 12:15:16PM +0100, Peter van Rossum wrote:
I have a package which can be build both on potato and on woody,
but the resulting binary package for woody won't install on potato.
Vica-versa, I don't know - just assume that it won't install either.
Compiled, yes? Then
On Tue, Feb 27, 2001 at 11:45:08AM +, Julian Gilbey wrote:
On Tue, Feb 27, 2001 at 12:15:16PM +0100, Peter van Rossum wrote:
I have a package which can be build both on potato and on woody,
but the resulting binary package for woody won't install on potato.
Vica-versa, I don't know -
On Tue, Feb 27, 2001 at 12:49:55PM +0100, Peter van Rossum wrote:
On Tue, Feb 27, 2001 at 11:45:08AM +, Julian Gilbey wrote:
But anyway, that's not the problem. I don't need the binary package to
work both on potato and on woody - I just want an easy way to create two
different versions of
On Tue, Feb 27, 2001 at 01:58:07AM -1000, Brian Russo wrote:
On Tue, Feb 27, 2001 at 12:49:55PM +0100, Peter van Rossum wrote:
On Tue, Feb 27, 2001 at 11:45:08AM +, Julian Gilbey wrote:
But anyway, that's not the problem. I don't need the binary package to
work both on potato and on
On Tue, Feb 27, 2001 at 01:34:07PM +0100, Peter van Rossum wrote:
Yes, of course, and that is what I did. But the actual question was:
how do I get dpkg-buildpackage to give the potato version a different
*name*? Just renaming the files gives problems with the signature on
the .changes/.dsc
On Tue, Feb 27, 2001 at 06:36:40AM -0600, Christian T. Steigies wrote:
With the changelog entry? Make one for potato and one for woody. the potato
version get something with potao in the version number, the woody get a
higher version number, without potato. Happens all the time, look in
On Tue, 27 Feb 2001, Peter van Rossum wrote:
Yes, of course, and that is what I did. But the actual question was:
how do I get dpkg-buildpackage to give the potato version a different
*name*? Just renaming the files gives problems with the signature on
the .changes/.dsc files.
If you're
On Tue, Feb 27, 2001 at 01:56:29PM +0100, Ove Kaaven wrote:
If you're just going to put these on the webpage, why would you even need
the .changes file? (And the .dsc is only for the source package, so you
don't need that for the potato build either)
I'd put the potato and woody build in
On Tue, 27 Feb 2001, Peter van Rossum wrote:
On Tue, Feb 27, 2001 at 01:56:29PM +0100, Ove Kaaven wrote:
If you're just going to put these on the webpage, why would you even need
the .changes file? (And the .dsc is only for the source package, so you
don't need that for the potato build
What I do is edit the last version in the debian/changelog, e.g.
gri (2.6.0-1) unstable; urgency=low
to:
gri (2.6.0-0potato1) unstable; urgency=low
Ove Kaaven wrote:
On Tue, 27 Feb 2001, Peter van Rossum wrote:
Yes, of course, and that is what I did. But the actual question was:
how do
Greetings!
Ben Collins [EMAIL PROTECTED] writes:
On Thu, Dec 07, 2000 at 12:14:53PM -0500, Camm Maguire wrote:
Greetings, and thank you so much for this helpful information!
1) I notice you reference 'apic'. Do you happen to know to what that
refers? The ones I recognize are
On Tue, Feb 27, 2001 at 12:21:25PM -0500, Camm Maguire wrote:
I'm getting around to this now, and had a question: What is the flag
that indicates SSE2 (I take it xmm - SSE1). I've looked through the
kernel source, and cannot find it.
arch/i386/kernel/setup.c get_cpuinfo()
The flags are sse
On Tue, 27 Feb 2001, Peter S Galbraith wrote:
In fact, make _sure_ you don't allow access to a signed .changes
file on an unofficial web page because that would allow anybody
to upload it to Debian. It's signed after all.
Are the Debian upload queues not all password-protected? If they are,
Steve Langasek wrote:
On Tue, 27 Feb 2001, Peter S Galbraith wrote:
In fact, make _sure_ you don't allow access to a signed .changes
file on an unofficial web page because that would allow anybody
to upload it to Debian. It's signed after all.
Are the Debian upload queues not all
Greetings, and thanks! I've been using the 2.2 series with xmm
patches. I take it then the analogous flags are:
xmm, and 26.
Correct (see setup.c)? ldso will know to look in these subdirs on
such a kernel? What then to do with the standard package? Will 2.4
become the Debian default soon?
Hi,
I have packaged xgospel, probably the best client for playing Go on
the Internet Go Server IGS, and put the sources into
deb-src http://samiel.theorie.physik.uni-muenchen.de/debian sid main
If you run the appropriate combination of system and platform, you can
also use the binary packages
On Tue, 27 Feb 2001, Peter van Rossum wrote:
I tried `dpkg-buildpackage -b -apotato_i386 -rfakeroot' on potato after
I first build the package with `dpkg-buildpackage -rfakeroot' on woody.
Potato may not be a different architecture than woody, but it was the
closest thing I could find. This
Hello,
I'm having the darndest time figuring out what's going wrong with the PETSc
build. It was fine when I built and uploaded PPC packages three weeks ago,
and alpha, sparc and arm seemed to build fine, but it breaks now in exactly
that way on unstable i386 and powerpc and testing alpha.
The
I will sponsor this, assuming it looks good (looking over it now).
Britton Kerin
__
GNU GPL: The Source will be with you... always.
On 27 Feb 2001, Jens Schmalzing wrote:
Hi,
I have packaged xgospel, probably the best client for playing Go on
the Internet Go Server IGS, and put the sources
On Tue, Feb 27, 2001 at 04:32:38PM -0500, Adam C Powell IV wrote:
The problem is that it's setting MPI_LIBS to -L{MPI_HOME}/build/... like it's
substituting ${MPI_HOME} with {MPI_HOME} instead of the value of the
Have you copied the -L option verbatim? If so, the error is clear:
there's no $
Julian Gilbey wrote:
On Tue, Feb 27, 2001 at 04:32:38PM -0500, Adam C Powell IV wrote:
The problem is that it's setting MPI_LIBS to -L{MPI_HOME}/build/... like
it's
substituting ${MPI_HOME} with {MPI_HOME} instead of the value of the
Have you copied the -L option verbatim? If so, the
Hi Adam,
On Tue, 27 Feb 2001, Adam C Powell IV wrote:
Have you copied the -L option verbatim? If so, the error is clear:
there's no $ between the -L and the {. Otherwise, I have no idea.
I'm sorry, I was very imprecise. Here are the details:
# For mpich: (woody mpich uses
39 matches
Mail list logo
