Hi, On Fri, Jun 9, 2023 at 3:21 AM Andrej Shadura <and...@shadura.me> wrote: > > Hi, > > On Thu, 8 Jun 2023, at 18:23, Bo YU wrote: > > jimtcl (0.82-1) experimental; urgency=medium > > . > > * New upstream release. > > * set --full default build options from upstream.(Closes: #1016657) > > * update symbols file > > * add libssl-dev,pkg-config on B-D > > > > ``` > > The repo is here: https://salsa.debian.org/debian/jimtcl > > > > I am not sure It is okay to drop the dfsg because I do not see any > > file licenses violation of Debian's dfsg. > > please let me know if there is any issues. > > Thanks again~ > > Thanks! > > You need to disable network tests, as networking is not allowed at buildds: > > ssl-2.2 ERR https to google.com, read with cert verify > /<<PKGBUILDDIR>>/tests/ssl.test:75:Error test failure > Expected: rc={ok return} result={HTTP/1.0 200 OK*</html>} > Got : rc=error result={failed to verify the connection authenticity} > > ssl.test: Total 5 Passed 4 Skipped 0 Failed 1 > ------------------------------------------------------------ > FAILED: 1 > /<<PKGBUILDDIR>>/tests/ssl.test:75 ssl-2.2 > Got it. I disabled/ignored the test with the $(testreport) it at this time. But I am wonder why it will not be reproduced on my local build with sbuild. Need I to change some modifies in ~/.sbuildrc?
Another serious issue is it fails to build on i386: https://salsa.debian.org/debian/jimtcl/-/pipelines/535907 I hope it can be uploaded to experimental this time and to see the issue if existed in others arch, this is to help upstream to debug the issue also I think. Could you help me to upload it in this situation? [0]: https://mentors.debian.net/package/jimtcl/ [1]: https://salsa.debian.org/debian/jimtcl ``` Changelog jimtcl (0.82-1) experimental; urgency=medium . * New upstream release. * set --full default build options from upstream.(Closes: #1016657) * update symbols file * add libssl-dev,pkg-config on B-D * disable network access test from ssl.test ``` Thanks! > > -- > Cheers, > Andrej
