Hi Kyle! First: Thanks very much for the code!!! I just reviewed your change and you used an obsolete branch: http://acurti.es/PTm The code for the actual branch changed a lot, because I migrated from Glade to GTKbuilder, from gksu application to DBus service, and more things. I will implement for the actual branch: http://acurti.es/OTm Thanks very much for the bug and the code ;) Cheers!
-- You received this bug notification because you are a member of Gufw Developers, which is subscribed to Gufw. https://bugs.launchpad.net/bugs/688601 Title: file conflict in mo files and license issue Status in Gufw: In Progress Status in “gui-ufw” package in Ubuntu: In Progress Bug description: Hi, This package has a couple issues: * Its translation files (the gufw.mo files, one for each language) are installed into /usr/share/locale-langpack/... However, this location is reserved for Ubuntu language pack .mo files. If this pkg ever moves into Ubuntu Main (which means language packs would install gufw.mo files into /usr/share/locale-langpack/... ), there would be a file conflict (two binary pkgs trying to install the same file). This would prevent installation of whichever pkg was installed second. - FIX: This can be fixed by releasing a new verson of the package that installs the .mo files into the package's location: /usr/share/locale/... * The source pkg in the archives contains .mo files instead of .po files. The proper appoach is for the src package to contain .po files in a directory named po/. that directory should to include a file named POTFILES.in that lists the path to every file with translatable messages. (Doing this enables intltool.) Then the .mo files need to be created on each build of the pkg. (Note, containing .mo files in the src package may be a license violation). Cheers, Kyle _______________________________________________ Mailing list: https://launchpad.net/~gufw-developers Post to : [email protected] Unsubscribe : https://launchpad.net/~gufw-developers More help : https://help.launchpad.net/ListHelp
