Package: kernel-package
Version: 10.019
Severity: minor
Why are there two different example directories for kernel-package,
one in /usr/share/doc and one in /usr/share? This is very confusing,
especially since kernel_grub_conf.sh and kernel_grub_rm.sh are
inverses of each other and are in two dif
Package: kernel-package
Version: 10.019
Severity: normal
modules.ofmap should be added to @files_to_remove in the postrm
script. This is needed so that you can do an "dpkg --install"
followed by an "dpkg --purge", without leaving behind the
/lib/modules/$kver directory and a leftover
/lib/modules
Package: kernel-package
Version: 10.019
Severity: normal
If you add the following lines to /etc/kernel-img.conf:
postinst_hook = /boot/grub/kernel_grub_conf.sh
postrm_hook = /boot/grub/kernel_grub_rm.sh
The postinst and postrm scripts will fail with exit code 128,
respectively. The /boot/grub/k
Package: blogtk
Version: 1.0-1.1
Severity: normal
blogtk requires gtkhtml2.py, which has been moved to
python-gnome2-extras.
-- System Information:
Debian Release: testing/unstable
APT prefers unstable
APT policy: (500, 'unstable'), (200, 'experimental')
Architecture: i386 (i686)
Shell: /bi
Package: login
Version: 1:4.0.3-35
Severity: normal
When CLOSE_SESSIONS is enabled, /bin/su runs the shell in a forked
child process, thanks to the patch 008_su_PAM_session. The problem
with this patch is that the parent process, which hangs around waiting
for the child to exit, doesn't notice if
Package: lintian
Version: 2.5.22.1
Severity: normal
http://lintian.debian.org/maintainer/ty...@mit.edu.html#e2fsprogs
is reporting:
e2fsprogs (1.42.9-3) Info PTS Bugs (last processed by Lintian/2.5.22.1)
E source-is-missing
misc/util.o
But misc/util.c is there; it doesn't get any mo
Package: initramfs-tools
Version: 0.107
Severity: wishlist
Tags: patch
It would be nice if the following chage (see attached patch) was made
to /usr/share/initramfs-tools/init, which changes the script to uses
blkid instead of /dev/disk/by-{label,uuid}. The reason why I consider
this an improveme
Package: e2fsprogs
Version: 1.42.4-3
Severity: normal
The logsave program is leaking a file descriptor when it fork and
exec's the program that it is logging. In the case of
/etc/init.d/checkroot, this would be fsck. This file descriptor never
gets closed, so it's still present when fsck runs e2
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 (#682
Package: lvm2
Version: 2.02.168-2
Severity: normal
The problem is that "vgchange --monitor y --ignoreskippedcluster" exits
with exit code 5 if there are any exported volume groups present on the
system:
# vgimport ext
Volume group "ext" successfully imported
# /sbin/lvm vgchange --monitor y --i
Package: e2fsprogs
Version: 1.43.4-2
Severity: important
The tune2fs program no longer properly enables quotas due to a
regression introduced in 1.43.4. The problem commit is 5c2a665afa:
"Avoid dereferencing beyond allocated memory in quota handling".
This causes xfstests generic/383, generic/38
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 FUTURE_SB_LAST_*_FUDGED
Package: debootstrap
Version: 1.0.81
Severity: wishlist
Tags: patch
This patch, suitable for application via "git am", will be used as part
of the xfstests-bld infrastructure. (See http://thunk.org/gce-xfstests
for more info). I'll be using a modified copy of this script for now,
but it would be
Package: blktrace
Version: 1.1.0-2
Severity: normal
Dear Maintainer,
blktrace depends on lsb-base, for no good reason I can see. The init
script uses LSB conventions for labelling when it should be started, but
that's not a reason to pull in lsb-base. The problem with depending on
lsb-base is t
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 a
Source: exim4
Severity: important
>From a recent discussion on IETF's Security Area Advisory Group:
Date: Thu, 6 Oct 2016 08:56:45 -0700
From: Watson Ladd
To: "s...@ietf.org"
Subject: [saag] Possible backdoor in RFC 5114
https://tools.ietf.org/html/rfc5114
Let's review some publicly known fac
Package: snapshot.debian.org
Followup-For: Bug #1034000
I'm seeing similar failures for a number for the last three snapshots
listed at:
http://snapshot.debian.org/archive/debian/?year=2023&month=8
Namely for:
* 2023-08-06 09:19:12
* 2023-08-07 15:08:23
* 2023-08-09 03:23:42
As noted in [1]
Package: clang-16
Version: 1:16.0.6-26
Severity: normal
Dear Maintainer,
I was trying to track down a regression reported by the ClusterFuzz
service, and when I try to build the fuzzing reproducer on trixie, it
fails. However, it works on Bookworm. So while I can work around the
problem by usin
Package: systemd-sysv
Version: 252.6-1
Severity: normal
Dear Maintainer,
* What led up to the situation?
I was updating the gce-xfstests[1] test appliance to Debian Bookworm from
Debian Bullseye.
[1] https://thunk.org/gce-xfstests
* What exactly did you do (or not do) that was effective
Package: src:linux
Version: 6.5.13-1
Severity: normal
Dear Maintainer,
I am running Debian testing in a Parallels VM (6 cores, 8GB memory)
running on Macbook Air M2 15" (10 cores, 24GB memory). gcc13 is
sig faulting when building xfsprogs or the Linux kernel when using make -j6.
Building xfsprog
Package: kernel-package
Version: 10.036
Severity: wishlist
As support for kexec/kdump support becomes more real, it will be very
useful to be able to build kernels that have debugging information
available, but not necessarily to install the debugging information on
every single client system.
Re
Package: devscript
Version: 2.9.10
Severity: wishlist
There ought to be an option to not download bugs that have already
been ignored. First of all, they unlikely to have changed since they
have been resolved; secondly, a developer is much less likely to care
about looking at resolved bugs while
Package: libdevmapper-dev
Version: 2:1.02.03-1
Severity: wishlist
It would be very nice if devmapper had a pkg-config file (i.e.,
devmapper.pc) so that programs could automatically figure out
dependencies that devmapper might have. I recently received a patch
for e2fsprogs from Red Hat which assu
Thanks for the report. I've checked in a fix for this into the
e2fsprogs git repository, and it will be in the next release of e2fsprogs.
- Ted
On Tue, Jun 12, 2018 at 11:38:15PM -0700, Elliott Mitchell wrote:
> Package: e2fsproc
> Version: 1.43.4-2
>
> Subject tells the story:
>
> # tune2fs -O dir_index,extent,metadata_csum,mmp,quota -Q
> usrquota,grpquota,prjquota /dev/foo
> tune2fs 1.43.4 (31-Jan-2017)
> [ERROR] ../../../../lib/suppo
On Fri, Jun 15, 2018 at 07:37:19PM -0700, Elliott Mitchell wrote:
>
> During the process I ended up running `e2fsck -f` multiple times. I
> ended up running `e2fsck -f` after enabling each feature (`tune2fs`
> really didn't like enabling multiple features at once).
OK, so I really need a reliabl
To the German, Dutch, and Vietnamese translators of e2fsprogs's po
file, --- I've added you to the cc list because Martin von Wittich has
pointed out the following error in your translation files. Please
read on
On Tue, Mar 06, 2018 at 01:15:56PM +0100, Martin von Wittich wrote:
> the German
On Tue, Mar 20, 2018 at 08:45:32AM +0100, Petter Reinholdtsen wrote:
>
> Packhage: e2fsprogs
> Version: 1.44.0~rc1-1
> Severity: important
> Tags: patch
>
> A code change introduced in version 1.44.0~rc1-1 according to the
> autobuild logs causes the program to fail to build from source on hurd.
On Tue, Mar 20, 2018 at 08:50:43AM +0100, Petter Reinholdtsen wrote:
>
> Package: e2fsprogs
> Version: 1.44.0~rc1-1
> Severity: important
>
> The automatic builders in Debian are unable to build e2fsprogs on
> kfreebsd, because the build depend on libtirpc1 depending on libcomerr2
> (>= 1.01). I
On Fri, Aug 31, 2018 at 01:06:00AM +1200, Stuart Richards wrote:
>
> Attempting to defrag a file with e4defrag -v filetobedefragged on a Raspberry
> Pi gives the error "-v: No such file or directory while trying to open file
> system: /dev/root". The same command works as expected on an AMD64 s
If e4defrag is run by root, it will try to open the underlying file
system for files that it is trying to defrag so it can get the file
system parameters. It's currently doing this by searching /etc/mtab.
This isn't the best way to go about doing things, but we'll leave it
for now, at least for a
On Thu, May 13, 2021 at 09:56:53PM +0100, Marcin Kulisz wrote:
>
> I hope that we're be able to change it, but for me fundamental
> question is if Google is interested in participating in effort to
> keep those packages in Debian main and if so what resources can be
> committed to do so. From my
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 rea
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 li
tags 989630 +pending
thanks
I finally had time to investigate this problem. It turns out the only
time this bug manifests is when creating an file system smaller than
(blocksize)**2 bytes (e.g., 16 megabytes when the is block size is
4k).
The bug was introduced almost ten years ago (September 20
Package: debhelper
Version: 13.4+nmu1
Followup-For: Bug #992469
I can confirm Samuel's analysis. When I tried debugging why building
e2fsprogs was causing a new lintian error:
E: e2fsprogs: systemd-service-file-outside-lib
usr/lib/systemd/system/e2scrub@.service
N:
E: systemd-service-file-outsi
Package: gcc-8
Version: 8.3.0-19
Severity: normal
Dear Maintainer,
The e2fsprogs package is currently not reproducible. See:
https://tests.reproducible-builds.org/debian/rb-pkg/unstable/amd64/e2fsprogs.html
This is caused by an unfortunate interaction between LTO and the flags
from dpkg-buildf
Control: tags -1 +pending
On Wed, Feb 27, 2019 at 03:01:52AM +, Dmitry Bogatov wrote:
>
> Package: e2fsprogs
> Version: 1.44.5-1
> Severity: normal
>
> Dear Maintainer,
>
> for long time e2fsprogs were essential, and bin:initscripts used
> /sbin/logsave from e2fsprogs. Nowdays, e2fsprogs ar
Package: e2tools
Version: 0.0.16-6.1+b2
Severity: wishlist
The original source for e2tools has disappeared (the home.earthlink.net
pages is dead), but it looks like there is activity at:
https://github.com/ndim/e2tools
Hans has modernized the package, fixing the FSF's address in the
copyright no
This Lintian check is also a false positive for e2fsprogs, where it's
triggering 4 false positive Lintian errors.
Per
https://lintian.debian.org/tags/package-supports-alternative-init-but-no-init.d-script.html:
This lintian tag has:
Emitted (non-overridden): 787, overridden: 22, total: 809
A
control: -1 +pending
On Sun, Jul 21, 2019 at 01:27:38PM +0200, Laurent Bigonville wrote:
>
> The cronjob (/etc/cron.d/e2scrub_all) file is a conffile, that means
> that if the package is removed without being purge, the cronjob will
> still be installed, but the executable will not.
>
> The cron
Control: tags 932855 +pending
Control: tags 932859 +pending
Control: tags 932861 +pending
Control: tags 932881 +pending
Control: tags 932888 +pending
My apologies, I hadn't realized initramfs had a dependency on logsave.
I guess I should have known that, but it had slipped my mind. This
will be f
On Wed, Jul 24, 2019 at 05:52:48AM +0200, Sven Joachim wrote:
> Package: logsave
> Version: 1.45.3-1
>
> Like the package it partially replaces (e2fsprogs), logsave should be
> Multi-Arch: foreign. The initramfs-tools-core package will have to
> depend on logsave, which makes cross-grades (say, f
On Wed, Jul 24, 2019 at 05:46:50AM +0200, Sven Joachim wrote:
> Package: logsave
> Version: 1.45.3-1
> Severity: serious
>
> Installing logsave without upgrading e2fsprogs fails:
>
> ,
> | Preparing to unpack .../logsave_1.45.3-1_amd64.deb ...
> | Unpacking logsave (1.45.3-1) ...
> | dpkg: er
Control: tags -1 +pending
On Wed, Jul 24, 2019 at 05:17:28PM +0200, Thorsten Glaser wrote:
>
> 355 tests succeeded 1 tests failed
> Tests failed: f_pre_1970_date_encoding
>
> I assume this is because x32 is a 32-bit (ILP32) architecture
> with 64-bit time_t.
Thanks for the bug report. This
On Thu, Jul 25, 2019 at 07:03:50PM +0200, Domenico Andreoli wrote:
> Hi Theodore,
>
> apologies, I'll prepare a new upload. Would you mind sponsoring it?
Sure, I'd be happy to sponsor it.
- Ted
control: -1 tags +pending
On Sun, Jul 28, 2019 at 08:09:22AM +0200, Helmut Grohne wrote:
> Source: e2fsprogs
> Version: 1.45.3-3
> Severity: important
> Tags: patch
> User: debian-cr...@lists.debian.org
> Usertags: ftcbfs
>
> e2fsprogs fails to cross build from source, since the -3 upload, becaus
On Sun, Jul 28, 2019 at 06:21:57PM +0200, Helmut Grohne wrote:
> Hi Ted,
>
> On Sun, Jul 28, 2019 at 10:04:48AM -0400, Theodore Y. Ts'o wrote:
> > Yes, I had noticed that this was breaking some of the ports build as
> > well, and so I have a similar patch in my tree al
On Mon, Jul 29, 2019 at 02:51:49PM +0200, Domenico Andreoli wrote:
>
> Here it is: https://mentors.debian.net/package/dwarves-dfsg
>
> I found not useful to reuse your git history as-is, although I could
> not drop your changelog entry ;)
It looks like you did merge in my git changes, though? H
On Mon, Jul 29, 2019 at 10:32:38AM -0400, Theodore Y. Ts'o wrote:
> On Mon, Jul 29, 2019 at 02:51:49PM +0200, Domenico Andreoli wrote:
> >
> > Here it is: https://mentors.debian.net/package/dwarves-dfsg
> >
> > I found not useful to reuse your git history as-i
On Tue, Jul 30, 2019 at 05:54:37PM +0200, Domenico Andreoli wrote:
> Edited history again, just fixed the typo in the only patch. I could
> not find any other low hanging fruit, anything else requires some
> investigation (included the warnings on debian/copyright)
Well, debian-watch-uses-insecure
OK, I've upload 1.15-1, so let's not rewrite the history on Salsa any
more. :-)
Thanks!!
- Ted
On Wed, Jul 31, 2019 at 04:22:35PM +0100, Ian Jackson wrote:
> Submodules are intensely frustrating[1]. One way they are frustrating is
> that it is not clear even what it means for a .dsc to be identical to
> a git tree which has submodule references. Are the submodules
> supposed to be populate
On Thu, May 21, 2020 at 10:04:54AM +0200, Wilmer van der Gaast wrote:
> I just started a downsizing resize2fs operation over an SSH session
> without screen and then realised how bad an idea that was..
>
> Then found this bug as a confirmation. :-)
>
> It looks like resize2fs (still) doesn't inst
On Mon, Apr 27, 2020 at 09:01:56AM -0700, Igor Dvorzhak wrote:
> Package: e2fsprogs
>
> resize2fs takes extra 90 seconds to resize 2TB boot disk during boot on
> Debian 10 than on Debian 9.
>
> Note that time to create/provision VM instance (gcloud compute instances
> create ...) is the same (aro
On Tue, Oct 27, 2020 at 12:24:51AM +0100, Diederik de Haas wrote:
> Package: f2fs-tools
> Version: 1.11.0-1.1
> Followup-For: Bug #970176
>
> On salsa.d.o it looks like version 1.13 was ready to go, but it appears
> that it just never got uploaded to the archives/sid.
> It would be really welcome
On Wed, Mar 21, 2018 at 09:47:41AM +0100, Ansgar Burchardt wrote:
> > On Tue, Mar 20, 2018 at 08:50:43AM +0100, Petter Reinholdtsen wrote:
> >> The automatic builders in Debian are unable to build e2fsprogs on
> >> kfreebsd, because the build depend on libtirpc1 depending on libcomerr2
> >> (>= 1.0
Source: mesa
Version: 17.3.4-1
Severity: important
Dear Maintainer,
After upgrading to Mesa 17.3.4-1, starting emacs (in X11) would reliably
cause the X server to crash. Reverting to mesa 17.3.3-1 with the
following packages:
libegl1-mesa_17.3.3-1_amd64.deb
libegl-mesa0_17.3.3-1_amd64.deb
libg
On Tue, May 01, 2018 at 10:29:19AM +0200, Helmut Grohne wrote:
>
> On Sun, Apr 15, 2018 at 07:15:45PM +0200, Helmut Grohne wrote:
> > Thus I ask Ted to drop the Essential flag now. I am attaching a patch
> > that replaces Essential: yes with XB-Important: yes.
>
> It seems that you presently lack
--- Begin Message ---
On Tue, May 01, 2018 at 10:29:19AM +0200, Helmut Grohne wrote:
>
> On Sun, Apr 15, 2018 at 07:15:45PM +0200, Helmut Grohne wrote:
> > Thus I ask Ted to drop the Essential flag now. I am attaching a patch
> > that replaces Essential: yes with XB-Important: yes.
>
> It seems t
On Tue, May 01, 2018 at 05:22:34PM +0200, Helmut Grohne wrote:
> Hi Ted,
>
> I do want to ensure that this has gone through well ahead of the
> transition freeze. Batching up such changes to the last moment makes
> releasing buster on time harder. Even though the chance of breaking
> something is
On Thu, May 03, 2018 at 01:33:39PM +0200, David Regajo wrote:
> Package: e2fsprogs
> Version: 1.43.4-2
>
> With the system installed with spanish settings, mkfs.ext4 asks for (y,N),
> but when answered "y" does nothing. I have to reply "s" to proceed.
>
> See below 3 tries, the two first are "y"
On Sat, May 05, 2018 at 02:11:59AM +0200, Piotr Jurkiewicz wrote:
> Package: e2fsprogs
> Version: 1.44.1-2
>
> Trying to mkfs.ext4 from initramfs (so with klibc) inside QEMU, it gets
> stuck on getrandom syscall. Running it with strace:
>
> I wasn't experiencing such a behavior one month before,
By the way, if anyone is interested in working on this related
problem:
https://news.ycombinator.com/item?id=16976421
The reason why this is hard is because Linux is supported on a
great number of architectures, and some architectures have more
than one boot loader that is used. The a
On Mon, May 07, 2018 at 02:58:03PM +1200, Ben Caradoc-Davies wrote:
> This reverts commit 43838a23a05f ("random: fix crng_ready() test"),
> which causes urandom to hang in early boot even when crng_init==1.
>
> One impact of this hang is that it prevents display of the plymouth
> graphical passphr
On Thu, May 10, 2018 at 12:41:41PM +1200, Ben Caradoc-Davies wrote:
> tl;dr: fontconfig tries to regenerate .uuid files with getrandom (via
> libuuid) in early boot, which hangs because of low pool entropy; the
> plymouth fix is to copy the .uuid files into the initramfs with the DejaVu
> fonts.
O
On Sun, Nov 03, 2019 at 05:07:22AM +0100, gregor herrmann wrote:
>
> Cron sends me the following mail once per week:
>
> /sbin/e2scrub_all: line 173: /proc/8234/fd/pipe:[90083173]: No such file or
> directory
Gregor, thanks for the bug report! This is coming from:
stdin="$(realpath /dev/stdin
On Sun, Nov 03, 2019 at 11:09:00AM -0800, Darrick J. Wong wrote:
>
> Because if you don't do that, the e2scrub process gets started with fd 0
> mapped to stdout of ls_targets on account of the "ls_targets | while
> read tgt" loop. Yay bash. I guess the problem here is that
> e2scrub_all's stdin
On Wed, Nov 13, 2019 at 11:38:55AM +0100, Svante Signell wrote:
> Source: e2fsprogs
> Version: 1.45.4-1
> Severity: important
> Tags: patch
> Usertags: hurd
> User: debian-h...@lists.debian.org
>
> Hello,
>
> The latest version of e2fsprogs in sid, 1.45.4-1, FTBFS on GNU/Hurd due to two
> reasons
On Sat, Jan 04, 2020 at 07:57:16PM -0800, Josh Triplett wrote:
> Package: e2fsprogs
> Version: 1.45.4-1
> Severity: important
>
> The e2fsprogs package installs a service and timer to run e2scrub. That
> service sleeps for 2 seconds before exiting, delaying the boot by 2
> seconds.
It's not neces
On Mon, Jan 06, 2020 at 12:39:52AM -0800, Josh Triplett wrote:
> That's an *additional* delay, on top of the sleeps above. The two-second
> sleep in the "exitcode" function seems like the primary culprit. Note
> that I don't even have lvm2-tools installed.
Ah, yes, sorry, I had missed the sleep i
Package: e2fsprogs
Version: 1.43.4-2+deb9u1
Severity: grave
Tags: security
Justification: user security hole
E2fsprogs 1.45.5 contains a bug fix for CVE-2019-5188 / TALOS-2019-0973.
The following commits need to be backported to address this
vulnerability in Debian Buster and Debian Stretch:
8dd7
Package: e2fsprogs
Version:
Severity: grave
Tags: security
Justification: user security hole
E2fsprogs 1.45.5 contains a bug fix for a use after free which could
potentially be used to run malicious code if a user can be tricked into
running e2fsck on a maliciously crafted file system. The follo
: 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: #9
On Tue, Mar 10, 2020 at 05:10:29AM +0800, 積丹尼 Dan Jacobson wrote:
> Package: e2fsprogs
> Version: 1.45.5-2
> File: /usr/share/man/man8/mke2fs.8.gz
>
> Please add to the mke2fs man page:
>
> ** This version of mke2fs is guaranteed to make filesystems that
>support timestamps *beyond* 2038. **
On Tue, Mar 10, 2020 at 05:57:33AM +0800, 積丹尼 Dan Jacobson wrote:
> Package: e2fsprogs
> Version: 1.45.5-2
>
> Idea: make a new file
> /usr/share/doc/e2fsprogs/Year2038warnings
> that would say:
>
> If you get
> ext4 filesystem being mounted at ... supports timestamps until 2038
> (0x7fff)
b/debian/control
index 71613e11..69471f45 100644
--- a/debian/control
+++ b/debian/control
@@ -2,7 +2,7 @@ Source: e2fsprogs
Section: admin
Priority: required
Maintainer: Theodore Y. Ts'o
-Build-Depends: gettext, texinfo, pkg-config, libfuse-dev [linux-any
kfreebsd-any] , libattr1-dev, de
Package: lintian
Version: 2.58.0
Severity: normal
Dear Maintainer,
Lintian is reporting a number of spurious failures:
E: e2fsprogs-udeb udeb: debian-changelog-file-missing
E: e2fsprogs buildinfo: field-too-long Installed-Build-Depends (5090 chars >
5000)
E: e2fsprogs-udeb udeb: file-in-etc-not
Package: iwd
Version: 1.2-1
Severity: grave
Justification: renders package unusable
Dear Maintainer,
I upgraded my Debian testing system to the latest version of Bullseye,
and I was completely unable to connect to wireless. In the logs, I see
that iwd is crashing:
Dec 12 09:40:11 lambda kernel:
Control: tag 942121 +upstream
Hi Chao, Jaeguk,
Could you take a look at this complaint and let me know if I should
close the bug as Working As Intended or not?
The concern seems to be that for desktop distros (which I know was not
f2fs's original target), some users update their kernels frequent
On Mon, Oct 14, 2019 at 10:12:34AM -0700, Jaegeuk Kim wrote:
> On 10/14, Theodore Y. Ts'o wrote:
> > Control: tag 942121 +upstream
> >
> > Hi Chao, Jaeguk,
> >
> > Could you take a look at this complaint and let me know if I should
> > close the bu
Package: dwarves
Version: 1.12-2
Severity: normal
Tags: patch
Dear Maintainer,
There is a newer version of dwarves upstream (1.14). Version 1.13 is
needed to build the latest kernels with CONFIG_DEBUG_INFO_BTF.
Please consider merging the debian/master branch from:
https://salsa.debian
On Fri, Sep 20, 2019 at 11:40:30PM +0200, Francesco Poli wrote:
>
> Hello Thorsten, hello Theodore,
> I am another user who began receiving the same error messages from cron
> on a box with LVM, but without systemd.
It's only going to happen if you aren't using systemd, since if you
are using sys
Package: debian
Version: 1.44.5-1+deb10u1
Severity: grave
Tags: security
Justification: user security hole
E2fsprogs 1.45.4 contains a bugfix for CVE-2019-5094 / TALOS-2019-0887.
We need to backport commit 8dbe7b475ec5: "libsupport: add checks to
prevent buffer overrun bugs in quota code" to the v
Phillip,
Peace.
You may not like the fact that David Oberhollenzer (GitHub username
AgentD) started an effort to implement a new set of tools to generate
squashfs images on April 30th, 2019, and called it squashfs-tools-ng.
However, it's really not fair to complain that there is a "violation
of
On Fri, Aug 02, 2019 at 11:25:10AM +1000, Ralph Ronnquist wrote:
> Package: libuuid1
> Version: 2.34-0.1
>
> The package is declared to replace e2fsprogs, which it doesn't do.
> Rather, installing it has a fair few ramifications on the installed system.
>
> The package belongs to the util-linux s
On Fri, Aug 02, 2019 at 02:09:03PM +1000, Ralph Ronnquist wrote:
> Well,
>
> when I then "agt-get install libuuid1:i386" (on this multiarch)
> I get advice about a page full of packages to be removed, and the
> following (plus a bit more):
> ---
> WARNING: The following essential packages will be
-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&#
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 stretch
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 promo
ogs-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+deb10u1) buster; urgency=medium
+
+ * Fix e4defrag crashes on 32-bit architectures (Closes: #920767)
+
+ -- Theodore Y. Ts&#
On Wed, Jan 11, 2017 at 09:27:26AM +0100, Helmut Grohne wrote:
> Source: xzgv
> Version: 0.9.1-4
> Tags: patch
> User: helm...@debian.org
> Usertags: rebootstrap
>
> xzgv fails to cross build from source, because it uses build
> architecture build tools. Simply adding the host architecture triplet
Package: flowblade
Version: 2.2-1
Severity: grave
Justification: renders package unusable
Dear Maintainer,
I installed flowblade, and then tried to start it. It failed to start;
I expected it to start and be usable. :-)
% flowblade
FLOWBLADE MOVIE EDITOR 2.2
--
Launch s
On Sat, Sep 14, 2019 at 02:42:29PM +0200, Thorsten Glaser wrote:
> Package: e2fsprogs
> Version: 1.45.3-4
> Severity: minor
>
> From: Cron Daemon
> Message-ID: <20190914011004.3afc6220...@tglase.lan.tarent.de>
> To: r...@tglase.lan.tarent.de
> Date: Sat, 14 Sep 2019 03:10:04 +0200 (CEST)
> Subjec
On Sun, Dec 16, 2018 at 10:35:55AM +, Simon McVittie wrote:
> >* Fix mk_cmds so it works on a usrmerge system when e2fsprogs is built
> > on a non-usrmerge system (Closes: #914087)
>
> In the interests of avoiding inaccurate information, this bug was actually
> the other way round: th
On Thu, Dec 20, 2018 at 03:17:03PM -0500, Daniel Kahn Gillmor wrote:
>
> I wonder whether we can rule out any interaction with gpg-agent itself
> -- does "echo getpin | pinentry-gnome3" itself fall back to curses on
> your system when nfs-kernel-server is installed?
I can confirm that that I did
Regarding in-kernel recovery "being good enough". The reason why some
file systems and system administrators prefer to run fsck at boot,
even you can there is "in-kernel recovery", is that journal/log replay
only works on an unclean shutdown.
However, sometimes there are can be file system incons
Control: tags -1 +pending
Control: severity -1 normal
On Sun, Aug 18, 2019 at 04:16:25AM +0200, Mikhail Morfikov wrote:
> There's no error indicating what could be wrong.
>
> Looking through the /usr/sbin/e2scrub_all file, I noticed the following line:
>
> local devices=$(lvs -o lv_path --nohead
Control: tags -1 +pending
On Wed, Oct 18, 2017 at 10:31:31AM -0400, Theodore Ts'o wrote:
> On Tue, Oct 17, 2017 at 01:56:32PM -0400, Michael Stone wrote:
> > I'd like the fuse2fs package to gain the norecovery option so that read-only
> > sources with dirty journals can be mounted via fuse. This s
Package: iwd
Version: 1.24-1
Severity: important
Dear Maintainer,
After upgrading to iwd 1.24-1, it is crashing on my system. (Dell
XPS-13 with an ath10k/QCA6174/hw3.0 wireless card.) Downgrading to iwd
1.21-3 allows things to work. Restalling iwd 1.24-1 causes it crash
again.
If I run /usr/l
1 - 100 of 142 matches
Mail list logo
