Bug#680011:

2012-07-10 Thread Michael Biebl
On 10.07.2012 23:03, Michael Biebl wrote: > On 10.07.2012 22:08, Jakub Wilk wrote: >>> - $(XSLTPROC) -o $@ $(XSLTPROC_FLAGS) >>> http://docbook.sourceforge.net/release/xsl/current/manpages/docbook.xsl $< >>> + faketime "`TZ=GMT stat -c %y $<`" $(XSLTPROC) -o $@ $(XSLTPROC_FLAGS) >>> http://d

Bug#680011:

2012-07-10 Thread Michael Biebl
On 10.07.2012 22:08, Jakub Wilk wrote: > * Michael Biebl , 2012-07-10, 21:15: >>> It parses timezones correctly, but it doesn't change TZ for the >>> program it executes. So xsltproc would still print date in local >>> timezone, unless you reset TZ manually. >> >> You are right, of course. >> Upd

Bug#680011:

2012-07-10 Thread Jakub Wilk
* Michael Biebl , 2012-07-10, 21:15: It parses timezones correctly, but it doesn't change TZ for the program it executes. So xsltproc would still print date in local timezone, unless you reset TZ manually. You are right, of course. Updated patch attached. [...] - $(XSLTPROC) -o $@ $(X

Bug#680011:

2012-07-10 Thread Michael Biebl
On 10.07.2012 21:09, Jakub Wilk wrote: > * Michael Biebl , 2012-07-10, 20:58: >> It seems faketime seems to handle timezone information just fine, which >> simplifies it quite a bit. > > It parses timezones correctly, but it doesn't change TZ for the program > it executes. So xsltproc would stil

Bug#680011:

2012-07-10 Thread Jakub Wilk
* Michael Biebl , 2012-07-10, 20:58: It seems faketime seems to handle timezone information just fine, which simplifies it quite a bit. It parses timezones correctly, but it doesn't change TZ for the program it executes. So xsltproc would still print date in local timezone, unless you reset T

Bug#680011:

2012-07-10 Thread Michael Biebl
On 10.07.2012 20:39, Michael Biebl wrote: > And to avoid skew from differing timezones, also set TZ to GMT... It seems faketime seems to handle timezone information just fine, which simplifies it quite a bit. -- Why is it that all of the instruments seeking intelligent life in the universe are p

Bug#680011:

2012-07-10 Thread Michael Biebl
On 10.07.2012 20:33, Michael Biebl wrote: > On 10.07.2012 20:09, Jakub Wilk wrote: >> * Michael Biebl , 2012-07-10, 19:44: >>> As for a work-around: >>> the attached, simple script replaces the dates with the mtime of the >>> corresponding .xml file. >>> This could be run in override_dh_install: b

Bug#680011:

2012-07-10 Thread Michael Biebl
On 10.07.2012 20:09, Jakub Wilk wrote: > * Michael Biebl , 2012-07-10, 19:44: >> As for a work-around: >> the attached, simple script replaces the dates with the mtime of the >> corresponding .xml file. >> This could be run in override_dh_install: before we call dh_install > > It might be simpler

Bug#680011:

2012-07-10 Thread Michael Biebl
Shawn, On 10.07.2012 18:39, Michael Biebl wrote: > Splitting off an arch:all package for a single man page is overkill. > > I would probably just ignore the bug and wait for a fix in docbook-xsl > or remove ma:same from libpam-systemd again for the time being. have you filed a corresponding bug

Bug#680011:

2012-07-10 Thread Jakub Wilk
* Michael Biebl , 2012-07-10, 19:44: As for a work-around: the attached, simple script replaces the dates with the mtime of the corresponding .xml file. This could be run in override_dh_install: before we call dh_install It might be simpler to run xsltproc (or whatever does the conversion) u

Bug#680011:

2012-07-10 Thread Michael Biebl
On 10.07.2012 18:39, Michael Biebl wrote: > On 10.07.2012 18:28, shawn wrote: >> A workaround for this bug, would be to ship the man pages in a arch: >> all, instead of arch: any package, this way they would only be built >> once. (there would only be one package), but it would also mean another >>

Bug#680011:

2012-07-10 Thread Michael Biebl
On 10.07.2012 18:28, shawn wrote: > A workaround for this bug, would be to ship the man pages in a arch: > all, instead of arch: any package, this way they would only be built > once. (there would only be one package), but it would also mean another > package. Any other way that involved post-proce

Bug#680011:

2012-07-10 Thread shawn
A workaround for this bug, would be to ship the man pages in a arch: all, instead of arch: any package, this way they would only be built once. (there would only be one package), but it would also mean another package. Any other way that involved post-processing the generated man pages seems very u

Bug#680011: libpam-systemd: arch-dependent file in "Multi-Arch: same" package

2012-07-10 Thread Jakub Wilk
* shawn , 2012-07-09, 17:39: retitle 680011 build-time timestamps in generated manpages break multiarch reassign 680011 docbook-xsl affects 680011 systemd tag 680011 patch stop This is wrong. I'm interested in the concrete bug in libpam-systemd. Just making docbook-xsl not output dates in comm

Bug#680011: libpam-systemd: arch-dependent file in "Multi-Arch: same" package

2012-07-09 Thread shawn
retitle 680011 build-time timestamps in generated manpages break multiarch reassign 680011 docbook-xsl affects 680011 systemd tag 680011 patch stop In docbook-xsl/manpages/other.xsl:290 and 377 (see also docbook-xsl/params/man.th.extra1.suppress.xml) docbook emits build-time timestamps into man p

Bug#680011: libpam-systemd: arch-dependent file in "Multi-Arch: same" package

2012-07-02 Thread Jakub Wilk
Package: libpam-systemd Version: 44-3 Severity: important User: multiarch-de...@lists.alioth.debian.org Usertags: multiarch libpam-systemd is marked as "Multi-Arch: same", but the following file is architecture-dependent: /usr/share/man/man8/pam_systemd.8.gz An example diff between i386 and a