source packages are removed from Sources index while binary packages still depend on them - makes maintaining gpl compliance hard for mirrors
Bug #549041 reported by
James Troup
This bug affects 3 people
Affects | Status | Importance | Assigned to | Milestone | |
---|---|---|---|---|---|
Launchpad itself |
Triaged
|
High
|
Unassigned |
Bug Description
The source <-> binary reference counting appears to be broken unless
I'm missing something really obvious.
| linux-image-
Yet:
| /srv/ftp.
| -rw-r--r-- 1 archvsync archvsync 3803441 2008-04-10 14:03 linux_2.
| -rw-r--r-- 1 archvsync archvsync 4805685 2010-03-16 23:13 linux_2.
| -rw-r--r-- 1 archvsync archvsync 4805899 2010-03-24 10:04 linux_2.
dak style source <-> binary reference counting (which is critical for
GPL compliance) shouldn't have allowed the source for 2.6.24-26 to be
de-published. So, err, where did it go?
summary: |
- don't de-index source packages until they're due to be removed from disk + source packages are removed from indices while binary packages still + depend on them - makes maintaining gpl compliance hard for mirrors |
summary: |
- source packages are removed from indices while binary packages still - depend on them - makes maintaining gpl compliance hard for mirrors + source packages are removed from Sources index while binary packages + still depend on them - makes maintaining gpl compliance hard for mirrors |
Changed in launchpad: | |
importance: | Medium → High |
To post a comment you must log in.
Lala. So it turns out this is in fact my fault and nothing to do with soyuz. The source is on ftp-master, it gets eaten by our magic mirror script which splits out the archive into archive.u.c and ports.u.c because that syncs source based on what's in the Sources indices files. We'll fix it to just blindly sync all source.