Re: help in chages necessary for rules file( creating .deb packages)

2005-01-12 Thread Chirag Kantharia
On Wed, Jan 12, 2005 at 02:23:25AM -0800, TIFR students wrote:
|  We are trying to make .deb packages using
| dh_make...it works fine..it creates a template for
| rules filesuppose a source file is a simple c
| program(hello world) what changes should we make in
| the rules file so that the dpkg-buildpackage works
| properly

You could probably lookup some example rules files from a debian
package. Do a:
$ apt-get source package-name

Do that, for some package, which you're familiar with. Something, you
may have compiled and install from source. You, would find easy to
corelate.

Regards,

-- 
Chirag Kantharia, puggy.symonds.net/~chyrag/



signature.asc
Description: Digital signature


Re: How to -- debian distribution CD...

2005-01-03 Thread Chirag Kantharia
On Mon, Jan 03, 2005 at 01:01:35AM -0800, TIFR students wrote:
| We would like to know if there is any way by which we can create an debian 
distro ISO which contains packages of our choice.

Look at www.knoppix.org for an example of debian based distribution, and
search for customizing knoppix on google, for HOWTO on remastering the
distribution.

Regards,

-- 
Chirag Kantharia, puggy.symonds.net/~chyrag/



signature.asc
Description: Digital signature


Re: Packaging kernel patches

2004-10-28 Thread Chirag Kantharia
On Wed, Oct 27, 2004 at 02:28:48PM +0300, Eugeniy Meshcheryakov wrote:
| 26.10.2004 ?? 12:07 +0530 Chirag Kantharia ??(-):
|  So, they don't have a .orig.tar.gz which I can use. Though debuild
| So make it. Put patches into tarball. There are many packages for that
| there is no upstream tarballs (mozilla* locales for example, other
| kernel patches probably too).

Thanks! Will do.

-- 
Chirag Kantharia, puggy.symonds.net/~chyrag/



signature.asc
Description: Digital signature


Re: Packaging kernel patches

2004-10-27 Thread Chirag Kantharia
On Wed, Oct 27, 2004 at 02:28:48PM +0300, Eugeniy Meshcheryakov wrote:
| 26.10.2004 ?? 12:07 +0530 Chirag Kantharia ??(-):
|  So, they don't have a .orig.tar.gz which I can use. Though debuild
| So make it. Put patches into tarball. There are many packages for that
| there is no upstream tarballs (mozilla* locales for example, other
| kernel patches probably too).

Thanks! Will do.

-- 
Chirag Kantharia, puggy.symonds.net/~chyrag/



signature.asc
Description: Digital signature


Packaging kernel patches

2004-10-26 Thread Chirag Kantharia
Hello,

Is there a doc/URL, which serves as guide for packaging kernel patches?
If so, I would appreciate a pointer.

I'm trying to package support for netdump (netconsole + dumping machine
state + memory dump over network). RedHat kernels have developed this
capability (and which is not available in vanilla kernels). They do not
have a project page, for publishing the netdump patches, and I have
obtained the netdump patch, from the SRPMs for Fedora Core 2 kernel
(http://download.fedora.redhat.com/pub/fedora/linux/core/development/SRPMS/).
So, they don't have a .orig.tar.gz which I can use. Though debuild
prints a warning (W: kernel-patch-netdump source:
native-package-with-dash-version), it exits with 0 return code.

Is that okay?

Regards,

-- 
Chirag Kantharia, puggy.symonds.net/~chyrag/



signature.asc
Description: Digital signature


Packaging kernel patches

2004-10-26 Thread Chirag Kantharia
Hello,

Is there a doc/URL, which serves as guide for packaging kernel patches?
If so, I would appreciate a pointer.

I'm trying to package support for netdump (netconsole + dumping machine
state + memory dump over network). RedHat kernels have developed this
capability (and which is not available in vanilla kernels). They do not
have a project page, for publishing the netdump patches, and I have
obtained the netdump patch, from the SRPMs for Fedora Core 2 kernel
(http://download.fedora.redhat.com/pub/fedora/linux/core/development/SRPMS/).
So, they don't have a .orig.tar.gz which I can use. Though debuild
prints a warning (W: kernel-patch-netdump source:
native-package-with-dash-version), it exits with 0 return code.

Is that okay?

Regards,

-- 
Chirag Kantharia, puggy.symonds.net/~chyrag/



signature.asc
Description: Digital signature


Debian vs RedHat init script

2004-07-28 Thread Chirag Kantharia
Hi!

I'm packaging netdump for Debian. The package comes with it's own
initscripts, which are RedHat specific. I had used the Debian template
for initscript, in my first attempt to package netdump. Using the
RedHat version of the initscript (maintained upstream), I edited
Debian template, to match the functionality provided by the RedHat
initscript.

Because of this, I have, now, two copies of initscripts (RedHat and
Debian), which my sponsor, thinks, is redundant. The initscripts
differ quite a bit, and I am not sure, if one format can be converted
to another, using simple commands (and thus, be able to maintain just
one copy).

How do the other packages, get around this? I would be glad, if you
would point me to specific packages, that have a (upstream maintained)
RedHat specific initscript within the package source.

Regards,

-- 
Chirag Kantharia, [EMAIL PROTECTED]


pgpfZVSDC0yBB.pgp
Description: PGP signature


Re: Debian vs RedHat init script

2004-07-28 Thread Chirag Kantharia
On Wed, Jul 28, 2004 at 11:57:02AM +0200, Adrian 'Dagurashibanipal' von Bidder 
wrote:
| Current prerelease of the LSB 2.0 spec has something on 
| http://www.linuxbase.org/spec/booksets/LSB-Core/LSB-Core/iniscrptfunc.html, 
| but I'd have to read and understand it really well, and also look at 
| how much of it Debian offers (with or without lsb package). Haven't 
| looked at the 1.3 spec.

Hi Adrian

Thanks for the url. I'm not sure how that solves my problem. As I
understand you, I need to convince the upstream maintainer to switch
to LSB style initscript. I can try doing that. The initscript has some
weird function, which might be optionally used by the user, to
exchange ssh keys, so that the dump is copied to the server using ssh
(scp). The function has no place in the initscript, but RedHat prefers
to do it, that way. I've placed that key exchange, as part of
postinst.

If, for some reason, the upstream maintainer doesn't wish to modify
the initscript, to adhere to LSB recommendations, then, do I have an
alternative way to resort to?

Regards,

-- 
Chirag Kantharia, [EMAIL PROTECTED]



pgpBvT1W3m30m.pgp
Description: PGP signature


Debian vs RedHat init script

2004-07-28 Thread Chirag Kantharia
Hi!

I'm packaging netdump for Debian. The package comes with it's own
initscripts, which are RedHat specific. I had used the Debian template
for initscript, in my first attempt to package netdump. Using the
RedHat version of the initscript (maintained upstream), I edited
Debian template, to match the functionality provided by the RedHat
initscript.

Because of this, I have, now, two copies of initscripts (RedHat and
Debian), which my sponsor, thinks, is redundant. The initscripts
differ quite a bit, and I am not sure, if one format can be converted
to another, using simple commands (and thus, be able to maintain just
one copy).

How do the other packages, get around this? I would be glad, if you
would point me to specific packages, that have a (upstream maintained)
RedHat specific initscript within the package source.

Regards,

-- 
Chirag Kantharia, [EMAIL PROTECTED]


pgpXKaiEDX1n6.pgp
Description: PGP signature


Re: RFS: netdump -- Dump kernel crash information over the network

2004-07-14 Thread Chirag Kantharia
[Third attempt for seeking a sponsor]

Hi!

I've uploaded netdump package to mentors.debian.net and am seeking for
a sponsor for this package.

The netdump client sets up the kernel to send crash dumps and/or
console messages as syslog packets to a remote system.

The netdump server listens to the network for crashed kernels to
contact it and then writes the oops log and a memory dump to
/var/crash before asking the crashed machine to reboot.

Netdump relies on CONFIG_NETCONSOLE=m set in the kernel configuration,
which is not present in 2.4 series Debian kernels, but is present in
2.6 series Debian kernels. So the package will not work with 2.4
Debian kernels.

More information about netdump can be got from:
http://www.redhat.com/support/wpapers/redhat/netdump/

I have got permission from netdump's current maintainer Jeff Moyer
[EMAIL PROTECTED] to include it in the Debian, and who is happy to
see its inclusion.

Regards,

-- 
Chirag Kantharia, [EMAIL PROTECTED]


pgpGEeRc01k0x.pgp
Description: PGP signature


Re: RFS: netdump -- Dump kernel crash information over the network

2004-07-14 Thread Chirag Kantharia
[Third attempt for seeking a sponsor]

Hi!

I've uploaded netdump package to mentors.debian.net and am seeking for
a sponsor for this package.

The netdump client sets up the kernel to send crash dumps and/or
console messages as syslog packets to a remote system.

The netdump server listens to the network for crashed kernels to
contact it and then writes the oops log and a memory dump to
/var/crash before asking the crashed machine to reboot.

Netdump relies on CONFIG_NETCONSOLE=m set in the kernel configuration,
which is not present in 2.4 series Debian kernels, but is present in
2.6 series Debian kernels. So the package will not work with 2.4
Debian kernels.

More information about netdump can be got from:
http://www.redhat.com/support/wpapers/redhat/netdump/

I have got permission from netdump's current maintainer Jeff Moyer
[EMAIL PROTECTED] to include it in the Debian, and who is happy to
see its inclusion.

Regards,

-- 
Chirag Kantharia, [EMAIL PROTECTED]


pgpT9BSTGcZdn.pgp
Description: PGP signature


RFS: netdump -- Dump kernel crash information over the network

2004-06-28 Thread Chirag Kantharia
[Second attempt for seeking a sponsor]

Hi!

I've uploaded netdump package to mentors.debian.net and am seeking for
a sponsor for this package.

The netdump client sets up the kernel to send crash dumps and/or
console messages as syslog packets to a remote system.

The netdump server listens to the network for crashed kernels to
contact it and then writes the oops log and a memory dump to
/var/crash before asking the crashed machine to reboot.

Netdump relies on CONFIG_NETCONSOLE=m set in the kernel configuration,
which is not present in 2.4 series Debian kernels, but is present in
2.6 series Debian kernels. So the package will not work with 2.4
Debian kernels.

More information about netdump can be got from:
http://www.redhat.com/support/wpapers/redhat/netdump/

I have got permission from netdump's current maintainer Jeff Moyer
[EMAIL PROTECTED] to include it in the Debian, and who is happy to
see its inclusion.

Regards,

-- 
Chirag Kantharia, [EMAIL PROTECTED]


pgpJUpmDvn5ea.pgp
Description: PGP signature


RFS: netdump -- Dump kernel crash information over the network

2004-06-08 Thread Chirag Kantharia
Hi!

I've just uploaded netdump package to mentors.debian.net and now am
seeking for a sponsor for this package.

The netdump client sets up the kernel to send crash dumps and/or
console messages as syslog packets to a remote system.

The netdump server listens to the network for crashed kernels to
contact it and then writes the oops log and a memory dump to
/var/crash before asking the crashed machine to reboot.

Netdump relies on CONFIG_NETCONSOLE=m set in the kernel configuration,
which is not present in 2.4 series Debian kernels, but is present in
2.6 series Debian kernels. So the package will not work with 2.4
Debian kernels.

Netdump was developed at RedHat, and so, the source code is available
only in form of an .srpm. How does one go about the debian/watch file,
in such cases?

More information about netdump can be got from:
http://www.redhat.com/support/wpapers/redhat/netdump/

Regards,

-- 
Chirag Kantharia, [EMAIL PROTECTED]


pgpuhqHWKUNsR.pgp
Description: PGP signature


RFS: netdump -- Dump kernel crash information over the network

2004-06-08 Thread Chirag Kantharia
Hi!

I've just uploaded netdump package to mentors.debian.net and now am
seeking for a sponsor for this package.

The netdump client sets up the kernel to send crash dumps and/or
console messages as syslog packets to a remote system.

The netdump server listens to the network for crashed kernels to
contact it and then writes the oops log and a memory dump to
/var/crash before asking the crashed machine to reboot.

Netdump relies on CONFIG_NETCONSOLE=m set in the kernel configuration,
which is not present in 2.4 series Debian kernels, but is present in
2.6 series Debian kernels. So the package will not work with 2.4
Debian kernels.

Netdump was developed at RedHat, and so, the source code is available
only in form of an .srpm. How does one go about the debian/watch file,
in such cases?

More information about netdump can be got from:
http://www.redhat.com/support/wpapers/redhat/netdump/

Regards,

-- 
Chirag Kantharia, [EMAIL PROTECTED]


pgpiFJXlneCf4.pgp
Description: PGP signature