Il 13/07/2014 14:52, Tomasz Paweł Gajc ha scritto:
Can you please post some examples of such two rpm files with different
distepoch ?
After this logs I've start to search what to blame on :
http://file-store.rosalinux.ru/api/v1/file_stores/a234bb3782b8236b285c9aae295d8cc94b8c40e0.log?show=true
http://file-store.rosalinux.ru/api/v1/file_stores/71c82bc594bd068de3972eeb03247f4307944137.log?show=true
#
Few doubled packages that I've came across during the builds :
http://abf-downloads.rosalinux.ru/cooker/repository/i586/main/release/chkconfig-1.3.60-4-omv2014.0.i586.rpm
http://abf-downloads.rosalinux.ru/cooker/repository/i586/main/release/chkconfig-1.3.60-8-omv2014.1.i586.rpm
-(republished by me)
#
http://abf-downloads.rosalinux.ru/cooker/repository/i586/main/release/desktop-file-utils-0.22-2-omv2014.0.i586.rpm
http://abf-downloads.rosalinux.ru/cooker/repository/i586/main/release/desktop-file-utils-0.22-6-omv2014.1.i586.rpm
#
http://abf-downloads.rosalinux.ru/cooker/repository/i586/main/release/drakconf-12.19.2-12-omv2013.0.noarch.rpm
http://abf-downloads.rosalinux.ru/cooker/repository/i586/main/release/drakconf-12.19.4-2-omv2014.1.noarch.rpm
#
http://abf-downloads.rosalinux.ru/cooker/repository/i586/main/release/libusb1.0_0-1.0.16-3-omv2014.0.i586.rpm
http://abf-downloads.rosalinux.ru/cooker/repository/i586/main/release/libusb1.0_0-1.0.18-2-omv2014.1.i586.rpm
#
-wayland libs start with 2013.0 and ends with 2015.0
-all webkit is 2015.0 distepoched
-all localles-%lang are a 2014.1&&2015.0 compilation ..
#
I mean we have from 2013.0 distepoch till 2015.0
in the same main repo...
( just some examples i don't really search all the main media...)
Just to be sure , did i mentin that all this confusion is in
MAIN-release media ? How much did we have until the next stable spin?
Now of course that I'm overreacting , (as you already told me) , just to
be clear , I'm confronting main with
other main , in my case the main that i know best is rosa, of course i
won't confront oma's main with LTS
(because then will be a repo bloodbath), but with rosa2014.1, I guess
oma2014.1 is a devel as rosa2014.1 , this being said just take the
repoclosure for a tour ...
I say let's hold our horses and clean as much as possible the main, and
barricade ABF with unidirectional rsync ,
if we have a perfect starting point for rsync all corrupted or missing
pkgs. will be fixed after the next rsync across the mirros,
ounce we have a sane env. to build on we could start to plan releases...
But I know , just because it was me who said it, nobody will agree, IMO
better loose a scheduled release
in order to have a sane base to build on for later run ...
Ps.
I'm using only distepoch here, in order to point one or another release,
because I lost tracks about the official
releases names.
--
Greetings
___________________
MRB ain't no shit
Rosalinux.Ro
Mandrivausers.Ro
________________
Talk is cheap, show me the code.
