Bug#1065310: I've been hit by this bug also

Using different package name, all with t64 in their names and yes it seams that Provides: is not taken into account for reverse depends. -- eric

Bug#1065819: linux-source-6.6 cannot be rebuild according to debian documentation

Package: linux-source-6.6 Version: 6.6.15-2 Severity: grave Justification: renders package unusable As I wanted: 1) to stay on long term kernel 6.6 branch, 2) 6.7.x has been uploaded to unstable already, 3) I would like to enable NTFS3, and AMD TEE I decided I will try to recompile

Bug#1065388: libqt5core5t64: control files are wrong for all t64 qt libraries

Package: libqt5core5t64 Version: 5.15.10+dfsg-7.1 Severity: grave Justification: renders package unusable Package: libqt5core5t64 Source: qtbase-opensource-src Version: 5.15.10+dfsg-7.1 Architecture: amd64 Maintainer: Debian Qt/KDE Maintainers Installed-Size: 6061 Depends: shared-mime-info,

Bug#1065349: libsmbclient0: Actually breaks part of t64 transition

Package: libsmbclient0 Version: 2:4.19.5+dfsg-3 Severity: grave Justification: renders package unusable the control file should contain: Provides: libsmbclient (= 2:4.19.5+dfsg-3) Otherwyse as many package depends on libsmbclient it cannot be removed and the replace is not sufficient. I

Bug#1061242: libreoffice-impress: impress cannot start. Its display an error loading a dll that is installed

On 21/01/2024 14:49, Rene Engelhard wrote: Exactly that is the point of #1059040. The binary packages have to be renamed. (Then rebuild against libxml2-WHATEVERNEW). Then a rebuild LO will have a proper dependency on libxml2-WHATEVERNEW. I agree that package with different APIs should bump

Bug#1061242: libreoffice-impress: impress cannot start. Its display an error loading a dll that is installed

Package: libreoffice-impress Version: 4:24.2.0~rc2-2 Severity: grave Justification: renders package unusable When I open a odp file, I get the message: loading of component failed /usr/lib/libreoffice/program/libsdlo.so dpkg -S /usr/lib/libreoffice/program/libsdlo.so libreoffice-draw:

Bug#1031363: Fixed with 0.17.0-3 and thunderbird 1:115.1.1-1

The 0.17 in unstable and the thunderbird version that use the external lib are happily working together. But can be closed. -- eric

Bug#1034796: kio-gdrive: Does not work. Network account create does not propose gogle drive

Package: kio-gdrive Version: 22.12.3-1 Severity: grave Justification: renders package unusable Using dolphin for network, you can select gdrive but it does not propose to add a google account. Using systemsettings, I have the same problem and using the command rpoposed in the packahe readme.md

Bug#1031363: librnp0 from experimental breaks thunderbird openpgp feature

Package: librnp0 Version: 0.17.0~git20220428-1 Severity: serious Justification: makes unrelated software on the system Thre is no dependency and the packages installs but thunderbird do not manage to dlopen the dddl and it breaks opengpg. Downgrading to unstable version fixes the problem. --

Bug#1031129: libglib2.0-0: breaks pipewire/wireplumber

On Sun, 12 Feb 2023 13:23:40 +0100 Eric Valette wrote: On 12/02/2023 12:15, Simon McVittie wrote: > Control: severity -1 serious > > On Sun, 12 Feb 2023 at 11:16:18 +0100, Eric Valette wrote: >> Severity: critical >> Justification: breaks unrelated software > >

Bug#1031129: libglib2.0-0: breaks pipewire/wireplumber

On 12/02/2023 12:15, Simon McVittie wrote: Control: severity -1 serious On Sun, 12 Feb 2023 at 11:16:18 +0100, Eric Valette wrote: Severity: critical Justification: breaks unrelated software wireplumber uses GLib, so this is not unrelated software. If you use this definition, you cannot

Bug#1031129: libglib2.0-0: breaks pipewire/wireplumber

On 12/02/2023 12:14, Jeremy Bícha wrote: Control: forwarded -1 https://gitlab.gnome.org/GNOME/glib/-/issues/2769 On Sun, Feb 12, 2023 at 5:18 AM Eric Valette wrote: Package: libglib2.0-0 Version: 2.75.2-1 Severity: critical Justification: breaks unrelated software I've tried to install

Bug#1031129: libglib2.0-0: breaks pipewire/wireplumber

Package: libglib2.0-0 Version: 2.75.2-1 Severity: critical Justification: breaks unrelated software I've tried to install this version on two different machines and each time it did break wireplumber/pulseoaudio. extract of journalctl: févr. 12 11:13:06 tri-yann4 wireplumber[2267]: Failed to

Bug#1025366: Note that the bug is also present in 7.0.6

On 25/01/2023 10:36, Gianfranco Costamagna wrote: On Sun, 4 Dec 2022 11:19:52 +0100 Eric Valette wrote: Already fixed there same ways but did not report the bug hoping it will be soon fixed. -- eric Hello, please try 7.0.6 thanks Same error, same fix. As long as the file does

Bug#1025901: libunistring2: Breaks system due to missing libunistring.so.2

Package: libunistring2 Version: 1.1-1~experimental1 Severity: critical Justification: breaks unrelated software This breaks NetworkManaget, apt ... nmcli nmcli: error while loading shared libraries: libunistring.so.2: cannot open shared object file: No such file or directory apt-cache policy

Bug#1025366: Note that the bug is also present in 7.0.2

Already fixed there same ways but did not report the bug hoping it will be soon fixed. -- eric

Bug#1025366: virtualbox-dkms does not compile with gcc-12

Package: virtualbox-dkms Version: 7.0.4-dfsg-4 Severity: grave Tags: upstream Justification: renders package unusable dkms autoinstall Sign command: /usr/lib/linux-kbuild-5.10/scripts/sign-file Binary /usr/lib/linux-kbuild-5.10/scripts/sign-file not found, modules won't be signed Building

Bug#1024395: CONFIG_INTEGRITY_PLATFORM_KEYRING was missing for mokutil --list-enrolled to work

CONFIG_INTEGRITY_PLATFORM_KEYRING=y But the bug is still there -- eric

Bug#1024395: The mokutil --list-enrolled is due to kernel config or version

I tested with 6.0.0-4-amd kernel version, and there mokutil --list-enrolled works. So either it is a missing config item in my own generated kernel (what is needed beside all *EFI* config items, something in keyring or crypto algo?) or a kernel incompatibilty (5.10.155). But that has

Bug#1024647: trac: The versiuon packaged by debian contain a bug fixed upstream that prevent it to work with python3

Package: trac Version: 1.5.3+dfsg-1 Severity: grave Tags: upstream Justification: renders package unusable Afterupgrading and oldoldstable distrib to stable 11.5, becaue of the move to python3 I had to update trac to the sid version as there is not stable version yet. It did not work at all

Bug#1024395: Downgrading fixes the problem.

downgrading to 1+2.06+3~deb11x grub-common grub-efi grub-efi-amd64 grub-efi-amd64-bin grub-efi-amd64-signed grub2-common shim-helpers-amd64-signed fix the error. However the mokutils --list-enrolled command is still void. -- eric

Bug#1024395: inconsistencies between shim-signed versions (= 15.4-7) and shim-helpers-amd64-signed shim (= 15.6-1)

dpkg -s shim-signed Package: shim-signed Status: install ok installed Priority: optional Section: utils Installed-Size: 937 Maintainer: Debian EFI Team Architecture: amd64 Multi-Arch: same Source: shim-signed (1.38) Version: 1.38+15.4-7 Depends: shim-signed-common (>= 1.38+15.4-7),

Bug#1024395: If I try to enroll the same key again : no chnage.

So apparently the keys is still there but mokutil does not see it. Strange! -- eric

Bug#1024395: grub-efi-amd64-signed: after upgrade to 1+2.06+5 I get errors when booting (although I manage to boot)

Package: grub-efi-amd64-bin Version: 1+2.06+5 Severity: grave Tags: security Justification: user security hole X-Debbugs-Cc: Debian Security Team After upgrade to 2.06-5, I get an error message "prohibited by secure boot policy" and it boot with a strange look with \xe7caracaters instead of

Bug#1014745: Bug seems fixed in 102.0.3 (SMIME was activated for me)

As I had SMIME configured on that specific account, I assume from changelog it could be fixed. --eric

Bug#1014745: thunderbird: Reply all remove Cc participants

On 14/07/2022 12:04, Carsten Schoenert wrote: Hello Eric, Am 14.07.22 um 11:48 schrieb eric: I had the same problem on a specific exchnage account. Reply all did not copy the content and did remove all the CC. you could try out TB 1:103.0~b5-1 from experimental which should have included the

Bug#1013447: gupnp-tools: gupnp-av-cp fails to detect upnp av serveur that kodi or vlc detects correctly

Package: gupnp-tools Version: 0.10.3-1 Severity: grave Justification: renders package unusable starting gupnp-av-cp does not detect any DLNA (minidlnad, smartv TV, ...) content server on local network. VLC and Kodi do detect them. -- System Information: Debian Release: bookworm/sid APT

Bug#1008316: dpkg-fsys-usrunmess breaks system boot

On 28/03/2022 12:35, Guillem Jover wrote: There was no printed error beside the arror from dkms postinst (virtualbox assumed it was running virtualized, and nvidia just failling): just a congratulation message. Diid not check the return value of the script  via echo $? Ok, so if the script

Bug#1008316: dpkg-fsys-usrunmess breaks system boot

Package: dpkg Version: 1.21.4 Severity: critical Justification: breaks the whole system Gobally the scripts does a very good job but it missed to copy /usr/lib/modules to /lib/modules on a self generated kernel that has modules build via dkms and a few native kernel modules. Invoquing the dkms

Bug#979719: socat in experimental is obsolete and no installable

Package: socat Version: 2.0.0~beta9-1 1 Severity: grave Justification: renders package unusable I can no more be installed apt-get -t experimental install socat Reading package lists... Done Building dependency tree Reading state information... Done Some packages could not be installed.

Bug#979540: kde-config-gtk-style: Configuring gtk theme on KDE result in abnormal output on stdout

Package: kde-config-gtk-style Version: 4:5.20.5-1 Severity: critical Justification: breaks unrelated software I have been hunting a bug that after this morning update it took me the day long and one of the visible effect was that it broke my vpn application that is using yad to display some

Bug#974730: systemd 247~rc2-2 install crashed several system

Le 14/11/2020 à 17:50, Michael Biebl a écrit : This is very bad for remote managed Linux system with difficult access like in data center... In a data center (without remote access) I would recommend *not* using unstable, and experimental even more so. I uploaded this version to experimental

Bug#974730: systemd 247~rc2-2 install crashed several system

Le 14/11/2020 à 13:54, Michael Biebl a écrit : Are you configuring your NAS with ifupdown (using allow-hotplug). Yes indeed. I use a fixed address outside my DHCP dynamic range so no need to something sophisticated and no graphical interface so no need for network-manager and I hate

Bug#974730: systemd 247~rc2-2 install crashed several system

Package: systemd Version: 247~rc2-2 Severity: critical Justification: breaks the whole system I have updated several machine with experimental version and they did break for various reasosn during install: 1) One is a NAS that I was updating via ssh. during update, the ssh session

Bug#971072: nvidia-kernel-support from experimental cannot be installed due to missing nvidia-modprobe (>= 455)

Package: nvidia-kernel-support Version: 455.23.04-1 Severity: grave Justification: renders package unusable apt-get -t experimental install nvidia-driver nvidia-kernel-dkms nvidia-alternative nvidia-kernel-support Reading package lists... Done Building dependency tree Reading state

Bug#969171: akonadi-server expects akonadi-backend-mysql allthough any sql backend should work

Package: akonadi-server Version: 4:20.04.1-2+b1 Severity: grave Justification: renders package unusable akonadi server support any backend from package dependency point of view. However trying to start it via akonadictl start you get: org.kde.pim.akonadictl: Starting Akonadi Server...

Bug#936785: Fix has been proposed to support python 3

-- eric #!/usr/bin/python3 # # ketchup 1.0.1 #http://github.com/psomas/ketchup #git://github.com/psomas/ketchup.git # # Orignial code by: #Copyright 2004 Matt Mackall # # Added code for new RT location and maintained until 2011 by: #Steven Rostedt # # Now maintained by: #

Bug#952426: digikam: digkam experimental not correctly instalable

On 25/02/2020 14:35, Eric Valette wrote: I disagree with your interpretation : I read since then the policy for the shared libraries and indeed only libraries with the dynamic linker attribute NEEDED create dependencies. So on this part you are perfectly right. However that does not explain

Bug#952426: digikam: digkam experimental not correctly instalable

On 25/02/2020 10:38, Simon Frei wrote: On 25/02/2020 10:27, Agustin Martin wrote: There is still the problem of the undeclared digikam dependency on the hdf5 stuff. There's no such problem, digikam does not in itself depend on hdf5 (https://www.digikam.org/api/index.html#externaldeps). As I

Bug#952426: digikam: digkam experimental not correctly instalable

On 25/02/2020 02:37, Steven Robbins wrote: Eric, Thank you for the bug report. Per your question: I do indeed test before uploading -- I've been using Digikam 7 since I uploaded last week. Well if there had been an explicit dependency against libhdf5-103, installing would not have even

Bug#952426: digikam: digkam experimental not correctly instalable

On 24/02/2020 12:47, Agustin Martin wrote: This bug has already been reported by me and fixed for 6.4 To be honest, it just disappeared for 6.4, bit I could not find an action leading to that. According to "ldd -v /usr/bin/digikam" output digikam 5.9.0 had a dependency on

Bug#952426: digikam: digkam experimental not correctly instalable

On 24/02/2020 12:57, Agustin Martin wrote: Hi, According to https://packages.debian.org/source/experimental/hdf5 there is a new "libhdf5-hl-100" package in experimental. Looking into it, seems that libhdf5_serial_hl.so.100 has been moved there, so installing that new package should help in

Bug#952426: digikam: digkam experimental not correctly instalable

On 24/02/2020 12:09, Simon Frei wrote: Firstly: I don't upload digikam to debian. I am just a user interested in having it packaged and very occasional contributor upstream. By helping to triage and clarify bugs I hope to remove some workload from Steve (uploader), which hopefully makes it more

Bug#952426: digikam: digkam experimental not correctly instalable

On 24/02/2020 10:50, Simon Frei wrote: Did you just copy the error message from there, or did this error come up with the package from experimental installed? The experimental version installed type digikam digikam est /usr/bin/digikam valette@tri-yann4:~$ digikam --version digikam: error

Bug#952426: digikam: digkam experimental not correctly instalable

Package: digikam Version: 4:7.0.0~beta2+dfsg-1 Severity: grave Justification: renders package unusable digikam digikam: error while loading shared libraries: libhdf5_serial_hl.so.100: cannot open shared object file: No such file or directory Has already been reported. But in addition,

Bug#950576: network-manager fails to correctly configure eth0 speed and fails when autoneg is on

Package: network-manager Version: 1.22.6-1 Severity: critical Justification: breaks unrelated software If I let eth0 in /etc/network/interface I get my eth0 card correctly configured by ifplugd each time using full duplex and 1000Mbps ethtool eth0 Settings for eth0: Supported ports: [

Bug#949644: Note that it also breaks thunderbird in addition to firefox

Both were broken and reverting fixed both -- eric

Bug#949648: firefox-esr: New version crash immediately at start

On 23/01/2020 09:06, Jonas Smedegaard wrote: Please check the details at https://bugs.debian.org/949644 and report back if reverting package libsqlite3-0 from version 3.31.0-1 to the previous version 3.30.1+fossil1 makes Firefox work again. After opening this one, I found thunderbird was

Bug#949648: firefox-esr: New version crash immediately at start

Package: firefox-esr Version: 68.4.2esr-1 Severity: grave Justification: renders package unusable Crash at startup sice yesterday upgrade. -- Package-specific info: -- Addons package information -- System Information: Debian Release: bullseye/sid APT prefers unstable APT policy: (500,

Bug#948207: kio-gdrive: No more work because google temoprarilly supressed the access

Package: kio-gdrive Version: 1.2.7-1+b2 Severity: grave Tags: upstream Justification: renders package unusable I received this moring an email form google I had non trusted application using my google information. It was KDE access and indeed it asked for a handfull of authorizations when ony

Bug#946380: wicd-gtk does not find gtk modules

Package: wicd-gtk Version: 1.7.4+tb2+2019.09.18git2e0ba579-1 Severity: grave Justification: renders package unusable wicd-gtk Traceback (most recent call last): File "/usr/share/wicd/gtk/wicd-client.py", line 41, in import gtk ModuleNotFoundError: No module named 'gtk' And the

Bug#943974: [debian-mysql] Bug#943974: mariadb-server-10.3: as "service mysql stop" fails, system refuse to shut down

On 02/11/2019 13:03, Otto Kekäläinen wrote: Control: tags-1 moreinfo Hello! Thanks for reporting! Unfortunately you report does not include anything useful for debugging. Please provide some log output from system and mariadb logs, what files you have, maybe something how your system is

Bug#931985: file: Experimental file breaks package creation at dh_shlibdeps stage due to file command

Package: file Version: 1:5.37-1 Severity: critical Justification: breaks unrelated software I know it is experimental but anyway it should be fixed and if you build pacakges, you cannot anymore. Tried on two pacakges, same error. dh_shlibdeps --dpkg-shlibdeps-params=--ignore-missing-info

Bug#919554: Indeed the chmod solves the problem

Thanks Michael. As a side note, I would like to point out that the 5.2.24 version of virtualbox in unstable is also set to 6755 but in this case it does not prevent to run correctly. I have no clue if it is also needed for 5.2.24, if not why not remove it or why it now breaks for 6.0.2.

Bug#919554: virtualbox-qt: Cannot launch Virtualbox

Package: virtualbox-qt Version: 6.0.2-dfsg-1~exp1 Severity: grave Justification: renders package unusable sh -x /usr/bin/VirtualBox + PATH=/usr/bin:/bin:/usr/sbin:/sbin + INSTALL_DIR=/usr/lib/virtualbox + [ ! -c /dev/vboxdrv ] + grep VBoxSVC + whoami + awk { print $1 } + ps -U valette +

Bug#917457: libilmbase23: 2.3.0-3 bumped so name without transition (breaks digikam, gimp, ...)

On 29/12/2018 08:11, Matteo F. Vescovi wrote: Andreas, I'll open a specific transition bug report for that, once I've tested all r-deps but not earlier. Its amazing how people think they can put garbarge in experimental and still expecting code to be tested and surprised to discover

Bug#917167: Bug #917167 in systemd marked as pending

On 27/12/2018 14:34, Michael Biebl wrote: Control: tag -1 pending Hello, Bug #917167 in systemd reported by you has been fixed in the Git repository and is awaiting an upload. You can see the commit message below and you can check the diff of the fix at: Thanks. Happily tested -2 version

Bug#917457: libilmbase23: 2.3.0-3 bumped so name without transition (breaks digikam, gimp, ...)

Package: libilmbase23 Version: 2.3.0-3 Severity: critical Justification: breaks unrelated software ldd /usr/bin/digikam | grep libIlmImf-2_2.so.23 libIlmImf-2_2.so.23 => not found ldd /usr/bin/digikam | grep 'not found' libImath-2_2.so.23 => not found libIlmImf-2_2.so.23

Bug#917167: systemd: 240 breaks kde (rakes ages to launch)

On 23/12/2018 19:15, Michael Biebl wrote: Thanks for the info. Very interesting read . Learned a few things today. -- eric

Bug#917167: systemd: 240 breaks kde (rakes ages to launch)

Please provide a verbose debug log with precise error messages. No time to do that. I already wasted two hours today... It was just to warn people that this version of udev should have gone to experimental or receive more testing before deploying it... You have now tree bugs on the same

Bug#917167: systemd: 240 breaks kde (rakes ages to launch)

On 23/12/2018 17:57, Michael Biebl wrote: Control: tags -1 + moreinfo Am 23.12.18 um 17:11 schrieb Eric Valette: Package: systemd Version: 240-1 Severity: critical Justification: breaks unrelated software After upgrading to 240 version, all my system started to take ages to boot. It seems

Bug#910879: print-manager: Prevent to start a kde session for all users

Package: print-manager Version: 4:18.04.1-1 Severity: critical Justification: breaks unrelated software Yesterday my daughther came with her laptop and said it was no more possible to log in. After entering the password, plasmashell was starting, then a strange message from okular and then a

Bug#908681: digikam, xsane are currently uninstaable

apt-get install libsane1 Reading package lists... Done Building dependency tree Reading state information... Done The following packages were automatically installed and are no longer required: enfuse libkf5calendarcore5abi1 libkf5mediawiki5 libkf5sane-data libpodofo0.9.5 libqtav1

Bug#907460: kdepim-runtime: /usr/bin/akonadi_imap_resource keeps crashing preventing kmail to work

Package: kdepim-runtime Version: 4:18.07.90-1 Severity: grave Justification: renders package unusable I manged to install expetimental kdepim today but when starting kmail I cannot acces to my ipmap account on exhange server (works with TB on same machine). I keep having crash traces in my out

Bug#894978: lightning: Unable to create event with experimental version (working before migration to 58)

On Fri, 27 Jul 2018 12:09:22 +0800 Carsten Schoenert wrote: Hello Eric, On Thu, Apr 05, 2018 at 09:35:01PM +0200, Eric Valette wrote: > Wanted to send an event as a reminder and was uable to vreate the > event either by clicking, or keyboard. how this looks like in recent v

Bug#902884: upowerd fails to start

Package: upower Version: 0.99.8-1 Severity: grave Justification: renders package unusable I had no upowerd daemon running on all my boxes: Jul 02 20:52:00 htpc1 systemd[1]: Starting Daemon for power management... Jul 02 20:52:01 htpc1 upowerd[1106]: /usr/lib/upower/upowerd: error while loading

Bug#900248: The proposed patch in nvidia conf fix DRI but many other problems remains

On 6/28/18 7:16 PM, Jiri Palecek wrote: Are you using xserver 1.20 from unstable or 1.19.6 from testing? I've had similar problems when I updated, and they went away when I downgraded xserver-xorg-core. 1.20 from unstable. -- eric

Bug#900248: The proposed patch in nvidia conf fix DRI but many other problems remains

Just a quick note to say that indeed the proposed patch to look for DRI modules at the right place is working. However, I have a bunch of other problems since driver update even with the fix in place: Sddm does not start. I get only a black

Bug#900789: 340xx 340.17 has been released with xorg 1.20 support

http://www.nvidia.com/Download/driverResults.aspx/135161/en-us

Bug#901185: me too

On 6/10/18 11:57 AM, Eric Valette wrote: On 6/10/18 11:35 AM, Andreas Metzler wrote: exports both dc_directives and any variable listed in dc_directives, i.e. any external command will see both ${dc_directives} and ${dc_eximconfig_configtype} et al. right but did you intent that? The rest

Bug#901185: me too

On 6/10/18 11:35 AM, Andreas Metzler wrote: exports both dc_directives and any variable listed in dc_directives, i.e. any external command will see both ${dc_directives} and ${dc_eximconfig_configtype} et al. right but did you intent that? The rest of the script seems not to use explicitly

Bug#901185: me too

On 6/10/18 10:59 AM, Eric Valette wrote: On 6/10/18 10:51 AM, Eric Valette wrote: 2) mv /etc/exim4/update-exim4.conf.conf /etc/exim4/update-exim4.conf.conf.old

Bug#901185: me too

On 6/10/18 10:51 AM, Eric Valette wrote: On 6/10/18 10:34 AM, Eric Valette wrote: line 330 :export dc_directives ${dc_directives} Shodul be export dc_directives=${dc_directives} as far as I understand. To fix I did : 1) use dash temporarilly 2) /etc/exim4/update-exim4

Bug#901185: me too

On 6/10/18 10:34 AM, Eric Valette wrote: line 330 :export dc_directives ${dc_directives} Shodul be export dc_directives=${dc_directives} as far as I understand. -- eric

Bug#901185: closed by Andreas Metzler (Re: Bug#901185: me too)

On 6/10/18 10:33 AM, Debian Bug Tracking System wrote: This is an automatic notification regarding your Bug report which was filed against the exim4-config package: But now how do we fix the problem? I will reopen until I have a fix. Putting dash as /bin/sh does fix anything BTW. -- eric

Bug#901185: me too

On 6/10/18 7:07 AM, Andreas Metzler wrote: On 2018-06-10 積丹尼 Dan Jacobson wrote: Oops. I mean just: Setting up exim4-config (4.91-5) ... /etc/exim4/update-exim4.conf.conf: line 26: dc_eximconfig_configtype: command not found Hello, Are you running bash (or other stuff) from experimental?

Bug#901185: exim4-config: fails to install

Package: exim4-config Version: 4.91-5 Severity: grave Justification: renders package unusable apt-get -f install Lecture des listes de paquets... Fait Construction de l'arbre des dépendances Lecture des informations d'état... Fait 0 mis à jour, 0 nouvellement installés, 0 à enlever et

Bug#900269: ifupdown: last version breaks upgrade

Package: ifupdown Version: 0.8.34 Severity: critical Justification: breaks the whole system Dear Maintainer, I now have been experiency three freeze during apt upgrade on three machines with the lattest update. When upgrading, you're stuck with the last message in console "setting up ifupdown"

Bug#894978: lightning: Unable to create event with experimental version (working before migration to 58)

Package: lightning Version: 1:58.0~b3-1 Severity: grave Justification: renders package unusable Wanted to send an event as a reminder and was uable to vreate the event either by clicking, or keyboard. -- System Information: Debian Release: buster/sid APT prefers unstable APT policy: (500,

Bug#892360: Bug #892360 in systemd marked as pending

On Sat, 10 Mar 2018 00:14:40 + aga...@siduction.org wrote: Bug #892360 in systemd reported by you has been fixed in the Git repository and is awaiting an upload. You can see the commit message below, and you can check the diff of the fix at: Confirmed fixed on my two machines. Thanks for

Bug#892360: systemd: No problem on my amd64 systems

On Thu, 08 Mar 2018 20:29:49 +0100 Diederik de Haas wrote: CONFIG_CGROUP_CPUACCT=y As the bug is triggered if this config is not set, no surprise. --eric

Bug#892360: systemd: Breaks also all my tested amd64 machines

On 3/8/18 7:26 PM, Eric Valette wrote: On 3/8/18 7:13 PM, Elimar Riesebieter wrote: I do have CONFIG_CGROUP_CPUACCT=y on my amd64 kernels and systemd runs fine... Ok. So still in line with hypothesis... ATM I am building a x86 with CONFIG_CGROUP_CPUACCT=not set. Let's wait and see

Bug#892360: systemd: Breaks also all my tested amd64 machines

On 3/8/18 7:13 PM, Elimar Riesebieter wrote: I do have CONFIG_CGROUP_CPUACCT=y on my amd64 kernels and systemd runs fine... Ok. So still in line with hypothesis... ATM I am building a x86 with CONFIG_CGROUP_CPUACCT=not set. Let's wait and see And I'm rebuilding my failing kernel

Bug#892360: systemd: Breaks also all my tested amd64 machines

On 3/8/18 7:03 PM, Elimar Riesebieter wrote: * Michael Biebl [2018-03-08 18:54 +0100]: [...] Can you check your custom kernel config, specifically if CONFIG_CGROUP_CPUACCT=y I do have CONFIG_CGROUP_CPUACCT=y Well, but why does 237 works with the very same kernel? In my

Bug#892360: systemd: Breaks also all my tested amd64 machines

Can you check your custom kernel config, specifically if CONFIG_CGROUP_CPUACCT=y Probably easiest if you just use grep grep CGROUP /boot/config-$(uname -r) Done in another private email. Can copy here: diff config-4.14.0-3-amd64 config-4.14.23 | grep CGROUP < CONFIG_BLK_CGROUP=y < #

Bug#892360: same here on amd64 system

I also have a system crash at init, witha sigsegv that points in libc. I use unstable today (8 march). --eric

Bug#890067: libgl1-mesa-dri: breaks kde experimental (sddm or sddm-greeter crash, ksplashscreen crash)

On 2/12/18 10:36 AM, Timo Aaltonen wrote: On 10.02.2018 20:57, Eric Valette wrote: Package: libgl1-mesa-dri Version: 18.0.0~rc2-1 Severity: critical Justification: breaks unrelated software After sucesfully upgrading this machine with experimental kde; libc6, mesa, I went down and upgraded

Bug#889804: flashplugin-nonfree: Does not work anymore because adobe site have moved to https and script does not hanlde redirect

Package: flashplugin-nonfree Version: 1:3.7 Severity: grave Justification: renders package unusable update-flashplugin-nonfree --status Flash Player version installed on this system : 28.0.0.161 link to Adobe Flash Player not found on http://www.adobe.com/ at get-upstream-version.pl line 58.

Bug#887078: Bug#887886: libc6 from experimental makes vlc crash (even after rebuilding from source)

On 21/01/2018 17:16, Aurelien Jarno wrote: control: forcemerge -1 887078 On 2018-01-21 14:12, Eric Valette wrote: Package: libc6 Version: 2.26.9000+20180108.401311cf-0experimental0 Severity: critical Justification: breaks unrelated software launching vlc crash immediately with sigsegv

Bug#887886: libc6 from experimental makes vlc crash (even after rebuilding from source)

Package: libc6 Version: 2.26.9000+20180108.401311cf-0experimental0 Severity: critical Justification: breaks unrelated software launching vlc crash immediately with sigsegv. Downgrading to unstable makes it work again. -- System Information: Debian Release: buster/sid APT prefers unstable APT

Bug#886322: libkf5kdelibs4support-dev: Should libkf5kdelibs4support-dev still depend on libssl1.0-dev

On 01/04/2018 03:13 PM, Pino Toscano wrote: Firrst thanks for taking time to respond to my questions... No, there are parts of kdelibs4support that use OpenSSL, but because of its obnoxious license then it is not common for code using OpenSSL to link directly to it. It do not follow the idea

Bug#886322: libkf5kdelibs4support-dev: Should libkf5kdelibs4support-dev still depend on libssl1.0-dev

On 01/04/2018 02:25 PM, Pino Toscano wrote: On giovedì 4 gennaio 2018 14:17:59 CET Eric Valette wrote: this is a duplicate of bug #850888, since the dependency in the -dev package depends on which libssl was used for the build. When kdelibs4support is ported to libssl1.1, then the dependency

Bug#886322: libkf5kdelibs4support-dev: Should libkf5kdelibs4support-dev still depend on libssl1.0-dev

On 01/04/2018 02:13 PM, Pino Toscano wrote: reassign 886322 kdelibs4support/5.37.0-2 forcemerge 850888 886322 thanks Hi, this is a duplicate of bug #850888, since the dependency in the -dev package depends on which libssl was used for the build. When kdelibs4support is ported to libssl1.1,

Bug#850888: Today unstable upgrade prevent me to build anything requiring sll 1.1

Please fix the dependency. So far I was using libssl-dev and kde -dev packages without problems. -- eric

Bug#884257: digikam: Experimental version no more installable

Package: digikam Version: 4:5.7.0-2 Severity: grave Justification: renders package unusable apt-get -t experimental install digikam-private-libs Reading package lists... Done Building dependency tree Reading state information... Done Some packages could not be installed. This may mean that

Bug#881990: Same here

Just to confirm... -- eric

Bug#878807: wpasupplicant: Please port the security fixes to 2.6 also

Package: wpasupplicant Version: 2:2.6-4 Severity: grave Tags: upstream security Justification: user security hole Upstream patches patches for 2.6 are here http://w1.fi/security/2017-1/ -- System Information: Debian Release: buster/sid APT prefers unstable APT policy: (500, 'unstable'), (1,

Bug#878028: libopencv-imgcodecs3.2: Not anymore installable due to gdal-abi-2-2-1 dependency

Package: libopencv-imgcodecs3.2 Severity: grave Justification: renders package unusable gdal-abi-2-2-1 is no more availble because libgdal2 has been updated to a new version. -- System Information: Debian Release: buster/sid APT prefers unstable APT policy: (500, 'unstable'), (1,

Bug#876070: My bad : the var file system was indeed broken. Bug can be closed

I never saw this message before either... And creating the failing file manually was possible. But a e2fsck -f -y DEV(/var) was indeed necessary. And after that package did install correctly. -- eric

Bug#876070: libavahi-core7: Does not install

Package: libavahi-core7 Version: 0.7-1 Severity: grave Justification: renders package unusable apt-get -f install Reading package lists... Done Building dependency tree Reading state information... Done The following additional packages will be installed: libavahi-core7 The following

  1   2   3   4   >