> "BX" == Benda Xu writes:
BX> I think you might be occupied and need help to get this package
BX> in shape. Shall we put it into group maintenance of the common
BX> lisp team? I tracked my efforts to bump it by creating a new
BX> repository under the common lisp team at
Package: wnpp
Severity: normal
I haven't used (and maintained) the package for very long time, so I'm
orphaning it.
Package: wnpp
Severity: normal
The only purpose of packaging cpopen was to provided it as a required
dependency for Vdsm packaging. Since Vdsm packaging has been abandoned,
there is no sense to provide cpopen in Debian any longer. So I'm
orphaning the package and it can safely disappear.
Package: wnpp
Severity: normal
The only purpose of packaging sanlock was to provide it as a required
dependency for Vdsm packaging. Since Vdsm packaging has been abandoned,
I'm orphaning the package. If you use it for some purpose, please
consider adopting and fixing it.
Package: wnpp
Severity: normal
The only purpose of packaging safelease was to provided it as a required
dependency for Vdsm packaging. Since Vdsm packaging has been abandoned,
there is no sense to provide safelease in Debian any longer. So I'm
orphaning the package and it can safely disappear.
Package: wnpp
Severity: normal
The only purpose of packaging pthreading was to provided it as a required
dependency for Vdsm packaging. Since Vdsm packaging has been abandoned,
there is no sense to provide pthreading in Debian any longer. So I'm
orphaning the package and it can safely
Package: wnpp
Severity: normal
The only purpose of packaging ioprocess was to provided it as a required
dependency for Vdsm packaging. Since Vdsm packaging has been abandoned,
there is no sense to provide ioprocess in Debian any longer. So I'm
orphaning the package and it can safely disappear.
Thank you for the report and the patch. I applied the patch and
uploaded the updated package. I'm going to review the bug further
later, together with updating the package to a new upstream version and
other changes.
Regards,
Milan
Package: ovirt-guest-agent
Version: 1.0.13.dfsg-2
Severity: wishlist
ovirt-guest-agent 1.0.12.2.dfsg-2 doesn't work with oVirt 4.2 due to
changed paths. It would be nice to make a backport of the new package
version for stretch so that users of stable don't have to install the
package from
Package: ovirt-guest-agent
Version: 1.0.13.dfsg-2
ovirt-guest-agent 1.0.12.2.dfsg-2 doesn't work with oVirt 4.2 due to
changed paths. But when one upgrades to 1.0.13.dfsg-2, the agent still
doesn't start and it's necessary to reboot the system or to trigger the
necessary changes manually:
Anton Gladky writes:
> If you are agree with this upload, I can reschedule it to day/0 and
> let it be built right now.
Yes, I agree.
Thanks,
Milan
Anton Gladky writes:
> I have prepared an NMU (versioned as 3.3.0-2.1) and
> uploaded to DELAYED/5.
Thank you very much for the NMU!
Regards,
Milan
I wonder why such a serious bug hasn't been fixed yet. I had to
reinstall a Debian machine unexpectedly and being confronted with this
bug in the rush was no pleasant experience. I wasted a significant
amount of time finding out what was the hidden thing rendering my newly
installed system into
> "CL" == Chris Lamb writes:
CL> There hasn't seem to be any update on this bug in 37 days, in
CL> which time the Reproducible Builds effort has come on a long
CL> way. :)
CL> Would you consider applying this patch and uploading?
I'm sorry, I missed the
> "SJ" == Sven Joachim writes:
SJ> I haven't looked at the stockfish source, but I can imagine that
SJ> this is not going to improve the situation on 32-bit arches. If
SJ> the config machinery cannot find out the pointer size by itself,
SJ> dpkg-architecture
Thanks for the report. I changed the default build architecture to
general-64, I guess that's a good default these days. Let's see what
happens (I'm afraid this package will require a bit more experiments
before it builds on all architectures, sorry about that).
Regards,
Milan
--
"László Böszörményi (GCS)" writes:
> Please use the following: dget -x
> http://www.barcikacomp.hu/gcs/ovirt-guest-agent_1.0.10.2.dfsg-2+deb8u1.dsc
Thank you. I checked it and:
- It works for me with sysvinit.
- With systemd, there is the same permission problem as in
László Böszörményi (GCS) writes:
> [1] dget -x
> http://http.debian.net/debian/pool/main/o/ovirt-guest-agent/ovirt-guest-agent_1.0.10.2.dfsg-2.dsc
Is the URL correct? This is the package from February 2015, isn't it?
Could this bug be fixed please? For me, simply adding
chown ovirtagent:ovirtagent /var/log/ovirt-guest-agent
to postinst makes ovirt-guest-agent working fine.
The sanlock package is unmaintained, it hasn't been updated for 3 years.
I tried to contact its maintainer (not a DD) twice during the last
months without any response.
So unless anybody objects, I'm going to take over the package.
The sanlock package is unmaintained, it hasn't been updated for 3 years.
I tried to contact its maintainer (not a DD) twice during the last
months without any response.
So unless anybody objects, I'm going to take over the package.
Package: ftp.debian.org
Severity: normal
`Section' field in `mom' package was mistakenly set to `python'. Please
change it to `admin' as the package is primarily a memory managing
daemon and not a Python library (the section has already been fixed in
the package).
Package: wnpp
Owner: Milan Zamazal <mzama...@redhat.com>
Severity: wishlist
* Package name: safelease
Version : 1.0
Upstream Author :
* URL or Web page : https://github.com/oVirt/safelease
* License : GPL2+
Description : Legacy locking utility for Vdsm
Saf
Package: ovirt-guest-agent
Version: 1.0.11.2.dfsg-1
Severity: important
When systemd is used, ovirt-guest-agent still doesn't start. The
problem is that /var/log/ovirt-guest-agent owner is set to root:root, so
the daemon can't write to the directory and fails. (The directory
ownership is fixed
Is this bug still present with slime 2.15-1 in current unstable?
It doesn't look like a SLIME bug, but let's check.
Package: wnpp
Owner: Milan Zamazal <mzama...@redhat.com>
Severity: wishlist
* Package name: mom
Version : 0.5.1
Upstream Author :
* URL or Web page : https://github.com/oVirt/mom
* License : GPL2
Description : Dynamically manage system resources on virtuali
Package: wnpp
Owner: Milan Zamazal <mzama...@redhat.com>
Severity: wishlist
* Package name: VDSM
Version : 4.17.14
Upstream Author :
* URL or Web page : http://www.ovirt.org/Vdsm
* License : GPL2
Description : Virtual Desktop Server Manager
The VDSM s
Package: wnpp
Owner: Milan Zamazal <mzama...@redhat.com>
Severity: wishlist
* Package name: ioprocess
Version : 0.15.1
Upstream Author : Saggi Mizrahi <smizr...@redhat.com>
* URL or Web page : https://github.com/oVirt/ioprocess
* License : GPL2
Description
Package: keynav
Version: 0.20110708.0-2
Severity: normal
When I try to use Hyper key modifier in keynavrc, it doesn't work.
For example, the following line
Hyper_L+i start
doesn't make Hyper_L+i key combination working as the start key.
It seems keynav.c uses Super key instead of Hyper key.
MV == Martin Vlk mar...@vlkk.cz writes:
MV I tried installing slime again and curiously, it doesn't install
MV that file (/etc/emacs/site-start.d/50slime.el) at all.
It looks like something strange happens on your computer. The file is
present in the package (you can check it with
MV == Martin Vlk mar...@vlkk.cz writes:
MV Hi, when the slime package is uninstalled and purged, it leaves
MV behind the /etc/emacs/site-start.d/50slime.el config file.
I can't reproduce the bug -- whatever I do the file disappears after
purge. On both wheezy and current sid.
Can you
I experienced the same problem on my desktop computer, apparently after
I had installed pm-utils (but I'm not sure). I had to do two things to
remedy it:
1. To set ANACRON_RUN_ON_BATTERY_POWER=yes in /etc/default/anacron.
2. To put
service anacron stop
service anacron start
to
Thanks for help, I could reproduce the bug again and it fixes it.
Since this bug makes slime package unusable for some users, I'll raise
its priority and request to unblock it for testing. Please test the new
version (2.10-3).
--
To UNSUBSCRIBE, email to
I could see the bug too and it was reproducible but after some
experiments it suddenly disappeared for reasons unknown to me and it
hasn't appeared again since then. Apparently it has something to do
with the load ordering of contrib modules, maybe in
slime--setup-contribs in slime.el. I might
EL == Emilio Lopes ec...@gmx.net writes:
EL In my case I have the following in my ~/.emacs:
EL (setq-default frame-title-format (list Emacs Macht Alle
EL Computer Sch\366n))
EL Eval this in an Emacs buffer an watch stumpwm crash:
EL *** - CONVERT-STRING-FROM-BYTES:
EL == Emilio Lopes ec...@gmx.net writes:
EL after installing `stumpwm' I could not start the window manager. There
EL was some error message mentioning `asdf', which was *not* installed.
EL Note that `cl-asdf' is not `required' by `stumpwm', just `recommended'.
EL After
It looks like a CLISP bug to me, so I've reassigned it to clisp.
FWIW, it doesn't crash on my system when built using cowbuilder.
--
To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org
with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
I review old bug reports on stumpwm Debian package. Is this bug still
present?
--
To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org
with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
There are actually three bug reports here:
- I confirm that non-ASCII input doesn't work in the Stumpwm prompt.
- I can't reproduce the problem with set-font, it should work.
- I'm afraid the occasional crashes, especially when working with
LibreOffice are still present in 0.9.8.
--
To
Stumpwm indeed runs with SBCL. Did you read
/usr/share/doc/stumpwm/README.Debian and set LISP variable
appropriately?
--
To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org
with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
I review Debian bug reports on stumpwm. Is this bug still present?
--
To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org
with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
I run Stumpwm with cl-clx-sbcl without problems. Does the problem still
exist with stumpwm 0.9.8?
--
To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org
with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
While there are some problems with Stumpwm and LibreOffice, the current
version doesn't crash on lowriter startup on my system. Is that problem
still present with stupmwm 0.9.8 on your system?
--
To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org
with a subject of unsubscribe.
PG == Paul Gevers elb...@debian.org writes:
PG I fully understand the latter rationale, but I thought you meant
PG (by some Indian languages do that) that it was already
PG possible. What are they than doing if not fixing festival
PG itself?
I guess they do that because those
PG == Paul Gevers elb...@debian.org writes:
PG As a side note, I think that czech can not be expressed in
PG ISO-8859-15, but I don't think festival is limited to -15, but
PG supports the other ISO-8859 character sets as well.
Basically, Festival doesn't support any encoding and it
PG == Paul Gevers elb...@debian.org writes:
PG On 20-05-14 17:01, Milan Zamazal wrote:
In theory, it's possible to implement the support for a given
language in UTF-8 (some Indian languages do that), but it's
cumbersome as all the UTF handling must be done manually, without
TB == Thorsten Bonow thorsten.bo...@withouthat.org writes:
TB updating to the newest version of the slime package failed with
TB the messages attached below. Downgrading to
TB cl-swank_20130626-1_all.deb and slime_20130626-1_all.deb worked.
TB One more thing: I'm using
Package: wnpp
Severity: normal
On behalf of Boris Dušek, the current sponsored maintainer, I claim
speech-dispatcher officially orphaned. speech-dispatcher is an
important accessibility package and someone should really take it and
maintain it properly.
--
To UNSUBSCRIBE, email to
Package: wnpp
Severity: normal
Although sound-icons is trivial to maintain, I fail to do it properly,
so I orphan the package. It's useful for Speech Dispatcher / Debian
accessibility so it would be nice if someone could take it.
--
To UNSUBSCRIBE, email to
Package: wnpp
Severity: normal
I'm no longer going to maintain the package. It's necessary to make
Speech Dispatcher work with Festival so it's important for Debian
accessibility. Someone should take the package, it's easy to maintain
and I can provide limited upstream support.
--
To
Package: wnpp
Severity: normal
I'm no longer interested in maintaining the package, so I'm looking for
a new maintainer. The package is trivial to maintain.
--
To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org
with a subject of unsubscribe. Trouble? Contact
Package: wnpp
Severity: normal
On behalf of Boris Dušek, the current official sponsored maintainer of
the package, I'm looking for a new maintainer of the package. The
package is trivial to maintain.
If nobody takes it, I'll take it over but I'll still be looking for a
new maintainer.
--
To
Package: wnpp
Severity: normal
On behalf of Boris Dušek, the current official sponsored maintainer of
the package, I'm looking for a new maintainer of the package. The
package is trivial to maintain.
If nobody takes it, I'll take it over but I'll still be looking for a
new maintainer.
--
To
Package: wnpp
Severity: normal
On behalf of Boris Dušek, the current official sponsored maintainer of
the package, I'm looking for a new maintainer of the package. The
package is trivial to maintain.
If nobody takes it, I'll take it over but I'll still be looking for a
new maintainer.
--
To
Package: wnpp
Severity: normal
I'm no longer interested in maintaining the package so I orphan it.
--
To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org
with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Package: wnpp
Severity: normal
I'm no longer interested in maintaining the package, so I orphan it.
The package is basically abandoned upstream.
--
To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org
with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Package: wnpp
Severity: normal
The package is only useful for now orphaned cl-mcclim package, so I
orphan it as well. Unless somebody wants to maintain cl-mcclim, this
package is probably no longer necessary in Debian as it can be easily
installed via Quicklisp.
--
To UNSUBSCRIBE, email to
Package: wnpp
Severity: normal
The package is only useful for now orphaned cl-mcclim package, so I
orphan it as well. Unless somebody wants to maintain cl-mcclim, this
package is probably no longer necessary in Debian as it can be easily
installed via Quicklisp.
--
To UNSUBSCRIBE, email to
Package: wnpp
Severity: normal
I'm no longer interested to maintain the package so I'm looking for a
new maintainer. The package is easy to maintain.
--
To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org
with a subject of unsubscribe. Trouble? Contact
Package: wnpp
Severity: normal
I'm looking for a new maintainer of scanbuttond. I no longer have a
scanner on my desk so I can't test the package. I may continue to
maintain the package for a while but I'm going to orphan it sooner or
later.
Maintaining the package is not difficult. Just note
HY == Hideki Yamane henr...@debian.or.jp writes:
HY Attached patch would fix this FTBFS, could you consider to apply
HY it, please?
Thanks for the patch, I'll try to handle it soon.
--
To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org
with a subject of unsubscribe.
Is the bug still present in slime 20130626-1 (uploaded yesterday to
unstable)? I can't reproduce it so I guess it's gone.
--
To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org
with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
CS == Christoph Schloen schloenli...@gmail.com writes:
CS I hope one of you can add turn it into a proper patch.
Could you please create and send me the patch? You're the one who knows
what to do exactly and who can test it. It needn't be a proper Debian
patch, anything what can be
BM == Bernhard Marx be...@bernhard-marx.de writes:
BM Please add support for Fujitsu fi-5220C.
Added and uploaded to experimental. Thanks for the patch!
BM Please check whether it is right to decrease the numbers in the
BM following two lines (as I did in the patch):
It is,
AM == Agustin Martin agmar...@debian.org writes:
AM I am attaching a patch that may help here with speechd-el. For
AM emacs21 and emacs22 it checks if a standalone eieio package is
AM installed and otherwise warns and skips byte-compilation for
AM that flavour.
Thanks for the
Thanks for testing. If I compute correctly, 1620 ms is exactly 4.5
hours, not half an hour. Well, the exactness of the value is still
suspicious.
Please note that xprintidle doesn't do much more than reading and
printing the idle value returned from XScreenSaverQueryInfo. The only
possible
LZ == Lei Zhang lei-0400-deb...@leiz.org writes:
LZ IMO, if you are going to keep fujitsu.c, it's better to just
LZ replace to remove the scansnap backend altogether. It is just a
LZ duplicate of the epson backend.
I can see some differences between the two backends, they don't
NR == Nicholas Romero n...@romero.org writes:
NR FUJITSU fi-5110EOX works with the same codes as the newer
NR models.
Thanks, added in scanbuttond 0.2.3.cvs20090713-10.
--
To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org
with a subject of unsubscribe. Trouble?
Well, let's try it: Applied in scanbuttond 0.2.3.cvs20090713-9 in
experimental. Thanks for the patch!
--
To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org
with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
NS == Neil Schemenauer n...@debian.org writes:
NS The patch I submitted (bug #614312) is included in the debian
NS control directory but doesn't appear to be applied to the source
NS tree before building. It doesn't appear in the 'series' file
NS and I think that's the cause.
I've got the same problem and indeed `scanner' is a non-system group
(created by hand) on my system.
% sudo addgroup --system scanner
addgroup: The group `scanner' already exists and is not a system group. Exiting.
--
To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org
with a
CE == Christoph Egger christ...@debian.org writes:
CE This one looks like writing to $HOME which is not allowed and
CE will not fail in a cowbuilder environment normally. Would be
CE easy to test building with HOME=/something-not-existing
Thanks for explanation, indeed it's the
LN == Lucas Nussbaum lu...@lucas-nussbaum.net writes:
LN Source: slime
LN Version: 1:20111027-2
LN Severity: serious
LN Tags: wheezy sid
LN User: debian...@lists.debian.org
LN Usertags: qa-ftbfs-20120331 qa-ftbfs
LN Justification: FTBFS on amd64
LN Hi,
LN
JM == John McMonagle jo...@advocap.org writes:
JM Maybe I'll take a peek at the code :-)
Good idea. :-) The code is trivial, I suggest adding fprintf of the
retrieved values to workaroundCreepyXServer and to identify which one of
them is wrong when the incorrect idle time is printed.
I recompiled the package to debug it and the bug no longer appears.
It's also no longer reproducible with the binary package version 0.2-5
from testing.
Could you please install xprintidle 0.2-5 from testing
(http://packages.debian.org/wheezy/i386/xprintidle/download) and test
whether the bug is
DB == Daniel Baumann daniel.baum...@progress-technologies.net writes:
DB create a 'default' wheezy container with 'lxc-create -t debian
DB -n foo'.
This doesn't work:
# lxc-create -t debian -n foo
Note: Usually the template option is called with a configuration
file option
With lxc 0.7.5-24 container creation works and the container startup
problem is the same:
# lxc-start -n foo
lxc-start: Invalid argument - pivot_root syscall failed
lxc-start: failed to setup pivot root
lxc-start: failed to set rootfs for 'foo'
lxc-start: failed to setup the container
DB == Daniel Baumann daniel.baum...@progress-technologies.net writes:
DB i've fixed that in git some time ago but didn't upload it yet.
DB please redo with lxc built from the debian branch of
DB git://vcs.progress-linux.org/users/daniel/packages/lxc.git
The first container creation
I tried to test pivot_root from command line after an unsuccessful
container start:
# cd /mnt/lxc
# ls
bin boot dev etc home lib lib64 media mnt opt proc root run sbin
selinux srv sys tmp usr var
# ls mnt
# pivot_root . /mnt/lxc/mnt
pivot_root: Invalid argument
I've got the same problem, with both lxc 0.7.5 and lxc 0.8.0~rc1-3.
--
To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org
with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
On my system the containers start fine on boot. Then I can stop any of
the containers, but I can't start any of them again nor can start any of
the non-auto containers. E.g. `/etc/init.d/lxc restart' stops all the
containers but doesn't start any of them again and the system is left
with many
So the failure happens in the call
pivot_root(., path)
in conf.c:setup_rootfs_pivot_root, with the error message Invalid
argument. `path' value is /mnt/lxc/mnt, current directory is
/mnt/lxc. This seems to be correct, or at least intended. The
directories in /mnt/lxc are mounted as follows:
No response from the upstream author so far, but I can reproduce the
bug. Example of reported times on my LTSP system:
14:20 302997
14:30 2703096 (30 minutes more)
14:40 3303215
14:50 2103337 (30 minutes less -- correct time again after 30 minutes idle)
It looks related to DPMS suspend
Package: wnpp
Severity: normal
I can't maintain the package for Debian anymore, so I orphan it.
--
To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org
with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Thanks for the information. I can't identify the problem, I've reported
it to one of the upstream authors.
--
To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org
with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
What are your DPMS timeout settings, as reported by `xset q'?
--
To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org
with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Package: wnpp
Severity: normal
I no longer print photos so I'm going to orphan this package. The
package is in a good state and the upstream author is responsive.
Tell me if you want to take over the package.
--
To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org
with a
speechd-el doesn't work with Emacs 23.3. Reported upstream.
Thanks for the bug report.
--
To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org
with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
RH == Raphael Hertzog hert...@debian.org writes:
RH BTW, you would have more success if you forwarded bugs to the
RH upstream maintainer (assuming there's one who is active, I
RH haven't checked).
Exactly. Please note that handling bug reports on possibly upstream
problems in
for the report.
commit d502393fb04706c80e3aa6d608d0d6bee7ef4927
Author: Milan Zamazal p...@debian.org
Date: Wed Feb 2 17:34:32 2011 +0100
Fix logrotate script breaking logrotate configuration of other packages (#611711)
diff --git a/debian/changelog b/debian/changelog
index c6835c1..7159ae5
NL == Nerius Landys nlan...@gmail.com writes:
NL How to cleanly shut down speech-dispatcher (experimental) when I
NL log out?
I believe that simply killing it (sending the TERM signal) is OK.
If I understand you right, you've solved all the other previously
mentioned usage problems?
NL == Nerius Landys nlan...@gmail.com writes:
NL The problem is that when I have speech-dispatcher configured
NL using the espeak module, it will stop responding sometimes and
NL go into an infinite loop. top will show speech dispatcher
NL using 100% CPU and it will no longer
Package: xxkb
Version: 1.11-2.1
Severity: normal
xxkb man page documents `*.xpm.*' configuration options, e.g.
XXkb.button.xpm.1
These used to work in lenny, but is not working for me anymore in
squeeze. These should actually be of the form `*.image.*' now, e.g.
XXkb.button.image.1
Package: xnee-doc
Version: 3.06-1
Severity: normal
When I view Info documentation index in Emacs 23.2 (after pressing
`C-h i'), the Xnee entry is present, but it can't be entered and it
looks a bit weird:
Miscellaneous
* Xnee: (Xnee).Xnee's Not Event Emulator.
i.e. it is
Package: xnee-doc
Version: 3.06-1
Severity: normal
In some sections of the Xnee Info manual (namely Functional overview
and File format) there are ^M characters present within the text when
viewed in Emacs 23.2.
-- System Information:
Debian Release: squeeze/sid
APT prefers testing
APT
It seems the bug has already been fixed in speech-dispatcher 0.7.1 which
is currently in experimental (due to freeze).
--
To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org
with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
ST == Samuel Thibault sthiba...@debian.org writes:
ST Ok, but shouldn't we fix it in squeeze too?
Maybe we should, but the bug is not marked as release critical now.
--
To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org
with a subject of unsubscribe. Trouble? Contact
As reported by upstream the bug is fixed in Speech Dispatcher 0.7.1, so
I'll close it once 0.7.1 package gets moved from experimental to
unstable.
--
To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org
with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Thanks for the patch, forwarded upstream.
--
To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org
with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Thanks for the report, forwarded upstream.
--
To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org
with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
1 - 100 of 321 matches
Mail list logo