Bug#887576: mupen64plus-qt FTBFS with libquazip5-headers 0.7.3-3
This was the change I was waiting for to update the header location since almost every other distribution places them at quazip5. I've released version 1.11 to fix this issue. Could someone update the package? Thanks!
Bug#887530: cen64-qt FTBFS with libquazip5-headers 0.7.3-3
On Wed, 24 Jan 2018 23:29:33 +0200 Juhani Numminen
wrote:
John Paul Adrian Glaubitz kirjoitti 24.01.2018 klo 23:06:
> On 01/24/2018 09:42 PM, Juhani Numminen wrote:
>> Fixed in this upstream commit:
>>
https://github.com/dh4/cen64-qt/commit/2592c4f977a798e9787f9f50f5d1d334db9ad94d
>
> Thanks.
>
> If you could release a new upstream release. I could go ahead and package that
> version. Then I wouldn't have to carry the patch in the Debian package.
To clear a possible misunderstanding, I am not the upstream, rather I was
connecting upstream fixes to FTBFS bugs in Debian ("Bug squasher view" at
https://udd.debian.org/bugs/).
In the case of this bug, I reported the problem for mupen64plus-qt first
https://github.com/dh4/mupen64plus-qt/issues/33#issuecomment-359922529
and then the upstream developer fixed both mupen64plus-qt and cen64-qt.
Cheers,
Juhani
I've released a new upstream version incorporating the fix for this bug:
https://github.com/dh4/cen64-qt/releases/tag/20180125-alpha
- Dan
Bug#538396: libsqlite3 on sparc problem
Hi, Is is possible to reproduce the crash with an unoptimized build that includes debugging symbols? If so, can you post the output of [bt full] after the SIGBUS occurs. It's likely we could find and fix the problem with this information. Thanks, Dan Kennedy. -- To UNSUBSCRIBE, email to debian-bugs-rc-requ...@lists.debian.org with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org
Bug#843530: docker.io: docker broken: oci runtime error: could not synchronize with container process
For anyone needing a workaround. This bug also hit me this morning. I looked through a bit of the code in runc/libcontainer and it looks like it is caused by a cgroup issue. I took an educated guess and downgraded systemd from 232-2 to 231-9 (which is still available in stretch) and now docker works again.
Bug#673921: guake: fails to start with AttributeError: object has no attribute "set_alternate_screen_scroll"
Package: guake Version: 0.4.2-9 Severity: grave Justification: renders package unusable Dear Maintainer, When attempting to start guake, I get the following error message: user@system:~$ guake Traceback (most recent call last): File "/usr/lib/guake/guake.py", line 1357, in if not main(): File "/usr/lib/guake/guake.py", line 1300, in main instance = Guake() File "/usr/lib/guake/guake.py", line 620, in __init__ self.add_tab() File "/usr/lib/guake/guake.py", line 1128, in add_tab box.terminal.set_alternate_screen_scroll(True) AttributeError: 'GuakeTerminal' object has no attribute 'set_alternate_screen_scroll' user@system:~$ -- System Information: Debian Release: wheezy/sid APT prefers unstable APT policy: (400, 'unstable'), (300, 'experimental') Architecture: amd64 (x86_64) Kernel: Linux 3.2.0-2-amd64 (SMP w/2 CPU cores) Locale: LANG=en_US.utf8, LC_CTYPE=en_US.utf8 (charmap=UTF-8) Shell: /bin/sh linked to /bin/dash Versions of packages guake depends on: ii gconf2 3.2.5-1 ii libatk1.0-0 2.4.0-2 ii libc62.13-32 ii libcairo21.12.2-2 ii libfontconfig1 2.9.0-5 ii libfreetype6 2.4.9-1 ii libgdk-pixbuf2.0-0 2.26.1-1 ii libglib2.0-0 2.32.3-1 ii libgtk2.0-0 2.24.10-1 ii libpango1.0-01.30.0-1 ii libpython2.7 2.7.3~rc2-2.1 ii libx11-6 2:1.4.99.901-2 ii notification-daemon 0.7.4-1 ii python 2.7.2-10 ii python-dbus 1.1.0-1 ii python-gconf 2.28.1+dfsg-1 ii python-glade22.24.0-3 ii python-notify0.1.1-3 ii python-vte 1:0.28.2-4 ii python2.72.7.3~rc2-2.1 guake recommends no packages. guake suggests no packages. -- no debconf information -- To UNSUBSCRIBE, email to debian-bugs-rc-requ...@lists.debian.org with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org
Bug#673922: guake fails to load with set_alternate_screen_scroll attribute error
Package: guake Version: 0.4.2-9 Justification: renders package unusable Severity: grave Hello, guake fails to load on my sid system with the following error: dan@system:~$ guake Traceback (most recent call last): File "/usr/lib/guake/guake.py", line 1357, in if not main(): File "/usr/lib/guake/guake.py", line 1300, in main instance = Guake() File "/usr/lib/guake/guake.py", line 620, in __init__ self.add_tab() File "/usr/lib/guake/guake.py", line 1128, in add_tab box.terminal.set_alternate_screen_scroll(True) AttributeError: 'GuakeTerminal' object has no attribute 'set_alternate_screen_scroll' -- System Information: Debian Release: wheezy/sid APT prefers unstable APT policy: (400, 'unstable'), (300, 'experimental') Architecture: amd64 (x86_64) Kernel: Linux 3.2.0-2-amd64 (SMP w/2 CPU cores) Locale: LANG=en_US.utf8, LC_CTYPE=en_US.utf8 (charmap=UTF-8) Shell: /bin/sh linked to /bin/dash Versions of packages guake depends on: ii gconf2 3.2.5-1 ii libatk1.0-0 2.4.0-2 ii libc62.13-32 ii libcairo21.12.2-2 ii libfontconfig1 2.9.0-5 ii libfreetype6 2.4.9-1 ii libgdk-pixbuf2.0-0 2.26.1-1 ii libglib2.0-0 2.32.3-1 ii libgtk2.0-0 2.24.10-1 ii libpango1.0-01.30.0-1 ii libpython2.7 2.7.3~rc2-2.1 ii libx11-6 2:1.4.99.901-2 ii notification-daemon 0.7.4-1 ii python 2.7.2-10 ii python-dbus 1.1.0-1 ii python-gconf 2.28.1+dfsg-1 ii python-glade22.24.0-3 ii python-notify0.1.1-3 ii python-vte 1:0.28.2-4 ii python2.72.7.3~rc2-2.1 guake recommends no packages. guake suggests no packages. -- no debconf information -- To UNSUBSCRIBE, email to debian-bugs-rc-requ...@lists.debian.org with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org
Bug#294867: base: de4x5.ko generates endless loop of errors with phobos p430tx
Package: base Severity: critical Justification: breaks the whole system Debian autodetects my 4 port Phobos P430TX and attempts to use the de4x5.ko driver. When the boot process gets to initializeing the card it outputs an endless loop of this message, and won't finish booting: bad media code [17] detected in SROM I had to remove the card to get it the machine to boot. I corrected the problem by renaming de4x5.ko to de4x5.off. Then on next boot it defaulted to useing tulip.ko and so far everything appears to work ok. I tried the card in 2 different debian machines, same problem. I tried both the current 2.6 and 2.4 kernel, same problem. -- System Information: Debian Release: 3.1 APT prefers testing APT policy: (500, 'testing') Architecture: i386 (i686) Kernel: Linux 2.6.8-1-386 Locale: LANG=en_US, LC_CTYPE=en_US (charmap=ISO-8859-1) -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
Bug#606350: sasl2-bin: "Too many open files" error with PAM - recovery with saslauthd restart
On 08/12/10 09:20 -0400, dteed wrote: This is working fine - users can authenticate against Active Directory when sending email over secure ports 465 and 587 on Postfix. Once every two weeks or so, saslauthd requires a restart to fix a failure to authenticate. Nothing else needs to be touched to remedy the failure. When the failure appears, this is observed in the auth.log: Dec 5 15:45:22 myhostname saslauthd[32586]: PAM unable to dlopen(/lib/security/pam_winbind.so): /lib/security/pam_winbind.so: cannot open shared object file: Too many open files Dec 5 15:45:22 myhostname saslauthd[32586]: PAM adding faulty module: /lib/security/pam_winbind.so Dec 5 15:45:22 myhostname saslauthd[32586]: PAM unable to dlopen(/lib/security/pam_deny.so): /lib/security/pam_deny.so: cannot open shared object file: Too many open files Dec 5 15:45:22 myhostname saslauthd[32586]: PAM adding faulty module: /lib/security/pam_deny.so Dec 5 15:45:22 myhostname saslauthd[32586]: PAM _pam_load_conf_file: unable to open /etc/pam.d/common-auth Dec 5 15:45:22 myhostname saslauthd[32586]: PAM error loading (null) Dec 5 15:45:22 myhostname saslauthd[32586]: PAM _pam_init_handlers: error reading /etc/pam.d/other Dec 5 15:45:22 myhostname saslauthd[32586]: PAM _pam_init_handlers: [Critical error - immediate abort] Dec 5 15:45:22 myhostname saslauthd[32586]: PAM error reading PAM configuration file Dec 5 15:45:22 myhostname saslauthd[32586]: PAM pam_start: failed to initialize handlers Dec 5 15:45:22 myhostname saslauthd[32586]: DEBUG: auth_pam: pam_start failed: Critical error - immediate abort Dec 5 15:45:22 myhostname saslauthd[32586]: do_auth : auth failure: [user=dteed] [service=smtp] [realm=] [mech=pam] [reason=PAM start error] Dec 5 15:45:32 myhostname saslauthd[32586]: server_exit : master exited: 32586 Dec 5 15:45:32 myhostname saslauthd[1696]: detach_tty : master pid is: 1696 Dec 5 15:45:32 myhostname saslauthd[1696]: ipc_init : listening on socket: /var/run/saslauthd/mux I'd guess that would be caused by a file descriptor leak, either in saslauthd itself or in one of your PAM modules. Can you monitor /proc//fd/ to see if you can find out what type of file descriptors are being left open? -- Dan White -- To UNSUBSCRIBE, email to debian-bugs-rc-requ...@lists.debian.org with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org
Bug#606350: sasl2-bin: "Too many open files" error with PAM - recovery with saslauthd restart
On 08/12/10 15:33 -0400, D G Teed wrote: Here is what one of the directories looked like: ls -l 15950/fd total 0 lrwx-- 1 root root 64 Dec 8 13:52 0 -> /dev/null lrwx-- 1 root root 64 Dec 8 13:52 1 -> /dev/null lrwx-- 1 root root 64 Dec 7 15:47 10 -> socket:[38109596] lrwx-- 1 root root 64 Dec 7 15:47 11 -> socket:[38112677] lrwx-- 1 root root 64 Dec 8 13:52 12 -> socket:[38129166] lrwx-- 1 root root 64 Dec 8 13:52 13 -> socket:[38177341] lrwx-- 1 root root 64 Dec 8 13:52 14 -> socket:[38198508] lrwx-- 1 root root 64 Dec 8 13:52 15 -> socket:[38256709] lrwx-- 1 root root 64 Dec 8 13:52 16 -> socket:[38307912] lrwx-- 1 root root 64 Dec 8 13:52 17 -> socket:[38351349] lrwx-- 1 root root 64 Dec 8 13:52 18 -> socket:[38378460] Try doing a 'netstat -e' and see if you can match some of those sockets up with a connection, and see if you can determine what it's being used for, and what connection state it's in. I'm hoping you can tie the down to a particular type of connection, say, your pam_winbind attempts. If that's the case, then the problem might be due to a bug in that specific pam module, or could be due to a bug in the way saslauthd uses pam. -- Dan White -- To UNSUBSCRIBE, email to debian-bugs-rc-requ...@lists.debian.org with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org
Bug#699124: [PATCH] Resolve FTBFS based on new group data
On Sun, Jan 27, 2013 at 4:56 PM, gregor herrmann wrote: > Dan, you write "patches from upstream": Out of curiosity, can you > point us to the source, please? I don't seen anything new for > Business-ISBN on the CPAN or on github. > Apologies, I should have noted them in my git commit messages. They are: https://github.com/briandfoy/business--isbn/commit/5df30504329b1402c6aa31ebd7564a194ca0d88e and https://github.com/briandfoy/business--isbn/commit/a3a6f1dafa5fa74dacd5bdff28d472a80d7e99e3
Bug#1022025: Upstream Reports
Yeah, I tried to apply it, but I had that same problem where I managed to compile the .debs, but got a bunch of errors installing them with a black screen at the end of the test. I use DKMS for nvidia and openrazer, and that's been posing problems, which you'll see below. In addition, there are dependency issues that dpkg and apt both complain about. Here's what I did (I'm including console output when relevant to spare you the full output of a kernel build job): $ apt source -t bullseye-security linux $ sudo apt -t bullseye build-dep linux $ cd linux-5.10.149 $ debian/bin/test-patches -j14 /home/dan/Downloads/0001-drm-amdgpu-fix-sdma-doorbell-init-ordering-on-APUs.patch [Kernel builds without a problem as far as I can tell] $ cd .. $ ls linux-5.10.149 linux-headers-5.10.0-19-amd64_5.10.149-1a~test_amd64.deb linux_5.10.149-1.debian.tar.xz linux-image-5.10.0-19-amd64-dbg_5.10.149-1a~test_amd64.deb linux_5.10.149-1.dsc linux-image-5.10.0-19-amd64-unsigned_5.10.149-1a~test_amd64.deb linux_5.10.149.orig.tar.xz linux-image-amd64-dbg_5.10.149-1a~test_amd64.deb $ sudo apt install ./linux-headers-5.10.0-19-amd64_5.10.149-1a~test_amd64.deb ./linux-image-5.10.0-19-amd64-unsigned_5.10.149-1a~test_amd64.deb Reading package lists... Done Building dependency tree... Done Reading state information... Done Note, selecting 'linux-headers-5.10.0-19-amd64' instead of './linux-headers-5.10.0-19-amd64_5.10.149-1a~test_amd64.deb' Note, selecting 'linux-image-5.10.0-19-amd64-unsigned' instead of './linux-image-5.10.0-19-amd64-unsigned_5.10.149-1a~test_amd64.deb' Some packages could not be installed. This may mean that you have requested an impossible situation or if you are using the unstable distribution that some required packages have not yet been created or been moved out of Incoming. The following information may help to resolve the situation: The following packages have unmet dependencies: linux-headers-5.10.0-19-amd64 : Depends: linux-headers-5.10.0-19-common (= 5.10.149-1a~test) but 5.10.149-1 is to be installed Depends: linux-kbuild-5.10 (>= 5.10.149-1a~test) E: Unable to correct problems, you have held broken packages. $ sudo dpkg -i ./linux-headers-5.10.0-19-amd64_5.10.149-1a~test_amd64.deb ./linux-image-5.10.0-19-amd64-unsigned_5.10.149-1a~test_amd64.deb Preparing to unpack .../linux-headers-5.10.0-19-amd64_5.10.149-1a~test_amd64.deb ... Unpacking linux-headers-5.10.0-19-amd64 (5.10.149-1a~test) over (5.10.149-1) ... Selecting previously unselected package linux-image-5.10.0-19-amd64-unsigned. dpkg: considering removing linux-image-5.10.0-19-amd64 in favour of linux-image-5.10.0-19-amd64-unsigned ... dpkg: no, cannot proceed with removal of linux-image-5.10.0-19-amd64 (--auto-deconfigure will help): linux-image-amd64 depends on linux-image-5.10.0-19-amd64 (= 5.10.149-1) linux-image-5.10.0-19-amd64 is to be removed. dpkg: regarding .../linux-image-5.10.0-19-amd64-unsigned_5.10.149-1a~test_amd64.deb containing linux-image-5.10.0-19-amd64-unsigned: linux-image-5.10.0-19-amd64-unsigned conflicts with linux-image-5.10.0-19-amd64 linux-image-5.10.0-19-amd64 (version 5.10.149-1) is present and installed. dpkg: error processing archive ./linux-image-5.10.0-19-amd64-unsigned_5.10.149-1a~test_amd64.deb (--install): conflicting packages - not installing linux-image-5.10.0-19-amd64-unsigned dpkg: dependency problems prevent configuration of linux-headers-5.10.0-19-amd64: linux-headers-5.10.0-19-amd64 depends on linux-headers-5.10.0-19-common (= 5.10.149-1a~test); however: Version of linux-headers-5.10.0-19-common on system is 5.10.149-1. linux-headers-5.10.0-19-amd64 depends on linux-kbuild-5.10 (>= 5.10.149-1a~test); however: Version of linux-kbuild-5.10 on system is 5.10.149-1. dpkg: error processing package linux-headers-5.10.0-19-amd64 (--install): dependency problems - leaving unconfigured Errors were encountered while processing: ./linux-image-5.10.0-19-amd64-unsigned_5.10.149-1a~test_amd64.deb linux-headers-5.10.0-19-amd64 $ sudo apt remove linux-image-amd64 linux-headers-amd64 linux-headers-5.10.0-19-amd64 linux-headers-5.10.0-19-common linux-image-5.10.0-19-amd64 Reading package lists... Done Building dependency tree... Done Reading state information... Done The following packages will be REMOVED: linux-headers-5.10.0-19-amd64 linux-headers-5.10.0-19-common linux-headers-amd64 linux-image-5.10.0-19-amd64 linux-image-amd64 0 upgraded, 0 newly installed, 5 to remove and 0 not upgraded. 1 not fully installed or removed. After this operation, 376 MB disk space will be freed. Do you want to continue? [Y/n] (Reading database ... 546461 files and directories currently installed.) Removing linux-headers-amd64 (5.10.149-1) ... Removing linux-headers-5.10.0-19-amd64 (5.10.149-1a~test) ... Removing linux-headers-5.10.0-19-common (5.10.149-1) ... Remov
Bug#1022025: Upstream Reports
Hi Diederik, Great news! I'm glad I did it correctly. On 10/20/22 11:32 AM, Diederik de Haas wrote: > Hi Dan, > > On Thursday, 20 October 2022 17:26:42 CEST Dan Coleman wrote: >> Yeah, I tried to apply it, but I had that same problem where I managed to >> compile the .debs, but got a bunch of errors installing them with a black >> screen at the end of the test. I use DKMS for nvidia and openrazer, and >> that's been posing problems, which you'll see below. In addition, there are >> dependency issues that dpkg and apt both complain about. > I see that you, Salvatore and the upstream maintainer are in discussion in the > upstream repo, so I'll leave that part in their capable hands :-) > > As for your build+install attempts, it looks like you did everything correct! > > Apparently "test-patches" does not build a 'headers-common' package and > therefor installing the headers failed which in turn made DKMS fail. That seems like less-than-ideal behavior for test-patches. Is that a bug that would benefit from being reported? > I understand that you'd want that for a complete functioning system, but for > testing this particular issue/patch it is sufficient. Once the proper fix is > validated, all the kernel (related) packages will be rebuild and then the > other things like DKMS should work again too. > Unfortunately it turned out that just this patch wasn't sufficient to fix the > issue as Alex Deucher indicated. How to proceed with that, I'll leave that up > to Alex/Salvatore :-) > > You also removed the normal (i.e. Debian's) kernel meta package (linux-image- > amd64) which prevented the installation of your patched kernel. After that the > installation of your patched kernel succeeded. And you rebooted into that. > Earlier you indicated you had doubts whether you did it correctly and therefor > whether you were actually testing the patch and I'm quite sure you did (at > least this time based on the output you shared). > > HTH, >Diederik
Bug#1022025: two reverts required, submitted to stable review list
Hey, > On Thursday, 20 October 2022 22:10:27 CEST Salvatore Bonaccorso wrote: > > So there are two patches who need to be reverted: > > > > https://lore.kernel.org/stable/20221020153857.565160-1-alexander.deuc...@amd.com/ > > https://lore.kernel.org/stable/20221020153857.565160-2-alexander.deuc...@amd.com/ How do I apply these patches to see if they work for me? Thus far in this bug, I've just seen .patch files.
Bug#1022025: two reverts required, submitted to stable review list
Thanks for sending them! No need for the binary packages, I mostly just want to see if I can successfully apply patches and get a working kernel. On 10/21/22 08:42 AM, Salvatore Bonaccorso wrote: > Hi, > > On Fri, Oct 21, 2022 at 12:55:09PM +, Dan Coleman wrote: >> Hey, >> >> > On Thursday, 20 October 2022 22:10:27 CEST Salvatore Bonaccorso wrote: >> >> > > So there are two patches who need to be reverted: >> > > >> > > >> https://lore.kernel.org/stable/20221020153857.565160-1-alexander.deuc...@amd.com/ >> > > >> https://lore.kernel.org/stable/20221020153857.565160-2-alexander.deuc...@amd.com/ >> >> >> How do I apply these patches to see if they work for me? Thus far in >> this bug, I've just seen .patch files. > Here are those as patches. > > If you trust unsigned binary packages build I would put somehwere I > can provide you those with those two applied. But again, after testing > make sure you reinstall the meta package and go back to the -18 > version. > > Regards, > Salvatore
Bug#1022025: two reverts required, submitted to stable review list
On Fri, 21 Oct 2022 13:51:48 + Dan Coleman wrote: > Thanks for sending them! No need for the binary packages, I mostly just want > to see if I can successfully apply patches and get a working kernel. The patches work! I booted into the new kernel just fine.
Bug#1022268: linux-image-5.10.0-19-amd64: Boot failure under xen as dom0
Package: src:linux Version: 5.10.149-1 Severity: critical Justification: breaks the whole system X-Debbugs-Cc: mar...@mydatex.cz Dear Maintainer, after upgrade kernel from 5.10.0-18 to 5.10.0-19 system is unbootable. Problem is similar this bug https://bugzilla.kernel.org/show_bug.cgi?id=209177. I try recommended solution mpt3sas.max_queue_depth=1 but nothing helps. Without xen system boots. With xen I must use 5.10.0-18. Regards Dan -- Package-specific info: ** Kernel log: boot messages should be attached ** Model information sys_vendor: Supermicro product_name: Super Server product_version: 0123456789 chassis_vendor: Supermicro chassis_version: 0123456789 bios_vendor: American Megatrends Inc. bios_version: 2.2a board_vendor: Supermicro board_name: X11SSL-F board_version: 1.01 ** Network interface configuration: *** /etc/network/interfaces: source /etc/network/interfaces.d/* auto lo iface lo inet loopback iface eno2 inet manual auto xenbr1 iface xenbr1 inet static address 192.168.2.2 netmask 255.255.255.248 gateway 192.168.2.1 bridge_ports eno2 bridge_stp off # disable Spanning Tree Protocol bridge_waitport 0 # no delay before a port becomes available bridge_fd 0 # no forwarding delay iface eno1 inet manual auto xenbr0 iface xenbr0 inet manual bridge_ports eno1 bridge_stp off # disable Spanning Tree Protocol bridge_waitport 0 # no delay before a port becomes available bridge_fd 0 # no forwarding delay iface enp2s0 inet manual auto xenbr2 iface xenbr2 inet manual bridge_ports enp2s0 bridge_stp off # disable Spanning Tree Protocol bridge_waitport 0 # no delay before a port becomes available bridge_fd 0 # no forwarding delay ** PCI devices: 00:00.0 Host bridge [0600]: Intel Corporation Xeon E3-1200 v6/7th Gen Core Processor Host Bridge/DRAM Registers [8086:5918] (rev 05) Subsystem: Super Micro Computer Inc Xeon E3-1200 v6/7th Gen Core Processor Host Bridge/DRAM Registers [15d9:089a] Control: I/O- Mem+ BusMaster+ SpecCycle- MemWINV- VGASnoop- ParErr- Stepping- SERR- FastB2B- DisINTx- Status: Cap+ 66MHz- UDF- FastB2B+ ParErr- DEVSEL=fast >TAbort- SERR- Kernel driver in use: ie31200_edac Kernel modules: ie31200_edac 00:01.0 PCI bridge [0604]: Intel Corporation 6th-10th Gen Core Processor PCIe Controller (x16) [8086:1901] (rev 05) (prog-if 00 [Normal decode]) Control: I/O+ Mem+ BusMaster+ SpecCycle- MemWINV- VGASnoop- ParErr- Stepping- SERR- FastB2B- DisINTx+ Status: Cap+ 66MHz- UDF- FastB2B- ParErr- DEVSEL=fast >TAbort- SERR- TAbort- Reset- FastB2B- PriDiscTmr- SecDiscTmr- DiscTmrStat- DiscTmrSERREn- Capabilities: Kernel driver in use: pcieport 00:13.0 Non-VGA unclassified device []: Intel Corporation 100 Series/C230 Series Chipset Family Integrated Sensor Hub [8086:a135] (rev 31) Subsystem: Super Micro Computer Inc 100 Series/C230 Series Chipset Family Integrated Sensor Hub [15d9:089a] Control: I/O- Mem+ BusMaster+ SpecCycle- MemWINV- VGASnoop- ParErr- Stepping- SERR- FastB2B- DisINTx- Status: Cap+ 66MHz- UDF- FastB2B- ParErr- DEVSEL=fast >TAbort- SERR- Kernel modules: intel_ish_ipc 00:14.0 USB controller [0c03]: Intel Corporation 100 Series/C230 Series Chipset Family USB 3.0 xHCI Controller [8086:a12f] (rev 31) (prog-if 30 [XHCI]) Subsystem: Super Micro Computer Inc 100 Series/C230 Series Chipset Family USB 3.0 xHCI Controller [15d9:089a] Control: I/O- Mem+ BusMaster+ SpecCycle- MemWINV- VGASnoop- ParErr- Stepping- SERR- FastB2B- DisINTx+ Status: Cap+ 66MHz- UDF- FastB2B+ ParErr- DEVSEL=medium >TAbort- SERR- Kernel driver in use: xhci_hcd Kernel modules: xhci_pci 00:14.2 Signal processing controller [1180]: Intel Corporation 100 Series/C230 Series Chipset Family Thermal Subsystem [8086:a131] (rev 31) Subsystem: Super Micro Computer Inc 100 Series/C230 Series Chipset Family Thermal Subsystem [15d9:089a] Control: I/O- Mem+ BusMaster+ SpecCycle- MemWINV- VGASnoop- ParErr- Stepping- SERR- FastB2B- DisINTx- Status: Cap+ 66MHz- UDF- FastB2B- ParErr- DEVSEL=fast >TAbort- SERR- Kernel driver in use: intel_pch_thermal Kernel modules: intel_pch_thermal 00:16.0 Communication controller [0780]: Intel Corporation 100 Series/C230 Series Chipset Family MEI Controller #1 [8086:a13a] (rev 31) Subsystem: Super Micro Computer Inc 100 Series/C230 Series Chipset Family MEI Controller [15d9:089a] Control: I/O- Mem+ BusMaster+ SpecCycle- MemWINV- VGASnoop- ParErr- Stepping- SERR- FastB2B- DisINTx- Status: Cap+ 66MHz- UDF- FastB2B- ParErr- DEVSEL=fast >TAbort- SERR- Kernel modules: mei_me 00:17.0 SATA controller [0106]: Intel Corp
Bug#1022025: Bug#1022051: Acknowledgement (linux-image-5.10.0-19-amd64: no boot possible)
Revised kernel works for me as well! Thanks everyone for the rapid response.
Bug#1031596: London-Tokyo vs. Tokyo-London distance much different!!
Package: libgeo-calc-perl Version: 0.12-1 Severity: grave File: /usr/share/doc/libgeo-calc-perl Forwarded: https://rt.cpan.org/Public/Bug/Display.html?id=146578 Regarding Geo::Calc version 0.12, there is something very wrong. The distance from London to Tokyo, 11314595.851556 is different that from Tokyo to London, 8256133.168096 !! See https://rt.cpan.org/Public/Bug/Display.html?id=146578 . There is no activity on the many years of reports there. Are you sure this package should be in Debian?
Bug#1030190: mplayer uninstallable
Package: mplayer Version: 2:1.4+ds1-3+b2 Severity: critical The following packages have unmet dependencies: mplayer : Depends: libavcodec58 (>= 7:4.4) which is a virtual package and is not provided by any available package Depends: libavformat58 (>= 7:4.4) which is a virtual package and is not provided by any available package Depends: libavutil56 (>= 7:4.4) which is a virtual package and is not provided by any available package Depends: libpostproc55 (>= 7:4.4) which is a virtual package and is not provided by any available package Depends: libswresample3 (>= 7:4.4) which is a virtual package and is not provided by any available package Depends: libswscale5 (>= 7:4.4) which is a virtual package and is not provided by any available package The following actions will resolve these dependencies: Keep the following packages at their current version: 1) mplayer [Not Installed] *** No more solutions available *** In sources.list I have deb http://.../debian/ unstable main contrib non-free non-free-firmware
Bug#1030190: mplayer uninstallable
Also: The following packages have unmet dependencies: libavformat58 : Depends: libsrt1.4-gnutls (>= 1.4.4) which is a virtual package and is not provided by any available package
Bug#958853: Fix
Upstream has now moved away from Bazel: https://github.com/ankitects/anki/commit/5e0a761b875fff4c9e4b202c08bd740c7bb37763 The new build system uses cargo and ninja. It'll still be a substantial job to package this for Debian, but hopefully more feasible than before.
Bug#882806: xen-hypervisor-4.8-amd64: After upgrade to stretch all Windows VM crash on boot or hang on boot
Package: src:xen Version: 4.8.1-1+deb9u3 Severity: critical Justification: breaks the whole system This problem is CPU E5420 and Xem hypervisor related. The same Windows VM boot on another Xen 4.6 on another machine. And also boot on Xen 4.8 on another machine. On this machine with Debian Jessie works without problem. After dist-upgrade all Win VMs stop working. I test fresh install but nothing helps. -- System Information: Debian Release: 9.2 APT prefers proposed-updates APT policy: (500, 'proposed-updates'), (500, 'stable') Architecture: amd64 (x86_64) Kernel: Linux 4.9.0-4-amd64 (SMP w/1 CPU core) Locale: LANG=cs_CZ.UTF-8, LC_CTYPE=cs_CZ.UTF-8 (charmap=UTF-8), LANGUAGE=cs_CZ.UTF-8 (charmap=UTF-8) Shell: /bin/sh linked to /bin/dash Init: systemd (via /run/systemd/system) xen-hypervisor-4.8-amd64 depends on no packages. Versions of packages xen-hypervisor-4.8-amd64 recommends: ii xen-utils-4.8 4.8.1-1+deb9u3 xen-hypervisor-4.8-amd64 suggests no packages. -- no debconf information
Bug#950172: gpscorrelate ftbfs with libexiv2-27
The problem is also fixed in the upstream ver. 2.0 (upstream has moved to https://github.com/dfandrich/gpscorrelate).
Bug#868202: Python 3.7 incompatibility
I've upgraded to Python 3.7, and this python3-trollinus dependency is blocking me from installing python3-qtile. The python3.7 package "breaks" python3-trollinus (i.e. prevents python3-trollinus from installing, via https://salsa.debian.org/cpython-team/python3/blob/python3.7/debian/py37-breaks.Debian). To fix this, I think it'd be fine to bump up the required Python version of this package from 3.3 to 3.4. The Qtile docs ( http://docs.qtile.org/en/latest/manual/install/index.html#asyncio-trollius) state that with 3.4, Trollinus is no longer required. I've attached a sample diff with these control changes. What do you think? - Dan Cecile sample.diff Description: Binary data
Bug#911680: xserver-xorg-core: X server crashes when loading libglamorgl.so module (Bug #911680)
Hi, I had the same crash with xorg-server 2:1.20.1-5 on Virtualbox. I worked around it by turning off the “3D accelaration” option for my VM from VirtualBox.
Bug#887666: (no subject)
Can this bug be moved along? It keeps biting me
Bug#879789: intercal: Link error when compiling Intercal programs
Package: intercal Version: 30:0.30-1 Severity: grave Justification: renders package unusable Dear Maintainer, I tried using intercal 0.30 today and it cannot compile any programs, due to a link error: /usr/bin/ld: /usr/lib/libick.a(cesspool.o): relocation R_X86_64_32 against `.rodata.str1.8' can not be used when making a shared object; recompile with -fPIC /usr/bin/ld: /usr/lib/libick.a(ick_lose.o): relocation R_X86_64_32 against `.rodata.str1.1' can not be used when making a shared object; recompile with -fPIC /usr/bin/ld: /usr/lib/libick.a(fiddle.o): relocation R_X86_64_32 against `.rodata.str1.8' can not be used when making a shared object; recompile with -fPIC /usr/bin/ld: /usr/lib/libick.a(arrgghh.o): relocation R_X86_64_32S against `.rodata' can not be used when making a shared object; recompile with -fPIC /usr/bin/ld: /usr/lib/libick.a(clc-cset.o): relocation R_X86_64_32 against `.rodata.str1.1' can not be used when making a shared object; recompile with -fPIC /usr/bin/ld: /usr/lib/libick.a(uncommon.o): relocation R_X86_64_32 against `.rodata.str1.1' can not be used when making a shared object; recompile with -fPIC /usr/bin/ld: final link failed: Nonrepresentable section on output collect2: error: ld returned 1 exit status This error appears when using `ick` on example programs included in package. This seems like a packaging problem because I was able to download the upstream tarball, configure and build using default options, and run my locally-built `ick` without any problems. -- System Information: Debian Release: buster/sid APT prefers unstable APT policy: (500, 'unstable'), (500, 'oldstable') Architecture: amd64 (x86_64) Foreign Architectures: i386 Kernel: Linux 3.18.0-15956-gde0b452850f1 (SMP w/2 CPU cores; PREEMPT) Locale: LANG=en_US.UTF-8, LC_CTYPE=en_US.UTF-8 (charmap=UTF-8), LANGUAGE=en_US.UTF-8 (charmap=UTF-8) Shell: /bin/sh linked to /bin/dash Init: unable to detect Versions of packages intercal depends on: ii gcc [c-compiler]4:6.3.0-4d1 ii gcc-6 [c-compiler] 6.4.0-2 ii libc6 2.24-14 intercal recommends no packages. intercal suggests no packages. -- no debconf information
Bug#1065725: adns: FTBFS on arm{el,hf}: FAILED ./case-1stservbroken - WRONG OUTPUT - lines of syscall remaining 0
Greetings!
I took a look at this bug today.
I found that the regress testsuite make use of some negative offsets, which
seem to perplex the reader on 32 bit systems.
Please see the attached patch, which has allowed this to build for Ubuntu.
-Dan
Author: Dan Bungert
Description: Fix reads of signed values into unsigned variables
Bug-Ubuntu: https://bugs.launchpad.net/bugs/2057735
Bug-Debian: https://bugs.debian.org/1065725
Forwarded: yes
Last-Update: 2024-03-14
The regress testsuite makes use of time offsets to mock the passage of time,
and some of the usec values are expressed as negative numbers. Update the
reader to be able to handle that.
--- a/regress/hplayback.c.m4
+++ b/regress/hplayback.c.m4
@@ -108,7 +108,8 @@
void Tensuresetup(void) {
int fd;
int chars;
- unsigned long sec, usec;
+ time_t sec;
+ suseconds_t usec;
Tensure_reportfile();
Tensure_fuzzrawfile();
@@ -124,7 +125,7 @@
if (!adns__vbuf_ensure(&vb2,1000)) Tnomem();
fgets(vb2.buf,vb2.avail,Tinputfile); Pcheckinput();
chars= -1;
- sscanf(vb2.buf," start %lu.%lu%n",&sec,&usec,&chars);
+ sscanf(vb2.buf," start %lld.%ld%n",&sec,&usec,&chars);
if (chars==-1) Psyntax("start time invalid");
currenttime.tv_sec= sec;
currenttime.tv_usec= usec;
@@ -170,12 +171,13 @@
static void P_updatetime(void) {
int chars;
- unsigned long sec, usec;
+ time_t sec;
+ suseconds_t usec;
if (!adns__vbuf_ensure(&vb2,1000)) Tnomem();
fgets(vb2.buf,vb2.avail,Tinputfile); Pcheckinput();
chars= -1;
- sscanf(vb2.buf," +%lu.%lu%n",&sec,&usec,&chars);
+ sscanf(vb2.buf," +%lld.%ld%n",&sec,&usec,&chars);
if (chars==-1) Psyntax("update time invalid");
currenttime.tv_sec+= sec;
currenttime.tv_usec+= usec;
Bug#1038608: rust-coretuils: FTBFS: error: no matching package named `remove_dir_all` found
This dependency was removed upstream in v0.0.18 (and v0.0.19).
Bug#1040853: python-lockfile autopkg test fail with setuptools 68
Just wanted to quickly confirm that the same fix proposed at: https://bugs.debian.org/cgi-bin/bugreport.cgi?att=1;bug=1040854;filename=python-tinyrpc_0.6-4ubuntu1.debdiff;msg=10 works well for python-lockfile. -Dan
Bug#1040633: pilkit autopkg tests fail with pillow 10.0.0
Upstream proposal resolves this: https://github.com/matthewwithanm/pilkit/pull/66/commits/e2eb73e1798865a201e570fced0bac195b2a590c -Dan
Bug#1070733: linux-image-5.10.0-29-amd64 fails to boot with Error 16: Inconsistent filesystem structure
Package: src:linux Version: 5.10.216-1 Severity: grave Justification: renders package unusable Dear Maintainer, After upgrading to linux-image-5.10.0-29 the system fails to boot with grub 'Error 16: Inconsistent filesystem structure'. Booting into linux-image-5.10.0-28-amd64 and the system is once again bootable The console displays: Booting 'Debian GNU/Linux, kernel 5.10.0-29-amd64' root (hd0,0) Filesystem type is ext2fs, partition type 0x83 kernel /boot/vmlinuz-5.10.0-29-amd64 root=UUID=ca38e015-f8d1-4ef0-9dc9-b56d7c8 le0f1 ro [Linux-bzImage, setup=0x3c00, size=0x6b5f40] Initrd /boot/initrd. img-5.10.0-29-amd64 Error 16: Inconsistent filesystem structure Press any key to continue...- -- Package-specific info: ** Kernel log: boot messages should be attached ** Model information sys_vendor: QEMU product_name: Standard PC (i440FX + PIIX, 1996) product_version: pc-i440fx-8.1 chassis_vendor: QEMU chassis_version: pc-i440fx-8.1 bios_vendor: SeaBIOS bios_version: rel-1.16.2-0-gea1b7a073390-prebuilt.qemu.org ** PCI devices: 00:00.0 Host bridge [0600]: Intel Corporation 440FX - 82441FX PMC [Natoma] [8086:1237] (rev 02) Subsystem: Red Hat, Inc. Qemu virtual machine [1af4:1100] Control: I/O+ Mem+ BusMaster- SpecCycle- MemWINV- VGASnoop- ParErr- Stepping- SERR+ FastB2B- DisINTx- Status: Cap- 66MHz- UDF- FastB2B- ParErr- DEVSEL=fast >TAbort- SERR- TAbort- SERR- TAbort- SERR- TAbort- SERR- TAbort- SERR- TAbort- SERR- TAbort- SERR- Kernel driver in use: virtio-pci Kernel modules: virtio_pci 00:05.0 SCSI storage controller [0100]: Red Hat, Inc. Virtio SCSI [1af4:1004] Subsystem: Red Hat, Inc. Virtio SCSI [1af4:0008] Physical Slot: 5 Control: I/O+ Mem+ BusMaster+ SpecCycle- MemWINV- VGASnoop- ParErr- Stepping- SERR+ FastB2B- DisINTx+ Status: Cap+ 66MHz- UDF- FastB2B- ParErr- DEVSEL=fast >TAbort- SERR- Kernel driver in use: virtio-pci Kernel modules: virtio_pci 00:12.0 Ethernet controller [0200]: Red Hat, Inc. Virtio network device [1af4:1000] Subsystem: Red Hat, Inc. Virtio network device [1af4:0001] Physical Slot: 18 Control: I/O+ Mem+ BusMaster+ SpecCycle- MemWINV- VGASnoop- ParErr- Stepping- SERR+ FastB2B- DisINTx+ Status: Cap+ 66MHz- UDF- FastB2B- ParErr- DEVSEL=fast >TAbort- SERR- Kernel driver in use: virtio-pci Kernel modules: virtio_pci 00:13.0 Ethernet controller [0200]: Red Hat, Inc. Virtio network device [1af4:1000] Subsystem: Red Hat, Inc. Virtio network device [1af4:0001] Physical Slot: 19 Control: I/O+ Mem+ BusMaster+ SpecCycle- MemWINV- VGASnoop- ParErr- Stepping- SERR+ FastB2B- DisINTx+ Status: Cap+ 66MHz- UDF- FastB2B- ParErr- DEVSEL=fast >TAbort- SERR- Kernel driver in use: virtio-pci Kernel modules: virtio_pci 00:1e.0 PCI bridge [0604]: Red Hat, Inc. QEMU PCI-PCI bridge [1b36:0001] (prog-if 00 [Normal decode]) Control: I/O+ Mem+ BusMaster- SpecCycle- MemWINV- VGASnoop- ParErr- Stepping- SERR+ FastB2B- DisINTx- Status: Cap+ 66MHz+ UDF- FastB2B+ ParErr- DEVSEL=fast >TAbort- SERR- TAbort- Reset- FastB2B- PriDiscTmr- SecDiscTmr- DiscTmrStat- DiscTmrSERREn- Capabilities: 00:1f.0 PCI bridge [0604]: Red Hat, Inc. QEMU PCI-PCI bridge [1b36:0001] (prog-if 00 [Normal decode]) Control: I/O+ Mem+ BusMaster- SpecCycle- MemWINV- VGASnoop- ParErr- Stepping- SERR+ FastB2B- DisINTx- Status: Cap+ 66MHz+ UDF- FastB2B+ ParErr- DEVSEL=fast >TAbort- SERR- TAbort- Reset- FastB2B- PriDiscTmr- SecDiscTmr- DiscTmrStat- DiscTmrSERREn- Capabilities: ** USB devices: not available -- System Information: Debian Release: 11.9 APT prefers oldstable-security APT policy: (500, 'oldstable-security'), (500, 'oldstable') Architecture: amd64 (x86_64) Kernel: Linux 5.10.0-28-amd64 (SMP w/6 CPU threads) Locale: LANG=en_GB.UTF-8, LC_CTYPE=en_GB.UTF-8 (charmap=UTF-8), LANGUAGE not set Shell: /bin/sh linked to /bin/dash Init: systemd (via /run/systemd/system) LSM: AppArmor: enabled Versions of packages linux-image-5.10.0-29-amd64 depends on: ii initramfs-tools [linux-initramfs-tool] 0.140 ii kmod28-1 ii linux-base 4.6 Versions of packages linux-image-5.10.0-29-amd64 recommends: ii apparmor 2.13.6-10 ii firmware-linux-free 20200122-1 Versions of packages linux-image-5.10.0-29-amd64 suggests: pn debian-kernel-handbook pn grub-pc | grub-efi-amd64 | extlinux pn linux-doc-5.10 Versions of packages linux-image-5.10.0-29-amd64 is related to: pn firmware-amd-graphics pn firmware-atheros pn firmware-bnx2 pn firmware-bnx2x pn firmware-brcm80211 pn firmware-cavium pn firmware-intel-sound pn firmware-intelwimax pn firmware-ipw2x00 pn f
Bug#1070733: linux-image-5.10.0-29-amd64 fails to boot with Error 16: Inconsistent filesystem structure
> If I find time I'll have a look at this (probably just by looking > through GRUB 2 for candidate backports and hoping that one of them > helps). However, I should warn you that GRUB Legacy is extremely very > unmaintained at this point; I've really just been doing last-resort > patching for years, and this normally hasn't included debugging its > filesystem code. It'd be in your interests to migrate to GRUB 2. Thanks for your response - I hadn't quite noticed that this was legacy grub (and had kinda made the assumption the Debian upgrades had forced the upgrade). I have migrated to GRUB 2 and can confirm this resolves the issue. cheers, Dan The Networking People (TNP) Limited. Registered office: Network House, Caton Rd, Lancaster, LA1 3PE. Registered in England & Wales with company number: 07667393 This email and any files transmitted with it are confidential and intended solely for the use of the individual or entity to whom they are addressed. If you have received this email in error please notify the system manager. This message contains confidential information and is intended only for the individual named. If you are not the named addressee you should not disseminate, distribute or copy this e-mail. Please notify the sender immediately by e-mail if you have received this e-mail by mistake and delete this e-mail from your system. If you are not the intended recipient you are notified that disclosing, copying, distributing or taking any action in reliance on the contents of this information is strictly prohibited.
Bug#964866: When upgrade from Stretch to Buster my development environment stop working and Arm (sama5d3) never mount his root on NFS
Package: nfs-kernel-server Version: 1:1.3.4-2.5 Severity: critical Tags: upstream I have using development environment for ARM (sama5d3) with root on NFS. Arm donwload kernel and DTB boots and mount root exported by my computer with Debian Buster. I works perfect with Ddebian Stretch but stop with Buster. I tested many kernels on ARM (latest 5.4.41 and 4.19.131) and nothing helps. In Virtual Box I have Debian Stretch (works) upgraded to Buster (desn't work) and upgraded to testing (doesn't work). Booting always end when kernel try mount root on NFS with: macb f802c000.ethernet eth0: link up (100/Full) Sending DHCP requests ., OK IP-Config: Got DHCP answer from 192.168.3.55, my address is 192.168.3.100 IP-Config: Complete: device=eth0, hwaddr=3e:36:65:ba:6f:be, ipaddr=192.168.3.100, mask=255.255.255.0, gw=255.255.255.255 host=192.168.3.100, domain=, nis-domain=(none) bootserver=192.168.3.10, rootserver=192.168.3.10, rootpath=/usr/local/tftpboot/acquaA5/namornik nameserver0=192.168.3.55 cfg80211: Loading compiled-in X.509 certificates for regulatory database cfg80211: Loaded X.509 cert 'sforshee: 00b28ddf47aef9cea7' platform regulatory.0: Direct firmware load for regulatory.db failed with error -2 cfg80211: failed to load regulatory.db random: crng init done VFS: Unable to mount root fs via NFS, trying floppy. VFS: Cannot open root device "nfs" or unknown-block(2,0): error -6 Please append a correct "root=" boot option; here are the available partitions: 1f00 256 mtdblock0 (driver?) 1f01 512 mtdblock1 (driver?) 1f02 256 mtdblock2 (driver?) 1f03 256 mtdblock3 (driver?) 1f04 256 mtdblock4 (driver?) 1f05 512 mtdblock5 (driver?) 1f066144 mtdblock6 (driver?) 1f07 253952 mtdblock7 (driver?) Kernel panic - not syncing: VFS: Unable to mount root fs on unknown-block(2,0) CPU: 0 PID: 1 Comm: swapper Not tainted 4.19.56 #1 Hardware name: Atmel SAMA5 [] (unwind_backtrace) from [] (show_stack+0x10/0x14) [] (show_stack) from [] (panic+0xdc/0x258) [] (panic) from [] (mount_block_root+0x1ec/0x2d0) [] (mount_block_root) from [] (mount_root+0x144/0x160) [] (mount_root) from [] (prepare_namespace+0x150/0x198) [] (prepare_namespace) from [] (kernel_init_freeable+0x1b8/0x1c8) [] (kernel_init_freeable) from [] (kernel_init+0x8/0x110) [] (kernel_init) from [] (ret_from_fork+0x14/0x2c) Exception stack(0xcf425fb0 to 0xcf425ff8) 5fa0: 5fc0: 5fe0: 0013 ---[ end Kernel panic - not syncing: VFS: Unable to mount root fs on unknown-block(2,0) ]-- And on server: Jul 10 13:37:40 think rpc.mountd[666]: from_local: updating local if addr list Jul 10 13:37:40 think rpc.mountd[666]: from_local: checked 9 local if addrs; incoming address not found Jul 10 13:37:40 think rpc.mountd[666]: check_default: access by 192.168.3.102 ALLOWED Jul 10 13:37:40 think rpc.mountd[666]: Received NULL request from 192.168.3.102 Jul 10 13:37:40 think rpc.mountd[666]: check_default: access by 192.168.3.102 ALLOWED (cached) Jul 10 13:37:40 think rpc.mountd[666]: Received MNT1(/usr/local/tftpboot/acquaA5/namornik) request from 192.168.3.102 Jul 10 13:37:40 think rpc.mountd[666]: authenticated mount request from 192.168.3.102:774 for /usr/local/tftpboot/acquaA5/namornik (/usr/local/tftpboot/acquaA5/namornik) Jul 10 13:37:45 think rpc.mountd[666]: check_default: access by 192.168.3.102 ALLOWED (cached) Jul 10 13:37:45 think rpc.mountd[666]: Received NULL request from 192.168.3.102 Jul 10 13:37:45 think rpc.mountd[666]: check_default: access by 192.168.3.102 ALLOWED (cached) Jul 10 13:37:45 think rpc.mountd[666]: Received MNT1(/usr/local/tftpboot/acquaA5/namornik) request from 192.168.3.102 Jul 10 13:37:45 think rpc.mountd[666]: authenticated mount request from 192.168.3.102:899 for /usr/local/tftpboot/acquaA5/namornik (/usr/local/tftpboot/acquaA5/namornik) Jul 10 13:37:55 think rpc.mountd[666]: check_default: access by 192.168.3.102 ALLOWED (cached) Jul 10 13:37:55 think rpc.mountd[666]: Received NULL request from 192.168.3.102 Jul 10 13:37:55 think rpc.mountd[666]: check_default: access by 192.168.3.102 ALLOWED (cached) Jul 10 13:37:55 think rpc.mountd[666]: Received MNT1(/usr/local/tftpboot/acquaA5/namornik) request from 192.168.3.102 Jul 10 13:37:55 think rpc.mountd[666]: authenticated mount request from 192.168.3.102:980 for /usr/local/tftpboot/acquaA5/namornik (/usr/local/tftpboot/acquaA5/namornik) All is corectly exported but client never mounts. But when I boot Arm with root on Stretch machine a try mount directory exported from Buster machine all works. -- Package-specific info: -- rpcinfo -- program vers proto port service 104 tcp111 portmapper 103 tcp11
Bug#957077: cen64: ftbfs with GCC-10
On 2020-04-17 06:57, Matthias Klose wrote: The package fails to build in a test rebuild on at least amd64 with gcc-10/g++-10, but succeeds to build with gcc-9/g++-9. The severity of this report will be raised before the bullseye release, so nothing has to be done for the buster release. A new version of this package has been uploaded that fixes this issue (0.3+git20200723-1)
Bug#997756: python-meshplex: FTBFS: sed: no input files
tags 997756 patch thanks Hi, I ran across this FTBFS today and investigated. Here's a patch. The forkme sed now appears unneeded, and the other one needs a URL update. -Dan diff -Nru python-meshplex-0.15.13/debian/rules python-meshplex-0.15.13/debian/rules --- python-meshplex-0.15.13/debian/rules 2021-03-16 04:39:31.0 -0600 +++ python-meshplex-0.15.13/debian/rules 2021-11-30 15:35:13.0 -0700 @@ -4,6 +4,7 @@ #export DH_VERBOSE = 1 export PYBUILD_NAME=meshplex +latestjs=https://cdn.jsdelivr.net/npm/mathjax@3/es5/tex-mml-chtml.js %: dh $@ --with python3,sphinxdoc --buildsystem=pybuild @@ -21,5 +22,4 @@ override_dh_sphinxdoc-indep: dh_sphinxdoc -i - grep "https://cdnjs.cloudflare.com/ajax/libs/mathjax/.*/latest.js"; debian/python-meshplex-doc/usr/share/doc/python-meshplex-doc/* -r --files-with-matches | xargs sed "s|src=\"https://cdnjs.cloudflare.com/ajax/libs/mathjax/.*/latest.js|src=\"file://usr/share/javascript/mathjax/unpacked/latest.js|g" -i - grep "https://s3.amazonaws.com/github/ribbons/forkme_right_darkblue_121621.png"; debian/python-meshplex-doc/usr/share/doc/python-meshplex-doc/* -r --files-with-matches | xargs sed "s|src=\"https://s3.amazonaws.com/github/ribbons/forkme_right_darkblue_121621.png|src=\"_static/forkme_right_darkblue_121621.png|g" -i + grep "$(latestjs)" debian/python-meshplex-doc/usr/share/doc/python-meshplex-doc/* -r --files-with-matches | xargs sed "s|src=\"$(latestjs)|src=\"file://usr/share/javascript/mathjax/unpacked/latest.js|g" -i
Bug#1004797: xpra: FTBFS with ffmpeg 5.0
Dear Maintainer,
I backported the work done by upstream around ffmpeg 5. Please see attached.
This was sufficient to address the FTBFS both for Sid and Ubuntu Kinetic.
-Dan
Subject: Backport ffmpeg 5 fixes
Author: Dan Bungert
Origin: https://github.com/Xpra-org/xpra
Bug: https://github.com/Xpra-org/xpra/pull/3242
Bug-Ubuntu: https://bugs.launchpad.net/bugs/1982418
Bug-Debian: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1004797
Forwarded: not-needed
Last-Update: 2022-07-20
Backport fixes from Antoine Martin upstream:
* b66a358fc31852ad246a9956dfa5f09a0f2b5274
* 5058864909fdf76652d20c3d555bd91667762f88
* f70e01d6e66245b689c11433abef9c51d345452e
* 19060163bc0a0174dafce40ee7c176e8c7fbb9df
--- a/xpra/codecs/enc_ffmpeg/encoder.pyx
+++ b/xpra/codecs/enc_ffmpeg/encoder.pyx
@@ -203,7 +203,7 @@
int width
int height
AVPixelFormat pix_fmt
-int thread_safe_callbacks
+#int thread_safe_callbacks
int thread_count
int thread_type
int flags
@@ -286,7 +286,7 @@
AVCodecID AV_CODEC_ID_AAC
#init and free:
-AVCodec *avcodec_find_encoder(AVCodecID id)
+const AVCodec *avcodec_find_encoder(AVCodecID id)
AVCodecContext *avcodec_alloc_context3(const AVCodec *codec)
int avcodec_open2(AVCodecContext *avctx, const AVCodec *codec, AVDictionary **options)
int avcodec_send_frame(AVCodecContext *avctx,const AVFrame *frame) nogil
@@ -367,10 +367,8 @@
int AVFMT_FLAG_DISCARD_CORRUPT #Discard frames marked corrupted
int AVFMT_FLAG_FLUSH_PACKETS#Flush the AVIOContext every packet
int AVFMT_FLAG_BITEXACT
-int AVFMT_FLAG_MP4A_LATM#Enable RTP MP4A-LATM payload
int AVFMT_FLAG_SORT_DTS #try to interleave outputted packets by dts (using this flag can slow demuxing down)
int AVFMT_FLAG_PRIV_OPT #Enable use of private options by delaying codec open (this could be made default once all code is converted)
-int AVFMT_FLAG_KEEP_SIDE_DATA #Don't merge side data but keep it separate.
int AVFMT_FLAG_FAST_SEEK#Enable fast, but inaccurate seeks for some formats
int AVFMT_NOFILE#Demuxer will use avio_open, no opened file should be provided by the caller
@@ -509,10 +507,8 @@
AVFMT_FLAG_DISCARD_CORRUPT : "DISCARD_CORRUPT",
AVFMT_FLAG_FLUSH_PACKETS : "FLUSH_PACKETS",
AVFMT_FLAG_BITEXACT: "BITEXACT",
-AVFMT_FLAG_MP4A_LATM : "MP4A_LATM",
AVFMT_FLAG_SORT_DTS: "SORT_DTS",
AVFMT_FLAG_PRIV_OPT: "PRIV_OPT",
-AVFMT_FLAG_KEEP_SIDE_DATA : "KEEP_SIDE_DATA",
AVFMT_FLAG_FAST_SEEK : "FAST_SEEK",
}
@@ -747,7 +743,7 @@
cdef object muxer_format
cdef object file
#video:
-cdef AVCodec *video_codec
+cdef const AVCodec *video_codec
cdef AVStream *video_stream
cdef AVCodecContext *video_ctx
cdef AVPixelFormat pix_fmt
@@ -759,7 +755,7 @@
cdef object encoding
cdef object profile
#audio:
-cdef AVCodec *audio_codec
+cdef const AVCodec *audio_codec
cdef AVStream *audio_stream
cdef AVCodecContext *audio_ctx
cdef uint8_t ready
@@ -902,7 +898,7 @@
self.video_ctx.height = self.height
self.video_ctx.bit_rate = max(20, self.width*self.height*4) #4 bits per pixel
self.video_ctx.pix_fmt = self.pix_fmt
-self.video_ctx.thread_safe_callbacks = 1
+#self.video_ctx.thread_safe_callbacks = 1
#if oformat.flags & AVFMT_GLOBALHEADER:
if self.encoding not in ("mpeg1", "mpeg2"):
self.video_ctx.thread_type = THREAD_TYPE
--- a/xpra/codecs/dec_avcodec2/decoder.pyx
+++ b/xpra/codecs/dec_avcodec2/decoder.pyx
@@ -71,7 +71,7 @@
int width
int height
AVPixelFormat pix_fmt
-int thread_safe_callbacks
+#int thread_safe_callbacks
int thread_count
int thread_type
int flags
@@ -87,7 +87,7 @@
AVCodecID AV_CODEC_ID_MPEG2VIDEO
#init and free:
-AVCodec *avcodec_find_decoder(AVCodecID id)
+const AVCodec *avcodec_find_decoder(AVCodecID id)
AVCodecContext *avcodec_alloc_context3(const AVCodec *codec)
int avcodec_open2(AVCodecContext *avctx, const AVCodec *codec, AVDictionary **options)
AVFrame* av_frame_alloc()
@@ -95,7 +95,8 @@
int avcodec_close(AVCodecContext *avctx)
#actual decoding:
-void av_init_packet(AVPacket *pkt) nogil
+AVPacket *av_packet_alloc() nogil
+void av_packet_free(AVPacket **avpkt)
void avcodec_get_frame_defaults(AVFrame *frame) nogil
int avcodec_send_packet(AVCodecContext *avctx, const AVPacket *avpkt) nogil
int avcodec_receive_frame(AVCodecContext *avctx, AVFrame *frame) nogil
@@ -293,7 +294,7 @@
It also handles reconstructing a single ImageWrapper
constructed from
Bug#1004805: xmms2: FTBFS with ffmpeg 5.0
Dear Maintainer,
I backported the work merged upstream around ffmpeg 5. Please see attached.
This was sufficient to address the FTBFS both for Sid and Ubuntu Kinetic.
-Dan
Description: ffmpeg 5 compat
Author: Dan Bungert
Bug-Ubuntu: https://bugs.launchpad.net/debian/+source/xmms2/+bug/1982419
Bug-Debian: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1004805
Forwarded: not-needed
Origin: https://github.com/xmms2/xmms2-devel/pull/11
Last-Update: 2022-07-20
diff --git a/src/plugins/avcodec/avcodec.c b/src/plugins/avcodec/avcodec.c
index 23fd4615e..a5c5aa0f4 100644
--- a/src/plugins/avcodec/avcodec.c
+++ b/src/plugins/avcodec/avcodec.c
@@ -31,6 +31,7 @@
typedef struct {
AVCodecContext *codecctx;
+ AVPacket packet;
guchar *buffer;
guint buffer_length;
@@ -149,13 +150,12 @@ xmms_avcodec_init (xmms_xform_t *xform)
data->buffer = g_malloc (AVCODEC_BUFFER_SIZE);
data->buffer_size = AVCODEC_BUFFER_SIZE;
data->codecctx = NULL;
+ data->packet.size = 0;
data->read_out_frame = av_frame_alloc ();
xmms_xform_private_data_set (xform, data);
- avcodec_register_all ();
-
mimetype = xmms_xform_indata_get_str (xform,
XMMS_STREAM_TYPE_MIMETYPE);
data->codec_id = mimetype + strlen ("audio/x-ffmpeg-");
@@ -466,45 +466,37 @@ FF_INPUT_BUFFER_PADDING_SIZE long.
static gint
xmms_avcodec_internal_decode_some (xmms_avcodec_data_t *data)
{
- int got_frame = 0;
- gint bytes_read = 0;
- AVPacket packet;
+ int rc = 0;
- av_init_packet (&packet);
- packet.data = data->buffer;
- packet.size = data->buffer_length;
+ if (data->packet.size == 0) {
+ av_init_packet (&data->packet);
+ data->packet.data = data->buffer;
+ data->packet.size = data->buffer_length;
- /* clear buffers and reset fields to defaults */
- av_frame_unref (data->read_out_frame);
-
- bytes_read = avcodec_decode_audio4 (
- data->codecctx, data->read_out_frame, &got_frame, &packet);
+ rc = avcodec_send_packet(data->codecctx, &data->packet);
+ if (rc == AVERROR_EOF)
+ rc = 0;
+ }
- /* The DTS decoder of ffmpeg is buggy and always returns
- * the input buffer length, get frame length from header */
- /* FIXME: Is still true? */
- if (!strcmp (data->codec_id, "dca") && bytes_read > 0) {
- bytes_read = ((int)data->buffer[5] << 12) |
- ((int)data->buffer[6] << 4) |
- ((int)data->buffer[7] >> 4);
- bytes_read = (bytes_read & 0x3fff) + 1;
+ if (rc == 0) {
+ rc = avcodec_receive_frame(data->codecctx, data->read_out_frame);
+ if (rc < 0) {
+ data->packet.size = 0;
+ data->buffer_length = 0;
+ if (rc == AVERROR(EAGAIN)) rc = 0;
+ else if (rc == AVERROR_EOF) rc = 1;
+ }
+ else
+ rc = 1;
}
- if (bytes_read < 0 || bytes_read > data->buffer_length) {
+ if (rc < 0) {
+ data->packet.size = 0;
XMMS_DBG ("Error decoding data!");
return -1;
}
- if (bytes_read < data->buffer_length) {
- data->buffer_length -= bytes_read;
- g_memmove (data->buffer,
- data->buffer + bytes_read,
- data->buffer_length);
- } else {
- data->buffer_length = 0;
- }
-
- return got_frame ? 1 : 0;
+ return rc;
}
static void
diff --git a/src/plugins/avcodec/wscript b/src/plugins/avcodec/wscript
index 00b182b24..4b6227437 100644
--- a/src/plugins/avcodec/wscript
+++ b/src/plugins/avcodec/wscript
@@ -1,7 +1,7 @@
from waftools.plugin import plugin
## Code fragments for configuration
-avcodec_decode_audio4_fragment = """
+avcodec_send_packet_fragment = """
#ifdef HAVE_LIBAVCODEC_AVCODEC_H
# include "libavcodec/avcodec.h"
#else
@@ -9,11 +9,9 @@ avcodec_decode_audio4_fragment = """
#endif
int main(void) {
AVCodecContext *ctx;
-AVFrame *frame;
-int got_frame;
AVPacket *pkt;
-avcodec_decode_audio4 (ctx, frame, &got_frame, pkt);
+avcodec_send_packet (ctx, pkt);
return 0;
}
@@ -40,12 +38,12 @@ def plugin_configure(conf):
conf.check_cc(header_name="avcodec.h", uselib="avcodec", type="cshlib", mandatory=False)
conf.check_cc(header_name="libavcodec/avcodec.h", uselib="avcodec", type="cshlib", mandatory=False)
-# mandatory function avcodec_decode_audio4 available since
-# * ffmpeg: commit e4de716, lavc 53.40.0, release 0.9
-# * libav: commit 0eea212, lavc 53.25.0, release 0.8
-conf.check_cc(fragment=avcodec_decode_audio4_fragment, uselib="avcodec",
- uselib_store="avcodec_decode_audio4",
- msg="Checking for function avcodec_decode_audio4", mandatory=True)
+# mandatory function avcodec_send_packet available since
+# * ffmpeg: commit 7fc329e, lavc 57.37.100, release 3.1
+# *
Bug#1004616: performous: FTBFS with ffmpeg 5.0
Dear Maintainer,
I did a test build using the version of performous in experimental on Sid and
Ubuntu Kinetic. I found that it continues to have a const-related build
failure.
Upstream commit
https://github.com/performous/performous/pull/752/commits/80d5b08d34a97db16fe12f82e9060570087ef0f0
is a step in the right direction, but in this older codebase needed more.
Please see attached for a patch that fixes build of the version in experimental
with Sid and Ubuntu Kinetic.
-Dan
Description: constify AVCodec* for ffmpeg 5 compat
Origin: https://github.com/performous/performous/pull/752/commits/80d5b08d34a97db16fe12f82e9060570087ef0f0
Author: Dan Bungert
Bug-Ubuntu: https://bugs.launchpad.net/bugs/1982781
Bug-Debian: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1004616
Forwarded: not-needed
Last-Update: 2022-07-25
Extended above commit to handle an additional const.
--- a/game/ffmpeg.cc
+++ b/game/ffmpeg.cc
@@ -96,10 +96,16 @@
if (avformat_find_stream_info(m_formatContext, nullptr) < 0) throw std::runtime_error("Cannot find stream information");
m_formatContext->flags |= AVFMT_FLAG_GENPTS;
// Find a track and open the codec
+#if (LIBAVFORMAT_VERSION_INT) >= (AV_VERSION_INT(59, 0, 100))
+ const
+#endif
AVCodec* codec = nullptr;
m_streamId = av_find_best_stream(m_formatContext, (AVMediaType)m_mediaType, -1, -1, &codec, 0);
if (m_streamId < 0) throw std::runtime_error("No suitable track found");
+#if (LIBAVFORMAT_VERSION_INT) >= (AV_VERSION_INT(59, 0, 100))
+ const
+#endif
#if (LIBAVCODEC_VERSION_INT) >= (AV_VERSION_INT(57,0,0))
AVCodec* pCodec = avcodec_find_decoder(m_formatContext->streams[m_streamId]->codecpar->codec_id);
AVCodecContext* pCodecCtx = avcodec_alloc_context3(pCodec);
Bug#1010095: performous: FTBFS on ppc64el
Hi Maintainer, I was able to get it building again, at least on the ppc64el machine I tested, by not using with -mno-altivec. Builds both with Sid and Ubuntu Kinetic, if you use my patch from bug 1004616 and no longer set -mno-altivec. See also this commit: https://salsa.debian.org/games-team/performous/-/commit/de72e1dfae743adb65a444341872bda06d6941e7 Is -mno-altivec still required? -Dan
Bug#1010095: performous: FTBFS on ppc64el
Just saw the existing merge request. Oh well, I guess I can treat this as +1 for merging https://salsa.debian.org/games-team/performous/-/merge_requests/1 .
Bug#1004629: motion: FTBFS with ffmpeg 5.0
Dear Maintainer,
I backported the work merged upstream around ffmpeg 5. Please see attached.
This was sufficient to address the FTBFS both for Sid and Ubuntu Kinetic.
-Dan
Description: Backport ffmpeg 5 fixes.
Author: Dan Bungert
Origin: https://github.com/Motion-Project/motion/pull/1351/commits/fc9ed24c467006a463684f7db2f760a61f1eebe0
Bug-Ubuntu: https://bugs.launchpad.net/bugs/1982886
Bug-Debian: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1004629
Forwarded: not-needed
Last-Update: 2022-07-26
--- a/src/ffmpeg.c
+++ b/src/ffmpeg.c
@@ -340,7 +340,7 @@
if (ffmpeg->tlapse == TIMELAPSE_APPEND){
ffmpeg->oc->oformat = av_guess_format ("mpeg2video", NULL, NULL);
-if (ffmpeg->oc->oformat) ffmpeg->oc->oformat->video_codec = MY_CODEC_ID_MPEG2VIDEO;
+if (ffmpeg->oc->oformat) ffmpeg->oc->video_codec_id = MY_CODEC_ID_MPEG2VIDEO;
retcd = snprintf(ffmpeg->filename,PATH_MAX,"%s.mpg",basename);
if ((!ffmpeg->oc->oformat) ||
(retcd < 0) || (retcd >= PATH_MAX)){
@@ -362,7 +362,7 @@
if (strcmp(codec_name, "msmpeg4") == 0) {
ffmpeg->oc->oformat = av_guess_format("avi", NULL, NULL);
retcd = snprintf(ffmpeg->filename,PATH_MAX,"%s.avi",basename);
-if (ffmpeg->oc->oformat) ffmpeg->oc->oformat->video_codec = MY_CODEC_ID_MSMPEG4V2;
+if (ffmpeg->oc->oformat) ffmpeg->oc->video_codec_id = MY_CODEC_ID_MSMPEG4V2;
}
if (strcmp(codec_name, "swf") == 0) {
@@ -373,13 +373,13 @@
if (strcmp(codec_name, "flv") == 0) {
ffmpeg->oc->oformat = av_guess_format("flv", NULL, NULL);
retcd = snprintf(ffmpeg->filename,PATH_MAX,"%s.flv",basename);
-if (ffmpeg->oc->oformat) ffmpeg->oc->oformat->video_codec = MY_CODEC_ID_FLV1;
+if (ffmpeg->oc->oformat) ffmpeg->oc->video_codec_id = MY_CODEC_ID_FLV1;
}
if (strcmp(codec_name, "ffv1") == 0) {
ffmpeg->oc->oformat = av_guess_format("avi", NULL, NULL);
retcd = snprintf(ffmpeg->filename,PATH_MAX,"%s.avi",basename);
-if (ffmpeg->oc->oformat) ffmpeg->oc->oformat->video_codec = MY_CODEC_ID_FFV1;
+if (ffmpeg->oc->oformat) ffmpeg->oc->video_codec_id = MY_CODEC_ID_FFV1;
}
if (strcmp(codec_name, "mov") == 0) {
@@ -390,19 +390,19 @@
if (strcmp(codec_name, "mp4") == 0) {
ffmpeg->oc->oformat = av_guess_format("mp4", NULL, NULL);
retcd = snprintf(ffmpeg->filename,PATH_MAX,"%s.mp4",basename);
-if (ffmpeg->oc->oformat) ffmpeg->oc->oformat->video_codec = MY_CODEC_ID_H264;
+if (ffmpeg->oc->oformat) ffmpeg->oc->video_codec_id = MY_CODEC_ID_H264;
}
if (strcmp(codec_name, "mkv") == 0) {
ffmpeg->oc->oformat = av_guess_format("matroska", NULL, NULL);
retcd = snprintf(ffmpeg->filename,PATH_MAX,"%s.mkv",basename);
-if (ffmpeg->oc->oformat) ffmpeg->oc->oformat->video_codec = MY_CODEC_ID_H264;
+if (ffmpeg->oc->oformat) ffmpeg->oc->video_codec_id = MY_CODEC_ID_H264;
}
if (strcmp(codec_name, "hevc") == 0) {
ffmpeg->oc->oformat = av_guess_format("mp4", NULL, NULL);
retcd = snprintf(ffmpeg->filename,PATH_MAX,"%s.mp4",basename);
-if (ffmpeg->oc->oformat) ffmpeg->oc->oformat->video_codec = MY_CODEC_ID_HEVC;
+if (ffmpeg->oc->oformat) ffmpeg->oc->video_codec_id = MY_CODEC_ID_HEVC;
}
//Check for valid results
@@ -422,7 +422,7 @@
return -1;
}
-if (ffmpeg->oc->oformat->video_codec == MY_CODEC_ID_NONE) {
+if (ffmpeg->oc->video_codec_id == MY_CODEC_ID_NONE) {
MOTION_LOG(ERR, TYPE_ENCODER, NO_ERRNO, _("Could not get the codec"));
ffmpeg_free_context(ffmpeg);
free(codec_name);
@@ -721,7 +721,7 @@
} else {
ffmpeg->codec = avcodec_find_encoder_by_name(&ffmpeg->codec_name[codec_name_len+1]);
if ((ffmpeg->oc->oformat) && (ffmpeg->codec != NULL)) {
-ffmpeg->oc->oformat->video_codec = ffmpeg->codec->id;
+ffmpeg->oc->video_codec_id = ffmpeg->codec->id;
} else if (ffmpeg->codec == NULL) {
MOTION_LOG(WRN, TYPE_ENCODER, NO_ERRNO
,_("Preferred codec %s not found")
@@ -730,7 +730,7 @@
}
}
if (!ffmpeg->codec)
-ffmpeg->codec = avcodec_find_encoder(ffmpeg->oc->oformat->video_codec);
+ffmpeg->codec =
Bug#948645: pesign FTBFS: nss-induced error: unsigned conversion from ‘int’ to ‘unsigned char’ changes value from ‘496’ to ‘240’ [-Werror=overflow]
This was fixed upstream in https://github.com/rhboot/pesign/commit/b535d1ac5cbcdf18a97d97a92581e38080d9e521.
Bug#968015: resolvconf-pull-resolved.service fails with systemd 246-2
On Mon, Aug 17, 2020 at 4:42 AM Michael Biebl wrote: > > Control: severity -1 serious > Control: tags -1 + patch > > Hi everyone, > > I think the effects of this issue are severe enough, that it needs to be > fixed for bullseye. In other words, it should be RC > > On Sat, 08 Aug 2020 13:13:44 +0200 =?utf-8?q?Thomas_M=C3=BChlbacher?= > wrote: > > I noticed that there were already two related bugreports, with Michael > > Biebl providing a solution for the issue: > > > > https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=967906 > > > > And to a lesser degree this one, I suppose: > > > > https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=968009 > > > > I tried the container setup again with `PathExists=` dropped from > > `resolvconf-pull-resolved.path` and it stops the errors from occurring, > > however I did not verify that this way the service still does what it's > > supposed to. > > #967906 and the related upstream bug report > https://github.com/systemd/systemd/issues/16669 have more context. > > In short: PathExists in systemd v246 changed its behaviour to actually > match the documentation. > For resolvconf-pull-resolved.service that means, it's continuously > started over and over again. > > Afaics, the simplest solution, is to simply drop > > PathExists=/run/systemd/resolve/stub-resolv.conf > > and instead add a > > [Install] > WantedBy=systemd-resolved.service > > > to resolvconf-pull-resolved.service and also add a > After=systemd-resolved.service It looks like resolvconf's resolvconf-pull-resolved.path has been updated to use PathChanged instead. That should fix the constant loop, though I'm not sure if it is optimal, as I vaguely remember someone complaining that systemd-resolved rewrites stub-resolv.conf often, and IIUC PathChanged= triggers on inotify IN_CLOSE_WRITE so it would trigger each time systemd-resolved opened (for write) and closed the file. Although I have not actually looked into the code, so maybe it's fine. In general I've tried to stay away from resolvconf as the integration with resolved has been a bit painful, and I think xnox is in the process of trying to fix that up. I do tag any LP bugs that I notice relate to resolved/resolvconf integration/interaction with the 'resolved-resolvconf' tag: https://bugs.launchpad.net/bugs/+bugs?field.tag=resolved-resolvconf > > I've attached a prospective patch. > > Dan, Dimitri, would welcome your feedback here, since most of the > resolvconf/resolved integration is seemingly coming from you. > > > Regards, > Michael
Bug#968015: resolvconf-pull-resolved.service fails with systemd 246-2
On Thu, Sep 3, 2020 at 3:02 PM Michael Biebl wrote: > > Hi Dan Hi Michael > > Am 03.09.20 um 20:42 schrieb Dan Streetman: > > On Mon, Aug 17, 2020 at 4:42 AM Michael Biebl wrote: > and over again. > >> > >> Afaics, the simplest solution, is to simply drop > >> > >> PathExists=/run/systemd/resolve/stub-resolv.conf > >> > >> and instead add a > >> > >> [Install] > >> WantedBy=systemd-resolved.service > >> > >> > >> to resolvconf-pull-resolved.service and also add a > >> After=systemd-resolved.service > > > > It looks like resolvconf's resolvconf-pull-resolved.path has been > > updated to use PathChanged instead. > > > Now I'm confused. > What my patch does (and which has been applied to resolvconf) is to drop > PathExists (instead the service is activated via > [Install] > WantedBy=systemd-resolved.service > ) > The PathChanged= bit has always been there. My patch did not add this. Sorry my bad, you are right, both PathExists= and PathChanged= were there before, and just PathChanged= now. Looks correct! > > Michael >
Bug#1057139: Update
Is anyone monitoring these bug reports? Any suggestions on next steps?
Bug#1030129: (no subject)
Are there any plans to backport this? Is the bug in a state that allows it to show up as an action item for the maintainers?
Bug#1051570: [Mlt-devel] Fwd: Bug#1051570: mlt: FTBFS with RtAudio 6
Fixed in git, supports old (4) and new versions. See also https://github.com/mltframework/mlt/issues/930 On Thu, Oct 12, 2023 at 6:34 AM Patrick Matthäi via Mlt-devel < mlt-de...@lists.sourceforge.net> wrote: > Hello, > > I have got this patch for RTAudio 6 "support" (not tested, but it builds > with 7.18.0). This patch also applies to the 7.20.0 version. > The problem is with the patch applied mlt builds against rtaudio 6.0.1, > but it fails against 5.2.0 just with: > > [ 57%] Linking CXX shared module ../../../out/lib/mlt/libmltmovit.so > cd /build/mlt-7.20.0/obj-x86_64-linux-gnu/src/modules/movit && > /usr/bin/cmake -E cmake_link_script CMakeFiles/mltmovit.dir/link.txt > --verbose=1 > /usr/bin/c++ -fPIC -g -O2 -ffile-prefix-map=/build/mlt-7.20.0=. > -fstack-protector-strong -fstack-clash-protection -Wformat > -Werror=format-security -fcf-protection -Wdate-time -D_FORTIFY_SOURCE=2 > -Wl,-z,relro -Wl,-z,now -shared -o ../../../out/lib/mlt/libmltmovit.so > CMakeFiles/mltmovit.dir/factory.c.o > CMakeFiles/mltmovit.dir/filter_glsl_manager.cpp.o > CMakeFiles/mltmovit.dir/filter_movit_blur.cpp.o > CMakeFiles/mltmovit.dir/filter_movit_convert.cpp.o > CMakeFiles/mltmovit.dir/filter_movit_crop.cpp.o > CMakeFiles/mltmovit.dir/filter_movit_deconvolution_sharpen.cpp.o > CMakeFiles/mltmovit.dir/filter_movit_diffusion.cpp.o > CMakeFiles/mltmovit.dir/filter_movit_flip.cpp.o > CMakeFiles/mltmovit.dir/filter_movit_glow.cpp.o > CMakeFiles/mltmovit.dir/filter_movit_lift_gamma_gain.cpp.o > CMakeFiles/mltmovit.dir/filter_movit_mirror.cpp.o > CMakeFiles/mltmovit.dir/filter_movit_opacity.cpp.o > CMakeFiles/mltmovit.dir/filter_movit_rect.cpp.o > CMakeFiles/mltmovit.dir/filter_movit_resample.cpp.o > CMakeFiles/mltmovit.dir/filter_movit_resize.cpp.o > CMakeFiles/mltmovit.dir/filter_movit_saturation.cpp.o > CMakeFiles/mltmovit.dir/filter_movit_vignette.cpp.o > CMakeFiles/mltmovit.dir/filter_movit_white_balance.cpp.o > CMakeFiles/mltmovit.dir/mlt_movit_input.cpp.o > CMakeFiles/mltmovit.dir/transition_movit_luma.cpp.o > CMakeFiles/mltmovit.dir/transition_movit_mix.cpp.o > CMakeFiles/mltmovit.dir/transition_movit_overlay.cpp.o > CMakeFiles/mltmovit.dir/consumer_xgl.c.o > -Wl,-rpath,/build/mlt-7.20.0/obj-x86_64-linux-gnu/out/lib: -lm > ../../../out/lib/libmlt++-7.so.7.20.0 /usr/lib/x86_64-linux-gnu/libX11.so > ../../../out/lib/libmlt-7.so.7.20.0 /usr/lib/x86_64-linux-gnu/libGLX.so > /usr/lib/x86_64-linux-gnu/libOpenGL.so > /usr/lib/x86_64-linux-gnu/libmovit.so /usr/lib/x86_64-linux-gnu/libepoxy.so > make[3]: Leaving directory '/build/mlt-7.20.0/obj-x86_64-linux-gnu' > [ 57%] Built target mltmovit > make[2]: Leaving directory '/build/mlt-7.20.0/obj-x86_64-linux-gnu' > make[1]: *** [Makefile:139: all] Error 2 > make[1]: Leaving directory '/build/mlt-7.20.0/obj-x86_64-linux-gnu' > dh_auto_build: error: cd obj-x86_64-linux-gnu && make -j2 "INSTALL=install > --strip-program=true" VERBOSE=1 returned exit code 2 > make: *** [debian/rules:11: binary] Error 2 > dpkg-buildpackage: error: debian/rules binary subprocess returned exit > status 2 > > > A better fix would be welcome :) > > > Weitergeleitete Nachricht > Betreff: Bug#1051570: mlt: FTBFS with RtAudio 6 > Weitersenden-Datum: Sat, 09 Sep 2023 21:15:01 + > Weitersenden-Von: IOhannes m zmoelnig > > Weitersenden-An: debian-bugs-d...@lists.debian.org > Weitersenden-CC: Patrick Matthäi > > Datum: Sat, 09 Sep 2023 23:10:59 +0200 > Von: IOhannes m zmoelnig > Antwort an: IOhannes m zmoelnig > , 1051...@bugs.debian.org > An: Debian Bug Tracking System > > > Source: mlt > Version: 7.18.0-2 > Severity: serious > Tags: ftbfs patch > Justification: fails to build from source (but built successfully in the > past) > > Dear Maintainer, > > mlt ftbfs with RtAudio 6 (currently in experimental). > > ``` > [ 89%] Building CXX object > src/modules/rtaudio/CMakeFiles/mltrtaudio.dir/consumer_rtaudio.cpp.o > cd /build/mlt-zme0kO/mlt-7.18.0/obj-x86_64-linux-gnu/src/modules/rtaudio > && /usr/lib/ccache/c++ -Dmltrtaudio_EXPORTS > -I/build/mlt-zme0kO/mlt-7.18.0/src/framework/.. -isystem > /usr/include/rtaudio -g -O2 > -ffile-prefix-map=/build/mlt-zme0kO/mlt-7.18.0=. -fstack-protector-strong > -fstack-clash-protection -Wformat -Werror=format-security -fcf-protection > -Wdate-time -D_FORTIFY_SOURCE=2 -std=c++14 -fPIC -mmmx -msse -msse2 > -pthread -D__LINUX_ALSA__ -D__LINUX_PULSE__ -D__UNIX_JACK__ -D_REENTRANT > -MD -MT > src/modules/rtaudio/CMakeFiles/mltrtaudio.dir/consumer_rtaudio.cpp.o -MF > CMakeFiles/mltrtaudio.dir/consumer_rtaudio.cpp.o.d -o > CMakeFiles/mltrtaudio.dir/consumer_rtaudio.cpp.o -c > /build/mlt-zme0kO/mlt-7.18.0/src/modules/rtaudio/consumer_rtaudio.cpp > /build/mlt-zme0kO/mlt-7.18.0/src/modules/rtaudio/consumer_rtaudio.cpp: In > member function ‘bool RtAudioConsumer::create_rtaudio(RtAudio::Api, int, > int)’: > /build/mlt-zme0kO/mlt-7.18.0/src/modules/rtaudio/consumer_rtaudio.cpp:164:26: > error: ‘struct RtAudio::DeviceInfo’ has no member named ‘probed’ > 164 | i
Bug#1042012: libqt6opengl6-dev unavailable in debian unstable
Package: qt6-base-dev Version: 6.4.2+dfsg-16 Severity: grave Justification: renders package unusable libqt6opengl6-dev has been unavailable in sid for a bit now. The last available version was 6.4.2+dfsg-11 (which cannot be installed now due to version conflicts). -- System Information: Debian Release: trixie/sid APT prefers unstable APT policy: (500, 'unstable'), (1, 'experimental') Architecture: amd64 (x86_64) Kernel: Linux 6.4.4-3-siduction-amd64 (SMP w/12 CPU threads; PREEMPT) Locale: LANG=en_US.UTF-8, LC_CTYPE=en_US.UTF-8 (charmap=UTF-8), LANGUAGE not set Shell: /bin/sh linked to /usr/bin/dash Init: systemd (via /run/systemd/system) LSM: AppArmor: enabled Versions of packages qt6-base-dev depends on: ii libgl-dev 1.6.0-1 ii libglx-dev 1.6.0-1 ii libopengl-dev 1.6.0-1 ii libqt6concurrent6 6.4.2+dfsg-16 ii libqt6core6 6.4.2+dfsg-16 ii libqt6dbus6 6.4.2+dfsg-16 ii libqt6gui6 6.4.2+dfsg-16 ii libqt6network6 6.4.2+dfsg-16 ii libqt6openglwidgets6 6.4.2+dfsg-16 ii libqt6printsupport6 6.4.2+dfsg-16 ii libqt6sql6 6.4.2+dfsg-16 ii libqt6test6 6.4.2+dfsg-16 ii libqt6widgets6 6.4.2+dfsg-16 ii libqt6xml6 6.4.2+dfsg-16 ii libvulkan-dev 1.3.250.0-1 ii qmake6 6.4.2+dfsg-16 ii qt6-base-dev-tools 6.4.2+dfsg-16 ii qt6-qpa-plugins 6.4.2+dfsg-16 qt6-base-dev recommends no packages. qt6-base-dev suggests no packages. -- no debconf information
Bug#1042012: Thanks
Thank you for the clarification and quick response.
Bug#1030129: (no subject)
Can this bug be backported to stable?
Bug#1057875: Remove this upstream deprecated package
Package: libgis-distance-perl Severity: grave On https://metacpan.org/pod/Geo::Distance is says Deprecated. The maintainer of this distribution has indicated that it is deprecated and no longer suitable for use. So it is time to remove this package from Debian! Thanks.
Bug#1057875: I'm not sure if I'm talking about Geo:: or Gis::
Sorry. I don't know if I am talking about Geo:: or Gis:: or libgeo or libgis. It is all too confusing. I'll leave it to others to straighten out.
Bug#1060173: ruby-hiredis FTBFS with hiredis 1.2.0-6
I examined this bug a bit. In test/reader_test.rb, test_nil / test_null_multi_bulk are both failing. If these tests are commented out, the package build will complete. Doesn't sound like a great idea though as it's not clear to me why these tests regressed. -Dan
Bug#558014: sasl2-bin: doesn't return from /etc/init.d/saslauthd start -> postinst script hangs
On 25/11/09 23:02 +0100, Dirk Dike wrote: Package: sasl2-bin Version: 2.1.22.dfsg1-8+etch1 Severity: critical Justification: breaks unrelated software # /etc/init.d/saslauthd start saslauthd[28763] :main: num_procs : 5 saslauthd[28763] :main: mech_option: NULL saslauthd[28763] :main: run_path : /var/run/saslauthd saslauthd[28763] :main: auth_mech : kerberos5 Have you customized your /etc/default/saslauthd? It appears that saslauthd is attempting to use the kerberos5 mech, which may in turn be hanging on a call to a kerberos library. -- Dan White -- To UNSUBSCRIBE, email to debian-bugs-rc-requ...@lists.debian.org with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org
Bug#550010: CONFIG_LBD has gone missing sometime after 2.6.18
$ ls /boot/config* /boot/config-2.6.18-6-amd64 /boot/config-2.6.29-2-amd64 /boot/config-2.6.26-1-amd64 /boot/config-2.6.30-1-amd64 $ grep LBD /boot/config* /boot/config-2.6.18-6-amd64:CONFIG_LBD=y Is it at all concerning that the sd driver tries a read capacity 16 and fails? I propose the following sequence of events: 1) 'sd' block device tries to read capacity 16 and fails because CONFIG_LBD is not asserted, defaulting to a size of 2TB 2) 'hfsplus' then tries to mount this larger-than-2TB filesystem and is successful 3) Writes to this inappropriately mounted filesystem fail once they run off of the edge I submit that the proposed patch is in error, and that hfsplus does very well support >2TB filesystems on Linux. Further, hfsplus and all filesystem drivers should check for the degenerate case of block device Dan Dennison
Bug#550010: HFS Plus supports a maximum volume size just south of 8EiB
FWIW, HFS Plus has a maximum size of (2^63 - 2^31) bytes, which is just shy of 8EB. http://support.apple.com/kb/HT2422 http://en.wikipedia.org/wiki/HFS_Plus dan :) -- To UNSUBSCRIBE, email to debian-bugs-rc-requ...@lists.debian.org with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org
Bug#550010: CONFIG_LBD has gone missing sometime after 2.6.18
-original message- From: "Ben Hutchings" b...@decadent.org.uk To: "Dan Dennison" d...@thedennisons.org, 550...@bugs.debian.org Date: Wed, 07 Oct 2009 23:02:40 +0100 - > CONFIG_LBD is irrelevant on 64-bit architectures. Good to know. >> I propose the following sequence of events: >> >> 1) 'sd' block device tries to read capacity 16 and fails because >> CONFIG_LBD is not asserted, defaulting to a size of 2TB So _something_else_ is causing read capacity 16 to fail in this case. Thoughts? dan :) -- To UNSUBSCRIBE, email to debian-bugs-rc-requ...@lists.debian.org with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org
Bug#551971: at: Segfaults when trying to execute task
Package: at Version: 3.1.11-1 Severity: grave Justification: renders package unusable This problem started after an apt-get upgrade. When the time for a task to run is reached, the console displays a message such as Oct 22 01:32:00 debian kernel: atd[21556]: segfault at b7f7eff4 ip b7fb5004 sp bfcd0c37 error 7 in ld-2.9.so[b7fb5000+1c000] and the task does not run. To uncover this bug, I used a task consisting of the single command ls. When 1:32:00 rolled over, the message above was displayed on the consle (and logged to the syslog) and the task was not run. In particular, atq reports that the task is still in the queue. cron seems to be experiencing similar issues at the moment. (See bug #551885) -- System Information: Debian Release: squeeze/sid APT prefers unstable APT policy: (990, 'unstable'), (500, 'stable'), (200, 'experimental') Architecture: i386 (i686) Kernel: Linux 2.6.26custom Locale: LANG=en_US, LC_CTYPE=en_US (charmap=ISO-8859-1) Shell: /bin/sh linked to /bin/bash Versions of packages at depends on: ii libc6 2.10.1-1 GNU C Library: Shared libraries ii libpam0g 1.1.0-4Pluggable Authentication Modules l ii lsb-base 3.2-23 Linux Standard Base 3.2 init scrip Versions of packages at recommends: ii exim4 4.69-11metapackage to ease Exim MTA (v4) ii exim4-daemon-light [mail-tran 4.69-11+b1 lightweight Exim MTA (v4) daemon at suggests no packages. -- no debconf information -- To UNSUBSCRIBE, email to debian-bugs-rc-requ...@lists.debian.org with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org
Bug#551971: at: Segfaults when trying to execute task
> > Please try /etc/init.d/atd restart? > That solved the problem. I have tried /etc/init.d/cron restart and that seems to be stopping the cron messages as well. -- To UNSUBSCRIBE, email to debian-bugs-rc-requ...@lists.debian.org with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org
Bug#564117: fails on a "large" install
Package: apt-listbugs Version: 0.1.2 Severity: normal Happened here, only the update wasn't a program with lots of dependencies, but rather an apt-get upgrade of the unstable distribution. 120 upgraded, 0 newly installed, 0 to remove and 38 not upgraded. 1 not fully installed or removed. Need to get 0B/32.3MB of archives. After this operation, 807kB of additional disk space will be used. Do you want to continue [Y/n]? y Reading package fields... 65%/usr/lib/ruby/1.8/debian/utils.rb:32:in `pipe': Too many open files (Errno::EMFILE) from /usr/lib/ruby/1.8/debian/utils.rb:32:in `pipeline' from /usr/lib/ruby/1.8/debian/utils.rb:71:in `gunzip' from /usr/lib/ruby/1.8/debian.rb:515:in `deb_fp' from /usr/lib/ruby/1.8/debian/ar.rb:146:in `open' from /usr/lib/ruby/1.8/debian/ar.rb:143:in `each' from /usr/lib/ruby/1.8/debian/ar.rb:143:in `open' from /usr/lib/ruby/1.8/debian.rb:514:in `deb_fp' from /usr/lib/ruby/1.8/debian.rb:528:in `control_fp' from /usr/lib/ruby/1.8/debian.rb:549:in `filename=' from /usr/lib/ruby/1.8/debian.rb:147:in `load' from /usr/lib/ruby/1.8/debian.rb:82:in `field' from /usr/share/apt-listbugs/apt-listbugs/logic.rb:729:in `field' from /usr/share/apt-listbugs/apt-listbugs/logic.rb:747:in `create' from /usr/share/apt-listbugs/apt-listbugs/logic.rb:739:in `each_index' from /usr/share/apt-listbugs/apt-listbugs/logic.rb:739:in `create' from /usr/sbin/apt-listbugs:323 E: Sub-process /usr/sbin/apt-listbugs apt || exit 10 returned an error code (10)E: Failure running script /usr/sbin/apt-listbugs apt || exit 10 -- System Information: Debian Release: squeeze/sid APT prefers unstable APT policy: (990, 'unstable'), (500, 'stable'), (200, 'experimental') Architecture: i386 (i686) Kernel: Linux 2.6.26custom Locale: LANG=en_US, LC_CTYPE=en_US (charmap=ISO-8859-1) Shell: /bin/sh linked to /bin/bash Versions of packages apt-listbugs depends on: ii apt 0.7.25 Advanced front-end for dpkg ii libdpkg-ruby1.8 0.3.4 modules/classes for dpkg on ruby 1 ii libgettext-ruby1.8 1.93.0-1.1 Gettext for ruby1.8 ii libhttp-access2-ruby1.8 2.1.5.2-1 HTTP accessing library for ruby (t ii libruby1.8 [libzlib-ruby1.8] 1.8.7.248-1 Libraries necessary to run Ruby 1. ii libxml-parser-ruby1.80.6.8-4 Interface of expat for the scripti ii ruby 4.2 An interpreter of object-oriented apt-listbugs recommends no packages. Versions of packages apt-listbugs suggests: ii debianutils 3.2.2Miscellaneous utilities specific t ii iceape-browser [www-browser 2.0.1-1 Iceape Navigator (Internet browser ii iceweasel [www-browser] 3.5.6-1 lightweight web browser based on M ii konqueror [www-browser] 4:4.3.4-1KDE 4's advanced file manager, web ii links2 [www-browser]2.2-1+b1 Web browser running in both graphi ii lynx-cur [www-browser] 2.8.8dev.2-1 Text-mode WWW Browser with NLS sup ii midori [www-browser]0.2.2-1 fast, lightweight graphical web br ii reportbug 4.10 reports bugs in the Debian distrib ii w3m [www-browser] 0.5.2-2.1WWW browsable pager with excellent ii xemacs21-mule [www-browser] 21.4.22-2highly customizable text editor -- -- no debconf information -- To UNSUBSCRIBE, email to debian-bugs-rc-requ...@lists.debian.org with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org
Bug#438336: [Kino-dev] Kino in Debian
On Sun, Jan 10, 2010 at 12:54 PM, Stefan Richter wrote: > David Liontooth wrote: >> Debian bug http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=438336 is >> preventing kino from entering squeeze. I can see from the versions listing on the bug page that the problem is that this version of Debian does not have a recent enough version of libraw1394. You need at least version 2.0.0. >> I noticed Stefan Richter posting here -- is it really the case that kino >> can't use the new firewire stack? > > The newer (now not so "new" anymore) firewire kernel drivers work very > well for applications like Kino and dvgrab now. They actually did for Of course, there will still be situations where some hardware/device combinations work in one subsystem but not another due to subtle interoperability bugs. > quite a while now. But I at least did not push distributors to move to > the new drivers for reasons that were unrelated to Kino et al (IPv4, > DVB, audio support --- all solved in recent kernel releases now). > > We have some information about this topic, targeted towards > distributors/ packagers and advanced users: > http://ieee1394.wiki.kernel.org/index.php/Juju_Migration > > Furthermore, the release notes give a detailed view on which > improvements and fixes came in which release: > http://ieee1394.wiki.kernel.org/index.php/Release_Notes > http://ieee1394.wiki.kernel.org/index.php/Release_Notes_-_Libraries > > For a works-out-of-the-box experience, kernel 2.6.31 (or later) and udev > 144 or later are very much recommended. At these versions, proper > mechanisms and policies for user access to FireWire devices arrived in > mainline udev. (Somewhat late, sorry for that. Other rules which are > not part of mainline udev can achieve the same with older kernels, as > documented in the kernel wiki.) > -- > Stefan Richter > -=-==-=- ---= -=-=- > http://arcgraph.de/sr/ > > -- > This SF.Net email is sponsored by the Verizon Developer Community > Take advantage of Verizon's best-in-class app development support > A streamlined, 14 day to market process makes app distribution fast and easy > Join now and get one step closer to millions of Verizon customers > http://p.sf.net/sfu/verizon-dev2dev > ___ > Kino-dev mailing list > kino-...@lists.sourceforge.net > https://lists.sourceforge.net/lists/listinfo/kino-dev > -- +-DRD-+ -- To UNSUBSCRIBE, email to debian-bugs-rc-requ...@lists.debian.org with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org
Bug#565477: apt-listbugs: After removal, breaks apt-get.
Package: apt-listbugs Severity: critical Justification: breaks unrelated software On a system on which the current unstable version of apt-listbugs has been removed (via apt-get remove apt-listbugs), apt-get still attempts to execute the non-existent apt-listbugs program, which of course does not exist. Specifically, I get the following error meesages whenever I attempt to install software with apt-get: /bin/sh: /usr/sbin/apt-listbugs: No such file or directory E: Sub-process /usr/sbin/apt-listbugs apt || exit 10 returned an error code(10) E: Failure running script /usr/sbin/apt-listbugs apt || exit 10 To reproduce, install apt-listbugs, then do: # apt-get remove apt-listbugs then try to install another program. In order to get apt-get usable afterwords, I had to create an empty file at /usr/sbin/apt-listbugs and make it executable. -- System Information: Debian Release: squeeze/sid APT prefers unstable APT policy: (990, 'unstable'), (500, 'stable'), (200, 'experimental') Architecture: i386 (i686) Kernel: Linux 2.6.26custom Locale: LANG=en_US, LC_CTYPE=en_US (charmap=ISO-8859-1) Shell: /bin/sh linked to /bin/bash Versions of packages apt-listbugs depends on: ii apt 0.7.25.1Advanced front-end for dpkg ii libdpkg-ruby1.8 0.3.4 modules/classes for dpkg on ruby 1 ii libgettext-ruby1.8 1.93.0-1.1 Gettext for ruby1.8 ii libhttp-access2-ruby1.8 2.1.5.2-1 HTTP accessing library for ruby (t ii libruby1.8 [libzlib-ruby1.8] 1.8.7.248-1 Libraries necessary to run Ruby 1. ii libxml-parser-ruby1.80.6.8-4 Interface of expat for the scripti ii ruby 4.2 An interpreter of object-oriented apt-listbugs recommends no packages. Versions of packages apt-listbugs suggests: ii debianutils 3.2.2Miscellaneous utilities specific t ii iceape-browser [www-browser 2.0.1-1 Iceape Navigator (Internet browser ii iceweasel [www-browser] 3.5.6-1 lightweight web browser based on M ii konqueror [www-browser] 4:4.3.4-1KDE 4's advanced file manager, web ii links2 [www-browser]2.2-1+b1 Web browser running in both graphi ii lynx-cur [www-browser] 2.8.8dev.2-1 Text-mode WWW Browser with NLS sup ii midori [www-browser]0.2.2-1 fast, lightweight graphical web br ii reportbug 4.10.1 reports bugs in the Debian distrib ii w3m [www-browser] 0.5.2-2.1WWW browsable pager with excellent ii xemacs21-mule [www-browser] 21.4.22-2highly customizable text editor -- -- To UNSUBSCRIBE, email to debian-bugs-rc-requ...@lists.debian.org with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org
Bug#589896: [Pkg-alsa-devel] Bug#589896: Bug#589896: openarena: segfaults when using pulse-via-ALSA output and PulseAudio capture
[Apologies for top-posting due to broken MUA] Please see http://git.alsa-project.org/?p=alsa-lib.git;a=commitdiff_plain;h=91c9c8f1b85e69b4bdc94a777d2767c4906c3f47 which was just raised on the alsa-devel mailing list. -D - Original Message From: Simon McVittie To: 589...@bugs.debian.org Sent: Sat, August 21, 2010 2:07:03 PM Subject: [Pkg-alsa-devel] Bug#589896: Bug#589896: openarena: segfaults when using pulse-via-ALSA output and PulseAudio capture (You didn't cc me or the bug, so I didn't see this until I tried replying with bts show --mbox to attach a proposed patch; please cc bugs and submitters if you expect a response :-) On Fri, 20 Aug 2010 at 23:56:02 +0200, Elimar Riesebieter wrote: > There are already bugs in thet ALSA-BTS. So what do you expect? > Another forward? I've tested openarena on my ppc-box and can't > reproduce. I suggested removing the call to snd_dlobj_cache_cleanup(); I've now tested this and confirmed that it works, see attached (trivial) patch. -- To UNSUBSCRIBE, email to debian-bugs-rc-requ...@lists.debian.org with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org
Bug#581229: [moodle-packaging] Bug#581229: Needs to be actively maintained to be included in Squeeze
On Thu, Jun 24, 2010 at 10:23 PM, Moritz Muehlenhoff wrote: > I'm reopening this bug for now: > > It's been now over a week that new Moodle security issues have been > reported for which there is no visible action from your side. > > Plus, you haven't gotten in contact with the Security Team as how > to fix the numerous open security bugs in stable. We require better > for an application like Moodle. Just for info as it hasn't been mentioned on this bug yet before there is an (relatively recent orphan bug here: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=574969 -- To UNSUBSCRIBE, email to debian-bugs-rc-requ...@lists.debian.org with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org
Bug#784587: [Pkg-utopia-maintainers] Bug#784587: network-manager: does not set up resolv.conf
On Thu, 2015-05-07 at 13:15 +0900, Norbert Preining wrote: > On Thu, 07 May 2015, Michael Biebl wrote: > > The attached patch should fix the issue. Will poke upstream for a review > > and upload tomorrow. > > Thanks for the quick fix! Got found and fixed yesterday in nm-1-0... In git master there is no longer fallback if resolvconf fails for some reason; but the resolv.conf manager is now a config option. So we'd expect distros to ship a sub-package that drops a config snippet into /etc/NetworkManager/conf.d/ enabling resolvconf which also requires the resolvconf package itself, so that when the config option is set, resolvconf is always installed. We may need some tweaking of the default handling here, but the idea is that if the user specifically chose resolvconf and it fails, that should be a hard failure and NM shouldn't be touching resolv.conf since the user told NM not to... Dan -- To UNSUBSCRIBE, email to debian-bugs-rc-requ...@lists.debian.org with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org
Bug#784587: [Pkg-utopia-maintainers] Bug#784587: Bug#784587: network-manager: does not set up resolv.conf
On Thu, 2015-05-07 at 19:08 +0200, Michael Biebl wrote: > Hi Dan! > > Am 07.05.2015 um 18:09 schrieb Dan Williams: > > On Thu, 2015-05-07 at 13:15 +0900, Norbert Preining wrote: > >> On Thu, 07 May 2015, Michael Biebl wrote: > >>> The attached patch should fix the issue. Will poke upstream for a review > >>> and upload tomorrow. > >> > >> Thanks for the quick fix! > > > > Got found and fixed yesterday in nm-1-0... > > Hm, I don't do any changes in the nm-1-0 related to that. Where those > fixes not pushed? Yeah, that was it. Pushed now. > > In git master there is no longer fallback if resolvconf fails for some > > reason; but the resolv.conf manager is now a config option. So we'd > > expect distros to ship a sub-package that drops a config snippet > > into /etc/NetworkManager/conf.d/ enabling resolvconf which also requires > > the resolvconf package itself, so that when the config option is set, > > resolvconf is always installed. We may need some tweaking of the > > default handling here, but the idea is that if the user specifically > > chose resolvconf and it fails, that should be a hard failure and NM > > shouldn't be touching resolv.conf since the user told NM not to... > > I kind of liked the if-resolvconf-found-use-it behaviour. > The new behaviour will be a bit icky if I go the subpackage route due to > how conffiles are handled. > conffiles (config files in /etc/) are not automatically removed by dpkg > if the package is removed (they are only removed on purge). > So if the user uninstalles (but doesn't purge) the sub-package, the > conf.d snippet will stay around and he'll get resolv.conf failures > because it's no longer guaranteed the resolvconf package is installed. Hmm, ok. I guess we'll have to allow fallback to writing resolvconf if the executable doesn't exist. dan -- To UNSUBSCRIBE, email to debian-bugs-rc-requ...@lists.debian.org with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org
Bug#785265: xorg: SEG FAULT! CANNOT USE X!
Package: xorg Version: 1:7.7+9 Severity: grave Justification: renders package unusable Starting today I cannot use X windows, thus cannot do almost anything anymore! Furthermore it is not clear which package I need to revert to its previous version to be able to hardly use my computer anymore! -- Package-specific info: X server symlink status: lrwxrwxrwx 1 root root 13 2013-07-27 /etc/X11/X -> /usr/bin/Xorg -rwxr-xr-x 1 root root 2544344 05-05 06:49 /usr/bin/Xorg VGA-compatible devices on PCI bus: -- 00:05.0 VGA compatible controller [0300]: NVIDIA Corporation C51G [GeForce 6100] [10de:0242] (rev a2) /etc/X11/xorg.conf does not exist. /etc/X11/xorg.conf.d does not exist. /etc/modprobe.d contains no KMS configuration files. Kernel version (/proc/version): --- Linux version 4.0.0-1-686-pae (debian-ker...@lists.debian.org) (gcc version 4.9.2 (Debian 4.9.2-16) ) #1 SMP Debian 4.0.2-1 (2015-05-11) Xorg X server log files on system: -- -rw-r--r-- 1 root root 24454 05-14 07:41 /var/log/Xorg.0.log Contents of most recent Xorg X server log file (/var/log/Xorg.0.log): - [94.673] X.Org X Server 1.17.1 Release Date: 2015-02-10 [94.673] X Protocol Version 11, Revision 0 [94.673] Build Operating System: Linux 3.16.0-4-amd64 i686 Debian [94.673] Current Operating System: Linux jidanni6 4.0.0-1-686-pae #1 SMP Debian 4.0.2-1 (2015-05-11) i686 [94.673] Kernel command line: BOOT_IMAGE=/boot/vmlinuz-4.0.0-1-686-pae root=UUID=d1f948b9-ebb5-45d8-bf20-035d65853302 ro panic=33 [94.673] Build Date: 04 May 2015 10:46:42PM [94.673] xorg-server 2:1.17.1-2 (http://www.debian.org/support) [94.673] Current version of pixman: 0.32.6 [94.673]Before reporting problems, check http://wiki.x.org to make sure that you have the latest version. [94.673] Markers: (--) probed, (**) from config file, (==) default setting, (++) from command line, (!!) notice, (II) informational, (WW) warning, (EE) error, (NI) not implemented, (??) unknown. [94.673] (==) Log file: "/var/log/Xorg.0.log", Time: Thu May 14 07:41:52 2015 [94.673] (==) Using system config directory "/usr/share/X11/xorg.conf.d" [94.674] (==) No Layout section. Using the first Screen section. [94.674] (==) No screen section available. Using defaults. [94.674] (**) |-->Screen "Default Screen Section" (0) [94.674] (**) | |-->Monitor "" [94.674] (==) No monitor specified for screen "Default Screen Section". Using a default monitor configuration. [94.674] (==) Automatically adding devices [94.674] (==) Automatically enabling devices [94.674] (==) Automatically adding GPU devices [94.674] (WW) The directory "/usr/share/fonts/X11/cyrillic" does not exist. [94.674]Entry deleted from font path. [94.674] (==) FontPath set to: /usr/share/fonts/X11/misc, /usr/share/fonts/X11/100dpi/:unscaled, /usr/share/fonts/X11/75dpi/:unscaled, /usr/share/fonts/X11/Type1, /usr/share/fonts/X11/100dpi, /usr/share/fonts/X11/75dpi, built-ins [94.674] (==) ModulePath set to "/usr/lib/xorg/modules" [94.675] (II) The server relies on udev to provide the list of input devices. If no devices become available, reconfigure udev or disable AutoAddDevices. [94.675] (II) Loader magic: 0xb7709700 [94.675] (II) Module ABI versions: [94.675]X.Org ANSI C Emulation: 0.4 [94.675]X.Org Video Driver: 19.0 [94.675]X.Org XInput driver : 21.0 [94.675]X.Org Server Extension : 9.0 [94.675] (II) xfree86: Adding drm device (/dev/dri/card0) [94.678] (--) PCI:*(0:0:5:0) 10de:0242:: rev 162, Mem @ 0xfc00/16777216, 0xd000/268435456, 0xfb00/16777216, BIOS @ 0x/131072 [94.678] (II) LoadModule: "glx" [94.678] (II) Loading /usr/lib/xorg/modules/extensions/libglx.so [94.681] (II) Module glx: vendor="X.Org Foundation" [94.681]compiled for 1.17.1, module version = 1.0.0 [94.681]ABI class: X.Org Server Extension, version 9.0 [94.681] (==) AIGLX enabled [94.681] (==) Matched nouveau as autoconfigured driver 0 [94.681] (==) Matched nv as autoconfigured driver 1 [94.681] (==) Matched nouveau as autoconfigured driver 2 [94.681] (==) Matched nv as autoconfigured driver 3 [94.681] (==) Matched modesetting as autoconfigured driver 4 [94.681] (==) Matched fbdev as autoconfigured driver 5 [94.681] (==) Matched vesa as autoconfigured driver 6 [94.681] (==) Assigned the driver to the xf86ConfigLayout [94.681] (II) LoadModule: "nouveau" [94.681] (WW) Warning, couldn't open module nouveau [94.682] (II) UnloadModule: "nouveau" [94.682] (II) Unloading nouveau [94.682] (EE) Failed to load module "nouveau" (mo
Bug#785266: libnettle4: seg fault
Package: libnettle4 Version: 2.7.1-5 Severity: grave $ wget [ 904.343687] wget[2256]: segfault at 10 ip b763f788 sp bfbac250 error 4 in libnettle.so.4.7[b761d000+33000] -- System Information: Debian Release: stretch/sid Architecture: i386 (i686) Kernel: Linux 4.0.0-1-686-pae (SMP w/1 CPU core) Locale: LANG=zh_TW.UTF-8, LC_CTYPE=zh_TW.UTF-8 (charmap=UTF-8) Shell: /bin/sh linked to /bin/bash Init: systemd (via /run/systemd/system) Versions of packages libnettle4 depends on: ii libc6 2.21-0experimental0 ii multiarch-support 2.21-0experimental0 libnettle4 recommends no packages. libnettle4 suggests no packages. -- no debconf information -- To UNSUBSCRIBE, email to debian-bugs-rc-requ...@lists.debian.org with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org
Bug#760538: [Ceph-maintainers] Bug#760538: Bug#760538: ceph maintainer address redirects to a closed list
On 11/14/2014 01:36 PM, Clint Adams wrote: > Control: severity 760538 serious > > On Tue, Sep 09, 2014 at 03:31:39PM +1000, Dmitry Smirnov wrote: >> Thanks but how do you justify severity level? "serious" may affect unstable- >> to-testing migration so I'm lowering severity to "important". > > It is serious because it is a violation of Policy §3.3. > >> Besides those who subscribed to ceph bug reports will get all updates from >> bug >> tracker anyway. Since bug reports are not subject to moderation I don't see >> a >> big problem here. > > This appears to be incorrect, since I received a bounce message > after submitting a bug report. 1) presumably it was a moderation message, not a bounce, and your message has been approved, and your address is now on the whitelist 2) bug report email doesn't flow through ceph-maintainers 3) this addresses spam and member removal from spam noise quite nicely, and messages are rarely held up for more than a few hours. Is there really a problem here? -- To UNSUBSCRIBE, email to debian-bugs-rc-requ...@lists.debian.org with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org
Bug#760538: [Ceph-maintainers] Bug#760538: Bug#760538: Bug#760538: ceph maintainer address redirects to a closed list
-BEGIN PGP SIGNED MESSAGE- Hash: SHA512 On 11/14/2014 03:16 PM, Dmitry Smirnov wrote: > On Fri, 14 Nov 2014 14:49:24 Dan Mick wrote: >>>> It is serious because it is a violation of Policy §3.3. >> >> Further: please quote me the provision of 3.3 that this mailing >> list setup violates. > > I think he meant to refer to the following: > > The maintainer must be specified in the Maintainer control field > with their correct name and a working email address. The email > address given in the Maintainer control field must accept mail from > those role accounts in Debian used to send automated mails > regarding the package. This includes non-spam mail from the > bug-tracking system, all mail from the Debian archive maintenance > software, and other role accounts or automated processes that are > commonly agreed on by the project.[7] If one person or team > maintains several packages, they should use the same form of their > name and email address in the Maintainer fields of those packages. > > https://www.debian.org/doc/debian-policy/ch-binary.html#s-maintainer I > agree that that is a paragraph from section 3.3. As the address is clearly working, and accepts mail from the Debian automated mail accounts, I don't see how this remotely applies to human-submitted email at all. > I fail to see how it is in conflict with moderated list but I will > not object if someone considers switching mail list back to > non-moderated. > > Clint, please don't you worry, I see your bug reports just fine. > -BEGIN PGP SIGNATURE- Version: GnuPG v1 iQEcBAEBCgAGBQJUZo3nAAoJEFx+Dr1on4lNyRYH/iO4REHdceaEjuomGqMupBnH 6gdQWdoItD9gBnAVd4aSMuPrXKUfeVYN5fszz1C8CX4BfD4qJ1Gn8j5t76Zu9T4S zkI1EN8ipY4wcOFv/c8rFNCWxAKC2f9b4cHv1/LslxI3D/mPymT131oNSFrqVfDl KIZZDIGt1FS+ooLYcXTO70DPE47OG219o6fQMlqBgyMhmsjKQDJXlcWXj0HOO9i1 3LpnV8Jitgr2hCS6uxLJTA4ZWwWWOdPqqJwm4yemsFHOWBJpEf9pP3eyZRuKxGmo 5pNgf3xYxAqpo3gQa3sCSLtkwxJ5DWV1xyTorAatAWo/ZXGNZg+Oi0BWzW94hDk= =Lfi5 -END PGP SIGNATURE- -- To UNSUBSCRIBE, email to debian-bugs-rc-requ...@lists.debian.org with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org
Bug#770185: linux-image-3.2.0-4-kirkwood: Unknown symbol ip_idents_reserve breaks IPv6
Package: src:linux Version: 3.2.63-2+deb7u1 Severity: grave Tags: ipv6 Justification: renders package unusable Dear Maintainer, the package introduces unmet symbol dependencies for the ipv6 kernel module and hence breaks IPv6 support. This appears to be caused by the inclusion of a Debian specific patch 'drivers-net-ipv6-select-ipv6-fragment-idents-for-vir.patch' written by Ben Hutchings . Downgrading to version 3.2.60-1+deb7u3 appears to be the only remedy. Many thanks. -- Package-specific info: ** Version: Linux version 3.2.0-4-kirkwood (debian-ker...@lists.debian.org) (gcc version 4.6.3 (Debian 4.6.3-14) ) #1 Debian 3.2.57-3+deb7u1 ** Command line: console=ttyS0,115200 ** Not tainted ** Kernel log: [ 24.361697] usbcore: registered new interface driver snd-usb-audio [ 24.517306] libertas_sdio mmc0:0001:1: firmware: agent aborted loading libertas/sd8688_helper.bin (not found?) [ 24.565007] libertas_sdio mmc0:0001:1: firmware: agent aborted loading sd8688_helper.bin (not found?) [ 24.574442] libertas_sdio: failed to find firmware (-2) [ 24.583236] libertas_sdio: probe of mmc0:0001:1 failed with error -2 [ 24.602645] Bluetooth: vendor=0x2df, device=0x9105, class=255, fn=2 [ 24.668293] btmrvl_sdio mmc0:0001:2: firmware: agent aborted loading sd8688_helper.bin (not found?) [ 25.253582] Adding 1049084k swap on /dev/sda2. Priority:-1 extents:1 across:1049084k SS [ 25.328307] EXT4-fs (sdb2): re-mounted. Opts: (null) [ 25.594492] EXT4-fs (sdb2): re-mounted. Opts: errors=remount-ro [ 25.822865] loop: module loaded [ 28.600446] EXT4-fs (sda1): warning: maximal mount count reached, running e2fsck is recommended [ 28.610013] EXT4-fs (sda1): mounted filesystem with ordered data mode. Opts: discard,data=ordered,errors=remount-ro [ 30.020234] ipv6: Unknown symbol ip_idents_reserve (err 0) [ 30.040902] ipv6: Unknown symbol ip_idents_reserve (err 0) [ 30.087839] ipv6: Unknown symbol ip_idents_reserve (err 0) [ 30.320561] ipv6: Unknown symbol ip_idents_reserve (err 0) [ 30.342165] ipv6: Unknown symbol ip_idents_reserve (err 0) [ 30.408901] RPC: Registered named UNIX socket transport module. [ 30.414855] RPC: Registered udp transport module. [ 30.419631] RPC: Registered tcp transport module. [ 30.424359] RPC: Registered tcp NFSv4.1 backchannel transport module. [ 30.470326] FS-Cache: Loaded [ 30.538512] FS-Cache: Netfs 'nfs' registered for caching [ 30.583836] Installing knfsd (copyright (C) 1996 o...@monad.swb.de). [ 32.957724] mv643xx_eth_port mv643xx_eth_port.1: eth1: link up, 1000 Mb/s, full duplex, flow control disabled [ 34.769176] ipv6: Unknown symbol ip_idents_reserve (err 0) [ 35.017457] ipv6: Unknown symbol ip_idents_reserve (err 0) [ 38.599557] ipv6: Unknown symbol ip_idents_reserve (err 0) [ 42.329340] ipv6: Unknown symbol ip_idents_reserve (err 0) [ 43.676240] ipv6: Unknown symbol ip_idents_reserve (err 0) [ 54.137370] ipv6: Unknown symbol ip_idents_reserve (err 0) [ 54.177423] ipv6: Unknown symbol ip_idents_reserve (err 0) [ 58.147370] ipv6: Unknown symbol ip_idents_reserve (err 0) [ 58.213917] ipv6: Unknown symbol ip_idents_reserve (err 0) [ 58.867175] ipv6: Unknown symbol ip_idents_reserve (err 0) [ 58.917969] ipv6: Unknown symbol ip_idents_reserve (err 0) [ 60.548808] ipv6: Unknown symbol ip_idents_reserve (err 0) [ 61.044748] ipv6: Unknown symbol ip_idents_reserve (err 0) [ 61.176379] ipv6: Unknown symbol ip_idents_reserve (err 0) [ 75.308553] ipv6: Unknown symbol ip_idents_reserve (err 0) [ 75.371951] ipv6: Unknown symbol ip_idents_reserve (err 0) [ 88.766351] ipv6: Unknown symbol ip_idents_reserve (err 0) [ 99.726306] The scan_unevictable_pages sysctl/node-interface has been disabled for lack of a legitimate use case. If you have one, please send an email to linux...@kvack.org. [ 191.458947] ipv6: Unknown symbol ip_idents_reserve (err 0) [ 779.571632] ipv6: Unknown symbol ip_idents_reserve (err 0) [ 874.047456] ipv6: Unknown symbol ip_idents_reserve (err 0) [ 874.109899] ipv6: Unknown symbol ip_idents_reserve (err 0) [ 1040.791628] ipv6: Unknown symbol ip_idents_reserve (err 0) [ 1560.301116] ipv6: Unknown symbol ip_idents_reserve (err 0) [ 1734.276133] ipv6: Unknown symbol ip_idents_reserve (err 0) [ 1734.339141] ipv6: Unknown symbol ip_idents_reserve (err 0) [ 2240.469869] ipv6: Unknown symbol ip_idents_reserve (err 0) [ 2341.065607] ipv6: Unknown symbol ip_idents_reserve (err 0) [ 2642.217421] ipv6: Unknown symbol ip_idents_reserve (err 0) [ 2642.341013] ipv6: Unknown symbol ip_idents_reserve (err 0) [ 3121.831884] ipv6: Unknown symbol ip_idents_reserve (err 0) [ 3440.280069] ipv6: Unknown symbol ip_idents_reserve (err 0) [ 3539.840499] ipv6: Unknown symbol ip_idents_reserve (err 0) [ 3539.905766] ipv6: Unknown symbol ip_idents_reserve (err 0) [ 3902.719434] ipv6: Unknown symbol ip_idents_reserve (err 0) [ 4107.627900] ipv6: Unknown symbol ip_idents_reserve (err 0) [ 4446.188858] ipv6: Un
Bug#770035: [Mlt-devel] Bug#770035: kdenlive: Processed videos have image pauses or accelerations while sound goes well
No. I do not know how to reproduce the problem. The bug reporter needs to narrow down the problem. Is it something in the project, something related specifically to those source files, or something related to that combination of MLT and Libav versions? I do consider the usage of the latest versions of Libav and FFmpeg with MLT somewhat experimental. On Wed, Nov 19, 2014 at 6:03 AM, Patrick Matthäi wrote: > Hi Dan, > > do you have an idea to http://bugs.debian.org/770035 ? > > Am 19.11.2014 um 14:54 schrieb Javier Ortega Conde (Malkavian): > >Could you retest it with the libmlt*, mlt*, melt* packages from >> experimental (not jessie/sid)? >> > > Done, and problem persists. > > >
Bug#692626: non-free files in upstream tarball ("The Software shall be used for Good, not Evil")
We have resolved this upstream in version 2.4 (http://tracker.moodle.org/browse/MDL-36457). We will consider back-porting this in http://tracker.moodle.org/browse/MDL-36463 -- To UNSUBSCRIBE, email to debian-bugs-rc-requ...@lists.debian.org with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org
Bug#693770: dvgrab: Does no longer work
It already works great with the new subsystem. In fact it was the first application to really work with it. Your source is simply wrong. Also the real porting effort went into libraw1394 2.0 and not the apps. On Wednesday, November 21, 2012, Erik Schanze (Debian) wrote: > Hi Dan, > > [Please keep at least 693770-forwar...@bugs.debian.org in > CC.] > > I'm the Debian Maintainer for dvgrab. > I have received a bugreport for it. > Since ieee1394 driver was removed from Linux 2.6.37 it > is not possible to use dvgrab any more. > > Unfortunately there is no new version since 2010. > > Are there plans to port dvgrab to new FireWire stack? > > Thank you in advance, > > Erik > > > > Am 20.11.2012 07:06, schrieb Matthias Urlichs: > > Package: dvgrab > > Severity: grave > > Justification: renders package unusable > > > > Linux 2.6.37 removed the ieee1394 driver. > > dvgrab does not work with the new firewire subsystem. > > It's therefore 100% useless and should be removed. > > > > -- System Information: > > Debian Release: wheezy/sid > > APT prefers testing > > APT policy: (700, 'testing'), (650, 'unstable'), (600, 'stable'), > (550, 'experimental') > > Architecture: amd64 (x86_64) > > > > Kernel: Linux 3.6-trunk-amd64 (SMP w/2 CPU cores) > > Locale: LANG=en_US.UTF-8, LC_CTYPE=de_DE.UTF-8 (charmap=UTF-8) (ignored: > LC_ALL set to en_US.UTF-8) > > Shell: /bin/sh linked to /bin/dash > > > > > > Freundlich grüßend, > > Erik > > -- +-DRD-+
Bug#754565: [moodle-packaging] Bug#754565: Bug#754565: Non free icc profile
Hi Riley, On 22 January 2015 at 06:34, Riley Baird wrote: > P.S. I tried writing a message on the moodle forums to give them a heads > up on the situation, but the spam filter stopped me. It told me to send > my post to he...@moodle.org, so hopefully it will still get through. 'Upstream' here. Apologies that you got hit by a spam filter (I'm afraid we were getting hit quite aggressively by first time link spammers which is probably the cause of your filtering). Thank you very much for trying to get in touch with us. I've been cc'd on the Moodle debian bugs for quite some time and i'm afraid that this is a bit of a cycle with the package. Quite some time ago I was part of a team to keep up with keeping the package in order, but eventually could not keep on top of it - then others like Tomasz Muras and Thijs Kinkhorst have valiantly tried to get it in order. See #494642 #647489 #747084 etc. So much as it saddens me - I think this is the right course of action. There is little evidence to suggest that the package is widely used which makes it even less motivating for contributors for the significant amount of work it takes to keep up with our wide ranging upstream security fixes. cheers, Dan Poltawski -- To UNSUBSCRIBE, email to debian-bugs-rc-requ...@lists.debian.org with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org
Bug#754565: Fwd: future of Moodle in Debian stable/unstable (was: Re: [moodle-packaging] Bug#754565: Bug#754565: Bug#754565: Non free icc profile)
Hi Joost, On Wed, Feb 4, 2015 at 8:54 AM, Joost van Baal-Ilić wrote: > I am currently working on packaging latest moodle & keeping it up to date in > Debian unstable, see https://packages.debian.org/sid/moodle and especially > http://metadata.ftp-master.debian.org/changelogs//main/m/moodle/moodle_2.7.5+dfsg-1_changelog > for what I did. At Tilburg University we are running moodle on some Debian > systems; we have an interest in keeping it working for us. I basically took > over the work from Thijs. Thank you! Please feel free to get in touch with me if we can be of help. ps. Noting Rileys post on moodle.org was eventually posted here: https://moodle.org/mod/forum/discuss.php?d=278847 cheers, Dan -- To UNSUBSCRIBE, email to debian-bugs-rc-requ...@lists.debian.org with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org
Bug#760998: [Pkg-utopia-maintainers] Bug#760998: Acknowledgement (network-manager: auto restarts)
On Mon, 2015-03-09 at 09:13 +0100, Michael Biebl wrote: > Am 19.02.2015 um 07:35 schrieb Kurt Roeckx: > > severity 760998 serious > > thanks > > > > At this point I'm unable to stop network manager and keep it > > stopped. Now I have 0.9.10.0-6. > > > > The log file shows: > > NetworkManager[15359]: exiting (success) > > systemd[1]: Stopped Network Manager. > > dbus[658]: [system] Activating via systemd: service > > name='org.freedesktop.NetworkManager' > > unit='dbus-org.freedesktop.NetworkManager.service' > > systemd[1]: Starting Network Manager... > > dbus[658]: [system] Successfully activated service > > 'org.freedesktop.nm_dispatcher' > > systemd[1]: Started Network Manager Script Dispatcher Service. > > NetworkManager[20467]: NetworkManager (version 0.9.10.0) is > > starting... > > > > I assume something else restarts it, but I have no idea what. Is > > there some way to debug this so I can reassign it? > > It's most likely D-Bus activated, e.g. by nm-applet. > > Atm, you need to run "systemctl disable NetworkManager.service; > systemctl stop NetworkManager.service; ; systemctl start > NetworkManager.service; systemctl enable NetworkManager.service". > > Dan, is dropping the D-Bus autoactivation safe, i.e. removing > /usr/share/dbus-1/system-services/org.freedesktop.NetworkManager.service? Yeah, it's safe, though it might slightly slow your bootup for some reason I don't remember. Something about not being able to parallelize bootup, because if something calls NM methods via D-Bus, systemd won't be able to activate NM and block the receiving process until NM starts, so the receiving process will just get an error instead of waiting. But I guess that's supposed to be the current situation too with our Exec=/bin/false hack that hasn't worked in a while. It's worth a try to remove that file, and change the systemd unit file's [install] section to remove the Alias. Let me know if that breaks bootup horribly or something? Dan -- To UNSUBSCRIBE, email to debian-bugs-rc-requ...@lists.debian.org with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org
Bug#746594: [moodle-packaging] Bug#746594: Embedded OLE is not DFSG-compliant (PHP-2.02)
Hi, On 2 May 2014 02:46, David Prévot wrote: > The embedded PHPExcel copy (#718585) embeds OLE (#487558) which is not > DFSG compliant (PHP-2.02)[1,2]. We have removed this library in upstream in version 2.6: https://tracker.moodle.org/browse/MDL-42381 http://git.moodle.org/gw?p=moodle.git;a=commit;h=383d414478f1f3129f243e4d047d4fa06b9a3b8f It wasn't used and can be safely deleted. Is there another instance of this library or is it a packaging problem? cheers, Dan -- To UNSUBSCRIBE, email to debian-bugs-rc-requ...@lists.debian.org with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org
Bug#746594: [moodle-packaging] Bug#746594: Bug#746594: Embedded OLE is not DFSG-compliant (PHP-2.02)
forwarded 746594 https://tracker.moodle.org/browse/MDL-45395 On 2 May 2014 21:50, Thijs Kinkhorst wrote: > It's indeeed a second copy, it's under lib/phpexcel/PHPExcel/Shared/ Thanks! Grr! I've created https://tracker.moodle.org/browse/MDL-45395 cheers, Dan -- To UNSUBSCRIBE, email to debian-bugs-rc-requ...@lists.debian.org with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org
Bug#796175: linux-image-3.16.0-4-amd64: ext4 filesystem corruption
Package: src:linux Version: 3.16.7-ckt11-1+deb8u3 Severity: critical Justification: causes serious data loss Dear Maintainer, I have installed new system to little old HW. Connect 3 disks and made RAID5 array on top of this array I made volumegroup data. Create volume about 800G. Format it with ext4. And start copynig data. And after couple of hour I get this: [252440.711127] EXT4-fs warning (device dm-5): ext4_end_bio:317: I/O error -5 writing to inode 35913733 (offset 167268843520 size 3674112 starting block 95985792) [252440.711799] buffer_io_error: 246 callbacks suppressed [252440.712032] Buffer I/O error on device dm-5, logical block 95985792 [252440.712308] Buffer I/O error on device dm-5, logical block 95985793 [252440.712585] Buffer I/O error on device dm-5, logical block 95985794 [252440.712879] Buffer I/O error on device dm-5, logical block 95985795 [252440.713162] Buffer I/O error on device dm-5, logical block 95985796 [252440.713419] Buffer I/O error on device dm-5, logical block 95985797 [252440.713691] Buffer I/O error on device dm-5, logical block 95985798 [252440.713953] Buffer I/O error on device dm-5, logical block 95985799 [252440.714213] Buffer I/O error on device dm-5, logical block 95985800 [252440.714467] Buffer I/O error on device dm-5, logical block 95985801 [252440.714820] EXT4-fs warning (device dm-5): ext4_end_bio:317: I/O error -5 writing to inode 35913733 (offset 167268843520 size 3674112 starting block 95985664) And copying files fails. Switching to XFS solve problem. -- Package-specific info: ** Version: Linux version 3.16.0-4-amd64 (debian-ker...@lists.debian.org) (gcc version 4.8.4 (Debian 4.8.4-1) ) #1 SMP Debian 3.16.7-ckt11-1+deb8u3 (2015-08-04) ** Command line: BOOT_IMAGE=/vmlinuz-3.16.0-4-amd64 root=UUID=48055e75-93e4-4a4a-9ebf-7efc863d2b42 ro panic=60 rootdelay=20 acpi_enforce_resources=lax ** Not tainted ** Kernel log: [ 4805.480518] Buffer I/O error on device dm-5, logical block 90742918 [ 4805.480686] Buffer I/O error on device dm-5, logical block 90742919 [ 4805.480840] Buffer I/O error on device dm-5, logical block 90742920 [ 4805.481003] Buffer I/O error on device dm-5, logical block 90742921 [ 4805.481215] EXT4-fs warning (device dm-5): ext4_end_bio:317: I/O error -5 writing to inode 23594668 (offset 2684354560 size 2625536 starting block 90742784) [10102.928593] Key type dns_resolver registered [10102.948768] NFS: Registering the id_resolver key type [10102.948945] Key type id_resolver registered [10102.949047] Key type id_legacy registered [11653.573226] perf interrupt took too long (2509 > 2500), lowering kernel.perf_event_max_sample_rate to 5 [27739.440193] md: md2: recovery done. [27739.510050] RAID conf printout: [27739.510061] --- level:5 rd:3 wd:3 [27739.510066] disk 0, o:1, dev:sdi1 [27739.510068] disk 1, o:1, dev:sdh1 [27739.510070] disk 2, o:1, dev:sdj2 [31831.278461] EXT4-fs warning (device dm-5): ext4_end_bio:317: I/O error -5 writing to inode 23594668 (offset 25165824 size 2625536 starting block 90742912) [31831.278997] buffer_io_error: 246 callbacks suppressed [31831.279227] Buffer I/O error on device dm-5, logical block 90742912 [31831.279488] Buffer I/O error on device dm-5, logical block 90742913 [31831.279736] Buffer I/O error on device dm-5, logical block 90742914 [31831.279988] Buffer I/O error on device dm-5, logical block 90742915 [31831.280263] Buffer I/O error on device dm-5, logical block 90742916 [31831.280528] Buffer I/O error on device dm-5, logical block 90742917 [31831.280802] Buffer I/O error on device dm-5, logical block 90742918 [31831.281106] Buffer I/O error on device dm-5, logical block 90742919 [31831.281399] Buffer I/O error on device dm-5, logical block 90742920 [31831.281657] Buffer I/O error on device dm-5, logical block 90742921 [31831.282003] EXT4-fs warning (device dm-5): ext4_end_bio:317: I/O error -5 writing to inode 23594668 (offset 25165824 size 2625536 starting block 90742784) [78659.737750] md/raid:md2: Disk failure on sdj2, disabling device. md/raid:md2: Operation continuing on 2 devices. [78660.145486] RAID conf printout: [78660.145494] --- level:5 rd:3 wd:2 [78660.145497] disk 0, o:1, dev:sdi1 [78660.145500] disk 1, o:1, dev:sdh1 [78660.145502] disk 2, o:0, dev:sdj2 [78660.156017] RAID conf printout: [78660.156020] --- level:5 rd:3 wd:2 [78660.156023] disk 0, o:1, dev:sdi1 [78660.156025] disk 1, o:1, dev:sdh1 [78665.891504] md: unbind [78665.900034] md: export_rdev(sdj2) [78748.981628] sdj: sdj1 [78796.295182] md: bind [78796.679036] RAID conf printout: [78796.679042] --- level:5 rd:3 wd:2 [78796.679045] disk 0, o:1, dev:sdi1 [78796.679048] disk 1, o:1, dev:sdh1 [78796.679050] disk 2, o:1, dev:sdj1 [78796.679754] md: recovery of RAID array md2 [78796.680046] md: minimum _guaranteed_ speed: 1000 KB/sec/disk. [78796.680392] md: using maximum available idle IO bandwidth (but not more than 20 KB/sec) for recovery. [78796.680712] md: using 128k window, over a to
Bug#785782:
I am now having this same problem. Gdm3 greeter shows no login prompt, no users. It happens on two different computers. gdm3: 3.14.2-2, amd64 The op's workaround doesn't work for me. Dan
Bug#785782:
Weird. It now works. It appears that an update of libpam-systemd solved the problem. Could that be it? Thanks. Dan
Bug#834928: This is fixed in ifupdown 0.8.11
This is a bug in ifupdown, not isc-dhcp-client. It's fixed in 0.8.11
by the change to ifupdown's wait-for-ll6.sh:
--- ifupdown-0.8.10/wait-for-ll6.sh 2015-12-01 16:50:26.0 -0500
+++ ifupdown-0.8.11/wait-for-ll6.sh 2016-04-20 08:57:37.0 -0400
@@ -4,7 +4,7 @@
delay=${IF_LL_INTERVAL:-0.1}
for attempt in $(seq 1 $attempts); do
- lladdress=$(ip -6 -o a s dev "$IFACE" scope link)
+ lladdress=$(ip -6 -o a s dev "$IFACE" scope link -tentative)
if [ -n "$lladdress" ]; then
attempt=0
break
Bug#674386: supercollider: FTBFS: scons: *** No SConstruct file found.
2012/8/12 peter green : >> >> I'd like to mark this as "won't fix" because we're dropping the scons >> build system. The latest version of supercollider 3.5.x (which I'm >> currently asking debian-multimedia maintainers to upload) uses cmake >> instead which is much less mess. >> > > Supercollider 1:3.5.2-1 was uploaded just before the freeze deadline, > however > it did not migrate to testing due to build failures. > > So if supercollider is going to release with wheezy you either need to open > discussions with the release team about either getting a freeze exception > for > the version in sid or making a TPU upload to fix the scons build system in > the wheezy package Thanks. I'm not very familiar with debian processes so I'd appreciate guidance from pkg-multimedia-maintainers on this. I don't know how to do either of the things you describe, or which is better. (What's TPU?) In git I made a branch "3.4debianfixes" which potentially contains a fix for the scons issue. Dan -- To UNSUBSCRIBE, email to debian-bugs-rc-requ...@lists.debian.org with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org
Bug#674386: supercollider: FTBFS: scons: *** No SConstruct file found.
2012/8/13 Felipe Sateler : > On Sun, Aug 12, 2012 at 5:37 PM, Dan S wrote: >> 2012/8/12 peter green : >>>> >>>> I'd like to mark this as "won't fix" because we're dropping the scons >>>> build system. The latest version of supercollider 3.5.x (which I'm >>>> currently asking debian-multimedia maintainers to upload) uses cmake >>>> instead which is much less mess. >>>> >>> >>> Supercollider 1:3.5.2-1 was uploaded just before the freeze deadline, >>> however >>> it did not migrate to testing due to build failures. >>> >>> So if supercollider is going to release with wheezy you either need to open >>> discussions with the release team about either getting a freeze exception >>> for >>> the version in sid or making a TPU upload to fix the scons build system in >>> the wheezy package >> >> Thanks. I'm not very familiar with debian processes so I'd appreciate >> guidance from pkg-multimedia-maintainers on this. I don't know how to >> do either of the things you describe, or which is better. (What's >> TPU?) In git I made a branch "3.4debianfixes" which potentially >> contains a fix for the scons issue. > > The basic process is described by Raphael Hertzhog at [1]. The > description, however, does not describe the current issue. What > happens if testing is frozen, there is a bug in the package in > testing, and there is a newer release in unstable? There are three > options: > > 1. Remove the software from testing (and therefore, from the next > stable release). > 2. Somehow convince the release team that the new version in unstable > should migrate to testing. > 3. Upload a localized fix to testing-proposed-updates (TPU for short, > a special "distribution" meant for fixes that cannot go through > unstable). > > > Each option has its benefits and drawbacks. The release team usually > prefers option 3. Rewriting the choices for our current situation, we > have: > > 1. Do not release supercollider in wheezy > 2. Somehow convince the rt that 3.5 should migrate. > 3. Ship 3.4 with the fix, via an upload to tpu. > > > As I see it, there are significant drawbacks with the standard option > (n° 3), because I'm not quite sure if 3.4 offers the best experience > for users. However, I'd prefer if you (Dan) made this call, because > you know sc much better, and thus can make a more informed decision. > At this point, option 2 looks very unlikely, though. We can try to do > it, but it is more likely that we will end up doing either 1 or 3. But > we need to be clear on which one to do. As discussed, 3.4 is not a fantastic package, but it does provide the core language+server, so option 1 seems pointless when bug #674386 apparently has a fix we can go straight for. I don't have any strong motivation to go into negotiations with the RT for option 2: although 3.4 is less than ideal, once it's shipped we can focus on making the 3.5 sid package great. So I suggest let's go for TPU. Dan -- To UNSUBSCRIBE, email to debian-bugs-rc-requ...@lists.debian.org with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org
Bug#691860: [PATCH] Remove non-free recommendation
tags 691860 + patch thanks flexbackup_1.2.1-6.1.debdiff Description: Binary data
Bug#710419: [Mlt-devel] Bug#710419: kdenlive: needs porting to use avconv executable (not ffmpeg)
On Thu, May 30, 2013 at 8:19 AM, Patrick Matthäi wrote: > Am 30.05.2013 18:02, schrieb Jonas Smedegaard: >> Package: kdenlive >> Severity: serious >> Justification: Renders (soon) the package unusable >> >> Kdenlive depends on ffmpeg executable for transcoding source material >> (and possibly other tasks as well). >> >> ffmpeg is targeted for removal, so kdenlive need adaptation to instead >> use avconv executable. >> >> - Jonas >> > > Hola mlt and kdenlive developers, > > are you aware of this issue? For myself, this is new! > Kdenlive is already compatible with avconv since version 0.9.4. So, if this is an upgrade request, then the justification makes perfect sense. MLT does not use libav/ffmpeg executables directly and is already compatible with both projects' libs. Or, are you just saying you are unaware of the libav fork? -- +-DRD-+ -- To UNSUBSCRIBE, email to debian-bugs-rc-requ...@lists.debian.org with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org
Bug#710419: [Mlt-devel] Bug#710419: kdenlive: needs porting to use avconv executable (not ffmpeg)
On Thu, May 30, 2013 at 11:14 AM, Patrick Matthäi wrote: > Am 30.05.2013 22:08, schrieb Dan Dennedy: >>> are you aware of this issue? For myself, this is new! >>> >> >> Kdenlive is already compatible with avconv since version 0.9.4. So, if >> this is an upgrade request, then the justification makes perfect >> sense. MLT does not use libav/ffmpeg executables directly and is >> already compatible with both projects' libs. Or, are you just saying >> you are unaware of the libav fork? > > Ah, nice to know, thanks for the information! > I remember that kdenlive and/or mlt used the ffmpeg binary (in the > past). I currently have not access to my Linux desktops, so I can not > check the current status, so is there anything I have to change at the > most up to date mlt and kdenlive packages to support this transition? Not that I am aware of, but I maybe you want to hear from one of the regular kdenlive devs. Yes, it is still compatible with ffmpeg executable. The Config Wizard looks for various helpers, and it first searches for ffmpeg and if that is not found, searches for avconv. Also, the wizard is re-run upon first launch after an upgrade. Lastly, the paths are configurable in Settings. -- +-DRD-+ -- To UNSUBSCRIBE, email to debian-bugs-rc-requ...@lists.debian.org with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org
Bug#728573: supercollider: FTBFS on sparc and ppc but built there in the past
2013/11/6 Felipe Sateler : > On Sun, Nov 3, 2013 at 7:44 AM, Dan S wrote: >> >> Thanks. As discussed previously on pkg-multimedia-maintainers, I >> propose that we restrict archs for one package >> "supercollider-supernova". The package is optional for users (it's a >> non-default drop-in alternative to "supercollider-server") and there >> is very little upstream support for getting it working across archs. >> It uses some fancy coding and boost libs that I'm not familiar with, >> and these are what incur these build fails. I know it would be great >> to avoid having to special-case any archs, but I don't see where the >> expertise will come from to do this, and supercollider is >> fully-functional without that package. > > I thought sc used the problematic boost libs elsewhere so this was not > really a workable solution... Hi all - just tested this on sparc/ppc porterboxes and the proposed fix works. I've pushed the fix to git.debian.org - please could I request a new upload, so that it's possible for the supercollider packages to go eventually to testing? Dan -- To UNSUBSCRIBE, email to debian-bugs-rc-requ...@lists.debian.org with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org
Bug#715424:
tags 715424 + patch thanks Hi all, attached is a debdiff against the current sid source package. It was recently uploaded to Ubuntu 14.04 and built successfully. Upstream 3.4rc1 does not appear to have any arm-related changes for this build failure. Cheers, --dan debdiff Description: Binary data
Bug#852152: kernel 4.9: NVIDIA: Failed to load the NVIDIA kernel module
Package: nvidia-legacy-304xx-kernel-dkms Version: 304.134-1 Severity: grave Even though your package Description says "Building the kernel module has been tested up to Linux 4.9." Maybe BUILDING yes, but not RUNNING, no. With 4.9 you will get: NVIDIA: Failed to load the NVIDIA kernel module P.S., https://wiki.debian.org/NvidiaGraphicsDrivers does not mention the case when $ cat /etc/debian_version 9.0 Only older versions. -- System Information: Debian Release: 9.0 APT prefers experimental APT policy: (990, 'experimental'), (500, 'unstable') Architecture: amd64 (x86_64) Kernel: Linux 4.9.0-1-amd64 (SMP w/1 CPU core) Locale: LANG=en_US.UTF-8, LC_CTYPE=zh_TW.UTF-8 (charmap=UTF-8) Shell: /bin/sh linked to /bin/bash Init: systemd (via /run/systemd/system) Versions of packages nvidia-legacy-304xx-kernel-dkms depends on: ii dkms 2.3-2 ii nvidia-installer-cleanup 20151021+4 ii nvidia-legacy-304xx-kernel-support [nvidia-legacy-304xx-kernel- 304.134-1 Versions of packages nvidia-legacy-304xx-kernel-dkms recommends: ii nvidia-legacy-304xx-driver 304.134-1 nvidia-legacy-304xx-kernel-dkms suggests no packages. Versions of packages nvidia-legacy-304xx-driver depends on: ii nvidia-installer-cleanup20151021+4 ii nvidia-legacy-304xx-alternative 304.134-1 ii nvidia-legacy-304xx-driver-bin 304.134-1 ii nvidia-legacy-304xx-driver-libs 304.134-1 ii nvidia-legacy-304xx-vdpau-driver304.134-1 ii nvidia-support 20151021+4 ii xserver-xorg-video-nvidia-legacy-304xx 304.134-1 Versions of packages nvidia-legacy-304xx-driver recommends: ii nvidia-persistenced 375.26-1 ii nvidia-settings-legacy-304xx 304.134-1 nvidia-legacy-304xx-driver suggests no packages. Versions of packages nvidia-legacy-304xx-driver-libs depends on: ii libgl1-nvidia-legacy-304xx-glx 304.134-1 Versions of packages nvidia-legacy-304xx-driver-libs recommends: ii libnvidia-legacy-304xx-cfg1 304.134-1 pn nvidia-legacy-304xx-driver-libs-i386 Versions of packages libgl1-nvidia-legacy-304xx-glx depends on: ii libc62.24-9 ii libnvidia-legacy-304xx-glcore304.134-1 ii libx11-6 2:1.6.4-2 ii libxext6 2:1.3.3-1 ii libxv1 2:1.0.11-1 ii libxvmc1 2:1.0.10-1 ii nvidia-installer-cleanup 20151021+4 ii nvidia-legacy-304xx-alternative 304.134-1 ii nvidia-support 20151021+4 libgl1-nvidia-legacy-304xx-glx recommends no packages. libgl1-nvidia-legacy-304xx-glx suggests no packages. Versions of packages xserver-xorg-video-nvidia-legacy-304xx depends on: ii libc6 2.24-9 ii libnvidia-legacy-304xx-glcore 304.134-1 ii nvidia-installer-cleanup 20151021+4 ii nvidia-legacy-304xx-alternative304.134-1 ii nvidia-support 20151021+4 ii xserver-xorg-core [xorg-video-abi-23] 2:1.19.1-4 ii xserver-xorg-legacy2:1.19.1-4 Versions of packages xserver-xorg-video-nvidia-legacy-304xx recommends: ii nvidia-legacy-304xx-driver304.134-1 ii nvidia-legacy-304xx-vdpau-driver 304.134-1 ii nvidia-settings-legacy-304xx 304.134-1 xserver-xorg-video-nvidia-legacy-304xx suggests no packages. Versions of packages nvidia-legacy-304xx-alternative depends on: ii glx-alternative-nvidia 0.7.4 Versions of packages glx-alternative-nvidia depends on: ii glx-alternative-mesa 0.7.4 ii glx-diversions0.7.4 ii update-glx0.7.4 Versions of packages glx-alternative-nvidia suggests: pn nvidia-driver Versions of packages xserver-xorg-video-intel depends on: ii libc6 2.24-9 ii libdrm-intel1 2.4.74-1 ii libdrm22.4.74-1 ii libpciaccess0 0.13.4-1 ii libpixman-1-0 0.34.0-1 ii libudev1 232-12 ii libx11-6 2:1.6.4-2 ii libx11-xcb12:1.6.4-2 ii libxcb-dri2-0 1.12-1 ii libxcb-dri3-0 1.12-1 ii libxcb-sync1 1.12-1 ii libxcb-util0 0.3.8-3 ii libxcb11.12-1 ii libxcursor11:1.1.14-1+b1 ii libxdamage11:1.1.4-2+b1 ii libxext6 2:1.3.3-1 ii libxfixes3 1:5.0.3-1 ii libxinerama1 2:1.1.3-1+b1 ii libxrandr2 2:1.5.1-1 ii libxrender11:0.9.10-1 ii libxshmfence1 1.2-1 ii libxss11:1.
Bug#651246: vice: "Illegal Instruction" on Pentium III
Package: vice Version: 2.3.dfsg-2 Followup-For: Bug #651246 Dear Maintainer, This bug also happens on my machine, which has an AMD Athlon XP 2600+ CPU. -- System Information: Debian Release: wheezy/sid APT prefers unstable APT policy: (990, 'unstable'), (500, 'stable'), (200, 'experimental') Architecture: i386 (i686) Kernel: Linux 3.0.0-1-486 Locale: LANG=en_US, LC_CTYPE=en_US (charmap=ISO-8859-1) Shell: /bin/sh linked to /bin/bash Versions of packages vice depends on: ii dpkg1.16.1.2 ii install-info4.13a.dfsg.1-8 ii libasound2 1.0.24.1-4 ii libatk1.0-0 2.2.0-2 ii libc6 2.13-21 ii libcairo2 1.10.2-6.1 ii libfontconfig1 2.8.0-3 ii libfreetype62.4.8-1 ii libgcc1 1:4.6.2-6 ii libgdk-pixbuf2.0-0 2.24.0-1 ii libglib2.0-02.30.2-4 ii libgtk2.0-0 2.24.8-2 ii libieee1284-3 0.2.11-10 ii libjpeg88c-2 ii libpango1.0-0 1.29.4-2 ii libpcap0.8 1.1.1-10 ii libpng12-0 1.2.46-3 ii libreadline66.2-8 ii libstdc++6 4.6.2-6 ii libx11-62:1.4.4-4 ii libxrandr2 2:1.3.2-2 ii libxxf86vm1 1:1.1.1-2 ii zlib1g 1:1.2.3.4.dfsg-3 vice recommends no packages. vice suggests no packages. -- no debconf information -- To UNSUBSCRIBE, email to debian-bugs-rc-requ...@lists.debian.org with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org
Bug#646903: FTBFS: Cannot detect libclamav
tags 646903 + patch thanks Package: dansguardian Version: 2.10.1.1-3 Followup-For: Bug #646903 User: ubuntu-de...@lists.ubuntu.com Usertags: origin-ubuntu precise ubuntu-patch Here's the relevant hunk from the Ubuntu Oneiric/11.10 source package resolving the configure.ac breakage. Unfortunately, dpatch-edit-patch runs the clean target, which causes the build to bail since this patch hasn't yet been applied... Thanks for considering the patch. -- System Information: Debian Release: wheezy/sid APT prefers oneiric-updates APT policy: (500, 'oneiric-updates'), (500, 'oneiric-security'), (500, 'oneiric-proposed'), (500, 'oneiric') Architecture: amd64 (x86_64) Kernel: Linux 3.0.0-12-generic (SMP w/8 CPU cores) Locale: LANG=en_US.UTF-8, LC_CTYPE=en_US.UTF-8 (charmap=UTF-8) Shell: /bin/sh linked to /bin/dash dansguardian_2.10.1.1-3ubuntu1.dsc.debdiff_full Description: Binary data
Bug#644113: Fixes for BTS #644113
tags 644113 + patch thanks Package: gtklp Version: 1.2.7-2.1 Followup-For: Bug #644113 User: ubuntu-de...@lists.ubuntu.com Usertags: origin-ubuntu precise ubuntu-patch In Debian sid, the attached patch can be applied to achieve the following: * bts644113.diff: Fix format string literals and some unused variables. Resolves FTBFS. (Closes: #644113) Thanks for considering the patch. -- System Information: Debian Release: wheezy/sid APT prefers oneiric-updates APT policy: (500, 'oneiric-updates'), (500, 'oneiric-security'), (500, 'oneiric-proposed'), (500, 'oneiric') Architecture: amd64 (x86_64) Kernel: Linux 3.0.0-12-generic (SMP w/8 CPU cores) Locale: LANG=en_US.UTF-8, LC_CTYPE=en_US.UTF-8 (charmap=UTF-8) Shell: /bin/sh linked to /bin/dash gtklp_1.2.7-2.1ubuntu2.debdiff Description: Binary data
Bug#625411:
tags 625411 + unreproducible thanks I vote for closing this bug. ┌──┐ │ Summary │ └──┘ Architecture: amd64 Build-Space: 69936 Build-Time: 230 Distribution: sid Install-Time: 15 Job: tla_1.3.5+dfsg-16.dsc Package: tla Package-Time: 251 Source-Version: 1.3.5+dfsg-16 Space: 69936 Status: successful Version: 1.3.5+dfsg-16 Finished at 2001-1834 Build needed 00:04:11, 69936k disc space
Bug#615772: scenic: ftbfs with gold or ld --no-add-needed
tags 615772 + patch thanks Attached are the combined changes from Ubuntu resolving FTBFS on i386 and amd64. scenic_0.6.3-1ubuntu3.debdiff Description: Binary data
Bug#565070: rampart: ftbfs with gcc-4.5
tags 565070 + patch
thanks
Attached is the Ubuntu patch resolving FTBFS with gcc-4.5.
diff -Naurp rampartc-src-1.3.0.orig//src/omxmlsec/key_mgr.c rampartc-src-1.3.0//src/omxmlsec/key_mgr.c
--- rampartc-src-1.3.0.orig//src/omxmlsec/key_mgr.c 2009-05-13 01:13:54.0 -0400
+++ rampartc-src-1.3.0//src/omxmlsec/key_mgr.c 2011-02-12 16:38:13.120379524 -0500
@@ -351,7 +351,7 @@ oxs_key_mgr_get_prv_key(
if(prv_key_file)
{
- if(oxs_util_get_format_by_file_extension(env, prv_key_file) ==OXS_ASYM_CTX_FORMAT_PEM)
+ if((int) oxs_util_get_format_by_file_extension(env, prv_key_file) == OXS_ASYM_CTX_FORMAT_PEM)
{
prvkey = oxs_key_mgr_load_private_key_from_pem_file(env, prv_key_file, password);
if(!prvkey)
Bug#615766: predict: ftbfs with gold or ld --no-add-needed
tags 615766 + patch thanks Package: predict Version: 2.2.3-3 Followup-For: Bug #615766 User: ubuntu-de...@lists.ubuntu.com Usertags: origin-ubuntu precise ubuntu-patch Here is the patch from Ubuntu Oneiric; thanks for considering it. -- System Information: Debian Release: wheezy/sid APT prefers oneiric-updates APT policy: (500, 'oneiric-updates'), (500, 'oneiric-security'), (500, 'oneiric-proposed'), (500, 'oneiric') Architecture: amd64 (x86_64) Kernel: Linux 3.0.0-12-generic (SMP w/8 CPU cores) Locale: LANG=en_US.UTF-8, LC_CTYPE=en_US.UTF-8 (charmap=UTF-8) Shell: /bin/sh linked to /bin/dash diff -u predict-2.2.3/debian/rules predict-2.2.3/debian/rules --- predict-2.2.3/debian/rules +++ predict-2.2.3/debian/rules @@ -28,10 +28,10 @@ cc $(CFLAGS) \ vocalizer/vocalizer.c -o vocalizer/vocalizer - (cd utils/fodtrack-0.1 ; cc $(CFLAGS) -lm fodtrack.c -o fodtrack ) - (cd utils/geosat ; cc $(CFLAGS) -lm geosat.c -o geosat ) - (cd utils/moontracker ; cc $(CFLAGS) -lm moontracker.c -o moontracker ) - (cd clients/earthtrack ; cc $(CFLAGS) -lm earthtrack.c -o earthtrack ) + (cd utils/fodtrack-0.1 ; cc $(CFLAGS) fodtrack.c -o fodtrack -lm ) + (cd utils/geosat ; cc $(CFLAGS) geosat.c -o geosat -lm ) + (cd utils/moontracker ; cc $(CFLAGS) moontracker.c -o moontracker -lm ) + (cd clients/earthtrack ; cc $(CFLAGS) earthtrack.c -o earthtrack -lm ) (cd clients/map; cc $(CFLAGS) -o predict-map map.c map_cb.c map_main.c -I/usr/include/X11 -lforms -lX11 -lm)
Bug#674386: supercollider: FTBFS: scons: *** No SConstruct file found.
Hi - Thanks for reporting this. The problem seems to be something to do with dh's automatic invocation of scons to perform cleaning - if you look at the log you'll see that the package successfully builds (calling scons on the directory "./common"), but the clean step invokes scons on the "." directory which is incorrect. I'd like to mark this as "won't fix" because we're dropping the scons build system. The latest version of supercollider 3.5.x (which I'm currently asking debian-multimedia maintainers to upload) uses cmake instead which is much less mess. Best Dan 2012/5/24 Lucas Nussbaum : > Source: supercollider > Version: 1:3.4.5-1 > Severity: serious > Tags: wheezy sid > User: debian...@lists.debian.org > Usertags: qa-ftbfs-20120524 qa-ftbfs > Justification: FTBFS on amd64 > > Hi, > > During a rebuild of all packages in sid, your package failed to build on > amd64. > > Relevant part: >> debian/rules build >> test -x debian/rules >> mkdir -p "common" >> >> WARNING: copyright-check disabled - licensecheck (from devscripts package) >> is missing. >> >> touch debian/stamp-copyright-check >> touch debian/stamp-upstream-cruft >> scons --directory="." CC="cc" CFLAGS="-g -O2 -fstack-protector >> --param=ssp-buffer-size=4 -Wformat -Werror=format-security -Wall" CXX="g++" >> CXXFLAGS="" DEVELOPMENT=yes PREFIX=/usr CROSSCOMPILE=1 CURL=0 SCVIM=0 >> SCED=0 STRIP=0 >> >> scons: *** No SConstruct file found. >> File "/usr/lib/scons/SCons/Script/Main.py", line 904, in _main >> make: *** [debian/stamp-scons-build] Error 2 > > The full build log is available from: > > http://people.debian.org/~lucas/logs/2012/05/24/supercollider_3.4.5-1_unstable.log > > A list of current common problems and possible solutions is available at > http://wiki.debian.org/qa.debian.org/FTBFS . You're welcome to contribute! > > About the archive rebuild: The rebuild was done on about 50 AMD64 nodes > of the Grid'5000 platform, using a clean chroot. Internet was not > accessible from the build systems. > > > > ___ > pkg-multimedia-maintainers mailing list > pkg-multimedia-maintain...@lists.alioth.debian.org > http://lists.alioth.debian.org/cgi-bin/mailman/listinfo/pkg-multimedia-maintainers -- To UNSUBSCRIBE, email to debian-bugs-rc-requ...@lists.debian.org with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org
