Bug#767999: base-files: fails to install with pre-jessie debootstrap
reassign -1 debootstrap thanks On Tue, Nov 04, 2014 at 01:05:11AM +0100, Adam Borowski wrote: Package: base-files Version: 7.10 Severity: grave W: Failure trying to run: chroot /tmp/unstable/. dpkg --force-depends --install /var/cache/apt/archives/base-files_7.10_i386.deb /var/cache/apt/archives/base-passwd_3.5.36_i386.deb While #766459 fixed debootstrapping with jessie's debootstrap, I'm afraid this doesn't solve most use cases that include upgrading, installation from non-DI or installation in hosting scenarios. For a long time, most versions of debootstrap in use will come from wheezy, Red Hat or some random live-cd. None of those can install jessie :( Thus, I'm afraid that fixing *new* copies of debootstrap is not enough, and this bug needs to be solved in base-files or base-passwd. For the umpteenth time: This is a bug in debootstrap and that's where it should be fixed!!! (And you should really read the full logs for Bug#766459 to understand this instead of killing the messenger one more time, base-files does not do anything which is not allowed by policy). Just ask debootstrap maintainers to make an upload for stable so that the next point release of wheezy has a fix for this. We *need* a new debootstrap in stable. -- To UNSUBSCRIBE, email to debian-bugs-rc-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#765285: removed on failed archs
Waiting upstream fix on aotmic operations, a RM request has been sent to remove binaries from failing archs: #766961: RM: mapsembler2 [mips mipsel powerpc sparc] -- RoM; FTBFS -- gpg key id: 4096R/326D8438 (keyring.debian.org) Key fingerprint = 5FB4 6F83 D3B9 5204 6335 D26D 78DC 68DB 326D 8438
Bug#765285: removed on failed archs
Hi Olivier, On Tue, Nov 04, 2014 at 09:21:47AM +0100, Olivier Sallou wrote: Waiting upstream fix on aotmic operations, a RM request has been sent to remove binaries from failing archs: #766961: RM: mapsembler2 [mips mipsel powerpc sparc] -- RoM; FTBFS What about mapsembler2/amd64 unsatisfiable Depends: libhdf5-7 [1] Looks suspicious to me as well. Kind regards Andreas. [1] https://qa.debian.org/excuses.php?package=mapsembler2 -- http://fam-tille.de -- To UNSUBSCRIBE, email to debian-bugs-rc-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#767616: [Pkg-lyx-devel] Bug#767616: Bug#767616: lyx: fails to upgrade from 'testing' - trying to overwrite /usr/share/icons/hicolor/48x48/apps/lyx.png
Hi Nikos,
2014-11-03 16:19, Nikos Andrikos skrev:
In lyx control file, there is this line:
Depends: ... lyx-common (= ${source:Version}), ...
I thought this is enough to make sure that along lyx 2.1.2-3, the only
installable lyx-common version will be 2.1.2-3 .
No, it is not enough. Depends only ensures that the packages are
configured in the right order, but there can still be different versions
unpacked on the system at the same time. (One can use Pre-Depends to
force packages to be unpacked in some order, but that is discouraged and
needs approval.)
If this is not the case, then we would need to add the breaks/replaces
options as you suggested, but could you please confirm that this is
the proper action?
Yes. You need something like
Package: lyx
...
Replaces: lyx-common ( 2.1.2-3)
Breaks: lyx-common ( 2.1.2-3)
--
Pelle
--
To UNSUBSCRIBE, email to debian-bugs-rc-requ...@lists.debian.org
with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#764162: linux-image-3.16-2-kirkwood: [regression 3.14-3.16] file data corruption, via network
On Fri, 2014-10-31 at 14:29 +0100, Julien D'Ascenzio wrote: Le vendredi 31 octobre 2014 à 09:50 +, Ian Campbell a écrit : On Sun, 2014-10-19 at 14:27 +0100, Ian Campbell wrote: You could inactivate this feature manually with: ethtool -K eth0 tso off I'm in contact with the developer of this feature. Tell me if this command resolve your problem Excellent, please let us know how you get on (feel free to CC the bug too if you want). Did you make any progress with the developer? In the changes to this driver since v3.16 I see commit 817dbfa5d1bc276a72c1a577310382008e8aca0a Author: Vlad Yasevich vyasev...@gmail.com Date: Mon Aug 25 10:34:54 2014 -0400 mvneta: Fix TSO and checksum for non-acceleration vlan traffic which might be potentially interesting, except no one on this bug has mentioned VLANs at any point. I don't see anything else of interest. Ian. I don't have more information. They seems not to understand why there are data corrupt with this soc. The only solution at this time is to inactivate tso or apply this patch, which makes TSO disabled by default: I've now managed to update my qnap box too and can trivially see file corruption over NFS. Unless anyone has any ideas or suggested fixes I'm going to apply this patch to disable TSO by default to the Debian kernel. diff --git a/drivers/net/ethernet/marvell/mv643xx_eth.c b/drivers/net/ethernet/marvell/mv643xx_eth.c index 693b5b5..8e6df75 100644 --- a/drivers/net/ethernet/marvell/mv643xx_eth.c +++ b/drivers/net/ethernet/marvell/mv643xx_eth.c @@ -3113,11 +3113,11 @@ static int mv643xx_eth_probe(struct platform_device *pdev) dev-watchdog_timeo = 2 * HZ; dev-base_addr = 0; - dev-features = NETIF_F_SG | NETIF_F_IP_CSUM | NETIF_F_TSO; + dev-features = NETIF_F_SG | NETIF_F_IP_CSUM; dev-vlan_features = dev-features; dev-features |= NETIF_F_RXCSUM; - dev-hw_features = dev-features; + dev-hw_features = dev-features | NETIF_F_TSO; dev-priv_flags |= IFF_UNICAST_FLT; dev-gso_max_segs = MV643XX_MAX_TSO_SEGS; I CC my contact Julien D'Ascenzio -- To UNSUBSCRIBE, email to debian-bugs-rc-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#767819: bareos-*: modifies conffiles (policy 10.7.3): /etc/bareos/bareos-*.conf
I would upload in my lunch-break if you do not object ;) Certainly. Please go ahead. regards, Jörg -- To UNSUBSCRIBE, email to debian-bugs-rc-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#764162: linux-image-3.16-2-kirkwood: [regression 3.14-3.16] file data corruption, via network
On Tue, 2014-11-04 at 08:51 +, Ian Campbell wrote: On Fri, 2014-10-31 at 14:29 +0100, Julien D'Ascenzio wrote: Le vendredi 31 octobre 2014 à 09:50 +, Ian Campbell a écrit : On Sun, 2014-10-19 at 14:27 +0100, Ian Campbell wrote: You could inactivate this feature manually with: ethtool -K eth0 tso off I'm in contact with the developer of this feature. Tell me if this command resolve your problem Excellent, please let us know how you get on (feel free to CC the bug too if you want). Did you make any progress with the developer? In the changes to this driver since v3.16 I see commit 817dbfa5d1bc276a72c1a577310382008e8aca0a Author: Vlad Yasevich vyasev...@gmail.com Date: Mon Aug 25 10:34:54 2014 -0400 mvneta: Fix TSO and checksum for non-acceleration vlan traffic which might be potentially interesting, except no one on this bug has mentioned VLANs at any point. I don't see anything else of interest. Ian. I don't have more information. They seems not to understand why there are data corrupt with this soc. The only solution at this time is to inactivate tso or apply this patch, which makes TSO disabled by default: I've now managed to update my qnap box too and can trivially see file corruption over NFS. Unless anyone has any ideas or suggested fixes I'm going to apply this patch to disable TSO by default to the Debian kernel. I've just seen https://patchwork.ozlabs.org/patch/405792/ so I'm going to go ahead for now. Ian. -- To UNSUBSCRIBE, email to debian-bugs-rc-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Processed: Debian bug #767837
Processing commands for cont...@bugs.debian.org: fixed 767837 argyll/1.6.3-4 Bug #767837 [argyll] argyll: fails to upgrade from 'wheezy' - trying to overwrite /usr/share/man/man1/icclu.1.gz The source argyll and version 1.6.3-4 do not appear to match any binary packages Marked as fixed in versions argyll/1.6.3-4. -- Stopping processing here. Please contact me if you need assistance. -- 767837: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=767837 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems -- To UNSUBSCRIBE, email to debian-bugs-rc-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#767999: base-files: fails to install with pre-jessie debootstrap
reassign 767999 debootstrap thanks People who do not understand the essential flag keep filing bugs against base-files. Kind debootstrap maintainers: I think it's about time that you make an upload for stable fixing this. I've heard that the fix is already in git, so apparently it's just a matter of making the upload. Please. -- To UNSUBSCRIBE, email to debian-bugs-rc-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Processed: Re: Bug#767999: base-files: fails to install with pre-jessie debootstrap
Processing commands for cont...@bugs.debian.org: reassign 767999 debootstrap Bug #767999 [base-files] base-files: fails to install with pre-jessie debootstrap Bug reassigned from package 'base-files' to 'debootstrap'. No longer marked as found in versions base-files/7.10. Ignoring request to alter fixed versions of bug #767999 to the same values previously set thanks Stopping processing here. Please contact me if you need assistance. -- 767999: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=767999 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems -- To UNSUBSCRIBE, email to debian-bugs-rc-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#767646: marked as done (miniupnpd: modifies conffiles (policy 10.7.3): /etc/miniupnpd/miniupnpd.conf)
Your message dated Tue, 04 Nov 2014 09:20:39 + with message-id e1xlai3-um...@franck.debian.org and subject line Bug#767646: fixed in miniupnpd 1.8.20140523-3 has caused the Debian Bug report #767646, regarding miniupnpd: modifies conffiles (policy 10.7.3): /etc/miniupnpd/miniupnpd.conf 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 this message is talking about, this may indicate a serious mail system misconfiguration somewhere. Please contact ow...@bugs.debian.org immediately.) -- 767646: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=767646 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems ---BeginMessage--- Package: miniupnpd Version: 1.8.20140523-2 Severity: serious User: debian...@lists.debian.org Usertags: piuparts Hi, during a test with piuparts I noticed your package modifies conffiles. This is forbidden by the policy, see http://www.debian.org/doc/debian-policy/ch-files.html#s-config-files 10.7.3: [...] The easy way to achieve this behavior is to make the configuration file a conffile. [...] This implies that the default version will be part of the package distribution, and must not be modified by the maintainer scripts during installation (or at any other time). Note that once a package ships a modified version of that conffile, dpkg will prompt the user for an action how to handle the upgrade of this modified conffile (that was not modified by the user). Further in 10.7.3: [...] must not ask unnecessary questions (particularly during upgrades) [...] If a configuration file is customized by a maintainer script after having asked some debconf questions, it may not be marked as a conffile. Instead a template could be installed in /usr/share and used by the postinst script to fill in the custom values and create (or update) the configuration file (preserving any user modifications!). This file must be removed during postrm purge. ucf(1) may help with these tasks. See also http://wiki.debian.org/DpkgConffileHandling In https://lists.debian.org/debian-devel/2012/09/msg00412.html and followups it has been agreed that these bugs are to be filed with severity serious. debsums reports modification of the following files, from the attached log (scroll to the bottom...): /etc/miniupnpd/miniupnpd.conf cheers, Andreas miniupnpd_1.8.20140523-2.log.gz Description: application/gzip ---End Message--- ---BeginMessage--- Source: miniupnpd Source-Version: 1.8.20140523-3 We believe that the bug you reported is fixed in the latest version of miniupnpd, which is due to be installed in the Debian FTP archive. 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 767...@bugs.debian.org, and the maintainer will reopen the bug report if appropriate. Debian distribution maintenance software pp. Thomas Goirand z...@debian.org (supplier of updated miniupnpd 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 ftpmas...@ftp-master.debian.org) -BEGIN PGP SIGNED MESSAGE- Hash: SHA256 Format: 1.8 Date: Tue, 04 Nov 2014 16:35:36 +0800 Source: miniupnpd Binary: miniupnpd Architecture: source amd64 Version: 1.8.20140523-3 Distribution: unstable Urgency: medium Maintainer: Thomas Goirand z...@debian.org Changed-By: Thomas Goirand z...@debian.org Description: miniupnpd - UPnP and NAT-PMP daemon for gateway routers Closes: 767646 Changes: miniupnpd (1.8.20140523-3) unstable; urgency=medium . * Do not install the configuration file in /etc/miniupnpd, use /usr/share instead, so that miniupnpd.conf isn't CONFFILE (Closes: #767646). * Do not use /usr/share/doc/miniupnpd/examples to get our default config file, which isn't policy compliant, but use /usr/share/miniupnpd. Checksums-Sha1: d80c0ae2a19db088dea34ade8ba6b1ec1ec7483b 1923 miniupnpd_1.8.20140523-3.dsc 497cee3bc5ddb1a428d35973864a5f737140e7a3 14804 miniupnpd_1.8.20140523-3.debian.tar.xz ab02a70e39d979bc436a1a6bf98665e390e9fb29 84140 miniupnpd_1.8.20140523-3_amd64.deb Checksums-Sha256: 31e6d91398f49e6523b1e424ca0d52a3a12612e98d8069b14877ec5d9395b52c 1923 miniupnpd_1.8.20140523-3.dsc 393a4b7f1584ca8837b4976e13747d3df57139a5c0109e18957adf42e19a5c79 14804 miniupnpd_1.8.20140523-3.debian.tar.xz 5eb97d053af834e1cbc08ec5336b6a2547229c0fb64745a34a78e12319286ef5 84140 miniupnpd_1.8.20140523-3_amd64.deb Files: 052b9d566e8e6583b60aa43625b353f5 1923 net optional miniupnpd_1.8.20140523-3.dsc 4a3ea3b91d325bf90d4cb184c0d463ef 14804 net optional miniupnpd_1.8.20140523-3.debian.tar.xz 4b8cef2dc81273cc878564aba9c0018b 84140
Bug#762775: marked as done (pynfft: FTBFS: dh: unable to load addon sphinxdoc)
Your message dated Tue, 04 Nov 2014 09:35:11 + with message-id e1xlaw7-0005bw...@franck.debian.org and subject line Bug#762775: fixed in pynfft 1.3.2-1.1 has caused the Debian Bug report #762775, regarding pynfft: FTBFS: dh: unable to load addon sphinxdoc 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 this message is talking about, this may indicate a serious mail system misconfiguration somewhere. Please contact ow...@bugs.debian.org immediately.) -- 762775: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=762775 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems ---BeginMessage--- Source: pynfft Version: 1.3.2-1 Severity: serious Justification: fails to build from source Builds of pynfft in minimal environments geared for building its architecture-dependent binary packages (e.g., on the autobuilders) have been failing: dh clean --with python2,python3,sphinxdoc --buildsystem=pybuild dh: unable to load addon sphinxdoc: Can't locate Debian/Debhelper/Sequence/sphinxdoc.pm in @INC (you may need to install the Debian::Debhelper::Sequence::sphinxdoc module) (@INC contains: /etc/perl /usr/local/lib/«arch»/perl/5.20.0 /usr/local/share/perl/5.20.0 /usr/lib/«arch»/perl5/5.20 /usr/share/perl5 /usr/lib/«arch»/perl/5.20 /usr/share/perl/5.20 /usr/local/lib/site_perl .) at (eval 13) line 2. BEGIN failed--compilation aborted at (eval 13) line 2. make: *** [clean] Error 2 debian/rules:10: recipe for target 'clean' failed Could you please either conditionalize the usage of --with sphinxdoc appropriately or move python-sphinx into the main Build-Depends field? In the latter case, please bump the version to (= 1.2.2+dfsg-2~) to avoid running into errors if there is no actual documentation to install. (See #745690.) Thanks! ---End Message--- ---BeginMessage--- Source: pynfft Source-Version: 1.3.2-1.1 We believe that the bug you reported is fixed in the latest version of pynfft, which is due to be installed in the Debian FTP archive. 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 762...@bugs.debian.org, and the maintainer will reopen the bug report if appropriate. Debian distribution maintenance software pp. YunQiang Su s...@debian.org (supplier of updated pynfft 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 ftpmas...@ftp-master.debian.org) -BEGIN PGP SIGNED MESSAGE- Hash: SHA256 Format: 1.8 Date: Mon, 03 Nov 2014 15:30:59 +0800 Source: pynfft Binary: python-pynfft python-pynfft-dbg python3-pynfft python3-pynfft-dbg python-pynfft-doc Architecture: source amd64 all Version: 1.3.2-1.1 Distribution: unstable Urgency: low Maintainer: Debian Science Maintainers debian-science-maintain...@lists.alioth.debian.org Changed-By: YunQiang Su s...@debian.org Description: python-pynfft - Python bindings for the NFFT3 library - Python 2 python-pynfft-dbg - Python bindings for the NFFT3 library - Python 2 (debug) python-pynfft-doc - Python bindings for the NFFT3 library - Documentation python3-pynfft - Python bindings for the NFFT3 library - Python 3 python3-pynfft-dbg - Python bindings to the NFFT3 library - Python 3 (debug) Closes: 762775 Changes: pynfft (1.3.2-1.1) unstable; urgency=low . * Non-maintainer upload. * Move python-sphinx to build-dep instead of build-indep (Closes: 762775) * Don't use -malign-double, as it is x86 only. Checksums-Sha1: 64b3b592b3f788c9265831cfe24e3062f0c62f67 2157 pynfft_1.3.2-1.1.dsc 6e569722660c0fca5b160bc9b86e6e4e730c6bfc 2628 pynfft_1.3.2-1.1.debian.tar.xz d197159ce9398fb18f000db5b73226d74a997b81 71734 python-pynfft_1.3.2-1.1_amd64.deb 0867ae038c367075a88795f718515c06d4fdae8d 82608 python-pynfft-dbg_1.3.2-1.1_amd64.deb fd0eb7f1220c56dec6a92dc38972700e6390cfa3 64946 python3-pynfft_1.3.2-1.1_amd64.deb 5220287c34c801bafc69ecd3896e20ecea3e06e1 76320 python3-pynfft-dbg_1.3.2-1.1_amd64.deb 3e39c0899f003f2a4a2f87f23cb4db18752d3e2b 29204 python-pynfft-doc_1.3.2-1.1_all.deb Checksums-Sha256: c94f68a6d0da8a3af7d2a32cf526eec03b785d2df7e62d6c6c581f1fc4eb87ed 2157 pynfft_1.3.2-1.1.dsc b7b6efc4f7854948bb90f728b7b02f0fc9ecea780a847baefe8f566ca2ff761a 2628 pynfft_1.3.2-1.1.debian.tar.xz 3f6b996dabc06f2a1e8b0e3d8191afb7a5f355924bf803ca5a987208ec57b05a 71734 python-pynfft_1.3.2-1.1_amd64.deb e8eaaf46e8c9c678172d8c3a71a17bddf3454ece6c491ba5795f0607243041b9 82608 python-pynfft-dbg_1.3.2-1.1_amd64.deb 56e39e7fedcd7d75cf38b9e8e73568ee5efbe262437eb7c435914aa06a94fcfc 64946 python3-pynfft_1.3.2-1.1_amd64.deb
Bug#768025: systemd-logind: default configuration breaks any existing ACPI button handling
Package: systemd
Version: 215-5+b1
Severity: critical
Justification: breaks unrelated software
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
systemd-logind breaks acpid by default.
Merely installing systemd with default configuration causes it to start
handling the PowerKey, LidSwitch, HibernateKey and SuspendKey without
considering existing acpid configuration. This completely breaks those
events to break due to the double handling (pressing either of these
buttons two times does not give the desired result).
acpid and systemd are unrelated according to dependencies. The breakage
is therefore unexpected.
Note that this bug affects systems using sysvinit as well. systemd is
dragged in by policykit, and systemd-logind will be started by dbus on
request regardless of the init system being used.
Bjørn
- -- Package-specific info:
- -- System Information:
Debian Release: jessie/sid
APT prefers testing
APT policy: (990, 'testing'), (600, 'unstable'), (500, 'testing-updates'),
(1, 'experimental')
Architecture: amd64 (x86_64)
Foreign Architectures: i386
Kernel: Linux 3.18.0-rc3 (SMP w/2 CPU cores)
Locale: LANG=en_US.UTF-8, LC_CTYPE=en_US.UTF-8 (charmap=UTF-8)
Shell: /bin/sh linked to /bin/dash
Versions of packages systemd depends on:
ii acl 2.2.52-2
ii adduser 3.113+nmu3
ii initscripts 2.88dsf-53.4
ii libacl1 2.2.52-2
ii libaudit1 1:2.4-1
ii libblkid1 2.25.2-2
ii libc6 2.19-12
ii libcap2 1:2.24-6
ii libcap2-bin 1:2.24-6
ii libcryptsetup4 2:1.6.6-3
ii libgcrypt20 1.6.2-4
ii libkmod218-3
ii liblzma55.1.1alpha+20120614-2
ii libpam0g1.1.8-3.1
ii libselinux1 2.3-2
ii libsystemd0 215-5+b1
ii sysv-rc 2.88dsf-53.4
ii udev215-5+b1
ii util-linux 2.25.2-2
Versions of packages systemd recommends:
ii dbus1.8.8-2
ii libpam-systemd 215-5+b1
Versions of packages systemd suggests:
pn systemd-ui none
- -- Configuration Files:
/etc/systemd/logind.conf changed:
[Login]
HandlePowerKey=ignore
HandleSuspendKey=ignore
HandleHibernateKey=ignore
HandleLidSwitch=ignore
- -- no debconf information
-BEGIN PGP SIGNATURE-
Version: GnuPG v1
iEYEARECAAYFAlRYoZYACgkQ10rqkowbIskBEACdGQyrci0zI+0RV4QkbP/5H7M1
wXEAnj7CqasQJWzW+C1BqUwPv+sHJ8e5
=sFS0
-END PGP SIGNATURE-
[OVERRIDDEN] /etc/udev/rules.d/40-usb_modeswitch.rules - /lib/udev/rules.d/40-usb_modeswitch.rules
--- /lib/udev/rules.d/40-usb_modeswitch.rules 2014-06-09 11:21:49.0 +0200
+++ /etc/udev/rules.d/40-usb_modeswitch.rules 2012-11-10 21:18:02.0 +0100
@@ -1,12 +1,13 @@
-# Part of usb-modeswitch-data, version 20140529
+# Part of usb-modeswitch-data, version 20121109
#
-# Works with usb_modeswitch versions = 2.2.0 (introduction of HuaweiNewMode)
+# Recommended use with USB_ModeSwitch = 1.2.5, works with versions = 1.0.3
+# (New style, interface class check moved to dispatcher)
#
ACTION!=add|change, GOTO=modeswitch_rules_end
# Adds a symlink gsmmodem[n] to the lowest ttyUSB port with interrupt
# transfer; checked against a list of known modems, or else no action
-KERNEL==ttyUSB*, ATTRS{bNumConfigurations}==*, PROGRAM=usb_modeswitch --symlink-name %p %s{idVendor} %s{idProduct} %E{PRODUCT}, SYMLINK+=%c
+KERNEL==ttyUSB*, ATTRS{bNumConfigurations}==*, PROGRAM=usb_modeswitch --symlink-name %p %s{idVendor} %s{idProduct} %E{PRODUCT}, SYMLINK=%c
SUBSYSTEM!=usb, GOTO=modeswitch_rules_end
@@ -20,36 +21,18 @@
ACTION!=add, GOTO=modeswitch_rules_end
-# Generic entry for all Huawei devices
-ATTRS{idVendor}==12d1, ATTR{bInterfaceNumber}==00, ATTR{bInterfaceClass}==08, RUN+=usb_modeswitch '%b/%k'
-
# HP LaserJet Professional P1102
ATTR{idVendor}==03f0, ATTR{idProduct}==002a, RUN+=usb_modeswitch '%b/%k'
-# Quanta 1KR / USB-lte 7410
-ATTR{idVendor}==0408, ATTR{idProduct}==ea17, RUN+=usb_modeswitch '%b/%k'
-
-# Quanta 1K3 LTE
-ATTR{idVendor}==0408, ATTR{idProduct}==ea25, RUN+=usb_modeswitch '%b/%k'
-
-# Quanta MobileGenie 4G lte
-ATTR{idVendor}==0408, ATTR{idProduct}==ea43, RUN+=usb_modeswitch '%b/%k'
-
# Yota Router (Quanta 1QDLZZZ0ST2)
ATTR{idVendor}==0408, ATTR{idProduct}==f000, RUN+=usb_modeswitch '%b/%k'
-# SpeedUp SU-8500U
-ATTR{idVendor}==0408, ATTR{idProduct}==f001, RUN+=usb_modeswitch '%b/%k'
-
# Nokia CS-10
ATTR{idVendor}==0421, ATTR{idProduct}==060c, RUN+=usb_modeswitch '%b/%k'
# Nokia CS-15
ATTR{idVendor}==0421, ATTR{idProduct}==0610, RUN+=usb_modeswitch '%b/%k'
-# Nokia CS-12
-ATTR{idVendor}==0421, ATTR{idProduct}==0618, RUN+=usb_modeswitch '%b/%k'
-
# Nokia CS-11
ATTR{idVendor}==0421, ATTR{idProduct}==061d, RUN+=usb_modeswitch '%b/%k'
@@ -68,7 +51,7 @@
# Nokia CS-21M-02
ATTR{idVendor}==0421, ATTR{idProduct}==0637, RUN+=usb_modeswitch '%b/%k'
-# Philips (?), Vodafone MD950 (Wisue Technology)
+# Vodafone MD950 (Wisue Technology), Philips (?)
ATTR{idVendor}==0471, ATTR{idProduct}==1210, RUN+=usb_modeswitch '%b/%k'
# Philips TalkTalk (NXP
Bug#749994: tdiary-mode: fails to upgrade from sid
Followup-For: Bug #749994 Control: found -1 4.0.5.1-1 Install tdiary-mode for emacs24 install/tdiary-mode: Handling install for emacsen flavor emacs24 ERROR: install script from tdiary-mode package failed dpkg: error processing package emacs24-nox (--configure): subprocess installed post-installation script returned error exit status 1 Andreas tdiary-mode_4.0.5.1-1.log.gz Description: application/gzip
Processed: tdiary-mode: fails to upgrade from sid
Processing control commands:
found -1 4.0.5.1-1
Bug #749994 {Done: Hideki Yamane henr...@debian.org} [tdiary-mode]
tdiary-mode: fails to upgrade from wheezy
Marked as found in versions tdiary-contrib/4.0.5.1-1; no longer marked as fixed
in versions tdiary-contrib/4.0.5.1-1 and reopened.
--
749994: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=749994
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--
To UNSUBSCRIBE, email to debian-bugs-rc-requ...@lists.debian.org
with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Processed: fw
Processing commands for cont...@bugs.debian.org: forwarded 765118 http://bugzilla.scilab.org/show_bug.cgi?id=13586 Bug #765118 [src:scilab] scilab: FTBFS: [javac] /«PKGBUILDDIR»/modules/scirenderer/src/org/scilab/forge/scirenderer/implementation/jogl/JoGLCanvas.java:23: error: cannot find symbol Set Bug forwarded-to-address to 'http://bugzilla.scilab.org/show_bug.cgi?id=13586'. thanks Stopping processing here. Please contact me if you need assistance. -- 765118: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=765118 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems -- To UNSUBSCRIBE, email to debian-bugs-rc-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#768032: frontaccounting: fails to install: ERROR 1146 (42S02) at line 1: Table 'frontaccounting.0_company' doesn't exist
Package: frontaccounting Version: 2.3.21-1 Severity: serious User: debian...@lists.debian.org Usertags: piuparts Hi, during a test with piuparts I noticed your package failed to install. As per definition of the release team this makes the package too buggy for a release, thus the severity. From the attached log (scroll to the bottom...): Selecting previously unselected package frontaccounting. (Reading database ... 14828 files and directories currently installed.) Preparing to unpack .../frontaccounting_2.3.21-1_all.deb ... Unpacking frontaccounting (2.3.21-1) ... Setting up frontaccounting (2.3.21-1) ... ERROR 1146 (42S02) at line 1: Table 'frontaccounting.0_company' doesn't exist dpkg: error processing package frontaccounting (--configure): subprocess installed post-installation script returned error exit status 1 Errors were encountered while processing: frontaccounting mysql was installed and running in the chroot ... cheers, Andreas frontaccounting_2.3.21-1.log.gz Description: application/gzip
Bug#749994: tdiary-mode: fails to upgrade from sid
Control: notfound -1 4.0.5.1-1 Control: close -1 4.0.5.1-1 On 2014-11-04 11:31, Andreas Beckmann wrote: Install tdiary-mode for emacs24 install/tdiary-mode: Handling install for emacsen flavor emacs24 ERROR: install script from tdiary-mode package failed dpkg: error processing package emacs24-nox (--configure): subprocess installed post-installation script returned error exit status 1 darn, that was still the old package being installed ... Andreas -- To UNSUBSCRIBE, email to debian-bugs-rc-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Processed: Re: tdiary-mode: fails to upgrade from sid
Processing control commands: notfound -1 4.0.5.1-1 Bug #749994 [tdiary-mode] tdiary-mode: fails to upgrade from wheezy No longer marked as found in versions tdiary-contrib/4.0.5.1-1. close -1 4.0.5.1-1 Bug #749994 [tdiary-mode] tdiary-mode: fails to upgrade from wheezy Marked as fixed in versions tdiary-contrib/4.0.5.1-1. Bug #749994 [tdiary-mode] tdiary-mode: fails to upgrade from wheezy Marked Bug as done -- 749994: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=749994 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems -- To UNSUBSCRIBE, email to debian-bugs-rc-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#765156: flashproxy is marked for autoremoval from testing
Hi, On Dienstag, 4. November 2014, Ximin Luo wrote: OK, so it turns out you can do this in automake easily with a flag. I've added it to debian/rules. cool Candidate for 1.7-2: https://mentors.debian.net/package/flashproxy Let me know if it works, and I'll upload a proper release. I wont check today or probably tomorrow anyway, I'm sick with fever atm, so why don't you make it a release anyway and once I'm better I will look at probably just upload. That also saves us another roundtrip... cheers, Holger signature.asc Description: This is a digitally signed message part.
Processed: Re: Bug#749994: tdiary-mode: fails to upgrade from sid
Processing control commands:
found -1 4.0.5.1-1
Bug #749994 {Done: Andreas Beckmann a...@debian.org} [tdiary-mode]
tdiary-mode: fails to upgrade from wheezy
Marked as found in versions tdiary-contrib/4.0.5.1-1; no longer marked as fixed
in versions tdiary-contrib/4.0.5.1-1 and reopened.
tags -1 + patch
Bug #749994 [tdiary-mode] tdiary-mode: fails to upgrade from wheezy
Added tag(s) patch.
--
749994: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=749994
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--
To UNSUBSCRIBE, email to debian-bugs-rc-requ...@lists.debian.org
with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#749994: tdiary-mode: fails to upgrade from sid
Control: found -1 4.0.5.1-1
Control: tags -1 + patch
On November 4, 2014 at 11:31AM +0100, anbe (at debian.org) wrote:
install/tdiary-mode: Handling install for emacsen flavor emacs24
ERROR: install script from tdiary-mode package failed
It seems tdiary-mode fails when byte-compiling because of missing
apel/*.elc files. (This problem is potentially caused even if
`Depends: apel`. See also a known issue in emacsen-common, bug#737389.)
The following patch should fix this bug.
```
--- s/debian/tdiary-mode.emacsen-install2013-01-03 09:40:47.0
+0900
+++ b/debian/tdiary-mode.emacsen-install2014-11-04 20:40:29.337884783
+0900
@@ -10,6 +10,7 @@
LOG=CompilationLog
if [ ${FLAVOR} = emacs ]; then exit 0; fi
+if [ ! -f /usr/share/$FLAVOR/site-lisp/apel/pces.elc ]; then exit 0; fi
echo install/${PACKAGE}: Handling install for emacsen flavor ${FLAVOR}
```
Thanks,
--
Tatsuya Kinoshita
pgparQRrb6JWm.pgp
Description: PGP signature
Processed: Re: libblitz-doc: fails to upgrade from 'testing' - trying to overwrite /usr/share/info/blitz.info.gz
Processing control commands:
found -1 1:0.10-3
Bug #767564 {Done: Andreas Tille ti...@debian.org} [libblitz-doc]
libblitz-doc: fails to upgrade from 'testing' - trying to overwrite
/usr/share/info/blitz.info.gz
Marked as found in versions blitz++/1:0.10-3; no longer marked as fixed in
versions blitz++/1:0.10-3 and reopened.
--
767564: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=767564
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--
To UNSUBSCRIBE, email to debian-bugs-rc-requ...@lists.debian.org
with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#767564: libblitz-doc: fails to upgrade from 'testing' - trying to overwrite /usr/share/info/blitz.info.gz
Followup-For: Bug #767564 Control: found -1 1:0.10-3 Breaks without Replaces is not sufficient Andreas -- To UNSUBSCRIBE, email to debian-bugs-rc-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#767589: systemd: cryptdisks other than root/swap fail cryptsetup
Am 04.11.2014 um 11:46 schrieb Arnaud Installe: cue shell is booted off an initrd image which doesn't have enough of systemd / journalctl available (libraries missing etc.). So I ran the commands you mention after I manually ran cryptsetup for boulez-_home_, boulez-_usr_, and boulez-_var_, exited the rescue shell, and waited for the system to finish booting. I hope that the logs will help finding the problem. Thanks for looking into it! Ok, that log is then not really helpful. What confuses me though, is that you said you have no journalctl available in the rescue shell? Are you by chance dropped into the rescue shell from the initramfs and not the systemd rescue shell? Can you make a screenshot of the rescue shell prompt? -- Why is it that all of the instruments seeking intelligent life in the universe are pointed away from Earth? signature.asc Description: OpenPGP digital signature
Processed: found 767917 in 1.3.2-1, found 767917 in 2.0.8-0.1, affects 767819, affects 767690 ...
Processing commands for cont...@bugs.debian.org: found 767917 1.3.2-1 Bug #767917 [waagent] waagent: prompting due to modified conffiles which were not modified by the user: /etc/init.d/waagent Marked as found in versions waagent/1.3.2-1. found 767917 2.0.8-0.1 Bug #767917 [waagent] waagent: prompting due to modified conffiles which were not modified by the user: /etc/init.d/waagent Marked as found in versions waagent/2.0.8-0.1. affects 767819 + bareos-director bareos-bconsole Bug #767819 [bareos] bareos-*: modifies conffiles (policy 10.7.3): /etc/bareos/bareos-*.conf Added indication that 767819 affects bareos-bconsole affects 767690 + tpm-tools Bug #767690 [trousers] trousers: fails to install: subprocess installed post-installation script returned error exit status 2 Added indication that 767690 affects tpm-tools found 767826 0.10-2 Bug #767826 [python3-django-assets] python3-django-assets: fails to install: SyntaxError: Missing parentheses in call to 'print' Marked as found in versions django-assets/0.10-2. thanks Stopping processing here. Please contact me if you need assistance. -- 767690: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=767690 767819: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=767819 767826: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=767826 767917: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=767917 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems -- To UNSUBSCRIBE, email to debian-bugs-rc-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#767734: upgrade failure: perl-modules depends on perl which is not configured yet
On Sun, Nov 02, 2014 at 12:51:02PM +0100, Sven Joachim wrote: [CC'ing apt maintainers.] On 2014-11-02 10:27 +0100, Peter Palfrader wrote: Package: perl Version: 5.20.1-2 Severity: serious while upgrading a sid chroot, perl fails to upgrade: } Unpacking perl-modules (5.20.1-2) over (5.18.2-7) ... } dpkg: dependency problems prevent configuration of perl-modules: } perl-modules depends on perl (= 5.20.1-1); however: } Package perl is not configured yet. } } dpkg: error processing package perl-modules (--configure): } dependency problems - leaving unconfigured } Errors were encountered while processing: } perl-modules } E: Sub-process /usr/bin/dpkg returned an error code (1) The circular dependency between perl and perl-modules has been around for ages, and it can be broken by configuring both perl and perl-modules in one run and letting dpkg figure out the order. It seems as if apt told dpkg to only configure perl-modules which cannot work. I think this is the same problem as in https://bugs.launchpad.net/ubuntu/+source/apt/+bug/1347721, and it's fixed in apt 1.0.7 (you have apt 1.0.6, 0.9.9 introduced the bug). Thanks for looking at this. While the above sounds good, we also have a wheezy-jessie jenkins upgrade failure with a similar error, tracked as #766260. The log looks like it was with wheezy's apt (0.9.7.9+deb7u6), although it got bumped to 1.0.9.3 during the upgrade. So I wonder if there's another related apt bug or if this is something else. There's a full log in #766260, quoting some snippets: [in a just-prepared wheezy chroot] + apt-get -y install 'haskell-platform.*' 'libghc-.*' [...] [switch to jessie] + apt-get -y upgrade [...] [no change to perl-base/perl/perl-modules yet] + apt-get -yf dist-upgrade [...] Preparing to unpack .../perl_5.20.1-1_amd64.deb ... Unpacking perl (5.20.1-1) over (5.14.2-21+deb7u2) ... [...] Preparing to unpack .../perl-base_5.20.1-1_amd64.deb ... Unpacking perl-base (5.20.1-1) over (5.14.2-21+deb7u2) ... Processing triggers for man-db (2.7.0.2-1) ... Setting up perl-base (5.20.1-1) ... [...] Preparing to unpack .../perl-modules_5.20.1-1_all.deb ... Unpacking perl-modules (5.20.1-1) over (5.14.2-21+deb7u2) ... [...] dpkg: dependency problems prevent configuration of perl: perl depends on perl-modules (= 5.20.1-1); however: Package perl-modules is not configured yet. dpkg: error processing package perl (--configure): dependency problems - leaving unconfigured -- Niko Tyni nt...@debian.org -- To UNSUBSCRIBE, email to debian-bugs-rc-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Processed: Re: Bug#768038: dgit: on jessie clone of package for suite sid gets jessie version
Processing control commands: severity -1 serious Bug #768038 [dgit] dgit: on jessie clone of package for suite sid gets jessie version Severity set to 'serious' from 'important' -- 768038: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=768038 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems -- To UNSUBSCRIBE, email to debian-bugs-rc-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#763909: Bug#767919: unblock: viewmol/2.4.1-21
Hi Andreas So far, I haven't been able to get the package to build at all without switching to source format 3.0. I'll try now to see if I am able to skip the getmachine call. For the record, debian/patches/010_build_scripts.diff already contains a patch to allow it to build on kfreebsd: +case $os in +GNU/k*BSD | GNU) +# GNU variants are treated like Linux +os=Linux +;; +*) +;; +esac + I was able to build the package in a kfreebsd virtual machine (although after switching to source format 3.0) and the package installed and ran, but complained about missing files ($VIEWMOL/GNU/kFreeBSD/*) when trying to view some of the sample molecules. So some additional work is required there, but that's for another bug. Regards Graham -- To UNSUBSCRIBE, email to debian-bugs-rc-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Processed: Re: Bug#767589: systemd: cryptdisks other than root/swap fail cryptsetup
Processing control commands: reassign -1 initramfs-tools Bug #767589 [systemd] systemd: cryptdisks other than root/swap fail cryptsetup Bug reassigned from package 'systemd' to 'initramfs-tools'. No longer marked as found in versions systemd/215-5. Ignoring request to alter fixed versions of bug #767589 to the same values previously set -- 767589: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=767589 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems -- To UNSUBSCRIBE, email to debian-bugs-rc-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#767589: systemd: cryptdisks other than root/swap fail cryptsetup
Control: reassign -1 initramfs-tools Am 04.11.2014 um 13:37 schrieb Arnaud Installe: On Tue, 04 Nov 2014 13:20:05 +0100 Michael Biebl bi...@debian.org wrote: Am 04.11.2014 um 11:46 schrieb Arnaud Installe: cue shell is booted off an initrd image which doesn't have enough of systemd / journalctl available (libraries missing etc.). So I ran the commands you mention after I manually ran cryptsetup for boulez-_home_, boulez-_usr_, and boulez-_var_, exited the rescue shell, and waited for the system to finish booting. I hope that the logs will help finding the problem. Thanks for looking into it! Ok, that log is then not really helpful. What confuses me though, is that you said you have no journalctl available in the rescue shell? Are you by chance dropped into the rescue shell from the initramfs and not the systemd rescue shell? Yes. The shell prompt says (initramfs) . Does that mean that this bug should have been assigned to initramfs-tools instead of systemd? Yes. Can you make a screenshot of the rescue shell prompt? If you're looking for more than just the rescue shell prompt, I'll make a screenshot tonight, and add it to the bug report. Otherwise, I'll just add the information from this e-mail. No, this information is sufficient, so a screenshot is not necessary. Since this is indeed an issue in initramfs-tools, which is started *before* systemd, systemd is not involved here. Therefore re-assigning to initramfs-tools. Please followup on the bug report and include the version of initramfs-tools you have installed. As well as the version of cryptsetup. thanks, Michael -- Why is it that all of the instruments seeking intelligent life in the universe are pointed away from Earth? signature.asc Description: OpenPGP digital signature
Bug#765156: flashproxy is marked for autoremoval from testing
On 04/11/14 11:54, Holger Levsen wrote: Candidate for 1.7-2: https://mentors.debian.net/package/flashproxy Let me know if it works, and I'll upload a proper release. I wont check today or probably tomorrow anyway, I'm sick with fever atm, so why don't you make it a release anyway and once I'm better I will look at probably just upload. That also saves us another roundtrip... OK, I've uploaded a release candidate to mentors, same address as above. Get well soon! X -- GPG: 4096R/1318EFAC5FBBDBCE git://github.com/infinity0/pubkeys.git signature.asc Description: OpenPGP digital signature
Bug#763909: Bug#767919: unblock: viewmol/2.4.1-21
Hi Graham, On Tue, Nov 04, 2014 at 02:41:27PM +0200, Graham Inggs wrote: Hi Andreas So far, I haven't been able to get the package to build at all without switching to source format 3.0. Well, I personally do not agree with the set freeze rules but we need to follow if we want to see viewmol in Jessie. I'll try now to see if I am able to skip the getmachine call. This would be great. For the record, debian/patches/010_build_scripts.diff already contains a patch to allow it to build on kfreebsd: +case $os in +GNU/k*BSD | GNU) +# GNU variants are treated like Linux +os=Linux +;; +*) +;; +esac + I was able to build the package in a kfreebsd virtual machine (although after switching to source format 3.0) and the package installed and ran, but complained about missing files ($VIEWMOL/GNU/kFreeBSD/*) when trying to view some of the sample molecules. So some additional work is required there, but that's for another bug. Yes. Thanks for your work on this Andreas. -- http://fam-tille.de -- To UNSUBSCRIBE, email to debian-bugs-rc-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#768038: marked as done (dgit: on jessie clone of package for suite sid gets jessie version)
Your message dated Tue, 04 Nov 2014 13:03:55 + with message-id e1xldm7-00081m...@franck.debian.org and subject line Bug#768038: fixed in dgit 0.22.1 has caused the Debian Bug report #768038, regarding dgit: on jessie clone of package for suite sid gets jessie version 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 this message is talking about, this may indicate a serious mail system misconfiguration somewhere. Please contact ow...@bugs.debian.org immediately.) -- 768038: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=768038 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems ---BeginMessage--- Package: dgit Version: 0.22 Severity: important Using dgit with bibletime The version of bibletime in sid/amd64 is 2.10.1-1 The version of bibletime in jessie/amd64 is 2.9.2-1.1 $ dgit clone bibletime canonical suite name for unstable is sid starting new git history downloading http://ftp.debian.org/debian//pool/main/b/bibletime/bibletime_2.9.2-1.1.dsc... last upload to archive has NO git hash $ dgit clone bibletime sid does same -- System Information: Debian Release: jessie/sid APT prefers testing APT policy: (500, 'testing') Architecture: amd64 (x86_64) Foreign Architectures: i386 Kernel: Linux 3.16-3-amd64 (SMP w/2 CPU cores) Locale: LANG=en_GB.UTF-8, LC_CTYPE=en_GB.UTF-8 (charmap=UTF-8) Shell: /bin/sh linked to /bin/dash Versions of packages dgit depends on: ii curl 7.38.0-2 ii devscripts 2.14.10 ii dpkg-dev 1.17.21 ii dput 0.9.6.4 ii git [git-core] 1:2.1.1-1 ii libdpkg-perl 1.17.21 ii libwww-perl6.08-1 ii perl [libdigest-sha-perl] 5.20.1-2 ii realpath 8.23-2 ii wget 1.16-1 Versions of packages dgit recommends: ii openssh-client [ssh-client] 1:6.7p1-2 Versions of packages dgit suggests: ii sbuild 0.65.0-1 -- no debconf information ---End Message--- ---BeginMessage--- Source: dgit Source-Version: 0.22.1 We believe that the bug you reported is fixed in the latest version of dgit, which is due to be installed in the Debian FTP archive. 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 768...@bugs.debian.org, and the maintainer will reopen the bug report if appropriate. Debian distribution maintenance software pp. Ian Jackson ijack...@chiark.greenend.org.uk (supplier of updated dgit 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 ftpmas...@ftp-master.debian.org) -BEGIN PGP SIGNED MESSAGE- Hash: SHA256 Format: 1.8 Date: Tue, 04 Nov 2014 12:46:40 + Source: dgit Binary: dgit Architecture: all source Version: 0.22.1 Distribution: unstable Urgency: high Maintainer: Ian Jackson ijack...@chiark.greenend.org.uk Changed-By: Ian Jackson ijack...@chiark.greenend.org.uk Closes: 768038 Description: dgit - git interoperability with the Debian archive Changes: dgit (0.22.1) unstable; urgency=high . * Use Dpkg::Version::version_compare everywhere, not Dpkg::Version::version_compare_string. The latter is entirely wrong, meaning that dgit would get many version comparisons wrong. Closes:#768038. Checksums-Sha1: 236d27e6fb6fb8f34896659ae1a3d92aa6498f6f 1215 dgit_0.22.1.dsc 1e0079b3ef8b3c2d49e7fc0ab459db938f176bf4 169464 dgit_0.22.1.tar.gz f571bb38e99b029370a5a2fef135e4bf17c0b0e3 39804 dgit_0.22.1_all.deb Checksums-Sha256: 1888c4de424f886eebbedd1c90ce8d2fbf4f6c26a37e44ec4a47689d14802130 1215 dgit_0.22.1.dsc 978d2ad2df7784a2cc553ce16e4904ab20df9e477175b7d826b7f7eb26bf374a 169464 dgit_0.22.1.tar.gz 9072f4c09fc5ca513fa1c3435318ee371b5898c49b3aa46d3bd6cf03675516a3 39804 dgit_0.22.1_all.deb Files: 862e956b5b7ce88b13c3866e8514acc0 1215 devel optional dgit_0.22.1.dsc abb212328fcee7559f27106e1fb58bd3 169464 devel optional dgit_0.22.1.tar.gz 3071ad9612de83b886e09342e8688850 39804 devel optional dgit_0.22.1_all.deb -BEGIN PGP SIGNATURE- Version: GnuPG v1.4.12 (GNU/Linux) iQEcBAEBCAAGBQJUWM4IAAoJEOPjOSNItQ05K4IH+QH4EXf3suyuELwFwOIYQFif FHF9SSaTM9R012pxnQuKWkdXHtfl7AT8weGqmSWayC+JWFdX1Gb3enwmY22hoKK0 y9rNwlGmlrxRhBR94p3GawRsQqUNErCQVgN/3BnI7x2YPdMCa+Hq+hOh5UHENaiU 7bpnbAfmIH8TeBmJWnSEJJw+mfutYApELlUqHhZjPkGu//0gTSjBC5Pz9GvhPLrB MuCRbs/wAFeW/9wTfzZQRGRvEdrRhnLqeUbNFtP7Y10Ozefue9g7ebkkMoHdzyVM 821XbWtw+tW7l4otYVseUTJlz6GDZ0qVoZVK7yG41Cpiu7fFxcE4MJ2ao20wrGM= =PfXt -END PGP SIGNATUREEnd Message---
Processed: Re: Bug#765129: tcos: FTBFS: build-dependency not installable: libxmlrpc-c3-dev
Processing control commands:
reopen -1
Bug #765129 {Done: David Suárez david.sephi...@gmail.com} [src:tcos] tcos:
FTBFS: build-dependency not installable: libxmlrpc-c3-dev
Bug reopened
Ignoring request to alter fixed versions of bug #765129 to the same values
previously set
--
765129: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=765129
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--
To UNSUBSCRIBE, email to debian-bugs-rc-requ...@lists.debian.org
with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#765129: tcos: FTBFS: build-dependency not installable: libxmlrpc-c3-dev
Control: reopen -1 On 14/10/14 19:03, Mario Izquierdo Rodríguez wrote: El 13/10/14 a las #4, David Suárez escribió: Source: tcos Version: 0.89.93 Severity: serious Tags: jessie sid User: debian...@lists.debian.org Usertags: qa-ftbfs-20141012 qa-ftbfs Justification: FTBFS on amd64 Hi, During a rebuild of all packages in sid, your package failed to build on amd64. Relevant part (hopefully): ┌──┐ │ Install tcos build dependencies (apt-based resolver) │ └──┘ Installing build dependencies Reading package lists... Building dependency tree... Reading state information... Some packages could not be installed. This may mean that you have requested an impossible situation or if you are using the unstable distribution that some required packages have not yet been created or been moved out of Incoming. The following information may help to resolve the situation: The following packages have unmet dependencies: sbuild-build-depends-tcos-dummy : Depends: libxmlrpc-c3-dev but it is not installable E: Unable to correct problems, you have held broken packages. apt-get failed. The full build log is available from: http://aws-logs.debian.net/ftbfs-logs/2014/10/12/tcos_0.89.93_unstable.log A list of current common problems and possible solutions is available at http://wiki.debian.org/qa.debian.org/FTBFS . You're welcome to contribute! About the archive rebuild: The rebuild was done on EC2 VM instances from Amazon Web Services, using a clean, minimal and up-to-date chroot. Every failed build was retried once to eliminate random failures. Hi Build-Depends of tcos contains: |libxmlrpc-c3-dev | libxmlrpc-core-c3-dev| || |It isn't enough?| No, that's not good. The buildds only consider the first alternative, so that must be installable. However libxmlrpc-c3-dev no longer exists. See e.g.: https://buildd.debian.org/status/fetch.php?pkg=tcosarch=armelver=0.89.96stamp=1415104393 Emilio -- To UNSUBSCRIBE, email to debian-bugs-rc-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#765285: lower severity to important
package: mapsembler2 severity 765285 important thanks FTBS archs have been removed by FTP masters (#766961). -- gpg key id: 4096R/326D8438 (keyring.debian.org) Key fingerprint = 5FB4 6F83 D3B9 5204 6335 D26D 78DC 68DB 326D 8438
Bug#766849: gnome-shell responds and renders hazardously
Hello, Perhaps you could share more details of your system; it sounds like maybe a graphics driver problem. Maybe you only see issues under GNOME because 3D acceleration is active all of the time. You can probably gather the most relevant info by running: $ /usr/share/bug/xserver-xorg/script 31 You may want to pipe that through `gzip --best` and attach it to this bug report. Thanks. Regards, -- Steven Chamberlain ste...@pyro.eu.org -- To UNSUBSCRIBE, email to debian-bugs-rc-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#768054: fp-units-multimedia: Upgrade fail from wheezy to jessie (versioned dependency on fp-units-multimedia-2.6.0)
Package: fp-units-multimedia Version: 2.6.4+dfsg-4 Severity: serious User: debian-...@lists.debian.org Usertags: debian-edu We discovered this when testing package upgrades of the Debian Edu tasks. The upgrade of the education-development task/metapackage failed like this: Building dependency tree... Reading state information... The following packages have unmet dependencies: fp-units-multimedia : Depends: fp-units-multimedia-2.6.0 (= 2.6.0-9) but it is not going to be installed fpc-2.6.0 : Depends: fp-units-multimedia-2.6.0 (= 2.6.0-9) but it is not going to be installed E: Error, pkgProblemResolver::Resolve generated breaks, this may be caused by held packages. Sat Nov 1 09:32:20 UTC 2014 - /srv/jenkins/bin/chroot-installation.sh stopped running as /tmp/jenkins-script-SioIc9Mr, which will now be removed. Build step 'Execute shell' marked build as failure The full log can be seen on URL: https://jenkins.debian.net/view/edu_devel/job/chroot-installation_wheezy_install_education-development_upgrade_to_jessie/ . I guess there is something wrong with the dependencies of fp-units-multimedia but have not investigated. Setting severity to serious, as packages should be upgradable between releases. -- Happy hacking Petter Reinholdtsen -- To UNSUBSCRIBE, email to debian-bugs-rc-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#765129: tcos: FTBFS: build-dependency not installable: libxmlrpc-c3-dev
Hello Emilio. Can I reverse the build deps order or I need to remove libxmlrpc-c3-dev from build deps? - libxmlrpc-c3-dev | libxmlrpc-core-c3-dev, + libxmlrpc-core-c3-dev | libxmlrpc-c3-dev, I want to build the same source in old distros, for ex: http://www.tcosproject.org/versions.php Thanks for your help El 04/11/14 a las 14:08, Emilio Pozuelo Monfort escribió: Control: reopen -1 On 14/10/14 19:03, Mario Izquierdo Rodríguez wrote: El 13/10/14 a las #4, David Suárez escribió: Source: tcos Version: 0.89.93 Severity: serious Tags: jessie sid User: debian...@lists.debian.org Usertags: qa-ftbfs-20141012 qa-ftbfs Justification: FTBFS on amd64 Hi, During a rebuild of all packages in sid, your package failed to build on amd64. Relevant part (hopefully): ┌──┐ │ Install tcos build dependencies (apt-based resolver) │ └──┘ Installing build dependencies Reading package lists... Building dependency tree... Reading state information... Some packages could not be installed. This may mean that you have requested an impossible situation or if you are using the unstable distribution that some required packages have not yet been created or been moved out of Incoming. The following information may help to resolve the situation: The following packages have unmet dependencies: sbuild-build-depends-tcos-dummy : Depends: libxmlrpc-c3-dev but it is not installable E: Unable to correct problems, you have held broken packages. apt-get failed. The full build log is available from: http://aws-logs.debian.net/ftbfs-logs/2014/10/12/tcos_0.89.93_unstable.log A list of current common problems and possible solutions is available at http://wiki.debian.org/qa.debian.org/FTBFS . You're welcome to contribute! About the archive rebuild: The rebuild was done on EC2 VM instances from Amazon Web Services, using a clean, minimal and up-to-date chroot. Every failed build was retried once to eliminate random failures. Hi Build-Depends of tcos contains: |libxmlrpc-c3-dev | libxmlrpc-core-c3-dev| || |It isn't enough?| No, that's not good. The buildds only consider the first alternative, so that must be installable. However libxmlrpc-c3-dev no longer exists. See e.g.: https://buildd.debian.org/status/fetch.php?pkg=tcosarch=armelver=0.89.96stamp=1415104393 Emilio -- Mario Izquierdo Rodríguez http://mariodebian.com -- To UNSUBSCRIBE, email to debian-bugs-rc-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Processed: Bug#767999
Processing commands for cont...@bugs.debian.org: retitle 767999 please upload for stable Bug #767999 [debootstrap] base-files: fails to install with pre-jessie debootstrap Changed Bug title to 'please upload for stable' from 'base-files: fails to install with pre-jessie debootstrap' thanks Stopping processing here. Please contact me if you need assistance. -- 767999: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=767999 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems -- To UNSUBSCRIBE, email to debian-bugs-rc-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#766250: eject: [kfreebsd] fails to open cdrom tray
tags 766250 + wheezy thanks Hi, There seems to be no problem with this on a jessie system. I'm still leaving this 'gift' bug if someone would like practice at simple debugging on kfreebsd. Thanks, Regards, -- Steven Chamberlain ste...@pyro.eu.org -- To UNSUBSCRIBE, email to debian-bugs-rc-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Processed: Re: Bug#766250: eject: [kfreebsd] fails to open cdrom tray
Processing commands for cont...@bugs.debian.org: tags 766250 + wheezy Bug #766250 [eject] eject: [kfreebsd] fails to open cdrom tray Added tag(s) wheezy. thanks Stopping processing here. Please contact me if you need assistance. -- 766250: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=766250 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems -- To UNSUBSCRIBE, email to debian-bugs-rc-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#765129: tcos: FTBFS: build-dependency not installable: libxmlrpc-c3-dev
On 04/11/14 15:28, Mario Izquierdo Rodríguez wrote: Hello Emilio. Can I reverse the build deps order or I need to remove libxmlrpc-c3-dev from build deps? You can reverse it. All that matters is that the first alternative is fine, as the buildds will ignore the rest. Emilio -- To UNSUBSCRIBE, email to debian-bugs-rc-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Processed: Re: Bug#756076: Acknowledgement (does not cleanup sessions when user logs out: No such interface 'org.freedesktop.systemd1.Scope')
Processing control commands: retitle -1 does not cleanup sessions when user logs out Bug #756076 [systemd-shim] does not cleanup sessions when user logs out: No such interface 'org.freedesktop.systemd1.Scope' Bug #756760 [systemd-shim] systemd: stale session prevents hibernation of workstation Changed Bug title to 'does not cleanup sessions when user logs out' from 'does not cleanup sessions when user logs out: No such interface 'org.freedesktop.systemd1.Scope'' Changed Bug title to 'does not cleanup sessions when user logs out' from 'systemd: stale session prevents hibernation of workstation' -- 756076: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=756076 756760: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=756760 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems -- To UNSUBSCRIBE, email to debian-bugs-rc-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#756076: Acknowledgement (does not cleanup sessions when user logs out: No such interface 'org.freedesktop.systemd1.Scope')
Control: retitle -1 does not cleanup sessions when user logs out Cameron Norman [2014-09-28 14:35 -0700]: While this is true, it seems that device permissions are actually removed correctly. Not here actually. At least under current Ubuntu, when I log out my test user, the automatic ACL on /dev/kvm persists as long as the corresponding logind session remains in closing state. This might look differently in other scenarios, but that it happens in some scenarios is IMHO enough to justify the high severity. I adjust the bug title as the org.freedesktop.systemd1.Scope part was implemented a while ago. Indeed the cgroups get cleaned up properly, just nothing tells logind about that as there is currently no notify_on_release being set/used. I'm looking into that now. Thanks, Martin -- Martin Pitt| http://www.piware.de Ubuntu Developer (www.ubuntu.com) | Debian Developer (www.debian.org) signature.asc Description: Digital signature
Processed: forcibly merging 764355 764340
Processing commands for cont...@bugs.debian.org: forcemerge 764355 764340 Bug #764355 [targetcli] targetcli: Fails to load or save any config on Jessie Bug #764340 [targetcli] targetcli: On new install exit or configure etc. fail due to missing /var/target/policy Severity set to 'grave' from 'important' Merged 764340 764355 thanks Stopping processing here. Please contact me if you need assistance. -- 764340: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=764340 764355: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=764355 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems -- To UNSUBSCRIBE, email to debian-bugs-rc-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#767931: fusionforge-plugin-foafprofiles: fails to install: PHP Fatal error: require_once(): Failed opening required 'arc/ARC2.php'
Hi. Andreas Beckmann a...@debian.org writes: during a test with piuparts I noticed your package failed to install. As per definition of the release team this makes the package too buggy for a release, thus the severity. From the attached log (scroll to the bottom...): Setting up fusionforge-plugin-foafprofiles (5.3.2-1) ... Entering upgrade-db.php PHP Warning: require_once(arc/ARC2.php): failed to open stream: No such file or directory in /usr/share/gforge/common/include/rdfutils.php on line 23 PHP Fatal error: require_once(): Failed opening required 'arc/ARC2.php' (include_path='/usr/share/php-htmlpurifier/library:/etc/fusionforge//custom:/etc/fusionforge/:/usr/share/gforge/common:/usr/share/gforge/www:/usr/share/gforge/plugins:/usr/share/gforge:/usr/share/gforge/www/include:/usr/share/gforge/common/include:.:/usr/share/php:/usr/share/pear') in /usr/share/gforge/common/include/rdfutils.php on line 23 dpkg: error processing package fusionforge-plugin-foafprofiles (--configure): subprocess installed post-installation script returned error exit status 255 Processing triggers for libc-bin (2.19-11) ... Errors were encountered while processing: fusionforge-plugin-foafprofiles This very much looks like a missing dependency on php-arc Don't have the time to fix this myself for the moment, sorry. Hope this helps. Best regards, -- Olivier BERGER http://www-public.telecom-sudparis.eu/~berger_o/ - OpenPGP-Id: 2048R/5819D7E8 Ingenieur Recherche - Dept INF Institut Mines-Telecom, Telecom SudParis, Evry (France) -- To UNSUBSCRIBE, email to debian-bugs-rc-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#767819: marked as done (bareos-*: modifies conffiles (policy 10.7.3): /etc/bareos/bareos-*.conf)
Your message dated Tue, 04 Nov 2014 16:04:39 + with message-id e1xlgb1-0002pc...@franck.debian.org and subject line Bug#767819: fixed in bareos 14.2.1+20141017gitc6c5b56-3 has caused the Debian Bug report #767819, regarding bareos-*: modifies conffiles (policy 10.7.3): /etc/bareos/bareos-*.conf 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 this message is talking about, this may indicate a serious mail system misconfiguration somewhere. Please contact ow...@bugs.debian.org immediately.) -- 767819: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=767819 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems ---BeginMessage--- Package: bareos Version: 14.2.1+20141017gitc6c5b56-2 Severity: serious User: debian...@lists.debian.org Usertags: piuparts Hi, during a test with piuparts I noticed your package modifies conffiles. This is forbidden by the policy, see http://www.debian.org/doc/debian-policy/ch-files.html#s-config-files 10.7.3: [...] The easy way to achieve this behavior is to make the configuration file a conffile. [...] This implies that the default version will be part of the package distribution, and must not be modified by the maintainer scripts during installation (or at any other time). Note that once a package ships a modified version of that conffile, dpkg will prompt the user for an action how to handle the upgrade of this modified conffile (that was not modified by the user). Further in 10.7.3: [...] must not ask unnecessary questions (particularly during upgrades) [...] If a configuration file is customized by a maintainer script after having asked some debconf questions, it may not be marked as a conffile. Instead a template could be installed in /usr/share and used by the postinst script to fill in the custom values and create (or update) the configuration file (preserving any user modifications!). This file must be removed during postrm purge. ucf(1) may help with these tasks. See also http://wiki.debian.org/DpkgConffileHandling In https://lists.debian.org/debian-devel/2012/09/msg00412.html and followups it has been agreed that these bugs are to be filed with severity serious. debsums reports modification of the following files, from the attached log (scroll to the bottom...): /etc/bareos/bareos-dir.conf and from other tests /etc/bareos/bareos-sd.conf /etc/bareos/bconsole.conf /etc/bareos/bareos-fd.conf /etc/bareos/bat.conf /etc/bareos/tray-monitor.conf cheers, Andreas bareos-director_14.2.1+20141017gitc6c5b56-2.log.gz Description: application/gzip ---End Message--- ---BeginMessage--- Source: bareos Source-Version: 14.2.1+20141017gitc6c5b56-3 We believe that the bug you reported is fixed in the latest version of bareos, which is due to be installed in the Debian FTP archive. 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 767...@bugs.debian.org, and the maintainer will reopen the bug report if appropriate. Debian distribution maintenance software pp. Evgeni Golov evg...@debian.org (supplier of updated bareos 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 ftpmas...@ftp-master.debian.org) -BEGIN PGP SIGNED MESSAGE- Hash: SHA512 Format: 1.8 Date: Tue, 04 Nov 2014 07:19:30 +0100 Source: bareos Binary: bareos bareos-bconsole bareos-client bareos-common bareos-database-common bareos-database-postgresql bareos-database-mysql bareos-database-sqlite3 bareos-database-tools bareos-dbg bareos-devel bareos-director bareos-filedaemon bareos-storage bareos-storage-fifo bareos-storage-tape bareos-tools bareos-bat bareos-director-python-plugin bareos-filedaemon-python-plugin bareos-storage-python-plugin bareos-traymonitor Architecture: source amd64 Version: 14.2.1+20141017gitc6c5b56-3 Distribution: unstable Urgency: medium Maintainer: Bareos Packaging Team pkg-bareos-de...@lists.alioth.debian.org Changed-By: Evgeni Golov evg...@debian.org Description: bareos - Backup Archiving Recovery Open Sourced - metapackage bareos-bat - Backup Archiving Recovery Open Sourced - Bareos Admin Tool (BAT) bareos-bconsole - Backup Archiving Recovery Open Sourced - text console bareos-client - Backup Archiving Recovery Open Sourced - client metapackage bareos-common - Backup Archiving Recovery Open Sourced - common files bareos-database-common - Backup Archiving Recovery Open Sourced - common catalog files bareos-database-mysql - Backup Archiving Recovery Open Sourced - MySQL backend bareos-database-postgresql - Backup Archiving Recovery Open Sourced -
Bug#767931: marked as done (fusionforge-plugin-foafprofiles: fails to install: PHP Fatal error: require_once(): Failed opening required 'arc/ARC2.php')
Your message dated Tue, 04 Nov 2014 16:05:50 + with message-id e1xlgca-0003u7...@franck.debian.org and subject line Bug#767931: fixed in fusionforge 5.3.2+20141104-1 has caused the Debian Bug report #767931, regarding fusionforge-plugin-foafprofiles: fails to install: PHP Fatal error: require_once(): Failed opening required 'arc/ARC2.php' 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 this message is talking about, this may indicate a serious mail system misconfiguration somewhere. Please contact ow...@bugs.debian.org immediately.) -- 767931: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=767931 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems ---BeginMessage--- Package: fusionforge-plugin-foafprofiles Version: 5.3.2-1 Severity: serious User: debian...@lists.debian.org Usertags: piuparts Hi, during a test with piuparts I noticed your package failed to install. As per definition of the release team this makes the package too buggy for a release, thus the severity. From the attached log (scroll to the bottom...): Setting up fusionforge-plugin-foafprofiles (5.3.2-1) ... Entering upgrade-db.php PHP Warning: require_once(arc/ARC2.php): failed to open stream: No such file or directory in /usr/share/gforge/common/include/rdfutils.php on line 23 PHP Fatal error: require_once(): Failed opening required 'arc/ARC2.php' (include_path='/usr/share/php-htmlpurifier/library:/etc/fusionforge//custom:/etc/fusionforge/:/usr/share/gforge/common:/usr/share/gforge/www:/usr/share/gforge/plugins:/usr/share/gforge:/usr/share/gforge/www/include:/usr/share/gforge/common/include:.:/usr/share/php:/usr/share/pear') in /usr/share/gforge/common/include/rdfutils.php on line 23 dpkg: error processing package fusionforge-plugin-foafprofiles (--configure): subprocess installed post-installation script returned error exit status 255 Processing triggers for libc-bin (2.19-11) ... Errors were encountered while processing: fusionforge-plugin-foafprofiles cheers, Andreas fusionforge-plugin-foafprofiles_5.3.2-1.log.gz Description: application/gzip ---End Message--- ---BeginMessage--- Source: fusionforge Source-Version: 5.3.2+20141104-1 We believe that the bug you reported is fixed in the latest version of fusionforge, which is due to be installed in the Debian FTP archive. 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 767...@bugs.debian.org, and the maintainer will reopen the bug report if appropriate. Debian distribution maintenance software pp. Sylvain Beucler b...@debian.org (supplier of updated fusionforge 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 ftpmas...@ftp-master.debian.org) -BEGIN PGP SIGNED MESSAGE- Hash: SHA1 Format: 1.8 Date: Tue, 04 Nov 2014 11:44:47 +0100 Source: fusionforge Binary: fusionforge-standard fusionforge-minimal fusionforge-full gforge gforge-common gforge-web-apache2 gforge-web-apache2-vhosts gforge-db-postgresql gforge-db-remote gforge-mta-exim4 gforge-mta-postfix gforge-shell-postgresql gforge-ftp-proftpd gforge-dns-bind9 gforge-lists-mailman fusionforge-plugin-admssw fusionforge-plugin-authcas fusionforge-plugin-authhttpd fusionforge-plugin-authldap fusionforge-plugin-blocks fusionforge-plugin-compactpreview fusionforge-plugin-contribtracker fusionforge-plugin-doaprdf fusionforge-plugin-extsubproj fusionforge-plugin-foafprofiles fusionforge-plugin-globalsearch fusionforge-plugin-gravatar fusionforge-plugin-headermenu fusionforge-plugin-hudson fusionforge-plugin-mediawiki fusionforge-plugin-message fusionforge-plugin-moinmoin fusionforge-plugin-projectlabels fusionforge-plugin-scmarch fusionforge-plugin-scmbzr fusionforge-plugin-scmcvs fusionforge-plugin-scmdarcs fusionforge-plugin-scmgit fusionforge-plugin-scmhg fusionforge-plugin-scmhook fusionforge-plugin-scmsvn fusionforge-plugin-sysauthldap Architecture: source all Version: 5.3.2+20141104-1 Distribution: unstable Urgency: medium Maintainer: Roland Mas lola...@debian.org Changed-By: Sylvain Beucler b...@debian.org Description: fusionforge-full - FusionForge collaborative development tool - full metapackage fusionforge-minimal - FusionForge collaborative development tool - minimal metapackage fusionforge-plugin-admssw - collaborative development tool - ADMS.SW plugin fusionforge-plugin-authcas - collaborative development tool - CAS authentication plugin fusionforge-plugin-authhttpd - collaborative development tool - HTTPD authentication plugin fusionforge-plugin
Bug#767688: marked as done (gforge-web-apache2: directory vs. symlink conflict: /etc/gforge)
Your message dated Tue, 04 Nov 2014 16:05:50 + with message-id e1xlgca-0003u1...@franck.debian.org and subject line Bug#767688: fixed in fusionforge 5.3.2+20141104-1 has caused the Debian Bug report #767688, regarding gforge-web-apache2: directory vs. symlink conflict: /etc/gforge 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 this message is talking about, this may indicate a serious mail system misconfiguration somewhere. Please contact ow...@bugs.debian.org immediately.) -- 767688: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=767688 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems ---BeginMessage--- Package: gforge-web-apache2 Version: 5.3.2-1 Severity: serious User: debian...@lists.debian.org Usertags: piuparts Hi, during a test with piuparts I noticed your package installs files over an existing symlink shipped or created by another package. Your package ships: /etc/gforge/custom/index_std.php but package ??? ships: /etc/??? cannot investigate in detail since someone broke php-htmlpurifier probably /etc/gforge - fusionforge or /etc/gforge/custom - ../fusionforge/custom Installing something over existing symlinks is considered bad practice. See e.g. http://lists.debian.org/87ehlevcrf@windlord.stanford.edu It may break in subtle ways and dpkg cannot detect this as a problem. * Your package might silently overwrite files installed at the symlink destination by other packages. * If the package shipping the symlink decides to make the link point somewhere else (or turn it into a real directory), the files owned by your package will be lost somewhere in the filesystem. * Depending on installation order the problematic path will be created either as a symlink or a directory: the package installed first will win and all others have lost. Note that dpkg intentionally does not replace directories with symlinks and vice versa, see in particular the end of point 4 in http://www.debian.org/doc/debian-policy/ch-maintainerscripts.html#s-unpackphase (Note: Adding Pre-Depends is *not* a solution.) Please move the files shipped in your package to the real location. From the attached log (usually somewhere in the middle...): 1m19.0s INFO: dirname part contains a symlink: /etc/gforge/custom/index_std.php (gforge-web-apache2) != /etc/fusionforge/custom/index_std.php (?) And at the end, the shipped conffile is not cleaned up since the symlink is already gone, making the file unreachable: 1m33.6s INFO: Warning: Package purging left files on system: /etc/fusionforge/custom/index_std.php not owned /etc/systemd/system/postgresql.service - /dev/nullnot owned /var/lib/systemd/deb-systemd-helper-masked/not owned /var/lib/systemd/deb-systemd-helper-masked/postgresql.service not owned (leaving the systemd stuff is another problem I haven't investigated so far) cheers, Andreas gforge-web-apache2_5.3.2-1.log.gz Description: application/gzip ---End Message--- ---BeginMessage--- Source: fusionforge Source-Version: 5.3.2+20141104-1 We believe that the bug you reported is fixed in the latest version of fusionforge, which is due to be installed in the Debian FTP archive. 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 767...@bugs.debian.org, and the maintainer will reopen the bug report if appropriate. Debian distribution maintenance software pp. Sylvain Beucler b...@debian.org (supplier of updated fusionforge 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 ftpmas...@ftp-master.debian.org) -BEGIN PGP SIGNED MESSAGE- Hash: SHA1 Format: 1.8 Date: Tue, 04 Nov 2014 11:44:47 +0100 Source: fusionforge Binary: fusionforge-standard fusionforge-minimal fusionforge-full gforge gforge-common gforge-web-apache2 gforge-web-apache2-vhosts gforge-db-postgresql gforge-db-remote gforge-mta-exim4 gforge-mta-postfix gforge-shell-postgresql gforge-ftp-proftpd gforge-dns-bind9 gforge-lists-mailman fusionforge-plugin-admssw fusionforge-plugin-authcas fusionforge-plugin-authhttpd fusionforge-plugin-authldap fusionforge-plugin-blocks fusionforge-plugin-compactpreview fusionforge-plugin-contribtracker fusionforge-plugin-doaprdf fusionforge-plugin-extsubproj fusionforge-plugin-foafprofiles fusionforge-plugin-globalsearch fusionforge-plugin-gravatar fusionforge-plugin-headermenu fusionforge-plugin-hudson fusionforge-plugin-mediawiki fusionforge-plugin-message fusionforge-plugin-moinmoin fusionforge-plugin-projectlabels fusionforge-plugin
Bug#764355: marked as done (targetcli: Fails to load or save any config on Jessie)
Your message dated Tue, 04 Nov 2014 16:06:48 + with message-id e1xlgd6-0003r8...@franck.debian.org and subject line Bug#764355: fixed in rtslib 3.0+git0.86e46bc6-4 has caused the Debian Bug report #764355, regarding targetcli: Fails to load or save any config on Jessie 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 this message is talking about, this may indicate a serious mail system misconfiguration somewhere. Please contact ow...@bugs.debian.org immediately.) -- 764355: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=764355 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems ---BeginMessage--- Package: targetcli Version: 3.0+git0.7e32595e-2 Severity: grave Justification: renders package unusable Having tried on two systems (one fresh install netboot system), and I really can't get this package to do anything at all: . Give useless error message if kernel modules aren't loaded: This RTSRoot does not exist in configFS. . Fails to save an empty config ( #FIXME ) . Fails to create any usable export config, even for a file backed I/O: / ls o- / . [...] o- backstores .. [...] | o- fileio [0 Storage Object] | o- iblock [0 Storage Object] | o- pscsi . [0 Storage Object] | o- rd_mcp [0 Storage Object] o- ib_srpt ... [0 Targets] o- iscsi . [0 Targets] o- loopback .. [0 Targets] o- qla2xxx ... [0 Targets] o- tcm_fc [0 Targets] o- vhost . [0 Targets] / /backstores/fileio /backstores/fileio create test /home/testfile 100m Generating a wwn serial. Using buffered mode. Created fileio test. /backstores/fileio cd / / saveconfig WARNING: Saving ermintrude current configuration to disk will overwrite your boot settings. The current target configuration will become the default boot config. Are you sure? Type 'yes': yes Saving new startup configuration Traceback (most recent call last): File /usr/lib/python2.7/dist-packages/configshell/shell.py, line 990, in run_interactive self._cli_loop() File /usr/lib/python2.7/dist-packages/configshell/shell.py, line 820, in _cli_loop self.run_cmdline(cmdline) File /usr/lib/python2.7/dist-packages/configshell/shell.py, line 934, in run_cmdline self._execute_command(path, command, pparams, kparams) File /usr/lib/python2.7/dist-packages/configshell/shell.py, line 909, in _execute_command result = target.execute_command(command, pparams, kparams) File /usr/lib/python2.7/dist-packages/targetcli/ui_node.py, line 103, in execute_command pparams, kparams) File /usr/lib/python2.7/dist-packages/configshell/node.py, line 1416, in execute_command result = method(*pparams, **kparams) File /usr/lib/python2.7/dist-packages/targetcli/ui_root.py, line 68, in ui_command_saveconfig CliConfig.save_running_config() File /usr/lib/python2.7/dist-packages/targetcli/cli_config.py, line 65, in save_running_config config.load_live() File /usr/lib/python2.7/dist-packages/rtslib/config.py, line 562, in load_live source=source, allow_new_attrs=True) File /usr/lib/python2.7/dist-packages/rtslib/config.py, line 190, in _load_parse_tree token = self.validate_obj(token, cur) File /usr/lib/python2.7/dist-packages/rtslib/config.py, line 385, in validate_obj raise ConfigError(Unknown object type: %s % obj_type) ConfigError: Unknown object type: storage / Same problem on previous 3.14 kernel and on both machines. It seems strange that this managed to get through testing in this state, as it currently seems completely unusuable. -- System Information: Debian Release: jessie/sid APT prefers testing APT policy: (500, 'testing') Architecture: amd64 (x86_64) Foreign Architectures: i386 Kernel: Linux 3.16-2-amd64 (SMP w/8 CPU cores) Locale: LANG=en_GB.UTF-8, LC_CTYPE=en_GB.UTF-8 (charmap=UTF-8) Shell: /bin/sh linked to /bin/dash Versions of packages targetcli depends on: ii python 2.7.8-1 ii python-configshell 1.5+git0.0827baa6-2 ii python-rtslib 3.0+git0.86e46bc6-2 targetcli recommends no packages. targetcli suggests no packages. -- debconf-show failed ---End Message--- ---BeginMessage--- Source: rtslib Source-Version: 3.0+git0.86e46bc6-4 We believe that the bug you reported is fixed in the latest version of rtslib, which is due to be installed in the Debian FTP archive. A summary of the changes between this version and the previous one is attached. Thank you for reporting the bug,
Bug#764162: [karl.bel...@gmail.com: Re: [PATCH 0/1] mv643xx_eth: Disable TSO by default]
Hi,
I think this patch fixes this bug, if someone can try it.
Karl
- Forwarded message from Karl Beldan karl.bel...@gmail.com -
Date: Tue, 4 Nov 2014 15:20:20 +0100
From: Karl Beldan karl.bel...@gmail.com
To: Ezequiel Garcia ezequiel.gar...@free-electrons.com
Cc: net...@vger.kernel.org, David Miller da...@davemloft.net, Thomas
Petazzoni thomas.petazz...@free-electrons.com, Gregory
Clement gregory.clem...@free-electrons.com, Tawfik Bayouk
taw...@marvell.com, Lior Amsalem al...@marvell.com, Nadav
Haklai nad...@marvell.com
Subject: Re: [PATCH 0/1] mv643xx_eth: Disable TSO by default
User-Agent: Mutt/1.5.23 (2014-03-12)
On Sat, Nov 01, 2014 at 12:30:19PM -0300, Ezequiel Garcia wrote:
Several users ([1], [2]) have been reporting data corruption with TSO on
Kirkwood platforms (i.e. using the mv643xx_eth driver).
Until we manage to find what's causing this, this simple patch will make
the TSO path disabled by default. This patch should be queued for stable,
fixing the TSO feature introduced in v3.16.
The corruption itself is very easy to reproduce: checking md5sum on a mounted
NFS directory gives a different result each time. Same tests using the mvneta
driver (Armada 370/38x/XP SoC) pass with no issues.
Frankly, I'm a bit puzzled about this, and so any ideas or debugging hints
are well received.
Hi,
Can you try this :
@@ -1067,7 +1082,8 @@ static int txq_reclaim(struct tx_queue *txq, int budget,
int force)
txq-tx_desc_count--;
skb = NULL;
- if (cmd_sts TX_LAST_DESC)
+ if ((cmd_sts (TX_LAST_DESC | TX_ENABLE_INTERRUPT)) ==
+ (TX_LAST_DESC | TX_ENABLE_INTERRUPT))
skb = __skb_dequeue(txq-tx_skb);
if (cmd_sts ERROR_SUMMARY) {
--
Karl
- End forwarded message -
--
To UNSUBSCRIBE, email to debian-bugs-rc-requ...@lists.debian.org
with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#764340: marked as done (targetcli: On new install exit or configure etc. fail due to missing /var/target/policy)
Your message dated Tue, 04 Nov 2014 16:06:48 + with message-id e1xlgd6-0003r8...@franck.debian.org and subject line Bug#764355: fixed in rtslib 3.0+git0.86e46bc6-4 has caused the Debian Bug report #764355, regarding targetcli: On new install exit or configure etc. fail due to missing /var/target/policy 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 this message is talking about, this may indicate a serious mail system misconfiguration somewhere. Please contact ow...@bugs.debian.org immediately.) -- 764355: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=764355 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems ---BeginMessage--- Package: targetcli Version: 3.0+git0.7e32595e-2 Severity: important On a new install, on Jessie: root@ermintrude:/home/tim/Downloads# targetcli targetcli GIT_VERSION (rtslib GIT_VERSION) Copyright (c) 2011-2014 by Datera, Inc. All rights reserved. /backstores/iblock/win7 exit Traceback (most recent call last): File /usr/lib/python2.7/dist-packages/configshell/shell.py, line 990, in run_interactive self._cli_loop() File /usr/lib/python2.7/dist-packages/configshell/shell.py, line 820, in _cli_loop self.run_cmdline(cmdline) File /usr/lib/python2.7/dist-packages/configshell/shell.py, line 934, in run_cmdline self._execute_command(path, command, pparams, kparams) File /usr/lib/python2.7/dist-packages/configshell/shell.py, line 909, in _execute_command result = target.execute_command(command, pparams, kparams) File /usr/lib/python2.7/dist-packages/targetcli/ui_node.py, line 216, in execute_command return UINode.execute_command(self, command, pparams, kparams) File /usr/lib/python2.7/dist-packages/targetcli/ui_node.py, line 103, in execute_command pparams, kparams) File /usr/lib/python2.7/dist-packages/configshell/node.py, line 1416, in execute_command result = method(*pparams, **kparams) File /usr/lib/python2.7/dist-packages/targetcli/ui_node.py, line 115, in ui_command_exit config = Config() File /usr/lib/python2.7/dist-packages/rtslib/config.py, line 133, in __init__ self._load_policy() File /usr/lib/python2.7/dist-packages/rtslib/config.py, line 140, in _load_policy for path in os.listdir(self.policy_dir) OSError: [Errno 2] No such file or directory: '/var/target/policy' /backstores/iblock/win7 Quit -- System Information: Debian Release: jessie/sid APT prefers testing APT policy: (500, 'testing') Architecture: amd64 (x86_64) Foreign Architectures: i386 Kernel: Linux 3.14-2-amd64 (SMP w/8 CPU cores) Locale: LANG=en_GB.UTF-8, LC_CTYPE=en_GB.UTF-8 (charmap=UTF-8) Shell: /bin/sh linked to /bin/dash Versions of packages targetcli depends on: ii python 2.7.8-1 ii python-configshell 1.5+git0.0827baa6-2 ii python-rtslib 3.0+git0.86e46bc6-2 targetcli recommends no packages. targetcli suggests no packages. -- no debconf information ---End Message--- ---BeginMessage--- Source: rtslib Source-Version: 3.0+git0.86e46bc6-4 We believe that the bug you reported is fixed in the latest version of rtslib, which is due to be installed in the Debian FTP archive. 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 764...@bugs.debian.org, and the maintainer will reopen the bug report if appropriate. Debian distribution maintenance software pp. Ritesh Raj Sarraf r...@debian.org (supplier of updated rtslib 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 ftpmas...@ftp-master.debian.org) -BEGIN PGP SIGNED MESSAGE- Hash: SHA1 Format: 1.8 Date: Tue, 04 Nov 2014 20:52:09 +0530 Source: rtslib Binary: python-rtslib Architecture: source all Version: 3.0+git0.86e46bc6-4 Distribution: unstable Urgency: medium Maintainer: Ritesh Raj Sarraf r...@debian.org Changed-By: Ritesh Raj Sarraf r...@debian.org Description: python-rtslib - LIO core target management framework - Python libs Closes: 764355 Changes: rtslib (3.0+git0.86e46bc6-4) unstable; urgency=medium . * [acc103e] Install the policy files. Thanks to Jerome Martin (Closes: #764355) * [6cb7aac] Add dh-python to build-depends Checksums-Sha1: e85e6b0f31e8ca1acd4c01779a97f937157c338d 2187 rtslib_3.0+git0.86e46bc6-4.dsc 6a7b151ee002c09b77b57ecf6d26c16683f88e87 5852 rtslib_3.0+git0.86e46bc6-4.debian.tar.xz 696ca9d5f4effe1a02da7fa857cce0645e5d200d 439380 python-rtslib_3.0+git0.86e46bc6-4_all.deb Checksums-Sha256: 0c7df720c807492bd02d3ef7981a1064045ac01562260ba2e85d94f6c5145ba5 2187 rtslib_3.0+git0.86e46bc6-4.dsc
Bug#767690: marked as done (trousers: fails to install: subprocess installed post-installation script returned error exit status 2)
Your message dated Tue, 04 Nov 2014 16:07:08 + with message-id e1xlgdq-0003yi...@franck.debian.org and subject line Bug#767690: fixed in trousers 0.3.13-3 has caused the Debian Bug report #767690, regarding trousers: fails to install: subprocess installed post-installation script returned error exit status 2 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 this message is talking about, this may indicate a serious mail system misconfiguration somewhere. Please contact ow...@bugs.debian.org immediately.) -- 767690: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=767690 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems ---BeginMessage--- Package: trousers Version: 0.3.13-2 Severity: serious User: debian...@lists.debian.org Usertags: piuparts Hi, during a test with piuparts I noticed your package failed to install. As per definition of the release team this makes the package too buggy for a release, thus the severity. From the attached log (scroll to the bottom...): Selecting previously unselected package trousers. (Reading database ... 7406 files and directories currently installed.) Preparing to unpack .../trousers_0.3.13-2_amd64.deb ... Unpacking trousers (0.3.13-2) ... Setting up trousers (0.3.13-2) ... dpkg: error processing package trousers (--configure): subprocess installed post-installation script returned error exit status 2 Errors were encountered while processing: trousers cheers, Andreas trousers.log.gz Description: application/gzip ---End Message--- ---BeginMessage--- Source: trousers Source-Version: 0.3.13-3 We believe that the bug you reported is fixed in the latest version of trousers, which is due to be installed in the Debian FTP archive. 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 767...@bugs.debian.org, and the maintainer will reopen the bug report if appropriate. Debian distribution maintenance software pp. Pierre Chifflier pol...@debian.org (supplier of updated trousers 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 ftpmas...@ftp-master.debian.org) -BEGIN PGP SIGNED MESSAGE- Hash: SHA1 Format: 1.8 Date: Tue, 04 Nov 2014 15:11:08 +0100 Source: trousers Binary: trousers trousers-dbg libtspi1 libtspi-dev Architecture: source amd64 Version: 0.3.13-3 Distribution: unstable Urgency: high Maintainer: Pierre Chifflier pol...@debian.org Changed-By: Pierre Chifflier pol...@debian.org Description: libtspi-dev - open-source TCG Software Stack (development) libtspi1 - open-source TCG Software Stack (library) trousers - open-source TCG Software Stack (daemon) trousers-dbg - open-source TCG Software Stack (debug) Closes: 767690 Changes: trousers (0.3.13-3) unstable; urgency=high . * Fix postinst script, preventing installation (Closes: #767690) - The postinst script does not fail anymore if the TPM device is not present, or if udev reload command fails. This is typically the case in a chroot environment. * Fix init script to be more robust: - Test for TPM device owner and issue a warning if not matching the tss user. - Do not try to change uid before running tcsd, the daemon already changes its uid just after starting. * Urgency high, RC bug Checksums-Sha1: 33cfc697da8d2f0c8e5c0c1e1ff6813e453c5fae 1595 trousers_0.3.13-3.dsc 92bc8b1f935a84ba5a39053cb8accf8c3cff544f 15748 trousers_0.3.13-3.debian.tar.xz 099535c19ea625224a9f401eb5e3dfdf37a6e4b3 139162 trousers_0.3.13-3_amd64.deb 028271fa81c93b946538f6459ef2a2d3e3108906 843684 trousers-dbg_0.3.13-3_amd64.deb 5553d2e7b0a74bcf1857c037ff88217281547d62 167656 libtspi1_0.3.13-3_amd64.deb ee6441dbb10e5e9025b02c6985572a2d8f145ad9 634968 libtspi-dev_0.3.13-3_amd64.deb Checksums-Sha256: 21fe09136a5d52d78ebbe681cee54387a4a8bd07cc7f82496109b6eaa9b529bb 1595 trousers_0.3.13-3.dsc 02a0c77b7273c06542b3ee8bd3c383c9b1fb7aea4679ed8091fad44d03a4b789 15748 trousers_0.3.13-3.debian.tar.xz 091243c946f05f540fcf926037c9be047c114364d264ebe09fe28ca5c40a188f 139162 trousers_0.3.13-3_amd64.deb 9cf5b63fe4565fef5b07372b5f1613106bbc8fc3ad4b5fdfd94ac50a33cd1055 843684 trousers-dbg_0.3.13-3_amd64.deb 3a18aee7857654a6272864e34639380ad3d63170111057105a22e67d2487483d 167656 libtspi1_0.3.13-3_amd64.deb 32a9b900f6c28e43ac8c030eaaeca643a333ef99de3490148f9339f2c7f5a49e 634968 libtspi-dev_0.3.13-3_amd64.deb Files: 49dfb9d20793b706048c087ce0a7f439 1595 admin optional trousers_0.3.13-3.dsc cb666fbf6e61cc9ea45654c64dfb371d 15748 admin optional
Bug#767683: marked as done (gforge-dns-bind9: fails to install: cat: /bind/dns.simple.template: No such file or directory)
Your message dated Tue, 4 Nov 2014 17:21:36 +0100 with message-id 20141104162136.ga32...@mail.beuc.net and subject line Re: gforge-dns-bind9: fails to install: cat: /bind/dns.simple.template: No such file or directory has caused the Debian Bug report #767683, regarding gforge-dns-bind9: fails to install: cat: /bind/dns.simple.template: No such file or directory 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 this message is talking about, this may indicate a serious mail system misconfiguration somewhere. Please contact ow...@bugs.debian.org immediately.) -- 767683: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=767683 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems ---BeginMessage--- Package: gforge-dns-bind9 Version: 5.3.2-1 Severity: serious User: debian...@lists.debian.org Usertags: piuparts Hi, during a test with piuparts I noticed your package failed to install. As per definition of the release team this makes the package too buggy for a release, thus the severity. From the attached log (scroll to the bottom...): Selecting previously unselected package gforge-dns-bind9. (Reading database ... 14140 files and directories currently installed.) Preparing to unpack .../gforge-dns-bind9_5.3.2-1_all.deb ... Unpacking gforge-dns-bind9 (5.3.2-1) ... Setting up gforge-dns-bind9 (5.3.2-1) ... Creating /bind/dns.zone /usr/share/gforge/bin/install-dns.sh: 1: eval: cannot create /bind/dns.zone: Directory nonexistent cat: /bind/dns.simple.template: No such file or directory dpkg: error processing package gforge-dns-bind9 (--configure): subprocess installed post-installation script returned error exit status 2 Errors were encountered while processing: gforge-dns-bind9 Also /bind/ sounds like a serious FHS violation, probably some prefix variable is empty that shouldn't. cheers, Andreas gforge-dns-bind9_5.3.2-1.log.gz Description: application/gzip ---End Message--- ---BeginMessage--- Version: 5.3.2+20141104-1---End Message---
Bug#768065: opendnssec-enforcer: lacks versioned dependency on dpkg
Package: opendnssec-enforcer Version: 1:1.4.6-2 Severity: serious Tags: patch Justification: Policy 7.2 -BEGIN PGP SIGNED MESSAGE- Hash: SHA512 Upgrade from 1:1.3.9-5 to 1:1.4.6-2 fails: dpkg-maintscript-helper: error: command symlink_to_dir is unknown Hint: upgrading dpkg to a newer version might help. - Jonas -BEGIN PGP SIGNATURE- Version: GnuPG v1 iQF8BAEBCgBmBQJUWQDvXxSAAC4AKGlzc3Vlci1mcHJAbm90YXRpb25zLm9w ZW5wZ3AuZmlmdGhob3JzZW1hbi5uZXQ3NjQ4ODQwMTIyRTJDNTBFQzUxRDQwRTI0 RUMxQjcyMjM3NEY5QkQ2AAoJEE7BtyI3T5vWKKoH/A5sO/JQFJ/156/KZHg0hQRR LjfYpZbjsufAVUXig5n2D+sxy6xTdO1NML2ZznvQWpzwSfMKXbxrfXlGQ21R6KWM eHntwarb2YGZugvUcPPoUvgeJ78N/78etcJmumRmfnv54DqxFVT+huRMCmC/H/6Y /5UmVWbIc0vi4DvTfx7VTWHGcKwebyWFJP7CyHrYQigz0zvjL6FJCZ6+ycRtuOdu RU03sjE9Pj9zJ7r+r8w1XNwTiWH6mMmj8A3hlRFVkbNxkEtkjb8uzT9/rIn+UFNJ GNpeZuvkxUU6ID/NpaukE/DLsW8kYoVqRpW6bHZ3w2RYgVDH/llfCnm2exVSlOY= =UUBK -END PGP SIGNATURE- -- To UNSUBSCRIBE, email to debian-bugs-rc-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#755340: marked as done (cython: FTBFS: Tests failures)
Your message dated Tue, 4 Nov 2014 11:47:26 -0500 with message-id 20141104164726.ga30...@onerussian.com and subject line looks like fixed in 0.21.1 has caused the Debian Bug report #755340, regarding cython: FTBFS: Tests failures 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 this message is talking about, this may indicate a serious mail system misconfiguration somewhere. Please contact ow...@bugs.debian.org immediately.) -- 755340: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=755340 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems ---BeginMessage--- Source: cython Version: 0.20.2-1 Severity: serious Tags: jessie sid User: debian...@lists.debian.org Usertags: qa-ftbfs-20140718 qa-ftbfs Justification: FTBFS on amd64 Hi, During a rebuild of all packages in sid, your package failed to build on amd64. Relevant part (hopefully): == ERROR: test_all (Cython.Debugger.Tests.TestLibCython.TestAll) -- Traceback (most recent call last): File /«PKGBUILDDIR»/Cython/Debugger/Tests/TestLibCython.py, line 281, in test_all sys.stderr.write(errmsg) UnicodeEncodeError: 'ascii' codec can't encode characters in position 21072-21075: ordinal not in range(128) -- Ran 8339 tests in 2258.934s FAILED (errors=1) ALL DONE make[1]: *** [override_dh_auto_test] Error 1 The full build log is available from: http://aws-logs.debian.net/ftbfs-logs/2014/07/18/cython_0.20.2-1_unstable.log A list of current common problems and possible solutions is available at http://wiki.debian.org/qa.debian.org/FTBFS . You're welcome to contribute! About the archive rebuild: The rebuild was done on EC2 VM instances from Amazon Web Services, using a clean, minimal and up-to-date chroot. Every failed build was retried once to eliminate random failures. ---End Message--- ---BeginMessage--- Version: 0.21.1-1 I did manage to replicate such an issue before on some builds: $ grep codec can't encode characters in position 0.2*/*build 0.20.1+git90-g0e6e38e-1/cython_0.20.1+git90-g0e6e38e-1~nd70+1_i386.build:UnicodeEncodeError: 'ascii' codec can't encode characters in position 19661-19664: ordinal not in range(128) 0.20.2-1/cython_0.20.2-1~nd70+1_i386.build:UnicodeEncodeError: 'ascii' codec can't encode characters in position 18851-18854: ordinal not in range(128) 0.20.2+git216-ga96882e-1/cython_0.20.2+git216-ga96882e-1~nd70+1_i386.build:UnicodeEncodeError: 'ascii' codec can't encode characters in position 21001-21004: ordinal not in range(128) but as you can see there were no hit in 0.21.1-1 so closing Please reopen if it strikes back -- Yaroslav O. Halchenko, Ph.D. http://neuro.debian.net http://www.pymvpa.org http://www.fail2ban.org Research Scientist,Psychological and Brain Sciences Dept. Dartmouth College, 419 Moore Hall, Hinman Box 6207, Hanover, NH 03755 Phone: +1 (603) 646-9834 Fax: +1 (603) 646-1419 WWW: http://www.linkedin.com/in/yarik---End Message---
Bug#768065: marked as done (opendnssec-enforcer: lacks versioned dependency on dpkg)
Your message dated Tue, 04 Nov 2014 17:19:21 + with message-id e1xlhlj-0005fz...@franck.debian.org and subject line Bug#768065: fixed in opendnssec 1:1.4.6-3 has caused the Debian Bug report #768065, regarding opendnssec-enforcer: lacks versioned dependency on dpkg 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 this message is talking about, this may indicate a serious mail system misconfiguration somewhere. Please contact ow...@bugs.debian.org immediately.) -- 768065: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=768065 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems ---BeginMessage--- Package: opendnssec-enforcer Version: 1:1.4.6-2 Severity: serious Tags: patch Justification: Policy 7.2 -BEGIN PGP SIGNED MESSAGE- Hash: SHA512 Upgrade from 1:1.3.9-5 to 1:1.4.6-2 fails: dpkg-maintscript-helper: error: command symlink_to_dir is unknown Hint: upgrading dpkg to a newer version might help. - Jonas -BEGIN PGP SIGNATURE- Version: GnuPG v1 iQF8BAEBCgBmBQJUWQDvXxSAAC4AKGlzc3Vlci1mcHJAbm90YXRpb25zLm9w ZW5wZ3AuZmlmdGhob3JzZW1hbi5uZXQ3NjQ4ODQwMTIyRTJDNTBFQzUxRDQwRTI0 RUMxQjcyMjM3NEY5QkQ2AAoJEE7BtyI3T5vWKKoH/A5sO/JQFJ/156/KZHg0hQRR LjfYpZbjsufAVUXig5n2D+sxy6xTdO1NML2ZznvQWpzwSfMKXbxrfXlGQ21R6KWM eHntwarb2YGZugvUcPPoUvgeJ78N/78etcJmumRmfnv54DqxFVT+huRMCmC/H/6Y /5UmVWbIc0vi4DvTfx7VTWHGcKwebyWFJP7CyHrYQigz0zvjL6FJCZ6+ycRtuOdu RU03sjE9Pj9zJ7r+r8w1XNwTiWH6mMmj8A3hlRFVkbNxkEtkjb8uzT9/rIn+UFNJ GNpeZuvkxUU6ID/NpaukE/DLsW8kYoVqRpW6bHZ3w2RYgVDH/llfCnm2exVSlOY= =UUBK -END PGP SIGNATURE- ---End Message--- ---BeginMessage--- Source: opendnssec Source-Version: 1:1.4.6-3 We believe that the bug you reported is fixed in the latest version of opendnssec, which is due to be installed in the Debian FTP archive. 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 768...@bugs.debian.org, and the maintainer will reopen the bug report if appropriate. Debian distribution maintenance software pp. Ondřej Surý ond...@debian.org (supplier of updated opendnssec 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 ftpmas...@ftp-master.debian.org) -BEGIN PGP SIGNED MESSAGE- Hash: SHA512 Format: 1.8 Date: Tue, 04 Nov 2014 17:38:09 +0100 Source: opendnssec Binary: opendnssec-common opendnssec opendnssec-doc opendnssec-enforcer opendnssec-enforcer-mysql opendnssec-enforcer-sqlite3 opendnssec-signer libhsm-bin opendnssec-dbg-mysql opendnssec-dbg-sqlite3 Architecture: source all Version: 1:1.4.6-3 Distribution: unstable Urgency: medium Maintainer: Ondřej Surý ond...@debian.org Changed-By: Ondřej Surý ond...@debian.org Description: libhsm-bin - library for interfacing PKCS#11 Hardware Security Modules opendnssec - dependency package to install full OpenDNSSEC suite opendnssec-common - common configuration files for OpenDNSSEC suite opendnssec-dbg-mysql - Debug symbols for OpenDNSSEC (Enforcer with MySQL support) opendnssec-dbg-sqlite3 - Debug symbols for OpenDNSSEC (Enforcer with SQLite3 support) opendnssec-doc - documentation for OpenDNSSEC suite opendnssec-enforcer - tool to prepare DNSSEC keys (common package) opendnssec-enforcer-mysql - tool to prepare DNSSEC keys (mysql backend) opendnssec-enforcer-sqlite3 - tool to prepare DNSSEC keys (sqlite3 backend) opendnssec-signer - daemon to sign DNS zone files periodically Closes: 768065 Changes: opendnssec (1:1.4.6-3) unstable; urgency=medium . * Add Pre-Depends: dpkg (= 1.17.5) for dpkg-maintscript-helper (Closes: #768065) Checksums-Sha1: 8781bfbe47f8d12b732523e2319e655e61f5391b 2816 opendnssec_1.4.6-3.dsc 767ce6735b883c38266a7747a5b5e2ea25a1c610 16784 opendnssec_1.4.6-3.debian.tar.xz e67ac46195b21a3b6588be397f18243ccd73d75a 50182 opendnssec-common_1.4.6-3_all.deb 9219c1ac87b3b558179a0eda2c10e4fae81a 28290 opendnssec_1.4.6-3_all.deb e8f6ee27533b3fca15b441b12d2b5043ab775292 58883836 opendnssec-doc_1.4.6-3_all.deb 63d2c8b6d88549e50eea31399ae3e66b57156c86 29862 opendnssec-enforcer_1.4.6-3_all.deb Checksums-Sha256: c391e0d6c295c3bf2d70a5db12fac60d7b85f35506a2bee2226f2a78d397329c 2816 opendnssec_1.4.6-3.dsc ef6c702b83beac25ac241efe92a1e967e12ebb0286dfb907f50cd6d42749e6e4 16784 opendnssec_1.4.6-3.debian.tar.xz a06995d89a79661c8deff28fdc8f8da7ed82989181457352068b8f57ec11a20c 50182 opendnssec-common_1.4.6-3_all.deb 6d752f1cffbd02895f2df51c09ec161f9c406ceb5d4decbb7d31611b57403781 28290 opendnssec_1.4.6-3_all.deb e2cf6ff757863677897355f947b931dfa6db75d6f597b38615ed139d7f5100bb 58883836
Processed: tagging 767817
Processing commands for cont...@bugs.debian.org: tags 767817 + confirmed Bug #767817 [dhcpy6d] dhcpy6d: modifies conffiles (policy 10.7.3): /etc/default/dhcpy6d Added tag(s) confirmed. thanks Stopping processing here. Please contact me if you need assistance. -- 767817: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=767817 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems -- To UNSUBSCRIBE, email to debian-bugs-rc-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#768025: marked as done (systemd-logind: default configuration breaks any existing ACPI button handling)
Your message dated Tue, 04 Nov 2014 18:33:07 +0100
with message-id 54590dd3.4040...@debian.org
and subject line Re: Bug#768025: systemd-logind: default configuration breaks
any existing ACPI button handling
has caused the Debian Bug report #768025,
regarding systemd-logind: default configuration breaks any existing ACPI button
handling
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 this
message is talking about, this may indicate a serious mail system
misconfiguration somewhere. Please contact ow...@bugs.debian.org
immediately.)
--
768025: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=768025
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
---BeginMessage---
Package: systemd
Version: 215-5+b1
Severity: critical
Justification: breaks unrelated software
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
systemd-logind breaks acpid by default.
Merely installing systemd with default configuration causes it to start
handling the PowerKey, LidSwitch, HibernateKey and SuspendKey without
considering existing acpid configuration. This completely breaks those
events to break due to the double handling (pressing either of these
buttons two times does not give the desired result).
acpid and systemd are unrelated according to dependencies. The breakage
is therefore unexpected.
Note that this bug affects systems using sysvinit as well. systemd is
dragged in by policykit, and systemd-logind will be started by dbus on
request regardless of the init system being used.
Bjørn
- -- Package-specific info:
- -- System Information:
Debian Release: jessie/sid
APT prefers testing
APT policy: (990, 'testing'), (600, 'unstable'), (500, 'testing-updates'),
(1, 'experimental')
Architecture: amd64 (x86_64)
Foreign Architectures: i386
Kernel: Linux 3.18.0-rc3 (SMP w/2 CPU cores)
Locale: LANG=en_US.UTF-8, LC_CTYPE=en_US.UTF-8 (charmap=UTF-8)
Shell: /bin/sh linked to /bin/dash
Versions of packages systemd depends on:
ii acl 2.2.52-2
ii adduser 3.113+nmu3
ii initscripts 2.88dsf-53.4
ii libacl1 2.2.52-2
ii libaudit1 1:2.4-1
ii libblkid1 2.25.2-2
ii libc6 2.19-12
ii libcap2 1:2.24-6
ii libcap2-bin 1:2.24-6
ii libcryptsetup4 2:1.6.6-3
ii libgcrypt20 1.6.2-4
ii libkmod218-3
ii liblzma55.1.1alpha+20120614-2
ii libpam0g1.1.8-3.1
ii libselinux1 2.3-2
ii libsystemd0 215-5+b1
ii sysv-rc 2.88dsf-53.4
ii udev215-5+b1
ii util-linux 2.25.2-2
Versions of packages systemd recommends:
ii dbus1.8.8-2
ii libpam-systemd 215-5+b1
Versions of packages systemd suggests:
pn systemd-ui none
- -- Configuration Files:
/etc/systemd/logind.conf changed:
[Login]
HandlePowerKey=ignore
HandleSuspendKey=ignore
HandleHibernateKey=ignore
HandleLidSwitch=ignore
- -- no debconf information
-BEGIN PGP SIGNATURE-
Version: GnuPG v1
iEYEARECAAYFAlRYoZYACgkQ10rqkowbIskBEACdGQyrci0zI+0RV4QkbP/5H7M1
wXEAnj7CqasQJWzW+C1BqUwPv+sHJ8e5
=sFS0
-END PGP SIGNATURE-
[OVERRIDDEN] /etc/udev/rules.d/40-usb_modeswitch.rules - /lib/udev/rules.d/40-usb_modeswitch.rules
--- /lib/udev/rules.d/40-usb_modeswitch.rules 2014-06-09 11:21:49.0 +0200
+++ /etc/udev/rules.d/40-usb_modeswitch.rules 2012-11-10 21:18:02.0 +0100
@@ -1,12 +1,13 @@
-# Part of usb-modeswitch-data, version 20140529
+# Part of usb-modeswitch-data, version 20121109
#
-# Works with usb_modeswitch versions = 2.2.0 (introduction of HuaweiNewMode)
+# Recommended use with USB_ModeSwitch = 1.2.5, works with versions = 1.0.3
+# (New style, interface class check moved to dispatcher)
#
ACTION!=add|change, GOTO=modeswitch_rules_end
# Adds a symlink gsmmodem[n] to the lowest ttyUSB port with interrupt
# transfer; checked against a list of known modems, or else no action
-KERNEL==ttyUSB*, ATTRS{bNumConfigurations}==*, PROGRAM=usb_modeswitch --symlink-name %p %s{idVendor} %s{idProduct} %E{PRODUCT}, SYMLINK+=%c
+KERNEL==ttyUSB*, ATTRS{bNumConfigurations}==*, PROGRAM=usb_modeswitch --symlink-name %p %s{idVendor} %s{idProduct} %E{PRODUCT}, SYMLINK=%c
SUBSYSTEM!=usb, GOTO=modeswitch_rules_end
@@ -20,36 +21,18 @@
ACTION!=add, GOTO=modeswitch_rules_end
-# Generic entry for all Huawei devices
-ATTRS{idVendor}==12d1, ATTR{bInterfaceNumber}==00, ATTR{bInterfaceClass}==08, RUN+=usb_modeswitch '%b/%k'
-
# HP LaserJet Professional P1102
ATTR{idVendor}==03f0, ATTR{idProduct}==002a, RUN+=usb_modeswitch '%b/%k'
-# Quanta 1KR / USB-lte 7410
-ATTR{idVendor}==0408, ATTR{idProduct}==ea17, RUN+=usb_modeswitch '%b/%k'
-
-# Quanta 1K3 LTE
-ATTR{idVendor}==0408, ATTR{idProduct}==ea25, RUN+=usb_modeswitch '%b/%k'
-
-# Quanta MobileGenie 4G lte
-ATTR{idVendor}==0408,
Bug#768014: libgnutls-dev: not installable in sid
On 2014-11-04 Ralf Treinen trei...@pps.univ-paris-diderot.fr wrote: Package: libgnutls-dev Version: 2.12.23-17 Severity: serious User: trei...@debian.org Usertags: edos-uninstallable Hi, libgnutls-dev is not installable in sid since 2014-09-29. The reason is that it depends on libgcrypt11-dev (= 1.4.0), and the current version of libgcrypt11-dev in sid (1.5.4-3+really1.6.2-4) declares: Breaks: libgnutls-dev ( 2.12.23-18) That is known, and by intention. gnutls26 has already been removed from testing and is scheduled for removal from sid and experimental. https://bugs.debian.org/767610 cu Andreas -- `What a good friend you are to him, Dr. Maturin. His other friends are so grateful to you.' `I sew his ears on from time to time, sure' -- To UNSUBSCRIBE, email to debian-bugs-rc-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#766114: [pkg-fso-maint] Bug#766114: fso-deviced: uninstallable in i386/amd64/armhf
Am Dienstag, 21. Oktober 2014, 00:33:51 schrieb hikaru: apt-get install fso-deviced * What was the outcome of this action? # apt-get install fso-deviced Reading package lists... Done Building dependency tree Reading state information... Done Recommended packages: fso-deviced-platform The following NEW packages will be installed: fso-deviced Please try to install the fso-deviced-n900 package too. Rico signature.asc Description: This is a digitally signed message part.
Processed: Re: Bug#767075: pidgin-otr: Needs to Depend: libotr5 (= 4.1.0)
Processing control commands: severity -1 important Bug #767075 [pidgin-otr] pidgin-otr: Needs to Depend: libotr5 (= 4.1.0) Severity set to 'important' from 'serious' -- 767075: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=767075 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems -- To UNSUBSCRIBE, email to debian-bugs-rc-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#768054: fp-units-multimedia: Upgrade fail from wheezy to jessie (versioned dependency on fp-units-multimedia-2.6.0)
Control: tags -1 moreinfo On 04-11-14 15:23, Petter Reinholdtsen wrote: The following packages have unmet dependencies: fp-units-multimedia : Depends: fp-units-multimedia-2.6.0 (= 2.6.0-9) but it is not going to be installed fp-units-multimedia in jessie depends on fp-units-multimedia-2.6.4. Where does this dependency come from as this is the dependency in wheezy? fpc-2.6.0 : Depends: fp-units-multimedia-2.6.0 (= 2.6.0-9) but it is not going to be installed fpc-2.6.0 should get removed during an upgrade. Why is it not removed? Do you directly depend on it somewhere? Can you please help me to read the log? If you just upgrade fpc (wheezy) to fpc (jessie) the above should not happen with the dependencies in both releases, so you must be trying to force something that isn't supported, or the resolvers have issues. Paul signature.asc Description: OpenPGP digital signature
Processed: Re: Bug#768054: fp-units-multimedia: Upgrade fail from wheezy to jessie (versioned dependency on fp-units-multimedia-2.6.0)
Processing control commands: tags -1 moreinfo Bug #768054 [fp-units-multimedia] fp-units-multimedia: Upgrade fail from wheezy to jessie (versioned dependency on fp-units-multimedia-2.6.0) Added tag(s) moreinfo. -- 768054: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=768054 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems -- To UNSUBSCRIBE, email to debian-bugs-rc-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#767209: marked as done (bibletime: FTBFS on s390x (relocation truncated to fit))
Your message dated Tue, 04 Nov 2014 19:04:03 + with message-id e1xljod-0001oz...@franck.debian.org and subject line Bug#767209: fixed in bibletime 2.10.1-2 has caused the Debian Bug report #767209, regarding bibletime: FTBFS on s390x (relocation truncated to fit) 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 this message is talking about, this may indicate a serious mail system misconfiguration somewhere. Please contact ow...@bugs.debian.org immediately.) -- 767209: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=767209 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems ---BeginMessage--- Source: bibletime Version: 2.10.1-1 Severity: serious Justification: fails to build from source (but built successfully in the past) Hi, your package no longer builds on the s390x buildd: /usr/bin/c++ -g -O2 -fstack-protector-strong -Wformat -Werror=format-security -D_FORTIFY_SOURCE=2 -ggdb -Wl,-z,relro CMakeFiles/bibletime.dir/src/backend/btmoduletreeitem.cpp.o CMakeFiles/bibletime.dir/src/backend/cswordmodulesearch.cpp.o CMakeFiles/bibletime.dir/src/backend/btinstallbackend.cpp.o CMakeFiles/bibletime.dir/src/backend/btinstallmgr.cpp.o CMakeFiles/bibletime.dir/src/backend/btinstallthread.cpp.o CMakeFiles/bibletime.dir/src/backend/bookshelfmodel/btbookshelffiltermodel.cpp.o CMakeFiles/bibletime.dir/src/backend/bookshelfmodel/btbookshelfmodel.cpp.o CMakeFiles/bibletime.dir/src/backend/bookshelfmodel/btbookshelftreemodel.cpp.o CMakeFiles/bibletime.dir/src/backend/bookshelfmodel/categoryitem.cpp.o CMakeFiles/bibletime.dir/src/backend/bookshelfmodel/indexingitem.cpp.o CMakeFiles/bibletime.dir/src/backend/bookshelfmodel/item.cpp.o CMakeFiles/bibletime.dir/src/backend/bookshelfmodel/languageitem.cpp.o CMakeFiles/bibletime.dir/src/backend/bookshelfmodel/moduleitem.cpp.o CMakeFiles/bibletime.dir/src/backend/config/btconfig.cpp.o CMakeFiles/bibletime.dir/src/backend/config/btconfigcore.cpp.o CMakeFiles/bibletime.dir/src/backend/drivers/cswordbiblemoduleinfo.cpp.o CMakeFiles/bibletime.dir/src/backend/drivers/cswordbookmoduleinfo.cpp.o CMakeFiles/bibletime.dir/src/backend/drivers/cswordcommentarymoduleinfo.cpp.o CMakeFiles/bibletime.dir/src/backend/drivers/cswordlexiconmoduleinfo.cpp.o CMakeFiles/bibletime.dir/src/backend/drivers/cswordmoduleinfo.cpp.o CMakeFiles/bibletime.dir/src/backend/filters/gbftohtml.cpp.o CMakeFiles/bibletime.dir/src/backend/filters/osistohtml.cpp.o CMakeFiles/bibletime.dir/src/backend/filters/plaintohtml.cpp.o CMakeFiles/bibletime.dir/src/backend/filters/teitohtml.cpp.o CMakeFiles/bibletime.dir/src/backend/filters/thmltohtml.cpp.o CMakeFiles/bibletime.dir/src/backend/filters/thmltoplain.cpp.o CMakeFiles/bibletime.dir/src/backend/filters/btosismorphsegmentation.cpp.o CMakeFiles/bibletime.dir/src/backend/keys/cswordkey.cpp.o CMakeFiles/bibletime.dir/src/backend/keys/cswordldkey.cpp.o CMakeFiles/bibletime.dir/src/backend/keys/cswordtreekey.cpp.o CMakeFiles/bibletime.dir/src/backend/keys/cswordversekey.cpp.o CMakeFiles/bibletime.dir/src/backend/rendering/cbookdisplay.cpp.o CMakeFiles/bibletime.dir/src/backend/rendering/cchapterdisplay.cpp.o CMakeFiles/bibletime.dir/src/backend/rendering/cdisplayrendering.cpp.o CMakeFiles/bibletime.dir/src/backend/rendering/centrydisplay.cpp.o CMakeFiles/bibletime.dir/src/backend/rendering/chtmlexportrendering.cpp.o CMakeFiles/bibletime.dir/src/backend/rendering/cplaintextexportrendering.cpp.o CMakeFiles/bibletime.dir/src/backend/rendering/ctextrendering.cpp.o CMakeFiles/bibletime.dir/src/backend/managers/btstringmgr.cpp.o CMakeFiles/bibletime.dir/src/backend/managers/cdisplaytemplatemgr.cpp.o CMakeFiles/bibletime.dir/src/backend/managers/clanguagemgr.cpp.o CMakeFiles/bibletime.dir/src/backend/managers/cswordbackend.cpp.o CMakeFiles/bibletime.dir/src/backend/managers/referencemanager.cpp.o CMakeFiles/bibletime.dir/src/util/cresmgr.cpp.o CMakeFiles/bibletime.dir/src/util/directory.cpp.o CMakeFiles/bibletime.dir/src/util/btmodules.cpp.o CMakeFiles/bibletime.dir/src/util/geticon.cpp.o CMakeFiles/bibletime.dir/src/util/tool.cpp.o CMakeFiles/bibletime.dir/src/bibletime.cpp.o CMakeFiles/bibletime.dir/src/bibletime_dbus.cpp.o CMakeFiles/bibletime.dir/src/bibletime_dbus_adaptor.cpp.o CMakeFiles/bibletime.dir/src/bibletime_init.cpp.o CMakeFiles/bibletime.dir/src/bibletime_slots.cpp.o CMakeFiles/bibletime.dir/src/bibletimeapp.cpp.o CMakeFiles/bibletime.dir/src/btglobal.cpp.o CMakeFiles/bibletime.dir/src/main.cpp.o CMakeFiles/bibletime.dir/src/frontend/btaboutdialog.cpp.o CMakeFiles/bibletime.dir/src/frontend/btaboutmoduledialog.cpp.o CMakeFiles/bibletime.dir/src/frontend/btbookshelfdockwidget.cpp.o
Bug#767075: pidgin-otr: Needs to Depend: libotr5 (= 4.1.0)
Control: severity -1 important Hi, Ralf Jung wrote (28 Oct 2014 09:38:10 GMT) : I just upgraded pidgin-otr on my testing system. Then pidgin fails to start, saying Expected libotr API version 4.1.0 incompatible with actual version 4.0.0. Aborting. Thanks for reporting this bug to us. I had to upgrade libotr5 to the current unstable version to fix this. Obviously, the dependencies are not tight enough. Right. The root cause of the problem was in libotr itself, and has been fixed (short-term: #767230; long-term: #767652) in 4.1.0-2, which is now in sid, has been unblocked by the release team, and should then migrate to testing in 10 days. Given this, pidgin-otr will automatically pick up the right versioned dependency on libotr next time it is rebuilt. Also, libotr 4.1.0-1 has now migrated to testing, so this bug should not be an issue in practice (since libotr5 didn't exist in Wheezy, so partial upgrades are not a problem for Wheezy-Jessie upgrades). Hence, I'm downgrading the severity of this bug. The only remaining problematic case I can think of is partial upgrades from Wheezy + backports to Jessie, with pidgin-otr being upgraded but libotr being kept at the version that's currently in wheezy-backports. To address this potential problem, I'm going to upload libotr 4.1.0-2 to wheezy-backports soon after it reaches testing. Once this is done, I'll close this bug, as all real-world issues it may trigger will have been solved in some way. Cheers, -- intrigeri -- To UNSUBSCRIBE, email to debian-bugs-rc-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#766114: [pkg-fso-maint] Bug#766114: fso-deviced: uninstallable in i386/amd64/armhf
That doesn't help: # apt-get install fso-deviced-n900 Reading package lists... Done Building dependency tree Reading state information... Done The following packages were automatically installed and are no longer required: libgcrypt11 libgee2 libgnutls26 libjpeg62 Use 'apt-get autoremove' to remove them. The following extra packages will be installed: fso-deviced Recommended packages: fso-deviced-platform The following NEW packages will be installed: fso-deviced fso-deviced-n900 0 upgraded, 2 newly installed, 0 to remove and 114 not upgraded. Need to get 0 B/146 kB of archives. After this operation, 617 kB of additional disk space will be used. Do you want to continue? [Y/n] Selecting previously unselected package fso-deviced. (Reading database ... 42289 files and directories currently installed.) Preparing to unpack .../fso-deviced_0.12.0-2_armhf.deb ... Unpacking fso-deviced (0.12.0-2) ... Selecting previously unselected package fso-deviced-n900. Preparing to unpack .../fso-deviced-n900_0.12.0-2_armhf.deb ... Unpacking fso-deviced-n900 (0.12.0-2) ... Processing triggers for man-db (2.7.0.2-2) ... Processing triggers for dbus (1.8.8-2) ... Setting up fso-deviced (0.12.0-2) ... [FAIL] Starting freesmartphone.org device daemon : fso-deviced failed! invoke-rc.d: initscript fso-deviced, action start failed. dpkg: error processing package fso-deviced (--configure): subprocess installed post-installation script returned error exit status 1 dpkg: dependency problems prevent configuration of fso-deviced-n900: fso-deviced-n900 depends on fso-deviced (= 0.12.0-2); however: Package fso-deviced is not configured yet. dpkg: error processing package fso-deviced-n900 (--configure): dependency problems - leaving unconfigured Processing triggers for dbus (1.8.8-2) ... Errors were encountered while processing: fso-deviced fso-deviced-n900 E: Sub-process /usr/bin/dpkg returned an error code (1) (that was on the N900, right after running apt-get update) btw, even if it were the solution this would mean that fso-deviced-platform should be a dependency of fso-deviced and not a recommendation. That in turn would mean that fso-deviced should only be available in armel and armhf because all the packages that provide fso-deviced-platform are only available here. That on the other hand would be unfortunate because phoneui-apps depends on phoneuid depends on phonefsod depends on fso-deviced, which means people like me who want to have a look at the UI first on their x86 machine before deciding whether they want to obtain some HW for actually running phoneui-apps can't get a preview anymore. -- To UNSUBSCRIBE, email to debian-bugs-rc-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#767103: irssi-plugin-otr doesn't work with irssi 0.8.17
Control: tag -1 + moreinfo Hi, David Kalnischkies wrote (28 Oct 2014 14:00:40 GMT) : Upgrading irssi from 0.8.16-1+b1 to 0.8.17-1 seems to break the OTR plugin for me. I'm wondering if this could be a side-effect of #767230. Can you reproduce this after upgrading libotr5 to 4.1.0-1? Cheers, -- intrigeri -- To UNSUBSCRIBE, email to debian-bugs-rc-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Processed: Re: Bug#767103: irssi-plugin-otr doesn't work with irssi 0.8.17
Processing control commands: tag -1 + moreinfo Bug #767103 [irssi-plugin-otr] irssi-plugin-otr doesn't work with irssi 0.8.17 Added tag(s) moreinfo. -- 767103: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=767103 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems -- To UNSUBSCRIBE, email to debian-bugs-rc-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#768054: fp-units-multimedia: Upgrade fail from wheezy to jessie (versioned dependency on fp-units-multimedia-2.6.0)
Hmm, some duckduckgo helped. The problem is that you did an apt-get upgrade. However, with the fpc chain, you need an apt-get dist-upgrade. Can you reproduce the problem if you apt-get dist-upgrade? Otherwise, I don't think this is a bug, but a feature of apt-get. Paul signature.asc Description: OpenPGP digital signature
Bug#768054: fp-units-multimedia: Upgrade fail from wheezy to jessie (versioned dependency on fp-units-multimedia-2.6.0)
[Paul Gevers] fp-units-multimedia in jessie depends on fp-units-multimedia-2.6.4. Where does this dependency come from as this is the dependency in wheezy? No idea. :) fpc-2.6.0 should get removed during an upgrade. Why is it not removed? Do you directly depend on it somewhere? These are the entires in our tasks/development file: Depends: fp-compiler, fp-ide, fp-units-base, fp-units-gfx, fp-utils, fp-units-gtk2, \ fp-docs, fpc-source, fp-units-fcl, fp-units-i386, fp-units-multimedia, \ fp-units-misc, fp-units-net, fp-units-rtl, fp-units-fv The fpc-2.6.0 package is not mentioned there. Can you please help me to read the log? If you just upgrade fpc (wheezy) to fpc (jessie) the above should not happen with the dependencies in both releases, so you must be trying to force something that isn't supported, or the resolvers have issues. Holger know the details better than me, but as far as I know, the test consist of these steps: (1) build chroot (2) apt-get install education-development (3) change apt source from wheezy to jessie (4) run apt-get dist-upgrade All packages involved are in the Debian archive. The full log can be seen on URL: https://jenkins.debian.net/view/edu_devel/job/chroot-installation_wheezy_install_education-development_upgrade_to_jessie/1/consoleFull . It did not tell me much more about what is going wrong. -- Happy hacking Petter Reinholdtsen -- To UNSUBSCRIBE, email to debian-bugs-rc-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#767632: marked as done (ust: FTBFS on most architectures)
Your message dated Tue, 04 Nov 2014 19:49:58 + with message-id e1xlk74-0007cd...@franck.debian.org and subject line Bug#767632: fixed in ust 2.5.1-2 has caused the Debian Bug report #767632, regarding ust: FTBFS on most architectures 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 this message is talking about, this may indicate a serious mail system misconfiguration somewhere. Please contact ow...@bugs.debian.org immediately.) -- 767632: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=767632 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems ---BeginMessage--- package: ust severity: serious version: 2.5.1-1 Hi, The latest upload of ust fails on most architectures, but built fine in the past. This prevents migration to testing. https://buildd.debian.org/status/package.php?p=ust Cheers, Ivo ---End Message--- ---BeginMessage--- Source: ust Source-Version: 2.5.1-2 We believe that the bug you reported is fixed in the latest version of ust, which is due to be installed in the Debian FTP archive. 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 767...@bugs.debian.org, and the maintainer will reopen the bug report if appropriate. Debian distribution maintenance software pp. Jon Bernard jbern...@debian.org (supplier of updated ust 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 ftpmas...@ftp-master.debian.org) -BEGIN PGP SIGNED MESSAGE- Hash: SHA1 Format: 1.8 Date: Tue, 04 Nov 2014 19:44:13 + Source: ust Binary: liblttng-ust0 liblttng-ust-ctl2 liblttng-ust-dev Architecture: source amd64 Version: 2.5.1-2 Distribution: unstable Urgency: medium Maintainer: Jon Bernard jbern...@debian.org Changed-By: Jon Bernard jbern...@debian.org Description: liblttng-ust-ctl2 - LTTng 2.0 Userspace Tracer (trace control library) liblttng-ust-dev - LTTng 2.0 Userspace Tracer (development files) liblttng-ust0 - LTTng 2.0 Userspace Tracer (tracing libraries) Closes: 767632 Changes: ust (2.5.1-2) unstable; urgency=medium . * [65a639d] Tag arch-specfic symbols for i386 and amd64 (Closes: #767632) Checksums-Sha1: 725181b328a5f41eb7c401e8b03a692816920f55 2216 ust_2.5.1-2.dsc ebb78846389dccac46ce1ccb9b2793c7ccf52125 8772 ust_2.5.1-2.debian.tar.xz 1ace9158a6ec7eb5157b10e1a1b86bf88038f408 134088 liblttng-ust0_2.5.1-2_amd64.deb dd84526f7aa48557ed75b186eecee62bbcfe453c 84434 liblttng-ust-ctl2_2.5.1-2_amd64.deb 2b4f13b007f26371741e7ca46db2ff9e41df300e 183186 liblttng-ust-dev_2.5.1-2_amd64.deb Checksums-Sha256: e2a6860fe297aa5748c80e352a0861ec5050ac31fe3a5207449ffb3d8a5ec998 2216 ust_2.5.1-2.dsc 9b468673e438f8469ad1ec15b15cb06206bb9ab97013d2383f9c73e4ebbd57cf 8772 ust_2.5.1-2.debian.tar.xz d4feaf873298f36ce0248129bb2cee90931eca5cc904909301918ca551769861 134088 liblttng-ust0_2.5.1-2_amd64.deb e6675ab8e78ed5960e881cfad19178f12782a355f5b66cb329a1fb7a3540509e 84434 liblttng-ust-ctl2_2.5.1-2_amd64.deb 1ea8298beb9d4da2f5f270bca1b110ddf73c3de17ae756c07cc8009382e352dd 183186 liblttng-ust-dev_2.5.1-2_amd64.deb Files: 9224a96ecb7f593bf37ad361d6e3756b 2216 libs extra ust_2.5.1-2.dsc e0a6546b2fba2d3fabdac76ba0ba782b 8772 libs extra ust_2.5.1-2.debian.tar.xz 91a41c38688de30b0f04d3f7a25c2a7f 134088 libs extra liblttng-ust0_2.5.1-2_amd64.deb dad8f9222c94cd63a04485f8effe00d0 84434 libs extra liblttng-ust-ctl2_2.5.1-2_amd64.deb 844497c65d6a640e7a9bc314130dcab8 183186 libdevel extra liblttng-ust-dev_2.5.1-2_amd64.deb -BEGIN PGP SIGNATURE- Version: GnuPG v1 iQIcBAEBAgAGBQJUWSzpAAoJEN+j8UsohsyzFzcP/AmZ/+BYZfJU58wGjJ7kFpOi iHqnOyrXq7mT24TGkCVobHPEruhMyiyC7Hk79/CY6X5IDcQms9Y6AOLOIO2PPa5U YstdzyIGNPV3Z7F9Vjf8qpKKoHYUkOFDTNcqy4QxGnpVF/Ur/XTdcgEA+pKfPwGT WitLSfkYob4893bTQDxkPF1hkX7edRH4ZwAL9lerkTzAxNKl8fhFtzmsm4xAeJ2F ZKECrUDF+s46RI+1E5FNtWfWM6WIQcWtvZqM72uCRbtfMoeq7RnzwJW0xzPZCh+c 2ryDdWGhLPGslFnvVBrc6ZACIzkH7jm9Dy/Hl66YgQkF/Pc/A/XYxHGY0eraNFXs YyyMWYjjCTbzKJmJHBElQGogoURHUbwxHTxKN8LNMXaRQztz4j7ujZNT+xMfQpM9 BGWDBthfhXXCtp5Lj7xwmFt0gZtuNlGeIgiqDhR6/R4owOMKp615SE6OwNgSixGC eqHXXS+/HqqHOdKhFkMxfXcIM8YWQ1/LyInU5G9wNxCQmDG5Lft1IeqIgZtfj75q +mz5d5f3+GDsse+OckxvFWBDMmswHvSqzoVlbFZx6ErjKl2889ZGRPAlcZHXE8to mEqx4HGToSPmjC2/5dlRvy49511nR+0nvd3q/kdYM8x/LW6XQQoanomZ3FjU1tG2 HQqzxYGma1mBMYB/Vum4 =tdy6 -END PGP SIGNATUREEnd Message---
Bug#767561: [Pkg-freeipa-devel] Bug#767561: pki-tools, strongswan-starter: error when trying to install together
On 02.11.2014 19:20, Romain Francoise wrote: severity 767561 important quit On Sat, Nov 01, 2014 at 11:37:48AM +0200, Timo Aaltonen wrote: I don't mind adding a Conflicts. On Fedora though strongswan changed the binary/manpage name to strongswan-pki: [...] Either solution would be fine with me, but in the meantime this bug will block strongswan's migration to testing before the freeze, so I'm downgrading it to important and we can see how to handle this in the coming weeks. Strongswan 5.2.1-4 is now in testing, how about the following diff applied quickly so that dogtag-pki could migrate before the freeze? diff --git a/debian/changelog b/debian/changelog index 1cf0050..c02b490 100644 --- a/debian/changelog +++ b/debian/changelog @@ -1,3 +1,11 @@ +strongswan (5.2.1-5) UNRELEASED; urgency=medium + + * Non-maintainer upload. + * rules, strongswan-starter.install: Rename pki to strongswan-pki to +avoid conflict with pki-tools. (Closes: #767561) + + -- Timo Aaltonen tjaal...@debian.org Tue, 04 Nov 2014 20:57:31 +0200 + strongswan (5.2.1-4) unstable; urgency=medium * Give up on trying to run the test suite on !amd64, it now times out on diff --git a/debian/rules b/debian/rules index ba9eefa..a18e7bc 100755 --- a/debian/rules +++ b/debian/rules @@ -83,6 +83,10 @@ override_dh_auto_clean: override_dh_install: + # rename $bin/pki to avoid conflict with dogtag/pki-tools + mv $(CURDIR)/debian/tmp/usr/bin/pki $(CURDIR)/debian/tmp/usr/bin/strongswan-pki + mv $(CURDIR)/debian/tmp/usr/share/man/man1/pki.1 $(CURDIR)/debian/tmp/usr/share/man/man1/strongswan-pki.1 + # first special cases ifeq ($(DEB_BUILD_ARCH_OS),linux) # handle Linux-only plugins diff --git a/debian/strongswan-starter.install b/debian/strongswan-starter.install index 5d765ee..a2a5374 100644 --- a/debian/strongswan-starter.install +++ b/debian/strongswan-starter.install @@ -19,7 +19,7 @@ usr/lib/ipsec/_updown_espmark usr/share/man/man8/_updown.8 usr/share/man/man8/_updown_espmark.8 #tools -usr/bin/pki +usr/bin/strongswan-pki usr/lib/ipsec/scepclient usr/share/man/man8/scepclient.8 usr/share/man/man1/pki---acert.1 @@ -33,7 +33,7 @@ usr/share/man/man1/pki---req.1 usr/share/man/man1/pki---self.1 usr/share/man/man1/pki---signcrl.1 usr/share/man/man1/pki---verify.1 -usr/share/man/man1/pki.1 +usr/share/man/man1/strongswan-pki.1 usr/share/strongswan/templates/config/strongswan.d/pki.conf usr/share/strongswan/templates/config/strongswan.d/scepclient.conf etc/strongswan.d/pki.conf -- To UNSUBSCRIBE, email to debian-bugs-rc-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#764162: [karl.bel...@gmail.com: Re: [PATCH 0/1] mv643xx_eth: Disable TSO by default]
On Tue, 4 Nov 2014 17:06:43 +0100 Karl Beldan karl.bel...@gmail.com wrote:
Hi,
I think this patch fixes this bug, if someone can try it.
Karl
- Forwarded message from Karl Beldan karl.bel...@gmail.com -
Date: Tue, 4 Nov 2014 15:20:20 +0100
From: Karl Beldan karl.bel...@gmail.com
To: Ezequiel Garcia ezequiel.gar...@free-electrons.com
Cc: net...@vger.kernel.org, David Miller da...@davemloft.net,
Thomas Petazzoni thomas.petazz...@free-electrons.com, Gregory
Clement gregory.clem...@free-electrons.com, Tawfik Bayouk
taw...@marvell.com, Lior Amsalem al...@marvell.com, Nadav
Haklai nad...@marvell.com
Subject: Re: [PATCH 0/1] mv643xx_eth: Disable TSO by default
User-Agent: Mutt/1.5.23 (2014-03-12)
On Sat, Nov 01, 2014 at 12:30:19PM -0300, Ezequiel Garcia wrote:
Several users ([1], [2]) have been reporting data corruption with
TSO on
Kirkwood platforms (i.e. using the mv643xx_eth driver).
Until we manage to find what's causing this, this simple patch will
make
the TSO path disabled by default. This patch should be queued for
stable,
fixing the TSO feature introduced in v3.16.
The corruption itself is very easy to reproduce: checking md5sum on
a mounted
NFS directory gives a different result each time. Same tests using
the mvneta
driver (Armada 370/38x/XP SoC) pass with no issues.
Frankly, I'm a bit puzzled about this, and so any ideas or
debugging hints
are well received.
Hi,
Can you try this :
@@ -1067,7 +1082,8 @@ static int txq_reclaim(struct tx_queue *txq,
int budget, int force)
txq-tx_desc_count--;
skb = NULL;
- if (cmd_sts TX_LAST_DESC)
+ if ((cmd_sts (TX_LAST_DESC | TX_ENABLE_INTERRUPT)) ==
+ (TX_LAST_DESC | TX_ENABLE_INTERRUPT))
skb = __skb_dequeue(txq-tx_skb);
if (cmd_sts ERROR_SUMMARY) {
--
Karl
- End forwarded message -
Great! I test this patch and it seems to solve the data corruption that
I have
Julien
--
To UNSUBSCRIBE, email to debian-bugs-rc-requ...@lists.debian.org
with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#767561: pki-tools, strongswan-starter: error when trying to install together
On 2014-11-04 21:24, Timo Aaltonen wrote: Strongswan 5.2.1-4 is now in testing, how about the following diff applied quickly so that dogtag-pki could migrate before the freeze? If this gets renamed in strongswan, pki-tools still needs to add Breaks: strongswan-starter ( 5.2.1-5~) Replaces: strongswan-starter ( 5.2.1-5~) Andreas -- To UNSUBSCRIBE, email to debian-bugs-rc-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Processed: Re: Bug#768054: fp-units-multimedia: Upgrade fail from wheezy to jessie (versioned dependency on fp-units-multimedia-2.6.0)
Processing commands for cont...@bugs.debian.org: Severity 768054 normal Bug #768054 [fp-units-multimedia] fp-units-multimedia: Upgrade fail from wheezy to jessie (versioned dependency on fp-units-multimedia-2.6.0) Severity set to 'normal' from 'serious' Tags 768054 moreinfo Bug #768054 [fp-units-multimedia] fp-units-multimedia: Upgrade fail from wheezy to jessie (versioned dependency on fp-units-multimedia-2.6.0) Ignoring request to alter tags of bug #768054 to the same tags previously set Thanks Stopping processing here. Please contact me if you need assistance. -- 768054: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=768054 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems -- To UNSUBSCRIBE, email to debian-bugs-rc-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#768054: fp-units-multimedia: Upgrade fail from wheezy to jessie (versioned dependency on fp-units-multimedia-2.6.0)
Severity 768054 normal Tags 768054 moreinfo Thanks Petter Reinholdtsen wrote: Package: fp-units-multimedia Version: 2.6.4+dfsg-4 Severity: serious User: debian-...@lists.debian.org Usertags: debian-edu We discovered this when testing package upgrades of the Debian Edu tasks. The upgrade of the education-development task/metapackage failed like this: Reading package lists... Building dependency tree... Reading state information.. Indicates a new apt invocation of apt but the log doesn't contain the actual invocation. Can you fix your test script to print the commands it's invoking? Building dependency tree... Reading state information... The following packages have unmet dependencies: fp-units-multimedia : Depends: fp-units-multimedia-2.6.0 (= 2.6.0-9) but it is not going to be installed fpc-2.6.0 : Depends: fp-units-multimedia-2.6.0 (= 2.6.0-9) but it is not going to be installed E: Error, pkgProblemResolver::Resolve generated breaks, this may be caused by held packages. Sat Nov 1 09:32:20 UTC 2014 - /srv/jenkins/bin/chroot-installation.sh stopped running as /tmp/jenkins-script-SioIc9Mr, which will now be removed. Build step 'Execute shell' marked build as failure It looks like either apt's resolver didn't try hard enough or there was a problem somewhere that made the action you requested not possible (which from bitter experiance may have little or nothing to do with the packages apt lists in the error message). I've especially seen problems of apt's resolver not trying hard enough when trying to upgrade a package and it's dependencies using apt-get install and where said upgrade would require significant removal activity. The full log can be seen on URL: https://jenkins.debian.net/view/edu_devel/job/chroot-installation_wheezy_install_education-development_upgrade_to_jessie/ . I guess there is something wrong with the dependencies of fp-units-multimedia but have not investigated. Setting severity to serious, as packages should be upgradable between releases I see no evidence that fpc in general is not upgradable. I'm downgrading this to normal until /unless evidence is provided of a real bug in fpc. -- To UNSUBSCRIBE, email to debian-bugs-rc-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#766819: cinnamon freezes for a minute or so, when opening images or text with gnome/gtk apps and when closing them later on
Control: severity -1 important Hi, This bug seems to be an openafs issue that's blocking some other program (probably gvfs), I think the same bug would be reproduceable in other desktop environments, but I don't have an openafs available to test it. In any case, it doesnt make any good if cinnamon can't migrate to testing because of this bug, so I'm lowering the severity of the issue. Happy hacking, -- “First, solve the problem. Then, write the code.” -- John Johnson Saludos /\/\ /\ `/ signature.asc Description: Digital signature
Processed: Re: cinnamon freezes for a minute or so, when opening images or text with gnome/gtk apps and when closing them later on
Processing control commands: severity -1 important Bug #766819 [cinnamon] cinnamon freezes for a minute or so, when opening images or text with gnome/gtk apps and when closing them later on Severity set to 'important' from 'grave' -- 766819: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=766819 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems -- To UNSUBSCRIBE, email to debian-bugs-rc-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Processed: Re: Iceweasel dies on Segmentation fault, in 64 bit linux
Processing commands for cont...@bugs.debian.org: tags 765961 unreproducible Bug #765961 [iceweasel] Iceweasel dies on Segmentation fault, in 64 bit linux Added tag(s) unreproducible. severity 765961 important Bug #765961 [iceweasel] Iceweasel dies on Segmentation fault, in 64 bit linux Severity set to 'important' from 'grave' thanks Stopping processing here. Please contact me if you need assistance. -- 765961: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=765961 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems -- To UNSUBSCRIBE, email to debian-bugs-rc-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#762031: debian-security-support: Please use interest-noawait for your trigger
Guillem Jover wrote... On Sun, 2014-10-26 at 20:01:22 +0100, Christoph Biedl wrote: Guillem Jover wrote... Control: severity -1 serious Why? Well, because as it stands, it creates trigger cycles, so I don't think it is fit for release. (Those cycles started to get detected recently, then that regressed and stopped being detected, which meant that Jakub closed the other RC bug, but now should be detected correctly again.) Ah, that one. I thought it had been dealt with, nevertheless if you consider that kind of trigger usage a bad idea, let's get rid of it. Actually, besides creating triggers cycles, this seems rather an abuse of triggers. Because what the package seems to want is to be notified when any package is unpacked. This is really not what triggers where intended for, even if they allow this kind of usage. There was no indication for me at all you consider this abuse. I'm not sure if you mean in general, like in documentation or previous posts about this, or if you mean in the above comment, if the former I'll gladly try to improve the documentation, or write a post to say debian-devel to state that clearly. If the latter, I'll try to explain below why anyway. Actually the latter but this deserves broader knowledge anyway. An updated version will be uploaded in a few minutes, Just some comments: In this case you want dpkg to trigger for every and each package installed, and you are assuming all packages ship at least a file under /usr (in practice this might do the job, but you'd really want would be to trigger on /). Being sophistic (but not serious), /usr/share/doc/ should be sufficient due to policy 12.5 Copyright information :) (...) Please do not access the dpkg database on the filesystem directly, and move the functionality into a new script, or update the existing one to do the equivalent. Did so. I was thinking of invoking dpkg-reconfigure instead but that might cause nasty effects due to dpkg nesting. And I don't think that using debconf outside of a maintainer script is a problem TBH, but you might want to check with the debconf maintainers. Don't think so, although lintian is a bit unhappy. This sounds a bit weird. And creates a problem: Even if I check $DPKG_HOOK_ACTION for configure, this hook will be called for each package if more than just one is being installed. This will increase load on my side unless there's a way to to detect the *last* configure invocation of a dpkg run in a sane way - that's the job the trigger served very well. The hook is executed per dpkg run, not per package action, so if apt bundles say 40 packages in a dpkg call, then there will be only one post-invoke execution. The problem is that if apt does multiple dpkg runs, because for example it is dealing with Essential packages, then yes it will be called multiple times. But the same applies to a trigger as dpkg might end up calling it multiple times depending on when it gets processed, or when it subsequently gets triggered. As things just happen, my observation above was the result of an unlucky test scenario where I saw several hook invocations. But there were also several trigger invocations, so there is no differences. Please confirm this approach or suggest a better one. Yes, that should do the trick. You can easily check how this behaves on your system by adding something like: ,--- /etc/dpkg/dpkg.cfg.d/10-post-invoke --- post-invoke echo Dpkg hook action: $DPKG_HOOK_ACTION `--- But, let me know if anything is not clear, etc. A heads-up: Trailing spaces in that post-invoke line might result in completely mis-leading error messages. Will investigate further and perhaps file a bug report about that. Thanks a lot for your explanations. It was insightful and I love to learn from people who are willing to share their knowledge in a patient way. Christoph signature.asc Description: Digital signature
Bug#767248: marked as done (dbconfig-common: removes permissions of include files on)
Your message dated Tue, 04 Nov 2014 21:19:25 + with message-id e1xllvd-0001qg...@franck.debian.org and subject line Bug#767248: fixed in dbconfig-common 1.8.47+nmu3 has caused the Debian Bug report #767248, regarding dbconfig-common: removes permissions of include files on 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 this message is talking about, this may indicate a serious mail system misconfiguration somewhere. Please contact ow...@bugs.debian.org immediately.) -- 767248: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=767248 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems ---BeginMessage--- Package: roundcube Version: 0.9.5+dfsg1-4.1 Severity: grave Justification: renders package unusable The recent upgrade of the package broke roundcube with a permission problem upon reading its configuration. The file /etc/roundcube/debian-db.php was identified as being the culprit. This file is generated by dbconfig-common and should be owned by root:www-data with permissions 0640. After the upgrade, however, it was owned by root:root with permissions 0640 (reproducible on two systems), making it unreadable by the webserver. I got the idea that it might be related to #720517 somehow… As a workaround, this solves the issue: # chown :www-data /etc/roundcube/debian-db.php Credits to Simon Bruder simon.bru...@teckids.org, our 10 year-old infrastructure admin, for stumbling upon this in a dist-upgrade, identifying the origin of the failure in the server logs and helping find out it is dbconfig-common related by reading the postinst script ;). You rock, fellow ☺! Cheers, Nik -- System Information: Debian Release: jessie/sid APT prefers testing-updates APT policy: (500, 'testing-updates'), (500, 'testing') Architecture: amd64 (x86_64) Kernel: Linux 3.16-3-amd64 (SMP w/2 CPU cores) Locale: LANG=de_DE.UTF-8, LC_CTYPE=en_GB.UTF-8 (charmap=UTF-8) Shell: /bin/sh linked to /bin/dash Versions of packages roundcube-core depends on: ii dbconfig-common1.8.47+nmu2 ii debconf [debconf-2.0] 1.5.53 ii libapache2-mod-php55.6.2+dfsg-1 ii libjs-jquery 1.7.2+dfsg-3.2 ii libmagic1 1:5.19-2 ii php-auth 1.6.4-1 ii php-mail-mime 1.8.9-1 ii php-net-smtp 1.6.2-2 ii php-net-socket 1.0.14-1 ii php5 5.6.2+dfsg-1 ii php5-common5.6.2+dfsg-1 ii php5-intl 5.6.2+dfsg-1 ii php5-json 1.3.6-1 ii php5-mcrypt5.6.2+dfsg-1 ii roundcube-sqlite3 0.9.5+dfsg1-4.1 ii tinymce3.4.8+dfsg0-1 ii ucf3.0030 Versions of packages roundcube-core recommends: ii apache2 [httpd-cgi] 2.4.10-5 ii apache2-mpm-prefork [httpd-cgi] 2.4.10-5 ii apache2-mpm-worker [httpd-cgi] 2.4.10-5 ii php5-gd 5.6.2+dfsg-1 ii php5-pspell 5.6.2+dfsg-1 Versions of packages roundcube-core suggests: ii php-auth-sasl 1.0.6-1 pn php-crypt-gpg none ii roundcube-plugins 0.9.5+dfsg1-4.1 roundcube depends on no packages. -- Configuration Files: /etc/roundcube/apache.conf changed [not included] -- debconf information: roundcube/internal/reconfiguring: false roundcube/remote/newhost: roundcube/reconfigure-webserver: apache2, lighttpd roundcube/mysql/admin-user: root roundcube/db/app-user: * roundcube/database-type: sqlite3 roundcube/db/basepath: /var/lib/dbconfig-common/sqlite3/roundcube roundcube/dbconfig-reinstall: false roundcube/pgsql/changeconf: false roundcube/pgsql/no-empty-passwords: roundcube/mysql/method: unix socket roundcube/pgsql/authmethod-admin: ident roundcube/remote/host: roundcube/pgsql/authmethod-user: password roundcube/dbconfig-upgrade: true roundcube/db/dbname: roundcube roundcube/pgsql/method: unix socket roundcube/missing-db-package-error: abort roundcube/upgrade-backup: true roundcube/purge: false roundcube/hosts: roundcube/language: de_DE roundcube/passwords-do-not-match: roundcube/pgsql/admin-user: postgres roundcube/remove-error: abort roundcube/internal/skip-preseed: false * roundcube/dbconfig-install: true roundcube/pgsql/manualconf: roundcube/install-error: abort roundcube/upgrade-error: abort roundcube/remote/port: roundcube/restart-webserver: true roundcube/dbconfig-remove: ---End Message--- ---BeginMessage--- Source: dbconfig-common Source-Version: 1.8.47+nmu3 We believe that the bug you reported is fixed in the latest version of dbconfig-common, which is due to be installed in the Debian FTP archive. 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
Bug#767991: marked as done (elasticsearch: plugin manager does not work)
Your message dated Tue, 04 Nov 2014 21:19:38 + with message-id e1xllvq-0001tf...@franck.debian.org and subject line Bug#767991: fixed in elasticsearch 1.0.3+dfsg-5 has caused the Debian Bug report #767991, regarding elasticsearch: plugin manager does not work 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 this message is talking about, this may indicate a serious mail system misconfiguration somewhere. Please contact ow...@bugs.debian.org immediately.) -- 767991: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=767991 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems ---BeginMessage--- Package: elasticsearch Version: 1.0.3+dfsg-4 Severity: grave $ /usr/share/elasticsearch/bin/plugin Error: Could not find or load main class org.elasticsearch.plugins.PluginManager This happens because we forgot to adjust the classpath in the script. -Hilko ---End Message--- ---BeginMessage--- Source: elasticsearch Source-Version: 1.0.3+dfsg-5 We believe that the bug you reported is fixed in the latest version of elasticsearch, which is due to be installed in the Debian FTP archive. 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 767...@bugs.debian.org, and the maintainer will reopen the bug report if appropriate. Debian distribution maintenance software pp. Hilko Bengen ben...@debian.org (supplier of updated elasticsearch 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 ftpmas...@ftp-master.debian.org) -BEGIN PGP SIGNED MESSAGE- Hash: SHA1 Format: 1.8 Date: Tue, 04 Nov 2014 09:24:46 +0100 Source: elasticsearch Binary: elasticsearch Architecture: source all Version: 1.0.3+dfsg-5 Distribution: unstable Urgency: medium Maintainer: Hilko Bengen ben...@debian.org Changed-By: Hilko Bengen ben...@debian.org Description: elasticsearch - Open Source, Distributed, RESTful Search Engine Closes: 767364 767991 Changes: elasticsearch (1.0.3+dfsg-5) unstable; urgency=medium . * Team upload. * Added script to remove non-free bits from orig tarballs * Fixed Vcs-Git entry (Closes: #767364) * Edited patches (correct attribution) * Added common shell script snippet to determine classpath (Closes: #767991) * Added plugin/ directory, conf/, data/, log/ links to /usr/share/elasticsearch * Added versioned (build) dependencies to avoid Lucene 4.10 Checksums-Sha1: 6b621bcdc1a9166a543ec0af4a41ed4fb695b09f 1903 elasticsearch_1.0.3+dfsg-5.dsc b88edede56109442128c62fc82b3241d5ec48bea 9544 elasticsearch_1.0.3+dfsg-5.debian.tar.xz 0ca5b8267c6bc618e22f5eddd8f395c6eca227b2 10495304 elasticsearch_1.0.3+dfsg-5_all.deb Checksums-Sha256: 6d0d58a2030335db10682ee730ffc3ad85c86cc9a8b42aa30dfc7b57658fb7bc 1903 elasticsearch_1.0.3+dfsg-5.dsc 57643998742ca69834203a167c32d1e800dd312023440aa99a5a8c9fe22e8629 9544 elasticsearch_1.0.3+dfsg-5.debian.tar.xz 80e1658f25d7595704e09861eb63ce18f7aa30b775da4d50d5667422b5f67594 10495304 elasticsearch_1.0.3+dfsg-5_all.deb Files: 079aa218ce5b8d1b5775fa49304040d7 1903 web optional elasticsearch_1.0.3+dfsg-5.dsc d3cb2f747596659994b898f5ee441d2c 9544 web optional elasticsearch_1.0.3+dfsg-5.debian.tar.xz 878df8b938b95397c7f6ebccec450a22 10495304 web optional elasticsearch_1.0.3+dfsg-5_all.deb -BEGIN PGP SIGNATURE- Version: GnuPG v1 iEYEARECAAYFAlRZQDEACgkQUCgnLz/SlGgXgACgj31LrBSxnl8qJVh1jEH93fc0 1XYAn1hV+cwyu3UkGt4n3/Etp3sJymOr =68N8 -END PGP SIGNATUREEnd Message---
Bug#768011: marked as done (blends-dev: Dependencies from non-free or unstable can be included by accident)
Your message dated Tue, 04 Nov 2014 21:19:17 + with message-id e1xllvv-0001nu...@franck.debian.org and subject line Bug#768011: fixed in blends 0.6.92.2 has caused the Debian Bug report #768011, regarding blends-dev: Dependencies from non-free or unstable can be included by accident 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 this message is talking about, this may indicate a serious mail system misconfiguration somewhere. Please contact ow...@bugs.debian.org immediately.) -- 768011: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=768011 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems ---BeginMessage--- Package: blends-dev Severity: critical Tags: patch Justification: breaks unrelated software If a user who creates metapackages for a Blend by chance includes non-free, unstable, experimental or any unrelated repository in /etc/apt/sources.list.d/ some dependencies that are not in testing could be included into the metapackage. This might result in metapackages which conflict Debian policy. A fix for the problem is commited to packaging Git and was tested. Kind regards Andreas. -- System Information: Debian Release: 7.7 APT prefers stable APT policy: (500, 'stable') Architecture: amd64 (x86_64) Kernel: Linux 3.2.0-4-amd64 (SMP w/1 CPU core) Locale: LANG=de_DE.UTF-8, LC_CTYPE=de_DE.UTF-8 (charmap=UTF-8) Shell: /bin/sh linked to /bin/dash ---End Message--- ---BeginMessage--- Source: blends Source-Version: 0.6.92.2 We believe that the bug you reported is fixed in the latest version of blends, which is due to be installed in the Debian FTP archive. 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 768...@bugs.debian.org, and the maintainer will reopen the bug report if appropriate. Debian distribution maintenance software pp. Andreas Tille ti...@debian.org (supplier of updated blends 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 ftpmas...@ftp-master.debian.org) -BEGIN PGP SIGNED MESSAGE- Hash: SHA512 Format: 1.8 Date: Mon, 03 Nov 2014 11:28:06 +0100 Source: blends Binary: blends-dev blends-common blends-doc Architecture: source all Version: 0.6.92.2 Distribution: unstable Urgency: medium Maintainer: Debian Pure Blend Team debian-ble...@lists.debian.org Changed-By: Andreas Tille ti...@debian.org Description: blends-common - Debian Pure Blends common package blends-dev - Debian Pure Blends common files for developing metapackages blends-doc - Debian Pure Blends documentation Closes: 768011 Changes: blends (0.6.92.2) unstable; urgency=medium . * devtools/blend-gen-control: Prevent respecting users sources.list.d dir Closes: #768011 Checksums-Sha1: 8bd48c0dda21d1bf51c91bf9b6bf520c8c066d3e 1919 blends_0.6.92.2.dsc a933cff0364e8fd830eb95751060121f7c366b6d 98228 blends_0.6.92.2.tar.xz 209b777f497e658100a5986ed59df1558d86a7ae 31088 blends-dev_0.6.92.2_all.deb e7e3c9704ce835eb434d3470394b9be31a47187e 22348 blends-common_0.6.92.2_all.deb c8e5c325c6285fc46febe20bd3ee05436fc82503 442914 blends-doc_0.6.92.2_all.deb Checksums-Sha256: 02c2f9b1ca8a90f660985c2d05593592dddc95947f6cd3e27e9f9ccbd5657e07 1919 blends_0.6.92.2.dsc ea9b5def2bf9b00bbc6ed8f2b71d556cd88f6b6e9a409e3ea87c886fa2c85651 98228 blends_0.6.92.2.tar.xz 506dad3cb74dc32479e73ac51e1eb139227cfeac0ecc0fa4aa23150d273252e1 31088 blends-dev_0.6.92.2_all.deb 4452d0e45e2f628cc39e381b7f653fb2ebbef3bd8a57d15bab4898c417053eee 22348 blends-common_0.6.92.2_all.deb df795015cabcde4538ad848321243795df46f9d27aac63e3ba6e283b474ee8e9 442914 blends-doc_0.6.92.2_all.deb Files: 65259785acf9a7b5d892c4d3c8699b81 1919 devel optional blends_0.6.92.2.dsc ffa2e376973a58bc77cd683eea6b530c 98228 devel optional blends_0.6.92.2.tar.xz a686c4ae29fe7dbc7e1cfa386c0e8774 31088 devel optional blends-dev_0.6.92.2_all.deb 4a14e96a4a3d751cb9e7dac06c8dce91 22348 misc optional blends-common_0.6.92.2_all.deb 3759d63799f887eeda6ae0af630a9682 442914 doc optional blends-doc_0.6.92.2_all.deb -BEGIN PGP SIGNATURE- Version: GnuPG v1 iQIcBAEBCgAGBQJUWTgUAAoJEFeKBJTRxkbR3aEP/jgYb7RAK0+hNSwji4FfRYa9 U/IaN/MzICdNe/fxPYxIaM8JltZIC0P6Q8a8ABEp1l6HsKMeak0+RLCeE+u3sOEU fshezRIPNv1cdZoKmor0a1Yrn7wALW+TGOVccf3PRtQ4pOIEZ0rl7Kleh41Na0sZ 4ppx7Mt6AaSuFpYKMCbfzFCJqDB/T4fL5IviwxCZXlpQsl1rnI3PPjHvDzww64Os MpLjj35ov2wJCW/tuALeDWCOXhiteMDDEpJJWZi6RDdEyXR8cP96t4ICYQEglIAZ 7bbh5JXTCOFjronCedcaLKFDy1cM5Od20eEVJWJkGbC70payatISgIk1IqrF+MNj /HEDUzWYfFeAwraR8o0NRFjP8HQCSGVMWQQznrcEaOYKDNQVk0HJXImT+X2hePAe
Bug#763378: marked as done (syslog-nagios-bridge is not installable)
Your message dated Tue, 04 Nov 2014 22:32:58 +0100 with message-id 5459460a.80...@pocock.pro and subject line Re: [Pkg-monitoring-maintainers] Bug#763378: Bug#763378: syslog-nagios-bridge is not installable has caused the Debian Bug report #763378, regarding syslog-nagios-bridge is not installable 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 this message is talking about, this may indicate a serious mail system misconfiguration somewhere. Please contact ow...@bugs.debian.org immediately.) -- 763378: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=763378 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems ---BeginMessage--- Package: syslog-nagios-bridge Version: 1.0.1-4 Severity: grave Justification: renders package unusable Latest upload of syslog-nagios-bridge bumped the dependency on pynag to 0.9.1: | syslog-nagios-bridge (1.0.1-4) unstable; urgency=low | | * Update pynag dependency to 0.9.1 or greater, fixing file_time bug. | | -- Daniel Pocock dan...@pocock.pro Sun, 03 Aug 2014 18:34:51 +0200 This makes syslog-nagios-bridge uninstallable as this version is not available in debian (not even in experimental). -- System Information: Debian Release: jessie/sid APT prefers unstable APT policy: (500, 'unstable'), (1, 'experimental') Architecture: amd64 (x86_64) Foreign Architectures: i386 Kernel: Linux 3.14-1-amd64 (SMP w/4 CPU cores) Locale: LANG=fr_FR.UTF-8, LC_CTYPE=fr_FR.UTF-8 (charmap=UTF-8) Shell: /bin/sh linked to /bin/bash ---End Message--- ---BeginMessage--- On 04/11/14 06:32, Clint Byrum wrote: I've uploaded 0.9.1 to unstable. https://packages.qa.debian.org/p/pynag.html Great, thanks for that - I'm marking this bug closed as it is satisfied by this upload---End Message---
Bug#768090: beignet: pow(n), erf(c), tgamma give wrong results
Package: beignet
Version: 0.9.3~dfsg-1
Severity: serious
Justification: a math library should NOT silently give wrong answers
Control: found -1 0.8-1.1
Control: tags -1 upstream patch
In current beignet (0.8, 0.9.3 and upstream-HEAD):
-pow/pown ignore the sign of their first argument (e.g. pow(-2,3) gives
8 instead of -8)
-erf/erfc diverge (instead of converging to 1 or 0) for arguments above
about 2
-tgamma is actually lgamma, a related but very different function (and
the test suite doesn't notice because it checks against glibc's gammaf,
which is also lgamma, instead of tgammaf)
#!/usr/bin/env python3
#Depends: python3-pyopencl python3-scipy
import pyopencl
import pyopencl.array
import numpy as np
import scipy.special as spfn
import time
ctx=pyopencl.create_some_context()
cq=pyopencl.CommandQueue(ctx)
a1=np.array(-0.95*np.random.rand(1e6)-0.01,dtype=np.float32)
a2=-1000*a1
a3=20*(a1+0.5)
ai=np.array(a3,dtype=np.int32)
aCL1=pyopencl.array.to_device(cq,a1)
aCL2=pyopencl.array.to_device(cq,a2)
aCL3=pyopencl.array.to_device(cq,a3)
aCLi=pyopencl.array.to_device(cq,ai)
bCL=aCL1+1
c=np.array(range(20),dtype=np.float32)/3-2
ci=np.array(c,dtype=np.int32)
cCL=pyopencl.array.to_device(cq,c)
cCLi=pyopencl.array.to_device(cq,ci)
dCL=cCL+1
def approx_erfc(x):
p = 0.3275911
a1 = 0.254829592
a2 = -0.284496736
a3 = 1.421413741
a4 = -1.453152027
a5 = 1.061405429
d = np.exp(-x*x)
t = 1/(1+p*np.abs(x))
r = (a1*t+a2*t*t+a3*t*t*t+a4*t*t*t*t+a5*t*t*t*t*t)*d
return r*np.sign(x)+1-np.sign(x)
erfc_err=np.abs(spfn.erfc(a3)-approx_erfc(a3))
print(x:,c,\n,ci)
print(erfc:,np.max(erfc_err),np.mean(erfc_err))
f_to_test=[(cos,np.cos),(sin,np.sin),(tan,np.tan),(cosh,np.cosh),(cospi,lambda x:np.cos(np.pi*x)),(tanh,np.tanh),(exp,np.exp),(log,np.log),(sqrt,np.sqrt),(acos,np.arccos),(acosh,np.arccosh),(pow(a[i],c[i]),lambda x,y:x**y),(pown(a[i],d[i]),lambda x,y:x**y),(tgamma,spfn.gamma),(erf,spfn.erf),(erfc,spfn.erfc)]
for f in f_to_test:
for aCL in aCL1,aCL2,aCL3:
fCL=pyopencl.elementwise.ElementwiseKernel(ctx,float *a,float *b,float *c,int *d,b[i]=+f[0]+( if f[0] in (pow(a[i],c[i]),pown(a[i],d[i]),powr(a[i],c[i])) else (a[i])))
t0=time.time()
fCL(aCL,bCL,aCL3,aCLi).wait()
t=time.time()-t0
b=bCL.get()
if f[0] in (pow(a[i],c[i]),powr(a[i],c[i])):
b0=f[1](aCL.get(),a3)
elif f[0] in (pown(a[i],d[i]),):
b0=f[1](aCL.get(),ai)
else:
b0=f[1](aCL.get())
abserr=np.abs(b-b0)
relerr=np.abs(b/b0-1)
print(f[0],abs avg err:,np.nanmean(abserr), max err:,np.max(abserr),rel avg err:,np.nanmean(relerr), max err:,np.max(relerr), time:,t)
if f[0] in (erf,erfc,tgamma,pown(a[i],d[i]),pow(a[i],c[i])):
fCL(cCL,dCL,cCL,cCLi).wait()
if f[0] in (pow(a[i],c[i]),powr(a[i],c[i])):
d0=f[1](c,c)
elif f[0] in (pown(a[i],d[i]),):
d0=f[1](c,ci)
else:
d0=f[1](c)
print(dCL.get(),\n,d0)
Description: short summary of the patch
TODO: Put a short summary on the line above and replace this paragraph
with a longer explanation of this change. Complete the meta-information
with other relevant fields (see below for details). To make it easier, the
information below has been extracted from the changelog. Adjust it or drop
it.
.
beignet (0.9.3~dfsg-2) UNRELEASED; urgency=medium
.
* Fix tgamma,pow,pown,erf,erfc
* Enable debug output in tests
Author: Rebecca N. Palmer rnpalmer@rnpalmer-laptop
---
The information above should follow the Patch Tagging Guidelines, please
checkout http://dep.debian.net/deps/dep3/ to learn about the format. Here
are templates for supplementary fields that you might want to add:
Origin: vendor|upstream|other, url of original patch
Bug: url in upstream bugtracker
Bug-Debian: https://bugs.debian.org/bugnumber
Bug-Ubuntu: https://launchpad.net/bugs/bugnumber
Forwarded: no|not-needed|url proving that it has been forwarded
Reviewed-By: name and email of someone who approved the patch
Last-Update: -MM-DD
--- beignet-0.9.3~dfsg.orig/utests/builtin_acos_asin.cpp
+++ beignet-0.9.3~dfsg/utests/builtin_acos_asin.cpp
@@ -2,12 +2,13 @@
#include cmath
#include algorithm
-#define udebug 0
+#define udebug 1
#define printf_c(...) \
{\
printf(\033[1m\033[40;31m);\
printf( __VA_ARGS__ );\
printf(\033[0m);\
+ status = 1;\
}
const float input_data[] = {-30, -1, -0.92, -0.5, -0.09, 0, 0.09, 0.5, 0.92, 1, 30};
@@ -29,6 +30,7 @@ static void builtin_acos_asin(void)
{
// Setup kernel and buffers
int k, i, index_cur;
+ int status = 0;
float gpu_data[max_function * count_input] = {0}, cpu_data[max_function * count_input] = {0};
OCL_CREATE_KERNEL(builtin_acos_asin);
@@ -82,6 +84,7 @@ static void builtin_acos_asin(void)
#endif
}
}
+ OCL_ASSERT(status == 0);
}
MAKE_UTEST_FROM_FUNCTION(builtin_acos_asin)
--- beignet-0.9.3~dfsg.orig/utests/builtin_pow.cpp
+++
Processed: beignet: pow(n), erf(c), tgamma give wrong results
Processing control commands: found -1 0.8-1.1 Bug #768090 [beignet] beignet: pow(n), erf(c), tgamma give wrong results Marked as found in versions beignet/0.8-1.1. tags -1 upstream patch Bug #768090 [beignet] beignet: pow(n), erf(c), tgamma give wrong results Added tag(s) upstream and patch. -- 768090: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=768090 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems -- To UNSUBSCRIBE, email to debian-bugs-rc-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#768093: possible data loss when --git-dir is set to wacky thing
Package: git-annex Version: 5.20141024 Severity: serious http://git-annex.branchable.com/bugs/misuse_of_--git-dir_might_destroy_a_git_repository_completely/ -- see shy jo signature.asc Description: Digital signature
Bug#767745: pidgin: Aborting due to incompatible libotr API version 4.0.0
reassign 767745 pidgin-otr severity 767745 important thanks Reassigning to correct package and adjusting severity according to intrigeri's comment in #767075. -- To UNSUBSCRIBE, email to debian-bugs-rc-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Processed: Re: Bug#767745: pidgin: Aborting due to incompatible libotr API version 4.0.0
Processing commands for cont...@bugs.debian.org: reassign 767745 pidgin-otr Bug #767745 [pidgin] pidgin: Aborting due to incompatible libotr API version 4.0.0 Bug reassigned from package 'pidgin' to 'pidgin-otr'. No longer marked as found in versions pidgin/2.10.10-1. Ignoring request to alter fixed versions of bug #767745 to the same values previously set severity 767745 important Bug #767745 [pidgin-otr] pidgin: Aborting due to incompatible libotr API version 4.0.0 Severity set to 'important' from 'grave' thanks Stopping processing here. Please contact me if you need assistance. -- 767745: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=767745 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems -- To UNSUBSCRIBE, email to debian-bugs-rc-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#765525: marked as done (git: gitweb broken by libcgi-pm-perl 4.06-1)
Your message dated Tue, 04 Nov 2014 22:19:29 + with message-id e1xlmrl-0001p7...@franck.debian.org and subject line Bug#765525: fixed in git 1:2.1.3-1 has caused the Debian Bug report #765525, regarding git: gitweb broken by libcgi-pm-perl 4.06-1 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 this message is talking about, this may indicate a serious mail system misconfiguration somewhere. Please contact ow...@bugs.debian.org immediately.) -- 765525: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=765525 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems ---BeginMessage--- Package: git Version: 1:2.1.1-1 Severity: important gitweb uses old functions that used to be provided (although deprecated) by CGI.pm; however, these functions have been removed in version 4.05 of that package, which entered unstable when libcgi-pm-perl 4.03-1 was upgraded to 4.06-1. As a consequence, gitweb now returns an empty body. I did a s/startform/start_form/ in gitweb.cgi, which fixed two calls to the now nonexisting startform function, and gitweb started working again. Roland. -- System Information: Debian Release: jessie/sid APT prefers unstable APT policy: (500, 'unstable'), (1, 'experimental') Architecture: amd64 (x86_64) Kernel: Linux 3.16-2-amd64 (SMP w/8 CPU cores) Locale: LANG=fr_FR.utf8, LC_CTYPE=fr_FR.utf8 (charmap=UTF-8) Shell: /bin/sh linked to /bin/dash Versions of packages git depends on: ii git-man 1:2.1.1-1 ii libc62.19-11 ii libcurl3-gnutls 7.38.0-2 ii liberror-perl0.17-1.1 ii libexpat12.1.0-6 ii libpcre3 1:8.35-3.1 ii perl-modules 5.20.1-1 ii zlib1g 1:1.2.8.dfsg-2 Versions of packages git recommends: ii less 458-3 ii openssh-client [ssh-client] 1:6.7p1-2 ii patch2.7.1-6 ii rsync3.1.1-2 Versions of packages git suggests: ii gettext-base 0.19.2-3 pn git-arch none pn git-cvs none pn git-daemon-run | git-daemon-sysvinit none pn git-doc none pn git-elnone pn git-email none ii git-gui 1:2.1.1-1 pn git-mediawiki none pn git-svn none ii gitk 1:2.1.1-1 pn gitwebnone -- no debconf information -- Roland Mas Death *was* hereditary. You got it from your ancestors. -- in Hogfather (Terry Pratchett) ---End Message--- ---BeginMessage--- Source: git Source-Version: 1:2.1.3-1 We believe that the bug you reported is fixed in the latest version of git, which is due to be installed in the Debian FTP archive. 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 765...@bugs.debian.org, and the maintainer will reopen the bug report if appropriate. Debian distribution maintenance software pp. Jonathan Nieder jrnie...@gmail.com (supplier of updated git 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 ftpmas...@ftp-master.debian.org) -BEGIN PGP SIGNED MESSAGE- Hash: SHA1 Format: 1.8 Date: Tue, 04 Nov 2014 13:20:39 -0800 Source: git Binary: git git-man git-core git-doc git-arch git-cvs git-svn git-mediawiki git-email git-daemon-run git-daemon-sysvinit git-gui gitk git-el gitweb git-all Architecture: source amd64 all Version: 1:2.1.3-1 Distribution: unstable Urgency: low Maintainer: Gerrit Pape p...@smarden.org Changed-By: Jonathan Nieder jrnie...@gmail.com Description: git- fast, scalable, distributed revision control system git-all- fast, scalable, distributed revision control system (all subpacka git-arch - fast, scalable, distributed revision control system (arch interop git-core - fast, scalable, distributed revision control system (obsolete) git-cvs- fast, scalable, distributed revision control system (cvs interope git-daemon-run - fast, scalable, distributed revision control system (git-daemon s git-daemon-sysvinit - fast, scalable, distributed revision control system (git-daemon s git-doc- fast, scalable, distributed revision control system (documentatio git-el - fast, scalable, distributed revision control system (emacs suppor git-email - fast, scalable, distributed revision control system (email add-on git-gui- fast, scalable, distributed revision control system (GUI)
Bug#762031: marked as done (debian-security-support: Please use interest-noawait for your trigger)
Your message dated Tue, 04 Nov 2014 22:18:57 + with message-id e1xlmrf-0001ww...@franck.debian.org and subject line Bug#762031: fixed in debian-security-support 2014.11.04 has caused the Debian Bug report #762031, regarding debian-security-support: Please use interest-noawait for your trigger 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 this message is talking about, this may indicate a serious mail system misconfiguration somewhere. Please contact ow...@bugs.debian.org immediately.) -- 762031: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=762031 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems ---BeginMessage--- Package: debian-security-support Version: 2014.09.07 Severity: normal An interest /usr trigger means that any package installing a file in /usr will be marked as triggers-noawait instead of being immediately configured. This is counter-productive given that debian-security-support doesn't bring anything to those packages and they have no reason to wait until debian-security-support's trigger is applied... Thus please use interest-noawait instead of interest. Beware that this directive is not supported in oldstable (it has been introduced in dpkg 1.16.1), you will have to change that for backports to squeeze. -- System Information: Debian Release: jessie/sid APT prefers unstable APT policy: (500, 'unstable'), (500, 'testing'), (500, 'stable'), (1, 'experimental') Architecture: amd64 (x86_64) Foreign Architectures: i386 Kernel: Linux 3.14-2-amd64 (SMP w/4 CPU cores) Locale: LANG=fr_FR.UTF-8, LC_CTYPE=fr_FR.UTF-8 (charmap=UTF-8) Shell: /bin/sh linked to /bin/dash Versions of packages debian-security-support depends on: ii adduser3.113+nmu3 ii debconf [debconf-2.0] 1.5.53 ii gettext-base 0.19.2-2 debian-security-support recommends no packages. debian-security-support suggests no packages. -- debconf information: debian-security-support/ended: * debian-security-support/limited: ---End Message--- ---BeginMessage--- Source: debian-security-support Source-Version: 2014.11.04 We believe that the bug you reported is fixed in the latest version of debian-security-support, which is due to be installed in the Debian FTP archive. 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 762...@bugs.debian.org, and the maintainer will reopen the bug report if appropriate. Debian distribution maintenance software pp. Christoph Biedl debian.a...@manchmal.in-ulm.de (supplier of updated debian-security-support 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 ftpmas...@ftp-master.debian.org) -BEGIN PGP SIGNED MESSAGE- Hash: SHA512 Format: 1.8 Date: Tue, 04 Nov 2014 22:01:42 +0100 Source: debian-security-support Binary: debian-security-support Architecture: source all Version: 2014.11.04 Distribution: unstable Urgency: high Maintainer: Christoph Biedl debian.a...@manchmal.in-ulm.de Changed-By: Christoph Biedl debian.a...@manchmal.in-ulm.de Description: debian-security-support - Debian security support coverage checker Closes: 762031 765374 Changes: debian-security-support (2014.11.04) unstable; urgency=high . * Closes an RC bug, urgency set to high * Add src:axis2c to list of packages not supported in squeeze-lts. Closes: #765374 * Use dpkg invoke hook instead of triggers. Thanks Guillem Jover for the detailed explanations. Closes: #762031 Checksums-Sha1: 952be7bd7e4f8985c8cfbdeafd13b9400ac28e67 1795 debian-security-support_2014.11.04.dsc 289e1584cc092a287dd03857cc442f9692bdcf45 20116 debian-security-support_2014.11.04.tar.xz b582a24b6e46aebc678129bb9f590b4ef199d9bd 19244 debian-security-support_2014.11.04_all.deb Checksums-Sha256: 06cc3690f53841dbe1196762bd6abc5fed0a39479786104a6484da050644a484 1795 debian-security-support_2014.11.04.dsc 80d4a0500956ceef0ea68508af707cc3e776cf4dd7407b6c3ac5f98d071ee050 20116 debian-security-support_2014.11.04.tar.xz bdecf9ccb7c6767e31dffb412d4be261e74f968bfd380c3520713c750353cf5d 19244 debian-security-support_2014.11.04_all.deb Files: 1fd0b14e77687a1dc3b433489038bf96 1795 admin optional debian-security-support_2014.11.04.dsc 3099921198df3b709a0d60e2bdaa86fa 20116 admin optional debian-security-support_2014.11.04.tar.xz 28257a12ff0ff4349ff8fb09a1e79bc5 19244 admin optional debian-security-support_2014.11.04_all.deb -BEGIN PGP SIGNATURE- Version: GnuPG v1.4.12 (GNU/Linux) iQIcBAEBCgAGBQJUWUVnAAoJEMQsWOtZFJL9l5oP/Rdpfid46cTJPN4ivCgW1Pr0
Bug#765525: gitweb broken by libcgi-pm-perl 4.06-1
Jonathan Nieder wrote: * gitweb: use start_form instead of startform for compatibility with CGI.pm 4.04 and newer (thx Roland Max; closes: #765525). Gah. I've fixed the spelling in this changelog entry in the development repo, so it should be back to sanity in the next upload (2.1.3-2). Thanks again for the quick fix. -- To UNSUBSCRIBE, email to debian-bugs-rc-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#767561: marked as done (pki-tools,strongswan-starter: error when trying to install together)
Your message dated Tue, 04 Nov 2014 22:49:19 + with message-id e1xlmud-0006rp...@franck.debian.org and subject line Bug#767561: fixed in dogtag-pki 10.2.0-3 has caused the Debian Bug report #767561, regarding pki-tools,strongswan-starter: error when trying to install together 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 this message is talking about, this may indicate a serious mail system misconfiguration somewhere. Please contact ow...@bugs.debian.org immediately.) -- 767561: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=767561 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems ---BeginMessage--- Package: pki-tools,strongswan-starter Version: 10.2.0-2 Severity: serious User: trei...@debian.org Usertags: edos-file-overwrite Control: found -1 5.2.1-4 Architecture: amd64 Distribution: sid Hi, automatic installation tests of packages that share a file and at the same time do not conflict by their package dependency relationships has detected the following problem: Selecting previously unselected package strongswan-starter. Preparing to unpack .../strongswan-starter_5.2.1-4_amd64.deb ... Unpacking strongswan-starter (5.2.1-4) ... dpkg: error processing archive /var/cache/apt/archives/strongswan-starter_5.2.1-4_amd64.deb (--unpack): trying to overwrite '/usr/bin/pki', which is also in package pki-tools 10.2.0-2 dpkg-deb: error: subprocess paste was killed by signal (Broken pipe) Errors were encountered while processing: /var/cache/apt/archives/strongswan-starter_5.2.1-4_amd64.deb This is a serious bug as it makes installation fail, and violates sections 7.6.1 and 10.1 of the policy. An optimal solution would consist in only one of the packages installing that file, and renaming or removing the file in the other package. Depending on the circumstances you might also consider Replace relations or file diversions. If the conflicting situation cannot be resolved then, as a last resort, the two packages have to declare a mutual Conflict. Please take into account that Replaces, Conflicts and diversions should only be used when packages provide different implementations for the same functionality. Here is a list of files that are known to be shared by both packages (according to the Contents file for sid/amd64, which may be slightly out of sync): usr/bin/pki usr/share/man/man1/pki.1.gz This bug is assigned to both packages. If you, the maintainers of the two packages in question, have agreed on which of the packages will resolve the problem please reassign the bug to that package. You may also register in the BTS that the other package is affected by the bug. Cheers, Andreas PS: for more information about the detection of file overwrite errors of this kind see http://edos.debian.net/file-overwrites/. pki-tools=10.2.0-2_strongswan-starter=5.2.1-4.log.gz Description: application/gzip ---End Message--- ---BeginMessage--- Source: dogtag-pki Source-Version: 10.2.0-3 We believe that the bug you reported is fixed in the latest version of dogtag-pki, which is due to be installed in the Debian FTP archive. 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 767...@bugs.debian.org, and the maintainer will reopen the bug report if appropriate. Debian distribution maintenance software pp. Timo Aaltonen tjaal...@debian.org (supplier of updated dogtag-pki 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 ftpmas...@ftp-master.debian.org) -BEGIN PGP SIGNED MESSAGE- Hash: SHA1 Format: 1.8 Date: Wed, 05 Nov 2014 00:40:10 +0200 Source: dogtag-pki Binary: dogtag-pki pki-base pki-tools pki-server pki-ca dogtag-pki-console-theme dogtag-pki-server-theme pki-console pki-kra pki-ocsp pki-tks pki-tps pki-tps-client pki-javadoc libsymkey-java libsymkey-jni Architecture: source all amd64 Version: 10.2.0-3 Distribution: unstable Urgency: medium Maintainer: Debian FreeIPA Team pkg-freeipa-de...@lists.alioth.debian.org Changed-By: Timo Aaltonen tjaal...@debian.org Description: dogtag-pki - Dogtag Public Key Infrastructure (PKI) Suite dogtag-pki-console-theme - Certificate System - PKI Console User Interface dogtag-pki-server-theme - Certificate System - PKI Server User Interface libsymkey-java - Symmetric Key Java library libsymkey-jni - Symmetric Key JNI Library pki-base - Certificate System - PKI Framework pki-ca - Certificate System - Certificate Authority pki-console - Certificate System - PKI Console pki-javadoc - Certificate System - PKI Framework Javadocs
Processed: Re: Bug#756076: Acknowledgement (does not cleanup sessions when user logs out: No such interface 'org.freedesktop.systemd1.Scope')
Processing control commands: tag -1 fixed-upstream pending Bug #756076 [systemd-shim] does not cleanup sessions when user logs out Bug #756760 [systemd-shim] does not cleanup sessions when user logs out Added tag(s) pending and fixed-upstream. Added tag(s) pending and fixed-upstream. -- 756076: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=756076 756760: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=756760 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems -- To UNSUBSCRIBE, email to debian-bugs-rc-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#756076: Acknowledgement (does not cleanup sessions when user logs out: No such interface 'org.freedesktop.systemd1.Scope')
Control: tag -1 fixed-upstream pending Martin Pitt [2014-11-04 16:16 +0100]: Indeed the cgroups get cleaned up properly, just nothing tells logind about that as there is currently no notify_on_release being set/used. I'm looking into that now. The three last commits on https://github.com/desrt/systemd-shim/commits/master (Clean up closing logind sessions and the two previous ones) implement this now. Tomorrow I'll still look into https://bugs.debian.org/756247 (my original patch does not work), then we'll have all bugs except #747821 (moreinfo) fixed. Thanks, Martin -- Martin Pitt| http://www.piware.de Ubuntu Developer (www.ubuntu.com) | Debian Developer (www.debian.org) signature.asc Description: Digital signature
Bug#767589: systemd: cryptdisks other than root/swap fail cryptsetup
On Tue, 04 Nov 2014 13:52:16 +0100 Michael Biebl bi...@debian.org wrote: Therefore re-assigning to initramfs-tools. Please followup on the bug report and include the version of initramfs-tools you have installed. As well as the version of cryptsetup. initramfs-tools 0.118 cryptsetup 2:1.6.6-3 Thanks, Arnaud -- Arnaud Installe +32 477 304199 ESAT - STADIUS, KULeuven iMinds Medical Information Technologies pgpkgGWICHWnW.pgp Description: OpenPGP digital signature
Processed: your mail
Processing commands for cont...@bugs.debian.org: notfixed 739828 1.6-1 Bug #739828 [enigmail] enigmail: mistaken identity of signature There is no source info for the package 'enigmail' at version '1.6-1' with architecture '' Unable to make a source version for version '1.6-1' No longer marked as fixed in versions 1.6-1. fixed 739828 2:1.6-1 Bug #739828 [enigmail] enigmail: mistaken identity of signature Marked as fixed in versions enigmail/2:1.6-1. #Fixed versions. The epoch was missing End of message, stopping processing here. Please contact me if you need assistance. -- 739828: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=739828 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems -- To UNSUBSCRIBE, email to debian-bugs-rc-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
