Hi Jeroen, Am 06.05.2015 um 13:06 schrieb Jeroen Massar: > On 2015-05-06 12:29, Michael Biebl wrote: >> reassign: -1 aiccu >> >> Am 06.05.2015 um 04:43 schrieb Daniel Albers: >>> This is a critical bug of either aiccu or systemd as explained by >>> Pascal. >>> >>> Assigning also to systemd as the aiccu maintainer considers this a >>> systemd bug, although I think message #26 < >>> 546673f0.1040...@localhost.localdomain.org> already points to the >>> proper fix for aiccu. >> >> Jeroen Massar is not listed as maintainer of the aiccu package > > Apologies for not being able to get a DD-bit. > > I am only the person that designed and implemented aiccu, for the rest > indeed, that is totally a useless thing in the Debian universe, why care > about the original author of the code.
Well, the currently listed maintainer is Reinier and he hasn't officially orphaned the package. This should probably be corrected, now that you pointed me to #692465 I wasn't aware of your role regarding this package/software when reading #754121, especially upstream. This was not meant as an offense. So my apologies if this came across the wrong way. > But that is indeed likely just a symptom. systemd is all magic as this > bug shows. As you point out though the 'ifup.d' script might be the > cause of the whole problem though. See also bug #689584 where I've noted > that that script should not exist. > >> Therefor re-assigning back to aiccu. > > I think it should be re-assigned to Debian then as the problem lies > there as that is where the modifications where made and well, Debian is > the entity that can really resolve this. I think what should happen, is that the package is properly orphaned and then someone can pick it up. If you (or your team at SixXS) is interested in having aiccu properly maintained in Debian, you could try to adopt the package after it has been orphaned and get it uploaded to the archive via a sponsored upload. See http://mentors.debian.net/ >> Reinier, if you need help with getting this sorted out, please contact >> the pkg-systemd team. > > He does not want to maintain the package: > https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=692465 > > Thus all those problems will remain. Ok, understood, see above. > And without a DD-bit, nobody can resolve this problem. > >> Is there a reason, aiccu needs to be restarted on ifup? > > Absolutely not. There is no need to *EVER* restart AICCU. > The protocols are made for handling dynamic networks. Thanks for the clarification. I just noticed, that aiccu actually no longer installs the ifup hook. But since the if-up hook is a conffile, it's not automatically removed on upgrades, so needs to be dealt with explicitly. See https://wiki.debian.org/DpkgConffileHandling I also noticed, that the aiccu package installs a pm-utils hook, which restarts the aiccu service on suspend/resume. I guess this one could go as well? > Unfortunately Debian package "maintainers" seem to think they know > better hence instead of listening to the original author of the code and > the persons who run the SixXS service (hint: same people :) things are > changed anyway. See above, if you feel like taking over maintainership of the package, this would be appreciated. -- Why is it that all of the instruments seeking intelligent life in the universe are pointed away from Earth?
signature.asc
Description: OpenPGP digital signature
