Bug#1042968: emacs: Gnus unusable after upgrading to Emacs 29

Hi David, David Bremner wrote: > Please try to duplicate the problem with "emacs -q". I suspect there is > either some obsolete/broken third party package or just some personal > configuration causing this problem. You're right, the problem was in my .gnus.el which had a

Bug#1042968: emacs: Gnus unusable after upgrading to Emacs 29

Package: emacs Version: 1:29.1+1-2 Severity: normal Dear maintainer, This morning, I performed the following upgrade: [UPGRADE] emacs:amd64 1:28.2+1-16 -> 1:29.1+1-2 [UPGRADE] emacs-bin-common:amd64 1:28.2+1-16 -> 1:29.1+1-2 [UPGRADE] emacs-common:amd64 1:28.2+1-16 -> 1:29.1+1-2 [UPGRADE]

Bug#1042817: doesn't apply MODE="0664" action to uinput upon boot anymore

Package: udev Version: 254-1 Severity: normal Dear maintainer, The computer this report is sent from runs sid and is upgraded almost daily. The problem described here appeared on the first boot of 2023-07-20 and is still present today. This computer has the following rule in

Bug#1017757: Same error with emacs 28.1+1-2

Since #1017739 is filed on emacs-lucid and I use emacs-gtk, not emacs-lucid, I don't know how to reassign this bug to merge it with #1017739; will let this to the Emacs maintainer. Thanks & regards :-) -- Florent

Bug#1017757: Same error with emacs 28.1+1-2

Thanks for your input, Luis! TL;DR: this is the same bug as #1017739: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1017739 While trying what you suggested, I had again the same error after: - quitting Emacs; - deleting ~/.emacs.d; - upgrading again to the current version of the

Bug#1017757: emacs: early error: no suitable directory for output in 'comp-native-load-path'

After downgrading to 1:27.1+1-3, the error is gone. Regards -- Florent

Bug#1017757: emacs: early error: no suitable directory for output in 'comp-native-load-path'

Package: emacs Version: 1:28.1+1-1 Severity: normal Dear maintainer, After performing the following upgrades today on sid: [UPGRADE] emacs:amd64 1:27.1+1-3.1 -> 1:28.1+1-1 [UPGRADE] emacs-bin-common:amd64 1:27.1+1-3.1+b1 -> 1:28.1+1-1 [UPGRADE] emacs-bin-common-dbgsym:amd64 1:27.1+1-3.1+b1 ->

Bug#1007697: xserver-xorg-input-wacom: New release completely breaks Intuos5 touch S

Package: xserver-xorg-input-wacom Version: 1.0.0-1 Severity: important Hello, Yesterday, my xserver-xorg-input-wacom:amd64 package was upgraded from version 0.34.99.1-1+b1 to 1.0.0-1, which rendered my Wacom Intuos5 touch S tablet completely unusable: moving the finger over the touch pad has no

Bug#1005102: sane-utils.postinst: 65: [: /var/lib/saned: unexpected operator

Package: sane-utils Version: 1.1.1-1 Severity: normal Hello, There is a syntax error in /var/lib/dpkg/info/sane-utils.postinst which causes the following message to be printed: /var/lib/dpkg/info/sane-utils.postinst: 65: [: /var/lib/saned: unexpected operator I could suggest a fix, however

Bug#990331: reportbug: cups-browsed printing fails due to apparmor config with message 'No destination host name supplied by cups-browsed for printer'

Hello Brian, As I wrote in my previous message, the two lines I quoted from my /var/log/syslog are from **before the fix** (i.e., before I purged cups-browsed). Regards -- Florent

Bug#990331: reportbug: cups-browsed printing fails due to apparmor config with message 'No destination host name supplied by cups-browsed for printer'

Hello, I also had the not-very-helpful message from CUPS: No destination host name supplied by cups-browsed for printer, is cups-browsed running? Of course, cups-browsed was well running and I even tried to restart it, also cups.service, etc. The solution I found, before reading this

Bug#980144: mailutils: movemail does not remove start mailbox when moving

Hello, This appears to be a duplicate of #980042: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=980042 Regards -- Florent

Bug#980042: mailutils: does not remove extracted emails

Package: mailutils Version: 1:3.11.1-4 Severity: important Dear maintainer, Since I upgraded mailutils from 1:3.10-3+b1 to 1:3.11.1-2 a couple of days ago, movemail doesn't remove extracted emails anymore from the source mbox file (I do *not* use option --keep-messages). Example: 1) Verify

Bug#975919: okular: Back and Forward navigation functions are broken

/commit/585340cef5ca4dd1e26fe3baea1cf396f8de6469>. + + -- Florent Rougon Wed, 25 Nov 2020 22:25:47 +0100 + okular (4:20.08.3-1) unstable; urgency=medium * Team upload. diff -Nru okular-20.08.3/debian/patches/fix-back-and-forward-navigation.patch okular-20.08.3/debian/patches/fix-back-and-forward-navigation.patch --- okul

Bug#972885: emacs: Bundled Gnus unable to enter any group

tags 972885 + upstream thanks Hi Rob, thanks for your reply. Rob Browning wrote: > Nice catch. Have you, or are you already planning to post this > upstream? Well, I haven't done so but could certainly do it. I assume the Gnus development list ("ding") would be more appropriate than an Emacs

Bug#972885: emacs: Bundled Gnus unable to enter any group

retitle 972885 Lexical binding causes regression for gnus-summary-highlight thanks The problem appears to be due to the (presumably recent) use of lexical binding in /usr/share/emacs/27.1/lisp/gnus/gnus-sum.el.gz (cf. lexical-binding:t on the first line). It is triggered by this piece of

Bug#972885: emacs: Bundled Gnus unable to enter any group

Package: emacs Version: 1:27.1+1-2 Severity: normal Hello, After upgrading my emacs packages today: [UPGRADE] emacs:amd64 1:26.3+1-2 -> 1:27.1+1-2 [UPGRADE] emacs-bin-common:amd64 1:26.3+1-2 -> 1:27.1+1-2 [UPGRADE] emacs-bin-common-dbgsym:amd64 1:26.3+1-2 -> 1:27.1+1-2 [UPGRADE]

Bug#965193: policykit-1: fails to install: chown error on /usr/lib/policykit-1/polkit-agent-helper-1

Hello, Same problem here, please provide a fix. Thanks. -- Florent

Bug#852108: usbguard: fails to start after installation: "ERROR: Configuration: /etc/usbguard/rules.conf: usbguard::Exception"

Hello, Thanks for your work on this package! This bug has the 'pending' tag since January 24, 2017. Maybe the fix is not pending anymore? Thanks & regards -- Florent

Bug#918358: libsane:amd64: Missing permissions for scanner group on usb device

Hello, Same problem for me as well as for other people at [1]. This happened after upgrading to 'buster' the machine where the scanner is plugged. Adding the udev rule fixes the issue. This regression is annoying, it would be nice for other users if our dear maintainers could fix it. :-) Thanks

Bug#921598: No METAR available since noaa.gov switched to https

Hi again Gabriel, hi Tobias, "Dr. Tobias Quathamer" wrote: > Hi Gabriel and Florent, > > thanks for reporting this bug and pointing to the commits! I'm currently > preparing a new upload of simgear which should still be in time for buster. The partial revert I foresaw has happened. :)

Bug#921598: No METAR available since noaa.gov switched to https

Hello, "Gabriel F. T. Gomes" wrote: > I updated the merge request. > > When I first wrote the merge request, upstream did not have a fix for > the METAR problem. Now they do [1]. So, I removed the simple patch I > wrote, and replaced it with this upstream fix. (...) > [1] >

Bug#887411: [pkg-fgfs-crew] Bug#887411: fgfs: segfaults when receiving UDP data too early

Hello, Frank Heckenbach wrote: > When receiving UDP data too early, fgfs segfaults after giving the > message: > > AI error: updating aircraft without traffic record at ... > > I've traced the segfault to trafficcontrol.cxx:984 > > At this point, "current" is

Bug#870806: Also fails with 2.1.22

Hi, The workaround I've found is to put: disable-ipv6 in ~/.gnupg/dirmngr.conf. It's a pity that IPv4 isn't supported by default anymore, because some people disable IPv6 on their boxes *precisely* for security reasons---following the same logic that leads one to only install the server

Bug#873439: [pkg-fgfs-crew] Bug#873439: flightgear: CVE-2017-13709: Incorrect access control

are not in the Debian DEP-3 format, this needs fixing. + + -- Florent Rougon <f.rou...@free.fr> Mon, 28 Aug 2017 18:07:28 +0200 + flightgear (3.0.0-5+deb8u2) jessie; urgency=high * Add patch restrict-save-flightplan-secu-fix-faf872.patch: prevent diff -Nru flightgear-3.0.0/debian/patche

Bug#869309: [pkg-fgfs-crew] Bug#869309: Bug#869309: Updating the fgo Uploaders list

Hi, Tobias Frost wrote: > It's your decission; close the bug, you will be kept as Uploader, > keep it open -> you will eventually be removed. (I gues this decission > should not be delegated to the maintainer, but thats just my 2ct) This bug is fixed in the Git repository on

Bug#869310: Updating the pythondialog Uploaders list

Hallo Tobias, Tobias Frost <t...@debian.org> wrote: > Source: pythondialog > Version: 3.4.0-1 > Severity: minor > User: m...@qa.debian.org > Usertags: mia-teammaint > > Florent Rougon <f...@debian.org> has retired, so can't work on > the pythondialog package

Bug#869309: [pkg-fgfs-crew] Bug#869309: Bug#869309: Updating the fgo Uploaders list

Hallo Tobias, Tobias Frost wrote: > The database told me you've retired. If that is not the case or you've > resumed (e.g using your @free.frp email) please appologize and just > close the "Remove from uploaders" bugs. I absolutly do not want that > you're being removed from

Bug#869309: [pkg-fgfs-crew] Bug#869309: Updating the fgo Uploaders list

Hello, Tobias Frost <t...@debian.org> wrote: > Florent Rougon <f...@debian.org> has retired, so can't work on > the fgo package anymore (at least with this address). > > We are tracking their status in the MIA team and would like to ask you > to remove them from the Up

Bug#857050: firefox no longer plays sound without pulseaudio daemon

Hello, Let me add a “me too” to express my sadness seeing firefox not being able to use alsa anymore. IMO, this is a clear regression. Regards -- Florent

Bug#848114: flightgear: Allows the route manager to overwrite arbitrary files

Markus Wanner wrote: > Hello Florent, > > thanks a lot for your notification and the patch(es). Uploads to stable > (security) and unstable should follow, shortly. Fine, thank you, Markus! Regards -- Florent

Bug#848114: flightgear: Allows the route manager to overwrite arbitrary files

ore overwriting the file. . (also add a missing include that is directly needed for this commit) Author: Florent Rougon <f.rou...@free.fr> Origin: upstream, https://sourceforge.net/p/flightgear/flightgear/ci/280cd523686fbdb175d50417266d2487a8ce67d2/ --- a/src/Autopilot/route_mgr.cxx +++

Bug#785606: linux-image-4.0.0-1-amd64: DragonRise joystick support broken in 4.0.2-1

It seems the bug was fixed by this upstream commit: commit 18339f59c3a6698ee17d32970c9e1e450b16e7c3 Author: Maciej Zuk Date: Thu Sep 3 21:46:39 2015 +0200 HID: dragonrise: fix HID Descriptor for 0x0006 PID Fixed HID descriptor for DragonRise Joystick. Replaced default descriptor

Bug#785606: linux-image-4.0.0-1-amd64: DragonRise joystick support broken in 4.0.2-1

Update: - upstream kernel 4.3.3 (most probably Debian also) and many kernels (probably all) between, at least and inclusive on both ends, versions 4.0.2 and 4.3.3 are affected by this bug; - upstream kernel 4.5.5 is *not affected*; Debian kernels 4.5.4-1 and 4.5.5-1 are *not

Bug#816227: ping: socket: Address family not supported by protocol (raw socket required by specified options).

Hello, Noah Meyerhans wrote: > Confirmed that this breaks ping when run without an explicit address > family. This is actually already fixed upstream, but not in a tagged > snapshot. It'll be fixed in the next upload, by cherry-picking that > commit or syncing a new snapshot.

Bug#815864: python3-venv: unable to create a virtual environment

Simple workaround for this bug: 1) Create the venv with --without-pip. For instance: /usr/bin/python3.5 -m venv --without-pip 2) Download https://bootstrap.pypa.io/get-pip.py as ~/tmp/get-pip.py. 3) Bootstrap pip "manually" in your venv: /bin/python ~/tmp/get-pip.py HTH

Bug#816227: ping: socket: Address family not supported by protocol (raw socket required by specified options).

Hello, On Sun, 28 Feb 2016 22:38:05 + Jamie Heilman wrote: > Noah Meyerhans wrote: > > I cannot reproduce this on a host with no ipv6 connectivity. Does > > 'ping -4 127.0.0.1' work any differently? > > Yeah, that works. Same here. 'ping -4 ' works fine but

Bug#815864: python3-venv: unable to create a virtual environment

Some more info: Inserting a 'print(cmd)' at line 259 showed that the direct cause of the error message is the command: ['/home/flo/python-venv/testdir/bin/python3.5', '-Im', 'ensurepip', '--upgrade', '--default-pip'] exiting with a non-zero exit status. Running this command by hand after

Bug#815864: python3-venv: unable to create a virtual environment

Package: python3-venv Version: 3.5.1-2 Severity: serious Justification: renders the package unusable Hello, It seems current Python 3 packages in Debian unstable don't allow creating a virtual environment anymore with pyvenv and friends: ~/python-venv % /usr/bin/python3.5 -m venv testdir The

Bug#811479: boot fails in "run-init -n ..."

Hello, Same problem here after yesterday's upgrade. The 0.122~a.test initramfs-tools and initramfs-tools-core packages mentioned by Ben at allowed my system to boot, thank you! (along with the Debian jessie installation DVD in rescue

Bug#808762: 'remote: error: unable to update info/refs+' when pushing to a repo on alioth

Package: tracker.debian.org Severity: normal Hello, I got the error cited in the subject when doing 'git push' for the fgo Git repo hosted on alioth: % git push Counting objects: 4, done. Delta compression using up to 8 threads. Compressing objects: 100% (4/4), done. Writing objects: 100%

Bug#805964: geographiclib: Please provide a package for Python 3

Hi Bas, > I've just uploaded geographiclib (1.45-2) which adds > python3-geographiclib using pybuild for all python versions. > > Because python3-geographiclib is a new package it will have to pass the > NEW queue before it will be available in the archive. That's great, thank you very much! :-)

Bug#805964: geographiclib: Please provide a package for Python 3

Source: geographiclib Severity: wishlist Hello, I am using GeographicLib under Python 3 for FFGo[1], and it works fine for what I ask it to do. It would be nice for users if you could ship a package for Python 3 in addition to the Python 2 package. Not to mention that Python 2 is progressively

Bug#801150: openssh-client: PubkeyAuthentication not working when ~/.ssh/id_rsa.pub is present

retitle 801150 PubkeyAuthentication not working when ~/.ssh/id_rsa.pub is present thanks (I let you adjust the severity as you see fit) Hi Colin, thanks for your prompt answer! Colin Watson wrote: > Do you have a good reason to still be using the RSAAuthentication >

Bug#801150: openssh-client: RSAAuthentication not working

Package: openssh-client Version: 1:6.9p1-2 Severity: important Hello, I am having problems connecting to other hosts using RSAAuthentication. The password prompt for the key does not even appear. Adding the key to the ssh-agent doesn't help. Usually, it works fine between the same hosts. Tested

Bug#785606: linux-image-4.0.0-1-amd64: DragonRise joystick support broken in 4.0.2-1

forwarded 785606 Benjamin!Tissoires!t!redhat!com thanks Bug forwarded on Wed, 26 Aug 2015 10:37:23 +0200 to the author of commit 79346d620e9de87912de73337f6df8b7f9a46888, no response received so far AFAICT. This bug still applies to: 4.2.0-1-amd64 #1 SMP Debian 4.2.1-1 (2015-09-25) x86_64

Bug#750601: GnuTLS: Error in the push function when using a client certificate

reopen 750601 retitle 750601 wget: Unable to connect with HTTPS using a client certificate found 750601 1.16-1 tags 750601 - moreinfo thanks Hello, I'm afraid the problem remains that wget cannot download anything with HTTPS when a client certificate is required. Tested on current unstable and

Bug#750601: GnuTLS: Error in the push function when using a client certificate

Hello Noël, Noël Köthe n...@debian.org wrote: Is this still reproduce able with wget in jessie (1.16) or later? Um, that was more than one year ago... and I don't have the Apache setup to test this anymore, unfortunately. I'll keep you informed when I can do this test again (on jessie and

Bug#788856: joystick: jscal-store and jscal-restore can't find the product name or vendor anymore

Well, this problem seems to be sorted out now. Since the joystick package has received no update in the meantime, and I don't think I have upgraded the kernel after the last time I reproduced the bug, I suppose the fix may have been brought by a recent udev upgrade (221-1?). From my POV, the bug

Bug#789922: kio-dev: uninstallable on current unstable

Hi Lisandro, Lisandro Damián Nicanor Pérez Meyer perezme...@gmail.com wrote: Qt5 is currently going trough a transition, so this is just OK. You just need to wait until it's sorted out. Actually you will need to wait until the package gets pushed to unstable or rebuilt in experimental. It

Bug#789922: kio-dev: uninstallable on current unstable

Package: kio-dev Version: 5.9.0-1 Severity: serious Justification: Policy 7.2 Hello, Since yesterday's upgrade, kio-dev is not installable anymore on sid: # aptitude install kio-dev The following NEW packages will be installed: kio{a} (for kio-dev) kio-dev libdbusmenu-qt5-2{a} (for kio-dev)

Bug#785606: linux-image-4.0.0-1-amd64: DragonRise joystick support broken in 4.0.2-1

retitle 785606 HID support broken for some devices (incl. DragonRise USB joystick) tags 785606 upstream notfound 785606 3.16.7-ckt9-3 thanks On Mon, 18 May 2015 11:29:32 +0200 Florent Rougon f.rou...@free.fr wrote: The DragonRise joystick used to work fine in linux-image-3.16.0-4-amd64

Bug#788856: joystick: jscal-store and jscal-restore can't find the product name or vendor anymore

Package: joystick Version: 1:1.4.8-1 Severity: important Hello, I used to be able to use jscal-store and jscal-restore normally a few months ago (probably with kernel linux-image-3.16.0-4-amd64 version 3.16.7-ckt9-3), but these programs don't work in a satisfactory way anymore: # jscal-store

Bug#787464: libplib1: jsJoystick::open() breaks system calibration on Linux

Package: libplib1 Version: 1.8.5-7 Severity: important Tags: upstream [ Duplicating a bug I reported upstream, in the hope it could be fixed in Debian at least, as the upstream project appears to be dead unfortunately ] [ FlightGear maintainers in Cc, as proper joystick calibration is likely

Bug#787464: Acknowledgement (libplib1: jsJoystick::open() breaks system calibration on Linux)

of the OS joystick + driver, it should not break system settings for that reason!) + + -- Florent Rougon f.rou...@free.fr Mon, 01 Jun 2015 21:34:52 +0200 + plib (1.8.5-7) unstable; urgency=medium * Enable hardened build flags @@ -484,3 +496 @@ -Local variables: -mode: debian-changelog

Bug#785606: linux-image-4.0.0-1-amd64: DragonRise joystick support broken in 4.0.2-1

Package: src:linux Version: 4.0.2-1 Severity: normal Hello, The DragonRise joystick used to work fine in linux-image-3.16.0-4-amd64 version 3.16.7-ckt9-3 and earlier versions, however its support is broken in linux-image-4.0.0-1-amd64 version 4.0.2-1. The problem is with the right stick: -

Bug#780716: [pkg-fgfs-crew] Bug#780716: flightgear-data: nasal scripts can ready any file

Hi again, As far as I know, this bug is still present in 3.4.0+dfsg-0~exp1 (from experimental). The fix you applied to unstable (commit d8603af7f98a6394442818d823a79b680b1f9e8b) can be cherry-picked to experimental with minor conflicts (d/changelog and d/patches/series). It seems to work fine

Bug#775903: systemd: 'service initscript start' starts initscript.dpkg-dist under systemd

Hi Martin, hi Michael, Martin Pitt mp...@debian.org wrote: I'm 99% sure that this is another duplicate of https://bugs.debian.org/775404 I take it you have a /run/systemd/generator.late/fetchmail.service symlink which points to fetchmail.dpkg-dist.service? Well, I have this file but it is a

Bug#775903: systemd: 'service initscript start' starts initscript.dpkg-dist under systemd

Package: systemd Version: 215-9 Severity: serious Tags: security Dear maintainer, I tried systemd after a wheezy → sid upgrade and encountered an annoying problem: after modifying a file related to my /etc/init.d/fetchmail script[1], I decided to start the fetchmail service with 'service

Bug#750601: GnuTLS: Error in the push function when using a client certificate

Package: wget Version: 1.13.4-3+deb7u1 Severity: normal Hello, It seems unfortunately that bug #646983 is back in wheezy, or something that looks similar: % wget --certificate=*.pem --private-key=*** -rc -nH -np -vvv \ --ca-cert=*** https://server-name:port/path --2014-06-03 23:09:39--

Bug#746475: flightgear: crash with Nasal bindings

Package: flightgear Version: 3.0.0-1 Severity: normal Tags: fixed-upstream Origin: upstream, https://gitorious.org/fg/flightgear/commit/b3c7cb7c151858ef79f9371a29be49915e5d3803 Bug: https://code.google.com/p/flightgear-bugs/issues/detail?id=1397 Author: Nicholas Scheel Date: Tue Apr 15 14:13:46

Bug#746475: flightgear: crash with Nasal bindings

Hello, Sorry, I hit the wrong key in the draft folder, before writing the body of the e-mail! So, I encountered a crash with FlightGear 3.0.0-1 and the backtrace led me to upstream bug https://code.google.com/p/flightgear-bugs/issues/detail?id=1397 That address indicates that the bug has been

Bug#741411: fgo: invalid or outdated format for machine-readable debian/copyright

By the way, the copyright file has a Maintainer field set to: Debian FlightGear Crew pkg-fgfs-c...@lists.alioth.debian.org which seems to be in contradiction with debian/control. The patch I posted renamed the field to Debian-Maintainer to make lintian (IIRC) happy, but given the contents of

Bug#741410: fgo: new upstream version available

Package: fgo Version: 1.3.1-2 Severity: wishlist Hello, There have been a few fgo releases in the last years... At the time of this writing, upstream is at 1.5.0. Will attach a patch once I get the bug number. Thanks. -- System Information: Debian Release: 7.4 APT prefers stable-updates

Bug#741411: fgo: invalid or outdated format for machine-readable debian/copyright

Package: fgo Version: 1.3.1-2 Severity: normal Hello, When building fgo, lintian complains: W: fgo source: syntax-error-in-dep5-copyright line 18: Continuation line outside a paragraph. The patch in #741410 addresses this problem. -- Florent -- To UNSUBSCRIBE, email to

Bug#741410: fgo: new upstream version available

); + - remove the leading slashes. + + -- Florent Rougon f.rou...@free.fr Wed, 12 Mar 2014 11:57:33 +0100 + fgo (1.3.1-2) unstable; urgency=low * Fixed lintian info warning about encoding in .desktop file diff -ur fgo-1.3.1/debian/copyright fgo-1.5.0.for_debian/debian/copyright --- fgo-1.3.1/debian

Bug#670966: fgo: Default paths for FG_ROOT and FG_SCENERY are incorrect

Hello, This is addressed in the proposed patch for bug #741410. -- Florent -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org

Bug#737870: fgo: menu icon entry missing

of the icon in XPM format, install it in +/usr/share/pixmaps and declare it in debian/menu (closes: #737870). + + -- Florent Rougon f.rou...@free.fr Wed, 12 Mar 2014 16:22:28 +0100 + fgo (1.5.0-1~frougon1+deb7.0) stable; urgency=low * Improve debian/patches/increase-font-sizes.patch: all font

Bug#655154: woof: No space left on device when /tmp is full

tags 655154 + upstream forwarded 655154 si...@budig.de thanks Hello, The attached patch fixes this problem. I have forwarded it to the upstream maintainer. Here follows the patch description: , | Improve handling of files received with option -U | | Instead of storing the downloaded

Bug#732640: woof: could have better tagging

Package: woof Version: 20091227-2 Severity: wishlist Hello, woof is a very nice program but not so easy to find among the myriad of Debian packages. Neither did the pages for sendfile and so-called similar packages on packages.debian.org, nor did a search for file transfer in packagesearch give

Bug#573007: NIC r8169 doesn t start at restart on kernel linux-image-2.6.32-trunk-686 (workaround)

Hi, I applied this patch (http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=573007#54) on March 29[1], but unfortunately, the bug is still there for me. More precisely, my script which detects and works around the problem triggered at the following times since then: Thu, 01 Apr 2010 21:11:18

Bug#573007: NIC r8169 doesn t start at restart on kernel linux-image-2.6.32-trunk-686 (workaround)

Another possible workaround (didn't try Ben's one, I just discovered this thread today): Save the attached script in /root/bin/flo-check-network-connections (using bash because of $RANDOM). Change the line: interfaces=eth0 eth1 to list the interfaces that have the problem (and that you want

Bug#573007: NIC r8169 doesn t start at restart on kernel linux-image-2.6.32-trunk-686 (workaround)

Would be even better with the script actually attached... -- Florent #! /bin/bash interfaces=eth0 eth1 max_attempts=15 exit_status=1 for attempt in $(seq 1 $max_attempts); do all_intf_ok=1 for intf in $interfaces; do ifconfig $intf | grep /dev/null ^[[:space:]]*inet addr: \

Bug#573007: NIC r8169 doesn t start at restart on kernel linux-image-2.6.32-trunk-686 (workaround)

Ben Hutchings b...@decadent.org.uk wrote: This is now being handled upstream and there is a proposed fix. We will apply that once it has been tested across a range of RTL8169-family chips. Thank you. If it can be of some help, I may test something. I am currently using upstream 2.6.32

Bug#444307: [Frank Küster] Re: Wrong documentation for CM-Super in texdoctk

Norbert Preining [EMAIL PROTECTED] wrote: Or we just ignore it and wait for something more useful ... that reminds me that I have to ask Florent whether there is any progress on the new texdoc viewer... Sorry about that, but no. Unfortunately, I'm unable to work on it these days, and I cannot

Bug#441526: lmodern: updmap-sys failed.

Frank Küster [EMAIL PROTECTED] wrote: I agree that we shouldn't change dh_installtex's default. Florent, will you have time to fix this? Sorry, I don't feel well these days. Please do what you think should be done. -- Florent

Bug#400494: lirc: Fix for the build failure caused by the inclusion of linux/config.h is incomplete

Hi, Loïc's upload of lirc 0.8.0-10 commented out the inclusion of linux/config.h in drivers/lirc_dev/lirc_dev.c, but that was not enough for me. lirc-modules-source still failed to build because drivers/lirc_serial/lirc_serial.c also wants to include that file. Commenting out the relevant line

Bug#435132: texlive-metapost: Please include latest latexmp version

Dear TeX Live maintainers, We have here a request in the Debian BTS to update the version of latexmp as shipped in TL. Could anyone take care of this? Dylan Thurston [EMAIL PROTECTED] wrote: The version of latexmp included with texlive-metapost, version 1.1.0, is very outdated. The current

Bug#436235: texlive-lang-ukenglish: postinst and uninstall fail: Package color Error: No driver specified.

Hi, Johannes Rohr [EMAIL PROTECTED] wrote: I was apparantly hit by bug #425803 Can we (or you) close the bug, then? Thanks. -- Florent -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]

Bug#434706: texlive-latex-base: color package uses black for figure captions and page numbers

retitle 434706 Color handling could have the concept of a default foreground color severity 434706 wishlist thanks Hi, Ryo Furue [EMAIL PROTECTED] wrote: Hmm . . . It seems to me that a possible solution is to add a default foreground color (DFC) to the protocol. The LaTeX color package

Bug#436690: gkrellm-reminder: cannot remind about events more than 120 minutes early

Package: gkrellm-reminder Version: 2.0.0-2 Severity: minor Hi, In the Settings tab, there is a spinbox for Remind me about events x minutes early. The value of x is limited to 120 in reminder.c, line 2371: adj_remind_early = gtk_adjustment_new( config.remind_early, 0, 120, 1, 10, 0 ); For

Bug#436687: tex-common: Package upgrade fails in the Configure stage

reassign 436687 aptitude retitle 436687 Symbol lookup error thanks This looks like a problem with aptitude or one of its dependencies. Thus, I am reassigning the bug. -- Florent -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]

Bug#434706: texlive-latex-base: color package uses black for figure captions and page numbers

Hi, Ryo Furue [EMAIL PROTECTED] wrote: If the original LaTeX source uses the color package, xdvi -rv shows figure captions and page numbers in black, which is invisible in default colors. I confirmed they are black by Frankly, I doubt upstream would want to workaround that (I say

Bug#430976: texlive-metapost: symbols don't appear when using metapost

Rogério Brito wrote: I think that Florent might not have seen the problem as, from what I understand, he has lmodern fonts installed in his system. Quite so. -- Florent

Bug#433329: Please clarify whether Lucida Bright/Lucida Sans fonts are supported

[Dropping the TL upstream list] Rogério Brito [EMAIL PROTECTED] wrote: Wouldn't it be the case for having the support files for non-free fonts to be in contrib here? If I learned it correctly, I think that is the purpose of the contrib section. Is that right? Quite correct. But if the

Bug#400742: Bug#431671: Bug#400742: Bug#431671: piuparts test: fails to install: line 43: update-updmap: command not found

Hi, Nice to see you back! Frank Küster [EMAIL PROTECTED] wrote: I suggest we remove the wontfix tag and add a block on the dpkg bug requesting the trigger, what do you think? Fine, feel free to do so. Regards, -- Florent

Bug#400742: Bug#431671: Bug#400742: Bug#431671: piuparts test: fails to install: line 43: update-updmap: command not found

Norbert Preining [EMAIL PROTECTED] wrote: retitle 400742 dh_installtex should check the existence for tex file tags 400742 - wontfix thanks [...] Ok, I retitled the bug and removed the wontfix stuff. If I find time I will implement it. *WARNING* *WARNING* *WARNING* *WARNING* *WARNING*

Bug#400742: Bug#431671: Bug#400742: Bug#431671: piuparts test: fails to install: line 43: update-updmap: command not found

Rene Engelhard [EMAIL PROTECTED] wrote: Reason: if there were TeX files in any previous version of the package (up to the previous Debian release), then mktexlsr *has* to be run. Why weren't they in their own package then? Huh? I don't know. I'm not the maintainer of texpower. Then if the

Bug#430976: texlive-metapost: symbols don't appear when using metapost

Rogério Brito [EMAIL PROTECTED] wrote: Indeed, they lack the fonts. Did you notice that the generated output comes with the math fonts embedded many times, when used this way? And one thing that is quite noticeable is that the fonts embedded in the PDF file normally have names in all caps,

Bug#430976: texlive-metapost: symbols don't appear when using metapost

Florent Rougon [EMAIL PROTECTED] wrote: Weird. It does here on etch and also on sid (the sid chroot isn't very up-to-date, I'm upgrading it right now and will tell you if this changes something once the upgrade is finished). On an up-to-date sid chroot, I have the same results except

Bug#430976: texlive-metapost: symbols don't appear when using metapost

Hi, Rogério Brito [EMAIL PROTECTED] wrote: I am trying to create a diagram for a text of mine using metapost. Unfortunately, when I typeset the following file (having the environment variable TEX=latex), I can't see all the symbols: the square does not appear (its position is blank), while

Bug#430976: texlive-metapost: symbols don't appear when using metapost

Rogério Brito [EMAIL PROTECTED] wrote: Sorry for the use of wrong names. They should all have been metapost-fail in the examples above. I understood that. Here, with texlive-metapost version 2007-12.np.etch.1, including the compiled figure in a LaTeX document processed by pdfTeX works fine.

Bug#364426: xserver-xorg-video-ati: display completely garbled with DRI, can even hard lock

Hi, Brice Goglin [EMAIL PROTECTED] wrote: About a year ago, you reported a bug to the Debian BTS regarding the display being garbled when DRI is enabled on an ATI board. Did you reproduce this problem recently? With Xorg/Etch? With latest xserver-xorg-core and drivers? If not, I will close

Bug#429314: texlive-context: missing dependency on lmodern

Sanjoy Mahajan [EMAIL PROTECTED] wrote: So, why are you reporting a bug against texlive-context, since you know it is deprecated? To help Debian ConTeXt users, because etch will be used for perhaps two years (and longer by people who then run it as 'oldstable'). OK. [...] Meanwhile I'll

Bug#429314: texlive-context: missing dependency on lmodern

Hi, Sanjoy Mahajan wrote: Installing 'lmodern' fixes the errors, because it provides those missing tfm files. So texlive-context should depend on lmodern, not merely recommend lmodern. Without lmodern, I think the package is totally unusable. texlive-context is an old package. In

Bug#429314: texlive-context: missing dependency on lmodern

Sanjoy Mahajan [EMAIL PROTECTED] wrote: I know: I maintain Ubuntu edgy backports of the Debian unstable/Ubuntu gutsy packages for texlive 2007, including 'context'. So, why are you reporting a bug against texlive-context, since you know it is deprecated? apt-get is not a tool for newbies. If

Bug#429314: texlive-context: missing dependency on lmodern

Frank Küster [EMAIL PROTECTED] wrote: So, why are you reporting a bug against texlive-context, since you know it is deprecated? Because context doesn't have the bug, but texlive-context has it. And I think it should be even serious. Okay, but texlive-context is dead, so this bug is nothing

Bug#426169: texlive-games: Compilation problems with psgo

Hi, Frank Küster [EMAIL PROTECTED] wrote: minimum.sty and its sister, tableau.sty, is completely in french. Could one of you guys try to find a name or contact address of the author in the file? At a first glance, I didn't find one. There is none. And while you're at it, could you please

Bug#427562: forkbomb: Workaround and request for comment on documentation

Frank Küster [EMAIL PROTECTED] wrote: Comments? Nice explanation, thank you. -- Florent

Bug#428158: Dependency on texlive is not fine-grained enough

Package: maxima-emacs Version: 5.10.0-6 Severity: normal Hi, maxima-emacs depends on tetex-extra | texlive, and this is wrong. texlive is a meta package that depends on a *lot* of packages (all -lang packages), which are obviously not needed for maxima-emacs. You should find the exact texlive

  1   2   3   4   >