Il 16/02/23 22:30, Ben Cotton ha scritto:
> On Thu, Feb 16, 2023 at 3:45 PM Mattia Verga via devel
> wrote:
>> This user should not have been detected as inactive if the Bugzilla
>> check was run. @Ben, maybe you forgot to set the BZ_API_KEY before
>> running the script?
> I didn't forget, I
https://bugzilla.redhat.com/show_bug.cgi?id=2165792
Fedora Update System changed:
What|Removed |Added
Fixed In Version|perl-HTML-Parser-3.81-1.fc3 |perl-HTML-Parser-3.81-1.fc3
OLD: Fedora-38-20230216.n.0
NEW: Fedora-38-20230216.n.1
= SUMMARY =
Added images:2
Dropped images: 2
Added packages: 2
Dropped packages:0
Upgraded packages: 56
Downgraded packages: 0
Size of added packages: 1.32 MiB
Size of dropped packages:0 B
Size
OLD: Fedora-Rawhide-20230216.n.2
NEW: Fedora-Rawhide-20230216.n.3
= SUMMARY =
Added images:4
Dropped images: 3
Added packages: 124
Dropped packages:1
Upgraded packages: 60
Downgraded packages: 0
Size of added packages: 47.41 MiB
Size of dropped packages
Kenneth Goldman wrote:
> > -Original Message-
> > From: Miro Hrončok
> >
> > On 16. 02. 23 14:50, Kenneth Goldman wrote:
> > > Could not execute mockbuild: Could not query n-v-r of hello: 'utf-8'
> > > codec
> > can't decode byte 0x93 in position 259: invalid start byte
> >
> >
On Thu, Feb 16, 2023 at 3:45 PM Mattia Verga via devel
wrote:
>
> This user should not have been detected as inactive if the Bugzilla
> check was run. @Ben, maybe you forgot to set the BZ_API_KEY before
> running the script?
I didn't forget, I intentionally did not. I thought we had already
https://bugzilla.redhat.com/show_bug.cgi?id=2170647
Bug ID: 2170647
Summary: Please branch and build perl-Net-Telnet for EPEL 9
Product: Fedora EPEL
Version: epel9
Status: NEW
Component: perl-Net-Telnet
Assignee:
https://bugzilla.redhat.com/show_bug.cgi?id=2170646
Bug ID: 2170646
Summary: Please branch and build perl-Config-Grammar for EPEL 9
Product: Fedora EPEL
Version: epel9
Status: NEW
Component: perl-Config-Grammar
Assignee:
Il 16/02/23 20:26, Mattia Verga ha scritto:
> Il 16/02/23 18:36, Kevin Fenzi ha scritto:
>> On Thu, Feb 16, 2023 at 09:04:01AM -0500, Ben Cotton wrote:
>>> On Thu, Feb 16, 2023 at 6:29 AM Daniel P. Berrangé
>>> wrote:
I'm a little surprised that the pagure ticket doesn't have the
I think I followed all those steps - identifying the package, announcing that
I want to be the packager, making an account, etc.
What's next? Does someone approve me? Are there more steps? Other accounts
to make? Move a git repo somewhere?
> -Original Message-
> From: Petr Pisar
>
Il 16/02/23 18:36, Kevin Fenzi ha scritto:
> On Thu, Feb 16, 2023 at 09:04:01AM -0500, Ben Cotton wrote:
>> On Thu, Feb 16, 2023 at 6:29 AM Daniel P. Berrangé
>> wrote:
>>> I'm a little surprised that the pagure ticket doesn't have the
>>> maintainer to whom it refers added as a subscriber to
On 1/19/23 04:52, Michal Schorm wrote:
Hello,
While playing around with Sourcegraph, which indexed all Fedora
package repositories, I was able to craft a query listing all '%if'
conditionals referencing Fedora releases that reached EOL.
On Sat, Feb 11, 2023 at 2:40 AM Fabio Valentini wrote:
>
> Hello fellow Rustaceans and / or frustrated Rust packagers,
>
> My work on the "next generation" of Rust packaging tools has finally
> progressed to the point where it can be tested by actual people. :)
After a few more days of code
On Thu, Feb 16, 2023 at 06:30:39PM +0100, Jun Aruga (he / him) wrote:
> I reviviced a retired package (rpms/smide) by the process below.
> https://pagure.io/releng/issue/11281
>
> Then when I added a new commit to rebase on the rawhide branch, and
> build, I got the following error by `fedpkg
We expect to start rebuilds for
https://fedoraproject.org/wiki/Changes/F39Boost181
in the f39-boost side tag Monday 2022-02-20.
If your package depends on Boost, or just if you see a "Rebuilt for
Boost 1.81" commit pushed to your package's dist-git repo, please
coordinate with me about any
On Thu, Feb 16, 2023 at 09:04:01AM -0500, Ben Cotton wrote:
> On Thu, Feb 16, 2023 at 6:29 AM Daniel P. Berrangé
> wrote:
> >
> > I'm a little surprised that the pagure ticket doesn't have the
> > maintainer to whom it refers added as a subscriber to the ticket.
>
> As far as I know, you can't
I reviviced a retired package (rpms/smide) by the process below.
https://pagure.io/releng/issue/11281
Then when I added a new commit to rebase on the rawhide branch, and
build, I got the following error by `fedpkg build`. Do you know what's
wrong and what I need to do to fix the error?
This is not the case, pcs is a cluster configuration and management tool
written in Python and Ruby. But thank you for bringing it up, it is a valid
point. I read that part of the guidelines and decided that it is not
applicable, so I probably should have mentioned that in my original email.
On
> -Original Message-
> From: Miro Hrončok
> Sent: Thursday, February 16, 2023 8:56 AM
> To: Kenneth Goldman ;
> devel@lists.fedoraproject.org
> Subject: [EXTERNAL] Re: fedpkg: Failed to get repository name from Git url or
> pushurl - solved
>
> On 16. 02. 23 14:50, Kenneth Goldman
On 16/02/2023 14:42, Michal Pospíšil (he / him) wrote:
We are considering making pcs a noarch package because we will no longer
compile bundled dependencies in Fedora.
Header-only libraries must not be noarch:
On Thu, Feb 16, 2023 at 6:29 AM Daniel P. Berrangé wrote:
>
> I'm a little surprised that the pagure ticket doesn't have the
> maintainer to whom it refers added as a subscriber to the ticket.
As far as I know, you can't subscribe others to a ticket the way you
can add a CC in Bugzilla. We could
On Wed, Feb 15, 2023 at 5:20 PM Paul Wouters wrote:
>
> How many packages depend _only_ on people from this list? Eg are likely
> to be unmaintained ?
There's a command in the script that will check the impact, but I'm
going to hold off on running it for a bit. It takes a long time to
iterate
On 16. 02. 23 14:50, Kenneth Goldman wrote:
Could not execute mockbuild: Could not query n-v-r of hello: 'utf-8' codec
can't decode byte 0x93 in position 259: invalid start byte
That indicates it's not actually UTF-8.
--
Miro Hrončok
--
Phone: +420777974800
IRC: mhroncok
> -Original Message-
> From: Miro Hrončok
> Sent: Wednesday, February 15, 2023 5:19 PM
> To: Development discussions related to Fedora ;
> Kenneth Goldman
> Subject: [EXTERNAL] Re: fedpkg: Failed to get repository name from Git url or
> pushurl - solved
>
> On 15. 02. 23 22:48,
On 16. 02. 23 14:42, Michal Pospíšil (he / him) wrote:
We are considering making pcs a noarch package because we will no longer
compile bundled dependencies in Fedora. We found this issue about switching a
package from noarch to arch: https://pagure.io/packaging-committee/issue/117
On Wed, Feb 15, 2023 at 6:42 PM Ben Cotton wrote:
> https://fedoraproject.org/wiki/Changes/F39ModernizeTBB
>
> 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
We are considering making pcs a noarch package because we will no longer
compile bundled dependencies in Fedora. We found this issue about switching
a package from noarch to arch:
https://pagure.io/packaging-committee/issue/117
So, adding Obsoletes of all our arched versions should be enough? I
On Thu, 16 Feb 2023 at 08:25, Stephen Smoogen wrote:
>
>
> On Thu, 16 Feb 2023 at 05:56, Richard W.M. Jones
> wrote:
>
>> On Wed, Feb 15, 2023 at 02:02:54PM -0500, Ben Cotton wrote:
>> > In accordance with FESCo's Inactive Packager Policy[1], packagers that
>> > have been identified as inactive
On Thu, 16 Feb 2023 at 05:56, Richard W.M. Jones wrote:
> On Wed, Feb 15, 2023 at 02:02:54PM -0500, Ben Cotton wrote:
> > In accordance with FESCo's Inactive Packager Policy[1], packagers that
> > have been identified as inactive have a ticket in the
> > find-inactive-packagers repo[2]. One week
OLD: Fedora-38-20230215.n.0
NEW: Fedora-38-20230216.n.0
= SUMMARY =
Added images:2
Dropped images: 2
Added packages: 2
Dropped packages:0
Upgraded packages: 81
Downgraded packages: 0
Size of added packages: 8.46 MiB
Size of dropped packages:0 B
Size
Announcing the creation of a new nightly release validation test event
for Fedora 38 Branched 20230216.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
https://bugzilla.redhat.com/show_bug.cgi?id=2169177
Petr Pisar changed:
What|Removed |Added
Resolution|RAWHIDE |NEXTRELEASE
--
You are receiving this
https://bugzilla.redhat.com/show_bug.cgi?id=2169177
Petr Pisar changed:
What|Removed |Added
Status|ON_QA |CLOSED
Resolution|---
OLD: Fedora-Rawhide-20230213.n.0
NEW: Fedora-Rawhide-20230216.n.2
= SUMMARY =
Added images:1
Dropped images: 6
Added packages: 133
Dropped packages:0
Upgraded packages: 205
Downgraded packages: 1
Size of added packages: 1.73 GiB
Size of dropped packages:0
On Thu, Feb 16, 2023 at 10:55:55AM +, Richard W.M. Jones wrote:
> On Wed, Feb 15, 2023 at 02:02:54PM -0500, Ben Cotton wrote:
> > In accordance with FESCo's Inactive Packager Policy[1], packagers that
> > have been identified as inactive have a ticket in the
> > find-inactive-packagers
On Wed, Feb 15, 2023 at 02:02:54PM -0500, Ben Cotton wrote:
> In accordance with FESCo's Inactive Packager Policy[1], packagers that
> have been identified as inactive have a ticket in the
> find-inactive-packagers repo[2]. One week after the final release,
> packagers who remain inactive will be
Filled it in now :)
On 2/15/23, Ben Cotton wrote:
> In case you missed it on the Community Blog[1], the F37 retrospective
> survey[2] is open through 9 March. As a reminder, this survey is about
> the _process_ of creating F37, not the end result. This is the third
> such survey, so we'll be
Dne 16. 02. 23 v 1:08 Matthew Miller napsal(a):
On Thu, Feb 09, 2023 at 09:51:37AM -0800, Kevin Fenzi wrote:
Yep. Sigs exist because they say they do. ;)
The risc-v sig has been around for a while, but I guess a sig wiki page
was never made. :(
I like that we have low barriers to entry for
38 matches
Mail list logo
