> "Ari" == Ari Pollak <[EMAIL PROTECTED]> writes:
Ari> I had been taking the full brunt of the responsibility for
Ari> the xscreensaver NMU, but since I was a pre-NM at the time
Ari> and sponsors of uploads are supposed to follow Debian policy
Ari> as well, he ended up taking m
> "Ari" == Ari Pollak <[EMAIL PROTECTED]> writes:
>> IIRC Ari has caused upset with NMUs before; xscreensaver, I
>> believe. (I express no opinion about whether that upload was a
>> good idea or not.)
Ari> Didn't you sponsor the upload?
Um, so? While yes the sponsor is at
> "Russell" == Russell Coker <[EMAIL PROTECTED]> writes:
Russell> Do we have a library in Debian that provides reliable
Russell> stream based communication over UDP?
librx from openafs provides this functionality; it may be somewhat
more complexity than you are looking for.
> "Christian" == Christian Surchi <[EMAIL PROTECTED]> writes:
Christian> Ari wrote to me in the end of october to ask me about
Christian> my intention about logjam packaging. I had an enormous
Christian> backlog and I could not be able to reply. Then he filed
Christian> a wish
package: wnpp
severity: wishlist
I'm planning on packaging libsasl2-gssapi-mit, a version of the GSSAPI
plugin for libsasl2 compiled against MIT Kerberos.
This package has the same source as cyrus-sasl2, but different build
environment and options. It's not really possible to avoid having two
so
package: wnpp
severity: wishlist
Hi. AS discussed below, I intend to package OpenSSH using the current
Debian sources with patches to allow krb5 authentication. I will use
the patches available at
http://www.sxw.org.uk/computing/patches/openssh.html. These patches
attempt to comply with draft-i
> "Randolph" == Randolph Chung <[EMAIL PROTECTED]> writes:
>> The Automatic Package Building System page[1] lists the build
>> daemons with web pages. It does not list those without,
>> however. Since my latest libcdaudio packages are considered
>> out of date on i386, I was
>>>>> "Marc" == Marc Haber <[EMAIL PROTECTED]> writes:
Marc> On 02 Sep 2001 23:18:56 -0400, Sam Hartman
Marc> <[EMAIL PROTECTED]>
Marc> wrote:
>>>>>>> "Marc" == Marc Haber
>>>>>>
> "Jules" == Jules Bean <[EMAIL PROTECTED]> writes:
Jules> This seems a step back from the old freeze procedure, where
Jules> you could upload to frozen (and, I assume, auto-builders
Jules> were building against frozen)
Well, once your library and all dependencies are frozen you
> "Marc" == Marc Haber <[EMAIL PROTECTED]> writes:
Marc> On Sun, 2 Sep 2001 22:49:00 +0200 (CEST), Santiago Vila
Marc> <[EMAIL PROTECTED]> wrote:
>> However, you can repackage the .orig.tar.gz source and remove
>> the non-US bits from it. Then you could upload both source and
> "Henrique" == Henrique de Moraes Holschuh <[EMAIL PROTECTED]> writes:
Henrique> AFAIK, I cannot do that. If I build against testing, I
Henrique> help the breakage by adding yet another package that
Henrique> depends on the outdated libraries that are in testing,
Henrique> th
>>>>> "Manoj" == Manoj Srivastava <[EMAIL PROTECTED]> writes:
>>> "Sam" == Sam Hartman <[EMAIL PROTECTED]> writes:
>>>>> "Manoj" == Manoj Srivastava <[EMAIL PROTECTED]> writes:
>>>>> &q
>>>>> "Herbert" == Herbert Xu <[EMAIL PROTECTED]> writes:
Herbert> Sam Hartman <[EMAIL PROTECTED]> wrote:
>> This brings up an interesting point. While we should work with
>> upstream maintainers to fix these problems, we should a
>>>>> "Herbert" == Herbert Xu <[EMAIL PROTECTED]> writes:
Herbert> Sam Hartman <[EMAIL PROTECTED]> wrote:
>> for needs to be determined by the architecture maintainers.
>> For Sparc, modversions are not used so you can probably buil
So, a week or so ago, I asked for comments on some problems I've been
having with the Debian kernel modules build system for modules not in
the Linux source tree. I'm only dealing with modules for upload to
Debian. The make-kpkg solution seems to work for individuals building
modules for their
> "Herbert" == Herbert Xu <[EMAIL PROTECTED]> writes:
Herbert> I won't look at all of them as this is really the
Herbert> upstream maintainer's job.
This brings up an interesting point. While we should work with
upstream maintainers to fix these problems, we should also try to
avoid
>>>>> "Herbert" == Herbert Xu <[EMAIL PROTECTED]> writes:
Herbert> Sam Hartman <[EMAIL PROTECTED]> wrote:
>> We do? please explain what it is. Herbert produces kernel
>> headers packages for all flavors of kernels he produce
> "Manoj" == Manoj Srivastava <[EMAIL PROTECTED]> writes:
>>> "Aaron" == Aaron Lehmann <[EMAIL PROTECTED]> writes:
Aaron> So you're saying it's better to hardcode syscall numbers
Aaron> and stuff than using the kernel headers? Sre...
Manoj> We already have a process f
> "Ivan" == Ivan E Moore <[EMAIL PROTECTED]> writes:
Ivan> Solution?: create a program (update-dm?) that would pull
Ivan> the current list of window/session-managers installed on the
Ivan> system and build the appropriate config files for whichever
You should probably consider w
> "Petr" == Petr Cech <[EMAIL PROTECTED]> writes:
>> Since this question is currently being referred to legal
>> advice, do you want me to move postgresql into non-us, which
>> will force any packages depending on it into non-us too, or
>> should I leave it alone pending resol
> "Joey" == Joey Hess <[EMAIL PROTECTED]> writes:
Joey> If these tools become widly enough accepted that we think
Joey> everyone should have them available by default, we can make
Joey> them standard priority.
In the new universe (debbootstrap, tasksel, etc) where a user might
nev
> "Brian" == Brian May <[EMAIL PROTECTED]> writes:
Brian> I have got a bug report #95246 requesting Heimdal be
Brian> compiled against openldap2. This would enable being able to
Brian> store the Kerberos database in the openldap database. All
Brian> data is stored in LDAP encry
>>>>> "Herbert" == Herbert Xu <[EMAIL PROTECTED]> writes:
Herbert> Sam Hartman <[EMAIL PROTECTED]> wrote:
>> This is misleading. The kernel-image-*-arch packages are much
>> simpler because they do not depend both on a kernel sour
L PROTECTED] (kernel-image-i386 maintainer),
[EMAIL PROTECTED] (concerned about package size)
Subject: Referring what kernel-images to build to the technical committee?
Reply-to: debian-devel@lists.debian.org
From: Sam Hartman <[EMAIL PROTECTED]>
Resent-Message-ID: <[EMAIL PROTECTED]&
L PROTECTED] (kernel-image-i386 maintainer),
[EMAIL PROTECTED] (concerned about package size)
Subject: Referring what kernel-images to build to the technical committee?
Reply-to: debian-devel@lists.debian.org
From: Sam Hartman <[EMAIL PROTECTED]>
Resent-Message-ID: <[EMAIL PROTECTED]&
> "Herbert" == Herbert Xu <[EMAIL PROTECTED]> writes:
Herbert> BTW, this is how the kernel images are organised on
Herbert> alpha/i386/sparc.
This is misleading. The kernel-image-*-arch packages are much simpler
because they do not depend both on a kernel source package and on a
mod
One thing that strikes me as excellent about Debian is the build
system. The autobuilders and tools make it very likely that package
builds are reproducible and a variety of tools like debhelper make it
easier to do the "right thing" in many circumstances than doing
something wrong. I've come a
[cc list is an attempt at stakeholders for this issue. If I missed
people, I'm sorry. If I annoyed people by ccing them even though they
read the list, well I'm sorry too, but there are a fair number of
people who tend to want to be explicitly cc'd when an issue pertains
to them.]
Summary: He
> "Herbert" == Herbert Xu <[EMAIL PROTECTED]> writes:
Herbert> I doubt the increase is going to be that significant.
Herbert> Since most of these will eventually become part of the
Herbert> mainstream kernel or get dropped.
I hope that is not actually the trend we see.
>> im
[I'm responding to Herbert directly to draw attention to this question
and make sure I get a response from him. I have also read the rest of
this thread even though I am responding to a fairly early message. ]
I'm approaching this as the maintainer of the openafs package, which
has a kernel mod
> "Bernd" == Bernd Eckenfels <[EMAIL PROTECTED]> writes:
Bernd> Hello Sam, On Sat, Dec 30, 2000 at 11:27:44PM -0500, Sam
Bernd> Hartman wrote:
>> In order to actually get something done in an electronic
>> office, we need a certain amount of infrastructure.
Bernd> Thanks f
In order to actually get something done in an electronic office, we
need a certain amount of infrastructure. In a large environment, the
incremental costs are somewhat visible, but you won't see how much
work it took to get there. In practice, starting from ground zero
means identi
401 - 432 of 432 matches
Mail list logo
