Re: Joliet name length in amd64 netinst versus DVD-2

Hi, Steve McIntyre wrote: > Fixing it right now, thanks for the clear report! I did not want to open a bug without knowing more background. As you are in fixing mode, could you please look whether https://bugs.debia

Re: cdbuilder log files moved

Hi, Steve McIntyre wrote: > I think you're the main person who might be using the logs published > from cdbuilder. I did not even know that such logs exist. > https://cdbuilder-logs.debian.org/ Ahum. What's the meaning of the number prefixes of the file names ? ("3sidamd64", "4amd64") I alway

Scheduling 9.4

Hi, we shipped 9.3 a couple of months ago, so we're overdue for 9.4. Can you please let us know your availability on the following: - March 3 - March 10 - March 17 - March 24 - March 31 Thanks, Julien signature.asc Description: PGP signature

Re: Scheduling 9.4

On Sat, Feb 10, 2018 at 12:27:43PM +0100, Julien Cristau wrote: >Hi, > >we shipped 9.3 a couple of months ago, so we're overdue for 9.4. > >Can you please let us know your availability on the following: >- March 3 >- March 10 Both doable for me. >- March 17 >- March 24 I'm away at a conference 1

Re: Joliet name length in amd64 netinst versus DVD-2

Hi, looking at https://salsa.debian.org/images-team/debian-cd/commit/6112370e0abf29018a5346467aaf27cf7cb8ba91 "Ensure that in all places where we use -J we also use --joliet-long" i wonder whether it is wise to rely on the undocumented double-dash tolerance of xorrisofs and genisoimage. Bo

Re: Joliet name length in amd64 netinst versus DVD-2

On Sat, Feb 10, 2018 at 12:58:55PM +0100, Thomas Schmitt wrote: >Hi, > >looking at > > > https://salsa.debian.org/images-team/debian-cd/commit/6112370e0abf29018a5346467aaf27cf7cb8ba91 > "Ensure that in all places where we use -J we also use --joliet-long" > >i wonder whether it is wise to rely

Re: Joliet name length in amd64 netinst versus DVD-2

Hi, Steve McIntyre wrote: > I've got too used to the relaxed handling in xorriso. IIRC the tolerance of xorrisofs exists because genisoimage and mkisofs show it. It's contageous and each adoption possibly widens it. E.g. i did not check whether genisoimage refuses on some double-dash options but

magnet links and pushing them to meta-search engines.

Dear Friends, >From the last few days/week I have been poking around torrent meta-search engines, While looking through, I noticed that the sometimes (not all the times) there have been occasions where the hashes have told to be a virus. Most recent example is https://torrentz2.eu/1193adc8d620b0e