.deb's produce "corrupt builds" when building on an openSUSE system, and installing on a debian one.

[zackp30]

Command: fpm -s gem -t deb --verbose fpm

Output:

Trying to download {:gem=>"fpm", :version=>nil, :level=>:info}
Downloaded fpm-1.1.0 {:level=>:info}
Using gem file {:path=>"/tmp/package-gem-build20140714-4714-1qz16qs/fpm/fpm-1.1.0.gem", :level=>:info}
Successfully installed fpm-1.1.0 {:level=>:info}
1 gem installed {:level=>:info}
Setting from flags: epoch= {:level=>:info}
Setting from flags: iteration= {:level=>:info}
Converting gem to deb {:level=>:info}
No deb_installed_size set, calculating now. {:level=>:info}
Reading template {:path=>"/home/zack/.rvm/gems/ruby-2.1.2/gems/fpm-1.1.0/templates/deb.erb", :level=>:info}
Creating {:path=>"/tmp/package-deb-build20140714-4714-1pkdm08/control.tar.gz", :from=>"/tmp/package-deb-build20140714-4714-1pkdm08/control", :level=>:info}
Created package {:path=>"rubygem-fpm_1.1.0_all.deb"}

Installing using dpkg -i rubygems-fpm_1.1.0_all.deb:

(Reading database ... 446435 files and directories currently installed.)
Preparing to replace rubygem-fpm 1.1.0 (using rubygem-fpm_1.1.0_all.deb) ...
Unpacking replacement rubygem-fpm ...
dpkg: error processing rubygem-fpm_1.1.0_all.deb (--install):
 corrupted filesystem tarfile - corrupted package archive
dpkg-deb: error: subprocess paste was killed by signal (Broken pipe)
Errors were encountered while processing:
 rubygem-fpm_1.1.0_all.deb

However, .deb's created on Ubuntu systems do work.

I would prefer to keep using openSUSE for all my build systems.

Thanks!

[djha-skin]

Funny thing is, I believe I've made debs on red hat/cent machines and they've worked fine.

[zackp30]

Yes, I'm rather perplexed as well...

[jordansissel]

Hmm.. Is there any chance you can upload your corrupt .deb file somewhere I can download it?

[zackp30]

@jordansissel http://assets.apertron.net/rubygem-fpm_1.1.0_all.deb

[jordansissel]

@zackp30 thanks!

I can confirm that dpkg -i ... reports your same error. dpkg -c ... shows me the filesystem contents of the package, though. Odd.

[jordansissel]

lintian doesn't complain, either.

[jordansissel]

This works, too:

dpkg-deb -x ~/rubygem-fpm_1.1.0_all.deb /tmp/z

[jordansissel]

I had a look at dpkg's source code and it's not entirely obvious what is causing the failure. I'll have to build a custom version with extra debugging to figure out what's going on.

[Rush]

I just encountered the same problem. I am using openSUSE for development. Any ideas? Did you have any success @jordansissel

[jordansissel]

@Rush thank you so much for confirming this.

I'll see about setting up an openSUSE vm so I can reproduce this.

[diegopdomingos]

I had similar issues with SuSe. The solution for me was set --format=gnu instead --format=posix in tar compression

[Takios]

Sorry to dig up an old bug report but this is still an issue for me. How do I apply the workaround proposed by @diegopdomingos ? How can I tell fpm to use --format=gnu when using tar compression?

[vibhutisawant]

@diegopdomingos @jordansissel I am facing same issue on OpenSUSE, fpm version used is 1.11.0.
As @Takios mentioned , I am unable to use --format=gnu in tar compression. Any pointers would be of great help. Thanks

[vibhutisawant]

Above issue can be resolved on SLES distro by using dpkg-deb -c to unpack the tar instead of using dpkg -i.