Re: [Kolab-devel] roundcubemail-plugin-libkolab-skin-larry missing

"Carpenter, Troy" <[email protected]>
Newsgroups gmane.comp.kde.devel.kolab
Message-ID <[email protected]>
On 2015-10-27 5:07 am, Timotheus Pokorra wrote:
> Hello Thomas,
> 
>> There are still files missing:
>> %files -n roundcubemail-plugin-libkolab-skin-larry -f 
>> plugin-libkolab-skin-
>> larry.files
>> %files -n roundcubemail-plugin-libkolab-skin-larry -f 
>> plugin-libkolab-skin-
>> larry.files
>> %files -n roundcubemail-plugin-kolab_activesync-skin-larry-assets -f 
>> plugin-
>> kolab_activesync-skin-larry-assets.files
> 
> I had a look into this.
> 
> For libkolab, there is only the file libkolab.css in
> https://cgit.kolab.org/roundcubemail-plugins-kolab/tree/plugins/libkolab/skins/larry,
> and that is delivered in the package
> roundcubemail-plugin-libkolab-skin-larry-assets
> 
> rpm -ql roundcubemail-plugin-libkolab-skin-larry-assets
> shows:
> /usr/share/roundcubemail/public_html/assets/plugins/libkolab/skins
> /usr/share/roundcubemail/public_html/assets/plugins/libkolab/skins/larry
> /usr/share/roundcubemail/public_html/assets/plugins/libkolab/skins/larry/libkolab.css
> 
> As you wrote in a private email, spec files without contained files
> "[...] prevents the packages from building with new rpm-4.13.0-RC1".
> Are there any release notes documenting this breaking change?
> Or is it a bug in the release candiate and will be fixed for the final
> release of rpm 4.13?
> I checked http://www.rpm.org/wiki/Releases/4.13.0
> 
> Since there are no other files, we probably can drop the package
> roundcubemail-plugin-libkolab-skin-larry from the spec file.
> I have committed this now to Kolab Development.
> 
> I checked the other package as well:
> rpm -ql roundcubemail-plugin-kolab_activesync-skin-larry-assets
> shows:
> /usr/share/roundcubemail/public_html/assets/plugins/kolab_activesync/skins
> /usr/share/roundcubemail/public_html/assets/plugins/kolab_activesync/skins/larry
> /usr/share/roundcubemail/public_html/assets/plugins/kolab_activesync/skins/larry/alarm-clock.png
> /usr/share/roundcubemail/public_html/assets/plugins/kolab_activesync/skins/larry/config.css
> /usr/share/roundcubemail/public_html/assets/plugins/kolab_activesync/skins/larry/foldertypes.png
> /usr/share/roundcubemail/public_html/assets/plugins/kolab_activesync/skins/larry/pointer-left.png
> /usr/share/roundcubemail/public_html/assets/plugins/kolab_activesync/skins/larry/synchronize.png
> 
> So we should keep that package.
> 
> Timotheus


I don't know if this is related to a change you made, but now I'm 
getting this in the Centos 7 Development repository:

Started getting this error this morning on my Centos 7 using the 3.5 
Development repository.


--> Finished Dependency Resolution
Error: Package: 
roundcubemail-plugin-libkolab-skin-larry-3.3-28.1.el7.kolab_3.5.noarch 
(@Kolab_Development)
            Requires: roundcubemail(plugin-libkolab) = 
3.3-28.1.el7.kolab_3.5
            Removing: 
roundcubemail-plugin-libkolab-3.3-28.1.el7.kolab_3.5.noarch 
(@Kolab_Development)
                roundcubemail(plugin-libkolab) = 3.3-28.1.el7.kolab_3.5
            Updated By: 
roundcubemail-plugin-libkolab-3.3-34.1.el7.kolab_3.5.noarch 
(Kolab_Development)
                roundcubemail(plugin-libkolab) = 3.3-34.1.el7.kolab_3.5
Error: Package: 
roundcubemail-plugin-libkolab-skin-larry-3.3-28.1.el7.kolab_3.5.noarch 
(@Kolab_Development)
            Requires: roundcubemail(plugin-libkolab-skin-larry-assets) = 
3.3-28.1.el7.kolab_3.5
            Removing: 
roundcubemail-plugin-libkolab-skin-larry-assets-3.3-28.1.el7.kolab_3.5.noarch 
(@Kolab_Development)
                roundcubemail(plugin-libkolab-skin-larry-assets) = 
3.3-28.1.el7.kolab_3.5
            Updated By: 
roundcubemail-plugin-libkolab-skin-larry-assets-3.3-34.1.el7.kolab_3.5.noarch 
(Kolab_Development)
                roundcubemail(plugin-libkolab-skin-larry-assets) = 
3.3-34.1.el7.kolab_3.5

Do I need to delete something as a result of the change you made?
lmpx.com only provides a reader for public news (NNTP) servers. It is not affiliated with the servers or forums shown here and is not responsible for the content of articles, which is written by their respective authors.