Re: Improving the compose: leave the current compose in place

2018-12-01 Thread Ken Dreyer
On Tue, Nov 27, 2018 at 7:59 AM Owen Taylor wrote: > > A lot of discussion about improving the compose process seem to end up > with a "reality check" - that ideas have already been tried but don't > work because of requirements a) b) c) d). You can't have the pony, but > maybe if a lot of effort

Re: Improving the compose: leave the current compose in place

2018-11-29 Thread Peter Robinson
rk because of requirements a) b) c) d). You can't have the pony, but > > maybe if a lot of effort is put into it, you can have a faster rocking > > horse. > > > > If want to fundamentally improve the Fedora workflow we need compose > > ponies, we can't just h

Re: Improving the compose: leave the current compose in place

2018-11-27 Thread Paul Frields
ybe if a lot of effort is put into it, you can have a faster rocking > horse. > > If want to fundamentally improve the Fedora workflow we need compose > ponies, we can't just have rocking horses! > > Perhaps it would make sense to leave the current 8-10 hour compose in > place f

Re: Improving the compose: leave the current compose in place

2018-11-27 Thread Owen Taylor
On Tue, Nov 27, 2018 at 10:12 AM Stephen John Smoogen wrote: > Define what a compose is? Currently it is a word which covers a > multitude of different processes and reasons for those processes. We > can't 'fix' or even 'replace' or parallel them without actually > knowing why someone duct taped

Re: Improving the compose: leave the current compose in place

2018-11-27 Thread Stephen John Smoogen
maybe if a lot of effort is put into it, you can have a faster rocking > horse. > > If want to fundamentally improve the Fedora workflow we need compose > ponies, we can't just have rocking horses! > > Perhaps it would make sense to leave the current 8-10 hour compose in > plac

Improving the compose: leave the current compose in place

2018-11-27 Thread Owen Taylor
. If want to fundamentally improve the Fedora workflow we need compose ponies, we can't just have rocking horses! Perhaps it would make sense to leave the current 8-10 hour compose in place for the forseeable future, and work on a new system in parallel where the primary constraint is to

Re: leave

2018-02-02 Thread inderaue23
thanks! ;) > Kevin Fenzi <ke...@scrye.com> hat am 2. Februar 2018 um 18:49 geschrieben: > > > On 02/02/2018 06:51 AM, inderau...@arcor.de wrote: > > leave > > > If you are trying to unsubscribe, please m

Re: leave

2018-02-02 Thread Kevin Fenzi
On 02/02/2018 06:51 AM, inderau...@arcor.de wrote: > leave If you are trying to unsubscribe, please mail the unsubscribe address below: > ___ > devel mailing list -- devel@lists.fedoraproject.org > To unsubscribe send an email

leave

2018-02-02 Thread inderaue23
leave ___ devel mailing list -- devel@lists.fedoraproject.org To unsubscribe send an email to devel-le...@lists.fedoraproject.org

leave

2017-07-02 Thread ChunYu Wang
___ devel mailing list -- devel@lists.fedoraproject.org To unsubscribe send an email to devel-le...@lists.fedoraproject.org

[389-devel] Please review: ticket 49008 - aborted operation can leave RUV in incorrect state

2017-01-17 Thread Ludwig Krispenz
https://fedorahosted.org/389/ticket/49008 https://fedorahosted.org/389/attachment/ticket/49008/ticket49008_test.py https://fedorahosted.org/389/attachment/ticket/49008/0001-Ticket-49008-aborted-operation-can-leave-RUV-in-inco.patch -- Red Hat GmbH, http://www.de.redhat.com/, Registered seat