tags 390667 etch-ignore thanks On Thu, 2006-11-30 at 00:09 +0100, Aurélien GÉRÔME wrote: > tags 390667 pending > notfound 390667 1:7.2.2-2 > found 390667 1:7.2.2.dfsg.1-3 > thanks > > Hi Simon, > > On Wed, Nov 29, 2006 at 10:35:56PM +0100, Simon Josefsson wrote: > > Hi! I looked at the version 1:7.2.2.dfsg.1-2 package, and it seems > > the bug have not been fixed. I still see these files in the source > > package: > > > > ircd-hybrid-7.2.2.dfsg.1/doc/technical/rfc1459.txt > > ircd-hybrid-7.2.2.dfsg.1/doc/technical/rfc2812.txt > > ircd-hybrid-7.2.2.dfsg.1/doc/technical/rfc2813.txt > > > > The contents of the files is the real IETF RFCs, which are not > > licensed under a free license. > > Well, in any case, I have been right to setup a dsfg.1 release... ;) > You did not mention those files in your initial bug report, you just > mentioned [1].
Hi! Sorry, my mistake, I didn't notice that. > Of course, I will remove them too, but our dear Release Managers will > probably tag this bug as etch-ignore. I did not give them the time > to do so on this one when you submitted it in the first place. ;P I'm adding the tag now. There is no hurry in fixing this now. If waiting after the release gives you more time to do things properly (e.g., write a script to re-pack the upstream source so you don't have to do it manually), that's fine. I know the timing of these reports is bad regards to the release, but it seems better to report them and tag them etch-ignore than not report them at all. Thanks, Simon
