On Sat, Jul 19, 2014 at 7:12 PM, Richard Shaw wrote:
> On Sat, Jul 19, 2014 at 7:20 PM, Eric Smith wrote:
>> That could lead to packages that happen to build some of the time due
>> to an undetected dependency on something that isn't in the BR but
>> happens to be in a cached buildroot.
> I fail
lör 2014-07-19 klockan 12:30 +0100 skrev Richard W.M. Jones:
> The first step of most Koji builds is buildSRPMFromSCM, where a
> .src.rpm file is built from the git repo.
>
> Currently this involves completely building a mock buildroot
> containing all the BuildRequires, and running `rpmbuild -bs'
On Sat, Jul 19, 2014 at 7:20 PM, Eric Smith wrote:
> On Sat, Jul 19, 2014 at 7:26 AM, Richard Shaw
> wrote:
> > How about not rebuilding the chroot every time... It's not like you have
> to
> > worry about leftover BR's from building another package.
>
> That could lead to packages that happen t
On Saturday, July 19, 2014, 8:20:30 PM, Eric Smith wrote:
> On Sat, Jul 19, 2014 at 7:26 AM, Richard Shaw wrote:
>> How about not rebuilding the chroot every time... It's not like you have to
>> worry about leftover BR's from building another package.
> That could lead to packages that happen to
On Sat, Jul 19, 2014 at 7:26 AM, Richard Shaw wrote:
> How about not rebuilding the chroot every time... It's not like you have to
> worry about leftover BR's from building another package.
That could lead to packages that happen to build some of the time due
to an undetected dependency on someth
On Sat, Jul 19, 2014 at 5:30 AM, Richard W.M. Jones wrote:
> (1) Limit the use of macros in Source lines, so that only a simple,
> standard, perhaps pre-cached buildroot can be used.
How about just trying to parse the Source lines, and if that fails due
to use of macros that can't be evaluated in
Hello Everyone,
Since this package has been abandoned and I'd like to have it for dependencies
for users of Second Life and maybe others who might find it useful.
I've also fixed some minor compile issues for string security.
Thanks,
Shawn--
devel mailing list
devel@lists.fedoraproject.org
ht
On Thu, Jul 10, 2014 at 08:17:07AM +0300, Oron Peled wrote:
> On Thursday 10 July 2014 01:49:41 Lennart Poettering wrote:
> > Please understand that we are not duplicating "adduser" here. Already in
> > the name of the tool we wanted to make clear thtat this is abotu system
> > users, nothing else.
On Sat, Jul 19, 2014 at 03:37:15PM +0100, Sérgio Basto wrote:
>
>
> On Sáb, 2014-07-19 at 12:30 +0100, Richard W.M. Jones wrote:
> > The first step of most Koji builds is buildSRPMFromSCM, where a
> > .src.rpm file is built from the git repo.
> >
> > Currently this involves completely building
On Sat, Jul 19, 2014 at 1:30 PM, Richard W.M. Jones wrote:
>
> The first step of most Koji builds is buildSRPMFromSCM, where a
> .src.rpm file is built from the git repo.
>
> Currently this involves completely building a mock buildroot
> containing all the BuildRequires, and running `rpmbuild -bs'
On Sáb, 2014-07-19 at 12:30 +0100, Richard W.M. Jones wrote:
> The first step of most Koji builds is buildSRPMFromSCM, where a
> .src.rpm file is built from the git repo.
>
> Currently this involves completely building a mock buildroot
> containing all the BuildRequires, and running `rpmbuild -
How about not rebuilding the chroot every time... It's not like you have to
worry about leftover BR's from building another package.
Richard
--
devel mailing list
devel@lists.fedoraproject.org
https://admin.fedoraproject.org/mailman/listinfo/devel
Fedora Code of Conduct: http://fedoraproject.org/
The first step of most Koji builds is buildSRPMFromSCM, where a
.src.rpm file is built from the git repo.
Currently this involves completely building a mock buildroot
containing all the BuildRequires, and running `rpmbuild -bs'. This
takes many minutes (especially when arm is chosen as a builder
This has been a long time coming but after running on smaller systems
for the last couple months to make sure that all the parts are running
smoothly, Taskotron is now running in staging:
https://taskotron.stg.fedoraproject.org/
What does this mean? It means that we are almost ready to turn on th
so just in case it completely passed anybody *else* by, I thought I'd
note that we totally have a Fedora Jenkins instance:
http://jenkins.cloud.fedoraproject.org/
After a bit of poking about, I found a wiki page which explains a bit
about who's running it, why, and what you can do with it:
https
15 matches
Mail list logo
