Re: [ptxdist] ptxdist: support podman

2019-10-15 Thread Andreas Friesen 
Hi

> I am currently migrating our containerized CI pipelines from docker (moby) to
> podman as it's more secure[1]. But ptxdist refuse to run as "root", but in 
> reality
> it's running with less privileges then the user that started it.
>
> ptxdist: error: refusing to run PTXdist as root

Yesterday I had the same problem, but with docker container...

creating a buildbot user solves the problem:

--8<--- Dockefile
FROM ubuntu:18.04
...

RUN groupadd -r buildbot && useradd -r -g buildbot buildbot -m -d /buildbot
USER buildbot
## END
-->8--- Dockerfile

> Is it possible to do an extra podman check?
>
> I found "/run/.containerenv" documented as an official flag to detect that a 
> program
> is in a container.
>
> Bruno
>
> [1] 
> https://eur01.safelinks.protection.outlook.com/?url=https%3A%2F%2Fcloudnweb.dev%2F2019%2F06%2Freplacing-docker-with-podman-power-of-podman%2Fdata=02%7C01%7Candreas.friesen%40hbkworld.com%7Cb1fdce80d12a425cb8d808d7517496dd%7C6cce74a3397545e09893b072988b30b6%7C0%7C1%7C637067433499587697sdata=ElDMLtqmeC0MCpolB%2FJBOY4ychVC0nZLilAPXqPSZAo%3Dreserved=0
> [2] 
> https://eur01.safelinks.protection.outlook.com/?url=https%3A%2F%2Fgithub.com%2Fcontainers%2Flibpod%2Fblob%2Fmaster%2Fdocs%2Fpodman-run.1.mddata=02%7C01%7Candreas.friesen%40hbkworld.com%7Cb1fdce80d12a425cb8d808d7517496dd%7C6cce74a3397545e09893b072988b30b6%7C0%7C1%7C637067433499587697sdata=%2FiB%2Bm9OI18uE8Tq0FH%2FHpJ8DeX0ZTEZ%2F0sLmNzDlFxQ%3Dreserved=0
> ___________
> ptxdist mailing list
> ptxdist@pengutronix.de


--
Andreas Friesen
R Embedded Control Software
Tel.   : +49 6151-803445
Fax: +49 6151-8039445
E-Mail : andreas.frie...@hbkworld.com
Web: www.hbkworld.com
Hottinger Baldwin Messtechnik GmbH, Im Tiefen See 45, 64293 Darmstadt, Germany 
| www.hbm.com Registered as GmbH (German limited liability corporation) in the 
commercial register at the local court of Darmstadt, HRB 1147 Company domiciled 
in Darmstadt | Managing Directors: Thomas Lippok & Jens Wiegand | Chairman of 
the board: Joe Vorih Als Gesellschaft mit beschränkter Haftung eingetragen im 
Handelsregister des Amtsgerichts Darmstadt unter HRB 1147 Sitz der 
Gesellschaft: Darmstadt | Geschäftsführung: Thomas Lippok & Jens Wiegand | 
Aufsichtsratsvorsitzender: Joe Vorih The information in this email is 
confidential. It is intended solely for the addressee. If you are not the 
intended recipient, please let me know and delete this email. Die in dieser 
E-Mail enthaltene Information ist vertraulich und lediglich für den Empfänger 
bestimmt. Sollten Sie nicht der eigentliche Empfänger sein, informieren Sie 
mich bitte kurz und löschen diese E-Mail.

___
ptxdist mailing list
ptxdist@pengutronix.de

Re: [ptxdist] How to create multiple packages, which contain same filename ?

2018-12-14 Thread Andreas Friesen 
Hi Florian,

I added some randomized sleeps to *.install rules.  It works for now, but
its realy ugly.

Best Regards,
Andreas.

Am Di., 11. Dez. 2018 um 12:14 Uhr schrieb Baeuerle, Florian <
florian.baeue...@allegion.com>:

> Hi Andreas,
>
> maybe you can confirm if this assumption is correct:
>
> You are using image packages with your collections to create rootfs images
> for
> your three different variants.
>
> If so, then this probably the root cause:
>
> ptxdist has this "nfsroot" feature. By default, it installs everything into
> $build/root. This is a bit problematic when using image packages, because
> it
> will install all your variant packages in parallel. This leads to races
> where
> variant-1 wants to install and chmod a file, but shortly before variant-1's
> targetinstall wants to chmod the file, variant-2 replaces it.
>
> Additionally, the content of the nfsroot are not really predictable.
>
> There is currently no option to disable nfsroot (wouldn't be a problem
> anyway,
> because for image packages you can have an nfsroot for each root image you
> create). I want to submit a patch (well, at some point...).
>
> If you just need a short workaround, you can place sleeps into your image
> packages .targetinstall stages (That's what I do).
>
> variant-1: no sleeping
> variant-2: sleep 1
> variant-3: sleep 2
>
> It's just an ugly workaround and it can still fail.
>
> Feel free to go ahead and submit a patch, proposal #1 or #2 to fix the
> issue
> probably have chance to get accepted:
> https://www.mail-archive.com/ptxdist@pengutronix.de/msg13614.html
>
>
> Best Regards
> Florian
>
> Am Dienstag, den 11.12.2018, 11:59 +0100 schrieb Andreas Friesen:
> > Hi Florian,
> >
> > ptxdist reports me after workspace clean this error (see below). This is
> > always first targetinstall  one of the above mentioned packages. The
> build
> > order seems to be random.
> > After repetition of "ptxdist go -j -q " is the build OK.  Who create
> /boot in
> > root ? Or witch /boot  is meant ?  What is wrong ?
> >
> > -
>
> >
>
> >
> >  target: fpgaimage-cx27c.targetinstall
>
> >
>
> >
> >  -
>
> >
>
> >
> >
>
> >
>
> >
> > install_init:   preparing for image creation of 'fpgaimage-cx27c'...
>
> >
>
> >
> > 
>
> >
> > xpkg_finish:creating opkg package ...
>
> >
>
> >
> >
>
> >
>
> >
> > install file:
>
> >
>
> >
> >
>  src=ptx-multi/projectroot/lib/firmware/fpga_complete/soc_system_cx27c.rbf
>
> >
>
> >
> > dst=/boot/fpgaimage.rbf
>
> >
>
> >
> >   owner=0
>
> >
>
> >
> > group=0
>
> >
>
> >
> >   permissions=0755
>
> >
>
> >
> >
>
> >
>
> >
> > chmod: cannot access
> '/home/friesen/quantumx/projects/ppc/ptx-multi/platform-
> > soc/root/boot/fpgaimage.rbf': No such file or directory
>
> >
> > Error: install_file failed!
>
> >
>
> >
> >
>
> >
>
> >
> > xpkg_finish: failed.
>
> >
>
> >
> >
>
> >
>
> >
> >
> /home/friesen/quantumx/projects/ppc/ptx-multi/rules/fpgaimage-cx27c.make:12:
> > recipe for target
> '/home/friesen/quantumx/projects/ppc/ptx-multi/platform-
> > soc/state/fpgaimage-cx27c.targetinstall' failed
> > make: *** [/home/friesen/quantumx/projects/ppc/ptx-multi/platform-
> > soc/state/fpgaimage-cx27c.targetinstall] Error 1
>
> >
> > make: *** Waiting for unfinished jobs
>
> >
>
> >
> >
>
> >
> >
> > Am Di., 11. Dez. 2018 um 09:58 Uhr schrieb Baeuerle, Florian <
> > florian.baeue...@allegion.com>:
> > > Hi Andreas,
> > >
> > > this use case is supported by ptxdist, actually quite exactly as you
> planned
> > > it.
> > >
> > > You will eventually run into this issue:
> > >
> > > https://www.mail-archive.com/ptxdist@pengutronix.de/msg13611.html
> > >
> > > But probably only if you use image packages for creating your three
> rootfses
> > > at
> > > the same time (saves a lot of build time btw).
> > >
> > >
> > > Best Regards
> > > Florian
> > >
> > > Am Donnerstag, den 06.12.2018, 12:49 +0100 schrieb Andreas Friesen:
> > > > Hello everyone,
>

Re: [ptxdist] How to create multiple packages, which contain same filename ?

2018-12-11 Thread Andreas Friesen 
Hi Florian,

ptxdist reports me after workspace clean this error (see below). This is
always first targetinstall  one of the above mentioned packages. The build
order seems to be random.
After repetition of "ptxdist go -j -q " is the build OK.  Who create /boot
in root ? Or witch /boot  is meant ?  What is wrong ?

-


 target: fpgaimage-cx27c.targetinstall


 -





install_init:   preparing for image creation of 'fpgaimage-cx27c'...




xpkg_finish:creating opkg package ...





install file:



src=ptx-multi/projectroot/lib/firmware/fpga_complete/soc_system_cx27c.rbf


dst=/boot/fpgaimage.rbf


  owner=0


group=0


  permissions=0755





chmod: cannot access
'/home/friesen/quantumx/projects/ppc/ptx-multi/platform-soc/root/boot/fpgaimage.rbf':
No such file or directory

Error: install_file failed!





xpkg_finish: failed.





/home/friesen/quantumx/projects/ppc/ptx-multi/rules/fpgaimage-cx27c.make:12:
recipe for target
'/home/friesen/quantumx/projects/ppc/ptx-multi/platform-soc/state/fpgaimage-cx27c.targetinstall'
failed
make: ***
[/home/friesen/quantumx/projects/ppc/ptx-multi/platform-soc/state/fpgaimage-cx27c.targetinstall]
Error 1

make: *** Waiting for unfinished jobs





Am Di., 11. Dez. 2018 um 09:58 Uhr schrieb Baeuerle, Florian <
florian.baeue...@allegion.com>:

> Hi Andreas,
>
> this use case is supported by ptxdist, actually quite exactly as you
> planned it.
>
> You will eventually run into this issue:
>
> https://www.mail-archive.com/ptxdist@pengutronix.de/msg13611.html
>
> But probably only if you use image packages for creating your three
> rootfses at
> the same time (saves a lot of build time btw).
>
>
> Best Regards
> Florian
>
> Am Donnerstag, den 06.12.2018, 12:49 +0100 schrieb Andreas Friesen:
> > Hello everyone,
> >
> > we've got many module types, each module type  builds on same platform. I
> > would like create a generic barebox environment for all module types.
> >
> > My problem is, that ptxdist  don't like packages, which contain same
> filename.
> > My plan was to create several packages :
> >
> > - firmware-Type-A.ipkg (contains /boot/{fpga.bin,platform.dtb)
> > - firmware-Type-B.ipkg (contains  /boot/{fpga.bin,platform.dtb)
> > - firmware-Type-C.ipkg (contains  /boot/{fpga.bin,platform.dtb)
> >
> > And each module install via" collection" the respective package.
> >
> > What can I do ? I would like to avoid having foreign components in the
> > firmware package.
> >
> > Regards,
> > Andreas Friesen
> > ___
> > ptxdist mailing list
> > ptxdist@pengutronix.de
> ___
> ptxdist mailing list
> ptxdist@pengutronix.de


fpgaimage-cx27c.make
Description: Binary data


collectionconfig.cx27c
Description: Binary data


quantumx-cx27c.in
Description: Binary data
___
ptxdist mailing list
ptxdist@pengutronix.de

[ptxdist] How to create multiple packages, which contain same filename ?

2018-12-06 Thread Andreas Friesen 
Hello everyone,

we've got many module types, each module type  builds on same platform. I
would like create a generic barebox environment for all module types.

My problem is, that ptxdist  don't like packages, which contain same
filename. My plan was to create several packages :

- firmware-Type-A.ipkg (contains /boot/{fpga.bin,platform.dtb)
- firmware-Type-B.ipkg (contains  /boot/{fpga.bin,platform.dtb)
- firmware-Type-C.ipkg (contains  /boot/{fpga.bin,platform.dtb)

And each module install via" collection" the respective package.

What can I do ? I would like to avoid having foreign components in the
firmware package.

Regards,
Andreas Friesen
___
ptxdist mailing list
ptxdist@pengutronix.de

Re: [ptxdist] rootfs: package

2018-12-04 Thread Andreas Friesen 
Great ! It's works now!
Many Thanks, Michael for support.




Am Di., 4. Dez. 2018 um 14:39 Uhr schrieb Michael Olbrich <
m.olbr...@pengutronix.de>:

> On Tue, Dec 04, 2018 at 02:25:15PM +0100, Andreas Friesen wrote:
> > Also I extracted my opkg.conf from ptxdist after little hack in
> >
> /usr/local/lib/ptxdist-2018.11.0/scripts/lib/ptxd_make_image_prepare_work_dir.sh
> >
> > ptxd_make_image_extract_xpkg_files() {
> > ...
> > cat "${xpkg_conf}" > /tmp/opkg.conf &&
> > ..
> > }
> >
> >
> > ââ[$] <> cat opkg.conf
> > option force_postinstall 1
> > #
> > # /etc/opkg/opkg.conf
> > #
> > src/gz willi http://willi.devel.hbm.com/clipx/soc-packages
> > dest root /
> > arch armhf 10
> > arch all 1
> > arch noarch 1
> > option check_signature 0
> > #option signature_ca_path /etc/ssl/certs
> > #option signature_ca_file /etc/ssl/certs/opkg.crt
>
> This is generated from projectroot/etc/opkg/opkg.conf. I expect you have
> one in your BSP. You need to add the lock_file option there.
>
> Michael
>
> --
> Pengutronix e.K.   | |
> Industrial Linux Solutions | http://www.pengutronix.de/  |
> Peiner Str. 6-8, 31137 Hildesheim, Germany | Phone: +49-5121-206917-0|
> Amtsgericht Hildesheim, HRA 2686   | Fax:   +49-5121-206917- |
>
> ___
> ptxdist mailing list
> ptxdist@pengutronix.de
___
ptxdist mailing list
ptxdist@pengutronix.de

Re: [ptxdist] rootfs: package

2018-12-04 Thread Andreas Friesen 
Also I extracted my opkg.conf from ptxdist after little hack in
/usr/local/lib/ptxdist-2018.11.0/scripts/lib/ptxd_make_image_prepare_work_dir.sh

ptxd_make_image_extract_xpkg_files() {
...
cat "${xpkg_conf}" > /tmp/opkg.conf &&
..
}


ââ[$] <> cat opkg.conf
option force_postinstall 1
#
# /etc/opkg/opkg.conf
#
src/gz willi http://willi.devel.hbm.com/clipx/soc-packages
dest root /
arch armhf 10
arch all 1
arch noarch 1
option check_signature 0
#option signature_ca_path /etc/ssl/certs
#option signature_ca_file /etc/ssl/certs/opkg.crt



Am Di., 4. Dez. 2018 um 13:58 Uhr schrieb Michael Olbrich <
m.olbr...@pengutronix.de>:

> On Tue, Dec 04, 2018 at 01:47:45PM +0100, Andreas Friesen wrote:
> > DESTDIR="/home/friesen/rootfs/rootfs0"  strace -orootfs.log  opkg -f
> > "/home/friesen/rootfs/opkg.conf" -o "/home/friesen/rootfs/rootfs0/"
> install
> > rootfs_1.0.0_armhf.ipk
> > ââ[$] <> cat rootfs.log| grep run
> [...]
> > mkdir("/home/friesen/rootfs/rootfs0///usr/local/var/run", 0777) = 0
> > chmod("/home/friesen/rootfs/rootfs0///usr/local/var/run", 0755) = 0
> > creat("/home/friesen/rootfs/rootfs0///usr/local/var/run/opkg.lock",
> 0640) =
> > 4
> [...]
> > DESTDIR="/home/friesen/rootfs/rootfs" strace -orootfs0.log
> >
> /home/friesen/gitlab/quantumx-master/projects/ppc/ptx-multi/platform-soc/sysroot-host/bin/opkg
> > -f "/home/friesen/rootfs/opkg.conf" -o "/home/friesen/rootfs/rootfs/"
> > install  rootfs_1.0.0_armhf.ipk
> > ââ[$] <> cat rootfs0.log| grep run
> [...]
> > mkdir("/home/friesen/rootfs/rootfs///var/run", 0777) = 0
> > chmod("/home/friesen/rootfs/rootfs///var/run", 0755) = 0
> > creat("/home/friesen/rootfs/rootfs///var/run/opkg.lock", 0640) = 4
>
> The opkg.conf template contains this:
>
> option  lock_file /var/lock/opkg.lock
>
> As a result, the lock file is created there and I don't see this error.
> I'm guessing, that you have a custom opkg.conf without this entry.
> You need to add it with a path outside of /var/run.
>
> Michael
>
> --
> Pengutronix e.K.   | |
> Industrial Linux Solutions | http://www.pengutronix.de/  |
> Peiner Str. 6-8, 31137 Hildesheim, Germany | Phone: +49-5121-206917-0|
> Amtsgericht Hildesheim, HRA 2686   | Fax:   +49-5121-206917- |
>
> ___
> ptxdist mailing list
> ptxdist@pengutronix.de
___
ptxdist mailing list
ptxdist@pengutronix.de

Re: [ptxdist] rootfs: package

2018-12-04 Thread Andreas Friesen 
Here as attachment config.log files

--- ptxdist opkg config.log
  $ ./configure --prefix= --disable-libopkg-api --disable-static
--disable-pathfinder --disable-xz --disable-bzip2 --disable-curl
--disable-sha256 --disable-openssl --disable-ssl-curl --disable-gpg
--without-l
ibsolv --without-static-libopkg

## - ##
## Platform. ##
## - ##

hostname = sumo
uname -m = x86_64
uname -r = 4.19.4-arch1-1-ARCH
uname -s = Linux
uname -v = #1 SMP PREEMPT Fri Nov 23 09:06:58 UTC 2018

-- my opkg config.log


  $ ./configure

## - ##
## Platform. ##
## - ##

hostname = sumo
uname -m = x86_64
uname -r = 4.19.4-arch1-1-ARCH
uname -s = Linux
uname -v = #1 SMP PREEMPT Fri Nov 23 09:06:58 UTC 2018



Am Di., 4. Dez. 2018 um 12:47 Uhr schrieb Andreas Friesen :

> Also rootfs and rootfs0 exists not!
>
> $ DESTDIR="/home/friesen/rootfs/rootfs"
> /home/friesen/gitlab/quantumx-master/projects/ppc/ptx-multi/platform-soc/sysroot-host/bin/opkg
> -f "/home/friesen/rootfs/opkg.conf" -o "/home/friesen/rootfs/rootfs/"
> install  rootfs_1.0.0_armhf.ipk
> Installing rootfs (1.0.0) on root.
> To remove package debris, try `opkg remove rootfs`.
> To re-attempt the install, try `opkg install rootfs`.
> Collected errors:
>  * check_data_file_clashes: Package rootfs wants to install file
> /home/friesen/rootfs/rootfs//var/run
> But that path is currently a directory
>  * opkg_solver_install: Cannot install package rootfs.
>
> [$] <> ls -all rootfs/var
> total 20
> drwxr-xr-x 5 friesen friesen 4096 Dec  4 12:42 .
> drwxr-xr-x 3 friesen friesen 4096 Dec  4 12:42 ..
> drwxr-xr-x 3 friesen friesen 4096 Dec  4 12:42 cache
> drwxr-xr-x 3 friesen friesen 4096 Dec  4 12:42 lib
> drwxr-xr-x 2 friesen friesen 4096 Dec  4 12:42 run  <-- ! is a
> directory
>
>
> DESTDIR="/home/friesen/rootfs/rootfs0"  opkg -f
> "/home/friesen/rootfs/opkg.conf" -o "/home/friesen/rootfs/rootfs0/" install
> rootfs_1.0.0_armhf.ipk
> Installing rootfs (1.0.0) on root.
>
>
> Warning when extracting archive entry
> '/home/friesen/rootfs/rootfs0//proc/': Can't set UID=0
> Warning when extracting archive entry
> '/home/friesen/rootfs/rootfs0//mnt/': Can't set UID=0
> Warning when extracting archive entry
> '/home/friesen/rootfs/rootfs0//sys/': Can't set UID=0
> Warning when extracting archive entry
> '/home/friesen/rootfs/rootfs0//etc/': Can't set UID=0
> Warning when extracting archive entry
> '/home/friesen/rootfs/rootfs0//etc/profile': Can't set UID=0
> Warning when extracting archive entry
> '/home/friesen/rootfs/rootfs0//etc/resolv.conf': Can't set UID=0
> Warning when extracting archive entry
> '/home/friesen/rootfs/rootfs0//etc/hostname': Can't set UID=0
> Warning when extracting archive entry
> '/home/friesen/rootfs/rootfs0//etc/group': Can't set UID=0
> Warning when extracting archive entry
> '/home/friesen/rootfs/rootfs0//etc/issue': Can't set UID=0
> Warning when extracting archive entry
> '/home/friesen/rootfs/rootfs0//etc/passwd': Can't set UID=0
> Warning when extracting archive entry
> '/home/friesen/rootfs/rootfs0//etc/shadow': Can't set UID=0
> Warning when extracting archive entry
> '/home/friesen/rootfs/rootfs0//etc/nsswitch.conf': Can't set UID=0
> Warning when extracting archive entry
> '/home/friesen/rootfs/rootfs0//etc/mtab': Can't set UID=0
> Warning when extracting archive entry
> '/home/friesen/rootfs/rootfs0//etc/services': Can't set UID=0
> Warning when extracting archive entry
> '/home/friesen/rootfs/rootfs0//etc/hosts': Can't set UID=0
> Warning when extracting archive entry
> '/home/friesen/rootfs/rootfs0//etc/profile.environment': Can't set UID=0
> Warning when extracting archive entry
> '/home/friesen/rootfs/rootfs0//etc/fstab': Can't set UID=0
> Warning when extracting archive entry
> '/home/friesen/rootfs/rootfs0//etc/protocols': Can't set UID=0
> Warning when extracting archive entry
> '/home/friesen/rootfs/rootfs0//run/': Can't set UID=0
> Warning when extracting archive entry
> '/home/friesen/rootfs/rootfs0//root/': Can't set UID=0
> Warning when extracting archive entry
> '/home/friesen/rootfs/rootfs0//dev/': Can't set UID=0
> Warning when extracting archive entry
> '/home/friesen/rootfs/rootfs0//dev/zero': Can't create
> '/home/friesen/rootfs/rootfs0/dev/zero'
> Warning when extracting archive entry
> '/home/friesen/rootfs/rootfs0//dev/console': Can't create
> '/home/friesen/rootfs/rootfs0/dev/console'
> Warning when extracting archive entry
> '/home/friesen/rootfs/rootfs0//dev/null': Can't create
> '/home/friesen/rootfs/rootfs0/dev/null'
> Warning when extracting archive entry
> '/home/friesen/rootfs/rootfs0//home/': Can't set UID=0
&g

Re: [ptxdist] rootfs: package

2018-12-04 Thread Andreas Friesen 
 Uhr schrieb Michael Olbrich <
m.olbr...@pengutronix.de>:

> On Tue, Dec 04, 2018 at 10:40:11AM +0100, Andreas Friesen wrote:
> > Hi Michael.
> >
> > I compiled opkg for my host system (archlinux) with : "./configure ;
> make ;
> > make install" and installed all packages from ptxdist without any errors:
> > DESTDIR="/home/friesen/rootfs/rootfs" opkg -f
> > "/home/friesen/rootfs/opkg.conf" -o "/home/friesen/rootfs/rootfs/"
> install
> > /home/friesen/ptx-multi/platform-soc/packages/*.ipk
> >
> > but
> >
> > DESTDIR="/home/friesen/rootfs/rootfs"
> > /home/friesen/gitlab/ptx-multi/platform-soc/sysroot-host/bin/opkg
> > -f "/home/friesen/rootfs/opkg.conf" -o "/home/friesen/rootfs/rootfs/"
> > install
> >
> /home/friesen/gitlab/quantumx-master/projects/ppc/ptx-multi/platform-soc/packages/*,pkg
> >
> > produced this error:
> >
> > * check_data_file_clashes: Package rootfs wants to install file
> > /home/faix/ptx-multi/platform-soc/build-target/image-nor-mxfs4/var/run
> > But that path is currently a directory
> >
> > I finded out with try-and-error method, that opkg do not like "prefix= "
> !
>
> Very strange. I don't see this issue here. Also, did you copy the correct
> error message? The path there is not inside the specified DESTDIR. And is
> var/run inside the generated rootfs an empty directory?
>
> Also, calling opkg manually may work for other reasons: If rootfs is
> installed before another package created the directory, then I think it
> will just work.
>
> Michael
>
> --
> Pengutronix e.K.   | |
> Industrial Linux Solutions | http://www.pengutronix.de/  |
> Peiner Str. 6-8, 31137 Hildesheim, Germany | Phone: +49-5121-206917-0|
> Amtsgericht Hildesheim, HRA 2686   | Fax:   +49-5121-206917- |
>
> ___
> ptxdist mailing list
> ptxdist@pengutronix.de
___
ptxdist mailing list
ptxdist@pengutronix.de

Re: [ptxdist] package: What is wrong with host-unfs3

2018-12-04 Thread Andreas Friesen 
Thanks Michael, It works !
-
Andreas Friesen

Am Di., 4. Dez. 2018 um 11:33 Uhr schrieb Michael Olbrich <
m.olbr...@pengutronix.de>:

> On Tue, Dec 04, 2018 at 10:53:52AM +0100, Andreas Friesen wrote:
> > M, sorry Michael, but PTXCONF_FIX_PERMISSIONS is not set
> >
> > cat configs/platform-soc/ptxconfig | grep FIX
> > # PTXCONF_FIX_PERMISSIONS is not set
> > PTXCONF_BUSYBOX_CROSS_COMPILER_PREFIX=""
> > PTXCONF_BUSYBOX_PREFIX="./_install"
>
> Right, sorry, I didn't look closely enough at the error message.
> You're running 'ptxdist nfsroot', right? It basically suffers from the same
> issue. You'll need the commit 403d1f49c78bc484f0de036c366dfd9072725d3f
> ("ptxd_make_image_common: set ptx_packages_selected for image/env") for
> this.
> I think, in this case you can just copy the modified file
> (rules/post/ptxd_make_image_common.make) into your BSP.
>
> Michael
>
> > Am Di., 4. Dez. 2018 um 08:36 Uhr schrieb Michael Olbrich <
> > m.olbr...@pengutronix.de>:
> >
> > > On Tue, Dec 04, 2018 at 12:38:00AM +0100, Andreas Friesen wrote:
> > > > After BSP upgrade to 2018.11.0  I've got this error:
> > > >
> > > > ---
> > > > target: host-unfs3.install.post
> > > > ---
> > > >
> > > > finished target host-unfs3.install.post
> > > >
> > > > ptxdist: error: ethtool is not a package or not selected
> > > >
> > > > /usr/local/lib/ptxdist-2018.11.0/rules/post/ptxd_make_nfsd.make:12:
> > > recipe
> > > > for target 'ptxd_make_nfsd' failed
> > > > make: *** [ptxd_make_nfsd] Error 1
> > >
> > > This is now fixed in master. For a workaround for the latest release
> see
> > > my comment in the thread 'ptxdist upgrade from v2014.12.0 to latest ->
> > > error'.
> > >
> > > Michael
> > >
> > > --
> > > Pengutronix e.K.   |
>|
> > > Industrial Linux Solutions |
> http://www.pengutronix.de/  |
> > > Peiner Str. 6-8, 31137 Hildesheim, Germany | Phone: +49-5121-206917-0
>   |
> > > Amtsgericht Hildesheim, HRA 2686   | Fax:
>  +49-5121-206917- |
> > >
> > > ___
> > > ptxdist mailing list
> > > ptxdist@pengutronix.de
>
> > ___
> > ptxdist mailing list
> > ptxdist@pengutronix.de
>
>
> --
> Pengutronix e.K.   | |
> Industrial Linux Solutions | http://www.pengutronix.de/  |
> Peiner Str. 6-8, 31137 Hildesheim, Germany | Phone: +49-5121-206917-0|
> Amtsgericht Hildesheim, HRA 2686   | Fax:   +49-5121-206917- |
>
> ___
> ptxdist mailing list
> ptxdist@pengutronix.de
___
ptxdist mailing list
ptxdist@pengutronix.de

Re: [ptxdist] package: What is wrong with host-unfs3

2018-12-04 Thread Andreas Friesen 
M, sorry Michael, but PTXCONF_FIX_PERMISSIONS is not set

cat configs/platform-soc/ptxconfig | grep FIX
# PTXCONF_FIX_PERMISSIONS is not set
PTXCONF_BUSYBOX_CROSS_COMPILER_PREFIX=""
PTXCONF_BUSYBOX_PREFIX="./_install"


Am Di., 4. Dez. 2018 um 08:36 Uhr schrieb Michael Olbrich <
m.olbr...@pengutronix.de>:

> On Tue, Dec 04, 2018 at 12:38:00AM +0100, Andreas Friesen wrote:
> > After BSP upgrade to 2018.11.0  I've got this error:
> >
> > ---
> > target: host-unfs3.install.post
> > ---
> >
> > finished target host-unfs3.install.post
> >
> > ptxdist: error: ethtool is not a package or not selected
> >
> > /usr/local/lib/ptxdist-2018.11.0/rules/post/ptxd_make_nfsd.make:12:
> recipe
> > for target 'ptxd_make_nfsd' failed
> > make: *** [ptxd_make_nfsd] Error 1
>
> This is now fixed in master. For a workaround for the latest release see
> my comment in the thread 'ptxdist upgrade from v2014.12.0 to latest ->
> error'.
>
> Michael
>
> --
> Pengutronix e.K.   | |
> Industrial Linux Solutions | http://www.pengutronix.de/  |
> Peiner Str. 6-8, 31137 Hildesheim, Germany | Phone: +49-5121-206917-0|
> Amtsgericht Hildesheim, HRA 2686   | Fax:   +49-5121-206917- |
>
> ___
> ptxdist mailing list
> ptxdist@pengutronix.de
___
ptxdist mailing list
ptxdist@pengutronix.de

Re: [ptxdist] rootfs: package

2018-12-04 Thread Andreas Friesen 
Hi Michael.

I compiled opkg for my host system (archlinux) with : "./configure ; make ;
make install" and installed all packages from ptxdist without any errors:
DESTDIR="/home/friesen/rootfs/rootfs" opkg -f
"/home/friesen/rootfs/opkg.conf" -o "/home/friesen/rootfs/rootfs/" install
/home/friesen/ptx-multi/platform-soc/packages/*.ipk

but

DESTDIR="/home/friesen/rootfs/rootfs"
/home/friesen/gitlab/ptx-multi/platform-soc/sysroot-host/bin/opkg
-f "/home/friesen/rootfs/opkg.conf" -o "/home/friesen/rootfs/rootfs/"
install
/home/friesen/gitlab/quantumx-master/projects/ppc/ptx-multi/platform-soc/packages/*,pkg

produced this error:

* check_data_file_clashes: Package rootfs wants to install file
/home/faix/ptx-multi/platform-soc/build-target/image-nor-mxfs4/var/run
But that path is currently a directory

I finded out with try-and-error method, that opkg do not like "prefix= " !



Am Di., 4. Dez. 2018 um 08:50 Uhr schrieb Michael Olbrich <
m.olbr...@pengutronix.de>:

> On Mon, Dec 03, 2018 at 11:38:46PM +0100, Andreas Friesen wrote:
> > Hello everyone,
> >
> > it's work now. Here is a little patch.
> >
> >
> > --- /usr/local/lib/ptxdist-2018.11.0/rules/host-opkg.make
>  2018-11-22
> > 20:12:56.0 +0100
> >
> > +++ rules/host-opkg.make2018-12-03 23:36:48.214811901 +0100
> > @@ -31,7 +31,6 @@
> >  #
> >  HOST_OPKG_CONF_TOOL:= autoconf
> >  HOST_OPKG_CONF_OPT := \
> > -   $(HOST_AUTOCONF) \
> > --disable-libopkg-api \
> > --disable-static \
> > --disable-pathfinder \
> > @@ -45,4 +44,6 @@
> > --without-libsolv \
> > --without-static-libopkg
> >
> > +#  $(HOST_AUTOCONF) \
> > +
> >  # vim: syntax=make
>
> This just removes opkg from your PATH. Did you rebuild the BSP afterwards?
> Maybe you have opkg somewhere else in PATH.
>
> Michael
>
> --
> Pengutronix e.K.   | |
> Industrial Linux Solutions | http://www.pengutronix.de/  |
> Peiner Str. 6-8, 31137 Hildesheim, Germany | Phone: +49-5121-206917-0|
> Amtsgericht Hildesheim, HRA 2686   | Fax:   +49-5121-206917- |
>
> ___
> ptxdist mailing list
> ptxdist@pengutronix.de
___
ptxdist mailing list
ptxdist@pengutronix.de

[ptxdist] package: What is wrong with host-unfs3

2018-12-03 Thread Andreas Friesen 
Hi,

After BSP upgrade to 2018.11.0  I've got this error:

---
target: host-unfs3.install.post
---

finished target host-unfs3.install.post

ptxdist: error: ethtool is not a package or not selected

/usr/local/lib/ptxdist-2018.11.0/rules/post/ptxd_make_nfsd.make:12: recipe
for target 'ptxd_make_nfsd' failed
make: *** [ptxd_make_nfsd] Error 1
___
ptxdist mailing list
ptxdist@pengutronix.de

Re: [ptxdist] rootfs: package

2018-12-03 Thread Andreas Friesen 
Hello everyone,

it's work now. Here is a little patch.


--- /usr/local/lib/ptxdist-2018.11.0/rules/host-opkg.make   2018-11-22
20:12:56.0 +0100

+++ rules/host-opkg.make2018-12-03 23:36:48.214811901 +0100
@@ -31,7 +31,6 @@
 #
 HOST_OPKG_CONF_TOOL:= autoconf
 HOST_OPKG_CONF_OPT := \
-   $(HOST_AUTOCONF) \
--disable-libopkg-api \
--disable-static \
--disable-pathfinder \
@@ -45,4 +44,6 @@
--without-libsolv \
--without-static-libopkg

+#  $(HOST_AUTOCONF) \
+
 # vim: syntax=make


Am Do., 29. Nov. 2018 um 08:35 Uhr schrieb Andreas Friesen <
ms.f...@gmail.com>:

> ...
> Hello everyone,
>
> I migrated my project from 2017.05.0 to 2018.11.0 without any troubles,
> but
> "ptxdist images" has a problem with rootfs package. Options
> PTXCONF_ROOTFS_RUN=y
> PTXCONF_ROOTFS_VAR_RUN=y are active and I don't have any packages, which
> install /run or /var/run as a directory.  I checked all packages with
> manually extract with :
> ar x $package ; tar -xf ./data.tar.gz ;
>
> rootfs_1.0.0_armhf.ipk
> ...
> drwx--   240 Nov  1 01:00 root
> drwxr-xr-x   240 Nov  1 01:00 run
> drwxr-xr-x   240 Nov  1 01:00 sys
> ...
> drwxr-xr-x  2   40 Nov  1 01:00 var/log
> lrwxrwxrwx  1   6 Nov  1 01:00 var/run -> ../run
> drwxr-xr-x  2   40 Nov  1 01:00 var/tmp
>
> also, rootfs package looks great for me, but what is wrong  with "ptxdist
> images"
> ...
> Installing usr-rootfs (1.0) on root.
> InstallinCollected errors:
>  * check_data_file_clashes: Package rootfs wants to install file
> /home/faix/ptx-multi/platform-soc/build-target/image-nor-mxfs4/var/run
> But that path is currently a directory
>  * opkg_solver_install: Cannot install package rootfs.
> g luacjson (1.0.0) on root.
> 
> Installing rootfs (1.0.0) on root.
> To remove package debris, try `opkg remove rootfs`.
> To re-attempt the install, try `opkg install rootfs`.
> ...
> Configuring libndp.
> make: *** [/home/faix/ptx-multi/rules/image-ubifs-mxfs4.make:12:
> /home/ffaix/ptx-multi/platform-soc/images/root-mxfs4.ubifs] Error 255
>
> - Andreas
>
___
ptxdist mailing list
ptxdist@pengutronix.de

[ptxdist] rootfs: package

2018-11-28 Thread Andreas Friesen 
...
Hello everyone,

I migrated my project from 2017.05.0 to 2018.11.0 without any troubles, but
"ptxdist images" has a problem with rootfs package. Options
PTXCONF_ROOTFS_RUN=y
PTXCONF_ROOTFS_VAR_RUN=y are active and I don't have any packages, which
install /run or /var/run as a directory.  I checked all packages with
manually extract with :
ar x $package ; tar -xf ./data.tar.gz ;

rootfs_1.0.0_armhf.ipk
...
drwx--   240 Nov  1 01:00 root
drwxr-xr-x   240 Nov  1 01:00 run
drwxr-xr-x   240 Nov  1 01:00 sys
...
drwxr-xr-x  2   40 Nov  1 01:00 var/log
lrwxrwxrwx  1   6 Nov  1 01:00 var/run -> ../run
drwxr-xr-x  2   40 Nov  1 01:00 var/tmp

also, rootfs package looks great for me, but what is wrong  with "ptxdist
images"
...
Installing usr-rootfs (1.0) on root.
InstallinCollected errors:
 * check_data_file_clashes: Package rootfs wants to install file
/home/faix/ptx-multi/platform-soc/build-target/image-nor-mxfs4/var/run
But that path is currently a directory
 * opkg_solver_install: Cannot install package rootfs.
g luacjson (1.0.0) on root.

Installing rootfs (1.0.0) on root.
To remove package debris, try `opkg remove rootfs`.
To re-attempt the install, try `opkg install rootfs`.
...
Configuring libndp.
make: *** [/home/faix/ptx-multi/rules/image-ubifs-mxfs4.make:12:
/home/ffaix/ptx-multi/platform-soc/images/root-mxfs4.ubifs] Error 255

- Andreas
___
ptxdist mailing list
ptxdist@pengutronix.de