Bug#1005206: Split into separate C and C++ API packages

2022-02-13 Thread nurupo
It looks like starting with 4.0.0, C and C++ libraries got split in
separate codebases and their version numbers have decoupled -- the
latest msgpack-c release is 4.0.0, while C++ had 4.0.0, 4.0.1, 4.0.2,
4.0.3 and 4.1.0 releases[1].

[1] https://github.com/msgpack/msgpack-c/releases



Bug#1005206: Split into separate C and C++ API packages

2022-02-08 Thread nurupo
Package: libmsgpack-dev
Version: 3.3.0-4
Severity: wishlist

Dear Maintainer,

MessagePack provides separate C and C++ APIs. If all you want is the C
API, having to install around 150MiB of C++ boost libraries is rather
undesired. It would be nice if the package was split into two -- one
providing the C API and another for C++.



Bug#990023: The daily apt-listbugs.timer runs hourly instead

2021-06-17 Thread nurupo
Package: apt-listbugs
Version: 0.1.35

In my syslog I see apt-listbugs.service running every hour, claiming
it runs a *daily* job:

Jun 16 08:38:18 debian systemd[1]: Starting Daily apt-listbugs
preferences cleanup...
Jun 16 08:38:18 debian systemd[1]: apt-listbugs.service: Succeeded.
Jun 16 08:38:18 debian systemd[1]: Finished Daily apt-listbugs
preferences cleanup.
Jun 16 09:37:18 debian systemd[1]: Starting Daily apt-listbugs
preferences cleanup...
Jun 16 09:37:18 debian systemd[1]: apt-listbugs.service: Succeeded.
Jun 16 09:37:18 debian systemd[1]: Finished Daily apt-listbugs
preferences cleanup.
Jun 16 10:31:18 debian systemd[1]: Starting Daily apt-listbugs
preferences cleanup...
Jun 16 10:31:18 debian systemd[1]: apt-listbugs.service: Succeeded.
Jun 16 10:31:18 debian systemd[1]: Finished Daily apt-listbugs
preferences cleanup.
Jun 16 11:20:18 debian systemd[1]: Starting Daily apt-listbugs
preferences cleanup...
Jun 16 11:20:18 debian systemd[1]: apt-listbugs.service: Succeeded.
Jun 16 11:20:18 debian systemd[1]: Finished Daily apt-listbugs
preferences cleanup.

systemd says that apt-listbugs.service is triggered by
/lib/systemd/system/apt-listbugs.timer, which contains:

Description=Daily apt-listbugs preferences cleanup
OnCalendar=*-*-* *:20

*-*-* *:20 is a hourly calendar event according to the systemd documentation
https://www.freedesktop.org/software/systemd/man/systemd.time.html#Calendar%20Events



Bug#925941: nvenc not in ffmpeg

2020-05-29 Thread nurupo
Interestingly enough, ffmpeg package in Ubuntu 20.04 LTS has NVENC enabled:

>ffmpeg (7:4.2.2-1ubuntu1) focal; urgency=medium
>
>  * Build with external nv-codec-headers for NVENC accelerated video
>encoding. (LP: #1810649)
>- debian/control:
>  + Add B-D libffmpeg-nvenc-dev
>- debian/rules:
>  + Add --enable-nvenc for amd64 only
>
> -- Martin Wimpress   Sat, 07 Mar 2020 08:39:35 
> +

Looks like they have created libffmpeg-nvenc-dev package for this too.

Link to the referenced LP:
https://bugs.launchpad.net/ubuntu/+source/ffmpeg/+bug/1810649



Bug#958105: ferm: v2.5 broke @ipfilter(), resulting in deferred=ARRAY(0x55b7a9219368) errors

2020-04-18 Thread nurupo
Package: ferm
Version: 2.5-1.1
Severity: serious
Tags: upstream

Dear Maintainer,

Ferm got updated from v2.4 to v2.5, which brought a regression of @ipfilter()
function, when used, resulting in an error.

I believe the serious severity is warranted. The error makes it so that ferm
doesn't apply any rules, so if you rely on ferm to setup firewall rules, your
system would be unprotected. It might also break other software on the system
which rely on the rules to be present.

My particular issue is detailed in the upstream bug tracker
https://github.com/MaxKellermann/ferm/issues/71. It looks like it was already
fixed in master
https://github.com/MaxKellermann/ferm/commit/cea364a246f6988c6dc7f1603586f58c11b7dc28,
but the fix hasn't made it into any release yet.



Bug#947207: chromium: Video is garbled on twitch.tv, most other video sites

2020-01-03 Thread nurupo
Since the VAAPI patch is originally taken from Arch Linux, it might be
worth while to check if they had any issues with it on Chromium 79.
Looking at the comments and changes in
https://aur.archlinux.org/packages/chromium-vaapi it looks like they
did, and they have fixed those issues by updating the patches and
requiring a specially patched libva-vdpau-driver for Nvidia GPUs.



Bug#947207: chromium: Video is garbled on twitch.tv, most other video sites

2020-01-02 Thread nurupo
No point in reporting this bug upstream, they will not be able to
reproduce it as it's related to the hardware video acceleration patch
that Debian has recently started applying on top of the upstream
Chromium: 
https://salsa.debian.org/chromium-team/chromium/blob/c88b97a6dc183a6a7f8a05aee9e99957285a9371/debian/patches/fixes/vaapi.patch

As I can see, there are two possibilities here:
1. the patch got broken in Chromium 79, in which case it needs to be
updated and fixed
2. the issue is not with Chromium but the VAAPI library or the
hardware you use, in which case you could make Chromium use different
GPU (integrated graphics) or disable hardware video acceleration
altogether, either by passing some flag to Chromium (removing
--ignore-gpu-blacklist from /etc/chromium.d/default-flags might work
too) or rebuilding Chromium without the patch



Bug#940074: chromium: Enable vaapi

2019-11-20 Thread nurupo
The patch added in 78.0.3904.97-1 works.

There is an extra step you must do to enable it though. You need to
start Chromium with --ignore-gpu-blacklist flag. I have added it to my
/etc/chromium.d/default-flags.

Also, if your GPU doesn't support vp9 video decoding, you can use
h264ify or enhanced-h264ify browser extensions to force YouTube video
player to use h264 video streams, as it uses vp9 by default.



Bug#916410: closed by Michael Gilbert (Re: Bug#916410: chromium: Chromium 71.0.3578.80-1 fails to build from source due to missing subdirectories in third_party)

2018-12-13 Thread nurupo
Thanks for the reply, I have identified the issue.
I was trying to build it on a NTFS fs and it setup to set 0777 on all files.

On Thu, Dec 13, 2018 at 11:21 PM Debian Bug Tracking System <
ow...@bugs.debian.org> wrote:

> This is an automatic notification regarding your Bug report
> which was filed against the chromium package:
>
> #916410: chromium: Chromium 71.0.3578.80-1 fails to build from source due
> to missing subdirectories in third_party
>
> It has been closed by Michael Gilbert .
>
> 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 Michael Gilbert <
> mgilb...@debian.org> by
> replying to this email.
>
>
> --
> 916410: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=916410
> Debian Bug Tracking System
> Contact ow...@bugs.debian.org with problems
>
>
>
> -- Forwarded message --
> From: Michael Gilbert 
> To: 916410-cl...@bugs.debian.org
> Cc:
> Bcc:
> Date: Thu, 13 Dec 2018 23:21:28 -0500
> Subject: Re: Bug#916410: chromium: Chromium 71.0.3578.80-1 fails to build
> from source due to missing subdirectories in third_party
> On Thu, Dec 13, 2018 at 9:45 PM Maxim Biro wrote:
> > dh_clean: debian/clean is marked executable but does not appear to an
> > executable config.
> > dh_clean:
> > dh_clean: If debian/clean is intended to be an executable config file,
> please
> > ensure it can
> > dh_clean: be run as a stand-alone script/program (e.g. "./debian/clean")
> > dh_clean: Otherwise, please remove the executable bit from the file
> (e.g. chmod
> > -x "debian/clean")
> > dh_clean:
> > dh_clean: Please see "Executable debhelper config files" in debhelper(7)
> for
> > more information.
>
> The build log states exactly what is wrong and what needs to be done
> to fix it.  debian/clean needs to not be executable, otherwise
> debhelper will handle it differently.  It is not shipped that way.
>
> Best wishes,
> Mike
>
>
> -- Forwarded message --
> From: Maxim Biro 
> To: Debian Bug Tracking System 
> Cc:
> Bcc:
> Date: Thu, 13 Dec 2018 21:40:04 -0500
> Subject: chromium: Chromium 71.0.3578.80-1 fails to build from source due
> to missing subdirectories in third_party
> Package: chromium
> Version: 71.0.3578.80-1
> Severity: serious
> Justification: fails to build from source (but built successfully in the
> past)
>
> Trying to build Chromium off the source package, but it fails with
> Chromium's
> builds system unable to find third_party/{libvpx,opus,freetype} and so on.
>
> Here is what I do:
>
> sudo docker run --rm -it -v /tmp/chromium-pkgs:/build debian:sid /bin/bash
> echo "
> deb http://deb.debian.org/debian sid main contrib
> deb-src http://deb.debian.org/debian/ sid main contrib
> " > /etc/apt/sources.list
> apt-get update
> apt-get dist-upgrade -y
> apt-get install -y fakeroot devscripts build-essential
> apt-get build-dep -y chromium
> cd /build
> apt-get source -y chromium
> cd chromium-*
> debuild
>
> The error:
>
> # debuild
> dpkg-buildpackage -us -uc -ui
> dpkg-buildpackage: info: source package chromium
> dpkg-buildpackage: info: source version 71.0.3578.80-1
> dpkg-buildpackage: info: source distribution unstable
> dpkg-buildpackage: info: source changed by Michael Gilbert
> 
> dpkg-source --before-build .
> dpkg-buildpackage: info: host architecture amd64
> debian/rules clean
> dh clean
>   debian/rules override_dh_auto_clean
> make[1]: Entering directory '/build/chromium-71.0.3578.80'
> rm -rf out
> find . -name \*.pyc -execdir rm -f {} \;
> dh_auto_clean
> make[1]: Leaving directory '/build/chromium-71.0.3578.80'
>   dh_clean
> rm -f debian/debhelper-build-stamp
> rm -rf debian/.debhelper/
> /build/chromium-71.0.3578.80/debian/clean: 1:
> /build/chromium-71.0.3578.80/debian/clean: debian/files: not found
> /build/chromium-71.0.3578.80/debian/clean: 2:
> /build/chromium-71.0.3578.80/debian/clean: debian/scripts/mk-origtargz: not
> found
> /build/chromium-71.0.3578.80/debian/clean: 4:
> /build/chromium-71.0.3578.80/debian/clean: Makefile: not found
> /build/chromium-71.0.3578.80/debian/clean: 5:
> /build/chromium-71.0.3578.80/debian/clean: third_party/flot/*.js: not found
> /build/chromium-71.0.3578.80/debian/clean: 7:
> /build/chromium-71.0.3578.80/debian/clean:
> base/third_party/libevent/BUILD.gn:
> not found
> /build/chromium-71.0.3578.80/debian/clean: 8:
> /build/chromium-71.0.3578.80/debian/clean:
> build/secondary/third_party/libjpeg_turbo/BUILD.gn: not found
> /build/chromium-71.0.3578.80/debian/clean: 10:
> /build/chromium-71.0.3578.80/debian/clean: third_party/re2/BUILD.gn: not
> found
> /build/chromium-71.0.3578.80/debian/clean: 11:
> /build/chromium-71.0.3578.80/debian/clean: third_party/icu/BUILD.gn: not
> found
> /build/chromium-71.0.3578.80/debian/clean: 12:
> /build/chromium-71.0.3578.80/debian/clean: third_party/flac/BUILD.gn: not
> found
> third_party/zlib/BUILD.gn: 5: 

Bug#874706:

2017-12-10 Thread nurupo
Looks like this bug got resolved. Had the same issue before, but it got
fixed in the latest (4:17.08.3-1) version of the package.


Bug#874706:

2017-09-21 Thread nurupo
This is also happening for me. Whenever I start Gwenview, I get a message
box:

"There are two actions (Cut, Delete) that want to use the same shortcut
(Shift+Del). This is most probably a bug. Please report it in bugs.kde.org"

It's minor bug as clicking Ok in the message box takes you to Gwenview, but
it's annoying.

It looks like this was already reported and fixed upstream
https://bugs.kde.org/show_bug.cgi?id=347373