Hello Seth, or anyone else affected,

Accepted systemd into zesty-proposed. The package will build now and be
available at https://launchpad.net/ubuntu/+source/systemd/232-21ubuntu3
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, and change the tag
from verification-needed to verification-done. If it does not fix the
bug for you, please add a comment stating that, and change the tag to
verification-failed.  In either case, details of your testing will help
us make a better decision.

Further information regarding the verification process can be found at
https://wiki.ubuntu.com/QATeam/PerformingSRUVerification .  Thank you in
advance!

** Changed in: systemd (Ubuntu Zesty)
       Status: In Progress => Fix Committed

** Tags added: verification-needed

-- 
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to systemd in Ubuntu.
https://bugs.launchpad.net/bugs/1672542

Title:
  systemd 232-18ubuntu1 ADT test failure with linux 4.10.0-13.15

Status in systemd package in Ubuntu:
  Fix Committed
Status in systemd source package in Zesty:
  Fix Committed

Bug description:
  [Impact]

   * Due to upgraded netcat in zesty, ADT testcase 12 started to hang upon 
calls to netcat.
   * The upgraded netcat changed default behaviour from -q0 (quit straight 
away) to -q-1 (wait infinity)
   * Proposed fix is an upstream cherry-pick to add a `-w1` option (quit after 
1 second) which resolves the test-suite hang and is compatible across Ubuntu 
and Fedora (uses nmap netcat).

  [Test Case]

   * ADT tests should pass on kvm architectures.

  [Regression Potential]

   * This is a testsuite fix for netcat-openbsd compat, does not affect
  systemd runtime binaries / libraries.

  [Other Info]
   
   * Original bug report.

  Testing failed on:
    amd64: 
https://objectstorage.prodstack4-5.canonical.com/v1/AUTH_77e2ada1e7a84929a74ba3b87153c0ac/autopkgtest-zesty/zesty/amd64/s/systemd/20170313_204550_ecb32@/log.gz
    i386: 
https://objectstorage.prodstack4-5.canonical.com/v1/AUTH_77e2ada1e7a84929a74ba3b87153c0ac/autopkgtest-zesty/zesty/i386/s/systemd/20170311_013142_b5cf9@/log.gz
    ppc64el: 
https://objectstorage.prodstack4-5.canonical.com/v1/AUTH_77e2ada1e7a84929a74ba3b87153c0ac/autopkgtest-zesty/zesty/ppc64el/s/systemd/20170311_020037_b5cf9@/log.gz

  Upstream tests time out. Last thing displayed in the logs before the
  timeout is the login prompt from a container running one of the tests.

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

-- 
Mailing list: https://launchpad.net/~touch-packages
Post to     : touch-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~touch-packages
More help   : https://help.launchpad.net/ListHelp

Reply via email to