On Fri, Nov 28, 2003 at 01:22:36AM +0100, Max Vozeler wrote:
>
> What's not ready:
> - README.Debian hasnt been updated to reflect the switch to module-assistant
> - loop-aes-ciphers-source hasnt been converted to module-assistant
Done in just uploaded loop-aes-source 1.7e-14 and
loop-aes-ciph
On Fri, Nov 28, 2003 at 01:22:36AM +0100, Max Vozeler wrote:
>
> What's not ready:
> - README.Debian hasnt been updated to reflect the switch to module-assistant
> - loop-aes-ciphers-source hasnt been converted to module-assistant
Done in just uploaded loop-aes-source 1.7e-14 and
loop-aes-ciph
On Thu, Nov 27, 2003 at 04:12:12AM +0100, Peter Palfrader wrote:
> On Fri, 21 Nov 2003, Max Vozeler wrote:
> > > As for the util-linux incompatibility, a Replaces: is the first solution
> > > that comes to mind..
> >
> > Does that mean I could create a package, say loop-aes-utils, that
> > Replace
Hi Eduard,
thanks for suggesting module-assistant, I read up on it and re-wrote
debian/rules in loop-aes-source accordingly. This should address most
of the issues, details below. The modass override files are included
in loop-aes-utils 2.11z-5.
What's not ready:
- README.Debian hasnt been updat
On Thu, Nov 27, 2003 at 04:12:12AM +0100, Peter Palfrader wrote:
> On Fri, 21 Nov 2003, Max Vozeler wrote:
> > > As for the util-linux incompatibility, a Replaces: is the first solution
> > > that comes to mind..
> >
> > Does that mean I could create a package, say loop-aes-utils, that
> > Replace
Hi Eduard,
thanks for suggesting module-assistant, I read up on it and re-wrote
debian/rules in loop-aes-source accordingly. This should address most
of the issues, details below. The modass override files are included
in loop-aes-utils 2.11z-5.
What's not ready:
- README.Debian hasnt been updat
Hello all,
I have to move a config file, and I am not sure of the best way of
handling it, so I wanted to ask for opinions.
The problem is that I am currently shipping an /etc/default/$package,
which needs to now become /etc/$package.conf - it's not a shell script,
but more of a hacked together c
Hello all,
I have to move a config file, and I am not sure of the best way of
handling it, so I wanted to ask for opinions.
The problem is that I am currently shipping an /etc/default/$package,
which needs to now become /etc/$package.conf - it's not a shell script,
but more of a hacked together c
On Fri, 21 Nov 2003, Max Vozeler wrote:
> On Thu, Nov 20, 2003 at 08:56:58PM -0800, Joshua Kwan wrote:
> > On Fri, Nov 21, 2003 at 05:54:39AM +0100, Max Vozeler wrote:
> > > Additional ciphers (Blowfish, Twofish and Serpent) can be used if the
> > > loop-aes-ciphers-source package is installed a
On Fri, 21 Nov 2003, Max Vozeler wrote:
> On Thu, Nov 20, 2003 at 08:56:58PM -0800, Joshua Kwan wrote:
> > On Fri, Nov 21, 2003 at 05:54:39AM +0100, Max Vozeler wrote:
> > > Additional ciphers (Blowfish, Twofish and Serpent) can be used if the
> > > loop-aes-ciphers-source package is installed a
Hi all,
I've made some changes to the libogg-vorbis-header-perl package. Please check
it again if you had earlier.
It now doesn't remove the test.ogg.bak file present in upstream; rather
there's a new rule in debian/rules which teaches dh_clean not to remove it.
The script that used this file
Hi all,
I've made some changes to the libogg-vorbis-header-perl package. Please check
it again if you had earlier.
It now doesn't remove the test.ogg.bak file present in upstream; rather
there's a new rule in debian/rules which teaches dh_clean not to remove it.
The script that used this file
#include
* Max Vozeler [Wed, Nov 26 2003, 12:31:16AM]:
> > mv /usr/src/modules/loop-aes/debian/tmp/lib/modules/2.4.23 \
> > /usr/src/modules/loop-aes/debian/tmp/lib/modules/2.4.23-rc3
> > mv: cannot stat `/usr/src/modules/loop-aes/debian/tmp/lib/modules/2.4.23':
> > No such file or directory
>
#include
* Max Vozeler [Wed, Nov 26 2003, 12:31:16AM]:
> > mv /usr/src/modules/loop-aes/debian/tmp/lib/modules/2.4.23 \
> > /usr/src/modules/loop-aes/debian/tmp/lib/modules/2.4.23-rc3
> > mv: cannot stat `/usr/src/modules/loop-aes/debian/tmp/lib/modules/2.4.23': No such
> > file or directory
>
Well that interface is fully taken care of through the new_fax function.
Please have a look at the docs for exact workings. It normally calls a
script called new_fax, check exact location in your source files (it is
a compile time option) or go to the dir where mgetty resides, and then
type "string
Well that interface is fully taken care of through the new_fax function.
Please have a look at the docs for exact workings. It normally calls a
script called new_fax, check exact location in your source files (it is
a compile time option) or go to the dir where mgetty resides, and then
type "string
16 matches
Mail list logo
