On Thu, May 20, 2021 at 05:55:34PM +0200, Cyril Brulebois wrote:
> Paul Gevers (2021-05-20):
> > On 20-05-2021 00:11, Theodore Y. Ts'o wrote:
> >
> > Unfortunately, there was no release.debian.org bug to track this. Due
> > to the current high volume to our lis
Ping to the debian-release bug. Do you want me to upload a fix to
this bug where e2fsprogs fails its regression test (and thus its
package build) when armhf and armel are running on a 64-bit ARM
platform, but they were built successfully when run on a 32-bit ARM
builder?
No question this is a
On Wed, Jan 22, 2020 at 09:27:01AM +0100, Cyril Brulebois wrote:
> You can upload. And no, it will stay in p-u-new until it's approved by
> some SRM, at which point it will be made available in
> stable-proposed-updates (note word order), until the point release.
Great, thanks!
And thanks for
Oh, one more question. Is a source-only upload OK? I'm still a bit
confused when a source-only upload is required, and when a binary
upload is required? Is the latter only for the NEW queue?
- Ted
On Tue, Jan 21, 2020 at 07:57:54PM +, Adam D. Barratt wrote:
> Control: tags -1 + confirmed d-i
>
> On Thu, 2020-01-09 at 22:34 -0500, Theodore Y. Ts'o wrote:
> > +e2fsprogs (1.44.5-1+deb10u3) buster; urgency=medium
> > +
> > + * Fix CVE-2019-5188: potential stack
: potential stack underflow in e2fsck (Closes: #948508)
+ * Fix use after free in e2fsck (Closes: #948517)
+
+ -- Theodore Y. Ts'o Thu, 09 Jan 2020 20:19:57 -0500
+
e2fsprogs (1.44.5-1+deb10u2) buster-security; urgency=high
* Fix CVE-2019-5094: potential buffer overrun in e2fsck (Closes: #941139
/debian/changelog 2018-12-15 22:46:49.0 -0500
+++ e2fsprogs-1.44.5/debian/changelog 2019-08-02 23:49:00.0 -0400
@@ -1,3 +1,9 @@
+e2fsprogs (1.44.5-1+deb10u1) buster; urgency=medium
+
+ * Fix e4defrag crashes on 32-bit architectures (Closes: #920767)
+
+ -- Theodore Y. Ts'o Fri, 02
Oh, one more question --- should I be doing a source-only, or binary
push when I push to buster-proposed-updates.
I'm a bit confused about whether it will be going into the NEW queue,
and hence require a binary push, or a source-only build because that's
the new hotness and it's required for
On Sat, Aug 03, 2019 at 04:08:14PM +0100, Adam D. Barratt wrote:
>
> I assume this is simply a case of an outdated chroot pointing at
> "stable" or similar. The net effect is that the upload ended up in NEW
> (presumably as buster's e2fsprogs builds additional binary packages
> relative to
-1.44.5/debian/changelog 2018-12-15 22:46:49.0 -0500
+++ e2fsprogs-1.44.5/debian/changelog 2019-08-02 23:49:00.0 -0400
@@ -1,3 +1,9 @@
+e2fsprogs (1.44.5-1+deb9u1) stretch; urgency=medium
+
+ * Fix e4defrag crashes on 32-bit architectures (Closes: #920767)
+
+ -- Theodore Y. Ts'o
On Fri, Aug 02, 2019 at 09:03:19AM +0100, Adam D. Barratt wrote:
> I suspect that may have been what it was originally intended to mean. (I
> think the DevRef text dates from before my involvement in Debian.) It's not
> the yardstick that is currently applied, however. I need to find some tuits
>
Hi,
I'm trying to mean what is meant by "truly critical functionality
problem" in Section 5.5.1 in the Debian Developer's Reference:
Extra care should be taken when uploading to stable. Basically, a
package should only be uploaded to stable if one of the following
happens:
*
(Quoting somewhat out of order)
On Sun, May 13, 2018 at 09:23:39PM +, Thorsten Glaser wrote:
>
> It’s also no solution for the arc4random API… seems like a cultural
> clash (BSD expectations vs. what Linux can actually deliver).
It's instructive to look how OpenBSD solves this problem.
Package: release.debian.org
Severity: normal
User: release.debian@packages.debian.org
Usertags: unblock
Please unblock package e2fsprogs
1.43.4 is the new upstream version of e2fsprogs which fixes a RC bug
(#840733: e2fsprogs contains non-free file). n.b., the non-free file is
only used in
Package: release.debian.org
Severity: normal
Tags: jessie
User: release.debian@packages.debian.org
Usertags: pu
As requested (sorry for the delay) here is an upload which contains a
cherry-pick for to address Debian Bug #812141: "Cherry-pick "e2fsck: use
PROMPT_NONE for
Package: release.debian.org
Severity: normal
User: release.debian@packages.debian.org
Usertags: unblock
Please unblock package e2fsprogs
This fixes a number of fairly serious bugs:
* It fixes a foreign multiarch bug (#678395), and multiarch is a
release goal
* It fixes a bug
16 matches
Mail list logo
