Pacman

Historical bug tracker for the Pacman package manager.

The pacman bug tracker has moved to gitlab:
https://gitlab.archlinux.org/pacman/pacman/-/issues

This tracker remains open for interaction with historical bugs during the transition period. Any new bugs reports will be closed without further action.
Tasklist

FS#35244 - [pacman] PKGBUILD with bzr source with '+' in URL fails to update

Attached to Project: Pacman
Opened by Alain Kalker (ackalker) - Monday, 13 May 2013, 13:38 GMT
Last edited by Allan McRae (Allan) - Wednesday, 19 November 2014, 08:00 GMT
Task Type Bug Report
Category General
Status Closed
Assigned To No-one
Architecture All
Severity Low
Priority Normal
Reported Version 4.1.2
Due in Version 4.2.0
Due Date Undecided
Percent Complete 100%
Votes 0
Private No

Details

Description:

Working on the attached PKGBUILD, I found that the initial `makepkg -o` fetched the source Bazaar branch alright, but subsequent updates failed with the error:
$ makepkg -o
==> Making package: ntrig_calib-bzr 1:2-1 (Mon May 13 14:37:43 CEST 2013)
==> Retrieving sources...
==> ERROR: /home/miki/pkg/export/ntrig_calib is not a branch of http://bazaar.launchpad.net/~rafi-seas/+junk/ntrig_calib/

After some searching, I found this post: https://mailman.archlinux.org/pipermail/pacman-dev/2013-April/016988.html
which led me to try `bzr info` on the source URL to find out what Bazaar was actually looking for:
$ bzr info http://bazaar.launchpad.net/~rafi-seas/+junk/ntrig_calib/

Standalone branch (format: 2a)
Location:
branch root: http://bazaar.launchpad.net/~rafi-seas/%2Bjunk/ntrig_calib/

I found that I had to URL escape the '+' to make updates work.

It would be nice if this could be fixed in makepkg, so people can copy/paste 'friendly' URLs without having to worry about which strange characters to escape or not.
If else, some documentation in the Wiki on bzr gotchas like this would be nice (this includes having to sometimes add '/trunk/' to the URL).

Additional info:
* package version(s)
pacman 4.1.1-1
bzr 2.5.1-2
* config and/or log files etc.


Steps to reproduce:
- Uncomment the first (failing), comment the second (working) source=... line in the PKGBUILD
- $ makepkg -o; makepkg -o
   PKGBUILD (1.3 KiB)
This task depends upon

Closed by  Allan McRae (Allan)
Wednesday, 19 November 2014, 08:00 GMT
Reason for closing:  Fixed
Additional comments about closing:  fixed somewhere in git...
Comment by Alain Kalker (ackalker) - Monday, 13 May 2013, 14:02 GMT
Ah, I think the discussion I linked to deals with problems like this bug, so I should probably wait for the next version of pacman/makepkg, right?
Comment by Allan McRae (Allan) - Monday, 13 May 2013, 22:08 GMT
That discussion resulted in fixes in 4.1.1. There have been no further fixes if you are using that version.
Comment by Alain Kalker (ackalker) - Tuesday, 14 May 2013, 21:36 GMT
I'm using 4.1.1, so I guess this means the problem exists in -git also? (haven't checked)
Comment by Allan McRae (Allan) - Tuesday, 14 May 2013, 21:50 GMT
Yes.
Comment by Allan McRae (Allan) - Wednesday, 19 November 2014, 08:00 GMT
Just tested with git version. All works fine.

Loading...