Your message dated Mon, 14 Jun 2010 15:55:42 +0200
with message-id <20100614135542.gb27...@an3as.eu>
and subject line Re: Bug#585666: feh: FTBFS: Relies on writable home directory?
has caused the Debian Bug report #585666,
regarding feh: FTBFS: Relies on writable home directory?
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 ow...@bugs.debian.org
immediately.)
--
585666: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=585666
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Source: feh
Version: 1.6.1-1
Severity: serious
Justification: FTBFS
Hi,
it looks like feh FTBFS when the home directory is missing or
write-protected:
| # Failed test 'missing arguments print usage (stderr)'
| # at test/feh.t line 44.
| # got: 'feh WARNING: Unable to create default config file
/home/buildd/.fehrc
| #
| # feh - No loadable images specified.
| # Use feh --help for detailed usage information
| # '
| # expected: 'feh - No loadable images specified.
| # Use feh --help for detailed usage information
| # '
|
| # Failed test 'stderr_is_eq: src/feh --loadable test/ok.* test/fail.*, '
| # at test/feh.t line 59.
| # got: 'feh WARNING: Unable to create default config file
/home/buildd/.fehrc
| #
| # '
| # expected: ''
|
| # Failed test 'stderr_is_eq: src/feh --unloadable test/ok.* test/fail.*, '
| # at test/feh.t line 65.
| # got: 'feh WARNING: Unable to create default config file
/home/buildd/.fehrc
| #
| # '
| # expected: ''
|
| # Failed test 'stderr_is_eq: src/feh --list --quiet test/ok.* test/fail.*, '
| # at test/feh.t line 97.
| # got: 'feh WARNING: Unable to create default config file
/home/buildd/.fehrc
| #
| # '
| # expected: ''
| # Looks like you failed 4 tests of 48.
| test/feh.t .....
| Dubious, test returned 4 (wstat 1024, 0x400)
| Failed 4/48 subtests
Being unable to deal with .fehrc seems to lead to extra messages,
breaking the comparison with the reference strings.
[ BTW, looks like you could run some more tests:
Can't exec "mandoc": No such file or directory at test/mandoc.t line 8.
test/mandoc.t .. ok ]
Full build logs:
https://buildd.debian.org/status/package.php?p=feh
Mraw,
KiBi.
--- End Message ---
--- Begin Message ---
Hi,
uhmm, just forgt to close the bug in the changelog of the upload - doing
it now manually.
Kind regards
Andreas.
On Mon, Jun 14, 2010 at 01:11:45PM +0200, Daniel Friesel wrote:
> Hi,
>
> I'm the feh upstream.
>
> On Sat, Jun 12, 2010 at 11:50:39PM +0200, Cyril Brulebois wrote:
> > it looks like feh FTBFS when the home directory is missing or
> > write-protected:
> [...]
> > Being unable to deal with .fehrc seems to lead to extra messages,
> > breaking the comparison with the reference strings.
>
> I have fixed this issue (or at least I think I did) in feh 1.7, which should
> reach the Debian repositories some time soon - I've already notified the
> maintainer of the new release and the fixed test cases.
>
> > [ BTW, looks like you could run some more tests:
> > Can't exec "mandoc": No such file or directory at test/mandoc.t line 8.
> > test/mandoc.t .. ok ]
>
> I use mandoc to test if the documentation is valid. However, since there is no
> Debian package for mandoc, the test is skipped if it cannot execute mandoc.
>
> In that case, the above error message is produced, but it does not mean test
> failure. This should be clearer in feh 1.7 thanks to an extra diagnostic
> message.
>
> --derf
--
http://fam-tille.de
--- End Message ---
