On Thu, Jul 19, 2012 at 11:36:02PM +0200, Nicolas Lécureuil wrote:
in the devel ?
i think a libsoup-l10n ( noarch package ) would be a better idea.
This has been split into a -common package before, such as libexif12-common.
Dan
ovitters buildsystem-dae...@mageia.org writes:
Name: libsoup Relocations: (not relocatable)
Version : 2.39.4.1 Vendor: Mageia.Org
Release : 1.mga3Build Date: Tue Jul 17 14:51:59
2012
Hello,
There are file
On Thu, Jul 19, 2012 at 11:09:05PM +0200, Olivier Blin wrote:
ovitters buildsystem-dae...@mageia.org writes:
Name: libsoup Relocations: (not relocatable)
Version : 2.39.4.1 Vendor: Mageia.Org
Release : 1.mga3
On Thu, 19 Jul 2012 23:12:34 +0200
Olav Vitters wrote:
Name: libsoup Relocations: (not
relocatable) Version : 2.39.4.1
Vendor: Mageia.Org Release : 1.mga3
Build Date: Tue Jul 17 14:51:59 2012
Hello,
There are file conflicts between the
Olav Vitters o...@vitters.nl writes:
On Thu, Jul 19, 2012 at 11:09:05PM +0200, Olivier Blin wrote:
ovitters buildsystem-dae...@mageia.org writes:
Name: libsoup Relocations: (not relocatable)
Version : 2.39.4.1 Vendor: Mageia.Org
Le jeudi 19 juillet 2012 17:28:41 Charles A Edwards a écrit :
On Thu, 19 Jul 2012 23:12:34 +0200
Olav Vitters wrote:
Name: libsoup Relocations: (not
relocatable) Version : 2.39.4.1
Vendor: Mageia.Org Release : 1.mga3
Build Date: Tue Jul 17
Charles A Edwards c...@eslrahc.com writes:
file /usr/share/locale/be/LC_MESSAGES/libsoup.mo from install of
lib64soup2.4_1-2.39.4.1-1.mga3.x86_64 conflicts with file fr
om package libsoup2.4_1-2.39.3-1.mga3.i586
How can we solve that? By adding explicit conflicts?
Conflicts:
On Thu, Jul 19, 2012 at 05:28:41PM -0400, Charles A Edwards wrote:
On Thu, 19 Jul 2012 23:12:34 +0200
Olav Vitters wrote:
file /usr/share/locale/be/LC_MESSAGES/libsoup.mo from install of
lib64soup2.4_1-2.39.4.1-1.mga3.x86_64 conflicts with file fr
om package
On Thu, Jul 19, 2012 at 11:33:30PM +0200, Olivier Blin wrote:
neoclust mentionned another possible solution: move the locale files
into a noarch package.
I tried doing that in -3 (ignore -2 :P)
--
Regards,
Olav
On Thu, 19 Jul 2012 23:36:45 +0200
Olivier Blin wrote:
How can we solve that? By adding explicit conflicts?
Conflicts: lib%{_other_arch} != %{version}-%{release}
I thought such files should never conflict? Is this a packaging
bug or upstream thing? I don't get why these files
10 matches
Mail list logo
