Let's talk about subversion/svn
Given the incessant focus on everything using Subversion now (please do not get me started, it will be like arguing with a brick wall), I'd like to know what the plan is for minimising the number of dependencies. The present subversion **package** on the official FTP servers is for subversion-1.7.6: root@icarus:~ # ftp ftp://ftp.freebsd.org/pub/FreeBSD/ports/amd64/packages-9-stable/Latest/ ... ftp> dir subversion*.tbz 229 Entering Extended Passive Mode (|||10279|). 150 Here comes the directory listing. lrwxr-xr-x1 967 10032 Oct 14 14:53 subversion-java.tbz -> ../All/subversion-java-1.7.6.tbz lrwxr-xr-x1 967 10027 Oct 13 13:24 subversion.tbz -> ../All/subversion-1.7.6.tbz lrwxr-xr-x1 967 10028 Oct 14 01:54 subversion16.tbz -> ../All/subversion-1.6.18.tbz 226 Directory send OK. And this is partially what it pulls down dependency-wise: root@icarus:~ # pkg_add -r -n subversion Fetching ftp://ftp.freebsd.org/pub/FreeBSD/ports/amd64/packages-9-stable/Latest/subversion.tbz... Done. Package dependency sqlite3-3.7.14.1 for ftp://ftp.freebsd.org/pub/FreeBSD/ports/amd64/packages-9-stable/Latest/subversion.tbz not found! Package dependency gdbm-1.9.1 for ftp://ftp.freebsd.org/pub/FreeBSD/ports/amd64/packages-9-stable/Latest/subversion.tbz not found! Package dependency db42-4.2.52_5 for ftp://ftp.freebsd.org/pub/FreeBSD/ports/amd64/packages-9-stable/Latest/subversion.tbz not found! Package dependency neon29-0.29.6_4 for ftp://ftp.freebsd.org/pub/FreeBSD/ports/amd64/packages-9-stable/Latest/subversion.tbz not found! I say partially because due to use of -n, some of those packages weren't downloaded, thus the recursive dependency nature is lost (I consider this mostly a bug with -n when used with a remote package, but it could also be deemed a feature). However, GDBM and Oracle/Sleepycat DB aren't (by default) enabled in 1.7.7 which is what's in ports currently: root@icarus:/usr/ports/devel/subversion # make run-depends-list /usr/ports/databases/sqlite3 /usr/ports/devel/apr1 /usr/ports/devel/gettext /usr/ports/textproc/expat2 /usr/ports/www/neon29 So GDBM and Oracle/Sleepycat DB are now disabled by default (good!), but now we have the following (and I will describe each of them for readers so they know what they're for): - SQLite -- which I believe is used for data storage for commits/etc. and tends to work well for that, so I'm okay with it. - gettext -- needed for NLS, which I've learned to accept although I'd rather everything today just use UTF-8 universally (idealistic me). However, there are many people who are heavy WITHOUT_NLS advocates, and I used to be one, so they should be honoured (IMO). - APR -- have yet to figure this out. All I can think of is "svn is an Apache project and we like injecting all our crap into everything, so enjoy!". - expat2 -- XML parsing library, which I also have yet to figure out the need for. What VCS uses XML and why? Is this really *needed*? - neon -- OPTIONS description labels this as "WebDAV/DAV support", but in reality what this provides that's most important is HTTPS/SSL support. I found this out the hard way when building svn for a customer 4-5 months ago. NEON_DESC should really become this: NEON_DESC=WebDAV/Delta-V access module + HTTPS/SSL support I want people reading this to remember olden days, because it seems we've taken a step backwards when it comes to applying minimalistic approaches and KISS principle. I want people to remember the days of this command: pkg_add -r cvsup-without-gui And how it had a dependency on ezm3 (Modula-3 language), which its author insisted was needed "because cvsup's design needed M3 for speed" (I'd have to dig up his exact words). This utter nonsense was debunked when csup -- written purely in C -- was introduced into the base system. I remember that day, and it was one of the happiest moments I had using FreeBSD. Yes really. All of my co-workers at the time who used FreeBSD rejoiced as well. I understand everyone uses svn differently, but there *needs* to be a package (or stub port) that is minimal, i.e. "install this to use svn on FreeBSD if you want to check out src and ports and other stuff"[1], that has absolutely no fluff in it other than what's needed, and I am not sure if the above defaults meet that requirement (thus possibly a stub-port would be good). Possibly that can be accomplished by someone updating the existing subversion.tbz package on the servers to 1.7.7? Not sure. I also know FREEBSD_TEMPLATE is absolutely needed (failure to include that will result in weird breakage, which I've seen posts complaining about on the lists in the past). There is STATIC, which would be great for solving this (if you ask me), but if I remember right the port maintainer stated sometime in the past that he had concerns over this option given "security implications", e.g. if SQLite, etc. had security holes in them and thu
FreeBSD Port: istgt-20121028
Hello, I am using your istgt port at my FreeBSD box. I've problem with creating targets for VirtualBox VDI disk images. My config for VDI image: [LogicalUnit2] TargetName "esxi-base.vdi" Mapping PortalGroup1 InitiatorGroup1 AuthMethod Auto UseDigest Auto ReadOnly Yes UnitType Disk UnitInquiry "FreeBSD" "iSCSI Disk" "0123" "00e0816537d52" UnitOnline yes BlockLength 512 QueueDepth 32 LUN0 Storage /iSCSI/esxi-base.vdi auto LUN0 Option Serial 00e0816537d52 And after trying to reload the istgt service: Nov 19 00:02:09 volt istgt[9957]: istgt version 0.5 (20121028) Nov 19 00:02:09 volt istgt[9957]: normal mode Nov 19 00:02:09 volt istgt[9957]: using kqueue Nov 19 00:02:09 volt istgt[9957]: using host atomic Nov 19 00:02:46 volt istgt[9958]: reload configuration #1 Nov 19 00:02:46 volt istgt[9958]: istgt_lu_disk.c: 578:istgt_lu_disk_init: ***ERROR*** LU2: LUN0: lu_disk_vbox_lun_init() failed Nov 19 00:02:46 volt istgt[9958]: istgt_lu.c:2091:istgt_lu_init_unit: ***ERROR*** LU2: lu_disk_init() failed Nov 19 00:02:46 volt istgt[9958]: istgt_lu.c:2345:istgt_lu_reload_update: ***ERROR*** LU2: lu_init_unit() failed % file /iSCSI/esxi-base.vdi /iSCSI/esxi-base.vdi: VirtualBox Disk Image, major 1, minor 1 % chmod of file is set to 644 I am using VirtualBox 4.2.4 under FreeBSD 9.1-PRERELEASE amd64. Could you provide me some help / hints how to enable VDI disk images to work as iSCSI targets? Regards, -- Marek Salwerowicz ___ 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: ${name}_fib fix in rc.d script (ports/173366)
Hiroki Sato wrote in <20121118.031240.1840537590824524280@allbsd.org>: hr> Hello, hr> hr> I will commit the attached patch for the following today to fix a hr> breakage of the rc.d script after ${name}_fib is introduced into hr> rc.subr: hr> hr> net/sslh hr> www/apache22 hr> www/cblog hr> www/fcgiwrap hr> www/shellinabox hr> www/squid hr> www/squid31 hr> www/squid32 hr> net/sslh hr> hr> The change should be compatible with both of the older releases and hr> head. If this commit is not convenient for you or there is something hr> wrong with it, please let me know as soon as possible. Thank you. I committed the patch just now. If you notice there is something wrong with it, please let me know. Thank you. -- Hiroki pgpc0G0nWseDJ.pgp Description: PGP signature
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 +-+ cad/varkon | 1.19D | 1.19E +-+ devel/allegro | 4.2.2 | 5.0.8 +-+ textproc/pear-Text_Template | 1.1.2 | 1.1.3 +-+ 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 If wish to stop receiving portscout reminders, please contact portsc...@portscout.freebsd.org 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: portsnap fetch
On Sunday 18 November 2012 05:35:30 ajtiM wrote: > Hi! > > I am using FreeBSD 9.1 RC-3. All the time I use portsnap. Today I ran > portsnap fetch && portsnap extract > and it stopped extract on > /usr/ports/multimedia/mplayer2/ > files/aa53f85d11a3fd077801a5d63b76022647420c8c480f9022315806e911aa33dd.gz > not found -- snapshot corrupt. > > All /usr/ports after /mail are empty and the last is "mplayer" in > /multimedia. > > Is it results of maintaining or is something else. > > Thanks in advance. > > Mitja > > http://www.redbubble.com/people/lumiwa I did as was suggested: rm /var/db/portsnap/* rm -rf /usr/ports and portsnap fetch && portsnap extract works :). Thank you. Mitja http://www.redbubble.com/people/lumiwa ___ 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: portsnap fetch
On Sun, 18 Nov 2012 05:35:30 -0600 ajtiM wrote: > Hi! > > I am using FreeBSD 9.1 RC-3. All the time I use portsnap. Today I ran > portsnap fetch && portsnap extract > and it stopped extract on > /usr/ports/multimedia/mplayer2/ > files/aa53f85d11a3fd077801a5d63b76022647420c8c480f9022315806e911aa33dd.gz > not found -- snapshot corrupt. > > All /usr/ports after /mail are empty and the last is "mplayer" > in /multimedia. > > Is it results of maintaining or is something else. > > Thanks in advance. > > Mitja Start with a fresh ports tree portsnap fetch && portsnap extract (I also did this beforehand, mostly out of paranoia: rm /var/db/portsnap/* rm -rf /usr/ports ) See here for details why: http://www.freebsd.org/news/2012-compromise.html > > http://www.redbubble.com/people/lumiwa > ___ > 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" -- Michael Gmelin ___ 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"
portsnap fetch
Hi! I am using FreeBSD 9.1 RC-3. All the time I use portsnap. Today I ran portsnap fetch && portsnap extract and it stopped extract on /usr/ports/multimedia/mplayer2/ files/aa53f85d11a3fd077801a5d63b76022647420c8c480f9022315806e911aa33dd.gz not found -- snapshot corrupt. All /usr/ports after /mail are empty and the last is "mplayer" in /multimedia. Is it results of maintaining or is something else. Thanks in advance. Mitja http://www.redbubble.com/people/lumiwa ___ 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: xmlcatmgr gives error for: iso8879, docbook-sk, xmlcharent
[SOLVED] It seems this is caused by a corrupt catalog structure. I solved this by: 1. Deinstall textproc/xmlcatmgr 2. Delete everything /usr/local/share/sgml and /usr/local/share/xml 3. Reinstall textproc/xmlcatmgr 4 rebuild every dependent port (portmaster -r textproc/xmlcatmgr) -- View this message in context: http://freebsd.1045724.n5.nabble.com/xmlcatmgr-gives-error-for-iso8879-docbook-sk-xmlcharent-tp5759961p5761960.html Sent from the freebsd-ports mailing list archive at Nabble.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"