Hi everyone,
Is here any chance to get sources for RHBA-2020:2659, RHBA-2020:2662 and RHBA-2020:2661 to be imported to git.centos.org? Are they planned to be skipped completely like it was for RHSA-2020:2250?
Is this new CentOS feature to skip importing sources, perhaps, there is any 'algorithm' behind this?
On 26/06/2020 12:50, plageat@tut.by wrote:
Hi everyone,
Is here any chance to get sources for RHBA-2020:2659, RHBA-2020:2662 and RHBA-2020:2661 to be imported to git.centos.org? Are they planned to be skipped completely like it was for RHSA-2020:2250?
Is this new CentOS feature to skip importing sources, perhaps, there is any 'algorithm' behind this?
CentOS does not import the sources into git.centos.org. Red Hat RCM do that as and when they release updates for RHEL.
Trevor
Same for RHBA-2020:2682
26.06.2020, 14:50, "plageat@tut.by" plageat@tut.by:
Hi everyone,
Is here any chance to get sources for RHBA-2020:2659, RHBA-2020:2662 and RHBA-2020:2661 to be imported to git.centos.org? Are they planned to be skipped completely like it was for RHSA-2020:2250?
Is this new CentOS feature to skip importing sources, perhaps, there is any 'algorithm' behind this? _______________________________________________ CentOS-devel mailing list CentOS-devel@centos.org https://lists.centos.org/mailman/listinfo/centos-devel
Hm, so, should I contact rh bugzilla for the issue?
26.06.2020, 15:01, "Trevor Hemsley" trevor.hemsley@ntlworld.com:
CentOS does not import the sources into git.centos.org. Red Hat RCM do that as and when they release updates for RHEL.
Trevor
Well, tried to do this via RH bugzilla with no success - they just closed the bug with something like "I do not know, I do not care" as NOTABUG
So, does anybody know anyone responsible for importing rhel sources to be asked?
26.06.2020, 16:40, "Manuel Wolfshant" wolfy@nobugconsulting.ro:
On 6/26/20 3:05 PM, plageat@tut.by wrote:
Hm, so, should I contact rh bugzilla for the issue?
yes
Can you provide a link to the bugzilla please?
On 6/26/20 5:01 AM, plageat@tut.by wrote:
Same for RHBA-2020:2682
26.06.2020, 14:50, "plageat@tut.by" plageat@tut.by:
Hi everyone,
Is here any chance to get sources for RHBA-2020:2659, RHBA-2020:2662 and RHBA-2020:2661 to be imported to git.centos.org? Are they planned to be skipped completely like it was for RHSA-2020:2250?
Is this new CentOS feature to skip importing sources, perhaps, there is any 'algorithm' behind this? _______________________________________________ CentOS-devel mailing list CentOS-devel@centos.org https://lists.centos.org/mailman/listinfo/centos-devel
CentOS-devel mailing list CentOS-devel@centos.org https://lists.centos.org/mailman/listinfo/centos-devel
Here is one to the RH bugzilla:
https://bugzilla.redhat.com/show_bug.cgi?id=1851394
27.06.2020, 07:37, "Jim Perrin" jperrin@centos.org:
Can you provide a link to the bugzilla please?
Actually, still on the way of undestanding how to report such cases. The practise shows, that RH bugzilla is not a solution atm, they do not even have applicable Product/Component field for such cases. Should we better contact directly someone from CentOSEngineeringTeamAtRedHat or fill centos bug?
Here is one to the RH bugzilla:
https://bugzilla.redhat.com/show_bug.cgi?id=1851394
27.06.2020, 07:37, "Jim Perrin" jperrin@centos.org:
Can you provide a link to the bugzilla please?
CentOS-devel mailing list CentOS-devel@centos.org https://lists.centos.org/mailman/listinfo/centos-devel
On Mon, Jun 29, 2020 at 2:39 AM plageat@tut.by wrote:
Actually, still on the way of undestanding how to report such cases. The practise shows, that RH bugzilla is not a solution atm, they do not even have applicable Product/Component field for such cases. Should we better contact directly someone from CentOSEngineeringTeamAtRedHat or fill centos bug?
Here is one to the RH bugzilla:
https://bugzilla.redhat.com/show_bug.cgi?id=1851394
27.06.2020, 07:37, "Jim Perrin" jperrin@centos.org:
Can you provide a link to the bugzilla please?
Looks like that particular package has just been released. I see the component "releng" which is probably most appropriate for reporting issues like this.
I also believe filing a CentOS bug would also help. CentOS devs should be able to take it from there.
Akemi