Hi Sam,
Sam Morris wrote:
> I would appreciate it if you could make a gnucash-dbg package available
> to aid in debugging this further.
Gnucash 2.2.9-2, currently available in Debian unstable, has now a
gnucash-dbg package with debugging symbols. Could you triage your bug
again with this package
Your message dated Mon, 07 Dec 2009 02:26:32 -0500
with message-id <4b1cae28.6020...@josephspiros.com>
and subject line Re: Bug#559547: __init__.pys present on my system
has caused the Debian Bug report #559547,
regarding python-coherence: Doesn't include __init__.py in submodules
to be marked as d
Processing commands for cont...@bugs.debian.org:
> # Mon Dec 7 07:03:29 UTC 2009
> # Tagging as pending bugs that are closed by packages in NEW
> # http://ftp-master.debian.org/new.html
> #
> # Source package in NEW: libpdl-netcdf-perl
> tags 559476 + pending
Bug #559476 [wnpp] ITP: libpdl-netcdf
Your message dated Mon, 07 Dec 2009 07:17:28 +
with message-id
and subject line Bug#559851: fixed in igerman98 20091006-2
has caused the Debian Bug report #559851,
regarding aspell-de: tries to register non-existent alternative
to be marked as done.
This means that you claim that the problem
No version before 1.0.9 is vulnerable - they do not use libtool and ltdl.
That leaves:
testing/squeeze 1.0.9-2
unstable/sid1.0.9-3
which are vulnerable.
No etch or lenny releases are vulnerable.
redland 1.0.9 upstream was built with libtool 2.2.6 so patching
source file redland-1.0.9/libltd
severity 559787 important
thanks
Hi Michael,
safe_mode and open_basedir do not receive security support (see
README.Debian.security in php4-common and data/package-tags on the
tracker repo) and PHP4 is far behind security updates anyway.
Sean, apparently at some point you said you were going to
Package: aspell-de
Version: 20091006-1
Severity: serious
Your package fails to configure:
,
| # LC_ALL=C dpkg --configure aspell-de
| Setting up aspell-de (20091006-1) ...
| update-alternatives: error: alternative path /usr/lib/aspell/de-neu.multi
doesn't exist.
| dpkg: error processing aspe
Processing commands for cont...@bugs.debian.org:
> severity 559787 important
Bug #559787 [php4] php4: CVE-2008-5624
Severity set to 'important' from 'serious'
> thanks
Stopping processing here.
Please contact me if you need assistance.
Debian bug tracking system administrator
(administrator, De
Your message dated Mon, 07 Dec 2009 07:17:09 +0100
with message-id <4b1c9de5.1020...@debian.org>
and subject line Re: Processed: severity of 559106 is serious
has caused the Debian Bug report #559106,
regarding mail-notification-evolution: Please recompile against evolution 2.28
to be marked as don
Your message dated Mon, 07 Dec 2009 06:03:13 +
with message-id
and subject line Bug#520862: fixed in libkarma 0.0.6-4.2
has caused the Debian Bug report #520862,
regarding libkarma - FTBFS: /usr/bin/csc: Command not found
to be marked as done.
This means that you claim that the problem has be
Your message dated Sun, 6 Dec 2009 23:57:43 -0600 (CST)
with message-id
and subject line
has caused the Debian Bug report #559838,
regarding CVE-2009-3736 local privilege escalation
to be marked as done.
This means that you claim that the problem has been dealt with.
If this is not the case it i
tag 520862 pending
thanks
peter green (23/03/2009):
> mono-devel needs to be moved from build-depends-indep to
> build-depends to fix this bug.
Indeed, thanks. Please find attached the patch for my NMU.
Mraw,
KiBi.
diff -u libkarma-0.0.6/debian/changelog libkarma-0.0.6/debian/changelog
--- libk
Processing commands for cont...@bugs.debian.org:
> tag 520862 pending
Bug #520862 [libkarma] libkarma - FTBFS: /usr/bin/csc: Command not found
Added tag(s) pending.
> thanks
Stopping processing here.
Please contact me if you need assistance.
Debian bug tracking system administrator
(administrato
On Sun, 6 Dec 2009 21:19:50 -0800 Steve Langasek wrote:
> On Mon, Dec 07, 2009 at 12:04:18AM -0500, Michael Gilbert wrote:
> > Package: unixodbc
> > Severity: grave
> > Tags: security
>
> > The following CVE (Common Vulnerabilities & Exposures) id was
> > published for libtool. I have determined
Hi Maximiliano.
Did you take in account the patch "01_debian_4.0.patch" introduced in the
version 2.6.0-2lenny2? It replaces the appereances of "debian-3.0" for just
"debian".
It is described in:
http://packages.debian.org/changelogs/pool/main/s/system-tools-backends/system-tools-backends_2.6.0-2l
Package: freecad
Version: 0.9.2646.3-1
Severity: grave
1) "create a new empty document"
2) "create a box feature"
(10 mm / 10 mm / 10 mm) at (0 / 0 / 0)
3) "create a Cylinder"
(10 mm height / 2 mm radius) at (0 / 0 /0)
4) edit Cylinder Data:
Angle from 360 degree to 45 degr
Sorry about the first NMU, looks like I only removed libc6-dev from
Build-Depends on a porter box, and checked it was OK there; and only
wrote about it on my devel box, where the NMU was prepared. Hopefully
the next one is OK. Sorry about that.
Mraw,
KiBi.
diff -u jconv-0.8.1/debian/changelog jcon
Your message dated Sun, 6 Dec 2009 21:19:50 -0800
with message-id <20091207051950.gh6...@dario.dodds.net>
and subject line Re: Bug#559830: CVE-2009-3736 local privilege escalation
has caused the Debian Bug report #559830,
regarding CVE-2009-3736 local privilege escalation
to be marked as done.
Thi
Package: sdcc
Severity: grave
Tags: security
Hi,
The following CVE (Common Vulnerabilities & Exposures) id was
published for libtool. I have determined that this package embeds a
vulnerable copy of the libtool source code. However, since this is a
mass bug filing (due to so many packages embedd
Package: imagemagick
Severity: grave
Tags: security
Hi,
The following CVE (Common Vulnerabilities & Exposures) id was
published for libtool. I have determined that this package embeds a
vulnerable copy of the libtool source code. However, since this is a
mass bug filing (due to so many packages
Package: heartbeat
Severity: grave
Tags: security
Hi,
The following CVE (Common Vulnerabilities & Exposures) id was
published for libtool. I see that heartbeat in unstable no longer
embeds libtool, but it appears that etch and lenny still have it. I am
not sure if it is actually used in the bin
Package: openmpi
Severity: grave
Tags: security
Hi,
The following CVE (Common Vulnerabilities & Exposures) id was
published for libtool. I have determined that this package embeds a
vulnerable copy of the libtool source code. However, since this is a
mass bug filing (due to so many packages emb
On Mon, Dec 07, 2009 at 04:22:11AM +0100, Cyril Brulebois wrote:
> Really good work! I've just slightly reworded the changelog to
> describe what was done, so that others can check and understand what's
> going on, I hope you're fine with that.
That's no problem at all -- in fact, I was very tire
Package: hypre
Severity: grave
Tags: security
Hi,
The following CVE (Common Vulnerabilities & Exposures) id was
published for libtool. I have determined that this package embeds a
vulnerable copy of the libtool source code. However, since this is a
mass bug filing (due to so many packages embed
Package: libprelude
Severity: grave
Tags: security
Hi,
The following CVE (Common Vulnerabilities & Exposures) id was
published for libtool. I have determined that this package embeds a
vulnerable copy of the libtool source code. However, since this is a
mass bug filing (due to so many packages
Package: proftpd-dfsg
Severity: grave
Tags: security
Hi,
The following CVE (Common Vulnerabilities & Exposures) id was
published for libtool. I have determined that this package embeds a
vulnerable copy of the libtool source code. However, since this is a
mass bug filing (due to so many package
Package: xmlsec1
Severity: grave
Tags: security
Hi,
The following CVE (Common Vulnerabilities & Exposures) id was
published for libtool. I have determined that this package embeds a
vulnerable copy of the libtool source code. However, since this is a
mass bug filing (due to so many packages emb
Package: unixodbc
Severity: grave
Tags: security
Hi,
The following CVE (Common Vulnerabilities & Exposures) id was
published for libtool. I have determined that this package embeds a
vulnerable copy of the libtool source code. However, since this is a
mass bug filing (due to so many packages em
Package: ski
Severity: grave
Tags: security
Hi,
The following CVE (Common Vulnerabilities & Exposures) id was
published for libtool. I have determined that this package embeds a
vulnerable copy of the libtool source code. However, since this is a
mass bug filing (due to so many packages embeddi
Package: parser
Severity: grave
Tags: security
Hi,
The following CVE (Common Vulnerabilities & Exposures) id was
published for libtool. I have determined that this package embeds a
vulnerable copy of the libtool source code. However, since this is a
mass bug filing (due to so many packages embe
Package: synfig
Severity: grave
Tags: security
Hi,
The following CVE (Common Vulnerabilities & Exposures) id was
published for libtool. I have determined that this package embeds a
vulnerable copy of the libtool source code. However, since this is a
mass bug filing (due to so many packages embe
Package: babel
Severity: grave
Tags: security
Hi,
The following CVE (Common Vulnerabilities & Exposures) id was
published for libtool. I have determined that this package embeds a
vulnerable copy of the libtool source code. However, since this is a
mass bug filing (due to so many packages embed
Package: sbnc
Severity: grave
Tags: security
Hi,
The following CVE (Common Vulnerabilities & Exposures) id was
published for libtool. I have determined that this package embeds a
vulnerable copy of the libtool source code. However, since this is a
mass bug filing (due to so many packages embedd
Package: parser-mysql
Severity: grave
Tags: security
Hi,
The following CVE (Common Vulnerabilities & Exposures) id was
published for libtool. I have determined that this package embeds a
vulnerable copy of the libtool source code. However, since this is a
mass bug filing (due to so many package
Package: clamav
Severity: grave
Tags: security
Hi,
The following CVE (Common Vulnerabilities & Exposures) id was
published for libtool. I have determined that this package embeds a
vulnerable copy of the libtool source code. However, since this is a
mass bug filing (due to so many packages embe
Package: mp4h
Severity: grave
Tags: security
Hi,
The following CVE (Common Vulnerabilities & Exposures) id was
published for libtool. I have determined that this package embeds a
vulnerable copy of the libtool source code. However, since this is a
mass bug filing (due to so many packages embedd
Package: naim
Severity: grave
Tags: security
Hi,
The following CVE (Common Vulnerabilities & Exposures) id was
published for libtool. I have determined that this package embeds a
vulnerable copy of the libtool source code. However, since this is a
mass bug filing (due to so many packages embedd
Package: redland
Severity: grave
Tags: security
Hi,
The following CVE (Common Vulnerabilities & Exposures) id was
published for libtool. I have determined that this package embeds a
vulnerable copy of the libtool source code. However, since this is a
mass bug filing (due to so many packages emb
Package: pinball
Severity: grave
Tags: security
Hi,
The following CVE (Common Vulnerabilities & Exposures) id was
published for libtool. I have determined that this package embeds a
vulnerable copy of the libtool source code. However, since this is a
mass bug filing (due to so many packages emb
Package: wml
Severity: grave
Tags: security
Hi,
The following CVE (Common Vulnerabilities & Exposures) id was
published for libtool. I have determined that this package embeds a
vulnerable copy of the libtool source code. However, since this is a
mass bug filing (due to so many packages embeddi
Package: pdsh
Severity: grave
Tags: security
Hi,
The following CVE (Common Vulnerabilities & Exposures) id was
published for libtool. I have determined that this package embeds a
vulnerable copy of the libtool source code. However, since this is a
mass bug filing (due to so many packages embedd
Package: lam
Severity: grave
Tags: security
Hi,
The following CVE (Common Vulnerabilities & Exposures) id was
published for libtool. I have determined that this package embeds a
vulnerable copy of the libtool source code. However, since this is a
mass bug filing (due to so many packages embeddi
Package: siproxd
Severity: grave
Tags: security
Hi,
The following CVE (Common Vulnerabilities & Exposures) id was
published for libtool. I have determined that this package embeds a
vulnerable copy of the libtool source code. However, since this is a
mass bug filing (due to so many packages emb
Package: kdelibs
Severity: grave
Tags: security
Hi,
The following CVE (Common Vulnerabilities & Exposures) id was
published for libtool. I have determined that this package embeds a
vulnerable copy of the libtool source code. However, since this is a
mass bug filing (due to so many packages emb
Package: libannodex
Severity: grave
Tags: security
Hi,
The following CVE (Common Vulnerabilities & Exposures) id was
published for libtool. I have determined that this package embeds a
vulnerable copy of the libtool source code. However, since this is a
mass bug filing (due to so many packages
Package: libextractor
Severity: grave
Tags: security
Hi,
The following CVE (Common Vulnerabilities & Exposures) id was
published for libtool. I have determined that this package embeds a
vulnerable copy of the libtool source code. However, since this is a
mass bug filing (due to so many package
Package: jags
Severity: grave
Tags: security
Hi,
The following CVE (Common Vulnerabilities & Exposures) id was
published for libtool. I have determined that this package embeds a
vulnerable copy of the libtool source code. However, since this is a
mass bug filing (due to so many packages embedd
Package: libtunepimp
Severity: grave
Tags: security
Hi,
The following CVE (Common Vulnerabilities & Exposures) id was
published for libtool. I have determined that this package embeds a
vulnerable copy of the libtool source code. However, since this is a
mass bug filing (due to so many packages
Package: libmcrypt
Severity: grave
Tags: security
Hi,
The following CVE (Common Vulnerabilities & Exposures) id was
published for libtool. I have determined that this package embeds a
vulnerable copy of the libtool source code. However, since this is a
mass bug filing (due to so many packages e
Package: glame
Severity: grave
Tags: security
Hi,
The following CVE (Common Vulnerabilities & Exposures) id was
published for libtool. I have determined that this package embeds a
vulnerable copy of the libtool source code. However, since this is a
mass bug filing (due to so many packages embed
Package: guile-1.6
Severity: grave
Tags: security
Hi,
The following CVE (Common Vulnerabilities & Exposures) id was
published for libtool. I have determined that this package embeds a
vulnerable copy of the libtool source code. However, since this is a
mass bug filing (due to so many packages e
Package: hercules
Severity: grave
Tags: security
Hi,
The following CVE (Common Vulnerabilities & Exposures) id was
published for libtool. I have determined that this package embeds a
vulnerable copy of the libtool source code. However, since this is a
mass bug filing (due to so many packages em
Package: ggobi
Severity: grave
Tags: security
Hi,
The following CVE (Common Vulnerabilities & Exposures) id was
published for libtool. I have determined that this package embeds a
vulnerable copy of the libtool source code. However, since this is a
mass bug filing (due to so many packages embed
Package: graphicsmagick
Severity: grave
Tags: security
Hi,
The following CVE (Common Vulnerabilities & Exposures) id was
published for libtool. I have determined that this package embeds a
vulnerable copy of the libtool source code. However, since this is a
mass bug filing (due to so many packa
Package: graphviz
Severity: grave
Tags: security
Hi,
The following CVE (Common Vulnerabilities & Exposures) id was
published for libtool. I have determined that this package embeds a
vulnerable copy of the libtool source code. However, since this is a
mass bug filing (due to so many packages em
Package: gnu-smalltalk
Severity: grave
Tags: security
Hi,
The following CVE (Common Vulnerabilities & Exposures) id was
published for libtool. I have determined that this package embeds a
vulnerable copy of the libtool source code. However, since this is a
mass bug filing (due to so many packag
Package: freeradius
Severity: grave
Tags: security
Hi,
The following CVE (Common Vulnerabilities & Exposures) id was
published for libtool. I have determined that this package embeds a
vulnerable copy of the libtool source code. However, since this is a
mass bug filing (due to so many packages
Package: hamlib
Severity: grave
Tags: security
Hi,
The following CVE (Common Vulnerabilities & Exposures) id was
published for libtool. I have determined that this package embeds a
vulnerable copy of the libtool source code. However, since this is a
mass bug filing (due to so many packages embe
Package: dico
Severity: grave
Tags: security
Hi,
The following CVE (Common Vulnerabilities & Exposures) id was
published for libtool. I have determined that this package embeds a
vulnerable copy of the libtool source code. However, since this is a
mass bug filing (due to so many packages embedd
Package: gnash
Severity: grave
Tags: security
Hi,
The following CVE (Common Vulnerabilities & Exposures) id was
published for libtool. I have determined that this package embeds a
vulnerable copy of the libtool source code. However, since this is a
mass bug filing (due to so many packages embed
Package: google-gadgets
Severity: grave
Tags: security
Hi,
The following CVE (Common Vulnerabilities & Exposures) id was
published for libtool. I have determined that this package embeds a
vulnerable copy of the libtool source code. However, since this is a
mass bug filing (due to so many packa
Package: bochs
Severity: grave
Tags: security
Hi,
The following CVE (Common Vulnerabilities & Exposures) id was
published for libtool. I have determined that this package embeds a
vulnerable copy of the libtool source code. However, since this is a
mass bug filing (due to so many packages embed
Package: collectd
Severity: grave
Tags: security
Hi,
The following CVE (Common Vulnerabilities & Exposures) id was
published for libtool. I have determined that this package embeds a
vulnerable copy of the libtool source code. However, since this is a
mass bug filing (due to so many packages em
Package: arts
Severity: grave
Tags: security
Hi,
The following CVE (Common Vulnerabilities & Exposures) id was
published for libtool. I have determined that this package embeds a
vulnerable copy of the libtool source code. However, since this is a
mass bug filing (due to so many packages embedd
Package: camserv
Severity: grave
Tags: security
Hi,
The following CVE (Common Vulnerabilities & Exposures) id was
published for libtool. I have determined that this package embeds a
vulnerable copy of the libtool source code. However, since this is a
mass bug filing (due to so many packages emb
Package: courier-authlib
Severity: grave
Tags: security
Hi,
The following CVE (Common Vulnerabilities & Exposures) id was
published for libtool. I have determined that this package embeds a
vulnerable copy of the libtool source code. However, since this is a
mass bug filing (due to so many pack
Package: cvsnt
Severity: grave
Tags: security
Hi,
The following CVE (Common Vulnerabilities & Exposures) id was
published for libtool. I have determined that this package embeds a
vulnerable copy of the libtool source code. However, since this is a
mass bug filing (due to so many packages embed
Hi,
basilisk2 was already spotted once as being in a very bad shape[1]. It
is currently only built on a few architectures[2], and has been
FTBFSing for 1.5 year[3]. Riky is also wondering[4].
1. http://bugs.debian.org/cgi-bin/bugreport.cgi?msg=45;bug=309501
2. https://buildd.debian.org/status/p
On Sun, Dec 06, 2009 at 10:16:37PM -0500, Joseph Spiros wrote:
> Yes, it is line 23 that fails. I reverted my find+touch "fix", purged,
> ensured that /usr/lib/pymodules/python2.5/coherence and
> /usr/share/pyshared/coherence no longer existed before reinstalling the
> python-coherence package to o
Package: libtool
Severity: grave
Tags: security
Hi,
The following CVE (Common Vulnerabilities & Exposures) id was
published for libtool.
CVE-2009-3736[0]:
| ltdl.c in libltdl in GNU Libtool 1.5.x, and 2.2.6 before 2.2.6b,
| attempts to open a .la file in the current working directory, which
| al
Cyril Brulebois (07/12/2009):
> Its ./configure now runs fine. Using “block” accordingly.
And the next blocker, at least on kfreebsd-i386 is:
| make[3]: Entering directory
`/srv/storage/kibi/hack/code-saturne-2.0.0.beta2/gui/Base'
| failed to find pyuic4; tried ./pyuic4
| failed to find pyrcc4;
block 557020 by 559794
thanks
Cyril Brulebois (07/12/2009):
> Please find attached a patch to fix those. I didn't use the .la's
> since they're Evil©®™, but more importantly since not all libraries
> you're using provide one. (Of course, automake helps getting
> src/Makefile.in in line.)
I obvio
Processing commands for cont...@bugs.debian.org:
> block 557020 by 559794
Bug #557020 [code-saturne] FTBFS: Fails to find fvm.
Was not blocked by any bugs.
Added blocking bug(s) of 557020: 559794
> thanks
Stopping processing here.
Please contact me if you need assistance.
Debian bug tracking sys
Package: libfvm-dev
Version: 0.14.0-2
Severity: serious
Tags: patch
Justification: Broken shared objects
Hi,
as discussed quickly in #557020, libfvm might have some undefined
references. So I added -Wl,-z,defs to CFLAGS, and then noticed 900+
undefined references.
Please find attached a patch to
Your message dated Mon, 07 Dec 2009 03:51:07 +
with message-id
and subject line Bug#527732: fixed in orpie 1.5.1-7.1
has caused the Debian Bug report #527732,
regarding orpie: FTBFS: (.data+0x2c0): undefined reference to
`ml_gsl_vector_float_minmaxindex'
to be marked as done.
This means that
Your message dated Mon, 07 Dec 2009 03:50:31 +
with message-id
and subject line Bug#540669: fixed in kflickr 0.9.1-2.2
has caused the Debian Bug report #540669,
regarding kflickr: FTBFS: `.libs/libkflickrpart.so': No such file or directory
to be marked as done.
This means that you claim that
severity 559776 normal
thanks
On Mon, Dec 07, 2009 at 01:08:12AM +, peter green wrote:
> package: e2fsprogs
> severity: critical
> justification: breaks the entire system
Your system is broken already because it doesn't have a usable RTC.
Having correct system time is important! Indeed, ther
Your message dated Mon, 07 Dec 2009 03:50:08 +
with message-id
and subject line Bug#554638: fixed in jconv 0.8.1-1.1
has caused the Debian Bug report #554638,
regarding jconv_0.8.1-1(ia64/unstable): FTBFS: build-depnds libc6-dev
to be marked as done.
This means that you claim that the problem
Processing commands for cont...@bugs.debian.org:
> severity 559776 normal
Bug #559776 [e2fsprogs] fsck now considers last mount time in the future to be
an error causing boot failure on systems without a usable rtc
Severity set to 'normal' from 'critical'
> thanks
Stopping processing here.
Plea
Your message dated Mon, 07 Dec 2009 03:49:44 +
with message-id
and subject line Bug#552677: fixed in heimdal 1.3.1.dfsg.1-2
has caused the Debian Bug report #552677,
regarding heimdal: FTBFS: rm: cannot remove
`debian/heimdal-docs/usr/share/info/dir': No such file or directory
to be marked as
Your message dated Mon, 07 Dec 2009 03:50:08 +
with message-id
and subject line Bug#540427: fixed in jconv 0.8.1-1.1
has caused the Debian Bug report #540427,
regarding jconv: Build-Depends on libc6-dev (>= 2.7)
to be marked as done.
This means that you claim that the problem has been dealt w
Hi,
The proposed patch only modifies the get_interface_dist function, but whatever
this function returns is looked up in another dict. Since the patch returns
"debian" there it should be a definition in the other dict (in
get_interface_parse_table, and get_interface_replace_table) for "debian".
Package: libgnucrypto-java
Version: 2.1.0-2
Severity: grave
Tags: security
Hi,
the following CVE (Common Vulnerabilities & Exposures) id was
published for classpath. libgnucrypto-java embeds classpath, so it is
also affected.
CVE-2008-5659[0]:
| The gnu.java.security.util.PRNG class in GNU Class
Processing commands for cont...@bugs.debian.org:
> tag 527732 pending
Bug #527732 [orpie] orpie: FTBFS: (.data+0x2c0): undefined reference to
`ml_gsl_vector_float_minmaxindex'
Added tag(s) pending.
> tag 550058 pending
Bug #550058 [orpie] uses convenience copy of ocamlgsl
Added tag(s) pending.
>
tag 527732 pending
tag 550058 pending
thanks
Richard Darst (16/11/2009):
> I recently looked at FTBFS bug #527732, and eventually fixed it (I
> don't know ocaml that well). In the process, I also fixed #550058,
> which is using a convenience copy of the Gnu Scientific Library.
Hi Richard.
Real
Oh, I should probably note that despite the UserWarning that appears
regardless of my "fix", the last log entry resulted in a working UPnP
server that I was able to access with my Playstation 3.
(P.S. - If you are wondering about the inconsistency, I tend to edit my
prompt to a single "$" when I p
Package: php4
Version: 6:4.4.4-8
Severity: serious
Tags: security
Hi,
the following CVE (Common Vulnerabilities & Exposures) id was
published for php4.
CVE-2008-5624[0]:
| PHP 5 before 5.2.7 does not properly initialize the page_uid and
| page_gid global variables for use by the SAPI php_getuid f
Yes, it is line 23 that fails. I reverted my find+touch "fix", purged,
ensured that /usr/lib/pymodules/python2.5/coherence and
/usr/share/pyshared/coherence no longer existed before reinstalling the
python-coherence package to obtain this log:
> $ coherence
> Traceback (most recent call last):
>
tag 554638 patch pending
tag 540427 patch pending
thanks
Please find attached the patch for my NMU, uploaded to DELAYED/0 given
the current number of FTBFS and the current number of months without
a single reply.
Mraw,
KiBi.
diff -u jconv-0.8.1/debian/changelog jconv-0.8.1/debian/changelog
--- jc
Processing commands for cont...@bugs.debian.org:
> tag 554638 patch pending
Bug #554638 [jconv] jconv_0.8.1-1(ia64/unstable): FTBFS: build-depnds libc6-dev
Added tag(s) pending and patch.
> tag 540427 patch pending
Bug #540427 [jconv] jconv: Build-Depends on libc6-dev (>= 2.7)
Added tag(s) pending
Package: ktoon
Version: 0.8.1-4
Severity: serious
Justification: FTBFS
Hi,
when trying to build with the attached patch to fix #527721, one
encounters new issues, since ffmpeg/*.h went away, and are now
replaced by new paths. I then tried the attached patch, but given
the ffmpeg API changed, it s
Package: libpam-heimdal
Version: 3.15-2
Severity: critical
Justification: breaks the whole system
After updating to the current Heimdal packages, at the next boot,
everything broke - su, login, cron, etc regressing to the testing
level of heimdal packages makes everything work again.
The mi
Kurt Roeckx (15/08/2009):
> Source: kde-style-qtcurve
> Version: 0.65.1-1
> Severity: serious
I believe I found the issue: config.h's line 6 is about prefix. As can
be seen in a cowbuilder build log:
| -- Found automoc4: /usr/bin/automoc4
| ** PREFIX=/usr
| -- Configuring done
| -- Generating don
Package: ghostscript
Version: 8.62.dfsg.1-3.2lenny1
Severity: serious
Tags: security
Hi,
the following CVE (Common Vulnerabilities & Exposures) ids were
published for jasper. Ghostscript embeds jasper in lenny embeds
jasper, and statically links to jasper in unstable (so it needs to be
rebuilt).
Processing commands for cont...@bugs.debian.org:
> tag 540669 patch pending
Bug #540669 [kflickr] kflickr: FTBFS: `.libs/libkflickrpart.so': No such file
or directory
Added tag(s) pending and patch.
> thanks
Stopping processing here.
Please contact me if you need assistance.
Debian bug tracking
tag 540669 patch pending
thanks
Ilya Barygin (14/10/2009):
> Here's the fix, applied in Ubuntu
> (see https://bugs.launchpad.net/ubuntu/+source/kflickr/+bug/451316)
ACK.
> Also, it makes sense to enable building with automake 1.11:
Yeah. :)
Thanks. Next time, you could even tag the bugreport
Processing commands for cont...@bugs.debian.org:
> retitle 559747 zita-convolver: must not use -march=native
Bug #559747 [zita-convolver] FTBFS: unrecognized command line option
"-march=native"
Changed Bug title to 'zita-convolver: must not use -march=native' from 'FTBFS:
unrecognized command li
retitle 559747 zita-convolver: must not use -march=native
thanks
zita-convolver appears to be using -march=native , there are two
problems with this
1: It's not supported on most debian architectures (hence a load of
build failures)
2: Even on architectures where it is supported it's totally
Hello,
I have been able to reproduce this bug. I think installing xfonts-100dpi or
xfonts-75dpi should fix it. Could you please confirm that ?
Thanks,
Vincent
--
To UNSUBSCRIBE, email to debian-bugs-rc-requ...@lists.debian.org
with a subject of "unsubscribe". Trouble? Contact listmas...@lists
package: e2fsprogs
severity: critical
justification: breaks the entire system
When booting my quemu armel system I get the following
Checking root file system...fsck from util-linux-ng 2.16.1
/dev/sda1: Superblock last mount time (Thu Jan 1 01:03:11 1970,
now = Thu Jan 1 01:00:52 1970)
1 - 100 of 230 matches
Mail list logo
