Bug#1001827: minder FTBFS: error: lvalue required as unary ‘&’ operand
Control: reassign -1 valac 0.54.5-1 Control: affects -1 src:minder Control: close -1 0.54.6-1 On Fri, Dec 17, 2021 at 08:45:21AM +0100, Helmut Grohne wrote: > Source: minder > Version: 1.13.1-1 > Severity: serious > Tags: ftbfs > > minder fails to build from source in unstable. A non-parallel build now > ends as follows: > > | FAILED: com.github.phase1geo.minder.p/meson-generated_src_DrawArea.c.o > | cc -Icom.github.phase1geo.minder.p -I. -I.. -I/usr/include/glib-2.0 > -I/usr/lib/x86_64-linux-gnu/glib-2.0/include -I/usr/include/cairo > -I/usr/include/pixman-1 -I/usr/include/uuid -I/usr/include/freetype2 > -I/usr/include/libpng16 -I/usr/include/gee-0.8 -I/usr/include/granite > -I/usr/include/gtk-3.0 -I/usr/include/at-spi2-atk/2.0 > -I/usr/include/at-spi-2.0 -I/usr/include/dbus-1.0 > -I/usr/lib/x86_64-linux-gnu/dbus-1.0/include -I/usr/include/gio-unix-2.0 > -I/usr/include/pango-1.0 -I/usr/include/harfbuzz -I/usr/include/fribidi > -I/usr/include/atk-1.0 -I/usr/include/gdk-pixbuf-2.0 > -I/usr/include/x86_64-linux-gnu -I/usr/include/libmount -I/usr/include/blkid > -I/usr/include/libxml2 -I/usr/include/gtksourceview-4 > -I/usr/include/libhandy-1 -fdiagnostics-color=always -D_FILE_OFFSET_BITS=64 > -w '-DGETTEXT_PACKAGE="com.github.phase1geo.minder"' -g -O2 > -ffile-prefix-map=/<>=. -fstack-protector-strong -Wformat > -Werror=format-security -Wdate-time -D_FORTIFY_SOURCE=2 -pthread -include > config.h -MD -MQ > com.github.phase1geo.minder.p/meson-generated_src_DrawArea.c.o -MF > com.github.phase1geo.minder.p/meson-generated_src_DrawArea.c.o.d -o > com.github.phase1geo.minder.p/meson-generated_src_DrawArea.c.o -c > com.github.phase1geo.minder.p/src/DrawArea.c > | com.github.phase1geo.minder.p/src/DrawArea.c: In function > ‘draw_area_set_node_mode’: > | com.github.phase1geo.minder.p/src/DrawArea.c:6007:53: error: lvalue > required as unary ‘&’ operand > | 6007 | draw_area_set_cursor (self, > _AREA_text_cursor); > | | ^ > | com.github.phase1geo.minder.p/src/DrawArea.c: In function > ‘draw_area_set_connection_mode’: > | com.github.phase1geo.minder.p/src/DrawArea.c:6137:53: error: lvalue > required as unary ‘&’ operand > | 6137 | draw_area_set_cursor (self, > _AREA_text_cursor); > | | ^ > | com.github.phase1geo.minder.p/src/DrawArea.c: In function > ‘draw_area_on_motion’: > | com.github.phase1geo.minder.p/src/DrawArea.c:11162:149: error: lvalue > required as unary ‘&’ operand > | 11162 | > draw_area_set_cursor > (self, _AREA_url_cursor); > | | > > ^ > | com.github.phase1geo.minder.p/src/DrawArea.c:11174:149: error: lvalue > required as unary ‘&’ operand > | 11174 | > draw_area_set_cursor > (self, _AREA_text_cursor); > | | > > ^ > | com.github.phase1geo.minder.p/src/DrawArea.c: In function > ‘draw_area_handle_control’: > | com.github.phase1geo.minder.p/src/DrawArea.c:19241:85: error: lvalue > required as unary ‘&’ operand > | 19241 | > draw_area_set_cursor (self, _AREA_url_cursor); > | | > ^ > | ninja: build stopped: subcommand failed. > | dh_auto_build: error: cd obj-x86_64-linux-gnu && LC_ALL=C.UTF-8 ninja -j1 > -v returned exit code 1 > | make: *** [debian/rules:12: binary] Error 25 > | dpkg-buildpackage: error: debian/rules binary subprocess returned exit > status 2 It now builds again: https://tests.reproducible-builds.org/debian/rb-pkg/unstable/amd64/minder.html src/DrawArea.c is generated by valac, I'm reassigning this bug there since it was likely there and fixed in 0.54.6. > Helmut cu Adrian
Bug#1003714: ITP: oci-cli -- Command Line Interface for Oracle Cloud Infrastructure
On 1/14/22 07:03, Paul Wise wrote: Package: wnpp Severity: wishlist Owner: Paul Wise X-Debbugs-Cc: debian-de...@lists.debian.org, debian-cl...@lists.debian.org Control: block -1 by 1003372 * Package name: oci-cli Version : 3.4.1 Upstream Author : Mike Ross and others at Oracle * URL : https://docs.cloud.oracle.com/Content/API/Concepts/cliconcepts.htm * License : Universal Permissive License or Apache Programming Lang: Python Description : Command Line Interface for Oracle Cloud Infrastructure This package is needed by my employer for managing their OCI instances. I plan to maintain it within the Debian Cloud Team after joining it. It depends on oci-python-sdk, which I also intend to package (#1003372). Hi, Just please make sure it doesn't conflict with: packages.debian.org/openstack-cluster-installer-cli Hopefully, yours will be oci-cli, when mine is ocicli ... Cheers, Thomas Goirand (zigo)
Bug#1003650: firejail-profiles: Chromium running under the current profile cannot play sound
On Sat, Jan 15, 2022 at 11:07:30AM +0800, Mad Horse wrote:
> I do not have any custom setup on my pipewire, nor custom firejail profile
> for chromium.
Do I understand it correctly that you are also using pipewire?
> Started within firejail, chromium reported:
>
> > [10:46:0115/104317.720203:ERROR:bus.cc(397)] Failed to connect to the
> > bus: Failed to connect to socket /run/firejail/mnt/dbus/system:
> > Permission denied
> > libva error: /usr/lib/x86_64-linux-gnu/dri/iHD_drv_video.so init failed
> > [56:56:0115/104317.772250:ERROR:sandbox_linux.cc(378)]
> > InitializeSandbox() called with multiple threads in process gpu-process.
> > [10:85:0115/104317.887055:ERROR:bus.cc(397)] Failed to connect to the
> > bus: Failed to connect to socket /run/firejail/mnt/dbus/system:
> > Permission denied
> > [10:85:0115/104317.887112:ERROR:bus.cc(397)] Failed to connect to the
> > bus: Failed to connect to socket /run/firejail/mnt/dbus/system:
> > Permission denied
> > [10:85:0115/104317.887169:ERROR:bus.cc(397)] Failed to connect to the
> > bus: Failed to connect to socket /run/firejail/mnt/dbus/system:
> > Permission denied
> > [10:85:0115/104317.887206:ERROR:bus.cc(397)] Failed to connect to the
> > bus: Failed to connect to socket /run/firejail/mnt/dbus/system:
> > Permission denied
> > [10:85:0115/104317.887235:ERROR:bus.cc(397)] Failed to connect to the
> > bus: Failed to connect to socket /run/firejail/mnt/dbus/system:
> > Permission denied
> /run/firejail/mnt/dbus/system do have permission 600, owned by root.
I think they are not related. I see these messages as well, but sound is
working for me.
> When trying to play sound, chromium in firejail reported:
>
> > Failed to create secure directory (/run/user/1000/pulse): Operation not
> > permitted
> > ALSA lib dlmisc.c:337:(snd_dlobj_cache_get0) Cannot open shared library
> > libasound_module_pcm_pulse.so
> > (/usr/lib/x86_64-linux-gnu/alsa-lib/libasound_module_pcm_pulse.so:
> > cannot open shared object file: Permission denied)
> > [307:307:0115/104404.402900:ERROR:alsa_util.cc(204)] PcmOpen: default,No
> > such device or address
> > ALSA lib dlmisc.c:337:(snd_dlobj_cache_get0) Cannot open shared library
> > libasound_module_pcm_pulse.so
> > (/usr/lib/x86_64-linux-gnu/alsa-lib/libasound_module_pcm_pulse.so:
> > cannot open shared object file: Permission denied)
> > [307:307:0115/104404.404678:ERROR:alsa_util.cc(204)] PcmOpen:
> > plug:default,No such device or address
>
> but there is a unix domain socket /run/user/1000/pulse/native, owned by UID
> 1000, with permission 666,
> and the permission of
> /usr/lib/x86_64-linux-gnu/alsa-lib/libasound_module_pcm_pulse.so is
> root,644.
> Both were inspected inside firejail for chromium.
>
> Do you have any idea about these?
Assuming that you are using pipewire, can you please add the following
to your chromium.profile (or chromium.local):
> whitelist ${RUNUSER}/pipewire-?
> whitelist /usr/share/pipewire
Kind regards,
Reiner
signature.asc
Description: PGP signature
Bug#1001168: Info received (Bug#1001168: Info received (Bug#1001168: hkl: FTBFS on mipsel: FAIL: trajectory.py))
On Fri, 14 Jan 2022 23:34:57 +0800 YunQiang Su wrote: > 在 2022/1/14 23:30, Sandro Tosi 写道: > > On Fri, Jan 14, 2022 at 9:24 AM YunQiang Su > > wrote: > >> > >> On Mon, 3 Jan 2022 22:56:58 +0100 (CET) PICCA Frederic-emmanuel > >> wrote: > >> > Built with gcc-11 and -fno-lto it doesn not work. > >> > > >> > > >> (sid_mips64el-dchroot)picca@eller:~/matplotlib/build/lib.linux-mips64-3.9$ > >> ../../../test.py > >> > Segmentation fault > >> > > >> (sid_mips64el-dchroot)picca@eller:~/matplotlib/build/lib.linux-mips64-3.9$ > >> PYTHONPATH=. ../../../test.py > >> > Segmentation fault > >> > > >> > > >> > >> It seems due to gcc-11. > >> > >> I tried to build with gcc-10 on sid, it works again. > > > > yes, that's what PICCA found and reported at > > https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1001168#72 > > > > are you going to look into a fix for gcc-11? > > > > Sure, I will dig it, since it may effect lots of other packages. > It is strange that -O1/-O2 fail, while -O0/-O3 succeed... > > Thanks, > > >
Bug#1003763: FTBFS: fails test fails test test_billion_laughs - just varying whitespace?
Package: python3-html-sanitizer Version: 1.9.1-2 Severity: serious Tags: ftbfs -BEGIN PGP SIGNED MESSAGE- Hash: SHA512 Building html-sanitizer 1.9.2 officially on Debian fails the test test_billion_laughs: https://buildd.debian.org/status/fetch.php?pkg=python-html-sanitizer=all=1.9.2-1=1642027358=0 FAIL: test_billion_laughs (html_sanitizer.tests.SanitizerTestCase) (before='\n\n \n \n \n \n \n \n \n \n \n \n]>\n\n', after=' ] lol9; ') - -- Traceback (most recent call last): File "/<>/.pybuild/cpython3_3.9/build/html_sanitizer/tests.py", line 15, in run_tests self.assertEqual( AssertionError: '] lol9; ' != ' ] lol9; ' - - ] lol9; + ] lol9; ? + : Cleaning 'b'\\n\\n \\n \\n \\n \\n \\n \\n \\n \\n \\n \\n]>\\n\\n'', expected 'b' ] lol9; '' but got 'b'] lol9; '' - Jonas -BEGIN PGP SIGNATURE- iQIzBAEBCgAdFiEEn+Ppw2aRpp/1PMaELHwxRsGgASEFAmHiq44ACgkQLHwxRsGg ASHzAw//chfsKnYHMOGJIzu+dUjiK8Uzk+I7gcPDMI1v7dLXoLKZttUuSdPXgrU6 NyJROI767DFVoi97fkspoySlUfic4CrgIgzxq3MpXTzdvOUwIUkDvNYeXF4Y99KH cLXW+tznHhOz4nlLw0gwOWKsyhPdjaHDva6zetKje+gwvnoTpWWGXBpcZaWJ2zC2 Mq+tUzQDKzYKPa+Mu3zjsxhAU5vd17Lcz+xKz5DZHHc1ELOpgsRKocEkOq+F+ZpL TrwqYTcqnaJ3s1riJxgybFidNuWhwBEvj4nMticNxEwOyg9E18h41NE/rj97OCCR jhHKSf9aW758Enz7aKiBh0OznOsjUoQxGJaX7emUSjxN1xGsTebHRaS75DJlM0kD zPnzcwWwI0Yg0GBpvpipYG/0oRXqqBRqXJSskokuoGkpIEFGyf9DTviIDlRHj7MW Kl6S4waVPseuSF5oTTGR5Kk9JsqLKQxnmWix6md2UU7uppHo+EBDm9LEqEG6pEo4 WRgkuFE4Z+UvQje4adZKitbmaR0zm38D/7rgMu5SYSbvtkM25GGkZJk9s4c65rUe qS5Mn3f24F54BMjFLMdxvVHCD9iSPgXTyF2ybZ/869hYrfdOw30vxWTjQjNyjXQ0 Gvm3vWEAvYY2YCIyF0mgpnN0bvdnBomwlntMYYwZUvY5bVFqwMo= =qFK2 -END PGP SIGNATURE-
Bug#1003574: segfault in libc-2.33.so during i386 boot ofde QEMU VM
control: reopen -1 control: merge 1003610 -1 control: severity -1 serious control: found -1 glibc/2.33-1 control: forwarded -1 https://sourceware.org/bugzilla/show_bug.cgi?id=28784 On 2022-01-12 14:08, Christian Kastner wrote: > Hi Aurelien, > > thank you for the quick reply. > > On 2022-01-12 11:45, Aurelien Jarno wrote: > >> # Boot image. -enable-kvm assumes that this is being tested on amd64 > >> # Optionally use -nographic for terminal output instead of GUI > >> $ qemu-system-i386 \ > >>-machine q35 \ > >>-enable-kvm \ > > > > You might also want to try without -enable-kvm > > Indeed, this fixed the issue. > > So sorry for the noise. I was 120% sure that I had tried that. My turn to be sorry, it appears to be a genuine issue on the GNU libc side, and changing the CPU definition in QEMU, either with -cpu or by disabling kvm) just hide the bug. I was not able to reproduce the issue as you need a non-Intel CPU to get the issue with the command line your provided. This bug also affects via C7 CPUs. I have reported the issue upstream and provided a patch, currently waiting for review. Regards, Aurelien -- Aurelien Jarno GPG: 4096R/1DDD8C9B aurel...@aurel32.net http://www.aurel32.net
Bug#1003762: RFP: gvls -- GNOME Vala Language Server library
Package: wnpp Severity: wishlist * Package name: gvls Version : 20.1 (2021-10-20) Upstream Author : Daniel Espinosa Ortiz * URL or Web page : https://gitlab.gnome.org/esodan/gvls * License : LGPL-2.1+ Description : GNOME Vala Language Server library Provides a set of objects useful to parse, navigate and provide syntax highligth, among others. . Currently it provides: * Tree of symbol servers, one per file to parse * Automatic loading of VAPI files referenced by using directive * Multi-file parse for symbol search * Document Symbol map useful for syntax highlight
Bug#1003313: closed by Debian FTP Masters (reply to Daniel Kahn Gillmor ) (Bug#1003313: fixed in libgpg-error 1.43-2)
Control: reopen -1 Hi Daniel, On Fri, Jan 14, 2022 at 02:39:05PM +, Debian Bug Tracking System wrote: > #1003313: libgpg-error FTCBFS for musl: refuses to use generic lock object > detection > > It has been closed by Debian FTP Masters > (reply to Daniel Kahn Gillmor ). I disagree. The version proposed by me was: > -*-*-linux-gnu*) > +*-*-linux-*) The version that actually ended up upstream was: +*-*-linux-gnu* | *-*-linux-musl) The thing that it doesn't match is: arm-linux-musleabihf Helmut
Bug#1003710: Acknowledgement (stardict crash in gnome with message Segmentation fault)
Dear Maintainer, For newly created users, the problem is the same. On 1/14/22 11:33, Debian Bug Tracking System wrote: Thank you for filing a new Bug report with Debian. You can follow progress on this Bug here: 1003710: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1003710. This is an automatically generated reply to let you know your message has been received. Your message is being forwarded to the package maintainers and other interested parties for their attention; they will reply in due course. As you requested using X-Debbugs-CC, your message was also forwarded to ql...@whu.edu.cn (after having been given a Bug report number, if it did not have one). Your message has been sent to the package maintainer(s): xiao sheng wen If you wish to submit further information on this problem, please send it to 1003...@bugs.debian.org. Please do not send mail to ow...@bugs.debian.org unless you wish to report a problem with the Bug-tracking system.
Bug#1003592: pysdl2: autopkgtest needs update for new version of libsdl2-ttf: text rendered 1px narrower than expected
unsubscribe
On Wed, Jan 12, 2022 at 12:39 PM Simon McVittie wrote:
> Source: pysdl2
> Version: 0.9.9+dfsg1-1
> Severity: important
> X-Debbugs-Cc: debian...@lists.debian.org
> Tags: experimental
> User: debian...@lists.debian.org
> Usertags: needs-update
> Control: affects -1 src:libsdl2-ttf
>
> When libsdl2-ttf git snapshots from experimental are used in the
> autopkgtest for pysdl2 from unstable, two tests fail:
>
> > sdlttf.TTF_SizeText(font, b"Hi there!", byref(w), byref(h))
> > > assert w.value == expected_w
> > E assert 69 == 70
> > E +69
> > E -70
> ...
> > sdlttf.TTF_SizeUTF8(font, u"Hï thère!".encode('utf-8'),
> byref(w), byref(h))
> > > assert w.value == expected_w
> > E assert 72 == 73
> > E +72
> > E -73
>
> (Example logs:
>
> https://ci.debian.net/data/autopkgtest/unstable/amd64/p/pysdl2/18161524/log.gz
> ,
>
> https://ci.debian.net/data/autopkgtest/unstable/arm64/p/pysdl2/18161611/log.gz
> )
>
> I'm about to upload the final release of libsdl2-ttf 2.0.18, which I
> suspect will have the same behaviour as this prerelease. 2.0.18 uses
> Harfbuzz for better support for non-Latin text and 2.0.15 did not,
> which might explain the different width; I don't think SDL_ttf aims to
> make any particular guarantee that text will render as exactly the same
> pixels in each version.
>
> You can see this in the "pseudo-excuses" report for experimental, which
> asks
> what would happen if experimental -> unstable had a migration process
> similar
> to unstable -> testing:
>
> https://release.debian.org/britney/pseudo-excuses-experimental.html#libsdl2-ttf
>
> The affected version is currently only in experimental, but it is likely
> to be uploaded to unstable soon, at which point this will become RC.
>
> Please update the test's expectations. There seems to be some support for
> having several expected values for height, so adding the same thing for
> width would make sense.
>
> Thanks,
> smcv
>
>
Bug#1003755: mailutils: mail(1) completely broken, fails with "undefined symbol: mu_stream_timed_getdelim" on start
severity 1003755 normal thanks Hi, El ds. 15 de 01 de 2022 a les 05:10 +0100, en/na наб va escriure: > Package: mailutils > Version: 1:3.14-1 > Severity: grave > Justification: renders package unusable > > Dear Maintainer, > > I upgraded today; > the changelog in my root mail (heh) shows just 1:3.14-1, > so this is broken vs. previous (1:3.13-1). > > When running mail(1), at all, it doesn't: > -- >8 -- > $ mail > mail: symbol lookup error: mail: undefined symbol: > mu_stream_timed_getdelim > $ date | mail -s test > mail: symbol lookup error: mail: undefined symbol: > mu_stream_timed_getdelim > -- >8 -- I can't reproduce this. One of these two might be important: > Architecture: x32 (x86_64) Ie, a x32 specific issue Or more probably: > Versions of packages mailutils depends on: > ii libmailutils8 1:3.13-1 > ii mailutils-common 1:3.14-1 This version mismatch between mailutils and its libs. It shouldn't happen, but if this is the problem, I'll look into it and will tighten the dependency. Jordi -- Jordi Mallach Debian Project
Bug#1003761: libxml-libxml-perl FTCBFS: uses the build architecture pkg-config
Source: libxml-libxml-perl Version: 2.0207+dfsg-1 Tags: patch User: debian-cr...@lists.debian.org Usertags: ftcbfs libxml-libxml-perl fails to cross build from source, because debian/rules hard codes the build architecture pkg-config. Seeding it from dpkg's buildtools.mk fixes the build. Please consider applying the attached patch. Helmut diff --minimal -Nru libxml-libxml-perl-2.0207+dfsg/debian/changelog libxml-libxml-perl-2.0207+dfsg/debian/changelog --- libxml-libxml-perl-2.0207+dfsg/debian/changelog 2022-01-14 22:46:30.0 +0100 +++ libxml-libxml-perl-2.0207+dfsg/debian/changelog 2022-01-15 09:05:08.0 +0100 @@ -1,3 +1,10 @@ +libxml-libxml-perl (2.0207+dfsg-1.1) UNRELEASED; urgency=medium + + * Non-maintainer upload. + * Fix FTCBFS: Use the host architecture pkg-config. (Closes: #-1) + + -- Helmut Grohne Sat, 15 Jan 2022 09:05:08 +0100 + libxml-libxml-perl (2.0207+dfsg-1) unstable; urgency=medium [ gregor herrmann ] diff --minimal -Nru libxml-libxml-perl-2.0207+dfsg/debian/rules libxml-libxml-perl-2.0207+dfsg/debian/rules --- libxml-libxml-perl-2.0207+dfsg/debian/rules 2022-01-14 22:46:30.0 +0100 +++ libxml-libxml-perl-2.0207+dfsg/debian/rules 2022-01-15 09:05:05.0 +0100 @@ -1,11 +1,13 @@ #!/usr/bin/make -f +include /usr/share/dpkg/buildtools.mk + # skip tests that need files we remove in the +dfsg version SKIP_TESTS = $(shell cat debian/tests/pkg-perl/smoke-skip) TEST_FILES = $(filter-out $(SKIP_TESTS), $(wildcard t/*.t)) -XML_LIBS := $(shell pkg-config --libs libxml-2.0) -XML_INC := $(shell pkg-config --cflags libxml-2.0) +XML_LIBS := $(shell $(PKG_CONFIG) --libs libxml-2.0) +XML_INC := $(shell $(PKG_CONFIG) --cflags libxml-2.0) export DEB_BUILD_MAINT_OPTIONS = hardening=+all
Bug#1003760: vdr-plugin-xineliboutput FTCBFS: builds for the build architecture
Source: vdr-plugin-xineliboutput Version: 2.2.0+git20211212-2 Tags: patch User: debian-cr...@lists.debian.org Usertags: ftcbfs vdr-plugin-xineliboutput fails to cross build from source for a number of reasons. It has a hand-written configure script that doesn't accept the standard autotools flags at all. Instead, one is supposed to pass build tools via flags like --cc=$(CC). Unfortunately, this isn't being done. Worse, it doesn't cover all the relevant tools and it has no provisions to select the host architecture pkg-config. Finally, it runs a tool mpg2c during build. This tool must not be built with the cross toolchain. The attached patch fixes all of these aspects and makes vdr-plugin-xineliboutput cross buildable. Please consider applying it. Helmut diff --minimal -Nru vdr-plugin-xineliboutput-2.2.0+git20211212/debian/changelog vdr-plugin-xineliboutput-2.2.0+git20211212/debian/changelog --- vdr-plugin-xineliboutput-2.2.0+git20211212/debian/changelog +++ vdr-plugin-xineliboutput-2.2.0+git20211212/debian/changelog @@ -1,3 +1,13 @@ +vdr-plugin-xineliboutput (2.2.0+git20211212-2.1) UNRELEASED; urgency=medium + + * Non-maintainer upload. + * Fix FTCBFS: (Closes: #-1) ++ Add --pkg-config flag to configure. ++ Pass all build tools to configure. ++ Build mpg2c.c with the build architecture compiler. + + -- Helmut Grohne Thu, 15 Jan 2022 06:20:04 +0100 + vdr-plugin-xineliboutput (2.2.0+git20211212-2) unstable; urgency=medium [ Tobias Grimm ] diff --minimal -Nru vdr-plugin-xineliboutput-2.2.0+git20211212/debian/patches/cross.patch vdr-plugin-xineliboutput-2.2.0+git20211212/debian/patches/cross.patch --- vdr-plugin-xineliboutput-2.2.0+git20211212/debian/patches/cross.patch +++ vdr-plugin-xineliboutput-2.2.0+git20211212/debian/patches/cross.patch @@ -0,0 +1,71 @@ +--- vdr-plugin-xineliboutput-2.2.0+git20211212.orig/configure vdr-plugin-xineliboutput-2.2.0+git20211212/configure +@@ -189,9 +189,9 @@ + if $PKG_CONFIG --exists $libname; then +if $PKG_CONFIG --libs $libname >/dev/null; then + add_flags LIBS_$subsys \ +- `pkg-config --libs-only-L $libname` \ +- `pkg-config --libs-only-l $libname` +-add_flags CFLAGS_$subsys `pkg-config --cflags-only-I $libname` ++ `$PKG_CONFIG --libs-only-L $libname` \ ++ `$PKG_CONFIG --libs-only-l $libname` ++add_flags CFLAGS_$subsys `$PKG_CONFIG --cflags-only-I $libname` + log "yes" + return 0 +fi +@@ -312,6 +312,7 @@ + echo " --disable-pkgconfigdo not use pkg-config" + echo " --cc=CCselect C compiler" + echo " --cxx=CXX select C++ compiler" ++ echo " --pkg-config=PKG-CONFIG select the pkg-config executable" + echo " --add-cflags=FLAGS add compiler flags" + } + +@@ -334,6 +335,10 @@ + CXX=$optval + logdbg "C++ compiler: $CXX" + ;; ++--pkg-config=?*) ++ PKG_CONFIG=$optval ++ logdbg "pkg-config: $PKG_CONFIG" ++ ;; + --add-cflags=?*) + CFLAGS="$CFLAGS $optval" + logdbg "CFLAGS: $CFLAGS" +@@ -517,6 +522,7 @@ + # cc/ld flags + echo "CC = $CC">>$makefile + echo "CXX = $CXX">>$makefile ++echo "PKG_CONFIG = $PKG_CONFIG">>$makefile + echo "CFLAGS_XINE += $CFLAGS_XINE">>$makefile + echo "CFLAGS_VDR += $CFLAGS_VDR">>$makefile + echo "CFLAGS_X11 += $CFLAGS_X11">>$makefile +--- vdr-plugin-xineliboutput-2.2.0+git20211212.orig/Makefile vdr-plugin-xineliboutput-2.2.0+git20211212/Makefile +@@ -45,6 +45,8 @@ + + CXX ?= g++ + CC ?= gcc ++PKG_CONFIG ?= pkg-config ++CC_FOR_BUILD ?= gcc + OPTFLAGS ?= + + ifeq ($(ARCH_APPLE_DARWIN), yes) +@@ -63,7 +65,7 @@ + ### + + # Use package data if installed...otherwise assume we're under the VDR source directory: +-PKGCFG = $(if $(VDRDIR),$(shell pkg-config --variable=$(1) $(VDRDIR)/vdr.pc),$(shell PKG_CONFIG_PATH="$$PKG_CONFIG_PATH:../../.." pkg-config --variable=$(1) vdr)) ++PKGCFG = $(if $(VDRDIR),$(shell $(PKG_CONFIG) --variable=$(1) $(VDRDIR)/vdr.pc),$(shell $(PKG_CONFIG) --variable=$(1) vdr)) + BINDIR = $(call PKGCFG,bindir) + LIBDIR = $(call PKGCFG,libdir) + LOCDIR = $(call PKGCFG,locdir) +@@ -296,7 +298,7 @@ + + mpg2c: mpg2c.c + @echo CCLD $@ +- $(Q)$(CC) $(CPPFLAGS) $(CFLAGS) $(LDFLAGS) mpg2c.c -o $@ ++ $(Q)$(CC_FOR_BUILD) $(CPPFLAGS) $(CFLAGS) $(LDFLAGS) mpg2c.c -o $@ + + # data + black_720x576.c: mpg2c black_720x576.mpg diff --minimal -Nru vdr-plugin-xineliboutput-2.2.0+git20211212/debian/patches/series vdr-plugin-xineliboutput-2.2.0+git20211212/debian/patches/series --- vdr-plugin-xineliboutput-2.2.0+git20211212/debian/patches/series +++ vdr-plugin-xineliboutput-2.2.0+git20211212/debian/patches/series @@ -1,2 +1,3 @@ disable-po-update.patch cppflags.patch +cross.patch diff --minimal -Nru vdr-plugin-xineliboutput-2.2.0+git20211212/debian/rules vdr-plugin-xineliboutput-2.2.0+git20211212/debian/rules --- vdr-plugin-xineliboutput-2.2.0+git20211212/debian/rules +++
Bug#1003090: RFS: ffcvt/1.7.5-1
Hi Tong,
On 1/15/22 2:55 AM, Tong Sun wrote:
Hi,
The situation should have been fixed with the new upload of easygen.
However, the CI build is still failing in salsa. This is something
that I don't understand as it builds OK on github.
Sorry I've run out of ideas why it is happening like this, and am now
thinking to remove the build dependency of easygen, to fix this and to
make things easier...
I still don't have a clue why
I intended to reply earlier, but I was occupied and simply forgot later, sorry
about that!
it builds OK on github but fails in
salsa CI build, and I still hope that somebody can help.
Okay, so there are two parts to it.
1) Why does github CI pass?
Ok, so there are two reasons about this as well
+ test-all.sh does not seem to run anywhere in your github actions/CI and that
error stems from this script (in the deb package)
+ `go test -v` in your CI essentially does nothing since there are no _test.go
files and it is visible
on the CI too
| go test -v ./...
| shell: /usr/bin/bash -e {0}
| env:
|GOROOT: /opt/hostedtoolcache/go/1.15.15/x64
| github.com/suntong/ffcvt
| ? github.com/suntong/ffcvt[no test files]
So you probably should update it accordingly there as well.
2) For salsa CI, I thought that it is because of the failing build.
You will find the build failure logs pasted at the end of this email.
The reason for test to be failing is that you have not updated
"test/ffcvt_test.txt" file in accordance with the
latest manpage/latest ffcvt options upstream.
However, even after I have pushed a patch to fix the build, salsa CI chokes.
@Alois, could you shed some light on the CI thingy?
From the logs, it is hard to figure out what went wrong.
The packages that are shown failing there do not have anything to do with ffcvt
package, are the failing logs stored somewhere?
I'll wait for one or two weeks more, and if still nobody can help,
It is usually a good idea to ask on #debian-mentors if there is more delay in a
reply.
Also, feel free to ping me if you think I can be of any help.
I'll remove the build dependency of easygen as planned, as I know for
sure it can fix the issue
I am not sure if that's the problem here. Why would it fix the issue?
Somebody help please.
Hope that helps. Let me know if you need sponsoring.
Regards,
Nilesh
| cd obj-x86_64-linux-gnu/src/github.com/suntong/ffcvt/test && ./test-all.sh
| ffcvt
| Version 1.7.5 built on 2022-01-02
| - Test (config.go) cli help output
| - Test transcoding single file
| - Test -sym control
| - Compare test results
| --- ffcvt_test.txt2022-01-15 07:35:05.137033394 +
| +++ /tmp/ffcvt_test.txt 2022-01-15 07:35:08.193097895 +
| @@ -6,3 +6,3 @@
|
| - -t target type: webm/x265-opus/x264-mp3/youtube (FFCVT_T)
| + -t target type: webm/x265-opus/x264-mp3/wx/youtube/copy (FFCVT_T)
| -vesvideo encoding method set (FFCVT_VES)
| @@ -32,3 +32,8 @@
| -vssvideo: same size (FFCVT_VSS)
| + -C,Cut Cut segment(s) out to keep. Specify in the form of start-[end],
| + strictly in the format of hh:mm:ss, and may repeat (FFCVT_C,CUT)
| + -S,Seg Split video into multiple segments (strictly in format:
hh:mm:ss) (FFCVT_S,SEG)
| + -Speed Speed up/down video playback speed (e.g. 1.28) (FFCVT_SPEED)
| -lang language selection for audio stream extraction (FFCVT_LANG)
| + -sel subtitle encoding language (language picked for reencoded
video) (FFCVT_SEL)
| -o more options that will pass to ffmpeg program (FFCVT_O)
| @@ -49,2 +54,14 @@
|
| + -C value
| + Cut segment(s) out to keep. Specify in the form of start-[end],
| + strictly in the format of hh:mm:ss, and may repeat
| + -Cut value
| + Cut segment(s) out to keep. Specify in the form of start-[end],
| + strictly in the format of hh:mm:ss, and may repeat
| + -S string
| + Split video into multiple segments (strictly in format: hh:mm:ss)
| + -Seg string
| + Split video into multiple segments (strictly in format: hh:mm:ss)
| + -Speed string
| + Speed up/down video playback speed (e.g. 1.28)
| -abr string
| @@ -90,2 +107,4 @@
| -p par2create, create par2 files (in work directory)
| + -sel value
| + subtitle encoding language (language picked for reencoded video)
| -sep string
| @@ -99,3 +118,3 @@
| -t string
| - target type: webm/x265-opus/x264-mp3/youtube (default "webm")
| + target type: webm/x265-opus/x264-mp3/wx/youtube/copy (default "webm")
| -vc
| 1
OpenPGP_signature
Description: OpenPGP digital signature
