Bug#881937: diffoscope: Doesn't show differences in .deb's control.tar.xz (regression?)

2017-11-16 Thread Axel Beckert
Package: diffoscope Version: 88 Severity: normal Control: found -1 78 Hi, when comparing the two attached .deb files with diffoscope, it doesn't show any differences inside the control.data.xz, despite it shows a different size of the two control.data.xz members: --- ../aptitude-robot_1.5.2-1_al

Processed: diffoscope: Doesn't show differences in .deb's control.tar.xz (regression?)

2017-11-16 Thread Debian Bug Tracking System
Processing control commands: > found -1 78 Bug #881937 [diffoscope] diffoscope: Doesn't show differences in .deb's control.tar.xz (regression?) Marked as found in versions diffoscope/78. -- 881937: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=881937 Debian Bug Tracking System Contact ow...

Re: Bug#876901: QFINDTESTDATA uses __FILE__

2017-11-16 Thread Lisandro Damián Nicanor Pérez Meyer
On jueves, 16 de noviembre de 2017 13:22:00 -03 Ximin Luo wrote: [snip] > I pointed to the various C standards documents, as well as documentation > from multiple compilers, stating that __FILE__ is the "name of the source > file" and in no way guarantees that the expansion can later be re-used as

Re: Bug#876901: QFINDTESTDATA uses __FILE__

2017-11-16 Thread Ximin Luo
Lisandro Damián Nicanor Pérez Meyer: > By the way: is there a macro or combination of macros which *default* value > can be replaced in the use of __FILE__ without caussing regressions? > > Because if that's the case it's easier to convince upstream people that > changing the usage goes in favor

Re: Bug#876901: QFINDTESTDATA uses __FILE__

2017-11-16 Thread Ximin Luo
Lisandro Damián Nicanor Pérez Meyer: > [..] > > Yes, we do understand that your workaround solves the issue, but we do also > understand that we should not be using this workaround in the first place. > > Guillem: the thread is long, but be sure that we Qt/KDE maintainers consider > that this c

Re: Bug#876901: QFINDTESTDATA uses __FILE__

2017-11-16 Thread Lisandro Damián Nicanor Pérez Meyer
By the way: is there a macro or combination of macros which *default* value can be replaced in the use of __FILE__ without caussing regressions? Because if that's the case it's easier to convince upstream people that changing the usage goes in favor of reproducibility without using strange up- t

Re: Bug#876901: QFINDTESTDATA uses __FILE__

2017-11-16 Thread Lisandro Damián Nicanor Pérez Meyer
Explicitely CCing Guillem for this one. On miércoles, 15 de noviembre de 2017 23:01:00 -03 Ximin Luo wrote: [sip] > The GCC patch (neither the previous nor the planned version) does not change > the default behaviour of __FILE__, and was never intended to. Instead, it > gives users the ability to

Re: Please review the draft for week 133's blog post

2017-11-16 Thread Holger Levsen
On Thu, Nov 16, 2017 at 10:06:00AM +, Ximin Luo wrote: > Ping, are you ready? I don't see any commits from you in the log... not yet & on a very bad internet connection atm. i will publish 133 once it's ready. thanks. -- cheers, Holger signature.asc Description: PGP signature __

Re: Please review the draft for week 133's blog post

2017-11-16 Thread Ximin Luo
Holger Levsen: > On Tue, Nov 14, 2017 at 01:34:00PM +, Ximin Luo wrote: >> This week's blog post draft is now available for review: >> https://reproducible.alioth.debian.org/blog/drafts/133/ > [...] >> I'll wait at least 24 hours from the time of this email for any comments, >> and if everyth