Am 28.04.2013 18:28, schrieb Adam D. Barratt: > Indeed. From the release perspective, however, the question we're > concerned with is whether the issue is severe enough that it /must/ be > fixed before the release.
> If it only occurs when a non-default option is used and has affected > fetchmail since before the squeeze release without any users reporting > it, my inclination at this stage is that the above is not the case. I cannot judge if it is easier (process-/effort-wise) to fix this before or after the release; I take that this will be patched only, rather than solved through a patchlevel update. The bug was recently reported against Ubuntu who derived the Debian package; I suppose there are other fetchmail bugs that strike more often in the field than this particular one. The excessively long freeze has however caused the Debian fetchmail package to miss no less than five releases, with two important consequences: 1. it creates a burden on the maintainer for backporting fixes (which grows the further the Debian package diverges from the upstream); 2. it essentially voids support for Debian users through fetchmail channels. The latter only accept inquiries for the latest respective patchlevel release (6.3.26 as of this writing), and the current Debian fetchmail packagers can - this is no reproach, but an observation since the still-current Debian stable release day - hardly keep up with packaging (else we'd have 6.3.25 or .26 in unstable), so you would not want to burden him with additional support load. -- To UNSUBSCRIBE, email to debian-bugs-rc-requ...@lists.debian.org with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org
