Bug 644349

Description of problem:
when syncing an erratum that contains packages for several channels, errata notification won't bve sent

Version-Release number of selected component (if applicable):
sat540

Steps to Reproduce:
1. sync rhel-i386-server-5 and rhel-x86_64-server-5
2. take a x86_64 client an register it to satellite
3. downgrade libvorbis (part of RHSA-2009:1561 - Security Advisory erratum)
4. just make sure this erratum is relevant only for one system - x86_64
(even if it contains packages for both - rhel-i386-server-5 and rhel-x86_64-server-5)
5. find out errata id, rhel-i386-server-5 id and rhel-x86_64-server-5 id
(in my case: errata_id: 1227, rhel-i386-server-5_id: 121, rhel-x86_64-server-5_ id: 101)
this is an entry point for taskomatic when an erratum get synced:
open sql console - sqlplus $(spacewalk-cfg-get default_db)
SQL> INSERT INTO rhnErrataQueue (ERRATA_ID,CHANNEL_ID,NEXT_ACTION) VALUES (<errata_id>, <rhel-i386-server-5_id>, sysdate);
1 row created.
SQL> INSERT INTO rhnErrataQueue (ERRATA_ID,CHANNEL_ID,NEXT_ACTION) VALUES (<errata_id>, <rhel-x86_64-server-5_ id>, sysdate);
1 row created.
SQL> commit;
Commit complete.
6. wait for ErrataMailer task ... you can check taskomatic log file
7. do the same inserts as in point 5.) but in reverse order

Actual results:
in one of both cases no errata notification arrives

Expected results:
errata notification in both cases