* Joey Hess <[EMAIL PROTECTED]> [010425 11:12]:
> This is actually quite doable, you just need to have a clued isp[1] who
> sets up a nifty little forwarding trick in the reverse DNS. Here's an
> exmple of how my old ISP did it:
>
>net152 ns kitenet.net.
>153
In short, how do you do them?
AFAICT, I could conceivably add either
Build-Depends: kernel-headers
or
Build-Depends: kernel-headers-2.2.19
If I did the former, there doesn't seem to be any way to reliably
get at the kernel headers. The only way I can see is to hardcode
-I/usr/src
Anthony Towns wrote:
> The latter'll obviously break as soon as 2.2.20 comes out and 2.2.19 gets
> removed from the archive.
If you're building modules, then they'll have to be rebuilt when 2.2.20
comes out anyway. If this is a user-space program, then it better stop
using kernel headers all to
>In short, how do you do them?
What do you want to do with them?
There are a whole load of wacky special source dependencies (*LINUX24-HEADERS
and so on) which seem to be trying to solve variants of this problem. But
this mechanism doesn't seem to be all that robust either.
I think the whole
Philip Blundell <[EMAIL PROTECTED]> wrote:
> I think the whole idea of putting the kernel version number in the name of
> the
> headers package is pretty bogus. It would probably be better to just have a
> "kernel-headers" package which installed itself in /usr/src/kernel-headers;
> then you c
Tom Lear <[EMAIL PROTECTED]> wrote:
>> Sure, don't run the daemon at all. When you install exim, "rm
>> /etc/init.d/rc?.d/S*exim" and it won't start. Local processes will be
> BTW, I think this is what ssh should do if you choose not to run the
> daemon on startup (rather than making /etc/init.d
>Having version numbers in the kernel-headers package name is a consequence
>of having them in the kernel-image package name. The point of having them
>in the kernel-image package name should be pretty obvious...
Actually, I'm not even completely convinced that having them in the
kernel-image pa
On Sat, May 05, 2001 at 06:23:39PM +1000, Anthony Towns wrote:
> In short, how do you do them?
>
> AFAICT, I could conceivably add either
>
> Build-Depends: kernel-headers
> or
> Build-Depends: kernel-headers-2.2.19
>
or
Build-Depends: kernel-headers-2.2
or
Build-Depe
* "Steve M. Robbins"
| I tried Netscape, Mozilla, Galeon (mozilla-based), "Browse X", and
| lynx. None of them would display text/x-csrc. The first three tried
| to save it to disk, BrowseX showed a blank page, and lynx completely
| ignored my attempt to open the link.
lynx opened it just fine
On Sat, May 05, 2001 at 06:07:54AM -0400, Ben Collins wrote:
> On Sat, May 05, 2001 at 06:23:39PM +1000, Anthony Towns wrote:
> > In short, how do you do them?
> > AFAICT, I could conceivably add either
> Build-Depends: kernel-headers-2.2
> or
> Build-Depends: kernel-headers-2.4
> You'l
On Fri, May 04, 2001 at 09:19:29AM +0200, Tollef Fog Heen wrote:
> * Radovan Garabik
>
> | > Can it be run from inetd? I'm really dying for a dict server that can be
> |
> | More or less, yes, it can, but currently it is a bit unusable
> | since it takes forever to start (it has to parse the ind
Package: wnpp
Severity: wishlist
`smartcard' allows you to control a smart card reader from the
command line. Currently, it supports just a few basic commands
which only work on plain I2C memory cards.
URL: http://www.lionking.org/~kianga/software/smartcard/
Copyright: Copyright (C) 2000 Rene Pul
I have prepared the packages needed to run kernels up to 2.4.4 on a Debian
2.2r3 (potato) system. Please read [1] for more information.
Changes since the last release:
+ added: isdnutils
Binary packages:
o ipppd
o isdnactivecards
On Fri, May 04, 2001 at 07:12:07PM -0700, Tom Lear wrote:
> BTW, I think this is what ssh should do if you choose not to run the
> daemon on startup (rather than making /etc/init.d/ssh not work at all).
> I have ssh installed on my laptop, and I don't want it running by
> default, but I'd like to
On Fri, May 04, 2001 at 09:48:54PM -0500, John Hasler wrote:
> > Well I guess you could use sourceforge.
>
> I assume that the author has his reasons for not wanting to use
> Sourceforge.
There are (were?) mailing lists for other projects on lists.debian.org...?
--
Digital Electronic Being Inte
Previously Christoph Simon wrote:
> The german expression has a somewhat special history.
Germanic at least, possible even older (considering Dutch has the
exact some meaning).
Wichert.
--
_
/ Nothing is fool-proof to a su
Previously Hamish Moffatt wrote:
> There's a lot more interesting ones than that. Last year, an RFC
> described transmission of electricity over IP.
Probably because noone implemented RFC2549 yet: IP over Avian Carriers
with Quality of Service. Unfortunately there still is ongoing litigation
about
Carlos Laviola schrieb:
> I hope that's a joke, because, based _solely_ on that
> comparison table, the reason one should use snarf over wget is
> because it has a cool progressbar.
snarf is also a lot smaller than wget. (According to the chart)
ciao, 2ri
--
They are really completely different
* Wichert Akkerman
| Previously Hamish Moffatt wrote:
| > There's a lot more interesting ones than that. Last year, an RFC
| > described transmission of electricity over IP.
|
| Probably because noone implemented RFC2549 yet: IP over Avian Carriers
| with Quality of Service. Unfortunately there
On Sat, May 05, 2001 at 10:27:53AM +0100, Philip Blundell wrote:
>
> Actually, I'm not even completely convinced that having them in the
> kernel-image package name is particularly beneficial. But, even if we leave
> that the way it is, I don't think it's impossible to arrange for
> kernel-hea
Anthony Towns wrote:
> On Sat, May 05, 2001 at 06:07:54AM -0400, Ben Collins wrote:
>> > AFAICT, I could conceivably add either
>> Build-Depends: kernel-headers-2.2
>> or
>> Build-Depends: kernel-headers-2.4
>> You'll notice that recent kernel-headers packages provide the
>> major.min
On Thu, 3 May 2001, Joey Hess wrote:
[Substitution in long description]
> I see nothing wrong with this, it should work.
Hrm, I just tested with a description of:
Description: ${hostname}
${hostname} long
The first substitution worked, the second didn't. I suspect this may be
because I'm runn
On Sat, May 05, 2001 at 09:44:07PM +1000, Herbert Xu wrote:
> On Sat, May 05, 2001 at 10:27:53AM +0100, Philip Blundell wrote:
> >
> > Actually, I'm not even completely convinced that having them in the
> > kernel-image package name is particularly beneficial. But, even if we
> > leave
> > tha
Simon Richter wrote:
> Hrm, I just tested with a description of:
>
> Description: ${hostname}
> ${hostname} long
>
> The first substitution worked, the second didn't. I suspect this may be
> because I'm running testing instead of unstable at home. I'll try unstable
> debconf now.
That sounds si
John Hasler wrote:
> Joey Hess writes:
> > Well I guess you could use sourceforge.
>
> I assume that the author has his reasons for not wanting to use
> Sourceforge.
I was thinking just use it for the list, and ignore the other stuff.
--
see shy jo
Some time ago I told, that a company called BeOpen is no more. Well, I
just found, that their software is available at SourceForge:
http://sourceforge.net/projects/infodock/
http://sourceforge.net/projects/hyperbole/
http://sourceforge.net/projects/oo-browser/
--
Juhapekka "naula" Tolvanen * *
While we're at it: How on earth can I get rid of those
Warning: locale not supported by Xlib, locale set to C
messages? I use LC_CTYPE=de_DE.ISO-8859-1 to get Umlauts etc in mutt.
Unfortunately, this produces the above error message with lots of X
programs - especially annoying when you use at
> "Richard" == Richard Atterer <[EMAIL PROTECTED]> writes:
Richard> While we're at it: How on earth can I get rid of those
Richard> Warning: locale not supported by Xlib, locale set to C
Richard> messages? I use LC_CTYPE=de_DE.ISO-8859-1 to get Umlauts
Richard> etc in mutt. Un
On Fri, May 04, 2001 at 11:20:21PM +0200, Richard Atterer wrote:
[...]
> messages? I use LC_CTYPE=de_DE.ISO-8859-1 to get Umlauts etc in mutt.
Try "LC_CTYPE=de_DE" instead.
--
CU,
Patrick.
"Never run on auto-pilot" - The Pragmatic Programmer
pgpzbiy9d7Pvs.pgp
Description: PGP signature
Hello,
I am maintaing the Debian package puzzle and have a problem
with the new upstream version. The package and program has been
renamed by upstream to tree-puzzle, because there was a conflict
with another program named puzzle.
I was considering to make a new package tree-puzzle which conflicts
On Sat, May 05, 2001 at 11:09:20AM -0400, Ben Collins wrote:
> The point here is to make packages start moving to Build-Dep'ing on
> kernel-headers-* packages. The question is, how to allow them to do that
> easily.
>
> IMO, we can use alternatives. And it should be fairly easy
>
> update-altern
Sat, May 05, 2001 at 08:43:30PM +0200 wrote:
> Hello,
>
> I am maintaing the Debian package puzzle and have a problem
> with the new upstream version. The package and program has been
> renamed by upstream to tree-puzzle, because there was a conflict
> with another program named puzzle.
> I was co
>>"Ben" == Ben Collins <[EMAIL PROTECTED]> writes:
Ben> False. That is the very thing I want to alleviate (people using kernel
Ben> headers from the libc6-dev package).
However, that is what 99% of the programs out there need to
do, since they really are not dependent on the specifics
Je Sat, 5 May 2001 11:09:20 -0400,
Ben Collins <[EMAIL PROTECTED]> scribis:
> IMO, we can use alternatives. And it should be fairly easy
>
> update-alternatives --install /usr/src/kernel-headers-2.2 kernel-headers-2.2 \
> /usr/src/kernel-headers-2.2.
>
> Where "" would be something like "19" (
Hi all,
maybe it is a stupid question, but can debian packages be installed in other
places than / ?
I know that when the package is compiled the Makefile has a $DESTDIR
attribute, but is this preserved in the deb package?
This issue came up when i tried to convince someone that debian packages
On Sat, May 05, 2001 at 12:39:48PM -0700, David Whedon wrote:
> Sat, May 05, 2001 at 08:43:30PM +0200 wrote:
> > Hello,
> >
> > I am maintaing the Debian package puzzle and have a problem
> > with the new upstream version. The package and program has been
> > renamed by upstream to tree-puzzle, be
On Sat, May 05, 2001 at 10:00:14PM +0200, Egon Willighagen wrote:
> Hi all,
>
> maybe it is a stupid question, but can debian packages be installed in other
> places than / ?
It is not a stupid question, IMHO.
Unfortunately, I believe the answer is "not in general". One of the
problems is that
On Sat, May 05, 2001 at 10:00:14PM +0200, Egon Willighagen wrote:
> maybe it is a stupid question, but can debian packages be installed in other
> places than / ?
>
> I know that when the package is compiled the Makefile has a $DESTDIR
> attribute, but is this preserved in the deb package?
>
>
On 5 May 2001, Ben Gertzfield wrote:
> > "Richard" == Richard Atterer <[EMAIL PROTECTED]> writes:
>
> Richard> While we're at it: How on earth can I get rid of those
> Richard> Warning: locale not supported by Xlib, locale set to C
>
> Richard> messages? I use LC_CTYPE=de_DE.ISO-8
On Sat, May 05, 2001 at 10:00:14PM +0200, Egon Willighagen wrote:
> Hi all,
>
> maybe it is a stupid question, but can debian packages be installed in other
> places than / ?
i was thinking about this myself. i suppose in theory it is possible,
and the data.tar.gz has all the files that are inst
>Now, how are we going to support: If there's a version of libc6 that's
>known to use kernel headers incompatible with a particular
>kernel-headers-*, then a package compiled against those kernel headers
>should conflict with that libc6.
Eh? Why would this be useful?
p.
Read the archives for the sad history of version numbers and the flamewars :)
Please remember that the reason we went to using version names was prompted
by Debian 1.0. [For those that don't know: Debian was at something like
0.97 when a vendor [?? Infomagic ??] released a prerelease snapshot whi
Je 05 May 2001 15:06:11 -0500,
Manoj Srivastava <[EMAIL PROTECTED]> scribis:
> Try this: suggest the kernel-headers package, and set
> CFLAGS += -I$(KSRC)/include
> and instruct people to set the KSRC variable as needed.
> [...]
> Have a default value for KSRC if you need, and arrang
On Sat, May 05, 2001 at 02:33:45PM -0700, Alexander Hvostov wrote:
> One could use fakeroot to create a sort of virtual machine, in which regular
> users can install packages as they please, but fakeroot doesn't support
> chroot (yet?), and I'm beginning to think a better solution would be an
> op
Hi,
it seems to be a trend that maintainers try to change their packages to be
Debian native. Policy says about native packages (in the chapter about
version numbering):
<-- snip -->
This part of the version number specifies the version of the
Debian package based on
On Sat, May 05, 2001 at 10:00:14PM +0200, Egon Willighagen wrote:
>
> maybe it is a stupid question, but can debian packages be installed in other
> places than / ?
You could try the --root=dir, --admindir=dir or --instdir=dir options
to dpkg. But I think that maybe this is not what you really
On Sat, May 05, 2001 at 09:44:07PM +1000, Herbert Xu wrote:
> The thing is, kernel-headers should not be used at all unless you're
> compile glibc, or modules. Anything else will break.
So you're saying it's better to hardcode syscall numbers and stuff
than using the kernel headers? Sre...
On Sat, 5 May 2001 19:01:03 -0400
Matt Zimmerman <[EMAIL PROTECTED]> wrote:
> On Sat, May 05, 2001 at 02:33:45PM -0700, Alexander Hvostov wrote:
>
> > One could use fakeroot to create a sort of virtual machine, in which
regular
> > users can install packages as they please, but fakeroot doesn't
s
Ben Collins <[EMAIL PROTECTED]> wrote:
> On Sat, May 05, 2001 at 09:44:07PM +1000, Herbert Xu wrote:
>> The thing is, kernel-headers should not be used at all unless you're
>> compile glibc, or modules. Anything else will break.
> False. That is the very thing I want to alleviate (people using k
On Sat, May 05, 2001 at 09:40:40PM -0400, Ben Collins wrote:
> >
> > Personally I think you're trying to solve a problem that will become a
> > non-issue as people realise this and stop using kernel headers.
>
> That's wishful thinking, but I agree. I'm not sure it is possible
> though.
I'm more
On Sun, May 06, 2001 at 09:46:32AM +1000, Herbert Xu wrote:
> > The point here is to make packages start moving to Build-Dep'ing on
> > kernel-headers-* packages. The question is, how to allow them to do that
> > easily.
>
> Personally I think you're trying to solve a problem that will become a
>
Hi,
On Sat, May 05, 2001 at 12:39:48PM -0700, David Whedon wrote:
> This is discussed in the Developer's Reference [1]:
>
> 9.3 Replacing or renaming packages
>
> Sometimes you made a mistake naming the package and you need to rename it. In
> this case, you need to follow a two-step process. Fir
On Sat, May 05, 2001 at 05:47:21PM -0700, Alexander Hvostov wrote:
> On Sat, 5 May 2001 19:01:03 -0400 Matt Zimmerman <[EMAIL PROTECTED]> wrote:
> > You should look into the S/390 port.
>
> The S/390 port is hardware specific. For obvious reasons (how many Debian
> machines are S/390s?), this is
On Sat, 5 May 2001 16:48:05 -0400
Matt Zimmerman <[EMAIL PROTECTED]> wrote:
> On Sat, May 05, 2001 at 10:00:14PM +0200, Egon Willighagen wrote:
>
> > maybe it is a stupid question, but can debian packages be installed in
other
> > places than / ?
> >
> > I know that when the package is compiled
> Thanks, - I know this and have done it previously in the case of
> zicq and krolden. However, what I really wanted to know is, how
> this (or any other) procedure can take care that the users of the
> old package will get the renamed package automatically updated with
> 'apt-get upgrade'? Other
> Thanks, - I know this and have done it previously in the case of
> zicq and krolden. However, what I really wanted to know is, how
> this (or any other) procedure can take care that the users of the
> old package will get the renamed package automatically updated with
> 'apt-get upgrade'?
Oh,
56 matches
Mail list logo
