Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Errors were encountered while processing #85

Open
riesebie opened this issue Mar 28, 2020 · 6 comments
Open

Errors were encountered while processing #85

riesebie opened this issue Mar 28, 2020 · 6 comments

Comments

@riesebie
Copy link

grml-live -A -V -s sid -c DEBORPHAN,GRMLBASE,GRML_FULL,RELEASE,AMD64,IGNORE,SNAPSHOT -r"lxtec20200328" -g grml64-full -o .

Errors were encountered while processing:
grml-etc
ERROR: 256 256
ERROR: chroot /source/grml-live/grml-live/grml_chroot dpkg --configure --pending return code 1
install_packages: executing chroot /source/grml-live/grml-live/grml_chroot dpkg -C
The following packages have been unpacked but not yet configured.
They must be configured using dpkg --configure or the configure
menu option in dselect for them to work:
grml-etc etcetera files for the Grml system

install_packages: executing chroot /source/grml-live/grml-live/grml_chroot apt-get clean
2 errors during executing of install_packages

@riesebie
Copy link
Author

This is running grml-live 0.34.4

@mika
Copy link
Member

mika commented Mar 31, 2020

The actual error message isn't listed here, also we don't see any such issue in our daily builds. You'd need to provide the software.log from the logs (should be /source/grml-live/grml-live/grml_logs/fai/software.log or so on your system) which should include the actual error message.

PS: I consider it a bit rude to just dump an error message into a bug report without any prosa text

@riesebie
Copy link
Author

Thank you @mika to dive in to this issue and please forgive me for my unfriendliness.
To be honest I tried to build a grml-live image like shown in my first post and got "Errors were encountered while processing:" at the end.

Please find the software.log which resides at /var/log/fai/grml on my system. The important message I found is:

Setting up grml-etc (1.7.0) ...

Configuration file '/etc/motd'
 ==> File on system created by you or by a script.
 ==> File also in package provided by package maintainer.
   What would you like to do about it ?  Your options are:
    Y or I  : install the package maintainer's version
    N or O  : keep your currently-installed version
      D     : show the differences between the versions
      Z     : start a shell to examine the situation
 The default action is to keep your current version.
*** motd (Y/I/N/O/D/Z) [default=N] ? dpkg: error processing package grml-etc (--configure):
 end of file on stdin at conffile prompt

BTW a build against testing instead of sid runs just fine.
Thanks for cooperation ;-)

@mika
Copy link
Member

mika commented May 27, 2020

@riesebie https://lxtec.de/grml-live/software.log leads to a 404. The file /etc/motd on your system seems to have been modified by you or another Debian package (which we don't ship by default in Grml), if you provide me steps how to reproduce it I could look into it.

@riesebie
Copy link
Author

@mika I provide grml-live.log again. On the build system there is no /etc/motd.

find /etc -name '*motd*'
/etc/update-motd.d
/etc/grml/fai/config/files/etc/motd
/etc/grml/fai/config/scripts/GRMLBASE/31-motd

The second error is behalf to a missing xfsdump.dpkg-new

dpkg: error processing archive /tmp/apt-dpkg-install-dPLvwm/778-xfsdump_3.1.9_amd64.deb (--unpack):                                                                                                        
   unable to open '/sbin/xfsdump.dpkg-new': No such file or directory

which indeed isn't available.

I can't reproduce it at the moment because

W: Failure while configuring base packages.  This will be re-attempted up to five times.                                                                                                                     
W: See /source/grml-live/build-area/grml_chroot/debootstrap/debootstrap.log for details (possibly the package libgcc1 is at fault)
Error in task extrbase. Code: 801

Thanks for participation

@mika
Copy link
Member

mika commented May 28, 2020

Regarding the motd file, the logfile says:

Setting up grml-etc (1.7.0) ...

Configuration file '/etc/motd'
 ==> File on system created by you or by a script.
 ==> File also in package provided by package maintainer.
   What would you like to do about it ?  Your options are:
    Y or I  : install the package maintainer's version
    N or O  : keep your currently-installed version
      D     : show the differences between the versions
      Z     : start a shell to examine the situation
 The default action is to keep your current version.
*** motd (Y/I/N/O/D/Z) [default=N] ? dpkg: error processing package grml-etc (--configure):
 end of file on stdin at conffile prompt
Setting up nfs-kernel-server (1:1.3.4-3) ...

What's inside /source/grml-live/grml-live/grml_chroot/etc/motd? If you chroot into the grml_chroot and invoke dpkg -S /etc/motd, does it report anything?

Regarding xfsdump issue: that's https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=953537

mika added a commit that referenced this issue Jun 3, 2020
By default debootstrap creates systems with /usr being merged, leading
to issues like the xfsdump issue we saw in
#85, also dpkg -S ... and
further commands break with /usr being merged.

It's possible to generate custom basefiles with debootstrap, but by
default we should invoke debootstrap with the --no-merged-usr option,
otherwise we might have different ISO layouts, depending on whether we
use appropriate basefiles (as on our offical build host) vs. locally.

Closes: #86
clexanis pushed a commit to clexanis/grml-build that referenced this issue Dec 12, 2022
By default debootstrap creates systems with /usr being merged, leading
to issues like the xfsdump issue we saw in
grml#85, also dpkg -S ... and
further commands break with /usr being merged.

It's possible to generate custom basefiles with debootstrap, but by
default we should invoke debootstrap with the --no-merged-usr option,
otherwise we might have different ISO layouts, depending on whether we
use appropriate basefiles (as on our offical build host) vs. locally.

Closes: grml#86
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

2 participants