Bug#1028541: lvm2: LVM filters render servers unusable post bookworm upgrade

point release of Bookworm?. If you need support in testing I'm ready to provide that. Thanks and Regards, Vasudev Kamath -- System Information: Debian Release: trixie/sid APT prefers unstable APT policy: (500, 'unstable'), (1, 'experimental') Architecture: amd64 (x86_64) Kernel: Linux 6.7.12

Bug#1068753: live-build: Should not install raspi-firmware on x86_64

Roland Clobus writes: > Control: severity -1 normal > Control: tags -1 +pending > Control: tags 1065640 +pending > Control: merge -1 1065640 > > Hello Vasudev Kamath, > >> Built the live image for bookworm using live build (on bookworm as well as >> from uns

Bug#1068753: live-build: Should not install raspi-firmware on x86_64

my side. [1] https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1035382 [2] https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1065640 Thanks and Regards, Vasudev Kamath -- Package-specific info: -- System Information: Debian Release: trixie/sid APT prefers unstable APT policy: (

Bug#1032771: libzim7: Package name is wrong, should be 'libzim'

an extra 7 doesn’t hurt. People can search package by libzim and description should give information of same. Thanks and Regards -- Vasudev Kamath http://copyninja.info copyninja@{frndk.de|vasudev.homelinux.net}

Bug#1018818: bpfcc: FTBFS with libbpf 1.0.0

Control: fixed -1 0.25.0+ds-1 Hi Sudip, Thanks for the report new upstream release is fixing this issue and I've already uploaded new version and is building fine against all release architecture. So closing this bug. Thanks and Regards, Vasudev

Bug#1020559: libc6: After upgrading libc6 expr is crashing with "stack smashing detected"

Aurelien Jarno writes: > Hi, > > On 2022-09-26 09:45, Vasudev Kamath wrote: >> And post removing /usr/lib version of libc it seems to work fine and no >> crash is happening. >> >&g

Bug#1020559: libc6: After upgrading libc6 expr is crashing with "stack smashing detected"

Vasudev Kamath writes: > Post installation of usrmerge this output is changed > > └─(09:37:07 on master)──> ls -ld /lib/x86_64-linux-gnu/libc.so.6 > > 1 ↵ ──(Mon,Sep26

Bug#1020559: libc6: After upgrading libc6 expr is crashing with "stack smashing detected"

Vasudev Kamath writes: > > └─(09:09:40 on master)──> ls -ld /lib > > ──(Mon,Sep26)─┘ > drwxr-xr-x 9 root root 4096 Sep 23 14:37 /l

Bug#1020559: libc6: After upgrading libc6 expr is crashing with "stack smashing detected"

> > I have looked at the coredump you sent me: > > $ eu-unstrip -n --core > core.expr.1000.d5ff83e0fd69439497afd17511de3417.85280.166392358300 > 0x5604c0781000+0x1e000 > b919757cbc30fbb64b14498222499d972fd80acd@0x5604c0781368 . - /usr/bin/expr > 0x7fbfabc0+0x201000 >

Bug#1020559: libc6: After upgrading libc6 expr is crashing with "stack smashing detected"

> Hello Vasudev, > ok, reverting back would explain reportbug using version 2.34-8. > > But was this core taken at a time where all libc packages > should have been at 2.35-1 ? > Then I don't understand that "Module" line, > which shows the build-id from 2.34-8. Ah sorry I did coredumpctl

Bug#1020559: libc6: After upgrading libc6 expr is crashing with "stack smashing detected"

Sep-2022, at 03:21, Aurelien Jarno wrote: > > Hi, > >> On 2022-09-23 21:28, Bernhard Übelacker wrote: >>> On Fri, 23 Sep 2022 14:45:07 +0530 Vasudev Kamath >>> wrote: >>> Package: libc6 >>> Version: 2.34-8 >> >>> I upgraded libc6

Bug#1020559: libc6: After upgrading libc6 expr is crashing with "stack smashing detected"

Package: libc6 Version: 2.34-8 Severity: important Dear Maintainer, *** Reporter, please consider answering these questions, where appropriate *** * What led up to the situation? I upgraded libc6 to latest released 2.35-1 * What exactly did you do (or not do) that was effective (or

Bug#1019248: linux: Enable EDAC module for Intel Icelake (10nm processors)

Source: linux Version: 5.10.127-1 Severity: important Dear Maintainer, Recently when testing the newer Icelake servers in our DC we noticed that EDAC module is not available in Debian for Intel Icelake (10nm processor). This is needed for utilities like rasdaemon to work properly on new

Bug#995289: foolscap: ready for upload

Hi Andrius, Andrius Merkys writes: > Hello, > > I have removed unneeded files from python3-foolscap binary package. > Furthermore, there was an issue with building package with > git-buildpackage, which I solved by updating the certificates used for > tests. > > The package is ready for the

Bug#987295: closed by Vasudev Kamath (Re: profile-bpf: 3 warnings generated)

Jacobo Nájera writes: > Hi, > > Thanks Vasudev > > I tried on a fresh install with Bullseye: > > > Sampling at 49 Hertz of all threads by user + kernel stack... Hit Ctrl-C > to end. > In file included from :2: > In file included from /virtual/include/bcc/bpf.h:12: > In file included from

Bug#996961: bpfcc-tools: biosnoop fails to print the SIZE field correctly on bullseye

Control: fixed -1 0.24.0+ds-1 Hi Rich, Sorry for the delayed response. This is no longer an issue in latest version of bpfcc-tools. Hence closing the bug. Thanks and Regards, Vasudev

Bug#987295: profile-bpf: 3 warnings generated

Control: fixed -1 0.24.0+ds-1 Hi Jacobo, Sorry for delayed response. I checked with latest version of bpfcc-tools and this is no longer an issue. So closing this bug. Thanks and Regards, Vasudev

Bug#1010346: linux-image-cloud-amd64: Enable CONFIG_FB_EFI=y in Buster Cloud Kernel

Package: linux-image-cloud-amd64 Version: 4.19+105+deb10u15 Severity: important Dear Maintainer, Booting a KVM based VM with UEFI enabled using Buster image with cloud kernel will have a non working VNC console. Console seems to be frozen on debugging we figured out that its because buster

Bug#976960: systemd: Please package systemd-userdbd and systemd-homed

Hi Michael, > I still fail to see the use-case for homed, tbh and the current > implementation still requires quite a few hacks (see the fosdem 2020 > talk of Lennart and the problems e.g. with SSH keys). > Atm this appears more like a tech-preview/demo and I don't feel > comfortable yet

Bug#1002291: bpfcc: Fails to build with libbpf/0.6.1-1

Sudip Mukherjee writes: > On Tue, Feb 22, 2022 at 4:12 AM Vasudev Kamath wrote: >> >> Sudip Mukherjee writes: >> >> > You are trying to build 0.24.0+ds and I am rebuilding 0.22.0+ds-2 to test. >> > :) >> > >> > Can you rebuild 0.22.

Bug#1002291: bpfcc: Fails to build with libbpf/0.6.1-1

Sudip Mukherjee writes: > You are trying to build 0.24.0+ds and I am rebuilding 0.22.0+ds-2 to test. :) > > Can you rebuild 0.22.0+ds-2 and verify. Err yes. It works with 0.22.0. I was preparing 0.23.0 and then 0.24.0. Both of which fails as of now. Not sure what should be done. Cheers,

Bug#1002291: bpfcc: Fails to build with libbpf/0.6.1-1

Sudip Mukherjee writes: > I have now uploaded libbpf/0.7.0 to experimental, can you please try > building bpfcc and let me know if it works for you. > I'm ending up getting different error now related to deprecation. >/<>/src/cc/bcc_btf.cc:178:33: error: invalid application of >‘sizeof’ to

Bug#1002291: bpfcc: Fails to build with libbpf/0.6.1-1

Hi Sudip, Sudip Mukherjee writes: > > Reported error: > In file included from /<>/src/cc/bcc_libbpf_inc.h:5, > from > /<>/src/cc/frontends/clang/b_frontend_action.cc:37: > /usr/include/bpf/btf.h: In function ‘bool btf_is_mod(const btf_type*)’: > /usr/include/bpf/btf.h:463:24:

Bug#995352: ITP: tahoe-lafs -- Secure distributed file store

Package: wnpp Severity: wishlist Owner: Madhu Adav X-Debbugs-Cc: debian-de...@lists.debian.org * Package name: tahoe-lafs Version : 1.16.0rc0 Upstream Author : The Tahoe-LAFS Software Foundation * URL : http://tahoe-lafs.readthedocs.io/en/latest/ * License :

Bug#995289: ITP: foolscap -- object-capability-based RPC system for Twisted Python

Package: wnpp Severity: wishlist Owner: Vasudev Kamath X-Debbugs-Cc: debian-de...@lists.debian.org * Package name: foolscap Version : 21.7.0 Upstream Author : Brian Warner * URL : https://github.com/warner/foolscap/ * License : MIT Programming Lang: Python

Bug#994914: python-autobahn: Please package new upstream release of autobahn

Source: python-autobahn Severity: wishlist Dear Maintainer, We are working on to reintroduce tahoe-lafs to Debian since a new version with python3 support has been release. New version need autobahn >= 19.5.2. Can you please consider updating the package to latest upstream release so we will

Bug#994913: python-eliot: Please package eliot version 1.13.0

Source: python-eliot Severity: wishlist Dear Maintainer, We are working on reintroducing the tahoe-lafs back to Debian now that it supports python3. But newer version of tahoe-lafs needs eliot to be updated to 1.13.0. Here is the comment from the upstream requirements file # On Python 3,

Bug#993856: [Pkg-libvirt-maintainers] Bug#993856: libvirt-daemon-system: vfio device passthrough fails with device pools due to apparmor profile

Hi Again, Vasudev Kamath writes: > > And the network configuration in libvirt domain looks like below > > > > > >function='0x0'/> > > > When I start the domain even though domain starts fine VF pass through does >

Bug#993856: libvirt-daemon-system: vfio device passthrough fails with device pools due to apparmor profile

Package: libvirt-daemon-system Version: 7.6.0-1 Severity: important Dear Maintainer, Possibly related bug [1]. Issue is similar to what is explained in this bug but is not addressed by the fix which is already present in src:libvirt 7.6 version. PS: Though I reporting from unstable machine

Bug#978727: bpfcc: Provide separate package for libbpf-tools?

Hello guys, Sorry for delaying uploading this version. So I started working on the libbpf-tools but I'm facing weird error when trying to build the package in sbuild. > /usr/sbin/bpftool gen skeleton .output/biolatency.bpf.o > > .output/biolatency.skel.h > libbpf: failed to find BTF for

Bug#892058: Your Debian key is expiring

Felix Lechner writes: > > Please keep in mind that the Debian folks in charge of the keyring > update it only once a month. That usually happens on the 24th of each > month. It it just a few days away. > > If you like this service, please leave a favorable comment here [2]. > Thank you! Thanks

Bug#978727: bpfcc: Provide separate package for libbpf-tools?

Salvatore Bonaccorso writes: > Hi Mika, > > On Sat, Feb 13, 2021 at 09:42:53AM +0100, Michael Prokop wrote: >> * Michael Prokop [Wed Dec 30, 2020 at 11:11:32PM +0100]: >> >> > With the ongoing efforts around BTF and CO-RE (see >> >

Bug#980296: bpfcc-tools: ${lang}gc-bpfcc and ${lang}stat-bpfcc do not work properly

Vasudev Kamath writes: > Ritesh Raj Sarraf writes: > >> Hi Vasudev, >> >> On Mon, 2021-01-18 at 09:27 +0530, Vasudev Kamath wrote: >>> Ritesh Raj Sarraf writes: >>> >>> > I had fixed this some time ago. Looks like the recent n

Bug#980296: bpfcc-tools: ${lang}gc-bpfcc and ${lang}stat-bpfcc do not work properly

Ritesh Raj Sarraf writes: > Hi Vasudev, > > On Mon, 2021-01-18 at 09:27 +0530, Vasudev Kamath wrote: >> Ritesh Raj Sarraf writes: >> >> > I had fixed this some time ago. Looks like the recent new updates >> > needed a >> > new adaptation. Thanks

Bug#980296: bpfcc-tools: ${lang}gc-bpfcc and ${lang}stat-bpfcc do not work properly

Hi Ritesh, Ritesh Raj Sarraf writes: > I had fixed this some time ago. Looks like the recent new updates needed a > new adaptation. Thanks for reporting this bug > I had fixed a couple of paths before but this one I did not find out. If you are not considering fixing this I will go ahead and

Bug#957037: biboumi: ftbfs with GCC-10

Michel Le Bihan writes: > Hello, > > I opened a merge request, but merging all branches into your repo > might cause issues in the upstream branch in the future due to the > merge commits. Instead, it will be best to pull all branches from my > repo into branches of your repo, but without adding

Bug#979016: libbpfcc: vendors libbpf

Luca Boccassi writes: > Package: libbpfcc > Version: 0.8.0-4 > Severity: important > Tags: bullseye patch > > Dear Maintainer(s), > > libbpfcc vendors and statically links against libbpf, which is now > available in the Debian archive as a fully maintained shared library. > > This is a problem

Bug#957037: biboumi: ftbfs with GCC-10

Michel Le Bihan writes: > Le mardi 22 décembre 2020 à 17:35 +0530, Vasudev Kamath a écrit : >> Jonas Smedegaard writes: >> >> > Quoting Michel Le Bihan (2020-12-20 17:15:29) >> > > Le dimanche 20 décembre 2020 à 16:50 +0100, Jonas Smedegaard a >> &g

Bug#957037: biboumi: ftbfs with GCC-10

Jonas Smedegaard writes: > Quoting Michel Le Bihan (2020-12-20 17:15:29) >> Le dimanche 20 décembre 2020 à 16:50 +0100, Jonas Smedegaard a écrit : >> > Quoting Michel Le Bihan (2020-12-20 16:06:27) >> > > A quick summary of the differences between both repos: >> > >> > Thanks, that is no doubt

Bug#957037: biboumi: ftbfs with GCC-10

Hi Alberto, > I have checked that current upstream (9.0) builds flawlessly, and made > my release available at https://salsa.debian.org/aluaces-guest/biboumi > . That is great. > Can I be sponsored so we can upload to at least experimental? Sure, please raise a merge request against biboumi

Bug#976596: bpfcc FTBFS: symbol differences

Hi Adrian, Adrian Bunk writes: > Source: bpfcc > Version: 0.17.0-7 > Severity: serious > Tags: ftbfs > > This might be due to the LLVM 9 -> 11 transition, > or for other reasons. > > The general problem of shipping symbols files for C++ code > is discussed at

Bug#949863: #949863: please enable CONFIG_NET_SWITCHDEV

Vasudev Kamath writes: > Salvatore Bonaccorso writes: > >> Hi >> >> On Tue, Sep 15, 2020 at 02:00:51PM +0530, Vasudev Kamath wrote: >>> Tzafrir Cohen writes: >>> >>> > Hi, >>> > >>> > A patch for fix of the reg

Bug#949863: #949863: please enable CONFIG_NET_SWITCHDEV

Salvatore Bonaccorso writes: > Hi > > On Tue, Sep 15, 2020 at 02:00:51PM +0530, Vasudev Kamath wrote: >> Tzafrir Cohen writes: >> >> > Hi, >> > >> > A patch for fix of the regression is in 4.19.145 (commit >> > 044be307e550b45

Bug#942290: libbpfcc: libbcc_bpf.so: needs to link with -lelf

Ritesh Raj Sarraf writes: > If you have some spare cycles for bpfcc, it could use your help. > I'm bit confused here, is this the upstream issue?. Or I need to patch the upstream CMake to make sure these linker options are passed?. Some input appreciated. Cheers, Vasudev

Bug#949863: #949863: please enable CONFIG_NET_SWITCHDEV

Tzafrir Cohen writes: > Hi, > > A patch for fix of the regression is in 4.19.145 (commit > 044be307e550b4532960eadabfb6942de96751f0  "net/mlx5e: Don't support phys > switch id if not in switchdev mode"). > > Please enable CONFIG_NET_SWITCHDEV once this is merged to the Buster > kernel tree. >

Bug#970350: linux: Enable CONFIG_NET_SWITCHDEV in Buster kernel

Source: linux Version: 4.19.132-1 Severity: normal Dear Maintainer, The regression issue which I reported in [1] has been fixed by Mellanox upstream [2] and is now part of linux-4.19.145-1 [3]. So can we now enable the CONFIG_NET_SWITCHDEV support in Debian Buster? [1]

Bug#965263: debian-installer: Script exected in preseed/late_command on dual CPU socket system sees only Single CPU socket

Vasudev Kamath writes: > Geert Stappers writes: > >> On Sat, Jul 18, 2020 at 06:19:55PM +0530, Vasudev Kamath wrote: >>> >>> Please let me know if you need more information. >>> >> >> Both kernel versions > > We mirror Debian r

Bug#966229: ITP: protocol -- a simple command line tool for displaying standard network protocol headers

Ben Hutchings writes: > On Sat, 2020-07-25 at 08:36 +0530, Vasudev Kamath wrote: >> Package: wnpp >> Severity: wishlist >> Owner: Vasudev Kamath >> >> * Package name: protocol > > I think this name is too generic. Any suggestions?. I'm bad with choos

Bug#966229: ITP: protocol -- a simple command line tool for displaying standard network protocol headers

Package: wnpp Severity: wishlist Owner: Vasudev Kamath * Package name: protocol Version : 0.1 Upstream Author : Luis MartinGarcia * URL : http://www.luismg.com/protocol/ * License : GPL-3.0 Programming Lang: Python Description : a simple command line

Bug#965263: debian-installer: Script exected in preseed/late_command on dual CPU socket system sees only Single CPU socket

Geert Stappers writes: > On Sat, Jul 18, 2020 at 06:19:55PM +0530, Vasudev Kamath wrote: >> >> Please let me know if you need more information. >> > > Both kernel versions We mirror Debian repository on daily basis and found this bug with latest installer released w

Bug#965263: debian-installer: Script exected in preseed/late_command on dual CPU socket system sees only Single CPU socket

Package: debian-installer Severity: normal Dear Maintainer, I recently moved some code to preseed/late_command script to do the CPU pinning for host machine. Script snippet looks something like below NODE_CPUS=2 for node in /sys/devices/system/node/node[0-9];

Bug#949863: [Vasudev Kamath] Re: Bug#949863: Info received (#949863: please enable CONFIG_NET_SWITCHDEV)

Sending it to BTS to track in bug log. --- Begin Message --- [Sending reply to bug so we can have a record of discussion] [Please keep Ashruth and my colleague in CC while replying] Tzafrir Cohen writes: [snip] >> >> I don't think we should make a config change that hurts users of stock >>

Bug#962791: pristine-tar: pristine-xz failed to reproduce build of ../libvirt_6.4.0.orig.tar.xz

Package: pristine-tar Version: 1.47 Severity: normal Dear Maintainer, Unable to import the new version of libvirt [1]. Seeing following message bp:info: Importing '../libvirt_6.4.0.orig.tar.xz' to branch 'upstream/latest'... gbp:info: Source package is libvirt gbp:info: Upstream version is

Bug#954290: kexec doesn't do reboots on systemd install?

Khalid Aziz writes: > > kdump relies upon kexec but it is configured separately by kdump-tools. > kexec works just fine with systemd. It is just the wording of configure > message in kexec-tools package that is misleading and needs fixing. Yes that was part of my confusion too. Was wondering it

Bug#954290: kexec doesn't do reboots on systemd install?

Vasudev Kamath writes: > In our setup of Debian 9 we noticed many kernel panic which never crash > dumped so was searching if there is something wrong in our setup and > came across this bug. While looking at systemd I noticed there is a > service called systemd-kexec.service which

Bug#954290: kexec doesn't do reboots on systemd install?

In our setup of Debian 9 we noticed many kernel panic which never crash dumped so was searching if there is something wrong in our setup and came across this bug. While looking at systemd I noticed there is a service called systemd-kexec.service which is disabled by default. Is this needs to be

Bug#961197: debmirror does not clean up temporary files created under /tmp

Package: debmirror Version: 1:2.33 Severity: normal Dear Maintainer, I noticed this behavior initially on the stretch-backports version, but later when I tried the same command on my machine the behavior is reproducible. Below is sample command I used for testing debmirror

Bug#937413: pycryptopp: Python2 removal in sid/bullseye

Hi Moritz, Moritz Mühlenhoff writes: > > Hi Vasudev, > > https://github.com/tahoe-lafs/pycryptopp/issues/36#issuecomment-504130020 > states: > > | The Tahoe-LAFS project has decided it is not interested in porting > | pycryptopp to Python 3. Instead, Tahoe-LAFS is switching to the > |

Bug#959844: RM: pycryptopp -- ROM; upstream no longer has intent to support python 3

Package: ftp.debian.org Severity: normal As mentioned in [1] upstream has moved from pycryptopp to cryptography library for tahoe-lafs and tahoe was the only dependency using this package. Since there is no intent by upstream to provide py3 support for this library I'm requesting its removal

Bug#959691: RM: tahoe-lafs -- ROM; python2 only no python3 support is available from upstream

Package: ftp.debian.org Severity: normal Requesting the removal of this package as suggested in [1]. Currently there is no support of Python3 and package is python2 only. Upstream is working on Python3 package but there is no clear ETA yet on when it will be ready. I will reintroduce the

Bug#949863: Info received (#949863: please enable CONFIG_NET_SWITCHDEV)

Ben Hutchings writes: > On Mon, 9 Mar 2020 13:58:38 +0200 Tzafrir Cohen wrote: >> Hi, >> >> > Also: please consider this change for inclusion in a stable update, if >> > possible. >> >> I see that this was merged into git. Thanks. What are the chances of >> this fix getting included into

Bug#951047: udev/rules.d/50-udev-default.rules: Invalid GROUP operation

Michael Biebl writes: > Am 23.03.20 um 05:02 schrieb Vasudev Kamath: >> Michael Biebl writes: >> >>>> >>>> >>>> I see above message in syslog as well. Also this is a fresh Buster >>>> installation. If you want any more informat

Bug#951047: udev/rules.d/50-udev-default.rules: Invalid GROUP operation

Control: reopen -1 I also see these messages in the startup and it seems to be originating from initramfs. Mar 20 15:41:59 fk-cloud-d3a-ms-1375774 kernel: <1051>[7.441386] systemd-udevd[585]: /usr/lib/udev/rules.d/50-udev-default.rules:18: Invalid GROUP operation Mar 20 15:41:59

Bug#948404: glances crashes on startup

Hi Daniel, Daniel Echeverry writes: > On Wed, Jan 08, 2020 at 11:25:05PM -0500, Daniel Echeverry wrote: >> tags 948404 + moreinfo unreproducible >> thanks >> >> Hi! >> >> Thanks for your report! Unfortunately I can't reproduce this bug, I install >> glances via ap-get install and works

Bug#948404: glances crashes on startup

Package: glances Version: 3.1.1-1 Severity: grave Justification: Renders glances use less Dear Maintainer, I installed glances from Debian repository and when trying to launch It crashes with following stack trace Error while initializing the ip plugin ('NoneType' object has no attribute

Bug#938887: zfec: diff for NMU version 1.5.2-2.1

Sandro Tosi writes: > > I've prepared an NMU for zfec (versioned as 1.5.2-2.1). The diff > is attached to this message. Thanks Sandro. I've merged your patch into Git. Cheers, Vasudev

Bug#944703: nvidia-graphics-drivers: Vcs-* fields points to non existent location for nvidia-graphics-driver source package

Control: merge -1 903302 Looks like there was already a bug for same purpose and already answered on why its not publicly available. For now I will work using the source downloaded from Debian archive. Cheers,

Bug#944703: nvidia-graphics-drivers: Vcs-* fields points to non existent location for nvidia-graphics-driver source package

Source: nvidia-graphics-drivers Severity: normal Dear Maintainer, Vcs-* fields for nvidia-graphics-drivers points to https://salsa.debian.org/nvidia-team/nvidia-graphics-drivers but going to this link leads to 404 error. I'm unable to checkout the source using debcheckout Can some one point me

Bug#944111: bpftrace fails with message "Creation of the required BPF maps has failed."

Vincent Bernat writes: > ❦ 4 novembre 2019 18:55 +0530, Vasudeva Sathish Kamath > : Copying Ritesh who is also the maintainer of the libbpfcc > > I get the same results. Also, it doesn't work with a 5.2 kernel either. > Using "strace -febpf", I see the following: > > bpf(BPF_MAP_CREATE,

Bug#932781: Bug#932428, Bug#932767, Bug#932781: gnome-shell crashes involving monitor changes

nnector for the external monitor. > > On Tue, 23 Jul 2019 at 10:36:59 +0530, Vasudev Kamath wrote: >> Closing laptop lid normally puts laptop sleep and I get back my session on >> reopen. But after recent update >> I see that I get logged out and closer inspection rev

Bug#932781: gnome-shell crashed on laptop lid close

Control: severity -1 serious Increasing severity to serious as this is hampering day to day productivity. Even connecting secondary display causes GNOME shell to crash with same crash dump as before. Cheers, Vasudev

Bug#932781: gnome-shell crashed on laptop lid close

Simon McVittie writes: > Control: tags -1 + moreinfo > > On Tue, 23 Jul 2019 at 10:36:59 +0530, Vasudev Kamath wrote: >> Closing laptop lid normally puts laptop sleep and I get back my session on >> reopen. But after recent update >> I see that I get logged out and

Bug#932781: gnome-shell crashed on laptop lid close

Simon McVittie writes: > Control: tags -1 + moreinfo > > On Tue, 23 Jul 2019 at 10:36:59 +0530, Vasudev Kamath wrote: >> Closing laptop lid normally puts laptop sleep and I get back my session on >> reopen. But after recent update >> I see that I get logged out and

Bug#932781: gnome-shell crashed on laptop lid close

Package: gnome-shell Version: 3.30.2-9 Severity: important Dear Maintainer, Closing laptop lid normally puts laptop sleep and I get back my session on reopen. But after recent update I see that I get logged out and closer inspection revealed that gnome-shell is crashing with following error [

Bug#921094: [Pkg-fonts-devel] Bug#921094: fonts-fantasque-sans: Single quote/apostrophe is not clearly readable

Cyril Augier writes: > Package: fonts-fantasque-sans > Version: 1.7.1~dfsg-1 > Severity: important > > Hi ! > > According to the issues on Github, the problem is solved in the higher > versions. > > I installed the latest version from GitHub and it works perfectly. Which version did you check

Bug#774274: fontforge: please use SOURCE_DATE_EPOCH for reproducible font modification time

Theppitak Karoonboonyanan writes: > Package: fontforge > Version: 1:20170731~dfsg-1 > Followup-For: Bug #774274 > > Dear Maintainer, > > This bug still exists for Type 1 font generation, which causes my package > fonts-sipa-arundina to be unreproducible. > >

Bug#920708: fonts-b612 segfault and other problems with ufo2otf

Control: tag -1 +moreinfo Gürkan Myczko writes: > Package: python-fontforge > Version: 1:20170731~dfsg-1 > Severity: normal > > Forwarding this to fontforge/python-fontforge: > > Hello, > > I can indeed reproduce the crash. > It looks a bug in libfontforge2. (ufo2otf simply calls

Bug#917048: cargo: Please drop patch to disable incremental builds on sparc64

John Paul Adrian Glaubitz writes: > Hi! > > On 12/22/18 12:15 AM, John Paul Adrian Glaubitz wrote: >> While upstream hasn't fixed the bug yet, I have provided a temporary >> fix for the bug in #917000 [2]. Once this bug has been fixed, incremental >> builds work fine on sparc64 and the patch to

Bug#920414: tahoe-lafs: Please package new upstream version 1.13.0

Hi, New version needs magic-wormhole lib in py2 but currently it's py3 package. I filed a bug but maintainer said he won't be able to do it. If some one can package python-magic-wormhole then I can package new version. Thanks and Regards On 25 January 2019 2:51:30 PM IST, Elena ``of

Bug#912062: [Pkg-fonts-devel] Bug#912062: fontforge: segfaults when opening some UFO fonts

Control: forwarded -1 https://github.com/fontforge/fontforge/pull/3358 Control: tag -1 +upstream Hi Thibaut, I've forwarded the patch to upstream. If they say it looks good I will merge the same and release in next update. Thanks for the patch. Cheers, Vasudev

Bug#908961: cargo: debian/rules overrides DEB_BUILD_PROFILES

Hi Helmut, Helmut Grohne writes: > Source: cargo > Version: 0.29.0-1 > > debian/rules sets DEB_BUILD_PROFILES. The variable is not meant to be > changed during build. Changing it can lead to inconsistency between > tools run by debian/rules and tools run outside debian/rules, but it > also

Bug#906539: magic-wormhole: Please provide python-magic-wormhole library its needed by new version of tahoe-lafs

Antoine Beaupré writes: > I'm happy to accept patches to ship a Python2 debian package of the > wormhole library, but I do not have time to make the change myself. NMU, > patches welcome. I will see what I can do. > > I would also strongly recommend pushing tahoe-lafs to port to Py3 > already.

Bug#906539: magic-wormhole: Please provide python-magic-wormhole library its needed by new version of tahoe-lafs

Source: magic-wormhole Severity: important Dear Maintainer, I was packaging new version of tahoe-lafs and noticed it won't launch even after adding magic-wormhole to dependency. Then I noticed magic-wormhole is using python3 and tahoe-lafs still does not support python3. I propose to provide

Bug#897732: patches

Vasudev Kamath writes: > Hi Adrian, > > Adrian Bunk writes: >> >> Hi Vasudev, >> >> are there any remaining problems with >> https://salsa.debian.org/debian/ctpp2/merge_requests/1 >> ? > > I've merged the changes. I had requested changes

Bug#904803: pugixml: please update to new version 1.9

Gianfranco Costamagna writes: > > * Non-maintainer upload (Closes: #-1) > > * Move vcs to salsa.d.o > > * Drop duplicated "section" libs > > * Bump std-version to 4.1.5, no changes required > > * New upstream release > > * Patch refresh > > * Update copyright file > > > let me know if I can push

Bug#899124: fa-solid-900.ttf symlinked as fontawesome-webfont.ttf

Alexis Murzeau writes: > Hi, > > Le 27/06/2018 à 00:21, Alexis Murzeau a écrit : >> Le 26/06/2018 à 04:13, vasudev-debian a écrit : >>> I'll have a look. if possible clone from team repo and raise a pr on it. >>> >> >> I've created 3 PR at [0], one for each branch (in this order: upstream, >>

Bug#899124: fa-solid-900.ttf symlinked as fontawesome-webfont.ttf

Hi Alexis, Thomas, First of all I apologise for not replying in time. I'm bit occupied by family work so not getting enough time to deal with package. Alexis Murzeau writes: >> >> I also would like to highlight that what you're describing here is the >> workflow of a transition, which is what

Bug#884440: zimlib: Please package new 3.1.0 upstream version

dea. [1] https://www.eyrie.org/~eagle/journal/2012-01/008.html > > This is needed so I can upgrade libkiwix and start packaging the rest of > the kiwix suite. Understand.. That's why I'm asking take over the maintenance -- Vasudev Kamath http://copyninja.info

Bug#899124: fa-solid-900.ttf symlinked as fontawesome-webfont.ttf

Hi Thomas, I read through and prepared a version to experimental which symlinks fa-solid-900.ttf as fontawesome-webfont.ttf. I've uploaded it to experimental, can you please check if this helps?. @Others Please let me know if this new version in experimental with suggestion from Thomas

Bug#899124: fonts-font-awesome: completely breaks web applications, with no notice

Pierre-Elliott Bécue writes: > > Hi, > > I'm maintaining HyperKitty, and it relies on fontawesome-webfont.ttf and > FontAwesome.otf from the v4 version. To avoid shipping the files with the > package, I linked them from the debian's one in d/rules. (see [1]) > > Do we agree that

Bug#899124: fonts-font-awesome: completely breaks web applications, with no notice

; On Sun, May 20, 2018 at 10:32:38PM +0530, Vasudev Kamath wrote: >> > Antonio Terceiro <terce...@debian.org> writes: >> > > 2) revert the changes in fonts-font-awesome in unstable, upload the >> > > new release to experimental, and give people a few months to ada

Bug#899124: fonts-font-awesome: completely breaks web applications, with no notice

Hi Antonio, Antonio Terceiro writes: > Package: fonts-font-awesome > Version: 5.0.10-1 > Severity: grave > > Font-Awesome version completely changed everything, and any web > applications that use it are now broken unless they go through some > manual intervention. > >

Bug#898501: Broken symlinks

Hi all, First of all sorry for mess I created. I made a silly mistake of not updating the links file properly before upload. I'm rectifying it now and will upload the fixed version ASAP. Second I noted that from the bug report by Antonio that the usage patterns have changed a lot between 4 and

Bug#895300: cargo: Please disable incremental-by-default on sparc64

John Paul Adrian Glaubitz writes: > Hi! > > The attached patch disables incremental builds on sparc64 and resolves > the issue for me. It would be good if the patch could be applied for > the time being until we have investigated what causes the issues with >

Bug#888811: dnscrypt-proxy: Please package newer upstream release

Package: dnscrypt-proxy Version: 1.9.5-1+b1 Followup-For: Bug #11 Dear Maintainer, There are lot of new release of the package and we are still in old version. Can you please consider updating the package?. If you are busy can you make the package team maintained so interested party can

Bug#892370: Aerial Bold chosen when it should not be

Hi Wouter, Wouter Verhelst writes: > Package: fonts-arkpandora > Version: 2.04-1 > Severity: normal > > Hi, > > fonts-arkpandora contains a number of fonts, amongst which Aerial and > Aerial Bold. > > For some reason, on my system firefox chooses Aerial Bold when it should >

Bug#891855: fonts-monoid: installs no less than 4000 font files!

Fabian Greffrath <fab...@debian.org> writes: > Hi Vasudev, > > Am Sonntag, den 04.03.2018, 14:59 +0530 schrieb Vasudev Kamath: >> Feel free to suggest and join in the maintenance work :-). It was long >> pending and recently I noticed that it could be already built si

Bug#891855: fonts-monoid: installs no less than 4000 font files!

Hi Fabian, Fabian Greffrath writes: > Am Donnerstag, den 01.03.2018, 17:36 +0100 schrieb Fabian Greffrath: >> etc. Another alternative would be to split the packages up by groups >> of variants, or whatever. > > I think I have a better idea: In e.g. the Libreoffice font

Bug#890211: [Pkg-fonts-devel] Bug#890211: Bug#890211: fonts-noto-hinted: Certain font characters crash Emacs 25

Jonas Smedegaard writes: > Hi Chiraag, > > Quoting Chiraag Nataraj (2018-02-12 02:00:06) >> I went to open mpc in Emacs, and my artists (and song titles) are in >> multiple languages, including Kannada (the font for which I found this >> problem). A very specific character (ಕು)

Bug#888413: lintian: Don't consider README file under debian/patches as patch file

Chris Lamb writes: > tags 888413 + pending > thanks > > Hi Vasudev, > >> Please do not consider README file under debian/patches folder as >> a patch file. > > Thanks for the report! This was already fixed a few days ago in Git > here: > > >

  1   2   3   4   5   6   >