Hi everyone -
On Tue, Jan 28, 2025 at 10:51:44AM +0100, Tarik Graba wrote:
> I have tested the version merged in Salsa (built on Debian Bookworm) and it
> seems ok.
> Le 27/01/2025 à 20:06, Scott Ashcroft a écrit :
> > I think I've done the work to get 0.49 packaged and it has been merged
> > in s
Package: verilator
Version: 5.030-1
Severity: serious
Attempting to build actual verilated executables always crashes with
python3: can't open file '/usr/share/verilator/bin/verilator_includer'
How to reproduce:
On a system with git build-essential verilator installed,
git clone https://githu
Debian friends -
Bug #1069424 yosys: FTBFS on armhf appears to be documentation-related,
and found in version yosys/0.33-5.
I note that there is a changelog item for yosys-0.40: Major documentation
overhaul.
It would make sense to try updating to that version -- or 0.44, as
noted on the Debian
On Sun, Nov 05, 2023 at 01:39:30PM -0800, Larry Doolittle wrote:
> On Mon, Oct 02, 2023 at 11:04:12PM -0700, Larry Doolittle wrote:
> > [...] working versions are v5.014 and v5.016.
> [and v5.018]
Verilator v5.020 was pushed to upstream git on Jan 1, 2024,
and I can confirm it a
On Mon, Oct 02, 2023 at 11:04:12PM -0700, Larry Doolittle wrote:
> [...] working versions are v5.014 and v5.016.
Verilator v5.018 was pushed to upstream git on Oct 31,
and I can confirm it also does not suffer from this bug.
- Larry
Andreas -
On Thu, Nov 02, 2023 at 04:51:55PM +0100, Andreas Metzler wrote:
> Just to be clear: You have got a domain but lack both control of a
> machine that is not blocked from accessing outgoing port 25 (and could
> deliver)
Right. Standard for a "modern" consumer-grade ISP in the U.S.
> and
Andreas -
On Mon, Oct 16, 2023 at 07:13:28PM +0200, Andreas Metzler wrote:
> > severity 941804 normal
> > This exim4 bug has taken on increased importance now that gmail requires
> > DKIM
> > on all (?) incoming messages.
>
> I do not follow:
>
> The smarthost transport is typically used by a
Control:
found 941804 4.94.2-7+deb11u1
found 941804 4.96-15+deb12u2
found 941804 4.97~RC1-2
severity 941804 normal
thanks
This exim4 bug has taken on increased importance now that gmail requires DKIM
on all (?) incoming messages.
I checked and can confirm its presence in the three versions above,
Apologies for the possibly confusing typo above.
> I can confirm that the bug shows up in v5.012, but not v5.014 or v6.016.
Of course I mean to say that working versions are v5.014 and v5.016.
Where v5.016 doesn't look properly tagged yet, but is actually commit cef3960a.
- Larry
Package: verilator
Version: 5.012-1+b1
My use case triggers upstream issue 4362
https://github.com/verilator/verilator/issues/4362
Earlier versions of verilator, like 5.006-3 found in bookworm,
do not show the same bug, so it counts as a regression.
I personally built several versions from sourc
H for docs guide conf.py 3918.patch" in patches/series)
verilator should build reproducibly on tests.reproducible-builds.org!
Thanks for maintaining Verilator!
- Larry
>From bc6a7787ed271a8f52ed5b8f8a9e0e8cbba1ab38 Mon Sep 17 00:00:00 2001
From: Larry Doolittle
Date: Sun, 12 Feb 2
Thanks, John, for the patch.
Submitted upstream as pull-request #3954.
https://github.com/verilator/verilator/pull/3954
Debian Electronics Team -
I confirm that Debian Verilator is outdated and not useful
for Real Work.
I can also confirm that "modern" versions of upstream Verilator build
easily from source in Debian Testing, and work well.
For me, "modern" means v4.220 or later -- that was posted March 2022.
At t
I can confirm that the xdaliclock 2.46 in Bookworm/testing works nothing like
historical copies of the program. In my case, I have an ancient incantation
buried in my .xsession file
/usr/bin/xdaliclock -noseconds -nocycle -builtin1 -bg steelblue -fg black -geom
-0-0
and the new xdaliclock underst
My testing confirms this bug still applies to xauth-1:1.1-1 in Bullseye,
as the status graphic indicates.
Fixed upstream in xauth-1.1.1. I hope that version can be
packaged in time for Bookworm -- it includes a number of
subtle but important improvements.
Looking at the upstream repo at
https:
Alexis Murzeau wrote:
> See here: https://news.ycombinator.com/item?id=19826903
Which instructs people to install
https://storage.googleapis.com/moz-fx-normandy-prod-addons/extensions/hotfix-update-xpi-intermediate%40mozilla.com-1.0.2-signed.xpi
For me at least, that download resulted in a file
Friends -
Working in Debian Wheezy, I built scala-2.11.2 from sources without using
un-sourced jars. Source is
https://github.com/scala/scala/archive/v2.11.2.tar.gz
52654124565a1706e9e6d0ad7b0969d319628847 scala-sources-2.11.2.tar.gz
In scala's build.xml I changed the definition of lib-ant.dir
Friends -
I tried to figure out where the sources are for the .jar files
required for scala-2.11.2. I'll append my stupid shell script,
and its output. Some, but not all, of those sources show up in
http://www.java.net/download/openjdk/jdk7u40/promoted/b43/openjdk-7u40-fcs-src-b43-26_aug_2013
Dear iceweasel maintainers and lurkers,
Here's some history, analysis, and a recommendation.
Firefox 10-ESR disabled WebGL/Mesa based on
https://bugzilla.mozilla.org/show_bug.cgi?id=777028
in which the rationale comes out clearly:
1. the Firefox team can't control the quality of the Mesa vers
Maybe I'm talking to myself. The offending blacklist code is the
stanza on lines 329-332 of widget/xpwidgets/GfxInfoX11.cpp :
if (aFeature == nsIGfxInfo::FEATURE_WEBGL_OPENGL) {
*aStatus = nsIGfxInfo::FEATURE_BLOCKED_DRIVER_VERSION;
aSuggestedDriverVersion.AssignLi
I confirmed a few things:
1. Visiting get.webgl.org with iceweasel 17.0.8esr-1~deb7u1
tells me that webgl is not available.
2. Downgrading to
iceweasel_10.0.12esr-1_amd64.deb
libmozjs10d_10.0.12esr-1_amd64.deb
xulrunner-10.0_10.0.12esr-1_amd64.deb
from my CD not only shows
WebGL Renderer: X.Org -
Package: iceweasel
Version: 17.0.8esr-1~deb7u1
Severity: normal
Dear Maintainer,
Upgrading stock wheezy from iceweasel 10.0.12esr-1 (on the CD)
to 17.0.8esr-1~deb7u1 (current security patch as of 2013-08-19)
breaks WebGL renderer detection, at least on my test machine with
Adapter Description: X
I reviewed the pmw-4.24 code, and Thorsten Glaser's patch.
His analysis and patch is correct. After the patch, the code
is correct even in the presence of ASLR.
At least every Debian system, and probably every POSIX system,
will unmap page zero to make sure null pointer dereferences
are trapped.
It would be really stupid to go through another Debian
release with this bug unfixed. Upstream's evilwm-1.0.1
is a targeted fix for this bug.
- Larry
--
To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org
with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debi
I suffer from a less severe case of this bug on amd64.
There are only tens, not thousands, of false positives.
valgrind version 1:3.4.0-1
Debian sid/squeeze on amd64.
Here's a typical false positive:
==28899== Conditional jump or move depends on uninitialised value(s)
==28899==at 0x4015AEE:
block 510033 512821
severity 510033 important
thanks
Since nobody has put in a rebuttal of my analysis, or offered
another suggestion, ...
Policy 10.7.4 says "The related packages _must_ use the provided
program", which I suppose is the justification for the original
"serious" severity level. Bu
Package: sysvinit
Version: 2.86.ds1-61
Severity: wishlist
/etc/inittab is a historical relic. Useful and standardized,
but in some ways it is not a good fit to the rest of Debian.
My reading of Debian policy 10.7.1 suggests it qualifies as
a "configuration file", although not a conffile.
At
Package: evilwm
Version: 1.0.0-1
Severity: normal
The signal handler in 1.0.0 (and earlier) evilwm is theoretically
buggy, and some Debian system changes this past year made the
consequences real. Stock evilwm now hangs up in response to a
kill signal (e.g., control-C or killall evilwm).
Since t
Thomas -
On Thu, Jan 08, 2009 at 10:27:02AM -0500, Thomas Dickey wrote:
> On Wed, Jan 07, 2009 at 07:30:08PM +0100, Larry Doolittle wrote:
> > Package: xterm
> > Version: 238-2
> > Severity: normal
> >
> > Upgrading amd64 from xterm_237-1 to xterm_238-2, the
>
Package: xterm
Version: 238-2
Severity: normal
Upgrading amd64 from xterm_237-1 to xterm_238-2, the
keypad PgUp and PgDn keys stopped responding. This
is an ordinary PC keyboard. The dedicated PageUp and
PageDown keys are still OK.
(fixed font ASCII table)
key keycode xterm_2
Sune Vuorela reported
>Runit does cat/sed magic on /etc/inittab on installation and removal.
True.
> it looks like a clear violation of 10.4.7.
ITIYM 10.7.4
My analysis:
/etc/inittab is not a Debian 10.7.1 conffile, it is rather a
configuration file, owned and managed (cough) by sysvinit.
The
On Mon, Nov 17, 2008 at 07:10:34PM -0800, Larry Doolittle wrote:
> I can confirm that AR5212 doesn't work as-is on Lenny.
Never mind. User error. An AR5212 (pci id 168c:0013 (rev 01))
works for me now on linux-image-2.6.26-1-686 version 2.6.26-10.
- Larry
--
To UNSUBSCRIBE,
An apparently successful patch has been worked out upstream. See
http://thread.gmane.org/gmane.linux.kernel.wireless.general/22825/focus=22840
The concluding patch for 2.6.27 was posted
From: Elias Oltmanns
Subject: Re: [PATCH] ath5k: Fix reset sequence for AR5212 in general and
RF5111 in pa
Package: link-grammar
Version: 4.3.5-1
Severity: important
After a fresh install of link-grammar, I try
$ man link-grammar
[blah-bah]
Looks good. So I try
$ link-grammar
bash: link-grammar: command not found
That's odd.
$ dpkg-query -L link-grammar
[blah-blah]
/usr/bin/link-parser
OK, I try
Josselin -
> Is there anything that is possible to help fixing this before the
> release?
My reading of header files shows that libc6-dev in etch, lenny,
and sid does not suffer from the original problem. The files
that include a workaround (ugly, but apparently functional) for
possible namespac
I can see the same effect on every package (tried 4 before I got bored),
including reportbug itself. The screen looks as follows:
36) #475641 [n||] [audacity] audacity: audacity.1.gz is not a gzipped file Re
37) #481424 [n||] [audacity] does not respect locales/$LANG Reported by: "W.
38) #
Hi Alexander,
I can't reproduce this on my Sid box. My amd64 is not SMP,
and the kernel is 2.6.26-8 instead of 2.6.25.4.
Could that make a difference?
- Larry
--
To UNSUBSCRIBE, email to [EMAIL PROTECTED]
with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
Package: uml-utilities
Version: 20070815-1.1
Severity: wishlist
Tags: patch
$ ls -l /usr/lib/uml/uml_net
-rwsr-x--- 1 root uml-net 23616 2008-04-05 06:46 /usr/lib/uml/uml_net
All's well except for the missing "r" for other. There are no secrets
in that file, as far as I can see. If a user want
I propose we close this bug. The current dash behavior matches
that of bash. The corresponding bash bug report (288319) was
closed with the changelog entry
- Fixed exit status code so that a suspended job returns 128+signal as its
exit status (preventing commands after it in `&&' lists fr
Try this patch. I haven't stress-tested it, but it
does at least address the original complaint.
- Larry
--- a/src/exec.c2007-07-13 01:26:43.0 -0700
+++ b/src/exec.c2008-07-23 12:46:04.0 -0700
@@ -752,7 +752,7 @@
struct cmdentry entry;
struct tb
Steve -
On Mon, Jul 21, 2008 at 11:36:03AM -0700, Steve Langasek wrote:
> On Mon, Jul 21, 2008 at 09:38:43AM -0700, Larry Doolittle wrote:
> > smbclient1270425628
>
> > My hope is that there is some systematic cause that can
> > be fixed, an
Hi -
Repeating the original (2008-04-28) table:
3.0.28a-1 3.2.0~pre1-1
libtalloc1 0 84
libwbclient0 0 136
libsmbclient 2320 3808
samba-common 694410928
smbclient1252
I can't verify that Jonathan Cichos answered Junichi Uekawa's question.
Here is the debug trace for the case that I hit on my machine.
Upgrading texlive-latex-base from 2007-14 to 2007.dfsg.1-1 on sid amd64.
$ (echo 'VERSION 2'; echo '' ; ls -1
/var/cache/apt/archives/texlive-latex-base_*.deb | s
you don't like me acting as a messenger in this case, tough
noogies. I didn't write the DFSG. The real blame here lies with
Linus's historical sloppiness in accepting non-DFSG-free code.
I hear he has improved his process this past couple of years.
- Larry Doolittle
[*] and yes
This is Icarus bug 1890393
https://sourceforge.net/tracker/index.php?func=detail&aid=1890393&group_id=149850&atid=775997
Solution given (by me) on 2008-04-11:
> It should also work to remove the # include
> line from vvp/main.cc.
>
> That include (and the surrounding if defined(LINUX)/endif) s
Package: smbclient
Version: 3.2.0~pre2-1
Severity: wishlist
On sid amd64, I just upgraded to 3.2.0~pre2-1.
I hope most of the jump in size is temporary -- maybe executables
weren't stripped? I expect some size increase with every version,
but this looks excessive. Installed sizes:
Gerrit -
I just spent another half hour poking around looking at bug 470029 et al.
I start to get the impression that there is no bug in dash.
evolution-data-server crashes, traps the crash, calls
/usr/lib/libgnomeui-0/gnome_segv2 \"evolution-data-server-1.12\" 11 \"1.12.1\"
in an attempt to ge
The origin of the problem is a change (between fltk1.1-1.1.7 and
fltk1.1-1.1.8~rc1) in the output of fltk-config.
With libfltk1.1{,-dev} version 1.1.7-7 installed, I get
$ fltk-config --use-gl --libs
/usr/lib/libfltk.a /usr/lib/libfltk_gl.a
$
but with revision 1.1.8~rc1-2 I get
$ fltk-config --
There is one Ubuntu filing on this bug:
https://bugs.launchpad.net/ubuntu/+bug/185075
There are a couple of hints that Evolution is involved
somehow in triggering this bug. Thus the page
http://www.gnome.org/projects/evolution/bugs.shtml
"A Quick Guide to Evolution Bug Hunting" may be helpful.
I
For the record, ThomB is running an Ubuntu Gutsy dash .deb that
I provided him. It has the same cmdtxt bug fix as Debian 0.5.4-8,
and is built with DEB_BUILD_OPTIONS=nostrip, hence the halfway-useful
stack trace.
For a start, that trace makes it clear that it is not a duplicate
of #467065. By an
Falk -
On Fri, Mar 07, 2008 at 03:02:41PM +0100, Falk Hueffner wrote:
> On Thu, Mar 06, 2008 at 10:39:34PM +0100, Rafael Laboissiere wrote:
> > You are absolutely right. I will consider producing two independent library
> > packages, one with MathPROG support and the other without. [chop]
>
> J
Package: libglpk0
Version: 4.25-1
Severity: wishlist
The 4.27-1 update includes:
* debian/control: Build-depend on libiodbc2-dev and
libmysqlclient15-dev in order to get MathPROG support
Apparently this also adds to the install-time dependencies.
Upgrading to this version, apt-get tells me:
Package: octave3.0
Version: 1:3.0.0-7
Severity: minor
Tags: patch
PostScript output for e.g. axis labels uses a tolower() version
of the font name, which is broken. Please pull upstream's fix
at the next available opportunity.
http://velveeta.che.wisc.edu/cgi-bin/hgwebdir.cgi/octave/rev/71209c
The runit-1.8.0-3 changelog includes
* debian/runit.preinst, debian/runit.postinst: move away from /var/service/
to /etc/service/; restart runsvdir; retain backward compatibility symlink
/var/service -> /etc/service until rdepends have adopted (#461478).
which presumably triggers the effect
Package: runit
Version: 1.8.0-4
Severity: critical
Justification: breaks unrelated software
Upgrading from runit 1.8.0-2 to 1.8.0-4 fails.
It seems to restart user processes, including the
one that is doing the upgrade. The first time it
kicked me out of X. It leaves dpkg/apt in an unusable
and
Dear submitters -
I just posted a patch for dash in
http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=467065
Is it possible for you to test and find out if it
addresses your dash problems?
Please report back. If it does not solve your problem,
you probably need to provide more in-depth informa
(Herbert: for context, see
http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=467065 )
This is a real bug in upstream dash, which has existed since at
least dash-0.5.1 (July 2004). It is a latent bug in cmdtxt()
(which I think applies only to pipes) as it handles "if" commands.
The attached patch f
On Fri, Feb 22, 2008 at 02:34:09PM -0800, Larry Doolittle wrote:
> The bug does not reproduce on i386/gcc-4.1 (Gutsy).
The second example does. I have simplified the example some more.
No setup required. To an interactive dash, cut-and-paste:
if true; then for x in foo; do echo bar; done;
I spent way too much time in front of gdb. More info:
The bug does not reproduce on i386/gcc-4.1 (Gutsy).
The bug does reproduce with stock dash-0.5.4 on amd64/gcc-4.2 (Sid).
It is not affected, and is much easier to follow within gdb,
by compiling -O0.
The bug is not affected by building/runn
Package: dash
Version: 0.5.4-7
Severity: important
Steps to reproduce segfault, within dash:
mkdir -p dash-test
touch dash-test/a.xpm
if test -d "dash-test"; then echo "dash-test"; for pixmap in "dash-test/"*.xpm;
do echo "${pixmap}"; done; fi | less
The first two lines can be given in any she
Package: flex
Version: 2.5.34-3
Severity: normal
I started getting new warnings from the C compile phase of
lexers as of 2.5.34, which I verified showed up in the transition
from 2.5.33-12 to 2.5.34-1. The warnings are:
warning: comparison between signed and unsigned integer expressions
I trac
The problem is in a different treatment of echo "\n".
Under bash it comes out "\n", under dash it comes out "
".
This patch quickly bypasses the problem. Trust it as
far as you can throw it.
- Larry
--- kbd-1.12/configure 2004-01-03 06:53:39.0 -0800
+++ kbd-1.12-hack/configure 2
Martin -
> After running for a mere 20 hours, /proc/cpu/alignment reports
> millions of misaligned word accesses from the kernel:
> System: 2765980
After checking 2.6.23 from unstable as maks suggested,
please report back more detail on the hardware you have
in service. I have seen an AR
Package: xmds
Version: 1.6.3-1
Severity: important
please rebuild against libfftw3-3
Justification for using important instead of wishlist:
other software in this category, e.g. octave, is built
against libfftw3-3, which replaces fftw3. Thus it's
not currently possible in sid to install both xm
To me, youtube-dl is the epitome of a package that
belongs in volatile. Putting it in stable invites
bugs like this.
I have no idea if it can be switched to etch-volatile
at this time.
Personally, I run a copy built from upstream source.
Its build requirements and resource needs are trivial.
Package: linux-2.6
Severity: serious
Justification: Policy 2.1
The following 59 files, found in Debian's linux-2.6_2.6.17.orig.tar.gz,
apparently contain software in binary form, for which Debian has no
corresponding source code. Debian policy states that "The program
must include source code, a
Package: cpio
Version: 2.6-14
Severity: grave
Justification: renders package unusable
cpio_2.6-14 fails to install with apt-get upgrade.
Preparing to replace cpio 2.6-13 (using .../archives/cpio_2.6-14_amd64.deb) ...
dpkg: error processing /var/cache/apt/archives/cpio_2.6-14_amd64.deb (--unpack)
Package: python2.3
Version: 2.3.5-14
Followup-For: Bug #373952
I get an identical error message when attempting to update
python2.3 on my amd64 sid machine.
-- System Information:
Debian Release: testing/unstable
APT prefers unstable
APT policy: (500, 'unstable')
Architecture: amd64 (x86_64
Package: libselinux1
Version: 1.30-1
Severity: normal
# apt-get install libselinux1
appears to succeed, messages are:
Preparing to replace libselinux1 1.30-1 (using
.../libselinux1_1.30-1_amd64.deb) ...
Unpacking replacement libselinux1 ...
Setting up libselinux1 (1.30-1) ...
#
But after su
Package: libg2c0-dev
Version: 1:3.4.5-1
Severity: normal
Out of the 905 packages on my pure 64-bit amd64 debian sid machine,
only this one and fakeroot put any files in /emul/ia32-linux/ .
For general cleanliness and possible improved security, I don't
want any 32-bit compatibility libraries on t
Package: fakeroot
Version: 1.5.5
Severity: normal
Out of the 905 packages on my pure 64-bit amd64 debian sid machine,
only this one and the recent libg2c0-dev put any files in
/emul/ia32-linux/ . For general cleanliness and possible improved
security, I don't want any 32-bit compatibility librari
I summarized my "research" with:
> [T]his might not apply to debian at all.
Michelle Konzack chimed in with:
> It does not affect Debian, but Mandrake and Redhat... :-)
Florian Weimer asked:
> Can you rule out that it's not reproducible with some other charset?
I can't rule anything out. If I
Guys -
I get similar problems building USRP (not yet a Debian package).
I can fix things up by deleting the line
#include
from /usr/include/linux/usbdevice_fs.h.
This change is not obviously broken, as it is one of only two *.h
files in there that includes compat.h. The other one is kexec.h,
I read the full-disclosure post, and its reply.
http://www.derkeiler.com/Mailing-Lists/Full-Disclosure/2005-08/0600.html
Two example mailboxes are given (one in each post),
and it is suggested that the problem is triggered
by a library runtime version mismatch.
I tried both examples on
debian s
Package: htmldoc
Severity: grave
Justification: renders package unusable
# apt-get install libfltk1.1c102
Reading package lists... Done
Building dependency tree... Done
Package libfltk1.1c102 is not available, but is referred to by another package.
This may mean that the package is missing, has b
While freetype version 2.1.10 (as used in Debian sid)
still has the source code constructs described in this
bug report, the result does seem to work fine on a 64-bit
arch (amd64).
* It builds without any of the characteristic 64-bit
unclean warnings.
* I can run
ttfbanner -p 8 $f test
Hamish -
On Mon, Jul 11, 2005 at 02:40:45PM +1000, Hamish Moffatt wrote:
> Derek (upstream) says
> "There was a change in the way FT handles CID font encodings in 2.1.8.
> I'm just about to release Xpdf 3.01 which will have code to handle that
> correctly."
OK, I believe it. Someone with more de
I wrote -
> Replacing libfreetype6 with 2.1.7-2.4 on debian sid
> makes the problem disappear.
Working on debian sid amd64,
I just downloaded freetype-2.1.{7,8,9,10}.tar.bz2 from
http://sourceforge.net/project/showfiles.php?group_id=3157
I gave each of them a "./configure && make", which ran
sm
I wrote -
> Broken stack on amd64 sid:
>xpdf 3.00-13
>libt1-5 5.0.2-3
>libfreetype6 2.1.10-1
>zlib1g 1:1.2.2-6
>
> Working stack on i386 sarge:
> xpdf 3.00-13
> libt1-5 5.0.2-3
> libfreetype6 2.1.7-2.4
> zlib1g 1:1.2.2-4.sarge.1
>
> I'll try to figure out the reci
I wrote -
> So it's either a deeper library version problem, or xpdf
> on amd64 itself.
Combining Hamish's results with mine points to a deeper
library version problem. Something to do with font encoding.
Broken stack on amd64 sid:
xpdf 3.00-13
libt1-5 5.0.2-3
libfreetype6 2.1.10-1
es are CVS tags and some trailing spaces in the source.
Tested, works. 2005-05-23 Larry Doolittle <[EMAIL PROTECTED]>
diff -ur xc~/extras/Xpm/lib/RdFToI.c xc/extras/Xpm/lib/RdFToI.c
--- xc~/extras/Xpm/lib/RdFToI.c 2005-05-23 10:12:01.211131000 -0700
+++ xc/extras/Xpm/lib/RdFToI.c
On Mon, May 23, 2005 at 11:20:52AM -0700, Larry Doolittle wrote:
> [chop]
> I noticed you changed the semantics of compressed file detection.
Sorry for the brainless chatter. I jumped to conclusions after
reading the patch, not looking at or testing the final code.
Both versions of th
Thomas -
I just read your patch to RdFToI.c titled
October 2004, source code review by Thomas Biege <[EMAIL PROTECTED]>
where you replaced calls to popen with the new routine xpmPipeThrough().
That is a big improvement, and debian needs to incorporate that
improvement in the upcoming sarge release
Daniel et al. -
On Mon, May 23, 2005 at 11:32:19AM +1000, Daniel Stone wrote:
> > I might play around with option 2. There are two strategies
> > that make technical sense:
>
> Why would you do this when there's already a version upstream that fixes
> this? I don't like the idea of having yet a
Branden Robinson asked:
> Could I get a second opinion (or more than one) from you guys as to
> whether this is actually an exploitable security problem?
I can't answer this in the affirmative, but then I only spent
about 15 minutes looking for a way to exploit it. I note that
apt-rdepends finds
Bug #309507 is effectively a duplicate of #303856.
Same source, same bug, different compiler and host
system. The patch given by Kurt Roeckx in 303856
for AMD64 should also take care of the S390 folks.
- Larry
signature.asc
Description: Digital signature
I can reproduce the bug on amd64 pure64. I can isolate the
segfault to
t->db->setDirty(true);
in the middle of void TodoDB::remove() in TodoDB.cc.
It's helpful to run with "-vv".
- Larry
signature.asc
Description: Digital signature
File compiler/back-ends/c-gen/gen-code.c uses ctime(3) without a
prototype, so its result is assumed integer (it's really a pointer).
Adding #include to that file fixes the FTBFS. Patch appended.
I can't vouch for proper operation of the result. There are still
a ton of warnings about incompati
Like many other people, I kept getting
dpkg: error processing
/var/cache/apt/archives/libwxgtk2.4-python_2.4.2.6.1_amd64.deb (--unpack):
trying to overwrite `/usr/bin/helpviewer', which is also in package
wxpython2.5.3
during an apt-get upgrade of libwxgtk2.4-python.
Turns out wxpython2.5.3 ha
I reproduced this bug, found the problem, and fixed it. Patch attached.
The problem is in the usage of get_attribute, which is a variable
argument function. The function checks for a NULL (char *) argument
to terminate processing. Callers used 0 to represent the end of
the list, which fails on
Presumably this error was caused by a missing /etc/network
in your chroot. Is it appropriate to add
mkdir -p /etc/network
to ifupdown.postinst before line 95
: > /etc/network/ifstate
? Or maybe earlier in the script?
- Larry
signature.asc
Description: Digital signature
91 matches
Mail list logo
