Hello Maintainers,
It looks that the problem has been fixed with the current "gem2deb"
package (release 0.7.5, Bug: #743671).
I have rebuilt this package with the new gem2deb for my own and the
mkmf.log file is gone.
I my eyes there is only a "Binary-only" rebuild with the new gem2deb needed.
But
Package: ruby-bcrypt
Followup-For: Bug #743664
Confirmed.
-- System Information:
Debian Release: jessie/sid
APT prefers testing
APT policy: (990, 'testing'), (500, 'unstable'), (500, 'stable'), (500,
'oldstable')
Architecture: amd64 (x86_64)
Foreign Architectures: i386
Kernel: Linux 3.12-1
brian m. carlson (2014-04-04):
> It looks like you need to sort out which package should own this file.
> From what I can see of the contents, it looks like the answer is
> probably "none of them", as it appears to be a build log which should
> not be included in the package.
Disclaimer: I know N
Package: ruby-atomic,ruby-bcrypt,ruby-curb,ruby-nokogiri
Severity: serious
dpkg says:
Preparing to unpack .../ruby-bcrypt_3.1.7-2_amd64.deb ...
Unpacking ruby-bcrypt (3.1.7-2) over (3.1.7-1) ...
dpkg: error processing archive
/var/cache/apt/archives/ruby-bcrypt_3.1.7-2_amd64.deb (--unpack)
4 matches
Mail list logo
