Thanks very much @zdohnal. https://bugzilla.redhat.com/show_bug.cgi?id=1763693 does not happen with this build now.

Not sure if this is related to this update, but spellcheck now seems weird. Filed this bug:

https://bugzilla.redhat.com/show_bug.cgi?id=1763693

It does seem to be a server side error. Using a different client (https://github.com/benapetr/stikkit) also gives the same behaviour. I'll get in touch with the server folks and see what can be done. It's got to be a weird edge case with parsing the spec I reckon.

Thanks, I'll look at it this evening.

@alciregi: that's because dnf blocks while waiting for input if it hasn't been used before and imported gpg keys etc. I guess I could do -y to work around it, but I'm a bit wary of using -y.

Let me take a look at it first---we need to have some idea of why this particular file fails.

@vascom, could you please e-mail me the file at ankursinha AT fp.o so I can run some tests?

Hrm, so:

$ fpaste -l rpmspec < python-nibabel.spec 
Uploading (6.6KiB)...
https://paste.centos.org/view/fbcfa1e9

Works fine.

$ cat python-nibabel.spec | fpaste -l rpmspec
Uploading (6.6KiB)...
https://paste.centos.org/view/3372fe3a

Also works.

$ fpaste python-nibabel.spec 
Uploading (6.6KiB)...
https://paste.centos.org/view/6771fd45

Also works.

Is your spec file correct?

Thanks---I'd filed a few bugs upstream and the fixes have landed in 2.0.0 now. I'm Just building and pushing that now. It should obsolete these beta updates.

This will need some investigation. Could you please file a bug? I'll send it upstream and see what they have to say too.

Thanks very much.

This update has been unpushed.

Sure, I've unpushed this one. Thanks very much!

Please let me know if I can do anything else to help with this.

This update has been unpushed.

Turns out I can't because I don't have commit access to those two packages.

Would you have proven packager privileges by any chance? Otherwise I can add you as a co-maintainer for these packages for you to push the updates---and then you can remove yourself from them later?

(Or we push the sip updates separately and I make sure they reach stable before these do---I'll disable autopush here)

DNF says it can't be installed because of dep errors:

Skipping packages with broken dependencies:                                                                                                                                                   
 packit                                                   noarch                          0.5.1-1.fc30                                         updates-testing                           15 k
 python3-packit                                           noarch                          0.5.1-1.fc30                                         updates-testing                          105 k

Fixes the firmware issue for me with kernel 5.2.9 as suggested:

(ins)[asinha@ankur-pc  ~]$ uname -a
Linux ankur-pc 5.2.9-200.fc30.x86_64 #1 SMP Fri Aug 16 21:37:45 UTC 2019 x86_64 x86_64 x86_64 GNU/Linux

(ins)[asinha@ankur-pc  ~]$ rpm -q \*firmware\*
package *firmware* is not installed
(ins)[asinha@ankur-pc  ~]$ rpm -qa \*firmware\*
iwl4965-firmware-228.61.2.24-101.fc30.noarch
iwl6050-firmware-41.28.5.1-101.fc30.noarch
iwl100-firmware-39.31.5.1-101.fc30.noarch
iwl3945-firmware-15.32.2.9-101.fc30.noarch
iwl5150-firmware-8.24.2.2-101.fc30.noarch
iwl6000g2b-firmware-18.168.6.1-101.fc30.noarch
iwl1000-firmware-39.31.5.1-101.fc30.noarch
libertas-usb8388-firmware-20190815-101.fc30.noarch
iwl135-firmware-18.168.6.1-101.fc30.noarch
iwl3160-firmware-25.30.13.0-101.fc30.noarch
iwl5000-firmware-8.83.5.1_1-101.fc30.noarch
atmel-firmware-1.3-20.fc30.noarch
iwl6000g2a-firmware-18.168.6.1-101.fc30.noarch
linux-firmware-whence-20190815-101.fc30.noarch
iwl7260-firmware-25.30.13.0-101.fc30.noarch
ipw2200-firmware-3.1-17.fc30.noarch
iwl105-firmware-18.168.6.1-101.fc30.noarch
iwl2030-firmware-18.168.6.1-101.fc30.noarch
ipw2100-firmware-1.3-24.fc30.noarch
iwl6000-firmware-9.221.4.1-101.fc30.noarch
zd1211-firmware-1.5-4.fc30.noarch
linux-firmware-20190815-101.fc30.noarch
iwl2000-firmware-18.168.6.1-101.fc30.noarch

Works well! Thanks!

Works OK here---no weirdness noted