Bug#402482: RC?
severity 402482 important thanks * Steve McIntyre ([EMAIL PROTECTED]) [061211 17:02]: > Joey wrote: > >I don't belive that this bug is actually RC: There's a workaround for > >the problem in debian-cd, and the bug's not causing any other > >problems that I know of. > > I'm happy for this to be tagged etch-ignore, but it can potentially > lead to data loss so I think it should stay as serious in the long > run I have yet to see the dataloss. Anyways, bugs being important doesn't mean they are not allowed to be fixed (and I would let such an fix still to Etch currently), but I don't think we should wait on the fix. So I'm downgrading to important. Cheers, Andi -- http://home.arcor.de/andreas-barth/ -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
Bug#403397: marked as done (conflict file with lxr-cvs: /usr/bin/genxref without Conflicts)
Your message dated Wed, 20 Dec 2006 07:32:02 + with message-id <[EMAIL PROTECTED]> and subject line Bug#403397: fixed in lxr 0.3.1-4 has caused the attached Bug report to be marked as done. This means that you claim that the problem has been dealt with. If this is not the case it is now your responsibility to reopen the Bug report if necessary, and/or fix the problem forthwith. (NB: If you are a system administrator and have no idea what I am talking about this indicates a serious mail system misconfiguration somewhere. Please contact me immediately.) Debian bug tracking system administrator (administrator, Debian Bugs database) --- Begin Message --- Package: lxr Version: 0.3.1-2.1 Severity: serious Justification: conflicting file installed: /usr/bin/genxref Hi, apparently there's a conflicting file that gets installed by both lxr-cvs and lxr, namely /usr/bin/genxref probably the best solution is to install genxref-cvs into lxr-cvs (but I'm not sure, genxref could use common paths, in that case an alternative or Conflicts is in order) thanks, filippo -- System Information: Debian Release: 4.0 APT prefers unstable APT policy: (600, 'unstable') Architecture: powerpc (ppc) Shell: /bin/sh linked to /bin/bash Kernel: Linux 2.6.17 Locale: LANG=en_US, LC_CTYPE=en_US (charmap=ISO-8859-1) --- End Message --- --- Begin Message --- Source: lxr Source-Version: 0.3.1-4 We believe that the bug you reported is fixed in the latest version of lxr, which is due to be installed in the Debian FTP archive: lxr_0.3.1-4.diff.gz to pool/main/l/lxr/lxr_0.3.1-4.diff.gz lxr_0.3.1-4.dsc to pool/main/l/lxr/lxr_0.3.1-4.dsc lxr_0.3.1-4_all.deb to pool/main/l/lxr/lxr_0.3.1-4_all.deb A summary of the changes between this version and the previous one is attached. Thank you for reporting the bug, which will now be closed. If you have further comments please address them to [EMAIL PROTECTED], and the maintainer will reopen the bug report if appropriate. Debian distribution maintenance software pp. Giacomo Catenazzi <[EMAIL PROTECTED]> (supplier of updated lxr package) (This message was generated automatically at their request; if you believe that there is a problem with it please contact the archive administrators by mailing [EMAIL PROTECTED]) -BEGIN PGP SIGNED MESSAGE- Hash: SHA1 Format: 1.7 Date: Wed, 20 Dec 2006 08:16:33 +0100 Source: lxr Binary: lxr Architecture: source all Version: 0.3.1-4 Distribution: unstable Urgency: low Maintainer: Giacomo Catenazzi <[EMAIL PROTECTED]> Changed-By: Giacomo Catenazzi <[EMAIL PROTECTED]> Description: lxr- Linux Cross-Reference Closes: 379229 400953 403397 Changes: lxr (0.3.1-4) unstable; urgency=low . * acknowledgement of last NMU Thanks Luk! (Closes: #379229). * and removing last references of /var/lib (Closes: #400953) * conflict with lxr-cvs, because we use same binary program name. Thanks James and Filippo! (info at the end of in already closed: #326467, also closes: #403397). * Correct debian/copyright file. Files: b98c9ab01779777c0a893e60a3f04a94 544 misc extra lxr_0.3.1-4.dsc 51298f065d11ce1029158b9d38594d3b 5374 misc extra lxr_0.3.1-4.diff.gz 130e3c50f1416eb95c8cc39cbcd47459 26788 misc extra lxr_0.3.1-4_all.deb -BEGIN PGP SIGNATURE- Version: GnuPG v1.4.6 (GNU/Linux) iD8DBQFFiOU8+ZNUJLHfmlcRAsDZAKCH7FjgNzyAxcoucF0sNoQu5jqD4QCeItmm 6YMw8KIu1i9LApQGXjQJFMc= =YBTS -END PGP SIGNATURE- --- End Message ---
Bug#354355: sympa: Please stop kidding
Jean Charles Delepine wrote:
"Stefan Hornburg (Racke)" <[EMAIL PROTECTED]> écrivait (wrote) :
Right and sorry, I'll fix that.
Thats not the only problems with your package.
* wwsympa will not start :
## Check effective ID
unless ($> eq (getpwnam('--USER--'))[2]) {
&report::reject_report_web('intern_quiet','incorrect_server_config',{},
'','');
&wwslog('err','Config error: wwsympa should run with UID %s (instead of
%s)', (getpwnam('--USER--'))[2], $>);
}
In your package --USER-- is root. But wwsympa will, correctly start as
sympa.
see sympa-5.2.3-0.7/debian/patch/01_owner-vs-user.dpatch
and my debian rules for a solution.
* no soap
+ same problem as wwsympa if the admin manage to start it
see my package for a solution
* if the user choose mysql and ask not to give root password as suggested
your package will fail. See my package for something wich works as stated.
You will also need 05_default_database_none.dpatch and my debian/config
test:/home/delepine# mysql mysql connect($dsn, "root","")) {exit 0;} else {exit 1;}' /dev/null;
test:/home/delepine# echo $?
1
* debian/config is craps. Please use diff and see my changes.
Extract: if [ "db_hostname" = "localhost" ]; then
* you will create arc and bounce dir in /usr/lib/sympa
06_dont_create_arc_and_bounce.dpatch
OK, i fixed that in my source tree by just removing these directories in the
install target.
If possible, I would like to avoid doing automake/autoconf in package builds.
Bye
Racke
--
LinuXia Systems => http://www.linuxia.de/
Expert Interchange Consulting and System Administration
ICDEVGROUP => http://www.icdevgroup.org/
Interchange Development Team
--
To UNSUBSCRIBE, email to [EMAIL PROTECTED]
with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
Processed: Re: RC?
Processing commands for [EMAIL PROTECTED]: > severity 402482 important Bug#402482: busybox gunzip / zcat fail to decompress validly gzipped files Severity set to `important' from `serious' > thanks Stopping processing here. Please contact me if you need assistance. Debian bug tracking system administrator (administrator, Debian Bugs database) -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
Bug#403795: Bug#403300: nagios2-common: resource.cfg missing
Version: 2.6-2 On Sat, Dec 16, 2006 at 12:48:53AM +, Tristan Hill wrote: > chown: cannot access `/etc/nagios2/resource.cfg': No such file or > directory This was fixed in nagios2 2.6-2. Greetings Marc -- - Marc Haber | "I don't trust Computers. They | Mailadresse im Header Mannheim, Germany | lose things."Winona Ryder | Fon: *49 621 72739834 Nordisch by Nature | How to make an American Quilt | Fax: *49 621 72739835 -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
Bug#403300: marked as done (nagios2-common: resource.cfg missing)
Your message dated Wed, 20 Dec 2006 08:13:56 +0100 with message-id <[EMAIL PROTECTED]> and subject line Bug#403300: nagios2-common: resource.cfg missing has caused the attached Bug report to be marked as done. This means that you claim that the problem has been dealt with. If this is not the case it is now your responsibility to reopen the Bug report if necessary, and/or fix the problem forthwith. (NB: If you are a system administrator and have no idea what I am talking about this indicates a serious mail system misconfiguration somewhere. Please contact me immediately.) Debian bug tracking system administrator (administrator, Debian Bugs database) --- Begin Message --- Package: nagios2-common Version: 2.6-1 Severity: normal On installation: Setting up nagios2-common (2.6-1) ... Adding system-user for nagios Creating config file /etc/nagios2/apache2.conf with new version Creating config file /etc/nagios2/conf.d/host-gateway_nagios2.cfg with new version Reloading web server config...10950 .. Adding password for user nagiosadmin chown: cannot access `/etc/nagios2/resource.cfg': No such file or directory dpkg: error processing nagios2-common (--configure): subprocess post-installation script returned error exit status 1 -- System Information: Debian Release: 4.0 APT prefers unstable APT policy: (500, 'unstable') Architecture: i386 (i686) Shell: /bin/sh linked to /bin/bash Kernel: Linux 2.6.17-10-generic Locale: LANG=C, LC_CTYPE=C (charmap=ANSI_X3.4-1968) Versions of packages nagios2-common depends on: ii adduser 3.100 Add and remove users and groups ii apache2 2.2.3-3.2 Next generation, scalable, extenda ii apache2-mpm-work 2.2.3-3.2 High speed threaded model for Apac ii coreutils5.97-5.2The GNU core utilities ii debconf [debconf 1.5.10 Debian configuration management sy ii lsb-base 3.1-22 Linux Standard Base 3.1 init scrip ii mailx1:8.1.2-0.20050715cvs-1 A simple mail user agent ii nagios-plugins-b 1.4.5-2 Plugins for the nagios network mon ii nagios2-doc 2.6-1 documentation for nagios2 ii ucf 2.0017 Update Configuration File: preserv Versions of packages nagios2-common recommends: pn nagios-images (no description available) pn nagios-plugins (no description available) -- debconf information excluded --- End Message --- --- Begin Message --- Version: 2.6-2 On Sat, Dec 16, 2006 at 12:48:53AM +, Tristan Hill wrote: > chown: cannot access `/etc/nagios2/resource.cfg': No such file or > directory This was fixed in nagios2 2.6-2. Greetings Marc -- - Marc Haber | "I don't trust Computers. They | Mailadresse im Header Mannheim, Germany | lose things."Winona Ryder | Fon: *49 621 72739834 Nordisch by Nature | How to make an American Quilt | Fax: *49 621 72739835 --- End Message ---
Bug#403795: marked as done (nagios2 doesn't install)
Your message dated Wed, 20 Dec 2006 08:13:56 +0100 with message-id <[EMAIL PROTECTED]> and subject line Bug#403300: nagios2-common: resource.cfg missing has caused the attached Bug report to be marked as done. This means that you claim that the problem has been dealt with. If this is not the case it is now your responsibility to reopen the Bug report if necessary, and/or fix the problem forthwith. (NB: If you are a system administrator and have no idea what I am talking about this indicates a serious mail system misconfiguration somewhere. Please contact me immediately.) Debian bug tracking system administrator (administrator, Debian Bugs database) --- Begin Message --- Package: nagios2 Version: 2.6-1 Severity: normal Hello, I was just trying to install nagios2 and it fails because of missing file /etc/nagios2/resource.cfg It's a fresh install, no previous install of nagios/nagios2. That's what i get (french system): r-d:/home/lord# apt-get install nagios2 Lecture des listes de paquets... Fait Construction de l'arbre des dépendances... Fait Les paquets supplémentaires suivants seront installés : apache2 apache2-mpm-worker apache2-utils apache2.2-common iputils-ping libapr1 libaprutil1 libpq4 nagios-plugins-basic nagios2-common nagios2-doc Paquets suggérés : nagios-text nagios nagios-nrpe-plugin Paquets recommandés : nagios-plugins nagios-images Les paquets suivants seront ENLEVÉS : netkit-ping Les NOUVEAUX paquets suivants seront installés : apache2 apache2-mpm-worker apache2-utils apache2.2-common iputils-ping libapr1 libaprutil1 libpq4 nagios-plugins-basic nagios2 nagios2-common nagios2-doc 0 mis à jour, 12 nouvellement installés, 1 à enlever et 2 non mis à jour. Il est nécessaire de prendre 4885ko dans les archives. Après dépaquetage, 13,2Mo d'espace disque supplémentaires seront utilisés. Souhaitez-vous continuer [O/n] ? Réception de : 1 http://ftp2.fr.debian.org testing/main iputils-ping 3:20020927-3.1 [41,4kB] Réception de : 2 http://ftp2.fr.debian.org testing/main libapr1 1.2.7-8.1 [109kB] Réception de : 3 http://ftp2.fr.debian.org testing/main libpq4 8.1.5-2 [262kB] Réception de : 4 http://ftp2.fr.debian.org testing/main libaprutil1 1.2.7+dfsg-2 [68,5kB] Réception de : 5 http://ftp2.fr.debian.org testing/main apache2-utils 2.2.3-3.2 [340kB] Réception de : 6 http://ftp2.fr.debian.org testing/main apache2.2-common 2.2.3-3.2 [931kB] Réception de : 7 http://ftp2.fr.debian.org testing/main apache2-mpm-worker 2.2.3-3.2 [421kB] Réception de : 8 http://ftp2.fr.debian.org testing/main apache2 2.2.3-3.2 [38,4kB] Réception de : 9 http://ftp2.fr.debian.org testing/main nagios-plugins-basic 1.4.5-1 [470kB] Réception de : 10 http://ftp2.fr.debian.org testing/main nagios2-doc 2.6-1 [1133kB] Réception de : 11 http://ftp2.fr.debian.org testing/main nagios2-common 2.6-1 [55,8kB] Réception de : 12 http://ftp2.fr.debian.org testing/main nagios2 2.6-1 [1015kB] 4885ko réceptionnés en 13s (375ko/s) Préconfiguration des paquets... dpkg : netkit-ping : problème de dépendance, mais suppression comme demandé : gnome-nettool dépend de ping ; cependant : Le paquet ping n'est pas installé. Le paquet netkit-ping qui fournit ping doit être supprimé. netbase dépend de iputils-ping | ping ; cependant : Le paquet iputils-ping n'est pas installé. Le paquet ping n'est pas installé. Le paquet netkit-ping qui fournit ping doit être supprimé. (Lecture de la base de données... 128753 fichiers et répertoires déjà installés.) Suppression de netkit-ping ... Sélection du paquet iputils-ping précédemment désélectionné. (Lecture de la base de données... 128747 fichiers et répertoires déjà installés.) Dépaquetage de iputils-ping (à partir de .../iputils-ping_3%3a20020927-3.1_i386.deb) ... Sélection du paquet libapr1 précédemment désélectionné. Dépaquetage de libapr1 (à partir de .../libapr1_1.2.7-8.1_i386.deb) ... Sélection du paquet libpq4 précédemment désélectionné. Dépaquetage de libpq4 (à partir de .../libpq4_8.1.5-2_i386.deb) ... Sélection du paquet libaprutil1 précédemment désélectionné. Dépaquetage de libaprutil1 (à partir de .../libaprutil1_1.2.7+dfsg-2_i386.deb) ... Sélection du paquet apache2-utils précédemment désélectionné. Dépaquetage de apache2-utils (à partir de .../apache2-utils_2.2.3-3.2_i386.deb) ... Sélection du paquet apache2.2-common précédemment désélectionné. Dépaquetage de apache2.2-common (à partir de .../apache2.2-common_2.2.3-3.2_i386.deb) ... Sélection du paquet apache2-mpm-worker précédemment désélectionné. Dépaquetage de apache2-mpm-worker (à partir de .../apache2-mpm-worker_2.2.3-3.2_i386.deb) ... Sélection du paquet apache2 précédemment désélectionné. Dépaquetage de apache2 (à partir de .../apache2_2.2.3-3.2_all.deb) ... Sélection du paquet nagios-plugins-basic précédemment désélectionné. Dépaquetage de nagios-plugins-basic (à partir de .../nagios-plugins-basic_1.4.5-1_i386.deb) ... Sélection du paquet nagios2-doc précédemment désélectionné. Dépaquetage de n
Bug#403795: marked as done (nagios2 doesn't install)
Your message dated Wed, 20 Dec 2006 08:13:56 +0100 with message-id <[EMAIL PROTECTED]> and subject line Bug#403300: nagios2-common: resource.cfg missing has caused the attached Bug report to be marked as done. This means that you claim that the problem has been dealt with. If this is not the case it is now your responsibility to reopen the Bug report if necessary, and/or fix the problem forthwith. (NB: If you are a system administrator and have no idea what I am talking about this indicates a serious mail system misconfiguration somewhere. Please contact me immediately.) Debian bug tracking system administrator (administrator, Debian Bugs database) --- Begin Message --- Package: nagios2 Version: 2.6-1 Severity: normal Hello, I was just trying to install nagios2 and it fails because of missing file /etc/nagios2/resource.cfg It's a fresh install, no previous install of nagios/nagios2. That's what i get (french system): r-d:/home/lord# apt-get install nagios2 Lecture des listes de paquets... Fait Construction de l'arbre des dépendances... Fait Les paquets supplémentaires suivants seront installés : apache2 apache2-mpm-worker apache2-utils apache2.2-common iputils-ping libapr1 libaprutil1 libpq4 nagios-plugins-basic nagios2-common nagios2-doc Paquets suggérés : nagios-text nagios nagios-nrpe-plugin Paquets recommandés : nagios-plugins nagios-images Les paquets suivants seront ENLEVÉS : netkit-ping Les NOUVEAUX paquets suivants seront installés : apache2 apache2-mpm-worker apache2-utils apache2.2-common iputils-ping libapr1 libaprutil1 libpq4 nagios-plugins-basic nagios2 nagios2-common nagios2-doc 0 mis à jour, 12 nouvellement installés, 1 à enlever et 2 non mis à jour. Il est nécessaire de prendre 4885ko dans les archives. Après dépaquetage, 13,2Mo d'espace disque supplémentaires seront utilisés. Souhaitez-vous continuer [O/n] ? Réception de : 1 http://ftp2.fr.debian.org testing/main iputils-ping 3:20020927-3.1 [41,4kB] Réception de : 2 http://ftp2.fr.debian.org testing/main libapr1 1.2.7-8.1 [109kB] Réception de : 3 http://ftp2.fr.debian.org testing/main libpq4 8.1.5-2 [262kB] Réception de : 4 http://ftp2.fr.debian.org testing/main libaprutil1 1.2.7+dfsg-2 [68,5kB] Réception de : 5 http://ftp2.fr.debian.org testing/main apache2-utils 2.2.3-3.2 [340kB] Réception de : 6 http://ftp2.fr.debian.org testing/main apache2.2-common 2.2.3-3.2 [931kB] Réception de : 7 http://ftp2.fr.debian.org testing/main apache2-mpm-worker 2.2.3-3.2 [421kB] Réception de : 8 http://ftp2.fr.debian.org testing/main apache2 2.2.3-3.2 [38,4kB] Réception de : 9 http://ftp2.fr.debian.org testing/main nagios-plugins-basic 1.4.5-1 [470kB] Réception de : 10 http://ftp2.fr.debian.org testing/main nagios2-doc 2.6-1 [1133kB] Réception de : 11 http://ftp2.fr.debian.org testing/main nagios2-common 2.6-1 [55,8kB] Réception de : 12 http://ftp2.fr.debian.org testing/main nagios2 2.6-1 [1015kB] 4885ko réceptionnés en 13s (375ko/s) Préconfiguration des paquets... dpkg : netkit-ping : problème de dépendance, mais suppression comme demandé : gnome-nettool dépend de ping ; cependant : Le paquet ping n'est pas installé. Le paquet netkit-ping qui fournit ping doit être supprimé. netbase dépend de iputils-ping | ping ; cependant : Le paquet iputils-ping n'est pas installé. Le paquet ping n'est pas installé. Le paquet netkit-ping qui fournit ping doit être supprimé. (Lecture de la base de données... 128753 fichiers et répertoires déjà installés.) Suppression de netkit-ping ... Sélection du paquet iputils-ping précédemment désélectionné. (Lecture de la base de données... 128747 fichiers et répertoires déjà installés.) Dépaquetage de iputils-ping (à partir de .../iputils-ping_3%3a20020927-3.1_i386.deb) ... Sélection du paquet libapr1 précédemment désélectionné. Dépaquetage de libapr1 (à partir de .../libapr1_1.2.7-8.1_i386.deb) ... Sélection du paquet libpq4 précédemment désélectionné. Dépaquetage de libpq4 (à partir de .../libpq4_8.1.5-2_i386.deb) ... Sélection du paquet libaprutil1 précédemment désélectionné. Dépaquetage de libaprutil1 (à partir de .../libaprutil1_1.2.7+dfsg-2_i386.deb) ... Sélection du paquet apache2-utils précédemment désélectionné. Dépaquetage de apache2-utils (à partir de .../apache2-utils_2.2.3-3.2_i386.deb) ... Sélection du paquet apache2.2-common précédemment désélectionné. Dépaquetage de apache2.2-common (à partir de .../apache2.2-common_2.2.3-3.2_i386.deb) ... Sélection du paquet apache2-mpm-worker précédemment désélectionné. Dépaquetage de apache2-mpm-worker (à partir de .../apache2-mpm-worker_2.2.3-3.2_i386.deb) ... Sélection du paquet apache2 précédemment désélectionné. Dépaquetage de apache2 (à partir de .../apache2_2.2.3-3.2_all.deb) ... Sélection du paquet nagios-plugins-basic précédemment désélectionné. Dépaquetage de nagios-plugins-basic (à partir de .../nagios-plugins-basic_1.4.5-1_i386.deb) ... Sélection du paquet nagios2-doc précédemment désélectionné. Dépaquetage de n
Bug#403300: marked as done (nagios2-common: resource.cfg missing)
Your message dated Wed, 20 Dec 2006 08:13:56 +0100 with message-id <[EMAIL PROTECTED]> and subject line Bug#403300: nagios2-common: resource.cfg missing has caused the attached Bug report to be marked as done. This means that you claim that the problem has been dealt with. If this is not the case it is now your responsibility to reopen the Bug report if necessary, and/or fix the problem forthwith. (NB: If you are a system administrator and have no idea what I am talking about this indicates a serious mail system misconfiguration somewhere. Please contact me immediately.) Debian bug tracking system administrator (administrator, Debian Bugs database) --- Begin Message --- Package: nagios2-common Version: 2.6-1 Severity: normal On installation: Setting up nagios2-common (2.6-1) ... Adding system-user for nagios Creating config file /etc/nagios2/apache2.conf with new version Creating config file /etc/nagios2/conf.d/host-gateway_nagios2.cfg with new version Reloading web server config...10950 .. Adding password for user nagiosadmin chown: cannot access `/etc/nagios2/resource.cfg': No such file or directory dpkg: error processing nagios2-common (--configure): subprocess post-installation script returned error exit status 1 -- System Information: Debian Release: 4.0 APT prefers unstable APT policy: (500, 'unstable') Architecture: i386 (i686) Shell: /bin/sh linked to /bin/bash Kernel: Linux 2.6.17-10-generic Locale: LANG=C, LC_CTYPE=C (charmap=ANSI_X3.4-1968) Versions of packages nagios2-common depends on: ii adduser 3.100 Add and remove users and groups ii apache2 2.2.3-3.2 Next generation, scalable, extenda ii apache2-mpm-work 2.2.3-3.2 High speed threaded model for Apac ii coreutils5.97-5.2The GNU core utilities ii debconf [debconf 1.5.10 Debian configuration management sy ii lsb-base 3.1-22 Linux Standard Base 3.1 init scrip ii mailx1:8.1.2-0.20050715cvs-1 A simple mail user agent ii nagios-plugins-b 1.4.5-2 Plugins for the nagios network mon ii nagios2-doc 2.6-1 documentation for nagios2 ii ucf 2.0017 Update Configuration File: preserv Versions of packages nagios2-common recommends: pn nagios-images (no description available) pn nagios-plugins (no description available) -- debconf information excluded --- End Message --- --- Begin Message --- Version: 2.6-2 On Sat, Dec 16, 2006 at 12:48:53AM +, Tristan Hill wrote: > chown: cannot access `/etc/nagios2/resource.cfg': No such file or > directory This was fixed in nagios2 2.6-2. Greetings Marc -- - Marc Haber | "I don't trust Computers. They | Mailadresse im Header Mannheim, Germany | lose things."Winona Ryder | Fon: *49 621 72739834 Nordisch by Nature | How to make an American Quilt | Fax: *49 621 72739835 --- End Message ---
Bug#403641: Is this RC: "postrm remove" assumes Depended-on packages are configured and fails (was: Bug#403641: tetex-base: postrm fails if just unpackaged.)
severity 403641 important thanks On Mon, Dec 18, 2006 at 07:36:10PM +0100, Frank Küster wrote: > do you consider the following scenario release-critical? If yes, we > have more than one RC bug: > - $packagemanager install B X > - package A is unpacked > - package B which Depends: A is unpacked > - package X which is unrelated is tried to unpack, but fails (e.g. a > file conflict > - $packagmanager starts removing all new packages > - the postrm of B is called with "remove" and fails since it assumes > that A is configured and uses commands which fail > This happened with tetex-base on a build, but the problem exists in all > packages that use dh_installtex with any other options than common > debhelper ones. > The Policy document is a bit misleading in this respect, I have filed a > bug about it (no number yet), since it doesn't mention any difference > between "relying on being present" and "relying on being configured". > Therefore I suspect that many more packages suffer from this problem. > And actually each command used in any "postrm remove" can become > dependent on "configuredness" by later uploads of the depended-on > package, so this is a general problem for all types of packages. As might be obvious from my reply to the policy discussion, I don't think this is release-critical, no. :) Downgrading accordingly; Andi has unblocked the new version of the package anyway which handles this case, so this is more or less a formality at this point. Cheers, -- Steve Langasek Give me a lever long enough and a Free OS Debian Developer to set it on, and I can move the world. [EMAIL PROTECTED] http://www.debian.org/
Processed: Re: Is this RC: "postrm remove" assumes Depended-on packages are configured and fails (was: Bug#403641: tetex-base: postrm fails if just unpackaged.)
Processing commands for [EMAIL PROTECTED]: > severity 403641 important Bug#403641: tetex-base: postrm fails if just unpackaged. Severity set to `important' from `serious' > thanks Stopping processing here. Please contact me if you need assistance. Debian bug tracking system administrator (administrator, Debian Bugs database) -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
Processed: your mail
Processing commands for [EMAIL PROTECTED]: > reassign 403673 libattr1 Bug#403673: /lib/libacl.so.1: symbol getxattr, version ATTR_1.0 not defined in file libattr.so.1 with link time reference Bug reassigned from package `libacl1' to `libattr1'. > forcemerge 403585 403587 403590 403592 403599 403601 403651 403673 Bug#403585: Regression in 2.4.35-1 Bug#403587: libattr1: Upgrade renders ls unuseable Bug#403590: ls -l does not work any longer Bug#403592: libattr1: relocation error: /lib/libacl.so.1: Bug#403599: Regression in 2.2.42-1 Bug#403601: tex-common: unable to install because of cp Bug#403651: libacl1: symbol setxattr ATTR_1.0 not defined libattr.so.1 (ATTR_1.1) Bug#403673: /lib/libacl.so.1: symbol getxattr, version ATTR_1.0 not defined in file libattr.so.1 with link time reference Forcibly Merged 403585 403587 403590 403592 403599 403601 403651 403673. > -- Stopping processing here. Please contact me if you need assistance. Debian bug tracking system administrator (administrator, Debian Bugs database) -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
Bug#403585: Regression in 2.4.35-1
On Tue, 2006-12-19 at 09:22 +0100, Aurélien GÉRÔME wrote: > On Tue, Dec 19, 2006 at 05:57:00PM +1100, Nathan Scott wrote: > > Hmm, my upload got rejected for some version ... I've sent off some > > mail to try figure out why. > > > > On Tue, 2006-12-19 at 03:02 +, Debian Installer wrote: > > > Rejected: libattr1-dev_2.4.36-1_i386.deb: old version (1:2.4.32-1.1) > > in unstable >= new version (2.4.36-1) targeted at unstable. > > > Rejected: libattr1_2.4.36-1_i386.deb: old version (1:2.4.32-1.1) in > > unstable >= new version (2.4.36-1) targeted at unstable. > > > Rejected: attr_2.4.36-1_i386.deb: old version (1:2.4.32-1.1) in > > unstable >= new version (2.4.36-1) targeted at unstable. > > > Rejected: attr_2.4.36-1.dsc: old version (1:2.4.32-1.1) in unstable >= > > new version (2.4.36-1) targeted at unstable. > > > > > > === > > > > > > If you don't understand why your files were rejected, or if the > > > override file requires editing, reply to this email. > > As reports of broken sid systems rose up, Andreas Barth NMUed > your package yesterday in a 0-day NMU policy. He setup an epoch > to the package version which IMHO is a bad thing now that we > have the possibility of ~ in version strings. He could have used > 2.4.35~is.2.4.32-0.1 instead of the ugly 1:2.4.32-1.1, because from > now on, you are stuck with an epoch in your package versions. Oh. What is your recommendation on fixing this Andi? How do I get past this epoch that's been thown into my previously neat and tidy version management, and back to the simple versioning model I had? thanks. -- Nathan
Bug#403857: synaptic: uninstallable on i386 (depends on unavailable libapt-pkg-libc6.3-6-4.3)
Package: synaptic Version: 0.57.11.1 Severity: grave Justification: renders package unusable The i386 build of synaptic 0.57.11.1 uploaded by the maintainer is uninstallable due to a dependency on libapt-pkg-libc6.3-6-4.3. Steve Langasek already scheduled a binNMU to fix this. This report is mainly to let Michael know of the issue and can be closed next dinstall. -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
Bug#403818: marked as done (xserver-xorg: no video or keyboard after upgrading to sarge (deps too loose))
Your message dated Wed, 20 Dec 2006 04:17:02 + with message-id <[EMAIL PROTECTED]> and subject line Bug#403818: fixed in xorg 1:7.1.0-9 has caused the attached Bug report to be marked as done. This means that you claim that the problem has been dealt with. If this is not the case it is now your responsibility to reopen the Bug report if necessary, and/or fix the problem forthwith. (NB: If you are a system administrator and have no idea what I am talking about this indicates a serious mail system misconfiguration somewhere. Please contact me immediately.) Debian bug tracking system administrator (administrator, Debian Bugs database) --- Begin Message --- Package: xserver-xorg Version: 1:7.1.0-8 Severity: serious Justification: 23:28 < vorlon> Sesse: I'd call it RC, no? After dist-upgrading (using etch's aptitude) from sarge to etch, one machine here was completely without keyboard or mouse support, and X refused to work. A bit of hunting revealed that aptitude had pulled in xserver-xorg-input-magictouch and xserver-xorg-video-siliconmotion to fulfill xserver-xorg's dependencies on "xserver-xorg-video-all | xserver-xorg-video" and "xserver-xorg-input-all | xserver-xorg-input", respectively. This is clearly not satisfiable. AFAICS there are two OK ways of solving this: 1. Make the depends into "xserver-xorg-video, xserver-xorg-input", and add Recommends for the -all packages instead. 2. Add xserver-xorg-input-kbd and xserver-xorg-input-mouse explicitly to the list of depends (or possibly recommends?), which should make aptitude Do The Right Thing (hopefully). This won't solve the issue for video, though. One could use a combination of 1 and 2. Note that the request to "aptitude install xorg", which was given by debconf, was a no-op, since all the dependencies were already fulfilled. Also, xorg.conf was blank after the upgrade, but I guess that's for another bug, which will be far harder to track down... :-) --- End Message --- --- Begin Message --- Source: xorg Source-Version: 1:7.1.0-9 We believe that the bug you reported is fixed in the latest version of xorg, which is due to be installed in the Debian FTP archive: libglu1-xorg-dev_7.1.0-9_all.deb to pool/main/x/xorg/libglu1-xorg-dev_7.1.0-9_all.deb libglu1-xorg_7.1.0-9_all.deb to pool/main/x/xorg/libglu1-xorg_7.1.0-9_all.deb x-window-system-core_7.1.0-9_all.deb to pool/main/x/xorg/x-window-system-core_7.1.0-9_all.deb x-window-system_7.1.0-9_all.deb to pool/main/x/xorg/x-window-system_7.1.0-9_all.deb x11-common_7.1.0-9_i386.deb to pool/main/x/xorg/x11-common_7.1.0-9_i386.deb xlibmesa-dri_7.1.0-9_all.deb to pool/main/x/xorg/xlibmesa-dri_7.1.0-9_all.deb xlibmesa-gl-dev_7.1.0-9_all.deb to pool/main/x/xorg/xlibmesa-gl-dev_7.1.0-9_all.deb xlibmesa-gl_7.1.0-9_all.deb to pool/main/x/xorg/xlibmesa-gl_7.1.0-9_all.deb xlibmesa-glu_7.1.0-9_all.deb to pool/main/x/xorg/xlibmesa-glu_7.1.0-9_all.deb xlibs-data_7.1.0-9_all.deb to pool/main/x/xorg/xlibs-data_7.1.0-9_all.deb xlibs-static-dev_7.1.0-9_all.deb to pool/main/x/xorg/xlibs-static-dev_7.1.0-9_all.deb xorg-dev_7.1.0-9_all.deb to pool/main/x/xorg/xorg-dev_7.1.0-9_all.deb xorg_7.1.0-9.dsc to pool/main/x/xorg/xorg_7.1.0-9.dsc xorg_7.1.0-9.tar.gz to pool/main/x/xorg/xorg_7.1.0-9.tar.gz xorg_7.1.0-9_all.deb to pool/main/x/xorg/xorg_7.1.0-9_all.deb xserver-xfree86_7.1.0-9_all.deb to pool/main/x/xorg/xserver-xfree86_7.1.0-9_all.deb xserver-xorg-input-all_7.1.0-9_i386.deb to pool/main/x/xorg/xserver-xorg-input-all_7.1.0-9_i386.deb xserver-xorg-video-all_7.1.0-9_i386.deb to pool/main/x/xorg/xserver-xorg-video-all_7.1.0-9_i386.deb xserver-xorg_7.1.0-9_all.deb to pool/main/x/xorg/xserver-xorg_7.1.0-9_all.deb A summary of the changes between this version and the previous one is attached. Thank you for reporting the bug, which will now be closed. If you have further comments please address them to [EMAIL PROTECTED], and the maintainer will reopen the bug report if appropriate. Debian distribution maintenance software pp. David Nusinow <[EMAIL PROTECTED]> (supplier of updated xorg package) (This message was generated automatically at their request; if you believe that there is a problem with it please contact the archive administrators by mailing [EMAIL PROTECTED]) -BEGIN PGP SIGNED MESSAGE- Hash: SHA1 Format: 1.7 Date: Tue, 19 Dec 2006 22:19:00 -0500 Source: xorg Binary: x-window-system xlibs-static-dev xlibmesa-dri xserver-xorg-video-all xserver-xorg xorg-dev xserver-xorg-input-all libglu1-xorg-dev xlibmesa-glu xlibmesa-gl x11-common xserver-xfree86 xlibmesa-gl-dev x-window-system-core libglu1-xorg xlibs-data xorg Architecture: source all i386 Version: 1:7.1.0-9 Distribution: unstable Urgency: high Maintainer: David Nusinow <[EMAIL PROTECTED]> Changed-By: David Nusinow <[EMAIL PROTECTED]> Description: libglu1-xorg - transitional package for Debian etch libglu1-xorg-dev - transitional package for Debian etch x-window-system -
Processed: found 403853 in 3.3.0-5.4
Processing commands for [EMAIL PROTECTED]: > # Automatically generated email from bts, devscripts version 2.9.26 > found 403853 3.3.0-5.4 Bug#403853: xtel: install files in /usr/lib/X11/fonts/, conflicts with x11-common Bug marked as found in version 3.3.0-5.4. > End of message, stopping processing here. Please contact me if you need assistance. Debian bug tracking system administrator (administrator, Debian Bugs database) -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
Processed: libpng14-dev tags 403393 experimental
Processing commands for [EMAIL PROTECTED]: > tags 403393 experimental Bug#403393: stellarium_0.8.2-1(hppa/experimental): FTBFS: pngdefs.h: No such file or directory There were no tags set. Tags added: experimental > thanks Stopping processing here. Please contact me if you need assistance. Debian bug tracking system administrator (administrator, Debian Bugs database) -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
Bug#396631: Same problem with latest version of apache2/libapr1
[Marcos Torres Marado] > Shouldn't this bug be marked as closed? While the existing fix works, it's not quite in its final form. We were waiting for someone to test my preferred patch. Now that he's done so, we'll use that and close the bug. Thanks, Peter signature.asc Description: Digital signature
Bug#403818: xserver-xorg: no video or keyboard after upgrading to sarge (deps too loose)
On Wed, Dec 20, 2006 at 02:47:40AM +0100, Steinar H. Gunderson wrote: > On Tue, Dec 19, 2006 at 08:40:26PM -0500, David Nusinow wrote: > > Ouch. This is a bug in aptitude, aiui. It should be choosing the first > > option if nothing is currently installed, and allowing the second to > > substitute. > > Probably something in -all caused a conflict, and the conflict resolution > manager preferred a random choice providing -input instead. I can't imagine what that would be... I'd love to know. Was this on x86? > > Either way, it's probably too late to fix this in aptitude for etch, so a > > workaround is necessary... > > Most upgrades will probably happen with the aptitude from sarge, BTW. Right. I'm retarded :-) > > If I build a package set with this, will you be able to test it to make > > sure it works? > > Unfortunately, no; the machine was just my mother's workstation. However, > I've picked out the dpkg status backup and reconstructed the aptitude lines; > talk to Julien Cristau, he has the data in question. Got it, thank you. I'll take a look. > >> Also, xorg.conf was blank after the upgrade, but I guess that's for > >> another bug, which will be far harder to track down... :-) > > Gyah... did xserver-xorg error out during postinst? I'll have to look for a > > codepath that can cause that beyond errors. > > No, it didn't error out. It just showed the warning debconf template, and > then continued as nothing was wrong. > > Note that due to some conflicts etc., the upgrading line was "aptitude > install gnome" (the full dist-upgrade was not done until later); it _might_ > be that a full dist-upgrade is luckier somehow, but I'm not going to bet on > it. Just giving aptitude the explicit hint that the user would probably like > to have -input-(kbd,mouse) and -video-vesa sounds like the best hint to me, > especially as they're not likely to conflict with anything (so the conflict > resolver accepts that more or less right away). Perhaps for video 'xserver-xorg-video-all | xserver-xorg-video-vesa' in the recommends. This doesn't map to input though, since we'd need both -kbd and -mouse. Simply duplicating the recommendation may be possible though (xserver-xorg-input-all | xserver-xorg-input-kbd, xserver-xorg-input-all | xserver-xorg-input-mouse). - David Nusinow -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
Processed: cloning 403765, reassign 403765 to xutils-dev, reassign -2 to xtel, severity of -2 is serious ...
Processing commands for [EMAIL PROTECTED]: > # Automatically generated email from bts, devscripts version 2.9.26 > clone 403765 -2 Bug#403765: x11-common: trying to overwrite `/usr/lib/X11/fonts' which is also in package xtel Bug 403765 cloned as bug 403853. > reassign 403765 xutils-dev Bug#403765: x11-common: trying to overwrite `/usr/lib/X11/fonts' which is also in package xtel Bug reassigned from package `x11-common' to `xutils-dev'. > reassign -2 xtel Bug#403853: x11-common: trying to overwrite `/usr/lib/X11/fonts' which is also in package xtel Bug reassigned from package `x11-common' to `xtel'. > severity -2 serious Bug#403853: x11-common: trying to overwrite `/usr/lib/X11/fonts' which is also in package xtel Severity set to `serious' from `normal' > retitle -2 xtel: install files in /usr/lib/X11/fonts/, conflicts with > x11-common Bug#403853: x11-common: trying to overwrite `/usr/lib/X11/fonts' which is also in package xtel Changed Bug title. > End of message, stopping processing here. Please contact me if you need assistance. Debian bug tracking system administrator (administrator, Debian Bugs database) -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
Processed: Re: segfault on baz ancestry-graph
Processing commands for [EMAIL PROTECTED]: > found 403849 1.4.2-5.2 Bug#403849: segfault on baz ancestry-graph Bug marked as found in version 1.4.2-5.2. > thanks Stopping processing here. Please contact me if you need assistance. Debian bug tracking system administrator (administrator, Debian Bugs database) -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
Bug#403818: xserver-xorg: no video or keyboard after upgrading to sarge (deps too loose)
On Tue, Dec 19, 2006 at 08:40:26PM -0500, David Nusinow wrote: > Ouch. This is a bug in aptitude, aiui. It should be choosing the first > option if nothing is currently installed, and allowing the second to > substitute. Probably something in -all caused a conflict, and the conflict resolution manager preferred a random choice providing -input instead. > Either way, it's probably too late to fix this in aptitude for etch, so a > workaround is necessary... Most upgrades will probably happen with the aptitude from sarge, BTW. >> 1. Make the depends into "xserver-xorg-video, xserver-xorg-input", and >> add Recommends for the -all packages instead. > If I build a package set with this, will you be able to test it to make > sure it works? Unfortunately, no; the machine was just my mother's workstation. However, I've picked out the dpkg status backup and reconstructed the aptitude lines; talk to Julien Cristau, he has the data in question. >> Also, xorg.conf was blank after the upgrade, but I guess that's for >> another bug, which will be far harder to track down... :-) > Gyah... did xserver-xorg error out during postinst? I'll have to look for a > codepath that can cause that beyond errors. No, it didn't error out. It just showed the warning debconf template, and then continued as nothing was wrong. Note that due to some conflicts etc., the upgrading line was "aptitude install gnome" (the full dist-upgrade was not done until later); it _might_ be that a full dist-upgrade is luckier somehow, but I'm not going to bet on it. Just giving aptitude the explicit hint that the user would probably like to have -input-(kbd,mouse) and -video-vesa sounds like the best hint to me, especially as they're not likely to conflict with anything (so the conflict resolver accepts that more or less right away). /* Steinar */ -- Homepage: http://www.sesse.net/ -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
Bug#403849: segfault on baz ancestry-graph
found 403849 1.4.2-5.2 thanks On Wed, Dec 20, 2006 at 02:41:43AM +0100, Steinar H. Gunderson wrote: > During import to bzr, I got a segfault. The following command reproduces > it: FWIW, binary searching using snapshot.debian.net shows that this segfault was introduced in version 1.4.2-5.2 (-5.1 is fine). /* Steinar */ -- Homepage: http://www.sesse.net/ -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
Bug#341397: artwiz-cursor: package is indeed *horribly* broken
Package: artwiz-cursor
Followup-For: Bug #341397
I don't know why I tried to install this package, but after the
installation failed miserably, I tried to purge it. At the time the
purging seemed to be successful.
Upon restarting Xorg, I got the following:
Build Date: 07 July 2006
Before reporting problems, check http://wiki.x.org
to make sure that you have the latest version.
Module Loader present
Markers: (--) probed, (**) from config file, (==) default setting,
(++) from command line, (!!) notice, (II) informational,
(WW) warning, (EE) error, (NI) not implemented, (??) unknown.
(==) Log file: "/var/log/Xorg.0.log", Time: Tue Dec 19 20:47:09 2006
(==) Using config file: "/etc/X11/xorg.conf"
xkb_keycodes { include "xfree86+aliases(qwerty)" };
xkb_types{ include "complete" };
xkb_compatibility{ include "complete" };
xkb_symbols { include "pc(pc105)+us" };
xkb_geometry { include "pc(pc104)" };
Fatal server error:
could not open default cursor font 'cursor'
XIO: fatal IO error 104 (Connection reset by peer) on X server ":0.0"
after 0 requests (0 known processed) with 0 events remaining.
Hilarity indeed. =P
A simple `dpkg-divert --remove /usr/share/fonts/X11/misc/cursor.pcf.gz
&& apt-get --reinstall install xfonts-base` fixed the damage
though.
-- System Information:
Debian Release: 4.0
APT prefers testing
APT policy: (600, 'testing'), (500, 'testing-proposed-updates'), (50,
'unstable'), (1, 'experimental')
Architecture: i386 (i686)
Shell: /bin/sh linked to /bin/bash
Kernel: Linux 2.6.19-cks2
Locale: LANG=en_US.UTF-8, LC_CTYPE=en_US.UTF-8 (charmap=UTF-8)
signature.asc
Description: Digital signature
Bug#403818: xserver-xorg: no video or keyboard after upgrading to sarge (deps too loose)
On Tue, Dec 19, 2006 at 11:29:07PM +0100, Steinar H. Gunderson wrote: > Package: xserver-xorg > Version: 1:7.1.0-8 > Severity: serious > Justification: 23:28 < vorlon> Sesse: I'd call it RC, no? Definitely. I'm treating it as grave even if it's not officially so. > After dist-upgrading (using etch's aptitude) from sarge to etch, one > machine here was completely without keyboard or mouse support, and X > refused to work. > > A bit of hunting revealed that aptitude had pulled in > xserver-xorg-input-magictouch and xserver-xorg-video-siliconmotion to > fulfill xserver-xorg's dependencies on "xserver-xorg-video-all | > xserver-xorg-video" and "xserver-xorg-input-all | xserver-xorg-input", > respectively. This is clearly not satisfiable. Ouch. This is a bug in aptitude, aiui. It should be choosing the first option if nothing is currently installed, and allowing the second to substitute. On an upgrade, none of these would be installed, so it would choose the first options in both instances. In this case, that would be xserver-xorg-video-all and xserver-xorg-input-all by default. Is this a misunderstanding? Either way, it's probably too late to fix this in aptitude for etch, so a workaround is necessary... > AFAICS there are two OK ways of solving this: > > 1. Make the depends into "xserver-xorg-video, xserver-xorg-input", and > add Recommends for the -all packages instead. If I build a package set with this, will you be able to test it to make sure it works? > 2. Add xserver-xorg-input-kbd and xserver-xorg-input-mouse explicitly > to the list of depends (or possibly recommends?), which should make > aptitude Do The Right Thing (hopefully). This won't solve the issue > for video, though. I can add xserver-xorg-video-vesa as a depends. At the very least we'd have a fail-safe option. The xserver-xorg xorg.conf creation scripting should work with this too, in theory, although I'll have to check that. > One could use a combination of 1 and 2. Better safe than sorry :-) > Note that the request to "aptitude install xorg", which was given by > debconf, was a no-op, since all the dependencies were already fulfilled. > > Also, xorg.conf was blank after the upgrade, but I guess that's for > another bug, which will be far harder to track down... :-) Gyah... did xserver-xorg error out during postinst? I'll have to look for a codepath that can cause that beyond errors. - David Nusinow -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
Bug#403849: segfault on baz ancestry-graph
Package: bazaar Version: 1.4.2-5.2+b1 Severity: grave During import to bzr, I got a segfault. The following command reproduces it: pannekake:~> baz ancestry-graph [EMAIL PROTECTED]/pitch--mainline--0.1--patch-14 zsh: segmentation fault baz ancestry-graph [EMAIL PROTECTED]/pitch--mainline--0.1--patch-1 The archive in question is available from http://arch.sesse.net/[EMAIL PROTECTED] . Downgrading bazaar to the version in sarge made the import work flawlessly, so this must be a newer issue somehow. -- System Information: Debian Release: 4.0 APT prefers testing APT policy: (800, 'testing'), (500, 'unstable'), (500, 'stable'), (1, 'experimental') Architecture: i386 (x86_64) Shell: /bin/sh linked to /bin/bash Kernel: Linux 2.6.19 Locale: LANG=en_DK.UTF-8, LC_CTYPE=en_DK.UTF-8 (charmap=UTF-8) Versions of packages bazaar depends on: ii diff 2.8.1-11 File comparison utilities ii gawk 1:3.1.5.dfsg-4 GNU awk, a pattern scanning and pr ii libc6 2.3.6.ds1-8GNU C Library: Shared libraries ii libgpgme111.1.2-2GPGME - GnuPG Made Easy ii libneon26-gnutls 0.26.2-3 An HTTP and WebDAV client library ii patch 2.5.9-4Apply a diff file to an original bazaar recommends no packages. -- no debconf information -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
Processed: your mail
Processing commands for [EMAIL PROTECTED]: > tags 245826 + pending Bug#245826: t-gnus: please fix lintian errors & warnings Tags were: patch Tags added: pending > tags 403152 + pending Bug#403152: t-gnus: Please add a depends against emacsen or emacs-snapshot There were no tags set. Tags added: pending > thanks Stopping processing here. Please contact me if you need assistance. Debian bug tracking system administrator (administrator, Debian Bugs database) -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
Bug#403789: gnucash regression
Thomas Bushnell BSG writes: > Your NMU of gnucash has introduced an FTBFS regression. I trust you are > fixing it, right? not my problem; I'm glad that we found the build failure before the release; CCing -arm to point out the build failure. -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
Bug#403842: MkProg: hmake: the compiler 'ghc' is not known.
Package: hmake Version: 3.12-1 Severity: grave % hmake -ghc test.hs MkProg: hmake: the compiler 'ghc' is not known. Stop - hmake dependency error. -- System Information: Debian Release: 4.0 APT prefers unstable APT policy: (500, 'unstable') Architecture: amd64 (x86_64) Shell: /bin/sh linked to /bin/bash Kernel: Linux 2.6.19 Locale: LANG=C, LC_CTYPE=C (charmap=ANSI_X3.4-1968) Versions of packages hmake depends on: ii ghc6 6.6-3 GHC - the Glasgow Haskell Compilat ii haskell-utils 1.7Utilities used by the Debian Haske ii libc6 2.3.6.ds1-9GNU C Library: Shared libraries ii libgmp3c2 2:4.2.1+dfsg-4 Multiprecision arithmetic library ii libncurses5 5.5-5 Shared libraries for terminal hand ii libreadline5 5.2-1 GNU readline and history libraries hmake recommends no packages. -- no debconf information -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
Bug#401938: libapache2-mod-fcgid: Some stack trace info
Package: libapache2-mod-fcgid
Version: 2.0-1
Followup-For: Bug #401938
I can confirm the problem. It looks like mod_fcgid doesn't like it when the
server (a Ruby dispatcher in my case) is closing the connection right after
the fastcgi request has been sent (deduced from strace info). I'm on a semi-
production server, I've only recompiled the module with debug symbols:
# gdb /usr/sbin/apache2
...
(gdb) set args -DNO_DETACH -DONE_PROCESS
...
Program received signal SIGSEGV, Segmentation fault.
[Switching to Thread 16384 (LWP 7814)]
0x0058 in ?? ()
(gdb) bt
#0 0x0058 in ?? ()
#1 0x4079aac4 in getsfunc_fcgid_BRIGADE (buf=0xbfffa2d4 "Status", len=8191,
arg=0x82fadf0) at fcgid_bridge.c:212
#2 0x08079afc in ap_scan_script_header_err_core ()
#3 0x4079b289 in handle_request (r=0x82f62b8, argv0=0x82f9da8
"/var/www/sandbox.af83.com/wiki/public/dispatch.fcgi",
wrapper_conf=0x0, output_brigade=0x82fad50) at fcgid_bridge.c:395
#4 0x4079baa6 in bridge_request (r=0x82f62b8, role=1, argv0=0x82f9da8
"/var/www/sandbox.af83.com/wiki/public/dispatch.fcgi",
wrapper_conf=0x0) at fcgid_bridge.c:590
#5 0x4079fdca in fcgid_handler (r=0x82f62b8) at mod_fcgid.c:182
#6 0x08074587 in ap_run_handler ()
#7 0x08077731 in ap_invoke_handler ()
#8 0x080845aa in ap_internal_redirect ()
#9 0x40e29d7c in ?? () from /usr/lib/apache2/modules/mod_rewrite.so
#10 0x082f62a0 in ?? ()
#11 0x082ebd68 in ?? ()
#12 0x in ?? ()
(gdb) frame 1
#1 0x4079aac4 in getsfunc_fcgid_BRIGADE (buf=0xbfffa2d4 "Status", len=8191,
arg=0x82fadf0) at fcgid_bridge.c:212
(gdb) print *e
$3 = {link = {next = 0x82fadf4, prev = 0x82fadf4}, type = 0x82e9d28, length =
137342304, start = 4613506809820327408,
data = 0x8061060, free = 0x82ebd30, list = 0xc}
(gdb) print *e->type
$8 = {name = 0x82e3ad8 "�v\n\b }.\b�\f\r\b�v\n\b�;.\b", num_func = 137247312,
is_metadata = 137274744, destroy = 0x82e9d10,
read = 0x58, setaside = 0x82e9d28, split = 0x82e9d10, copy = 0}
The module was compiled from CVS, the fcgid_bridge.c:212 line is:
rv = apr_bucket_read(e, &bucket_data, &bucket_data_len, APR_BLOCK_READ);
... where apr_bucket_read() is a macro calling the e->type->read function
which is obviously not initialized (0x58!).
-- System Information:
Debian Release: 4.0
APT prefers testing
APT policy: (500, 'testing')
Architecture: i386 (i686)
Shell: /bin/sh linked to /bin/bash
Kernel: Linux 2.6.19.1
Locale: LANG=en_US.UTF-8, LC_CTYPE=en_US.UTF-8 (charmap=UTF-8)
Bug#403841: Does not work
Package: hat Version: 2.05-7 Severity: grave % cat z.hs data Node = Node String [Node] | Text String tag t e@(Node t' _) | t == t' = [e] tag _ _ = [] children (Node _ c) = c children _ = [] text (Text s) = [s] text _ = [] container s x = tag s x >>= children textNode s x = container s x >>= text mainA x = do z <- container "xml" x a <- textNode "noBallots" z b <- textNode "noDs" z return (a, b) main = do print $ mainA (Node "xml" [Node "noBallots" [Text "nb"], Node "noDs" [Text "nd"]]) % hmake -hat z hat-trans z.hs Wrote Hat/z.hs /usr/bin/haskell-compiler -c -package hat -o Hat/z.o Hat/z.hs /usr/bin/haskell-compiler -package hat -o z Hat/z.o % ./z [] % hat-trail z hat-trail: attempt to read beyond end of file hat-trail: offset = 0x300, filesize = 0x28b6 hat-trail: errno = 0 (Success) -- System Information: Debian Release: 4.0 APT prefers unstable APT policy: (500, 'unstable') Architecture: amd64 (x86_64) Shell: /bin/sh linked to /bin/bash Kernel: Linux 2.6.19 Locale: LANG=C, LC_CTYPE=C (charmap=ANSI_X3.4-1968) Versions of packages hat depends on: ii libc6 2.3.6.ds1-9GNU C Library: Shared libraries ii libghc6-hat-dev 2.05-7 Haskell source-level tracer librar ii libglib1.21.2.10-17 The GLib library of C routines ii libgmp3c2 2:4.2.1+dfsg-4 Multiprecision arithmetic library ii libncurses5 5.5-5 Shared libraries for terminal hand ii libreadline5 5.2-1 GNU readline and history libraries Versions of packages hat recommends: ii hmake 3.12-1 The Haskell Make System -- no debconf information -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
Bug#403836: hat depends on "resize" command
Package: hat Version: 2.05-7 Severity: serious hat-observe appears to require the "resize" command, probably the one from the xutils package. Not exactly a reasonable dependency -- since my system has no x11 on it. -- System Information: Debian Release: 4.0 APT prefers unstable APT policy: (500, 'unstable') Architecture: amd64 (x86_64) Shell: /bin/sh linked to /bin/bash Kernel: Linux 2.6.19 Locale: LANG=C, LC_CTYPE=C (charmap=ANSI_X3.4-1968) Versions of packages hat depends on: ii libc6 2.3.6.ds1-9GNU C Library: Shared libraries ii libghc6-hat-dev 2.05-7 Haskell source-level tracer librar ii libglib1.21.2.10-17 The GLib library of C routines ii libgmp3c2 2:4.2.1+dfsg-4 Multiprecision arithmetic library ii libncurses5 5.5-5 Shared libraries for terminal hand ii libreadline5 5.2-1 GNU readline and history libraries Versions of packages hat recommends: ii hmake 3.12-1 The Haskell Make System -- no debconf information -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
Bug#403659: marked as done (sash: no longer statically linked)
Your message dated Tue, 19 Dec 2006 23:47:04 + with message-id <[EMAIL PROTECTED]> and subject line Bug#403659: fixed in sash 3.7-7.2 has caused the attached Bug report to be marked as done. This means that you claim that the problem has been dealt with. If this is not the case it is now your responsibility to reopen the Bug report if necessary, and/or fix the problem forthwith. (NB: If you are a system administrator and have no idea what I am talking about this indicates a serious mail system misconfiguration somewhere. Please contact me immediately.) Debian bug tracking system administrator (administrator, Debian Bugs database) --- Begin Message --- Package: sash Version: 3.7-7.1 Severity: grave Justification: renders package unusable NMU of this package appears to be no longer statically linked. -- System Information: Debian Release: 4.0 APT prefers testing APT policy: (950, 'testing'), (750, 'unstable'), (550, 'stable') Architecture: i386 (i686) Shell: /bin/sh linked to /bin/bash Kernel: Linux 2.6.17-2-k7 Locale: LANG=C, [EMAIL PROTECTED] (charmap=ISO-8859-15) Versions of packages sash depends on: ii debconf [debconf-2.0] 1.5.8Debian configuration management sy ii libc6 2.3.6.ds1-8 GNU C Library: Shared libraries ii lockfile-progs 0.1.10 Programs for locking and unlocking ii passwd 1:4.0.18.1-6 change and administer password and ii zlib1g 1:1.2.3-13 compression library - runtime sash recommends no packages. -- debconf information excluded --- End Message --- --- Begin Message --- Source: sash Source-Version: 3.7-7.2 We believe that the bug you reported is fixed in the latest version of sash, which is due to be installed in the Debian FTP archive: sash_3.7-7.2.diff.gz to pool/main/s/sash/sash_3.7-7.2.diff.gz sash_3.7-7.2.dsc to pool/main/s/sash/sash_3.7-7.2.dsc sash_3.7-7.2_i386.deb to pool/main/s/sash/sash_3.7-7.2_i386.deb A summary of the changes between this version and the previous one is attached. Thank you for reporting the bug, which will now be closed. If you have further comments please address them to [EMAIL PROTECTED], and the maintainer will reopen the bug report if appropriate. Debian distribution maintenance software pp. Joey Hess <[EMAIL PROTECTED]> (supplier of updated sash package) (This message was generated automatically at their request; if you believe that there is a problem with it please contact the archive administrators by mailing [EMAIL PROTECTED]) -BEGIN PGP SIGNED MESSAGE- Hash: SHA1 Format: 1.7 Date: Tue, 19 Dec 2006 18:16:21 -0500 Source: sash Binary: sash Architecture: source i386 Version: 3.7-7.2 Distribution: unstable Urgency: low Maintainer: Tollef Fog Heen <[EMAIL PROTECTED]> Changed-By: Joey Hess <[EMAIL PROTECTED]> Description: sash - Stand-alone shell Closes: 403659 Changes: sash (3.7-7.2) unstable; urgency=low . * NMU * Apparently CDBS decided to start overwriting the LDFLAGS setting, which made sash no longer statically linked. Work around this brain-damage. Closes: #403659 Files: fbdfd2f0be530704b265430a47b4b679 608 shells optional sash_3.7-7.2.dsc cd7943f5485cd984aa721f1db1467263 19243 shells optional sash_3.7-7.2.diff.gz 557fce70f042cba711ddccda23f2 307968 shells optional sash_3.7-7.2_i386.deb -BEGIN PGP SIGNATURE- Version: GnuPG v1.4.6 (GNU/Linux) iD8DBQFFiHfr2tp5zXiKP0wRApDdAKDCncvZ3Q+IPJ6+Hy+Zdk4BsG5vAwCgsP4N Pw4zMdIM5qT8JTqYJqdDtwI= =/+uS -END PGP SIGNATURE- --- End Message ---
Bug#396631: Same problem with latest version of apache2/libapr1
* H. S. Teoh ([EMAIL PROTECTED]) [061219 18:39]: > On Tue, Dec 19, 2006 at 09:55:39AM +0100, Andreas Barth wrote: > [...] > > I uploaded packages for this architecture now on > > http://people.debian.org/~aba/apr/ - the changes-file is signed by me > > so that you know it was really me. > [...] > > I just tested it. It works flawlessly! Cool. Ok, in this case I intend to upload another package tomorrow, finally fixing this bug. Cheers, Andi -- http://home.arcor.de/andreas-barth/ -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
Processed: sash: diff for NMU version 3.7-7.2
Processing commands for [EMAIL PROTECTED]: > tags 403659 + patch Bug#403659: sash: no longer statically linked There were no tags set. Tags added: patch > thanks Stopping processing here. Please contact me if you need assistance. Debian bug tracking system administrator (administrator, Debian Bugs database) -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
Bug#403659: sash: diff for NMU version 3.7-7.2
tags 403659 + patch thanks Hi, Attached is the diff for my sash 3.7-7.2 NMU. CDBS considered harmful, and a PITA to NMU. -- see shy jo diff -u sash-3.7/debian/rules sash-3.7/debian/rules --- sash-3.7/debian/rules +++ sash-3.7/debian/rules @@ -3,6 +3,8 @@ pkgdir := `pwd`/debian/sash DEB_MAKE_INSTALL_TARGET=install BINDIR=$(pkgdir)/bin MANDIR=$(pkgdir)/usr/share/man/man1 +# work around cdbs brain-damage +LDFLAGS=-static -s include /usr/share/cdbs/1/class/makefile.mk include /usr/share/cdbs/1/rules/debhelper.mk diff -u sash-3.7/debian/changelog sash-3.7/debian/changelog --- sash-3.7/debian/changelog +++ sash-3.7/debian/changelog @@ -1,3 +1,12 @@ +sash (3.7-7.2) unstable; urgency=low + + * NMU + * Apparently CDBS decided to start overwriting the LDFLAGS setting, which +made sash no longer statically linked. Work around this brain-damage. +Closes: #403659 + + -- Joey Hess <[EMAIL PROTECTED]> Tue, 19 Dec 2006 18:16:21 -0500 + sash (3.7-7.1) unstable; urgency=low * Non-maintainer upload to fix longstanding l10n issues signature.asc Description: Digital signature
Processed: severity of 403621 is important
Processing commands for [EMAIL PROTECTED]: > # Automatically generated email from bts, devscripts version 2.9.27 > # non-copyrightable interface definitions, not RC > severity 403621 important Bug#403621: Incomplete copyright/license information: Additional restrictions to GPL Severity set to `important' from `serious' > End of message, stopping processing here. Please contact me if you need assistance. Debian bug tracking system administrator (administrator, Debian Bugs database) -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
Bug#389579: Unmerging
unmerge 389579 400879 stop Matthew confirmed in a private mail that this package is not supposed to be released with etch as it is not actively supported by upstream (him) and will thus probably be orphaned soon. bye, -christian- -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
Bug#389068: #389068: any progress ?
On Tue, 19 Dec 2006 23:28:52 +0100, Lucas Nussbaum wrote: > This bug is still open, and it might prevent jabref from being included > in etch. Has any progress been done ? Yes and no. JabRef now uses 8 precompiled libraries, 2 are in Debian and I've started to package the others. Some of them are not that tricky but one of them uses some precompiled libs too, and the last one downloads dozens of precompiled libraries from the web and uses them for building - a real mess. > It would a shame if jabref wasn't included into etch ... I don't think that's realistic unless some Java gurus jump up and help in preparing these 6 packages. If you are interested you can find the preliminary packages at http://www.toastfreeware.priv.at/debian/ Thanks for your interest in JabRef, gregor -- .''`. http://info.comodo.priv.at/ | gpg key ID: 0x00F3CFE4 : :' : debian: the universal operating system - http://www.debian.org/ `. `' member of https://www.vibe.at/ | how to reply: http://got.to/quote/ `-NP: Joint Venture: Freitag signature.asc Description: Digital signature
Bug#394392: msync() in recent kernels fails LSB
On Tue, Dec 19, 2006 at 05:08:24PM +0100, Martin Michlmayr wrote: > > 10|852 /tset/LSB.os/mfiles/msync_P/T.msync_P 22:58:49|TC Start, scenario > > ref 858-0 > > FSG internal testing showed that Fedora Core 5's 2.6.18 kernel does not > > fail in the same way. I believe I've traced it to a backported change > > from 2.6.19 development. The specific commit touching msync() is > > 204ec841fbea3e5138168edbc3a76d46747cc987 in git; it relies on several > > commits immediately preceding it. I've built Linus's tree on amd64, and > > it passes the test. I have not, however, built a 2.6.18 kernel with > > this patch and tested it, though it's the only patch in the Fedora > > kernel which touches the msync() code. > So it seems that the patches needed for msync() conformance we applied > from 2.6.19 to our 2.6.18 cause filesystem corruption, see the current > discussion on this on lkml. From what I understand it, plain 2.6.18 > is not LSB 3.1 conform and you need some fixes which are associated > with filesystem corruption. While Andrew, Linus and co are currently > trying to come up with a patch, I think it might be better for us to > simply back out these patches. What doe it take to get an exception > for this LSB test? Surely the reasons cited above (fails with 2.6.18, > a fairly current kernel and the patches to fix it are associated with > fs corruption) are pretty good arguments for an exception... Reverting this is an ABI change which may be installer-affecting (I don't know if it is, but unlike most of the other pressing ABI changes this one would apply to the kernels used by the installer). If we think the fix may be available soon, I think we're better off pushing forward rather than reverting. If the decision *is* made to revert, release-wise it's best if the kernel team can bundle up any final ABI changes they want to make for etch at the same time so that we can get it done with and get d-i RC2 out. Thanks, -- Steve Langasek Give me a lever long enough and a Free OS Debian Developer to set it on, and I can move the world. [EMAIL PROTECTED] http://www.debian.org/ -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
Processed: add tag pending
Processing commands for [EMAIL PROTECTED]: > tags 403767 + pending Bug#403767: Licensing information is missing There were no tags set. Tags added: pending > thanks Stopping processing here. Please contact me if you need assistance. Debian bug tracking system administrator (administrator, Debian Bugs database) -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
Processed: bug maintainance
Processing commands for [EMAIL PROTECTED]: > close 386259 1.00-1 Bug#386259: FTBFS: aclocal: macro `AM_PROG_MKDIR_P' required but not defined 'close' is deprecated; see http://www.debian.org/Bugs/Developer#closing. Bug marked as fixed in version 1.00-1, send any further explanations to Martin Michlmayr <[EMAIL PROTECTED]> > close 386259 0.92+svn-r217-1 Bug#386259: FTBFS: aclocal: macro `AM_PROG_MKDIR_P' required but not defined 'close' is deprecated; see http://www.debian.org/Bugs/Developer#closing. Bug marked as fixed in version 0.92+svn-r217-1, send any further explanations to Martin Michlmayr <[EMAIL PROTECTED]> > close 402100 1.00-1 Bug#402100: enigma: 1.00 beta should not enter etch 'close' is deprecated; see http://www.debian.org/Bugs/Developer#closing. Bug marked as fixed in version 1.00-1, send any further explanations to Erich Schubert <[EMAIL PROTECTED]> > thanks Stopping processing here. Please contact me if you need assistance. Debian bug tracking system administrator (administrator, Debian Bugs database) -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
Bug#403753: marked as done (addresses-goodies-for-gnustep: file conflict with adtool)
Your message dated Tue, 19 Dec 2006 22:47:02 + with message-id <[EMAIL PROTECTED]> and subject line Bug#403753: fixed in addresses-for-gnustep 0.4.6-8 has caused the attached Bug report to be marked as done. This means that you claim that the problem has been dealt with. If this is not the case it is now your responsibility to reopen the Bug report if necessary, and/or fix the problem forthwith. (NB: If you are a system administrator and have no idea what I am talking about this indicates a serious mail system misconfiguration somewhere. Please contact me immediately.) Debian bug tracking system administrator (administrator, Debian Bugs database) --- Begin Message --- Package: addresses-goodies-for-gnustep Version: 0.4.6-7 Severity: serious Hello Eric, The package addresses-goodies-for-gnustep includes the file /usr/share/man/man1/adtool.1.gz which is also part of the package 'adtool'. adtool in Sarge also includes /usr/share/man/man1/adtool.1.gz. Cheers, -- Bill. <[EMAIL PROTECTED]> Imagine a large blue swirl here. --- End Message --- --- Begin Message --- Source: addresses-for-gnustep Source-Version: 0.4.6-8 We believe that the bug you reported is fixed in the latest version of addresses-for-gnustep, which is due to be installed in the Debian FTP archive: addresses-for-gnustep_0.4.6-8.diff.gz to pool/main/a/addresses-for-gnustep/addresses-for-gnustep_0.4.6-8.diff.gz addresses-for-gnustep_0.4.6-8.dsc to pool/main/a/addresses-for-gnustep/addresses-for-gnustep_0.4.6-8.dsc addresses-goodies-for-gnustep_0.4.6-8_i386.deb to pool/main/a/addresses-for-gnustep/addresses-goodies-for-gnustep_0.4.6-8_i386.deb addresses.framework_0.4.6-8_all.deb to pool/main/a/addresses-for-gnustep/addresses.framework_0.4.6-8_all.deb addressmanager.app_0.4.6-8_i386.deb to pool/main/a/addresses-for-gnustep/addressmanager.app_0.4.6-8_i386.deb addressview.framework_0.4.6-8_all.deb to pool/main/a/addresses-for-gnustep/addressview.framework_0.4.6-8_all.deb libaddresses-dev_0.4.6-8_i386.deb to pool/main/a/addresses-for-gnustep/libaddresses-dev_0.4.6-8_i386.deb libaddresses0_0.4.6-8_i386.deb to pool/main/a/addresses-for-gnustep/libaddresses0_0.4.6-8_i386.deb libaddressview-dev_0.4.6-8_i386.deb to pool/main/a/addresses-for-gnustep/libaddressview-dev_0.4.6-8_i386.deb libaddressview0_0.4.6-8_i386.deb to pool/main/a/addresses-for-gnustep/libaddressview0_0.4.6-8_i386.deb A summary of the changes between this version and the previous one is attached. Thank you for reporting the bug, which will now be closed. If you have further comments please address them to [EMAIL PROTECTED], and the maintainer will reopen the bug report if appropriate. Debian distribution maintenance software pp. Hubert Chan <[EMAIL PROTECTED]> (supplier of updated addresses-for-gnustep package) (This message was generated automatically at their request; if you believe that there is a problem with it please contact the archive administrators by mailing [EMAIL PROTECTED]) -BEGIN PGP SIGNED MESSAGE- Hash: RIPEMD160 Format: 1.7 Date: Tue, 19 Dec 2006 16:06:18 -0500 Source: addresses-for-gnustep Binary: libaddressview0 addressmanager.app addresses.framework libaddresses0 addresses-goodies-for-gnustep libaddressview-dev addressview.framework libaddresses-dev Architecture: source i386 all Version: 0.4.6-8 Distribution: unstable Urgency: low Maintainer: Eric Heintzmann <[EMAIL PROTECTED]> Changed-By: Hubert Chan <[EMAIL PROTECTED]> Description: addresses-goodies-for-gnustep - Personal Address Manager for GNUstep (Goodies) addresses.framework - Database API backend framework for GNUstep addressmanager.app - Personal Address Manager for GNUstep addressview.framework - Address display/edit framework for GNUstep libaddresses-dev - Database API backend framework for GNUstep (development files) libaddresses0 - Database API backend framework for GNUstep (library files) libaddressview-dev - Address display/edit framework for GNUstep (development files) libaddressview0 - Address display/edit framework for GNUstep (library files) Closes: 403753 Changes: addresses-for-gnustep (0.4.6-8) unstable; urgency=low . * Rename adtool to addresstool to avoid conflict with adtool package. (closes: #403753) * Update debian/control to agree with overrides file for .framework packages. Files: 17b58bfe737dbad4ab9f7bf129f9258f 925 mail optional addresses-for-gnustep_0.4.6-8.dsc 17e8e34483e92d395965e92f55cf5be4 14542 mail optional addresses-for-gnustep_0.4.6-8.diff.gz 86d5bcef2feb8eff9b89f493cc4def7d 8136 libs optional addresses.framework_0.4.6-8_all.deb 77ad79b4ce65d21634564a5ea9d94fff 8124 libs optional addressview.framework_0.4.6-8_all.deb aeb3997050136bb01b1508f239080e0c 111292 mail optional addressmanager.app_0.4.6-8_i386.deb a64a00700102ec5c6fd7b950d18638c5 16584 libdevel optional libaddresses-dev_0.4.6-8_i386.deb 89426f786ffe2a3f791a92a06d11b9a8 65952 libs optional libaddresses0_0.4.6-8_i386.deb c1d68c25
Bug#394392: msync() in recent kernels fails LSB
On Tue, Dec 19, 2006 at 11:25:22PM +0100, Martin Michlmayr wrote: > * maximilian attems <[EMAIL PROTECTED]> [2006-12-19 20:30]: > > why not wait for the fix and backport it?! > > Well, have you seen the discussion on lkml in which people are > basically tapping in the dark? I hope there'll be a clean fix > in a few days but... > -- > Martin Michlmayr > http://www.cyrius.com/ yes there are 2 working hacks around, so the final should come up. but we shouldn't mould our hands to quickly with the first shot. -- maks christmas with dj dsl and mieze medusa -> http://www.cabaretrenz.org/programm+M5c858bac7ae.html -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
Bug#403795: [Pkg-nagios-devel] Bug#403795: nagios2 doesn't install
reassign #403795 nagios2-common severity #403795 serious tags #403795 confirmed pending merge #403795 #403300 thanks -- - Marc Haber | "I don't trust Computers. They | Mailadresse im Header Mannheim, Germany | lose things."Winona Ryder | Fon: *49 621 72739834 Nordisch by Nature | How to make an American Quilt | Fax: *49 621 72739835 -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
Bug#389068: #389068: any progress ?
Hi, This bug is still open, and it might prevent jabref from being included in etch. Has any progress been done ? It would a shame if jabref wasn't included into etch ... -- | Lucas Nussbaum | [EMAIL PROTECTED] http://www.lucas-nussbaum.net/ | | jabber: [EMAIL PROTECTED] GPG: 1024D/023B3F4F | -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
Bug#396631: Same problem with latest version of apache2/libapr1
Hi there,
Shouldn't this bug be marked as closed?
Best regards,
--
Marcos Marado <[EMAIL PROTECTED]>
Sonaecom ISP
$ perl
''=~('(?{'.('^)@@*@'^'.[).^`').'"'.('`@@[EMAIL
PROTECTED]//[*;)@`//)@|'^'-).[`<@@(^^[`.@@[)^').',$/})')
^Z
Processed: Re: [Pkg-nagios-devel] Bug#403795: nagios2 doesn't install
Processing commands for [EMAIL PROTECTED]: > reassign #403795 nagios2-common Bug#403795: nagios2 doesn't install Bug reassigned from package `nagios2' to `nagios2-common'. > severity #403795 serious Bug#403795: nagios2 doesn't install Severity set to `serious' from `serious' > tags #403795 confirmed pending Bug#403795: nagios2 doesn't install Tags were: pending confirmed Tags added: confirmed, pending > merge #403795 #403300 Bug#403300: nagios2-common: resource.cfg missing Bug#403795: nagios2 doesn't install Merged 403300 403795. > thanks Stopping processing here. Please contact me if you need assistance. Debian bug tracking system administrator (administrator, Debian Bugs database) -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
Bug#403818: xserver-xorg: no video or keyboard after upgrading to sarge (deps too loose)
Package: xserver-xorg Version: 1:7.1.0-8 Severity: serious Justification: 23:28 < vorlon> Sesse: I'd call it RC, no? After dist-upgrading (using etch's aptitude) from sarge to etch, one machine here was completely without keyboard or mouse support, and X refused to work. A bit of hunting revealed that aptitude had pulled in xserver-xorg-input-magictouch and xserver-xorg-video-siliconmotion to fulfill xserver-xorg's dependencies on "xserver-xorg-video-all | xserver-xorg-video" and "xserver-xorg-input-all | xserver-xorg-input", respectively. This is clearly not satisfiable. AFAICS there are two OK ways of solving this: 1. Make the depends into "xserver-xorg-video, xserver-xorg-input", and add Recommends for the -all packages instead. 2. Add xserver-xorg-input-kbd and xserver-xorg-input-mouse explicitly to the list of depends (or possibly recommends?), which should make aptitude Do The Right Thing (hopefully). This won't solve the issue for video, though. One could use a combination of 1 and 2. Note that the request to "aptitude install xorg", which was given by debconf, was a no-op, since all the dependencies were already fulfilled. Also, xorg.conf was blank after the upgrade, but I guess that's for another bug, which will be far harder to track down... :-) -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
Bug#394392: msync() in recent kernels fails LSB
* maximilian attems <[EMAIL PROTECTED]> [2006-12-19 20:30]: > why not wait for the fix and backport it?! Well, have you seen the discussion on lkml in which people are basically tapping in the dark? I hope there'll be a clean fix in a few days but... -- Martin Michlmayr http://www.cyrius.com/ -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
Processed: severity of 403706 is critical
Processing commands for [EMAIL PROTECTED]: > # Automatically generated email from bts, devscripts version 2.9.27 > severity 403706 critical Bug#403706: (sometimes?) fails to bring up interfaces on bootup by default Severity set to `critical' from `important' > End of message, stopping processing here. Please contact me if you need assistance. Debian bug tracking system administrator (administrator, Debian Bugs database) -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
Bug#403585: Regression in 2.4.35-1
Hi Andi, On Tue, 2006-12-19 at 08:55 +0100, Andreas Barth wrote: > Nathan, it is really not the right moment to exchange core libraries. Understood. I certainly didn't want to be uploading anything at this time. :| > There is already a fixed version uploaded, and I would propose that you > just wait with the upload until after release of Etch. Unfortunately, the problem the initial broken upload was attempting to fix (EABI issue on ARM) is not resolved by that upload. There is a low risk fix for that though, which is in attr-2.4.36, but thats now not making it into the archive due to your NMU back to the earlier version. 2.4.36 has the simple ARM EABI fix, and undoes the syscall stub removal which caused all the problems, so it would be my preference to move to that version if possible, even though it is very late in the release cycle (but its not my call in the end, I guess). The other changes between .32 and .36 are few, and only resolving build-related issues - so, also very low risk. cheers. -- Nathan -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
Bug#402949: marked as done (missing dependency against lsb-base)
Your message dated Tue, 19 Dec 2006 21:17:05 +
with message-id <[EMAIL PROTECTED]>
and subject line Bug#402949: fixed in wifi-radar 1.9.6-3.1
has caused the attached Bug report to be marked as done.
This means that you claim that the problem has been dealt with.
If this is not the case it is now your responsibility to reopen the
Bug report if necessary, and/or fix the problem forthwith.
(NB: If you are a system administrator and have no idea what I am
talking about this indicates a serious mail system misconfiguration
somewhere. Please contact me immediately.)
Debian bug tracking system administrator
(administrator, Debian Bugs database)
--- Begin Message ---
Package: wifi-radar
Severity: serious
Tags: patch
Hi dude
How is your trainee program going, hope you are doing well :)
I am sorry, but I am filling a serious bug against your package, because
it misses a dependency against lsb-base. Though lsb-base is
priority: required you need to depend on all packages which are
non-essential and lsb-base is not essential (which should be changed I
guess, but probably won't for etch).
I think the bug will never be really annoying as lsb-base is installed,
but according to policy it is still a bug, sorry ... you know
bureaucracy.
Cheers
Steffen
--- debian/control.orig 2006-12-13 19:15:23.0 +0100
+++ debian/control 2006-12-13 19:15:35.0 +0100
@@ -7,7 +7,7 @@
Package: wifi-radar
Architecture: all
-Depends: ${misc:Depends}, python, python-gtk2 (>= 2.0), dhcp3-client |
dhcp-client, wireless-tools, menu
+Depends: ${misc:Depends}, python, python-gtk2 (>= 2.0), dhcp3-client |
dhcp-client, wireless-tools, menu, lsb-base
Recommends: wpasupplicant
Description: graphical utility for managing Wi-Fi profiles
WiFi Radar enables you to scan for available wireless networks and create
--- End Message ---
--- Begin Message ---
Source: wifi-radar
Source-Version: 1.9.6-3.1
We believe that the bug you reported is fixed in the latest version of
wifi-radar, which is due to be installed in the Debian FTP archive:
wifi-radar_1.9.6-3.1.diff.gz
to pool/main/w/wifi-radar/wifi-radar_1.9.6-3.1.diff.gz
wifi-radar_1.9.6-3.1.dsc
to pool/main/w/wifi-radar/wifi-radar_1.9.6-3.1.dsc
wifi-radar_1.9.6-3.1_all.deb
to pool/main/w/wifi-radar/wifi-radar_1.9.6-3.1_all.deb
A summary of the changes between this version and the previous one is
attached.
Thank you for reporting the bug, which will now be closed. If you
have further comments please address them to [EMAIL PROTECTED],
and the maintainer will reopen the bug report if appropriate.
Debian distribution maintenance software
pp.
Nelson A. de Oliveira <[EMAIL PROTECTED]> (supplier of updated wifi-radar
package)
(This message was generated automatically at their request; if you
believe that there is a problem with it please contact the archive
administrators by mailing [EMAIL PROTECTED])
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
Format: 1.7
Date: Mon, 18 Dec 2006 01:06:24 -0200
Source: wifi-radar
Binary: wifi-radar
Architecture: source all
Version: 1.9.6-3.1
Distribution: unstable
Urgency: medium
Maintainer: Patrick Winnertz <[EMAIL PROTECTED]>
Changed-By: Nelson A. de Oliveira <[EMAIL PROTECTED]>
Description:
wifi-radar - graphical utility for managing Wi-Fi profiles
Closes: 402949
Changes:
wifi-radar (1.9.6-3.1) unstable; urgency=medium
.
* Non-maintainer upload.
* Add missing lsb-base dependency (Closes: #402949).
Files:
786b304e5faf743021462398c21f5ef9 620 net extra wifi-radar_1.9.6-3.1.dsc
8c18b16c483dff2b8e3a246e810d6bab 5148 net extra wifi-radar_1.9.6-3.1.diff.gz
77aa4946e55a160fdedbe630798f97f2 29168 net extra wifi-radar_1.9.6-3.1_all.deb
-BEGIN PGP SIGNATURE-
Version: GnuPG v1.4.6 (GNU/Linux)
iD8DBQFFhgm4AQwuptkwlkQRAuQ2AJ91HpmzVBkeJQG+9AJFH9nSfBQ9zACdF3sM
9gqgpzWorta2/giW8vjqbEQ=
=cNUw
-END PGP SIGNATURE-
--- End Message ---
Bug#403132: marked as done (ocsigen_0.5.0-1(alpha/unstable): FTBFS with -rsudo)
Your message dated Tue, 19 Dec 2006 21:47:03 + with message-id <[EMAIL PROTECTED]> and subject line Bug#403132: fixed in ocsigen 0.5.1-2 has caused the attached Bug report to be marked as done. This means that you claim that the problem has been dealt with. If this is not the case it is now your responsibility to reopen the Bug report if necessary, and/or fix the problem forthwith. (NB: If you are a system administrator and have no idea what I am talking about this indicates a serious mail system misconfiguration somewhere. Please contact me immediately.) Debian bug tracking system administrator (administrator, Debian Bugs database) --- Begin Message --- Package: ocsigen Version: 0.5.0-1 Severity: serious There was an error while trying to autobuild your package: > Automatic build of ocsigen_0.5.0-1 on goedel by sbuild/alpha 99.99 > Build started at 20061209-1805 [...] > ** Using build dependencies supplied by package: > Build-Depends: debhelper (>= 5), ocaml-nox (>= 3.08.4), ocaml-findlib, > libocamlnet-ocaml-dev (>= 1.1), libdbi-ocaml-dev, libssl-ocaml-dev (>= > 0.4.0-1) [...] > make[2]: *** [depend] Error 1 > make[2]: Leaving directory `/build/buildd/ocsigen-0.5.0/xmlp4' > make[1]: *** [xmlp4] Error 2 > make[1]: Leaving directory `/build/buildd/ocsigen-0.5.0' > make: [build-stamp] Error 2 (ignored) > /usr/bin/make all OCSIMORE=YES BINDIR=/usr/bin > make[1]: Entering directory `/build/buildd/ocsigen-0.5.0' > /usr/bin/make -C baselib all > make[2]: Entering directory `/build/buildd/ocsigen-0.5.0/baselib' > Makefile:61: .depend: No such file or directory > make[2]: *** No rule to make target `.depend'. Stop. > make[2]: Leaving directory `/build/buildd/ocsigen-0.5.0/baselib' > make[1]: *** [baselib] Error 2 > make[1]: Leaving directory `/build/buildd/ocsigen-0.5.0' > make: *** [build-stamp] Error 2 A full build log can be found at: http://buildd.debian.org/pkg.cgi?arch=alpha&pkg=ocsigen&ver=0.5.0-1 The clean target ends up creating .depend as root, so that the regular user cannot write to it in the build process. You can reproduce this on any architecture with the following command as a regular user with permissions to sudo to root: dpkg-buildpackage -uc -us -B -rsudo --- End Message --- --- Begin Message --- Source: ocsigen Source-Version: 0.5.1-2 We believe that the bug you reported is fixed in the latest version of ocsigen, which is due to be installed in the Debian FTP archive: ocsigen_0.5.1-2.diff.gz to pool/main/o/ocsigen/ocsigen_0.5.1-2.diff.gz ocsigen_0.5.1-2.dsc to pool/main/o/ocsigen/ocsigen_0.5.1-2.dsc ocsigen_0.5.1-2_i386.deb to pool/main/o/ocsigen/ocsigen_0.5.1-2_i386.deb A summary of the changes between this version and the previous one is attached. Thank you for reporting the bug, which will now be closed. If you have further comments please address them to [EMAIL PROTECTED], and the maintainer will reopen the bug report if appropriate. Debian distribution maintenance software pp. Samuel Mimram <[EMAIL PROTECTED]> (supplier of updated ocsigen package) (This message was generated automatically at their request; if you believe that there is a problem with it please contact the archive administrators by mailing [EMAIL PROTECTED]) -BEGIN PGP SIGNED MESSAGE- Hash: SHA1 Format: 1.7 Date: Mon, 18 Dec 2006 09:41:22 + Source: ocsigen Binary: ocsigen Architecture: source i386 Version: 0.5.1-2 Distribution: unstable Urgency: low Maintainer: Samuel Mimram <[EMAIL PROTECTED]> Changed-By: Samuel Mimram <[EMAIL PROTECTED]> Description: ocsigen- web programming framework in OCaml Closes: 403132 Changes: ocsigen (0.5.1-2) unstable; urgency=low . * Using dpatch to handle patches. * Added depends.dpatch in order to really solve the compilation problem with -rsudo, closes: #403132. Files: edaf797148f7dfba1137b80a216a3ba9 758 devel optional ocsigen_0.5.1-2.dsc 27d8539ea6d5d2ff16f1c97c75c96b52 5712 devel optional ocsigen_0.5.1-2.diff.gz e939e7d0d2d894aee0918fde17dc6682 1926796 devel optional ocsigen_0.5.1-2_i386.deb -BEGIN PGP SIGNATURE- Version: GnuPG v1.4.6 (GNU/Linux) iD8DBQFFiFy0Iae1O4AJae8RAtyeAJ9SZVDV+oaQDRtdpq1AW6o7sDT1dACfSnwP sKlO7rHLkPrFRMnsj3FQt7w= =peLD -END PGP SIGNATURE- --- End Message ---
Processed (with 2 errors): Re: [Pkg-nagios-devel] Bug#403795: nagios2 doesn't install
Processing commands for [EMAIL PROTECTED]: > reassign #403795 Unknown command or malformed arguments to command. > severity #403795 serious Bug#403795: nagios2 doesn't install Severity set to `serious' from `normal' > tags #403795 confirmed pending Bug#403795: nagios2 doesn't install There were no tags set. Tags added: confirmed, pending > merge #403795 #403300 Bug#403300: nagios2-common: resource.cfg missing Bug#403795: nagios2 doesn't install Mismatch - only Bugs in same state can be merged: Values for `package' don't match: #403300 has `nagios2-common'; #403795 has `nagios2' > thanks Stopping processing here. Please contact me if you need assistance. Debian bug tracking system administrator (administrator, Debian Bugs database) -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
Processed: severity of 403706 is normal
Processing commands for [EMAIL PROTECTED]: > # Automatically generated email from bts, devscripts version 2.9.27 > severity 403706 normal Bug#403706: (sometimes?) fails to bring up interfaces on bootup by default Severity set to `normal' from `critical' > End of message, stopping processing here. Please contact me if you need assistance. Debian bug tracking system administrator (administrator, Debian Bugs database) -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
Bug#403804: net.agent check for lo= in /etc/network/run/ifstate is broken on unclean shutdown; interface not brought up
Package: udev Version: 0.103-1 Severity: critical Please see bug #403706 for the bug that brought me here. For hotpluggable interfaces, net.agent checks to see if /etc/network/run/ifstate contains "lo=", and if not, waits a while for the interface to come up, which is a kind of a flag indicating that ifupdown is configured and ready to be used. If a system is uncleanly shutdown, then the ifstate file will still contain "lo=" when it comes back up. If the system has an interface, marked as hotpluggable, that is present during boot, then udev will run net.agent before the root filesystem is fscked, and before /etc/rcS.d/S18ifupdown-clean is run (which cleans the ifstate file). Since the "lo=" is still there, it will not wait, and will immediatly try to run ifupdown, which fails on a ro root filesystem. As a result, the network interface won't be up after boot. Currently, as noted in #403706, d-i marks nearly all interfaces as allow-hotplug, including pci cards, so all newly installed systems suffer from this problem, which makes their networking very non-robust. I feel that net.agent should be much more robust than this, should probably check to see if the ifup worked, and if not, sleep and retry. The whole check for lo being up based on /etc/network/run/ifstate seems less than ideal; it could instead check whether the actual interface is up, that seems less likely to have false positivies. -- Package-specific info: -- /etc/udev/rules.d/: /etc/udev/rules.d/: total 36 lrwxrwxrwx 1 root root39 Dec 5 10:00 020_libgphoto2_generic-ptp_support.rules -> ../libgphoto2_generic_ptp_support.rules lrwxrwxrwx 1 root root20 Jun 2 2006 020_permissions.rules -> ../permissions.rules lrwxrwxrwx 1 root root16 Aug 7 22:19 025_libsane.rules -> ../libsane.rules lrwxrwxrwx 1 root root16 Jun 12 2006 030_ifplugd.rules -> ../ifplugd.rules lrwxrwxrwx 1 root root24 Dec 13 20:11 030_sl-modem-daemon.rules -> ../sl-modem-daemon.rules lrwxrwxrwx 1 root root15 Jun 2 2006 85-pcmcia.rules -> ../pcmcia.rules lrwxrwxrwx 1 root root13 Jun 2 2006 udev.rules -> ../udev.rules lrwxrwxrwx 1 root root25 Jun 2 2006 z20_persistent-input.rules -> ../persistent-input.rules lrwxrwxrwx 1 root root19 Jun 2 2006 z20_persistent.rules -> ../persistent.rules -rw-r--r-- 1 root root 29677 Aug 29 17:26 z25_persistent-cd.rules -rw-r--r-- 1 root root 735 Oct 18 20:49 z25_persistent-net.rules lrwxrwxrwx 1 root root33 Jun 2 2006 z45_persistent-net-generator.rules -> ../persistent-net-generator.rules lrwxrwxrwx 1 root root12 Jun 2 2006 z50_run.rules -> ../run.rules lrwxrwxrwx 1 root root16 Jun 2 2006 z55_hotplug.rules -> ../hotplug.rules lrwxrwxrwx 1 root root19 Jun 2 2006 z60_alsa-utils.rules -> ../alsa-utils.rules lrwxrwxrwx 1 root root15 Jun 2 2006 z60_hdparm.rules -> ../hdparm.rules lrwxrwxrwx 1 root root33 Jun 2 2006 z60_xserver-xorg-input-wacom.rules -> ../xserver-xorg-input-wacom.rules lrwxrwxrwx 1 root root29 Jun 2 2006 z75_cd-aliases-generator.rules -> ../cd-aliases-generator.rules lrwxrwxrwx 1 root root12 Nov 28 02:17 z99_hal.rules -> ../hal.rules -- /sys/: /sys/block/hda/dev /sys/block/hda/hda1/dev /sys/block/hda/hda2/dev /sys/block/ram0/dev /sys/block/ram1/dev /sys/block/ram10/dev /sys/block/ram11/dev /sys/block/ram12/dev /sys/block/ram13/dev /sys/block/ram14/dev /sys/block/ram15/dev /sys/block/ram2/dev /sys/block/ram3/dev /sys/block/ram4/dev /sys/block/ram5/dev /sys/block/ram6/dev /sys/block/ram7/dev /sys/block/ram8/dev /sys/block/ram9/dev /sys/block/sr0/dev /sys/class/drm/card0/dev /sys/class/input/input0/event0/dev /sys/class/input/input1/event1/dev /sys/class/input/input11/event2/dev /sys/class/input/input11/mouse0/dev /sys/class/input/input11/ts0/dev /sys/class/input/mice/dev /sys/class/misc/agpgart/dev /sys/class/misc/device-mapper/dev /sys/class/misc/fuse/dev /sys/class/misc/hpet/dev /sys/class/misc/psaux/dev /sys/class/misc/rtc/dev /sys/class/misc/snapshot/dev /sys/class/misc/tun/dev /sys/class/misc/vmmon/dev /sys/class/scsi_generic/sg0/dev /sys/class/sound/adsp/dev /sys/class/sound/audio/dev /sys/class/sound/controlC0/dev /sys/class/sound/dsp/dev /sys/class/sound/mixer/dev /sys/class/sound/pcmC0D0c/dev /sys/class/sound/pcmC0D0p/dev /sys/class/sound/pcmC0D1c/dev /sys/class/sound/pcmC0D6c/dev /sys/class/sound/pcmC0D6p/dev /sys/class/sound/timer/dev /sys/class/usb_device/usbdev1.1/dev /sys/class/usb_device/usbdev2.1/dev /sys/class/usb_device/usbdev3.1/dev /sys/class/usb_device/usbdev3.7/dev /sys/class/usb_device/usbdev4.1/dev /sys/class/usb_device/usbdev4.6/dev /sys/class/usb_device/usbdev5.1/dev /sys/devices/pci:00/:00:1d.0/usb1/1-0:1.0/usbdev1.1_ep81/dev /sys/devices/pci:00/:00:1d.0/usb1/usbdev1.1_ep00/dev /sys/devices/pci:00/:00:1d.1/usb2/2-0:1.0/usbdev2.1_ep81/dev /sys/devices/pci:00/:00:1d.1/usb2/usbdev2.1_ep00/dev /sys/devices/pci:00/:00:1d.2/usb3/3-0:1.0/usbdev3.1_ep81/dev /sys/devices/pci
Bug#403661: torrentflux: fails to install with error code 10
severity 403661 normal tags 403661 unreproducible thanks On 12/19/06, Remi Vanicat <[EMAIL PROTECTED]> wrote: 2006/12/19, Micah Anderson <[EMAIL PROTECTED]>: > I just created a sid chroot and attempted to install torrentflux, I did > not encounter this problem. > > I tried a few different failure scenarios (mysql-client not available, > mysql-server not installed, database password incorrect, database server > not running) and they all worked fine. Note that failure happen before I've been asked the database password, and mysql-server and mysql-client were installed. answer to dbconfig question was : no for keeping admin password no for using non local database I've just try to do an aptitude reinstall dbconfig-common and everything worked as expected. Now, I'm trying to reproduce the bug on my computer, but it is not there anymore. I do'nt understand. It may be a one-time thing, or something may have happened to dbconfig-common that is unexpected. Had you just installed it recently? Does it work for other packages? I asked on the dbconfig-common mail list, and it seems that I have used it properly. The dbconfig-common developer did ask if you could try "debconf-show dbconfig-common", and "dpkg-reconfigure dbconfig-common", as the former would be informative, the latter might fix the problem (although I gather it's been fixed already). Since it's non-reoccurring (thanks Micah!), I have downgraded it accordingly. Cameron -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
Processed: Re: Bug#403661: torrentflux: fails to install with error code 10
Processing commands for [EMAIL PROTECTED]: > severity 403661 normal Bug#403661: torrentflux: fails to install with error code 10 Severity set to `normal' from `grave' > tags 403661 unreproducible Bug#403661: torrentflux: fails to install with error code 10 There were no tags set. Tags added: unreproducible > thanks Stopping processing here. Please contact me if you need assistance. Debian bug tracking system administrator (administrator, Debian Bugs database) -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
Processed: [bts-link] source package lprof
Processing commands for [EMAIL PROTECTED]: > # > # bts-link upstream status pull for source package lprof > # see http://lists.debian.org/debian-devel-announce/2006/05/msg1.html > # > user [EMAIL PROTECTED] Setting user to [EMAIL PROTECTED] (was [EMAIL PROTECTED]). > # remote status report for #400061 > # * > http://sourceforge.net/tracker/?func=detail&atid=764370&aid=1601945&group_id=146038 > # * remote status changed: Open -> Closed > # * remote resolution changed: (?) -> Invalid > # * closed upstream > tags 400061 + fixed-upstream Bug#400061: lprof: FTBFS: AttributeError in /usr/lib/scons/SCons/Node/FS.py Tags were: patch upstream confirmed Tags added: fixed-upstream > usertags 400061 - status-Open Bug#400061: lprof: FTBFS: AttributeError in /usr/lib/scons/SCons/Node/FS.py Usertags were: status-Open. Usertags are now: . > usertags 400061 + status-Closed resolution-Invalid Bug#400061: lprof: FTBFS: AttributeError in /usr/lib/scons/SCons/Node/FS.py There were no usertags set. Usertags are now: resolution-Invalid status-Closed. > thanks Stopping processing here. Please contact me if you need assistance. Debian bug tracking system administrator (administrator, Debian Bugs database) -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
Bug#403753: addresses-goodies-for-gnustep: file conflict with adtool
On 2006-12-19 10:18:32 -0500 Bill Allombert <[EMAIL PROTECTED]> wrote: The package addresses-goodies-for-gnustep includes the file /usr/share/man/man1/adtool.1.gz which is also part of the package 'adtool'. Worse than that, they both contain /usr/bin/adtool, which means that it needs to be renamed. I'll rename the tool from "adtool" to "addresstool". -- Hubert Chan <[EMAIL PROTECTED]> -- Jabber: [EMAIL PROTECTED] PGP/GnuPG key: 1024D/124B61FA http://www.uhoreg.ca/ Fingerprint: 96C5 012F 5F74 A5F7 1FF7 5291 AF29 C719 124B 61FA -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
Processed: [bts-link] source package evince
Processing commands for [EMAIL PROTECTED]: > # > # bts-link upstream status pull for source package evince > # see http://lists.debian.org/debian-devel-announce/2006/05/msg1.html > # > user [EMAIL PROTECTED] Setting user to [EMAIL PROTECTED] (was [EMAIL PROTECTED]). > # remote status report for #376579 > # * http://bugzilla.gnome.org/show_bug.cgi?id=374341 > # * remote status changed: UNCONFIRMED -> NEW > usertags 376579 - status-UNCONFIRMED Bug#376579: evince: Won't load files with relative path and : in name Usertags were: status-UNCONFIRMED. Usertags are now: . > usertags 376579 + status-NEW Bug#376579: evince: Won't load files with relative path and : in name There were no usertags set. Usertags are now: status-NEW. > # remote status report for #402063 > # * http://bugzilla.gnome.org/show_bug.cgi?id=380191 > # * remote status changed: (?) -> RESOLVED > # * remote resolution changed: (?) -> FIXED > # * closed upstream > forwarded 402063 http://bugzilla.gnome.org/show_bug.cgi?id=383485, > merged-upstream: http://bugzilla.gnome.org/show_bug.cgi?id=380191 Bug#402063: vulnerable to overflow in PS handling (CVE-2006-5864) Forwarded-to-address changed from http://bugzilla.gnome.org/show_bug.cgi?id=383485 to http://bugzilla.gnome.org/show_bug.cgi?id=383485, merged-upstream: http://bugzilla.gnome.org/show_bug.cgi?id=380191. (By the way, this Bug is currently marked as done.) > tags 402063 + fixed-upstream Bug#402063: vulnerable to overflow in PS handling (CVE-2006-5864) Tags were: patch security Tags added: fixed-upstream > usertags 402063 + status-RESOLVED resolution-FIXED Bug#402063: vulnerable to overflow in PS handling (CVE-2006-5864) There were no usertags set. Usertags are now: resolution-FIXED status-RESOLVED. > thanks Stopping processing here. Please contact me if you need assistance. Debian bug tracking system administrator (administrator, Debian Bugs database) -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
Bug#403661: [Dbconfig-common-devel] Fwd: Bug#403661: torrentflux: fails to install with error code 10
hey cameron, On Mon, 2006-12-18 at 23:15 -0800, Cameron Dale wrote: > Hi, > > I just received this RC bug on my package, and I think it is > dbconfig-common related. I don't think I've done anything wrong in my > config script (it's pretty basic, see attachment), but I can't tell > where this error is coming from. Any help or guidance you can provide > would be very much appreciated. that's really strange. i looked at your source package and you seem to have correctly put in conditional hooks so that the dbconfig stuff in the .config script is only executed if dbconfig is already installed (not conifgured, but unpacked and debconf templates registered). i don't have the time to look into this right now, but you might ask the reporter to "debconf-show dbconfig-common", and "dpkg-reconfigure dbconfig-common". the former would be informative, the latter might fix the problem? sean signature.asc Description: This is a digitally signed message part
Processed: [bts-link] source package gstreamer0.10-ffmpeg
Processing commands for [EMAIL PROTECTED]: > # > # bts-link upstream status pull for source package gstreamer0.10-ffmpeg > # see http://lists.debian.org/debian-devel-announce/2006/05/msg1.html > # > user [EMAIL PROTECTED] Setting user to [EMAIL PROTECTED] (was [EMAIL PROTECTED]). > # remote status report for #401311 > # * http://bugzilla.gnome.org/show_bug.cgi?id=383009 > # * remote status changed: (?) -> RESOLVED > # * remote resolution changed: (?) -> FIXED > # * closed upstream > tags 401311 + fixed-upstream Bug#401311: CVE-2006-4800: GStreamer FFmpeg Plug-in Multiple Buffer Overflows Tags were: patch security Tags added: fixed-upstream > usertags 401311 + status-RESOLVED resolution-FIXED Bug#401311: CVE-2006-4800: GStreamer FFmpeg Plug-in Multiple Buffer Overflows There were no usertags set. Usertags are now: resolution-FIXED status-RESOLVED. > # remote status report for #401311 > # * http://bugzilla.gnome.org/show_bug.cgi?id=383009 > # * remote status changed: (?) -> RESOLVED > # * remote resolution changed: (?) -> FIXED > # * closed upstream > tags 401311 + fixed-upstream Bug#401311: CVE-2006-4800: GStreamer FFmpeg Plug-in Multiple Buffer Overflows Tags were: fixed-upstream patch security Tags added: fixed-upstream > usertags 401311 + status-RESOLVED resolution-FIXED Bug#401311: CVE-2006-4800: GStreamer FFmpeg Plug-in Multiple Buffer Overflows Usertags were: resolution-FIXED status-RESOLVED. Usertags are now: resolution-FIXED status-RESOLVED. > # remote status report for #402090 > # * http://bugzilla.gnome.org/show_bug.cgi?id=363363 > # * remote status changed: NEW -> RESOLVED > # * remote resolution changed: (?) -> FIXED > # * closed upstream > tags 402090 + fixed-upstream Bug#402090: gstreamer0.10-ffmpeg: should link with system ffmpeg libraries Tags were: patch Tags added: fixed-upstream > usertags 402090 - status-NEW Bug#402090: gstreamer0.10-ffmpeg: should link with system ffmpeg libraries Usertags were: status-NEW. Usertags are now: . > usertags 402090 + status-RESOLVED resolution-FIXED Bug#402090: gstreamer0.10-ffmpeg: should link with system ffmpeg libraries There were no usertags set. Usertags are now: resolution-FIXED status-RESOLVED. > # remote status report for #403362 > # * http://bugzilla.gnome.org/show_bug.cgi?id=386129 > # * remote status changed: (?) -> UNCONFIRMED > usertags 403362 + status-UNCONFIRMED Bug#403362: totem-mozilla: dont register mediatypes which cant be played There were no usertags set. Usertags are now: status-UNCONFIRMED. > thanks Stopping processing here. Please contact me if you need assistance. Debian bug tracking system administrator (administrator, Debian Bugs database) -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
Processed: [bts-link] source package openoffice.org
Processing commands for [EMAIL PROTECTED]: > # > # bts-link upstream status pull for source package openoffice.org > # see http://lists.debian.org/debian-devel-announce/2006/05/msg1.html > # > user [EMAIL PROTECTED] Setting user to [EMAIL PROTECTED] (was [EMAIL PROTECTED]). > # remote status report for #401325 > # * http://qa.openoffice.org/issues/show_bug.cgi?id=72124 > # * remote status changed: (?) -> RESOLVED > # * remote resolution changed: (?) -> FIXED > # * closed upstream > tags 401325 + fixed-upstream Bug#401325: Potential non-free afm files in OpenOffice package There were no tags set. Tags added: fixed-upstream > usertags 401325 + status-RESOLVED resolution-FIXED Bug#401325: Potential non-free afm files in OpenOffice package There were no usertags set. Usertags are now: resolution-FIXED status-RESOLVED. > # remote status report for #403275 > # * http://qa.openoffice.org/issues/show_bug.cgi?id=68047 > # * remote resolution changed: (?) -> FIXED > usertags 403275 + resolution-FIXED Bug#403275: The zero width joiner shouldn't be filtered out Usertags were: status-VERIFIED. Usertags are now: resolution-FIXED status-VERIFIED. > thanks Stopping processing here. Please contact me if you need assistance. Debian bug tracking system administrator (administrator, Debian Bugs database) -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
Bug#403789: FTBFS on arm: "gcc: /usr/lib/libtasn1.so: No such file or directory"
Version: 2.0.3-2.1 Package: gnucash Severity: serious NMU upload of gnucash fails to build on arm. make[5]: Entering directory `/build/buildd/gnucash-2.0.2/src/network-utils/test' if gcc -DHAVE_CONFIG_H -I. -I. -I../../.. -I../../.. -I../../.. -I../../.. -I../../../src/test-core -I.. -pthread -I/usr/include/glib-2.0 -I/usr/lib/glib-2.0/include -Wall -Wunused -Wmissing-prototypes -Wmissing-declarations -Wdeclaration-after-statement -Wno-pointer-sign -D_FORTIFY_SOURCE=2 -MT test-link-module.o -MD -MP -MF ".deps/test-link-module.Tpo" -c -o test-link-module.o test-link-module.c; \ then mv -f ".deps/test-link-module.Tpo" ".deps/test-link-module.Po"; else rm -f ".deps/test-link-module.Tpo"; exit 1; fi /bin/sh ../../../libtool --tag=CC --mode=link gcc -I../../../src/test-core -I.. -pthread -I/usr/include/glib-2.0 -I/usr/lib/glib-2.0/include -Wall -Wunused -Wmissing-prototypes -Wmissing-declarations -Wdeclaration-after-statement -Wno-pointer-sign -D_FORTIFY_SOURCE=2 -L/usr/X11R6/lib -o test-link-module test-link-module.o ../../../src/engine/libgncmod-engine.la ../libgncmod-network-utils.la -lpopt -lm -lm mkdir .libs gcc -I../../../src/test-core -I.. -pthread -I/usr/include/glib-2.0 -I/usr/lib/glib-2.0/include -Wall -Wunused -Wmissing-prototypes -Wmissing-declarations -Wdeclaration-after-statement -Wno-pointer-sign -D_FORTIFY_SOURCE=2 -o .libs/test-link-module test-link-module.o -L/usr/X11R6/lib ../../../src/engine/.libs/libgncmod-engine.so ../.libs/libgncmod-network-utils.so /build/buildd/gnucash-2.0.2/src/gnc-module/.libs/libgncmodule.so /build/buildd/gnucash-2.0.2/src/core-utils/.libs/libcore-utils.so /usr/lib/libgwrap-guile-runtime.so /usr/lib/libgwrap-core-runtime.so /usr/lib/libguile.so /usr/lib/libguile-ltdl.so -lcrypt /usr/lib/libffi.so /usr/lib/libltdl.so /usr/lib/libgnomeui-2.so -L/usr/lib /usr/lib/libjpeg.so /usr/lib/libbonoboui-2.so -ldbus-1 /usr/lib/libesd.so /usr/lib/libaudiofile.so -lSM -lICE /usr/lib/libgnome-keyring.so /usr/lib/libgnomecanvas-2.so /usr/lib/libgnome-2.so /usr/lib/libart_lgpl_2.so /usr/lib/libpangoft2-1.0.so /usr/lib/libgtk-x11-2.0.so /usr/lib/libgdk-x11-2.0.so /usr/lib/libatk-1.0.so /usr/lib/libgdk_pixbuf-2.0.so /usr/lib/libpangocairo-1.0.so -lXext -lXinerama -lXi -lXrandr -lXcursor -lXfixes /usr/lib/libpango-1.0.so /usr/lib/libcairo.so /usr/lib/libfreetype.so -lfontconfig -lpng12 -lXrender -lX11 /usr/lib/libgnomevfs-2.so /usr/lib/libxml2.so /usr/lib/libgnutls.so /usr/lib/libtasn1.so -lz /usr/lib/libgcrypt.so -lnsl /usr/lib/libgpg-error.so /usr/lib/libavahi-glib.so /usr/lib/libavahi-common.so /usr/lib/libavahi-client.so -lresolv -lutil /usr/lib/libbonobo-2.so /usr/lib/libgconf-2.so /usr/lib/libbonobo-activation.so /usr/lib/libORBitCosNaming-2.so /usr/lib/libORBit-2.so /build/buildd/gnucash-2.0.2/lib/libqof/qof/.libs/libgncqof.so /usr/lib/libgthread-2.0.so -lpthread /usr/lib/libgobject-2.0.so /usr/lib/libgmodule-2.0.so -ldl /usr/lib/libglib-2.0.so -lrt /usr/lib/libpopt.so -lm -Wl,--rpath -Wl,/usr/lib/gnucash/gnucash -Wl,--rpath -Wl,/usr/lib/gnucash gcc: /usr/lib/libtasn1.so: No such file or directory make[5]: *** [test-link-module] Error 1 http://buildd.debian.org/fetch.cgi?pkg=gnucash;ver=2.0.2-2.1;arch=arm;stamp=1166366850 Thomas signature.asc Description: This is a digitally signed message part
Bug#403165: No items in default GNOME menu upon upgrade from 2.14 to 2.16
Ter, 2006-12-19 às 19:04 +0100, Josselin Mouette escreveu: > Le mardi 19 décembre 2006 à 11:37 +, Paulo Silva a écrit : > > Same problem here. > > > > Removing ~/.config/menus/ and ~/.local/ solved the problem (don't know > > if both are needed). > > Do you remember what was in the .config/menus directory? It had several *.menu files if I'm not mistaken. Now it has just one (it goes in attachment). It was generated by the update-menus program. > Paolo, Jean-Luc: if you have a .config/menus directory, I'd like to see > its contents. If it's not too big, please attach it to the bug report. > I'd also like to know how it was generated, e.g. with alacarte or > something else. > > Thanks for your input, -- Paulo Silva <[EMAIL PROTECTED]> debian-menu.menu.gz Description: GNU Zip compressed data signature.asc Description: Esta é uma parte de mensagem assinada digitalmente
Bug#403119: Bug#402903: I think this is a problem in apt actually
Hi Colin Good to know. Just of couriousity, what was the problem? Regards, // Ola On Tue, Dec 19, 2006 at 09:45:36AM +, Colin Watson wrote: > On Tue, Dec 19, 2006 at 07:59:01AM +0100, Ola Lundqvist wrote: > > This problem is probably not solveable in ssh as this has to > > do with package dependencies. > > Incorrect. I have an upload pending to fix this bug. > > -- > Colin Watson [EMAIL PROTECTED] > -- - Ola Lundqvist --- / [EMAIL PROTECTED] Annebergsslingan 37 \ | [EMAIL PROTECTED] 654 65 KARLSTAD | | +46 (0)54-10 14 30 +46 (0)70-332 1551 | | http://opalsys.net/ UIN/icq: 4912500 | \ gpg/f.p.: 7090 A92B 18FE 7994 0C36 4FE4 18A1 B1CF 0FE5 3DD9 / --- -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
Processed: merging
Processing commands for [EMAIL PROTECTED]: > merge 400879 389579 Bug#389579: libapache-mod-auth-mysql: FTBFS against apache 2.2 Bug#400879: libapache2-mod-auth-mysql not installable on etch or unstable Merged 389579 400879. > stop Stopping processing here. Please contact me if you need assistance. Debian bug tracking system administrator (administrator, Debian Bugs database) -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
Bug#397312: this bug: #397312/xchat: segfault on amd64 (japanese po/ja.po)
Thanks to Masami for his work tracking down this bug. I'm concerned about the patch applied to resolve this bug; the code should not segfault just because of bad datafiles; as long as the API is followed, errors should be detected (indeed, this will help detect invalid datafiles in a nicer way). If you agree, please reopen this bug with severity: normal, and someone will get around to checking the return values as necessary. Justin References [0] http://bugs.debian.org/397312 -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
Bug#394392: msync() in recent kernels fails LSB
On Tue, Dec 19, 2006 at 05:08:24PM +0100, Martin Michlmayr wrote: > > So it seems that the patches needed for msync() conformance we applied > from 2.6.19 to our 2.6.18 cause filesystem corruption, see the current > discussion on this on lkml. From what I understand it, plain 2.6.18 > is not LSB 3.1 conform and you need some fixes which are associated > with filesystem corruption. While Andrew, Linus and co are currently > trying to come up with a patch, I think it might be better for us to > simply back out these patches. What doe it take to get an exception > for this LSB test? Surely the reasons cited above (fails with 2.6.18, > a fairly current kernel and the patches to fix it are associated with > fs corruption) are pretty good arguments for an exception... > -- > Martin Michlmayr > http://www.cyrius.com/ why not wait for the fix and backport it?! -- maks -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
Bug#403645: #403590: kdeinit fails to start
Package: libattr1 Followup-For: Bug #403645 Installed libattr1_2.4.35-1_i386 via aptitude ugrade and saw above symptom. Rolled back to 2.4.32-1 and problem went away. -- System Information: Debian Release: 4.0 APT prefers unstable APT policy: (500, 'unstable'), (500, 'stable') Architecture: i386 (i686) Shell: /bin/sh linked to /bin/bash Kernel: Linux 2.6.16-18.061107-4 Locale: LANG=en_us, LC_CTYPE=en_us (charmap=ANSI_X3.4-1968) (ignored: LC_ALL set to C) Versions of packages libattr1 depends on: ii libc62.3.6.ds1-9 GNU C Library: Shared libraries libattr1 recommends no packages. -- no debconf information -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
Bug#403572: marked as done (proofgeneral_3.5-4(ia64/unstable): FTBFS: Missing build-depend?)
Your message dated Tue, 19 Dec 2006 18:47:09 + with message-id <[EMAIL PROTECTED]> and subject line Bug#403572: fixed in proofgeneral 3.5-4.1 has caused the attached Bug report to be marked as done. This means that you claim that the problem has been dealt with. If this is not the case it is now your responsibility to reopen the Bug report if necessary, and/or fix the problem forthwith. (NB: If you are a system administrator and have no idea what I am talking about this indicates a serious mail system misconfiguration somewhere. Please contact me immediately.) Debian bug tracking system administrator (administrator, Debian Bugs database) --- Begin Message --- Package: proofgeneral Version: 3.5-4 Severity: serious There was an error while trying to autobuild your package: > Automatic build of proofgeneral_3.5-4 on caballero by sbuild/ia64 98 > Build started at 20061218-0316 [...] > ** Using build dependencies supplied by package: > Build-Depends-Indep: debhelper (>= 4.1.16), mzscheme [...] > dh_clean: Compatibility levels before 4 are deprecated. > rm -f debian/*~ debian/#*# > rm -f minlog/*.o minlog/*.so > debian/rules build > dh_testdir > make scripts > make[1]: Entering directory `/build/buildd/proofgeneral-3.5' > make[1]: Leaving directory `/build/buildd/proofgeneral-3.5' > (cd minlog; make) > make[1]: Entering directory `/build/buildd/proofgeneral-3.5/minlog' > mzc --cc mzfork.c > make[1]: mzc: Command not found > make[1]: *** [mzfork.o] Error 127 > make[1]: Leaving directory `/build/buildd/proofgeneral-3.5/minlog' > make: *** [build-stamp] Error 2 A full build log can be found at: http://buildd.debian.org/build.php?arch=ia64&pkg=proofgeneral&ver=3.5-4 Build dependencies need to be specified in Build-Depends, unless all of the binaries delivered are Architecture: all (in which case the buildds won't try to build it.) lamont --- End Message --- --- Begin Message --- Source: proofgeneral Source-Version: 3.5-4.1 We believe that the bug you reported is fixed in the latest version of proofgeneral, which is due to be installed in the Debian FTP archive: proofgeneral-coq_3.5-4.1_all.deb to pool/main/p/proofgeneral/proofgeneral-coq_3.5-4.1_all.deb proofgeneral-doc_3.5-4.1_all.deb to pool/main/p/proofgeneral/proofgeneral-doc_3.5-4.1_all.deb proofgeneral-minlog_3.5-4.1_i386.deb to pool/main/p/proofgeneral/proofgeneral-minlog_3.5-4.1_i386.deb proofgeneral-misc_3.5-4.1_all.deb to pool/main/p/proofgeneral/proofgeneral-misc_3.5-4.1_all.deb proofgeneral_3.5-4.1.diff.gz to pool/main/p/proofgeneral/proofgeneral_3.5-4.1.diff.gz proofgeneral_3.5-4.1.dsc to pool/main/p/proofgeneral/proofgeneral_3.5-4.1.dsc proofgeneral_3.5-4.1_all.deb to pool/main/p/proofgeneral/proofgeneral_3.5-4.1_all.deb A summary of the changes between this version and the previous one is attached. Thank you for reporting the bug, which will now be closed. If you have further comments please address them to [EMAIL PROTECTED], and the maintainer will reopen the bug report if appropriate. Debian distribution maintenance software pp. Christian Perrier <[EMAIL PROTECTED]> (supplier of updated proofgeneral package) (This message was generated automatically at their request; if you believe that there is a problem with it please contact the archive administrators by mailing [EMAIL PROTECTED]) -BEGIN PGP SIGNED MESSAGE- Hash: SHA1 Format: 1.7 Date: Tue, 19 Dec 2006 08:27:28 +0100 Source: proofgeneral Binary: proofgeneral proofgeneral-coq proofgeneral-minlog proofgeneral-doc proofgeneral-misc Architecture: source all i386 Version: 3.5-4.1 Distribution: unstable Urgency: low Maintainer: Stefan Schimanski <[EMAIL PROTECTED]> Changed-By: Christian Perrier <[EMAIL PROTECTED]> Description: proofgeneral - A generic interface for proof assistants proofgeneral-coq - ProofGeneral support for coq proofgeneral-doc - Documentation for ProofGeneral in html format proofgeneral-minlog - ProofGeneral support for Minlog proofgeneral-misc - ProofGeneral support for different theorem provers Closes: 403572 Changes: proofgeneral (3.5-4.1) unstable; urgency=low . * Non-maintainer upload to fix an RC bug * Move debhelper and mzscheme to Build-Depends. Closes: 403572 Lintian warnings are things that should be taken seriously. * Lintian fixes: - Remove useless CVS directory minlog/CVS - Use 4 as debhelper compatibility (through debian/compat) Files: 41fab1a37fa52c7cc2c402f5d7fe6312 675 editors optional proofgeneral_3.5-4.1.dsc e3a5a0bc1169725bca18f6066c154bab 20067 editors optional proofgeneral_3.5-4.1.diff.gz 30aab36e477ddba9de0f44798cd56c92 421216 editors optional proofgeneral_3.5-4.1_all.deb 2de3ba753a93cc8e9d4739cf0981754a 44672 editors optional proofgeneral-coq_3.5-4.1_all.deb 25cc1436a24f541c90d2053ca47c4e53 150294 editors optional proofgeneral-misc_3.5-4.1_all.deb 4ea53c95c39b853e160eefae4035212c 121478 editors optional proofgeneral-doc_3.5-4.1_all.deb d7bdfe3cebe4ee53c6a6457f
Bug#402179: [Bug-tar] Race condition in GNU tar test-suite
On Tue, 2006-12-19 at 15:46 +, Alex Owen wrote: > This patch should fix the problem. I guess the opotions are to aply > this patch to 1.16 or package 1.16.1. I guess applying the patch is > the better option if we wnat to fix this for etch. It's not clear to me that we need to disturb etch to fix this. It's "just" a race in a regression test, and I *think* 1.16 is built for all the architectures that matter for etch release, isn't it? If not, I'm certainly willing to apply the patch and upload this. Packaging 1.16.1 for unstable clearly makes sense, and I'll try to do that tonight or tomorrow. Bdale -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
Bug#403641: tetex-base: postrm fails if just unpackaged.
Frank Küster <[EMAIL PROTECTED]> wrote:
> Why is --quiet only used for update-updmap? It's the same script behind
> the three, and with "-v" it always says
IMHO, it's a bug that --quiet isn't used for all three calls. But this
--quiet here dates from before we introduced
dhit_check_run_without_errors(). With this function, the output of the
three update-* calls is redirected to a file, so whether using --quiet
or not is not that important.
I believe we should still call all of them with --quiet in this context,
because most of the info that comes in without this option is
user-oriented and misleading in case of a package installation:
echo "$progname has updated '$output_file'. If you want to"
if [ "$progname" = "update-language" ]; then
echo "enable the new patterns, you should run fmtutil-sys or fmtutil"
echo "(with option --all, or with a particular format specified)."
elif [ "$progname" = "update-updmap" ]; then
echo "enable the map files with this new file, you should run" \
"updmap-sys or updmap."
elif [ "$progname" = "update-fmtutil" ]; then
echo "enable the new formats, you should run fmtutil-sys or fmtutil"
echo "(with option --all or --missing)."
This info is really intended for users running the update-* scripts
manually.
> ${progname}'s -v option is deprecated. The default mode of operation will
> be verbose as soon as enough packages use the --quiet option. Please update
> your scripts accordingly.\n\n" >&2; quiet=0; shift ;;
Yeah, we should really do the switch to verbose mode right after the
release of etch. Otherwise, we can still wait...
It's a pity we didn't do it for etch. :-|
--
Florent
Bug#403572: Patch for the the upcoming 3.5-4.1 NMU of proofgeneral
Dear maintainer of proofgeneral, Your package was recently reported with a RC bug (FTBFS). Therefore, I send this NMU to fix the RC issue, given the lack of input about this bug, the easiness of the fix I used this occasion to fix trivial lintian warnings as I don't doubt this will make the release managers refuse this update for etch. The NMU changelog is: Source: proofgeneral Version: 3.5-4.1 Distribution: unstable Urgency: low Maintainer: Christian Perrier <[EMAIL PROTECTED]> Date: Tue, 19 Dec 2006 08:27:28 +0100 Closes: 403572 Changes: proofgeneral (3.5-4.1) unstable; urgency=low . * Non-maintainer upload to fix an RC bug * Move debhelper and mzscheme to Build-Depends. Closes: 403572 Lintian warnings are things that should be taken seriously. * Lintian fixes: - Remove useless CVS directory minlog/CVS - Use 4 as debhelper compatibility (through debian/compat) -- diff -Nru proofgeneral-3.5.old/debian/changelog proofgeneral-3.5/debian/changelog --- proofgeneral-3.5.old/debian/changelog 2006-12-19 08:18:05.340607627 +0100 +++ proofgeneral-3.5/debian/changelog 2006-12-19 08:29:32.146355156 +0100 @@ -1,3 +1,14 @@ +proofgeneral (3.5-4.1) unstable; urgency=low + + * Non-maintainer upload to fix an RC bug + * Move debhelper and mzscheme to Build-Depends. Closes: 403572 +Lintian warnings are things that should be taken seriously. + * Lintian fixes: +- Remove useless CVS directory minlog/CVS +- Use 4 as debhelper compatibility (through debian/compat) + + -- Christian Perrier <[EMAIL PROTECTED]> Tue, 19 Dec 2006 08:27:28 +0100 + proofgeneral (3.5-4) unstable; urgency=low * Added support for Minlog diff -Nru proofgeneral-3.5.old/debian/compat proofgeneral-3.5/debian/compat --- proofgeneral-3.5.old/debian/compat 1970-01-01 01:00:00.0 +0100 +++ proofgeneral-3.5/debian/compat 2006-12-19 08:29:37.714403111 +0100 @@ -0,0 +1 @@ +4 diff -Nru proofgeneral-3.5.old/debian/control proofgeneral-3.5/debian/control --- proofgeneral-3.5.old/debian/control 2006-12-19 08:18:05.360607798 +0100 +++ proofgeneral-3.5/debian/control 2006-12-19 08:27:24.653198792 +0100 @@ -2,7 +2,7 @@ Section: editors Priority: optional Maintainer: Stefan Schimanski <[EMAIL PROTECTED]> -Build-Depends-Indep: debhelper (>= 4.1.16), mzscheme +Build-Depends: debhelper (>= 4.1.16), mzscheme Standards-Version: 3.6.1.0 Package: proofgeneral diff -Nru proofgeneral-3.5.old/debian/rules proofgeneral-3.5/debian/rules --- proofgeneral-3.5.old/debian/rules 2006-12-19 08:18:05.304607319 +0100 +++ proofgeneral-3.5/debian/rules 2006-12-19 08:29:59.646590324 +0100 @@ -1,7 +1,6 @@ #!/usr/bin/make -f #export DH_VERBOSE=1 -export DH_COMPAT=3 # the path should be changed in proofgeneral.postinst/prerm and proofgeneral.sh too PREFIX=share/emacs/site-lisp/proofgeneral diff -Nru proofgeneral-3.5.old/minlog/CVS/Entries proofgeneral-3.5/minlog/CVS/Entries --- proofgeneral-3.5.old/minlog/CVS/Entries 2006-12-19 08:18:05.452608585 +0100 +++ proofgeneral-3.5/minlog/CVS/Entries 1970-01-01 01:00:00.0 +0100 @@ -1,8 +0,0 @@ -/Makefile/1.4/Tue Apr 12 18:09:14 2005// -/README/1.6/Fri Jul 29 16:35:21 2005// -/minlog-abbrev.el/1.4/Sun Oct 9 11:56:10 2005// -/minlog-config.el/1.4/Sun Oct 9 11:50:18 2005// -/minlog-syntax.el/1.2/Wed Nov 29 14:07:15 2006// -/mzfork.c/1.2/Sat Sep 4 20:46:32 2004// -/minlog.el/1.23/Wed Dec 6 14:49:48 2006// -D diff -Nru proofgeneral-3.5.old/minlog/CVS/Repository proofgeneral-3.5/minlog/CVS/Repository --- proofgeneral-3.5.old/minlog/CVS/Repository 2006-12-19 08:18:05.452608585 +0100 +++ proofgeneral-3.5/minlog/CVS/Repository 1970-01-01 01:00:00.0 +0100 @@ -1 +0,0 @@ -proofgeneral/minlog diff -Nru proofgeneral-3.5.old/minlog/CVS/Root proofgeneral-3.5/minlog/CVS/Root --- proofgeneral-3.5.old/minlog/CVS/Root 2006-12-19 08:18:05.452608585 +0100 +++ proofgeneral-3.5/minlog/CVS/Root 1970-01-01 01:00:00.0 +0100 @@ -1 +0,0 @@ -:ext:[EMAIL PROTECTED]:/home/math/logik/proofgeneral/CVS signature.asc Description: Digital signature
Bug#374834: menu: Patch to just fork and die, instead of waiting on a si
On Mon, Dec 18, 2006 at 11:05:15AM +0100, Tim Dijkstra wrote: > On Mon, 18 Dec 2006 00:33:58 +0100 > Bill Allombert <[EMAIL PROTECTED]> wrote: > > > > > What worry me about the patch is the fact that create_lock() and > > > > check_dpkglock() are not performed in the same order. In particular, if > > > > create_lock() fail we exit with error 0 instead of 1 thus maybe > > > > concealing a real error. > > > > > > You used to exit with 1 only if both creat_lock and check_dpkglock were > > > false at the same time. If that is what you want, that is easy to fix. > > > New patch attached. The locking logic is now the same as in the original. > > > > If I am not mistaken, your new patch adds a race condition between > > create_lock() and check_dpkglock(). If dpkg release the lock after > > create_lock() and before check_dpkglock(), then we do exit(1) while we > > should not. In the original version, check_dpkglock was checked first > > so this race condition was not possible. > > I don't think that can happen. In normal circumstances we are a child > process of dpkg until the fork. So it can't release the lock in between > those two calls; it is waiting for us. You are absolutly correct: this cannot happen in normal circumstances. > Anyway, in the attached patch I swapped the order of check_dpkglock and > create_lock again to match the original. This one looks fine, thanks. > > Sorry to be so slow dealing with this issue... > > That's OK. I'm happy we're dealing with it know. And it is good you are > reviewing the patch thoroughly. I do not have much choice, since i cannot really test it. Cheers, -- Bill. <[EMAIL PROTECTED]> Imagine a large blue swirl here. -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
Bug#403165: No items in default GNOME menu upon upgrade from 2.14 to 2.16
Le mardi 19 décembre 2006 à 11:37 +, Paulo Silva a écrit : > Same problem here. > > Removing ~/.config/menus/ and ~/.local/ solved the problem (don't know > if both are needed). Do you remember what was in the .config/menus directory? Paolo, Jean-Luc: if you have a .config/menus directory, I'd like to see its contents. If it's not too big, please attach it to the bug report. I'd also like to know how it was generated, e.g. with alacarte or something else. Thanks for your input, -- Josselin Mouette/\./\ "Do you have any more insane proposals for me?"
Bug#403703: Bug #403703: already fixed upstream
Quoting Patrice Fournier <[EMAIL PROTECTED]>: The fix for bug #2111 ((http://www.cups.org/strfiles/2111/str2111.patch) did fix the problem for me. Seems I spoke too soon... the fix works fine on single page jobs, but multiple pages jobs still produce errors. I will do more tests and confirm later. -- Patrice Fournier -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
Bug#403775: evolution: crash on startup: gtkhtml-ERROR **: file htmlgdkpainter.c
Package: evolution
Version: 2.6.3-3
Severity: grave
Justification: renders package unusable
$ evolution
CalDAV Eplugin starting up ...
libnm_glib_nm_state_cb: dbus returned an error.
(org.freedesktop.DBus.Error.ServiceUnknown) The name
org.freedesktop.NetworkManager was not provided by any .service files
gtkhtml-ERROR **: file htmlgdkpainter.c: line 111 (begin): assertion failed:
(gdk_painter->pixmap == NULL)
aborting...
---Begin Strace log---
[..]
stat64("/home/nueces/.gnome2_private/Evolution", {st_mode=S_IFREG|0644,
st_size=579, ...}) = 0
time(NULL) = 1166549380
futex(0x1085f1cc, FUTEX_WAKE, 1)= 1
futex(0x1085f1c8, FUTEX_WAKE, 1)= 1
futex(0x107756d8, FUTEX_WAKE, 1)= 1
open("/home/nueces/.themes/Fantastic-1.1/gtk-2.0/Toolbar/toolbar-bg.png",
O_RDONLY|O_LARGEFILE) = 40
fstat64(40, {st_mode=S_IFREG|0644, st_size=250, ...}) = 0
mmap(NULL, 131072, PROT_READ|PROT_WRITE, MAP_PRIVATE|MAP_ANONYMOUS, -1, 0) =
0x35777000
read(40, "\211PNG\r\n\32\n\0\0\0\rIHDR\0\0\\0\0\0\21\10\6\0\0"..., 131072)
= 250
read(40, "", 131072)= 0
_llseek(40, 0, [0], SEEK_SET) = 0
read(40, "\211PNG\r\n\32\n\0\0\0\rIHDR\0\0\\0\0\0\21\10\6\0\0"..., 131072)
= 250
close(40) = 0
munmap(0x35777000, 131072) = 0
write(2, "\ngtkhtml-ERROR **: file htmlgdkp"..., 120) = 120
rt_sigprocmask(SIG_UNBLOCK, [ABRT], NULL, 8) = 0
write(26, "KEYS.000", 8)= 8
tgkill(4511, 4511, SIGABRT) = 0
--- SIGABRT (Aborted) @ 0 (0) ---
write(3, "[EMAIL PROTECTED]"..., 16320) = 16320
write(3, " \27\0\2\0\0\0\0", 8) = 8
write(3, "+\27\0\1", 4) = 4
read(3, "\26\0+b\1\340\0\353\1\340\0\353\0\0\0\0\0\0\377\321\2\266"..., 32) = 32
read(3, "\f\0+b\1\340\0\353\0\0\1$\2\266\0/\0\0\200\0\20#\271P\20"..., 32) = 32
read(3, "\23\35,\24\1\340\t\4\1\340\t\4\0\35X\24\20\35V\360\20\35"..., 32) = 32
read(3, "\23\35,\30\1\340\t\5\1\340\t\5\0\35X\24\20\35V\360\20\35"..., 32) = 32
read(3, "\1\2,v\0\0\0\0\1\340\0w\20\35W\20\177\370%\260\0\0\0\0"..., 32) = 32
clone(child_stack=0, flags=CLONE_CHILD_CLEARTID|CLONE_CHILD_SETTID|SIGCHLD,
child_tidptr=0x300409a8) = 4529
futex(0xe0b80e4, FUTEX_WAKE, 1) = 1
waitpid(4529, [{WIFEXITED(s) && WEXITSTATUS(s) == 0}], 0) = 4529
--- SIGCHLD (Child exited) @ 0 (0) ---
exit_group(1) = ?
---End Strace log---
$ file /home/nueces/.themes/Fantastic-1.1/gtk-2.0/Toolbar/toolbar-bg.png
/home/nueces/.themes/Fantastic-1.1/gtk-2.0/Toolbar/toolbar-bg.png: PNG image
data, 48 x 17, 8-bit/color RGBA, non-interlaced
-- System Information:
Debian Release: 4.0
APT prefers unstable
APT policy: (500, 'unstable')
Architecture: powerpc (ppc)
Shell: /bin/sh linked to /bin/dash
Kernel: Linux 2.6.18-3-powerpc
Locale: LANG=es_AR.UTF-8, LC_CTYPE=es_AR.UTF-8 (charmap=UTF-8)
Versions of packages evolution depends on:
ii dbus 1.0.2-1simple interprocess messaging syst
ii evolution-common 2.6.3-3architecture independent files for
ii evolution-data-server 1.6.3-3evolution database backend server
ii gconf22.16.0-3 GNOME configuration database syste
ii gnome-icon-theme 2.14.2-2 GNOME Desktop icon theme
ii gtkhtml3.83.12.1-2 HTML rendering/editing library - b
ii libart-2.0-2 2.3.17-1 Library of functions for 2D graphi
ii libatk1.0-0 1.12.3-1 The ATK accessibility toolkit
ii libaudiofile0 0.2.6-6Open-source version of SGI's audio
ii libavahi-client3 0.6.15-2 Avahi client library
ii libavahi-common3 0.6.15-2 Avahi common library
ii libavahi-glib10.6.15-2 Avahi glib integration library
ii libbonobo2-0 2.14.0-3 Bonobo CORBA interfaces library
ii libbonoboui2-02.14.0-5 The Bonobo UI library
ii libc6 2.3.6.ds1-9GNU C Library: Shared libraries
ii libcairo2 1.2.4-4The Cairo 2D vector graphics libra
ii libcamel1.2-8 1.6.3-3The Evolution MIME message handlin
ii libdbus-1-3 1.0.2-1simple interprocess messaging syst
ii libdbus-glib-1-2 0.71-3 simple interprocess messaging syst
ii libebook1.2-5 1.6.3-3Client library for evolution addre
ii libecal1.2-6 1.6.3-3Client library for evolution calen
ii libedataserver1.2-7 1.6.3-3Utility library for evolution data
ii libedataserverui1.2-6 1.6.3-3GUI utility library for evolution
ii libegroupwise1.2-10 1.6.3-3Client library for accessing group
ii libesd0 0.2.36-3 Enlightened Sound Daemon - Shared
ii libexchange-storage1.2-1 1.6.3-3Backend library for evolution cale
ii libfontconfig12.4.2-1generic fo
Bug#394392: msync() in recent kernels fails LSB
On Tue, 2006-12-19 at 17:08 +0100, Martin Michlmayr wrote: > So it seems that the patches needed for msync() conformance we applied > from 2.6.19 to our 2.6.18 cause filesystem corruption, see the current > discussion on this on lkml. From what I understand it, plain 2.6.18 > is not LSB 3.1 conform and you need some fixes which are associated > with filesystem corruption. While Andrew, Linus and co are currently > trying to come up with a patch, I think it might be better for us to > simply back out these patches. What doe it take to get an exception > for this LSB test? Surely the reasons cited above (fails with 2.6.18, > a fairly current kernel and the patches to fix it are associated with > fs corruption) are pretty good arguments for an exception... I brought this up at our weekly conference call, which generated quite a lot of discussion. The argument against issuing a waiver is that this isn't strictly required; a distro could fix the problem by downgrading the kernel to 2.6.16. I've also forwarded your message to Ian Murdock, who is the current chair of the LSB Steering Committee. The process for getting an exception is as follows: - Release a product with a problem. - Run the tests, and fail in some way. - Request a waiver from the LSB Specification Authority. There's a link for doing so from the certification site. Of course, the problem is that we have to make a decision now, so we also have an unofficial process of discussing known issues. That process has already been started. -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
Bug#401153: NMU uploaded
On Tue, December 19, 2006 1:09 am, Andreas Barth said: > * Andreas Barth ([EMAIL PROTECTED]) [061214 08:41]: >> I uploaded an NMU of your package to experimental to see if the test >> case really works on buildds. > > It failed as expected on powerpc and also on sparc, and worked on at > least amd64 and powerpc - so I think this package can be uploaded to > unstable, unless there is reason not to do it. > > In other words, I intend to upload it to unstable during the next days. please go on, I won't have time enough in the next days. Thanks -- mattia :wq!
Bug#389236: marked as done (gforth_0.6.2-7(hppa/unstable): FTBFS: broken hppa assembly)
Your message dated Tue, 19 Dec 2006 17:02:02 + with message-id <[EMAIL PROTECTED]> and subject line Bug#389236: fixed in gforth 0.6.2-7.2 has caused the attached Bug report to be marked as done. This means that you claim that the problem has been dealt with. If this is not the case it is now your responsibility to reopen the Bug report if necessary, and/or fix the problem forthwith. (NB: If you are a system administrator and have no idea what I am talking about this indicates a serious mail system misconfiguration somewhere. Please contact me immediately.) Debian bug tracking system administrator (administrator, Debian Bugs database) --- Begin Message --- Package: gforth Version: 0.6.2-7 Severity: serious There was an error while trying to autobuild your package: The fic instruction requires a space id. For linux, it can simply be changed to have a "4," after the left paren. For hp-ux compatibility, and to not be depending on the way parisc linux vm works, it should do a ldsid and mtsp... feel free to pester me to figure out the patch. lamont > Automatic build of gforth_0.6.2-7 on peri by sbuild/hppa 85 > Build started at 20060921-2004 [...] > ** Using build dependencies supplied by package: > Build-Depends: debhelper, autoconf, automake [...] > support.c:107: warning: pointer targets in passing argument 1 of 'cstr' > differ in signedness > support.c: In function 'listlfind': > support.c:190: warning: pointer targets in passing argument 2 of 'memcasecmp' > differ in signedness > support.c: In function 'hashlfind': > support.c:203: warning: pointer targets in passing argument 2 of 'memcasecmp' > differ in signedness > gcc -c -I./../arch/hppa -I. -Wall -O2 -DHAVE_CONFIG_H > -DDEFAULTPATH='".:/usr/lib/gforth/site-forth:/usr/share/gforth/site-forth:/usr/lib/gforth/0.6.2:/usr/share/gforth/0.6.2"' > -o ../arch/hppa/cache.o ../arch/hppa/cache.c > /tmp/cc6jnspd.s: Assembler messages: > /tmp/cc6jnspd.s:18: Error: Invalid operands > make[3]: *** [../arch/hppa/cache.o] Error 1 > make[3]: Leaving directory `/build/buildd/gforth-0.6.2/engine' > make[2]: *** [engines] Error 2 > make[2]: Leaving directory `/build/buildd/gforth-0.6.2' > make[1]: *** [kernel/version.fs] Error 2 > make[1]: Leaving directory `/build/buildd/gforth-0.6.2' > make: *** [build-stamp] Error 2 A full build log can be found at: http://buildd.debian.org/build.php?arch=hppa&pkg=gforth&ver=0.6.2-7 --- End Message --- --- Begin Message --- Source: gforth Source-Version: 0.6.2-7.2 We believe that the bug you reported is fixed in the latest version of gforth, which is due to be installed in the Debian FTP archive: gforth_0.6.2-7.2.diff.gz to pool/main/g/gforth/gforth_0.6.2-7.2.diff.gz gforth_0.6.2-7.2.dsc to pool/main/g/gforth/gforth_0.6.2-7.2.dsc gforth_0.6.2-7.2_amd64.deb to pool/main/g/gforth/gforth_0.6.2-7.2_amd64.deb A summary of the changes between this version and the previous one is attached. Thank you for reporting the bug, which will now be closed. If you have further comments please address them to [EMAIL PROTECTED], and the maintainer will reopen the bug report if appropriate. Debian distribution maintenance software pp. Andreas Barth <[EMAIL PROTECTED]> (supplier of updated gforth package) (This message was generated automatically at their request; if you believe that there is a problem with it please contact the archive administrators by mailing [EMAIL PROTECTED]) -BEGIN PGP SIGNED MESSAGE- Hash: SHA1 Format: 1.7 Date: Tue, 19 Dec 2006 16:48:45 + Source: gforth Binary: gforth Architecture: source amd64 Version: 0.6.2-7.2 Distribution: unstable Urgency: high Maintainer: Eric Schwartz (Skif) <[EMAIL PROTECTED]> Changed-By: Andreas Barth <[EMAIL PROTECTED]> Description: gforth - GNU Forth Language Environment Closes: 389236 Changes: gforth (0.6.2-7.2) unstable; urgency=high . * Non-maintainer upload. * Fix breackage on hppa based on the comments from Lamont. Closes: #389236 Files: f478d5055fe9df604a16fce52670e85d 586 interpreters optional gforth_0.6.2-7.2.dsc d471a5ee50513d8f9b7023ca7e9bc494 63754 interpreters optional gforth_0.6.2-7.2.diff.gz dfa91ce338adc57bf73affa2bd6151e1 779630 interpreters optional gforth_0.6.2-7.2_amd64.deb -BEGIN PGP SIGNATURE- Version: GnuPG v1.4.1 (GNU/Linux) iD8DBQFFiBiTmdOZoew2oYURAmdgAJ9JviSz4GBRnmNROuGdFOQsW5XanACgoaJy AXCtj3tG01/CfqGJTpdEJ20= =5vgr -END PGP SIGNATURE- --- End Message ---
Bug#375850: john removed from testing: modifies conffile
You are aware that this bug has resulted in package 'john' from being removed from testing, and isn't presently being considered for inclusion in etch? Justin -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
Bug#354355: sympa: Please stop kidding
I'm just a bit puzzled by such strange collaborative work... Couldn't it be better to try and work on the same source code base ? I know that ego is important in volunteer work, but it looks rather an unproductive way to go from the outside. Thanks anyway for the recent progress on Sympa. Just my 2 cents as a user, Le mardi 19 décembre 2006 à 15:26 +0100, Stefan Hornburg (Racke) a écrit : > Jean Charles Delepine wrote: > > "Stefan Hornburg (Racke)" <[EMAIL PROTECTED]> écrivait (wrote) : > > > >> I'll take this out. It is more hassle than it is really worth. > > > > We need, now, a workable package for etch. 5.2.3-0.2 is not that > > package, 5.2.3-0.3 will have bugs not in my 5.2.3-0.7. > > And vice versa. Please continue your constructive critiscm like > in your former posts. > > Bye > Racke > > -- Olivier BERGER <[EMAIL PROTECTED]> Ingénieur Recherche - Dept INF INT Evry (http://www.int-evry.fr) OpenPGP-Id: 1024D/6B829EEC
Bug#403767: Licensing information is missing
Package: sqlalchemy Severity: serious Hi, debian/copyright only references the LICENSE: --8<-- SQLAlchemy is licensed under an MIT-style license (see LICENSE). Other incorporated projects may be licensed under different licenses. All licenses allow for non-commercial and commercial use. --8<-- I did not see any other licenses or copyrights in the source tree. Here's the LICENSE file: # See the file LICENSE at the top of the source tree. Please include the full licensing information in debian/copyright, that is the full contents of the LICENSE file. And while we're at it, debian/copyright is supposed supposed to list the copyright statements, you can start collecting them with: % grep -ri copyright . At the very least include the main author's copyright in debian/copyright: Copyright (C) 2004,2005,2006 Michael Bayer [EMAIL PROTECTED] Thanks, -- System Information: Debian Release: 4.0 APT prefers unstable APT policy: (500, 'unstable'), (1, 'experimental') Architecture: i386 (i686) Shell: /bin/sh linked to /bin/bash Kernel: Linux 2.6.18-3-686 Locale: LANG=fr_FR.UTF-8, LC_CTYPE=fr_FR.UTF-8 (charmap=UTF-8) -- Loïc Minier <[EMAIL PROTECTED]> "Forget your stupid theme park! I'm gonna make my own! With hookers! And blackjack! In fact, forget the theme park!" -- Bender
Bug#396631: Same problem with latest version of apache2/libapr1
On Tue, Dec 19, 2006 at 09:55:39AM +0100, Andreas Barth wrote: [...] > I uploaded packages for this architecture now on > http://people.debian.org/~aba/apr/ - the changes-file is signed by me > so that you know it was really me. [...] I just tested it. It works flawlessly! I'm not sure why building on the server itself doesn't work... I'd like to track that down, although I don't think it's related to this bug. My locally-built package seems to be unable to correctly process apache's Include directives, so maybe this is related to filesystem access. T -- Life is unfair. Ask too much from it, and it may decide you don't deserve what you have now either. -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
Bug#387103: closed by Peter Eisentraut <[EMAIL PROTECTED]> (Bug#387103: fixed in cdbs 0.4.48)
Hi, > cdbs (0.4.48) unstable; urgency=medium > . >* Reverse patches before cleaning build directory (simple-patchsys.mk) > (closes: #387103) Urgh, this is pretty ugly. One of the great things about tarball.mk is that you don't need to jump through hoops to get a clean source tarball. Reversing patches takes very long and doesn't buy you anything. Why not simply skip the reverse-patches for cleaning completely? E. g. with --- 1/rules/tarball.mk.in 2006-06-16 07:33:41 + +++ 1/rules/tarball.mk.in 2006-10-02 13:02:06 + @@ -99,5 +99,6 @@ rm -rf $(_cdbs_tarball_dir) # Ignore errors from this. These stamps may not exist yet. -rm $(_cdbs_tarball_stamps) + -rm debian/stamp-patch-* 2>/dev/null endif Thanks, Martin -- Martin Pitthttp://www.piware.de Ubuntu Developer http://www.ubuntu.com Debian Developer http://www.debian.org signature.asc Description: Digital signature
Processed: Re: #365829
Processing commands for [EMAIL PROTECTED]: > tags 365829 + patch Bug#365829: kwin crashed (in KWinInternal::Workspace::updateMinimizedOfTransients ()) Tags were: fixed-upstream moreinfo Tags added: patch > thanks Stopping processing here. Please contact me if you need assistance. Debian bug tracking system administrator (administrator, Debian Bugs database) -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
Bug#365829: #365829
tags 365829 + patch thanks * Juergen Doenitz ([EMAIL PROTECTED]) [061217 05:31]: > [...] There is a patch upstream in http://bugs.kde.org/117677#c65 Cheers, Andi -- http://home.arcor.de/andreas-barth/ -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
Bug#389236: NMU uploaded
Hi, I uploaded an NMU of your package. Please see this as help to get the package into a releaseable condition for etch. Please find the used diff below. Cheers, Andi diff -ru ../gforth-0.6.2~/arch/hppa/cache.c ../gforth-0.6.2/arch/hppa/cache.c --- ../gforth-0.6.2~/arch/hppa/cache.c 2003-03-09 15:06:26.0 + +++ ../gforth-0.6.2/arch/hppa/cache.c 2006-12-19 16:48:09.0 + @@ -28,7 +28,7 @@ for(; p Tue, 19 Dec 2006 16:48:45 + + gforth (0.6.2-7.1) unstable; urgency=low * Non-maintainer upload. -- http://home.arcor.de/andreas-barth/ -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
Bug#402191: hercules cannot work with 2.6.18 host kernel, except as root
severity 402191 important thanks * Andreas Barth ([EMAIL PROTECTED]) [061208 12:00]: > hercules tries to setup tun device by itself. However, since 2.6.18, > this change has happend in the kernel: > [NET]: Require CAP_NET_ADMIN to create tuntap devices. > Date: Thu Jun 22 16:07:52 2006 -0700 > > The "usual" way to deal with this would be to use tunctl to add an > device, and tell hercules to use this device. However, this is not > supported (at least AFAICS). Other people, e.g. Frans Pop have reported to use hercules successfully with 2.6.18, so I assume that this is "just" a local configuration error. Downgrading to important for now. Cheers, Andi -- http://home.arcor.de/andreas-barth/ -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
Processed: Re: hercules cannot work with 2.6.18 host kernel, except as root
Processing commands for [EMAIL PROTECTED]: > severity 402191 important Bug#402191: hercules cannot work with 2.6.18 host kernel, except as root Severity set to `important' from `grave' > thanks Stopping processing here. Please contact me if you need assistance. Debian bug tracking system administrator (administrator, Debian Bugs database) -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
Bug#403621: Fwd: Re: IEEE copyrighted files in vhdl tools
Forwarding this message from debian-legal since it shows what is being done about this bug: -- Forwarded Message -- Subject: Re: IEEE copyrighted files in vhdl tools Date: Tuesday 19 December 2006 09:06 From: "Wesley J. Landaker" <[EMAIL PROTECTED]> To: debian-legal@lists.debian.org Cc: José "L. Redrejo" Rodríguez <[EMAIL PROTECTED]> On Tuesday 19 December 2006 08:50, José L. Redrejo Rodríguez wrote: > This file is needed to use any vhdl compiling/simulation tool, and I've > later noticed that ghdl [2], already accepted in Debian, contains more > vhdl headers, and even body vhdl copyrighted files that are delivered as > binary libraries, i.e. object files. I've filled a bug[3] trying to > clarify ghdl situation too. > So, in short, I'm not legally expert at all, and specially if the text > is not in my native language, so I would like to know if somebody could > help me to clarify the situation of: > - uploading freehdl (with one vhdl header) to main (noticing the ieee > copyrighted file in debian/copyright) > - uploading it to non-free > - how this can affect to ghdl, already in main and ready to be released > with Etch. For GHDL, the IEEE VHDL body files should not be there--I didn't actually notice that until you filed a bug on it. They are compiled just to get consistent interfaces--the implementation in the body files is not actually used (e.g. numeric_std functions are implemented internally). So there is a problem here that I will fix. For the header files, they are not copyrightable as they just declare an interface. The comments are the only thing that could be copyrightable. But, I think I may just rewrite the whole set of headers to remove any doubt--this is a pretty trivial exercise. If FreeHDL only has one header and you are really worried about it, you might just want to rewrite it from scratch. (And no, unfortunately GHDL isn't going to be in etch no matter what, because of an unresolved bug in GNU ld on ia64 and now the freeze.) -- Wesley J. Landaker <[EMAIL PROTECTED]> OpenPGP FP: 4135 2A3B 4726 ACC5 9094 0097 F0A9 8A4C 4CD6 E3D2 --- -- Wesley J. Landaker <[EMAIL PROTECTED]> OpenPGP FP: 4135 2A3B 4726 ACC5 9094 0097 F0A9 8A4C 4CD6 E3D2 pgpFKbVQkDA4K.pgp Description: PGP signature
Bug#403703: Bug #403703: already fixed upstream
Upstream bug #2166 has been marked as a duplicate of bug #2111 (http://www.cups.org/str.php?L2111). The fix for bug #2111 ((http://www.cups.org/strfiles/2111/str2111.patch) did fix the problem for me. -- Patrice Fournier -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
Bug#394392: msync() in recent kernels fails LSB
* Jeff Licquia <[EMAIL PROTECTED]> [2006-10-20 19:17]: > >From a recent run of the LSB 3.1 tests: > > 10|852 /tset/LSB.os/mfiles/msync_P/T.msync_P 22:58:49|TC Start, scenario ref > 858-0 > > FSG internal testing showed that Fedora Core 5's 2.6.18 kernel does not > fail in the same way. I believe I've traced it to a backported change > from 2.6.19 development. The specific commit touching msync() is > 204ec841fbea3e5138168edbc3a76d46747cc987 in git; it relies on several > commits immediately preceding it. I've built Linus's tree on amd64, and > it passes the test. I have not, however, built a 2.6.18 kernel with > this patch and tested it, though it's the only patch in the Fedora > kernel which touches the msync() code. So it seems that the patches needed for msync() conformance we applied from 2.6.19 to our 2.6.18 cause filesystem corruption, see the current discussion on this on lkml. From what I understand it, plain 2.6.18 is not LSB 3.1 conform and you need some fixes which are associated with filesystem corruption. While Andrew, Linus and co are currently trying to come up with a patch, I think it might be better for us to simply back out these patches. What doe it take to get an exception for this LSB test? Surely the reasons cited above (fails with 2.6.18, a fairly current kernel and the patches to fix it are associated with fs corruption) are pretty good arguments for an exception... -- Martin Michlmayr http://www.cyrius.com/ -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
Bug#402179: [Bug-tar] Race condition in GNU tar test-suite
tags 402179 + patch upstream fixed-upstream thanks Attached is the diff for tests/append02 between upstream released versions 1.16 and 1.16.1. This patch should fix the problem. I guess the opotions are to aply this patch to 1.16 or package 1.16.1. I guess applying the patch is the better option if we wnat to fix this for etch. The only testing of this patch I have done is by runing the following... probably someone else should confirm the fix! This script should prove the point runing essentially the same code stand alone... based on the eariler stand alone code in this bug report ---8<--- #!/bin/sh # Make sure file timestamps in the archive will not differ MTIME="[EMAIL PROTECTED]" export TAR_OPTIONS="-H posix --pax-option=exthdr.name=%d/PaxHeaders/%f,delete=mtime,delete=atime,delete=ctime" echo hello > file1 echo goodbye > file2 while :; do tar $MTIME -cf archive.1 file1 file2 tar $MTIME -cf archive.2 -T /dev/null tar $MTIME -rf archive.2 file1 tar $MTIME -rf archive.2 file2 if cmp archive.1 archive.2 >/dev/null; then echo -n . else echo -n + fi done ---8<--- Regards Alex Owen --- tar-1.16/tests/append02.at 2006-07-24 10:09:30.0 +0100 +++ tar-1.16.1/tests/append02.at 2006-11-13 09:17:46.0 + @@ -44,19 +44,22 @@ genfile --file file1 genfile --file file2 +# Make sure file timestamps in the archive will not differ +MTIME="[EMAIL PROTECTED]" + # For PAX archives, we need to make sure extended header names are -# reproducible. +# reproducible and that their contents won't change with time if test $[]TEST_TAR_FORMAT = posix; then - TAR_OPTIONS="$TAR_OPTIONS --pax-option=exthdr.name=%d/PaxHeaders/%f" + TAR_OPTIONS="$TAR_OPTIONS --pax-option=exthdr.name=%d/PaxHeaders/%f,delete=mtime,delete=atime,delete=ctime" fi echo Creating archive.1 -tar cf archive.1 file1 file2 +tar $MTIME -cf archive.1 file1 file2 echo Creating archive.2 -tar cfT archive.2 /dev/null -tar rf archive.2 file1 -tar rf archive.2 file2 +tar $MTIME -cf archive.2 -T /dev/null +tar $MTIME -rf archive.2 file1 +tar $MTIME -rf archive.2 file2 echo Comparing archives cmp archive.1 archive.2
Bug#403641: marked as done (tetex-base: postrm fails if just unpackaged.)
Your message dated Tue, 19 Dec 2006 15:32:18 + with message-id <[EMAIL PROTECTED]> and subject line Bug#403641: fixed in tetex-base 3.0.dfsg.3-4 has caused the attached Bug report to be marked as done. This means that you claim that the problem has been dealt with. If this is not the case it is now your responsibility to reopen the Bug report if necessary, and/or fix the problem forthwith. (NB: If you are a system administrator and have no idea what I am talking about this indicates a serious mail system misconfiguration somewhere. Please contact me immediately.) Debian bug tracking system administrator (administrator, Debian Bugs database) --- Begin Message --- Package: tetex-base Version: 3.0.dfsg.3-3 Severity: serious Hi, It seems that you can't uninstall the package if things aren't set up properly. >From the buildd log I see: Selecting previously deselected package tetex-base. Unpacking tetex-base (from .../tetex-base_3.0.dfsg.3-3_all.deb) ... [...] E: Sub-process /usr/bin/dpkg returned an error code (1) apt-get failed. Package installation failed Trying to reinstall removed packages: Trying to uninstall newly installed packages: /usr/bin/sudo dpkg --root=/home/buildd/build/chroot-unstable --purge adduser dbus debhelper defoma docbook docbook-to-man ed file fontconfig-config gettext gettext-base html2text intltool-debian libdbus-1-3 libdbus-1-dev libexpat1 libfontconfig1 libfreetype6 libice6 libjpeg62 libkpathsea4 libltdl3 libmagic1 libpaper1 libpng12-0 libpoppler0c2 libsm6 libsp1c2 libt1-5 libx11-6 libx11-data libxau6 libxaw7 libxdmcp6 libxext6 libxmu6 libxpm4 libxt6 locales mime-support odbcinst1debian1 pkg-config po-debconf sgml-base sgml-data sp sun-java5-bin sun-java5-demo sun-java5-jdk sun-java5-jre tetex-base tetex-bin tex-common tex4ht tex4ht-common ttf-dejavu ucf unixodbc whiptail x11-common xml-core [...] Removing tetex-base ... update-language: cannot read /etc/texmf/language.d/00tex.cnf dpkg: error processing tetex-base (--purge): subprocess post-removal script returned error exit status 1 The buildd log is at: http://buildd.debian.org/fetch.cgi?pkg=libdbus-java;ver=1.12-1;arch=amd64;stamp=1166177715 Kurt --- End Message --- --- Begin Message --- Source: tetex-base Source-Version: 3.0.dfsg.3-4 We believe that the bug you reported is fixed in the latest version of tetex-base, which is due to be installed in the Debian FTP archive: tetex-base_3.0.dfsg.3-4.diff.gz to pool/main/t/tetex-base/tetex-base_3.0.dfsg.3-4.diff.gz tetex-base_3.0.dfsg.3-4.dsc to pool/main/t/tetex-base/tetex-base_3.0.dfsg.3-4.dsc tetex-base_3.0.dfsg.3-4_all.deb to pool/main/t/tetex-base/tetex-base_3.0.dfsg.3-4_all.deb tetex-doc_3.0.dfsg.3-4_all.deb to pool/main/t/tetex-base/tetex-doc_3.0.dfsg.3-4_all.deb tetex-extra_3.0.dfsg.3-4_all.deb to pool/main/t/tetex-base/tetex-extra_3.0.dfsg.3-4_all.deb A summary of the changes between this version and the previous one is attached. Thank you for reporting the bug, which will now be closed. If you have further comments please address them to [EMAIL PROTECTED], and the maintainer will reopen the bug report if appropriate. Debian distribution maintenance software pp. Frank Küster <[EMAIL PROTECTED]> (supplier of updated tetex-base package) (This message was generated automatically at their request; if you believe that there is a problem with it please contact the archive administrators by mailing [EMAIL PROTECTED]) -BEGIN PGP SIGNED MESSAGE- Hash: SHA1 Format: 1.7 Date: Tue, 19 Dec 2006 14:51:37 +0100 Source: tetex-base Binary: tetex-extra tetex-doc tetex-base Architecture: source all Version: 3.0.dfsg.3-4 Distribution: unstable Urgency: high Maintainer: Debian TeX maintainers <[EMAIL PROTECTED]> Changed-By: Frank Küster <[EMAIL PROTECTED]> Description: tetex-base - Basic TeX input files of teTeX tetex-doc - The documentation component of the Debian teTeX packages tetex-extra - Additional TeX input files of teTeX Closes: 402953 403641 Changes: tetex-base (3.0.dfsg.3-4) unstable; urgency=high . * The "King of QA release" * Do not assume that tex-common is configured when postrm is called with "remove" (closes: #403641). This is a RC bug, hence the urgency. Thanks to Kurt Roeckx <[EMAIL PROTECTED]> for reporting and for looking closely at an unrelated failed build log. * Remove obsolete conffile in the tetex-doc package if it is unchanged [frank] * Register documentation in the TeX section (closes: #402953) Files: 91a0e173ac9f417aaa1918ff7664f9f7 830 tex optional tetex-base_3.0.dfsg.3-4.dsc e57f6489d4b20c38808105b98fc837c0 528964 tex optional tetex-base_3.0.dfsg.3-4.diff.gz ab32ecb49a72c2fc42c0ed83cc35b3f3 22418328 tex optional tetex-base_3.0.dfsg.3-4_all.deb 4710430e96d4d81e92d56aea0c49f4ad 10848018 tex optional tetex-extra_3.0.dfsg.3-4_all.deb 3e31ead10f2b7eb25caeb7f109177123 44733032 doc optional tetex-doc_3.0.dfsg.3-4_all.deb -BEGIN PGP SIGNATURE- Version: GnuPG
Bug#379137: SIGSEGV: segmentation violation
Hi, On Friday 15 December 2006 01:14, Thomas K. wrote: > Package: boinc-client > Version: 5.4.11-4 > Followup-For: Bug #379137 > > boinc_client gets segfault on launch. > version from boinc-website works fine. > > [...] > 2006-12-15 01:04:50 [---] No general preferences found - using BOINC > defaults > 2006-12-15 01:04:50 [---] Local control only allowed > 2006-12-15 01:04:50 [---] Listening on port 31416 > > SIGSEGV: segmentation violationSpeicherzugriffsfehler Could you please install strace: apt-get install strace And then run strace boinc_client and send me the output of this command. Make sure that no other BOINC client is running by calling: /etc/init.d/boinc-client stop and killall boinc_client Grüße, Frank pgpZBzkduXjrh.pgp Description: PGP signature
Bug#403703: fixed upstream?
tags 403703 + upstream fixed-upstream patch thanks Loooking again at upstream bug STR #2166 the developers think this is a duplicate of upstream bug STR #2111: http://www.cups.org/str.php?L2111 STR #2111 has been fixed upstream... patch can be found here: http://www.cups.org/strfiles/2111/str2111.patch Regards Alex Owen -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
