On 14. 08. 19 14:23, Miro Hrončok wrote:
Hello.
Recently, a couple hundred packages were retired from rawhide (Fedora 31 at that
time) based on the Fedora Failed to Build From Source Policy [1]. From various
reactions over several threads it seems this policy is not ideal. This is an
attempt
> "GH" == Gerald Henriksen writes:
GH> On the other hand, unbuildable packages could be viewed as a
GH> security risk.
I mentioned security explicitly in my message. Just not in the portion
you quoted.
GH> If you can't just fix the security issue and rebuild, but instead
GH> have to also f
On Fri, 2019-08-16 at 15:21 +0100, Richard W.M. Jones wrote:
> On Wed, Aug 14, 2019 at 10:30:36AM -0700, Adam Williamson wrote:
> > I think the process is actually great. I kinda prefer the direction of
> > travel where we expect that packages are actively maintained and quite
> > aggressively thro
On 16. 08. 19 16:21, Richard W.M. Jones wrote:
I think if you make it easy to "throw out" packages then you must also
make it easy to add them back later. People do a lot of work adding
and maintaining packages and requiring a full re-review for a package
that was retired a few days ago is too m
On Wed, Aug 14, 2019 at 10:30:36AM -0700, Adam Williamson wrote:
> I think the process is actually great. I kinda prefer the direction of
> travel where we expect that packages are actively maintained and quite
> aggressively throw them out if they aren't, to the direction where we
> accumulate cru
On Thu, 2019-08-15 at 09:50 -0400, Gerald Henriksen wrote:
> On Wed, 14 Aug 2019 11:23:53 -0500, you wrote:
>
> > So in summary, I guess I mostly support allowing packages which can't be
> > rebuilt to stay in the distribution as long as they actually work and
> > aren't causing maintenance burden
Richard Shaw wrote:
> Perhaps a partial solution is encouraging people to ask for help. Sure
> it's easy to post to the devel list but sometimes it's difficult to admit
> you need help :)
IMHO, it should be the job of those people who broke the packages to fix
them. E.g., if yet another incompati
On Thu, Aug 15, 2019 at 1:33 PM Adam Williamson
wrote:
> Or just fix it so it damn well builds. Even if *you* don't need to use
> it. I mean, is it so hard? I get *itchy* if I have an FTBFS bug on one
> of my packages for three days. I can't imagine letting one sit there
> for six months!
>
I do
On Thu, 2019-08-15 at 09:33 +0200, Miro Hrončok wrote:
> On 15. 08. 19 7:39, Vít Ondruch wrote:
> > Of course you might consider this special case, but apparently all the
> > other people who speak up had different special cases.
>
> "special cases aren't special enough to break the rules"
>
> I
On Wed, 14 Aug 2019 11:23:53 -0500, you wrote:
>So in summary, I guess I mostly support allowing packages which can't be
>rebuilt to stay in the distribution as long as they actually work and
>aren't causing maintenance burden elsewhere
On the other hand, unbuildable packages could be viewed as a
On 15. 08. 19 14:40, Vít Ondruch wrote:
Interestingly enough, some people who complains the most about the process are
too busy to even switch the component to assigned ...
¯\_(ツ)_/¯
To rephrase: People have real work to do, so we should stop bothering them.
--
Miro Hrončok
--
Phone: +420777
Dne 15. 08. 19 v 14:40 Vít Ondruch napsal(a):
>
>
> Dne 15. 08. 19 v 13:36 Pavel Valena napsal(a):
>> - Original Message -
>>> Sent: Thursday, August 15, 2019 12:42:02 PM
>>> Subject: Re: Let's revisit the FTBFS policy
>>>
>>> On
Dne 15. 08. 19 v 13:36 Pavel Valena napsal(a):
> - Original Message -
>> Sent: Thursday, August 15, 2019 12:42:02 PM
>> Subject: Re: Let's revisit the FTBFS policy
>>
>> On 15. 08. 19 12:06, Vít Ondruch wrote:
>>> At the end, if somebody cares a
- Original Message -
> Sent: Thursday, August 15, 2019 12:42:02 PM
> Subject: Re: Let's revisit the FTBFS policy
>
> On 15. 08. 19 12:06, Vít Ondruch wrote:
> > At the end, if somebody cares about such cases, it should not be hard to
> > discover and ac
On 15. 08. 19 12:06, Vít Ondruch wrote:
At the end, if somebody cares about such cases, it should not be hard to
discover and act upon them, i.e. bugging the maintainer, fixing them,
taking over the maintenance etc.
This part is problematic. Because it requires human action that can be seen as
Dne 15. 08. 19 v 9:33 Miro Hrončok napsal(a):
> On 15. 08. 19 7:39, Vít Ondruch wrote:
>> Of course you might consider this special case, but apparently all the
>> other people who speak up had different special cases.
>
> "special cases aren't special enough to break the rules"
They had either
On 8/14/19 8:22 PM, Ben Cotton wrote:
I want to publicly express my appreciation for Miro's efforts to
enforce our policy and his willingness to take the hits from people
being rightly upset at its flaws.
Seconded. FWIW.
- Panu -
___
devel m
On 15. 08. 19 7:39, Vít Ondruch wrote:
Of course you might consider this special case, but apparently all the
other people who speak up had different special cases.
"special cases aren't special enough to break the rules"
I still think that if somebody would need to keep package unretired for
Dne 14. 08. 19 v 19:43 Miro Hrončok napsal(a):
> On 14. 08. 19 19:22, Ben Cotton wrote:
>> I want to publicly express my appreciation for Miro's efforts to
>> enforce our policy and his willingness to take the hits from people
>> being rightly upset at its flaws. I also appreciate that the communi
On 14. 08. 19 19:43, Miro Hrončok wrote:
E.g. when we release Fedora 32, Fedora 28 is already EOL for 5 months. It is
IMHO reasonable to expect the packages were rebuilt at least on Fedora 29.
Oh. When we release Fedora 32, Fedora 29 is already EOL for 5 months. But the
rest checks out. So the
- Original Message -
> From: "Miro Hrončok"
> To: devel@lists.fedoraproject.org
> Sent: Wednesday, August 14, 2019 7:43:13 PM
> Subject: Re: Let's revisit the FTBFS policy
>
> On 14. 08. 19 19:22, Ben Cotton wrote:
> > I want to publicly expres
On 14. 08. 19 19:22, Ben Cotton wrote:
I want to publicly express my appreciation for Miro's efforts to
enforce our policy and his willingness to take the hits from people
being rightly upset at its flaws. I also appreciate that the community
has done a good job of understanding that the policy i
On Wed, Aug 14, 2019 at 1:31 PM Adam Williamson
wrote:
>
> I actually think the consequences of the revival of the old policy have
> been fine. We are throwing out tons of cruft. Occasionally we find
> something very crufty yet important: this is a *good* outcome of the
> process. It alerts us to
On Wed, 2019-08-14 at 13:22 -0400, Ben Cotton wrote:
> I want to publicly express my appreciation for Miro's efforts to
> enforce our policy and his willingness to take the hits from people
> being rightly upset at its flaws. I also appreciate that the community
> has done a good job of understandi
I want to publicly express my appreciation for Miro's efforts to
enforce our policy and his willingness to take the hits from people
being rightly upset at its flaws. I also appreciate that the community
has done a good job of understanding that the policy is the problem
and not making it a persona
> "FW" == Florian Weimer writes:
FW> Debian treats FTBFS bugs as release-critical. They either have to
FW> be fixed, or the package gets removed from the release. However,
FW> this is not an automated process.
Of course, Debian works on a slightly different release schedule, so
it's not ex
> "MH" == Miro Hrončok writes:
MH> If we stop here, the current "setting to ASSIGNED to stop this"
MH> remains a problem.
Let's think about why this is perceived as a problem. The maintainer
has performed an affirmative act that shows they noticed. Can't we just
accept that as some stateme
On Wed, 2019-08-14 at 14:55 +0200, Vít Ondruch wrote:
> Dne 14. 08. 19 v 14:23 Miro Hrončok napsal(a):
> > Hello.
> >
> > Recently, a couple hundred packages were retired from rawhide (Fedora
> > 31 at that time) based on the Fedora Failed to Build From Source
> > Policy [1]. From various reaction
Dne 14. 08. 19 v 15:20 Miro Hrončok napsal(a):
> On 14. 08. 19 14:55, Vít Ondruch wrote:
>> I think it would be probably enough to stop here. Orphaned packages gets
>> garbage collected ATM. The step 4 was a bit unexpected for packages with
>> bugs in ASSIGNED state especially.
>
> If we stop here
On 14. 08. 19 14:55, Vít Ondruch wrote:
I think it would be probably enough to stop here. Orphaned packages gets
garbage collected ATM. The step 4 was a bit unexpected for packages with
bugs in ASSIGNED state especially.
If we stop here, the current "setting to ASSIGNED to stop this" remains a
Dne 14. 08. 19 v 14:23 Miro Hrončok napsal(a):
> Hello.
>
> Recently, a couple hundred packages were retired from rawhide (Fedora
> 31 at that time) based on the Fedora Failed to Build From Source
> Policy [1]. From various reactions over several threads it seems this
> policy is not ideal. This i
* Miro Hrončok:
> Recently, a couple hundred packages were retired from rawhide (Fedora
> 31 at that time) based on the Fedora Failed to Build From Source
> Policy [1]. From various reactions over several threads it seems this
> policy is not ideal. This is an attempt to collect feedback and make
32 matches
Mail list logo
