On 04/07/13 at 11:51am, Maxime GAUDUIN wrote: > On Sun, Apr 7, 2013 at 11:24 AM, Allan McRae <[email protected]> wrote: > > > On 06/04/13 16:13, Allan McRae wrote: > > > On 05/04/13 18:33, Maxime Gauduin wrote: > > >> From: Alucryd <[email protected]> > > >> > > >> Currently, you can pull bzr repos using different URLs like "lp:" > > >> "http://"; or "https://"; in the source array. This works well the first > > >> time, but when you want to build the package again and update the local > > >> repo, makepkg will run 'bzr config parent_location' to check if the > > >> local repo is the same as the distant one. Except the reported URL is > > >> generally not the one used in the source array (which is valid > > >> nonetheless) and will fail with a non helpful error message. This patch > > >> makes makepkg print the correct reported URL so that it can be manually > > >> changed in the source array. I, and Gary van der Merwe who wrote the bzr > > >> support, realize this may not be the best approach as it prevents people > > >> from using the convenient "lp:" URLs, but for the time being people will > > >> stop wondering why their valid URLs are rejected. > > >> > > > > > > So there is seriosuly no way to get to the original URL used by bzr? > > > That just seems... crap! This seems fine then. > > > > > > > Can bzr people also take a look at this: > > https://bugs.archlinux.org/task/34650 > > > > Allan > > > > > > > This is the issue I described above. I haven't found any way to determine > the URL used for pulling the distant repo yet, besides making makepkg store > it in a file to be read upon update. For now I have explained how to get > the correct URL on his bug report, I'll add a paragraph on this in the VCS > guidelines wiki article later today. > > -- > Maxime >
It may not be perfect, but bzr info can operate on a remote repo, so could you run `bzr info` on the source url and compare the returned branch root to parent_location? apg
