On Tuesday, July 02, 2013 09:15:06 Rémy Oudompheng wrote:

The packages are ready but they will tend to install /etc/texmf files as .pacnew instead of replacing the old ones. When it happens fmtutil will not unhappy and the things will be unusable until the user overwrites the old files with the pacnews then re-runs "fmtutil --all" as root.

What do you advise? Leave the behaviour as is and write instructions in the news page? Forcibly overwriting old files?

I would prefer just echo these notes in .install. Regards, Felix Yan

2013/7/2 Federico Cinelli :

On 07/02/2013 12:19 AM, Felix Yan wrote:

...

On Tuesday, July 02, 2013 09:15:06 Rémy Oudompheng wrote:

...

The packages are ready but they will tend to install /etc/texmf files as .pacnew instead of replacing the old ones. When it happens fmtutil will not unhappy and the things will be unusable until the user overwrites the old files with the pacnews then re-runs "fmtutil --all" as root.

What do you advise? Leave the behaviour as is and write instructions in the news page? Forcibly overwriting old files?

I would prefer just echo these notes in .install.

Regards, Felix Yan

Just wondering how everything is going with these packages. Also, is there anything that I can do to help with the process?

The packages are already done. TeXlive is hardly the last thing I am doing for Arch, and it's only one release per year. Any help is welcome, at the moment the process remains quite smooth. Improvements and documentation will be needed: the scripts are diverging more and more from François Charette's version and I have not be very careful cleaning them up. Rémy.

On 2013/7/2 Rashif Ray Rahman wrote:

An official announcement is useful here because it requires user intervention. An install message is not appropriate (i.e. not sufficient for the problem at hand).

So, yes, if there is no other way to solve this you should post a news announcement explaining the reason why this intervention is required and the steps to take in order to solve it.

I think we can try that. I will upload the current version of packages to [testing]. I don't think it is a common practice to sliently overwrite files in /etc, but I don't understand why new files get installed as .pacnew. I have tried the upgrade path from a clean Texlive 2012 install and it does not replace the old files. Rémy.

On 03/07/13 10:02, Allan McRae wrote:

On 03/07/13 07:56, Rémy Oudompheng wrote:

...

On 2013/7/2 Rashif Ray Rahman wrote:

...

An official announcement is useful here because it requires user intervention. An install message is not appropriate (i.e. not sufficient for the problem at hand).

So, yes, if there is no other way to solve this you should post a news announcement explaining the reason why this intervention is required and the steps to take in order to solve it.

I think we can try that. I will upload the current version of packages to [testing]. I don't think it is a common practice to sliently overwrite files in /etc, but I don't understand why new files get installed as .pacnew.

I have tried the upgrade path from a clean Texlive 2012 install and it does not replace the old files.

Hi Remy,

Can you send me a pacman --debug log for the upgrade from a fresh Texlive 2012 install that shows the .pacnew being created?

I missed that these files were changing packages. This is pacman bug https://bugs.archlinux.org/task/24543