*-svn AUR mega bug.

Question

SourceForge ([url]http://sourceforge.net/docs/A04[/url]) wrote:
Project Subversion (SVN) Service:       Online [1]          Last updated: 2007-01-05 Pacific
Recent Updates »
( 2007-07-09 10:43:54 - Project Subversion (SVN) Service )   As announced, support for the deprecated subversion access method (svn.sourceforge.net) was removed. Please use the PROJECT.svn.sourceforge.net access method that is described in our docs.
This is affecting A LOT of *-svn packages from AUR. They are fetching their SVN sources from https://svn.sourceforge.net and THIS ISN'T WORKING ANYMORE, because they must now specify the project name BEFORE "svn" (https://[projectname].svn.sourceforge.net).
Can any TU fix all of those packages?
Thanks in advance.
Last edited by Alejandro Nova (2007-07-11 04:26:58)

Answer 1

you could try alerting the maintainers/devs of such scripts as yaourt/pacbuild/etc.
alternatively
function sfs() {
pattern="://svn.\(sourceforge\|sf\).net/"
if [[ "${_svntrunk}x" != "x" && `echo $_svntrunk | grep "$pattern"` ]];
then _svntrunk=`echo $_svntrunk | sed "s@$pattern@://${_svnmod}.sourceforge.net/@g"`
fi
alias build="sfs;build;"
in /etc/makepkg.conf should be a sufficient workaround while the pkgbuild maintainers catch-up .
unfortnately i am nowhere near an AL system so i can't confirm that it works.. but simple test with
_svntrunk=https://sf.net/svn/project/trunk
_svnmod=project
function build() {
echo $_svntrunk
#::how i tested it::
#file1: mkpkg > above function + . pb \n build
#file2: pkgbuild >above code
shows promising results
sorry my bash programming isn't as good as I'd like feel free to rip it apart if you like
hope it works;)
Last edited by raeven (2007-07-12 19:38:00)