Bug#431671: Bug#400742: Bug#431671: Bug#400742: Bug#431671: piuparts test: fails to install: line 43: update-updmap: command not found
tags 400742 - wontfix block 400742 by 308285 thanks Florent Rougon [EMAIL PROTECTED] wrote: Frank Küster [EMAIL PROTECTED] wrote: I suggest we remove the wontfix tag and add a block on the dpkg bug requesting the trigger, what do you think? Fine, feel free to do so. Done. Regards, Frank -- Frank Küster Single Molecule Spectroscopy, Protein Folding @ Inst. f. Biochemie, Univ. Zürich Debian Developer (teTeX/TeXLive)
Bug#431671: Bug#400742: Bug#431671: Bug#400742: Bug#431671: piuparts test: fails to install: line 43: update-updmap: command not found
Florent Rougon [EMAIL PROTECTED] wrote: I'm not opposed to that, because this is clean. But do you realize that if go that route, when a package containing .tex files is upgraded to a version that also contains .tex files, then mktexlsr would be run *twice in a row*? Once by old-postrm upgrade and once by new-postinst configure. I can very well imagine the gazillion bug reports we would get if we did that. I guess we should actually go that route, but only once dpkg-triggers are available. Then it's no harm to request the trigger multiple times. new version contains .tex files, you're proposing a system where mktexlsr is run twice in a row in most cases. Doesn't look like an improvement to the current system to me. Not at the moment, indeed. I suggest we remove the wontfix tag and add a block on the dpkg bug requesting the trigger, what do you think? Regards, Frank -- Frank Küster Single Molecule Spectroscopy, Protein Folding @ Inst. f. Biochemie, Univ. Zürich Debian Developer (teTeX/TeXLive)
Bug#431672: Bug#400742: Bug#431671: Bug#400742: Bug#431671: piuparts test: fails to install: line 43: update-updmap: command not found
Hi, Nice to see you back! Frank Küster [EMAIL PROTECTED] wrote: I suggest we remove the wontfix tag and add a block on the dpkg bug requesting the trigger, what do you think? Fine, feel free to do so. Regards, -- Florent
Bug#431671: piuparts test: fails to install: line 43: update-updmap: command not found
Package: texpower-manual Version: 0.2-4 Severity: serious hi, while running archive wide piuparts tests your package failed on install with the following error: Setting up texpower-manual (0.2-4) ... /var/lib/dpkg/info/texpower-manual.postinst: line 43: update-updmap: command not found dpkg: error processing texpower-manual (--configure): subprocess post-installation script returned error exit status 127 Errors were encountered while processing: texpower-manual seems like a missing dependency on tex-common the full log can be found here: http://people.debian.org/~lucas/logs/2007/07/01/ bye, - michael -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Bug#431672: Bug#431671: piuparts test: fails to install: line 43: update-updmap: command not found
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
severity 400742 important
block 431671 by 400742
block 431672 by 400742
thanks
Michael Ablassmeier wrote:
while running archive wide piuparts tests your package failed on install with
the following error:
Setting up texpower-manual (0.2-4) ...
/var/lib/dpkg/info/texpower-manual.postinst: line 43: update-updmap:
command not found
dpkg: error processing texpower-manual (--configure):
subprocess post-installation script returned error exit status 127
Errors were encountered while processing:
texpower-manual
seems like a missing dependency on tex-common
${misc:Depends} is not there and so we don't get a tex-common dependency
from dh_installtex added...
BUT why oh why does dh_installtex add
update-* commands to a package which does *not* contain *any* tex files
at all?
$ dpkg -L texpower-manual
/.
/usr
/usr/share
/usr/share/doc
/usr/share/doc/texpower-manual
/usr/share/doc/texpower-manual/copyright
/usr/share/doc/texpower-manual/changelog.gz
/usr/share/doc/texpower-manual/changelog.Debian.gz
/usr/share/doc/texpower
/usr/share/doc/texpower/manual
/usr/share/doc/texpower/manual/manual.pdf.gz
/usr/share/doc/texpower-manual/manual
Increasing 400742s severity.
(and marking those two bugs blocked by it, I don't see *any* sense
of depending on tex-common and having maintainer scripts running
whatever TeX commands when the package doesn't contain files affecting
TeX itself.)
Regards,
Rene
-BEGIN PGP SIGNATURE-
Version: GnuPG v1.4.6 (GNU/Linux)
iD8DBQFGi2HT+FmQsCSK63MRAoG5AJsEwN4VheCNFtyEIyEagW9wLsgaygCcC/1f
HmWmwmy86wlVleN0ZDt3u7Y=
=f0+l
-END PGP SIGNATURE-
--
To UNSUBSCRIBE, email to [EMAIL PROTECTED]
with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Processed: Re: Bug#431671: piuparts test: fails to install: line 43: update-updmap: command not found
Processing commands for [EMAIL PROTECTED]: severity 400742 important Bug#400742: tex-common: dh_installtex: Introduces unneeded update-* calls in maintainer scripts Severity set to `important' from `normal' block 431671 by 400742 Bug#400742: tex-common: dh_installtex: Introduces unneeded update-* calls in maintainer scripts Bug#431671: piuparts test: fails to install: line 43: update-updmap: command not found Was not blocked by any bugs. Blocking bugs of 431671 added: 400742 block 431672 by 400742 Bug#400742: tex-common: dh_installtex: Introduces unneeded update-* calls in maintainer scripts Bug#431672: piuparts test: fails to install: line 43: update-updmap: command not found Was not blocked by any bugs. Blocking bugs of 431672 added: 400742 thanks Stopping processing here. Please contact me if you need assistance. Debian bug tracking system administrator (administrator, Debian Bugs database) -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Bug#431671: Bug#400742: Bug#431671: piuparts test: fails to install: line 43: update-updmap: command not found
severity 400742 normal
thanks
On Mit, 04 Jul 2007, Rene Engelhard wrote:
while running archive wide piuparts tests your package failed on install
with
the following error:
Setting up texpower-manual (0.2-4) ...
/var/lib/dpkg/info/texpower-manual.postinst: line 43: update-updmap:
command not found
dpkg: error processing texpower-manual (--configure):
subprocess post-installation script returned error exit status 127
Errors were encountered while processing:
texpower-manual
seems like a missing dependency on tex-common
${misc:Depends} is not there and so we don't get a tex-common dependency
from dh_installtex added...
BUT why oh why does dh_installtex add
update-* commands to a package which does *not* contain *any* tex files
at all?
Please check before setting wrong severity levels, or even better check
yourself!
This is a bug in texpower packaging, it should call dh_installtex ONLY
for the texpower and not for the texpower-manual package. As with ALL
dh_ scripts there are -p -A etc options.
And texpower (bin) packages *HAS* tex files so needs tex-common.
So please bug texpower not us.
Increasing 400742s severity.
(and marking those two bugs blocked by it, I don't see *any* sense
of depending on tex-common and having maintainer scripts running
whatever TeX commands when the package doesn't contain files affecting
TeX itself.)
dh_installtex -p texpower
fixes this, I have tried it myself.
Best wishes
Norbert
---
Dr. Norbert Preining [EMAIL PROTECTED]Vienna University of Technology
Debian Developer [EMAIL PROTECTED] Debian TeX Group
gpg DSA: 0x09C5B094 fp: 14DF 2E6C 0307 BE6D AD76 A9C0 D2BF 4AA3 09C5 B094
---
`Er, hey Earthman...'
`Arthur,' said Arthur.
`Yeah, could you just sort of keep this robot with you and
guard this end of the passageway. OK?'
What from? You just said there's no
one here.'
`Yeah, well, just for safety, OK?' said Zaphod.
`Whose? Yours or mine?'
--- Arthur drawing the short straw on Magrathea.
--- Douglas Adams, The Hitchhikers Guide to the Galaxy
--
To UNSUBSCRIBE, email to [EMAIL PROTECTED]
with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Bug#431672: Bug#431671: Bug#400742: Bug#431671: piuparts test: fails to install: line 43: update-updmap: command not found
Hi, Norbert Preining wrote: Please check before setting wrong severity levels, or even better check yourself! This is a bug in texpower packaging, it should call dh_installtex ONLY for the texpower and not for the texpower-manual package. As with ALL dh_ scripts there are -p -A etc options. Yes, there are. And for most dh_ stuff the dh_ scripts *do* figure out that they don't have do do stuff on package foo (like if package foo has no .menu you don't need to add the menu stuff). Even dh_pycentral does that... And texpower (bin) packages *HAS* tex files so needs tex-common. Yes, but neither has texpower-manual nor -examples. dh_installtex -p texpower fixes this, I have tried it myself. I know that this is possible, I'd call this a workaround, though. Gr��e/Regards, Ren� -- .''`. Ren� Engelhard -- Debian GNU/Linux Developer : :' : http://www.debian.org | http://people.debian.org/~rene/ `. `' [EMAIL PROTECTED] | GnuPG-Key ID: 248AEB73 `- Fingerprint: 41FA F208 28D4 7CA5 19BB 7AD9 F859 90B0 248A EB73 signature.asc Description: Digital signature
Bug#431672: Bug#431671: Bug#400742: Bug#431671: piuparts test: fails to install: line 43: update-updmap: command not found
retitle 400742 dh_installtex should check the existence for tex file
tags 400742 - wontfix
thanks
On Mit, 04 Jul 2007, Rene Engelhard wrote:
Yes, there are. And for most dh_ stuff the dh_ scripts *do* figure out
that they don't have do do stuff on package foo (like if package foo has
no .menu you don't need to add the menu stuff). Even dh_pycentral does
that...
Ok, I retitled the bug and removed the wontfix stuff. If I find time I
will implement it.
dh_installtex -p texpower
I know that this is possible, I'd call this a workaround, though.
The man page prominently specify:
Your package should depend on an appropriate version of tex-common so
that the update-* commands are available. (This program adds that
dependency to ${misc:Depends}.)
Furthermore, if someone uploads a package without trying to build it
himself in a clean pbuilder/cowbuilder/sbuild/whatever
Best wishes
Norbert
---
Dr. Norbert Preining [EMAIL PROTECTED]Vienna University of Technology
Debian Developer [EMAIL PROTECTED] Debian TeX Group
gpg DSA: 0x09C5B094 fp: 14DF 2E6C 0307 BE6D AD76 A9C0 D2BF 4AA3 09C5 B094
---
SAVERNAKE (vb.)
To sew municipal crests on to a windcheater in the belief that this
will make the wearer appear cosmopolitan.
--- Douglas Adams, The Meaning of Liff
--
To UNSUBSCRIBE, email to [EMAIL PROTECTED]
with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Bug#431672: Bug#431671: Bug#400742: Bug#431671: piuparts test: fails to install: line 43: update-updmap: command not found
Hi,
Norbert Preining wrote:
On Mit, 04 Jul 2007, Rene Engelhard wrote:
Yes, there are. And for most dh_ stuff the dh_ scripts *do* figure out
that they don't have do do stuff on package foo (like if package foo has
no .menu you don't need to add the menu stuff). Even dh_pycentral does
that...
Ok, I retitled the bug and removed the wontfix stuff. If I find time I
will implement it.
Thanks.
(I just added the workaround as that's needed now...)
dh_installtex -p texpower
I know that this is possible, I'd call this a workaround, though.
The man page prominently specify:
Your package should depend on an appropriate version of tex-common so
that the update-* commands are available. (This program adds that
dependency to ${misc:Depends}.)
I didn't deny that. Why are you citing this? I know that misc:Depends
should be there, that's why it is for texpower. Just not for
the -examples and -manual packages as those don't have any tex files and
I trusted dh_installtex to behave like the other dh_ stuff..
Furthermore, if someone uploads a package without trying to build it
himself in a clean pbuilder/cowbuilder/sbuild/whatever
Yes, but that's *completely* unrelated to the issue at hand. Building
in a sbuild didn't prevent anything mentioned here from happening. Of
course, you can blame me for not running piuparts, but...
Gr��e/Regards,
Ren�
--
.''`. Ren� Engelhard -- Debian GNU/Linux Developer
: :' : http://www.debian.org | http://people.debian.org/~rene/
`. `' [EMAIL PROTECTED] | GnuPG-Key ID: 248AEB73
`- Fingerprint: 41FA F208 28D4 7CA5 19BB 7AD9 F859 90B0 248A EB73
signature.asc
Description: Digital signature
Bug#431672: Bug#431671: Bug#400742: Bug#431671: piuparts test: fails to install: line 43: update-updmap: command not found
On 04/07/07 at 13:00 +0200, Rene Engelhard wrote: Ofcourse, you can blame me for not running piuparts, but... but nobody runs piuparts? ;) -- | Lucas Nussbaum | [EMAIL PROTECTED] http://www.lucas-nussbaum.net/ | | jabber: [EMAIL PROTECTED] GPG: 1024D/023B3F4F | signature.asc Description: Digital signature
Bug#431671: Bug#400742: Bug#431671: piuparts test: fails to install: line 43: update-updmap: command not found
On Mit, 04 Jul 2007, Rene Engelhard wrote:
Ok, I retitled the bug and removed the wontfix stuff. If I find time I
will implement it.
Thanks.
I already added a comment to the svn file with the policy to be
implemented.
that the update-* commands are available. (This program adds that
dependency to ${misc:Depends}.)
I didn't deny that. Why are you citing this? I know that misc:Depends
Because the debhelper manual clearly states that if you do not add -p/-N
or something the dh_installtex works on *all* packages.
himself in a clean pbuilder/cowbuilder/sbuild/whatever
Yes, but that's *completely* unrelated to the issue at hand. Building
Yes, my fault, forgot that it was about run and not build deps.
Best wishes
Norbert
---
Dr. Norbert Preining [EMAIL PROTECTED]Vienna University of Technology
Debian Developer [EMAIL PROTECTED] Debian TeX Group
gpg DSA: 0x09C5B094 fp: 14DF 2E6C 0307 BE6D AD76 A9C0 D2BF 4AA3 09C5 B094
---
Rome wasn't burned in a day.
--- Douglas Adams, The Hitchhikers Guide to the Galaxy
--
To UNSUBSCRIBE, email to [EMAIL PROTECTED]
with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Bug#431672: Bug#400742: Bug#431671: Bug#400742: Bug#431671: piuparts test: fails to install: line 43: update-updmap: command not found
Norbert Preining [EMAIL PROTECTED] wrote: retitle 400742 dh_installtex should check the existence for tex file tags 400742 - wontfix thanks [...] Ok, I retitled the bug and removed the wontfix stuff. If I find time I will implement it. *WARNING* *WARNING* *WARNING* *WARNING* *WARNING* *WARNING* *WARNING* If you check for the existence of TeX files in the package being built and don't run mktexlsr in case there is no TeX file, this is in general short-sighted and incorrect. *WARNING* *WARNING* *WARNING* *WARNING* *WARNING* *WARNING* *WARNING* Reason: if there were TeX files in any previous version of the package (up to the previous Debian release), then mktexlsr *has* to be run. People always complain about cheap stuff being run unnecessarily, but then they will also complain when hell breaks because the cheap stuff was so wisely not run... If there is nothing TeX-related in your package, don't run dh_installtex... -- Florent -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Bug#431671: Bug#400742: Bug#431671: Bug#400742: Bug#431671: piuparts test: fails to install: line 43: update-updmap: command not found
tags 400742 + wontfix thanks On Mit, 04 Jul 2007, Florent Rougon wrote: *WARNING* *WARNING* *WARNING* *WARNING* *WARNING* *WARNING* *WARNING* If you check for the existence of TeX files in the package being built and don't run mktexlsr in case there is no TeX file, this is in general short-sighted and incorrect. *WARNING* *WARNING* *WARNING* *WARNING* *WARNING* *WARNING* *WARNING* Reason: if there were TeX files in any previous version of the package (up to the previous Debian release), then mktexlsr *has* to be run. Right. As usual thanks Florent for reminding me of this. adding again the wontfix. If there is nothing TeX-related in your package, don't run dh_installtex... ACK-ed several times. Best wishes Norbert --- Dr. Norbert Preining [EMAIL PROTECTED]Vienna University of Technology Debian Developer [EMAIL PROTECTED] Debian TeX Group gpg DSA: 0x09C5B094 fp: 14DF 2E6C 0307 BE6D AD76 A9C0 D2BF 4AA3 09C5 B094 --- PITLOCHRY (n.) The background gurgling noise heard in Wimby Bars caused by people trying to get the last bubbles out of their milkshakes by slurping loudly through their straws. --- Douglas Adams, The Meaning of Liff -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Bug#431671: Bug#400742: Bug#431671: Bug#400742: Bug#431671: piuparts test: fails to install: line 43: update-updmap: command not found
Rene Engelhard [EMAIL PROTECTED] wrote: Reason: if there were TeX files in any previous version of the package (up to the previous Debian release), then mktexlsr *has* to be run. Why weren't they in their own package then? Huh? I don't know. I'm not the maintainer of texpower. Then if the package goes away you already have the postrm run mktexlsr because it's there in the old package and gets run when you remove it. Hah! So you would want mktexlsr to be run on 'postrm upgrade' for every package that ships .tex files and runs dh_installtex, right? I'm not opposed to that, because this is clean. But do you realize that if go that route, when a package containing .tex files is upgraded to a version that also contains .tex files, then mktexlsr would be run *twice in a row*? Once by old-postrm upgrade and once by new-postinst configure. I can very well imagine the gazillion bug reports we would get if we did that. Reminder: * Why does mktexlsr need to be run on upgrade? Because the list of .tex file can change (new files, removals, renamings). * Why does mktexlsr need to be run by postinst configure? Because when you go from the removed state to the installed state, the .tex files added by the installation have to be registered. Since new-postinst configure is automatically run on upgrades anyway, we thought it not useful to *additionally* run it on old-postrm upgrade, but if that's what you want, we can enable that and let you deal with the bug reports. :-P If I follow your reasoning, you're embarrassed seeing mktexlsr being run on postinst configure for a package that doesn't ship tex files. Right. But at the same time, you would like that the previous version of the package runs mktexlsr as old-postrm upgrade because you know, the next version might not ship the exact same list of .tex files. Since we don't have a time machine, there is no way to know when writing old-postrm that the next version will have .tex files (in which case, running mktexlsr in old-postrm upgrade is useless, since it will be run by new-postinst configure anyway). Therefore, by your reasoning, we would have to *always* run mktexlsr in old-postrm upgrade. Since, with your proposal of looking whether the new version contains .tex files, postinst configure would also cause a mktexlsr run whenever the new version contains .tex files, you're proposing a system where mktexlsr is run twice in a row in most cases. Doesn't look like an improvement to the current system to me. I'd have split out the tex files (let alone because the dependencies on TeX stuff) and if you app really needs them make the app depend on *them*, not ship them in the normal packages. Making a new binary package only in order to avoid a dependency on tex-common in the main package is ridiculous. tex-common is quite small. This is like comparable to programs/libs, where the (public) libs built from a programs' source package should also not be in package foo but in libfooX. Gni? The reason we need libfooX is for other packages to depend on it, and only on it. But programs that are the only users of their libraries don't need to create libfooX binary packages. dh_installmenu does not add update-menus to everything because one package produced has a menu file and is therefore called. It just adds the needed stuff to the needed packages. So? In contrast to that, dh_installtex when ran without -p adds its snippet to *every* binary package, may it have tex stuff in it or not. And rightly so, because if the maintainer runs dh_installtex for a package, he should have a reason to do so. For instance, because the previous version had .tex files. Anyway, I just worked around it by using -p and will keep it mind. It is not a workaround. It is simply using the tool where it is needed. Do whatever you think, but you are behaving completely different than many normal dh_*'s. dh_installtex is doing more complex stuff than many dh_*'s. It is normal that it is not a clone of all of them. -- Florent -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
