2
Discuss how to handle backports (Closes: #793633)
source link: https://salsa.debian.org/debian/developers-reference/-/merge_requests/27
Go to the source link to view the article. You can view the picture content, updated content and better typesetting reading experience. If the link is broken, please click the button below to view the snapshot at that time.
Merged
Created 1 month ago by
Discuss how to handle backports (Closes: #793633)
This commit adds a few words on how the stable-backports archive is working, and how to handle uploads to backports.
Request to merge
backports
into
master
Approval is optional
- 2461 2461 been moved to Incoming yet, it can be removed. (see 2462 2462 :ref:`upload-ftp-master`) 2463 2464 .. _backports: 2465 2466 The Stable backports archive 2467 ================================================================================================================================ 2468 2469 .. _backports-rules: 2470 2471 Basics 2472 -------------------------------------------------------------------------------------------------------------------------------- 2473 2474 Once a package reaches the ``testing`` distribution, it is possible for 2475 anyone to build and upload a backport of that package to the 2476 ``stable-backports``, so that the version of the package in Testing
- 2476 ``stable-backports``, so that the version of the package in Testing 2476 ``stable-backports``, so that the version of the package in ``testing``Suggested change
Is it really possible for "anyone to build and upload a backport of that package to the
stable-backports" ? (eg. I'm neither DD nor DM, and while somehow doubt I have that ability. I can do a lots of other stuff regarding packaging, so developers-reference is an active interest to me)
2490 however good practices to first get in touch with the original maintainer
2491 of the package before attempting to start the maintenance of a package
2492 in the ``stable-backports``. The maintainer can, if they wish, decide
2493 to maintain the backport themselves, or help you doing so. It is not
2494 uncommon, for example, to apply a patch to the unstable version of a
2495 package, to facilitate its backporting.
2496
2497 .. _backports-when:
2498
2499 When can one start uploading to stable-backports?
2500 --------------------------------------------------------------------------------------------------------------------------------
2501
2502 The new ``stable-backports`` is created before the freeze of the next
2503 ``stable`` suite. However, it is not allowed to upload there until the
2504 very end of the freeze cycle. The ``stable-backports`` archive is usually
2505 opened a few weeks before the final release of the next ``stable`` suite.
2494 uncommon, for example, to apply a patch to the unstable version of a
2495 package, to facilitate its backporting.
2496
2497 .. _backports-when:
2498
2499 When can one start uploading to stable-backports?
2500 --------------------------------------------------------------------------------------------------------------------------------
2501
2502 The new ``stable-backports`` is created before the freeze of the next
2503 ``stable`` suite. However, it is not allowed to upload there until the
2504 very end of the freeze cycle. The ``stable-backports`` archive is usually
2505 opened a few weeks before the final release of the next ``stable`` suite.
2506
2507 .. _backports-how-long:
2508
2509 How long shall a package must be maintained when uploaded to stable-backports?
2475 anyone to build and upload a backport of that package to the
2476 ``stable-backports``, so that the version of the package in Testing
2477 can be installed easily in the ``stable`` distribution.
2478
2479 It is forbiden to upload a package to ``stable-backports`` if the package
2480 didn't reach ``testing`` first.
2481
2482 .. _backports-who:
2483
2484 Who can maintain packages in the stable-backports archive?
2485 --------------------------------------------------------------------------------------------------------------------------------
2486
2487 It is not necessarily up to the original package maintainer to maintain
2488 the ``stable-backports`` version of the package. Anyone can do it, and
2489 one doesn't even need the original maintainer approval to do so. It is
2490 however good practices to first get in touch with the original maintainer
- 2501 one doesn't even need the original maintainer approval to do so. It is 2502 however good practices to first get in touch with the original maintainer 2501 one doesn't even need the original maintainer's approval to do so. It is 2502 however good practice to first get in touch with the original maintainerSuggested change
All of what's above has been taken into account in version 27007264...
zigo said on #dc21-talks-1: Let's keep that merge request opened for a while (a few days?), so it has time to gather some feedbacks...
h01ger replied 
Edited
by
Holger Levsen
1 month ago
Recommend
About Joyk
Aggregate valuable and interesting links.
Joyk means Joy of geeK