Re: [Rpm-maint] [rpm-software-management/rpm] rpm2cpio and rpm2archive: don't write archive data to a terminal. (#116)

2017-01-05 Thread ニール・ゴンパ
Conan-Kudo approved this pull request. Looks fantastic to me! -- You are receiving this because you are subscribed to this thread. Reply to this email directly or view it on GitHub:

[Rpm-maint] [rpm-software-management/rpm] Support pbzip command for multicore environment (#117)

2017-01-05 Thread Geunsik Lim
This commit is to support pbzip2 command for parallel (de) compression with 'rpmbuild' command. The pbzip2 is compatible with the existing bzip2. * Todo: The next step is adding pbzip2 content in .po files. Signed-off-by: Geunsik Lim You can view, comment on, or merge

[Rpm-maint] [rpm-software-management/rpm] rpm2cpio and rpm2archive: don't write archive data to a terminal. (#116)

2017-01-05 Thread Peter Jones
rpm2cpio and rpm2archive happily write binary data to the output terminal. This happens, for example, when I'm typing a command such as "rpm2cpio foo.rpm | less" and I make a typo, hitting instead of the pipe key. This often results in hilarious (if bewildering) font and character encoding

Re: [Rpm-maint] [PATCH] Unbreak short-circuited binary builds

2017-01-05 Thread Mark Wielaard
On Thu, Jan 05, 2017 at 03:40:42PM +0200, Panu Matilainen wrote: > > > When checking for pre-existing links see if they already point to > > > the right file and in that case just reuse it instead of creating new > > > ones. > > > > > @@ -1572,6 +1573,16 @@ static int addNewIDSymlink(FileList

Re: [Rpm-maint] [PATCH] Unbreak short-circuited binary builds

2017-01-05 Thread Panu Matilainen
On 01/05/2017 02:50 PM, Mark Wielaard wrote: On Thu, Jan 05, 2017 at 01:47:28PM +0200, Panu Matilainen wrote: Commit bbfe1f86b2e4b5c0bd499d9f3dd9de9c9c20fff2 broke short-circuited binary builds (which can be handy for testing when working on large packages), eg: rpmbuild -bi foo.spec;

Re: [Rpm-maint] [PATCH] Unbreak short-circuited binary builds

2017-01-05 Thread Mark Wielaard
On Thu, Jan 05, 2017 at 01:47:28PM +0200, Panu Matilainen wrote: > Commit bbfe1f86b2e4b5c0bd499d9f3dd9de9c9c20fff2 broke short-circuited > binary builds (which can be handy for testing when working on large > packages), eg: > rpmbuild -bi foo.spec; rpmbuild -bb --short-circuit foo.spec > >

Re: [Rpm-maint] [PATCH] Only process regular files when generating build-ids

2017-01-05 Thread Panu Matilainen
On 01/05/2017 02:08 PM, Mark Wielaard wrote: On Thu, Jan 05, 2017 at 12:27:52PM +0200, Panu Matilainen wrote: It looks commit bbfe1f86b2e4b5c0bd499d9f3dd9de9c9c20fff2 intends to skip symlinks since it filters on S_ISREG(), but since uses fstat() on already open()'ed file it ends up stat()'ing

Re: [Rpm-maint] [PATCH] Only process regular files when generating build-ids

2017-01-05 Thread Mark Wielaard
On Thu, Jan 05, 2017 at 12:27:52PM +0200, Panu Matilainen wrote: > It looks commit bbfe1f86b2e4b5c0bd499d9f3dd9de9c9c20fff2 intends to skip > symlinks since it filters on S_ISREG(), but since uses fstat() > on already open()'ed file it ends up stat()'ing the symlink target. > Flip stat() + open()

[Rpm-maint] [PATCH] Unbreak short-circuited binary builds

2017-01-05 Thread Panu Matilainen
Commit bbfe1f86b2e4b5c0bd499d9f3dd9de9c9c20fff2 broke short-circuited binary builds (which can be handy for testing when working on large packages), eg: rpmbuild -bi foo.spec; rpmbuild -bb --short-circuit foo.spec The problem is that in a short-circuited build all the links already exist and

[Rpm-maint] [PATCH] Only process regular files when generating build-ids

2017-01-05 Thread Panu Matilainen
Versioned shared libraries typically have several symlinks pointing to them directly and indirectly. When %_build_id_links is set to compat or separate this causes bogus warnings about duplicate build-ids. It looks commit bbfe1f86b2e4b5c0bd499d9f3dd9de9c9c20fff2 intends to skip symlinks since it