Processed: Re: Bug#898022: diffoscope: Traceback when comparing paths with invalid unicode characters

Processing control commands: > clone -1 -2 Bug #898022 [diffoscope] diffoscope: Traceback when comparing paths with invalid unicode characters Bug 898022 cloned as bug 898361 > tag -2 - patch Bug #898361 [diffoscope] diffoscope: Traceback when comparing paths with invalid unicode characters Remo

Bug#898022: diffoscope: Traceback when comparing paths with invalid unicode characters

Control: clone -1 -2 Control: tag -2 - patch Control: severity -2 wishlist Control: retitle -2 diffoscope: should handle the filenames as bytes On Thu, May 10, 2018 at 06:01:50PM +0200, Mattia Rizzolo wrote: > I believe that, like that bug is showing, we should just specify > type=os.fsencode

Bug#898022: diffoscope: Traceback when comparing paths with invalid unicode characters

Hi Mattia, > That was my initial idea as well, but apparently the Python developers > are of different opinion. Check out the PEP I linked in my previous > email: https://www.python.org/dev/peps/pep-0383/ Ah, thanks I merely skimmed this one and not the the issue. Hey, the Python developers coul

Bug#898022: diffoscope: Traceback when comparing paths with invalid unicode characters

On Thu, May 10, 2018 at 04:43:37PM +0100, Chris Lamb wrote: > > Do you think this would be fine? > > Whilst this works, would it not be better if we could use bytes for > filenames throughout? I mean, AIUI there is no assumption that > filesystems need to have any form of valid encoding whatsoever

Bug#898022: diffoscope: Traceback when comparing paths with invalid unicode characters

Hi Mattia, > That's because argparse decodes the arguments Ahh! Nice spot. > Do you think this would be fine? Whilst this works, would it not be better if we could use bytes for filenames throughout? I mean, AIUI there is no assumption that filesystems need to have any form of valid encoding wh

Bug#898022: diffoscope: Traceback when comparing paths with invalid unicode characters

Control: tag -1 patch On Sun, May 06, 2018 at 01:38:58AM +0100, Chris Lamb wrote: > This is via , but I > think the bug is in diffoscope itself. It is, although one could say it's a bug in argparse. > However, I can't seem to minimally reproduce

Processed: Re: Bug#898022: diffoscope: Traceback when comparing paths with invalid unicode characters

Processing control commands: > tag -1 patch Bug #898022 [diffoscope] diffoscope: Traceback when comparing paths with invalid unicode characters Added tag(s) patch. -- 898022: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=898022 Debian Bug Tracking System Contact ow...@bugs.debian.org with p

diffoscope_94~bpo9+1_source.changes ACCEPTED into stretch-backports

Accepted: -BEGIN PGP SIGNED MESSAGE- Hash: SHA512 Format: 1.8 Date: Thu, 10 May 2018 16:21:30 +0200 Source: diffoscope Binary: diffoscope Architecture: source Version: 94~bpo9+1 Distribution: stretch-backports Urgency: medium Maintainer: Reproducible builds folks Changed-By: Mattia Ri

Processed: Re: Bug#855273: diffoscope: fails to clean up after SIGTERM

Processing control commands: > close -1 Bug #855273 [diffoscope] diffoscope: fails to clean up after SIGTERM Marked Bug as done -- 855273: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=855273 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems

Bug#855273: diffoscope: fails to clean up after SIGTERM

Control: close -1 On Tue, Dec 05, 2017 at 06:55:02AM +0900, Chris Lamb wrote: > > > diffoscope: still fails to clean up after SIGTERM > > > > Can we reproduce this outside of Jenkins? Would really love a testcase > > so I can my teeth into this... > > Ping on this, Mattia? Would be great to eith

Processing of diffoscope_94~bpo9+1_source.changes

diffoscope_94~bpo9+1_source.changes uploaded successfully to localhost along with the files: diffoscope_94~bpo9+1.dsc diffoscope_94~bpo9+1.tar.xz diffoscope_94~bpo9+1_amd64.buildinfo Greetings, Your Debian queue daemon (running on host usper.debian.org)

Bug#898287: disorderfs: inodes returned by getdents are all the same value

tags 898287 + pending thanks Fixed in Git, with testcase.. Now ending upload: https://anonscm.debian.org/git/reproducible/disorderfs.git/commit/?id=39e29c4ef96319a4c716832a73ad5fd62ed9ff75 disorderfs.cpp | 13 + tests/inodes | 87 ++

Processed: Re: disorderfs: inodes returned by getdents are all the same value

Processing commands for cont...@bugs.debian.org: > tags 898287 + pending Bug #898287 [disorderfs] disorderfs: inodes returned by getdents are all the same value Added tag(s) pending. > thanks Stopping processing here. Please contact me if you need assistance. -- 898287: https://bugs.debian.org/

Bug#898287: Subject: disorderfs inode on getdents

Hello, I'm currently leading a research project on deterministic execution of programs. We're developing a tool to enforce determinism dynamically on arbitrary code. Inodes are a easy way to uniquely identify files within our execution, so our runtime virtualizes inodes by mapping them to unique d