On Mon, Nov 02, 2015 at 12:34:03PM -0800, Adam Williamson wrote:
> it would be to do a scratch build of libtirpc , download the results,
> make a side repository, and do mock builds of the dependent packages.
> It's easy to create a mock target which uses a local side repository:
> you just copy th
On Tue, 2015-11-03 at 15:06 +0800, Ian Kent wrote:
> On Tue, 2015-11-03 at 15:00 +0800, Ian Kent wrote:
> > On Mon, 2015-11-02 at 19:55 -0800, Adam Williamson wrote:
> > > On Tue, 2015-11-03 at 11:30 +0800, Ian Kent wrote:
> > > >
> > > > Still, with COPR I would need to find a suitable location
On Tue, 2015-11-03 at 15:00 +0800, Ian Kent wrote:
> On Mon, 2015-11-02 at 19:55 -0800, Adam Williamson wrote:
> > On Tue, 2015-11-03 at 11:30 +0800, Ian Kent wrote:
> > >
> > > Still, with COPR I would need to find a suitable location to put
> > > the
> > > repo. so perhaps the mock method would
On Mon, 2015-11-02 at 19:55 -0800, Adam Williamson wrote:
> On Tue, 2015-11-03 at 11:30 +0800, Ian Kent wrote:
> >
> > Still, with COPR I would need to find a suitable location to put
> > the
> > repo. so perhaps the mock method would suit me better.
>
> COPR *is* a repo. All you need to do is l
On Tue, 2015-11-03 at 11:30 +0800, Ian Kent wrote:
>
> Still, with COPR I would need to find a suitable location to put the
> repo. so perhaps the mock method would suit me better.
COPR *is* a repo. All you need to do is log in, create a new COPR repo,
and you can upload SRPMs and it will build t
On Mon, 2015-11-02 at 18:46 -0800, Adam Williamson wrote:
> On Tue, 2015-11-03 at 09:49 +0800, Ian Kent wrote:
> >
> > This policy is clearly sensible and necessary, no question about
> > that.
> >
> > But this appears to be an opportunity for improvement as well.
> >
> > Fortunately the breaka
On Tue, 2015-11-03 at 09:49 +0800, Ian Kent wrote:
>
> This policy is clearly sensible and necessary, no question about
> that.
>
> But this appears to be an opportunity for improvement as well.
>
> Fortunately the breakage looks like it should be straight forward to
> resolve but that obviously
On Mon, 2015-11-02 at 11:15 -0800, Adam Williamson wrote:
> On Mon, 2015-11-02 at 11:02 +0800, Ian Kent wrote:
> > On Sun, 2015-11-01 at 18:48 +0100, Kalev Lember wrote:
> > > On 10/30/2015 05:36 PM, Kevin Fenzi wrote:
> > > > On Fri, 30 Oct 2015 11:50:48 -0400
> > > > Steve Dickson wrote:
> > > >
I often use mockchain locally to make sure all dependent packages rebuild
against the new library. The only watchout is that it will still try the
next build even if the main one (the one changing) doesn't build so make
sure you check in root.log that it used the new build or you will get a
false p
On 11/02/2015 03:32 PM, Adam Williamson wrote:
> On Mon, 2015-11-02 at 14:59 -0500, Steve Dickson wrote:
>
>>> Folks, this is not okay. This is not the right way to do things. If
>>> you
>>> aren't reasonably sure that all the library's consumers can be made
>>> to
>>> work with the new version
On Mon, 2015-11-02 at 14:59 -0500, Steve Dickson wrote:
> > Folks, this is not okay. This is not the right way to do things. If
> > you
> > aren't reasonably sure that all the library's consumers can be made
> > to
> > work with the new version of the library, *don't put the new
> > version in
> >
Hello,
On 11/02/2015 02:15 PM, Adam Williamson wrote:
> On Mon, 2015-11-02 at 11:02 +0800, Ian Kent wrote:
>> On Sun, 2015-11-01 at 18:48 +0100, Kalev Lember wrote:
>>> On 10/30/2015 05:36 PM, Kevin Fenzi wrote:
On Fri, 30 Oct 2015 11:50:48 -0400
Steve Dickson wrote:
> 2) find and r
On Mon, 2015-11-02 at 11:02 +0800, Ian Kent wrote:
> On Sun, 2015-11-01 at 18:48 +0100, Kalev Lember wrote:
> > On 10/30/2015 05:36 PM, Kevin Fenzi wrote:
> > > On Fri, 30 Oct 2015 11:50:48 -0400
> > > Steve Dickson wrote:
> > > > 2) find and rebuild all the dependencies?
> > >
> > > Should be so
On Mon, 2015-11-02 at 11:02 +0800, Ian Kent wrote:
> On Sun, 2015-11-01 at 18:48 +0100, Kalev Lember wrote:
> > On 10/30/2015 05:36 PM, Kevin Fenzi wrote:
> > > On Fri, 30 Oct 2015 11:50:48 -0400
> > > Steve Dickson wrote:
> > > > 2) find and rebuild all the dependencies?
> > >
> > > Should be so
On Sun, 2015-11-01 at 18:48 +0100, Kalev Lember wrote:
> On 10/30/2015 05:36 PM, Kevin Fenzi wrote:
> > On Fri, 30 Oct 2015 11:50:48 -0400
> > Steve Dickson wrote:
> > > 2) find and rebuild all the dependencies?
> >
> > Should be something like:
> >
> > % sudo dnf repoquery --whatrequires 'libt
On 10/30/2015 05:36 PM, Kevin Fenzi wrote:
> On Fri, 30 Oct 2015 11:50:48 -0400
> Steve Dickson wrote:
>> 2) find and rebuild all the dependencies?
>
> Should be something like:
>
> % sudo dnf repoquery --whatrequires 'libtirpc.so.1()(64bit)'
> Last metadata expiration check performed 0:01:17 a
On 10/30/2015 07:57 PM, Ian Kent wrote:
> On Fri, 2015-10-30 at 14:16 -0400, Steve Dickson wrote:
>>
>> On 10/30/2015 12:36 PM, Kevin Fenzi wrote:
>>> On Fri, 30 Oct 2015 11:50:48 -0400
>>> Steve Dickson wrote:
>>>
Hello,
Well place sources tell me in the upcoming
libtirpc re
On Fri, 2015-10-30 at 14:16 -0400, Steve Dickson wrote:
>
> On 10/30/2015 12:36 PM, Kevin Fenzi wrote:
> > On Fri, 30 Oct 2015 11:50:48 -0400
> > Steve Dickson wrote:
> >
> > > Hello,
> > >
> > > Well place sources tell me in the upcoming
> > > libtirpc release the soname will be changing
> >
On 10/30/2015 12:36 PM, Kevin Fenzi wrote:
> On Fri, 30 Oct 2015 11:50:48 -0400
> Steve Dickson wrote:
>
>> Hello,
>>
>> Well place sources tell me in the upcoming
>> libtirpc release the soname will be changing
>> due to some API changes.
>>
>> The API changes will make the Linux version
>>
On Fri, 30 Oct 2015 11:50:48 -0400
Steve Dickson wrote:
> Hello,
>
> Well place sources tell me in the upcoming
> libtirpc release the soname will be changing
> due to some API changes.
>
> The API changes will make the Linux version
> more compatible with litbirpc implementations
>
> Obvio
Hello,
Well place sources tell me in the upcoming
libtirpc release the soname will be changing
due to some API changes.
The API changes will make the Linux version
more compatible with litbirpc implementations
Obviously this change will just go in rawhide
but how do I
1) request the build rpm
21 matches
Mail list logo
