Bug#780634: Please allow graceful fallback on error (split from #776911)

2015-03-17 Thread Kill Your TV
Package: gnome-shell Severity: wishlist It would be nice if gnome-shell could handle failures from drivers (e.g. mesa) more gracefully. For example, I have a hexcore AMD processor and if I try to emulate a SandyBridge CPU in qemu (but my CPU doesn't actually support the same features) and then

Bug#776911: gnome-shell: fails to start on i386 when [Mesa was] built with llvm-3.5

2015-03-10 Thread Kill Your TV
On Tue, 10 Mar 2015 08:16:03 + (UTC) Simon McVittie wrote: > On 09/03/15 22:30, Kill Your TV wrote: > > On Mon, 9 Mar 2015 21:04:55 + (UTC) > > Simon McVittie wrote: > >> If your host CPU is missing any of those features, then emulating a > >> SandyBri

Bug#776911: gnome-shell: fails to start on i386 when [Mesa was] built with llvm-3.5

2015-03-10 Thread Kill Your TV
On Mon, 9 Mar 2015 21:04:55 + (UTC) Simon McVittie wrote: > If your host CPU is missing any of those features, then emulating a > SandyBridge CPU in your VM is probably an invalid configuration. This is absolutely true of course (I personally use -cpu host), but IMHO there should be more g

Bug#779991: libguestfs-tools: firstboot-command scripts do not run

2015-03-07 Thread Kill Your TV
Package: libguestfs-tools Version: 1:1.29.26-1 Severity: normal Control: found -1 libguestfs-tools/1:1.28.6-1 The initscripts added by --firstboot-command are not run without `at` installed and/or running. I see this with the version currently in Sid as well as the one in experimental. I can rep

Bug#777548: The Sid package also works

2015-03-05 Thread Kill Your TV
Control: fixed -1 libguestfs/1:1.28.6-1 I can confirm that the version from Sid also works. If it's not too late it would be great to get this version in Jessie. pgp6a4QngNJSc.pgp Description: OpenPGP digital signature

Bug#777548: Fixed in experimental

2015-03-05 Thread Kill Your TV
found -1 1:1.29.6-1 fixed -1 1.29.26-1 I hit this bug with package version 1:1.29.6-1, dated Fri, 07 Nov 2014 21:09:14 +0100. I do not see it in the latest version from experimental dated Sat, 28 Feb 2015 12:50:14 +0100. I do not know which package update actually fixed it. pgpbu5wgvZ9Ot

Bug#766533: tlsdate cannot be started with systemd

2014-10-23 Thread Kill Your TV
On Thu, 23 Oct 2014 21:00:01 + (UTC) Jacob Appelbaum wrote: > I'm aware of this issue with the AUR package of tlsdate - thanks for > confirming it also impacts Debian! > > I'm planning a new upstream release for another minor fix - it will be > fixed in 0.0.12. > > Could you confirm that it

Bug#766579: tlsdate's apparmor rules are a bit too restrictive

2014-10-23 Thread Kill Your TV
Package: tlsdate Version: 0.0.11-2 Severity: normal I've noticed the following logged while tlsdate is running: audit: type=1400 audit([CENSORED]): apparmor="DENIED" operation="open" profile="/usr/sbin/tlsdated" name="/var/cache/tlsdated/timestamp" pid=30105 comm="tlsdated" requested_mask="r"

Bug#766533: tlsdate cannot be started with systemd

2014-10-23 Thread Kill Your TV
Package: tlsdate Version: 0.0.11-2 Severity: normal On a Debian unstable system with systemd, updating tlsdate from 0.0.8-1 to 0.0.11-2 fails when systemd goes to start the daemon. I resolved this locally by changing Type=forking to Type=simple but I'm not sure that this is the proper "fix". Th

Bug#759565: service-wrapper: new upstream release available

2014-08-28 Thread Kill Your TV
anges can be found at https://github.com/kytvi2p/service-wrapper-java.git in the master-3.5.25 branch. From 64c11ee6995a9e916ce47f8d40a6fd2dcf341d59 Mon Sep 17 00:00:00 2001 From: Kill Your TV Date: Thu, 28 Aug 2014 14:31:04 + Subject: [PATCH] Update packaging for 3.5.25 --- debian/chan

Bug#742439: fcgiwrap: Does not start with systemd

2014-03-23 Thread Kill Your TV
Package: fcgiwrap Version: 1.1.0-2 Severity: normal After moving to systemd fcgiwrap no longer started at boot. The following was logged: Mar 23 13:37:16 hostname systemd[1]: Starting Simple CGI Server... Mar 23 13:37:16 hostname systemd[1]: Started Simple CGI Server. Mar 23 13:37:16 hostname fc

Bug#742440: fcgiwrap: incorrect svn url in control file

2014-03-23 Thread Kill Your TV
Package: fcgiwrap Version: 1.1.0-2 Severity: minor Tags: patch Trivial patch inlined. Index: control === --- control (revision 25126) +++ control (working copy) @@ -9,7 +9,7 @@ libsystemd-daemon-dev [linu

Bug#730010: (no subject)

2013-11-22 Thread Kill Your TV
for mips but copying or symlinking the makefile in debian/rules would perhaps be better (if this method is deemed to be acceptable). From: Kill Your TV Date: Sat, 23 Nov 2013 00:17:46 + Subject: mips support --- src/c/Makefile-linux-mips-32.make | 48 +++ 1

Bug#610374: version 3.5.22 is available

2013-11-07 Thread Kill Your TV
On Wed, 6 Nov 2013 17:59:39 + (UTC) tony mancill wrote: > Hi, > > I have taken a half-hearted stab at updating to the newer versions, > but ran into some issues with changes in the build system. > > Please provide a pointer to your packaging, that would be a great > help. Here you go: ht

Bug#610374: version 3.5.22 is available

2013-11-05 Thread Kill Your TV
Hi, It's been more than 2 years since this bug was opened and the wrapper is already up to version 3.5.22 with 3.5.21 being regarded as the stable release. If it would help I can provide the packaging that I use for 3.5.22 in our project. Cheers, kytv signature.asc Description: PGP signature

Bug#627639: Please suggest Tor instead of depending on it

2011-05-24 Thread Kill Your TV
-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 On Tue, 24 May 2011, Peter Palfrader wrote: > On Sun, 22 May 2011, Kill Your TV wrote: > > > Please consider having tor-geoipdb suggest or recommend tor instead > > of depending on it. I would like to depend on this package bu

Bug#627736: New upstream version

2011-05-23 Thread Kill Your TV
al-options to prevent these patches from sneaking in in the future. - - converts debian/rules to use "dh" - - removes the accidental *debhelper.log and *substvars files. Hope this helps (and thank you for your work!), - -- Kill Your TV GPG Key 0xDF0A0A1A -BEGIN PGP SIGNATURE

Bug#627639: Please suggest Tor instead of depending on it

2011-05-22 Thread Kill Your TV
-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 Package: tor-geoipdb Version: 0.2.1.30-1 Please consider having tor-geoipdb suggest or recommend tor instead of depending on it. I would like to depend on this package but not have tor forcefully pulled in. Thank you, - -- Kill Your TV GPG Key