Bug#898867: lintian: embedded-php-library libmarkdown-php vs. php-markdown confusion

2021-07-01 Thread Felix Lechner
Hi, On Thu, Jul 1, 2021 at 8:29 AM Thorsten Glaser wrote: > > I don’t follow: movim in sid depends on php-markdown: No worries. I assumed, mistakenly so it seems, that php-markdown was not part of the substitution variables here:

Bug#898867: lintian: embedded-php-library libmarkdown-php vs. php-markdown confusion

2021-07-01 Thread Thorsten Glaser
Felix Lechner dixit: >> Surprised, I discovered that we have *two* versions of the same >> michelf/php-markdown source in Debian, libmarkdown-php being the >> older 1.0 version. > >Even though some time has passed, neither version seems to be used by >other packages in bullseye. (And, despite

Bug#898867: lintian: embedded-php-library libmarkdown-php vs. php-markdown confusion

2021-07-01 Thread Felix Lechner
Hi Thorsten, > Surprised, I discovered that we have *two* versions of the same > michelf/php-markdown source in Debian, libmarkdown-php being the > older 1.0 version. Even though some time has passed, neither version seems to be used by other packages in bullseye. (And, despite your message,

Bug#898867: lintian: embedded-php-library libmarkdown-php vs. php-markdown confusion

2018-10-26 Thread Chris Lamb
Hey Thorsten, > > Let's await input from the markdown maintainers themselves - I have > > not used these libraries. > > indeed, just mind that Nik and I just took over php-markdown by request > of Florian, the former maintainer. Sure. Did you get a reply on this? Would be nice to make some

Bug#898867: lintian: embedded-php-library libmarkdown-php vs. php-markdown confusion

2018-05-17 Thread Chris Lamb
tags 898867 + moreinfo thanks Hey Thorsten, > Now, the 1.0 version allegedly has a feature in that it can be > used as Wordpress plugin or something, so perhaps this situation > is deliberate, but even so, shouldn’t the warning point to the > newer package or even better both? Let's await input