Re: devel/libevent shopstopper
On Wed, Feb 22, 2017 at 10:14 AM, Christian Weisgerber wrote: > On 2017-02-20, Jim Ohlstein wrote: > > > Yup, it's a big one. That's why there's an entry in /usr/ports/UPDATING: > > > > 20170220: > >AFFECTS: devel/libevent2 > >AUTHOR: jbe...@freebsd.org > > > >libevent2 has been renamed back to libevent as the default version. > >If you manage out of tree ports make sure to run the following: > > > > # pkg set -n libevent2:libevent > > # pkg set -o devel/libevent2:devel/libevent > > The "If you manage out of tree ports" part is very confusing. > Either it is plain wrong or I don't understand what it means. > > -- > Christian "naddy" Weisgerber na...@mips.inka.de > I have no idea what it means exactly, but, as far as I know, I do no such thing. I use pkg to keep ports up to date and since this changes I get a report that libevent2-2.1.8 is orphaned from portversion. After a couple of days of this, I want ahead and did the package rename and origin commands in UPDATING and the orphan warning is gone. I'm not sure that there is an issue. It may have been totally cosmetic and disappeared of its own accord at some point, but I am at least curious. -- Kevin Oberman, Part time kid herder and retired Network Engineer E-mail: rkober...@gmail.com PGP Fingerprint: D03FB98AFA78E3B78C1694B318AB39EF1B055683 ___ freebsd-ports@freebsd.org mailing list https://lists.freebsd.org/mailman/listinfo/freebsd-ports To unsubscribe, send any mail to "freebsd-ports-unsubscr...@freebsd.org"
Re: devel/libevent shopstopper
On 2017-02-20, Jim Ohlstein wrote: > Yup, it's a big one. That's why there's an entry in /usr/ports/UPDATING: > > 20170220: >AFFECTS: devel/libevent2 >AUTHOR: jbe...@freebsd.org > >libevent2 has been renamed back to libevent as the default version. >If you manage out of tree ports make sure to run the following: > > # pkg set -n libevent2:libevent > # pkg set -o devel/libevent2:devel/libevent The "If you manage out of tree ports" part is very confusing. Either it is plain wrong or I don't understand what it means. -- Christian "naddy" Weisgerber na...@mips.inka.de ___ freebsd-ports@freebsd.org mailing list https://lists.freebsd.org/mailman/listinfo/freebsd-ports To unsubscribe, send any mail to "freebsd-ports-unsubscr...@freebsd.org"
Re: devel/libevent shopstopper
On Tue, 21 Feb 2017, Dewayne Geraghty wrote: For those interested in synth but skittish: 1. install synth; read the manual 2. synth configure which places the synth.ini file in /usr/local/etc/synth and for testing purposes try 3. synth just-build $category/$portname; Example: synth just-build devel/check devel/libevent ftp/curl 4. Examine your logs in /var/log/synth Particularly 00_last_results.log and 02_failure_list.log 5. Examine your new packages in /var/synth/live_packages/All Gotchas: if you have complex make.conf file that pulls in other files, you will need to concatenate them into the one make.conf. You'll need to use /etc/LiveSystem-make.conf which synth uses INSTEAD of /etc/make.conf, assuming you use the default profile. This threw me for a loop, hope to save new synth users some time and hair pulling. The man page is a bit vague on where the "builder's /etc/make.conf" is sourced -- from within the jail or the base system? "This is an optional, user-provided file. If it exists, the builder's /etc/make.conf will be appended with the contents of this file. For the default profile, the file would normally be located at /usr/local/etc/synth/LiveSystem-make.conf" Beckman --- Peter Beckman Internet Guy beck...@angryox.com http://www.angryox.com/ --- ___ freebsd-ports@freebsd.org mailing list https://lists.freebsd.org/mailman/listinfo/freebsd-ports To unsubscribe, send any mail to "freebsd-ports-unsubscr...@freebsd.org"
Re: devel/libevent shopstopper
On 21 February 2017 at 07:48, The Doctor wrote: > On Mon, Feb 20, 2017 at 12:35:41PM -0800, Kevin Oberman wrote: > > On Mon, Feb 20, 2017 at 11:57 AM, The Doctor > > wrote: > > > > > On Mon, Feb 20, 2017 at 05:55:46PM +, Jan Beich wrote: > > > > The Doctor writes: > > > > > > > > > We have a big one!! > > > > > > > > > > Libevent compiles but does not install > > > > > > > > > > ===> Installing for libevent-2.1.8 > > > > > ===> Checking if libevent already installed > > > > > ===> Registering installation for libevent-2.1.8 as automatic > > > > > Installing libevent-2.1.8... > > > > > pkg-static: libevent-2.1.8 conflicts with libevent2-2.1.8 (installs > > > > > files into the same place). Problematic file: > > > > > /usr/local/bin/event_rpcgen.py > > > > > *** Error code 70 > > > > > > > > > > Stop. > > > > > make[1]: stopped in /usr/ports/devel/libevent > > > > > *** Error code 1 > > > > > > > > > > Stop. > > > > > make: stopped in /usr/ports/devel/libevent > > > > > > > > > > ===>>> Installation of libevent-2.1.8 (devel/libevent) failed > > > > > ===>>> Aborting update > > > > > > > > > > ===>>> Update for devel/libevent failed > > > > > ===>>> Aborting update > > > > > > > > How did you invoke the build? portmaster and portupgrade are > supposed to > > > > look into /usr/ports/MOVED before proceeding. If they don't then > you're > > > > probably treading the unsupported territory[1] or encountered a bug. > > > > > > My sequence is > > > > > > pkg update -f > > > portsnap fetch update > > > portmaster -a > > > > > > Am I doing something wrong? > > > > > > > If you are building from ports, I'm not clear on why you do 'pkg update > > -f', but it should not hurt. > > > > Before running "portmaster -a", you should run "portmster -o > devel/libevent > > devel/libevent2". > > > > Just looking quickly at portmaster, it appears to deal with deleted ports > > and ports moved to a different location in the tree, but it does not look > > to me like it handles renamed ports properly. If someone who is better at > > shell scripting than I am wants to look at the code after line 1100, > maybe > > this could either be fixed or added. > > Is this a portmaster issue? > > > -- > > Kevin Oberman, Part time kid herder and retired Network Engineer > > E-mail: rkober...@gmail.com > > PGP Fingerprint: D03FB98AFA78E3B78C1694B318AB39EF1B055683 > > -- > Member - Liberal International This is doctor@@nl2k.ab.ca Ici doctor@@ > nl2k.ab.ca > Yahweh, Queen & country!Never Satan President Republic!Beware AntiChrist > rising! > http://www.fullyfollow.me/rootnl2k Look at Psalms 14 and 53 on Atheism > God is dead! Yahweh lives! Jesus his only begotten Son is the Risen > Saviour!! > ___ > freebsd-ports@freebsd.org mailing list > https://lists.freebsd.org/mailman/listinfo/freebsd-ports > To unsubscribe, send any mail to "freebsd-ports-unsubscr...@freebsd.org" > Unlikely to be a portmaster issue. If you look inside /usr/ports/UPDATING you're find some useful references to the way that portmaster handles name changes and John's "portmaster -o" advice is correct; its easy to miss that point in the man page ;) Perhaps its just a timing issue but both libevent2 and libcheck name changed broke our overnight builds. Unfortunately we didn't realise that we had a dependency until databases/memcached barfed. So we need to check /usr/ports/UPDATING and MOVED against a previous build to minimise that liklihood and catch dependencies. Upside is that we've just completed testing of synth, and decided to move the development servers to it. A recent post (from Bapt@) reaffirmed that the changes to /usr/ports is likely to break portmaster and other tools due to flavour's same origin. So rather than continue to rely upon a previously advocated tool, which is well suited to our very narrow purpose, its time to move. For those interested in synth but skittish: 1. install synth; read the manual 2. synth configure which places the synth.ini file in /usr/local/etc/synth and for testing purposes try 3. synth just-build $category/$portname; Example: synth just-build devel/check devel/libevent ftp/curl 4. Examine your logs in /var/log/synth Particularly 00_last_results.log and 02_failure_list.log 5. Examine your new packages in /var/synth/live_packages/All Gotchas: if you have complex make.conf file that pulls in other files, you will need to concatenate them into the one make.conf. If you have home grown build systems like we do, that have used portmaster since around 2005, its a big deal to change. We're looking forward to this incremental change. And if you use jails extensively, synth runs happily in a jail too - but this was against John Marinos advice, however we have strict functional separation here. ___ freebsd-ports@freebsd.org mailing list https://lists.freebsd.org/mailman/listinfo/freebsd-ports To unsubscribe, send any mail to "freebsd-por
Re: devel/libevent shopstopper
On Mon, Feb 20, 2017 at 12:35:41PM -0800, Kevin Oberman wrote: > On Mon, Feb 20, 2017 at 11:57 AM, The Doctor > wrote: > > > On Mon, Feb 20, 2017 at 05:55:46PM +, Jan Beich wrote: > > > The Doctor writes: > > > > > > > We have a big one!! > > > > > > > > Libevent compiles but does not install > > > > > > > > ===> Installing for libevent-2.1.8 > > > > ===> Checking if libevent already installed > > > > ===> Registering installation for libevent-2.1.8 as automatic > > > > Installing libevent-2.1.8... > > > > pkg-static: libevent-2.1.8 conflicts with libevent2-2.1.8 (installs > > > > files into the same place). Problematic file: > > > > /usr/local/bin/event_rpcgen.py > > > > *** Error code 70 > > > > > > > > Stop. > > > > make[1]: stopped in /usr/ports/devel/libevent > > > > *** Error code 1 > > > > > > > > Stop. > > > > make: stopped in /usr/ports/devel/libevent > > > > > > > > ===>>> Installation of libevent-2.1.8 (devel/libevent) failed > > > > ===>>> Aborting update > > > > > > > > ===>>> Update for devel/libevent failed > > > > ===>>> Aborting update > > > > > > How did you invoke the build? portmaster and portupgrade are supposed to > > > look into /usr/ports/MOVED before proceeding. If they don't then you're > > > probably treading the unsupported territory[1] or encountered a bug. > > > > My sequence is > > > > pkg update -f > > portsnap fetch update > > portmaster -a > > > > Am I doing something wrong? > > > > If you are building from ports, I'm not clear on why you do 'pkg update > -f', but it should not hurt. > > Before running "portmaster -a", you should run "portmster -o devel/libevent > devel/libevent2". > > Just looking quickly at portmaster, it appears to deal with deleted ports > and ports moved to a different location in the tree, but it does not look > to me like it handles renamed ports properly. If someone who is better at > shell scripting than I am wants to look at the code after line 1100, maybe > this could either be fixed or added. Is this a portmaster issue? > -- > Kevin Oberman, Part time kid herder and retired Network Engineer > E-mail: rkober...@gmail.com > PGP Fingerprint: D03FB98AFA78E3B78C1694B318AB39EF1B055683 -- Member - Liberal International This is doctor@@nl2k.ab.ca Ici doctor@@nl2k.ab.ca Yahweh, Queen & country!Never Satan President Republic!Beware AntiChrist rising! http://www.fullyfollow.me/rootnl2k Look at Psalms 14 and 53 on Atheism God is dead! Yahweh lives! Jesus his only begotten Son is the Risen Saviour!! ___ freebsd-ports@freebsd.org mailing list https://lists.freebsd.org/mailman/listinfo/freebsd-ports To unsubscribe, send any mail to "freebsd-ports-unsubscr...@freebsd.org"
Re: devel/libevent shopstopper
On Mon, Feb 20, 2017 at 11:57 AM, The Doctor wrote: > On Mon, Feb 20, 2017 at 05:55:46PM +, Jan Beich wrote: > > The Doctor writes: > > > > > We have a big one!! > > > > > > Libevent compiles but does not install > > > > > > ===> Installing for libevent-2.1.8 > > > ===> Checking if libevent already installed > > > ===> Registering installation for libevent-2.1.8 as automatic > > > Installing libevent-2.1.8... > > > pkg-static: libevent-2.1.8 conflicts with libevent2-2.1.8 (installs > > > files into the same place). Problematic file: > > > /usr/local/bin/event_rpcgen.py > > > *** Error code 70 > > > > > > Stop. > > > make[1]: stopped in /usr/ports/devel/libevent > > > *** Error code 1 > > > > > > Stop. > > > make: stopped in /usr/ports/devel/libevent > > > > > > ===>>> Installation of libevent-2.1.8 (devel/libevent) failed > > > ===>>> Aborting update > > > > > > ===>>> Update for devel/libevent failed > > > ===>>> Aborting update > > > > How did you invoke the build? portmaster and portupgrade are supposed to > > look into /usr/ports/MOVED before proceeding. If they don't then you're > > probably treading the unsupported territory[1] or encountered a bug. > > My sequence is > > pkg update -f > portsnap fetch update > portmaster -a > > Am I doing something wrong? > If you are building from ports, I'm not clear on why you do 'pkg update -f', but it should not hurt. Before running "portmaster -a", you should run "portmster -o devel/libevent devel/libevent2". Just looking quickly at portmaster, it appears to deal with deleted ports and ports moved to a different location in the tree, but it does not look to me like it handles renamed ports properly. If someone who is better at shell scripting than I am wants to look at the code after line 1100, maybe this could either be fixed or added. -- Kevin Oberman, Part time kid herder and retired Network Engineer E-mail: rkober...@gmail.com PGP Fingerprint: D03FB98AFA78E3B78C1694B318AB39EF1B055683 ___ freebsd-ports@freebsd.org mailing list https://lists.freebsd.org/mailman/listinfo/freebsd-ports To unsubscribe, send any mail to "freebsd-ports-unsubscr...@freebsd.org"
Re: devel/libevent shopstopper
On Mon, Feb 20, 2017 at 05:55:46PM +, Jan Beich wrote: > The Doctor writes: > > > We have a big one!! > > > > Libevent compiles but does not install > > > > ===> Installing for libevent-2.1.8 > > ===> Checking if libevent already installed > > ===> Registering installation for libevent-2.1.8 as automatic > > Installing libevent-2.1.8... > > pkg-static: libevent-2.1.8 conflicts with libevent2-2.1.8 (installs > > files into the same place). Problematic file: > > /usr/local/bin/event_rpcgen.py > > *** Error code 70 > > > > Stop. > > make[1]: stopped in /usr/ports/devel/libevent > > *** Error code 1 > > > > Stop. > > make: stopped in /usr/ports/devel/libevent > > > > ===>>> Installation of libevent-2.1.8 (devel/libevent) failed > > ===>>> Aborting update > > > > ===>>> Update for devel/libevent failed > > ===>>> Aborting update > > How did you invoke the build? portmaster and portupgrade are supposed to > look into /usr/ports/MOVED before proceeding. If they don't then you're > probably treading the unsupported territory[1] or encountered a bug. My sequence is pkg update -f portsnap fetch update portmaster -a Am I doing something wrong? > > [1] All installed packages should be upgraded together. Limiting upgrade > to just one package is a recipe for trouble. Ditto for port updates. > ___ > freebsd-ports@freebsd.org mailing list > https://lists.freebsd.org/mailman/listinfo/freebsd-ports > To unsubscribe, send any mail to "freebsd-ports-unsubscr...@freebsd.org" -- Member - Liberal International This is doctor@@nl2k.ab.ca Ici doctor@@nl2k.ab.ca Yahweh, Queen & country!Never Satan President Republic!Beware AntiChrist rising! http://www.fullyfollow.me/rootnl2k Look at Psalms 14 and 53 on Atheism God is dead! Yahweh lives! Jesus his only begotten Son is the Risen Saviour!! ___ freebsd-ports@freebsd.org mailing list https://lists.freebsd.org/mailman/listinfo/freebsd-ports To unsubscribe, send any mail to "freebsd-ports-unsubscr...@freebsd.org"
Re: devel/libevent shopstopper
The Doctor writes: > We have a big one!! > > Libevent compiles but does not install > > ===> Installing for libevent-2.1.8 > ===> Checking if libevent already installed > ===> Registering installation for libevent-2.1.8 as automatic > Installing libevent-2.1.8... > pkg-static: libevent-2.1.8 conflicts with libevent2-2.1.8 (installs > files into the same place). Problematic file: > /usr/local/bin/event_rpcgen.py > *** Error code 70 > > Stop. > make[1]: stopped in /usr/ports/devel/libevent > *** Error code 1 > > Stop. > make: stopped in /usr/ports/devel/libevent > > ===>>> Installation of libevent-2.1.8 (devel/libevent) failed > ===>>> Aborting update > > ===>>> Update for devel/libevent failed > ===>>> Aborting update How did you invoke the build? portmaster and portupgrade are supposed to look into /usr/ports/MOVED before proceeding. If they don't then you're probably treading the unsupported territory[1] or encountered a bug. [1] All installed packages should be upgraded together. Limiting upgrade to just one package is a recipe for trouble. Ditto for port updates. ___ freebsd-ports@freebsd.org mailing list https://lists.freebsd.org/mailman/listinfo/freebsd-ports To unsubscribe, send any mail to "freebsd-ports-unsubscr...@freebsd.org"
Re: devel/libevent shopstopper
On Mon, Feb 20, 2017 at 11:55:44AM -0500, Jim Ohlstein wrote: > Hello, > > On 02/20/2017 11:11 AM, The Doctor wrote: > > > > > > We have a big one!! > > Yup, it's a big one. That's why there's an entry in /usr/ports/UPDATING: > > 20170220: >AFFECTS: devel/libevent2 >AUTHOR: jbe...@freebsd.org > >libevent2 has been renamed back to libevent as the default version. >If you manage out of tree ports make sure to run the following: > > # pkg set -n libevent2:libevent > # pkg set -o devel/libevent2:devel/libevent That did the trick. Also why is my UPDATING file not updating? > > > > > Libevent compiles but does not install > > > > ===> Installing for libevent-2.1.8 > > ===> Checking if libevent already installed > > ===> Registering installation for libevent-2.1.8 as automatic > > Installing libevent-2.1.8... > > pkg-static: libevent-2.1.8 conflicts with libevent2-2.1.8 (installs files > > into the same place). Problematic file: /usr/local/bin/event_rpcgen.py > > *** Error code 70 > > > > Stop. > > make[1]: stopped in /usr/ports/devel/libevent > > *** Error code 1 > > > > Stop. > > make: stopped in /usr/ports/devel/libevent > > > > ===>>> Installation of libevent-2.1.8 (devel/libevent) failed > > ===>>> Aborting update > > > > ===>>> Update for devel/libevent failed > > ===>>> Aborting update > > > > Also > > > > pkg delete -f libevent > > Updating database digests format: 100% > > No packages matched for pattern 'libevent' > > > > Checking integrity... done (0 conflicting) > > Package(s) not found! > > > > Please fix!! > > > > Not surprising since that is the port that won't install on your system. > > Instead: > > # pkg delete -f libevent2 > > and then recompile devel/libevent and any ports that depend on it. > > -- > Jim Ohlstein > ___ > freebsd-ports@freebsd.org mailing list > https://lists.freebsd.org/mailman/listinfo/freebsd-ports > To unsubscribe, send any mail to "freebsd-ports-unsubscr...@freebsd.org" -- Member - Liberal International This is doctor@@nl2k.ab.ca Ici doctor@@nl2k.ab.ca Yahweh, Queen & country!Never Satan President Republic!Beware AntiChrist rising! http://www.fullyfollow.me/rootnl2k Look at Psalms 14 and 53 on Atheism God is dead! Yahweh lives! Jesus his only begotten Son is the Risen Saviour!! ___ freebsd-ports@freebsd.org mailing list https://lists.freebsd.org/mailman/listinfo/freebsd-ports To unsubscribe, send any mail to "freebsd-ports-unsubscr...@freebsd.org"
Re: devel/libevent shopstopper
On Mon, 20 Feb 2017 16:54:37 -, The Doctor wrote: On Mon, Feb 20, 2017 at 04:22:03PM -, Kevin Golding wrote: On Mon, 20 Feb 2017 16:11:09 -, The Doctor wrote: > pkg-static: libevent-2.1.8 conflicts with libevent2-2.1.8 (installs > files into the same place). Problematic file: devel/libevent2 has been replaced with devel/libevent Yes, we know!! Does that fix the above issue? Yes, the conflicts message tells you that you're trying to install devel/libevent when you already have devel/libevent2 installed. Since they're both version 2.1.8 you're installing two copies of the same thing so the conflict is logical. ___ freebsd-ports@freebsd.org mailing list https://lists.freebsd.org/mailman/listinfo/freebsd-ports To unsubscribe, send any mail to "freebsd-ports-unsubscr...@freebsd.org"
Re: devel/libevent shopstopper
On Mon, Feb 20, 2017 at 04:22:03PM -, Kevin Golding wrote: > On Mon, 20 Feb 2017 16:11:09 -, The Doctor > wrote: > > > > > > > We have a big one!! > > > > Libevent compiles but does not install > > > > ===> Installing for libevent-2.1.8 > > ===> Checking if libevent already installed > > ===> Registering installation for libevent-2.1.8 as automatic > > Installing libevent-2.1.8... > > pkg-static: libevent-2.1.8 conflicts with libevent2-2.1.8 (installs > > files into the same place). Problematic file: > > /usr/local/bin/event_rpcgen.py > > *** Error code 70 > > > > Stop. > > make[1]: stopped in /usr/ports/devel/libevent > > *** Error code 1 > > > > Stop. > > make: stopped in /usr/ports/devel/libevent > > > > ===>>> Installation of libevent-2.1.8 (devel/libevent) failed > > ===>>> Aborting update > > > > ===>>> Update for devel/libevent failed > > ===>>> Aborting update > > > > Also > > > > pkg delete -f libevent > > Updating database digests format: 100% > > No packages matched for pattern 'libevent' > > > > Checking integrity... done (0 conflicting) > > Package(s) not found! > > > > Please fix!! > > > > http://www.freshports.org/devel/libevent > > devel/libevent2 has been replaced with devel/libevent Yes, we know!! Does that fix the above issue? > ___ > freebsd-ports@freebsd.org mailing list > https://lists.freebsd.org/mailman/listinfo/freebsd-ports > To unsubscribe, send any mail to "freebsd-ports-unsubscr...@freebsd.org" -- Member - Liberal International This is doctor@@nl2k.ab.ca Ici doctor@@nl2k.ab.ca Yahweh, Queen & country!Never Satan President Republic!Beware AntiChrist rising! http://www.fullyfollow.me/rootnl2k Look at Psalms 14 and 53 on Atheism God is dead! Yahweh lives! Jesus his only begotten Son is the Risen Saviour!! ___ freebsd-ports@freebsd.org mailing list https://lists.freebsd.org/mailman/listinfo/freebsd-ports To unsubscribe, send any mail to "freebsd-ports-unsubscr...@freebsd.org"
Re: devel/libevent shopstopper
Hello, On 02/20/2017 11:11 AM, The Doctor wrote: We have a big one!! Yup, it's a big one. That's why there's an entry in /usr/ports/UPDATING: 20170220: AFFECTS: devel/libevent2 AUTHOR: jbe...@freebsd.org libevent2 has been renamed back to libevent as the default version. If you manage out of tree ports make sure to run the following: # pkg set -n libevent2:libevent # pkg set -o devel/libevent2:devel/libevent Libevent compiles but does not install ===> Installing for libevent-2.1.8 ===> Checking if libevent already installed ===> Registering installation for libevent-2.1.8 as automatic Installing libevent-2.1.8... pkg-static: libevent-2.1.8 conflicts with libevent2-2.1.8 (installs files into the same place). Problematic file: /usr/local/bin/event_rpcgen.py *** Error code 70 Stop. make[1]: stopped in /usr/ports/devel/libevent *** Error code 1 Stop. make: stopped in /usr/ports/devel/libevent ===>>> Installation of libevent-2.1.8 (devel/libevent) failed ===>>> Aborting update ===>>> Update for devel/libevent failed ===>>> Aborting update Also pkg delete -f libevent Updating database digests format: 100% No packages matched for pattern 'libevent' Checking integrity... done (0 conflicting) Package(s) not found! Please fix!! Not surprising since that is the port that won't install on your system. Instead: # pkg delete -f libevent2 and then recompile devel/libevent and any ports that depend on it. -- Jim Ohlstein ___ freebsd-ports@freebsd.org mailing list https://lists.freebsd.org/mailman/listinfo/freebsd-ports To unsubscribe, send any mail to "freebsd-ports-unsubscr...@freebsd.org"
Re: devel/libevent shopstopper
On Mon, 20 Feb 2017 16:11:09 -, The Doctor wrote: We have a big one!! Libevent compiles but does not install ===> Installing for libevent-2.1.8 ===> Checking if libevent already installed ===> Registering installation for libevent-2.1.8 as automatic Installing libevent-2.1.8... pkg-static: libevent-2.1.8 conflicts with libevent2-2.1.8 (installs files into the same place). Problematic file: /usr/local/bin/event_rpcgen.py *** Error code 70 Stop. make[1]: stopped in /usr/ports/devel/libevent *** Error code 1 Stop. make: stopped in /usr/ports/devel/libevent ===>>> Installation of libevent-2.1.8 (devel/libevent) failed ===>>> Aborting update ===>>> Update for devel/libevent failed ===>>> Aborting update Also pkg delete -f libevent Updating database digests format: 100% No packages matched for pattern 'libevent' Checking integrity... done (0 conflicting) Package(s) not found! Please fix!! http://www.freshports.org/devel/libevent devel/libevent2 has been replaced with devel/libevent ___ freebsd-ports@freebsd.org mailing list https://lists.freebsd.org/mailman/listinfo/freebsd-ports To unsubscribe, send any mail to "freebsd-ports-unsubscr...@freebsd.org"
devel/libevent shopstopper
We have a big one!! Libevent compiles but does not install ===> Installing for libevent-2.1.8 ===> Checking if libevent already installed ===> Registering installation for libevent-2.1.8 as automatic Installing libevent-2.1.8... pkg-static: libevent-2.1.8 conflicts with libevent2-2.1.8 (installs files into the same place). Problematic file: /usr/local/bin/event_rpcgen.py *** Error code 70 Stop. make[1]: stopped in /usr/ports/devel/libevent *** Error code 1 Stop. make: stopped in /usr/ports/devel/libevent ===>>> Installation of libevent-2.1.8 (devel/libevent) failed ===>>> Aborting update ===>>> Update for devel/libevent failed ===>>> Aborting update Also pkg delete -f libevent Updating database digests format: 100% No packages matched for pattern 'libevent' Checking integrity... done (0 conflicting) Package(s) not found! Please fix!! -- Member - Liberal International This is doctor@@nl2k.ab.ca Ici doctor@@nl2k.ab.ca Yahweh, Queen & country!Never Satan President Republic!Beware AntiChrist rising! http://www.fullyfollow.me/rootnl2k Look at Psalms 14 and 53 on Atheism God is dead! Yahweh lives! Jesus his only begotten Son is the Risen Saviour!! ___ freebsd-ports@freebsd.org mailing list https://lists.freebsd.org/mailman/listinfo/freebsd-ports To unsubscribe, send any mail to "freebsd-ports-unsubscr...@freebsd.org"
