Re: lang/gcc and tmpfs no space let on device
On Fri, May 16, 2014 at 02:43:09PM +0200, Marko Cupa?? wrote: > Hi, > > I am using 10.0-RELEASE-p3 amd64, and am trying to build lang/gcc as a > dependency for emulators/virtualbox-ose. Building fails giving the > following messages: > > jc1: fatal error: error writing to /tmp/ccwgXZ8m.s: No space left on > device compilation terminated. > gmake[5]: *** [javax/crypto/spec.lo] Error 1 > gmake[5]: *** Waiting for unfinished jobs > [...] > > I am using 128mb tmpfs file system mounted at /tmp: > tmpfs /tmp tmpfs rw,size=128m,mode=1777 0 0 tmpfs-backed WRKDIR is certainly possible with lang/gcc* ports, albeit I'm not sure if 128MB is enough. However, normally I never limit tmpfs size, but try to provide sufficient swap space. That said, I observed similar "no space left on device" errors even on a box with 16GB of RAM when building lang/gcc *with default options*, which includes JAVA. > Does anyone know how big /tmp do I need to have in order to compile > lang/gcc successfully? I always patch all lang/gcc* ports locally like this: -OPTIONS_DEFAULT_i386=JAVA -OPTIONS_DEFAULT_amd64= JAVA +#OPTIONS_DEFAULT_i386= JAVA +#OPTIONS_DEFAULT_amd64= JAVA It allows to use tmpfs-backed storage of sane sizes to build them. I once wondered why is JAVA in the defaults anyways; someone gave me the reason, which I cannot remember right now. ./danfe ___ freebsd-ports@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-ports To unsubscribe, send any mail to "freebsd-ports-unsubscr...@freebsd.org"
Re: Poudriere & Haskell ports "Options changed, deleting" every time
On 21/05/2014 04:30, J David wrote: > Whenever I build a ports list with Haskell modules in it, poudriere > insists on rebuilding those Haskell modules every time, claiming the > options have changed. The options haven't changed; it will happily > report this even if run twice in a row on a system with no other > activity in between: [...] > Does anyone have any idea where I should look to figure this out? Is > there a way to manually see what the "before and after" options are > that poudriere is looking at to determine that something has changed? Try CHECK_CHANGED_OPTIONS=verbose in /usr/local/etc/poudriere.conf ? Cheers, Matthew -- Dr Matthew J Seaman MA, D.Phil. PGP: http://www.infracaninophile.co.uk/pgpkey JID: matt...@infracaninophile.co.uk signature.asc Description: OpenPGP digital signature
Re: Done with this port
Am 21.05.2014 03:49, schrieb Paul Schmehl: > Thanks. With some of my ports I have been really struggling trying to > get staging working. I'd be very interested to see what you did, since > it was apparently easy for you to do. A bit of experience with packaging helped indeed. The differences are visible in this automated message: http://lists.freebsd.org/pipermail/svn-ports-head/2014-May/058212.html The INSTALL_TARGET that sets the INSTALL_ROOT (supported by iwidget's Makefile) is useful, and more help (for the MANN conversion) is available on the FreeBSD Wiki: http://wiki.freebsd.org/ports/StageDir/ ___ freebsd-ports@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-ports To unsubscribe, send any mail to "freebsd-ports-unsubscr...@freebsd.org"
Re: PORT META: Installed files conflict between ports
On Tue, May 20, 2014 at 6:53 PM, Robert Backhaus wrote:
> The fact that those two ports install conflicting binaries isn't a problem.
> The problem is that you were allowed to install the second port.
>
> With mplayer, there is a correct CONFLICTS line in mplayer2, but does not
> appear to be one in mplayer. But both samba ports seem to have the correct
> CONFLICTS line, but that may have been fixed after you installed the port.
>
>
> On 21 May 2014 08:25, Ronald F. Guilmette wrote:
>
> >
> > I just submitted the following PR:
> >
> > http://www.freebsd.org/cgi/query-pr.cgi?pr=190027
> >
> > I was a bit flabberghasted to believe that such file conflicts between
> > ports was even possible. Seeing that it is possible prompted me to
> > write the attached small Perl script, which can quickly find all such
> > cases among a set of installed ports on a given system.
> >
> > To use this simple script, place it somewhere on your path and name
> > it "pccheck" (Port Conflict Check). Then do the following:
> >
> > cd /var/db/pkg
> > pccheck *
> >
> > That will tell you if any of your installed ports have installed any
> > files which any other of your installed ports also believe that they
> > also have installed.
> >
> > When I ran it on my system, I got this, which is worrying, to say the
> > least:
> >
> > mplayer2-2.0.20130428_4: Conflict -- file=/usr/local/bin/mplayer
> > pkg=mplayer-1.1.r20140418
> > mplayer2-2.0.20130428_4: Conflict --
> file=/usr/local/man/man1/mplayer.1.gz
> > pkg=mplayer-1.1.r20140418
> > samba36-nmblookup-3.6.23: Conflict -- file=/usr/local/bin/nmblookup
> > pkg=samba36-3.6.23
> > samba36-nmblookup-3.6.23: Conflict --
> > file=/usr/local/man/man1/nmblookup.1.gz pkg=samba36-3.6.23
> > samba36-nmblookup-3.6.23: Conflict --
> > file=/usr/local/man/man5/smb.conf.5.gz pkg=samba36-3.6.23
> >
> > How does this sort of problem even creep in (to the ports tree)? Is
> > there nothing in place which prevents it from arising?
> >
> >
> >
>
> > #!/usr/bin/perl -w
> >
> > use strict;
> >
> > my $origin;
> > my %installed_files;
> >
> > foreach my $arg (@ARGV) {
> > next unless (-d "$arg");
> > open (IFILE, "<$arg/+CONTENTS") || die "$arg: Open failed\n";
> > while (my $line = ) {
> > chop $line;
> > if ($line =~ m/^\@/) {
> > if ($line =~ m/^\@conflicts /) {
> > #print STDERR ("$arg: $line\n");
> > # do nothing
> > } elsif ($line =~ m/^\@cwd /) {
> > $origin = $';
> > } else {
> > # do nothing
> > }
> > } else {
> > next if ($line =~ m/^\+[A-Z]/);
> > die "$arg: Origin not defined\n" unless (defined ($origin));
> > my $fullpath = "$origin/$line";
> > # print "$fullpath\n";
> > if (exists ($installed_files{$fullpath})) {
> > print STDERR ("$arg: Conflict -- file=$fullpath
> > pkg=$installed_files{$fullpath}\n");
> > } else {
> > $installed_files{$fullpath} = $arg;
> > }
> > }
> > }
> > close (IFILE);
> > }
> >
>
The old pkg system did not check or block the installation of files over
existing files installed by a different port. pkgng does, so these will
all be eventually caught.
It is not clear to me whether the pkg2pkgng conversion process will catch
these. Since the loading of identical packing list files into the SQL
database should not be possible, I woul axpect it to, bu it may just spit
out error messages and either replace the old entry with the new or leave
the old one in place.
--
R. Kevin Oberman, Network Engineer, Retired
E-mail: rkober...@gmail.com
___
freebsd-ports@freebsd.org mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-ports
To unsubscribe, send any mail to "freebsd-ports-unsubscr...@freebsd.org"
Poudriere & Haskell ports "Options changed, deleting" every time
Whenever I build a ports list with Haskell modules in it, poudriere insists on rebuilding those Haskell modules every time, claiming the options have changed. The options haven't changed; it will happily report this even if run twice in a row on a system with no other activity in between: >> Options changed, deleting: hs-HTTP-4000.2.8_4.txz >> Options changed, deleting: hs-HUnit-1.2.5.2_4.txz >> Options changed, deleting: hs-HaXml-1.24_4.txz >> Options changed, deleting: hs-MonadCatchIO-mtl-0.3.0.5_6.txz >> Options changed, deleting: hs-QuickCheck-2.6_4.txz >> Options changed, deleting: hs-SHA-1.6.1_6.txz >> Options changed, deleting: hs-alex-3.0.5_4.txz >> Options changed, deleting: hs-ansi-terminal-0.6_5.txz >> Options changed, deleting: hs-ansi-wl-pprint-0.6.6_6.txz >> Options changed, deleting: hs-cabal-install-1.16.0.2_4.txz >> Options changed, deleting: hs-cgi-3001.1.7.5_4,1.txz >> Options changed, deleting: hs-curl-1.3.8_7.txz >> Options changed, deleting: hs-dataenc-0.14.0.5_5.txz >> Options changed, deleting: hs-dlist-0.5_13.txz >> Options changed, deleting: hs-darcs-2.8.4_6.txz >> Options changed, deleting: hs-extensible-exceptions-0.1.1.4_4.txz >> Options changed, deleting: hs-ghc-paths-0.1.0.9_5.txz >> Options changed, deleting: hs-haddock-2.13.2_4.txz >> Options changed, deleting: hs-happy-1.18.10_6.txz >> Options changed, deleting: hs-hostname-1.0_12.txz >> Options changed, deleting: hs-hashed-storage-0.5.10_6.txz >> Options changed, deleting: hs-haskeline-0.7.0.3_5.txz >> Options changed, deleting: hs-hscolour-1.20.3_6,1.txz >> Options changed, deleting: hs-html-1.0.1.2_11.txz >> Options changed, deleting: hs-mmap-0.5.8_7.txz >> Options changed, deleting: hs-mtl-2.1.2_6.txz >> Options changed, deleting: hs-network-2.4.1.2_4.txz >> Options changed, deleting: hs-parsec-3.1.3_6.txz >> Options changed, deleting: hs-primitive-0.5.0.1_6.txz >> Options changed, deleting: hs-polyparse-1.9_4.txz >> Options changed, deleting: hs-random-1.0.1.1_8.txz >> Options changed, deleting: hs-regex-base-0.93.2_11.txz >> Options changed, deleting: hs-regex-compat-0.95.1_9.txz >> Options changed, deleting: hs-stringsearch-0.3.6.4_6.txz >> Options changed, deleting: hs-regex-posix-0.95.2_6.txz >> Options changed, deleting: hs-tar-0.4.0.1_6.txz >> Options changed, deleting: hs-test-framework-0.8_7.txz >> Options changed, deleting: hs-text-0.11.3.1_4.txz >> Options changed, deleting: hs-transformers-0.3.0.0_8.txz >> Options changed, deleting: hs-test-framework-quickcheck2-0.3.0.1_7.txz >> Options changed, deleting: hs-test-framework-hunit-0.3.0_7.txz >> Options changed, deleting: hs-unix-compat-0.4.1.1_4.txz >> Options changed, deleting: hs-utf8-string-0.3.7_9.txz >> Options changed, deleting: hs-xhtml-3000.2.1_8.txz >> Options changed, deleting: hs-zlib-0.5.4.1_4.txz >> Options changed, deleting: hs-xml-1.3.13_4.txz >> Options changed, deleting: hs-vector-0.10.0.1_6.txz The actual Haskell language port itself isn't affected, just the modules. The packages do build successfully every time. It's pretty much certain that this is a result of something silly I've done, rather than a defect in poudriere, but I'm baffled as to what it could be. Nothing I do with "poudriere options" seems to affect it. Does anyone have any idea where I should look to figure this out? Is there a way to manually see what the "before and after" options are that poudriere is looking at to determine that something has changed? Thanks for any advice! ___ freebsd-ports@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-ports To unsubscribe, send any mail to "freebsd-ports-unsubscr...@freebsd.org"
Re: PORT META: Installed files conflict between ports
The fact that those two ports install conflicting binaries isn't a problem.
The problem is that you were allowed to install the second port.
With mplayer, there is a correct CONFLICTS line in mplayer2, but does not
appear to be one in mplayer. But both samba ports seem to have the correct
CONFLICTS line, but that may have been fixed after you installed the port.
On 21 May 2014 08:25, Ronald F. Guilmette wrote:
>
> I just submitted the following PR:
>
> http://www.freebsd.org/cgi/query-pr.cgi?pr=190027
>
> I was a bit flabberghasted to believe that such file conflicts between
> ports was even possible. Seeing that it is possible prompted me to
> write the attached small Perl script, which can quickly find all such
> cases among a set of installed ports on a given system.
>
> To use this simple script, place it somewhere on your path and name
> it "pccheck" (Port Conflict Check). Then do the following:
>
> cd /var/db/pkg
> pccheck *
>
> That will tell you if any of your installed ports have installed any
> files which any other of your installed ports also believe that they
> also have installed.
>
> When I ran it on my system, I got this, which is worrying, to say the
> least:
>
> mplayer2-2.0.20130428_4: Conflict -- file=/usr/local/bin/mplayer
> pkg=mplayer-1.1.r20140418
> mplayer2-2.0.20130428_4: Conflict -- file=/usr/local/man/man1/mplayer.1.gz
> pkg=mplayer-1.1.r20140418
> samba36-nmblookup-3.6.23: Conflict -- file=/usr/local/bin/nmblookup
> pkg=samba36-3.6.23
> samba36-nmblookup-3.6.23: Conflict --
> file=/usr/local/man/man1/nmblookup.1.gz pkg=samba36-3.6.23
> samba36-nmblookup-3.6.23: Conflict --
> file=/usr/local/man/man5/smb.conf.5.gz pkg=samba36-3.6.23
>
> How does this sort of problem even creep in (to the ports tree)? Is
> there nothing in place which prevents it from arising?
>
>
>
> #!/usr/bin/perl -w
>
> use strict;
>
> my $origin;
> my %installed_files;
>
> foreach my $arg (@ARGV) {
> next unless (-d "$arg");
> open (IFILE, "<$arg/+CONTENTS") || die "$arg: Open failed\n";
> while (my $line = ) {
> chop $line;
> if ($line =~ m/^\@/) {
> if ($line =~ m/^\@conflicts /) {
> #print STDERR ("$arg: $line\n");
> # do nothing
> } elsif ($line =~ m/^\@cwd /) {
> $origin = $';
> } else {
> # do nothing
> }
> } else {
> next if ($line =~ m/^\+[A-Z]/);
> die "$arg: Origin not defined\n" unless (defined ($origin));
> my $fullpath = "$origin/$line";
> # print "$fullpath\n";
> if (exists ($installed_files{$fullpath})) {
> print STDERR ("$arg: Conflict -- file=$fullpath
> pkg=$installed_files{$fullpath}\n");
> } else {
> $installed_files{$fullpath} = $arg;
> }
> }
> }
> close (IFILE);
> }
> ___
> freebsd-ports@freebsd.org mailing list
> http://lists.freebsd.org/mailman/listinfo/freebsd-ports
> To unsubscribe, send any mail to "freebsd-ports-unsubscr...@freebsd.org"
>
___
freebsd-ports@freebsd.org mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-ports
To unsubscribe, send any mail to "freebsd-ports-unsubscr...@freebsd.org"
Re: Done with this port
--On May 20, 2014 at 8:53:36 PM +0200 Matthias Andree wrote: Am 20.05.2014 18:49, schrieb Paul Schmehl: I'm giving up x11-toolkits/iwidgets. Someone else can wrestle this thing into compliance with STAGE. I've beaten my head against that damn wall long enough. If no one takes it, it dies in June. Staging may kill a lot of ports. I'm not longer the maintainer for that one. Paul, Thank you for maintaining the port thus far. However, I have just committed a port upgrade to convert it to staging (SVN revision 354666). Would you be willing to continue maintaining this port with this particular obstacle out of your way? Please let us know ASAP, and please Cc: me on your reply. Thanks. With some of my ports I have been really struggling trying to get staging working. I'd be very interested to see what you did, since it was apparently easy for you to do. I guess I'll keep maintainership for now. I'm retiring in about 18 months, so I may have to give all my ports up then. Paul Schmehl, Senior Infosec Analyst As if it wasn't already obvious, my opinions are my own and not those of my employer. *** "It is as useless to argue with those who have renounced the use of reason as to administer medication to the dead." Thomas Jefferson "There are some ideas so wrong that only a very intelligent person could believe in them." George Orwell ___ freebsd-ports@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-ports To unsubscribe, send any mail to "freebsd-ports-unsubscr...@freebsd.org"
PORT META: Installed files conflict between ports
I just submitted the following PR:
http://www.freebsd.org/cgi/query-pr.cgi?pr=190027
I was a bit flabberghasted to believe that such file conflicts between
ports was even possible. Seeing that it is possible prompted me to
write the attached small Perl script, which can quickly find all such
cases among a set of installed ports on a given system.
To use this simple script, place it somewhere on your path and name
it "pccheck" (Port Conflict Check). Then do the following:
cd /var/db/pkg
pccheck *
That will tell you if any of your installed ports have installed any
files which any other of your installed ports also believe that they
also have installed.
When I ran it on my system, I got this, which is worrying, to say the
least:
mplayer2-2.0.20130428_4: Conflict -- file=/usr/local/bin/mplayer
pkg=mplayer-1.1.r20140418
mplayer2-2.0.20130428_4: Conflict -- file=/usr/local/man/man1/mplayer.1.gz
pkg=mplayer-1.1.r20140418
samba36-nmblookup-3.6.23: Conflict -- file=/usr/local/bin/nmblookup
pkg=samba36-3.6.23
samba36-nmblookup-3.6.23: Conflict -- file=/usr/local/man/man1/nmblookup.1.gz
pkg=samba36-3.6.23
samba36-nmblookup-3.6.23: Conflict -- file=/usr/local/man/man5/smb.conf.5.gz
pkg=samba36-3.6.23
How does this sort of problem even creep in (to the ports tree)? Is
there nothing in place which prevents it from arising?
#!/usr/bin/perl -w
use strict;
my $origin;
my %installed_files;
foreach my $arg (@ARGV) {
next unless (-d "$arg");
open (IFILE, "<$arg/+CONTENTS") || die "$arg: Open failed\n";
while (my $line = ) {
chop $line;
if ($line =~ m/^\@/) {
if ($line =~ m/^\@conflicts /) {
#print STDERR ("$arg: $line\n");
# do nothing
} elsif ($line =~ m/^\@cwd /) {
$origin = $';
} else {
# do nothing
}
} else {
next if ($line =~ m/^\+[A-Z]/);
die "$arg: Origin not defined\n" unless (defined ($origin));
my $fullpath = "$origin/$line";
# print "$fullpath\n";
if (exists ($installed_files{$fullpath})) {
print STDERR ("$arg: Conflict -- file=$fullpath
pkg=$installed_files{$fullpath}\n");
} else {
$installed_files{$fullpath} = $arg;
}
}
}
close (IFILE);
}
___
freebsd-ports@freebsd.org mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-ports
To unsubscribe, send any mail to "freebsd-ports-unsubscr...@freebsd.org"
FreeBSD Port: comms/hylafax
Hello, I have a fresh install of Freebsd 10, trying to use hylafax. The faxgetty program which answers incoming fax calls hangs and uses 100% of the cpu. The hylafax guys suggest it is an OS problem. I am thinking about rolling back to Freebsd 9 and give it a go, but before I do would you guys like any info from my system that might help troubleshoot? Brandon Gabert Direct 780.912.2300 Office 780.998.3771 ___ freebsd-ports@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-ports To unsubscribe, send any mail to "freebsd-ports-unsubscr...@freebsd.org"
Need help getting docbook mess unsnarled
I rarely update my installed ports. I do it only every few months. Unfortunately, when I tried to do it a few days ago (using "portupgrade -a") I neglected to read over the last several thousand lines of the UPDATING file, in particular this entry: 20140219: AFFECTS: users of textproc/docbook* AUTHOR: m...@freebsd.org The textproc/docbook-* ports have been consolidated into two ports textproc/docbook-sgml and textproc/docbook-xml. Before upgrading you should force the removal of the existing ports, they will conflict with the new ones. pkg users can run: pkg delete -f docbook-xml\* docbook-sk\* docbook\[2345\]\?\?-\* docbook-4\* the other users can run: pkg_delete -f docbook-xml\* docbook-sk\* docbook\[2345\]\?\?-\* docbook-4\* So, um, naturally, a whole bunch of my port updates failed, whereupon I went and read the UPDATING file and found the note quoted above. Upon seeing this I did as suggested, albeit after having already tried to update everything: pkg_delete -f docbook-xml\* docbook-sk\* docbook\[2345\]\?\?-\* docbook-4\* Now it seems that my installed ports are still all messed up, and I seem to have two different version of the docbook port installed. (See below.) What must I do in order to untangle all this? I've tried removing some of the packages mentioned below, but pkg_delete won't let me because they have other things dependent upon them. Do I have to delete each and every one of those installed ports too, then delete the ``bad'' (obsolete) docbbook-* things, and then just manually reinstall all of the dependent ports? Another question: If one had... at some prior point in time... installed some package `X', and if one subsequently then did a "portinstall X", would that be an OK thing to do? I'm worried/paranoid about doing this because I am aware of the fact that when one is manually building & installing ports, particularly ones that have previously been installed, then one is supposed to do "make deinstall" and then "make reinstall". Obviously, there is some magic that is associated with these specific make targets... in particular "make reinstall"... and I don't know if that required magic is or is not incorporated into portinstall. So I'm worried about using portinstall for anything that was every previously installed. Will anything get messed up if I do? P.S. Yes, yes. I know. I'm supposed to be using pkgng. I haven't had the time yet to familiarize myself with that. I still have until September to convert myself, right? % pkg_info docbook\* Information for docbook-1.5: Comment: Meta-port for the different versions of the DocBook DTD Required by: brasero-2.32.1_6 docbook-xsl-1.76.1_2 evince-2.32.0_11 gimp-app-2.8.10_2,1 gimp-gutenprint-5.2.8 gnome-desktop-2.32.1_5 gnome-doc-utils-0.20.10_2 gnome-mount-0.8_12 gthumb-2.14.1_8 gtk-doc-1.18_1 gvfs-1.12.3_2 nautilus-2.32.2.1_6 policykit-gnome-0.9.2_7 py27-gimp-2.8.10_1 rarian-0.8.1_1 xmlto-0.0.26_1 yelp-2.30.2_7 Description: A meta-port for the DocBook DTD. This port depends upon the docbook-* ports, to ensure that they are installed correctly. WWW: http://www.oasis-open.org/docbook/ Information for docbook-5.0_1: Comment: DocBook 5.0, designed for technical documentation Required by: brasero-2.32.1_6 docbook-1.5 docbook-xsl-1.76.1_2 evince-2.32.0_11 gimp-app-2.8.10_2,1 gimp-gutenprint-5.2.8 gnome-desktop-2.32.1_5 gnome-doc-utils-0.20.10_2 gnome-mount-0.8_12 gthumb-2.14.1_8 gtk-doc-1.18_1 gvfs-1.12.3_2 nautilus-2.32.2.1_6 policykit-gnome-0.9.2_7 py27-gimp-2.8.10_1 rarian-0.8.1_1 xmlto-0.0.26_1 yelp-2.30.2_7 Description: DocBook is a general purpose XML schema particularly well suited to books and papers about computer hardware and software (though it is by no means limited to these applications). The Version 5.0 release is a complete rewrite of DocBook in RELAX NG. The intent of this rewrite is to produce a schema that is true to the spirit of DocBook while simultaneously removing inconsistencies that have arisen as a natural consequence of DocBook's long, slow evolution. The Technical Committee has taken this opportunity to simplify a number of content models and tighten constraints where RELAX NG makes that possible. The Technical Committee provides the DocBook 5.0 schema in other schema languages, including W3C XML Schema and an XML DTD, but the RELAX NG Schema is now the normative schema. WWW: http://www.docbook.org/specs/docbook-5.0-spec-cd-04.html Information for docbook-sgml-4.5_1: Comment: DocBook SGML DTD Required by: brasero-2.32.1_6 docbook-1.5 docbook-xsl-1.76.1_2 evince-2.32.0_11 gimp-app-2.8.10_2,1 gimp-gutenprint-5.2.8 gnome-desktop-2.32.1_5 gnome-doc-utils-0.20.10_2 gnome-mount-0.8_12 gthumb-2.14.1_8 gtk-doc-1.18_1 gvfs-1.12.
Re: Staging issue with staging of net-im/libpurple (libtool?)
On Tue, 20 May 2014 08:52:46 -0700 Kevin Oberman wrote: > Removed the FIND and re-built. After the build I looked in > stage/usr/local/lib and the .so.0 files are still present! I then installed > with no errors. I'll admit that I don't understand what is happening or why > the touch of the files would break things, but it seems to be fixed, now. The touch didn't always give all files the same timestamp so sometimes make thought the configure script was out of date and regenerated it erasing any patches that had been applied to it. > Thanks, Tijl. (Some day I'd like to know how "Tijl" is pronounced.) It's difficult to explain in English. My name is actually Tijl (3 letters) with ij being some sort of vowel. There's a fairly long article about it on wikipedia: https://en.wikipedia.org/wiki/IJ_%28digraph%29 It sounds like this: http://www.dutchgrammar.com/sound/y.mp3 Then just add t and l :) ___ freebsd-ports@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-ports To unsubscribe, send any mail to "freebsd-ports-unsubscr...@freebsd.org"
Re: Done with this port
Am 20.05.2014 18:49, schrieb Paul Schmehl: > I'm giving up x11-toolkits/iwidgets. Someone else can wrestle this > thing into compliance with STAGE. I've beaten my head against that damn > wall long enough. If no one takes it, it dies in June. Staging may > kill a lot of ports. I'm not longer the maintainer for that one. > Paul, Thank you for maintaining the port thus far. However, I have just committed a port upgrade to convert it to staging (SVN revision 354666). Would you be willing to continue maintaining this port with this particular obstacle out of your way? Please let us know ASAP, and please Cc: me on your reply. Cheers, Matthias signature.asc Description: OpenPGP digital signature
Re: Net-SNMP conflict
On 20/05/2014 18:34, Richard Kuhns wrote: > So doesn't that mean that the net-snmp port is doing things wrong? If > pkg *isn't* installed it's pretty safe to say that net-snmpd is not > going to be able to use pkg(8) to extract the the list of installed > packages even after listing it as a dependency & therefore installing > it, right? > > Just trying to get clear on what's going on... Yes. net-snmpd assumes you're using pkg(8). If you're going to stick with old pkg_tools, then you're also going to have to stick with old net-snmpd. Of you could just, you know, step into the modern age, become one with the zeitgeist and switch to pkgng. Don't dither too long though -- you've only got until September before the question becomes academic, as that's when pkg_tools is being EoL'd. Cheers, Matthew -- Dr Matthew J Seaman MA, D.Phil. PGP: http://www.infracaninophile.co.uk/pgpkey signature.asc Description: OpenPGP digital signature
Re: Net-SNMP conflict
Matthew Seaman wrote:
On 05/20/14 15:05, Richard Kuhns wrote:
Mark Felder wrote:
On 2014-05-20 03:18, Pete Carah wrote:
PLEASE don't automatically install pkg during the build of ANY other
package; if this happens in the middle of a portupgrade -a on a system
without pkgng, the result is not pretty; all packages built after
net-snmp have a duplicated origin, among other things. I hope I can
recover the system since it is supposed to be a production server.
Yes, I realize I'll have to convert. However, this forced install
doesn't convert the database so the pkg database and /var/db/pkg end up
inconsistent, and I can't tell what is really installed on all of the
packages that show a duplicated origin.
ports-mgmt/pkg should not be a dependency of any port. Are you saying
this happened? Can you identify which port?
Actually, pkg(8) being a dependency of something else is OK. It's
pkg(8) itself that should not have any dependencies.
___
The Makefile for net-mgmt/net-snmp contains this snippet:
# pkg-1.2 cannot handle this dependency well.
.if !defined(WITH_PKGNG)
LIB_DEPENDS=libpkg.so:${PORTSDIR}/ports-mgmt/pkg
.endif
net-snmpd uses pkg(8) to extract the list of installed packages.
To the OP: just having pkg(8) installed out of ports and sitting on your
drive will not hurt you. You have to start running it before anything
(nice or nasty) would happen.
If you don't want to switch to pkgng just yet, then don't run pkg2ng.
Similarly don't add 'WITH_PKGNG=yes' to /etc/make.conf (if you're going
to be compiling your own ports using portmaster(8) or otherwise) and
don't use pkg(8) to install any packages. Everything that is pkgng
aware should be using somewhat more sophisticated tests than just 'is
/usr/local/sbin/pkg installed' to determine if the system is pkgng-ified
or not.
Cheers,
Matthew
So doesn't that mean that the net-snmp port is doing things wrong? If
pkg *isn't* installed it's pretty safe to say that net-snmpd is not
going to be able to use pkg(8) to extract the the list of installed
packages even after listing it as a dependency & therefore installing
it, right?
Just trying to get clear on what's going on...
Thanks,
- Richard
--
Richard Kuhns Main Number: 765-742-8428
Wintek Corporation Direct: 765-269-8541
427 N 6th Street Internet Support: 765-269-8503
Lafayette, IN 47901-2211 Consulting: 765-269-8504
___
freebsd-ports@freebsd.org mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-ports
To unsubscribe, send any mail to "freebsd-ports-unsubscr...@freebsd.org"
Done with this port
I'm giving up x11-toolkits/iwidgets. Someone else can wrestle this thing into compliance with STAGE. I've beaten my head against that damn wall long enough. If no one takes it, it dies in June. Staging may kill a lot of ports. I'm not longer the maintainer for that one. -- Paul Schmehl, Senior Infosec Analyst As if it wasn't already obvious, my opinions are my own and not those of my employer. *** "It is as useless to argue with those who have renounced the use of reason as to administer medication to the dead." Thomas Jefferson "There are some ideas so wrong that only a very intelligent person could believe in them." George Orwell ___ freebsd-ports@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-ports To unsubscribe, send any mail to "freebsd-ports-unsubscr...@freebsd.org"
Re: Staging issue with staging of net-im/libpurple (libtool?)
On Tue, May 20, 2014 at 7:39 AM, Albert Shih wrote:
> Le 20/05/2014 à 14:55:59+0200, Tijl Coosemans a écrit
> > On Tue, 20 May 2014 14:14:49 +0200 Albert Shih wrote:
> > > Le 20/05/2014 à 14:09:45+0200, Tijl Coosemans a écrit
> > > with
> > >
> > > [root@io libpurple]# tail Makefile
> > > ${WRKSRC}/libpurple/purple-send-async
> > > @${REINPLACE_CMD} -e 's|/python|/env python|' \
> > > ${WRKSRC}/libpurple/purple-remote \
> > > ${WRKSRC}/libpurple/purple-url-handler
> > > .if defined(PIDGIN_SLAVE)
> > > @${FIND} ${BUILD_WRKSRC} -name Makefile.in | ${XARGS}
> ${REINPLACE_CMD} -e \
> > > 's|$$(top_builddir)/libpurple/libpurple.la
> |-lpurple|'
> > > .endif
> > >
> > > .include
> > > [root@io libpurple]#
> >
> > Silly question perhaps, but did you run "make clean" before rebuilding?
>
> Why silly ? ;-)
>
> You rightafter a make clean everything works.
>
> I was able to upgrade everything.
>
>
> Thanks.
>
> Regards.
>
> JAS
> --
> Albert SHIH
> DIO bâtiment 15
> Observatoire de Paris
> 5 Place Jules Janssen
> 92195 Meudon Cedex
> France
> Téléphone : +33 1 45 07 76 26/+33 6 86 69 95 71
> xmpp: j...@obspm.fr
> Heure local/Local time:
> mar 20 mai 2014 16:38:16 CEST
>
Removed the FIND and re-built. After the build I looked in
stage/usr/local/lib and the .so.0 files are still present! I then installed
with no errors. I'll admit that I don't understand what is happening or why
the touch of the files would break things, but it seems to be fixed, now.
Now to rebuild pidgin.
Thanks, Tijl. (Some day I'd like to know how "Tijl" is pronounced.)
--
R. Kevin Oberman, Network Engineer, Retired
E-mail: rkober...@gmail.com
___
freebsd-ports@freebsd.org mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-ports
To unsubscribe, send any mail to "freebsd-ports-unsubscr...@freebsd.org"
Re: Net-SNMP conflict
On 05/20/14 15:05, Richard Kuhns wrote:
> Mark Felder wrote:
>> On 2014-05-20 03:18, Pete Carah wrote:
>>> PLEASE don't automatically install pkg during the build of ANY other
>>> package; if this happens in the middle of a portupgrade -a on a system
>>> without pkgng, the result is not pretty; all packages built after
>>> net-snmp have a duplicated origin, among other things. I hope I can
>>> recover the system since it is supposed to be a production server.
>>>
>>> Yes, I realize I'll have to convert. However, this forced install
>>> doesn't convert the database so the pkg database and /var/db/pkg end up
>>> inconsistent, and I can't tell what is really installed on all of the
>>> packages that show a duplicated origin.
>>>
>>
>> ports-mgmt/pkg should not be a dependency of any port. Are you saying
>> this happened? Can you identify which port?
Actually, pkg(8) being a dependency of something else is OK. It's
pkg(8) itself that should not have any dependencies.
>> ___
>
>
> The Makefile for net-mgmt/net-snmp contains this snippet:
>
> # pkg-1.2 cannot handle this dependency well.
> .if !defined(WITH_PKGNG)
> LIB_DEPENDS=libpkg.so:${PORTSDIR}/ports-mgmt/pkg
> .endif
>
net-snmpd uses pkg(8) to extract the list of installed packages.
To the OP: just having pkg(8) installed out of ports and sitting on your
drive will not hurt you. You have to start running it before anything
(nice or nasty) would happen.
If you don't want to switch to pkgng just yet, then don't run pkg2ng.
Similarly don't add 'WITH_PKGNG=yes' to /etc/make.conf (if you're going
to be compiling your own ports using portmaster(8) or otherwise) and
don't use pkg(8) to install any packages. Everything that is pkgng
aware should be using somewhat more sophisticated tests than just 'is
/usr/local/sbin/pkg installed' to determine if the system is pkgng-ified
or not.
Cheers,
Matthew
signature.asc
Description: OpenPGP digital signature
Problem on 8-STABLE installing ports: pkg_add: could not find package broken_contents
(-ports@ people, please CC me.) I am having problems installing ports via "portmaster" or "make" on 8-STABLE & ports tree is at r354272 during "pkg_add" stage. Error via "portmaster x11-toolkits/gtk20" ... ===> Installing for gtk2-2.24.22_3 ===> Checking if x11-toolkits/gtk20 already installed pkg_add: could not find package broken_contents ! *** Error code 1 Stop in /misc/ports/x11-toolkits/gtk20. *** Error code 1 ... or error via "make install" ... ===> Checking if x11-toolkits/gtk20 already installed pkg_add: could not find package broken_contents ! *** Error code 1 Stop in /misc/ports/x11-toolkits/gtk20. ... done [1] install in /misc/ports/x11-toolkits/gtk20 I searched the web but could not find a solution; did find something related ... - identify the installed ports' +CONTENTS with empty "@pkgdep" http://www.freebsddiary.org/phorum/read.php?f=4&i=341&t=341 https://forums.freebsd.org/viewtopic.php?&t=13899 Above error has started happening recently. Earlier, same problem was with libgsf, which I had installed as a package instead and added "+IGNOREME" for portmaster to skip it. Is this PR ... devel/libgsf fix installation of GObject Introspection files http://www.freebsd.org/cgi/query-pr.cgi?pr=ports/188522 ... related or of any significance? What is creating broken package contents (manifest?) of newly built port to be installed? Or, how could I go finding the culprit? - parv -- ___ freebsd-ports@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-ports To unsubscribe, send any mail to "freebsd-ports-unsubscr...@freebsd.org"
Re: Net-SNMP conflict
On 2014-05-20 04:18, Pete Carah wrote: PLEASE don't automatically install pkg during the build of ANY other package; if this happens in the middle of a portupgrade -a on a system without pkgng, the result is not pretty; all packages built after net-snmp have a duplicated origin, among other things. I hope I can recover the system since it is supposed to be a production server. Yes, I realize I'll have to convert. However, this forced install doesn't convert the database so the pkg database and /var/db/pkg end up inconsistent, and I can't tell what is really installed on all of the packages that show a duplicated origin. -- Pete (portupgrade maintainer and pkg developer here) Having pkg installed should be perfectly safe. Portupgrade, nor the ports framework, consider pkg installed as "converted". All packages will continue to be registered in the old format unless you run pkg2ng or 'pkg install' or add WITH_PKGNG=yes to your make.conf. Can you please elaborate on what the "duplicated origin" issue is? net-snmp also should (if I remember the code I reviewed right) be only considering the new package database if it has packages in it, meaning not until you pkg2ng or 'pkg install'. -- Regards, Bryan Drewery ___ freebsd-ports@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-ports To unsubscribe, send any mail to "freebsd-ports-unsubscr...@freebsd.org"
Re: Staging issue with staging of net-im/libpurple (libtool?)
Le 20/05/2014 à 14:55:59+0200, Tijl Coosemans a écrit
> On Tue, 20 May 2014 14:14:49 +0200 Albert Shih wrote:
> > Le 20/05/2014 à 14:09:45+0200, Tijl Coosemans a écrit
> > with
> >
> > [root@io libpurple]# tail Makefile
> > ${WRKSRC}/libpurple/purple-send-async
> > @${REINPLACE_CMD} -e 's|/python|/env python|' \
> > ${WRKSRC}/libpurple/purple-remote \
> > ${WRKSRC}/libpurple/purple-url-handler
> > .if defined(PIDGIN_SLAVE)
> > @${FIND} ${BUILD_WRKSRC} -name Makefile.in | ${XARGS}
> > ${REINPLACE_CMD} -e \
> > 's|$$(top_builddir)/libpurple/libpurple.la|-lpurple|'
> > .endif
> >
> > .include
> > [root@io libpurple]#
>
> Silly question perhaps, but did you run "make clean" before rebuilding?
Why silly ? ;-)
You rightafter a make clean everything works.
I was able to upgrade everything.
Thanks.
Regards.
JAS
--
Albert SHIH
DIO bâtiment 15
Observatoire de Paris
5 Place Jules Janssen
92195 Meudon Cedex
France
Téléphone : +33 1 45 07 76 26/+33 6 86 69 95 71
xmpp: j...@obspm.fr
Heure local/Local time:
mar 20 mai 2014 16:38:16 CEST
___
freebsd-ports@freebsd.org mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-ports
To unsubscribe, send any mail to "freebsd-ports-unsubscr...@freebsd.org"
Re: Net-SNMP conflict
Mark Felder wrote:
On 2014-05-20 03:18, Pete Carah wrote:
PLEASE don't automatically install pkg during the build of ANY other
package; if this happens in the middle of a portupgrade -a on a system
without pkgng, the result is not pretty; all packages built after
net-snmp have a duplicated origin, among other things. I hope I can
recover the system since it is supposed to be a production server.
Yes, I realize I'll have to convert. However, this forced install
doesn't convert the database so the pkg database and /var/db/pkg end up
inconsistent, and I can't tell what is really installed on all of the
packages that show a duplicated origin.
ports-mgmt/pkg should not be a dependency of any port. Are you saying
this happened? Can you identify which port?
___
The Makefile for net-mgmt/net-snmp contains this snippet:
# pkg-1.2 cannot handle this dependency well.
.if !defined(WITH_PKGNG)
LIB_DEPENDS=libpkg.so:${PORTSDIR}/ports-mgmt/pkg
.endif
--
Richard Kuhns Main Number: 765-742-8428
Wintek Corporation Direct: 765-269-8541
427 N 6th Street Internet Support: 765-269-8503
Lafayette, IN 47901-2211 Consulting: 765-269-8504
___
freebsd-ports@freebsd.org mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-ports
To unsubscribe, send any mail to "freebsd-ports-unsubscr...@freebsd.org"
Re: Staging issue with staging of net-im/libpurple (libtool?)
On Tue, 20 May 2014 15:06:43 +0200 Dominic Fandrey wrote:
> On 20/05/2014 14:55, Tijl Coosemans wrote:
> > On Tue, 20 May 2014 14:14:49 +0200 Albert Shih wrote:
> >> Le 20/05/2014 à 14:09:45+0200, Tijl Coosemans a écrit
> >>> On Tue, 20 May 2014 10:55:44 +0200 Albert Shih wrote:
> Le 18/05/2014 à 21:11:16-0700, Kevin Oberman a écrit
> > I have a problem installing net-im/libpurple. I get the following error:
> > ===> Registering installation for libpurple-2.10.9_2
> > pkg-static:
> > lstat(/usr/ports/net-im/libpurple/work/stage/usr/local/lib/purple-2/libjabber.so.0):
> > No such file or directory
> > pkg-static:
> > lstat(/usr/ports/net-im/libpurple/work/stage/usr/local/lib/purple-2/liboscar.so.0):
> > No such file or directory
> > pkg-static:
> > lstat(/usr/ports/net-im/libpurple/work/stage/usr/local/lib/purple-2/libymsg.so.0):
> > No such file or directory
> > pkg-static:
> > lstat(/usr/ports/net-im/libpurple/work/stage/usr/local/lib/libpurple-client.so.0):
> > No such file or directory
> > pkg-static:
> > lstat(/usr/ports/net-im/libpurple/work/stage/usr/local/lib/libpurple.so.0):
> > No such file or directory
> > *** Error code 74
> >
> > Stop.
> >
> > Wherethis gets really weird is that on another system it installed
> > correctly. I wanted to look at the stage directory content, so
> > deinstalled
> > and reinstalled. Now it won't install there, either. Same error. Why
> > did it
> > only install once?
>
> Exact same problem for me. I got two PC, one laptop, another desktop,
> both
> with FreeBSD 10-stable, both using portupgrade.
>
> On one everything work (the desktop), on the laptop I have exact same
> message.
> >>>
> >>> The last command in the port Makefile is this:
> >>> @${FIND} ${WRKSRC} -type f | ${XARGS} ${TOUCH}
> >>>
> >>> Try removing that line.
> >>
> >> Change nothing.
> >>
> >> Still get the same error
> >>
> >> ===> Checking if net-im/libpurple already installed
> >> ===> Registering installation for libpurple-2.10.9_2
> >> pkg-static:
> >> lstat(/usr/ports/net-im/libpurple/work/stage/usr/local/lib/purple-2/libjabber.so.0):
> >> No such file or directory
> >> pkg-static:
> >> lstat(/usr/ports/net-im/libpurple/work/stage/usr/local/lib/purple-2/liboscar.so.0):
> >> No such file or directory
> >> pkg-static:
> >> lstat(/usr/ports/net-im/libpurple/work/stage/usr/local/lib/purple-2/libymsg.so.0):
> >> No such file or directory
> >> pkg-static:
> >> lstat(/usr/ports/net-im/libpurple/work/stage/usr/local/lib/libpurple-client.so.0):
> >> No such file or directory
> >> pkg-static:
> >> lstat(/usr/ports/net-im/libpurple/work/stage/usr/local/lib/libpurple.so.0):
> >> No such file or directory
> >> *** Error code 74
> >>
> >> with
> >>
> >> [root@io libpurple]# tail Makefile
> >> ${WRKSRC}/libpurple/purple-send-async
> >> @${REINPLACE_CMD} -e 's|/python|/env python|' \
> >> ${WRKSRC}/libpurple/purple-remote \
> >> ${WRKSRC}/libpurple/purple-url-handler
> >> .if defined(PIDGIN_SLAVE)
> >> @${FIND} ${BUILD_WRKSRC} -name Makefile.in | ${XARGS}
> >> ${REINPLACE_CMD} -e \
> >> 's|$$(top_builddir)/libpurple/libpurple.la|-lpurple|'
> >> .endif
> >>
> >> .include
> >> [root@io libpurple]#
> >
> > Silly question perhaps, but did you run "make clean" before rebuilding?
>
> I turned MYSPACE support of and reproduced the problem. Then I tried
> with MYSPACE and it works. Afterwards I tried again without MYSPACE
> and it still works.
>
> Then I turned MYSPACE back on and got the error again.
>
> Looks like a timing issue to me. I'd say turn MAKE_JOBS off.
>
Is this with or without that ${FIND} command?
___
freebsd-ports@freebsd.org mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-ports
To unsubscribe, send any mail to "freebsd-ports-unsubscr...@freebsd.org"
Re: Staging issue with staging of net-im/libpurple (libtool?)
On 20/05/2014 14:55, Tijl Coosemans wrote:
> On Tue, 20 May 2014 14:14:49 +0200 Albert Shih wrote:
>> Le 20/05/2014 à 14:09:45+0200, Tijl Coosemans a écrit
>>> On Tue, 20 May 2014 10:55:44 +0200 Albert Shih wrote:
Le 18/05/2014 à 21:11:16-0700, Kevin Oberman a écrit
> I have a problem installing net-im/libpurple. I get the following error:
> ===> Registering installation for libpurple-2.10.9_2
> pkg-static:
> lstat(/usr/ports/net-im/libpurple/work/stage/usr/local/lib/purple-2/libjabber.so.0):
> No such file or directory
> pkg-static:
> lstat(/usr/ports/net-im/libpurple/work/stage/usr/local/lib/purple-2/liboscar.so.0):
> No such file or directory
> pkg-static:
> lstat(/usr/ports/net-im/libpurple/work/stage/usr/local/lib/purple-2/libymsg.so.0):
> No such file or directory
> pkg-static:
> lstat(/usr/ports/net-im/libpurple/work/stage/usr/local/lib/libpurple-client.so.0):
> No such file or directory
> pkg-static:
> lstat(/usr/ports/net-im/libpurple/work/stage/usr/local/lib/libpurple.so.0):
> No such file or directory
> *** Error code 74
>
> Stop.
>
> Wherethis gets really weird is that on another system it installed
> correctly. I wanted to look at the stage directory content, so deinstalled
> and reinstalled. Now it won't install there, either. Same error. Why did
> it
> only install once?
Exact same problem for me. I got two PC, one laptop, another desktop, both
with FreeBSD 10-stable, both using portupgrade.
On one everything work (the desktop), on the laptop I have exact same
message.
>>>
>>> The last command in the port Makefile is this:
>>> @${FIND} ${WRKSRC} -type f | ${XARGS} ${TOUCH}
>>>
>>> Try removing that line.
>>
>> Change nothing.
>>
>> Still get the same error
>>
>> ===> Checking if net-im/libpurple already installed
>> ===> Registering installation for libpurple-2.10.9_2
>> pkg-static:
>> lstat(/usr/ports/net-im/libpurple/work/stage/usr/local/lib/purple-2/libjabber.so.0):
>> No such file or directory
>> pkg-static:
>> lstat(/usr/ports/net-im/libpurple/work/stage/usr/local/lib/purple-2/liboscar.so.0):
>> No such file or directory
>> pkg-static:
>> lstat(/usr/ports/net-im/libpurple/work/stage/usr/local/lib/purple-2/libymsg.so.0):
>> No such file or directory
>> pkg-static:
>> lstat(/usr/ports/net-im/libpurple/work/stage/usr/local/lib/libpurple-client.so.0):
>> No such file or directory
>> pkg-static:
>> lstat(/usr/ports/net-im/libpurple/work/stage/usr/local/lib/libpurple.so.0):
>> No such file or directory
>> *** Error code 74
>>
>> with
>>
>> [root@io libpurple]# tail Makefile
>> ${WRKSRC}/libpurple/purple-send-async
>> @${REINPLACE_CMD} -e 's|/python|/env python|' \
>> ${WRKSRC}/libpurple/purple-remote \
>> ${WRKSRC}/libpurple/purple-url-handler
>> .if defined(PIDGIN_SLAVE)
>> @${FIND} ${BUILD_WRKSRC} -name Makefile.in | ${XARGS}
>> ${REINPLACE_CMD} -e \
>> 's|$$(top_builddir)/libpurple/libpurple.la|-lpurple|'
>> .endif
>>
>> .include
>> [root@io libpurple]#
>
> Silly question perhaps, but did you run "make clean" before rebuilding?
I turned MYSPACE support of and reproduced the problem. Then I tried
with MYSPACE and it works. Afterwards I tried again without MYSPACE
and it still works.
Then I turned MYSPACE back on and got the error again.
Looks like a timing issue to me. I'd say turn MAKE_JOBS off.
--
A: Because it fouls the order in which people normally read text.
Q: Why is top-posting such a bad thing?
A: Top-posting.
Q: What is the most annoying thing on usenet and in e-mail?
___
freebsd-ports@freebsd.org mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-ports
To unsubscribe, send any mail to "freebsd-ports-unsubscr...@freebsd.org"
Re: Staging issue with staging of net-im/libpurple (libtool?)
On Tue, 20 May 2014 14:14:49 +0200 Albert Shih wrote:
> Le 20/05/2014 à 14:09:45+0200, Tijl Coosemans a écrit
> > On Tue, 20 May 2014 10:55:44 +0200 Albert Shih wrote:
> > > Le 18/05/2014 à 21:11:16-0700, Kevin Oberman a écrit
> > >> I have a problem installing net-im/libpurple. I get the following error:
> > >> ===> Registering installation for libpurple-2.10.9_2
> > >> pkg-static:
> > >> lstat(/usr/ports/net-im/libpurple/work/stage/usr/local/lib/purple-2/libjabber.so.0):
> > >> No such file or directory
> > >> pkg-static:
> > >> lstat(/usr/ports/net-im/libpurple/work/stage/usr/local/lib/purple-2/liboscar.so.0):
> > >> No such file or directory
> > >> pkg-static:
> > >> lstat(/usr/ports/net-im/libpurple/work/stage/usr/local/lib/purple-2/libymsg.so.0):
> > >> No such file or directory
> > >> pkg-static:
> > >> lstat(/usr/ports/net-im/libpurple/work/stage/usr/local/lib/libpurple-client.so.0):
> > >> No such file or directory
> > >> pkg-static:
> > >> lstat(/usr/ports/net-im/libpurple/work/stage/usr/local/lib/libpurple.so.0):
> > >> No such file or directory
> > >> *** Error code 74
> > >>
> > >> Stop.
> > >>
> > >> Wherethis gets really weird is that on another system it installed
> > >> correctly. I wanted to look at the stage directory content, so
> > >> deinstalled
> > >> and reinstalled. Now it won't install there, either. Same error. Why did
> > >> it
> > >> only install once?
> > >
> > > Exact same problem for me. I got two PC, one laptop, another desktop, both
> > > with FreeBSD 10-stable, both using portupgrade.
> > >
> > > On one everything work (the desktop), on the laptop I have exact same
> > > message.
> >
> > The last command in the port Makefile is this:
> > @${FIND} ${WRKSRC} -type f | ${XARGS} ${TOUCH}
> >
> > Try removing that line.
>
> Change nothing.
>
> Still get the same error
>
> ===> Checking if net-im/libpurple already installed
> ===> Registering installation for libpurple-2.10.9_2
> pkg-static:
> lstat(/usr/ports/net-im/libpurple/work/stage/usr/local/lib/purple-2/libjabber.so.0):
> No such file or directory
> pkg-static:
> lstat(/usr/ports/net-im/libpurple/work/stage/usr/local/lib/purple-2/liboscar.so.0):
> No such file or directory
> pkg-static:
> lstat(/usr/ports/net-im/libpurple/work/stage/usr/local/lib/purple-2/libymsg.so.0):
> No such file or directory
> pkg-static:
> lstat(/usr/ports/net-im/libpurple/work/stage/usr/local/lib/libpurple-client.so.0):
> No such file or directory
> pkg-static:
> lstat(/usr/ports/net-im/libpurple/work/stage/usr/local/lib/libpurple.so.0):
> No such file or directory
> *** Error code 74
>
> with
>
> [root@io libpurple]# tail Makefile
> ${WRKSRC}/libpurple/purple-send-async
> @${REINPLACE_CMD} -e 's|/python|/env python|' \
> ${WRKSRC}/libpurple/purple-remote \
> ${WRKSRC}/libpurple/purple-url-handler
> .if defined(PIDGIN_SLAVE)
> @${FIND} ${BUILD_WRKSRC} -name Makefile.in | ${XARGS}
> ${REINPLACE_CMD} -e \
> 's|$$(top_builddir)/libpurple/libpurple.la|-lpurple|'
> .endif
>
> .include
> [root@io libpurple]#
Silly question perhaps, but did you run "make clean" before rebuilding?
___
freebsd-ports@freebsd.org mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-ports
To unsubscribe, send any mail to "freebsd-ports-unsubscr...@freebsd.org"
Re: Net-SNMP conflict
On 2014-05-20 03:18, Pete Carah wrote: PLEASE don't automatically install pkg during the build of ANY other package; if this happens in the middle of a portupgrade -a on a system without pkgng, the result is not pretty; all packages built after net-snmp have a duplicated origin, among other things. I hope I can recover the system since it is supposed to be a production server. Yes, I realize I'll have to convert. However, this forced install doesn't convert the database so the pkg database and /var/db/pkg end up inconsistent, and I can't tell what is really installed on all of the packages that show a duplicated origin. ports-mgmt/pkg should not be a dependency of any port. Are you saying this happened? Can you identify which port? ___ freebsd-ports@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-ports To unsubscribe, send any mail to "freebsd-ports-unsubscr...@freebsd.org"
Re: Staging issue with staging of net-im/libpurple (libtool?)
Le 20/05/2014 à 14:09:45+0200, Tijl Coosemans a écrit
> On Tue, 20 May 2014 10:55:44 +0200 Albert Shih wrote:
> > Le 18/05/2014 à 21:11:16-0700, Kevin Oberman a écrit
> >> I have a problem installing net-im/libpurple. I get the following error:
> >> ===> Registering installation for libpurple-2.10.9_2
> >> pkg-static:
> >> lstat(/usr/ports/net-im/libpurple/work/stage/usr/local/lib/purple-2/libjabber.so.0):
> >> No such file or directory
> >> pkg-static:
> >> lstat(/usr/ports/net-im/libpurple/work/stage/usr/local/lib/purple-2/liboscar.so.0):
> >> No such file or directory
> >> pkg-static:
> >> lstat(/usr/ports/net-im/libpurple/work/stage/usr/local/lib/purple-2/libymsg.so.0):
> >> No such file or directory
> >> pkg-static:
> >> lstat(/usr/ports/net-im/libpurple/work/stage/usr/local/lib/libpurple-client.so.0):
> >> No such file or directory
> >> pkg-static:
> >> lstat(/usr/ports/net-im/libpurple/work/stage/usr/local/lib/libpurple.so.0):
> >> No such file or directory
> >> *** Error code 74
> >>
> >> Stop.
> >>
> >> Wherethis gets really weird is that on another system it installed
> >> correctly. I wanted to look at the stage directory content, so deinstalled
> >> and reinstalled. Now it won't install there, either. Same error. Why did it
> >> only install once?
> >
> > Exact same problem for me. I got two PC, one laptop, another desktop, both
> > with FreeBSD 10-stable, both using portupgrade.
> >
> > On one everything work (the desktop), on the laptop I have exact same
> > message.
>
> The last command in the port Makefile is this:
> @${FIND} ${WRKSRC} -type f | ${XARGS} ${TOUCH}
>
> Try removing that line.
Change nothing.
Still get the same error
===> Checking if net-im/libpurple already installed
===> Registering installation for libpurple-2.10.9_2
pkg-static:
lstat(/usr/ports/net-im/libpurple/work/stage/usr/local/lib/purple-2/libjabber.so.0):
No such file or directory
pkg-static:
lstat(/usr/ports/net-im/libpurple/work/stage/usr/local/lib/purple-2/liboscar.so.0):
No such file or directory
pkg-static:
lstat(/usr/ports/net-im/libpurple/work/stage/usr/local/lib/purple-2/libymsg.so.0):
No such file or directory
pkg-static:
lstat(/usr/ports/net-im/libpurple/work/stage/usr/local/lib/libpurple-client.so.0):
No such file or directory
pkg-static:
lstat(/usr/ports/net-im/libpurple/work/stage/usr/local/lib/libpurple.so.0): No
such file or directory
*** Error code 74
with
[root@io libpurple]# tail Makefile
${WRKSRC}/libpurple/purple-send-async
@${REINPLACE_CMD} -e 's|/python|/env python|' \
${WRKSRC}/libpurple/purple-remote \
${WRKSRC}/libpurple/purple-url-handler
.if defined(PIDGIN_SLAVE)
@${FIND} ${BUILD_WRKSRC} -name Makefile.in | ${XARGS}
${REINPLACE_CMD} -e \
's|$$(top_builddir)/libpurple/libpurple.la|-lpurple|'
.endif
.include
[root@io libpurple]#
Regards.
JAS
--
Albert SHIH
DIO bâtiment 15
Observatoire de Paris
5 Place Jules Janssen
92195 Meudon Cedex
France
Téléphone : +33 1 45 07 76 26/+33 6 86 69 95 71
xmpp: j...@obspm.fr
Heure local/Local time:
mar 20 mai 2014 14:13:12 CEST
___
freebsd-ports@freebsd.org mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-ports
To unsubscribe, send any mail to "freebsd-ports-unsubscr...@freebsd.org"
Re: Staging issue with staging of net-im/libpurple (libtool?)
On Tue, 20 May 2014 10:55:44 +0200 Albert Shih wrote:
> Le 18/05/2014 à 21:11:16-0700, Kevin Oberman a écrit
>> I have a problem installing net-im/libpurple. I get the following error:
>> ===> Registering installation for libpurple-2.10.9_2
>> pkg-static:
>> lstat(/usr/ports/net-im/libpurple/work/stage/usr/local/lib/purple-2/libjabber.so.0):
>> No such file or directory
>> pkg-static:
>> lstat(/usr/ports/net-im/libpurple/work/stage/usr/local/lib/purple-2/liboscar.so.0):
>> No such file or directory
>> pkg-static:
>> lstat(/usr/ports/net-im/libpurple/work/stage/usr/local/lib/purple-2/libymsg.so.0):
>> No such file or directory
>> pkg-static:
>> lstat(/usr/ports/net-im/libpurple/work/stage/usr/local/lib/libpurple-client.so.0):
>> No such file or directory
>> pkg-static:
>> lstat(/usr/ports/net-im/libpurple/work/stage/usr/local/lib/libpurple.so.0):
>> No such file or directory
>> *** Error code 74
>>
>> Stop.
>>
>> Wherethis gets really weird is that on another system it installed
>> correctly. I wanted to look at the stage directory content, so deinstalled
>> and reinstalled. Now it won't install there, either. Same error. Why did it
>> only install once?
>
> Exact same problem for me. I got two PC, one laptop, another desktop, both
> with FreeBSD 10-stable, both using portupgrade.
>
> On one everything work (the desktop), on the laptop I have exact same
> message.
The last command in the port Makefile is this:
@${FIND} ${WRKSRC} -type f | ${XARGS} ${TOUCH}
Try removing that line.
___
freebsd-ports@freebsd.org mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-ports
To unsubscribe, send any mail to "freebsd-ports-unsubscr...@freebsd.org"
Re: how to install ruby18
Gryd T L wrote (from
https://www.mail-archive.com/freebsd-ports@freebsd.org/msg54593.html)
...
> The following helped me identity the ports with bad files:
>
> find /var/db/pkg -type f -exec iconv -t US-ASCII {} > /dev/null \;
>
> Reinstalling the indicated ports solved it for me. I'm currently
> using pkg-tools, ruby19 and portupgrade with no problems on
> FreeBSD 8.3.
...
Thanks much, Gryd, for your find-iconv command.
- parv
--
___
freebsd-ports@freebsd.org mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-ports
To unsubscribe, send any mail to "freebsd-ports-unsubscr...@freebsd.org"
Re: smplayer dependency on mplayer1
On Mon, 19 May 2014 17:54:26 -0700 Ronald F. Guilmette wrote: > > Looking at the Makefile for multimedia/smplayer it appears to me > that smplayer is dependent upon the 1.x version of mplayer being > installed, however there exists what I would guess is a later > and better version of mplayer called multimedia/mplayer2 in the > ports tree. > > So why is smplayer dependent upon an oldre (and now obsolete?) > version of mplayer? mplayer2 is a fork of mplayer, not a later version. ___ freebsd-ports@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-ports To unsubscribe, send any mail to "freebsd-ports-unsubscr...@freebsd.org"
FreeBSD ports you maintain which are out of date
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 +-+ biology/iolib | 1.13.5 | 1.13.6 +-+ 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 http://lists.freebsd.org/mailman/listinfo/freebsd-ports To unsubscribe, send any mail to "freebsd-ports-unsubscr...@freebsd.org"
Re: firefox-29.0,1 -- dumps core
Please allow me to clarify two things: 1) The exact set of build options that are needed in order to reproduce the crash I have reported are as follows: DBUS (enabled by default) GIO (enabled by default) GSTREAMER (enabled by default) ALSA (enabled by default) DEBUG Apparently enabling or disabling the LOGGING option makes no difference at all. The crash will arise (when broswing around on, e.g. www.newegg.com) as long as the DEBUG build-time option is enabled. 2) When built with DEBUG, Firefox is quite a bit more verbose than when it is built without that option. In particular, some text messages that Firefox writes to its stderr channel just before it segfaults appear to provide some indication of the reason why it elects to do so: ... XRE_main+0x0058 [/usr/local/lib/firefox/libxul.so +0x03348aa7] _start+0x0825 [/usr/local/bin/firefox +0x4935] _start+0x0c20 [/usr/local/bin/firefox +0x4d30] _start+0x008e [/usr/local/bin/firefox +0x419e] UNKNOWN 0x800696000 [79233] ###!!! ABORT: Should be tracking any image we're going to use!: 'mImageTracked', file /usr/ports/www/firefox/work/mozilla-release/layout/style/nsStyleStruct.h, line 208 Hit MOZ_CRASH() at /usr/ports/www/firefox/work/mozilla-release/memory/mozalloc/mozalloc_abort.cpp:30 Can anybody who knows their way around the Firefox code look into this further? I myself am not at all familiar with the code base of Firefox. ___ freebsd-ports@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-ports To unsubscribe, send any mail to "freebsd-ports-unsubscr...@freebsd.org"
Re: Staging issue with staging of net-im/libpurple (libtool?)
Le 18/05/2014 à 21:11:16-0700, Kevin Oberman a écrit > I have a problem installing net-im/libpurple. I get the following error: > ===> Registering installation for libpurple-2.10.9_2 > pkg-static: > lstat(/usr/ports/net-im/libpurple/work/stage/usr/local/lib/purple-2/libjabber.so.0): > No such file or directory > pkg-static: > lstat(/usr/ports/net-im/libpurple/work/stage/usr/local/lib/purple-2/liboscar.so.0): > No such file or directory > pkg-static: > lstat(/usr/ports/net-im/libpurple/work/stage/usr/local/lib/purple-2/libymsg.so.0): > No such file or directory > pkg-static: > lstat(/usr/ports/net-im/libpurple/work/stage/usr/local/lib/libpurple-client.so.0): > No such file or directory > pkg-static: > lstat(/usr/ports/net-im/libpurple/work/stage/usr/local/lib/libpurple.so.0): > No such file or directory > *** Error code 74 > > Stop. > > Wherethis gets really weird is that on another system it installed > correctly. I wanted to look at the stage directory content, so deinstalled > and reinstalled. Now it won't install there, either. Same error. Why did it > only install once? Exact same problem for me. I got two PC, one laptop, another desktop, both with FreeBSD 10-stable, both using portupgrade. On one everything work (the desktop), on the laptop I have exact same message. Regards. -- Albert SHIH DIO bâtiment 15 Observatoire de Paris 5 Place Jules Janssen 92195 Meudon Cedex France Téléphone : +33 1 45 07 76 26/+33 6 86 69 95 71 xmpp: j...@obspm.fr Heure local/Local time: mar 20 mai 2014 10:54:30 CEST ___ freebsd-ports@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-ports To unsubscribe, send any mail to "freebsd-ports-unsubscr...@freebsd.org"
Net-SNMP conflict
PLEASE don't automatically install pkg during the build of ANY other package; if this happens in the middle of a portupgrade -a on a system without pkgng, the result is not pretty; all packages built after net-snmp have a duplicated origin, among other things. I hope I can recover the system since it is supposed to be a production server. Yes, I realize I'll have to convert. However, this forced install doesn't convert the database so the pkg database and /var/db/pkg end up inconsistent, and I can't tell what is really installed on all of the packages that show a duplicated origin. -- Pete ___ freebsd-ports@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-ports To unsubscribe, send any mail to "freebsd-ports-unsubscr...@freebsd.org"
