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 +-+ graphics/qiv| 2.2.4 | 2.3.1 +-+ math/asir2000 | 20110810| 20131219 +-+ 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 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
vlc 2.1.2,4
Hi! I don't know what is different but previous update of 2.1.1,4 which I had problem to built (QT4 plugin) to version 2.1.1_1,4 works and version 2.1.1_2,4 works too but todays update doesn't works again: GEN ../modules/plugins.dat gmake[4]: *** [../modules/plugins.dat] Segmentation fault (core dumped) gmake[4]: Leaving directory `/usr/ports/multimedia/vlc/work/vlc-2.1.2/bin' gmake[3]: *** [all-recursive] Error 1 gmake[3]: Leaving directory `/usr/ports/multimedia/vlc/work/vlc-2.1.2' gmake[2]: *** [all] Error 2 gmake[2]: Leaving directory `/usr/ports/multimedia/vlc/work/vlc-2.1.2' === Compilation failed unexpectedly. Try to set MAKE_JOBS_UNSAFE=yes and rebuild before reporting the failure to the maintainer. *** Error code 1 Stop. make[1]: stopped in /usr/ports/multimedia/vlc *** Error code 1 I don't know what is going wrong...it works...it doesn't. -- 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: If ports@ list continues to be used as substitute for GNATS, I'm unsubscribing
Date: Thu, 19 Dec 2013 11:13:43 -0700 From: Chad Perrin c...@apotheon.net To: freebsd-ports@freebsd.org Subject: Re: If ports@ list continues to be used as substitute for GNATS, I'm unsubscribing On Thu, Dec 19, 2013 at 01:44:57AM -0800, Anton Shterenlikht wrote: From: Thomas Mueller There are many messages on this thread, and I don't know which or what to quote, but I agree on send-pr being user-unfriendly. I disagree. I use only send-pr to send PRs. I use sendmail. I disagree with you. For new users, send-pr is a fucking usability train wreck, and insufficiently well documented. Let's agree to disagree. A slightly different point: I was a new user not so long ago. The major issue for me was whether to send a report at all. Most times I'd be thinking that I fucked up myself (and in many cases I did). In that case my first action would be to ask in questions@, usually after several days of trying to figure out what I have done wrong. Only after being advised in questions@ that it might be a real issue and that I should submit a PR for it, would I do it. In other words, as a new user I thought of sending a PR as a last resort, because I doubted myself a lot more than the stability of FreeBSD and the expertise of the team. The actual tools to submit a PR were never an obstacle. Anton ___ 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: If ports@ list continues to be used as substitute for GNATS, I'm unsubscribing
On Wed, 2013-12-18 at 12:45 -0500, Eitan Adler wrote: On Wed, Dec 18, 2013 at 11:20 AM, Lars Engels lars.eng...@0x20.net wrote: Am 2013-12-17 23:33, schrieb John Marino: Over the months I've seen several ports users copy a failure log and mail it to ports@, usually without even saying hello. I've tried to discourage that behavior but other members of this mail list encourage this method of bypassing writing PRs. One user even proudly boasted that sending email to ports@ is faster than writing a PR so of course he was going to do that instead. That only shows how badly GNATS sucks and that it's much more uncomfortable to use than writing a mail. I totally agree that error need to be tracked in an error tracker where reports don't get lost, you have a proper history etc. pp. but GNATS is just ancient and should have died in a fire a long time ago. Agreed. There is active work on moving to bugzilla instead of GNATS. I can't give a definite timeline but it should be 'soon'. I would suggest to take a look at redmine. Not because I'm a ruby developer. Pivotal and redmine are trackers which people like most. Redmine does the same thing as a jira or a track but in more polite manner :) ___ 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: If ports@ list continues to be used as substitute for GNATS, I'm unsubscribing
On Thu, Dec 19, 2013 at 01:44:57AM -0800, Anton Shterenlikht wrote: From: Thomas Mueller There are many messages on this thread, and I don't know which or what to quote, but I agree on send-pr being user-unfriendly. I disagree. I use only send-pr to send PRs. I use sendmail. I disagree with you. For new users, send-pr is a fucking usability train wreck, and insufficiently well documented. Sendmail is legendary for its obtuse configuration. I suppose you should be proud of the fact you find these tools easy to use, but that does not mean you should dismiss others' concerns over how difficult some people find them. The fact many people find these tools very difficult to use is in fact kind of a big problem, and I'm glad something is being done about it with regard to the bugzilla system. I wouldn't have chosen bugzilla if it was up to me, but it's not up to me and it's sure to be a huge improvement over the system currently in place, so I'm grateful for the work being done. Hopefully the command line send-pr tool will also be replaced with something that actually provides a low-friction way for people with problem reports to contribute to the FreeBSD project. In conclusion, I agree with Thomas (though I much prefer fdm over mpop, personally), and believe that send-pr (or its replacement, whenever that happens) desperately needs some better documentation. I rather suspect that a lot of people with problems to report simply give up and leave us with no clue there's anything wrong. -- Chad Perrin [ original content licensed OWL: http://owl.apotheon.org ] I think train wreck applies more to sendmail than send-pr. Sendmail dates back to long-ago pre-Internet days where computer users didn't send email to other computer users. Now a computer user needs to be able to send through ISP's SMTP server. I see in FreeBSD 10-prerelease, certificates in /etc/mail, suspect that might be related to sendmail, but looks useful even to a sendmail nonuser. Otherwise I'd put WITHOUT_SENDMAIL=yes in /etc/src.conf . There needs to be documentation on how to use send-pr for sending through ISP's SMTP server, and computer's hostname should not have to match email address. Nowadays, computer users may have multiple email accounts. When I had OS/2 Warp 4, I sent mail by sendmail -t outgoing-message-with-all-headers but figuring what to add to sendmail.cf took many hours. Tom ___ 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: If ports@ list continues to be used as substitute for GNATS, I'm unsubscribing
On Thu, 2013-12-19 at 11:13 -0700, Chad Perrin wrote: On Thu, Dec 19, 2013 at 01:44:57AM -0800, Anton Shterenlikht wrote: From: Thomas Mueller There are many messages on this thread, and I don't know which or what to quote, but I agree on send-pr being user-unfriendly. I disagree. I use only send-pr to send PRs. I use sendmail. I disagree with you. For new users, send-pr is a fucking usability train wreck, and insufficiently well documented. Sendmail is legendary for its obtuse configuration. I suppose you should be proud of the fact you find these tools easy to use, but that does not mean you should dismiss others' concerns over how difficult some people find them. The fact many people find these tools very difficult to use is in fact kind of a big problem, and I'm glad something is being done about it with regard to the bugzilla system. I wouldn't have chosen bugzilla if it was up to me, but it's not up to me and it's sure to be a huge improvement over the system currently in place, so I'm grateful for the work being done. Hopefully the command line send-pr tool will also be replaced with something that actually provides a low-friction way for people with problem reports to contribute to the FreeBSD project. In conclusion, I agree with Thomas (though I much prefer fdm over mpop, personally), and believe that send-pr (or its replacement, whenever that happens) desperately needs some better documentation. I rather suspect that a lot of people with problems to report simply give up and leave us with no clue there's anything wrong. +1 People wouldn't read the «Porters Handbook» because they want to make a bug report. Category and Class are far away from obvious. Handbook said that the FreeBSD consists from src, ports, and docs. The send-pr Category dropbox contains ports, bin, java, ia64, etc. It's insane to put everything here. ___ 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: If ports@ list continues to be used as substitute for GNATS, I'm unsubscribing
Subject: Re: If ports@ list continues to be used as substitute for GNATS, I'm unsubscribing From: clutton clut...@zoho.com To: freebsd-ports@freebsd.org On Thu, Dec 19, 2013 at 01:44:57AM -0800, Anton Shterenlikht wrote: From: Thomas Mueller There are many messages on this thread, and I don't know which or what to quote, but I agree on send-pr being user-unfriendly. I disagree. I use only send-pr to send PRs. I use sendmail. I disagree with you. For new users, send-pr is a fucking usability train wreck, and insufficiently well documented. Sendmail is legendary for its obtuse configuration. I suppose you should be proud of the fact you find these tools easy to use, but that does not mean you should dismiss others' concerns over how difficult some people find them. The fact many people find these tools very difficult to use is in fact kind of a big problem, and I'm glad something is being done about it with regard to the bugzilla system. I wouldn't have chosen bugzilla if it was up to me, but it's not up to me and it's sure to be a huge improvement over the system currently in place, so I'm grateful for the work being done. Hopefully the command line send-pr tool will also be replaced with something that actually provides a low-friction way for people with problem reports to contribute to the FreeBSD project. In conclusion, I agree with Thomas (though I much prefer fdm over mpop, personally), and believe that send-pr (or its replacement, whenever that happens) desperately needs some better documentation. I rather suspect that a lot of people with problems to report simply give up and leave us with no clue there's anything wrong. +1 People wouldn't read the «Porters Handbook» because they want to make a bug report. Category and Class are far away from obvious. Handbook said that the FreeBSD consists from src, ports, and docs. The send-pr Category dropbox contains ports, bin, java, ia64, etc. It's insane to put everything here. This is a minor issue. You could probably also remove severity and priority, and let committers reclassify as they see fit. Most bug report systems I used - GCC, kde, paraview, qt - present report submission forms which are too detailed, in my users' opinion. Sure these extra fields might help those dealing with the problem, who are ultimately the people designing these systems. Anyway, all this is trivia. The major issues are - not enough people dealing with PRs and PRs taking too long to be addressed. Anton ___ 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: If ports@ list continues to be used as substitute for GNATS, I'm unsubscribing
On 20/12/2013 10:32 PM, Anton Shterenlikht wrote: In other words, as a new user I thought of sending a PR as a last resort, because I doubted myself a lot more than the stability of FreeBSD and the expertise of the team. The actual tools to submit a PR were never an obstacle. This. If you don't *get* what Anton just said, read it again until you do. I don't know about the rest of you, but I am that user too. A @FreeBSD.org email, commit bit and still a new user that doubts myself sometimes and looks to the team for the right thing to do. If not for the encouragement of those in the project who grok what motivates and demotivates people, I wouldn't be doing what I do today. This thread is a real shame, mired in technical minutia as if that's what really matters. I am here to enable and be a steward for users like Anton, and your contributions are valued. So thank you for sharing. -- koobs. ___ 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: If ports@ list continues to be used as substitute for GNATS, I'm unsubscribing
On 12/20/2013 14:17, Kubilay Kocak wrote: I don't know about the rest of you, but I am that user too. A @FreeBSD.org email, commit bit and still a new user that doubts myself sometimes and looks to the team for the right thing to do. If not for the encouragement of those in the project who grok what motivates and demotivates people, I wouldn't be doing what I do today. This thread is a real shame, mired in technical minutia as if that's what really matters. I am here to enable and be a steward for users like Anton, and your contributions are valued. So thank you for sharing. This sentiment described above is fine, but the thread was never focused on cases like this. The very narrow focus is on when the user is saavy enough to recognize that the problem is not him, and that the problem deserves a report. Rather than submit a PR however, the user just sends it to ports@. That is not the case you are talking about -- in your scenario, the user is going to provide context and express his confusion or doubt. That is a far cry from sending exclusively a build log. So the real shame is that topic is getting expanding to include all user interaction which was never the intent. btw, accepting PRs at ports@ because we the maintainers are not processing GNATS PRs better is treating the symptom of a bigger issue. Yes, GNATS is antiquated, and letting the user specified the classification is beyond boneheaded (as is never fixing that issue). However, a lot of the PR processing issues is centered on inadequate policies and frankly a coddling of delinquent maintainers (I'd like to see it a lot easier to loss commit privileges). But this is an entirely different topic, one that portmgr has to stop avoiding and start addressing. In fact, there are a lot of areas of policy that need updating (for years now) that are flat-out being neglected. But the PR system as it exists today is still the official process so we should try to make it work. John ___ 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: x11/fbpanel: pkg fallout at 10.x
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA512
20.12.2013 10:58, Baptiste Daroussin пишет:
On Fri, Dec 20, 2013 at 10:42:38AM +0400, Boris Samorodov wrote:
Hi All!
The last week I started to get pkg-fallout@ emails about x11/fbpanel
error:
-
cc panel.o misc.o plugin.o gtkbar.o bg.o gtkbgbox.o ev.o run.o xconf.o
gconf.o gconf_panel.o gconf_plugins.o -o fbpanel -L/usr/local/lib
-lglib-2.0 -lintl -lgtk-x11-2.0 -lgdk-x11-2.0 -lpangocairo-1.0
-latk-1.0 -lcairo -pthread -lgdk_pixbuf-2.0 -lgio-2.0 -lpangoft2-1.0
-lpango-1.0 -lgobject-2.0 -lglib-2.0 -lintl -lfontconfig
-L/usr/local/lib -lfreetype -Wl,--export-dynamic -lgmodule-2.0
-pthread -L/usr/local/lib -lglib-2.0 -lintl -L/usr/local/lib
-lglib-2.0 -lintl -lgtk-x11-2.0 -lgdk-x11-2.0 -lpangocairo-1.0
-latk-1.0 -lcairo -pthread -lgdk_pixbuf-2.0 -lgio-2.0 -lpangoft2-1.0
-lpango-1.0 -lgobject-2.0 -lglib-2.0 -lintl -lfontconfig
-L/usr/local/lib -lfreetype
/usr/bin/ld: �: invalid DSO for symbol `XChangeGC' definition
//usr/local/lib/libX11.so.6: could not read symbols: Bad value
cc: error: linker command failed with exit code 1 (use -v to see invocation)
gmake[2]: *** [fbpanel] Error 1
-
Full log is here:
http://beefy2.isc.freebsd.org/bulk/10amd64-default/2013-12-19_20h45m51s/logs/fbpanel-6.1_4.log
However I can not reproduce it myself:
http://gw.wart.ru/bulk/10-i386-testing/2013-12-19_21h02m40s/logs/fluxbox-1.3.5.log
http://gw.wart.ru/bulk/10-amd64-testing/2013-12-19_21h01m49s/logs/fluxbox-1.3.5.log
Any help is appreciated. Thanks.
That is probably a gtk2 upgrade fallout.
gtk2 pkgconfig file is not adding -lX11 to LDFLAGS anymore.
In general: on FreeBSD 10+, the ld(1) behaviour has been changed so that it
does
not recursively get the DT_NEEDED from libraries it linked binaries to.
Meaning in that case something exposes a X function to fbpanel, but does not
tell it is needs to link to X11
/usr/bin/ld: �: invalid DSO for symbol `XChangeGC' definition
//usr/local/lib/libX11.so.6: could not read symbols: Bad value
LDFLAGS+= -lX11 should solve this.
I've seen some similar commit at the portstree. The problem is: I can't
reproduce the errors (hence can't test a fix).
The strange thing is that my test and pkg-fallout@ use different
environments:
=== pkg-fallout ===
- ---Begin OPTIONS List---
=== The following configuration options are available for fbpanel-6.1_4:
DOCS=on: Build and/or install documentation
=== Use 'make config' to modify these settings
- ---End OPTIONS List---
- --CONFIGURE_ARGS--
- --prefix=/usr/local
- --End CONFIGURE_ARGS--
===
=== my poudriere test ===
- ---Begin OPTIONS List---
=== The following configuration options are available for fluxbox-1.3.5:
DEBUG=off: Install debug symbols
DOCHTML=off: Install html documentation
DOCS=on: Build and/or install documentation
GNOME=off: GNOME desktop environment support
IMLIB2=off: Imlib 2 image library support
NLS=on: Native Language Support
PDFDOCS=off: Build and install PDF documentation
REMEMBER=on: Enable remember feature
SLIT=on: Enable slit feature
SYSTRAY=on: Enable systray feature
TOOLBAR=on: Enable toolbar feature
XINERAMA=off: X11 Xinerama extension support
XRENDER=on: Enable xrender support
=== Use 'make config' to modify these settings
- ---End OPTIONS List---
- --CONFIGURE_ARGS--
- --disable-imlib2 --enable-xinerama --enable-nls --enable-remember
- --enable-slit --enable-systray --enable-toolbar --enable-xrender
- --enable-gnome --x-libraries=/usr/local/lib
- --x-includes=/usr/local/include --prefix=/usr/local
${_LATE_CONFIGURE_ARGS}
- --End CONFIGURE_ARGS--
==
Seems that pkg-fallout does not know anything about port options and
their default values. My poudriere test uses default options. While
pkg-fallout just use the DOCS option.
- --
WBR, Boris Samorodov (bsam)
FreeBSD Committer, http://www.FreeBSD.org The Power To Serve
-BEGIN PGP SIGNATURE-
Version: GnuPG v2.0.22 (FreeBSD)
Comment: Using GnuPG with Thunderbird - http://www.enigmail.net/
iQIcBAEBCgAGBQJStEwsAAoJEJYOILA6P20oWUkP/R9oAGPCupUMLLPUwxlPPXLq
awBJO2iLNfYUlyW37wj8hAidMyCQpit0T4jcuj+f897Y/I7P2He33s7Z3d/gvzF+
M9E8XXHIRFbJYmeT9HDuPCVaOGBEVrHAHfQ4PBZw0zkhnhyjElMZsv0f8RlnQHFt
EU+PsCUl33LabTpD7by3eVpM/whULSjedpmQEuqDsDn7pCBEGPH5f3Oige1h2VSH
5/Xy/3Iw/M5u5kn8Y83l0j3GmfJVQjNhfwrrqMPJFA5n4d29sMMdcaisiN5QYuNs
kA9EPYt6IdOEv3NqW1G4lyIP5Pk6ijBgYcL0EVf7wy4bOaJ6Mk5W2XSKhV17qiPP
P5Yrsao9qocErT02IPe/O4aW7hDVUeUzr50/rhRP/FzDeE0s7OLOrF/1uf1RST19
BMil5IO1LFeWsbfols/b12lOK+d/8T2am3uaEzKWm/JPH7dlyFQjh5kUsOmwgLY3
ty0QvgqvMHKUwE2tXlQJzhh1aAkerPENTX0sxfO/SChohMPJVE61nxNbZTaQL0Hn
orm81c6quWWNpp+7CMGbe0PdSWxKXSkvQrKhJO6pY9B7QIKSwEvGZfVhJ3VEhmub
LLICpttC2vSjEh6T8T3MS60/xB6Syrp7phdW9qvWnSZImo+RLulxu4OfQdCkJHAY
UjpA3YRXX6XT9RUn2nMI
=WWeA
-END PGP SIGNATURE-
___
freebsd-ports@freebsd.org mailing list
Re: x11/fbpanel: pkg fallout at 10.x
On 12/20/2013 14:54, Boris Samorodov wrote: 20.12.2013 10:58, Baptiste Daroussin пишет: On Fri, Dec 20, 2013 at 10:42:38AM +0400, Boris Samorodov wrote: gtk2 pkgconfig file is not adding -lX11 to LDFLAGS anymore. In general: on FreeBSD 10+, the ld(1) behaviour has been changed so that it does not recursively get the DT_NEEDED from libraries it linked binaries to. Meaning in that case something exposes a X function to fbpanel, but does not tell it is needs to link to X11 /usr/bin/ld: �: invalid DSO for symbol `XChangeGC' definition //usr/local/lib/libX11.so.6: could not read symbols: Bad value LDFLAGS+= -lX11 should solve this. I've seen some similar commit at the portstree. The problem is: I can't reproduce the errors (hence can't test a fix). I've recently seen dozens of similar, new errors on dports/dragonfly. It's definitely a pkgconf issue and it just appeared. I haven't tracked it done yet, but adding LDFLAGS+= to every broken port is not ideal. It's better to figure out which .pc file is broken and fix that. John ___ 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: x11/fbpanel: pkg fallout at 10.x
20.12.2013 18:00, John Marino пишет: It's better to figure out which .pc file is broken and fix that. I believe it's what kwm@ is working on. -- WBR, Boris Samorodov (bsam) FreeBSD Committer, http://www.FreeBSD.org The Power To Serve ___ 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: If ports@ list continues to be used as substitute for GNATS, I'm unsubscribing
On 21/12/2013 12:41 AM, John Marino wrote: On 12/20/2013 14:17, Kubilay Kocak wrote: I don't know about the rest of you, but I am that user too. A @FreeBSD.org email, commit bit and still a new user that doubts myself sometimes and looks to the team for the right thing to do. If not for the encouragement of those in the project who grok what motivates and demotivates people, I wouldn't be doing what I do today. This thread is a real shame, mired in technical minutia as if that's what really matters. I am here to enable and be a steward for users like Anton, and your contributions are valued. So thank you for sharing. This sentiment described above is fine, but the thread was never focused on cases like this. The very narrow focus is on when the user is saavy enough to recognize that the problem is not him, and that the problem deserves a report. Rather than submit a PR however, the user just sends it to ports@. That is not the case you are talking about -- in your scenario, the user is going to provide context and express his confusion or doubt. That is a far cry from sending exclusively a build log. So the real shame is that topic is getting expanding to include all user interaction which was never the intent. btw, accepting PRs at ports@ because we the maintainers are not processing GNATS PRs better is treating the symptom of a bigger issue. Yes, GNATS is antiquated, and letting the user specified the classification is beyond boneheaded (as is never fixing that issue). However, a lot of the PR processing issues is centered on inadequate policies and frankly a coddling of delinquent maintainers (I'd like to see it a lot easier to loss commit privileges). But this is an entirely different topic, one that portmgr has to stop avoiding and start addressing. In fact, there are a lot of areas of policy that need updating (for years now) that are flat-out being neglected. But the PR system as it exists today is still the official process so we should try to make it work. John I appreciate the distinction, and I agree with your premises. Setting a high standard is not in question. If your aim however, is to change or influence others, and you'll grant that not everyone can know all there is to know about the values and behaviours we espouse in advance, then a reply guiding (read: leading) those individuals in the right direction would likely prove more effective than what was perhaps just a symptom of frustration. If you don't feel up to taking on that role, then maybe unsubscribing is the way to go, though I hope its not as you have a lot of value to add. koobs ___ 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: If ports@ list continues to be used as substitute for GNATS, I'm unsubscribing
On 12/20/2013 15:09, Kubilay Kocak wrote: I appreciate the distinction, and I agree with your premises. Setting a high standard is not in question. Thanks. If your aim however, is to change or influence others, and you'll grant that not everyone can know all there is to know about the values and behaviours we espouse in advance, then a reply guiding (read: leading) those individuals in the right direction would likely prove more effective than what was perhaps just a symptom of frustration. At the beginning of the thread, I used the gcc developer list as an actual example. If anyone posst an inappropriate topic to the list, it may get answered, but it will always get a this is not appropriate for this list, please don't do it again, use the list for this next time. I can imagine it's a slight put-off for brand new users but it is effective. People make a mistake once, and after that they do the right thing. Since they are publicly corrected, you can imagine they educate dozens of people *before* they can make the same mistake. So I'm talking about policing the list consistently. If you don't feel up to taking on that role, then maybe unsubscribing is the way to go, though I hope its not as you have a lot of value to add. I had to try, but I suspected this thread would go the way of NetBSD (Much discussion, zero net effect) and so far it has. I expect this topic to die down soon and I'll unsubscribe around new years eve, since two weeks seems to be the ports grace period. :) John ___ 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
ports/181836
Hi, It was suggested to me that I ask this question here. Per http://www.freebsd.org/cgi/query-pr.cgi?pr=181836 An issue in the FreeBSD port of smartmontools was fixed on 21-November, yet an update containing that fix has not yet propagated through the ports system. What needs to happen for an updated port to be distributed? Thank you. Jay 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: If ports@ list continues to be used as substitute for GNATS, I'm unsubscribing
On 21/12/2013 1:24 AM, John Marino wrote: On 12/20/2013 15:09, Kubilay Kocak wrote: I appreciate the distinction, and I agree with your premises. Setting a high standard is not in question. Thanks. If your aim however, is to change or influence others, and you'll grant that not everyone can know all there is to know about the values and behaviours we espouse in advance, then a reply guiding (read: leading) those individuals in the right direction would likely prove more effective than what was perhaps just a symptom of frustration. At the beginning of the thread, I used the gcc developer list as an actual example. If anyone posst an inappropriate topic to the list, it may get answered, but it will always get a this is not appropriate for this list, please don't do it again, use the list for this next time. I can imagine it's a slight put-off for brand new users but it is effective. People make a mistake once, and after that they do the right thing. Since they are publicly corrected, you can imagine they educate dozens of people *before* they can make the same mistake. Delivery matters, more than people think, or recognize. corrected - developed, enlightened, tutored, polished policing - maintaining high quality It *is* possible to set assertive, clear expectations and have a positive interaction that sets the tone for the rest of a users experience. So I'm talking about policing the list consistently. If you don't feel up to taking on that role, then maybe unsubscribing is the way to go, though I hope its not as you have a lot of value to add. I had to try, but I suspected this thread would go the way of NetBSD (Much discussion, zero net effect) and so far it has. I expect this topic to die down soon and I'll unsubscribe around new years eve, since two weeks seems to be the ports grace period. :) John Seek and you shall find. Confirmation bias perhaps. :) ___ 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: vlc 2.1.2,4
On Friday 20 December 2013 06:18:24 you wrote:
Hi!
I don't know what is different but previous update of 2.1.1,4 which I had
problem to built (QT4 plugin) to version 2.1.1_1,4 works and version
2.1.1_2,4 works too but todays update doesn't works again:
GEN ../modules/plugins.dat
gmake[4]: *** [../modules/plugins.dat] Segmentation fault (core dumped)
gmake[4]: Leaving directory `/usr/ports/multimedia/vlc/work/vlc-2.1.2/bin'
gmake[3]: *** [all-recursive] Error 1
gmake[3]: Leaving directory `/usr/ports/multimedia/vlc/work/vlc-2.1.2'
gmake[2]: *** [all] Error 2
gmake[2]: Leaving directory `/usr/ports/multimedia/vlc/work/vlc-2.1.2'
=== Compilation failed unexpectedly.
Try to set MAKE_JOBS_UNSAFE=yes and rebuild before reporting the failure to
the maintainer.
*** Error code 1
Stop.
make[1]: stopped in /usr/ports/multimedia/vlc
*** Error code 1
I don't know what is going wrong...it works...it doesn't.
It missed vlc-notify.patch. With this patch it build on my FreeBSD 10.0-RC2.
--
Mitja
---
http://www.redbubble.com/people/lumiwa
Index: Makefile
===
--- Makefile (revision 335948)
+++ Makefile (working copy)
@@ -167,7 +167,8 @@
NLS_USES= gettext
NLS_CONFIGURE_ENABLE= nls
-NOTIFY_LIB_DEPENDS= libnotify.so:${PORTSDIR}/devel/libnotify
+NOTIFY_LIB_DEPENDS= libnotify.so:${PORTSDIR}/devel/libnotify \
+ libgtk-x11-2.0.so:${PORTSDIR}/x11-toolkits/gtk20
NOTIFY_CONFIGURE_ENABLE= notify
OPTIMIZED_CFLAGS_CFLAGS= -O3 -ffast-math -fomit-frame-pointer
___
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: ports/181836
El 20/12/2013 15:50, Jay Borkenhagen j...@braeburn.org escribió: Hi, It was suggested to me that I ask this question here. Per http://www.freebsd.org/cgi/query-pr.cgi?pr=181836 An issue in the FreeBSD port of smartmontools was fixed on 21-November, yet an update containing that fix has not yet propagated through the ports system. What needs to happen for an updated port to be distributed? It needs to catch the attention of a ports committer. Thank you. Jay 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 ___ 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: ports/181836
Hi, Ask/harass someone to commit the patch and bump PORTREVISION ... That's all. - regard On 20/12/13 09:49 -0500, Jay Borkenhagen wrote: Hi, It was suggested to me that I ask this question here. Per http://www.freebsd.org/cgi/query-pr.cgi?pr=181836 An issue in the FreeBSD port of smartmontools was fixed on 21-November, yet an update containing that fix has not yet propagated through the ports system. What needs to happen for an updated port to be distributed? Thank you. Jay 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 ___ 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
Can someone please commit ports/183905
It's super trivial. http://www.freebsd.org/cgi/query-pr.cgi?pr=ports/183905 -- 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
Re: ports/181836
Thanks, Rodrigo (and Fernando as well). Have I come to the right place to find someone who can and will do that kind of thing? Rodrigo Osorio writes: Hi, Ask/harass someone to commit the patch and bump PORTREVISION ... That's all. - regard On 20/12/13 09:49 -0500, Jay Borkenhagen wrote: Hi, It was suggested to me that I ask this question here. Per http://www.freebsd.org/cgi/query-pr.cgi?pr=181836 An issue in the FreeBSD port of smartmontools was fixed on 21-November, yet an update containing that fix has not yet propagated through the ports system. What needs to happen for an updated port to be distributed? Thank you. Jay 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 ___ 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: ports/181836
El 20/12/2013 17:26, Jay Borkenhagen j...@braeburn.org escribió: Thanks, Rodrigo (and Fernando as well). Have I come to the right place to find someone who can and will do that kind of thing? IMHO, freebsd-ports@ is the proper place. Let's see if some committer reads your message. Rodrigo Osorio writes: Hi, Ask/harass someone to commit the patch and bump PORTREVISION ... That's all. - regard On 20/12/13 09:49 -0500, Jay Borkenhagen wrote: Hi, It was suggested to me that I ask this question here. Per http://www.freebsd.org/cgi/query-pr.cgi?pr=181836 An issue in the FreeBSD port of smartmontools was fixed on 21-November, yet an update containing that fix has not yet propagated through the ports system. What needs to happen for an updated port to be distributed? Thank you. Jay 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 ___ 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
Re: Can someone please commit ports/183905
Hi, Committed. On Fri, Dec 20, 2013 at 1:54 PM, Michael Gmelin free...@grem.de wrote: It's super trivial. http://www.freebsd.org/cgi/query-pr.cgi?pr=ports/183905 -- 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 -- William Grzybowski -- Curitiba/PR - Brasil ___ 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: Can someone please commit ports/183905
On Fri, 20 Dec 2013 15:29:09 -0200 William Grzybowski willia...@gmail.com wrote: Hi, Committed. Thank you. -- 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
Re: If ports@ list continues to be used as substitute for GNATS, I'm unsubscribing
On Sat, Dec 21, 2013 at 12:17:21AM +1100, Kubilay Kocak wrote: On 20/12/2013 10:32 PM, Anton Shterenlikht wrote: In other words, as a new user I thought of sending a PR as a last resort, because I doubted myself a lot more than the stability of FreeBSD and the expertise of the team. The actual tools to submit a PR were never an obstacle. This. If you don't *get* what Anton just said, read it again until you do. I don't know about the rest of you, but I am that user too. A @FreeBSD.org email, commit bit and still a new user that doubts myself sometimes and looks to the team for the right thing to do. I got what Anton said, and it's irrelevant to what I said before that. I take the same approach, except that it usually never gets to the last resort phase of submitting a PR because it's much easier to seek help in IRC channels I frequent with knowledgeable people in them, and when *that* is exhausted I *still* don't want to use the PR system, because it sucks so badly. The PR system sucks. That's the problem I was pointing out. Yes, the approach of triple-checking to make sure it's not you who's at fault, and of using questions@ instead of ports@ to seek help, is good. No, that doesn't mean the PR system is easy to use. I also think that people who post nothing but a dump log to ports@ are Doing It Wrong and should be gently encouraged to do things differently, and I doubt that making problem reports easier than send-pr will affect the kinds of people who think that ports@ is a good place for dump logs with no explanation very much, but that doesn't mean the PR system doesn't need help. I'm glad something is being done about the PR system. I'm grateful to those making the changes. Making comments to the effect that there's nothing wrong with the PR system when many people obviously find it daunting and discouraging to attempt to use it -- that comes off like a dismissal of the very people who can contribute real value by alerting port maintainers and committers to the fact there are potentially unnoticed issues. -- Chad Perrin [ original content licensed OWL: http://owl.apotheon.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: If ports@ list continues to be used as substitute for GNATS, I'm unsubscribing
On Fri, Dec 20, 2013 at 12:30:09PM +, Thomas Mueller wrote: I think train wreck applies more to sendmail than send-pr. Sendmail dates back to long-ago pre-Internet days where computer users didn't send email to other computer users. Now a computer user needs to be able to send through ISP's SMTP server. I think the fact one needs, by default, to have sendmail set up before one can use send-pr is a problem with send-pr as well. -- Chad Perrin [ original content licensed OWL: http://owl.apotheon.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: If ports@ list continues to be used as substitute for GNATS, I'm unsubscribing
On Fri, Dec 20, 2013 at 12:51 PM, Chad Perrin c...@apotheon.net wrote: On Fri, Dec 20, 2013 at 12:30:09PM +, Thomas Mueller wrote: I think train wreck applies more to sendmail than send-pr. Sendmail dates back to long-ago pre-Internet days where computer users didn't send email to other computer users. Now a computer user needs to be able to send through ISP's SMTP server. I think the fact one needs, by default, to have sendmail set up before one can use send-pr is a problem with send-pr as well. [ bugmeister@ hat off ] I think just about everyone doesn't like send-pr / GNATS. We *are* working to move towards bugzilla. In fact I think a few test emails may have leaked. ;) The question is what to do in the meantime. Merely sending the build log an no additional context (revision of ports tree, what other ports were being installed, etc.) is not useful either as a PR or as an email. In either case this forces the maintainer/developer/contributor to email back and ask for more details. We *do* have documents explaining the needed information but they are long and probably confusing. A simple one paragraph here is the information we need when you send a bug report is a good idea. That said, assuming you are providing enough details, a PR is the most helpful as it allows us at least some rudimentary level of tracking. Emails shouldn't be ignored, but also shouldn't be the first resort for bug reports either. ___ 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: x11/fbpanel: pkg fallout at 10.x
On 20-12-2013 15:00, John Marino wrote: On 12/20/2013 14:54, Boris Samorodov wrote: 20.12.2013 10:58, Baptiste Daroussin пишет: On Fri, Dec 20, 2013 at 10:42:38AM +0400, Boris Samorodov wrote: gtk2 pkgconfig file is not adding -lX11 to LDFLAGS anymore. In general: on FreeBSD 10+, the ld(1) behaviour has been changed so that it does not recursively get the DT_NEEDED from libraries it linked binaries to. Meaning in that case something exposes a X function to fbpanel, but does not tell it is needs to link to X11 /usr/bin/ld: �: invalid DSO for symbol `XChangeGC' definition //usr/local/lib/libX11.so.6: could not read symbols: Bad value LDFLAGS+= -lX11 should solve this. I've seen some similar commit at the portstree. The problem is: I can't reproduce the errors (hence can't test a fix). I've recently seen dozens of similar, new errors on dports/dragonfly. It's definitely a pkgconf issue and it just appeared. I haven't tracked it done yet, but adding LDFLAGS+= to every broken port is not ideal. It's better to figure out which .pc file is broken and fix that. John Should be fixed now, I restored the old behaviour. --- This email is free from viruses and malware because avast! Antivirus protection is active. http://www.avast.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: x11/fbpanel: pkg fallout at 10.x
21.12.2013 01:20, Koop Mast пишет: On 20-12-2013 15:00, John Marino wrote: On 12/20/2013 14:54, Boris Samorodov wrote: 20.12.2013 10:58, Baptiste Daroussin пишет: On Fri, Dec 20, 2013 at 10:42:38AM +0400, Boris Samorodov wrote: gtk2 pkgconfig file is not adding -lX11 to LDFLAGS anymore. In general: on FreeBSD 10+, the ld(1) behaviour has been changed so that it does not recursively get the DT_NEEDED from libraries it linked binaries to. Meaning in that case something exposes a X function to fbpanel, but does not tell it is needs to link to X11 /usr/bin/ld: �: invalid DSO for symbol `XChangeGC' definition //usr/local/lib/libX11.so.6: could not read symbols: Bad value LDFLAGS+= -lX11 should solve this. I've seen some similar commit at the portstree. The problem is: I can't reproduce the errors (hence can't test a fix). I've recently seen dozens of similar, new errors on dports/dragonfly. It's definitely a pkgconf issue and it just appeared. I haven't tracked it done yet, but adding LDFLAGS+= to every broken port is not ideal. It's better to figure out which .pc file is broken and fix that. Should be fixed now, I restored the old behaviour. Thank you! -- WBR, Boris Samorodov (bsam) FreeBSD Committer, http://www.FreeBSD.org The Power To Serve ___ 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: x11/fbpanel: pkg fallout at 10.x
On 12/20/2013 22:20, Koop Mast wrote:
On 20-12-2013 15:00, John Marino wrote:
On 12/20/2013 14:54, Boris Samorodov wrote:
20.12.2013 10:58, Baptiste Daroussin пишет:
On Fri, Dec 20, 2013 at 10:42:38AM +0400, Boris Samorodov wrote:
gtk2 pkgconfig file is not adding -lX11 to LDFLAGS anymore.
In general: on FreeBSD 10+, the ld(1) behaviour has been changed so
that it does
not recursively get the DT_NEEDED from libraries it linked binaries to.
Meaning in that case something exposes a X function to fbpanel, but
does not
tell it is needs to link to X11
/usr/bin/ld: �: invalid DSO for symbol `XChangeGC' definition
//usr/local/lib/libX11.so.6: could not read symbols: Bad value
LDFLAGS+= -lX11 should solve this.
I've seen some similar commit at the portstree. The problem is: I can't
reproduce the errors (hence can't test a fix).
I've recently seen dozens of similar, new errors on dports/dragonfly.
It's definitely a pkgconf issue and it just appeared.
I haven't tracked it done yet, but adding LDFLAGS+= to every broken port
is not ideal. It's better to figure out which .pc file is broken and
fix that.
John
Should be fixed now, I restored the old behaviour.
Hmm, I fixed it differently. I waited until now until the partial bulk
build completed, which confirmed the fix worked. The attached
Makefile.DragonFly has been present for months, but the diff to the
Makefile is what was missing which caused a bad .pc file generation.
After adding the one line to the makefile and in addition to the changes
in Makefile.DragonFly, all the broken ports built.
John
--- Makefile.orig 2013-12-20 16:29:25.910469000 +
+++ Makefile
@@ -61,6 +61,7 @@ post-patch:
@${FIND} ${WRKSRC} -name Makefile.in | ${XARGS} ${GREP} -l lgmodule |
\
${XARGS} ${REINPLACE_CMD} -e 's|-lgmodule|@GMODULE_LIBS@|g'
@${REINPLACE_CMD} -e 's|[{]libdir[}]/locale|{datadir}/locale|g' \
+ -e 's|GTK_PACKAGES pangoft2|GTK_PACKAGES x11 pangoft2|' \
${WRKSRC}/configure
@${REINPLACE_CMD} -e 's|@LN_S@|${LN} -sf|' ${WRKSRC}/gtk/Makefile.in
@${REINPLACE_CMD} -e 's|file,cups|file,cups,lpr|' \
USE_XORG+= pixman
LIB_DEPENDS+= png15:${PORTSDIR}/graphics/png
LIB_DEPENDS+= freetype.9:${PORTSDIR}/print/freetype2
LIB_DEPENDS+= fontconfig:${PORTSDIR}/x11-fonts/fontconfig
LIB_DEPENDS+= cairo:${PORTSDIR}/graphics/cairo
LIB_DEPENDS+= expat:${PORTSDIR}/textproc/expat2
___
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
