Processed: ruby-omniauth-openid
Processing commands for cont...@bugs.debian.org: > forwarded 999722 https://github.com/omniauth/omniauth-openid/pull/44 Bug #999722 [src:ruby-omniauth-openid] ruby-omniauth-openid: FTBFS with ruby-omniauth 2.0.x: ERROR: Test "ruby2.7" failed: /usr/lib/ruby/vendor_ruby/rubygems/specification.rb:1404:in `rescue in block in activate_dependencies': Could not find 'omniauth' (~> 1.0) among 77 total gem(s) (Gem::MissingSpecError) Set Bug forwarded-to-address to 'https://github.com/omniauth/omniauth-openid/pull/44'. > thanks Stopping processing here. Please contact me if you need assistance. -- 999722: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=999722 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems
Processed: ruby-omniauth-google-oauth2
Processing commands for cont...@bugs.debian.org: > forwarded 999716 https://github.com/zquestz/omniauth-google-oauth2/pull/403 Bug #999716 [src:ruby-omniauth-google-oauth2] ruby-omniauth-google-oauth2: FTBFS with ruby-omniauth 2.0.x: ERROR: Test "ruby2.7" failed: NoMethodError: Set Bug forwarded-to-address to 'https://github.com/zquestz/omniauth-google-oauth2/pull/403'. > thanks Stopping processing here. Please contact me if you need assistance. -- 999716: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=999716 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems
Processed: tagging 938921
Processing commands for cont...@bugs.debian.org: > tags 938921 + ftbfs Bug #938921 [src:zorp] zorp: Python2 removal in sid/bullseye Bug #953377 [src:zorp] src:zorp: Depends/Build-Depends on cruft package python-dnspython Bug #966801 [src:zorp] zorp: Unversioned Python removal in sid/bullseye Added tag(s) ftbfs. Added tag(s) ftbfs. Added tag(s) ftbfs. > thanks Stopping processing here. Please contact me if you need assistance. -- 938921: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=938921 953377: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=953377 966801: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=966801 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems
Bug#1010556: marked as done (undefined symbol extract_begin)
Your message dated Sat, 14 May 2022 05:38:09 + with message-id and subject line Bug#1010556: fixed in qpdfview 0.4.18-7 has caused the Debian Bug report #1010556, regarding undefined symbol extract_begin 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.) -- 1010556: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1010556 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems --- Begin Message --- Package: qpdfview-pdf-mupdf-plugin Version: 0.4.18-6 Severity: important Hi, opening PDFs using qpdfview-pdf-mupdf-plugin doesn't work for me. When I try to do it, qpdfview displays these error messages in the GUI: Could not load plug-in for file type 'PDF'! Could not open 'some.pdf'. On the console I get the following more helpful messages: $ LC_ALL=C qpdfview some.pdf Could not load local plug-in: "/usr/bin/libqpdfview_pdf.so" "The shared library was not found." Could not load global plug-in: "/usr/lib/qpdfview/libqpdfview_pdf.so" "The shared library was not found." Could not load local plug-in: "/usr/bin/libqpdfview_fitz.so" "The shared library was not found." Could not load global plug-in: "/usr/lib/qpdfview/libqpdfview_fitz.so" "Cannot load library /usr/lib/qpdfview/libqpdfview_fitz.so: (/usr/lib/qpdfview/libqpdfview_fitz.so: undefined symbol: extract_begin)" Looks to me like libqpdfview_fitz.so is missing some dynamic linking dependency. Regards Sven -- System Information: Debian Release: bookworm/sid APT prefers testing-debug APT policy: (990, 'testing-debug'), (990, 'testing'), (102, 'unstable-debug'), (102, 'unstable'), (101, 'experimental-debug'), (101, 'experimental') Architecture: amd64 (x86_64) Kernel: Linux 5.17.0-1-amd64 (SMP w/12 CPU threads; PREEMPT) Kernel taint flags: TAINT_PROPRIETARY_MODULE, TAINT_OOT_MODULE, TAINT_UNSIGNED_MODULE Locale: LANG=de_DE.UTF-8, LC_CTYPE=de_DE.UTF-8 (charmap=UTF-8), LANGUAGE not set Shell: /bin/sh linked to /bin/dash Init: systemd (via /run/systemd/system) LSM: AppArmor: enabled Versions of packages qpdfview-pdf-mupdf-plugin depends on: ii libc62.33-7 ii libgcc-s112-20220428-1 ii libjbig2dec0 0.19-3 ii libjpeg62-turbo 1:2.1.2-1 ii libmujs1 1.1.3-4 ii libopenjp2-7 2.4.0-6 ii libqt5core5a 5.15.2+dfsg-16+b1 ii libqt5gui5 5.15.2+dfsg-16+b1 ii libqt5widgets5 5.15.2+dfsg-16+b1 ii libstdc++6 12-20220428-1 qpdfview-pdf-mupdf-plugin recommends no packages. qpdfview-pdf-mupdf-plugin suggests no packages. -- no debconf information OpenPGP_signature Description: OpenPGP digital signature --- End Message --- --- Begin Message --- Source: qpdfview Source-Version: 0.4.18-7 Done: Louis-Philippe Véronneau We believe that the bug you reported is fixed in the latest version of qpdfview, which is due to be installed in the Debian FTP archive. A summary of the changes between this version and the previous one is attached. Thank you for reporting the bug, which will now be closed. If you have further comments please address them to 1010...@bugs.debian.org, and the maintainer will reopen the bug report if appropriate. Debian distribution maintenance software pp. Louis-Philippe Véronneau (supplier of updated qpdfview package) (This message was generated automatically at their request; if you believe that there is a problem with it please contact the archive administrators by mailing ftpmas...@ftp-master.debian.org) -BEGIN PGP SIGNED MESSAGE- Hash: SHA512 Format: 1.8 Date: Fri, 13 May 2022 23:50:10 -0400 Source: qpdfview Architecture: source Version: 0.4.18-7 Distribution: unstable Urgency: medium Maintainer: Louis-Philippe Véronneau Changed-By: Louis-Philippe Véronneau Closes: 996430 1010556 Changes: qpdfview (0.4.18-7) unstable; urgency=medium . [ Louis-Philippe Véronneau ] * d/patches: add DEP-3 headers and rename patches for consistency. * d/patches: update 0001 to fix AppStream compliance. * d/control: fix errors in descriptions. (Closes: #996430) . [ Sven Bartscher ] * Link fitz plugin with libmupdf-third and libgumbo. (Closes: #1010556) Checksums-Sha1: 2a56316126e80e221e97cd82649a595ef7cecce7 2144 qpdfview_0.4.18-7.dsc b85330257af97dae6d960295526abe38f479d808 70536 qpdfview_0.4.18-7.debian.tar.xz 53d497e463a6fca9f306db44b1fc5c6672d65fba 15036 qpdfview_0.4.18-7_amd64.buildinfo Checksums-Sha256: 7a055c47aee5833595048172ce71171e36a266b3a6fc0df6f8b406498c2d29a7 2144 qpdfview_0.4.18-7.dsc 4662f24473cbd03e68a2cae4643f235ebf4e17b82915f660b34c545e9726fcb1 70536 qpdfview_0.4.18-7.debian.tar.xz
Processed: affects 996422
Processing commands for cont...@bugs.debian.org: > affects 996422 src:mender-client Bug #996422 [src:golang-github-mendersoftware-openssl] golang-github-mendersoftware-openssl: FTBFS with OpenSSL 3.0 Added indication that 996422 affects src:mender-client > thanks Stopping processing here. Please contact me if you need assistance. -- 996422: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=996422 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems
Processed: ruby-omniauth-saml
Processing commands for cont...@bugs.debian.org: > forwarded 999725 https://github.com/omniauth/omniauth-saml/commit/f7ec7ee Bug #999725 [src:ruby-omniauth-saml] ruby-omniauth-saml: FTBFS with ruby-omniauth 2.0.x: ERROR: Test "ruby2.7" failed: /usr/lib/ruby/vendor_ruby/rubygems/specification.rb:1404:in `rescue in block in activate_dependencies': Could not find 'omniauth' (~> 1.3, >= 1.3.2) among 77 total gem(s) (Gem::MissingSpecError) Set Bug forwarded-to-address to 'https://github.com/omniauth/omniauth-saml/commit/f7ec7ee'. > thanks Stopping processing here. Please contact me if you need assistance. -- 999725: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=999725 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems
Bug#1010556: undefined symbol extract_begin
On 2022-05-05 04 h 46, Sven Bartscher wrote: > > Since the fix was relatively simple, I opened a merge request on salsa[1]. > > Regards > Sven > > [1]: https://salsa.debian.org/pollo/qpdfview/-/merge_requests/1 Many thanks for the patch. -- ⢀⣴⠾⠻⢶⣦⠀ ⣾⠁⢠⠒⠀⣿⡁ Louis-Philippe Véronneau ⢿⡄⠘⠷⠚⠋ po...@debian.org / veronneau.org ⠈⠳⣄
Processed: reassign 1010946 to wnpp, tagging 999715
Processing commands for cont...@bugs.debian.org:
> reassign 1010946 wnpp
Bug #1010946 [w3c-keyname] ITP: node-w3c-keyname
Warning: Unknown package 'w3c-keyname'
Bug reassigned from package 'w3c-keyname' to 'wnpp'.
Ignoring request to alter found versions of bug #1010946 to the same values
previously set
Ignoring request to alter fixed versions of bug #1010946 to the same values
previously set
> tags 999715 + experimental
Bug #999715 {Done: Mohammed Bilal }
[src:ruby-omniauth-github] ruby-omniauth-github: FTBFS with ruby-omniauth
2.0.x: ERROR: Test "ruby2.7" failed:
/usr/lib/ruby/vendor_ruby/rubygems/specification.rb:1404:in `rescue in block in
activate_dependencies': Could not find 'omniauth' (~> 1.5) among 82 total
gem(s) (Gem::MissingSpecError)
Added tag(s) experimental.
> thanks
Stopping processing here.
Please contact me if you need assistance.
--
1010946: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1010946
999715: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=999715
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
Bug#1010941: python-argcomplete salvaging and possible team (re)join
Hi Marco, Marc and the Team,
I have just uploaded to --delayed 5 a workaround fix for #1010941
(FTBFS). The diff is attached
I have a clone at https://salsa.debian.org/yoh/python-argcomplete
with Marc's NMU imported, and my NMU changes on top. So could be a good
starting point to update packaging to a new release ;)
would also be nice to add tags (may be original from Marco?) for prior
upstream/debian releases.
Cheers,
On Wed, 27 Apr 2022, Marc Dequènes (duck) wrote:
> Quack,
> python-argcomplete has not been actively maintained and I did a NMU last
> year that got unacknowledged. I intend to salvage it. I think it would make
> sense to maintain it under the team's umbrella, which leads me to…
> I was part of the "Python Modules Team" between 2006 and 2009 but since then
> did not maintain Python packages except for some sponsoring (mainly
> postfix-mta-sts-resolver and dico related packages but not team-maintained
> although wikitrans was in the Python Modules Team as the Maintainer field
> attest). I'd be glad to rejoin if you would allow me. I don't know if I
> would have time to work on other team packages but occasionally I should be
> able to give a hand.
> I have read and agree to the policy on:
> https://salsa.debian.org/python-team/tools/python-modules/blob/master/policy.rst
> I am not familiar with gbp-pq but I looked at the doc and it seems quite
> interesting. The rest of the workflow is is almost identical to what I'm
> used to and should not be a problem.
> Regards.
> \_o<
--
Yaroslav O. Halchenko
Center for Open Neuroscience http://centerforopenneuroscience.org
Dartmouth College, 419 Moore Hall, Hinman Box 6207, Hanover, NH 03755
WWW: http://www.linkedin.com/in/yarik
diff -Nru python-argcomplete-1.12.3/debian/changelog python-argcomplete-1.12.3/debian/changelog
--- python-argcomplete-1.12.3/debian/changelog 2021-09-28 10:29:56.0 -0400
+++ python-argcomplete-1.12.3/debian/changelog 2022-05-13 13:07:30.0 -0400
@@ -1,3 +1,12 @@
+python-argcomplete (1.12.3-0.2) unstable; urgency=medium
+
+ * Non-maintainer upload.
+ * debian/rules
+- provide workaround for tests to not fail (Closes: #1010941).
+ Upstream issue: https://github.com/kislyuk/argcomplete/issues/337
+
+ -- Yaroslav Halchenko Fri, 13 May 2022 13:07:30 -0400
+
python-argcomplete (1.12.3-0.1) unstable; urgency=medium
* Non-maintainer upload.
diff -Nru python-argcomplete-1.12.3/debian/rules python-argcomplete-1.12.3/debian/rules
--- python-argcomplete-1.12.3/debian/rules 2021-09-28 10:29:56.0 -0400
+++ python-argcomplete-1.12.3/debian/rules 2022-05-13 13:07:30.0 -0400
@@ -26,6 +26,17 @@
cp debian/$$i.1 debian/python3-argcomplete/usr/share/man/man1/$${i}3.1; \
done
+# Workaround
+# https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1010941
+# https://github.com/kislyuk/argcomplete/issues/337#issuecomment-771835184
+override_dh_auto_test:
+ echo "set enable-bracketed-paste off" > .inputrc
+ INPUTRC=$(CURDIR)/.inputrc dh_auto_test
+
+override_dh_auto_clean:
+ rm -f .inputrc
+ dh_auto_clean
+
generate_manpages:
VERSION=$$(./setup.py -V) ; \
for file in \
signature.asc
Description: PGP signature
Bug#990872: puppetdb.jar crashes out of the box with clojure classpath error
Had a look at similar failures today and I fixed the way libcore-async-clojure exports its classpath [1]. This should _at least_ fix the need for adding tools.analyzer.jar and tools.analyzer.jvm.jar manually to the classpath. I'd be curious to know how that changed things for puppetdb! (maybe this bug is fixed?) [1]: https://tracker.debian.org/news/1324649/accepted-core-async-clojure-13610-5-source-into-unstable/ -- ⢀⣴⠾⠻⢶⣦⠀ ⣾⠁⢠⠒⠀⣿⡁ Louis-Philippe Véronneau ⢿⡄⠘⠷⠚⠋ po...@debian.org / veronneau.org ⠈⠳⣄
Bug#1010941: FTBFS due to tests 56 tests failing
Package: python3-argcomplete Version: 1.12.3-0.1 Severity: serious Tags: ftbfs Justification: fails to build from source Wanted to build a backport but failed to have it built even in current sid. A complete log is at http://www.onerussian.com/tmp/python-argcomplete_1.12.3-0.1_amd64.build and here is a typical (they are all of the same kind - not matching desired empty string) fail: == FAIL: test_wordbreak_chars (test.test.TestBashGlobal) -- Traceback (most recent call last): File "/build/python-argcomplete-1.12.3/test/test.py", line 1215, in setUp self.assertEqual(output, '') AssertionError: '\x1b[?2004l\r\x1b[?2004h' != '' - ^[[?2004l^M- ^[[?2004h -- System Information: Debian Release: bookworm/sid APT prefers testing APT policy: (900, 'testing'), (600, 'unstable'), (300, 'experimental'), (100, 'unstable-debug'), (100, 'stable-updates'), (100, 'stable-security'), (100, 'stable') Architecture: amd64 (x86_64) Foreign Architectures: i386 Kernel: Linux 5.16.0-6-amd64 (SMP w/12 CPU threads; PREEMPT) Kernel taint flags: TAINT_PROPRIETARY_MODULE, TAINT_OOT_MODULE, TAINT_UNSIGNED_MODULE Locale: LANG=en_US.UTF-8, LC_CTYPE=en_US.UTF-8 (charmap=UTF-8), LANGUAGE not set Shell: /bin/sh linked to /usr/bin/dash Init: systemd (via /run/systemd/system) LSM: AppArmor: enabled Versions of packages python3-argcomplete depends on: ii python3 3.9.8-1 python3-argcomplete recommends no packages. python3-argcomplete suggests no packages. -- debconf-show failed
Bug#1010232: Processed: severity of 1010232 is serious
Hi Ricardo, Ricardo Mones wrote: > > > # Typos in hard dependencies are clearly release-critical > > Indeed, thanks for adjusting severity. Unfortunately I didn't receive the > original bug report, Oh, I already wondered why there was no reaction from you on that bug report. That explains it well. > so thanks also for the heads up. You're welcome. BTW, https://tracker.debian.org/pkg/claws-mail also argues: ∙ Not built on buildd: arch amd64 binaries uploaded by mones ∙ Not built on buildd: arch all binaries uploaded by mones, a new source-only upload is needed to allow migration Looks like an oversight when doing the upload. (Occasionally happens to me, too. Old habits… ;-) Regards, Axel -- ,''`. | Axel Beckert , https://people.debian.org/~abe/ : :' : | Debian Developer, ftp.ch.debian.org Admin `. `' | 4096R: 2517 B724 C5F6 CA99 5329 6E61 2FF9 CD59 6126 16B5 `-| 1024D: F067 EA27 26B9 C3FC 1486 202E C09E 1D89 9593 0EDE
Processed: Re: Processed: severity of 1010232 is serious
Processing control commands: > tags -1 fixed pending Bug #1010232 [claws-mail-extra-plugins] claws-mail-extra-plugins: version 4.1.0-1 not installable due to typo in debian/control Added tag(s) pending and fixed. -- 1010232: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1010232 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems
Bug#1010232: Processed: severity of 1010232 is serious
control: tags -1 fixed pending On Thu, 12 May 2022 23:21:03 + Axel Beckert wrote: > > # Typos in hard dependencies are clearly release-critical Indeed, thanks for adjusting severity. Unfortunately I didn't receive the original bug report, so thanks also for the heads up. Adjusting tags accordingly¹. best regards, ¹ https://salsa.debian.org/claws-mail-team/claws-mail/-/commit/02f82af95fda4e3d5c241567edbc2a5eddcc0e26 -- Ricardo Mones http://people.debian.org/~mones «"Experience has proved that some people indeed know everything." -- Russell Baker» pgpVPP9Yjw2gc.pgp Description: Firma digital OpenPGP
Bug#1008443: golang-github-smartystreets-assertions: FTBFS: dh_auto_test: error: cd obj-x86_64-linux-gnu && go test -vet=off -v -p 8 github.com/smartystreets/assertions github.com/smartystreets/assert
Source: golang-github-smartystreets-assertions Version: 1.10.1+ds-1 Followup-For: Bug #1008443 The problem passing tests is still there with smartystreets-assertions 0.13.0 (building with golang 1.18) -- System Information: Debian Release: bookworm/sid APT prefers unstable APT policy: (500, 'unstable'), (1, 'experimental') Architecture: amd64 (x86_64) Foreign Architectures: i386 Kernel: Linux 5.17.0-1-amd64 (SMP w/8 CPU threads; PREEMPT) Kernel taint flags: TAINT_OOT_MODULE Locale: LANG=en_AU.UTF-8, LC_CTYPE=en_AU.UTF-8 (charmap=UTF-8), LANGUAGE=en_AU:en Shell: /bin/sh linked to /bin/dash Init: systemd (via /run/systemd/system) LSM: AppArmor: enabled
Bug#1009939: sip6: AttributeError: 'YaccProduction' object has no attribute 'parser_manager'
On 4/21/22 05:39, Bas Couwenberg wrote: Since the upgrade to 6.6.1+dfsg-1 qgis FTBFS: According to [0] the current hg tip enables successfull building of QGIS again. That's quite a number of additional changes which I doubt is a good idea to add as patches. That is unless it's going to take a long time until 6.6.2 release. Do you have any insight when to expect the next sip6 upstream release? [0] https://www.riverbankcomputing.com/pipermail/pyqt/2022-May/044641.html Kind Regards, Bas -- GPG Key ID: 4096R/6750F10AE88D4AF1 Fingerprint: 8182 DE41 7056 408D 6146 50D1 6750 F10A E88D 4AF1
Bug#1006510: marked as done (myproxy: FTBFS with OpenSSL 3.0)
Your message dated Fri, 13 May 2022 11:36:55 + with message-id and subject line Bug#1006510: fixed in myproxy 6.2.9-3 has caused the Debian Bug report #1006510, regarding myproxy: FTBFS with OpenSSL 3.0 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.) -- 1006510: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1006510 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems --- Begin Message --- Source: myproxy Version: 6.2.9-2 Severity: important Tags: bookworm sid User: pkg-openssl-de...@lists.alioth.debian.org Usertags: ftbfs-3.0 Your package is failing to build using OpenSSL 3.0 with the following error: | make check-TESTS | make[3]: Entering directory '/<>' | make[4]: Entering directory '/<>' | FAIL: myproxy-test-wrapper | = |myproxy 6.2.9: ./test-suite.log | = | | # TOTAL: 1 | # PASS: 0 | # SKIP: 0 | # XFAIL: 0 | # FAIL: 1 | # XPASS: 0 | # ERROR: 0 | | .. contents:: :depth: 2 | | FAIL: myproxy-test-wrapper | == | | anonymous retrievers allowed | MyProxy v6.2 Aug 2021 PAM SASL KRB5 LDAP VOMS OCSP | Attempting to connect to 127.0.0.1:35389 | Successfully connected to localhost:35389 | | User Cert File: /tmp/x509up_u1005 | User Key File: /tmp/x509up_u1005 | | Trusted CA Cert Dir: /tmp/rajSSzhqAe/privcerts.4182428/grid-security | | Output File: /tmp/myproxy-proxy.1005.4186176 | Your identity: /CN=MyProxy Test User | Creating proxy .+ | + | Done | Proxy Verify OK | Your proxy is valid until: Tue Feb 15 03:09:22 2022 | Expecting non-standard server DN "/CN=MyProxy Test User" | using trusted certificates directory /tmp/rajSSzhqAe/privcerts.4182428/grid-security | Using Proxy file (/tmp/myproxy-proxy.1005.4186176) | server name: /CN=MyProxy Test User | checking that server name is acceptable... | server name matches "/CN=MyProxy Test User" | authenticated server name is acceptable | ERROR from myproxy-server: | Failed to accept credentials. | Error delegating credentials: server-side error: check server logs | MyProxy Test 1 (store credential with default name): FAILED | Skipping remaining tests. | MyProxy Tests Complete: 0 tests passed, 1 tests failed | FAIL myproxy-test-wrapper (exit status: 1) | | | Testsuite summary for myproxy 6.2.9 | | # TOTAL: 1 | # PASS: 0 | # SKIP: 0 | # XFAIL: 0 | # FAIL: 1 | # XPASS: 0 | # ERROR: 0 | | See ./test-suite.log | | make[4]: *** [Makefile:1449: test-suite.log] Error 1 For more information see: https://www.openssl.org/docs/man3.0/man7/migration_guide.html Sebastian --- End Message --- --- Begin Message --- Source: myproxy Source-Version: 6.2.9-3 Done: Mattias Ellert We believe that the bug you reported is fixed in the latest version of myproxy, which is due to be installed in the Debian FTP archive. A summary of the changes between this version and the previous one is attached. Thank you for reporting the bug, which will now be closed. If you have further comments please address them to 1006...@bugs.debian.org, and the maintainer will reopen the bug report if appropriate. Debian distribution maintenance software pp. Mattias Ellert (supplier of updated myproxy package) (This message was generated automatically at their request; if you believe that there is a problem with it please contact the archive administrators by mailing ftpmas...@ftp-master.debian.org) -BEGIN PGP SIGNED MESSAGE- Hash: SHA512 Format: 1.8 Date: Fri, 13 May 2022 11:13:09 +0200 Source: myproxy Architecture: source Version: 6.2.9-3 Distribution: unstable Urgency: medium Maintainer: Mattias Ellert Changed-By: Mattias Ellert Closes: 1006510 Changes: myproxy (6.2.9-3) unstable; urgency=medium . * Use sha256 when signing request * Fix some compiler warnings * Fix IPv6 glitch in the trust root retrieval in the client * Fix wrong name in myproxy-store -V output * Use write+rename when changing passphrase * Improve detection of an encrypted private key * Fix broken sprintf format in myproxy test * Support both SHA1 (backward compatibility) and SHA256 (compatible with openssl 3.0.2) (Closes: #1006510) * Fix a double free Checksums-Sha1:
Bug#1009420: marked as done (libotr: FTBFS: client.c:624:30: error: ‘PF_UNIX’ undeclared (first use in this function))
Your message dated Fri, 13 May 2022 10:04:04 +
with message-id
and subject line Bug#1009420: fixed in libotr 4.1.1-5
has caused the Debian Bug report #1009420,
regarding libotr: FTBFS: client.c:624:30: error: ‘PF_UNIX’ undeclared (first
use in this function)
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.)
--
1009420: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1009420
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Source: libotr
Version: 4.1.1-4
Severity: serious
Justification: FTBFS
Tags: bookworm sid ftbfs
User: lu...@debian.org
Usertags: ftbfs-20220412 ftbfs-bookworm
Hi,
During a rebuild of all packages in sid, your package failed to build
on amd64.
Relevant part (hopefully):
> gcc -DHAVE_CONFIG_H -I. -I../../.. -Wdate-time -D_FORTIFY_SOURCE=2
> -I../../../include -I../../../src -I../../../tests/utils/ -I. -g -O2
> -ffile-prefix-map=/<>=. -fstack-protector-strong -Wformat
> -Werror=format-security -D_FORTIFY_SOURCE=2 -fstack-protector-all
> -Wstack-protector -fwrapv -fno-strict-overflow -Wall -Wextra
> -Wno-unused-parameter -Wformat-security --param ssp-buffer-size=1 -fPIE -c -o
> client.o client.c
> client.c: In function ‘ops_inject_msg’:
> client.c:151:15: warning: implicit declaration of function ‘send’
> [-Wimplicit-function-declaration]
> 151 | ret = send(oinfo->sock, , sizeof(msg), 0);
> | ^~~~
> client.c: In function ‘recv_otr_msg’:
> client.c:553:15: warning: implicit declaration of function ‘recv’
> [-Wimplicit-function-declaration]
> 553 | ret = recv(sock, , sizeof(omsg), 0);
> | ^~~~
> client.c: In function ‘alice_thread’:
> client.c:624:23: warning: implicit declaration of function ‘socket’
> [-Wimplicit-function-declaration]
> 624 | sock_to_bob = socket(PF_UNIX, SOCK_STREAM, 0);
> | ^~
> client.c:624:30: error: ‘PF_UNIX’ undeclared (first use in this function)
> 624 | sock_to_bob = socket(PF_UNIX, SOCK_STREAM, 0);
> | ^~~
> client.c:624:30: note: each undeclared identifier is reported only once for
> each function it appears in
> client.c:624:39: error: ‘SOCK_STREAM’ undeclared (first use in this function)
> 624 | sock_to_bob = socket(PF_UNIX, SOCK_STREAM, 0);
> | ^~~
> client.c:638:15: warning: implicit declaration of function ‘connect’
> [-Wimplicit-function-declaration]
> 638 | ret = connect(sock_to_bob, (struct sockaddr *) _sun,
> | ^~~
> client.c:725:57: warning: implicit declaration of function ‘accept’; did you
> mean ‘acct’? [-Wimplicit-function-declaration]
> 725 | sock_from_bob = accept(fd,
> (struct sockaddr *) ,
> | ^~
> | acct
> client.c: In function ‘bob_thread’:
> client.c:776:32: error: ‘PF_UNIX’ undeclared (first use in this function)
> 776 | sock_to_alice = socket(PF_UNIX, SOCK_STREAM, 0);
> |^~~
> client.c:776:41: error: ‘SOCK_STREAM’ undeclared (first use in this function)
> 776 | sock_to_alice = socket(PF_UNIX, SOCK_STREAM, 0);
> | ^~~
> client.c: In function ‘create_unix_socket’:
> client.c:979:28: error: ‘PF_UNIX’ undeclared (first use in this function)
> 979 | if ((sock = socket(PF_UNIX, SOCK_STREAM, 0)) < 0) {
> |^~~
> client.c:979:37: error: ‘SOCK_STREAM’ undeclared (first use in this function)
> 979 | if ((sock = socket(PF_UNIX, SOCK_STREAM, 0)) < 0) {
> | ^~~
> client.c:986:27: error: ‘AF_UNIX’ undeclared (first use in this function)
> 986 | sun->sun_family = AF_UNIX;
> | ^~~
> client.c:990:15: warning: implicit declaration of function ‘bind’
> [-Wimplicit-function-declaration]
> 990 | ret = bind(sock, (struct sockaddr *) sun, sizeof(struct
> sockaddr_un));
> | ^~~~
> client.c:996:15: warning: implicit declaration of function ‘listen’
> [-Wimplicit-function-declaration]
> 996 | ret = listen(sock, 10);
> | ^~
> make[5]: *** [Makefile:375: client.o] Error 1
The full build log is available from:
http://qa-logs.debian.net/2022/04/12/libotr_4.1.1-4_unstable.log
All bugs
Processed: severity of 1010921 is serious
Processing commands for cont...@bugs.debian.org: > # SONAME bump without package rename > severity 1010921 serious Bug #1010921 [src:waylandpp] kodi FTBFS due to outdated shlibs Severity set to 'serious' from 'important' > thanks Stopping processing here. Please contact me if you need assistance. -- 1010921: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1010921 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems
