Re: Bug#419111: context: Fails to install: ctxfmtutil: line 12: kpsewhich: command not found
Dear release people, I think you know best how to contact buildd admins. Reversing the order of what Kurt Roeckx [EMAIL PROTECTED] wrote: http://buildd.debian.org/fetch.cgi?pkg=dfsbuildver=1.0.0arch=amd64stamp=1176485127file=log This one was probably attempted after the first one? No wonder. It's just that removal of texlive-nearlyeverything failed, and now dpkg thinks the files are still present, while they aren't. Now that the debhelper change has been reverted, we can't rebuild texlive with fixed tex-common. We need to upload a reverted tex-common, and then rebuild texlive. Until this has happened, buildds should be prevented to install texlive if that is possible, and the buildds need to be fixed. I think they will even fix themselves as soon as they once installed and then purged a working version. Thanks. The following is only interesting to the bug in Cc: It happened after I got those 2 buildd log: http://buildd.debian.org/fetch.cgi?pkg=frown;ver=0.6.1-6;arch=amd64;stamp=1176485011 This one doesn't show any bug except the removal ones, which are due to the debhelper change. And it shows a strange thing, namely that context is installed at all - I think we've got some dependencies wrong, but I don't see it. Hm, or it's a problem with the buildd log: the commandline in the buildd log installs only texlive packages, but actualy tetex-bin is installed, too. And that pulls in context. Regards, Frank -- Dr. Frank Küster Single Molecule Spectroscopy, Protein Folding @ Inst. f. Biochemie, Univ. Zürich Debian Developer (teTeX/TeXLive)
Re: Bug#419111: context: Fails to install: ctxfmtutil: line 12: kpsewhich: command not found
On Sat, Apr 14, 2007 at 08:56:28AM +0200, Frank Küster wrote: Dear release people, I think you know best how to contact buildd admins. Reversing the order of what Kurt Roeckx [EMAIL PROTECTED] wrote: http://buildd.debian.org/fetch.cgi?pkg=dfsbuildver=1.0.0arch=amd64stamp=1176485127file=log This one was probably attempted after the first one? No wonder. It's just that removal of texlive-nearlyeverything failed, and now dpkg thinks the files are still present, while they aren't. Yes, the 2 logs were after each other. Now that the debhelper change has been reverted, we can't rebuild texlive with fixed tex-common. We need to upload a reverted tex-common, and then rebuild texlive. Until this has happened, buildds should be prevented to install texlive if that is possible, and the buildds need to be fixed. I think they will even fix themselves as soon as they once installed and then purged a working version. What happens if we do install texlive other then it breaks on removal? Kurt -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Re: Bug#419111: context: Fails to install: ctxfmtutil: line 12: kpsewhich: command not found
Kurt Roeckx [EMAIL PROTECTED] wrote: On Sat, Apr 14, 2007 at 08:56:28AM +0200, Frank Küster wrote: Now that the debhelper change has been reverted, we can't rebuild texlive with fixed tex-common. We need to upload a reverted tex-common, and then rebuild texlive. Until this has happened, buildds should be prevented to install texlive if that is possible, and the buildds need to be fixed. I think they will even fix themselves as soon as they once installed and then purged a working version. What happens if we do install texlive other then it breaks on removal? Nothing if the right packages will be installed. But as soon as it was attempted once, everytime it is tried the next time builds will fail because they think the postrm-failed texlive packages are still installed and do not try to install them again. That's what resulted in the context error in the second build log. If none of the buggy texlive packages are installed, the new ones will be automatically picked up when they are available. If they are installed, the least that needs to be done is to manually install and purge the new ones; I didn't check whether this is sufficient. I know we should, but I don't have any time this weekend, and Norbert probably not much, and we rather upload working packages as soon as possible. If the automatic cleanup (i.e. just installing the new ones) does not help, we need an other upload of tex-common to fix this. Regards, Frank -- Dr. Frank Küster Single Molecule Spectroscopy, Protein Folding @ Inst. f. Biochemie, Univ. Zürich Debian Developer (teTeX/TeXLive)
