Pacman-dev

Download

pacman-dev@lists.archlinux.org

May 2017

17 participants
22 discussions

[pacman-dev] pacman sorting incompatible with 'sort' command
by Adesh Kumar 05 May '17

05 May '17

pacman internal sorting on package names differ from the one implemented in linux 'sort' command. pacman treats '-' (hyphen) differently. Testcase: 1. Install i3 group. It will install i3-wm, i3lock and i3status 2. Check the following commands: --($:~)-- pacman -Qeq | grep i3 i3-wm i3lock i3status --($:~)-- pacman -Qeq | grep i3 | sort i3lock i3status i3-wm --($:~)-- pacman -Qeq | grep i3 | sort -c sort: -:2: disorder: i3lock

5 4

Re: [pacman-dev] [PATCH 3/4] makepkg: unify source file times for improved build reproducibility
by Allan McRae 02 May '17

02 May '17

On 21/04/17 13:36, Eli Schwartz wrote: > On 04/20/2017 11:01 PM, Allan McRae wrote: >> I am probably moving this to after source extraction/prepare() running, >> so it can be skipped with --noextract. > > But --noextract depends on your having at some point previously run > --nobuild, in order to pull updated sources, re-patch any patches, etc. > which I still don't want to do manually outside of makepkg... I don't > see why makepkg should start breaking things for me. > > How about instead we guard it with > BUILDENV+=(fix_everyone_elses_SOURCE_DATE_EPOCH_stuff) > > Or better yet, just file bugs against whatever upstream build > system/programming language/source code is determined to sneakily embed > source code modification times into generated files, and call it a day? > Adding list back - any further off-list replies will be completely ignored. The reproducible builds people will provide details, but it appears pyo/pyc do this. A

3 3