We have moved to a new Sailfish OS Forum. Please start new discussions there.
![]() | 1 | initial version | posted 2015-01-20 13:45:45 +0300 |
When building sailfish applications on mer OBS, it generates RPM filenames that have text jolla in them between release and architecture
These were accepted still during week starting 13th Jan 2015, but not anymore.
e.g. harbour-chargemon-0.3.2-10.7.1.jolla.armv7hl.rpm
now gets rejected (week ago similar was approved)
I would like to build my apps on mer OBS and publish them "as is" without renaming the filename.
I have studied the biary guidelines, and they clearly say that this is not allowed naming:
But still this s**ks.
I'm just interested what are the reasons behind for restrict naming of packages like this? and specially why it has been now changed to reject them automatically?
Also is there a way to configure mer OBS so that it does not add jolla in the RPM filename?
Or is it just me being stupid and not getting it?
When building sailfish applications on mer OBS, it generates RPM filenames that have text jolla in them between release and architecture
These were accepted still during week starting 13th Jan 2015, but not anymore.
e.g. harbour-chargemon-0.3.2-10.7.1.jolla.armv7hl.rpm
now gets rejected (week ago similar was approved)
I would like to build my apps on mer OBS and publish them "as is" without renaming the filename.
I have studied the biary guidelines, and they clearly say that this is not allowed naming:
But still this s**ks.
I'm just interested what are the reasons behind for restrict naming of packages like this? and specially why it has been now changed to reject them automatically?
Also is there a way to configure mer OBS so that it does not add jolla in the RPM filename?
Or is it just me being stupid and not getting it?