[opensuse-buildservice] Fedora 18 - Please update mingw packages of boost on b.o.o
-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1 Hi, I'm building some packages of mine both for Linux and also for Fedora18 mingw targets on b.o.o. My packages depend on boost and the mingw[32|64] packages of boost use versioned file names. Now Fedora18 recently upgraded to Boost 1.50 and thus my packages from b.o.o now have dependency problems like this: - --> Running transaction check - ---> Package mingw32-ehs.noarch 0:1.5.0-160.fc17 will be updated - ---> Package mingw32-ehs.noarch 0:1.5.0-160.fc18 will be an update - --> Processing Dependency: mingw32(boost_regex-gcc47-mt-1_48.dll) for package: mingw32-ehs-1.5.0-160.fc18.noarch - ---> Package mingw32-ehs-devel.noarch 0:1.5.0-160.fc17 will be updated - ---> Package mingw32-ehs-devel.noarch 0:1.5.0-160.fc18 will be an update - --> Finished Dependency Resolution Error: Package: mingw32-ehs-1.5.0-160.fc18.noarch (opennx) Requires: mingw32(boost_regex-gcc47-mt-1_48.dll) Available: mingw32-boost-1.48.0-10.fc18.noarch (fedora) mingw32(boost_regex-gcc47-mt-1_48.dll) Installed: mingw32-boost-1.50.0-1.fc18.noarch (installed) Not found So can some admin please update at least mingw*boost*, perhaps even mingw* (lots of other mingw packages on Fedora appear to have a similar versioning scheme). Thanks -Fritz -----BEGIN PGP SIGNATURE----- Version: GnuPG v1.4.13 (GNU/Linux) Comment: Using GnuPG with Thunderbird - http://www.enigmail.net/ iEYEARECAAYFAlEtmSkACgkQboM4mAMyprB/PgCffp/sznPkNJEpJU42OwRbfGHE OP8AnAqSKzG/lSch/y5Ld+JvD/LMsbQq =FVkS -----END PGP SIGNATURE----- -- To unsubscribe, e-mail: opensuse-buildservice+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse-buildservice+owner@opensuse.org
On Mittwoch, 27. Februar 2013, 06:27:05 wrote Fritz Elfert:
-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1
Hi,
I'm building some packages of mine both for Linux and also for Fedora18 mingw targets on b.o.o. My packages depend on boost and the mingw[32|64] packages of boost use versioned file names. Now Fedora18 recently upgraded to Boost 1.50 and thus my packages from b.o.o now have dependency problems like this:
- --> Running transaction check - ---> Package mingw32-ehs.noarch 0:1.5.0-160.fc17 will be updated - ---> Package mingw32-ehs.noarch 0:1.5.0-160.fc18 will be an update - --> Processing Dependency: mingw32(boost_regex-gcc47-mt-1_48.dll) for package: mingw32-ehs-1.5.0-160.fc18.noarch - ---> Package mingw32-ehs-devel.noarch 0:1.5.0-160.fc17 will be updated - ---> Package mingw32-ehs-devel.noarch 0:1.5.0-160.fc18 will be an update - --> Finished Dependency Resolution Error: Package: mingw32-ehs-1.5.0-160.fc18.noarch (opennx) Requires: mingw32(boost_regex-gcc47-mt-1_48.dll) Available: mingw32-boost-1.48.0-10.fc18.noarch (fedora) mingw32(boost_regex-gcc47-mt-1_48.dll) Installed: mingw32-boost-1.50.0-1.fc18.noarch (installed) Not found
So can some admin please update at least mingw*boost*, perhaps even mingw* (lots of other mingw packages on Fedora appear to have a similar versioning scheme).
We have the version which get shipped with the Fedora release. We can not update them because users would not be able install them from Fedora repos. And most likely the new versions would break other builds (and I guess introducing binary incompatibilities, since it is boost). The only way you have is either to build against another repo building fitting packages for you or to import the sources of your wanted boost packages yourself in your project. -- Adrian Schroeter SUSE Linux Products GmbH email: adrian@suse.de
-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1 On 02/27/2013 09:49 AM, Adrian Schrter wrote:
On Mittwoch, 27. Februar 2013, 06:27:05 wrote Fritz Elfert:
-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1
Hi,
I'm building some packages of mine both for Linux and also for Fedora18
mingw targets on b.o.o. My packages depend on boost and the mingw[32|64]
packages of boost use versioned file names. Now Fedora18 recently
upgraded to Boost 1.50 and thus my packages from b.o.o now have
dependency problems like this:
- --> Running transaction check
- ---> Package mingw32-ehs.noarch 0:1.5.0-160.fc17 will be updated
- ---> Package mingw32-ehs.noarch 0:1.5.0-160.fc18 will be an update
- --> Processing Dependency: mingw32(boost_regex-gcc47-mt-1_48.dll) for
package: mingw32-ehs-1.5.0-160.fc18.noarch
- ---> Package mingw32-ehs-devel.noarch 0:1.5.0-160.fc17 will be updated
- ---> Package mingw32-ehs-devel.noarch 0:1.5.0-160.fc18 will be an update
- --> Finished Dependency Resolution
Error: Package: mingw32-ehs-1.5.0-160.fc18.noarch (opennx)
Requires: mingw32(boost_regex-gcc47-mt-1_48.dll)
Available: mingw32-boost-1.48.0-10.fc18.noarch (fedora)
mingw32(boost_regex-gcc47-mt-1_48.dll)
Installed: mingw32-boost-1.50.0-1.fc18.noarch (installed)
Not found
So can some admin please update at least mingw*boost*, perhaps even
mingw* (lots of other mingw packages on Fedora appear to have a similar
versioning scheme).
We have the version which get shipped with the Fedora release.
We can not update them because users would not be able install them from
Fedora repos. And most likely the new versions would break other builds
(and I guess introducing binary incompatibilities, since it is boost).
Huh? That's not true. Of course they can. boost 1.50 and the other mingw packages *ARE* in the standard Fedora 18 Repos (the "fedora-updates" repo to be specific which is enabled by default). So it get's pulled in automatically if someone installs a package that has a dependency on it. Its the other way round as you can see clearly in my example above. - -Fritz -----BEGIN PGP SIGNATURE----- Version: GnuPG v1.4.13 (GNU/Linux) Comment: Using GnuPG with Thunderbird - http://www.enigmail.net/ iEYEARECAAYFAlEuAbAACgkQboM4mAMyprBtawCeJb0X7J2dUqBFLpMUXg8i+Wep ueIAn2hscSsiw7zW9gCVskvLZHS4S+/h =VOcP -----END PGP SIGNATURE----- -- To unsubscribe, e-mail: opensuse-buildservice+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse-buildservice+owner@opensuse.org
-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1 On 02/27/2013 01:53 PM, Fritz Elfert wrote:
On 02/27/2013 09:49 AM, Adrian Schrter wrote:
On Mittwoch, 27. Februar 2013, 06:27:05 wrote Fritz Elfert:
-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1
Hi,
I'm building some packages of mine both for Linux and also for Fedora18
mingw targets on b.o.o. My packages depend on boost and the mingw[32|64]
packages of boost use versioned file names. Now Fedora18 recently
upgraded to Boost 1.50 and thus my packages from b.o.o now have
dependency problems like this:
- --> Running transaction check
- ---> Package mingw32-ehs.noarch 0:1.5.0-160.fc17 will be updated
- ---> Package mingw32-ehs.noarch 0:1.5.0-160.fc18 will be an update
- --> Processing Dependency: mingw32(boost_regex-gcc47-mt-1_48.dll) for
package: mingw32-ehs-1.5.0-160.fc18.noarch
- ---> Package mingw32-ehs-devel.noarch 0:1.5.0-160.fc17 will be updated
- ---> Package mingw32-ehs-devel.noarch 0:1.5.0-160.fc18 will be an update
- --> Finished Dependency Resolution
Error: Package: mingw32-ehs-1.5.0-160.fc18.noarch (opennx)
Requires: mingw32(boost_regex-gcc47-mt-1_48.dll)
Available: mingw32-boost-1.48.0-10.fc18.noarch (fedora)
mingw32(boost_regex-gcc47-mt-1_48.dll)
Installed: mingw32-boost-1.50.0-1.fc18.noarch (installed)
Not found
So can some admin please update at least mingw*boost*, perhaps even
mingw* (lots of other mingw packages on Fedora appear to have a similar
versioning scheme).
We have the version which get shipped with the Fedora release.
We can not update them because users would not be able install them from
Fedora repos. And most likely the new versions would break other builds
(and I guess introducing binary incompatibilities, since it is boost).
Huh? That's not true. Of course they can. boost 1.50 and the other mingw packages *ARE* in the standard Fedora 18 Repos (the "fedora-updates" repo to be specific which is enabled by default). So it get's pulled in automatically if someone installs a package that has a dependency on it. Its the other way round as you can see clearly in my example above.
-Fritz
And here's the proof: [felfert@fritz wsgate]$ yum list | grep mingw.*boost mingw32-boost.noarch 1.50.0-1.fc18 installed mingw32-boost-static.noarch 1.50.0-1.fc18 @updates mingw64-boost.noarch 1.50.0-1.fc18 installed mingw64-boost-static.noarch 1.50.0-1.fc18 @updates -----BEGIN PGP SIGNATURE----- Version: GnuPG v1.4.13 (GNU/Linux) Comment: Using GnuPG with Thunderbird - http://www.enigmail.net/ iEYEARECAAYFAlEuBCkACgkQboM4mAMyprCLkACeJraViB8nc7+EnPUKBM4PeWb+ FbkAoI3qzQ6cxrCJRFQJhPRhDKWNWQox =Q1QG -----END PGP SIGNATURE----- -- To unsubscribe, e-mail: opensuse-buildservice+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse-buildservice+owner@opensuse.org
On Mittwoch, 27. Februar 2013, 14:03:37 wrote Fritz Elfert:
-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1
On 02/27/2013 01:53 PM, Fritz Elfert wrote:
On 02/27/2013 09:49 AM, Adrian Schrter wrote:
On Mittwoch, 27. Februar 2013, 06:27:05 wrote Fritz Elfert:
-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1
Hi,
I'm building some packages of mine both for Linux and also for Fedora18
mingw targets on b.o.o. My packages depend on boost and the mingw[32|64]
packages of boost use versioned file names. Now Fedora18 recently
upgraded to Boost 1.50 and thus my packages from b.o.o now have
dependency problems like this:
- --> Running transaction check
- ---> Package mingw32-ehs.noarch 0:1.5.0-160.fc17 will be updated
- ---> Package mingw32-ehs.noarch 0:1.5.0-160.fc18 will be an update
- --> Processing Dependency: mingw32(boost_regex-gcc47-mt-1_48.dll) for
package: mingw32-ehs-1.5.0-160.fc18.noarch
- ---> Package mingw32-ehs-devel.noarch 0:1.5.0-160.fc17 will be updated
- ---> Package mingw32-ehs-devel.noarch 0:1.5.0-160.fc18 will be an update
- --> Finished Dependency Resolution
Error: Package: mingw32-ehs-1.5.0-160.fc18.noarch (opennx)
Requires: mingw32(boost_regex-gcc47-mt-1_48.dll)
Available: mingw32-boost-1.48.0-10.fc18.noarch (fedora)
mingw32(boost_regex-gcc47-mt-1_48.dll)
Installed: mingw32-boost-1.50.0-1.fc18.noarch (installed)
Not found
So can some admin please update at least mingw*boost*, perhaps even
mingw* (lots of other mingw packages on Fedora appear to have a similar
versioning scheme).
We have the version which get shipped with the Fedora release.
We can not update them because users would not be able install them from
Fedora repos. And most likely the new versions would break other builds
(and I guess introducing binary incompatibilities, since it is boost).
Huh? That's not true. Of course they can. boost 1.50 and the other mingw packages *ARE* in the standard Fedora 18 Repos (the "fedora-updates" repo to be specific which is enabled by default). So it get's pulled in automatically if someone installs a package that has a dependency on it. Its the other way round as you can see clearly in my example above.
nevertheless they will have influence to other builds, so I can not update them in the main GA project or I risk breakages in other projects. Also I will not spend time to review their changes. And esp. boost packages are known to break a lot :/ What we could do is to have a seperate :Update project containing the official fedora updates. however, I will not do this atm, since manual updating is too much work. Some time in future, when we have a complete download on demand feature, we can add this. -- Adrian Schroeter SUSE Linux Products GmbH email: adrian@suse.de
On Wednesday 27 Feb 2013 16:36:45 Adrian Schröter wrote:
What we could do is to have a seperate :Update project containing the official fedora updates. however, I will not do this atm, since manual updating is too much work. Some time in future, when we have a complete download on demand feature, we can add this.
+1 this would also help building kernel modules for multiple distributions (not just Fedora) Nico -- To unsubscribe, e-mail: opensuse-buildservice+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse-buildservice+owner@opensuse.org
On Wednesday 2013-02-27 16:36, Adrian Schröter wrote:
[shitload of quote trimmed - Fedora 18 updates]
nevertheless they will have influence to other builds, so I can not update them in the main GA project or I risk breakages in other projects.
Also I will not spend time to review their changes. And esp. boost packages are known to break a lot :/
What we could do is to have a seperate :Update project containing
Yes please. That's also what some recent FATE# entry desires. -- To unsubscribe, e-mail: opensuse-buildservice+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse-buildservice+owner@opensuse.org
participants (4)
-
Adrian Schröter -
Fritz Elfert -
Jan Engelhardt -
Nico Kruber