[Bug 1971960] Re: [FTBFS] python-xmlsec fails to build on s390x
This bug was fixed in the package python-xmlsec - 1.3.12-1ubuntu0.22.04.1 --- python-xmlsec (1.3.12-1ubuntu0.22.04.1) jammy; urgency=medium [ Steve Langasek ] * debian/patches/big-endian.patch: use the right format string for the target variable (LP: #1971960). -- Corey Bryant Fri, 06 May 2022 09:19:11 -0400 ** Changed in: python-xmlsec (Ubuntu Jammy) Status: Fix Committed => Fix Released -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1971960 Title: [FTBFS] python-xmlsec fails to build on s390x To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/python-xmlsec/+bug/1971960/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1971960] Re: [FTBFS] python-xmlsec fails to build on s390x
I can confirm that this now builds on all architectures (https://launchpad.net/ubuntu/+source/python- xmlsec/1.3.12-1ubuntu0.22.04.1) as well as being newly installable on s390x: $ apt-cache policy python3-xmlsec python3-xmlsec: Installed: (none) Candidate: 1.3.12-1ubuntu0.22.04.1 Version table: 1.3.12-1ubuntu0.22.04.1 500 500 http://ports.ubuntu.com/ubuntu-ports jammy-proposed/universe s390x Packages ** Tags removed: verification-needed verification-needed-jammy ** Tags added: verification-done verification-done-jammy -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1971960 Title: [FTBFS] python-xmlsec fails to build on s390x To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/python-xmlsec/+bug/1971960/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1971960] Re: [FTBFS] python-xmlsec fails to build on s390x
Hello Chris, or anyone else affected,
Accepted python-xmlsec into jammy-proposed. The package will build now
and be available at https://launchpad.net/ubuntu/+source/python-
xmlsec/1.3.12-1ubuntu0.22.04.1 in a few hours, and then in the -proposed
repository.
Please help us by testing this new package. See
https://wiki.ubuntu.com/Testing/EnableProposed for documentation on how
to enable and use -proposed. Your feedback will aid us getting this
update out to other Ubuntu users.
If this package fixes the bug for you, please add a comment to this bug,
mentioning the version of the package you tested, what testing has been
performed on the package and change the tag from verification-needed-
jammy to verification-done-jammy. If it does not fix the bug for you,
please add a comment stating that, and change the tag to verification-
failed-jammy. In either case, without details of your testing we will
not be able to proceed.
Further information regarding the verification process can be found at
https://wiki.ubuntu.com/QATeam/PerformingSRUVerification . Thank you in
advance for helping!
N.B. The updated package will be released to -updates after the bug(s)
fixed by this package have been verified and the package has been in
-proposed for a minimum of 7 days.
** Description changed:
[Impact]
- python3-xmlsec isn't available to installce on s390x on Jammy.
+ python3-xmlsec isn't available to install on s390x on Jammy.
As can be seen in this build log
(https://launchpadlibrarian.net/599963344/buildlog_ubuntu-
focal-s390x.python-xmlsec_1.3.12-1build1~cloud0_BUILDING.txt.gz), the
s390x build fails testing with a lot of errors matching:
___ ERROR at teardown of
TestSignContext.test_set_enabled_key_data_bad_args
self =
- def test_set_enabled_key_data_bad_args(self):
- ctx = xmlsec.SignatureContext()
+ def test_set_enabled_key_data_bad_args(self):
+ ctx = xmlsec.SignatureContext()
> ctx.key = xmlsec.Key.from_file(self.path('rsakey.pem'),
format=consts.KeyDataFormatPem)
E xmlsec.Error: (1, 'cannot read key')
tests/test_ds.py:326: Error
- Captured stderr call
-
func=xmlSecOpenSSLAppKeyLoadBIO:file=app.c:line=330:obj=unknown:subj=unknown:error=17:invalid
format:format=131072
func=xmlSecOpenSSLAppKeyLoad:file=app.c:line=175:obj=unknown:subj=xmlSecOpenSSLAppKeyLoadBIO:error=1:xmlsec
library function
failed:filename=/<>/.pybuild/cpython3_3.8/build/tests/data/rsakey.pem
func=xmlSecOpenSSLAppKeyLoadBIO:file=app.c:line=330:obj=unknown:subj=unknown:error=17:invalid
format:format=131072
func=xmlSecOpenSSLAppKeyLoad:file=app.c:line=175:obj=unknown:subj=xmlSecOpenSSLAppKeyLoadBIO:error=1:xmlsec
library function
failed:filename=/<>/.pybuild/cpython3_3.8/build/tests/data/rsakey.pem
func=xmlSecOpenSSLAppKeyLoadBIO:file=app.c:line=330:obj=unknown:subj=unknown:error=17:invalid
format:format=131072
func=xmlSecOpenSSLAppKeyLoad:file=app.c:line=175:obj=unknown:subj=xmlSecOpenSSLAppKeyLoadBIO:error=1:xmlsec
library function
failed:filename=/<>/.pybuild/cpython3_3.8/build/tests/data/rsakey.pem
func=xmlSecOpenSSLAppKeyLoadBIO:file=app.c:line=330:obj=unknown:subj=unknown:error=17:invalid
format:format=131072
func=xmlSecOpenSSLAppKeyLoad:file=app.c:line=175:obj=unknown:subj=xmlSecOpenSSLAppKeyLoadBIO:error=1:xmlsec
library function
failed:filename=/<>/.pybuild/cpython3_3.8/build/tests/data/rsakey.pem
func=xmlSecOpenSSLAppKeyLoadBIO:file=app.c:line=330:obj=unknown:subj=unknown:error=17:invalid
format:format=131072
func=xmlSecOpenSSLAppKeyLoad:file=app.c:line=175:obj=unknown:subj=xmlSecOpenSSLAppKeyLoadBIO:error=1:xmlsec
library function
failed:filename=/<>/.pybuild/cpython3_3.8/build/tests/data/rsakey.pem
func=xmlSecOpenSSLAppKeyLoadBIO:file=app.c:line=330:obj=unknown:subj=unknown:error=17:invalid
format:format=131072
func=xmlSecOpenSSLAppKeyLoad:file=app.c:line=175:obj=unknown:subj=xmlSecOpenSSLAppKeyLoadBIO:error=1:xmlsec
library function
failed:filename=/<>/.pybuild/cpython3_3.8/build/tests/data/rsakey.pem
func=xmlSecOpenSSLAppKeyLoadBIO:file=app.c:line=330:obj=unknown:subj=unknown:error=17:invalid
format:format=131072
func=xmlSecOpenSSLAppKeyLoad:file=app.c:line=175:obj=unknown:subj=xmlSecOpenSSLAppKeyLoadBIO:error=1:xmlsec
library function
failed:filename=/<>/.pybuild/cpython3_3.8/build/tests/data/rsakey.pem
func=xmlSecOpenSSLAppKeyLoadBIO:file=app.c:line=330:obj=unknown:subj=unknown:error=17:invalid
format:format=131072
func=xmlSecOpenSSLAppKeyLoad:file=app.c:line=175:obj=unknown:subj=xmlSecOpenSSLAppKeyLoadBIO:error=1:xmlsec
library function
failed:filename=/<>/.pybuild/cpython3_3.8/build/tests/data/rsakey.pem
func=xmlSecOpenSSLAppKeyLoadBIO:file=app.c:line=330:obj=unknown:subj=unknown:error=17:invalid
format:format=131072
[Bug 1971960] Re: [FTBFS] python-xmlsec fails to build on s390x
** Description changed:
+ [Impact]
+
+ python3-xmlsec isn't available to installce on s390x on Jammy.
+
As can be seen in this build log
(https://launchpadlibrarian.net/599963344/buildlog_ubuntu-
focal-s390x.python-xmlsec_1.3.12-1build1~cloud0_BUILDING.txt.gz), the
s390x build fails testing with a lot of errors matching:
___ ERROR at teardown of
TestSignContext.test_set_enabled_key_data_bad_args
self =
def test_set_enabled_key_data_bad_args(self):
ctx = xmlsec.SignatureContext()
> ctx.key = xmlsec.Key.from_file(self.path('rsakey.pem'),
format=consts.KeyDataFormatPem)
E xmlsec.Error: (1, 'cannot read key')
tests/test_ds.py:326: Error
- Captured stderr call
-
func=xmlSecOpenSSLAppKeyLoadBIO:file=app.c:line=330:obj=unknown:subj=unknown:error=17:invalid
format:format=131072
func=xmlSecOpenSSLAppKeyLoad:file=app.c:line=175:obj=unknown:subj=xmlSecOpenSSLAppKeyLoadBIO:error=1:xmlsec
library function
failed:filename=/<>/.pybuild/cpython3_3.8/build/tests/data/rsakey.pem
func=xmlSecOpenSSLAppKeyLoadBIO:file=app.c:line=330:obj=unknown:subj=unknown:error=17:invalid
format:format=131072
func=xmlSecOpenSSLAppKeyLoad:file=app.c:line=175:obj=unknown:subj=xmlSecOpenSSLAppKeyLoadBIO:error=1:xmlsec
library function
failed:filename=/<>/.pybuild/cpython3_3.8/build/tests/data/rsakey.pem
func=xmlSecOpenSSLAppKeyLoadBIO:file=app.c:line=330:obj=unknown:subj=unknown:error=17:invalid
format:format=131072
func=xmlSecOpenSSLAppKeyLoad:file=app.c:line=175:obj=unknown:subj=xmlSecOpenSSLAppKeyLoadBIO:error=1:xmlsec
library function
failed:filename=/<>/.pybuild/cpython3_3.8/build/tests/data/rsakey.pem
func=xmlSecOpenSSLAppKeyLoadBIO:file=app.c:line=330:obj=unknown:subj=unknown:error=17:invalid
format:format=131072
func=xmlSecOpenSSLAppKeyLoad:file=app.c:line=175:obj=unknown:subj=xmlSecOpenSSLAppKeyLoadBIO:error=1:xmlsec
library function
failed:filename=/<>/.pybuild/cpython3_3.8/build/tests/data/rsakey.pem
func=xmlSecOpenSSLAppKeyLoadBIO:file=app.c:line=330:obj=unknown:subj=unknown:error=17:invalid
format:format=131072
func=xmlSecOpenSSLAppKeyLoad:file=app.c:line=175:obj=unknown:subj=xmlSecOpenSSLAppKeyLoadBIO:error=1:xmlsec
library function
failed:filename=/<>/.pybuild/cpython3_3.8/build/tests/data/rsakey.pem
func=xmlSecOpenSSLAppKeyLoadBIO:file=app.c:line=330:obj=unknown:subj=unknown:error=17:invalid
format:format=131072
func=xmlSecOpenSSLAppKeyLoad:file=app.c:line=175:obj=unknown:subj=xmlSecOpenSSLAppKeyLoadBIO:error=1:xmlsec
library function
failed:filename=/<>/.pybuild/cpython3_3.8/build/tests/data/rsakey.pem
func=xmlSecOpenSSLAppKeyLoadBIO:file=app.c:line=330:obj=unknown:subj=unknown:error=17:invalid
format:format=131072
func=xmlSecOpenSSLAppKeyLoad:file=app.c:line=175:obj=unknown:subj=xmlSecOpenSSLAppKeyLoadBIO:error=1:xmlsec
library function
failed:filename=/<>/.pybuild/cpython3_3.8/build/tests/data/rsakey.pem
func=xmlSecOpenSSLAppKeyLoadBIO:file=app.c:line=330:obj=unknown:subj=unknown:error=17:invalid
format:format=131072
func=xmlSecOpenSSLAppKeyLoad:file=app.c:line=175:obj=unknown:subj=xmlSecOpenSSLAppKeyLoadBIO:error=1:xmlsec
library function
failed:filename=/<>/.pybuild/cpython3_3.8/build/tests/data/rsakey.pem
func=xmlSecOpenSSLAppKeyLoadBIO:file=app.c:line=330:obj=unknown:subj=unknown:error=17:invalid
format:format=131072
func=xmlSecOpenSSLAppKeyLoad:file=app.c:line=175:obj=unknown:subj=xmlSecOpenSSLAppKeyLoadBIO:error=1:xmlsec
library function
failed:filename=/<>/.pybuild/cpython3_3.8/build/tests/data/rsakey.pem
func=xmlSecOpenSSLAppKeyLoadBIO:file=app.c:line=330:obj=unknown:subj=unknown:error=17:invalid
format:format=131072
func=xmlSecOpenSSLAppKeyLoad:file=app.c:line=175:obj=unknown:subj=xmlSecOpenSSLAppKeyLoadBIO:error=1:xmlsec
library function
failed:filename=/<>/.pybuild/cpython3_3.8/build/tests/data/rsakey.pem
func=xmlSecOpenSSLAppKeyLoadBIO:file=app.c:line=330:obj=unknown:subj=unknown:error=17:invalid
format:format=131072
func=xmlSecOpenSSLAppKeyLoad:file=app.c:line=175:obj=unknown:subj=xmlSecOpenSSLAppKeyLoadBIO:error=1:xmlsec
library function
failed:filename=/<>/.pybuild/cpython3_3.8/build/tests/data/rsakey.pem
___ ERROR at teardown of TestSignContext.test_set_enabled_key_data_bad_list
- Digging into it, I see that module seems to be loosing track of the
- passed in key file's argument, leading to the key being none, and unable
- to be read.
+ [Test Plan]
+
+ The unit tests for the build should pass on all architectures, including
+ big-endian (S390X).
+
+ [Where problems could occur]
+
+ Problems could occur in key-loading, given that the issue is identified
+ as specifically relating to code that's loading private keys from the
+ filesystem. This specific test is what caused the build failures on
+ s390x so should be fairly low risk.
+
+ [Other Info]
+
+ The specific issue
[Bug 1971960] Re: [FTBFS] python-xmlsec fails to build on s390x
This bug is going to need SRU details outlined and then the ubuntu-sru team will need to be subscribed. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1971960 Title: [FTBFS] python-xmlsec fails to build on s390x To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/python-xmlsec/+bug/1971960/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1971960] Re: [FTBFS] python-xmlsec fails to build on s390x
A fixed version of python-xmlsec has been uploaded to the jammy unapproved queue: https://launchpad.net/ubuntu/jammy/+queue?queue_state=1_text= -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1971960 Title: [FTBFS] python-xmlsec fails to build on s390x To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/python-xmlsec/+bug/1971960/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1971960] Re: [FTBFS] python-xmlsec fails to build on s390x
A fix for this has been uploaded to Kinetic in https://launchpad.net/ubuntu/+source/python-xmlsec/1.3.12-1ubuntu1 ** Also affects: python-xmlsec (Ubuntu Jammy) Importance: Undecided Status: New ** Changed in: python-xmlsec (Ubuntu) Status: New => Fix Released -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1971960 Title: [FTBFS] python-xmlsec fails to build on s390x To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/python-xmlsec/+bug/1971960/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
