Hello all,
At work, we are making custom Debian packages and we need a special versioning
system so that apt does not try to replace our package with a newer upstream
one.
I would like to know if there's a standard way to proceed, apart from setting
the debian version to customX, which is good,
On Tue, Apr 17, 2001 at 11:18:32AM +0200, Amaya wrote:
Hello all,
At work, we are making custom Debian packages and we need a special versioning
system so that apt does not try to replace our package with a newer upstream
one.
I would like to know if there's a standard way to proceed,
On Tue, Apr 17, 2001 at 11:18:32AM +0200, Amaya wrote:
Hello all,
At work, we are making custom Debian packages and we need a special versioning
system so that apt does not try to replace our package with a newer upstream
one.
I would like to know if there's a standard way to proceed,
On Tue, Apr 17, 2001 at 13:03:44 +0200, Russell Coker wrote:
What is the name of the Alpha machine for Debian package development?
faure.d.o
http://db.debian.org/machines.cgi
Cheers,
M/
--
/~\ ASCII ribbon | "i have decided to release the first 24GB of my genetic
\ / campaign | code
On Tue, Apr 17, 2001 at 01:09:14PM +0200, Michael Weber wrote:
On Tue, Apr 17, 2001 at 13:03:44 +0200, Russell Coker wrote:
What is the name of the Alpha machine for Debian package development?
faure.d.o
http://db.debian.org/machines.cgi
Cheers,
M/
--
/~\ ASCII ribbon | "i have
On Tue, Apr 17, 2001 at 13:26:56 +0200, Davide Puricelli wrote:
On Tue, Apr 17, 2001 at 01:09:14PM +0200, Michael Weber wrote:
On Tue, Apr 17, 2001 at 13:03:44 +0200, Russell Coker wrote:
What is the name of the Alpha machine for Debian package development?
faure.d.o
On Tue, 17 Apr 2001, Amaya wrote:
At work, we are making custom Debian packages and we need a special
versioning system so that apt does not try to replace our package with
a newer upstream one.
I would like to know if there's a standard way to proceed, apart from
setting the debian
OK, thanks for this good piece of advice.
On Fri, Apr 13, 2001 at 06:10:22PM -0700, Mike Markley wrote:
On Fri, Apr 13, 2001 at 04:30:15PM -0800, Britton [EMAIL PROTECTED] spake forth:
It actually works with tcl 8.0, 8.1 and 8.2 you are right. So what about :
Depends: tcl8.0 |
Hi,
the upgrade-checklist says:
| - If your package has a daemon startup script in /etc/init.d/,
|and that script has parameters a system administrator may need,
|you need to modify the script to read values from a conffile
|placed in /etc/default/ directory. This
Hi,
the policy upgrading checklist says:
| - Files in /usr/share/doc may not be referenced by any
|program. If such files are needed, they must be placed in
|/usr/share/package-name/, and symbolic links created as required
|in /usr/share/doc/package-name/
Does "any
On Tue, 17 Apr 2001, Marc Haber wrote:
the policy upgrading checklist says:
| - Files in /usr/share/doc may not be referenced by any
|program. If such files are needed, they must be placed in
|/usr/share/package-name/, and symbolic links created as required
|in
Hullo! :)
I'm playing with packaging, and lintian's complaining about no manpage for
a binary... but I have a myapp.1 manpage in both the debian/
control-directory and the root of the source directory..
I don't understand what I'm doing wrong :(
Any pointers would be greatly appreciated.. as
On Tue, 17 Apr 2001 [EMAIL PROTECTED] wrote:
I don't understand what I'm doing wrong :(
Is your man page actually being installed in the build directory?
hunts through the tmp directory
Actually I don't have a tmp directory, but one with the same name as the
package itself...
But no sign
On Tue, Apr 17, 2001 at 10:43:00PM +0200, Marc Haber wrote:
Hi,
the upgrade-checklist says:
The upgrading-checklist starts by saying:
The checklist below has been created to simplify the upgrading process of
old packages. Note, that this list is not `official.' If you have doubts
On Tue, Apr 17, 2001 at 10:50:28PM +0200, Marc Haber wrote:
Hi,
the policy upgrading checklist says:
| - Files in /usr/share/doc may not be referenced by any
|program. If such files are needed, they must be placed in
|/usr/share/package-name/, and symbolic links
On Tue, Apr 17, 2001 at 05:27:16PM -0400, [EMAIL PROTECTED] wrote:
Another camp said that this practice should be avoided. The rationale
was that administrators might do something more drastic to avoid
populating /usr/share/doc in the first place, like mounting it as a
read-only partition or
On Tue, 17 Apr 2001 [EMAIL PROTECTED] wrote:
Are you using debhelper? If so, are you calling "dh_installmanpages" or
"dh_installman path/to/myapp.1" in debian/rules?
Ah :) Tried dh_installmanpages and it worked fine...
Since that seems to be a deprecated way of doing things, I'll use the
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
On 17-Apr-2001 Davide Puricelli wrote:
On Tue, Apr 17, 2001 at 01:09:14PM +0200, Michael Weber wrote:
On Tue, Apr 17, 2001 at 13:03:44 +0200, Russell Coker wrote:
What is the name of the Alpha machine for Debian package development?
On Mon, Apr 16, 2001 at 03:13:09PM -0700, Sean 'Shaleh' Perry wrote:
b) init script stuff, see update-inetd manpage.
I believe update-rc.d would be more appropriate. :)
--
Karl Söderström
[EMAIL PROTECTED] http://www.xanadunet.net
[EMAIL PROTECTED] http://www.debian.org
On Mon, Apr 16, 2001 at 01:21:45PM -0700, Sean 'Shaleh' Perry wrote:
To mistake a hard link for a zero-length file is sloppy coding.
This is a bug in lintian.
lintian gets its information from tar's output. A hardlink is shown as a zero
byte file.
So lintian does something like ar
Hello all,
At work, we are making custom Debian packages and we need a special versioning
system so that apt does not try to replace our package with a newer upstream
one.
I would like to know if there's a standard way to proceed, apart from setting
the debian version to customX, which is good,
On Tue, Apr 17, 2001 at 11:18:32AM +0200, Amaya wrote:
Hello all,
At work, we are making custom Debian packages and we need a special versioning
system so that apt does not try to replace our package with a newer upstream
one.
I would like to know if there's a standard way to proceed,
On Tue, Apr 17, 2001 at 11:18:32AM +0200, Amaya wrote:
Hello all,
At work, we are making custom Debian packages and we need a special versioning
system so that apt does not try to replace our package with a newer upstream
one.
I would like to know if there's a standard way to proceed,
I'm asking on d-m because this may be too stupid for d-d.
What is the name of the Alpha machine for Debian package development? It
seems that my programs operate differently on Alpha due to some subtleties of
floating point math and I'd like to try it out myself...
I have sent in my ssh key
On Tue, Apr 17, 2001 at 13:03:44 +0200, Russell Coker wrote:
What is the name of the Alpha machine for Debian package development?
faure.d.o
http://db.debian.org/machines.cgi
Cheers,
M/
--
/~\ ASCII ribbon | i have decided to release the first 24GB of my genetic
\ / campaign | code
On Tue, Apr 17, 2001 at 01:09:14PM +0200, Michael Weber wrote:
On Tue, Apr 17, 2001 at 13:03:44 +0200, Russell Coker wrote:
What is the name of the Alpha machine for Debian package development?
faure.d.o
http://db.debian.org/machines.cgi
Cheers,
M/
--
/~\ ASCII ribbon | i have
On Tue, Apr 17, 2001 at 13:26:56 +0200, Davide Puricelli wrote:
On Tue, Apr 17, 2001 at 01:09:14PM +0200, Michael Weber wrote:
On Tue, Apr 17, 2001 at 13:03:44 +0200, Russell Coker wrote:
What is the name of the Alpha machine for Debian package development?
faure.d.o
On Tue, 17 Apr 2001, Amaya wrote:
At work, we are making custom Debian packages and we need a special
versioning system so that apt does not try to replace our package with
a newer upstream one.
I would like to know if there's a standard way to proceed, apart from
setting the debian
OK, thanks for this good piece of advice.
On Fri, Apr 13, 2001 at 06:10:22PM -0700, Mike Markley wrote:
On Fri, Apr 13, 2001 at 04:30:15PM -0800, Britton [EMAIL PROTECTED] spake
forth:
It actually works with tcl 8.0, 8.1 and 8.2 you are right. So what about :
Depends: tcl8.0 |
Hi,
the upgrade-checklist says:
| - If your package has a daemon startup script in /etc/init.d/,
|and that script has parameters a system administrator may need,
|you need to modify the script to read values from a conffile
|placed in /etc/default/ directory. This
Hi,
the policy upgrading checklist says:
| - Files in /usr/share/doc may not be referenced by any
|program. If such files are needed, they must be placed in
|/usr/share/package-name/, and symbolic links created as required
|in /usr/share/doc/package-name/
Does any
On Tue, 17 Apr 2001, Marc Haber wrote:
I have a package where the init script contains most of the package's
functionality, and parses a free-format config file
/etc/$PACKAGE.conf. That file is not a shell script and can't be
directly sourced.
Can I keep that file as /etc/$PACKAGE, should I
On Tue, 17 Apr 2001, Marc Haber wrote:
the policy upgrading checklist says:
| - Files in /usr/share/doc may not be referenced by any
|program. If such files are needed, they must be placed in
|/usr/share/package-name/, and symbolic links created as required
|in
| - Files in /usr/share/doc may not be referenced by any
|program. If such files are needed, they must be placed in
|/usr/share/package-name/, and symbolic links created as required
|in /usr/share/doc/package-name/
Does any program include postinst scripts?
I'm playing with packaging, and lintian's complaining about no manpage for
a binary... but I have a myapp.1 manpage in both the debian/
control-directory and the root of the source directory..
I don't understand what I'm doing wrong :(
Any pointers would be greatly appreciated.. as
On Tue, 17 Apr 2001 [EMAIL PROTECTED] wrote:
I don't understand what I'm doing wrong :(
Is your man page actually being installed in the build directory?
hunts through the tmp directory
Actually I don't have a tmp directory, but one with the same name as the
package itself...
But no sign
On Tue, Apr 17, 2001 at 10:43:00PM +0200, Marc Haber wrote:
Hi,
the upgrade-checklist says:
The upgrading-checklist starts by saying:
The checklist below has been created to simplify the upgrading process of
old packages. Note, that this list is not `official.' If you have doubts
On Tue, Apr 17, 2001 at 06:17:15PM -0300, Henrique M Holschuh wrote:
Most definately yes. You better have a damn very good reason (e.g: the world
will end in a flood of Microsoft-made bovine crap with a mint smell because
their marketing tried to use hordes of purple dinossaurs with shovels to
On Tue, Apr 17, 2001 at 05:27:16PM -0400, [EMAIL PROTECTED] wrote:
Another camp said that this practice should be avoided. The rationale
was that administrators might do something more drastic to avoid
populating /usr/share/doc in the first place, like mounting it as a
read-only partition or
On Tue, Apr 17, 2001 at 11:23:43PM +0100, Gavin Hamill wrote:
Hullo! :)
I'm playing with packaging, and lintian's complaining about no manpage for
a binary... but I have a myapp.1 manpage in both the debian/
control-directory and the root of the source directory..
I don't understand what
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
On 17-Apr-2001 Davide Puricelli wrote:
On Tue, Apr 17, 2001 at 01:09:14PM +0200, Michael Weber wrote:
On Tue, Apr 17, 2001 at 13:03:44 +0200, Russell Coker wrote:
What is the name of the Alpha machine for Debian package development?
faure.d.o
41 matches
Mail list logo
