On Wed, Apr 06, 2022 at 03:02:07PM +0100, Philip Wyett wrote:

Could someone point me to the documentation that relates to upload of packages that have new binary
packages i.e. name change during an update? Specifically to the new/by-hand queue.

Can you explain the context for this? You never need to do anything
special to put a package into NEW.

--
WBR, wRAR

-----BEGIN PGP SIGNATURE-----

iQJhBAABCgBLFiEEolIP6gqGcKZh3YxVM2L3AxpJkuEFAmJNnkgtFIAAAAAAFQAP cGthLWFkZHJlc3NAZ251cGcub3Jnd3JhckBkZWJpYW4ub3JnAAoJEDNi9wMaSZLh qr4P/iRae6PxlpRnByMFNkwKG6sSGEJfMZWal5GZQRlAjMTKKX6H9TEomc9QIjWz i6ZFRYoD7mTRlNkDR16j8s1vgag9u8AW9a/Pg49nDPwotOvBT+IoDUvDL6Xt94KF IExQsA7WIv3RLKo+N3mFp/5VS+UObYEz6aGLvR/ybsd6uH22u5NPDSeCfyWJAvX0 tAXcxpVtFKtrVH6B/2sfcu92yfLmZmUpA1ijgtgLWnRTFjeNDOEJqXedyPBgxgSp +EbfLwYWz3Sn8qV9Q1AXDvktuBxh2HoJcjvnxXLMdOc3CzVyJbv6/7n8XU25Ce2q T6Vz2qAfeYR9pHfeE/hry0l5c07jcSlZilxTBwjtqMAcmuQ5b4p+JO8p/LALqiI5 xtXOoBTjz5lNTlk+LwM9+U37TfsfOJHmWf93b0yTjg4DZtbAHU8sUckxRRVj9Z2D JFt63xOqnTJsU7sdyONkqT+k07bebGDz/tHYOvEtRSLpiSLSQPZ3AABYf/I8MJXN NCenvbhXNBBlceVkO02aMgVyWNt34XRbAjNpwMK8T4R8BsbDBl24Chg8adcZvNs0 LjeGt1XnQJ0EKBiEAev/7+/FHUo8lNbPDhrELOkwhy/3U6/9aAL/yHRlHcHGjUtz oOFXW4/LHSZGSUSK9xF0asUagTGKhHQ/0a1tdfGprUmw2EGr
=1adx
-----END PGP SIGNATURE-----

--- SoupGate-Win32 v1.05
* Origin: fsxNet Usenet Gateway (21:1/5)

Hi all,

Could someone point me to the documentation that relates to upload of packages that have new binary
packages i.e. name change during an update? Specifically to the new/by-hand queue.

Regards

Phil

--
*** Playing the game for the games own sake. ***

WWW: https://kathenas.org

Twitter: @kathenasorg

IRC: kathenas

GPG: 724AA9B52F024C8B

-----BEGIN PGP SIGNATURE-----

iQIzBAABCAAdFiEEcKCsRax3nv6E9jrtckqptS8CTIsFAmJNnV8ACgkQckqptS8C TIvDmg//fImEHE390CJSFk54OBzXOLCr+TDUOANvQFAz5th7hqQ6J5/WyBDwW8VM mB11j/NUMPDuvRm8jB3WZLAE5o9yGVxosc8+SdvKc4IcfukbjnGKJhnb9+0qCJEx ecskDzkRFZvFc9GwHKnQLmSoZvI3dt/0ZVwWYz5q1OYv+rtZyk+A9w5+wP0GT5EN onDEns9BoTve9ZEU/wlYtTt8Sj5biTveJ/IS9wyOs0XyVHYyMEKu0YbGVusOqnwv v9Vdqk+v9djVNJ5+J+2PFWFOEndl0IrtYwLAah97t6alWWJA/GXOG127wHKRkeuG O3i0ehApJ/q0ajCb2wXNyhm0jO0VhzrV03LuV5V/yXElN6kZTZW/bFCxllfDfbwP uctZCRc1L9QIiACkQ8me5NmKVBBXu8r7CdSfSjN+htqfR1Am4tUt8GwbIetf5xQB KEf6kQ4aPamKSbXYcwoiIXdcdwxUG1b+uiR3Sps2aYSkkmJp6D5+iPlxeb8YxKmQ Ny6mLPoNm367XgyTa7gYgx9sAt/mHxijwi5dfvzQV7BlQPnFYiZKoR27h0u/lzCf H2OjlNcVaO1UcOT+j4Dyx8/gRdJFBEb2PRtvQ49HxAJIIjZFTQtZrs49Owh6JzpN orNbyXFaNAEsul4PN3HGgEWmJrHicRwq909xaeEaj3CoCEkp4wA=
=DK0r
-----END PGP SIGNATURE-----

--- SoupGate-Win32 v

On Wed, Apr 06, 2022 at 03:02:07PM +0100, Philip Wyett wrote:

Could someone point me to the documentation that relates to upload of packages that have new binary
packages i.e. name change during an update? Specifically to the new/by-hand queue.

Dunno where the docs are, but in short:

* rename the binary package:
+ edit debian/control
+ mv debian/libfoo42.* → libfoo43.*
+ "git grep libfoo42" elsewhere, just to be sure
* [optional but strongly recommended] test the library's users
* request a sponsored upload even if you're a DM
* once it passes NEW, its users might need a binNMU to rebuild with the new
soname

For a sane library, that's it.

On the other hand, if the -dev package name changes as well, it's
effectively a new package; usually co-installable with the old version.


Meow!
--
⢀⣴⠾⠻⢶⣦⠀ Eight legs good, four legs bad! -- when your drider pwns a
⣾⠁⢠⠒⠀⣿⡁ smelly goodie centaur.
⢿⡄⠘⠷⠚⠋⠀ Rearkick OP -- my grandpa's brother-in-law got one-shotted
⠈⠳⣄⠀⠀⠀⠀ from full hp in RL, please nerf!

--- SoupGate-Win32 v1.05
* Origin: fsxNet Usenet Gateway (21:1/5)

On Wed, Apr 06, 2022 at 03:37:33PM +0100, Philip Wyett wrote:

Could someone point me to the documentation that relates to upload of packages that have new
binary
packages i.e. name change during an update? Specifically to the new/by-hand queue.

Dunno where the docs are, but in short:

* rename the binary package:
+ edit debian/control
+ mv debian/libfoo42.* → libfoo43.*
+ "git grep libfoo42" elsewhere, just to be sure
* [optional but strongly recommended] test the library's users
* request a sponsored upload even if you're a DM
* once it passes NEW, its users might need a binNMU to rebuild with the new
soname

For a sane library, that's it.

On the other hand, if the -dev package name changes as well, it's effectively a new package; usually co-installable with the old version.

Meow!

Thanks Adam, that answered it for me. I will do a mentors upload later on.

If you were actually asking about the whole procedure, and not about NEW, please read and follow https://wiki.debian.org/Teams/ReleaseTeam/Transitions

--
WBR, wRAR

-----BEGIN PGP SIGNATURE-----

iQJhBAABCgBLFiEEolIP6gqGcKZh3YxVM2L3AxpJkuEFAmJNpnMtFIAAAAAAFQAP cGthLWFkZHJlc3NAZ251cGcub3Jnd3JhckBkZWJpYW4ub3JnAAoJEDNi9wMaSZLh SPYP/j32PBjM5VZNdmIvu9NU3tXzdSVETfYNo1dX91ZcxJQ7bUPOs+i8nTuVt6gv pMlrwb1KbIisw9B1ZXTvRuF8xQ3UoGXLd7Z/m8i5G+NXyE+aQH0wkh3SsQ7ijpdz mFc79C5gPwELY4sFNs+8zIgZ/lHXzsFFz8OSuuIAvXLAZynnDGljwU84hh/Mt73K PbY6sJJCMexU6poGNj0SihQkbxKrIyfdgXsTTFJil5XrbGL15xuUel+3zKHpSlGo RPKGQOkjrVq2XAw+z33Biyw0xkBPnTgHbYCyH4LL5zHKpkMrP3N41jveBQWrY8wz biHsWhChTyejjKWHsNLGvxNkocrt8SNaPLiTuxpAkFDfUdACix5g8eAcg1cRug6T zEfVnzxyPloS6NsM/Xq99k0g2+EFh6uuTTMF5WJpoygZcRVccCEURVTN757b0WDZ APi0KO75dNe97B/ixyFJFik4CQUVBZEHqdYozY6HPZGZcZIcw1lSyT+WYDikNsnR rUprnjVft1/kbU/Dot6ST1dL86/HMfIDwywERtEzfGS9TwvP9N1i+WOn6zogcPGs F+QQ5k/sWmR3rECiurrsbRP2gPYxGKrut/7TfwYIef1LIAqiYn9+UgezWEaqPU/M Ssa/rtIVRxPMcQisXG5oSAI8RJIYgGeujmAQyqMeNsXKqTd/
=cyX5
-----END PGP SIGNATURE-----

--- SoupGate-Win32 v1.05
* Origin: fsxNet Usenet Gateway (21:1/5)

On Wed, 2022-04-06 at 16:16 +0200, Adam Borowski wrote:

On Wed, Apr 06, 2022 at 03:02:07PM +0100, Philip Wyett wrote:

Could someone point me to the documentation that relates to upload of packages that have new
binary
packages i.e. name change during an update? Specifically to the new/by-hand queue.

Dunno where the docs are, but in short:

* rename the binary package:
+ edit debian/control
+ mv debian/libfoo42.* → libfoo43.*
+ "git grep libfoo42" elsewhere, just to be sure
* [optional but strongly recommended] test the library's users
* request a sponsored upload even if you're a DM
* once it passes NEW, its users might need a binNMU to rebuild with the new
soname

For a sane library, that's it.

On the other hand, if the -dev package name changes as well, it's
effectively a new package; usually co-installable with the old version.

Meow!

Thanks Adam, that answered it for me. I will do a mentors upload later on.

Regards

Phil

--
*** Playing the game for the games own sake. ***

WWW: https://kathenas.org

Twitter: @kathenasorg

IRC: kathenas

GPG: 724AA9B52F024C8B

-----BEGIN PGP SIGNATURE-----

iQIzBAABCAAdFiEEcKCsRax3nv6E9jrtckqptS8CTIsFAmJNpa0ACgkQckqptS8C TIvt6Q//VM8VVKcOhBfvUJcU5Q87cFhG1qhDdRBTT7IgR2OSOslzfsPmeQoGYORW euCE9uw61K25ynW64+XbbPxAhkryqFK3dhjZnhApTT965mclhIS8tOdRNq8VxFOp wb7E6n5d+ghG0omBIQVco6UiCmcnTXakR+eDmRGYAuAErOLo/N6phO15IIAnvO7N kiDWSlZvy3zlILckrac2Ytajmw0HJt5ETxTpv07ttKWMkziNYXPsraY9zgUF3dMw FoQRClMEbDdgUyfCn1uuUJR8YVTGwILACUieptQXq7ZHN4NO88zOIS8RFnt+oiIr 0FM8+Q8vLzEBVPHl9RPpc9MkBKFInaztxYOkJY4U/7taXbovqAgrrWkGzB9Ffc3J L1tYY4mwNsBPH5vINfAMca5tnA6P7pQV5hh4KVSPWLl9FnCxkizVikKSEbWU+D2E MmMOnQOB5fgOlkIjGrLJHEQrKFz4hlwxuVP3pmMx4S9B8n9p08Lveil2bkd2dbYu Y2TeqxnIT6ja1IFh2HVU9vZT7CswSpAoJn7/kcAyxtGv/pZk6JuCw9CTyHprIoLU 258lHqQU21lTnHiLxw2tGaALR/H/haT6JoGs6uGpPsgRTqiLiXdxujOwaGv5II0T ZTdQ65kdo68uUEGpGWKVLixRSi1nc12ayHCahdWvlgBda8x4aBo=
=aGHw
-----END PGP SIGNATURE-----

--- SoupGate-Win32 v

On Wed, Apr 06, 2022 at 03:36:31PM +0100, Philip Wyett wrote:

Could someone point me to the documentation that relates to upload of packages that have new
binary
packages i.e. name change during an update? Specifically to the new/by-hand queue.

Can you explain the context for this? You never need to do anything
special to put a package into NEW.

This was just related to libfilezilla that has regular API soname bumps.

My question was answered by Adam (kilobyte) that upload of such packages need to be a sponsored
upload even if a DM.

Please note that your question didn't mention the DM context.


--
WBR, wRAR

-----BEGIN PGP SIGNATURE-----

iQJhBAABCgBLFiEEolIP6gqGcKZh3YxVM2L3AxpJkuEFAmJNqIItFIAAAAAAFQAP cGthLWFkZHJlc3NAZ251cGcub3Jnd3JhckBkZWJpYW4ub3JnAAoJEDNi9wMaSZLh evYP/0bk5dreaXysNQyFNn4WJNF7mrnvdbWizAEX1yz2VGwIURkMN22kysNnqBdS My7fTxi5iAbJbyeC6nHQrBbd0LHoumVsKwyFJrv8v0502RT+RcYMFi2B5CFu0Vgy sm+3e9CFM9BmOzNXmEBBOu5NKejxNo+QSAZdrVhTjFFp/7usNhKx77fkvJfsmkrj zmfcf6sCrODdu503lVPcf8BBJGBcbX4+bsOIZH01ha+iILsd34FImo+YCOBHq9Qj dhMCl9nYf4RV7nKK9tOiPU3i6bzGFjmThyd4o6mmOxJfAlVHz28jzZ8LiZuI9Ml1 WdDOkUgcWlD7im21Y0MFztoU0ExTz0qFFgr+1bUT3Q4qcnEEKMKoOwlW1flOARHy yculM1CbStId1JZqQoMsRfduiO2SWx+2jkWwB3/4HlYwWK4KMTfhfx57Y4O9+mth toP62hvt0zH6q+NRnAGtozVXkG8Ou1g2MTO42uDMppqQG+FLyvkHNtC5Q9BNs2Wd L7FzjsFka8e8Y05Rk1E+ZRCH10lDyOV4cmIlUnSzTYHf3NQbpm6gntclT2mkymzG 1W72N+M4OPxqm9+uFzE7dfeyuQNCZl84tUrCtWVr/3LWdbCd/HpRhtRUJoE1qUtv JBn3riw4AlRpZ4ScTSvXwcUcxNxDqyW0YBX1QDqoth+rhkki
=wm/5
-----END PGP SIGNATURE-----

--- SoupGate-Win32 v1.05
* Origin: fsxNet Usenet Gateway (21:1/5)

On Wed, 2022-04-06 at 19:49 +0500, Andrey Rahmatullin wrote:

On Wed, Apr 06, 2022 at 03:36:31PM +0100, Philip Wyett wrote:

Could someone point me to the documentation that relates to upload of packages that have
new
binary
packages i.e. name change during an update? Specifically to the new/by-hand queue.

Can you explain the context for this? You never need to do anything special to put a package into NEW.

This was just related to libfilezilla that has regular API soname bumps.

My question was answered by Adam (kilobyte) that upload of such packages need to be a sponsored
upload even if a DM.

Please note that your question didn't mention the DM context.

Hi,

I understand that, but Adam did answer the one thing I needed to know and stopped what would have
been a lot of head scratching. Many thank for the assistance.

Regards

Phil

--
*** Playing the game for the games own sake. ***

WWW: https://kathenas.org

Twitter: @kathenasorg

IRC: kathenas

GPG: 724AA9B52F024C8B

-----BEGIN PGP SIGNATURE-----

iQIzBAABCAAdFiEEcKCsRax3nv6E9jrtckqptS8CTIsFAmJNqbkACgkQckqptS8C TIvaxQ//b9ghQplVdypQ7qS6W9SGLHBlOfcksGMY8geNncIT7Ry8XTBVjuQLu84j NoY85Se9wgCvF6MBuQtOep4YgU8x5d/SuCATcO941cwWpZGUBDopINILMZl3zCXQ 6OFIM2nEuW3eQjbM6vD+uMTzBKnKW3xcBqe2MIRkZHDoiNa9W84p25gYBxIIFQrF 0Q757yMq89ru29G2FwVR31igrJ6pa5dTCdpsmM02MQMLWRGAhq/B0jhqF3fmrylJ svZztzoCIz6NJm+6oXzG6CQTiZPHOnU5WZvetlH4hDABqu2e2wSk/hc26DhPPOn+ ND19eX4dqBlZbPmk3wbJF2g4aaqsaXYg8xuefAO/UM/LVENYDyTMk5JIKnPbCe/W WYuf9IA0uT3W/bY2hCA399hwdm2G+0IBoz/k9hpaCio7wY4ucxmqtQqHMzASD0uc 4FMJnTFJp81k9NAjA95QyXvQ8jteYG7+/GN8tecpwepQ6HpWciloKX+FQ6MO02I+ 0LjFxiI0sXwix/lewHLfmL2atuQLkLbpyAXq87H7Ip9GtcGNXaGSyJbX8Fv09Z3Z ADrpNg+v6EpzwVL25M9q7+rFXd7Sg/Ik5+SNveSKf1Q+7AIK7TccEoFcW+UG9IkD RKDHcUicfCOAL2jAhMH9tXBFBk6+AGHSdznCXqlP67C5h0Kbe6s=
=VuRM
-----END PGP SIGNATURE-----

--- SoupGate-Win32 v

On 2022-04-06 Adam Borowski <[email protected]> wrote:

On Wed, Apr 06, 2022 at 03:02:07PM +0100, Philip Wyett wrote:

Could someone point me to the documentation that relates to upload
of packages that have new binary packages i.e. name change during an update? Specifically to the new/by-hand queue.

Dunno where the docs are, but in short:

* rename the binary package:
+ edit debian/control
+ mv debian/libfoo42.* → libfoo43.*
+ "git grep libfoo42" elsewhere, just to be sure
* [optional but strongly recommended] test the library's users
* request a sponsored upload even if you're a DM
* once it passes NEW, its users might need a binNMU to rebuild with the new
soname

[...]

Worth mentioning: An upload introducing new biary packages cannot be a source-only upload, the binaries needs to included in the upload.

cu Andreas
--
`What a good friend you are to him, Dr. Maturin. His other friends are
so grateful to you.'
`I sew his ears on from time to time, sure'

--- SoupGate-Win32 v1.05
* Origin: fsxNet Usenet Gateway (21:1/5)