Prev: google-earth
Next: net/samba3
From: Jerry on 20 Jun 2010 06:55 FreeBSD-PRERELEASE 8.1 amd64 Since the release of "libassuan-2.0.0", I have not been able to update or reinstall "security/GPA". All of the other ports appear to build fine. I tried removing the old "libassuan-1-1.0.5" ports; however, when attempting to rebuld the 'GPA' port, it only appears to want the older and not newer version of "libassuan". Build the newer "libassuan" port first does not appear to help either. A copy of the last failed build attempt with the newer "libassuan" port installed follows. Script started on Sun Jun 20 06:44:08 2010 ---> Reinstalling 'gpa-0.9.0_5' (security/gpa) ---> Building '/usr/ports/security/gpa' ===> Cleaning for gpa-0.9.0_5 ===> Vulnerability check disabled, database not found ===> License check disabled, port has not defined LICENSE ===> Found saved configuration for gpa-0.9.0_3 ===> Extracting for gpa-0.9.0_5 => MD5 Checksum OK for gpa-0.9.0.tar.bz2. => SHA256 Checksum OK for gpa-0.9.0.tar.bz2. ===> Patching for gpa-0.9.0_5 ===> gpa-0.9.0_5 depends on executable: gpgv2 - found ===> gpa-0.9.0_5 depends on package: libassuan-1>=1.0.5 - not found ===> Verifying install for libassuan-1>=1.0.5 in /usr/ports/security/libassuan-1 ===> libassuan-1-1.0.5 conflicts with installed package(s): libassuan-2.0.0 They install files into the same place. Please remove them first with pkg_delete(1). *** Error code 1 Stop in /usr/ports/security/libassuan-1. *** Error code 1 Stop in /usr/ports/security/gpa. ** Command failed [exit code 1]: /usr/bin/script -qa /tmp/portupgrade20100620-14986-1cjhi6p-0 env UPGRADE_TOOL=portupgrade UPGRADE_PORT=gpa-0.9.0_5 UPGRADE_PORT_VER=0.9.0_5 make ** Fix the problem and try again. ** Listing the failed packages (-:ignored / *:skipped / !:failed) ! security/gpa (gpa-0.9.0_5) (unknown build error) Script done on Sun Jun 20 06:44:15 2010 -- Jerry â FreeBSD-Ports.user(a)seibercom.net Disclaimer: off-list followups get on-list replies or get ignored. Please do not ignore the Reply-To header. __________________________________________________________________ COBOL: An exercise in Artificial Inelegance.
From: "Jason E. Hale" on 20 Jun 2010 12:30 On Sunday, June 20, 2010 06:55:52 you wrote: > FreeBSD-PRERELEASE 8.1 amd64 > > Since the release of "libassuan-2.0.0", I have not been able to update > or reinstall "security/GPA". All of the other ports appear to build > fine. > > I tried removing the old "libassuan-1-1.0.5" ports; however, when > attempting to rebuld the 'GPA' port, it only appears to want the older > and not newer version of "libassuan". Build the newer "libassuan" port > first does not appear to help either. > > A copy of the last failed build attempt with the newer "libassuan" port > installed follows. > > Script started on Sun Jun 20 06:44:08 2010 > ---> Reinstalling 'gpa-0.9.0_5' (security/gpa) > ---> Building '/usr/ports/security/gpa' > ===> Cleaning for gpa-0.9.0_5 > ===> Vulnerability check disabled, database not found > ===> License check disabled, port has not defined LICENSE > ===> Found saved configuration for gpa-0.9.0_3 > ===> Extracting for gpa-0.9.0_5 > => MD5 Checksum OK for gpa-0.9.0.tar.bz2. > => SHA256 Checksum OK for gpa-0.9.0.tar.bz2. > ===> Patching for gpa-0.9.0_5 > ===> gpa-0.9.0_5 depends on executable: gpgv2 - found > ===> gpa-0.9.0_5 depends on package: libassuan-1>=1.0.5 - not found > ===> Verifying install for libassuan-1>=1.0.5 > in /usr/ports/security/libassuan-1 > > ===> libassuan-1-1.0.5 conflicts with installed package(s): > libassuan-2.0.0 > > They install files into the same place. > Please remove them first with pkg_delete(1). > *** Error code 1 > > Stop in /usr/ports/security/libassuan-1. > *** Error code 1 > > Stop in /usr/ports/security/gpa. > ** Command failed [exit code 1]: /usr/bin/script > -qa /tmp/portupgrade20100620-14986-1cjhi6p-0 env > UPGRADE_TOOL=portupgrade UPGRADE_PORT=gpa-0.9.0_5 > UPGRADE_PORT_VER=0.9.0_5 make ** Fix the problem and try again. ** > Listing the failed packages (-:ignored / *:skipped / !:failed) ! > security/gpa (gpa-0.9.0_5) (unknown build error) > > Script done on Sun Jun 20 06:44:15 2010 I know all too well. Unfortunately a committer made a hasty move and updated libassuan to version 2.0.0 and then made gnupg 2.x use the newer libassuan. This of course turns into a chain of conflicts because everything else that depends on libassuan 1.x usually needs gnupg 2.x as well. I am working to resolve the situation for my ports, however, the author of gpa has not released a version that will work with libassuan 2.x. There is a ports freeze now too, so I am not sure if my updates will even go through for a while. If you really need to use gpa immediately, I suggest downgrading everything that depended on libassuan 2.x to use libassuan 1.x. - Jason _______________________________________________ freebsd-ports(a)freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-ports To unsubscribe, send any mail to "freebsd-ports-unsubscribe(a)freebsd.org"
From: Ion-Mihai Tetcu on 20 Jun 2010 13:08 On Sun, 20 Jun 2010 12:30:37 -0400 "Jason E. Hale" <bsdkaffee(a)gmail.com> wrote: > On Sunday, June 20, 2010 06:55:52 you wrote: > > FreeBSD-PRERELEASE 8.1 amd64 > > > > Since the release of "libassuan-2.0.0", I have not been able to > > update or reinstall "security/GPA". All of the other ports appear > > to build fine. > > > > I tried removing the old "libassuan-1-1.0.5" ports; however, when > > attempting to rebuld the 'GPA' port, it only appears to want the > > older and not newer version of "libassuan". Build the newer > > "libassuan" port first does not appear to help either. > > > > A copy of the last failed build attempt with the newer "libassuan" > > port installed follows. > > > > Script started on Sun Jun 20 06:44:08 2010 > > ---> Reinstalling 'gpa-0.9.0_5' (security/gpa) > > ---> Building '/usr/ports/security/gpa' > > ===> Cleaning for gpa-0.9.0_5 > > ===> Vulnerability check disabled, database not found > > ===> License check disabled, port has not defined LICENSE > > ===> Found saved configuration for gpa-0.9.0_3 > > ===> Extracting for gpa-0.9.0_5 > > => MD5 Checksum OK for gpa-0.9.0.tar.bz2. > > => SHA256 Checksum OK for gpa-0.9.0.tar.bz2. > > ===> Patching for gpa-0.9.0_5 > > ===> gpa-0.9.0_5 depends on executable: gpgv2 - found > > ===> gpa-0.9.0_5 depends on package: libassuan-1>=1.0.5 - not > > found ===> Verifying install for libassuan-1>=1.0.5 > > in /usr/ports/security/libassuan-1 > > > > ===> libassuan-1-1.0.5 conflicts with installed package(s): > > libassuan-2.0.0 > > > > They install files into the same place. > > Please remove them first with pkg_delete(1). > > *** Error code 1 > > > > Stop in /usr/ports/security/libassuan-1. > > *** Error code 1 > > > > Stop in /usr/ports/security/gpa. > > ** Command failed [exit code 1]: /usr/bin/script > > -qa /tmp/portupgrade20100620-14986-1cjhi6p-0 env > > UPGRADE_TOOL=portupgrade UPGRADE_PORT=gpa-0.9.0_5 > > UPGRADE_PORT_VER=0.9.0_5 make ** Fix the problem and try again. ** > > Listing the failed packages (-:ignored / *:skipped / !:failed) ! > > security/gpa (gpa-0.9.0_5) (unknown build error) > > > > Script done on Sun Jun 20 06:44:15 2010 > > I know all too well. Unfortunately a committer made a hasty move and > updated libassuan to version 2.0.0 and then made gnupg 2.x use the > newer libassuan. This of course turns into a chain of conflicts > because everything else that depends on libassuan 1.x usually needs > gnupg 2.x as well. > > I am working to resolve the situation for my ports, however, the > author of gpa has not released a version that will work with > libassuan 2.x. There is a ports freeze now too, so I am not sure if > my updates will even go through for a while. If you really need to > use gpa immediately, I suggest downgrading everything that depended > on libassuan 2.x to use libassuan 1.x. Only slush, not full freeze. If your patches fix a problem, they will go in. -- IOnut - Un^d^dregistered ;) FreeBSD "user" "Intellectual Property" is nowhere near as valuable as "Intellect" FreeBSD committer -> itetcu(a)FreeBSD.org, PGP Key ID 057E9F8B493A297B
From: Jerry on 20 Jun 2010 14:35 On Sun, 20 Jun 2010 20:08:19 +0300 Ion-Mihai Tetcu <itetcu(a)FreeBSD.org> articulated: [snip] > Only slush, not full freeze. > If your patches fix a problem, they will go in. I filed a PR, so perhaps it will get fixed in the near future. http://www.freebsd.org/cgi/query-pr.cgi?pr=148016 -- Jerry â FreeBSD-Ports.user(a)seibercom.net Disclaimer: off-list followups get on-list replies or get ignored. Please do not ignore the Reply-To header. __________________________________________________________________ "Just saying "no" prevents teenage pregnancy the way "Have a nice day" cures chronic depression." Faye Wattleton http://en.wikipedia.org/wiki/Faye_Wattleton
From: Doug Barton on 21 Jun 2010 15:07
On 06/20/10 09:30, Jason E. Hale wrote: > On Sunday, June 20, 2010 06:55:52 you wrote: >> FreeBSD-PRERELEASE 8.1 amd64 >> >> Since the release of "libassuan-2.0.0", I have not been able to >> update or reinstall "security/GPA". All of the other ports appear >> to build fine. Jerry, I'm sorry to hear that you're having problems. At this time if you want to use gpa the only alternative is to use gnupg 1.x. I realize that's not necessarily an attractive alternative, but see below. > I know all too well. Unfortunately a committer made a hasty move and > updated libassuan to version 2.0.0 and then made gnupg 2.x use the > newer libassuan. Jason, It wasn't hasty. My first public message to maintainers of affected ports went out on May 11th. According to this message on May 12th you seemed quite optimistic that you would be able to deal with gpa, and actually gave some helpful information on some of the other ports as well, which I appreciated. http://mail.kde.org/pipermail/kde-freebsd/2010-May/008334.html In subsequent messages I agreed with your suggestion that handling everything at once was the best option, however after repeated prompting neither you, nor any of the other maintainers came forward with patches to accomplish that. Due to a bug in gnupg 2.0.14 (albeit a minor one) I thought it was important to move forward with the upgrade prior to 8.1-RELEASE. FWIW, I agree that the situation with libassuan 2.x being incompatible with 1.x is not ideal, but it's not something I have any control over. The authors of the software made that choice, and the theory is that the benefits outweigh the costs. I hope they are right. :) > This of course turns into a chain of conflicts because everything > else that depends on libassuan 1.x usually needs gnupg 2.x as well. Anything that depends on gnupg 2.x will also work with 1.x as it applies to strict gnupg functionality. Once again, I realize that this is not necessarily the most desirable option, however it _does_ leave the users with a path. It's probably also worth pointing that out of the 3 remaining ports that need to be fixed, kdepim will be fixed in the next release, and the kde folks have already committed to dealing with it. In opensc the dependency is optional, and the feature that depends on it will be removed in the next version anyway. > I am working to resolve the situation for my ports, Do you have ports other than gpa that are affected by this change? > however, the author of gpa has not released a version that will work > with libassuan 2.x. I asked Werner about this, and unfortunately it's not likely that he will be able to cut a new release of gpa prior to our 8.1-RELEASE. Are you still optimistic about using what's in their source tree to produce a patch for libassuan 2.x compatibility? I downloaded their tree but haven't had time to look at it much since I've had other urgent issues to handle. > There is a ports freeze now too, so I am not sure if my updates will > even go through for a while. Just in case I haven't been clear, if you get a patch for gpa I will commit it. Making it work with libassuan 2.0.0 definitely falls into the category of what's acceptable to commit during the slush. > If you really need to use gpa immediately, I suggest downgrading > everything that depended on libassuan 2.x to use libassuan 1.x. At this point the only thing that depends on it is gnupg 2.x (and dirmngr, but the only thing that depends on it is gnupg 2.x). hth, Doug -- ... and that's just a little bit of history repeating. -- Propellerheads Improve the effectiveness of your Internet presence with a domain name makeover! http://SupersetSolutions.com/ _______________________________________________ freebsd-ports(a)freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-ports To unsubscribe, send any mail to "freebsd-ports-unsubscribe(a)freebsd.org" |