FS#3420 - Subversion now depends on cyrus-sasl it seems, but the dependency is missing

Attached to Project: Arch Linux
Opened by Paul Mattal (paul) - Wednesday, 02 November 2005, 19:07 GMT
Task Type Bug Report
Category Packages: Extra
Status Closed
Assigned To Jason Chu (jason)
Architecture not specified
Severity Low
Priority Normal
Reported Version 0.7 Wombat
Due in Version Undecided
Due Date Undecided
Percent Complete 100%
Votes 0
Private No

Details

Hi Jason,

It looks like the newest build of subversion (1.2.3-5) is built against SASL and should therefore require it, as it needs libgssapi.

Can you fix, or I can if you tell me how you wish to resolve it. (build not against SASL, if possible, vs. add the dependency)

Or maybe I've got it entirely wrong. So let me know.

- P
This task depends upon

Closed by  Jason Chu (jason)
Saturday, 19 November 2005, 16:53 GMT
Reason for closing:  Fixed
Additional comments about closing:  Fixed in neon 0.24.7-4.
Comment by Jason Chu (jason) - Wednesday, 02 November 2005, 19:20 GMT
What does SASL get for us? Is this only for the server or for the client as well?
Comment by Paul Mattal (paul) - Wednesday, 02 November 2005, 20:40 GMT
The ld.so error for libgssapi came for me when I tried to check something out with the svn program. So it appears to affect the client; I'm not sure if it affects the server at all.

My general feeling would be that cyrus-sasl is fairly small, and to require it isn't so bad for people who already have subversion installed, so that's probably the thing to do. The alternative might be to find a build flag that turns off building against sasl, but it seems like a minor point -- and then someone will want it and come along and ask us to build against it. ;)
Comment by Jason Chu (jason) - Wednesday, 02 November 2005, 21:18 GMT
You really just weigh it against how many people you think will ask us to build it without ;)

That's why my first question was what does it get us.
Comment by Paul Mattal (paul) - Wednesday, 02 November 2005, 21:24 GMT
So then my question is: how do we know what it's getting us?

And I guess then you go with the Greg K-H answer with devfs: remove it and find out! It does make some sense, actually.

- P
Comment by Jason Chu (jason) - Thursday, 10 November 2005, 06:48 GMT
I believe it's actually heimdal it depends on and it depends on it because neon depends on it. Strangely, there's no option in the configure script to disable kerberos support. I don't have time to fix this thing tonight, but I've narrowed it down a bit.

It wasn't in there before because I don't use kerberos, but apparently tpowa does so when he libtool slayed it heimdal got added.
Comment by Jan de Groot (JGC) - Thursday, 10 November 2005, 08:43 GMT
Heimdal is a dependency of sasl, which is a dependency for OpenLDAP, which is a dependency for Samba, which is required to use windows shares...

I don't have a problem with having heimdal or sasl included, nor do I have problems when it's not included. And yes, I do use SASL and Kerberos, but not for SVN :P

Loading...