Bug#866973: cyrus-imapd 3.0 needs to be (eventually) packaged
Package: cyrus-imapd cyrus-imapd 3 has been released. It has not yet been packaged for Debian. It should (eventually) be. Release notes: - 3.0.0: contains description of major changes since 2.5: https://www.cyrusimap.org/imap/download/release-notes/3.0/x/3.0.0.html - 3.0.1: https://www.cyrusimap.org/imap/download/release-notes/3.0/x/3.0.1.html - 3.0.2: https://www.cyrusimap.org/imap/download/release-notes/3.0/x/3.0.2.html
Bug#641193: /usr/lib/grub/grub-mkconfig_lib: considers 2.6.32-bpo.5 newer than 2.6.32-5; affects grub menu order and default kernel
Package: grub-common Version: 1.98+20100804-14 Severity: normal File: /usr/lib/grub/grub-mkconfig_lib I used lenny with kernel from squeeze through backports. Then I upgraded to squeeze. It was strange to me that after reboot, the machine still booted the kernel from backports and not the one from squeeze. The versions of linux-image packages: $ dpkg -l | grep linux-image | grep 2.6.32 | awk ii linux-image-2.6-amd64 2.6.32+29 ii linux-image-2.6.32-5-amd642.6.32-35squeeze1 ii linux-image-2.6.32-bpo.5-amd642.6.32-31~bpo50+1 I traced it to line 185 in grub-mkconfig_lib file, where /boot/vmlinux-* filenames are compared using dpkg --compare-versions. If however the regular expression on line 173 of the same file gets bpo alongside pre, rc, git etc., it seems to resolve the issue (but I did not test it extensively to make sure it does not introduce new issues, nor have I any intimate knowledge of the bpo package naming scheme). From brief inspection of the grub-mkconfig_lib file, it seems that the same buggy logic is present in the unstable version of the package as well (the line numbers there are 218 and 206). So this is probably a bug in the debian/patches/dpkg_version_comparison.patch source package file. -- System Information: Debian Release: 6.0.2 APT prefers stable-updates APT policy: (500, 'stable-updates'), (500, 'stable') Architecture: amd64 (x86_64) Kernel: Linux 2.6.32-bpo.5-amd64 (SMP w/4 CPU cores) Locale: LANG=C, LC_CTYPE=C (charmap=UTF-8) (ignored: LC_ALL set to en_US.UTF-8) Shell: /bin/sh linked to /bin/bash Versions of packages grub-common depends on: ii base-files6.0squeeze2Debian base system miscellaneous f ii dpkg 1.15.8.11 Debian package management system ii gettext-base 0.18.1.1-3 GNU Internationalization utilities ii install-info 4.13a.dfsg.1-6 Manage installed documentation in ii libc6 2.11.2-10 Embedded GNU C Library: Shared lib ii libdevmapper1.02.12:1.02.48-5The Linux Kernel Device Mapper use ii libfreetype6 2.4.2-2.1+squeeze1 FreeType 2 font engine, shared lib ii zlib1g1:1.2.3.4.dfsg-3 compression library - runtime Versions of packages grub-common recommends: ii os-prober 1.42 utility to detect other OSes on a Versions of packages grub-common suggests: pn grub-emu none (no description available) pn multiboot-doc none (no description available) pn xorriso none (no description available) -- no debconf information -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#636283: speech-dispatcher: Pico doesn't work anymore
I forwarded the issue to upstream's bug tracker with some detailed way to reproduce it. You can follow further progress there - just register at its.freebsoft.org and subscribe notifications for the specific issue (https://its.freebsoft.org/its/issues/7500), or alternatively for the whole Speech Dispatcher project if you are interested in other Speech Dispatcher bug reports as well (https://its.freebsoft.org/its/projects/1876). Or you can just view the issue at that address without registering, but you won't get notifications on new comments and won't be able to add your comments. Anyway, when there is a conclusion available in upstream's bugtracker, I will update this bug with it and act accordingly. -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#625235: speech-dispatcher: Combined with pulseaudio breaks ALSA
Hello Bruno, thanks for the information. Also please tell me if you use pulseaudio or ALSA now as your main sound system in KDE (or other DE you are currently using). Anyway you can set RUN=no in /etc/default/speech-dispatcher to prevent speech-dispatcher from starting automatically on system boot. I will make this change automatically in next version speech-dispatcher package when I am confident it is the right way to fix. -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#636283: speech-dispatcher: Pico doesn't work anymore
Hello Jean, thanks for the bug report. I reproduced the problem with both pico-generic and espeak-generic. So it looks like rather a bug in the generic module itself not specific to pico. Since it's reproducible on my side, I will try to see and debug what the problem is. This could take some time (rather weeks than days), so please be patient. For the record, the settings I reproduced it with: * audio output is alsa * pico-generic and espeak-generic are uncommented in /etc/speech-dispatcher/speechd.conf * optional: default speech module is pico-generic or espeak-generic, for convenience to not specify it with each spd-say run * speech-dispatcher starts in system-wide mode (RUN=yes in /etc/default/speech-dispatcher) * I use spd-say like this: SPEECHD_SOCKET=/var/run/speech-dispatcher/speechd.sock spd-say -o pico-generic hello; the -o pico-generic can be changed espeak-generic, and/or omitted if default speech module is set appropriately in configuration I am not saying it is not reproducible with other settings, just that these are the settings I used. I tried debugging with gdb, it seems the generic module exits gracefully on its own will, it does not crash. Also I noticed your output module is named espeak-pico-generic, but the official Debian package has this as just pico-generic. You should be using the official pico-generic module for reporting bugs in the future, or updating this bug report - even though I reproduced the problem fine with the original pico-generic, it's better we use consistent modules. W.r.t. upgrade to git, the right thing now is to try debugging the generic module to see where the problem is and then fix it, instead of just upgrading to git. Below are my thoughts about packaging current upstream git in Debian: First if there will be upstream's git packaged for Debian, I would definitely put it into experimental, not unstable, especially for the reason that I have no experience about how stable and usable the current git is, and also have no way to tell whether there will be any developments in the git version, which would be good for providing subsequent updated versions of the package in the future. I have no information about upcoming upstream release, the better place to ask would be the speech-dispatcher mailing list. Note that if this was about packaging an upstream beta into experimental or even unstable, it would be much more OK for me to package it. Also providing libao is not a valid reason, since libao output is already enabled in unstable (0.7.1-4) and testing (0.7.1-6). If you feel adventurous and really want to try out speech-dispatcher from git, there is current speech-dispatcher git packaged (including native pico module) for Ubuntu using automated daily build system - it's in the ppa:dusek/spd-daily PPA. So you might try installing that directly with dpkg or somehow with apt (I haven't tried), hopefully the Ubuntu package will be usable in Debian. You also need to install libdotconf1.0 from that repository first. Please let me (and/or the debian-accessibility list) know about your results if you try it. But in general, the preferred approach by me to handling bugs is to fix problem in current release than upgrading to git. If you want to discuss upgrade to git further, please open a new bug, it really would confuse communication in this bug which is really about the specific problem of generic module not working, and there might be other reasons, apart from native pico module, that you or others might mention why upgrading to git is a good thing. You can always mention that other bug number in this bug. 2.8.2011 v 0:48, Jean-Philippe MENGUAL: Package: speech-dispatcher Version: 0.7.1-6 Severity: normal Hi, I tried upgrading spd package, but it's really too complex. However, as you can see on this thread: http://lists.debian.org/debian-accessibility/2011/07/msg00126.html it seems there're 2 reasons to try packaging the current git release. 1st, Pico now doesn't work since the last update (see the thread). Then, it seems that we could ship libao as suggested in another thread of the list. Finally, it'd allow to test the last modules for pico and ibmtts viavoice. The most important bug is that pico absolutely doesn't work now. It seems the espeak-pico-generic doesn't suit, it should be replaced by the current module in the dev release. So could you upgrade the package please? Optionally in experimental repo? To upgrade to the current git release? Otherwise, do you know if a release will come soon? Thanks for your answer. -- System Information: Debian Release: wheezy/sid APT prefers unstable APT policy: (500, 'unstable'), (1, 'experimental') Architecture: i386 (i686) Kernel: Linux 3.0.0-1-686-pae (SMP w/1 CPU core) Locale: LANG=fr_FR.UTF-8, LC_CTYPE=fr_FR.UTF-8 (charmap=UTF-8) Shell: /bin/sh linked to /bin/dash Versions of packages speech-dispatcher depends on: ii
Bug#636283: speech-dispatcher: Pico doesn't work anymore
Correction: instead of SPEECHD_SOCKET=..., it should be: SPEECHD_ADDRESS=unix_socket:/var/run/speech-dispatcher/speechd.sock spd-say... -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#631350: speech-dispatcher: Speech Dispatcher overriding Intel HD internal sound
There is no need to reinstall speech-dispatcher, because: a. you uninstalled it with --purge, then you no longer have its configuration file and would install the default configuration file, whose contents I already well know b. you did uninstalled it without --purge, then it left the conffiles I am asking you for, and you can send the information I inquired without installing the respective package In any case, knowing your /etc/default/pulseaudio would be helpful, and if you still have the /etc/speech-dispatcher/speechd.conf, then the grep output I asked too. Anyway while the problem looks like in pulseaudio since it should be able to run fine with 2 instances under different users, the speech-dispatcher.postinst script should not have modified /etc/default/speech-dispatcher to be RUN=yes on upgrade from 0.6* (it should have been 0.7). Unfortunately no way to fix that now in the package for those who upgraded from 0.6. New installs of speech-dispatcher should be fine, though. If you did not use --purge when uninstalling speech-dispatcher, just edit /etc/default/speech-dispatcher and change RUN=yes to RUN=no, speech-dispatcher 0.7 should not run as a system-wide service. 10.8.2011 v 0:56, Marc J. Driftmeyer: I'll have to reinstall it. After uninstalling it PulseAudio and ALSA work seemlessly within both KDE 4.6.5 and GNOME 3.0.2. What is the boot order of loaded services/daemons and perhaps that is the problem? - Marc On 08/08/2011 12:51 PM, Boris Dušek wrote: Hello, sorry for not getting to you earlier. Could you please: 1. post your /etc/default/pulseaudio 2. post output of: grep AudioOutputMethod /etc/speech-dispatcher/speechd.conf Also, would you remember whether you had this problem also with previous 0.7* versions of the package? Finally, the bugreport information says that you have modified the conffile /etc/default/speech-dispatcher. Do you remember modifying it? (A theory I have is that a package installation script modified it without you doing it). -- Marc J. Driftmeyer Email :: m...@reanimality.com Web :: http://www.reanimality.com Cell :: (509) 435-5212 mjd.vcf Boris Dušek BRAILCOM, o.p.s.
Bug#626351: speech-dispatcher-festival: speech-dispatcher 0.7.1-6 locks pulseaudio (only dummy output appears as sound device)
Hello, sorry for not getting to you earlier. Could you please: 1. post your /etc/default/pulseaudio 2. post your /etc/default/speech-dispatcher 3. post output of: grep AudioOutputMethod /etc/speech-dispatcher/speechd.conf Thanks. -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#626351: (no subject)
Thanks. Also would you remember whether the problem started with exactly 0.7.1-6? I.e. in previous 0.7* versions (e.g. 0.7.1-5 or 0.7-6.1 etc.), was everything was fine or was the problem present as well? -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#625235: speech-dispatcher: Combined with pulseaudio breaks ALSA
Hello, sorry for not getting to you earlier. Do you remember the problem happening with previous 0.7* versions of speech-dispatcher, or is it specific to exactly 0.7.1-6 (and not 0.7.1-5 or 0.7-6.1 etc.)? -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#625235: (no subject)
Markus, could you please: 1. post your /etc/default/pulseaudio 2. post your /etc/default/speech-dispatcher 3. post output of: grep AudioOutputMethod /etc/speech-dispatcher/speechd.conf Also, could you answer the same question I sent to Jan, i.e.: Do you remember the problem happening with previous 0.7* versions of speech-dispatcher, or is it specific to exactly 0.7.1-6 (and not 0.7.1-5 or 0.7-6.1 etc.)?
Bug#631350: speech-dispatcher: Speech Dispatcher overriding Intel HD internal sound
Hello, sorry for not getting to you earlier. Could you please: 1. post your /etc/default/pulseaudio 2. post output of: grep AudioOutputMethod /etc/speech-dispatcher/speechd.conf Also, would you remember whether you had this problem also with previous 0.7* versions of the package? Finally, the bugreport information says that you have modified the conffile /etc/default/speech-dispatcher. Do you remember modifying it? (A theory I have is that a package installation script modified it without you doing it). -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
