Am 01.06.2013 08:00, schrieb Allan McRae:

On 01/06/13 15:51, Allan McRae wrote:

...

New thread for ongoing updates to instructions as issues are noticed:

Updates fix: - post_install scripts can call scripts with /bin/bash shebangs (e.g. mkinitcpio). - pamcan -Qm sorting is not consistent with that from "sort" in some locales - autofs and non-mounted partitions

Further update... mention non-official repos

--- Update Instructions ---

1) Fix any non-official packages with files in /bin, /sbin or /usr/sbin to put those files in /usr/bin. The list of packages that are not in a repo that need to be fixed can be generated using: $ comm -12 <(pacman -Qqm | sort) <(pacman -Qqo /bin /sbin /usr/sbin | sort -u)

Also check packages installed from non-official repos using: $ paclist <repo> | awk ' { print $1 } ' | pacman -Ql - | grep ' /s\?bin/\| /usr/sbin/'

2) Make sure any packages in IgnorePkg or IgnoreGroup do not have files in /bin, /sbin, or /usr/sbin. Fix them if necessary.

3) If you have files in /bin, /sbin or /usr/sbin that are unowned by any package, you need to move them. Find a list using: $ find /bin /sbin /usr/sbin -exec pacman -Qo -- {} + >/dev/null

4) Ensure all partitions are mounted if using autofs. They may not automount when needed later in this update.

5) Update your system: # pacman -Syu --ignore filesystem,bash

We should mention that at this point, the user will not be able to log in via ssh or virtual console. It is best to have a second terminal open just in case.

# pacman -S bash # pacman -Su

I think for the final announcement, we should also add a sentence explaining the conflicts: "The update merges all binaries into a unified /usr/bin directory. This step removes a distinction that has been meaningless for Arch systems and simplifies package maintenance for the development team." Something like that.

Am 02.06.2013 02:35, schrieb Allan McRae:

On 01/06/13 19:55, Thomas Bächler wrote:

...

We should mention that at this point, the user will not be able to log in via ssh or virtual console. It is best to have a second terminal open just in case.

Just for my clarification, what is wrong with the terminal that you are doing the update in that requires a second terminal?

No idea, but I wished for a second terminal when pacman hung and I wasn't sure why.

And the news draft: --- Begin --- Binaries move to /usr/bin requiring update intervention During your next update, you will get a error message like: error: failed to commit transaction (conflicting files) filesystem: /bin exists in filesystem The update merges all binaries into a unified /usr/bin directory. This step removes a distinction that has been meaningless for Arch systems and simplifies package maintenance for the development team. The following instructions will ensure a safe update: 1) Fix any non-official packages with files in /bin, /sbin or /usr/sbin to put those files in /usr/bin. The list of packages that are not in a repo that need to be fixed can be generated using: $ pacman -Qqo /bin /sbin /usr/sbin | pacman -Qm - Also check packages installed from non-official repos using: $ paclist <repo> | awk ' { print $1 } ' | pacman -Ql - | \ grep ' /s\?bin/\| /usr/sbin/' 2) Make sure any packages in IgnorePkg or IgnoreGroup do not have files in /bin, /sbin, or /usr/sbin. Fix them if necessary. 3) If you have files in /bin, /sbin or /usr/sbin that are unowned by any package, you need to move them. Find a list using: $ find /bin /sbin /usr/sbin -exec pacman -Qo -- {} + >/dev/null 4) Ensure all partitions are mounted if using autofs. They may not automount when needed later in this update. 5) Update your system. Before performing this update, you may want to ensure you have a second terminal open with root privileges in the unlikely event of an emergency, particularly if updating over ssh. # pacman -Syu --ignore filesystem,bash # pacman -S bash # pacman -Su --- End ---

Am 03.06.2013 09:41, schrieb Tom Gundersen:

On Mon, Jun 3, 2013 at 5:05 AM, Allan McRae wrote:

...

And the news draft:

Looks good to me. Time to make the move?

Fine with me. Maybe we could also explain more about the reasons or just link to you mail here: https://mailman.archlinux.org/pipermail/arch-dev-public/2012-March/022625.ht... Greetings, Pierre -- Pierre Schmitz, https://pierre-schmitz.com