Re: Fw: [Bug 2066129] mingw-libgsf-1_14_52 is available

2024-02-16 Thread Daniel P . Berrangé
On Fri, Feb 09, 2024 at 11:12:42PM -0600, Greg Hellings wrote:
> Looks like I'm not allowed to retire on the f39 branch. It was already
> retired in Rawhide before I could get there.
> 
> $ fedpkg retire "MinGW support merged to native package in Fedora 39
> release"
> Fedora release (f39) is in state 'current' - retire operation is not
> allowed.

Oh well, it should be harmless as long as no one ever updates that
branch with new versions, nor does any new builds from that branch.
The NEVR from the native package should be newer and thus the mingw
sub-RPMs from the native build are what should get into the yum repos.

With regards,
Daniel
-- 
|: https://berrange.com  -o-https://www.flickr.com/photos/dberrange :|
|: https://libvirt.org -o-https://fstop138.berrange.com :|
|: https://entangle-photo.org-o-https://www.instagram.com/dberrange :|
--
___
devel mailing list -- devel@lists.fedoraproject.org
To unsubscribe send an email to devel-le...@lists.fedoraproject.org
Fedora Code of Conduct: 
https://docs.fedoraproject.org/en-US/project/code-of-conduct/
List Guidelines: https://fedoraproject.org/wiki/Mailing_list_guidelines
List Archives: 
https://lists.fedoraproject.org/archives/list/devel@lists.fedoraproject.org
Do not reply to spam, report it: 
https://pagure.io/fedora-infrastructure/new_issue


Re: Fw: [Bug 2066129] mingw-libgsf-1_14_52 is available

2024-02-06 Thread Fabio Valentini
On Tue, Feb 6, 2024 at 1:42 PM Dan Horák  wrote:
>
> On Tue, 6 Feb 2024 13:11:55 +0100
> Sandro Mani  wrote:
>
> >
> > On 06.02.24 8:50 AM, Marc-André Lureau wrote:
> > > Hi
> > >
> > > On Mon, Feb 5, 2024 at 8:52 PM Daniel P. Berrangé  
> > > wrote:
> > >> On Mon, Feb 05, 2024 at 05:34:06PM +0100, Dan Horák wrote:
> > >>> Hi,
> > >>>
> > >>> could someone in the mingw team look at mingw-libgsf / libgsf (please
> > >>> see the bug forwarded below)? If I see right, then the standalone
> > >>> mingw-libgsf package should be retired as there are mingw builds from
> > >>> the regular libgsf package, which seems to be regularly updated.
> > >> Copying Marc-André who added the mingw sub-RPMs to the native
> > >> package.
> > >>
> > >> The mingw-libgsf should have been retired on rawhide, as soon
> > >> as the libgsf native had a successful build with mingw packages.
> > >>
> > >> At this point I guess it'll need retiring on both rawhide
> > >> and f39
> > > Correct, I missed that. Geg, Sandro, can you retire the mingw-libgsf 
> > > package?
> > >
> > I've retired the package, but not sure if it worked 100% as I'm not
> > listed as package admin.
>
> I suspect it hasn't finished the retiring, mingw-libgfs is still active
> in koji and in pagure ... Likely it needs either Greg (who seems to be
> inactive) or a releng ticket.

No, processing package retirements happens during the compose process,
so it takes up to 24 hours.

Fabio
--
___
devel mailing list -- devel@lists.fedoraproject.org
To unsubscribe send an email to devel-le...@lists.fedoraproject.org
Fedora Code of Conduct: 
https://docs.fedoraproject.org/en-US/project/code-of-conduct/
List Guidelines: https://fedoraproject.org/wiki/Mailing_list_guidelines
List Archives: 
https://lists.fedoraproject.org/archives/list/devel@lists.fedoraproject.org
Do not reply to spam, report it: 
https://pagure.io/fedora-infrastructure/new_issue


Re: Fw: [Bug 2066129] mingw-libgsf-1_14_52 is available

2024-02-06 Thread Daniel P . Berrangé
On Tue, Feb 06, 2024 at 08:27:33AM -0600, Greg Hellings wrote:
> I'm happy to pass the project off to whomever needs it, if you give me the
> user name and a quick reference. Or retire it, if you have a link with
> instructions on how to do that.

It should not require more than  the first step in the docs[1]

  fedpkg retire "Merged mingw support into native package"

un in the 'rawhide' branch of dist-git for mingw-libgsf
and then push.

Normally you would never retire in a fedora release branch, but that's
ok in this place as the content isn't going away, it just moved to the
native package. So I think its ok to run fedpkg retire in the f39
branch too, unless something blocks that.

Blocking from koji isn't needed, as the sub-RPMs from the native build
should be newer and thus take priority in the compose too.

With regards,
Daniel

[1] 
https://docs.fedoraproject.org/en-US/package-maintainers/Package_Retirement_Process/
-- 
|: https://berrange.com  -o-https://www.flickr.com/photos/dberrange :|
|: https://libvirt.org -o-https://fstop138.berrange.com :|
|: https://entangle-photo.org-o-https://www.instagram.com/dberrange :|
--
___
devel mailing list -- devel@lists.fedoraproject.org
To unsubscribe send an email to devel-le...@lists.fedoraproject.org
Fedora Code of Conduct: 
https://docs.fedoraproject.org/en-US/project/code-of-conduct/
List Guidelines: https://fedoraproject.org/wiki/Mailing_list_guidelines
List Archives: 
https://lists.fedoraproject.org/archives/list/devel@lists.fedoraproject.org
Do not reply to spam, report it: 
https://pagure.io/fedora-infrastructure/new_issue


Re: Fw: [Bug 2066129] mingw-libgsf-1_14_52 is available

2024-02-06 Thread Dan Horák
On Tue, 6 Feb 2024 13:11:55 +0100
Sandro Mani  wrote:

> 
> On 06.02.24 8:50 AM, Marc-André Lureau wrote:
> > Hi
> >
> > On Mon, Feb 5, 2024 at 8:52 PM Daniel P. Berrangé  
> > wrote:
> >> On Mon, Feb 05, 2024 at 05:34:06PM +0100, Dan Horák wrote:
> >>> Hi,
> >>>
> >>> could someone in the mingw team look at mingw-libgsf / libgsf (please
> >>> see the bug forwarded below)? If I see right, then the standalone
> >>> mingw-libgsf package should be retired as there are mingw builds from
> >>> the regular libgsf package, which seems to be regularly updated.
> >> Copying Marc-André who added the mingw sub-RPMs to the native
> >> package.
> >>
> >> The mingw-libgsf should have been retired on rawhide, as soon
> >> as the libgsf native had a successful build with mingw packages.
> >>
> >> At this point I guess it'll need retiring on both rawhide
> >> and f39
> > Correct, I missed that. Geg, Sandro, can you retire the mingw-libgsf 
> > package?
> >
> I've retired the package, but not sure if it worked 100% as I'm not 
> listed as package admin.

I suspect it hasn't finished the retiring, mingw-libgfs is still active
in koji and in pagure ... Likely it needs either Greg (who seems to be
inactive) or a releng ticket.


Dan
--
___
devel mailing list -- devel@lists.fedoraproject.org
To unsubscribe send an email to devel-le...@lists.fedoraproject.org
Fedora Code of Conduct: 
https://docs.fedoraproject.org/en-US/project/code-of-conduct/
List Guidelines: https://fedoraproject.org/wiki/Mailing_list_guidelines
List Archives: 
https://lists.fedoraproject.org/archives/list/devel@lists.fedoraproject.org
Do not reply to spam, report it: 
https://pagure.io/fedora-infrastructure/new_issue


Re: Fw: [Bug 2066129] mingw-libgsf-1_14_52 is available

2024-02-06 Thread Sandro Mani


On 06.02.24 8:50 AM, Marc-André Lureau wrote:

Hi

On Mon, Feb 5, 2024 at 8:52 PM Daniel P. Berrangé  wrote:

On Mon, Feb 05, 2024 at 05:34:06PM +0100, Dan Horák wrote:

Hi,

could someone in the mingw team look at mingw-libgsf / libgsf (please
see the bug forwarded below)? If I see right, then the standalone
mingw-libgsf package should be retired as there are mingw builds from
the regular libgsf package, which seems to be regularly updated.

Copying Marc-André who added the mingw sub-RPMs to the native
package.

The mingw-libgsf should have been retired on rawhide, as soon
as the libgsf native had a successful build with mingw packages.

At this point I guess it'll need retiring on both rawhide
and f39

Correct, I missed that. Geg, Sandro, can you retire the mingw-libgsf package?

I've retired the package, but not sure if it worked 100% as I'm not 
listed as package admin.


Sandro
--
___
devel mailing list -- devel@lists.fedoraproject.org
To unsubscribe send an email to devel-le...@lists.fedoraproject.org
Fedora Code of Conduct: 
https://docs.fedoraproject.org/en-US/project/code-of-conduct/
List Guidelines: https://fedoraproject.org/wiki/Mailing_list_guidelines
List Archives: 
https://lists.fedoraproject.org/archives/list/devel@lists.fedoraproject.org
Do not reply to spam, report it: 
https://pagure.io/fedora-infrastructure/new_issue


Re: Fw: [Bug 2066129] mingw-libgsf-1_14_52 is available

2024-02-05 Thread Daniel P . Berrangé
On Mon, Feb 05, 2024 at 05:34:06PM +0100, Dan Horák wrote:
> Hi,
> 
> could someone in the mingw team look at mingw-libgsf / libgsf (please
> see the bug forwarded below)? If I see right, then the standalone
> mingw-libgsf package should be retired as there are mingw builds from
> the regular libgsf package, which seems to be regularly updated.

Copying Marc-André who added the mingw sub-RPMs to the native
package.

The mingw-libgsf should have been retired on rawhide, as soon
as the libgsf native had a successful build with mingw packages.

At this point I guess it'll need retiring on both rawhide
and f39

> 
> 
>   Thanks,
> 
>   Dan
> 
> 
> 
> Begin forwarded message:
> 
> Date: Mon, 05 Feb 2024 00:09:44 +
> From: bugzi...@redhat.com
> Subject: [Bug 2066129] mingw-libgsf-1_14_52 is available
> 
> 
> https://bugzilla.redhat.com/show_bug.cgi?id=2066129
> 
> Upstream Release Monitoring
>  changed:
> 
>What|Removed |Added
> 
> Summary|mingw-libgsf-1_14_51 is |mingw-libgsf-1_14_52 is
>|available   |available
> 
> 
> 
> --- Comment #8 from Upstream Release Monitoring
>  --- Releases retrieved:
> 1_14_52 Upstream release that is considered latest: 1_14_52
> Current version/release in rawhide: 1.14.48-7.fc40
> URL: http://www.gnome.org/projects/libgsf/
> 
> Please consult the package updates policy before you issue an update to
> a stable branch:
> https://docs.fedoraproject.org/en-US/fesco/Updates_Policy/
> 
> 
> More information about the service that created this bug can be found
> at:
> https://docs.fedoraproject.org/en-US/package-maintainers/Upstream_Release_Monitoring
> 
> 
> Please keep in mind that with any upstream change, there may also be
> packaging changes that need to be made. Specifically, please remember
> that it is your responsibility to review the new version to ensure that
> the licensing is still correct and that no non-free or legally
> problematic items have been added upstream.
> 
> 
> Based on the information from Anitya:
> https://release-monitoring.org/project/1980/
> 
> 
> To change the monitoring settings for the project, please visit:
> https://src.fedoraproject.org/rpms/mingw-libgsf
> 
> 
> -- 
> You are receiving this mail because:
> You are on the CC list for the bug.
> https://bugzilla.redhat.com/show_bug.cgi?id=2066129
> 
> Report this comment as SPAM:
> https://bugzilla.redhat.com/enter_bug.cgi?product=Bugzilla&format=report-spam&short_desc=Report%20of%20Bug%202066129%23c8
> --
> ___
> devel mailing list -- devel@lists.fedoraproject.org
> To unsubscribe send an email to devel-le...@lists.fedoraproject.org
> Fedora Code of Conduct: 
> https://docs.fedoraproject.org/en-US/project/code-of-conduct/
> List Guidelines: https://fedoraproject.org/wiki/Mailing_list_guidelines
> List Archives: 
> https://lists.fedoraproject.org/archives/list/devel@lists.fedoraproject.org
> Do not reply to spam, report it: 
> https://pagure.io/fedora-infrastructure/new_issue

With regards,
Daniel
-- 
|: https://berrange.com  -o-https://www.flickr.com/photos/dberrange :|
|: https://libvirt.org -o-https://fstop138.berrange.com :|
|: https://entangle-photo.org-o-https://www.instagram.com/dberrange :|
--
___
devel mailing list -- devel@lists.fedoraproject.org
To unsubscribe send an email to devel-le...@lists.fedoraproject.org
Fedora Code of Conduct: 
https://docs.fedoraproject.org/en-US/project/code-of-conduct/
List Guidelines: https://fedoraproject.org/wiki/Mailing_list_guidelines
List Archives: 
https://lists.fedoraproject.org/archives/list/devel@lists.fedoraproject.org
Do not reply to spam, report it: 
https://pagure.io/fedora-infrastructure/new_issue


Fw: [Bug 2066129] mingw-libgsf-1_14_52 is available

2024-02-05 Thread Dan Horák
Hi,

could someone in the mingw team look at mingw-libgsf / libgsf (please
see the bug forwarded below)? If I see right, then the standalone
mingw-libgsf package should be retired as there are mingw builds from
the regular libgsf package, which seems to be regularly updated.


Thanks,

Dan



Begin forwarded message:

Date: Mon, 05 Feb 2024 00:09:44 +
From: bugzi...@redhat.com
Subject: [Bug 2066129] mingw-libgsf-1_14_52 is available


https://bugzilla.redhat.com/show_bug.cgi?id=2066129

Upstream Release Monitoring
 changed:

   What|Removed |Added

Summary|mingw-libgsf-1_14_51 is |mingw-libgsf-1_14_52 is
   |available   |available



--- Comment #8 from Upstream Release Monitoring
 --- Releases retrieved:
1_14_52 Upstream release that is considered latest: 1_14_52
Current version/release in rawhide: 1.14.48-7.fc40
URL: http://www.gnome.org/projects/libgsf/

Please consult the package updates policy before you issue an update to
a stable branch:
https://docs.fedoraproject.org/en-US/fesco/Updates_Policy/


More information about the service that created this bug can be found
at:
https://docs.fedoraproject.org/en-US/package-maintainers/Upstream_Release_Monitoring


Please keep in mind that with any upstream change, there may also be
packaging changes that need to be made. Specifically, please remember
that it is your responsibility to review the new version to ensure that
the licensing is still correct and that no non-free or legally
problematic items have been added upstream.


Based on the information from Anitya:
https://release-monitoring.org/project/1980/


To change the monitoring settings for the project, please visit:
https://src.fedoraproject.org/rpms/mingw-libgsf


-- 
You are receiving this mail because:
You are on the CC list for the bug.
https://bugzilla.redhat.com/show_bug.cgi?id=2066129

Report this comment as SPAM:
https://bugzilla.redhat.com/enter_bug.cgi?product=Bugzilla&format=report-spam&short_desc=Report%20of%20Bug%202066129%23c8
--
___
devel mailing list -- devel@lists.fedoraproject.org
To unsubscribe send an email to devel-le...@lists.fedoraproject.org
Fedora Code of Conduct: 
https://docs.fedoraproject.org/en-US/project/code-of-conduct/
List Guidelines: https://fedoraproject.org/wiki/Mailing_list_guidelines
List Archives: 
https://lists.fedoraproject.org/archives/list/devel@lists.fedoraproject.org
Do not reply to spam, report it: 
https://pagure.io/fedora-infrastructure/new_issue