Bug#770004: dpkg-maintscript-helper: dir_to_symlink fails when upgrading package that has gone from arch:any to arch:all
Ok, I probably read some other commit. This looks good. Thanks, Ondrej On Wed, Mar 4, 2015, at 10:08, Guillem Jover wrote: Hi! On Thu, 2015-02-26 at 19:07:46 +0100, Ondřej Surý wrote: On Sat, Feb 21, 2015, at 16:51, Guillem Jover wrote: I think the other merged bug, already fixed in git should cover this problem, by improving the documentation. Let me know if it does not. https://anonscm.debian.org/cgit/dpkg/dpkg.git/commit/?id=9d70c7a6582b2d I still think you should explicitly mention the cases when switching from arch:all to arch:any or vice versa and what to do and what not. As I am not so well versed in dpkg internals the commit you mentioned doesn't make it very clear for me. This is the change: ,--- +The package name. When the package is Multi-Arch: same this parameter +must include the architecture qualifier, otherwise it should \fBnot\fP +usually include the architecture qualifier (as it would disallow +cross-grades, or switching from being architecture specific to +architecture \fBall\fP or vice versa). +If the parameter is empty or omitted, the \fBDPKG_MAINTSCRIPT_PACKAGE\fP +and \fBDPKG_MAINTSCRIPT_ARCH\fP environment variables (as set by \fBdpkg\fP) +will be used to generate an arch-qualified package name. `--- Here, I'm actually mentioning the arch:all ←→ arch:any case explicitly, and it seems to be clear to me, so it would be helpful if you could point out where the wording is not clear or what can be improved to make it so? Thanks, Guillem -- Ondřej Surý ond...@sury.org Knot DNS (https://www.knot-dns.cz/) – a high-performance DNS server -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#770004: dpkg-maintscript-helper: dir_to_symlink fails when upgrading package that has gone from arch:any to arch:all
Hi! On Thu, 2015-02-26 at 19:07:46 +0100, Ondřej Surý wrote: On Sat, Feb 21, 2015, at 16:51, Guillem Jover wrote: I think the other merged bug, already fixed in git should cover this problem, by improving the documentation. Let me know if it does not. https://anonscm.debian.org/cgit/dpkg/dpkg.git/commit/?id=9d70c7a6582b2d I still think you should explicitly mention the cases when switching from arch:all to arch:any or vice versa and what to do and what not. As I am not so well versed in dpkg internals the commit you mentioned doesn't make it very clear for me. This is the change: ,--- +The package name. When the package is Multi-Arch: same this parameter +must include the architecture qualifier, otherwise it should \fBnot\fP +usually include the architecture qualifier (as it would disallow +cross-grades, or switching from being architecture specific to +architecture \fBall\fP or vice versa). +If the parameter is empty or omitted, the \fBDPKG_MAINTSCRIPT_PACKAGE\fP +and \fBDPKG_MAINTSCRIPT_ARCH\fP environment variables (as set by \fBdpkg\fP) +will be used to generate an arch-qualified package name. `--- Here, I'm actually mentioning the arch:all ←→ arch:any case explicitly, and it seems to be clear to me, so it would be helpful if you could point out where the wording is not clear or what can be improved to make it so? Thanks, Guillem -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#770004: dpkg-maintscript-helper: dir_to_symlink fails when upgrading package that has gone from arch:any to arch:all
Guillem, I still think you should explicitly mention the cases when switching from arch:all to arch:any or vice versa and what to do and what not. As I am not so well versed in dpkg internals the commit you mentioned doesn't make it very clear for me. O. On Sat, Feb 21, 2015, at 16:51, Guillem Jover wrote: Control: forcemerge 776072 -1 Hi! On Thu, 2014-11-20 at 06:08:29 +0100, Guillem Jover wrote: On Tue, 2014-11-18 at 14:30:09 +0100, Ondřej Surý wrote: Control: severity -1 wishlist Control: reassign -1 dpkg Thus filling this as a wishlist... feel free to mark it as wontfix or just document that it won't be supported never ever - both are fine with me, but of course if you can come up with some solution that would allow this to work without jumping through the hoops, it would be much preferred. I'll think about this, but take into account that dpkg-maintscript-helper has always been just a hack to cover deficiencies in dpkg itself, and a proper integrated solution should be developed instead. If a solution for this does not interfere much or does not make other things ugly I might add it, otherwise I'd rather come up with a proper replacement for the helper. But, I might end up just closing it, see below… I think the other merged bug, already fixed in git should cover this problem, by improving the documentation. Let me know if it does not. https://anonscm.debian.org/cgit/dpkg/dpkg.git/commit/?id=9d70c7a6582b2d On Tue, Nov 18, 2014, at 13:08, Ondřej Surý wrote: On Tue, Nov 18, 2014, at 12:24, Guillem Jover wrote: dpkg-maintscript-helper only does what it is told. In this case the packaging has not specified a package name (with the required arch-qualifier) to the dpkg-maintscript-helper call, so it cannot infer that you are doing an arch switch. Please read the man page for the command for more details. The manpage doesn't say anything about upgrades from arch:any to arch:all, just about Multi-Arch? Hmm, true, it's all very implicit. I'm fixing the package argument description for 1.18.x to make all this more clear. It should now. Thanks, Guillem -- Ondřej Surý ond...@sury.org Knot DNS (https://www.knot-dns.cz/) – a high-performance DNS server -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#770004: dpkg-maintscript-helper: dir_to_symlink fails when upgrading package that has gone from arch:any to arch:all
Control: forcemerge 776072 -1 Hi! On Thu, 2014-11-20 at 06:08:29 +0100, Guillem Jover wrote: On Tue, 2014-11-18 at 14:30:09 +0100, Ondřej Surý wrote: Control: severity -1 wishlist Control: reassign -1 dpkg Thus filling this as a wishlist... feel free to mark it as wontfix or just document that it won't be supported never ever - both are fine with me, but of course if you can come up with some solution that would allow this to work without jumping through the hoops, it would be much preferred. I'll think about this, but take into account that dpkg-maintscript-helper has always been just a hack to cover deficiencies in dpkg itself, and a proper integrated solution should be developed instead. If a solution for this does not interfere much or does not make other things ugly I might add it, otherwise I'd rather come up with a proper replacement for the helper. But, I might end up just closing it, see below… I think the other merged bug, already fixed in git should cover this problem, by improving the documentation. Let me know if it does not. https://anonscm.debian.org/cgit/dpkg/dpkg.git/commit/?id=9d70c7a6582b2d On Tue, Nov 18, 2014, at 13:08, Ondřej Surý wrote: On Tue, Nov 18, 2014, at 12:24, Guillem Jover wrote: dpkg-maintscript-helper only does what it is told. In this case the packaging has not specified a package name (with the required arch-qualifier) to the dpkg-maintscript-helper call, so it cannot infer that you are doing an arch switch. Please read the man page for the command for more details. The manpage doesn't say anything about upgrades from arch:any to arch:all, just about Multi-Arch? Hmm, true, it's all very implicit. I'm fixing the package argument description for 1.18.x to make all this more clear. It should now. Thanks, Guillem -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#770004: dpkg-maintscript-helper: dir_to_symlink fails when upgrading package that has gone from arch:any to arch:all
Hi! On Tue, 2014-11-18 at 14:30:09 +0100, Ondřej Surý wrote: Control: severity -1 wishlist Control: reassign -1 dpkg as discussed with helmut on IRC, I am reassigning back to dpkg with severity wishlist. No problem. dpkg-maintscript-helper (and dpkg) know the arch of previous package, so it could support this scenario (and the reverse one). dpkg-maintscript-helper does not have enough information for this, as dpkg only passes the architecture of the package instance currently being acted on, be that the new or the old. Thus filling this as a wishlist... feel free to mark it as wontfix or just document that it won't be supported never ever - both are fine with me, but of course if you can come up with some solution that would allow this to work without jumping through the hoops, it would be much preferred. I'll think about this, but take into account that dpkg-maintscript-helper has always been just a hack to cover deficiencies in dpkg itself, and a proper integrated solution should be developed instead. If a solution for this does not interfere much or does not make other things ugly I might add it, otherwise I'd rather come up with a proper replacement for the helper. But, I might end up just closing it, see below… On Tue, Nov 18, 2014, at 13:08, Ondřej Surý wrote: On Tue, Nov 18, 2014, at 12:24, Guillem Jover wrote: On Tue, 2014-11-18 at 08:20:36 +0100, Ondřej Surý wrote: Package: dpkg Version: 1.17.21 Severity: grave File: /usr/bin/dpkg-maintscript-helper (BTW, if this had been an issue in dpkg, then it would not have been grave, as it would not break unrelated software, just the one currently being acted on.) JFTR I have discussed this with Helmut Grohne on #-devel before filling the bug. I only meant that this would at most be serious not grave. :) dpkg-maintscript-helper only does what it is told. In this case the packaging has not specified a package name (with the required arch-qualifier) to the dpkg-maintscript-helper call, so it cannot infer that you are doing an arch switch. Please read the man page for the command for more details. The manpage doesn't say anything about upgrades from arch:any to arch:all, just about Multi-Arch? Hmm, true, it's all very implicit. I'm fixing the package argument description for 1.18.x to make all this more clear. What I've not checked is if debhelper can pass different arguments depending on the maintainer script invoked, which _might_ be required here, but I've not thought about it. Because then you'd probably need to call dpkg-maintscript-helper manually. The problem here is more complex - which arch should I pick in the call? E.g. should I pass f.e. libcyrus-imap-perl24:$(dpkg --print-architecture) to the dpkg-maintscript-helper call? «dpkg --print-architecture» is never the right answer when dealing with binary package architectures. After having checked the code, in this case just passing the arch-unqualified package name should be enough. Would that work for M-A packages? No, in that case you'd need to arch-qualify them, but you'd have the additional problem of switching from possibly multiple M-A:same instances to a single M-A:no arch:all instance, which ISTR apt does not handle too well? In any case, definitely a bug in the packaging, and as such reassigning. I can definitely fix that in the packaging, but it's going to be a horrible hack :(. I think it's just way simpler than what it seemed, before having checked. :) Thanks, Guillem -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#770004: dpkg-maintscript-helper: dir_to_symlink fails when upgrading package that has gone from arch:any to arch:all
Control: reassign -1 cyrus-imapd-2.4 Control: retitle -1 cyrus-imapd-2.4: Insuficient arguments passed to dpkg-maintscript-helper Control: severity -1 serious On Tue, 2014-11-18 at 08:20:36 +0100, Ondřej Surý wrote: Package: dpkg Version: 1.17.21 Severity: grave File: /usr/bin/dpkg-maintscript-helper (BTW, if this had been an issue in dpkg, then it would not have been grave, as it would not break unrelated software, just the one currently being acted on.) dpkg-maintscript-helper fails to find the package files when using dir_to_symlink (and probably vice versa) and upgrading from arch:any to arch:all at the same time. dpkg-maintscript-helper only does what it is told. In this case the packaging has not specified a package name (with the required arch-qualifier) to the dpkg-maintscript-helper call, so it cannot infer that you are doing an arch switch. Please read the man page for the command for more details. The bug manifests in libcyrus-imap-perl24 upgrade from wheezy to jessie (filled as #769553): Preparing to unpack .../libcyrus-imap-perl24_2.4.17+caldav~beta10-7_all.deb ... dpkg-query: no packages found matching libcyrus-imap-perl24:all […] But I can reproduce this with any transitional package from src:cyrus-imapd-2.4 (anything with -2.4 suffix except cyrus-common-2.4), f.e.: Preparing to unpack .../cyrus-clients-2.4_2.4.17+caldav~beta10-7_all.deb ... dpkg-query: no packages found matching cyrus-clients-2.4:all […] ,--- $ grep . debian/*.maintscript debian/cyrus-admin-2.4.maintscript:dir_to_symlink /usr/share/doc/cyrus-admin-2.4 /usr/share/doc/cyrus-common-2.4 2.4.17+caldav~beta10-7~ debian/cyrus-admin.maintscript:symlink_to_dir /usr/share/doc/cyrus-admin /usr/share/doc/cyrus-common-2.4 2.4.17+caldav~beta10-3~ debian/cyrus-caldav-2.4.maintscript:dir_to_symlink /usr/share/doc/cyrus-caldav-2.4 /usr/share/doc/cyrus-common-2.4 2.4.17+caldav~beta10-7~ debian/cyrus-clients-2.4.maintscript:dir_to_symlink /usr/share/doc/cyrus-clients-2.4 /usr/share/doc/cyrus-common-2.4 2.4.17+caldav~beta10-7~ debian/cyrus-clients.maintscript:symlink_to_dir /usr/share/doc/cyrus-clients /usr/share/doc/cyrus-common-2.4 2.4.17+caldav~beta10-3~ debian/cyrus-common.maintscript:mv_conffile /etc/logcheck/violations.ignore.d/cyrus-common-2_4 /etc/logcheck/violations.ignore.d/cyrus-common 2.4.17+caldav~beta10-3~ debian/cyrus-dev-2.4.maintscript:dir_to_symlink /usr/share/doc/cyrus-dev-2.4 /usr/share/doc/cyrus-common-2.4 2.4.17+caldav~beta10-7~ debian/cyrus-doc-2.4.maintscript:dir_to_symlink /usr/share/doc/cyrus-doc-2.4 /usr/share/doc/cyrus-common-2.4 2.4.17+caldav~beta10-7~ debian/cyrus-imapd-2.4.maintscript:dir_to_symlink /usr/share/doc/cyrus-imapd-2.4 /usr/share/doc/cyrus-common-2.4 2.4.17+caldav~beta10-7~ debian/cyrus-murder-2.4.maintscript:dir_to_symlink /usr/share/doc/cyrus-murder-2.4 /usr/share/doc/cyrus-common-2.4 2.4.17+caldav~beta10-7~ debian/cyrus-nntpd-2.4.maintscript:dir_to_symlink /usr/share/doc/cyrus-nntpd-2.4 /usr/share/doc/cyrus-common-2.4 2.4.17+caldav~beta10-7~ debian/cyrus-pop3d-2.4.maintscript:dir_to_symlink /usr/share/doc/cyrus-pop3d-2.4 /usr/share/doc/cyrus-common-2.4 2.4.17+caldav~beta10-7~ debian/cyrus-replication-2.4.maintscript:dir_to_symlink /usr/share/doc/cyrus-replication-2.4 /usr/share/doc/cyrus-common-2.4 2.4.17+caldav~beta10-7~ debian/libcyrus-imap-perl.maintscript:symlink_to_dir /usr/share/doc/libcyrus-imap-perl /usr/share/doc/cyrus-common-2.4 2.4.17+caldav~beta10-3~ debian/libcyrus-imap-perl24.maintscript:dir_to_symlink /usr/share/doc/libcyrus-imap-perl24 /usr/share/doc/cyrus-common-2.4 2.4.17+caldav~beta10-7~ `--- What I've not checked is if debhelper can pass different arguments depending on the maintainer script invoked, which _might_ be required here, but I've not thought about it. Because then you'd probably need to call dpkg-maintscript-helper manually. In any case, definitely a bug in the packaging, and as such reassigning. Thanks, Guillem -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#770004: dpkg-maintscript-helper: dir_to_symlink fails when upgrading package that has gone from arch:any to arch:all
Hi Guillem, thanks for getting back so quickly. On Tue, Nov 18, 2014, at 12:24, Guillem Jover wrote: Control: reassign -1 cyrus-imapd-2.4 Control: retitle -1 cyrus-imapd-2.4: Insuficient arguments passed to dpkg-maintscript-helper Control: severity -1 serious On Tue, 2014-11-18 at 08:20:36 +0100, Ondřej Surý wrote: Package: dpkg Version: 1.17.21 Severity: grave File: /usr/bin/dpkg-maintscript-helper (BTW, if this had been an issue in dpkg, then it would not have been grave, as it would not break unrelated software, just the one currently being acted on.) JFTR I have discussed this with Helmut Grohne on #-devel before filling the bug. dpkg-maintscript-helper fails to find the package files when using dir_to_symlink (and probably vice versa) and upgrading from arch:any to arch:all at the same time. dpkg-maintscript-helper only does what it is told. In this case the packaging has not specified a package name (with the required arch-qualifier) to the dpkg-maintscript-helper call, so it cannot infer that you are doing an arch switch. Please read the man page for the command for more details. The manpage doesn't say anything about upgrades from arch:any to arch:all, just about Multi-Arch? What I've not checked is if debhelper can pass different arguments depending on the maintainer script invoked, which _might_ be required here, but I've not thought about it. Because then you'd probably need to call dpkg-maintscript-helper manually. The problem here is more complex - which arch should I pick in the call? E.g. should I pass f.e. libcyrus-imap-perl24:$(dpkg --print-architecture) to the dpkg-maintscript-helper call? Would that work for M-A packages? In any case, definitely a bug in the packaging, and as such reassigning. I can definitely fix that in the packaging, but it's going to be a horrible hack :(. (Personally I think we should have just fixed dh_installdoc --link-doc...) Cheers, -- Ondřej Surý ond...@sury.org Knot DNS (https://www.knot-dns.cz/) – a high-performance DNS server -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#770004: dpkg-maintscript-helper: dir_to_symlink fails when upgrading package that has gone from arch:any to arch:all
Control: severity -1 wishlist Control: reassign -1 dpkg Hi Guillem, as discussed with helmut on IRC, I am reassigning back to dpkg with severity wishlist. dpkg-maintscript-helper (and dpkg) know the arch of previous package, so it could support this scenario (and the reverse one). Thus filling this as a wishlist... feel free to mark it as wontfix or just document that it won't be supported never ever - both are fine with me, but of course if you can come up with some solution that would allow this to work without jumping through the hoops, it would be much preferred. Cheers, Ondrej On Tue, Nov 18, 2014, at 13:08, Ondřej Surý wrote: Hi Guillem, thanks for getting back so quickly. On Tue, Nov 18, 2014, at 12:24, Guillem Jover wrote: Control: reassign -1 cyrus-imapd-2.4 Control: retitle -1 cyrus-imapd-2.4: Insuficient arguments passed to dpkg-maintscript-helper Control: severity -1 serious On Tue, 2014-11-18 at 08:20:36 +0100, Ondřej Surý wrote: Package: dpkg Version: 1.17.21 Severity: grave File: /usr/bin/dpkg-maintscript-helper (BTW, if this had been an issue in dpkg, then it would not have been grave, as it would not break unrelated software, just the one currently being acted on.) JFTR I have discussed this with Helmut Grohne on #-devel before filling the bug. dpkg-maintscript-helper fails to find the package files when using dir_to_symlink (and probably vice versa) and upgrading from arch:any to arch:all at the same time. dpkg-maintscript-helper only does what it is told. In this case the packaging has not specified a package name (with the required arch-qualifier) to the dpkg-maintscript-helper call, so it cannot infer that you are doing an arch switch. Please read the man page for the command for more details. The manpage doesn't say anything about upgrades from arch:any to arch:all, just about Multi-Arch? What I've not checked is if debhelper can pass different arguments depending on the maintainer script invoked, which _might_ be required here, but I've not thought about it. Because then you'd probably need to call dpkg-maintscript-helper manually. The problem here is more complex - which arch should I pick in the call? E.g. should I pass f.e. libcyrus-imap-perl24:$(dpkg --print-architecture) to the dpkg-maintscript-helper call? Would that work for M-A packages? In any case, definitely a bug in the packaging, and as such reassigning. I can definitely fix that in the packaging, but it's going to be a horrible hack :(. (Personally I think we should have just fixed dh_installdoc --link-doc...) Cheers, -- Ondřej Surý ond...@sury.org Knot DNS (https://www.knot-dns.cz/) – a high-performance DNS server ___ Pkg-Cyrus-imapd-Debian-devel mailing list pkg-cyrus-imapd-debian-de...@lists.alioth.debian.org http://lists.alioth.debian.org/cgi-bin/mailman/listinfo/pkg-cyrus-imapd-debian-devel -- Ondřej Surý ond...@sury.org Knot DNS (https://www.knot-dns.cz/) – a high-performance DNS server -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#770004: dpkg-maintscript-helper: dir_to_symlink fails when upgrading package that has gone from arch:any to arch:all
Package: dpkg Version: 1.17.21 Severity: grave File: /usr/bin/dpkg-maintscript-helper Hi, dpkg-maintscript-helper fails to find the package files when using dir_to_symlink (and probably vice versa) and upgrading from arch:any to arch:all at the same time. The bug manifests in libcyrus-imap-perl24 upgrade from wheezy to jessie (filled as #769553): Preparing to unpack .../libcyrus-imap-perl24_2.4.17+caldav~beta10-7_all.deb ... dpkg-query: no packages found matching libcyrus-imap-perl24:all dpkg-query: package 'libcyrus-imap-perl24' is not installed Use dpkg --info (= dpkg-deb --info) to examine archive files, and dpkg --contents (= dpkg-deb --contents) to list their contents. dpkg-query: package 'libcyrus-imap-perl24' is not installed Use dpkg --info (= dpkg-deb --info) to examine archive files, and dpkg --contents (= dpkg-deb --contents) to list their contents. dpkg-query: package 'libcyrus-imap-perl24' is not installed Use dpkg --info (= dpkg-deb --info) to examine archive files, and dpkg --contents (= dpkg-deb --contents) to list their contents. dpkg-query: package 'libcyrus-imap-perl24' is not installed Use dpkg --info (= dpkg-deb --info) to examine archive files, and dpkg --contents (= dpkg-deb --contents) to list their contents. dpkg-maintscript-helper: error: directory '/usr/share/doc/libcyrus-imap-perl24' contains files not owned by package libcyrus-imap-perl24:all, cannot switch to symlink dpkg: error processing archive /var/cache/apt/archives/libcyrus-imap-perl24_2.4.17+caldav~beta10-7_all.deb (--unpack): subprocess new pre-installation script returned error exit status 1 But I can reproduce this with any transitional package from src:cyrus-imapd-2.4 (anything with -2.4 suffix except cyrus-common-2.4), f.e.: Preparing to unpack .../cyrus-clients-2.4_2.4.17+caldav~beta10-7_all.deb ... dpkg-query: no packages found matching cyrus-clients-2.4:all dpkg-query: package 'cyrus-clients-2.4' is not installed Use dpkg --info (= dpkg-deb --info) to examine archive files, and dpkg --contents (= dpkg-deb --contents) to list their contents. dpkg-query: package 'cyrus-clients-2.4' is not installed Use dpkg --info (= dpkg-deb --info) to examine archive files, and dpkg --contents (= dpkg-deb --contents) to list their contents. dpkg-query: package 'cyrus-clients-2.4' is not installed Use dpkg --info (= dpkg-deb --info) to examine archive files, and dpkg --contents (= dpkg-deb --contents) to list their contents. dpkg-query: package 'cyrus-clients-2.4' is not installed Use dpkg --info (= dpkg-deb --info) to examine archive files, and dpkg --contents (= dpkg-deb --contents) to list their contents. dpkg-query: package 'cyrus-clients-2.4' is not installed Use dpkg --info (= dpkg-deb --info) to examine archive files, and dpkg --contents (= dpkg-deb --contents) to list their contents. dpkg-query: package 'cyrus-clients-2.4' is not installed Use dpkg --info (= dpkg-deb --info) to examine archive files, and dpkg --contents (= dpkg-deb --contents) to list their contents. dpkg-maintscript-helper: error: directory '/usr/share/doc/cyrus-clients-2.4' contains files not owned by package cyrus-clients-2.4:all, cannot switch to symlink dpkg: error processing archive /var/cache/apt/archives/cyrus-clients-2.4_2.4.17+caldav~beta10-7_all.deb (--unpack): subprocess new pre-installation script returned error exit status 1 Cheers, Ondrej -- System Information: Debian Release: jessie/sid APT prefers unstable APT policy: (500, 'unstable'), (500, 'testing'), (1, 'experimental') Architecture: amd64 (x86_64) Foreign Architectures: i386 Kernel: Linux 3.16-3-amd64 (SMP w/4 CPU cores) Locale: LANG=en_DK.UTF-8, LC_CTYPE=en_DK.UTF-8 (charmap=UTF-8) Shell: /bin/sh linked to /bin/dash Versions of packages dpkg depends on: ii libbz2-1.0 1.0.6-7 ii libc62.19-12 ii liblzma5 5.1.1alpha+20120614-2 ii libselinux1 2.3-2 ii tar 1.27.1-2 ii zlib1g 1:1.2.8.dfsg-2 dpkg recommends no packages. Versions of packages dpkg suggests: ii apt 1.0.9.3 -- no debconf information -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
