Le lundi 05 septembre 2022 à 08:28 +1000, Brian May a écrit : > On Wed, Aug 03, 2022 at 12:22:32PM +0200, > julien.pu...@gmail.com wrote: > > I'm sorry, but I don't see why you think this is a problem with > > setuptools-scm. > > > > sshuttle's debian/rules asks setuptools-scm to generate a version > > file > > in its clean target. So setuptools-scm does so, and it doesn't look > > invalid. > > > > But it doesn't not correspond to the version file as shipped, so > > dpkg > > protests that the source tree has been modified. > > Please make sure you CC responses to me. Otherwise I won't get them. > > At first glance I thought this was invalid Python code, but oh wait, > I > think this is valid. Problem when dealing with too many languages. > > __version__ = version = '1.1.0' > __version_tuple__ = version_tuple = (1, 1, 0) > > But what seems to be the problem here is that setuptools-scm has > silently changed how it generates this file. Which breaks Debian > packages. > > If you don't agree with me, then assign this bug back to sshuttle and > I > will deal with it. In fact latest upstream sshuttle removes > setuptools-scm support anyway.
If I remember well, that generation is done in the clean target: if that's the case, then it's sshuttle's (package's) problem. I see two solutions: - add a patch so the file becomes re-generation invariant ; - add an empty override_dh_whatever_clean in d/rules so the re- generation isn't triggered. Cheers, J.Puydt
