2.8.6-1ubuntu1 is the current package in Lucid which contains the new
wordpress-l10n binary. Marking Fix Released.
** Changed in: wordpress (Ubuntu)
Status: In Progress => Fix Released
--
please package localization files separately
https://bugs.launchpad.net/bugs/414838
You received this
Over the last couple of weeks I coached Alex to prepare the necessary
changes for fixing this bug. Last week, Giuseppe has made an upload to
Debian that obliviated the need to any particular Ubuntu changes.
Therefore, I suggest to merge 2.8.4-3 from Debian unstable to fix this
bug.
Thank you Alex
Rolf Leggewie ha scritto:
> ... but eventually you will need to understand that you're still raising
> a new issue, separate from this one. The bug you are talking about is
> already in the package in the archive. So, that obviously (!) is a
> separate issue from this one.
Yes it is a separate
Giuseppe, your work in Debian and you pointing out this potential (!)
copyright problem here is appreciated ...
Giuseppe Iuculano wrote:
> I don't know if is the same in Ubuntu, but if I split i18n files in a separate
> package, it will go in NEW queue, and so, yes, if there is a copyright issue
>
Rolf Leggewie ha scritto:
> PS: Because you make such a fuss here (in the wrong place, really), I
> just had a look at debian/copyright. Haha! You are the Debian
...
Congratulations, your arrogant tone is really appreciate.
> maintainer. So, if there's anything fishy about the copyright, that
Giuseppe Iuculano wrote:
> So if you are going to package some files with no license (and yes, this is a
> bug also in the current wordpress package), Isn't this related to the new
> package?
Again, if there is currently a problem, then it's a bug, but not this
bug. One isse, one ticket as I alr
Rolf Leggewie ha scritto:
> Giuseppe Iuculano wrote:
>> A good start point is to ask upstream to clarify license for all
>> localization files.
>>
>
> Not really. If there is anything that needs to be done wrt the
> copyright file, then that would be a bug in itself, only slightly
> related to
Giuseppe Iuculano wrote:
> A good start point is to ask upstream to clarify license for all
> localization files.
>
Not really. If there is anything that needs to be done wrt the
copyright file, then that would be a bug in itself, only slightly
related to this one. One issue, one ticket, plea
A good start point is to ask upstream to clarify license for all
localization files.
--
please package localization files separately
https://bugs.launchpad.net/bugs/414838
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
--
ubuntu-bugs m
Hi Alex, try to grab me on IRC or Jabber for coaching.
--
please package localization files separately
https://bugs.launchpad.net/bugs/414838
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
--
ubuntu-bugs mailing list
ubuntu-bugs@lists.
Rolf
Couple weeks have passed since your offer, and noone took upon it :-)
So I would take it now. What should I do?
Alex.
--
please package localization files separately
https://bugs.launchpad.net/bugs/414838
You received this bug notification because you are a member of Ubuntu
Bugs, which is
11 matches
Mail list logo
