On Tue, 21 Apr 2009, James Vega wrote:
No one *needs* to do anything. If you want to make sure it gets fixed
to your satisfaction, send a patch and I'll gladly forward it upstream
to Bram for his consideration.
Bram hasn't expressed any interest in fixing syntax highlighting of what
he
On Sat, 18 Apr 2009, Debian Bug Tracking System wrote:
This is an automatic notification regarding your Bug report
which was filed against the vim-runtime package:
#319830: [vim-runtime] gcc's statement expression breaks syntax highlighting
[...]
As Bram posted a few years ago, adding let
Package: iceweasel
Version: 2.0.0.1+dfsg-3
Severity: grave
Upon upgrading my system, and installing the new versions of
the firefox/iceweasel packages, the next attempt to start firefox
results in one of those import preferences from mozilla 6.x
windows, and then, of course, a fresh iceweasel
Package: vim-runtime
Version: 7.0-164+1
When this sort of construct is included in C code,
brace highlighting breaks in the rest of the file:
#define FUNCTION(x) ({ x; })
That macro is a statement expression (a very useful gcc
extension). Add it in the beginning of your file, and all the
curly
On Tue, 28 Nov 2006, Steve Langasek wrote:
On Tue, Nov 28, 2006 at 02:30:32PM -0800, Alvaro Martinez Echevarria wrote:
The last version of x11-common in sid (1:7.1.0-7) includes an
explicit conflict for xephem (with no version), so this extremely
useful astronomy package becomes
Package: xephem
Version: 3.5.2-1
Severity: grave
The last version of x11-common in sid (1:7.1.0-7) includes an
explicit conflict for xephem (with no version), so this extremely
useful astronomy package becomes uninstallable. A relatively
quick would be appreciated (recompilation?).
Regards,
--
On Sun, 26 Nov 2006, Debian Bug Tracking System wrote:
This is an automatic notification regarding your Bug report
#399571: mozilla-mplayer: plugin does not handle media types in mozilla (and
firefox),
which was filed against the mozilla-mplayer package.
It has been closed by Ari Pollak
On Tue, 21 Nov 2006, Ari Pollak wrote:
On Tue, 2006-11-21 at 01:15 -0800, Alvaro Martinez Echevarria wrote:
The bug specifies that firefox does not work either.
Should that be confirmed before closing the bug?
Please accept my deepest apologies for missing a small parenthetical
remark
This patch fixes the problem for me (I'm having the exact same
problem, where a fresh sid instalation fails with the cannot
write errors). It seems to me that the code in
FcDirCacheProcess() is wrong: since files are being modified in
the cache directory, dir_stat.st_mtime = file_stat.st_mtime
Package: linux-source-2.6.12
Version: 2.6.12-1
Severity: normal
Hi,
Regarding this problem with iproute:
http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=282492
Would it be possible to include a fix for this, or at least make
CONFIG_ATM_CLIP a module instead of a yes in the stock kernel?
I'm
Package: gpart
Version: 0.1h-4
Severity: important
Tags: patch
For crying out loud, support for reiserfs 3.6 has been ready for
two and a half years already; the bug was first reported 15 months
ago. Considering how many modern installations of reiserfs there
are, this package is useless in a
Package: linux-source-2.6.12
Version: 2.6.12-1
Severity: wishlist
Hi,
It would be wonderful if you could include this patch in the
stock debian kernel:
http://hem.bredband.net/ekmlar/vt1211.html
It's the sensor chip contained in mini-ITX boards, among others,
providing temperature readings,
The bug is obvious and I provided a patch with my report.
That was two months ago. Why on earth nothing was done
about it?
--
Álvaro Martínez Echevarría
``Pero yo que he sentido una vez en mis manos temblar
la alegría / ya no podré morir nunca. / Pero yo que he
tocado una vez las agudas agujas del
Ph
There's yet another, more serious problem. apcupsd depends on
libcrypto and libsnmp, which are on /usr/lib. Again, this could
be (and normally is) a different filesystem and it won't be there
when apcupsd --killpower is invoked. Two fixes I can think of
would be to either make the
will not work (because
+by the time it is invoked from halt, the filesystems will not be
+mounted anymore). Add a killpower script in /etc/apcupsd with a
+small comment indicating the potential need to mount /var and /usr
+read-only.
+
+ -- Alvaro Martinez Echevarria [EMAIL PROTECTED] Mon
Package: apcupsd
Version: 3.10.16-7
apcupsd does not shut down the UPS in my configuration (detected
as model Back-UPS ES 500, using USB). There are two problems.
- First, the file /var/spool/apcupsd/powerfail is not being
created, so apcupsd is never called with --killpower because
of the
Package: mozilla-browser
Version: 1.7.5-1
The sound system detection in the mozilla wrapper script is
broken: it tests for the existence of /dev/dsp using '-f', which
is meant for regular files. The result is no wrapper is used when
MOZILLA_DSP is 'auto', and sound doesn't work. This fixes the
17 matches
Mail list logo
