14:28 <infinity> Breaks loops are pretty friendly (compared to Conflicts 
loops), they just both deconfigure, both upgrade, and both configure.
14:28 <infinity> I tested from 2.21, and it went fine, I can't see why it would 
be worse from older  versions.
14:29 <infinity> (The libc->Breaks locales relationship is standard in the 
Debian packaging to make sure the tools match libc, I was just adding it back)


** Tags added: block-proposed

-- 
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to langpack-locales in Ubuntu.
https://bugs.launchpad.net/bugs/1394929

Title:
  [FFe]Please provide 'locales-all' as in Debian

Status in glibc package in Ubuntu:
  Confirmed
Status in langpack-locales package in Ubuntu:
  Confirmed

Bug description:
  Repurposing this bug as a Feature Freeze exception request to merge
  langpack-locales into glibc, and make locales-all available in the
  process.  Working on getting that all done and properly tested by
  tonight, but if this doesn't make it, it'll happen in early 16.10
  instead.

  [Original Report]
  Hi,

  Debian provides a 'locales-all' package, which is very convenient to
  ensure all locales are available, and installs very quickly.

  It's particularly handy when providing i18n'd web applications (e.g. that use 
php-gettext).
  As they may be accessed by visitors of all supported languages, rather than 
documenting how the server administrator should enable a list of 10-15 
languages by reconfiguring 'locales', the packager can just add 'locales-all' 
to the Recommends or Depends.
  See for instance the FusionForge package in Debian 
(https://packages.debian.org/jessie/gforge-web-apache2).

  Cheers!
  Sylvain

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

-- 
Mailing list: https://launchpad.net/~desktop-packages
Post to     : [email protected]
Unsubscribe : https://launchpad.net/~desktop-packages
More help   : https://help.launchpad.net/ListHelp

Reply via email to