Bug#998627: linux: please enable the new NTFS3 driver in 5.15

[Felix Zielcke]

Hi,

upstream has now completely removed the old classic NTFS driver.
And ntfs3 has been setup to serve as alias to the old one:

https://git.kernel.org/pub/scm/linux/kernel/git/torvalds/linux.git/commit/fs/ntfs3?id=74871791ffa9562d43567c5ff2ae93def3f39f65

Are there still concerns to enable it by default? And if so which ones?

Regards
Felix

Bug#998627:

[Felix Zielcke]

On Sat, 17 Feb 2024 22:38:57 +0800 an xiao 
> Hello,
> 
> Paragon-software is active enough on their subsystem,
> and NTFS3 is extremely stable now.
> Please consider enabling the NTFS3 driver for sid.
> 
> Thinks and best regards,
> Littlewhite

Hi,

today was a pull request submitted which removes the old ntfs driver
from kernel [1]. Ok it's not enabled in Debian.

But it also says that ntfs3 is a full replacement and that Archlinux
has enabled it since 5.15

Would be nice to have it enabled in Debian too.

TIA
Felix

[1] https://lore.kernel.org/lkml/20240308-vfs-ntfs-ede727d2a142@brauner/

Bug#1062854: reiserfsprogs: NMU diff for 64-bit time_t transition

[Felix Zielcke]

Am Samstag, dem 03.02.2024 um 20:27 + schrieb Sergio Durigan
Junior:
> Source: reiserfsprogs
> Version: 1:3.6.27-7
> Severity: serious
> Tags: patch pending sid trixie
> Justification: library ABI skew on upgrade
> User: debian-...@lists.debian.org
> Usertags: time-t
> 
> NOTICE: these changes must not be uploaded to unstable yet!
> 
> Dear maintainer,
> 
> As part of the 64-bit time_t transition required to support 32-bit
> architectures in 2038 and beyond
> (https://wiki.debian.org/ReleaseGoals/64bit-time), we have identified
> reiserfsprogs as a source package shipping runtime libraries whose
> ABI
> either is affected by the change in size of time_t, or could not be
> analyzed via abi-compliance-checker (and therefore to be on the safe
> side we assume is affected).
> 
> 

Hi,

thanks for working on the time_t transistion.

But ReiserFS is too old. It still uses 32bit fields in it's superblock
and other metadata blocks.
And fsck is just writing out the return value of time(NULL) to the
superblock when the last check was run.

So I don't think it makes currently any problems. But it can't be made
64bit safe and so shouldn't be used at all in 2038 and beyond.

Luckly it has been already marked deprecated upstream and scheduled for
removal in Linux this year 2024

Only problem to directly RM reiserfsprogs is, that now btrfs-progs
depend on libreiserfscore0 due to btrfs-convert supporting ReiserFS.

Cheers
Felix

Bug#1055422: please package 545.xx with open source kernel module

[Felix Zielcke]

Source: nvidia-graphics-drivers
Severity: wishlist


NVIDIA has released the 545 branch of their drivers.
And also says now in the README[1]:

  Use of the open kernel modules on GeForce and Workstation GPUs should be 
considered Beta quality in this release and no longer requires setting of the 
"NVreg_OpenRmEnableUnsupportedGpus" nvidia.ko kernel module parameter. The open 
kernel modules are suitable for broad usage, and NVIDIA requests feedback on 
any issues encountered that are specific to them.


Would be nice to have this avaible in experimental.

Thanks in advance

[1] 
https://download.nvidia.com/XFree86/Linux-x86_64/545.29.02/README/kernel_open.html

Bug#1053920: suggests non-existent package phantomjs

[Felix Zielcke]

Package: yt-dlp
Version: 2023.10.13-1
Severity: minor


yt-dlp still suggests phantomjs, which has been removed over 3 years ago from 
Debian.

Bug#1053594: grub: KDE Neon installation on seperate partition is not recognized

[Felix Zielcke]

Control: reassign -1 grub2 2.06-13+deb12u1
Control: forcemerge 1038974 -1 

Am Samstag, dem 07.10.2023 um 10:43 +0200 schrieb Michael Josenhans:
> Hi,
> 
> grub was just a guess of the package name from my side. It should be
> grub 2:
> 
> The grub boot selection page says GNU Grub 2.06-13+deb12u1.
> 
> Br,
> 
> Michael
> 

Then this probable is a case of not installed and not (by default)
enabled os-prober.

So install os-prober if it's not already.

And in /etc/default/grub

GRUB_DISABLE_OS_PROBER=false

And last

sudo update-grub

os-prober won't be enabled by default anymore.

See https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1038974

Bug#1053594: grub: KDE Neon installation on seperate partition is not recognized

[Felix Zielcke]

Am Samstag, dem 07.10.2023 um 09:09 +0200 schrieb Michael Josenhans:
> Source: grub
> Version: 0.97-80
> Severity: normal
> X-Debbugs-Cc: m_josenh...@web.de
> 
> Dear Maintainer,
> 
> *** Reporter, please consider answering these questions, where
> appropriate ***
> 
>    * What led up to the situation?
> I updated debian with
> su
> apt update 
> apt upgrade
> 
>    * What exactly did you do (or not do) that was effective (or
>  ineffective)?
> grub from debian installation was installed during debian package
> update
> 
>    * What was the outcome of this action?
> debian version of grub is now installed (likely in MBR)
> This version does not show an option to start kde neon
>    * What outcome did you expect instead?
> the installed debian grub version detects KDE Neon and provides an
> option to start the installed KDE Neon besides the option to start
> debian
> 

Hi, 

what's the reason that you still use the old GRUB Legacy instead of
GRUB 2?

I suggest using GRUB 2 with os-prober installed.
Though you need to enable usage of os-prober in /etc/default/grub with

GRUB_DISABLE_OS_PROBER=false

GRUB 0.97 won't get any fixes from us anymore.

Bug#1051543: grub2: Fails to load normal.mod from a XFS v5 parition.

[Felix Zielcke]

Am Samstag, dem 09.09.2023 um 15:41 +0200 schrieb Sebastian Andrzej
Siewior:
> Package: grub2
> Version: 2.12~rc1-9
> Severity: Serious
> control: forwarded -1 https://savannah.gnu.org/bugs/?64376
> 
> I have a single XFS partition which contains the root filesystem and
> the
> boot partition. Since the recent upgrade to the 2.12 series I can't
> boot
> anymore because grub complains that it can't find normal.mod and
> remains in
> the rescue shell.
> The ls command kind of works. A ls in /boot/grub/i386-pc/ (where the
> normal.mod should be) shows a few files and then abort with the error
> message: 'error: invalid XFS directory entry'.
> 

Hi Sebastian,

there's now a patch from Jon DeVree upstream, which might fix this for
you. Is it possible for you to test his patch?

https://lists.gnu.org/archive/html/grub-devel/2023-09/msg00059.html

Bug#905094: Grub2 boot card dead

[Felix Zielcke]

On Fri, 3 Aug 2018 18:11:20 +0800 binnan hao 
wrote:
> More info on the issue:
> 
> The display is connected to motherboard via mDP cable. The memory
contains
> two 16gb memory sticks.
> I don't know whether the issue has something to do with the
resolution. The
> resolution of Grub2 is 1920*1080 when Secure Boot is enabled, and it
is
> 1024*768 when Secure Boot is disabled.
> This patch still does not work:
>
https://bugs.launchpad.net/ubuntu/+source/grub2/+bug/1785033/+attachment/5170756/+files/0001-i386-linux-Add-support-for-ext_lfb_base.patch
> 
> Hope this info helps a bit to fix the issue.
> 

Does a recent grub2 version now works for you?

Bug#1041722: steam is incompatible with libgudev 238-2

[Felix Zielcke]

Am Montag, dem 24.07.2023 um 19:43 +0100 schrieb Simon McVittie:
> I'm surprised that you're seeing this crash, because it seems you
> already
> have the factors that were mentioned in the upstream bug as potential
> workarounds: libnm0:i386 is installed, and so is libudev0:i386.
> 
> Are these things that you installed as a (successful) workaround, but
> were
> not present at the time that you saw the crash you're reporting?

Actually libnm0:i386 wasn't installed.
And yes, this fixed it now.

So it's just a problem if you don't have all Recommends installed.

Thanks for your hint

Bug#1023205: bullseye-pu: package memtest86+/6.00-1

[Felix Zielcke]

(Adding Fabio)

Am Sonntag, dem 23.07.2023 um 13:42 +0100 schrieb Jonathan Wiltshire:
> Control: tag -1 moreinfo
> 
> Hi,
> 
> On Mon, Oct 31, 2022 at 05:38:07PM +0100, Felix Zielcke wrote:
> > memtest86+ 5.01-3.1 in stable is very old and doestn't run
> > correctly
> > on recent hardware.
> 
> In the meantime I see there has been a backport of 6 to bullseye-
> backports.
> Is it still the best course of action to remove 5.01-3.1 from stable,
> or
> does it work well enough on old hardware to be worth keeping?
> 
> Thanks,
> 

Hi,

actually now I think we could just keep it in bullseye. Anyone with
recent hardware could get it from backports and probable also will (if
not have already) upgrade to bookworm.
Or what do you think Fabio? Should the old memtest still be removed
from oldstable?

I at least didn't get any complains about the old version, since I
became a co-maintainer of memtest86+

Bug#1041722: steam is incompatible with libgudev 238-2

[Felix Zielcke]

forwarded -1 https://github.com/ValveSoftware/steam-for-linux/issues/9805
thanks

Am Samstag, dem 22.07.2023 um 18:46 +0100 schrieb Simon McVittie:
> On Sat, 22 Jul 2023 at 17:43:56 +0200, Felix Zielcke wrote:
> > Steam crashes on startup with libgudev 238-2 currently in unstable.
> 
> Debian has no control over what's in the proprietary Steam client, so
> please report this sort of thing to
> <https://github.com/ValveSoftware/steam-for-linux/issues>.
> 
> Thanks,
>     smcv

Hi,

this seems to have been already reported upstream 2 weeks ago.
I guess even if on Debian side, nothing can be changed, it's still
useful to have the problem at least known. Which was mainly my
motivation.
As soon as it enters testing more people are affected

Bug#1041722: steam is incompatible with libgudev 238-2

[Felix Zielcke]

Package: steam-installer
Version: 1:1.0.0.78~ds-2
Severity: grave

Steam crashes on startup with libgudev 238-2 currently in unstable.
libgudev 237-2 from testing works fine with Steam.

Console only shows this for the crash:

Assertion 'device' failed at src/libsystemd/sd-device/device-private.c:103, 
function device_get_tags_generation(). Aborting.
crash_20230722173957_25.dmp[26236]: Uploading dump (out-of-process)

No stack trace or anything else which differs between working and crashing 
steam.


-- System Information:
Debian Release: trixie/sid
  APT prefers unstable
  APT policy: (500, 'unstable'), (499, 'experimental'), (499, 'testing')
Architecture: amd64 (x86_64)
Foreign Architectures: i386

Kernel: Linux 6.3.0-2-amd64 (SMP w/12 CPU threads; PREEMPT)
Kernel taint flags: TAINT_PROPRIETARY_MODULE, TAINT_OOT_MODULE, 
TAINT_UNSIGNED_MODULE
Locale: LANG=de_DE.UTF-8, LC_CTYPE=de_DE.UTF-8 (charmap=UTF-8), LANGUAGE not set
Shell: /bin/sh linked to /usr/bin/dash
Init: systemd (via /run/systemd/system)

Versions of packages steam-installer depends on:
ii  debconf [debconf-2.0]  1.5.82
ii  steam-libs 1:1.0.0.78~ds-2
ii  steam-libs-i3861:1.0.0.78
ii  yad0.40.0-1+b1
ii  zenity 3.44.0-3

steam-installer recommends no packages.

steam-installer suggests no packages.

Versions of packages steam-libs depends on:
ii  ca-certificates  20230311
ii  curl 7.88.1-10
ii  file 1:5.44-3
ii  libc62.37-6
ii  libcrypt11:4.4.35-1
ii  libgcc-s1 [libgcc1]  13.1.0-9
ii  libgl1   1.6.0-1
ii  libgl1-mesa-dri  23.1.3-1
ii  libgpg-error01.46-1
ii  libstdc++6   13.1.0-9
ii  libudev1 254~rc2-3
ii  libva-x11-2  2.19.0-1
ii  libva2   2.19.0-1
ii  libxcb-dri3-01.15-1
ii  libxcb1  1.15-1
ii  libxi6   2:1.8-1+b1
ii  libxinerama1 2:1.1.4-3
ii  xz-utils 5.4.1-0.2

Versions of packages steam-libs recommends:
ii  fontconfig   2.14.1-4
ii  fonts-liberation 1:2.1.5-3
ii  libasound2-plugins   1.2.7.1-1
ii  libegl1  1.6.0-1
ii  libexpat12.5.0-2
ii  libfontconfig1   2.14.1-4
ii  libgbm1  23.1.3-1
ii  libsdl2-2.0-02.28.1+dfsg-1
ii  libva-drm2   2.19.0-1
ii  libva-glx2   2.19.0-1
ii  libx11-6 2:1.8.6-1
ii  libx11-xcb1  2:1.8.6-1
ii  libxau6  1:1.0.9-1
ii  libxcb-dri2-01.15-1
ii  libxcb-glx0  1.15-1
ii  libxcb-present0  1.15-1
ii  libxcb-sync1 1.15-1
ii  libxdamage1  1:1.1.6-1
ii  libxdmcp61:1.1.2-3
ii  libxext6 2:1.3.4-1+b1
ii  libxfixes3   1:6.0.0-2
ii  libxss1  1:1.2.3-1
ii  libxxf86vm1  1:1.1.4-1+b2
ii  mate-terminal [x-terminal-emulator]  1.26.1-1
pn  mesa-vulkan-drivers  
pn  steam-devices
pn  va-driver-all | va-driver
ii  xdg-desktop-portal   1.16.0-2
ii  xdg-desktop-portal-gtk [xdg-desktop-portal-backend]  1.14.1-1
ii  xdg-utils1.1.3-4.1
ii  xterm [x-terminal-emulator]  384-1
ii  zenity   3.44.0-3

Versions of packages steam-libs suggests:
ii  libudev0200-1
ii  nvidia-driver-libs  525.125.06-1
ii  nvidia-vulkan-icd   525.125.06-1
ii  pipewire0.3.74-1

Versions of packages steam-libs-i386 depends on:
ii  libc62.37-6
ii  libcrypt11:4.4.35-1
ii  libegl1  1.6.0-1
ii  libgbm1  23.1.3-1
ii  libgcc-s1 [libgcc1]  13.1.0-9
ii  libgl1   1.6.0-1
ii  libgl1-mesa-dri  23.1.3-1
ii  libgpg-error01.46-1
ii  libstdc++6   13.1.0-9
ii  libudev0 200-1
ii  libudev1 254~rc2-3
ii  libx11-6 2:1.8.6-1
ii  libxcb-dri3-01.15-1
ii  libxcb1  1.15-1
ii  libxinerama1 2:1.1.4-3

Versions of packages steam-libs-i386 recommends:
ii  libasound2-plugins 1.2.7.1-1
ii  libfontconfig1 

Bug#1035744: memtest86+: new upstream version

[Felix Zielcke]

Am Montag, dem 08.05.2023 um 17:44 +0200 schrieb Fabio Fantoni:
> Il 08/05/2023 17:22, Christoph Anton Mitterer ha scritto:
> > Package: memtest86+
> > Version: 6.10-4
> > Severity: wishlist
> > 
> > Hey.
> > 
> > 6.20 is out :-)
> > 
> > Cheers,
> > Chris.
> 
> Hi, Felix Zielcke already uploaded 6.20-1 into experimental, the new 
> version for bookworm is too late, there is the "hard freeze" and I 
> suppose Felix uploaded to experimental instead unstable to make
> possible 
> an urgent fixes upload for bookworm if will be needed, even if I
> suppose 
> there is very low probability to spot RC bugs on 6.10-4
> 

Correct.
I don't think either we need another upload for bookform.
But better be safe. And also the freeze policy says to avoid uploads to
unstable which aren't meant for bookworm

Bug#1031511: RFS: reiserfsprogs/1:3.6.27-5 -- User-level tools for ReiserFS filesystems

[Felix Zielcke]

Am Freitag, dem 07.04.2023 um 16:41 +0200 schrieb Bastian Germann:
> Thanks for the update.

Thanks very much for uploading!
Patience pays off.

Bug#1032375: memtest86+: fails to work with Secure Boot enabled

[Felix Zielcke]

Control: severity -1 wishlist

Am Sonntag, dem 05.03.2023 um 23:20 +1100 schrieb Russell Coker:
> Package: memtest86+
> Version: 6.10-4
> Severity: normal
> 
> If you select the EFI version of memtest86+ from GRUB when Secure
> Boot is
> enabled then it gives the message "error: bad shim signature" and
> fails back
> to GRUB.
> 
> Please provide a signed version so Secure Boot doesn't have to be
> disabled to
> run it.
> 

Hi,

this has been already talked on IRC in #debian-efi.
First step is to get the ok from the shim-review process.
I created already an issue here:

https://github.com/rhboot/shim-review/issues/314

Bug#1031511: RFS: reiserfsprogs/1:3.6.27-5 -- User-level tools for ReiserFS filesystems

[Felix Zielcke]

Package: sponsorship-requests
Severity: normal

Dear mentors,

I am looking for a sponsor for my package "reiserfsprogs":

 * Package name : reiserfsprogs
   Version  : 1:3.6.27-5
   Upstream contact : reiserfs-de...@vger.kernel.org
 * URL  : 
https://www.kernel.org/pub/linux/kernel/people/jeffm/reiserfsprogs
 * License  : GPL-2
   Section  : admin

The source builds the following binary packages:

  reiserfsprogs - User-level tools for ReiserFS filesystems
  libreiserfscore0 - ReiserFS core library
  libreiserfscore-dev - ReiserFS core library - headers
  reiserfsprogs-udeb - User-level tools for ReiserFS filesystems
  mkreiserfs-udeb - User-level tools for ReiserFS filesystems

To access further information about this package, please visit the
following URL:

  https://mentors.debian.net/package/reiserfsprogs/

Alternatively, you can download the package with 'dget' using this
command:

  dget -x
https://mentors.debian.net/debian/pool/main/r/reiserfsprogs/reiserfsprogs_3.6.27-5.dsc

Changes since the last upload:

 reiserfsprogs (1:3.6.27-5) experimental; urgency=medium
 .
   * Build and ship libreiserfsprogs. (Closes: #1031342)
   * Bump policy to 4.6.2.
   * Rewrite d/copyright in copyright-format 1.0.
   * Add Rules-Requires-Root: no.
   * Update watch file to use version 4 and verify upstream signature.

Regards,
-- 
  Felix Zielcke

Bug#1031342: Bug#1030950: btrfs-convert is built without support for reiserfs

[Felix Zielcke]

On Wed, 15 Feb 2023 12:38:15 +0100 Adam Borowski 
wrote:
> 
> On Thu, Feb 09, 2023 at 10:07:56PM +0100, Oswald Buddenhagen wrote:
> > Package: btrfs-progs
> > Version: 6.1.2-1
> > Severity: normal
> > 
> > for the purpose of helping people to move away from reiserfs, it
would 
> > make sense to actually build btrfs-convert with support for it.
> > 
> > the catch is that libreiserfscore is not packaged separately;
rather, 
> > it's built into reiserfsprogs. i guess factoring out a static-only 
> > libreiserfscore-dev would make sense.
> 
> This would require help from the src:reiserfsprogs side.  I'm thus
cloning
> accordingly.
> 
> Too bad, the freeze blocks the usual ways of introducing such a
library. 
> There are ways to work around that but none are pretty.
> 
> But, it's Felix (reiser maintainer) who knows how the library looks
like;
> compiling against a library is trivial in comparison.  Thus, it's him
who
> can enlighten us.
> 
> 

Hi,

When uploading -4 I didn't think the lib would be ever needed. So I
just removed it.
I packaged it now the proper way and uploaded -5 to mentors.
I'm just a DM so I'll need a sponsor for binNEW.

Adam do you have interest in doing this one upload or should I file a
RFS?

Bug#1031231: tries to overwrite /etc/cron.yearly/.placeholder from systemd-cron

[Felix Zielcke]

Package: cron-daemon-common
Version: 3.0pl1-159
Severity: serious

Hi,

cron-daemon-common can't be upgraded if systemd-cron is also installed:

Preparing to unpack .../cron-daemon-common_3.0pl1-159_all.deb ...
Unpacking cron-daemon-common (3.0pl1-159) over (3.0pl1-156) ...
dpkg: error processing archive 
/var/cache/apt/archives/cron-daemon-common_3.0pl1-159_all.deb (--unpack):
 trying to overwrite '/etc/cron.yearly/.placeholder', which is also in package 
systemd-cron 1.15.19-4
Errors were encountered while processing:
 /var/cache/apt/archives/cron-daemon-common_3.0pl1-159_all.deb
E: Sub-process /usr/bin/dpkg returned an error code (1)


AFAICS this hasn't been fixed in the already uploaded but not yet avaible 
3.0pl1-160

Bug#989001: memtest86+: Fails to run in Grub graphical(?) mode?

[Felix Zielcke]

Control: tag -1 moreinfo

On Sun, 23 May 2021 09:02:40 +0900 Junichi Uekawa 
wrote:
> Package: memtest86+
> Version: 5.01-3.1
> Severity: normal
> 
> Dear Maintainer,
> 
> I think I default installed Debian bullseye and Grub is configured to
> use graphical framebuffer and render text. When invoked from there
> memtest86+ doesn't seem to update the screen at all (presumably
trying
> to write to text buffer?).
> 

We have now memtest86+ 6.10 which has many rewritten code.
Can you please test if that works now fine?

Bug#1026317: new upstream version 0.0.8

[Felix Zielcke]

Package: nvidia-vaapi-driver
Version: 0.0.5-1+b1
Severity: wishlist

Hi,

0.0.8 has been now released, whereas unstable still has 0.0.5.

TIA,
Felix

Bug#1025493: firefox crashes instantly at start

[Felix Zielcke]

Am Dienstag, dem 06.12.2022 um 21:07 +0100 schrieb VA:
> Le 06/12/2022 à 19:37, Felix Zielcke a écrit :
> > I have exactly the same problem since Mesa 22.3.0 was uploaded to
> > unstable.
> > Downgrading all src:mesa packages to version 22.2.4 from testing
> > fixes
> > this for me.
> > I've got a Nvidia graphic card and use the Nvidia driver packages
> > from
> > Debian. It doestn't matter at all if nvidia-vaapi-driver is
> > installed
> > or removed/purged.
> 
> Seems mesa 22.3.0-2 fixed the problem for me. What about you?
> Maybe it was
> https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1025312

Thanks. Haven't seen that yet.
Yes it fixes it also for me.

Bug#1025493: firefox crashes instantly at start

[Felix Zielcke]

On Mon, 5 Dec 2022 20:31:02 +0100 VA  wrote:
> Package: firefox
> Version: 107.0.1-1
> Severity: important
> 
> It's not a broken profile, even when running "firefox --
ProfileManager" 
> or "firefox --safe-mode":
> 
> [GFX1-]: glxtest: VA-API test failed: failed to initialise VAAPI
connection.
> ATTENTION: default value of option mesa_glthread overridden by
environment.
> ATTENTION: default value of option mesa_glthread overridden by
environment.
> ATTENTION: default value of option mesa_glthread overridden by
environment.
> ExceptionHandler::GenerateDump cloned child 231737
> ExceptionHandler::SendContinueSignalToChild sent continue signal to
child
> ExceptionHandler::WaitForContinueSignal waiting for continue
signal...
> 
> 

I have exactly the same problem since Mesa 22.3.0 was uploaded to
unstable.
Downgrading all src:mesa packages to version 22.2.4 from testing fixes
this for me.
I've got a Nvidia graphic card and use the Nvidia driver packages from
Debian. It doestn't matter at all if nvidia-vaapi-driver is installed
or removed/purged. 

Bug#1023638: memtest86+: README.Debian: wrong file names for EFI images

[Felix Zielcke]

Control: tag -1 pending

Am Dienstag, dem 08.11.2022 um 07:28 +0100 schrieb Michael Prokop:
> Package: memtest86+
> Version: 6.00-1
> Severity: minor
> 
> Quoting from /usr/share/doc/memtest86+/README.Debian:
> 
> > Multiple binary images are provided:
> > 
> >   - A legacy bios 32bit /boot/memtest86+x32.bin that uses Linux
> > zImage
> >     boot protocol.
> > 
> >   - A legacy bios 64bit /boot/memtest86+x64.bin that uses Linux
> > zImage
> >     boot protocol.
> > 
> >   - A 32bit EFI Image /boot/memtest86+x32.bin
> > 
> >   - A 64bit EFI Image /boot/memtest86+x64.bin
> 
> Those are twice the same file names (e.g. /boot/memtest86+x64.bin),
> I suppose the later ones are meant to refer to
> /boot/memtest86+x32.efi + /boot/memtest86+x64.efi?
> 
> regards
> -mika-


Thanks for the hint.
Fixed in git for next upload

Bug#1023205: bullseye-pu: package memtest86+/6.00-1

[Felix Zielcke]

Package: release.debian.org
Severity: normal
Tags: bullseye
User: release.debian@packages.debian.org
Usertags: pu
X-Debbugs-Cc: fziel...@z-51.de, fantonifa...@tiscali.it

[ Reason ]

memtest86+ 5.01-3.1 in stable is very old and doestn't run correctly
on recent hardware.

[ Impact ]

Fail to run memtest86+ on their hardware.

[ Tests ]

manually tested.

[ Risks ]

Completely rewritten from scratch. So could have bugs not yet known.


[ Checklist ]
  [X] *all* changes are documented in the d/changelog
  [X] I reviewed all changes and I approve them
  [X] attach debdiff against the package in (old)stable
  [X] the issue is verified as fixed in unstable

[ Changes ]

Comeplete new upstream version.
Rewritten GRUB integration scripts.
New ISO/USB bootable Images.

[ Other info ]

I requested a backport [1] but Thomas Goirand (zigo) recommend me to ask you 
for a
complete update in stable [2].
If this will be rejected, I recommend to remove memtest86+ from stable
and hopefully somebody uploads the new version to backports.
As a DM I can't do this myself.

[1] https://lists.debian.org/debian-backports/2022/10/msg00056.html
[2] https://lists.debian.org/debian-backports/2022/10/msg00061.html

Bug#546219: memtest86+: fails to load from pxelinux with default filename

[Felix Zielcke]

On Fri, 11 Sep 2009 11:13:35 -0700 Vagrant Cascadian
 wrote:
> Package: memtest86+
> Version: 2.01-1.1
> Severity: normal
> 
> when trying to network boot memtest86+.bin using pxelinux (from
> syslinux-common), it fails to run. on machines with a floppy drive,
it polls
> the floppy drive repeatedly. eventually, it spits out out "8000" over
and over
> again.
> 
> a workaround is to symlink or copy memtest86+.bin to memtest86+, and
it works
> fine, although having to rename or symlink the binary to network boot
> memtest86+ seems a bit of unnecessary hassle.
> 
> i also experienced the same problem with version 2.11-3 of
memtest86+, as well
> as versions of memtest86 in lenny and sid.
> 
> thanks for maintaining memtest86+, we use it extensively at Freegeek!
> http://freegeek.org
> 
> live well,
>   vagrant
> 
> 

Hi,

this bug is very old.
Can you or anybody else confirm if current version 5.31 or better 6.00
in sid works now fine with pxelinux? 

Bug#1008263: pcmemtest is goging to replace memtest86+ upstream

[Felix Zielcke]

Control: severity -1 serious

Am Freitag, dem 09.09.2022 um 10:55 -0400 schrieb Antoine Beaupré:
> On 2022-03-25 17:12:42, Felix Zielcke wrote:
> > I'm not yet sure if I should file a removal bug for pcmemtest.
> > But I think I'll just wait and see if that is necessary
> 
> I think you should: right now pcmemtest *will* ship with Debian
> bookworm, and I don't think that's right if upstream development has
> shifted to memtest86+...
> 
> Instead of maintaining this package, it seems to me efforts should be
> made to bring memtest86+ 6 into bookworm (which it is currently not,
> it
> seems stuck in experimental).
> 
> A fair way to keep this package out of bookworm would be to raise the
> severity of this bug report to `serious`, which should kick it out of
> bookworm in no time.
> 
> Then, of course, an RM request would be appropriate as well.
> 
> Thanks for maintaining those packages!
> 
> A.
> 

Thanks for the reminder.
I wasn't sure if I should wait until the new memtest86+ gets out of
beta and uploaded to unstable. But yeah, maybe it's better to just file
the RM now

Regards,
Felix

Bug#1019451: RM: pcmemtest -- ROM; dead upstream, replaced by memtest86+ v6.00

[Felix Zielcke]

Package: ftp.debian.org
Severity: normal


Hi,

pcmemtest was a fork of memtest86+ v.5.31b.
Upstream of it has now joined development of memtest86+ and abandoned pcmemtest.
memtest86+ 6.00 in experimental has merged back the code changes from pcmemtest.
Will hit unstable as soon as it goes out of beta.
So IMHO pcmemtest is now useless and shouldn't be in bookworm release and even 
sid.

TIA
Felix

Bug#1016189: RM: memtest86 -- RoQA; obsolete, buggy, alternatives exist

[Felix Zielcke]

Am Freitag, dem 29.07.2022 um 00:05 +0200 schrieb Chris Hofstaedtler:
> Package: ftp.debian.org
> Severity: normal
> X-Debbugs-Cc: m...@debian.org, fantonifa...@tiscali.it,
> fziel...@z-51.de
> 
> Dear FTP Masters,
> 
> please remove memtest86. As stated by the last maintainer in #969192,
> alternatives exist. Actually it appears memtest86+ and pcmemtest have
> been merged, and memtest86+ 6.0 will be the pcmemtest code base.
> Having an old, unmaintained memory tester which, according to bug
> reports, does not even start anymore helps no one. Lets get rid of
> this
> variant.
> 
> I'll tag this moreinfo in a moment, so everyone interested has enough
> time to say something about this bug. I'll untag it in a month or so.
> 
> Best,
> Chris

AFAIK even the new memtest86+ 6.0, should run fine on old systems.
I'm not sure pcmemtest supports them.

But as soon as the pcmemtest based memtest86+ has been uploaded to
unstable, I'll file a removal request for pcmemtest. 

So I don't see either a reason to still keep the very old memtest86 in
Debian.

Regards,
Felix

Bug#1005197: pcmemtest: please make the build partly reproducible

[Felix Zielcke]

Am Freitag, dem 25.03.2022 um 14:13 -0700 schrieb Vagrant Cascadian:
> On 2022-03-25, Felix Zielcke wrote:
> > Am Mittwoch, dem 23.02.2022 um 09:36 +0100 schrieb Thomas Schmitt:
> > I totally forgot about this. Sorry!
> > 
> > I just tried to test it with TZ set.
> > But I always get the same binaries. No matter to what I change TZ
> > or
> > /etc/timezone between the builds.
> > 
> > So is this just a bullseye problem? unstable has a newer mtools
> > 
> > I'll try to test this in stable chroot the next days
> 
> I can reproduce the issue in a debian sid chroot with pcmemtest 1.5-3
> from debian, using:
> 
>   reprotest --verbose --min-cpus=1 --vary=-user_group,-domain_host,-
> fileordering auto -- null
> 
> Passing TZ=UTC in three different ways, exporting TZ=UTC from
> debian/rules, exporting TZ=UTC from the upstream Makefiles, and
> prepending the mcopy calls in the upstream Makefiles. All three
> approaches are below:

Thanks Thomas and Vagrant.
I finally could test this.
Seems like an export TZ=UTC directly before the mcopy call doestn't
work. And I wrongly thought stuff like TZ=UTC+1 works too.

I export it now globally at the start of both Makefiles

Oh and by the way, in case you don't know it already:

memtest86+ 6.0 will be based on pcmemtest. And this means development
of pcmemtest will stop.

But the reproducible work done here is also good for memtest86+. :)
Where I'm the new co-maintainer.

Cheers,
Felix

Bug#1008263: pcmemtest is goging to replace memtest86+ upstream

[Felix Zielcke]

Am Freitag, dem 25.03.2022 um 16:59 +0100 schrieb Christoph Anton
Mitterer:
> Hey.
> 
> Just for you information:
> 
> Memtest86+ upstream (Samuel D. ) had already told me that
> a while
> ago... and pcmemtest upstream seems to have confirmed it now:
> https://github.com/martinwhitaker/pcmemtest/issues/13#issuecomment-1079164505
> 
> The current pcmemtest will "replace" memtest86+ (AFAIU under the name
> of the
> latter) in its next major version.
> 
> 
> Cheers,
> Chris.

Hi Chris,

thanks for your report.
I already agreed with Fabio to Co-Maintain memtest86+ with him.
Actually it's memtest86+ which will replace pcmemtest.
pcmemtest won't be developed any further.

I'm not yet sure if I should file a removal bug for pcmemtest.
But I think I'll just wait and see if that is necessary

Cheers,
Felix

Bug#1005197: pcmemtest: please make the build partly reproducible

[Felix Zielcke]

Control: tags -1 pending

Am Freitag, dem 11.02.2022 um 22:46 +0100 schrieb Thomas Schmitt:
> Hi,
> 
> Chris Lamb wrote:
> > Did you try the --invariant flag?
> 
> Well, i step aside and let this question reach Felix. :))
> 
>   https://manpages.debian.org/unstable/dosfstools/mkdosfs.8.en.html
> says that this is what we need if my theory about the second
> difference
> is correct:
> 
>   --invariant
>     Use constants for normally randomly generated or time based data
>     such as volume ID and creation time. Multiple runs of mkfs.fat on
>     the same device create identical results with this option.
> 
> 
> So the options to be added to the mkdosfs runs in the hope for a
> fully
> reproducible ISO are:
> 
>   -i 12345678 --invariant
> 
> If a more more individual -i number is desired, one could use
> something
> like
> 
>   -i $(printf '%8.8x' "$SOURCE_DATE_EPOCH" | head -c 8)
> 
> 

Wow. Thanks very much to you both.
This is the solution. I would never come up that fast with it.



> Have a nice day :)
> 
Have a nice weekend :)

Felix

Bug#1005197: pcmemtest: please make the build partly reproducible

[Felix Zielcke]

Am Freitag, dem 11.02.2022 um 11:41 +0100 schrieb Thomas Schmitt:
> Hi,
> 
> Felix Zielcke wrote:
> > I modifed the patch now to use --set_all_file_dates.
> 
> I wonder whether the "file list" in "data.tar.xz" of
>  
> https://tests.reproducible-builds.org/debian/rb-pkg/unstable/amd64/diffosc
> ope-results/pcmemtest.html
> is made from the files in the ISO or from the input files on hard
> disk.
> 
> In the latter case, it would be better to use the solution of Chris
> which enforces dates on hard disk.
> But then this solution should also enforce user id and group id
> numbers
> on hard disk.
> 
> > 
Ah ok. I can try that.

> > diffoscope still tells me some differences in the ISOs.
> 
> Is there a chance to quote some of the found differences here ?
> If it's about meta data of the ISO then i would be the person to
> decode
> them and to make first theories from where the deviations might come.
> 
> 
Here's the output for the 64bit ISO:

 │ ├── ./usr/lib/pcmemtest/memtestx64.iso
│ │ │┄ Format-specific differences are supported for ISO 9660 CD images but no 
file-specific differences were detected; falling back to a binary diff. file(1) 
reports: ISO 9660 CD-ROM filesystem data (DOS/MBR boot sector) 'PCMemTest64' 
(bootable)
│ │ │ @@ -96508,15 +96508,15 @@
│ │ │  00178fb0:          
│ │ │  00178fc0:          
│ │ │  00178fd0:          
│ │ │  00178fe0:          
│ │ │  00178ff0:          
│ │ │  00179000: eb3c 906d 6b66 732e 6661 7400 0204 0100  .<.mkfs.fat.
│ │ │  00179010: 0200 0200 20f8 0600 2000 0200     ... ...
│ │ │ -00179020:   8000 296c 13ae 4d4d 454d 5445  ..)l..MMEMTE
│ │ │ +00179020:   8000 29d6 8629 594d 454d 5445  ..)..)YMEMTE
│ │ │  00179030: 5354 2d45 5350 4641 5431 3220 2020 0e1f  ST-ESPFAT12   ..
│ │ │  00179040: be5b 7cac 22c0 740b 56b4 0ebb 0700 cd10  .[|.".t.V...
│ │ │  00179050: 5eeb f032 e4cd 16cd 19eb fe54 6869 7320  ^..2...This 
│ │ │  00179060: 6973 206e 6f74 2061 2062 6f6f 7461 626c  is not a bootabl
│ │ │  00179070: 6520 6469 736b 2e20 2050 6c65 6173 6520  e disk.  Please 
│ │ │  00179080: 696e 7365 7274 2061 2062 6f6f 7461 626c  insert a bootabl
│ │ │  00179090: 6520 666c 6f70 7079 2061 6e64 0d0a 7072  e floppy and..pr
│ │ │ @@ -96922,16 +96922,16 @@
│ │ │  0017a990:          
│ │ │  0017a9a0:          
│ │ │  0017a9b0:          
│ │ │  0017a9c0:          
│ │ │  0017a9d0:          
│ │ │  0017a9e0:          
│ │ │  0017a9f0:          
│ │ │ -0017aa00: 4d45 4d54 4553 542d 4553 5008  a750  MEMTEST-ESPP
│ │ │ -0017aa10: 4b54 4b54  a750 4b54     KTKT...PKT..
│ │ │ +0017aa00: 4d45 4d54 4553 542d 4553 5008  0951  MEMTEST-ESPQ
│ │ │ +0017aa10: 4b54 4b54  0951 4b54     KTKT...QKT..
│ │ │  0017aa20: 4546 4920 2020 2020 2020 2010  186a  EFIj
│ │ │  0017aa30: 4954 4954  186a 4954 0200    ITIT...jIT..
│ │ │  0017aa40:          
│ │ │  0017aa50:          
│ │ │  0017aa60:          
│ │ │  0017aa70:          
│ │ │  0017aa80:          

Bug#1005197: pcmemtest: please make the build partly reproducible

[Felix Zielcke]

Am Donnerstag, dem 10.02.2022 um 16:24 -0800 schrieb Chris Lamb:
> Hi Thomas,
> 
> > > Have you had a look at the diffoscope output after this patch is
> > > applied?
> > 
> > Where can a curious bystander get that look ?
> 
> I was referring to a hypothetical diff that you might generate
> locally; updating the result on tests.reproducible-builds.org would
> require a new upload. :)
> 
> > i see in the isoinfo output only differences of user id, group id,
> > and timestamps of /boot and /boot/floppy.img.
> [...]
> > https://bugs.debian.org/cgi-bin/bugreport.cgi?att=1;bug=1005197;filename=pcmemtest.diff.txt;msg=5
> > should fix both.
> 
> It perhaps should, but alas it does not. When I apply my patch, the
> user ID, group ID and timestamp differences do disappear for me too,
> but that is not the only difference I see. I mean, hence why I said
> that my patch "does not make the ISOs entirely reproducible; there is
> another part or parts of the image that elude me right now". :)
> 
> I wouldn't jump to the conclusion that it is a bug in xorriso just
> yet. It might be reproducible for you locally, but it is likely I am
> varying more things between my two builds. And even more on
> tests.reproducible-builds.org.
> 
> The next step might be to upload with this patch so we can both work
> with the same output on tests.reproducible-builds.org.
> 
> >   --set_all_file_dates "=$SOURCE_DATE_EPOCH"
> 
> Ah, neat. :)  Yes, of course, feel free to use this over touch(1).
> 
> 

Hi Thomas and Chris,

thanks very much for your efforts.
I modifed the patch now to use --set_all_file_dates.

diffoscope still tells me some differences in the ISOs. I built it
multiple times with cowbuilder.

As soon as it migrated to bookworm I'll do an upload with the patch.

Regards,
Felix

Bug#1005197: pcmemtest: please make the build partly reproducible

[Felix Zielcke]

Am Dienstag, dem 08.02.2022 um 12:06 -0800 schrieb Chris Lamb:
> Hi,
> 
> Whilst working on the Reproducible Builds effort [0] we noticed that
> pcmemtest could not be built reproducibly.
> 
> This is because the generated ISOs inherit the uid/gid of the build
> process, as well as the modification times of (at least) floppy.img
> 
> Patch attached that modifies the two Makefiles involved, although
> this
> does not make the ISOs entirely reproducible; there is another part
> or parts of the image that elude me right now.
> 
>  [0] https://reproducible-builds.org/
> 
> 
> Regards,
> 

Hi Chris,

thanks for your patch. Just committed it.
Do you or anyone else have a hint how to make the ISOs fully
reproducible? How to do this is totally new to me.

Regards,
Felix

Bug#1002825: fails to detect write cache on SATA disks

[Felix Zielcke]

Package: src:linux
Version: 5.15.5-2
Severity: important
Tags: upstream fixed-upstream
Forwarded: https://bugzilla.kernel.org/show_bug.cgi?id=215137

Kernel 5.15.5 fails to detect write cache of SATA disks:

# dmesg|grep sda
[  +0,003954] sd 0:0:0:0: [sda] 1953525168 512-byte logical blocks: (1.00 
TB/932 GiB)
[  +0,001724] sd 0:0:0:0: [sda] 4096-byte physical blocks
[  +0,001840] sd 0:0:0:0: [sda] Write Protect is off
[  +0,001796] sd 0:0:0:0: [sda] Mode Sense: 00 3a 00 00
[  +0,001795] sd 0:0:0:0: [sda] Asking for cache data failed
[  +0,001782] sd 0:0:0:0: [sda] Assuming drive cache: write through
[  +0,013566]  sda: sda1
[  +0,018629] sd 0:0:0:0: [sda] Attached SCSI disk

This breaks write barriers. And could result in an unmountable btrfs
filesystem on a crash or otherwise unclean shutdown.

It's fixed upstream in 5.15.6 and commit 
c749301ebee82eb5e97dec14b6ab31a4aabe37a6


-- Package-specific info:
** Version:
Linux version 5.15.0-2-amd64 (debian-ker...@lists.debian.org) (gcc-11 (Debian 
11.2.0-13) 11.2.0, GNU ld (GNU Binutils for Debian) 2.37) #1 SMP Debian 
5.15.5-2 (2021-12-18)

** Command line:
BOOT_IMAGE=/vmlinuz-5.15.0-2-amd64 
root=UUID=de343167-b5ff-4758-aed3-7000e6e9e5d4 ro

** Tainted: POE (12289)
 * proprietary module was loaded
 * externally-built ("out-of-tree") module was loaded
 * unsigned module was loaded

** Kernel log:
[  124.330665] systemd-journald[1113]: Received client request to flush runtime 
journal.
[  124.331901] RAPL PMU: API unit is 2^-32 Joules, 1 fixed counters, 163840 ms 
ovfl timer
[  124.333070] RAPL PMU: hw unit of domain package 2^-16 Joules
[  124.797362] input: Power Button as 
/devices/LNXSYSTM:00/LNXSYBUS:00/PNP0C0C:00/input/input16
[  124.799011] ACPI: button: Power Button [PWRB]
[  124.799069] input: PC Speaker as /devices/platform/pcspkr/input/input17
[  124.800366] input: Power Button as 
/devices/LNXSYSTM:00/LNXPWRBN:00/input/input18
[  124.802592] ACPI: button: Power Button [PWRF]
[  124.805784] sp5100_tco: SP5100/SB800 TCO WatchDog Timer Driver
[  124.807280] sp5100-tco sp5100-tco: Using 0xfed80b00 for watchdog MMIO address
[  124.807729] sd 0:0:0:0: Attached scsi generic sg0 type 0
[  124.808526] sp5100-tco sp5100-tco: Watchdog hardware is disabled
[  124.809826] sd 1:0:0:0: Attached scsi generic sg1 type 0
[  124.812894] sd 2:0:0:0: Attached scsi generic sg2 type 0
[  124.815192] sr 3:0:0:0: Attached scsi generic sg3 type 5
[  124.818088] ccp :09:00.1: enabling device ( -> 0002)
[  124.819510] ccp :09:00.1: ccp: unable to access the device: you might be 
running a broken BIOS.
[  124.862462] input: HDA NVidia HDMI/DP,pcm=3 as 
/devices/pci:00/:00:03.1/:07:00.1/sound/card0/input19
[  124.862611] kvm: Nested Virtualization enabled
[  124.863707] input: HDA NVidia HDMI/DP,pcm=7 as 
/devices/pci:00/:00:03.1/:07:00.1/sound/card0/input20
[  124.864896] SVM: kvm: Nested Paging enabled
[  124.864917] SVM: Virtual VMLOAD VMSAVE supported
[  124.866164] input: HDA NVidia HDMI/DP,pcm=8 as 
/devices/pci:00/:00:03.1/:07:00.1/sound/card0/input21
[  124.867370] SVM: Virtual GIF supported
[  124.868635] input: HDA NVidia HDMI/DP,pcm=9 as 
/devices/pci:00/:00:03.1/:07:00.1/sound/card0/input22
[  124.873679] input: HDA NVidia HDMI/DP,pcm=10 as 
/devices/pci:00/:00:03.1/:07:00.1/sound/card0/input23
[  124.875028] input: HDA NVidia HDMI/DP,pcm=11 as 
/devices/pci:00/:00:03.1/:07:00.1/sound/card0/input24
[  124.879082] MCE: In-kernel MCE decoding enabled.
[  124.879273] nvidia: loading out-of-tree module taints kernel.
[  124.879313] nvidia: loading out-of-tree module taints kernel.
[  124.879322] nvidia: module license 'NVIDIA' taints kernel.
[  124.879323] Disabling lock debugging due to kernel taint
[  124.888717] alg: No test for fips(ansi_cprng) (fips_ansi_cprng)
[  124.911987] nvidia: module verification failed: signature and/or required 
key missing - tainting kernel
[  124.913593] EDAC amd64: MCT channel count: 2
[  124.915038] EDAC MC0: Giving out device to module amd64_edac controller 
F19h_M20h: DEV :00:18.3 (INTERRUPT)
[  124.916506] EDAC amd64: F19h_M20h detected (node 0).
[  124.917979] EDAC MC: UMC0 chip selects:
[  124.917980] EDAC amd64: MC: 0: 0MB 1: 0MB
[  124.919433] EDAC amd64: MC: 2:  8192MB 3: 0MB
[  124.920980] EDAC MC: UMC1 chip selects:
[  124.920981] EDAC amd64: MC: 0: 0MB 1: 0MB
[  124.922439] EDAC amd64: MC: 2:  8192MB 3: 0MB
[  124.923902] EDAC amd64: using x16 syndromes.
[  124.926016] EDAC PCI0: Giving out device to module amd64_edac controller 
EDAC PCI controller: DEV :00:18.0 (POLLED)
[  124.927542] AMD64 EDAC driver v3.5.0
[  124.936409] nvidia-nvlink: Nvlink Core is being initialized, major device 
number 244

[  124.938591] EXT4-fs (nvme0n1p6): mounted filesystem with ordered data mode. 
Opts: (null). Quota mode: none.
[  124.939494] nvidia :07:00.0: vgaarb: changed VGA decodes: 

Bug#998697: ITP: bees -- a btrfs deduplication agent

[Felix Zielcke]

Am Samstag, dem 06.11.2021 um 21:32 +0300 schrieb Alexander GQ
Gerasiov:
> Package: wnpp
> Severity: wishlist
> Owner: Alexander GQ Gerasiov 
> X-Debbugs-Cc: debian-de...@lists.debian.org
> 
> * Package name    : bees
>   Version : 0.7
>   Upstream Author : Zygo Blaxell b...@furryterror.org
> * URL : https://github.com/Zygo/bees
> * License : GPL-3+
>   Programming Lang: C++
>   Description : a btrfs deduplication agent
> 
> Best-Effort Extent-Same, a btrfs deduplication agent.
> 
> bees is a block-oriented userspace deduplication agent designed for
> large
> btrfs filesystems. It is an offline dedupe combined with an
> incremental data
> scan capability to minimize time data spends on disk from write to
> dedupe.
> 

Hi Alexander,

I totally forgot to look if there's already an ITP filed when I did my
one #1002036.

How far are you with packaging? And do you want a Co-Maintainer? Though
I'm only a DM not DD.

I just did a first version of a Debian package avaible at:
https://salsa.debian.org/fzielcke/bees/

Feel free to use anything of it.

Regards,
Felix

Bug#1002036: ITP: bees -- Best-Effort Extent-Same, a btrfs deduplication agent.

[Felix Zielcke]

Package: wnpp
Severity: wishlist
Owner: Felix Zielcke 
X-Debbugs-Cc: debian-de...@lists.debian.org

* Package name: bees
  Version : 0.7
  Upstream Author : Zygo Blaxell b...@furryterror.org
* URL : https://github.com/Zygo/bees
* License : GPL-3+
  Programming Lang: C++
  Description : Best-Effort Extent-Same, a btrfs deduplication agent.

 bees is a block-oriented userspace deduplication agent designed for
 large btrfs filesystems. It is an offline dedupe combined with an
 incremental data scan capability to minimize time data spends on disk
 from write to dedupe.

I'm happy to maintain it inside a team or with co-maintainer(s).
I'm only DM so if someone has interest in sponsoring this, feel free to
contact me.

First debianized version avaible at https://salsa.debian.org/fzielcke/bees

I guess it's a problem for ftp-masters that copyright and license is only
mentioned inside README.md, but not directly at the source files?
Then it can't yet be uploaded.

Bug#1000208: ITP: pcmemtest -- stand-alone memory tester

[Felix Zielcke]

Am Freitag, dem 26.11.2021 um 15:34 +0100 schrieb Stephan Lachnit:
> Hi Felix,
> 
> I was a bit more stressed this week than I hoped, I'll try to look at
> it
> saturday or sunday. If you don't get a reply by monday morning, feel
> free
> to ping me again.

Hi Stephan,

here's your friendly ping.
Did you have time to look at pcmemtest?

Regards,
Felix

Bug#1000208: ITP: pcmemtest -- stand-alone memory tester

[Felix Zielcke]

Am Samstag, dem 20.11.2021 um 18:47 +0100 schrieb Stephan Lachnit:
> Sounds interesting.
> 
> On Fri, Nov 19, 2021 at 8:03 PM  wrote:
> > 
> > I'm happy to maintain it inside a team or with co-maintainer(s).
> > I'm only DM so if someone has interest in sponsoring this, feel
> > free to
> > contact me.
> 
> If you need me as sponsor, ping me when the package is ready for
> upload.

Hi Stephan, do you have time to review it? I think it's ready to
upload.

> Regards
> Stephan

Bug#1000208: ITP: pcmemtest -- stand-alone memory tester

[Felix Zielcke]

Am Samstag, dem 20.11.2021 um 10:00 -0500 schrieb Antoine Beaupré:
> Do let me know if you need a sponsor.

Hi Antoine,

as talked on IRC: I would be happy if you do the review (audit) of
pcmemtest.
Since you didn't reply back if you actually do this now: Would be good
to have a clear answer here on the ITP so others know I have you as a
sponsor.

TIA
Felix

Bug#1000208: ITP: pcmemtest -- stand-alone memory tester

[Felix Zielcke]

Hi Adam,

thanks for all your comments.

Am Montag, dem 22.11.2021 um 09:27 +0100 schrieb Adam Borowski:
> On Sun, Nov 21, 2021 at 04:46:50PM +0100, Felix Zielcke wrote:
> > Am Sonntag, dem 21.11.2021 um 10:15 -0500 schrieb Antoine Beaupré:
> > > i would suggest not blocking on the grub deployment. you can
> > > probably
> > > just deploy whatever architecture the package was built from, in
> > > any
> > > case.
> 
> > I just added now the GRUB 2 integration and a README.Debian.
> 
> The integration isn't triggered on the package's install, but it is
> picked
> up the next time something else bumps grub.

I forgot that grub2 isn't using triggers.
Added now a postinst based on the one from memtest86+. Except that I
removed the lilo parts.

> 
> 
> > Note that I mention in README.Debian one nasty bug/issue:
> > 
> > In EFI mode the keyboard only works if you have the CSM aka legacy
> > boot
> > also enabled:
> > 
> > https://github.com/martinwhitaker/pcmemtest/issues/2
> 
> This is a nasty one.  It seems most new machines lack CSM; no one wants
> to
> support and validate 16-bit stuff -- it's effectively expending
> resources
> to have two BIOSes instead of one, and the 8086 one has no practical
> usage.
> 

I opened now upstream a new issue about this:

https://github.com/martinwhitaker/pcmemtest/issues/13

But in the closed one he said, it takes a while to write a usb keyboard
driver for EFI.

> > Upstream doestn't say anything there that this will change. Issue was
> > closed with the hint it's documented. And it will just run with
> > default
> > settings.
> 
> It does, but using just a single thread.  There's not exactly many x86
> machines with only a single hardware thread that are still in use.
> 
> What about defaulting to SMP when there's no user input?  The UP mode
> has little purpose for existing -- if concurrent accesses to memory
> break, they'll also break when running the actual productive task the
> machine is supposed to do.
> 

I also made an issue for this:

https://github.com/martinwhitaker/pcmemtest/issues/14

I don't know the reasons why it's not enabled by default. So I woudn't
change that for the first upload to Debian on my own.

> Meow!

Cheers!
Felix

Bug#1000208: ITP: pcmemtest -- stand-alone memory tester

[Felix Zielcke]

Am Sonntag, dem 21.11.2021 um 10:15 -0500 schrieb Antoine Beaupré:
> 
> i would suggest not blocking on the grub deployment. you can probably
> just deploy whatever architecture the package was built from, in any
> case.
> 
> a.
> 

Hi Antoine and Stephan,

I just added now the GRUB 2 integration and a README.Debian.
You can now review it. And I think it would be better to first upload
this to experimental? So a bit more experienced Debian users can test
it first. 

Note that I mention in README.Debian one nasty bug/issue:

In EFI mode the keyboard only works if you have the CSM aka legacy boot
also enabled:

https://github.com/martinwhitaker/pcmemtest/issues/2

Upstream doestn't say anything there that this will change. Issue was
closed with the hint it's documented. And it will just run with default
settings.

Is for you my salsa repo enough or just I also upload to mentors?
Git repo is in git-buildpackage format:

https://salsa.debian.org/fzielcke/pcmemtest

TIA
Felix

Bug#1000208: ITP: pcmemtest -- stand-alone memory tester

[Felix Zielcke]

Am Samstag, dem 20.11.2021 um 10:00 -0500 schrieb Antoine Beaupré:
> On 2021-11-19 19:50:45, fziel...@z-51.de wrote:
> [...]
> 
> >  PCMemTest is a fork and rewrite of Memtest86+, which in turn was a
> > fork of
> >  Memtest86.
> > 
> > 
> > I'm happy to maintain it inside a team or with co-maintainer(s).
> > I'm only DM so if someone has interest in sponsoring this, feel free
> > to
> > contact me.
> 
> Great find! I was disappointed to find out that memtest86* is basically
> unusable these days in Debian, and find this ITP to be very
> interesting!
> Do let me know if you need a sponsor.
> 
> Did you test the program at all? Does it behave better than the
> existing
> memtest86 packages currently in Debian?
> 
> a.

Thanks for your interest :)

I pushed now my first work to my personal salsa profile:

https://salsa.debian.org/fzielcke/pcmemtest

The files are for now in /usr/lib/pcmemtest
There are 32bit and 64bit legacy BIOS + EFI files
Not sure if there's actually a different between the 2 legacy BIOS
versions.

I haven't yet tried it myself but will do soon.
The suggestion came from #btrfs IRC channel. So it can't be that bad.


And I'm not sure how I want to do the GRUB integration. Due to the
differences with 32bit and 64bit EFI.
Is there actually a way to find out with what EFI version the system
booted?

Regards
Felix

Bug#992410: move of /bin/run-parts to /usr/bin breaks network with ifup

[Felix Zielcke]

Am Mittwoch, dem 18.08.2021 um 15:12 + schrieb Clint Adams:
> On Wed, Aug 18, 2021 at 10:33:17AM +0200, fziel...@z-51.de wrote:
> > After todays updates and a reboot my network didn't come up
> > anymore.
> > Problem is the move of /bin/run-parts to /usr/bin:
> > 
> > systemd[1]: Starting Raise network interfaces...
> > ifup[1663]: /bin/sh: 1: /bin/run-parts: not found
> > ifup[1661]: ifup: pre-up script failed
> > systemd[1]: networking.service: Main process exited, code=exited,
> > status=1/FAILURE
> > systemd[1]: networking.service: Failed with result 'exit-code'.
> > systemd[1]: Failed to start Raise network interfaces.
> 
> Also see #992425

I can confirm that the NMU of ifupdown fixes the problem.
So you can add now a Breks: and close #992410

Bug#992410: closed by Debian FTP Masters (reply to Clint Adams ) (Bug#992396: fixed in debianutils 5.0.1-2)

[Felix Zielcke]

Control: unmerge -1
Control: reopen -1

> Changes:
> debianutils (5.0.1-2) unstable; urgency=medium
> .
>   * Redirect stderr from which in smoke test
>   * Add Breaks on x11-common still using `tempfile`.
> closes: #992396.

Sorry but my bug has with run-parts to do and nothing with tempfile in
x11-common.

Am Mittwoch, dem 18.08.2021 um 15:51 + schrieb Debian Bug Tracking
System:
> This is an automatic notification regarding your Bug report
> which was filed against the debianutils package:
> 
> #992410: move of /bin/run-parts to /usr/bin breaks network with ifup
> 
> It has been closed by Debian FTP Masters
>  (reply to Clint Adams
> ).
> 
> Their explanation is attached below along with your original report.
> If this explanation is unsatisfactory and you have not received a
> better one in a separate message then please contact Debian FTP
> Masters  (reply to Clint Adams
> ) by
> replying to this email.
> 
> 

Bug#987125: Re: systemd notify support is broken

[Felix Zielcke]

tags #987125 + fixed-upstream
thanks

On Wed, 21 Apr 2021 20:15:55 +0200 Felix Zielcke 
wrote:
> Am Mittwoch, dem 21.04.2021 um 19:45 +0200 schrieb Christian
Göttsche:
> > > import_environment = TZ
> > 
> > I can reproduce this issue when setting 'import_environment = TZ',
> > and
> > it is fixed by setting 'import_environment = TZ NOTIFY_SOCKET'.
> 
> Thanks very much! This indeed fixes it.
> But I wonder why this is uncommented in my config. Maybe some
leftover
> from the stretch default config?
> 
> Maybe it's a good idea to check for this on upgrades?
> 
> 
> 

Todays release v2.3.15 fixes this:

- master: Systemd service: Dovecot announces readiness for accepting
   connections earlier than it should. The following environment
variables
   are now imported automatically and can be omitted from
   import_environment setting: NOTIFY_SOCKET LISTEN_FDS LISTEN_PID.

Bug#987125: Re: systemd notify support is broken

[Felix Zielcke]

Am Sonntag, dem 18.04.2021 um 09:16 +0200 schrieb Felix Zielcke:
> Package: dovecot-core
> Version: 1:2.3.13+dfsg1-1
> Severity: important
> 
> I have upgraded a buster system to bullseye.
> Even though dovecot starts up fine with the old config, systemd fails
> to notify that. And kills it again:
> 
> # systemctl start dovecot
> 
> Job for dovecot.service failed because a timeout was exceeded.
> 
> I have brought this up on upstream's mailing list:
> 
> https://dovecot.org/pipermail/dovecot/2021-April/121921.html
> 
> Solution was to change the dovecot.service file to not use
> Type=notify but Type=simple
> 

Upstreams' fixes, which will be released with 2.3.15, are here:

https://github.com/dovecot/core/compare/19e05adc3657d2133412635f1345b53cc210ba5b%5E..576d40df2ca38e16c2c9dad798d9b74721568fb0

I'm not sure if this actually should be RC. Anyone who uses systemd
can't start dovecot without manual changes. So this really should be
fixed before bullseye will be released.

Bug#987125: systemd notify support is broken

[Felix Zielcke]

Package: dovecot-core
Version: 1:2.3.13+dfsg1-1
Severity: important

I have upgraded a buster system to bullseye.
Even though dovecot starts up fine with the old config, systemd fails to notify 
that. And kills it again:

# systemctl start dovecot

Job for dovecot.service failed because a timeout was exceeded.

I have brought this up on upstream's mailing list:

https://dovecot.org/pipermail/dovecot/2021-April/121921.html

Solution was to change the dovecot.service file to not use Type=notify but 
Type=simple

-- Package-specific info:

-- System Information:
Debian Release: bullseye/sid
  APT prefers testing
  APT policy: (500, 'testing')
Architecture: amd64 (x86_64)
Foreign Architectures: i386

Kernel: Linux 5.10.0-6-cloud-amd64 (SMP w/2 CPU threads)
Locale: LANG=de_DE.UTF-8, LC_CTYPE=de_DE.UTF-8 (charmap=UTF-8), LANGUAGE not set
Shell: /bin/sh linked to /bin/dash
Init: systemd (via /run/systemd/system)
LSM: AppArmor: enabled

Versions of packages dovecot-core depends on:
ii  adduser  3.118
ii  init-system-helpers  1.60
ii  libapparmor1 2.13.6-10
ii  libbz2-1.0   1.0.8-4
ii  libc62.31-11
ii  libcap2  1:2.44-1
ii  libcrypt11:4.4.18-2
ii  libexttextcat-2.0-0  3.4.5-1
ii  libicu67 67.1-6
ii  liblua5.3-0  5.3.3-1.1+b1
ii  liblz4-1 1.9.3-1
ii  liblzma5 5.2.5-2
ii  libpam-runtime   1.4.0-7
ii  libpam0g 1.4.0-7
ii  libsodium23  1.0.18-1
ii  libssl1.11.1.1k-1
ii  libstemmer0d 2.1.0-1
ii  libtirpc31.3.1-1
ii  libwrap0 7.6.q-31
ii  libzstd1 1.4.8+dfsg-2.1
ii  lsb-base 11.1.0
ii  openssl  1.1.1k-1
ii  ssl-cert 1.1.0
ii  ucf  3.0043
ii  zlib1g   1:1.2.11.dfsg-2

dovecot-core recommends no packages.

Versions of packages dovecot-core suggests:
pn  dovecot-gssapi
ii  dovecot-imapd 1:2.3.13+dfsg1-1
pn  dovecot-ldap  
ii  dovecot-lmtpd 1:2.3.13+dfsg1-1
pn  dovecot-lucene
ii  dovecot-managesieved  1:2.3.13+dfsg1-1
pn  dovecot-mysql 
pn  dovecot-pgsql 
pn  dovecot-pop3d 
ii  dovecot-sieve 1:2.3.13+dfsg1-1
pn  dovecot-solr  
pn  dovecot-sqlite
pn  dovecot-submissiond   
pn  ntp   

Versions of packages dovecot-core is related to:
ii  dovecot-core [dovecot-common]  1:2.3.13+dfsg1-1
ii  dovecot-dev1:2.3.13+dfsg1-1
pn  dovecot-gssapi 
ii  dovecot-imapd  1:2.3.13+dfsg1-1
pn  dovecot-ldap   
ii  dovecot-lmtpd  1:2.3.13+dfsg1-1
ii  dovecot-managesieved   1:2.3.13+dfsg1-1
pn  dovecot-mysql  
pn  dovecot-pgsql  
pn  dovecot-pop3d  
ii  dovecot-sieve  1:2.3.13+dfsg1-1
pn  dovecot-sqlite 

-- no debconf information

-- debsums errors found:
debsums: changed file /lib/systemd/system/dovecot.service (from dovecot-core 
package)

Bug#976285: please enable redis plugin

[Felix Zielcke]

Am Freitag, den 04.12.2020, 11:05 +1100 schrieb Dmitry Smirnov:
> On Thursday, 3 December 2020 6:12:01 PM AEDT Felix Zielcke wrote:
> > So what's missing to enable Agent 2?
> 
> I think Agent 2 is not the issue.

In the docs it's listed for Agent 2:

https://www.zabbix.com/documentation/5.0/manual/config/templates_out_of_the_box/zabbix_agent2

So I guess it's needed?

> > zabbix_get [2294402]: Check access restrictions in Zabbix agent
> > configuration
> 
> Agent will only respond to requests from hosts listed in "Server=".
> 

Yeah, I found it out now that it was using IPv6 even though only
127.0.0.1 was allowed:

# zabbix_get -s 127.0.0.1 -k redis.ping
ZBX_NOTSUPPORTED: Unsupported item key.

Bug#976285: please enable redis plugin

[Felix Zielcke]

Control: retitle -1  please enable Zabbix Agent 2

Am Donnerstag, den 03.12.2020, 13:10 +1100 schrieb Dmitry Smirnov:
> On Thursday, 3 December 2020 6:44:45 AM AEDT Felix Zielcke wrote:
> > it looks like Zabbix is compiled without the redis plugin.
> 
> No, it looks like there is no special support for Redis in zabbix-
> agent.
> 
> You probably need (Golang-based) Zabbix Agent 2, which is not
> provided
> by Debian package (yet).
> 

Thanks for your fast reply.
So what's missing to enable Agent 2?

> > From /usr/share/doc/zabbix-frontend-
> > php/templates/db/redis/README.md.gz
> > Test availability: `zabbix_get -s redis-master -k redis.ping`
> > 
> > # `zabbix_get -s redis-master -k redis.ping`
> > zabbix_get [2264555]: Get value error: cannot resolve [redis-
> > master]
> 
> That error indicates that your network have no "redis-master" host
> (or that there is no DNS record for it).
> 
> 
> > And the template indeed doestn't work.
> 
> That's hardly a surprise if "redis master" don't resolve...

Whoops. So I didn't read the docs fully.
But now I get a different error:

zabbix_get [2294402]: Check access restrictions in Zabbix agent
configuration

Well this isn't a support channel, so I'll try to find it out myself,
what's now wrong.

Thanks again for your answer.

Bug#976285: please enable redis plugin

[Felix Zielcke]

Package: zabbix-agent
Version: 1:5.0.5+dfsg-1~bpo10+1
Severity: wishlist

Hello,

it looks like Zabbix is compiled without the redis plugin.

>From /usr/share/doc/zabbix-frontend-php/templates/db/redis/README.md.gz
Test availability: `zabbix_get -s redis-master -k redis.ping`

# `zabbix_get -s redis-master -k redis.ping`
zabbix_get [2264555]: Get value error: cannot resolve [redis-master]

And the template indeed doestn't work.

Would be nice to have redis support enabled.


-- System Information:
Debian Release: 10.6
  APT prefers stable
  APT policy: (510, 'stable'), (500, 'stable-updates'), (500, 
'proposed-updates'), (498, 'testing'), (497, 'unstable')
Architecture: amd64 (x86_64)
Foreign Architectures: i386

Kernel: Linux 4.19.0-12-amd64 (SMP w/2 CPU cores)
Locale: LANG=de_DE.UTF-8, LC_CTYPE=de_DE.UTF-8 (charmap=UTF-8), 
LANGUAGE=de_DE.UTF-8 (charmap=UTF-8)
Shell: /bin/sh linked to /bin/dash
Init: systemd (via /run/systemd/system)
LSM: AppArmor: enabled

Versions of packages zabbix-agent depends on:
ii  adduser  3.118
ii  init-system-helpers  1.56+nmu1
ii  libc62.28-10
ii  libcurl3-gnutls  7.64.0-4+deb10u1
ii  libgnutls30  3.6.7-4+deb10u5
ii  libldap-2.4-22.4.56+dfsg-1~bpo10+1
ii  libpcre3 2:8.42-1+0~20190203125152.5+buster~1.gbp79d75d
ii  lsb-base 10.2019051400
ii  pciutils 1:3.5.2-1
ii  ucf  3.0038+nmu1
ii  zlib1g   1:1.2.11.dfsg-1

Versions of packages zabbix-agent recommends:
ii  usbutils  1:010-3

Versions of packages zabbix-agent suggests:
ii  logrotate  3.14.0-4

-- no debconf information

Bug#961450: changelog.gz is different between amd64 and i386 packages

[Felix Zielcke]

Package: libsqlite3-0
Version: 3.32.0-1
Severity: important

Now that changelog.gz is generated on build time to fix #959983 it can't be 
co-installed for amd64 and i386:

Preparing to unpack .../libsqlite3-dev_3.32.0-1_amd64.deb ...
Unpacking libsqlite3-dev:amd64 (3.32.0-1) over (3.31.1-5) ...
Preparing to unpack .../libsqlite3-0_3.32.0-1_i386.deb ...
De-configuring libsqlite3-0:amd64 (3.31.1-5) ...
Unpacking libsqlite3-0:i386 (3.32.0-1) over (3.31.1-5) ...
Preparing to unpack .../libsqlite3-0_3.32.0-1_amd64.deb ...
Unpacking libsqlite3-0:amd64 (3.32.0-1) over (3.31.1-5) ...
dpkg: error processing archive 
/var/cache/apt/archives/libsqlite3-0_3.32.0-1_amd64.deb (--unpack):
 trying to overwrite shared '/usr/share/doc/libsqlite3-0/changelog.gz', which 
is different from other instances of package libsqlite3-0:amd64
dpkg-deb: error: paste subprocess was killed by signal (Broken pipe)
Errors were encountered while processing:
 /var/cache/apt/archives/libsqlite3-0_3.32.0-1_amd64.deb
E: Sub-process /usr/bin/dpkg returned an error code (1)


-- System Information:
Debian Release: bullseye/sid
  APT prefers unstable
  APT policy: (500, 'unstable'), (1, 'experimental')
Architecture: amd64 (x86_64)
Foreign Architectures: i386

Kernel: Linux 5.6.0-1-amd64 (SMP w/4 CPU cores)
Kernel taint flags: TAINT_OOT_MODULE, TAINT_UNSIGNED_MODULE
Locale: LANG=de_DE.UTF-8, LC_CTYPE=de_DE.UTF-8 (charmap=UTF-8), 
LANGUAGE=de_DE.UTF-8 (charmap=UTF-8)
Shell: /bin/sh linked to /bin/dash
Init: systemd (via /run/systemd/system)
LSM: AppArmor: enabled

Versions of packages libsqlite3-0 depends on:
ii  libc6  2.30-8

libsqlite3-0 recommends no packages.

libsqlite3-0 suggests no packages.

-- no debconf information

Bug#961320: backported version needs newer node-dot-prop to work

[Felix Zielcke]

Package: npm
Version: 6.14.3+ds-1~bpo10+1
Severity: grave

npm installed from backports fails with:

$ npm
npm ERR! pathArray is not defined

Installing node-dot-prop from testing fixes this.

-- System Information:
Debian Release: 10.4
  APT prefers stable
  APT policy: (510, 'stable'), (500, 'stable-updates'), (500, 
'proposed-updates'), (498, 'testing'), (497, 'unstable')
Architecture: amd64 (x86_64)

Kernel: Linux 4.19.0-9-amd64 (SMP w/2 CPU cores)
Locale: LANG=de_DE.UTF-8, LC_CTYPE=de_DE.UTF-8 (charmap=UTF-8), 
LANGUAGE=de_DE.UTF-8 (charmap=UTF-8)
Shell: /bin/sh linked to /bin/dash
Init: systemd (via /run/systemd/system)

Versions of packages npm depends on:
ii  ca-certificates 20190110
ii  node-abbrev 1.1.1-1
ii  node-ajv6.10.2-1~bpo10+1
ii  node-ansi   0.3.0-3
ii  node-ansi-regex 3.0.0-1
ii  node-ansi-styles3.2.1-1
ii  node-ansistyles 0.1.3-1
ii  node-aproba 1.2.0-1
ii  node-archy  1.0.0-2
ii  node-are-we-there-yet   1.1.4-1
ii  node-asap   2.0.6-1
ii  node-asn1   0.2.3-1
ii  node-assert-plus1.0.0-1
ii  node-asynckit   0.4.0-2
ii  node-aws-sign2  0.7.1-1
ii  node-aws4   1.8.0-1
ii  node-balanced-match 0.4.2-1
ii  node-bcrypt-pbkdf   1.0.1-1
ii  node-bl 1.1.2-1
ii  node-bluebird   3.5.1+dfsg2-2
ii  node-boxen  1.2.2-1
ii  node-brace-expansion1.1.8-1
ii  node-builtin-modules3.0.0-1
ii  node-builtins   1.0.3-1
ii  node-cacache11.3.2-2
ii  node-call-limit 1.1.0-1
ii  node-camelcase  5.0.0-1
ii  node-caseless   0.12.0-1
ii  node-chalk  2.4.2-1~bpo10+1
ii  node-chownr 1.1.1-1
ii  node-ci-info1.1.2-1
ii  node-cli-boxes  1.0.0-1
ii  node-cliui  4.1.0-1
ii  node-clone  2.1.2-1
ii  node-co 4.6.0-1
ii  node-color-convert  1.9.0-3
ii  node-color-name 1.1.3-1
ii  node-colors 1.1.2-1
ii  node-columnify  1.5.4-1
ii  node-combined-stream1.0.7-1
ii  node-concat-map 0.0.1-1
ii  node-concat-stream  1.6.2-1
ii  node-config-chain   1.1.11-1
ii  node-configstore3.1.1-2
ii  node-console-control-strings1.1.0-1
ii  node-copy-concurrently  1.0.5-4
ii  node-core-util-is   1.0.2-1
ii  node-cross-spawn5.1.0-2
ii  node-crypto-random-string   1.0.0-1
ii  node-cyclist1.0.1-2
ii  node-dashdash   1.14.1-2
ii  node-debug  3.1.0-2
ii  node-decamelize 1.2.0-1
ii  node-deep-extend0.4.1-2
ii  node-defaults   1.0.3-1
ii  node-define-properties  1.1.3-1~bpo10+1
ii  node-delayed-stream 0.0.5-1
ii  node-delegates  1.0.0-1
ii  node-detect-indent  5.0.0-1
ii  node-detect-newline 2.1.0-1
ii  node-dot-prop   4.1.1-1+deb10u1
ii  node-duplexer3  0.1.4-4
ii  node-duplexify  3.6.1-1
ii  node-ecc-jsbn   0.1.1-1
ii  node-editor 1.0.0-1
ii  node-encoding   0.1.12-2
ii  node-end-of-stream  1.4.1-1
ii  node-err-code   1.1.2+dfsg-1
ii  node-errno  0.1.4-1
ii  node-es6-promise4.2.5-2
ii  node-escape-string-regexp   1.0.5-1
ii  node-execa  0.10.0+dfsg-1
ii  node-extend 3.0.2-1
ii  node-extsprintf 1.3.0-1
ii  node-fast-deep-equal1.0.0-1
ii  node-find-up2.1.0-1
ii  node-flush-write-stream 1.0.3-1
ii  node-forever-agent  0.6.1-1
ii  node-form-data  2.3.2-2
ii  node-from2  2.3.0-1
ii  node-fs-vacuum  1.2.10-2
ii  node-fs-write-stream-atomic 1.0.10-4
ii  node-fs.realpath1.0.0-1
ii  node-function-bind  1.1.1+ds-2
ii  node-gauge  2.7.4-1
ii  node-genfun 4.0.1-1
ii  node-get-caller-file1.0.2-1
ii  node-getpass0.1.7-1
ii  node-glob   7.1.3-2
ii  node-got7.1.0-1
ii  node-graceful-fs4.1.11-1
ii  node-gyp6.1.0-3
ii  node-har-schema 2.0.0-3
ii  node-har-validator  5.1.3-1
ii  node-has-flag   2.0.0-1
ii  node-has-unicode2.0.1-2
ii  node-hosted-git-info

Bug#950556: initramfs-tools hook fails to copy libgcc_s.so.1

[Felix Zielcke]

On Mon, 03 Feb 2020 14:43:25 +0100 Felix Zielcke 
wrote:
> 
> My system didn't boot anymore. initramfs complained that for
> phread_cancel you need libgcc_s.so installed.
> 
> The btrfs hook for initramfs expects it to be in the same dir as
libc6.
> But that's not true anymore since libgcc1 has been updated from gcc-9 
to gcc-10.
> 
> libgcc1 in bullseye (version: 1:9.2.1-25) has it in /lib/x86_64-
linux-gnu/
> In sid (version: 1:10-20200202-1) it's directly in /lib/
> or alternatetively in the new libgcc-s1 it is in /usr/lib/x86_64-
linux-gnu/
>

This gets now handled directly in initramfs-tools:

https://salsa.debian.org/kernel-team/initramfs-tools/commit/f2ac13e8881f975b062a56050ceda85ef9ccc015

See also #950556

Bug#950551: libgcc1: after libgcc1 upgrade, can't unlock luks partition at boot

[Felix Zielcke]

Am Montag, den 03.02.2020, 18:59 +0100 schrieb Matthias Klose:

> $ dpkg -S libgcc_s.so.1
> libgcc-s1:amd64: /usr/lib/x86_64-linux-gnu/libgcc_s.so.1
> libgcc1: /lib/libgcc_s.so.1
> 
> if you need the library in /lib, make sure that you depend on
> libgcc1, else it's
> found in /usr/lib/.
> 
> I'm fine to add some breaks if required.

This gets now fixed directly in initramfs-tools:

https://salsa.debian.org/kernel-team/initramfs-tools/commit/f2ac13e8881f975b062a56050ceda85ef9ccc015

See also #950254

So I guess as soon as that is uploaded, libgcc1 should then Breaks: the
older versions.

Bug#950551: libgcc1: after libgcc1 upgrade, can't unlock luks partition at boot

[Felix Zielcke]

On Mon, 03 Feb 2020 15:35:21 +0200 dimit...@stinpriza.org wrote:
> Package: libgcc1
> Version: 1:9.2.1-25
> Severity: grave
> Justification: renders package unusable
> 
> hey,
> 
> after upgrading some latest packages on sid, i can no longer unlock
luks
> partition and boot. message:
> 
> "Please unlock disk rootfs:
> libgcc_s.so.1 must be installed for pthread-cancel to work
> Aborted"
> 
> so i think it's libgcc1 related.
> had to chroot to disk from liveusb, downgrade some packages & finally
use a
> different kernel to boot.
> noticed that update-initramfs with libgcc1 1:9.2.1-25 adds file :
"Adding
> binary /lib/x86_64-linux-gnu/libgcc_s.so.1" , while libgcc1 version
> 1:10-20200202-1 doesn't add any libgcc_s.so.1.
> 
> also, version from testing includes file /lib/x86_64-linux-
gnu/libgcc_s.so.1,
> while sid version uses /lib/libgcc_s.so.1 . libgcc-s1 also includes
this file :
> /usr/lib/x86_64-linux-gnu/libgcc_s.so.1
> 
> let me know if you need anymore info.
> 
> thanks,
> d.

The btrfs binary in initramfs is also affected by this.
See #950556 [1]

Just now with your report I saw that both btrfs and cryptroot initramfs
hooks expects libgcc_s.so.1 in the same dir as libc.so.6
This was true in bullseye but now with the change to gcc-10 the path
has also changed.

[1] https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=950556

Bug#950556: initramfs-tools hook fails to copy libgcc_s.so.1

[Felix Zielcke]

Package: btrfs-progs
Version: 5.4.1-1
Severity: critical

My system didn't boot anymore. initramfs complained that for
phread_cancel you need libgcc_s.so installed.

The btrfs hook for initramfs expects it to be in the same dir as libc6.
But that's not true anymore since libgcc1 has been updated from gcc-9 to gcc-10.

libgcc1 in bullseye (version: 1:9.2.1-25) has it in /lib/x86_64-linux-gnu/
In sid (version: 1:10-20200202-1) it's directly in /lib/
or alternatetively in the new libgcc-s1 it is in /usr/lib/x86_64-linux-gnu/

quick solution:

--- btrfs.old   2020-02-03 14:39:26.409270708 +0100
+++ btrfs   2020-02-03 14:39:46.602089060 +0100
@@ -25,8 +25,8 @@
then
copy_exec /sbin/fsck.btrfs /sbin
fi
-   LIBC_DIR=$(ldd /bin/btrfs | sed -nr 's#.* => 
(/lib.*)/libc\.so\.[0-9.-]+ \(0x[[:xdigit:]]+\)$#\1#p')
-   find -L "$LIBC_DIR" -maxdepth 1 -name 'libgcc_s.*' -type f | while read 
so; do
+#  LIBC_DIR=$(ldd /bin/btrfs | sed -nr 's#.* => 
(/lib.*)/libc\.so\.[0-9.-]+ \(0x[[:xdigit:]]+\)$#\1#p')
+   find -L "/lib" -maxdepth 1 -name 'libgcc_s.*' -type f | while read so; 
do
copy_exec "$so"
done
 fi

-- System Information:
Debian Release: bullseye/sid
  APT prefers unstable
  APT policy: (500, 'unstable'), (1, 'experimental')
Architecture: amd64 (x86_64)
Foreign Architectures: i386

Kernel: Linux 5.3.0-3-amd64 (SMP w/4 CPU cores)
Kernel taint flags: TAINT_OOT_MODULE, TAINT_UNSIGNED_MODULE
Locale: LANG=de_DE.UTF-8, LC_CTYPE=de_DE.UTF-8 (charmap=UTF-8), 
LANGUAGE=de_DE.UTF-8 (charmap=UTF-8)
Shell: /bin/sh linked to /bin/dash
Init: systemd (via /run/systemd/system)
LSM: AppArmor: enabled

Versions of packages btrfs-progs depends on:
ii  libblkid12.34-0.1
ii  libc62.29-9
ii  libcom-err2  1.45.5-2
ii  libext2fs2   1.45.5-2
ii  liblzo2-22.10-2
ii  libuuid1 2.34-0.1
ii  libzstd1 1.4.4+dfsg-1
ii  zlib1g   1:1.2.11.dfsg-1.2

btrfs-progs recommends no packages.

Versions of packages btrfs-progs suggests:
pn  duperemove  

-- no debconf information

Bug#946746: virtualbox: after upgrade virtualbox can not open it .

[Felix Zielcke]

On Sun, 15 Dec 2019 10:42:07 +0330 alirezaimi 
wrote:
> Package: virtualbox
> Version: 6.1.0-dfsg-1
> Severity: important
> 
> Dear Maintainer,
> 
> *** Reporter, please consider answering these questions, where
appropriate ***
> 
>* What led up to the situation?
>  apt-get dist-upgrade
>* What exactly did you do (or not do) that was effective (or
>  ineffective)?
>  system upgrade
>* What was the outcome of this action?
>  virtualbox can not open .
>* What outcome did you expect instead?
>  open virtualbox .
> 
> *** End of the template - remove these template lines ***

The package seems to be missing UICommon.so:

$ virtualbox
/usr/lib/virtualbox/VirtualBox: error while loading shared libraries: 
UICommon.so: cannot open shared object file: No such file or directory

Bug#941675: Same thing here

[Felix Zielcke]

On Tue, 15 Oct 2019 09:20:36 -0400 Frank McCormick <
fmccorm...@videotron.ca> wrote:
> One has to wait until it times out before desktop will appear.
> 

It seems like the updated mate-session-manager 1.22.2-2 in sid fixes
the long delay with MATE.
The original Launchpad bug for this is here:

https://bugs.launchpad.net/ubuntu/+source/mate-session-manager/+bug/1846987

But the gkr-pam failure is still in the logs.

Bug#941675: gkr-pam: unable to locate daemon control file

[Felix Zielcke]

Package: libpam-gnome-keyring
Version: 3.34.0-1
Severity: normal

I use MATE and lightdm. With the new version in sid it needs more time
until the desktop appears.

auth.log says:
lightdm: gkr-pam: unable to locate daemon control file

downgrading to the version in testing or commenting out the
libpam_gnome_keyring.so PAM lines in /etc/pam.d/lightdm makes it fast again.

-- System Information:
Debian Release: bullseye/sid
  APT prefers unstable
  APT policy: (500, 'unstable'), (500, 'testing'), (1, 'experimental')
Architecture: amd64 (x86_64)
Foreign Architectures: i386

Kernel: Linux 5.2.0-3-amd64 (SMP w/4 CPU cores)
Kernel taint flags: TAINT_OOT_MODULE, TAINT_UNSIGNED_MODULE
Locale: LANG=de_DE.UTF-8, LC_CTYPE=de_DE.UTF-8 (charmap=UTF-8), 
LANGUAGE=de_DE.UTF-8 (charmap=UTF-8)
Shell: /bin/sh linked to /bin/dash
Init: systemd (via /run/systemd/system)
LSM: AppArmor: enabled

Versions of packages libpam-gnome-keyring depends on:
ii  libc6   2.29-2
ii  libpam-runtime  1.3.1-5
ii  libpam0g1.3.1-5
ii  libselinux1 2.9-2+b2

Versions of packages libpam-gnome-keyring recommends:
ii  gnome-keyring  3.34.0-1

libpam-gnome-keyring suggests no packages.

-- no debconf information

Bug#932603: missing dependency on libnet1

[Felix Zielcke]

Package: tcptraceroute
Version: 1.5beta7+debian-4.1
Severity: serious

I hadn't libnet1 installed due to nothing depending on it and tcptraceroute 
failed now with:

# tcptraceroute www.debian.org
tcptraceroute: error while loading shared libraries: libnet.so.1: cannot open 
shared object file: No such file or directory

And indeed the tcptraceroute_1.5beta7+debian-4.1_amd64.deb doestn't have any 
Depends: line in DEBIAN/control.
Even though packages.debian.org says the sid version would depend on libnet1.


-- System Information:
Debian Release: bullseye/sid
  APT prefers unstable
  APT policy: (500, 'unstable'), (1, 'experimental')
Architecture: amd64 (x86_64)
Foreign Architectures: i386

Kernel: Linux 4.19.0-5-amd64 (SMP w/4 CPU cores)
Kernel taint flags: TAINT_OOT_MODULE, TAINT_UNSIGNED_MODULE
Locale: LANG=de_DE.UTF-8, LC_CTYPE=de_DE.UTF-8 (charmap=UTF-8), 
LANGUAGE=de_DE.UTF-8 (charmap=UTF-8)
Shell: /bin/sh linked to /bin/dash
Init: systemd (via /run/systemd/system)
LSM: AppArmor: enabled

-- no debconf information

Bug#932199: insserv: warning: could not find all dependencies for $portmap

[Felix Zielcke]

control: forcemerge 932199 932260

Am Donnerstag, den 18.07.2019, 12:44 + schrieb Dmitry Bogatov:


> control: forcemerge 932199 932266

I guess you actually meant #932260 which is my filed bug.
#932266 is an ITP.

> 
> 
> [...]

> By the way, lightdm seems (according to apt-file) to not provide
> /etc/insserv.conf.d/lightdm file. This is bug, I think.

So there should be another bug report filed against lightdm about this?

> This warning was introduced in upstream [ddd9d38] with following
> changelog:
> 
>   - When an initscript contains a "$service" dependency which cannot
> be
> resolved (ie $service does not expand or does not exist) insserv
> will display a warning. The initscript is still added.
> 
> Seems problem is that warning emitted not only for hard, but only for
> soft dependencies. Patch at bottom.
> 
> Please check whether is solves all problems.
> 

Now with todays apt upgrade and insserv 1.20.0-2 there were'nt any
warnins now at all from it.

Thanks for fixing!

Bug#932260: insserv: warning: could not find all dependencies for $x-display-manager

[Felix Zielcke]

Package: insserv
Version: 1.20.0-1
Severity: important

Wasn't sure if I should make a new report or just reply to #932199
I got the same as in #932199 but additionally with $x-display-manager:

[...]
sysv-rc (2.95-1) wird eingerichtet ...
initscripts (2.95-1) wird eingerichtet ...
Neue Version der Konfigurationsdatei /etc/init.d/bootlogs wird installiert ...
Neue Version der Konfigurationsdatei /etc/init.d/bootmisc.sh wird installiert 
...
Neue Version der Konfigurationsdatei /etc/init.d/checkfs.sh wird installiert ...
Neue Version der Konfigurationsdatei /etc/init.d/mountall.sh wird installiert 
...
Neue Version der Konfigurationsdatei /etc/init.d/reboot wird installiert ...
Neue Version der Konfigurationsdatei /etc/init.d/umountfs wird installiert ...
Neue Version der Konfigurationsdatei /etc/default/halt wird installiert ...
2cc9a54ea561142b44d68f84d588aaee  /etc/rc.local.dpkg-old
insserv: warning: could not find all dependencies for $portmap
insserv: warning: could not find all dependencies for $x-display-manager
[...]

I have lightdm installed as display manager.

-- System Information:
Debian Release: bullseye/sid
  APT prefers unstable
  APT policy: (510, 'unstable'), (500, 'experimental')
Architecture: amd64 (x86_64)
Foreign Architectures: i386

Kernel: Linux 4.19.0-5-amd64 (SMP w/4 CPU cores)
Kernel taint flags: TAINT_OOT_MODULE, TAINT_UNSIGNED_MODULE
Locale: LANG=de_DE.UTF-8, LC_CTYPE=de_DE.UTF-8 (charmap=UTF-8), 
LANGUAGE=de_DE.UTF-8 (charmap=UTF-8)
Shell: /bin/sh linked to /bin/dash
Init: systemd (via /run/systemd/system)
LSM: AppArmor: enabled

Versions of packages insserv depends on:
ii  libc6  2.28-10

insserv recommends no packages.

Versions of packages insserv suggests:
pn  bootchart2  

-- debconf information:
* insserv/enable: false

Bug#931255: regexps used seems to be incompatible with libpcre2 10.32

[Felix Zielcke]

Package: php-horde-text-filter
Version: 2.3.5-3
Severity: grave
Tags: patch

On buster with PHP 7.3 the tabs used on the horde settings webpage are empty 
instead of the usual General/Database etc.
With PHP 7.2 from packages.surey.org they work fine. They are linked against 
libpcre3 2:8.42

Log says:

WARN: HORDE [horde] PHP ERROR: preg_replace_callback(): Compilation failed: 
invalid range in character class at offset 68 [pid 21655 on line 99 of 
"/usr/share/php/Horde/Text/Filter.php"]

Problem seems to be that it doestn't like anymore ranges like [\w-+]. The 
hyphen needs to be first

Attached patch fixes it for me.

-- System Information:
Debian Release: 10.0
  APT prefers testing
  APT policy: (500, 'testing')
Architecture: amd64 (x86_64)

Kernel: Linux 4.19.0-5-amd64 (SMP w/1 CPU core)
Locale: LANG=de_DE.UTF-8, LC_CTYPE=de_DE.UTF-8 (charmap=UTF-8), 
LANGUAGE=de_DE.UTF-8 (charmap=UTF-8)
Shell: /bin/sh linked to /bin/dash
Init: systemd (via /run/systemd/system)

Versions of packages php-horde-text-filter depends on:
ii  php-common   2:69
ii  php-horde-exception  2.0.8-4
ii  php-horde-idna   1.1.1-3
ii  php-horde-util   2.5.8-3

Versions of packages php-horde-text-filter recommends:
pn  php-horde-test 
ii  php-horde-text-flowed  2.0.3-5
ii  php-horde-translation  2.2.2-3
pn  php-tidy   

Versions of packages php-horde-text-filter suggests:
pn  php-horde-text-filter-jsmin  

-- no debconf information
diff --git a/Horde_Text_Filter-2.3.5/lib/Horde/Text/Filter/Emails.php 
b/Horde_Text_Filter-2.3.5/lib/Horde/Text/Filter/Emails.php
index ad760b9..929d829 100644
--- a/Horde_Text_Filter-2.3.5/lib/Horde/Text/Filter/Emails.php
+++ b/Horde_Text_Filter-2.3.5/lib/Horde/Text/Filter/Emails.php
@@ -61,7 +61,7 @@ class Horde_Text_Filter_Emails extends Horde_Text_Filter_Base
 ((?(1)\s*\]))
 |
 # Version 2 Pattern 9 and 10: simple email addresses.
-(^|\s||<|\[)([\w-+.=]+@[-A-Z0-9.]*[A-Z0-9])
+(^|\s||<|\[)([-\w+.=]+@[-A-Z0-9.]*[A-Z0-9])
 # Pattern 11 to 13: Optional parameters
 ((\?)([^\s"<]*[\w+#?\/&=]))?
 # Pattern 14: Optional closing bracket
diff --git a/Horde_Text_Filter-2.3.5/lib/Horde/Text/Filter/Linkurls.php 
b/Horde_Text_Filter-2.3.5/lib/Horde/Text/Filter/Linkurls.php
index a88dc12..72e19ec 100644
--- a/Horde_Text_Filter-2.3.5/lib/Horde/Text/Filter/Linkurls.php
+++ b/Horde_Text_Filter-2.3.5/lib/Horde/Text/Filter/Linkurls.php
@@ -86,7 +86,7 @@ class Horde_Text_Filter_Linkurls extends 
Horde_Text_Filter_Base
 (?:\b|^)
 (  # Capture 1: entire matched URL
   (
-   (?:[a-z][\w-+]{0,19})?:/{1,3}  # URL protocol and colon followed by 1-3
+   (?:[a-z][-\w+]{0,19})?:/{1,3}  # URL protocol and colon followed by 1-3
   # slashes, or just colon and slashes (://)
 | #  - or -
 (?

Bug#926509: keepassxc: Please update to Version 2.4.0

[Felix Zielcke]

Am Samstag, den 06.04.2019, 12:28 +0200 schrieb Julian Andres Klode:
> On Sat, Apr 06, 2019 at 11:23:29AM +0200, Philipp Kolmann wrote:
> > Package: keepassxc
> > Version: 2.3.4+dfsg.1-1
> > Severity: wishlist
> > 
> > Hi,
> > 
> > could you please update keepassxc to the latest release 2.4.0.
> > 
> > https://keepassxc.org/blog/2019-03-19-2.4.0-released/
> 
> No, we're in freeze.
> 

Hi,

it would be nice if you could make an upload to experimental. That
would be independent of the freeze.

Thanks
Felix

Bug#929381: needs cdrecord binary which isn't in Debian

[Felix Zielcke]

Package: simpleburn
Version: 1.8.0-1+b3
Severity: grave

I tried burning an iso with simpleburn but it completely fails due to depending 
on cdrecord:

$ simpleburn
command: simpleburn.sh /dev/cdrom b-iso 'debian-buster-DI-rc1-amd64-netinst.iso'
/usr/bin/simpleburn.sh: line 171: cdrecord: command not found

cdrecord isn't avaible even in oldstable.

-- System Information:
Debian Release: 10.0
  APT prefers unstable
  APT policy: (500, 'unstable'), (1, 'experimental')
Architecture: amd64 (x86_64)
Foreign Architectures: i386

Kernel: Linux 4.19.0-5-amd64 (SMP w/4 CPU cores)
Kernel taint flags: TAINT_OOT_MODULE, TAINT_UNSIGNED_MODULE
Locale: LANG=de_DE.UTF-8, LC_CTYPE=de_DE.UTF-8 (charmap=UTF-8), 
LANGUAGE=de_DE.UTF-8 (charmap=UTF-8)
Shell: /bin/sh linked to /bin/dash
Init: systemd (via /run/systemd/system)
LSM: AppArmor: enabled

Versions of packages simpleburn depends on:
ii  cdrdao   1:1.2.4-1
ii  cdrskin  1.5.0-1
ii  icedax   9:1.1.11-3+b2
ii  libatk1.0-0  2.30.0-2
ii  libc62.28-10
ii  libcairo-gobject21.16.0-4
ii  libcairo21.16.0-4
ii  libcddb2 1.3.2-6
ii  libcdio-utils2.0.0-2
ii  libcdio182.0.0-2
ii  libdvdread4  6.0.1-1
ii  libfribidi0  1.0.5-3.1
ii  libgdk-pixbuf2.0-0   2.38.1+dfsg-1
ii  libglib2.0-0 2.58.3-1
ii  libgtk-3-0   3.24.5-1
ii  libpango-1.0-0   1.42.4-6
ii  libpangocairo-1.0-0  1.42.4-6
ii  xorriso  1.5.0-1

Versions of packages simpleburn recommends:
pn  flac
pn  mencoder
pn  mpg123  
pn  mplayer | mplayer2  
pn  normalize-audio 
pn  vorbis-tools

simpleburn suggests no packages.

-- no debconf information

Bug#911921: Bug ##911921: yubikey-manager new upstream version 1.0.1

[Felix Zielcke]

Am Samstag, den 09.03.2019, 17:21 +0100 schrieb Nicolas Braud-Santoni:
> Hi Felix,

Hi Nicolas,

> On Fri, Feb 08, 2019 at 09:03:37AM +0100, Felix Zielcke wrote:
> > Any chance that you could also package yubikey-manager-qt and
> > update
> > (the much outdated) yubioath-desktop?
> > I thought about doing it myself, but I'm just a DM. So I would need
> > a
> > sponsor.
> 
> I'm not using those GUI applications, so I wouldn't be familiar
> enough with them
> to feel comfortable maintaining them myself -- what if the
> functionality is
> broken and I don't notice? -- but I can definitely be your sponsor
> for
> maintaining those (and eventually get you direct upload rights there,
> since you
> are already a DM).
> 
> Would you also be interested in co-maintaining yubikey-manager?
> 

Great. I like to join the authentication team and help you.
My salsa login is be: fzielcke-guest

I'm just not so familiar with git. Especially because upstream ships a
debian/ directory in their git repos. I have to figure out how to
manage this.


> > And for yubikey-manager-qt it's now too late anyway to get it
> > into buster.
> 
> Same for yubioath-desktop: it was dropped from testing in 2017, so
> the soft
> freeze would have prevented it from re-entering.
> 
> We can make it available in buster-backports though, if that's
> something you
> need; I recently applied for upload access to backports  :)
> 

I was more thinking for the other users of Debian :-)
I myself use unstable anyway.


Do I need to file an intent to salvage bug and wait 3 weeks or could I
just go ahead?
I noticed now on github, that the Yubico people gave up maintaining the
official Debian packages and just care now about their Ubuntu PPA:

https://github.com/Yubico/yubioath-desktop/issues/328#issuecomment-457492367

> Best,
> 
>   nicoo

Thanks again Nicoo
Felix

Bug#784512: [Python-modules-team] Bug#784512: Remove pyside?

[Felix Zielcke]

Am Freitag, den 01.03.2019, 14:32 -0300 schrieb Lisandro Damián Nicanor
Pérez Meyer:
> 
> removing it also means removing python-ghost, yubikey-piv-manager and
> yubioath-desktop
> 

Hi,

the version of yubioath-desktop in sid is very old.
Current upstream version uses pyotherside which has been salvaged by me
for this reason.
There's already #886810 filed against yubioath-desktop but it seems
that it currently doestn't have any active maintainers.

Regards
Felix

Bug#911921: Bug ##911921: yubikey-manager new upstream version 1.0.1

[Felix Zielcke]

Am Donnerstag, den 07.02.2019, 22:29 +0100 schrieb Nicolas Braud-
Santoni:
> On Fri, Oct 26, 2018 at 09:17:32AM +0200, Felix Zielcke wrote:
> > Dear Maintainer,
> > 
> > please package the new upstream version 1.0.1 released by Yubico.
> > This adds support for the new Yubikey 5 series which I just bought.
> 
> Dear Felix,
> 
> Sorry for failing to notice your bug for so long.
> I have been struggling with health issues in the last half year, so
> the 
> maintainership of my packages suffered.  :(
> 
> I am uploading version 2.0.0 tonight, so you should enjoy support for
> your
> Yubikey 5 very soon!
> 
> 
> Best,
> 
>   nicoo

Hi Nicoo,

thanks very much for the upload. In the meanwhile I've used a
selfcompiled version.
Any chance that you could also package yubikey-manager-qt and update
(the much outdated) yubioath-desktop?
I thought about doing it myself, but I'm just a DM. So I would need a
sponsor. And for yubikey-manager-qt it's now too late anyway to get it
into buster.

Regards
Felix

Bug#886810: yubioath-desktop: New upstream release: 4.3.2

[Felix Zielcke]

Am Freitag, den 26.10.2018, 09:22 +0200 schrieb Felix Zielcke:
> On Wed, 10 Jan 2018 07:00:04 +0200 Tristan Seligmann <
> mithra...@mithrandi.net> wrote:
> > Package: yubioath-desktop
> > Version: 3.0.1-2
> > Severity: wishlist
> > 
> > There is a new upstream version available.
> > 
> 
> Hello,
> 
> any plans to upload the new 4.3.4 version?
> 3.0.1 is now very old and doesn't work with the new Yubikey 5 series
> which got released this year.

Hi,

an news about an upload of the current upstream version?
pyotherside, which the new version depends on, has been now updated in
unstable and testing.
So the current version builds and runs fine on sid without any change.
Freeze is nearing slowly and it would be great if buster would have it.

Regards
Felix

Bug#912739: RFS: pyotherside/1.5.3-1 [RC] [ITA]

[Felix Zielcke]

Package: sponsorship-requests
Severity: important

  Dear mentors,

  I am looking for a sponsor for my package "pyotherside"

 * Package name: pyotherside
   Version : 1.5.3-1
   Upstream Author : Thomas Perl 
 * URL : https://thp.io/2011/pyotherside/
 * License : ISC
   Section : libs

  It builds those binary packages:

pyotherside - transitional dummy package
 pyotherside-doc - asynchronous Python 3 Bindings for Qt 5 (documentation)
 pyotherside-tests - Asynchronous Python 3 Bindings for Qt 5 (tests)
 qml-module-io-thp-pyotherside - asynchronous Python 3 Bindings for Qt 5 (QML 
plugin)

  To access further information about this package, please visit the following 
URL:

  https://mentors.debian.net/package/pyotherside


  Alternatively, one can download the package with dget using this command:

dget -x 
https://mentors.debian.net/debian/pool/main/p/pyotherside/pyotherside_1.5.3-1.dsc

  More information about pyotherside can be obtained from 
https://thp.io/2011/pyotherside/.

  Changes since the last upload:

  * Salvage and take over maintainership. (Closes: #912720)
  * New upstream version.
- Fixes compatibility with newer QT versions. (Closes: #880093)
  * Add libqt5svg5-dev to the build dependencies.
  * Update to policy 4.2.1.
  * Remove old VCS Urls.
  * Update watch file.
  * Incorporate changes made on salsa by Chris Lamb and Ondřej Nový
- Respect nocheck in DEB_BUILD_OPTIONS.
- d/control: Remove ancient X-Python3-Version field.
- d/tests: Use AUTOPKGTEST_TMP instead of ADTTMP.
- d/changelog: Remove trailing whitespaces.
- d/control: Deprecating priority extra as per policy 4.0.1.
- d/copyright: Use https protocol in Format field.
- d/control: Remove ancient X-Python3-Version field.


  Regards,
   Felix Zielcke



signature.asc
Description: This is a digitally signed message part

Bug#912720: ITS: pyotherside

[Felix Zielcke]

Package: pyotherside
Severity: important


Dear Maintainers,

I intent to take over and salvage pyotherside according to chapter 5.12 of the 
developers-reference.

One week ago I wrote you all a mail if you are still interested in maintaining 
this package. But didn't got a reply.
The last upload is now almost 3 years old.
Over 1 year there is an RC bug open which has been already fixed upstream: 
#880093
There is still no reply at all from you.
As the bug submitter and I confirmed, you would only need to add libqt5svg5-dev 
to the build dependencies for the current upstream version 1.5.3.
Due to that RC bug the package has been removed from buster.
The version in experimental is linked against Python 3.5 and so can't be used 
with some Python 3.6 only modules.

I saw that the git repository was moved to salsa and that Ondřej Nový did some 
changes there. So I asked him if that package is still maintained but he 
replied to me that he did these changes by a script and don't intent to 
maintain it.

This package is needed to compile current upstream versions of the 
yubioath-desktop and yubikey-manager-qt packages.

I don't have any experience at all with QT and Python packages. If you or 
anyone else wants to step in then please feel free to do so.

Regards
Felix Zielcke

Bug#912442: new upstream version 0.5.1

[Felix Zielcke]

Package: yubikey-luks
Severity: wishlist


Hi Markus,

upstream has released version 0.5.1.
Any plans to package it for Debian?

Regards
Felix

Bug#912095: missing dependency on tracker

[Felix Zielcke]

Package: brasero
Version: 3.12.2-4
Severity: serious

Dear Maintainers,

I just installed brasero and wanted to start it. But it failed with the 
following error:

$ brasero

(brasero:1313): Tracker-ERROR **: 09:22:16.246: Unable to find default domain 
ontology rule /usr/share/tracker/domain-ontologies/default.rule
Trace/Breakpoint ausgelöst

After installing the missing tracker package it started fine.
I use MATE not Gnome. That's why I don't have that package installed by default.

Thanks in advance
Regards
Felix Zielcke

-- System Information:
Debian Release: buster/sid
  APT prefers unstable
  APT policy: (500, 'unstable')
Architecture: amd64 (x86_64)
Foreign Architectures: i386

Kernel: Linux 4.18.0-2-amd64 (SMP w/4 CPU cores)
Locale: LANG=de_DE.UTF-8, LC_CTYPE=de_DE.UTF-8 (charmap=UTF-8), 
LANGUAGE=de_DE.UTF-8 (charmap=UTF-8)
Shell: /bin/sh linked to /bin/dash
Init: systemd (via /run/systemd/system)
LSM: AppArmor: enabled

Versions of packages brasero depends on:
ii  brasero-common  3.12.2-4
ii  gstreamer1.0-plugins-base   1.14.4-1
ii  gvfs1.38.0-2
ii  libbrasero-media3-1 3.12.2-4
ii  libc6   2.27-6
ii  libcairo2   1.16.0-1
ii  libgdk-pixbuf2.0-0  2.38.0+dfsg-6
ii  libglib2.0-02.58.1-2
ii  libgstreamer-plugins-base1.0-0  1.14.4-1
ii  libgstreamer1.0-0   1.14.4-1
ii  libgtk-3-0  3.24.1-2
ii  libpango-1.0-0  1.42.4-3
ii  libtotem-plparser18 3.26.1-1
ii  libtracker-sparql-2.0-0 2.1.4-1
ii  libxml2 2.9.4+dfsg1-7+b1

Versions of packages brasero recommends:
pn  brasero-cdrkit  
pn  nautilus-extension-brasero  
ii  yelp3.30.0-1

Versions of packages brasero suggests:
ii  libdvd-pkg [libdvdcss2]  1.4.2-1-1
ii  libdvdcss2   1.4.2-1~local
ii  tracker  2.1.4-1
pn  vcdimager

-- no debconf information

Bug#886810: yubioath-desktop: New upstream release: 4.3.2

[Felix Zielcke]

On Wed, 10 Jan 2018 07:00:04 +0200 Tristan Seligmann <
mithra...@mithrandi.net> wrote:
> Package: yubioath-desktop
> Version: 3.0.1-2
> Severity: wishlist
> 
> There is a new upstream version available.
> 

Hello,

any plans to upload the new 4.3.4 version?
3.0.1 is now very old and doesn't work with the new Yubikey 5 series
which got released this year.

Are you still maintaining this package? If not then please orphan it.

Regards
Felix

Bug#911921: new upstream version 1.0.1

[Felix Zielcke]

Package: yubikey-manager
Version: 0.7.1-1
Severity: wishlist


Dear Maintainer,

please package the new upstream version 1.0.1 released by Yubico. This adds 
support for the new Yubikey 5 series which I just bought.
Thanks in advance

Regards
Felix

Bug#880093: pyotherside 1.2 cannot convert QVariant to QJSValue with qt5.7

[Felix Zielcke]

On Sun, 29 Oct 2017 13:18:54 +0100 Max Zhao 
wrote:
> Package: pyotherside
> Version: 1.2.0-1
> Severity: important
> Tags: upstream
> 
> Dear Maintainer,
> 
[...]
> Please consider updating the the package to the latest upstream
release 1.5.3. Since the issue has
> been resolved upstream.
> 
> I have already patched the debian source package locally to build
against the latest release,
> which only requires an added build dependency for libqt5svg5.
> 
> I am a complete newcomer in debian packaging and the bug reporting
system, if there are errors or missing
> information in my report, I would be glad be glad for corrections.
> 

Hello,

I had now the problem that I needed to recompile the
qml-module-io-thp-pyotherside package from experimental so it works
with Python3.6 instead of 3.5 which it currently uses.

I can confirm that version 1.5.3 compiles fine with just libqt5svg5-dev 
package added to the build dependencies.

Is this package actually still maintained? It would be great if it
could be updated. Some of the Yubikey packages depend on it. And they
are unfortunately also pretty outdated in unstable.

Regards
Felix

Bug#911603: evolution-data-server: Postinst script returned error exit status 1 with latest upload

[Felix Zielcke]

On Mon, 22 Oct 2018 09:53:31 -0400 Boyuan Yang 
wrote:
> Package: evolution-data-server
> Severity: serious
> Version: 3.30.2-1
> 
> % LANG=C.UTF-8 sudo apt install -f
> Reading package lists... Done
> Building dependency tree
> Reading state information... Done
> The following packages were automatically installed and are no longer
required:
>   android-libext4-utils android-libselinux android-libsepol
> Use 'sudo apt autoremove' to remove them.
> 0 upgraded, 0 newly installed, 0 to remove and 0 not upgraded.
> 1 not fully installed or removed.
> After this operation, 0 B of additional disk space will be used.
> Setting up evolution-data-server (3.30.2-1) ...
> dpkg: error processing package evolution-data-server (--configure):
>  installed evolution-data-server package post-installation script
> subprocess returned error exit status 1
> Errors were encountered while processing:
>  evolution-data-server
> E: Sub-process /usr/bin/dpkg returned an error code (1)
> 
> If you can't reproduce it, please let me know and I will provide with
> more details.

Hello,

I just got this bug too.
The problem is that update-notifier isn't installed.
The postinst doestn't clear the error from the test command.
I changed the line to
[ -x /usr/share/update-notifier/notify-reboot-required ] && 
/usr/share/update-notifier/notify-reboot-required || true

and it continued without problems.

Regards,
Felix

> --
> Regards,
> Boyuan Yang
> 
> 

Bug#890603: new version generates high load

[Felix Zielcke]

Am Freitag, den 16.02.2018, 18:56 +0100 schrieb Alex ARNAUD:
> Le 16/02/2018 à 18:47, Felix Zielcke a écrit :
> > Yes. The problem is then still there
> 
> Could you check if .xsession-errors is spammed by logs from 
> mate-power-manager ?
> 
> Best regards.

There are a bunch of entries like this one, but for different
processes:

** (mate-power-manager:1178): WARNING **: Couldn't register with
accessibility bus: Did not receive a reply. Possible causes include:
the remote application did not send a reply, the message bus security
policy blocked the reply, the reply timeout expired, or the network
connection was broken.

Bug#890603: new version generates high load

[Felix Zielcke]

Am Freitag, den 16.02.2018, 17:16 +0100 schrieb Alex ARNAUD:
> Le 16/02/2018 à 16:29, Felix Zielcke a écrit :
> > Hello,
> 
> Hello Felix,
> 
> > mate-applets and mate-power-manager in sid generate a high load on
> > my notebook. As soon as I downgrade to the versions in buster
> > everything is back to normal.
> > I haven't found out if this is more a bug in mate-applets or in
> > mate-power-manager.
> > I only use the power-manager applet and the sysmon one.
> > 
> > Please tell me if you need more information
> 
> Could you remove all the applets and check if the issue still occurs?
> If 
> not, could you add the applet one by one and tell us which one cause
> the 
> issue? What is sysmon, system-monitor?
> 
> Best regards.

Hi Alex,

yes I meant system-monitor.
It seems the problem is actually in mate-power-manager. I thought I
tried just downgrading that one to 1.18.
With applets at 1.20 and power-manager 1.18 the load is normal.
Wit power-manager 1.20 and the applets removed the load is still high.

/usr/lib/mate-power-manager/mate-inhibit-applet uses then 6% of CPU and
is in state sleeping. With 3.18 that process doestn't show up in top
sorted by CPU usage.

Regards

Bug#890603: new version generates high load

[Felix Zielcke]

Package: mate-applets
Version: 1.20.0-1
Severity: important

Hello,

mate-applets and mate-power-manager in sid generate a high load on my notebook. 
As soon as I downgrade to the versions in buster everything is back to normal.
I haven't found out if this is more a bug in mate-applets or in 
mate-power-manager.
I only use the power-manager applet and the sysmon one.

Please tell me if you need more information


-- System Information:
Debian Release: buster/sid
  APT prefers unstable
  APT policy: (501, 'unstable'), (500, 'experimental'), (499, 'testing')
Architecture: amd64 (x86_64)
Foreign Architectures: i386

Kernel: Linux 4.14.0-3-amd64 (SMP w/4 CPU cores)
Locale: LANG=de_DE.UTF-8, LC_CTYPE=de_DE.UTF-8 (charmap=UTF-8), 
LANGUAGE=de_DE.UTF-8 (charmap=UTF-8)
Shell: /bin/sh linked to /bin/dash
Init: systemd (via /run/systemd/system)
LSM: AppArmor: enabled

Versions of packages mate-applets depends on:
ii  gir1.2-mate-panel  1.20.0-1
ii  gsettings-desktop-schemas  3.27.90-1
ii  gvfs   1.34.1-2
ii  libatk1.0-02.26.1-3
ii  libc6  2.26-6
ii  libcairo-gobject2  1.15.10-1
ii  libcairo2  1.15.10-1
ii  libcpufreq0008-1+b1
ii  libdbus-1-31.12.4-1
ii  libdbus-glib-1-2   0.110-2
ii  libgdk-pixbuf2.0-0 2.36.11-1
ii  libglib2.0-0   2.54.3-2
ii  libgtk-3-0 3.22.28-1
ii  libgtksourceview-3.0-1 3.24.6-1
ii  libgtop-2.0-11 2.38.0-2
ii  libgucharmap-2-90-71:10.0.3-2
ii  libice62:1.0.9-2
ii  libiw3030~pre9-12+b1
ii  libmate-panel-applet-4-1   1.20.0-1
ii  libmateweather11.20.0-1
ii  libnotify4 0.7.7-3
ii  libpango-1.0-0 1.40.14-1
ii  libpangocairo-1.0-01.40.14-1
ii  libpolkit-gobject-1-0  0.113-6
ii  libsm6 2:1.2.2-1+b3
ii  libupower-glib30.99.7-2
ii  libwnck-3-03.24.1-2
ii  libx11-6   2:1.6.4-3
ii  libxml22.9.4+dfsg1-6.1
ii  mate-applets-common1.20.0-1
ii  mate-panel 1.20.0-1
ii  python 2.7.14-4
ii  python-gi  3.26.1-2

Versions of packages mate-applets recommends:
ii  cpufrequtils 008-1+b1
ii  mate-media   1.20.0-1
ii  mate-polkit  1.20.0-1
ii  mate-system-monitor  1.20.0-1

mate-applets suggests no packages.

-- no debconf information

Bug#883779: reiserfsprogs: conffiles not removed

[Felix Zielcke]

Am Donnerstag, den 07.12.2017, 22:16 +0800 schrieb Paul Wise:
> Package: reiserfsprogs
> Version: 1:3.6.27-1
> Severity: normal
> User: debian...@lists.debian.org
> Usertags: obsolete-conffile adequate
> 
> The recent upgrade did not deal with obsolete conffiles properly.
> Please use the dpkg-maintscript-helper support provided by
> dh_installdeb
> to remove these obsolete conffiles on upgrade.
> 

Hi Paul,

I don't understand why this is still the case.
I have in debian/reiserfsprogs.maintscript this line:

rm_conffile /etc/initramfs-tools/hooks/reiserfsprogs 1:3.6.25-5~ reiserfsprogs

And it gets added to the preinst/postinst/postrm scripts:

# Automatically added by dh_installdeb/10.10.9
dpkg-maintscript-helper rm_conffile /etc/initramfs-tools/hooks/reiserfsprogs 
1:3.6.25-5\~ reiserfsprogs -- "$@"
# End automatically added section

Is the version number the problem or what else could it be?

Regards
Felix

Bug#873634: missing module files libbd_*.so

[Felix Zielcke]

Package: udisks2
Version: 2.7.2-1
Severity: important

Hi,

I just upgraded udisks2 package to the new sid version and it failed to start 
its service:

# systemctl status udisks2.service

Aug 29 18:32:10 helios systemd[1]: Starting Disk Manager...
Aug 29 18:32:10 helios udisksd[7107]: udisks daemon version 2.7.2 starting
Aug 29 18:32:10 helios udisksd[7107]: failed to load module swap: 
libbd_swap.so.2: cannot open shared object file: No such file or directory
Aug 29 18:32:10 helios udisksd[7107]: failed to load module loop: 
libbd_loop.so.2: cannot open shared object file: No such file or directory
Aug 29 18:32:10 helios udisksd[7107]: failed to load module crypto: 
libbd_crypto.so.2: cannot open shared object file: No such file or directory
Aug 29 18:32:10 helios udisksd[7107]: failed to load module mdraid: 
libbd_mdraid.so.2: cannot open shared object file: No such file or directory
Aug 29 18:32:10 helios systemd[1]: udisks2.service: Main process exited, 
code=killed, status=5/TRAP
Aug 29 18:32:10 helios systemd[1]: Failed to start Disk Manager.

I used packages.d.o to find the package which contains these files, but haven't 
found one.

-- System Information:
Debian Release: buster/sid
  APT prefers unstable
  APT policy: (501, 'unstable'), (500, 'experimental')
Architecture: amd64 (x86_64)
Foreign Architectures: i386

Kernel: Linux 4.12.0-1-amd64 (SMP w/4 CPU cores)
Locale: LANG=de_DE.UTF-8, LC_CTYPE=de_DE.UTF-8 (charmap=UTF-8), 
LANGUAGE=de_DE.UTF-8 (charmap=UTF-8)
Shell: /bin/sh linked to /bin/dash
Init: systemd (via /run/systemd/system)

Versions of packages udisks2 depends on:
ii  dbus   1.11.16+really1.10.22-1
ii  init-system-helpers1.49
ii  libacl12.2.52-3+b1
ii  libatasmart4   0.19-4+b1
ii  libblockdev2   2.11-2
ii  libc6  2.24-17
ii  libglib2.0-0   2.53.6-1
ii  libgudev-1.0-0 230-3
ii  libpam-systemd 234-2.3
ii  libpolkit-agent-1-00.113-6
ii  libpolkit-gobject-1-0  0.113-6
ii  libsystemd0234-2.3
ii  libudisks2-0   2.7.2-1
ii  parted 3.2-17
ii  udev   234-2.3

Versions of packages udisks2 recommends:
ii  dosfstools   4.1-1
ii  e2fsprogs1.43.5-1
ii  eject2.1.5+deb1+cvs20081104-13.2
ii  exfat-utils  1.2.7-1
ii  ntfs-3g  1:2016.2.22AR.2-2
ii  policykit-1  0.113-6
pn  udftools 

Versions of packages udisks2 suggests:
ii  btrfs-progs 4.12-1
ii  cryptsetup-bin  2:1.7.3-4
pn  f2fs-tools  
pn  mdadm   
pn  nilfs-tools 
pn  reiserfsprogs   
pn  xfsprogs

-- no debconf information

Bug#844739: partclone FTBFS on mips and mipsel: reiser4progs need to be recompiled with -fPIC

[Felix Zielcke]

Am Freitag, den 18.11.2016, 16:54 +0100 schrieb Felix Zielcke:

> First it applies cleanly and then it complains.
> I don't get why. Quilt push works cleanly and quilt refresh does
> nothing.
> Do you have an idea why this patch makes problems? The other 2 work
> fine.

Ok silly me. I don't need a patch file for this anyway.

> Regards
> Felix

Bug#844739: partclone FTBFS on mips and mipsel: reiser4progs need to be recompiled with -fPIC

[Felix Zielcke]

Am Freitag, den 18.11.2016, 15:17 + schrieb Radovan Birdic:
> I have created and attached a patch that adds -fPIC flag and resolves
> this issue.
> With this patch package builds successfully on mips, mipsel, mips64el
> and i386 architectures.
> 
> Regards,
> Radovan

Hi Radovan,

thanks for the patches. But unfortunately debuild fails with it:

[...]
dpkg-source: info: applying fix_ldconfig.patch
dpkg-source: info: applying 05_libreiser4~profile.c.patch
dpkg-source: info: applying add-fPIC-for-mips.patch
 fakeroot debian/rules clean
[...]
dpkg-source: info: building reiser4progs using existing
./reiser4progs_1.1.0.orig.tar.gz
patching file debian/rules
Reversed (or previously applied) patch detected!  Skipping patch.
1 out of 1 hunk ignored
dpkg-source: info: the patch has fuzz which is not allowed, or is
malformed
dpkg-source: info: if patch 'add-fPIC-for-mips.patch' is correctly
applied by quilt, use 'quilt refresh' to update it
dpkg-source: error: LC_ALL=C patch -t -F 0 -N -p1 -u -V never -E -b -B
.pc/add-fPIC-for-mips.patch/ --reject-file=- < reiser4progs-
1.1.0.orig.DC8bmd/debian/patches/add-fPIC-for-mips.patch gave error
exit status 1
dpkg-buildpackage: error: dpkg-source -b reiser4progs-1.1.0 gave error
exit status 2

First it applies cleanly and then it complains.
I don't get why. Quilt push works cleanly and quilt refresh does
nothing.
Do you have an idea why this patch makes problems? The other 2 work
fine.

Regards
Felix

Bug#784856: duperemove

[Felix Zielcke]

Am Mittwoch, den 21.09.2016, 17:00 +0100 schrieb
peter.zahrad...@znik.sk:
> Hi Felix,
> 
> I can takeover building the package for this tool if you agree.
> 
> regards,
> Peter Zahradnik

Hi,

feel free to do so.

Regards,
Felix Zielcke

Bug#818161: Cannot use 'String' as class name as it is reserved

[Felix Zielcke]

Package: php-horde-css-parser
Version: 1.0.8-2
Severity: important


Hi,

I just upgraded the php-horde* packages to the new ones with support for PHP 7.
But I get the following error after login:

PHP Fatal error:  Cannot use 'String' as class name as it is reserved in 
/usr/share/php/Horde/Css/Parser/vendor/sabberworm/php-css-parser/lib/Sabberworm/CSS/Value/String.php
 on line 5

Regards
Felix Zielcke

Bug#804245: Please update initramfs in postinst

[Felix Zielcke]

Please make a NMU. 
I won't be able to do an upload soon

Am 6. November 2015 15:03:51 MEZ, schrieb Steve McIntyre :
>Source: reiser4progs
>Version: 1.1.0-1
>Severity: important
>Tags: d-i
>
>Hi!
>
>Since the move to systemd as the default init system, the initramfs
>will attempt to fsck and mount both / and /usr (where applicable). To
>aid this, initramfs-tools will copy necessary filesystem tools into
>the initramfs when it is generated.
>
>To make this work well, all filesystem tools packages for filesystems
>that are likely to be used for / and/or /usr should call
>"update-initramfs -u" in their postinst. This will
>
> (a) ensure that necesssary fsck tools are included in the initramfs
> generated by debian-installer (see #801961 for an example failure
> here); and
> (b) ensure that bug fixes to fsck tools get included immediately in
> the initramfs
>
>I've checked your package and I don't see any update-initramfs
>calls. Please add one, if you consider reiser4 to be a likely/sensible
>option as a base (/ or /usr) filesystem. If you'd like help doing that
>postinst work, I can supply a patch - just ask!

Bug#804247: Please update initramfs in postinst

[Felix Zielcke]

Please make a NMU. 
I won't be able to do an upload soon

Am 6. November 2015 15:07:06 MEZ, schrieb Steve McIntyre :
>Package: reiserfsprogs
>Version: 1:3.6.24-1
>Severity: important
>Tags: d-i
>
>Hi!
>
>Since the move to systemd as the default init system, the initramfs
>will attempt to fsck and mount both / and /usr (where applicable). To
>aid this, initramfs-tools will copy necessary filesystem tools into
>the initramfs when it is generated.
>
>To make this work well, all filesystem tools packages for filesystems
>that are likely to be used for / and/or /usr should call
>"update-initramfs -u" in their postinst. This will
>
> (a) ensure that necesssary fsck tools are included in the initramfs
> generated by debian-installer (see #801961 for an example failure
> here); and
> (b) ensure that bug fixes to fsck tools get included immediately in
> the initramfs
>
>I've checked your package and I don't see any update-initramfs
>calls. Please add one, if you consider reiserfs to be a
>likely/sensible option as a base (/ or /usr) filesystem. If you'd like
>help doing that postinst work, I can supply a patch - just ask!
>
>And yes - I've seen that you've recently added an initramfs hook for
>reiserfsprogs but AFAICS that won't necessarily get called unless you
>excplicitly run the update-initramfs command yourself.
>
>-- System Information:
>Debian Release: 8.2
>  APT prefers stable
>  APT policy: (500, 'stable')
>Architecture: amd64 (x86_64)
>Foreign Architectures: i386
>
>Kernel: Linux 3.16.0-4-amd64 (SMP w/4 CPU cores)
>Locale: LANG=en_GB.UTF-8, LC_CTYPE=en_GB.UTF-8 (charmap=UTF-8)
>Shell: /bin/sh linked to /bin/dash
>Init: systemd (via /run/systemd/system)
>
>Versions of packages reiserfsprogs depends on:
>ii  libc6 2.19-18+deb8u1
>ii  libuuid1  2.25.2-6
>
>reiserfsprogs recommends no packages.
>
>reiserfsprogs suggests no packages.
>
>-- no debconf information

Bug#784898: I would be interested

[Felix Zielcke]

Hi, 

sorry but I won't be able that soon to do anything for Debian

Am 6. November 2015 16:40:26 MEZ, schrieb Gianfranco Costamagna 
:
>-BEGIN PGP SIGNED MESSAGE-
>Hash: SHA256
>
>Hi Felix!
>
>ping, if you are still interested, please answer and fix the above :)
>(or ask about how to fix it)
>
>otherwise I'll close the RFS and unassign myself :)
>
>cheers,
>
>G.
>
>On Fri, 30 Oct 2015 09:02:33 -0400 Yaroslav Halchenko
> wrote:
>> Great to see activity going and please pardon me staying silent on
>> this issue ;)
>> 
>> Cheers everyone!
>> 
>> -- Yaroslav O. Halchenko Center for Open Neuroscience
>> http://centerforopenneuroscience.org Dartmouth College, 419 Moore
>> Hall, Hinman Box 6207, Hanover, NH 03755 Phone: +1 (603) 646-9834
>> Fax: +1 (603) 646-1419 WWW:   http://www.linkedin.com/in/yarik
>> 
>> 
>> 
>-BEGIN PGP SIGNATURE-
>Version: GnuPG v2
>
>iQIcBAEBCAAGBQJWPMnqAAoJEPNPCXROn13ZVPAP/R035jhoh/UJPKLRvMOzzkz7
>wLrC8h8otF5jh4BxBUlZwAH4jhb+CDTpcm7TADPoVuE+rwL3wzKFBZqkZgARH6gM
>wj6hVpmpyvrprAHWmpgldyf2Y2Hp/EBMQhJaevWQsIRW1bAfUJhKQCM9DrrrDFwV
>ZOFUSO7tTDHE7lWII6Wxz/P10s6JdEmAojnUeZZDdYUBVuxwNuOx9YI+v0c

Bug#784898: RFS: duperemove/0.10-1 [ITP]

[Felix Zielcke]

Am Mittwoch, den 14.10.2015, 18:41 +0100 schrieb Gianfranco Costamagna:


> thanks for the fix,

Thanks very much to both of you.
I created now a github fork for it:

https://github.com/fezie/duperemove

Though I didn't do much yet.

> 
> (please finish your NM process! we need you :p )


Thanks again very much.
You can't imagine how good that feels to me :-)

Regards
Felix

Bug#784898: RFS: duperemove/0.10-1 [ITP]

[Felix Zielcke]

Hi,

is there now anything missing for getting duperemove into Debian?

Bug#756253: Upgrade from 2.02~beta2-10 to 2.02~beta2-11 left grub unbootable

[Felix Zielcke]

Am Montag, den 24.08.2015, 10:28 +0200 schrieb Giorgio Valocchi:
 The problem was that the nvram entry wasn't properly created under 
 sid.
 
 I managed to login in a stable distribution I have on the same system 
 to 
 create it.

In that case it would be a bug either in efibootmgr or the Linux
Kernel.
grub-install just calls efibootmgr to create the entry

Bug#795810: grub-pc: passwords never allowed in config

[Felix Zielcke]

Am Montag, den 17.08.2015, 01:51 -0500 schrieb Richard Jasmin:
 
 I cannot follow grub-install option either.
 
 Installing for i386-pc platform.
 grub-install: warning: File system `ext2' doesn't support embedding.
 grub-install: warning: Embedding is not possible.  GRUB can only be 
 installed
 in this setup by using blocklists.  However, blocklists are 
 UNRELIABLE and
 their use is discouraged..
 grub-install: error: will not proceed with blocklists.
 
 This is an EXT4 system and its 64BIT. I had to force install in 32bit 
 mode to
 get Linux to take on this hardware.
 

Do you have a partition table or do you have ext4 directly on the full
device?


 -- Package-specific info:
 
 *** BEGIN /proc/mounts
 /dev/sda1 / ext4 rw,relatime 0 0
 *** END /proc/mounts
 
 *** BEGIN /boot/grub/grub.cfg
 

Please attach your complete grub.cfg where the password doestn't work

Bug#784898: I would be interested

[Felix Zielcke]

Am Mittwoch, den 10.06.2015, 19:15 -0400 schrieb Yaroslav Halchenko:
 to see this package in Debian so I can provide review/sponsorship 
 when
 time allows (hopefully in the next day or so).
 
 meanwhile:  
 
 - make package really ready -- vcs fields should point to existing
   repository.  Do you want to keep it under collab-maint?  Then 
 please
   join the team at https://alioth.debian.org/projects/collab-maint an
 d
   initiate that repository
 
 Cheers,

Hi Yaroslav,

it got totally under.
But now in the DebConf15 packaging workshop I updated it now.
Just uploaded to mentors.
I haven't thought yet about collab-maint.
Are you interested in co-maintaining it or others?
Else it wouldn't make much sense for such a small package or does it?

Cheers,
Felix

Bug#756253: Upgrade from 2.02~beta2-10 to 2.02~beta2-11 left grub unbootable

[Felix Zielcke]

Am Mittwoch, den 21.01.2015, 00:58 + schrieb Steve McIntyre:
 On Wed, Jan 21, 2015 at 06:55:05AM +0900, Mike Hommey wrote:
  On Tue, Jan 20, 2015 at 01:44:37PM +, Steve McIntyre wrote:
   
   The automatic setup of grub-install calling efibootmgr won't be
   touching the grub entry at all - it's set up to only play with
   debian entries. So that should be safe.
  
  Was it always a debian entry?
 
 As far back as I remember, yes.
 
But then comes the second thing: when I reboot, the debian 
entry is
lost. Poof, disappeared. And I do wonder if the initial problem 
is not
related to that.
   
   That is still happening? Can you successfully re-create it each 
   time?
  
  It happens reliably. efibootmgr displays it, but after a reboot, 
  it's
  gone.
 
 OK, now that's just *weird* and suggests a firmware bug to me. I'd be
 tempted to try and create an exact copy with another name and see how
 that works, but I'm struggling to understand what's going on here 
 now!
 

Is still a problem or got it somehow solved?

Bug#772795: grub installation fails on a fakeraid/sataraid/dmraid system

[Felix Zielcke]

Am Donnerstag, den 11.12.2014, 12:49 +0530 schrieb Pirate Praveen:
 package: grub-pc
 version: 1.99-27+deb7u2
 severity: critical
 
 I had to spend a lot of time researching on the internet to finally 
 find
 this https://wiki.debian.org/DebianInstaller/SataRaid and install 
 grub
 manually. This was wheezy 7.7.0 DVD 1.
 
 I don't know if debian installer can detect a sataraid system and 
 load
 dm-raid module manually (I'll open another bug for that). But grub
 installation should not fail when dmraid=true.
 
 Instead of suggesting to install on /dev/mapper grub should choose 
 the
 correct devise like /dev/mapper/isw_bdfjhfbiei_Volume1 when 
 dmraid=true
 is present in the kernel command line.
 
 Server model is Dell PowerEdge T20 and SATA controller is Intel C226
 chipset.
 
Is this still a problem with jessie or got it solved?

Bug#735932: [grub2-common] Computer does not boot

[Felix Zielcke]

Am Montag, den 13.10.2014, 15:54 +0100 schrieb Colin Watson:
 On Wed, Jan 29, 2014 at 05:54:40PM +0100, Vincent Barichard wrote:
  I had the same issue, and I succeeded to recover by using a live cd 
  and a
  chroot environment.
  In the chroot environment I reinstalled grub with : grub-install -
  -removable
  
  It updates the file in EFI/boot/ instead of EFI/debian.
  I hope it will help.
 
 This may well be a quite different issue from that of the original
 reporter, who has so far not indicated whether they were using BIOS 
 or
 UEFI.  Your issue is #708430.
 

Hi Marco,

is this still a problem?
If so, could you please provide more information?

Like the above question if this is BIOS or EFI

Bug#752381: initramfs-tools: does not activate logical volume before trying to mount root filesystem on LVM

[Felix Zielcke]

Am Montag, den 23.06.2014, 10:42 +0200 schrieb Martin Steigerwald:
 What did I do:
 
 Today I installed backports version of open-vm-dkms and upgraded to 
 most
 recent 3.14 backport kernel from a previous version of it I installed 
 due
 to using BTRFS with skinny meta data on one partition.
 
 
 Current results:
 
 After this the machine failed to boot. It didn´t find the root 
 filesystem
 by its UUID. I typed vgchange -ay in initramfs and then Ctrl-D and 
 then
 it booted. This used to work without manual interaction before.

Hi Martin,

is there still something to do for us grub2 maintainers or is it
solved?
I'm a bit confused with the control mails from Ben Hutchings.

Cheers,
Felix