This bug was fixed in the package curtin - 0.1.0~bzr470-0ubuntu1~16.04.1

---------------
curtin (0.1.0~bzr470-0ubuntu1~16.04.1) xenial-proposed; urgency=medium

  * debian/rules: record debian package version in installed package.
    (LP: #1666986)
  * New upstream snapshot.
    - vmtest: allow time-based skipping of tests, apply to ZestyMdadmBcache
      to temporarily avoid bug 1667078.
    - Add iSCSI disk support. (LP: #1645515)
    - vmtest: handle change in btrfs-progs when finding fs UUID. (LP: #1665701)
    - pycodestyle: fix bare except in vmtests
    - unittests: add subp coverage for retries, and rcs
    - reporting: Add better descriptions and granularity of events
    - tox: do not bother with pep8 from trusty in trusty-check
    - tests: add two scripts used for running vmtest with installed package.
    - Make add-apt-repository command retry
    - Add tests for network bridging configuration

 -- Scott Moser <smo...@ubuntu.com>  Wed, 01 Mar 2017 11:13:58 -0500

** Changed in: curtin (Ubuntu Xenial)
       Status: Fix Committed => Fix Released

-- 
You received this bug notification because you are a member of नेपाली
भाषा समायोजकहरुको समूह, which is subscribed to Xenial.
Matching subscriptions: Ubuntu 16.04 Bugs
https://bugs.launchpad.net/bugs/1666986

Title:
  package does not include dpkg version

Status in curtin package in Ubuntu:
  Fix Released
Status in curtin source package in Xenial:
  Fix Released
Status in curtin source package in Yakkety:
  Fix Released
Status in curtin source package in Zesty:
  Fix Released

Bug description:
  ==== Begin SRU Template ====
  [Impact] 
  A feature was added to curtin upstream to allow the package build
  process to add its version to the curtin version reported.

  That version is exposed via:
    $ curtin version
    0.1.0~bzr460-0ubuntu1

  And then also
    $ python3 -c 'from curtin import version; print(version.version_string())'
    0.1.0~bzr460-0ubuntu1

  The above are shown in zesty.  However, the SRU'd versions did not
  get the packaging change to write that information, so they show only

    0.1.0

  The fix is to make the change made in zesty's debian/rules.

  [Test Case]

   $ apt-get install curtin
   $ curtin version

  Expect to see the packaged version reported, with bzr460 in it.

  [Regression Potential] 
  Low chance of regression, as 'curtin version' and the python library
  function version_string was only recently added for this feature, so
  nothing would depend on the broken behavior.

  ==== End SRU Template ====

  in trunk revno 448, we added patching of a file in curtin via
  debian/rules so that the packaged version would report its version
  correctly.

  ProblemType: Bug
  DistroRelease: Ubuntu 16.10
  Package: curtin 0.1.0~bzr460-0ubuntu1~16.10.1
  ProcVersionSignature: Ubuntu 4.9.0-15.16-generic 4.9.5
  Uname: Linux 4.9.0-15-generic x86_64
  ApportVersion: 2.20.3-0ubuntu8.2
  Architecture: amd64
  Date: Wed Feb 22 16:20:42 2017
  PackageArchitecture: all
  ProcEnviron:
   TERM=xterm-256color
   PATH=(custom, no user)
   LANG=C.UTF-8
  SourcePackage: curtin
  UpgradeStatus: No upgrade log present (probably fresh install)

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

_______________________________________________
Mailing list: https://launchpad.net/~group.of.nepali.translators
Post to     : group.of.nepali.translators@lists.launchpad.net
Unsubscribe : https://launchpad.net/~group.of.nepali.translators
More help   : https://help.launchpad.net/ListHelp

Reply via email to