Obsoleting LuxRender by luxcorerender

2019-04-04 Thread Luya Tshimbalanga
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

[Bug 1693012] perl-DateTime-TimeZone-2.34 is available

2019-04-04 Thread bugzilla
https://bugzilla.redhat.com/show_bug.cgi?id=1693012 Fedora Update System changed: What|Removed |Added Fixed In Version|perl-DateTime-TimeZone-2.34 |perl-DateTime-TimeZone-2.34

Re: Self-introduction : Zubin

2019-04-04 Thread zubin choudhary
yeah, I'd be working on Fedora Gooey Karma project for now. On Thu, 4 Apr, 2019, 23:25 Matthew Miller, wrote: > On Sat, Mar 30, 2019 at 02:56:15PM +0530, zubin choudhary wrote: > > Hi, I'm Zubin. I'm 19 years old. Using Linux for a while now wanted to > > contribute back to the community,

[EPEL-devel] Fedora EPEL 6 updates-testing report

2019-04-04 Thread updates
The following Fedora EPEL 6 Security updates need testing: Age URL 35 https://bodhi.fedoraproject.org/updates/FEDORA-EPEL-2019-06b243cced guacamole-server-1.0.0-1.el6 14 https://bodhi.fedoraproject.org/updates/FEDORA-EPEL-2019-62f9745b71 drupal7-7.65-1.el6 12

Re: Heads up: OpenColorIO 1.1.1

2019-04-04 Thread Luya Tshimbalanga
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

[389-devel] 389 DS nightly 2019-04-05 - 92% PASS

2019-04-04 Thread vashirov
https://fedorapeople.org/groups/389ds/ci/nightly/2019/04/05/report-389-ds-base-1.4.1.2-20190404git0319ec0.fc29.x86_64.html ___ 389-devel mailing list -- 389-devel@lists.fedoraproject.org To unsubscribe send an email to

Re: luxcorerender failure to build

2019-04-04 Thread Luya Tshimbalanga
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

[Bug 1693012] perl-DateTime-TimeZone-2.34 is available

2019-04-04 Thread bugzilla
https://bugzilla.redhat.com/show_bug.cgi?id=1693012 Fedora Update System changed: What|Removed |Added Fixed In Version|perl-DateTime-TimeZone-2.34 |perl-DateTime-TimeZone-2.34

Re: Package Naming Guildelines for compat-lua packages

2019-04-04 Thread Jason L Tibbitts III
> "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

[Bug 1688648] Upgrade perl-DBIx-RunSQL to 0.21

2019-04-04 Thread bugzilla
https://bugzilla.redhat.com/show_bug.cgi?id=1688648 Fedora Update System changed: What|Removed |Added Status|ON_QA |CLOSED Fixed In Version|

[Bug 1694347] perl-BerkeleyDB-0.60 is available

2019-04-04 Thread bugzilla
https://bugzilla.redhat.com/show_bug.cgi?id=1694347 Fedora Update System changed: What|Removed |Added Status|ON_QA |CLOSED Fixed In

[Bug 1679592] perl-Mock-Sub-1.09-5.fc30 FTBFS: files are not named in the MANIFEST file: /builddir/build/BUILD/Mock-Sub-1.09/debugfiles.list

2019-04-04 Thread bugzilla
https://bugzilla.redhat.com/show_bug.cgi?id=1679592 Fedora Update System changed: What|Removed |Added Status|ON_QA |CLOSED Fixed In Version|

[Bug 1694382] perl-BerkeleyDB-0.61 is available

2019-04-04 Thread bugzilla
https://bugzilla.redhat.com/show_bug.cgi?id=1694382 Fedora Update System changed: What|Removed |Added Status|ON_QA |CLOSED Fixed In

[Bug 1679590] perl-File-Edit-Portable-1.24-9.fc30 FTBFS: files are not named in the MANIFEST file: /builddir/build/BUILD/File-Edit-Portable-1.24/debugfiles.list

2019-04-04 Thread bugzilla
https://bugzilla.redhat.com/show_bug.cgi?id=1679590 Fedora Update System changed: What|Removed |Added Status|ON_QA |CLOSED Fixed In Version|

Re: Fedora 30 Beta Silverblue Feedback

2019-04-04 Thread John Harris
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

Re: Package Naming Guildelines for compat-lua packages

2019-04-04 Thread Robert Scheck
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-*

Fedora 30 Beta Silverblue Feedback

2019-04-04 Thread Ty Young
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

[Bug 1696467] New: perl-Test-Needs-0.002006 is available

2019-04-04 Thread bugzilla
https://bugzilla.redhat.com/show_bug.cgi?id=1696467 Bug ID: 1696467 Summary: perl-Test-Needs-0.002006 is available Product: Fedora Version: rawhide Status: NEW Component: perl-Test-Needs Keywords: FutureFeature, Triaged

[Bug 1696463] New: perl-HTTP-BrowserDetect-3.23 is available

2019-04-04 Thread bugzilla
https://bugzilla.redhat.com/show_bug.cgi?id=1696463 Bug ID: 1696463 Summary: perl-HTTP-BrowserDetect-3.23 is available Product: Fedora Version: rawhide Status: NEW Component: perl-HTTP-BrowserDetect Keywords:

Re: Maintainer test instances

2019-04-04 Thread Neal Gompa
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: > >> > >>

Re: Modularity question for packagers about rolling/latest/stable/master streams

2019-04-04 Thread Richard W.M. Jones
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

[Bug 1696450] New: perl-DB_File-1.851 is available

2019-04-04 Thread bugzilla
https://bugzilla.redhat.com/show_bug.cgi?id=1696450 Bug ID: 1696450 Summary: perl-DB_File-1.851 is available Product: Fedora Version: rawhide Status: NEW Component: perl-DB_File Keywords: FutureFeature, Triaged

Re: luxcorerender failure to build

2019-04-04 Thread Robert-André Mauchin
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.

Re: Maintainer test instances

2019-04-04 Thread Kevin Fenzi
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: >> >>

Re: Maintainer test instances

2019-04-04 Thread Neal Gompa
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. > >

Re: Maintainer test instances

2019-04-04 Thread Kevin Fenzi
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

Re: Maintainer test instances

2019-04-04 Thread Sergio Durigan Junior
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

Re: Maintainer test instances

2019-04-04 Thread Tom Hughes
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

Re: Maintainer test instances

2019-04-04 Thread Sergio Durigan Junior
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

Re: Maintainer test instances

2019-04-04 Thread Tom Hughes
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

Re: Maintainer test instances

2019-04-04 Thread Sergio Durigan Junior
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,

[EPEL-devel] Re: Major upgrade for singularity in EPEL

2019-04-04 Thread David Dykstra
The pagure issue https://pagure.io/epel/issue/53 was already approved so I will now do the builds and give them a 4 week testing period. Dave On Wed, Apr 03, 2019 at 11:47:43AM -0500, Dave Dykstra wrote: > Thanks very much for your reply, Stephen. > > I have already done scratch builds for

[Bug 1692114] perl-SNMP-Info-3.66 is available

2019-04-04 Thread bugzilla
https://bugzilla.redhat.com/show_bug.cgi?id=1692114 Fedora Update System changed: What|Removed |Added Status|MODIFIED|ON_QA --- Comment #2 from

Re: Self-introduction : Zubin

2019-04-04 Thread Matthew Miller
On Sat, Mar 30, 2019 at 02:56:15PM +0530, zubin choudhary wrote: > Hi, I'm Zubin. I'm 19 years old. Using Linux for a while now wanted to > contribute back to the community, Fedora is a great community to be part > of. I have some experience in python scripting and on Web Programming. > Looking

Re: luxcorerender failure to build

2019-04-04 Thread Robert-André Mauchin
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

Re: Maintainer test instances

2019-04-04 Thread Kevin Fenzi
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

Re: Please revert the python-impacket package removal

2019-04-04 Thread Miro Hrončok
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.

Re: luxcorerender failure to build

2019-04-04 Thread Robert-André Mauchin
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

Please revert the python-impacket package removal

2019-04-04 Thread Michal Ambroz
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

Re: Maintainer test instances

2019-04-04 Thread Tom Hughes
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

Maintainer test instances

2019-04-04 Thread Kevin Fenzi
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

Re: Heads up: OpenColorIO 1.1.1

2019-04-04 Thread Richard Shaw
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 failure to build

2019-04-04 Thread Luya Tshimbalanga
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

Re: Heads up: OpenColorIO 1.1.1

2019-04-04 Thread Richard Shaw
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

Re: Modularity question for packagers about rolling/latest/stable/master streams

2019-04-04 Thread Adam Samalik
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

Re: Modularity question for packagers about rolling/latest/stable/master streams

2019-04-04 Thread Adam Samalik
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 > > >

Re: Modularity question for packagers about rolling/latest/stable/master streams

2019-04-04 Thread Matthew Miller
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

Re: Modularity question for packagers about rolling/latest/stable/master streams

2019-04-04 Thread Matthew Miller
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

Using %verify and %ghost and other issues for mass cleanups

2019-04-04 Thread Tomasz Kłoczko
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

[389-devel] Re: Updated commit message format

2019-04-04 Thread Lukas Slebodnik
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

Re: Modularity question for packagers about rolling/latest/stable/master streams

2019-04-04 Thread Stephen Gallagher
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

Re: Modularity question for packagers about rolling/latest/stable/master streams

2019-04-04 Thread Stephen Gallagher
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

Re: Modularity question for packagers about rolling/latest/stable/master streams

2019-04-04 Thread Matthew Miller
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

[389-devel] Updated commit message format

2019-04-04 Thread Matus Honek
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 requests by automatically updating the

Re: Package Naming Guildelines for compat-lua packages

2019-04-04 Thread Tomas Krizek
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 >

Re: Package Naming Guildelines for compat-lua packages

2019-04-04 Thread Miro Hrončok
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:

Re: LD_LIBRARY_PATH vs rpath and libtool

2019-04-04 Thread Pavel Raiskup
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

Package Naming Guildelines for compat-lua packages

2019-04-04 Thread Tomas Krizek
(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

Re: f28/f29 container composes failure since a while, is it already tracked by an issue ?

2019-04-04 Thread Clement Verna
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

[EPEL-devel] Re: EPEL: Python34 moving to Python36

2019-04-04 Thread Miro Hrončok
On 04. 04. 19 10:08, Phil Wyett wrote: Hi, Just performed migration from 34 to 36. After yum update to pull all packages and install, I proceeded to install 36 packages to match my current 34 install before removing 34 packages. The only issue in the whole process was the one below that

f28/f29 container composes failure since a while, is it already tracked by an issue ?

2019-04-04 Thread Normand
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

Re: LD_LIBRARY_PATH vs rpath and libtool

2019-04-04 Thread Ingvar Hagelund
> 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

[Bug 1696126] Upgrade perl-Math-Pari to 2.030516

2019-04-04 Thread bugzilla
https://bugzilla.redhat.com/show_bug.cgi?id=1696126 Paul Howarth changed: What|Removed |Added Status|NEW |CLOSED Fixed In Version|

[EPEL-devel] Re: EPEL: Python34 moving to Python36

2019-04-04 Thread Phil Wyett
-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 On Tue, 2019-04-02 at 07:18 -0700, Troy Dawson wrote: > On Wed, Mar 13, 2019 at 7:31 AM Stephen John Smoogen wrote: > > > > Over the last 5 days, Troy Dawson, Jeroen van Meeuwen, Carl W George, > > and several helpers have gotten nearly all of the

[Bug 1696126] New: Upgrade perl-Math-Pari to 2.030516

2019-04-04 Thread bugzilla
https://bugzilla.redhat.com/show_bug.cgi?id=1696126 Bug ID: 1696126 Summary: Upgrade perl-Math-Pari to 2.030516 Product: Fedora Version: rawhide Status: NEW Component: perl-Math-Pari Assignee: p...@city-fan.org

[Bug 1692114] perl-SNMP-Info-3.66 is available

2019-04-04 Thread bugzilla
https://bugzilla.redhat.com/show_bug.cgi?id=1692114 Jitka Plesnikova changed: What|Removed |Added CC||jples...@redhat.com Fixed In

[Bug 1692114] perl-SNMP-Info-3.66 is available

2019-04-04 Thread bugzilla
https://bugzilla.redhat.com/show_bug.cgi?id=1692114 Fedora Update System changed: What|Removed |Added Status|NEW |MODIFIED --- Comment #1 from

DevConf.IN 2019 Inviting Speakers - CFP Open

2019-04-04 Thread P J P
Hello, The annual DevConf.IN conference is here again!   -> https://devconf.info/in/ We are glad to announce that CFP for DevConf.IN 2019 is now open!! :) Event Dates: 2 - 3 August 2019 Venue: Selection underway - TBA , Bengaluru, KA, India. Important dates  -> CFP closes: May 1st, 2019  ->

Re: Let's update pytest to 4.x

2019-04-04 Thread Zbigniew Jędrzejewski-Szmek
On Wed, Apr 03, 2019 at 09:28:47PM +0200, Miro Hrončok wrote: > On 03. 04. 19 20:47, Robert-André Mauchin wrote: > >On Wednesday, 3 April 2019 20:20:58 CEST Miro Hrončok wrote: > >>Hi. > >> > >>I'd like to update pytest as soon as possible to 4.3 (or 4.4 if agreed > >>upon). > >>This update will