Re: FreeBSD Port: samba34-3.4.14
On Apr 9, 2012, at 5:26 PM, Da Rock wrote: [ ... ] If you think there is a missing dependency, then doing send-pr with the fix is a reasonable procedure. I was only thinking the maintainer might want to know and fix and test themselves before commit. I know I would as a maintainer. Sure-- a PR with a change to a port will be assigned to the maintainer to test and approve. However, you might first want to look into what was different in your case from pointyhat, since the builds of samba-3.x worked fine: http://pointyhat.freebsd.org/errorlogs/amd64-9-latest-logs/samba34-3.4.14.log http://pointyhat.freebsd.org/errorlogs/amd64-9-latest-logs/samba35-3.5.11.log http://pointyhat.freebsd.org/errorlogs/amd64-9-latest-logs/samba36-3.6.3.log Hmmm. You're right. I can narrow it down to the SWAT or AIO option (most likely given the obvious network connection there), but it could be ADS, ACL, or FAM; but I doubt that very much. You have me intrigued now, I have to look into it to know :) So what should the patch look like? Am I correct in my understanding of the BUILD_DEPENDS, or have I chased a goose on that one? Don't know-- I don't recall having a build of Samba fail for me any time recently, but if you can confirm that a specific option causes the build failure, that would help reproduce. Note that I'd gotten the impression that you had installed libnet separately, which would be a library and not just a build dependency... Regards, -- -Chuck ___ freebsd-ports@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-ports To unsubscribe, send any mail to freebsd-ports-unsubscr...@freebsd.org
Re: FreeBSD Port: samba34-3.4.14
On 04/10/12 16:30, Chuck Swiger wrote: On Apr 9, 2012, at 5:26 PM, Da Rock wrote: [ ... ] If you think there is a missing dependency, then doing send-pr with the fix is a reasonable procedure. I was only thinking the maintainer might want to know and fix and test themselves before commit. I know I would as a maintainer. Sure-- a PR with a change to a port will be assigned to the maintainer to test and approve. Ah. I wasn't aware that was the case, especially if the maintainer cannot specifically commit. However, you might first want to look into what was different in your case from pointyhat, since the builds of samba-3.x worked fine: http://pointyhat.freebsd.org/errorlogs/amd64-9-latest-logs/samba34-3.4.14.log http://pointyhat.freebsd.org/errorlogs/amd64-9-latest-logs/samba35-3.5.11.log http://pointyhat.freebsd.org/errorlogs/amd64-9-latest-logs/samba36-3.6.3.log Hmmm. You're right. I can narrow it down to the SWAT or AIO option (most likely given the obvious network connection there), but it could be ADS, ACL, or FAM; but I doubt that very much. You have me intrigued now, I have to look into it to know :) So what should the patch look like? Am I correct in my understanding of the BUILD_DEPENDS, or have I chased a goose on that one? Don't know-- I don't recall having a build of Samba fail for me any time recently, but if you can confirm that a specific option causes the build failure, that would help reproduce. So far all the options are causing _a_ failure- swat, ads, aio, acl, fam. I'm still going, but I think thats all of them. Note that I'd gotten the impression that you had installed libnet separately, which would be a library and not just a build dependency... I am still looking into it as time permits, but I'm not sure I understand the difference? I had to install libnet separately in order to build. How does that fit in your comment? I'm still a very newbie developer so I'm not always accurately understanding the terms, I think. If I start getting these terms right I think I might just get better at this stuff in the makefiles :) ___ 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: samba34-3.4.14
On Tue, Apr 10, 2012 at 9:57 AM, Da Rock freebsd-po...@herveybayaustralia.com.au wrote: On 04/10/12 16:30, Chuck Swiger wrote: On Apr 9, 2012, at 5:26 PM, Da Rock wrote: [ ... ] If you think there is a missing dependency, then doing send-pr with the fix is a reasonable procedure. I was only thinking the maintainer might want to know and fix and test themselves before commit. I know I would as a maintainer. Sure-- a PR with a change to a port will be assigned to the maintainer to test and approve. Ah. I wasn't aware that was the case, especially if the maintainer cannot specifically commit. Note that I'd gotten the impression that you had installed libnet separately, which would be a library and not just a build dependency... I am still looking into it as time permits, but I'm not sure I understand the difference? I had to install libnet separately in order to build. How does that fit in your comment? I'm still a very newbie developer so I'm not always accurately understanding the terms, I think. I'm not sure, which libnet you are referring to. None of the Sambas should really depend from anything called libnet. At least - externally. Also, please show the content of your /etc/make.conf, it could be that you are mangling include flags. With regards, Timur Bakeyev. ___ 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: samba34-3.4.14
On 04/10/12 18:06, Timur I. Bakeyev wrote: On Tue, Apr 10, 2012 at 9:57 AM, Da Rock freebsd-po...@herveybayaustralia.com.au wrote: On 04/10/12 16:30, Chuck Swiger wrote: On Apr 9, 2012, at 5:26 PM, Da Rock wrote: [ ... ] If you think there is a missing dependency, then doing send-pr with the fix is a reasonable procedure. I was only thinking the maintainer might want to know and fix and test themselves before commit. I know I would as a maintainer. Sure-- a PR with a change to a port will be assigned to the maintainer to test and approve. Ah. I wasn't aware that was the case, especially if the maintainer cannot specifically commit. Note that I'd gotten the impression that you had installed libnet separately, which would be a library and not just a build dependency... I am still looking into it as time permits, but I'm not sure I understand the difference? I had to install libnet separately in order to build. How does that fit in your comment? I'm still a very newbie developer so I'm not always accurately understanding the terms, I think. I'm not sure, which libnet you are referring to. None of the Sambas should really depend from anything called libnet. At least - externally. Thats what I'm trying to figure out now, well, as my time permits anyway :) Also, please show the content of your /etc/make.conf, it could be that you are mangling include flags. make.conf: end of make.conf ;) Well thats not entirely accurate, I only have a USE_OPENSSL_BASE and the usual perl stuff and thats all. I get a bit of a kick out of that when someone asks if there's something in the make.conf- I only use some of the kerberos options on occasion when called for (not lately), but I learnt my lesson a long time ago: don't touch the make.conf! I created some issues in the past doing that... :) ___ 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: samba34-3.4.14
On Tue, 10 Apr 2012 19:31:13 +1000 Da Rock articulated: Also, please show the content of your /etc/make.conf, it could be that you are mangling include flags. make.conf: end of make.conf ;) Well thats not entirely accurate, I only have a USE_OPENSSL_BASE and the usual perl stuff and thats all. I get a bit of a kick out of that when someone asks if there's something in the make.conf- I only use some of the kerberos options on occasion when called for (not lately), but I learnt my lesson a long time ago: don't touch the make.conf! I created some issues in the past doing that... :) You have effectively shown us nothing. If you don't want to reveal the contents of your make.conf file, then simply say so. This poppycock nonsense about the usual perl stuff is useless. I checked, and I have exactly two lines that reference perl: # added by use.perl 2012-03-08 19:17:29 PERL_VERSION=5.14.2 Are these the usual perl stuff you are referencing? If so, then your make.conf file consists of only three lines; two if you don't count comments. Is that a correct statement? I have samba34-3.4.14 installed and it works fine and I did not have to mangle the Makefile or install additional software in order to accomplish that feat. Since you, according to you, appear to be the only user afflicted by this condition, it is readily apparent that the problem exists on your end. Your unwillingness to supply unredacted information and documentation raises doubts as to the validity of your claims. For grins, have you tried doing a make rmconfig-recursive in the samba port and then running something like: portmanager net/samba34 -f -l which would effectively rebuild samba and all of the ports it depends on? You should probably remove libnet or what ever extraneous port you installed to get samba to install in the first place first. While you are at it, move your /etc/make.conf file out of the way and have the port build with a truly empty file. -- Jerry ♔ Disclaimer: off-list followups get on-list replies or get ignored. Please do not ignore the Reply-To header. __ ___ 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: samba34-3.4.14
On 4/10/2012 06:14, Da Rock wrote: On 04/10/12 13:14, Mel Flynn wrote: On 4/10/2012 02:26, Da Rock wrote: So what should the patch look like? Am I correct in my understanding of the BUILD_DEPENDS, or have I chased a goose on that one? I'd like to divert your attention to the libnet source directory in samba distribution. It's built by default and integrated into pretty much every binary through libnetapi. Your focus should shift to the compilation error itself, your solution of installing the port libnet masked the actual problem. I'll look into it then. I'm still trying to determine what sets it off. I'm fairly sure ADS is a major factor, though simply disabling it merely grows another failure elsewhere... :/ I'll start posting the logs soon. Is there a particular reason why a dependency on libnet is an issue? If you'd just post the error message and the compilation line that caused it, there'd be a lot of info there that can narrow things down. -- 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: samba34-3.4.14
Completely offtopic, but we have a nice unauthenticated remote root here: http://www.samba.org/samba/security/CVE-2012-1182 -- Regards, Ruslan Tinderboxing kills... the drives. ___ 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: samba34-3.4.14
On Tue, Apr 10, 2012 at 11:35:46PM +0400, Ruslan Mahmatkhanov wrote: Completely offtopic, but we have a nice unauthenticated remote root here: http://www.samba.org/samba/security/CVE-2012-1182 It looks like the ports have just been updated. Please let the update mirror out and then update quickly! This one is particularly nasty. -- 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: FreeBSD Port: samba34-3.4.14
Wesley Shields wrote on 11.04.2012 06:05: On Tue, Apr 10, 2012 at 11:35:46PM +0400, Ruslan Mahmatkhanov wrote: Completely offtopic, but we have a nice unauthenticated remote root here: http://www.samba.org/samba/security/CVE-2012-1182 It looks like the ports have just been updated. Please let the update mirror out and then update quickly! This one is particularly nasty. -- WXS Yes, that was extremely quick update. Thank you Xin Li! But at least for samba34 I was forced to fetch tarball manually because of Moved permanently messages. Some MASTER_SITE_SUBDIR updates should be done to make it work. Thanks. -- Regards, Ruslan Tinderboxing kills... the drives. ___ 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: samba34-3.4.14
On 04/08/12 09:59, Da Rock wrote: On 04/08/12 00:02, Chris Rees wrote: On 7 April 2012 13:51, Da Rockfreebsd-po...@herveybayaustralia.com.au wrote: On 04/06/12 13:20, Timur I. Bakeyev wrote: Hi! Can you show the build output? Port should't directly dipend from anything like this. Sorry, it was on a clients system and I couldn't get the info across. I can only say for sure that installing libnet fixed the issue. The build error was an undeclared function or const (most likely const) that was supplied by libnet. Sorry I can't tell you any more information; I emailed this to notify of the fix, and for others if they come across the issue in the future. Googling was what put me on to this fix as well. If you could give some idea of the site that advised this, that could probably help too. Again, my apologies. Let me try this again and see if I can be a little more organised with my description. This was a clean, fresh install on an amd64 (Atom cpu, although I did try on a real cpu too). I tried 3.6 first, it didn't build. Then I tried 3.5, when that didn't work (same error) I looked at the handbook and it was still on 3.4, and during my googling I noticed that there could be an issue with incompatibility with the libsmbclient; so I reverted to 3.4. It didn't build either, and they all had the same error. So I googled some more on this error, but there wasn't much on it at all. I did notice a lot of comments on samba, tdb, and libnet, and there was a clue in the error of a libnet dependency (sorry I just can't remember, so much has happened in the 24 hr period); so I tried installing libnet and then built samba 3.4 (to avoid further issues and conflicts) and presto! it all built. That was the day prior to my post, and I figured someone could run a clean build and find this as well; failing that, someone would come across this again in the future. As you can see it wasn't anything in particular that set me on this, just a hunch I followed and lucked out on a resolution, but it worked :) I hope that helps someone... To drag this up again, I was thinking about the number of cases I've found like this recently, and I was considering what the most appropriate action to take here. This one is obviously controversial, and I didn't have the time to do more or test further, but for future reference I'd like some clarification. I'd say a PR is not really appropriate as a response to an issue such as this (unless the maintainer offers no response at all), but should I create a patch to assist the maintainer? Or is that over doing it? If I were to create a patch, what is the correct (usable) procedure? And for something like this it would be an adjustment to BUILD_DEPENDS, correct? Thanks for the clarification guys. ___ 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: samba34-3.4.14
Hi-- On Apr 9, 2012, at 4:01 PM, Da Rock wrote: To drag this up again, I was thinking about the number of cases I've found like this recently, and I was considering what the most appropriate action to take here. This one is obviously controversial, and I didn't have the time to do more or test further, but for future reference I'd like some clarification. I'd say a PR is not really appropriate as a response to an issue such as this (unless the maintainer offers no response at all), but should I create a patch to assist the maintainer? Or is that over doing it? If I were to create a patch, what is the correct (usable) procedure? And for something like this it would be an adjustment to BUILD_DEPENDS, correct? If you think there is a missing dependency, then doing send-pr with the fix is a reasonable procedure. However, you might first want to look into what was different in your case from pointyhat, since the builds of samba-3.x worked fine: http://pointyhat.freebsd.org/errorlogs/amd64-9-latest-logs/samba34-3.4.14.log http://pointyhat.freebsd.org/errorlogs/amd64-9-latest-logs/samba35-3.5.11.log http://pointyhat.freebsd.org/errorlogs/amd64-9-latest-logs/samba36-3.6.3.log Regards, -- -Chuck ___ freebsd-ports@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-ports To unsubscribe, send any mail to freebsd-ports-unsubscr...@freebsd.org
Re: FreeBSD Port: samba34-3.4.14
On 04/10/12 09:12, Chuck Swiger wrote: Hi-- On Apr 9, 2012, at 4:01 PM, Da Rock wrote: To drag this up again, I was thinking about the number of cases I've found like this recently, and I was considering what the most appropriate action to take here. This one is obviously controversial, and I didn't have the time to do more or test further, but for future reference I'd like some clarification. I'd say a PR is not really appropriate as a response to an issue such as this (unless the maintainer offers no response at all), but should I create a patch to assist the maintainer? Or is that over doing it? If I were to create a patch, what is the correct (usable) procedure? And for something like this it would be an adjustment to BUILD_DEPENDS, correct? If you think there is a missing dependency, then doing send-pr with the fix is a reasonable procedure. I was only thinking the maintainer might want to know and fix and test themselves before commit. I know I would as a maintainer. However, you might first want to look into what was different in your case from pointyhat, since the builds of samba-3.x worked fine: http://pointyhat.freebsd.org/errorlogs/amd64-9-latest-logs/samba34-3.4.14.log http://pointyhat.freebsd.org/errorlogs/amd64-9-latest-logs/samba35-3.5.11.log http://pointyhat.freebsd.org/errorlogs/amd64-9-latest-logs/samba36-3.6.3.log Hmmm. You're right. I can narrow it down to the SWAT or AIO option (most likely given the obvious network connection there), but it could be ADS, ACL, or FAM; but I doubt that very much. You have me intrigued now, I have to look into it to know :) So what should the patch look like? Am I correct in my understanding of the BUILD_DEPENDS, or have I chased a goose on that one? ___ 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: samba34-3.4.14
On 4/10/2012 02:26, Da Rock wrote: So what should the patch look like? Am I correct in my understanding of the BUILD_DEPENDS, or have I chased a goose on that one? I'd like to divert your attention to the libnet source directory in samba distribution. It's built by default and integrated into pretty much every binary through libnetapi. Your focus should shift to the compilation error itself, your solution of installing the port libnet masked the actual problem. -- 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: samba34-3.4.14
On 04/10/12 13:14, Mel Flynn wrote: On 4/10/2012 02:26, Da Rock wrote: So what should the patch look like? Am I correct in my understanding of the BUILD_DEPENDS, or have I chased a goose on that one? I'd like to divert your attention to the libnet source directory in samba distribution. It's built by default and integrated into pretty much every binary through libnetapi. Your focus should shift to the compilation error itself, your solution of installing the port libnet masked the actual problem. I'll look into it then. I'm still trying to determine what sets it off. I'm fairly sure ADS is a major factor, though simply disabling it merely grows another failure elsewhere... :/ I'll start posting the logs soon. Is there a particular reason why a dependency on libnet is an issue? ___ 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: samba34-3.4.14
On 04/06/12 13:20, Timur I. Bakeyev wrote: Hi! Can you show the build output? Port should't directly dipend from anything like this. Sorry, it was on a clients system and I couldn't get the info across. I can only say for sure that installing libnet fixed the issue. The build error was an undeclared function or const (most likely const) that was supplied by libnet. Sorry I can't tell you any more information; I emailed this to notify of the fix, and for others if they come across the issue in the future. Googling was what put me on to this fix as well. Cheers Cheers. On Fri, Apr 6, 2012 at 3:40 AM, Da Rock freebsd-po...@herveybayaustralia.com.au wrote: Building samba 3.6, 3.5, 3.4... noticed a missing dependency during build on net/libnet. Maybe need to add this to the port? Cheers ___ 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: FreeBSD Port: samba34-3.4.14
On 7 April 2012 13:51, Da Rock freebsd-po...@herveybayaustralia.com.au wrote: On 04/06/12 13:20, Timur I. Bakeyev wrote: Hi! Can you show the build output? Port should't directly dipend from anything like this. Sorry, it was on a clients system and I couldn't get the info across. I can only say for sure that installing libnet fixed the issue. The build error was an undeclared function or const (most likely const) that was supplied by libnet. Sorry I can't tell you any more information; I emailed this to notify of the fix, and for others if they come across the issue in the future. Googling was what put me on to this fix as well. If you could give some idea of the site that advised this, that could probably help too. Chris ___ 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: samba34-3.4.14
On 04/08/12 00:02, Chris Rees wrote: On 7 April 2012 13:51, Da Rockfreebsd-po...@herveybayaustralia.com.au wrote: On 04/06/12 13:20, Timur I. Bakeyev wrote: Hi! Can you show the build output? Port should't directly dipend from anything like this. Sorry, it was on a clients system and I couldn't get the info across. I can only say for sure that installing libnet fixed the issue. The build error was an undeclared function or const (most likely const) that was supplied by libnet. Sorry I can't tell you any more information; I emailed this to notify of the fix, and for others if they come across the issue in the future. Googling was what put me on to this fix as well. If you could give some idea of the site that advised this, that could probably help too. Again, my apologies. Let me try this again and see if I can be a little more organised with my description. This was a clean, fresh install on an amd64 (Atom cpu, although I did try on a real cpu too). I tried 3.6 first, it didn't build. Then I tried 3.5, when that didn't work (same error) I looked at the handbook and it was still on 3.4, and during my googling I noticed that there could be an issue with incompatibility with the libsmbclient; so I reverted to 3.4. It didn't build either, and they all had the same error. So I googled some more on this error, but there wasn't much on it at all. I did notice a lot of comments on samba, tdb, and libnet, and there was a clue in the error of a libnet dependency (sorry I just can't remember, so much has happened in the 24 hr period); so I tried installing libnet and then built samba 3.4 (to avoid further issues and conflicts) and presto! it all built. That was the day prior to my post, and I figured someone could run a clean build and find this as well; failing that, someone would come across this again in the future. As you can see it wasn't anything in particular that set me on this, just a hunch I followed and lucked out on a resolution, but it worked :) I hope that helps someone... ___ 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 Port: samba34-3.4.14
Building samba 3.6, 3.5, 3.4... noticed a missing dependency during build on net/libnet. Maybe need to add this to the port? Cheers ___ 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: samba34-3.4.14
Hi! Can you show the build output? Port should't directly dipend from anything like this. Cheers. On Fri, Apr 6, 2012 at 3:40 AM, Da Rock freebsd-po...@herveybayaustralia.com.au wrote: Building samba 3.6, 3.5, 3.4... noticed a missing dependency during build on net/libnet. Maybe need to add this to the port? Cheers ___ 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