Re: [arch-general] Texlive 2013 packages releases to [testing]
On 07/02/2013 06:01 PM, Rémy Oudompheng wrote: If pacnew files appear (notably texmf.cnf and fmtutil.cnf), and the installation reports a failure in regenerating formats (which you will know by not being able to use an engine), you will need to handle the pacnew files, and run "fmtutil-sys --all" by hand. What does 'handle the .pacnew' files mean - move them over the orig? If this situation reaches a high level of absurdity, and if possible considering pacman's behaviour, new packages not behaving like this might be built later before going to [extra]. I'd vote for non-absurd behaviour sooner rather than later ... :-) gene
[arch-general] OpenNTPd not correcting time on boot
Hi, First time posting so forgive me if I get it wrong. (This is already a resend because I used the wrong email previously!) I'm using OpenNTPd as a time server for my local network, but I have a slight issue. I run it on my Raspberry Pi which lacks a hardware clock, so every time I boot it, it thinks the time is 1970. In the systemd init file, openntpd.service, it runs the ntpd daemon with the '-s' option, which tell it that if the time is really far out of sync, just update it straight to the time that the server has. The problem is, this doesn't happen after boot. If I manually set the time with 'date -s @00' and then restart the openntpd service it will work, but not automatically after boot up. I suspect it might be that it's not able to talk to a server because it's starting the service before the network is ready or something, but I'm using a static IP and have told openntpd.service that "wants" and "after" both == network.target. Any ideas? Joe -- *:wq!*
[arch-general] Texlive 2013 packages releases to [testing]
Hello, I have pushed TeXLive 2013 packages to [testing]. The main difference with the 2012 packages is that /etc/texmf files are now in texlive-core rather than texlive-bin. The texlive-bin package now contains almost only binaries, and texlive-core contains all basic data files including the ones in /etc/texmf. Feel free to report any issues you encounter. If you have an existing installation, the upgrade might install new versions of /etc/texmf/ files as *.pacnew. It is unlikely that things work properly if you don't handle the pacnew files unless you realy know what you are doing. If pacnew files appear (notably texmf.cnf and fmtutil.cnf), and the installation reports a failure in regenerating formats (which you will know by not being able to use an engine), you will need to handle the pacnew files, and run "fmtutil-sys --all" by hand. If this situation reaches a high level of absurdity, and if possible considering pacman's behaviour, new packages not behaving like this might be built later before going to [extra]. Regards, Rémy.
