Re: Need help: Idle X-user?

Dennis Stampfer [EMAIL PROTECTED] writes: timeoutd loggs user out when they reached timeout-restrictions like max. login-time, max. idle-time, etc. Is there any way to querry how long a X-user is idle? You might look at the xscreensaver driver source; the basic answer is yes, about four of

Accepted lm-sensors 2.8.1-2 (i386 source all)

-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 Format: 1.7 Date: Sat, 15 Nov 2003 11:45:16 -0500 Source: lm-sensors Binary: sensord lm-sensors-source libsensors-dev libsensors2 lm-sensors Architecture: source all i386 Version: 2.8.1-2 Distribution: unstable Urgency: low Maintainer: David Z Maze

Re: Library packages and their use

[EMAIL PROTECTED] (Otto Wyss) writes: The discussion about the libc6-dev package and its headers let me to the impression that the Debian package structure isn't optimal for libraries. If anyone wants to build his own version of a package (i.e. libwxgtk2.4) he has to get all the dependent

Accepted i2c 2.8.1-1 (all source)

-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 Format: 1.7 Date: Sun, 9 Nov 2003 17:49:02 -0500 Source: i2c Binary: i2c-source Architecture: source all Version: 2.8.1-1 Distribution: unstable Urgency: low Maintainer: David Z Maze [EMAIL PROTECTED] Changed-By: David Z Maze [EMAIL PROTECTED

Accepted lm-sensors 2.8.1-1 (i386 source all)

-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 Format: 1.7 Date: Sun, 9 Nov 2003 20:03:48 -0500 Source: lm-sensors Binary: sensord lm-sensors-source libsensors-dev libsensors2 lm-sensors Architecture: source all i386 Version: 2.8.1-1 Distribution: unstable Urgency: low Maintainer: David Z Maze

Bug#219172: RFA: lm-sensors, i2c

Package: wnpp Severity: normal I'm looking for someone to take over maintenance of the lm-sensors hardware monitoring package, along with the corresponding i2c interface kernel modules. These two packages have the same upstream and they're pretty closely related, so it'd be nice if they had the

Re: Question about libcdda_paranoia

Henning Moll [EMAIL PROTECTED] writes: But now i am in a bit of trouble: i packaged a woody backport of k3b. This programm tries to dlopen (=at runtime) 'libcdda_paranoia.so'. But that is only possible if package 'libcdparanoia0-dev' is installed. This would mean a dependency to a

Accepted lm-sensors 2.8.0-2 (i386 source all)

-sensors-2.4.22-1-k6 sensord libsensors2 lm-sensors-2.4.22-1-586tsc Architecture: source i386 all Version: 2.8.0-2 Distribution: unstable Urgency: low Maintainer: David Z Maze [EMAIL PROTECTED] Changed-By: David Z Maze [EMAIL PROTECTED] Description: libsensors-dev - Lm-sensors development kit

Accepted i2c 2.8.0-2 (i386 source all)

: 2.8.0-2 Distribution: unstable Urgency: low Maintainer: David Z Maze [EMAIL PROTECTED] Changed-By: David Z Maze [EMAIL PROTECTED] Description: i2c-2.4.22-1-386 - drivers for the i2c bus i2c-2.4.22-1-586tsc - drivers for the i2c bus i2c-2.4.22-1-686 - drivers for the i2c bus i2c-2.4.22-1-686-smp

Re: Building kernel modules for stock kernels is a hell of a job!

Henning Makholm [EMAIL PROTECTED] writes: Scripsit Manoj Srivastava [EMAIL PROTECTED] He said use the kernel-headers package, not kernel-package. Any debian packaged module shall work with something like: ./debian/rules KVERS=2.4.21 KSRC=/usr/src/kernel-headers-2.4.21

Re: To what extent should Debian modify the kernel? (Re: Debian should not modify the kernels!)

Herbert Xu [EMAIL PROTECTED] writes: Matt Zimmerman [EMAIL PROTECTED] wrote: So, I'm curious why you chose to make it a part of the Debian kernel source, rather than a separate patch (kernel-patch-ipsec or such). Well the reason for it to be in the default kernel-source is simple: The

Accepted i2c 2.8.0-1 (i386 source all)

: 2.8.0-1 Distribution: unstable Urgency: low Maintainer: David Z Maze [EMAIL PROTECTED] Changed-By: David Z Maze [EMAIL PROTECTED] Description: i2c-2.4.21-4-386 - drivers for the i2c bus i2c-2.4.21-4-586tsc - drivers for the i2c bus i2c-2.4.21-4-686 - drivers for the i2c bus i2c-2.4.21-4-686-smp

Accepted lm-sensors 2.8.0-1 (i386 source all)

-686-smp libsensors2 lm-sensors-2.4.21-4-386 lm-sensors-2.4.21-4-686 Architecture: source i386 all Version: 2.8.0-1 Distribution: unstable Urgency: low Maintainer: David Z Maze [EMAIL PROTECTED] Changed-By: David Z Maze [EMAIL PROTECTED] Description: libsensors-dev - Lm-sensors development kit

Accepted xcircuit 3.1.19-1 (i386 source)

-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 Format: 1.7 Date: Sun, 24 Aug 2003 09:08:10 -0400 Source: xcircuit Binary: xcircuit Architecture: source i386 Version: 3.1.19-1 Distribution: unstable Urgency: low Maintainer: David Z Maze [EMAIL PROTECTED] Changed-By: David Z Maze [EMAIL PROTECTED

Re: Building kernel modules for stock kernels is a hell of a job!

. :-/ People, stock kernels are very comfortable, but building modules for them is not! Please tell me what I did wrong, or make the procedure a lot easier! (The latter especially applies to the maintainers of that NVIDIA package...) Luckily, David Z. Maze has the lm-sensors as binary package

Accepted xcircuit 3.1.18-1 (i386 source)

-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 Format: 1.7 Date: Sat, 9 Aug 2003 10:59:26 -0400 Source: xcircuit Binary: xcircuit Architecture: source i386 Version: 3.1.18-1 Distribution: unstable Urgency: low Maintainer: David Z Maze [EMAIL PROTECTED] Changed-By: David Z Maze [EMAIL PROTECTED

Re: How to install X-Chat in five hours (or more)

Frederik Rousseau [EMAIL PROTECTED] writes: I really think aptitude should only show end user packages with decent, readable, localised names (Apache Web Server, x Chat (IRC Client), Infrared Control for XMMS). At the moment the user is completely overwhelmed by the list of packages, which is

Re: libraries being removed from the archive

Chris Cheney [EMAIL PROTECTED] writes: IMHO we need to make an addition to policy stating that an old lib can not be removed from the archive until no other packages still depend on it. So say I maintain foo. The source package produces two binary packages, foo and libfoo1. Now, there's a

Re: Bug#203588: acpid: Shell script has nothing to do in /etc

Cajus Pollmeier [EMAIL PROTECTED] writes: On Donnerstag, 31. Juli 2003 07:24, Pierre THIERRY wrote: Severity: serious Justification: Policy 9.1.1 (Debian should obey the FHS; I don't claim to be an FHS expert, but all it seems to say about /etc is no binaries, which this doesn't violate.)

Re: Future releases of Debian

Jamin W. Collins [EMAIL PROTECTED] writes: On Thu, Jul 24, 2003 at 08:25:16PM +0200, Robert Lemmen wrote: me too! any package that doesn't build on m68k or arm is broken and needs to be fixed, even if it works on x86 by chance! So, are you volunteering to help those of us without access to

Re: Kernel build dependencies for prepackaged modules

Herbert Xu [EMAIL PROTECTED] writes: How many Debian users are there that will use lm-sensors and i2c modules for a prepackaged kernel on a non-i386 architecture? I've had at least one user ask me about support for powerpc, which is the big thing that's driving me to ask. If it makes you

Kernel build dependencies for prepackaged modules

My kernel module packages (lm-sensors and i2c) both build-depend on kernel-build-2.4.20-1, which provides enough bits to build packages (as far as I can tell, successfully). Problem is, evidence suggests that kernel-build-2.4.20-1 is i386-only. I'm looking at moving to 2.4.21, but

Accepted lm-sensors 2.7.0-6 (i386 source all)

-sensors-2.4.20-3-686-smp lm-sensors-2.4.20-3-586tsc lm-sensors-2.4.20-3-386 Architecture: source i386 all Version: 2.7.0-6 Distribution: unstable Urgency: low Maintainer: David Z Maze [EMAIL PROTECTED] Changed-By: David Z Maze [EMAIL PROTECTED] Description: libsensors-1debian1 - Library to read

Accepted i2c 2.7.0-4 (i386 source all)

: 2.7.0-4 Distribution: unstable Urgency: low Maintainer: David Z Maze [EMAIL PROTECTED] Changed-By: David Z Maze [EMAIL PROTECTED] Description: i2c-2.4.20-3-386 - drivers for the i2c bus i2c-2.4.20-3-586tsc - drivers for the i2c bus i2c-2.4.20-3-686 - drivers for the i2c bus i2c-2.4.20-3-686-smp

Accepted lm-sensors 2.7.0-5 (i386 source all)

-sensors-2.4.20-3-686-smp lm-sensors-2.4.20-3-586tsc lm-sensors-2.4.20-3-386 Architecture: source i386 all Version: 2.7.0-5 Distribution: unstable Urgency: low Maintainer: David Z Maze [EMAIL PROTECTED] Changed-By: David Z Maze [EMAIL PROTECTED] Description: libsensors-1debian1 - Library to read

Re: Bug#194938: ITP: drivel -- A LiveJournal client for the GNOME desktop

Josselin Mouette [EMAIL PROTECTED] writes: Le mar 27/05/2003 à 20:42, Neil McGovern a écrit : Description : A LiveJournal client for the GNOME desktop Drivel is a LiveJournal.com client for the GNOME desktop. It supports all livejournal-based servers, and allows you to perform most

Accepted lm-sensors 2.7.0-4 (i386 source all)

-sensors-2.4.20-1-k7-smp lm-sensors-2.4.20-1-686 lm-sensors-2.4.20-1-586tsc Architecture: source i386 all Version: 2.7.0-4 Distribution: unstable Urgency: low Maintainer: David Z Maze [EMAIL PROTECTED] Changed-By: David Z Maze [EMAIL PROTECTED] Description: libsensors-1debian1 - Library to read

Re: Maintaining kernel source in sarge

Ola Lundqvist [EMAIL PROTECTED] writes: Kernel module policy: - * Kernel modules must be provided as a binary source package. * Module source packages should provide a debian/rules file. * The debian/rules file must compile the module if KSRC=kernelsourcedir and

Re: ABI change in libsensors1 (from lm-sensors)

Chris Cheney [EMAIL PROTECTED] writes: Why not kick upstream into releasing 2.7.1 with proper soname bump to libsensors2 (Make sure they are aware they screwed up...). Then upload libsensors2, there are only 8 sources depending on libsensors1 now so it wouldn't be a big deal to rebuild those

Re: Bug marked as done messages to-be-MIMEified?

Adrian 'Dagurashibanipal' von Bidder [EMAIL PROTECTED] writes: Q: is content-disposition handled properly, especially for messag/rfc822 type attachments? (Or if not, are message attachments displayed inline by default?) Gnus: yes (since 5.8.0, the first MIME-aware version) (Yes,

Re: ABI change in libsensors1 (from lm-sensors)

Steve Langasek [EMAIL PROTECTED] writes: On Mon, May 12, 2003 at 01:45:30PM -0400, David Z Maze wrote: (a) Repackaging lm-sensors 2.6.5, which would just have libsensors1 1:2.6.5-1, which in turn would Conflict: with any packages that have compiled against libsensors1 2.7.0 (AFAIK

Accepted xcircuit 3.0rev8-1 (i386 source)

-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 Format: 1.7 Date: Sun, 19 Jan 2003 10:57:32 -0500 Source: xcircuit Binary: xcircuit Architecture: source i386 Version: 3.0rev8-1 Distribution: unstable Urgency: low Maintainer: David Z Maze [EMAIL PROTECTED] Changed-By: David Z Maze [EMAIL PROTECTED

Accepted xcircuit 3.0rev7-1 (i386 source)

-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 Format: 1.7 Date: Wed, 18 Dec 2002 23:58:36 -0500 Source: xcircuit Binary: xcircuit Architecture: source i386 Version: 3.0rev7-1 Distribution: unstable Urgency: low Maintainer: David Z Maze [EMAIL PROTECTED] Changed-By: David Z Maze [EMAIL PROTECTED

Using kernel-build packages to autobuild modules

The perennial wart on the side of kernel module packages is that it's a big pain to auto-build modules for the stock kernels. It looks like the 2.4.20 kernel packages now include a kernel-build package, which advertises that it contains everything you need to do module builds. Is there a good way

Re: Bug#171555: ITP: kernel-patch-sensors Hardware health monitoring tool (kernel patch) . This package contains two kernel patches. For 2.4.19 and 2.4.20.

Robert Nagy [EMAIL PROTECTED] writes: * Package name: kernel-patch-sensors Version : 2.6.5 Upstream Author : The Lm_sensors Group [EMAIL PROTECTED] * URL : http://www2.lm-sensors.nu/~lm78/ * License : GPL Description : Lm-sensors is a hardware health

Accepted lm-sensors 2.6.5-3 (i386 source all)

-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 Format: 1.7 Date: Sun, 24 Nov 2002 12:01:48 -0500 Source: lm-sensors Binary: sensord lm-sensors-source libsensors-dev libsensors1 lm-sensors Architecture: source i386 all Version: 2.6.5-3 Distribution: unstable Urgency: low Maintainer: David Z Maze

Accepted i2c 2.6.5-3 (all source)

-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 Format: 1.7 Date: Sun, 24 Nov 2002 14:51:25 -0500 Source: i2c Binary: i2c-source Architecture: source all Version: 2.6.5-3 Distribution: unstable Urgency: low Maintainer: David Z Maze [EMAIL PROTECTED] Changed-By: David Z Maze [EMAIL PROTECTED

Accepted xcircuit 3.0rev4-1 (i386 source)

-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 Format: 1.7 Date: Sat, 23 Nov 2002 10:24:39 -0500 Source: xcircuit Binary: xcircuit Architecture: source i386 Version: 3.0rev4-1 Distribution: unstable Urgency: low Maintainer: David Z Maze [EMAIL PROTECTED] Changed-By: David Z Maze [EMAIL PROTECTED

Accepted lm-sensors 2.6.5-2 (i386 source all)

-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 Format: 1.7 Date: Tue, 12 Nov 2002 00:09:53 -0500 Source: lm-sensors Binary: sensord lm-sensors-source libsensors-dev libsensors1 lm-sensors Architecture: source i386 all Version: 2.6.5-2 Distribution: unstable Urgency: low Maintainer: David Z Maze

Accepted i2c 2.6.5-2 (all source)

-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 Format: 1.7 Date: Fri, 8 Nov 2002 22:12:00 -0500 Source: i2c Binary: i2c-source Architecture: source all Version: 2.6.5-2 Distribution: unstable Urgency: low Maintainer: David Z Maze [EMAIL PROTECTED] Changed-By: David Z Maze [EMAIL PROTECTED

Accepted i2c 2.6.5-1 (all source)

-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 Format: 1.7 Date: Thu, 31 Oct 2002 22:36:30 -0500 Source: i2c Binary: i2c-source Architecture: source all Version: 2.6.5-1 Distribution: unstable Urgency: low Maintainer: David Z Maze [EMAIL PROTECTED] Changed-By: David Z Maze [EMAIL PROTECTED

Re: How to put files at a location determined at install-time.

Marc L de Bruin [EMAIL PROTECTED] writes: MLdB What I am trying to build are a couple of packages (let's call one of MLdB these mydata.deb) containing just ordinary files, related to a MLdB specific application. All these packages Depend on a generic MLdB configuration package. This configuration

Re: An Idea/RFP: x group /

Andreas Rottmann [EMAIL PROTECTED] writes: AR Wht about a package that contains the following commands (yet to be AR written): AR AR xuseradd user # Add's the user to the x group AR xuserdel user # Deletes the user from the x group AR AR The package would have an config file where it lists all

Re: Deselect problems.

Steve Dunham [EMAIL PROTECTED] writes: SD Hamish Moffatt [EMAIL PROTECTED] writes: HM On Mon, Jan 05, 1998 at 08:59:50AM +0800, Lindsay Allen wrote: LA The kernel-source-2.0.32 deb has a 130K diff file against the LA standard source. Just where do these patches come from and why LA are

Re: PGP pack.

Massimo Lusetti [EMAIL PROTECTED] writes: ML I wish only know if out there's a .deb for PGP 2.6.3i ... tnx Read ftp://ftp.debian.org/debian/README.pgp. -- _ / \ The cat's been in the box for over | David Maze | 20

/debian/project/experimental in dftp

Is there any way to get directories that don't have the normal architecture structure, i.e. project/experimental, to show up in dselect using the ftp backend? (I at least want the Packages file to get loaded when I press [U]pdate...) -- _ /