In <[🔎] ij4ebp$kke$1@dough.gmane.org>, Thilo Six wrote: >Boyd Stephen Smith Jr. wrote the following on 11.02.2011 22:55 >> In this case, it is probably an upload that was scheduled before the Lenny >> -> Squeeze transition but finished after the transition. At least one >> security update has done this and is currently being repackaged for >> oldstable. It's possible it also happened with something that was >> targeting stable-proposed- updates. >> >> This package won't cause any problems where it is at, so a bug is not >> appropriate for it being present in squeeze-proposed-updates. However, if >> you think this should appear in lenny-proposed-updates and it isn't there, >> you should make sure the maintainer is notified. > >Now how to find out those 2 packages which are in squeeze-proposed-updates >but not in lenny-proposed-updates? (aptitude search '~S~Asqueeze-proposed-updates!~Alenny-proposed-updates'), maybe? You might have to use different search terms, depending on what is in those Release files. >If i understand you correctly the debian workflow is to upload all >stable-updates to s-p-u and then the SRM moves those to o-p-u afterwards? No, sorry. My understanding is that updates and go directly into os-p-u or s-p-u and then they can migrate to s-u (new) when tested, or oldstable or stable at a point release. I mean that having packages that were supposed to be for os-p-u in s-p-u will not adversely affect users of s-p-u, since the version numbers will be lower than the ones in stable. -- Boyd Stephen Smith Jr. ,= ,-_-. =. bss@iguanasuicide.net ((_/)o o(\_)) ICQ: 514984 YM/AIM: DaTwinkDaddy `-'(. .)`-' http://iguanasuicide.net/ \_/
Attachment:
signature.asc
Description: This is a digitally signed message part.