Re: Users and groups kept after a port deinstallation
-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 On 23/05/2010 02:50:00, Ade Lovett wrote: On May 22, 2010, at 16:39 , Anonymous wrote: Such unused entries in passwd add clutter. It in turn makes managing users more complex. You have to remember which users are created by you and which ones are created by ports. Irrespective of the UID/GID stuff mentioned elsewhere, merely go through the ports tree and add (or append) (created by ports) to the GECOS field of any such created users. OpenBSD has a convention that all system user accounts start with a '_' character. There are a few accounts in UIDs that have adopted that, but no great stampede to adopt the idea despite most people agreeing with it. Cheers, Matthew - -- Dr Matthew J Seaman MA, D.Phil. 7 Priory Courtyard Flat 3 PGP: http://www.infracaninophile.co.uk/pgpkey Ramsgate Kent, CT11 9PW -BEGIN PGP SIGNATURE- Version: GnuPG/MacGPG2 v2.0.14 (Darwin) Comment: Using GnuPG with Mozilla - http://enigmail.mozdev.org/ iEYEARECAAYFAkv4xFkACgkQ8Mjk52CukIxtUgCgh3ulQ2NBlHrFJIMWSb0eQYnc lhEAn2J9Fx+gpzv7Z28pL3VS8sv9rBDw =GACU -END PGP SIGNATURE- ___ 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: Users and groups kept after a port deinstallation
-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 On 23/05/2010 04:47:49, jhell wrote: But if a port can install a user there is no reason that it can not uninstall a user via pw(8) that is available from bsd.commands.mk after checking a recorded md5(1) sum that it could create upon installation for the output of pw usershow/groupshow UID/GID. The trick would be to teach the ports how to tell if a port was being deleted for good, when trashing the user would be appropriate, or if the port was being deleted as part of the process of upgrading it, when you'ld want to keep the user. Cheers, Matthew - -- Dr Matthew J Seaman MA, D.Phil. 7 Priory Courtyard Flat 3 PGP: http://www.infracaninophile.co.uk/pgpkey Ramsgate Kent, CT11 9PW -BEGIN PGP SIGNATURE- Version: GnuPG/MacGPG2 v2.0.14 (Darwin) Comment: Using GnuPG with Mozilla - http://enigmail.mozdev.org/ iEYEARECAAYFAkv4xPcACgkQ8Mjk52CukIyoCwCdERkAVk19Iy0el1EpR46GlKSo b6UAnAuVqhInDCfnAqw77mP5UrKKAYgK =17k9 -END PGP SIGNATURE- ___ 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: Users and groups kept after a port deinstallation
On Sat, 22 May 2010 23:21:35 -0400 jhell jh...@dataix.net wrote: You being the originator of the thread called Users and groups kept after a port deinstallation which implies to me that you had a problem with users left behind on a system am I correct ? No, and the OP and I have different names and email addresses. If you really do not care about them after suggestions have been made in either point that would help with the above subject line then what is the original intention of your email ? why did you even write it ? I didn't ___ 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: Users and groups kept after a port deinstallation
On Sun, 23 May 2010 07:57:36 +0400 Anonymous swel...@gmail.com wrote: You don't have to remember, just look at the UID/GID values, ordinary users start at 1001, ports create UIDs 1000. You're presuming non-ordinary users are created only by ports framework. That's not always the case. I may want for example a separate user for telnetd to broadcast ascii movies or youterm sessions. ;) This has no relevance, we're talking about users that were previously created by ports and left behind after port deletions. This appears to refer to an admin confusing a normal user with a system user that's still in use by a port, so I don't see the relevance. No. It's about conflict: system user created by admin and system user created by port happen to have same username. pw and adduser wont let you add usernames that already exist. I've no idea whether pwd_mkdb allows duplicates usernames with different UIDs, I've never tried it, but if you create users that way without performing a check, you deserve what you get. ___ 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
Update java for Firefox-3.6.3
It has been several months now since Firefox-3.6.3 was released into the ports system. Has a viable version of Java been created to work with this version of Firefox? I am unable to locate any information in regards to this on the FreeBSD web page. -- Jerry freebsd-ports.u...@seibercom.net Disclaimer: off-list followups get on-list replies or get ignored. Please do not ignore the Reply-To header. __ signature.asc Description: PGP signature
Re: Porting SANE backend 1.0.21 to FreeBSD 7.2
Warren, If this is the wrong place, please be gentle! I need to get a Canon 8800F scanner running on FreeBSD 7.2 . SANE's latest version is said to support this scanner. sane-backends 1.0.21 showed up in ports this morning... I'm sorry to be further trouble, but I've tried portupgrade and pkgdb -FU followed by portupgrade and even though the INDEX-7 file indicates that the sane-backend version is 1.0.21 I keep getting 1.0.20 downloaded. What should I be looking at? Mark Terribile ___ 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: Porting SANE backend 1.0.21 to FreeBSD 7.2
Warren, sane-backends 1.0.21 showed up in ports this morning... I'm sorry to be further trouble, but I've tried portupgrade and pkgdb -FU followed by portupgrade and even though the INDEX-7 file indicates that the sane-backend version is 1.0.21 I keep getting 1.0.20 downloaded. Here's a little more information: portinstall -f sane-backends-1.0.21 tells me Found already installed package(s) of 'graphics/sane-backends': sane-backends-1.0.20_4 portupgrade with various flags simply does nothing. The entry for sane-backends in INDEX-7 reads sane-backends-1.0.21|/usr/ports/graphics/sane-backends|/usr/local|API for access to scanners, digitals camera, frame grabbers etc|/usr/ports/graphics/sane-backends/pkg-descr|po...@freebsd.org|graphics|gettext-0.17_1 gmake-3.81_3 jbigkit-1.6 jpeg-8_2 libiconv-1.13.1_1 libusb-0.1.12_4 tiff-3.9.2_1|gettext-0.17_1 jbigkit-1.6 jpeg-8_2 libiconv-1.13.1_1 libusb-0.1.12_4 tiff-3.9.2_1|http://www.sane-project.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: Porting SANE backend 1.0.21 to FreeBSD 7.2
Mark Terribile materrib...@yahoo.com writes: Warren, sane-backends 1.0.21 showed up in ports this morning... I'm sorry to be further trouble, but I've tried portupgrade and pkgdb -FU followed by portupgrade and even though the INDEX-7 file indicates that the sane-backend version is 1.0.21 I keep getting 1.0.20 downloaded. Here's a little more information: portinstall -f sane-backends-1.0.21 tells me Found already installed package(s) of 'graphics/sane-backends': sane-backends-1.0.20_4 portupgrade with various flags simply does nothing. The entry for sane-backends in INDEX-7 reads sane-backends-1.0.21|/usr/ports/graphics/sane-backends|/usr/local|API for access to scanners, digitals camera, frame grabbers etc|/usr/ports/graphics/sane-backends/pkg-descr|po...@freebsd.org|graphics|gettext-0.17_1 gmake-3.81_3 jbigkit-1.6 jpeg-8_2 libiconv-1.13.1_1 libusb-0.1.12_4 tiff-3.9.2_1|gettext-0.17_1 jbigkit-1.6 jpeg-8_2 libiconv-1.13.1_1 libusb-0.1.12_4 tiff-3.9.2_1|http://www.sane-project.org/||| Sounds like you need a portsdb -uf. ___ 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: Porting SANE backend 1.0.21 to FreeBSD 7.2
Lowell, --- On Sun, 5/23/10, Lowell Gilbert freebsd-ports-lo...@be-well.ilk.org Warren, sane-backends 1.0.21 showed up in ports this morning... I'm sorry to be further trouble, but I've tried portupgrade and pkgdb -FU followed by portupgrade and even though the INDEX-7 file indicates that the sane-backend version is 1.0.21 I keep getting 1.0.20 downloaded. Here's a little more information: portinstall -f sane-backends-1.0.21 tells me Found already installed package(s) of 'graphics/sane-backends': sane-backends-1.0.20_4 portupgrade with various flags simply does nothing. The entry for sane-backends in INDEX-7 reads sane-backends-1.0.21|/usr/ports/graphics/sane-backends|/usr/local|API for access to scanners, digitals camera, frame grabbers etc|/usr/ports/graphics/sane-backends/pkg-descr|po...@freebsd.org|graphics|gettext-0.17_1 gmake-3.81_3 jbigkit-1.6 jpeg-8_2 libiconv-1.13.1_1 libusb-0.1.12_4 tiff-3.9.2_1|gettext-0.17_1 jbigkit-1.6 jpeg-8_2 libiconv-1.13.1_1 libusb-0.1.12_4 tiff-3.9.2_1|http://www.sane-project.org/||| Sounds like you need a portsdb -uf. I just tried it. Same results. Here's the result of portinstall -f sane-backends-1.0.21 (which I interrupted after it went wrong). [Gathering depends for graphics/sane-backends .. done] --- Installing 'sane-backends-1.0.20_4' from a port (graphics/sane-backends) --- Building '/usr/ports/graphics/sane-backends' === Cleaning for sane-backends-1.0.20_4 === Found saved configuration for sane-backends-1.0.20_4 === Extracting for sane-backends-1.0.20_4 = MD5 Checksum mismatch for sane-backends-1.0.20.tar.gz. = SHA256 Checksum mismatch for sane-backends-1.0.20.tar.gz. === Refetch for 1 more times files: sane-backends-1.0.20.tar.gz sane-backends-1.0.20.tar.gz === Found saved configuration for sane-backends-1.0.20_4 = sane-backends-1.0.20.tar.gz doesn't seem to exist in /usr/ports/distfiles/. = Attempting to fetch from http://alioth.debian.org/frs/download.php/3026/. ^?fetch: transfer interrupted ** Command failed [exit code 2]: /usr/bin/script -qa /tmp/portinstall20100523-79910-1ktytu1-0 env make FETCH_BEFORE_ARGS=-q ** Fix the problem and try again. ** Listing the failed packages (-:ignored / *:skipped / !:failed) ! graphics/sane-backends(checksum mismatch) ___ 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: Porting SANE backend 1.0.21 to FreeBSD 7.2
On Sun, 23 May 2010, Mark Terribile wrote: sane-backends 1.0.21 showed up in ports this morning... I'm sorry to be further trouble, but I've tried portupgrade and pkgdb -FU followed by portupgrade and even though the INDEX-7 file indicates that the sane-backend version is 1.0.21 I keep getting 1.0.20 downloaded. What should I be looking at? portsnap or csup to update the ports tree. Or maybe a different mirror in case the one you're using is outdated. Here's what I use: csup ports-supfile portsdb -Fu(portsdb is from portupgrade[-devel]) and then portversion -vL= to show outdated ports. -Warren Block * Rapid City, South Dakota USA ___ 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: Users and groups kept after a port deinstallation
-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 On Sun, 23 May 2010 02:02, Matthew Seaman wrote: In Message-Id: 4bf8c4f8.9090...@infracaninophile.co.uk On 23/05/2010 04:47:49, jhell wrote: But if a port can install a user there is no reason that it can not uninstall a user via pw(8) that is available from bsd.commands.mk after checking a recorded md5(1) sum that it could create upon installation for the output of pw usershow/groupshow UID/GID. The trick would be to teach the ports how to tell if a port was being deleted for good, when trashing the user would be appropriate, or if the port was being deleted as part of the process of upgrading it, when you'ld want to keep the user. That shouldn't actually be to hard. If a utility like the three main upgrade tools that are being used the most right now would export a variable for say UPGRADING=yes then the uninstall script could check against that to decide whether or not the port is being removed or upgraded and make the proper decision while alerting the admin to whats going on. Regards, - -- jhell -BEGIN PGP SIGNATURE- Version: GnuPG v2.0.14 (FreeBSD) iQEcBAEBAgAGBQJL+VbIAAoJEJBXh4mJ2FR+6d0H/RzxsitENOuEiG1j9l6cucod taGMfoitDYEFe7umLAyx/qfcLVkxRoVKNcStXGdQYFmhgbs0U3LgRfeCroKHcgaG GQkojvJvHMq0bGPXkGyM5Uqk2duN59dJbWyRqlfAxAt1b9SDl6LkHzfi4Bb0CoZ6 6/+izQ5Nl0nDDGGwzou2uCqhJ20YTm9N+XD5pdvDPPdC208wCc+1IPRNlZbx1stM B4viIveIBNJei1ooNqH3qwzO/fdOpJhd09eZNncOGLKPguHNNmqa/UH0ftXIBykU 3edE+gP+bvnf0kYeFBofYJDrG7H6grAyRUoObcD42sROLoD9Wk/RTO/MXZ8ekjA= =6JuP -END PGP SIGNATURE- ___ 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: Users and groups kept after a port deinstallation
Hi-- On May 22, 2010, at 10:59 PM, Matthew Seaman wrote: OpenBSD has a convention that all system user accounts start with a '_' character. There are a few accounts in UIDs that have adopted that, but no great stampede to adopt the idea despite most people agreeing with it. That convention is being adopted by MacOS 10.6, also. It does make it easier for one to separate out processes invoked by a human from automated tasks in ps or top... Regards, -- -Chuck ___ 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: Users and groups kept after a port deinstallation
On 05/23/10 09:24, jhell wrote: That shouldn't actually be to hard. If a utility like the three main upgrade tools that are being used the most right now would export a variable for say UPGRADING=yes then the uninstall script could check against that to decide whether or not the port is being removed or upgraded and make the proper decision while alerting the admin to whats going on. The previous author of portupgrade and I agreed on the following variables to be set in our tools: UPGRADE_TOOL=portmaster UPGRADE_PORT=name of port with version UPGRADE_PORT_VER=`echo $UPGRADE_PORT | sed 's#.*-\(.*\)#\1#'` The last 2 are not set if this is a new install. hth, Doug -- ... and that's just a little bit of history repeating. -- Propellerheads Improve the effectiveness of your Internet presence with a domain name makeover!http://SupersetSolutions.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
Now OK (Re: cvs commit: ports/arabic/libitl Makefile ports/audio/xmms-infopipe Makefile ports/devel/sfslite Makefile ports/misc/compat3x Makefile ports/textproc/lemmatizer Makefile)
audio/xmms-infopipe, which was previously failing is OK after this commit. Thanks for fixing it! A description of the testing process can be found here: http://T32.TecNik93.com/FreeBSD/QA-Tindy/ Thanks for your work on making FreeBSD better, -- QAT - your friendly neighborhood Daemon, preparing a heck of an error trapping system: - HMC and EOI? - Halt, Melt and Catch fire or Execute Operator Immediately. ___ 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: Porting SANE backend 1.0.21 to FreeBSD 7.2
Thanks to help from Warren Block and Lowell Gilbert, I now have the offical
ported version of sane-backends-1.0.21 running. Unfortunately, it's behaving
the same way as before, apparently not properly recognizing the USB device. It
Does anyone have experience using this? Or better yet, some sense of what it
needs from the USB side? A clue on enabling the internal debugging would also
be welcome.
Mark Terribile
=
I have added
product CANON CS8800F0x1901CanoScan 8800F
to /usr/src/sys/dev/usb/usbdevs. I have also added
{{ USB_VENDOR_CANON, USB_PRODUCT_CANON_CS8800F }, 0 },
to /usr/src/sys/dev/usb/uscanner.c
When I run scanimage -L I get
-
device `pixma:04A91901' is a CANON Canoscan 8800F multi-function peripheral
---
When I run scanimage -d pixma:04A9101 I get
scanimage: sane_read: Invalid argument
Which I have traced to a defaulted fill routine in a table.
scanimage --help gives me a message ending with
---
Options specific to device `pixma:04A91901':
Scan mode:
--resolution auto||75|150|300|600|1200|2400|4800dpi [75]
Sets the resolution of the scanned image.
--mode auto|Color|Gray [Color]
Selects the scan mode (e.g., lineart, monochrome, or color).
--source Flatbed|Transparency Unit [Flatbed]
Selects the scan source (such as a document-feeder).
--button-controlled[=(yes|no)] [no]
When enabled, scan process will not start immediately. To proceed,
press SCAN button (for MP150) or COLOR button (for other models).
To cancel, press GRAY button.
Gamma:
--custom-gamma[=(auto|yes|no)] [yes]
Determines whether a builtin or a custom gamma-table should be used.
--gamma-table auto|0..255,...
Gamma-correction table. In color mode this option equally affects the
red, green, and blue channels simultaneously (i.e., it is an intensity
gamma table).
Geometry:
-l auto|0..216.069mm [0]
Top-left x position of scan area.
-t auto|0..297.011mm [0]
Top-left y position of scan area.
-x auto|0..216.069mm [216.069]
Width of scan-area.
-y auto|0..297.011mm [297.011]
Height of scan-area.
Buttons:
--button-update
Update button state
--button-1 int [0]
Button 1
--button-2 int [0]
Button 2
Type ``scanimage --help -d DEVICE'' to get list of all options for DEVICE.
List of available devices:
There is a /dev/usb/uscanner .
I haven't figured out how to turn on the internal debugging system, so my first
question to someone who may have ported an earlier version is how to do that.
My second question is whether I have the USB entries right, and whether I need
to do anything else to make this work.
And finally, I ask for any general wisdom or hints in dealing with SANE and
SANE with USB devices.
___
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 installation
Hello here, I am a new freebsd user and would like to know how to install port from link below: http://www.freebsd.org/cgi/cvsweb.cgi/ports/net-mgmt/nav/ There are not much info on howto for this particular package. Any help or guide would be appreciated. M _ Hotmail: Trusted email with Microsoft’s powerful SPAM protection. https://signup.live.com/signup.aspx?id=60969___ 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 installation
On Sun, May 23, 2010 at 3:25 PM, madal 30 mada...@hotmail.com wrote: Hello here, I am a new freebsd user and would like to know how to install port from link below: http://www.freebsd.org/cgi/cvsweb.cgi/ports/net-mgmt/nav/ There are not much info on howto for this particular package. Any help or guide would be appreciated. Hi, The documentation you're looking for can be found here: http://www.freebsd.org/doc/handbook/ports.html . The port corresponds to net-mgmt/nav in the ports tree on your machine. HTH, -Garrett ___ 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
How to determine the history of a port
Greetings again. A few years ago, I proposed editors/emacs-nox11 and submitted a patch to create it, and thus became listed in the comments at the beginning of the Makefile (but I am not the package maintainer, I believe). Today I got a report that the package does not build; I verified this. I want to help the user, but I have no idea how the change that broke the build was added to the Makefile. How do I find the history so I can find out who added the problematic line and figure out what they actually meant? --Paul Hoffman ___ 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 determine the history of a port
Hello, On Sun, May 23, 2010 at 4:46 PM, Paul Hoffman phoff...@proper.com wrote: Greetings again. A few years ago, I proposed editors/emacs-nox11 and submitted a patch to create it, and thus became listed in the comments at the beginning of the Makefile (but I am not the package maintainer, I believe). Today I got a report that the package does not build; I verified this. I want to help the user, but I have no idea how the change that broke the build was added to the Makefile. How do I find the history so I can find out who added the problematic line and figure out what they actually meant? You can find the CVS history via : - cvsweb at http://www.freebsd.org/cgi/cvsweb.cgi/ports/editors/emacs-nox11/Makefile - freshports at http://www.freshports.org/editors/emacs-nox11/ Regards, Julien ___ 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 determine the history of a port
On Sun, May 23, 2010 at 04:46:46PM -0700, Paul Hoffman wrote: Greetings again. A few years ago, I proposed editors/emacs-nox11 and submitted a patch to create it, and thus became listed in the comments at the beginning of the Makefile (but I am not the package maintainer, I believe). Today I got a report that the package does not build; I verified this. I want to help the user, but I have no idea how the change that broke the build was added to the Makefile. How do I find the history so I can find out who added the problematic line and figure out what they actually meant? --Paul Hoffman cvs -d anon...@anoncvs1.freebsd.org:/home/ncvs rlog ports/editors/emacs-nox11 or http://www.freebsd.org/cgi/cvsweb.cgi/ports/editors/emacs-nox11/ HTH, Yuri ___ 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
gtk, gimp
Hi! After all of updtaes I have a little problem with GIMP: on the image window doesn't show anymore pointer coordinates, units and zoom. It show just Background... I have FreeBSD 8.0 p2, KDE 4.4.3. If I start GIMP from Konsole I got: gimp ** Message: Module '/usr/local/lib/gegl-0.1/ff-load.so' load error: /usr/local/lib/gegl-0.1/ff-load.so: Undefined symbol avcodec_decode_video2 :1: error: unexpected character `\1', expected keyword - e.g. `style' (gimp:70750): Gtk-CRITICAL **: gtk_container_remove: assertion `GTK_IS_TOOLBAR (container) || widget-parent == GTK_WIDGET (container)' failed (gimp:70750): Gtk-WARNING **: Attempting to add a widget with type GtkHBox to a GtkFrame, but as a GtkBin subclass a GtkFrame can only contain one widget at a time; it already contains a widget of type GtkHBox (gimp:70750): Gtk-CRITICAL **: gtk_box_pack: assertion `child-parent == NULL' failed Thanks in advance. Mitja http://starikarp.redbubble.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: How to determine the history of a port
On Sun 23 May 2010 at 17:05:04 PDT Julien Laffaye wrote: Hello, On Sun, May 23, 2010 at 4:46 PM, Paul Hoffman phoff...@proper.com wrote: Greetings again. A few years ago, I proposed editors/emacs-nox11 and submitted a patch to create it, and thus became listed in the comments at the beginning of the Makefile (but I am not the package maintainer, I believe). Today I got a report that the package does not build; I verified this. I want to help the user, but I have no idea how the change that broke the build was added to the Makefile. How do I find the history so I can find out who added the problematic line and figure out what they actually meant? You can find the CVS history via : - cvsweb at http://www.freebsd.org/cgi/cvsweb.cgi/ports/editors/emacs-nox11/Makefile - freshports at http://www.freshports.org/editors/emacs-nox11/ Another thing that is sometimes useful is to query the GNATS database for closed PR's related to the port. For example: http://www.freebsd.org/cgi/query-pr-summary.cgi?category=severity=priority=class=state=sort=nonetext=emacs-nox11responsible=multitext=originator=closedtoo=onrelease= Interestingly, the only thing this turns up for emacs-nox11 is the original PR that created the port -- which means any subsequent changes were probably the result of some comprehensive updates each of which affected several ports in one swoop. Or that the people submitting the PR's didn't follow the accepted practice of including category portname in the subject 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: portmaster cannot find package
On Fri, 21 May 2010, Eitan Adler wrote: Thanks for the suggestion, I'll definitely consider that for the next version. I already have problems with the documentation being long and detailed, whether it is too much of either is sort of in the eye of the beholder. :) Detailed documentation is almost never a problem It is when it becomes so long and/or complex that no one reads it. If you look in the current man page there is a quick start reference that was added because a couple of FreeBSD committers complained that they didn't have time to read the man page thoroughly in order to get started with it quickly. -- Improve the effectiveness of your Internet presence with a domain name makeover!http://SupersetSolutions.com/ Computers are useless. They can only give you answers. -- Pablo Picasso ___ 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: did sudo change the default sense of env_reset option?
On Sat, May 22, 2010 at 08:02:19AM -0400, jhell wrote: Attached is the copy of the sudoers.default take a look through it to see how to set a environment variable for use with portupgrade or portmaster etc... Hmm. I see that that is now the installed default, but of course (by design) the fact that it has changed in this significant way is not automatically reflected in the already-in-use sudoers file. I think that this could usefully have been flagged in UPDATING. I also prefer my fix (reverting the default sense of env_reset): I know that I'm not going to try to subvert any of my root processes by fiddling with LD_PATH or whatever paranoia has produced this change. Sudoers(5) is too complicated as it is, with too many options. Cheers, -- Andrew ___ 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
kdebase4-runtime doesn't pull in libssh if compat7x is installed
Hi,
x11/kdebase4-runtime doesn't in pull security/libssh as dependency if we
have misc/compat7x installed (installs libssh.so.4 as well, in different
location). Detection of security/libssh could be changed to
${LOCALBASE}/include/libssh/libssh.h. Patch attached.
Thanks,
Yuri
Index: Makefile
===
RCS file: /home/ncvs/ports/x11/kdebase4-runtime/Makefile,v
retrieving revision 1.235
diff -u -r1.235 Makefile
--- Makefile21 May 2010 16:22:40 - 1.235
+++ Makefile24 May 2010 02:27:58 -
@@ -8,7 +8,7 @@
PORTNAME= kdebase-runtime
PORTVERSION= ${KDE4_VERSION}
-PORTREVISION= 0
+PORTREVISION= 1
CATEGORIES=x11 kde
MASTER_SITES= ${MASTER_SITE_KDE}
MASTER_SITE_SUBDIR=${KDE4_BRANCH}/${PORTVERSION}/src
@@ -17,10 +17,11 @@
MAINTAINER=k...@freebsd.org
COMMENT= Basic applications for the KDE system
+BUILD_DEPENDS= ${LOCALBASE}/include/libssh/libssh.h
LIB_DEPENDS= xine.1:${PORTSDIR}/multimedia/libxine \
slp.1:${PORTSDIR}/net/openslp \
- attica.0:${PORTSDIR}/x11-toolkits/attica \
- ssh.4:${PORTSDIR}/security/libssh
+ attica.0:${PORTSDIR}/x11-toolkits/attica
+RUN_DEPENDS= ${LOCALBASE}/include/libssh/libssh.h
USE_KDE4= kdelibs kdeprefix kdehier automoc4 #pimlibs
KDE4_BUILDENV= yes
___
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 installation
On May 23, 2010, at 4:22 PM, Indi wrote: On Sun, May 23, 2010 at 03:40:47PM -0700, Garrett Cooper wrote: On Sun, May 23, 2010 at 3:25 PM, madal 30 mada...@hotmail.com wrote: Hello here, I am a new freebsd user and would like to know how to install port from link below: http://www.freebsd.org/cgi/cvsweb.cgi/ports/net-mgmt/nav/ There are not much info on howto for this particular package. Any help or guide would be appreciated. Hi, The documentation you're looking for can be found here: http://www.freebsd.org/doc/handbook/ports.html . The port corresponds to net-mgmt/nav in the ports tree on your machine. Really? That port doesn't exist on my machine... (just portsnapped today) It was removed ages ago (read through the cvs history for the port and you'll figure out why). Thanks, -Garrett___ 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
