severity 950684 serious
Thanks

Hi,

Am Samstag, den 22.02.2020, 17:17 +0100 schrieb Johannes Schauer:
> Control: severity -1 important
> 
> Quoting Johannes Schauer (2020-02-22 17:05:47)
> > Quoting Jörg Frings-Fürst (2020-02-22 16:48:52)
> > > > please show me evidence of that.
> > > > 
> > > > Setting a bug severity to serious means that sbuild will be
> > > > removed from
> > > > testing in March. You should have evidence before such a
> > > > drastic measure is
> > > > taken.
> > > All packages that directly or indirectly have systemd as build
> > > depend can no
> > > longer be compiled. I think that is reason enough.
> > 
> > Indeed I now see the problem myself.
> > 
> > Can you confirm something for me?
> > 
> > Above you quote an sbuild-createchroot command. Could you run the
> > same command
> > on your machine again but with --debootstrap=mmdebstrap in it?
> > 
> > Because for me, that fixes the problem. This suggests that the
> > problem is not
> > with sbuild but with the program that creates the chroot:
> > debootstrap
> 
> something else you can try: Instead of adding --
> debootstrap=mmdebstrap try
> adding --no-merged-usr to your sbuild-createchroot invocation. This
> also fixed
> the problem for me.
> 
> So it seems whatever it is, and whoever is at fault, this problem is
> not
> severity "serious", thus lowering severity accordingly.
> 

No. Also with a schroot build with --no-merged-usr I get:

[quote]
Unpacking sbuild-build-depends-dose3-dummy (0.invalid.0) ...
Setting up systemd (244.3-1) ...
Detected unsafe path transition / → /var during canonicalization of 
/var/log/journal.
Detected unsafe path transition / → /var during canonicalization of 
/var/log/journal.
Detected unsafe path transition / → /var during canonicalization of 
/var/log/journal.
Detected unsafe path transition / → /var during canonicalization of 
/var/log/journal.
dpkg: error processing package systemd (--configure):
 installed systemd package post-installation script subprocess returned error 
exit status 73
Setting up libnspr4:amd64 (2:4.24-1) ...
Setting up liblua5.2-0:amd64 (5.2.4-1.1+b3) ...
Setting up libelf1:amd64 (0.176-1.1) ...
Setting up libpopt0:amd64 (1.16-14) ...
Setting up libnss3:amd64 (2:3.50-1) ...
Setting up librpmio8 (4.14.2.1+dfsg1-1+b1) ...
Setting up librpm8 (4.14.2.1+dfsg1-1+b1) ...
Setting up dose-distcheck (5.0.1-14+b2) ...
Setting up sbuild-build-depends-dose3-dummy (0.invalid.0) ...
Processing triggers for libc-bin (2.29-10) ...
Errors were encountered while processing:
 systemd
W: Download is performed unsandboxed as root as file 
'/var/cache/apt/archives/partial/liblua5.2-0_5.2.4-1.1+b3_amd64.deb' couldn't 
be accessed by user '_apt'. - pkgAcquire::Run (13: Permission denied)
E: Sub-process /usr/bin/dpkg returned an error code (1)
apt-get failed.
E: Package installation failed
Not removing build depends: cloned chroot in use
E: Failed to explain bd-uninstallable
[/quote]


Build log is attached.

Back to serious

> Thanks!
> 
> cheers, josch

CU
Jörg
-- 
New:
GPG Fingerprint: 63E0 075F C8D4 3ABB 35AB  30EE 09F8 9F3C 8CA1 D25D
GPG key (long) : 09F89F3C8CA1D25D
GPG Key        : 8CA1D25D
CAcert Key S/N : 0E:D4:56

Old pgp Key: BE581B6E (revoked since 2014-12-31).

Jörg Frings-Fürst
D-54470 Lieser


git:      https://jff.email/cgit/

Threema:  SYR8SJXB
Wire:     @joergfringsfuerst
Skype:    joergpenguin
Ring:     jff
Telegram: @joergfringsfuerst


My wish list: 
 - Please send me a picture from the nature at your home.

Attachment: simple-scan_3.34.4-1_amd64-2020-02-22T16:24:21Z.build.gz
Description: application/gzip

Attachment: signature.asc
Description: This is a digitally signed message part

Reply via email to