FreeBSD ports you maintain which are out of date

[portscout]

Dear port maintainer,

The portscout new distfile checker has detected that one or more of your
ports appears to be out of date. Please take the opportunity to check
each of the ports listed below, and if possible and appropriate,
submit/commit an update. If any ports have already been updated, you can
safely ignore the entry.

You will not be e-mailed again for any of the port/version combinations
below.

Full details can be found at the following URL:
http://portscout.freebsd.org/po...@freebsd.org.html


Port| Current version | New version
+-+
japanese/rubygem-mail-iso-2022-jp   | 2.0.4   | 2.0.6
+-+
net/yaz | 5.19.0  | 5.20.2
+-+


If any of the above results are invalid, please check the following page
for details on how to improve portscout's detection and selection of
distfiles on a per-port basis:

http://portscout.freebsd.org/info/portscout-portconfig.txt

Thanks.
___
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: Expulsion of John Marino - reasons and impact?

[Dewayne Geraghty]

Some people collect brown pebbles, you know, those little maintainership
pebbles where people generously volunteer to keep ports up-to-date and
remain functioning on the various platforms.  Collecting these and
demonstrating an ongoing professional and technically competent
contribution, sometimes leads to the much coveted white pebbles, the ones
that denote recognition of technical abilities and ultimate providers of
source to the FreeBSD consumers – the larger family. They, the trusted
elite with their commit-bit.


Sometimes a commit bit is relinguished due to exhaustion or simply lack of
time for volunteer activities. But even these are held onto until the owner
feels like its time to hand-it-back. Rarely, very rarely is a commit bit
withdrawn and in such a public way as


https://svnweb.freebsd.org/ports?view=revision&revision=433827


Bryan quite rightly advised that negative discussion of an individual
shouldn’t be public.  Perhaps strange that it was the FreeBSD portmgr that
alluded to unacceptable and intractable behaviour which resulted in the
removal of the commit bit.  It’s appreciated that the maintainership of the
60+ ports, some quite complex (gcc6-aux and other compilers),


http://www.freshports.org/search.php?stype=maintainer&method=match&query=marino&num=30&orderby=category&orderbyupdown=asc&search=Search&format=html&branch=head

that John maintained was reinstated.  Mistakes happen but it is a concern
that the impression of automatic removal of maintainership rights had taken
hold - and without any discussion with the maintainer.


Unfortunately when you’ve held the white stone, once taken, diminishes the
motivation to retain the brown ones.

https://forums.freebsd.org/threads/59705/page-2#post-343136

So perhaps these ports, now semi-abandoned – difficult to acquire, easily
removed; are now likely to follow the familiar path of dormant PR’s and
eventually made available for others to adopt. An unintended consequence...


So that we can better understand the person, this is an interview with John
(jump to 21 minutes):

http://www.jupiterbroadcasting.com/93926/synthesize-all-the-things-bsd-
now-129/

Clearly a person proud of the recognition afforded by having a commit-bit
and as demonstrated by his ports contribution, deservedly so.


Sadly the lack of involvement by the Foundation is somewhat surprising,
even for a group that advocates a hands off approach; and for the FreeBSD
base, its probably warranted.  Unfortunate for that paradigm to apply in
the ports arena, a shame really.


Not retaining people of John Marino’s calibre is a loss, to push him out of
the Project is a travesty.  Such a strong word, but appropriate when the
REASON for his departure has not been revealed - to John!  Discussions that
affect someone’s professional reputation are held, decisions made and
without recourse, review or an opportunity for defence.  The victim remains
uninformed as to the cause.


I thank those of you that have mailed me privately.  We can only hope that
those that have the authority to look at the impact and the consequences of
this decision, properly review the efficacy of such, the consequences and
take the right action.  Which for those not privy to the impugned
horrendous and ongoing misconduct, are better served by having John inside
the FreeBSD family foistering the relationship between Dragonfly and
FreeBSD and others; continuing to provide packaging choice, a voice (one of
the few) that challenges the status quo; but mostly for his passion in
contributing to the project as a top contributor for 3 years!


To be clear, the only person that is ENTITLED to know the reason is John
Marino; it is then up to him to assess and whether it should be made
public.  That is the very least that should happen.

Regards, Dewayne
___
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: Make index fails with no entry for /usr/ports/audio/linux-c7-mikmod

[Vasil Dimov]

On Mon, Feb 20, 2017 at 19:28:55 +0100, Tijl Coosemans wrote:
> On Mon, 20 Feb 2017 08:35:55 +0200 Vasil Dimov  wrote:
> > This happens when emulators/linux_base-c7 is installed. Then
> > games/linux-uplink-demo/Makefile which contains "USE_LINUX=... mikmod
> > ..." picks up a dependency on audio/linux-c7-mikmod which does not
> > exist.
> > 
> > Should audio/linux-c7-mikmod be added, similarly to other?
> 
> I've removed the mikmod dependency in r434476 (and r434481) because it's
> no longer needed.
[...]

It works. Thanks!

-- 
Vasil Dimov
gro.DSBeerF@dv
%
Cutler Webster's Law:
There are two sides to every argument, unless a person
is personally involved, in which case there is only one.


signature.asc
Description: PGP signature

Re: devel/libevent shopstopper

[Peter Beckman]

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

[Dewayne Geraghty]

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

shutting down computer causes WindowMaker coredump

[Marco Beishuizen]

Hi,

I just discovered a really strange issue with my machine running FreeBSD 
11/amd64.


Sometimes WM coredumps when shutting down the computer from an xterm, 
using "shutdown -p now" (after closing all running programs). This is a 
small problem by itself, but the strange thing is that this *only* happens 
after I have upgraded firefox from ports. E.g today FF had a small update, 
I upgraded FF this afternoon and this evening when shutting down, WM 
coredumps.


Right now I can't see the relationship between WM, FF, shutting down and 
what can cause this.


Has anyone seen something like this before?

Regards,
Marco
--
Tax reform means "Don't tax you, don't tax me, tax that fellow behind
the tree."
-- Russell Long
___
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]

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

[Kevin Oberman]

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

[The Doctor]

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: qt5 fails to build

[tech-lists]

On 19/02/2017 20:44, Walter Schwarzenfeld wrote:
> Have the same problem.  (Maybe, it is a problem with libressl)
> Make this PR
> https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=217220

added your patch, recompiled & installed fine. Then I redid qt5-core,
then devel/qt5 and it's all ok now :D

many thanks,
-- 
J.
___
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: Make index fails with no entry for /usr/ports/audio/linux-c7-mikmod

[Tijl Coosemans]

On Mon, 20 Feb 2017 08:35:55 +0200 Vasil Dimov  wrote:
> This happens when emulators/linux_base-c7 is installed. Then
> games/linux-uplink-demo/Makefile which contains "USE_LINUX=... mikmod
> ..." picks up a dependency on audio/linux-c7-mikmod which does not
> exist.
> 
> Should audio/linux-c7-mikmod be added, similarly to other?

I've removed the mikmod dependency in r434476 (and r434481) because it's
no longer needed.  Mikmod is not provided by centos.org but by Fedora's
EPEL repository and for CentOS 7 this repository is amd64 only so it
would not work for this i386 game anyway.

> This is a diff between c6 and c7 ports, that could eventually cause
> similar problems:

Thanks, I've also removed naslibs from www/linux-opera in r434483.  The
other ports aren't causing any problems at moment I think.  I'll try to
keep an eye on it.
___
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: elf_load_section problem

[Steve Kargl]

On Mon, Feb 20, 2017 at 09:04:35AM +0100, Dimitry Andric wrote:
> On 19 Feb 2017, at 21:30, Steve Kargl  
> wrote:
> > ===>  Building for help2man-1.47.4
> > elf_load_section: truncated ELF file
> > Abort trap
> 
> but this looks like a half-written or empty file.  Did you do a full
> fsck, and did you already try cleaning out your work directory?
> 

Yes, I did.  It seems that the perl5.24 port was damaged
during one of the black screens of death events.  Removing
perl5.24 and re-installing seems to have fixed the help2man
problem.

I can 'kldload joy.ko'.  If I try to load any of drm.ko,
drm2.ko, or i915kms.ko.  Instant lock-up.  I have no 
idea how to get any more information about the lock-up.

This laptop, Dell Latitude D530, has worked very well with
FreeBSD with sources from Jan 31th and earlier.  Something
in the last month has been broken.

-- 
Steve
20161221 https://www.youtube.com/watch?v=IbCHE-hONow
___
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

[Jan Beich]

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

[The Doctor]

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: Fwd: 2017-02-18 Update to Qt 4 and Qt 5

[Robert_Burmeister]

I was able to fix the QT upgrade with minimal port deletions:

> pkg delete -f qt4-linguisttools-4.8.7
> pkg delete -f qt4-rcc-4.8.7
> cd /usr/ports/misc/qtchooser/ && make install clean
> pkg delete -f qt4-qmake-4.8.7
> cd /usr/ports/devel/qt4-qmake/ && make install clean
> cd /usr/ports/devel/qt4-linguisttools/ && make install clean
> cd /usr/ports/devel/qt4-rcc/ && make install clean

Portupgrade -arR was then able to finish the rest.

Though qt5-buildtools-5.7.1 failed and had to be retried manually.




--
View this message in context: 
http://freebsd.1045724.x6.nabble.com/Fwd-2017-02-18-Update-to-Qt-4-and-Qt-5-tp6168714p6169050.html
Sent from the freebsd-ports mailing list archive at Nabble.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

[Kevin Golding]

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

[The Doctor]

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

[Jim Ohlstein]

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"

Chromium on RPI2

[bob prohaska]

In playing with www/chromium on an RPI2 running -current I've gotten far 
enough to see the error

/usr/local/bin/python2.7: can't open file 
'./build/linux/unbundle/replace_gn_files.py': [Errno 2] No such file or 
directory

I realize that www/chromium isn't expected to work on ARM, but this error
does not seem ARM-specific.

If anyone can suggest a workaround I'd be pleased to try it. A brute-force
search for that filename found nothing.

Thanks for reading,

bob prohaska

___
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

[Kevin Golding]

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

[The Doctor]

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"

CRM Software Clients List

[Macy Johnson]

Hi,



Hope my email finds you well!



This is Macy, I hope you are the right person to discuss about Mailing List 
which includes complete contact details and Tele-verified Email addresses.



Are you interested in acquiring CRM Software Clients list for your marketing 
campaigns?



We also have other Technology Users like: Salesforce CRM, Microsoft CRM, SAP 
CRM, Business Intelligence Software (BI), Content & Collaboration Software, 
Database & File Management Software, Engineering Software, Enterprise Resource 
Planning Software (ERP), Financial, Legal & HR Software, Healthcare Software, 
Multimedia ,Games and graphics Software, Networking Software, Supply chain 
management Software(SCM), Security software, Storage & System Management 
Software, Retail Software  and many more.



If you're interested please let me know the geography and job title you are 
looking out to target for so that we can provide you with counts, pricing, 
sample file and more information in my next email.



Regards,

Macy Johnson

Business Data Analyst



If you wish not to receive these emails, please reply Remove in the subject 
line.




___
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: Problem with index

[Jason E. Hale]

On Mon, Feb 20, 2017 at 9:12 AM, Gerard Seibert  wrote:
> On Mon, 20 Feb 2017 13:41:41 +0100, Tijl Coosemans stated:
>
>>On Mon, 20 Feb 2017 12:29:47 + Matthew Seaman
>> wrote:
>>> On 2017/02/20 11:36, Gerard Seibert wrote:
 I just updated my ports tree using "portsnap". I then ran the
 following command:

 /usr/sbin/pkg version -vL=

 This resulted in the following message:

 postfix-current-3.2.20170129,4 >   succeeds index (index has
 3.2.0.r1,4)

 This does not seem correct. What is happening and how do I correct
 it?
>>>
>>> Your index file is out of date -- portsnap doesn't updated it
>>> because it changes too fast to be suitable for keeping in SVN.
>>>
>>> You need to
>>>
>>>   # make fetchindex
>>>
>>> from /usr/ports to download a pre-built index.  Or build your own, by
>>> 'make index'.  Or tell 'pkg version' to compare versions directly
>>> with what's in your ports tree by 'pkg version -vP=' (but this will
>>> be quite a bit slower).
>>
>>Portsnap should update the INDEX file.  Check /etc/portsnap.conf.
>>There should be a line like this: INDEX INDEX- DESCRIBE- where
>> is the major version of the FreeBSD release you have installed
>>(10, 11 or 12).
>
>
> Okay, I followed Matthew's advice and ran 'make index', but that did
> not change anything. The line described by Tiji is present and correct
> in the '/etc/portsnap.conf' file.
>
> Also, 'pkg version -vP=' bombs out with an "illegal option -- =". Sans
> the "=", it reports, "postfix-current-3.2.20170129,4 >   succeeds
> index (index has 3.2.0.r1,4), which is what was being reported
> previously.
>
> I even ran 'portsdb -Fu' which updated the index also. However, that
> did not correct the problem.
>
> I am open to suggestions.
>

I just went ahead and fixed the mail/postfix-current port.  If you run
portsnap again in 20-30 minutes, it should fix the problem you're
seeing.
___
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: Problem with index

[Gerard Seibert]

On Mon, 20 Feb 2017 13:41:41 +0100, Tijl Coosemans stated:

>On Mon, 20 Feb 2017 12:29:47 + Matthew Seaman
> wrote:
>> On 2017/02/20 11:36, Gerard Seibert wrote:  
>>> I just updated my ports tree using "portsnap". I then ran the
>>> following command:
>>> 
>>> /usr/sbin/pkg version -vL=
>>> 
>>> This resulted in the following message:
>>> 
>>> postfix-current-3.2.20170129,4 >   succeeds index (index has
>>> 3.2.0.r1,4)
>>> 
>>> This does not seem correct. What is happening and how do I correct
>>> it? 
>> 
>> Your index file is out of date -- portsnap doesn't updated it
>> because it changes too fast to be suitable for keeping in SVN.
>> 
>> You need to
>> 
>>   # make fetchindex
>> 
>> from /usr/ports to download a pre-built index.  Or build your own, by
>> 'make index'.  Or tell 'pkg version' to compare versions directly
>> with what's in your ports tree by 'pkg version -vP=' (but this will
>> be quite a bit slower).  
>
>Portsnap should update the INDEX file.  Check /etc/portsnap.conf.
>There should be a line like this: INDEX INDEX- DESCRIBE- where
> is the major version of the FreeBSD release you have installed
>(10, 11 or 12).


Okay, I followed Matthew's advice and ran 'make index', but that did
not change anything. The line described by Tiji is present and correct
in the '/etc/portsnap.conf' file.

Also, 'pkg version -vP=' bombs out with an "illegal option -- =". Sans
the "=", it reports, "postfix-current-3.2.20170129,4 >   succeeds
index (index has 3.2.0.r1,4), which is what was being reported
previously.

I even ran 'portsdb -Fu' which updated the index also. However, that
did not correct the problem.

I am open to suggestions.

-- 
Carmel
___
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: Problem with index

[Jason E. Hale]

On Mon, Feb 20, 2017 at 7:41 AM, Tijl Coosemans  wrote:
> On Mon, 20 Feb 2017 12:29:47 + Matthew Seaman  wrote:
>> On 2017/02/20 11:36, Gerard Seibert wrote:
>>> I just updated my ports tree using "portsnap". I then ran the following
>>> command:
>>>
>>> /usr/sbin/pkg version -vL=
>>>
>>> This resulted in the following message:
>>>
>>> postfix-current-3.2.20170129,4 >   succeeds index (index has 3.2.0.r1,4)
>>>
>>> This does not seem correct. What is happening and how do I correct it?
>>
>> Your index file is out of date -- portsnap doesn't updated it because it
>> changes too fast to be suitable for keeping in SVN.
>>
>> You need to
>>
>>   # make fetchindex
>>
>> from /usr/ports to download a pre-built index.  Or build your own, by
>> 'make index'.  Or tell 'pkg version' to compare versions directly with
>> what's in your ports tree by 'pkg version -vP=' (but this will be quite
>> a bit slower).
>
> Portsnap should update the INDEX file.  Check /etc/portsnap.conf.  There
> should be a line like this: INDEX INDEX- DESCRIBE- where  is the
> major version of the FreeBSD release you have installed (10, 11 or 12).
>

Your INDEX is probably fine. I think this is simply a case of
PORTEPOCH not getting bumped on the last update of
mail/postfix-current. 3.2.20170129,4 is numerically greater than the
current version of 3.2.0.r1,4. PORTEPOCH should be bumped to 5.
Maintainer of mail/postfix-current CC'd.
___
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"

froxlor port

[gianluca pego]

hi guys,
i don't know f this is the right place to come,
but froxlor package is no longer supported in freebs and right now is an 
outdated version
from their forum 
https://forum.froxlor.org/index.php?/topic/13196-support-for-freebsd/&page=2#comment-33279
the last free hosting panel for bsd has gone also
bye
___
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: Problem with index

[Tijl Coosemans]

On Mon, 20 Feb 2017 12:29:47 + Matthew Seaman  wrote:
> On 2017/02/20 11:36, Gerard Seibert wrote:
>> I just updated my ports tree using "portsnap". I then ran the following
>> command:
>> 
>> /usr/sbin/pkg version -vL=
>> 
>> This resulted in the following message:
>> 
>> postfix-current-3.2.20170129,4 >   succeeds index (index has 3.2.0.r1,4)
>> 
>> This does not seem correct. What is happening and how do I correct it?   
> 
> Your index file is out of date -- portsnap doesn't updated it because it
> changes too fast to be suitable for keeping in SVN.
> 
> You need to
> 
>   # make fetchindex
> 
> from /usr/ports to download a pre-built index.  Or build your own, by
> 'make index'.  Or tell 'pkg version' to compare versions directly with
> what's in your ports tree by 'pkg version -vP=' (but this will be quite
> a bit slower).

Portsnap should update the INDEX file.  Check /etc/portsnap.conf.  There
should be a line like this: INDEX INDEX- DESCRIBE- where  is the
major version of the FreeBSD release you have installed (10, 11 or 12).
___
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: Problem with index

[Matthew Seaman]

On 2017/02/20 11:36, Gerard Seibert wrote:
> I just updated my ports tree using "portsnap". I then ran the following
> command:
> 
> /usr/sbin/pkg version -vL=
> 
> This resulted in the following message:
> 
> postfix-current-3.2.20170129,4 >   succeeds index (index has 3.2.0.r1,4)
> 
> This does not seem correct. What is happening and how do I correct it?
> 

Your index file is out of date -- portsnap doesn't updated it because it
changes too fast to be suitable for keeping in SVN.

You need to

  # make fetchindex

from /usr/ports to download a pre-built index.  Or build your own, by
'make index'.  Or tell 'pkg version' to compare versions directly with
what's in your ports tree by 'pkg version -vP=' (but this will be quite
a bit slower).

Cheers,

Matthew






signature.asc
Description: OpenPGP digital signature

Problem with index

[Gerard Seibert]

I just updated my ports tree using "portsnap". I then ran the following
command:

/usr/sbin/pkg version -vL=

This resulted in the following message:

postfix-current-3.2.20170129,4 >   succeeds index (index has 3.2.0.r1,4)

This does not seem correct. What is happening and how do I correct it?

-- 
Carmel
___
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: Odd daily security run output message

[Mathieu Arnold]

Le 19/02/2017 à 09:52, Mike Clarke a écrit :
> On Sat, 18 Feb 2017 15:45:12 -0800
> Kevin Oberman  wrote:
>
>> This belongs here because the message is a muddled mess. It might belong to
>> gnome@ because I am only aware that gnome is the remaining ports user of
>> this port. (I'm quite possibly wrong about this.)
>>
>> It's telling you (very poorly) that Samba v3.6 is no longer supported by
>> the samba folks and you should stop using it and that it is scheduled to be
>> deleted at hte end of June.
> It's not just gnome. Kde4 requires it too:
>
> curlew:/home/mike% pkg info -r samba36-libsmbclient-3.6.25_2
> samba36-libsmbclient-3.6.25_2:
> gvfs-1.26.3_2
> gnome-vfs-2.24.4_4
> kde-runtime-4.14.3_4
>

This is currently being worked on, the only samba installing
libsmbclient is samba36 and it is so that it does not conflict with
samba4*, but samba4 could install a libsmbclient. This needs a bit of
thinking, and a DEFAULT_VERSIONS+=samba=xx.


-- 
Mathieu Arnold




signature.asc
Description: OpenPGP digital signature

FreeBSD ports you maintain which are out of date

[portscout]

Dear port maintainer,

The portscout new distfile checker has detected that one or more of your
ports appears to be out of date. Please take the opportunity to check
each of the ports listed below, and if possible and appropriate,
submit/commit an update. If any ports have already been updated, you can
safely ignore the entry.

You will not be e-mailed again for any of the port/version combinations
below.

Full details can be found at the following URL:
http://portscout.freebsd.org/po...@freebsd.org.html


Port| Current version | New version
+-+
databases/py-apsw   | 3.14.1  | 3.17.0-r1
+-+
games/lm-solve  | 0.8.4   | 0.10.0
+-+


If any of the above results are invalid, please check the following page
for details on how to improve portscout's detection and selection of
distfiles on a per-port basis:

http://portscout.freebsd.org/info/portscout-portconfig.txt

Thanks.
___
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: elf_load_section problem

[Dimitry Andric]

On 19 Feb 2017, at 21:30, Steve Kargl  wrote:
> 
> Looks like I picked the wrong time to update a month old.
> 
> Problem #1: 'kldload -v i915kms.ko' locks up the system.  No
> panic.  No messages logged.  No keyboard response.  Black
> screen of death.
> 
> Problem #2: 'kldload -v drm2.ko' locks up the system. No panic.
> No messages logged.  No keyboard response.  Black screen of death.
> 
> Problem #3: #1 and #2 along with an update of xorg to 1.18.4
> prevents X from firing up.
> 
> Problem #4: Ok. I re-install everything that X uses and their
> dependencies from source.

I can't help you with these...


> ===>  Building for help2man-1.47.4
> elf_load_section: truncated ELF file
> Abort trap

but this looks like a half-written or empty file.  Did you do a full
fsck, and did you already try cleaning out your work directory?

-Dimitry



signature.asc
Description: Message signed with OpenPGP