Bug#1041865: AW: Bug#1041865: debos: Output of apt action not shown when running debos in noninteractive shell
Hi Christopher, thank you very much for sharing your finding about the complete raw log! Indeed we can see the whole output of apt actions there. I think this is a satisfying workaround, especially since this seems to be an issue which needs to be fixed elsewhere. Best regards Tobias
Bug#1041865: debos: Output of apt action not shown when running debos in noninteractive shell
Control: forwarded -1 https://github.com/go-debos/debos/issues/416 On Mon, 2023-07-24 at 17:56 +0200, q wrote: > Package: debos > Version: 1.1.1-2.1 > Severity: important > Tags: upstream > > Dear Maintainer, > > we're using debos within Gitlab CI runners which basically works. However the > output of apt does not appear in the job logs due to special character > sequences > printed by apt. This makes it hard to debug any issues if the apt action fails > and always requires us to run debos in an interactive shell manually. > > Please see https://github.com/go-debos/debos/issues/416 for details and Hi, It is shown, it is just that GitLab Runner seems to hide certain lines ending in certain newline character sequences. You _can_ get to the full apt actions logs by going to the job and pressing the "Show complete raw" button at the top next to the Search bar. > https://github.com/go-debos/debos/commit/b1197b80b4e87c6cd1cd7b06669faa7c40798551 > > for a possible solution which already has been merged into the upstream's main > branch. Would it be possible to include this patch in an package update? Unfortunately this will not fix the issue and the issue really belong to the GitLab runner and its termination character detection. I will search for an issue on the GitLab.com tracker, but so far I haven't found anything as yet. It would help if we could find a bug on the tracker already about the termination character issue.
Bug#1041865: debos: Output of apt action not shown when running debos in noninteractive shell
Package: debos Version: 1.1.1-2.1 Severity: important Tags: upstream Dear Maintainer, we're using debos within Gitlab CI runners which basically works. However the output of apt does not appear in the job logs due to special character sequences printed by apt. This makes it hard to debug any issues if the apt action fails and always requires us to run debos in an interactive shell manually. Please see https://github.com/go-debos/debos/issues/416 for details and https://github.com/go-debos/debos/commit/b1197b80b4e87c6cd1cd7b06669faa7c40798551 for a possible solution which already has been merged into the upstream's main branch. Would it be possible to include this patch in an package update? Thanks, Tobias -- System Information: Debian Release: 12.0 APT prefers stable-updates APT policy: (500, 'stable-updates'), (500, 'stable-security'), (500, 'stable') Architecture: amd64 (x86_64) Kernel: Linux 6.1.0-10-amd64 (SMP w/32 CPU threads; PREEMPT) Locale: LANG=de_DE.UTF-8, LC_CTYPE=de_DE.UTF-8 (charmap=UTF-8), LANGUAGE not set Shell: /bin/sh linked to /usr/bin/dash Init: systemd (via /run/systemd/system) LSM: AppArmor: enabled Versions of packages debos depends on: ii busybox1:1.35.0-4+b3 pn debootstrap ii libc6 2.36-9 ii libglib2.0-0 2.74.6-2 pn libostree-1-1 pn qemu-system-x86 ii qemu-user-static 1:7.2+dfsg-7 pn systemd-container Versions of packages debos recommends: pn bmap-tools ii bzip2 1.0.8-5+b1 ii e2fsprogs 1.47.0-2 ii linux-image-amd64 6.1.37-1 ii mount 2.38.1-5+b1 pn ovmf pn parted pn systemd-resolved ii udev 252.6-1 ii xz-utils 5.4.1-0.2 pn zip Versions of packages debos suggests: pn libslirp-helper pn user-mode-linux
