From: Andreas Friesen <ms.frsn@gmail.com>
To: ptxdist@pengutronix.de
Subject: [ptxdist] rootfs: package
Date: Thu, 29 Nov 2018 08:35:09 +0100 [thread overview]
Message-ID: <CAA0ZWqbvs+ShSoMRm=QzLMcuO45fTLbemeSjdQ9qX=Amxk+qiQ@mail.gmail.com> (raw)
[-- Attachment #1.1: Type: text/plain, Size: 1394 bytes --]
...
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------ 2 40 Nov 1 01:00 root
drwxr-xr-x 2 40 Nov 1 01:00 run
drwxr-xr-x 2 40 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
[-- Attachment #1.2: Type: text/html, Size: 2128 bytes --]
[-- Attachment #2: Type: text/plain, Size: 91 bytes --]
_______________________________________________
ptxdist mailing list
ptxdist@pengutronix.de
next reply other threads:[~2018-11-29 7:35 UTC|newest]
Thread overview: 14+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-11-29 7:35 Andreas Friesen [this message]
2018-12-03 22:38 ` Andreas Friesen
2018-12-04 7:50 ` Michael Olbrich
2018-12-04 9:40 ` Andreas Friesen
2018-12-04 10:40 ` Michael Olbrich
2018-12-04 11:47 ` Andreas Friesen
2018-12-04 11:53 ` Andreas Friesen
2018-12-04 11:58 ` Michael Olbrich
2018-12-04 12:47 ` Andreas Friesen
2018-12-04 12:58 ` Michael Olbrich
2018-12-04 13:25 ` Andreas Friesen
2018-12-04 13:39 ` Michael Olbrich
2018-12-05 6:32 ` Andreas Friesen
2018-12-04 7:49 ` Michael Olbrich
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to='CAA0ZWqbvs+ShSoMRm=QzLMcuO45fTLbemeSjdQ9qX=Amxk+qiQ@mail.gmail.com' \
--to=ms.frsn@gmail.com \
--cc=ptxdist@pengutronix.de \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox