Bug#1051301: Updated to 0.9.6. meanwhile
Upstream has just released v0.9.6 which fixes a hang I encountered: https://github.com/uoaerg/wavemon/issues/120 And 0.9.5 problems with non-black backgrounds: https://github.com/uoaerg/wavemon/pull/119 Please update. Thanks! signature.asc Description: PGP signature
Bug#1061403: python3-pykwalify: Missing dependencies to docopt and dateutil
Package: python3-pykwalify
Version: 1.8.0-2
Severity: important
Dear Maintainer,
after upgrading to latest bookworm (but happened also with trixie),
running pykwalify failed with:
File "/usr/bin/pykwalify", line 33, in
sys.exit(load_entry_point('pykwalify==1.8.0', 'console_scripts',
'pykwalify')())
File "/usr/bin/pykwalify", line 25, in importlib_load_entry_point
return next(matches).load()
File "/usr/lib/python3.11/importlib/metadata/__init__.py", line 202, in load
module = import_module(match.group('module'))
File "/usr/lib/python3.11/importlib/__init__.py", line 126, in import_module
return _bootstrap._gcd_import(name[level:], package, level)
File "", line 1206, in _gcd_import
File "", line 1178, in _find_and_load
File "", line 1149, in _find_and_load_unlocked
File "", line 690, in _load_unlocked
File "", line 940, in exec_module
File "", line 241, in _call_with_frames_removed
File "/usr/lib/python3/dist-packages/pykwalify/cli.py", line 11, in
from docopt import docopt
ModuleNotFoundError: No module named 'docopt'
After manually installing python3-docopt, the same happened for module
'dateutil'. With both modules installed, everything works fine again.
Upstream explicitly mentions these packages as "required
dependencies"[1]. Yet, I don't see the dependencies mentioned in the
Debian package. I haven't researched why it worked before the update,
but I think the dependencies should be added in any case.
Thank you for your work,
Wolfram
[1] https://pykwalify.readthedocs.io/en/unstable/
-- System Information:
Debian Release: trixie/sid
APT prefers testing
APT policy: (500, 'testing')
Architecture: amd64 (x86_64)
Kernel: Linux 6.5.0-5-amd64 (SMP w/4 CPU threads; PREEMPT)
Locale: LANG=en_GB.UTF-8, LC_CTYPE=en_GB.UTF-8 (charmap=UTF-8),
LANGUAGE=en_GB:en
Shell: /bin/sh linked to /usr/bin/dash
Init: systemd (via /run/systemd/system)
Versions of packages python3-pykwalify depends on:
ii python3 3.11.4-5+b1
Versions of packages python3-pykwalify recommends:
ii python3-ruamel.yaml 0.17.21-1
python3-pykwalify suggests no packages.
-- no debconf information
Bug#1037955: egctl: New version 0.3 available
Package: egctl Version: 1:0.1-1.1 Severity: wishlist Dear Maintainer, upstream has now version 0.3 available. It adds support for the WLAN variant of the device which is the mainly available one these days. Also, the README now mentions how to overload PREFIX, so the Debian patch could be dropped, I assume. Thanks and happy hacking, Wolfram -- System Information: Debian Release: bookworm/sid APT prefers testing-security APT policy: (500, 'testing-security'), (500, 'testing') Architecture: amd64 (x86_64) Kernel: Linux 5.18.0-2-amd64 (SMP w/4 CPU threads; PREEMPT) Locale: LANG=en_GB.UTF-8, LC_CTYPE=en_GB.UTF-8 (charmap=UTF-8), LANGUAGE=en_GB:en Shell: /bin/sh linked to /bin/dash Init: systemd (via /run/systemd/system) Versions of packages egctl depends on: ii libc6 2.36-6 egctl recommends no packages. egctl suggests no packages. -- no debconf information
Bug#1035620: picocom: New upstream and new release
Package: picocom Version: 3.1-2+b1 Severity: normal Dear Maintainer, after 5 years of silence, I took over maintainership for picocom, collected bugfixes and pull requests and released a new version. Please find more information here: https://gitlab.com/wsakernel/picocom/-/releases I hope this can be added to Debian as-is. If not, please let me know and we can work it out. Happy hacking, Wolfram -- System Information: Debian Release: bookworm/sid APT prefers testing APT policy: (500, 'testing') Architecture: amd64 (x86_64) Kernel: Linux 5.18.0-2-amd64 (SMP w/4 CPU threads; PREEMPT) Locale: LANG=en_GB.UTF-8, LC_CTYPE=en_GB.UTF-8 (charmap=UTF-8), LANGUAGE=en_GB:en Shell: /bin/sh linked to /bin/dash Init: systemd (via /run/systemd/system) Versions of packages picocom depends on: ii libc6 2.36-6 picocom recommends no packages. picocom suggests no packages. -- no debconf information
Bug#1016715: modem-manager-gui: Assertion when XDG_CURRENT_DESKTOP is not set
Package: modem-manager-gui
Version: 0.0.20
Severity: minor
Tags: patch upstream
Dear Maintainer,
for some reason, my system using i3wm does not have XDG_CURRENT_DESKTOP
set. This leads to a critical assertion when starting modem-manager-gui.
While this is no problem because the program still starts, it is easy
enough to fix, so here is a patch for it. I did not send it to upstream,
because there doesn't seem to be an active upstream anymore.
All the best,
Wolfram
-- System Information:
Debian Release: bookworm/sid
APT prefers testing
APT policy: (500, 'testing')
Architecture: amd64 (x86_64)
Kernel: Linux 5.18.0-2-amd64 (SMP w/4 CPU threads; PREEMPT)
Locale: LANG=en_GB.UTF-8, LC_CTYPE=en_GB.UTF-8 (charmap=UTF-8),
LANGUAGE=en_GB:en
Shell: /bin/sh linked to /bin/dash
Init: systemd (via /run/systemd/system)
Versions of packages modem-manager-gui depends on:
ii libayatana-appindicator3-1 0.5.90-5
ii libc6 2.33-7
ii libcairo2 1.16.0-6
ii libgdbm61.23-1
ii libgdk-pixbuf-2.0-0 2.42.8+dfsg-2
ii libglib2.0-02.70.3-1
ii libgtk-3-0 3.24.34-1
ii libgtkspell3-3-03.0.10-1
ii mobile-broadband-provider-info 20210805-1
ii modemmanager1.18.10-1
ii network-manager 1.38.2-1
ii policykit-1 0.105-31.1+b1
ii ppp 2.4.9-1+1
Versions of packages modem-manager-gui recommends:
ii modem-manager-gui-help 0.0.20-4
pn yelp
Versions of packages modem-manager-gui suggests:
pn evolution-data-server
pn libindicate5 | libmessaging-menu0
ii libnotify4 0.8.1-1
From: Wolfram Sang
Date: Tue, 2 Aug 2022 17:32:53 +0200
Subject: avoid assertion when XDG_CURRENT_DESKTOP is not set
---
src/addressbooks.c | 2 +-
src/main.c | 2 +-
2 files changed, 2 insertions(+), 2 deletions(-)
diff --git a/src/addressbooks.c b/src/addressbooks.c
index ff9c423..fd28285 100644
--- a/src/addressbooks.c
+++ b/src/addressbooks.c
@@ -979,7 +979,7 @@ mmgui_addressbooks_t
mmgui_addressbooks_new(mmgui_event_ext_callback callback, m
addressbooks->gnomecontacts = NULL;
/*GNOME code path*/
- if (g_strrstr(desktop, "GNOME") != NULL) {
+ if (desktop && g_strrstr(desktop, "GNOME") != NULL) {
if (mmgui_libpaths_cache_check_library_version(libcache,
"libebook-1.2", 12, 3, 0)) {
/*Open module*/
addressbooks->ebookmodule =
g_module_open(mmgui_libpaths_cache_get_library_full_path(libcache,
"libebook-1.2"), G_MODULE_BIND_LAZY);
diff --git a/src/main.c b/src/main.c
index 733a190..2e31d13 100644
--- a/src/main.c
+++ b/src/main.c
@@ -2035,7 +2035,7 @@ static void
mmgui_main_tray_icon_build(mmgui_application_t mmguiapp)
desktop = getenv("XDG_CURRENT_DESKTOP");
/*Indicator*/
- if (g_strrstr(desktop, "GNOME") != NULL) {
+ if (desktop && g_strrstr(desktop, "GNOME") != NULL) {
iconfilepath = g_build_filename(RESOURCE_SYMBOLIC_ICONS_DIR,
"modem-manager-gui-symbolic.svg", NULL);
} else {
iconfilepath = g_build_filename(RESOURCE_PNG_ICONS_DIR,
"modem-manager-gui.png", NULL);
Bug#1004258: improvements to the bugfix
Hi,
first of all, thank you for fixing this bug. I was also bitten by it
and I am happy that it was fixed already by a patch.
I'd like to suggest some improvements, though. First, I think the new
variable introduced should be 'gint' rather than 'int' to stay
consistent. Also, there were some white space issues with one of the new
lines. I add an updated patch here to this message. It is also a tad
shorter because of the ternary operator. Its usage is often a matter of
taste but I think it fits nicely here.
Thanks and looking forward to comments,
Wolfram
From: Patrizio Tufarolo
Date: Wed, 25 May 2022 08:11:36 +0200
Subject: fix_segfault_on_DNS_entries
Slightly edited by Wolfram Sang
---
src/modules/nm09.c | 5 +++--
1 file changed, 3 insertions(+), 2 deletions(-)
diff --git a/src/modules/nm09.c b/src/modules/nm09.c
index 2b3098b..02d0e20 100644
--- a/src/modules/nm09.c
+++ b/src/modules/nm09.c
@@ -529,7 +529,7 @@ static mmguiconn_t mmgui_module_connection_get_params(mmguicore_t mmguicore, con
GVariant *connconsec, *connipv4sec, *conntechsec;
GVariant *conndnsvar;
gchar *conntypestr, *connparamstr;
- gint i, addrint;
+ gint i, addrint, n_dns_entries;
GVariant *addrvar;
gchar *techstr;
mmguiconn_t connection;
@@ -630,7 +630,8 @@ static mmguiconn_t mmgui_module_connection_get_params(mmguicore_t mmguicore, con
if (connipv4sec != NULL) {
/*DNS*/
conndnsvar = g_variant_lookup_value(connipv4sec, "dns", G_VARIANT_TYPE_ARRAY);
- for (i = 0; i < g_variant_n_children(conndnsvar); i++) {
+ n_dns_entries = conndnsvar ? g_variant_n_children(conndnsvar) : 0;
+ for (i = 0; i < n_dns_entries; i++) {
addrvar = g_variant_get_child_value(conndnsvar, i);
addrint = ntohl(g_variant_get_uint32(addrvar));
if (connection->dns1 == NULL) {
signature.asc
Description: PGP signature
Bug#993350: [sane-devel] Epson Perfection1640 and the epson2 backend: summary
Hi, > 1) This started out with focus problems. >I appear to have confirmed that the 1640 accepts, but ignores, focus >commands, so the current version of the backend >(commit 3b47d1d26a73054b7138759fa7af57ed6c8e8e35 (HEAD -> master, > origin/master, origin/HEAD) >with dev->focusSupport = SANE_FALSE is correct. Thanks for confirming! > 2) The > --film-type Positive Film|Negative Film|Positive Slide|Negative Slide >includes the Slide options which I suspect are not available on >the 1640SU. They result in something like invalid parameter messages. Confirmed. I can reproduce this with my 1640SU. I don't really know where the "Slide" come from or what they actually do. I need to dig in a little further. In about two weeks, I can also double check if a 12000XL does support the "Slide" options. > 3) There is a failure to transfer larger scans: perhaps a counter >overflowing. So a significant bug. I still need to reproduce this one. But I'd think this is easy to reproduce. > 4) Using xsane, and [cancel]ing during a scan fails. It is usually >necessary to restart the 1640. I have only mentioned this bug in >passing in previous messages. I had this, too, on my 1640SU. I seem to recall that it worked fine on the 12000XL. I'll cross-check this as well. > I hope this is helpful in following the earlier messages, especially > the first few when things were not so clear. Thanks again for your investigations! Much appreciated! Kind regards, Wolfram signature.asc Description: PGP signature
Bug#993350: Epson Perfection1640: Slide scan fails
> I have had a very quick skim of epson2.c and a couple of other files. > I can see a DBG macro which seems to be defined in sanei_debug.h > but I am not sure how to invoke it just yet. SANE_DEBUG_EPSON2= xsane Sorry, I am stuffed with work currently. I'll try to check your other mails until the weekend. signature.asc Description: PGP signature
Bug#993350: [sane-devel] Epson Perfection1640: Operation not supported
> It is better in that it no longer crashes, but is still a > regression: I suspect that I can no longer scan films. > > So it seems that commit 580c278dcafe4159213406b4307ee8598fe08fe7 > was too simplistic? It is true that the option is not a boolean anymore but an integer. But still, if you selet the TPU the old default value for 2.5mm above glass (89) should be automatically selected. Without TPU, it should use the default of on glass (64). I tested this on an Epson 12000XL and Perfection1640. Please check if that works on your system as well. signature.asc Description: PGP signature
Bug#993350: [sane-devel] Epson Perfection1640: Operation not supported
> I tried this but I still have xsane Version: 0.999-12 so there was no > change. I couldn't find a newer version of xsane, even in Ubuntu. > Indeed in the Ubuntu pool that I checked, the xsane directory was empty. You need a newer version of libsane than debian testing. Probably packages "libsane-common" and friends. The xsane version can stay the same. But a quick look tells me that Ubuntu repos won't be useful for you because they also don't have the patch you need. Maybe your best bet is to push Debian maintainers to include the patch I mentioned. They should have it anyhow. Fedora already includes it. signature.asc Description: PGP signature
Bug#980311: Patch is upstream
The aforementioned patch is now upstream as commit: 63942f7a7473496d1160f02f5c1da3620525690d # gt68xx: fix use-after-free and two mem leaks Thanks for the report! signature.asc Description: PGP signature
Bug#980311: Fix available!
Okay, I found a scanner here which needs the same driver and the fix in
this merge request fixes it for me:
https://gitlab.com/sane-project/backends/-/merge_requests/634
The attached patch should apply on 1.0.32 at least, probably earlier
versions, too. It should be upstream with 1.0.33 then.
Hope it helps!
From 63942f7a7473496d1160f02f5c1da3620525690d Mon Sep 17 00:00:00 2001
From: Wolfram Sang
Date: Thu, 10 Jun 2021 11:32:04 +0200
Subject: [PATCH] gt68xx: fix use-after-free and two mem leaks
The config file argument needs to be freed when a device is not set.
That was missed for two occasions. The other occasion was freeing it
unconditionally leading to a use-after-free for the regular use case.
Fixes: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=980311
This is the least intrusive fix. The code really wants to be refactored.
Tested with a Mustek 1200 UB Plus.
---
backend/gt68xx.c | 22 +++---
1 file changed, 15 insertions(+), 7 deletions(-)
diff --git a/backend/gt68xx.c b/backend/gt68xx.c
index 6e43765d3..08919287a 100644
--- a/backend/gt68xx.c
+++ b/backend/gt68xx.c
@@ -1174,8 +1174,11 @@ static SANE_Status probe_gt68xx_devices(void)
new_dev[i]->model->firmware_name);
}
if (i == 0)
-DBG (5, "sane_init: firmware %s can't be loaded, set device "
- "first\n", word);
+{
+ DBG (5, "sane_init: firmware %s can't be loaded, set device "
+ "first\n", word);
+ free (word);
+}
}
else
{
@@ -1198,8 +1201,11 @@ static SANE_Status probe_gt68xx_devices(void)
new_dev[i]->model->name, new_dev[i]->model->vendor);
}
if (i == 0)
-DBG (5, "sane_init: can't set vendor name %s, set device "
- "first\n", word);
+{
+ DBG (5, "sane_init: can't set vendor name %s, set device "
+ "first\n", word);
+ free (word);
+}
}
else
{
@@ -1221,9 +1227,11 @@ static SANE_Status probe_gt68xx_devices(void)
new_dev[i]->model->name, new_dev[i]->model->model);
}
if (i == 0)
-DBG (5, "sane_init: can't set model name %s, set device "
- "first\n", word);
- free (word);
+{
+ DBG (5, "sane_init: can't set model name %s, set device "
+ "first\n", word);
+ free (word);
+}
}
else
{
--
2.30.2
signature.asc
Description: PGP signature
Bug#980311: no need for more data
I found the culprit (hiding between the confusing indentation). No need to send more data. I will work now on a fix. signature.asc Description: PGP signature
Bug#980311: some more debug output needed
Hi, > > SANE_DEBUG_GT68XX=5 scanimage -L Could you kindly also provide this output? SANE_DEBUG_GT68XX=5 SANE_DEBUG_DLL=3 scanimage -L Let's hope this will bring something new... Kind regards, Wolfram signature.asc Description: PGP signature
Bug#741663: linux-image-3.13-1-powerpc-smp: therm_windtunnel does not load correctly
> > Yes and no. I am quite optimistic the bug was fixed with a patch which > > is included upstream since 4.19-rc1. It still needs confirmation, > > though, i.e. testing. > > The PowerMac G5 users on this list are kindly asked to confirm the bug has > been fixed. Until then, I'll reopen it. Makes perfect sense to me. > > Back then, that meant compiling your own kernel. These days, you can > > just use any Debian-provided kernel from 4.19 onwards. > > I'm not sure how this is relevant to the question whether the bug was fixed > or not in the Debian kernel package. Not relevant. It was just to say that the tester's job has become much easier meanwhile. signature.asc Description: PGP signature
Bug#741663: linux-image-3.13-1-powerpc-smp: therm_windtunnel does not load correctly
> Any reporting back here? For the record, no need to build custom kernels anymore. Any Debian supplied kernel 4.19 or later will do for testing. signature.asc Description: PGP signature
Bug#980311: Odd behaviour with sane_exit
Hi, > sorry, I've been away for a while. No worries, thanks for the log file. > [07:57:42.570625] [gt68xx] sane_get_devices: exit > [07:57:44.957116] [gt68xx] sane_exit: start > [07:57:44.957176] [gt68xx] sane_exit: exit > device `gt68xx:libusb:005:003' is a Plustek PI&�U flatbed scanner This is odd. sane_exit() frees the acquired devices. It should come after the "... is a ..." printout. This is how it looks with the epson2 driver: [09:50:47.330296] [epson2] sane_epson2_get_devices - results: [09:50:47.330334] [epson2] 0 (3): Perfection1640 device `epson2:libusb:001:007' is a Epson Perfection1640 flatbed scanner Calling sane_exit [09:50:47.373343] [epson2] sane_epson2_exit Here you see that sane_exit() is called after the printout. Sadly, I don't see why this happens yet. The codepath in scanimage should be the same independently of the backend. I'll need to think about it some more. > Yes, I think so. Just send them along, I'd be happy to test them. Cool, this is great (once we have a patch). Kind regards, Wolfram signature.asc Description: PGP signature
Bug#980311: ping
Hi, can you run this command please and provide the output? SANE_DEBUG_GT68XX=5 scanimage -L And can you test patches? Regards, Wolfram signature.asc Description: PGP signature
Bug#980311: debug output
Hi, can you run this command please and provide the output? SANE_DEBUG_GT68XX=5 scanimage -L And can you test patches? Regards, Wolfram signature.asc Description: PGP signature
Bug#950329: can be closed
Upstream provided version 0.9 with Python3 + Qt5 support. Already available in Debian testing. Can be closed. signature.asc Description: PGP signature
Bug#971389: seascope: Dependency to 'python3-pyqt5.qtsvg' missing, does not start
Package: seascope Version: 0.9+8a669e0e-2 Severity: grave Justification: renders package unusable Dear Maintainer, after upgrading to bullseye, starting seascope failed for me: No module named 'PyQt5.QtSvg' Error: failed to import supporting packages. Error: program aborted. After installing python3-pyqt5.qtsvg manually, the program worked fine. Kind regards, Wolfram -- System Information: Debian Release: bullseye/sid APT prefers testing APT policy: (500, 'testing') Architecture: amd64 (x86_64) Kernel: Linux 5.8.0-1-amd64 (SMP w/8 CPU threads) Locale: LANG=en_GB.UTF-8, LC_CTYPE=en_GB.UTF-8 (charmap=UTF-8), LANGUAGE=en_GB:en Shell: /bin/sh linked to /bin/dash Init: systemd (via /run/systemd/system) Versions of packages seascope depends on: ii python3 3.8.2-3 ii python3-pyqt5 5.15.0+dfsg-1+b1 ii python3-pyqt5.qsci 2.11.2+dfsg-7 Versions of packages seascope recommends: ii cscope 15.9-1 ii exuberant-ctags 1:5.9~svn20110310-13 ii id-utils 4.6.28-20200521ss15dab+b1 seascope suggests no packages. -- no debconf information
Bug#947942: Can't reproduce the issues with 2.35.2-2
Using 2.35.2-2, I can use bash-completion when unmounting a USB drive which was mounted to a directory containing spaces. The 'gawk' issues was properly fixed, too, check #933934 Maybe someone wants to verify, yet I think this can be closed. signature.asc Description: PGP signature
Bug#892261: fixed upstream
Fixed upstream with commit aef913e ("mmc-utils: use MMC_IOC_MULTI_CMD
for RPMB access") since December 2018.
signature.asc
Description: PGP signature
Bug#791707: Fixed upstream
The issue has been fixed upstream since April 2016 with commit 2e31d1c3a
("chrt: validate priority before trying to use it") which also mentions
this bugreport.
signature.asc
Description: PGP signature
Bug#947942: upstream has a patch for the gawk issue now
Hi, I also hit the 'gawk' problem after upgrading to bullseye and my simple proposal: https://www.spinics.net/lists/util-linux-ng/msg16081.html was commited upstream: https://git.kernel.org/pub/scm/utils/util-linux/util-linux.git/commit/?id=76f969fe6ff149c7748894dcf881218f84873d67 Kind regards, Wolfram signature.asc Description: PGP signature
Bug#741663: linux-image-3.13-1-powerpc-smp: therm_windtunnel does not load correctly
On Sat, Sep 08, 2018 at 02:48:01PM -0700, Rick Thomas wrote: > Thanks! Yes, I’ll give it a try. Note: You can either build the v4.19-rc1 tarball which has the patch already included. Or you can take your Debian kernel and add this patch: http://patchwork.ozlabs.org/patch/960488/ You can download it as mbox there which gives you a file to apply. signature.asc Description: PGP signature
Bug#853122: [Regression] Changes to i2c-piix4.c initialisation prevent loading of sp5100_tco watchdog driver on AMD SB800 chipset
> Unfortunately, commit 2fee61d22e (i2c: piix4: Add support for > multiplexed main adapter in SB800) [1] caused a regression. Tim > reported that to the Linux Kernel Bugtracker as bug #170741 last > September [2], but it looks like the affected subsystems don’t use it. Jean Delvare pointed out this issue amongst others[1] last year already. Let me quote: === 5* The I/O ports used for SMBus configuration and port switching are also needed by a watchdog driver, sp5100_tco. Both drivers request the region, so the first one wins, and the other driver can't be loaded. sp5100_tco was there first, so the changes done to the i2c-piix4 driver recently will cause a regression for some users by preventing them from using the sp5100_tco and i2c-piix4 drivers at the same time. In the long run I guess we will need a helper module to handle this shared resource. Unless IORESOURCE_MUXED can be used for that. Either way, that's more work than I can put into this before kernel v4.5 is released. For the time being, I think we should simply make it non-fatal if the I/O ports can't be requested, and continue without multiplexing (as before.) === Seems nobody had the resources, so far. I don't have the HW and not much experience with non-embedded platforms. I wonder, though, if we really need to convert the drivers to MFD ones, or if we could use the simpler MFD_SYSCON mechanism which helps in exactly such cases for embedded platforms. But I am really lacking details here and am afraid this is probably all the input I can give currently. Regards, Wolfram [1] http://www.spinics.net/lists/linux-i2c/msg23437.html signature.asc Description: PGP signature
Bug#829417: dosemu: *** stack smashing detected ***: /usr/bin/xdosemu terminated
Try using this in your config: $_cpu_emu = "full" signature.asc Description: PGP signature
Bug#838755: texlive-latex-extra: package datetime2 can not be used without tracklang.sty from texlive-generic-extra
Package: texlive-latex-extra Version: 2016.20160819-1 Severity: normal Dear Maintainer, datetime2 needs tracklang.sty. Trying to build one of the examples: pdflatex /usr/share/doc/texlive-doc/latex/datetime2/samples/datetime2-sample-filedate.tex gives: This is pdfTeX, Version 3.14159265-2.6-1.40.17 (TeX Live 2016/Debian) (preloaded format=pdflatex) restricted \write18 enabled. entering extended mode (./datetime2-sample-filedate.tex LaTeX2e <2016/03/31> patch level 3 Babel <3.9r> and hyphenation patterns for 8 language(s) loaded. (/usr/share/texlive/texmf-dist/tex/latex/base/article.cls Document Class: article 2014/09/29 v1.4h Standard LaTeX document class (/usr/share/texlive/texmf-dist/tex/latex/base/size10.clo)) (/usr/share/texlive/texmf-dist/tex/latex/datetime2/datetime2.sty ! LaTeX Error: File `tracklang.sty' not found. Installing texlive-generic-extra fixes the problem. I understand that latex dependencies are tricky, still I thought I'd let you know. Thanks, Wolfram -- System Information: Debian Release: stretch/sid APT prefers testing APT policy: (500, 'testing') Architecture: amd64 (x86_64) Foreign Architectures: i386 Versions of packages texlive-latex-extra depends on: ii preview-latex-style11.87-3+deb8u1 ii tex-common 6.04 ii texlive-base 2016.20160819-2 ii texlive-binaries 2016.20160513.41080-6 ii texlive-latex-recommended 2016.20160819-2 ii texlive-pictures 2016.20160819-2 Versions of packages texlive-latex-extra recommends: ii texlive-fonts-recommended 2016.20160819-2 ii texlive-latex-extra-doc2016.20160819-1 Versions of packages texlive-latex-extra suggests: ii libfile-which-perl 1.19-1 pn libspreadsheet-parseexcel-perl ii python-pygments 2.1+dfsg-1 Versions of packages tex-common depends on: ii dpkg 1.18.4 ii ucf 3.0035 Versions of packages tex-common suggests: ii debhelper 9.20160115 Versions of packages texlive-latex-extra is related to: ii tex-common6.04 ii texlive-binaries 2016.20160513.41080-6 -- debconf information: tex-common/check_texmf_wrong: tex-common/check_texmf_missing: signature.asc Description: PGP signature
Bug#714345: Airport gone
> Could you please double check the following output from modinfo and > confirm this is the same issue as Debian #714345 You already found out, yes it is. Good: > > alias: of:NradioT*C* Bad; > > alias: of:NradioT*CC* > > alias: of:NradioT*C ^ Note the 'C' without the asterisk. signature.asc Description: PGP signature
Bug#714345: No sound on PowerPC with Jessie upgrade
On Thu, Jun 02, 2016 at 03:13:18PM +0200, Mathieu Malaterre wrote: > On Thu, Jun 2, 2016 at 3:09 PM, Wolfram Sang <w...@the-dreams.de> wrote: > > > >> So if this is not working for me (Mac Mini G4/PPC), I leave it open > >> for now. This used to work out of the box on wheezy, without > >> explicitely setting snd-aoa-i2sbus in `/etc/modules`. > > > > But with it, it is working? > > > > Sure ! Works beautifully here. I am leaving the bug open, since one > need to manually add `snd-aoa-i2sbus` module. OK. As debugged in private conversation with Mathieu, this patch is needed as well: http://patchwork.ozlabs.org/patch/631060/ Technically, this should be a seperate bug, because it is a totally different issue. However, if you have other module autoloading problems on PowerMacs, give this patch a try. signature.asc Description: PGP signature
Bug#741663: linux-image-3.13-1-powerpc-smp: therm_windtunnel does not load correctly
On Tue, Apr 12, 2016 at 12:08:03PM +0200, Mathieu Malaterre wrote: > Dear all, > > I am looking for testers for the following patch: > > https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=741663#20 > > Wolfram (CC here) is looking for feedback from users for this patch. For completeness, it should be one of those machines: https://en.wikipedia.org/wiki/Power_Mac_G4#Wind_Tunnel signature.asc Description: PGP signature
Bug#714345: No sound on PowerPC with Jessie upgrade
> So if this is not working for me (Mac Mini G4/PPC), I leave it open > for now. This used to work out of the box on wheezy, without > explicitely setting snd-aoa-i2sbus in `/etc/modules`. But with it, it is working? signature.asc Description: PGP signature
Bug#714345: No sound on PowerPC with Jessie upgrade
> Does not seems to be present in 4.5.5-1 which is the current (sid) > debian kernel. $ git show 28760c195e22856aedbacad5eb7b46ac1d76bb90 Author: Wolfram Sang <w...@the-dreams.de> Date: Sat May 23 18:15:11 2015 +0200 ALSA: ppc: keywest: check if DEQ was already instantiated Due to changes in i2c-powermac, for some Macs the DEQ is instantiated now in i2c-powermac while some need the instantiation here in the keywest sound driver. The proper fix is to convert this driver to AOA. Until then support both ways of instantiation. Before this patch, some Macs lost sound because the sound driver failed when instantiating the DEQ for the second time. Signed-off-by: Wolfram Sang <w...@the-dreams.de> Tested-by: Dan DeVoto <dand1...@yahoo.com> Signed-off-by: Takashi Iwai <ti...@suse.de> $ git describe 28760c195e22856aedbacad5eb7b46ac1d76bb90 v4.1-rc3-151-g28760c195e2285 So, this commit IS upstream since v4.2. If you don't have sound, this is probably due to another issue. Wolfram signature.asc Description: PGP signature
Bug#714345: No sound on PowerPC with Jessie upgrade
On Tue, Apr 12, 2016 at 11:05:00AM +0200, Mathieu Malaterre wrote: > > https://lists.ozlabs.org/pipermail/linuxppc-dev/2015-May/129212.html > > Has it been merged yet ? Yes, is is upstream since 4.2 and was promised to go back into stable trees. signature.asc Description: PGP signature
Bug#714345: This is the proper patch
The previous patch turned out to be broken, this patch will soon get tested in linux-next instead: https://lists.ozlabs.org/pipermail/linuxppc-dev/2015-May/129212.html signature.asc Description: Digital signature
Bug#741663: Follow up patch
Hi Bryan,
I hope you are still around and still interested in this bug. I am the
Linux I2C maintainer and I am currently trying to get rid of the
attach_adapter method which produces this ugly warning you already
mentioned. Your patch may work for you but I am afraid it is very likely
to cause regressions on other Macintosh computers with different device
trees. Can you try the following patch which is closer to the original
instantiation procedure? It should at least get rid of the warning. The
driver should still be loaded on boot. I am unsure if it fixes the
reload problem, you would need to try and report back. I'd be willing to
help further if the problem still remains.
Thanks,
Wolfram
From: Wolfram Sang w...@the-dreams.de
Subject: [PATCH] macintosh: therm_windtunnel: drop using attach adapter
As we now have deferred probing, we can use a custom mechanism and
finally get rid of the legacy interface from the i2c core.
Signed-off-by: Wolfram Sang w...@the-dreams.de
---
drivers/macintosh/therm_windtunnel.c | 25 +++--
1 file changed, 23 insertions(+), 2 deletions(-)
diff --git a/drivers/macintosh/therm_windtunnel.c
b/drivers/macintosh/therm_windtunnel.c
index 835ca8be4c1632..57909a3ce67bf2 100644
--- a/drivers/macintosh/therm_windtunnel.c
+++ b/drivers/macintosh/therm_windtunnel.c
@@ -422,7 +422,6 @@ static struct i2c_driver g4fan_driver = {
.driver = {
.name = therm_windtunnel,
},
- .attach_adapter = do_attach,
.probe = do_probe,
.remove = do_remove,
.id_table = therm_windtunnel_id,
@@ -435,7 +434,29 @@ static struct i2c_driver g4fan_driver = {
static int therm_of_probe(struct platform_device *dev)
{
- return i2c_add_driver( g4fan_driver );
+ struct i2c_adapter *adap;
+ int ret, i = 0;
+
+ adap = i2c_get_adapter(0);
+ if (!adap)
+ return -EPROBE_DEFER;
+
+ ret = i2c_add_driver(g4fan_driver);
+ if (ret) {
+ i2c_put_adapter(adap);
+ return ret;
+ }
+
+ /* We assume Macs have consecutive I2C bus numbers starting at 0 */
+ while (adap) {
+ do_attach(adap);
+ if (x.running)
+ return 0;
+ i2c_put_adapter(adap);
+ adap = i2c_get_adapter(++i);
+ }
+
+ return -ENODEV;
}
static int
signature.asc
Description: Digital signature
Bug#667014: I hit the same problem
I'd assume that this is the culprit: http://bugs.irssi.org/index.php?do=detailstask_id=841 Haven't tried the patch, though... -- Pengutronix e.K. | Wolfram Sang| Industrial Linux Solutions | http://www.pengutronix.de/ | signature.asc Description: Digital signature
Bug#646467: supposed fix
tags 646467 patch thanks -- Pengutronix e.K. | Wolfram Sang| Industrial Linux Solutions | http://www.pengutronix.de/ | From: Wolfram Sang w.s...@pengutronix.de Subject: fix '-Werror=format-security' flaw We won't have format specifiers, so simply use fputs. This patch applies to the current debian version and upstream master as well (with offset). Signed-off-by: Wolfram Sang w.s...@pengutronix.de --- debug.c |2 +- 1 file changed, 1 insertion(+), 1 deletion(-) Index: src/debug.c === --- a/src/debug.c +++ b/src/debug.c @@ -28,7 +28,7 @@ void print_message_to_stderr(const char va_start(va, fmt); vsnprintf(msg, PATH_MAX, fmt, va); va_end(va); - fprintf(stderr, msg); + fputs(msg, stderr); } #ifdef DEBUG signature.asc Description: Digital signature
Bug#643363: fix format not a string literal and no format arguments issue
Debian has a release-critical bug filed against your project [1], because
'-Werror=format-security' [2] is used there to harden included software. The
following manually created patch is a standard way of resolving the bug, but
since I don't use your software I could not actually test it. It would be kind
of you if you could evaluate if this patch is applicable.
[1] http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=643363
[2]
http://wiki.debian.org/Hardening#DEB_BUILD_HARDENING_FORMAT_.28gcc.2BAC8-g.2B-.2B-_-Wformat_-Wformat-security_-Werror.3Dformat-security.29
Signed-off-by: Wolfram Sang w.s...@pengutronix.de
--- CbcOrClpParam.cpp.orig 2011-12-03 17:15:35.0 +0100
+++ CbcOrClpParam.cpp 2011-12-03 17:16:39.0 +0100
@@ -1079,7 +1079,7 @@
}
#else
if (CbcOrClpReadCommand == stdin) {
- fprintf(stdout, coin_prompt);
+ fputs(coin_prompt, stdout);
fflush(stdout);
}
where = fgets(line, 1000, CbcOrClpReadCommand);
--
Pengutronix e.K. | Wolfram Sang|
Industrial Linux Solutions | http://www.pengutronix.de/ |
signature.asc
Description: Digital signature
Bug#612466: snmp-mibs-downloader: Make the user aware of a potential change in /etc/snmp/snmp.conf
Package: snmp-mibs-downloader Version: 1.1 Severity: wishlist just stumbled over this. snmp.conf (from libsnmp) says: --- # As the snmp packages come without MIB files due to license reasons, loading # of MIBs is disabled by default. If you added the MIBs you can reenable # loaging them by commenting out the following line. mibs : --- It took me a bit of time to find out that I need to do this. My wish here would be that the user is informed about the need of this change (because we _are_ downloading the MIBs here). Maybe using a debconf-infobox when this packet is installed and the above config-file is present? Maybe it could even ask if it can perform this change immediately? -- System Information: Debian Release: 6.0 APT prefers stable APT policy: (990, 'stable') Architecture: i386 (i686) Kernel: Linux 2.6.37-rc3+ (SMP w/2 CPU cores) Locale: LANG=en_GB.UTF-8, LC_CTYPE=en_GB.UTF-8 (charmap=UTF-8) Shell: /bin/sh linked to /bin/dash Versions of packages snmp-mibs-downloader depends on: ii patch 2.6-2 Apply a diff file to an original ii smistrip 0.4.8+dfsg2-3 extract MIB from text files like R ii wget 1.12-2.1 retrieves files from the web snmp-mibs-downloader recommends no packages. Versions of packages snmp-mibs-downloader suggests: ii unzip 6.0-4 De-archiver for .zip files -- debconf-show failed -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#593869: Can't reproduce
I can't reproduce this on my up-to-date squeeze system (with custom 2.6.36-rc4 kernel, i686). I also tried uninstalling gstreamer-alsa, still works. I do see all the warnings before the segmentation fault, but not the fault itself. What soundcard do you have (Intel 82801DB/DBL/DBM here)? Are there sound issues with other programs? Cheers, Wolfram -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#538822: Bitten, too
I have also been bitten by this, although I don't know if my local modifications will classify it as a bug: I switched very early to dash by simply changing the /bin/sh-symlink by hand (it ought to be a test). I totally forgot that I did it this way until the upgrade to squeeze yesterday. The symptoms were the same as in message #5. The solution was given in message #134 (thanks a lot!). Removing the divert and restoring the original /bin/sh-symlink solved the problem for me. I could continue upgrading, although /bin/sh was pointing to bash afterwards. Regards! -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#565126: Bitten, too
Hi, I have been bitten by this bug, too, while upgrading from lenny to squeeze. As udev now throws warnings on deprecated SYSFS usage, this led to a zillion warnings after rebooting. Manually deleting the file in /etc helped (and is possibly the cause for the below error under Configuration files). Happened also with the 2.6.30-kernel; besides this according to dpkg.log that was a normal upgrade: dpkg.log:2010-06-08 04:43:27 upgrade xserver-xorg-input-wacom 0.7.9.3-2 0.10.5+20100416-1 Regards, Wolfram -- System Information: Debian Release: squeeze/sid APT prefers testing APT policy: (990, 'testing') Architecture: i386 (i686) Kernel: Linux 2.6.32-trunk-686 (SMP w/2 CPU cores) Locale: LANG=en_GB.UTF-8, LC_CTYPE=en_GB.UTF-8 (charmap=UTF-8) Shell: /bin/sh linked to /bin/dash Versions of packages xserver-xorg-input-wacom depends on: ii libc6 2.10.2-9 Embedded GNU C Library: Shared lib ii libx11-6 2:1.3.3-3 X11 client-side library ii libxi62:1.3-4X11 Input extension library ii xserver-xorg-core 2:1.7.7-1 Xorg X server - core server xserver-xorg-input-wacom recommends no packages. Versions of packages xserver-xorg-input-wacom suggests: pn xinputnone (no description available) -- Configuration Files: /etc/udev/rules.d/z60_xserver-xorg-input-wacom.rules [Errno 2] No such file or directory: u'/etc/udev/rules.d/z60_xserver-xorg-input-wacom.rules' -- debconf-show failed -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#562937: liblockfile1: make ar overwritable (for cross-builds)
Package: liblockfile1 Version: 1.08-3 Severity: normal Tags: patch [PATCH] [Makefile] make ar overwritable (for cross-builds) Signed-off-by: Marc Kleine-Budde m...@pengutronix.de Signed-off-by: Wolfram Sang w.s...@pengutronix.de --- Makefile.in |2 +- 1 files changed, 1 insertions(+), 1 deletions(-) diff --git a/Makefile.in b/Makefile.in index 7ae5406..84fc5b7 100644 --- a/Makefile.in +++ b/Makefile.in @@ -29,7 +30,7 @@ shared: liblockfile.so dotlockfile nfslib:nfslock.so.$(VER) liblockfile.a: lockfile.o - ar rv liblockfile.a lockfile.o + $(AR) rv liblockfile.a lockfile.o liblockfile.so: liblockfile.a $(CC) -fPIC -shared -Wl,-soname,liblockfile.so.1 \ -- System Information: Debian Release: lenny/sid APT prefers stable APT policy: (700, 'stable'), (650, 'testing') Architecture: i386 (i686) Kernel: Linux 2.6.30-2-686 (SMP w/2 CPU cores) Locale: LANG=en_GB.UTF-8, LC_CTYPE=en_GB.UTF-8 (charmap=UTF-8) Shell: /bin/sh linked to /bin/dash Versions of packages liblockfile1 depends on: ii libc6 2.7-13 GNU C Library: Shared libraries liblockfile1 recommends no packages. liblockfile1 suggests no packages. -- no debconf information -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#382425: [PATCH] discover: use sysfs for pcmcia
Hi,
trying to get rid of the old pcmcia-ioctl-interface in the kernel, I modified
discover to use sysfs for that. Please find the patch attached. It modifies
configure.ac, so autoreconf has to be used to generate the new configure.
Is this interesting? I hope so, it seems discover is the last more prominent
user of that old interface...
Regards,
Wolfram
---
Finally get rid of these messages that discover uses the outdated pcmcia-ioctl
interface. For that, the sysfs-code was copied from PCI and adapted. That means
the ioctl-method is still there as a fallback.
Signed-off-by: Wolfram Sang w.s...@pengutronix.de
---
configure.ac |3 +
sysdeps/linux/pcmcia.c | 147 -
2 files changed, 148 insertions(+), 2 deletions(-)
Index: configure.ac
===
--- configure.ac.orig
+++ configure.ac
@@ -218,6 +218,7 @@ linux*)
PATH_PROC_PCI=/proc/bus/pci/devices
PATH_PROC_PCI_DIR=`dirname $PATH_PROC_PCI`
PATH_SYS_PCI=/sys/bus/pci/devices
+PATH_SYS_PCMCIA=/sys/bus/pcmcia/devices
PATH_PROC_SCSI=/proc/scsi/scsi
PATH_PROC_USB=/proc/bus/usb/devices
AC_DEFINE_UNQUOTED(PATH_PROC_IDE, $PATH_PROC_IDE,
@@ -228,6 +229,8 @@ linux*)
[Define path to /proc/bus/pci.])
AC_DEFINE_UNQUOTED(PATH_SYS_PCI, $PATH_SYS_PCI,
[Define path to /sys/bus/pci/devices.])
+AC_DEFINE_UNQUOTED(PATH_SYS_PCMCIA, $PATH_SYS_PCMCIA,
+ [Define path to /sys/bus/pcmcia/devices.])
AC_DEFINE_UNQUOTED(PATH_PROC_SCSI, $PATH_PROC_SCSI,
[Define path to /proc/scsi/scsi.])
AC_DEFINE_UNQUOTED(PATH_PROC_USB, $PATH_PROC_USB,
Index: sysdeps/linux/pcmcia.c
===
--- sysdeps/linux/pcmcia.c.orig
+++ sysdeps/linux/pcmcia.c
@@ -72,6 +72,8 @@
#include errno.h
#include fcntl.h
#include ctype.h
+#include string.h
+#include dirent.h
#include pcmcia/version.h
#include pcmcia/cs_types.h
@@ -79,13 +81,18 @@
#include pcmcia/cistpl.h
#include pcmcia/ds.h
-
+#include discover/sysdep.h
#include discover/device.h
#include discover/utils.h
/* XXX: There's no reason for this to be global. */
static int major = 0;
+static int cmpstringp(const void *p1, const void *p2)
+{
+ return strcmp(* (char * const *) p1, * (char * const *) p2);
+}
+
static int lookup_dev(char *name){
FILE *f;
int n;
@@ -153,7 +160,7 @@ _discover_sysdep_init(discover_sysdep_da
}
discover_sysdep_data_t *
-_discover_get_pcmcia_raw(void)
+_discover_get_pcmcia_raw_ioctl(void)
{
int fd, ns;
ds_ioctl_arg_t arg;
@@ -198,6 +205,142 @@ _discover_get_pcmcia_raw(void)
return head;
}
+discover_sysdep_data_t *
+_discover_get_pcmcia_raw_sys(void)
+{
+discover_sysdep_data_t *head = NULL, *node, *last = NULL;
+FILE *f;
+DIR *pcmciaDir;
+struct dirent *pcmcia_device_entry;
+unsigned int len;
+char *device_dir, *vendor, *model, *p;
+char **device_dir_list = NULL;
+size_t device_dir_list_len, device_dir_index;
+char path[256];
+int ret;
+
+/* Open the directory containing all the PCMCIA device dirs. */
+pcmciaDir = opendir(PATH_SYS_PCMCIA);
+if (pcmciaDir == NULL)
+return _discover_get_pcmcia_raw_ioctl();
+
+/*
+ * The order of links in PATH_SYS_PCMCIA is not sorted. Since
+ * module load order can affect things like device naming,
+ * we should collect the device directory names and sort them.
+ */
+
+for (pcmcia_device_entry = readdir(pcmciaDir); pcmcia_device_entry;
+ pcmcia_device_entry = readdir(pcmciaDir)) {
+device_dir = strdup(pcmcia_device_entry-d_name);
+if (device_dir == NULL)
+continue;
+if (device_dir[0] == '.') {
+free(device_dir);
+continue;
+}
+
+if (device_dir_list == NULL) {
+device_dir_list = (char **)malloc(sizeof(char *));
+device_dir_list_len = 1;
+} else {
+device_dir_list =
+(char **)realloc(device_dir_list,
+ sizeof(char *) * ++device_dir_list_len);
+}
+
+if (device_dir_list != NULL) {
+device_dir_list[device_dir_list_len - 1] = device_dir;
+} else {
+free(device_dir);
+}
+}
+
+closedir(pcmciaDir);
+
+if (device_dir_list == NULL)
+return _discover_get_pcmcia_raw_ioctl();
+
+/* Do a sort. */
+qsort(device_dir_list, device_dir_list_len, sizeof(char *), cmpstringp);
+
+/* Loop through the PCMCIA device dirs. */
+vendor = model = NULL;
+for (device_dir_index = 0; device_dir_index device_dir_list_len;
+ device_dir_index++) {
+device_dir = device_dir_list[device_dir_index];
+if (device_dir == NULL
Bug#509355: cpufreqd: segfault while reading acpi battery info
Hello, maybe I can add a bit of information: On Mon, Dec 22, 2008 at 06:54:56AM +0900, Mattia Dongili wrote: On Sun, Dec 21, 2008 at 04:40:28PM +0100, Jonas Zeiger wrote: Package: cpufreqd Version: 2.3.3-3 Severity: grave Justification: renders package unusable I've been trying to run cpufreqd on a Dell Latitude D530 Laptop with a Intel Core2Duo 2.00Ghz CPU, 3GB of DDR2 RAM and two attached battery units using the stock Debian kernel version 2.6.26, but the problem is exactly the same with my custom kernel 2.6.26zlinux (tuned for install on SSD). I have a pretty similar laptop (D530, 2x 2GHz, 2GB RAM, but just one battery). I am running the standard lenny kernel at the moment. I installed cpufreqd to verify this problem, but it does not occur here. So my guess is that it has to do with the second battery... acpi_battery_update : BAT1 - present acpi_battery_update : BAT1 - estimating battery life (timeout: 30.00 - status: (null)) Speicherzugriffsfehler /* german locale, it' a segfault! :( */ ... which seems to get seconded by the status: (null) above (Broken pointer?). To Jonas: What does 'cat /sys/class/power_supply/BAT1/status' print after/before you get this segfault? This is how it looks here: === acpi_battery_update : BAT0 - present acpi_battery_update : BAT0 - estimating battery life (timeout: 28.00 - status: Discharging ) acpi_battery_update : BAT0 - remaining capacity: 5199147 acpi_battery_update : battery life for BAT0 is 112% acpi_battery_update : average battery life 112% === Kind regards, Wolfram -- Dipl.-Ing. Wolfram Sang | http://www.pengutronix.de Pengutronix - Linux Solutions for Science and Industry signature.asc Description: Digital signature
Bug#456550: Bugfixes on the way
Hi Nicolas,
thanks for the bug report.
I sent the following patch upstream and it was comitted in r360. So, I
leave it to the package maintainers if they want to apply the patch
themselves, update to r360 or wait for the 0.5.2. release which should
happen in the near future.
Kind regards,
Wolfram Sang
pcf2vpnc: don't print two spaces if $item is not used
See Debian Bug Report #456550.
Signed-off-by: Wolfram Sang [EMAIL PROTECTED]
---
pcf2vpnc |2 +-
1 file changed, 1 insertion(+), 1 deletion(-)
Index: trunk/pcf2vpnc
===
--- trunk.orig/pcf2vpnc
+++ trunk/pcf2vpnc
@@ -84,7 +84,7 @@
my $text = ## generated by pcf2vpnc\n;
foreach my $section (keys %$config) {
foreach my $item (keys %{ $config-{$section} }) {
- $text .= $section $item .$config-{$section}{$item}.\n;
+ $text .= $section .($item ? $item : '').$config-{$section}{$item}.\n;
}
}
unless (defined $config-{Xauth}) {
Bug#505278: lockfile-progs: lockfile-create locks the file even if it already exists
Hello Manuel, I found a bug in liblockfile1, which makes a lockfile stale after 10 seconds instead of 5 minutes (#505851). So, please report if the fix mentioned there also solves your problem, then we can merge and close this bug. All the best, Wolfram -- Dipl.-Ing. Wolfram Sang | http://www.pengutronix.de Pengutronix - Linux Solutions for Science and Industry signature.asc Description: Digital signature
Bug#505851: liblockfile1: Lockfiles get stale after 10 seconds instead of 5 minutes
Package: liblockfile1 Version: 1.08-2 Severity: grave Tags: patch Justification: might cause serious data loss The lockfile_create-function still contains some debug code, which considers a lock stale after 10 seconds instead of 5 minutes. As the documentation suggests refreshing the lock every 60 seconds, programs might lose the lock unexpectedly. Found while researching #505278. -- System Information: Debian Release: lenny/sid APT prefers testing APT policy: (500, 'testing') Architecture: i386 (i686) Kernel: Linux 2.6.26-1-686 (SMP w/2 CPU cores) Locale: LANG=en_GB.UTF-8, LC_CTYPE=en_GB.UTF-8 (charmap=UTF-8) Shell: /bin/sh linked to /bin/bash Versions of packages liblockfile1 depends on: ii libc6 2.7-13 GNU C Library: Shared libraries liblockfile1 recommends no packages. liblockfile1 suggests no packages. -- no debconf information *** /home/wsa/Tools/liblockfile-1.08/patches/remove_debug_code --- lockfile.c |7 ++- 1 file changed, 2 insertions(+), 5 deletions(-) Index: liblockfile-1.08/lockfile.c === --- liblockfile-1.08.orig/lockfile.c +++ liblockfile-1.08/lockfile.c @@ -391,13 +391,10 @@ int lockfile_check(const char *lockfile, * Without a pid in the lockfile, the lock * is valid if it is newer than 5 mins. */ -#if 0 + if (now st.st_mtime + 300) return 0; -#else - if (now st.st_mtime + 10) - return 0; -#endif + return -1; } -- Dipl.-Ing. Wolfram Sang | http://www.pengutronix.de Pengutronix - Linux Solutions for Science and Industry signature.asc Description: Digital signature
Bug#505378: openssh-client: Backslashes from a banner are printed twice
Package: openssh-client Version: 1:5.1p1-3 Severity: minor Tags: patch If a banner from the server contains a backslash, it will be printed twice. A more detailed description and a patch can be found here: http://bugs.gentoo.org/show_bug.cgi?id=244222 -- System Information: Debian Release: lenny/sid APT prefers testing APT policy: (500, 'testing') Architecture: i386 (i686) Kernel: Linux 2.6.26-1-686 (SMP w/1 CPU core) Locale: LANG=en_US.UTF-8, LC_CTYPE=en_US.UTF-8 (charmap=UTF-8) Shell: /bin/sh linked to /bin/dash Versions of packages openssh-client depends on: ii adduser 3.105 add and remove users and groups ii debconf [debconf-2.0] 1.5.14 Debian configuration management sy ii dpkg 1.14.22Debian package management system ii libc6 2.7-10 GNU C Library: Shared libraries ii libcomerr21.40.2-1 common error description library ii libedit2 2.9.cvs.20050518-4 BSD editline and history libraries ii libkrb53 1.6.dfsg.3~beta1-2 MIT Kerberos runtime libraries ii libncurses5 5.6+20071013-1 Shared libraries for terminal hand ii libssl0.9.8 0.9.8g-10+lenny1 SSL shared libraries ii passwd1:4.0.18.1-11 change and administer password and ii zlib1g1:1.2.3.3.dfsg-6 compression library - runtime Versions of packages openssh-client recommends: ii openssh-blacklist 0.4.1 list of default blacklisted OpenSS ii openssh-blacklist-extra 0.4.1 list of non-default blacklisted Op ii xauth 1:1.0.3-2 X authentication utility Versions of packages openssh-client suggests: pn keychain none (no description available) pn libpam-sshnone (no description available) pn ssh-askpass none (no description available) -- no debconf information -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Bug#447386: typo in INFO
Package: iasl Version: 20061109-0.1 Severity: minor Tags: patch --- Please enter the report below this line. --- There is a typo, I think. Patch attached. Index: temp/INFO === --- temp.orig/INFO 2007-10-20 19:32:29.0 +0200 +++ temp/INFO 2007-10-20 19:33:11.0 +0200 @@ -13,7 +13,7 @@ Priority: optional Description: Intel ASL compiler/decompiler iASL compiles ASL (ACPI Source Language) into AML (ACPI Machine - Language). This AML is suitable for inclusion as a DSDT in sytem + Language). This AML is suitable for inclusion as a DSDT in system firmware. It also can disassemble AML, for debugging purposes. . Homepage: http://developer.intel.com/technology/iapc/acpi/ --- System information. --- Architecture: i386 Kernel: Linux 2.6.22-2-686 Debian Release: lenny/sid 500 testing security.debian.org 500 testing ftp.tu-chemnitz.de 500 stable ftp.uni-kl.de --- Package information. --- Depends (Version) | Installed ===-+-=== libc6(= 2.5-5) | 2.6.1-1+b1 -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Bug#447387: changes.txt and changelog are redundant
Package: iasl Version: 20061109-0.1 Severity: minor --- Please enter the report below this line. --- /usr/share/doc/iasl contains changes.txt.gz and changelog.gz, which have the same content. --- System information. --- Architecture: i386 Kernel: Linux 2.6.22-2-686 Debian Release: lenny/sid 500 testing security.debian.org 500 testing ftp.tu-chemnitz.de 500 stable ftp.uni-kl.de --- Package information. --- Depends (Version) | Installed ===-+-=== libc6(= 2.5-5) | 2.6.1-1+b1 -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Bug#443606: Only first console in unicode-mode
Package: kbd Version: 1.12-18 Severity: normal --- Please enter the report below this line. --- After booting, only the first console is in unicode-mode. I worked around this by putting printf '\033%%G' to /etc/profiles. Still, I think it would be nice if this was handled automatically. --- System information. --- Architecture: i386 Kernel: Linux 2.6.21-2-686 Debian Release: lenny/sid 500 testing security.debian.org 500 testing ftp.tu-chemnitz.de --- Package information. --- Depends (Version) | Installed ==-+- libc6 (= 2.5-5) | 2.6.1-1+b1 console-common | 0.7.70 OR console-setup | lsb-base (= 3.0-10) | 3.1-24 -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Bug#443645: let unicode_start honor CONSOLE_FONT from /etc/kbd/config
Package: kbd Version: 1.12-18 Severity: wishlist --- Please enter the report below this line. --- Currently when booting, a lot of font changes are happening on my system: 1) Kernel sets up 132x60-screen-mode with an 8x8 font 2) keymap.sh calls unicode_start without a parameter, so a default 8x16(!) font is loaded 3) console-screen.kbd.sh finally loads the desired 8x8-font specified in /etc/kbd/config In my eyes, this font-changing from small to big to small does not look very elegant. I would suggest a solution, that unicode_start will honor a possible default-font from /etc/kbd/config, too. I experimently added some simple support for CONSOLE_FONT and it works nicely. I would extend this to also support CONSOLE_FONT_vcX and send it as a patch, if this is a wanted feature. All the best, Wolfram --- System information. --- Architecture: i386 Kernel: Linux 2.6.21-2-686 Debian Release: lenny/sid 500 testing security.debian.org 500 testing ftp.tu-chemnitz.de --- Package information. --- Depends (Version) | Installed ==-+- libc6 (= 2.5-5) | 2.6.1-1+b1 console-common | 0.7.70 OR console-setup | lsb-base (= 3.0-10) | 3.1-24 -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Bug#133421: Still present in 0.76
found 133421 0.7.6 thanks Please apply the patch which Julien sent in this thread on 21 Jun 2007. And maybe fix the double closing in the changelog as well ;) Bye, Wolfram -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Bug#304694: kanatest: finer selection
Version 0.4.2. includes such a feature, so I suggest to close this bug. Wolfram -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Bug#256558: kanatest: best times
Since version 0.4 kanatest can do such things. I suggest to close this bug. -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Bug#431926: quilt: fails to run with mawk or original-awk
Package: quilt
Severity: minor
The quilt test-suite fails when using mawk or original-awk instead of
gawk. After applying this patch, all run fine. It just drops a check
for a word boundary, which is a gawk-extension. I think it is safe to
use it, as there is very similar code in mail.in which does neither use
word-boundary checks. I suggest applying this patch and replacing the
gawk-dependency with a general awk-dependency.
*** awk-fix
Index: quilt-0.46/quilt/mail.in
===
--- quilt-0.46.orig/quilt/mail.in 2006-09-05 15:44:45.0 +0200
+++ quilt-0.46/quilt/mail.in2007-07-03 23:47:04.0 +0200
@@ -204,9 +204,9 @@
if [ [EMAIL PROTECTED] -eq 0 ]
then
local desc=$(echo $(echo $header | awk '
- /^EDESC\/ { desc = 0 }
+ /^EDESC/{ desc = 0 }
desc{ print }
- /^DESC\/ { desc = 1 }
+ /^DESC/ { desc = 1 }
'))
if [ -n $desc ]
then
-- System Information:
Debian Release: 4.0
APT prefers stable
APT policy: (990, 'stable'), (500, 'oldstable')
Architecture: i386 (i586)
Kernel: Linux 2.4.32
Locale: LANG=C, LC_CTYPE=C (charmap=ANSI_X3.4-1968)
Shell: /bin/sh linked to /bin/bash
--
To UNSUBSCRIBE, email to [EMAIL PROTECTED]
with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Bug#409857: #409857 solved IMHO
I also had this problem back then with version 3.31, for example when querying 'svgatextmode'. Since I updated to 3.38 this error never occured again, although I queried all projects again which made reportbug crash before. I suggest to close this bug. Wolfram -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
