- Arch-announce - lists.archlinux.org

[arch-announce] Dropping tcp_wrappers support
by Arch Linux: Recent news updates: Dan McGee 16 Jul '11

16 Jul '11

Dan McGee wrote: `tcp_wrappers` support is being dropped frrom all packages and the package removed from `[core]`. This is due to upstream not having released a new version since April 1997. Additionally, newer daemons and applications are inconsistent in their support for libwrap, leading to confusion as to whether an application supports the library. If you currently use `/etc/hosts.allow` or `/etc/hosts.deny` for security or logging purposes, you will need to adjust accordingly and use another tool such as `iptables`. URL: http://www.archlinux.org/news/dropping-tcp_wrappers-support/

1 0

[arch-announce] Ardour loses LV2 support
by Arch Linux: Recent news updates: Ray Rashif 08 Jul '11

08 Jul '11

Ray Rashif wrote: An incoming update to [ardour][1] will not have support for [LV2][2] plug-ins due to the removal of [slv2][3] from its dependencies. This is a result of an API/ABI incompatibility between the latest releases of the [Redland/Rasqal/Raptor][4] suite that we ship and Ardour's internal supported versions of those libraries, which SLV2 depends on. This is also primarily what caused the [build failures and runtime segmentation fault][5] that you may have experienced. [Upstream will not be updating its codebase][6] as all efforts have shifted to version 3 of the [DAW][7], which will do away with SLV2 altogether (and possibly adopt other implementations of the LV2 standard, if at all). Currently, no-one has submitted a patch to address the issue. Compatibility packages are not possible to provide in this case, and as such, we have decided to drop LV2 support from our Ardour package. Users can still use [LADSPA][8] plug-ins or, which is probably already a popular workflow, resort to [other LV2 hosts][9] with the help of [jack][10] and its routing capabilities. [1]: http://www.archlinux.org/packages/?q=ardour [2]: http://lv2plug.in/trac/ [3]: http://www.archlinux.org/packages/?q=slv2 [4]: http://librdf.org/ [5]: https://bugs.archlinux.org/task/25060 [6]: https://ardour.org/node/4301#comment-25145 [7]: http://en.wikipedia.org/wiki/Digital_audio_workstation [8]: http://www.ladspa.org/ [9]: http://aur.archlinux.org/packages.php?O=0&K=lv2&do_Search=Go&PP=50&SB=v&SO=d [10]: http://www.archlinux.org/packages/?q=jack URL: http://www.archlinux.org/news/ardour-loses-lv2-support/

1 0

[arch-announce] python2-zope-interface update requires user interaction
by Arch Linux: Recent news updates: Ionuț Mircea Bîr u 27 Jun '11

27 Jun '11

Ionuț Mircea Bîru wrote: Due to a bug in pacman file conflict resolution, the upgrade to the package formerly named `zope-interface` requires manual steps. pacman -Rdd zope-interface pacman -Su python2-zope-interface --asdeps URL: http://www.archlinux.org/news/python2-zope-interface-update-requires-user-i…

1 0

[arch-announce] Bug Day: Saturday, June 18
by Arch Linux: Recent news updates: Evangelos Foutras 15 Jun '11

15 Jun '11

Evangelos Foutras wrote: Join the **#archlinux-bugs** channel on Freenode this **Saturday the 18th**, and help us squash some bugs! URL: http://www.archlinux.org/news/bug-day-saturday-june-18/

1 0

[arch-announce] Changes to module blacklisting
by Arch Linux: Recent news updates: Tom Gundersen 08 Jun '11

08 Jun '11

Tom Gundersen wrote: Since the dawn of time we have shipped our homegrown system for blacklisting kernel modules (in various incarnations). This has served us well, but we (or rather our various upstreams) have now reached a point where it is no longer necessary. We have therefore decided to remove all our module blacklisting logic, and rely entirely on the blacklisting provided by `modprobe`. This means a change in syntax, and a minor change in functionality. We hope that the short-term inconvenience will be justified by the long-term gain. Due to an unrelated change in our udev package, we no longer load as many modules as we used to by default, so some problematic modules (such as `pcspkr` and `snd-seq-oss`) might no longer need to be blacklisted. ## The different notions of blacklisting The notion of module blacklisting that we have used is (sadly) slightly different from what is used by modprobe. * our blacklisting: a blacklisted module, or any module that depends on it, will never be loaded automatically by udev, but may be loaded manually. * modprobe's blacklisting: a blacklisted module will not be loaded automatically, but may be loaded if another non-blacklisted module depends on it, or if it is loaded manually. * disabling a module: one can get similar behavior to what we used to provide by forcing a module to always fail loading, it will not be possible to load it manually. ## Boot time blacklisting or disabling Modules can be blacklisted at boot time by appending `modprobe.blacklist=mod1,mod2,mod3` to the kernel command line (in grub, lilo or syslinux). Alternatively, the modules can be disabled altogether by appending `mod1.disable=1 mod2.disable=1 mod3.disable=1` instead. This is useful in an emergency where a broken module makes it impossible to boot your system. ## Persistent blacklisting or disabling Rather than blacklisting modules in `rc.conf`, use modprobe's native configuration files. These can be found in /etc/modprobe.d/, and are documented in `man modprobe.d`. The replacement of `rc.d`'s `MODULES=(!mod1 !mod2 !mod3)` is to add a `.conf` file to `/etc/modprobe.d/` with the contents: blacklist mod1 blacklist mod2 blacklist mod3 Alternatively, to ensure that the modules are never inserted, even if they are needed by other modules you load: install mod1 /bin/false install mod2 /bin/false install mod3 /bin/false URL: http://www.archlinux.org/news/changes-to-module-blacklisting/

1 0

[arch-announce] Deprecation of net-tools
by Arch Linux: Recent news updates: Tom Gundersen 08 Jun '11

08 Jun '11

Tom Gundersen wrote: This April marked the ten year anniversary of the last net-tools release. We decided to look at this as an opportunity to deprecate net-tools and provide alternative, and better maintained, solutions for net-tools functionality. This has a few consequences, but most people should not notice. net-tools will continue to be in the repositories, so scripts relying on it should still work. ## `rc.conf` A new syntax is introduced in `rc.conf` for configuring a simple network setup using `iproute2` rather than `net-tools`. The old functionality is still preserved for those preferring to stay with that, but do not expect it to gain new features. The new syntax is very simplistic and only supports one wired network device (configured statically or by dhcp) and we do not expect to add more features in the future. We want to encourage the use of more advanced network solutions, such as `networkmanager` or our own `netcfg`. ## `domainname` (a.k.a. `nisdomainname`, a.k.a `ypdomainname`) These binaries are now provided by `yp-tools`, rather than by `net-tools`. Furthermore, the domain name is no longer set by initscripts, rather it is dealt with entirely by the ypbind rc script. Before this change the domain name was handled inconsistently, sometimes being read from `/etc/conf.d/nisdomainname`, and sometimes from `/etc/defaultdomain`. >From now on, the domain name is only ever read from `/etc/conf.d/nisdomainname`. ## `hostname` This binary is now provided by `coreutils`, rather than by `net-tools`. URL: http://www.archlinux.org/news/deprecation-of-net-tools/

1 0

[arch-announce] initscripts update
by Arch Linux: Recent news updates: Tom Gundersen 11 May '11

11 May '11

Tom Gundersen wrote: Due to a clash with another package we have moved our newly introduced script from `/sbin/rc` to `/sbin/rc.d`. `rc.d` allows you to start and stop daemons, as well as show the status of the daemons on your system. URL: http://www.archlinux.org/news/initscripts-update-2/

1 0

[arch-announce] initscripts update
by Arch Linux: Recent news updates: Tom Gundersen 02 May '11

02 May '11

Tom Gundersen wrote: New Features: * A new script, `/sbin/rc`, that allows to start/stop and list daemons. * Support FakeRAID (dmraid). * Support btrfs. Functional change: * The adjustment of the hwclock for drift is moved into a daemon that should not be used in most scenarios as it can lead to subtle bugs (especially if using dual-boot or ntp). If you know what you are doing and want to adjust the hardware clock for drift, add `"hwclock"` to your `DAEMONS` array. * We now let udev deal with mdadm, and no longer call mdadm explicitly. This should make things more robust without losing any functionality. Recommendations: * We would like to remind everyone that initscripts expect all other packages (except for the kernel) to be up-to-date. This in particular includes udev, mdadm, dmraid and lvm. * We now strongly discourage the use of `HWCLOCK="localtime"`, as this may lead to several known and unfixable bugs. However, there are no plans to drop support for `"localtime"`. URL: http://www.archlinux.org/news/initscripts-update-1/

1 0

[arch-announce] GNOME3 in [extra]
by Arch Linux: Recent news updates: Ionuț Mircea Bîr u 30 Apr '11

30 Apr '11

Ionuț Mircea Bîru wrote: GNOME 3.0.1 is being moved in [extra] This is a major update and you should take note of a couple of things: * GNOME3 is replacing GNOME2 * GNOME3 has two modes, "standard" mode (gnome-shell) and "fallback" mode (gnome-panel + metacity) * Some packages, like applets using Bonobo, will be dropped in the next few days. A list will be available at [https://wiki.archlinux.org/index.php/GNOME_3/Packages_dropped][1] * pulseaudio is now required to run the GNOME desktop Update and installation instructions are available at [https://wiki.archlinux.org/index.php/GNOME_3][2] Only bugs related to packaging should be reported to [http://bugs.archlinux.org/][3] Crashes and feature requests should be reported to [https://bugzilla.gnome.org/][4] [1]: https://wiki.archlinux.org/index.php/GNOME_3/Packages_dropped [2]: https://wiki.archlinux.org/index.php/GNOME_3 [3]: http://bugs.archlinux.org/ [4]: https://bugzilla.gnome.org/ URL: http://www.archlinux.org/news/gnome3-in-extra/

1 0

[arch-announce] nvidia-173xx and nvidia-96xx removed from [extra]
by Arch Linux: Recent news updates: Gaetan Bisson 15 Apr '11

15 Apr '11

Gaetan Bisson wrote: The nvidia-173xx and nvidia-96xx driver packages have been removed from our repositories as they are incompatible with newer xorg servers. This can only be fixed by an upstream update, which has not happened yet. For most video cards, the best alternative should be xf86-video-nouveau; see: [https://wiki.archlinux.org/index.php/Nouveau][1] As lower-grade options, you might also consider xf86-video-nv and xf86-video- vesa: simply remove the old nvidia driver(s), install these, and the xorg server will automatically pick the best at startup. [1]: https://wiki.archlinux.org/index.php/Nouveau URL: http://www.archlinux.org/news/nvidia-173xx-and-nvidia-96xx-removed-from-ext…

1 0