Notice: We have migrated to GitLab launching 2024-05-01 see here:

#2420 closed defect (wontfix)

RSB %source file fails

Reported by: Jakob Viketoft Owned by: Chris Johns
Priority: normal Milestone: 5.1
Component: tool/rsb Version: 5
Severity: normal Keywords:
Cc: Blocked By:


It seems that the method for accessing an existing file repository both isn't covered much in the "manual", but it also fails to find it. Looking at the python code in, it requires the format file:// to identify the local file protocol, but then tries to access the actual file/directory using that the entire url (including file://).

This unfortunately fails and I'm not familiar enough with Python to correct this, although it appears that the "file://" part should be cut from the URL before calling the "return path.isdir(url)" in the _file_downloader function.

Change History (9)

comment:1 Changed on 09/14/15 at 14:03:57 by Gedare Bloom

Owner: set to Chris Johns
Status: newassigned
Version: 4.104.11

comment:2 Changed on 09/14/15 at 14:05:11 by Gedare Bloom

Can you provide some more information about the failure? What are you trying to build, what is the config/bset being used, what %source directive fails? It may help to attach the log

comment:3 Changed on 09/15/15 at 08:45:29 by Jakob Viketoft

Well, at the moment I'm chasing a build bug in newlib and have modified a bset to allow me to change the source code locally. This was a perfect match for the "file" type available for %source, but as I stated it doesn't seem to work completely. (I would also like to use it later to have git sources as submodules instead of cloned-on-demand.)

E.g., if I use a bset and modify the %source path for newlib from e.g. git:// to file:///full_path_to_this_dir/sources/git/newlib it doesn't find the directory. I added a printout of the url variable in _file_downloader in, and the url contains the full given address as file:///full_path_to_this_dir/sources/git/newlib. This is then given to path.isdir and predictably fails.

Or am I missing something fundamental here?

comment:4 Changed on 09/15/15 at 23:54:47 by Chris Johns

There maybe a bug in the 'file' implementation, but I think what you are asking for is something new. I think you are asking to use the source tree as is in the location it is and to build using it where the 'file' expects a tar type file. Using the source in the specified location is currently not implemented. It is an interesting feature to add and I like it. It however would require I take a look to see what it effects and currently time is limited.

comment:5 Changed on 01/26/17 at 07:16:00 by Sebastian Huber


comment:6 Changed on 03/22/17 at 23:58:33 by Chris Johns

Version: 4.114.12

This is a new feature and not suitable on a release branch.

comment:7 Changed on 05/11/17 at 07:31:02 by Sebastian Huber


comment:8 Changed on 11/09/17 at 06:27:14 by Sebastian Huber


Milestone renamed

comment:9 Changed on 12/13/19 at 15:24:21 by Chris Johns

Resolution: wontfix
Status: assignedclosed

I have no time to work on this.

Note: See TracTickets for help on using tickets.