Package: wnpp
Severity: wishlist
Owner: Dave Beckett
Package name: nghttp2
Version : 0.2.0
Upstream Author : Tatsuhiro Tsujikawa
URL : http://tatsuhiro-t.github.io/nghttp2/
License : MIT/X
Programming Lang: C
Description : HTTP/2 library
A
"Starting with the 6.0 / 12c releases, all Berkeley DB products are licensed
under the GNU AFFERO GENERAL PUBLIC LICENSE (AGPL), version 3."
--
http://docs.oracle.com/cd/E17076_03/html/installation/license_change60.html
This probably means that some things cannot link with db6.0 and so will have
That option was removed from raptor's configure some time ago, it
just generates a warning and has no new effect since libxml2 is now
the only choice.
Dave
On Mon, 10 Sep 2012, Jonathan Nieder wrote:
Dave Beckett wrote:
There are no more changes coming for 2.0.8
I didn't real
On 9/8/12 1:58 PM, Jonathan Nieder wrote:
> Dave Beckett wrote:
>
>>* debian/control: add a breaks relation by libraptor2-0 against squeeze
>> libraptor1 to force upgrades to a version with symbol versioning
>> (Closes: #656928)
>>* Added debi
I read the description but I don't think I can attempt to reproduce
or diagnose this. I need steps like: install this package, type this
Thanks
Dave
--
To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org
with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian
This is a documentation bug. -m strict was removed from rapper as
part of the Raptor V2 work. It's replacement is -f strict=true
(default is -f strict=false)
I will update the help message
Dave
--
To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org
with a subject of "unsubscri
There's a version 1.10.0 out now (9 May 2011). I intend to package that
instead of the 1.9.x series. Can you check if that is ok for gtkmm3.0
Thanks
Dave
--
To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org
with a subject of "unsubscribe". Trouble? Contact listmas...@list
> You'll get "good enough" symbol versions by adding
> LDFLAGS += -Wl,--default-symver
I can try this but I'm skeptical it will fix the essential problem - two
versions of the same library in the same memory space. It's not just
symbols, it's that they will attempt to use and control the same res
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 (
On 2/15/11 7:12 AM, Frederic Peters wrote:
> Dave Beckett wrote:
>
>> An aside at Ardour:
>> If I look in sid at ardour, it says:
>> Build-Depend:
>> ... libraptor1 (>= 1.4.19), librasqal2 (>= 0.9.18), librdf0 (>= 1.0.9),
>>
>> which is shortly g
On 1/21/10 3:51 AM, Benjamin Scherrer wrote:
> Hi,
>
> I also asked at the Ardour forums about this problem.
> (http://ardour.org/node/3287)
>
> As advices there, a quick
> ln -s /usr/lib/librasqal.so.2 /usr/lib/librasqal.so.1
> as root solved my problems.
That seems indicates ardour must have b
On 1/21/10 2:26 AM, Benjamin Scherrer wrote:
> Hi,
>
> this bug seems to be still active to me. I'm up to date on Debian
> testing amd64 with the versions:
>
> ardour 2.8.4-3
> librdf0 1.0.10-1
> librdf0-dev 1.0.10-1
> librasqal2 0.9.17-1
> librasqal2-dev 0.9.17-1
>
> But I still get this consol
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-dist-requ...@lists.debian.org
with a subject of "unsubscr
I applied Kjetil's patch and made some other changes to give 1.0.3-2
at http://download.dajobe.org/debian/unstable/
4store (1.0.3-2) unstable; urgency=low
.
* debian/control: Build-Depend: on libavahi-client-dev and libavahi-glib-dev
to get mDNS enabled
* set initial KB to 'default'
I made a test package of 4store 1.0.3 (latest release) at
http://download.dajobe.org/debian/unstable/
Based on a much derived version of some earlier work.
It builds and is relatively lintian clean but I haven't tested it.
It makes a new user 'fourstore' but I've just remembered it still starts
The links here don't seem recent and working but if there are some packages
in a reasonable state, I'll take a look.
Dave
--
To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org
with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org
On Fri, 7 May 2010, Jari Aalto wrote:
In that case, would you like to file the removal request to ftp masters
or is it okay if I do it?
Thanks for keeping Debian archives in shape,
Jari
Go ahead and file it
Dave
--
To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org
with a
At the time of your email 1.8.4 had been packaged and installed for 6 days.
The 1.8.4-2 has a critical fix and it's uploading now. 10 days after that
reaches unstable, it'll migrate to testing and this bug will become out of
date and I'll close it.
Dave
--
To UNSUBSCRIBE, email to debian-bug
See subject
Dave
--
To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org
with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org
One more vote for a new version - some software I want to use needs this.
Thanks
Dave
--
To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org
with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org
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
reassign 523043 liblrdf
forcemerge 521898 523043
done
fixing previous reassignment - liblrdf != librdf
--
To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org
with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org
FYI the next release of redland 1.0.9 has the dynamic loading storages
enabled so that means the packages can be adjusted to have just a core with
the simple storages (sqlite, bdb, files) separate from packages for the
relational backends (mysql, postgresql, others in future).
I'm just noting this
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
Mark Hedges wrote:
> The latest libcairo2_1.6.4-6.1 did not contain this fix. I
> had to downgrade using your packages.
>
> Any chance your patch to libcairo2_1.6.4-6.0.1 can make it
> into the next upgrade?
I don't now where "this fix" that was in Mike's build called
libcairo2_1.6.4-6.0.1 came
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,
Mike Hommey said:
> Looks like it's happening in cairo.
>> #6 0xb7241e2d in nsProfileLock::FatalSignalHandler (signo=11) at
nsProfileLock.cpp:216
>> #7
>> #8 cairo_draw_with_xlib (cr=0xbc55ff8, callback=0xb79c4698
, closure=0xbfea8c40, dpy=0x0, width=560, height=228,
is_opaque=CAIRO_XLIB_DRAWIN
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
Package: wnpp
Severity: normal
I request an adopter for the nant package as I no longer use
or have interest in .NET/mono.
The package description is:
NAnt is different. Instead of a model where it is extended with
shell-based commands, NAnt is extended using task classes. Instead of
writin
Package: wnpp
Severity: normal
I intend to orphan the ikvm package.
To any future maintainer:
There are lots of packaging problems that ikvm 0.36.0.5 have
including needing extra source packages, plus licensing concerns of
combining OpenJDK, Classpath and IKVM code, some of which is only
avail
... libcurl4-openssl-dev, which conflicts with several other packages...
I can imagine both versions clash with other packages. Can you provide
some more specific details to pick one over the other?
Dave
--
To UNSUBSCRIBE, email to [EMAIL PROTECTED]
with a subject of "unsubscribe". Trouble?
Package: ftp.debian.org
Severity: normal
Please remove the following packages from unstable (all architectures):
libpixman1 - Cairo pixel manipulation library
libpixman1-dev - Cairo pixel manipulation library development libraries and
headers
which are generated from the libpixman source packa
The cairo upstream bug for this:
http://bugzilla.gnome.org/show_bug.cgi?id=359243
claims it was fixed in cairo 1.2+ series which was a long time ago.
Attilio: can you check since you knew of the workaround?
Dave
--
To UNSUBSCRIBE, email to [EMAIL PROTECTED]
with a subject of "unsubscribe".
This is cairo bug
https://bugs.freedesktop.org/show_bug.cgi?id=9719
Dave
--
To UNSUBSCRIBE, email to [EMAIL PROTECTED]
with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
> Program received signal SIGFPE, Arithmetic exception.
> [Switching to Thread 0xb6d996b0 (LWP 4198)]
> 0xb725dcd2 in _get_bitmap_surface (bitmap=0x83efe34, own_buffer=0,
> font_options=0x844d358, surface=0xbfcfe02c)
> at /home/slomo/projects/debian/tmp/libcairo-1.4.10/src/cairo-ft-font.c:7
>Firefox stopped displaying some pages correctly on updating from
>libcairo2 version 1.4.10-1 .
>Some text is missing. Downgrading helps
>
>Sample pages:
>www.debian.org
Never was able to duplicate this - far too vague.
Please try 1.4.10-1.3 and see if that fixed what you saw.
Otherwise, pro
Nico Golde wrote:
> Hi Gabor,
> * Gabor Gombas <[EMAIL PROTECTED]> [2007-12-11 15:02]:
>> On Tue, Dec 11, 2007 at 02:46:59PM +0100, Nico Golde wrote:
>>
>>> I did not forget it, it was attached by the one who replied
>>> to this bug before me :)
>> Hmm, that mail did not reach me for some reason.
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
Kumar Appaiah wrote:
> Package: wnpp
> Severity: wishlist
> Owner: Kumar Appaiah <[EMAIL PROTECTED]>
>
>
> * Package name: flickcurl
> Version : 0.11
> Upstream Author : Dave Beckett <[EMAIL PROTE
Rene Engelhard wrote:
> Package: wnpp
> Severity: wishlist
> Owner: Rene Engelhard <[EMAIL PROTECTED]>
>
> * Package name: libsvg
> Version : 0.1.4
> Upstream Author : Carl Worth <[EMAIL PROTECTED]>
> * URL : http://cairographics.org/snapshots/
> * License : LGP
Jérémy Bobbio wrote:
> Package: libcairo
> Version: 1.4.6-1.1
> Severity: important
>
> Hi!
>
> libcairo2 and libcairo-directfb2 .shlibs files disagree on which
> dependencies should be used for udebs:
>
> * /var/lib/dpkg/info/libcairo2.shlibs
>
> libcairo 2 libcairo2 (>=1.4.0)
> udeb
Michael Biebl wrote:
> Package: librdf0-dev
> Severity: normal
>
> Currently librdf builds and links against libdb4.3, librfd0-dev depends
> on libdb4.3-dev.
> Unfortunately, most of the other packages, like libsvn were built against
> db4.4, and
> the -dev packages of libsvn can't be installed i
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
Guus Sliepen wrote:
> Package: libcairomm-1.0-dev
> Version: 0.6.0-4
> Severity: important
>
> Hello, upstream has released cairomm 1.2.4 on January 17, 2007. Please
> update the Debian package. I set the severity to important, because the
> latest version of gtkmm also depends on cairomm >= 1.2.0
Dirk Haage wrote:
> Dave Beckett wrote:
>> On Fri, 27 Apr 2007, Dirk Haage wrote:
>>> Package: libcairo2
>>> Version: 1.4.4-1
>>> Severity: important
>>>
>>>
>>> when version 1.4.4-1 of libcairo2 is installed, Azureus is not able
&g
On Fri, 27 Apr 2007, Dirk Haage wrote:
Package: libcairo2
Version: 1.4.4-1
Severity: important
when version 1.4.4-1 of libcairo2 is installed, Azureus is not able to start:
Error: Cairo 1.4.4 does not yet support the requested image format:
Depth: 32
Alpha mask: 0x
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
On Fri, 16 Feb 2007, Jerome Blondel wrote:
Package: libcairo2
Version: 1.2.4-4
# LANG=en apt-get -s install libcairo2
Reading Package Lists... Done
Building Dependency Tree... Done
Some packages could not be installed. This may mean that you have
requested an impossible situation or if you ar
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
Jeroen Pulles wrote:
> Package: python-librdf
> Version: 1.0.4.1-2
> Severity: normal
>
> Hi Dave,
>
> "import RDF" fails because RDF.py is not in the modules path.
> RDF.py is available in the pycentral/python-librdf/site-packages
> directory. I can't find any (byte-compiled) copies or symlink
On Tue, 31 Oct 2006, jetxee wrote:
Package: tomboy
Version: 0.4.1-1
Severity: normal
After upgrade from 0.3.3-3 to 0.4.1-1 tomboy does not start any more.
It seems like a broken dependency on mono, but all dependencies are
satisfied. The stderr output of the programme follows:
...
Versions
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
Jesse Alec Wolfe wrote:
> This bug affects my system, too. It still occurs in the most recent
> unstable (0.8.5-1.1). I spoke to the developers in #muine, and they
> tell me that this issue is fixed in CVS. (until then, Muine is nearly
> unusable: can we get a pre-release package in experimental? h
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_
Nigel: you say:
I connect to my Debian system from OS X (latest) using 'ssh -Y'. Using
gdb & xsane, I get: [crash]
when I do the same from OSX, it works just fine but does nothing
since I don't have a scanner.
I probably can't test things like:
dimensions:3120x1050 pixels (1055x355 mill
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:
Marcelo Monteiro wrote:
> I was idem problem.
>
> I use vncserver and gtk application crash with 1.2.2.
>
> When I downgrade to 1.0.4 everything works fine.
Please can you give more information on your X setup. What
does xdpyinfo show?
Also note there are bugs with 8-bit displays not fixed ups
Nigel Johnston wrote:
> I've just been trying to run various GTK based apps and they all fail in
> the same place - cairo_xlib_surface_get_display(), so I guess I've got
> the same problem.
>
> I connect to my Debian system from OS X (latest) using 'ssh -Y'. Using
> gdb & xsane, I get:
So it's no
Emil Nowak wrote:
> Package: libcairo2
> Version: 1.2.2-1
> Severity: normal
>
> I'm using ssh X11Forwarding to run applications remotely from other machines.
> As long as I remember it worked well.
>
> But with the current libairo every gtk application crashes on startup on
> cairo_xlib_surface
Loïc Minier wrote:
> tag 383297 + patch
> stop
>
> Hi,
>
> On Wed, Aug 16, 2006, Loïc Minier wrote:
>> I've rebuilt libcairo (with a newer directfb snapshot too, see #383238)
>> with these flags, and Gtk 2.10 now links fine.
>
> I've confirmed this also works with unstable's DirectFB.
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
Oliver Jato wrote:
> hello,
>
> the file seems to be okay:
...
> flyricky:/home/olli# cat > foo.c
> main() { FT_GlyphSlot_Embolden(); }
> flyricky:/home/olli# less foo.c
> flyricky:/home/olli# gcc -o foo foo.c -lcairo
> flyricky:/home/olli# ./foo
> flyricky:/home/olli#
so in terms of this bug, i
The antialiasing problem seems to be caused by the KDE bug mentioned in
the cairo bug https://bugs.freedesktop.org/show_bug.cgi?id=7494
[[
I think I've figured out what was all this about, and it's not cairo's
fault. In fact, it's been a fix on cairo
(http://gitweb.freedesktop.org/?p=cairo;a=comm
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
stall ok installed
> Priority: optional
> Section: libs
> Installed-Size: 676
> Maintainer: Dave Beckett <[EMAIL PROTECTED]>
> Architecture: i386
> Source: libcairo
> Version: 1.2.0-3
> Replaces: libcairo0.5.1, libcairo0.6.0, libcairo0.9.0, libcairo1
> Pr
This seems more like a compiler problem, the mathcalls.h lines are
things like:
extern double y1 (double) __attribute__ ((__nothrow__)); extern double
__y1 (double) __attribute__ ((__nothrow__));
(after pre-processor expansion)
The name in a function declaration.
In cairo, they are parameters i
Nick Lewycky wrote:
> Package: libcairomm-1.0-dev
> Version: 0.6.0-2
> Severity: normal
>
> The examples for PsSurface, PdfSurface and SvgSurface don't link:
>
> $ g++ `pkg-config --cflags --libs cairomm-1.0` cairograph.cpp
> /tmp/ccqYR7Sy.o: In function `main':
> cairograph.cpp:(.text+0x141): un
ASJ wrote:
> Package: libcairo2
> Version: 1.2.0-3
> Followup-For: Bug #325526
>
>
> In the latest update to 1.2.0-3 anything using python's wxGtk interface
> dies on startup:
>
> Traceback (most recent call last):
> File "CastPodderGui.py", line 32, in ?
> import wx
> File "/usr/lib/pytho
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
Nick Lewycky wrote:
> Package: libglitz1
> Version: 0.4.4-1
> Severity: wishlist
>
> The latest release snapshot of glitz is version 0.5.3, which is one of
> the components needed to compile Xgl. The debian/ directory from 0.4.4
> can be inserted into the 0.5.3 directory tree just fine. Please upd
You said re cairo 1.0.2-3 on 12 Jan 2006:
> So, maybe just downgrade this bug report to severity normal and I'll
> re-check with the next regular unstable version.
If you haven't seen this crash since then, I'd propose to close this bug
as unreproducable.
Dave
--
To UNSUBSCRIBE, email to [EMAI
Benoît Dejean wrote:
> Package: tomboy
> Version: 0.3.3-3
> Severity: normal
>
> Please change /usr/bin/tomboy so that tomboy's mono VM
> is not started with --debug. This saves some memory.
> Thanks.
It doesn't start with debug in normal use:
$ sh -x /usr/bin/tomboy
+ '[' -e ./Tomboy.exe ']'
+
Sebastian Rittau wrote:
> Package: libcairo2-dev
> Version: 1.0.4-1
> Severity: important
>
> Please rebuild cairo against X11R7. With X11R7 the .la files have gone
> from X -dev packages, but are still referenced in /usr/lib/libcairo.la.
Why have they been removed?
> (This would be the right mo
Sebastian Rittau wrote:
> Package: pycairo
> Severity: wishlist
>
> It would be great the Debian package of pycairo could support SVG.
> Currently libsvg and libsvg-cairo aren't packaged, but I would be
> willing to work on that if pycairo will then get SVG support.
Neither (cairo) libsvg or libs
On Wed, 2006-03-22 at 14:52 +0100, Bernhard R. Link wrote:
> * Dave Beckett <[EMAIL PROTECTED]> [060322 08:11]:
...
> > I am not going to do either of these. The choice cairo made is
> > perfectly acceptable and good, common practice.
>
> I even want to challenge the
[EMAIL PROTECTED] wrote:
> Package: librdf0
> Version: 1.0.2-2
>
> The librasqual provided by the package, as also reported in librdf's
> BTS [1], makes Python bindings unusable.
>
> [EMAIL PROTECTED]:~/rdf/foaf_db$ python raptor_foaf.py
> Querying..
> rdf_query_rasqal.c:177:rasqal_literal_to_r
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
Bernhard R. Link wrote:
> libcairo2-dev has headers in /usr/include/cairo that
> are referenced by itself and by other packages without
> the cairo subdirectory thus forcing all programs directly
> or indirectly (e.g. gtk) libcairo to include an
> -I/
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
Dave Beckett wrote:
> Are you actually using cairomm under Debian? If not, then you can't
> really maintain it there.
To keep the bug info up-to-date.
Danilo doesn't use Debian so can't really maintain it properly. I
propose to use his packaging and maintain it myself esp
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
Danilo Piazzalunga wrote:
> On Tuesday 21 February 2006 04:40, Dave Beckett wrote:
>
>>If you want this in Debian and can do the packaging, I might be able to
>>sponsor it for you. I'm not really a C++ developer so I would mo
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
Danilo Piazzalunga wrote:
> Package: wnpp
> Version: N/A; reported 2006-02-13
> Severity: wishlist
> Owner: Danilo Piazzalunga <[EMAIL PROTECTED]>
>
> * Package name: cairomm
> Version : 0.5.0
> Upstream Authors: Murray Cumming <[EMAIL
Package: git-core
Version: 1.1.5-1
Severity: normal
Please can you package git 1.2.0 which has been released at
http://www.kernel.org/pub/software/scm/git/
a few days.
(and 1.1.6 has been available for 2 weeks at this time).
Thanks
Dave
-- System Information:
Debian Release: testing/unstable
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
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
Aaron M. Ucko wrote:
> reopen 348792 327407
> thanks
>
> Although the tweak for string-to-double conversion on 64-bit systems
> that made it into the latest gcj-4.0 upload has been a definite
> improvement, the new code still fails on at least one inp
Emil Nowak wrote:
> Package: libcairo2-dev
> Version: 1.0.2-3
> Severity: normal
>
> If I try to use some pdf related functions (which are described in
> libcairo2-doc package). I have error message that this symbol is undefined.
>
> It seems that there is nothing related to pdf:
>
> $ objdump -
Andreas Degert wrote:
> Update:
>
> I rebuilt the package libcairo2 (with apt-get -b source ...), now it
> works.
Ok... this is good, but not really very helpful in finding what actually
caused the segv. Wwhat broke? Clearly cairo didn't change recently so
it must have been something else in t
Marco Tulio Gontijo e Silva wrote:
> Package: python2.3-cairo
> Version: 1.0.0-1
> Severity: normal
>
> As pygtk 2.7+ is not on sid yet, it would be good that cairo have cairo.gtk
> support
> cause if not there's no way to use cairo + python + gtk.
As I was just reviewing the bugs for pycairo I
Tim Nowaczyk wrote:
> Package: redland-bindings
> Severity: wishlist
>
> dpkg-buildpackage does not currently build the php modules that are a
> part of this source package. Can these modules be built officially?
They could. Do you have a preference for which php version?
The downside of addin
Jamie Wilkinson wrote:
import cairo
print cairo.HAS_PDF_SURFACE
0
print cairo.HAS_PS_SURFACE
0
print cairo.HAS_GLITZ_SURFACE
0
This makes me a sad panda. Can you please enable all the target
formats?
Not at present since they are totally unsupported by upstream and I
don't want to
"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
On Sat, 2005-09-10 at 00:10 +0200, Kurt Roeckx wrote:
> Package: ikvm
> Version: 0.18.0.0-2
> Severity: important
>
> Hi,
>
> Your package is failing to build on amd64. I see those things in
> the build log:
> [exec] 1. ERROR in ../classtmp/java/lang/Double.java
>
1 - 100 of 135 matches
Mail list logo
