Samuel Sieb wrote:
> You keep making this point, but I haven't seen any explanation for it.
> Why is it necessary to have Rawhide broken in order to do development?
> Don't you develop locally and then push the result when it's functional?
No (at least not for the typical packaging "development" w
Adam Williamson wrote:
> But it does depend on several other things that went through the libldb
> / libtdb complex. KDE images failed to compose and KDE package sets
> failed to install just like Server and Workstation. (KDE is in fact
> still broken even now ldb and tdb have been fixed, but that'
On Wed, Dec 7, 2016 at 2:13 AM, Adam Williamson
wrote:
> Emphasis is original, not mine.
>
> More to the point: it is entirely awful for the quality of Fedora as a
> whole if Rawhide is allowed to be completely broken for substantial
> periods of time - and this *did* make Rawhide completely brok
On Wednesday, December 7, 2016 6:21:02 AM CET Kevin Kofler wrote:
> Kamil Paral wrote:
> > This serves as a nice example why we need to tweak how Rawhide works if we
> > want people actually running on it.
>
> And why do we need that?
This is clear to me: Early testing -> early fixes -> faster d
On 12/07/2016 05:13 PM, Kevin Kofler wrote:
Adam Williamson wrote:
More to the point: it is entirely awful for the quality of Fedora as a
whole if Rawhide is allowed to be completely broken for substantial
periods of time - and this *did* make Rawhide completely broken.
You may consider it awf
On Thu, 2016-12-08 at 02:13 +0100, Kevin Kofler wrote:
> Adam Williamson wrote:
> > More to the point: it is entirely awful for the quality of Fedora as a
> > whole if Rawhide is allowed to be completely broken for substantial
> > periods of time - and this *did* make Rawhide completely broken.
>
Adam Williamson wrote:
> More to the point: it is entirely awful for the quality of Fedora as a
> whole if Rawhide is allowed to be completely broken for substantial
> periods of time - and this *did* make Rawhide completely broken.
You may consider it awful, but it is necessary to allow developme
Dne 6.12.2016 v 15:19 Kamil Paral napsal(a):
>> To all Rawhide users, be careful with update of mutter. It seems that
>> mutter-3.23.2-2.fc26 is broken [1], which prevents you from log in to
>> your system. Downgrade to mutter-3.23.1-2.fc26.x86_64 workarounded the
>> issues for me.
>>
>>
>> Vít
>>
> Kamil Paral wrote:
>
> And why do we need that? Rawhide is a place to do development, not a rolling
> release distro.
What is the purpose of Rawhide if it could be broken anytime?
I can't understand that, the development could be done and Rawhide could be
functional at the same time. It's not
On Wed, 2016-12-07 at 06:21 +0100, Kevin Kofler wrote:
> Kamil Paral wrote:
> > This serves as a nice example why we need to tweak how Rawhide works if we
> > want people actually running on it.
>
> And why do we need that? Rawhide is a place to do development, not a rolling
> release distro.
>
Kamil Paral wrote:
> This serves as a nice example why we need to tweak how Rawhide works if we
> want people actually running on it.
And why do we need that? Rawhide is a place to do development, not a rolling
release distro.
> So, we either need:
> a) updates-testing for Rawhide - e.g. with au
> To all Rawhide users, be careful with update of mutter. It seems that
> mutter-3.23.2-2.fc26 is broken [1], which prevents you from log in to
> your system. Downgrade to mutter-3.23.1-2.fc26.x86_64 workarounded the
> issues for me.
>
>
> Vít
>
>
> [1] https://bugzilla.redhat.com/show_bug.cgi?
12 matches
Mail list logo
