Hi Florian,
Yes, it's unavailable for me as well:
$ yum whatprovides /usr/lib64/librdkafka++.so.1 | grep rsyslog | wc -l
0
$ yum whatprovides /usr/lib64/librdkafka++.so.1 | grep epel | wc -l
2
Thanks for making that repo split! Very helpful for us.
best,
-Derek.
On Fri, Apr 27, 2018 at 8:19 AM
Here is what I did:
I made a copy of the v8-stable repo and named it v8-stable-build. We
will use this new repo for building new packages. In the regular
v8-stable repo we will only publish the RPMs that are intended for
public use. Also, I deleted all librdkafka support libraries that were
previo
Hi Florian,
As of now there are 8 packages in the rsyslog repo providing the
librdkafka++.so.1 dependency.
(and one package in epel, that's the last in the list below)
thanks,
-Derek.
**
$ yum whatprovides --disablerepo=epel /usr/lib64/librdkafka++.so.1
Loaded plugins: langpacks, produc
Hi Florian:
Thanks for removing that package.
So you know, there are still others in the rsyslog repo that satisfy the
same dependency
We still see a conflict but now with one of the adiscon-librdkafka packages.
The conflict used to be this:
Transaction check error:
file /usr/lib64/librdkafka
Derek, quick update.
I removed the librdkafka1 RPM from the repository for EL6 and EL7.
Since this exact RPM was not used by rsyslog anyway, it seems safe to
let it go.
I updated the repository accordingly, did a quick install test on my
lab machine and yum couldn't find it anymore, so I assume t
Derek,
thanks for the info. This is very useful for me. Obviously I
misunderstood how RPMs work in that regard.
As as far as librdkafka1 is involved, the root problem is clear. I
probably need to review now if we build non-rsyslog components
somewhere else which may also cause issues.
I think we
It's done by file name, not package name.
To double check I made a simple rpm that builds and packages two of the
examples from the librdkafka repo.
There's no mention of rsyslog or librdkafka packages anywhere. The
dependencies are driven by the files.
Two examples below. In the second I disabl
But packages require other packages by package name, not file name - or am
I wrong here? If I am not wrong, it would still mean a manual installation?
Rainer
Sent from phone, thus brief.
Derek DiFilippo schrieb am Do., 19. Apr. 2018, 22:47:
> Well, here's one way to create the bug, but it does
Well, here's one way to create the bug, but it doesn't have anything to do
with the rsyslog package and it doesn't require any willing installation of
librdkafka1... this is what I've been trying to communicate -- apologies
that it's been so long winded.
Imagine someone had added the rsyslog repo
Sent from phone, thus brief.
Derek DiFilippo schrieb am Do., 19. Apr. 2018, 22:05:
> We install rsyslog by adding the rsyslog repository to /etc/yum.repos.d and
> rely on yum from there.
>
> We do not modify or repackage rsyslog in any way.
>
> Florian can't guarantee anything about librdkafka1,
We install rsyslog by adding the rsyslog repository to /etc/yum.repos.d and
rely on yum from there.
We do not modify or repackage rsyslog in any way.
Florian can't guarantee anything about librdkafka1, unfortunately. Once
you've added the repositories to yum.repos.d, you get the following:
[ec2-
Mmm. Even then it doesn't totally explain. At least if Florian is
correct in that librdkafka1 was never installed anywhere automatically and
was never needed by rsyslog. I should call it a day...
Rainer
Sent from phone, thus brief.
Rainer Gerhards schrieb am Do., 19. Apr. 2018,
21:46:
> Oh
Ohhh... Are you a software developer who packages for third parties (like
we)? Are you concerned the a user of both of our products rubs into this
problem? Then this explains everything...
I was always under the impression that you are a user who installs a
different package in addition to rsyslog
Rainer,
yum sees those as different packages, not different versions of the same
package.
So we have two differently named packages installing the same file. That's
a conflict.
It's easy to reproduce. First yum install librdkafka1 from rsyslog then try
installing librdkafka from epel.
$ yum ins
Or is it so that yum takes the 1 in librdkafka1 as a version and this means
librdkafka1 has higher priority than librdkafka?
If so, why does in our setup a yum install librdkafka indeed install
librdkafka and not librdkafka1 albeit both repos are configured?
That counters the idea of version numb
Hi Rainier,
We install software on systems that aren't always under our control.
I have zero interest in librdkafka1 but I also have zero control over
whether some other package has installed it.
If yum already sees that dependency as satisfied by your librdkafka1, I'm
either stuck with that old
Sorry if I am dense, but why did you install librdkafka1?
Maybe I really don't understand anything at all, then so be it. I just
prefer to know why things happen.
I understand that there should be no kafka package at all in our repo. That
I always requested. I understand that two conflicting pack
Hi everyone,
The situation is exactly as described in my original email. We had a
combination of packages and dependencies that led to the yum conflict. It's
there, it's hard to get at, but we did it. The solution was to build from
source and link statically because we can't play around with rand
But the package names are different, so that other app's package should
depend on the other kafka package name, so nobody should drag in ours as
that name is never requested. That's at least my weak understanding ;-)
Rainer
Sent from phone, thus brief.
David Lang schrieb am Do., 19. Apr. 2018,
The conflict is that he has other software on his system that requires a
different version of librdkafka, and the version that gets pulled in from the
adiscon repo is wrong for his other software.
It's not a conflict with anything that rsyslog uses, it's a conflict with the
other software he's
yone for the rapid replies, much appreciated.
>> > > > >
>> > > > > best,
>> > > > > -Derek
>> > > > >
>> > > > > On Wed, Apr 18, 2018 at 8:59 AM, Florian Riedl > >
>> > > > wrote:
>> >
; > Florian
> > > > > >
> > > > > > 2018-04-17 18:26 GMT+02:00 Derek DiFilippo :
> > > > > > > If it is statically linked, can librdkafka1 be removed from
the
> > > > > > repository?
> > > > > > > It&
> >
> > > > > > 2018-04-17 18:26 GMT+02:00 Derek DiFilippo :
> > > > > > > If it is statically linked, can librdkafka1 be removed from the
> > > > > > repository?
> > > > > > > It's quite an old
the
> > > > > repository?
> > > > > > It's quite an old version of the library. It should be sufficient
> > to
> > > > use
> > > > > > the one from epel, correct?
> > > > > >
> > > > > > Th
> the one from epel, correct?
> > > > >
> > > > > That would fix our conflict.
> > > > >
> > > > > Thanks,
> > > > > -D.
> > > > >
> > > > >
> > > > > On Tue, Apr 17, 2018, 01:05 Andre Lorbach
> >
here?
> > > >>
> > > >> Florian can you check please if the package scripts are using
> > > >> --enable-kafka-static properly?
> > > >>
> > > >> The adisconbuild-librdkafka packages are used for building only, and
> >
gt; >> Florian can you check please if the package scripts are using
> > >> --enable-kafka-static properly?
> > >>
> > >> The adisconbuild-librdkafka packages are used for building only, and
> we
> > >> need them to get the static builds running on Laun
o get the static builds running on Launchpad!
> >>
> >> Best regards,
> >> Andre Lorbach
> >>
> >> > -Original Message-----
> >> > From: rsyslog [mailto:rsyslog-boun...@lists.adiscon.com] On Behalf Of
> >> > Rainer Gerha
gt;> > Rainer Gerhards
>> > Sent: Monday, April 16, 2018 8:26 PM
>> > To: rsyslog-users
>> > Subject: Re: [rsyslog] librdkafka packages in
>> v8-stable/epel-7/x86_64/RPMS
>> >
>> > Mmm... I was told that we link statically to librdkafka
the static builds running on Launchpad!
>
> Best regards,
> Andre Lorbach
>
> > -Original Message-
> > From: rsyslog [mailto:rsyslog-boun...@lists.adiscon.com] On Behalf Of
> > Rainer Gerhards
> > Sent: Monday, April 16, 2018 8:26 PM
> > To: rsyslog-us
og [mailto:rsyslog-boun...@lists.adiscon.com] On Behalf Of
>> Rainer Gerhards
>> Sent: Monday, April 16, 2018 8:26 PM
>> To: rsyslog-users
>> Subject: Re: [rsyslog] librdkafka packages in
> v8-stable/epel-7/x86_64/RPMS
>>
>> Mmm... I was told that we link stati
running on Launchpad!
Best regards,
Andre Lorbach
> -Original Message-
> From: rsyslog [mailto:rsyslog-boun...@lists.adiscon.com] On Behalf Of
> Rainer Gerhards
> Sent: Monday, April 16, 2018 8:26 PM
> To: rsyslog-users
> Subject: Re: [rsyslog] librdkafka packages i
Mmm... I was told that we link statically to librdkafka, so there
should no kafka package at all be installed (actually this was what I asked
for).
@florian, @andre can you comment?
Rainer
Sent from phone, thus brief.
Derek DiFilippo schrieb am Mo., 16. Apr. 2018, 20:19:
> Hi Rainer, hi e
Hi Rainer, hi everyone,
In addition to a dependency on rsyslog, one of our packages now depends on
librdkafka and librdkafka-devel.
We want to use the librdkafka packages provided by epel, nothing fancy.
I'm seeing a conflict between the librdkafka1 package in the rsyslog repo
(note the "1" at t
34 matches
Mail list logo
