Package: nginx
Version: 1.26.0-1
Severity: wishlist
It would be nice to actually enable the QUICK module, either as part of
the main package or a separate module. This requires
--with-http_v3_module at build time.
Reading the debian changelog I saw QUICK support for ufw and I got the
impression
Package: chromium
Version: 124.0.6367.78-1
Severity: grave
The current package in debian unstable fails to start with the following
missing symbol:
$ chromium
grep: warning: stray \ before -
/usr/lib/chromium/chromium: symbol lookup error: /usr/lib/chromium/chromium:
undefined symbol:
Package: olive-editor
Version: 20221024+ds-1+b2
Severity: wishlist
It would be nice to have a more current snapshop of olive-editor.
I tried the packaged version, but I run in numerious audio sync issues
and other bugs that made it hard to actually use.
A current version from the appimage
Package: syslog-ng-core
Version: 4.3.1-2
Severity: normal
The configuration file provided in syslog-ng-core has "@version: 3.38",
which triggers the following warning on startup:
> WARNING: Configuration file format is too old, syslog-ng is running in
> compatibility mode. Please update it to
Package: syncthing
Version: 1.19.2~ds1-2
Severity: normal
With 1.19.2~ds1-2 syncthing panis immediately on the first connection
with the following error:
| goroutine 685 [select]:
|
github.com/syncthing/syncthing/lib/fs.(*BasicFilesystem).watchLoop(0xc0002ec180,
{0x12318d0, 0xc00066f7c0},
On Tue, Aug 08 2023, Stéphane Glondu wrote:
> Meanwhile, there are things to do:
> - generalize the use of ocaml_dune DH buildsystem (~60 packages)
> - replace dependencies on ocaml-nox by ocaml, to eventually remove the
> transitional package (~174 packages)
> - wait for camlp5-buildscripts to
Package: ocaml
Version: 4.13.1-4
Severity: wishlist
Is there any plan to eventually package ocaml 5.0.0?
-- System Information:
Debian Release: trixie/sid
APT prefers unstable
APT policy: (900, 'unstable'), (800, 'experimental'), (500, 'unstable-debug')
Architecture: amd64 (x86_64)
Foreign
Package: debdelta
Version: 0.67
Severity: normal
Seems like the server hosting deltas has ran out of space on the
2023-08-01:
http://debdeltas.debian.net/logs.txt
| 2023-08-01 13:23:41,248 32034 ERROR append_to_sql_history error while
adding to history
| Traceback (most recent call last):
|
> Which was simply not do-able with the previous codebase;
> so I'm quite stuck in chicken & egg problem and need
> to cut the knot somehow.
>
> I never wrote any unit test before (even at work ...)
> so this is my first attempt:
>
Package: systemd-cron
Version: 1.16.1-1
Severity: important
Unfortunately 1.16.1 doesn't accept my existing crontab, failing on the
already on first line:
crontab: unknown schedule in /tmp/crontab_o81kjgn_: */5 * * * * fetch-mail
It seems that any entry with a '*' gets rejected
-- System
Package: systemd-cron
Version: 1.16-1
Severity: important
% crontab
File "/usr/bin/crontab", line 106
if (not len(job.timespec_month)
^
SyntaxError: '(' was never closed
-- System Information:
Debian Release: trixie/sid
APT prefers unstable
APT policy: (900, 'unstable'), (800,
Package: qbittorrent-nox
Version: 4.5.2-2
Severity: important
dpkg: error processing archive
/var/cache/apt/archives/qbittorrent-nox_4.5.2-2_amd64.deb (--unpack):
trying to overwrite '/lib/systemd/systemd', which is also in package systemd
252.6-1
-- System Information:
Debian Release: 12.0
Package: aide
Version: 0.18.1-1
Severity: normal
After updating from 0.18-2 to 0.18.1-1, dailyaidecheck doesn't start
anymore:
dailyaidecheck[102105]: terminated: Temporary directory
/var/lib/aide/dailyaidecheck has wrong owner/mode.
systemd[1]: dailyaidecheck.service: Main process exited,
Source: postgrey
Version: 1.37-1.1
Severity: normal
systemd complains about %r usage when reloading postgrey's service file:
postgrey.service: Specifier '%r' used in unit configuration, which is
deprecated. Please update your unit file, as it does not work as
intended.
-- System Information:
On Fri, Dec 30 2022, Konomi wrote:
> I just did another round of updates and rebooted and could not
> reproduce the bug so I leave it to more experienced users to determine
> what should be done.
Looks like this was fixed by console-setup 1.214 for #1027247
Package: libmpfr-dev
Version: 4.1.1-1
Severity: important
According to https://github.com/CGAL/cgal/issues/7064 mpfr 4.1.1 was
updated after-the-fact without a version bump.
mpfr 4.1.1 in debian has a broken macro definition of
mpfr_custom_get_kind that prevents building against CGAL.
Looks
Package: cryptsetup
Version: 2:2.6.0-2
Followup-For: Bug #1027068
> There is no occurrence of ‘CCHAR’ or ‘UNUMBER’ in the source, so I
> suspect this might be orthogonal to src:cryptsetup.
Just FIY I was hit by the same.
This happens before the vg password prompt, clearly something I would
Package: libwxgtk3.2-0
Version: 3.2.1+dfsg-1
Severity: normal
wxWidgets 3.1+ enables EGL support by default, which also needs to be
enabled in GLEW. GLEW 2.2.0 EGL support is disabled (see #1020640 for
bug in glew 2.2).
This results a failure in creating an opengl context in several programs:
Package: python3-aiohttp-socks
Version: 0.7.1-1
Severity: grave
aiohttp-socks 0.7.1 fails to import:
>>> import aiohttp_socks
Traceback (most recent call last):
File "", line 1, in
File "/usr/lib/python3/dist-packages/aiohttp_socks/__init__.py", line 4, in
from python_socks import (
On Mon, Oct 31 2022, Michael Tokarev wrote:
>> to 4.9.11+dfsg-1. The error code given by CUPS is
>> NT_STATUS_LOGON_FAILURE, although I did not change the smb:// URI so the
>> credentials are known to be correct. Downgrading to 4.9.5+dfsg-5 fixes
>> the problem.
>
> Is it still an issue with
Package: fonts-noto-color-emoji
Version: 2.038-1
Severity: wishlist
Noto also includes a mostly black version called simply "Noto Emoji".
https://fonts.google.com/noto/specimen/Noto+Emoji
I find this version to be a better up-to-date replacement for
fonts-symbola, as well as being more readable
Package: mesa-common-dev
Version: 22.2.0~rc1-1
Followup-For: Bug #1016801
Upstream bug report: https://gitlab.freedesktop.org/mesa/mesa/-/issues/6976
-- System Information:
Debian Release: bookworm/sid
APT prefers unstable
APT policy: (900, 'unstable'), (800, 'experimental'), (500,
Package: libgl1-mesa-dri
Version: 22.2.0~rc1-1
Severity: important
Upgrading from 22.1.3-1 to 22.2.0~rc1-1 makes blender crash on
startup inside libllvm, I guess due to llvmpipe.
Thread 24 "blender:sh4" received signal SIGSEGV, Segmentation fault.
[Switching to Thread 0x7fff96eff640 (LWP
On Sat, Jul 16, 2022 at 11:39:55AM +0200, Tobias Frost wrote:
On Fri, 26 Nov 2021 16:15:32 +0100 Yuri D'Elia
wrote:
libocct-visualization is supposed to include TKIVtk, but in reality
it doesnt.
Can you describe your use case a bit?
Otherwise, this is on purpose. See #978017 for rationale
On Wed, May 18 2022, Debian Bug Tracking System wrote:
> This is an automatic notification regarding your Bug report
> which was filed against the shiboken2 package:
>
> #1010747: Unusable with current python version
>
> It has been closed by Debian FTP Masters
> (reply to Georges Khaznadar
> ).
Package: shiboken2
Version: 5.15.2-2+b2
Severity: grave
shiboken2 cannot currently be used to build any package due to #1008849.
I'm reporting this again as a grave bug, since while #1008849 might be
intended to address the underlying issue, it's important to note that
the _current_ package is
On Thu, Apr 21 2022, Yuri D'Elia wrote:
> On Thu, Apr 21 2022, Nicholas D Steeves wrote:
>> Unfortunately I'm out of time for the near future, but if you'd like I
>> can upload an untested 5.15.3 package to experimental for you to test.
>
> I can definitely help testing this.
Ping! ;)
On Thu, Apr 21 2022, Nicholas D Steeves wrote:
> Unfortunately I'm out of time for the near future, but if you'd like I
> can upload an untested 5.15.3 package to experimental for you to test.
I can definitely help testing this.
> To be honest, I won't have time to make the cmake fix for what
On Wed, Apr 13 2022, Nicholas D Steeves wrote:
> I understand, and agree that the issue is real, and that a rebuild is
> required. A binNMU is the most expedient solution ;-) Please read
> "What are binNMUs?" at the link provided above...
Yes, but I wouldn't call this "expedient", since ...
>
On Tue, Apr 12 2022, Nicholas D Steeves wrote:
>> This also requires that shiboken2 should be currently rebuilt.
>>
>
> Agreed.
>
>> Either the python3 dependency should be tightened, or FORCE_LIMITED_API
>> should be used.
>
> These are not the only available options. Are you aware of binNMUs?
>
Package: libshiboken2-py3-5.15
Version: 5.15.2-2+b2
Severity: important
shiboken2 depends on a sepecific major+minor version of python.
/usr/lib/x86_64-linux-gnu/cmake/Shiboken2-5.15.2/shiboken_helpers.cmake
checks for this.
As a result, attempting to build any package cmake package using
Source: python-systemd
Followup-For: Bug #1006743
This issue currently breaks fail2ban for me, which is now defaulting to
python3.10 (via the default python3 dependency).
Package: xserver-xorg-video-amdgpu
Version: 21.0.0-2
Severity: normal
I'm currently setting up a new system, but cannot install this driver as
xorg 2:21.* is now providing xorg-video-abi-25.
I'm not seeing any automatic transitions and/or new rebuilds.
On Mon, Jan 24 2022, Yves-Alexis Perez wrote:
> I assume you're talking about systemd user services or something? I don't
> think there's any specific code in lightdm about starting manually pulseaudio,
> pipewire or anything, so I don't think there's a way to special cases some
> thing.
Yes, the
Package: lightdm
Version: 1.26.0-8
Severity: normal
The user which is running lightdm starts all "user" services which are
enabled by default, which might include pipewire (and I guess
pulseaudio), gnupg.. synchthing.
I find this behavior undersiderable. pipewire/pulseaudio could probably
by
Package: oomd
Severity: normal
Unpacking oomd (0.5.0-1+b1) ...
dpkg: error processing archive
/var/cache/apt/archives/oomd_0.5.0-1+b1_amd64.deb (--unpack):
unable to open '/usr/lib/systemd/system/oomd.service.dpkg-new': No such file
or directory
Errors were encountered while processing:
Package: grub2-common
Version: 2.06-2
Followup-For: Bug #1000832
IMHO the warning should be suppressed if the value is set (with either
value). I had/have:
GRUB_DISABLE_OS_PROBER=true
in my /etc/default/grub and I still see the warning, despite the fact
that I intentionally always disabled
Package: debdelta
Version: 0.67
Severity: normal
When a package includes a "+" in the version, apt currently saves the
file using "+", whereas debdelta saves the file using a % escape: "%2b".
Because of this, debdelta can still download/create the deb archive,
but apt will fail to recognize its
Package: jupyter-notebook
Version: 6.4.5-3
Followup-For: Bug #1003722
This should be higher priority.
I can confirm I get a JS error upon starting 'jupyter notebook' from the
CLI using either Firefox:
Uncaught ReferenceError: exports is not defined
Package: intel-opencl-icd
Followup-For: Bug #998058
Any news?
On Sun, Jan 02 2022, Louis-Philippe Véronneau wrote:
> I see that you've done some work packaging this module in Debian already:
>
> https://salsa.debian.org/python-team/packages/tabview/
>
> I'm currently packaging CleverCSV and tabview is an optional dependency.
> I was wondering if you were
Package: weechat-python
Version: 3.3-1+b1
Severity: normal
With the recent updates of python3-async-timeout/python3-aiohttp
packages, I cannot load the weechat-matrix python plugin anymore (among
others). Weechat either crashes with an illegal instruction during
start, gets stuck forever while
On Sat, Dec 11 2021, Ludovic Rousseau wrote:
> If you mask both the socket and the service (or just the service) then
> you do not have any problem. Exact?
> If yes, may I close this bug report?
Yes, thank you.
On Sat, Dec 11 2021, Ludovic Rousseau wrote:
> Hello Yuri,
>
> I got no answer to my questions.
Sorry about that, didn't get anything.
>> I note I get the same error if I use service(8) instead of
>> invoke-rc.d(8) to
>> restart pcscd:
>> $ sudo service pcscd restart
>> Failed to restart
Package: pcscd
Version: 1.9.5-1
Severity: normal
Errors were encountered while processing:
pcscd
E: Sub-process /usr/bin/dpkg returned an error code (1)
Setting up pcscd (1.9.5-1) ...
Failed to restart pcscd.service: Unit pcscd.socket is masked.
invoke-rc.d: initscript pcscd, action "restart"
On Tue, Nov 30 2021, Debian Bug Tracking System wrote:
> This is an automatic notification regarding your Bug report
> which was filed against the python-aiohttp package:
>
> #1000664: python-aiohttp 3.7.4 depends on python-async-timeout < 4.0
By the way, it seems that weechat-python still
Package: dpkg
Version: 1.20.9
Followup-For: Bug #892664
I'd also love to see zstd support in dpkg. I'm following several PPAs
that offer daily builds and since ubuntu's migration to zstd-by-default
I can no longer benefit from the pre-built packages.
-- Package-specific info:
System tainted due
Package: python3-async-timeout
Version: 4.0.1-1
Severity: normal
Version 4.0.1-1 indirectly breaks weechat-python, which crashes with a
IOT signal. Downgrading to 3.3-1+b1 unbreaks it.
I'm not sure whether there's an issue with async-timeout, in
weechat-python, or some module used by
Package: libocct-visualization-7.5
Version: 7.5.1+dfsg1-2
Severity: normal
libocct-visualization is supposed to include TKIVtk, but in reality it
doesnt.
-- System Information:
Debian Release: bookworm/sid
APT prefers unstable
APT policy: (900, 'unstable'), (800, 'experimental'), (500,
On Wed, Nov 24 2021, Salvatore Bonaccorso wrote:
> On Wed, Nov 24, 2021 at 03:36:27PM +0100, Yuri D'Elia wrote:
>> Package: src:linux
>> Version: 5.15.3-1
>> Followup-For: Bug #1000403
>>
>> I'd like to report the same, still holding true on the current package
&
Package: src:linux
Version: 5.15.3-1
Followup-For: Bug #1000403
I'd like to report the same, still holding true on the current package
with a dell 7410 with the AX201.
The 5.16-rc1 has the same problem.
Package: xserver-xorg-video-dummy
Version: 1:0.3.8-1+b1
Severity: normal
xserver-xorg-video-dummy depends on xorg-video-abi-24, but the new
release of xorg 21.1 on experimental provides xorg-video-abi-25
Is there any progress on the FTBS?
libigc is now at 1.0.8744-2 which breaks 21.32.20609-1, making the icd
uninstallable.
Package: firefox
Version: 94.0-1
Followup-For: Bug #998108
Same here, problems started with 93.0-1+b1, and are also present on FF 94.
Firefox hangs at random times, doesn't quit properly preventing normal
restart, doesn't recognize audio devices correctly. As others noted,
FF hangs almost
Package: systemd-cron
Version: 1.5.17-3
Severity: important
cron-failure@ is using DynamicUser=yes, however this causes a silent
delivery failure when using exim4:
systemd[1]: Starting cron-failure@cron-monthly.service...
mail_on_failure[328561]: 2021-11-01 14:11:23 1mhX5v-001NTN-LU Failed to
Package: python3-click-threading
Version: 0.4.4-2
Followup-For: Bug #996337
The priority should probably be changed to important or above, since the
functionality of this package is broken currently and breaks software
which depends on it.
-- System Information:
Debian Release: bookworm/sid
Package: libvkd3d1
Severity: normal
Version: 1.2-6
Vesion 1.2-6 is currently uninstallable on debian experimental due to
the mesa-vulkan-drivers (< 21) dependency.
I assume this should have been >=.
-- System Information:
Debian Release: bookworm/sid
APT prefers unstable
APT policy: (900,
Hi everyone, any progress on this?
I noticed carla is now packaged in ubuntu
(https://launchpad.net/ubuntu/+source/carla) and I wonder if we could
reuse that effort to bring carla to debian too.
Package: llvm-12-linker-tools
Version: 1:12.0.1-7
Severity: important
Got this error while linking:
/usr/bin/ld: /usr/lib/llvm-12/bin/../lib/LLVMgold.so: error loading plugin:
/usr/lib/llvm-12/bin/../lib/LLVMgold.so: cannot open shared object file: No
such file or directory
The current
Package: libopenmpi-dev
Version: 4.1.1-2
Severity: important
dpkg: error processing archive
/var/cache/apt/archives/libopenmpi3_4.1.1-2_amd64.deb (--install):
trying to overwrite
'/usr/lib/x86_64-linux-gnu/openmpi/lib/libopen-orted-mpir.so', which is also in
package libopenmpi-dev:amd64
Package: siril
Version: 0.99.10.1-1
Severity: normal
In the latest package, siril depends on gvfs-backends, however I don't
see why this is the case.
Siril works fine without gvfs-backends installed.
-- System Information:
Debian Release: 11.0
APT prefers unstable
APT policy: (900,
Package: bluez
Version: 5.55-3
Followup-For: Bug #986005
Upstream is now at 5.58
On Sun, Apr 25 2021, Yuri D'Elia wrote:
> Relevant upstream bug reports:
>
> https://bugzilla.kernel.org/show_bug.cgi?id=212751
> https://bugzilla.kernel.org/show_bug.cgi?id=212725
FIY the proposed/accepted patch:
https://lore.kernel.org/linux-usb/20210421074513.4327-1-oneu...@
Source: linux
Version: 5.10.28-1
Followup-For: Bug #986995
I can confirm any device controlled by the acm driver has issues
starting with 5.10.28. Sometimes it's possible to just replug the serial
device to fix the issue, however for devices that reconnect after reset,
there's no work-around.
Package: libell-dev
Version: 0.36-1
Severity: wishlist
Upstream released ell 0.39
-- System Information:
Debian Release: 11.0
APT prefers unstable
APT policy: (900, 'unstable'), (800, 'experimental'), (500, 'unstable-debug')
Architecture: amd64 (x86_64)
Kernel: Linux 5.10.0-6-amd64 (SMP
Package: pulseeffects
Severity: wishlist
Hi maintainers,
Since pipewire is now available in unstable, would it be possible to
support for using pulseeffects directly with a pipewire daemon?
Would the current package/build already work with pipewire, or would
pulseeffects require a different
Package: rlwrap
Version: 0.43-1+b2
Severity: wishlist
Dear maintainer, upstream has released 0.45. It would be nice to update
due to several bug fixes affecting the current package.
Thanks!
-- System Information:
Debian Release: bullseye/sid
APT prefers unstable
APT policy: (900,
Package: bluez
Version: 5.55-3
Severity: wishlist
Dear maintainer, there seems to be a newer version of bluez 5.56
available.
-- System Information:
Debian Release: bullseye/sid
APT prefers unstable
APT policy: (900, 'unstable'), (800, 'experimental'), (500, 'unstable-debug')
Architecture:
Package: openjdk-17-jre-headless
Version: 17~14-1
Severity: normal
Just tried to run "josm" on openjdk-17, but I get the following error:
021-03-21 19:27:07.757 SEVERE: Handled by bug report queue:
java.lang.UnsatisfiedLinkError:
/usr/lib/jvm/java-17-openjdk-amd64/lib/libfontmanager.so:
Package: src:linux
Version: 5.10.13-1
Severity: wishlist
Recently our department upgraded some wireless Cisco equipment and as a result
I'm no longer able to connect to the wifi network.
The relevant part from the kernel shown during association is:
RX AssocResp from 4c:a6:4d:54:09:4c
On Mon, Feb 22 2021, Michael Biebl wrote:
> iwd will re-initialize your wireless interface when it starts (I think
> it unloads the firmware or something like that). At that point, both iwd
> and udevd are running and race against each other and usually iwd wins
> to claim the device.
I was about
On Sun, Feb 14 2021, Michael Biebl wrote:
>> I'd like, ideally, to keep stable interface names. I'm not sure if this
>> is intended, but so far after masking 80-iwd and removing "keep" from
>> the NamePolicy it seems that udev is always able to rename the interface
>> across reboots.
>>
>> It
On Sat, Feb 13 2021, Michael Biebl wrote:
>> If I want to keep exiting interface names I'd rather have to do this
>> configuration explicitly.
>
> By masking 80-iwd.link, both udev and iwd race against each other.
> Sometimes udev is fast enough to rename the interface, sometimes iwd is
> quick
On Sat, Feb 13 2021, Andreas Henriksson wrote:
>> Is it possible to synthesize a target for network interface names, to be
>> reached when all network interface names have settled somehow?
>
> As I see it the problem is that you currently have 2 options, but you
> configured things to be in a
It seems that the current version is 13.00, released March 2020,
at the new URL: https://dn-works.com/ufas/
On Thu, Jan 07 2021, Salvatore Bonaccorso wrote:
> Is this potentially the same as
> https://lore.kernel.org/keyrings/67250277-7903-2005-b94b-193bce0a3...@markus-regensburg.de/
> ?
Excellent catch, same scenario (and even hardware it seems)!
I created a new report earlier today:
Package: libjs-popper.js
Version: 1.16.1+ds-2
Severity: minor
libjs-popper.js shouldn't depend on javascript-common directly, unless a
web server is actually required (which isn't).
The dependency should be changed to a recommends or less.
Thanks.
Package: src:linux
Version: 5.10.4-1
Severity: normal
Starting with 5.10, kernel dies when attempting to connect to a 802.1x
network, showing the following trace:
[ 232.661980] Oops: [#5] SMP NOPTI
[ 232.661987] CPU: 5 PID: 2131 Comm: iwd Tainted: G DOE
5.10.0-1-amd64 #1
Package: sauerbraten
Version: 0.0.20140302-2
Severity: wishlist
Dear maintainer, there seems to be a newer version of sauerbraten
available: the "2020 edition".
It would be nice to have an update!
-- System Information:
Debian Release: bullseye/sid
APT prefers unstable
APT policy: (900,
Package: freecad
Version: 0.19~pre1+git20201123.8d73c8f0+dfsg1-1
Severity: important
freecad is searching modules in /usr/lib/freecad/Mod, however
freecad-common has them in /usr/share/freecad. Startup fails with:
Log: Init: starting App::FreeCADInit.py
Wrn: No modules found in
On Sat, Nov 21 2020, Sven Joachim wrote:
>> If the mlterm package changed that ut-default setting, then providing your
>> own termcap settings may have reset the behavior to match the compiled-in
>> NON-ut default.
>
> That seems to have hit the mark. Indeed, if ":ut" is added to Yuri's
> termcap
On Sat, Nov 21 2020, Sven Joachim wrote:
>>> mlterm-256color:\
>>> k1=\E[11~:k2=\E[12~:k3=\E[13~:k4=\E[14~
>>>
>>> Removing this (so that mlterm sends it's usual \EOP/*) fixes the
>>> background-color rendering.
>>>
>>> I'm puzzled as of why this override would influence this at all?
>>
>>
On Fri, Nov 20 2020, Sven Joachim wrote:
> Which version of mlterm do you use?
I'm also using mlterm 3.9.0-1.
So after some scrambling, I have a custom ~/.mlterm/termcap config to
override the sequence sent by F[1-4]:
mlterm-256color:\
k1=\E[11~:k2=\E[12~:k3=\E[13~:k4=\E[14~
Removing
Package: ncurses-term
Version: 6.2+20201114-1
Severity: normal
With the latest version, it seems that the
mlterm/mlterm3/mlterm-256color definitions are somewhat broken. The
background color set by term programs (say, aptitude) is not set
correctly anymore.
Switching to
Package: wine-development
Version: 5.5-5
Severity: wishlist
The current development package is a bit lagging against upstream.
Upstream's wine-development is at 5.18.
Package: libboost-dev
Version: 1.71.0.3
Severity: wishlist
It would be nice to have a package for an updated version of boost.
I've ran into a couple of packages that expect features from 1.73
already.
At the time of writing, upstream is at 1.74
On Tue, Jul 07 2020, Rémi Vanicat wrote:
> Could you show me the line 30 of the file
>
> /usr/share/emacs/site-lisp/elpa-src/magit-2.99.0/magit-tag.el
(require 'magit)
> Also please check if there is another version of magit installed in
> /root/.emacs.d or in /usr/local/share/emacs/site-lisp/
Package: elpa-magit
Version: 2.99.0.git0957.ge8c7bd03-1
Severity: important
The newer git version removes the dependency on elpa-magit-popup which
seems to be required:
...
In toplevel form:
magit-tag.el:30:1:Error: Cannot open load file: No such file or directory,
magit-popup
In toplevel
Package: hunspell-en-us
Version: 1:2019.10.06-1
Severity: minor
For an embarassingly long time I was wondering why
aspell/ispell/hunspell wouldn't handle correctly anything basic with
apostrophes, such as "isn't".
Turns out I read the explaination, by random chance, here:
Package: meshio-tools
Version: 4.0.16-1
Severity: normal
Caught during install:
Setting up meshio-tools (4.0.16-1) ...
Traceback (most recent call last):
File "/usr/bin/pypy3compile", line 186, in
main()
File "/usr/bin/pypy3compile", line 178, in main
py_compile.compile(module,
Package: screenkey
Severity: wishlist
A new upstream version of screenkey (1.1) is officially available, which
should fix bug #962118 as well.
Additionally, the package dependencies are incomplete.
screenkey should also depend explicitly on required GI interface
gir1.2-gtk-3.0.
I would also
Package: maim
Version: 5.5.3-1
Severity: important
I didn't realize maim depended on slop through a dso (I assumed it
simply called the binary).
slop was updated to 7.5, which broke maim as a result:
maim: error while loading shared libraries: libslopy.so.7.4: cannot open shared
object file:
Package: libyaml-cpp0.6
Version: 0.6.3-4
Followup-For: Bug #959201
This ABI breakage also affects blender (indirecly via opencolorio).
Version 0.6.3-4 does fix the symbol lookup error, however blender will
incur a crash soon after with a segmentation fault.
Downgrading libyaml-cpp0.6 to 0.6.2-4
Package: opencascade
Version: 7.3.3+dfsg1-2
Severity: minor
My understanding is that when choosing to include the version in the
package name of a library, is that so that we can allow for multiple
versions of the library to coexist on the same system.
However all libocct-* 7.4 libs break 7.3,
Package: systemd
Version: 245.5-1
Severity: minor
A time-keeping daemon is not always needed (guest OSes being the primary
example).
I know systemd-timesyncd was built-in up to 245.4-1, but it would be
nice to drop the hard dependency nonetheless so that I can avoid masking
the service entirely.
Package: libpango-1.0-0
Version: 1.44.7-3
Followup-For: Bug #939748
I was wondering why "dunst", suddenly, stopped displaying characters,
even though dunst itself didn't change.
Looking at the upgrade log, I catch pango, and now I see this.
I generally don't use bitmap fonts, but they have their
Package: debdelta
Version: 0.65
Severity: minor
There's a new deprecation warning that popped up recently:
/usr/bin/debdelta-upgrade:5386: DeprecationWarning: isAlive() is deprecated,
use is_alive() instead
while patching_thread.isAlive() or ('a' in DEB_POLICY and no_delta):
-- System
Package: aptitude
Version: 0.8.12-3
Followup-For: Bug #498241
I encountered this problem today. I'm trying to match all packages which
will upgraded on the next run, but turns out to be non-trivial.
'~U' includes packages with holds and forbids (and according to the
description: "packages that
Package: libxcb-xinput-dev
Version: 1.13.1-4
Severity: important
The new version cannot be installed as it depends on
"libxcb-xfixes0-dev." (typo with a trailing dot).
On Tue, Feb 04 2020, Nicholas D Steeves wrote:
>> This makes libqt5core5a uninstallable for me. I have several programs
>> which still depend on libqtcore4. I also still develop on qt4.
>
> FYI https://lists.debian.org/debian-devel-announce/2017/08/msg6.html
> and
1 - 100 of 765 matches
Mail list logo
