[Dev] help on building packer

Aurélien DESBRIÈRES aurelien at hackers.camp
Thu Dec 11 18:30:00 GMT 2014


André Silva <emulatorman at riseup.net> writes:

> On 12/11/2014 03:55 AM, Aurélien DESBRIÈRES wrote:
>> André Silva <emulatorman at riseup.net> writes:
>> 
>>> On 12/10/2014 04:41 PM, Aurélien DESBRIÈRES wrote:
>>>> 
>>>> Anyone can please remove packer from repo.
>>>> 
>>>> I need to rebuild it and repush it ... but ::
>>>> 
>>>> [uncle at bob packer]$ sudo libremakepkg ==> Initializing the 
>>>> chroot... ==> Starting pre-build activities... |  ==>
>>>> Downloading blacklist of proprietary software packages...done |
>>>> -> Inspecting package pkgname=packer (20140810-1) ==>
>>>> Downloading sources... |  ==> Making package: packer 20140810-1
>>>> (Wed Dec 10 19:38:07 CET 2014) |  ==> Retrieving sources... |
>>>> -> Updating packer git repo... |  Fetching origin |  ==>
>>>> Validating source files with md5sums... |      packer ...
>>>> Skipped ==> Starting to build the package... |  ==> Making
>>>> package: packer 20140810-1 (Wed Dec 10 19:38:09 CET 2014) |
>>>> ==> Checking runtime dependencies... | ==> Checking buildtime
>>>> dependencies... |  ==> Retrieving sources... |    -> Updating
>>>> packer git repo... |  error: cannot open FETCH_HEAD: Read-only
>>>> file system | |  ==> WARNING: Failure while updating packer git
>>>> repo |  ==> Validating source files with md5sums... |
>>>> packer ... Skipped |  ==> Extracting sources... | -> Creating
>>>> working copy of packer git repo... |  Cloning into 'packer'...
>>>> |  done. |  ==> Starting pkgver()... |  ==> Updated version:
>>>> packer 20140817-1 |  ==> Sources are ready. |  ==> Cleaning
>>>> chroot... |    -> Creating a full list of packages... | -> No
>>>> packages to remove |  ==> Making package: packer 20140817-1 | 
>>>> (Wed Dec 10 19:38:11 CET 2014) |  ==> Checking runtime 
>>>> dependencies... |  ==> Checking buildtime dependencies... |
>>>> ==> WARNING: Using existing src/ tree |  ==> Entering fakeroot 
>>>> environment... |  ==> Starting package()... |  ==> Tidying 
>>>> install... |    -> Purging unwanted files... |    -> Removing 
>>>> libtool files... |    -> Removing static library files... |
>>>> -> Compressing man and info pages... |    -> Stripping
>>>> unneeded symbols from |  binaries and libraries... |  ==>
>>>> Creating package "packer"... |    -> Generating .PKGINFO
>>>> file... |    -> Generating .MTREE file... |    -> Compressing
>>>> package... |  ==> Leaving fakeroot environment. |  ==> Finished
>>>> making: packer 20140817-1 (Wed |  Dec 10 19:38:11 CET 2014) ==>
>>>> Starting post-build activities... |  ==> Extracting database to
>>>> a temporary location... |  ==> Adding package | 
>>>> 'packer-20140817-1-any.pkg.tar.xz' |    -> Computing
>>>> checksums... | -> Creating 'desc' db entry... |    -> Creating
>>>> 'depends' db entry... |  ==> Creating updated database file |
>>>> 'repo.db.tar.gz' ==> Copying log and package files out of the
>>>> chroot... [uncle at bob packer]$ librestage pcr fatal: Not a git
>>>> repository (or any parent up to mount |  point /home) Stopping
>>>> at filesystem boundary | (GIT_DISCOVERY_ACROSS_FILESYSTEM not
>>>> set). ==> ERROR: Nothing was staged
>>>> 
>>>> 
>>>> or maybe that does not comes from that ?
>>> 
>>> I've built a new version of packer, test it if works well 
>>> _______________________________________________ Dev mailing list 
>>> Dev at lists.parabola.nu 
>>> https://lists.parabola.nu/mailman/listinfo/dev
>>> 
>> <#secure method=pgpmime mode=sign>
>> 
>> That does not explain to me from where come the trouble during the 
>> build, but thanks.
>> 
> The problem related it was because you built packer under 20140810
> version, but how it is a git so packer was built as 20140817 because
> was the date that you built it, so i put a automatic date to pkgver
> [0] to solve it.
>
> [0]:https://projects.parabola.nu/abslibre.git/commit/?id=df2d8d4f7b6c6dbf1d8d767d12f74fa596241a6b

<#secure method=pgpmime mode=sign>

Ok ok!

Thanks :-)

-- 
Aurelien Desbrieres
http://www.hackers.camp



More information about the Dev mailing list