Hi Vagrant,
>
> https://pad.sfconservancy.org/p/-NUkgkGAezz0wc7n54el
>
> Feel free to comment or even edit directly.
Thanks. The only substantive change I made was to add a paragraph
regarding packages that filter -fdebug-prefix-map from CFLAGS but
don't do this for -ffile-prefix-map. These will
On 2020-10-26, Vagrant Cascadian wrote:
> On 2020-10-22, Chris Lamb wrote:
>> Guillem (and all the other dpkg folks), do you see any impediment to
>> raising the question of enabling fixfilepath by default with the
>> Debian community at large?
>>
>>> All of the patches I submitted were merely disa
On 2020-10-22, Chris Lamb wrote:
> Guillem (and all the other dpkg folks), do you see any impediment to
> raising the question of enabling fixfilepath by default with the
> Debian community at large?
>
>> All of the patches I submitted were merely disable fixfilepath, though
>> they could all use f
[moving Lucas to BCC]
Hi Guillem,
> I don't see either an issue with whether the bugs have been filed or
> not, but I think that's just part of the conversation with
> debian-devel at large (which I doubt would be a matter of contention
> there either).
Judging by some emails flying past my inbo
Hi!
On Thu, 2020-10-22 at 22:58:02 -, Chris Lamb wrote:
> Guillem (and all the other dpkg folks), do you see any impediment to
> raising the question of enabling fixfilepath by default with the
> Debian community at large?
Sorry, had pending a reply to this but was caught up with other stuff.
Hi all,
Guillem (and all the other dpkg folks), do you see any impediment to
raising the question of enabling fixfilepath by default with the
Debian community at large?
> All of the patches I submitted were merely disable fixfilepath, though
> they could all use further exploration to find the ro
On 2020-10-15, Vagrant Cascadian wrote:
> On 2020-10-15, Chris Lamb wrote:
>>> At a quick glance, looks to be 33 packages, many of which were already
>>> identified in by our tags:
>>>
>>> https://tests.reproducible-builds.org/debian/issues/unstable/ftbfs_due_to_f-file-prefix-map_issue.html
>>> htt
On 2020-10-15, Chris Lamb wrote:
>> At a quick glance, looks to be 33 packages, many of which were already
>> identified in by our tags:
>>
>> https://tests.reproducible-builds.org/debian/issues/unstable/ftbfs_due_to_f-file-prefix-map_issue.html
>> https://tests.reproducible-builds.org/debian/issue
Hi all,
> At a quick glance, looks to be 33 packages, many of which were already
> identified in by our tags:
>
> https://tests.reproducible-builds.org/debian/issues/unstable/ftbfs_due_to_f-file-prefix-map_issue.html
> https://tests.reproducible-builds.org/debian/issues/unstable/ffile_prefix_map_p
On 2020-09-27, Lucas Nussbaum wrote:
> On 07/09/20 at 20:42 -0700, Vagrant Cascadian wrote:
>> On 2020-08-31, Lucas Nussbaum wrote:
>> > On 31/08/20 at 09:35 -0700, Vagrant Cascadian wrote:
>> >> On 2020-08-31, Lucas Nussbaum wrote:
>> >> > On 30/08/20 at 19:15 -0700, Vagrant Cascadian wrote:
>> >>
On 27/09/20 at 18:37 +0200, Lucas Nussbaum wrote:
> Hi,
>
> On 07/09/20 at 20:42 -0700, Vagrant Cascadian wrote:
> > On 2020-08-31, Lucas Nussbaum wrote:
> > > On 31/08/20 at 09:35 -0700, Vagrant Cascadian wrote:
> > >> On 2020-08-31, Lucas Nussbaum wrote:
> > >> > On 30/08/20 at 19:15 -0700, Vagr
Hi,
On 07/09/20 at 20:42 -0700, Vagrant Cascadian wrote:
> On 2020-08-31, Lucas Nussbaum wrote:
> > On 31/08/20 at 09:35 -0700, Vagrant Cascadian wrote:
> >> On 2020-08-31, Lucas Nussbaum wrote:
> >> > On 30/08/20 at 19:15 -0700, Vagrant Cascadian wrote:
> >> >> I'm looking into proposing to enabl
Hi,
On 23/09/20 at 14:39 +0100, Chris Lamb wrote:
> Vagrant Cascadian wrote:
>
> > Proposed merge request adding a script that does just that:
> >
> > https://salsa.debian.org/lucas/collab-qa-tools/-/merge_requests/9
>
> 2+ weeks on, any update on this? I keep coming across packages that
> wo
Vagrant Cascadian wrote:
> Proposed merge request adding a script that does just that:
>
> https://salsa.debian.org/lucas/collab-qa-tools/-/merge_requests/9
2+ weeks on, any update on this? I keep coming across packages that
would be fixed by fixfilepath.
--
o
⬋ ⬊ Chris Lam
On 2020-08-31, Lucas Nussbaum wrote:
> On 31/08/20 at 09:35 -0700, Vagrant Cascadian wrote:
>> On 2020-08-31, Lucas Nussbaum wrote:
>> > On 30/08/20 at 19:15 -0700, Vagrant Cascadian wrote:
>> >> I'm looking into proposing to enable dpkg's
>> >> DEB_BUILD_OPTIONS=reproducible=+fixfilepath by defaul
On Mon, Aug 31, 2020 at 09:35:52AM -0700, Vagrant Cascadian wrote:
> > Could you provide a dpkg package in a private repo (or in experimental)
> > with that enabled by default? And ideally a script similar to
> > https://salsa.debian.org/lucas/collab-qa-tools/-/blob/master/modes/gcc10
> > to instal
On 2020-08-31, Lucas Nussbaum wrote:
> On 31/08/20 at 09:35 -0700, Vagrant Cascadian wrote:
>> On 2020-08-31, Lucas Nussbaum wrote:
>> > On 30/08/20 at 19:15 -0700, Vagrant Cascadian wrote:
>> >> I've appreciated all the work you've been doing with archive-wide
>> >> rebuilds of Debian over the yea
On 31/08/20 at 09:35 -0700, Vagrant Cascadian wrote:
> Thanks for the quick response! More in-line below.
>
> On 2020-08-31, Lucas Nussbaum wrote:
> > On 30/08/20 at 19:15 -0700, Vagrant Cascadian wrote:
> >> I've appreciated all the work you've been doing with archive-wide
> >> rebuilds of Debian
Thanks for the quick response! More in-line below.
On 2020-08-31, Lucas Nussbaum wrote:
> On 30/08/20 at 19:15 -0700, Vagrant Cascadian wrote:
>> I've appreciated all the work you've been doing with archive-wide
>> rebuilds of Debian over the years!
>>
>> I'm looking into proposing to enable dpkg
Hi Vagrant,
On 30/08/20 at 19:15 -0700, Vagrant Cascadian wrote:
> Hi Lucas!
>
> I've appreciated all the work you've been doing with archive-wide
> rebuilds of Debian over the years!
>
> I'm looking into proposing to enable dpkg's
> DEB_BUILD_OPTIONS=reproducible=+fixfilepath by default, furthe
Hi Lucas!
I've appreciated all the work you've been doing with archive-wide
rebuilds of Debian over the years!
I'm looking into proposing to enable dpkg's
DEB_BUILD_OPTIONS=reproducible=+fixfilepath by default, further
background in this thread:
https://alioth-lists.debian.net/pipermail/repro
On Mon, Jun 22, 2020 at 05:04:54PM -0700, Vagrant Cascadian wrote:
> On 2020-06-17, Holger Levsen wrote:
> > interesting findings!
> >
> > On Tue, Jun 16, 2020 at 10:03:24PM -0700, Vagrant Cascadian wrote:
> >> > Many of them appear to go from FTBFS to reproducible, FWIW.
> >
> > nice. what is your
On 2020-06-17, Holger Levsen wrote:
> interesting findings!
>
> On Tue, Jun 16, 2020 at 10:03:24PM -0700, Vagrant Cascadian wrote:
>> > Many of them appear to go from FTBFS to reproducible, FWIW.
>
> nice. what is your general recommendation/plan for the next action item here?
Well, the FTBFS woul
Hi Vagrant,
interesting findings!
On Tue, Jun 16, 2020 at 10:03:24PM -0700, Vagrant Cascadian wrote:
> > Many of them appear to go from FTBFS to reproducible, FWIW.
nice. what is your general recommendation/plan for the next action item here?
> The packages that seem to have been "fixed" were r
On 2020-06-16, Vagrant Cascadian wrote:
> On 2020-06-13, Holger Levsen wrote:
>> On Fri, Jun 12, 2020 at 02:27:50PM -0700, Vagrant Cascadian wrote:
> We've got some updated numbers now!
>
> unstable (with reproducible=+all):
>
> 15 FTBFS packages in unstable/amd64:
>
> analitza firmware-micr
On 2020-06-13, Holger Levsen wrote:
> On Fri, Jun 12, 2020 at 02:27:50PM -0700, Vagrant Cascadian wrote:
>> I've pushed to git:
>>
>> https://salsa.debian.org/qa/jenkins.debian.net/-/commit/f2a447eacfe375951476f369c8b61f02891d97c7
>
> cool, thanks.
>
>> Refreshing my memory on how to deploy it
On Fri, Jun 12, 2020 at 02:27:50PM -0700, Vagrant Cascadian wrote:
> I've pushed to git:
>
> https://salsa.debian.org/qa/jenkins.debian.net/-/commit/f2a447eacfe375951476f369c8b61f02891d97c7
cool, thanks.
> Refreshing my memory on how to deploy it by reading the docs... once
> that's done, we
On 2020-06-10, Holger Levsen wrote:
> On Sat, Jun 06, 2020 at 03:21:06PM -0700, Vagrant Cascadian wrote:
>> We'd be able to get more accurate data if we remove the flag for
>> bullseye and manually schedule all of those packages, at least
>> temporarily... anyone have concerns with doing that and w
Hi,
I'm very glad to see this moving forward!
On Sat, Jun 06, 2020 at 03:21:06PM -0700, Vagrant Cascadian wrote:
> We'd be able to get more accurate data if we remove the flag for
> bullseye and manually schedule all of those packages, at least
> temporarily... anyone have concerns with doing tha
On 2020-06-03, Vagrant Cascadian wrote:
> On 2020-06-03, Benjamin Barenblat wrote:
>> Related discussion [2] concluded that the option
>> should be disabled by default and enabled after Reproducible Builds had
>> trialed it for a while. Having enabled it in some of my recent
>> packaging, I’m curio
Hi Guillem,
> > I recall this thread where it broke test suites of some packages:
> >
> >
> > https://alioth-lists.debian.net/pipermail/reproducible-builds/Week-of-Mon-20190204/011101.html
>
> But I assume this would have been detected while building?
It would have been detected during build,
Hi!
On Wed, 2020-06-03 at 11:59:32 -0700, Vagrant Cascadian wrote:
> On 2020-06-03, Benjamin Barenblat wrote:
> > Related discussion [2] concluded that the option
> > should be disabled by default and enabled after Reproducible Builds had
> > trialed it for a while. Having enabled it in some of my
Vagrant Cascadian wrote:
> I believe maintainers can override this flag in their packages if
> needed? If so, I'd be inclined to explore setting it by default!
I would be very much in favour of enabling this at the earliest
opportunity.
Regarding maintainer control over this I have two remarks t
On 2020-06-03, Benjamin Barenblat wrote:
> About two years ago, Guillem Jover added support for -ffile-prefix-map
> to dpkg [1] (thanks!).
Wow, hard to believe that was nearly two years ago!
Thanks for bringing this up!
> Related discussion [2] concluded that the option
> should be disabled by
34 matches
Mail list logo
