touch-packages team mailing list archive

[Matthias Klose <doko@xxxxxxxxxx>]

On 07/10/2015 07:58 AM, Steve Langasek wrote:
> Reviewing the debdiff of the package uploaded to the queue.
>  - debian/patches/apport-support.dpatch,

unused ("dpatch"). left over.

> debian/patches/doc-build.diff

needed to build with sphinx 0.5, trusty has 1.2

> debian/patches/installed-testsuite.diff

this just disabled a test, fixed it upstream.

> debian/patches/issue21097.diff

applied upstream

> why have these patches been removed?  I find no references to these in
the changelog.


> - debian/rules:
> @@ -221,21 +231,22 @@
>      stamps/stamp-check stamps/stamp-pystone stamps/stamp-pybench
>         touch $@
>  
> -PROFILE_EXCLUDES = test_compiler test_distutils test_platform test_subprocess \
> +PROFILE_EXCLUDES = test_compiler test_distutils test_subprocess \
>         test_multiprocessing test_socketserver \
>         test_thread test_threaded_import test_threadedtempfile \
>         test_threading test_threading_local test_threadsignals \
>         test_concurrent_futures test_ctypes \
>         test_dbm_dumb test_dbm_ndbm test_pydoc test_sundry \
> -       test_signal test_ioctl test_gdb
> +       test_signal test_ioctl test_gdb test_ensurepip test_venv
>  @@ -416,6 +426,7 @@
>  endif
>  TESTOPTS = -j 1 -w -u$(TEST_RESOURCES)
>  TEST_EXCLUDES =
> +TEST_EXCLUDES += test_ensurepip test_venv
>  ifeq ($(on_buildd),yes)
>    TEST_EXCLUDES += test_tcl test_codecmaps_cn test_codecmaps_hk \
>          test_codecmaps_jp test_codecmaps_kr test_codecmaps_tw \
> 
> Why are the ensurepip and venv tests being skipped?  Considering the
> great deal of work that's been put into ensurepip and venv in this
> version, don't we want this to pass the tests?

this would add build dependencies on all the setuptools and pip packages
currently in universe, because we remove the internal copies in the packages.
these tests just failed in the 3.4.0 packages.

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

Title:
  update Python3 for trusty

Status in python3-defaults package in Ubuntu:
  Confirmed
Status in python3-stdlib-extensions package in Ubuntu:
  Confirmed
Status in python3.4 package in Ubuntu:
  Confirmed
Status in python3-defaults source package in Trusty:
  New
Status in python3-stdlib-extensions source package in Trusty:
  New
Status in python3.4 source package in Trusty:
  New

Bug description:
  update Python3 for trusty.

  Rationale: the LTS was released with 3.4.0, the first 3.4 release
  which certainly had some issues. The idea is to update the python3.4
  packages to the version found in 15.04 (vivid), which currently
  doesn't have any outstanding issues.  A test rebuild of the trusty
  main component was done without showing any regressions during the
  package builds.

  http://people.ubuntuwire.org/~wgrant/rebuild-ftbfs-test/test-rebuild-20150317-trusty.html
  http://people.ubuntuwire.org/~wgrant/rebuild-ftbfs-test/test-rebuild-20150501-updates-trusty.html

  To validate this SRU, I'm proposing to use the results from the test
  rebuild, plus evaluating the testsuite results of the python3.4
  package itself.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/python3-defaults/+bug/1348954/+subscriptions