Re: Source install to look like installed package
On Wed, Sep 17, 2008 at 04:40:59PM -0400, Francisco Reyes wrote: > Matthew Seaman writes: > > > You mean you want to generate a /var/db/pkg/portname-1.2.3 > > directory with appropriate contents so you can wrangle a bunch > > of files already on your hard drive as if they were a port? > > Yes. > > > Actually, that's pretty much what the ports system does when you > > do an install from source. Check out the commands the 'do-package' > > target runs as shown in /usr/ports/Mk/bsd.port.mk > > > Ok. > > > Submitting PRs with updates to bring the FreePascal port up to date > > will earn you karma points... > > I am thinking perhaps start out with a "binary" port or a package until I > get familiar with the port system. In most cases that's actually a bit harder than doing a simple port :) Of course, there are applications that do not lend themselves to porting simply, but in most cases even the "Quick Porting" procedure described in the Porters Handbook[1] is enough to get you a working, albeit not picture-perfect, package. [1] http://www.freebsd.org/doc/en_US.ISO8859-1/books/porters-handbook/ G'luck, Peter -- Peter Pentchev [EMAIL PROTECTED][EMAIL PROTECTED][EMAIL PROTECTED] PGP key:http://people.FreeBSD.org/~roam/roam.key.asc Key fingerprint FDBA FD79 C26F 3C51 C95E DF9E ED18 B68D 1619 4553 You have, of course, just begun reading the sentence that you have just finished reading. pgpJvoNTRvwDE.pgp Description: PGP signature
ftp/py-curl - fails: mtree
Hi, The build which triggered this email is done under tinderbox-2.4.3, on 7-STABLE on amd64, with tinderd_flags="-nullfs -plistcheck -onceonly" and ccache support, with the "official" up-to-date Ports Tree, with the following vars set: NOPORTDOCS=yes, NOPORTEXAMPLES=yes, NOPORTDATA=yes, FORCE_PACKAGE=yes. The build of this port was tried 6 times since last BotMail while trying to build ports that depend on it. Excerpt from http://T64.TecNik93.com/logs/7-STABLE-FTP/py25-curl-7.16.4.log : building py25-curl-7.16.4 in directory /var/tinderbox/7-STABLE-FTP maintained by: [EMAIL PROTECTED] building for: 7.0-STABLE amd64 port directory: /usr/ports/ftp/py-curl Makefile ident: $FreeBSD: ports/ftp/py-curl/Makefile,v 1.30 2008/05/30 05:21:25 perky Exp $ prefixes: LOCALBASE=usr/local X11BASE=usr/local NO* env vars: NOPORTDOCS=yes NOPORTEXAMPLES=yes NOPORTDATA=yes build started at Thu Sep 18 06:29:13 UTC 2008 ... Registering depends: curl-7.18.0 python25-2.5.2_3. Creating bzip'd tar ball in '/tmp/packages/All/py25-curl-7.16.4.tbz' Deleting py25-curl-7.16.4 === Checking filesystem state list of extra files and directories in / (not present before this port was installed but present after it was deinstalled) 28983504 drwxr-xr-x3 root wheel 512 Sep 18 06:29 usr/local/share/doc/py-curl 2898351 56 -rw-r--r--1 root wheel 27397 Jul 11 2007 usr/local/share/doc/py-curl/ChangeLog 2898352 52 -rw-r--r--1 root wheel 26526 Jul 18 2002 usr/local/share/doc/py-curl/COPYING 28983534 -rw-r--r--1 root wheel1509 Sep 6 2005 usr/local/share/doc/py-curl/INSTALL 28983544 -rw-r--r--1 root wheel 471 Apr 22 2007 usr/local/share/doc/py-curl/README 28983554 -rw-r--r--1 root wheel1058 Apr 23 2007 usr/local/share/doc/py-curl/TODO 28983644 drwxr-xr-x2 root wheel1024 Sep 18 06:29 usr/local/share/doc/py-curl/tests 28983654 -rw-r--r--1 root wheel1953 Apr 10 2007 usr/local/share/doc/py-curl/tests/test.py 28983664 -rw-r--r--1 root wheel 693 Apr 21 2003 usr/local/share/doc/py-curl/tests/test_cb.py 28983674 -rw-r--r--1 root wheel 340 Apr 21 2003 usr/local/share/doc/py-curl/tests/test_debug.py 28983684 -rw-r--r--1 root wheel 289 Aug 24 2006 usr/local/share/doc/py-curl/tests/test_ftp.py 28983694 -rw-r--r--1 root wheel1419 May 1 2003 usr/local/share/doc/py-curl/tests/test_getinfo.py 28983708 -rw-r--r--1 root wheel2733 Mar 30 2005 usr/local/share/doc/py-curl/tests/test_gtk.py 2898371 12 -rw-r--r--1 root wheel5476 May 1 2003 usr/local/share/doc/py-curl/tests/test_internals.py 28983724 -rw-r--r--1 root wheel1126 May 1 2003 usr/local/share/doc/py-curl/tests/test_memleak.py 28983734 -rw-r--r--1 root wheel 676 Mar 11 2005 usr/local/share/doc/py-curl/tests/test_multi.py 28983744 -rw-r--r--1 root wheel1746 Apr 10 2007 usr/local/share/doc/py-curl/tests/test_multi2.py 28983758 -rw-r--r--1 root wheel2068 Mar 11 2005 usr/local/share/doc/py-curl/tests/test_multi3.py 28983764 -rw-r--r--1 root wheel1400 Mar 11 2005 usr/local/share/doc/py-curl/tests/test_multi4.py 28983774 -rw-r--r--1 root wheel1472 Mar 11 2005 usr/local/share/doc/py-curl/tests/test_multi5.py 28983784 -rw-r--r--1 root wheel1536 Mar 11 2005 usr/local/share/doc/py-curl/tests/test_multi6.py 28983794 -rw-r--r--1 root wheel1924 Nov 10 2006 usr/local/share/doc/py-curl/tests/test_multi_socket.py 28983804 -rw-r--r--1 root wheel1749 Nov 10 2006 usr/local/share/doc/py-curl/tests/test_multi_timer.py 2898381 12 -rw-r--r--1 root wheel5773 Apr 12 2005 usr/local/share/doc/py-curl/tests/test_multi_vs_thread.py 28983824 -rw-r--r--1 root wheel 589 Apr 21 2003 usr/local/share/doc/py-curl/tests/test_post.py 28983834 -rw-r--r--1 root wheel 535 Mar 3 2005 usr/local/share/doc/py-curl/tests/test_post2.py 28983844 -rw-r--r--1 root wheel 804 Jun 21 2004 usr/local/share/doc/py-curl/tests/test_post3.py 28983
clamav port for 0.94 version , pls help
Hi, My server version is freebsd6.2 amd64. I have installed clamav to scan my incoming mail. Everything works smoothly for several years. Recently, I need to upgrade clamav version from 0.92 to 0.94 (latest version). Actually, I had done this upgrade clamav process before. My procedures is : 1. run "make deinstall" to deinstall the clamav version of 0.92 2. Modify /usr/ports-supfile (to make sure security port can be download from a correct default host) *default host=ftp.tw.freebsd.org ports-security <--- remark ports-all, and enable the ports-security only 3. cd /usr ; run "cvsup -g -L 2 ports-supfile 4. check /usr/port/security/clamav port is updated 5. cd /usr/port/security/clamav 6. run "make install clean" There is no error message found in the whole process, however, I cannot find the file of "clamd", "clamscan" & "freshclam". The previous version of these file can be found in /usr/local/sbin and /usr/local/bin Anyone have encoutered the same problem ? I am not sure whether my posting is put in the correct mailling list. Any comments are appreciated. Thanks. ___ freebsd-ports@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-ports To unsubscribe, send any mail to "[EMAIL PROTECTED]"
Re: STILL OPEN: Fwd: ports/127015: [patch] Impossible to fetch devel/valgrind from the jail
On Thu, Sep 18, 2008 at 03:38:28AM +0400, Alexander Churanov wrote: > In the beginning of September, I've filed an issue about > devel/valgrind and also sent an e-mail to port maintainer. The issue > is still unresolved. For future reference, the address to contact with issues with maintainers is [EMAIL PROTECTED] I've already forwarded your email to [EMAIL PROTECTED] mcl ___ freebsd-ports@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-ports To unsubscribe, send any mail to "[EMAIL PROTECTED]"
textproc/xslide.el - fails: mtree
Hi,
The build which triggered this email is done under tinderbox-2.4.3, on
7-STABLE on amd64, with tinderd_flags="-nullfs -plistcheck -onceonly"
and ccache support, with the "official" up-to-date Ports Tree, with the
following vars set:
NOPORTDOCS=yes, NOPORTEXAMPLES=yes, NOPORTDATA=yes, FORCE_PACKAGE=yes.
Excerpt from http://T64.TecNik93.com/logs/7-STABLE-FTP/xslide.el-0.2.2_1.log :
building xslide.el-0.2.2_1 in directory /var/tinderbox/7-STABLE-FTP
maintained by: [EMAIL PROTECTED]
building for: 7.0-STABLE amd64
port directory: /usr/ports/textproc/xslide.el
Makefile ident: $FreeBSD: ports/textproc/xslide.el/Makefile,v 1.6 2006/06/26
19:21:03 anray Exp $
prefixes: LOCALBASE=usr/local X11BASE=usr/local
NO* env vars: NOPORTDOCS=yes NOPORTEXAMPLES=yes NOPORTDATA=yes
build started at Thu Sep 18 00:51:20 UTC 2008
...
(cd /work/a/ports/textproc/xslide.el/work/xslide-0.2.2 && for f in xslide.el
xslide-abbrev.el xslide-data.el xslide-font.el xslide-initial.xsl
xslide-process.el; do install -o root -g wheel -m 444 $f
/usr/local/share/emacs/site-lisp; /bin/ln -sf
/usr/local/share/emacs/site-lisp/$f /usr/local/lib/xemacs/site-lisp; done;
install -o root -g wheel -m 444 README.TXT TODO NEWS ChangeLog
/usr/local/share/doc/xslide.el )
To use xsl-mode, add to your ~/.emacs the following lines:
;; XSL mode
(autoload 'xsl-mode "xslide" "Major mode for XSL stylesheets." t)
;; Turn on font lock when in XSL mode
(add-hook 'xsl-mode-hook
'turn-on-font-lock)
(setq auto-mode-alist
(append
(list
'("\\.fo" . xsl-mode)
'("\\.xsl" . xsl-mode))
auto-mode-alist))
;; Uncomment if using abbreviations
;; (abbrev-mode t)
===> Registering installation for xslide.el-0.2.2_1
===> Building package for xslide.el-0.2.2_1
Creating package /tmp/packages/All/xslide.el-0.2.2_1.tbz
Registering depends:.
Creating bzip'd tar ball in '/tmp/packages/All/xslide.el-0.2.2_1.tbz'
Deleting xslide.el-0.2.2_1
=== Checking filesystem state
list of extra files and directories in / (not present before this port was
installed but present after it was deinstalled)
27793344 drwxr-xr-x2 root wheel 512 Sep
18 00:51 usr/local/share/doc/xslide.el
2779341 12 -r--r--r--1 root wheel4574 Sep
18 00:51 usr/local/share/doc/xslide.el/README.TXT
27793424 -r--r--r--1 root wheel 95 Sep
18 00:51 usr/local/share/doc/xslide.el/TODO
27793434 -r--r--r--1 root wheel 427 Sep
18 00:51 usr/local/share/doc/xslide.el/NEWS
27793448 -r--r--r--1 root wheel2781 Sep
18 00:51 usr/local/share/doc/xslide.el/ChangeLog
build of /usr/ports/textproc/xslide.el ended at Thu Sep 18 00:51:23 UTC 2008
A description of the testing process can be found here:
http://T32.TecNik93.com/FreeBSD/QA-Tindy/testing_process.txt
Thanks for your work on making FreeBSD better,
--
IOnut - Un^d^dregistered ;) FreeBSD "user"
"Intellectual Property" is nowhere near as valuable as "Intellect"
FreeBSD committer -> [EMAIL PROTECTED], PGP Key ID 057E9F8B493A297B
___
freebsd-ports@freebsd.org mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-ports
To unsubscribe, send any mail to "[EMAIL PROTECTED]"
Re: port: security/cfs
On Wed, Sep 17, 2008 at 06:38:56PM -0400, Christopher Sean Hilton wrote: > The port security/cfs, Matt Blaze's userland Cryptographic filesystem, > is marked as broken because it does not compile under FreeBSD-7.0 or > later. ports/127457 Edwin -- Edwin Groothuis |Personal website: http://www.mavetju.org [EMAIL PROTECTED]| Weblog: http://www.mavetju.org/weblog/ ___ freebsd-ports@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-ports To unsubscribe, send any mail to "[EMAIL PROTECTED]"
Re: port: security/cfs
On Wed, Sep 17, 2008 at 06:38:56PM -0400, Christopher Sean Hilton wrote: > The port security/cfs, Matt Blaze's userland Cryptographic filesystem, > is marked as broken because it does not compile under FreeBSD-7.0 or > later. I got patches which I (stupidely) never commited. I'll send0pr them so they will be kept tracked. Edwin -- Edwin Groothuis |Personal website: http://www.mavetju.org [EMAIL PROTECTED]| Weblog: http://www.mavetju.org/weblog/ ___ freebsd-ports@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-ports To unsubscribe, send any mail to "[EMAIL PROTECTED]"
STILL OPEN: Fwd: ports/127015: [patch] Impossible to fetch devel/valgrind from the jail
Wesley, In the beginning of September, I've filed an issue about devel/valgrind and also sent an e-mail to port maintainer. The issue is still unresolved. I've also noted that the same person is responsible for devel/boost, that is of version 1.34 in ports while current version is 1.36. The version 1.34 released more than a year ago. Given that, could you verify that the person who maintains that ports is still interested in / capable of doing that? In case current maintainer is not reachable I'd like to start managing this two ports. I was not maintaining ports in FreeBSD before, but I'm experienced software engineer and think that I could manage all technical issues that may arise if any. Alexander Churanov -- Forwarded message -- From: Alexander Churanov <[EMAIL PROTECTED]> Date: Tue, 9 Sep 2008 00:39:32 +0400 Subject: ports/127015: [patch] Impossible to fetch devel/valgrind from the jail To: [EMAIL PROTECTED] Hi! Recently I've suggested a patch to devel/valgrind Makefile. However, the issue is still open currently. Details are here: http://www.freebsd.org/cgi/query-pr.cgi?pr=127015 Just want to know, is supplied patch acceptable to check it in? Alexander Churanov ___ freebsd-ports@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-ports To unsubscribe, send any mail to "[EMAIL PROTECTED]"
port: security/cfs
The port security/cfs, Matt Blaze's userland Cryptographic filesystem,
is marked as broken because it does not compile under FreeBSD-7.0 or
later.
I've managed to get it to compile through some simple changes but I
don't know enough about RPC to know if I am on the right track. I'm
asking for the help of an RPC wizard to check my train of thought.
The big change is rpcgen. In FreeBSD 6.0 it builds a C header file
with prototypes like this:
void * rpc_entry_point();
Now it builds prototypes like this:
void * rpc_entry_point(struct yourtype * yourvar, CLIENT * clnt);
I'm guessing that the first prototype caused GCC 4.x to gag so rpcgen
was patched to produce the second when the move was made to FreeBSD-7.0.
The second problem is that CFS is coded with rpc entry points that
look like this.
void * rpc_entry_point(yourvar, rp)
struct yourtype * yourvar;
struct svc_req *rp;
{
int ret = 0;
...
return ret;
}
While gcc doesn't completely gag on that one it's not that happy about
it either.
The small issue here is that the coding style is ancient. Returning an
(int) 0 as NULL has been taboo in C for years and gcc is getting more
and more fussy about these problems as time passes. The bigger problem
is that the parameter types don't match up. But the mismatch is so
huge that I find it difficult to believe that code ever worked.
Looking further into things I discovered that rpcgen is basically
specifying an client-server interface. For every:
void * rpc_entry_point(struct yourtype * yt, CLIENT * clnt);
You also get:
void * rpc_entry_point_svc(struct yourtype *yt, struct svc_req
*rp);
Now CFS uses K&R to mangle up the _svc functions pretty well to but
basically if you patch cfs_adm.c and cfs_nfs.c to change the rpc entry
points from client to service definitions then the code compiles
reasonably cleanly with gcc 4.
After that long discussion does someone know RPC programming well
enough to verify that CFS was defining the Service side of thing all
along and that in the past RPC was loose enough to take
rpc_entry_point(... as the definition of the service which is now
properly called rpc_entry_point_svc(... ?
-- Chris
--
Chris Hilton chris-at-vindaloo-dot-com
"All I was doing was trying to get home from work!"
-- Rosa Parks
___
freebsd-ports@freebsd.org mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-ports
To unsubscribe, send any mail to "[EMAIL PROTECTED]"
Re: axis2/c & port
-BEGIN PGP SIGNED MESSAGE- Hash: SHA512 Franco Marchesini wrote: | Hello guys, Hello, | there is someone that already working on axis2/c ports? Yes me, I have a draft ready and am waiting for the ports tree to un-freeze before committing it. I will send it to you tomorrow for review, if you would like :) | Ciao Ciao, | Franco - -- Pietro Cerutti [EMAIL PROTECTED] PGP Public Key: http://gahr.ch/pgp -BEGIN PGP SIGNATURE- Version: GnuPG v2.0.9 (FreeBSD) iEYEAREKAAYFAkjRdZ4ACgkQwMJqmJVx9474qQCghk2tbzDp74tWvbjhF+CuEXbf GEkAnjgMgm/RXKeNBFObm3qlv3tmQOlG =hESM -END PGP SIGNATURE- ___ freebsd-ports@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-ports To unsubscribe, send any mail to "[EMAIL PROTECTED]"
Re: Source install to look like installed package
Matthew Seaman writes: You mean you want to generate a /var/db/pkg/portname-1.2.3 directory with appropriate contents so you can wrangle a bunch of files already on your hard drive as if they were a port? Yes. Actually, that's pretty much what the ports system does when you do an install from source. Check out the commands the 'do-package' target runs as shown in /usr/ports/Mk/bsd.port.mk Ok. Submitting PRs with updates to bring the FreePascal port up to date will earn you karma points... I am thinking perhaps start out with a "binary" port or a package until I get familiar with the port system. Thanks for the pointers. ___ freebsd-ports@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-ports To unsubscribe, send any mail to "[EMAIL PROTECTED]"
Re: OPTIONS handling doesn't seem to work fully in dependencies anymore
Alexey Dokuchaev wrote: > I also don't think that we can simply tell our users to user portmaster > or some force-config switches. If you read my post carefully I was suggesting that using portmaster would be a temporary workaround while the actual problem is (hopefully) being fixed. Doug -- This .signature sanitized for your protection ___ freebsd-ports@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-ports To unsubscribe, send any mail to "[EMAIL PROTECTED]"
Re: OPTIONS handling doesn't seem to work fully in dependencies anymore
On Wednesday 17 September 2008 03:44:14 am Alexey Dokuchaev wrote: > On Wed, Sep 17, 2008 at 08:52:31AM +0200, Alex Dupre wrote: > > Alexey Dokuchaev wrote: > > >Nevertheless, going back to rev. 1.559 of b.p.m. restores correct > > >behavior. > > > > Are you sure? I didn't try, but that commit seems to add new reasons to > > show up the dialog box while not removing any of the old ones. > > Running "make config-recursive" still works (and it calls recursively > > "make config-conditional" that works), so it seems john's analysis is > > correct, but I cannot figure how (and if) ever worked before. > > Perhaps I was too fast in my response; I cannot reproduce it now. While > I'm trying to continuously approach revision that used to work, I'm > starting to suspect that what if it never actually worked? > > John, how old was your ports tree on 6.x? Maybe this can shed some light > on the subject.. I had updated it the day before my e-mail. When I noticed that ports weren't popping up config screens, I actually stopped my build of ports/x11/kde4 at one point and did a 'make config-recursive' from that port and encountered several config screens (libxine, qt4-gui, etc.) -- John Baldwin ___ freebsd-ports@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-ports To unsubscribe, send any mail to "[EMAIL PROTECTED]"
Re: OPTIONS handling doesn't seem to work fully in dependencies anymore
On Wednesday 17 September 2008 02:41:07 am Alex Dupre wrote: > Doug Barton wrote: > > John was referring to the problem of 'make config' not being called for > > ports being installed as dependencies of a port that has OPTIONS. > > John said (correct me if I'm wrong) that with an up-to-date system > OPTIONS doesn't correctly shows up (when the top port has OPTIONS), but > with an "old" system this worked. Reading the bsd.port.mk, the > "incriminated" CONFIG_DONE rows never changed since the introduction of > the OPTIONS support, so I think this *never* worked as expected. It used to work. I was just guessing about how it might not be working now based on reading the existing logic. I have not delved into the history to see what has changed. -- John Baldwin ___ freebsd-ports@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-ports To unsubscribe, send any mail to "[EMAIL PROTECTED]"
Re: Evince 2.22.2_3: "Unhandled MIME type: “applic ation/pdf”"
Jeremy Messenger wrote: [...] Have you guys follow in /usr/ports/UPDATING? Mezz is refering to the entry labeled 20080725: 20080725: AFFECTS: users of x11-fm/nautilus and misc/shared-mime-info AUTHOR: [EMAIL PROTECTED] In order to properly update x11-fm/nautilus and misc/shared-mime-info, do the following using portupgrade: # pkg_deinstall -fO nautilus # portupgrade shared-mime-info # portinstall -O nautilus Once misc/shared-mime-info has been updated, each user will need to run the following command: $ update-mime-database ~/.local/share/mime/ which, after I followed the instructions, results in a working Nautilus. I wasn't able to find a Nautilus/GNOME command-line equivalent to file(1), but context-clicking in Nautilus to show the "Properties" dialog reports the MIME type that Nautilus thinks the file represents. -- <[EMAIL PROTECTED]> "[T]his is not a disentanglement from, but a progressive knotting into." ___ freebsd-ports@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-ports To unsubscribe, send any mail to "[EMAIL PROTECTED]"
Re: Evince 2.22.2_3: "Unhandled MIME type: “application/pdf”""
On Wed, 17 Sep 2008 07:56:55 -0500, Mark Evenson <[EMAIL PROTECTED]> wrote: Jeremy Messenger wrote: On Tue, 16 Sep 2008 09:57:03 -0500, Mark Evenson <[EMAIL PROTECTED]> wrote: Dan Reinholz wrote: Since updating to the latest revision of Evince (to 2.22.2_3 from 2.22.2_2) I am no longer able to open .pdf files. Anytime I try to do so I now get the error: [...] Have you guys follow in /usr/ports/UPDATING? Which entry? Grep'ing for 'evince' doesn't show anything. Grep for 'mime'. You shouldn't be use grep, which you should be use your own eyes. On additional nosing around, it seems that GNOME (at least Nautilus) has lost the notion of MIME types altogether. Is there a command-line equivalent to magic(1) for GNOME to show what GNOME thinks the underlying MIME type consists of? -- [EMAIL PROTECTED] - [EMAIL PROTECTED] FreeBSD GNOME Team http://www.FreeBSD.org/gnome/ - [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: Evince 2.22.2_3: "Unhandled MIME type: “applic ation/pdf”"
Em Qua, 2008-09-17 às 14:56 +0200, Mark Evenson escreveu: > Jeremy Messenger wrote: > > On Tue, 16 Sep 2008 09:57:03 -0500, Mark Evenson <[EMAIL PROTECTED]> > > wrote: > > > >> Dan Reinholz wrote: > >>> Since updating to the latest revision of Evince (to > >>> 2.22.2_3 from 2.22.2_2) I am no longer able to open > >>> .pdf files. Anytime I try to do so I now get the > >>> error: > > [...] > > > Have you guys follow in /usr/ports/UPDATING? > > Which entry? Grep'ing for 'evince' doesn't show anything. > > On additional nosing around, it seems that GNOME (at least Nautilus) has > lost the notion of MIME types altogether. > > Is there a command-line equivalent to magic(1) for GNOME to show what > GNOME thinks the underlying MIME type consists of? > > > seems that your mime database is corrupted/altered the command: "update-mime-database" (root user) should fix it (in a global basis) if not, your local mime database is corrupted as a last help, 1) save evolution by making a backup of it (in the evolution file tab) 2) rename your user directory to anoter one 3) log out, in again 4) move your directories files (documents) 5) restore evolution from backup... restore your background image... panel icons... sure works > ___ freebsd-ports@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-ports To unsubscribe, send any mail to "[EMAIL PROTECTED]"
Re: Evince 2.22.2_3: "Unhandled MIME type: “applic ation/pdf”"
Jeremy Messenger wrote: On Tue, 16 Sep 2008 09:57:03 -0500, Mark Evenson <[EMAIL PROTECTED]> wrote: Dan Reinholz wrote: Since updating to the latest revision of Evince (to 2.22.2_3 from 2.22.2_2) I am no longer able to open .pdf files. Anytime I try to do so I now get the error: [...] Have you guys follow in /usr/ports/UPDATING? Which entry? Grep'ing for 'evince' doesn't show anything. On additional nosing around, it seems that GNOME (at least Nautilus) has lost the notion of MIME types altogether. Is there a command-line equivalent to magic(1) for GNOME to show what GNOME thinks the underlying MIME type consists of? -- <[EMAIL PROTECTED]> "[T]his is not a disentanglement from, but a progressive knotting into." ___ freebsd-ports@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-ports To unsubscribe, send any mail to "[EMAIL PROTECTED]"
axis2/c & port
Hello guys, there is someone that already working on axis2/c ports? Ciao Franco ___ freebsd-ports@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-ports To unsubscribe, send any mail to "[EMAIL PROTECTED]"
Re: OPTIONS handling doesn't seem to work fully in dependencies anymore
On Wed, Sep 17, 2008 at 08:52:31AM +0200, Alex Dupre wrote: > Alexey Dokuchaev wrote: > >Nevertheless, going back to rev. 1.559 of b.p.m. restores correct > >behavior. > > Are you sure? I didn't try, but that commit seems to add new reasons to > show up the dialog box while not removing any of the old ones. > Running "make config-recursive" still works (and it calls recursively > "make config-conditional" that works), so it seems john's analysis is > correct, but I cannot figure how (and if) ever worked before. Perhaps I was too fast in my response; I cannot reproduce it now. While I'm trying to continuously approach revision that used to work, I'm starting to suspect that what if it never actually worked? John, how old was your ports tree on 6.x? Maybe this can shed some light on the subject.. ./danfe ___ freebsd-ports@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-ports To unsubscribe, send any mail to "[EMAIL PROTECTED]"
