upgrade of guppi fails
Dear sir/madam, the upgrade of guppi to the new version fails on my system. I get the following error and I have already tried the loganalyzer.sh script but that didn't give any results. Look at my error message and can you discover what is happening from that? I hope so, so I can go on and upgrade gnucash as wel. C -o guppi-config-model.o In file included from guppi-config-model.c:32: guppi-config-model.h:32:25: glade/glade.h: No such file or directory In file included from guppi-config-model.c:32: guppi-config-model.h:89: error: syntax error before '*' token guppi-config-model.c:40: warning: excess elements in array initializer guppi-config-model.c:40: warning: (near initialization for `guppi_config_model_signals') guppi-config-model.c:188: error: syntax error before '*' token guppi-config-model.c: In function `glade_info_cb': guppi-config-model.c:207: error: `GladeXML' undeclared (first use in this function) guppi-config-model.c:207: error: (Each undeclared identifier is reported only once guppi-config-model.c:207: error: for each function it appears in.) guppi-config-model.c:207: error: `glade' undeclared (first use in this function) guppi-config-model.c:210: warning: implicit declaration of function `glade_xml_new' guppi-config-model.c:217: warning: implicit declaration of function `glade_xml_get_widget' guppi-config-model.c:217: warning: assignment makes pointer from integer without a cast guppi-config-model.c: At top level: guppi-config-model.c:229: error: syntax error before '*' token gmake[3]: *** [guppi-config-model.lo] Error 1 gmake[3]: Leaving directory `/usr/ports/math/guppi/work/Guppi-0.40.3/src/libguppiuseful' gmake[2]: *** [all-recursive] Error 1 gmake[2]: Leaving directory `/usr/ports/math/guppi/work/Guppi-0.40.3/src' gmake[1]: *** [all-recursive] Error 1 gmake[1]: Leaving directory `/usr/ports/math/guppi/work/Guppi-0.40.3' gmake: *** [all-recursive-am] Error 2 *** Error code 2 Stop in /usr/ports/math/guppi. ** Command failed [exit code 1]: /usr/bin/script -qa /tmp/portupgrade.5858.0 env PORT_UPGRADE=yes make WITH_FAM_SYSTEM=fam ** Fix the problem and try again. ** Listing the failed packages (*:skipped / !:failed) ! math/guppi (guppi-0.40.3_5) (missing header) --- Packages processed: 0 done, 0 ignored, 0 skipped and 1 failed Thanks in advanced, Robert Gilaard signature.asc Description: This is a digitally signed message part
Port Bloat
A couple months ago somebody posted a heads up on this list from the FreeBSD Ports Team about ports bloat and the massive influx of new software along with all the unmaintained ports. Has the port team ever thought about: A) Making a delete port pr request. This way port maintainers INSTEAD of marking 'transfer ownership to [EMAIL PROTECTED]' and hoping somebody takes it over one day could actually just delete ports they no longer wish to maintain. There should be some sort of WARN marking mechanism though (valid for X months (maybe 6)) that notifies any new user (or current via a portupgrade and EPOCH bumb) that this port is no longer maintained and scheduled for deletion unless one of them takes over maitainership by DATE. B) In line with A, has anybody thought about just marking ALL [EMAIL PROTECTED] as scheduled for deletion on X date. Thousands of people are using these ports, you can't tell me if they were actually scheduled to be deleted from the tree at least one of the users wouldn't take over maintainership. -Peter Just some ideas (as I have ports I own that I no longer care about and would like to delete), -Peter ___ freebsd-ports@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-ports To unsubscribe, send any mail to [EMAIL PROTECTED]
Re: Is portsmon.freebsd.org down?
On Sat, 14 Oct 2006 22:39:22 -0700 (PDT) Peter Thoenen [EMAIL PROTECTED] wrote: Is portsmon down? Been trying to hit if for the last couple days. http://portsmon.freebsd.org/[EMAIL PROTECTED] Yes, hardware problems AFAIR. -- IOnut - Un^d^dregistered ;) FreeBSD user Intellectual Property is nowhere near as valuable as Intellect signature.asc Description: PGP signature
Re: Port Bloat
Peter Thoenen wrote: A couple months ago somebody posted a heads up on this list from the FreeBSD Ports Team about ports bloat and the massive influx of new software along with all the unmaintained ports. Has the port team ever thought about: A) Making a delete port pr request. This way port maintainers INSTEAD of marking 'transfer ownership to [EMAIL PROTECTED]' and hoping somebody takes it over one day could actually just delete ports they no longer wish to maintain. There should be some sort of WARN marking mechanism though (valid for X months (maybe 6)) that notifies any new user (or current via a portupgrade and EPOCH bumb) that this port is no longer maintained and scheduled for deletion unless one of them takes over maitainership by DATE. You can do this right now: http://www.freebsd.org/doc/en_US.ISO8859-1/books/porters-handbook/dads-deprecated.html Committers will regularly sweep through expired ports and remove them. B) In line with A, has anybody thought about just marking ALL [EMAIL PROTECTED] as scheduled for deletion on X date. Thousands of people are using these ports, you can't tell me if they were actually scheduled to be deleted from the tree at least one of the users wouldn't take over maintainership. That's a fairly drastic action, and it would cause a massive amount of work. People know we have unmaintained ports - they can submit updates if they wish. Pruning out obsolete ports is useful too, but it requires motivation apart from an interest in just a single port. ___ freebsd-ports@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-ports To unsubscribe, send any mail to [EMAIL PROTECTED]
Ports with version numbers going backwards: print/pdflib, print/pdflib-perl
** The following ports have a version number that sorts before a previous one ** For many package tools to work correctly, it is of utmost importance that version numbers of a port form a monotonic increasing sequence over time. Refer to the FreeBSD Porter's Handbook, 'Package Naming Conventions' for more information. Tools that won't work include pkg_version, portupgrade and portaudit. A common error is an accidental deletion of PORTEPOCH. Please fix any errors as soon as possible. - *print/pdflib* [EMAIL PROTECTED]: pdflib-7.0.0_1 pdflib-7.0.0p1 | revision 1.50 | date: 2006/10/15 08:30:11; author: ale; state: Exp; lines: +3 -2 | Fix fetching. | | Approved by: portmgr (implicitly) - *print/pdflib-perl* [EMAIL PROTECTED]: pdflib-perl-7.0.0_1 pdflib-perl-7.0.0p1 | revision 1.3 | date: 2004/06/25 11:23:01; author: ale; state: Exp; lines: +3 -5 | - Update to 6.0.0 release | - Re-enable cxx support (master: print/pdflib) | revision 1.50 | date: 2006/10/15 08:30:11; author: ale; state: Exp; lines: +3 -2 | Fix fetching. | | Approved by: portmgr (implicitly) ___ freebsd-ports@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-ports To unsubscribe, send any mail to [EMAIL PROTECTED]
Re: Ports with version numbers going backwards: print/pdflib, print/pdflib-perl
[EMAIL PROTECTED] ha scritto: Please fix any errors as soon as possible. - *print/pdflib* [EMAIL PROTECTED]: pdflib-7.0.0_1 pdflib-7.0.0p1 7.0.0p1 wasn't fetchable, so it should be ok 7.0.0_1. -- Alex Dupre ___ freebsd-ports@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-ports To unsubscribe, send any mail to [EMAIL PROTECTED]
graphics/cairo broken on 4.11-RELEASE-p25?
I can't get this to upgrade from cairo-1.0.4_1 to cairo-1.2.4. Far into the build: ... cc -DHAVE_CONFIG_H -I. -I. -I.. -I. -I../pixman/src -I/usr/local/include/freetype2 -I/usr/local/include -I/usr/X11R6/include -I/usr/local/include -I/usr/X11R6/include -Wall -Wsign-compare -Werror-implicit-function-declaration -Wpointer-arith -Wwrite-strings -Wstrict-prototypes -Wmissing-prototypes -Wmissing-declarations -Wnested-externs -fno-strict-aliasing -D_THREAD_SAFE -I/usr/X11R6/include -O -pipe -march=pentiumpro -c cairo-scaled-font.c -Wp,-MD,.deps/cairo-scaled-font.TPlo -fPIC -DPIC -o .libs/cairo-scaled-font.o cairo-scaled-font.c: In function `_cairo_scaled_font_glyph_device_extents': cairo-scaled-font.c:826: `INT16_MAX' undeclared (first use in this function) cairo-scaled-font.c:826: (Each undeclared identifier is reported only once cairo-scaled-font.c:826: for each function it appears in.) cairo-scaled-font.c:826: `INT16_MIN' undeclared (first use in this function) *** Error code 1 Stop in /usr/ports/graphics/cairo/work/cairo-1.2.4/src. *** Error code 1 Stop in /usr/ports/graphics/cairo/work/cairo-1.2.4/src. *** Error code 1 Stop in /usr/ports/graphics/cairo/work/cairo-1.2.4. *** Error code 1 Stop in /usr/ports/graphics/cairo/work/cairo-1.2.4. *** Error code 1 Stop in /usr/ports/graphics/cairo. ** Command failed [exit code 1]: /usr/bin/script -qa /tmp/portupgrade.64751.0 env PORT_UPGRADE=yes make ** Fix the problem and try again. ** Listing the failed packages (*:skipped / !:failed) ! graphics/cairo (cairo-1.0.4_1)(compiler error) --- Packages processed: 0 done, 0 ignored, 0 skipped and 1 failed Any ideas? -- Kjell ___ freebsd-ports@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-ports To unsubscribe, send any mail to [EMAIL PROTECTED]
Re: Port Bloat
On Sat, Oct 14, 2006 at 10:53:32PM -0700, Peter Thoenen wrote: B) In line with A, has anybody thought about just marking ALL [EMAIL PROTECTED] as scheduled for deletion on X date. It turns out that a few of them are key pieces of infrastructure. Perhaps we can generate a list of ports that we would really like to see adopted. It has also turned out, in the past, that one man's trash is another man's treasure as the old saying goes. When we first instituted the DEPRECATED/ EXPIRATION_DATE process, a lot of people did indeed adopt some ports in a flurry of activity, but there was a fair amount of fuss generated, too. Since then, several hundred stale/dead ports have indeed been pruned. Unfortunately we don't really have any good proxy for what ports are in use. The closest we have is FreshPorts subscriptions, which, the last we checked, showed that several thousand ports were not being tracked by anyone who subscribed. Unfortunately the sample space for FreshPorts is self-selecting so it can't be taken as authoritative. I advocate that people subscribe to FreshPorts and list the ports they use so that we can better judge this. One of my eventual goals for portsmon is to include date of last commit (as well as the fetch survey results) to try to generate another proxy for this. I don't have any other ideas that wouldn't just create a bunch of controversy, however. mcl ___ freebsd-ports@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-ports To unsubscribe, send any mail to [EMAIL PROTECTED]
Re: Port Bloat
On Sun, 15 Oct 2006 00:53:32 -0500, Peter Thoenen [EMAIL PROTECTED] wrote: A couple months ago somebody posted a heads up on this list from the FreeBSD Ports Team about ports bloat and the massive influx of new software along with all the unmaintained ports. Has the port team ever thought about: A) Making a delete port pr request. This way port maintainers INSTEAD of marking 'transfer ownership to [EMAIL PROTECTED]' and hoping somebody takes it over one day could actually just delete ports they no longer wish to maintain. There should be some sort of WARN marking mechanism though (valid for X months (maybe 6)) that notifies any new user (or current via a portupgrade and EPOCH bumb) that this port is no longer maintained and scheduled for deletion unless one of them takes over maitainership by DATE. B) In line with A, has anybody thought about just marking ALL [EMAIL PROTECTED] as scheduled for deletion on X date. Thousands of people are using these ports, you can't tell me if they were actually scheduled to be deleted from the tree at least one of the users wouldn't take over maintainership. I disagree with all of this, because ports@ or unmaintain don't mean they are broke. They work fine, so no reason to delete them. When it is broke then can add scheduled for deletion on X date until someone steps in and fix it without take the maintain. Cheers, Mezz -Peter Just some ideas (as I have ports I own that I no longer care about and would like to delete), -Peter -- [EMAIL PROTECTED] - [EMAIL PROTECTED] FreeBSD GNOME Team - FreeBSD Multimedia Hat (ports, not src) http://www.FreeBSD.org/gnome/ - [EMAIL PROTECTED] http://wiki.freebsd.org/multimedia - [EMAIL PROTECTED] ___ freebsd-ports@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-ports To unsubscribe, send any mail to [EMAIL PROTECTED]
Re: Port Bloat
On Sat, Oct 14, 2006 at 10:53:32PM -0700, Peter Thoenen wrote: A) Making a delete port pr request. This way port maintainers INSTEAD of marking 'transfer ownership to [EMAIL PROTECTED]' and hoping somebody takes it over one day could actually just delete ports they no longer wish to maintain. There should be some sort of WARN marking mechanism though (valid for X months (maybe 6)) that notifies any new user (or current via a portupgrade and EPOCH bumb) that this port is no longer maintained and scheduled for deletion unless one of them takes over maitainership by DATE. B) In line with A, has anybody thought about just marking ALL [EMAIL PROTECTED] as scheduled for deletion on X date. Thousands of people are using these ports, you can't tell me if they were actually scheduled to be deleted from the tree at least one of the users wouldn't take over maintainership. A port with no official maintainer is not necessarily unmaintained or uncared for. On the contrary, many ports assigned to [EMAIL PROTECTED] either require no work, or are taken care of collectively by everyone else. Ports that genuinely are not looked after are scheduled for deletion. -- Shaun Amott // PGP: 0x6B387A9A A foolish consistency is the hobgoblin of little minds. - Ralph Waldo Emerson pgph8T38N28k8.pgp Description: PGP signature
Re: graphics/cairo broken on 4.11-RELEASE-p25?
On Sun, Oct 15, 2006 at 04:56:07PM +0200, Kjell B. wrote: I can't get this to upgrade from cairo-1.0.4_1 to cairo-1.2.4. Far into the build: ... cc -DHAVE_CONFIG_H -I. -I. -I.. -I. -I../pixman/src -I/usr/local/include/freetype2 -I/usr/local/include -I/usr/X11R6/include -I/usr/local/include -I/usr/X11R6/include -Wall -Wsign-compare -Werror-implicit-function-declaration -Wpointer-arith -Wwrite-strings -Wstrict-prototypes -Wmissing-prototypes -Wmissing-declarations -Wnested-externs -fno-strict-aliasing -D_THREAD_SAFE -I/usr/X11R6/include -O -pipe -march=pentiumpro -c cairo-scaled-font.c -Wp,-MD,.deps/cairo-scaled-font.TPlo -fPIC -DPIC -o .libs/cairo-scaled-font.o cairo-scaled-font.c: In function `_cairo_scaled_font_glyph_device_extents': cairo-scaled-font.c:826: `INT16_MAX' undeclared (first use in this function) cairo-scaled-font.c:826: (Each undeclared identifier is reported only once cairo-scaled-font.c:826: for each function it appears in.) cairo-scaled-font.c:826: `INT16_MIN' undeclared (first use in this function) *** Error code 1 Download this patch and put it in /usr/ports/graphics/cairo/files: http://people.freebsd.org/~shaun/patches/cairo/patch-freebsd4 The Gnome team refuses to support FreeBSD 4.x any more. I highly recommend that you consider upgrading to a recent release. -- Shaun Amott // PGP: 0x6B387A9A A foolish consistency is the hobgoblin of little minds. - Ralph Waldo Emerson pgpfcABC7QtH9.pgp Description: PGP signature
Ports with version numbers going backwards: print/pdflib, print/pdflib-perl
** The following ports have a version number that sorts before a previous one ** For many package tools to work correctly, it is of utmost importance that version numbers of a port form a monotonic increasing sequence over time. Refer to the FreeBSD Porter's Handbook, 'Package Naming Conventions' for more information. Tools that won't work include pkg_version, portupgrade and portaudit. A common error is an accidental deletion of PORTEPOCH. Please fix any errors as soon as possible. - *print/pdflib* [EMAIL PROTECTED]: pdflib-7.0.0_1 pdflib-7.0.0p1 | revision 1.50 | date: 2006/10/15 08:30:11; author: ale; state: Exp; lines: +3 -2 | Fix fetching. | | Approved by: portmgr (implicitly) - *print/pdflib-perl* [EMAIL PROTECTED]: pdflib-perl-7.0.0_1 pdflib-perl-7.0.0p1 | revision 1.3 | date: 2004/06/25 11:23:01; author: ale; state: Exp; lines: +3 -5 | - Update to 6.0.0 release | - Re-enable cxx support (master: print/pdflib) | revision 1.50 | date: 2006/10/15 08:30:11; author: ale; state: Exp; lines: +3 -2 | Fix fetching. | | Approved by: portmgr (implicitly) ___ freebsd-ports@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-ports To unsubscribe, send any mail to [EMAIL PROTECTED]
Re: graphics/cairo broken on 4.11-RELEASE-p25?
On 10/15/06, Shaun Amott [EMAIL PROTECTED] wrote: On Sun, Oct 15, 2006 at 04:56:07PM +0200, Kjell B. wrote: I can't get this to upgrade from cairo-1.0.4_1 to cairo-1.2.4. Far into the build: ... cc -DHAVE_CONFIG_H -I. -I. -I.. -I. -I../pixman/src -I/usr/local/include/freetype2 -I/usr/local/include -I/usr/X11R6/include -I/usr/local/include -I/usr/X11R6/include -Wall -Wsign-compare -Werror-implicit-function-declaration -Wpointer-arith -Wwrite-strings -Wstrict-prototypes -Wmissing-prototypes -Wmissing-declarations -Wnested-externs -fno-strict-aliasing -D_THREAD_SAFE -I/usr/X11R6/include -O -pipe -march=pentiumpro -c cairo-scaled-font.c -Wp,-MD,.deps/cairo-scaled-font.TPlo -fPIC -DPIC -o .libs/cairo-scaled-font.o cairo-scaled-font.c: In function `_cairo_scaled_font_glyph_device_extents': cairo-scaled-font.c:826: `INT16_MAX' undeclared (first use in this function) cairo-scaled-font.c:826: (Each undeclared identifier is reported only once cairo-scaled-font.c:826: for each function it appears in.) cairo-scaled-font.c:826: `INT16_MIN' undeclared (first use in this function) *** Error code 1 Download this patch and put it in /usr/ports/graphics/cairo/files: http://people.freebsd.org/~shaun/patches/cairo/patch-freebsd4 We support a select few on 4.x and cairo is one of them. We should commit this patch. The Gnome team refuses to support FreeBSD 4.x any more. I highly recommend that you consider upgrading to a recent release. -- Shaun Amott // PGP: 0x6B387A9A A foolish consistency is the hobgoblin of little minds. - Ralph Waldo Emerson ___ freebsd-ports@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-ports To unsubscribe, send any mail to [EMAIL PROTECTED]
Re: Port Bloat
On Sat, Oct 14, 2006 at 10:53:32PM -0700, Peter Thoenen wrote: A couple months ago somebody posted a heads up on this list from the FreeBSD Ports Team about ports bloat and the massive influx of new software along with all the unmaintained ports. Has the port team ever thought about: A) Making a delete port pr request. This way port maintainers INSTEAD of marking 'transfer ownership to [EMAIL PROTECTED]' and hoping somebody takes it over one day could actually just delete ports they no longer wish to maintain. There should be some sort of WARN marking mechanism though (valid for X months (maybe 6)) that notifies any new user (or current via a portupgrade and EPOCH bumb) that this port is no longer maintained and scheduled for deletion unless one of them takes over maitainership by DATE. If you can make a good case for a port being useless (e.g. superceded by something else, only useful for obsolete purposes, etc), then you can follow the usual deprecation procedure. Otherwise, functioning but unmaintained ports should not be deleted en masse. Kris pgph5FwOPbb60.pgp Description: PGP signature
Re: devel/avr-gcc and devel/avr-gcc-devel
As Doug Barton wrote: Looks like someone else already got to this, the cvs master is already updated. I did after Matthew reported it, and after getting portmgr's approval. -- cheers, Jorg .-.-. --... ...-- -.. . DL8DTL http://www.sax.de/~joerg/NIC: JW11-RIPE Never trust an operating system you don't have sources for. ;-) ___ freebsd-ports@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-ports To unsubscribe, send any mail to [EMAIL PROTECTED]
Re: Port Bloat
Peter Thoenen wrote: A) Making a delete port pr request. This way port maintainers INSTEAD of marking 'transfer ownership to [EMAIL PROTECTED]' and hoping somebody takes it over one day could actually just delete ports they no longer wish to maintain. There should be some sort of WARN marking mechanism though (valid for X months (maybe 6)) that notifies any new user (or current via a portupgrade and EPOCH bumb) that this port is no longer maintained and scheduled for deletion unless one of them takes over maitainership by DATE. When I asked for one of my ports to be deleted, the request was honored extremely quickly and without trouble. I see no need for a special procedure for this. Stephen ___ freebsd-ports@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-ports To unsubscribe, send any mail to [EMAIL PROTECTED]
Re: HEADS UP: GNOME 2.16.1 has been committed
Joe Marcus Clarke wrote: The FreeBSD GNOME Team is proud to announce that GNOME 2.16.1 has been imported into the ports tree in time for FreeBSD 6.2. This is a first. Usually the GNOME release cycle has conflicted with the FreeBSD release cycle. However, thanks to Kris and pointyhat, we were able to get the major patch tested. Below is the commit message that accompanied this huge release. In addition to the core GNOME ports, almost 500 ports were also touched to chase the GNOME move from X11BASE to LOCALBASE and fix build problems with the new freetype2. Presenting GNOME 2.16.1 for FreeBSD. This release represents a massive amount of work by the FreeBSD GNOME Team and our testers. On top of the usual GNOME update, we have taken this opportunity to move GNOME from X11BASE to LOCALBASE. This means roughly 600 ports NOT part of the GNOME Desktop also need to be changed. The bulk of the move was carried out by ahze, mezz, and pav, but it would not have been possible without cooperation from the FreeBSD KDE team who worked with us to make sure GNOME and KDE can still coexist happily. We would also like to send a shout out to kris and pointyhat for putting up with multiple test runs until we got something that was solid. Back to GNOME 2.16. This release brings a huge amount of new functionality to FreeBSD. The standard release notes can be read at http://www.gnome.org/start/2.16/ . But on top of what you will read there, jylefort and marcus have completed work on a port of HAL to FreeBSD. This will allow FreeBSD to take advantage of closer hardware interaction such as auto-mounting CD-ROMs, USB drives, and music players; auto-playing audio CDs; and managing laptop power consumption. Hello and thanks for your hard work! I've been using WITH_GECKO=seamonkey (and WITH_MOZILLA=seamonkey) and now when trying to install new Gnome (after uninstalling nearly everything) I've got the following error message from yelp installation: checking which gecko to use... seamonkey checking for compiler -fshort-wchar option... yes checking whether to enable C++ RTTI... no checking whether we have a gtk 2 gecko build... yes checking whether we have a gecko debug build... no checking for gecko version... 1.8 configure: error: seamonkey is not supported === Script configure failed unexpectedly. Please run the gnomelogalyzer, available from http://www.freebsd.org/gnome/gnomelogalyzer.sh;, which will diagnose the problem and suggest a solution. If - and only if - the gnomelogalyzer cannot solve the problem, report the build failure to the FreeBSD GNOME team at [EMAIL PROTECTED], and attach (a) /usr/ports/x11/yelp/work/yelp-2.16.1/config.log, (b) the output of the failed make command, and (c) the gnomelogalyzer output. Also, it might be a good idea to provide an overview of all packages installed on your system (i.e. an `ls /var/db/pkg`). Put your attachment up on any website, copy-and-paste into http://freebsd-gnome.pastebin.com, or use send-pr(1) with the attachment. Try to avoid sending any attachments to the mailing list ([EMAIL PROTECTED]), because attachments sent to FreeBSD mailing lists are usually discarded by the mailing list software. *** Error code 1 Stop in /usr/ports/x11/yelp. *** Error code 1 Stop in /usr/ports/x11/yelp. *** Error code 1 Stop in /usr/ports/x11/gnome2-lite. *** Error code 1 Stop in /usr/ports/x11/gnome2-lite. ** Command failed [exit code 1]: /usr/bin/script -qa /tmp/portinstall.3919.0 env make reinstall ** Fix the installation problem and try again. --- Installation of x11/gnome2-lite ended at: Mon, 16 Oct 2006 00:24:55 +0200 (consumed 00:04:15) --- Fresh installation of x11/gnome2-lite ended at: Mon, 16 Oct 2006 00:24:55 +0200 (consumed 00:05:26) --- ** Install tasks 1: 0 done, 0 ignored, 0 skipped and 1 failed [Updating the pkgdb format:bdb_btree in /var/db/pkg ... - 372 packages found (-0 +1) . done] --- Listing the results (+:done / -:ignored / *:skipped / !:failed) ! x11/gnome2-lite (install error) --- Packages processed: 0 done, 0 ignored, 0 skipped and 1 failed --- Session ended at: Mon, 16 Oct 2006 00:24:57 +0200 (consumed 00:06:22) I cannot see a reason why seamonkey wouldn't be supported (and it's listed in yelp/Makefile). Could you please check and fix this ? Cheers, Martin ___ freebsd-ports@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-ports To unsubscribe, send any mail to [EMAIL PROTECTED]
Ports with version numbers going backwards: print/pdflib, print/pdflib-perl
** The following ports have a version number that sorts before a previous one ** For many package tools to work correctly, it is of utmost importance that version numbers of a port form a monotonic increasing sequence over time. Refer to the FreeBSD Porter's Handbook, 'Package Naming Conventions' for more information. Tools that won't work include pkg_version, portupgrade and portaudit. A common error is an accidental deletion of PORTEPOCH. Please fix any errors as soon as possible. - *print/pdflib* [EMAIL PROTECTED]: pdflib-7.0.0_1 pdflib-7.0.0p1 | revision 1.50 | date: 2006/10/15 08:30:11; author: ale; state: Exp; lines: +3 -2 | Fix fetching. | | Approved by: portmgr (implicitly) - *print/pdflib-perl* [EMAIL PROTECTED]: pdflib-perl-7.0.0_1 pdflib-perl-7.0.0p1 | revision 1.3 | date: 2004/06/25 11:23:01; author: ale; state: Exp; lines: +3 -5 | - Update to 6.0.0 release | - Re-enable cxx support (master: print/pdflib) | revision 1.50 | date: 2006/10/15 08:30:11; author: ale; state: Exp; lines: +3 -2 | Fix fetching. | | Approved by: portmgr (implicitly) ___ freebsd-ports@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-ports To unsubscribe, send any mail to [EMAIL PROTECTED]
FreeBSD Port: audio/gtkpod
Hi, I ranned into a couple of problems with this port. 1. Checksum mismatch. Attempting to fetch from http://heanet.dl.sourceforge.net/sourceforge/gtkpod/. fetch: http://heanet.dl.sourceforge.net/sourceforge/gtkpod/gtkpod-0.99.8.tar.gz: size of remote file is not known gtkpod-0.99.8.tar.gz 2600 B 479 kBps === Found saved configuration for gtkpod-0.99.8 = MD5 Checksum mismatch for gtkpod-0.99.8.tar.gz. = SHA256 Checksum mismatch for gtkpod-0.99.8.tar.gz. === Giving up on fetching files: gtkpod-0.99.8.tar.gz gtkpod-0.99.8.tar.gz Make sure the Makefile and distinfo file (/usr/ports/audio/gtkpod/distinfo) are up to date. If you are absolutely sure you want to override this check, type make NO_CHECKSUM=yes [other args]. *** Error code 1 2. Tar format problem? make NO_CHECKSUM=yes install === Found saved configuration for gtkpod-0.99.8 === Extracting for gtkpod-0.99.8 tar: Unrecognized archive format: Inappropriate file type or format *** Error code 1 v/r Derrick ___ freebsd-ports@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-ports To unsubscribe, send any mail to [EMAIL PROTECTED]
Cricket port on AMD64
I'm trying to replace an old machine. I've got a new Sun X2100 that I plan on using for this, and I have installed 6.2 AMD64 on it. However, I'm getting a message in the Cricket cgi pages about AMD64 not being supported. What is the status of this? Should I reinstall with teh I386 version of 6.2? -- Unix is very simple, but it takes a genius to understand the simplicity. (Dennis Ritchie) ___ freebsd-ports@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-ports To unsubscribe, send any mail to [EMAIL PROTECTED]
eboard port puking
tried to portupgrade.. no avail sd# portupgrade eboard [Updating the pkgdb format:dbm_hash in /var/db/pkg ... - 115 packages found (-0 +1) . done] [Updating the portsdb format:dbm_hash in /usr/ports ... - 14186 port entries found .1000.2000.3000.4000.5000.6000.7000.8000.9000.1.11000.12000.13000.14000. . done] --- Skipping 'games/eboard' (eboard-0.9.5_1) because it has already been ignored ** Listing the failed packages (*:skipped / !:failed) * games/eboard (eboard-0.9.5_1) --- Packages processed: 0 done, 1 ignored, 1 skipped and 0 failed bsd# eboard /libexec/ld-elf.so.1: Shared object libgmodule12.so.3 not found, required by libgdk_imlib.so.5 bsd# ___ freebsd-ports@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-ports To unsubscribe, send any mail to [EMAIL PROTECTED]
