Hi,
The PTS shows cryptoloop-source to be orphaned, with a note that
someone is intending to take over. The note is quite old now and
references a bugreport which gives no further clues.
At the moment, I am maintaining enterprise kernel packages which
depend on this package, and I have made
Hello,
Thanks to the persons who have kindly answered my questions about the
/etc/dir.d/ problem.
At the beginning, the software did use the /usr/etc/dir.d
configuration directory, but then the packaging system would complain
that this is not a standard location. I used this location because
On Thu, Feb 12, 2004 at 09:19:16AM +0100, Juergen Strobel wrote:
The PTS shows cryptoloop-source to be orphaned, with a note that
someone is intending to take over. The note is quite old now and
references a bugreport which gives no further clues.
Have you attempted to contact Vincent Bernat
.20040212? This package would of course
not only fix the bug but also include new features of gdal and fix
some other bugs.
I would prefer to do the second option but I am not sure whether
the tarball will be accepted then.
Greetings,
Silke
[1] http://packages.qa.debian.org/g/gdal.html
[2
Hi Silke,
I would prefer to do the second option but I am not sure whether
the tarball will be accepted then.
Then i would go for this option. As long as you believe the new snapshot
is more useful and has less bugs than the old one, there is no reason to
keep the old one.
--jochen
--
To
On Thu, Feb 12, 2004 at 12:13:21AM +0100, Filippo Rusconi wrote:
Hello all,
in the software that I'm trying (gosh, that's not trivial...) to
package, some configuration files are due to go in /etc/polyxmass.d
Configuration files are configuration files, not else.
If you need to rewrite
Filippo Rusconi [EMAIL PROTECTED] schrieb:
Hello,
Thanks to the persons who have kindly answered my questions about the
/etc/dir.d/ problem.
At the beginning, the software did use the /usr/etc/dir.d
configuration directory, but then the packaging system would complain
that this is not a
On Wed, Feb 11, 2004 at 09:01:57PM +0100, Nico Golde wrote:
Hallo Frank,
* Frank Küster [EMAIL PROTECTED] [2004-02-11 20:07]:
every program must have a man page?
Policy, 12.1:
,
| Each program, utility, and function should have an associated manual
| page included in the
Sorry,
http://www.fast.sh/~vi64pa/
Ville Palo wrote:
Hi
I fixed one little bug (213654) and some lintian reported errors.
New debian package can be downloaded from http://www.fast.sh/~vi64pa/debian
I need sponsor for checking this packet and possibly
uploading it.
ville
--
To
Hi.
Ville Palo ([EMAIL PROTECTED]) wrote:
I fixed one little bug (213654) and some lintian reported errors.
Just a few thoughts
- The package presently in Debian is xcruise, not xcruiser.
- Declare your intend to adopt the package by appropriatly changing
the orphaning bug. Debian has policy on
Ok, now there is a .tar.gz.
It should contain all the necessary files.
Thomas Viehmann wrote:
Hi.
Ville Palo wrote:
http://www.fast.sh/~vi64pa/
The directory you pointed to does not contain the files necessary to
review your package.
Kind regards
Thomas
--
To UNSUBSCRIBE, email to [EMAIL
Ville Palo wrote:
Ok, now there is a .tar.gz.
It should contain all the necessary files.
The canonical way to do this (and thus probably the best way to get your
package looked at is to have *.orig.tar.gz, *.diff.gz, *.dsc and
possibly *.changes and *.deb in a directory.
Note also that you also
Ok, I just uploaded
*.orig.tar.gz
*.diff.gz
*.dsc
*.changes
*.deb
I haven't decclared my self maintainer yet,
Before I do that, i want to be sure the package is ok.
And thanks for helping me with this.
Thomas Viehmann wrote:
Ville Palo wrote:
Ok, now there is a .tar.gz.
It should contain all the
On 2004-02-12 Filippo Rusconi [EMAIL PROTECTED] wrote:
[...]
I effectively get the said file in
debian/polyxmassdata/etc/polyxmass.d/polyxmassdata.conf
telling me that the make install target has worked ok.
However, I also noticed that this file is referenced here:
Nico Golde wrote:
I am surprised because i saw programs with an automatic created debian
manpage or without a manpage.
If you find a program in Debian without a manpage, please file a bug
(severity normal) against the package that provides it.
--Joe
Hi,
The PTS shows cryptoloop-source to be orphaned, with a note that
someone is intending to take over. The note is quite old now and
references a bugreport which gives no further clues.
At the moment, I am maintaining enterprise kernel packages which
depend on this package, and I have made
Hello,
Thanks to the persons who have kindly answered my questions about the
/etc/dir.d/ problem.
At the beginning, the software did use the /usr/etc/dir.d
configuration directory, but then the packaging system would complain
that this is not a standard location. I used this location because
On Thu, Feb 12, 2004 at 09:19:16AM +0100, Juergen Strobel wrote:
The PTS shows cryptoloop-source to be orphaned, with a note that
someone is intending to take over. The note is quite old now and
references a bugreport which gives no further clues.
Have you attempted to contact Vincent Bernat
.20040212? This package would of course
not only fix the bug but also include new features of gdal and fix
some other bugs.
I would prefer to do the second option but I am not sure whether
the tarball will be accepted then.
Greetings,
Silke
[1] http://packages.qa.debian.org/g/gdal.html
[2
Hi Silke,
I would prefer to do the second option but I am not sure whether
the tarball will be accepted then.
Then i would go for this option. As long as you believe the new snapshot
is more useful and has less bugs than the old one, there is no reason to
keep the old one.
--jochen
On Thu, Feb 12, 2004 at 12:13:21AM +0100, Filippo Rusconi wrote:
Hello all,
in the software that I'm trying (gosh, that's not trivial...) to
package, some configuration files are due to go in /etc/polyxmass.d
Configuration files are configuration files, not else.
If you need to rewrite
Filippo Rusconi [EMAIL PROTECTED] schrieb:
Hello,
Thanks to the persons who have kindly answered my questions about the
/etc/dir.d/ problem.
At the beginning, the software did use the /usr/etc/dir.d
configuration directory, but then the packaging system would complain
that this is not a
On Wed, Feb 11, 2004 at 09:01:57PM +0100, Nico Golde wrote:
Hallo Frank,
* Frank Küster [EMAIL PROTECTED] [2004-02-11 20:07]:
every program must have a man page?
Policy, 12.1:
,
| Each program, utility, and function should have an associated manual
| page included in the
Hi
I fixed one little bug (213654) and some lintian reported errors.
New debian package can be downloaded from http://www.fast.sh/~vi64pa/debian
I need sponsor for checking this packet and possibly
uploading it.
ville
Sorry,
http://www.fast.sh/~vi64pa/
Ville Palo wrote:
Hi
I fixed one little bug (213654) and some lintian reported errors.
New debian package can be downloaded from http://www.fast.sh/~vi64pa/debian
I need sponsor for checking this packet and possibly
uploading it.
ville
Hi.
Ville Palo ([EMAIL PROTECTED]) wrote:
I fixed one little bug (213654) and some lintian reported errors.
Just a few thoughts
- The package presently in Debian is xcruise, not xcruiser.
- Declare your intend to adopt the package by appropriatly changing
the orphaning bug. Debian has policy on
Hi.
Ville Palo wrote:
http://www.fast.sh/~vi64pa/
The directory you pointed to does not contain the files necessary to
review your package.
Kind regards
Thomas
--
Thomas Viehmann, http://beamnet.de/tv/
pgphFsV0NXP1u.pgp
Description: PGP signature
Ok, now there is a .tar.gz.
It should contain all the necessary files.
Thomas Viehmann wrote:
Hi.
Ville Palo wrote:
http://www.fast.sh/~vi64pa/
The directory you pointed to does not contain the files necessary to
review your package.
Kind regards
Thomas
Hi Thomas
Thomas Viehmann wrote:
Hi.
Ville Palo ([EMAIL PROTECTED]) wrote:
I fixed one little bug (213654) and some lintian reported errors.
Just a few thoughts
- The package presently in Debian is xcruise, not xcruiser.
- Declare your intend to adopt the package by appropriatly changing
Ville Palo wrote:
Ok, now there is a .tar.gz.
It should contain all the necessary files.
The canonical way to do this (and thus probably the best way to get your
package looked at is to have *.orig.tar.gz, *.diff.gz, *.dsc and
possibly *.changes and *.deb in a directory.
Note also that you also
Ok, I just uploaded
*.orig.tar.gz
*.diff.gz
*.dsc
*.changes
*.deb
I haven't decclared my self maintainer yet,
Before I do that, i want to be sure the package is ok.
And thanks for helping me with this.
Thomas Viehmann wrote:
Ville Palo wrote:
Ok, now there is a .tar.gz.
It should contain
Hi!
There are some files in /etc which are actually data files representing
the state of the system. Like /etc/mtab, /etc/network/ifstate, or
/etc/lvmconf/* (it is not even a text file).
These files are written by programs in occasions one cannot with good
heart call configuration. Isn't it
On Thu, Feb 12, 2004 at 10:47:15PM +0100, Magos?nyi ?rp?d wrote:
There are some files in /etc which are actually data files representing
the state of the system. Like /etc/mtab, /etc/network/ifstate, or
/etc/lvmconf/* (it is not even a text file).
These files are written by programs in
On Thu, Feb 12, 2004 at 10:47:15PM +0100, Magosányi Árpád wrote:
There are some files in /etc which are actually data files representing
the state of the system. Like /etc/mtab, /etc/network/ifstate, or
/etc/lvmconf/* (it is not even a text file).
These files are written by programs in
34 matches
Mail list logo
