bug#25235: Wrapped python programs get native-inputs in PYTHONPATH

The 'wrap' phase of 'python-build-system' adds native-inputs to PYTHONPATH of the wrapped programs. This causes unnecessary runtime dependencies and may create problems when cross-compiling. Given that all python dependencies are now supposed to be propagated, perhaps we can simply remove the wra

bug#25227: [Website] Package-related pages redesign proposal

Hello! Luis Felipe López Acevedo skribis: > On 2016-12-19 02:35, Alex Sassmannshausen wrote: >> Hi Luis, >> >> Luis Felipe López Acevedo writes: >> >>> Hi, >>> >>> I was thinking on improving the package-related pages, and made these >>> mockups: >>> >>> >>> Figure 1. Package list page. >>> http

bug#25231: Linux-libre 4.9 fails to load modules on i686 (release blocker!)

Mark H Weaver skribis: > l...@gnu.org (Ludovic Courtès) writes: > >> Linux-libre 4.9.0 triggers this problem on i686 (quoting >> ): >> >> loading kernel modules... >> [6.085552] libahci: disagrees about version of symbol mcount >> [6.0859

bug#25227: [Website] Package-related pages redesign proposal

On 2016-12-19 02:35, Alex Sassmannshausen wrote: Hi Luis, Luis Felipe López Acevedo writes: Hi, I was thinking on improving the package-related pages, and made these mockups: Figure 1. Package list page. https://multimedialib.files.wordpress.com/2016/12/guixsd-package-list-view-v0.png Ove

bug#25231: Linux-libre 4.9 fails to load modules on i686 (release blocker!)

l...@gnu.org (Ludovic Courtès) writes: > Linux-libre 4.9.0 triggers this problem on i686 (quoting > ): > > loading kernel modules... > [6.085552] libahci: disagrees about version of symbol mcount > [6.085978] libahci: Unknown symbol mcount

bug#25231: Linux-libre 4.9 fails to load modules on i686 (release blocker!)

Hello! Linux-libre 4.9.0 triggers this problem on i686 (quoting ): --8<---cut here---start->8--- loading kernel modules... [6.085552] libahci: disagrees about version of symbol mcount [6.085978] libahci

bug#25139: making the update procedure more obvious

Hi, Dave Love skribis: > It's not very obvious to a newcomer how to update to a new release as > it's rather buried in the doc. I think it would help to reference > "pull" in the installation section of the manual, and maybe in release > announcements, and to index "upgrading" and/or "upgrades"