On Wed, Sep 25, 2019 at 6:01 PM Adam Samalik wrote:
>
> This is the Minimization Objective [0] update.
>
> Status: Discovery phase
>
> == Regular meeting canceled ==
>
> We have decided to cancel the regular Minimization Team Meeting [1] as we
> prefer async discussions on #fedora-devel and de...
On 9/25/19 8:26 PM, Tomasz Torcz wrote:
> On Wed, Sep 25, 2019 at 12:14:54PM +0200, Christophe de Dinechin wrote:
>> Hi Lokesh,
>>
>>
>> As you know, I have been working on bringing kata containers to Fedora.
>>
>> Since this adds a new runtime, the docker.service file would need to be
>> modified
Greetings,
Fedora Infrastructure currently has the majority of its hardware in a
datacenter in Arizona, USA. Red Hat leases this space for use by a number of
teams, including Fedora. However, they've been seeking a more modern and cost
effective location for some time and have decided on one:
OLD: Fedora-31-20190926.n.0
NEW: Fedora-31-20190927.n.1
= SUMMARY =
Added images:0
Dropped images: 0
Added packages: 1
Dropped packages:1
Upgraded packages: 49
Downgraded packages: 0
Size of added packages: 37.53 KiB
Size of dropped packages:96.51 MiB
No missing expected images.
Failed openQA tests: 5/152 (x86_64), 1/2 (arm)
New failures (same test not failed in Fedora-31-20190926.n.0):
ID: 459545 Test: x86_64 Silverblue-dvd_ostree-iso desktop_terminal
URL: https://openqa.fedoraproject.org/tests/459545
ID: 459550 Test: x86_64 univer
Coty Sutherland wrote:
> I'm working on (learning modularity) and developing a module for my
> package and created a not-so-great (super long) branch name in the
> dist-git rpm and module repo before I realized that it would be the
> stream's name too. Also, it seems that the incomplete module was
On Fri, Sep 27, 2019 at 10:57:21AM -0400, Neal Gompa wrote:
> On Fri, Sep 27, 2019 at 9:54 AM Panu Matilainen wrote:
> >
> > On 9/26/19 10:05 PM, Jeremy Cline wrote:
> > > On Thu, Sep 26, 2019 at 02:57:56PM -0400, Randy Barlow wrote:
> > >> On Thu, 2019-09-26 at 14:49 +, Jeremy Cline wrote:
>
Action summary
Accepted blockers
-
1. mutter — can't turn zoom off once enabled — NEW
ACTION: upstream to diagnose and fix issue
2. distribution — Cannot upgrade to Fedora 31: package
exa-0.9.0-2.module_f31+5365+04413d87.x86_64 requires
libgit2.so.28()(64bit),
On Wed, Sep 25, 2019 at 05:52:31PM +0200, Adam Samalik wrote:
> == pcre -> pcre2 ==
> Moving grep (one of the last packages using pcre) to pcre2. [4]
Is this a perfectly drop-in compatible replacement from a user point of
view?
--
Matthew Miller
Fedora Project Leader
__
# F31 Blocker Review meeting
# Date: 2019-09-30
# Time: 16:00 UTC
# Location: #fedora-blocker-review on irc.freenode.net
Hi folks! We have 10 proposed Final blockers and 4 proposed Final freeze
exception to review, so let's have a Fedora 31 blocker review meeting
on Monday!
If you have time today
# Fedora Quality Assurance Meeting
# Date: 2019-09-30
# Time: 15:00 UTC
(https://fedoraproject.org/wiki/Infrastructure/UTCHowto)
# Location: #fedora-meeting on irc.freenode.net
Greetings testers!
We didn't meet last week and F31 is cranking up, so let's check in on
where we're at.
If anyone has
>> Yes, you can hide the branch from the result of "dnf module list". I
>> asked it to someone to hide "private-jaruga-master" stream.
>> But I forget the way.
>
>
> Maybe someone else can help :D
I remembered the way after searching my past emails. :D
You can open a ticket on releng to hide it li
On Thu, Sep 26, 2019, at 10:24 AM, Pierre-Yves Chibon wrote:
> I like this.
> It means that the build-system would have to generate the tarball of the
> source
> and put it into dist-git at srpm-build time (I believe we still want to store
> a
> copy of the sources used for a build).
https://gi
On Fri, 2019-09-27 at 12:06 -0400, Neal Gompa wrote:
> On Fri, Sep 27, 2019 at 12:03 PM Sérgio Basto
> wrote:
> > Hi,
> > epel 8 brings a new file called package.cfg, I strongly prefer to
> > keep
> > branches mergeable with fast forward , may we merge this into
> > master ?
> > like I did in pngq
Hello,
I have 2 new dependencies for Rclone in needs of a review:
Review Request: golang-github-jzelinskie-whirlpool - Whirlpool cryptographic
hashing library
https://bugzilla.redhat.com/show_bug.cgi?id=1755566
Review Request: golang-github-putdotio-putio - Put.io Go API client
https://bugzill
This is a test message, please ignore it. (I'm trying to find out
why my last reply had mangled In-Reply-To header.)
-- Petr
___
devel mailing list -- devel@lists.fedoraproject.org
To unsubscribe send an email to devel-le...@lists.fedoraproject.org
Fedor
On Fri, Sep 27, 2019 at 12:03 PM Sérgio Basto wrote:
>
> Hi,
> epel 8 brings a new file called package.cfg, I strongly prefer to keep
> branches mergeable with fast forward , may we merge this into master ?
> like I did in pngquant [1]
>
It disables the normal build behavior for all non-master br
Hi,
epel 8 brings a new file called package.cfg, I strongly prefer to keep
branches mergeable with fast forward , may we merge this into master ?
like I did in pngquant [1]
[1]
https://src.fedoraproject.org/rpms/pngquant/commits/master
Thanks
--
Sérgio M. B.
___
Hi fellow Fedorans,
I'm trying to contact Benjamin Pereto (FAS: bpereto), maintainer of
borgbackup and borgmatic.
https://src.fedoraproject.org/user/bpereto
https://src.fedoraproject.org/rpms/borgmatic
I have started the non-responsive maintainer process as borgmatic has
not seen an upd
On Fri, 2019-09-27 at 08:50 -0700, Tom Stellard wrote:
>
> The LLVM update has the necessary karma now and all the gating tests
> have passed. Should I push this to stable now and then push the mesa
> update later or should we still try to combine the updates?
You can push LLVM and then mesa, it
27.09.2019, 16:51, "Tom Stellard" :
> The LLVM update has the necessary karma now and all the gating tests
> have passed. Should I push this to stable now and then push the mesa
> update later or should we still try to combine the updates?
Yes, go for it and push it to stable. I'll submit mesa to
On Thu, 2019-09-26 at 13:21 -0700, Adam Williamson wrote:
> On Thu, 2019-09-26 at 20:55 +0200, Hans de Goede wrote:
> > Hi Tom,
> >
> > On 26-09-2019 20:47, Tom Stellard wrote:
> > > On 09/26/2019 11:24 AM, Adam Williamson wrote:
> > > > On Thu, 2019-09-26 at 11:20 -0700, Tom Stellard wrote:
> > >
On 09/26/2019 01:21 PM, Adam Williamson wrote:
> On Thu, 2019-09-26 at 20:55 +0200, Hans de Goede wrote:
>> Hi Tom,
>>
>> On 26-09-2019 20:47, Tom Stellard wrote:
>>> On 09/26/2019 11:24 AM, Adam Williamson wrote:
On Thu, 2019-09-26 at 11:20 -0700, Tom Stellard wrote:
> On 09/26/2019 11:03
On Fri, 2019-09-27 at 10:26 +0200, Michal Konecny wrote:
> There is still possibility to use libraries.io
> instead of Anitya, but there are some issues:
> - lack of downstream mapping (this could be easily solved by some
> database with only downstream mapping)
> - lack of custom project additio
I am updating dogpile.cache to 0.8.0 on Rawhide, and it has switched
from BSD to MIT:
https://github.com/sqlalchemy/dogpile.cache/commit/474a9a329f86e4c2d1cdf6e35e346979c9dd07c6
https://src.fedoraproject.org/rpms/python-dogpile-cache/c/b6bac12befdace274a1c21a215fc2e9a1236da0a?branch=master
signa
On Fri, Sep 27, 2019 at 10:53:32AM -0400, Neal Gompa wrote:
> On Fri, Sep 27, 2019 at 8:30 AM Daniel P. Berrangé
> wrote:
> >
> > On Fri, Sep 27, 2019 at 01:26:09PM +0200, Jun Aruga wrote:
> > > > Does anyone know of, or have, any critical/important use cases that
> > > > would
> > > be disrupte
On Fri, Sep 27, 2019 at 9:54 AM Panu Matilainen wrote:
>
> On 9/26/19 10:05 PM, Jeremy Cline wrote:
> > On Thu, Sep 26, 2019 at 02:57:56PM -0400, Randy Barlow wrote:
> >> On Thu, 2019-09-26 at 14:49 +, Jeremy Cline wrote:
> >>> The combination of these two makes no sense to me. I do plenty of
On Fri, Sep 27, 2019 at 8:30 AM Daniel P. Berrangé wrote:
>
> On Fri, Sep 27, 2019 at 01:26:09PM +0200, Jun Aruga wrote:
> > > Does anyone know of, or have, any critical/important use cases that would
> > be disrupted by QEMU dropping 32-bit *host* support ? If so, let me know
> > here & I can for
Thanks for responding!
On Fri, Sep 27, 2019 at 8:54 AM Jun Aruga wrote:
> > I'm working on (learning modularity) and developing a module for my
> package and created a not-so-great (super long) branch name in the dist-git
> rpm and module repo before I realized that it would be the stream's name
No problem! Thanks for the quick resolution:-)
Jirka
On Fri, Sep 27, 2019 at 3:29 PM Hannes Frederic Sowa <
han...@stressinduktion.org> wrote:
> Hello,
>
> On Fri, Sep 27, 2019, at 11:21, Miro Hrončok wrote:
> > On 27. 09. 19 11:07, Jiri Hladky wrote:
> > > Hello Hannes,
> > >
> > > thanks for t
On Fri, 2019-09-27 at 00:20 +0200, Dan Čermák wrote:
> Randy Barlow writes:
>
> > This suggestion gives a nice clean place to write the bodhi update
> > description, right in git. The commit messages can remain the way they
> > are today: authored for the audience of spec file contributors.
> >
I will be updating plplot to 5.15.0 soon in rawhide. This is a soname
bump. I will rebuild the 3 dependent packages:
gdl
psfex
scamp
Test builds here
https://copr.fedorainfracloud.org/coprs/orion/plplot/builds/ mostly
worked (despite some copr infrastructure failures)
--
Orion Poplawski
M
On 9/26/19 10:05 PM, Jeremy Cline wrote:
On Thu, Sep 26, 2019 at 02:57:56PM -0400, Randy Barlow wrote:
On Thu, 2019-09-26 at 14:49 +, Jeremy Cline wrote:
The combination of these two makes no sense to me. I do plenty of
work
where I don't want to build it (specfile cleanup, patches,
configu
Hello,
On Fri, Sep 27, 2019, at 11:21, Miro Hrončok wrote:
> On 27. 09. 19 11:07, Jiri Hladky wrote:
> > Hello Hannes,
> >
> > thanks for the quick response! I'm happy to take over the datamash package.
> >
> > Could you please give the admin rights by going to
> > https://src.fedoraproject.org/
Hi everyone,
I’d like to introduce myself first, my name is Aoife Moloney and I recently
started with the Community Platform Engineering (CPE) team. My role within
this team is going to be a hybrid role of a Product Owner / Project Manager.
As part of that, I want to send a weekly update to the l
> I'm working on (learning modularity) and developing a module for my package
> and created a not-so-great (super long) branch name in the dist-git rpm and
> module repo before I realized that it would be the stream's name too.
I faced similar situation. Ruby module was released as
"private-jaru
On Fri, Sep 27, 2019 at 01:26:09PM +0200, Jun Aruga wrote:
> > Does anyone know of, or have, any critical/important use cases that would
> be disrupted by QEMU dropping 32-bit *host* support ? If so, let me know
> here & I can forward feedback on. Or feel free to go direct to QEMU thread
> upstream
> For example, how about releasing compat-qemu50 RPM if upstream will
> drop armv7 on qemu 6.x?
> It's like compat-openssl10 RPM for openssl (version 1.1) RPM.
>
> Maybe if some RPM packages need armv7 support, they can use
> compat-qemu50 conditionally in the spec file.
Sorry. Typo.
s/compat-qem
> Does anyone know of, or have, any critical/important use cases that would
be disrupted by QEMU dropping 32-bit *host* support ? If so, let me know
here & I can forward feedback on. Or feel free to go direct to QEMU thread
upstream.
I am not a real user of ARM 32-bit. I just checked information f
On Fri, Sep 27, 2019 at 12:40:42PM +0200, Martin Kolman wrote:
> On Thu, 2019-09-26 at 16:24 +0200, Pierre-Yves Chibon wrote:
> > On Thu, Sep 26, 2019 at 02:57:45PM +0100, Daniel P. Berrangé wrote:
> > > On Thu, Sep 26, 2019 at 11:36:10AM +0200, Pierre-Yves Chibon wrote:
> > > > Good Morning Everyo
On Thu, 2019-09-26 at 16:24 +0200, Pierre-Yves Chibon wrote:
> On Thu, Sep 26, 2019 at 02:57:45PM +0100, Daniel P. Berrangé wrote:
> > On Thu, Sep 26, 2019 at 11:36:10AM +0200, Pierre-Yves Chibon wrote:
> > > Good Morning Everyone,
> > >
> > > At Flock, a few of us met to discuss a future vision o
On Thu, 2019-09-26 at 18:26 +0200, Ben Rosser wrote:
> On Thu, Sep 26, 2019 at 5:29 PM Pierre-Yves Chibon
> wrote:
> > On Thu, Sep 26, 2019 at 04:46:32PM +0200, Ben Rosser wrote:
> > > On Thu, Sep 26, 2019 at 4:29 PM Pierre-Yves Chibon
> > > wrote:
> > > > There is a clear initial rejection of
On Fri, Sep 27, 2019 at 11:56 AM Miro Hrončok wrote:
> Yes. I've em-mailed you about the problem when it was happening, asking
> you to
> disable it, there was no reply and I managed to build it at the end.
>
>
So, I apologize. I missed your email.
___
On 27. 09. 19 11:50, Fabien Boucher wrote:
I remember that during the Python 3.8 rebuilds in the side tag, one package
had
this automated somehow already. I was bumping the release/changelog and
trying
to build it in the side tag at least 5 times, but I was building with
--backg
On Fri, Sep 27, 2019 at 12:03 AM Miro Hrončok wrote:
> I remember that during the Python 3.8 rebuilds in the side tag, one
> package had
> this automated somehow already. I was bumping the release/changelog and
> trying
> to build it in the side tag at least 5 times, but I was building with
> --b
On 27. 09. 19 11:07, Jiri Hladky wrote:
Hello Hannes,
thanks for the quick response! I'm happy to take over the datamash package.
Could you please give the admin rights by going to
https://src.fedoraproject.org/rpms/datamash
Settings -> Users & Groups -> Add User
Or even
Settings -> Give Pro
Hello Hannes,
thanks for the quick response! I'm happy to take over the datamash package.
Could you please give the admin rights by going to
https://src.fedoraproject.org/rpms/datamash
Settings -> Users & Groups -> Add User
Thanks a lot!
Jiri
On Fri, Sep 27, 2019 at 4:53 AM Hannes Frederic Sow
The upstream QEMU community is raising the possibility of deprecating,
and subsequently deleting, support for running emulation guests on
32-bit *hosts*. Running 32-bit guests would *not* be affected.
See this thread:
https://lists.gnu.org/archive/html/qemu-devel/2019-09/msg06168.html
IOW, if
On 2019-09-26, Pierre-Yves Chibon wrote:
> ○ Every changes to dist-git is done via pull-requests
Pull requests are great for proposing your changes to foreign packages.
It does not make sense when maintaining the code. Either when doing
a mass changes like rebuilding all Perl packages against a n
On 2019-09-26 20:35, Jeremy Cline wrote:
On Thu, Sep 26, 2019 at 09:08:16AM -0700, Adam Williamson wrote:
On Thu, 2019-09-26 at 15:46 +, Jeremy Cline wrote:
Ah right, that makes a lot of sense.
I can imagine automatically detecting the new upstream release, building
that, and presenting
50 matches
Mail list logo
