Hi Robert,
On 23/08/13 14:26, Aurelien Jarno via RT wrote:
> The debdiff looks fine to me. Could you please upload the resulting
> package for either ki or ka to security-master? I'll handle the
> remaining part of the DSA when possible.
Would you be able to upload to security-master with the att
On 04/08/13 17:32, Robert Millan wrote:
> 2013/8/4 Steven Chamberlain :
>> How do I cause the NEWS entry to be displayed/emailed to the user on
>> package upgrade?
> [...]
> This is a user-side setting: Install apt-listchanges. I think that's all.
Aha! I was testing it in only a minimal chroot wh
2013/8/4 Steven Chamberlain :
> How do I cause the NEWS entry to be displayed/emailed to the user on
> package upgrade?
>
> With what I committed to SVN, the file is being installed as
> /usr/share/doc/kfreebsd-image-9.0-2-amd64/NEWS.Debian.gz only.
Hi Steven,
This is a user-side setting: Install
How do I cause the NEWS entry to be displayed/emailed to the user on
package upgrade?
With what I committed to SVN, the file is being installed as
/usr/share/doc/kfreebsd-image-9.0-2-amd64/NEWS.Debian.gz only.
Thanks,
Regards,
--
Steven Chamberlain
ste...@pyro.eu.org
--
To UNSUBSCRIBE, email
2013/7/31 Steven Chamberlain :
> On 31/07/13 12:45, Robert Millan wrote:
>>> It probably needs to
>>> end up in a README.Debian at least, plus mentioned in the changelog:
>>
>> Sounds fine too.
>
> I'm not sure how to deploy that file exactly. Could you please try?
> I'll be a little busy today.
On 31/07/13 12:45, Robert Millan wrote:
>> It probably needs to
>> end up in a README.Debian at least, plus mentioned in the changelog:
>
> Sounds fine too.
I'm not sure how to deploy that file exactly. Could you please try?
I'll be a little busy today.
Thanks,
Regards,
--
Steven Chamberlain
s
2013/7/30 Steven Chamberlain :
> I've written the following text to explain 'workarounds' for those
> issues. I'm not sure exactly where to put this.
Maybe DSA advisory is the best place?
> It probably needs to
> end up in a README.Debian at least, plus mentioned in the changelog:
Sounds fine t
On 29/07/13 13:30, Steven Chamberlain wrote:
> Probably we just need to add some text explaining CVE-2012-5365,
> CVE-2012-5363 and CVE-2011-2393, and that would be good enough to call
> them all 'fixed in wheezy'. We'd need to send a final debdiff
> containing all this. I'll try and draft someth
On 28/07/13 20:59, Moritz Muehlenhoff via RT wrote:
> There're also CVE-2012-5365, CVE-2012-5363 and CVE-2011-2393 open
> for kfreebsd-9. Any chance we can fix these along?
It still seems our best option for wheezy is to merely document those
issues, as suggested in http://bugs.debian.org/684072#2
9 matches
Mail list logo
