On Tue, Oct 21, 2014 at 9:23 PM, Mike Hommey m...@glandium.org wrote:
On Tue, Oct 21, 2014 at 08:18:14PM -0400, William Herrin wrote:
On Tue, Oct 21, 2014 at 6:42 PM, Mike Hommey m...@glandium.org wrote:
On Tue, Oct 21, 2014 at 06:05:27PM -0400, William Herrin wrote:
Am 22.10.2014 um 18:33 schrieb William Herrin:
Wanna bet what Red Hat does? Spoiler alert: the same thing
https://www.redhat.com/archives/rhsa-announce/2014-October/msg00026.html
Mike, you summarize my complaint: with iceweasel you've done the same
lousy job at versioning that Red Hat does.
1. Introduce an iceweasel32 package and obsolete the old iceweasel
package at the point where you're no longer able to provide security
updates to it. The obsoleted package won't be removed until the
sysadmin decides to remove it.
This means we should skip the ESR version 31 with the
Subject: iceweasel: wheezy force upgraded to 31.2.0esr-2~deb7u1
Package: iceweasel
Version: 31.2.0esr-2~deb7u1
Severity: important
Dear Maintainer,
*** Please consider answering these questions, where appropriate ***
* What led up to the situation?
used dselect for routine security patches
Hello William,
On Tue, Oct 21, 2014 at 02:44:34PM -0400, William Herrin wrote:
Subject: iceweasel: wheezy force upgraded to 31.2.0esr-2~deb7u1
This is a major breach of protocol for debian security patches.
You DO NOT, DO NOT, DO NOT release major new upstream
versions in the middle of a
https://www.debian.org/security/faq
The most important guideline when making a new package that fixes a
security problem is to make as few changes as possible. Our users and
developers are relying on the exact behaviour of a release once it is made,
so any change we make can possibly break
On Tue, Oct 21, 2014 at 06:05:27PM -0400, William Herrin wrote:
https://www.debian.org/security/faq
The most important guideline when making a new package that fixes a
security problem is to make as few changes as possible. Our users and
developers are relying on the exact behaviour of a
On Tue, Oct 21, 2014 at 6:42 PM, Mike Hommey m...@glandium.org wrote:
On Tue, Oct 21, 2014 at 06:05:27PM -0400, William Herrin wrote:
https://www.debian.org/security/faq
The most important guideline when making a new package that fixes a
security problem is to make as few changes as
On Tue, Oct 21, 2014 at 08:18:14PM -0400, William Herrin wrote:
On Tue, Oct 21, 2014 at 6:42 PM, Mike Hommey m...@glandium.org wrote:
On Tue, Oct 21, 2014 at 06:05:27PM -0400, William Herrin wrote:
https://www.debian.org/security/faq
The most important guideline when making a new
9 matches
Mail list logo
