Package Details: ruby-archive-tar-minitar 0.5.2-2

Git Clone URL: https://aur.archlinux.org/ruby-archive-tar-minitar.git (read-only)
Package Base: ruby-archive-tar-minitar
Description: A pure-Ruby library and command-line utility that provides the ability to deal with POSIX tar(1) archive files.
Upstream URL: https://rubygems.org/gems/archive-tar-minitar
Licenses: ruby, GPL2
Submitter: liganic
Maintainer: axil42
Last Packager: axil42
Votes: 48
Popularity: 0.037550
First Submitted: 2011-08-24 17:21
Last Updated: 2015-06-10 06:15

Latest Comments

axil42 commented on 2014-12-13 06:37

@bePolite read the comments below. If you use rvm/rbenv make sure you have switched to system ruby to package it.

Adopted, cleaned up and bumped pkgrel.

bePolite commented on 2014-12-13 05:30

I am having the following error when installing this package

==> Validating source files with md5sums...
archive-tar-minitar-0.5.2.gem ... Passed
==> Extracting sources...
==> Entering fakeroot environment...
==> Starting build()...
ERROR: While executing gem ... (Errno::ENOENT)
No such file or directory @ dir_s_mkdir - /home/xift/Downloads/ruby-archive-tar-minitar/pkg/ruby-archive-tar-minitar/usr/bin
==> ERROR: A failure occurred in build().
Aborting...


webmonarch commented on 2014-03-14 23:03

@cpence thanks for the tip on rbenv/rvm!

Due to the fact that RBENV/RVM is effectively required on any Ruby dev's machine, is it possible to tweak the build scripts to use Arch's ruby explicitly instead of using the PATH...avoiding picking up RBENV/RVM ruby?

cpence commented on 2014-03-12 12:13

If anybody else gets the error mentioned below about /usr/bin not being created automatically by the installation process, then it's likely you're running rbenv or rvm, which is overriding your gem installation paths and creating an Arch package containing references to ~/.rbenv/versions (or wherever your home-directory Rubies are stored). You *do not* want rbenv/rvm to be called while you're making these AUR gem packages, make sure you remove it from your current shell!

amatriain commented on 2014-03-12 10:10

The pakage fails to build for me:

==> Starting build()...
ERROR: While executing gem ... (NoMethodError)
undefined method `full_name' for nil:NilClass
==> ERROR: A failure occurred in build().
Aborting...

masterkorp commented on 2013-12-05 17:09

Yet minitar file conflicts.

Can you rename your bin file to the gem file accordingly ?

masterkorp commented on 2013-12-05 17:09

$ sudo pacman -U ruby-minitar-0.5.4-1-any.pkg.tar.xz
pacman[sudo] password for masterkorp:
loading packages...
resolving dependencies...
looking for inter-conflicts...

Packages (1): ruby-minitar-0.5.4-1

Total Installed Size: 0.18 MiB

:: Proceed with installation? [Y/n]
(1/1) checking keys in keyring [#############################################################################] 100%
(1/1) checking package integrity [#############################################################################] 100%
(1/1) loading package files [#############################################################################] 100%
(1/1) checking for file conflicts [#############################################################################] 100%
error: failed to commit transaction (conflicting files)
ruby-minitar: /usr/bin/minitar exists in filesystem
Errors occurred, no packages were upgraded.

joschi commented on 2013-12-05 17:02

@masterkorp: minitar (https://rubygems.org/gems/minitar) and archive-tar-minitar (https://rubygems.org/gems/archive-tar-minitar) are different Ruby gems.

masterkorp commented on 2013-12-05 16:54

Doesn't this package conflist with ruby-minitar ?????

kidoz commented on 2012-08-08 16:59

Created automatically during installation. Check: through yaourt and manually via makepkg.

All comments