FS#45799 - [x264] source commit deleted upstream

Attached to Project: Arch Linux
Opened by Johannes Dewender (JonnyJD) - Monday, 27 July 2015, 19:54 GMT
Last edited by Maxime Gauduin (Alucryd) - Tuesday, 28 July 2015, 21:59 GMT
Task Type Bug Report
Category Packages: Extra
Status Closed
Assigned To Ionut Biru (wonder)
Bartłomiej Piotrowski (Barthalion)
Maxime Gauduin (Alucryd)
Architecture All
Severity Low
Priority Normal
Reported Version
Due in Version Undecided
Due Date Undecided
Percent Complete 100%
Votes 1
Private No


In the latest package update for x264 (2:148.20150717-1)
an unstable repository is used:

The used commit (e6d2a36bbc994274281e1a800b8125102774f2a7) was recently removed from the upstream repository.
So the PKGBUILD can not be used anymore to build a package (unless the commit is still available locally).

This breaks usage in abs, but more importantly for me it makes it impossible to use the same commit for
https://aur.archlinux.org/packages/lib32-libx264/ (discussion was started on AUR 3, PKGBUILD also on AUR 4)

I would recommend to never use x264-sandbox.git since it is not stable and rather use x264.git together with a patch (if necessary).

Steps to reproduce:

copy PKGBUILD of x264 into a new (empty!) directory and "makepkg -c" yields:
==> Extracting sources...
-> Creating working copy of x264-sandbox git repo...
fatal: Cannot update paths and switch to branch 'makepkg' at the same time.
Did you intend to checkout 'e6d2a36bb' which can not be resolved as commit?
==> ERROR: Failure while creating working copy of x264-sandbox git repo
This task depends upon

Closed by  Maxime Gauduin (Alucryd)
Tuesday, 28 July 2015, 21:59 GMT
Reason for closing:  Fixed
Additional comments about closing:  2:148.20150725-1
Comment by Johannes Dewender (JonnyJD) - Monday, 27 July 2015, 20:06 GMT
I do have a local repository where the commit still exists and checked the logs.
According to that there is an equivalent (but probably rebased) commit now at x264.git:
Comment by Maxime Gauduin (Alucryd) - Tuesday, 28 July 2015, 21:58 GMT
Learned afterwards that the sandbox repo was subject to some push --force. Switched back to using the regular repo.