Post AFcQfwr0BIeSQSA3W4 by Iutech@fosstodon.org
 (DIR) More posts by Iutech@fosstodon.org
 (DIR) Post #AFcQHNmOw120h9INOq by mplammers@fosstodon.org
       2022-01-12T14:42:39Z
       
       0 likes, 0 repeats
       
       Debian question. My system is affected by a bug in an upstream package:https://midnight-commander.org/ticket/4182The fix is not in Debian stable yet.When I use reportbug, it asks me if the bug could be solved by running either testing/unstable release. After truthfully answering with yes, the reportbug tool says bye.While true, I would still like to indicate that stable is now degraded, until the package from testing is moved to stable. Is it acceptable to still report a bug, just to +1 it?
       
 (DIR) Post #AFcQHOPkZiVUfBhnjU by FreePietje@x0f.org
       2022-01-20T03:17:44Z
       
       0 likes, 0 repeats
       
       @mplammers I'm surprised that reportbug reacted like that. It's perfectly fine to report such an issue.If you can't make reportbug act differently, you can just send an email to submit@bugs.debian.orgDo try to provide the appropriate metadataMake explicit that the bug is present in Stable (and fixed in version XYZ) and that you'd like a backport of https://github.com/MidnightCommander/mc/commit/09e904bf3dec360630b75a895927ca0e7dd9bf0a (the patch being this small greatly increases the chances of it being accepted for Stable)
       
 (DIR) Post #AFcQfwr0BIeSQSA3W4 by Iutech@fosstodon.org
       2022-01-12T14:44:55Z
       
       0 likes, 0 repeats
       
       @mplammers Packages are not moved from testing to stable.The full distribution, once all bugs are fixed, is moved from testing version to stable version.Critical packages may get "backports" that allow to use the fixed version of the package in the stable distribution.
       
 (DIR) Post #AFcQfxHaaRv1kubHxQ by mplammers@fosstodon.org
       2022-01-12T14:51:13Z
       
       0 likes, 0 repeats
       
       @Iutech Ah thanks for that distinction. So there is nothing I should do now?
       
 (DIR) Post #AFcQfxlMnjjpFGX4N6 by Iutech@fosstodon.org
       2022-01-12T14:53:25Z
       
       0 likes, 0 repeats
       
       @mplammers Exactly.Or you can follow to see if the package is considered critical enough to be backported, or you can move to Testing (I'm on stable myself but many people told me than Testing - not SID - is good enough for daily usage nowadays).
       
 (DIR) Post #AFcQfyD18vr8d1T9TE by mplammers@fosstodon.org
       2022-01-12T15:05:30Z
       
       0 likes, 0 repeats
       
       @Iutech I know I can select a backports release, if there is one, which is not the case here yet. Can I select the testing repository for a single package, in this case to get the updated version of mc from bookworm?
       
 (DIR) Post #AFcQfyhVJaF69ZjUzQ by FreePietje@x0f.org
       2022-01-20T03:22:10Z
       
       0 likes, 0 repeats
       
       @mplammers If you go this route, the simplest is adding testing to sources.list, apt update, apt upgrade mc, disable testing in sources.list, apt updateIOW, temporarily adding it to install/upgrade the package, then disabling again.There are ofc also other solutions (like using 'APT::Default-Release "bullseye";'), but that may be more trouble then it's worth. Try to get the Stable package fixed first I'd suggest
       
 (DIR) Post #AFdEVtFPjJHm3Mydyy by mplammers@fosstodon.org
       2022-01-20T12:40:27Z
       
       0 likes, 0 repeats
       
       @FreePietje Thanks Pietje! Long time no speaky, hope you are well. Also thanks for the advice, I have a lot of other stuff going on, but I may push some buttons later.