https://bugzilla.redhat.com/show_bug.cgi?id=2160344
--- Comment #5 from Fedora Update System ---
FEDORA-2023-03d711e44f has been pushed to the Fedora 37 testing repository.
Soon you'll be able to install the update with the following command:
`sudo dnf upgrade --enablerepo=updates-testing
https://bugzilla.redhat.com/show_bug.cgi?id=2160344
Fedora Update System changed:
What|Removed |Added
Status|MODIFIED|ON_QA
--- Comment #4 from
https://bugzilla.redhat.com/show_bug.cgi?id=2158086
Fedora Update System changed:
What|Removed |Added
Status|ON_QA |CLOSED
Fixed In Version|
https://bugzilla.redhat.com/show_bug.cgi?id=2157630
Fedora Update System changed:
What|Removed |Added
Resolution|--- |ERRATA
Status|ON_QA
On Thu, Jan 12, 2023 at 7:14 PM Michael Cronenworth wrote:
>
> On 1/6/23 3:34 PM, Neal Gompa wrote:
> > * autotrace (contacting upstream planned)
>
> Any update on this one? It is blocking wine.
It looks like there's a proposed IM7 compatibility patch mentioned in
the pull request to fix the
On 1/6/23 3:34 PM, Neal Gompa wrote:
* autotrace (contacting upstream planned)
Any update on this one? It is blocking wine.
___
devel mailing list -- devel@lists.fedoraproject.org
To unsubscribe send an email to devel-le...@lists.fedoraproject.org
> Can take this if no-one else is interested (@Sergio Basto?)
>
> > docker-compose lsm5, orphan, ttomecek 1 weeks
> > ago
The Python docker-compose is deprecated upstream in favor of the Compose
V2 Docker CLI Plugin written in Go. The latter is not yet packaged for
It appears that all the dependent packages are now compatible (i.e., they
build).
The plan is to build them in a side tag over the next few days. The
dependencies are:
OpenImageIO
usd
blender
krita
luxcorerender
Thanks,
Richard
___
devel mailing list
On Thu, Jan 12, 2023 at 6:38 PM Jakub Jelinek wrote:
> But at least you don't need both -U_FORTIFY_SOURCE and
> -Wp,-U_FORTIFY_SOURCE, one of them is enough. And the latter I think
> better gets through libtool and other tools; especially if you put it
> into a single -Wp, option together with
On Thu, Jan 12, 2023 at 06:29:10PM -0500, Siddhesh Poyarekar wrote:
> On Thu, Jan 12, 2023 at 12:41 PM Jakub Jelinek wrote:
> > > I've filed a ccache bug. It looks like ccache is moving the compiler
> > > arguments around, causing one of the -U_FORTIFY_SOURCE to the end.
> > >
> > >
On Thu, Jan 12, 2023 at 07:57:28PM +0100, Miro Hrončok wrote:
> On 12. 01. 23 18:53, Susi Lehtola wrote:
> > On 1/12/23 19:48, Miro Hrončok wrote:
> >> On 12. 01. 23 18:42, Susi Lehtola wrote:
> >>> On 12/5/22 13:36, Miro Hrončok wrote:
> The following packages are orphaned and will be
On Thu, Jan 12, 2023 at 12:41 PM Jakub Jelinek wrote:
> > I've filed a ccache bug. It looks like ccache is moving the compiler
> > arguments around, causing one of the -U_FORTIFY_SOURCE to the end.
> >
> > https://bugzilla.redhat.com/show_bug.cgi?id=2160275
>
> Why we do have those
On Thu, Jan 12, 2023 at 10:19 PM David Woodhouse wrote:
> The English word for that is 'fortnightly', FWIW.
While that is Old English, and still commonly used
in parts of the world and in some formal language
usage, most people just use the words "every two
weeks" rather than asking people to
On Thu, Jan 12 2023 at 08:31:33 PM +, Jonathan Wakely
wrote:
IIUC the difficulty is finding out which ones are being slow, but that
could be solved by changing the signal to SIGABRT, right?
Well we still have to end with SIGKILL because SIGABRT is ignorable, so
the new proposed behavior
On Thu, 2023-01-12 at 14:08 -0800, Jilayne Lovejoy wrote:
> every two weeks was my understanding too, although I don't think
> Miro set up a recurring invite b/c we were also going to try to
> alternate the time of day to accommodate various time zones.
>
> Bi-weekly is ambiguous in English,
Fortnightly isn't ambiguous :-)
On Thu, 12 Jan 2023, 22:09 Jilayne Lovejoy, wrote:
> every two weeks was my understanding too, although I don't think Miro set
> up a recurring invite b/c we were also going to try to alternate the time
> of day to accommodate various time zones.
>
> Bi-weekly is
every two weeks was my understanding too, although I don't think Miro
set up a recurring invite b/c we were also going to try to alternate the
time of day to accommodate various time zones.
Bi-weekly is ambiguous in English, I've had this challenge before!
Jilayne
On 1/12/23 10:14 AM,
https://bugzilla.redhat.com/show_bug.cgi?id=2157099
Upstream Release Monitoring
changed:
What|Removed |Added
Summary|perl-DateTime-Format-Natura
On Thu, Jan 12, 2023 at 7:00 AM wrote:
>
> Dear all,
>
> You are kindly invited to the meeting:
>ELN SIG on 2023-01-13 from 12:00:00 to 13:00:00 US/Eastern
>At fedora-meet...@irc.libera.chat
>
> The meeting will be about:
We haven't met yet in 2023, so I'm going to hold a general "open
On Wed, 11 Jan 2023 at 16:36, Zbigniew Jędrzejewski-Szmek wrote:
>
> On Tue, Jan 10, 2023 at 06:16:07PM -0800, Kevin Fenzi wrote:
> > Ok, but it seems safer to just add timeouts to things that take too long
> > and can safely be killed off rather than lowering the timeout for
> > everything and
On 12. 01. 23 18:53, Susi Lehtola wrote:
On 1/12/23 19:48, Miro Hrončok wrote:
On 12. 01. 23 18:42, Susi Lehtola wrote:
On 12/5/22 13:36, 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
On Thu, Jan 12, 2023 at 07:14:33PM +0100, Jun Aruga (he / him) wrote:
> > > > 1.
> > > > https://lists.fedoraproject.org/archives/list/devel@lists.fedoraproject.org/thread/Z2RR2OE5TAQH5CVJ5VB5T3R7OM5ULYPQ/#QZUTH6DSULKYBMGPPYNZMPX7YSYKOBTT
> > > > 2.
> > > >
> > > 1.
> > > https://lists.fedoraproject.org/archives/list/devel@lists.fedoraproject.org/thread/Z2RR2OE5TAQH5CVJ5VB5T3R7OM5ULYPQ/#QZUTH6DSULKYBMGPPYNZMPX7YSYKOBTT
> > > 2.
> > >
On Thu, Jan 12, 2023 at 11:33 AM Miro Hrončok wrote:
> On 11. 01. 23 20:10, Miroslav Suchý wrote:
> > This is intended to be bi-weekly.
>
> Every two weeks or twice a week?
>
Since I was at a meeting yesterday where this was discussed I am pretty
sure the intention was every two weeks. Yes,
On 12. 01. 23 18:42, Susi Lehtola wrote:
On 12/5/22 13:36, 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
On 12/5/22 13:36, 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:
>
On Wed, Jan 11, 2023 at 06:44:22PM -0500, Siddhesh Poyarekar wrote:
> On Wed, Jan 11, 2023 at 4:43 PM Siddhesh Poyarekar
> wrote:
> > On Wed, Jan 11, 2023 at 4:37 PM Siddhesh Poyarekar
> > wrote:
> > >
> > > On Wed, Jan 11, 2023 at 3:05 PM Michel Alexandre Salim
> > > wrote:
> > > > Just
On Thu, Jan 12, 2023 at 11:41:20AM -0500, Stephen Smoogen wrote:
> On Thu, 12 Jan 2023 at 11:34, Jun Aruga (he / him)
> wrote:
>
> > I see one issue on HyperKitty on the Fedora project.
> >
> > Below is thread 1 and 2 for the actual thread: "RISC-V -- are we ready
> > for more, and what do we
As a reminder, the deadline for submitting Self-Contained F38 Change
proposals is Tuesday, 17 January 2023.
The F38 mass rebuild is scheduled to begin on Wednesday, 18 January.
Any approved Changes that require a mass rebuild must be ready by
then. If you will not be ready, please notify Release
As a reminder, the deadline for submitting Self-Contained F38 Change
proposals is Tuesday, 17 January 2023.
The F38 mass rebuild is scheduled to begin on Wednesday, 18 January.
Any approved Changes that require a mass rebuild must be ready by
then. If you will not be ready, please notify Release
https://fedoraproject.org/wiki/Changes/IPPUSBasPrintScanDependency
This document represents a proposed Change. As part of the Changes
process, proposals are publicly announced in order to receive
community feedback. This proposal will only be implemented if approved
by the Fedora Engineering
https://fedoraproject.org/wiki/Changes/IPPUSBasPrintScanDependency
This document represents a proposed Change. As part of the Changes
process, proposals are publicly announced in order to receive
community feedback. This proposal will only be implemented if approved
by the Fedora Engineering
On Thu, 12 Jan 2023 at 11:34, Jun Aruga (he / him)
wrote:
> I see one issue on HyperKitty on the Fedora project.
>
> Below is thread 1 and 2 for the actual thread: "RISC-V -- are we ready
> for more, and what do we need to do it?" Do you know why it's not one
> thread page?
>
> 1.
>
I see one issue on HyperKitty on the Fedora project.
Below is thread 1 and 2 for the actual thread: "RISC-V -- are we ready
for more, and what do we need to do it?" Do you know why it's not one
thread page?
1.
On 11. 01. 23 20:10, Miroslav Suchý wrote:
This is intended to be bi-weekly.
Every two weeks or twice a week?
--
Miro Hrončok
--
Phone: +420777974800
IRC: mhroncok
___
devel mailing list -- devel@lists.fedoraproject.org
To unsubscribe send an email
On Thu Jan 12, 2023 at 01:19 +0100, Sergio Pascual wrote:
> El vie, 30 dic 2022 a las 2:33, Maxwell G via devel (<
> devel@lists.fedoraproject.org>) escribió:
>
> > On Thu Dec 29, 2022, Maxwell G via devel wrote:
> > > On Thu Dec 29, 2022, Maxwell G via devel wrote:
> > > > On Wed Dec 28, 2022 at
Siddhesh Poyarekar wrote:
> That came up in yesterday's FESCO meeting, so hopefully at least that
> workflow hole will be plugged:
Still does not help the current case though, unfortunately.
Kevin Kofler
___
devel mailing list --
On Wed Jan 11, 2023 at 10:56 AM EST, Michael Catanzaro wrote:
> No. There are no Fedora Flatpaks on Flathub, and there are no filters
> to prevent users from installing Fedora Flatpaks.
Oh ok; I have no objection then. Apologies for the confusion.
Cheers,
--
DJ Chase
They, Them, Theirs
PS:
--
Gwyn Ciesla
she/her/hers
in your fear, seek only peace
in your fear, seek only love
-d. bowie
Sent with Proton Mail secure email.
--- Original Message ---
On Thursday, January 12th, 2023 at 8:40 AM, Stephen Smoogen
wrote:
>
On Thu, 12 Jan 2023 at 09:27, Jonathan Wright via devel <
devel@lists.fedoraproject.org> wrote:
> Just got the following error:
> https://pagure.io/releng/fedora-scm-requests/issue/50417
>
> I'm pretty sure I've always requested branches as someone with "commit"
> access and never had them
On Thu, Dec 22, 2022, at 12:35 PM, Ben Cotton wrote:
> https://fedoraproject.org/wiki/Changes/Shorter_Shutdown_Timer
>
> This document represents a proposed Change. As part of the Changes
> process, proposals are publicly announced in order to receive
> community feedback. This proposal will
Just got the following error:
https://pagure.io/releng/fedora-scm-requests/issue/50417
I'm pretty sure I've always requested branches as someone with "commit"
access and never had them rejected.
On Thu, Jan 12, 2023 at 3:30 AM Dominik 'Rathann' Mierzejewski <
domi...@greysector.net> wrote:
> On
https://bugzilla.redhat.com/show_bug.cgi?id=2159571
Jitka Plesnikova changed:
What|Removed |Added
Fixed In Version|perl-Email-MIME-Kit-3.0 |perl-Email-Stuffer-0.020-1.
jplesnik merged a pull-request against the project: `perl-Email-Stuffer` that
you are following.
Merged pull-request:
``
0.020 bump; Package tests
``
https://src.fedoraproject.org/rpms/perl-Email-Stuffer/pull-request/1
___
perl-devel mailing list --
https://bugzilla.redhat.com/show_bug.cgi?id=2159570
Jitka Plesnikova changed:
What|Removed |Added
Status|NEW |CLOSED
Fixed In Version|
jplesnik opened a new pull-request against the project: `perl-Email-Stuffer`
that you are following:
``
0.020 bump; Package tests
``
To reply, visit the link below
https://src.fedoraproject.org/rpms/perl-Email-Stuffer/pull-request/1
___
perl-devel
Hi Dominik,
Thank you for your response, that is very enlightening and helps a lot.
I'm referring to the browser exploitation framework, hence BeEF.
https://github.com/beefproject/beef
Hence me being unsure if this is something likely to be accepted.
I will follow up the maintainer route and
https://bugzilla.redhat.com/show_bug.cgi?id=2160344
--- Comment #3 from Fedora Update System ---
FEDORA-2023-be647b4bac has been submitted as an update to Fedora 36.
https://bodhi.fedoraproject.org/updates/FEDORA-2023-be647b4bac
--
You are receiving this mail because:
You are on the CC list
https://bugzilla.redhat.com/show_bug.cgi?id=2160344
--- Comment #2 from Fedora Update System ---
FEDORA-2023-03d711e44f has been submitted as an update to Fedora 37.
https://bodhi.fedoraproject.org/updates/FEDORA-2023-03d711e44f
--
You are receiving this mail because:
You are on the CC list
https://bugzilla.redhat.com/show_bug.cgi?id=2159571
Jitka Plesnikova changed:
What|Removed |Added
Status|ASSIGNED|CLOSED
Resolution|---
jplesnik merged a pull-request against the project: `perl-Email-MIME-Kit` that
you are following.
Merged pull-request:
``
3.07 bump; Package tests
``
https://src.fedoraproject.org/rpms/perl-Email-MIME-Kit/pull-request/1
___
perl-devel mailing
OLD: Fedora-Rawhide-20230111.n.0
NEW: Fedora-Rawhide-20230112.n.0
= SUMMARY =
Added images:0
Dropped images: 4
Added packages: 6
Dropped packages:3
Upgraded packages: 109
Downgraded packages: 0
Size of added packages: 5.70 MiB
Size of dropped packages
https://bugzilla.redhat.com/show_bug.cgi?id=2159571
Jitka Plesnikova changed:
What|Removed |Added
CC|jples...@redhat.com |
Doc Type|---
https://bugzilla.redhat.com/show_bug.cgi?id=2160344
Petr Pisar changed:
What|Removed |Added
Status|ASSIGNED|MODIFIED
Fixed In Version|
jplesnik opened a new pull-request against the project: `perl-Email-MIME-Kit`
that you are following:
``
3.07 bump; Package tests
``
To reply, visit the link below
https://src.fedoraproject.org/rpms/perl-Email-MIME-Kit/pull-request/1
___
https://bugzilla.redhat.com/show_bug.cgi?id=2160344
Petr Pisar changed:
What|Removed |Added
CC|ppi...@redhat.com |
Doc Type|---
https://bugzilla.redhat.com/show_bug.cgi?id=2160317
Petr Pisar changed:
What|Removed |Added
Status|ON_QA |CLOSED
Resolution|---
Dear all,
You are kindly invited to the meeting:
ELN SIG on 2023-01-13 from 12:00:00 to 13:00:00 US/Eastern
At fedora-meet...@irc.libera.chat
The meeting will be about:
Source: https://calendar.fedoraproject.org//meeting/10133/
___
devel
https://bugzilla.redhat.com/show_bug.cgi?id=2160317
Petr Pisar changed:
What|Removed |Added
Status|ASSIGNED|MODIFIED
Fixed In Version|
https://bugzilla.redhat.com/show_bug.cgi?id=2160317
Petr Pisar changed:
What|Removed |Added
Status|NEW |ASSIGNED
Doc Type|---
On Mon, Jan 9, 2023 at 4:30 PM Kalev Lember wrote:
> On Thu, Jan 5, 2023 at 10:55 AM Kalev Lember
> wrote:
>
>> Hi all,
>>
>> Hopefully most people are back from vacations now so I think we can go on
>> with organizing the first Flatpak SIG meeting.
>>
>> I have created a whenisgood poll for
On Wednesday, 11 January 2023 at 17:13, Michal Konecny wrote:
> Hi everyone,
>
> all the remaining issues were solved and the bot is now processing
> tickets as it should. I will watch the SCM request repository for next
> few days to see if everything is working as it should.
> Thanks for your
Hello, Josh.
On Thursday, 12 January 2023 at 06:34, josh crew wrote:
> Hi there, I want to ask about adding a package to DNF, if it would be
> accepted, how i may go about doing/helping with it.
To make a package available for installation with dnf from package
repositories provided by Fedora,
The idea of faking this and that (timestamps, builder hostname, ...
whatever) is weird.
It always leads to a question: why do we even have / use such
metadata, if we fake them anyway?
Only either ditching such values entirely or always honoring them does
make sense to me.
Or inventing new ones
On Wed, Jan 11, 2023 at 5:46 PM Michel Alexandre Salim <
sali...@fedoraproject.org> wrote:
> On Wed, Jan 11, 2023 at 01:58:51PM +0100, Miro Hrončok wrote:
> > Dear maintainers.
> >
> > Based on the current fail to build from source policy, the following
> packages
> > should be retired from
65 matches
Mail list logo
