Re: pkg: fetching binary packages to a local dumpdir for a different ABI
Mathieu Arnold wrote on 03/11/2016 18:26:
+--On 11 mars 2016 13:04:11 +0100 Miroslav Lachman <000.f...@quip.cz> wrote:
| Matthew Seaman wrote on 03/11/2016 12:15:
|> On 03/11/16 10:00, Miroslav Lachman wrote:
|>> O. Hartmann wrote on 03/11/2016 10:42:
|>>
|>> [...]
|>>
|>>> The ABI is also unclear. Some documents say it is freebsd:10:x86:64
|>>> (which
|>>> looks more the Intel/Linux dominated terminology) and also this one is
|>>> considered correct: FreeBSD:10:amd64 (looks more FreeBSD'ish). It is
|>>> said that
|>>> the variable ABI is derived from "sh" - how?
|>>
|>> It is freebsd:10:x86:64. You can look at http://pkg.freebsd.org/
|>> The full URL is http://pkg.freebsd.org/freebsd:10:x86:64/
|>
|> Actually, ${ABI} *used* to be freebsd:10:x86:64. It changed to
|> FreeBSD:10:amd64 quite some time and numerous releases of pkg(8) ago now.
|
| It's strange that it is not listed at mirror page http://pkg.freebsd.org/
| There are only old ABI formats.
I knew putting a web server behind pkg.freebsd.org, and putting an index
page there was a bad idea, now people go there, and look at it.
I think it is useful. We can browse the packages for different versions
and architectures. It just needs update for current ABI format. It is
always better to show some content then act like a black box full of
magic :)
(the mentioned mirror supports both if I tried the URL by hand, but does
not mention it on the index)
Miroslav Lachman
___
freebsd-ports@freebsd.org mailing list
https://lists.freebsd.org/mailman/listinfo/freebsd-ports
To unsubscribe, send any mail to "freebsd-ports-unsubscr...@freebsd.org"
Re: pkg: fetching binary packages to a local dumpdir for a different ABI
+--On 11 mars 2016 13:04:11 +0100 Miroslav Lachman <000.f...@quip.cz> wrote:
| Matthew Seaman wrote on 03/11/2016 12:15:
|> On 03/11/16 10:00, Miroslav Lachman wrote:
|>> O. Hartmann wrote on 03/11/2016 10:42:
|>>
|>> [...]
|>>
|>>> The ABI is also unclear. Some documents say it is freebsd:10:x86:64
|>>> (which
|>>> looks more the Intel/Linux dominated terminology) and also this one is
|>>> considered correct: FreeBSD:10:amd64 (looks more FreeBSD'ish). It is
|>>> said that
|>>> the variable ABI is derived from "sh" - how?
|>>
|>> It is freebsd:10:x86:64. You can look at http://pkg.freebsd.org/
|>> The full URL is http://pkg.freebsd.org/freebsd:10:x86:64/
|>
|> Actually, ${ABI} *used* to be freebsd:10:x86:64. It changed to
|> FreeBSD:10:amd64 quite some time and numerous releases of pkg(8) ago now.
|
| It's strange that it is not listed at mirror page http://pkg.freebsd.org/
| There are only old ABI formats.
I knew putting a web server behind pkg.freebsd.org, and putting an index
page there was a bad idea, now people go there, and look at it.
--
Mathieu Arnold
pgpoPWScjsNm6.pgp
Description: PGP signature
Re: pkg: fetching binary packages to a local dumpdir for a different ABI
Am Fri, 11 Mar 2016 11:00:28 +0100 Miroslav Lachman <000.f...@quip.cz> schrieb: > O. Hartmann wrote on 03/11/2016 10:42: > > [...] > > > The ABI is also unclear. Some documents say it is freebsd:10:x86:64 (which > > looks more the Intel/Linux dominated terminology) and also this one is > > considered correct: FreeBSD:10:amd64 (looks more FreeBSD'ish). It is said > > that > > the variable ABI is derived from "sh" - how? > > It is freebsd:10:x86:64. You can look at http://pkg.freebsd.org/ > The full URL is http://pkg.freebsd.org/freebsd:10:x86:64/ > > Miroslav Lachman Thank you very much. Kind regards, O. Hartmann pgpc_x1O3B2bT.pgp Description: OpenPGP digital signature
Re: pkg: fetching binary packages to a local dumpdir for a different ABI
On 2016/03/11 12:04, Miroslav Lachman wrote:
> Matthew Seaman wrote on 03/11/2016 12:15:
>> On 03/11/16 10:00, Miroslav Lachman wrote:
>>> O. Hartmann wrote on 03/11/2016 10:42:
>>>
>>> [...]
>>>
The ABI is also unclear. Some documents say it is freebsd:10:x86:64
(which
looks more the Intel/Linux dominated terminology) and also this one is
considered correct: FreeBSD:10:amd64 (looks more FreeBSD'ish). It is
said that
the variable ABI is derived from "sh" - how?
>>>
>>> It is freebsd:10:x86:64. You can look at http://pkg.freebsd.org/
>>> The full URL is http://pkg.freebsd.org/freebsd:10:x86:64/
>>
>> Actually, ${ABI} *used* to be freebsd:10:x86:64. It changed to
>> FreeBSD:10:amd64 quite some time and numerous releases of pkg(8) ago now.
>
> It's strange that it is not listed at mirror page
> http://pkg.freebsd.org/ There are only old ABI formats.
Yeah. But that page also mentions packages for 8.x which is now well
out of support. I believe that the official package mirrors have been
set up to work with both variants of the ABI string, and the page you
reference simply hasn't been updated for a while.
Cheers,
Matthew
signature.asc
Description: OpenPGP digital signature
Re: pkg: fetching binary packages to a local dumpdir for a different ABI
Matthew Seaman wrote on 03/11/2016 12:15:
On 03/11/16 10:00, Miroslav Lachman wrote:
O. Hartmann wrote on 03/11/2016 10:42:
[...]
The ABI is also unclear. Some documents say it is freebsd:10:x86:64
(which
looks more the Intel/Linux dominated terminology) and also this one is
considered correct: FreeBSD:10:amd64 (looks more FreeBSD'ish). It is
said that
the variable ABI is derived from "sh" - how?
It is freebsd:10:x86:64. You can look at http://pkg.freebsd.org/
The full URL is http://pkg.freebsd.org/freebsd:10:x86:64/
Actually, ${ABI} *used* to be freebsd:10:x86:64. It changed to
FreeBSD:10:amd64 quite some time and numerous releases of pkg(8) ago now.
It's strange that it is not listed at mirror page
http://pkg.freebsd.org/ There are only old ABI formats.
Miroslav Lachman
___
freebsd-ports@freebsd.org mailing list
https://lists.freebsd.org/mailman/listinfo/freebsd-ports
To unsubscribe, send any mail to "freebsd-ports-unsubscr...@freebsd.org"
Re: pkg: fetching binary packages to a local dumpdir for a different ABI
On 03/11/16 09:42, O. Hartmann wrote:
> The process will require 4 GiB more space.
> 4 GiB to be downloaded.
> Fetching pkg-1.6.4_1.txz: 100%3 MiB 562.3kB/s00:05
> pkg-static: cached package pkg-1.6.4_1: size mismatch, fetching from remote
> Fetching pkg-1.6.4_1.txz: 100%3 MiB 562.3kB/s00:05
> pkg-static: cached package pkg-1.6.4_1: size mismatch, cannot continue
>
> Well, it seems clear - somewhere (on that specific box nowhere!) is a cache
> and
> the size-hash is compared - but where? The list in pkglist contains also
> ports-mgmt/pkg and it is the first package to be fetched.
At a guess you're mixing packages from one architecture with the package
catalogue from a different one.
You can achieve what you want, but you should use a tailored
${LOCALBASE}/etc/pkg.conf with custom settings for ABI, PKG_CACHEDIR and
PKG_DBDIR.
In principle it is possible to install packages for a foreign
architecture using this sort of setup: that's what the '-R' flag to
pkg(8) is all about -- so you can build a system image for a foreign
arch on eg. a micro SD card you've mounted onto your filesystem but be
able to store its package database and caches offline.
Cheers,
Matthew
signature.asc
Description: OpenPGP digital signature
Re: pkg: fetching binary packages to a local dumpdir for a different ABI
On 03/11/16 10:00, Miroslav Lachman wrote:
> O. Hartmann wrote on 03/11/2016 10:42:
>
> [...]
>
>> The ABI is also unclear. Some documents say it is freebsd:10:x86:64
>> (which
>> looks more the Intel/Linux dominated terminology) and also this one is
>> considered correct: FreeBSD:10:amd64 (looks more FreeBSD'ish). It is
>> said that
>> the variable ABI is derived from "sh" - how?
>
> It is freebsd:10:x86:64. You can look at http://pkg.freebsd.org/
> The full URL is http://pkg.freebsd.org/freebsd:10:x86:64/
Actually, ${ABI} *used* to be freebsd:10:x86:64. It changed to
FreeBSD:10:amd64 quite some time and numerous releases of pkg(8) ago now.
The ABI is usually determined by examining the binary of /bin/sh --
chosen because /bin/sh is likely to be present even on the most cut-down
jail. It works vaguely similarly to the way file(1) does:
% file /bin/sh
/bin/sh: ELF 64-bit LSB executable, x86-64, version 1 (FreeBSD),
dynamically linked, interpreter /libexec/ld-elf.so.1, for FreeBSD 10.2
(1002509), stripped
although there's no common code history between file(1) and pkg(8). If
you feel like reading some C code, look at
https://github.com/freebsd/pkg/blob/master/libpkg/pkg_elf.c#L691
-- the functions pkg_get_myarch_elfparse() and pkg_get_myarch() at line
964 are what does the job.
Cheers,
Matthew
signature.asc
Description: OpenPGP digital signature
Re: pkg: fetching binary packages to a local dumpdir for a different ABI
O. Hartmann wrote on 03/11/2016 10:42: [...] The ABI is also unclear. Some documents say it is freebsd:10:x86:64 (which looks more the Intel/Linux dominated terminology) and also this one is considered correct: FreeBSD:10:amd64 (looks more FreeBSD'ish). It is said that the variable ABI is derived from "sh" - how? It is freebsd:10:x86:64. You can look at http://pkg.freebsd.org/ The full URL is http://pkg.freebsd.org/freebsd:10:x86:64/ Miroslav Lachman ___ freebsd-ports@freebsd.org mailing list https://lists.freebsd.org/mailman/listinfo/freebsd-ports To unsubscribe, send any mail to "freebsd-ports-unsubscr...@freebsd.org"
pkg: fetching binary packages to a local dumpdir for a different ABI
On CURRENT, I try to "silly fetch" a selection of binary packages for FreeBSD 10-STABLE from a regular user via this command sequence: env ABI=freebsd:10:x86:64 PKG_CACHEDIR=./tmp/packages/cache \ REPOS_DIR=./tmp/packages cat /usr/local/etc/poudriere.d/pkglist | \ xargs pkg fetch -y -U -d -o ./tmp/packages/ pkg trie to fecth, but then it simply complains about crap being fetched: [...] The process will require 4 GiB more space. 4 GiB to be downloaded. Fetching pkg-1.6.4_1.txz: 100%3 MiB 562.3kB/s00:05 pkg-static: cached package pkg-1.6.4_1: size mismatch, fetching from remote Fetching pkg-1.6.4_1.txz: 100%3 MiB 562.3kB/s00:05 pkg-static: cached package pkg-1.6.4_1: size mismatch, cannot continue Well, it seems clear - somewhere (on that specific box nowhere!) is a cache and the size-hash is compared - but where? The list in pkglist contains also ports-mgmt/pkg and it is the first package to be fetched. How can I force package to download "brutal force" the specified package for the desired ABI? Background: since poudriere fails building packages (especially lang/python27, see my posts prior to this) within a 10-stable jail running on CURRENT (maybe this doesn't work, but I didn't find anything regarding this on the rush), I'd like to have a set of packages for installation on some 10-STABLE appliance images. The ABI is also unclear. Some documents say it is freebsd:10:x86:64 (which looks more the Intel/Linux dominated terminology) and also this one is considered correct: FreeBSD:10:amd64 (looks more FreeBSD'ish). It is said that the variable ABI is derived from "sh" - how? Many thanks in advance, Oliver P.S. Please CC me - I'm not subscribing this specific list. Thank you. ___ freebsd-ports@freebsd.org mailing list https://lists.freebsd.org/mailman/listinfo/freebsd-ports To unsubscribe, send any mail to "freebsd-ports-unsubscr...@freebsd.org"
