Re: FreeBSD Port: mplayer-0.99.11_14
On Wednesday 22 July 2009 14:40:50 Thomas Zander wrote: > On Wed, Jul 22, 2009 at 22:33, Michael D. > > Stackhouse wrote: > > I think we'll investigate VLC as an alternative. Not too comfortable > > building around a solution that's not being maintained as it should be. > > mplayer is definitely continuously developed, it's not an abandoned > project! They just do not follow a release scheme at the moment. I don't consider sticking code into a repository "developing". Release engineering is an important part of the development process and shifting this burden onto packagers, while stuffing more and more non-portable code into the repository is exactly why it's hard to find volunteers with the time and knowledge to maintain an up-to-date mplayer port. -- Mel ___ 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: FreeBSD Port: mplayer-0.99.11_14
Thomas Zander wrote: >Stackhouse wrote: >> I think we'll investigate VLC as an alternative. Not too comfortable >> building around a solution that's not being maintained as it should be. > mplayer is definitely continuously developed, it's not an abandoned > project! They just do not follow a release scheme at the moment. He may have been referring to the FreeBSD port here, not upstream. ;) > If the svn version does the job you want it to do, it's definitely worth a > try. > I personally like mplayer as it is still lighter than VLC. I was going to submit a snapshot update some months ago to Riggs, but I got bogged down (sorry, Riggs!) with sound problems on my computer, and other demands on my time. By the time that I returned to it, upstream developers who were using Linux had introduced several additional hurdles by using SSE3 and several C99 math functions that were missing from our gcc 4.2 base compiler toolchain and our aging and largely unmaintained math library. Since then, after complaints from users on the mplayer mailing list who were attempting to build snapshots on FreeBSD, they resolved some but not all of these problems by just disabling some of the newer code, which is ... not altogether satisfactory. Also, there was, the last time I checked, some kind of problem with our base compiler on amd64. Suggested workarounds for some of these problems were submitted by "Tomek" on March 2 to the freebsd-multimedia mailing list (under messages entitled "x264 patch" and "ffmpeg patch", but there are still some problems to resolve. So this will probably require a little time and effort to update. If no one else does it, I'll try to get to it in the next few weeks. It definitely ought to be done. b. ___ 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: current Samba ports?
The port for 3.2 is net/samba32, the one for 3.3 is net/samba33, and there's even a net/samba4-devel one. -Boris Raymond Vetter wrote: Hello FreeBSD Team, FreeBSD Ports provide only Samba 3.0.x. It is possible to port Samba 3.2.x, 3.3.x for the current FreeBSD? The 3.0.x is quit old. thanks Raymond ___ freebsd-ports@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-ports To unsubscribe, send any mail to "freebsd-ports-unsubscr...@freebsd.org" ___ freebsd-ports@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-ports To unsubscribe, send any mail to "freebsd-ports-unsubscr...@freebsd.org"
current Samba ports?
Hello FreeBSD Team, FreeBSD Ports provide only Samba 3.0.x. It is possible to port Samba 3.2.x, 3.3.x for the current FreeBSD? The 3.0.x is quit old. thanks Raymond ___ 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: Typo in screen's manpage
In message <86bpna8xzv@gmail.com>, Anonymous writes: > Reinout Stevens writes: > > > Hi, > > > > Today I spotted a typo in screen's manpage: it's useful instead of > > usefull. I've made a small diff in case that's necessary. I also filed > > a "bug" in the screen dev's bugtracker. > > > > I'll disappoint you. It was fixed long ago. > > http://git.savannah.gnu.org/cgit/screen.git/commit/?id=b12a744ebdda8edf6bc79d > a6242b6d1240d86c10 > > In case you're interested in -devel like port I keep git-master-pulled > port in here: > ftp://ftp.lissyara.su/users/Guest/screen.diff > > You can use it without distfile by generating one yourself. > For that you need autotools and git. Then you can type smth like > > $ make maint-gen-distfile && make makesum && make install clean > > Perhaps, you can test it. > > > > > Regards, > > > > > > Reinout [...] Sorry for the late reply. I'm out of town this weekend and my Internet access is limited at the moment. I'll check out the -devel port next week. -- Cheers, Cy Schubert FreeBSD UNIX: Web: http://www.FreeBSD.org e**(i*pi)+1=0 ___ 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"
portlint: incorrect Makefile analysis
Hi Folks! I've encountered an issue with the portlint tool and do not find a better place to file it. Description: For the set of new boost-ports, I'm using included Makefiles to remove duplication. Portlint complains on variables contained in included Makefiles. For example, it prints: FATAL: Makefile: no MAINTAINER listed. While "make -V MAINTAINER" works properly. My ports are not checked in yet, if you need the source it's at http://alexanderchuranov.com/boost-port/boost-ports-200907241320.tar.bz2 If I edit the master Makefile (which includes others) for a port and add a MAINTAINER variable with the value "somebody", then portlint do not fails with the same. However, it examines the content of the variable listed in the master Makefile. It is incorrect, because according to the rules of make, the variable has the last assigned value. The assignment is done in the included Makefile. Output of portlint if master Makefile also contains assignment to the "MAINTAINER" variable: OK: seen MAINTAINER, in order. OK: MAINTAINER section is ordered properly. FATAL: Makefile: MAINTAINER address, somebody, does not appear to be a valid email address. Sincerely, Alexander Churanov ___ 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: status of FreeBSD ports you maintain as of 20090705
On Fri, Jul 24, 2009 at 04:52:00PM +0200, Martin Tournoij wrote: > On Fri, 24 Jul 2009 12:00:13 +0200, Alex Dupre wrote: > > Martin Tournoij ha scritto: > >> Really, I have better things to do, I would have liked to do this in a > >> nicer way, but I've been waiting for more than a week to revert the > >> maintainer switch > > > > Do you mean you never approved the switch, as stated in the commit log? > > > > Change maintainer to scjamo...@bsd.com.br > > > > Submitted by: scjamo...@bsd.com.br (to ports@) > > Approved by:carpetsmo...@rwxrwxrwx.net (maintainer) > > Not explicitly, and in my original post I said ``will resign the > maintainership of all my ports in the **coming weeks**, (For a few ports > I have a few changes/ updates **in the pipeline I would like to > finish**).'' > > Misunderstandings happen, and that's ok. I explained reassigning > maintainership immediately was not my intention and asked to revert the > changes, no word ever since ... Which is not so ok IMO... And this is why I think we should have a policy of not changing maintainer of things based upon mailing list traffic. I know I'm guilty of doing it in the past but I have come to the conclusion that it can cause these kinds of problems and set a precedent of people expecting mailing list traffic to result in commits. We should have an official record of who requested changes in the PR database and not give the community the idea that mailing list traffic asking for a commit to happen is the right way to do things. -- WXS ___ 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: status of FreeBSD ports you maintain as of 20090705
On Fri, 24 Jul 2009 12:00:13 +0200, Alex Dupre wrote: > Martin Tournoij ha scritto: >> Really, I have better things to do, I would have liked to do this in a >> nicer way, but I've been waiting for more than a week to revert the >> maintainer switch > > Do you mean you never approved the switch, as stated in the commit log? > > Change maintainer to scjamo...@bsd.com.br > > Submitted by: scjamo...@bsd.com.br (to ports@) > Approved by: carpetsmo...@rwxrwxrwx.net (maintainer) Not explicitly, and in my original post I said ``will resign the maintainership of all my ports in the **coming weeks**, (For a few ports I have a few changes/ updates **in the pipeline I would like to finish**).'' Misunderstandings happen, and that's ok. I explained reassigning maintainership immediately was not my intention and asked to revert the changes, no word ever since ... Which is not so ok IMO... ___ 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: misc/e2fsprogs-libuuid should be MAKE_JOBS_UNSAFE
on 21/07/2009 18:20 Dmitry Marakasov said the following: > > A fix for this was recently added. Does the updated port show the > same bahavior? Matthias, Dmitry, thank you very much for the responses (off- and on- list)! And sorry for the delay. Yes, the updated port works perfectly. -- Andriy Gapon ___ 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: status of FreeBSD ports you maintain as of 20090705
Martin Tournoij ha scritto: > Really, I have better things to do, I would have liked to do this in a > nicer way, but I've been waiting for more than a week to revert the > maintainer switch Do you mean you never approved the switch, as stated in the commit log? Change maintainer to scjamo...@bsd.com.br Submitted by: scjamo...@bsd.com.br (to ports@) Approved by:carpetsmo...@rwxrwxrwx.net (maintainer) -- Alex Dupre ___ 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: request for commit approval to change my email address
On Fri, Jul 24, 2009 at 12:21:15PM +0200, Nick Barkas wrote: > Hello Hi Nick, > I'm a src but not ports committer and I'd like to change the email > address on ports I maintain to my FreeBSD address. Can a ports committer > check the attached patch and let me know if committing it would be all > right? The ports in question: Looks good, please go ahead. Thanks -erwin -- Erwin Lansing http://droso.org Prediction is very difficult especially about the futureer...@freebsd.org pgpbw9qIiRjUx.pgp Description: PGP signature
request for commit approval to change my email address
Hello
I'm a src but not ports committer and I'd like to change the email
address on ports I maintain to my FreeBSD address. Can a ports committer
check the attached patch and let me know if committing it would be all
right? The ports in question:
net/splatd
security/openvpn-auth-ldap
security/osslsigncode
sysutils/apt
sysutils/farbot
sysutils/ipmi-kmod
Thanks much!
Nick
Index: net/splatd/Makefile
===
RCS file: /home/pcvs/ports/net/splatd/Makefile,v
retrieving revision 1.9
diff -u -r1.9 Makefile
--- net/splatd/Makefile 5 Jan 2009 19:04:30 - 1.9
+++ net/splatd/Makefile 24 Jul 2009 10:03:46 -
@@ -10,7 +10,7 @@
CATEGORIES= net
MASTER_SITES= ${MASTER_SITE_GOOGLE_CODE}
-MAINTAINER= s...@threerings.net
+MAINTAINER= s...@freebsd.org
COMMENT= Splat is the Scalable Periodic LDAP Attribute Transmogrifier
BUILD_DEPENDS= ${LOCALBASE}/bin/zconfig:${PORTSDIR}/devel/py-zconfig \
Index: security/openvpn-auth-ldap/Makefile
===
RCS file: /home/pcvs/ports/security/openvpn-auth-ldap/Makefile,v
retrieving revision 1.5
diff -u -r1.5 Makefile
--- security/openvpn-auth-ldap/Makefile 5 Jan 2009 19:04:33 - 1.5
+++ security/openvpn-auth-ldap/Makefile 24 Jul 2009 10:03:46 -
@@ -11,7 +11,7 @@
MASTER_SITES= http://dpw.threerings.net/projects/openvpn-auth-ldap/
DISTNAME= auth-ldap-${PORTVERSION}
-MAINTAINER= s...@threerings.net
+MAINTAINER= s...@freebsd.org
COMMENT= LDAP authentication plugin for OpenVPN
BUILD_DEPENDS= re2c:${PORTSDIR}/devel/re2c \
Index: security/osslsigncode/Makefile
===
RCS file: /home/pcvs/ports/security/osslsigncode/Makefile,v
retrieving revision 1.4
diff -u -r1.4 Makefile
--- security/osslsigncode/Makefile 23 Jan 2009 15:43:08 - 1.4
+++ security/osslsigncode/Makefile 24 Jul 2009 10:03:46 -
@@ -11,7 +11,7 @@
CATEGORIES= security devel
MASTER_SITES= SF
-MAINTAINER= s...@threerings.net
+MAINTAINER= s...@freebsd.org
COMMENT= OpenSSL-based signcode utility
PLIST_FILES= bin/osslsigncode
Index: sysutils/apt/Makefile
===
RCS file: /home/pcvs/ports/sysutils/apt/Makefile,v
retrieving revision 1.7
diff -u -r1.7 Makefile
--- sysutils/apt/Makefile 23 Jan 2009 15:43:09 - 1.7
+++ sysutils/apt/Makefile 24 Jul 2009 10:03:46 -
@@ -11,7 +11,7 @@
MASTER_SITES= ${MASTER_SITE_DEBIAN_POOL}
DISTNAME= apt_0.6.46.4-0.1
-MAINTAINER= s...@threerings.net
+MAINTAINER= s...@freebsd.org
COMMENT= Advanced front-end for dpkg
BUILD_DEPENDS= bash:${PORTSDIR}/shells/bash \
Index: sysutils/farbot/Makefile
===
RCS file: /home/pcvs/ports/sysutils/farbot/Makefile,v
retrieving revision 1.5
diff -u -r1.5 Makefile
--- sysutils/farbot/Makefile 6 Dec 2008 21:39:05 - 1.5
+++ sysutils/farbot/Makefile 24 Jul 2009 10:03:46 -
@@ -11,7 +11,7 @@
MASTER_SITES= http://dpw.threerings.net/projects/farbot/
DISTNAME= farbot-1.0-beta2
-MAINTAINER= s...@threerings.net
+MAINTAINER= s...@freebsd.org
COMMENT= FreeBSD Automated Release Bot
BUILD_DEPENDS= ${LOCALBASE}/bin/zconfig:${PORTSDIR}/devel/py-zconfig
Index: sysutils/ipmi-kmod/Makefile
===
RCS file: /home/pcvs/ports/sysutils/ipmi-kmod/Makefile,v
retrieving revision 1.13
diff -u -r1.13 Makefile
--- sysutils/ipmi-kmod/Makefile 6 Jan 2009 17:59:28 - 1.13
+++ sysutils/ipmi-kmod/Makefile 24 Jul 2009 10:03:47 -
@@ -11,7 +11,7 @@
CATEGORIES= sysutils kld
MASTER_SITES= http://dpw.threerings.net/projects/ipmi-kmod/
-MAINTAINER= s...@threerings.net
+MAINTAINER= s...@freebsd.org
COMMENT= Backport of ipmi driver from FreeBSD 7-CURRENT for FreeBSD 5.3 - 6.1
SUB_FILES= pkg-install pkg-deinstall
___
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: Unable to build /x11/kdelibs3 with updated jpeg-7 port
On Thursday 23 July 2009 22:14:39 Milan Obuch wrote: > On Thursday 23 July 2009 23:58:03 Mel Flynn wrote: > > On Tuesday 21 July 2009 02:59:29 Milan Obuch wrote: > > > On Tuesday 21 July 2009 12:40:34 Jerry wrote: > > > > It appears that the /x11/kdelibs3 ports insists on using the older > > > > "libjpeg.so.9" library. Since updating to jpeg-7, this library is > > > > no-longer available. Therefore, I cannot build this port. > > > > > > > > A complete copy of the build log is available here: > > > > > > > > http://filebin.ca/yrdvkw/kdelibs.log > > > > > > There is notice in UPDATING, section 20090719, > > > > > > I found temporary workaround > > > > > > ln -s /usr/local/lib/libjpeg.so.10 /usr/local/lib/libjpeg.so.9 > > > > I don't know why people keep advising this, it only makes future upgrades > > harder. > > Please read again: it is temporary workaround. At least for me. It makes my > installed ports working *immediately* with small possibility something will > not work at all due some ABI chabge or somesuch. Because experience shows, people reading solutions from google skip the temporary part. > Rebuilding some KDE ports > took me couple of days (finding the way, compile etc). > > The difference - works immediately vs. a week or so without working kde is > immense. > > > The solution is also very simple to determine: > > % ldd -a /usr/local/lib/libkdefx.so.6|egrep '(^/|jpeg.so)' > > How did you determine this is exactly the lib to look into? Just > wondering... Cause I actually took the time to read the above mentioned build log. > > /usr/local/lib/libkdefx.so.6: > > libjpeg.so.10 => /usr/local/lib/libjpeg.so.10 (0x28b31000) > > /usr/local/lib/libqt-mt.so.3: > > libjpeg.so.10 => /usr/local/lib/libjpeg.so.10 (0x28b31000) > > /usr/local/lib/libpng.so.5: > > /lib/libz.so.5: > > /usr/local/lib/libXext.so.6: > > /usr/local/lib/libX11.so.6: > > /usr/local/lib/libSM.so.6: > > /usr/local/lib/libICE.so.6: > > /usr/local/lib/libXrender.so.1: > > /usr/local/lib/libjpeg.so.10: > > /usr/lib/libstdc++.so.6: > > /lib/libm.so.5: > > /lib/libgcc_s.so.1: > > /usr/local/lib/libaudio.so.2: > > /usr/local/lib/libXt.so.6: > > /usr/local/lib/libmng.so.1: > > libjpeg.so.10 => /usr/local/lib/libjpeg.so.10 (0x28b31000) > > > > From this you can tell that you need to rebuild libqt-mt.so.3 and > > libmng.so.1. One more step: > > % egrep -l '(libqt-mt.so.3|libmng.so.1)' /var/db/pkg/*/+CONTENTS | xargs > > grep -h '@comment ORIGIN:' > > @comment ORIGIN:graphics/libmng > > @comment ORIGIN:x11-toolkits/qt33 > > > > And those are the ports to rebuild for kdelibs3 to be able to build. > > After my symlink trick, portmaster rebuilt everything necessary, so aj > could remove the symlink afterwards. So I think it was kind of hackish > solution, but made my fixing *much* easier and, more important, less > stressfull. That's it. Maybe not nice, but really effective. And if you'd actually run portmaster -rf graphics/jpeg to begin with, you wouldn't have seen the problem, as qt33 and libmng would have been relinked before you started on kdelibs3, though we should probably blame that on the questionable UPDATING entry about 'www/jpeg'. -- Mel ___ 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"
