Re: List of long term FTBFS packages to be retired in August

2023-08-01 Thread Andrew Bauer
Perfect. Thank you.
___
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: List of long term FTBFS packages to be retired in August

2023-08-01 Thread Fabio Valentini
On Tue, Aug 1, 2023 at 4:47 PM Andrew Bauer
 wrote:
>
> I appreciate the response. Would you mind pointing me to Miro's latest FTBS 
> announcement?
>
> This list was emailed to me again on July 25, and it still identified a 
> problem with xmvn-connector-ivy.

It was sent to the mailing lists (and affected maintainers) again yesterday:
https://lists.fedoraproject.org/archives/list/devel@lists.fedoraproject.org/thread/JW7LL42NOM7I4TVN3RPIE65ZUYUYLO25/

You are no longer affected, so you no longer received a direct copy.
(Though you should likely subscribe to at least the devel-announce
mailing list to not miss other important announcements.)

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: List of long term FTBFS packages to be retired in August

2023-08-01 Thread Andrew Bauer
I appreciate the response. Would you mind pointing me to Miro's latest FTBS 
announcement?

This list was emailed to me again on July 25, and it still identified a problem 
with xmvn-connector-ivy. 

___
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: List of long term FTBFS packages to be retired in August

2023-08-01 Thread David Schwörer
> However, xmvn-connector-ivy mock builds in rawhide just fine. 

Note that this is an old mail from Miro, in his most recent FTBFS announcement 
the package isn't listed anymore as it has been fixed in the mean time.
Before that, there was no successful build since f36.

Hope that helps
___
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: List of long term FTBFS packages to be retired in August

2023-08-01 Thread Andrew Bauer
After reading through this list multiple times, I am having trouble 
understanding if there is anything that needs to be done in my case.

This list flags the package I maintain, combozola:
>cambozola (maintained by: kni)
>   cambozola-0.936-20.fc38.noarch requires jpackage-utils
>  cambozola-0.936-20.fc38.src requires jpackage-utils
> cambozola-javadoc-0.936-20.fc38.noarch requires jpackage-utils

jpackage-utils is provided by javapackages-tools:
>$ dnf whatprovides jpackage-utils
>Last metadata expiration check: 7 days, 0:01:58 ago on Tue 25 Jul 2023 
>08:09:42 AM CDT.
>javapackages-tools-6.1.0-7.fc38.noarch : Macros and scripts for Java packaging
>   : support
>Repo: @System
>Matched from:
>Provide: jpackage-utils = 6.1.0-7.fc38
>
>javapackages-tools-6.1.0-7.fc38.noarch : Macros and scripts for Java packaging
>   : support
>Repo: fedora
>Matched from:
>Provide: jpackage-utils = 6.1.0-7.fc38

javapackages-tools is flagged on this list due to an issue with 
xmvn-connector-ivy:
>javapackages-tools
>xmvn-connector-ivy (maintained by: mizdebsk)
>xmvn-connector-ivy-4.0.0~20210707.d300ce6-3.fc36.noarch 
> requires

However, xmvn-connector-ivy mock builds in rawhide just fine. 

This is where I get stuck.
What is the issue here and what can I do about it?
___
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: List of long term FTBFS packages to be retired in August

2023-07-29 Thread Zbigniew Jędrzejewski-Szmek
On Tue, Jul 25, 2023 at 02:24:46PM +0200, Miro Hrončok wrote:
> jblas zbyszek
> xml-maven-plugin  mbooth, mizdebsk

I built those two now.

Zbyszek
___
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: List of long term FTBFS packages to be retired in August

2023-07-29 Thread Zbigniew Jędrzejewski-Szmek
On Thu, Jul 27, 2023 at 05:39:20PM +0900, Mamoru TASAKA wrote:
> > nom-tam-fits  gil, lupinix, zbyszek

Thanks!

> > telepathy-qt  jgrulich, jreznik, kde-sig, 
> > rdieter
> 
> Rescued these 2 packages (fixed FTBFS).
> Regards,
> Mamoru
___
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: List of long term FTBFS packages to be retired in August

2023-07-29 Thread Zbigniew Jędrzejewski-Szmek
On Wed, Jul 26, 2023 at 11:44:09AM -0700, Kevin Fenzi wrote:
> On Tue, Jul 25, 2023 at 06:45:41PM +0200, Miro Hrončok wrote:
> > Should I open a releng ticket to include this package in the next mass 
> > rebuild?
> 
> I suppose we could rebuild it, I don't think that would matter any?
> Or would it? Florian?

Yes, please rebuild it. It doesn't matter that it's not shipped
itself. It's still code that is used in other places and shipped.

(And also: no, we really don't need yet another exception.)

Zbyszek
___
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: List of long term FTBFS packages to be retired in August

2023-07-27 Thread Mamoru TASAKA

Miro Hrončok wrote on 2023/07/25 21:24:

Dear maintainers.

Based on the current fail to build from source policy, the following packages
should be retired from Fedora 39 approximately one week before branching.

5 weekly reminders are required, hence the retirement will happen
approximately in 2 weeks, i.e. around 2023-08-01.

Policy: 
https://docs.fedoraproject.org/en-US/fesco/Fails_to_build_from_source_Fails_to_install/

The packages in rawhide were not successfully built at least since Fedora 36.

This report is based on dist tags.

Packages collected via:
https://github.com/hroncok/fedora-report-ftbfs-retirements/blob/master/ftbfs-retirements.ipynb

If you see a package that was built, please let me know.
If you see a package that should be exempted from the process,
please let me know and we can work together to get a FESCo approval for that.

If you see a package that can be rebuilt, please do so.

     Package   (co)maintainers

nom-tam-fits  gil, lupinix, zbyszek
telepathy-qt  jgrulich, jreznik, kde-sig, rdieter


Rescued these 2 packages (fixed FTBFS).

Regards,
Mamoru
___
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: List of long term FTBFS packages to be retired in August

2023-07-26 Thread Kevin Fenzi
On Tue, Jul 25, 2023 at 06:45:41PM +0200, Miro Hrončok wrote:
> IMHO it is what the policy says, quite explicitly:
> 
> From 
> https://docs.fedoraproject.org/en-US/fesco/Fails_to_build_from_source_Fails_to_install/#_package_removal_for_long_standing_ftbfs_and_fti_bugs
> 
> """
> Cca six weeks before the Fedora N mass branching, packages that weren’t
> successfully rebuilt at least in Fedora N-2 are collected and weekly
> reminders are sent to affected maintainers and the Fedora devel mailing
> list.
> 
> Cca a week before the Fedora N mass branching, packages that weren’t
> successfully rebuilt at least in Fedora N-2 will be retired assuming there
> have been at least 5 warnings on the devel mailing list. The bug status has
> no effect on this retirement. This can be requested via a releng issue.
> """
> 
> When I included glibc32 in the list, it wasn't successfully rebuilt at least
> in Fedora 37.
> 
> We could argue what "successfully rebuilt" actually means, but when I wrote
> that policy, the spirit was "an actual built shipped to Fedora users" rather
> than "a Koschei rebuild".

Sure, but glibc32 is in fact never shipped to Fedora users. :)

We explicily block it in pungi so it never goes out.
It's a buildsystem implementation detail.

> I see you rebuilt it now, thanks.
> 
> Should I open a releng ticket to include this package in the next mass 
> rebuild?

I suppose we could rebuild it, I don't think that would matter any?
Or would it? Florian?

kevin


signature.asc
Description: PGP signature
___
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: List of long term FTBFS packages to be retired in August

2023-07-25 Thread Miro Hrončok

On 25. 07. 23 17:49, Florian Weimer wrote:

* Miro Hrončok:


On 25. 07. 23 16:42, Florian Weimer wrote:

* Miro Hrončok:


glibc32   codonell, fweimer, jakub, mcermak

Is this about FTBFS issues?  There isn't any recent build failure in
Koji, so I don't get why it's on this list?


The build currently in Rawhide was done on Fedora 36 which is end of life.

Apparently the release engineering team has not rebuilt this package
in a mass rebuild at least since Fedora 35.

To remove it from the list, build the package on Rawhide please.


That's not what the subject line and the policy say, though.  The policy
requires failing builds and FTBFS bugs in Bugzilla.

Please update the policy if you think this is no longer appropriate.


IMHO it is what the policy says, quite explicitly:

From 
https://docs.fedoraproject.org/en-US/fesco/Fails_to_build_from_source_Fails_to_install/#_package_removal_for_long_standing_ftbfs_and_fti_bugs


"""
Cca six weeks before the Fedora N mass branching, packages that weren’t 
successfully rebuilt at least in Fedora N-2 are collected and weekly reminders 
are sent to affected maintainers and the Fedora devel mailing list.


Cca a week before the Fedora N mass branching, packages that weren’t 
successfully rebuilt at least in Fedora N-2 will be retired assuming there have 
been at least 5 warnings on the devel mailing list. The bug status has no 
effect on this retirement. This can be requested via a releng issue.

"""

When I included glibc32 in the list, it wasn't successfully rebuilt at least in 
Fedora 37.


We could argue what "successfully rebuilt" actually means, but when I wrote 
that policy, the spirit was "an actual built shipped to Fedora users" rather 
than "a Koschei rebuild".




I see you rebuilt it now, thanks.

Should I open a releng ticket to include this package in the next mass rebuild?


--
Miro Hrončok
--
Phone: +420777974800
IRC: mhroncok
___
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: List of long term FTBFS packages to be retired in August

2023-07-25 Thread Florian Weimer
* Peter Robinson:

>> Are bootloaders fully treated as firmware and no longer built by Fedora?
>> At least the shim package does not come with corresponding source code
>> AFAICS.  But I expect that there are other 32-bit pre-boot packages that
>> we still rebuild.
>
> There's shim-unsigned* which is built in Fedora, the output of those
> are sent off to be signed and then the signed binaries are put into
> the final shim packages which don't have source code but they are
> still built on Fedora with the source, just in a two step process due
> to the out of band signing.

I think it's more complicated than that because the shim package can be
cobbled together from multiple different shim-unsigned package versions.

Anyway, I think Fedora strives to be better than “you can find sources
somewhere else if you just look hard enough”.  Can't you automatically
include all relevant SRPMs in the shim SRPM?

Thanks,
Florian
___
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: List of long term FTBFS packages to be retired in August

2023-07-25 Thread Stephen Smoogen
On Tue, 25 Jul 2023 at 11:54, Josh Boyer  wrote:

> On Tue, Jul 25, 2023 at 11:44 AM Florian Weimer 
> wrote:
> >
> > * Josh Boyer:
> >
> > > On Tue, Jul 25, 2023 at 10:53 AM Miro Hrončok 
> wrote:
> > >>
> > >> On 25. 07. 23 16:42, Florian Weimer wrote:
> > >> > * Miro Hrončok:
> > >> >
> > >> >> glibc32   codonell, fweimer,
> jakub, mcermak
> > >> >
> > >> > Is this about FTBFS issues?  There isn't any recent build failure in
> > >> > Koji, so I don't get why it's on this list?
> > >>
> > >> The build currently in Rawhide was done on Fedora 36 which is end of
> life.
> > >>
> > >> Apparently the release engineering team has not rebuilt this package
> in a mass
> > >> rebuild at least since Fedora 35.
> > >>
> > >> To remove it from the list, build the package on Rawhide please.
> > >
> > > Or we could not, and drop i686 completely.
> >
> > If we drop glibc32, we can't build any 32-bit code at all because GCC
> > will no longer support -m32.  In this regardm x86-64 is different than
> > the other Fedora architectures which can target bare metal 32-bit even
> > from 64-bit-only compilers.
> >
> > Are bootloaders fully treated as firmware and no longer built by Fedora?
> > At least the shim package does not come with corresponding source code
> > AFAICS.  But I expect that there are other 32-bit pre-boot packages that
> > we still rebuild.
> >
> > We need to fix this GCC build issue for CentOS 10 eventually, and at
> > that point, we won't need glibc32 anymore.  It's been a constant source
> > of annoyance.
>
> Necessity is the mother of all invention.  If you need this solved by
> CentOS Stream 10, you really want to solve it now and get that
> solution into F39 or F40 at the latest.
>
>
As much as I would like to see the i686 problem dealt with finally, I am
not sure what is done with a fundamental change like this after the closing
period for such changes for Fedora 39. [It does lead to a funny problem..
if i686 were to get removed after the mass rebuild because a cascade of
FTBFS or other reasons.. does FESCO need a change proposal :)]



> josh
> ___
> 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
>


-- 
Stephen Smoogen, Red Hat Automotive
Let us be kind to one another, for most of us are fighting a hard battle.
-- Ian MacClaren
___
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: List of long term FTBFS packages to be retired in August

2023-07-25 Thread Peter Robinson
On Tue, Jul 25, 2023 at 4:44 PM Florian Weimer  wrote:
>
> * Josh Boyer:
>
> > On Tue, Jul 25, 2023 at 10:53 AM Miro Hrončok  wrote:
> >>
> >> On 25. 07. 23 16:42, Florian Weimer wrote:
> >> > * Miro Hrončok:
> >> >
> >> >> glibc32   codonell, fweimer, jakub, 
> >> >> mcermak
> >> >
> >> > Is this about FTBFS issues?  There isn't any recent build failure in
> >> > Koji, so I don't get why it's on this list?
> >>
> >> The build currently in Rawhide was done on Fedora 36 which is end of life.
> >>
> >> Apparently the release engineering team has not rebuilt this package in a 
> >> mass
> >> rebuild at least since Fedora 35.
> >>
> >> To remove it from the list, build the package on Rawhide please.
> >
> > Or we could not, and drop i686 completely.
>
> If we drop glibc32, we can't build any 32-bit code at all because GCC
> will no longer support -m32.  In this regardm x86-64 is different than
> the other Fedora architectures which can target bare metal 32-bit even
> from 64-bit-only compilers.
>
> Are bootloaders fully treated as firmware and no longer built by Fedora?
> At least the shim package does not come with corresponding source code
> AFAICS.  But I expect that there are other 32-bit pre-boot packages that
> we still rebuild.

There's shim-unsigned* which is built in Fedora, the output of those
are sent off to be signed and then the signed binaries are put into
the final shim packages which don't have source code but they are
still built on Fedora with the source, just in a two step process due
to the out of band signing.
___
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: List of long term FTBFS packages to be retired in August

2023-07-25 Thread Josh Boyer
On Tue, Jul 25, 2023 at 11:44 AM Florian Weimer  wrote:
>
> * Josh Boyer:
>
> > On Tue, Jul 25, 2023 at 10:53 AM Miro Hrončok  wrote:
> >>
> >> On 25. 07. 23 16:42, Florian Weimer wrote:
> >> > * Miro Hrončok:
> >> >
> >> >> glibc32   codonell, fweimer, jakub, 
> >> >> mcermak
> >> >
> >> > Is this about FTBFS issues?  There isn't any recent build failure in
> >> > Koji, so I don't get why it's on this list?
> >>
> >> The build currently in Rawhide was done on Fedora 36 which is end of life.
> >>
> >> Apparently the release engineering team has not rebuilt this package in a 
> >> mass
> >> rebuild at least since Fedora 35.
> >>
> >> To remove it from the list, build the package on Rawhide please.
> >
> > Or we could not, and drop i686 completely.
>
> If we drop glibc32, we can't build any 32-bit code at all because GCC
> will no longer support -m32.  In this regardm x86-64 is different than
> the other Fedora architectures which can target bare metal 32-bit even
> from 64-bit-only compilers.
>
> Are bootloaders fully treated as firmware and no longer built by Fedora?
> At least the shim package does not come with corresponding source code
> AFAICS.  But I expect that there are other 32-bit pre-boot packages that
> we still rebuild.
>
> We need to fix this GCC build issue for CentOS 10 eventually, and at
> that point, we won't need glibc32 anymore.  It's been a constant source
> of annoyance.

Necessity is the mother of all invention.  If you need this solved by
CentOS Stream 10, you really want to solve it now and get that
solution into F39 or F40 at the latest.

josh
___
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: List of long term FTBFS packages to be retired in August

2023-07-25 Thread Florian Weimer
* Miro Hrončok:

> On 25. 07. 23 16:42, Florian Weimer wrote:
>> * Miro Hrončok:
>> 
>>> glibc32   codonell, fweimer, jakub, mcermak
>> Is this about FTBFS issues?  There isn't any recent build failure in
>> Koji, so I don't get why it's on this list?
>
> The build currently in Rawhide was done on Fedora 36 which is end of life.
>
> Apparently the release engineering team has not rebuilt this package
> in a mass rebuild at least since Fedora 35.
>
> To remove it from the list, build the package on Rawhide please.

That's not what the subject line and the policy say, though.  The policy
requires failing builds and FTBFS bugs in Bugzilla.

Please update the policy if you think this is no longer appropriate.

Thanks,
Florian
___
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: List of long term FTBFS packages to be retired in August

2023-07-25 Thread Florian Weimer
* Josh Boyer:

> On Tue, Jul 25, 2023 at 10:53 AM Miro Hrončok  wrote:
>>
>> On 25. 07. 23 16:42, Florian Weimer wrote:
>> > * Miro Hrončok:
>> >
>> >> glibc32   codonell, fweimer, jakub, 
>> >> mcermak
>> >
>> > Is this about FTBFS issues?  There isn't any recent build failure in
>> > Koji, so I don't get why it's on this list?
>>
>> The build currently in Rawhide was done on Fedora 36 which is end of life.
>>
>> Apparently the release engineering team has not rebuilt this package in a 
>> mass
>> rebuild at least since Fedora 35.
>>
>> To remove it from the list, build the package on Rawhide please.
>
> Or we could not, and drop i686 completely.

If we drop glibc32, we can't build any 32-bit code at all because GCC
will no longer support -m32.  In this regardm x86-64 is different than
the other Fedora architectures which can target bare metal 32-bit even
from 64-bit-only compilers.

Are bootloaders fully treated as firmware and no longer built by Fedora?
At least the shim package does not come with corresponding source code
AFAICS.  But I expect that there are other 32-bit pre-boot packages that
we still rebuild.

We need to fix this GCC build issue for CentOS 10 eventually, and at
that point, we won't need glibc32 anymore.  It's been a constant source
of annoyance.

Thanks,
Florian
___
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: List of long term FTBFS packages to be retired in August

2023-07-25 Thread Josh Boyer
On Tue, Jul 25, 2023 at 10:53 AM Miro Hrončok  wrote:
>
> On 25. 07. 23 16:42, Florian Weimer wrote:
> > * Miro Hrončok:
> >
> >> glibc32   codonell, fweimer, jakub, mcermak
> >
> > Is this about FTBFS issues?  There isn't any recent build failure in
> > Koji, so I don't get why it's on this list?
>
> The build currently in Rawhide was done on Fedora 36 which is end of life.
>
> Apparently the release engineering team has not rebuilt this package in a mass
> rebuild at least since Fedora 35.
>
> To remove it from the list, build the package on Rawhide please.

Or we could not, and drop i686 completely.

josh
___
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: List of long term FTBFS packages to be retired in August

2023-07-25 Thread Miro Hrončok

On 25. 07. 23 16:42, Florian Weimer wrote:

* Miro Hrončok:


glibc32   codonell, fweimer, jakub, mcermak


Is this about FTBFS issues?  There isn't any recent build failure in
Koji, so I don't get why it's on this list?


The build currently in Rawhide was done on Fedora 36 which is end of life.

Apparently the release engineering team has not rebuilt this package in a mass 
rebuild at least since Fedora 35.


To remove it from the list, build the package on Rawhide please.

--
Miro Hrončok
--
Phone: +420777974800
IRC: mhroncok
___
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: List of long term FTBFS packages to be retired in August

2023-07-25 Thread Florian Weimer
* Miro Hrončok:

> glibc32   codonell, fweimer, jakub, mcermak

Is this about FTBFS issues?  There isn't any recent build failure in
Koji, so I don't get why it's on this list?

Thanks,
Florian
___
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: List of long term FTBFS packages to be retired in August

2023-07-25 Thread Hans de Goede
Hi,

On 7/25/23 15:52, Mikolaj Izdebski wrote:
> On Tue, Jul 25, 2023 at 2:48 PM Hans de Goede  wrote:
> 
>>> xmvn-connector-ivymizdebsk
>>
>> This one has a long long list of deps which will break if it is
>> retired and there is a pull-req here fixing the FTBFS:
>>
>> https://src.fedoraproject.org/rpms/xmvn-connector-ivy/pull-request/2
>>
>> Are there any objections against solving it with the rebase to
>> a newer git snapshot (it already is a git snapshot) ?
>>
>> If not then I'll use my proven-packager rights to get this
>> pull-request merge and close the FTBFS bug.
>>
>> Mikolaj any objections against merging the pull-request ?
> 
> I made a new upstream release of version 4.0.0 and updated the package
> to the latest version.
> Bodhi update: https://bodhi.fedoraproject.org/updates/FEDORA-2023-41256115ad

Great, thank you!

Regards,

Hans


___
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: List of long term FTBFS packages to be retired in August

2023-07-25 Thread Mikolaj Izdebski
On Tue, Jul 25, 2023 at 2:48 PM Hans de Goede  wrote:

> > xmvn-connector-ivymizdebsk
>
> This one has a long long list of deps which will break if it is
> retired and there is a pull-req here fixing the FTBFS:
>
> https://src.fedoraproject.org/rpms/xmvn-connector-ivy/pull-request/2
>
> Are there any objections against solving it with the rebase to
> a newer git snapshot (it already is a git snapshot) ?
>
> If not then I'll use my proven-packager rights to get this
> pull-request merge and close the FTBFS bug.
>
> Mikolaj any objections against merging the pull-request ?

I made a new upstream release of version 4.0.0 and updated the package
to the latest version.
Bodhi update: https://bodhi.fedoraproject.org/updates/FEDORA-2023-41256115ad

>
> Miro can you hold of on retiring xmvn-connector-ivy please ?
>
> Regards,
>
> Hans
>
>
>
>
___
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: List of long term FTBFS packages to be retired in August

2023-07-25 Thread Miro Hrončok

On 25. 07. 23 14:48, Hans de Goede wrote:

Miro can you hold of on retiring xmvn-connector-ivy please ?


ack

--
Miro Hrončok
--
Phone: +420777974800
IRC: mhroncok
___
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: List of long term FTBFS packages to be retired in August

2023-07-25 Thread Hans de Goede
Hi all,

On 7/25/23 14:24, Miro Hrončok wrote:
> Dear maintainers.
> 
> Based on the current fail to build from source policy, the following packages
> should be retired from Fedora 39 approximately one week before branching.
> 
> 5 weekly reminders are required, hence the retirement will happen
> approximately in 2 weeks, i.e. around 2023-08-01.
> 
> Policy: 
> https://docs.fedoraproject.org/en-US/fesco/Fails_to_build_from_source_Fails_to_install/
> 
> The packages in rawhide were not successfully built at least since Fedora 36.
> 
> This report is based on dist tags.
> 
> Packages collected via:
> https://github.com/hroncok/fedora-report-ftbfs-retirements/blob/master/ftbfs-retirements.ipynb
> 
> If you see a package that was built, please let me know.
> If you see a package that should be exempted from the process,
> please let me know and we can work together to get a FESCo approval for that.
> 
> If you see a package that can be rebuilt, please do so.
> 
>     Package   (co)maintainers
> 
> DecodeIR  leamas
> apache-commons-fileupload jerboaa, jjelen, mizdebsk, spike
> avarice   lucilanga
> burp  cicku, kaptk2
> clang12   tstellar
> cvise mpolacek
> emacs-common-ess  alexlan, jamatos
> fasttext  kenhys
> glibc32   codonell, fweimer, jakub, mcermak
> golang-github-burntsushi-xgbutil  eclipseo, go-sig
> golang-github-chifflier-nfqueue   fab, go-sig
> golang-github-cupcake-rdb eclipseo, go-sig
> golang-github-d5-tengo-2  fab, go-sig
> golang-github-docker-slim eclipseo, go-sig
> golang-github-facebookarchive-inject  agerstmayr, go-sig, mgoodwin, 
> nathans
> golang-github-facebookarchive-structtag   agerstmayr, go-sig, mgoodwin, 
> nathans
> golang-github-facebookgo-clock    eclipseo, go-sig
> golang-github-facebookgo-ensure   dcavalca, go-sig
> golang-github-facebookgo-httpdown go-sig, orphan
> golang-github-facebookgo-stack    dcavalca, go-sig
> golang-github-facebookgo-stats    go-sig, orphan
> golang-github-fonts-dejavu    go-sig, orphan
> golang-github-ghemawat-stream eclipseo, go-sig
> golang-github-google-tspi go-sig, orphan
> golang-github-gorp-3  dcavalca, go-sig
> golang-github-haproxytech-models  bdperkin, go-sig
> golang-github-influxdata-tdigest  go-sig, orphan
> golang-github-jackc-pgproto3  eclipseo, go-sig
> golang-github-jackc-pgservicefile eclipseo, go-sig
> golang-github-michaeltjones-walk  go-sig, orphan
> golang-github-nkovacs-streamquote eclipseo, go-sig
> golang-github-phpdave11-gofpdi    go-sig, orphan
> golang-github-powerman-check  eclipseo, go-sig
> golang-github-quay-clair-3    eclipseo, go-sig
> golang-github-remind101-migrate   eclipseo, go-sig
> golang-github-tj-buffer   go-sig, orphan
> golang-github-vmihailenco-msgpack go-sig, orphan
> golang-github-vmware-vmw-guestinfo    eclipseo, go-sig
> golang-github-wsxiaoys-terminal   go-sig, orphan
> golang-github-x-cray-logrus-prefixed-formatter  dcavalca, go-sig
> golang-github-zmap-zlint  eclipseo, go-sig
> golang-github-zmap-zlint-2    go-sig, orphan
> golang-go4    eclipseo, go-sig, jchaloup
> golang-gopkg-redis-2  go-sig, orphan
> golang-gopkg-retry-1  eclipseo, go-sig
> golang-gopkg-seborama-govcr-2 go-sig, qulogic
> golang-gopkg-sourcemap-1  eclipseo, go-sig, jchaloup
> golang-gvisor eclipseo, elmarco, go-sig
> golang-k8s-legacy-cloud-providers go-sig, orphan
> golang-rsc-qr go-sig, qulogic
> golang-sigs-k8s-kustomize dcavalca, go-sig
> golang-vitess eclipseo, go-sig
> hibernate-jpa-2.1-api jjelen
> httping   fab
> jblas zbyszek
> libffi3.1 codonell
> libifp    konradm
> log4c stevetraylen, valtri
> mongo-cxx-driver  hhorak, mmuzila
> mspdebug  till
> multican  jnovy
> nom-tam-fits  gil, lupinix, zbyszek
> opentracker   cicku, lbazan
> procinfo-ng   fab
> racket   

Re: List of long term FTBFS packages to be retired in August

2023-07-25 Thread Miro Hrončok

On 25. 07. 23 14:33, Sandro wrote:

On 25-07-2023 14:24, Miro Hrončok wrote:

5 weekly reminders are required, hence the retirement will happen
approximately in 2 weeks, i.e. around 2023-08-01.


1 August is exactly 1 week from now...



Apologies, I forgot to update the number of weeks.

--
Miro Hrončok
--
Phone: +420777974800
IRC: mhroncok
___
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: List of long term FTBFS packages to be retired in August

2023-07-25 Thread Sandro

On 25-07-2023 14:24, Miro Hrončok wrote:

5 weekly reminders are required, hence the retirement will happen
approximately in 2 weeks, i.e. around 2023-08-01.


1 August is exactly 1 week from now...
___
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: List of long term FTBFS packages to be retired in August

2023-07-17 Thread Jerry James
On Mon, Jul 17, 2023 at 1:15 PM Miro Hrončok  wrote:
> xmvn-connector-ivymizdebsk

Didik opened a PR to fix this:
https://src.fedoraproject.org/rpms/xmvn-connector-ivy/pull-request/2.
-- 
Jerry James
https://www.jamezone.org/
___
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: List of long term FTBFS packages to be retired in August

2023-07-14 Thread Mikel Olasagasti
Hau idatzi du Fabio Valentini (decatho...@gmail.com) erabiltzaileak
(2023 uzt. 13(a), og. (14:27)):
>
> On Wed, Jul 12, 2023 at 1:01 PM Mikel Olasagasti  
> wrote:
> >
> > Hau idatzi du Fabio Valentini (decatho...@gmail.com) erabiltzaileak
> > (2023 uzt. 12(a), az. (11:53)):
> > >
> > > On Tue, Jul 11, 2023 at 10:06 PM Mikel Olasagasti  
> > > wrote:
> > > >
> > >
> > > (snip)
> > >
> > > >
> > > > > golang-github-moby-spdystreamgo-sig, mikelo2
> > > >
> > > > Builds fine in Koschei and no BZ
> > > >
> > > > > golang-github-openapi-validate   alexsaezm, go-sig
> > > >
> > > > Builds fine in Koschei and no BZ
> > >
> > > This is usually an indication that the package fails to even produce a
> > > valid SRPM file (i.e. "fedpkg srpm" fails).
> > > In this case, mass rebuild will skip it, no FTBFS bug will be filed,
> > > and koschei will keep using the last "known good" SRPM from koji.
> >
> > Both packages work for me. I'm doing the following:
> >
> > $ fedpkg clone golang-github-moby-spdystream
> > $ cd golang-github-moby-spdystream
> > $ fedpkg srpm
> > $ mock -r fedora-rawhide-x86_64
> > /tmp/golang-github-openapi-validate/golang-github-openapi-validate-0.20.1-5.fc39.src.rpm
>
> If that is indeed the case, then the missing f38 build was likely
> caused by a hiccup during the f38 mass rebuild.
> To get the package off the "long term FTBFS retirements" list, all
> that would be needed is to run "fedpkg build".

Thanks, Fabio. I realized that packages were not built for rawhide,
f38 and f37. I built the packages for rawhide and f38, I hope it's
enough to be out of the list.

Regards,
Mikel
___
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: List of long term FTBFS packages to be retired in August

2023-07-13 Thread Fabio Valentini
On Wed, Jul 12, 2023 at 1:01 PM Mikel Olasagasti  wrote:
>
> Hau idatzi du Fabio Valentini (decatho...@gmail.com) erabiltzaileak
> (2023 uzt. 12(a), az. (11:53)):
> >
> > On Tue, Jul 11, 2023 at 10:06 PM Mikel Olasagasti  
> > wrote:
> > >
> >
> > (snip)
> >
> > >
> > > > golang-github-moby-spdystreamgo-sig, mikelo2
> > >
> > > Builds fine in Koschei and no BZ
> > >
> > > > golang-github-openapi-validate   alexsaezm, go-sig
> > >
> > > Builds fine in Koschei and no BZ
> >
> > This is usually an indication that the package fails to even produce a
> > valid SRPM file (i.e. "fedpkg srpm" fails).
> > In this case, mass rebuild will skip it, no FTBFS bug will be filed,
> > and koschei will keep using the last "known good" SRPM from koji.
>
> Both packages work for me. I'm doing the following:
>
> $ fedpkg clone golang-github-moby-spdystream
> $ cd golang-github-moby-spdystream
> $ fedpkg srpm
> $ mock -r fedora-rawhide-x86_64
> /tmp/golang-github-openapi-validate/golang-github-openapi-validate-0.20.1-5.fc39.src.rpm

If that is indeed the case, then the missing f38 build was likely
caused by a hiccup during the f38 mass rebuild.
To get the package off the "long term FTBFS retirements" list, all
that would be needed is to run "fedpkg build".

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: List of long term FTBFS packages to be retired in August

2023-07-12 Thread Mikel Olasagasti
Hau idatzi du Fabio Valentini (decatho...@gmail.com) erabiltzaileak
(2023 uzt. 12(a), az. (11:53)):
>
> On Tue, Jul 11, 2023 at 10:06 PM Mikel Olasagasti  
> wrote:
> >
>
> (snip)
>
> >
> > > golang-github-moby-spdystreamgo-sig, mikelo2
> >
> > Builds fine in Koschei and no BZ
> >
> > > golang-github-openapi-validate   alexsaezm, go-sig
> >
> > Builds fine in Koschei and no BZ
>
> This is usually an indication that the package fails to even produce a
> valid SRPM file (i.e. "fedpkg srpm" fails).
> In this case, mass rebuild will skip it, no FTBFS bug will be filed,
> and koschei will keep using the last "known good" SRPM from koji.

Both packages work for me. I'm doing the following:

$ fedpkg clone golang-github-moby-spdystream
$ cd golang-github-moby-spdystream
$ fedpkg srpm
$ mock -r fedora-rawhide-x86_64
/tmp/golang-github-openapi-validate/golang-github-openapi-validate-0.20.1-5.fc39.src.rpm

Mikel
___
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: List of long term FTBFS packages to be retired in August

2023-07-12 Thread Fabio Valentini
On Tue, Jul 11, 2023 at 10:06 PM Mikel Olasagasti  wrote:
>

(snip)

>
> > golang-github-moby-spdystreamgo-sig, mikelo2
>
> Builds fine in Koschei and no BZ
>
> > golang-github-openapi-validate   alexsaezm, go-sig
>
> Builds fine in Koschei and no BZ

This is usually an indication that the package fails to even produce a
valid SRPM file (i.e. "fedpkg srpm" fails).
In this case, mass rebuild will skip it, no FTBFS bug will be filed,
and koschei will keep using the last "known good" SRPM from koji.

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: List of long term FTBFS packages to be retired in August

2023-07-11 Thread Mikel Olasagasti
Hi,

Hau idatzi du Miro Hrončok (mhron...@redhat.com) erabiltzaileak (2023
uzt. 11(a), ar. (15:07)):
>

> golang-code-cloudfoundry-bytefmt go-sig, mikelo2

Fixed

> golang-github-aliyun-cli bdperkin, go-sig

Fixed

> golang-github-d2g-dhcp4clientalexsaezm, go-sig

Fixed

> golang-github-dennwc-varint  alexsaezm, go-sig

Fixed

> golang-github-macaron-inject go-sig, mikelo2

Fixed

> golang-github-moby-spdystreamgo-sig, mikelo2

Builds fine in Koschei and no BZ

> golang-github-openapi-validate   alexsaezm, go-sig

Builds fine in Koschei and no BZ

> golang-github-rogpeppe-charset   go-sig, mikelo2

Fixed

> golang-github-yvasiyarov-metrics alexsaezm, go-sig

Fixed

> golang-gopkg-tomb-1  go-sig, mikelo2

Fixed

> golang-gopkg-validator-2 alexsaezm, go-sig

To retire after uber-tally doesn't depend anymore. Will check after
dep refreshes.

--
Mikel
___
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: List of long term FTBFS packages to be retired in August

2023-07-11 Thread Jerry James
On Tue, Jul 11, 2023 at 7:07 AM Miro Hrončok  wrote:
> sbcl green, rdieter

About a month ago, I opened a PR to fix this.  It looks like the PR
was merged, but no build was done.  I am taking it upon myself to
update sbcl to the next released version (the PR was for 2.3.5, but
2.3.6 has since been released) and do the build.  I hope I am not
stepping on any toes.

> xmvn-connector-ivy   mizdebsk

The problem appears to be that apache-ivy does not have VFS support,
which xmvn-connector-ivy needs.  It doesn't have VFS support because
apache-commons-vfs was retired.  I need apache-commons-vfs back anyway
for other reasons, so I have filed a review bug:

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

-- 
Jerry James
https://www.jamezone.org/
___
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: List of long term FTBFS packages to be retired in August

2023-07-02 Thread Till Hofmann

Hi,

On 6/28/23 09:43, Miro Hrončok wrote:


If you see a package that was built, please let me know.
If you see a package that should be exempted from the process,
please let me know and we can work together to get a FESCo approval 
for that.


If you see a package that can be rebuilt, please do so. 



openni is now fixed:
https://koji.fedoraproject.org/koji/taskinfo?taskID=102844216

Kind regards,
Till
___
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: List of long term FTBFS packages to be retired in August

2023-06-28 Thread Miro Hrončok

On 28. 06. 23 15:33, Hans de Goede wrote:

Hi,

On 6/28/23 09:43, Miro Hrončok wrote:

Dear maintainers.

Based on the current fail to build from source policy, the following packages
should be retired from Fedora 39 approximately one week before branching.

5 weekly reminders are required, hence the retirement will happen
approximately in 5 weeks, i.e. around 2023-08-01.

Policy: 
https://docs.fedoraproject.org/en-US/fesco/Fails_to_build_from_source_Fails_to_install/

The packages in rawhide were not successfully built at least since Fedora 36.

This report is based on dist tags.

Packages collected via:
https://github.com/hroncok/fedora-report-ftbfs-retirements/blob/master/ftbfs-retirements.ipynb

If you see a package that was built, please let me know.
If you see a package that should be exempted from the process,
please let me know and we can work together to get a FESCo approval for that.


So it seems that pretty much all of java is scheduled to go away,


It is not scheduled to go away. It is marked as impacted whent he deps go away.


or at least
have its deps taken away because of:

javapackages-filesystem
javapackages-tools (also through its jpackage-utils alias / Provides)
javapackages-local


This will merely start FTBFS when xmvn-connector-ivy will be retired.


Which all are build from the same javapackages SRPM being FTBFS for a long time 
now.


No?


Does anyone know what is going on here ?


I think so. javapackages-tools BuidlRequires xmvn-connector-ivy.


Can we please exempt the javapackages srpm from being retired
until we have sorted things out?


They will not be retired based on this policy, only xmvn-connector-ivy will be 
retired.



That will remove a ton of deps from the list of affected packages.


To remove the packages from the list, somebody would need to manually hack the 
script or the output. Or javapackages-tools could stop BRing 
xmvn-connector-ivy. Or xmvn-connector-ivy could be fixed. Or retired sooner.


--
Miro Hrončok
--
Phone: +420777974800
IRC: mhroncok
___
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: List of long term FTBFS packages to be retired in August

2022-07-27 Thread Pavel Valena
Yes, thank you very much!

Pavel

On Wed, Jul 27, 2022 at 4:00 PM Vít Ondruch  wrote:

>
> Dne 26. 07. 22 v 17:00 Mamoru TASAKA napsal(a):
> > Miro Hrončok wrote on 2022/07/26 22:40:
> >> On 26. 07. 22 15:07, Mamoru TASAKA wrote:
> >>> Miro Hrončok wrote on 2022/07/26 21:28:
>  Dear maintainers.
> 
>  Based on the current fail to build from source policy, the
>  following packages
>  will be retired from Fedora 37 approximately one week before
>  branching (August 2022).
> 
>  Policy:
> 
> https://docs.fedoraproject.org/en-US/fesco/Fails_to_build_from_source_Fails_to_install/
> 
>  The packages in rawhide were not successfully built at least since
>  Fedora 35.
> 
>  This report is based on dist tags.
> 
>  Packages collected via:
> 
> https://github.com/hroncok/fedora-report-ftbfs-retirements/blob/master/ftbfs-retirements.ipynb
> 
> 
>  If you see a package that was built, please let me know.
>  If you see a package that should be exempted from the process,
>  please let me know and we can work together to get a FESCo approval
>  for that.
> 
>  If you see a package that can be rebuilt, please do so.
> 
>    Package   (co)maintainers
> 
> =
> 
>  rubygem-sprockets-rails  jaruga, pvalena,
>  ruby-packagers-sig
> 
>  Depending on: rubygem-sprockets-rails (22)
>   rubygem-actionmailbox (maintained by: pvalena)
>   rubygem-actionmailbox-7.0.2.3-2.fc37.src requires
>  rubygem(sprockets-rails) = 3.2.2
> 
>   rubygem-activestorage (maintained by: ruby-packagers-sig,
>  vondruch)
>   rubygem-activestorage-7.0.2.3-1.fc37.src requires
>  rubygem(sprockets-rails) = 3.2.2
> 
>   rubygem-railties (maintained by: mmorsi, pvalena, tdawson,
>  vondruch)
>   rubygem-railties-7.0.2.3-2.fc37.src requires
>  rubygem(sprockets-rails) = 3.2.2
> 
>   rubygem-sassc-rails (maintained by: pvalena)
>   rubygem-sassc-rails-2.1.2-4.fc36.noarch requires
>  rubygem(sprockets-rails) = 3.2.2
>   rubygem-sassc-rails-2.1.2-4.fc36.src requires
>  rubygem(sprockets-rails) = 3.2.2
>  ...
> 
> >>>
> >>> Can you show what changed for rubygem-sprockets-rails compared with
> >>> the previous report one week ago?
> >>>
> >>>
> https://lists.fedoraproject.org/archives/list/devel@lists.fedoraproject.org/thread/BEYCREMETV6DDVFMLKOE5HR2XWEWBPFE/
> >>>
> >>>
> >>> The above report seems to be saying that no package depends on
> >>> rubygem-sprockets-rails,
> >>> but this time many packages depend on rubygem-sprockets-rails.
> >>
> >> Only 4 packages directly require rubygem(sprockets-rails):
> >>
> >> rubygem-actionmailbox
> >>  rubygem-actionmailbox-7.0.2.3-2.fc37.src
> >>
> >> rubygem-activestorage
> >>  rubygem-activestorage-7.0.2.3-1.fc37.src
> >>
> >> rubygem-railties
> >>  rubygem-railties-7.0.2.3-2.fc37.src
> >>
> >> rubygem-sassc-rails
> >>  rubygem-sassc-rails-2.1.2-4.fc36.noarch
> >>  rubygem-sassc-rails-2.1.2-4.fc36.src
> >>
> >>
> >> I've checked and from the spec files, it seems that they always did.
> >>
> >> I've repoqueried this compose
> >>
> https://kojipkgs.fedoraproject.org/compose/rawhide/Fedora-Rawhide-20220719.n.0/
> >> and it seems that the requirements were there.
> >>
> >> The only difference, it seems, is that rubygem-image_processing was
> >> part of the FTBFS packages set before and its dep tree already
> >> included those packages, so the script decided not to report them
> >> twice :(
> >>
> >>
> https://pagure.io/releng/blob/c9a08daa74/f/scripts/find_unblocked_orphans.py#_419
> >>
> >>
> >> When I remove this thing, and re-add rubygem-image_processing to the
> >> list of FTBFS packages, I see rubygem-sprockets-rails's dependencies
> >> reported.
> >>
> >> I guess we should fix the script, this is dangerous.
> >>
> >> And if you think this justifies not retiring rubygem-sprockets-rails
> >> this round, I am OK with that.
> >>
> >> Thanks for spotting this. No other remaining packages here seem to be
> >> affected by this now.
> >>
> >
> > Okay, thank you for confirmation.
> >
> > Anyway now I checked the upstream repo and the upstream already fixed
> > build issue.
> > So I've backported the upstream fix and now build was successful as
> > rubygem-sprockets-rails-3.2.2-6.fc37 .
> >
> > https://koji.fedoraproject.org/koji/buildinfo?buildID=2036386
>
>
> Thx a lot for fixing those. I appreciate that.
>
>
> Vít
>
>
> >
> > Regards,
> > Mamoru
> > ___
> > 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 Guidelin

Re: List of long term FTBFS packages to be retired in August

2022-07-27 Thread Vít Ondruch


Dne 26. 07. 22 v 17:00 Mamoru TASAKA napsal(a):

Miro Hrončok wrote on 2022/07/26 22:40:

On 26. 07. 22 15:07, Mamoru TASAKA wrote:

Miro Hrončok wrote on 2022/07/26 21:28:

Dear maintainers.

Based on the current fail to build from source policy, the 
following packages
will be retired from Fedora 37 approximately one week before 
branching (August 2022).


Policy: 
https://docs.fedoraproject.org/en-US/fesco/Fails_to_build_from_source_Fails_to_install/


The packages in rawhide were not successfully built at least since 
Fedora 35.


This report is based on dist tags.

Packages collected via:
https://github.com/hroncok/fedora-report-ftbfs-retirements/blob/master/ftbfs-retirements.ipynb 



If you see a package that was built, please let me know.
If you see a package that should be exempted from the process, 
please let me know and we can work together to get a FESCo approval 
for that.


If you see a package that can be rebuilt, please do so.

  Package   (co)maintainers
= 

rubygem-sprockets-rails  jaruga, pvalena, 
ruby-packagers-sig


Depending on: rubygem-sprockets-rails (22)
 rubygem-actionmailbox (maintained by: pvalena)
 rubygem-actionmailbox-7.0.2.3-2.fc37.src requires 
rubygem(sprockets-rails) = 3.2.2


 rubygem-activestorage (maintained by: ruby-packagers-sig, 
vondruch)
 rubygem-activestorage-7.0.2.3-1.fc37.src requires 
rubygem(sprockets-rails) = 3.2.2


 rubygem-railties (maintained by: mmorsi, pvalena, tdawson, 
vondruch)
 rubygem-railties-7.0.2.3-2.fc37.src requires 
rubygem(sprockets-rails) = 3.2.2


 rubygem-sassc-rails (maintained by: pvalena)
 rubygem-sassc-rails-2.1.2-4.fc36.noarch requires 
rubygem(sprockets-rails) = 3.2.2
 rubygem-sassc-rails-2.1.2-4.fc36.src requires 
rubygem(sprockets-rails) = 3.2.2

...



Can you show what changed for rubygem-sprockets-rails compared with
the previous report one week ago?

https://lists.fedoraproject.org/archives/list/devel@lists.fedoraproject.org/thread/BEYCREMETV6DDVFMLKOE5HR2XWEWBPFE/ 



The above report seems to be saying that no package depends on 
rubygem-sprockets-rails,

but this time many packages depend on rubygem-sprockets-rails.


Only 4 packages directly require rubygem(sprockets-rails):

rubygem-actionmailbox
 rubygem-actionmailbox-7.0.2.3-2.fc37.src

rubygem-activestorage
 rubygem-activestorage-7.0.2.3-1.fc37.src

rubygem-railties
 rubygem-railties-7.0.2.3-2.fc37.src

rubygem-sassc-rails
 rubygem-sassc-rails-2.1.2-4.fc36.noarch
 rubygem-sassc-rails-2.1.2-4.fc36.src


I've checked and from the spec files, it seems that they always did.

I've repoqueried this compose 
https://kojipkgs.fedoraproject.org/compose/rawhide/Fedora-Rawhide-20220719.n.0/ 
and it seems that the requirements were there.


The only difference, it seems, is that rubygem-image_processing was 
part of the FTBFS packages set before and its dep tree already 
included those packages, so the script decided not to report them 
twice :(


https://pagure.io/releng/blob/c9a08daa74/f/scripts/find_unblocked_orphans.py#_419 



When I remove this thing, and re-add rubygem-image_processing to the 
list of FTBFS packages, I see rubygem-sprockets-rails's dependencies 
reported.


I guess we should fix the script, this is dangerous.

And if you think this justifies not retiring rubygem-sprockets-rails 
this round, I am OK with that.


Thanks for spotting this. No other remaining packages here seem to be 
affected by this now.




Okay, thank you for confirmation.

Anyway now I checked the upstream repo and the upstream already fixed 
build issue.

So I've backported the upstream fix and now build was successful as
rubygem-sprockets-rails-3.2.2-6.fc37 .

https://koji.fedoraproject.org/koji/buildinfo?buildID=2036386



Thx a lot for fixing those. I appreciate that.


Vít




Regards,
Mamoru
___
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 on the list, report it: 
https://pagure.io/fedora-infrastructure


OpenPGP_signature
Description: OpenPGP digital signature
___
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 on the list, repo

Re: List of long term FTBFS packages to be retired in August

2022-07-26 Thread Mamoru TASAKA

Miro Hrončok wrote on 2022/07/26 22:40:

On 26. 07. 22 15:07, Mamoru TASAKA wrote:

Miro Hrončok wrote on 2022/07/26 21:28:

Dear maintainers.

Based on the current fail to build from source policy, the following packages
will be retired from Fedora 37 approximately one week before branching (August 
2022).

Policy: 
https://docs.fedoraproject.org/en-US/fesco/Fails_to_build_from_source_Fails_to_install/

The packages in rawhide were not successfully built at least since Fedora 35.

This report is based on dist tags.

Packages collected via:
https://github.com/hroncok/fedora-report-ftbfs-retirements/blob/master/ftbfs-retirements.ipynb

If you see a package that was built, please let me know.
If you see a package that should be exempted from the process, please let me 
know and we can work together to get a FESCo approval for that.

If you see a package that can be rebuilt, please do so.

  Package   (co)maintainers
=
rubygem-sprockets-rails  jaruga, pvalena, ruby-packagers-sig

Depending on: rubygem-sprockets-rails (22)
 rubygem-actionmailbox (maintained by: pvalena)
 rubygem-actionmailbox-7.0.2.3-2.fc37.src requires 
rubygem(sprockets-rails) = 3.2.2

 rubygem-activestorage (maintained by: ruby-packagers-sig, vondruch)
 rubygem-activestorage-7.0.2.3-1.fc37.src requires 
rubygem(sprockets-rails) = 3.2.2

 rubygem-railties (maintained by: mmorsi, pvalena, tdawson, vondruch)
 rubygem-railties-7.0.2.3-2.fc37.src requires rubygem(sprockets-rails) 
= 3.2.2

 rubygem-sassc-rails (maintained by: pvalena)
 rubygem-sassc-rails-2.1.2-4.fc36.noarch requires 
rubygem(sprockets-rails) = 3.2.2
 rubygem-sassc-rails-2.1.2-4.fc36.src requires rubygem(sprockets-rails) 
= 3.2.2
...



Can you show what changed for rubygem-sprockets-rails compared with
the previous report one week ago?

https://lists.fedoraproject.org/archives/list/devel@lists.fedoraproject.org/thread/BEYCREMETV6DDVFMLKOE5HR2XWEWBPFE/

The above report seems to be saying that no package depends on 
rubygem-sprockets-rails,
but this time many packages depend on rubygem-sprockets-rails.


Only 4 packages directly require rubygem(sprockets-rails):

rubygem-actionmailbox
     rubygem-actionmailbox-7.0.2.3-2.fc37.src

rubygem-activestorage
     rubygem-activestorage-7.0.2.3-1.fc37.src

rubygem-railties
     rubygem-railties-7.0.2.3-2.fc37.src

rubygem-sassc-rails
     rubygem-sassc-rails-2.1.2-4.fc36.noarch
     rubygem-sassc-rails-2.1.2-4.fc36.src


I've checked and from the spec files, it seems that they always did.

I've repoqueried this compose 
https://kojipkgs.fedoraproject.org/compose/rawhide/Fedora-Rawhide-20220719.n.0/ 
and it seems that the requirements were there.

The only difference, it seems, is that rubygem-image_processing was part of the 
FTBFS packages set before and its dep tree already included those packages, so 
the script decided not to report them twice :(

https://pagure.io/releng/blob/c9a08daa74/f/scripts/find_unblocked_orphans.py#_419

When I remove this thing, and re-add rubygem-image_processing to the list of 
FTBFS packages, I see rubygem-sprockets-rails's dependencies reported.

I guess we should fix the script, this is dangerous.

And if you think this justifies not retiring rubygem-sprockets-rails this 
round, I am OK with that.

Thanks for spotting this. No other remaining packages here seem to be affected 
by this now.



Okay, thank you for confirmation.

Anyway now I checked the upstream repo and the upstream already fixed build 
issue.
So I've backported the upstream fix and now build was successful as
rubygem-sprockets-rails-3.2.2-6.fc37 .

https://koji.fedoraproject.org/koji/buildinfo?buildID=2036386

Regards,
Mamoru
___
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 on the list, report it: 
https://pagure.io/fedora-infrastructure


Re: List of long term FTBFS packages to be retired in August

2022-07-26 Thread Miro Hrončok

On 26. 07. 22 15:40, Miro Hrončok wrote:

On 26. 07. 22 15:07, Mamoru TASAKA wrote:

Miro Hrončok wrote on 2022/07/26 21:28:

Dear maintainers.

Based on the current fail to build from source policy, the following packages
will be retired from Fedora 37 approximately one week before branching 
(August 2022).


Policy: 
https://docs.fedoraproject.org/en-US/fesco/Fails_to_build_from_source_Fails_to_install/ 



The packages in rawhide were not successfully built at least since Fedora 35.

This report is based on dist tags.

Packages collected via:
https://github.com/hroncok/fedora-report-ftbfs-retirements/blob/master/ftbfs-retirements.ipynb 



If you see a package that was built, please let me know.
If you see a package that should be exempted from the process, please let me 
know and we can work together to get a FESCo approval for that.


If you see a package that can be rebuilt, please do so.

  Package   (co)maintainers
=
rubygem-sprockets-rails  jaruga, pvalena, ruby-packagers-sig

Depending on: rubygem-sprockets-rails (22)
 rubygem-actionmailbox (maintained by: pvalena)
 rubygem-actionmailbox-7.0.2.3-2.fc37.src requires 
rubygem(sprockets-rails) = 3.2.2


 rubygem-activestorage (maintained by: ruby-packagers-sig, vondruch)
 rubygem-activestorage-7.0.2.3-1.fc37.src requires 
rubygem(sprockets-rails) = 3.2.2


 rubygem-railties (maintained by: mmorsi, pvalena, tdawson, vondruch)
 rubygem-railties-7.0.2.3-2.fc37.src requires 
rubygem(sprockets-rails) = 3.2.2


 rubygem-sassc-rails (maintained by: pvalena)
 rubygem-sassc-rails-2.1.2-4.fc36.noarch requires 
rubygem(sprockets-rails) = 3.2.2
 rubygem-sassc-rails-2.1.2-4.fc36.src requires 
rubygem(sprockets-rails) = 3.2.2

...



Can you show what changed for rubygem-sprockets-rails compared with
the previous report one week ago?

https://lists.fedoraproject.org/archives/list/devel@lists.fedoraproject.org/thread/BEYCREMETV6DDVFMLKOE5HR2XWEWBPFE/ 



The above report seems to be saying that no package depends on 
rubygem-sprockets-rails,

but this time many packages depend on rubygem-sprockets-rails.


Only 4 packages directly require rubygem(sprockets-rails):

rubygem-actionmailbox
     rubygem-actionmailbox-7.0.2.3-2.fc37.src

rubygem-activestorage
     rubygem-activestorage-7.0.2.3-1.fc37.src

rubygem-railties
     rubygem-railties-7.0.2.3-2.fc37.src

rubygem-sassc-rails
     rubygem-sassc-rails-2.1.2-4.fc36.noarch
     rubygem-sassc-rails-2.1.2-4.fc36.src


I've checked and from the spec files, it seems that they always did.

I've repoqueried this compose 
https://kojipkgs.fedoraproject.org/compose/rawhide/Fedora-Rawhide-20220719.n.0/ 
and it seems that the requirements were there.


The only difference, it seems, is that rubygem-image_processing was part of the 
FTBFS packages set before and its dep tree already included those packages, so 
the script decided not to report them twice :(


https://pagure.io/releng/blob/c9a08daa74/f/scripts/find_unblocked_orphans.py#_419

When I remove this thing, and re-add rubygem-image_processing to the list of 
FTBFS packages, I see rubygem-sprockets-rails's dependencies reported.


I guess we should fix the script, this is dangerous.

And if you think this justifies not retiring rubygem-sprockets-rails this 
round, I am OK with that.


Thanks for spotting this. No other remaining packages here seem to be affected 
by this now.


https://pagure.io/releng/pull-request/10924

--
Miro Hrončok
--
Phone: +420777974800
IRC: mhroncok
___
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 on the list, report it: 
https://pagure.io/fedora-infrastructure


Re: List of long term FTBFS packages to be retired in August

2022-07-26 Thread Miro Hrončok

On 26. 07. 22 15:07, Mamoru TASAKA wrote:

Miro Hrončok wrote on 2022/07/26 21:28:

Dear maintainers.

Based on the current fail to build from source policy, the following packages
will be retired from Fedora 37 approximately one week before branching 
(August 2022).


Policy: 
https://docs.fedoraproject.org/en-US/fesco/Fails_to_build_from_source_Fails_to_install/ 



The packages in rawhide were not successfully built at least since Fedora 35.

This report is based on dist tags.

Packages collected via:
https://github.com/hroncok/fedora-report-ftbfs-retirements/blob/master/ftbfs-retirements.ipynb 



If you see a package that was built, please let me know.
If you see a package that should be exempted from the process, please let me 
know and we can work together to get a FESCo approval for that.


If you see a package that can be rebuilt, please do so.

  Package   (co)maintainers
=
rubygem-sprockets-rails  jaruga, pvalena, ruby-packagers-sig

Depending on: rubygem-sprockets-rails (22)
 rubygem-actionmailbox (maintained by: pvalena)
 rubygem-actionmailbox-7.0.2.3-2.fc37.src requires 
rubygem(sprockets-rails) = 3.2.2


 rubygem-activestorage (maintained by: ruby-packagers-sig, vondruch)
 rubygem-activestorage-7.0.2.3-1.fc37.src requires 
rubygem(sprockets-rails) = 3.2.2


 rubygem-railties (maintained by: mmorsi, pvalena, tdawson, vondruch)
 rubygem-railties-7.0.2.3-2.fc37.src requires 
rubygem(sprockets-rails) = 3.2.2


 rubygem-sassc-rails (maintained by: pvalena)
 rubygem-sassc-rails-2.1.2-4.fc36.noarch requires 
rubygem(sprockets-rails) = 3.2.2
 rubygem-sassc-rails-2.1.2-4.fc36.src requires 
rubygem(sprockets-rails) = 3.2.2

...



Can you show what changed for rubygem-sprockets-rails compared with
the previous report one week ago?

https://lists.fedoraproject.org/archives/list/devel@lists.fedoraproject.org/thread/BEYCREMETV6DDVFMLKOE5HR2XWEWBPFE/ 



The above report seems to be saying that no package depends on 
rubygem-sprockets-rails,

but this time many packages depend on rubygem-sprockets-rails.


Only 4 packages directly require rubygem(sprockets-rails):

rubygem-actionmailbox
rubygem-actionmailbox-7.0.2.3-2.fc37.src

rubygem-activestorage
rubygem-activestorage-7.0.2.3-1.fc37.src

rubygem-railties
rubygem-railties-7.0.2.3-2.fc37.src

rubygem-sassc-rails
rubygem-sassc-rails-2.1.2-4.fc36.noarch
rubygem-sassc-rails-2.1.2-4.fc36.src


I've checked and from the spec files, it seems that they always did.

I've repoqueried this compose 
https://kojipkgs.fedoraproject.org/compose/rawhide/Fedora-Rawhide-20220719.n.0/ 
and it seems that the requirements were there.


The only difference, it seems, is that rubygem-image_processing was part of the 
FTBFS packages set before and its dep tree already included those packages, so 
the script decided not to report them twice :(


https://pagure.io/releng/blob/c9a08daa74/f/scripts/find_unblocked_orphans.py#_419

When I remove this thing, and re-add rubygem-image_processing to the list of 
FTBFS packages, I see rubygem-sprockets-rails's dependencies reported.


I guess we should fix the script, this is dangerous.

And if you think this justifies not retiring rubygem-sprockets-rails this 
round, I am OK with that.


Thanks for spotting this. No other remaining packages here seem to be affected 
by this now.


--
Miro Hrončok
--
Phone: +420777974800
IRC: mhroncok
___
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 on the list, report it: 
https://pagure.io/fedora-infrastructure


Re: List of long term FTBFS packages to be retired in August

2022-07-26 Thread Mamoru TASAKA

Miro Hrončok wrote on 2022/07/26 21:28:

Dear maintainers.

Based on the current fail to build from source policy, the following packages
will be retired from Fedora 37 approximately one week before branching (August 
2022).

Policy: 
https://docs.fedoraproject.org/en-US/fesco/Fails_to_build_from_source_Fails_to_install/

The packages in rawhide were not successfully built at least since Fedora 35.

This report is based on dist tags.

Packages collected via:
https://github.com/hroncok/fedora-report-ftbfs-retirements/blob/master/ftbfs-retirements.ipynb

If you see a package that was built, please let me know.
If you see a package that should be exempted from the process, please let me 
know and we can work together to get a FESCo approval for that.

If you see a package that can be rebuilt, please do so.

  Package   (co)maintainers
=
rubygem-sprockets-rails  jaruga, pvalena, ruby-packagers-sig

Depending on: rubygem-sprockets-rails (22)
 rubygem-actionmailbox (maintained by: pvalena)
     rubygem-actionmailbox-7.0.2.3-2.fc37.src requires 
rubygem(sprockets-rails) = 3.2.2

 rubygem-activestorage (maintained by: ruby-packagers-sig, vondruch)
     rubygem-activestorage-7.0.2.3-1.fc37.src requires 
rubygem(sprockets-rails) = 3.2.2

 rubygem-railties (maintained by: mmorsi, pvalena, tdawson, vondruch)
     rubygem-railties-7.0.2.3-2.fc37.src requires rubygem(sprockets-rails) 
= 3.2.2

 rubygem-sassc-rails (maintained by: pvalena)
     rubygem-sassc-rails-2.1.2-4.fc36.noarch requires 
rubygem(sprockets-rails) = 3.2.2
     rubygem-sassc-rails-2.1.2-4.fc36.src requires rubygem(sprockets-rails) 
= 3.2.2

 rubygem-rails (maintained by: jstribny, kanarip, mmorsi, mtasaka, pvalena, 
ruby-packagers-sig, sseago, tdawson, vondruch)
     rubygem-rails-1:7.0.2.3-2.fc37.noarch requires rubygem(actionmailbox) 
= 7.0.2.3

 rubygem-rspec-rails (maintained by: clalance, vondruch)
     rubygem-rspec-rails-5.1.1-2.fc37.src requires rubygem(actionmailbox) = 
7.0.2.3

 rubygem-actiontext (maintained by: pvalena)
     rubygem-actiontext-7.0.2.3-2.fc37.noarch requires 
rubygem(activestorage) = 7.0.2.3
     rubygem-actiontext-7.0.2.3-2.fc37.src requires rubygem(activestorage) 
= 7.0.2.3

 rubygem-actionpack (maintained by: jaruga, jstribny, kanarip, mmorsi, 
pvalena, ruby-packagers-sig, sseago, vondruch)
     rubygem-actionpack-1:7.0.2.3-1.fc37.src requires rubygem(railties) = 
7.0.2.3

 rubygem-actionview (maintained by: jaruga, pvalena, ruby-packagers-sig)
     rubygem-actionview-7.0.2.3-1.fc37.src requires rubygem(railties) = 
7.0.2.3

 rubygem-activemodel (maintained by: jstribny, mmorsi, pvalena, tdawson, 
vondruch)
     rubygem-activemodel-7.0.2.3-2.fc37.src requires rubygem(railties) = 
7.0.2.3

 rubygem-ammeter (maintained by: jstribny, ruby-packagers-sig, vondruch)
     rubygem-ammeter-1.1.5-3.fc37.noarch requires rubygem(railties) = 
7.0.2.3
     rubygem-ammeter-1.1.5-3.fc37.src requires rubygem(railties) = 7.0.2.3

 rubygem-font-awesome-rails (maintained by: abradshaw, ckyriakidou, evgeni, 
fale, snecker)
     rubygem-font-awesome-rails-4.7.0.8-2.fc37.noarch requires 
rubygem(railties) = 7.0.2.3
     rubygem-font-awesome-rails-4.7.0.8-2.fc37.src requires 
rubygem(railties) = 7.0.2.3

 rubygem-generator_spec (maintained by: ilgrad)
     rubygem-generator_spec-0.9.4-12.fc37.noarch requires rubygem(railties) 
= 7.0.2.3
     rubygem-generator_spec-0.9.4-12.fc37.src requires rubygem(railties) = 
7.0.2.3

 rubygem-globalid (maintained by: jaruga, pvalena, ruby-packagers-sig)
     rubygem-globalid-1.0.0-3.fc37.src requires rubygem(railties) = 7.0.2.3

 rubygem-haml (maintained by: kanarip, pvalena)
     rubygem-haml-5.2.2-3.fc37.src requires rubygem(railties) = 7.0.2.3

 rubygem-importmap-rails (maintained by: pvalena)
     rubygem-importmap-rails-1.0.3-2.fc37.noarch requires rubygem(railties) 
= 7.0.2.3

 rubygem-jbuilder (maintained by: pvalena, vondruch)
     rubygem-jbuilder-2.11.5-2.fc37.src requires rubygem(railties) = 7.0.2.3

 rubygem-jquery-rails (maintained by: jstribny, tdawson, vondruch)
     rubygem-jquery-rails-4.4.0-3.fc37.noarch requires rubygem(railties) = 
7.0.2.3

 rubygem-rails-controller-testing (maintained by: valtri)
     rubygem-rails-controller-testing-1.0.5-6.fc37.src requires 
rubygem(railties) = 7.0.2.3

 rubygem-sass-twitter-bootstrap (maintained by: tdawson)
     rubygem-sass-twitter-bootstrap-2.3.0-16.fc37.noarch requires 
rubygem(railties) = 7.0.2.3

 rubygem-slim (maintained by: vondruch)
     rubygem-slim-4.1.0-6.fc37.src requires rubygem(railties) = 7.0.2.3

 rubygem-web-console (maintained by: jaruga, ruby-packagers-sig, vondruch)
     rubygem-web-console-4.1.0-4.fc36.noarch requires rubygem(

List of long term FTBFS packages to be retired in August

2022-07-26 Thread Miro Hrončok

Dear maintainers.

Based on the current fail to build from source policy, the following packages
will be retired from Fedora 37 approximately one week before branching (August 
2022).


Policy: 
https://docs.fedoraproject.org/en-US/fesco/Fails_to_build_from_source_Fails_to_install/


The packages in rawhide were not successfully built at least since Fedora 35.

This report is based on dist tags.

Packages collected via:
https://github.com/hroncok/fedora-report-ftbfs-retirements/blob/master/ftbfs-retirements.ipynb

If you see a package that was built, please let me know.
If you see a package that should be exempted from the process, please let me 
know and we can work together to get a FESCo approval for that.


If you see a package that can be rebuilt, please do so.

 Package   (co)maintainers
=
golang-grpc-go4  eclipseo, go-sig, jchaloup
lancer   willb
php-aws-sdk3 lcts
php-pimple   lcts
recorder ddd
rubygem-coffee-rails jaruga, ruby-packagers-sig, vondruch
rubygem-minitest-reporters   pvalena
rubygem-sprockets-rails  jaruga, pvalena, ruby-packagers-sig
tinygo   go-sig, qulogic
uom-parent   lberk, mgoodwin, nathans
xs   petersen


The following packages require above mentioned packages:
Depending on: golang-grpc-go4 (1)
golang-x-build (maintained by: eclipseo, go-sig, jchaloup)
		golang-x-build-0-0.19.20201229git0a4bf69.fc35.src requires 
golang(grpc.go4.org) = 0-0.9.20180421git11d0a25.fc34, 
golang(grpc.go4.org/codes) = 0-0.9.20180421git11d0a25.fc34
		golang-x-build-devel-0-0.19.20201229git0a4bf69.fc35.noarch requires 
golang(grpc.go4.org) = 0-0.9.20180421git11d0a25.fc34, 
golang(grpc.go4.org/codes) = 0-0.9.20180421git11d0a25.fc34


Depending on: rubygem-sprockets-rails (22)
rubygem-actionmailbox (maintained by: pvalena)
		rubygem-actionmailbox-7.0.2.3-2.fc37.src requires rubygem(sprockets-rails) = 
3.2.2


rubygem-activestorage (maintained by: ruby-packagers-sig, vondruch)
		rubygem-activestorage-7.0.2.3-1.fc37.src requires rubygem(sprockets-rails) = 
3.2.2


rubygem-railties (maintained by: mmorsi, pvalena, tdawson, vondruch)
rubygem-railties-7.0.2.3-2.fc37.src requires 
rubygem(sprockets-rails) = 3.2.2

rubygem-sassc-rails (maintained by: pvalena)
rubygem-sassc-rails-2.1.2-4.fc36.noarch requires 
rubygem(sprockets-rails) = 3.2.2
rubygem-sassc-rails-2.1.2-4.fc36.src requires 
rubygem(sprockets-rails) = 3.2.2

	rubygem-rails (maintained by: jstribny, kanarip, mmorsi, mtasaka, pvalena, 
ruby-packagers-sig, sseago, tdawson, vondruch)

rubygem-rails-1:7.0.2.3-2.fc37.noarch requires 
rubygem(actionmailbox) = 7.0.2.3

rubygem-rspec-rails (maintained by: clalance, vondruch)
rubygem-rspec-rails-5.1.1-2.fc37.src requires 
rubygem(actionmailbox) = 7.0.2.3

rubygem-actiontext (maintained by: pvalena)
		rubygem-actiontext-7.0.2.3-2.fc37.noarch requires rubygem(activestorage) = 
7.0.2.3

rubygem-actiontext-7.0.2.3-2.fc37.src requires 
rubygem(activestorage) = 7.0.2.3

	rubygem-actionpack (maintained by: jaruga, jstribny, kanarip, mmorsi, pvalena, 
ruby-packagers-sig, sseago, vondruch)

rubygem-actionpack-1:7.0.2.3-1.fc37.src requires 
rubygem(railties) = 7.0.2.3

rubygem-actionview (maintained by: jaruga, pvalena, ruby-packagers-sig)
rubygem-actionview-7.0.2.3-1.fc37.src requires 
rubygem(railties) = 7.0.2.3

rubygem-activemodel (maintained by: jstribny, mmorsi, pvalena, tdawson, 
vondruch)
rubygem-activemodel-7.0.2.3-2.fc37.src requires 
rubygem(railties) = 7.0.2.3

rubygem-ammeter (maintained by: jstribny, ruby-packagers-sig, vondruch)
rubygem-ammeter-1.1.5-3.fc37.noarch requires rubygem(railties) 
= 7.0.2.3
rubygem-ammeter-1.1.5-3.fc37.src requires rubygem(railties) = 
7.0.2.3

	rubygem-font-awesome-rails (maintained by: abradshaw, ckyriakidou, evgeni, 
fale, snecker)
		rubygem-font-awesome-rails-4.7.0.8-2.fc37.noarch requires rubygem(railties) = 
7.0.2.3
		rubygem-font-awesome-rails-4.7.0.8-2.fc37.src requires rubygem(railties) = 
7.0.2.3


rubygem-generator_spec (maintained by: ilgrad)
rubygem-generator_spec-0.9.4-12.fc37.noarch requires 
rubygem(railties) = 7.0.2.3
rubygem-generator_spec-0.9.4-12.fc37.src requires 
rubygem(railties) = 7.0.2.3

rubygem-globalid (maintained by: jaruga, pvalena, ruby-packagers-sig)
rubygem-globalid-1.0.0-3.fc37.src requires rubygem(railties) = 
7.0.2.3

rubygem-haml (maintained by: kanarip, pvalena)
rub

Re: List of long term FTBFS packages to be retired in August

2022-07-20 Thread Ewoud Kohl van Wijngaarden

On Wed, Jul 20, 2022 at 10:30:14AM +0200, Vít Ondruch wrote:


Dne 19. 07. 22 v 9:58 Ewoud Kohl van Wijngaarden napsal(a):

On Tue, Jul 19, 2022 at 09:48:33AM +0200, Vít Ondruch wrote:

Dear Ewoud,


Dne 12. 07. 22 v 15:16 Ewoud Kohl van Wijngaarden napsal(a):

On Tue, Jul 12, 2022 at 01:03:59PM +0200, Miro Hrončok wrote:

rubygem-bundler_ext jaruga, ruby-packagers-sig, vondruch


I have an interest in this package so I started to look into 
this. It mostly comes down to porting to rspec 3 which I have 
passing.


https://github.com/bundlerext/bundler_ext/pull/23 is the 
upstream PR, I'll look into a packaging PR too.



Would you mind to take over the package from me? I inherited the 
package from previous maintainer together with other packages and 
I was never doing the right job maintaining it, mainly because I 
am not user of the package.


I'd be happy to take it over.



I have transferred the package to you. Thx I lot.


Thanks! I just managed to get an upstream 0.4.2 release out with all the 
fixes and currently pushing that to Fedora. That should resolve it.

___
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 on the list, report it: 
https://pagure.io/fedora-infrastructure


Re: List of long term FTBFS packages to be retired in August

2022-07-20 Thread Vít Ondruch


Dne 19. 07. 22 v 9:58 Ewoud Kohl van Wijngaarden napsal(a):

On Tue, Jul 19, 2022 at 09:48:33AM +0200, Vít Ondruch wrote:

Dear Ewoud,


Dne 12. 07. 22 v 15:16 Ewoud Kohl van Wijngaarden napsal(a):

On Tue, Jul 12, 2022 at 01:03:59PM +0200, Miro Hrončok wrote:

rubygem-bundler_ext jaruga, ruby-packagers-sig, vondruch


I have an interest in this package so I started to look into this. 
It mostly comes down to porting to rspec 3 which I have passing.


https://github.com/bundlerext/bundler_ext/pull/23 is the upstream 
PR, I'll look into a packaging PR too.



Would you mind to take over the package from me? I inherited the 
package from previous maintainer together with other packages and I 
was never doing the right job maintaining it, mainly because I am not 
user of the package.


I'd be happy to take it over.



I have transferred the package to you. Thx I lot.

Of course if you need some assistance, please let me know.


Vít




OpenPGP_signature
Description: OpenPGP digital signature
___
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 on the list, report it: 
https://pagure.io/fedora-infrastructure


Re: List of long term FTBFS packages to be retired in August

2022-07-19 Thread Kevin Kofler via devel
Miro Hrončok wrote:
> klamav kkofler
> koffice-kivio  kkofler, rdieter

These are fixed now, successfully built in Rawhide, and I have closed the 
bugs. So they should disappear from your report next time.

Kevin Kofler
___
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 on the list, report it: 
https://pagure.io/fedora-infrastructure


List of long term FTBFS packages to be retired in August

2022-07-19 Thread Miro Hrončok

Dear maintainers.

Based on the current fail to build from source policy, the following packages
will be retired from Fedora 37 approximately one week before branching (August 
2022).


Policy: 
https://docs.fedoraproject.org/en-US/fesco/Fails_to_build_from_source_Fails_to_install/


The packages in rawhide were not successfully built at least since Fedora 35.

This report is based on dist tags.

Packages collected via:
https://github.com/hroncok/fedora-report-ftbfs-retirements/blob/master/ftbfs-retirements.ipynb

If you see a package that was built, please let me know.
If you see a package that should be exempted from the process, please let me 
know and we can work together to get a FESCo approval for that.


If you see a package that can be rebuilt, please do so.

 Package   (co)maintainers

golang-grpc-go4eclipseo, go-sig, jchaloup
klamav kkofler
koffice-kivio  kkofler, rdieter
lancer willb
php-aws-sdk3   lcts
php-pimple lcts
recorder   ddd
rubygem-bundler_extjaruga, ruby-packagers-sig, vondruch
rubygem-coffee-rails   jaruga, ruby-packagers-sig, vondruch
rubygem-image_processing   pvalena
rubygem-minitest-reporters pvalena
rubygem-sprockets-railsjaruga, pvalena, ruby-packagers-sig
tinygo go-sig, qulogic
uom-parent lberk, mgoodwin, nathans
xs petersen


The following packages require above mentioned packages:
Depending on: golang-grpc-go4 (1)
golang-x-build (maintained by: eclipseo, go-sig, jchaloup)
		golang-x-build-0-0.19.20201229git0a4bf69.fc35.src requires 
golang(grpc.go4.org) = 0-0.9.20180421git11d0a25.fc34, 
golang(grpc.go4.org/codes) = 0-0.9.20180421git11d0a25.fc34
		golang-x-build-devel-0-0.19.20201229git0a4bf69.fc35.noarch requires 
golang(grpc.go4.org) = 0-0.9.20180421git11d0a25.fc34, 
golang(grpc.go4.org/codes) = 0-0.9.20180421git11d0a25.fc34


Depending on: rubygem-image_processing (28)
rubygem-activestorage (maintained by: ruby-packagers-sig, vondruch)
		rubygem-activestorage-7.0.2.3-1.fc37.src requires rubygem(image_processing) = 
1.11.0


rubygem-actionmailbox (maintained by: pvalena)
		rubygem-actionmailbox-7.0.2.3-1.fc37.noarch requires rubygem(activestorage) = 
7.0.2.3
		rubygem-actionmailbox-7.0.2.3-1.fc37.src requires rubygem(activestorage) = 
7.0.2.3


rubygem-actiontext (maintained by: pvalena)
		rubygem-actiontext-7.0.2.3-1.fc37.noarch requires rubygem(activestorage) = 
7.0.2.3

rubygem-actiontext-7.0.2.3-1.fc37.src requires 
rubygem(activestorage) = 7.0.2.3

	rubygem-rails (maintained by: jstribny, kanarip, mmorsi, mtasaka, pvalena, 
ruby-packagers-sig, sseago, tdawson, vondruch)

rubygem-rails-1:7.0.2.3-1.fc37.noarch requires 
rubygem(activestorage) = 7.0.2.3

rubygem-railties (maintained by: mmorsi, pvalena, tdawson, vondruch)
rubygem-railties-7.0.2.3-1.fc37.src requires 
rubygem(activestorage) = 7.0.2.3

rubygem-rspec-rails (maintained by: clalance, vondruch)
rubygem-rspec-rails-5.1.1-1.fc37.src requires 
rubygem(actionmailbox) = 7.0.2.3

rubygem-apipie-rails (maintained by: ruby-packagers-sig, vondruch)
rubygem-apipie-rails-0.5.18-5.fc36.noarch requires 
rubygem(rails) = 7.0.2.3

rubygem-declarative_authorization (maintained by: mcpierce)
		rubygem-declarative_authorization-0.5.7-17.fc36.noarch requires 
rubygem(rails) = 7.0.2.3


rubygem-importmap-rails (maintained by: pvalena)
rubygem-importmap-rails-1.0.3-1.fc37.src requires 
rubygem(rails) = 7.0.2.3

rubygem-sass-rails (maintained by: ruby-packagers-sig, tdawson, 
vondruch)
rubygem-sass-rails-6.0.0-4.fc36.src requires rubygem(rails) = 
7.0.2.3

rubygem-shoulda (maintained by: stahnma, tdawson)
rubygem-shoulda-3.6.0-10.fc36.src requires rubygem(rails) = 
7.0.2.3

rubygem-shoulda-context (maintained by: tdawson, vondruch)
rubygem-shoulda-context-1.2.2-11.fc36.src requires 
rubygem(rails) = 7.0.2.3

rubygem-shoulda-matchers (maintained by: vondruch)
rubygem-shoulda-matchers-4.5.1-3.fc36.src requires 
rubygem(rails) = 7.0.2.3

	rubygem-actionpack (maintained by: jaruga, jstribny, kanarip, mmorsi, pvalena, 
ruby-packagers-sig, sseago, vondruch)

rubygem-actionpack-1:7.0.2.3-1.fc37.src requires 
rubygem(railties) = 7.0.2.3

rubygem-actionview (maintained by: jaruga, pvalena, ruby-packagers-sig)
rubygem-actionview-7.0.2.3-1.fc37.src requires 
rubygem(railties) = 7.0.2.3

rubygem-activemodel (maintained by: jstribny, mmor

Re: List of long term FTBFS packages to be retired in August

2022-07-19 Thread Ewoud Kohl van Wijngaarden

On Tue, Jul 19, 2022 at 05:17:44PM +0900, Mamoru TASAKA wrote:

Ewoud Kohl van Wijngaarden wrote on 2022/07/19 16:58:

On Tue, Jul 19, 2022 at 09:48:33AM +0200, Vít Ondruch wrote:

Dear Ewoud,


Dne 12. 07. 22 v 15:16 Ewoud Kohl van Wijngaarden napsal(a):

On Tue, Jul 12, 2022 at 01:03:59PM +0200, Miro Hrončok wrote:

rubygem-bundler_ext    jaruga, ruby-packagers-sig, vondruch


I have an interest in this package so I started to look into this. It mostly 
comes down to porting to rspec 3 which I have passing.

https://github.com/bundlerext/bundler_ext/pull/23 is the upstream PR, I'll look 
into a packaging PR too.



Would you mind to take over the package from me? I inherited the package from 
previous maintainer together with other packages and I was never doing the 
right job maintaining it, mainly because I am not user of the package.


I'd be happy to take it over.


BTW are you working on this FTBFS? For now I've added minimum patches to make 
rubygem-bundler_ext rpm
build (with porting to rspec3) and I can commit these changes myself.


Right now I'm trying the upstream route first. I just sent an email to 
the listed contributors who still work for Red Hat to see about a new 
upstream release. That would be easier than carrying downstream patches. 
If not, we can go with a large downstream patch.

___
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 on the list, report it: 
https://pagure.io/fedora-infrastructure


Re: List of long term FTBFS packages to be retired in August

2022-07-19 Thread Mamoru TASAKA

Ewoud Kohl van Wijngaarden wrote on 2022/07/19 16:58:

On Tue, Jul 19, 2022 at 09:48:33AM +0200, Vít Ondruch wrote:

Dear Ewoud,


Dne 12. 07. 22 v 15:16 Ewoud Kohl van Wijngaarden napsal(a):

On Tue, Jul 12, 2022 at 01:03:59PM +0200, Miro Hrončok wrote:

rubygem-bundler_ext    jaruga, ruby-packagers-sig, vondruch


I have an interest in this package so I started to look into this. It mostly 
comes down to porting to rspec 3 which I have passing.

https://github.com/bundlerext/bundler_ext/pull/23 is the upstream PR, I'll look 
into a packaging PR too.



Would you mind to take over the package from me? I inherited the package from 
previous maintainer together with other packages and I was never doing the 
right job maintaining it, mainly because I am not user of the package.


I'd be happy to take it over.


BTW are you working on this FTBFS? For now I've added minimum patches to make 
rubygem-bundler_ext rpm
build (with porting to rspec3) and I can commit these changes myself.

Regards,
Mamoru
___
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 on the list, report it: 
https://pagure.io/fedora-infrastructure


Re: List of long term FTBFS packages to be retired in August

2022-07-19 Thread Ewoud Kohl van Wijngaarden

On Tue, Jul 19, 2022 at 09:48:33AM +0200, Vít Ondruch wrote:

Dear Ewoud,


Dne 12. 07. 22 v 15:16 Ewoud Kohl van Wijngaarden napsal(a):

On Tue, Jul 12, 2022 at 01:03:59PM +0200, Miro Hrončok wrote:
rubygem-bundler_ext    jaruga, 
ruby-packagers-sig, vondruch


I have an interest in this package so I started to look into this. 
It mostly comes down to porting to rspec 3 which I have passing.


https://github.com/bundlerext/bundler_ext/pull/23 is the upstream 
PR, I'll look into a packaging PR too.



Would you mind to take over the package from me? I inherited the 
package from previous maintainer together with other packages and I 
was never doing the right job maintaining it, mainly because I am not 
user of the package.


I'd be happy to take it over.
___
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 on the list, report it: 
https://pagure.io/fedora-infrastructure


Re: List of long term FTBFS packages to be retired in August

2022-07-19 Thread Vít Ondruch

Dear Ewoud,


Dne 12. 07. 22 v 15:16 Ewoud Kohl van Wijngaarden napsal(a):

On Tue, Jul 12, 2022 at 01:03:59PM +0200, Miro Hrončok wrote:

Dear maintainers.

Based on the current fail to build from source policy, the following 
packages
will be retired from Fedora 37 approximately one week before 
branching (August 2022).


Policy: 
https://docs.fedoraproject.org/en-US/fesco/Fails_to_build_from_source_Fails_to_install/


The packages in rawhide were not successfully built at least since 
Fedora 35.


This report is based on dist tags.

Packages collected via:
https://github.com/hroncok/fedora-report-ftbfs-retirements/blob/master/ftbfs-retirements.ipynb 



If you see a package that was built, please let me know.
If you see a package that should be exempted from the process, please 
let me know and we can work together to get a FESCo approval for that.


If you see a package that can be rebuilt, please do so.

   Package    (co)maintainers
=== 

rubygem-bundler_ext    jaruga, 
ruby-packagers-sig, vondruch


I have an interest in this package so I started to look into this. It 
mostly comes down to porting to rspec 3 which I have passing.


https://github.com/bundlerext/bundler_ext/pull/23 is the upstream PR, 
I'll look into a packaging PR too.



Would you mind to take over the package from me? I inherited the package 
from previous maintainer together with other packages and I was never 
doing the right job maintaining it, mainly because I am not user of the 
package.



Vít





OpenPGP_signature
Description: OpenPGP digital signature
___
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 on the list, report it: 
https://pagure.io/fedora-infrastructure


Re: List of long term FTBFS packages to be retired in August

2022-07-12 Thread Maxwell G via devel
On 22/07/12 01:03PM, Miro Hrončok wrote:
> golang-github-apparentlymart- textseg-12   eclipseo, go-sig

I have successfully rebuilt this: 
https://bodhi.fedoraproject.org/updates/FEDORA-2022-07d3083c35

-- 
Thanks,

Maxwell G (@gotmax23)
Pronouns: He/Him/His


signature.asc
Description: PGP signature
___
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 on the list, report it: 
https://pagure.io/fedora-infrastructure


Re: List of long term FTBFS packages to be retired in August

2022-07-12 Thread Ewoud Kohl van Wijngaarden

On Tue, Jul 12, 2022 at 01:03:59PM +0200, Miro Hrončok wrote:

Dear maintainers.

Based on the current fail to build from source policy, the following packages
will be retired from Fedora 37 approximately one week before branching 
(August 2022).


Policy: 
https://docs.fedoraproject.org/en-US/fesco/Fails_to_build_from_source_Fails_to_install/

The packages in rawhide were not successfully built at least since Fedora 35.

This report is based on dist tags.

Packages collected via:
https://github.com/hroncok/fedora-report-ftbfs-retirements/blob/master/ftbfs-retirements.ipynb

If you see a package that was built, please let me know.
If you see a package that should be exempted from the process, please 
let me know and we can work together to get a FESCo approval for that.


If you see a package that can be rebuilt, please do so.

   Package(co)maintainers
===
rubygem-bundler_extjaruga, ruby-packagers-sig, vondruch


I have an interest in this package so I started to look into this. It 
mostly comes down to porting to rspec 3 which I have passing.


https://github.com/bundlerext/bundler_ext/pull/23 is the upstream PR, 
I'll look into a packaging PR too.

___
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 on the list, report it: 
https://pagure.io/fedora-infrastructure


List of long term FTBFS packages to be retired in August

2022-07-12 Thread Miro Hrončok

Dear maintainers.

Based on the current fail to build from source policy, the following packages
will be retired from Fedora 37 approximately one week before branching (August 
2022).


Policy: 
https://docs.fedoraproject.org/en-US/fesco/Fails_to_build_from_source_Fails_to_install/


The packages in rawhide were not successfully built at least since Fedora 35.

This report is based on dist tags.

Packages collected via:
https://github.com/hroncok/fedora-report-ftbfs-retirements/blob/master/ftbfs-retirements.ipynb

If you see a package that was built, please let me know.
If you see a package that should be exempted from the process, please let me 
know and we can work together to get a FESCo approval for that.


If you see a package that can be rebuilt, please do so.

Package(co)maintainers
===
golang-github-apparentlymart- textseg-12   eclipseo, go-sig
golang-grpc-go4eclipseo, go-sig, jchaloup
klamav kkofler
koffice-kivio  kkofler, rdieter
lancer willb
libgnomecanvasmm26 nphilipp, verdurin
libowfat   cicku, kevin
opari2 loveshack, orion
openjpeg   oliver, phracek, rdieter
pesign-test-appjavierm, pjones
php-aws-sdk3   lcts
php-pimple lcts
recorder   ddd
rubygem-bundler_extjaruga, ruby-packagers-sig, vondruch
rubygem-coffee-rails   jaruga, ruby-packagers-sig, vondruch
rubygem-image_processing   pvalena
rubygem-minitest-reporters pvalena
rubygem-sprockets-railsjaruga, pvalena, ruby-packagers-sig
tinygo go-sig, qulogic
uom-parent lberk, mgoodwin, nathans
xs petersen

The following packages require above mentioned packages:
Depending on: golang-github-apparentlymart-textseg-12 (15)
golang-github-hashicorp-hcl-2 (maintained by: eclipseo, go-sig)
		golang-github-hashicorp-hcl-2-2.8.2-4.fc36.src requires 
golang(github.com/apparentlymart/go-textseg/v12/textseg) = 12.0.0-3.fc34
		golang-github-hashicorp-hcl-2-devel-2.8.2-4.fc36.noarch requires 
golang(github.com/apparentlymart/go-textseg/v12/textseg) = 12.0.0-3.fc34


golang-ariga-atlas (maintained by: eclipseo, go-sig)
		golang-ariga-atlas-0.3.6-3.fc37.src requires 
golang(github.com/hashicorp/hcl/v2) = 2.8.2-4.fc36, 
golang(github.com/hashicorp/hcl/v2/gohcl) = 2.8.2-4.fc36, 
golang(github.com/hashicorp/hcl/v2/hclparse) = 2.8.2-4.fc36, 
golang(github.com/hashicorp/hcl/v2/hclsyntax) = 2.8.2-4.fc36, 
golang(github.com/hashicorp/hcl/v2/hclwrite) = 2.8.2-4.fc36
		golang-ariga-atlas-devel-0.3.6-3.fc37.noarch requires 
golang(github.com/hashicorp/hcl/v2) = 2.8.2-4.fc36, 
golang(github.com/hashicorp/hcl/v2/gohcl) = 2.8.2-4.fc36, 
golang(github.com/hashicorp/hcl/v2/hclparse) = 2.8.2-4.fc36, 
golang(github.com/hashicorp/hcl/v2/hclsyntax) = 2.8.2-4.fc36, 
golang(github.com/hashicorp/hcl/v2/hclwrite) = 2.8.2-4.fc36


golang-github-alecthomas-kong-hcl (maintained by: eclipseo, go-sig)
		golang-github-alecthomas-kong-hcl-1:1.0.1-3.fc36.src requires 
golang(github.com/hashicorp/hcl/v2) = 2.8.2-4.fc36, 
golang(github.com/hashicorp/hcl/v2/gohcl) = 2.8.2-4.fc36, 
golang(github.com/hashicorp/hcl/v2/hclparse) = 2.8.2-4.fc36, 
golang(github.com/hashicorp/hcl/v2/hclsyntax) = 2.8.2-4.fc36
		golang-github-alecthomas-kong-hcl-devel-1:1.0.1-3.fc36.noarch requires 
golang(github.com/hashicorp/hcl/v2) = 2.8.2-4.fc36, 
golang(github.com/hashicorp/hcl/v2/gohcl) = 2.8.2-4.fc36, 
golang(github.com/hashicorp/hcl/v2/hclparse) = 2.8.2-4.fc36, 
golang(github.com/hashicorp/hcl/v2/hclsyntax) = 2.8.2-4.fc36


golang-github-alecthomas-kong-hcl-2 (maintained by: eclipseo, go-sig)
		golang-github-alecthomas-kong-hcl-2-2.0.0-6.20210731gitd3b99e5.fc36.src 
requires golang(github.com/hashicorp/hcl/v2) = 2.8.2-4.fc36, 
golang(github.com/hashicorp/hcl/v2/gohcl) = 2.8.2-4.fc36, 
golang(github.com/hashicorp/hcl/v2/hclparse) = 2.8.2-4.fc36, 
golang(github.com/hashicorp/hcl/v2/hclsyntax) = 2.8.2-4.fc36
	 
golang-github-alecthomas-kong-hcl-2-devel-2.0.0-6.20210731gitd3b99e5.fc36.noarch requires 
golang(github.com/hashicorp/hcl/v2) = 2.8.2-4.fc36, 
golang(github.com/hashicorp/hcl/v2/gohcl) = 2.8.2-4.fc36, 
golang(github.com/hashicorp/hcl/v2/hclparse) = 2.8.2-4.fc36, 
golang(github.com/hashicorp/hcl/v2/hclsyntax) = 2.8.2-4.fc36


golang-entgo-ent (maintained by: salimma)
		golang-entgo-ent-0.10.0-4.fc37.src requires 
golang(ariga.io/atlas/sql/migrate) = 0.3.6-3.fc37, 
golang(ariga.io/atlas/sql/mysql) 

List of long term FTBFS packages to be retired in August

2021-07-20 Thread Miro Hrončok

Dear maintainers.

Based on the current fail to build from source policy, the following packages
will be retired from Fedora 35 approximately one week before branching (August 
2021).


Policy: 
https://docs.fedoraproject.org/en-US/fesco/Fails_to_build_from_source_Fails_to_install/


The packages in rawhide were not successfully built at least since Fedora 32.

This report is based on dist tags.

Packages collected via:
https://github.com/hroncok/fedora-report-ftbfs-retirements/blob/master/ftbfs-retirements.ipynb

If you see a package that was built, please let me know.
If you see a package that should be exempted from the process, please let me 
know and we can work together to get a FESCo approval for that.


If you see a package that can be rebuilt, please do so.

 Package  (co)maintainersLatest build
==
cardpeek kalev   Fedora 32
percona-xtrabackup   slaanesh, slankes   Fedora 32
sugar-view-slidescallkalpa, chimosky, pbrobinson, tuxbrewr   Fedora 31

The following packages require above mentioned packages:
Depending on: percona-xtrabackup (1)
holland (maintained by: immanetize, jeffreyness, survient)
holland-xtrabackup.noarch requires /usr/bin/xtrabackup

Affected (co)maintainers
callkalpa: sugar-view-slides
chimosky: sugar-view-slides
immanetize: percona-xtrabackup
jeffreyness: percona-xtrabackup
kalev: cardpeek
pbrobinson: sugar-view-slides
slaanesh: percona-xtrabackup
slankes: percona-xtrabackup
survient: percona-xtrabackup
tuxbrewr: sugar-view-slides
___
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 on the list, report it: 
https://pagure.io/fedora-infrastructure


Re: List of long term FTBFS packages to be retired in August

2021-07-13 Thread Miro Hrončok

On 13. 07. 21 17:18, Miro Hrončok wrote:

...
If you see a package that can be rebuilt, please do so.

  Package  (co)maintainers    Latest build
=
...
proxyfuzz    psklenar    Fedora 32


Fixed.

--
Miro Hrončok
--
Phone: +420777974800
IRC: mhroncok
___
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 on the list, report it: 
https://pagure.io/fedora-infrastructure


List of long term FTBFS packages to be retired in August

2021-07-13 Thread Miro Hrončok

Dear maintainers.

Based on the current fail to build from source policy, the following packages
will be retired from Fedora 35 approximately one week before branching (August 
2021).


Policy: 
https://docs.fedoraproject.org/en-US/fesco/Fails_to_build_from_source_Fails_to_install/


The packages in rawhide were not successfully built at least since Fedora 32.

This report is based on dist tags.

Packages collected via:
https://github.com/hroncok/fedora-report-ftbfs-retirements/blob/master/ftbfs-retirements.ipynb

If you see a package that was built, please let me know.
If you see a package that should be exempted from the process, please let me 
know and we can work together to get a FESCo approval for that.


If you see a package that can be rebuilt, please do so.

 Package  (co)maintainersLatest build
=
cardpeek kalev   Fedora 32
percona-xtrabackup   slaanesh, slankes   Fedora 32
proxyfuzzpsklenarFedora 32
sugar-view-slidescallkalpa, chimosky, pbrobinson, tuxbrewr   Fedora 31

The following packages require above mentioned packages:
Depending on: percona-xtrabackup (1)
holland (maintained by: immanetize, jeffreyness, survient)
holland-xtrabackup.noarch requires /usr/bin/xtrabackup

Affected (co)maintainers
callkalpa: sugar-view-slides
chimosky: sugar-view-slides
immanetize: percona-xtrabackup
jeffreyness: percona-xtrabackup
kalev: cardpeek
pbrobinson: sugar-view-slides
psklenar: proxyfuzz
slaanesh: percona-xtrabackup
slankes: percona-xtrabackup
survient: percona-xtrabackup
tuxbrewr: sugar-view-slides
___
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 on the list, report it: 
https://pagure.io/fedora-infrastructure


Re: List of long term FTBFS packages to be retired in August

2021-07-07 Thread Miro Hrončok

On 07. 07. 21 15:26, Peter Robinson wrote:

sugar-view-slidescallkalpa, chimosky, pbrobinson, tuxbrewr   Fedora 31

I believe the sugar people are working on that now.


As said last week:

"""
Fails to install, fails to build since Fedora 32, was exempted from this policy 
last time with a promise of a fix.


Has many bugzillas 
https://bugzilla.redhat.com/buglist.cgi?component=sugar-view-slides&product=Fedora

"""

I don't understand what is the benefit of keeping this broken package in the 
repos. Why don't we retire it and unretire it once actually fixed?



zram pbrobinson  Fedora 32

That's fixed.


I am confused. Fixed how exactly? As said last week:

"""
This might not actually be a FTBFS, but simply a package that has not been 
built in 1.5 years.

It has a noautobuild file with:

> it's a couple of bash scripts, no need for rebuilds

I tend to disagree with that statement. The rebuilds are useful for:

 - new possible dependency generators
 - new possible buildroot policy scripts
 - new RPM/buildsystem features (compression, content signatures, etc.)

I think it's worth rebuilding it at least once in a year.
"""

See the thread for reaction(s):

https://lists.fedoraproject.org/archives/list/devel@lists.fedoraproject.org/thread/3RJHPPF66KQ4RPDHTADLKBJJLDW3CKE2/

--
Miro Hrončok
--
Phone: +420777974800
IRC: mhroncok
___
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 on the list, report it: 
https://pagure.io/fedora-infrastructure


Re: List of long term FTBFS packages to be retired in August

2021-07-07 Thread Peter Robinson
On Wed, Jul 7, 2021 at 9:45 AM Miro Hrončok  wrote:
>
> Dear maintainers.
>
> Based on the current fail to build from source policy, the following packages
> will be retired from Fedora 35 approximately one week before branching (August
> 2021).
>
> Policy:
> https://docs.fedoraproject.org/en-US/fesco/Fails_to_build_from_source_Fails_to_install/
>
> The packages in rawhide were not successfully built at least since Fedora 32.
>
> This report is based on dist tags.
>
> Packages collected via:
> https://github.com/hroncok/fedora-report-ftbfs-retirements/blob/master/ftbfs-retirements.ipynb
>
> If you see a package that was built, please let me know.
> If you see a package that should be exempted from the process, please let me
> know and we can work together to get a FESCo approval for that.
>
> If you see a package that can be rebuilt, please do so.
>
>   Package  (co)maintainersLatest build
> =
> cardpeek kalev   Fedora 32
> percona-xtrabackup   slaanesh, slankes   Fedora 32
> proxyfuzzpsklenarFedora 32
> sugar-view-slidescallkalpa, chimosky, pbrobinson, tuxbrewr   Fedora 31

I believe the sugar people are working on that now.

> zram pbrobinson  Fedora 32

That's fixed.

> The following packages require above mentioned packages:
> Depending on: percona-xtrabackup (1), status change: 2020-11-22 (32 weeks ago)
> holland (maintained by: immanetize, jeffreyness, survient)
> holland-xtrabackup-1.2.4-2.fc35.noarch requires 
> /usr/bin/xtrabackup
>
> Affected (co)maintainers
> callkalpa: sugar-view-slides
> chimosky: sugar-view-slides
> immanetize: percona-xtrabackup
> jeffreyness: percona-xtrabackup
> kalev: cardpeek
> pbrobinson: sugar-view-slides, zram
> psklenar: proxyfuzz
> slaanesh: percona-xtrabackup
> slankes: percona-xtrabackup
> survient: percona-xtrabackup
> tuxbrewr: sugar-view-slides
>
___
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 on the list, report it: 
https://pagure.io/fedora-infrastructure


List of long term FTBFS packages to be retired in August

2021-07-07 Thread Miro Hrončok

Dear maintainers.

Based on the current fail to build from source policy, the following packages
will be retired from Fedora 35 approximately one week before branching (August 
2021).


Policy: 
https://docs.fedoraproject.org/en-US/fesco/Fails_to_build_from_source_Fails_to_install/


The packages in rawhide were not successfully built at least since Fedora 32.

This report is based on dist tags.

Packages collected via:
https://github.com/hroncok/fedora-report-ftbfs-retirements/blob/master/ftbfs-retirements.ipynb

If you see a package that was built, please let me know.
If you see a package that should be exempted from the process, please let me 
know and we can work together to get a FESCo approval for that.


If you see a package that can be rebuilt, please do so.

 Package  (co)maintainersLatest build
=
cardpeek kalev   Fedora 32
percona-xtrabackup   slaanesh, slankes   Fedora 32
proxyfuzzpsklenarFedora 32
sugar-view-slidescallkalpa, chimosky, pbrobinson, tuxbrewr   Fedora 31
zram pbrobinson  Fedora 32

The following packages require above mentioned packages:
Depending on: percona-xtrabackup (1), status change: 2020-11-22 (32 weeks ago)
holland (maintained by: immanetize, jeffreyness, survient)
holland-xtrabackup-1.2.4-2.fc35.noarch requires 
/usr/bin/xtrabackup

Affected (co)maintainers
callkalpa: sugar-view-slides
chimosky: sugar-view-slides
immanetize: percona-xtrabackup
jeffreyness: percona-xtrabackup
kalev: cardpeek
pbrobinson: sugar-view-slides, zram
psklenar: proxyfuzz
slaanesh: percona-xtrabackup
slankes: percona-xtrabackup
survient: percona-xtrabackup
tuxbrewr: sugar-view-slides
___
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 on the list, report it: 
https://pagure.io/fedora-infrastructure


Re: List of long term FTBFS packages to be retired in August

2021-06-30 Thread Zbigniew Jędrzejewski-Szmek
On Wed, Jun 30, 2021 at 12:57:18PM -0400, Steve Grubb wrote:
> On Wednesday, June 30, 2021 5:43:10 AM EDT Zbigniew Jędrzejewski-Szmek wrote:
> > > >radamsa   huzaifas, mrniranjan
> > > >Fedora 32> 
> > > Has no bugzillas, the mass rebuilds builds never finished (they hang for
> > > days)
> >
> > It'd be sad to lose radamsa from the distro. I pushed a snapshot build.
> 
> Agreed and thanks. It has found many bugs in Fedora packages. However, I see 
> that the package's version has a '^' in it. I wonder if that is a typo?

That's just me hoping that 
https://pagure.io/packaging-committee/pull-request/1073
gets approved ;-]

Zbyszek
___
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 on the list, report it: 
https://pagure.io/fedora-infrastructure


Re: List of long term FTBFS packages to be retired in August

2021-06-30 Thread Steve Grubb
On Wednesday, June 30, 2021 5:43:10 AM EDT Zbigniew Jędrzejewski-Szmek wrote:
> > >radamsa   huzaifas, mrniranjan
> > >Fedora 32> 
> > Has no bugzillas, the mass rebuilds builds never finished (they hang for
> > days)
>
> It'd be sad to lose radamsa from the distro. I pushed a snapshot build.

Agreed and thanks. It has found many bugs in Fedora packages. However, I see 
that the package's version has a '^' in it. I wonder if that is a typo?

-Steve

___
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 on the list, report it: 
https://pagure.io/fedora-infrastructure


Re: List of long term FTBFS packages to be retired in August

2021-06-30 Thread Zbigniew Jędrzejewski-Szmek
On Wed, Jun 30, 2021 at 01:36:40AM +0200, Miro Hrončok wrote:
> On 30. 06. 21 1:32, Miro Hrončok wrote:
> >Dear maintainers.
> >
> >Based on the current fail to build from source policy, the following packages
> >will be retired from Fedora 35 approximately one week before
> >branching (August 2021).
> >
> >Policy: 
> >https://docs.fedoraproject.org/en-US/fesco/Fails_to_build_from_source_Fails_to_install/
> >
> >
> >The packages in rawhide were not successfully built at least since Fedora 32.
> >
> >This report is based on dist tags.
> >
> >Packages collected via:
> >https://github.com/hroncok/fedora-report-ftbfs-retirements/blob/master/ftbfs-retirements.ipynb
> >
> >
> >If you see a package that was built, please let me know.
> >If you see a package that should be exempted from the process,
> >please let me know and we can work together to get a FESCo
> >approval for that.
> >
> >If you see a package that can be rebuilt, please do so.
> >
> >     Package  (co)maintainers   Latest 
> > build
> >
> >cardpeek  kalev    Fedora 32
> 
> Has ASSIGNED bugzillas since Fedora 33:
> 
> https://bugzilla.redhat.com/show_bug.cgi?id=1863309
> https://bugzilla.redhat.com/show_bug.cgi?id=1923409
> 
> >percona-xtrabackup    slaanesh, slankes    Fedora 32
> 
> Has a MODIFIED bugzilla since Fedora 33:
> 
> https://bugzilla.redhat.com/show_bug.cgi?id=1865206
> 
> >php-opencloud-openstack   lcts Fedora 32
> 
> Has CLOSED (but not fixed) and NEW bugzillas since Fedora 33:
> 
> https://bugzilla.redhat.com/show_bug.cgi?id=1865221
> https://bugzilla.redhat.com/show_bug.cgi?id=1923428
> https://bugzilla.redhat.com/show_bug.cgi?id=1977297
> 
> >proxyfuzz psklenar Fedora 32
> 
> Had no bugzillas because it failed to build even the SRPM.
> I've opened one quite recently:
> 
> https://bugzilla.redhat.com/show_bug.cgi?id=1974327
> 
> >radamsa   huzaifas, mrniranjan Fedora 32
>
> Has no bugzillas, the mass rebuilds builds never finished (they hang for days)

It'd be sad to lose radamsa from the distro. I pushed a snapshot build.

> >sugar-view-slides callkalpa, chimosky, pbrobinson, Fedora 31
> >   tuxbrewr
> 
> Fails to install, fails to build since Fedora 32, was exempted from
> this policy last time with a promise of a fix.
> 
> Has many bugzillas 
> https://bugzilla.redhat.com/buglist.cgi?component=sugar-view-slides&product=Fedora
> 
> >zram  pbrobinson   Fedora 32
> 
> This might not actually be a FTBFS, but simply a package that has
> not been built in 1.5 years.
> It has a noautobuild file with:
> 
> > it's a couple of bash scripts, no need for rebuilds
> 
> I tend to disagree with that statement. The rebuilds are useful for:
> 
>  - new possible dependency generators
>  - new possible buildroot policy scripts
>  - new RPM/buildsystem features (compression, content signatures, etc.)
> 
> I think it's worth rebuilding it at least once in a year.

It's a case of "save a little bit of work for the machine by
generating more work for the humans" ;)
Yeah, a bad trade-off.

Zbyszek
___
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 on the list, report it: 
https://pagure.io/fedora-infrastructure


Re: List of long term FTBFS packages to be retired in August

2021-06-29 Thread Miro Hrončok

On 30. 06. 21 1:32, Miro Hrončok wrote:

Dear maintainers.

Based on the current fail to build from source policy, the following packages
will be retired from Fedora 35 approximately one week before branching (August 
2021).


Policy: 
https://docs.fedoraproject.org/en-US/fesco/Fails_to_build_from_source_Fails_to_install/ 



The packages in rawhide were not successfully built at least since Fedora 32.

This report is based on dist tags.

Packages collected via:
https://github.com/hroncok/fedora-report-ftbfs-retirements/blob/master/ftbfs-retirements.ipynb 



If you see a package that was built, please let me know.
If you see a package that should be exempted from the process, please let me 
know and we can work together to get a FESCo approval for that.


If you see a package that can be rebuilt, please do so.

     Package  (co)maintainers   Latest build

cardpeek  kalev    Fedora 32


Has ASSIGNED bugzillas since Fedora 33:

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


percona-xtrabackup    slaanesh, slankes    Fedora 32


Has a MODIFIED bugzilla since Fedora 33:

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


php-opencloud-openstack   lcts Fedora 32


Has CLOSED (but not fixed) and NEW bugzillas since Fedora 33:

https://bugzilla.redhat.com/show_bug.cgi?id=1865221
https://bugzilla.redhat.com/show_bug.cgi?id=1923428
https://bugzilla.redhat.com/show_bug.cgi?id=1977297


proxyfuzz psklenar Fedora 32


Had no bugzillas because it failed to build even the SRPM.
I've opened one quite recently:

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


radamsa   huzaifas, mrniranjan Fedora 32


Has no bugzillas, the mass rebuilds builds never finished (they hang for days)


sugar-view-slides callkalpa, chimosky, pbrobinson, Fedora 31
   tuxbrewr


Fails to install, fails to build since Fedora 32, was exempted from this policy 
last time with a promise of a fix.


Has many bugzillas 
https://bugzilla.redhat.com/buglist.cgi?component=sugar-view-slides&product=Fedora



zram  pbrobinson   Fedora 32


This might not actually be a FTBFS, but simply a package that has not been 
built in 1.5 years.

It has a noautobuild file with:

> it's a couple of bash scripts, no need for rebuilds

I tend to disagree with that statement. The rebuilds are useful for:

 - new possible dependency generators
 - new possible buildroot policy scripts
 - new RPM/buildsystem features (compression, content signatures, etc.)

I think it's worth rebuilding it at least once in a year.

--
Miro Hrončok
--
Phone: +420777974800
IRC: mhroncok
___
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 on the list, report it: 
https://pagure.io/fedora-infrastructure


List of long term FTBFS packages to be retired in August

2021-06-29 Thread Miro Hrončok

Dear maintainers.

Based on the current fail to build from source policy, the following packages
will be retired from Fedora 35 approximately one week before branching (August 
2021).


Policy: 
https://docs.fedoraproject.org/en-US/fesco/Fails_to_build_from_source_Fails_to_install/


The packages in rawhide were not successfully built at least since Fedora 32.

This report is based on dist tags.

Packages collected via:
https://github.com/hroncok/fedora-report-ftbfs-retirements/blob/master/ftbfs-retirements.ipynb

If you see a package that was built, please let me know.
If you see a package that should be exempted from the process, please let me 
know and we can work together to get a FESCo approval for that.


If you see a package that can be rebuilt, please do so.

Package  (co)maintainers   Latest build

cardpeek  kalevFedora 32
percona-xtrabackupslaanesh, slankesFedora 32
php-opencloud-openstack   lcts Fedora 32
proxyfuzz psklenar Fedora 32
radamsa   huzaifas, mrniranjan Fedora 32
sugar-view-slides callkalpa, chimosky, pbrobinson, Fedora 31
  tuxbrewr
zram  pbrobinson   Fedora 32


The following packages require above mentioned packages:
Depending on: percona-xtrabackup (1), status change: 2020-11-22 (31 weeks ago)
holland (maintained by: immanetize, jeffreyness, survient)
holland-xtrabackup-1.2.4-2.fc35.noarch requires 
/usr/bin/xtrabackup

Affected (co)maintainers
callkalpa: sugar-view-slides
chimosky: sugar-view-slides
huzaifas: radamsa
immanetize: percona-xtrabackup
jeffreyness: percona-xtrabackup
kalev: cardpeek
lcts: php-opencloud-openstack
mrniranjan: radamsa
pbrobinson: zram, sugar-view-slides
psklenar: proxyfuzz
slaanesh: percona-xtrabackup
slankes: percona-xtrabackup
survient: percona-xtrabackup
tuxbrewr: sugar-view-slides
___
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 on the list, report it: 
https://pagure.io/fedora-infrastructure


Re: List of long term FTBFS packages to be retired in August

2020-07-27 Thread Miro Hrončok

On 27. 07. 20 12:55, Vít Ondruch wrote:

I think this is a bit optimistic POV. I think that in most of the
packages, there won't be even "bundled(jquery)" which would let the SRT
report the proper trackers. But I hope you are right and I am wrong


The most might not. But even if some do, it will be better than nothing.

--
Miro Hrončok
--
Phone: +420777974800
IRC: mhroncok
___
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


Re: List of long term FTBFS packages to be retired in August

2020-07-27 Thread Vít Ondruch

Dne 26. 07. 20 v 13:44 Miro Hrončok napsal(a):
> On 29. 06. 20 17:49, Vít Ondruch wrote:
>> Dne 29. 06. 20 v 17:21 Miro Hrončok napsal(a):
>>> js-jquery1 nodejs-sig, patches, vondruch   Fedora 30
>>> js-jquery2 vondruch    Fedora 30
>>> js-sizzle  nodejs-sig, patches, vondruch   Fedora 30
>>>
>> I was ranting about js-jquery (and js-sizzle is dependency of js-jquery)
>> on this list already several times. I picked it up just to keep it alive
>> in whatever state, because bundling it everywhere won't make things
>> better. So is there anybody who would like to give it some love? Or
>> should I let the packages finally go and let everybody else to bundle
>> whatever they want?
>
> Since the packages are on their way to retirement, I've taken a look.
>
> 1) I see that most of the build dependencies of js-jquery1/js-jquery2
> are gone.
>
> 2) I see that all the FTBFS bugs are ASSIGNED without a single
> response about a plan to fix the problem. From your emails it seems
> the plan was always to "do nothing".
>
> 3) I see that both jqueries have several moderate CVEs open without a
> single response for months. From your "in whatever state" staement it
> seems the plan was to never fix those. The packages would need to be
> buildable in the first place in order to be able to fix them.
>
> Arguably, the benefit of having an unbundled dependency is mostly gone
> when the library is not maintained at all. It seems safer if other
> packages bundle and when they have a CVE open, the maintainers can
> evaluate the impact of the problem on their package. Even if 100
> packages bundle jquery and only 10 of them evaluate the impact of CVEs
> and/or fix the CVEs in their packages, the situation is better than now.


I think this is a bit optimistic POV. I think that in most of the
packages, there won't be even "bundled(jquery)" which would let the SRT
report the proper trackers. But I hope you are right and I am wrong :)


>
> So yes, please let the packages go.

I will.



Vít
___
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


Re: List of long term FTBFS packages to be retired in August

2020-07-26 Thread Miro Hrončok

On 29. 06. 20 17:49, Vít Ondruch wrote:

Dne 29. 06. 20 v 17:21 Miro Hrončok napsal(a):

js-jquery1 nodejs-sig, patches, vondruch   Fedora 30
js-jquery2 vondruch    Fedora 30
js-sizzle  nodejs-sig, patches, vondruch   Fedora 30


I was ranting about js-jquery (and js-sizzle is dependency of js-jquery)
on this list already several times. I picked it up just to keep it alive
in whatever state, because bundling it everywhere won't make things
better. So is there anybody who would like to give it some love? Or
should I let the packages finally go and let everybody else to bundle
whatever they want?


Since the packages are on their way to retirement, I've taken a look.

1) I see that most of the build dependencies of js-jquery1/js-jquery2 are gone.

2) I see that all the FTBFS bugs are ASSIGNED without a single response about a 
plan to fix the problem. From your emails it seems the plan was always to "do 
nothing".


3) I see that both jqueries have several moderate CVEs open without a single 
response for months. From your "in whatever state" staement it seems the plan 
was to never fix those. The packages would need to be buildable in the first 
place in order to be able to fix them.


Arguably, the benefit of having an unbundled dependency is mostly gone when the 
library is not maintained at all. It seems safer if other packages bundle and 
when they have a CVE open, the maintainers can evaluate the impact of the 
problem on their package. Even if 100 packages bundle jquery and only 10 of them 
evaluate the impact of CVEs and/or fix the CVEs in their packages, the situation 
is better than now.


So yes, please let the packages go.

--
Miro Hrončok
--
Phone: +420777974800
IRC: mhroncok
___
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


Re: List of long term FTBFS packages to be retired in August

2020-07-21 Thread Jens-Ulrik Petersen
On Tue, Jul 21, 2020 at 7:11 AM Miro Hrončok  wrote:

> ghc-pretty-show (maintained by: mathstuf)
> ghc-pretty-show-1.9.5-3.fc32.x86_64 requires js-jquery1 =
> 1.12.4-7.fc30


Turns out the upstream bundling already moved to jquery 3.3, so I am fixing
this.

On the other hand, I don't have a good feel for jquery3 compatibility:
is it a safe bet to assume 3.5 should be compatible with 3.3.1?

Jens
___
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


List of long term FTBFS packages to be retired in August

2020-07-20 Thread Miro Hrončok

Dear maintainers.

Based on the current fail to build from source policy, the following packages
will be retired from Fedora 33 approximately one week before branching (August 
2020).


Policy: 
https://docs.fedoraproject.org/en-US/fesco/Fails_to_build_from_source_Fails_to_install/


Note that some listed packages are orphaned and hence may be retired even 
sooner.

The packages in rawhide were not successfully built at least since Fedora 31.

This report is based on dist tags.

Packages collected via:
https://github.com/hroncok/fedora-report-ftbfs-retirements/blob/master/ftbfs-retirements.ipynb

If you see a package that was built, please let me know.
If you see a package that should be exempted from the process, please let me 
know and we can work together to get a FESCo approval for that.


If you see a package that can be rebuilt, please do so.


   Package (co)maintainers  Latest build

OpenCoarrays   jussilehtola Fedora 30
js-jquery-jqplot   xavierb  Fedora 30
js-jquery1 nodejs-sig, patches, vondruchFedora 30
js-jquery2 vondruch Fedora 30
js-sizzle  nodejs-sig, patches, vondruchFedora 30
nodejs-path-type   nodejs-sig, orphan   Fedora 30
nodejs-temp-write  orphan   Fedora 30
nodejs-unique-stream   jsmith, nodejs-sig   Fedora 30
orpie  bowlofeggs, orphan   Fedora 30
rubygem-ruby-hmac  humaton, mmorsi  Fedora 30


The following packages require above mentioned packages:
Depending on: js-jquery-jqplot (1)
sympa (maintained by: xavierb)
sympa-6.2.56-1.fc33.src requires js-jquery-jqplot = 1.0.9-3.fc30
sympa-6.2.56-1.fc33.x86_64 requires js-jquery-jqplot = 
1.0.9-3.fc30

Depending on: js-jquery1 (70)
R-profvis (maintained by: qulogic)
R-profvis-0.3.6-3.fc33.src requires js-jquery1 = 1.12.4-7.fc30
R-profvis-0.3.6-3.fc33.x86_64 requires js-jquery1 = 
1.12.4-7.fc30

R-rmarkdown (maintained by: qulogic)
R-rmarkdown-2.2-1.fc33.noarch requires js-jquery1 = 
1.12.4-7.fc30
R-rmarkdown-2.2-1.fc33.src requires js-jquery1 = 1.12.4-7.fc30

copr-frontend (maintained by: clime, copr-sig, dturecek, frostyx, 
msuchy, praiskup)
copr-frontend-1.166-1.fc33.noarch requires js-jquery1 = 
1.12.4-7.fc30

ghc-pretty-show (maintained by: mathstuf)
ghc-pretty-show-1.9.5-3.fc32.x86_64 requires js-jquery1 = 
1.12.4-7.fc30

mkdocs (maintained by: cheeselee)
mkdocs-1.1.2-1.fc33.noarch requires js-jquery1 = 1.12.4-7.fc30
mkdocs-1.1.2-1.fc33.src requires js-jquery1 = 1.12.4-7.fc30

python-XStatic-jQuery (maintained by: mrunge, openstack-sig, rdopiera)
python3-XStatic-jQuery-3.4.1.0-2.fc33.noarch requires 
js-jquery1 = 1.12.4-7.fc30

python-sphinx-bootstrap-theme (maintained by: besser82, sic)
		python3-sphinx-bootstrap-theme-0.8.0-3.fc33.noarch requires js-jquery1 = 
1.12.4-7.fc30


rubygem-apipie-rails (maintained by: jaruga, ruby-packagers-sig, 
vondruch)
rubygem-apipie-rails-0.5.5-6.fc32.noarch requires js-jquery1 = 
1.12.4-7.fc30

R-BiocFileCache (maintained by: spot)
R-BiocFileCache-1.12.0-2.fc33.src requires R-rmarkdown = 
2.2-1.fc33

R-DBItest (maintained by: qulogic)
R-DBItest-1.7.0-1.fc33.src requires R-rmarkdown = 2.2-1.fc33

R-V8 (maintained by: qulogic)
R-V8-3.1.0-3.fc33.src requires R-rmarkdown = 2.2-1.fc33

R-broom (maintained by: qulogic)
R-broom-0.5.6-2.fc33.src requires R-rmarkdown = 2.2-1.fc33

R-cellranger (maintained by: qulogic)
R-cellranger-1.1.0-6.fc33.src requires R-rmarkdown = 2.2-1.fc33

R-clipr (maintained by: qulogic)
R-clipr-0.7.0-3.fc33.src requires R-rmarkdown = 2.2-1.fc33

R-dbplyr (maintained by: qulogic)
R-dbplyr-1.4.3-2.fc33.src requires R-rmarkdown = 2.2-1.fc33

R-devtools (maintained by: qulogic)
R-devtools-2.1.0-2.fc33.src requires R-rmarkdown = 2.2-1.fc33

R-diffobj (maintained by: qulogic)
R-diffobj-0.3.0-2.fc33.src requires R-rmarkdown = 2.2-1.fc33

R-dplyr (maintained by: qulogic)
R-dplyr-0.8.5-2.fc33.src requires R-rmarkdown = 2.2-1.fc33

R-dtplyr (maintained by: qulogic)
R-dtplyr-1.0.1-2.fc33.src requires R-rmarkdown = 2.2-1.fc33

R-foghorn (maintained by: qulogic)
R-foghorn-1.1.0-5.fc33.src requires R-rmarkdown = 2.2-1.fc33

R-forcats (maintained by: qulogic)
R-forcats-0.5.0-2.fc33.src requires R-rmarkdown = 2.

List of long term FTBFS packages to be retired in August

2020-07-14 Thread Miro Hrončok

Dear maintainers.

Based on the current fail to build from source policy, the following packages
will be retired from Fedora 33 approximately one week before branching (August 
2020).


Policy: 
https://docs.fedoraproject.org/en-US/fesco/Fails_to_build_from_source_Fails_to_install/


Note that some listed packages are orphaned and hence may be retired even 
sooner.

The packages in rawhide were not successfully built at least since Fedora 31.

This report is based on dist tags.

Packages collected via:
https://github.com/hroncok/fedora-report-ftbfs-retirements/blob/master/ftbfs-retirements.ipynb

If you see a package that was built, please let me know.
If you see a package that should be exempted from the process, please let me 
know and we can work together to get a FESCo approval for that.


If you see a package that can be rebuilt, please do so.


  Package (co)maintainers  Latest build

OpenCoarrays   jussilehtolaFedora 30
js-jquery-jqplot   xavierb Fedora 30
js-jquery1 nodejs-sig, patches, vondruch   Fedora 30
js-jquery2 vondruchFedora 30
js-sizzle  nodejs-sig, patches, vondruch   Fedora 30
nodejs-path-type   nodejs-sig, orphan  Fedora 30
nodejs-temp-write  orphan  Fedora 30
nodejs-unique-stream   jsmith, nodejs-sig  Fedora 30
orpie  bowlofeggs, orphan  Fedora 30
rubygem-ruby-hmac  humaton, mmorsi Fedora 30


The following packages require above mentioned packages:
Depending on: js-jquery-jqplot (1)
sympa (maintained by: xavierb)
sympa-6.2.56-1.fc33.src requires js-jquery-jqplot = 1.0.9-3.fc30
sympa-6.2.56-1.fc33.x86_64 requires js-jquery-jqplot = 
1.0.9-3.fc30

Depending on: js-jquery1 (70)
R-profvis (maintained by: qulogic)
R-profvis-0.3.6-3.fc33.src requires js-jquery1 = 1.12.4-7.fc30
R-profvis-0.3.6-3.fc33.x86_64 requires js-jquery1 = 
1.12.4-7.fc30

R-rmarkdown (maintained by: qulogic)
R-rmarkdown-2.2-1.fc33.noarch requires js-jquery1 = 
1.12.4-7.fc30
R-rmarkdown-2.2-1.fc33.src requires js-jquery1 = 1.12.4-7.fc30

copr-frontend (maintained by: clime, copr-sig, dturecek, frostyx, 
msuchy, praiskup)
copr-frontend-1.166-1.fc33.noarch requires js-jquery1 = 
1.12.4-7.fc30

ghc-pretty-show (maintained by: mathstuf)
ghc-pretty-show-1.9.5-3.fc32.x86_64 requires js-jquery1 = 
1.12.4-7.fc30

mkdocs (maintained by: cheeselee)
mkdocs-1.1.2-1.fc33.noarch requires js-jquery1 = 1.12.4-7.fc30
mkdocs-1.1.2-1.fc33.src requires js-jquery1 = 1.12.4-7.fc30

python-XStatic-jQuery (maintained by: mrunge, openstack-sig, rdopiera)
python3-XStatic-jQuery-3.4.1.0-2.fc33.noarch requires 
js-jquery1 = 1.12.4-7.fc30

python-sphinx-bootstrap-theme (maintained by: besser82, sic)
		python3-sphinx-bootstrap-theme-0.8.0-3.fc33.noarch requires js-jquery1 = 
1.12.4-7.fc30


rubygem-apipie-rails (maintained by: jaruga, ruby-packagers-sig, 
vondruch)
rubygem-apipie-rails-0.5.5-6.fc32.noarch requires js-jquery1 = 
1.12.4-7.fc30

R-BiocFileCache (maintained by: spot)
R-BiocFileCache-1.12.0-2.fc33.src requires R-rmarkdown = 
2.2-1.fc33

R-DBItest (maintained by: qulogic)
R-DBItest-1.7.0-1.fc33.src requires R-rmarkdown = 2.2-1.fc33

R-V8 (maintained by: qulogic)
R-V8-3.1.0-3.fc33.src requires R-rmarkdown = 2.2-1.fc33

R-broom (maintained by: qulogic)
R-broom-0.5.6-2.fc33.src requires R-rmarkdown = 2.2-1.fc33

R-cellranger (maintained by: qulogic)
R-cellranger-1.1.0-6.fc33.src requires R-rmarkdown = 2.2-1.fc33

R-clipr (maintained by: qulogic)
R-clipr-0.7.0-3.fc33.src requires R-rmarkdown = 2.2-1.fc33

R-dbplyr (maintained by: qulogic)
R-dbplyr-1.4.3-2.fc33.src requires R-rmarkdown = 2.2-1.fc33

R-devtools (maintained by: qulogic)
R-devtools-2.1.0-2.fc33.src requires R-rmarkdown = 2.2-1.fc33

R-diffobj (maintained by: qulogic)
R-diffobj-0.3.0-2.fc33.src requires R-rmarkdown = 2.2-1.fc33

R-dplyr (maintained by: qulogic)
R-dplyr-0.8.5-2.fc33.src requires R-rmarkdown = 2.2-1.fc33

R-dtplyr (maintained by: qulogic)
R-dtplyr-1.0.1-2.fc33.src requires R-rmarkdown = 2.2-1.fc33

R-foghorn (maintained by: qulogic)
R-foghorn-1.1.0-5.fc33.src requires R-rmarkdown = 2.2-1.fc33

R-forcats (maintained by: qulogic)
R-forcats-0.5.0-2.fc33.src requires R-rmarkdown = 2.2-1.fc33

 

List of long term FTBFS packages to be retired in August

2020-07-07 Thread Miro Hrončok

Dear maintainers.

Based on the current fail to build from source policy, the following packages
will be retired from Fedora 33 approximately one week before branching (August 
2020).


Policy: 
https://docs.fedoraproject.org/en-US/fesco/Fails_to_build_from_source_Fails_to_install/


Note that some listed packages are orphaned and hence may be retired even 
sooner.

The packages in rawhide were not successfully built at least since Fedora 31.

This report is based on dist tags.

Packages collected via:
https://github.com/hroncok/fedora-report-ftbfs-retirements/blob/master/ftbfs-retirements.ipynb

If you see a package that was built, please let me know.
If you see a package that should be exempted from the process, please let me 
know and we can work together to get a FESCo approval for that.


If you see a package that can be rebuilt, please do so.


  Package (co)maintainers  Latest build

OpenCoarrays   jussilehtolaFedora 30
js-jquery-jqplot   xavierb Fedora 30
js-jquery1 nodejs-sig, patches, vondruch   Fedora 30
js-jquery2 vondruchFedora 30
js-sizzle  nodejs-sig, patches, vondruch   Fedora 30
nodejs-path-type   nodejs-sig, orphan  Fedora 30
nodejs-temp-write  orphan  Fedora 30
nodejs-unique-stream   jsmith, nodejs-sig  Fedora 30
orpie  bowlofeggs, orphan  Fedora 30
rubygem-ruby-hmac  humaton, mmorsi Fedora 30
xvarstar   orphan  Fedora 30

The following packages require above mentioned packages:
Depending on: js-jquery-jqplot (1)
sympa (maintained by: xavierb)
sympa-6.2.56-1.fc33.src requires js-jquery-jqplot = 1.0.9-3.fc30
sympa-6.2.56-1.fc33.x86_64 requires js-jquery-jqplot = 
1.0.9-3.fc30

Depending on: js-jquery1 (70)
R-profvis (maintained by: qulogic)
R-profvis-0.3.6-3.fc33.src requires js-jquery1 = 1.12.4-7.fc30
R-profvis-0.3.6-3.fc33.x86_64 requires js-jquery1 = 
1.12.4-7.fc30

R-rmarkdown (maintained by: qulogic)
R-rmarkdown-2.2-1.fc33.noarch requires js-jquery1 = 
1.12.4-7.fc30
R-rmarkdown-2.2-1.fc33.src requires js-jquery1 = 1.12.4-7.fc30

copr-frontend (maintained by: clime, copr-sig, dturecek, frostyx, 
msuchy, praiskup)
copr-frontend-1.166-1.fc33.noarch requires js-jquery1 = 
1.12.4-7.fc30

ghc-pretty-show (maintained by: mathstuf)
ghc-pretty-show-1.9.5-3.fc32.x86_64 requires js-jquery1 = 
1.12.4-7.fc30

mkdocs (maintained by: cheeselee)
mkdocs-1.1.2-1.fc33.noarch requires js-jquery1 = 1.12.4-7.fc30
mkdocs-1.1.2-1.fc33.src requires js-jquery1 = 1.12.4-7.fc30

python-XStatic-jQuery (maintained by: mrunge, openstack-sig, rdopiera)
python3-XStatic-jQuery-3.4.1.0-2.fc33.noarch requires 
js-jquery1 = 1.12.4-7.fc30

python-sphinx-bootstrap-theme (maintained by: besser82, sic)
		python3-sphinx-bootstrap-theme-0.8.0-3.fc33.noarch requires js-jquery1 = 
1.12.4-7.fc30


rubygem-apipie-rails (maintained by: jaruga, ruby-packagers-sig, 
vondruch)
rubygem-apipie-rails-0.5.5-6.fc32.noarch requires js-jquery1 = 
1.12.4-7.fc30

R-BiocFileCache (maintained by: spot)
R-BiocFileCache-1.12.0-2.fc33.src requires R-rmarkdown = 
2.2-1.fc33

R-DBItest (maintained by: qulogic)
R-DBItest-1.7.0-1.fc33.src requires R-rmarkdown = 2.2-1.fc33

R-V8 (maintained by: qulogic)
R-V8-3.1.0-2.fc33.src requires R-rmarkdown = 2.2-1.fc33

R-broom (maintained by: qulogic)
R-broom-0.5.6-2.fc33.src requires R-rmarkdown = 2.2-1.fc33

R-cellranger (maintained by: qulogic)
R-cellranger-1.1.0-6.fc33.src requires R-rmarkdown = 2.2-1.fc33

R-clipr (maintained by: qulogic)
R-clipr-0.7.0-3.fc33.src requires R-rmarkdown = 2.2-1.fc33

R-dbplyr (maintained by: qulogic)
R-dbplyr-1.4.3-2.fc33.src requires R-rmarkdown = 2.2-1.fc33

R-devtools (maintained by: qulogic)
R-devtools-2.1.0-2.fc33.src requires R-rmarkdown = 2.2-1.fc33

R-diffobj (maintained by: qulogic)
R-diffobj-0.3.0-2.fc33.src requires R-rmarkdown = 2.2-1.fc33

R-dplyr (maintained by: qulogic)
R-dplyr-0.8.5-2.fc33~bootstrap.src requires R-rmarkdown = 
2.2-1.fc33

R-dtplyr (maintained by: qulogic)
R-dtplyr-1.0.1-2.fc33.src requires R-rmarkdown = 2.2-1.fc33

R-foghorn (maintained by: qulogic)
R-foghorn-1.1.0-5.fc33.src requires R-rmarkdown = 2.2-1.fc33

R-forcats (maintained by: qulogic)

Re: List of long term FTBFS packages to be retired in August

2020-07-03 Thread Vít Ondruch
Would you mind to follow this page to get sponsored?

https://fedoraproject.org/wiki/Join_the_package_collection_maintainers

Also, it would be probably good to join the Node.js SIG to coordinate
and start contributing via PRs.

While I could sponsor you, I don't think I'd be good mentor for node
packaging. Sorry.


Vít


Dne 02. 07. 20 v 13:42 Alexandre de Farias napsal(a):
> In fact, I am not at this time.
>
> On Wed, 2020-07-01 at 15:38 +0200, Vít Ondruch wrote:
>> Hi Alexandre,
>>
>> Thank you for your offer. I just wonder, are you sponsored into
>> packager group?
>>
>>
>>
>> Vít
>>
>>
>>
>>
>>
>> Dne 29. 06. 20 v 17:57 alexandrebfar...@gmail.com napsal(a):
>>> I'm interested in helping with those NodeJS packages. 
>>>
>>> -- 
>>> Alexandre de Farias / etinin
>>>
>>> On Mon, Jun 29, 2020, 12:50 Vít Ondruch 
>>> wrote:
 Dne 29. 06. 20 v 17:21 Miro Hrončok napsal(a):
> js-jquery1 nodejs-sig, patches, vondruch   Fedora
 30
> js-jquery2 vondruchFedora
 30
> js-sizzle  nodejs-sig, patches, vondruch   Fedora
 30
 I was ranting about js-jquery (and js-sizzle is dependency of js-
 jquery)
 on this list already several times. I picked it up just to keep
 it alive
 in whatever state, because bundling it everywhere won't make
 things
 better. So is there anybody who would like to give it some love?
 Or
 should I let the packages finally go and let everybody else to
 bundle
 whatever they want?



 Vít

 ___
 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

>>>
>>> ___
>>> 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
>> ___
>> 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
>>
>> ___
>> 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
___
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


Re: List of long term FTBFS packages to be retired in August

2020-07-02 Thread Alexandre de Farias
In fact, I am not at this time.

On Wed, 2020-07-01 at 15:38 +0200, Vít Ondruch wrote:
> Hi Alexandre,
> 
> Thank you for your offer. I just wonder, are you sponsored into
> packager group?
> 
> 
> 
> Vít
> 
> 
> 
> 
> 
> Dne 29. 06. 20 v 17:57 alexandrebfar...@gmail.com napsal(a):
> > I'm interested in helping with those NodeJS packages. 
> > 
> > -- 
> > Alexandre de Farias / etinin
> > 
> > On Mon, Jun 29, 2020, 12:50 Vít Ondruch 
> > wrote:
> > > Dne 29. 06. 20 v 17:21 Miro Hrončok napsal(a):
> > > > js-jquery1 nodejs-sig, patches, vondruch   Fedora
> > > 30
> > > > js-jquery2 vondruchFedora
> > > 30
> > > > js-sizzle  nodejs-sig, patches, vondruch   Fedora
> > > 30
> > > >
> > > 
> > > I was ranting about js-jquery (and js-sizzle is dependency of js-
> > > jquery)
> > > on this list already several times. I picked it up just to keep
> > > it alive
> > > in whatever state, because bundling it everywhere won't make
> > > things
> > > better. So is there anybody who would like to give it some love?
> > > Or
> > > should I let the packages finally go and let everybody else to
> > > bundle
> > > whatever they want?
> > > 
> > > 
> > > 
> > > Vít
> > > 
> > > ___
> > > 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
> > > 
> > 
> > 
> > ___
> > 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
> 
> ___
> 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


smime.p7s
Description: S/MIME cryptographic signature
___
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


Re: List of long term FTBFS packages to be retired in August

2020-07-01 Thread Vít Ondruch
Hi Alexandre,

Thank you for your offer. I just wonder, are you sponsored into packager
group?


Vít



Dne 29. 06. 20 v 17:57 alexandrebfar...@gmail.com napsal(a):
> I'm interested in helping with those NodeJS packages. 
>
> -- 
> Alexandre de Farias / etinin
>
> On Mon, Jun 29, 2020, 12:50 Vít Ondruch  > wrote:
>
>
> Dne 29. 06. 20 v 17:21 Miro Hrončok napsal(a):
> > js-jquery1 nodejs-sig, patches, vondruch   Fedora 30
> > js-jquery2 vondruch    Fedora 30
> > js-sizzle  nodejs-sig, patches, vondruch   Fedora 30
> >
>
> I was ranting about js-jquery (and js-sizzle is dependency of
> js-jquery)
> on this list already several times. I picked it up just to keep it
> alive
> in whatever state, because bundling it everywhere won't make things
> better. So is there anybody who would like to give it some love? Or
> should I let the packages finally go and let everybody else to bundle
> whatever they want?
>
>
>
> Vít
>
> ___
> 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
>
>
> ___
> 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
___
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


Re: List of long term FTBFS packages to be retired in August

2020-06-29 Thread Till Maas
On Mon, Jun 29, 2020 at 05:21:58PM +0200, Miro Hrončok wrote:

>   Package (co)maintainers  Latest build
> 

> gpscorrelate   tillFedora 30

fixed.

Thanks
Till
___
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


Re: List of long term FTBFS packages to be retired in August

2020-06-29 Thread alexandrebfarias
I'm interested in helping with those NodeJS packages.

-- 
Alexandre de Farias / etinin

On Mon, Jun 29, 2020, 12:50 Vít Ondruch  wrote:

>
> Dne 29. 06. 20 v 17:21 Miro Hrončok napsal(a):
> > js-jquery1 nodejs-sig, patches, vondruch   Fedora 30
> > js-jquery2 vondruchFedora 30
> > js-sizzle  nodejs-sig, patches, vondruch   Fedora 30
> >
>
> I was ranting about js-jquery (and js-sizzle is dependency of js-jquery)
> on this list already several times. I picked it up just to keep it alive
> in whatever state, because bundling it everywhere won't make things
> better. So is there anybody who would like to give it some love? Or
> should I let the packages finally go and let everybody else to bundle
> whatever they want?
>
>
>
> Vít
>
> ___
> 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
>
___
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


Re: List of long term FTBFS packages to be retired in August

2020-06-29 Thread Vít Ondruch

Dne 29. 06. 20 v 17:21 Miro Hrončok napsal(a):
> js-jquery1 nodejs-sig, patches, vondruch   Fedora 30
> js-jquery2 vondruch    Fedora 30
> js-sizzle  nodejs-sig, patches, vondruch   Fedora 30
>

I was ranting about js-jquery (and js-sizzle is dependency of js-jquery)
on this list already several times. I picked it up just to keep it alive
in whatever state, because bundling it everywhere won't make things
better. So is there anybody who would like to give it some love? Or
should I let the packages finally go and let everybody else to bundle
whatever they want?



Vít

___
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


List of long term FTBFS packages to be retired in August

2020-06-29 Thread Miro Hrončok

Dear maintainers.

Based on the current fail to build from source policy, the following packages
will be retired from Fedora 33 approximately one week before branching (August 
2020).


Policy: 
https://docs.fedoraproject.org/en-US/fesco/Fails_to_build_from_source_Fails_to_install/


Note that some listed packages are orphaned and hence may be retired even 
sooner.

The packages in rawhide were not successfully built at least since Fedora 31.

This report is based on dist tags.

Packages collected via:
https://github.com/hroncok/fedora-report-ftbfs-retirements/blob/master/ftbfs-retirements.ipynb

If you see a package that was built, please let me know.
If you see a package that should be exempted from the process, please let me 
know and we can work together to get a FESCo approval for that.


If you see a package that can be rebuilt, please do so.


  Package (co)maintainers  Latest build

OpenCoarrays   jussilehtolaFedora 30
gpscorrelate   tillFedora 30
js-jquery-jqplot   xavierb Fedora 30
js-jquery1 nodejs-sig, patches, vondruch   Fedora 30
js-jquery2 vondruchFedora 30
js-sizzle  nodejs-sig, patches, vondruch   Fedora 30
nodejs-path-type   jsmith, nodejs-sig  Fedora 30
nodejs-temp-write  jsmith  Fedora 30
nodejs-unique-stream   jsmith, nodejs-sig  Fedora 30
ocaml-pxp  orphan  Fedora 30
ocaml-ulex orphan  Fedora 30
orpie  bowlofeggs, jaredwallaceFedora 30
rubygem-ruby-hmac  humaton, mmorsi Fedora 30
xvarstar   orphan  Fedora 30


The following packages require above mentioned packages:
Depending on: gpscorrelate (1)
foxtrotgps (maintained by: bubeck)
foxtrotgps-1.2.2-5.fc33.x86_64 requires gpscorrelate = 
1.6.1-27.fc30

Depending on: js-jquery-jqplot (1)
sympa (maintained by: xavierb)
sympa-6.2.56-1.fc33.src requires js-jquery-jqplot = 1.0.9-3.fc30
sympa-6.2.56-1.fc33.x86_64 requires js-jquery-jqplot = 
1.0.9-3.fc30

Depending on: js-jquery1 (69)
R-profvis (maintained by: qulogic)
R-profvis-0.3.6-3.fc33.src requires js-jquery1 = 1.12.4-7.fc30
R-profvis-0.3.6-3.fc33.x86_64 requires js-jquery1 = 
1.12.4-7.fc30

R-rmarkdown (maintained by: qulogic)
R-rmarkdown-2.2-1.fc33.noarch requires js-jquery1 = 
1.12.4-7.fc30
R-rmarkdown-2.2-1.fc33.src requires js-jquery1 = 1.12.4-7.fc30

copr-frontend (maintained by: clime, copr-sig, dturecek, frostyx, 
msuchy, praiskup)
copr-frontend-1.166-1.fc33.noarch requires js-jquery1 = 
1.12.4-7.fc30

ghc-pretty-show (maintained by: mathstuf)
ghc-pretty-show-1.9.5-3.fc32.x86_64 requires js-jquery1 = 
1.12.4-7.fc30

mkdocs (maintained by: cheeselee)
mkdocs-1.1.2-1.fc33.noarch requires js-jquery1 = 1.12.4-7.fc30
mkdocs-1.1.2-1.fc33.src requires js-jquery1 = 1.12.4-7.fc30

python-XStatic-jQuery (maintained by: mrunge, openstack-sig, rdopiera)
python3-XStatic-jQuery-3.4.1.0-2.fc33.noarch requires 
js-jquery1 = 1.12.4-7.fc30

python-sphinx-bootstrap-theme (maintained by: besser82, sic)
		python3-sphinx-bootstrap-theme-0.8.0-3.fc33.noarch requires js-jquery1 = 
1.12.4-7.fc30


rubygem-apipie-rails (maintained by: jaruga, ruby-packagers-sig, 
vondruch)
rubygem-apipie-rails-0.5.5-6.fc32.noarch requires js-jquery1 = 
1.12.4-7.fc30

R-BiocFileCache (maintained by: spot)
R-BiocFileCache-1.12.0-2.fc33.src requires R-rmarkdown = 
2.2-1.fc33

R-DBItest (maintained by: qulogic)
R-DBItest-1.7.0-1.fc33.src requires R-rmarkdown = 2.2-1.fc33

R-V8 (maintained by: qulogic)
R-V8-3.1.0-2.fc33.src requires R-rmarkdown = 2.2-1.fc33

R-broom (maintained by: qulogic)
R-broom-0.5.6-2.fc33.src requires R-rmarkdown = 2.2-1.fc33

R-cellranger (maintained by: qulogic)
R-cellranger-1.1.0-6.fc33.src requires R-rmarkdown = 2.2-1.fc33

R-clipr (maintained by: qulogic)
R-clipr-0.7.0-3.fc33.src requires R-rmarkdown = 2.2-1.fc33

R-dbplyr (maintained by: qulogic)
R-dbplyr-1.4.3-2.fc33.src requires R-rmarkdown = 2.2-1.fc33

R-devtools (maintained by: qulogic)
R-devtools-2.1.0-2.fc33.src requires R-rmarkdown = 2.2-1.fc33

R-diffobj (maintained by: qulogic)
R-diffobj-0.3.0-2.fc33.src requires R-rmarkdown = 2.2-1.fc33

R-dplyr (maintained by: qulogic)
R