Re: [arch-general] [WAS:arch-dev-public] raptor/rasqal/redland .so rebuilds moved to testing
On Fri, Apr 22, 2011 at 6:16 PM, Andreas Radke <a.radke@arcor.de> wrote:
We had to add ugly compat packages because liblrdf and soprano can't be ported to the latest releases.
Please test if anything went broken. The packages shouldn't stay long in testing.
-Andy
I see that the {redland,rasqal}-compat packages conflict with {redland,rasqal}. In the case of redland-1.0.13-1 and redland-compat-1.0.12-1 that means I cannot have both at the same time. Which means I have to choose between kdelibs (depends on soprano, hence redland-compat) and slv2 (depends on redland-1.0.13) (or, in my system, between having KDE software and having ardour). Any way around this? I'm wondering why redland-compat isn't at the same version as redland, though I'm sure if this has been done there's a pretty good reason.
On Saturday 23 April 2011 10:19:42 you wrote:
I see that the {redland,rasqal}-compat packages conflict with {redland,rasqal}. In the case of redland-1.0.13-1 and redland-compat-1.0.12-1 that means I cannot have both at the same time. Which means I have to choose between kdelibs (depends on soprano, hence redland-compat) and slv2 (depends on redland-1.0.13) (or, in my system, between having KDE software and having ardour).
Any way around this? I'm wondering why redland-compat isn't at the same version as redland, though I'm sure if this has been done there's a pretty good reason. Hi, first of all rasqal > 0.9.21 and redland > 1.0.12, both requires raptor >= 2.0.0 to build, that's because they are out-of-date. Said that, we cannot ship a redland-base package (for example) and add a redland-compat package which provides the libraries built with raptor1 and depends on redland-base.
The only way to install the both version redland and redland-compat is to rename every file in the redland-compat package, (maybe using --program-suffix/- prefix) but this will require patches for things like soprano (cmake files and headers have to point to the -compat stuff). Patches are welcome. I've no others idea. We've to wait KDE devs port it to raptor2. -- Andrea
On Sat, Apr 23, 2011 at 9:47 PM, Andrea Scarpino <andrea@archlinux.org> wrote:
On Saturday 23 April 2011 10:19:42 you wrote:
I see that the {redland,rasqal}-compat packages conflict with {redland,rasqal}. In the case of redland-1.0.13-1 and redland-compat-1.0.12-1 that means I cannot have both at the same time. Which means I have to choose between kdelibs (depends on soprano, hence redland-compat) and slv2 (depends on redland-1.0.13) (or, in my system, between having KDE software and having ardour).
Any way around this? I'm wondering why redland-compat isn't at the same version as redland, though I'm sure if this has been done there's a pretty good reason. Hi, first of all rasqal > 0.9.21 and redland > 1.0.12, both requires raptor >= 2.0.0 to build, that's because they are out-of-date. Said that, we cannot ship a redland-base package (for example) and add a redland-compat package which provides the libraries built with raptor1 and depends on redland-base.
The only way to install the both version redland and redland-compat is to rename every file in the redland-compat package, (maybe using --program-suffix/- prefix) but this will require patches for things like soprano (cmake files and headers have to point to the -compat stuff). Patches are welcome.
I've no others idea. We've to wait KDE devs port it to raptor2.
Fair enough. I don't think the combination of (for example) KDE and any non-KDE app depending on redland is all that rare. Come to think of it, doesn't libreoffice depend on redland as well? Not that I've any say in this, but it does seem if this rebuild is moved out of [testing] there'll be lots of conflicts. Not sure what else is affected, but basically whatever packages have been affected by this rebuild (at least the redland portion of it) now does not function with KDE?
On 23 April 2011 22:36, Oon-Ee Ng <ngoonee.talk@gmail.com> wrote:
On Sat, Apr 23, 2011 at 9:47 PM, Andrea Scarpino <andrea@archlinux.org> wrote:
On Saturday 23 April 2011 10:19:42 you wrote:
I see that the {redland,rasqal}-compat packages conflict with {redland,rasqal}. In the case of redland-1.0.13-1 and redland-compat-1.0.12-1 that means I cannot have both at the same time. Which means I have to choose between kdelibs (depends on soprano, hence redland-compat) and slv2 (depends on redland-1.0.13) (or, in my system, between having KDE software and having ardour).
Any way around this? I'm wondering why redland-compat isn't at the same version as redland, though I'm sure if this has been done there's a pretty good reason. Hi, first of all rasqal > 0.9.21 and redland > 1.0.12, both requires raptor >= 2.0.0 to build, that's because they are out-of-date. Said that, we cannot ship a redland-base package (for example) and add a redland-compat package which provides the libraries built with raptor1 and depends on redland-base.
The only way to install the both version redland and redland-compat is to rename every file in the redland-compat package, (maybe using --program-suffix/- prefix) but this will require patches for things like soprano (cmake files and headers have to point to the -compat stuff). Patches are welcome.
I've no others idea. We've to wait KDE devs port it to raptor2.
Fair enough. I don't think the combination of (for example) KDE and any non-KDE app depending on redland is all that rare. Come to think of it, doesn't libreoffice depend on redland as well?
Not that I've any say in this, but it does seem if this rebuild is moved out of [testing] there'll be lots of conflicts. Not sure what else is affected, but basically whatever packages have been affected by this rebuild (at least the redland portion of it) now does not function with KDE?
You are correct. That's libreoffice and audacity, as can be seen now. I think the rebuild was done slightly wrong. All these should be changed to depend on compat packages. -- GPG/PGP ID: 8AADBB10
On Sat, Apr 23, 2011 at 11:36 PM, Ray Rashif <schiv@archlinux.org> wrote:
On 23 April 2011 22:36, Oon-Ee Ng <ngoonee.talk@gmail.com> wrote:
On Sat, Apr 23, 2011 at 9:47 PM, Andrea Scarpino <andrea@archlinux.org> wrote:
On Saturday 23 April 2011 10:19:42 you wrote:
I see that the {redland,rasqal}-compat packages conflict with {redland,rasqal}. In the case of redland-1.0.13-1 and redland-compat-1.0.12-1 that means I cannot have both at the same time. Which means I have to choose between kdelibs (depends on soprano, hence redland-compat) and slv2 (depends on redland-1.0.13) (or, in my system, between having KDE software and having ardour).
Any way around this? I'm wondering why redland-compat isn't at the same version as redland, though I'm sure if this has been done there's a pretty good reason. Hi, first of all rasqal > 0.9.21 and redland > 1.0.12, both requires raptor >= 2.0.0 to build, that's because they are out-of-date. Said that, we cannot ship a redland-base package (for example) and add a redland-compat package which provides the libraries built with raptor1 and depends on redland-base.
The only way to install the both version redland and redland-compat is to rename every file in the redland-compat package, (maybe using --program-suffix/- prefix) but this will require patches for things like soprano (cmake files and headers have to point to the -compat stuff). Patches are welcome.
I've no others idea. We've to wait KDE devs port it to raptor2.
Fair enough. I don't think the combination of (for example) KDE and any non-KDE app depending on redland is all that rare. Come to think of it, doesn't libreoffice depend on redland as well?
Not that I've any say in this, but it does seem if this rebuild is moved out of [testing] there'll be lots of conflicts. Not sure what else is affected, but basically whatever packages have been affected by this rebuild (at least the redland portion of it) now does not function with KDE?
You are correct. That's libreoffice and audacity, as can be seen now. I think the rebuild was done slightly wrong. All these should be changed to depend on compat packages.
Wouldn't that mean that everything would then depend on redland (and not on redland-compat)? No reason to rebuild, then?
On 24 April 2011 06:17, Oon-Ee Ng <ngoonee.talk@gmail.com> wrote:
On Sat, Apr 23, 2011 at 11:36 PM, Ray Rashif <schiv@archlinux.org> wrote:
On 23 April 2011 22:36, Oon-Ee Ng <ngoonee.talk@gmail.com> wrote:
On Sat, Apr 23, 2011 at 9:47 PM, Andrea Scarpino <andrea@archlinux.org> wrote:
On Saturday 23 April 2011 10:19:42 you wrote:
I see that the {redland,rasqal}-compat packages conflict with {redland,rasqal}. In the case of redland-1.0.13-1 and redland-compat-1.0.12-1 that means I cannot have both at the same time. Which means I have to choose between kdelibs (depends on soprano, hence redland-compat) and slv2 (depends on redland-1.0.13) (or, in my system, between having KDE software and having ardour).
Any way around this? I'm wondering why redland-compat isn't at the same version as redland, though I'm sure if this has been done there's a pretty good reason. Hi, first of all rasqal > 0.9.21 and redland > 1.0.12, both requires raptor >= 2.0.0 to build, that's because they are out-of-date. Said that, we cannot ship a redland-base package (for example) and add a redland-compat package which provides the libraries built with raptor1 and depends on redland-base.
The only way to install the both version redland and redland-compat is to rename every file in the redland-compat package, (maybe using --program-suffix/- prefix) but this will require patches for things like soprano (cmake files and headers have to point to the -compat stuff). Patches are welcome.
I've no others idea. We've to wait KDE devs port it to raptor2.
Fair enough. I don't think the combination of (for example) KDE and any non-KDE app depending on redland is all that rare. Come to think of it, doesn't libreoffice depend on redland as well?
Not that I've any say in this, but it does seem if this rebuild is moved out of [testing] there'll be lots of conflicts. Not sure what else is affected, but basically whatever packages have been affected by this rebuild (at least the redland portion of it) now does not function with KDE?
You are correct. That's libreoffice and audacity, as can be seen now. I think the rebuild was done slightly wrong. All these should be changed to depend on compat packages.
Wouldn't that mean that everything would then depend on redland (and not on redland-compat)? No reason to rebuild, then?
It would just mean we would have lone updated redland/raptor packages, just so things can tango along with KDE. Otherwise, the particular KDE functionality can be removed. It is up to Andrea in that case. -- GPG/PGP ID: 8AADBB10
On Sunday 24 April 2011 12:10:22 Ray Rashif wrote:
It would just mean we would have lone updated redland/raptor packages, just so things can tango along with KDE. Otherwise, the particular KDE functionality can be removed. It is up to Andrea in that case. The redland backend is used by kdelibs, digikam and others apps to store nepomuk information. We cannot build soprano without it.
-- Andrea
On Sun, Apr 24, 2011 at 5:42 PM, Andrea Scarpino <andrea@archlinux.org> wrote:
On Sunday 24 April 2011 12:10:22 Ray Rashif wrote:
It would just mean we would have lone updated redland/raptor packages, just so things can tango along with KDE. Otherwise, the particular KDE functionality can be removed. It is up to Andrea in that case. The redland backend is used by kdelibs, digikam and others apps to store nepomuk information. We cannot build soprano without it.
Quite the deadlock then. Any other apps than ardour (via slv2) affected?
All file conflicts should now be solved. Please test the new soprano pkg in testing and all the other redland/rasqal/raptor packages in testing. -Andy
On Sunday 24 April 2011 20:49:49 Andreas Radke wrote:
All file conflicts should now be solved. Please test the new soprano pkg in testing and all the other redland/rasqal/raptor packages in testing.
Sorry if missed out something but soprano 2.6.0-3 still requires redland- compat. From your message I understand it should come with redland as dependency so that libreoffice wouldn't complain... -- Arthur Titeica
On 04/24/2011 11:28 PM, Arthur Titeica wrote:
On Sunday 24 April 2011 20:49:49 Andreas Radke wrote:
All file conflicts should now be solved. Please test the new soprano pkg in testing and all the other redland/rasqal/raptor packages in testing.
Sorry if missed out something but soprano 2.6.0-3 still requires redland- compat. From your message I understand it should come with redland as dependency so that libreoffice wouldn't complain...
you should do a pacman -Syu. now redland-compat doesn't conflict with redland anymore and can be installed along with it. -- Ionuț
On Mon, Apr 25, 2011 at 4:34 AM, Ionut Biru <ibiru@archlinux.org> wrote:
On 04/24/2011 11:28 PM, Arthur Titeica wrote:
On Sunday 24 April 2011 20:49:49 Andreas Radke wrote:
All file conflicts should now be solved. Please test the new soprano pkg in testing and all the other redland/rasqal/raptor packages in testing.
Sorry if missed out something but soprano 2.6.0-3 still requires redland- compat. From your message I understand it should come with redland as dependency so that libreoffice wouldn't complain...
you should do a pacman -Syu. now redland-compat doesn't conflict with redland anymore and can be installed along with it.
error: failed to commit transaction (conflicting files) redland: /usr/lib/librdf.so.0 exists in filesystem redland: /usr/lib/librdf.so.0.0.0 exists in filesystem Errors occurred, no packages were upgraded. redland-1.0.13-1 redland-compat-1.0.12-3
On Mon, Apr 25, 2011 at 4:50 AM, Oon-Ee Ng <ngoonee.talk@gmail.com> wrote:
On Mon, Apr 25, 2011 at 4:34 AM, Ionut Biru <ibiru@archlinux.org> wrote:
On 04/24/2011 11:28 PM, Arthur Titeica wrote:
On Sunday 24 April 2011 20:49:49 Andreas Radke wrote:
All file conflicts should now be solved. Please test the new soprano pkg in testing and all the other redland/rasqal/raptor packages in testing.
Sorry if missed out something but soprano 2.6.0-3 still requires redland- compat. From your message I understand it should come with redland as dependency so that libreoffice wouldn't complain...
you should do a pacman -Syu. now redland-compat doesn't conflict with redland anymore and can be installed along with it.
error: failed to commit transaction (conflicting files) redland: /usr/lib/librdf.so.0 exists in filesystem redland: /usr/lib/librdf.so.0.0.0 exists in filesystem Errors occurred, no packages were upgraded.
redland-1.0.13-1 redland-compat-1.0.12-3
Should an upstream bug be filed? I'm pretty sure having the same soname across different minor versions is a bug. I've already checked the current librdf.org bug tracker, no such bug filed yet.
Am Tue, 26 Apr 2011 15:01:44 +0800 schrieb Oon-Ee Ng <ngoonee.talk@gmail.com>:
error: failed to commit transaction (conflicting files) redland: /usr/lib/librdf.so.0 exists in filesystem redland: /usr/lib/librdf.so.0.0.0 exists in filesystem Errors occurred, no packages were upgraded.
redland-1.0.13-1 redland-compat-1.0.12-3
Should an upstream bug be filed? I'm pretty sure having the same soname across different minor versions is a bug. I've already checked the current librdf.org bug tracker, no such bug filed yet.
You should probably do this. You may want to ask in the irc channel before. I'm usually logged in there #redland. -Andy
On Tue, Apr 26, 2011 at 2:07 PM, Andreas Radke <a.radke@arcor.de> wrote:
Am Tue, 26 Apr 2011 15:01:44 +0800 schrieb Oon-Ee Ng <ngoonee.talk@gmail.com>:
error: failed to commit transaction (conflicting files) redland: /usr/lib/librdf.so.0 exists in filesystem redland: /usr/lib/librdf.so.0.0.0 exists in filesystem Errors occurred, no packages were upgraded.
redland-1.0.13-1 redland-compat-1.0.12-3
Should an upstream bug be filed? I'm pretty sure having the same soname across different minor versions is a bug. I've already checked the current librdf.org bug tracker, no such bug filed yet.
You should probably do this. You may want to ask in the irc channel before. I'm usually logged in there #redland.
Hello Andreas, A bug is already filled here : https://bugs.archlinux.org/task/23919. If you need more precision, I'm at your service. Regards, -- Sébastien Luttringer www.seblu.net
On Tue, Apr 26, 2011 at 11:05 PM, Seblu <seblu@seblu.net> wrote:
On Tue, Apr 26, 2011 at 2:07 PM, Andreas Radke <a.radke@arcor.de> wrote:
Am Tue, 26 Apr 2011 15:01:44 +0800 schrieb Oon-Ee Ng <ngoonee.talk@gmail.com>:
error: failed to commit transaction (conflicting files) redland: /usr/lib/librdf.so.0 exists in filesystem redland: /usr/lib/librdf.so.0.0.0 exists in filesystem Errors occurred, no packages were upgraded.
redland-1.0.13-1 redland-compat-1.0.12-3
Should an upstream bug be filed? I'm pretty sure having the same soname across different minor versions is a bug. I've already checked the current librdf.org bug tracker, no such bug filed yet.
You should probably do this. You may want to ask in the irc channel before. I'm usually logged in there #redland.
Hello Andreas,
A bug is already filled here : https://bugs.archlinux.org/task/23919. If you need more precision, I'm at your service.
Regards,
I believe he was talking about an upstream bug. A bug at bugs.archlinux.org is for alerting Arch devs. Of course, Andreas is already replying to this thread, so he IS aware. @Andreas, I'll try to drop by the IRC channel soon. Its midnight here =).
Already done by myself: http://bugs.librdf.org/mantis/view.php?id=441 -Andy
On Wed, Apr 27, 2011 at 12:39 AM, Andreas Radke <a.radke@arcor.de> wrote:
Already done by myself: http://bugs.librdf.org/mantis/view.php?id=441
-Andy
Thanks. I was wondering whether a 'soprano-noredland' package would make sense, compiled against latest rasqal/redland. From http://mailman.archlinux.org/pipermail/arch-dev-public/2011-February/019502.... I believe it would simply not have the redland backend (and so lose nepomuk)? For someone like me who's only using a few KDE apps and no nepomuk that would work? Yes, for the record, I'm aware this is hacky, and I would not upload such a package to the AUR.
On Sunday 24 April 2011 23:34:41 Ionut Biru wrote:
On 04/24/2011 11:28 PM, Arthur Titeica wrote:
On Sunday 24 April 2011 20:49:49 Andreas Radke wrote:
All file conflicts should now be solved. Please test the new soprano pkg in testing and all the other redland/rasqal/raptor packages in testing.
Sorry if missed out something but soprano 2.6.0-3 still requires redland- compat. From your message I understand it should come with redland as dependency so that libreoffice wouldn't complain...
you should do a pacman -Syu. now redland-compat doesn't conflict with redland anymore and can be installed along with it.
Yes. I've tried that but it gives # pacman -S redland ..... error: failed to commit transaction (conflicting files) redland: /usr/lib/librdf.so.0 exists in filesystem redland: /usr/lib/librdf.so.0.0.0 exists in filesystem Errors occurred, no packages were upgraded. # pkgfile -s /usr/lib/librdf.so.0 local/redland-compat All that after many -Suy ;) http://www.archlinux.org/packages/testing/x86_64/redland-compat/ also shows usr/lib/librdf.so.0 -- Arthur Titeica
On Sun, Apr 24, 2011 at 7:49 PM, Andreas Radke <a.radke@arcor.de> wrote:
All file conflicts should now be solved. Please test the new soprano pkg in testing and all the other redland/rasqal/raptor packages in testing.
Issue is still present today. https://bugs.archlinux.org/task/23919 Kind regards, -- Sébastien Luttringer www.seblu.net
* Seblu [2011-04-26 09:03 +0200]:
On Sun, Apr 24, 2011 at 7:49 PM, Andreas Radke <a.radke@arcor.de> wrote:
All file conflicts should now be solved. Please test the new soprano pkg in testing and all the other redland/rasqal/raptor packages in testing.
Issue is still present today.
I've followed the hint at <https://bbs.archlinux.org/viewtopic.php?pid=923782#p923782> and it works.
On Tue, Apr 26, 2011 at 11:28 PM, F. Gr. <francesco.groccia@poste.it> wrote:
* Seblu [2011-04-26 09:03 +0200]:
On Sun, Apr 24, 2011 at 7:49 PM, Andreas Radke <a.radke@arcor.de> wrote:
All file conflicts should now be solved. Please test the new soprano pkg in testing and all the other redland/rasqal/raptor packages in testing.
Issue is still present today.
I've followed the hint at <https://bbs.archlinux.org/viewtopic.php?pid=923782#p923782> and it works.
That is a hacky workaround, not a fix.
participants (8)
-
Andrea Scarpino
-
Andreas Radke
-
Arthur Titeica
-
F. Gr.
-
Ionut Biru
-
Oon-Ee Ng
-
Ray Rashif
-
Seblu