Comments

62 Comments
BZ#1805769 Upgrade path broken: F-31 -> F-32

I think the correct build is proj-6.3.1-3 in FEDORA-2020-2b538f8cb6

3.2.1 is in testing now and should be available soon.

This does not fix a 32-bit mock shell.

BZ#1804415 'mock -r fedora-rawhide-i386 shell' fails

This update should have included golang-github-mmarkdown-mmark. However, Bodhi is buggy and won't allow adding an existing build to an update when it's in another update, even if unpushed, so there's not much to be done about that now.

karma

As noted in the spec comments, the Obsoletes and Provides should be removed after Fedora 31. (Actually, I made a mistake, they should be there for 2 releases after the last possible existence of the old name, so they should be removed after Fedora 32.)

OK, I don't know how many R packages there are in EPEL8 as I don't build anything for it. If this seems to be working there, feel free to push.

karma

This works now.

Also note that autopush got disabled from my earlier karma.

BZ#1727281 R-3.6.1 is available
BZ#1744723 R-devel requires R-rpm-macros
karma

This works now, and also fixes a few packages that don't load because they were built while 3.6.0 was a build override.

Also note that autopush got disabled from my earlier karma.

BZ#1703495 R-3.6.0 is available
BZ#1727281 R-3.6.1 is available
BZ#1744723 R-devel requires R-rpm-macros
karma

Pulling in R-rpm-macros means that all subsequent builds will gain automatic Requires, but none of the packages have been rebuilt with the corresponding Provides, like they were in F31 with the Mass Rebuild.

if you want to backport this, feel free to do so, but that means you'll need to rebuild everything. I suggest not doing so, either removing R-rpm-macros from R-devel for <31, or we can disable automatic dependencies in R-rpm-macros on older releases.

karma

Pulling in R-rpm-macros means that all subsequent builds will gain automatic Requires, but none of the packages have been rebuilt with the corresponding Provides, like they were in F31 with the Mass Rebuild.

if you want to backport this, feel free to do so, but that means you'll need to rebuild everything. I suggest not doing so, either removing R-rpm-macros from R-devel for <31, or we can disable automatic dependencies in R-rpm-macros on older releases.

User Icon qulogic commented & provided feedback on R-3.6.1-2.el7 8 months ago
karma

Pulling in R-rpm-macros means that all subsequent builds will gain automatic Requires, but none of the packages have been rebuilt with the corresponding Provides, like they were in F31 with the Mass Rebuild.

if you want to backport this, feel free to do so, but that means you'll need to rebuild everything. I suggest not doing so, either removing R-rpm-macros from R-devel for <31, or we can disable automatic dependencies in R-rpm-macros on older releases.

karma

Pulling in R-rpm-macros means that all subsequent builds will gain automatic Requires, but none of the packages have been rebuilt with the corresponding Provides, like they were in F31 with the Mass Rebuild.

if you want to backport this, feel free to do so, but that means you'll need to rebuild everything. I suggest not doing so, either removing R-rpm-macros from R-devel for <31, or we can disable automatic dependencies in R-rpm-macros on older releases.