Barry deFreese [EMAIL PROTECTED] writes:
I don't learn a great deal from reading unfortunately.
I think we're alike here. But at least for me some texts were great
inspiration. While reading The Algorithmic Beauty of Plants I was
always itching to implement what was described.
I am pretty
Barry deFreese [EMAIL PROTECTED] writes:
I don't learn a great deal from reading unfortunately.
I think we're alike here. But at least for me some texts were great
inspiration. While reading The Algorithmic Beauty of Plants I was
always itching to implement what was described.
I am pretty
Johannes Rohr [EMAIL PROTECTED] writes:
Well, I don't know. Until today I've contacted them three times and
there as been no response except for an acknowledgement of receipt.
Therefore I don't think they'd turn out to be more responsive if I came
begging for money...
It's actually called
Johannes Rohr [EMAIL PROTECTED] writes:
Well, I don't know. Until today I've contacted them three times and
there as been no response except for an acknowledgement of receipt.
Therefore I don't think they'd turn out to be more responsive if I came
begging for money...
It's actually called
Johannes Rohr [EMAIL PROTECTED] writes:
Is using the install(1) command recommended, or is it sufficient to use
cp(1)?
cp excels in bulk handling while install can set owner, permissions,
etc. Use the tool which fits your problem best. All other things being
equal, use the one with the most
Johannes Rohr [EMAIL PROTECTED] writes:
[...] I am examining if it is possible to replace
the installer package with a package that contains the actual
software. So I'm not planning to make more non-free software available
to Debian users, but simply to replace an existing package by
Johannes Rohr [EMAIL PROTECTED] writes:
Is using the install(1) command recommended, or is it sufficient to use
cp(1)?
cp excels in bulk handling while install can set owner, permissions,
etc. Use the tool which fits your problem best. All other things being
equal, use the one with the most
Johannes Rohr [EMAIL PROTECTED] writes:
[...] I am examining if it is possible to replace
the installer package with a package that contains the actual
software. So I'm not planning to make more non-free software available
to Debian users, but simply to replace an existing package by
Matt Zimmerman [EMAIL PROTECTED] writes:
If you're developing software FOR Debian (e.g., packaging), run unstable (or
an unstable chroot).
I encourage developers of Debian packages to spend as much time as
possible on unstable (inside the chroot, or on a plain unstable
installation). We as a
Frank Gevaerts [EMAIL PROTECTED] writes:
AFAIK, non-free only needs permission to redistribute.
Yes. For examples of disqualified-from-non-free software look at the
various installers. Newer Sun JDKs also haven't made it into non-free
(don't remember why).
We also sometimes disqualify software
Matt Zimmerman [EMAIL PROTECTED] writes:
If you're developing software FOR Debian (e.g., packaging), run unstable (or
an unstable chroot).
I encourage developers of Debian packages to spend as much time as
possible on unstable (inside the chroot, or on a plain unstable
installation). We as a
Frank Gevaerts [EMAIL PROTECTED] writes:
AFAIK, non-free only needs permission to redistribute.
Yes. For examples of disqualified-from-non-free software look at the
various installers. Newer Sun JDKs also haven't made it into non-free
(don't remember why).
We also sometimes disqualify software
Ivo Marino [EMAIL PROTECTED] writes:
If anyone on this list is searching for a maintainer for a package
related to Perl or PHP I'm available as contributor to the Debian
project.
You know about wnpp? Take a look at
URL:http://www.debian.org/devel/wnpp/work_needing ... a quick scan
showed a
Karolina Lindqvist [EMAIL PROTECTED] writes:
That is the individual solution when the trouble is there. But is
there no way to make the package so that the trouble does not occur,
or at least is warned for?
If random files go missing on your system you have bigger problems.
I.e. if
Frank Gevaerts [EMAIL PROTECTED] writes:
I'm trying to package foobillard (http://foobillard.sunsite.dk/) for
debian.
Looks nice.
a foobillard goes to non-free, which would be a pity.
And people who have ttf-larabie-* installed will have some fonts
double, which is also bad.
b The
Juan Manuel García Molina [EMAIL PROTECTED] writes:
[...] , so 12 o'clock noon would be equivalent to @500 Swatch beats.
[...]
A day in the internet time begins at midnight BMT (@000) in Central Europe
wintertime.
These sentences contradict each other; you may want to rewrite the
first
Ah, seems you've implemented your option (d) already. Good.
Frank Gevaerts [EMAIL PROTECTED] writes:
Depends: ttf-freefonts | ttf-larabie-straight, ttf-freefonts |
ttf-larabie-deco
That is indeed the same thing. This means my original requirement is not
entirely what I want either.
Henrique de Moraes Holschuh [EMAIL PROTECTED] writes:
May I suggest that dh_installinit adds 'debconf (= 1.2.9)' to
${misc:Depends}?
No. That's a build-dependency, you know. There is no runtime dependency.
Of course debconf (dpkg-reconfigure) is needed at run time. Are you
confusing it
Ross Boylan [EMAIL PROTECTED] writes:
What is the debian way to do this when I'm building packages from
source?
Take a look at pentium-builder.
And, using kernel-package, how do I build kernels and modules
appropriately?
Well, as usual. What problems do you have in mind?
Should I build
[EMAIL PROTECTED] (Bob Proulx) writes:
May I voice an opinion against a gratuitous message saying that the
behavior has changed but without real useful value? Those darn
click-throughs are a large part of the complaints against debian
packages during an install. May I suggest that if at all
Henrique de Moraes Holschuh [EMAIL PROTECTED] writes:
May I suggest that dh_installinit adds 'debconf (= 1.2.9)' to
${misc:Depends}?
No. That's a build-dependency, you know. There is no runtime dependency.
Of course debconf (dpkg-reconfigure) is needed at run time. Are you
confusing it
Ross Boylan [EMAIL PROTECTED] writes:
What is the debian way to do this when I'm building packages from
source?
Take a look at pentium-builder.
And, using kernel-package, how do I build kernels and modules
appropriately?
Well, as usual. What problems do you have in mind?
Should I build
[EMAIL PROTECTED] (Bob Proulx) writes:
May I voice an opinion against a gratuitous message saying that the
behavior has changed but without real useful value? Those darn
click-throughs are a large part of the complaints against debian
packages during an install. May I suggest that if at all
Sean 'Shaleh' Perry [EMAIL PROTECTED] writes:
can't see anything other than a slightly different layout and the
word 'porn' in its name.
... which will make it easier to find for some people. Of course we
could help these as well by including porn in gqview's description,
or make gqview
Sean 'Shaleh' Perry [EMAIL PROTECTED] writes:
can't see anything other than a slightly different layout and the
word 'porn' in its name.
... which will make it easier to find for some people. Of course we
could help these as well by including porn in gqview's description,
or make gqview
Colin Watson [EMAIL PROTECTED] writes:
it lets you unpack the file as is without having to worry about
overwriting the debianized version.
Use a temporary directory. You should get into the habit of doing this
when unpacking random tarballs anyway.
Or use aunpack (from the atool
Colin Watson [EMAIL PROTECTED] writes:
it lets you unpack the file as is without having to worry about
overwriting the debianized version.
Use a temporary directory. You should get into the habit of doing this
when unpacking random tarballs anyway.
Or use aunpack (from the atool
Marc Haber [EMAIL PROTECTED] writes:
Inform the user about the change, and optionally provide a conversion
script.
OK. So I will be shipping a package that will break existing and
working setups, while handling this automatically is perfectly
possible.
What about upgrading inform the user
Marc Haber [EMAIL PROTECTED] writes:
Inform the user about the change, and optionally provide a conversion
script.
OK. So I will be shipping a package that will break existing and
working setups, while handling this automatically is perfectly
possible.
What about upgrading inform the user
Sven Luther [EMAIL PROTECTED] writes:
All packages have to be buildable with the current release. And this
does not include non-us if you happen to be in the us.
Nope, you may freely download from non-us.debian.org, even if you're
currently in the USofA.
--
Robbe
signature.ng
Description:
Sven Luther [EMAIL PROTECTED] writes:
All packages have to be buildable with the current release. And this
does not include non-us if you happen to be in the us.
Nope, you may freely download from non-us.debian.org, even if you're
currently in the USofA.
--
Robbe
signature.ng
Description:
Marco Kuhlmann [EMAIL PROTECTED] writes:
* Geert Stappers [EMAIL PROTECTED] (2002-09-12 13:48:43 +0200):
Could you tell us why you want prevent free software being
ported to certain architectures?
Sorry, perhaps I should reformulate my question: How do I tell
porters not to try to
Stephen Peters [EMAIL PROTECTED] writes:
One workaround I can think of for this case is to provide a pair of
stub classes that would merely implement the interface that the
package needs to compile, and add a note to the README.Debian stating
that the user will have to download their own
Stephen Peters [EMAIL PROTECTED] writes:
One workaround I can think of for this case is to provide a pair of
stub classes that would merely implement the interface that the
package needs to compile, and add a note to the README.Debian stating
that the user will have to download their own copy
Edd Dumbill [EMAIL PROTECTED] writes:
My current thinking is to make two packages, bluez-bluefw and
bluez-bluefw-firmware. The latter would have to go into non-free, and
the former into contrib as it requires a non-free package to function.
Does this sound OK?
It is most correct, yes.
Marc Leeman [EMAIL PROTECTED] writes:
deb http://lesbos.esat.kuleuven.ac.be/~mleeman/debian unstable/
deb-src http://lesbos.esat.kuleuven.ac.be/~mleeman/debian unstable/
Your chances to find a sponsor are better if you tell us what the
ogmtools do. Pasting your package description here would
Marco Kuhlmann [EMAIL PROTECTED] writes:
wimsey:~# apt-get --purge remove mozart mozart-contrib mozart-doc-html
[...]
I guess there is some problem with the dependencies here, but I
am a little lost in finding exactly what it is. Can you help me?
Could you add -s to that call and see how
Edd Dumbill [EMAIL PROTECTED] writes:
My current thinking is to make two packages, bluez-bluefw and
bluez-bluefw-firmware. The latter would have to go into non-free, and
the former into contrib as it requires a non-free package to function.
Does this sound OK?
It is most correct, yes.
Marc Leeman [EMAIL PROTECTED] writes:
deb http://lesbos.esat.kuleuven.ac.be/~mleeman/debian unstable/
deb-src http://lesbos.esat.kuleuven.ac.be/~mleeman/debian unstable/
Your chances to find a sponsor are better if you tell us what the
ogmtools do. Pasting your package description here would
Cédric Delfosse [EMAIL PROTECTED] writes:
% LANG=C debsign
signfile ../darkstat_2.1-1.dsc Cédric Delfosse [EMAIL PROTECTED]
gpg: skipped `Cédric Delfosse [EMAIL PROTECTED]': secret key not
available
gpg: [stdin]: clearsign failed: secret key not available
/usr/bin/debsign: GPG error
Marc Haber [EMAIL PROTECTED] writes:
Is there a recommendation to make one's package better behaved? Using
start-stop-daemon --oknodo does not seem to be the correct way since
this turns off error detection completely.
Why do you think so? My man page says:
-o|--oknodo
Bas Zoetekouw [EMAIL PROTECTED] writes:
In my packages, I copy the new config.{sub,guess} over the old ones
in one of the build targets, and put a backup of the original ones
back in the clean target.
You'll have to build-depend on autotools-dev, though ...
--
Robbe
signature.ng
Cédric Delfosse [EMAIL PROTECTED] writes:
% LANG=C debsign
signfile ../darkstat_2.1-1.dsc Cédric Delfosse [EMAIL PROTECTED]
gpg: skipped `Cédric Delfosse [EMAIL PROTECTED]': secret key not
available
gpg: [stdin]: clearsign failed: secret key not available
/usr/bin/debsign: GPG error
Marc Haber [EMAIL PROTECTED] writes:
Is there a recommendation to make one's package better behaved? Using
start-stop-daemon --oknodo does not seem to be the correct way since
this turns off error detection completely.
Why do you think so? My man page says:
-o|--oknodo
Bas Zoetekouw [EMAIL PROTECTED] writes:
In my packages, I copy the new config.{sub,guess} over the old ones
in one of the build targets, and put a backup of the original ones
back in the clean target.
You'll have to build-depend on autotools-dev, though ...
--
Robbe
signature.ng
Jens Peter Secher [EMAIL PROTECTED] writes:
Summary: How do one make pbuilder, debarchiver, quintuple-agent work
together?
[...]
Nice!
Second, I am required to type my passphrase four times. Is there a
way to make quintuple-agent work with debuild and dpkg-buildpakage
(through pbuilder)?
Jens Peter Secher [EMAIL PROTECTED] writes:
Summary: How do one make pbuilder, debarchiver, quintuple-agent work
together?
[...]
Nice!
Second, I am required to type my passphrase four times. Is there a
way to make quintuple-agent work with debuild and dpkg-buildpakage
(through pbuilder)?
Geert Stappers [EMAIL PROTECTED] writes:
When the cause of the buildproblem is a missing library,
then the problem will be fixed by adding the lib.
You're correct that this is usually no reason for frobbing the
Architecture field. (Build-)Depends fully suffice, and have the bonus
of making a
Holger Kubiak [EMAIL PROTECTED] writes:
Is it possible that lintian searches this entrys (in the sense: is
it possible to change lintian).
It is. But db_* commands return status for a reason, so people may
want to omit the || true and actually do something with the exit
codes. lintian has no
Geert Stappers [EMAIL PROTECTED] writes:
When the cause of the buildproblem is a missing library,
then the problem will be fixed by adding the lib.
You're correct that this is usually no reason for frobbing the
Architecture field. (Build-)Depends fully suffice, and have the bonus
of making a
David Given [EMAIL PROTECTED] writes:
Anyone interested in sponsoring them? I've managed to tick off
everything else on the checklist...
You didn't tick me off, yet. IOW, I'm willing to sponsor you, if
nobody has beat me to it. Please mail me privately in this case.
--
Robbe
signature.ng
David Given [EMAIL PROTECTED] writes:
Anyone interested in sponsoring them? I've managed to tick off
everything else on the checklist...
You didn't tick me off, yet. IOW, I'm willing to sponsor you, if
nobody has beat me to it. Please mail me privately in this case.
--
Robbe
signature.ng
Hamish Moffatt [EMAIL PROTECTED] writes:
Does your package check spells or spelling?
I think your package would be better described as a spelling-checker
add-on rather than a spell-checking addon, unless it really checks
spells.
The American Heritage Dictionary of the English Language, 4th
Marc Leeman [EMAIL PROTECTED] writes:
OK, contrib/x11 it is then, ...
But is this a good location? Can it be in contrib, since it is not
possible to package (binary) versions of those packages:
[...]
contrib is for packages that depend on other stuff outside of Debian.
It doesn't matter
Marc Leeman [EMAIL PROTECTED] writes:
OK, contrib/x11 it is then, ...
But is this a good location? Can it be in contrib, since it is not
possible to package (binary) versions of those packages:
[...]
contrib is for packages that depend on other stuff outside of Debian.
It doesn't matter
Jens Schmalzing [EMAIL PROTECTED] writes:
Since my main machine is an Apple Powerbook, this means that the
package can go into main, because the only packages providing
java-virtual-machine /on powerpc/ are kaffe and gij-3.0, which are
both free.
*Iff* it works with kaffe, yes.
This is
Alexandre [EMAIL PROTECTED] writes:
* having pyro and host conflict (but this annoys me since I need both
packages on my machine)
Note that bind9-host also provides the host binary, but without the
mx, ns, soa, etc. convenience symlinks (at least I guess they
are symlinks).
* renaming
Richard A Nelson [EMAIL PROTECTED] writes:
Does sbuild not properly support build-depends-indep ?
It need not, as it does not concern itself with the indep part.
Should binary not call binary-arch *and* binary-indep ?
It should too. The real problem at hand is not the binary* targets,
but
Stefano Zacchiroli [EMAIL PROTECTED] writes:
I'm wondering why packages libshell-ocaml and libshell-ocaml-dev (two
binaries packages from the same source package) are not in testing
despite that they were successfully built on all architectures and that
there is no excuse for them.
#
Marc Haber [EMAIL PROTECTED] writes:
Since you're using libtool,
Am I? Libtool is not installed in the chroot where I am building the
package. This suspiciously looks like somebody invented his own broken
stuff :-(
No, libtool scripts, like configure, usually come with the source. You
Marc Haber [EMAIL PROTECTED] writes:
W: atm-tools: binary-or-shlib-defines-rpath ./usr/sbin/mpcd
/home/haber/devel/linux-atm-2.4.0/debian/atm-tools/usr/lib
Note that this rpath, apart from being superflous, is also broken as
it points to a directory that will be nonexistent except on your
Junichi Uekawa [EMAIL PROTECTED] writes:
I'd rather have shared libs with some Debian-specific
versioning than unversioned static library because it is easier to track
bugs on them, and fix them.
The problem is that if upstream gets real later and uses proper
versioning that may clash with
Jérôme Marant [EMAIL PROTECTED] writes:
You don't seem to have understood what cooperative work
means.
In another mail, Jérôme Marant [EMAIL PROTECTED] writes:
So what? The one who uploads the first wins.
[...]
Obtaining permission is just a matter of courtesy.
Pot. Kettle.
Marcelo Leal [EMAIL PROTECTED] writes:
I'm brazilian... do not speak english very well, but i'm a very good
reader. My books about linux and FreeBSD are in english, all ones. And,
maybe, can i help in the translate job.
Debian specific translation tasks include the translation of package
Jérôme Marant [EMAIL PROTECTED] writes:
You don't seem to have understood what cooperative work
means.
In another mail, Jérôme Marant [EMAIL PROTECTED] writes:
So what? The one who uploads the first wins.
[...]
Obtaining permission is just a matter of courtesy.
Pot. Kettle.
Marcelo Leal [EMAIL PROTECTED] writes:
I'm brazilian... do not speak english very well, but i'm a very good
reader. My books about linux and FreeBSD are in english, all ones. And,
maybe, can i help in the translate job.
Debian specific translation tasks include the translation of package
Oohara Yuuma [EMAIL PROTECTED] writes:
* gpgp should be in main (gpgp contains no crypto code --- all crypto things
are done by calling gpg)
So gpgp should be where gnupg is. Today that's main, you're right on that.
I admit seahorse is better than gpgp, but gpgp seems rather popular
David Caldwell [EMAIL PROTECTED] writes:
snipping a good suggestion
Even better than what I just said above is to make a source dir and 2
build dirs, like so:
project_base/source-tree
project_base/build1
project_base/build2
project_base/debian
That way the source files are nicely
Oohara Yuuma [EMAIL PROTECTED] writes:
* gpgp should be in main (gpgp contains no crypto code --- all crypto things
are done by calling gpg)
So gpgp should be where gnupg is. Today that's main, you're right on that.
I admit seahorse is better than gpgp, but gpgp seems rather popular
David Caldwell [EMAIL PROTECTED] writes:
snipping a good suggestion
Even better than what I just said above is to make a source dir and 2
build dirs, like so:
project_base/source-tree
project_base/build1
project_base/build2
project_base/debian
That way the source files are nicely
Oohara Yuuma [EMAIL PROTECTED] writes:
Subscribe to (high volume) [EMAIL PROTECTED] .
Some developers explain why the urgency is medium or high
in the changelog.
URL:http://www.google.com/search?q=debian-devel-changes+urgency+medium+site%3Alists.debian.org
might help discovering such
Oohara Yuuma [EMAIL PROTECTED] writes:
Subscribe to (high volume) debian-devel-changes@lists.debian.org .
Some developers explain why the urgency is medium or high
in the changelog.
URL:http://www.google.com/search?q=debian-devel-changes+urgency+medium+site%3Alists.debian.org
might help
martin f krafft [EMAIL PROTECTED] writes:
i don't think users run it, so
/usr/lib/tempest4eliza/mksong.sh
If it is really a shell script, /usr/share/... is more correct.
--
Robbe
signature.ng
Description: PGP signature
to 0.4.3+20020409-1)
* Maintainer: Robert Bihlmeyer
* Too young, only 1 of 10 days old
* Not considered
shouldn't only 5 days be needed -- did I do something wrong?
--
Robbe
signature.ng
Description: PGP signature
martin f krafft [EMAIL PROTECTED] writes:
i don't think users run it, so
/usr/lib/tempest4eliza/mksong.sh
If it is really a shell script, /usr/share/... is more correct.
--
Robbe
signature.ng
Description: PGP signature
to 0.4.3+20020409-1)
* Maintainer: Robert Bihlmeyer
* Too young, only 1 of 10 days old
* Not considered
shouldn't only 5 days be needed -- did I do something wrong?
--
Robbe
signature.ng
Description: PGP signature
Erik Rigtorp [EMAIL PROTECTED] writes:
I'm packaging Tempest for Eliza, but I'm unsure what to name the package.
The original tar file's name is tempest_for_eliza-1.0.5.tar.gz and the
generated binarys namnes: tempest_for_eliza and tempest_for_eliza_mp3. I
think those names are rather ugly.
Erik Rigtorp [EMAIL PROTECTED] writes:
My package tempest-for-eliza includes a script called mksong.sh, but I don't
now were to install it.
/usr/bin if users are expected to run it. See the Filesystem Hierarchy
Standard (available in the debian-policy package, which you should
have
Erik Rigtorp [EMAIL PROTECTED] writes:
I'm packaging Tempest for Eliza, but I'm unsure what to name the package.
The original tar file's name is tempest_for_eliza-1.0.5.tar.gz and the
generated binarys namnes: tempest_for_eliza and tempest_for_eliza_mp3. I
think those names are rather ugly.
Erik Rigtorp [EMAIL PROTECTED] writes:
My package tempest-for-eliza includes a script called mksong.sh, but I don't
now were to install it.
/usr/bin if users are expected to run it. See the Filesystem Hierarchy
Standard (available in the debian-policy package, which you should
have installed).
Hi,
how much time does new-processing usually take on a package moved from
crypto to main? I moved freenet-unstable a week ago, and still no
word. I might have done it wrong.
If I must fix an RC bug in this time, should I upload to non-us (to
guarantee speedy processing), or main?
--
Robbe
Junichi Uekawa [EMAIL PROTECTED] writes:
The upstream prefers it jack-audio-connection-kit.
Maybe that would be a good name.
A bit longish. As a user, I don't have much problem with such a name
(apart from dpkg -l), but I wouldn't want to maintain such a beast.
I am annoyed enough with my
Junichi Uekawa [EMAIL PROTECTED] writes:
The upstream prefers it jack-audio-connection-kit.
Maybe that would be a good name.
A bit longish. As a user, I don't have much problem with such a name
(apart from dpkg -l), but I wouldn't want to maintain such a beast.
I am annoyed enough with my
Hi,
I maintain freenet-unstable, a free Java application that builds with
jikes, but unfortunately not with the version in unstable and testing.
I've now got a bug about that and wonder whether it should really be
serious. It's not that this package is not buildable in principle --
but woody
Hi,
I maintain freenet-unstable, a free Java application that builds with
jikes, but unfortunately not with the version in unstable and testing.
I've now got a bug about that and wonder whether it should really be
serious. It's not that this package is not buildable in principle --
but woody sid
Kjetil Torgrim Homme [EMAIL PROTECTED] writes:
If an application uses libc6 and libslang (say), it will break when
libslang is recompiled against libc7. Therefore the libc6 version of
libslang needs to retained in a libc6 specific directory for backwards
compatibility, and ld.so needs to
Kjetil Torgrim Homme [EMAIL PROTECTED] writes:
If an application uses libc6 and libslang (say), it will break when
libslang is recompiled against libc7. Therefore the libc6 version of
libslang needs to retained in a libc6 specific directory for backwards
compatibility, and ld.so needs to
Michael Moerz [EMAIL PROTECTED] writes:
Well is there any documentation out there that would line out
the usage of the DBS (doogie build system)?
[...]
Is there any url where I could fetch a debian/scripts tarball
from? (or should I stick to the mentioned packages?)
I think you want to
Jaldhar H. Vyas [EMAIL PROTECTED] writes:
Third, and probably cleanest, is the option to simply stop shipping
different config files (they are different, are they?) under the same
name. /etc/webmin-ssl/* and /etc/init.d/webmin-ssl should work fine.
I don't want to do either of these
Michael Moerz [EMAIL PROTECTED] writes:
Well is there any documentation out there that would line out
the usage of the DBS (doogie build system)?
[...]
Is there any url where I could fetch a debian/scripts tarball
from? (or should I stick to the mentioned packages?)
I think you want to
Jaldhar H. Vyas [EMAIL PROTECTED] writes:
Third, and probably cleanest, is the option to simply stop shipping
different config files (they are different, are they?) under the same
name. /etc/webmin-ssl/* and /etc/init.d/webmin-ssl should work fine.
I don't want to do either of these
Jaldhar H. Vyas [EMAIL PROTECTED] writes:
I'm having a problem with something I thought was wery simple.
I have two packages, webmin and webmin-ssl which are interchangeable
(except as you've probably guessed one has SSL support, the other
doesn't). They both install certain conffiles
Jaldhar H. Vyas [EMAIL PROTECTED] writes:
I'm having a problem with something I thought was wery simple.
I have two packages, webmin and webmin-ssl which are interchangeable
(except as you've probably guessed one has SSL support, the other
doesn't). They both install certain conffiles such
Sven [EMAIL PROTECTED] writes:
On Sat, Jan 19, 2002 at 06:42:23PM +0100, Torsten Landschoff wrote:
On Thu, Jan 17, 2002 at 07:55:09PM +0100, Stefano Zacchiroli wrote:
These are not standard executable, see my just posted reply.
Indeed. But they are labelled as such, which is wrong.
Sven [EMAIL PROTECTED] writes:
On Sat, Jan 19, 2002 at 06:42:23PM +0100, Torsten Landschoff wrote:
On Thu, Jan 17, 2002 at 07:55:09PM +0100, Stefano Zacchiroli wrote:
These are not standard executable, see my just posted reply.
Indeed. But they are labelled as such, which is wrong.
Oohara Yuuma [EMAIL PROTECTED] writes:
struct.h says:
| #ifndef MAXPATHLEN
| # define MAXPATHLEN 1024
| #endif
As long as there are no assumptions in the code that library functions
won't return longer data, that's ok.
p Is writing something like:
Note that this license is not
Oohara Yuuma [EMAIL PROTECTED] writes:
struct.h says:
| #ifndef MAXPATHLEN
| # define MAXPATHLEN 1024
| #endif
As long as there are no assumptions in the code that library functions
won't return longer data, that's ok.
p Is writing something like:
Note that this license is not
Hamish Moffatt [EMAIL PROTECTED] writes:
On Wed, Jan 16, 2002 at 07:15:13PM +0900, Oohara Yuuma wrote:
I want to adopt osh (#89433), but I am not a Debian developer.
Is it OK just to change the title of the wnpp bug and find a sponsor?
(I am in the NM queue.)
Please find a sponsor
Stefano Zacchiroli [EMAIL PROTECTED] writes:
The file foo (for example) have not to be stripped (is a bytecode
executable, so stripping will remove the bytecode and the executable
will become useless), [...]
Isn't putting valuable bytecode in an ELF section that is a target of
strip kludgy
Tollef Fog Heen [EMAIL PROTECTED] writes:
It includes some private perl modules, which are only used
internally. Is it okay to put those in
/usr/share/request-tracker/lib or should I try to put them somewhere
sane in /usr/share/perl5/ ? I don't think they are useful for any
application
1 - 100 of 352 matches
Mail list logo
