- Arch-announce - lists.archlinux.org

[arch-announce] Fontconfig 2.10.1 update - manual intervention required
by Arch Linux: Recent news updates: Andreas Radke 06 Sep '12

06 Sep '12

Andreas Radke wrote: Fontconfig 2.10.1 update overwrites symlinks created by the former package version. These symlinks need to be removed before any further update: rm /etc/fonts/conf.d/20-unhint-small-vera.conf rm /etc/fonts/conf.d/29-replace-bitmap-fonts.conf rm /etc/fonts/conf.d/30-metric-aliases.conf rm /etc/fonts/conf.d/30-urw-aliases.conf rm /etc/fonts/conf.d/40-nonlatin.conf rm /etc/fonts/conf.d/45-latin.conf rm /etc/fonts/conf.d/49-sansserif.conf rm /etc/fonts/conf.d/50-user.conf rm /etc/fonts/conf.d/51-local.conf rm /etc/fonts/conf.d/60-latin.conf rm /etc/fonts/conf.d/65-fonts-persian.conf rm /etc/fonts/conf.d/65-nonlatin.conf rm /etc/fonts/conf.d/69-unifont.conf rm /etc/fonts/conf.d/80-delicious.conf rm /etc/fonts/conf.d/90-synthetic.conf pacman -Syu Main systemwide configuration should be done by symlinks (especially for autohinting, sub-pixel and lcdfilter): cd /etc/fonts/conf.d ln -s ../conf.avail/XX-foo.conf Check also [Font_Configuration][1] and [Fonts][2]. [1]: https://wiki.archlinux.org/index.php/Font_Configuration [2]: https://wiki.archlinux.org/index.php/Fonts URL: http://www.archlinux.org/news/fontconfig-2101-update-manual-intervention-re…

1 0

[arch-announce] netcfg-2.8.9 drops initscripts compatibility
by Arch Linux: Recent news updates: Florian Pritz 11 Aug '12

11 Aug '12

Florian Pritz wrote: All interfaces should now be configured in `/etc/conf.d/netcfg` rather than `/etc/rc.conf`. URL: http://www.archlinux.org/news/netcfg-289-drops-initscripts-compatibility/

1 0

[arch-announce] Install media 2012.08.04 available
by Arch Linux: Recent news updates: Pierre Schmitz 04 Aug '12

04 Aug '12

Pierre Schmitz wrote: The August snapshot of our live and install media comes with updated packages and the following changes on top of the [previous iso image][1]: * GRUB 2.0 instead of the legacy 0.9 version is available. * The [Installation Guide][2] can be found at _/root/install.txt_. * ZSH with [Grml's configuration][3] is used as interactive shell to provide a user friendly and more convenient environment. This includes completion support for pacstrap, arch-chroot, pacman and most other tools. * The network daemon is started by default which will automatically setup your network if DHCP is available. Note that all these changes only affect the live system and not the base system you install using pacstrap. The iso image can be downloaded from our [Download page][4]. The next snapshot is scheduled for September. [1]: https://www.archlinux.org/news/install-media-20120715-released/ [2]: https://wiki.archlinux.org/index.php/Installation_Guide [3]: http://grml.org/zsh/ [4]: https://www.archlinux.org/download/ URL: https://www.archlinux.org/news/install-media-20120804-available/

1 0

[arch-announce] Changes to rc.conf and crypttab
by Arch Linux: Recent news updates: Tom Gundersen 30 Jul '12

30 Jul '12

Tom Gundersen wrote: As of `initscripts-2012.07.5`, the default format of `/etc/rc.conf` and `/etc/crypttab` have changed. See their respective man pages for more details. The purpose of this change is to unify the configuration of systemd and initscripts. This will allow us to share code and documentation, and should make maintenance of initscripts simpler in the long-run. The old format is still supported, so old config files should still work unchanged. URL: http://www.archlinux.org/news/changes-to-rcconf-and-crypttab/

1 0

[arch-announce] pkgstats now collects modules usage
by Arch Linux: Recent news updates: Tom Gundersen 30 Jul '12

30 Jul '12

Tom Gundersen wrote: In an attempt at making the default kernel and initramfs more robust for the majority of users, we would like to gather some information about which kernel modules and cpu architecture are most common. As of version 2.3, pkgstats is now able to collect this information. We would like to encourage everyone to install pkgstats so your setup will be taken into account. See [this][1] previous news item for more information about pkgstats. [1]: https://www.archlinux.org/news/pkgstats-round-two-take-your-vote-and- help-improving-arch/ URL: http://www.archlinux.org/news/pkgstats-now-collects-modules-usage/

1 0

[arch-announce] Install media 2012.07.15 released
by Arch Linux: Recent news updates: Pierre Schmitz 22 Jul '12

22 Jul '12

Pierre Schmitz wrote: New iso images containing a current Arch Linux snapshot have been released and can be found on our [Download][1] page. Most notable change is that AIF (the Arch Installation Framework) is no longer included but instead some simple [install scripts][2] are provided to aid in the installation process. This means a menu driven installer is no longer available and we rely more on documentation to guide new users. We would like to encourage our community to fill in the remaining gaps in [our wiki][3]. >From now on our install images are signed and it is highly recommend to verify their signature before use. On Arch Linux this can be done by using `pacman-key -v <iso-file>.sig`. * The pacman keyring is automatically initialized on bootup. Therefore signature verification is available on the live media and will work out of the box on the installed system. * Instead of six different images we only provide a single one which can be booted into an i686 and x86_64 live system to install Arch Linux over the network. Media containing the [core] repository are no longer provided. * Regular iso snapshots are planned on a monthly basis. * The install media can also be booted directly via [PXE][4]. Note that its PGP signature cannot be verified this way! * More archiso related options and new features can be found in its [README][5] file. AIF had to be dropped due to lack of maintenance and contributions. Of course we would appreciate it if people would start hacking on it to bring it up to par. [1]: https://www.archlinux.org/download/ [2]: https://wiki.archlinux.org/index.php/Arch_Install_Scripts [3]: https://wiki.archlinux.org/ [4]: https://releng.archlinux.org/pxeboot/ [5]: https://projects.archlinux.org/archiso.git/plain/README URL: http://www.archlinux.org/news/install-media-20120715-released/

1 0

[arch-announce] GRUB legacy no longer supported
by Arch Linux: Recent news updates: Ronald van Haren 20 Jul '12

20 Jul '12

Ronald van Haren wrote: GRUB 2.x has moved to [core]. With this move support for GRUB legacy (i.e. version 0.9x) is dropped, which is now moved to AUR. Although GRUB legacy will not be removed from your system and will stay fully functional, you should consider upgrading to GRUB version 2.x, or one of the other supported bootloaders. Please consult [the GRUB wiki page][1] for detailed installation instructions for GRUB version 2.x. [1]: https://wiki.archlinux.org/index.php/Grub URL: http://www.archlinux.org/news/grub-legacy-no-longer-supported/

1 0

[arch-announce] The /lib directory becomes a symlink
by Arch Linux: Recent news updates: Allan McRae 14 Jul '12

14 Jul '12

Allan McRae wrote: All Arch Linux packages have had there files in the /lib directory moved to /usr/lib and now /lib is a symlink to usr/lib. When performing this update, pacman will likely identify a conflict in the /lib directory. In the simplest case, this is worked around by doing: ` pacman -Syu --ignore glibc pacman -Su ` Never use `--force` during this update. If either of this steps does not work (e.g. due to dependency version issues, file conflicts in /lib), refer to this [guide][1] for more detailed instructions on performing this upgrade. [1]: https://wiki.archlinux.org/index.php/DeveloperWiki:usrlib URL: http://www.archlinux.org/news/the-lib-directory-becomes-a-symlink/

1 0

[arch-announce] filesystem upgrade - manual intervention required
by Arch Linux: Recent news updates: Tom Gundersen 07 Jun '12

07 Jun '12

Tom Gundersen wrote: As of `filesystem-2012.6-2` the folders `/var/run` and `/var/lock` will be replaced by symlinks to `/run` and `/run/lock`, respectively. On most systems this is already the case, as `initscripts` create the symlinks on boot. However, these symlinks are not owned by any package, which is what we are fixing with this upgrade. If the symlinks are already in place on your system (which should be the case for most people), then you can simply perform `# pacman -Syu --ignore filesystem && pacman -S filesystem --force` Otherwise, if `/var/run` or `/var/lock` are directories (e.g. if you are using `systemd` and never booted with `initscripts`) you need to delete the directories before performing the update. As these directories are used at runtime, it is recommended to shutdown any background tasks before performing `# rm -rf /var/run /var/lock && pacman -Syu && reboot` Note: In general, it is strongly advised to avoid the `--force` switch as it is not safe. However, in this particular case it is safe, and suggested to avoid having to manually delete the `/var/run` or `/var/lock` symlinks. Lastly, on upgrading `filesystem` users of kernels prior to `linux-3.4` will get a warning about permissions on `/sys`. This is nothing to worry about, as of `linux-3.4` the permissions will be `555`, and this upgrade reflects this in the `filesyste` package. URL: http://www.archlinux.org/news/filesystem-upgrade-manual-intervention-requir…

1 0

[arch-announce] Having pacman verify packages
by Arch Linux: Recent news updates: Gaetan Bisson 04 Jun '12

04 Jun '12

Gaetan Bisson wrote: For the past six months, pacman's package verification features were turned off by default while we were figuring out the details of our public-key infrastructure. They have finally been enabled in pacman-4.0.3-2; when you upgrade, you will be prompted to run: pacman-key --init pacman-key --populate archlinux This sets up a local keyring for pacman, and populates it with the data needed to authenticate official packages. This includes five master keys used to authenticate Arch Linux packagers (developers and trusted users), so you do not need to know who joins or leaves the team: you only have to verify those five master keys once and for all. The populate command will prompt you to do so; please do this cautiously by checking the fingerprints displayed against [those published on our website][1]. Then, merge your `pacman.conf` with `pacman.conf.pacnew`, that is, enable package verification through the SigLevel option, and you should be good to go. For details on the development of pacman and archlinux-keyring, see the blog posts of [Allan][2] and [Pierre][3]. [1]: https://www.archlinux.org/master-keys/ [2]: http://allanmcrae.com/2011/12/pacman-package-signing-4-arch-linux/ [3]: https://pierre-schmitz.com/verify-all-the-packages/ URL: http://www.archlinux.org/news/having-pacman-verify-packages/

1 0