Starting from Fedora 30, LuxRender repository
(https://src.fedoraproject.org/rpms/LuxRender/) is retired in favour of
luxcorerender (https://src.fedoraproject.org/rpms/luxcorender/)
following upstream.
Unfortunately, I don't know how to move other members to the new
luxcorender repository and they
On 2019-04-04 7:48 a.m., Richard Shaw wrote:
> On Wed, Apr 3, 2019 at 8:25 PM Luya Tshimbalanga
> mailto:l...@fedoraproject.org>> wrote:
>
> Add luxcorerender.
>
>
> Looks like it just directly depends on OpenImageIO, not OpenColorIO...
>
> # dnf repoquery --source --whatrequires "libOpenColorI
On 2019-04-04 1:42 p.m., Robert-André Mauchin wrote:
> On Thursday, 4 April 2019 19:39:23 CEST you wrote: >> On Thursday, 4 April
> 2019 16:53:38 CEST Luya Tshimbalanga wrote: >>>
luxcorerender kept on failing despite fulfilling all necessary build >>>
requirement. It occurred with slg-core which
> "RS" == Robert Scheck writes:
RS> wouldn't it have been a clever alternative to use lua52-* rather a
RS> quite unspecific "compat-lua-" to be really similar with your
RS> python2/3 example?
I made a similar suggestion in the packaging committee ticket.
"compat-" is nonspecific and goes aga
On Thursday, April 4, 2019 6:54:34 PM EDT Ty Young wrote:
> Hi,
>
>
> I didn't see a Silverblue specific mailing list and Fedora 30 is a beta
> so hopefully this is right. If it isn't, where is the appropriate place?
The Silverblue folks prefer the Fedora Discourse instance, found at
https://di
Hello Tomas,
On Thu, 04 Apr 2019, Tomas Krizek wrote:
> This makes it difficult to search for lua packages and preferably, there
> should be just a single naming scheme. Based on a discussion with
> maintainer of lua-lpeg and lua-mpack [2], we've agreed to use the naming
> scheme compat-lua-*
wou
Hi,
I didn't see a Silverblue specific mailing list and Fedora 30 is a beta
so hopefully this is right. If it isn't, where is the appropriate place?
Firstly I'd like to just say that the idea behind Fedora Silverblue is
really amazing. My understanding it's more orientated for containers an
On Thu, Apr 4, 2019 at 3:27 PM Kevin Fenzi wrote:
>
> On 4/4/19 1:16 PM, Neal Gompa wrote:
> > On Thu, Apr 4, 2019 at 10:02 AM Kevin Fenzi wrote:
> >>
> >> Greetings.
> >>
> >> This is a periodic reminder that we have some test instances setup for
> >> package maintainers. Please see:
> >>
> >> h
On Thu, Apr 04, 2019 at 09:24:13AM -0400, Stephen Gallagher wrote:
> On Wed, Apr 3, 2019 at 11:46 AM Adam Samalik wrote:
> >
> > Some modules now use "latest", "stable", or "master" as stream names for
> > various different things. It's quite confusing and I want to fix that.
> >
> > Without nami
On Thursday, 4 April 2019 19:39:23 CEST you wrote:
> On Thursday, 4 April 2019 16:53:38 CEST Luya Tshimbalanga wrote:
> > luxcorerender kept on failing despite fulfilling all necessary build
> > requirement. It occurred with slg-core which I vainly try to ignore it
> > as suggested by upstream. Can
On 4/4/19 1:16 PM, Neal Gompa wrote:
> On Thu, Apr 4, 2019 at 10:02 AM Kevin Fenzi wrote:
>>
>> Greetings.
>>
>> This is a periodic reminder that we have some test instances setup for
>> package maintainers. Please see:
>>
>> https://fedoraproject.org/wiki/Test_Machine_Resources_For_Package_Mainta
On Thu, Apr 4, 2019 at 10:02 AM Kevin Fenzi wrote:
>
> Greetings.
>
> This is a periodic reminder that we have some test instances setup for
> package maintainers. Please see:
>
> https://fedoraproject.org/wiki/Test_Machine_Resources_For_Package_Maintainers
>
> for more information.
>
> Additional
On 4/4/19 11:56 AM, Sergio Durigan Junior wrote:
> On Thursday, April 04 2019, Tom Hughes wrote:
>
>> On 04/04/2019 19:49, Sergio Durigan Junior wrote:
>>> On Thursday, April 04 2019, Tom Hughes wrote:
>>>
On 04/04/2019 19:39, Sergio Durigan Junior wrote:
> That's awesome, thanks Kev
On Thursday, April 04 2019, Tom Hughes wrote:
> On 04/04/2019 19:49, Sergio Durigan Junior wrote:
>> On Thursday, April 04 2019, Tom Hughes wrote:
>>
>>> On 04/04/2019 19:39, Sergio Durigan Junior wrote:
>>>
That's awesome, thanks Kevin. A while ago I wanted access to an arm32
machine r
On 04/04/2019 19:49, Sergio Durigan Junior wrote:
On Thursday, April 04 2019, Tom Hughes wrote:
On 04/04/2019 19:39, Sergio Durigan Junior wrote:
That's awesome, thanks Kevin. A while ago I wanted access to an arm32
machine running Rawhide, but found that the test machines are
unfortunately
On Thursday, April 04 2019, Tom Hughes wrote:
> On 04/04/2019 19:39, Sergio Durigan Junior wrote:
>
>> That's awesome, thanks Kevin. A while ago I wanted access to an arm32
>> machine running Rawhide, but found that the test machines are
>> unfortunately outdated (I may be wrong, but I tried usin
On 04/04/2019 19:39, Sergio Durigan Junior wrote:
That's awesome, thanks Kevin. A while ago I wanted access to an arm32
machine running Rawhide, but found that the test machines are
unfortunately outdated (I may be wrong, but I tried using mock inside
them and wasn't able either). Would it be
On Wednesday, April 03 2019, Kevin Fenzi wrote:
> Greetings.
>
> This is a periodic reminder that we have some test instances setup for
> package maintainers. Please see:
>
> https://fedoraproject.org/wiki/Test_Machine_Resources_For_Package_Maintainers
>
> for more information.
>
> Additionally, I
On Thursday, 4 April 2019 16:53:38 CEST Luya Tshimbalanga wrote:
> luxcorerender kept on failing despite fulfilling all necessary build
> requirement. It occurred with slg-core which I vainly try to ignore it
> as suggested by upstream. Can someone investigate?
>
> Here is the scratch build result
On 4/4/19 8:08 AM, Tom Hughes wrote:
> On 03/04/2019 23:48, Kevin Fenzi wrote:
>
>> Additionally, I have just added 2 aarch64 instances (running Fedora 29).
>
> That's great, except neither of them wants to let me in ;-)
Sorry about that. Fixed.
kevin
signature.asc
Description: OpenPGP digi
On 04. 04. 19 17:46, Michal Ambroz wrote:
Package python-impacket was providing whole bunch of utilities with additional
functionality like *wmiexec.py* and *psexec.py*, which currently do not have
replacement (process automation from linux to windows hosts).
This was an automation failure. As
On Thursday, 4 April 2019 16:53:38 CEST Luya Tshimbalanga wrote:
> luxcorerender kept on failing despite fulfilling all necessary build
> requirement. It occurred with slg-core which I vainly try to ignore it
> as suggested by upstream. Can someone investigate?
>
> Here is the scratch build result
Hello fellow packagers,
please am I the only one who doesn't like the way how the python2 packages
are being removed from Fedora?
I believe the package python-impacket should not have been removed.
Please Miro Hroncok can you revert the package removal?
The memo says:
"(Sub-)packages o
On 03/04/2019 23:48, Kevin Fenzi wrote:
Additionally, I have just added 2 aarch64 instances (running Fedora 29).
That's great, except neither of them wants to let me in ;-)
Tom
--
Tom Hughes (t...@compton.nu)
http://compton.nu/
___
devel mailing li
Greetings.
This is a periodic reminder that we have some test instances setup for
package maintainers. Please see:
https://fedoraproject.org/wiki/Test_Machine_Resources_For_Package_Maintainers
for more information.
Additionally, I have just added 2 aarch64 instances (running Fedora 29).
I hope
On a side note, OCIO doesn't support Python 3 (yet) so I'm going to drop
the python parts, I don't think there are any consumers of it on Fedora
anyway.
Thanks,
Richard
___
devel mailing list -- devel@lists.fedoraproject.org
To unsubscribe send an email
luxcorerender kept on failing despite fulfilling all necessary build
requirement. It occurred with slg-core which I vainly try to ignore it
as suggested by upstream. Can someone investigate?
Here is the scratch build result:
https://koji.fedoraproject.org/koji/taskinfo?taskID=33953912
Luya
_
On Wed, Apr 3, 2019 at 8:25 PM Luya Tshimbalanga
wrote:
> Add luxcorerender.
>
Looks like it just directly depends on OpenImageIO, not OpenColorIO...
# dnf repoquery --source --whatrequires "libOpenColorIO.so.1()(64bit)"
Last metadata expiration check: 0:01:41 ago on Thu 04 Apr 2019 09:45:27 AM
On Thu, Apr 4, 2019 at 3:59 PM Matthew Miller
wrote:
> On Thu, Apr 04, 2019 at 09:24:13AM -0400, Stephen Gallagher wrote:
> > > Without naming them, I see two different use cases:
> > > 1/ "for end users" — rolling stream meant for end users to consume,
> likely used in projects without tradition
On Thu, Apr 4, 2019 at 3:55 PM Matthew Miller
wrote:
> On Thu, Apr 04, 2019 at 09:25:36AM -0400, Stephen Gallagher wrote:
> > > > So the question is, do people agree there are two? Or just one? Or
> more?
> > > Upstreams aren't consistent. There's a good argument for making our
> branches
> > > m
On Thu, Apr 04, 2019 at 09:24:13AM -0400, Stephen Gallagher wrote:
> > Without naming them, I see two different use cases:
> > 1/ "for end users" — rolling stream meant for end users to consume, likely
> > used in projects without traditional versioning scheme, or for the latest
> > version that
On Thu, Apr 04, 2019 at 09:25:36AM -0400, Stephen Gallagher wrote:
> > > So the question is, do people agree there are two? Or just one? Or more?
> > Upstreams aren't consistent. There's a good argument for making our branches
> > match the pratices of upstreams -- but when two different upstreams
Hi,
Looks like I found something to do for someone with proven packager
privileges (which allow straight modify of any Fedora package git repo
without asking package maintainer to do modification).
Submitting hundreds of separated PRs for all below cases does not make to
much sense and totally wil
On (04/04/19 13:52), Matus Honek wrote:
>Hello,
>
>I would like to bring to your attention a recent change in our
>Contribution Guide [1]. We have updated the recommended commit message
>format. In particular, the "Fixes " string prefixing the URL which
>will make our lives easier in case of pull r
On Thu, Apr 4, 2019 at 9:23 AM Matthew Miller wrote:
>
> On Wed, Apr 03, 2019 at 05:44:43PM +0200, Adam Samalik wrote:
> > So the question is, do people agree there are two? Or just one? Or more?
>
> Upstreams aren't consistent. There's a good argument for making our branches
> match the pratices
On Wed, Apr 3, 2019 at 11:46 AM Adam Samalik wrote:
>
> Some modules now use "latest", "stable", or "master" as stream names for
> various different things. It's quite confusing and I want to fix that.
>
> Without naming them, I see two different use cases:
>
> 1/ "for end users" — rolling stream
On Wed, Apr 03, 2019 at 05:44:43PM +0200, Adam Samalik wrote:
> So the question is, do people agree there are two? Or just one? Or more?
Upstreams aren't consistent. There's a good argument for making our branches
match the pratices of upstreams -- but when two different upstreams think
different
On 04/04/2019 12.54, Miro Hrončok wrote:
> On 04. 04. 19 12:33, Tomas Krizek wrote:
>> If anyone has the rights to edit Package naming guidelines [1], please
>> document the proper way to name lua and compat-lua packages.
>
> Could you please open a ticket at
> https://pagure.io/packaging-committe
On 04. 04. 19 12:33, Tomas Krizek wrote:
If anyone has the rights to edit Package naming guidelines [1], please
document the proper way to name lua and compat-lua packages.
Could you please open a ticket at https://pagure.io/packaging-committee/issues ?
Thanks,
--
Miro Hrončok
--
Phone: +42077
On Thursday, April 4, 2019 11:28:36 AM CEST Ingvar Hagelund wrote:
> > On Thursday, March 28, 2019 11:58:21 AM CET Ingvar Hagelund wrote:
> > > Fedora prohibits the use of rpath (...)
>
> to., 28.03.2019 kl. 13.27 +0100, skrev Pavel Raiskup:
> > With new enough libtool script, you can use this ins
(This message is a copy for fedora-devel archival purposes, original
message was rejected by mailing list and was only sent to CCed maintainers)
Hi,
there is no official package naming guideline for lua packages in Fedora
[1].
Similarly to python2/python3, there are two version of lua: lua and
c
On Thu, 4 Apr 2019 at 11:31, Normand wrote:
>
>
> In fedora registry (1) we have f30/rawhide containers updated from last
> compose (2)
>but f28 last dated 20181007
>but f29 last dated 20190218
>Probably related to the DOOMED status reported in Container compose
> (3) Where f28/f29 tra
In fedora registry (1) we have f30/rawhide containers updated from last
compose (2)
but f28 last dated 20181007
but f29 last dated 20190218
Probably related to the DOOMED status reported in Container compose
(3) Where f28/f29 traceback.global file reports failures.
Is there already kno
> On Thursday, March 28, 2019 11:58:21 AM CET Ingvar Hagelund wrote:
> > Fedora prohibits the use of rpath (...)
to., 28.03.2019 kl. 13.27 +0100, skrev Pavel Raiskup:
> With new enough libtool script, you can use this instead:
>
> %configure LT_SYS_LIBRARY_PATH=%_libdir
>
> or if that makes
44 matches
Mail list logo
