Bug#996627: kodi-data: Kodi cannot be installed on a foreign architecture

Vasyl Gello writes: > What's better about solution to widevinecdm is that it'll solve eternal pain > of CoreELEC and LibreELEC requiring them to stick with armv7l userspace and > Kodi only to get Widevine support. > > However I have an idea to test. Are you able to test builds? Yes.

Bug#996627: kodi-data: Kodi cannot be installed on a foreign architecture

Vasyl Gello writes: > Well, as far as I have researched, there might be even the possibility > to co-install two different Kodi sets for different architectures, but > that will require fixing the whole Python packaging down to > python3.x-minimal. > > So what did you, do specifically? Did you

Bug#996627: kodi-data: Kodi cannot be installed on a foreign architecture

Package: kodi-data Version: 2:19.1+dfsg2-2 Severity: normal Dear Maintainer, Kodi cannot be installed on a foreign architecture. I asked in #multiarch for help, and this was our discussion: 13:36 I'm trying to install kodi:armhf on arm64 13:37 but, kodi-data (which is ma: foreign) depends on

Bug#992238: debian-installer: Installation fails on HP ProLiant m400 Server: additional cores crash, kernel hangs in acpi_init

Justus Winter writes: > Steve McIntyre writes: > >> OK, this is not looking good. I'll ask some of the Arm folks to have a >> look here in case they can help. > > Thanks! Any news from Arm? Justus signature.asc Description: PGP signature

Bug#992238: debian-installer: Installation fails on HP ProLiant m400 Server: additional cores crash, kernel hangs in acpi_init

Steve McIntyre writes: > On Mon, Aug 16, 2021 at 01:24:14PM +0200, Justus Winter wrote: >>Steve McIntyre writes: >>> >>> OK, and my upgrade worked just fine. The key difference that I'm >>> seeing is that on my system ACPI is *not* used: >>> >

Bug#992238: debian-installer: Installation fails on HP ProLiant m400 Server: additional cores crash, kernel hangs in acpi_init

Steve McIntyre writes: > On Mon, Aug 16, 2021 at 12:54:47PM +0200, Justus Winter wrote: >>Steve McIntyre writes: >>> On Mon, Aug 16, 2021 at 10:09:49AM +0200, Justus Winter wrote: >>>>Package: debian-installer >>>>Version: 20210731 >>>>Seve

Bug#992238: debian-installer: Installation fails on HP ProLiant m400 Server: additional cores crash, kernel hangs in acpi_init

Hi Steve :) Steve McIntyre writes: > Reassigning to the right package. While you're seeing this during d-i, > the problem is clearly coming from the Linux kernel. Thanks! > On Mon, Aug 16, 2021 at 10:09:49AM +0200, Justus Winter wrote: >>Package: debian-installer >

Bug#992238: debian-installer: Installation fails on HP ProLiant m400 Server: additional cores crash, kernel hangs in acpi_init

Package: debian-installer Version: 20210731 Severity: critical Tags: d-i Justification: breaks the whole system Dear Maintainer, I'm trying to install Debian Bullseye on a ProLiant m400 Server Cartridge. The cartridge is in EFI mode, we boot the EFI shim, GRUB, the kernel, and the netboot

Bug#969588: sqv: Cannot use ASCII armored key as keyring?

Daniel Kahn Gillmor writes: > On Fri 2020-10-16 12:05:48 +0200, Justus Winter wrote: >> And in general, the expectation that you can join two files does not >> hold. Concatenating two photos doesn't yield a slideshow, etc. So my >> position on the matter is that con

Bug#969588: sqv: Cannot use ASCII armored key as keyring?

Hi :) Guillem Jover writes: > I was also embarrassed for a moment, :) then realized this should have > failed with GnuPG, and rechecking the signing-key.asc recalled it > contains the two certificates concatenated one after the other, which > GnuPG seems to be able to import correctly. Now I'm

Bug#954094: /bin/systemd: Running startx in X session switches to VC, input duplicated to X, login at getty exfiltrates creds

Package: systemd Version: 241-7~deb10u3 Severity: critical File: /bin/systemd Tags: security Justification: root security hole Dear Maintainer, I was trying to spawn an Xephyr server using startx, but messed up the arguments (I can reproduce it by simply running 'startx'). My X session

Bug#952853: thunderbird: Account wizard fails to configure server settings using Mozilla's own autoconfig protocol, uses heuristic, fails

Package: thunderbird Version: 1:68.4.1-1~deb10u1 Severity: normal Dear Maintainer, I'm trying to improve the account creation for a mail server setup of mine. To this end, I setup and configured automx2 on the server, and now I'm trying to get Thunderbird to use it. automx2 implements

Bug#842015: [PINENTRY PATCH] gnome3: Test if Gcr System Prompter is available at startup.

Daniel Kahn Gillmor writes: > * gnome3/pinentry-gnome3.c (gcr_system_prompt_available): new function > tests whether it is possible to create a GcrSystemPrompt; (main): > use gcr_system_prompt_available() to decide whether to fall back to > curses or not. Please

Bug#839991: [pkg-gnupg-maint] Bug#839991: gnupg-agent: 'allow-emacs-pinentry' setting in agent conf makes gpg2 respond no secret key

Daiki Ueno writes: > Werner Koch writes: > >> Alrthough we could handle this in gpg-agent, I consider it better to fix >> this in Pinentry. The name "allow-emacs-prompt" means to me that Emacs >> support is optional and thus Pinentry should just return OK. A new

Bug#749890: [Jakub Wilk] Bug#749890: python3-notmuch: missing header in mbox message -> NullPointerError

Hi, Quoting David Bremner (2014-05-30 15:14:46) > this looks like a bug in the python bindings to me > > Package: python3-notmuch > Version: 0.18-3 > Severity: minor > > If a message starts with the "From " postmark (i.e., it's in the mbox > format), and you ask the get_header() method for a

Bug#817964: notmuch: indexing daemon

Quoting David Bremner (2016-03-12 12:24:47) > Paul Wise writes: > > I expect the right interface to use for notifications of filesystem > > events is inotify since fanotify doesn't send rename events. This would > > require one inotify per directory. Fwiw, afew does exactly

Bug#812763: libadns1: Please provide Tor support

Package: libadns1 Version: 1.5.0~rc1-1 Severity: wishlist Tags: patch Dear Maintainer, please provide Tor support in libadns. For your convenience I created a branch with the relevant patches without any whitespace changes. Please see the six topmost patches here:

Bug#802053: Fix probing of Hurd installations on the Hurd

Package: os-prober Version: 1.68 Severity: normal Tags: patch User: debian-h...@lists.debian.org Usertags: hurd X-Debbugs-CC: debian-h...@lists.debian.org Hello, with os-prober working on the Hurd now, I noticed that the grub installation would hang. I traced the problem to a Hurd-specific

Bug#760275: e2fsprogs: e2fsck corrupts Hurd filesystems

Quoting Theodore Ts'o (2015-01-23 16:25:11) On Thu, Jan 22, 2015 at 07:41:10PM +0100, Justus Winter wrote: I can accept that you do not care about the Hurd, but I feel deeply saddened by the fact that you appreciate my effort to improve the software you maintain so little. Sorry, this e

Bug#760275: e2fsprogs: e2fsck corrupts Hurd filesystems

Hello, Quoting Justus Winter (2014-09-02 19:22:57) Quoting Theodore Ts'o (2014-09-02 18:56:58) Probably not. We can switch to the Linux on-disk format once we can store all Hurdish stuff in extended attributes though. Hm. When you do this, it would be good to simply stop using

Bug#760275: e2fsprogs: e2fsck corrupts Hurd filesystems

Quoting Theodore Ts'o (2014-09-02 15:50:14) On Tue, Sep 02, 2014 at 01:59:34PM +0200, 4win...@informatik.uni-hamburg.de wrote: Package: e2fsprogs Version: 1.42.12-1 Severity: normal Tags: patch Dear Maintainer, e2fsck accesses the field osd2.linux2.l_i_file_acl_high field

Bug#760275: e2fsprogs: e2fsck corrupts Hurd filesystems

Quoting Theodore Ts'o (2014-09-02 18:56:58) Probably not. We can switch to the Linux on-disk format once we can store all Hurdish stuff in extended attributes though. Hm. When you do this, it would be good to simply stop using EXT4_OS_HURD in the superblock, Sure, that's the idea.

Bug#756912: linux-image-3.14-2-amd64: kernel oops in the radeon driver using a RV730 XT [Radeon HD 4670] [1002:9490]

Package: src:linux Version: 3.14.13-2 Severity: important Dear Maintainer, I am getting kernel oopses with the 3.14 series. Using 3.2 was ok, modulo some major visual glitches in certain applications (e.g. gdm3) that were accompanied by messages in the kernel log saying something about the

Bug#595135: pulseaudio: Cached volume data causes abort previously-working USB DAC

Hi :) Quoting Felipe Sateler (2014-04-09 00:18:23) Hi Devin, Justus, Devin wrote: pulseaudio would die on startup or on device connection with this assert failure: E: volume.c: Assertion 'a' failed at pulse/volume.c:39, function pa_cvolume_equal(). Aborting. Aborted Removing

Bug#742779: coccinelle introduces spurious whitespace changes

Package: coccinelle Version: 1.0.0~rc20.deb-1 Severity: normal Dear Maintainer, coccinelle recently (since I upgraded to jessie I guess) began to introduce spurious whitespace changes for a certain semantic patch. I made a minimal test case: % tail test.* == test.c == int main () { int a =

Bug#742615: make runsystem.sysv honor init=something

on Debian/Linux. Thanks, Justus From 9ecdb676b9b3ae316ab43303084f6bfe84b04027 Mon Sep 17 00:00:00 2001 From: Justus Winter 4win...@informatik.uni-hamburg.de Date: Tue, 25 Mar 2014 14:51:21 +0100 Subject: [PATCH] Make runsystem.sysv honor init=something in the kernel command line This makes

Bug#721917: [Pkg-sysvinit-devel] Bug#721917: Patches fixing sysvinit issues on Debian/Hurd

Quoting Petter Reinholdtsen (2014-01-13 10:36:02) [Justus Winter 2013-09-18] Please find attached a patch introducing a proper break line for all the Hurd versions that do not have the features needed for this patch series. This seem to complete the change request, increasing the chance

Bug#721917: [Pkg-sysvinit-devel] Bug#721917: Patches fixing sysvinit issues on Debian/Hurd

Here is an updated patch series, including the final patch that includes a runsystem.sysv that can be used instead of the current runsystem.gnu to use sysvinit to boot Debian/Hurd systems. Thanks, Justus From 3957b17c8ffb9da8679e600b4b3142377051c172 Mon Sep 17 00:00:00 2001 From: Justus Winter

Bug#721917: [Pkg-sysvinit-devel] Bug#721917: Patches fixing sysvinit issues on Debian/Hurd

Quoting Justus Winter (2013-09-08 13:49:55) Quoting Petter Reinholdtsen (2013-09-08 08:20:52) [Justus Winter] Dear maintainer :) Hi. :) This is a patch series fixing sysvinit issues on Debian/Hurd *without* actually switching to sysvinit as init system on Debian/Hurd

Bug#721917: [Pkg-sysvinit-devel] Bug#721917: Patches fixing sysvinit issues on Debian/Hurd

Quoting Petter Reinholdtsen (2013-09-08 08:20:52) [Justus Winter] Dear maintainer :) Hi. :) This is a patch series fixing sysvinit issues on Debian/Hurd *without* actually switching to sysvinit as init system on Debian/Hurd as this requires a rebuilt hurd package with recently

Bug#721917: Patches fixing sysvinit issues on Debian/Hurd

implemented functionality. Thanks, Justus From 66a3c62db00e01ff894c7d63bf9182e1a4f2700c Mon Sep 17 00:00:00 2001 From: Justus Winter 4win...@informatik.uni-hamburg.de Date: Mon, 8 Jul 2013 11:41:33 +0200 Subject: [PATCH 1/6] initscripts: hurd has a proper tmpfs now, remove workaround --- debian

Bug#720531: ifupdown: Fixes for Debian/Hurd

Hi Andrew :) The second patch sanitizes the file names of pid files written by ifupdown and provides the macro %iface_file_name% that provides the interface name sanitized in a way so that it is safe to use as a file name fragment. This is motivated by the fact that on the Hurd network

Bug#720531: ifupdown: Fixes for Debian/Hurd

Package: ifupdown Version: 0.7.8 Severity: wishlist Tags: patch Dear Maintainer, I've attached a patch series that fixes ifupdown to work properly on Debian/Hurd. The first patch makes ifupdown use inetutils-ifconfig instead of ifconfig and fixes its use in two cases. The second patch

Bug#688112: gummi leaks file descriptors leading to a crash if the fd limit is reached

descriptor leak. Author: Justus Winter teyth...@thinkbox.jade-hamburg.de --- gummi-0.6.3.orig/src/utils.c +++ gummi-0.6.3/src/utils.c @@ -250,6 +250,8 @@ Tuple2 utils_popen_r (const gchar* cmd, g_free (rot); } +close(pout); + #ifndef WIN32 // TODO: command

Bug#658421: golang-weekly: go build and go install fail

found 658421 2012.03.04-1 thanks Quoting Ondřej Surý (2012-03-03 20:38:42) Ah, thanks for the hint. The timestamps are different because I copy the source manually from debian/rules. That problem has easy solution, I am adding --preserve-timestamp option to install invocation. Hm, the issue is

Bug#658421: golang-weekly: go build and go install fail

Quoting Ondřej Surý (2012-03-03 20:38:42) Ah, thanks for the hint. The timestamps are different because I copy the source manually from debian/rules. That problem has easy solution, I am adding --preserve-timestamp option to install invocation. Could you retry it, when 2012.02.22-4 hits the

Bug#658421: golang-weekly: go build and go install fail

Hi Ondřej, I've been seeing the same error with 2012.02.22-3 and I think it is because the library archive is older than the go source files, hence the archive is considered old and go install tries to rebuild it. The following workaround solves this, dunno why the timestamps are wrong in the

Bug#564249: ario: Libgcrypt warning: missing initialization

forwarded 564249 https://sourceforge.net/tracker/?func=detailaid=3274178group_id=197448atid=961512 tag 564249 +patch thanks Looking at arios source I can confirm the problem, though I don't see the log message mentioned by the bug reporter. I attached a patch for the version of ario currently

Bug#610209: mlocate: FTBFS on hurd-i386: unconditional use of PATH_MAX

Package: mlocate Version: 0.23.1-1 Severity: important Tags: patch User: debian-h...@lists.debian.org Usertags: hurd The attached patch fixes three unconditional occurrences of PATH_MAX. Thanks, Justus -- System Information: Debian Release: 6.0 APT prefers unstable APT policy: (900,

Bug#595135: pulseaudio: Cached volume data causes abort previously-working USB DAC

Hey Dan :) I've got the same system with an usb sound card and can reproduce this problem with both the version in squeeze and the one in experimental. I am using the system as a target for a tunnel-sink and removing the volume state files prevents pulseaudio from triggering the assertion, but

Bug#556522: hurd - using the login shell is insecure

Hey Samuel :) Justus Winter, le Wed 12 Jan 2011 00:39:35 +0100, a écrit : diff -r a95557dc73eb daemons/getty.c --- a/daemons/getty.c Tue Jan 11 00:00:32 2011 + +++ b/daemons/getty.c Tue Jan 11 23:38:12 2011 + @@ -129,10 +129,10 @@ if (tt strcmp (tt-ty_type

Bug#609688: syslinux: isohybrid fails to set the MBR ID

Package: syslinux Version: 2:4.03+dfsg-7 Severity: normal isohybrid fails to set the MBR ID when invoked with -id, whereas isohybrid.pl works as expected. Attached is a small program to read the id from a given file. $ python getid.py some.iso 0x9785721e $ isohybrid -id 0x12345678 some.iso $

Bug#556522: hurd - using the login shell is insecure

Hey Samuel :) Justus Winter, le Mon 10 Jan 2011 00:36:07 +0100, a écrit : I incorporated some code from util-linuxs getty to make hurds getty ask for a login name and pass that name to login. This way the login shell is no longer needed. I also turned on logins --paranoid flag to prevent

Bug#609444: tmux hangs when closing the session on hurd

Package: tmux Version: 1.4-2 Severity: normal When the session is ended by closing the last shell within tmux, tmux hangs. It also hangs when a new session is started (this time with an existing socket): teyth...@ganymede:~$ id uid=1000(teythoon) gid=1000(teythoon) groups=1000(teythoon),4(adm)

Bug#556522: hurd - using the login shell is insecure

tags 556522 patch thanks Hi :) I incorporated some code from util-linuxs getty to make hurds getty ask for a login name and pass that name to login. This way the login shell is no longer needed. I also turned on logins --paranoid flag to prevent it leaking whether a user exists or not. Cheers,

Bug#609333: tmux-1.4 FTBFS on the hurd

Package: tmux Version: 1.4-1 Severity: serious Tags: patch Justification: fails to build from source tmux-1.4 fails to build from source on the hurd since the PATH_MAX macro isn't defined. There is already a debian specific patch to make tmux build on hurd by simply defining it in case it is

Bug#609333: tmux-1.4 FTBFS on the hurd

Hey Julien :) severity 609333 normal kthxbye On Sat, Jan 8, 2011 at 17:09:55 +, Justus Winter wrote: Package: tmux Version: 1.4-1 Severity: serious No. Hm, I am sorry about that. FWIW I used the report bug utility and it asked me: How would you rate the severity

Bug#595876: multiboot: FTBFS in squeeze: rm: cannot remove `debian/multiboot/usr/share/info/dir': No such file or directory

Hey Gregor :) or to rm -rf the dir, IMO) As I said, I'd vote to add install-info as a build dependency since documentation is the purpose of this package. Ok ... but: I guess I'm to tired for today: Anyway I tried now: + removed install-info from the chroot - first build without

Bug#595876: multiboot: FTBFS in squeeze: rm: cannot remove `debian/multiboot/usr/share/info/dir': No such file or directory

Hey Gregor :) On Fri, 17 Sep 2010 04:29:55 +0200, Justus Winter wrote: install-info needs to be added to the list of build dependencies or rm debian/$(package)/usr/share/info/dir removed from debian/rules. But since this is a package containing documentation, I'd say we should go

Bug#595448: glob2: Crash during tutorial part 4 (src/Game.cpp Assertion `building' failed)

tags 595448 patch thanks To set the building type to 17 (racetrack level 1 under construction, size 6x6) you can either do echo -en '\x00\x00\x00\x11' | \ dd of=tutorial-part4.map bs=1 seek=49210 conv=notrunc or apply the attached patch using bspatch. Cheers, Justus

Bug#597164: mock: fails with ImportError: No module named root_cache

I cannot reproduce this bug, I just built rpms for both epel-5-x86_64 and epel-5-i386 on two different machines running squeeze (one being a x86_64 machine, the other one is an i386). # dpkg -l mock [...] ii mock 1.0.8-1Build rpm packages inside a chroot # mock -r epel-5-i386

Bug#595448: (no subject)

forwarded 595448 http://savannah.nongnu.org/bugs/?27969 tags 595448 upstream confirmed thanks The assertion is only triggered when the opponents race track is destroyed, one can also trigger it from within the editor by loading the map and deleting the race track. The problem lies within the

Bug#595448: glob2: Crash during tutorial part 4 (src/Game.cpp Assertion `building' failed)

forwarded http://savannah.nongnu.org/bugs/?27969 tags upstream confirmed thanks Uh, I didn't know that I have to cc the control@ address... and I wanted to add, that you can actually *see* the bug when your warriors are attacking the race track but they are not actually hitting the building when

Bug#595876: multiboot: FTBFS in squeeze: rm: cannot remove `debian/multiboot/usr/share/info/dir': No such file or directory

tags 595876 confirmed patch thanks install-info needs to be added to the list of build dependencies or rm debian/$(package)/usr/share/info/dir removed from debian/rules. But since this is a package containing documentation, I'd say we should go with the first option. Cheers, Justusdiff

Bug#595448: (no subject)

forwarded http://savannah.nongnu.org/bugs/?27969 tags upstream confirmed thanks Hi :) I can confirm that the bug is present in both the debian package and upstream when building the mercurial head. I also found the bug at the projects bugtracker (note that savannahs bugtracker interprets * as

Bug#581584: /etc/grub.d/10_hurd: generate entries for each gnumach kernel found in /boot

Package: grub-pc Version: 1.98-1 Severity: wishlist Tags: patch /etc/grub.d/10_linux generates menu entries for each kernel found in /boot and I believe that 10_hurd should do the same for each gnumach kernel. reportbug was so kind as to include an example configuration created using my patch.

Bug#579834: gdb fails on the hurd with Can't fetch registers from thread bogus thread id 1: No such thread

Package: gdb Version: 7.1-1 Severity: grave Justification: renders package unusable Debugging even the most simple c program fails on my hurd installation (fwiw I downloaded debian-hurd-17042010-qemu.img.tar.gz prepared by Jose and installed some development stuff; the system is running under

Bug#532098: bluez-alsa is silent, but mplayer complains loudly

I ran into the same issue. # dpkg -l | egrep 'bluetooth|bluez' ii bluetooth 4.60-1 Bluetooth support ii bluez 4.60-1 Bluetooth tools and

Bug#547159: readahead fails to check the return value of blkid_devno_to_devname

I encountered this bug since I build a custom kernel that didn't used an initrd. To produce an core dump, use the attached wrapper script and change /etc/init.d/early-readahead to use it instead of /sbin/readahead (idea taken from https://bugzilla.redhat.com/show_bug.cgi?id=500946). In my case

Bug#540072: testcase

I also ran into that one and I managed to produce a test case. The problem is that askyesno calls askquestion and compares the result with 'yes' which is always false if type(result) is _tkinter.Tcl_Obj. Using a tkFileDialog is (for me) a reliable way to trigger this condition. Justus # from