Bug#869659: salt-common: Missing Dependency: python-msgpack
Package: salt-common Version: 2016.11.2+ds-1 Severity: important Dear Maintainer, I just did a minimal installation of Debian to configure it completely using salt. I was following the instructions for a masterless salt setup [1], except for installing `salt-common` instead of using their recommended bootstrapping script. [1] https://docs.saltstack.com/en/2016.11/topics/tutorials/quickstart.html After putting a minimal configuration in place, I invoked `salt-call` with the appropriate arguments, but it failed with this being the last two lines displayed: File "/usr/lib/python2.7/dist-packages/salt/transport/frame.py", line 7, in import msgpack ImportError: No module named msgpack So I installed `python-msgpack` and everything works fine. It looks like that dependency should be added to the `salt-common` package. Thank you very much, Sven -- System Information: Debian Release: 9.1 APT prefers stable APT policy: (500, 'stable') Architecture: amd64 (x86_64) Kernel: Linux 4.9.0-3-amd64 (SMP w/2 CPU cores) Locale: LANG=de_DE.UTF-8, LC_CTYPE=de_DE.UTF-8 (charmap=UTF-8), LANGUAGE=de_DE.UTF-8 (charmap=UTF-8) Shell: /bin/sh linked to /bin/dash Init: systemd (via /run/systemd/system) Versions of packages salt-common depends on: ii python2.7.13-2 ii python-apt1.4.0~beta3 ii python-dateutil 2.5.3-2 ii python-jinja2 2.8-1 ii python-pkg-resources 33.1.1-1 ii python-requests 2.12.4-1 ii python-tornado4.4.3-1 ii python-yaml 3.12-1 Versions of packages salt-common recommends: ii lsb-release 9.20161125 ii python-croniter 0.3.12-2 Versions of packages salt-common suggests: pn python-mako pn salt-doc -- no debconf information
Bug#796651: ooniprobe: package cannot be purged
Package: ooniprobe Severity: important Steps to reproduce: 1. Install ooniprobe 2. Let it run for a while 3. Try to purge it Expected result: 4. Package was purged from the computer Actual result: 4. The postrm script yields an error and aborts. The package is not completely removed: $ LC_ALL=C sudo apt-get remove --purge ooniprobe Reading package lists... Done Building dependency tree Reading state information... Done The following packages will be REMOVED: ooniprobe* 0 upgraded, 0 newly installed, 1 to remove and 0 not upgraded. After this operation, 0 B of additional disk space will be used. Do you want to continue? [Y/n] (Reading database ... 31254 files and directories currently installed.) Removing ooniprobe (1.3.1-1) ... Purging configuration files for ooniprobe (1.3.1-1) ... rmdir: failed to remove '/var/lib/ooni': No such file or directory dpkg: error processing package ooniprobe (--purge): subprocess installed post-removal script returned error exit status 1 Errors were encountered while processing: ooniprobe E: Sub-process /usr/bin/dpkg returned an error code (1) $ Please wrap the rmdir call into an if statement that checks whether the folder exists (as it seems dpkg removed it already). -- System Information: Debian Release: 8.1 APT prefers stable APT policy: (500, 'stable') Architecture: amd64 (x86_64) Foreign Architectures: i386 Kernel: Linux 2.6.32-042stab108.5 (SMP w/1 CPU core) Locale: LANG=de_DE.UTF-8, LC_CTYPE=de_DE.UTF-8 (charmap=UTF-8) Shell: /bin/sh linked to /bin/dash Init: systemd (via /run/systemd/system)
Bug#771337: init-scripts: iptables-persistent initialized after psad
Package: general Severity: important I installed the psad in order to detect port scanning attempts and – according to the recommendations from https://wiki.debian.org/iptables – installed my initial set of rule to be loaded by iptables-persistent. However, in the init script order, psad has priority 20 and iptables-persistent has 37, which will trigger a warning email because psad does not find the logging rules in iptables when it starts. My expectation would be that iptables-persistent gets initialized before psad. Kind regards, Sven -- System Information: Debian Release: 7.7 APT prefers stable APT policy: (500, 'stable') Architecture: amd64 (x86_64) Kernel: Linux 2.6.32-042stab093.5 (SMP w/2 CPU cores) Locale: LANG=de_DE.UTF-8, LC_CTYPE=de_DE.UTF-8 (charmap=UTF-8) Shell: /bin/sh linked to /bin/dash -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#770652: initscript: status command always exits with code 1
Package: psad Version: 2.2-3.1 Severity: important Running the status script always returns the exit code 1 on my system (with detected scan attempts). The return code should conform the the return codes of other scripts (e.g. nginx, apache) to make sure other systems can invoke 'invoke-rc.d psad status' in order to check if the daemon is running. This currently has a negative impact on maintenance tools like saltstack (packages salt-minion, salt-master). Right now, salt always claims that there is a need to start the psad service, even if it's running already. -- System Information: Debian Release: 7.7 APT prefers stable APT policy: (500, 'stable') Architecture: amd64 (x86_64) Foreign Architectures: i386 Kernel: Linux 2.6.32-042stab092.3 (SMP w/1 CPU core) Locale: LANG=de_DE.UTF-8, LC_CTYPE=de_DE.UTF-8 (charmap=UTF-8) Shell: /bin/sh linked to /bin/dash Versions of packages psad depends on: ii bsd-mailx [mailx] 8.1.2-0.2006cvs-1 ii exim4-daemon-light [mail-transport-agent] 4.80-7+deb7u1 ii iptables 1.4.14-3.1 ii libc6 2.13-38+deb7u6 ii libcarp-clan-perl 6.04-1 ii libdate-calc-perl 6.3-1 ii libiptables-chainmgr-perl 1.2-1 ii libiptables-parse-perl 1.1-1 ii libnet-ip-perl 1.25-3 ii libunix-syslog-perl1.1-2+b2 ii lsb-base 4.1+Debian8+deb7u1 ii perl 5.14.2-21+deb7u2 ii psmisc 22.19-1+deb7u1 ii rsyslog [system-log-daemon]7.6.3-2~bpo70+1 ii whois 5.1.1~deb7u1 psad recommends no packages. Versions of packages psad suggests: pn bastille none pn fwsnort none -- Configuration Files: /etc/psad/psad.conf changed [not included] -- no debconf information -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#770164: php5: /usr/lib/php5/sessionclean broken: passes incompatible argument to sed
Package: php5
Version: 5.4.35-0+deb7u1
Severity: serious
Tags: security
Justification: Policy 10.4
With the latest update of the php5-package, the session cleaning script is
broken. As
I'm unfamiliar with the session cleaning implementation, I guess this might
cause a
security issue by potentially not deleting session information that should be
deleted.
Here's some debugging information from manually running the script that is run
by
the cron job.
root@vm-b:~# set -x
root@vm-b:~# . /usr/lib/php5/sessionclean /var/lib/php5
$(/usr/lib/php5/maxlifetime)
++ /usr/lib/php5/maxlifetime
+ . /usr/lib/php5/sessionclean /var/lib/php5 24
++ '[' -x /usr/bin/lsof ']'
++ xargs -0i echo touch -c -h ''\''{}'\'''
++ sed -zne 's/^n//p'
sed: invalid option -- 'z'
Usage: sed [OPTION]... {script-only-if-no-other-script} [input-file]...
-n, --quiet, --silent
suppress automatic printing of pattern space
-e script, --expression=script
add the script to the commands to be executed
-f script-file, --file=script-file
add the contents of script-file to the commands to be
executed
--follow-symlinks
follow symlinks when processing in place
-i[SUFFIX], --in-place[=SUFFIX]
edit files in place (makes backup if extension supplied)
-l N, --line-length=N
specify the desired line-wrap length for the `l' command
--posix
disable all GNU extensions.
-r, --regexp-extended
use extended regular expressions in the script.
-s, --separate
consider files as separate rather than as a single continuous
long stream.
-u, --unbuffered
load minimal amounts of data from the input files and flush
the output buffers more often
--help display this help and exit
--version output version information and exit
If no -e, --expression, -f, or --file option is given, then the first
non-option argument is taken as the sed script to interpret. All
remaining arguments are names of input files; if no input files are
specified, then the standard input is read.
GNU sed home page: http://www.gnu.org/software/sed/.
General help using GNU software: http://www.gnu.org/gethelp/.
++ /usr/bin/lsof -w -l +d /var/lib/php5 -F0
++ find /var/lib/php5 -depth -mindepth 1 -maxdepth 1 -ignore_readdir_race
-type f -cmin +24 -delete
-- System Information:
Debian Release: 7.7
APT prefers stable
APT policy: (500, 'stable')
Architecture: amd64 (x86_64)
Kernel: Linux 2.6.32-042stab092.3 (SMP w/1 CPU core)
Locale: LANG=en_GB.UTF-8, LC_CTYPE=en_GB.UTF-8 (charmap=UTF-8)
Shell: /bin/sh linked to /bin/dash
Versions of packages php5 depends on:
ii libapache2-mod-php5 5.4.35-0+deb7u1
ii php5-cgi 5.4.35-0+deb7u1
ii php5-common 5.4.35-0+deb7u1
php5 recommends no packages.
php5 suggests no packages.
-- no debconf information
--
To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org
with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#770222: icecast2: on-connect scripts: icecast can leak output to attentive sources
Package: icecast2 Version: 2.4.0-1~bpo70+1 Severity: critical Tags: security upstream Justification: root security hole Icecast can leak the output of on-connect scripts to source clients by sending their output via HTTP. This information-disclosure can contain confidential information if the administrator of the icecast server did not explicitly check the output of their scripts. Information contained can include passwords or script interna helping to possibly exploit weak scripts. This bug has been reported upstream [1] which fixed it quickly in the bugfix release 2.4.1 [2]. Please consider upgrading to the latest upstream version. [1] https://trac.xiph.org/ticket/2089 [2] http://icecast.org/news/icecast-release-2_4_1/ -- System Information: Debian Release: 7.7 APT prefers stable APT policy: (500, 'stable') Architecture: amd64 (x86_64) Kernel: Linux 3.2.41-042stab094.7 (SMP w/2 CPU cores) Locale: LANG=de_DE.UTF-8, LC_CTYPE=de_DE.UTF-8 (charmap=UTF-8) Shell: /bin/sh linked to /bin/dash Versions of packages icecast2 depends on: ii adduser3.113+nmu3 ii debconf [debconf-2.0] 1.5.49 ii libc6 2.13-38+deb7u6 ii libcurl3-gnutls7.26.0-1+wheezy11 ii libogg01.3.0-4 ii libspeex1 1.2~rc1-7 ii libtheora0 1.1.1+dfsg.1-3.1 ii libvorbis0a1.3.2-1.3 ii libxml22.8.0+dfsg1-7+wheezy2 ii libxslt1.1 1.1.26-14.1 icecast2 recommends no packages. Versions of packages icecast2 suggests: pn ices2 none -- Configuration Files: /etc/default/icecast2 changed [not included] /etc/icecast2/icecast.xml [Errno 13] Keine Berechtigung: u'/etc/icecast2/icecast.xml' -- debconf information excluded -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#764916: bar: typo in man page
Package: bar Version: 1.11.0+debian-4 Severity: minor Tags: upstream Hi, there is a bug in the man page of bar which says: Wait for the fist byte of data before displaying anything. I guess this is supposed to be “Wait for the first byte[…]”. Kind regards, Sven -- System Information: Debian Release: 7.6 APT prefers stable APT policy: (500, 'stable') Architecture: amd64 (x86_64) Kernel: Linux 3.2.41-042stab085.17 (SMP w/2 CPU cores) Locale: LANG=de_DE.UTF-8, LC_CTYPE=de_DE.UTF-8 (charmap=UTF-8) Shell: /bin/sh linked to /bin/dash Versions of packages bar depends on: ii libc6 2.13-38+deb7u4 bar recommends no packages. bar suggests no packages. -- no debconf information -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#750459: New Patch (less inversive)
Hi, I realized this bug/patch already exist. Here is a patch that I did before finding this ticket. It just reuses the existing method for testing and – to me – seems to be the most straight-forward implementation of this feature. However, this patch has been generated against the version that’s currently shipped in wheezy-backports (1.5.4-1~bpo70+2). Kind regards, Sven Herzberg PS: Does it make sense to open a new bug report for the “conf.d” configuration scheme, instead of having these two different feature requests in just one ticket? haproxy-configtest.patch Description: Binary data
Bug#763829: More information on this
Hi,
I can confirm Vincent’s conclusions, the init script has a do_stop() method
containing the line:
start-stop-daemon --stop --quiet --retry=TERM/30/KILL/5 --pidfile
/var/run/rsyslogd.pid --exec /usr/sbin/rsyslogd
And here’s the trailing output from:
# sudo strace start-stop-daemon --stop --quiet --retry=TERM/30/KILL/5
--pidfile /var/run/rsyslogd.pid --exec /usr/sbin/rsyslogd; echo $?
[…]
stat(/usr/sbin/rsyslogd, {st_mode=S_IFREG|0755, st_size=384416, ...}) = 0
open(/var/run/rsyslogd.pid, O_RDONLY) = 3
fstat(3, {st_mode=S_IFREG|0644, st_size=5, ...}) = 0
mmap(NULL, 4096, PROT_READ|PROT_WRITE, MAP_PRIVATE|MAP_ANONYMOUS, -1, 0) =
0x7fdb20e4d000
read(3, 1566\n, 4096) = 5
readlink(/proc/1566/exe, (deleted)/usr/sbin/rsyslogd..., 256) = 28
stat( (deleted)/usr/sbin/rsyslogd, 0x7fffd3dcc8e0) = -1 ENOENT (No such
file or directory)
close(3)= 0
munmap(0x7fdb20e4d000, 4096)= 0
exit_group(1) = ?
1
I looked at the nginx script and then tried this modified version:
sudo strace start-stop-daemon --stop --quiet --retry=TERM/30/KILL/5 --pidfile
/var/run/rsyslogd.pid --name rsyslogd; echo $?
[…]
0
So, I propose to ship another fix which replaces “--exec $DAEMON” with “-name
$RSYSLOGD” in the SysV init script.
Kind regards,
Sven
--
To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org
with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#742798: icecast2: init script does not support 'status' command
Package: icecast2
Version: 2.3.2-9+deb7u2
Severity: normal
Tags: patch
It would be great to provide a way to query the status of the service.
This is useful for systems such as salt [1] to query the status of a
service.
[1] http://www.saltstack.com/community/
Other services (e.g. sshd) provide a status command for this purpose.
I'll provide a patch to add support for this feature. The patch is
tested on my system after these things:
* install libxml2-utils (for xmllint)
* create a folder /var/run/icecast2
* set the owner to icecast2:icecast
* set the pidfile in /etc/icecast2/icecast.xml to
/var/run/icecast2/icecast.pid
* restart the icecast server
* Happiness!
Thank you very much,
Sven Herzberg
-- System Information:
Debian Release: 7.4
APT prefers stable
APT policy: (500, 'stable')
Architecture: amd64 (x86_64)
Foreign Architectures: i386
Kernel: Linux 2.6.32-26-pve (SMP w/1 CPU core)
Locale: LANG=de_DE.UTF-8, LC_CTYPE=de_DE.UTF-8 (charmap=UTF-8)
Shell: /bin/sh linked to /bin/dash
diff --git a/debian/icecast2.init b/debian/icecast2.init
index f244804..d508caf 100644
--- a/debian/icecast2.init
+++ b/debian/icecast2.init
@@ -33,6 +33,7 @@ CONFIGDEFAULTFILE=/etc/default/icecast2
USERID=icecast2
GROUPID=icecast
ENABLE=false
+PIDFILE=`xmllint --xpath '/icecast/paths/pidfile/text()' $CONFIGFILE 2/dev/null`
# Reads config file (will override defaults above)
[ -r $CONFIGDEFAULTFILE ] . $CONFIGDEFAULTFILE
@@ -42,6 +43,8 @@ if [ $ENABLE != true ]; then
exit 0
fi
+. /lib/lsb/init-functions
+
set -e
case $1 in
@@ -69,6 +72,13 @@ case $1 in
--exec $DAEMON -- -b -c $CONFIGFILE
echo $NAME.
;;
+ status)
+ if test -z $PIDFILE; then
+ log_failure_msg $NAME does not specify a pid file in $CONFIGFILE
+ exit 1
+ fi
+ status_of_proc -p $PIDFILE $DAEMON $NAME exit 0 || exit $?
+ ;;
*)
echo Usage: $0 {start|stop|restart|reload|force-reload} 2
exit 1
Bug#720275: Still not working?
I have been trying the version of wheezy-backports (as the wheezy version
exposes this bug).
I think this bug is still not solved. Executing the update call like this (just
like /etc/cron.d/munin-node does, except for more debugging here):
$ sudo munin-run -d apt_all update 7200 12; echo $?
# Processing plugin configuration from /etc/munin/plugin-conf.d/munin-node
# Setting /rgid/ruid/ to /111/65534/
# Setting /egid/euid/ to /111 111/65534/
# Setting up environment
# About to run '/etc/munin/plugins/apt_all update'
apt update maxinterval probability -- update apt databases randomly
maxinterval:
Enforce the updating of the apt database if it has
been more than (maxinterval many seconds since the last update.
probability:
There's a 1 in (probability) chance that the database
will be updated.
1
It looks like munin-run forwards the first argument only, causing silent errors
(because of the pipe in the crontab file).
Package information:
$ LC_ALL=C dpkg -l munin-{node,plugin*}
Desired=Unknown/Install/Remove/Purge/Hold
| Status=Not/Inst/Conf-files/Unpacked/halF-conf/Half-inst/trig-aWait/Trig-pend
|/ Err?=(none)/Reinst-required (Status,Err: uppercase=bad)
||/ NameVersionArchitecture
Description
+++-===-==-==-
ii munin-node 2.0.19-2~bpo70+1 all
network-wide graphing framework (node)
un munin-plugins none
(no description available)
ii munin-plugins-core 2.0.19-2~bpo70+1 all
network-wide graphing framework (plugins for node)
ii munin-plugins-extra 2.0.19-2~bpo70+1 all
network-wide graphing framework (user contributed plugins for node)
un munin-plugins-java none
(no description available)
If there is any way to move on with this ticket, I'd love to help.
--
Sven Herzberg
--
To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org
with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#540039: Status Update, please
What's the current status of this? -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#585116: Fix committed upstream
Hi,
this patch is supposed to fix that issue. Please try it and report if it
works. Also, feel free to include that patch into your current tarball
to fix this until there is a new release.
http://github.com/herzi/mango-lassi/commit/0357046972ebc6596ff26348c91f3de1662c3e77
Regards,
Sven
From 0357046972ebc6596ff26348c91f3de1662c3e77 Mon Sep 17 00:00:00 2001
From: Sven Herzberg he...@gnome-de.org
Date: Sat, 19 Jun 2010 14:21:59 +0200
Subject: [PATCH] disable GNOME's crash dialog
Fixes: http://github.com/herzi/mango-lassi/issues/#issue/1
* src/lassi-server.c: disable GNOME's crash dialog in order to avoid it
calling our logging handler with invalid arguments
---
src/lassi-server.c |6 ++
1 files changed, 6 insertions(+), 0 deletions(-)
diff --git a/src/lassi-server.c b/src/lassi-server.c
index 43082df..f669d9c 100644
--- a/src/lassi-server.c
+++ b/src/lassi-server.c
@@ -1560,6 +1560,12 @@ int main(int argc, char *argv[]) {
LassiServer ls;
GError *error = NULL;
+/* workaround bug-buddy using our logging handler in an unsave way
+ * http://github.com/herzi/mango-lassi/issues/#issue/1
+ * and
+ * http://bugs.gnome.org/622068 */
+g_setenv (GNOME_DISABLE_CRASH_DIALOG, 1, TRUE);
+
/* Initialize the i18n stuff */
bindtextdomain(GETTEXT_PACKAGE, LOCALEDIR);
bind_textdomain_codeset(GETTEXT_PACKAGE, UTF-8);
--
1.6.6.1
Bug#585116: Upstream Bug discussion
Hi, this bug has been forwarded upstream by Kartik: http://github.com/herzi/mango-lassi/issues#issue/1 Please follow the discussion over there (and realize that I already blame the gnome-breapd module for calling functions without knowing how to call them properly). Kind regards, Sven -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#449996: Proposed fix
The attached watch file (modelled after gnome-blog's one) should fix this. Regards, Sven version=3 http://ftp.gnome.org/pub/GNOME/sources/passepartout/([\d\.]+)/passepartout-([\d\.]+).tar.gz
Bug#315297: fedora-directory-server Debian packages
Am Freitag, den 03.11.2006, 16:00 +0100 schrieb Noèl Köthe: there is an ITP for fedora-directory-server from you. Any news on the packages? Not yet. Because its big like OpenLDAP maybe packaging could be done on http://alioth.debian.org/ with an svn repository? Good Idea. I just registered it, should be available soon. Regards, Sven -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Bug#244043: GQ 1.2.0 is out
GQ 1.2.0 includes fixed for the bugs in the TO: header. I think it also contains fixes to the ones in the CC: header. Regards, Sven -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Bug#386206: ITP: fedora-directory-server -- An LDAP server designed to manage large directories of users and resources
Package: wnpp Severity: wishlist Owner: Sven Herzberg [EMAIL PROTECTED] * Package name: fedora-directory-server Version : 1.0.2 Upstream Author : * URL : http://www.directory.fedora.redhat.com/ * License : GPL + exceptions: http://directory.fedora.redhat.com/wiki/Licensing Programming Lang: C Description : An LDAP server designed to manage large directories of users and resources An LDAP server designed to manage large directories of users and resources. Feature include: .. * 4-Way Multi-Master Replication * High Scalability * Active Directory user and group synchronization * Secure authentication and transport (SSLv3, TLSv1, and SASL) * Support for LDAPv3 * On-line, zero downtime, LDAP-based update of schema, configuration, management and in-tree Access Control Information (ACIs) * Graphical console for all facets of user, group, and server management -- System Information: Debian Release: testing/unstable APT prefers sid APT policy: (500, 'sid') Architecture: i386 (i686) Shell: /bin/sh linked to /bin/dash Kernel: Linux 2.6.17-6-686 Locale: LANG=de_DE.UTF-8, LC_CTYPE=de_DE.UTF-8 (charmap=UTF-8) -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Bug#371069: grub2: doesn't work on Debian PowerPC
Subject: grub2: doesn't work on Debian PowerPC Package: grub2 Severity: normal I tried installing grub2 the way I'm used to for grub 1: sudo grub-install --root-directory=/boot/grub /dev/hda1 /grub-mkimage: Not found. The I read /usr/share/doc/grub2/README.Debian and tried this: grub-mkimage -v -d /usr/share/grub/powerpc-pc/ -o /tmp/core.img _chain ext2 xfs grub-mkimage: error: cannot open /usr/share/grub/powerpc-pc//kernel.elf So I checked the path against the installed files (via 'dpkg -L grub2 | grep kernel') and found that this should work: grub-mkimage -v -d /usr/lib/grub/powerpc-ieee1275 -o /tmp/core.img _chain ext2 xfs grub-mkimage: info: copying segment 0, type 1 grub-mkimage: info: writing 0xc490 bytes at offset 0xa0 grub-mkimage: info: copying segment 1, type 1685382481 grub-mkimage: info: writing 0x0 bytes at offset 0x0 grub-mkimage: info: getting the size of /usr/lib/grub/powerpc-ieee1275/_chain.mod grub-mkimage: error: cannot stat /usr/lib/grub/powerpc-ieee1275/_chain.mod So please do these 2 things: 1. make sure grub-install works 2. Update the documentation 3. Add documentation about automatically installing new kernels (like grub1 has) Regards, Sven -- System Information: Debian Release: testing/unstable Architecture: i386 (i686) Shell: /bin/sh linked to /bin/bash Kernel: Linux 2.6.15-23-k7 Locale: LANG=de_DE.UTF-8, LC_CTYPE=de_DE.UTF-8 (charmap=UTF-8) signature.asc Description: This is a digitally signed message part
Bug#370259: grub2: FTBFS on debian powerpc
Subject: grub2: FTBFS on debian powerpc Package: grub2 Severity: normal According to the buildd [1], grub2 was not compiled successfully on Debian Powerpc. Can you please fix this? [1]http://buildd.debian.org/fetch.php?pkg=grub2ver=1.93-1arch=powerpcstamp=1143897828file=logas=raw -- System Information: Debian Release: testing/unstable Architecture: i386 (i686) Shell: /bin/sh linked to /bin/bash Kernel: Linux 2.6.15-23-k7 Locale: LANG=de_DE.UTF-8, LC_CTYPE=de_DE.UTF-8 (charmap=UTF-8) -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Bug#357853: April Fools Day?
Hey guys, was it just an april folls day joke that this bug was closed on April 1st? I cannot find a powerpc deb on http://packages.debian.org/grub2 . Is this bug really supposed to be closed? Regards, Sven signature.asc Description: This is a digitally signed message part
Bug#238711: using -geometry results in a startup error
Hi guys, to my opinion, this it _not a bug_. Executing gq --help lists all supported command line arguments and if you pass unknown ones, it simply aborts with an error (and that's the same as most of the tools I'm using do - including the list of cd, mv, cp, chown, chmod, etc.). Regards, Sven PS: If you're still interested in geometry support, please file a bug at the upstream bug tracker [http://www.sf.net/projects/gq] signature.asc Description: This is a digitally signed message part
Bug#242532: This feature depends on OpenSSL
Hi guys, please build GQ with build-dep libssl-dev. Then this gets available within GQ's GUI. Regards, Sven signature.asc Description: This is a digitally signed message part
Bug#365206: Add editor for UNIX-dates, needed for shadow-account-information
Hey guys, this patch looks okay for me. I'm going to include it into the current development tree of GQ (which is supposed to become GQ 1.2.0 in nothern fall 2006). As GQ 1.0.x is intended to contain bug fixes and translation updates only, I'm not going to apply this patch to the 1.0.x branch (but the Debian maintainer may want to deliver this patch). Regards, Sven signature.asc Description: This is a digitally signed message part
Bug#364721: GQ 1.0.0 is available
Hi guys, it been some time since I released GQ 1.0.0. Can you please update to this version? It fixes several bugs reported both for Ubuntu [1] and for Debian and reduces the necessary patchset to contain one patch only. So please do this: apt-get source gq download [2] and extract new tarball cp -r gq_1.0beta1-4/debian gq-1.0.0 # this is necessary as the debdiff # contains several passages about config.guess etc. which have been # updated with this upstream release Remove these patches: debian/patches/01_maintainhiddenstatus.dpatch committed on 2006-04-05 [3] debian/patches/03_gcc4.dpatch committed on 2005-04-27 [4] debian/patches/03_gcc4.dpatch.OLD that patch never worked (see [5] and [6]) and has been deprecated by 03_gcc4.dpatch Then build a package. The debian/patches/02_deletepassonask.dpatch is not included with GQ 1.0.0 as I don't agree with this behaviour. But with GQ 1.2.0 (northern hemisphere fall 2006) I'm sure you can drop this patch as we're going to have something that's really better than both the current situation and this patch. Regards, Sven PS: Sivan, as you're doing this for Ubuntu, can you please add a notification to this bug when the work is done (so debian just needs to copy the work, I see no sense in doing this twice). [1]https://launchpad.net/bugs/25825 [2]http://www.sf.net/projects/gqclient/ [3]http://gqclient.cvs.sourceforge.net/gqclient/gq/src/input.c?view=diffr1=1.87r2=1.88 [4]http://gqclient.cvs.sourceforge.net/gqclient/gq/src/configfile.h?view=diffr1=1.39r2=1.40 [5]http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=300104 [6]http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=318796 signature.asc Description: This is a digitally signed message part
Bug#326521: alleyoop: New upstream version available
Package: alleyoop Severity: wishlist There's a new upstream version available, please update to 0.9.0 from http://alleyoop.sf.net/ -- System Information: Debian Release: 3.1 Architecture: powerpc (ppc) Kernel: Linux 2.6.8-pegasos Locale: [EMAIL PROTECTED], [EMAIL PROTECTED] (charmap=UTF-8) -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Bug#296299: Updates?
Any updates on this bug? Would you accept patches against libxml2 once sarge is out? Regards, Sven signature.asc Description: This is a digitally signed message part
Bug#295394: Status?
Hi there, did anything happen yet? I just got my hula packages into Ubuntu. If you want to, I can provide packages for debian too. Regards, Sven signature.asc Description: This is a digitally signed message part
