Bug #987050 “No “Prepare for shipping ...” option after OEM inst...” : Bugs : ubiquity package : Ubuntu

Revision history for this message

Ubuntu QA Website (ubuntuqa) wrote on 2012-04-23:

#1

This bug has been reported on the Ubuntu ISO testing tracker.

A list of all reports related to this bug can be found here:
http://iso.qa.ubuntu.com/qatracker/reports/bugs/987050

tags:

added: iso-testing

Revision history for this message

Stéphane Graber (stgraber) wrote on 2012-04-23:

#2

Can't reproduce on Ubuntu Alternate i386, looks like it's Kubuntu specific.

Revision history for this message

Colin Watson (cjwatson) wrote on 2012-04-24:

#3

A workaround would be to add oem-config-slideshow-ubuntu to the ship seed, if you have room - it's a bit north of 700KB and isn't actually used for the KDE frontend, so it's a bit of a waste, but the alternative is a ubiquity upload which is a bit of a pain at this point in the release.

affects:	debian-installer (Ubuntu) → ubiquity (Ubuntu)
Changed in ubiquity (Ubuntu):
assignee:	nobody → Colin Watson (cjwatson)
importance:	Undecided → High
status:	New → Fix Committed

Revision history for this message

Colin Watson (cjwatson) wrote on 2012-04-24:

#4

I worked around this for 12.04 with a seed change.

Revision history for this message

Scott Kitterman (kitterman) wrote on 2012-04-24:

#5

Medium due to workaround.

Changed in ubiquity (Ubuntu):
importance:	High → Medium
milestone:	none → ubuntu-12.04.1

Revision history for this message

Launchpad Janitor (janitor) wrote on 2012-05-17:

#6

Download full text (6.3 KiB)

This bug was fixed in the package ubiquity - 2.11.0

---------------
ubiquity (2.11.0) quantal; urgency=low

  [ Colin Watson ]
  * Install oem-config-slideshow-ubuntu in a separate pass from
    oem-config-$frontend and ubiquity-frontend-$frontend, since it may be
    missing from images; and only do this for the GTK frontend in any case,
    since other frontends don't currently use the slideshow (LP: #987050).
  * Re-enable alpha warning for quantal.
  * Upgrade to debhelper 9 for improved handling of compiler flags. Make
    sure that /usr/lib/girepository-1.0/ stays where it's supposed to be
    despite changes in the default libdir for multiarch.
  * Port to Python 3:
    - Use Python 3-style print functions.
    - Use "except Exception as e" syntax rather than the old-style "except
      Exception, e".
    - Use reduce from functools rather than relying on the builtin.
    - Use list comprehensions rather than filter or map.
    - Use open() rather than file().
    - Import configparser rather than ConfigParser if available.
    - Use input() rather than raw_input() when running under Python 3.
    - Use set comprehensions.
    - Import quote from urllib.parse rather than urllib if available.
    - Use new-style octal literals.
    - Use test.support rather than test.test_support if available.
    - Add --python2 and --python3 options to tests/run to force running the
      tests under Python 2 or 3 respectively.
    - Handle renaming of __builtin__ to builtins in Python 3.
    - Only pass unicode=1 to gettext.install in Python 2.
    - Port ubiquity.auto_update to python-apt 0.8 progress classes.
    - Use Python 3 names for itertools.izip and itertools.izip_longest if
      available.
    - Use helpers from the six module to deal with some bytes/unicode
      differences.
    - As a general rule, open subprocesses with universal_newlines=True when
      expecting to read text from them. This has no effect on Python 2
      (aside from \r\n conversion and the like, which is mostly a no-op for
      us), but causes Python 3 to read str rather than bytes. The
      exceptions at the moment are: debconf-copydb subprocesses, which
      return mixed-encoding data that needs to be handled specially; and
      when feeding the output of a subprocess to hashlib.
    - Use six.reraise rather than the three-argument form of raise.
    - Adjust test_filteredcommand for Python 3 text handling.
    - Fix test_ubi_partman.question_has_variables to handle templates files
      as binary data, since they're mixed-encoding.
    - Cope with assertItemsEqual/assertCountEqual naming difference between
      Python 2.7 and 3.2.
    - Rearrange ubiquity.i18n.get_translations to treat debconf-copydb
      output as binary data and do field-dependent decoding.
    - Adjust test_misc and test_upower to cope with file type changes in
      Python 3.
    - Use xml.etree.cElementTree instead of libxml2; it's faster, has a
      smaller footprint by virtue of being built into the standard library,
      arguably easier to read, and works with Python 3.
    - Fix a slew of file handle leaks, including making much more liberal
      use of context managers.
   ...

This bug was fixed in the package ubiquity - 2.11.0

---------------
ubiquity (2.11.0) quantal; urgency=low

[ Colin Watson ]
  * Install oem-config-slideshow-ubuntu in a separate pass from
    oem-config-$frontend and ubiquity-frontend-$frontend, since it may be
    missing from images; and only do this for the GTK frontend in any case,
    since other frontends don't currently use the slideshow (LP: #987050).
  * Re-enable alpha warning for quantal.
  * Upgrade to debhelper 9 for improved handling of compiler flags.  Make
    sure that /usr/lib/girepository-1.0/ stays where it's supposed to be
    despite changes in the default libdir for multiarch.
  * Port to Python 3:
    - Use Python 3-style print functions.
    - Use "except Exception as e" syntax rather than the old-style "except
      Exception, e".
    - Use reduce from functools rather than relying on the builtin.
    - Use list comprehensions rather than filter or map.
    - Use open() rather than file().
    - Import configparser rather than ConfigParser if available.
    - Use input() rather than raw_input() when running under Python 3.
    - Use set comprehensions.
    - Import quote from urllib.parse rather than urllib if available.
    - Use new-style octal literals.
    - Use test.support rather than test.test_support if available.
    - Add --python2 and --python3 options to tests/run to force running the
      tests under Python 2 or 3 respectively.
    - Handle renaming of __builtin__ to builtins in Python 3.
    - Only pass unicode=1 to gettext.install in Python 2.
    - Port ubiquity.auto_update to python-apt 0.8 progress classes.
    - Use Python 3 names for itertools.izip and itertools.izip_longest if
      available.
    - Use helpers from the six module to deal with some bytes/unicode
      differences.
    - As a general rule, open subprocesses with universal_newlines=True when
      expecting to read text from them.  This has no effect on Python 2
      (aside from \r\n conversion and the like, which is mostly a no-op for
      us), but causes Python 3 to read str rather than bytes.  The
      exceptions at the moment are: debconf-copydb subprocesses, which
      return mixed-encoding data that needs to be handled specially; and
      when feeding the output of a subprocess to hashlib.
    - Use six.reraise rather than the three-argument form of raise.
    - Adjust test_filteredcommand for Python 3 text handling.
    - Fix test_ubi_partman.question_has_variables to handle templates files
      as binary data, since they're mixed-encoding.
    - Cope with assertItemsEqual/assertCountEqual naming difference between
      Python 2.7 and 3.2.
    - Rearrange ubiquity.i18n.get_translations to treat debconf-copydb
      output as binary data and do field-dependent decoding.
    - Adjust test_misc and test_upower to cope with file type changes in
      Python 3.
    - Use xml.etree.cElementTree instead of libxml2; it's faster, has a
      smaller footprint by virtue of being built into the standard library,
      arguably easier to read, and works with Python 3.
    - Fix a slew of file handle leaks, including making much more liberal
      use of context managers.
    - When creating a default username based on the user's full name, decode
      it back to a Unicode type after running it through the
      ascii_transliterate encoder.
    - Remove __pycache__ directories on clean.
    - Use 'from __future__ import unicode_literals' in tests requiring
      Unicode literals.
    - Cope with various builtins and dict methods returning iterators rather
      than lists in Python 3.
    - Use chr rather than unichr in Python 3.
    - Use six.string_types rather than types.StringTypes.
    - Pass a byte string to Gtk.CssProvider.load_from_data.
    - Replace all calls to unicode() with calls to six.text_type() or
      misc.utf8() as appropriate.
    - Use unicode_literals in ubiquity.keyboard_names.
    - Fix up ubiquity.filteredcommand.debug and its tests for Python 3.  In
      Python 3, we can write Unicode strings (i.e. str) directly to
      sys.stderr, and its defaults are such that the worst case is that they
      get backslash-encoded.  Arrange the tests to simulate this.
    - Simplify ubiquity.nm.decode_ssid using bytearray(), allowing it to
      work with Python 3 too.
    - Open .debs in binary mode when verifying their contents.
    - Decode text read from debconffilter subprocesses in Python 3.
    - Only encode preseeded values in Python 2.  Python 3's debconf module
      accepts Unicode strings directly.
    - Encode the second argument to struct.pack.
    - Fix byte array handling when generating /etc/iftab.
    - Fix a missing bit of python-apt 0.8 porting in ubiquity.install_misc.
    - Open /var/lib/dpkg/status in binary mode when compressing it.
    - Pass bytes rather than text to kdecore.ki18n.
    - Call sip.setapi("QVariant", 1) on KDE frontend startup, pending a more
      complete port to the new API.
    - Use boolean tests rather than isNull, to cope with getting ordinary
      Python strings rather than QStrings.
    - In Python 3, pass strings directly to Qt rather than creating
      QStrings.
    - (Build-)depend on python3-gi, since python3-gi-cairo doesn't depend on
      that and in any case we use it directly.
  * Add Burmese translations.
  * Remove obsolete uxlaunch handling, since it's no longer used and has
    been removed from the archive.
  * Avoid locking failures when clicking on the "update this installer" link
    more than once.
  * Move a bit more code into ubiquity.install_misc, including a new
    target_file helper method.
  * Remove unnecessary #! lines from non-executable files.
  * Improve download verification to handle systems not configured for
    multiarch, i.e. anything other than amd64 by default (LP: #998492).
  * Automatic update of included source packages: choose-mirror 2.39ubuntu5,
    clock-setup 0.110ubuntu1, debian-installer-utils 1.89ubuntu1,
    localechooser 2.40ubuntu1.

[ Stéphane Graber ]
  * Spawn dconf-service from ubiquity-dm and drop all the dbus-launch calls.
    This should ensure we have a single dconf-service running and that gets
    killed on ubiquity's exit.
  * ubiquity-dm: Turn on the compositor in metacity. (LP: #987168)
  * wallpaper: Update code to properly set the wallpaper when compositing
    is enabled.
 -- Colin Watson <cjwatson@ubuntu.com>   Thu, 17 May 2012 03:09:54 +0100

Changed in ubiquity (Ubuntu Quantal):
status:	New → Fix Released

Stéphane Graber (stgraber) on 2012-07-13

Changed in ubiquity (Ubuntu Precise):
status:	Fix Committed → In Progress

Stéphane Graber (stgraber) on 2012-07-17

description:

updated

Revision history for this message

Brian Murray (brian-murray) wrote on 2012-07-19: Please test proposed package

#7

Hello Scott, or anyone else affected,

Accepted ubiquity into precise-proposed. The package will build now and be available at http://launchpad.net/ubuntu/+source/ubiquity/2.10.18 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 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 change the bug tag from verification-needed to verification-done. If it does not, 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 ubiquity (Ubuntu Precise):
status:	In Progress → Fix Committed
tags:	added: verification-needed

Revision history for this message

Stéphane Graber (stgraber) wrote on 2012-07-27:

#8

OEM install worked and no oem-config-slideshow installed post-install, marking this a pass.

tags:

added: verification-done
removed: verification-needed

Revision history for this message

Launchpad Janitor (janitor) wrote on 2012-08-02:

#9

This bug was fixed in the package ubiquity - 2.10.19

---------------
ubiquity (2.10.19) precise-proposed; urgency=low

  * Automatic update of included source packages: base-installer
    1.122ubuntu7.1, debian-installer-utils 1.88ubuntu2.1, flash-kernel
    2.28ubuntu42.2. (one-time update from precise-proposed) (LP: #1021293)
-- Stephane Graber <email address hidden> Mon, 30 Jul 2012 10:36:51 -0400

Changed in ubiquity (Ubuntu Precise):
status:	Fix Committed → Fix Released

Ubuntu
ubiquity package

No "Prepare for shipping ..." option after OEM install from D-I

Bug Description

Related branches

Other bug subscribers

Remote bug watches

	Status	Importance	Assigned to	Milestone
ubiquity (Ubuntu)	Fix Released	Medium	Colin Watson	Ubuntu ubuntu-12.04.1
Precise	Fix Released	Medium	Colin Watson	Ubuntu ubuntu-12.04.1
Quantal	Fix Released	Undecided	Unassigned

Ubuntuubiquity package

No "Prepare for shipping ..." option after OEM install from D-I

Bug Description

Related branches

Other bug subscribers

Remote bug watches

Ubuntu
ubiquity package