Chris Lamb writes:
> Other work that can be done in the meantime include improving our
> triage scripts -- I still have a half-draft of the "renamed packages"
> script, for example.
>
> IIRC I believe the subject to search for is "Improvement needed to our
> triaging scripts".
Ok, if I understand
Chris Lamb writes:
> Other work that can be done in the meantime include improving our
> triage scripts -- I still have a half-draft of the "renamed packages"
> script, for example.
>
> IIRC I believe the subject to search for is "Improvement needed to our
> triaging scripts".
Is there a list of
On Thu, Jun 07, 2018 at 06:07:24PM -0400, Antoine Beaupré wrote:
> Sorry for resurrecting this old thread…
No!
I very much appreciate it when people keep issues in the back of their minds
and keep thinking about them and keep reminding us "others" until they are
solved properly!
Thank you.
:)
Sorry for resurrecting this old thread, but I've been looking at how to
deal with renamed packages in CVE triaging again. When we last talked
about this, we observed how we were sometimes missing packages during
triage, e.g. `tiff3` that was present in wheezy. That's not an issue
anymore since whee
Hi Antoine,
> >> I'm not sure how that avoids duplicate work. Just writing to the BTS
> >> does not make it very explicit that we're working on the package, unless
> >> we explicitly say so ("hi, i'm working on this")
> >
> > I think you missed the bit where I wrote "Quasi 'claim' them by
> > writ
On 2018-06-07 16:38:21, Chris Lamb wrote:
> Hi Antoine,
>
>> I'm not sure how that avoids duplicate work. Just writing to the BTS
>> does not make it very explicit that we're working on the package, unles
>> we explicitely say so ("hi, i'm working on this")
>
> I think you missed the bit where I w
On Thu, Jun 07, 2018 at 08:08:06AM -0400, Antoine Beaupré wrote:
> On 2018-06-07 04:45:06, Chris Lamb wrote:
> > Hi Antoine,
> >
> >> A peculiar thing with the patchset is that it adds the --debug flag to
> >> the test suite: I don't know why, but it's the only way to make it pass
> >> the (new) te
Hi Antoine,
> I'm not sure how that avoids duplicate work. Just writing to the BTS
> does not make it very explicit that we're working on the package, unles
> we explicitely say so ("hi, i'm working on this")
I think you missed the bit where I wrote "Quasi 'claim' them by
writing to the aforemen
On 2018-06-07 15:42:17, Chris Lamb wrote:
> Hi Antoine et al.,
>
>> After staring at that thing and trying to deal with a few of those, I am
>> a little unsure how to actually coordinate this work for now.
>
> I agree that that foo-needed.txt files are a little confusing right
> now. :)
>
> To ensu
Hi,
Am 07.06.2018 um 20:58 schrieb Antoine Beaupré:
[...]
> * graphicsmagick (~50+ CVEs): apo will handle this with his LTS hat on
>if it can't be done before the transition
[...]
I have already sent an update to the security team but it is still
pending review and ACK. As you said I intend
Hi Antoine et al.,
> After staring at that thing and trying to deal with a few of those, I am
> a little unsure how to actually coordinate this work for now.
I agree that that foo-needed.txt files are a little confusing right
now. :)
To ensure no duplicated work in the next week (or at least to
On 2018-06-06 11:05:28, Antoine Beaupré wrote:
> Here is the current output:
After staring at that thing and trying to deal with a few of those, I am
a little unsure how to actually coordinate this work for now. All this
will be resolved within a week or two when jessie transitions over to
the LTS
On 2018-06-07 09:36:29, Antoine Beaupré wrote:
> Oh, and for what it's worth, I've also uploaded the (successful) build
> log here:
>
> https://people.debian.org/~anarcat/debian/jessie-lts/mercurial_3.1.2-2+deb8u5_amd64-2018-06-07T00:41:12Z.build
>
> Warning: that is about 5MB of logs.
I've also p
On 2018-06-07 11:23:45, Didier 'OdyX' Raboud wrote:
> Le jeudi, 7 juin 2018, 16.13:39 h CEST Antoine Beaupré a écrit :
>> Hi again,
>>
>> Next in line: cups. Two fairly simple patches and this time the test
>> suite passes without a fuss, provided that the local hostname resolves
>> within the chr
Le jeudi, 7 juin 2018, 16.13:39 h CEST Antoine Beaupré a écrit :
> Hi again,
>
> Next in line: cups. Two fairly simple patches and this time the test
> suite passes without a fuss, provided that the local hostname resolves
> within the chroot. ;)
Excellent, thanks for caring about CUPS in oldolds
Hi again,
Next in line: cups. Two fairly simple patches and this time the test
suite passes without a fuss, provided that the local hostname resolves
within the chroot. ;)
Packages, as usual, are available here, signed by me:
https://people.debian.org/~anarcat/debian/jessie-lts/
Debdiff also av
Oh, and for what it's worth, I've also uploaded the (successful) build
log here:
https://people.debian.org/~anarcat/debian/jessie-lts/mercurial_3.1.2-2+deb8u5_amd64-2018-06-07T00:41:12Z.build
Warning: that is about 5MB of logs.
a.
--
The history of any one part of the earth, like the life of a
On 2018-06-07 04:45:06, Chris Lamb wrote:
> Hi Antoine,
>
>> A peculiar thing with the patchset is that it adds the --debug flag to
>> the test suite: I don't know why, but it's the only way to make it pass
>> the (new) test-http-permissions.t tests. Otherwise it just hangs there
>> forever.
>
> Pe
Hi Antoine,
> A peculiar thing with the patchset is that it adds the --debug flag to
> the test suite: I don't know why, but it's the only way to make it pass
> the (new) test-http-permissions.t tests. Otherwise it just hangs there
> forever.
Personally, it would make me very very hesitant to pro
19 matches
Mail list logo
