Hello,

In this build, I do not see a call to dh_autoreconf_clean

https://buildd.debian.org/status/fetch.php?pkg=hkl&arch=amd64&ver=5.0.0.3434-1&stamp=1713518550&raw=0

this package override_dh_clean like this

override_dh_clean:
rm -f Documentation/api/hkl-docs.sgml
dh_clean

so my question is: is it normal or a bug in dh-autoreconf ?

thanks for your help

Frederic

--- SoupGate-Win32 v1.05
* Origin: fsxNet Usenet Gateway (21:1/5)

On 19/04/2024 13:27, PICCA Frederic-Emmanuel wrote:

Hello,

In this build, I do not see a call to dh_autoreconf_clean

snip

so my question is: is it normal or a bug in dh-autoreconf ?

thanks for your help

Frederic

Checked one of my packages that uses autoreconf and is building OK.
There is no dh_autoreconf_clean showing in the log. Cheers, Peter P.S. I
guess you could add it to your rules file if really needed.

--- SoupGate-Win32 v1.05
* Origin: fsxNet Usenet Gateway (21:1/5)

--=_dd189d24-5e94-4af5-ad46-7d311428beca
Content-Type: text/plain; charset=utf-8
Content-Transfer-Encoding: quoted-printable



----- Le 19 Avr 24, à 15:11, Gianfranco Costamagna [email protected] a écrit :

Hello,

Instead, I see it on the very same file :)

where ???, I am looking for dh_autoreconf_clean

cheers

dpkg-buildpackage: info: host architecture amd64
debian/rules clean
dh clean --with=gir
   debian/rules override_dh_clean
make[1]: Entering directory '/<<PKGBUILDDIR>>'
rm -f Documentation/api/hkl-docs.sgml
dh_clean
    rm -f debian/debhelper-build-stamp
    rm -rf debian/.debhelper/
    rm -f -- debian/ghkl.substvars debian/libhkl5.substvars >    debian/libhkl-dev.substvars debian/libhkl-doc.substvars >    debian/gir1.2-hkl-5.0.substvars debian/files
    rm -fr -- debian/ghkl/ debian/tmp/ debian/libhkl5/ debian/libhkl-dev/ >    debian/libhkl-doc/ debian/gir1.2-hkl-5.0/
    find .  \( \( \
        \( -path .\*/.git -o -path .\*/.svn -o -path .\*/.bzr -o -path .\*/.hg -o -path
        .\*/CVS -o -path .\*/.pc -o -path .\*/_darcs \) -prune -o -type f -a \
            \( -name '#*#' -o -name '.*~' -o -name '*~' -o -name DEADJOE \
         -o -name '*.orig' -o -name '*.rej' -o -name '*.bak' \ >         -o -name '.*.orig' -o -name .*.rej -o -name '.SUMS' \ >         -o -name TAGS -o \( -path '*/.deps/*' -a -name '*.P' \) \ >        \) -exec rm -f {} + \) -o \
        \( -type d -a \( -name autom4te.cache -o -name __pycache__ \) -prune -exec rm
        -rf {} + \) \)
make[1]: Leaving directory '/<<PKGBUILDDIR>>'

G.

Il venerdì 19 aprile 2024 alle ore 14:45:15 CEST, PICCA Frederic-Emmanuel <[email protected]> ha scritto:

Hello,

In this build, I do not see a call to dh_autoreconf_clean

https://buildd.debian.org/status/fetch.php?pkg=hkl&arch=amd64&ver=5.0.0.3434-1&stamp=1713518550&raw=0

this package override_dh_clean like this

override_dh_clean:
        rm -f Documentation/api/hkl-docs.sgml
        dh_clean

so my question is: is it normal or a bug in dh-autoreconf ?

thanks for your help

Frederic

--=_dd189d24-5e94-4af5-ad46-7d311428beca--

--- SoupGate-Win32 v1.05
* Origin: fsxNet Usenet Gateway (21:1/5)

On 2024-04-19, at 14:27:40 +0200, PICCA Frederic-Emmanuel wrote:

Hello,

In this build, I do not see a call to dh_autoreconf_clean

https://buildd.debian.org/status/fetch.php?pkg=hkl&arch=amd64&ver=5.0.0.3434-1&stamp=1713518550&raw=0

this package override_dh_clean like this

override_dh_clean:
rm -f Documentation/api/hkl-docs.sgml
dh_clean

so my question is: is it normal or a bug in dh-autoreconf ?

This is normal. du_autoreconf_clean exits without doing anything unless debian/autoreconf.before and debian/autoreconf.after exist.

To use a different package that I happen to have to hand as an example:

$ git status
On branch master
Your branch is up to date with 'debian/master'.

nothing to commit, working tree clean
$ schroot -r -c sid-conntrack-tools -- dpkg-source --before-build .
$ schroot -r -c sid-conntrack-tools -- fakeroot debian/rules clean binary
dh clean
dh_clean
rm -f debian/debhelper-build-stamp
rm -rf debian/.debhelper/
rm -f -- debian/conntrack.substvars debian/conntrackd.substvars debian/nfct.substvars debian/files
rm -fr -- debian/conntrack/ debian/tmp/ debian/conntrackd/ debian/nfct/
find . \( \( \
\( -path .\*/.git -o -path .\*/.svn -o -path .\*/.bzr -o -path .\*/.hg -o -path .\*/CVS -o -path .\*/.pc -o -path .\*/_darcs \) -prune -o -type f -a \
\( -name '#*#' -o -name '.*~' -o -name '*~' -o -name DEADJOE \
-o -name '*.orig' -o -name '*.rej' -o -name '*.bak' \
-o -name '.*.orig' -o -name .*.rej -o -name '.SUMS' \
-o -name TAGS -o \( -path '*/.deps/*' -a -name '*.P' \) \
\) -exec rm -f {} + \) -o \
\( -type d -a \( -name autom4te.cache -o -name __pycache__ \) -prune -exec rm -rf {} + \) \)
dh binary
dh_update_autotools_config
[...]
$ schroot -r -c sid-conntrack-tools -- fakeroot debian/rules clean
dh clean
dh_auto_clean
make -j1 distclean
[...]
make[1]: Leaving directory '/space/azazel/work/git/repos/salsa/pkg-netfilter-team/pkg-conntrack-tools'
dh_autoreconf_clean
rm -f -- ./Makefile.in ./configure ./autom4te.cache/output.2 ./autom4te.cache/requests ./autom4te.cache/output.0 ./autom4te.cache/traces.1 ./autom4te.cache/traces.2 ./autom4te.cache/output.1 ./autom4te.cache/traces.0 ./extensions/Makefile.in ./m4/
lt\~obsolete.m4 ./m4/ltsugar.m4 ./m4/libtool.m4 ./m4/ltversion.m4 ./m4/ltoptions.m4 ./src/Makefile.in ./src/helpers/Makefile.in ./configure\~ ./build-aux/ar-lib ./build-aux/compile ./build-aux/missing ./build-aux/ltmain.sh ./build-aux/ylwrap ./build-aux/
depcomp ./aclocal.m4 ./include/Makefile.in ./include/helpers/Makefile.in ./include/linux/Makefile.in ./include/linux/netfilter/Makefile.in
rm -f debian/autoreconf.before debian/autoreconf.after
dh_clean
[...]

The first time `debian/rules clean` runs, dh_autoreconf has not run, so dh_autoreconf_clean has nothing to do and is silent. The second time,
after dh_autoreconf has run, you can see it doing stuff.

J.

-----BEGIN PGP SIGNATURE-----

iQIzBAABCgAdFiEEbB20U2PvQDe9VtUXKYasCr3xBA0FAmYietwACgkQKYasCr3x BA2P9A//RUb2CrWnR+7ftz+G+b9N0IWLowjoKM72dfCWN2N/MkElkExqiRihsUaQ UYE6jVadhJUjaufmBsrqweMX1D7YGBLUHA5JlxTyd6W3xhOxm+Tnq+vIex5oIHze uhLVsTwx/NP5l+cnNmYmZfgdIgyZGzvpjoj3LcFdmcSrGj8li5doGep2V4j8eizn jdwZJBigNZ3Y6TwMQEWL0NjLkOWv/gAUMCJYACh0qdxbXzHOLI7a9dXmEczvO2ii IPf/9CY5ApLXROmdJyaOpBwtp4V7DDU/xoWObFK7fv74SlBzilsb1Itvk3ZsYFx/ aEe+eysR8PJD6AyVp6GTX56ZeuCYF0+sc4MBDJG8Ly6jsPERuCE+Y7WvM2plR8sV pkzPhO+SDfN5CHTQyD57zjo7MhugnVou9BHrvbwI4ndxMfgR2Jp7WdwvVVmWKYL9 7L0/RzXcBTxp6VOG+ChKLvsAx7LfOQ97MVTnuNR5Y5Z00Q2iHIfnqRlQWt+9YvjW YupJjqkGgMSkYn/erm6Of2bAIbFWc8u3KqfLJWtbOadpFmUqmixU8X60TGdzG569 ZDKvboSfxy0OmitgjWtIkQW8Yusv8BXvH81NKsc8mwIEQtx8Y8roVBFhySqki1uA Uejw30XkzLcXqa9NDvvIXLaR+dS7+UK3fsxM8k2JVLGckI9dqRI=
=G7t7
-----END PGP SIGNATURE-----

--- SoupGate-Win32 v1.05
* Origin: fsxNet Usenet Gateway (21:1/5)

[...]

The first time `debian/rules clean` runs, dh_autoreconf has not run, so dh_autoreconf_clean has nothing to do and is silent. The second time,
after dh_autoreconf has run, you can see it doing stuff.

ok, in that case it would be nice to display a message saying I do nothing :), in order to manifest its presence :)

cheers

Fred

--- SoupGate-Win32 v1.05
* Origin: fsxNet Usenet Gateway (21:1/5)