On Sun, Nov 16, 2025, 7:56 PM Willy Sudiarto Raharjo < [email protected]> wrote:
> >I had the same problem. I reverted to version 122.0.5463.142 of Opera, > >and version 0.101.0 of the codecs. Video still works with those two. > > > >On Sun, Nov 16, 2025 at 3:44 PM Heiko Rosemann via SlackBuilds-users < > >[email protected]> wrote: > > > >> On 11/15/25 05:39, Willy Sudiarto Raharjo wrote: > >> > multimedia/opera-ffmpeg-codecs: Updated for version 0.105.0, new > >> > >> Depends on glibc 2.35 where Slackware 15.0 only provides 2.33: > >> > >> ldd /usr/lib64/opera/lib_extra/libffmpeg.so > >> /usr/lib64/opera/lib_extra/libffmpeg.so: /lib64/libm.so.6: version > >> `GLIBC_2.35' not found (required by > >> /usr/lib64/opera/lib_extra/libffmpeg.so) > >> /usr/lib64/opera/lib_extra/libffmpeg.so: /lib64/libc.so.6: version > >> `GLIBC_ABI_DT_RELR' not found (required by > >> /usr/lib64/opera/lib_extra/libffmpeg.so) > >> /usr/lib64/opera/lib_extra/libffmpeg.so: /lib64/libc.so.6: version > >> `GLIBC_2.34' not found (required by > >> /usr/lib64/opera/lib_extra/libffmpeg.so) > >> > >> This is probably going to be more and more of an issue, the older > >> Slackware 15.0 gets and the more build pipelines get updated beyond > >> its basic libraries. > >> > >> I went back to 0.94.1 but that does not work with the latest > >> opera... so no more video in opera :-/ > > > Thanks for the report > i have documented the report and notified the last commiter about this > issue > https://github.com/SlackBuildsOrg/slackbuilds/issues/13103 > > FYI, opera-ffmpeg-codecs is currently orphaned, so if anyone here is > using it, i suggest to take maintainership or else it will be removed > in the next development cycle. > > -- > Willy Sudiarto Raharjo > _______________________________________________ > SlackBuilds-users mailing list > [email protected] > https://lists.slackbuilds.org/mailman/listinfo/slackbuilds-users > Archives - https://lists.slackbuilds.org/pipermail/slackbuilds-users/ > FAQ - https://slackbuilds.org/faq/ Is SBo accepting updates of orphaned packages without that person submitting updates taking ownership? Seems like if you're going to submit an update for an orphaned package, you should take ownership of it... but maybe that's just my thought process and others wouldn't agree. Jeremy
_______________________________________________ SlackBuilds-users mailing list [email protected] https://lists.slackbuilds.org/mailman/listinfo/slackbuilds-users Archives - https://lists.slackbuilds.org/pipermail/slackbuilds-users/ FAQ - https://slackbuilds.org/faq/
