Re: Processed: Fixed in NMU xawtv 3.03-1.1
severity 53630 important
thanks
On 8 Jan 2000, Debian Bug Tracking System wrote:
> Processing commands for control@bugs.debian.org:
> > severity 53630 fixed
> Bug#53630: xawtv_3.03-1(unstable): build error
> Severity set to `fixed'.
> > quit
> Stopping processing here.
>From 7.3 of the Developer's Reference:
===
* Make sure that the package bug is in the Debian Bug Tracking System
(BTS). If not, submit a bug.
(bug already existed, and is what prompted the nmu in the first place)
* Email the maintainer, and offer to help fix the package bug. Give it a
few days.
(done during a bug-squash party, not needed)
* Go ahead and fix the bug, submitting a patch to the right bug in the
BTS. Build the package and test it as discussed in Checking the package
prior to upload, Section 6.2.3. Use it locally.
(Not needed in this case, as it is only a bug during the compile of the
package)
* Wait a couple of weeks for a response.
(done during a bug-squash party, not needed)
* Email the maintainer, asking if it is OK to do an NMU.
(done during a bug-squash party, not normally needed, however, emailing the
patch to the bts would suffice for this, which wasn't done)
* Double check that your patch doesn't have any unexpected side effects.
Make sure your patch is as small and as non-disruptive as it can be.
(the non-existant patch(which I had to generate myself, and is included below)
has no effect whatsoever, so it can't possibly have side effects)
* Wait another week for a response.
(done during a bug-squash party, not needed)
* Go ahead and do the source NMU, as described in How to do a source NMU,
Section 7.4.
===
and 7.4.3, of the same document:
===
Maintainers other than the official package maintainer should make as few
changes to the package as possible, and they should always send a patch as
a unified context diff (diff -u) detailing their changes to the Bug
Tracking System.
===
This is NOT fixed. No way at all.
First, before doing an nmu, you should send a diff of your changes to the bts.
This was not done.
Next, you should actually verify that you have fixed the problem in question.
This was not done(note, doing the diff mentioned above would have shown that
nothing had been fixed).
I see no diff from you, for this nmu.
This means I have to take time to figure out what you have done to the
package. If you would have generated the diff at the time you did your
non-fix, it would have saved time.
Please, please, please, follow protocol when doing nmu's.
If a package is too complicated for you to understand how it is built, don't
attempt to fix it, until you understand it.
Now, because you did this non-fixing nmu, I am obliged to store this into my
changelog. I really don't want to, because you did nothing for this upload.
===
diff -ruN 1/xawtv-3.03/debian/changelog 1.1/xawtv-3.03/debian/changelog
--- 1/xawtv-3.03/debian/changelog Sat Jan 8 14:35:58 2000
+++ 1.1/xawtv-3.03/debian/changelog Sat Jan 8 14:28:11 2000
@@ -1,3 +1,10 @@
+xawtv (3.03-1.1) unstable; urgency=low
+
+ * Non-maintainer upload during bug-squashing-party.
+ * Fixed build error (closes: #53630)
+
+ -- Christian Kurz <shorty@debian.org> Sat, 8 Jan 2000 15:26:28 +0100
+
xawtv (3.03-1) unstable; urgency=low
* New upstream source.
===
----BEGIN GEEK CODE BLOCK----
Version: 3.12
GCS d- s: a-- c+++ UL++++ P+ L++++ !E W+ M o+ K- W--- !O M- !V PS--
PE++ Y+ PGP++ t* 5++ X+ tv b+ D++ G e h*! !r z?
-----END GEEK CODE BLOCK-----
----BEGIN PGP INFO----
Adam Heath <doogie@debian.org> Finger Print | KeyID
67 01 42 93 CA 37 FB 1E 63 C9 80 1D 08 CF 84 0A | DE656B05 PGP
AD46 C888 F587 F8A3 A6DA 3261 8A2C 7DC2 8BD4 A489 | 8BD4A489 GPG
-----END PGP INFO-----
Reply to: