Hi,
It appears Thunderbird 78.6.0 was never released for CentOS 8.3. Could someone please check on it? Perhaps the Files->c8 section warning is a clue:
Warning: This package was configured for automatic debranding, but the changes failed to apply.
As a related topic, I have experience building RPM's/mock, superficial git user, but I'm still kinda lost how I might be able to get a .src.rpm out of the current state of
https://git.centos.org/rpms/thunderbird/tree/404b3fff4f6bcc2c23e085b4ad2c1eb...
Any brief / terse tips would be appreciated.
I did see Johnny's msg https://lists.centos.org/pipermail/centos-devel/2020-December/075681.html
but it doesn't seem to apply to this situation as there is no koji build info.
Thanks!
Chris
Hi,
It appears Thunderbird 78.6.0 was never released for CentOS 8.3. Could someone please check on it? Perhaps the Files->c8 section warning is a clue:
Warning: This package was configured for automatic debranding, but the changes failed to apply.
As a related topic, I have experience building RPM's/mock, superficial git user, but I'm still kinda lost how I might be able to get a .src.rpm out of the current state of
https://git.centos.org/rpms/thunderbird/tree/404b3fff4f6bcc2c23e085b4ad2c1eb...
Did you try to simply download the source files from SOURCES / and SPECS/ and then build from there, like 'rpm -bs thunderbird.spec' to get a .src.rpm file? This should always work, no?
Regards, Simon
On 1/15/21 2:26 AM, Simon Matter wrote:
Hi,
It appears Thunderbird 78.6.0 was never released for CentOS 8.3. Could someone please check on it? Perhaps the Files->c8 section warning is a clue:
Warning: This package was configured for automatic debranding, but the changes failed to apply.
As a related topic, I have experience building RPM's/mock, superficial git user, but I'm still kinda lost how I might be able to get a .src.rpm out of the current state of
https://git.centos.org/rpms/thunderbird/tree/404b3fff4f6bcc2c23e085b4ad2c1eb...
Did you try to simply download the source files from SOURCES / and SPECS/ and then build from there, like 'rpm -bs thunderbird.spec' to get a .src.rpm file? This should always work, no?
Regards, Simon
Hi Simon,
Thanks for your suggestion, but the SOURCES and SPECS did not exist a few days ago, sorry for not being clear about that. I emailed Johnny Hughes off-list several days ago but received no reply, but maybe he found it and started working on it. I think fixing the debranding issue got things rolling.
Thanks to Fabian also for his detailed reply!
On 15/01/2021 04:35, Chris Schanzle via CentOS-devel wrote:
Hi,
It appears Thunderbird 78.6.0 was never released for CentOS 8.3. Could someone please check on it? Perhaps the Files->c8 section warning is a clue:
Warning: This package was configured for automatic debranding, but the changes failed to apply.
If you look at the git history, you'll see in the c8 (https://git.centos.org/rpms/thunderbird/commits/c8) and c8-plus (https://git.centos.org/rpms/thunderbird/commits/c8-plus) that there were newer commits, also to release the 1:1 matching thunderbird (for c8) and a different one for c8-plus (that doesn't disable openpgp).
The buildsystem interface is public, so you can see that both were built : https://koji.mbox.centos.org/koji/packageinfo?packageID=2346
So at stage it needs a compose+sign+push , so I guess it's on Johnny's list for today :)
As a related topic, I have experience building RPM's/mock, superficial git user, but I'm still kinda lost how I might be able to get a .src.rpm out of the current state of
https://git.centos.org/rpms/thunderbird/tree/404b3fff4f6bcc2c23e085b4ad2c1eb...
Any brief / terse tips would be appreciated.
The following page explains how to get automatically the sources and also how to rebuild easily a .src.rpm from any branch : https://wiki.centos.org/Sources#Usage
Kind Regards,
Am 15.01.21 um 09:07 schrieb Fabian Arrotin:
On 15/01/2021 04:35, Chris Schanzle via CentOS-devel wrote:
Hi,
It appears Thunderbird 78.6.0 was never released for CentOS 8.3. Could someone please check on it? Perhaps the Files->c8 section warning is a clue:
Warning: This package was configured for automatic debranding, but the changes failed to apply.
If you look at the git history, you'll see in the c8 (https://git.centos.org/rpms/thunderbird/commits/c8) and c8-plus (https://git.centos.org/rpms/thunderbird/commits/c8-plus) that there were newer commits, also to release the 1:1 matching thunderbird (for c8) and a different one for c8-plus (that doesn't disable openpgp).
The buildsystem interface is public, so you can see that both were built : https://koji.mbox.centos.org/koji/packageinfo?packageID=2346
So at stage it needs a compose+sign+push , so I guess it's on Johnny's list for today :)
the packages were build in koji some days ago. I wonder how big the average time window between koji builds and being on a mirror in a repo looks like?
-- Thanks Leon
-
Chris Schanzle -
Fabian Arrotin -
Leon Fauster -
Simon Matter