QA checks for package directory dev-util/perforce: dev-util/perforce: digest collisions: major: Digest conflict on 'p4d' in 'dev-util/perforce/files/digest-perforce-2003.1' (original was 'dev-util/perforce/files/digest-perforce-2002.2') major: Digest conflict on 'p4web' in 'dev-util/perforce/files/digest-perforce-2003.1' (original was 'dev-util/perforce/files/digest-perforce-2002.2') major: Digest conflict on 'p4ftpd' in 'dev-util/perforce/files/digest-perforce-2003.1' (original was 'dev-util/perforce/files/digest-perforce-2002.2') major: Digest conflict on 'p4d.1' in 'dev-util/perforce/files/digest-perforce-2003.1' (original was 'dev-util/perforce/files/digest-perforce-2002.2') major: Digest conflict on 'p4d' in 'dev-util/perforce/files/digest-perforce-2003.1-r1' (original was 'dev-util/perforce/files/digest-perforce-2002.2') major: Digest conflict on 'p4web' in 'dev-util/perforce/files/digest-perforce-2003.1-r1' (original was 'dev-util/perforce/files/digest-perforce-2002.2') major: Digest conflict on 'p4ftpd' in 'dev-util/perforce/files/digest-perforce-2003.1-r1' (original was 'dev-util/perforce/files/digest-perforce-2002.2') major: Digest conflict on 'p4d.1' in 'dev-util/perforce/files/digest-perforce-2003.1-r1' (original was 'dev-util/perforce/files/digest-perforce-2002.2') QA checks for package directory dev-util/perforce-cli: dev-util/perforce-cli: digest collisions: major: Digest conflict on 'p4' in 'dev-util/perforce-cli/files/digest-perforce-cli-2003.1' (original was 'dev-util/perforce/files/digest-perforce-2002.2') major: Digest conflict on 'p4.1' in 'dev-util/perforce-cli/files/digest-perforce-cli-2003.1' (original was 'dev-util/perforce/files/digest-perforce-2002.2') major: Digest conflict on 'p4' in 'dev-util/perforce-cli/files/digest-perforce-cli-2003.2' (original was 'dev-util/perforce/files/digest-perforce-2002.2') major: Digest conflict on 'p4.1' in 'dev-util/perforce-cli/files/digest-perforce-cli-2003.2' (original was 'dev-util/perforce/files/digest-perforce-2002.2') QA checks for package directory dev-util/perforce-proxy: dev-util/perforce-proxy: digest collisions: major: Digest conflict on 'p4p' in 'dev-util/perforce-proxy/files/digest-perforce-proxy-2003.1' (original was 'dev-util/perforce/files/digest-perforce-2002.2') major: Digest conflict on 'p4p' in 'dev-util/perforce-proxy/files/digest-perforce-proxy-2003.2' (original was 'dev-util/perforce/files/digest-perforce-2002.2') QA checks for package directory dev-util/perforce-server: dev-util/perforce-server: digest collisions: major: Digest conflict on 'p4d' in 'dev-util/perforce-server/files/digest-perforce-server-2003.2' (original was 'dev-util/perforce/files/digest-perforce-2002.2') major: Digest conflict on 'p4web' in 'dev-util/perforce-server/files/digest-perforce-server-2003.2' (original was 'dev-util/perforce/files/digest-perforce-2002.2') major: Digest conflict on 'p4ftpd' in 'dev-util/perforce-server/files/digest-perforce-server-2003.2' (original was 'dev-util/perforce/files/digest-perforce-2002.2') major: Digest conflict on 'p4d.1' in 'dev-util/perforce-server/files/digest-perforce-server-2003.2' (original was 'dev-util/perforce/files/digest-perforce-2002.2') Looks like this is caused by the same filename being used across packages and versions.
I guess that is supposed to mean stuart does not want the pkg in question anymore. In which case then it becomes a candidate for p.masking/removal as it has qa problems.
maintainer-wanted is for packages not in the tree. maintainer-needed is for packages in the tree. I sent out a request for maintainer to -dev for this one.
I fixed at first in a quit, boring minute the digest files I will not take the maintainance of the packages. Also i checked dev-util/perforce-gui, repoman show me digest errors but did not recommit the digestfiles .oO(?) perforce-server & perforce-proxy was nothing wrong with the digest, Plz recheck this again /bin/joerg
QA checks for package directory /mnt/usbdisc/portage/dev-util/perforce-proxy: /mnt/usbdisc/portage/dev-util/perforce-proxy: digest collisions: major: Digest conflict on 'p4p' in '/mnt/usbdisc/portage/dev-util/perforce-pr oxy/files/digest-perforce-proxy-2003.1' (original was '/mnt/usbdisc/portage/dev- util/perforce/files/digest-perforce-2002.2') major: Digest conflict on 'p4p' in '/mnt/usbdisc/portage/dev-util/perforce-pr oxy/files/digest-perforce-proxy-2003.2' (original was '/mnt/usbdisc/portage/dev- util/perforce/files/digest-perforce-2002.2') QA checks for package directory /mnt/usbdisc/portage/dev-util/perforce-server: /mnt/usbdisc/portage/dev-util/perforce-server: digest collisions: major: Digest conflict on 'p4d' in '/mnt/usbdisc/portage/dev-util/perforce-se rver/files/digest-perforce-server-2003.2' (original was '/mnt/usbdisc/portage/de v-util/perforce/files/digest-perforce-2002.2') major: Digest conflict on 'p4web' in '/mnt/usbdisc/portage/dev-util/perforce- server/files/digest-perforce-server-2003.2' (original was '/mnt/usbdisc/portage/ dev-util/perforce/files/digest-perforce-2002.2') major: Digest conflict on 'p4ftpd' in '/mnt/usbdisc/portage/dev-util/perforce -server/files/digest-perforce-server-2003.2' (original was '/mnt/usbdisc/portage /dev-util/perforce/files/digest-perforce-2002.2') major: Digest conflict on 'p4d.1' in '/mnt/usbdisc/portage/dev-util/perforce- server/files/digest-perforce-server-2003.2' (original was '/mnt/usbdisc/portage/ dev-util/perforce/files/digest-perforce-2002.2') Looks like it's still an issue.
Since these packages will download files with the exact same filename, but different contents, I can't se how this conflicts will go away. Does portage have support for downloading a file into a different filename? If not, maybe it should be considered. For instance: SRC_URI="http://whatever/foo.tar.gz => ${P}-foo.tar.gz" could mean the file foo.tar.gz should be fetched as/renamed to ${P}-foo.tar.gz ?
I masked this
Perforce has now been removed from the tree. Best regards, Stu
