Re: glibc32 in rawhide is now built from glibc

2024-03-20 Thread Florian Weimer
* Kevin Fenzi:

> However, our filter config is... quite possibly out of date. :)
>
> Currently it is: 
>
> filter_packages = [
> ("^.*$", {
> "*": ["glibc32", "libgcc32"],
> "s390x": ["rust-std-static-wasm*"],
> }),
> ('(Server)$', {
> '*': [
> 'kernel*debug*',
> 'kernel-kdump*',
> 'kernel-tools*',
> 'syslog-ng*',
> 'astronomy-bookmarks',
> 'generic*',
> 'GConf2-dbus*',
> 'bluez-gnome',
> 'java-11-openjdk',
> 'community-mysql*',
> 'jruby*',
> 'gimp-help-*',
> ]
> }),
> ]
>
> Does libgcc32 exist anymore?

I planned to bring this up later. 8-) I requested the addition of
libgcc32 because I thought it was needed.  But it turns out that all the
files that would be part of that package have always been gcc.x86_64.
This means that we don't need a libgcc32 subpackage after all.

I'll comment on the ticket as well.

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: glibc32 in rawhide is now built from glibc

2024-03-19 Thread Kevin Fenzi
On Tue, Mar 19, 2024 at 04:36:03PM +0100, Florian Weimer wrote:
> * Kevin Fenzi:
> 
> > So, seems glibc32 was updated to update license headers?
> >
> > https://bodhi.fedoraproject.org/updates/FEDORA-2024-cd577e1535
> >
> > So, it's in f40-updates-testing now. 
> >
> > It's not in rawhide or f40 composes because pungi filters it out, but
> > it's currently not filtered in updates-testing. I can fix that, but...
> > isn't this package just going to be retired/blocked now?
> 
> Uh-oh?  Does this mean that glibc32 (the binary package) will land in
> updates-testing as well, each time we have glibc in gating?

Yep. So I will filter it there too...

> I planned to retire glibc32 after my vacation, in early April, but I can
> retire it now if that's better.

Naw, I can add it to filter out and then it shouldn't matter.

However, our filter config is... quite possibly out of date. :)

Currently it is: 

filter_packages = [
("^.*$", {
"*": ["glibc32", "libgcc32"],
"s390x": ["rust-std-static-wasm*"],
}),
('(Server)$', {
'*': [
'kernel*debug*',
'kernel-kdump*',
'kernel-tools*',
'syslog-ng*',
'astronomy-bookmarks',
'generic*',
'GConf2-dbus*',
'bluez-gnome',
'java-11-openjdk',
'community-mysql*',
'jruby*',
'gimp-help-*',
]
}),
]

Does libgcc32 exist anymore? 
Do we need that exclude on wasm on s390x?
Those sever ones look... weird.

Anyhow, I have filed: 
https://pagure.io/releng/issue/12023
on this, so if you want something to stay in there that's listed above,
please note it there. ;) 

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: glibc32 in rawhide is now built from glibc

2024-03-19 Thread Florian Weimer
* Kevin Fenzi:

> So, seems glibc32 was updated to update license headers?
>
> https://bodhi.fedoraproject.org/updates/FEDORA-2024-cd577e1535
>
> So, it's in f40-updates-testing now. 
>
> It's not in rawhide or f40 composes because pungi filters it out, but
> it's currently not filtered in updates-testing. I can fix that, but...
> isn't this package just going to be retired/blocked now?

Uh-oh?  Does this mean that glibc32 (the binary package) will land in
updates-testing as well, each time we have glibc in gating?

I planned to retire glibc32 after my vacation, in early April, but I can
retire it now if that's better.

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: glibc32 in rawhide is now built from glibc

2024-03-19 Thread Kevin Fenzi
On Fri, Mar 15, 2024 at 05:10:52PM +0100, Florian Weimer wrote:
> Joseph Myers enhanced glibc.spec so that we no longer need the separate
> glibc32 source package which its tarball of pre-built glibc binaries.
> 
> As part of the DNF5 adjustment to the removal of filelists, I believe
> some reverse dependencies (including gcc) have been adjusted to use the
> package name explicitly, as in:
> 
> %ifarch x86_64
> BuildRequires: (glibc32 or glibc-devel(%{__isa_name}-32))
> %endif
> 
> Most packages have dropped the glibc32 dependency because it was
> unneeded (or should do so).
> 
> This new package only contains the glibc files needed to build gcc.
> Other shared objects, such as libcrypt.so.2 or libgcc_s.so.1, are no
> longer included.
> 
> There is a pungi configuration which is expected to filter out glibc32
> from the compose.  We'll see how that works out.  The new glibc32
> package does not have any ELF dependency information, so the risk of it
> being installed by accident is reduced compared to the old one.
> 
> Once we have a compose without glibc32, I will retire the glibc32 source
> package because we no longer need it.  Currently, glibc32 is still
> tagged in, but it has a lower version than the glibc-built package, so
> the latter is installed in the buildroot.

So, seems glibc32 was updated to update license headers?

https://bodhi.fedoraproject.org/updates/FEDORA-2024-cd577e1535

So, it's in f40-updates-testing now. 

It's not in rawhide or f40 composes because pungi filters it out, but
it's currently not filtered in updates-testing. I can fix that, but...
isn't this package just going to be retired/blocked now?

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: glibc32 in rawhide is now built from glibc

2024-03-15 Thread Kevin Fenzi
On Fri, Mar 15, 2024 at 05:10:52PM +0100, Florian Weimer wrote:
> Joseph Myers enhanced glibc.spec so that we no longer need the separate
> glibc32 source package which its tarball of pre-built glibc binaries.
> 
> As part of the DNF5 adjustment to the removal of filelists, I believe
> some reverse dependencies (including gcc) have been adjusted to use the
> package name explicitly, as in:
> 
> %ifarch x86_64
> BuildRequires: (glibc32 or glibc-devel(%{__isa_name}-32))
> %endif
> 
> Most packages have dropped the glibc32 dependency because it was
> unneeded (or should do so).
> 
> This new package only contains the glibc files needed to build gcc.
> Other shared objects, such as libcrypt.so.2 or libgcc_s.so.1, are no
> longer included.
> 
> There is a pungi configuration which is expected to filter out glibc32
> from the compose.  We'll see how that works out.  The new glibc32
> package does not have any ELF dependency information, so the risk of it
> being installed by accident is reduced compared to the old one.
> 
> Once we have a compose without glibc32, I will retire the glibc32 source
> package because we no longer need it.  Currently, glibc32 is still
> tagged in, but it has a lower version than the glibc-built package, so
> the latter is installed in the buildroot.

Awesome. Thanks for all the work on this... I realize it's a weird
corner case, but now it's a lot more sane.

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


glibc32 in rawhide is now built from glibc

2024-03-15 Thread Florian Weimer
Joseph Myers enhanced glibc.spec so that we no longer need the separate
glibc32 source package which its tarball of pre-built glibc binaries.

As part of the DNF5 adjustment to the removal of filelists, I believe
some reverse dependencies (including gcc) have been adjusted to use the
package name explicitly, as in:

%ifarch x86_64
BuildRequires: (glibc32 or glibc-devel(%{__isa_name}-32))
%endif

Most packages have dropped the glibc32 dependency because it was
unneeded (or should do so).

This new package only contains the glibc files needed to build gcc.
Other shared objects, such as libcrypt.so.2 or libgcc_s.so.1, are no
longer included.

There is a pungi configuration which is expected to filter out glibc32
from the compose.  We'll see how that works out.  The new glibc32
package does not have any ELF dependency information, so the risk of it
being installed by accident is reduced compared to the old one.

Once we have a compose without glibc32, I will retire the glibc32 source
package because we no longer need it.  Currently, glibc32 is still
tagged in, but it has a lower version than the glibc-built package, so
the latter is installed in the buildroot.

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