Package: wnpp
Severity: wishlist
Owner: Russ Allbery <[EMAIL PROTECTED]>
* Package name: svn2cl
Version : 0.4
Upstream Author : Arthur de Jong <[EMAIL PROTECTED]>
* URL : http://ch.tudelft.nl/~arthur/svn2cl/
* License : BSD (3-clause)
Description : Convert
On Saturday 24 December 2005 11:35, Goswin von Brederlow
> > Also as for sym-links, there's no reason why /var/run couldn't be used
> > all along. Imagine we have a system where /var is mounted from an LVM
> > volume (or something else that can't be mounted early on). So we start
> > with a /var
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
Package: wnpp
Severity: wishlist
* Package name: ttf-cjk-compact
Version : 1.0
Upstream Author : Kenshi Muto
* URL : deb http://kmuto.jp/debian/mtu unstable main
deb-src http://kmuto.jp/debian/mtu unstab
On Fri, Dec 23, 2005 at 09:59:18AM +0100, Stefano Zacchiroli wrote:
> On Fri, Dec 23, 2005 at 12:40:40PM +1000, Anthony Towns wrote:
> > > I don't like downgrading the vim -> vim-runtime dependency since IMO if
> > > a user apt-get-installs vim he expect a fully working vim installation
> > > (incl
Anand Kumria <[EMAIL PROTECTED]> writes:
>> The ffmpeg library in debian is a problem case and probably should not
>> be in there. That issue hasn't been decided yet and till then anything
>> using it stays stuck.
>
> Really? Excellent then. I would expect that gstreamer0.10-ffmpeg,
> recently up
Andrew Suffield wrote:
> As a general rule, UK bandwidth prices are roughly five to ten times
> those of equivalent service in other EU countries. Not that you can
> get equivalent service.
Ouch. I pay less than that for a T1 to my house, and far far far less
for bandwidth at a colo. I suggest th
Henrique de Moraes Holschuh <[EMAIL PROTECTED]> writes:
> On a vm-based fs, you always use *address space* for data in it, and it is
> linearly coupled to the amount of filesystem used (or even to the full size,
> for extremely dumb filesystems).
>
> Not that address space shortage is something I'
Russell Coker <[EMAIL PROTECTED]> writes:
> On Monday 19 December 2005 11:49, Bernd Eckenfels <[EMAIL PROTECTED]> wrote:
>> In article <[EMAIL PROTECTED]> you wrote:
>> > If /run is tmpfs, it means everything stored there eats virtual memory.
>> > So a musch metter strategy would be to move everyt
Eduard Bloch <[EMAIL PROTECTED]> writes:
> #include
> * Goswin von Brederlow [Wed, Dec 21 2005, 04:19:56PM]:
>
>> > Actual maintainer of dpkg is evaluating the possibility to use 7zip.
>> > Even if the decision of using 7zip by default is far from being taken, it
>> > looks
>> > likely that dpkg
Ron Johnson <[EMAIL PROTECTED]> writes:
> On Wed, 2005-12-21 at 16:12 +0100, Goswin von Brederlow wrote:
>> "Steinar H. Gunderson" <[EMAIL PROTECTED]> writes:
>>
>> > On Sun, Dec 18, 2005 at 12:34:56PM +0100, Gürkan Sengün wrote:
> [snip]
>> The transition itself would go completly unadminister
Olaf van der Spek <[EMAIL PROTECTED]> writes:
> On 12/21/05, Goswin von Brederlow <[EMAIL PROTECTED]> wrote:
>> > Who need PARALELISM and who has a bandwidth of more then 8 MBit?
>>
>> I have 10240kBit downstream and get way less from security.debian.org.
>> Especialy when there is a security rele
Anthony Towns wrote:
> Yeah; vi not behaving like vi by default seems like a showstopper.
I don't understand why. Debian is a GNU/Linux system, not a UNIX system.
Even such simple things as our "echo" command do not behave exactly as
POSIX dictates and classic UNIX does; we've generally, I think,
Andrew Suffield wrote:
On Fri, Dec 23, 2005 at 02:31:19PM -0500, Benjamin Seidenberg wrote:
Andrew Suffield wrote:
On the other hand, I think there might be some benefit to requiring
that the Maintainer field must always denote one single Debian
developer, who would be the "buck stops
Joey Hess wrote:
>
>[1] It's hard to say for sure since the i386 netinst CD is already too
>big for some installation methods and we haven't figured out if
>we're going to trim it back down, or drop it.
Ouch. I'd hope that the netinst should still work. As/when/if we can
drop 2.4 kernels t
On Fri, Dec 23, 2005 at 02:31:19PM -0500, Benjamin Seidenberg wrote:
> Andrew Suffield wrote:
>
> >On the other hand, I think there might be some benefit to requiring
> >that the Maintainer field must always denote one single Debian
> >developer, who would be the "buck stops here" guy for that
> >
In article <[EMAIL PROTECTED]> you wrote:
> Will that work for sockets?
or mmaped files? (however not sure if there are any on early boot).
Like /var/run/samba/*.tdb
Greetings
Bernd
--
To UNSUBSCRIBE, email to [EMAIL PROTECTED]
with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED
On Fri, Dec 23, 2005 at 02:02:28PM +, Paul Hedderly wrote:
> On Sun, Dec 18, 2005 at 08:56:42PM +0200, Lars Wirzenius wrote:
> >
> > I'm one of the people who prefers nvi over vim. I do so quite strongly,
> > because I find that nvi obeys my fingers and vim does not. The
>
> Sounds like you s
Package: wnpp
Severity: wishlist
* Package name: polymer
Version : 0.3.2
Upstream Author : Adam Jakubek <[EMAIL PROTECTED]>
* URL or Web page : http://static.int.pl/~mig21/dev/releases/polymer/
* License : GPL
Description : a pure QT3 theme engine without requiring KD
Eric Dorland wrote:
but this
change is the sort of thing that will help the change perception of
Debian for people who think we're a bunch of crazies.
Wait...is that an arguement for or against? ;-)
Benjamin
signature.asc
Description: OpenPGP digital signature
Miquel van Smoorenburg wrote:
> Well, it appears there's MS_MOVE support in 2.4 too, since 2.4.19.
mount --move doesn't work here (2.4.27)
> Well actually, perhaps we should not even use mount --move. Just
> copying the files is enough:
Will that work for sockets?
--
see shy jo
signature.asc
Andrew Suffield wrote:
On the other hand, I think there might be some benefit to requiring
that the Maintainer field must always denote one single Debian
developer, who would be the "buck stops here" guy for that
package. Not an applicant, not a mailing list, and not a group of
people. I believe
Stefano Zacchiroli wrote:
> But still, people have complained in this thread about a size increase
> of about 370 Kb (nvi vs vim-tiny + vim-common), moving towards vim +
> vim-common would mean an *additional* 340 Kb size increase. Is this
> still considered a fair increase by the installer/cd team
On Tue, Dec 20, 2005 at 01:59:55PM -0600, Steve Greenland wrote:
> On 19-Dec-05, 09:21 (CST), Theodore Ts'o <[EMAIL PROTECTED]> wrote:
> > Specifically, what I would propose is /etc/localtime.conf contain
> > something like "US/Eastern", and let /etc/zoneinfo be a copy of the
> > file /usr/share/z
Thomas Hood wrote:
And that is probably not what I would expect. What about doing something
like this...
NOLOGIN=boot nologin exists during boot
NOLOGIN=always nologin always exists
NOLOGIN=never nologin never exists
That would be fine if we were adding a new feature, but I am trying
to m
On Tue, Dec 20, 2005 at 02:37:59PM +1000, Anthony Towns wrote:
>
> Yeah; vi not behaving like vi by default seems like a showstopper.
But that is not the case. vi by default not acting like a very old and
(imho) broken version of vi... is not a showstopper.
I love vi - and I love the progress vi
On Sun, Dec 18, 2005 at 08:56:42PM +0200, Lars Wirzenius wrote:
>
> I'm one of the people who prefers nvi over vim. I do so quite strongly,
> because I find that nvi obeys my fingers and vim does not. The
Sounds like you should file a bug against your fingers then.
> differences are minute, of c
> And that is probably not what I would expect. What about doing something
> like this...
>
> NOLOGIN=boot nologin exists during boot
> NOLOGIN=alwaysnologin always exists
> NOLOGIN=never nologin never exists
That would be fine if we were adding a new feature, but I am trying
to modify
Package: wnpp
Severity: wishlist
Owner: Sune Vuorela <[EMAIL PROTECTED]>
* Package name: comixcursors
Version : 0.3.2
Upstream Author : Jens Luetkens
* URL : http://kde-look.org/content/show.php?content=32627
* License : GPL
Description : X11 mouse theme
Em Sex, 2005-12-23 às 00:46 +0100, Raphael Hertzog escreveu:
> On Thu, 22 Dec 2005, Daniel Ruoso wrote:
> > So, the nicest way is to create yet another subsystem that would manage
> > this type of information, and once many people starts putting
> > information there, the PTS will include it also..
Anyone see any problems with this scheme? Any better ideas?
This might be a silly question, but what would happen if DELAYLOGIN=yes
and /var/lib/initscripts/nologin does not exist?
I surmise that it's created somewhere in runmefirst. After all, the
usual state of a running system is tha
On Fri, Dec 23, 2005 at 08:40:22AM +0100, Adrian von Bidder wrote:
> The other side, and we've seen some people say this in this thread already,
> is that even if a maintainer asks for help, he may not get any - IIRC nis
> was one such package, and I claim that its still used by quite a few, so
Henrique de Moraes Holschuh wrote:
> How well that works with /var in a separate partition?
It should work fine because S55bootmisc.sh runs after S45mountnfs.sh.
--
Thomas
--
To UNSUBSCRIBE, email to [EMAIL PROTECTED]
with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
Here's a small sinopsys:
1. There is a need for a directory that is writeable *very* early in the
boot process. The alternative is complex and probably far more
undesireable (running daemon that implements a very simplified
filesystem-like interface and keeps all data in memory. Also
On Thu, 22 Dec 2005, Thomas Hood wrote:
> 2. One thing I would like to do in this release is to remove the
> dynamically created/deleted /etc/nologin file from the root filesystem.
> It is proposed that initscripts create and delete the nologin flag file
> in /var/lib/initscripts/ and that /etc/nol
On Thu, Dec 22, 2005 at 10:43:34AM +0100, Thijs Kinkhorst wrote:
> On Thu, 2005-12-22 at 08:38 +, Andrew Suffield wrote:
> > On the other hand, I think there might be some benefit to requiring
> > that the Maintainer field must always denote one single Debian
> > developer, who would be the "bu
Osamu Aoki <[EMAIL PROTECTED]> wrote:
> Hi,
>
>> Osamu Aoki <[EMAIL PROTECTED]> wrote:
> ...
>> > I think one to ease tension is to make tetex packages to coexist in
>> > archive just like many gcc.
[...]
> I should have been clear. I wish them to coexist only in "archive" but
> they can conflic
Package: wnpp
Severity: wishlist
* Package name: projectmanager.app
Version : 0.1.2
Upstream Author : Sašo Kiselkov <[EMAIL PROTECTED]>
* URL : http://pmanager.sf.net/
* License : GNU GPL v2
Description : Simple IDE for GNUstep
ProjectManager is an integr
On Fri, Dec 23, 2005 at 12:40:40PM +1000, Anthony Towns wrote:
> > I don't like downgrading the vim -> vim-runtime dependency since IMO if
> > a user apt-get-installs vim he expect a fully working vim installation
> > (including help and syntax highlighting).
> Right; but having vim Depends: vim-ba
I fully support your campaign Lars. I've ever been willing to write
automatic tests for a lot of packages of mine. And even a large subset
of them (all OCaml related ones for example) can benefit of the very
same test applied to them. I never added the test simply because there
is no infrastructure
On Tue, 20 Dec 2005, Daniel Schepler wrote:
Hi,
> Yes, a Makefile with
> all:
> echo 'foo'\
> 'bar'
>
> will pass to the shell:
> (old make) echo 'foo''bar'
> (new make) echo 'foo'\
> 'bar'
>
> And both will echo a single word.
Unfortunatelly that's not true: the sarge version of m
40 matches
Mail list logo
