Bug 2192963

Summary:	pkgconf-1.9.5 is available
Product:	[Fedora] Fedora	Reporter:	Upstream Release Monitoring <upstream-release-monitoring>
Component:	pkgconf	Assignee:	Neal Gompa <ngompa13>
Status:	POST ---	QA Contact:	Fedora Extras Quality Assurance <extras-qa>
Severity:	medium	Docs Contact:
Priority:	unspecified
Version:	rawhide	CC:	igor.raits, ngompa13, petersen
Target Milestone:	---	Keywords:	FutureFeature, Triaged
Target Release:	---	Flags:	petersen: needinfo? (ngompa13)
Hardware:	Unspecified
OS:	Unspecified
Whiteboard:
Fixed In Version:		Doc Type:	If docs needed, set a value
Doc Text:		Story Points:	---
Clone Of:		Environment:
Last Closed:		Type:	---
Regression:	---	Mount Type:	---
Documentation:	---	CRM:
Verified Versions:		Category:	---
oVirt Team:	---	RHEL 7.3 requirements from Atomic Host:
Cloudforms Team:	---	Target Upstream Version:
Embargoed:

Description Upstream Release Monitoring 2023-05-03 17:33:24 UTC

Releases retrieved: 1.9.5
Upstream release that is considered latest: 1.9.5
Current version/release in rawhide: 1.9.4-1.fc39
URL: http://pkgconf.org/

Please consult the package updates policy before you issue an update to a stable branch: https://docs.fedoraproject.org/en-US/fesco/Updates_Policy/


More information about the service that created this bug can be found at: https://docs.fedoraproject.org/en-US/package-maintainers/Upstream_Release_Monitoring


Please keep in mind that with any upstream change, there may also be packaging changes that need to be made. Specifically, please remember that it is your responsibility to review the new version to ensure that the licensing is still correct and that no non-free or legally problematic items have been added upstream.


Based on the information from Anitya: https://release-monitoring.org/project/12753/


To change the monitoring settings for the project, please visit:
https://src.fedoraproject.org/rpms/pkgconf

Comment 1 Upstream Release Monitoring 2023-05-03 17:33:28 UTC

Scratch build failed. Details below:

GenericError: File upload failed: cli-build/1683135207.5693336.DMiOjfxy/pkgconf-1.9.5-1.fc36.src.rpm
Traceback:
  File "/usr/local/lib/python3.10/site-packages/hotness/use_cases/package_scratch_build_use_case.py", line 56, in build
    result = self.builder.build(request.package, request.opts)
  File "/usr/local/lib/python3.10/site-packages/hotness/builders/koji.py", line 235, in build
    output["build_id"] = self._scratch_build(session, package.name, srpm)
  File "/usr/local/lib/python3.10/site-packages/hotness/builders/koji.py", line 451, in _scratch_build
    session.uploadWrapper(source, serverdir)
  File "/usr/lib/python3.10/site-packages/koji/__init__.py", line 3243, in uploadWrapper
    self.fastUpload(localfile, path, name, callback, blocksize, overwrite, volume=volume)
  File "/usr/lib/python3.10/site-packages/koji/__init__.py", line 3167, in fastUpload
    raise GenericError("File upload failed: %s/%s" % (path, name))

If you think this issue is caused by some bug in the-new-hotness, please report it on the-new-hotness issue tracker: https://github.com/fedora-infra/the-new-hotness/issues

Comment 2 Jens Petersen 2023-07-07 05:36:19 UTC

https://src.fedoraproject.org/rpms/pkgconf/pull-request/5

Is it okay for we or I to build this, please?

pkgconf-1.9.4 --modversion seems quite broken:
it ignores more than two packages!
which I believe got fixed in 1.9.5, which came out in May.

fedora39$ /usr/bin/pkg-config --modversion pango glib-2.0 gio-2.0 harfbuzz
1.50.14
2.76.3
fedora39$

Comment 3 Jens Petersen 2023-07-07 05:56:45 UTC

I guess I should have tested... 1.9.5 is actually worse,
it only prints a single version, lol, hmm.

Is this really the intended new behaviour?
Though I admit the use-case is somewhat tenuous,
but some programs are actually use this "feature"
eg cabal-install for one.

Comment 4 Jens Petersen 2023-07-07 06:00:44 UTC

Anyway I still think it would to update rawhide unless there's a good reason not to, or you consider it too late for f39. :)

Comment 5 Jens Petersen 2023-07-07 06:13:34 UTC

Actually reading the original upstream issue https://github.com/pkgconf/pkgconf/issues/295
it appears that the new behavior is indeed the intended one: just print one package version.
(Though as pointed out there pkgconf should really error or at least warn if more packages given.)