FS#34675 - [makepkg] svn export creates build problems

Attached to Project: Pacman
Opened by Joakim Hernberg (jhernberg) - Monday, 08 April 2013, 08:31 GMT
Last edited by Allan McRae (Allan) - Tuesday, 16 April 2013, 02:35 GMT
Task Type Bug Report
Category General
Status Closed
Assigned To No-one
Architecture All
Severity Medium
Priority Normal
Reported Version 4.1.0
Due in Version 4.1.1
Due Date Undecided
Percent Complete 100%
Votes 0
Private No

Details

The use of svn export in makepkg to clone a svn repo seems to break certain functionality, like "svn info" and svnversion, I've also seen the buildsystem itself being confused when building in such a cloned repo. I suggest to use cp -r for svn repos instead to work around this problem.

Steps to Reproduce:

Clone a svn repo with svn export and try to use svn info or svnversion on it.
See: https://aur.archlinux.org/packages/oscam-svn/ and try building it with and without prepare().
With prepare() (meaning that cp -r has been used) the buildprocess will output the string: OSCam ver: 1.20-unstable_svn rev: 8603 target: x86_64-unknown-linux-gnu-ssl-libusb-pcsc
With prepare() commented out (svn export used), the string is: OSCam ver: 1.20-unstable_svn rev: 0 target: x86_64-unknown-linux-gnu-ssl-libusb-pcsc
Note the strange rev number.
This task depends upon

Closed by  Allan McRae (Allan)
Tuesday, 16 April 2013, 02:35 GMT
Reason for closing:  Fixed
Additional comments about closing:  git commit 695f0e44

Loading...