Re: Fedora 37 mass rebuild started

2022-07-26 Thread Michael J Gruber
> On 26. 07. 22 17:15, Michael J Gruber wrote:
> 
> I don't think so:
> 
> https://src.fedoraproject.org/rpms/redhat-rpm-config/c/1926c37598951ae307...
> 
> https://koji.fedoraproject.org/koji/buildinfo?buildID=1968550
> 
> https://bodhi.fedoraproject.org/updates/FEDORA-2022-925c18db47

Indeed. It was introduced in 219 for F36 and rawhide and in 201 for F35. That 
is not how I do my versions and branches, but to each their own.
___
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 on the list, report it: 
https://pagure.io/fedora-infrastructure


Re: Fedora 37 mass rebuild started

2022-07-26 Thread Miro Hrončok

On 26. 07. 22 17:15, Michael J Gruber wrote:

The %java_arches macro mentioned in the change proposal is available on F36 and 
up only


I don't think so:

https://src.fedoraproject.org/rpms/redhat-rpm-config/c/1926c37598951ae30749eb212b2412973a0300e5?branch=f35

https://koji.fedoraproject.org/koji/buildinfo?buildID=1968550

https://bodhi.fedoraproject.org/updates/FEDORA-2022-925c18db47

--
Miro Hrončok
--
Phone: +420777974800
IRC: mhroncok
___
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 on the list, report it: 
https://pagure.io/fedora-infrastructure


Re: Fedora 37 mass rebuild started

2022-07-26 Thread Michael J Gruber
> Next failure is portmidi due to "Drop_i686_JDKs"
> https://fedoraproject.org/wiki/Changes/Drop_i686_JDKs
> 
> I don't know how I missed that change proposal. I cannot even make sense of 
> the
> English in those template mails (never got any myself). This is going to be a 
> lot of fun
> ... java-17-openjdk-devel got installed but JNI is missing???

For the record:
portmidi is rebuilt in rawhide now, with portmidi-tools dropping the pmdefaults 
app if java is not available on that arch.

The %java_arches macro mentioned in the change proposal is available on F36 and 
up only, btw, so the suggestions in that proposal need to be treated with some 
caveat, or as they say: caveat packagor ;-)
___
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 on the list, report it: 
https://pagure.io/fedora-infrastructure


Re: Fedora 37 mass rebuild started

2022-07-23 Thread Kevin Fenzi
As a quick and dirty thing I took the f37-needs-rebuild list and the
f37-failed to build list and found things that were only on the
needs-rebuild list. 

I then filtered out the ones we don't try and mass rebuild (shim,
kernel, grub2, etc) and the silly ones we have like Fedora-Live-Xfce
(placeholder for the live image) and got a list with 191 entries. 

So these didn't fail after making a src.rpm, but might have failed then.
I also see a lot of these that are epel specific, but arent retired on
rawhide. There also may have been a very few that didn't get tried
because the fedora-messaging cluster was down. ;( 

aardvark-dns
aboot
andy-super-great-park
anthy-unicode-epel
askbot-plugin-authfas
autoconf268
aws-c-cal
bash-completion-extras
bird2
boost1.78
caribou0
Charliecloud
clang11.0
clap_generate_fig
community-mysql
compat-tidy
cube
cyrus-imapd
debootstrap
dnscrypt-proxy2
docker-swarm
double-conversion-epel
erlang-riak_ensemble
fizz
gcc-epel
gdl
generic-release
ghc8.2
ghc8.8
glibc32
gnome-commander
gnuplot44
golang-cloud-google
golang-github-apparentlymart-textseg
golang-github-bits-and-blooms-bloom
golang-github-btcsuite-btcd-btcec
golang-github-cloudflare-golz4
golang-github-datadog-sketches
golang-github-exchange-interface
golang-github-github-ssdb-gossdb
golang-github-go-stack-stack
golang-github-ipfs-bitswap
golang-github-ipfs-block-format
golang-github-ipfs-blockservice
golang-github-ipfs-blockstore
golang-github-ipfs-blocksutil
golang-github-ipfs-cmds
golang-github-ipfs-datastore
golang-github-ipfs-delay
golang-github-ipfs-ds-flatfs
golang-github-ipfs-ds-help
golang-github-ipfs-http-client
golang-github-ipfs-ipld-format
golang-github-ipfs-log-2
golang-github-ipfs-merkledag
golang-github-ipfs-peertaskqueue
golang-github-ipfs-util
golang-github-jbenet-cienv
golang-github-jbenet-goprocess
golang-github-jcmturner-aescts-2
golang-github-jcmturner-dnsutils-2
golang-github-jcmturner-goidentity-6
golang-github-jcmturner-gokrb5-8
golang-github-jcmturner-rpc-2
golang-github-logr-stdr
golang-github-stomp
golang-github-vinyldns-vinyldns
golang-gopkg-playground-validator-10
golang-grpc-go4
golang-jaytaylor.com-html2text
icecat
ignition-fuel-tools
inih-epel
iptables-epel
isis
jama
java-1.8.0-openjdk-aarch32
jd
kclock
keepassx2
kernel-headers
keysmith
libappindicator-sharp
libburn1
libgit2_0.26
LibRaw-epel
libxslxwriter
lightdm-gtk
linux-firmware
lorax-templates-rhel
lua5.1-lpeg
mesa-demos-epel
mesos
mingw-libidl
mingw-windows-default-manifest
mingw-wine-gecko
mingw-win-iconv
mingw-winpthreads
mingw-winstorecompat
mingw-wpcap
mingw-wxWidgets
minizip1.2
module-build-macros
monafont
netcdf-fortran
nodejs-async-lock
nvidia-texture-tools
openh264
openmolar
osbs-client
osmo
perl-Math-Calc-Units
perl-Math-Cartesian-Product
perl-Math-ConvexHull
perl-Math-ConvexHull-MonotoneChain
pesign-test-app
php53-simplepie
proj
proxygen
pycairo-epel
python26-msgpack
python38-coverage
python38-hvac
python38-hypothesis-epel
python38-netaddr
python38-ntlm-auth-epel
python38-pynetbox
python38-pytest-helpers-namespace
python38-requests_ntlm-epel
python38-setuptools_scm_git_archive
python3-cryptography-vectors
python3-doctutils
python3-greenlet
python3-gssapi
python3-kitchen
python3-prctl
python3-pyasn1
python3-zope-event
python-antlr4-python3-runtime
python-asana
python-charon
python-dataclasses
python-django-oauth-toolkit
python-gear
python-genshi06
python-hbmqtt
python-hudman
python-k2hr3-osnl
python-neutronclient
python-osa
python-proton-client
python-pysam
python-satyr
python-tqdm
python-webob1.4
python-yubikey-manager
qtscrob
quazip-qt5
realtime-setup
redhat-rpm-config
retrace-client
R-TH-data
rust-bat
rust-gag
rust-git-delta
rust-gitui
rust-platform-info
rust-pwd
rust-syntect4
rust-sysinfo0.19
rust-uucore
rust-wasi-cap-std-sync
rust-wasi-tokio
rust-wasmtime-wasi
sahara-image-elements
serafettin-cartoon-fonts
solo3
status-report
systemd-boot
termbox
tinygo
tnt
trace-gui
twincam
vera++
vttest
wasmedge
webkit2gtk3
xfce4-soundmenu-plugin
xsetpointer
zeek

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 on the list, report it: 
https://pagure.io/fedora-infrastructure


Re: Fedora 37 mass rebuild started

2022-07-23 Thread Jerry James
On Sat, Jul 23, 2022 at 4:03 PM Kevin Fenzi  wrote:
> Yeah, fixed. I retagged all the things in the signing pending tag.
>
> However, this might cause some really old updates to land...
> so keep an eye out for that.

Will do, thank you!

> Yeah, this the old 'if koji can't rebuild the src.rpm, it never shows up
> as a 'build'' thing. ;(
>
> https://koji.fedoraproject.org/koji/taskinfo?taskID=89838907
>
> It looks like it couldn't download src. ;(
>
> DEBUG util.py:443:  curl: (35) OpenSSL SSL_connect: Connection reset by peer 
> in connection to src.fedoraproject.org:443
> DEBUG util.py:596:  Child return code was: 35
>
> So, just do a build like normal in rawhide and it should be good.
>
> There's a releng ticket on this issue...
>
> https://pagure.io/releng/issue/8601
>
> Looks like there was some support added to koji to query these, but the
> mass rebuild failures script never got updated to try and use it? ;(

Ah, I see.  Thanks for the information.  I will kick off that build shortly.
-- 
Jerry James
http://www.jamezone.org/
___
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 on the list, report it: 
https://pagure.io/fedora-infrastructure


Re: Fedora 37 mass rebuild started

2022-07-23 Thread Kevin Fenzi
On Sat, Jul 23, 2022 at 02:49:53PM -0600, Jerry James wrote:
> On Sat, Jul 23, 2022 at 2:35 PM Kevin Fenzi  wrote:
> > The packages were signed and the sidetag is through to f37.
> >
> > Also, the signing queue is all caught up.
> 
> Can you take a look at gap-4.11.1-5.fc37?  It's been in
> f37-signing-pending for over 2 days now.

Yeah, fixed. I retagged all the things in the signing pending tag. 

However, this might cause some really old updates to land...
so keep an eye out for that. 

> > The only things left for the mass rebuild are a few of the larger
> > packages (ceph, webkit, etc). Then we should be able to merge the
> > f37-rebuild tag in and be done.
> 
> No build seems to have been submitted for ocaml-ppx-inline-test.  I
> just mention this in case there are other packages that were skipped.

Yeah, this the old 'if koji can't rebuild the src.rpm, it never shows up
as a 'build'' thing. ;( 

https://koji.fedoraproject.org/koji/taskinfo?taskID=89838907

It looks like it couldn't download src. ;( 

DEBUG util.py:443:  curl: (35) OpenSSL SSL_connect: Connection reset by peer in 
connection to src.fedoraproject.org:443
DEBUG util.py:596:  Child return code was: 35

So, just do a build like normal in rawhide and it should be good. 

There's a releng ticket on this issue...

https://pagure.io/releng/issue/8601

Looks like there was some support added to koji to query these, but the
mass rebuild failures script never got updated to try and use it? ;( 

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 on the list, report it: 
https://pagure.io/fedora-infrastructure


Re: Fedora 37 mass rebuild started

2022-07-23 Thread Kevin Fenzi
On Sat, Jul 23, 2022 at 10:43:38PM +0200, Fabio Valentini wrote:
> 
> Can confirm, looks all good now, thanks!
> 
> BTW, I'd like to know whatever magic you did to fedora notifications.
> Because it apparently kept chugging on right through the mass rebuild,
> and is now caught up again. :)

Yeah, I am pretty amazed by that. ;) 

Currently it's pretty heavily patched... we still want to move to the
python3 one. Hopefully next week. 

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 on the list, report it: 
https://pagure.io/fedora-infrastructure


Re: Fedora 37 mass rebuild started

2022-07-23 Thread Jerry James
On Sat, Jul 23, 2022 at 2:35 PM Kevin Fenzi  wrote:
> The packages were signed and the sidetag is through to f37.
>
> Also, the signing queue is all caught up.

Can you take a look at gap-4.11.1-5.fc37?  It's been in
f37-signing-pending for over 2 days now.

> The only things left for the mass rebuild are a few of the larger
> packages (ceph, webkit, etc). Then we should be able to merge the
> f37-rebuild tag in and be done.

No build seems to have been submitted for ocaml-ppx-inline-test.  I
just mention this in case there are other packages that were skipped.
--
Jerry James
http://www.jamezone.org/
___
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 on the list, report it: 
https://pagure.io/fedora-infrastructure


Re: Fedora 37 mass rebuild started

2022-07-23 Thread Fabio Valentini
On Sat, Jul 23, 2022 at 10:35 PM Kevin Fenzi  wrote:
>
> On Sat, Jul 23, 2022 at 10:09:50AM -0700, Kevin Fenzi wrote:
> > On Sat, Jul 23, 2022 at 10:37:39AM +0200, Fabio Valentini wrote:
> ...snip...
> >
> > So, as long as that sidetag update goes out all should be fine.
>
> The packages were signed and the sidetag is through to f37.
>
> Also, the signing queue is all caught up.
>
> The only things left for the mass rebuild are a few of the larger
> packages (ceph, webkit, etc). Then we should be able to merge the
> f37-rebuild tag in and be done.

Can confirm, looks all good now, thanks!

BTW, I'd like to know whatever magic you did to fedora notifications.
Because it apparently kept chugging on right through the mass rebuild,
and is now caught up again. :)

Fabio
___
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 on the list, report it: 
https://pagure.io/fedora-infrastructure


Re: Fedora 37 mass rebuild started

2022-07-23 Thread Kevin Fenzi
On Sat, Jul 23, 2022 at 10:09:50AM -0700, Kevin Fenzi wrote:
> On Sat, Jul 23, 2022 at 10:37:39AM +0200, Fabio Valentini wrote:
...snip...
> 
> So, as long as that sidetag update goes out all should be fine. 

The packages were signed and the sidetag is through to f37. 

Also, the signing queue is all caught up. 

The only things left for the mass rebuild are a few of the larger
packages (ceph, webkit, etc). Then we should be able to merge the
f37-rebuild tag in and be done. 

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 on the list, report it: 
https://pagure.io/fedora-infrastructure


Re: Fedora 37 mass rebuild started

2022-07-23 Thread Kevin Fenzi
On Sat, Jul 23, 2022 at 10:37:39AM +0200, Fabio Valentini wrote:
> On Fri, Jul 22, 2022 at 10:30 PM Kevin Fenzi  wrote:
> >
> > We have had several issues in the last few days sadly.
> > I think your build ran into systemd-oomd running on some builders after
> > I had disabled it and thought I stopped it, but didn't. ;(
> >
> > Anyhow, the thing to do here if it builds is just go ahead abd build it
> > into rawhide like normal.
> 
> Looks like the package signing queue is getting really really long?

It has, but only just this morning. ;( 

https://admin.fedoraproject.org/collectd/bin/graph.cgi?hostname=rabbitmq_slash_pubsub;plugin=queues;plugin_instance=robosignatory;type=messages;begin=-86400

> I built an update for several packages and submitted it to rawhide a
> day before the mass rebuild script reached packages starting with "r".
> But it appears that the signing queue is getting so long that the
> update still hasn't been pushed to stable (almost two days since I
> submitted it to bodhi, still stuck in "pending" because of unsigned
> builds):
> https://bodhi.fedoraproject.org/updates/FEDORA-2022-a7ad4a64b5

I fear what might have happened is that you were doing this at a time
when we were having problems with our rabbitmq cluster, so the messages
might have been lost. ;( 

I retagged them into the signing pending tag, but of course signing is
backed up, so will take a while to get to them. Probibly later today.
 
> And now the mass rebuild script has pushed commits to all these
> packages and submitted them individually, which of course, failed.
> So should I just resubmit those failed builds once my bodhi update is
> finally signed and pushed to stable?

Should be no need if this update goes out. 
The script that will merge the f37-rebuild tag looks to see if there is
a build thats been tagged into f37 thats newer than the proposed one. If
there is, it just doesn't tag it, and in this case that build doesn't
exist even. ;) 

So, as long as that sidetag update goes out all should be fine. 

If it's still stuck after the signing queue is caught up, let me know
and I can look at it more to see why it's not moving. 

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 on the list, report it: 
https://pagure.io/fedora-infrastructure


Re: Fedora 37 mass rebuild started

2022-07-23 Thread Alexander Ploumistos
Thank you Vitaly.
___
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 on the list, report it: 
https://pagure.io/fedora-infrastructure


Re: Fedora 37 mass rebuild started

2022-07-23 Thread Vitaly Zaitsev via devel

On 23/07/2022 14:46, Alexander Ploumistos wrote:

First, do I need to wait for the FTBFS bugs to be filed before I fix
the packages or can I submit updated builds to the f37-rebuild side
tag myself?


You can build directly to Rawhide without waiting. Mass rebuild will 
automatically pick build with higher NVR.


--
Sincerely,
  Vitaly Zaitsev (vit...@easycoding.org)
___
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 on the list, report it: 
https://pagure.io/fedora-infrastructure


Re: Fedora 37 mass rebuild started

2022-07-23 Thread Alexander Ploumistos
Hello,

Two of my packages failed to build due to a trailing "." after the
%cmake macro in the spec file. I have a couple of questions:

First, do I need to wait for the FTBFS bugs to be filed before I fix
the packages or can I submit updated builds to the f37-rebuild side
tag myself?

Second, I hadn't touched these spec files because I was waiting to see
what the resolution of RHBZ#2079833 would be. If I understand
correctly, any packages that required the declaration of a source path
after the %cmake macro in order to build were exploiting an unintended
behavior and the paths should be set in the corresponding cmake files,
regardless of the macro's behavior. Have I got things right?
___
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 on the list, report it: 
https://pagure.io/fedora-infrastructure


Re: Fedora 37 mass rebuild started

2022-07-23 Thread Fabio Valentini
On Fri, Jul 22, 2022 at 10:30 PM Kevin Fenzi  wrote:
>
> We have had several issues in the last few days sadly.
> I think your build ran into systemd-oomd running on some builders after
> I had disabled it and thought I stopped it, but didn't. ;(
>
> Anyhow, the thing to do here if it builds is just go ahead abd build it
> into rawhide like normal.

Looks like the package signing queue is getting really really long?
I built an update for several packages and submitted it to rawhide a
day before the mass rebuild script reached packages starting with "r".
But it appears that the signing queue is getting so long that the
update still hasn't been pushed to stable (almost two days since I
submitted it to bodhi, still stuck in "pending" because of unsigned
builds):
https://bodhi.fedoraproject.org/updates/FEDORA-2022-a7ad4a64b5

And now the mass rebuild script has pushed commits to all these
packages and submitted them individually, which of course, failed.
So should I just resubmit those failed builds once my bodhi update is
finally signed and pushed to stable?

Fabio
___
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 on the list, report it: 
https://pagure.io/fedora-infrastructure


Re: Fedora 37 mass rebuild started

2022-07-22 Thread Kevin Fenzi
On Fri, Jul 22, 2022 at 02:24:21PM -0500, Maxwell G via devel wrote:
> On 22/07/22 09:08AM, Michael J Gruber wrote:
> > notmuch failed to build from source because of a strange test suite failure 
> > on ppc64le:
> > 
> > https://koji.fedoraproject.org/koji/taskinfo?taskID=89837091
> > 
> > The only failing test is a pytest run on the bindings
> > 
> > ```
> > T391-python-cffi: Testing python bindings (pytest)
> > FATAL: /builddir/build/BUILD/notmuch-0.36/test/T391-python-cffi.sh: 
> > interrupted by signal 15
> > ```
> > 
> > whereas other tests of those bindings work. What makes it even more strange 
> > is that for a scratch build all tests work on all architectures:
> > 
> > https://koji.fedoraproject.org/koji/taskinfo?taskID=89853627
> > 
> > Is there possibly a timing issue where tests on ppc64le happen to take "too 
> > long" and pytest gets killed?
> 
> It sounds like this might've been a transient issue, likely related to
> something on the builder, as it also worked fine when I scratch built
> it. The releng folks can probably tell you how to handle this and if you
> should rebuild it, just wait, or whatever. As Kevin said:
> 
> > You can contact releng in #fedora-releng channel on Libera.Chat, the
> > #releng:fedoraproject.org room on Matrix, or by dropping an email to
> > our list[2] or filing an issue in pagure[3].

Yeah. ;) 

We have had several issues in the last few days sadly. 
I think your build ran into systemd-oomd running on some builders after
I had disabled it and thought I stopped it, but didn't. ;( 

Anyhow, the thing to do here if it builds is just go ahead abd build it
into rawhide like normal. 

Hope that helps.

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 on the list, report it: 
https://pagure.io/fedora-infrastructure


Re: Fedora 37 mass rebuild started

2022-07-22 Thread Maxwell G via devel
On 22/07/22 09:08AM, Michael J Gruber wrote:
> notmuch failed to build from source because of a strange test suite failure 
> on ppc64le:
> 
> https://koji.fedoraproject.org/koji/taskinfo?taskID=89837091
> 
> The only failing test is a pytest run on the bindings
> 
> ```
> T391-python-cffi: Testing python bindings (pytest)
> FATAL: /builddir/build/BUILD/notmuch-0.36/test/T391-python-cffi.sh: 
> interrupted by signal 15
> ```
> 
> whereas other tests of those bindings work. What makes it even more strange 
> is that for a scratch build all tests work on all architectures:
> 
> https://koji.fedoraproject.org/koji/taskinfo?taskID=89853627
> 
> Is there possibly a timing issue where tests on ppc64le happen to take "too 
> long" and pytest gets killed?

It sounds like this might've been a transient issue, likely related to
something on the builder, as it also worked fine when I scratch built
it. The releng folks can probably tell you how to handle this and if you
should rebuild it, just wait, or whatever. As Kevin said:

> You can contact releng in #fedora-releng channel on Libera.Chat, the
> #releng:fedoraproject.org room on Matrix, or by dropping an email to
> our list[2] or filing an issue in pagure[3].

-- 
Thanks,

Maxwell G (@gotmax23)
Pronouns: He/Him/His


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 on the list, report it: 
https://pagure.io/fedora-infrastructure


Re: Fedora 37 mass rebuild started

2022-07-22 Thread Michael J Gruber
Next failure is portmidi due to "Drop_i686_JDKs" 
https://fedoraproject.org/wiki/Changes/Drop_i686_JDKs

I don't know how I missed that change proposal. I cannot even make sense of the 
English in those template mails (never got any myself). This is going to be a 
lot of fun ... java-17-openjdk-devel got installed but JNI is missing???
___
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 on the list, report it: 
https://pagure.io/fedora-infrastructure


Re: Fedora 37 mass rebuild started

2022-07-22 Thread Michael J Gruber
notmuch failed to build from source because of a strange test suite failure on 
ppc64le:

https://koji.fedoraproject.org/koji/taskinfo?taskID=89837091

The only failing test is a pytest run on the bindings

```
T391-python-cffi: Testing python bindings (pytest)
FATAL: /builddir/build/BUILD/notmuch-0.36/test/T391-python-cffi.sh: interrupted 
by signal 15
```

whereas other tests of those bindings work. What makes it even more strange is 
that for a scratch build all tests work on all architectures:

https://koji.fedoraproject.org/koji/taskinfo?taskID=89853627

Is there possibly a timing issue where tests on ppc64le happen to take "too 
long" and pytest gets killed?
___
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 on the list, report it: 
https://pagure.io/fedora-infrastructure


Re: Fedora 37 mass rebuild started

2022-07-21 Thread Mamoru TASAKA

Richard Shaw wrote on 2022/07/21 10:52:

Looking at brasero I can build "fine" doing a fedpkg mockbuild but adding
"--enablerepo=local" replicates the failure seen in koji[1].

I tried comparing the root logs between the two to see what's different but
I don't find the results particularly helpful:

lua-libs-5.4.4-3.fc37.x86_64 vs lua-libs-5.4.4-2.fc37.x86_64
setup-2.14.1-1.fc37.noarch vs setup-2.13.10-1.fc37.noarch
python-srpm-macros-3.11-3.fc37.noarch vs
python-srpm-macros-3.11-1.fc37.noarch

The error messages themselves seem like something that should have been
caught some time ago (not just newer gcc error checking).

Any ideas?

Thanks,
Richard
[1] https://kojipkgs.fedoraproject.org//work/tasks/7772/89767772/build.log




Would you check what "nautilus" is used when build of brasero gets fine?
koji says "nautilus" goes 42.2 -> 43~alpha, with switching gtk3 -> gtk4.

And brasero seems to be compiling with gtk3, but when compiling 
nautilus-burn-extension.c
in brasero, it tries to include gtk4 header, while successful build
(on eln: https://koji.fedoraproject.org/koji/buildinfo?buildID=1992598)
tries to include gtk3 header when compiling nautilus-burn-extension.c .

Regards,
Mamoru
___
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 on the list, report it: 
https://pagure.io/fedora-infrastructure


Re: Fedora 37 mass rebuild started

2022-07-21 Thread Florian Weimer
* Bob Mauchin:

>  Seems to be related to this post on the ML:
>
>  Long-running side tag for porting Fedora to C99 (no implicit decls) 

> https://lists.fedoraproject.org/archives/list/devel@lists.fedoraproject.org/message/LRPFW3IJTM7BWKL6RDSB3VYGAVDDUFR3/

This can't be it, it was never established.

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 on the list, report it: 
https://pagure.io/fedora-infrastructure


Fedora 37 mass rebuild started

2022-07-20 Thread Kevin Fenzi
Hi all,

Per the Fedora f37 schedule[1] we have started a mass rebuild
on 2022-07-20 for Fedora f37. We are running this mass rebuild
for the changes listed in:

https://pagure.io/releng/issues?status=Open=mass+rebuild

This mass rebuild will be done in a side tag (f37-rebuild) and merged
when completed.

Failures can be seen
https://kojipkgs.fedoraproject.org/mass-rebuild/f37-failures.html


Things still needing rebuilding
https://kojipkgs.fedoraproject.org/mass-rebuild/f37-need-rebuild.html


FTBFS (Fails To Build From Source) bugs will be filed shortly after
the mass rebuild is complete.

Please be sure to let releng know if you see any bugs in the
reporting. You can contact releng in #fedora-releng channel on Libera.Chat,
the #releng:fedoraproject.org room on Matrix, or by dropping an email
to our list[2] or filing an issue in pagure[3].

This email template is also in https://pagure.io/releng if you wish to
propose improvements or changes to it.

Regards,

Fedora Release Engineering

[1] https://fedorapeople.org/groups/schedule/f-37/f-37-key-tasks.html
[2] https://lists.fedoraproject.org/admin/lists/rel-eng.lists.fedoraproject.org/
[3] https://pagure.io/releng/


signature.asc
Description: PGP signature
___
devel-announce mailing list -- devel-annou...@lists.fedoraproject.org
To unsubscribe send an email to devel-announce-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-annou...@lists.fedoraproject.org
Do not reply to spam on the list, report it: 
https://pagure.io/fedora-infrastructure
___
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 on the list, report it: 
https://pagure.io/fedora-infrastructure


Fedora 37 mass rebuild started

2022-07-20 Thread Kevin Fenzi
Hi all,

Per the Fedora f37 schedule[1] we have started a mass rebuild
on 2022-07-20 for Fedora f37. We are running this mass rebuild
for the changes listed in:

https://pagure.io/releng/issues?status=Open=mass+rebuild

This mass rebuild will be done in a side tag (f37-rebuild) and merged
when completed.

Failures can be seen
https://kojipkgs.fedoraproject.org/mass-rebuild/f37-failures.html


Things still needing rebuilding
https://kojipkgs.fedoraproject.org/mass-rebuild/f37-need-rebuild.html


FTBFS (Fails To Build From Source) bugs will be filed shortly after
the mass rebuild is complete.

Please be sure to let releng know if you see any bugs in the
reporting. You can contact releng in #fedora-releng channel on Libera.Chat,
the #releng:fedoraproject.org room on Matrix, or by dropping an email
to our list[2] or filing an issue in pagure[3].

This email template is also in https://pagure.io/releng if you wish to
propose improvements or changes to it.

Regards,

Fedora Release Engineering

[1] https://fedorapeople.org/groups/schedule/f-37/f-37-key-tasks.html
[2] https://lists.fedoraproject.org/admin/lists/rel-eng.lists.fedoraproject.org/
[3] https://pagure.io/releng/


signature.asc
Description: PGP signature
___
devel-announce mailing list -- devel-announce@lists.fedoraproject.org
To unsubscribe send an email to devel-announce-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-announce@lists.fedoraproject.org
Do not reply to spam on the list, report it: 
https://pagure.io/fedora-infrastructure