Michael Stone dixit: > No, that's something else that shouldn't have happened
It’s important to me because the upload of rng-tools (>> 2) broke things on unstable. Perhaps letting it migrate to testing wasn’t ideal, but it will work for people there, and it won’t affect existing users or those who not explicitly install it. > as it won't preserve an existing configuration. That, it doesn’t. That’s too tricky to get right anyway. But in my scenario, it isn’t even used with the config or the init script, but as the recipient of a stream from a network service — that to not break was more important at that point after rng-tools (>> 2) was uncoordinatedly up‐ loaded into unstable and all attempts to communicate ig‐ nored (we had this discussion in 2013 or so on Launchpad, and, besides suggesting to me to package it separately as rng-tools-debian, nothing happened there, so don’t be of‐ fended if I merely picked up that suggestion and enacted it). I’m open for discussion about things to get users informed correctly, such as a NEWS entry about not retaining the configuration from rng-tools (though I think apt-listchanges does not show NEWS from newly installed packages), or more explicitly pointing out in the documentation that most users will want the 5.x version except perhaps for low-bandwidth RNGs, or something. I do intend to improve rng-tools-debian occasionally but will insist on keeping it. bye, //mirabilos (hat: rng-tools-debian maintainer) -- <cnuke> den AGP stecker anfeilen, damit er in den slot aufm 440BX board passt… oder netzteile, an die man auch den monitor angeschlossen hat und die dann für ein elektrisch aufgeladenes gehäuse gesorgt haben […] für lacher gut auf jeder LAN party │ <nvb> damals, als der pizzateig noch auf dem monior "gegangen" ist
