Bug 1216355

Summary:	Packman Discord package upgrade lockout defeat inoperative.
Product:	[openSUSE] openSUSE Tumbleweed	Reporter:	Rick Kunath <rskunath>
Component:	Other	Assignee:	E-mail List <screening-team-bugs>
Status:	RESOLVED FIXED	QA Contact:	E-mail List <qa-bugs>
Severity:	Normal
Priority:	P5 - None	CC:	Andreas.Stieger
Version:	Current
Target Milestone:	---
Hardware:	x86-64
OS:	openSUSE Tumbleweed
Whiteboard:
Found By:	---	Services Priority:
Business Priority:		Blocker:	---
Marketing QA Status:	---	IT Deployment:	---

Description Rick Kunath 2023-10-17 20:20:12 UTC

There is a script in the Packman Discord srpm package (0.0.31-1699.98.pm.1) that is supposed to defeat the upgrade check that Discord does when they release a new version. This pops up a box to grab a deb or a tarball to update outside the Suse system. This script that is in the rpm spec file apparently has not worked for a while. I don't know if it can work, but it is in there and inoperative. The idea according to the script is to bypass the update check lockout and give the package maintainer time to update the Discord package without locking users out of Discord until that is done. This is a very good idea.

In the last few Discord update cycles the box pops up and at that point you can't start Discord until the new package is released by the package maintainer.

I did see a while ago a forum post about bumping the JSON file revision number by one version to get around this manually:
(/usr/lib64/discord/resources and edit the build_info.json file) 

This appears to work but it's a kludge and the script is a better and a more appropriate way to do this if doing it is still possible.

I'm just passing along the discovery and hoping defeating the lockout is still possible. I use Discord daily on the Suse Discord and users getting locked out is disconcerting.

Thanks in advance.

Comment 1 Andreas Stieger 2023-10-17 20:57:35 UTC

You should contact the packman project.

Comment 2 Rick Kunath 2023-10-17 21:24:05 UTC

(In reply to Andreas Stieger from comment #1)
> You should contact the packman project.

I'd be glad to.

I seem to be having trouble finding out how to contact Packman and file the bug?

Is there a link to them please?

Thanks in advance.

Comment 3 Rick Kunath 2023-10-17 22:18:52 UTC

There is a slightly older version in Main NON-OSS that has the same script in it and that doesn't work either. It would be my guess that Packman got the script from the MAIN package.

So, shouldn't this be sent on to the MAIN package maintainer then?

Reopened but close again if I am wrong, please.

Thanks again.

Comment 4 Rick Kunath 2023-10-18 00:24:31 UTC

Closed please.

The script seemed to be ineffective based on Discord testing anyway. But it should likely be removed from the package.

Comment 5 OBSbugzilla Bot 2023-10-20 07:55:05 UTC

This is an autogenerated message for OBS integration:
This bug (1216355) was mentioned in
https://build.opensuse.org/request/show/1119163 Factory / sg3_utils

Comment 9 Maintenance Automation 2023-12-20 20:30:11 UTC

SUSE-RU-2023:4937-1: An update that has three fixes can now be installed.

Category: recommended (moderate)
Bug References: 1215720, 1215772, 1216355
Sources used:
openSUSE Leap Micro 5.3 (src): sg3_utils-1.47+15.b6898b8-150400.3.11.1
openSUSE Leap Micro 5.4 (src): sg3_utils-1.47+15.b6898b8-150400.3.11.1
openSUSE Leap 15.4 (src): sg3_utils-1.47+15.b6898b8-150400.3.11.1
openSUSE Leap 15.5 (src): sg3_utils-1.47+15.b6898b8-150400.3.11.1
SUSE Linux Enterprise Micro for Rancher 5.3 (src): sg3_utils-1.47+15.b6898b8-150400.3.11.1
SUSE Linux Enterprise Micro 5.3 (src): sg3_utils-1.47+15.b6898b8-150400.3.11.1
SUSE Linux Enterprise Micro for Rancher 5.4 (src): sg3_utils-1.47+15.b6898b8-150400.3.11.1
SUSE Linux Enterprise Micro 5.4 (src): sg3_utils-1.47+15.b6898b8-150400.3.11.1
SUSE Linux Enterprise Micro 5.5 (src): sg3_utils-1.47+15.b6898b8-150400.3.11.1
Basesystem Module 15-SP4 (src): sg3_utils-1.47+15.b6898b8-150400.3.11.1
Basesystem Module 15-SP5 (src): sg3_utils-1.47+15.b6898b8-150400.3.11.1

NOTE: This line indicates an update has been released for the listed product(s). At times this might be only a partial fix. If you have questions please reach out to maintenance coordination.