Felix Schwarz writes:
>
> - package testing
>Manually checking updates-testing is too tedious and usually I don't want
>to install everything in updates-testing right away. But there are some
>packages which I like to get as fast as possible/which I can test easily.
>
>- So I
On Sat, Nov 30, 2019 at 01:42:04AM +0100, Kevin Kofler wrote:
> Fabio Valentini wrote:
> > I'm not really sure what you want to say here. There's a pretty strict
> > policy about what changes provenpackagers are "allowed" to make to
> > "foreign" packages, and it doesn't include pushing minor
On November 30, 2019 11:46:46 AM GMT+01:00, Felix Schwarz
wrote:
>
>Am 30.11.19 um 07:27 schrieb Chris Adams:
>> I think the problem is that unmaintained packages are still
>> unmaintained; drive-by changes by provenpackagers are not actual
>> maintenance, because that's not a scalable
Am 30.11.19 um 07:27 schrieb Chris Adams:
> I think the problem is that unmaintained packages are still
> unmaintained; drive-by changes by provenpackagers are not actual
> maintenance, because that's not a scalable organization (expecting
> provenpackagers to do all maintenance on random
Am 30.11.19 um 01:42 schrieb Kevin Kofler:
> Fabio Valentini wrote:
>> I'm not really sure what you want to say here. There's a pretty strict
>> policy about what changes provenpackagers are "allowed" to make to
>> "foreign" packages, and it doesn't include pushing minor improvements.
>
> Well,
Once upon a time, Kevin Kofler said:
> Well, in practice, a provenpackager can usually get away with just pushing
> stuff as long as nobody complains, and in particular with just pushing
> pretty much anything to effectively unmaintained packages. :-) And I don't
> really see a problem with
Fabio Valentini wrote:
> I'm not really sure what you want to say here. There's a pretty strict
> policy about what changes provenpackagers are "allowed" to make to
> "foreign" packages, and it doesn't include pushing minor improvements.
Well, in practice, a provenpackager can usually get away
Le 2019-11-29 11:39, Felix Schwarz a écrit :
Am 29.11.19 um 11:18 schrieb Miro Hrončok:
My effort is to raise the awareness about he failure. Despite my large
effort,
I cannot possibly fix all the build failures in Fedora.
I just wanted to mention that I appreciate your efforts.
I think the
On Fri, Nov 29, 2019 at 11:40 AM Felix Schwarz
wrote:
Hi Felix!
> Am 29.11.19 um 11:18 schrieb Miro Hrončok:
> > My effort is to raise the awareness about he failure. Despite my large
> > effort,
> > I cannot possibly fix all the build failures in Fedora.
>
> I just wanted to mention that I
Am 29.11.19 um 11:18 schrieb Miro Hrončok:
> My effort is to raise the awareness about he failure. Despite my large effort,
> I cannot possibly fix all the build failures in Fedora.
I just wanted to mention that I appreciate your efforts.
I think the "fallout" from retired packages may be a
On 29. 11. 19 2:53, Conrad Sand wrote:
Hi Miro,
Please _do not_ remove arpack and arpack-devel.
Sure, please rebuilt it. Orion has started to work on it in
https://src.fedoraproject.org/rpms/arpack/pull-request/1
A lot of other packages depend on that.
At least 49 according to the
11 matches
Mail list logo
