Custom Query (1155 matches)

During translation I find something for me strange in English documentation, that I like to fix

• virtualbox_quickstart.rst
  • On linux do the following -> On Ubuntu do the following

• osm_dataset_overview.rst
  • but the maps can also be viewed, imported, or edited in many applications such as Quantum GIS, OpenLayers, -> but the data can also be viewed, imported, or edited in many applications such as :doc:qgis_overview, :doc:OpenLayers <openlayers_overview>
  • polyline, and area coverage. -> polyline, area coverage and relations.

• openjub_overview.rst
  • deegree -> :doc:deegree <deegree_overview>

• geomoose_overview.rst
  • MapServer and OpenLayers -> :doc:MapServer <mapserver_overview> and :doc:OpenLayers <openlayers_overview>

• gpsdrive_overview.rst
  • LANDSAT or OpenStreetMap -> LANDSAT or :doc:OpenStreetMap <osm_dataset_overview>
  • :doc:OpenStreetMap <osm_dataset_overview> data stored in a :doc:PostGIS <postgis_overview> database using :doc:Mapnik <mapnik_overview>

• gpsprune_overview.rst
  • It uses OpenStreetMap imagery -> It uses :doc:OpenStreetMap <osm_dataset_overview> imagery

• mapproxy_overview.rst
  • for an OpenLayers web client -> for an :doc:OpenLayers <openlayers_overview> web client
  • others in core features

• metacrs_overview.rst
  • a lot of software after "The sub-projects that make up MetaCRS include:"

• osgeoearth_overview.rst
  • change link of MapServer, WMS and OpenStreetMap from external resource to internal one

• qgis_overview.rst
  • through integration with GRASS -> through integration with :doc:GRASS <grass_overview>
  • PostgreSQL Database tables -> PostgreSQL/PostGIS Database tables

• rasdaman_overview.rst
  • A rasdaman driver is a part of the GDAL -> A rasdaman driver is a part of the :doc:GDAL <gdal_overview>
  • a MapServer integration is available in beta -> a :doc:MapServer <mapserver_overview> integration is available in beta

• viking_overview.rst
  • It works with OpenStreetMap data -> It works with :doc:OpenStreetMap <osm_dataset_overview> data
  • from services such as OpenStreetMap and -> from services such as :doc:OpenStreetMap <osm_dataset_overview> and

• zoo-project_overview.rst
  • based on the GEOS and OGR Libraries -> based on the :doc:GEOS <geos_overview.html> and :doc:OGR Libraries <gdal_overview>

• in all pages a lot of standard could be linked to appropriate pages

This issue happens when build_chroot script is used with live session username set to "user". The created iso refuses to autologin. This has been tracked with debug script so far and limited down to 3 packages (liblas, rasdaman and mb-system). When initrd modifications are not used this issue is not present.

Proposed solutions:

1. Create the iso first without initrd customization and then use the created image file to run a second customization.
2. Keep building with debug chroot scripts until we track down the package causing this.

Any other ideas I am missing?

Hi,

it worries me a bit that a new user will pick up the DVD and click past the warnings that install ubuntu will reformat your hard drive. great way to lose a customer.

the default 'chroot method' puts this in your face a bit more, so we might consider making the autoboot just offer the "Try ${RELEASE}" button, and leave the "Install ${RELEASE}" to the documented desktop icon or elsewhere.

it seems the file to hack is /usr/share/ubiquity/gtk/stepLanguage.ui

maybe we can just remove the GtkButton <child> object for "install_ubuntu" on lines 88-108 and the image object for ubuntu_installed.png on lines 75-87? (hopefully the widget packing of the rest adapts well)

better yet, figure how to bypass ubiquity at boot time all together, but still have it work if the user installs from the menu. maybe just edit /etc/init/ubiquity.conf and comment out the "starton" lines at the top?

Hamish