Mailinglist Archive: opensuse-ruby (24 mails)

< Previous Next >
Re: [opensuse-ruby] %gem_install leads to multiple binaries in /usr/bin/
  • From: Adam Spiers <aspiers@xxxxxxxx>
  • Date: Thu, 28 May 2015 15:26:57 +0100
  • Message-id: <20150528142657.GO13247@pacific.linksys.moosehall>
Robert Munteanu <robert.munteanu@xxxxxxxxx> wrote:
On Tue, May 19, 2015 at 12:45 PM, Robert Munteanu
<robert.munteanu@xxxxxxxxx> wrote:
On Tue, May 19, 2015 at 12:51 AM, Adam Spiers <aspiers@xxxxxxxx> wrote:
Robert Munteanu <robert.munteanu@xxxxxxxxx> wrote:
vagrant is no longer distributed as a gem as of 1.5.0 -
https://rubygems.org/gems/vagrant . This means that I can't use
gem2rpm ( to my knowledge ) as I'm already in the build process when
the gem is available.

Thinking out loud, is it acceptable to change the update process from:

- download tarball; update spec file; osc build

Actually that's not the current process for that gem; it's

- update revision param in _service file; run osc service dr;
update spec file; osc build


I tried to refresh the _service file but this failed.

$ osc diff _service

Index: _service
===================================================================
--- _service (revision 57ae2e4a605654c4d32c5562f5d64c92)
+++ _service (working copy)
@@ -1,6 +1,6 @@
<services>
<service name="tar_scm" mode="disabled">
- <param name="url">git://github.com/mitchellh/vagrant.git</param>
+ <param name="url">https://github.com/mitchellh/vagrant.git</param>
<param name="scm">git</param>

<param name="package-meta">yes</param>
@@ -8,8 +8,8 @@
<param name="exclude">.gitreview</param>

<param name="filename">vagrant</param>
- <param name="version">1.6.5</param>
- <param name="revision">v1.6.5</param>
+ <param name="version">1.7.2</param>
+ <param name="revision">v1.7.2</param>
<param name="changesgenerate">enable</param>
</service>

$ osc service dr

Cloning into '/tmp/tmpqi99Pl/tmpu6TVeW/vagrant'...
ERROR(1): ''
HEAD is now at 1cd667b Update CHANGELOG
Cleaning: /tmp/tmpqi99Pl/tmpu6TVeW /tmp/tmpqi99Pl/vagrant-1.7.2
Identical target file vagrant-1.7.2.tar.bz2 already exists, skipping..
quilt setup failed:
### md5sum: .........b.
### rpmbuild: pppp
ln: failed to create symbolic link 'vagrant-1.7.2/patches': No such file or
directory
/usr/share/quilt/setup: line 490: cd: vagrant-1.7.2: No such file or directory
/usr/share/quilt/setup: line 501: vagrant-1.7.2/series: No such file or
directory
/usr/share/quilt/setup: line 504: vagrant-1.7.2/series: No such file or
directory
ln: failed to create symbolic link 'vagrant-1.7.2/patches': No such file or
directory
/usr/share/quilt/setup: line 490: cd: vagrant-1.7.2: No such file or directory
/usr/share/quilt/setup: line 501: vagrant-1.7.2/series: No such file or
directory
/usr/share/quilt/setup: line 504: vagrant-1.7.2/series: No such file or
directory
ln: failed to create symbolic link 'vagrant-1.7.2/patches': No such file or
directory
/usr/share/quilt/setup: line 490: cd: vagrant-1.7.2: No such file or directory
/usr/share/quilt/setup: line 501: vagrant-1.7.2/series: No such file or
directory
/usr/share/quilt/setup: line 504: vagrant-1.7.2/series: No such file or
directory
ln: failed to create symbolic link 'vagrant-1.7.2/patches': No such file or
directory
/usr/share/quilt/setup: line 490: cd: vagrant-1.7.2: No such file or directory
/usr/share/quilt/setup: line 501: vagrant-1.7.2/series: No such file or
directory
/usr/share/quilt/setup: line 504: vagrant-1.7.2/series: No such file or
directory

Aborting: service call failed: /usr/lib/obs/service/refresh_patches
--changesgenerate enable --outdir /tmp/tmpm3uvnE

What am I doing wrong?

Probably nothing, but I'm puzzled why you get that error. Clearly
it's related to the refresh_patches source service. I don't think I
added that service in, but presumably it's there to keep the existing
patches up to date. If I comment that out then it works fine, but
that's probably not ideal. If I leave it in and simply change the
version to 1.7.2, I get a different error:

--------- 8< --------- 8< --------- 8< --------- 8< --------- 8< ---------
$ osc service dr
Cloning into '/tmp/tmpVkT402/tmpaXFdjk/vagrant'...
ERROR(1): ''
HEAD is now at 1cd667b Update CHANGELOG
Cleaning: /tmp/tmpVkT402/tmpaXFdjk /tmp/tmpVkT402/vagrant-1.7.2
Compressed vagrant-1.7.2.tar to vagrant-1.7.2.tar.bz2
quilt setup rubygem-vagrant.spec failed:
[md5sum <
/home/adam/SUSE/OBS/devel/languages/ruby/extensions/rubygem-vagrant//0001-remove-windows-dependencies.patch
md5sum <
/home/adam/SUSE/OBS/devel/languages/ruby/extensions/rubygem-vagrant//0002-remove-general-installer-notice.pat
ch
md5sum <
/home/adam/SUSE/OBS/devel/languages/ruby/extensions/rubygem-vagrant//_link
md5sum <
/home/adam/SUSE/OBS/devel/languages/ruby/extensions/rubygem-vagrant//_service
md5sum <
/home/adam/SUSE/OBS/devel/languages/ruby/extensions/rubygem-vagrant//_servicedata
md5sum <
/home/adam/SUSE/OBS/devel/languages/ruby/extensions/rubygem-vagrant//rubygem-vagrant-rpmlintrc
md5sum <
/home/adam/SUSE/OBS/devel/languages/ruby/extensions/rubygem-vagrant//vagrant-1.7.2.tar.bz2
bzip2 -cd
/home/adam/SUSE/OBS/devel/languages/ruby/extensions/rubygem-vagrant//vagrant-1.7.2.tar.bz2
| md5sum
md5sum <
/home/adam/SUSE/OBS/devel/languages/ruby/extensions/rubygem-vagrant//vagrant.sh
error: line 29: Dependency tokens must begin with alpha-numeric, '_' or '/':
BuildRequires: %{ruby >= 1.9.3}







The %prep section of rubygem-vagrant.spec failed; results may be incomplete
]
Aborting: service call failed: /usr/lib/obs/service/refresh_patches
--changesgenerate 'enable' --outdir /tmp/tmpOiXsuN
--------- 8< --------- 8< --------- 8< --------- 8< --------- 8< ---------

Unfortunately I don't have any more time to look at this right now.
--
To unsubscribe, e-mail: opensuse-ruby+unsubscribe@xxxxxxxxxxxx
To contact the owner, e-mail: opensuse-ruby+owner@xxxxxxxxxxxx

< Previous Next >
List Navigation