Fedora-Rawhide-20220211.n.3 compose check report

Missing expected images: Minimal raw-xz armhfp Compose FAILS proposed Rawhide gating check! 10 of 43 required tests failed, 4 results missing openQA tests matching unsatisfied gating requirements shown with **GATING** below Failed openQA tests: 34/231 (x86_64), 20/161 (aarch64) New failures (s

Re: Unannounced soname bump: libjasper.so.4 -> libjasper.so.6

On 12. 02. 22 2:42, Miro Hrončok wrote: I've cc'ed them on all rebuild and received no reply. *I've cc'ed them on all my emails. -- Miro Hrončok -- Phone: +420777974800 IRC: mhroncok ___ devel mailing list -- devel@lists.fedoraproject.org To unsubsc

Re: Unannounced soname bump: libjasper.so.4 -> libjasper.so.6

On 11. 02. 22 21:45, Kevin Kofler via devel wrote: Miro Hrončok wrote: It was actually announced: https://lists.fedoraproject.org/archives/list/devel@lists.fedoraproject.org/thread/FV53ADNJB5STFN3YAEEXEVHMIA6DMXCN/ But for reasons I don't understand, it was pushed to rawhide without using a

Re: report on the "ELF package notes" status

On Fri, Feb 11, 2022 at 08:27:51PM +0100, Miro Hrončok wrote: > On 11. 02. 22 20:01, Zbigniew Jędrzejewski-Szmek wrote: > > I did some quick analysis, and the reasons why the notes section is > > missing differ: > >... > >61 python packages > > So... Are the Python packages explicitly opti

Re: What should we do about the "Install only newly recommended packages on upgrades" F36 change?

On 11. 02. 22 21:58, Kevin Kofler via devel wrote: Miro Hrončok wrote: Another thing I'd like to understand from your POV is why would packagers actually *need* exactly-versioned Recommends. Could you please give me an example use case? I understand why they might *assume they need* it, because

Re: Rawhide arm compiler bug?

* David Muse: > Ahh, ok. Should I mark any buzilla bugs that I get as duplicates of > that one? Yes, and rebuild in Koji. Koji has the fixed compiler. Thanks, Florian ___ devel mailing list -- devel@lists.fedoraproject.org To unsubscribe send an emai

Re: Rawhide arm compiler bug?

On Fri, 11 Feb 2022 21:37:55 +0100 Florian Weimer wrote: > * David Muse: > > > Forgive me if I'm pointing out a known issue, but I haven't noticed > > anything on the list about this yet... > > > > I keep getting sent rawhide build errors for my project. They only appear > > to occur on the a

Re: Unannounced soname bump: libjasper.so.4 -> libjasper.so.6

On Fri, Feb 11, 2022 at 09:45:53PM +0100, Kevin Kofler via devel wrote: > Miro Hrončok wrote: > > It was actually announced: > > > > > https://lists.fedoraproject.org/archives/list/devel@lists.fedoraproject.org/thread/FV53ADNJB5STFN3YAEEXEVHMIA6DMXCN/ > > > > But for reasons I don't understand,

Re: What should we do about the "Install only newly recommended packages on upgrades" F36 change?

Miro Hrončok wrote: > Another thing I'd like to understand from your POV is why would packagers > actually *need* exactly-versioned Recommends. Could you please give me an > example use case? I understand why they might *assume they need* it, > because packaging is complex and this might seem like

Re: Unannounced soname bump: libjasper.so.4 -> libjasper.so.6

Miro Hrončok wrote: > It was actually announced: > > https://lists.fedoraproject.org/archives/list/devel@lists.fedoraproject.org/thread/FV53ADNJB5STFN3YAEEXEVHMIA6DMXCN/ > > But for reasons I don't understand, it was pushed to rawhide without using > a side tag and without doing rebuilds :( > >

Re: Rawhide arm compiler bug?

* David Muse: > Forgive me if I'm pointing out a known issue, but I haven't noticed anything > on the list about this yet... > > I keep getting sent rawhide build errors for my project. They only appear to > occur on the avmv7hl platform. It builds fine on all other architectures. > > > The er

Re: Problems building on F36, F37 caused by vtk?

On Fri, Feb 11, 2022 at 08:33:14PM +0100, Miro Hrončok wrote: > On 11. 02. 22 20:31, Miro Hrončok wrote: > > On 11. 02. 22 20:21, Kevin Fenzi wrote: > > > > I would be really happy to drop armv7hl for the vtk stack. > > > So, just to clarify and provide more info here: > > > > > > There's a bug/is

Re: Fedora ID and HTTPS

On Thu, Feb 03, 2022 at 07:16:01AM -0800, Jan Staněk wrote: > Hi list, > > tl;dr: Why is the Fedora ID server using HTTP communication by default? Fedora openid is using http because long ago when we started offering openid users were 'http://username.id.fedoraproject.org' and thus were tied to t

Re: Problems building on F36, F37 caused by vtk?

On 11. 02. 22 20:31, Miro Hrončok wrote: On 11. 02. 22 20:21, Kevin Fenzi wrote: I would be really happy to drop armv7hl for the vtk stack. So, just to clarify and provide more info here: There's a bug/issue with 32bit arm using LPAE kernels and xfs/ext4 where it's overeager with OOM killing p

Re: Problems building on F36, F37 caused by vtk?

On 11. 02. 22 20:21, Kevin Fenzi wrote: I would be really happy to drop armv7hl for the vtk stack. So, just to clarify and provide more info here: There's a bug/issue with 32bit arm using LPAE kernels and xfs/ext4 where it's overeager with OOM killing processes. ( rhbz 1920183 ). The issue does

Re: Do we have any policy for disabling inactive users

On Fri, Feb 11, 2022 at 07:12:04AM -0600, Richard Shaw wrote: > Not quoting anyone in particular but I thought I saw it referenced in this > thread (and definitely the previous thread from last year). > > What's wrong with having someone "sign" the CLA every year? At work a > non-disclosure is onl

Re: report on the "ELF package notes" status

On 11. 02. 22 20:01, Zbigniew Jędrzejewski-Szmek wrote: I did some quick analysis, and the reasons why the notes section is missing differ: ... 61 python packages So... Are the Python packages explicitly opting out? Python itself does not, instead it stores %extension_ldflags rather than

Re: report on the "ELF package notes" status

On Fri, 2022-02-11 at 20:01 +0100, Zbigniew Jędrzejewski-Szmek wrote: > Hi! > > I did some quick'n'dirty statistics of how many ELF files successfully gained > a .package.note section. > > packages: 28742, see [1] for the list (*) > ELF files: 72464, see [2] > ELF files with .package.note: 47939,

Re: Do we have any policy for disabling inactive users

On Fri, Feb 11, 2022 at 11:33:13AM +, Mattia Verga via devel wrote: > Il 11/02/22 12:20, Florian Weimer ha scritto: > > * Mattia Verga via devel: > > > >> Il 11/02/22 10:41, Miro Hrončok ha scritto: > >>> On 11. 02. 22 10:12, Mattia Verga via devel wrote: > Where are those 2543 packagers c

Re: Problems building on F36, F37 caused by vtk?

On Thu, Feb 10, 2022 at 07:29:56PM -0700, Orion Poplawski wrote: > On 2/10/22 12:21, Michael Catanzaro wrote: > > On Thu, Feb 10 2022 at 02:09:32 PM -0500, Steven A. Falco > > wrote: > > > g++: fatal error: Killed signal terminated program cc1plus > > > > This indicates the builder ran out of mem

Re: Bodhi and "update ejected from the push" errors

On Thu, Feb 10, 2022 at 12:31:15PM +, Sérgio Basto wrote: > On Sat, 2022-01-29 at 11:12 -0800, Kevin Fenzi wrote: > > On Sat, Jan 29, 2022 at 05:38:42PM +, Mattia Verga via devel > > wrote: > > > Recently we're having some (a lot) of errors about updates stuck in > > > Bodhi with errors lik

Re: Fedora 36 Mass Branching

On 09. 02. 22 22:12, Zbigniew Jędrzejewski-Szmek wrote: On Wed, Feb 09, 2022 at 05:12:16PM +, Jonathan Wakely wrote: On Tue, 8 Feb 2022 at 20:40, Tomas Hrcka wrote: Hi All, Fedora 36 has now been branched, please be sure to do a git pull --rebase to pick up the new branch This part als

report on the "ELF package notes" status

Hi! I did some quick'n'dirty statistics of how many ELF files successfully gained a .package.note section. packages: 28742, see [1] for the list (*) ELF files: 72464, see [2] ELF files with .package.note: 47939, see [3] ELF files without: 24525, see [4] It turns out that many of those are specia

Rawhide arm compiler bug?

Forgive me if I'm pointing out a known issue, but I haven't noticed anything on the list about this yet... I keep getting sent rawhide build errors for my project. They only appear to occur on the avmv7hl platform. It builds fine on all other architectures. The errors are like: sha1.cpp: In

Re: What should we do about the "Install only newly recommended packages on upgrades" F36 change?

On 11. 02. 22 13:50, Jaroslav Mracek wrote: > No we didn't and it will make the feature less usable - see reported issues > during testing in original request ( > https://bugzilla.redhat.com/show_bug.cgi?id=1699672#c74 )

Re: Action Required: Bugzilla - API Authentication changes

On 01. 02. 22 14:25, Pierre-Yves Chibon wrote: On Tue, Feb 01, 2022 at 01:41:01PM +0100, Miro Hrončok wrote: On 01. 02. 22 13:37, Fabio Valentini wrote: Hi Miro, Thanks for forwarding this announcement. Apparently the talk about "improving communication between RHBZ and the Fedora Project" has

Re: JasPer 3.0.0 update in Rawhide and F36

On 11. 02. 22 15:20, Miro Hrončok wrote: On 09. 02. 22 17:03, Josef Řídký wrote: Hi, upstream authors of JasPer library have released a new major version. This rebase will introduce .so name bump from version 4 to version 6. I am going to rebase the library in rawhide on Friday February 11th

Re: [Fedocal] Reminder meeting : ELN SIG

On Fri, Feb 11, 2022 at 10:15 AM Stephen Gallagher wrote: > > On Thu, Feb 10, 2022 at 7:00 AM wrote: > > > > Dear all, > > > > You are kindly invited to the meeting: > >ELN SIG on 2022-02-11 from 12:00:00 to 13:00:00 US/Eastern > >At fedora-meet...@irc.libera.chat > > > > The meeting will

Re: Mathematical packages: looking for maintainers

Hi all, thank you Miro for the check of the dependency chain. Jerry, feel free to transfer the ownership to me: python-readthedocs-sphinx-ext -> ksurma python-sphinx_rtd_theme -> ksurma Have a great weekend, Karolina On 2/10/22 19:17, Miro Hrončok wrote: > On 09. 02. 22 16:38, Jerry James wrot

Re: [Fedocal] Reminder meeting : ELN SIG

On Thu, Feb 10, 2022 at 7:00 AM wrote: > > Dear all, > > You are kindly invited to the meeting: >ELN SIG on 2022-02-11 from 12:00:00 to 13:00:00 US/Eastern >At fedora-meet...@irc.libera.chat > > The meeting will be about: > Does anyone have a topic for the agenda, or shall we skip this we

Re: Unannounced soname bump: libjasper.so.4 -> libjasper.so.6

Mamoru TASAKA wrote on 2022/02/11 23:41: Miro Hrončok wrote on 2022/02/11 23:29: On 11. 02. 22 15:20, Mamoru TASAKA wrote: Hello, all: On rawhide (f37) jasper is updated from 2.0.33-2 to 3.0.0-1, which causes unannounced soname bump from  libjasper.so.4 to libjasper.so.6. What is strange here

Re: Unannounced soname bump: libjasper.so.4 -> libjasper.so.6

./find_unblocked_orphans.py --max_deps 1 --skip-orphans jasper Depending on: jasper (30), DevIL (maintained by: jwrdegoede) DevIL-1.7.8-38.fc36.i686 requires libjasper.so.4 DevIL-1.7.8-38.fc36.src requires jasper-devel = 2.0.33-2.fc36 DevIL-1.7.8-38.fc36.x86_64 requires libjasper.so.4()(64bit) De

Re: Unannounced soname bump: libjasper.so.4 -> libjasper.so.6

Miro Hrončok wrote on 2022/02/11 23:29: On 11. 02. 22 15:20, Mamoru TASAKA wrote: Hello, all: On rawhide (f37) jasper is updated from 2.0.33-2 to 3.0.0-1, which causes unannounced soname bump from  libjasper.so.4 to libjasper.so.6. What is strange here is that the committer seems aware of this

Re: What should we do about the "Install only newly recommended packages on upgrades" F36 change?

On Fri, Feb 11, 2022 at 02:05:15PM +0100, Kevin Kofler via devel wrote: > Am Freitag, 11. Februar 2022 13:50:57 CET schrieb Jaroslav Mracek: > > On Tue, Feb 8, 2022 at 7:30 PM Zbigniew Jędrzejewski-Szmek < > > zbys...@in.waw.pl> wrote: > > > Hmm, but why is metadata of repository needed? IIUC, all

Re: Unannounced soname bump: libjasper.so.4 -> libjasper.so.6

On 11. 02. 22 15:20, Mamoru TASAKA wrote: Hello, all: On rawhide (f37) jasper is updated from 2.0.33-2 to 3.0.0-1, which causes unannounced soname bump from  libjasper.so.4 to libjasper.so.6. What is strange here is that the committer seems aware of this change: https://src.fedoraproject.org/rp

Re: JasPer 3.0.0 update in Rawhide and F36

Josef Řídký wrote on 2022/02/11 22:55: Hi, just reminder - a new jasper version is now available in Rawhide. All packages that require jasper, should be rebuilt - in most cases it is all that is needed. In rare occasions more work would be needed - this is valid for packages, which didn't use j

Unannounced soname bump: libjasper.so.4 -> libjasper.so.6

Hello, all: On rawhide (f37) jasper is updated from 2.0.33-2 to 3.0.0-1, which causes unannounced soname bump from libjasper.so.4 to libjasper.so.6. What is strange here is that the committer seems aware of this change: https://src.fedoraproject.org/rpms/jasper/c/13f23ce40bfeafccd96ecc8872f965e

Re: JasPer 3.0.0 update in Rawhide and F36

On 09. 02. 22 17:03, Josef Řídký wrote: Hi, upstream authors of JasPer library have released a new major version. This rebase will introduce .so name bump from version 4 to version 6. I am going to rebase the library in rawhide on Friday February 11th. For testing purposes, you may use the c

Re: JasPer 3.0.0 update in Rawhide and F36

Hi, just reminder - a new jasper version is now available in Rawhide. All packages that require jasper, should be rebuilt - in most cases it is all that is needed. In rare occasions more work would be needed - this is valid for packages, which didn't use jasper library in the standard way. Best

Re: Do we have any policy for disabling inactive users

Not quoting anyone in particular but I thought I saw it referenced in this thread (and definitely the previous thread from last year). What's wrong with having someone "sign" the CLA every year? At work a non-disclosure is only good for two years. Is a CLA a lifetime agreement? Thanks, Richard __

Re: What should we do about the "Install only newly recommended packages on upgrades" F36 change?

Am Freitag, 11. Februar 2022 13:50:57 CET schrieb Jaroslav Mracek: On Tue, Feb 8, 2022 at 7:30 PM Zbigniew Jędrzejewski-Szmek < zbys...@in.waw.pl> wrote: Hmm, but why is metadata of repository needed? IIUC, all deps (including rich) are part of the package header, i.e. are in the RPM database fo

Re: Do we have any policy for disabling inactive users

Dne 11. 02. 22 v 11:38 Björn Persson napsal(a): Gary Buhrmaster wrote: A quick (and likely bad and incomplete) bugzilla search shows over 1000 tickets where there are upstream updates that are still in NEW status in bugzilla and had been (initially) opened over a year ago. I think that represe

Re: What should we do about the "Install only newly recommended packages on upgrades" F36 change?

On Tue, Feb 8, 2022 at 7:30 PM Zbigniew Jędrzejewski-Szmek < zbys...@in.waw.pl> wrote: > On Tue, Feb 08, 2022 at 02:30:30PM +0100, Jaroslav Mracek wrote: > > On Tue, Feb 8, 2022 at 1:56 PM Kevin Kofler via devel < > > devel@lists.fedoraproject.org> wrote: > > > > > Jaroslav Mracek wrote: > > > > I

Re: Do we have any policy for disabling inactive users

Il 11/02/22 13:11, Zbigniew Jędrzejewski-Szmek ha scritto: > On Fri, Feb 11, 2022 at 11:42:19AM +, Mattia Verga via devel wrote: >> I've written down a script [1] to fetch users which belong to packager >> group and show no activity in datagrepper in a year. >> >> It found 104 users [2]. >> >>

Re: Do we have any policy for disabling inactive users

On Fri, Feb 11, 2022 at 11:42:19AM +, Mattia Verga via devel wrote: > I've written down a script [1] to fetch users which belong to packager > group and show no activity in datagrepper in a year. > > It found 104 users [2]. > > [1] > https://mattia.fedorapeople.org/inactive-packagers/find_ina

Re: Do we have any policy for disabling inactive users

On Fri, Feb 11, 2022 at 10:43 AM Ian McInerney via devel wrote: > > On Fri, Feb 11, 2022 at 10:39 AM Björn Persson wrote: >> >> Yes, that's a bad search. Till Maas told me eight years ago that the >> release monitoring tickets are supposed to remain open when the >> packages are upgraded. Thus an

Re: Do we have any policy for disabling inactive users

I've written down a script [1] to fetch users which belong to packager group and show no activity in datagrepper in a year. It found 104 users [2]. [1] https://mattia.fedorapeople.org/inactive-packagers/find_inactive_packagers.py [2] https://mattia.fedorapeople.org/inactive-packagers/inactive_use

Re: Do we have any policy for disabling inactive users

Il 11/02/22 12:20, Florian Weimer ha scritto: > * Mattia Verga via devel: > >> Il 11/02/22 10:41, Miro Hrončok ha scritto: >>> On 11. 02. 22 10:12, Mattia Verga via devel wrote: Where are those 2543 packagers come from? src.fedoraproject.org only shows 1787 users in the packager group: >>

Re: Do we have any policy for disabling inactive users

* Mattia Verga via devel: > Il 11/02/22 10:41, Miro Hrončok ha scritto: >> On 11. 02. 22 10:12, Mattia Verga via devel wrote: >>> Where are those 2543 packagers come from? src.fedoraproject.org only >>> shows 1787 users in the packager group: >>> >>> https://src.fedoraproject.org/api/0/group/packa

Re: How to clone by fedpkg ?

Well done. Thanks for you Artur. On 2022/2/11 17:33, Artur Frenszek-Iwicki wrote: You need to generate an SSH key and upload it to https://accounts.fedoraproject.org Log in, go to Settings and switch to the "SSH & GPG keys". If this isn't the only key you're using, you will also need to edit

Re: Do we have any policy for disabling inactive users

On Fri, Feb 11, 2022 at 10:39 AM Björn Persson wrote: > Gary Buhrmaster wrote: > > A quick (and likely > > bad and incomplete) bugzilla search shows > > over 1000 tickets where there are upstream > > updates that are still in NEW status in > > bugzilla and had been (initially) opened > > over a y

Re: Do we have any policy for disabling inactive users

Ben Cotton wrote: > I would support removing the 113 who don't exist in Koji. If they have been that way for a long time, I suppose. Don't cause additional hurdles for newcomers just because their first review takes a while. Björn Persson pgp11SGC3hJR2.pgp Description: OpenPGP digital signatur

Re: Do we have any policy for disabling inactive users

Gary Buhrmaster wrote: > A quick (and likely > bad and incomplete) bugzilla search shows > over 1000 tickets where there are upstream > updates that are still in NEW status in > bugzilla and had been (initially) opened > over a year ago. I think that represents > around 350 unique people. Those p

Re: Do we have any policy for disabling inactive users

Il 11/02/22 10:41, Miro Hrončok ha scritto: > On 11. 02. 22 10:12, Mattia Verga via devel wrote: >> Il 10/02/22 22:57, Ben Cotton ha scritto: >>> On Thu, Feb 10, 2022 at 1:39 PM Zbigniew Jędrzejewski-Szmek >>> wrote: since you have the script handy, could you check how many (non-pp) pack

Re: Mock v2.16 release, mock-core-configs v37

On Wednesday, February 2, 2022 3:28:30 PM CET Pavel Raiskup wrote: > Hello folks. > > I know the current Mock+configs Bodhi updates have not meet stable so far. > > The main problem being resolved is that 'fedpkg mockbuild' on 'epel8' > checked-out branch doesn't work properly ATM. I was informe

Fedora-Cloud-34-20220211.0 compose check report

No missing expected images. Soft failed openQA tests: 1/8 (x86_64), 1/8 (aarch64) (Tests completed, but using a workaround for a known bug) Old soft failures (same test soft failed in Fedora-Cloud-34-20220210.0): ID: 1125439 Test: x86_64 Cloud_Base-qcow2-qcow2 cloud_autocloud URL: https://op

Re: Mathematical packages: looking for maintainers

Hi. Feel free to asing me as a maintainer of python-repoze-sphinx-autointerface. The package has dead upstream so I hope nothing will break soon. Have a nice day. Lumír On 2/10/22 19:17, Miro Hrončok wrote: On 09. 02. 22 16:38, Jerry James wrote: On Tue, Feb 8, 2022 at 1:20 PM Miro Hrončo

Re: Do we have any policy for disabling inactive users

On 11. 02. 22 10:12, Mattia Verga via devel wrote: Il 10/02/22 22:57, Ben Cotton ha scritto: On Thu, Feb 10, 2022 at 1:39 PM Zbigniew Jędrzejewski-Szmek wrote: since you have the script handy, could you check how many (non-pp) packagers would be reported as inactive pretty please? Maybe with t

Re: How to clone by fedpkg ?

You need to generate an SSH key and upload it to https://accounts.fedoraproject.org Log in, go to Settings and switch to the "SSH & GPG keys". If this isn't the only key you're using, you will also need to edit your ssh config. A.FI. ___ devel mailing

How to clone by fedpkg ?

Hi developer, I want to clone the rpms through fedpkg, but failed log like this: jmiao@fedora36:temp$ fedpkg clone tboot Cloning into 'tboot'... miaojun0...@pkgs.fedoraproject.org: Permission denied (publickey). fatal: Could not read from remote reposito

Re: Do we have any policy for disabling inactive users

Il 10/02/22 22:57, Ben Cotton ha scritto: > On Thu, Feb 10, 2022 at 1:39 PM Zbigniew Jędrzejewski-Szmek > wrote: >> since you have the script handy, could you check how many (non-pp) >> packagers would be reported as inactive pretty please? Maybe with the >> inactivility threshold raised to 1 year

Re: Do we have any policy for disabling inactive users

Mattia Verga via devel writes: > Il 11/02/22 07:54, Zbigniew Jędrzejewski-Szmek ha scritto: >> On Thu, Feb 10, 2022 at 11:05:03PM +, Gary Buhrmaster wrote: >>> On Thu, Feb 10, 2022 at 9:58 PM Ben Cotton wrote: >>> I have concerns with this approach. I would guess there's a long tail >>>

Fedora-Cloud-35-20220211.0 compose check report

No missing expected images. Soft failed openQA tests: 1/8 (x86_64), 1/8 (aarch64) (Tests completed, but using a workaround for a known bug) Old soft failures (same test soft failed in Fedora-Cloud-35-20220210.0): ID: 1125423 Test: x86_64 Cloud_Base-qcow2-qcow2 cloud_autocloud URL: https://op

Re: Do we have any policy for disabling inactive users

Il 11/02/22 07:54, Zbigniew Jędrzejewski-Szmek ha scritto: > On Thu, Feb 10, 2022 at 11:05:03PM +, Gary Buhrmaster wrote: >> On Thu, Feb 10, 2022 at 9:58 PM Ben Cotton wrote: >> >>> I have concerns with this approach. I would guess there's a long tail >>> of packagers that maintain relatively

Re: How to make fedpkg --release epel9 mockbuild use crb?

On Sunday, February 6, 2022 8:35:15 PM CET Roman Inflianskas via devel wrote: > Sorry, I've forgotten to reply yesterday. > > I've installed these updates, but I still get this error: > mockbuild.exception.ConfigError: Could not find included config file: > /tmp/epel-9-x86_64.j_mo4dzgmockconfig/te