On September 15, 2015 8:42:02 AM EDT, Jan Engelhardt <jengelh@inai.de> wrote:
On Tuesday 2015-09-15 14:17, greg.freemyer@gmail.com wrote:
For the 32-bit proponents with package maintenance skills there are 4 packages currently failing for 32-bit builds, but not 64-bit builds.
giflib
The 32-bit volunteers need to figure out if they can branch, patch, and submit fixes to the above. Or encourage (work with) the main maintainer to do so.
The OBS maintainers need to figure out if they can branch, patch, and submit fixes, because apparently this is an OBS bug (possibly in bs_worker) rather than a compile failure of the software itself:
14:39 ares40:~/obs/zu > cd openSUSE/Leap/42.1/giflib/ 14:39 ares40:../42.1/giflib > sosc bl standard i586 unexpected EOF
Interestingly I branched all 4 failures. 3 of them built fine for 32-bit, so the build errors appear to be transient (or build server specific). https://build.opensuse.org/project/monitor/home:gregfreemyer:branches:openSUSE:Leap:42.1?arch_i586=1&defaults=0&repo_standard=1&succeeded=1 So it appears the first 'power' the 32-bit team needs is the ability to trigger a rebuild. Due to the potential to cause a cascade of rebuilds, I realize that is not a trivial power. How should it be done for now? Send an email to a key Leap distro maintainer? If one is reading, the 4 packages in my initial email should be given a kick to try and rebuild as 32-bit successfully: apache2-mod_perl giflib ksh perl-Devel-Cover Greg -- Sent from my Android device with K-9 Mail. Please excuse my brevity. -- To unsubscribe, e-mail: opensuse-factory+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse-factory+owner@opensuse.org