Bug#772882: Please, rename as php-markdown-classic
Hi Andreas, On Mon, Jul 6, 2026 at 4:12 PM Andreas Tille wrote: > IMHO we now need a RoM bug to remove libmarkdown-php from > unstable (+testing) to cleanup the archive. I've filed the RoM and ftp-masters already removed libmarkdown-php from the archives. Regards, Laszlo/GCS
Bug#772882: Please, rename as php-markdown-classic
Hi László, thank you for uploading the new source package php-markdown-classic to fix this bug. IMHO we now need a RoM bug to remove libmarkdown-php from unstable (+testing) to cleanup the archive. Kind regards Andreas. Am Sat, May 16, 2026 at 10:33:04AM +0200 schrieb Andreas Tille: > Hi László, > > Am Sat, May 16, 2026 at 09:52:58AM +0200 schrieb László Böszörményi (GCS): > > > > > > https://salsa.debian.org/php-team/pear/php-markdown-classic > > > > > > is ready for upload? I can easily do so if you don't mind. > > I can do it today. > > Thank you. > > > I'm about to delete changelog entries with the old > > name. I'm not sure, should it go to Sid or experimental? Recently I > > saw some discussion that all binary:NEW should go through experimental > > first. > > I think this is more relevant for packages requiring larger scale > transitions. So I personally think sid is fine in this case. > > Thank you for caring for this package > Andreass. > > -- > https://fam-tille.de -- https://fam-tille.de
Bug#772882: Please, rename as php-markdown-classic
Hi László, Am Sat, May 16, 2026 at 09:52:58AM +0200 schrieb László Böszörményi (GCS): > > > > https://salsa.debian.org/php-team/pear/php-markdown-classic > > > > is ready for upload? I can easily do so if you don't mind. > I can do it today. Thank you. > I'm about to delete changelog entries with the old > name. I'm not sure, should it go to Sid or experimental? Recently I > saw some discussion that all binary:NEW should go through experimental > first. I think this is more relevant for packages requiring larger scale transitions. So I personally think sid is fine in this case. Thank you for caring for this package Andreass. -- https://fam-tille.de
Bug#772882: Please, rename as php-markdown-classic
Hi Andreas, On Wed, May 13, 2026 at 8:56 AM Andreas Tille wrote: > do you think > > https://salsa.debian.org/php-team/pear/php-markdown-classic > > is ready for upload? I can easily do so if you don't mind. I can do it today. I'm about to delete changelog entries with the old name. I'm not sure, should it go to Sid or experimental? Recently I saw some discussion that all binary:NEW should go through experimental first. Regards, Laszlo/GCS
Bug#772882: Please, rename as php-markdown-classic
Hi László, do you think https://salsa.debian.org/php-team/pear/php-markdown-classic is ready for upload? I can easily do so if you don't mind. Kind regards Andreas. Am Mon, Apr 27, 2026 at 07:46:57AM +0200 schrieb Andreas Tille: > > Am Sun, Apr 26, 2026 at 08:26:25PM +0200 schrieb László Böszörményi (GCS): > > > Ohhh, I have counterexamples, where my work does not look good. ;-) > > Sure, I've some questions by now. As php-markdown-classic is a new > > package, should not it start with a new d/changelog? > > It surely depends from your point of view. I think its the same code > which has some packaging history and I see no point in hiding this > history. > > > Maybe use some > > alternative versioning (for which I don't have any idea)? Due to > > 1.0.2-1 changes already exist and for php-markdown-classic it is a > > lower version than the previous few ones. > > I think we should definitely use 1.0.2 as upstream version. I simply > used -1 as Debian revision since this would have saved us from > specifying the -sa parameter when building. I'm absolutely fine with > 1.0.2-4 as version number and using -sa to make sure the orig.tar.gz > will be included into the upload. My bet is that the DFSG team will be > sensible enough to cope with both. Finally I consider this as a matter > of taste from the maintainer and we have not much example cases where > this is demonstrated. I also think its not a matter where users will > stumble upon. > > Kind regards >Andreas. > > -- > https://fam-tille.de -- https://fam-tille.de
Bug#772882: Please, rename as php-markdown-classic
Hi László, Am Sun, Apr 26, 2026 at 08:26:25PM +0200 schrieb László Böszörményi (GCS): > > Ohhh, I have counterexamples, where my work does not look good. ;-) > Sure, I've some questions by now. As php-markdown-classic is a new > package, should not it start with a new d/changelog? It surely depends from your point of view. I think its the same code which has some packaging history and I see no point in hiding this history. > Maybe use some > alternative versioning (for which I don't have any idea)? Due to > 1.0.2-1 changes already exist and for php-markdown-classic it is a > lower version than the previous few ones. I think we should definitely use 1.0.2 as upstream version. I simply used -1 as Debian revision since this would have saved us from specifying the -sa parameter when building. I'm absolutely fine with 1.0.2-4 as version number and using -sa to make sure the orig.tar.gz will be included into the upload. My bet is that the DFSG team will be sensible enough to cope with both. Finally I consider this as a matter of taste from the maintainer and we have not much example cases where this is demonstrated. I also think its not a matter where users will stumble upon. Kind regards Andreas. -- https://fam-tille.de
Bug#772882: Please, rename as php-markdown-classic
Hi Andreas, On Sun, Apr 19, 2026 at 4:52 PM Andreas Tille wrote: > Am Sun, Apr 19, 2026 at 03:10:21PM +0200 schrieb László Böszörményi (GCS): > > As always, your work looks good.s > > Ohhh, I have counterexamples, where my work does not look good. ;-) Sure, I've some questions by now. As php-markdown-classic is a new package, should not it start with a new d/changelog? Maybe use some alternative versioning (for which I don't have any idea)? Due to 1.0.2-1 changes already exist and for php-markdown-classic it is a lower version than the previous few ones. Cheers, Laszlo/GCS
Bug#772882: Please, rename as php-markdown-classic
Hi László, Am Sun, Apr 19, 2026 at 03:10:21PM +0200 schrieb László Böszörményi (GCS): > On Sun, Apr 19, 2026 at 2:57 PM Andreas Tille wrote: > > Please let me know what you think. > As always, your work looks good.s Ohhh, I have counterexamples, where my work does not look good. ;-) > Not yet build tested, so I have only > one question. Is there any way to let users follow this package > rename? From the archive side, libmarkdown-php will still exist. Maybe > put the replaces field to php-markdown-classic, the recommends field > to libmarkdown-php, making it an empty transitional package or > anything like that? We need some transitional package, thought. But for now I simply wanted to ask for confirmation, let it pass new queue and care for the transition later. Thanks a lot for your prompt and constructive response Andreas. -- https://fam-tille.de
Bug#772882: Please, rename as php-markdown-classic
On Sun, Apr 19, 2026 at 2:57 PM Andreas Tille wrote: > Please let me know what you think. As always, your work looks good. Not yet build tested, so I have only one question. Is there any way to let users follow this package rename? From the archive side, libmarkdown-php will still exist. Maybe put the replaces field to php-markdown-classic, the recommends field to libmarkdown-php, making it an empty transitional package or anything like that? Cheers, Laszlo/GCS
Bug#772882: Please, rename as php-markdown-classic
Control: tags -1 patch Thanks Hi Laszlo and David, I support the suggestion of David to migrate this package to the PEAR team and following its naming scheme. I have implemented the suggestion in Git at https://salsa.debian.org/php-team/pear/php-markdown-classic and added Laszlo as owner. Please let me know what you think. Kind regards Andreas. -- https://fam-tille.de
