> > Cause i can't offer a review-swap (cause i am not in the packager
> > group), i offer a do-anything-swap in exchange to white_dune fedora
> > sponsoring.
>
> Posting links to the informal reviews you completed would be the best
> way to attract potential sponsors, but I cannot find any.
>
> Sh
On Fri, Jul 26, 2019 at 2:26 PM Robert-André Mauchin
wrote:
> Review Request: wgctrl - Control of WireGuard interfaces on multiple
> platforms
> https://bugzilla.redhat.com/show_bug.cgi?id=1730911
>
Done.
> Review Request: golang-github-mattn-ieproxy - Detect the proxy settings on
> Windows pl
# F31 Blocker Review meeting
# Date: 2019-07-29
# Time: 16:00 UTC
# Location: #fedora-blocker-review on irc.freenode.net
Hi folks! We have 4 proposed Beta blockers to review, so let's have a
Fedora 31 blocker review meeting on Monday!
If you have time this weekend, you can take a look at the prop
Oh wow, it's already that time in the Fedora 31 release cycle. Welcome
to the first Fedora 31 Beta blocker status email!
Action summary
Accepted blockers
-
1. bes — https://bugzilla.redhat.com/show_bug.cgi?id=1728419
ACTION: Server WG to decide if it makes sen
On Fri, Jul 26, 2019 at 8:19 PM Kevin Fenzi wrote:
>
> On 7/25/19 11:05 AM, Kaleb Keithley wrote:
> > hmmm. from the root.log
> >
> > DEBUG util.py:585: BUILDSTDERR: Error:
> > DEBUG util.py:585: BUILDSTDERR: Problem: conflicting requests
> > DEBUG util.py:585: BUILDSTDERR: - nothing provid
No missing expected images.
Compose PASSES proposed Rawhide gating check!
All required tests passed
Failed openQA tests: 6/147 (x86_64), 1/2 (arm)
New failures (same test not failed in Fedora-Rawhide-20190725.n.0):
ID: 426641 Test: x86_64 KDE-live-iso desktop_notifications_postinstall
URL:
Hello,
On Friday, 26 July 2019 at 18:42, J. Scheurich wrote:
> Hi,
>
> Cause i can't offer a review-swap (cause i am not in the packager
> group), i offer a do-anything-swap in exchange to white_dune fedora
> sponsoring.
Posting links to the informal reviews you completed would be the best
way t
* Kevin Fenzi [26/07/2019 09:25] :
>
> That said, we could:
> * make a bugzilla user for every package named
> 'packagename-ow...@fedoraproject.org'
> * assign bugs for that package to that user (no ccs)
Please don't do this.
The best feature the system we currently use has is accountability.
It'
On 7/25/19 11:05 AM, Kaleb Keithley wrote:
> hmmm. from the root.log
>
> DEBUG util.py:585: BUILDSTDERR: Error:
> DEBUG util.py:585: BUILDSTDERR: Problem: conflicting requests
> DEBUG util.py:585: BUILDSTDERR: - nothing provides kernel >= 4.18.0
> needed by firewalld-0.6.4-1.fc31.noarch
>
Hello,
I'd like some help to review a handful of Golang packages:
Review Request: wgctrl - Control of WireGuard interfaces on multiple platforms
https://bugzilla.redhat.com/show_bug.cgi?id=1730911
Review Request: golang-github-mattn-ieproxy - Detect the proxy settings on
Windows platform
https:
> "JN" == Jamie Nguyen writes:
JN> I couldn't find clear packaging policy on this. The guidelines [0]
JN> talk about %config(noreplace) vs %config, but /etc/named.conf is
JN> installed as a "noreplace" file.
I don't think there's a guideline about this. %config and
%config(noreplace) are si
Hi,
Cause i can't offer a review-swap (cause i am not in the packager
group), i offer a do-anything-swap in exchange to white_dune fedora
sponsoring.
I have some experience in writing C, C++, java, awk, lex/yacc and
shellscript, but i don't have enough time to write a complex 30
lines program
On Fri, Jul 26, 2019 at 09:25:54AM -0700, Kevin Fenzi wrote:
> On 7/26/19 4:25 AM, Hans de Goede wrote:
> > Proposal to really fix this. We often say that people should not feel they
> > own a package, but that this is all a team effort, hence we also promote
> > co-maintainer ship, so I propose th
Dne 26. 07. 19 v 18:25 Kevin Fenzi napsal(a):
> On 7/26/19 4:25 AM, Hans de Goede wrote:
>
>> 1) Have some automated process automatically email co-maintainers when the
>> primary maintainer orphan the package.
> That should already be the case? FMN should mail you... perhaps this
> isn't working?
On 7/26/19 4:25 AM, Hans de Goede wrote:
> 1) Have some automated process automatically email co-maintainers when the
> primary maintainer orphan the package.
That should already be the case? FMN should mail you... perhaps this
isn't working?
> 2) Make taking over the package a 1 click action
T
On Fri, Jul 19, 2019 at 07:17:52PM +0200, Miro Hrončok wrote:
ape...@gmail.com apevec
https://bugzilla.redhat.com/show_bug.cgi?id=1731531
https://bugzilla.redhat.com/show_bug.cgi?id=1705932
athoscribe...@gmail.com athoscr
https://bugzilla.redhat.com/show_bug.cgi?id=1731532
https://bugzilla.redha
On Fri, Jul 26, 2019 at 04:13:50PM +0100, Peter Robinson wrote:
> On Fri, Jul 26, 2019 at 1:14 PM Hans de Goede wrote:
> > Can we please stop this gargantuan time waste? Proposal to make this
> > less painful:
> >
> > 1) Have some automated process automatically email co-maintainers when the
> >
On Fri, Jul 26, 2019 at 1:14 PM Hans de Goede wrote:
>
> Hi,
>
> On 22-07-19 10:47, Miro Hrončok wrote:
> > The following packages are orphaned and will be retired when they
> > are orphaned for six weeks, unless someone adopts them. If you know for sure
> > that the package should be retired, ple
On Fri, Jul 26, 2019 at 02:41:44PM +0100, Richard W.M. Jones wrote:
>
> I've been trying to build nbdkit which depends on libnbd >= 0.1.9
> in Fedora Rawhide this morning.
>
> I built libnbd a few hours ago, but it hasn't turned up in Rawhide.
>
> I also discovered that you can now submit update
I need python3-oauth for MythTV on RPM Fusion. I looked into it and there
hasn't been a successful build since F28. I tried a simple update to python
3 BR's and the package built fine so I went ahead and built packages for
Rawhide and F30 based on the "no one seems to care about this package"
statu
I've been trying to build nbdkit which depends on libnbd >= 0.1.9
in Fedora Rawhide this morning.
I built libnbd a few hours ago, but it hasn't turned up in Rawhide.
I also discovered that you can now submit updates for Rawhide, so why
not: https://bodhi.fedoraproject.org/updates/FEDORA-2019-d3e
On 26/07/2019 14:17, Tom Hughes wrote:
On 23/07/2019 21:51, Pierre-Yves Chibon wrote:
This is the first roll-out of this gating change, and so there may be
additional
tuning and fixes until things are as smooth as we want them to be.
With this
release we are looking for feedback on what can be
On 23/07/2019 21:51, Pierre-Yves Chibon wrote:
This is the first roll-out of this gating change, and so there may be additional
tuning and fixes until things are as smooth as we want them to be. With this
release we are looking for feedback on what can be improved. We have a dedicated
team worki
https://fedoraproject.org/wiki/Changes/EnableSysctlPingGroupRange
(Note this change proposal was originally submitted before the
deadline, but was delayed due to some discussion between the change
owner and change wrangler)
== Summary ==
Enable the Linux kernel's net.ipv4.ping_group_range
paramet
On Fri, Jul 19, 2019 at 2:12 PM Miro Hrončok wrote:
>
> ktdre...@ktdreyer.com ktdreyer
> https://bugzilla.redhat.com/show_bug.cgi?id=1731540
> https://bugzilla.redhat.com/show_bug.cgi?id=1706223
Use kdre...@redhat.com instead.
He is currently on paternity leave and may not be responding to wor
OLD: Fedora-Rawhide-20190725.n.0
NEW: Fedora-Rawhide-20190726.n.0
= SUMMARY =
Added images:0
Dropped images: 3
Added packages: 4
Dropped packages:59
Upgraded packages: 68
Downgraded packages: 0
Size of added packages: 4.80 MiB
Size of dropped packages
Hi,
On 22-07-19 10:47, Miro Hrončok wrote:
The following packages are orphaned and will be retired when they
are orphaned for six weeks, unless someone adopts them. If you know for sure
that the package should be retired, please do so now with a proper reason:
https://fedoraproject.org/wiki/How_
Announcing the creation of a new nightly release validation test event
for Fedora 31 Rawhide 20190726.n.0. Please help run some tests for this
nightly compose if you have time. For more information on nightly
release validation testing, see:
https://fedoraproject.org/wiki
On 26. 07. 19 8:09, Haïkel wrote:
I'm still around, I had a kidney failure recently hence not able to answer.
Thanks for reaching back. Sorry to hear that.
--
Miro Hrončok
--
Phone: +420777974800
IRC: mhroncok
___
devel mailing list -- devel@lists.fe
Dne 25. 07. 19 v 23:07 Jason L Tibbitts III napsal(a):
>> "RF" == Richard Fearn writes:
> RF> According to
> RF>
> https://docs.fedoraproject.org/en-US/packaging-guidelines/#_architecture_build_failures:
>
>>> If a Fedora package does not successfully compile, build or work on
>>> an archite
Hi,
I noticed on an Ansible run that a recent update to bind changed
/etc/named.conf directly, instead of creating a separate rpmnew file.
(It's running sed in a scriptlet.)
I couldn't find clear packaging policy on this. The guidelines [0] talk
about %config(noreplace) vs %config, but /etc/named
On Fri, 26 Jul 2019 09:02:57 +0200
Dan Čermák wrote:
> Jason L Tibbitts III writes:
>
> >> "KK" == Kaleb Keithley writes:
> >
> > KK> I built the latest ceph-14 (14.2.2) on rawhide successfully two
> > KK> days ago. Two different builds on f30 built or are building
> > KK> fine on x86_64,
Hi,
I am not consuming that package and not able to update it. Time which
i can dedicate to Fedora side is dropped for me now and I am not even
sure how long it would be the case so I hope `python-grapefruit` will
find an another package maintainer.
--
Praveen Kumar
http://fedoraproject.org/wiki
Jason L Tibbitts III writes:
>> "KK" == Kaleb Keithley writes:
>
> KK> I built the latest ceph-14 (14.2.2) on rawhide successfully two days
> KK> ago. Two different builds on f30 built or are building fine on
> KK> x86_64, i686, and aarch64, but failed with different errors on
> KK> ppc64le
34 matches
Mail list logo
