Re: ITP memlockd

On Friday 09 February 2007 10:43, Brian May <[EMAIL PROTECTED]> wrote: > How much memory typically needs to be locked for this to be > beneficial? It's best to have the shell used by the sysadmin, the login chain (getty + login or sshd and the PAM stuff), some utilities (EG busybox), and all shar

Re: /foo has been mounted xx times... check forced

On Thu, Feb 08, 2007 at 10:24:14PM -0500, Theodore Tso wrote: > > You do need a mounted /proc at that time, though, which may be the > > reason it's not working for you. > A mounted /proc and if ACPI has been built using modules, the ACPI > battery module needs to be installed, since that's how we

Re: Bug#409875: cannot setup device-mapper mapping ontop of /dev/md* device

Executive summary: dmsetup / cryptsetup both fail to create a mapping on top of a raid device (/dev/md0 in this case). For much more details, see the bug report, any help appreciated as I'm out of ideas on how to diagnose the error: http://bugs.debian.org/409875 -- David Härdeman -- To UNS

Nesta Semana na Compwork - Imbativel

Caso não visualize este e-mail clique aqui MP3 Player 512MB Preto c/ Prata Cyber R$ 135,36 ou 3x R$ 45,12 Teclado e Mouse Ópico PS2 s/ Fio A4TECH KBS-1527RP R$ 174,31 ou 3x R$ 58,10 Nobreak SMS Manager NET3+ USM 1400VA Bifx 115 Cinza R$ 459,00 ou 3x R$ 153,00 Wireless Broadband Router 54MBPS

Re: ITP memlockd

On Fri, Feb 09, 2007 at 08:57:19AM +1100, Russell Coker wrote: > memlockd - daemon to lock files into RAM > > When a system starts paging excessively it may be impossible for the sysadmin > to login for the purpose of killing the runaway processes (sometimes the > login program times out due to

Re: [Pkg-cryptsetup-devel] Bug#409875: cannot setup device-mapper mapping ontop of /dev/md* device

On Fri, February 9, 2007 11:45, Loic Minier said: > On Thu, Feb 08, 2007, David Härdeman wrote: >> dmsetup / cryptsetup both fail to create a mapping on top of a raid >> device (/dev/md0 in this case). > > I don't know where the error lies, but I created two loop devices loop0 > and loop1, added

Problem resolving bug http://bugs.debian.org/407494

Hi All! I've been trying to figure out why caudium dont work with the current pike7.6 package (7.6.93) but there is not much progress at this time, I've tried contacting the debian maintainer and the caudium community but no real progress with that. Is there any possibility at this time to

Re: [Pkg-cryptsetup-devel] Bug#409875: cannot setup device-mapper mapping ontop of /dev/md* device

On Fri, 09 Feb 2007, David Härdeman wrote: > > On Thu, Feb 08, 2007, David Härdeman wrote: > >> dmsetup / cryptsetup both fail to create a mapping on top of a raid > >> device (/dev/md0 in this case). > > > > I don't know where the error lies, but I created two loop devices loop0 > > and loop1, a

NEW queue frozen?

Hi, Is the NEW queue frozen or something? Currently 190 packages are waiting in NEW. I've only noticed this since I'm waiting for the current version of libgpod which is needed to get (not only) my IPod working again with Amarok from experimental. Sorry if this has been announced/explained elsewh

Re: NEW queue frozen?

Bastian Venthur wrote: > Hi, > > Is the NEW queue frozen or something? Currently 190 packages are waiting > in NEW. I've only noticed this since I'm waiting for the current version > of libgpod which is needed to get (not only) my IPod working again with > Amarok from experimental. > > Sorry if t

RFC: use readable $(cmd) syntax instead of unreadable `cmd`

FOREWORD I have seen following construct to be used in shell-context (makefiles, sh-scripts, Perl): `cmd` [1] However, the POSIX standard and SUSv[23] declares alternative way of accomplishing the same with in *sh context: $(cmd) [2] I would see following probl

Re: RFC: use readable $(cmd) syntax instead of unreadable `cmd`

On Fre, 09 Feb 2007, Jari Aalto wrote: > I'm askinf if it is ok to to reopen such bugs based of better QA > aspects. Possibly by providing patches if the maintainer is busy > elsewhere to handle such a "minor issue" from his perspective. I would leave it to the discretion of the developer what not

Re: RFC: use readable $(cmd) syntax instead of unreadable `cmd`

On pe, 2007-02-09 at 20:11 +0200, Jari Aalto wrote: > I'm askinf if it is ok to to reopen such bugs based of better QA > aspects. It's a matter of style and taste. Unless you can quote verifiable statistics that using backticks instead of $() is causing problems (that is, bug numbers), let it be.

Re: RFC: use readable $(cmd) syntax instead of unreadable `cmd`

On 2007-02-09, Jari Aalto <[EMAIL PROTECTED]> wrote: > - The backtick version is not easily readable in high resolution screens > or in terminals with small fonts Solution: get glasses. > - There may be problems in distinguishing character ' from ` with sme > particularly sel

Re: NEW queue frozen?

On 10925 March 1977, Bastian Venthur wrote: > Is the NEW queue frozen or something? No, its not that cold yet. -- bye Joerg I'm James Troup, long term source of all evil in Debian. you may know me from such debian-devel-announce gems as "Serious Problems With " -- To UNS

about gstreamer0.8 and python2.3 removal

Hi, It's been a while since someone mentioned removal of gst0.8 and py2.3 and wonder what's going on. -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]

Re: about gstreamer0.8 and python2.3 removal

On Fri, Feb 09, 2007, Tshepang Lekhonkhobe wrote: > It's been a while since someone mentioned removal of gst0.8 and py2.3 > and wonder what's going on. Concerning GStreamer 0.8, teatime, goobox and muine remain rdeps in unstable, so GStreamer 0.8 is kept for etch. -- Loïc Minier <[EMAIL PROTEC

Re: about gstreamer0.8 and python2.3 removal

On Fri, 2007-02-09 at 20:57 +0200, Tshepang Lekhonkhobe wrote: > Hi, > > It's been a while since someone mentioned removal of gst0.8 and py2.3 > and wonder what's going on. python2.3 is no more, as of a month ago today: python2.3 | 2.3.5-3sarge1 |stable | source, alpha, arm, hppa, i386,

Re: about gstreamer0.8 and python2.3 removal

On 2/9/07, Loïc Minier <[EMAIL PROTECTED]> wrote: On Fri, Feb 09, 2007, Tshepang Lekhonkhobe wrote: > It's been a while since someone mentioned removal of gst0.8 and py2.3 > and wonder what's going on. Concerning GStreamer 0.8, teatime, goobox and muine remain rdeps in unstable, so GStreamer 0

How many packages in Sid should reach Etch?

Hi, The useful bjorn,haxx.se/debian lists nearly 2000 packages trying to enter Testing which keeps on growing these days due to manual hinting of course. By I actually wonder if the release team is able to keep up. I know there's certain kinds of packages never meant to reach Testing, but is ther

Re: about gstreamer0.8 and python2.3 removal

On Fri, Feb 09, 2007, Tshepang Lekhonkhobe wrote: > Pretty surprising. Was there a discussion in which this decision was > made or is this just the assumed position? -- Loïc Minier <[EMAIL PROTECTED]> -- To UNSUBSCRIBE, email

Re: RFC: use readable $(cmd) syntax instead of unreadable `cmd`

Jari Aalto wrote: > > I have seen following construct to be used in shell-context > (makefiles, sh-scripts, Perl): > > `cmd` [1] > > However, the POSIX standard and SUSv[23] declares alternative way of > accomplishing the same with in *sh context: > > $(cmd) [2] The

Re: Bug#409875: [Pkg-cryptsetup-devel] Bug#409875: bug #409875

reassign 409875 libdevmapper1.02 retitle 409875 libdevmapper should provide more helpful error messages severity 409875 minor thanks On Fri, Feb 09, 2007 at 09:44:32PM +0100, Johannes Schlumberger wrote: Thanks, this looks mighty suspicious...it looks like /dev/md0 is mounted as your root partit

Re: RFC: use readable $(cmd) syntax instead of unreadable `cmd`

On Feb 09, Jari Aalto <[EMAIL PROTECTED]> wrote: > I have reported bugs against backtick and suggested to change to use > the more readable alternative. The result was surprising. To quote > one message (bug closed reasoning): > > "If your development environment cannot display ` differently

Re: RFC: use readable $(cmd) syntax instead of unreadable `cmd`

On Fri, Feb 09, 2007 at 07:26:21PM +0100, Marco d'Itri wrote: > > I'm askinf if it is ok to to reopen such bugs based of better QA > > aspects. Possibly by providing patches if the maintainer is busy > > elsewhere to handle such a "minor issue" from his perspective. > No, it's not. Even if a patch

Re: RFC: use readable $(cmd) syntax instead of unreadable `cmd`

On Fri, 9 Feb 2007, Jari Aalto wrote: > FOREWORD > > I have seen following construct to be used in shell-context > (makefiles, sh-scripts, Perl): > > `cmd` [1] > > However, the POSIX standard and SUSv[23] declares alternative way of > accomplishing the same with in *sh co

Re: about gstreamer0.8 and python2.3 removal

On 2/9/07, Loïc Minier <[EMAIL PROTECTED]> wrote: On Fri, Feb 09, 2007, Tshepang Lekhonkhobe wrote: > Pretty surprising. Was there a discussion in which this decision was > made or is this just the assumed position? I saw that

Re: NEW queue frozen?

On ven, 2007-02-09 at 17:47 +0100, Bastian Venthur wrote: > Is the NEW queue frozen or something? Currently 190 packages are > waiting > in NEW. I've only noticed this since I'm waiting for the current > version > of libgpod which is needed to get (not only) my IPod working again > with > Amarok fr

Re: ITP memlockd

On Friday 09 February 2007 22:47, [EMAIL PROTECTED] wrote: > superb, I've wanted one of these for a long time :-) > > Other scenarios might include having a working system if the binary > images are not acccessible for some other reason such as h/w failure ?? If the kernel umounts a filesystem bec

Bug#410359: ITP: python-pudge -- documentation generator for Python projects

Package: wnpp Severity: wishlist Owner: Piotr Ozarowski <[EMAIL PROTECTED]> * Package name: python-pudge Version : 0.1.2+svn134-1 Upstream Author : Ryan Tomayko <[EMAIL PROTECTED]> * URL : http://pudge.lesscode.org/ * License : MIT Programming Lang: Python D

Re: Handling of (inactive) Debian Accounts

Hi Joerg, I know I've gone MIA for quite a long time (graduated from university and got a full-time job). I don't know if I've gotten the WaT email yet, but I'd be glad to keep my email forwarding as an emeritus account. Anyway, thanks for taking the time to clean up all the accounts, and my ap