Hi,
regarding your analysis: I think you could just scan the .changes files
as they list all *.deb files uploaded. Though very old changes only
have MD5 hashes.
They can be found in
file://mirror.ftp-master.debian.org/srv/ftp-master.debian.org/queue/done
Regarding your observation regarding bash
Hi,
On Thu, 2025-04-03 at 00:25 +0200, Johannes Schauer Marin Rodrigues wrote:
> Quoting Ansgar 🙀 (2025-04-02 21:41:39)
> > regarding your analysis: I think you could just scan the .changes files as
> > they list all *.deb files uploaded.> Though very old changes only have MD5
> > hashes.
> >
>
Hi Ansgar,
thank you for chiming in!
Quoting Ansgar 🙀 (2025-04-02 21:41:39)
> regarding your analysis: I think you could just scan the .changes files as
> they list all *.deb files uploaded.> Though very old changes only have MD5
> hashes.
>
> They can be found in
> file://mirror.ftp-master.debi
Hi,
On Thu, 30 May 2024 14:26:31 + Holger Levsen wrote:
> very "nice" find, josch!
with the help of Holger and osuosl4 I have dug into this a bit more and tried
to get some hard data about this problem. My idea was the following: parse all
Packages files for all suites, all architectures and
Hi,
very "nice" find, josch!
On Thu, May 30, 2024 at 11:16:48AM +0200, Johannes Schauer Marin Rodrigues
wrote:
> This example with bash is especially problematic since bash is Essential:yes
> so
> there will now be a large portion of buildinfo files where it is not possible
> to figure out with
Package: ftp.debian.org
Severity: normal
X-Debbugs-Cc: reproducible-b...@lists.alioth.debian.org
User: reproducible-bui...@lists.alioth.debian.org
Usertags: infrastructure
User: ftp.debian@packages.debian.org
Usertags: dak
Hi,
the binary package bash 5.2.15-2+b3 was uploaded to the archive tw
6 matches
Mail list logo
