Hello Steve,
thank you for your reply to my status report.
Steve Langasek wrote:
> Andreas Jochens wrote:
>> It will only be necessary to describe the current situation
>> in the official release documents and include pointers
>> to the separate amd64 archive, which will be provided
>> by the
Le Fri, 22 Apr 2005 09:35:03 -0400, Dominic Amann a écrit :
>>
>>
>>On Sun, Apr 04, 2004 at 10:35:32AM +0200, Otto Wyss wrote:
>>> To solve my mkinitrd problem I searched for solutions. Each time someone
>>> has run into my problem he was asked if module-init-tools are installed
>>> and each time
On Fri, 22 Apr 2005 13:58:31 -0400, Patrick Ouellette wrote:
> On Mon, Apr 18, 2005 at 04:24:34PM -0500, Adam M wrote:
>> In many ways, current testing is your stable. Extending the testing
>> period from testing to your proposed candidate and then stable would
>> do nothing about normal bugs. RC b
On Sat, 23 Apr 2005, Russell Coker wrote:
> On Friday 22 April 2005 21:28, Henrique de Moraes Holschuh <[EMAIL
> PROTECTED]>
> wrote:
> > > SE Linux also has a list of device names for initially labelling a file
> > > system. Neither devfs nor devfs device names will work with SE Linux.
> >
> >
Hello,
On Fri, Apr 22, 2005 at 08:05:17PM +0200, Andreas Jochens wrote:
> As a preparation for the amd64 porters irc meeting tomorrow,
> I tried to build the complete Debian sarge archive for the
> amd64 architecture from the unpatched Debian sarge sources.
>
> The result was very encouraging.
Hi,
I am the maintainer of kernel-patch-cryptoloop. I am not a DD, so my gpg
key is not on the debian keyring.
Almost noone uses kernel-patch-cryptoloop, so I let things slide. AFAIK,
sarge is to use a 2.6.x kernel, so this package is mostly useless.
However, a few people expressed interest recen
On Fri, Apr 22, 2005 at 09:30:39PM +0200, Juergen Strobel wrote:
[...]
> I tried to upload an up to date version of this package today, but got
> denied again. I can't remember how I got the initial version in.
>
> Questions:
>
> 1. Where does Katie look for public keys?
In debian-keyring.
>
On Friday 22 April 2005 21:28, Henrique de Moraes Holschuh <[EMAIL PROTECTED]>
wrote:
> > SE Linux also has a list of device names for initially labelling a file
> > system. Neither devfs nor devfs device names will work with SE Linux.
>
> That's fine. But regular packages should not limit thems
Hi Andreas,
On Fri, Apr 22, 2005 at 08:05:17PM +0200, Andreas Jochens wrote:
> I consider this a good way to split up responsibilities.
> This way of handling things could serve as a good example of
> how other ports may be organized after sarge is released.
I certainly agree with that; unfortu
On Fri, Apr 22, 2005 at 02:54:38PM -0400, Patrick Ouellette wrote:
> On Fri, Apr 22, 2005 at 07:16:30PM +0200, Adrian Bunk wrote:
> >
> > The problem is that for many transitions, "slowly" means "never", since
> > the criteria you set are unlikely to be fulfilled for all parts of such
> > a tran
On Sun, Apr 04, 2004 at 10:35:32AM +0200, Otto Wyss wrote:
To solve my mkinitrd problem I searched for solutions. Each time someone
has run into my problem he was asked if module-init-tools are installed
and each time it was answered yes. Unfortunately also each time no
further action is mentioned
On Mon, Apr 18, 2005 at 04:24:34PM -0500, Adam M wrote:
> A similar thing is already here in http://snapshot.debian.net/
Similar only in that they have daily snapshots. Vastly dissimilar in
that what is provided is the complete archive, bugs and all.
I'm not saying we call each day a release, bu
On Fri, Apr 22, 2005 at 12:02:39PM -0400, Patrick Ouellette wrote:
> On Thu, Apr 21, 2005 at 01:04:34AM +0200, Adrian Bunk wrote:
> > Let my try to explain it:
> >
> >
> > The "debian stable == obsolete" is a release management problem of
> > Debian. One release every year and it would be suitab
On Thu, Apr 21, 2005 at 01:04:34AM +0200, Adrian Bunk wrote:
> Let my try to explain it:
>
>
> The "debian stable == obsolete" is a release management problem of
> Debian. One release every year and it would be suitable for most
> purposes.
>
This is the problem. Debian has NEVER been able to
On 21-Apr-05, 11:07 (CDT), Eric Cooper <[EMAIL PROTECTED]> wrote:
> But if apt-proxy is still installed and running when apt-proxy starts
> up, it will fail because the port is in use. Should I make the approx
> package conflict with apt-proxy? Both packages allow the port to be
> changed to som
On Wed, Apr 20, 2005 at 04:56:32AM +0200, Adrian Bunk wrote:
> The rules and goals of testing are clear.
>
> The more interesting points are the problems of testing that several
> years of using it have shown.
>
> > If package FOO has a RC bug, then everything that depends on FOO will be
> > stu
On Fri, Apr 22, 2005 at 07:16:30PM +0200, Adrian Bunk wrote:
>
> The problem is that for many transitions, "slowly" means "never", since
> the criteria you set are unlikely to be fulfilled for all parts of such
> a transition at any time in the future.
>
> And the more time passes, it becomes m
On 21-Apr-05, 05:12 (CDT), Gerrit Pape <[EMAIL PROTECTED]> wrote:
> > Why re-write cron when cron only needs a minor change?
>
> I'm afraid I again can't follow your thinking.
I'm pretty sure that he was only talking about implementing @reboot in
bcron, rather than requiring a whole new system
Hi,
did anybody see Warran Turkal (the current maintainer of dbs) lately?
He seems to be MIA WRT his NM-process and packaging work. I tried to
reach him at <[EMAIL PROTECTED]> for a while now, but to no avail.
Does anybody know of a another/better address?
thanks,
Michael
--
Michael Banck
De
On 20-Apr-05, 16:48 (CDT), Matthew Garrett <[EMAIL PROTECTED]> wrote:
> Steve Greenland <[EMAIL PROTECTED]> wrote:
>
> > And now you say it's *still* going on?
>
> Yes. For various reasons, I'm more hopeful now than I have been
> previously.
Well, I'll be amazed and delighted when you prove me
Moin Patrick!
Patrick Ouellette schrieb am Freitag, den 22. April 2005:
> > And the more time passes, it becomes more and more complicated since
> > additional transitions might be interdependent with a transition making
> > the problem even more complicated.
> >
>
> You are very good at repea
As a preparation for the amd64 porters irc meeting tomorrow,
I tried to build the complete Debian sarge archive for the
amd64 architecture from the unpatched Debian sarge sources.
It took about a week to build all 8800+ source packages on a standard
single processor EM64T-P4 box (Every package w
Package: wnpp
Severity: wishlist
* Package name: lynkeos.app
Version : 1.2
Upstream Authors: Christophe Jalady <[EMAIL PROTECTED]>,
Jean-Etienne Lamiaud <[EMAIL PROTECTED]>
* URL : http://lynkeos.sourceforge.net/
* License : GNU GPL
Descrip
On Mon, Apr 18, 2005 at 07:37:40PM -0500, Gunnar Wolf wrote:
> Patrick Ouellette dijo [Sat, Apr 16, 2005 at 01:04:59AM -0400]:
> > (...)
> > Another difference is that testing will get new versions of packages and
> > those versions might (but should not) cause breakage. Testing has had
> > breaka
Scripsit Russell Coker <[EMAIL PROTECTED]>
> Incidentally I wrote a shared object to support changing the apparent time
> which was actually useful for such tasks as Y2K testing and running demo
> software. Getting it to change the time() library call was easy, changing
> the time stamp on fil
On Fri, Apr 22, 2005 at 12:21:49PM -0400, Patrick Ouellette wrote:
> On Wed, Apr 20, 2005 at 04:56:32AM +0200, Adrian Bunk wrote:
> > The rules and goals of testing are clear.
> >
> > The more interesting points are the problems of testing that several
> > years of using it have shown.
> >
> > >
Following up to Message-ID: <[EMAIL PROTECTED]>, I've
put together a libaio package at http://holomorphy.com/~wli/libaio/
I figured a year or so was long enough to give people time to complain
about the kernel interface vs. glibc's worker thread -based emulation
library and so on, and thus far I've
On Fri, Apr 22, 2005 at 09:30:39PM +0200, Juergen Strobel wrote:
> Almost noone uses kernel-patch-cryptoloop, so I let things slide. AFAIK,
> sarge is to use a 2.6.x kernel, so this package is mostly useless.
> However, a few people expressed interest recently, and added to the old
> bug report #25
Package: wnpp
Severity: wishlist
* Package name: libservlet2.4-java
Version : 2.4
Upstream Author : Apache Jakarta Group
* URL or Web page : http://jakarta.apache.org/tomcat/index.html
* License : Apache 2.0
Description : Servlet 2.4 and JSP 2.0 Java classes and docum
Package: wnpp
Severity: wishlist
Owner: Romain Beauxis <[EMAIL PROTECTED]>
* Package name: kshutdown
Version : 0.6.0
Upstream Author : Konrad Twardowski <[EMAIL PROTECTED]>
* URL : http://kshutdown.sourceforge.net/
* License : GPL
Description : An advance
On Fri, 22 Apr 2005, Maciej Dems wrote:
> I have a simple question concerning the GFDL discussion.
For which the simple answer is:
Read http://people.debian.org/~srivasta/Position_Statement.xhtml
--
"One disk to rule them all, One disk to find them. One disk to bring
them all and in the dark
I have a simple question concerning the GFDL discussion.
Does the GFDL documentation which currently does not contain any invariant
section have to go to non-free as well?
As I understand the problem, such documentation is free and only can loose
its freeness in the future. But the same can be
On Fri, 22 Apr 2005, Russell Coker wrote:
> On Sunday 27 March 2005 00:26, Roger Leigh <[EMAIL PROTECTED]>
> wrote:
> > Is there a project-wide policy for support for devfs (and devfs-style,
> > e.g. udev devfs.rules) device naming?
>
> The SE Linux kernel code doesn't and won't support devfs. D
On Wed, Apr 20, 2005 at 05:57:02PM -0700, Jeff Carr wrote:
> Jurij Smakov wrote:
>
> >Since it is becoming more and more a kernel topic, you might also want
> >to move discussion to debian-kernel.
>
> Could someone give us a simple rundown of how we would submit a patch to
> the debian kernel s
On Thu, April 21, 2005 23:23, Dan Jacobson wrote:
> It feels odd that a handful of packages seem to use a dusty field:
> $ grep ^O /var/lib/dpkg/available|sort|uniq -c
> 3 Origin: Debian
> 35 Origin: debian
> Shall I clone this bug to them to get them to take it away?
Perhaps you can state in your
35 matches
Mail list logo
