Dear maintainer(s),

The Release Team considers packages that are out-of-sync between testing and unstable for more than 30 days as having a Release Critical bug in testing [1]. Your package src:gstreamer1.0 has been trying to migrate for 31 days [2], hence this bug report. The current output of the migration software for this package is copied to the bottom of this report and should list the reason why the package is blocked. Regularly, what needs to happen is reporting issues against reverse (build/test/regular) dependencies. Occasionally this has already been done, than this bug is just for tracking purposes.

If a package is out of sync between unstable and testing for a longer period, this usually means that bugs in the package in testing cannot be fixed via unstable. Blocked packages can have impact on other packages, which makes preparing for the release more difficult. The situation that caused this bug report might even be the result of such an issue. We expect maintainers to fix issues that hamper the migration of their package in a timely manner. If your package in this situation due to another package, consider helping out.

This bug will trigger auto-removal when appropriate. As with all new bugs, there will be at least 30 days before the package is auto-removed.

This bug submission immediately closes the bug with the version in unstable, so if that version or a later version migrates, this bug will no longer affect testing. This bug is also tagged to only affect sid and forky, so it doesn't affect (old-)stable.

If you believe your package is unable to migrate to testing due to issues beyond your control, don't hesitate to contact the Release Team.

This bug report has been automatically generated. If you have any comments with regards to the content or the process, please reach out to me.

Paul

[1] https://lists.debian.org/debian-devel-announce/2023/06/msg00001.html
[2] https://qa.debian.org/excuses.php?package=gstreamer1.0

Current text from [2]:
Migration status for gstreamer1.0 (1.28.4-2 to 1.28.6-1): BLOCKED: Rejected/violates migration policy/introduces a regression
Issues preventing migration:
∙ ∙ Autopkgtest for libreoffice/4:26.2.5.2-2: amd64: Pass, arm64: Test triggered (failure will be ignored), armhf: Test triggered (failure will be ignored), i386: Test triggered (failure will be ignored), ppc64el: Pass, s390x: Pass
∙ ∙ Autopkgtest for mopidy/3.4.2-8: amd64: Regression ♻ (reference ♻), arm64: Regression ♻ (reference ♻), armhf: Regression ♻ (reference ♻), i386: Regression ♻ (reference ♻), ppc64el: Regression ♻ (reference ♻), s390x: Regression ♻ (reference ♻)
Additional info (not blocking):
∙ ∙ Piuparts tested OK - https://piuparts.debian.org/sid/source/g/gstreamer1.0.html
∙ ∙ Reproduced on amd64 - info
∙ ∙ Reproduced on arm64 - info
∙ ∙ Reproduced on armhf - info
∙ ∙ Reproduced on i386 - info
∙ ∙ 10 days old (needed 5 days)

Initial investigation points to some fine tuning in the `typefind` element:

The test file that mopidy generates (single line) is detected as a
subtitle format:

```
$ GST_DEBUG=typefind*:5 gst-launch-1.0 filesrc
location=/home/marc/Development/salsa/mopidy/.pybuild/cpython3_3.13/build/tests/data/scanner/plain.txt
! typefind ! fakesink dump=0
0:00:00.008654079      44667      44667 DEBUG               typefind
gsttypefindelement.c:409:gst_type_find_handle_src_query:<typefindelement0>
Handling src query caps
0:00:00.008670771      44667      44667 DEBUG               typefind
gsttypefindelement.c:419:gst_type_find_handle_src_query:<typefindelement0>
Got caps query, our caps are (NULL)
0:00:00.008685844      44667      44667 DEBUG               typefind
gsttypefindelement.c:409:gst_type_find_handle_src_query:<typefindelement0>
Handling src query caps
0:00:00.008688759      44667      44667 DEBUG               typefind
gsttypefindelement.c:419:gst_type_find_handle_src_query:<typefindelement0>
Got caps query, our caps are (NULL)
Setting pipeline to PAUSED ...
Pipeline is PREROLLING ...
0:00:00.009315864      44667      44669 DEBUG               typefind
gsttypefindelement.c:409:gst_type_find_handle_src_query:<typefindelement0>
Handling src query uri
0:00:00.009340142      44667      44669 DEBUG               typefind
gsttypefindelement.c:1114:gst_type_find_element_loop:<typefindelement0>
Pushing STREAM_START
0:00:00.009355903      44667      44669 DEBUG               typefind
gsttypefindelement.c:1128:gst_type_find_element_loop:<typefindelement0>
find type in pull mode
0:00:00.009367582      44667      44669 DEBUG               typefind
gsttypefindelement.c:823:gst_type_find_get_extension:<typefindelement0>
finding extension of
file:///home/marc/Development/salsa/mopidy/.pybuild/cpython3_3.13/build/tests/data/scanner/plain.txt
0:00:00.009396859      44667      44669 DEBUG               typefind
gsttypefindelement.c:846:gst_type_find_get_extension:<typefindelement0>
found extension txt
0:00:00.015174636      44667      44669 DEBUG               typefind
gsttypefindelement.c:1169:gst_type_find_element_loop: Found caps
(NULL)
0:00:00.015183905      44667      44669 DEBUG               typefind
gsttypefindelement.c:1179:gst_type_find_element_loop: Trying to guess
using extension
0:00:00.015190564      44667      44669 DEBUG               typefind
gsttypefindelement.c:823:gst_type_find_get_extension:<typefindelement0>
finding extension of
file:///home/marc/Development/salsa/mopidy/.pybuild/cpython3_3.13/build/tests/data/scanner/plain.txt
0:00:00.015199078      44667      44669 DEBUG               typefind
gsttypefindelement.c:846:gst_type_find_get_extension:<typefindelement0>
found extension txt
0:00:00.015330116      44667      44669 DEBUG               typefind
gsttypefindelement.c:1192:gst_type_find_element_loop: Emitting found
caps application/x-subtitle
0:00:00.015339495      44667      44669 INFO                typefind
gsttypefindelement.c:183:gst_type_find_element_have_type:<typefindelement0>
found caps application/x-subtitle, probability=100
Pipeline is PREROLLED ...
Setting pipeline to PLAYING ...
0:00:00.015608737      44667      44667 DEBUG               typefind
gsttypefindelement.c:409:gst_type_find_handle_src_query:<typefindelement0>
Handling src query latency
Redistribute latency...
0:00:00.015698777      44667      44667 DEBUG               typefind
gsttypefindelement.c:409:gst_type_find_handle_src_query:<typefindelement0>
Handling src query latency
New clock: GstSystemClock
Got EOS from element "pipeline0".
Execution ended after 0:00:00.000245248
Setting pipeline to NULL ...
Freeing pipeline ...

```

While a longer text format is detected as text:

```
$ GST_DEBUG=typefind*:5 gst-launch-1.0 filesrc
location=/home/marc/vivotek-bug.txt ! typefind ! fakesink dump=0
0:00:00.008476834      44713      44713 DEBUG               typefind
gsttypefindelement.c:409:gst_type_find_handle_src_query:<typefindelement0>
Handling src query caps
0:00:00.008488294      44713      44713 DEBUG               typefind
gsttypefindelement.c:419:gst_type_find_handle_src_query:<typefindelement0>
Got caps query, our caps are (NULL)
0:00:00.008494098      44713      44713 DEBUG               typefind
gsttypefindelement.c:409:gst_type_find_handle_src_query:<typefindelement0>
Handling src query caps
0:00:00.008497422      44713      44713 DEBUG               typefind
gsttypefindelement.c:419:gst_type_find_handle_src_query:<typefindelement0>
Got caps query, our caps are (NULL)
Setting pipeline to PAUSED ...
Pipeline is PREROLLING ...
0:00:00.009285388      44713      44715 DEBUG               typefind
gsttypefindelement.c:409:gst_type_find_handle_src_query:<typefindelement0>
Handling src query uri
0:00:00.009322194      44713      44715 DEBUG               typefind
gsttypefindelement.c:1114:gst_type_find_element_loop:<typefindelement0>
Pushing STREAM_START
0:00:00.009344733      44713      44715 DEBUG               typefind
gsttypefindelement.c:1128:gst_type_find_element_loop:<typefindelement0>
find type in pull mode
0:00:00.009361943      44713      44715 DEBUG               typefind
gsttypefindelement.c:823:gst_type_find_get_extension:<typefindelement0>
finding extension of file:///home/marc/vivotek-bug.txt
0:00:00.009392056      44713      44715 DEBUG               typefind
gsttypefindelement.c:846:gst_type_find_get_extension:<typefindelement0>
found extension txt
0:00:00.016466129      44713      44715 DEBUG               typefind
gsttypefindelement.c:1169:gst_type_find_element_loop: Found caps
text/plain
0:00:00.016472763      44713      44715 DEBUG               typefind
gsttypefindelement.c:1192:gst_type_find_element_loop: Emitting found
caps text/plain
0:00:00.016482456      44713      44715 INFO                typefind
gsttypefindelement.c:183:gst_type_find_element_have_type:<typefindelement0>
found caps text/plain, probability=85
Pipeline is PREROLLED ...
Setting pipeline to PLAYING ...
0:00:00.016683200      44713      44713 DEBUG               typefind
gsttypefindelement.c:409:gst_type_find_handle_src_query:<typefindelement0>
Handling src query latency
Redistribute latency...
0:00:00.016720517      44713      44713 DEBUG               typefind
gsttypefindelement.c:409:gst_type_find_handle_src_query:<typefindelement0>
Handling src query latency
New clock: GstSystemClock
Got EOS from element "pipeline0".
Execution ended after 0:00:00.000107546
Setting pipeline to NULL ...
Freeing pipeline ...

```

When a longer text is added, the test succeeds. I suggest updating the
test in Mopidy to provide a more relevant text input.

reassign 1144521 mopidy
tags 1144521 + patch
thanks

I am re-assigning this to mopidy because I think the test on
`plain.txt` has too little context to succeed. Minor improvements in
typefind (gst-plugins-base1.0) result in the single line text file to
be detected as a subtitle format.

The patch attached extends the plain.txt file with an extra line and
lets the test succeed again.