On Sat, 20 Aug 2016, Niko Tyni wrote: > > So I guess we can close this bug? > > Either that, or reassign it to src:apt to track 1.3~rc2 testing migration > I guess. > > I don't mind much, but maybe Santiago (cc'd) does? (given you seem to be > rebuilding stretch not sid)
Hello. Yes, I am building on stretch, using (of course) packages also on stretch. I don't mind that this bug is closed if it's really fixed, but from the point of view of Quality Assurance, please help me to determine how this bug reached testing in the first place and how we could have avoided it to happen in testing. For example, if it's really a bug in apt, then please do a reassign but ensure that the bug is serious (as it breaks other packages), and that it has an "affects" on this package. In such case, also, a versioned build-depends on the fixed apt would help, as it is always a lot better to get an error like "build-dependencies may not be met" (i.e. a dep-wait in wanna-build speak) than an error like the one reported here. Thanks.
