i'm not sure, if you look at the worker log from an affected build eg.:
http://file-store.rosalinux.ru/api/v1/file_stores/1cc1dea0cce8f49217df21522e9a8505ee22d35d.log?show=true
you see a lot of scriplets failing during the chroot installation.
one thing is for sure we need to resolve this asap before something
important gets published with this bug as it renders the rpm uninstallable.
cheers
cris.
On 21/10/14 09:48, Tomasz Gajc wrote:
For me this sounds like this is related to rpm patch that wipes out epoch.
2014-10-20 16:37 GMT+02:00 Crispin Boylan <[email protected]
<mailto:[email protected]>>:
following rpms have been built like this, all today only:
-rw-r--r-- 278270 2014-10-20 13:56
baloo-4.14.2-1-omv.x86_64.rpm
-rw-r--r-- 73110 2014-10-20 13:32
kfilemetadata-4.14.2-1-omv.x86_64.rpm
-rw-r--r-- 19266 2014-10-20 13:56
lib64baloo-devel-4.14.2-1-omv.x86_64.rpm
-rw-r--r-- 10010 2014-10-20 14:16
lib64baloo-widgets-devel-4.14.2-1-omv.x86_64.rpm
-rw-r--r-- 29934 2014-10-20 13:56
lib64baloocore4-4.14.2-1-omv.x86_64.rpm
-rw-r--r-- 48146 2014-10-20 13:56
lib64baloofiles4-4.14.2-1-omv.x86_64.rpm
-rw-r--r-- 28642 2014-10-20 13:56
lib64baloopim4-4.14.2-1-omv.x86_64.rpm
-rw-r--r-- 38610 2014-10-20 13:56
lib64balooqueryparser4-4.14.2-1-omv.x86_64.rpm
-rw-r--r-- 69722 2014-10-20 14:16
lib64baloowidgets4-4.14.2-1-omv.x86_64.rpm
-rw-r--r-- 28806 2014-10-20 13:56
lib64balooxapian4-4.14.2-1-omv.x86_64.rpm
-rw-r--r-- 11430 2014-10-20 13:32
lib64kfilemetadata-devel-4.14.2-1-omv.x86_64.rpm
-rw-r--r-- 24182 2014-10-20 13:32
lib64kfilemetadata4-4.14.2-1-omv.x86_64.rpm
-rw-r--r-- 8718 2014-10-20 11:28
lib64pyglib2.0_0-2.28.6-11-omv.x86_64.rpm
-rw-r--r-- 9678 2014-10-20 13:43
lib64spice-server-devel-0.12.5-2-omv.x86_64.rpm
-rw-r--r-- 274370 2014-10-20 13:43
lib64spice-server1-0.12.5-2-omv.x86_64.rpm
-rw-r--r-- 156170 2014-10-20 11:28
python-gobject-2.28.6-11-omv.x86_64.rpm
-rw-r--r-- 327214 2014-10-20 11:28
python-gobject-devel-2.28.6-11-omv.x86_64.rpm
-rw-r--r-- 308290 2014-10-20 13:43
spice-server-client-0.12.5-2-omv.x86_64.rpm
no i586 ones are affected, only x86_64
On 20/10/14 15:29, Crispin Boylan wrote:
Hi
looks like something is causing distro-release-common to fail
to install during chroot generation.
This means /etc/release doesnt exist so distepoch gets empty, eg:
https://abf.rosalinux.ru/build_lists/2316492
https://abf.rosalinux.ru/build_lists/2316496
anyone know how this is happening?!
thanks
cris.
_______________________________________________
ABF-users mailing list
[email protected] <mailto:[email protected]>
http://lists.rosalab.ru/mailman/listinfo/abf-users
_______________________________________________
OM-Cooker mailing list
[email protected] <mailto:[email protected]>
http://ml.openmandriva.org/listinfo.cgi/om-cooker-openmandriva.org
_______________________________________________
OM-Cooker mailing list
[email protected]
http://ml.openmandriva.org/listinfo.cgi/om-cooker-openmandriva.org
_______________________________________________
OM-Cooker mailing list
[email protected]
http://ml.openmandriva.org/listinfo.cgi/om-cooker-openmandriva.org
