On Mon, Sep 08, 2014 at 10:46:28AM +0200, Fridrich Strba wrote:

That must be a temporary rebuild issue. The packages are little-by-little migrated to comply with the openSUSE shared library naming. It is possible that the repo has settled already in maybe x86_64, but some packages from i586 were not yet rebuilt and thus you get this conflicts. I would try again.

Is there any way to depend on the current DLL package? In contrast to openSuSE, mingw devel packages don't depend on their library package. https://build.opensuse.org/package/binary/windows:mingw:win32/mingw32-libgnurx?arch=x86_64&filename=mingw32-libgnurx-devel-2.5-9.6.noarch.rpm&repository=openSUSE_13.1 Provides: mingw32-libgnurx-devel = 2 mingw32(lib:gnurx) mingw32(lib:regex) mingw32-libgnurx-devel = 2 https://build.opensuse.org/package/binary/windows:mingw:win32/mingw32-libgnurx?arch=x86_64&filename=mingw32-libgnurx0-2.5-9.6.noarch.rpm&repository=openSUSE_13.1 Provides: mingw32-libgnurx0 = 2.5-9.6 mingw32(libgnurx-0.dll) If I need beside mingw32-libgnurx-devel the DLL during builing (eg. for creating a installer), my SPEC can't depend on the matching, current DLL package for mingw32-libgnurx-devel. It can only depend on a specific version (libgnurx0). Regards, Martin -- To unsubscribe, e-mail: opensuse-mingw+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse-mingw+owner@opensuse.org

-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1 Hello, Roger, Please, just wait for the repositories to settle. This kind of BuildRequires is really not necessary and, when everything is settled, it will be catered for automatically. I created some years ago a system for that and when all settles it will be working again. Cheers Fridrich On 09/09/14 07:21, Roger Oberholtzer wrote:

I added the following to my spec file and now it is building.

BuildRequires: mingw32-libstdc++6 BuildRequires: mingw32-libgcc_s_sjlj1

Only this package required this. The other 18 MinGW packages I build did not. Not sure why.

Roger

On Mon, Sep 8, 2014 at 7:54 PM, Martin Koegler wrote:

...

On Mon, Sep 08, 2014 at 10:46:28AM +0200, Fridrich Strba wrote:

...

That must be a temporary rebuild issue. The packages are little-by-little migrated to comply with the openSUSE shared library naming. It is possible that the repo has settled already in maybe x86_64, but some packages from i586 were not yet rebuilt and thus you get this conflicts. I would try again.

Is there any way to depend on the current DLL package?

In contrast to openSuSE, mingw devel packages don't depend on their library package.

https://build.opensuse.org/package/binary/windows:mingw:win32/mingw32-libgnurx?arch=x86_64&filename=mingw32-libgnurx-devel-2.5-9.6.noarch.rpm&repository=openSUSE_13.1

Provides:

...

mingw32-libgnurx-devel = 2 mingw32(lib:gnurx) mingw32(lib:regex) mingw32-libgnurx-devel = 2

https://build.opensuse.org/package/binary/windows:mingw:win32/mingw32-libgnurx?arch=x86_64&filename=mingw32-libgnurx0-2.5-9.6.noarch.rpm&repository=openSUSE_13.1

Provides:

...

mingw32-libgnurx0 = 2.5-9.6 mingw32(libgnurx-0.dll)

If I need beside mingw32-libgnurx-devel the DLL during builing (eg. for creating a installer), my SPEC can't depend on the matching, current DLL package for mingw32-libgnurx-devel. It can only depend on a specific version (libgnurx0).

Regards, Martin

-- To unsubscribe, e-mail: opensuse-mingw+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse-mingw+owner@opensuse.org

- -- Please avoid sending me Word, Excel or PowerPoint attachments. See http://www.gnu.org/philosophy/no-word-attachments.html -----BEGIN PGP SIGNATURE----- Version: GnuPG v2.0.22 (GNU/Linux) iEYEARECAAYFAlQOmMgACgkQu9a1imXPdA+2AACePvTfORKGws2KEIsmJa113iDm PjMAni1pa+6ZrCPoSZyGs+x+v2WOZ5ij =HS2l -----END PGP SIGNATURE----- -- To unsubscribe, e-mail: opensuse-mingw+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse-mingw+owner@opensuse.org

-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1 Please, this is a temporary problem due to the repositories not being in phase. It will go soon. Cheers Fridrich On 09/09/14 12:41, Roger Oberholtzer wrote:

I have added a new mingw package (spatialite-tools) and get a similar complaint:

have choice for mingw32(zlib1.dll) needed by mingw32-libspatialite: mingw32-tcl mingw32-zlib

Perhaps I could see what is happening if I understood what this message really means. There are four packages referenced here, in addition to the package that is being built.

Does 'have choices' mean that there is more than one possible zlib1.dll provided and that can be used? libspatialite and tcl do not contain a zlib1.dll and so do not provide it. zlib was needed when they were built, and was available at that time. They were just rebuilt ok. Why were they happy with zlib1.dll and not this package? All referenced packages are in https://build.opensuse.org/project/monitor/home:rogeroberholtzer:mingw

As is ordained in some law, of course the very packages that I am working with are the only ones that are failing to build. Oh well...

On Mon, Sep 8, 2014 at 7:54 PM, Martin Koegler wrote:

...

On Mon, Sep 08, 2014 at 10:46:28AM +0200, Fridrich Strba wrote:

...

That must be a temporary rebuild issue. The packages are little-by-little migrated to comply with the openSUSE shared library naming. It is possible that the repo has settled already in maybe x86_64, but some packages from i586 were not yet rebuilt and thus you get this conflicts. I would try again.

Is there any way to depend on the current DLL package?

In contrast to openSuSE, mingw devel packages don't depend on their library package.

https://build.opensuse.org/package/binary/windows:mingw:win32/mingw32-libgnurx?arch=x86_64&filename=mingw32-libgnurx-devel-2.5-9.6.noarch.rpm&repository=openSUSE_13.1

Provides:

...

mingw32-libgnurx-devel = 2 mingw32(lib:gnurx) mingw32(lib:regex) mingw32-libgnurx-devel = 2

https://build.opensuse.org/package/binary/windows:mingw:win32/mingw32-libgnurx?arch=x86_64&filename=mingw32-libgnurx0-2.5-9.6.noarch.rpm&repository=openSUSE_13.1

Provides:

...

mingw32-libgnurx0 = 2.5-9.6 mingw32(libgnurx-0.dll)

If I need beside mingw32-libgnurx-devel the DLL during builing (eg. for creating a installer), my SPEC can't depend on the matching, current DLL package for mingw32-libgnurx-devel. It can only depend on a specific version (libgnurx0).

Regards, Martin

-- To unsubscribe, e-mail: opensuse-mingw+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse-mingw+owner@opensuse.org

- -- Please avoid sending me Word, Excel or PowerPoint attachments. See http://www.gnu.org/philosophy/no-word-attachments.html -----BEGIN PGP SIGNATURE----- Version: GnuPG v2.0.22 (GNU/Linux) iEYEARECAAYFAlQO2dkACgkQu9a1imXPdA+2SgCeLZ3gpNWhAQFpNtzVP4R5hM+k 86UAni0yehBOCnJNoVeBgBWZYDVVGoZo =q2f8 -----END PGP SIGNATURE----- -- To unsubscribe, e-mail: opensuse-mingw+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse-mingw+owner@opensuse.org

I may have borrowed a bit... I was wanting a newer version of Tcl. I see that there is indeed a zlib1.dll in the %files section. Hmm... But I don't see where zlib is built. I don't have it as a BuildRequires. Does Tcl build it when compiled on Windows? I know it does not do so on Linux. Why would it have a copy? On Tue, Sep 9, 2014 at 12:47 PM, Fridrich Strba wrote:

-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1

I have spoken too fast.

On 09/09/14 12:41, Roger Oberholtzer wrote:

...

have choice for mingw32(zlib1.dll) needed by mingw32-libspatialite: mingw32-tcl mingw32-zlib

Did you branch the mingw32-tcl package? It seems that it actually builds zlib1.dll and bundles it. That is not the case for the mingw32-tcl in the repositories.

Cheers

F. -----BEGIN PGP SIGNATURE----- Version: GnuPG v2.0.22 (GNU/Linux)

iEUEARECAAYFAlQO2t0ACgkQu9a1imXPdA8FfwCYpGHe3BWFbk30FwLjnU9W2HtC egCdG3zBRKdQAW9ogGXeb65ilV66aso= =5Mkx -----END PGP SIGNATURE-----

-- Roger Oberholtzer -- To unsubscribe, e-mail: opensuse-mingw+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse-mingw+owner@opensuse.org