Re: heads up: nss 3.59 breaks firefox add-ons
by Kevin Fenzi
On Fri, Jan 08, 2021 at 06:41:36AM +0100, Onyeibo Oku wrote:
> Is this still active? My Firefox plugins are getting disabled and I
> cannot install new ones (they are reported as corrupt). Is there a new
> instance of this bug?
Yeah, it came back because as Adams says:
https://bugzilla.redhat.com/show_bug.cgi?id=1908018#c19
"So for the record this bug is back because mstransky switched Firefox
back to building against system NSS, but did not patch it as Bob
recommended to still allow SHA-1 signatures. I'll see if I can do that."
But the fix in firefox hasn't yet landed.
Your best bet right now is:
sudo update-crypto-policies --set DEFAULT:FEDORA32
for now.
kevin
PS: no need to cc me on replies to the list. I'm subscribed and read
posts. ;)
--
>
> Regards
> Onyeibo
>
> On Fri Dec 18, 2020 at 5:30 PM WAT, Adam Williamson wrote:
> > On Fri, 2020-12-18 at 07:33 -0700, James Szinger wrote:
> > > On Tue, 15 Dec 2020 11:17:21 -0800
> > > Kevin Fenzi <kevin(a)scrye.com> wrote:
> > >
> > > > If you upgrade in f33 or rawhide to nss 3.59, all your firefox add-ons
> > > > will stop working. Worse they will appear corrupted, so you will have
> > > > to remove them and re-install them (after downgrading nss).
> > > >
> > > > For now, downgrade nss or avoid updating to it until things can get
> > > > sorted out.
> > > >
> > > > https://bugzilla.redhat.com/show_bug.cgi?id=1908018
> > > >
> > > > kevin
> > >
> > > I see nss.x86_64 3.59.0-3.fc33 in today’s updates. Is this fixed or
> > > are there going to be a lot of unhappy Firefox users?
> >
> > It's fixed.
> >
> > > The bug is still open.
> >
> > Because we still need to do something (or, rather, get Mozilla to do
> > something) about the underlying situation.
> > --
> > Adam Williamson
> > Fedora QA
> > IRC: adamw | Twitter: adamw_ha
> > https://www.happyassassin.net
> >
> >
> > _______________________________________________
> > test mailing list -- test(a)lists.fedoraproject.org
> > To unsubscribe send an email to test-leave(a)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/test@lists.fedoraproject.org
> _______________________________________________
> test mailing list -- test(a)lists.fedoraproject.org
> To unsubscribe send an email to test-leave(a)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/test@lists.fedoraproject.org
3 years, 3 months
Un-retire the package python-pyswip
by Christoph Karl
Hello everyone!
I want to un-retire the package python-pyswip.
According to "dead.package" the reason for retiring this package is/was:
"SWI Prolog (package pl) has been retired from Fedora, this package
provided Python bindings for SWI Prolog."
I checked this with Jerry James (maintainer of SWI Prolog (package pl):
To his recall, the former maintainer of that package retired it on the
same day that he saved SWI Prolog from being retired.
PySwip seems to have an active upstream.
For me a Python/Prolog bridge has two advantages:
*) Easier to learn Prolog because I am familiar with Python.
*) Possibility to extend Python with Prolog-reasoning.
Best Regards
Christoph
3 years, 3 months
Mass spec file change: Adding BuildRequires: make
by Tom Stellard
Hi,
As part of the f34 change request[1] for removing make from the
buildroot, I will be doing a mass update of packages[2] to add
BuildRequires: make where it is needed.
If you are a package maintainer and would prefer to update your packages
on your own, please do so before Dec 14, which is when I will begin
doing the mass update.
I will be doing the updates in batches, so that if there is a mistake
the impact will be limited. Here is the rough schedule of the changes:
Dec 14: Update first 50 packages.
Dec 16: Next 1000.
Dec 18: Next 1000.
Jan 4: Next 1000.
Jan 5: Next 1000.
Jan 6: Next 1000.
Jan 7: Next 1000.
Jan 8: Rest of packages.
The deadline for completing these updates is the start of the f34 mass
rebuild (Jan 20).
Thanks,
Tom
[1] https://fedoraproject.org/wiki/Changes/Remove_make_from_BuildRoot
[2] https://fedorapeople.org/~tstellar/needs_br_make_packages.txt
3 years, 3 months
Fedora 34 Change: Ruby 3.0 (System-Wide Change)
by Ben Cotton
https://fedoraproject.org/wiki/Changes/Ruby_3.0
== Summary ==
Ruby 3.0 is the latest stable version of Ruby. Many new features and
improvements are included for the increasingly diverse and expanding
demands for Ruby. With this major update from Ruby 2.7 in Fedora 33 to
Ruby 3.0 in Fedora 34, Fedora becomes the superior Ruby development
platform.
== Owner ==
* Name: [[User:vondruch| Vít Ondruch]], [[User:pvalena| Pavel Valena]]
* Email: vondruch(a)redhat.com, pvalena(a)redhat.com
== Detailed Description ==
<!-- Expand on the summary, if appropriate. A couple sentences
suffices to explain the goal, but the more details you can provide the
better. -->
Ruby 3.0 is upstream's new major release of Ruby. Many new features
and improvements are included.
=== RBS ===
RBS is a language to describe the types of Ruby programs. Type
checkers including type-profiler and other tools supporting RBS will
understand Ruby programs much better with RBS definitions.
You can write down the definition of classes and modules: methods
defined in the class, instance variables and their types, and
inheritance/mix-in relations. The goal of RBS is to support commonly
seen patterns in Ruby programs and it allows writing advanced types
including union types, method overloading, and generics. It also
supports duck typing with interface types.
Ruby 3.0 ships with `rbs` gem, which allows parsing and processing
type definitions written in RBS.
=== Ractor (experimental) ===
Ractor is an Actor-model like concurrent abstraction designed to
provide a parallel execution feature without thread-safety concerns.
You can make multiple ractors and you can run them in parallel. Ractor
enables to make thread-safe parallel programs because ractors can not
share normal objects. Communication between ractors are supported by
message passing.
To limit sharing objects, Ractor introduces several restrictions to
the Ruby’s syntax (without multiple Ractors, there is no changes).
The specification and implementation are not matured and changed in
future, so this feature is marked as experimental and show the
experimental feature warning if Ractor is created.
=== Scheduler (Experimental) ===
`Thread#scheduler` is introduced for intercepting blocking operations.
This allows for light-weight concurrency without changing existing
code.
CAUTION: This feature is strongly experimental. Both the name and
feature will change in next preview release.
=== Other Notable New Features ===
* Rightward assignment statement is added.
* Endless method definition is added.
* Find pattern is added.
* `Hash#except` is now built-in.
* Memory view is added as an experimental feature
=== Performance improvements ===
Many improvements were implemented in MJIT.
=== Other notable changes since 2.7 ===
* Keyword arguments are separated from other arguments.
* The feature of `$SAFE` was completely removed; now it is a normal
global variable.
* The order of backtrace had been reversed at Ruby 2.5, but it was
cancelled. Now it behaves like Ruby 2.4; an error message and the line
number where the exception occurs are printed first, and its callers
are printed later.
* Some standard libraries are updated.
== Benefit to Fedora ==
With a latest release, Ruby language is supporting the newest language
features, which enables even faster and easier development of Ruby
applications.
== Scope ==
* Proposal owners:
** Finish packaging of Ruby 3.0. Current changes available in PR
https://src.fedoraproject.org/rpms/ruby/pull-request/70
** Rebuilding of Ruby packages providing native extensions (i.e.
packages which depends on libruby).
* Other developers:
** Rebuild of packages with binary extensions (i.e. packages which
depends on libruby) will be handled automatically, but some packages
might need fixes/updates to support Ruby 3.0 properly.
* Release engineering: [https://pagure.io/releng/issue/9882 #9882] (a
check of an impact with Release Engineering is needed)
** The packages are going to be rebuild in side-tag, but that does not
need releng involvement nowadays.
* Policies and guidelines: N/A (not a System Wide Change)
* Trademark approval: N/A (not needed for this Change)
* Alignment with Objectives:
== Upgrade/compatibility impact ==
* User specific Ruby binary extensions need to be rebuild.
== How To Test ==
* No special hardware is needed.
* To test, install Ruby 3.0. The test builds are pusblished in PR or
on Ruby-SIG ML
* Try to locally rebuild your packages using Ruby 3.0.
* Use the packages with your applications previously written in Ruby.
* If something doesn't work as it should, let us know.
== User Experience ==
The Ruby programs/scripts should behave as they were used to.
== Dependencies ==
<pre>
$ dnf repoquery --disablerepo=* --enablerepo=rawhide
--enablerepo=rawhide-source --arch=src --whatrequires 'ruby-devel' |
sort | uniq | wc -l
138
</pre>
== Contingency Plan ==
* Contingency mechanism: We would like to get a special buildroot tag
to be able to rebuild necessary the packages with Ruby 3.0. If
anything goes wrong, the tag could be easily dropped and previous
version of Ruby 2.7 and its dependencies stays intact. The tag would
be merged into F34 after everything is rebuild.
* Contingency deadline: Mass Rebuild
* Blocks release? No (not a System Wide Change), Yes/No
* Blocks product? No
== Documentation ==
* [http://www.ruby-doc.org/ Help and documentation for the Ruby
programming language]
* [https://github.com/ruby/ruby/blob/v3_0_0_preview1/NEWS.md Ruby
3.0.0.preview1 NEWS]
== Release Notes ==
* The Ruby 3.0 bumps soname, therefore Ruby packages, which use binary
extensions, should be rebuilt. Nevertheless, since upstream paid great
attention to source compatibility, no changes to your code are needed.
https://github.com/ruby/ruby/blob/master/NEWS
--
Ben Cotton
He / Him / His
Senior Program Manager, Fedora & CentOS Stream
Red Hat
TZ=America/Indiana/Indianapolis
3 years, 3 months
Fwd: Thoughts on the file system layout
by Neal Gompa
This may be of interest to us as well...
---------- Forwarded message ---------
From: Ludwig Nussel <ludwig.nussel(a)suse.de>
Date: Tue, Jan 5, 2021 at 11:03 AM
Subject: Thoughts on the file system layout
To: <factory(a)lists.opensuse.org>
Hi,
While working on MicroOS, UsrMerge, UsrEtc, playing with systemd
features I was wondering where that could lead us to. I'm sure we didn't
utilize the full potential of what we can do with our OS yet. So I've
tried to dump my thoughts into an article:
https://github.com/lnussel/lnussel.github.io/blob/fs/_posts/2020-12-16-fs...
tl;dr rpms to only operate below /usr and nowhere else.
cu
Ludwig
--
(o_ Ludwig Nussel
//\
V_/_ http://www.suse.com/
SUSE Software Solutions Germany GmbH, GF: Felix Imendörffer
HRB 36809 (AG Nürnberg)
--
真実はいつも一つ！/ Always, there's only one truth!
3 years, 3 months
GPG check FAILED for libuv on F32
by Endi Sukma Dewata
Hi, there seems to be a problem with libuv on F32.
It doesn't seem to be happening on F33. Is anybody
familiar with this? Thanks.
# podman run --rm -it fedora:32 dnf install libuv -y
Fedora 32 openh264 (From Cisco) - x86_64 1.5 kB/s | 2.5 kB 00:01
Fedora Modular 32 - x86_64 250 kB/s | 4.9 MB 00:20
Fedora Modular 32 - x86_64 - Updates 351 kB/s | 4.3 MB 00:12
Fedora 32 - x86_64 - Updates 466 kB/s | 28 MB 01:02
Fedora 32 - x86_64 533 kB/s | 70 MB 02:14
Dependencies resolved.
============================================================================================================================================================================================================================
Package Architecture Version Repository Size
============================================================================================================================================================================================================================
Installing:
libuv x86_64 1:1.40.0-1.fc32 updates 152 k
Transaction Summary
============================================================================================================================================================================================================================
Install 1 Package
Total download size: 152 k
Installed size: 393 k
Downloading Packages:
libuv-1.40.0-1.fc32.x86_64.rpm 202 kB/s | 152 kB 00:00
----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------
Total 100 kB/s | 152 kB 00:01
Package libuv-1.40.0-1.fc32.x86_64.rpm is not signed
The downloaded packages were saved in cache until the next successful transaction.
You can remove cached packages by executing 'dnf clean packages'.
Error: GPG check FAILED
--
Endi S. Dewata
3 years, 3 months
Mono help
by Jerry James
Hello all,
Antlr4 4.9.1 is out. This is mostly a small change from version 4.9,
except that the mono runtime has changed drastically. Upstream now
builds against netstandard2.0 and netstandard2.1, and I can no longer
build with "xbuild Antlr4.mono.sln" because Antlr4.mono.sln is gone.
I figured out that the package needs to BR: dotnet, and build with
"dotnet build", and that we have to build against netstandard2.1 only.
That works fine, but then we try to install with gacutil:
Failure adding assembly
runtime/CSharp/bin/Debug/netstandard2.1/Antlr4.Runtime.Standard.dll to
the cache: Strong name cannot be verified for delay-signed assembly
Upstream provides Antlr4.snk, which is the public key. They don't
hand out their private key for obvious reasons, so I cannot sign with
it. So I remove the signing bits from Antlr4.csproj and try again:
Failure adding assembly
runtime/CSharp/bin/Debug/netstandard2.1/Antlr4.Runtime.Standard.dll to
the cache: Attempt to install an assembly without a strong name
I don't understand Mono or .NET at all, really. Can somebody who does
tell me what I'm supposed to do? The SRPM (with a delay-signed
assembly) is here:
https://jjames.fedorapeople.org/antlr4/antlr4-project-4.9.1-1.fc33.src.rpm
Thank you!
--
Jerry James
http://www.jamezone.org/
3 years, 3 months
Help with compiling SASS to CSS in a Python package
by Benjamin Beasley
I am the reviewer for “python-furo - A clean customizable documentation theme for Sphinx” (https://bugzilla.redhat.com/show_bug.cgi?id=1910798). The Python part of the package is clean and simple, and the submitter is responsive, competent, and helpful. I’d really like to be able to approve the package. However, the review is hung up on the web assets it includes.
Upstream uses gulp to compile/bundle and minify the JavaScript, and compile SASS to CSS, in order to produce the PyPI source tarball. Based on https://docs.fedoraproject.org/en-US/packaging-guidelines/JavaScript/#_co..., https://docs.fedoraproject.org/en-US/packaging-guidelines/Web_Assets/#_css, and https://docs.fedoraproject.org/en-US/packaging-guidelines/what-can-be-pac..., it will be necessary to use the GitHub source tarball instead and do all of the additional work in the RPM build.
For the Python part, in which the GitHub tarball is a PEP 517/518 format source tree without a “legacy” setup.py, python3-flit can do the job of building a wheel, and %py3_install_wheel can install it. No problem.
For the JavaScript part, bundling and minification can’t use uglify-js because ES6 “const” is used, and it can’t use esbuild (golang-github-evanw-esbuild) as intended because upstream does not use ES6 modules and imports. However, “bundling” by simple concatenation with cat, optionally followed by minification with esbuild, should work fine. It would break source maps, but at least the original sources would still be included in the RPM.
The problem is the SASS. Upstream uses gulp-sass with the JavaScript-transpiled version of dart-sass, which seems to be the only SASS compiler that is not deprecated today. Trying to compile with rubygem-sass or either frontend to libsass (sassc/rubygem-sassc) gives an error like:
sassc -a src/furo/assets/styles/furo.sass
Error: Invalid CSS after "...ow-y: scroll; }": expected 1 selector or at-rule, was "not(html):not(body)"
on line 20:24 of src/furo/assets/styles/_scaffold.sass
from line 5:1 of src/furo/assets/styles/furo.sass
>> overflow-y: scroll; }
-----------------------^
with various other errors following if the offending section is commented out. I don’t know SASS too well, but it doesn’t look too practical to patch our way out of this.
This is a call for help, then. Does anyone see a way forward for this package?
More details are in the review request Bugzilla issue, linked at the beginning of this email.
Thanks,
Ben Beasley
3 years, 3 months
Schedule for Wednesday's FESCo Meeting (2021-01-06)
by Zbigniew Jędrzejewski-Szmek
Following is the list of topics that will be discussed in the
FESCo meeting Wednesday at 15:00UTC in #fedora-meeting-2 on
irc.freenode.net.
To convert UTC to your local time, take a look at
http://fedoraproject.org/wiki/UTCHowto
or run:
date -d '2021-01-06 15:00 UTC'
Links to all issues to be discussed can be found at:
https://pagure.io/fesco/report/meeting_agenda
= Discussed and Voted in the Ticket =
#2527 F34 Change: Use ibus-m17n as the default IME for Vietnamese
https://pagure.io/fesco/issue/2527
APPROVED (+4, 0, 0)
#2526 F34 Change: LLVM 12
https://pagure.io/fesco/issue/2526
APPROVED (+5, 0, 0)
#2525 Updates Policy exception for black (python-black)
https://pagure.io/fesco/issue/2525
APPROVED (+4, 0, 0)
#2524 F34 Change: Boost 1.75 upgrade
https://pagure.io/fesco/issue/2524
APPROVED (+5, 0, 0)
#2523 F34 Change: Stop Shipping Individual Nodejs Library Packages
https://pagure.io/fesco/issue/2523
APPROVED (+4, 0, 0)
#2521 F34 Change: Stratis 2.3.0
https://pagure.io/fesco/issue/2521
APPROVED (+5, 0, 0)
#2520 F34 Change: Ignore Anaconda kernel boot parameters without 'inst.' prefix
https://pagure.io/fesco/issue/2520
APPROVED (+5, 0, 0)
#2518 F34 Change: Ruby 3.0
https://pagure.io/fesco/issue/2518
APPROVED (+6, 0, 0)
#2517 F34 Change: ntp replacement
https://pagure.io/fesco/issue/2517
APPROVED (+5, 0, 0)
#2515 F34 Change: Xwayland as a standalone package
https://pagure.io/fesco/issue/2515
APPROVED (+4, 0, 0)
#2514 F34 Change: ibus-anthy for default Japanese IME
https://pagure.io/fesco/issue/2514
APPROVED (+3, 1, 0)
#2506 Nonresponsive maintainer: John Dennis (jdennis)
https://pagure.io/fesco/issue/2506
APPROVED (+4, 0, 0)
= Followups =
#2473 updates policy is out of date
https://pagure.io/fesco/issue/2473
Please review the latest pull request
(https://pagure.io/fesco/fesco-docs/pull-request/41).
= New business =
#2535 F34 Change: Enable systemd-oomd by default for all variants
https://pagure.io/fesco/issue/2535
#2532 F34 Change: Enable spec file preprocessing
https://pagure.io/fesco/issue/2532
= Open Floor =
For more complete details, please visit each individual
issue. The report of the agenda items can be found at
https://pagure.io/fesco/report/meeting_agenda
If you would like to add something to this agenda, you can
reply to this e-mail, file a new issue at
https://pagure.io/fesco, e-mail me directly, or bring it
up at the end of the meeting, during the open floor topic. Note
that added topics may be deferred until the following meeting.
3 years, 3 months
