NoMoreAptFtpArchive generates incorrect Releases file

This is required for signed Releases files for commercial.

<cprov> fabbione: ping
<fabbione> cprov: pong
<fabbione> reading your emails right now
<fabbione> just one sec :)
<fabbione> cprov: everything makes sense now
<fabbione> cprov: this is going to be hitchy
<fabbione> if we can't fix it in LP, we will need to do something that's really annoying by updating 4 releases
<cprov> fabbione: well, the fix in NoMoreAptFtparchive is simple (to include the checksums of plain indexes)
<fabbione> and hoping that users will update everything
<cprov> fabbione: however, I'm not sure yet about generating Release file for match the compatibility path
<fabbione> cprov: understood
<cprov> fabbione: of course it's feasible, I'm just not sure if it's right.
<fabbione> it's not the cleanest solution. We agree on this
<fabbione> on the other side it's the best thing to not break user settings
<cprov> fabbione: would it be horrible to request the change in sources.list client ?
<fabbione> cprov: yes..
<fabbione> imagine very large corporates... tons of users .. etc. etc.
<fabbione> there is another solution
<cprov> fabbione: are they using u-m ?
<fabbione> that means changing dapper commercial into its own pocket dapper-commercial and use main component
<fabbione> at that point we would be generating the same archive as it is now
<fabbione> we win for the signatures
<fabbione> and we win for the upload exception rules
<fabbione> cprov: we can't guarantee that
<fabbione> (u-m)
<fabbione> u-m is not the only package manager used to update machines
<cprov> fabbione: yes, I know, I meant also other clever apps
<fabbione> cprov: no matter how clever, if we need to update a stable release, we need to go and look for all packaging admin tools like apt-get and fix them to update sources.list automatically
<fabbione> cprov: that means really really really a lot of work
<cprov> fabbione: right, so you would really prefer that we look after 'keeping the compatibility layer in place' (meaning generate Release files to cope with dapper-commercial/main) ?
<fabbione> cprov: yes indeed
<fabbione> cprov: as i said the other option would be to produce an archive as it is now
<fabbione> cprov: with dapper-commercial pocket
<cprov> fabbione: right, add this to https://bugs.launchpad.net/bugs/134131
<ubuntoid> Malone bug 134131 in soyuz "NoMoreAptFtpArchive generates incorrect Releases file" [High,Confirmed]
<fabbione> cprov: mind if i just copy paste from IRC?
<cprov> fabbione: that's impossible since it would require to transform a COMPONENT into a POCKET
<cprov> fabbione: nope

<cprov> fabbione: talk to julian, but let him know that solving the bug (as comment originally) will only fix the "ubuntu/dapper commercial" problem with signed/valid Release files
<cprov> fabbione: when it is fixed, apt will work with 'ubuntu-commercial/dapper commercial' w/o errors and fail for 'ubuntu-commercial/dapper-commercial main' (the symlinked path)
<cprov> fabbione: extra code will be required to generate Release files for commercial archive that copes with the symlinked path.
<fabbione> well if we generate the Release files for dapper-commercial main, it makes no sense to have the symlinks
<fabbione> we can just publish them properly
<fabbione> like mkdir
<fabbione> etc.
<cprov> I have to leave now, you could call me for the next 4-5 hours
<fabbione> ok
<fabbione> i will past this too in the bug

Fixed in RF 4782