Re: 2nd deprecation campaign
On 6/17/11, Baptiste Daroussin b...@freebsd.org wrote: 2011/6/16 b. f. bf1...@googlemail.com: bapt wrote: I am in the middle of a new deprecation campaign, to remove ports where no more distfiles are publicly available (no other OS mirrors doesn't count except if they are the upstream of course). Maybe some will be false positive (I will try to not have too much of them). Could you please explain how you are checking this? Just looking at some of the recent deprecations, graphics/peps, graphics/vcg, and graphics/xfig are still available. On earlier ones, graphics/libconvolve exists in the jack_convolve section of the heaven sourceforge project: Those are not deprecated but broken, broken because they don't fetch and they need someone to take care of it, to send the new master_site line for example, I don't have time enough to update/fix all the master_site lines from the whole ports tree, so I I see none of the said master_site provide the distfiles, it is marked as broken because that is what it is. Well, the build often isn't broken (and users don't notice that it is broken) because the distfile may be cached locally, or on the project servers, so this is more a matter of policy in many cases. But I take your point. I saw that you began doing this soon after you announced a deprecation campaign, so I wasn't sure if your were doing this a preliminary step, before deprecating them in the near future. ... http://packages.qa.debian.org/g/gsmlib.html Debian having the package doesn't mean that they are the upstream. No, but in this case the Debian maintainer has taken over that role in the absence of the original authors, as described in the changelog there. 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: 2nd deprecation campaign
The depreciation is only for those ports that don't have public available distfiles right? So that I agree that broken ports should be excluded from this depreciation. That is the way it is done, anyway there still could be some false positive having people to doulble check is always good :) So yes, always give people chance to fix ports, not remove them from the tree. And, do we have a list of all maintainer-wanted ports, because that would be great if we have. Here you are :) http://www.freshports.org/search.php?stype=maintainermethod=exactquery=po...@freebsd.org Regards, Hai Lang regards, Bapt ___ 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: 2nd deprecation campaign
2011/6/17 b. f. bf1...@googlemail.com: On 6/17/11, Baptiste Daroussin b...@freebsd.org wrote: 2011/6/16 b. f. bf1...@googlemail.com: bapt wrote: I am in the middle of a new deprecation campaign, to remove ports where no more distfiles are publicly available (no other OS mirrors doesn't count except if they are the upstream of course). Maybe some will be false positive (I will try to not have too much of them). Could you please explain how you are checking this? Just looking at some of the recent deprecations, graphics/peps, graphics/vcg, and graphics/xfig are still available. On earlier ones, graphics/libconvolve exists in the jack_convolve section of the heaven sourceforge project: Those are not deprecated but broken, broken because they don't fetch and they need someone to take care of it, to send the new master_site line for example, I don't have time enough to update/fix all the master_site lines from the whole ports tree, so I I see none of the said master_site provide the distfiles, it is marked as broken because that is what it is. Well, the build often isn't broken (and users don't notice that it is broken) because the distfile may be cached locally, or on the project servers, so this is more a matter of policy in many cases. But I take your point. I saw that you began doing this soon after you announced a deprecation campaign, so I wasn't sure if your were doing this a preliminary step, before deprecating them in the near future. ... http://packages.qa.debian.org/g/gsmlib.html Debian having the package doesn't mean that they are the upstream. No, but in this case the Debian maintainer has taken over that role in the absence of the original authors, as described in the changelog there. b. Thanks for pointing this, but it still need a patch, because the distfile has change. Thanks. Bapt ___ 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: 2nd deprecation campaign
On Jun 17, 2011, at 2:05 PM, Baptiste Daroussin wrote: The depreciation is only for those ports that don't have public available distfiles right? So that I agree that broken ports should be excluded from this depreciation. That is the way it is done, anyway there still could be some false positive having people to doulble check is always good :) Agreed, but I just feel like these ports should not be in the depreciation list at the first place. That's my point my I could be wrong. So yes, always give people chance to fix ports, not remove them from the tree. And, do we have a list of all maintainer-wanted ports, because that would be great if we have. Here you are :) http://www.freshports.org/search.php?stype=maintainermethod=exactquery=po...@freebsd.org What if we just put all un-maintained ports in this list instead of in the depreciation list? Regards, Hai Lang regards, Bapt Regards, Hai Lang___ 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: 2nd deprecation campaign
On Jun 17, 2011, at 1:45 PM, Baptiste Daroussin wrote: 2011/6/16 b. f. bf1...@googlemail.com: bapt wrote: I am in the middle of a new deprecation campaign, to remove ports where no more distfiles are publicly available (no other OS mirrors doesn't count except if they are the upstream of course). Maybe some will be false positive (I will try to not have too much of them). Could you please explain how you are checking this? Just looking at some of the recent deprecations, graphics/peps, graphics/vcg, and graphics/xfig are still available. On earlier ones, graphics/libconvolve exists in the jack_convolve section of the heaven sourceforge project: Those are not deprecated but broken, broken because they don't fetch and they need someone to take care of it, to send the new master_site line for example, I don't have time enough to update/fix all the master_site lines from the whole ports tree, so I I see none of the said master_site provide the distfiles, it is marked as broken because that is what it is. The depreciation is only for those ports that don't have public available distfiles right? So that I agree that broken ports should be excluded from this depreciation. http://sourceforge.net/projects/heaven/files/Audio%20Applications/Jack%20Related/jack_convolve/ security/libident is available via one of the main vlc developers at: http://www.remlab.net/files/libident/ comms/gsmlib is maintained by Debian: http://packages.qa.debian.org/g/gsmlib.html Debian having the package doesn't mean that they are the upstream. science/bblimage has been renamed to pyvox and is available at: http://www.med.upenn.edu/bbl/downloads/pyvox/ That's eight false positives out of eleven deprecations that I selected by inspection, and I didn't spend more than two minutes checking any of them. Keep in mind that : deprecated != broken And those ports expecting for somone to look after them for a long time now it is done, then my process is good :) So yes, always give people chance to fix ports, not remove them from the tree. And, do we have a list of all maintainer-wanted ports, because that would be great if we have. I will fix the above. Thanks for a lot. 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 Regards, Hai Lang___ 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: 2nd deprecation campaign
On Jun 17, 2011, at 2:14 PM, Baptiste Daroussin wrote: 2011/6/17 Lang Hai freeal...@gmail.com: On Jun 17, 2011, at 2:05 PM, Baptiste Daroussin wrote: The depreciation is only for those ports that don't have public available distfiles right? So that I agree that broken ports should be excluded from this depreciation. That is the way it is done, anyway there still could be some false positive having people to doulble check is always good :) Agreed, but I just feel like these ports should not be in the depreciation list at the first place. That's my point my I could be wrong. So yes, always give people chance to fix ports, not remove them from the tree. And, do we have a list of all maintainer-wanted ports, because that would be great if we have. Here you are :) http://www.freshports.org/search.php?stype=maintainermethod=exactquery=po...@freebsd.org What if we just put all un-maintained ports in this list instead of in the depreciation list? They already are in this list :) That is this list I'm trying to cleanup Oh, sorry for my misunderstanding and I will try to see whether I can save some ports from that list. Regards, Hai Lang regards, Bapt Regards, Hai Lang___ 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 Regards, Hai Lang___ 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: Issue with apr1 on up to date freebsd stable
eculp-5 wrote: Quoting Olli Hauer lt;oha...@freebsd.orggt;: On 2011-05-19 19:51, eculp wrote: Quoting eculp lt;ec...@encontacto.netgt;: Quoting Olli Hauer lt;oha...@freebsd.orggt;: On 2011-05-18 20:57, eculp wrote: Quoting eculp lt;ec...@encontacto.netgt;: For a couple of days I have not been able to upgrade apr1. It dies with libtool that I've also rebuilt. checking for minix/config.h... no checking whether it is safe to define __EXTENSIONS__... yes checking for library containing strerror... none required checking whether system uses EBCDIC... no performing libtool configuration... ./configure: 9904: Syntax error: word unexpected (expecting )) *** Error code 2 Stop in /new/usr/local/ports/devel/apr1. *** Error code 1 Stop in /new/usr/local/ports/devel/apr1. uname -a FreeBSD unixmania.com 7.4-STABLE FreeBSD 7.4-STABLE #1203: Wed Apr 20 04:57:59 CDT 2011 r...@unixmania.com:/usr/obj/usr/src/sys/ENCONTACTO i386 The system is actually up to date with a kernel compile from this morning but I haven't reset it since Apr. 20. Ports are a few days behind because of this problem with apr1. Hi Ed, I just build apr1 with LDAP on 7.4-i386 and 8.2-amd64. Please try with an updated portstree, there was a patch submitted to apr1. If this doesn't help please provide also a $ make showconfig from your apr1 directory and which openldap version is used. Thanks for your reply Olli, The kernel and all sources are updated daily everything is based on today's sources, kernel and ports that build.. Ports are a bit behind because I need apr1 to build first. # uname -a FreeBSD unixmania.com 7.4-STABLE FreeBSD 7.4-STABLE #1210: Wed May 18 05:16:34 CDT 2011 r...@unixmania.com:/usr/obj/usr/src/sys/ENCONTACTO i386 /usr/ports/devel/apr1 # make showconfig === The following configuration options are available for apr-ipv6-devrandom-gdbm-db46-ldap24-1.4.4.1.3.11_1: THREADS=on Enable Threads in apr IPV6=on Enable IPV6 Support in apr BDB=on Enable Berkley BDB support in apr-util GDBM=on Enable GNU dbm support in apr-util LDAP=on Enable LDAP support in apr-util MYSQL=off Enable MySQL suport in apr-util NDBM=off Enable NDBM support in apr-util PGSQL=off Enable Postgresql suport in apr-util SQLITE=off Enable SQLite3 support in apr-util DEVRANDOM=on Use /dev/random or compatible in apr === Use 'make config' to modify these settings Ports that portmaster lists as needing upgrading follows: When I try to build apr1 with a simple make after cleaning all the old automake/config ports it still dies with configure. checking whether it is safe to define __EXTENSIONS__... yes checking for library containing strerror... none required checking whether system uses EBCDIC... no performing libtool configuration... ./configure: 9904: Syntax error: word unexpected (expecting )) *** Error code 2 Stop in /new/usr/local/ports/devel/apr1. *** Error code 1 I hope this is enough to help someone help me. I don't really understand the Syntas error: word unexpected (expecting )) *** Error Code 2 It exceeds my trouble shooting abalities. Hoping for an error I rebuilt all may ports except apache22 and apr1 because of the above error with apr1. All else built without a problem. if anyone has a suggestion, please let me know. Especially about the error above not getting past configure. Thanks, ed Hi Ed, I suspect we will see apr-1.4.5 in short time, hopefully this will fix your issue. Anyway, I wasn't able to reconstruct this issue on 7.4-i368. Maybe you can provide from apr-1.4.3 and apr-1.4.4. - apr1/work/apr-1.4.4/config.log - work/apr-util-1.3.11/config.log Thanks Olli. Only work/apr-util-1.3.11/config.log was generated. work/apr-1.4.4/config.log wasn't. Today I read that 1.4.4 has problems and will be updated soon. I have no idea how important this is but see that most of my php depends on it as does ldap, etc. For the time being I removed it from Apache with no ill effects. Thanks, ed Else I have to wait until the magic crystal ball is back from polishing olli I could sure use a good deal on a Crystal ball should you have an extra one;) I have the exact same problem at the moment... But with (apr1 1.4.5 and libtool 2.4): ./configure.lineno: 9900: Syntax error: word unexpected (expecting )) Din you manage to solve this? Thanks :-) /Jette Derriche -- View this message in context: http://freebsd.1045724.n5.nabble.com/Issue-with-apr1-on-up-to-date-freebsd-stable-tp4406329p4498442.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
Re: 2nd deprecation campaign
One thing you can also do is to provide better deprecation message, recommending alternative/replacement for example, anything that would help users. regards, Bapt ___ 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: tinderbox question
17.06.2011 18:14, Ruslan Mahmatkhanov пишет: Good day. How can i `inject` updated (or new) port into tinderbox Build to test it for correctness? I mean i have not any troubles to build any existing port, but what should i do to place updated or new port into the tinderbox portstree? Ok, it seems i got it. I have /usr/local/tinderbox/8.2-FreeBSD/usr/ports/ that is symlinked to /usr/local/tinderbox/8.2-FreeBSD/a/ports/. It's nullfs mounted fs and it's read-only. I realise that i can just patch /usr/local/tinderbox/portstrees/FreeBSD/ports to achive this goal, but i'm not sure if this is Right Thing or there is some another correct way. This procedure isn't mentioned in Tinderbox Users Guide (maybe it should be too obvious) so i ask there. Thanks. -- Regards, Ruslan ___ 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: tinderbox question
On Fri, Jun 17, 2011 at 06:24:57PM +0400, Ruslan Mahmatkhanov wrote: 17.06.2011 18:14, Ruslan Mahmatkhanov пишет: Good day. How can i `inject` updated (or new) port into tinderbox Build to test it for correctness? I mean i have not any troubles to build any existing port, but what should i do to place updated or new port into the tinderbox portstree? Ok, it seems i got it. I have /usr/local/tinderbox/8.2-FreeBSD/usr/ports/ that is symlinked to /usr/local/tinderbox/8.2-FreeBSD/a/ports/. It's nullfs mounted fs and it's read-only. I realise that i can just patch /usr/local/tinderbox/portstrees/FreeBSD/ports to achive this goal, but i'm not sure if this is Right Thing or there is some another correct way. This procedure isn't mentioned in Tinderbox Users Guide (maybe it should be too obvious) so i ask there. Thanks. Well, I think it is too obvious. Or, to say better, there are too many ways to do it. Personally, I build official ports in tinderbox. So, I null-mount /usr/ports to whatever tinderbox wants it to. If I want to test updated port I move original category/port to caterogy/port.orig and place the new port into category/port (all under /usr/ports). After testing I remove category/port and move original port back. This way csup/portsnap works as usual, keeping /usr/ports up-to-date. The big changes like marcuscom or area51 repos are handled the same way, but globally. So mv /usr/ports /usr/ports.orig, then copy/patch/fetch/... the new ports tree into /usr/ports, test the things, and move back at the end. I find this strategy optimal for occasional ports testing, if you are continiously working with the side repos like above, adding multiple ports trees into tinderbox is (IMHO) the way to go. This is described in tinderbox README. HTH, Alexey. ___ 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: test
sorry ignore this wrong email address On Fri, Jun 17, 2011 at 8:33 PM, matt donovan kitchet...@gmail.com wrote: test -- Technological progress is like an ax in the hands of a pathological criminal. -*Albert Einstein Breadth of Unix experience and depth of knowledge in the world of servers. * -- Technological progress is like an ax in the hands of a pathological criminal. -*Albert Einstein Breadth of Unix experience and depth of knowledge in the world of servers. * ___ 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
