On 29/03/2019 17:55, Markus Koschany wrote:
Am 29.03.19 um 17:38 schrieb Eugen Dedu:
Wouldn't it make sense to upload to unstable instead of experimental?
Currently, firefox 66 is in unstable, and does not work with ublock
origin from unstable. People who track unstable have to figure out that
they need to install ublock origin from experimental to make it work
with firefox.
I am sorry but Debian development is frozen. If someone discovers an
issue in ublock-origin that affects the Firefox ESR browser in testing,
I have to make an upload to unstable first which would replace the old
version in unstable. Also there is an easy workaround: just use Firefox
ESR for now, if you don't want to use the experimental version.
I am not sure that I have well understood the situation, so sorry if I
am wrong. I put myself in the place of debian users.
Currently in unstable we have two dependent packages which do not work
together. This is not what users expect: they expect debian to just
work, not bothering with installing some package from experimental to
make an unstable package work.
(This remembers me another story, with an update of an essential package
which made it stop functioning: I was told that this is not a
regression, I have just to create a file in my home directory ("look in
Internet for the lines to put inside") to make it work again. Can we
expect users do this??)
Even if debian is in freeze, I think there is a strong reason for debian
managers to accept the new ublock origin. Indeed, they uploaded the
huge firefox in unstable a few days ago, and now the two packages are
incompatible.
Sorry again if I missed something.
Cheers,
Eugen
_______________________________________________
Pkg-mozext-maintainers mailing list
Pkg-mozext-maintainers@alioth-lists.debian.net
https://alioth-lists.debian.net/cgi-bin/mailman/listinfo/pkg-mozext-maintainers
