Control: severity -1 wishlist
On Fri, 12 Apr 2024 19:57:23 +0200 Johannes Schauer Marin Rodrigues wrote: [...] > Quoting Francesco Poli (wintermute) (2024-04-11 00:13:51) [...] > > I can update the virtual machine (if I create a symlink, see bug > > [#1061816]): > > > > $ sbuild-qemu-update --boot=efi unstable-autopkgtest-amd64.img > > > > [#1061816]: <https://bugs.debian.org/1061816#98> > > I think 1061816 was fixed with 0.85.7 and the changelog was just missing the > "closes" entry: > > https://tracker.debian.org/news/1518576/accepted-sbuild-0857-source-into-unstable/ Yes, I have just tested sbuild-qemu/0.85.7 from unstable, and I can confirm that the symlink is no longer needed. I have just sent a message to close bug report #1061816 ... > > > But, when I try to build a package from withing the unpacked source > > tree: [...] > > Error reading configuration: PIUPARTS binary 'piuparts' does not exist or > > is not executable at /usr/share/perl5/Sbuild/Conf.pm line 76. > > > > Now, piuparts is indeed not installed on the host: [...] > > However, I thought that setting $run_piuparts = 1 in ~/.sbuildrc caused > > piuparts to be run inside the virtual machine guest system, not on the > > host system! > > What made you think that? Is the error message above not clear enough? Do you > think it should be improved to make things clearer? Do you have suggestions > for > a message that would've better explained that piuparts needs to be installed > on > the host system? My point is not that the error message should be improved. Actually, I think the error message clearness is basically OK. > > > Hence, I thought that piuparts was going to be automatically installed > > and executed on the guest system (actually on the throw-away overlay). > > And I thought that the same was going to happen for $run_autopkgtest = 1 > > and for $run_lintian = 1 ... > > > > Am I completely off-track? > > What did I fail to understand? > > > > Why does sbuild-qemu insist that piuparts be installed on the *host* > > system? > > Because it needs to be installed on the host. In the same way as autopkgtest > needs to be on the host. What can sbuild improve? My point is that sbuild{,-qemu} should install piuparts inside the build environment (chroot or VM guest system) and run it from within the build environment, if this is possible. Does sbuild{,-qemu} do so for lintian? I think this is even more important for lintian: if the host system runs Debian testing (or maybe even Debian stable) and the package is being built for Debian unstable (as upload target), then the package should be checked by the version of lintian which is currently in Debian unstable. If it were checked by the version of lintian from Debian testing (or even from Debian stable), many undeserved "unknown Policy version" complaints could pop up... Do you agree with the reasoning? Thanks for your time and patience! :-) -- http://www.inventati.org/frx/ There's not a second to spare! To the laboratory! ..................................................... Francesco Poli . GnuPG key fpr == CA01 1147 9CD2 EFDF FB82 3925 3E1C 27E1 1F69 BFFE
pgpli10LtTDY8.pgp
Description: PGP signature
