[Bug 2059156] Re: proposed-migration for m2crypto 0.40.1-2build1

[Simon Quigley]

Hi Spyros,

The package is orphaned in Debian, so I have gone ahead with an upload
there. I added the Debian bug to the DEP-3 headers, and ordered the
patch so it is the last one in the list instead of the first one.

In order to get this into Noble, an SRU bug template is required. For
more details, please see this link:
https://wiki.ubuntu.com/StableReleaseUpdates#SRU_Bug_Template (of
course, if an SRU team member disagrees we can move forward without it;
I am unsure of the implications in Noble.)

Unsubscribing sponsors for now, please feel free to resubscribe sponsors
once the paperwork is done for Noble.

Thanks!

** Changed in: m2crypto (Ubuntu Oracular)
       Status: In Progress => Fix Committed

-- 
You received this bug notification because you are a member of Ubuntu
Sponsors, which is subscribed to the bug report.
https://bugs.launchpad.net/bugs/2059156

Title:
  proposed-migration for m2crypto 0.40.1-2build1

Status in m2crypto package in Ubuntu:
  Fix Committed
Status in m2crypto source package in Noble:
  In Progress
Status in m2crypto source package in Oracular:
  Fix Committed

Bug description:
  m2crypto 0.40.1-2build1 fails tests on armhf:

  423s =================================== FAILURES ==============================
  =====
  423s ______________ MiscSSLClientTestCase.test_server_simple_timeouts __________
  _____
  423s 
  423s self = <tests.test_ssl.MiscSSLClientTestCase testMethod=test_server_simple_
  timeouts>
  423s 
  423s     def test_server_simple_timeouts(self):
  423s         pid = self.start_server(self.args)
  423s         # Arbitrary value:
  423s         test_timeout_sec = 909
  423s         # Linux rounds microseconds in the timeouts up to the HZ kernel par
  ameter.
  423s         # Windows rounds down to milliseconds.
  423s         # To avoid checking for rounded values, pick interval long enough
  423s         # so that it is a whole number of ms and HZ for any reasonable HZ v
  alue.
  423s         test_timeout_microsec = 500000
  423s     
  423s         try:
  423s             with self.assertRaises(ValueError):
  423s                 SSL.Context('tlsv5')
  423s             ctx = SSL.Context()
  423s             s = SSL.Connection(ctx)
  423s     
  423s             r = s.get_socket_read_timeout()
  423s             w = s.get_socket_write_timeout()
  423s             self.assertEqual(r.sec, 0, r.sec)
  423s             self.assertEqual(r.microsec, 0, r.microsec)
  423s             self.assertEqual(w.sec, 0, w.sec)
  423s             self.assertEqual(w.microsec, 0, w.microsec)
  423s     
  423s >           s.set_socket_read_timeout(SSL.timeout())

  "timeout" means time_t regression.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/m2crypto/+bug/2059156/+subscriptions