On Tue, Jun 11, 2019 at 11:08 PM Nico Kadel-Garcia wrote:
>
> On Mon, Jun 10, 2019 at 8:31 AM Dan Horák wrote:
> >
> > On Mon, 10 Jun 2019 11:35:52 +0200
> > Igor Gnatenko wrote:
> >
> > > On Mon, Jun 10, 2019 at 11:31 AM Vít Ondruch
> > > wrote:
> > > >
> > > > There used to be sent nagging em
On Thu, 2019-06-06 at 14:50 +0100, Sérgio Basto wrote:
> Hi,
>
> I'd like also update opencv to 3.4.6 on stable branches but due
> possible ABI breakage [1]. We might should rebuild all dependent
> software . Personally I think we do not have to follow all the advice
> of dist.abicheck , opencv h
On Mon, Jun 10, 2019 at 8:31 AM Dan Horák wrote:
>
> On Mon, 10 Jun 2019 11:35:52 +0200
> Igor Gnatenko wrote:
>
> > On Mon, Jun 10, 2019 at 11:31 AM Vít Ondruch
> > wrote:
> > >
> > > There used to be sent nagging email about broken dependencies, but
> > > it is not sent anymore. I last receive
Missing expected images:
Atomichost qcow2 x86_64
Atomichost raw-xz x86_64
Passed openQA tests: 2/2 (x86_64)
--
Mail generated by check-compose:
https://pagure.io/fedora-qa/check-compose
___
devel mailing list -- devel@lists.fedoraproject.org
To unsubsc
Awesome! Thank you.
-Original Message-
From: Eric Garver
To: Development discussions related to Fedora
Cc: Bojan Smojver
Subject: Re: Firewalld v nftables
Date: Tue, 11 Jun 2019 10:36:12 -0400
On Tue, Jun 11, 2019 at 07:14:49AM +1000, Bojan Smojver via devel wrote:
> This was patched
A new Fedora Atomic Host update is available via an OSTree update:
Version: 29.20190611.0
Commit(x86_64): 4ff9aafa12de2868cb3a4a4b9733e94d1165dac0f7d4ac1423efbd93bdaa58d2
Commit(aarch64):
6d24bdc428674dc3c793283180f038d7cbdb95d2879aed553227e1e76f1a98cb
Commit(ppc64le):
ed9e57c72ea107525d1c24246
Greetings,
It is has been 49 days since my package reviewer, Dave Love, last responded
to my review request: https://bugzilla.redhat.com/show_bug.cgi?id=1690046. How
do I proceed?
Note: I understand reviewers are pressed for time and I appreciate the heroic
efforts that keeps this community going
On Tue, Jun 11, 2019, 18:53 Ben Cotton wrote:
> On Wed, Jun 5, 2019 at 8:03 PM Ben Cotton wrote:
> >
> > Voting is now open for the Fedora 30 election cycle. You can vote in
> > the Elections app[1]. Interviews with candidates are available on the
> > Fedora Community Blog[2], with links availab
Is there a typo somewhere? Your original message or your last message.
Original says that voting ends on 20 June while today is 11th and you
write that there are only two more days left.
What is the correct date?
On Tue, Jun 11, 2019 at 6:53 PM Ben Cotton wrote:
>
> On Wed, Jun 5, 2019 at 8:03 P
On Tue, Jun 11, 2019 at 1:10 PM José Abílio Matos wrote:
>
> On Tuesday, 11 June 2019 17.15.18 WEST Ben Cotton wrote:
> > Reminder that voting is still open for two more days.
>
> I think that you mean nine more days. No? :-)
>
> That is what is written in the site and what I was expecting.
>
You'
On Tuesday, 11 June 2019 17.15.18 WEST Ben Cotton wrote:
> Reminder that voting is still open for two more days.
I think that you mean nine more days. No? :-)
That is what is written in the site and what I was expecting.
Best regards,
--
José Abílio
___
On 2019-06-10, Panu Matilainen wrote:
>
> As per https://fedoraproject.org/wiki/Changes/RPM-4.15, rpm 4.15-alpha
> will be hitting rawhide soon. A soname bump is involved but Igor kindly
> promised to handle rebuilding all dependent packages as part of the
> change, so no further action require
On Wed, Jun 5, 2019 at 8:03 PM Ben Cotton wrote:
>
> Voting is now open for the Fedora 30 election cycle. You can vote in
> the Elections app[1]. Interviews with candidates are available on the
> Fedora Community Blog[2], with links available in the Elections app.
> Voting ends at 23:59 UTC on 20
On Tue, Jun 11, 2019 10:24:21 +0200, Miro Hrončok wrote:
> > On Tue, Jun 11, 2019 08:59:11 +0100, Ankur Sinha wrote:
>
> > Still, since I don't know how it's done, what command does one use to
> > find these (and the reverse mappings) too please?
>
> That's a bit tedious. But you can follow the b
Richard Shaw wrote:
> I went ahead and kicked off a new build for 5.12.3.
>
> On a side note, shouldn't we update f30 to 5.12.3? looking at the
> changelogs between 5.12.2 and 5.12.3 there's about 450 bugs fixed.
>
> I recommend we do it in a side tag this time though :)
5.12.4 is coming soon,
On Tue, Jun 11, 2019 at 07:14:49AM +1000, Bojan Smojver via devel wrote:
> This was patched out, because an official feature was never submitted.
> Now that RHEL8 is using that combo, maybe it's time to try again? :-)
You are correct. Now that libvirt's integration with firewalld has
improved, it'
On 6/10/19 12:06 PM, Adam Williamson wrote:
> On Mon, 2019-06-10 at 09:24 +0900, Tristan Cacqueray wrote:
>> On Mon, Jun 10, 2019 at 01:24 Igor Gnatenko wrote:
>>> Hello,
>>>
>>> I have been trying to write some script which would listen on
>>> generation of new repository / successful build is t
I went ahead and kicked off a new build for 5.12.3.
On a side note, shouldn't we update f30 to 5.12.3? looking at the
changelogs between 5.12.2 and 5.12.3 there's about 450 bugs fixed.
I recommend we do it in a side tag this time though :)
Thanks,
Richard
>
_
It doesn't look like qt5-qtscxml has been updated to 5.12.3 yet...
https://koji.fedoraproject.org/koji/packageinfo?packageID=23346
Thanks,
Richard
___
devel mailing list -- devel@lists.fedoraproject.org
To unsubscribe send an email to devel-le...@lists.
On 11. 06. 19 10:24, Miro Hrončok wrote:
On 11. 06. 19 10:02, Ankur Sinha wrote:
On Tue, Jun 11, 2019 08:59:11 +0100, Ankur Sinha wrote:
> neuro-sig: jboss-jms-1.1-api, gsl
How would I ascertain which one of the neuro-sig packages requires this
jboss package?
$ sudo dnf repoquery --rec
On 11. 06. 19 10:02, Ankur Sinha wrote:
On Tue, Jun 11, 2019 08:59:11 +0100, Ankur Sinha wrote:
> neuro-sig: jboss-jms-1.1-api, gsl
How would I ascertain which one of the neuro-sig packages requires this
jboss package?
$ sudo dnf repoquery --recursive --whatrequires jboss-jms-1.1-api
j
On Mon, 10 Jun 2019 11:03:56 +0200
Felix Schwarz wrote:
> +1 to prevent broken dependencies to be pushed into stable. If Fedora
> aims to be a "polished"/"user friendly" distro users should never
> have to deal with broken dependencies.
>
> Also packages with broken dependencies should not be pa
On Tue, Jun 11, 2019 08:59:11 +0100, Ankur Sinha wrote:
> > > neuro-sig: jboss-jms-1.1-api, gsl
>
>
> How would I ascertain which one of the neuro-sig packages requires this
> jboss package?
>
> $ sudo dnf repoquery --recursive --whatrequires jboss-jms-1.1-api
> jbossws-cxf-0:5.1.5-6.fc30.n
Hello,
On Mon, Jun 10, 2019 21:28:55 +0100, Mat Booth wrote:
> On Mon, 10 Jun 2019 at 18:59, Fabio Valentini wrote:
>
> Hi Miro,
>
> I will request these for the stewardship SIG:
>
> jboss-websocket-1.0-api, weld-parent, jboss-jms-1.1-api,
> jboss-connector-1.7-api, jboss-marsh
Miro Hrončok writes:
> the-new-hotness orphan1 weeks ago
This looks scary, isn't this needed to actually run the-new-hotness? If
yes, I'll take it.
signature.asc
Description: PGP signature
___
devel mailin
> > lupinix: checkstyle, gsl
> >
>
> I requested ownership for gsl: https://pagure.io/releng/issue/8429
>
Thanks Christian.
Some scientific tools also depend on gsl, so the neuro-sig will be happy
to help out with it too. Please feel free to give "neuro-sig" commit
rights if you'd like.
--
T
26 matches
Mail list logo
