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 them, none of which are guaranteed to be there. If not, do you think it's okay to write something like IDLE-Logout does not work with X into Readme.Debian and into the config-file(,manpage, ...)? IMHO the README.Debian file and package description should be sufficient. Mentioning it in the man page wouldn't hurt; I think splattering it in the config file is going a bit far. -- David Maze [EMAIL PROTECTED] http://people.debian.org/~dmaze/ Theoretical politics is interesting. Politicking should be illegal. -- Abra Mitchell
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 [EMAIL PROTECTED] Changed-By: David Z Maze [EMAIL PROTECTED] Description: libsensors-dev - Lm-sensors development kit libsensors2 - Library to read temperature/voltage/fan sensors lm-sensors - Utilities to read temperature/voltage/fan sensors lm-sensors-source - Kernel drivers to read temperature/voltage/fan sensors (source) sensord- Hardware sensor information logging daemon Changes: lm-sensors (2.8.1-2) unstable; urgency=low . * Use the standalone dmidecode package, which has a newer dmidecode than what lm-sensors includes. * Standards-version 3.6.1.0. (No changes) * Fix sensors-detect to work if we're using devfs, but no i2c bus driver is loaded. Files: 7220f0d1617fc4e8e7c59aa6c10e3b8b 729 utils extra lm-sensors_2.8.1-2.dsc 712e1039a6e306d7e8c0161f6a751fa4 29227 utils extra lm-sensors_2.8.1-2.diff.gz 19d795461ebdf10df3a3251fd075765c 391826 utils extra lm-sensors_2.8.1-2_i386.deb 806c46a74faa342cde80cbc361ca5be8 51820 libs optional libsensors2_2.8.1-2_i386.deb 5443a796c4a9a3bfcaff3981c1365031 69196 libdevel extra libsensors-dev_2.8.1-2_i386.deb cc47e1ebd9b71070e573c57f382feb3c 44268 utils extra sensord_2.8.1-2_i386.deb 3e07071dd27d21462a6ddbc37ad4ec70 751432 misc extra lm-sensors-source_2.8.1-2_all.deb -BEGIN PGP SIGNATURE- Version: GnuPG v1.2.3 (GNU/Linux) iD8DBQE/tmDip3U1z1PHTekRAqWcAJ42DsBReJdyatFMgjilX19sTJxEJACgqQdW hxDnihUD5J4yRrISAI2sZLw= =Hxny -END PGP SIGNATURE- Accepted: libsensors-dev_2.8.1-2_i386.deb to pool/main/l/lm-sensors/libsensors-dev_2.8.1-2_i386.deb libsensors2_2.8.1-2_i386.deb to pool/main/l/lm-sensors/libsensors2_2.8.1-2_i386.deb lm-sensors-source_2.8.1-2_all.deb to pool/main/l/lm-sensors/lm-sensors-source_2.8.1-2_all.deb lm-sensors_2.8.1-2.diff.gz to pool/main/l/lm-sensors/lm-sensors_2.8.1-2.diff.gz lm-sensors_2.8.1-2.dsc to pool/main/l/lm-sensors/lm-sensors_2.8.1-2.dsc lm-sensors_2.8.1-2_i386.deb to pool/main/l/lm-sensors/lm-sensors_2.8.1-2_i386.deb sensord_2.8.1-2_i386.deb to pool/main/l/lm-sensors/sensord_2.8.1-2_i386.deb -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
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 underlying dev packages as well. This is a long line of dependencies which mostly aren't wished and shouldn't be necessary. Why is this a problem? I don't really understand, for example, why you want to recompile libraries, or what the problem is with needing to have -dev packages installed to get header files for libraries. There are 3 kinds of dissimilar user groups of a package: 1. Users just using a library linked to other packages (...who don't want the header files, static libraries, or .so links; they're just users.) 2. Developers building packages which depends on a library package (...who need the header files, etc.) 3. Developers building his own version of this library package I don't understand this category in particular. Do you mean maintainer? Or do you really want to install home-built versions of libraries? Supporting home-built versions of system things (not just libraries, but also things like MTAs) is something Debian has traditionally been bad at; if I was going to optimize for this, I'd probably use a BSD distribution over anything Linux-based. Currently group 1 just uses the normal packages while group 2 + 3 have both to use the dev packages. Especially for group 2 this isn't a good solution leading to a long line of unnecessary dependencies. Again, what makes them unnecessary? If myapp.c includes foo/foo.h, and foo/foo.h includes bar/bar.h, then you can't compile myapp.c without having bar/bar.h around, period. Which means that, in the Debian world, you need to have libbar-dev installed, even if myapp.c doesn't include anything out of bar.h directly. Solution 1: Splitting the 2 packages into 3. Not very attractive, it will more confuse than improve the situation. Maybe the dbg packages could take over the role of the 3. group. ...what is the proposed split here? All of your proposals are kind of hand-wavy, and I really don't understand what you're getting at. Solution 2: Packages are changed that group 1 + 2 can use the normal packages and only group 3 uses the dev. That means the normal library packages contain enough so that other packages depending on this can be build. That sounds like a proposal to get rid of -dev packages entirely. Is that what you're actually proposing? I'm not sure if any of the above solutions will improve the situation but we should all try to remove dependencies wherever possible. Dependencies are bad? Yeah, there are lots of ways to get around them (static linking and the like) but they come with lots of costs (binary bloat, need to rebuild every package when libc changes). -- David Maze [EMAIL PROTECTED] http://people.debian.org/~dmaze/ Theoretical politics is interesting. Politicking should be illegal. -- Abra Mitchell
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] Description: i2c-source - sources for drivers for the i2c bus Changes: i2c (2.8.1-1) unstable; urgency=low . * New upstream release. * Disable automatic building of kernel modules; they conflict with the stock kernel in unfortunate ways. * Use debhelper v4. Files: 1f8b198f487617e44976a43ac86cdbba 580 misc extra i2c_2.8.1-1.dsc 57aab055c33a6f8fdd47051d7f01941c 129857 misc extra i2c_2.8.1.orig.tar.gz 0ffea4dc87b94782180e21e3c8d96cff 18951 misc extra i2c_2.8.1-1.diff.gz c191bb2ffd45edff0dae487894b385c2 163320 misc extra i2c-source_2.8.1-1_all.deb -BEGIN PGP SIGNATURE- Version: GnuPG v1.2.3 (GNU/Linux) iD8DBQE/rvfYp3U1z1PHTekRAghMAJ9JFDJpsaYewltvowypduXSrpjdXwCbBLQG EGNnTPfH9jqCPFcSfcfIFjQ= =GbUi -END PGP SIGNATURE- Accepted: i2c-source_2.8.1-1_all.deb to pool/main/i/i2c/i2c-source_2.8.1-1_all.deb i2c_2.8.1-1.diff.gz to pool/main/i/i2c/i2c_2.8.1-1.diff.gz i2c_2.8.1-1.dsc to pool/main/i/i2c/i2c_2.8.1-1.dsc i2c_2.8.1.orig.tar.gz to pool/main/i/i2c/i2c_2.8.1.orig.tar.gz -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [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 [EMAIL PROTECTED] Changed-By: David Z Maze [EMAIL PROTECTED] Description: libsensors-dev - Lm-sensors development kit libsensors2 - Library to read temperature/voltage/fan sensors lm-sensors - Utilities to read temperature/voltage/fan sensors lm-sensors-source - Kernel drivers to read temperature/voltage/fan sensors (source) sensord- Hardware sensor information logging daemon Closes: 208385 211955 214338 215301 216093 219260 219601 Changes: lm-sensors (2.8.1-1) unstable; urgency=low . * New upstream release. Modified sensord source to build against newer DDCMON IDs. (Closes: #208385, #219601) * Update debian/rules to call i2ccheck.pl via perl, so it doesn't matter whether or not that script is executable. (Closes: #215301) * Have libsensors2 only Suggests: lm-sensors-mod-2.8, rather than Recommends: it. The main lm-sensors package still Recommends: the kernel modules. This is so that other things can depend on the library package (of present note, libsnmp) without aptitude trying to drag in a kernel module and probably also a new kernel. (Closes: #216093) * Updated Russian Debconf translation. (Closes: #214338, #219260) * Add Japanese Debconf translation; thanks to Kenshi Muto. (Closes: #211955) * Don't build kernel modules, since building i2c modules conflicts with things in the kernel and we'd otherwise depend on those. Files: 3c8b3ec0d9bf25a956dd495e49dc47cd 729 utils extra lm-sensors_2.8.1-1.dsc 2ea0d608404aced13211174e03b1268a 703525 utils extra lm-sensors_2.8.1.orig.tar.gz a92075c3b6206c2b021c2a902980e942 28957 utils extra lm-sensors_2.8.1-1.diff.gz acdb38713e8d9349460fc255493b2fc2 401196 utils extra lm-sensors_2.8.1-1_i386.deb b5e97f4e06c4c386a9b9c055f4d9f461 51720 libs optional libsensors2_2.8.1-1_i386.deb 3e411dedff8c4ff8a791841e23aebdce 68922 libdevel extra libsensors-dev_2.8.1-1_i386.deb b2eef7fc4fe5670e7f1fee544cc3313b 44166 utils extra sensord_2.8.1-1_i386.deb 3655fbe87c522acaebdf33ec8260eac5 751148 misc extra lm-sensors-source_2.8.1-1_all.deb -BEGIN PGP SIGNATURE- Version: GnuPG v1.2.3 (GNU/Linux) iD8DBQE/rv5+p3U1z1PHTekRAmE/AKCLcfM4Rv9guWPUtSqnw7oUXePRSACfRatW wN+4TiCGQamxJqXrY433rH4= =J4it -END PGP SIGNATURE- Accepted: libsensors-dev_2.8.1-1_i386.deb to pool/main/l/lm-sensors/libsensors-dev_2.8.1-1_i386.deb libsensors2_2.8.1-1_i386.deb to pool/main/l/lm-sensors/libsensors2_2.8.1-1_i386.deb lm-sensors-source_2.8.1-1_all.deb to pool/main/l/lm-sensors/lm-sensors-source_2.8.1-1_all.deb lm-sensors_2.8.1-1.diff.gz to pool/main/l/lm-sensors/lm-sensors_2.8.1-1.diff.gz lm-sensors_2.8.1-1.dsc to pool/main/l/lm-sensors/lm-sensors_2.8.1-1.dsc lm-sensors_2.8.1-1_i386.deb to pool/main/l/lm-sensors/lm-sensors_2.8.1-1_i386.deb lm-sensors_2.8.1.orig.tar.gz to pool/main/l/lm-sensors/lm-sensors_2.8.1.orig.tar.gz sensord_2.8.1-1_i386.deb to pool/main/l/lm-sensors/sensord_2.8.1-1_i386.deb -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
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 same maintainer. Both packages involve kernel modules. The lm-sensors package also involves a shared library and a few userspace packages. I'd like to say that these are clean friendly packages; they're at least lintian-clean, and the packaging is fairly sane (and debhelperful, if that matters to you), but there are Issues... (1) lm-sensors 2.8 userspace depends on lm-sensors 2.8 kernel modules, which depend on i2c 2.8 kernel modules. But the Linux kernel has i2c 2.6 kernel modules, and mix-and-match == kernel panic. See bug #209228. I haven't figured out a good way around this yet. Also, you can't just patch the kernel to use the newer i2c modules, since i2c support bleeds over into several other kernel modules. (2) The library's soname has changed recently. This wouldn't be so bad, but lm-sensors 2.7.0 contained a different libsensors1 from lm-sensors 2.6.5, so later versions of lm-sensors 2.7.0 had a libsensors-1debian1. Upstream did fix the soname, so now lm-sensors 2.8.0 has libsensors2. But, meanwhile, kdebase has a package (ksysguardd) that got compiled against libsensors-1debian1, and went into testing (!) in spite of the corresponding libsensors never having made it. (3) Minor i18n things that I've never gotten to looking at, mostly with the output wanting to use a degree character. I haven't really been using my one machine that can use lm-sensors much, and my current housemates object to it being left on (it's loud), so I don't have good access to a machine to test it on. If you're looking at this package, you should definitely have hardware that can make use of this package, and maybe you're using it already. -- System Information: Debian Release: testing/unstable Architecture: i386 Kernel: Linux everett 2.4.21-3-everett #1 Thu Aug 7 13:20:54 UTC 2003 i686 Locale: LANG=C, LC_CTYPE=C
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 development package. Is this a bug in k3b? Should k3b try to dlopen 'libcdda_paranoia.so.0' instead? That's probably what I would do... Is there a standard for so-naming (which is respected by all/ most Gnu/Linux distributions)? Well, the actual process involved is something like this: you specify -lfoo on the ld (cc) command line; the linker finds and reads libfoo.so, and looks for the SONAME field in it; that soname (typically libfoo.so.2) is written into the binary; when the binary is loaded by ld.so, that looks for the libfoo.so.2 that was the soname. So in the normal process, you only need lib*.so at build time, and the major-version symlink at runtime. Plus, if the major version of the library chages, you'll probably need to change your program anyways. So I think explicitly writing in libcdda_paranoia.so.0 is actually the right thing to do. -- David Maze [EMAIL PROTECTED] http://people.debian.org/~dmaze/ Theoretical politics is interesting. Politicking should be illegal. -- Abra Mitchell
Accepted lm-sensors 2.8.0-2 (i386 source all)
-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 Format: 1.7 Date: Sat, 27 Sep 2003 18:03:54 -0400 Source: lm-sensors Binary: lm-sensors-2.4.22-1-686 lm-sensors-source lm-sensors-2.4.22-1-k7-smp libsensors-dev lm-sensors-2.4.22-1-k7 lm-sensors-2.4.22-1-686-smp lm-sensors lm-sensors-2.4.22-1-386 lm-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 libsensors2 - Library to read temperature/voltage/fan sensors lm-sensors - Utilities to read temperature/voltage/fan sensors lm-sensors-2.4.22-1-386 - Kernel drivers to read temperature/voltage/fan sensors lm-sensors-2.4.22-1-586tsc - Kernel drivers to read temperature/voltage/fan sensors lm-sensors-2.4.22-1-686 - Kernel drivers to read temperature/voltage/fan sensors lm-sensors-2.4.22-1-686-smp - Kernel drivers to read temperature/voltage/fan sensors lm-sensors-2.4.22-1-k6 - Kernel drivers to read temperature/voltage/fan sensors lm-sensors-2.4.22-1-k7 - Kernel drivers to read temperature/voltage/fan sensors lm-sensors-2.4.22-1-k7-smp - Kernel drivers to read temperature/voltage/fan sensors lm-sensors-source - Kernel drivers to read temperature/voltage/fan sensors (source) sensord- Hardware sensor information logging daemon Closes: 209389 Changes: lm-sensors (2.8.0-2) unstable; urgency=low . * Build vs. kernel 2.4.22-1. * Make sure libsensors.so points at libsensors.so.2. (Closes: #209389) Files: c724385fedd41b3c72da346970b11f0b 752 utils extra lm-sensors_2.8.0-2.dsc a9f660aa007ecd42bcf4f33d0ecd981e 26355 utils extra lm-sensors_2.8.0-2.diff.gz 5c1be47c9223bd04bc6b709c0c361c91 381954 utils extra lm-sensors_2.8.0-2_i386.deb 3d78b22335da876d850e464adcb16fcb 49278 libs optional libsensors2_2.8.0-2_i386.deb 1739a88d992d06631708ec46242365e2 66280 libdevel extra libsensors-dev_2.8.0-2_i386.deb 6ab442055feb8a149e98620c62779f24 42404 utils extra sensord_2.8.0-2_i386.deb 17e3f08e228e8f1ec534868dd7ef46ea 188520 utils extra lm-sensors-2.4.22-1-386_2.8.0-2_i386.deb f568b9360900a1166f26901bd35123e2 188544 utils extra lm-sensors-2.4.22-1-586tsc_2.8.0-2_i386.deb 5b7d2ff19d32bfc0d9dd6fba24ea4399 188518 utils extra lm-sensors-2.4.22-1-686_2.8.0-2_i386.deb b841b4839bd31e739bed5235156a5fc1 188866 utils extra lm-sensors-2.4.22-1-686-smp_2.8.0-2_i386.deb fa30a33e11e879df5d71adc05cfade94 188504 utils extra lm-sensors-2.4.22-1-k6_2.8.0-2_i386.deb d9dcde039880819fa48a9276ffd67cf2 188298 utils extra lm-sensors-2.4.22-1-k7_2.8.0-2_i386.deb 59908d8e7c9e3ee2610ed47f9f5f436f 188656 utils extra lm-sensors-2.4.22-1-k7-smp_2.8.0-2_i386.deb 8cc281cf2308ad3c8bf8ddfa46023aaf 716052 misc extra lm-sensors-source_2.8.0-2_all.deb -BEGIN PGP SIGNATURE- Version: GnuPG v1.2.3 (GNU/Linux) iD8DBQE/dkaHp3U1z1PHTekRAhJoAJ9jsDMZxwRo6VySKWMH63Uh3aobTgCfcHiH HsJlxlZKTnAZK4LnfermJrQ= =fa1B -END PGP SIGNATURE- Accepted: libsensors-dev_2.8.0-2_i386.deb to pool/main/l/lm-sensors/libsensors-dev_2.8.0-2_i386.deb libsensors2_2.8.0-2_i386.deb to pool/main/l/lm-sensors/libsensors2_2.8.0-2_i386.deb lm-sensors-2.4.22-1-386_2.8.0-2_i386.deb to pool/main/l/lm-sensors/lm-sensors-2.4.22-1-386_2.8.0-2_i386.deb lm-sensors-2.4.22-1-586tsc_2.8.0-2_i386.deb to pool/main/l/lm-sensors/lm-sensors-2.4.22-1-586tsc_2.8.0-2_i386.deb lm-sensors-2.4.22-1-686-smp_2.8.0-2_i386.deb to pool/main/l/lm-sensors/lm-sensors-2.4.22-1-686-smp_2.8.0-2_i386.deb lm-sensors-2.4.22-1-686_2.8.0-2_i386.deb to pool/main/l/lm-sensors/lm-sensors-2.4.22-1-686_2.8.0-2_i386.deb lm-sensors-2.4.22-1-k6_2.8.0-2_i386.deb to pool/main/l/lm-sensors/lm-sensors-2.4.22-1-k6_2.8.0-2_i386.deb lm-sensors-2.4.22-1-k7-smp_2.8.0-2_i386.deb to pool/main/l/lm-sensors/lm-sensors-2.4.22-1-k7-smp_2.8.0-2_i386.deb lm-sensors-2.4.22-1-k7_2.8.0-2_i386.deb to pool/main/l/lm-sensors/lm-sensors-2.4.22-1-k7_2.8.0-2_i386.deb lm-sensors-source_2.8.0-2_all.deb to pool/main/l/lm-sensors/lm-sensors-source_2.8.0-2_all.deb lm-sensors_2.8.0-2.diff.gz to pool/main/l/lm-sensors/lm-sensors_2.8.0-2.diff.gz lm-sensors_2.8.0-2.dsc to pool/main/l/lm-sensors/lm-sensors_2.8.0-2.dsc lm-sensors_2.8.0-2_i386.deb to pool/main/l/lm-sensors/lm-sensors_2.8.0-2_i386.deb sensord_2.8.0-2_i386.deb to pool/main/l/lm-sensors/sensord_2.8.0-2_i386.deb -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Accepted i2c 2.8.0-2 (i386 source all)
-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 Format: 1.7 Date: Sat, 27 Sep 2003 17:10:31 -0400 Source: i2c Binary: i2c-2.4.22-1-k6 i2c-2.4.22-1-386 i2c-source i2c-2.4.22-1-k7 i2c-2.4.22-1-586tsc i2c-2.4.22-1-686-smp i2c-2.4.22-1-k7-smp i2c-2.4.22-1-686 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: 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 - drivers for the i2c bus i2c-2.4.22-1-k6 - drivers for the i2c bus i2c-2.4.22-1-k7 - drivers for the i2c bus i2c-2.4.22-1-k7-smp - drivers for the i2c bus i2c-source - sources for drivers for the i2c bus Closes: 183644 210607 Changes: i2c (2.8.0-2) unstable; urgency=low . * Set MODPREF in debian/rules, so that the upstream makefile installs modules in the right place. (Closes: #183644, #210607) * Build for kernel 2.4.22-1. Files: 1683f84ca10bedd0355501c9968153bc 596 misc extra i2c_2.8.0-2.dsc 8c352df1ac467331e1f15ecb222046e4 18707 misc extra i2c_2.8.0-2.diff.gz e738fe28257eb6d5896a782b689a1332 156354 misc extra i2c-source_2.8.0-2_all.deb 96a67592e982dfacc20fb90580835409 76902 misc extra i2c-2.4.22-1-386_2.8.0-2_i386.deb fa77dffd115c27ecd7ecf99bfbabba0b 41006 misc extra i2c-2.4.22-1-586tsc_2.8.0-2_i386.deb c1d606b1ed4627fb40634c8f666da2d1 40996 misc extra i2c-2.4.22-1-686_2.8.0-2_i386.deb 0753fe9e572ba22fc74a6e246e4facea 41102 misc extra i2c-2.4.22-1-686-smp_2.8.0-2_i386.deb 413ad4327cab5b3fec7ee262d7157bd7 40986 misc extra i2c-2.4.22-1-k6_2.8.0-2_i386.deb 0a687fd58ca806a88fbdb12af925a98c 41038 misc extra i2c-2.4.22-1-k7_2.8.0-2_i386.deb 69794e2f97547cefb1a8bbb24b7a622b 41154 misc extra i2c-2.4.22-1-k7-smp_2.8.0-2_i386.deb -BEGIN PGP SIGNATURE- Version: GnuPG v1.2.3 (GNU/Linux) iD8DBQE/dgkSp3U1z1PHTekRAoByAKCEWSVl7WsQY7X+ldvlFdvG/bPtVACeMOcX TvHNNf8efKBsbqG6XHsFPoA= =SJHd -END PGP SIGNATURE- Accepted: i2c-2.4.22-1-386_2.8.0-2_i386.deb to pool/main/i/i2c/i2c-2.4.22-1-386_2.8.0-2_i386.deb i2c-2.4.22-1-586tsc_2.8.0-2_i386.deb to pool/main/i/i2c/i2c-2.4.22-1-586tsc_2.8.0-2_i386.deb i2c-2.4.22-1-686-smp_2.8.0-2_i386.deb to pool/main/i/i2c/i2c-2.4.22-1-686-smp_2.8.0-2_i386.deb i2c-2.4.22-1-686_2.8.0-2_i386.deb to pool/main/i/i2c/i2c-2.4.22-1-686_2.8.0-2_i386.deb i2c-2.4.22-1-k6_2.8.0-2_i386.deb to pool/main/i/i2c/i2c-2.4.22-1-k6_2.8.0-2_i386.deb i2c-2.4.22-1-k7-smp_2.8.0-2_i386.deb to pool/main/i/i2c/i2c-2.4.22-1-k7-smp_2.8.0-2_i386.deb i2c-2.4.22-1-k7_2.8.0-2_i386.deb to pool/main/i/i2c/i2c-2.4.22-1-k7_2.8.0-2_i386.deb i2c-source_2.8.0-2_all.deb to pool/main/i/i2c/i2c-source_2.8.0-2_all.deb i2c_2.8.0-2.diff.gz to pool/main/i/i2c/i2c_2.8.0-2.diff.gz i2c_2.8.0-2.dsc to pool/main/i/i2c/i2c_2.8.0-2.dsc -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
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 KPKG_DEST_DIR=../ KDREV=blah kdist_image Interesting. Just out of curiosity, where is that supposed to be documented? All of the information is in /usr/share/doc/kernel-package/README.modules, though not with a single command line like that as such. (Btw, is it a bug for the debian/rules in a module package to run dh_testroot from its 'build' target? I know it's not allowed in the debian/rules in a _source_ package, but perhaps the conventions for kernel-module packages are different). I don't consider it a bug. I do think the kdist and kdist_image targets should reinvoke make under $(ROOT_CMD), though, just to be sure. The i2c-source debian/rules file has: kdist_image: $(ROOT_CMD) $(MAKE) $(MFLAGS) -f debian/rules binary-modules $(ROOT_CMD) $(MAKE) $(MFLAGS) -f debian/rules clean kdist: $(ROOT_CMD) $(MAKE) $(MFLAGS) -f debian/rules binary-modules dpkg-genchanges -b -e$(KMAINT) $(KEMAIL) -u$(KSRC)/.. $(CHFILE) debsign -e$(KMAINT) $(KEMAIL) $(CHFILE) $(ROOT_CMD) $(MAKE) $(MFLAGS) -f debian/rules clean kdist_clean: $(ROOT_CMD) $(MAKE) $(MFLAGS) -f debian/rules clean ...with some magic early on in the file to figure out the name of the .changes file $(CHFILE). -- David Maze [EMAIL PROTECTED] http://people.debian.org/~dmaze/ Theoretical politics is interesting. Politicking should be illegal. -- Abra Mitchell
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 patch should be used on all default Debian kernel images unless the arch maintainer chooses to override it. That doesn't sound like it really answers the question... I suppose the more fundamental question is, what is your vision for the Debian kernel source? What do you feel belongs there, and what does not? Perhaps vision is too strong a word. I have some simple checks when it comes to patch inclusion: * Is it actively maintained by someone? * If it's a feature, can it be disabled/enabled at runtime? * If it's a bug fix, how bad are its side-effects? * What size impact does it have to the binary kernel image? ...do you include *everything* that comes by you that meets these criteria? Because from this it sounds like anything that has an upstream that can be built as modules would be included. My particular directed thought right now is a somewhat invasive patch that updates the 2.4 kernels to use i2c-2.8, which would solve some headaches for me (somewhat invasive, in that it also goes off and modifies all of the other drivers that depend on i2c); if I were the kernel maintainer, it'd trip a too different from kernel.org flag for me, but it sounds like it does meet your four criteria here. -- David Maze [EMAIL PROTECTED] http://people.debian.org/~dmaze/ Theoretical politics is interesting. Politicking should be illegal. -- Abra Mitchell
Accepted i2c 2.8.0-1 (i386 source all)
-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 Format: 1.7 Date: Mon, 1 Sep 2003 09:31:07 -0400 Source: i2c Binary: i2c-2.4.21-4-k7-smp i2c-2.4.21-4-386 i2c-source i2c-2.4.21-4-586tsc i2c-2.4.21-4-k6 i2c-2.4.21-4-686-smp i2c-2.4.21-4-k7 i2c-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: 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 - drivers for the i2c bus i2c-2.4.21-4-k6 - drivers for the i2c bus i2c-2.4.21-4-k7 - drivers for the i2c bus i2c-2.4.21-4-k7-smp - drivers for the i2c bus i2c-source - sources for drivers for the i2c bus Changes: i2c (2.8.0-1) unstable; urgency=low . * New upstream version. Only works with kernel 2.4, not 2.2 or 2.6. * Upstream changed the module ABI; building modules now provides i2c-mod-2.8. * Build vs. kernel-build 2.4.21-4. * In the top-level Makefile, rename 'install' target to 'install-upstream' to avoid an unwanted call to depmod. This doesn't otherwise affect the package installation. Files: f13c6f4d8fcc617957b7695820415257 596 misc extra i2c_2.8.0-1.dsc b93f04a533cd783b1a1207c96596e736 123607 misc extra i2c_2.8.0.orig.tar.gz ef48087eea8e7791d68fc1c4b5303738 18614 misc extra i2c_2.8.0-1.diff.gz 67d377dbba4633b1c9a5df2b43afe592 156184 misc extra i2c-source_2.8.0-1_all.deb 0f6f44fc9f6e9b2490e234675c324f59 76434 misc extra i2c-2.4.21-4-386_2.8.0-1_i386.deb 2c9ab02b3dbde4cd864967d7be681a00 40578 misc extra i2c-2.4.21-4-586tsc_2.8.0-1_i386.deb e2b6d910d704db3401faaaed5cfe3e91 40584 misc extra i2c-2.4.21-4-686_2.8.0-1_i386.deb 02b50b80bc735ef5f416f0d5185fbd57 40732 misc extra i2c-2.4.21-4-686-smp_2.8.0-1_i386.deb 769a3b128c2ab168f7f42f2bddb19add 40572 misc extra i2c-2.4.21-4-k6_2.8.0-1_i386.deb 20205fd4bd6aa644b35f2ed7e9024f46 40628 misc extra i2c-2.4.21-4-k7_2.8.0-1_i386.deb 915e48629ec48a742ef865231e3c0e86 40788 misc extra i2c-2.4.21-4-k7-smp_2.8.0-1_i386.deb -BEGIN PGP SIGNATURE- Version: GnuPG v1.2.3 (GNU/Linux) iD8DBQE/U5Rvp3U1z1PHTekRAmg3AKCKfr4qhBXIyqEf4VKk6Y3vrpKG0wCfbLVD hN0cbVTnmFKOLGrv6NhIB8k= =8Bbo -END PGP SIGNATURE- Accepted: i2c-2.4.21-4-386_2.8.0-1_i386.deb to pool/main/i/i2c/i2c-2.4.21-4-386_2.8.0-1_i386.deb i2c-2.4.21-4-586tsc_2.8.0-1_i386.deb to pool/main/i/i2c/i2c-2.4.21-4-586tsc_2.8.0-1_i386.deb i2c-2.4.21-4-686-smp_2.8.0-1_i386.deb to pool/main/i/i2c/i2c-2.4.21-4-686-smp_2.8.0-1_i386.deb i2c-2.4.21-4-686_2.8.0-1_i386.deb to pool/main/i/i2c/i2c-2.4.21-4-686_2.8.0-1_i386.deb i2c-2.4.21-4-k6_2.8.0-1_i386.deb to pool/main/i/i2c/i2c-2.4.21-4-k6_2.8.0-1_i386.deb i2c-2.4.21-4-k7-smp_2.8.0-1_i386.deb to pool/main/i/i2c/i2c-2.4.21-4-k7-smp_2.8.0-1_i386.deb i2c-2.4.21-4-k7_2.8.0-1_i386.deb to pool/main/i/i2c/i2c-2.4.21-4-k7_2.8.0-1_i386.deb i2c-source_2.8.0-1_all.deb to pool/main/i/i2c/i2c-source_2.8.0-1_all.deb i2c_2.8.0-1.diff.gz to pool/main/i/i2c/i2c_2.8.0-1.diff.gz i2c_2.8.0-1.dsc to pool/main/i/i2c/i2c_2.8.0-1.dsc i2c_2.8.0.orig.tar.gz to pool/main/i/i2c/i2c_2.8.0.orig.tar.gz -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Accepted lm-sensors 2.8.0-1 (i386 source all)
-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 Format: 1.7 Date: Mon, 1 Sep 2003 10:11:25 -0400 Source: lm-sensors Binary: lm-sensors-2.4.21-4-k6 lm-sensors-2.4.21-4-586tsc lm-sensors-source libsensors-dev lm-sensors-2.4.21-4-k7 lm-sensors-2.4.21-4-k7-smp lm-sensors sensord lm-sensors-2.4.21-4-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 libsensors2 - Library to read temperature/voltage/fan sensors lm-sensors - Utilities to read temperature/voltage/fan sensors lm-sensors-2.4.21-4-386 - Kernel drivers to read temperature/voltage/fan sensors lm-sensors-2.4.21-4-586tsc - Kernel drivers to read temperature/voltage/fan sensors lm-sensors-2.4.21-4-686 - Kernel drivers to read temperature/voltage/fan sensors lm-sensors-2.4.21-4-686-smp - Kernel drivers to read temperature/voltage/fan sensors lm-sensors-2.4.21-4-k6 - Kernel drivers to read temperature/voltage/fan sensors lm-sensors-2.4.21-4-k7 - Kernel drivers to read temperature/voltage/fan sensors lm-sensors-2.4.21-4-k7-smp - Kernel drivers to read temperature/voltage/fan sensors lm-sensors-source - Kernel drivers to read temperature/voltage/fan sensors (source) sensord- Hardware sensor information logging daemon Closes: 183751 202154 205354 Changes: lm-sensors (2.8.0-1) unstable; urgency=low . * New upstream release. The modules ABI changed, so you need both i2c and lm-sensors 2.8.0 modules, not in-kernel modules. Upstream also changed the libsensors soname. (Closes: #183751, #202154) * Build vs. kernel 2.4.21-4. * Add Dutch debconf translation, from Bart Cornelis [EMAIL PROTECTED]. (Closes: #205354) Files: a75985d90c1ed41089073d0bf9e3f926 752 utils extra lm-sensors_2.8.0-1.dsc 228d3536e51f017e45aa5f21973ced0d 670987 utils extra lm-sensors_2.8.0.orig.tar.gz ab527e064e3e3f85f5016787aced700e 26311 utils extra lm-sensors_2.8.0-1.diff.gz 803745c8880ad95f726d0d86295d8fa7 381858 utils extra lm-sensors_2.8.0-1_i386.deb e0f5d1d6b22428d68f02bc229d6ad498 49084 libs optional libsensors2_2.8.0-1_i386.deb e4497b3aceba4c0f4b3c3a429a720e61 66112 libdevel extra libsensors-dev_2.8.0-1_i386.deb e5e2d659823e2f205542018322c2d34f 41948 utils extra sensord_2.8.0-1_i386.deb 8ffd841cd208f2ef70e36d19d299f466 185890 utils extra lm-sensors-2.4.21-4-386_2.8.0-1_i386.deb 5458368d7df1e5aa7ee45b7adc0a24a4 185724 utils extra lm-sensors-2.4.21-4-586tsc_2.8.0-1_i386.deb 98c1b05196db7b98577b0457547bbac2 185878 utils extra lm-sensors-2.4.21-4-686_2.8.0-1_i386.deb 0c268aa8f52bb28985473cac84417420 186176 utils extra lm-sensors-2.4.21-4-686-smp_2.8.0-1_i386.deb 3a1886833ea3b1d3d2711edf3fdb8660 185894 utils extra lm-sensors-2.4.21-4-k6_2.8.0-1_i386.deb 6cb003dc40566ed697dbfb1ce030091a 185730 utils extra lm-sensors-2.4.21-4-k7_2.8.0-1_i386.deb dc77655c1cf8f7089478965fa1781b33 186018 utils extra lm-sensors-2.4.21-4-k7-smp_2.8.0-1_i386.deb ef168d23104b06c153bd07b4e8cc1434 715942 misc extra lm-sensors-source_2.8.0-1_all.deb -BEGIN PGP SIGNATURE- Version: GnuPG v1.2.3 (GNU/Linux) iD8DBQE/U5lrp3U1z1PHTekRAhu1AKDMfjRu6Bk3d106pp8+NRD4VdWe5ACglUhN tousuHlPGAUSEOyfyKNVzEA= =145e -END PGP SIGNATURE- Accepted: libsensors-dev_2.8.0-1_i386.deb to pool/main/l/lm-sensors/libsensors-dev_2.8.0-1_i386.deb libsensors2_2.8.0-1_i386.deb to pool/main/l/lm-sensors/libsensors2_2.8.0-1_i386.deb lm-sensors-2.4.21-4-386_2.8.0-1_i386.deb to pool/main/l/lm-sensors/lm-sensors-2.4.21-4-386_2.8.0-1_i386.deb lm-sensors-2.4.21-4-586tsc_2.8.0-1_i386.deb to pool/main/l/lm-sensors/lm-sensors-2.4.21-4-586tsc_2.8.0-1_i386.deb lm-sensors-2.4.21-4-686-smp_2.8.0-1_i386.deb to pool/main/l/lm-sensors/lm-sensors-2.4.21-4-686-smp_2.8.0-1_i386.deb lm-sensors-2.4.21-4-686_2.8.0-1_i386.deb to pool/main/l/lm-sensors/lm-sensors-2.4.21-4-686_2.8.0-1_i386.deb lm-sensors-2.4.21-4-k6_2.8.0-1_i386.deb to pool/main/l/lm-sensors/lm-sensors-2.4.21-4-k6_2.8.0-1_i386.deb lm-sensors-2.4.21-4-k7-smp_2.8.0-1_i386.deb to pool/main/l/lm-sensors/lm-sensors-2.4.21-4-k7-smp_2.8.0-1_i386.deb lm-sensors-2.4.21-4-k7_2.8.0-1_i386.deb to pool/main/l/lm-sensors/lm-sensors-2.4.21-4-k7_2.8.0-1_i386.deb lm-sensors-source_2.8.0-1_all.deb to pool/main/l/lm-sensors/lm-sensors-source_2.8.0-1_all.deb lm-sensors_2.8.0-1.diff.gz to pool/main/l/lm-sensors/lm-sensors_2.8.0-1.diff.gz lm-sensors_2.8.0-1.dsc to pool/main/l/lm-sensors/lm-sensors_2.8.0-1.dsc lm-sensors_2.8.0-1_i386.deb to pool/main/l/lm-sensors/lm-sensors_2.8.0-1_i386.deb lm-sensors_2.8.0.orig.tar.gz to pool/main/l/lm-sensors/lm-sensors_2.8.0.orig.tar.gz sensord_2.8.0-1_i386.deb to pool/main/l/lm-sensors/sensord_2.8.0-1_i386.deb -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
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] Description: xcircuit - Draw circuit schematics or almost anything Changes: xcircuit (3.1.19-1) unstable; urgency=low . * New upstream release. Files: c08a676f400e92162f9bf0b82b58d287 619 electronics extra xcircuit_3.1.19-1.dsc f79e0761059214eef29f45590b1f6dff 804479 electronics extra xcircuit_3.1.19.orig.tar.gz f84f60c65bd14f3d102d90ca120489a5 5817 electronics extra xcircuit_3.1.19-1.diff.gz 427fcbd389b7995e39f65a795e05c4e6 408506 electronics optional xcircuit_3.1.19-1_i386.deb -BEGIN PGP SIGNATURE- Version: GnuPG v1.2.2 (GNU/Linux) iD8DBQE/SVqOp3U1z1PHTekRAu3KAKDZN4oVLJdsBemETPDmtAqrC+f57QCfS5c9 EaMyh+WbNEIHOhvtihBLHYo= =Uga8 -END PGP SIGNATURE- Accepted: xcircuit_3.1.19-1.diff.gz to pool/main/x/xcircuit/xcircuit_3.1.19-1.diff.gz xcircuit_3.1.19-1.dsc to pool/main/x/xcircuit/xcircuit_3.1.19-1.dsc xcircuit_3.1.19-1_i386.deb to pool/main/x/xcircuit/xcircuit_3.1.19-1_i386.deb xcircuit_3.1.19.orig.tar.gz to pool/main/x/xcircuit/xcircuit_3.1.19.orig.tar.gz -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Re: Building kernel modules for stock kernels is a hell of a job!
Manuel Bilderbeek [EMAIL PROTECTED] writes: After having worked with Debian testing for about 2 years, I'm getting fed up with the seemingly unnecessarily complicated way of building kernel modules for the stock kernels. 1) install the kernel source for the kernel, e.g. kernel-source-2.4.21 Since you're singling out lm-sensors here, I can tell you that lm-sensors-source does build fine against the correct kernel-headers package; the normal binary package build-depends on a kernel-build package to get all of the kernel-headers, and uses those without any particular magic. 5) apt-get install [modulename-source] (sometimes -src), e.g. lm-sensors-source. 6) this should give [modulename].tar.gz in /usr/src; extract it: tar xzvf [modulename].tar.gz now, the source is in /usr/src/modules/[modulename] At this point, I think what I would tell you to do is (untested): cd $MODULE_LOC/$modulename debian/rules kdist-image KDREV=2.4.21-4 KVERS=2.4.21-4-k7 \ KSRC=/usr/src/kernel-headers-2.4.21-4-k7 \ KMAINT=Your Name KEMAIL=[EMAIL PROTECTED] \ APPEND_TO_VERSION=-4-k7 ROOT_CMD=fakeroot which will produce the binary package you're looking for in /usr/src. This is just using the interface required by kernel-package. 9) install the just built package(s) with dpkg -i [package_name] now the kernel modules should be in the right dir in /lib/modules and modprobe (or modconf) can find them. - If you have just installed a new kernel-image package (i.e. a new stock kernel), you need to do everything from the start *after* booting this new kernel You shouldn't need to. (Though you go through a little more effort to get the right .config file.) - In my experience, if you forget the export of step 7, you have to wipe your whole kernel source tree and start at step 2. I know I'm supposed to do a make-kpgk modules clean, but that didn't do the trick; 'rm -rf /usr/src/modules' is often quite theraputic for odd problems like this. Screwing up --append-to-version using kernel-package has kind of unfortunate side effects for recovering. :-/ 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 in unstable nowadays... :) (Although not yet for 2.4.21...) In some ways, doing this feels a lot like a very slow game of Whack-A-Mole. The process goes something like this: (1) Notice that Debian kernel 2.4.21-1 exists. (2) Install kernel-build-2.4.21-1. Change debian/rules to reference the right kernel. (3) Actually rebuild the package. This winds up taking quite a long time for me, particularly since there are seven different kernel flavors and I'm foolishly doing the build over AFS over a cable modem. (Should probably fix that. :-) (4) Upload. (5) Wait for ftpmaster, since these are all new packages. (6) Notice that Debian kernel 2.4.21-2 exists. (7) ftpmaster accepts lm-sensors-2.4.21-1-*, which depend on kernel-image-2.4.21-1-*, which is no longer in the repository. (8) Go to 2. It's also a bit frustrating to look at cross-platform compatability, and realize that the magic to get things built is just going to be different on each platform, since the platform-specific kernel packages are all different. Plus getting stock kernel modules built is presently entirely in the hands of the module maintainers, and the glue code in debian/rules to actually do that is kind of groady. I suspect for unstable, there's just not a lot to be done. For sarge, we should probably pick a kernel and a kernel ABI (or sets thereof) and not change it, so that packages that provide prebuilt kernel modules can do that more reasonably. -- David Maze [EMAIL PROTECTED] http://people.debian.org/~dmaze/ Theoretical politics is interesting. Politicking should be illegal. -- Abra Mitchell
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] Description: xcircuit - Draw circuit schematics or almost anything Changes: xcircuit (3.1.18-1) unstable; urgency=low . * New upstream release. * Standards-Version 3.6.0 (no changes). * Build vs. Python 2.3. Files: 32a2efb4e56d095c22858f5951b9845c 619 electronics extra xcircuit_3.1.18-1.dsc 54eaf1f11e108bd746092049fc4bb73d 804422 electronics extra xcircuit_3.1.18.orig.tar.gz fc449287c19984ef67b0617eb9abd1ee 5802 electronics extra xcircuit_3.1.18-1.diff.gz c4bc0bf8ffb7935cde1bc05f075cc961 398758 electronics optional xcircuit_3.1.18-1_i386.deb -BEGIN PGP SIGNATURE- Version: GnuPG v1.2.2 (GNU/Linux) iD8DBQE/NRMrp3U1z1PHTekRAp4WAJ0XFYDaN2aeWBUlRrALK4cxpFIidQCgtpqw 0rl3PgOxlPl+o9pjY+ehfwI= =YXP2 -END PGP SIGNATURE- Accepted: xcircuit_3.1.18-1.diff.gz to pool/main/x/xcircuit/xcircuit_3.1.18-1.diff.gz xcircuit_3.1.18-1.dsc to pool/main/x/xcircuit/xcircuit_3.1.18-1.dsc xcircuit_3.1.18-1_i386.deb to pool/main/x/xcircuit/xcircuit_3.1.18-1_i386.deb xcircuit_3.1.18.orig.tar.gz to pool/main/x/xcircuit/xcircuit_3.1.18.orig.tar.gz -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [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 not helped by the fact that each one comes with a dozen or more libraries, extensions, and so forth. Some people like Ian Hickson don't want to see package names like libgtk2.0. But _I_ want to see this, I am sys admin and want to know exactly what I am putting on _my_ systems. Just one of the reasons why I like GNU/Linux ... I know what I'm doing! Anyway, does this mean we need something like a GNU/Linux Debian and a GNU/Linux Debian For Dummies showing only icons? It probably means there should be a configuration option in aptitude to hide sections like devel, libdevel, libs, and interpreters, since end users typically don't care (and 90% of the time I find myself not caring, too). Perhaps suggesting to new users that they look in the tasks section of aptitude would help reduce the package overload, too. I don't think we need to abandon the power of our current infrastructure, just have ways of making it less visible for people who don't want it. -- David Maze [EMAIL PROTECTED] http://people.debian.org/~dmaze/ Theoretical politics is interesting. Politicking should be illegal. -- Abra Mitchell
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 new foo release, that changes libfoo's soname. In the current scheme, I package the new upstream release and upload foo and libfoo2; since there's no source package for libfoo1, it eventually gets removed from unstable. Are you proposing that (a) the ftpmasters not remove libfoo1, or (b) that package maintainers of library packages are now compelled to package the last version of foo's source providing libfoo1 separately, potentially for multiple release cycles for a widely used library? Option (b) sounds problematic to me... -- David Maze [EMAIL PROTECTED] http://people.debian.org/~dmaze/ Theoretical politics is interesting. Politicking should be illegal. -- Abra Mitchell
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.) The shell script /etc/acpi/powerbtn.sh should be installed in something else, like /usr/share/acpid/ or /usr/sbin/. I've no problem with that, but: These scripts used by acpid should be treated as some kind of user configuration, like i.e. cron keeps skripts installed by someone in /etc/cron.daily, acpid keeps skripts that take actions when some events happened. Is this script that gets run when the console user presses the power button, and is it obvious that the user could potentially want to configure it? If so, then it makes sense that it should be a configuration file, and so by policy 10.7.2 it should live in /etc. (And as you point out, it's not like there aren't other admin-editable scripts in /etc already, say, all of /etc/init.d.) My reading is that what you're doing now is fine and the bug is wrong. -- David Maze [EMAIL PROTECTED] http://people.debian.org/~dmaze/ Theoretical politics is interesting. Politicking should be illegal. -- Abra Mitchell
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 either of the above architectures with bugs found in our packages? But Debian has ~public machines for pretty much every architecture. I'd say look on http://db.debian.org/machines.cgi;, except that's down; I can at least point you at section 4.4 of the Developer's Reference, though that doesn't say a whole lot beyond this. I admit that this doesn't necessarily help for testing installers, but for your own packages it should be straightforward for you to do testing and bugfixing even on architectures you don't personally own a machine for. -- David Maze [EMAIL PROTECTED] http://people.debian.org/~dmaze/ Theoretical politics is interesting. Politicking should be illegal. -- Abra Mitchell
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 happier, pretend I'm asking about something hardware-independent like openafs. -- David Maze [EMAIL PROTECTED] http://people.debian.org/~dmaze/ Theoretical politics is interesting. Politicking should be illegal. -- Abra Mitchell
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 kernel-build-2.4.21-1 also appears to just be an i386 thing. It looked like kernel-tree-2.4.21 might be useful for this, but it doesn't obviously appear to depend on architecture-specific patches and doesn't give any clue as to what flavors exist and has *no documentation at all*. Is there actually something I can build-depend on that will get me correct headers for the kernels on whatever platform I'm building on? -- David Maze [EMAIL PROTECTED] http://people.debian.org/~dmaze/ Theoretical politics is interesting. Politicking should be illegal. -- Abra Mitchell
Accepted lm-sensors 2.7.0-6 (i386 source all)
-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 Format: 1.7 Date: Sun, 22 Jun 2003 15:10:50 -0400 Source: lm-sensors Binary: libsensors-1debian1 lm-sensors-2.4.20-3-k7-smp lm-sensors-source lm-sensors-2.4.20-3-686 libsensors-dev lm-sensors-2.4.20-3-k7 lm-sensors sensord lm-sensors-2.4.20-3-k6 lm-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 temperature/voltage/fan sensors libsensors-dev - Lm-sensors development kit lm-sensors - Utilities to read temperature/voltage/fan sensors lm-sensors-2.4.20-3-386 - Kernel drivers to read temperature/voltage/fan sensors lm-sensors-2.4.20-3-586tsc - Kernel drivers to read temperature/voltage/fan sensors lm-sensors-2.4.20-3-686 - Kernel drivers to read temperature/voltage/fan sensors lm-sensors-2.4.20-3-686-smp - Kernel drivers to read temperature/voltage/fan sensors lm-sensors-2.4.20-3-k6 - Kernel drivers to read temperature/voltage/fan sensors lm-sensors-2.4.20-3-k7 - Kernel drivers to read temperature/voltage/fan sensors lm-sensors-2.4.20-3-k7-smp - Kernel drivers to read temperature/voltage/fan sensors lm-sensors-source - Kernel drivers to read temperature/voltage/fan sensors (source) sensord- Hardware sensor information logging daemon Closes: 196237 197309 198259 Changes: lm-sensors (2.7.0-6) unstable; urgency=low . * Make the libsensors.so link in libsensors-dev point at the right place, libsensors.so.1.debian.1. * Add Portugese (Brazilian) debconf translation, from Andre Luis Lopes [EMAIL PROTECTED]. (Closes: #198259) * Add French debconf translation, from Michel Grentzinger [EMAIL PROTECTED]. (Closes: #197309) * Get Perl dependencies correct, using dh_perl. (Closes: #196237) Files: cc0f85b978c0b5e7944b58f61392de48 760 utils extra lm-sensors_2.7.0-6.dsc 098b7e2e6385ebee25ae7dfae72ce844 26866 utils extra lm-sensors_2.7.0-6.diff.gz 48bc5b8c8e665cd32fbcd4650c5c8936 350662 utils extra lm-sensors_2.7.0-6_i386.deb ca84a5fd94e4688cd22c1c2b758881fa 43786 libs optional libsensors-1debian1_2.7.0-6_i386.deb 7f22a520d2547bf6371a3f1232947b95 58250 libdevel extra libsensors-dev_2.7.0-6_i386.deb 446f895863f66af8ae654d2d66ffc5b7 39870 utils extra sensord_2.7.0-6_i386.deb 481c40a9cfc7f2c827a0abc98e0fee39 147414 utils extra lm-sensors-2.4.20-3-386_2.7.0-6_i386.deb 95af9cd70fec2309a2c19a8f28d1d852 147162 utils extra lm-sensors-2.4.20-3-586tsc_2.7.0-6_i386.deb 39a639410d8a26f1fa9d165df78dc02e 147402 utils extra lm-sensors-2.4.20-3-686_2.7.0-6_i386.deb 8e05c54733e6076a84600c9dea2e37fe 147626 utils extra lm-sensors-2.4.20-3-686-smp_2.7.0-6_i386.deb d8714292f512108ee5dea6357c08cbdc 147410 utils extra lm-sensors-2.4.20-3-k6_2.7.0-6_i386.deb ecae85aa63747e1b3600e3637b666582 147414 utils extra lm-sensors-2.4.20-3-k7_2.7.0-6_i386.deb bce9c9c987c647f6875a8456a61e42fa 147626 utils extra lm-sensors-2.4.20-3-k7-smp_2.7.0-6_i386.deb c50c75b417f98a8a8feeaf543ac339d6 637490 misc extra lm-sensors-source_2.7.0-6_all.deb -BEGIN PGP SIGNATURE- Version: GnuPG v1.2.2 (GNU/Linux) iD8DBQE+9xZDp3U1z1PHTekRAugiAJ4utI/Nka3kz+xfh/qepNtQCAoGhQCcCL+s dT4zQ619IOGbIZeIngJAnmA= =r+3+ -END PGP SIGNATURE- Accepted: libsensors-1debian1_2.7.0-6_i386.deb to pool/main/l/lm-sensors/libsensors-1debian1_2.7.0-6_i386.deb libsensors-dev_2.7.0-6_i386.deb to pool/main/l/lm-sensors/libsensors-dev_2.7.0-6_i386.deb lm-sensors-2.4.20-3-386_2.7.0-6_i386.deb to pool/main/l/lm-sensors/lm-sensors-2.4.20-3-386_2.7.0-6_i386.deb lm-sensors-2.4.20-3-586tsc_2.7.0-6_i386.deb to pool/main/l/lm-sensors/lm-sensors-2.4.20-3-586tsc_2.7.0-6_i386.deb lm-sensors-2.4.20-3-686-smp_2.7.0-6_i386.deb to pool/main/l/lm-sensors/lm-sensors-2.4.20-3-686-smp_2.7.0-6_i386.deb lm-sensors-2.4.20-3-686_2.7.0-6_i386.deb to pool/main/l/lm-sensors/lm-sensors-2.4.20-3-686_2.7.0-6_i386.deb lm-sensors-2.4.20-3-k6_2.7.0-6_i386.deb to pool/main/l/lm-sensors/lm-sensors-2.4.20-3-k6_2.7.0-6_i386.deb lm-sensors-2.4.20-3-k7-smp_2.7.0-6_i386.deb to pool/main/l/lm-sensors/lm-sensors-2.4.20-3-k7-smp_2.7.0-6_i386.deb lm-sensors-2.4.20-3-k7_2.7.0-6_i386.deb to pool/main/l/lm-sensors/lm-sensors-2.4.20-3-k7_2.7.0-6_i386.deb lm-sensors-source_2.7.0-6_all.deb to pool/main/l/lm-sensors/lm-sensors-source_2.7.0-6_all.deb lm-sensors_2.7.0-6.diff.gz to pool/main/l/lm-sensors/lm-sensors_2.7.0-6.diff.gz lm-sensors_2.7.0-6.dsc to pool/main/l/lm-sensors/lm-sensors_2.7.0-6.dsc lm-sensors_2.7.0-6_i386.deb to pool/main/l/lm-sensors/lm-sensors_2.7.0-6_i386.deb sensord_2.7.0-6_i386.deb to pool/main/l/lm-sensors/sensord_2.7.0-6_i386.deb -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Accepted i2c 2.7.0-4 (i386 source all)
-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 Format: 1.7 Date: Fri, 30 May 2003 17:27:40 -0400 Source: i2c Binary: i2c-source i2c-2.4.20-3-k7-smp i2c-2.4.20-3-386 i2c-2.4.20-3-586tsc i2c-2.4.20-3-k6 i2c-2.4.20-3-k7 i2c-2.4.20-3-686-smp i2c-2.4.20-3-686 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: 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 - drivers for the i2c bus i2c-2.4.20-3-k6 - drivers for the i2c bus i2c-2.4.20-3-k7 - drivers for the i2c bus i2c-2.4.20-3-k7-smp - drivers for the i2c bus i2c-source - sources for drivers for the i2c bus Changes: i2c (2.7.0-4) unstable; urgency=low . * Build vs. kernel-build 2.4.20-3. Files: 5ef1a956271b8d2747aafe314d236474 596 misc extra i2c_2.7.0-4.dsc cc685ff8ed8883a78429e6a8ea97d442 17754 misc extra i2c_2.7.0-4.diff.gz 30858f5be71dc8edc4eebc956e19eb25 152798 misc extra i2c-source_2.7.0-4_all.deb bede506bfc7e90d535eaa135723a8061 75988 misc extra i2c-2.4.20-3-386_2.7.0-4_i386.deb 0a1ef72c2d72fa3ba1e96a087499381f 40402 misc extra i2c-2.4.20-3-586tsc_2.7.0-4_i386.deb d38d73b507b4081590a1751bcde884d8 40408 misc extra i2c-2.4.20-3-686_2.7.0-4_i386.deb f5c4b7fa22ef94de08349cc0ba569902 40600 misc extra i2c-2.4.20-3-686-smp_2.7.0-4_i386.deb 02745df625d650fb08f351085e011c11 40402 misc extra i2c-2.4.20-3-k6_2.7.0-4_i386.deb 2fbb5a32977ffe92e51a2e0507413596 40418 misc extra i2c-2.4.20-3-k7_2.7.0-4_i386.deb ec3329dd5c8f66bbda9bb3b29a1bd53f 40640 misc extra i2c-2.4.20-3-k7-smp_2.7.0-4_i386.deb -BEGIN PGP SIGNATURE- Version: GnuPG v1.2.2 (GNU/Linux) iD8DBQE+18+6p3U1z1PHTekRAulKAJwIckpT36XRP4Xc+rYlMhxANClzsgCdGrwX Oha7DWaw9exSonh6jMTPcq0= =XnAu -END PGP SIGNATURE- Accepted: i2c-2.4.20-3-386_2.7.0-4_i386.deb to pool/main/i/i2c/i2c-2.4.20-3-386_2.7.0-4_i386.deb i2c-2.4.20-3-586tsc_2.7.0-4_i386.deb to pool/main/i/i2c/i2c-2.4.20-3-586tsc_2.7.0-4_i386.deb i2c-2.4.20-3-686-smp_2.7.0-4_i386.deb to pool/main/i/i2c/i2c-2.4.20-3-686-smp_2.7.0-4_i386.deb i2c-2.4.20-3-686_2.7.0-4_i386.deb to pool/main/i/i2c/i2c-2.4.20-3-686_2.7.0-4_i386.deb i2c-2.4.20-3-k6_2.7.0-4_i386.deb to pool/main/i/i2c/i2c-2.4.20-3-k6_2.7.0-4_i386.deb i2c-2.4.20-3-k7-smp_2.7.0-4_i386.deb to pool/main/i/i2c/i2c-2.4.20-3-k7-smp_2.7.0-4_i386.deb i2c-2.4.20-3-k7_2.7.0-4_i386.deb to pool/main/i/i2c/i2c-2.4.20-3-k7_2.7.0-4_i386.deb i2c-source_2.7.0-4_all.deb to pool/main/i/i2c/i2c-source_2.7.0-4_all.deb i2c_2.7.0-4.diff.gz to pool/main/i/i2c/i2c_2.7.0-4.diff.gz i2c_2.7.0-4.dsc to pool/main/i/i2c/i2c_2.7.0-4.dsc -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Accepted lm-sensors 2.7.0-5 (i386 source all)
-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 Format: 1.7 Date: Mon, 2 Jun 2003 11:26:11 -0400 Source: lm-sensors Binary: libsensors-1debian1 lm-sensors-2.4.20-3-k7-smp lm-sensors-source lm-sensors-2.4.20-3-686 libsensors-dev lm-sensors-2.4.20-3-k7 lm-sensors sensord lm-sensors-2.4.20-3-k6 lm-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 temperature/voltage/fan sensors libsensors-dev - Lm-sensors development kit lm-sensors - Utilities to read temperature/voltage/fan sensors lm-sensors-2.4.20-3-386 - Kernel drivers to read temperature/voltage/fan sensors lm-sensors-2.4.20-3-586tsc - Kernel drivers to read temperature/voltage/fan sensors lm-sensors-2.4.20-3-686 - Kernel drivers to read temperature/voltage/fan sensors lm-sensors-2.4.20-3-686-smp - Kernel drivers to read temperature/voltage/fan sensors lm-sensors-2.4.20-3-k6 - Kernel drivers to read temperature/voltage/fan sensors lm-sensors-2.4.20-3-k7 - Kernel drivers to read temperature/voltage/fan sensors lm-sensors-2.4.20-3-k7-smp - Kernel drivers to read temperature/voltage/fan sensors lm-sensors-source - Kernel drivers to read temperature/voltage/fan sensors (source) sensord- Hardware sensor information logging daemon Changes: lm-sensors (2.7.0-5) unstable; urgency=low . * Build vs. kernel 2.4.20-3. Files: 948645701de51ec38a082aa1b11e14a8 760 utils extra lm-sensors_2.7.0-5.dsc 0641871596a9dd0e7792bf6d5051ca53 25811 utils extra lm-sensors_2.7.0-5.diff.gz ce822b458db02394ac85296e613181c3 350246 utils extra lm-sensors_2.7.0-5_i386.deb 7772159cf66cf6787428a85bb118d108 43608 libs optional libsensors-1debian1_2.7.0-5_i386.deb b8b58ebe7226979657d1fc9faf2f038a 58076 libdevel extra libsensors-dev_2.7.0-5_i386.deb 9885b4386ee8799956a02c17b5e76806 39752 utils extra sensord_2.7.0-5_i386.deb 7c58bf241083fe2cede8262c481cabe5 147254 utils extra lm-sensors-2.4.20-3-386_2.7.0-5_i386.deb dbb00ec6ba4b04132da1bdb9ddf43ada 147008 utils extra lm-sensors-2.4.20-3-586tsc_2.7.0-5_i386.deb a739537c306176c73225686f1646fe97 147240 utils extra lm-sensors-2.4.20-3-686_2.7.0-5_i386.deb 38fbde8b7e4838d0a4969c6272ad9225 147478 utils extra lm-sensors-2.4.20-3-686-smp_2.7.0-5_i386.deb bda9ae9b8cc633cee1dd3798c8260212 147240 utils extra lm-sensors-2.4.20-3-k6_2.7.0-5_i386.deb eba528b4053e2a8b31e9155c42e51ae4 147222 utils extra lm-sensors-2.4.20-3-k7_2.7.0-5_i386.deb 958631cab85c557ff97de7e29d5a8c35 147450 utils extra lm-sensors-2.4.20-3-k7-smp_2.7.0-5_i386.deb 366d8105bfdb59fe1b6c04b23695df34 636550 misc extra lm-sensors-source_2.7.0-5_all.deb -BEGIN PGP SIGNATURE- Version: GnuPG v1.2.2 (GNU/Linux) iD8DBQE+23ufp3U1z1PHTekRAgOJAJ4vKej/S9t2ssUmCy7GGGCNdqB0PACfS3UV pLNsF0EiU1xKEXvIe+Rb7Ws= =wgcC -END PGP SIGNATURE- Accepted: libsensors-1debian1_2.7.0-5_i386.deb to pool/main/l/lm-sensors/libsensors-1debian1_2.7.0-5_i386.deb libsensors-dev_2.7.0-5_i386.deb to pool/main/l/lm-sensors/libsensors-dev_2.7.0-5_i386.deb lm-sensors-2.4.20-3-386_2.7.0-5_i386.deb to pool/main/l/lm-sensors/lm-sensors-2.4.20-3-386_2.7.0-5_i386.deb lm-sensors-2.4.20-3-586tsc_2.7.0-5_i386.deb to pool/main/l/lm-sensors/lm-sensors-2.4.20-3-586tsc_2.7.0-5_i386.deb lm-sensors-2.4.20-3-686-smp_2.7.0-5_i386.deb to pool/main/l/lm-sensors/lm-sensors-2.4.20-3-686-smp_2.7.0-5_i386.deb lm-sensors-2.4.20-3-686_2.7.0-5_i386.deb to pool/main/l/lm-sensors/lm-sensors-2.4.20-3-686_2.7.0-5_i386.deb lm-sensors-2.4.20-3-k6_2.7.0-5_i386.deb to pool/main/l/lm-sensors/lm-sensors-2.4.20-3-k6_2.7.0-5_i386.deb lm-sensors-2.4.20-3-k7-smp_2.7.0-5_i386.deb to pool/main/l/lm-sensors/lm-sensors-2.4.20-3-k7-smp_2.7.0-5_i386.deb lm-sensors-2.4.20-3-k7_2.7.0-5_i386.deb to pool/main/l/lm-sensors/lm-sensors-2.4.20-3-k7_2.7.0-5_i386.deb lm-sensors-source_2.7.0-5_all.deb to pool/main/l/lm-sensors/lm-sensors-source_2.7.0-5_all.deb lm-sensors_2.7.0-5.diff.gz to pool/main/l/lm-sensors/lm-sensors_2.7.0-5.diff.gz lm-sensors_2.7.0-5.dsc to pool/main/l/lm-sensors/lm-sensors_2.7.0-5.dsc lm-sensors_2.7.0-5_i386.deb to pool/main/l/lm-sensors/lm-sensors_2.7.0-5_i386.deb sensord_2.7.0-5_i386.deb to pool/main/l/lm-sensors/sensord_2.7.0-5_i386.deb -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
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 functions that are supported by the server (posting, friends editing, friend groups, friend page checking, post editing etc). Reading this description, I have absolutely no idea abut whet this software is about. Could you please rewrite it by explaining what is a livejournal.com client ? http://www.livejournal.com/ is a quasi-free-as-in-beer online journaling service that seems to be fairly popular. There are a couple of other services that use the same code base, and a couple other livejournal clients already in Debian (I tend to use logjam, for example, which has a somewhat similar package description). I think the service is popular enough that you don't need to explain what it is, in the same way that you don't need to explain what an SNMP daemon is to have and snmpd package. -- David Maze [EMAIL PROTECTED] http://people.debian.org/~dmaze/ Theoretical politics is interesting. Politicking should be illegal. -- Abra Mitchell
Accepted lm-sensors 2.7.0-4 (i386 source all)
-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 Format: 1.7 Date: Tue, 20 May 2003 19:15:34 -0400 Source: lm-sensors Binary: libsensors-1debian1 lm-sensors-2.4.20-1-386 lm-sensors-source libsensors-dev lm-sensors lm-sensors-2.4.20-1-k6 lm-sensors-2.4.20-1-k7 sensord lm-sensors-2.4.20-1-686-smp lm-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 temperature/voltage/fan sensors libsensors-dev - Lm-sensors development kit lm-sensors - Utilities to read temperature/voltage/fan sensors lm-sensors-2.4.20-1-386 - Kernel drivers to read temperature/voltage/fan sensors lm-sensors-2.4.20-1-586tsc - Kernel drivers to read temperature/voltage/fan sensors lm-sensors-2.4.20-1-686 - Kernel drivers to read temperature/voltage/fan sensors lm-sensors-2.4.20-1-686-smp - Kernel drivers to read temperature/voltage/fan sensors lm-sensors-2.4.20-1-k6 - Kernel drivers to read temperature/voltage/fan sensors lm-sensors-2.4.20-1-k7 - Kernel drivers to read temperature/voltage/fan sensors lm-sensors-2.4.20-1-k7-smp - Kernel drivers to read temperature/voltage/fan sensors lm-sensors-source - Kernel drivers to read temperature/voltage/fan sensors (source) sensord- Hardware sensor information logging daemon Closes: 191572 193082 Changes: lm-sensors (2.7.0-4) unstable; urgency=low . * Rename libsensors.so.1 to libsensors.so.1.debian.1, and change the package name to libsensors1. This due to a change in the library ABI upstream which isn't reflected in an soname change. (Closes: #191572, #193082) Files: aea48ec81063294e9aecf09b536511ce 760 utils extra lm-sensors_2.7.0-4.dsc 1ee1a4e56c016a10eac77cf77653e150 25787 utils extra lm-sensors_2.7.0-4.diff.gz c32ad5d56f4270bca039875b386f163f 350242 utils extra lm-sensors_2.7.0-4_i386.deb f3c29b47eaea8e76f83bdf45482da299 43604 libs optional libsensors-1debian1_2.7.0-4_i386.deb 57c6cedd3d687709870c3d15340359b1 58080 libdevel extra libsensors-dev_2.7.0-4_i386.deb 108a5018fc37d628945a79258268ca14 39754 utils extra sensord_2.7.0-4_i386.deb fad060ac807fb91f077edba96a3e252c 147316 utils extra lm-sensors-2.4.20-1-386_2.7.0-4_i386.deb 33312ee3a214b0b41fbfbbde20623b06 147064 utils extra lm-sensors-2.4.20-1-586tsc_2.7.0-4_i386.deb dd6ce37118828f4ba477820c5e2be51f 147310 utils extra lm-sensors-2.4.20-1-686_2.7.0-4_i386.deb 5a3fc00473f49e12bc886a336528d266 147556 utils extra lm-sensors-2.4.20-1-686-smp_2.7.0-4_i386.deb f2fde9469333e82ba0a1fcd895c562f2 147320 utils extra lm-sensors-2.4.20-1-k6_2.7.0-4_i386.deb b0f85665a433cd1ab684dfdfe4055247 147300 utils extra lm-sensors-2.4.20-1-k7_2.7.0-4_i386.deb c443585cbe61348cdc5b935d5bff88cb 147534 utils extra lm-sensors-2.4.20-1-k7-smp_2.7.0-4_i386.deb b2c22982111d7da46207e9e6ec1d8b22 636544 misc extra lm-sensors-source_2.7.0-4_all.deb -BEGIN PGP SIGNATURE- Version: GnuPG v1.2.2 (GNU/Linux) iD8DBQE+yti3p3U1z1PHTekRAoy7AJwK3D7i6OBSHpqqLIKhuOpAvQ9rZwCg0AOo rVFXwn2VZnvMswY4kOQO+JU= =uWel -END PGP SIGNATURE- Accepted: libsensors-1debian1_2.7.0-4_i386.deb to pool/main/l/lm-sensors/libsensors-1debian1_2.7.0-4_i386.deb libsensors-dev_2.7.0-4_i386.deb to pool/main/l/lm-sensors/libsensors-dev_2.7.0-4_i386.deb lm-sensors-2.4.20-1-386_2.7.0-4_i386.deb to pool/main/l/lm-sensors/lm-sensors-2.4.20-1-386_2.7.0-4_i386.deb lm-sensors-2.4.20-1-586tsc_2.7.0-4_i386.deb to pool/main/l/lm-sensors/lm-sensors-2.4.20-1-586tsc_2.7.0-4_i386.deb lm-sensors-2.4.20-1-686-smp_2.7.0-4_i386.deb to pool/main/l/lm-sensors/lm-sensors-2.4.20-1-686-smp_2.7.0-4_i386.deb lm-sensors-2.4.20-1-686_2.7.0-4_i386.deb to pool/main/l/lm-sensors/lm-sensors-2.4.20-1-686_2.7.0-4_i386.deb lm-sensors-2.4.20-1-k6_2.7.0-4_i386.deb to pool/main/l/lm-sensors/lm-sensors-2.4.20-1-k6_2.7.0-4_i386.deb lm-sensors-2.4.20-1-k7-smp_2.7.0-4_i386.deb to pool/main/l/lm-sensors/lm-sensors-2.4.20-1-k7-smp_2.7.0-4_i386.deb lm-sensors-2.4.20-1-k7_2.7.0-4_i386.deb to pool/main/l/lm-sensors/lm-sensors-2.4.20-1-k7_2.7.0-4_i386.deb lm-sensors-source_2.7.0-4_all.deb to pool/main/l/lm-sensors/lm-sensors-source_2.7.0-4_all.deb lm-sensors_2.7.0-4.diff.gz to pool/main/l/lm-sensors/lm-sensors_2.7.0-4.diff.gz lm-sensors_2.7.0-4.dsc to pool/main/l/lm-sensors/lm-sensors_2.7.0-4.dsc lm-sensors_2.7.0-4_i386.deb to pool/main/l/lm-sensors/lm-sensors_2.7.0-4_i386.deb sensord_2.7.0-4_i386.deb to pool/main/l/lm-sensors/sensord_2.7.0-4_i386.deb -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
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 KVERS=versionname is priovided. I'd be slightly happier if the targets kernel-package used were supported here, 'debian/rules kdist-image' and such. (This is to accomodate binary source packages that have a single debian/rules file that's copied verbatim from the source package to the binary package; both lm-sensors and i2c work this way, don't know about other packages.) * The debian/rules file may fail if an unsupported version of the kernel is provided by the environment. * The debian/rules file may fail if no kernel-headers is in that location. * The debian/rules file should handke KMAINT and KEMAIL env variables. ...in fact, this looks a lot like what kernel-package currently documents. Is a separate policy from the kernel-package documentation needed? (FWIW, i2c and lm-sensors both successfully build against only the kernel headers, via the kernel-build-* packages.) -- David Maze [EMAIL PROTECTED] http://people.debian.org/~dmaze/ Theoretical politics is interesting. Politicking should be illegal. -- Abra Mitchell
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 few in any case. I did send upstream mail pointing out the issue and asking for an soname change, but I haven't heard anything back. I'll upload a new package with a Debian-specific soname as soon as I can get to a development machine with the relevant hardware, probably tomorrow... sources depending on libsensors1 hardware-monitor kdebase ksensors lm-sensors mrtgutils wmgtemp wmsensors xsensors (The other motivation for uploading a new libsensors1 is to Conflict: with the subset of these packages that have linked against the libsensors1 that doesn't work; if I'm not going to do that, then I should probably ask that libsensors1 be removed.) -- David Maze [EMAIL PROTECTED] http://people.debian.org/~dmaze/ Theoretical politics is interesting. Politicking should be illegal. -- Abra Mitchell
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, I've stopped caring about users of a certain other widespread MUA, as you've probably guessed anyway when you notice me using PGP/MIME to sign messages...) I'm not actually clear how much this is a good thing; at some level, we do want people reporting bugs. (Though at the same level, we also want them reading and using debian-user, and get a real MUA is a common sentiment there.) But yeah, its unnamed inbound MIME handling is pretty terrible; content-disposition is completely ignored, so if I attach a file to mail, the recipient sees my .signature as a separate attachment... -- David Maze [EMAIL PROTECTED] http://people.debian.org/~dmaze/ Theoretical politics is interesting. Politicking should be illegal. -- Abra Mitchell
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, just one). (b) Changing the soname of libsensors.so to libsensors.so.1.debian.1 in lm-sensors 2.7.0, and changing the name of the library package to libsensors-1debian1, and changing the shlibs file appropriately. (c) Checking that the user-kernel interface hasn't changed; that is, that the 2.6.5 library works vs. 2.7.0 modules, and vice versa. Is this a reasonable course of action? The soname feels a little ugly to me, but otherwise, assuming (c), it does feel like about the right thing to do. You're talking about doing all of the above? If you do (b) and (c), why do you still need to do (a)? (I.e., why would you maintain two versions of the library in unstable simultaneously?) Doing (b) and (c) seems reasonable, at least. But if you don't have kernel interface issues from (c), I don't see why you would want (a). I'd like packages that haven't recompiled vs. libsensors-1debian1 to still work. (a) would mean providing the old libsensors1 with the old ABI, which would enable this. (If (c) works and I do (b) but not (a), then the lm-sensors source package now provides libsensors-dev and libsensors-1debian1, and nothing provides libsensors1.) -- David Maze [EMAIL PROTECTED] http://people.debian.org/~dmaze/ Theoretical politics is interesting. Politicking should be illegal. -- Abra Mitchell
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] Description: xcircuit - Draw circuit schematics or almost anything Changes: xcircuit (3.0rev8-1) unstable; urgency=low . * New upstream release. * Update to CBS 1.50. Files: 83cdaff037a250d0f611d20e6cd47e83 607 electronics extra xcircuit_3.0rev8-1.dsc fa7d3d6efedaea72b7d5a67d6b7df11f 691847 electronics extra xcircuit_3.0rev8.orig.tar.gz 46f644fa4d56ecd0ae212ab02f6f4df6 26702 electronics extra xcircuit_3.0rev8-1.diff.gz 58ad83d206ef33af27424ed648680058 391700 electronics optional xcircuit_3.0rev8-1_i386.deb -BEGIN PGP SIGNATURE- Version: GnuPG v1.2.1 (GNU/Linux) iD8DBQE+KtAAp3U1z1PHTekRAnlsAJ9iaIBk/ouG7zysPlJestg7sI6ybgCgkfFN c6nSpSTg/Vd5cnC5TLQQon0= =vhjB -END PGP SIGNATURE- Accepted: xcircuit_3.0rev8-1.diff.gz to pool/main/x/xcircuit/xcircuit_3.0rev8-1.diff.gz xcircuit_3.0rev8-1.dsc to pool/main/x/xcircuit/xcircuit_3.0rev8-1.dsc xcircuit_3.0rev8-1_i386.deb to pool/main/x/xcircuit/xcircuit_3.0rev8-1_i386.deb xcircuit_3.0rev8.orig.tar.gz to pool/main/x/xcircuit/xcircuit_3.0rev8.orig.tar.gz -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [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] Description: xcircuit - Draw circuit schematics or almost anything Changes: xcircuit (3.0rev7-1) unstable; urgency=low . * New upstream release. * Update to CBS 1.48. Files: 5a2d2f271390b8dc6f292aba20b14607 608 electronics extra xcircuit_3.0rev7-1.dsc e48b62c5c566ed5f57e66e712db92079 1137811 electronics extra xcircuit_3.0rev7.orig.tar.gz 83f0aeba6b595fb728e2186bfc14208c 26670 electronics extra xcircuit_3.0rev7-1.diff.gz 67456a1b8e0feee7f4a8f7ec897392b3 379802 electronics optional xcircuit_3.0rev7-1_i386.deb -BEGIN PGP SIGNATURE- Version: GnuPG v1.2.1 (GNU/Linux) iD8DBQE+Afipp3U1z1PHTekRArZXAKCKoM5xpZahhxeedC9CnCiYTPSu9gCeKelc wJ9WYLHp3HG+vElwrAmxpME= =EZiR -END PGP SIGNATURE- Accepted: xcircuit_3.0rev7-1.diff.gz to pool/main/x/xcircuit/xcircuit_3.0rev7-1.diff.gz xcircuit_3.0rev7-1.dsc to pool/main/x/xcircuit/xcircuit_3.0rev7-1.dsc xcircuit_3.0rev7-1_i386.deb to pool/main/x/xcircuit/xcircuit_3.0rev7-1_i386.deb xcircuit_3.0rev7.orig.tar.gz to pool/main/x/xcircuit/xcircuit_3.0rev7.orig.tar.gz -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [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 to drop this into module builds? The fundamental problem seems to be that I want to build-depend on kernel-build-2.4.20, and then build a module for each of the flavors in /usr/src/kernel-build-2.4.20. But which flavors exactly exist varies per platform, and might also vary between builds of the kernel. This means that the contents of debian/control need to be different on each platform. I could put every possible architecture/version/flavor triple in debian/control, but this seems unmaintainable. Any hints? -- David Maze [EMAIL PROTECTED] http://people.debian.org/~dmaze/ Theoretical politics is interesting. Politicking should be illegal. -- Abra Mitchell
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 monitoring package for Linux (kernel patch) I've created the patches on my own for 2.4.19 and 2.4.20 from the lm-sensors-source package. This patch allow you patch you kernel with lm_sensors. Hmm. I (as the lm-sensors maintainer) am a little ambiguous about this. It seems wrong to have two separate source packages for lm-sensors when they both do the same thing. But I'm also unclear whether the effort of maintaining a kernel-patch version of lm-sensors in addition to the modules source is useful effort, since this sounds like something that's hard to debug via the BTS. How involved are the patches? (How does the kernel-package patch_the_kernel option work?) Can you submit a wishlist bug against lm-sensors-source, at least? This package Depends on kernel-patch-i2c. How much depends? Right now the standalone kernel modules for lm-sensors 2.6.5 depend on i2c 2.6.1 or newer, so the version of i2c in kernels 2.4.13 or newer works fine too. There's magic in the lm-sensors-source package to figure this out. Repeat everything I said before about kernel patches, replacing lm-sensors with i2c (including filing a wishlist bug against i2c-source). -- David Maze [EMAIL PROTECTED] http://people.debian.org/~dmaze/ Theoretical politics is interesting. Politicking should be illegal. -- Abra Mitchell
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 [EMAIL PROTECTED] Changed-By: David Z Maze [EMAIL PROTECTED] Description: libsensors-dev - Lm-sensors development kit libsensors1 - Library to read temperature/voltage/fan sensors lm-sensors - Utilities to read temperature/voltage/fan sensors lm-sensors-source - Kernel drivers to read temperature/voltage/fan sensors (source) sensord- Hardware sensor information logging daemon Changes: lm-sensors (2.6.5-3) unstable; urgency=low . * Pulled forward some changes from upstream. (I wish cvs-buildpackage dealt better with this; I think it's CVS' fault.) Updated debian/rules to correctly deal with the newer makefile. * Put kernel modules in /lib/modules/$KVERS/lm-sensors, not misc. Files: 52f47b37e5690b3eaa1d3aa5ea891336 696 utils extra lm-sensors_2.6.5-3.dsc 9f526f671323b1b12802b1e400b1dc48 22477 utils extra lm-sensors_2.6.5-3.diff.gz 99ce4ee73e831d98546a4bd0904503d3 331312 utils extra lm-sensors_2.6.5-3_i386.deb 909e602f0fda332af08c28be7bfb2b81 39364 libs optional libsensors1_2.6.5-3_i386.deb a30c18f587d4d14da067156814512d63 53728 devel extra libsensors-dev_2.6.5-3_i386.deb f97f6abef963ff7302aff72c3a334b7b 38012 utils extra sensord_2.6.5-3_i386.deb 7867461563c3e3395f3b559475d61d1c 598904 misc extra lm-sensors-source_2.6.5-3_all.deb -BEGIN PGP SIGNATURE- Version: GnuPG v1.2.1 (GNU/Linux) iD8DBQE94Qtlp3U1z1PHTekRAjz3AKC9PKvQPIOlJXBlJlUVT5MKtfRgoACg3BAg YXPalsGjvwAI0H/Xfcj11hs= =wYxp -END PGP SIGNATURE- Accepted: libsensors-dev_2.6.5-3_i386.deb to pool/main/l/lm-sensors/libsensors-dev_2.6.5-3_i386.deb libsensors1_2.6.5-3_i386.deb to pool/main/l/lm-sensors/libsensors1_2.6.5-3_i386.deb lm-sensors-source_2.6.5-3_all.deb to pool/main/l/lm-sensors/lm-sensors-source_2.6.5-3_all.deb lm-sensors_2.6.5-3.diff.gz to pool/main/l/lm-sensors/lm-sensors_2.6.5-3.diff.gz lm-sensors_2.6.5-3.dsc to pool/main/l/lm-sensors/lm-sensors_2.6.5-3.dsc lm-sensors_2.6.5-3_i386.deb to pool/main/l/lm-sensors/lm-sensors_2.6.5-3_i386.deb sensord_2.6.5-3_i386.deb to pool/main/l/lm-sensors/sensord_2.6.5-3_i386.deb -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
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] Description: i2c-source - sources for drivers for the i2c bus Changes: i2c (2.6.5-3) unstable; urgency=low . * Realize that I was using cvs-buildpackage incorrectly. Bring forward a bunch of stuff, so this really is i2c-2.6.5 rather than, uh, 2.6.2. * Make similar changes to what's happened in lm-sensors: add a modules-nokpkg rule to build modules without kernel-package, and sort out binary-indep vs. binary-arch. Files: 0cf2e2cbc275c11d7cd7e28cb34b8af1 548 misc extra i2c_2.6.5-3.dsc 1103ea4972872d3e0a8e58d6923cf01b 17415 misc extra i2c_2.6.5-3.diff.gz 300196e9481b235e5fa72f535072c495 148872 misc extra i2c-source_2.6.5-3_all.deb -BEGIN PGP SIGNATURE- Version: GnuPG v1.2.1 (GNU/Linux) iD8DBQE94S6Mp3U1z1PHTekRAiYPAJ9MIBb6J/r6fzgxrleuEAwDH5rnZACdH7up +AgarhS200hSJTYyGdC6Jnk= =121Z -END PGP SIGNATURE- Accepted: i2c-source_2.6.5-3_all.deb to pool/main/i/i2c/i2c-source_2.6.5-3_all.deb i2c_2.6.5-3.diff.gz to pool/main/i/i2c/i2c_2.6.5-3.diff.gz i2c_2.6.5-3.dsc to pool/main/i/i2c/i2c_2.6.5-3.dsc -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [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] Description: xcircuit - Draw circuit schematics or almost anything. Closes: 166509 Changes: xcircuit (3.0rev4-1) unstable; urgency=low . * New upstream release. This includes a fix to a critical bug (though with a goto rather than a continue). (Closes: #166509) * Switch to using the default version of Python, rather than forcing python2.1. * No longer manage a /usr/doc link. (These things are much easier when you use debhelper. :-) Files: feb0a37dbc40b8b62c9796325de77b23 585 electronics extra xcircuit_3.0rev4-1.dsc 077fc584a311315ecaa0d606d847087e 690168 electronics extra xcircuit_3.0rev4.orig.tar.gz 3e6ff9aea780fd79e87b020b6f032fcd 20632 electronics extra xcircuit_3.0rev4-1.diff.gz e5210f11b391c4c9526ade9f79896e15 353380 electronics optional xcircuit_3.0rev4-1_i386.deb -BEGIN PGP SIGNATURE- Version: GnuPG v1.2.1 (GNU/Linux) iD8DBQE936JFp3U1z1PHTekRAhIPAJ9AKeLuvbazS3Egv7HQmeo4/5nXcwCeLef2 FMzwZBt2Zf4j9eK3JVeqfwU= =eCXE -END PGP SIGNATURE- Accepted: xcircuit_3.0rev4-1.diff.gz to pool/main/x/xcircuit/xcircuit_3.0rev4-1.diff.gz xcircuit_3.0rev4-1.dsc to pool/main/x/xcircuit/xcircuit_3.0rev4-1.dsc xcircuit_3.0rev4-1_i386.deb to pool/main/x/xcircuit/xcircuit_3.0rev4-1_i386.deb xcircuit_3.0rev4.orig.tar.gz to pool/main/x/xcircuit/xcircuit_3.0rev4.orig.tar.gz -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [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 [EMAIL PROTECTED] Changed-By: David Z Maze [EMAIL PROTECTED] Description: libsensors-dev - Lm-sensors development kit libsensors1 - Library to read temperature/voltage/fan sensors lm-sensors - Utilities to read temperature/voltage/fan sensors lm-sensors-source - Kernel drivers to read temperature/voltage/fan sensors (source) sensord- Hardware sensor information logging daemon Closes: 161799 Changes: lm-sensors (2.6.5-2) unstable; urgency=low . * Make kernel-package rules understand $(ROOT_CMD). (Closes: #161799) * Correctly separated out building (arch-dependent) binary packages from (arch-all) module source in debian/rules. * Add 'debian/rules modules-nokpkg' to build and install kernel modules locally without building a package, since the working 'make' invocation is kind of gross. Suggest using it in lm-sensors-source's README.Debian file. This addresses the concern brought out by #165508, though it doesn't actually make the requested change. Files: 8e5ed1400e7e59d2d40f4f576c519fde 696 utils extra lm-sensors_2.6.5-2.dsc acc90fa00e6809e4fd7fd0707eafb678 23970 utils extra lm-sensors_2.6.5-2.diff.gz 875e566a9b2da35d42811b729646c1e5 329872 utils extra lm-sensors_2.6.5-2_i386.deb 867af6adc7e7542d5aa4b97f5c852160 39238 libs optional libsensors1_2.6.5-2_i386.deb abce1fcc691ce56c229d3d589974ca24 53614 devel extra libsensors-dev_2.6.5-2_i386.deb 16b4323ccfeb1a1e652996ab7615bd20 37822 utils extra sensord_2.6.5-2_i386.deb 0a51f7cfdf8a1da62d88a081219fde4e 598304 misc extra lm-sensors-source_2.6.5-2_all.deb -BEGIN PGP SIGNATURE- Version: GnuPG v1.2.1 (GNU/Linux) iD8DBQE90I+3p3U1z1PHTekRApd7AKCjM9YFBkCRDw1HCbJhFFfmgr3TkwCgmgaU gWK77ULrO3Oi0VWp0FXFInM= =s8MG -END PGP SIGNATURE- Accepted: libsensors-dev_2.6.5-2_i386.deb to pool/main/l/lm-sensors/libsensors-dev_2.6.5-2_i386.deb libsensors1_2.6.5-2_i386.deb to pool/main/l/lm-sensors/libsensors1_2.6.5-2_i386.deb lm-sensors-source_2.6.5-2_all.deb to pool/main/l/lm-sensors/lm-sensors-source_2.6.5-2_all.deb lm-sensors_2.6.5-2.diff.gz to pool/main/l/lm-sensors/lm-sensors_2.6.5-2.diff.gz lm-sensors_2.6.5-2.dsc to pool/main/l/lm-sensors/lm-sensors_2.6.5-2.dsc lm-sensors_2.6.5-2_i386.deb to pool/main/l/lm-sensors/lm-sensors_2.6.5-2_i386.deb sensord_2.6.5-2_i386.deb to pool/main/l/lm-sensors/sensord_2.6.5-2_i386.deb -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
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] Description: i2c-source - sources for drivers for the i2c bus Changes: i2c (2.6.5-2) unstable; urgency=low . * Understand magic variables that might appear, like $(ROOT_CMD). * Since this is only an Architecture: all package, change Build-Depends to Build-Depends-Indep. Files: 5c019ed2284c846918fa5bdf4c88362f 548 misc extra i2c_2.6.5-2.dsc 96b9bfeeefb2bd762357ff26b062f391 33848 misc extra i2c_2.6.5-2.diff.gz 3b63cb04d7e9aa9b3d29708f0024713a 145854 misc extra i2c-source_2.6.5-2_all.deb -BEGIN PGP SIGNATURE- Version: GnuPG v1.2.1 (GNU/Linux) iD8DBQE9zH5Wp3U1z1PHTekRAl9DAJ4igBXUcTgeYB/WBOv1j3AcGXVWHQCfUhWd hJquUgmZEEaBYUTxh2nfMKU= =j6xM -END PGP SIGNATURE- Accepted: i2c-source_2.6.5-2_all.deb to pool/main/i/i2c/i2c-source_2.6.5-2_all.deb i2c_2.6.5-2.diff.gz to pool/main/i/i2c/i2c_2.6.5-2.diff.gz i2c_2.6.5-2.dsc to pool/main/i/i2c/i2c_2.6.5-2.dsc -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [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] Description: i2c-source - sources for drivers for the i2c bus Changes: i2c (2.6.5-1) unstable; urgency=low . * New upstream version. The Web page claims that this will only build on 2.4.x kernels, be aware! You can probably still make this build on 2.2.x kernels by removing the mentions of __exit where they appear in a half dozen files. Files: 65a756842d81cf259a5e4b557759033f 542 misc extra i2c_2.6.5-1.dsc b8f102ec047374231d81b112d7c9212a 120678 misc extra i2c_2.6.5.orig.tar.gz 2cbabe768eb8bef1c2ca468f0cf6675d 33760 misc extra i2c_2.6.5-1.diff.gz ec7af5a805174103d8140ec760645edd 145706 misc extra i2c-source_2.6.5-1_all.deb -BEGIN PGP SIGNATURE- Version: GnuPG v1.2.1 (GNU/Linux) iD8DBQE9wfftp3U1z1PHTekRAsY0AJ9DsWi743MCD47M6v/K58Ii5+AXnQCg29Qx PosDNne6da3axMlnB9mW3hE= =f4VU -END PGP SIGNATURE- Accepted: i2c-source_2.6.5-1_all.deb to pool/main/i/i2c/i2c-source_2.6.5-1_all.deb i2c_2.6.5-1.diff.gz to pool/main/i/i2c/i2c_2.6.5-1.diff.gz i2c_2.6.5-1.dsc to pool/main/i/i2c/i2c_2.6.5-1.dsc i2c_2.6.5.orig.tar.gz to pool/main/i/i2c/i2c_2.6.5.orig.tar.gz -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [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 package determines the final MLdB location of these ordinary files by asking the user via MLdB debconf. Why do these files not have a specified location? The two cases I can think of are (a) you're installing something that's system-wide, in which case you can just pick a location as the package maintainer, or (b) you're installing something that potentially multiple users would want to use. In the case of (a), I'd just unpack under /var/lib/genericpackage, and then use a symlink or Apache configuration or whatever to tell whatever it is that uses the files where they actually are. For something that multiple users could potentially want to use, really the best thing to do is provide a tarball in the package, and let the end-user be responsible for unpacking it where they feel is appropriate; this is the approach the various kernel module packages use. -- David Maze [EMAIL PROTECTED] http://people.debian.org/~dmaze/ Theoretical politics is interesting. Politicking should be illegal. -- Abra Mitchell
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 users that AR are allowed to use x (there must be an user that x runs under, I think AR best called x ;-)). The x startup script would then call xhost AR +user@localhost for all of these users, and the above commands would AR use xhost (if X is running) to update the status immediatly. Does user-based xhost authentication work? At all? AR Since xhost supports NIS, it would be good to accept users like this AR nis:[EMAIL PROTECTED] and, for network use [EMAIL PROTECTED] (one could simply pass AR names that contain '@' without appending '@localhost'). My impression is that anything involving NIS is horribly insecure. Is there any encryption/authentication in the X protocol? AFAIK, the Kerberos-based authentication is horribly broken and won't work with any version of Kerberos 5 released within the past 5 years. Nothing else is secure at all over the network. (Hence, the popularity of X tunnelling over ssh.) BTW, why would you *want* to do this? You're basically creating a class of local and/or remote users who can spy on/take over arbitrary users' X sessions. I'd be pretty scared if I was using a system and another user's X windows started popping up on top of mine. Other things to think about if you're really set on doing this: what keeps the logged-in user from running 'xhost [EMAIL PROTECTED]'? What keeps someone on the acl from running 'xhost -:0.0'? What if there are multiple X servers running on the machine? -- David Maze [EMAIL PROTECTED] http://www.mit.edu/~dmaze/ Theoretical politics is interesting. Politicking should be illegal. -- Abra Mitchell -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
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 they necessary? Is the fact that I _have_ to have 2.0.32 LA source or headers going to stop me from going to 2.0.33? HM HM I don't know why all those patches are already applied. I have HM stopped using the kernel-source packages because they can't be HM patched up to the next kernel version easily (because of the HM already applied patches). You should be able to install HM kernel-headers to satisfy it and then dump the standard Linux HM source tree in for building kernels. SD SD Does anyone know why there is a dependency on kernel-headers? I SD was under the impression that glibc didn't use the kernel headers. ...or why it depends on kernel-headers-2.0.32 instead of just kernel-headers, which is provided by the kernel-source-* and kernel-headers-* packages? -- _ / \ The cat's been in the box for over | David Maze | 20 years. Nobody's feeding it. The | [EMAIL PROTECTED] |cat is dead. | http://donut.mit.edu/dmaze/ | -- Grant, on Schroedinger's Cat \_/ -- TO UNSUBSCRIBE FROM THIS MAILING LIST: e-mail the word unsubscribe to [EMAIL PROTECTED] . Trouble? e-mail to [EMAIL PROTECTED] .
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 years. Nobody's feeding it. The | [EMAIL PROTECTED] |cat is dead. | http://donut.mit.edu/dmaze/ | -- Grant, on Schroedinger's Cat \_/ -- TO UNSUBSCRIBE FROM THIS MAILING LIST: e-mail the word unsubscribe to [EMAIL PROTECTED] . Trouble? e-mail to [EMAIL PROTECTED] .
/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...) -- _ / \ The cat's been in the box for over | David Maze | 20 years. Nobody's feeding it. The | [EMAIL PROTECTED] |cat is dead. | http://donut.mit.edu/dmaze/ | -- Grant, on Schroedinger's Cat \_/ -- TO UNSUBSCRIBE FROM THIS MAILING LIST: e-mail the word unsubscribe to [EMAIL PROTECTED] . Trouble? e-mail to [EMAIL PROTECTED] .
