Groups | Search | Server Info | Keyboard shortcuts | Login | Register [http] [https] [nntp] [nntps]
Groups > linux.debian.maint.python > #17224
| From | Joost van Baal-Ilić <joostvb-debian@mdcc.cx> |
|---|---|
| Newsgroups | linux.debian.maint.python |
| Subject | Re: Guidence on package development |
| Date | 2025-12-04 12:10 +0100 |
| Message-ID | <LYfnH-ijX-3@gated-at.bofh.it> (permalink) |
| References | <LY0I1-8rN-11@gated-at.bofh.it> <LY1b3-8Cm-1@gated-at.bofh.it> <LY1up-900-7@gated-at.bofh.it> |
| Organization | linux.* mail to news gateway |
On Thu, Dec 04, 2025 at 01:40:27AM +0530, Jai kadam wrote: > > why are we making chages in a already debinized repo? If a version 2 of a > package is in upstream why would someone patch the already debinized repo > instead of patching the new upstream and debianzing it ? Because going again from pure upstream to debianized package is generally more work than reusing the previous debianization work. If we are lucky, the previous debianization fits without real changes on the new upstream. HTH! BTW, your questions are more about Debian packaging work then about Debian Python packaging: likely the people at debian-mentors@lists.debian.org (see https://wiki.debian.org/DebianMentorsFaq ) are a better target. Bye, Joost
Back to linux.debian.maint.python | Previous | Next — Previous in thread | Find similar
Guidence on package development jvk <jaivkadam@gmail.com> - 2025-12-03 20:30 +0100
Re: Guidence on package development Andrey Rakhmatullin <wrar@debian.org> - 2025-12-03 21:00 +0100
Re: Guidence on package development Alexandre Detiste <alexandre.detiste@gmail.com> - 2025-12-03 21:20 +0100
Re: Guidence on package development Jai kadam <jaivkadam@gmail.com> - 2025-12-03 21:20 +0100
Re: Guidence on package development Andrey Rakhmatullin <wrar@debian.org> - 2025-12-03 21:20 +0100
Re: Guidence on package development Joost van Baal-Ilić <joostvb-debian@mdcc.cx> - 2025-12-04 12:10 +0100
csiph-web