Re: glibc 2.34 vs firefox in rawhide vs mass build rebuild

[Florian Weimer]

This is now resolved in rawhide.  Thanks to all who have helped to get
us to this point.

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

Re: glibc 2.34 vs firefox in rawhide vs mass build rebuild

[Florian Weimer]

* Florian Weimer:

> Firefox in rawhide hasn't been built successfully since
> firefox-89.0-1.fc35 (built 2021-06-02).  Unfortunately that version does
> not treat the clone3 system call correctly in its sandbox, so it won't
> work with future glibc 2.34 snapshots.
>
> I fixed the issues to get firefox building again and attached a patch to
> this bug:
>
>   firefox: FTBFS with Python 3.10 in rawhide due to collections.abc change
>   
>
> (The patch also includes a glibc 2.34 compatibility change, separately
> tracked as #1983696 for downstream convenience.)
>
> The sandbox works again because the rawhide sources already had the
> required changes, they simply had not been built yet.
>
> What's the Fedora etiquette for fixing such long-standing FTBFS bugs?
>
> I seem to recall that firefox used to be a special package, not to be
> touched even by provenpackagers.
>
> On the other hand, I would like to upload another glibc 2.34 snapshot
> whose ABI is closer to what upstream is going to release on August 2nd.
> With that snapshot, glibc will start using clone3 internally, and that's
> incompatible with older firefox builds.
>
> It's not critical to do this glibc import before the mass rebuild
> because we definitely expect that the glibc 2.34 release will be
> backwards-compatible with what we have in Fedora today.  But we will
> miss some non-critical changes related to libresolv integration, so I'd
> like to proceed with the import.

Due to this issue, I disabled glibc for the mass rebuild.  The current
version in dist-git already uses clone3, and the mass rebuild would have
eventually tagged into the buildroot/compose, which we don't want until
firefox is fixed.

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

Re: glibc 2.34 vs firefox in rawhide vs mass build rebuild

[Martin Stransky]

Hi Florian,

I tried to install rawhide in VM to fix FF build but rawhide failed to 
boot (live iso and update by dnf from 34).


I'll look at it again.

Martin

On 7/20/21 12:17 PM, Florian Weimer wrote:

Firefox in rawhide hasn't been built successfully since
firefox-89.0-1.fc35 (built 2021-06-02).  Unfortunately that version does
not treat the clone3 system call correctly in its sandbox, so it won't
work with future glibc 2.34 snapshots.

I fixed the issues to get firefox building again and attached a patch to
this bug:

   firefox: FTBFS with Python 3.10 in rawhide due to collections.abc change
   

(The patch also includes a glibc 2.34 compatibility change, separately
tracked as #1983696 for downstream convenience.)

The sandbox works again because the rawhide sources already had the
required changes, they simply had not been built yet.

What's the Fedora etiquette for fixing such long-standing FTBFS bugs?

I seem to recall that firefox used to be a special package, not to be
touched even by provenpackagers.

On the other hand, I would like to upload another glibc 2.34 snapshot
whose ABI is closer to what upstream is going to release on August 2nd.
With that snapshot, glibc will start using clone3 internally, and that's
incompatible with older firefox builds.

It's not critical to do this glibc import before the mass rebuild
because we definitely expect that the glibc 2.34 release will be
backwards-compatible with what we have in Fedora today.  But we will
miss some non-critical changes related to libresolv integration, so I'd
like to proceed with the import.

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




--
Martin Stransky
Software Engineer / Red Hat, Inc
___
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: glibc 2.34 vs firefox in rawhide vs mass build rebuild

[stan via devel]

On Tue, 20 Jul 2021 12:17:34 +0200
Florian Weimer  wrote:

> Firefox in rawhide hasn't been built successfully since
> firefox-89.0-1.fc35 (built 2021-06-02).  Unfortunately that version
> does not treat the clone3 system call correctly in its sandbox, so it
> won't work with future glibc 2.34 snapshots.
> 
> I fixed the issues to get firefox building again and attached a patch
> to this bug:
> 
>   firefox: FTBFS with Python 3.10 in rawhide due to collections.abc
> change 

I think this has been fixed in later firefox,
https://bugzilla.mozilla.org/show_bug.cgi?id=1718878

> (The patch also includes a glibc 2.34 compatibility change, separately
> tracked as #1983696 for downstream convenience.)

I am having trouble building nightly (firefox development version) in
rawhide, and have a bugzilla open with mozilla,
https://bugzilla.mozilla.org/show_bug.cgi?id=1721251
I copied your mail to that bugzilla, because the compatibility change
*might* be related.  It could be just a misconfiguration by me, or
other issues, though.
___
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

glibc 2.34 vs firefox in rawhide vs mass build rebuild

[Florian Weimer]

Firefox in rawhide hasn't been built successfully since
firefox-89.0-1.fc35 (built 2021-06-02).  Unfortunately that version does
not treat the clone3 system call correctly in its sandbox, so it won't
work with future glibc 2.34 snapshots.

I fixed the issues to get firefox building again and attached a patch to
this bug:

  firefox: FTBFS with Python 3.10 in rawhide due to collections.abc change
  

(The patch also includes a glibc 2.34 compatibility change, separately
tracked as #1983696 for downstream convenience.)

The sandbox works again because the rawhide sources already had the
required changes, they simply had not been built yet.

What's the Fedora etiquette for fixing such long-standing FTBFS bugs?

I seem to recall that firefox used to be a special package, not to be
touched even by provenpackagers.

On the other hand, I would like to upload another glibc 2.34 snapshot
whose ABI is closer to what upstream is going to release on August 2nd.
With that snapshot, glibc will start using clone3 internally, and that's
incompatible with older firefox builds.

It's not critical to do this glibc import before the mass rebuild
because we definitely expect that the glibc 2.34 release will be
backwards-compatible with what we have in Fedora today.  But we will
miss some non-critical changes related to libresolv integration, so I'd
like to proceed with the import.

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