[Date Prev][Date Next] [Thread Prev][Thread Next] [Date Index] [Thread Index]

Re: dpkg-source: info: local changes detected and gbp:error: Cannot parse archive name



Thanks, I went for dh_auto_clean option.
Here is the explicit answer https://lists.debian.org/debian-science/2015/05/msg00078.html which is better for a newbie.

What about (explicit) instructions how to push the package to http://anonscm.debian.org/cgit/debian-science/packages/gpaw.git
asked at https://lists.debian.org/debian-science/2015/05/msg00079.html?
Or does this question is specific to debian science and I should wait for their answer?

Marcin

On Sun, May 31, 2015 at 10:57 PM, gregor herrmann <gregoa@debian.org> wrote:
On Sun, 31 May 2015 22:54:58 +0500, Andrey Rahmatullin wrote:

> On Sun, May 31, 2015 at 05:03:29PM +0200, Marcin Dulak wrote:

> > It looks to me like the configuration.log file, which is written during
> > compilation of gpaw
> > is treated as a source modification. How should I handle this?
> You need to removed it in the clean step. With dh(1) it can be done by
> overriding dh_auto_clean.

Or (matter of taste) by adding the configuration.log to debian/clean.


Cheers,
gregor

--
 .''`.  Homepage: http://info.comodo.priv.at/ - OpenPGP key 0xBB3A68018649AA06
 : :' : Debian GNU/Linux user, admin, and developer -  https://www.debian.org/
 `. `'  Member of VIBE!AT & SPI, fellow of the Free Software Foundation Europe
   `-   NP: Bob Dylan: Jokerman

-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1

iQJ8BAEBCgBmBQJVa3XHXxSAAAAAAC4AKGlzc3Vlci1mcHJAbm90YXRpb25zLm9w
ZW5wZ3AuZmlmdGhob3JzZW1hbi5uZXREMUUxMzE2RTkzQTc2MEE4MTA0RDg1RkFC
QjNBNjgwMTg2NDlBQTA2AAoJELs6aAGGSaoGFIoP/0xnSoF90gTPR/IxqmQkTncP
pa7XfLTCgnjNho3IdJS1vHrqUlNzbgvYCdUFlV3KgntsWk+ZJiGg+xmqIMaWTKgR
t+UKQfjooUk39ym6FC7yBSYHJbNh4WeXq/60BNLoAOLpSkfI812kzZr2+KCbfmhI
lhWJFNB4gnOuUPjmlmyAaPbx74hpSz3g3R70CNCCmrJ88o7edNKFd4PNVMs3jZfp
WNdFEUgJMibmcEgu02wfypGt8oHUR/zna9d5RjQwChBfbH4mD+RiPrTW970Db446
DYpjyKygUlpL/19w9Dm4Ft70+nIDy1tG63ElXPkoiw1QOVeSaQsj/kWevtjx6ykC
ajnUdneDjRknr5a5ZMvA2VZR6X/ncYLXS7r4P3lldI2aqxpizKKMHzsO9/8AK5OE
synsbSj+bTQL1tva493FH6Uz+zivwCMUxcxOOOMvA9hthuG901sii1nSIbpydG9+
xwkP/ZE+G2NhW7WaW2YQQyBEzMqPmgvA0gRgyqq5eSHdMXjAKZawXg15fpJ1qFZt
GJJ0ZPMu5ZtZ0Er4PNH0nsCYjaMV8KeUMQRvuhpOa/H2v28mV5qOiyhirA9mdNaE
VY/VCVrxIJc3wqnt/r+BIXTTuDYYHKK+ZlKKuFlUBOc8ASBHOehRKHvjWWMtzZB7
HARu0U0LVkuzX934flDx
=Tpwq
-----END PGP SIGNATURE-----



Reply to: