bugs.debian.org/1030586
Preview meta tags from the bugs.debian.org website.
Linked Hostnames
8- 2 links tobugs.debian.org
- 2 links tobuildd.debian.org
- 1 link topeople.debian.org
- 1 link toqa.debian.org
- 1 link tosalsa.debian.org
- 1 link totracker.debian.org
- 1 link towww.debian.org
- 1 link towww.eyrie.org
General Meta Tags
3- title#1030586 - lintian: Testsuite failure on some systems: 1h time offset in test ancient-source - Debian Bug report logs
- Content-Typetext/html;charset=utf-8
- viewportwidth=device-width, initial-scale=1
Link Tags
3- canonical<a href="bugreport.cgi?bug=1030586">1030586</a>
- icon/favicon.png
- stylesheet/css/bugs.css
Emails
8- [email protected]
- [email protected]
- [email protected]?In-Reply-To=%3C4P8nbD0yPYzHH%40c6.deuxchevaux.org%3E&body=On%20Sun%2C%20%205%20Feb%202023%2012%3A43%3A36%20%2B0100%20%28CET%29%20Axel%20Beckert%20%3Cabe%40debian.org%3E%20wrote%3A%0A%3E%20Package%3A%20lintian%0A%3E%20Version%3A%202.116.3%0A%3E%20Severity%3A%20important%0A%3E%20Tags%3A%20ftbfs%0A%3E%20%0A%3E%20While%20running%20Lintian%27s%20testsuite%20on%20a%20much%20faster%20system%20compared%20to%0A%3E%20my%20Sid%20amd64%20running%20development%20workstation%2C%20I%20noticed%20the%20following%0A%3E%20test%20suite%20failure%20when%20running%20%22private%2Fruntests%22%20or%20trying%20to%20build%0A%3E%20the%20package%20on%20a%20more%20modern%20and%20more%20performant%20box%20with%20Bookworm%0A%3E%20amd64.%20%28Use%20%22private%2Fruntests%20-o%20test%3Aancient-source%22%20to%20just%20run%20the%0A%3E%20affected%20test.%29%0A%3E%20%0A%3E%20%23%20Hints%20do%20not%20match%0A%3E%20%23%20%0A%3E%20%23%20---%20debian%2Ftest-out%2Feval%2Fchecks%2Funpack%2Fancient-source%2Fhints.specified.calibrated%0A%3E%20%23%20%2B%2B%2B%20debian%2Ftest-out%2Feval%2Fchecks%2Funpack%2Fancient-source%2Fhints.actual.parsed%0A%3E%20%23%20-ancient-source%20%28source%29%3A%20unpack-message-for-source%20tar%3A%20ancient-source-1.0%2FREADME%3A%20implausibly%20old%20time%20stamp%201969-12-31%2023%3A59%3A59%0A%3E%20%23%20%2Bancient-source%20%28source%29%3A%20unpack-message-for-source%20tar%3A%20ancient-source-1.0%2FREADME%3A%20implausibly%20old%20time%20stamp%201970-01-01%2000%3A59%3A59%0A%3E%20%23%20%0A%3E%20debian%2Ftest-out%2Feval%2Fchecks%2Funpack%2Fancient-source%2Fgeneric.t%20..%201%2F1%20%23%20%20%20Failed%20test%20%27Lintian%20passes%20for%20ancient-source%27%0A%3E%20%23%20%20%20at%20%2Fhome%2Fabe%2Fdebian%2Flintian%2Flib%2FTest%2FLintian%2FRun.pm%20line%20343.%0A%3E%20%23%20Looks%20like%20you%20failed%201%20test%20of%201.%0A%3E%20%0A%3E%20But%20I%20neither%20get%20that%20failure%20on%20my%20Sid%20amd64%20development%20workstation%0A%3E%20nor%20on%20SalsaCI%20%28https%3A%2F%2Fsalsa.debian.org%2Flintian%2Flintian%2F-%2Fpipelines%29%0A%3E%20nor%20in%20pbuilder%20nor%20on%20the%20buildd%0A%3E%20%28https%3A%2F%2Fbuildd.debian.org%2Fstatus%2Fpackage.php%3Fp%3Dlintian%29.%0A%3E%20%0A%3E%20So%20I%20tried%20to%20find%20differences.%0A%3E%20%0A%3E%20%24%20als%20debian%2Ftest-out%2Fpackages%2Fchecks%2Funpack%2Fancient-source%2Fancient-source_1.0.orig.tar.gz%20ancient-source-1.0%2FREADME%0A%3E%20-rw-r--r--%20root%2Froot%20%20%20%20%20%20%20%2021%201970-01-01%2000%3A59%20ancient-source-1.0%2FREADME%0A%3E%20%24%20env%20TZ%3DGMT%20als%20debian%2Ftest-out%2Fpackages%2Fchecks%2Funpack%2Fancient-source%2Fancient-source_1.0.orig.tar.gz%20ancient-source-1.0%2FREADME%0A%3E%20-rw-r--r--%20root%2Froot%20%20%20%20%20%20%20%2021%201969-12-31%2023%3A59%20ancient-source-1.0%2FREADME%0A%3E%20%0A%3E%20But%20these%20two%20outputs%20are%20identical%20on%20both%20hosts%2C%20the%20one%20where%20the%0A%3E%20test%20fails%20and%20one%20of%20those%20where%20it%20doesn%27t%20fail.%20%20So%20the%20timestamp%0A%3E%20actually%20seems%20to%20be%20the%20same%20and%20it%27s%20just%20Lintian%27s%20parsing%20of%20it%0A%3E%20seems%20to%20differ.%0A%3E%20%0A%3E%20The%20only%20potentially%20relevant%20package%20version%20difference%20I%20found%20was%0A%3E%20tar%2C%20which%20is%20at%201.34%2Bdfsg-1.1%20in%20Sid%20and%201.34%2Bdfsg-1%20in%20Bookworm%20due%0A%3E%20to%20a%20recent%20FTBFS%20on%2032-bit%20architectures.%20But%20the%20sole%20change%20was%20in%0A%3E%20debian%2Fcopyright%20and%20also%20downgrading%20the%20tar%20version%20in%20Sid%20to%20the%0A%3E%20one%20from%20Bookworm%20didn%27t%20make%20the%20test%20failing%20on%20Sid.%0A%3E%20%0A%3E%20Also%20running%20the%20test%20suite%20with%20%22env%20TZ%3DGMT%22%20prepended%20didn%27t%20make%20a%0A%3E%20difference.%0A%3E%20%0A%3E%20Additionally%2C%20build%202.116.2%20did%20work%20on%20that%20very%20same%20box%20where%0A%3E%202.116.3%20now%20FTBFS.%20So%20it%20seems%20to%20have%20caused%20been%20a%20recent%20change%0A%3E%20%28since%202023-01-29%29%20in%20Bookworm.%20Or%20maybe%20such%20a%20change%20just%20uncovered%0A%3E%20an%20older%20bug.%0A%3E%20%0A%3E%20The%20locales%20of%20two%20systems%20where%20it%20builds%20and%20where%20it%20no%20more%0A%3E%20builds%3A%0A%3E%20%0A%3E%20Builds%20fine%3A%0A%3E%20%0A%3E%20LANG%3DC.UTF-8%0A&subject=Re%3A%20lintian%3A%20Testsuite%20failure%20on%20some%20systems%3A%201h%20time%20offset%20in%20test%20ancient-source&References=%3C4P8nbD0yPYzHH%40c6.deuxchevaux.org%3E
- [email protected]?In-Reply-To=%3C87357kyrhf.fsf%40hope.eyrie.org%3E&subject=Re%3A%20Bug%231030586%3A%20lintian%3A%20Testsuite%20failure%20on%20some%20systems%3A%201h%0A%20time%20offset%20in%20test%20ancient-source&body=On%20Sun%2C%2005%20Feb%202023%2009%3A03%3A24%20-0800%20Russ%20Allbery%20%3Crra%40debian.org%3E%20wrote%3A%0A%3E%20Axel%20Beckert%20%3Cabe%40debian.org%3E%20writes%3A%0A%3E%20%0A%3E%20%3E%20While%20running%20Lintian%27s%20testsuite%20on%20a%20much%20faster%20system%20compared%20to%0A%3E%20%3E%20my%20Sid%20amd64%20running%20development%20workstation%2C%20I%20noticed%20the%20following%0A%3E%20%3E%20test%20suite%20failure%20when%20running%20%22private%2Fruntests%22%20or%20trying%20to%20build%0A%3E%20%3E%20the%20package%20on%20a%20more%20modern%20and%20more%20performant%20box%20with%20Bookworm%0A%3E%20%3E%20amd64.%20%28Use%20%22private%2Fruntests%20-o%20test%3Aancient-source%22%20to%20just%20run%20the%0A%3E%20%3E%20affected%20test.%29%0A%3E%20%0A%3E%20%3E%20%23%20Hints%20do%20not%20match%0A%3E%20%3E%20%23%20%0A%3E%20%3E%20%23%20---%20debian%2Ftest-out%2Feval%2Fchecks%2Funpack%2Fancient-source%2Fhints.specified.calibrated%0A%3E%20%3E%20%23%20%2B%2B%2B%20debian%2Ftest-out%2Feval%2Fchecks%2Funpack%2Fancient-source%2Fhints.actual.parsed%0A%3E%20%3E%20%23%20-ancient-source%20%28source%29%3A%20unpack-message-for-source%20tar%3A%20ancient-source-1.0%2FREADME%3A%20implausibly%20old%20time%20stamp%201969-12-31%2023%3A59%3A59%0A%3E%20%3E%20%23%20%2Bancient-source%20%28source%29%3A%20unpack-message-for-source%20tar%3A%20ancient-source-1.0%2FREADME%3A%20implausibly%20old%20time%20stamp%201970-01-01%2000%3A59%3A59%0A%3E%20%0A%3E%20The%20exactly%20one%20hour%20difference%20makes%20me%20suspicious%20something%20is%20going%20on%0A%3E%20with%20time%20zone%20conversions.%20%20That%27s%20also%20consistent%20with%20the%20one%20hour%20time%0A%3E%20difference%20between%20UTC%20and%20Europe%2FZurich%20at%20New%20Years.%0A%3E%20%0A%3E%20Looking%20at%20the%20source%20of%20tar%2C%20the%20output%20timestamp%20for%20this%20error%20seems%20to%0A%3E%20be%20in%20local%20time%20by%20default%2C%20which%20would%20certainly%20explain%20the%20problem%20but%0A%3E%20not%20why%20we%27re%20not%20seeing%20it%20everywhere.%20%20I%20would%20be%20curious%20if%20it%20went%0A%3E%20away%20if%20you%20added%20--utc%20to%20the%20flags%20to%20tar%20in%0A%3E%20Lintian%3A%3AIO%3A%3ASelect%3A%3Aunpack_and_index_piped_tar%20or%20%28bigger%20hammer%29%20just%0A%3E%20set%20TZ%3DUTC%20when%20running%20Lintian.%0A%3E%20%0A%3E%20Lintian%20should%20probably%20force%20all%20output%20it%20controls%20to%20UTC%20for%0A%3E%20reproducibility%2C%20including%20tar%27s%2C%20but%20I%27m%20still%20mystified%20as%20to%20why%20it%0A%3E%20works%20on%20the%20other%20system.%20%20This%20part%20of%20tar%20doesn%27t%20seem%20to%20have%20changed%2C%0A%3E%20and%20as%20you%20mentioned%20replacing%20tar%20didn%27t%20change%20anything.%0A%3E%20%0A%3E%20--%20%0A%3E%20Russ%20Allbery%20%28rra%40debian.org%29%20%20%20%20%20%20%20%20%20%20%20%20%20%20%3Chttps%3A%2F%2Fwww.eyrie.org%2F~eagle%2F%3E%0A%3E%20%0A%3E%20%0A&References=%3C4P8nbD0yPYzHH%40c6.deuxchevaux.org%3E%0A%20%3C87357kyrhf.fsf%40hope.eyrie.org%3E
- [email protected]?In-Reply-To=%3C87edr3yho7.fsf%40yucca%3E&References=%3C4P8nbD0yPYzHH%40c6.deuxchevaux.org%3E%0A%20%3C87edr3yho7.fsf%40yucca%3E&subject=Re%3A%20Bug%231030586%3A%20lintian%3A%20Testsuite%20failure%20on%20some%20systems%3A%201h%0A%20time%20offset%20in%20test%20ancient-source&body=On%20Sun%2C%2005%20Feb%202023%2012%3A35%3A20%20-0800%20Vagrant%20Cascadian%20%3Cvagrant%40reproducible-builds.org%3E%20wrote%3A%0A%3E%20On%202023-02-05%2C%20Axel%20Beckert%20wrote%3A%0A%3E%20%3E%20While%20running%20Lintian%27s%20testsuite%20on%20a%20much%20faster%20system%20compared%20to%0A%3E%20%3E%20my%20Sid%20amd64%20running%20development%20workstation%2C%20I%20noticed%20the%20following%0A%3E%20%3E%20test%20suite%20failure%20when%20running%20%22private%2Fruntests%22%20or%20trying%20to%20build%0A%3E%20%3E%20the%20package%20on%20a%20more%20modern%20and%20more%20performant%20box%20with%20Bookworm%0A%3E%20%3E%20amd64.%20%28Use%20%22private%2Fruntests%20-o%20test%3Aancient-source%22%20to%20just%20run%20the%0A%3E%20%3E%20affected%20test.%29%0A%3E%20%3E%0A%3E%20%3E%20%23%20Hints%20do%20not%20match%0A%3E%20%3E%20%23%20%0A%3E%20%3E%20%23%20---%20debian%2Ftest-out%2Feval%2Fchecks%2Funpack%2Fancient-source%2Fhints.specified.calibrated%0A%3E%20%3E%20%23%20%2B%2B%2B%20debian%2Ftest-out%2Feval%2Fchecks%2Funpack%2Fancient-source%2Fhints.actual.parsed%0A%3E%20%3E%20%23%20-ancient-source%20%28source%29%3A%20unpack-message-for-source%20tar%3A%20ancient-source-1.0%2FREADME%3A%20implausibly%20old%20time%20stamp%201969-12-31%2023%3A59%3A59%0A%3E%20%3E%20%23%20%2Bancient-source%20%28source%29%3A%20unpack-message-for-source%20tar%3A%20ancient-source-1.0%2FREADME%3A%20implausibly%20old%20time%20stamp%201970-01-01%2000%3A59%3A59%0A%3E%20%0A%3E%20Wild%20guess%20would%20be%20timezone%20differences%20between%20the%20build%20environments%3F%0A%3E%20%0A%3E%20live%20well%2C%0A%3E%20%20%20vagrant%0A%3E%20%0A%3E%20%0A
Links
10- https://bugs.debian.org/cgi-bin/bugspam.cgi?bug=1030586
- https://bugs.debian.org/debbugs-source
- https://buildd.debian.org/lintian
- https://buildd.debian.org/status/package.php?p=lintian
- https://people.debian.org/~abe