On 2/15/11 7:21 AM, Adrian Knoth wrote:
> Hi!
>
> I've built a debug version of librdf and found the following code:
>
> librdf_parser_raptor_constructor (world=0x877e5a0) at
> rdf_parser_raptor.c:1328
> 1328syntax_name = desc->names[0];
> (gdb) bt
> #0 librdf_parser_raptor_constructor (
This clearly shouldn't have been uploaded until raptor2 was accepted into
sid (1 month waiting), which is a dependency. I built it against my own
local copy. Not sure how to resolve it now.
Dave
--
To UNSUBSCRIBE, email to debian-bugs-rc-requ...@lists.debian.org
with a subject of "unsubscrib
Your package builds a PHP extension but doesn't depend on phpapi-*.
This is incorrect and will break it on PHP transitions, such as the
soon-to-come PHP 5.3 transition.
Why is it incorrect and where was this announced and documented? You
should have filed a wishlist or lower priority bug wel
Adrian Knoth wrote:
> On Sat, Dec 19, 2009 at 05:02:21PM +0100, hungerburg wrote:
>
> Hi!
>
>> the last time I used ardour two days ago. I believe it was
>> 1:2.8.4-1 - today after updating to 1:2.8.4-2 I can no longer
>> launch the application. A downgrade does not help. Maybe its
>> because a f
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
The package is not as you put "useless".
Yes, the libxml2-dev dependency needs adding but otherwise, it's still 1
line to compile a program against flickcurl:
gcc -o prog prog.c `pkg-config flickcurl --cflags` `pkg-config flickcurl --libs`
and that *does* include the right include line.
flickcu
If you are compiling against redland correctly you have two choices
to set up the compile flags correctly
either a)
$ redland-config --cflags
-I/usr/include/rasqal
(which uses the program /usr/bin/redland-config in librdf0-dev)
or b)
$ pkg-config redland --cflags
-I/usr/include/rasqal
(which uses
Michael Biebl wrote:
> Hi Dave,
>
> could you please comment on this issue and if you'd be willing to compile
> libraptor against libcurl-gnutls.
Sure, it's only used to get https urls working. I don't care which library
implements that. I haven't tested it but assume it works.
Dave
--
To
The patch looks OK although I cannot test any directfb stuff, or do
any cairo work today.
One reason the directfb was NOT enabled in the main cairo package
by me is that it is unsupported upstream. The customer for debian
is really just the installer, so limiting the packages for that
was a goal,
Otavio Salvador wrote:
notfound 1.4.14-1
found 1.5.6-1
thanks
I've been able to reproduce the issue outside d-i environment, using
cdebconf, and this allowed me to test with previous available versions
of package.
I figure that, of available packages, the first to show this issue is
1.5.6-1 whi
Marc 'HE' Brockschmidt wrote:
> tags 422388 + fixed-upstream
> thanks
>
> Heya,
>
> Marc 'HE' Brockschmidt <[EMAIL PROTECTED]> writes:
>> Lucas Nussbaum <[EMAIL PROTECTED]> writes:
>>> During a rebuild of all packages in sid, I discovered that your package
>>> failed to build on i386.
>> After so
Brian M. Carlson wrote:
> Is this bug still relevant? ikvm has successfully built on amd64 since
> this bug was filed, and it works on my amd64 machine. ISTR that some
> bug was present in Mono a few months ago, and that might have affected
> the build environment.
I've never had it working, and
Shawn K. Quinn wrote:
> Package: tomboy
> Version: 0.4.1-2
> Severity: grave
> Justification: renders package unusable
>
>
> After recent upgrades, tomboy crashes on start:
> ...
It worked for me when I built it.
Why don't you try 0.5.0 in experimental at
http://ftp.debian.org/debian/pool/mai
Loic Dachary wrote:
> Thanks for the explanation. I'm confused though because
> apt-cache show claims support for python2.3. Any idea why this is so ?
When I built it, there might have been support for python2.3. Although
I haven't changed anything, the python defaults have changed, so th
Andrey Fedoseev wrote:
> Package: tomboy
> Version: 0.4.1-2
> Severity: grave
> Justification: renders package unusable
>
...
> When trying to run tomboy I get:
>
> [START]
> ** ERROR **: file threadpool.c: line 990 (mono_thread_pool_init):
> assertion failed: (async_call_klass)
> aborting...
Jérémy Bobbio wrote:
> On Sat, Oct 07, 2006 at 03:40:43PM -0700, Dave Beckett wrote:
>>> I can reproduce this bug. I also tried to build pan against a libcairo2
>>> with the patch presented in #383034 and it still crash.
>>>
>>> The backtrace is totally unh
Jérémy Bobbio wrote:
> Hi!
>
> I can reproduce this bug. I also tried to build pan against a libcairo2
> with the patch presented in #383034 and it still crash.
>
> The backtrace is totally unhelpfull, though. :(
I agree it isn't. It must have been corrupted before you got
the crash. Maybe t
Looking at the end of the backtrace:
Core was generated by `pan'.
Program terminated with signal 11, Segmentation fault.
#0 0xb79281f9 in cairo_xlib_surface_get_display () from /usr/lib/libcairo.so.2
#1 0xb790d7b1 in cairo_surface_reference () from /usr/lib/libcairo.so.2
#2 0xb7901fdc in cairo_
Toufeeq Hussain wrote:
> Subject: libcairo2: GNOME app's fail to start
> Package: libcairo2
> Version: 1.2.4-1
> Severity: critical
> Justification: breaks unrelated software
>
> *** Please type your report below this line ***
>
> All GNOME app's fail to start. They quit with the following error:
Please report this information as soon as possible. The very same thing
has been reported previous times and it was always a local configuration
problem with out of date freetype.
See http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=325526 for what I mean
and tests you can try.
I will downgrade
Adeodato Simó wrote:
> unmerge 377147
> retitle 377147 libcairo 1.2.0: regression: gtk apps are not anti-aliased if
> anti-aliasing is disabled in ~/.qt/qtrc
> notforwarded 377147
> unblock 377879 by 377147
> unblock 379482 by 377147
>
> retitle 376714 libcairo 1.2.0 text disappears after first w
Loïc Minier wrote:
> Package: libcairo2-dev
> Version: 1.2.0-2
> Severity: serious
>
> Hi,
>
> #377234 was just filed against gnome-keyring which uses libtool and
> pkg-config --libs gtk+-2.0 to build. libtool sees the -lcairo from
> this command and includes the dependency_libs of li
Luk Claes wrote:
> Hi
>
> Attached the patch for the version I uploaded. Please respond if
> you think that the attached patch won't work.
It will work. This fix is in the redland 1.0.3 build which has been
stuck in the "new queue" for 7 days+ now and closes this bug.
Dave
--
To UNSUBSCRIBE,
Javier Kohen wrote:
> Package: muine
> Version: 0.8.4-1
> Severity: serious
> Justification: It allows itself to be installed with an incompatible library
>
> I just upgraded to dbus-0.61, ...
I think you've found the problem.
> ii libdbus-1-cil0.61-2 CLI binding for D-BUS
Regis Boudin wrote:
> Package: librdf0-dev
> Version: 1.0.2-2
> Severity: grave
>
> Hi,
>
> Trying to build Amaya using the system librdf fails because the
> raptor_locator type is not defined in rdf_log.h
>
> To fix this, I suppose rdf_log.h should include raptor.h
You should never include rdf
On Wed, 2006-02-08 at 16:57 -0500, Benjamin Seidenberg wrote:
> Package: muine
> Version: 0.8.3-8
> Severity: grave
> Justification: renders package unusable
>
> Muine fails to start after freshly being installed on my system.
>
> [EMAIL PROTECTED]:~$ muine
>
> ** (muine:19775): WARNING **: No
"When muine jumped the gun on gtk-sharp2 2.3.91, it did so only for
i386; on other architectures, the autobuilders naturally continued to
use 1.9.5. ..."
nope. It requires gtk-sharp2 1.9.2+ and was uploaded with that
dependency in the build which is recorded in, for example, the i386 deb.
Any 2.
severity 333259 normal
thanks
As of curl 7.15.0-3, libcurl3-dev has been restored so libraptor1-dev is
buildable from source again now (I checked, with a sid pbuilder
build).
This bug is thus not severe anymore, but the dependency can be updated at
next upload to pick one of libcurl3-gnutls or l
Yes, the postscript, PDF and OpenGL backends were removed at cairo 1.0.0
after upstream made them unsupported (for now) and the pycairo bindings
need a rebuild to reflect that.
Dave
signature.asc
Description: This is a digitally signed message part
On Fri, 2005-08-12 at 10:30 -0700, Matt Kraai wrote:
> Package: byacc
> Version: 20050505-1
> Severity: serious
>
> groff fails to build from source because byacc generates an incomplete
> declaration of YYSTYPE in the header file. The first attachement
> contains the header file it generates. T
poppler is still depending on a libcairo binary removed some time ago.
libcairo0.6.0{,dev} are the packages for latest cairo version 0.6.0 that
I've just added to sid (I'm the cairo maintainer). Upstream cairo
developers are heading for 1.0 and a stable API "soon" so there will
definitely be more
Package: fakeroot
Version: 1.4
Severity: grave
Justification: renders package unusable
The fakeroot scripts do not have the #! prefix before the path.
This causes fakeroot to invoke a shell, waiting for user response (^D
/ exit) before actually running the program requested.
$ mkdir foo
$ cd
On Sun, 29 May 2005, Kurt Roeckx wrote:
> Package: ikvm
> Version: 0.14.0.1-2
> Severity: serious
> Tags: experimental
>
> Hi,
>
> When only building the architecture specific .debs, it fails to
> build because "binary-arch" does nothing. Just running
> dpkg-buildpackage -B has this effect.
Pleas
On Sun, 03 Apr 2005 00:01:04 +0200
Joergen Scheibengruber <[EMAIL PROTECTED]> wrote:
> Subject: muine: Puhulease fix this bug :)
> Followup-For: Bug #300541
> Package: muine
> Version: 0.6.3-7
>
> I experience this bug, too. It's very annoying :(
> Could you please look into this?
It seems there
On Tue, 2005-03-22 at 15:25 -0500, Jeff Licquia wrote:
> Package: python2.3-librdf
> Version: 1.0.0.2-1
> Tags: sarge, sid
> Severity: grave
> Justification: renders package unusable
>
> [EMAIL PROTECTED]:~$ python
> Python 2.3.4 (#2, Dec 3 2004, 13:53:17)
> [GCC 3.3.5 (Debian 1:3.3.5-2)] on linu
On Sun, 2005-03-20 at 22:01 +0200, Gintautas Miliauskas wrote:
> Package: muine
> Version: 0.6.3-7
> Followup-For: Bug #300541
>
> I am experiencing the same problem. It appears that I can't even downgrade
> easily because the version in testing is the same as in unstable.
There is no version of
36 matches
Mail list logo
