Bug#334998: marked as done (dpkg-dev: Should include .orig also with 0something debian version.)
Your message dated Tue, 22 Jan 2008 12:04:36 +0100 with message-id [EMAIL PROTECTED] and subject line Bug#334998: dpkg-dev: Should include .orig also with 0something debian version. 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) ---BeginMessage--- Package: dpkg-dev Version: 1.10.28 Severity: wishlist Well, subjects says it all, when making experimental uploads, with debian version of -0experimental.n or similar, in order to be older than the -1 version which will go to unstable, dpkg-buildpackage does not include the .orig, and thus often builds are uploaded by mistake without the .orig, which is a pain. And yes, i know about -sa or whatever it was, but it is so easy to forget. I think it would be reasonable to include the .orig with -0experimental.1 or something such uploads, or at least issue a warning about this if such a version is detected and -sa not provided. Friendly, Sven Luther -- System Information: Debian Release: 3.1 Architecture: powerpc (ppc) Kernel: Linux 2.6.12-1-powerpc Locale: LANG=fr_FR.UTF-8, LC_CTYPE=fr_FR.UTF-8 (charmap=UTF-8) Versions of packages dpkg-dev depends on: ii binutils 2.15-6 The GNU assembler, linker and bina ii cpio 2.5-1.3GNU cpio -- a program to manage ar ii make 3.80-9 The GNU version of the make util ii patch 2.5.9-2Apply a diff file to an original ii perl [perl5] 5.8.4-8Larry Wall's Practical Extraction ii perl-modules 5.8.4-8Core Perl modules -- no debconf information ---End Message--- ---BeginMessage--- On Sun, 23 Sep 2007, Frank Lichtenheld wrote: I think it would be reasonable to include the .orig with -0experimental.1 or something such uploads, or at least issue a warning about this if such a version is detected and -sa not provided. Since we have '~' nowadays for problems like these and everything aside from the obvious stuff we currently catch (i.e. 0|1|0.1) is just pure guesswork I would suggest closing this bug. (The only somewhat sane way to improve automatic -sa handling is requested by #28701 dpkg-genchanges should compare the version numbers, IMHO) And given that the sane way is now implemented, this bug doesn't need to stay open. Closing it with this mail. Cheers, -- Raphaël Hertzog Le best-seller français mis à jour pour Debian Etch : http://www.ouaza.com/livre/admin-debian/ ---End Message---
Bug#4655: dpkg-buildpackage should do sanity checks on version number
On Tue, Jan 22, 2008 at 12:12:03PM +0100, Raphael Hertzog wrote: On Thu, 11 May 2006, Frank Lichtenheld wrote: I would leave the bug open. While I have no intentions to hack something like this into the current version of dpkg-parsechangelog, I would not say that it is a thing not ever worth thinking about. We could add this warning to dpkg-genchanges. We already have the code that extracts the two last version numbers... it's a trivial 2 line patch. Fine with me. Gruesse, -- Frank Lichtenheld [EMAIL PROTECTED] www: http://www.djpig.de/ -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Bug#462018: marked as done (start-stop-daemon: Unable to set initgroups() with gid 13 (Operation not permitted))
Your message dated Tue, 22 Jan 2008 11:32:02 + with message-id [EMAIL PROTECTED] and subject line Bug#462018: fixed in dpkg 1.14.16.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) ---BeginMessage--- Package: dpkg Version: 1.14.16.1 Severity: normal Hello, The packages polipo (in /usr/lib/polipo/polipo-control) and ipw3945d (in /etc/init.d/ipw3945d) are among those packages that say start-stop-daemon --chuid myuser:mygroup where myuser is a system user and mygroup is its primary group. This invocation seems to no longer work with the new version of dpkg, even though it works simply to omit :mygroup from the invocation. (By works I mean that start-stop-daemon succeeds, but the resulting daemon process stays in the root group.) start-stop-daemon: Unable to set initgroups() with gid 13 (Operation not permitted) Thanks, Ken -- System Information: Debian Release: lenny/sid APT prefers unstable APT policy: (500, 'unstable'), (500, 'stable') Architecture: i386 (i686) Kernel: Linux 2.6.22 (SMP w/2 CPU cores) Locale: LANG=zh_TW.UTF-8, LC_CTYPE=zh_TW.UTF-8 (charmap=UTF-8) Shell: /bin/sh linked to /bin/bash Versions of packages dpkg depends on: ii coreutils 5.97-5.7 The GNU core utilities ii libc6 2.7-6 GNU C Library: Shared libraries dpkg recommends no packages. -- no debconf information -- Edit this signature at http://www.digitas.harvard.edu/cgi-bin/ken/sig One thing that UNIX does not need is more features. It is successful in part because it has a small number of good ideas that work well together. Merely adding features does not make it easier for users to do things -- it just makes the manual thicker. -- Rob Pike, Brian W. Kernighan, 1983. signature.asc Description: Digital signature ---End Message--- ---BeginMessage--- Source: dpkg Source-Version: 1.14.16.2 We believe that the bug you reported is fixed in the latest version of dpkg, which is due to be installed in the Debian FTP archive: dpkg-dev_1.14.16.2_all.deb to pool/main/d/dpkg/dpkg-dev_1.14.16.2_all.deb dpkg_1.14.16.2.dsc to pool/main/d/dpkg/dpkg_1.14.16.2.dsc dpkg_1.14.16.2.tar.gz to pool/main/d/dpkg/dpkg_1.14.16.2.tar.gz dpkg_1.14.16.2_i386.deb to pool/main/d/dpkg/dpkg_1.14.16.2_i386.deb dselect_1.14.16.2_i386.deb to pool/main/d/dpkg/dselect_1.14.16.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. Guillem Jover [EMAIL PROTECTED] (supplier of updated dpkg 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, 22 Jan 2008 13:05:22 +0200 Source: dpkg Binary: dpkg dpkg-dev dselect Architecture: source i386 all Version: 1.14.16.2 Distribution: unstable Urgency: low Maintainer: Dpkg Developers [EMAIL PROTECTED] Changed-By: Guillem Jover [EMAIL PROTECTED] Description: dpkg - package maintenance system for Debian dpkg-dev - package building tools for Debian dselect- user tool to manage Debian packages Closes: 462018 Changes: dpkg (1.14.16.2) unstable; urgency=low . * Change uid after changing gid and initializing supplementary groups in start-stop-daemon. Closes: #462018 * Change temporary dpkg Breaks on dpkg-dev (= 1.14.13) and (= 1.14.14) to Conflicts, so that users from etch can upgrade to sid (or lenny once dpkg has migrated). Files: fc502102e5ec404cc5ca54c74c2a8ae9 1053 admin required dpkg_1.14.16.2.dsc b5f860a12aff9144a17854a8475f04d1 6305454 admin required dpkg_1.14.16.2.tar.gz 42e3f02f1b6c2d85b861a3a115ea94fb 2161230 admin required dpkg_1.14.16.2_i386.deb f71da4f5356b7a95d07f4c70cf80c431 742590 admin optional dselect_1.14.16.2_i386.deb e22f17f4325a5958771452b39163cb72 603052 utils optional dpkg-dev_1.14.16.2_all.deb -BEGIN PGP SIGNATURE- Version: GnuPG v1.4.6 (GNU/Linux) iD8DBQFHldBfuW9ciZ2SjJsRAr7VAJ0Yz6TjvStz4y3ssSpbdccaSbJa+ACfbVQa Elt2DIZMvAGMgf1GXd45N8o= =OCyR -END PGP SIGNATURE- ---End Message---
Bug#462075: dpkg: start-stop-daemon --chuid no longer changes the primary group
Package: dpkg Version: 1.14.16.1 Severity: important This might be considered critical as it makes some unrelated software break (not start). man start-stop-daemon says, and in 1.14.15 it worked, that with '--chuid user' the primary group is also set. But in 1.14.16.1 it is no longer the case, only the user id is changed. -- Michał Politowski Talking has been known to lead to communication if practiced carelessly. signature.asc Description: Digital signature
Bug#462072: dpkg: start-stop-daemon segfaults when using --group (starting asterisk)
Package: dpkg
Version: 1.14.16.1
Severity: important
Starting asterisk using start-stop-daemon:
# start-stop-daemon --start --group asterisk --pidfile
/var/run/asterisk/asterisk.pid --exec /usr/sbin/asterisk -- -U asterisk
Segmentation fault
The problem is the --group asterisk:
Using GDB (don't know how to get debugging symbols for start-stop-daemon
:-/):
# gdb --args start-stop-daemon --start --group asterisk --pidfile
/var/run/asterisk/asterisk.pid --exec /usr/sbin/asterisk -- -U asterisk
GNU gdb 6.7.1-debian
(no debugging symbols found)
Using host libthread_db library /lib/libthread_db.so.1.
(gdb) r
Starting program: /sbin/start-stop-daemon --start --group asterisk
--pidfile /var/run/asterisk/asterisk.pid --exec /usr/sbin/asterisk -- -U
asterisk
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
Program received signal SIGSEGV, Segmentation fault.
0xb7e5ddec in strcmp () from /lib/libc.so.6
(gdb) bt
#0 0xb7e5ddec in strcmp () from /lib/libc.so.6
#1 0xb7de7b6d in _nss_compat_initgroups_dyn () from /lib/libnss_compat.so.2
#2 0xb7e7ead6 in ?? () from /lib/libc.so.6
#3 0xb7e7ecbd in initgroups () from /lib/libc.so.6
#4 0x0804ab75 in ?? ()
#5 0x in ?? ()
Using strace:
# strace start-stop-daemon --start --group asterisk --pidfile
/var/run/asterisk/asterisk.pid --exec /usr/sbin/asterisk -- -U asterisk
chdir(/) = 0
getgid32() = 0
getgroups32(0, []) = 0
getgroups32(0, []) = 0
open(/proc/sys/kernel/ngroups_max, O_RDONLY) = 3
read(3, 65536\n, 31) = 6
close(3)= 0
open(/etc/group, O_RDONLY|0x8 /* O_??? */) = 3
fcntl64(3, F_GETFD) = 0
fcntl64(3, F_SETFD, FD_CLOEXEC) = 0
_llseek(3, 0, [0], SEEK_CUR)= 0
fstat64(3, {st_mode=S_IFREG|0644, st_size=637, ...}) = 0
mmap2(NULL, 637, PROT_READ, MAP_SHARED, 3, 0) = 0xb7ef1000
_llseek(3, 637, [637], SEEK_SET)= 0
--- SIGSEGV (Segmentation fault) @ 0 (0) ---
+++ killed by SIGSEGV +++
Process 31911 detached
Starting without --group asterisk works (but is not a fix, of course)
-- System Information:
Debian Release: lenny/sid
APT prefers unstable
APT policy: (500, 'unstable')
Architecture: i386 (i686)
Kernel: Linux 2.6.18-028stab053 (SMP w/2 CPU cores; PREEMPT)
Locale: LANG=C, LC_CTYPE=C (charmap=ANSI_X3.4-1968)
Shell: /bin/sh linked to /bin/bash
Versions of packages dpkg depends on:
ii coreutils 5.97-5.7 The GNU core utilities
ii libc6 2.7-6 GNU C Library: Shared libraries
dpkg recommends no packages.
-- no debconf information
--
To UNSUBSCRIBE, email to [EMAIL PROTECTED]
with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Bug#462079: dpkg-dev: dpkg-genchanges tries to use substvars
Package: dpkg-dev
Version: 1.14.16.1
When documenting, in the changelog, the use of a variable, say
${misc:Depends}, dpkg-genchanges tries to substitute it and warns about
an unknown substitution variable.
In the end, the variable name is removed in the generated changes file.
--
.''`.
: :' : We are debian.org. Lower your prices, surrender your code.
`. `' We will add your hardware and software distinctiveness to
`-our own. Resistance is futile.
signature.asc
Description: Ceci est une partie de message numériquement signée
Bug#462089: dpkg-dev: don't substitute vars in debian/changelog
Package: dpkg-dev
Version: 1.14.16.1
Severity: normal
Hi,
don't substitute vars in debian/changelog.
from kdepimlibs5-dev package changelog:
* kdepimlibs5-dev depends on kdelibs5-dev = 4:4.0.0-1 instead of
${binary:Version}.
produces in .changes:
* kdepimlibs5-dev depends on kdelibs5-dev = 4:4.0.0-1 instead of 4:4.0.0-4.
cheers,
Fathi
-- System Information:
Debian Release: lenny/sid
APT prefers unstable
APT policy: (500, 'unstable')
Architecture: amd64 (x86_64)
Kernel: Linux 2.6.23-1-amd64 (SMP w/2 CPU cores)
Locale: LANG=fr_FR.UTF-8, LC_CTYPE=fr_FR.UTF-8 (charmap=UTF-8)
Shell: /bin/sh linked to /bin/bash
Versions of packages dpkg-dev depends on:
ii binutils2.18.1~cvs20080103-1 The GNU assembler, linker and bina
ii bzip2 1.0.4-2 high-quality block-sorting file co
ii cpio2.9-9GNU cpio -- a program to manage ar
ii dpkg1.14.16.1package maintenance system for Deb
ii libtimedate-perl1.1600-9 Time and date functions for Perl
ii lzma4.43-12 Compression method of 7z format in
ii make3.81-3 The GNU version of the make util
ii patch 2.5.9-4 Apply a diff file to an original
ii perl [perl5]5.8.8-12 Larry Wall's Practical Extraction
ii perl-modules5.8.8-12 Core Perl modules
Versions of packages dpkg-dev recommends:
ii build-essential 11.3 informational list of build-essent
ii gcc [c-compiler] 4:4.2.2-2 The GNU C compiler
ii gcc-3.4 [c-compiler] 3.4.6-6The GNU C compiler
ii gcc-4.1 [c-compiler] 4.1.2-19 The GNU C compiler
ii gcc-4.2 [c-compiler] 4.2.2-7The GNU C compiler
-- no debconf information
--
To UNSUBSCRIBE, email to [EMAIL PROTECTED]
with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Bug#462098: dpkg-genchanges doesn't handle unicode in Changed-By field properly
Package: dpkg-dev Version: 1.14.16 Severity: serious Hi, since I updated my pbuilder chroot today (including dpkg 1.14.16.1) every package I build has a broken Changed-By field in the changes file. Before it contained my last name in proper UTF8, today it contains my last name with UTF8-in-ASCII, i.e. Changed-By: Sebastian Dröge [EMAIL PROTECTED] This marked my last uploads as NMU with wrong version number, thus I set the severity to serious. Bye -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Bug#462104: dpkg: [S-S-D] --pidfile and --retry seriously broken
Package: dpkg Version: 1.14.16 Severity: critical Quoting the changelog: * Keep checking for the process when start-stop-daemon is called with --retry even if the daemon removed the pidfile. Closes: #460903 This though broke s-s-d completely if you use --retry and --pidfile together, as now s-s-d will block for the amount of time specified by --retry, even if the process itself has stopped already. E.g. in network-manager I have start-stop-daemon --stop --retry 60 --quiet --pidfile $PIDFILE \ --oknodo --user $USER --exec $DAEMON Since 1.14.16, s-s-d will block now for 60 secs *always*, although the daemon is usually stopped withing less than a second. I'm filing with severity critical, because now an upgrade of network-manager will cause the update process to hang for 60 secs. Many users will believe that it crashed or hangs and abort the installation/upgrade. I tested this with other daemons, and e.g. added --retry 60 to /etc/init.d/ssh, which also caused the stop action to last 60 secs now. Cheers, Michael -- System Information: Debian Release: lenny/sid APT prefers unstable APT policy: (500, 'unstable'), (300, 'experimental') Architecture: i386 (i686) Kernel: Linux 2.6.23.14 Locale: LANG=de_DE.UTF-8, LC_CTYPE=de_DE.UTF-8 (charmap=UTF-8) Shell: /bin/sh linked to /bin/dash Versions of packages dpkg depends on: ii coreutils 5.97-5.7 The GNU core utilities ii libc6 2.7-6 GNU C Library: Shared libraries dpkg recommends no packages. -- no debconf information -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Processed: Re: Bug#462119: /etc/cron.daily/exim4-base error
Processing commands for [EMAIL PROTECTED]: reassign 462119 dpkg Bug#462119: /etc/cron.daily/exim4-base error Bug reassigned from package `exim4-base' to `dpkg'. severity 462119 normal Bug#462119: /etc/cron.daily/exim4-base error Severity set to `normal' from `minor' close 462119 1.14.16.2 Bug#462119: /etc/cron.daily/exim4-base error 'close' is deprecated; see http://www.debian.org/Bugs/Developer#closing. Bug marked as fixed in version 1.14.16.2, send any further explanations to Robert E. Riding [EMAIL PROTECTED] merge 462119 462018 Bug#462018: start-stop-daemon: Unable to set initgroups() with gid 13 (Operation not permitted) Bug#462119: /etc/cron.daily/exim4-base error Merged 462018 462119. 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: Re: Bug#462111: tor: fails to start: Unable to set initgroups() with gid 125
Processing commands for [EMAIL PROTECTED]: reassign 462110 dpkg 1.14.16.1 Bug#462110: tor: Fails to install because fails to start because calls initgroups() after setuid() Bug reassigned from package `tor' to `dpkg'. reassign 462111 dpkg 1.14.16.1 Bug#462111: tor: fails to start: Unable to set initgroups() with gid 125 Bug reassigned from package `tor' to `dpkg'. forcemerge 462018 462111 462110 Bug#462018: start-stop-daemon: Unable to set initgroups() with gid 13 (Operation not permitted) Bug#462110: tor: Fails to install because fails to start because calls initgroups() after setuid() Bug#462111: tor: fails to start: Unable to set initgroups() with gid 125 Bug#462119: /etc/cron.daily/exim4-base error Forcibly Merged 462018 462110 462111 462119. 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#462119: marked as done (/etc/cron.daily/exim4-base error)
Your message dated Tue, 22 Jan 2008 20:45:35 +0100 with message-id [EMAIL PROTECTED] and subject line Bug#462141: mldonkey-server: init script fails in initgroups() 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) ---BeginMessage--- Package: exim4-base Version: 4.68-2 Severity: minor anacron reports the following error, which occurs also when /etc/cron.daily/exim4-base is run alone: dusty:/etc/cron.daily# ./exim4-base start-stop-daemon: Unable to set initgroups() with gid 102 (Operation not permitted) start-stop-daemon: Unable to set initgroups() with gid 102 (Operation not permitted) dusty:/etc/cron.daily# -- Package-specific info: Exim version 4.68 #1 built 01-Nov-2007 19:21:36 Copyright (c) University of Cambridge 2006 Berkeley DB: Berkeley DB 4.6.21: (September 27, 2007) Support for: crypteq iconv() IPv6 GnuTLS move_frozen_messages Lookups: lsearch wildlsearch nwildlsearch iplsearch cdb dbm dbmnz dnsdb dsearch nis nis0 passwd Authenticators: cram_md5 plaintext Routers: accept dnslookup ipliteral manualroute queryprogram redirect Transports: appendfile/maildir/mailstore autoreply lmtp pipe smtp Fixed never_users: 0 Size of off_t: 8 Configuration file is /var/lib/exim4/config.autogenerated # /etc/exim4/update-exim4.conf.conf # # Edit this file and /etc/mailname by hand and execute update-exim4.conf # yourself or use 'dpkg-reconfigure exim4-config' # # Please note that this is _not_ a dpkg-conffile and that automatic changes # to this file might happen. The code handling this will honor your local # changes, so this is usually fine, but will break local schemes that mess # around with multiple versions of the file. # # update-exim4.conf uses this file to determine variable values to replace # the DEBCONFsomethingDEBCONF strings in the configuration template files. # # Most settings found in here do have corresponding questions in the # Debconf configuration, but not all of them. # # This is a Debian specific file dc_eximconfig_configtype='smarthost' dc_other_hostnames='' dc_local_interfaces='' dc_readhost='xmission.com' dc_relay_domains='' dc_minimaldns='false' dc_relay_nets='192.168.0.0/24' dc_smarthost='mail.xmission.com' CFILEMODE='644' dc_use_split_config='false' dc_hide_mailname='true' dc_mailname_in_oh='true' dc_localdelivery='mail_spool' mailname:dusty.savageroad.com -- System Information: Debian Release: lenny/sid APT prefers unstable APT policy: (500, 'unstable') Architecture: i386 (i686) Kernel: Linux 2.6.23.14 (PREEMPT) Locale: LANG=en_US, LC_CTYPE=en_US (charmap=ISO-8859-1) Shell: /bin/sh linked to /bin/bash Versions of packages exim4-base depends on: ii adduser 3.105 add and remove users and groups ii cron 3.0pl1-103 management of regular background p ii debconf [debconf-2.0] 1.5.18 Debian configuration management sy ii exim4-config [exim4-config-2] 4.68-2 configuration for the Exim MTA (v4 ii libc6 2.7-6 GNU C Library: Shared libraries ii libdb4.6 4.6.21-5 Berkeley v4.6 Database Libraries [ ii lsb-base 3.1-24 Linux Standard Base 3.1 init scrip ii netbase 4.30 Basic TCP/IP networking system Versions of packages exim4-base recommends: ii bsd-mailx [mailx] 8.1.2-0.20071201cvs-2 A simple mail user agent ii mailx 1:20071201-2 Transitional package for mailx ren ii psmisc 22.6-1Utilities that use the proc filesy -- debconf information: exim4/purge_spool: false exim4-base/drec: exim4/move_exim3_spool: false ---End Message--- ---BeginMessage--- reassign 462141 dpkg 1.14.16.1 forcemerge 462141 462018 thanks On Tue, Jan 22, 2008 at 08:09:10PM +0100, Marco Herrn wrote: mlnet refuses to start with the message start-stop-daemon: Unable to set initgroups() with gid 118 (Operation not permitted) There exist bugreports against dpkg in relation to such a problem. For example #222524 and #462018. These are marked as fixed. #462018 is fixed in dpkg 1.14.16.2, but you have dpkg 1.14.16.1. Upgrade to dpkg 1.14.16.2. -- Lionel ---End Message---
Bug#462111: marked as done (tor: fails to start: Unable to set initgroups() with gid 125)
Your message dated Tue, 22 Jan 2008 20:45:35 +0100 with message-id [EMAIL PROTECTED] and subject line Bug#462141: mldonkey-server: init script fails in initgroups() 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) ---BeginMessage--- Package: tor Version: 0.1.2.19-1 Severity: important Hi, tor doesnt start. I get the following messages at boot or when stating tor from /etc/init.d: [EMAIL PROTECTED] % sudo /etc/init.d/tor start Raising maximum number of filedescriptors (ulimit -n) to 8192. Starting tor daemon: tor... start-stop-daemon: Unable to set initgroups() with gid 125 (Operation not permitted) gid 125 is the one created for tor: [EMAIL PROTECTED] % grep 125 /etc/group debian-tor:x:125: Regards Jean-Luc -- System Information: Debian Release: lenny/sid APT prefers unstable APT policy: (900, 'unstable') Architecture: amd64 (x86_64) Kernel: Linux 2.6.24-rc8-git5-k8-2 (SMP w/2 CPU cores; PREEMPT) Locale: LANG=fr_FR.UTF-8, LC_CTYPE=fr_FR.UTF-8 (charmap=UTF-8) Shell: /bin/sh linked to /bin/bash Versions of packages tor depends on: ii adduser3.105 add and remove users and groups ii libc6 2.7-6 GNU C Library: Shared libraries ii libevent1 1.3e-1An asynchronous event notification ii libssl0.9.80.9.8g-4 SSL shared libraries ii tsocks 1.8beta5-6transparent network access through ii zlib1g 1:1.2.3.3.dfsg-11 compression library - runtime Versions of packages tor recommends: ii privoxy 3.0.8-1Privacy enhancing HTTP Proxy ii socat 1.6.0.0-1 multipurpose relay for bidirection -- no debconf information ---End Message--- ---BeginMessage--- reassign 462141 dpkg 1.14.16.1 forcemerge 462141 462018 thanks On Tue, Jan 22, 2008 at 08:09:10PM +0100, Marco Herrn wrote: mlnet refuses to start with the message start-stop-daemon: Unable to set initgroups() with gid 118 (Operation not permitted) There exist bugreports against dpkg in relation to such a problem. For example #222524 and #462018. These are marked as fixed. #462018 is fixed in dpkg 1.14.16.2, but you have dpkg 1.14.16.1. Upgrade to dpkg 1.14.16.2. -- Lionel ---End Message---
Processed: Re: Bug#462141: mldonkey-server: init script fails in initgroups()
Processing commands for [EMAIL PROTECTED]: reassign 462141 dpkg 1.14.16 Bug#462141: mldonkey-server: init script fails in initgroups() Bug#462018: start-stop-daemon: Unable to set initgroups() with gid 13 (Operation not permitted) Bug#462110: tor: Fails to install because fails to start because calls initgroups() after setuid() Bug#462111: tor: fails to start: Unable to set initgroups() with gid 125 Bug#462119: /etc/cron.daily/exim4-base error Bug reassigned from package `dpkg' to `dpkg'. forcemerge 462018 462141 Bug#462018: start-stop-daemon: Unable to set initgroups() with gid 13 (Operation not permitted) Bug#462141: mldonkey-server: init script fails in initgroups() Bug#462110: tor: Fails to install because fails to start because calls initgroups() after setuid() Bug#462111: tor: fails to start: Unable to set initgroups() with gid 125 Bug#462119: /etc/cron.daily/exim4-base error Forcibly Merged 462018 462110 462111 462119 462141. kthxbye 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#462110: marked as done (tor: Fails to install because fails to start because calls initgroups() after setuid())
Your message dated Tue, 22 Jan 2008 20:45:35 +0100 with message-id [EMAIL PROTECTED] and subject line Bug#462141: mldonkey-server: init script fails in initgroups() 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) ---BeginMessage--- Package: tor Version: 0.1.2.19-1 [EMAIL PROTECTED]:~$ sudo dpkg --configure tor Setting up tor (0.1.2.19-1) ... debian-tor uid check: ok debian-tor homedir check: ok Raising maximum number of filedescriptors (ulimit -n) to 8192. Starting tor daemon: tor... start-stop-daemon: Unable to set initgroups() with gid 114 (Operation not permitted) invoke-rc.d: initscript tor, action start failed. dpkg: error processing tor (--configure): subprocess post-installation script returned error exit status 2 Errors were encountered while processing: tor [EMAIL PROTECTED]:~$ sudo /etc/init.d/tor start Raising maximum number of filedescriptors (ulimit -n) to 8192. Starting tor daemon: tor... start-stop-daemon: Unable to set initgroups() with gid 114 (Operation not permitted) strace extract: [pid 14502] open(/var/run/tor/tor.pid, O_RDONLY|O_LARGEFILE) = -1 ENOENT (No such file or directory) [pid 14502] chdir(/) = 0 [pid 14502] getuid32() = 0 [pid 14502] setuid32(114) = 0 [pid 14502] getgid32() = 0 [pid 14502] getgroups32(0, NULL)= 1 [pid 14502] getgroups32(1, [0]) = 1 [pid 14502] open(/proc/sys/kernel/ngroups_max, O_RDONLY) = 3 [pid 14502] read(3, 65536\n, 31) = 6 [pid 14502] close(3)= 0 [pid 14502] open(/etc/group, O_RDONLY|0x8 /* O_??? */) = 3 (...) [pid 14502] close(3)= 0 [pid 14502] setgroups32(1, [114]) = -1 EPERM (Operation not permitted) I think it is customary to call initgroups() _before_ calling setuid precisely because only root can call setuid(). -- System Information: Debian Release: lenny/sid APT prefers unstable APT policy: (500, 'unstable'), (1, 'experimental') Architecture: i386 (i686) Kernel: Linux 2.6.22-2-686 (SMP w/1 CPU core) Locale: LANG=fr_LU.UTF-8, LC_CTYPE=fr_LU.UTF-8 (charmap=UTF-8) Shell: /bin/sh linked to /bin/bash Versions of packages tor depends on: ii adduser3.105 add and remove users and groups ii libc6 2.7-6 GNU C Library: Shared libraries ii libevent1 1.3e-1An asynchronous event notification ii libssl0.9.80.9.8g-4 SSL shared libraries ii tsocks 1.8beta5-6transparent network access through ii zlib1g 1:1.2.3.3.dfsg-11 compression library - runtime Versions of packages tor recommends: ii privoxy 3.0.7-1Privacy enhancing HTTP Proxy ii socat 1.6.0.0-1 multipurpose relay for bidirection -- no debconf information ---End Message--- ---BeginMessage--- reassign 462141 dpkg 1.14.16.1 forcemerge 462141 462018 thanks On Tue, Jan 22, 2008 at 08:09:10PM +0100, Marco Herrn wrote: mlnet refuses to start with the message start-stop-daemon: Unable to set initgroups() with gid 118 (Operation not permitted) There exist bugreports against dpkg in relation to such a problem. For example #222524 and #462018. These are marked as fixed. #462018 is fixed in dpkg 1.14.16.2, but you have dpkg 1.14.16.1. Upgrade to dpkg 1.14.16.2. -- Lionel ---End Message---
Bug#462141: marked as done (mldonkey-server: init script fails in initgroups())
Your message dated Tue, 22 Jan 2008 20:45:35 +0100 with message-id [EMAIL PROTECTED] and subject line Bug#462141: mldonkey-server: init script fails in initgroups() 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) ---BeginMessage--- Package: mldonkey-server Version: 2.9.3-1 Severity: important mlnet refuses to start with the message start-stop-daemon: Unable to set initgroups() with gid 118 (Operation not permitted) There exist bugreports against dpkg in relation to such a problem. For example #222524 and #462018. These are marked as fixed. Therefore I am not really sure, this is a bug of mldonkey or dpkg. But since this problem was introduced with my last upgrade of mldonkey, I assume it is mldonkeys fault. -- System Information: Debian Release: lenny/sid APT prefers unstable APT policy: (500, 'unstable') Architecture: amd64 (x86_64) Kernel: Linux 2.6.17 Locale: LANG=C, [EMAIL PROTECTED] (charmap=ISO-8859-15) Shell: /bin/sh linked to /bin/bash Versions of packages mldonkey-server depends on: ii adduser3.105 add and remove users and groups ii debconf [debconf-2.0] 1.5.18Debian configuration management sy ii dpkg 1.14.16.1 package maintenance system for Deb ii libbz2-1.0 1.0.4-2 high-quality block-sorting file co ii libc6 2.7-6 GNU C Library: Shared libraries ii libfreetype6 2.3.5-1+b1FreeType 2 font engine, shared lib ii libgcc11:4.3-20080116-1 GCC support library ii libgd2-xpm 2.0.36~rc1~dfsg-1 GD Graphics Library version 2 ii libjpeg62 6b-14 The Independent JPEG Group's JPEG ii libpng12-0 1.2.15~beta5-3PNG library - runtime ii libstdc++6 4.3-20080116-1The GNU Standard C++ Library v3 ii mime-support 3.40-1MIME files 'mime.types' 'mailcap ii ucf3.004 Update Configuration File: preserv ii zlib1g 1:1.2.3.3.dfsg-11 compression library - runtime mldonkey-server recommends no packages. -- debconf information: * mldonkey-server/max_hard_download_rate: 28 * mldonkey-server/launch_at_startup: false * mldonkey-server/mldonkey_group: mldonkey mldonkey-server/false_password: * mldonkey-server/max_hard_upload_rate: 7 mldonkey-server/max_alive: 48 * mldonkey-server/run_as_user: mldonkey mldonkey-server/reown_file: false * mldonkey-server/mldonkey_niceness: 15 mldonkey-server/fasttrack_problem: * mldonkey-server/mldonkey_dir: /var/lib/mldonkey mldonkey-server/mldonkey_move: false ---End Message--- ---BeginMessage--- reassign 462141 dpkg 1.14.16.1 forcemerge 462141 462018 thanks On Tue, Jan 22, 2008 at 08:09:10PM +0100, Marco Herrn wrote: mlnet refuses to start with the message start-stop-daemon: Unable to set initgroups() with gid 118 (Operation not permitted) There exist bugreports against dpkg in relation to such a problem. For example #222524 and #462018. These are marked as fixed. #462018 is fixed in dpkg 1.14.16.2, but you have dpkg 1.14.16.1. Upgrade to dpkg 1.14.16.2. -- Lionel ---End Message---
Bug#462018: marked as done (start-stop-daemon: Unable to set initgroups() with gid 13 (Operation not permitted))
Your message dated Tue, 22 Jan 2008 20:45:35 +0100 with message-id [EMAIL PROTECTED] and subject line Bug#462141: mldonkey-server: init script fails in initgroups() 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) ---BeginMessage--- Package: dpkg Version: 1.14.16.1 Severity: normal Hello, The packages polipo (in /usr/lib/polipo/polipo-control) and ipw3945d (in /etc/init.d/ipw3945d) are among those packages that say start-stop-daemon --chuid myuser:mygroup where myuser is a system user and mygroup is its primary group. This invocation seems to no longer work with the new version of dpkg, even though it works simply to omit :mygroup from the invocation. (By works I mean that start-stop-daemon succeeds, but the resulting daemon process stays in the root group.) start-stop-daemon: Unable to set initgroups() with gid 13 (Operation not permitted) Thanks, Ken -- System Information: Debian Release: lenny/sid APT prefers unstable APT policy: (500, 'unstable'), (500, 'stable') Architecture: i386 (i686) Kernel: Linux 2.6.22 (SMP w/2 CPU cores) Locale: LANG=zh_TW.UTF-8, LC_CTYPE=zh_TW.UTF-8 (charmap=UTF-8) Shell: /bin/sh linked to /bin/bash Versions of packages dpkg depends on: ii coreutils 5.97-5.7 The GNU core utilities ii libc6 2.7-6 GNU C Library: Shared libraries dpkg recommends no packages. -- no debconf information -- Edit this signature at http://www.digitas.harvard.edu/cgi-bin/ken/sig One thing that UNIX does not need is more features. It is successful in part because it has a small number of good ideas that work well together. Merely adding features does not make it easier for users to do things -- it just makes the manual thicker. -- Rob Pike, Brian W. Kernighan, 1983. signature.asc Description: Digital signature ---End Message--- ---BeginMessage--- reassign 462141 dpkg 1.14.16.1 forcemerge 462141 462018 thanks On Tue, Jan 22, 2008 at 08:09:10PM +0100, Marco Herrn wrote: mlnet refuses to start with the message start-stop-daemon: Unable to set initgroups() with gid 118 (Operation not permitted) There exist bugreports against dpkg in relation to such a problem. For example #222524 and #462018. These are marked as fixed. #462018 is fixed in dpkg 1.14.16.2, but you have dpkg 1.14.16.1. Upgrade to dpkg 1.14.16.2. -- Lionel ---End Message---
Bug#456332: dpkg could use an elevated pre-depends or depends on lzma
Raphael Hertzog writes (Bug#456332: dpkg could use an elevated pre-depends or depends on lzma): On Tue, 18 Dec 2007, Ian Jackson wrote: IMO the lzma binary package should Provide a new virtual package name, lzma-deb-support or some such. Packages could Pre-Depend on that. What does it bring? I assume you mean why do it like that. The answer is that you don't need the lzma support in cases where it's not needed. The dependencies are more accurate. Also, see my previous comments: that dpkg should execute decompressors as subprocesses (the way it used to before doogie changed it). Decompression also takes more memory than bzip2 but with 32M for the bigger packages, I think it's okay. I have machines still in service with as little as 20Mby of RAM. Obviously they don't have the biggest packages but such memory use during decompression can be a problem. Ian. -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Bug#462075: strace of --chuid failing
Package: dpkg Version: 1.14.16.1 Architecture: i386 Here's (the tail of) an strace of a failed operation. It's trying to change to 126:126, but because it's changing the group *after* changing the user, it no longer has permission to. Most annoying. 11528 getuid32()= 0 11528 setuid32(126) = 0 11528 getgid32()= 0 11528 getgroups32(0, NULL) = 1 11528 getgroups32(1, [0]) = 1 11528 open(/proc/sys/kernel/ngroups_max, O_RDONLY) = -1 ENOENT (No such file or directory) 11528 open(/etc/group, O_RDONLY|0x8 /* O_??? */) = -1 ENOENT (No such file or directory) 11528 setgroups32(1, [126]) = -1 EPERM (Operation not permitted) 11528 write(2, start-stop-daemon: , 19) = 19 11528 write(2, Unable to set initgroups() with gid 126, 39) = 39 11528 write(2, (Operation not permitted)\n, 27) = 27 11528 exit_group(2) = ? -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Bug#432893: Sort out these bugs
Sorry, I have just been prompted to look what happened here and it seems that my message to 432893@ was misaddressed and bounced. I wrote: Following discussions on debian-dpkg and debian-policy and in #443334, we seem to have concluded that the correct behaviour for dpkg is to not run the postinst in the confusing case. That is, if the package was halfconfigured beforehand, then the postinst should not be run in an attempt to fix it. I think it's still correct that if the package wasn't broken to start with (ie, installed or trig*), a failing dpkg --remove should put the package back the way it started - ie, it should run the postinst and if that's successful the usual rules about the meaning of successful postinst should apply (basically, the package will then be installed or perhaps trig*). Ian. -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Bug#462075: marked as done (dpkg: start-stop-daemon --chuid no longer changes the primary group)
Your message dated Tue, 22 Jan 2008 22:02:04 + with message-id [EMAIL PROTECTED] and subject line Bug#462075: fixed in dpkg 1.14.16.3 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) ---BeginMessage--- Package: dpkg Version: 1.14.16.1 Severity: important This might be considered critical as it makes some unrelated software break (not start). man start-stop-daemon says, and in 1.14.15 it worked, that with '--chuid user' the primary group is also set. But in 1.14.16.1 it is no longer the case, only the user id is changed. -- Michał Politowski Talking has been known to lead to communication if practiced carelessly. signature.asc Description: Digital signature ---End Message--- ---BeginMessage--- Source: dpkg Source-Version: 1.14.16.3 We believe that the bug you reported is fixed in the latest version of dpkg, which is due to be installed in the Debian FTP archive: dpkg-dev_1.14.16.3_all.deb to pool/main/d/dpkg/dpkg-dev_1.14.16.3_all.deb dpkg_1.14.16.3.dsc to pool/main/d/dpkg/dpkg_1.14.16.3.dsc dpkg_1.14.16.3.tar.gz to pool/main/d/dpkg/dpkg_1.14.16.3.tar.gz dpkg_1.14.16.3_i386.deb to pool/main/d/dpkg/dpkg_1.14.16.3_i386.deb dselect_1.14.16.3_i386.deb to pool/main/d/dpkg/dselect_1.14.16.3_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. Guillem Jover [EMAIL PROTECTED] (supplier of updated dpkg 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, 22 Jan 2008 23:39:59 +0200 Source: dpkg Binary: dpkg dpkg-dev dselect Architecture: source i386 all Version: 1.14.16.3 Distribution: unstable Urgency: low Maintainer: Dpkg Developers [EMAIL PROTECTED] Changed-By: Guillem Jover [EMAIL PROTECTED] Description: dpkg - package maintenance system for Debian dpkg-dev - package building tools for Debian dselect- user tool to manage Debian packages Closes: 462072 462075 462079 462089 462098 462104 Changes: dpkg (1.14.16.3) unstable; urgency=low . [ Raphael Hertzog ] * Remove the :utf8 layer that utf8-encodes already valid utf8. Closes: #462098 * Disable variable substitution in dpkg-genchanges. Closes: #462079, #462089 . [ Guillem Jover ] * Make start-stop-daemon set the supplementary groups if the real user or group are different than the ones we should switch to. Closes: #462075 * Fix segfault in start-stop-daemon when using --group w/o --chuid (as a side effect, using --group alone works for the first time in years). Closes: #462072 * Fix timeout computations for start-stop-daemon --retry option. This has not worked properly for a long time (maybe never), but came to light due to #460903's fix. Closes: #462104 Files: 82d00c83e882ed0e936be77d3380c6e2 1053 admin required dpkg_1.14.16.3.dsc d4500753aa14ced741b35a03cbb10cb1 6297898 admin required dpkg_1.14.16.3.tar.gz 401ecc93210f394b5bc09c77e0b12eef 2161546 admin required dpkg_1.14.16.3_i386.deb 9ac61477ff789cb2aee3adca07c2c1e3 742942 admin optional dselect_1.14.16.3_i386.deb b906ae151eb307cd1f74d1793a8ad2ba 603772 utils optional dpkg-dev_1.14.16.3_all.deb -BEGIN PGP SIGNATURE- Version: GnuPG v1.4.6 (GNU/Linux) iD8DBQFHlmUFuW9ciZ2SjJsRAr4YAKC7lfTqCkRhJYZvidg7wfKyGpk/HACffSFp V2KK2Yovsqzkf3vAQKrfM6Q= =XW/z -END PGP SIGNATURE- ---End Message---
Bug#462072: marked as done (dpkg: start-stop-daemon segfaults when using --group (starting asterisk))
Your message dated Tue, 22 Jan 2008 22:02:04 +
with message-id [EMAIL PROTECTED]
and subject line Bug#462072: fixed in dpkg 1.14.16.3
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)
---BeginMessage---
Package: dpkg
Version: 1.14.16.1
Severity: important
Starting asterisk using start-stop-daemon:
# start-stop-daemon --start --group asterisk --pidfile
/var/run/asterisk/asterisk.pid --exec /usr/sbin/asterisk -- -U asterisk
Segmentation fault
The problem is the --group asterisk:
Using GDB (don't know how to get debugging symbols for start-stop-daemon
:-/):
# gdb --args start-stop-daemon --start --group asterisk --pidfile
/var/run/asterisk/asterisk.pid --exec /usr/sbin/asterisk -- -U asterisk
GNU gdb 6.7.1-debian
(no debugging symbols found)
Using host libthread_db library /lib/libthread_db.so.1.
(gdb) r
Starting program: /sbin/start-stop-daemon --start --group asterisk
--pidfile /var/run/asterisk/asterisk.pid --exec /usr/sbin/asterisk -- -U
asterisk
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
Program received signal SIGSEGV, Segmentation fault.
0xb7e5ddec in strcmp () from /lib/libc.so.6
(gdb) bt
#0 0xb7e5ddec in strcmp () from /lib/libc.so.6
#1 0xb7de7b6d in _nss_compat_initgroups_dyn () from /lib/libnss_compat.so.2
#2 0xb7e7ead6 in ?? () from /lib/libc.so.6
#3 0xb7e7ecbd in initgroups () from /lib/libc.so.6
#4 0x0804ab75 in ?? ()
#5 0x in ?? ()
Using strace:
# strace start-stop-daemon --start --group asterisk --pidfile
/var/run/asterisk/asterisk.pid --exec /usr/sbin/asterisk -- -U asterisk
chdir(/) = 0
getgid32() = 0
getgroups32(0, []) = 0
getgroups32(0, []) = 0
open(/proc/sys/kernel/ngroups_max, O_RDONLY) = 3
read(3, 65536\n, 31) = 6
close(3)= 0
open(/etc/group, O_RDONLY|0x8 /* O_??? */) = 3
fcntl64(3, F_GETFD) = 0
fcntl64(3, F_SETFD, FD_CLOEXEC) = 0
_llseek(3, 0, [0], SEEK_CUR)= 0
fstat64(3, {st_mode=S_IFREG|0644, st_size=637, ...}) = 0
mmap2(NULL, 637, PROT_READ, MAP_SHARED, 3, 0) = 0xb7ef1000
_llseek(3, 637, [637], SEEK_SET)= 0
--- SIGSEGV (Segmentation fault) @ 0 (0) ---
+++ killed by SIGSEGV +++
Process 31911 detached
Starting without --group asterisk works (but is not a fix, of course)
-- System Information:
Debian Release: lenny/sid
APT prefers unstable
APT policy: (500, 'unstable')
Architecture: i386 (i686)
Kernel: Linux 2.6.18-028stab053 (SMP w/2 CPU cores; PREEMPT)
Locale: LANG=C, LC_CTYPE=C (charmap=ANSI_X3.4-1968)
Shell: /bin/sh linked to /bin/bash
Versions of packages dpkg depends on:
ii coreutils 5.97-5.7 The GNU core utilities
ii libc6 2.7-6 GNU C Library: Shared libraries
dpkg recommends no packages.
-- no debconf information
---End Message---
---BeginMessage---
Source: dpkg
Source-Version: 1.14.16.3
We believe that the bug you reported is fixed in the latest version of
dpkg, which is due to be installed in the Debian FTP archive:
dpkg-dev_1.14.16.3_all.deb
to pool/main/d/dpkg/dpkg-dev_1.14.16.3_all.deb
dpkg_1.14.16.3.dsc
to pool/main/d/dpkg/dpkg_1.14.16.3.dsc
dpkg_1.14.16.3.tar.gz
to pool/main/d/dpkg/dpkg_1.14.16.3.tar.gz
dpkg_1.14.16.3_i386.deb
to pool/main/d/dpkg/dpkg_1.14.16.3_i386.deb
dselect_1.14.16.3_i386.deb
to pool/main/d/dpkg/dselect_1.14.16.3_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.
Guillem Jover [EMAIL PROTECTED] (supplier of updated dpkg 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, 22 Jan 2008 23:39:59 +0200
Source: dpkg
Binary: dpkg dpkg-dev dselect
Architecture: source i386 all
Version: 1.14.16.3
Distribution: unstable
Urgency: low
Maintainer: Dpkg Developers [EMAIL PROTECTED]
Changed-By: Guillem Jover [EMAIL PROTECTED]
Description:
dpkg - package maintenance system for Debian
Bug#462079: marked as done (dpkg-dev: dpkg-genchanges tries to use substvars)
Your message dated Tue, 22 Jan 2008 22:02:04 +
with message-id [EMAIL PROTECTED]
and subject line Bug#462079: fixed in dpkg 1.14.16.3
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)
---BeginMessage---
Package: dpkg-dev
Version: 1.14.16.1
When documenting, in the changelog, the use of a variable, say
${misc:Depends}, dpkg-genchanges tries to substitute it and warns about
an unknown substitution variable.
In the end, the variable name is removed in the generated changes file.
--
.''`.
: :' : We are debian.org. Lower your prices, surrender your code.
`. `' We will add your hardware and software distinctiveness to
`-our own. Resistance is futile.
signature.asc
Description: Ceci est une partie de message numériquement signée
---End Message---
---BeginMessage---
Source: dpkg
Source-Version: 1.14.16.3
We believe that the bug you reported is fixed in the latest version of
dpkg, which is due to be installed in the Debian FTP archive:
dpkg-dev_1.14.16.3_all.deb
to pool/main/d/dpkg/dpkg-dev_1.14.16.3_all.deb
dpkg_1.14.16.3.dsc
to pool/main/d/dpkg/dpkg_1.14.16.3.dsc
dpkg_1.14.16.3.tar.gz
to pool/main/d/dpkg/dpkg_1.14.16.3.tar.gz
dpkg_1.14.16.3_i386.deb
to pool/main/d/dpkg/dpkg_1.14.16.3_i386.deb
dselect_1.14.16.3_i386.deb
to pool/main/d/dpkg/dselect_1.14.16.3_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.
Guillem Jover [EMAIL PROTECTED] (supplier of updated dpkg 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, 22 Jan 2008 23:39:59 +0200
Source: dpkg
Binary: dpkg dpkg-dev dselect
Architecture: source i386 all
Version: 1.14.16.3
Distribution: unstable
Urgency: low
Maintainer: Dpkg Developers [EMAIL PROTECTED]
Changed-By: Guillem Jover [EMAIL PROTECTED]
Description:
dpkg - package maintenance system for Debian
dpkg-dev - package building tools for Debian
dselect- user tool to manage Debian packages
Closes: 462072 462075 462079 462089 462098 462104
Changes:
dpkg (1.14.16.3) unstable; urgency=low
.
[ Raphael Hertzog ]
* Remove the :utf8 layer that utf8-encodes already valid utf8.
Closes: #462098
* Disable variable substitution in dpkg-genchanges. Closes: #462079, #462089
.
[ Guillem Jover ]
* Make start-stop-daemon set the supplementary groups if the real user or
group are different than the ones we should switch to. Closes: #462075
* Fix segfault in start-stop-daemon when using --group w/o --chuid (as
a side effect, using --group alone works for the first time in years).
Closes: #462072
* Fix timeout computations for start-stop-daemon --retry option. This has
not worked properly for a long time (maybe never), but came to light
due to #460903's fix. Closes: #462104
Files:
82d00c83e882ed0e936be77d3380c6e2 1053 admin required dpkg_1.14.16.3.dsc
d4500753aa14ced741b35a03cbb10cb1 6297898 admin required dpkg_1.14.16.3.tar.gz
401ecc93210f394b5bc09c77e0b12eef 2161546 admin required dpkg_1.14.16.3_i386.deb
9ac61477ff789cb2aee3adca07c2c1e3 742942 admin optional
dselect_1.14.16.3_i386.deb
b906ae151eb307cd1f74d1793a8ad2ba 603772 utils optional
dpkg-dev_1.14.16.3_all.deb
-BEGIN PGP SIGNATURE-
Version: GnuPG v1.4.6 (GNU/Linux)
iD8DBQFHlmUFuW9ciZ2SjJsRAr4YAKC7lfTqCkRhJYZvidg7wfKyGpk/HACffSFp
V2KK2Yovsqzkf3vAQKrfM6Q=
=XW/z
-END PGP SIGNATURE-
---End Message---
Bug#462098: marked as done (dpkg-genchanges doesn't handle unicode in Changed-By field properly)
Your message dated Tue, 22 Jan 2008 22:02:04 + with message-id [EMAIL PROTECTED] and subject line Bug#462098: fixed in dpkg 1.14.16.3 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) ---BeginMessage--- Package: dpkg-dev Version: 1.14.16 Severity: serious Hi, since I updated my pbuilder chroot today (including dpkg 1.14.16.1) every package I build has a broken Changed-By field in the changes file. Before it contained my last name in proper UTF8, today it contains my last name with UTF8-in-ASCII, i.e. Changed-By: Sebastian Dröge [EMAIL PROTECTED] This marked my last uploads as NMU with wrong version number, thus I set the severity to serious. Bye ---End Message--- ---BeginMessage--- Source: dpkg Source-Version: 1.14.16.3 We believe that the bug you reported is fixed in the latest version of dpkg, which is due to be installed in the Debian FTP archive: dpkg-dev_1.14.16.3_all.deb to pool/main/d/dpkg/dpkg-dev_1.14.16.3_all.deb dpkg_1.14.16.3.dsc to pool/main/d/dpkg/dpkg_1.14.16.3.dsc dpkg_1.14.16.3.tar.gz to pool/main/d/dpkg/dpkg_1.14.16.3.tar.gz dpkg_1.14.16.3_i386.deb to pool/main/d/dpkg/dpkg_1.14.16.3_i386.deb dselect_1.14.16.3_i386.deb to pool/main/d/dpkg/dselect_1.14.16.3_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. Guillem Jover [EMAIL PROTECTED] (supplier of updated dpkg 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, 22 Jan 2008 23:39:59 +0200 Source: dpkg Binary: dpkg dpkg-dev dselect Architecture: source i386 all Version: 1.14.16.3 Distribution: unstable Urgency: low Maintainer: Dpkg Developers [EMAIL PROTECTED] Changed-By: Guillem Jover [EMAIL PROTECTED] Description: dpkg - package maintenance system for Debian dpkg-dev - package building tools for Debian dselect- user tool to manage Debian packages Closes: 462072 462075 462079 462089 462098 462104 Changes: dpkg (1.14.16.3) unstable; urgency=low . [ Raphael Hertzog ] * Remove the :utf8 layer that utf8-encodes already valid utf8. Closes: #462098 * Disable variable substitution in dpkg-genchanges. Closes: #462079, #462089 . [ Guillem Jover ] * Make start-stop-daemon set the supplementary groups if the real user or group are different than the ones we should switch to. Closes: #462075 * Fix segfault in start-stop-daemon when using --group w/o --chuid (as a side effect, using --group alone works for the first time in years). Closes: #462072 * Fix timeout computations for start-stop-daemon --retry option. This has not worked properly for a long time (maybe never), but came to light due to #460903's fix. Closes: #462104 Files: 82d00c83e882ed0e936be77d3380c6e2 1053 admin required dpkg_1.14.16.3.dsc d4500753aa14ced741b35a03cbb10cb1 6297898 admin required dpkg_1.14.16.3.tar.gz 401ecc93210f394b5bc09c77e0b12eef 2161546 admin required dpkg_1.14.16.3_i386.deb 9ac61477ff789cb2aee3adca07c2c1e3 742942 admin optional dselect_1.14.16.3_i386.deb b906ae151eb307cd1f74d1793a8ad2ba 603772 utils optional dpkg-dev_1.14.16.3_all.deb -BEGIN PGP SIGNATURE- Version: GnuPG v1.4.6 (GNU/Linux) iD8DBQFHlmUFuW9ciZ2SjJsRAr4YAKC7lfTqCkRhJYZvidg7wfKyGpk/HACffSFp V2KK2Yovsqzkf3vAQKrfM6Q= =XW/z -END PGP SIGNATURE- ---End Message---
Bug#462089: marked as done (dpkg-dev: don't substitute vars in debian/changelog)
Your message dated Tue, 22 Jan 2008 22:02:04 +
with message-id [EMAIL PROTECTED]
and subject line Bug#462089: fixed in dpkg 1.14.16.3
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)
---BeginMessage---
Package: dpkg-dev
Version: 1.14.16.1
Severity: normal
Hi,
don't substitute vars in debian/changelog.
from kdepimlibs5-dev package changelog:
* kdepimlibs5-dev depends on kdelibs5-dev = 4:4.0.0-1 instead of
${binary:Version}.
produces in .changes:
* kdepimlibs5-dev depends on kdelibs5-dev = 4:4.0.0-1 instead of 4:4.0.0-4.
cheers,
Fathi
-- System Information:
Debian Release: lenny/sid
APT prefers unstable
APT policy: (500, 'unstable')
Architecture: amd64 (x86_64)
Kernel: Linux 2.6.23-1-amd64 (SMP w/2 CPU cores)
Locale: LANG=fr_FR.UTF-8, LC_CTYPE=fr_FR.UTF-8 (charmap=UTF-8)
Shell: /bin/sh linked to /bin/bash
Versions of packages dpkg-dev depends on:
ii binutils2.18.1~cvs20080103-1 The GNU assembler, linker and bina
ii bzip2 1.0.4-2 high-quality block-sorting file co
ii cpio2.9-9GNU cpio -- a program to manage ar
ii dpkg1.14.16.1package maintenance system for Deb
ii libtimedate-perl1.1600-9 Time and date functions for Perl
ii lzma4.43-12 Compression method of 7z format in
ii make3.81-3 The GNU version of the make util
ii patch 2.5.9-4 Apply a diff file to an original
ii perl [perl5]5.8.8-12 Larry Wall's Practical Extraction
ii perl-modules5.8.8-12 Core Perl modules
Versions of packages dpkg-dev recommends:
ii build-essential 11.3 informational list of build-essent
ii gcc [c-compiler] 4:4.2.2-2 The GNU C compiler
ii gcc-3.4 [c-compiler] 3.4.6-6The GNU C compiler
ii gcc-4.1 [c-compiler] 4.1.2-19 The GNU C compiler
ii gcc-4.2 [c-compiler] 4.2.2-7The GNU C compiler
-- no debconf information
---End Message---
---BeginMessage---
Source: dpkg
Source-Version: 1.14.16.3
We believe that the bug you reported is fixed in the latest version of
dpkg, which is due to be installed in the Debian FTP archive:
dpkg-dev_1.14.16.3_all.deb
to pool/main/d/dpkg/dpkg-dev_1.14.16.3_all.deb
dpkg_1.14.16.3.dsc
to pool/main/d/dpkg/dpkg_1.14.16.3.dsc
dpkg_1.14.16.3.tar.gz
to pool/main/d/dpkg/dpkg_1.14.16.3.tar.gz
dpkg_1.14.16.3_i386.deb
to pool/main/d/dpkg/dpkg_1.14.16.3_i386.deb
dselect_1.14.16.3_i386.deb
to pool/main/d/dpkg/dselect_1.14.16.3_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.
Guillem Jover [EMAIL PROTECTED] (supplier of updated dpkg 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, 22 Jan 2008 23:39:59 +0200
Source: dpkg
Binary: dpkg dpkg-dev dselect
Architecture: source i386 all
Version: 1.14.16.3
Distribution: unstable
Urgency: low
Maintainer: Dpkg Developers [EMAIL PROTECTED]
Changed-By: Guillem Jover [EMAIL PROTECTED]
Description:
dpkg - package maintenance system for Debian
dpkg-dev - package building tools for Debian
dselect- user tool to manage Debian packages
Closes: 462072 462075 462079 462089 462098 462104
Changes:
dpkg (1.14.16.3) unstable; urgency=low
.
[ Raphael Hertzog ]
* Remove the :utf8 layer that utf8-encodes already valid utf8.
Closes: #462098
* Disable variable substitution in dpkg-genchanges. Closes: #462079, #462089
.
[ Guillem Jover ]
* Make start-stop-daemon set the supplementary groups if the real user or
group are different than the ones we should switch to. Closes: #462075
* Fix segfault in start-stop-daemon when using --group w/o --chuid (as
a side effect, using --group alone works for the first time in years).
Closes: #462072
* Fix timeout computations for start-stop-daemon --retry option. This has
not worked properly for a long time (maybe never), but came to light
due to #460903's fix. Closes: #462104
Files:
Processed: Re: Bug#462160: Get error message Starting ipw3945 regulatory daemon: ipw3945d failed!
Processing commands for [EMAIL PROTECTED]: reassign 462160 dpkg 1.14.16.1 Bug#462160: Get error message Starting ipw3945 regulatory daemon: ipw3945d failed! Bug reassigned from package `ipw3945d' to `dpkg'. forcemerge 462018 462160 Bug#462018: start-stop-daemon: Unable to set initgroups() with gid 13 (Operation not permitted) Bug#462160: Get error message Starting ipw3945 regulatory daemon: ipw3945d failed! Bug#462110: tor: Fails to install because fails to start because calls initgroups() after setuid() Bug#462111: tor: fails to start: Unable to set initgroups() with gid 125 Bug#462119: /etc/cron.daily/exim4-base error Bug#462141: mldonkey-server: init script fails in initgroups() Forcibly Merged 462018 462110 462111 462119 462141 462160. kthxbye 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#462165: dpkg: Upgrade from 1.13.23-1.14.5 to 1.14.16 onwards is broken
Package: dpkg Version: 1.14.5 Severity: normal dpkg version 1.13.23 introduces the new Breaks header, and rejects it, with the full implementation coming in 1.14.6. The package for 1.14.16 has a Breaks header. Therefore, anyone who is upgrading from any version between 1.13.23 and 1.14.5 inclusive to 1.14.16 onwards (as is now the only option in unstable) will be met with the error message: dpkg: regarding .../dpkg_1.14.16.1_amd64.deb containing dpkg: package uses Breaks; not supported in this dpkg dpkg: error processing /var/cache/apt/archives/dpkg_1.14.16.1_amd64.deb (--unpack): unsupported dependency problem - not installing dpkg A chicken and egg situation. Solving the problem involves either hunting down an intermediate version or forcing an install against dpkg's better judgement, using --force-depends, as specified in the diff in bug #375703. -- System Information: Debian Release: lenny/sid APT prefers unstable APT policy: (500, 'unstable') Architecture: amd64 (x86_64) Kernel: Linux 2.6.21-1-amd64 (SMP w/2 CPU cores) Locale: LANG=en_GB, LC_CTYPE=en_GB (charmap=ISO-8859-1) Shell: /bin/sh linked to /bin/bash Versions of packages dpkg depends on: ii coreutils 5.97-5.7 The GNU core utilities ii libc6 2.7-6 GNU C Library: Shared libraries dpkg recommends no packages. -- no debconf information -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Processed: Re: Bug#462166: Installation fail. And fail dpkg command.
Processing commands for [EMAIL PROTECTED]: reassign 462166 dpkg 1.14.16.1 Bug#462166: Installation fail. And fail dpkg command. Bug reassigned from package `tor' to `dpkg'. forcemerge 462018 462166 Bug#462018: start-stop-daemon: Unable to set initgroups() with gid 13 (Operation not permitted) Bug#462166: Installation fail. And fail dpkg command. Bug#462110: tor: Fails to install because fails to start because calls initgroups() after setuid() Bug#462111: tor: fails to start: Unable to set initgroups() with gid 125 Bug#462119: /etc/cron.daily/exim4-base error Bug#462141: mldonkey-server: init script fails in initgroups() Bug#462160: Get error message Starting ipw3945 regulatory daemon: ipw3945d failed! Forcibly Merged 462018 462110 462111 462119 462141 462160 462166. 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#462172: marked as done (dpkg-dev: Undefined subroutine Dpkg::Cdata::capit called at /usr/share/perl5/Dpkg/Cdata.pm)
Your message dated Wed, 23 Jan 2008 07:02:03 + with message-id [EMAIL PROTECTED] and subject line Bug#462172: fixed in dpkg 1.14.16.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) ---BeginMessage--- Package: dpkg-dev Version: 1.14.15 Severity: normal Hi, recent versions of dpkg-dev cause failures with dpkg-buildpackage. With 1.14.15 it works fine. Here is a failed run with 1.14.16.1 and a successful run with 1.14.15: $ dpkg-buildpackage -rfakeroot -S -I.svn dpkg-buildpackage: source package mythtv dpkg-buildpackage: source version 0.21~trunk15543 dpkg-buildpackage: source changed by Tino Keitel [EMAIL PROTECTED] fakeroot debian/rules clean dh_testdir dh_testroot debconf-updatepo rm -f build-stamp configure-stamp [ ! -f Makefile ] || /usr/bin/make distclean find . -name '.qmake*' | xargs --no-run-if-empty rm -f rm -f config.mak config.h rm -rf debian/shlibs.local debian/rules unpatch make[1]: Entering directory `/home/scorpion/src/myth/pbuilder/src/mythtv-svn' dpatch deapply-all 50_skip_intel_textured_video not applied to ./ . 13_interlaced_fresh_rate not applied to ./ . 11_idle_countdown_reset-fix not applied to ./ . 09_perl_bindings_prefix not applied to ./ . 02_settings.pro not applied to ./ . rm -rf patch-stamp patch-stampT debian/patched make[1]: Leaving directory `/home/scorpion/src/myth/pbuilder/src/mythtv-svn' dh_clean Makefile config.log setup/Makefile programs/mythbackend/version.cpp \ programs/mythfrontend/version.cpp dpkg-source -I.svn -b mythtv-svn Undefined subroutine Dpkg::Cdata::capit called at /usr/share/perl5/Dpkg/Cdata.pm line 78, CDATA line 93. dpkg-buildpackage: failure: dpkg-source -I.svn -b mythtv-svn gave error exit /status 9 $ sudo dpkg -i ../dpkg-dev_1.14.15_all.deb dpkg - warning: downgrading dpkg-dev from 1.14.16.2 to 1.14.15. (Reading database ... 123886 files and directories currently installed.) Preparing to replace dpkg-dev 1.14.16.2 (using .../dpkg/dpkg-dev_1.14.15_all.deb) ... Unpacking replacement dpkg-dev ... Setting up dpkg-dev (1.14.15) ... $ $ dpkg-buildpackage -rfakeroot -S -I.svn dpkg-buildpackage: source package mythtv dpkg-buildpackage: source version 0.21~trunk15543 dpkg-buildpackage: source changed by Tino Keitel [EMAIL PROTECTED] fakeroot debian/rules clean dh_testdir dh_testroot debconf-updatepo rm -f build-stamp configure-stamp [ ! -f Makefile ] || /usr/bin/make distclean find . -name '.qmake*' | xargs --no-run-if-empty rm -f rm -f config.mak config.h rm -rf debian/shlibs.local debian/rules unpatch make[1]: Entering directory `/home/scorpion/src/myth/pbuilder/src/mythtv-svn' dpatch deapply-all 50_skip_intel_textured_video not applied to ./ . 13_interlaced_fresh_rate not applied to ./ . 11_idle_countdown_reset-fix not applied to ./ . 09_perl_bindings_prefix not applied to ./ . 02_settings.pro not applied to ./ . rm -rf patch-stamp patch-stampT debian/patched make[1]: Leaving directory `/home/scorpion/src/myth/pbuilder/src/mythtv-svn' dh_clean Makefile config.log setup/Makefile programs/mythbackend/version.cpp \ programs/mythfrontend/version.cpp dpkg-source -I.svn -b mythtv-svn dpkg-source: warning: source directory './mythtv-svn' is not sourcepackage-upstreamversion 'mythtv-0.21~trunk15543' dpkg-source: building mythtv in mythtv_0.21~trunk15543.tar.gz dpkg-source: building mythtv in mythtv_0.21~trunk15543.dsc signfile mythtv_0.21~trunk15543.dsc gpg: skipped Tino Keitel [EMAIL PROTECTED]: secret key not available gpg: [stdin]: clearsign failed: secret key not available dpkg-genchanges -S ../mythtv_0.21~trunk15543_source.changes dpkg-genchanges: including full source code in upload dpkg-buildpackage: source only upload: Debian-native package dpkg-buildpackage: warning: Failed to sign .dsc and .changes file $ I also tried 1.14.16.2, but the error was still there. Regards, Tino -- System Information: Debian Release: lenny/sid APT prefers unstable APT policy: (500, 'unstable'), (1, 'experimental') Architecture: i386 (i686) Kernel: Linux 2.6.24-rc8 (SMP w/2 CPU cores) Locale: LANG=C, LC_CTYPE=de_DE.UTF-8 (charmap=UTF-8) Shell: /bin/sh linked to /bin/bash Versions of packages dpkg-dev depends on: ii binutils2.18.1~cvs20080103-1 The GNU assembler, linker and bina ii bzip2 1.0.4-2 high-quality block-sorting file co ii cpio2.9-9GNU cpio -- a program to manage ar ii dpkg1.14.16.2package maintenance system for Deb ii lzma4.43-12 Compression
Bug#462165: marked as done (dpkg: Upgrade from 1.13.23-1.14.5 to 1.14.16 onwards is broken)
Your message dated Wed, 23 Jan 2008 08:54:05 +0200 with message-id [EMAIL PROTECTED] and subject line Bug#462165: dpkg: Upgrade from 1.13.23-1.14.5 to 1.14.16 onwards is broken 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) ---BeginMessage--- Package: dpkg Version: 1.14.5 Severity: normal dpkg version 1.13.23 introduces the new Breaks header, and rejects it, with the full implementation coming in 1.14.6. The package for 1.14.16 has a Breaks header. Therefore, anyone who is upgrading from any version between 1.13.23 and 1.14.5 inclusive to 1.14.16 onwards (as is now the only option in unstable) will be met with the error message: dpkg: regarding .../dpkg_1.14.16.1_amd64.deb containing dpkg: package uses Breaks; not supported in this dpkg dpkg: error processing /var/cache/apt/archives/dpkg_1.14.16.1_amd64.deb (--unpack): unsupported dependency problem - not installing dpkg A chicken and egg situation. Solving the problem involves either hunting down an intermediate version or forcing an install against dpkg's better judgement, using --force-depends, as specified in the diff in bug #375703. -- System Information: Debian Release: lenny/sid APT prefers unstable APT policy: (500, 'unstable') Architecture: amd64 (x86_64) Kernel: Linux 2.6.21-1-amd64 (SMP w/2 CPU cores) Locale: LANG=en_GB, LC_CTYPE=en_GB (charmap=ISO-8859-1) Shell: /bin/sh linked to /bin/bash Versions of packages dpkg depends on: ii coreutils 5.97-5.7 The GNU core utilities ii libc6 2.7-6 GNU C Library: Shared libraries dpkg recommends no packages. -- no debconf information ---End Message--- ---BeginMessage--- Version: 1.14.16.2 On Tue, 2008-01-22 at 23:05:55 +, Matthew Wakeling wrote: Package: dpkg Version: 1.14.5 Severity: normal dpkg version 1.13.23 introduces the new Breaks header, and rejects it, with the full implementation coming in 1.14.6. The package for 1.14.16 has a Breaks header. Therefore, anyone who is upgrading from any version between 1.13.23 and 1.14.5 inclusive to 1.14.16 onwards (as is now the only option in unstable) will be met with the error message: dpkg: regarding .../dpkg_1.14.16.1_amd64.deb containing dpkg: package uses Breaks; not supported in this dpkg dpkg: error processing /var/cache/apt/archives/dpkg_1.14.16.1_amd64.deb (--unpack): unsupported dependency problem - not installing dpkg A chicken and egg situation. Solving the problem involves either hunting down an intermediate version or forcing an install against dpkg's better judgement, using --force-depends, as specified in the diff in bug #375703. Yes, this was fixed in dpkg 1.14.16.2, please upgrade to that version. Closing. thanks, guillem ---End Message---
Bug#456332: dpkg could use an elevated pre-depends or depends on lzma
On Tue, 22 Jan 2008, Ian Jackson wrote: Raphael Hertzog writes (Bug#456332: dpkg could use an elevated pre-depends or depends on lzma): On Tue, 18 Dec 2007, Ian Jackson wrote: IMO the lzma binary package should Provide a new virtual package name, lzma-deb-support or some such. Packages could Pre-Depend on that. What does it bring? I assume you mean why do it like that. The answer is that you don't need the lzma support in cases where it's not needed. The dependencies are more accurate. You don't need a virtual package for that. You just need to have each package depend on the right decompressor. I would only be in favor of that if we modify dpkg to auto-generate that dependency, unfortunately right now we only know how to compress when dpkg-deb -b -Zsomething is called and this is after dpkg-gencontrol obviously. Cheers, -- Raphaël Hertzog Le best-seller français mis à jour pour Debian Etch : http://www.ouaza.com/livre/admin-debian/
