[SOLVED] Flag out of date or bug?

oofnik · 2020-04-12 05:24:31

Hi,

I recently encountered an issue in a core package, util-linux, that has been fixed upstream: https://github.com/karelzak/util-linux/issues/949

The commit that fixed this issue is from two days after the latest release of the util-linux Arch package.

I flagged the package as out-of-date in the package database, but it appears to have been un-flagged.

What can be done in the case where a bug is fixed in the latest stable release upstream, but the package maintainer has not yet incorporated these changes?

Last edited by oofnik (2020-04-14 18:05:11)

nl6720 · 2020-04-12 06:06:23

Are you certain that the bug is fixed in the latest stable release upstream?
The latest release is is v2.35.1 which matches the version of Arch's package. That means that the Arch package is up to date, so flagging it out of date is wrong.
If you want a fix made after a release to get backported, open a bug report in Arch's bug tracker. Or better yet, convince upstream to make a new release.

oofnik · 2020-04-12 07:00:42

nl6720 wrote:

Are you certain that the bug is fixed in the latest stable release upstream?
The latest release is is v2.35.1 which matches the version of Arch's package. That means that the Arch package is up to date, so flagging it out of date is wrong.
If you want a fix made after a release to get backported, open a bug report in Arch's bug tracker. Or better yet, convince upstream to make a new release.

Well, I just noticed that the upstream tag v2.35.1 points to an earlier commit, however the fix is included in the stable/v2.35 branch.

On a fully up-to-date system I am able to reproduce the bug.

This makes sense since the latest package release date as reported by the package database (2020-02-01) is earlier than the commit that fixed the bug (2020-02-04).

Guess I'll open a bug report. Thanks.

Last edited by oofnik (2020-04-12 07:01:42)

Omar007 · 2020-04-12 09:25:57

oofnik wrote:

Well, I just noticed that the upstream tag v2.35.1 points to an earlier commit, however the fix is included in the stable/v2.35 branch.

If upstream already has it in the stable branch, it's basically queued up for the next dot-release but hasn't been released yet.

If the bug is serious enough the bug report is the way to go and it'll probably be included (e.g. GTK recently had one that broke a lot of custom surface Wayland stuff), otherwise waiting for the release of v2.35.2 would probably suffice.

Last edited by Omar007 (2020-04-12 09:26:15)

oofnik · 2020-04-14 05:41:05

I received a reply from one of the maintainers requesting to open a bug report, so I did that. A new, fixed version was published several hours later.

Thanks everyone.

WorMzy · 2020-04-14 08:29:29

Please remember to mark your topic as solved by editing the first post and amending the topic title: https://wiki.archlinux.org/index.php/Co … ow_to_post

Arch Linux

#1 2020-04-12 05:24:31

[SOLVED] Flag out of date or bug?

#2 2020-04-12 06:06:23

Re: [SOLVED] Flag out of date or bug?

#3 2020-04-12 07:00:42

Re: [SOLVED] Flag out of date or bug?

#4 2020-04-12 09:25:57

Re: [SOLVED] Flag out of date or bug?

#5 2020-04-14 05:41:05

Re: [SOLVED] Flag out of date or bug?

#6 2020-04-14 08:29:29

Re: [SOLVED] Flag out of date or bug?

Board footer