Hello If we rename all the scripts to "ase-<name>", then the change is obvious enough that we probably won't need that - in my opinion. It would be slightly annoying to have many scripts installed under two names, with half of them deprecated.
Regards Ask 2013/7/29 Jens Jørgen Mortensen <je...@fysik.dtu.dk>: > Den 28-07-2013 23:12, Ask Hjorth Larsen skrev: > >> Hello >> >> I believe the 'ag' script in python-ase will change its name to >> ase-gui in future upstream versions. Jens Jørgen (CC'd), isn't that >> correct? > > > That's correct. The renaming is in the "cli" branch which I hope to merge > soon. > > Should we simply drop "ag" for version 3.8 or keep it for one more release > with a deprecation warning? > > Jens Jørgen > > >> >> Either way, two-letter script names are probably a very bad idea >> unless they are OS commands or something like that. >> >> Best regards >> Ask >> >> 2013/7/27 Andreas Beckmann <a...@debian.org>: >>> >>> Package: python-ase,silversearcher-ag >>> Severity: serious >>> User: trei...@debian.org >>> Usertags: edos-file-overwrite >>> >>> Architecture: amd64 >>> Distribution: jessie >>> >>> Hi, >>> >>> automatic installation tests of packages that share a file and at the >>> same time do not conflict by their package dependency relationships has >>> detected the following problem: >>> >>> Selecting previously unselected package python-ase. >>> Unpacking python-ase (from .../python-ase_3.6.0.2515-1.1_all.deb) ... >>> dpkg: error processing >>> /var/cache/apt/archives/python-ase_3.6.0.2515-1.1_all.deb (--unpack): >>> trying to overwrite '/usr/bin/ag', which is also in package >>> silversearcher-ag 0.15~pre+20130512-1 >>> dpkg-deb: error: subprocess paste was killed by signal (Broken pipe) >>> Errors were encountered while processing: >>> /var/cache/apt/archives/python-ase_3.6.0.2515-1.1_all.deb >>> >>> This is a serious bug as it makes installation fail, and violates >>> sections 7.6.1 and 10.1 of the policy. An optimal solution would >>> consist in only one of the packages installing that file, and renaming >>> or removing the file in the other package. Depending on the >>> circumstances you might also consider Replace relations or file >>> diversions. If the conflicting situation cannot be resolved then, as a >>> last resort, the two packages have to declare a mutual >>> Conflict. Please take into account that Replaces, Conflicts and >>> diversions should only be used when packages provide different >>> implementations for the same functionality. >>> >>> Here is a list of files that are known to be shared by both packages >>> (according to the Contents file for sid/amd64, which may be >>> slightly out of sync): >>> >>> usr/bin/ag >>> usr/share/man/man1/ag.1.gz >>> >>> This bug is assigned to both packages. If you, the maintainers of >>> the two packages in question, have agreed on which of the packages will >>> resolve the problem please reassign the bug to that package. You may >>> also register in the BTS that the other package is affected by the bug. >>> >>> Cheers, >>> >>> Andreas >>> >>> PS: for more information about the detection of file overwrite errors >>> of this kind see http://edos.debian.net/file-overwrites/. > > -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org
