Bug#1042837: Acknowledgement (signify-openbsd: Embedding signature in gz header does not work)

On Sun, 5 Nov 2023, at 16:43, Tomasz Buchert wrote: > the "binary garbage" you see is actually the exact contents of the gz > file for which you verify. See: > > [ ~/test ] $ cat out.gz | signify-openbsd -Vz -p ~/.ssh/signify.pub | cat > x > [ ~/test ] $ diff x out.gz > > (i.e., out.gz and the

Bug#1042837: Acknowledgement (signify-openbsd: Embedding signature in gz header does not work)

Hi Thomas, On Sun, 5 Nov 2023, at 14:19, Tomasz Buchert wrote: > On 01/08/23 17:15, Nikolaus Rath wrote: >> Using -x instead of -m when verifying gives "interesting" output: >> >> $ signify-openbsd -Vz -p s3ql-5.0.pub -x signed.gz >> untrus

Bug#1049327: leafnode: Bullseye upgrade switches to socket activation, disables host restrictions

Package: leafnode Version: 1.12.0-2 Severity: important Hi, After upgrading to bullseye, leafnode switched to systemd socket activation. As a side effect, access control settings in /etc/hosts.allow are no longer honored, and the service accepts connections from everywhere. According to

Bug#1042837: Acknowledgement (signify-openbsd: Embedding signature in gz header does not work)

Using -x instead of -m when verifying gives "interesting" output: $ signify-openbsd -Vz -p s3ql-5.0.pub -x signed.gz untrusted comment: verify with s3ql-5.0.pub RWSKPEtoJRYfrolP1xcoVCAxdIGvBp+I600+z5r4Ckcknx45J4pGrYvhlrWn6WTtwom7mTyjT7epM/oQyhfn/UbuKTR7pjN+0g0= date=2023-08-01T16:10:04Z

Bug#1042837: signify-openbsd: Embedding signature in gz header does not work

Package: signify-openbsd Version: 31-3 Severity: normal Dear Maintainer, I believe this should work, but it does not: $ signify-openbsd -Sz -s signify/s3ql-5.0.sec -m dist/s3ql-5.1.0.tar.gz -x out.gz $ signify-openbsd -Vz -m out.gz -p signify-s3ql-5.0.pub signify-openbsd: can't open out.gz.sig

Bug#1030394: Bug#1040690: reassign bug to correct package

Hi, In case it helps, I also still have the "apt dist-upgrade" output for an affected system. I don't remember installing any elpa packages from non-stable, but I can't rule it out either. Best, -Nikolaus

Bug#1040920: Acknowledgement (gnome-flashback: Gnome flashback unsets XDG_SESSION_ID)

t think there is much I can do from > gnome-flashback to change anything... > > > On Mon, Jul 17, 2023 at 11:15 PM Nikolaus Rath wrote: >> __ >> Hi Alberts, >> >> I believe that way you can get *a session id*. However, the fact that the >> dbus query

Bug#1040920: Acknowledgement (gnome-flashback: Gnome flashback unsets XDG_SESSION_ID)

ind manager using > /org/freedesktop/login1/session/auto path? > > dbus-send --system --print-reply --dest=org.freedesktop.login1 > /org/freedesktop/login1/session/auto org.freedesktop.DBus.Properties.Get > string:org.freedesktop.login1.Session string:Id > > On Sun, Jul 16,

Bug#1040920: Info received (Bug#1040920: Acknowledgement (gnome-flashback: Gnome flashback unsets XDG_SESSION_ID))

Another finding: starting gnome-session with `--builtin` instead of `--systemd` works around the problem.

Bug#1040787: dh-elpa: Lots of missing eln files

On Sun, 16 Jul 2023, at 15:20, Sean Whitton wrote: > Hello, > > On Sun 16 Jul 2023 at 12:06pm +01, Nikolaus Rath wrote: > >> Hmm. I think the problem is not that the various elpa packages did not >> get installed correctly, but that they did not get removed fully. So >&g

Bug#1040920: Acknowledgement (gnome-flashback: Gnome flashback unsets XDG_SESSION_ID)

retitle 1040920 "Gnome flashback breaks out of logind session" thanks Upon closer examination, the problem is not that GNome flashback unsets XDG_SESSION_ID, but that it breaks out of the active logind session (so unsetting the variable is, in some way, correct). In other desktop environments

Bug#1040917: Acknowledgement (xss-lock: Crashes after unlock)

On Sun, 16 Jul 2023, at 12:09, Ian Campbell wrote: > On Sun, 2023-07-16 at 10:58 +0100, Nikolaus Rath wrote: >> If not, can you tell me how to test for it? > > xss-lock uses dbus to talk to logind, specifically the service > org.freedesktop.login1, path /org/freed

Bug#1040787: dh-elpa: Lots of missing eln files

you're supposed to have is > /usr/share/emacs/site-lisp/elpa/async-1.9.7 I don't think so, because I do not have the elpa-async package installed anymore. It's completely purged (not even config left). > > Le dimanche 16 juillet 2023 à 10:52, Nikolaus Rath a > écrit : > >&

Bug#1040917: Acknowledgement (xss-lock: Crashes after unlock)

On Sun, 16 Jul 2023, at 10:56, Ian Campbell wrote: > Hi Nikolaus, > > Thanks for your report. > > On Wed, 2023-07-12 at 18:38 +0100, Nikolaus Rath wrote: >> It seems that running xss-lock as `xss-lock -- >> session=${XDG_SESSION_ID}` works around this problem. > >

Bug#1040787: dh-elpa: Lots of missing eln files

On Sun, 16 Jul 2023, at 08:22, Sean Whitton wrote: > Hello, > > On Mon 10 Jul 2023 at 03:27pm +01, Nikolaus Rath wrote: > >> Package: dh-elpa >> Severity: normal >> >> After upgrading to bookworm, I'm getting many warnings when starting >> emacs: >

Bug#1040917: Acknowledgement (xss-lock: Crashes after unlock)

It seems that running xss-lock as `xss-lock --session=${XDG_SESSION_ID}` works around this problem.

Bug#1040920: Acknowledgement (gnome-flashback: Gnome flashback unsets XDG_SESSION_ID)

On Wed, 12 Jul 2023, at 13:22, Alberts Muktupāvels wrote: > Maybe... Why do you need that variable? > > On Wed, Jul 12, 2023 at 3:12 PM Nikolaus Rath wrote: >> Could this be an unintended side effect of >> https://salsa.debian.org/gnome-team/g

Bug#1040920: gnome-flashback: Gnome flashback unsets XDG_SESSION_ID

On Wed, 12 Jul 2023, at 13:00, Alberts Muktupāvels wrote: > GNOME Flashback does not do that! > > That variable is blacklisted by gnome-session: > https://gitlab.gnome.org/GNOME/gnome-session/-/blob/main/gnome-session/gsm-util.c#L38 Apologies if this came across the wrong way. What I mean is

Bug#1040920: Acknowledgement (gnome-flashback: Gnome flashback unsets XDG_SESSION_ID)

Could this be an unintended side effect of https://salsa.debian.org/gnome-team/gnome-session/-/commit/6f5c3c80be8f92ababd8d6201c5c58e732b47f54?

Bug#1040920: gnome-flashback: Gnome flashback unsets XDG_SESSION_ID

Package: gnome-flashback Version: 3.46.0-1 Severity: normal When starting a Gnome Flashback session, the XDG_SESSION_ID environment variable is not set. This results on applications that rely on logind to not behave properly. Debugging this more closely, I found that XDG_SESSION_ID is still set

Bug#1040917: xss-lock: Crashes after unlock

Package: xss-lock Version: 0.3.0+git20230128.0c562b-1 Severity: important On my system, xss-lock works exactly once. Then, after entering the password, it crashes with: # xss-lock xsecurelock ** (xss-lock:1213549): WARNING **: 12:24:06.393: Error getting session:

Bug#1040787: dh-elpa: Lots of missing eln files

Package: dh-elpa Severity: normal After upgrading to bookworm, I'm getting many warnings when starting emacs: Warning (comp): Cannot look-up eln file as no source file was found for /usr/share/emacs/site-lisp/elpa/dash-2.17.0/dash.elc Disable showing Disable logging Warning (comp): Cannot

Bug#994972: devscripts: uscan signature verification fails, probably due to gpgv not supporting armored keyrings

On Tue, 28 Sep 2021, at 16:07, Mattia Rizzolo wrote: >> I guess you can close this bug since I can't reproduce it >> anymore.. weird. > > Good then :) > You can merge my branch into master to turn it into ascii-armored :P Done, thank you! Best, Nikolaus -- GPG Fingerprint: ED31 791B 2C5C 1613

Bug#995110: libaio-dev: Some manpages missing (e.g. io(3))

Package: libaio-dev Version: 0.3.112-9 Severity: normal It seems to me that several manpages available upstream (https://pagure.io/libaio/blob/master/f/man) are missing in the debian package, e.g. io.3, and io_submit(3). -- System Information: Debian Release: 11.0 APT prefers stable-updates

Bug#994972: devscripts: uscan signature verification fails, probably due to gpgv not supporting armored keyrings

On Fri, 24 Sep 2021, at 11:00, Mattia Rizzolo wrote: >> At first I thought that the upstream signature file was corrupted, but >> it seems that gpgv can't deal with a the keyring if it is generated the >> way that uscan(1) says it should be: > > I'll need to check your specifc case, but I can

Bug#994972: devscripts: uscan signature verification fails, probably due to gpgv not supporting armored keyrings

pgv:using RSA key ED31791B2C5C1613AF388B8AD113FCAC3C4E599F gpgv: Good signature from "Nikolaus Rath " -- Package-specific info: --- /etc/devscripts.conf --- Empty. --- ~/.devscripts --- DEBCHANGE_RELEASE_HEURISTIC=changelog -- System Information: Debian Release: 11.0 APT prefers stable-updates

Bug#994171: elpa-jedi-core incompatible with python3-jedi in bullseye

Package: elpa-jedi-core Version: 0.2.8-1 Severity: grave The elpa-jedi-core package in bullseye is incompatible with the python3-jedi package shipped in bullseye, thus rendering this package mostly useless (justifying 'grave' severity). I hope that maybe the problem can be solved with a

Bug#959117: Unable to mount with fuse3 (fusermount: unknown option 'nonempty')

Hi Graham, It might be fixed, I'm afraid I can't tell any better than you. I am no longer using the Debian packages. Best, -Nikolaus -- GPG Fingerprint: ED31 791B 2C5C 1613 AF38 8B8A D113 FCAC 3C4E 599F »Time flies like an arrow, fruit flies like a Banana.« On Fri, 8 Jan 2021,

Bug#912752: Status of pyfuse3 and s3ql

Hi Francesco, I have no idea about the status of pyfuse3 Debian packages. All I know is this: I do not have much time for Debian packaging anymore. I would rather have someone else package S3QL, but as long as no one adopts it, I will continue to do releases as long as the effort is small.

Bug#959117: Unable to mount with fuse3 (fusermount: unknown option 'nonempty')

Note that this is actually a problem with the fuse3 package: it provides the fusermount binary without accepting the -o nonempty mount option. fuse3 must not provide fusermount, only fusermount3. (I am not re-assigning this bug since the problem can also be worked around in S3QL, and IIRC

Bug#959117: Unable to mount with fuse3 (fusermount: unknown option 'nonempty')

Control: severity 959117 important thanks Hi Graham, This package is up for adoption. The only that's needed to get it in shape again is to upgrade to the newest upstream release. However, this requires packaging the new python3-pyfuse3 dependency first. I'm also downgrading the severity,

Bug#979137: s3ql: Update to newest upstream release

Package: s3ql Severity: serious Justification: N/A There is a new upstream release that fixes a number of bugs against the Debian package. However, it is blocked on a dependency on the python3-pyfuse3 module that is not in Debian. Uploading python3-pyfuse3 and the newest S3QL release would make

Bug#977104: s3ql: Missing dependency on python3-systemd

On Dec 10 2020, Leandro Lisboa Penz wrote: > Package: s3ql > Version: 3.3.2+dfsg-2+b2 > Severity: important > > Dear Maintainer, > > The package is missing a dependency on python3-systemd: > > $ mount.s3ql --systemd --log none --fg s3://... "$HOME/..." > <6>Using 10 upload threads. >

Bug#977093: s3ql FTBFS with pytest 6

On Dec 10 2020, Christian Kastner wrote: > Source: s3ql > Version: 3.3.2+dfsg-2 > Severity: important > User: pyt...@packages.debian.org > Usertags: pytest-v6 > > Hi, > > s3ql FTBFS with pytest 6 in experimental because it uses a > removed feature "catch_log_handler", see: > >

Bug#977086: python-dugong FTBFS with pytest 6

On Dec 10 2020, Christian Kastner wrote: > Source: python-dugong > Version: xx > Severity: important > User: pyt...@packages.debian.org > Usertags: pytest-v6 > > Hi, > > python-dugong FTBFS with pytest 6 in experimental because it uses a > removed feature "catch_log_handler", see: > >

Bug#912752: Update on packaging status?

Hi Raphael, Thanks for asking. I'm afraid I won't have time to maintain another Debian package for the foreseeable future. Best, -Nikolaus -- GPG Fingerprint: ED31 791B 2C5C 1613 AF38 8B8A D113 FCAC 3C4E 599F »Time flies like an arrow, fruit flies like a Banana.«

Bug#958989: dgit-user(7): building instructions don't work

On Apr 30 2020, Ian Jackson wrote: > Nikolaus Rath writes ("Bug#958989: dgit-user(7): building instructions don't > work"): >> Here's another datapoint: >> >> $ dgit clone valgrind >> $ cd vagrind; sbuild -c buster-amd64 >> >> works fine (i.e

Bug#958989: dgit-user(7): building instructions don't work

On Apr 30 2020, Ian Jackson wrote: > Nikolaus Rath writes ("Bug#958989: dgit-user(7): building instructions don't > work"): >> Here's another datapoint: >> >> $ dgit clone valgrind >> $ cd vagrind; sbuild -c buster-amd64 >> >> works fine (i.e

Bug#958989: dgit-user(7): building instructions don't work

On Apr 29 2020, Ian Jackson wrote: > Nikolaus Rath writes ("Bug#958989: dgit-user(7): building instructions don't > work"): >> On Apr 28 2020, Ian Jackson wrote: >> >mkdir ../aside >> >mv ../valgrind_* ../aside >> >sbuild --chroo

Bug#958989: dgit-user(7): building instructions don't work

On Apr 28 2020, Ian Jackson wrote: > Could I get you to do this: > > sbuild -c buster-amd64 -b -n 958989 Uhm. I feel pretty dumb, but what is the "958989" supposed to do? $ sbuild -c buster-amd64 -b -n 958989 No distribution defined Without that, I get: $ git reset --hard $ git clean -xdf $

Bug#958989: dgit-user(7): building instructions don't work

.« On Tue, 28 Apr 2020, at 12:54, Ian Jackson wrote: > Nikolaus Rath writes ("Bug#958989: dgit-user(7): building instructions > don't work"): > > FWIW, I have tried this on an AMD64 buster system with an AMD64 chroot. > > When compiling without schroot it works fine

Bug#958989: dgit-user(7): building instructions don't work

computer until tonight.) Best, Nikolaus -- GPG Fingerprint: ED31 791B 2C5C 1613 AF38 8B8A D113 FCAC 3C4E 599F »Time flies like an arrow, fruit flies like a Banana.« On Tue, 28 Apr 2020, at 12:42, Ian Jackson wrote: > Nikolaus Rath writes ("Re: Bug#958989: dgit-user(7):

Bug#958989: dgit-user(7): building instructions don't work

Hi Ian, Thanks for the quick response! On Apr 27 2020, Ian Jackson wrote: > Nikolaus Rath writes ("Bug#958989: dgit-user(7): building instructions don't > work"): >> I'm trying to follow dgit-user(7) to build a modified version of a package. >> I did: > &g

Bug#958989: dgit-user(7): building instructions don't work

ce package valgrind dpkg-buildpackage: info: source version 1:3.15.0-2~1.gbpd4e99a dpkg-buildpackage: info: source distribution UNRELEASED dpkg-buildpackage: info: source changed by Nikolaus Rath dpkg-source --before-build . dpkg-buildpackage: info: host architecture amd64 fakeroot debian/rules clea

Bug#939767: fuse3: Installing fuse3 breaks fuse2 applications using -o nonempty

Hi Dmitry, I think you are confusing mounting into a directory that already contains files with re-mounting the same filesystem on top of itself. Refusing to use a non-empty directory as a mountpoint does not prevent you from mounting the same filesystem multiple times, because the file system

Bug#939092: Workaround

The following workaround suppresses the bogus error, but probably also ignores legitimate problems: Create /etc/systemd/system/lvm2-pvscan@.service from /lib/systemd/system/lvm2-pvscan@.service but use: # Leading dash means to ignore exit status, necessary because # of

Bug#939092: More Info

The relevant .service file /lib/systemd/system/lvm2-pvscan@.service has: ExecStart=/sbin/lvm pvscan --cache --activate ay %i According to pvscan(8) this should result in: pvscan --cache -aay device... This begins by performing the same steps as above. Afterward, if the VG for

Bug#939767: fuse3: Installing fuse3 breaks fuse2 applications using -o nonempty

»Time flies like an arrow, fruit flies like a Banana.« On Sun, 8 Sep 2019, at 16:54, László Böszörményi (GCS) wrote: > On Sun, Sep 8, 2019 at 5:24 PM Nikolaus Rath wrote: > > fuse3 currently declares 'Replaces: fuse', but it is not actually a > > drop-in replacement. FUSE

Bug#939767: fuse3: Installing fuse3 breaks fuse2 applications using -o nonempty

Package: fuse3 Version: 3.4.1-1 Severity: important fuse3 currently declares 'Replaces: fuse', but it is not actually a drop-in replacement. FUSE 2.x filesystems that use the '-o nonempty' mount option (which was removed in FUSE 3) break with fusermount: unknown option 'nonempty' if fuse3 is

Bug#939649: /usr/bin/systemd-nspawn: systemd-nspawn fails with "Failed to register machine: Unit -.mount is masked."

On Sat, 7 Sep 2019, at 11:44, Michael Biebl wrote: > Control: tags -1 moreinfo > > Am 07.09.19 um 11:36 schrieb Nikolaus Rath: > > Package: systemd-container > > Version: 241-5 > > Severity: normal > > File: /usr/bin/systemd-nspawn > > > > Not

Bug#939649: /usr/bin/systemd-nspawn: systemd-nspawn fails with "Failed to register machine: Unit -.mount is masked."

Package: systemd-container Version: 241-5 Severity: normal File: /usr/bin/systemd-nspawn Not sure what to make of this: # systemd-nspawn -M resuce --boot --private-users -D /mnt/usbdrive Spawning container resuce on /mnt/usbdrive. Press ^] three times within 1s to kill container. Selected user

Bug#769607: systemd does not show shutdown or reboot messages with systemd.show_status=true

On Sep 04 2019, Michael Biebl wrote: > On Thu, 27 Nov 2014 14:43:33 -0800 Nikolaus Rath wrote: >> On Sat, 15 Nov 2014 00:17:59 +0100 Szymon Weihs wrote: >> > >> > When I'm doing reboot or shutdown from graphical environment (systemctl >> > reboot/poweroff),

Bug#939092: lvm2: Spurious(?) failure of lvm2-pvscan systemd unit

Package: lvm2 Version: 2.03.02-3 Severity: normal After upgrading to buster, I noticed that, according to `systemctl status` my system is always in degraded mode: # systemctl status | head ● vostro.rath.org State: degraded Jobs: 0 queued Failed: 1 units Since: Sun 2019-09-01

Bug#939023: More details

Maybe it's related to the amount of packages scheduled for removal? Some more experiments: # aptitude purge --schedule-only '~i ~pextra' (works) # aptitude purge --schedule-only '~i ~poptional' [ ERR] Writing extended state information -- GPG Fingerprint: ED31 791B 2C5C 1613 AF38 8B8A D113

Bug#939023: aptitude purge fails with [ ERR] Writing extended state information

Package: aptitude Version: 0.8.11-7 Severity: normal # Mark all non-essential packages for deletion # aptitude purge --schedule-only '~i !~E' [ ERR] Writing extended state information Not sure what to make of it. My first guess was insufficient disk space - but there is plenty in all

Bug#932319: RFA: s3ql -- Full-featured file system for online data storage

Package: wnpp Severity: normal I request an adopter for the s3ql package. I am upstream author and have so far maintained the package in Debian as a DM, but no longer have the time. The packaging is on Salsa under the python-applications team umbrella. The package description is: S3QL is a

Bug#928949: unblock: s3ql/3.1+dfsg-2

On May 27, 2019 8:55:53 PM GMT+01:00, Paul Gevers wrote: >Control: tags -1 moreinfo > >Hi David, > >On Mon, 13 May 2019 15:52:56 -0400 David Gilman >wrote: >> Users who want to use s3ql with Google's cloud storage API need to >> obtain an OAuth credential with the appropriate permissions.

Bug#928824: s3ql: Please release s3ql 3.1 with buster for Google OAuth compatibility

Hi, I don't have any more influence over the release team than you do, so please feel free to petition them directly. I have no objections and see no problem with a freeze exception. Best, Nikolaus On May 11, 2019 8:42:07 PM GMT+01:00, David Gilman wrote: >Package: s3ql >Version: 3.0+dfsg-1

Bug#912752: ITP: pyfuse3 -- Python 3 bindings for libfuse 3 using asynchronous I/O

Package: wnpp Severity: wishlist Owner: Nikolaus Rath * Package name: pyfuse3 Version : 1.1 Upstream Author : Nikolaus Rath * URL : https://github.com/libfuse/pyfuse3 * License : LGPL Programming Lang: Python Description : Python 3 bindings

Bug#871019: sshfs: Please update to 3.x

Hi, libfuse3 is now available in Debian - so hopefully SSHFS 3 can follow before the freeze :-). Best, -Nikolaus -- GPG Fingerprint: ED31 791B 2C5C 1613 AF38 8B8A D113 FCAC 3C4E 599F »Time flies like an arrow, fruit flies like a Banana.«

Bug#910183: linux-image-4.18.0-0.bpo.1-amd64: Debian 4.18 kernels breaks Intel WiFi ("Failed to start INIT")

Package: src:linux Version: 4.18.6-1~bpo9+1 Severity: normal Hi, The 4.18 Debian kernel from stretch-backports breaks my WiFi. The device is not present. At boot, I am getting these suspicious messages: Oct 3 12:51:58 thinkpad kernel: [ 10.944087] iwlwifi :04:00.0: Failed to start INIT

Bug#840075: Update?

Hi Laszlo, Have you heard anything about package from FTP masters? As far as I can tell, it's been sitting in the NEW queue with activity for 2 months now... Thanks, -Niko -- GPG Fingerprint: ED31 791B 2C5C 1613 AF38 8B8A D113 FCAC 3C4E 599F »Time flies like an arrow, fruit flies

Bug#900518: plymouth-start.service: Start request repeated too quickly

In my case, this was triggered by a flood of "pstore: crypto_comp_decompress failed" messages from the kernel, and removing /sys/fs/pstore/dmesg* fixed the problem (cf https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=902966) -Nikolaus -- GPG Fingerprint: ED31 791B 2C5C 1613 AF38 8B8A D113 FCAC

Bug#840075: How to help getting libfuse updated?

On Jul 21 2018, "László Böszörményi (GCS)" wrote: > Hi, > > On Wed, Jun 27, 2018 at 1:09 PM Nikolaus Rath wrote: >> > > Please let me know if there is anything I can do. >> > >> > I've a bug report and a feature request. Will post it on your

Bug#749832: systemd: ignores /run/do-not-hibernate, hibernates after kernel update

On Jul 22 2018, Ben Hutchings wrote: > On Sat, 2018-07-21 at 10:54 +0100, Nikolaus Rath wrote: >> On Jul 21 2018, Ben Hutchings wrote: >> > > > Prior to installing systemd, hibernating was not possible after a >> > > > kernel >> >

Bug#749832: systemd: ignores /run/do-not-hibernate, hibernates after kernel update

On Jul 21 2018, Ben Hutchings wrote: >> > Prior to installing systemd, hibernating was not possible after a kernel >> > update. I believe the mechanism to prevent it was a >> > /run/do-not-hibernate file that is not used by systemd. >> >> Is there a distro-agnostic way to determine whether it's

Bug#771491: Resolved

On Jul 21 2018, Michael Biebl wrote: > On Sat, 29 Nov 2014 21:09:42 -0800 Nikolaus Rath wrote: >> This is a consequence of a missing swap partition (bug #771492). After >> fixing swap, hibernation works. >> >> Wishlist: indicate the problem (missing swap) in the

Bug#840075: Update?

Hi, Any news on this? It's been another 3 weeks already... Thanks! -Nikolaus -- GPG Fingerprint: ED31 791B 2C5C 1613 AF38 8B8A D113 FCAC 3C4E 599F »Time flies like an arrow, fruit flies like a Banana.« On Thu, 5 Jul 2018, at 08:10, Nikolaus Rath wrote: > Hi, > > A

Bug#840075: Update?

Hi, Any update on this? I've merged most of the pull request. I believe the changes to create a static library aren't necessary (see comment on pull request), and when using systemd there is no need for any specific unit file (see bug). Do you need me to make a new release? Best, -Nikolaus --

Bug#902652: aptitude: Does not autoremove kernel and can't tell me why

Package: aptitude Version: 0.8.7-1 Severity: normal For some reason aptitude refuses to automatically remove kernel packages that apt-get would remove - and it doesn't even know why: # apt autoremove Reading package lists... Done Building dependency tree Reading state information... Done

Bug#840075: How to help getting libfuse updated?

Hi, > > Please let me know if there is anything I can do. > > I've a bug report and a feature request. Will post it on your Git repository. Are you still working on this, or am I looking in the wrong place for it? I checked https://github.com/libfuse/libfuse/issues. Best, -Nikolaus -- GPG

Bug#840075: How to help getting libfuse updated?

Hi László, Great, thank you so much! Best, Modus On 26 June 2018 00:15:28 BST, "László Böszörményi (GCS)" wrote: >Control: tags -1 +pending > >On Sat, Jun 23, 2018 at 1:21 PM Nikolaus Rath >wrote: >> What kind of help would be needed to move this forward? >

Bug#840075: How to help getting libfuse updated?

control: retitle 840075 "Please package libfuse 3" thanks Hi Laszlo, What kind of help would be needed to move this forward? libfuse 3 has been released in 2016, and this bug has been open for even longer (giving advance notice and referring to a pre-release for testing) with no update. It

Bug#764557: Problem persists

Hi, With the failures that I have in the journal at the moment, journalctl does not hang. I can't say whether this is because the corruption just happens to be more benign or because journalctl has been fixed. Best, -Nikolaus -- GPG Fingerprint: ED31 791B 2C5C 1613 AF38 8B8A D113 FCAC 3C4E

Bug#764557: Problem persists

Hi, Did you see the text that I included in the reopening email? Maybe I should have addressed it differently. I wrote: reopen 764557 thanks Hi, I'm afraid the problem persists. On on up-to-date stretch system, I just got: # journalctl --verify [...] 00: Invalid tail monotonic timestamp

Bug#755809: Ping

Hi, *ping* It would be very nice to have this patch applied. Trying to disable a monitor by following the instructions in the current manpage is frustrating. Best, -Nikolaus -- GPG Fingerprint: ED31 791B 2C5C 1613 AF38 8B8A D113 FCAC 3C4E 599F »Time flies like an arrow, fruit flies

Bug#875600: network-manager: Unable to switch between different WiFi networks

Package: network-manager Version: 1.6.2-3 Severity: normal Hello, I have an interesting problem with network-manager: I am unable to switch between different WiFi networks (by selecting them in the systray list). However, if I first click on "Disconnect", and then select the new network,

Bug#874635: debian-kernel-handbook: Some outdated instructions in "Common Tasks"

Package: debian-kernel-handbook Severity: normal > Hello, > > I would like to rebuild a Debian kernel with an extra patch. I have > followed the instructions at > https://kernel-handbook.alioth.debian.org/ch-common-tasks.html#s-common-official: > > $ apt-get source -t stretch linux > $ cd

Bug#871019: sshfs: Please update to 3.x

Package: sshfs Version: 2.8-1 Severity: wishlist Dear Maintainer, Apart from the required libfuse 3.x not yet being in Debian, is there anything that would prevent updating the package to the most recent sshfs version? Thanks! -Nikolaus

Bug#840075: libfuse3 in stretch?

Package: libfuse2 Version: 2.9.7-1 Followup-For: Bug #840075 control: #840075 please package libfuse 3 Hi there, Do you have any update on libfuse 3 making it into the archive? I would like to see SSHFS updated to 3.1 in Debian, but this requires libfuse 3. Best, -Nikolaus

Bug#867226: aptitude seems dependency problems when there are none

On Aug 05 2017, "Manuel A. Fernandez Montecelo" <manuel.montez...@gmail.com> wrote: > Hi, > > 2017-07-04 23:24 Nikolaus Rath: >> >>However, according to aptitude, there is something seriously wrong: >> >>$ aptitude >># Select Action

Bug#867226: aptitude seems dependency problems when there are none

Package: aptitude Version: 0.8.7-1 Severity: normal According to apt, there are no dependency problems on my system: # apt install -f Reading package lists... Done Building dependency tree Reading state information... Done The following packages were automatically installed and are no

Bug#866529: [Pkg-xfce-devel] Bug#866529: thunar: Missing dependency for mounting removable media

> gvfs is actually in Thunar Recommends. Duh, right you are. Sorry about that, I must have messed something up when checking this yesterday. Best, -Nikolaus

Bug#866529: [Pkg-xfce-devel] Bug#866529: thunar: Missing dependency for mounting removable media

On Fri, Jun 30, 2017, at 04:31, Yves-Alexis Perez wrote: > On Thu, 2017-06-29 at 14:39 -0700, Nikolaus Rath wrote: > > I recently purged a lot of packages from my system. Now, I am no longer > > able to mount removable media in Thunar. They are no longer listed in > &g

Bug#866529: [Pkg-xfce-devel] Bug#866529: thunar: Missing dependency for mounting removable media

type "usb-storage". Does that ring any bells? Thanks! -Nikolaus -- GPG Fingerprint: ED31 791B 2C5C 1613 AF38 8B8A D113 FCAC 3C4E 599F »Time flies like an arrow, fruit flies like a Banana.« On Fri, Jun 30, 2017, at 04:31, Yves-Alexis Perez wrote: > On Thu, 2017-06-29 a

Bug#867041: debfoster removes package without prompt

Package: debfoster Version: 2.7-2.1+b1 Severity: normal After upgrading from jessie to stretch, debfoster is very confused and tends to remove a lot of packages that it should not. For example: $ apt install liferea Reading package lists... Done Building dependency tree Reading state

Bug#766927: debfoster: Removes packages I want to keep

Package: debfoster Version: 2.7-2.1+b1 Followup-For: Bug #766927 I am having the same problem, debfoster is removing packages I explicitly told it should keep. I am using the standard locale: $ locale LANG=en_US.UTF-8 LANGUAGE= LC_CTYPE="en_US.UTF-8" LC_NUMERIC="en_US.UTF-8"

Bug#866529: thunar: Missing dependency for mounting removable media

Package: thunar Version: 1.6.3-2 Severity: normal Hello, I recently purged a lot of packages from my system. Now, I am no longer able to mount removable media in Thunar. They are no longer listed in the Tree side pane. I am pretty sure that this is because of a package that I uninstalled, but

Bug#769369: Workaround found

On Jun 02 2017, Michael Biebl <bi...@debian.org> wrote: > Control: tags -1 + moreinfo > > Hi Nikolaus > > On Thu, 27 Nov 2014 15:00:01 -0800 Nikolaus Rath <nikol...@rath.org> wrote: >> Hello, >> >> I have found that adding >> >> ExecSt

Bug#863361: dgit-user(7): replace apt-get build-deps with mk-build-deps

Package: dgit Version: 3.10~bpo8+1 Severity: normal Please consider replacing % sudo apt-get build-dep glibc with % mk-build-dep --root-cmd=sudo --install That way, you won't get bitten if the build deps of the new package differ from the build deps of the package in the archive. Does

Bug#862593: xarchiver: Adding files to .tar.xz deletes existing content

On May 20 2017, Markus Koschany <a...@debian.org> wrote: > On Fri, 19 May 2017 16:26:03 -0700 Nikolaus Rath <nikol...@rath.org> wrote: >> On May 20 2017, Markus Koschany <a...@debian.org> wrote: >> > Am 19.05.2017 um 23:23 schrieb Chris Lamb: &g

Bug#862593: xarchiver: Adding files to .tar.xz deletes existing content

On May 20 2017, Markus Koschany wrote: > Am 19.05.2017 um 23:23 schrieb Chris Lamb: >> tags 862593 + patch >> thanks >> >> The archive gets overwritten as the test to see whether it already exists >> (to determine whether to create a new one or simply add a new file) uses >> an

Bug#862593: xarchiver: Adding files to .tar.xz deletes existing content

> Steps to reproduce: > > $ echo foo > "Kieran Daycare Contract.pdf" > $ echo bar > "Kieran Daycare 2.pdf" > $ tar cJvf "Kieran Daycare Contract.pdf.tar.xz" "Kieran Daycare > Contract.pdf" > Kieran Daycare Contract.pdf > > $ xarchiver Kieran\ Daycare\ Contract.pdf.tar.xz > # Select Action->Add

Bug#862593: xarchiver: Adding files to .tar.xz deletes existing content

Package: xarchiver Version: 1:0.5.4-1+deb8u1 Severity: critical Justification: causes serious data loss As far as I can tell, using xarchiver to add additional files to a .tar.xz file will destroy the existing data. Steps to reproduce: $ echo foo > "Kieran Daycare Contract.pdf" $ echo bar >

Bug#856411: python-llfuse: Does not build with eatmydata

On Feb 28 2017, Nikolaus Rath <nikol...@rath.org> wrote: > On Feb 28 2017, Santiago Vila <sanv...@unex.es> wrote: >> On Tue, Feb 28, 2017 at 11:15:26AM -0800, Nikolaus Rath wrote: >> >>> It does build with libeatmydata - you just have to allow use of >>&g

Bug#856411: python-llfuse: Does not build with eatmydata

On Feb 28 2017, Santiago Vila <sanv...@unex.es> wrote: > On Tue, Feb 28, 2017 at 11:15:26AM -0800, Nikolaus Rath wrote: > >> It does build with libeatmydata - you just have to allow use of >> libeatmydata for setuid binaries by making >> /usr/lib/[t

Bug#851724: python-llfuse: FTBFS (failing tests)

On Jan 22 2017, Santiago Vila <sanv...@unex.es> wrote: > On Sat, Jan 21, 2017 at 04:12:28PM -0800, Nikolaus Rath wrote: > >> Are you able to reproduce this with Python 3.5? > > I don't know. I'm just building the package from source. > > The package currently build-

Bug#851724: python-llfuse: FTBFS (failing tests)

On Jan 17 2017, Santiago Vila wrote: > Exception in thread Thread-1 (most likely raised during interpreter shutdown): > Traceback (most recent call last): > File "/usr/lib/python2.7/threading.py", line 801, in __bootstrap_inner > File "/usr/lib/python2.7/threading.py",

Bug#850967: Clarify /usr/bin/foo should not be hardcoded even in upstream parts

>> Policy 6.1 says >> | Programs called from maintainer scripts should not normally have a >> | path prepended to them. >> >> Ie, programs that are on PATH should be found via the PATH rather than >> by hardcoding /usr/bin/foo or whatever. In general, I think we >> normally, at least in software

Bug#850052: Bug#850005: dgit push without dgit build-source

On Jan 10 2017, Ian Jackson <ijack...@chiark.greenend.org.uk> wrote: > Nikolaus Rath writes ("Re: Bug#850005: dgit push without dgit build-source"): >> On Jan 09 2017, Ian Jackson <ijack...@chiark.greenend.org.uk> wrote: >> > I just tried this with 2.13, u

  1   2   3   4   5   >