753218 – sys-auth/polkit-0.118: stabilize

Bug 753218 - sys-auth/polkit-0.118: stabilize

Summary: sys-auth/polkit-0.118: stabilize

Status:	RESOLVED FIXED

Alias:	None

Product:	Gentoo Linux
Classification:	Unclassified
Component:	Stabilization (show other bugs)
Hardware:	All Linux

Importance:	Normal normal (vote)
Assignee:	Freedesktop bugs

URL:
Whiteboard:
Keywords:	CC-ARCHES, STABLEREQ

Depends on:
Blocks:

Reported:	2020-11-05 16:11 UTC by Matt Turner
Modified:	2020-11-24 17:10 UTC (History)
CC List:	2 users (show)

See Also:	753233
Package list:	dev-lang/spidermonkey-78.4.0 amd64 arm arm64 ppc64 x86 sys-auth/polkit-0.118 amd64 arm arm64 ppc64 x86
Runtime testing required:	---

Flags:	nattka: sanity-check+

Attachments
Add an attachment (proposed patch, testcase, etc.)

Note You need to log in before you can comment on or make changes to this bug.

Description Matt Turner gentoo-dev

2020-11-05 16:11:02 UTC

Can we stabilize polkit-0.117? In tree since August 1 and it depends on spidermonkey:68 which is what is used by current stable GNOME, so we could depclean spidermonkey:60 from a lot of systems if we stabilized this.

Comment 1 NATTkA bot gentoo-dev

2020-11-05 16:12:59 UTC Comment hidden (obsolete)

Sanity check failed:

> sys-auth/polkit-0.117
>   depend ppc stable profile default/linux/powerpc/ppc32/17.0 (27 total)
>     dev-lang/spidermonkey:68[-debug]
>   rdepend ppc stable profile default/linux/powerpc/ppc32/17.0 (27 total)
>     dev-lang/spidermonkey:68[-debug]
>   depend ppc64 dev profile default/linux/ppc64le/17.0/desktop/plasma (2 total)
>     dev-lang/spidermonkey:68[-debug]
>   rdepend ppc64 dev profile default/linux/ppc64le/17.0/desktop/plasma (2 total)
>     dev-lang/spidermonkey:68[-debug]

Comment 2 Andreas Sturmlechner gentoo-dev

2020-11-05 16:13:42 UTC

Why not 0.118 when that is in tree since Sep 17.

Comment 3 Lars Wendler (Polynomial-C) (RETIRED) gentoo-dev

2020-11-05 16:15:03 UTC

(In reply to Andreas Sturmlechner from comment #2)
> Why not 0.118 when that is in tree since Sep 17.

Because that requires dev-lang/spidermonkey:78 which is not stable (yet).

Comment 4 NATTkA bot gentoo-dev

2020-11-05 16:20:59 UTC Comment hidden (obsolete)

Sanity check failed:

> sys-auth/polkit-0.117
>   depend sparc stable profile default/linux/sparc/17.0 (8 total)
>     dev-lang/spidermonkey:68[-debug]
>   rdepend sparc stable profile default/linux/sparc/17.0 (8 total)
>     dev-lang/spidermonkey:68[-debug]

Comment 5 Thomas Deutschmann (RETIRED) gentoo-dev

2020-11-05 16:22:18 UTC

Feel free to do stabilize :78.

Comment 6 NATTkA bot gentoo-dev

2020-11-05 16:29:02 UTC Comment hidden (obsolete)

Sanity check failed:

> sys-auth/polkit-0.118
>   depend arm dev profile default/linux/arm/17.0/armv4 (30 total)
>     dev-lang/spidermonkey:78[-debug]
>   rdepend arm dev profile default/linux/arm/17.0/armv4 (30 total)
>     dev-lang/spidermonkey:78[-debug]

Comment 7 NATTkA bot gentoo-dev

2020-11-05 16:32:57 UTC Comment hidden (obsolete)

Sanity check failed:

> sys-auth/polkit-0.118
>   depend arm dev profile default/linux/arm/17.0/armv4 (30 total)
>     dev-lang/spidermonkey:78[-debug]
>   rdepend arm dev profile default/linux/arm/17.0/armv4 (30 total)
>     dev-lang/spidermonkey:78[-debug]

Comment 8 Andreas Sturmlechner gentoo-dev

2020-11-05 16:35:04 UTC

It is a bit disappointing that dev-lang/spidermonkey:78 rekeywording effort was not started right away, but at least 78 can already be stabilised on every arch that currently has 68 stable.

Comment 9 Matt Turner gentoo-dev

2020-11-05 16:42:07 UTC

(In reply to Andreas Sturmlechner from comment #8)
> It is a bit disappointing that dev-lang/spidermonkey:78 rekeywording effort
> was not started right away, but at least 78 can already be stabilised on
> every arch that currently has 68 stable.

I was frustrated by this too, but I learned that the reason is that spidermonkey:78 requires Rust, so I feel a little better about it.

Comment 10 Andreas Sturmlechner gentoo-dev

2020-11-05 16:47:28 UTC

Oh I see. In that case it makes sense to do 0.117 with 68 in the meantime to get rid of old much faster.

Comment 11 Matt Turner gentoo-dev

2020-11-05 18:19:49 UTC

Removing arm from keyword list since spidermonkey:78 doesn't work on all arm profiles.

Comment 12 NATTkA bot gentoo-dev

2020-11-05 18:21:00 UTC Comment hidden (obsolete)

All sanity-check issues have been resolved

Comment 13 Larry the Git Cow gentoo-dev

2020-11-06 07:17:07 UTC

The bug has been referenced in the following commit(s):

https://gitweb.gentoo.org/repo/gentoo.git/commit/?id=92009e6b8982e74479a2f1f783aa0d88950c3f21

commit 92009e6b8982e74479a2f1f783aa0d88950c3f21
Author:     Sam James <sam@gentoo.org>
AuthorDate: 2020-11-06 07:16:32 +0000
Commit:     Sam James <sam@gentoo.org>
CommitDate: 2020-11-06 07:17:03 +0000

    profiles/arch/arm: mask >=sys-auth/polkit-0.118 where no Rust
    
    Bug: https://bugs.gentoo.org/753218
    Signed-off-by: Sam James <sam@gentoo.org>

 profiles/arch/arm/armv4/package.mask   | 1 +
 profiles/arch/arm/armv4t/package.mask  | 1 +
 profiles/arch/arm/armv5te/package.mask | 1 +
 3 files changed, 3 insertions(+)

Comment 14 Sam James archtester

2020-11-06 10:31:29 UTC

x86 done

Comment 15 Sam James archtester

2020-11-06 10:34:33 UTC

amd64 done

Comment 16 Sam James archtester

2020-11-06 10:57:19 UTC

arm64 done

Comment 17 Sam James archtester

2020-11-06 14:50:55 UTC

arm done

Comment 18 Sam James archtester

2020-11-06 20:08:10 UTC

ppc64 stable, closing

Comment 19 flippynelle 2020-11-24 06:10:26 UTC

can't emerge sys-auth/polkit-0.118 because none of the two available spidermonkey:78 versions compile:
=dev-lang/spidermonkey-78.4.1                                                                                                                                                                   
=dev-lang/spidermonkey-78.5.0

sample:

#     Running `CARGO=/usr/lib/rust/1.48.0/bin/cargo-1.48.0 CARGO_CRATE_NAME=mozglue_static CARGO_MANIFEST_DIR=/var/tmp/portage/dev-lang/spidermonkey-78.5.0/work/firefox-78.5.0/mozglue/static/rust CARGO_PKG_AUTHORS='' CARGO_PKG_DESCRIPTION='' CARGO_PKG_HOMEPAGE='' CARGO_PKG_LICENSE=MPL CARGO_PKG_LICENSE_FILE='' CARGO_PKG_NAME=mozglue-static CARGO_PKG_REPOSITORY='' CARGO_PKG_VERSION=0.1.0 CARGO_PKG_VERSION_MAJOR=0 CARGO_PKG_VERSION_MINOR=1 CARGO_PKG_VERSION_PATCH=0 CARGO_PKG_VERSION_PRE='' LD_LIBRARY_PATH='/var/tmp/portage/dev-lang/spidermonkey-78.5.0/work/build/release/deps:/usr/lib/rust/1.48.0/lib' OUT_DIR=/var/tmp/portage/dev-lang/spidermonkey-78.5.0/work/build/x86_64-unknown-linux-gnu/release/build/mozglue-static-72dcbf608171b403/out /usr/bin/rustc --crate-name mozglue_static --edition=2018 mozglue/static/rust/lib.rs --error-format=json --json=diagnostic-rendered-ansi,artifacts --crate-type lib --emit=dep-info,metadata,link -C opt-level=2 -C panic=abort -C embed-bitcode=no -C metadata=57b5a9ebbf075e53 -C extra-filename=-57b5a9ebbf075e53 --out-dir /var/tmp/portage/dev-lang/spidermonkey-78.5.0/work/build/x86_64-unknown-linux-gnu/release/deps --target x86_64-unknown-linux-gnu -C linker=/var/tmp/portage/dev-lang/spidermonkey-78.5.0/work/firefox-78.5.0/build/cargo-linker -L dependency=/var/tmp/portage/dev-lang/spidermonkey-78.5.0/work/build/x86_64-unknown-linux-gnu/release/deps -L dependency=/var/tmp/portage/dev-lang/spidermonkey-78.5.0/work/build/release/deps --extern arrayvec=/var/tmp/portage/dev-lang/spidermonkey-78.5.0/work/build/x86_64-unknown-linux-gnu/release/deps/libarrayvec-6f7b713bca0f4652.rmeta -C opt-level=2 -C debuginfo=2 -C force-frame-pointers=yes --cap-lints warn -C codegen-units=1 -L native=/var/tmp/portage/dev-lang/spidermonkey-78.5.0/work/build/x86_64-unknown-linux-gnu/release/build/mozglue-static-72dcbf608171b403/out -l static=wrappers -l stdc++`
#error[E0432]: unresolved import `crate::arch::x86_64::__m64`
#  --> /var/tmp/portage/dev-lang/spidermonkey-78.5.0/work/firefox-78.5.0/third_party/rust/packed_simd/src/api/into_bits/arch_specific.rs:51:15
#   |
#51 |               $($arch_ty),*
#   |                 ^^^^^^^^ no `__m64` in `arch::x86_64`
#...
#86 | / impl_arch!(
#87 | |     [x86["x86"]: __m64], [x86_64["x86_64"]: __m64],
#88 | |     [arm["arm"]: int8x8_t, uint8x8_t, poly8x8_t, int16x4_t, uint16x4_t,
#89 | |      poly16x4_t, int32x2_t, uint32x2_t, float32x2_t, int64x1_t,
#...  |
#96 | |     test: test_v64
#97 | | );
#   | |__- in this macro invocation
#   |
#   = note: this error originates in a macro (in Nightly builds, run with -Z macro-backtrace for more info)
#

Comment 20 flippynelle 2020-11-24 07:27:22 UTC

(In reply to flippynelle from comment #19)

apparently, this is an issue with encoding_rs using packed_simd version 0.3.3 instead of 0.3.4

as per: https://github.com/hsivonen/encoding_rs/pull/58
via: https://github.com/BurntSushi/ripgrep/issues/1721

that being said, firefox emerge also fails with the same errors

0.3.3 packed_simd is being used in:

/var/tmp/portage/www-client/firefox-83.0/work/firefox-83.0/third_party/rust/packed_simd/Cargo.toml


didn't check spidermonkey

I should probably make it a new bug report but sooooo lazy, but maybe if someone smacks me over the head...

Comment 21 Sam James archtester

2020-11-24 14:25:01 UTC

(In reply to flippynelle from comment #20)
> (In reply to flippynelle from comment #19)
> 
> apparently, this is an issue with encoding_rs using packed_simd version
> 0.3.3 instead of 0.3.4
> 
> as per: https://github.com/hsivonen/encoding_rs/pull/58
> via: https://github.com/BurntSushi/ripgrep/issues/1721
> 
> that being said, firefox emerge also fails with the same errors
> 
> 0.3.3 packed_simd is being used in:
> 
> /var/tmp/portage/www-client/firefox-83.0/work/firefox-83.0/third_party/rust/
> packed_simd/Cargo.toml
> 
> 
> didn't check spidermonkey
> 
> I should probably make it a new bug report but sooooo lazy, but maybe if
> someone smacks me over the head...

Yes, please file a new one, commenting on a closed unrelated bug will be easily missed.

Comment 22 flippynelle 2020-11-24 16:05:37 UTC

Thanks. Someone else already did it in https://bugs.gentoo.org/756334

Comment 23 Matt Turner gentoo-dev

2020-11-24 17:10:57 UTC

(In reply to flippynelle from comment #20)
> I should probably make it a new bug report but sooooo lazy, but maybe if
> someone smacks me over the head...

Don't ever do this again, please.