mplayer 1.0pre6a-4 for i386 and PowerPC
hi everybody thanks to help of many people (both on debian-legal , debian-devel , and privately), I have prepared a new debugged improved version of mplayer for the Debian archive : namely version 1.0pre6-4 Simon McVittie , in particular, has tried my packaging in powerpc : so he has provided me with many corrections , and with a powerpc binary Both source, i386 and powerpc binaries , are accessible at http://tonelli.sns.it/pub/mplayer/sarge I REALLY think that the time has come for mplayer to be part of Debian a. signature.asc Description: Digital signature
Re: Shouldn't kernel-image-2.6.x-y-z depend on alsa-base ?
Le jeudi 10 mars 2005 à 08:17 +0100, Goswin von Brederlow a écrit : > The kernel could blacklist alsa modules by default and the alsa-base > would divert that to blacklist oss. That sounds the simplest. It isn't possible to divert files in /etc. -- .''`. Josselin Mouette/\./\ : :' : [EMAIL PROTECTED] `. `'[EMAIL PROTECTED] `- Debian GNU/Linux -- The power of freedom
Re: NPTL and static linking
Josselin Mouette wrote: > Le mercredi 09 mars 2005 à 11:23 -0800, Blunt Jackson a écrit : >> I appreciate the clarification. What is desirable, then, is for the developer >> to be able to statically link his or her own libraries, and third >> party libraries, >> but to dynamically pick up "system" libraries, of which I would number >> libpthread. That would be adequate for my needs. I expect this is possible, >> as *everything* is possible, somehow. Perhaps it is something as trivial >> as a compiler or linker flag that I have missed? > > Yup, just enclose the libraries you want to link statically against > between -Wl,-Bstatic and -Wl,-Bdynamic: > > gcc -o something foo.o bar.o -lsystemlib -Wl,-Bstatic -lownlib > -lthirdpartylib -Wl,-Bdynamic -lpthread -Wl,-static ... -Wl,-dy are equivalent and shorter :-) -- Kevin B. McCarty <[EMAIL PROTECTED]> Physics Department WWW: http://www.princeton.edu/~kmccarty/Princeton University GPG public key ID: 4F83C751 Princeton, NJ 08544 -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
Re: Cron-standard package to replace current tasks in 'cron'
On Wed, Mar 09, 2005 at 11:04:04PM -0500, sean finney wrote: > i would argue then that user should use a tool called "rm", or "mv" :) Hmm, rm -rf: read mail, really fast? Bastian -- One does not thank logic. -- Sarek, "Journey to Babel", stardate 3842.4
Re: Shouldn't kernel-image-2.6.x-y-z depend on alsa-base ?
> Thomas Hood <[EMAIL PROTECTED]> writes: > > If a fresh sarge/2.6 system lacks alsa-base then this would seem to be a > > problem because in that case nothing enforces the mutual exclusion of OSS > > and ALSA modules. If linux26 doesn't install alsa-base then perhaps it > > should do so. Even better, possibly, would be to give the user a choice > > between OSS and ALSA: if the user chooses ALSA then she gets alsa-base; > > if she chooses OSS then she gets the (currently nonexistent) "oss" package > > which blacklists ALSA modules. > > The kernel could blacklist alsa modules by default and the alsa-base > would divert that to blacklist oss. That sounds the simplest. So to be clear the alternatives suggested so far are: 1. The two-package approach * oss blacklists ALSA modules * alsa-base blacklists OSS modules * alsa-base Conflicts with oss * kernel-image Depends on alsa-base | oss 2. The diversion approach * ALSA modules are blacklisted by default * alsa-base de-blacklists ALSA modules and blacklists OSS modules * linux26 installs alsa-base Have I got that right? -- Thomas Hood -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
Is Anthony Fok MIA?
Hi folks It seems that Anthony Foka is missing in action. He does not respond to bugs which removes his packages from the release. Current bug statistic: grave: 13 serious: 14 important: 21 outstanding: 146 fixed in NMU: 26 Current package statistic: count: 46 in woody: 40 in sarge: 40 same version in woody, sarge, sid: 6 same upstream version in woody, sarge, sid: 27 nmued versions in sid: 14 Bastian -- There's another way to survive. Mutual trust -- and help. -- Kirk, "Day of the Dove", stardate unknown signature.asc Description: Digital signature
Re: Shouldn't kernel-image-2.6.x-y-z depend on alsa-base ?
On Wed, Mar 09, 2005 at 05:46:22PM -0800, Steve Langasek <[EMAIL PROTECTED]> wrote: > Considering you're talking about solutions that require updates to > kernel-image packages *anyway*, why has no one suggested adding the > necessary blacklist entries to these packages? Far better than removing a > bunch of modules from the kernel-image at this late stage, IMHO. It doesn't work properly with several kernel-images installed. Mike -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
Re: mipsel binutils/gcc/glibc shared library breakage
Thiemo, The code builds OK. It even runs if I put less than 4 symbols in a shared library (it works with 3 symbols for sure). I presume multigot problem is unrelated to this... Pjotr Kourzanov On Thu, Mar 10, 2005 at 12:32:38AM +0100, Thiemo Seufer wrote: > Pjotr Kourzanov wrote: > > Dear Debian developers, > > > > I gather there are some people out there with MIPS little-endian > > machines (from mipsel drop discussion) and Debian on it. Do huge shared > > libraries (containing >4 symbols) work for you? I am currently > > investigating an issue I have with my MIPS32r4, binutils > 2.14.90, > > gcc-3.3.5 and glibc 2.3.2 (all Debian sources), which prevents e.g. > > Qt/Embedded to be used as shared library. > > The Debian binutils refuse to build multigot libraries with more than > 16k external symbols. This is a workaround to prevent silent breakage, > and most larger shared libraries can still be built by compiling with > -Wa,-xgot. > > > Thiemo > -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
Re: Is Anthony Fok MIA?
Bastian Blank <[EMAIL PROTECTED]> schrieb: > Hi folks > > It seems that Anthony Foka is missing in action. He does not respond to > bugs which removes his packages from the release. Have you asked [EMAIL PROTECTED] Regards, Frank -- Frank Küster Inst. f. Biochemie der Univ. Zürich Debian Developer
Re: Switchconf: Orphaning or removing?
Scripsit Thomas Hood <[EMAIL PROTECTED]> > laptop-net also contains a configuration file switching mechanism. For that matter, so does ifupdown. I have a bunch of post-up 'ln -fs' commands in the appropiate /etc/network/interfaces on my laptop. Does switchconf do more than can be simulated easily by that? -- Henning Makholm "Det er du nok fandens ene om at mene. For det ligger i Australien!" -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
Re: mipsel drop / buildd situation Was: [Fwd: Re: GTK+2.0 2.6.2-3 and buildds running out of space]
On Tue, 2005-03-08 at 16:22 -0800, Steve Langasek wrote: > Hi Gergely, > > On Wed, Mar 09, 2005 at 12:56:10AM +0100, Gergely Nagy wrote: > > Just to chime in, not saying that maintaining a consistent state between > > architectures is an easy thing and presents no problems, but Debian is > > the only distribution that supports all these many architectures. This > > has the *HUGE* benefit of making the life of those of us who actually > > run quite a few different architectures, to have the same distribution > > on all our machines. > > > So, from my point of view, there aren't too many architectures. > > Actually, the fact that Debian runs on so many architectures is in the > > top five reasons I'm a Debian user. > > Out of curiosity, how many of these architectures are you running stable on? i386, arm, m68k, mipsel. (alpha, powerpc and possibly sparc will be added to the list when sarge releases; if amd64 was official, that would get added there too) -- Gergely Nagy -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
automake/autoconf in build-dependencies
I have often tried to argue my position on automake/autoconf in packages' build dependencies: I do not think they belong there. If a package does not build without automake or autoconf, it is broken and should be fixed. However, bugs like #298336 seem to suggest that other maintainers deem it entirely appropriate to "go the easy way" -- if I may call it that without being condescending towards Uwe. I seem to recall the devel-reference or some similar document to specifically address this issue, but I cannot find the location anymore. Thus I am interested in opinions of people who argue that automake/autoconf are perfectly acceptable as build dependencies. Also, are there technical arguments against these build dependencies? I am too inexperienced with the GNU autotools to come up with something. I am perfectly aware that there are (and should be) exceptions. For instance, if a package should be made available sooner rather than later, and the maintainer then sits down to work on the autotools configuration to fix the bug for the next upload. However, this always bears the danger that the maintainer then loses interest and the archive will contain what I claim to be a broken source package... even though it may well build. -- Please do not send copies of list mail to me; I read the list! .''`. martin f. krafft <[EMAIL PROTECTED]> : :' :proud Debian developer, admin, user, and author `. `'` `- Debian - when you have better things to do than fixing a system Invalid/expired PGP subkeys? Use subkeys.pgp.net as keyserver! signature.asc Description: Digital signature
Re: Switchconf: Orphaning or removing?
also sprach Henning Makholm <[EMAIL PROTECTED]> [2005.03.10.1309 +0100]: > > laptop-net also contains a configuration file switching > > mechanism. > > For that matter, so does ifupdown. I have a bunch of post-up 'ln > -fs' commands in the appropiate /etc/network/interfaces on my > laptop. Does switchconf do more than can be simulated easily by > that? It provides a helpful means of abstraction, I find. Rather than keeping n files for each of m locations somewhere, and adding n /bin/ln calls to m interfaces(5) stanzas, I prefer to add the n files to the filesystem (as I have to do in any case) and rely on switchconf to process them all with a single call. -- Please do not send copies of list mail to me; I read the list! .''`. martin f. krafft <[EMAIL PROTECTED]> : :' :proud Debian developer, admin, user, and author `. `'` `- Debian - when you have better things to do than fixing a system Invalid/expired PGP subkeys? Use subkeys.pgp.net as keyserver! signature.asc Description: Digital signature
Re: Serious kernel problems on new i386 hardware
On Thu, Mar 10, 2005 at 03:10:12PM +0100, Andreas Tille <[EMAIL PROTECTED]> wrote: > ERROR: Removing 'trm290': Device or resource busy > ERROR: Removing 'vis82cxxx': Device or resource busy > pivot_root: No such file or directory > /sbin/init: 432: cannot open dev/console: No such file > Kernel panic - not syncing: Attempt to kill init! Let me guess... you are using devfs in 2.4, and /dev is empty if devfs is not mounted. Mike -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
Re: Serious kernel problems on new i386 hardware
On Thu, 10 Mar 2005, Mike Hommey wrote: On Thu, Mar 10, 2005 at 03:10:12PM +0100, Andreas Tille <[EMAIL PROTECTED]> wrote: ERROR: Removing 'trm290': Device or resource busy ERROR: Removing 'vis82cxxx': Device or resource busy pivot_root: No such file or directory /sbin/init: 432: cannot open dev/console: No such file Kernel panic - not syncing: Attempt to kill init! Let me guess... you are using devfs in 2.4, and /dev is empty if devfs is not mounted. Sorry, I did nothing but installing Debian from scratch and installing several kernel-image-2.6.x packages afterwards. I did no fiddling around with devfs whatever (to be honest I do not even have an idea why I should if everything would work fine). The only hint Google was able to reveal was a broken initrd which is not able to handle SATA - but as I said, I tried to disable SATA for exactly this reason (perhaps I failed but this does not explain why 2.4.x works). Please tell me what I should check and report to follow your idea. Kind regards Andreas. -- http://fam-tille.de -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
Re: Serious kernel problems on new i386 hardware
On Thu, 10 Mar 2005 15:48:55 +0100 (CET) Andreas Tille <[EMAIL PROTECTED]> wrote: > On Thu, 10 Mar 2005, Mike Hommey wrote: > > > On Thu, Mar 10, 2005 at 03:10:12PM +0100, Andreas Tille > > <[EMAIL PROTECTED]> wrote: > >> ERROR: Removing 'trm290': Device or resource busy > >> ERROR: Removing 'vis82cxxx': Device or resource busy > >> pivot_root: No such file or directory > >> /sbin/init: 432: cannot open dev/console: No such file > >> Kernel panic - not syncing: Attempt to kill init! > > > > Let me guess... you are using devfs in 2.4, and /dev is empty if > > devfs is not mounted. > Sorry, I did nothing but installing Debian from scratch and installing > several kernel-image-2.6.x packages afterwards. I did no fiddling > around with devfs whatever (to be honest I do not even have an idea > why I should if everything would work fine). > > The only hint Google was able to reveal was a broken initrd which is > not able to handle SATA - but as I said, I tried to disable SATA for > exactly this reason (perhaps I failed but this does not explain why > 2.4.x works). Which version of the Debian-Installer did you use? We had similar symptoms on a new Dell recently at work and had to grab the latest daily build to get a working version. I can check on the exact date of the daily build we used, if you want. HTH, Jacob -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
Re: automake/autoconf in build-dependencies
Scripsit martin f krafft <[EMAIL PROTECTED]> > I seem to recall the devel-reference or some similar document to > specifically address this issue, but I cannot find the location > anymore. Are you thinking about /usr/share/doc/autotools-dev/README.Debian.gz? -- Henning Makholm "They discussed old Tommy Somebody and Jerry Someone Else." -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
Re: Serious kernel problems on new i386 hardware
On Thu, Mar 10, 2005 at 03:10:12PM +0100, Andreas Tille wrote: > Hi, > I've got a new Dell machine which I was able to install with Kernel 2.4.27. > It has a SATA drive but I disabled SATA in BIOS according to the manuals. > All I write in the following has this SATA disabled BIOS setting. > As I said kernel 2.4.27 works fine. I attach a dmesg and syslog to this > mail. > I tried to upgrade to a 2.6.x kernel but failed always with kernel_panic. > I tried 2.6.8, 2.6.8 and 2.6.10 (here -1-386 and -1-686 versions) and > all failed with the same result: > pivot_root: No such file or directory > /sbin/init: 432: cannot open dev/console: No such file > Kernel panic - not syncing: Attempt to kill init! > ata: 0x1f0 IDE port busy > ata1: SATA max UDMA/133 cmd 0x170 ctl 0x376 bmdma 0xFFA8 irq 15 > ata1: dev 0 ATAPI, max UDMA/33 > ata1: dev 1 ATAPI, max UDMA/33 > ata1: dev 0 configured for UDMA/33 > ata1: dev 1 configured for UDMA/33 > scsi0 : ata_piix > elevator: using anticipatory as default io scheduler > Uniform Multi-Platform E-IDE driver Revision: 7.00alpha2 > ide: Assuming 33MHz system bus speed for PIO modes; override with idebus=xx > ide0: I/O resource 0x1F0-0x1F7 not free. > ide0: ports already in use, skipping probe > ide1: I/O resource 0x170-0x177 not free. > ide1: ports already in use, skipping probe This is your problem here. You made your initrd under 2.4.27, where your devices where /dev/hd?. However, 2.6 with the initrd has loaded them with the SATA driver, and sees them via /dev/sd?. I think you're going to have to manuall edit your initrd and fstab to deal with the change in device name between versions. Alternatively, pull ata_piix driver out of the initrd, and see if the ide driver will load and run your disks. However, that first line (IDE port busy) worries me a little, since it seems neither driver is actually claiming the port itself. If you want to experiment, there's a command you can put on the Linux kernel command line to break into the initrd before it actually does anything, and you can see what devices exist and drivers and whatnot. I can't remember the command though. -_- -- --- Paul "TBBle" Hampson, MCSE 8th year CompSci/Asian Studies student, ANU The Boss, Bubblesworth Pty Ltd (ABN: 51 095 284 361) [EMAIL PROTECTED] "No survivors? Then where do the stories come from I wonder?" -- Capt. Jack Sparrow, "Pirates of the Caribbean" This email is licensed to the recipient for non-commercial use, duplication and distribution. --- signature.asc Description: Digital signature
Re: automake/autoconf in build-dependencies
On Thu, Mar 10, 2005 at 01:52:45PM +0100, martin f krafft wrote: > I have often tried to argue my position on automake/autoconf in > packages' build dependencies: I do not think they belong there. If > a package does not build without automake or autoconf, it is broken > and should be fixed. However, bugs like #298336 seem to suggest that > other maintainers deem it entirely appropriate to "go the easy way" > -- if I may call it that without being condescending towards Uwe. > I seem to recall the devel-reference or some similar document to > specifically address this issue, but I cannot find the location > anymore. I think you're thinking of /usr/share/doc/autotools-dev/README.Debian.gz > Thus I am interested in opinions of people who argue that > automake/autoconf are perfectly acceptable as build dependencies. > Also, are there technical arguments against these build > dependencies? I am too inexperienced with the GNU autotools to > come up with something. The arguments _for_ build-depending on the various autotools are (off the top of my head) (In the below, read autoconf as autoconf/automake. ^_^) * keeps .diff.gz small and readable, as configure changes are not included. And small configure.in changes cascade into many configure changes * This is a maintainer decision, really. Not _wrong_ per se. * timestamp skew means that the autobuilt makefiles will try to rebuild configure from configure.in even if configure is patched by dpkg-source at the same time as configure.in * A solution for this is in the above-mentioned README.Debian * Upstream distributes without generated files (eg. CVS pull) or with generated files using older or buggier versions of the autotools. * In this case, pristine source tarball means pre-autoconf, and the maintainer again wants to keep the .diff.gz small. > I am perfectly aware that there are (and should be) exceptions. For > instance, if a package should be made available sooner rather than > later, and the maintainer then sits down to work on the autotools > configuration to fix the bug for the next upload. However, this > always bears the danger that the maintainer then loses interest and > the archive will contain what I claim to be a broken source > package... even though it may well build. I'm not sure I'd consider a package that build-depends on autoconf to be _broken_ per se. I don't _believe_ this shows up anywhere in policy or otherwise that can make this a non-ignorable bug report for such a package. I welcome corrections on this point. I am particularly interested in an argument that spells out how this is broken, as opposed to "not neat in my opinion". I _do_ think it is a riskier way of dealing with a package, as I'm not sure what new features are expected to appear in autoconf that weren't in the version used at last build-time, that can be taken advantage of automatically. Surely a bugfix in autoconf would have either already caused a bugreport against the package, or have been irrelevant to the package itself? Certainly, this dubious benefit to my mind does not outweigh the risk of having a previously working build-environment suddenly break, as I vaugely recall happened when autoconf went from 2.13 to 2.53 and suddenly half of the Debian archive FTBFS. (Exaggeration used for effect. ^_^) I don't see how build-depending on autoconf etc could possibly speed up a package release, unless the maintainer is trying to move to a different autoconf version than upstream is using, and refuses to install the version upstream is using. (But is happy for the buildds to do so) In short, _I_ wouldn't do it, same as I wouldn't build-depend on flex and bison. I might not store their output in my CVS tree, but I wouldn't build-depend on them either. (And if anyone feels the need to ask me what this means in terms of 'What is source?' they get to stand between me and Andrew Suffield if I answer. ^_^) (This doesn't apply to config.sub and config.guess. I _do_ pull those at build-time, since _they_ sometimes need to be upgraded for different architectures. This is a different (controversial?) issue. ^_^) -- --- Paul "TBBle" Hampson, MCSE 8th year CompSci/Asian Studies student, ANU The Boss, Bubblesworth Pty Ltd (ABN: 51 095 284 361) [EMAIL PROTECTED] "No survivors? Then where do the stories come from I wonder?" -- Capt. Jack Sparrow, "Pirates of the Caribbean" This email is licensed to the recipient for non-commercial use, duplication and distribution. --- signature.asc Description: Digital signature
Re: Serious kernel problems on new i386 hardware
might be fixable by regenerating a new initrd for the 2.6 kernel: mkinitrd -v /boot/initrd-2.6.x-x.img 2.6.x-x make sure to add this line to the grube menue.lst: initrd /boot/initrd-2.6.x-x.img On Fri, 11 Mar 2005 02:01:42 +1100, Paul Hampson wrote > On Thu, Mar 10, 2005 at 03:10:12PM +0100, Andreas Tille wrote: > > Hi, > > > I've got a new Dell machine which I was able to install with Kernel 2.4. 27. > > It has a SATA drive but I disabled SATA in BIOS according to the manuals. > > All I write in the following has this SATA disabled BIOS setting. > > > As I said kernel 2.4.27 works fine. I attach a dmesg and syslog to this > > mail. > > > I tried to upgrade to a 2.6.x kernel but failed always with kernel_panic. > > I tried 2.6.8, 2.6.8 and 2.6.10 (here -1-386 and -1-686 versions) and > > all failed with the same result: > > > pivot_root: No such file or directory > > /sbin/init: 432: cannot open dev/console: No such file > > Kernel panic - not syncing: Attempt to kill init! > > > ata: 0x1f0 IDE port busy > > ata1: SATA max UDMA/133 cmd 0x170 ctl 0x376 bmdma 0xFFA8 irq 15 > > ata1: dev 0 ATAPI, max UDMA/33 > > ata1: dev 1 ATAPI, max UDMA/33 > > ata1: dev 0 configured for UDMA/33 > > ata1: dev 1 configured for UDMA/33 > > scsi0 : ata_piix > > elevator: using anticipatory as default io scheduler > > Uniform Multi-Platform E-IDE driver Revision: 7.00alpha2 > > ide: Assuming 33MHz system bus speed for PIO modes; override with idebus=xx > > ide0: I/O resource 0x1F0-0x1F7 not free. > > ide0: ports already in use, skipping probe > > ide1: I/O resource 0x170-0x177 not free. > > ide1: ports already in use, skipping probe > > This is your problem here. You made your initrd under 2.4.27, where your > devices where /dev/hd?. However, 2.6 with the initrd has loaded them > with the SATA driver, and sees them via /dev/sd?. > > I think you're going to have to manuall edit your initrd and fstab to > deal with the change in device name between versions. > > Alternatively, pull ata_piix driver out of the initrd, and see if the > ide driver will load and run your disks. > > However, that first line (IDE port busy) worries me a little, since > it seems neither driver is actually claiming the port itself. > > If you want to experiment, there's a command you can put on the Linux > kernel command line to break into the initrd before it actually does > anything, and you can see what devices exist and drivers and whatnot. > > I can't remember the command though. -_- > > -- > --- > Paul "TBBle" Hampson, MCSE > 8th year CompSci/Asian Studies student, ANU > The Boss, Bubblesworth Pty Ltd (ABN: 51 095 284 361) > [EMAIL PROTECTED] > > "No survivors? Then where do the stories come from I wonder?" > -- Capt. Jack Sparrow, "Pirates of the Caribbean" > > This email is licensed to the recipient for non-commercial > use, duplication and distribution. > --- -- Have fun! -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
Debian LDAP schema for Debian Packages
Hi all, I have noticed debian has its own OID in IANA and googling I could only find userdir-ldap.schema in db.debian.org. I wonder if there is a debian ldap schema to store debian packages. Better yet, are we going to have one ever? cheers, juan -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
Status of bonsai package
Hi, what is the status of the bonsai package? There a serious bugs (not reported) and should be fixed. A new version of Bonsai is also available? -- Raphael Bossek -- DSL Komplett von GMX +++ Supergünstig und stressfrei einsteigen! AKTION "Kein Einrichtungspreis" nutzen: http://www.gmx.net/de/go/dsl -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
Re: NPTL and static linking
Kevin B. McCarty wrote: > Josselin Mouette wrote: > > > Le mercredi 09 mars 2005 à 11:23 -0800, Blunt Jackson a écrit : > >> I appreciate the clarification. What is desirable, then, is for the > >> developer > >> to be able to statically link his or her own libraries, and third > >> party libraries, > >> but to dynamically pick up "system" libraries, of which I would number > >> libpthread. That would be adequate for my needs. I expect this is possible, > >> as *everything* is possible, somehow. Perhaps it is something as trivial > >> as a compiler or linker flag that I have missed? > > > > Yup, just enclose the libraries you want to link statically against > > between -Wl,-Bstatic and -Wl,-Bdynamic: > > > > gcc -o something foo.o bar.o -lsystemlib -Wl,-Bstatic -lownlib > > -lthirdpartylib -Wl,-Bdynamic -lpthread > > -Wl,-static ... -Wl,-dy are equivalent and shorter :-) -Wl,-dn ... -Wl,-dy for further obfuscation. :-) Thiemo -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
Bug#298899: ITP: gourmet -- a recipe manager
Package: wnpp Severity: wishlist Owner: Robert Lemmen <[EMAIL PROTECTED]> * Package name: gourmet Version : 0.8.0 Upstream Author : [EMAIL PROTECTED] * URL : https://sourceforge.net/projects/grecipe-manager/ * License : GPL Description : a recipe manager Gourmet Recipe Manager is a recipe-organizer for GNOME that generates shopping lists and allows rapid searching of recipes. It imports mealmaster & mastercook files and exports webpages & other formats short and long description will be reworked together with upstream cu robert -- System Information: Debian Release: 3.1 APT prefers experimental APT policy: (600, 'experimental'), (500, 'unstable') Architecture: i386 (i686) Kernel: Linux 2.6.11.2 Locale: LANG=C, [EMAIL PROTECTED] (charmap=ISO-8859-15) -- Robert Lemmen http://www.semistable.com signature.asc Description: Digital signature
Re: Status of bonsai package
On Thu, Mar 10, 2005 at 04:33:32PM +0100, Raphael Bossek wrote: > Hi, > > what is the status of the bonsai package? There a serious bugs (not > reported) and should be fixed. A new version of Bonsai is also available? Well, please do file those bugs then! I see neither this serious bug, nor a bug wishing for new upstream. In december, the maintainer has stated something to the lines of needing help with the package[1]. --Jeroen [1] http://lists.debian.org/debian-qa/2004/12/msg00030.html Last part of the message -- Jeroen van Wolffelaar [EMAIL PROTECTED] (also for Jabber & MSN; ICQ: 33944357) http://Jeroen.A-Eskwadraat.nl -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
Re: Serious kernel problems on new i386 hardware
On Thu, 10 Mar 2005, Jacob S wrote: Which version of the Debian-Installer did you use? We had similar symptoms on a new Dell recently at work and had to grab the latest daily build to get a working version. I can check on the exact date of the daily build we used, if you want. On my desk I see only a CD with the hand written text "Sarge RC 2" and thus I'm relatively sure I took this one ... Are there any traces left in a logfile or something like that which contains the exact installer version? Kind regards Andreas. -- http://fam-tille.de -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
Re: Serious kernel problems on new i386 hardware
On Thu, 10 Mar 2005, Thomas Schneller wrote: mkinitrd -v /boot/initrd-2.6.x-x.img 2.6.x-x I guess you mean here "s/-v/-o/", right? Well, I did so mkinitrd -o /boot/initrd.img-2.6.10-1-686 2.6.10-1-686 (under # uname -a Linux wr-linux03 2.4.27-1-386 #1 Wed Dec 1 19:43:08 JST 2004 i686 GNU/Linux ) but nothing changed. The hint with the initrd problem was given when trying to get SATA work - but this will be only my next step once I switch SATA on in BIOS ... make sure to add this line to the grube menue.lst: initrd /boot/initrd-2.6.x-x.img Sure - I did not changed the default grub boot menu which is created by the kernel package. Not now - later, if the default Debian kernel works I normally go without an initial ramdisk. Kind regards Andreas. -- http://fam-tille.de -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
Re: Shouldn't kernel-image-2.6.x-y-z depend on alsa-base ?
[EMAIL PROTECTED] writes: >> Thomas Hood <[EMAIL PROTECTED]> writes: >> > If a fresh sarge/2.6 system lacks alsa-base then this would seem to be a >> > problem because in that case nothing enforces the mutual exclusion of OSS >> > and ALSA modules. If linux26 doesn't install alsa-base then perhaps it >> > should do so. Even better, possibly, would be to give the user a choice >> > between OSS and ALSA: if the user chooses ALSA then she gets alsa-base; >> > if she chooses OSS then she gets the (currently nonexistent) "oss" package >> > which blacklists ALSA modules. >> >> The kernel could blacklist alsa modules by default and the alsa-base >> would divert that to blacklist oss. That sounds the simplest. > > > So to be clear the alternatives suggested so far are: > > 1. The two-package approach > > * oss blacklists ALSA modules > * alsa-base blacklists OSS modules > * alsa-base Conflicts with oss > * kernel-image Depends on alsa-base | oss I would prefer "oss | alsa-base". Oss always worked out of the box for me and alsa never. > 2. The diversion approach > > * ALSA modules are blacklisted by default > * alsa-base de-blacklists ALSA modules and blacklists OSS modules > * linux26 installs alsa-base > > Have I got that right? > -- > Thomas Hood Why should linux26 install alsa-base? That would mean OSS will always be blacklisted. It would be beter if the D-I arch-detect looks at the soundcard of the system and then recommends either OSS or ALSA as default depending on it. MfG Goswin -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
Re: Serious kernel problems on new i386 hardware
Andreas Tille schrieb am Donnerstag, 10. März 2005 um 15:10:12 +0100: > Hi, > > I've got a new Dell machine which I was able to install with Kernel 2.4.27. > It has a SATA drive but I disabled SATA in BIOS according to the manuals. > All I write in the following has this SATA disabled BIOS setting. > [...] > I tried to upgrade to a 2.6.x kernel but failed always with kernel_panic. > I tried 2.6.8, 2.6.8 and 2.6.10 (here -1-386 and -1-686 versions) and > all failed with the same result: > [...] > The third attachment is what I dumped manually from the screen (I left out > certain parts which I could send later on request). I regard it as a > serious > bug but I'm not sure if this is a "mass bug filing" if all 2.6.x > kernel-images > for i386 fail or how to handle this. > > Any hint how to fix this? > It seems that you ran into the "SATA is now supported by the SCSI driver" problem. > Freeing unused kernel memory: 220k freed > initrd-tools: 0.1.77 > vesafb: probe of vesafb0 failed with error -6 > NET: Registered protocol family 1 > SCSI subsystem initialized > ACPI: PCI interrupt :00:1f.2[C] -> GSI 20 (level, low) -> IRQ 169 > ata: 0x1f0 IDE port busy > ata1: SATA max UDMA/133 cmd 0x170 ctl 0x376 bmdma 0xFFA8 irq 15 > ata1: dev 0 ATAPI, max UDMA/33 > ata1: dev 1 ATAPI, max UDMA/33 > ata1: dev 0 configured for UDMA/33 > ata1: dev 1 configured for UDMA/33 > scsi0 : ata_piix At this time the libata based driver is loaded for your harddisk > elevator: using anticipatory as default io scheduler > Uniform Multi-Platform E-IDE driver Revision: 7.00alpha2 > ide: Assuming 33MHz system bus speed for PIO modes; override with idebus=xx > ide0: I/O resource 0x1F0-0x1F7 not free. > ide0: ports already in use, skipping probe > ide1: I/O resource 0x170-0x177 not free. > ide1: ports already in use, skipping probe and the 'old' IDE-Driver cannot be loaded any more. disable one of these two conflicting drivers, but notice that you'll need scsi disk support for the libata driver and the devices will change from hd?? to sd?? -- Jörg Friedrich There are only 10 types of people: Those who understand binary and those who don't. -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
Re: Serious kernel problems on new i386 hardware
On Thu, 10 Mar 2005 17:04:55 +0100 (CET) Andreas Tille <[EMAIL PROTECTED]> wrote: > On Thu, 10 Mar 2005, Jacob S wrote: > > > Which version of the Debian-Installer did you use? We had similar > > symptoms on a new Dell recently at work and had to grab the latest > > daily build to get a working version. I can check on the exact date > > of the daily build we used, if you want. > On my desk I see only a CD with the hand written text "Sarge RC 2" and > thus I'm relatively sure I took this one ... > Are there any traces left in a logfile or something like that which > contains the exact installer version? I faintly remember hearing about an installer log, but I don't remember where to find it. I just checked my docs and the installer we had problems with was RC2. The daily build we used that worked for us was from Feb. 23rd. I would assume that newer daily builds would work as well. HTH, Jacob -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
Re: xend is stopped before xendomains in debs
On Thu, 10 Mar 2005, Miquel van Smoorenburg wrote: > On Wed, 9 Mar 2005, Adam Heath wrote: > >On Wed, 9 Mar 2005, Adam Heath wrote: > >>On Wed, 9 Mar 2005, Henning Glawe wrote: > >>> > >>> Moin, > >>> just discovered a small problem in the xen-debian packages (2.0.4-4, from > >>> people.d.o): > >>> the sysv init links are done in the following way: > >>> > >>> S20xend > >>> S20xendomains > >>> K20xend > >>> K20xendomains > >>> > >>> so xend is shutdown before the xen-domains are shutdown, which of cause > >>> fails > >>> when there's no xend... > > > >>This is a bug in run-parts. It should reverse the order. > >> > >>Or you are not understanding how it works. > > > >reassign 298783 sysv-rc > >thanks > > I don't understand. What is the bug? The order sysv-rc uses to > run the scripts is the standard order used by POSIX when you > do a "for i in S??*". That is well known. If that isn't what > you'd like it to be, fix the priority of the Sxx symlinks. > > Or am I overlooking something ? Hrm. Maybe this is a problem with update-rc.d. But I don't know. update-rc.d defaults bar creates rc2.d/S20bar and rc6.d/K20bar, and update-rc.d defaults foo creates rc2.d/S20foo and rc6.d/K20foo. During start, bar is started before foo, which is what is expected. However, during shutdown, bar is stopped *before* foo, instead of the other way around. Yes, one can change the priority of one of the scripts. But that is a lot more overhead. I'm cc'ing devel, as this could be a more general problem, worthy of a broader fix. -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
Re: Shouldn't kernel-image-2.6.x-y-z depend on alsa-base ?
Goswin Brederlow writes: > Thomas Hood <[EMAIL PROTECTED]> writes: > > So to be clear the alternatives suggested so far are: > > > > 1. The two-package approach > > > > * oss blacklists ALSA modules > > * alsa-base blacklists OSS modules > > * alsa-base Conflicts with oss > > * kernel-image Depends on alsa-base | oss > > I would prefer "oss | alsa-base". Oss always worked out of the box for > me and alsa never. Well, k-i 2.4 should Depend on "oss | alsa-base"; k-i 2.6 should Depend on "alsa-base | oss". If only one k-i is installed then it will determine which of the two is the default. The reasonable default for 2.6 is ALSA, even if it doesn't work for everyone. People like yourself who have no luck with ALSA can still apt-get install oss. > > 2. The diversion approach > > > > * ALSA modules are blacklisted by default > > * alsa-base de-blacklists ALSA modules and blacklists OSS modules > > * linux26 installs alsa-base > > Why should linux26 install alsa-base? That would mean OSS will always > be blacklisted. OSS will no longer be blacklisted if alsa-base is purged. On this scheme, if alsa-base is _not_ installed then it is the ALSA modules that are blacklisted. > It would be beter if the D-I arch-detect looks at the soundcard of the > system and then recommends either OSS or ALSA as default depending on it. That would be nice, but I take it that it is too late now to make such big changes to the installer before sarge. For all I know it may even be too late to add alsa-base to the list of packages to install in linux26 mode. -- Thomas -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
Re: automake/autoconf in build-dependencies
On Fri, 11 Mar 2005, Paul Hampson wrote: > * timestamp skew means that the autobuilt makefiles will try > to rebuild configure from configure.in even if configure is patched by > dpkg-source at the same time as configure.in > * A solution for this is in the above-mentioned README.Debian New dpkg-source support will work too. -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
Re: xend is stopped before xendomains in debs
This one time, at band camp, Adam Heath said: > On Thu, 10 Mar 2005, Miquel van Smoorenburg wrote: > > > On Wed, 9 Mar 2005, Adam Heath wrote: > > >On Wed, 9 Mar 2005, Adam Heath wrote: > > >>On Wed, 9 Mar 2005, Henning Glawe wrote: > > >>> > > >>> S20xend > > >>> S20xendomains > > >>> K20xend > > >>> K20xendomains > > >>> > > >>> so xend is shutdown before the xen-domains are shutdown, which of cause > > >>> fails > > >>> when there's no xend... > > > > > >>This is a bug in run-parts. It should reverse the order. > > >> > > I don't understand. What is the bug? The order sysv-rc uses to > > run the scripts is the standard order used by POSIX when you > > do a "for i in S??*". That is well known. If that isn't what > > you'd like it to be, fix the priority of the Sxx symlinks. > > Hrm. Maybe this is a problem with update-rc.d. But I don't know. > > update-rc.d defaults bar creates rc2.d/S20bar and rc6.d/K20bar, and > update-rc.d defaults foo creates rc2.d/S20foo and rc6.d/K20foo. During > start, bar is started before foo, which is what is expected. However, during > shutdown, bar is stopped *before* foo, instead of the other way around. > > Yes, one can change the priority of one of the scripts. But that is a lot > more overhead. > > I'm cc'ing devel, as this could be a more general problem, worthy of a broader > fix. It really is not that much more overhead to specify stop order in your scripts to avoid this problem. It looks to me like a packaging bug, is all. Take care, -- - | ,''`.Stephen Gran | | : :' :[EMAIL PROTECTED] | | `. `'Debian user, admin, and developer | |`- http://www.debian.org | - pgpqsTm436xm9.pgp Description: PGP signature
Re: NPTL and static linking
[EMAIL PROTECTED] said: > -Wl,-static ... -Wl,-dy are equivalent and shorter :-) Not for me, even though the ld manual claims they're the same. I have no idea why. But the reason I went looking for a more elaborate solution was the above not working in the first place. Jason -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
Re: Serious kernel problems on new i386 hardware
On Thursday, 10 de March de 2005 15:10, Andreas Tille wrote: > I tried to upgrade to a 2.6.x kernel but failed always with kernel_panic. > I tried 2.6.8, 2.6.8 and 2.6.10 (here -1-386 and -1-686 versions) and > all failed with the same result: > > ERROR: Removing 'trm290': Device or resource busy > ERROR: Removing 'vis82cxxx': Device or resource busy > pivot_root: No such file or directory > /sbin/init: 432: cannot open dev/console: No such file > Kernel panic - not syncing: Attempt to kill init! I've recently had those problems also on a Dell server, using SATA too. The fine guys from #gpul helped me a lot on this. Basically, what happened to me is that kernel 2.4 mapped the SATA drive as /dev/hdc and kernel 2.6 mapped it to /dev/sda So I booted using the installer with the linux26 option, followed the installation until the HD partitioning screen, jotted down the hard disk device (/dev/sda), switched to console 2 and mounted the partition. Then I changed /etc/fstab and /boot/grub/menu.lst acordingly. Everything worked fine when I rebooted. That's what I did on the same symptoms and worked for me. -- temp: http://temp.roncero.org Out: 17.69 ºC -- In: 19.38 ºC -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
Bug#298941: ITP: ext3rminator -- recover deleted files from an ext3 filesystem
Package: wnpp Severity: wishlist Owner: Mike Hommey <[EMAIL PROTECTED]> * Package name: ext3rminator Version : 0.3.0 Upstream Author : Mike Hommey <[EMAIL PROTECTED]> * URL : http://glandium.org/debian/repository/experimental/ * License : GPL Description : recover deleted files from an ext3 filesystem Ext3rminator is a last chance program when you just unthoughtfully deleted several megabytes of data on an ext3 (or ext2) partition. It goes through all free blocks in the filesystem to look for what can look like data. . It is only able to recover files where the 48 first KB (actually, 12 blocks, a block usually being 4096 bytes) are contiguous. -- System Information: Debian Release: 3.1 APT prefers unstable APT policy: (500, 'unstable') Architecture: i386 (i686) Kernel: Linux 2.6.10-1-686 Locale: LANG=ja_JP.UTF-8, LC_CTYPE=ja_JP.UTF-8 (charmap=UTF-8) -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
is xprint still used by mozilla, etc?
Back history: I added xprt-xprintorg to the desktop task at the end of January after receiving bug #226605 which stated that More and more applications like Firebird, Thunderbird, Mozilla, Java, Openoffice and more need it so the default Debian desktop and print server installations should provide it. Also near the end of January, a new debconf question was added to xprint-common, about printer DPI, for bug #280159. The result is that we now have an additional debconf question added to default high-priority desktop installs of Debian. Unfortunatly this question is both quite long, as well as not being translated to many languages due to only being added to the default install path recently. It is also yet another question in the default desktop install path, which we have carefully tried to limit to only the questions one really needs to answer. And it doesn't even make much sense if you don't have a prointer. Oh yeah, it probably means people doing preseeded automatic installs will need to add yet another question to their preseeding; which means the installation manual is out of date, and will need to be translated, etc. Anyway, besides illistrating why new debconf questions can be pretty painful to the installation team, I mostly wanted to ask: Is xprintorg still needed to print from mozilla, openoffice, firefox, etc, or has that been cleared up since january? Should I remove xprt-xprintorg from the desktop task again? I don't have a printer, so I find it hard to keep up with this kind of thing. IIRC the last install I did on a system with a printer, 2 weeks ago, worked without xprint, but I could be mistaken. -- see shy jo signature.asc Description: Digital signature
Re: is xprint still used by mozilla, etc?
On Thu, 10 Mar 2005, Joey Hess wrote: > painful to the installation team, I mostly wanted to ask: Is xprintorg > still needed to print from mozilla, openoffice, firefox, etc, or has > that been cleared up since january? Should I remove xprt-xprintorg from > the desktop task again? It is not absolutely needed for most people. It is absolutely needed for a small set of people (some charsets don't work without it, I seem recall. But unfortunatelyy I cannot recall which). It is *always* a good idea to use it if you can get it to work (and with CUPS, setting the DPI correctly is usually all it takes). I would leave it on the task, and instead get people to actually translate that message ASAP. -- "One disk to rule them all, One disk to find them. One disk to bring them all and in the darkness grind them. In the Land of Redmond where the shadows lie." -- The Silicon Valley Tarot Henrique Holschuh -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
Re: Shouldn't kernel-image-2.6.x-y-z depend on alsa-base ?
On Thu, 10 Mar 2005 02:50:04 +0100, Steve Langasek wrote: > Considering you're talking about solutions that require updates to > kernel-image packages *anyway*, why has no one suggested adding the > necessary blacklist entries to these packages? k-i packages aren't the right place to put the blacklists because more than one of them can be installed at once. -- Thomas Hood -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
Re: is xprint still used by mozilla, etc?
On Thu, Mar 10, 2005 at 02:45:35PM -0500, Joey Hess wrote: > Anyway, besides illistrating why new debconf questions can be pretty > painful to the installation team, I mostly wanted to ask: Is xprintorg > still needed to print from mozilla, openoffice, firefox, etc, or has > that been cleared up since january? Should I remove xprt-xprintorg from > the desktop task again? > > I don't have a printer, so I find it hard to keep up with this kind of > thing. IIRC the last install I did on a system with a printer, 2 weeks > ago, worked without xprint, but I could be mistaken. Well I have a box which I installed from d-i RC1 some time ago (when that was current) with the base system only, and then did nothing with. Two weeks ago I started using it as a desktop machine. I did approximately (with sarge in /etc/apt/sources.list) apt-get update apt-get dist-upgrade apt-get install x-window-system-core kdebase mozilla-firefox openoffice.org apt-get install cupsys-bsd cupsys-driver-gimpprint gs-esp and installed a home-compiled 2.6.11 kernel. I do not have xprt, xprt-common or xprt-xprintorg installed and can print fine from both Firefox and OOo. -- Martin Orr Linux Administrator, Methodist College Belfast -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
Re: Debian LDAP schema for Debian Packages
hi, On Thu, Mar 10, 2005 at 12:15:32PM -0300, [EMAIL PROTECTED] wrote: > I wonder if there is a debian ldap schema to > store debian packages. Better yet, > are we going to have one ever? while i am not the maintainer of the debian oid arch, i wrote an unofficial debian package schema some time back for an packages->LDAP gateway i threw together[1]. at the time there didn't seem to be much interest by other people, so i haven't worked on it in several months. sean [1] which could hypthetically allow apt-get update to only need to fetch changed package entries instead of the entire Packages.gz, among other neat features. -- signature.asc Description: Digital signature
Re: Shouldn't kernel-image-2.6.x-y-z depend on alsa-base ?
On Thu, Mar 10, 2005 at 11:57:11AM +0100, Mike Hommey wrote: > On Wed, Mar 09, 2005 at 05:46:22PM -0800, Steve Langasek <[EMAIL PROTECTED]> > wrote: > > Considering you're talking about solutions that require updates to > > kernel-image packages *anyway*, why has no one suggested adding the > > necessary blacklist entries to these packages? Far better than removing a > > bunch of modules from the kernel-image at this late stage, IMHO. > It doesn't work properly with several kernel-images installed. Why not? Why can't each kernel-image package add its own file in the /etc/hotplug/blacklist.d/ directory? Or if you mean "it doesn't work if you also have a 2.4 kernel-image installed", how is this any better or worse than if you have alsa-base blacklisting? -- Steve Langasek postmodern programmer signature.asc Description: Digital signature
Re: is xprint still used by mozilla, etc?
Around 14 o'clock on Mar 10, Joey Hess wrote: > Back history: I added xprt-xprintorg to the desktop task at the end of > January after receiving bug #226605 which stated that > > More and more applications like Firebird, Thunderbird, Mozilla, Java, > Openoffice and more need it so the > default Debian desktop and print server installations should provide it. I'm afraid Xprint is a political football; some people will say that more and more projects depends on it, and others (myself included) will say that it is decreasingly relevant. As far as I understand it, neither Mozilla nor OpenOffice are built to require Xprint in the Debian packages. Mozilla can be configured to use Xprint, and I believe it has additional capabilities not present in the bare postscript output mechanism. I believe the depends and recommends mechanism is sufficient to ensure that Xprint is available where necessary, and that we shouldn't burden the desktop task with optional software which provides no direct user-visible functionality. -keith pgpfodJlu1923.pgp Description: PGP signature
Re: Shouldn't kernel-image-2.6.x-y-z depend on alsa-base ?
On Thu, 10 Mar 2005 01:10:12 +0100, Josselin Mouette wrote: > Davide, would you agree with making gnome-media depend on something like > "alsa-base | kernel-image-2.4", to ensure sound is working properly upon > installation? I don't see why gnome-media should be involved. This problem has nothing specifically to do with GNOME. Also, the dependency you suggest would prevent people who install non-Debian 2.4 kernels from using OSS. Here is another idea. We create a new binary package "sound-system-chooser" which contains blacklists for both OSS and ALSA and provides a debconf interface that the administrator can use to disable either or both of the sound systems. Blacklists would be removed from alsa-base. k-i 2.6 and alsa-base would both Depend on sound-system-chooser. This would solve another problem with the current alsa-base, viz., that removing it isn't enough to enable OSS again -- alsa-base has to be purged in order to remove the hotplug blacklist file that it contains. sound-system-chooser could be generated from the alsa-driver source package. Anyone see anything wrong with this idea? P.S. I apologize for all my non-threading posts on this topic. My webmain interface apparently doesn't support In-Reply-To headers. -- Thomas Hood -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
Re: is xprint still used by mozilla, etc?
On Thu, 10 Mar 2005, Otavio Salvador wrote: > The problem is larger then that. Leave it on task will require update > of installation manual and update of all translations too. Then we are best served by removing it. It is suggested, anyway... -- "One disk to rule them all, One disk to find them. One disk to bring them all and in the darkness grind them. In the Land of Redmond where the shadows lie." -- The Silicon Valley Tarot Henrique Holschuh -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
Re: is xprint still used by mozilla, etc?
On Thu, Mar 10, 2005 at 02:45:35PM -0500, Joey Hess wrote: > Back history: I added xprt-xprintorg to the desktop task at the end of > January after receiving bug #226605 which stated that > > More and more applications like Firebird, Thunderbird, Mozilla, Java, > Openoffice and more need it so the > default Debian desktop and print server installations should provide it. > > Also near the end of January, a new debconf question was added to > xprint-common, about printer DPI, for bug #280159. I removed the xprint dependencies in debian-edu, cause it does not work out of the box, and it's confusing. Printing using cups works, both with mozilla (suite) and OOo. -- Finn-Arne Johansen [EMAIL PROTECTED] http://bzz.no/ -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
Re: is xprint still used by mozilla, etc?
|| On Thu, 10 Mar 2005 17:16:09 -0300 || Henrique de Moraes Holschuh <[EMAIL PROTECTED]> wrote: hdmh> On Thu, 10 Mar 2005, Joey Hess wrote: >> painful to the installation team, I mostly wanted to ask: Is xprintorg >> still needed to print from mozilla, openoffice, firefox, etc, or has >> that been cleared up since january? Should I remove xprt-xprintorg from >> the desktop task again? hdmh> It is not absolutely needed for most people. It is absolutely needed for a hdmh> small set of people (some charsets don't work without it, I seem recall. But hdmh> unfortunatelyy I cannot recall which). It is *always* a good idea to use it hdmh> if you can get it to work (and with CUPS, setting the DPI correctly is hdmh> usually all it takes). hdmh> I would leave it on the task, and instead get people to actually translate hdmh> that message ASAP. The problem is larger then that. Leave it on task will require update of installation manual and update of all translations too. -- O T A V I OS A L V A D O R - E-mail: [EMAIL PROTECTED] UIN: 5906116 GNU/Linux User: 239058 GPG ID: 49A5F855 Home Page: http://www.freedom.ind.br/otavio - "Microsoft gives you Windows ... Linux gives you the whole house." -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
Re: Is Anthony Fok MIA?
* Frank Küster <[EMAIL PROTECTED]> [2005-03-10 13:14]: > > It seems that Anthony Foka is missing in action. He does not respond to > > bugs which removes his packages from the release. > > Have you asked [EMAIL PROTECTED] I had dinner with Anthony last night. I'll follow up with more information on [EMAIL PROTECTED] -- Martin Michlmayr http://www.cyrius.com/ -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
Re: is xprint still used by mozilla, etc?
|| On Thu, 10 Mar 2005 18:13:46 -0300 || Henrique de Moraes Holschuh <[EMAIL PROTECTED]> wrote: hdmh> On Thu, 10 Mar 2005, Otavio Salvador wrote: >> The problem is larger then that. Leave it on task will require update >> of installation manual and update of all translations too. hdmh> Then we are best served by removing it. It is suggested, anyway... Not really. Like you did remember, exist some language that need it for printing and in this case i think it should be included. Like I suggested in another mail to this thread, I think the best solution is include it only in needed locales. tasksel have this feature. -- O T A V I OS A L V A D O R - E-mail: [EMAIL PROTECTED] UIN: 5906116 GNU/Linux User: 239058 GPG ID: 49A5F855 Home Page: http://www.freedom.ind.br/otavio - "Microsoft gives you Windows ... Linux gives you the whole house." -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
Re: is xprint still used by mozilla, etc?
|| On Thu, 10 Mar 2005 12:56:46 -0800 || Keith Packard <[EMAIL PROTECTED]> wrote: kp> Around 14 o'clock on Mar 10, Joey Hess wrote: >> Back history: I added xprt-xprintorg to the desktop task at the end of >> January after receiving bug #226605 which stated that >> >> More and more applications like Firebird, Thunderbird, Mozilla, Java, >> Openoffice and more need it so the >> default Debian desktop and print server installations should provide it. kp> I'm afraid Xprint is a political football; some people will say that more kp> and more projects depends on it, and others (myself included) will say kp> that it is decreasingly relevant. kp> As far as I understand it, neither Mozilla nor OpenOffice are built to kp> require Xprint in the Debian packages. Mozilla can be configured to use kp> Xprint, and I believe it has additional capabilities not present in the kp> bare postscript output mechanism. kp> I believe the depends and recommends mechanism is sufficient to ensure that kp> Xprint is available where necessary, and that we shouldn't burden the kp> desktop task with optional software which provides no direct user-visible kp> functionality. If it doesn't give a lot of extra functionaly for all users it can be leave included only on needed languages. We can add another task depending on desktop and then it'll only be installed if desktop task is selected for install. -- O T A V I OS A L V A D O R - E-mail: [EMAIL PROTECTED] UIN: 5906116 GNU/Linux User: 239058 GPG ID: 49A5F855 Home Page: http://www.freedom.ind.br/otavio - "Microsoft gives you Windows ... Linux gives you the whole house." -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
Bug#298973: ITP: libtorrent -- a BitTorrent library written in C++
Package: wnpp Severity: wishlist Owner: Qingning Huo <[EMAIL PROTECTED]> * Package name: libtorrent Version : 0.5.1 Upstream Author : Jari Sundel <[EMAIL PROTECTED]> * URL : http://libtorrent.rakshasa.no/ * License : GPL Description : a BitTorrent library written in C++ (Include the long description here.) LibTorrent is a BitTorrent library written in C++ for *nix. It is designed to avoid redundant copying and storing of data that other clients and libraries suffer from. Licensed under the GPL. Library Features: * The client has full control over the polling of sockets. * Sigc++ signals makes i easy for the client to react to events. * Fast resume which checks the file modification time. * Direct reading and writing from network to mmap'ed files: o Avoids duplication of data where both the application and the kernel has a copy of the file chunk. o Unused chunks get thrown out or written to disk instead of the swap. o Kernel handles caching of the file. * File hash check: o Uses the same thread. o Client can control the rate. (Will be improved) o Only one torrent at a time is checked. o Non-blocking and preload to cache with the mincore and madvise system calls. * Different download priorities for files in the torrent. * Support for files larger than 2 GB. * No dependency on any specific HTTP library, the client implements a wrapper class. * Dynamic request pipe size. -- System Information: Debian Release: 3.1 APT prefers unstable APT policy: (500, 'unstable') Architecture: i386 (i686) Kernel: Linux 2.6.9-1-686 Locale: LANG=C, LC_CTYPE=C (charmap=ANSI_X3.4-1968) -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
Bug#298976: ITP: rtorrent -- ncurses BitTorrent client based on LibTorrent
Package: wnpp Severity: wishlist Owner: Qingning Huo <[EMAIL PROTECTED]> * Package name: rtorrent Version : 0.1.2 Upstream Author : Jari Sundell <[EMAIL PROTECTED]> * URL : http://libtorrent.rakshasa.no/ * License : GPL Description : ncurses BitTorrent client based on LibTorrent (Include the long description here.) rtorrent is a BitTorrent client written in C++ for *nix based on LibTorrent. It uses ncurses and is therefor ideal to use with screen. It has the following features: * Use an URL or file path to add torrents at runtime * Stop/delete/resume torrents * Optionally loads/saves/deletes torrents automatically in a session directory * Safe fast resume support * Shows lots of information about peers and the torrent -- System Information: Debian Release: 3.1 APT prefers unstable APT policy: (500, 'unstable') Architecture: i386 (i686) Kernel: Linux 2.6.9-1-686 Locale: LANG=C, LC_CTYPE=C (charmap=ANSI_X3.4-1968) -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
jad package orphaned
Hello, I contacted Takashi Okamoto, the official maintainer of the jad package ( http://packages.debian.org/stable/devel/jad ). He can no longer maintain it and has asked me to adopt it. However, I am not yet an official maintainer, so I suggest that this package be orphaned. The link from the package page to the upstream author's homepage is broken; I would like to see it updated by whoever adopts it. There's a closed bug about this in the package bug archive, but the old link is still there. Regards, Jared -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
Re: jad package orphaned
On Thu, Mar 10, 2005 at 11:37:52PM +0100, Jared Boone wrote: > Hello, > > I contacted Takashi Okamoto, the official maintainer of the jad > package ( http://packages.debian.org/stable/devel/jad ). He can no > longer maintain it and has asked me to adopt it. However, I am not yet > an official maintainer, so I suggest that this package be orphaned. > > The link from the package page to the upstream author's homepage is > broken; I would like to see it updated by whoever adopts it. There's a > closed bug about this in the package bug archive, but the old link is > still there. jad is removed from unstable and testing, it's no longer in the archive. If you want to see it re-included, you'll need to file a 'RFP' about it, please see http://www.debian.org/devel/wnpp The reason for removal is: RoQA; non-free with free alternatives See @214201 --Jeroen -- Jeroen van Wolffelaar [EMAIL PROTECTED] (also for Jabber & MSN; ICQ: 33944357) http://Jeroen.A-Eskwadraat.nl -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
Re: Switchconf: Orphaning or removing?
On Thu, Mar 10, 2005 at 12:09:05PM +, Henning Makholm wrote: > Scripsit Thomas Hood <[EMAIL PROTECTED]> > > > laptop-net also contains a configuration file switching mechanism. > > For that matter, so does ifupdown. I have a bunch of post-up 'ln -fs' > commands in the appropiate /etc/network/interfaces on my laptop. > Does switchconf do more than can be simulated easily by that? I use switchconf to change more files, like the sources.list, XF86Config-4, gpm.conf. The last two are choosen by looking into PCI bus to detect what is the hardware the system is running. For example, if the vga display is a Matrox, I know the machine have a wheel PS/2 mouse and the monitor is capable of [EMAIL PROTECTED] If the display is a NVIDIA I know the mouse is a wheel USB and the display is a LCD capable of [EMAIL PROTECTED] So the switchconf change the XF86Config and the gpm.conf to match the hardware. Jose Calhariz -- Nao ha nada como o sonho para criar o futuro. Utopia hoje, carne e osso amanha. -- Victor Hugo signature.asc Description: Digital signature
Why are these packages in sarge?
I noticed that kernel-patch-2.6.10-hppa and kernel-patch-2.6.10-s390 are now in Sarge. Should they be there? There is no corresponding kernel-source-2.6.10 package in Sarge to which these patches could be applied (as it is only in Sid). Just a question I had. -Roberto -- Roberto C. Sanchez http://familiasanchez.net/~sanchezr -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
Re: is xprint still used by mozilla, etc?
Otavio Salvador wrote: > Not really. Like you did remember, exist some language that need it > for printing and in this case i think it should be included. What languages (and why)? -- see shy jo signature.asc Description: Digital signature
Re: is xprint still used by mozilla, etc?
|| On Thu, 10 Mar 2005 19:37:16 -0500 || Joey Hess <[EMAIL PROTECTED]> wrote: jh> Otavio Salvador wrote: >> Not really. Like you did remember, exist some language that need it >> for printing and in this case i think it should be included. jh> What languages (and why)? Like Henrique, I don't remember which languages. I think this detail is more adequate to it's maintainer then me. I haven't found the thread about it while I was finding on mailing list archive. Then, sorry if I can't point out which languages need to use it for proper printing :( -- O T A V I OS A L V A D O R - E-mail: [EMAIL PROTECTED] UIN: 5906116 GNU/Linux User: 239058 GPG ID: 49A5F855 Home Page: http://www.freedom.ind.br/otavio - "Microsoft gives you Windows ... Linux gives you the whole house." -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
Re: is xprint still used by mozilla, etc?
Finn-Arne Johansen wrote: > I removed the xprint dependencies in debian-edu, cause it does not work > out of the box, and it's confusing. Printing using cups works, both > with mozilla (suite) and OOo. Xprint works perfectly fine out of the box. I don't remember receiving a bug report from you. Drew Parsons Xprint maintainer -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
Re: is xprint still used by mozilla, etc?
Joey Hess wrote: > > Otavio Salvador wrote: > > Not really. Like you did remember, exist some language that need it > > for printing and in this case i think it should be included. > > What languages (and why)? > Xprint provides two (related) services, currently made use of by the mozillas and others. These are improvements in printing compared to the results of the default mozilla postscript driver (identified in the mozilla printing dialog as "Postscript/*"): 1) subtle improvements over general layout on the printed page. For instance, some CSS style settings were being ignored by the default driver, but handled by Xprint. Also Xprint can handle MathML. I haven't followed this advantage carefully, mind you, so maybe the default driver has improved. 2) ability to print non-latin text (russian, thai, hebrew, etc etc etc). This is the killer app for me, the specific reason why I introduced Xprint into Debian in the first place. You can see for yourself by printing www.rol.ru or www.dailynews.co.th from a mozilla with and without Xprint. Keith said Xprint is increasingly irrelevant, but I'm not aware how this language issue can be satisfactorily solved without Xprint. The dependency on Xprint was added to the mozillas mainly because of reason 2, I believe. Takuo KITAME is, after all, Japanese. As I wrote to bug #298954, current (reverse) dependencies on Xprint are: Depends: x-window-system Recommends: mozilla-thunderbird Suggests: mozilla-firefox, mozilla-browser I'm not sure why thunderbird recommends: rather than suggests: Xprint - possibly an oversight on behalf of the thunderbird maintainer, or maybe he saw it as the best way to allow the printing of non-latin emails. Alexander can speak for himself if he truly prefers Recommends: over Suggests. The desktop task depends on x-window-system-core, not x-window-system, and therefore shouldn't be hauling in Xprint. With regards to the priority of the debconf question, as discussed in bug #298954, I'm happy to lower the priority. With regards to general desktop dependencies, it's fair enough for the non-latin locales to include their own dependency on Xprint, I think. Though I like to believe Xprint does no harm to others. Even when it is installed, the default postscript driver is still there in the mozilla print dialog, available for use. Drew p.s. The lastest upload of Xprint is stalled in the NEW queue after renaming the packages (the -xprintorg suffix is no longer required. A dummy package is supplied to handle the dependencies but I'd like to have them updated). Can I beg on my heels for the ftpmasters to push it through? Then I can deal with the priority of the debconf question. -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
Re: is xprint still used by mozilla, etc?
Drew Parsons wrote: > The desktop task depends on x-window-system-core, not x-window-system, > and therefore shouldn't be hauling in Xprint. Like I said at the head of this thread I explicitly added xprt-xprintorg to the deaktop task on user request. However, nothing I've seen so far seems to be a solid reason to keep it. OTOH, if the high priority debconf question goes away, I don't care if it's left in. -- see shy jo signature.asc Description: Digital signature
Re: is xprint still used by mozilla, etc?
Around 12 o'clock on Mar 11, Drew Parsons wrote: > Keith said Xprint is increasingly irrelevant, but I'm not aware how this > language issue can be satisfactorily solved without Xprint. Mozilla is currently integrating Pango support for complex text layout issues; using that for printing would be a logical step as it would support many more scripts than Mozilla does today, even with Xprint. But, as of today, Mozilla does rely on Xprint for non-Latin printing, and so it does indeed remain a relevant part of Debian. I am working hard to make sure the Debian desktop supports all of the world's languages in an efficient and correct fashion. I'm hoping to provide a better solution than what is provided by Xprint today, but I also acknowledge that Xprint is still useful in some environments and hence has a place on some desktops for now. It should be available, but it shouldn't be mandatory -- many of us print quite happily from dozens of applications in many languages without the benefit of Xprint on our machine; Mozilla remains an exceptional case in this regard, one which I hope changes in the future. -keith pgpYpWOrFfM65.pgp Description: PGP signature
Bug#299008: ITP: torrentflux -- a PHP based, feature-rich Torrent download manager
Package: wnpp Severity: wishlist Owner: John Kolovos <[EMAIL PROTECTED]> * Package name: torrentflux Version : 1.5 Upstream Author : Qrome (to contact use: http://www.torrentflux.com/contact.php) * URL : http://www.torrentflux.com/ * License : GPL Description : a PHP based, feature-rich Torrent download manager TorrentFlux is a feature rich Torrent manager. * Upload Torrents via URL or File Upload * Start, Stop, and Delete Torrents with a click * Advanced Torrent start options (ports, speeds, etc.) * Multi-user interface * RSS Feeds, download Torrents files with a click * View Download Progress of all torrents at a glance * View drive space at a glance * View Torrent file meta information * Built-in User management and Security * Private Messaging * Themes (selectable per user) * Upload History * Detailed User Administration * Admin Searchable Logs * Language Support I've already got an experimental package build, which will hopefully finish next week. Regards, John Kolovos -- System Information: Debian Release: 3.1 APT prefers unstable APT policy: (990, 'unstable'), (500, 'testing') Architecture: i386 (i686) Kernel: Linux 2.6.9homer Locale: LANG=en_GB, LC_CTYPE=el_GR (charmap=ISO-8859-7) -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
