Your message dated Fri, 26 Sep 2008 14:57:57 +0200
with message-id <[EMAIL PROTECTED]>
and subject line Re: Bug#500083: redland: uninstallable due to new rasqal
(0.9.16-1)
has caused the Debian Bug report #500083,
regarding redland: uninstallable due to new rasqal (0.9.16-1)
to be marked as done.
This means that you claim that the problem has been dealt with.
If this is not the case it is now your responsibility to reopen the
Bug report if necessary, and/or fix the problem forthwith.
(NB: If you are a system administrator and have no idea what this
message is talking about, this may indicate a serious mail system
misconfiguration somewhere. Please contact [EMAIL PROTECTED]
immediately.)
--
500083: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=500083
Debian Bug Tracking System
Contact [EMAIL PROTECTED] with problems
--- Begin Message ---
Package: redland
Version: 1.0.7-1
Severity: serious
Justification: makes KDE4 uninstalable
Hi,
After the recent update of rasqal from 0.9.15 to 0.9.16 by you, the soname bump
made you update from librasqal0 to librasqal1. (And librasqal0-dev to
librasqal1-dev...)
This have made redland unninstalable: current librdf0 and redland-utils in the
archive needs librasqal0. This is very annoying since librdf0 is needed by
soprano (libsoprano4), that is a depend of the *whole* KDE 4.
As well, redland 1.0.7 does not build against newer rasqal, it needs to be
updated to version 1.0.8.
I do not fully understand how being maintainer and upstream of both packages
you did not update redland too. Or even worse, why in first instace, you
introduced this change in unstable now, when they are not meant for Lenny.
Casual reader can find more info about this in Dave's blog at [1])
So going back to what really annoys me: KDE 4 is now uninstallable, and we can
not update new stuff since build-depends are broken. So could you ASAP either:
-revert the rasqal change
-update redland and make sure all the stuff to complete this transition is
fine?
Whatever you think it is better, could you please fix it really really soon?
If not, I am planning looking at apply one of these solutions, in the next 2
days.
Ana
[1]
http://journal.dajobe.org/journal/posts/2008/07/06/redland-rdf-libraries-108-released/
--- End Message ---
--- Begin Message ---
Version: 1.0.8-1
On Wed, Sep 24, 2008 at 11:42:14PM +0200, Ana Guerrero wrote:
> Package: redland
> Version: 1.0.7-1
> Severity: serious
> Justification: makes KDE4 uninstalable
>
>
> Hi,
>
> After the recent update of rasqal from 0.9.15 to 0.9.16 by you, the soname
> bump
> made you update from librasqal0 to librasqal1. (And librasqal0-dev to
> librasqal1-dev...)
> This have made redland unninstalable: current librdf0 and redland-utils in the
> archive needs librasqal0. This is very annoying since librdf0 is needed by
> soprano (libsoprano4), that is a depend of the *whole* KDE 4.
>
> As well, redland 1.0.7 does not build against newer rasqal, it needs to be
> updated to version 1.0.8.
>
> I do not fully understand how being maintainer and upstream of both packages
> you did not update redland too. Or even worse, why in first instace, you
> introduced this change in unstable now, when they are not meant for Lenny.
>
> Casual reader can find more info about this in Dave's blog at [1])
>
>
> So going back to what really annoys me: KDE 4 is now uninstallable, and we
> can
> not update new stuff since build-depends are broken. So could you ASAP either:
>
> -revert the rasqal change
> -update redland and make sure all the stuff to complete this transition is
> fine?
>
> Whatever you think it is better, could you please fix it really really soon?
> If not, I am planning looking at apply one of these solutions, in the next 2
> days.
>
> Ana
>
>
>
> [1]
> http://journal.dajobe.org/journal/posts/2008/07/06/redland-rdf-libraries-108-released/
>
>
>
--- End Message ---
