Bug#1061743: Gramps in Debian

2024-05-27 Thread Debian GNU|Linux

On 5/26/24 23:56, Dr. Tobias Quathamer wrote:


The package builds on my machine, although I had to disable a single 
test for now. You'll find it in the newly created patch. Maybe you have 
an idea what's causing the failure, so it can be fixed properly.


https://gramps-project.org/bugs/view.php?id=13305

i think this is just a wrong assumption on the side of the upstream 
testsuite (shadowed by their workflows).


upstream evades this by ensuring that "~/.gramps/" is there before 
running the tests (both in their GitHub action, and in their debian/ 
packaging).


i think that for now the proper resolution for the problem is to simply 
do a `mkdir "$CURDIR)/build/.gramps` before running the tests.

(which i've now pushed to the 'experimental' branch)

as a sidenote: the testsuite now creates a *very* verbose buildlog (~420MB).
is that ok?

gf,madsr
IOhannes


OpenPGP_0xB65019C47F7A36F8.asc
Description: OpenPGP public key


OpenPGP_signature.asc
Description: OpenPGP digital signature


Bug#1070793: security.debian.org: Hibernate does not work from KDE Plasma menu. System does not power off.

2024-05-09 Thread Hibernation does not work after update to Debian GNU/Linux, with Linux 5.10.0-29-amd64
Package: security.debian.org
Severity: normal
X-Debbugs-Cc: martin@rod.cz

Dear Maintainer,

*** Reporter, please consider answering these questions, where appropriate ***

   * What led up to the situation?
   * What exactly did you do (or not do) that was effective (or
 ineffective)?
   * What was the outcome of this action?
   * What outcome did you expect instead?

*** End of the template - remove these template lines ***



Bug#1058934: apt install ./foo.deb re-downloads the package

2023-12-18 Thread Debian GNU|Linux

On 12/18/23 15:38, Stuart Prescott wrote:


This is a regression since bookworm.




note that i am experiencing this on a bookworm system.

while i don't use backports (so 'apt' should be indeed the one that 
comes with bookworm), i do have some third-party repository enabled 
(gitlab).


i did notice the problem when using 'apt-get' (rather than 'apt') to 
install a local .deb file (which happens to be >1GB, so the re-download 
is quite noticeable):


```sh
apt-get install /dev/shm/gitlab-ce_16.6.2-ce.0_amd64.deb
```

(that's just for completeness sake; i'm full aware that i'm on my own 
when enabling 3rd party repositories; but given that stuart was able to 
reproduce this on a (presumably) pristine system, it might help that 
others experience this before trixie)


gmasdr
IOhannes


OpenPGP_0xB65019C47F7A36F8.asc
Description: OpenPGP public key


OpenPGP_signature.asc
Description: OpenPGP digital signature


Bug#982195: obs-studio: Menus are messed up. highdpi related?

2022-09-20 Thread Debian GNU|Linux


On Sun, 07 Feb 2021 11:44:42 +0100 Alberto Fuentes  wrote:

Package: obs-studio
Version: 26.1.2+dfsg1-1+b1
Severity: normal
X-Debbugs-Cc: paj...@gmail.com

Dear Maintainer,

All menus are cut and messed up in general. I attach start log and snapshot

I have a very similar look in anki. And i have to start it with
ANKI_NOHIGHDPI=1

Maybe is related?


does it help if you start obs with the '--disable-high-dpi-scaling'
flag?

gfamdsr
IOhannes


OpenPGP_0xB65019C47F7A36F8.asc
Description: OpenPGP public key


OpenPGP_signature
Description: OpenPGP digital signature


Bug#1016685: v4l2loopback: CVE-2022-2652 - leaking kernel memory via crafted card labels

2022-08-05 Thread Debian GNU|Linux
On Fri, 05 Aug 2022 09:41:46 +0100 Neil Williams  
wrote:

The following vulnerability was published for v4l2loopback (and is not
included in the recent v0.12.7 git tag).


how so?



For further information see:

[0] https://security-tracker.debian.org/tracker/CVE-2022-2652
https://cve.mitre.org/cgi-bin/cvename.cgi?name=CVE-2022-2652

Please adjust the affected versions in the BTS as needed.


as upstream, i strongly believe that the v0.12.7 release includes the 
relevant fix.
is it enough t to just change the affected version or do I have to do 
something else as well?


mgfads
IOhannes


OpenPGP_signature
Description: OpenPGP digital signature


Bug#1009854: ITS: opusfile

2022-05-18 Thread Debian GNU|Linux


On 4/19/22 10:59, IOhannes m zmölnig (Debian/GNU) wrote:

Source: opusfile
Version: 0.9+20170913-1.1
Severity: important

[...]

it would be great to hear something from the current maintainer of
"opusfile".



given that i have not had any feedback from ron for 29 days (with 21 
days being the grace period as outlined in [1]), nor any objection from 
anyone else, i'm going to proceed with salvaging "opusfile".


thanks for your attentions.

gfdmasr
IOhannes



cheers




[1] Debian Developer's Reference §5.12



OpenPGP_0xB65019C47F7A36F8.asc
Description: OpenPGP public key


OpenPGP_signature
Description: OpenPGP digital signature


Bug#1004633: gmerlin-avdecoder: FTBFS with ffmpeg 5.0

2022-02-03 Thread Debian GNU|Linux
On Sun, 30 Jan 2022 23:04:11 +0100 Sebastian Ramacher 
 wrote:

Source: gmerlin-avdecoder
Version: 1.2.0~dfsg-11
Severity: important
X-Debbugs-Cc: sramac...@debian.org
Tags: sid bookworm ftbfs
Usertags: ffmpeg5.0


urgh.

i have done a quick search, but haven't found any upgrading guide to 
migrate code-bases from ffmpeg4 to ffmpeg5.


am i missing something?

gfamsdf
IOhannes


OpenPGP_signature
Description: OpenPGP digital signature


Bug#1004415: libassimp-dev: assimpTargets.cmake generates an invalid INTERFACE_INCLUDE_DIRECTORIES

2022-01-26 Thread Debian GNU|Linux

On 1/27/22 05:14, David Fries wrote:

It would be great if the Debian stable version of assimpTargets.cmake
be released with the fix.


in general, the "Debian stable version" is releasED.
the release date for the current Debian/stable version was 2021-08-14, 
that is: in the past.

i cannot really do anything about the past.

i'm not fully decided whether i would want to provide a package for 
"bullseye-update" for this issue (i'm leaning towards "no", but haven't 
actually assessed the amount of work that needs to be done for that),


gfmasd
IOhannes


OpenPGP_0xB65019C47F7A36F8.asc
Description: OpenPGP public key


OpenPGP_signature
Description: OpenPGP digital signature


Bug#988248: chiaki: No audio because of missing `libqt5multimedia5-plugins` package dependency

2021-06-01 Thread Debian GNU|Linux

Control: tags 988248 + patch
Control: tags 988248 + pending

Dear maintainer,

I've prepared an NMU for chiaki (versioned as 2.1.0-1.1) and
uploaded it to DELAYED/2. Please feel free to tell me if I should
cancel it.

mgdfsrt
IOhannes


OpenPGP_0xB65019C47F7A36F8.asc
Description: OpenPGP public key


OpenPGP_signature
Description: OpenPGP digital signature


Bug#985507: v4l2loopback-utils: Unable to use dynamic device management due to old version

2021-03-22 Thread Debian GNU|Linux

hi,

On 3/19/21 11:43 AM, JCGoran wrote:

Dear Maintainer,

The current version of v4l2loopback-ctl in Unstable (currently 0.6) is a bit
behind compared to upstream, and, as a result, I am unable to use dynamic
device management to create new loopback devices on-the-fly since the option
does not exist, see:

https://github.com/umlaeute/v4l2loopback#dynamic-device-management

As a workaround, I built v4l2loopback-ctl directly from upstream, but it would
be great if the new version was included in Debian.


ah no.
in order for dynamic device management to work, you need support in the 
loopback module itself.

just updating the utilities doesn't help.

there has not been a *release* of v4l2loopback that has dynamic device 
management.

the reasons are explained in
   https://github.com/umlaeute/v4l2loopback/issues/398

as soon as upstream releases a new version of `v4l2loopback`, the Debian 
packages will be updated accordingly.

not sooner.

gmsdrtf
IOhannes



Bug#968416: lintian: Gives ridiculous warning about spelling in overrides file

2020-10-21 Thread Debian GNU|Linux
On Fri, 14 Aug 2020 19:27:46 -0700 Felix Lechner 
 wrote:

> And BTW. are you going
> to check spelling of comments in source code files as well? I'm pretty
> sure you can find a lot of spelling typos there...


> I am sorry but we do not plan to implement your suggestion. You may be
> correct that there are lots of typos in code comments but that task is
> too complicated for us.

i think this was a tongue-in-cheek comment:
lintian doesn't do spell-checking in comments, and i think that's fine.
i (guess i) agree with robert, that lintian shouldn't do spell-checking 
in comments of lintian-override files either.



>
> > what's the point of checking spelling there?
>
> Like most of our tags, this one is based on user suggestions.

could you please point to the relevant bug-report?
i think it is great that lintian does spell-checking.
inevitably it will find false-positives (that's to be expected).
in this case, i think the sensible thing for maintainers is to override 
the false-positive it's good practice to document the context why this 
is not a spelling error in the first place.

in many cases, this will re-produce the false-positive in the comment.
which makes it all a bit tautological.
(if i override the "spelling-in-override-comment" tag, will it trigger 
another warning?)



i therefore propose to ignore spelling errors in lintian-override files 
if they appear in comments directly before any "spelling-in-*" tag in 
the overrides file.


fgmndasr
IOhannes



Bug#971737: lightning: all calendars disappeared (and throws errors when double-clicked)

2020-10-06 Thread Debian GNU|Linux

On 10/6/20 2:10 PM, Carsten Schoenert wrote:


lightning is since version 1:76.0_b1-1 a transitional package so there
aren't any files within this package except the default Debian specific
files.


yes, i'm aware of that (hence i only mentioned the upgrade of 
thunderbird to the new version)




Any Add-ons installed locally within the copied profile? Any Add-on not
disabled while working on the profile?




turns out the "lightning" add-on was still active.
once i disabled it (and restarted thunderbird), the calendars are back 
to normal.


i'm *pretty sure* that i didn't install the lightning add-on outside of 
Debian (that is: as a *local* add-on).
so i guess there's a problem with the upgrade path from the 
Debian-packaged lightning (1:68.12.0-1) to the transitional package.


gmdsr
IOhannes

PS: i'm leaving this open, in case you want to verify whether this is 
indeed an upgrade problem; for me, the problem is fixed now.