Unfortunately, we can't just sync from debian because we published a
separate mkpasswd package during the lucid cycle and thus people
upgrading will see the failure in bug 632791.
--
when whois and mkpasswd are build locally they have .mo file conflicts
https://bugs.launchpad.net/bugs/601803
You
There are several options to fix this issue:
1. Add a specific catalog for mkpasswd.
2. Create a whois-common package to share the po files.
3. Don't split the packages and sync from Debian (and reopen bug 284416).
The easiest solution seem to be 3: mkpasswd would be part of whois
again, we'd
** Changed in: server-papercuts
Assignee: (unassigned) = Mathias Gug (mathiaz)
--
when whois and mkpasswd are build locally they have .mo file conflicts
https://bugs.launchpad.net/bugs/601803
You received this bug notification because you are a member of Ubuntu
Server Team, which is
** Changed in: server-papercuts
Importance: Undecided = Low
** Changed in: server-papercuts
Status: New = Confirmed
** Changed in: server-papercuts
Milestone: None = maverick-beta
--
when whois and mkpasswd are build locally they have .mo file conflicts
** Also affects: server-papercuts
Importance: Undecided
Status: New
--
when whois and mkpasswd are build locally they have .mo file conflicts
https://bugs.launchpad.net/bugs/601803
You received this bug notification because you are a member of Ubuntu
Server Team, which is subscribed to
The line in debian/rules:
cd po $(MAKE) install BASEDIR=$D $(MAKE) install BASEDIR=$W
is responsible for it. Ideally mkpasswd would get its own NLS_CAT_NAME or just
a copy of the whois.mo (not ideal as it will duplicate some strings).
--
when whois and mkpasswd are build locally they
** Changed in: whois (Ubuntu)
Importance: Undecided = Medium
** Changed in: whois (Ubuntu)
Status: New = Confirmed
--
when whois and mkpasswd are build locally they have .mo file conflicts
https://bugs.launchpad.net/bugs/601803
You received this bug notification because you are a
