> Begin forwarded message:
>
> Since I am likely still censored on <mailto:rpm-l...@rpm.org>>, I will reply here as well.
>
>> Begin forwarded message:
>>
>> From: Jeffrey Johnson mailto:n3...@me.com>>
>> Subject: Re: support for manual fi
Since I am likely still censored on , I will reply here as
well.
> Begin forwarded message:
>
> From: Jeffrey Johnson
> Subject: Re: support for manual file dependencies ?
> Date: June 21, 2017 at 4:09:36 AM EDT
> To: General discussion about the RPM package manager
>
SSIA
> Begin forwarded message:
>
> From: Andrey Ponomarenko
> Subject: Relaunched ABI tracker for libRPM 5
> Date: April 18, 2017 at 5:07:49 AM EDT
> To: n3...@me.com
> Cc: n3...@mac.com
>
> Hi Jeff,
>
> The ABI tracker for libRPM 5 is relaunched here:
> https://abi-laboratory.pro/tracker/ti
> On Dec 28, 2016, at 4:59 PM, Mark Hatle wrote:
>
>
> AFAIK, only openssl 1.0.x supports the FIPS module. There are a few folks
> looking at private implementations of the older module with OpenSSL 1.1.x, but
> definitely not official.
>
Yes, only 1.0.x atm.
The development timeline from o
> On Dec 28, 2016, at 7:02 AM, Alexander Kanavin
> wrote:
>
> On 12/27/2016 08:00 PM, Jeffrey Johnson wrote:
>
>> FYI: most of the openssl-1.1.0 port in rpm is now done.
>>
>> I’ve done “Do no harm testing.” with openssl-1.0.2j, will get to
>> detailed
> On Dec 13, 2016, at 11:09 AM, Jeffrey Johnson wrote:
>
>>
>> On Dec 13, 2016, at 8:34 AM, Alexander Kanavin
>> > <mailto:alexander.kana...@linux.intel.com>> wrote:
>>
>> On 12/09/2016 06:11 PM, Jeffrey Johnson wrote:
>>> Good: yo
This patch is needed for db-6.1.26/db-6.2.23 (now inlined for posterity) with
rpm-5.x.y:
73 de Jeff
=
diff -up db-6.2.23/src/env/env_failchk.c.jbj db-6.2.23/src/env/env_failchk.c
--- db-6.2.23/src/env/env_failchk.c.jbj 2016-03-28 15:45:5
> On Dec 13, 2016, at 8:34 AM, Alexander Kanavin
> wrote:
>
> On 12/09/2016 06:11 PM, Jeffrey Johnson wrote:
>> Good: you appear to have +beecrypt (for digests) and +libtomcrypt
>> (recommended
>> because of ECDSA and stable) and +openssl (what Yocto wants l
> On Dec 9, 2016, at 10:23 AM, Alexander Kanavin
> wrote:
>
>
…
Good.
>> There may be some issues with bison/flex in rpmdb (its WIP, the targets
>> aren’t critical),
>> and perl-URPM likely should be nuked (rm -rf perl-URPM).
>
> This is the latest failure:
>
> make[4]: Entering director
If you try building createrepo_c (my build is in doit.sh), you will see
…
RPM5 builds against libgit2 tip and libgit2 “breaks” every other month.
The fixes are usually rather easy, but the code is entirely proof-of-concept.
I recommend
rm -rf libgit2
(which is likely enuf to disable) and
> On Dec 8, 2016, at 8:49 AM, Alexander Kanavin
> wrote:
>
> On 12/08/2016 10:54 AM, Jeff Johnson wrote:
>>> Jeff, can you commit the changes to cvs?
>>>
>>
>> I can’t check in code blindly, nor will I check in code that cannot be
>> tested,
>> nor do I have the time to generate diff’s and e
> On Dec 8, 2016, at 10:16 AM, Alexander Kanavin
> wrote:
>
> On 12/07/2016 07:21 PM, Jeffrey Johnson wrote:
>> Your next stopping point is going to be Berkeley DB as a pre-requisite.
>
> I didn't get there yet; I hit a couple different issues, and these do lo
> On Dec 7, 2016, at 11:28 AM, Alexander Kanavin
> wrote:
>
> On 12/07/2016 06:22 PM, Alexander Kanavin wrote:
>
>> checking whether to build with Perl ExtUtils::Embed library... no
>> ++ executing failure action
>> ++ searching location: /usr/lib64
>> configure: error: Unknown location specif
> On Dec 7, 2016, at 11:22 AM, Alexander Kanavin
> wrote:
>
> On 12/02/2016 07:01 PM, Jeffrey Johnson wrote:
>> Building RPM from CVS — once you have decided options and installed
>> pre-requisites) —
>> is mostly this
>> cd rpm
>> ./dev
> On Dec 5, 2016, at 9:09 AM, Alexander Kanavin
> wrote:
>
> On 12/02/2016 07:01 PM, Jeffrey Johnson wrote:
>> What I need is to be able to see what cmake options you are using in order
>> to be able to build dnf pre-requisites without having to checkout (or
>
> On Dec 2, 2016, at 4:19 AM, Alexander Kanavin
> wrote:
>
> On 12/01/2016 08:35 PM, Jeffrey Johnson wrote:
>
>> There is the additional porting issue that libhif has pre-requisites,
>> including (at least)
>> rpm
>> rpm-python
>>
> On Nov 30, 2016, at 7:30 AM, Alexander Kanavin
> wrote:
>
> On 11/29/2016 06:02 PM, Jeffrey Johnson wrote:
>
>> Apologies, I’m new to project/repository management thru github.
>>
>> Should be fixed.
>>
>> We may have to iterate thru ssh key ex
> On Nov 30, 2016, at 7:42 AM, Alexander Kanavin
> wrote:
>
>>
>> (aside)
>> For starters, RPM5 uses keyutils(8), which has some hope of refactoring
>> _ALL__ pubkey
>> management out of _ALL_ RPM tool chains by writing a helper that is invoked
>> by the
>> keyutils async callback.
>
> Mayb
> On Nov 30, 2016, at 7:42 AM, Alexander Kanavin
> wrote:
>
> On 11/29/2016 06:31 PM, Jeffrey Johnson wrote:
>> The fundamental issue is that can only provide compile time
>> API compatibility.
>>
>> That’s fine for apparently simple projects that o
> On Nov 29, 2016, at 9:49 AM, Alexander Kanavin
> wrote:
>
> On 11/28/2016 06:35 PM, Jeffrey Johnson wrote:
>> 2) There are several repetitive cosmetic (but annoying) API differences.
>> These problems could (almost) be handled with some #defines
>>
> On Nov 29, 2016, at 10:10 AM, Alexander Kanavin
> wrote:
>
> On 11/28/2016 06:35 PM, Jeffrey Johnson wrote:
>
>> Make yourself happy with libhif: all of my work was largely exploratory
>> assessing what issues need to be solved. Feel free to clobber anything
>&
> On Nov 28, 2016, at 11:35 AM, Jeffrey Johnson wrote:
>
>
> Yes, there were quite a few checkins since I created the forks. I updated all
> the
> repositories that did not need merging this weekend (but that wasn’t libhif).
>
rpm5/libhif:master is no sync’ed wit
> On Nov 28, 2016, at 9:28 AM, Alexander Kanavin
> wrote:
>
> On 11/26/2016 01:07 AM, Jeffrey Johnson wrote:
>> FWIW, your invitation expired or is otherwise unusable (but at least
>> I can read your code, todo++).
>
> Yeah, I pressed the button on github and o
Begin forwarded message:From: Jeff Johnson Subject: rpm needs db-6.1.26+ patch (was Re: python3 optional deps)Date: June 5, 2016 at 2:06:12 PM EDTTo: "PLD: Developers list (English)" On Jun 1, 2016, at 6:29 PM, Elan Ruusamäe wrote:1. were in middle o
I stubbed my toe on this link today:
https://blog.fuzzing-project.org/52-Multiple-vulnerabilities-in-RPM-and-a-rant.html
So I ran the 5 rpm’s posted at the link through rpm in CVS:
$ ../rpm --version
lt-rpm (RPM) 5.4.18
(where afaik *.rpm package reading is identical to released
> Begin forwarded message:
>
> From: Jeffrey Johnson
> Subject: Re: rpm-5.4.16 snapshot
> Date: March 15, 2016 at 6:36:06 PM EDT
> To: "PLD: Developers list (English)"
> Reply-To: "PLD: Developers list (English)"
>
>>
>> On M
>>
>> BTW, if you want to try a parallel install of rpm-5.4.16 to system rpm, do
>> this
>> 1) add configure ... --with-paths-versioned
>> 2) instead of doing "make install", do "make DESTDIR=/var/tmp/rpm-root"
>> and copy the tree to /
>> The issue is libtool relinking n
> Begin forwarded message:
>
> From: Jeff Johnson
> Subject: Re: [OM Cooker] rpm-5.4.16 snapshot
> Date: March 15, 2016 at 5:30:53 PM EDT
> To: Bernhard Rosenkraenzer
> Cc: Cooker OpenMandriva
> Reply-To: Cooker OpenMandriva
>
>
> On Mar 15, 2016, at 5:12 PM, Bernhard Rosenkraenzer wrote:
.
hth
73 de Jeff
> regards
> srinivasan
>
> regards
> srini
>
> On Tue, Apr 14, 2015 at 8:47 PM, Jeffrey Johnson <mailto:n3...@me.com>> wrote:
>
>> On Apr 14, 2015, at 4:07 AM, srinivasan j v > <mailto:srinivasanj...@gmail.com>> wrote:
>>
>
> On Apr 14, 2015, at 4:07 AM, srinivasan j v wrote:
>
> Hello All
> I need to sign RPM using X509 Certificate and save the signatures (signature
> file ) along with the RPM package .
>
>1. Is there any way can i do that ?
>2. How can i save the these signature and any other c
On Apr 2, 2015, at 5:29 PM, devzero2000 wrote:
>
> Il 02/Apr/2015 18:43 "Jeffrey Johnson" ha scritto:
> >
> >
> > On Apr 2, 2015, at 12:11 PM, devzero2000 wrote:
> >
> >>
> >> Il 02/Apr/2015 17:39 "Jeffrey Johnson" ha scr
On Apr 2, 2015, at 12:11 PM, devzero2000 wrote:
>
> Il 02/Apr/2015 17:39 "Jeffrey Johnson" ha scritto:
> >
> > Um ... was there actually a problem being solved here?
> >
> > Some of these scripts (like rpm2cpio.sh) are vitally
> > imp
Um ... was there actually a problem being solved here?
Some of these scripts (like rpm2cpio.sh) are vitally
important and have been posted publicly like here
http://stackoverflow.com/questions/18787375/how-do-i-extract-the-contents-of-an-rpm/25986787#25986787
and integrated into other project
On Mar 11, 2015, at 2:28 PM, devzero2000 wrote:
>
> Il 11/Mar/2015 18:26 "Jeffrey Johnson" ha scritto:
> >
> > Is a git remote checkout of config.guess really needed?
> >
> > Can't config.guess be checked in and copied into place in autogen.sh
&g
Is a git remote checkout of config.guess really needed?
Can't config.guess be checked in and copied into place in autogen.sh instead?
73 de Jeff
On Mar 11, 2015, at 1:07 PM, Pinto Elia wrote:
> RPM Package Manager, CVS Repository
> http://rpm5.org/cvs/
> __
On Mar 10, 2015, at 2:15 AM, srinivasan j v wrote:
> hello all
>
> I'm supposed to you use X509 format for signing .
>
> I'm trying to sign the CPIO archive of a rpm . I need to package this
> signature inside the RPM. I can't add this part of CPIO archive as the
> generated signature varie
> On Feb 2, 2015, at 6:51 AM, srinivasan j v wrote:
>
> Hello all,
>
> Does RPM supports x509 format ?
>
Short answer: No.
All depends on what is meant by “support”.
RPM crypto is/was based on BeeCrypt which has no dependency on format.
(These days NSS/OpenSSL/libgcyrpt/libtomcrypt are also
On Jul 18, 2014, at 5:04 PM, Mark Hatle wrote:
> On 7/18/14, 3:08 PM, Jeffrey Johnson wrote:
>>
>> On Jul 1, 2014, at 10:12 AM, Mark Hatle wrote:
>>
>>> The recent changes to add variable encryption have left one compilation
>>> issue that I found. At
On Jul 1, 2014, at 10:12 AM, Mark Hatle wrote:
> The recent changes to add variable encryption have left one compilation issue
> that I found. Attached is a patch that adds the missing ifdefs to resolve
> the issue.
>
> --Mark
>
This patch finally checked in, thank you.
There's _STILL_ som
Please add some curly braces so that c99 compilers aren't required.
73 de Jeff
On Dec 19, 2013, at 1:12 PM, Pinto Elia wrote:
> RPM Package Manager, CVS Repository
> http://rpm5.org/cvs/
>
>
> Server: rpm5.org
On Sep 12, 2013, at 10:40 PM, Per Øyvind Karlsen wrote:
> 2013/8/29 Jeffrey Johnson
>
> On Aug 29, 2013, at 4:13 PM, Matthew Dawkins wrote:
>
>> Idk if this an "official" item on the ROADMAP, but having support for 30+
>> diff redirects in RPMIO "
On Sep 12, 2013, at 11:52 PM, Per Øyvind Karlsen wrote:
> 2013/8/26 Jeffrey Johnson
>
> On Aug 26, 2013, at 2:51 PM, Per Øyvind Karlsen wrote:
>
>> 2013/8/26 Jeffrey Johnson
>>
>> On Aug 26, 2013, at 2:19 PM, Per Øyvind Karlsen wrote:
>>
>> >
On Sep 12, 2013, at 11:40 PM, Per Øyvind Karlsen wrote:
> 2013/8/27 Jeffrey Johnson
> Not the right fix.
>
> Here's why:
>
> RPM includes/uses magic strings returned from libmagic.
>
> For reproducible results, where external "system" magic changes
On Sep 3, 2013, at 3:44 PM, Jeffrey Johnson wrote:
> Tim et al -- FYI
>
> There's several larger compilation changes
> that have been quietly underway for quite some
> time that you may want to consider:
>
> 1) switching from C -> C++
>
> I'm mostly
Tim et al -- FYI
There's several larger compilation changes
that have been quietly underway for quite some
time that you may want to consider:
1) switching from C -> C++
I'm mostly interested in attaching the current rpm object
ctor/dtor so that proper sub-classing can be done.
I'm also interes
On Aug 30, 2013, at 3:18 PM, Tim Mooney wrote:
> In regard to: Re: patches for OpenIndiana/Solaris 11, Jeffrey Johnson said...:
>
>>> I'm replacing my current x86_64-pc-solaris2.10 (traditional Solaris 10
>>> from before Oracle bought Sun, 10u6 to be exact) build
On Aug 29, 2013, at 2:31 PM, Tim Mooney wrote:
>
> Jeff, et. al. -
>
> I'm replacing my current x86_64-pc-solaris2.10 (traditional Solaris 10
> from before Oracle bought Sun, 10u6 to be exact) build box with a new
> x86_64-pc-solaris2.11, which is actually OpenIndiana 151a8.
>
> The RPM 5.1.9
k transport in RPM.
RPM cannot support for hobbyist usage, what linux vendors choose not to support.
All of the above needs to be rationalized before it makes any sense to discuss
30x redirects.
73 de Jeff
> Regards,
> Matt
>
>
> On Mon, Aug 26, 2013 at 5:23 PM, Jeffrey
it your own way?
>
>
> On Mon, Aug 26, 2013 at 4:43 PM, Jeffrey Johnson wrote:
> No interest because already there are huge amounts
> of breakage making *.spec files tied to per-distro choices
> of what compressor to invoke.
>
> I have to fix issues like this in nearly
On Aug 29, 2013, at 2:31 PM, Tim Mooney wrote:
>
> Jeff, et. al. -
>
> I'm replacing my current x86_64-pc-solaris2.10 (traditional Solaris 10
> from before Oracle bought Sun, 10u6 to be exact) build box with a new
> x86_64-pc-solaris2.11, which is actually OpenIndiana 151a8.
>
Nice!
> The RP
re clearly different than yours
if we disagree on mileage.
On Aug 26, 2013, at 3:12 PM, Per Øyvind Karlsen wrote:
> 2013/8/26 Jeffrey Johnson
>
> On Aug 26, 2013, at 2:24 PM, Per Øyvind Karlsen wrote:
>
> > This patch will strip away the buildroot prefix for duplicate files
On Aug 26, 2013, at 5:19 PM, Per Øyvind Karlsen wrote:
> 2013/8/26 Jeffrey Johnson
>
> On Aug 26, 2013, at 3:17 PM, Per Øyvind Karlsen wrote:
>
> > This patch ensures that strings has a null terminator at end, otherwise
> > strings passed to mireRegexec might be missi
On Aug 26, 2013, at 4:24 PM, Per Øyvind Karlsen wrote:
> This patch fixes neon saving error pages when encountered to target file.
>
> I'm not entirely sure if this is the *correct* way to fix it though, but at
> least it does work... ;)
>
There's lots of work pending in rpmdav.c, and some of
No interest because already there are huge amounts
of breakage making *.spec files tied to per-distro choices
of what compressor to invoke.
I have to fix issues like this in nearly every Fedora package I look
at, to replace explicit suffixes with a glob in %files manifests.
Maintain outside of rp
On Aug 26, 2013, at 4:21 PM, Per Øyvind Karlsen wrote:
> I'm almost done with the first round of pushing (mainly ~pure) bug fix(/more
> trivial) patches for now..
>
This has _NOTHING to do with file colors (because its a script).
Only elf executables have colors.
Meanwhile I have no desire to
On Aug 26, 2013, at 4:17 PM, Per Øyvind Karlsen wrote:
> Here's a patch from devzero2000 that got lost on HEAD...
>
Nothing is "lost" on HEAD or we would not be having this exchange.
debuginfo is maintained parallel to @rpm.org which is the chosen
distribution mechanism of the @redhat.com glib
On Aug 26, 2013, at 4:13 PM, Per Øyvind Karlsen wrote:
> Subject says it all..
Um no. I can't tell whether you have sent a reversed patch
or are attempting a change in behavior.
RPM SHOULD extract dependencies only from executable files.
This is advertised behavior because of
chmod -x
I'd love to apply this patch, but the ensuing "legacy compatibility"
discussions would eat months of my time.
So I choose my battles wisely, and won't apply the patch.
tracking dependency is a polite euphemism for I-N-C-O-M-P-A-T-B-I-L-E
invented to distract LSB (and others) from recognizing an i
Not the right fix.
Here's why:
RPM includes/uses magic strings returned from libmagic.
For reproducible results, where external "system" magic changes
arbitrarily, there are any number of problems that ensue
because the (what used to be) /etc/magic text has changed.
The only proper "reproducibl
Not the right fix afaict.
lua is treated as a "helper" library and merged
into librpmmisc when internal.
But how lua gets linked into rpm is rather complicated.
73 de Jeff
On Aug 26, 2013, at 4:05 PM, Per Øyvind Karlsen wrote:
> This patch fixes an issue with internal lua not being linked agai
On Aug 26, 2013, at 4:04 PM, Per Øyvind Karlsen wrote:
> This patch prevents dependencies being generated for block & character
> devices.
>
Any packaging that includes block/char devices is intrinsically busted.
Use %dev instead. Its been implememnted for a L-O-N-G time.
73 de Jeff
> --
>
See other comments regarding automagically filtering autodeps
manifests based on either MIME suffix or paths.
Its all fabulously fg=fragile and broken and needs to be implemented
intelligently and generally, not ad hoc patches to fix Yet Another just
realized convention.
Note that the existing
This fix is merely a band-aid (afaict).
The right fix is to add trailing '/' to dirnames always and
achieve a representation for file paths that does not
represent DIRNAMES with '/' in RPMTAG_DIRNAMES and
(redundantly) DIRNAMES without '/' in RPMTAG_BASENAMES.
What stops the implementation is lac
There are poorly understood (as in "tested") "legacy compatibility" issues
here.
The patch will be applied when RPM_I18NSTRING_TYPE is ripped
out and I am prepared to deal with the endless
I'm socked! Simply shocked!
that you would consider ripping out support for I18N summary/group/descri
On Aug 26, 2013, at 3:52 PM, Per Øyvind Karlsen wrote:
> This fixes a segfault with --verify (IIRC on packages signed with old
> signature type).
>
> The bug is discussed at https://qa.mandriva.com/show_bug.cgi?id=64378
>
> No definite consensus were ever achieved in previous discussions about
On Aug 26, 2013, at 3:45 PM, Per Øyvind Karlsen wrote:
> This patch strips newlines for mono dependencies generated that really
> shouldn't be there.. ;)
>
I have no way of testing this patch, nor do I believe that
the generated mono(...) dependency are worth maintaining.
At a minimum, script
*shrug* applied
The entire idea that one can specify a vendor reliably
in a file for access portably by AutoCrap is naive.
73 de Jeff
On Aug 26, 2013, at 5:27 PM, Per Øyvind Karlsen wrote:
> The follow patch fixes /etc/os-release being sourced right into same
> environment as the configure scri
On Aug 26, 2013, at 3:42 PM, Per Øyvind Karlsen wrote:
> This patch fixes tagSwab() to work with RPM_UINT64_TYPE.
>
> I'm not sure why it's not using newer functions (ie. from endian(3)) with
> support for 64 integers rather than using two 32 bit integers, but I guess it
> might be related to
Send to @rpm.org.
So far, I track _EXACTLY_ what the @redhat.com glibc cabal
recommends with no other changes.
And the entire debugedit code base, replacing NSS with
BeeCrypt digests (the right fix is to add a SHA1 implementation
to debugedit.c directly to simplify upgrading changes).
I also bel
See other comments regarding C-O-N-F-I-G-U-R-A-T-I-O-N
and that -debug* should be attempted internally to RPM,
not with very fragile helpers.
Note that realpath isnt implemented @rpm.org either (iirc, not looked).
73 de Jeff
On Aug 26, 2013, at 3:28 PM, Per Øyvind Karlsen wrote:
> This resolves
See other comments regarding ruby packaging:
this patch changes distributed C-O-N-F-G-U-R-A-T-I-O-N
and rubygem packaging is insufficiently portable/general
for it to matter what C-O-N-F-I-G-U-R-A-T-I-O-N is
distributed with RPM itself.
On Aug 26, 2013, at 3:25 PM, Per Øyvind Karlsen wrote:
> Thi
On Aug 26, 2013, at 3:24 PM, Per Øyvind Karlsen wrote:
> Requires no explanation..
>
So _THAT_ is why the harmless message is being displayed. ;-)
Applied, thanks.
The better (and p[lanned) fix is to rip out all code
marked with SUPPORT_I18NSTRING_TYPE now
that distros have had almost 1.5y to
On Aug 26, 2013, at 3:21 PM, Per Øyvind Karlsen wrote:
> I don't think this patch requires any elaboration...
Well the patch *does* need elaboration.
The sequence id is maintained persistently.
You are attempting to change the sequence id on some
pathway within some process that should NOT be
On Aug 26, 2013, at 3:17 PM, Per Øyvind Karlsen wrote:
> This patch ensures that strings has a null terminator at end, otherwise
> strings passed to mireRegexec might be missing it.
>
Is there a specific problem here? DO you have a reproducer?
The use of alloca tells me that I applied a band-
On Aug 26, 2013, at 3:13 PM, Per Øyvind Karlsen wrote:
> The following patch fixes a couple of minor memleaks.
>
The first patch indicates Yet Again that the patch isn't/wasn'yt
for @rpm5.org code. Please send proper patches.
There is an attempt to free the malloc'd memory, which
means that al
On Aug 26, 2013, at 3:09 PM, Per Øyvind Karlsen wrote:
> This patch should be pretty self-explaining.. :)
A reproducer please. This may (or may not) be the right
pace to fix, and there may be other places in need of fixing.
None of this is self-explanatory. I routinely run under valgrind
and in
On Aug 26, 2013, at 3:06 PM, Per Øyvind Karlsen wrote:
> 2013/8/26 Jeffrey Johnson
>
> On Aug 26, 2013, at 2:21 PM, Per Øyvind Karlsen wrote:
>
> > This patch fixes so that soft dependencies won't be displayed with 'rpm -q
> > --requires', only with
This patch is to macro madness configuration.
RPM is expected to be "legacy compatible" even if distros
don't give a hoot about what packaging conventions/naming
might have been in place when a distro was released.
You have also pointed out that gdb, not rpm, is responsible
for establishing conve
On Aug 26, 2013, at 2:51 PM, Per Øyvind Karlsen wrote:
> 2013/8/26 Jeffrey Johnson
>
> On Aug 26, 2013, at 2:19 PM, Per Øyvind Karlsen wrote:
>
> > The following patch fixes querying rpmdb with wildcards, whereas without
> > this fix, it'll return all entrie
See my other comments regarding
path based filtering, all of which is non-portable
even in linux, where paths/needs are on a "de facto" per-interpreter,
per-distro, and per-FHS-version basis.
General rule based filtering on content (i.e. using "man 5 magic" strings), or
a more
general configurat
On Aug 26, 2013, at 2:36 PM, Per Øyvind Karlsen wrote:
> This patch fixes an incorrect attempt to get the string length with sizeof on
> a string allocated on the heap.
>
The line numbers and code both indicate that this patch
is not against rpm5.org code.
The proper fix here (imho) is _NOT_
On Aug 26, 2013, at 2:30 PM, Per Øyvind Karlsen wrote:
> This patch fixes compatibility with ruby 1.9.
>
There are far far far deeper issues with ruby 1.8.x != 1.9.x behavior
that need to be addressed.
There is no "consensus" (no even a goal) stated that might lead to
a more useful implementat
See other comments:
Resolving simple build flaws rather than detecting and terminating a
build
configurably is what is needed.
73 de Jeff
On Aug 26, 2013, at 2:29 PM, Per Øyvind Karlsen wrote:
> This patch adds support for termination builds with files listed twice by
> setting
The existing behavior of find-debuginfo.sh is already
configurable: there is no One True Answer, nor is there
any benefit to cosmetically removing errors from eu-strip.
The far deeper flaw is that package executables are stripped multiple times
even if no one has noticed.
The entire means by whic
On Aug 26, 2013, at 2:25 PM, Per Øyvind Karlsen wrote:
> This patch enables termination of build on duplicate files by setting
> %_duplicate_files_terminate_build .
>
This (and many other patches of yours) merely detect flaws which
all have fairly simple resolutions that could be fully automat
On Aug 26, 2013, at 2:24 PM, Per Øyvind Karlsen wrote:
> This patch will strip away the buildroot prefix for duplicate files listed,
> providing greater consistency with behaviour otherwise.
>
While the approach is sensible, the deeper flaw is that duplicate
file checks added by Alexey Tourbin
On Aug 26, 2013, at 2:21 PM, Per Øyvind Karlsen wrote:
> This patch fixes so that soft dependencies won't be displayed with 'rpm -q
> --requires', only with 'rpm -q --suggests'
>
This patch can be done (by masking RPMSENSE_MISSINGOK using awk) without
changing any C code.
I'm also very reluct
On Aug 26, 2013, at 2:19 PM, Per Øyvind Karlsen wrote:
> The following patch fixes querying rpmdb with wildcards, whereas without this
> fix, it'll return all entries and not just those matching.
>
The issue of wildcard queries is/was discussed years ago when implemented, and
the behavior
im
ion, bad connectivity, and so on.
>
> Best
> ----Messaggio originale
> Da: Jeffrey Johnson
> Inviato: 17/08/2013, 20:44
> A: rpm-devel@rpm5.org
> Oggetto: Re: [CVS] RPM: rpm-5_4: neon/test/ Makefile.in
>
>
> Um, why?
>
> neon (as used in rpm, not as
Um, why?
neon (as used in rpm, not as distributed) uses automake where Makefile.am
generates Makefile.in whichis expanded to a Makefile.
73 de Jeff
On Aug 17, 2013, at 1:43 PM, Pinto Elia wrote:
> RPM Package Manager, CVS Repository
> http://rpm5.org/cvs/
> __
On Aug 11, 2013, at 3:06 PM, Per Øyvind Karlsen wrote:
>
> Not really something that's to encouraging for reporting any bugs nor
> submitting any patches..
>
I will assume you are too discouraged to discuss features, submit patches/bugs,
or otherwise participate in RPM development: it has bee
On Aug 16, 2013, at 1:11 PM, Jeffrey Johnson wrote:
>
> So something like this is the correct fix to muzzle coverity whinings:
>
> xx = chdir(somedir)
> xx = chroot(somedir)
> xx = chroot("/")
---^^ chdir
&g
On Aug 16, 2013, at 8:52 AM, Jeffrey Johnson wrote:
> Careful here ... Coverity static analysis likely just wants to see SOME chdir
> after a chroot.
>
> Check mock to see what the code in roto.c should do meaningfully.
>
OK, this isn't the right fix.
What coverity
On Aug 16, 2013, at 12:19 PM, Jeffrey Johnson wrote:
>
> The reason for assigning to an otherwise unsigned pointer
--- unused of
course
> is to ensure 2 things:
> 1) the value is often preserved on stack for
ess to free'd or
uninitialized
memory that may take months to be discovered when code gets rearranged.
73 de Jeff
> Best
> Messaggio originale
> Da: Jeffrey Johnson
> Inviato: 16/08/2013, 14:57
> A: rpm-devel@rpm5.org
> Cc: rpm-...@rpm5.org
> Oggetto: Re: [
Careful here too ... there are hundreds of
UNUSED reports.
I see no benefit to actually changing code to conform
with a mindless program (i.e. coverity) that disagrees with a deliberate
programming practice.
I have been marking issues like this intentional/insignificant/ignore and
assigning
to "
Careful here ... Coverity static analysis likely just wants to see SOME chdir
after a chroot.
Check mock to see what the code in roto.c should do meaningfully.
Even better (but much harder): compile and run roto.c (but this is development
work from like 2 years ago).
73 de Jeff
On Aug 16, 2013,
On Aug 11, 2013, at 3:06 PM, Per Øyvind Karlsen wrote:
>
> Increasingly I suspect that its all those patches that you are about to
> push that may be related to differences in behavior.
> Have you ever actually tested these embeddings in actual usage beyond
> regression tests?
See archives fro
On Aug 11, 2013, at 2:58 PM, Per Øyvind Karlsen wrote:
> 2013/8/9 Jeffrey Johnson
>
> On Aug 9, 2013, at 1:59 AM, Per Øyvind Karlsen wrote:
>
>> 2013/8/9 Jeffrey Johnson
>>
>> On Aug 8, 2013, at 9:29 PM, Per Øyvind Karlsen wrote:
>>
>>> 2013/8/
On Aug 8, 2013, at 4:01 PM, Per Øyvind Karlsen wrote:
> The following patch fixes the syntax of the python initialization code that
> resulted in neither the output redirection working nor the rpm python module
> being loaded.
>
The original syntax WORKSFORME and I cannot reproduce the
proble
1 - 100 of 227 matches
Mail list logo