Bug#1066957: dependency not satisfiable in bookworm-backports

Same problem! At the moment, is not possible to update to the stable-backports version of Grub2 for amd64 (2.12-1~bpo12+1), because APT would require removing grub-efi-amd64-signed (1+2.06+13+deb12u1), which would then make the system unbootable with Secure Boot enabled. I suppose a backport

Bug#971630:

retitle: Imagemagick convert can't convert to PDF

Bug#963607: [Pkg-xen-devel] Bug#963607: xen-hypervisor-4.11-amd64: Xen Hypervisor kernel fails to load arcmsr module with "arcmsr0: dma_alloc_coherent got error" message.

On 1/07/2020 22:48, Hans van Kranenburg wrote: > On 7/1/20 5:09 PM, Alex Sanderson wrote: >> On 1/07/2020 02:05, Hans van Kranenburg wrote: >>> To do a bug report upstream, we'll need that information. >> Sorry, completely misunderstood.   Here is the output from the serial >> terminal as Xen

Bug#959733: cant update wireguard

Hi, on my site is the problem solved with ticket 956869. See On: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=956869

Bug#944020: Help with this for TAILS

Hello- I'm doing some work with the Tails team working to get Trezor python-trezor and python-libusb1 back-ported to Buster. These packages can then be put into testing for Tails to use. Currently this all hinges on getting debian bug 944020

Bug#959733: cant update wireguard

Package: wireguard-dkms Version: 1.0.20200429-1~bpo10+1 If i update my wireguard, i get the following error: DKMS make.log for wireguard-1.0.20200429 for kernel 4.19.0-8-amd64 (x86_64) Mo 4. Mai 18:42:30 CEST 2020 make: Verzeichnis „/usr/src/linux-headers-4.19.0-8-amd64“ wird betreten /bin/sh:

Bug#762029: Still happens

So I have the problem as well (6 years later). I just found that sleepd runs and fills up my swap entirely. I'm running buster if it helps. -- I always leave an empty milk carton is the refrigerator just in case someone wants their coffee black.

Bug#928525: Confirming

Confirming I have this problem too. My /etc/sshguard/sshguard.conf has LOGREADER="LANG=C /bin/journalctl -afb -p info -n1 -o cat SYSLOG_FACILITY=4 SYSLOG_FACILITY=10" The example provided by upstream has LOGREADER="LANG=C journalctl -afb -p info -n1 -t sshd -t sendmail -o cat"

Bug#926660: Acknowledgement (webfs: "systemctl stop webfs" not working)

the package version is not indicating this: This problem pops up on Debian buster, it was no issue on stretch.

Bug#926660: webfs: "systemctl stop webfs" not working

Package: webfs Version: 1.21+ds1-12 Severity: important Dear Maintainer, webfs keeps running, even though it should be stopped. After a systemctl stop webfs syslog shows: Apr 8 17:27:38 hostname webfs[13111]: Stopping httpd daemon: webfsdstart-stop-daemon: matching only on non-root pidfile

Bug#873249: FTBFS with Java 9: javadoc classpath with maven?

On Sat, Aug 26, 2017 at 12:25:16PM +0200, Emmanuel Bourg wrote: > With Java 8 a warning was displayed, but with Java 9 it's now > an error. The only workaround I've found besides fixing the classpath is > > Do you know how many packages are affected by this issue? I'd guess ~4 of the ~50 I looked

Bug#698240: build-rdeps also fails with lz4'd sources

Control: severity -1 important build-rdeps also fails with lz4'd sources, which appears to have become the default in sid at some point? It's the case in the "official" debian:sid Docker images, without any config I can see set. As the tool is broken on a default install, without me having

Bug#873030: RM? Superseded by Java 7, abandoned upstream, FTBFS on 9, 1 rdep

Source: jpathwatch Priority: wishlist Can we RM this package? It fails to build on Java 9. It has been abandoned by upstream in 2012, as Java 7 provides the functionality without all the hacks. It has one rdep: eclipse-pydev, which uses it only at build time, for a single test, I believe.

Bug#873021: RM? FTBFS with openjdk-9, outdated, no rdeps

Source: ha-jdbc Priority: wishlist This library package has no rdeps, is a release-candidate version from 2009, there are new major versions upstream. The currently packaged version fails to build with the current openjdk-9-jdk betas. Can we remove it? Cheers, Chris.

Bug#872946: FTBFS with openjdk-9

Source: charactermanaj Priority: normal This package fails to build with Java 9, for which there will hopefully soon be a transition. Please fix it. Build log excerpt: /build/charactermanaj-0.998+git20150728.a826ad85/src/charactermanaj/ui/util/SpinnerWheelSupportListener.java:53: error:

Bug#872945: FTBFS with openjdk-9-jdk

Source: dicomscope Priority: normal This package fails to build against openjdk-9, for which there should soon be a transition. The changes look like they should be easy to fix: error: [options] source value 1.5 is obsolete and will be removed in a future release error: [options] target value

Bug#872797: jaxe also seems to just be trying to fix fop

jaxe also seems to just trying to fix fop problems; i.e. it has no real dependence on avalon as far as I can see. Again, hard to test without trying a rebuild of a fixed fop. Chris.

Bug#872797: RM? Abandoned upstream in 2004, FTBFS with openjdk-9, few rdeps

Source: avalon-framework Priority: wishlist Could we RM this package? It was officially abandoned by upstream in 2004[1]. There was an upload to Maven Central in 2007, but it doesn't seem to have gone through source control: the last commit was in 2004. It FTBFS with openjdk-9, will require the

Bug#866908: doclint still haunts us

Control: reopen -1 Control: found 9~b181-2 The shipped javadoc command in 9~b181-2 still complains, as this bug report mentions; the testcase above still fails. I believe the patch, while updated, is not being applied: https://sources.debian.net/src/openjdk-9/9~b181-2/debian/rules/#L393 Please

Bug#859551: fixed upstream

Control: tags -1 + fixed-upstream pgbouncer contains an embedded copy of libusual, where the problems appear to lie. Upstream have picked up an updated embedded copy of libusual[1], and now builds fine. The libusual fixes are pretty spread out, e.g.

Bug#858939: fixed upstream

Control: tags -1 + fixed-upstream Upstream have added support for building against either SSL api: https://github.com/jorisvink/kore/commit/95daf3a62bef0b9c84101eecbb464fd474566f45 Chris.

Bug#859053: trivial compilation fix

Control: tags -1 + patch The attached trivial patch fixes compilation in my sid chroot. Chris. diff --git a/libofetion-2.2.2/debian/control b/libofetion-2.2.2/debian/control index 64a8b55..279cd46 100644 --- a/libofetion-2.2.2/debian/control +++ b/libofetion-2.2.2/debian/control @@ -4,7 +4,7 @@

Bug#863568: ..and of course I forgot the attachment

diff --git a/cfengine3-3.9.1/cf-key/cf-key-functions.c b/cfengine3-3.9.1/cf-key/cf-key-functions.c index 7c53ee5..5287b2c 100644 --- a/cfengine3-3.9.1/cf-key/cf-key-functions.c +++ b/cfengine3-3.9.1/cf-key/cf-key-functions.c @@ -48,6 +48,7 @@ RSA *LoadPublicKey(const char *filename) { FILE

Bug#851069: Builds fine with modern libssl

This package builds fine, and all the tests pass fine, with modern libssl. The version dependence on older versions has been there since the package was first uploaded; I am unable to work out why it was added: maybe a dependent library which has now been fixed? All that's necessary to close

Bug#850890: patch

Control: tags -1 + patch Attached is a trivial patch which fixes the build on OpenSSL 1.1. Chris. diff --git a/opennebula-4.12.3+dfsg/debian/control b/opennebula-4.12.3+dfsg/debian/control index 5cd7e8e..df9dc68 100644 --- a/opennebula-4.12.3+dfsg/debian/control +++

Bug#859717: Skipfish uses deleted openssl functionality

One of the failures here is using SSL_CIPHER->algo_strength, which has been removed with, as far as I can see, no replacement. I've raised a bug against OpenSSL upstream to consider exposing this: https://github.com/openssl/openssl/issues/3795 Chris.

Bug#859784: ssl 1.1 fix

Control: tags -1 + patch Control: forwarded https://github.com/tobez/validns/pull/64 A patch to fix compilation with openssl 1.1 is attached. The patch doesn't apply cleanly to upstream, so I sent them a different patch. Chris. diff --git a/validns-0.8+git20160720/debian/control

Bug#828413: fixed upstream

Control: tags -1 + fixed-upstream Upstream have resolved the issues, e.g. in cf1e808e2ffa1f26644fb5d2cb82a919f323deba. Packaging the newer tag (0.7.5) should pick up the fixes.

Bug#851092: upstream

Upstream have committed a better version of the patch for their latest version, which also fixes a load of deprecation warnings: https://github.com/boxbackup/boxbackup/commit/edd3687f067c68b131822e0064cdeff5bf7a3835

Bug#851092: patch

Control: tags -1 + patch Control: forwarded -1 https://github.com/boxbackup/boxbackup/issues/16 The above patch changes a single object into a pointer, and changes init/cleanup into new/free. Chris. commit 9d2bf90676206957a502e9ec1c3cfe4f4b40b0cc Author: Chris West (Faux)

Bug#859549: patch

Control: tags -1 + patch The attached patch fixes the configure script to not check for a removed symbol. Interestingly, the symbol hasn't really existed for a long, long time, and its removal isn't even in the changelog; I had to read the source. `CRYPTO_lock` was its name. Chris. commit

Bug#859227: mixmaster: ssl 1.1 support

Control: tags -1 + patch The attached patch moves the code over to using the openssl 1.1 api. It is entirely renames / accessors. Chris. diff --git a/mixmaster-3.0.0/Src/crypto.c b/mixmaster-3.0.0/Src/crypto.c index 1025b6d..e860a67 100644 --- a/mixmaster-3.0.0/Src/crypto.c +++

Bug#858931: isakmpd: Patch

Control: tags -1 + patch The attached patch moves the code over to using the appropriate accessors for OpenSSL 1.1 in most cases. I have disabled 40-bit DES, and not ported that code, as the crypto is comically useless in the modern world. Chris. diff --git

Bug#859542: puma: libssl-1.1 supported upstream

tags -1 + fixed-upstream thanks This is fixed upstream by this commit: https://github.com/puma/puma/commit/12a856ee63551809ffeb70cb8bfc405d2210febd Please apply the fix, or package the new version. Chris.

Bug#860098: writer2latex: please make the javadoc build reproducible

Source: writer2latex Version: 1.4-1 User: reproducible-bui...@lists.alioth.debian.org Usertags: timestamps Priority: wishlist The javadoc in writer2latex contains timestamps, which prevent the package from building reproducibly. Please pass the -notimestamp argument to javadoc. This can be done

Bug#859960: gcj-jdk: dh_javadoc: please add -notimestamp to invocation

The bug is not really in gcj, it's in a script in gcc-defaults, which ends up in the binary named gcj-jdk for some bizarre reason. However, I've just been looking further, and it looks like the script is literally only used by jaminid, and that jaminid looks pretty abandoned upstream, and has no

Bug#850708: [pkg-gnupg-maint] Bug#850708: gpg: decryption failed: No secret key

Hi There, I think this is a bug with pinentry-gtk-2. Running it almost always results in the following warning: $ echo getpin | pinentry-gtk-2 OK Pleased to meet you ** (pinentry-gtk-2:28067): WARNING **: it took 32 tries to grab the keyboard D this is a test OK Sometimes

Bug#848947: closed by Jerome Benoit <calcu...@rezozer.net> (Bug#848947: fixed in bibtool 2.66+ds-2)

Thanks! I confirm it's fixed on my system with the update. GI -- File not found. Should I fake it? (Y/N)

Bug#848947: bibtool: [Regression] Empty separators cause errors

On Wed, Dec 21, 2016 at 04:34:43AM +, Jerome BENOIT wrote: > Can you send a minimal material (sample(s) + procedure) that reproduce > the issue ? Dear Jerome, Thanks for your quick response, and apologies for not being more explicit. I'm attaching a minimal bib file and rsc file to

Bug#842635: Incorrect output on i386 due to UB

Package: docbook-to-man User: reproducible-bui...@lists.alioth.debian.org Usertags: toolchain Version: 1:2.0.0-35 X-Debbugs-Cc: reproducible-bui...@lists.alioth.debian.org On i386 (but not armhf or amd64), docbook-to-man inserts random characters into the output. e.g. it will sometimes generate

Bug#809982: closed by Sebastian Ramacher <sramac...@debian.org> (Re: Bug#809982: zathura: Memory leak when PDF is refreshed)

On Fri, Jan 08, 2016 at 10:44:00AM +0100, Sebastian Ramacher wrote: > The BTS knows about versions and keeps track of them. See the graph on > the top right of > https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=809982. Oh I see. Thanks. Best, Gautam -- Mathematicians are like Frenchmen:

Bug#809982: closed by Sebastian Ramacher <sramac...@debian.org> (Re: Bug#809982: zathura: Memory leak when PDF is refreshed)

Please don't close this bug as long as 0.3.1-2 is still the only version in Jessie! Some unsuspecting Jessie user will get burnt badly! GI -- One man's folly is another man's wife.

Bug#809982: zathura: Memory leak when PDF is refreshed

On Tue, Jan 05, 2016 at 09:25:57PM +0100, Sebastian Ramacher wrote: > I'd recommend to try the new version available in unstable and check > if the problem still exists. It appears that the problem is fixed in 0.3.4-1 in testing. (If not, I'll reopen a separate bug for 0.3.4-1). The version

Bug#809982: zathura: Memory leak when PDF is refreshed

Update: I ran valgrind. Here's the summary: ==13647== LEAK SUMMARY: ==13647==definitely lost: 274,913 bytes in 62 blocks ==13647==indirectly lost: 29,937 bytes in 1,264 blocks ==13647== possibly lost: 71,528 bytes in 876 blocks ==13647==still reachable:

Bug#809982: zathura: Memory leak when PDF is refreshed

On Tue, Jan 05, 2016 at 09:25:57PM +0100, Sebastian Ramacher wrote: > Otherwise we need a more verbose valgrind log with the GTK+ leaks > filtered out. How do I get you this log? If you tell me what I should run on my system to get you the info you need, I'm happy to do it. I'll check out the

Bug#809982: zathura: Memory leak when PDF is refreshed

Package: zathura Version: 0.3.1-2 Severity: normal Dear Maintainers, There is a memory leak in zathura. Steps to reproduce: 1. Open a PDF file (e.g. output generated by LaTeX) 2. Scroll 3. Refresh the PDF (e.g. by recompiling the LaTeX document) (You might have to do a forward /

Bug#808640: [Pkg-freeipa-devel] Bug#808640: custodia: FTBFS: Could not find any downloads that satisfy the requirement sphinx<1.3.0

On Tue, Dec 29, 2015 at 08:06:06AM +0200, Timo Aaltonen wrote: > > So what's special about this build env compared to normal sbuild, where > it builds just fine? > The build runs without networking, like the main buildds, and the Ubuntu buildds. The Policy requires builds to complete without

Bug#805249: pyparted: FTBFS: PartedException: Unknown disk flag, 1000.

Hmm. I re-test things on my local builder before reporting them, so I've definitely been able to reproduce this failure. My builder is much more normal than jenkins: it uses apt to resolve packages, and things like that. If you don't have any ideas then I can run the build a few more times and

Bug#802059: Already reported against glibmm2.4

Maybe this is a duplicate of: https://bugs.debian.org/800371 ..depending on the solution they arrive at.

Bug#802105: iodine: FTBFS: Assertion 'addr_len == sizeof(struct sockaddr_in)' failed

On Sat, Oct 17, 2015 at 05:58:13PM +0200, gregor herrmann wrote: > I'm lowering the severity of the bug for now, since this doesn't > look like a bug in the code itself but like a weird interaction > between the test suite and pbuilder's optional use of namespaces. > Heh. I try and eliminate

Bug#793319: FTBFS: ImportError: cannot import name component_re

On Wed, Aug 12, 2015 at 04:31:15PM +0300, Gediminas Paulauskas wrote: Now that Bug#779324 is fixed, a simple rebuild would fix the problem. Looks good, yep.

Bug#794372: Oh, the transition!

I have been reminded that there's a nasty C++ transition going on, so these might be transient (i.e. fixed when the upstream libraries are done transitioning). Feel free to close as invalid, drop priority, or whatever! -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with

Bug#793518: [pkg-go] Bug#793518: FTBFS: TestString fails: ini_test.go:167: Dict cannot be stringified as expected.

On Mon, Jul 27, 2015 at 07:26:10PM +0200, Michael Stapelberg wrote: control: tags -1 + unreproducible Chris, was this an issue on your end? Or am I misinterpreting something? The problem seems to have gone away. I was running local builds in response to errors on the reproducible-builds

Bug#793518: [pkg-go] Bug#793518: FTBFS: TestString fails: ini_test.go:167: Dict cannot be stringified as expected.

On Mon, Jul 27, 2015 at 10:45:17PM +0200, Michael Stapelberg wrote: Actually, my bad, the commit I referenced is already in the package in the form of a patch. In your https://paste.debian.net/286717/, I don’t see any mention of the patch, though…? Does your build environment not apply

Bug#792221: libnet-frame-device-perl: FTBFS without networking: t/04-new-default and t/05-new-target fail

On Mon, Jul 13, 2015 at 01:19:29AM +0200, gregor herrmann wrote: Full build log: https://reproducible.debian.net/rb-pkg/unstable/amd64/libnet-frame-device-perl.html It seems to be a bit more complicated than that. With USENETWORK=no I indeed see the failures: ... # Using Test.pm

Bug#792064: [Pkg-javascript-devel] Bug#792064: FTBFS: tests fail with CAP_DAC_OVERRIDE and without networking

On Sun, Jul 12, 2015 at 05:56:08PM +0200, Luca Bruno wrote: However, as this seems to be part of repro-build (which I do care about), you can find a patch here that should fix it. Let me know if it works. Woo, thanks! If you have CAP_DAC_OVERRIDE (e.g. you're running the build as root),

Bug#791410: m17n-db: FTBFS due to missing Build-Conflicts: locales-all

On Mon, Jul 06, 2015 at 03:37:04PM +0530, Harshula wrote: Hi, Could you please elaborate on what changed to cause this side-effect? There was no change to your package or any other package; it has (as far as I'm aware) always been legal to have locales-all instead of locales. It's just

Bug#790800: ..or maybe this is just transition noise

This is happening to other packages too, and I can't find the .moc files I thought were bundled before; maybe it's just transition related and will go away? See e.g. qapt: https://reproducible.debian.net/rb-pkg/unstable/amd64/qapt.html -- To UNSUBSCRIBE, email to

Bug#776292: -Werror is on by default, so FTBFS in sid

Control: severity -1 serious The package fails to build in sid, as -Werror is on by default. Full build log (checked locally): https://reproducible.debian.net/rb-pkg/unstable/amd64/ffrenzy.html -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of

Bug#745224: FTBFS on amd64/sid

Control: severity -1 serious The package fails to build on amd64 in sid with the same errors. Full build log (reproduced outside of pbuilder locally): https://reproducible.debian.net/rb-pkg/unstable/amd64/stretchplayer.html -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org

Bug#789832: unburden-home-dir: FTBFS: t/unexpected-cases.t fails on amd64

On Thu, Jun 25, 2015 at 12:03:04AM +0200, Axel Beckert wrote: t/undo.t ... ok t/unexpected-cases.t ... Dubious, test returned 1 (wstat 256, 0x100) Failed 1/98 subtests thanks for the report, but I couldn't reproduce this, neither with

Bug#778421: haskell-hscurses: FTBFS haskell-devscripts (= 0.9) isn't in unstable

Package: src:haskell-hscurses Version: 1.4.2.0-1 Severity: wishlist Dear Maintainer, The package depends on haskell-devscripts (= 0.9), which is only in experimental, not sid. pbuilder: The following NEW packages will be installed: cdbs{a} ghc{a} ghc-doc{a} ghc-haddock{a} ghc-prof{a}

Bug#775010: libmaven-archiver-java: please allow pom.properties' date to be deterministic

On Sat, Jan 10, 2015 at 10:19:19PM +0100, Emmanuel Bourg wrote: Thank you for the update. It's safe to assume the date always follow the comment specified, the Javadoc for the store() method states: Next, a comment line is always written, consisting of an ASCII # character, the current date

Bug#775010: libmaven-archiver-java: please allow pom.properties' date to be deterministic

Package: libmaven-archiver-java Version: 2.5-1 Severity: wishlist Tags: patch User: reproducible-bui...@lists.alioth.debian.org Usertags: toolchain Hi! While working on the “reproducible builds” effort [1], we have noticed that many Java packages would not build reproducibly because Maven emits

Bug#765472: Additional Info

Hi. Redhat has addressed a bug that looks quite like this one. See BZ#772619 in this document: https://access.redhat.com/documentation/en-US/Red_Hat_Enterprise_Linux/6/html/6.3_Technical_Notes/nfs-utils.html Greetings, Norbert F. -- To UNSUBSCRIBE, email to

Bug#755132: zathura: fails to start (symbol lookup error)

On Fri, Jul 18, 2014 at 09:04:20AM +0200, Sebastian Ramacher wrote: When I run zathura it exits immediately with the message /usr/bin/zathura: symbol lookup error: /usr/bin/zathura: undefined symbol: girara_template_add_variable Looks like you have an old copy of

Bug#755132: zathura: fails to start (symbol lookup error)

Package: zathura Version: 0.2.9-2 Severity: grave Justification: renders package unusable When I run zathura it exits immediately with the message /usr/bin/zathura: symbol lookup error: /usr/bin/zathura: undefined symbol: girara_template_add_variable PS: Note I'm running zathura in a

Bug#724038: libapache2-mod-gnutls: sites-available/default-tls isn't enableable; wrong name

Package: libapache2-mod-gnutls Version: 0.5.10-2 Severity: wishlist Dear Maintainer, /etc/apache2/sites-available/default-tls is provided as an example config, but can't be enabled as a2ensite expects a .conf extension. faux@om:/etc/apache2/sites-available% ls 000-default.conf default-ssl.conf

Bug#722016: netdiag: FTBFS under clang: main(unsigned int, ..) illegal

Package: netdiag Version: 1.1-1 Severity: wishlist Tags: patch tcpspray.c:74:3: error: first parameter of 'main' (argument count) must be of type 'int' main(argc, argv) diff --git a/tcpspray/tcpspray.c b/tcpspray/tcpspray.c index 80102c4..257b259 100644 --- a/tcpspray/tcpspray.c +++

Bug#706990: Only fixed in testing

I noticed that the iceweasel-17.0.6esr-1~deb7u1 is now pulled through wheezy/updates from security.debian.org. The xul-ext-pentadactyl-1.0~rc1-1 from wheezy is incompatible with iceweasel-17.0.6esr-1~deb7u1 (as pointed out above). The xul-ext-pentadactyl-1.0+hg6924-1 (from testing) is compatible

Bug#693874: closed by Christian PERRIER bubu...@debian.org (Bug fixed in 1.15-1)

and this ia not gonna be fixed in squeeze or wheezy? you dont want to give them a security fix that prevents them to unintentionally delete data? -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org

Bug#674142: upstream in 2.4.3 now

as the patch will be in 2.4.3 now, maybe the changes are there now that you will add the patch to the 2.2 debian apache package. The mentioned parameter rename nightmare should now not be a problem. -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of

Bug#661171: Needs desktop-file-utils

I had the same problem. However, I don't think there's a problem with xdg-open. I don't think that xdg-open does any translation of %c or %i (see the source). The translation seems to be done by mimeopen. I installed desktop-file-utils, and did update-desktop-database. It seems fine now, GI --

Bug#661845: biff: postinst assumes existence of /etc/inetd.conf and hence prints errors

Package: biff Version: 1:0.17.pre2412-5 Severity: minor postinst contains: if grep -q 'biff dgram udp wait nobody.mail /usr/sbin/in.comsat comsat' /etc/inetd.conf .. which prints: grep: /etc/inetd.conf: No such file or directory .. as /etc/inetd.conf doesn't exist on my system. This is

Bug#661846: biff: postinst assumes existence of /etc/inetd.conf and hence prints errors

Package: biff Version: 1:0.17.pre2412-5 Severity: minor postinst contains: if grep -q 'biff dgram udp wait nobody.mail /usr/sbin/in.comsat comsat' /etc/inetd.conf .. which prints: grep: /etc/inetd.conf: No such file or directory .. as /etc/inetd.conf doesn't exist on my system. This is

Bug#623194: Please upgrade fvwm to version 2.6.3

On Fri, Jan 20, 2012 at 09:31:42AM +, Michael Stevens wrote: It would be great to see fvwm 2.6.3 in debian. Please Upgrade I too would like to see this. I'd love to see this in Debian too. GI -- LIFE!Insert boring stuff here/LIFE -- To UNSUBSCRIBE, email to

Bug#315142: Gtk+Perl alternative to wacomcpl

The upgrade to xserver-xorg-input-wacom 0.12.0-1 broke everything. Here's an update of the calibration script to work with the new xsetwacom syntax. I've heard there's a way to set the calibration / etc. through HAL. However, as long as xsetwacom Works for me (tm), I'll follow the path of least

Bug#627482: Segmentation fault on level 1 of area 2

I have the same issue. I've noticed the segfault usually occurs when the ball leaves the TOP of the screen. Initially there are a bunch of thin yellow bricks, which break after the ball hits them once. The second time the ball goes there, it goes through the gap and off the top of the screen, and

Bug#626337: xserver-xorg-video-intel: Screen update problems (non-compositing)

On Wed, May 11, 2011 at 10:30:10AM +0200, Cyril Brulebois wrote: There was a suggestion on the Xournal mailing list that this bug is related to http://cgit.freedesktop.org/xorg/driver/xf86-video-intel/commit/?id=3145530feed879082bcfab11ffc8e7fd0911c920 But I haven't mastered debian

Bug#626337: xserver-xorg-video-intel: Screen update problems (non-compositing)

On Fri, May 13, 2011 at 09:49:23PM -0400, gi1242+debianb...@gmail.com wrote: Now installing this driver solves all the problems on my system. I'll post back confirming though. OK. The bug is back. It is a little more sporadic, and a lot less severe. But the bug is certainly back. (However the

Bug#626337: xserver-xorg-video-intel: Screen update problems (non-compositing)

Package: xserver-xorg-video-intel Version: 2:2.15.0-1 Severity: important There are various instances when the screen is not updated. Usually this happens when repeated keyboard, or mouse input is involved at the same time. Some examples: xournal When using the 2.6.38 kernel, some

Bug#315142: Gtk+Perl alternative to wacomcpl

Here's an updated version of the script. With the recent xsetwacom upgrade, it wasn't harvesting device names correctly. Should be fixed now, GI -- 100 THINGS I'D DO IF I EVER BECAME AN EVIL OVERLORD 49. If I learn the whereabouts of the one artifact which can destroy me, I will not send all my

Bug#607603: zsh: Completion of fuser command does not detect psmisc version

Hi Clint, Looks like there's a typo in your patch below: -if _pick_variant -c $words[1] psmisc=psmisc unix -V; then +if _pick_variant -c $words[1] psmisc='#(i)psmisc' unix -V; then Should be '(#i)...' not '#(i)...' right? Thanks, GI PS: I started using zsh 2 weeks ago. It is *AWESOME*,

Bug#569500: Updated patch combining solutions for #572203 and #569500

forwarded 569500 http://dev.mutt.org/trac/ticket/3261 thanks On Fri, Apr 02, 2010 at 09:44:57PM +, Antonio Radici wrote: On Fri, Apr 02, 2010 at 11:35:55AM -0400, James Vega wrote: Since #572203 and #569500 are both results of #528233, I figured I would send an updated patch combining

Bug#607603: zsh: Completion of fuser command does not detect psmisc version

Package: zsh Version: 4.3.10-14 Severity: normal Tags: patch The completion function for fuser tries to determine if fuser is provided by PSmisc, or other the (less functional) generic Unix version. It decides by checking the output of fuser -V for psmisc. However it does not use case insensitive

Bug#601733: python-moinmoin: wrong permissions on /etc/moin files

I can confirm that this is a problem on a fresh Debian Lenny install plus python-moinmoin Version: 1.7.1-3+lenny5. It prevents a successful set up following the steps in /usr/share/doc/python-moinmoin/README.Debian.gz. The error displayed is a s follows: - - - - - - - - - - - - - - - - - - - - -

Bug#590231: improperly nested partition?

On Sat, Oct 23, 2010 at 03:43:53PM -0400, gi1242+debianb...@gmail.com wrote: Perhaps grub-probe thinks that my /dev/sdb1 is an Extended partition, rather than swap? I got the same set of warnings, and had the same issue (i.e. a partition table residing in the mbr of my swap). I just

Bug#568608: Please reopen. Fixed upstream, but not in Debian.

Ok -- this problem has been fixed upstream. It's an issue with xserver-xorg-input-wacom. It's fixed in 0.10.8, for which no Debian package exists yet. The bug is present in 0.10.5+20100416-1 which is the latest version available with Debian. GI -- 'Common' Proof Techniques: 23. Proof by

Bug#590231: improperly nested partition?

On Mon, Oct 04, 2010 at 11:59:44AM +0800, Michael Deegan wrote: Perhaps grub-probe thinks that my /dev/sdb1 is an Extended partition, rather than swap? I got the same set of warnings, and had the same issue (i.e. a partition table residing in the mbr of my swap). I just recreated my swap and

Bug#594154: tcsh: Regression -- double history storage of commands when !#:q is used in jobcmd

On Tue, Aug 24, 2010 at 09:13:31PM +0200, Lucas Nussbaum wrote: The issue does not arise if you don't use the :q modifier. This bug was not present in 6.17.02-3 and is present in 6.17.02-2. Huh? I guess you mistyped one of the new versions. Could you check? Yes, I swapped them apologies.

Bug#594154: tcsh: Regression -- double history storage of commands when !#:q is used in jobcmd

On Tue, Aug 24, 2010 at 07:25:54AM +0200, Lucas Nussbaum wrote: The issue does not arise if you don't use the :q modifier. This bug was not present in 6.17.02-3 and is present in 6.17.02-2. Huh? I guess you mistyped one of the new versions. Could you check? Yes, I swapped them apologies. (I

Bug#594154: tcsh: Regression -- double history storage of commands when !#:q is used in jobcmd

Package: tcsh Version: 6.17.02-3 Severity: normal If the alias jobcmd contains !#:q, then all your typed commands are stored twice in the history. Once as typed, and once with only the first argument (and aliases expanded). The issue does not arise if you don't use the :q modifier. This bug was

Bug#560244: ITP: mysql-cluster

Toni Thanks for the update. I am really glad this being worked on. Do you know if the plan is have 2 separate packages like in Ubuntu, one w/ cluster support and one without (mysql-cluster-server mysql-server)? Also, if I can be of assistance in this effort to get this into Debian please let me

Bug#560244: ITP: mysql-cluster

Unfortunately the Ubuntu mysql-cluster package is broken, it has been since the release of 10.04, although there is a workaround that works. The bug report for this issue has been open since May with no activity, it's status is still still listed as new:

Bug#568608: closed by Cyril Brulebois k...@debian.org (Bug#568236: fixed in xorg-server 2:1.7.5.902-1)

On Mon, Mar 15, 2010 at 11:51:25PM +, Debian Bug Tracking System wrote: We believe that the bug you reported is fixed in the latest version of xorg-server, which is due to be installed in the Debian FTP archive: xdmx-tools_1.7.5.902-1_amd64.deb to

Bug#574003: Acknowledgement (alacarte recommends gnome-panel, should be suggests or not at all)

I've just realised that alacarte isn't actually working correctly. Prior to looking into it further i'm assuming this is due to some of the packages that would've come with gnome-panel not being installed. Sorry for the time waster, please disregard suggestion/bug report. Regards, Robert

Bug#568608: Regression: Slow VT switching

On Tue, Mar 02, 2010 at 12:31:34AM +1030, Ron wrote: This looks like you're probably just getting bitten by the fact that there is no support for serial tablets yet in the udev/config server. That should be coming soon. There is a patch in bug #568236 if you want it even sooner. Thanks Ron.

Bug#502346: virtualbox-ose-modules-* need to be rebuilt

reopen 502539 merge 502539 502346 thanks these bugs should have been merged (502539 was closed without explanation). live well, vagrant -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]

Bug#490596: approx: cannot download Release or Packages files

On Sat, Jul 12, 2008 at 08:33:03PM -0400, Eric Cooper wrote: it's transparently being proxied through squid, and i'm wondering if that's somehow messing with it, although until yesterday (the last time it worked), it was working with the identical squid configuration. the same mirrors are

Bug#462292: gjdoc: fails to upgrade/remove/install when /proc is not mounted

retitle 462292 gjdoc: fails to upgrade/remove/install when /proc is not mounted thanks it also fails similarly on removal or installation when /proc is not mounted. live well, vagrant -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL

  1   2   >