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

Bug#947293: marked as done (libkate: autopkgtest failures due to libkate-tools removal)



Your message dated Mon, 30 Dec 2019 22:06:04 +0100
with message-id <20191230210604.GA2645@pisco.westfalen.local>
and subject line Re: Bug#947293: libkate: autopkgtest failures due to libkate-tools removal
has caused the Debian Bug report #947293,
regarding libkate: autopkgtest failures due to libkate-tools removal
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 owner@bugs.debian.org
immediately.)


-- 
947293: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=947293
Debian Bug Tracking System
Contact owner@bugs.debian.org with problems
--- Begin Message ---
Package: libkate
Version: 0.4.1-10
Severity: serious
Tags: patch
Justification: autopkgtest regression
User: ubuntu-devel@lists.ubuntu.com
Usertags: origin-ubuntu focal ubuntu-patch

Dear maintainers,

With the removal of libkate-tools in libkate 0.4.1-10, the libkate
autopkgtest consistently fails, because all of the commands it previously
attempted to run were in the libkate-tools package:

[...]
autopkgtest [12:55:24]: test test-cmd-tools:  - - - - - - - - - - stderr - - - - - - - - - -
/tmp/autopkgtest-lxc.c5qiodhi/downtmp/build.Liw/src/debian/tests/test-cmd-tools: 25: kateenc: not found
/tmp/autopkgtest-lxc.c5qiodhi/downtmp/build.Liw/src/debian/tests/test-cmd-tools: 31: katalyzer: not found
/tmp/autopkgtest-lxc.c5qiodhi/downtmp/build.Liw/src/debian/tests/test-cmd-tools: 37: katedec: not found
/tmp/autopkgtest-lxc.c5qiodhi/downtmp/build.Liw/src/debian/tests/test-cmd-tools: 40: errorunable to run katedec: not found
[...]

  (https://ci.debian.net/data/autopkgtest/unstable/amd64/libk/libkate/3520793/log.gz)

I think the autopkgtest should simply be dropped, since there is nothing
left for it to do at present.  Please see the attached patch.

Cheers,
-- 
Steve Langasek                   Give me a lever long enough and a Free OS
Debian Developer                   to set it on, and I can move the world.
Ubuntu Developer                                   https://www.debian.org/
slangasek@ubuntu.com                                     vorlon@debian.org
diff -Nru libkate-0.4.1/debian/tests/control libkate-0.4.1/debian/tests/control
--- libkate-0.4.1/debian/tests/control	2019-11-26 16:03:42.000000000 -0600
+++ libkate-0.4.1/debian/tests/control	1969-12-31 18:00:00.000000000 -0600
@@ -1,2 +0,0 @@
-Depends: @
-Tests: test-cmd-tools
diff -Nru libkate-0.4.1/debian/tests/test-cmd-tools libkate-0.4.1/debian/tests/test-cmd-tools
--- libkate-0.4.1/debian/tests/test-cmd-tools	2019-11-26 16:03:42.000000000 -0600
+++ libkate-0.4.1/debian/tests/test-cmd-tools	1969-12-31 18:00:00.000000000 -0600
@@ -1,49 +0,0 @@
-#!/bin/sh
-#
-# Test the kate command line tools to ensure they can run without
-# returning an error.
-
-set -e
-
-retval=0
-
-success() { echo "success:" "$@"; }
-error() { echo "error:" "$@"; retval=1; }
-
-cat > input.srt <<EOF
-1
-00:00:08,000 --> 00:00:14,000
-This is a simple subtext block
-that will be encoded into an ogg file.
-
-2
-00:00:15,000 --> 00:00:16,000
-This is the second subtext block.
-
-EOF
-
-if kateenc -t srt -l cy -c SUB -o output.ogg input.srt ; then
-    success "kateenc could encode an SRT file to OGG"
-else
-    error "unable to run kateenc"
-fi
-
-if katalyzer output.ogg ; then
-    success "running katalyzer worked"
-else
-    error "unable to run katalyser"
-fi
-
-if katedec output.ogg ; then
-    success "running katedec worked"
-else
-    error"unable to run katedec"
-fi
-
-if KateDJ  --version ; then
-    success "running KateDJ worked"
-else
-    error "unable to run KateDJ"
-fi
-
-exit $retval

--- End Message ---
--- Begin Message ---
Version: 0.4.1-11

This was fixed in 0.4.1-11, which missed a "Closes:"

Cheers,
        Moritz

--- End Message ---

Reply to: