Bug#243938: ITP: rkhunter
* Micah Anderson [EMAIL PROTECTED], [2005-08-16 10:24 -0500]: On Sun, 14 Aug 2005, Frederik Dannemare wrote: I'll see what I can do. Hopefully, I'll manage to find some time in the upcoming weekends... Do not apply more stress than necessary. Myself, or one of the others here would be happy to get the package into shape and get it uploaded to get things started, then when you have more time you can begin to do either co-maintainence, or take over the package. [...] http://people.debian.org/~ema/packages/ This is Emanuele's last attempt, we haven't heard anything from him here, so we can assume it is the latest. It is. However, I imagine it needs to be updated to a newer version, and perhaps integrate your changes that you sent to upstream. Right. I'm currently a bit busy with Debian (and real life) work, so I don't think I'll have the time to maintain rkhunter with the due care. I think that Micah is surely a better sponsor than me for security related packages; however, if my help is needed, I'm here. ciao, ema signature.asc Description: Digital signature
Bug#315006: [Pkg-xfce-devel] Bug#315006: Should provide the xfce4-taskbar-plugin package
reassign 315006 wnpp retitle 315006 ITP: xfce4-taskbar-plugin -- taskbar plugin for the Xfce4 panel thanks * Package name: xfce4-taskbar-plugin Version : 0.2.2 Upstream Author : Andre Lerche [EMAIL PROTECTED] * URL : http://download.berlios.de/xfce-goodies/ * License : BSD Description : taskbar plugin for the Xfce4 panel This plugin allows to have an embed taskbar on the Xfce panel. The size can be changed via the properties dialog. . Homepage: http://xfce-goodies.berlios.de/ ciao, ema -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Bug#315447: xfce4-weather-plugin: fails to install
Hello Cyril, * Cyril Brulebois [EMAIL PROTECTED], [2005-06-22 20:45 +0200]: Package: xfce4-weather-plugin Version: 0.3.9-1 Severity: normal Tags: patch Due to dependency problems, this package do not install. It depends on: libxfcegui4-1, which is not installable. Yup! I am uploading 0.4.9-2 to unstable right now. Thanks for your report! ciao, ema signature.asc Description: Digital signature
Bug#322165: setfont from 1.2-12 seems broken
Package: kbd Version: 1.12-12 Severity: important Hello Denis, the recent upgrade from 1.12-11 to 1.12-12 breaks the setfont binary on my system. Trying to use it always causes the following error: setfont: Input file: trailing garbage Downgrading to 1.12-11 solves the problem. I really can't understand how this can be possible, since a debdiff between -11 and -12 doesn't show anything which can explain this behaviour. I'll be happy to provide additional information, if needed. Thanks for your time. ciao, ema signature.asc Description: Digital signature
Bug#369147: GetCache() segfaults if called before InitSystem()
tag 369147 patch
thanks
* Josh Triplett [EMAIL PROTECTED], [2006-05-27 13:02 -0700]:
apt_pkg.GetCache() segfaults if called before apt_pkg.InitSystem():
import apt_pkg
apt_pkg.GetCache()
Segmentation fault
It should raise an exception like other functions do:
import apt_pkg
apt_pkg.VersionCompare(1,2)
Traceback (most recent call last):
File stdin, line 1, in ?
ValueError: _system not initialized
The attached patch fixes this bug, please consider applying it.
Thanks.
ciao,
ema
diff -Nru python-apt-0.7.6/python/cache.cc python-apt-0.7.6/python/cache.cc
--- python-apt-0.7.6/python/cache.cc2008-06-17 17:26:33.0 +0200
+++ python-apt-0.7.6/python/cache.cc2008-07-12 19:31:15.0 +0200
@@ -928,6 +928,11 @@
if (PyArg_ParseTuple(Args, |O, pyCallbackInst) == 0)
return 0;
+if (_system == 0) {
+PyErr_SetString(PyExc_ValueError,_system not initialized);
+return 0;
+}
+
pkgCacheFile *Cache = new pkgCacheFile();
if(pyCallbackInst != 0) {
Bug#480026: RFA: midori -- Fast and lightweight web browser
Package: wnpp Severity: normal Due to lack of time I'm offering midori for adoption. Helpful upstream, package in decent shape. ciao, ema -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Bug#417597: vserver-debiantools: newvserver modifies /etc/motd of host system
* Ola Lundqvist [EMAIL PROTECTED], [2007-04-03 20:18 +0200]: On Tue, Apr 03, 2007 at 09:06:38AM -0700, Vagrant Cascadian wrote: so, after running: newvserver --hostname practice --ip 192.168.1.55/24 --domain localnet \ --dist etch --mirror http://mirrors.kernel.org/debian --interface eth0 i find the /etc/motd on the host system contains: Debian GNU/Linux (etch/i686) practice.localnet Me too! Could you add some debug output in the newvserver script to print the real location that it modifies. Commands given on the root server: [EMAIL PROTECTED]:~$ ls -l /etc/motd lrwxrwxrwx 1 root root 13 2007-02-19 21:46 /etc/motd - /var/run/motd [EMAIL PROTECTED]:~$ ls -l /var/lib/vservers/ns/etc/motd lrwxrwxrwx 1 root root 13 2007-04-06 13:18 /var/lib/vservers/ns/etc/motd - /var/run/motd They both point to the same file. Maybe the right thing to do is creating a new motd for the guests, rather than pointing to /var/run/motd? ciao, ema signature.asc Description: Digital signature
Bug#362394: After upgrade font not available
Hello Andrei, I had the same problem, and solved it (without knowing exactly what's happening). I used to call rxvt-unicode with -fn terminus-16 and it stopped working after the last update. I've tried to change the font name to xft:Terminus:pixelsize=16, and now it seems to work. HTH. ciao, ema signature.asc Description: Digital signature
Bug#354214: amule-daemon: fails to start
Package: amule-daemon Version: 2.1.0-3 Severity: grave Justification: renders package unusable Executing /etc/init.d/amuled as root the daemon fails to start without meaningful output. This is the output of /usr/bin/amuled launched as a normal user (user with a running amule configuration in ~/.aMule): aMule Version: aMuled 2.1.0 using wxGTK2 v2.6.1 (Unicoded) Terminated after throwing an instance of 'CInvalidStateEx' what(): CRunTimeException::CInvalidStateException: CFile: Cannot get length of closed file. backtrace: [2] wxAppTraits::~wxAppTraits() in amuled [0x806f27d] [3] wxEntry(int, wchar_t**) in /usr/lib/libwx_baseu-2.6.so.0[0xb79ef574] [4] wxEntry(int, char**) in /usr/lib/libwx_baseu-2.6.so.0[0xb79ef5ee] [5] __gxx_personality_v0 in amuled[0x80691ce] [6] __libc_start_main in /lib/tls/libc.so.6[0xb774aeb0] [7] wxAppConsole::Initialize(int, wchar_t**) in amuled[0x80690f1] -- System Information: Debian Release: testing/unstable APT prefers unstable APT policy: (500, 'unstable') Architecture: i386 (i686) Shell: /bin/sh linked to /bin/bash Kernel: Linux 2.6.14-1-686 Locale: LANG=it_IT.UTF-8, LC_CTYPE=it_IT.UTF-8 (charmap=UTF-8) Versions of packages amule-daemon depends on: ii amule-common 2.1.0-3common files for aMule ii libc6 2.3.6-1GNU C Library: Shared libraries an ii libcrypto++5.2c2a 5.2.1c2a-2 General purpose cryptographic shar ii libgcc1 1:4.0.2-9 GCC support library ii libpng12-01.2.8rel-5 PNG library - runtime ii libreadline5 5.1-6 GNU readline and history libraries ii libstdc++64.0.2-9The GNU Standard C++ Library v3 ii libwxgtk2.6-0 2.6.1.2wxWidgets Cross-platform C++ GUI t ii zlib1g1:1.2.3-9 compression library - runtime amule-daemon recommends no packages. -- no debconf information ciao, ema -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Bug#359206: [Pkg-xfce-devel] Bug#359206: xfce4-panel: xfce4 panel crashes due to a free() of an invalid pointer
* Yves-Alexis Perez [EMAIL PROTECTED], [2006-03-27 11:41 +0200]: On Mon, 2006-03-27 at 11:10 +0200, Nando Santagata wrote: *** glibc detected *** free(): invalid pointer: 0x083017a8 *** I tried to remove the plug-ins one by one, just to determine if the it's xfce4-panel itself to crash or one of the plugins, but the remove operation causes xfce4-panel to crash. This is a known bug (see #358358 and #358249) Could you try running xfce4-panel that way: G_SLICE=always-malloc xfce4-panel Are you using the xfce4-weather-plugin ? Could you please tell us which plugins you're using? Thanks. ciao, ema signature.asc Description: Digital signature
Bug#351434: [Pkg-xfce-devel] Bug#351434: xfce4-mixer: I have installed all updates from debian testing inklusiv alsa-base. Alsamixergui is working properly.
retitle 351434 xfce4-mixer: not working after the -oss -alsa split thanks * Simon Huggins [EMAIL PROTECTED], [2006-02-05 14:05 +]: On Sat, Feb 04, 2006 at 10:04:05PM +0100, Marek Straka wrote: [an empty bug report] What's the bug? I guess that xfce4-mixer is not working for Marek although he installed everything and alsamixergui is working fine. If my guess is incorrect, feel free to retitle the bug. Marek, did you choose the correct device and wannabe master in the plugin properties? ciao, ema signature.asc Description: Digital signature
Bug#351905: fwanalog: Please inlude all upstream examples files in the package
tag 351905 pending thanks Hello Jerome, * Jerome Warnier [EMAIL PROTECTED], [2006-02-08 13:04 +0100]: Package: fwanalog Version: 0.6.4-7 Severity: wishlist At least fwanalog.opts.fw1 is present upstream and not in your package. Please include it in any future upload. The next (pending) upload will include all the upstream examples. ciao, ema signature.asc Description: Digital signature
Bug#354214: followup for 354214
It seems that the problem is caused by wrong permissions on some files in ~/.aMule -rw-r--r-- 1 root root 5569 2006-02-24 12:56 amule.conf -rw-r- 1 ema ema 145780 2006-02-24 12:56 clients.met -rw-r- 1 root root 145780 2006-02-24 12:56 clients.met.BAK -rw-r--r-- 1 ema ema 361 2005-08-24 15:17 cryptkey.dat -rw-r- 1 ema ema 5 2006-02-24 12:56 emfriends.met -rw-r--r-- 1 ema ema 0 2005-12-29 18:55 ipfilter.dat -rw-r--r-- 1 ema ema 299 2006-02-21 17:54 ipfilter_static.dat -rw-r- 1 ema ema 28 2006-02-24 12:56 key_index.dat -rw-r- 1 ema ema 38280 2006-02-23 15:28 known2.met -rw-r- 1 ema ema9619 2006-02-24 12:56 known.met -rw-r--r-- 1 ema ema 12 2006-02-27 16:43 lastversion -rw-r- 1 ema ema 12 2006-02-24 12:56 load_index.dat -rw-r--r-- 1 ema ema 180 2006-02-27 16:43 logfile -rw--- 1 ema ema 6 2006-02-27 16:43 muleLock -rw-r- 1 ema ema 4 2006-02-24 12:56 nodes.dat -rw-r- 1 ema ema 17 2006-02-24 12:56 preferences.dat -rw-r- 1 ema ema 23 2006-02-24 12:56 preferencesKad.dat -rw-r- 1 root root 80842 2006-02-24 12:56 server.met -rw-r- 1 ema ema 80842 2006-02-24 12:55 server_met.old -rw-r--r-- 1 root root 0 2006-02-24 12:56 shareddir.dat -rw-r- 1 ema ema 12 2006-02-24 12:56 src_index.dat I really don't think I've changed them myself. Changing the ownership of the root:root files fixed the problem. Note that someone else seems to have a similar problem: http://bbs.kijiji.com.cn/topic/view/3713.html Not that it is very informative. :) Thanks. ciao, ema -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Bug#355254: mousepad: Command line options not working
Package: mousepad Version: 0.2.2-2 Severity: normal According to mousepad(1), the program accepts the -h (--help) and the -v (--version) command line options. Actually, they're handled as filenames, rather than as options. -- System Information: Debian Release: testing/unstable APT prefers unstable APT policy: (500, 'unstable') Architecture: i386 (i686) Shell: /bin/sh linked to /bin/bash Kernel: Linux 2.6.14-1-686 Locale: LANG=it_IT.UTF-8, LC_CTYPE=it_IT.UTF-8 (charmap=UTF-8) Versions of packages mousepad depends on: ii libatk1.0-0 1.10.3-1 The ATK accessibility toolkit ii libc6 2.3.6-3GNU C Library: Shared libraries an ii libglib2.0-0 2.8.6-1The GLib library of C routines ii libgtk2.0-0 2.8.13-1 The GTK+ graphical user interface ii libpango1.0-0 1.10.4-1 Layout and rendering of internatio ii libxfce4util-14.2.3.2-1 Utility functions library for Xfce ii libxfcegui4-3 4.2.3-1Basic GUI C functions for Xfce4 Versions of packages mousepad recommends: ii xfprint4 4.2.3-1Printer GUI for Xfce4 -- no debconf information ciao, ema signature.asc Description: Digital signature
Bug#346489: [Pkg-xfce-devel] Bug#346489: mousepad: cursor is hardcoded with black color, should be text color
tag 346489 unreproducible tag 346489 moreinfo thanks bts Hello Ashar, * Ashar Voultoiz [EMAIL PROTECTED], [2006-01-08 13:42 +0100]: I use a white font on dark blue background theme. In mousepad, the text is correctly displayed with a white color but the cursor is black. That makes it hard to see :p Could you please specify which theme you're using? I've tried with the theme called Xfce-dusk and mousepad behaves correctly, displaying a white blinking cursor on black background. Thanks. ciao, ema signature.asc Description: Digital signature
Bug#350470: ITP: xfce4-smartbookmark-plugin -- search the web via the Xfce4 panel
Package: wnpp Severity: wishlist Owner: Debian Xfce Maintainers [EMAIL PROTECTED] * Package name: xfce4-smartbookmark-plugin Version : 0.2 Upstream Author : Emanuele Rocca [EMAIL PROTECTED] * URL : http://people.debian.org/~ema/ * License : GPL Description : search the web via the Xfce4 panel This plugin adds a text field to the Xfce panel, allowing the user to search the web. The URL and the text field size are configurable options. . Typical use cases are: Google, Wikipedia, the Debian Bug Tracking System . xfce4-smartbookmark-plugin is based on the smart bookmark concept: http://en.wikipedia.org/wiki/Smart_Bookmark ciao, ema signature.asc Description: Digital signature
Bug#351038: ITP: arpoison -- A program to send custom ARP packets
Hello, * Pieter-Augustijn Van Malleghem [EMAIL PROTECTED], [2006-02-02 14:03 +0100]: * Package name: arpoison Version : 0.6 Upstream Author : Buer [EMAIL PROTECTED] * URL : http://arpoison.sourceforge.net * License : GPL-2 Description : A program to send custom ARP packets (Include the long description here.) You should really write a long description for the package and put it in the ITP. http://www.debian.org/doc/developers-reference/ch-best-pkging-practices.en.html#s-bpp-pkg-desc ciao, ema signature.asc Description: Digital signature
Bug#374287: ITP: tuxguitar -- TuxGuitar is a multitrack guitar tablature editor and player. It can open GP3, GP4, and GP5 files.
Hello Philippe, * Philippe Coval [EMAIL PROTECTED], [2006-06-18 13:14 +0200]: * Package name: tuxguitar Version : 0.6 Upstream Author : Julian Casadesus akdmia[a]users.sourceforge.net * URL : http://www.herac.com.ar/soluciones/tuxguitar.htm * License : LGPL Programming Lang: Java Description : TuxGuitar is a multitrack guitar tablature editor and player. It can open GP3, GP4, and GP5 files. With TuxGuitar, you will be able to compose music using the following features: Nice. BTW, you should follow some guidelines for the descriptions (short and long). http://www.debian.org/doc/debian-policy/ch-binary.html#s-descriptions http://www.debian.org/doc/debian-policy/ch-controlfields.html#s-f-Description http://www.debian.org/doc/manuals/developers-reference/ch-best-pkging-practices.en.html#s-bpp-desc-basics Thanks. ciao, ema -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Bug#374034: [Pkg-xfce-devel] Bug#374034: missing dependencies to get verve-focus working
Hello Roberto,
* Roberto Pariset [EMAIL PROTECTED], [2006-06-17 0:09 +0200]:
as reported on [1], it is possible to bind a key to verve-focus to allow
(guess?) verve plugin to have focus. This needs D-BUS bindings for Python.
So python2.4-dbus should be added to dependencies. In addiction,
python{,2.4}-gtk2 is required too.
Then, /usr/bin/verve-focus first line should be patched in this way:
- #!/usr/bin/env python
+ #!/usr/bin/env python2.4
After doing this, one would think to have things done. There we go:
$ verve-focus
Introspect error: The name org.xfce.RunDialog was not provided by any
.service files
Traceback (most recent call last):
File /usr/bin/verve-focus, line 48, in ?
dbus_interface = org.xfce.RunDialog)
File /usr/lib/python2.4/site-packages/dbus/proxies.py, line 25, in
__call__
ret = self._proxy_method (*args, **keywords)
File /usr/lib/python2.4/site-packages/dbus/proxies.py, line 102, in
__call__
reply_message = self._connection.send_with_reply_and_block(message,
timeout)
File dbus_bindings.pyx, line 458, in
dbus_bindings.Connection.send_with_reply_and_block
dbus_bindings.DBusException: The name org.xfce.RunDialog was not provided by
any .service files
After a quick search for org.xfce.RunDialog I've found this one:
http://mirror.gezeiten.org/lunar/modules/xfce4-goodies-svn/verve-plugin-svn/DEPENDS
If I understand that file correctly, it seems that you need to
--disable-dbus to enable the aforementioned org.xfce.RunDialog service.
HTH.
ciao,
ema
--
To UNSUBSCRIBE, email to [EMAIL PROTECTED]
with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Bug#370119: ITP: xfce4-mount-plugin -- mount plugin for the Xfce4 panel
Package: wnpp Severity: wishlist Owner: Debian Xfce Maintainers [EMAIL PROTECTED] * Package name: xfce4-mount-plugin Version : 0.4.5 Upstream Author : Jean-Baptiste Dulong [EMAIL PROTECTED] * URL : http://download.berlios.de/xfce-goodies/ * License : GPLv2 Programming Lang: C Description : mount plugin for the Xfce4 panel This plugin for Xfce displays a list of the various devices available, giving the opportunity to mount/umount them. . Homepage: http://xfce-goodies.berlios.de/ -- System Information: Debian Release: testing/unstable APT prefers unstable APT policy: (500, 'unstable'), (1, 'experimental') Architecture: i386 (i686) Shell: /bin/sh linked to /bin/bash Kernel: Linux 2.6.16-1-686 Locale: LANG=it_IT.utf8, LC_CTYPE=it_IT.utf8 (charmap=UTF-8) ciao, ema -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Bug#374618: (no subject)
The bug will be closed with the next upload, given that we decided to replace kill with /bin/kill to make lintian happy. Unfortnately, /bin/kill is provided by procps. Sorry for the inconvenience. ciao, ema -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Bug#395598: fortunes-it: missing binary-arch target in debian/rules (Policy 4.9)
severity 395598 serious tag 395598 pending thanks Hello Aurelien, * Aurelien Jarno [EMAIL PROTECTED], [2006-10-27 22:44 +0200]: Package: fortunes-it Severity: important [2] http://release.debian.org/etch_rc_policy.txt Raising the severity to serious, as per etch_rc_policy.txt. I'll upload a fixed version ASAP, thanks for your bug report. ciao, ema -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Bug#543023: NMU for this bug?
Hi guys, On 28/09/09 - 10:47, Kumar Appaiah wrote: Would you consider doing an NMU for this bug? Given that the bug has been open with a patch for well over a month, I'd say you could proceed with at least a DELAYED NMU. No need to delay the NMU, feel free to upload. ciao, ema signature.asc Description: Digital signature
Bug#617230: python-couchdbkit: Syntax errors in various scripts due to 'with' statements
Package: python-couchdbkit Version: 0.5.2-1.1 Severity: important Hi, I'm getting the following errors when upgrading python-couchdbkit. The attached patch fixes them, basically just adding a bunch of from __future__ import with_statement. Processing triggers for python-support ... /usr/lib/pymodules/python2.5/couchdbkit/consumer/ceventlet.py:51: Warning: 'with' will become a reserved keyword in Python 2.6 Compiling /usr/lib/pymodules/python2.5/couchdbkit/consumer/ceventlet.py ... File /usr/lib/pymodules/python2.5/couchdbkit/consumer/ceventlet.py, line 51 with resp.body_stream() as body: ^ SyntaxError: invalid syntax /usr/lib/pymodules/python2.5/couchdbkit/consumer/cgevent.py:39: Warning: 'with' will become a reserved keyword in Python 2.6 Compiling /usr/lib/pymodules/python2.5/couchdbkit/consumer/cgevent.py ... File /usr/lib/pymodules/python2.5/couchdbkit/consumer/cgevent.py, line 39 with resp.body_stream() as body: ^ SyntaxError: invalid syntax /usr/lib/pymodules/python2.5/couchdbkit/ext/pylons/test.py:15: Warning: 'with' will become a reserved keyword in Python 2.6 Compiling /usr/lib/pymodules/python2.5/couchdbkit/ext/pylons/test.py ... File /usr/lib/pymodules/python2.5/couchdbkit/ext/pylons/test.py, line 15 with open(fixture_path, r) as fp: ^ SyntaxError: invalid syntax -- System Information: Debian Release: wheezy/sid APT prefers testing APT policy: (500, 'testing'), (1, 'experimental') Architecture: amd64 (x86_64) Kernel: Linux 2.6.32-5-amd64 (SMP w/2 CPU cores) 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 python-couchdbkit depends on: ii python 2.6.6-3+squeeze5 interactive high-level object-orie ii python-anyjson 0.2.3-1 Wraps the best available JSON impl ii python-restkit 3.0.4-1 Restkit is an HTTP resource kit fo ii python-support 1.0.11 automated rebuilding support for P python-couchdbkit recommends no packages. python-couchdbkit suggests no packages. -- no debconf information diff -Nur python-couchdbkit-0.5.2/couchdbkit/consumer/ceventlet.py python-couchdbkit-0.5.2.new//couchdbkit/consumer/ceventlet.py --- python-couchdbkit-0.5.2/couchdbkit/consumer/ceventlet.py 2011-01-10 17:50:28.0 +0100 +++ python-couchdbkit-0.5.2.new//couchdbkit/consumer/ceventlet.py 2011-03-07 11:46:03.0 +0100 @@ -3,6 +3,8 @@ # This file is part of couchdbkit released under the MIT license. # See the NOTICE for more information. +from __future__ import with_statement + import traceback import eventlet @@ -13,7 +15,6 @@ from couchdbkit.consumer.sync import SyncConsumer from couchdbkit.utils import json - class ChangeConsumer(object): def __init__(self, db, callback, **params): self.process_change = callback diff -Nur python-couchdbkit-0.5.2/couchdbkit/consumer/cgevent.py python-couchdbkit-0.5.2.new//couchdbkit/consumer/cgevent.py --- python-couchdbkit-0.5.2/couchdbkit/consumer/cgevent.py 2011-01-10 17:50:28.0 +0100 +++ python-couchdbkit-0.5.2.new//couchdbkit/consumer/cgevent.py 2011-03-07 11:46:03.0 +0100 @@ -3,6 +3,8 @@ # This file is part of couchdbkit released under the MIT license. # See the NOTICE for more information. +from __future__ import with_statement + import traceback import gevent diff -Nur python-couchdbkit-0.5.2/couchdbkit/ext/pylons/test.py python-couchdbkit-0.5.2.new//couchdbkit/ext/pylons/test.py --- python-couchdbkit-0.5.2/couchdbkit/ext/pylons/test.py 2011-01-10 17:50:28.0 +0100 +++ python-couchdbkit-0.5.2.new//couchdbkit/ext/pylons/test.py 2011-03-07 11:46:03.0 +0100 @@ -1,3 +1,5 @@ +from __future__ import with_statement + from couchdbkit import BaseDocsLoader, ResourceNotFound from couchdbkit.ext.pylons.db import init_db, sync_design, default_design_path import os, json, unittest
Bug#570066: xen-utils-4.1: should depend on python-lxml
retitle 570066 xen-utils-4.1: should depend on python-lxml thanks Hi, 'xm new' fails on a freshly installed sid system (xen-utils-4.1 4.1.1-2) with the following import error: ImportError: No module named lxml Simply installing python-lxml solves the problem, so I think xen-utils should depend on it. Also, can 599520 be closed now that python-lxml is being used by xenapi? Thanks, ema -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#570066: [Pkg-xen-devel] Bug#570066: xen-utils-4.1: should depend on python-lxml
Hi Bastian, On 25/09 03:42, Bastian Blank wrote: On Sun, Sep 25, 2011 at 03:22:04PM +0200, Emanuele Rocca wrote: 'xm new' fails on a freshly installed sid system (xen-utils-4.1 4.1.1-2) with the following import error: xm create works without. But their behaviour is different, isn't it? Correct me if I am wrong, but my understanding is that machines added with xm create are removed from Xen management after you shut them down. For example, they are not manageable with virt-manager, and they do not show up in xm list. -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#628157: O: worklog -- Keep Track of Time worked on Projects
Package: wnpp Severity: normal I intend to orphan worklog since I am not using it anymore and active upstream development seems stopped. CCing Jon Daley as he has shown interest for urlview by reporting bugs on the BTS. Maintaining a package requires time and skills. Please only adopt this package if you will have enough time and attention to work on it. If you want to be the new maintainer, please see http://www.debian.org/devel/wnpp/index.html#howto-o for detailed instructions how to adopt a package properly. Some information about this package: Package: worklog Version: 1.8-4 Installed-Size: 84 Maintainer: Emanuele Rocca e...@debian.org Architecture: amd64 Homepage: http://www.truxton.com/~trux/software/ Depends: libc6 (= 2.3.5-1), libncurses5 (= 5.4-5) Description: Keep Track of Time worked on Projects From the author: Worklog is a program that helps you keep track of your time. I wrote this program because I have several projects that require me to keep a timesheet. I sometimes spend 5 minutes here and there doing miscellaneous administrative tasks. Rather than invoke an editor on a timesheet file for every little segment of my time spent doing these tasks, I wanted to leave a clock running and indicate with one or two keystrokes the onset or change of any given task. Worklog is a simple ncurses based program to do just that. Tag: admin::logging, interface::text-mode, role::program, scope::utility, uitoolkit::ncurses, use::timekeeping Section: misc Priority: optional Filename: pool/main/w/worklog/worklog_1.8-4_amd64.deb Size: 13818 MD5sum: ba9923fc70bc0919d72cb87094535671 SHA1: 5f562dfc763550cdf921f73303137491a9aab01e SHA256: 0e9410a5c824ab500d15cab0cae0a06c9cf70a7c755e7c4f77363c66097a17a9 -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#627210: fwanalog: Incomplete packaging
retitle 627210 Language file /usr/share/fwanalog/fwanalog.lng is empty tags 627210 + unreproducible thanks Hi Mickaël, thanks for your bug report! On 18/05 07:46, Mickaël Masquelin wrote: Package: fwanalog Version: 0.6.9-6.1 Severity: important Hi, After installing fwanalog on a Debian Squeeze i386 and executing it, i'm getting the following error : analog: Fatal error: language file /usr/share/fwanalog/fwanalog.lng too short: exiting I cannot reproduce the bug. After installing fwanalog in a freshly created squeeze chroot the language file is not empty as you reported: (squeeze)root@saturn:~# ls -l /usr/share/fwanalog/fwanalog.lng -rw-r--r-- 1 root root 14089 May 27 19:52 /usr/share/fwanalog/fwanalog.lng Can you please try to remove and re-install the package? -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#680291: xml2rfc: fails to install, remove, distupgrade, and install again
Hi, On 04/07 10:16, Andreas Beckmann wrote: during a test with piuparts I noticed your package failed to install (in 'squeeze'), remove (but not purge), distupgrade to 'wheezy', and install again. Before the second installation the package is in config-files-remaining state. The configuration is remaining from the last version that was successfully configured - which is from the previous release. Like a plain failure on initial install this makes the package too buggy for a release, thus the severity. This seems to be related to the changes introduced to dh_installcatalogs (see #477751). Helmut, I took the liberty to put you in CC as you probably have some hints for how to proceed? Note that other packages might show the same behavior reported here: docbook-website comes to mind. Thanks, Emanuele -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#674324: ruby-net-sftp: FTBFS: test failed
On 24/05 11:58, Lucas Nussbaum wrote: Source: ruby-net-sftp Version: 1:2.0.5-2 Severity: serious Tags: wheezy sid User: debian...@lists.debian.org Usertags: qa-ftbfs-20120524 qa-ftbfs Justification: FTBFS on amd64 [...] /usr/bin/ruby1.8 -I/usr/lib/ruby/vendor_ruby /usr/lib/ruby/vendor_ruby/gem2deb/test_runner.rb Loaded suite debian/ruby-tests [...] 418 tests, 1059 assertions, 7 failures, 0 errors ERROR: Test ruby1.8 failed. Exiting. dh_auto_install: dh_ruby --install /«PKGBUILDDIR»/debian/tmp returned exit code 1 make: *** [binary] Error 1 Interestingly, with older versions of ruby-mocha all the tests pass without problems. For example, on Ubuntu Oneiric: ema@saturn:~/debian/packages/ruby-net-sftp-2.0.5$ apt-cache policy ruby-mocha ruby-mocha: Installed: 0.9.12-1 Candidate: 0.9.12-1 Version table: *** 0.9.12-1 0 500 http://de.archive.ubuntu.com/ubuntu/ oneiric/universe amd64 Packages 100 /var/lib/dpkg/status ema@saturn:~/debian/packages/ruby-net-sftp-2.0.5$ /usr/bin/ruby1.8 -I/usr/lib/ruby/vendor_ruby /usr/lib/ruby/vendor_ruby/gem2de Running tests for ruby1.8 using debian/ruby-tests.rb... Loaded suite debian/ruby-tests Started ... Finished in 0.690501 seconds. 418 tests, 1147 assertions, 0 failures, 0 errors It looks like the changes introduced in recent upstream versions of ruby-mocha are breaking ruby-net-sftp's tests. Emanuele -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#672284: lintian: False positive: no-debian-copyright when packages supply debian/$pkgname.copyright
Package: lintian Version: 2.5.6 Severity: normal Hi, lintian reports a no-debian-copyright warning for packages that supply a copyright file in debian/$pkgname.copyright That seems to be a valid way to provide copyright files, at least according to dh_installdocs(1). Such a false positive is reported, for example, against eterm: http://lintian.debian.org/maintainer/muammarelkha...@gmail.com.html#eterm http://packages.debian.org/changelogs/pool/main/e/eterm/current/copyright Emanuele -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#672284: lintian: False positive: no-debian-copyright when packages supply debian/$pkgname.copyright
On 09/05 07:51, Jakub Wilk wrote: * Emanuele Rocca e...@debian.org, 2012-05-09, 19:23: lintian reports a no-debian-copyright warning for packages that supply a copyright file in debian/$pkgname.copyright This is correct. It's a violation of Policy §12.5: âA copy of the file which will be installed in â/usr/share/doc/package/copyrightâ should be in âdebian/copyrightâ in the source package.â I see. Than maybe lintian could detect this violation of the Policy and emit a separate tag for packages that ship copyright files under debian/$pkgname.copyright rather than debian/copyright? Thanks, Emanuele -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#628157: Fwd: worklog uploaded to mentors.debian.net
Hi Jon, On 03/09 06:19, Jon Daley wrote: So - Emanuele - I think you said you would be willing to continue sponsoring this package? If not, let me know, and I'll see if there is someone else. I did, but unfortunately I'm pretty busy at the moment. Please go ahead and see if you manage to find a sponsor for worklog. Cheers, Emanuele -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#557481: python-bzutils: removal request
retitle 557481 RM: python-bzutils -- RoQA; orphaned, last upload in 2007, unused reassign 557481 ftp.debian.org thanks Hi, please consider removing python-bzutils. - last upload was in 2007 - orphaned (with maintainer field != QA Group) since 2009 - very low popcon score - no reverse dependencies Thanks, Emanuele -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#641885: mic2: removal request
retitle 641885 RM: mic2 -- RoQA; orphaned, unused, dead upstream reassign 641885 ftp.debian.org thanks Hi, please consider removing mic2 for the following reasons: - very low popcon score - dead upstream - orphaned (with maintainer field != QA Group) since 2011 - no reverse dependencies Thanks, Emanuele -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#782450: ppp: Buffer overflow in radius plugin
NMU diff attached. diff -Nru ppp-2.4.6/debian/changelog ppp-2.4.6/debian/changelog --- ppp-2.4.6/debian/changelog 2014-10-19 11:56:12.0 +0200 +++ ppp-2.4.6/debian/changelog 2015-04-14 08:29:42.0 +0200 @@ -1,3 +1,16 @@ +ppp (2.4.6-3.1) unstable; urgency=high + + * Non-maintainer upload. + * Urgency high due to fix for DoS vulnerability. + * Fix buffer overflow in rc_mksid(). +The function converts the PID of pppd to hex to generate a pseudo-unique +string. If the process id is bigger than 65535 (), its hex +representation will be longer than 4 characters, resulting in a buffer +overflow. This bug can be exploited to cause a remote DoS. +(Closes: #782450) + + -- Emanuele Rocca e...@debian.org Tue, 14 Apr 2015 08:18:06 +0200 + ppp (2.4.6-3) unstable; urgency=high * Urgency high due to fix for CVE-2014-3158. diff -Nru ppp-2.4.6/debian/patches/rc_mksid-no-buffer-overflow ppp-2.4.6/debian/patches/rc_mksid-no-buffer-overflow --- ppp-2.4.6/debian/patches/rc_mksid-no-buffer-overflow 1970-01-01 01:00:00.0 +0100 +++ ppp-2.4.6/debian/patches/rc_mksid-no-buffer-overflow 2015-04-14 08:27:53.0 +0200 @@ -0,0 +1,23 @@ +Description: Fix buffer overflow in rc_mksid() + rc_mksid converts the PID of pppd to hex to generate a pseudo-unique string. + . + If the process id is bigger than 65535 (), its hex representation will be + longer than 4 characters, resulting in a buffer overflow. + . + The bug can be exploited to cause a remote DoS. + . +Author: Emanuele Rocca e...@debian.org +Bug-Debian: https://bugs.debian.org/782450 +Last-Update: 2015-04-14 + +--- ppp-2.4.6.orig/pppd/plugins/radius/util.c ppp-2.4.6/pppd/plugins/radius/util.c +@@ -77,7 +77,7 @@ rc_mksid (void) + static unsigned short int cnt = 0; + sprintf (buf, %08lX%04X%02hX, + (unsigned long int) time (NULL), +- (unsigned int) getpid (), ++ (unsigned int) getpid () % 65535, + cnt 0xFF); + cnt++; + return buf; diff -Nru ppp-2.4.6/debian/patches/series ppp-2.4.6/debian/patches/series --- ppp-2.4.6/debian/patches/series 2014-10-19 11:49:55.0 +0200 +++ ppp-2.4.6/debian/patches/series 2015-04-14 08:17:39.0 +0200 @@ -43,3 +43,4 @@ resolv.conf_no_log zzz_config secure-card-interpreter-fix +rc_mksid-no-buffer-overflow
Bug#770984: [apcupsd] apcaccess may not work on ARM
NMU diff attached.
diff -u apcupsd-3.14.12/debian/changelog apcupsd-3.14.12/debian/changelog
--- apcupsd-3.14.12/debian/changelog
+++ apcupsd-3.14.12/debian/changelog
@@ -1,3 +1,11 @@
+apcupsd (3.14.12-1.1) unstable; urgency=medium
+
+ * Non-maintainer upload.
+ * src/apcaccess.c: declare ch as int to match getopt return type. Fixes
+apcaccess on ARM. (Closes: #770984)
+
+ -- Emanuele Rocca e...@debian.org Tue, 14 Apr 2015 09:14:33 +0200
+
apcupsd (3.14.12-1) unstable; urgency=low
* [84a0ea2] Imported Upstream version 3.14.12
diff -u apcupsd-3.14.12/debian/patches/series apcupsd-3.14.12/debian/patches/series
--- apcupsd-3.14.12/debian/patches/series
+++ apcupsd-3.14.12/debian/patches/series
@@ -4,0 +5 @@
+05-apcaccess-arm.patch
only in patch2:
unchanged:
--- apcupsd-3.14.12.orig/debian/patches/05-apcaccess-arm.patch
+++ apcupsd-3.14.12/debian/patches/05-apcaccess-arm.patch
@@ -0,0 +1,13 @@
+Declare ch as int to match getopt return type. Fix apcaccess behavior on
+arm.
+--- a/src/apcaccess.c
b/src/apcaccess.c
+@@ -146,7 +146,7 @@
+ #endif
+
+// Process standard options
+- char ch;
++ int ch;
+while ((ch = getopt(argc, argv, f:h:p:u)) != -1)
+{
+ switch (ch)
Bug#782563: unblock: ppp/2.4.6-3.1
Package: release.debian.org User: release.debian@packages.debian.org Usertags: unblock Please unblock ppp/2.4.6-3.1. It fixes a DoS vulnerability in the pppd radius plugin. Thanks, ema diff -Nru ppp-2.4.6/debian/changelog ppp-2.4.6/debian/changelog --- ppp-2.4.6/debian/changelog 2014-10-19 11:56:12.0 +0200 +++ ppp-2.4.6/debian/changelog 2015-04-14 08:29:42.0 +0200 @@ -1,3 +1,16 @@ +ppp (2.4.6-3.1) unstable; urgency=high + + * Non-maintainer upload. + * Urgency high due to fix for DoS vulnerability. + * Fix buffer overflow in rc_mksid(). +The function converts the PID of pppd to hex to generate a pseudo-unique +string. If the process id is bigger than 65535 (), its hex +representation will be longer than 4 characters, resulting in a buffer +overflow. This bug can be exploited to cause a remote DoS. +(Closes: #782450) + + -- Emanuele Rocca e...@debian.org Tue, 14 Apr 2015 08:18:06 +0200 + ppp (2.4.6-3) unstable; urgency=high * Urgency high due to fix for CVE-2014-3158. diff -Nru ppp-2.4.6/debian/patches/rc_mksid-no-buffer-overflow ppp-2.4.6/debian/patches/rc_mksid-no-buffer-overflow --- ppp-2.4.6/debian/patches/rc_mksid-no-buffer-overflow1970-01-01 01:00:00.0 +0100 +++ ppp-2.4.6/debian/patches/rc_mksid-no-buffer-overflow2015-04-14 08:27:53.0 +0200 @@ -0,0 +1,23 @@ +Description: Fix buffer overflow in rc_mksid() + rc_mksid converts the PID of pppd to hex to generate a pseudo-unique string. + . + If the process id is bigger than 65535 (), its hex representation will be + longer than 4 characters, resulting in a buffer overflow. + . + The bug can be exploited to cause a remote DoS. + . +Author: Emanuele Rocca e...@debian.org +Bug-Debian: https://bugs.debian.org/782450 +Last-Update: 2015-04-14 + +--- ppp-2.4.6.orig/pppd/plugins/radius/util.c ppp-2.4.6/pppd/plugins/radius/util.c +@@ -77,7 +77,7 @@ rc_mksid (void) + static unsigned short int cnt = 0; + sprintf (buf, %08lX%04X%02hX, + (unsigned long int) time (NULL), +- (unsigned int) getpid (), ++ (unsigned int) getpid () % 65535, + cnt 0xFF); + cnt++; + return buf; diff -Nru ppp-2.4.6/debian/patches/series ppp-2.4.6/debian/patches/series --- ppp-2.4.6/debian/patches/series 2014-10-19 11:49:55.0 +0200 +++ ppp-2.4.6/debian/patches/series 2015-04-14 08:17:39.0 +0200 @@ -43,3 +43,4 @@ resolv.conf_no_log zzz_config secure-card-interpreter-fix +rc_mksid-no-buffer-overflow -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#782567: unblock: apcupsd/3.14.12-1.1
Package: release.debian.org
User: release.debian@packages.debian.org
Usertags: unblock
Please unblock apcupsd/3.14.12-1.1. The NMU fixes apcaccess on ARM (RC
bug #770984).
Thanks,
ema
diff -u apcupsd-3.14.12/debian/changelog apcupsd-3.14.12/debian/changelog
--- apcupsd-3.14.12/debian/changelog
+++ apcupsd-3.14.12/debian/changelog
@@ -1,3 +1,11 @@
+apcupsd (3.14.12-1.1) unstable; urgency=medium
+
+ * Non-maintainer upload.
+ * src/apcaccess.c: declare ch as int to match getopt return type. Fixes
+apcaccess on ARM. (Closes: #770984)
+
+ -- Emanuele Rocca e...@debian.org Tue, 14 Apr 2015 09:14:33 +0200
+
apcupsd (3.14.12-1) unstable; urgency=low
* [84a0ea2] Imported Upstream version 3.14.12
diff -u apcupsd-3.14.12/debian/patches/series
apcupsd-3.14.12/debian/patches/series
--- apcupsd-3.14.12/debian/patches/series
+++ apcupsd-3.14.12/debian/patches/series
@@ -4,0 +5 @@
+05-apcaccess-arm.patch
only in patch2:
unchanged:
--- apcupsd-3.14.12.orig/debian/patches/05-apcaccess-arm.patch
+++ apcupsd-3.14.12/debian/patches/05-apcaccess-arm.patch
@@ -0,0 +1,13 @@
+Declare ch as int to match getopt return type. Fix apcaccess behavior on
+arm.
+--- a/src/apcaccess.c
b/src/apcaccess.c
+@@ -146,7 +146,7 @@
+ #endif
+
+// Process standard options
+- char ch;
++ int ch;
+while ((ch = getopt(argc, argv, f:h:p:u)) != -1)
+{
+ switch (ch)
--
To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org
with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#782450: ppp: Buffer overflow in radius plugin
Correction: the bug occurs if pppd's pid is greater than 65535. The number of running processes is irrelevant.
Bug#782450: ppp: Buffer overflow in radius plugin
Package: ppp Version: 2.4.6-3 Severity: important Tags: patch On systems with more than 65535 processes running, pppd aborts when sending a start accounting message to the RADIUS server because of a buffer overflow in rc_mksid. The process id is used in rc_mksid to generate a pseudo-unique string, assuming that the hex representation of the pid will be at most 4 characters (). __sprintf_chk(), used when compiling with optimization levels greater than 0 and FORTIFY_SOURCE, detects the buffer overflow and makes pppd crash. The following patch fixes the problem. --- ppp-2.4.6.orig/pppd/plugins/radius/util.c +++ ppp-2.4.6/pppd/plugins/radius/util.c @@ -77,7 +77,7 @@ rc_mksid (void) static unsigned short int cnt = 0; sprintf (buf, %08lX%04X%02hX, (unsigned long int) time (NULL), - (unsigned int) getpid (), + (unsigned int) getpid () % 65535, cnt 0xFF); cnt++; return buf; -- System Information: Debian Release: 8.0 APT prefers testing APT policy: (500, 'testing') Architecture: amd64 (x86_64) Foreign Architectures: i386 Kernel: Linux 3.16.0-4-amd64 (SMP w/4 CPU cores) Locale: LANG=en_US.UTF-8, LC_CTYPE=en_US.UTF-8 (charmap=UTF-8) Shell: /bin/sh linked to /bin/dash Init: systemd (via /run/systemd/system) Versions of packages ppp depends on: ii init-system-helpers 1.22 ii libc62.19-17 ii libpam-modules 1.1.8-3.1 ii libpam-runtime 1.1.8-3.1 ii libpam0g 1.1.8-3.1 ii libpcap0.8 1.6.2-2 ii procps 2:3.3.9-9 -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#782450: ppp: Buffer overflow in radius plugin
Hi Roger, On 14/04 12:13, Roger Lynn wrote: On 14/04/2015 07:48, Emanuele Rocca wrote: +--- ppp-2.4.6.orig/pppd/plugins/radius/util.c ppp-2.4.6/pppd/plugins/radius/util.c +@@ -77,7 +77,7 @@ rc_mksid (void) + static unsigned short int cnt = 0; + sprintf (buf, %08lX%04X%02hX, + (unsigned long int) time (NULL), +- (unsigned int) getpid (), ++ (unsigned int) getpid () % 65535, Shouldn't this be 65536? If you're trying to limit to 0x then 65535 too small. getpid () 0x might be clearer than using the modulus operator and should have exactly the same effect. Good catch! You are right, the patch limits to 0xFFFE instead of 0x. However it does fix the vulnerability, so I don't think a new upload is required. Cheers, ema -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#770984: [apcupsd] apcaccess may not work on ARM
Hi,
On 25/11 07:15, Adrien Grellier wrote:
apcaccess is not working on raspberry pi : it always respond as if -h
option was given.
I can confirm that the issue is reproducible on asachi.debian.org (armhf):
(sid_armhf-dchroot)ema@asachi:~$ /sbin/apcaccess
Usage: apcaccess [-f config-file] [-h host[:port]] [-p
parameter-name] [-u] [command] [host[:port]]
-f Load default host,port from given conf file (default:
/etc/apcupsd/apcupsd.conf)
-h Connect to host and port (supercedes conf file)
-p Return only the value of the named parameter rather than all
parameters and values
-u Strip unit labels
Supported commands: 'status' (default)
Trailing host/port spec overrides -h and conf file.
And that the proposed patch fixes the bug:
(sid_armhf-dchroot)ema@asachi:~$ ./x/sbin/apcaccess
APC : 001,017,0437
DATE : 2015-04-10 20:51:16 +
HOSTNAME : asachi
[...]
--- apcupsd-3.14.12.orig/src/apcaccess.c
+++ apcupsd-3.14.12/src/apcaccess.c
@@ -146,7 +146,7 @@
#endif
// Process standard options
- char ch;
+ int ch;
while ((ch = getopt(argc, argv, f:h:p:u)) != -1)
{
switch (ch)
--
To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org
with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#785776: O: fwanalog -- firewall log-file report generator (using analog)
Package: wnpp Severity: normal Orphaning fwanalog since I am not using it any longer. fwanalog is a shell script that parses and summarizes firewall logfiles. It is able to work on firewall logs from ipchains (Linux 2.2), iptables (Linux 2.4), ipf (OpenBSD, FreeBSD and NetBSD) and some ZyXEL/NetGear routers. . It uses analog to generate the log-files, which includes daily statistics and such, and is both formatted in html and text (for online perusing, and a daily email, for instance). -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#827900: curl: new upstream release 7.49.1
Package: curl Version: 7.47.0-1 Severity: wishlist curl 7.49 ships important new features including TCP Fast Open and improved http2 support. https://curl.haxx.se/changes.html#7_49_1 Please consider packaging it. Thanks, Emanuele
Bug#828048: httping: build with TFO support
Package: httping Version: 2.4-1 Severity: wishlist Please enable TFO support in httping by passing the --with-tfo argument to ./configure. Cheers, Emanuele
Bug#819984: init-system-helpers: service(8) version number contains 'ubuntu1'
On 04/04 05:09, Michael Biebl wrote: > Version "0.91" seems rather arbitrary and has basically stayed the same > since the script was merged from Ubuntu, it doesn't seem to be > particularly useful. > > I wonder whether we shouldn't just drop "--version" or make it a nop. Given that --version has basically never changed it seems unlikely that other programs might depend on it. I'd suggest to drop it altogether. Cheers, ema
Bug#819984: init-system-helpers: service(8) version number contains 'ubuntu1'
Package: init-system-helpers Version: 1.29 Severity: minor Dear Maintainer, /usr/sbin/service --version returns the following output on Debian Sid: service ver. 0.91-ubuntu1 On Debian, the service script should probably not include 'ubuntu1' in its version number. Cheers, Emanuele -- System Information: Debian Release: stretch/sid APT prefers unstable APT policy: (500, 'unstable'), (1, 'experimental') Architecture: amd64 (x86_64) Kernel: Linux 4.5.0-rc7-amd64 (SMP w/4 CPU cores) Locale: LANG=en_US.UTF-8, LC_CTYPE=en_US.UTF-8 (charmap=UTF-8) Shell: /bin/sh linked to /bin/dash Init: systemd (via /run/systemd/system) Versions of packages init-system-helpers depends on: ii perl-base 5.22.1-9 init-system-helpers recommends no packages. init-system-helpers suggests no packages. -- no debconf information
Bug#830843: [Pkg-varnish-devel] Bug#830843: Bug#830843: varnish-modules: accesses the internet during build
On 12/07 12:21, Emanuele Rocca wrote: > We need to either patch varnishtest and hardcode feature_dns, or avoid > running the tests altogether. As ssm suggested, we can use libnss-wrapper instead and avoid actually performing the DNS request: http://anonscm.debian.org/cgit/pkg-varnish/varnish-modules.git/commit/?id=76bb49f0be2ecb0e33d39584987916a6aac254b7
Bug#830843: [Pkg-varnish-devel] Bug#830843: varnish-modules: accesses the internet during build
Hi, On 12/07 09:22, Chris Lamb wrote: > Whilst varnish-modules builds successfully on unstable/amd64, according to > Debian Policy 4.9 packages may not attempt network access during > a build. > > 00:00:00.00 IP e66b957b9098.60905 > > sitecomwlr1000.sitecomwlr1000.domain: 10880+ A? phk.freebsd.dk. (32) > 00:00:00.60 IP e66b957b9098.60905 > > sitecomwlr1000.sitecomwlr1000.domain: 24843+ ? phk.freebsd.dk. (32) > 00:00:00.001007 IP e66b957b9098.54550 > > sitecomwlr1000.sitecomwlr1000.domain: 27794+ A? phk.freebsd.dk. (32) > 00:00:00.001044 IP e66b957b9098.54550 > > sitecomwlr1000.sitecomwlr1000.domain: 39210+ ? phk.freebsd.dk. (32) > 00:00:00.001129 IP e66b957b9098.45718 > > sitecomwlr1000.sitecomwlr1000.domain: 1+ A? phk.freebsd.dk. (32) > 00:00:00.001152 IP e66b957b9098.45718 > > sitecomwlr1000.sitecomwlr1000.domain: 3037+ ? phk.freebsd.dk. (32) > > [..] This is because of varnishtest trying to resolve phk.freebsd.dk every time it is invoked to check if DNS works: https://github.com/varnishcache/varnish-cache/blob/master/bin/varnishtest/vtc_main.c#L616 We need to either patch varnishtest and hardcode feature_dns, or avoid running the tests altogether.
Bug#837089: ITP: prometheus-varnish-exporter -- Varnish exporter for Prometheus
Package: wnpp Severity: wishlist Owner: Emanuele Rocca <e...@debian.org> * Package name: prometheus-varnish-exporter Version : 0.1.0+git20160622.2.a3e-1 Upstream Author : Jonne Nauha * URL : https://github.com/jonnenauha/prometheus_varnish_exporter * License : MIT Programming Lang: Go Description : Prometheus exporter for Varnish Prometheus exporter for Varnish metrics. . prometheus-varnish-exporter scrapes the varnishstat -j JSON output on each Prometheus collect and exposes all reported metrics. Metrics with multiple backends or Varnish defined identifiers (e.g. VBE.*.happy SMA.*.c_bytes LCK.*.creat) and other metrics with similar structure (e.g. MAIN.fetch_*) are combined under a single metric name with distinguishable labels. Vanish naming conventions are preserved as much as possible to be familiar to Varnish users when building queries, while at the same time trying to following Prometheus conventions like lower casing and using _ separators.
Bug#900638: libre2-dev: missing pkg-config metadata file
Package: libre2-dev Version: 20180301+dfsg-1 Severity: normal libre2-dev does not ship re2.pc, hence pkg-config fails to locate the library (ie: `pkg-config --exists re2` fails). Please ship re2.pc by adding /usr/lib/*/pkgconfig/re2.pc to debian/libre2-dev.install.
Bug#899240: debian-installer: blank screen on boot (6th Gen. ThinkPad X1)
On Mon, 21 May 2018 15:47:20 +0300 =?UTF-8?B?TWF0dGkgUMO2bGzDpA==?= wrote: > Package: debian-installer > Severity: normal > Tags: d-i > > Dear Maintainer, > > booting to Debian Installer fails on a 6th Generation Lenovo ThinkPad > X1 (type 20KH-006MMX) with the following symptoms: > > * Boot from a Debian installation media (mini.iso 2018-05-18 on a USB > drive). Also tested with Wheezy, Jessie, Stretch and Testing amd64 > ISOs. > > * GRUB menu (version 2.02-2) shows options "Install", "Advanced > options" and "Install with speech synthesis". > > * On entering "Install", the screen goes blank. The machine is still > powered on and the keyboard leds respond to, e.g., the "mute" > button. Switching to virtual terminals does not help as the screen > appears dead. > > Similar problems with a blank screen have been reported on earlier > versions of the ThinkPad X1 (see > https://bbs.archlinux.org/viewtopic.php?id=210007) with workarounds > involving boot parameters intel_pstate=no_hwp or > intel_pstate=disable. In this case, this does not help. Also, the bug > appears on several kernel versions (from 3.16 in Jessie). > > Booting to a live environment using debian-live-9.3.0-amd64-gnome.iso > is not affected by the bug. The live system uses a full 2560x1440 > resolution on a 4.9.0-4-amd64 kernel. However, the "Install" option on > the same ISO results in a blank screen. > >
Bug#899240: debian-installer: blank screen on boot (6th Gen. ThinkPad X1)
On 21/05 03:47, Matti Pöllä wrote: > booting to Debian Installer fails on a 6th Generation Lenovo ThinkPad > X1 (type 20KH-006MMX) with the following symptoms: > > * Boot from a Debian installation media (mini.iso 2018-05-18 on a USB > drive). Also tested with Wheezy, Jessie, Stretch and Testing amd64 > ISOs. > > * GRUB menu (version 2.02-2) shows options "Install", "Advanced > options" and "Install with speech synthesis". > > * On entering "Install", the screen goes blank. The machine is still > powered on and the keyboard leds respond to, e.g., the "mute" > button. Switching to virtual terminals does not help as the screen > appears dead. This issue is reproducible if the installer is starting in UEFI mode (grub says "Debian GNU/Linux UEFI Installer menu") but CSM Support is disabled in the Thinkpad Setup screen, which is the one you access by pressing F1 at boot. Set CSM Support to "Yes" under Startup -> UEFI/Legacy Boot to get past this. Alternatively, set "UEFI/Legacy Boot" to "Legacy Only", in which case the installer will start in BIOS mode. > Booting to a live environment using debian-live-9.3.0-amd64-gnome.iso > is not affected by the bug. The live system uses a full 2560x1440 > resolution on a 4.9.0-4-amd64 kernel. However, the "Install" option on > the same ISO results in a blank screen. This might be due to the live image including i915.ko in its initrd? It seems to get loaded pretty early on, much earlier than X. To doublecheck, remove boot=live from the kernel parameters. You'll be dropped into a initramfs shell and by running lsmod you'll see that i915 is loaded already. Also I've tried booting the live image with modprobe.blacklist=i915 and it behaves exactly like the installer with CSM Support disabled (immediate blank screen).
Bug#906930: ITP: prometheus-trafficserver-exporter -- Prometheus exporter for Apache Traffic Server
Package: wnpp Severity: wishlist Owner: Emanuele Rocca * Package name: prometheus-trafficserver-exporter Version : 0.0.2 Upstream Author : Greg Dallavalle * URL : https://github.com/gdvalle/trafficserver_exporter * License : Apache-2.0 Programming Lang: Python Description : Prometheus exporter for Apache Traffic Server prometheus-trafficserver-exporter is an Apache Traffic Server metrics exporter for Prometheus. It uses the stats_over_http Traffic Server plugin to translate JSON data into Prometheus format.
Bug#892995: systemtap: failes to compile scripts, implicit declaration of some functions
Note that the failure is due to stapbpf/Makefile.am trying to add the stapusr group, and the systemtap Debian package does that in systemtap-runtime's postinst script already. Perhaps it would make sense to patch stapbpf/Makefile.am to get rid of install-exec-hook, and add a dpkg-statoverride call to systemtap-runtime.postinst for the stapbpf binary?
Bug#911836: pytest-localserver: autopkgtest needs update for new version of openssl
tag 911836 patch tag 911836 pending thanks Fix pushed to salsa: https://salsa.debian.org/python-team/modules/pytest-localserver/merge_requests/1/diffs?commit_id=bad8a656ec5383c5b8a1d1e52f75e7afbe7c8c1b
Bug#911836: pytest-localserver: autopkgtest needs update for new version of openssl
On 25/02 03:29, Sandro Tosi wrote: > Emanuele, pytest-localserver has been orphaned, so you can go ahead > and upload it if you want Done. > (and i dont think it's appropriate anymore to use the DPMT git repo, i > guess you can move it to the debian/ namespace) Also done, thanks Sandro.
Bug#890075: ruby-http ftbfs (test failures with 2.5)
On 10/02 09:47, Matthias Klose wrote: > ruby-http ftbfs for 2.5, but not for 2.3 in unstable: Note that the bug is not reproducible with ruby-http 3.3.0-2 as tests have been disabled: https://salsa.debian.org/ruby-team/ruby-http/commit/728a3fbcc7c59ebb14cb55aa9f084b910d666971 https://salsa.debian.org/ruby-team/ruby-http/commit/6ba2e142ef6952fc905ac2cac7e2eec536433ac3 Reverting the commits above makes ruby-http ftbfs in unstable.
Bug#923016: systemtap: scripts fail to compile with recent kernels
Package: systemtap
Version: 3.3-1
Severity: grave
Justification: renders package unusable
SystemTap 3.3-1 does not work with the kernel currently in sid,
linux-image-4.19.0-3-amd64 4.19.20-1.
$ sudo stap -e 'probe oneshot { println("hello world") }'
In file included from
/tmp/stapBznfoX/stap_7c11b6c20586a98b7853a74fee0e49f4_979_src.c:298:
/usr/share/systemtap/runtime/linux/stp_tracepoint.c: In function
‘stp_tracepoint_coming’:
/usr/share/systemtap/runtime/linux/stp_tracepoint.c:281:6: error: assignment
to ‘struct tracepoint *’ from ‘tracepoint_ptr_t’ {aka ‘const int’} makes
pointer from integer without a cast [-Werror=int-conversion]
tp = tp_mod->mod->tracepoints_ptrs[i];
^
/usr/share/systemtap/runtime/linux/stp_tracepoint.c: In function
‘stp_tracepoint_going’:
/usr/share/systemtap/runtime/linux/stp_tracepoint.c:323:6: error: assignment
to ‘struct tracepoint *’ from ‘tracepoint_ptr_t’ {aka ‘const int’} makes
pointer from integer without a cast [-Werror=int-conversion]
tp = tp_mod->mod->tracepoints_ptrs[i];
^
cc1: all warnings being treated as errors
make[3]: ***
[/usr/src/linux-headers-4.19.0-3-common/scripts/Makefile.build:308:
/tmp/stapBznfoX/stap_7c11b6c20586a98b7853a74fee0e49f4_979_src.o] Error 1
make[2]: *** [/usr/src/linux-headers-4.19.0-3-common/Makefile:1535:
_module_/tmp/stapBznfoX] Error 2
make[1]: *** [Makefile:146: sub-make] Error 2
make: *** [Makefile:8: all] Error 2
WARNING: kbuild exited with status: 2
Pass 4: compilation failed. [man error::pass4]
Tip: /usr/share/doc/systemtap/README.Debian should help you get started.
The latest upstream version (4.0) does however work fine. I'm gonna package it
right away to get a working SystemTap in Buster.
Bug#857973: dstat: uses network during build
tag 857973 patch
thanks
On 16/03 07:48, James Cowgill wrote:
> When running the testsuite, the ntp dstat plugin tries to get the time
> using NTP from 0.fedora.pool.ntp.org. As policy says, accessing the
> network in this way is not permitted for packages in the main archive.
Fixed by excluding ntp from --all-plugins. NMU diff attached.
diff -Nru dstat-0.7.3/debian/changelog dstat-0.7.3/debian/changelog
--- dstat-0.7.3/debian/changelog 2017-01-18 11:12:16.0 +0100
+++ dstat-0.7.3/debian/changelog 2019-02-23 02:10:18.0 +0100
@@ -1,3 +1,11 @@
+dstat (0.7.3-1.1) unstable; urgency=high
+
+ * Non-maintainer upload
+ * Fix crash in top-int plugin (closes: #852927)
+ * Exclude ntp plugin from --all-plugins, used by make test (closes: #857973)
+
+ -- Emanuele Rocca Sat, 23 Feb 2019 02:10:18 +0100
+
dstat (0.7.3-1) unstable; urgency=medium
* New upstream release (closes: #851494)
diff -Nru dstat-0.7.3/debian/patches/all_plugins_exclude_ntp_857973 dstat-0.7.3/debian/patches/all_plugins_exclude_ntp_857973
--- dstat-0.7.3/debian/patches/all_plugins_exclude_ntp_857973 1970-01-01 01:00:00.0 +0100
+++ dstat-0.7.3/debian/patches/all_plugins_exclude_ntp_857973 2019-02-23 02:10:18.0 +0100
@@ -0,0 +1,20 @@
+Description: exclude ntp from --all-plugins
+ dstat allows to specify --all-plugins, a CLI option used by `make test` for
+ testing purposes. Exclude the ntp plugin from the list as it performs network
+ access.
+Author: Emanuele Rocca
+Bug-Debian: https://bugs.debian.org/857973
+Last-Update: 2019-02-23
+
+--- dstat-0.7.3.orig/dstat
dstat-0.7.3/dstat
+@@ -177,6 +177,9 @@ class Options:
+ ### Make list unique in a fancy fast way
+ plugins = {}.fromkeys(allplugins).keys()
+ plugins.sort()
++# Do not include ntp plugin as it performs network access. See
++# https://bugs.debian.org/857973
++plugins.remove('ntp')
+ self.plugins += plugins
+ elif opt in ['--bits']:
+ self.bits = True
diff -Nru dstat-0.7.3/debian/patches/series dstat-0.7.3/debian/patches/series
--- dstat-0.7.3/debian/patches/series 2014-03-24 03:02:19.0 +0100
+++ dstat-0.7.3/debian/patches/series 2019-02-23 02:10:18.0 +0100
@@ -1 +1,3 @@
fix_629680
+top_int_plugin_852927
+all_plugins_exclude_ntp_857973
diff -Nru dstat-0.7.3/debian/patches/top_int_plugin_852927 dstat-0.7.3/debian/patches/top_int_plugin_852927
--- dstat-0.7.3/debian/patches/top_int_plugin_852927 1970-01-01 01:00:00.0 +0100
+++ dstat-0.7.3/debian/patches/top_int_plugin_852927 2019-02-23 02:08:28.0 +0100
@@ -0,0 +1,21 @@
+Description: avoid crashing in top-int plugin
+ The first intset can have less elements than the second one. Catch IndexError
+ to avoid crashing if that is the case.
+Author: Emanuele Rocca
+Bug-Debian: https://bugs.debian.org/852927
+Last-Update: 2019-02-23
+
+--- dstat-0.7.3.orig/plugins/dstat_top_int.py
dstat-0.7.3/plugins/dstat_top_int.py
+@@ -37,7 +37,10 @@ class dstat_plugin(dstat):
+ self.intset2 = [ long(int) for int in line[3:] ]
+
+ for i in range(len(self.intset2)):
+-total = (self.intset2[i] - self.intset1[i]) * 1.0 / elapsed
++try:
++total = (self.intset2[i] - self.intset1[i]) * 1.0 / elapsed
++except IndexError:
++continue
+
+ ### Put the highest value in self.val
+ if total > self.val['total']:
Bug#871285: libxmmsclient++4v5: requires rebuild against GCC 7 and symbols/shlibs bump
On 07/08 03:47, jcowg...@debian.org wrote: > - If your package does not provide a symbols file, add a dh_makeshlibs > override so that tight enough dependencies are generated. > > Using libebml as an example (debian/rules): > + override_dh_makeshlibs: > + # For new symbols when compiled with GCC 7 > + dh_makeshlibs -V'libebml4v5 (>= 1.3.4-2~)' > > Where "1.3.4-2" is the version this bug was fixed in. Done, NMU diff attached. diff -Nru xmms2-0.8+dfsg/debian/changelog xmms2-0.8+dfsg/debian/changelog --- xmms2-0.8+dfsg/debian/changelog 2017-11-16 13:54:03.0 +0100 +++ xmms2-0.8+dfsg/debian/changelog 2019-02-25 08:12:48.0 +0100 @@ -1,3 +1,11 @@ +xmms2 (0.8+dfsg-18.2) unstable; urgency=high + + * Non-maintainer upload. + * Build using GCC 8 and tighten dependency on the shared library. Closes: +#871285 + + -- Emanuele Rocca Mon, 25 Feb 2019 08:12:48 +0100 + xmms2 (0.8+dfsg-18.1) unstable; urgency=medium * Non-maintainer upload. diff -Nru xmms2-0.8+dfsg/debian/rules xmms2-0.8+dfsg/debian/rules --- xmms2-0.8+dfsg/debian/rules 2017-01-02 21:45:31.0 +0100 +++ xmms2-0.8+dfsg/debian/rules 2019-02-25 08:12:48.0 +0100 @@ -67,3 +67,7 @@ override_dh_install: dh_install --fail-missing + +override_dh_makeshlibs: + # For new symbols when compiled with GCC >= 7 + dh_makeshlibs -V'libxmmsclient++4v5 (>= 0.8+dfsg-18.2~)'
Bug#852927: dstat: FTBFS: Test failures
tag 852927 patch
thanks
On 28/01 09:25, Lucas Nussbaum wrote:
> > [7lTraceback (most recent call last):
> > File "./dstat", line 2842, in
> > main()
> > File "./dstat", line 2703, in main
> > scheduler.run()
> > File "/usr/lib/python2.7/sched.py", line 117, in run
> > action(*argument)
> > File "./dstat", line 2797, in perform
> > o.extract()
> > File "/<>/plugins/dstat_top_int.py", line 40, in extract
> > total = (self.intset2[i] - self.intset1[i]) * 1.0 / elapsed
> > IndexError: list index out of range
> > Makefile:36: recipe for target 'test' failed
Fixed in 0.7.3-1.1. NUM diff attached.
diff -Nru dstat-0.7.3/debian/changelog dstat-0.7.3/debian/changelog
--- dstat-0.7.3/debian/changelog 2017-01-18 11:12:16.0 +0100
+++ dstat-0.7.3/debian/changelog 2019-02-23 02:10:18.0 +0100
@@ -1,3 +1,11 @@
+dstat (0.7.3-1.1) unstable; urgency=high
+
+ * Non-maintainer upload
+ * Fix crash in top-int plugin (closes: #852927)
+ * Exclude ntp plugin from --all-plugins, used by make test (closes: #857973)
+
+ -- Emanuele Rocca Sat, 23 Feb 2019 02:10:18 +0100
+
dstat (0.7.3-1) unstable; urgency=medium
* New upstream release (closes: #851494)
diff -Nru dstat-0.7.3/debian/patches/all_plugins_exclude_ntp_857973 dstat-0.7.3/debian/patches/all_plugins_exclude_ntp_857973
--- dstat-0.7.3/debian/patches/all_plugins_exclude_ntp_857973 1970-01-01 01:00:00.0 +0100
+++ dstat-0.7.3/debian/patches/all_plugins_exclude_ntp_857973 2019-02-23 02:10:18.0 +0100
@@ -0,0 +1,20 @@
+Description: exclude ntp from --all-plugins
+ dstat allows to specify --all-plugins, a CLI option used by `make test` for
+ testing purposes. Exclude the ntp plugin from the list as it performs network
+ access.
+Author: Emanuele Rocca
+Bug-Debian: https://bugs.debian.org/857973
+Last-Update: 2019-02-23
+
+--- dstat-0.7.3.orig/dstat
dstat-0.7.3/dstat
+@@ -177,6 +177,9 @@ class Options:
+ ### Make list unique in a fancy fast way
+ plugins = {}.fromkeys(allplugins).keys()
+ plugins.sort()
++# Do not include ntp plugin as it performs network access. See
++# https://bugs.debian.org/857973
++plugins.remove('ntp')
+ self.plugins += plugins
+ elif opt in ['--bits']:
+ self.bits = True
diff -Nru dstat-0.7.3/debian/patches/series dstat-0.7.3/debian/patches/series
--- dstat-0.7.3/debian/patches/series 2014-03-24 03:02:19.0 +0100
+++ dstat-0.7.3/debian/patches/series 2019-02-23 02:10:18.0 +0100
@@ -1 +1,3 @@
fix_629680
+top_int_plugin_852927
+all_plugins_exclude_ntp_857973
diff -Nru dstat-0.7.3/debian/patches/top_int_plugin_852927 dstat-0.7.3/debian/patches/top_int_plugin_852927
--- dstat-0.7.3/debian/patches/top_int_plugin_852927 1970-01-01 01:00:00.0 +0100
+++ dstat-0.7.3/debian/patches/top_int_plugin_852927 2019-02-23 02:08:28.0 +0100
@@ -0,0 +1,21 @@
+Description: avoid crashing in top-int plugin
+ The first intset can have less elements than the second one. Catch IndexError
+ to avoid crashing if that is the case.
+Author: Emanuele Rocca
+Bug-Debian: https://bugs.debian.org/852927
+Last-Update: 2019-02-23
+
+--- dstat-0.7.3.orig/plugins/dstat_top_int.py
dstat-0.7.3/plugins/dstat_top_int.py
+@@ -37,7 +37,10 @@ class dstat_plugin(dstat):
+ self.intset2 = [ long(int) for int in line[3:] ]
+
+ for i in range(len(self.intset2)):
+-total = (self.intset2[i] - self.intset1[i]) * 1.0 / elapsed
++try:
++total = (self.intset2[i] - self.intset1[i]) * 1.0 / elapsed
++except IndexError:
++continue
+
+ ### Put the highest value in self.val
+ if total > self.val['total']:
Bug#929411: dstat: upstream discontinued due to reimplementation by RedHat
Hi, On 04/08 05:50, Otto Kekäläinen wrote: > There is however work now being done by Emmanuel Rocca at > https://salsa.debian.org/debian/dstat/commits/master > > I have adopted rdiff-backup now, so I don't have interest in taking on any > new packages atm, so please Emmanuel continue the good work! The package is now on salsa as you pointed out, so yeah feel free to help co-maintaining it anytime! I've sent an email to the current maintainer of dstat, Andrew Pollock, asking whether he's still interested in working on the package. Waiting a few days for a reply before starting the MIA procedure. Otto: can this bug be closed or is there any action required?
Bug#604453: #604453 reproducible way to crash the system with kernel.function("*@*/*.c")
Hi Timo, On 15/08 12:02, Timo Juhani Lindfors wrote: > just a status update, the following combination still crashes: > > systemtap 2.3-1 > linux-image-3.10-2-amd64 3.10.5-1 Running mmap-trace.stp on sid for a few minutes I could not reproduce the bug. systemtap 4.2-3 linux-image-5.4.0-4-amd64 5.4.19-1 Do you think this can be closed now or is there any work left to be done? Thanks, Emanuele
Bug#972247: Probes fail with error: ‘struct mm_struct’ has no member named mmap_sem
Package: systemtap
Version: 4.3-2
Severity: grave
With linux-image-5.8.0-3-amd64 version 5.8.14-1, stap fails as follows:
$ sudo stap -e 'probe oneshot { println("hello world") }'
[...]
/usr/share/systemtap/runtime/linux/access_process_vm.h: In function
‘__access_process_vm_’:
/usr/share/systemtap/runtime/linux/access_process_vm.h:32:19: error: ‘struct
mm_struct’ has no member named ‘mmap_sem’; did you mean ‘mmap_base’?
32 | down_read (>mmap_sem);
| ^~~~
| mmap_base
/usr/share/systemtap/runtime/linux/access_process_vm.h:87:17: error: ‘struct
mm_struct’ has no member named ‘mmap_sem’; did you mean ‘mmap_base’?
87 | up_read (>mmap_sem);
| ^~~~
| mmap_base
This upstream commit should fix the issue:
https://sourceware.org/git/?p=systemtap.git;a=commit;h=37066e2c3a9d9f48fc01b13ec0493b1c67551275
Bug#961830: systemtap: embeds build date in generated PDF files
Hi, On 29/05 04:27, Vagrant Cascadian wrote: > The generated PDF files included in the systemtap-doc package include > dates based on the build time, which breaks reproducible builds. > > The attached patch enables use of SOURCE_DATE_EPOCH, by setting > FORCE_SOURCE_DATE=1, which texlive requires in order to respect > SOURCE_DATE_EPOCH. > > https://reproducible-builds.org/docs/source-date-epoch/ Thanks for sending this patch! I've applied it and tried running a reprotest, but unfortunately the build still does not seem to be reproducible. How have you tested the change? Thanks, Emanuele
Bug#960503: xfonts-terminus: 50-enable-terminus.conf missing, fonts are not enabled
Hi Anton, On 13/05 03:16, Anton Zinoviev wrote: > On Wed, May 13, 2020 at 01:16:32PM +0200, Jochen Sprickerhof wrote: > > Severity: grave > > Justification: renders package unusable > > Well, the package is not unusable. It is usable by all X programs which > do not rely on fontconfig. It might still be usable, but the upgrade does break things for people who only have xfonts-terminus installed. > On the other hand, programs which rely on fontconfig should probably use > the fonts in fonts-terminus-otb instead of the fonts in this package. > Practically, this means that most users should install > fonts-terminus-otb instead xfonts-terminus. I think this should be explicitly communicated to users via NEWS.Debian.
Bug#969968: systemtap: FTBFS on non-linux architectures
Hi Svante, On 09/09 03:34, Svante Signell wrote: > Currently systemtap FTBFS on GNU/Hurd and GNU/kFreeBSD-any due to > several linux-specific includes in some .cxx-files and usage of > PATH_MAX, which does not exist on GNU/Hurd. Additionally, for non-linux > architectures only systemtap-common, systemtap-doc, and systemtap-sdt- > dev packages are built, according to the debian/control file. Yeah, SystemTap is very much Linux-specific and it really isn't worth the effort to build any of the systemtap binary packages on other kernels. For packages depending on systemtap-sdt-dev, I think that we should follow the approach proposed by Samuel in #970614. Thanks anyways for your patch, I appreciate it! Emanuele
Bug#977549: bpftrace: all programs fail with Segmentation fault
Package: bpftrace
Version: 0.11.3-3
Severity: grave
Justification: renders package unusable
Any attempt of running bpftrace programs fails on my sid workstation:
$ sudo bpftrace -e 'kprobe:do_nanosleep { printf("PID %d sleeping\n", pid); }'
Two passes with the same argument (-tti) attempted to be registered!
Segmentation fault
The issue isn't limited to kprobes, uprobes fail too:
$ sudo bpftrace -e 'uprobe:/bin/bash:readline { printf("Hello\n") }'
Two passes with the same argument (-tti) attempted to be registered!
Segmentation fault
Even bpftrace -V fails, though with a different error:
$ sudo bpftrace -V
bpftrace v0.11.3
free(): double free detected in tcache 2
Aborted
I'm running linux-image-5.9.0-4-amd64 5.9.11-1 and libllvm11
1:11.0.0-5+b1.
Bug#994814: nvidia-legacy-390xx-kernel-dkms: build failures on Linux 5.14
Package: nvidia-legacy-390xx-kernel-dkms
Version: 390.144-1
Severity: normal
Tags: patch
Hi,
today I've upgraded to linux-image-5.14.0-1-amd64-unsigned, and
nvidia-legacy-390xx-kernel-dkms failed to build with the following
error:
/var/lib/dkms/nvidia-legacy-390xx/390.144/build/nvidia/os-interface.c:583:18:
error: ‘struct task_struct’ has no member named ‘state’; did you mean ‘__state’?
583 | current->state = TASK_INTERRUPTIBLE;
| ^
| __state
Other than the changes to struct task_struct, the other relevant news in
Linux 5.14 is that the pdev field is now gone from struct drm_device
(see https://gist.github.com/joanbm/144a965c36fc1dc0d1f1b9be3438a368).
/var/lib/dkms/nvidia-legacy-390xx/390.144/build/nvidia-drm/nvidia-drm-drv.c:814:10:
error: ‘struct drm_device’ has no member named ‘pdev’; did you mean ‘dev’?
814 | dev->pdev = pdev;
| ^~~~
| dev
The attached changes to /usr/src/nvidia-legacy-390xx-390.144 fix the
driver with 5.14 on my workstation.
Thanks,
Emanuele
--- /usr/src/nvidia-legacy-390xx-390.144/nvidia/os-interface.c.orig 2021-09-21 10:03:57.965273627 +0200
+++ /usr/src/nvidia-legacy-390xx-390.144/nvidia/os-interface.c 2021-09-21 10:10:30.581119711 +0200
@@ -8,6 +8,8 @@
* _NVRM_COPYRIGHT_END_
*/
+#include
+
#define __NO_VERSION__
#include "nv-misc.h"
@@ -580,7 +582,11 @@
// the requested timeout has expired, loop until less
// than a jiffie of the desired delay remains.
//
+#if (LINUX_VERSION_CODE < KERNEL_VERSION(5, 14, 0))
current->state = TASK_INTERRUPTIBLE;
+#else
+WRITE_ONCE(current->__state, TASK_INTERRUPTIBLE);
+#endif
do
{
schedule_timeout(jiffies);
--- /usr/src/nvidia-legacy-390xx-390.144/nvidia/nvlink_linux.c.orig 2021-09-21 10:15:06.578262557 +0200
+++ /usr/src/nvidia-legacy-390xx-390.144/nvidia/nvlink_linux.c 2021-09-21 10:14:02.386927630 +0200
@@ -21,6 +21,7 @@
***/
+#include
#include "conftest.h"
#include "nvlink_common.h"
@@ -597,7 +598,11 @@
// the requested timeout has expired, loop until less
// than a jiffie of the desired delay remains.
//
+#if (LINUX_VERSION_CODE < KERNEL_VERSION(5, 14, 0))
current->state = TASK_INTERRUPTIBLE;
+#else
+WRITE_ONCE(current->__state, TASK_INTERRUPTIBLE);
+#endif
do
{
schedule_timeout(jiffies);
--- /usr/src/nvidia-legacy-390xx-390.144/nvidia-drm/nvidia-drm-drv.c.orig 2021-09-21 10:18:02.980433147 +0200
+++ /usr/src/nvidia-legacy-390xx-390.144/nvidia-drm/nvidia-drm-drv.c 2021-09-21 10:21:21.454372046 +0200
@@ -59,6 +59,7 @@
#include
#endif
+#include
#include
/*
@@ -811,7 +812,10 @@
dev->dev_private = nv_dev;
nv_dev->dev = dev;
+#if (LINUX_VERSION_CODE < KERNEL_VERSION(5, 14, 0))
+// Rel. commit "drm: Remove pdev field from struct drm_device" (Thomas Zimmermann, 3 May 2021)
dev->pdev = pdev;
+#endif
/* Register DRM device to DRM sub-system */
Bug#1049872: FTBFS on multiple release architectures
Control: retitle -1 asmjit: FTBFS on armel and armhf Hi Andrius, On 2023-08-28 07:42, Andrius Merkys wrote: > On Wed, 16 Aug 2023 14:29:10 +0200 Emanuele Rocca wrote: > > asmjit does not build correctly on the following architectures: > > armel, armhf, mips64el, mipsel, s390x. > > Does this constitute an RC bug? If not, severity should be lowered. It does, on armel and armhf the package did build successfully in the past. See: https://buildd.debian.org/status/logs.php?pkg=asmjit=armhf https://buildd.debian.org/status/logs.php?pkg=asmjit=armel Bug retitled given that meanwhile the issue has been fixed on mips64el, mipsel, and s390x.
Bug#1051204: O: urlview -- Extracts URLs from text
Package: wnpp I'm not really using urlview much these days. If you want to be the new maintainer, please take it. See http://www.debian.org/devel/wnpp/index.html#howto-o for detailed instructions on how to adopt a package properly. Emanuele
Bug#1010218: armnn FTCBFS: multiple reasons
Hi Helmut, On 2022-04-26 05:33, Helmut Grohne wrote: > armnn fails to cross build from source for a fair number of reasons. This does not seem to be the case anymore with 23.08-3 from testing/unstable, at least judging from sbuild --host=arm64 on a x86 machine: https://people.debian.org/~ema/armnn_23.08-3_arm64.build Any other test to perform before claiming victory? Thanks, Emanuele
Bug#1049872: FTBFS on multiple release architectures
Hello Andrius, On 2023-09-09 08:38, Andrius Merkys wrote: > This is news to me. Could you please point out where in Debian Policy I can > read more about such requirement? I thought I saw packages dropping support > for one or another release architecture without being removed from testing. See https://release.debian.org/testing/rc_policy.txt section 4 (Autobuilding). Emanuele
Bug#1021292: Enabling branch protection on amd64 and arm64
Hi Guillem, On 2023-08-31 02:12, Guillem Jover wrote: > So this happened, and Johannes reported that this seems to be breaking > cross-building. :( > > The problem, which is in fact not new, but is made way more evident > now, is that the flags used are accepted only per arch, so when > passing for example CFLAGS (the host ones) into CC_FOR_BUILD, then > that one will not know about them and fail. [...] > I'm thinking about uploading later today a workaround to disable these > flags for now when cross-building. Yeah this sounds like a good idea, thanks very much for taking care of the issue.
Bug#1050909: blhc: Please add support for -fstack-clash-protection
Package: blhc Version: 0.13-5 Severity: wishlist Hi, the flag -fstack-clash-protection has been added to the default build flags for amd64, arm64, armhf, and armel in dpkg 1.22.0. It would be great if blhc could add support for it. See https://bugs.debian.org/918914 and https://git.dpkg.org/cgit/dpkg/dpkg.git/diff/?id=11efff1bf Thanks! Emanuele
Bug#1050912: blhc: Please add support for -mbranch-protection=standard (arm64) and -fcf-protection (amd64)
Package: blhc Version: 0.13-5 Severity: wishlist Hi, the flag -mbranch-protection=standard has been added to the default build flags for arm64, and -fcf-protection for amd64, since dpkg 1.22.0. It would be great if blhc could add support for both. See https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1021292 and https://git.dpkg.org/cgit/dpkg/dpkg.git/diff/?id=8f5aca71c Thanks! Emanuele
Bug#1051200: O: fortunes-it -- Data files containing Italian fortune cookies
Package: wnpp Severity: normal 20 years after my first upload, 8 years since the last... it is high time to orphan fortunes-it. If you want to be the new maintainer, please take it -- see http://www.debian.org/devel/wnpp/index.html#howto-o for detailed instructions on how to adopt a package properly. Emanuele
Bug#1053803: debian-installer: grub2 2.12~rc1-10 on ARM64 daily installer makes linux image load fail
Control: reassign -1 grub-efi-arm64-bin Control: retitle -1 grub 2.12~rc1-10 fails loading linux on Renesas RZG2L, grub 2.06 works Hi John, thanks for the bug report! On 2023-10-11 04:15, John wrote: > The ARM64 daily installer stopped working from 19-Sep-2023 due to grub2 > 2.12~rc1-10 updates with linux image load failure. > > This was working ok on 04-Sep-2023 with grub 2.06-13 For now we've only been able to reproduce this on a Renesas RZG2L board as far as I'm aware, retitling the bug accordingly. For example, I can boot kernels with grub 2.12 on ARM systems such as the Thinkpad X13s, Macbook M1, and RPi 3B+. Also the problem is grub-specific and not limited to the installer, so I've reassigned it to the grub-efi-arm64-bin binary package. Booting with debug enabled, this is the output of a failed attempt on the Renesas board. The grub version used in this test was 2.12~rc1-10. loader/efi/linux.c:101:linux: UEFI stub kernel: loader/efi/linux.c:102:linux: PE/COFF header @ 0040 loader/efi/linux.c:128:linux: LoadFile2 initrd loading enabled loader/efi/linux.c:495:linux: kernel file size: 34445248 loader/efi/linux.c:497:linux: kernel numpages: 8410 loader/efi/linux.c:514:linux: kernel @ 0xb6b43000 loader/efi/linux.c:416:linux: Using LoadFile2 initrd loading protocol loader/efi/peimage.c:242:linux: PE-COFF header checked loader/efi/peimage.c:316:linux: sections loaded loader/efi/peimage.c:518:linux: no relocations loader/efi/linux.c:213:linux: linux command line: 'BOOT_IMAGE=/linux' error: image not loaded. This instead is grub 2.12~rc1-11 succeeding on a RPi: loader/efi/linux.c:101:linux: UEFI stub kernel: loader/efi/linux.c:102:linux: PE/COFF header @ 0040 loader/efi/linux.c:128:linux: LoadFile2 initrd loading enabled loader/efi/linux.c:495:linux: kernel file size: 34510784 loader/efi/linux.c:497:linux: kernel numpages: 8426 loader/efi/linux.c:514:linux: kernel @ 0x2c92 loader/efi/linux.c:416:linux: Using LoadFile2 initrd loading protocol loader/efi/peimage.c:200:linux: PE-COFF header checked loader/efi/peimage.c:276:linux: sections loaded loader/efi/peimage.c:478:linux: no relocations loader/efi/linux.c:213:linux: linux command line: 'BOOT_IMAGE=/install.amd64/vmlinuz --- quiet' loader/efi/linux.c:233:linux: starting image 0x351cf518
Bug#1035477: installation-reports: grub or kernel of D-I image hangs on Thinkpad X13s after "EFI stub: Exiting boot services..."
Hi Axel, On 2023-10-10 01:45, Axel Beckert wrote: > I tried that, installer ran through fine, grub boots from disk after > installation, kernel loads initramfs and then falls into the initramfs > prompt and fractions of a second later (sometimes even beforehand) the > whole screen goes black and then nothing helps then pressing the power > button for about 10 seconds. This sounds like you might have missed the wiki step "Add qnoc-sc8280xp module to initramfs": https://wiki.debian.org/InstallingDebianOn/Thinkpad/X13s > And I can easily install tons of packages when I boot from the > installer USB stick into the rescue mode and chroot into the > installation on disk. OK then once you chroot into the installed system you should be able to check if qnoc-sc8280xp is in /etc/initramfs-tools/modules. If not, echo qnoc-sc8280xp >> /etc/initramfs-tools/modules update-initramfs -u -k all To triple-check that the needed module is in there: zstdcat /initrd.img | cpio -itv | grep qnoc-sc8280xp.ko In any case, the daily netinst image should now work! There's no need to manually copy any firmware and similar shenanigans. If you have the time, please follow the InstallingDebianOn/Thinkpad/X13s page again from the begingging to the end (quite a few things have changed) and let me know if that works for you. Thanks, Emanuele
Bug#1054583: dpkg-dev: really enable -fstack-clash-protection on armhf/armel
Hi Guillem, On 2023-10-27 04:33, Guillem Jover wrote: > Checking now again, I realize Wookey mentioned enabling this for the 3 > arm arches (those would be arm64, armhf and armel), so the patch I > provided would match that. But I was wondering now what about armeb and > arm64ilp32? I mean, I assume those should be excluded for now as they > did not get any testing, and they might not even be used/lively(?), Correct, there has been no testing done on armeb/arm64ilp32 as far as I'm aware. I'd suggest enabling the feature only on armhf/armel for the time being. Thank you for looking into this so quickly! Emanuele
Bug#1055211: bookworm-pu: package gcc-12/12.2.0-14+deb12u1 (CVE-2023-4039)
-12.2.0/debian/changelog 2023-01-08 10:12:42.0 +0100
+++ gcc-12-12.2.0/debian/changelog 2023-10-09 11:45:48.0 +0200
@@ -1,3 +1,9 @@
+gcc-12 (12.2.0-14+deb12u1) bookworm; urgency=medium
+
+ * Fix -fstack-protector handling of overflows on AArch64 (CVE-2023-4039).
+
+ -- Emanuele Rocca Mon, 09 Oct 2023 11:45:48 +0200
+
gcc-12 (12.2.0-14) unstable; urgency=medium
* Update to git 20230108 from the gcc-12 branch.
diff -Nru gcc-12-12.2.0/debian/patches/CVE-2023-4039.diff
gcc-12-12.2.0/debian/patches/CVE-2023-4039.diff
--- gcc-12-12.2.0/debian/patches/CVE-2023-4039.diff 1970-01-01
01:00:00.0 +0100
+++ gcc-12-12.2.0/debian/patches/CVE-2023-4039.diff 2023-09-21
10:08:42.0 +0200
@@ -0,0 +1,1665 @@
+DP: Fix CVE-2023-4039.
+DP:
+DP: The patch includes the following upstream commits:
+DP:
+DP: aarch64: Use local frame vars in shrink-wrapping code
+DP: 62fbb215cc817e9f2c1ca80282a64f4ee30806bc
+DP:
+DP: aarch64: Avoid a use of callee_offset
+DP: 12a8889de169f892d2e927584c00d20b8b7e456f
+DP:
+DP: aarch64: Explicitly handle frames with no saved registers
+DP: 03d5e89e7f3be53fd7142556e8e0a2774c653dca
+DP:
+DP: aarch64: Add bytes_below_saved_regs to frame info
+DP: 49c2eb7616756c323b7f6b18d8616ec945eb1263
+DP:
+DP: aarch64: Add bytes_below_hard_fp to frame info
+DP: 34081079ea4de0c98331843f574b5f6f94d7b234
+DP:
+DP: aarch64: Tweak aarch64_save/restore_callee_saves
+DP: 187861af7c51db9eddc6f954b589c121b210fc74
+DP:
+DP: aarch64: Only calculate chain_offset if there is a chain
+DP: 2b983f9064d808daf909bde1d4a13980934a7e6e
+DP:
+DP: aarch64: Rename locals_offset to bytes_above_locals
+DP: 0a0a824808d1dec51004fb5805c1a0ae2a35433f
+DP:
+DP: aarch64: Rename hard_fp_offset to bytes_above_hard_fp
+DP: 3fbf0789202b30a67b12e1fb785c7130f098d665
+DP:
+DP: aarch64: Tweak frame_size comment
+DP: aac8b31379ac3bbd14fc6427dce23f56e54e8485
+DP:
+DP: aarch64: Measure reg_offset from the bottom of the frame
+DP: 8d5506a8aeb8dd7e8b209a3663b07688478f76b9
+DP:
+DP: aarch64: Simplify top of frame allocation
+DP: b47766614df3b9df878262efb2ad73aaac108363
+DP:
+DP: aarch64: Minor initial adjustment tweak
+DP: 08f71b4bb28fb74d20e8d2927a557e8119ce9f4d
+DP:
+DP: aarch64: Tweak stack clash boundary condition
+DP: f22315d5c19e8310e4dc880fd509678fd291fca8
+DP:
+DP: aarch64: Put LR save probe in first 16 bytes
+DP: 15e18831bf98fd25af098b970ebf0c9a6200a34b
+DP:
+DP: aarch64: Simplify probe of final frame allocation
+DP: c4f0e121faa36342f1d21919e54a05ad841c4f86
+DP:
+DP: aarch64: Explicitly record probe registers in frame info
+DP: 6f0ab0a9f46a17b68349ff6035aa776bf65f0575
+DP:
+DP: aarch64: Remove below_hard_fp_saved_regs_size
+DP: 8254e1b9cd500e0c278465a3657543477e9d1250
+DP:
+DP: aarch64: Make stack smash canary protect saved registers
+DP: 75c37e031408262263442f5b4cdb83d3777b6422
+DP:
+DP: aarch64: Fix return register handling in untyped_call
+DP: 38d0605ac8bc90324170041676fc05e7e595769e
+DP:
+DP: aarch64: Fix loose ldpstp check [PR111411]
+DP: 74f99f1adc696f446115f36974a3f94f66294a53
+
+Index: gcc-12-12.2.0/src/gcc/config/aarch64/aarch64.cc
+===
+--- gcc-12-12.2.0.orig/src/gcc/config/aarch64/aarch64.cc
gcc-12-12.2.0/src/gcc/config/aarch64/aarch64.cc
+@@ -8070,18 +8070,32 @@ aarch64_needs_frame_chain (void)
+ return aarch64_use_frame_pointer;
+ }
+
++/* Return true if the current function should save registers above
++ the locals area, rather than below it. */
++
++static bool
++aarch64_save_regs_above_locals_p ()
++{
++ /* When using stack smash protection, make sure that the canary slot
++ comes between the locals and the saved registers. Otherwise,
++ it would be possible for a carefully sized smash attack to change
++ the saved registers (particularly LR and FP) without reaching the
++ canary. */
++ return crtl->stack_protect_guard;
++}
++
+ /* Mark the registers that need to be saved by the callee and calculate
+the size of the callee-saved registers area and frame record (both FP
+and LR may be omitted). */
+ static void
+ aarch64_layout_frame (void)
+ {
+- poly_int64 offset = 0;
+ int regno, last_fp_reg = INVALID_REGNUM;
+ machine_mode vector_save_mode = aarch64_reg_save_mode (V8_REGNUM);
+ poly_int64 vector_save_size = GET_MODE_SIZE (vector_save_mode);
+ bool frame_related_fp_reg_p = false;
+ aarch64_frame = cfun->machine->frame;
++ poly_int64 top_of_locals = -1;
+
+ frame.emit_frame_chain = aarch64_needs_frame_chain ();
+
+@@ -8148,11 +8162,18 @@ aarch64_layout_frame (void)
+ && !crtl->abi->clobbers_full_reg_p (regno))
+ frame.reg_offset[regno] = SLOT_REQUIRED;
+
+- /* With stack-clash, LR must be saved in non-leaf functions. The saving of
+- LR counts as an implicit probe which allows us to maintain the invariant
+- described in the comment at expand_prologue. */
+- gcc_assert (crtl->is_leaf
Bug#1053503: Enable support for Renesas RZ/V2L, RZ/G2UL, and RZ/V2M
Hi! On 2023-10-05 10:05, John wrote: > CONFIG_ARCH_R9A07G054=y > CONFIG_ARCH_R9A07G043=y > CONFIG_ARCH_R9A09G011=y The changes have been merged into master some time ago already: https://salsa.debian.org/kernel-team/linux/-/merge_requests/867 Salvatore: what is the best way to ensure this makes its way into the next upload to sid? Should I open a new MR against sid, or can you just cherry-pick commit 87656545c ? Emanuele
Bug#1053503: Enable support for Renesas RZ/V2L, RZ/G2UL, and RZ/V2M
Hi Salvatore, On 2023-11-04 09:57, Salvatore Bonaccorso wrote: > I'm not sure this is really that urgent, 6.5.10 will be EOL upstream > at some point and in master branch Bastian et all are prearing the 6.6 > based once. After an extra round in experimental I would expect it > will now not take too much longer to have a version including this > change as well in unstable. Ah yeah that sounds good. Thanks! Emanuele
Bug#1055069: please enable SC8280XP sound modules
Hi! On Mon, Oct 30, 2023 at 07:54:25PM +0100, Vincent Blut wrote: > Le 2023-10-30 20:30, Dmitry Baryshkov a écrit : > > Package: src:linux > > Version: 6.5.8-1 > > Severity: normal > > > > Please enable the following options as modules to enable audio support > > on Lenovo X13s platform: > > > > CONFIG_SND_SOC_SC8280XP > > CONFIG_SC_LPASSCC_8280XP > > Emanuele, as you’re working on support for the Lenovo X13s platform, could you > please comment on that? Looks good, I've opened https://salsa.debian.org/kernel-team/linux/-/merge_requests/880 Emanuele
Bug#1055069: please enable SC8280XP sound modules
Hi Dmitry! On 2023-10-31 02:17, Dmitry Baryshkov wrote: > BTW, Emanuele, are you by chance responsible for the X13s wiki page? I started it, but most of the useful content has been provided by someone else. :-) See https://wiki.debian.org/InstallingDebianOn/Thinkpad/X13s?action=info > There are several corrections that I'd like to suggest. It's a wiki, please feel free to contribute your improvements directly. Emanuele
Bug#1015871: Please enable CONFIG_PCI_P2PDMA
Hi Uwe, On 2023-10-24 06:48, Uwe Kleine-König wrote: > I hesitate to actually enable it because I don't understand PCI good > enough to judge it's a safe choice for the Debian kernel. I am also not familiar with the details, but I see that PCI_P2PDMA is 'y' on both Fedora Server 38 and openSUSE Tumbleweed so probably it's not particularly unsafe. If we decide to switch it on, let's do it for arm64 too. Emanuele
Bug#1054583: dpkg-dev: really enable -fstack-clash-protection on armhf/armel
Package: dpkg-dev
Version: 1.22.0
Severity: normal
Tag: patch
Hi,
-fstack-clash-protection is supposed to be enabled by default on amd64,
arm64, armhf, and armel since dpkg 1.22.0:
https://git.dpkg.org/cgit/dpkg/dpkg.git/diff/?id=11efff1bf
However, due to an issue in the following conditional in
scripts/Dpkg/Vendor/Debian.pm, the flag is only on for amd64 and arm64:
if (none { $cpu eq $_ } qw(amd64 arm64 armhf armel)) {
The value of $cpu is "arm" for both armhf and armel. Please change the
line above to:
if (none { $cpu eq $_ } qw(amd64 arm64 arm)) {
Thanks!
Emanuele
Bug#1052693: live-manual-pdf: PDF manual is unreadable
Package: live-manual-pdf Version: 2:20151217.2 Severity: important Dear Maintainer, All files under /usr/share/doc/live-manual/pdf/ seem to be broken. Screenshot of `evince /usr/share/doc/live-manual/pdf/live-manual.portrait.en.a4.pdf.gz` attached. I've also tried decompressing the file to rule out any issues with that, still there's no readable output in the resulting PDF. Emanuele
Bug#1053457: live-build: Building live image fails when unmounting /sys: 'target is busy'
Package: live-build Version: 1:20230502 Severity: normal Dear Maintainer, Building a live image with `lb build` fails towards the end with the following error: P: Begin unmounting /sys... umount: /tmp/sid-image/chroot/sys: target is busy. E: An unexpected failure occurred, exiting... The issue can be reproduced as follows: lb config --distribution sid --updates false --archive-areas 'main non-free-firmware' --bootloaders grub-efi echo live-task-lxde > config/package-lists/desktop.list.chroot lb build --debug
Bug#1054210: shim: "Synchronous Abort" error due to wrong LogError invocation
Source: shim
Version: 15.7-1
Severity: important
Tags: patch, upstream
Dear Maintainer,
shim 15.7-1 fails on some systems with the following error (visible with
SHIM_VERBOSE enabled):
mok.c:298:mirror_one_esl() 0040 e1 06 49 f2 69 9f 41 f4 31 13 88 20 XX
XX XX XX |..I.i.A.1.. |
mok.c:296:mirror_one_esl() SetVariable("MokListXRT74", ... varsz=0x4C) = Out
of Resources
"Synchronous Abort" handler, esr 0x9606
The problem is due to an extra argument passed to LogError, and it is
know upstream. A patch is available but it has not been merged yet:
https://github.com/rhboot/shim/pull/577
Bug#1049884: birdtray: FTBFS on armhf, armel, mipsel due to thunderbird build-dep
Hi Adam, On 2023-08-16 05:14, Adam Borowski wrote: > This is not a regression, thus why would it be a bug? Well FTBFS is a bug isn't it? :-) > There's nothing in birdtray itself that would prevent it from being built on > these architectures the moment problems in thunderbird are resolved Why does birdtray build-depend on thunderbird? It seems to build perfectly fine in a clean armhf chroot without it. Cheers, Emanuele
Bug#1041249: cpp-httplib: FTBFS on s390x: ../test/test.cc:5462: Failure
Control: retitle -1 cpp-httplib: FTBFS on s390x, armhf due to flaky tests Hi, On 2023-07-24 04:26, Andrea Pappacoda wrote: > I've looked into this, but I couldn't find any change which would > cause test failures on s390x specifically. cpp-httplib's test suite > is a bit flaky though, so it may have been just an unlucky run (this > is an issue in itself, but I have already reported it upstream and it > didn't get much attention). Is it possible to re-try the build? I've bumped into a very similar failure on armhf too, so the problem is probably not s390x-specific. Note that the build succeeded on a second try. [--] 3 tests from HostAndPortPropertiesTest [ RUN ] HostAndPortPropertiesTest.NoSSL [ OK ] HostAndPortPropertiesTest.NoSSL (0 ms) [ RUN ] HostAndPortPropertiesTest.NoSSLWithSimpleAPI [ OK ] HostAndPortPropertiesTest.NoSSLWithSimpleAPI (0 ms) [ RUN ] HostAndPortPropertiesTest.SSL [ OK ] HostAndPortPropertiesTest.SSL (0 ms) [--] 3 tests from HostAndPortPropertiesTest (0 ms total) [--] 2 tests from SSLClientTest [ RUN ] SSLClientTest.UpdateCAStore [ OK ] SSLClientTest.UpdateCAStore (0 ms) [ RUN ] SSLClientTest.ServerCertificateVerification4 ../test/test.cc:4808: Failure Value of: res Actual: false Expected: true == Summary of Failures: 1/1 main TIMEOUT900.20s killed by signal 15 SIGTERM Ok: 0 Expected Fail: 0 Fail: 0 Unexpected Pass:0 Skipped:0 Timeout:1 dh_auto_test: error: cd obj-arm-linux-gnueabihf && LC_ALL=C.UTF-8 MESON_TESTTHREADS=8 meson test --timeout-multiplier=3 --test-args=--gtest_filter=-\*_Online:\*ClientProblemDetectionTest\* returned exit code 1 make[1]: *** [debian/rules:42: override_dh_auto_test] Error 25 make[1]: Leaving directory '/<>'
Bug#1049884: birdtray: FTBFS on armhf, armel, mipsel due to thunderbird build-dep
Hi! On 2023-08-21 07:36, Adam Borowski wrote: > On Mon, Aug 21, 2023 at 10:38:52AM +0200, Emanuele Rocca wrote: > > Well FTBFS is a bug isn't it? :-) > > A FTBFS on an architecture that has built before (and hasn't been RMed) > is a bug, and one that's policied as high severity. As far as I understand that is the case for birdtray on all 3 architectures? It used to build fine in the past, now it does not: https://buildd.debian.org/status/fetch.php?pkg=birdtray=mipsel=1.4-2=1547097073=0 > Obviously we'd prefer thunderbird:armhf to be a thing, but unless/until it > can be fixed, talk about thunderbird addons on armhf is quite moot. Agreed. > > Why does birdtray build-depend on thunderbird? It seems to build > > perfectly fine in a clean armhf chroot without it. > Build yes, work no. The result would be a pointless package you can't > use; adding this (otherwise superfluous) build-dependency avoids > having a non-installable package in the archive. Given that we know that birdtray does not work on armhf, armel, and mipsel, the Architecture field should reflect this fact I think. And yes I understand that in a hypothetical scenario in which thunderbird works on those arches, birdtray works too. That's not the present reality though and it seems more accurate to state this fact explicitly instead of implying it with a superfluous uninstallable build-dep. >From >https://www.debian.org/doc/debian-policy/ch-controlfields.html#architecture: | Specifying a list of architectures or architecture wildcards indicates | that the source will build an architecture-dependent package, and will | only work correctly on the listed or matching architectures. Cheers, Emanuele
Bug#1049346: Debian OS ARM64: Please enable support for Renesas RZ/G2L-SMARC
Hi, On 2023-08-14 01:16, John Vincent wrote: > The RZ/G2L SMARC is the reference board for the Renesas RZ/G2L MPU: > https://renesas.info/wiki/RZ-G/RZ-G2L_SMARC > > I think the following few configuration options in > debian/config/arm64/config are missing to run Debian on this board. > > For SoC support: > > CONFIG_ARCH_R9A07G044=y > > For USB2 support: > > CONFIG_RESET_RZG2L_USBPHY_CTRL=m I've opened a merge request here: https://salsa.debian.org/kernel-team/linux/-/merge_requests/809 Emanuele
Bug#918914: add -fstack-clash-protection to default buildflags
Hi! On 2019-01-29 09:56, Guillem Jover wrote: > Given its arch-dependent behavior this might need more exposure than a > simple rebuild on say amd64. Enabling this at the beginning of a > release cycle might seem more appropriate. Lucas performed a full archive rebuild on arm64 with -fstack-clash-protection and the results look good: http://qa-logs.debian.net/2023/08/11.stackclash-arm/ Please enable -fstack-clash-protection on arm64 too.
Bug#1050216: cpu-features: FTBFS on armhf, armel "Including cpuinfo_aarch64.h from a non-aarch64 target"
Source: cpu-features Version: 0.7.0-1 Severity: serious Tags: sid trixie ftbfs User: debian-...@lists.debian.org Usertags: armhf armel Hi, cpu-features fails to build on armhf and armel with the following error: In file included from /<>/test/cpuinfo_aarch64_test.cc:15: /<>/test/../include/cpuinfo_aarch64.h:155:2: error: #error "Including cpuinfo_aarch64.h from a non-aarch64 target." 155 | #error "Including cpuinfo_aarch64.h from a non-aarch64 target." | ^ make[3]: *** [test/CMakeFiles/cpuinfo_aarch64_test.dir/build.make:79: test/CMakeFiles/cpuinfo_aarch64_test.dir/cpuinfo_aarch64_test.cc.o] Error 1 make[3]: Leaving directory '/<>/obj-arm-linux-gnueabi' make[2]: *** [CMakeFiles/Makefile2:1400: test/CMakeFiles/cpuinfo_aarch64_test.dir/all] Error 2
Bug#1050216: cpu-features: FTBFS on armhf, armel "Including cpuinfo_aarch64.h from a non-aarch64 target"
Hi! On 2023-08-22 04:42, Shengjing Zhu wrote: > I can't reproduce it on abel.debian.org > https://db.debian.org/machines.cgi?host=abel > I assume you are cross building, or running it on an armhf/armel > container on arm64 host. Ah yes, good catch, I'm building on a arm64 host with: sbuild --arch=armhf Note that building 0.7.0-1 with `Machine Architecture: arm64` worked in the past, see: https://buildd.debian.org/status/fetch.php?pkg=cpu-features=armhf=0.7.0-1=1655403767=0
Bug#1049876: bbhash: FTBFS on 32 bit architectures
Source: bbhash Version: 1.0.0-5 Severity: serious Tags: sid trixie ftbfs Hi, bbhash does not build correctly on the following 32 bit architectures: armel, armhf, i386, mipsel. g++ -o example_custom_hash example_custom_hash.cpp -O3 -std=c++11 -lpthread In file included from example.cpp:1: BooPHF.h: In function ‘uint64_t boomphf::fastrange64(uint64_t, uint64_t)’: BooPHF.h:817:37: error: ‘__uint128_t’ was not declared in this scope; did you mean ‘__uint8_t’? 817 | return (uint64_t)(((__uint128_t)word * (__uint128_t)p) >> 64); | ^~~ | __uint8_t [...] See https://buildd.debian.org/status/fetch.php?pkg=bbhash=armel=1.0.0-5=1685880628=0
