Re: GMP 5 uploaded to Debian, -dev package changed
On Sun, Mar 6, 2011 at 8:49 AM, Steve M. Robbins st...@sumost.ca wrote:
Am Sonntag, den 06.03.2011, 09:17 -0600 schrieb Steve M. Robbins:
OK, so I'll make an upload with libgmp10-dev providing both libgmp-dev
and libgmp3-dev.
Done: just uploaded gmp_5.0.1+dfsg-6.
Good luck! :-)
-Steve
-BEGIN PGP SIGNATURE-
Version: GnuPG v1.4.11 (GNU/Linux)
iD8DBQFNc7sX0i2bPSHbMcURAs4AAJ9etcdiyImofPPUbsOJLf1L4jgQIQCgiVjX
CjlT5SZNRqvLHTe42DQRJw4=
=1qJN
-END PGP SIGNATURE-
I was unable to build this package until I removed these lines from
the debian/rules file:
dh_install -plibmp3 usr/lib/libmp.so.*
dh_install -plib32mp3 ${lib32dir}/libmp.so.*
In the changelog it is mentioned that libmp3 and lib32mp3 are obsolete packages.
--
To UNSUBSCRIBE, email to debian-haskell-requ...@lists.debian.org
with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Archive:
http://lists.debian.org/banlktinjtqjodkrotfes2apxckez1j2...@mail.gmail.com
Re: GMP 5 uploaded to Debian, -dev package changed
Hi Steve, Am Sonntag, den 06.03.2011, 10:49 -0600 schrieb Steve M. Robbins: Am Sonntag, den 06.03.2011, 09:17 -0600 schrieb Steve M. Robbins: OK, so I'll make an upload with libgmp10-dev providing both libgmp-dev and libgmp3-dev. Done: just uploaded gmp_5.0.1+dfsg-6. Good luck! :-) FYI, the change had the desired effects, builds are possible and successful (at least wrt this issue). Nevertheless, the transition to ghc-7 seems to be complicated, so it may take a little while until we can remove the work-around. Greetings, Joachim -- Joachim nomeata Breitner Debian Developer nome...@debian.org | ICQ# 74513189 | GPG-Keyid: 4743206C JID: nome...@joachim-breitner.de | http://people.debian.org/~nomeata signature.asc Description: This is a digitally signed message part
Re: GMP 5 uploaded to Debian, -dev package changed
Dear Steve, actually, this is getting all very complicated for us, since we have to maintain a compiler which needs itself to compile and which suddenly has become uninstallable. I’d be grateful if you could help us here. One solution seems to be if libgmp10-dev would provide libgmp3-dev, at least until we have built a new compiler depending on libgmp10-dev (or libgmp-dev) on all architectures. Would that be an option? @DHG: We need to investigate if we really need the dependencies on the -dev packages, both for ghc and for the library packages. Is someone interested in investigating what breaks if we remove them, why we need them and whether there is maybe a work-around such that the binary dependencies added by dpkg-shlibdeps are sufficient. Thanks, Joachim -- Joachim nomeata Breitner Debian Developer nome...@debian.org | ICQ# 74513189 | GPG-Keyid: 4743206C JID: nome...@joachim-breitner.de | http://people.debian.org/~nomeata signature.asc Description: This is a digitally signed message part
Re: GMP 5 uploaded to Debian, -dev package changed
Hello, You may continue to use versioned dev packages (libgmp10-dev and 32/64-bit variants) if you wish. Alternatively, these packages now provide an unversioned libgmp-dev package that may be used instead. hmm, this causes problems for us now. The ghc6 package (or the ghc package where available) depends on libgmp3-dev, which is no longer available, it seems. Therefore, new versions of ghc, which build-depends on ghc|ghc6, can not be built by any buildd. Well, I can honestly say I never expected this situation. This must be a nightmare to maintain. It seems we have to manually bootstrap ghc on each architecture, by building in a chroot where the old libgmp3-dev is available (to be able to install a previous ghc), and where the new libgmp-dev is available (to build against that). If that is not possible due to conflicts between these, things get even more complicated... The libgmp3-dev and libgmp10-dev packages contain an overlapping set of headers, so it would be quite difficult to co-install them sensibly. I'm not sure what to suggest. actually, this is getting all very complicated for us, since we have to maintain a compiler which needs itself to compile and which suddenly has become uninstallable. I???d be grateful if you could help us here. I'm sorry that the dev package was versioned. This must be something that you deal with regularly, though, as packages evolve. What do you normally do? One solution seems to be if libgmp10-dev would provide libgmp3-dev, at least until we have built a new compiler depending on libgmp10-dev (or libgmp-dev) on all architectures. Would that be an option? That's not a great option because libgmp3-dev promises the -dev package strictly for libgmp3, whereas libgmp10-dev promises the -dev package strictly for libgmp10. I'm sorry that the dev package was versioned to start with and as I indicated, an unversioned virtual package is now provided. Because autobuilders don't like virtual packages (?), I've been asked to create an unversioned NON-virtual libgmp-dev that simply depends on libgmp10-dev. I will do that shortly. I don't think that's going to help you, though, since you still can't have libgmp3-dev and libgmp-dev co-installed. I'm really at a loss. Sorry, -Steve signature.asc Description: Digital signature
Re: GMP 5 uploaded to Debian, -dev package changed
On Sun, Mar 06, 2011 at 07:01:49PM +0530, Joachim Breitner wrote: One solution seems to be if libgmp10-dev would provide libgmp3-dev, at least until we have built a new compiler depending on libgmp10-dev (or libgmp-dev) on all architectures. Would that be an option? That's not a great option because libgmp3-dev promises the -dev package strictly for libgmp3, whereas libgmp10-dev promises the -dev package strictly for libgmp10. I'm sorry that the dev package was versioned to start with and as I indicated, an unversioned virtual package is now provided. Right, therefore I am suggesting it as a work-around only until we managed to have ghc???s depending on libgmp-dev on all architectures. Then you can remove the Provides. I understand. I yet have to check if the current ghc packages actually work with libgmp10-dev instead of libgmp3-dev, otherwise this work-around would not help. OK, please let me know the outcome of this test. What would break? Other package build-depending on libgmp3-dev might try to build and then fail (if they are hit by incompatibilities). But they are not buildable now either, so while inconvenient, not a big problem. Any other possible consequence? No, not that I can think of. OK, so I'll make an upload with libgmp10-dev providing both libgmp-dev and libgmp3-dev. Cheers, -Steve signature.asc Description: Digital signature
Re: GMP 5 uploaded to Debian, -dev package changed
Am Sonntag, den 06.03.2011, 09:17 -0600 schrieb Steve M. Robbins: OK, so I'll make an upload with libgmp10-dev providing both libgmp-dev and libgmp3-dev. Done: just uploaded gmp_5.0.1+dfsg-6. Good luck! :-) -Steve signature.asc Description: Digital signature
Re: GMP 5 uploaded to Debian, -dev package changed
Hi, Am Sonntag, den 06.03.2011, 10:49 -0600 schrieb Steve M. Robbins: Am Sonntag, den 06.03.2011, 09:17 -0600 schrieb Steve M. Robbins: OK, so I'll make an upload with libgmp10-dev providing both libgmp-dev and libgmp3-dev. Done: just uploaded gmp_5.0.1+dfsg-6. Good luck! :-) thanks a lot! Gruß, Joachim -- Joachim nomeata Breitner Debian Developer nome...@debian.org | ICQ# 74513189 | GPG-Keyid: 4743206C JID: nome...@joachim-breitner.de | http://people.debian.org/~nomeata signature.asc Description: This is a digitally signed message part
Re: GMP 5 uploaded to Debian, -dev package changed
[CC to Steve just in case he is curious, I don’t think there is much he can do for us.] Hi Debian Haskell Group, Am Samstag, den 05.03.2011, 21:15 -0600 schrieb Steve M. Robbins: This email is being sent to the package contact address for all packages that build using GMP; i.e. each package that declares a build-dependency on one of the following packages: lib32gmp3-dev lib64gmp3-dev libgmp3-dev The latest version of GMP has just been uploaded to Debian and is being built. This is a SONAME change and, since the -dev package was versioned, the build-deps of your package must be adjusted. You may continue to use versioned dev packages (libgmp10-dev and 32/64-bit variants) if you wish. Alternatively, these packages now provide an unversioned libgmp-dev package that may be used instead. hmm, this causes problems for us now. The ghc6 package (or the ghc package where available) depends on libgmp3-dev, which is no longer available, it seems. Therefore, new versions of ghc, which build-depends on ghc|ghc6, can not be built by any buildd. It seems we have to manually bootstrap ghc on each architecture, by building in a chroot where the old libgmp3-dev is available (to be able to install a previous ghc), and where the new libgmp-dev is available (to build against that). If that is not possible due to conflicts between these, things get even more complicated... hmm, but that is the case: http://svn.debian.org/viewsvn/debian-science/packages/gmp/trunk/debian/control?revision=38158view=markup Maybe we can install the previous ghc forcibly (ignoring the libgmp3-dev dependency) and only install the library libgmp3c2 (= 2:4.3.2+dfsg-1), hoping that the previous ghc still works. The ghc we are building would build-depend on libgmp-dev. I’m not sure if DSA is happy to do such a forced installation on the porterboxes though. Sigh. Greetings, Joachim PS: I’m using a porterbox at the moment to manually build ghc, hoping to get around the -lpthread issue there. Build failure on powerpc reported to upstream. -- Joachim nomeata Breitner Debian Developer nome...@debian.org | ICQ# 74513189 | GPG-Keyid: 4743206C JID: nome...@joachim-breitner.de | http://people.debian.org/~nomeata signature.asc Description: This is a digitally signed message part
