Your message dated Sun, 1 May 2016 06:56:04 +0000
with message-id <[email protected]>
and subject line Re: Bug#478719: debhelper: Debhelper::Dh_Lib breaks scripts
unless script calls &inhibit_log
has caused the Debian Bug report #478719,
regarding debhelper: Debhelper::Dh_Lib breaks scripts unless script calls
&inhibit_log
to be marked as done.
This means that you claim that the problem has been dealt with.
If this is not the case it is now your responsibility to reopen the
Bug report if necessary, and/or fix the problem forthwith.
(NB: If you are a system administrator and have no idea what this
message is talking about, this may indicate a serious mail system
misconfiguration somewhere. Please contact [email protected]
immediately.)
--
478719: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=478719
Debian Bug Tracking System
Contact [email protected] with problems
--- Begin Message ---
Package: debhelper
Version: 7.0.4
Severity: normal
emdebian-tools scripts have begun failing constantly due to a bug in
Debhelper::Dh_Lib which tries to write debhelper.log files all over the
build:
$ find debian -name "*.log"
debian/gcc-4.3.debhelper.log
debian/gcc-4.3-base.debhelper.log
debian/gcc-4.3-multilib.debhelper.log
debian/gcc-4.3-hppa64.debhelper.log
debian/gcc-4.3-spu.debhelper.log
debian/g++-4.3-spu.debhelper.log
debian/gfortran-4.3-spu.debhelper.log
debian/cpp-4.3.debhelper.log
debian/g++-4.3.debhelper.log
debian/gcc-4.3-locales.debhelper.log
debian/g++-4.3-multilib.debhelper.log
debian/protoize.debhelper.log
debian/gobjc++-4.3.debhelper.log
debian/gobjc-4.3.debhelper.log
debian/gobjc-4.3-multilib.debhelper.log
debian/gfortran-4.3.debhelper.log
debian/fixincludes.debhelper.log
debian/gcc-4.3-source.debhelper.log
debian/gobjc++-4.3-multilib.debhelper.log
debian/libstdc++6-4.3-dev.debhelper.log
debian/gfortran-4.3-multilib.debhelper.log
debian/libstdc++6-4.3-pic.debhelper.log
debian/libstdc++6-4.3-dbg.debhelper.log
debian/libstdc++6-4.3-doc.debhelper.log
debian/gcc-4.3-soft-float.debhelper.log
debian/lib32stdc++6-4.3-dbg.debhelper.log
debian/lib64stdc++6-4.3-dbg.debhelper.log
debian/libn32stdc++6-4.3-dbg.debhelper.log
neil@holly:gcc-4.3-4.3.0$
Without &inhibit_log(); I get the following failure:
emdebuild: Compatibility levels before 4 are deprecated.
emdebuild: failed to write to debian/debhelper.log: No such file or
directory
Please make &inhibit_log the default and only allow logs where
explicitly required.
-- System Information:
Debian Release: lenny/sid
APT prefers unstable
APT policy: (500, 'unstable')
Architecture: amd64 (x86_64)
Kernel: Linux 2.6.22-2-amd64 (SMP w/1 CPU core)
Locale: LANG=en_GB.UTF-8, LC_CTYPE=en_GB.UTF-8 (charmap=UTF-8)
Shell: /bin/sh linked to /bin/bash
Versions of packages debhelper depends on:
ii binutils 2.18.1~cvs20080103-4+b1 The GNU assembler, linker and bina
ii dpkg-dev 1.14.18 package building tools for Debian
ii file 4.23-2 Determines file type using "magic"
ii html2text 1.3.2a-3 An advanced HTML to text converter
ii man-db 2.5.1-4 on-line manual pager
ii perl 5.8.8-12 Larry Wall's Practical Extraction
ii po-debconf 1.0.12.1 manage translated Debconf template
debhelper recommends no packages.
-- no debconf information
--- End Message ---
--- Begin Message ---
On Thu, 1 May 2008 12:33:27 -0400 Joey Hess <[email protected]> wrote:
> Neil Williams wrote:
> > > I can certianly see no reason for it to do so, since debhelper programs
> > > are out of devscripts' scope.
> >
> > ? debuild ? (upon which emdebuild is based) ?
>
> No, it certainly does not use debhelper code.
>
> > Can you at least assure me that &inhibit_log will retain current
> > behaviour until the Lenny release?
>
> Yes.
>
> --
> see shy jo
Hi,
In compat 10, we no longer create the log files by default. On the
other hand, debhelper has started to mandate a compat file, so the
situation has not really improved.
Anyway, I think I will echo Joey's remark about Dh_Lib is not a
general purpose library and close this bug here.
Mind you, I am open for extracting parts of it into a general purpose
library, if it would make sense. If there is anything you want in
particular, please file a bug for it and I will have a look at it.
Thanks,
~Niels
--- End Message ---
