Bug#717215: [pkg-dhcp-devel] Bug#717215: dhcpd: 5 bad udp checksums in 5 packets
Control: severity -1 normal Hi Simon, please choose a proper subject next time -- and not just the bug number. Simon Boulet wrote: This bug is really annoying. It has been fixed in recent version of Ubuntu: https://bugs.launchpad.net/ubuntu/+source/isc-dhcp/+bug/930962 I'd say in not so recent versions. That was back in 2013. By the way, the severity there is low because there are workarounds. Debian Bug Tracking System wrote: severity 717215 serious This is by no means a release-critical bug. annoying is no reason for being release-critical, despite I understand that people often wish so. Please see https://www.debian.org/Bugs/Developer#severities for a description of Debian's severities. merge 717215 717217 They are already merged since September 2013. Regards, Axel -- ,''`. | Axel Beckert a...@debian.org, http://people.debian.org/~abe/ : :' : | Debian Developer, ftp.ch.debian.org Admin `. `' | 4096R: 2517 B724 C5F6 CA99 5329 6E61 2FF9 CD59 6126 16B5 `-| 1024D: F067 EA27 26B9 C3FC 1486 202E C09E 1D89 9593 0EDE -- To UNSUBSCRIBE, email to debian-bugs-rc-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Processed: Re: [pkg-dhcp-devel] Bug#717215: dhcpd: 5 bad udp checksums in 5 packets
Processing control commands: severity -1 normal Bug #717215 [isc-dhcp-server] dhcpd: 5 bad udp checksums in 5 packets Bug #717217 [isc-dhcp-server] dhcpd: 5 bad udp checksums in 5 packets Severity set to 'normal' from 'serious' Severity set to 'normal' from 'serious' -- 717215: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=717215 717217: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=717217 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: Bug#779620: lldb-3.7: CommandLine Error: Option 'enable-objc-arc-opts' registered more than once!
Processing control commands: forwarded -1 http://llvm.org/bugs/show_bug.cgi?id=22543 Bug #779620 [lldb-3.7] lldb-3.7: CommandLine Error: Option 'enable-objc-arc-opts' registered more than once! Ignoring request to change the forwarded-to-address of bug#779620 to the same value -- 779620: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=779620 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: Bug#779620: lldb-3.7: CommandLine Error: Option 'enable-objc-arc-opts' registered more than once!
Processing control commands: forwarded -1 http://llvm.org/bugs/show_bug.cgi?id=22543 Bug #779620 [lldb-3.7] lldb-3.7: CommandLine Error: Option 'enable-objc-arc-opts' registered more than once! Set Bug forwarded-to-address to 'http://llvm.org/bugs/show_bug.cgi?id=22543'. -- 779620: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=779620 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#779620: lldb-3.7: CommandLine Error: Option 'enable-objc-arc-opts' registered more than once!
Control: forwarded -1 http://llvm.org/bugs/show_bug.cgi?id=22543 On 03/03/2015 07:54, Ph. Marek wrote: Package: lldb-3.7 Version: 1:3.7~svn230892-1 Severity: grave I tried the new version to see whether the arch detection has been fixed; it may have been, but the new version is still unusable: $ lldb-3.7 /bin/ls : CommandLine Error: Option 'enable-objc-arc-opts' registered more than once! LLVM ERROR: inconsistency in registered CommandLine options $ lldb-3.7 : CommandLine Error: Option 'enable-objc-arc-opts' registered more than once! LLVM ERROR: inconsistency in registered CommandLine options Yeh, still there, I am going to forward it to the dev mailing list. Sylvestre -- To UNSUBSCRIBE, email to debian-bugs-rc-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#766462: [Pkg-xfce-devel] Bug#766462: with plymouth installed, I don't get any gettys on my VCs
On mar., 2015-03-03 at 03:59 +, Mike Gabriel wrote: I am quite positive that some missing gettys because of two DMs being installed in parallel (or some similar normal thing that people might do) will definitely be worth a freeze exception. IMHO, if gettys don't come up properly, the system is rather broken and this is a no-go for jessie. Sure, but I had the impression that this wasn't the case for lightdm (and slim), according to Simon initial email. And I can confirm plymouth+lightdm seems to work just fine with init=systemd here. Regards, -- Yves-Alexis signature.asc Description: This is a digitally signed message part
Bug#766462: with plymouth installed, I don't get any gettys on my VCs
On 03/03/15 09:52, Yves-Alexis Perez wrote: On mar., 2015-03-03 at 03:59 +, Mike Gabriel wrote: IMHO, if gettys don't come up properly, the system is rather broken and this is a no-go for jessie. Sure, but I had the impression that this wasn't the case for lightdm (and slim), according to Simon initial email. And I can confirm plymouth+lightdm seems to work just fine with init=systemd here. I don't know whether lightdm, slim and/or wdm are affected (which is why I haven't cloned the bug already). The situation to test is: * have systemd as init * install plymouth, gdm3 and your favourite non-GDM DM implementation (kdm in the original bug report) * select the non-GDM DM implementation as the active DM * enable plymouth by putting splash on the kernel command-line I reproduced this for kdm by starting from a fresh task-standard installation in a VM and adding gdm3, kdm and plymouth. I haven't tested the other DMs in the same configuration so far. S -- To UNSUBSCRIBE, email to debian-bugs-rc-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Processed: your mail
Processing commands for cont...@bugs.debian.org:
reassign 777580 python-clang-3.5
Bug #777580 {Done: Sylvestre Ledru sylves...@debian.org}
[python-clang-3.5,python-clang-3.7] python-clang-3.7 and python-clang-3.5:
error when trying to install together
Bug reassigned from package 'python-clang-3.5,python-clang-3.7' to
'python-clang-3.5'.
No longer marked as found in versions llvm-toolchain-snapshot/1:3.7~svn227076-1
and llvm-toolchain-3.5/1:3.5-9.
No longer marked as fixed in versions llvm-toolchain-snapshot/1:3.7~svn230892-1.
fixed 777580 3.5-9
Bug #777580 {Done: Sylvestre Ledru sylves...@debian.org} [python-clang-3.5]
python-clang-3.7 and python-clang-3.5: error when trying to install together
There is no source info for the package 'python-clang-3.5' at version '3.5-9'
with architecture ''
Unable to make a source version for version '3.5-9'
Marked as fixed in versions 3.5-9.
thanks
Stopping processing here.
Please contact me if you need assistance.
--
777580: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=777580
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#779613: no such file or directory trying to connect through the blueman-applet
On 2015-03-03 01:57:24, Christopher Schramm wrote: Hi Antoine, unfortunately BlueZ 5's generic connect method is a misconception in my eyes as in your case it will not connect the NAP service. In the current upstream master you will not get a generic connect item in the menu anymore, but see which services are provided and could be connected with it. In case of Android phones there typically exists some audio service that should be connectible, but fails with that error message. It may just be that the device needs to be in a specific state (e.g. have a media app running) to make the connection work. Anyway, connecting to a NAP should work. You just have to select the service from the device menu and not use the generic connect item for that. There's no service from the menu, in fact, the Serial server menu item is gone. There's only a connect option which simply fails. And this is not an android phone, this is a LG flip phone. I insist on pointing out this is a regression from Wheezy and should really be fixed before jessie is released, hence the grave severity above. That's not correct as... I would seriously consider downgrading back to the stable version (1.23) while upstream works on 2.0, which seems to be more in an alpha state. This wouldn't bring us anywhere as 1.23 does not support BlueZ 5 at all. Understood. Upstream seems to be saying they fixed this peculiar problem in git (although the milestone item says the contrary), maybe a git snapshot should be tried in experimental? A. -- Be who you are and say what you feel Because those who mind don't matter And those who matter don't mind. - Dr. Seuss -- To UNSUBSCRIBE, email to debian-bugs-rc-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#762700: systemd: journald fails to forward most boot messages to syslog
Am 03.03.2015 um 15:33 schrieb Michael Biebl: Am 02.03.2015 um 15:42 schrieb Christian Seiler: - SOLUTION (mostly the same as before, but SendBuffer is set on a different unit and a Condition is added to the service): 1. Increase max_dgram_qlen to a reasonable value. The easiest way is via a systemd service: /lib/systemd/system/systemd-setup-dgram-qlen.service: [Unit] DefaultDependencies=no Before=syslog.socket ConditionPathIsReadWrite=/proc/sys/net/unix/max_dgram_qlen [Service] Type=oneshot ExecStart=/sbin/sysctl -w net.unix.max_dgram_qlen=512 StandardOutput=null A proper Description= is missing and it probably should have RemainAfterExit=yes. That said, why not simply use a sysctl.d conf snippet? I just tried the following: # cat /usr/lib/sysctl.d/50-qlen.conf net.unix.max_dgram_qlen=512 and adding RequiresMountsFor=/usr/lib/sysctl.d/ to systemd-sysctl.service (a change we should apply independently of this issue, given that we won't get the usr-mount patches for initramfs-tools in jessie). This seems to be sufficient to get rid of the Forwarding to syslog missed XXX messages. Add the following to /lib/systemd/systemd/syslog.socket: Wants=systemd-setup-dgram-qlen.service I didn't add an explicit Ordering to syslog.socket (After=systemd-sysctl.service). Will need to check if I was just lucky and without that it would be racy, or if the ordering is already correct. -- 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#779532: marked as done (ifetch-tools: superclass mismatch for class Monitor (TypeError))
Your message dated Tue, 03 Mar 2015 15:19:15 + with message-id e1ysobl-0006qe...@franck.debian.org and subject line Bug#779532: fixed in ifetch-tools 0.15.24d2-1 has caused the Debian Bug report #779532, regarding ifetch-tools: superclass mismatch for class Monitor (TypeError) 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.) -- 779532: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=779532 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems ---BeginMessage--- Package: ifetch-tools Version: 0.15.24d-1 Severity: normal During testing of ifetch-tools on jessie installs the following command was used to test part of the package: su ifetch-tools -c /usr/bin/wwwifetch Generates the following error: /usr/bin/wwwifetch:337:in `main': superclass mismatch for class Monitor (TypeError) This renders the package by default not usable in both a jessie and sid chroot. -- System Information: Debian Release: 8.0 APT prefers unstable APT policy: (500, 'unstable') Architecture: amd64 (x86_64) Kernel: Linux 3.16.0-4-amd64 (SMP w/4 CPU cores) Locale: LANG=en_US.UTF-8, LC_CTYPE=en_US.UTF-8 (charmap=locale: Cannot set LC_CTYPE to default locale: No such file or directory locale: Cannot set LC_MESSAGES to default locale: No such file or directory locale: Cannot set LC_ALL to default locale: No such file or directory ANSI_X3.4-1968) Shell: /bin/sh linked to /bin/dash Init: unable to detect Versions of packages ifetch-tools depends on: ii adduser3.113+nmu3 ii debconf [debconf-2.0] 1.5.55 ii libav-tools6:11.2-1 ii ruby 1:2.1.0.4 ii ruby-rmagick 2.13.2-4+b1 ifetch-tools recommends no packages. ifetch-tools suggests no packages. -- debconf information: perl: warning: Setting locale failed. perl: warning: Please check that your locale settings: LANGUAGE = (unset), LC_ALL = (unset), LANG = en_US.UTF-8 are supported and installed on your system. perl: warning: Falling back to the standard locale (C). locale: Cannot set LC_CTYPE to default locale: No such file or directory locale: Cannot set LC_MESSAGES to default locale: No such file or directory locale: Cannot set LC_ALL to default locale: No such file or directory ifetch-tools/purge: false ---End Message--- ---BeginMessage--- Source: ifetch-tools Source-Version: 0.15.24d2-1 We believe that the bug you reported is fixed in the latest version of ifetch-tools, 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 779...@bugs.debian.org, and the maintainer will reopen the bug report if appropriate. Debian distribution maintenance software pp. Richard Nelson unix...@gmail.com (supplier of updated ifetch-tools 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, 02 Mar 2015 22:18:41 -0600 Source: ifetch-tools Binary: ifetch-tools Architecture: source all Version: 0.15.24d2-1 Distribution: unstable Urgency: medium Maintainer: Richard Nelson unix...@gmail.com Changed-By: Richard Nelson unix...@gmail.com Description: ifetch-tools - Collect, monitor, and view images from ip cameras Closes: 779532 779536 779537 779538 779539 779614 Changes: ifetch-tools (0.15.24d2-1) unstable; urgency=medium . * Closing only stdin, stdout and stderr 0,1,2 on IO.for_fd() on wwwifetch (Closes: #779536). * Adjust class Monitor name to CMonitor in wwwifetch (Closes: #779532). * Adjusting VER for next release on wwwifetch. * Update copyright from 2005-2012 to 2005-2015. * Adjust Upstream-Homepage in debian/copyright (Closes: #779537). * Remove trailing whitespace on wwwifetch. * Remove unused array call in wwwifetch. * Upon a shutdown request stop camera collection as well in wwwifetch (Closes: #779539). * Minor adjustment for stop_all_cameras in wwwifetch. * Moving video export format from mpeg to mp4 in wwwifetch (Closes: #779538). * Renamed ifetch-tools.rubyforge.org ifetch-tools-html-page. * Updated url in ifetch-tools-html-pages/index.html. * Unify version number for VER in ifetch and wwwifetch for service release. * Improved video export for security of a more non deterministic structure on wwwifetch (Closes: #779614).
Bug#762700: systemd: journald fails to forward most boot messages to syslog
Am 03.03.2015 um 16:00 schrieb Michael Biebl: Am 03.03.2015 um 15:33 schrieb Michael Biebl: Am 02.03.2015 um 15:42 schrieb Christian Seiler: - SOLUTION (mostly the same as before, but SendBuffer is set on a different unit and a Condition is added to the service): 1. Increase max_dgram_qlen to a reasonable value. The easiest way is via a systemd service: /lib/systemd/system/systemd-setup-dgram-qlen.service: [Unit] DefaultDependencies=no Before=syslog.socket ConditionPathIsReadWrite=/proc/sys/net/unix/max_dgram_qlen [Service] Type=oneshot ExecStart=/sbin/sysctl -w net.unix.max_dgram_qlen=512 StandardOutput=null A proper Description= is missing and it probably should have RemainAfterExit=yes. That said, why not simply use a sysctl.d conf snippet? I just tried the following: # cat /usr/lib/sysctl.d/50-qlen.conf net.unix.max_dgram_qlen=512 and adding RequiresMountsFor=/usr/lib/sysctl.d/ to systemd-sysctl.service (a change we should apply independently of this issue, given that we won't get the usr-mount patches for initramfs-tools in jessie). This seems to be sufficient to get rid of the Forwarding to syslog missed XXX messages. Add the following to /lib/systemd/systemd/syslog.socket: Wants=systemd-setup-dgram-qlen.service I didn't add an explicit Ordering to syslog.socket (After=systemd-sysctl.service). Will need to check if I was just lucky and without that it would be racy, or if the ordering is already correct. I did a couple more reboots and did indeed run into the problem, that systemd-sysctl.service was started after syslog.socket, so I got the missed XXX messages again. Adding the After=systemd-sysctl.service ordering to syslog.socket fixed that. In [1] you mentioned, that a sysctl snippet is no option. Can you elaborate why? I'd really like to avoid shipping an extra service for this. Since systemd-sysctl.service uses DefaultDependencies=no as well, it can run pretty early. Michael [1] https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=762700#32 -- 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#762700: systemd: journald fails to forward most boot messages to syslog
Am 2015-03-03 15:33, schrieb Michael Biebl: Am 02.03.2015 um 15:42 schrieb Christian Seiler: - SOLUTION (mostly the same as before, but SendBuffer is set on a different unit and a Condition is added to the service): 1. Increase max_dgram_qlen to a reasonable value. The easiest way is via a systemd service: /lib/systemd/system/systemd-setup-dgram-qlen.service: [Unit] DefaultDependencies=no Before=syslog.socket ConditionPathIsReadWrite=/proc/sys/net/unix/max_dgram_qlen [Service] Type=oneshot ExecStart=/sbin/sysctl -w net.unix.max_dgram_qlen=512 StandardOutput=null A proper Description= is missing and it probably should have RemainAfterExit=yes. That said, why not simply use a sysctl.d conf snippet? systemd-sysctl.service is not ordered before the socket. Also it's ordered after a bunch of services, and syslog.socket is typically available really early. I've been using this on a Jessie system for the past couple of days (well, drop-ins in /etc, actually), and I didn't notice any side-effects so far. Did you run it with 1. and 2. applied, or only 1.? Only 1. so far. And 2. may not be necessary. Full disclosure: I decided to try to also tackle this issue on the kernel side (not for Jessie, but in general) by writing a patch that allows the user to change that option for individual sockets.[1] One of the issues that were mentioned in replies so far was that due to file descriptor passing in UNIX sockets, increasing the limit could reach OOM a little easier if an attacker were to do weird things. (Not with the syslog socket, but with a socket of their own.) I would argue that the current limits to the number of file descriptors etc. in a typical distro don't even come close to preventing OOM anyway, so it doesn't hurt much, but it's only fair to share this before you change anything. [1] http://www.spinics.net/lists/netdev/msg318492.html That said, w.r.t. buffer sizes: I did some tests during the test of my kernel patch, and if each datagram is less than 192 bytes in size (likely true for log messages), there will fit 555 of them in the standard send buffer of a socket - so a limit of 512 (513 in reality, the kernel is off by one) would cap that beforehand. (1 byte or 192 bytes don't make a difference btw., only = 193 bytes the number decreases.) So yes, setting SendBuffer on dev-log.socket is probably not needed, unless you have really, really large log messages. (The reason I mentioned the buffer in the first place was the fact that upstream sets it AND for some rather long test messages, I hit the buffer limit before I hit the queue length limit, but those are probably unrealistic.) So if the sysctl is reliably set before the socket is created, we should be good, the buffer size change is probably not needed unless there are REALLY long log messages. Christian -- To UNSUBSCRIBE, email to debian-bugs-rc-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#762700: systemd: journald fails to forward most boot messages to syslog
Am 03.03.2015 um 16:26 schrieb Christian Seiler: Am 2015-03-03 15:33, schrieb Michael Biebl: Am 02.03.2015 um 15:42 schrieb Christian Seiler: - SOLUTION (mostly the same as before, but SendBuffer is set on a different unit and a Condition is added to the service): 1. Increase max_dgram_qlen to a reasonable value. The easiest way is via a systemd service: /lib/systemd/system/systemd-setup-dgram-qlen.service: [Unit] DefaultDependencies=no Before=syslog.socket ConditionPathIsReadWrite=/proc/sys/net/unix/max_dgram_qlen [Service] Type=oneshot ExecStart=/sbin/sysctl -w net.unix.max_dgram_qlen=512 StandardOutput=null A proper Description= is missing and it probably should have RemainAfterExit=yes. That said, why not simply use a sysctl.d conf snippet? systemd-sysctl.service is not ordered before the socket. Yeah, see my other followup email. Can be fixed by adding After=systemd-sysctl.service to syslog.socket. Also it's ordered after a bunch of services, and syslog.socket is typically available really early. The only service I see ordered before systemd-sysctl.service is systemd-modules-load.service, and that one looks unproblematic, i.e. not something which would delay the start of syslog.socket noticeably. Then there is the proposed RequiresMountsFor=/usr/lib/sysctl.d/ which can translate into After=usr.mount, for a split-usr setup. In both cases, I don't see it leading to a regression compared to sysvinit, do you? I've been using this on a Jessie system for the past couple of days (well, drop-ins in /etc, actually), and I didn't notice any side-effects so far. Did you run it with 1. and 2. applied, or only 1.? Only 1. so far. And 2. may not be necessary. [..] So if the sysctl is reliably set before the socket is created, we should be good, the buffer size change is probably not needed unless there are REALLY long log messages. Given that it has been applied upstream (5e8b767df6e18444d5aff2987b5e5603361ed528), I personally wouldn't mind cherry-picking that patch. -- 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#762700: systemd: journald fails to forward most boot messages to syslog
Am 2015-03-03 16:26, schrieb Michael Biebl: I did a couple more reboots and did indeed run into the problem, that systemd-sysctl.service was started after syslog.socket, so I got the missed XXX messages again. Adding the After=systemd-sysctl.service ordering to syslog.socket fixed that. In [1] you mentioned, that a sysctl snippet is no option. Can you elaborate why? I'd really like to avoid shipping an extra service for this. Since systemd-sysctl.service uses DefaultDependencies=no as well, it can run pretty early. Danger! This could result in a deadlock. journald.service: After=syslog.socket (which is correct, otherwise messages will be silently discarded because it will get -ENOENT and think syslog is inactive anyway). syslog.socket: After=systemd-systctl.service systemd-sysctl.service: After=systemd-readahead-collect.service systemd-readahead-replay.service After=systemd-modules-load.service Even if you discard the readahead service, systemd-modules-load.service will generate log messages (1 for each module). Those log messages are then sent to the journal, which is not started yet (but its socket is), the default queue length for the kernel applies also here, but because logging is blocking (see shared/log.c, write_to_journal()), if the queue is full it will wait until the journal has collected the messages. But now you have the situation that journald is implicitly ordered after this service, so during the runtime of this service journald will never start and things deadlock. You can probably trigger this by putting 12 modules into /etc/modules-load.d. Each one will generate a message for the journal and after the 11th the service will hang. Jupp, just tried it, deadlocks. Will, kind-of, because after ~15s it will somehow still boot, I don't quite understand it, but I don't think this is fine the way it is. Christian -- To UNSUBSCRIBE, email to debian-bugs-rc-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#779331: wheezy update
Le 02/03/2015 14:47, Hans-Christoph Steiner a écrit : I think this also needs to be a security update in wheezy and jessie. What are the plans for that? Yes, it has been fixed in Jessie and will be included in the next point update of Wheezy. Emmanuel Bourg -- To UNSUBSCRIBE, email to debian-bugs-rc-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Processed: tagging 779599
Processing commands for cont...@bugs.debian.org: tags 779599 + pending Bug #779599 [libsocl-contrib-1.2-0,libsocl-1.2-0] libsocl-contrib-1.2-0, libsocl-1.2-0: missing breaks+replaces against each other Added tag(s) pending. thanks Stopping processing here. Please contact me if you need assistance. -- 779599: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=779599 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#778695: wheezy - jessie: no gdm3 prompt, dependency loops and broken initrd
Control: tag -1 moreinfo On Wed, Feb 18, 2015 at 12:04:38 -0500, Antoine Beaupré wrote: Package: upgrade-reports Severity: grave This is the third jessie upgrade I perform from jessie. The previous one was documented in #774314. It seems that the dependency loop problems are still there, and there were so many problems with the upgrade that I don't believe it would be right to release jessie as such (hence the grave severity). I know that I certainly can't spend the 6h i did on this workstation on all the workstations in the office. :) I followed the two-stage upgrade procedure from the install manual. My notes are here: https://wiki.koumbit.net/JessieUpgrade During the `dist-upgrade` step (after the `upgrade`), there was a failure i couldn't trace back (because i somehow got out of that ttyrec by mistake). After that, I got the following error trying to run `dist-upgrade` again: Do you still have the pre-upgrade dpkg status file? [...] The next problem I found was with gdm3: it was startup, but would only show the top toolbar: no user menu or user/password prompt. I worked around the problem by installing lightdm. I suspect this may be related to our LDAP setup. It usually has a not listed? click here bar that lets non-/etc/passwd users log in, IME. Was that not available? Do you have logs from gdm? Cheers, Julien signature.asc Description: Digital signature
Processed: Re: Bug#778695: wheezy - jessie: no gdm3 prompt, dependency loops and broken initrd
Processing control commands: tag -1 moreinfo Bug #778695 [upgrade-reports] wheezy - jessie: no gdm3 prompt, dependency loops and broken initrd Ignoring request to alter tags of bug #778695 to the same tags previously set -- 778695: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=778695 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: Bug#778695: wheezy - jessie: no gdm3 prompt, dependency loops and broken initrd
Processing control commands: tag -1 moreinfo Bug #778695 [upgrade-reports] wheezy - jessie: no gdm3 prompt, dependency loops and broken initrd Added tag(s) moreinfo. -- 778695: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=778695 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: severity of 779614 is serious, found 769146 in 1:5.7p1-1, unarchiving 705092 ...
Processing commands for cont...@bugs.debian.org:
severity 779614 serious
Bug #779614 {Done: Richard Nelson unix...@gmail.com} [ifetch-tools]
ifetch-tools: Possible tmpfile symlink attacks because of deterministic
filenames in /tmp
Severity set to 'serious' from 'normal'
found 769146 1:5.7p1-1
Bug #769146 [openntpd] openntpd: fails to upgrade from 'sid' - trying to
overwrite /etc/apparmor.d/usr.sbin.ntpd
There is no source info for the package 'openntpd' at version '1:5.7p1-1' with
architecture ''
Unable to make a source version for version '1:5.7p1-1'
Marked as found in versions 1:5.7p1-1.
unarchive 705092
Bug #705092 {Done: Hajime Mizuno mizuno...@ubuntu.com} [silversearcher-ag]
silversearcher-ag and python-ase: error when trying to install together
Unarchived Bug 705092
found 705092 0.28.0-1
Bug #705092 {Done: Hajime Mizuno mizuno...@ubuntu.com} [silversearcher-ag]
silversearcher-ag and python-ase: error when trying to install together
Marked as found in versions silversearcher-ag/0.28.0-1 and reopened.
thanks
Stopping processing here.
Please contact me if you need assistance.
--
705092: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=705092
769146: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=769146
779614: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=779614
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#779661: apt-config-auto-update: fails to upgrade from 'wheezy' - trying to overwrite /etc/apt/apt.conf.d/20archive
Package: apt-config-auto-update Version: 1.0.0-2 Severity: serious User: debian...@lists.debian.org Usertags: piuparts Hi, during a test with piuparts I noticed your package fails to upgrade from 'wheezy'. It installed fine in 'wheezy', then the upgrade to 'sid' fails because it tries to overwrite other packages files without declaring a Breaks+Replaces relation. See policy 7.6 at https://www.debian.org/doc/debian-policy/ch-relationships.html#s-replaces From the attached log (scroll to the bottom...): Selecting previously unselected package apt-config-auto-update. Unpacking apt-config-auto-update (from .../apt-config-auto-update_1.0.0-2_all.deb) ... dpkg: error processing /var/cache/apt/archives/apt-config-auto-update_1.0.0-2_all.deb (--unpack): trying to overwrite '/etc/apt/apt.conf.d/20archive', which is also in package update-notifier-common 0.99.3debian11 Errors were encountered while processing: /var/cache/apt/archives/apt-config-auto-update_1.0.0-2_all.deb update-notifier-common is not part of jessie, but may survive the upgrade from wheezy to jessie, and apt-config-auto-update is not part of jessie either, but to ensure smooth upgrades wheezy-jessie-stretch, it needs to add Breaks+Replaces: update-notifier-common This would also be needed for backporting it to jessie-backports at some point. cheers, Andreas update-notifier-common=0.99.3debian11_apt-config-auto-update=1.0.0-2.log.gz Description: application/gzip
Bug#779662: package fails to build without network connection
Package: src:fedmsg-meta-fedora-infrastructure Version: 0.2.18-1 Severity: serious Tags: sid jessie The package fails to build in an unstable environment on amd64 without having network access. the build log shows errors like these, which go away if you have network connection. == FAIL: test_secondary_icon (fedmsg_meta_fedora_infrastructure.tests.TestGithubDelete) Does fedmsg.meta produce the expected secondary icon? -- Traceback (most recent call last): File /usr/lib/python2.7/dist-packages/fedmsg/tests/test_meta.py, line 44, in inner return func(self) File /usr/lib/python2.7/dist-packages/fedmsg/tests/test_meta.py, line 100, in test_secondary_icon eq_(actual_icon, self.expected_secondary_icon) AssertionError: None != 'https://seccdn.libravatar.org/avatar/9c9f7784935381befc302fe3c814f9136e7a33953d0318761669b8643f4df55c?s=64d=retro' == FAIL: test_icon (fedmsg_meta_fedora_infrastructure.tests.TestGithubFork) Does fedmsg.meta produce the expected icon? -- Traceback (most recent call last): File /usr/lib/python2.7/dist-packages/fedmsg/tests/test_meta.py, line 44, in inner return func(self) File /usr/lib/python2.7/dist-packages/fedmsg/tests/test_meta.py, line 94, in test_icon eq_(actual_icon, self.expected_icon) AssertionError: 'https://apps.fedoraproject.org/img/icons/git-logo.png' != 'https://apps.fedoraproject.org/img/icons/github.png' == FAIL: test_link (fedmsg_meta_fedora_infrastructure.tests.TestGithubFork) Does fedmsg.meta produce the expected link? -- Traceback (most recent call last): File /usr/lib/python2.7/dist-packages/fedmsg/tests/test_meta.py, line 44, in inner return func(self) File /usr/lib/python2.7/dist-packages/fedmsg/tests/test_meta.py, line 88, in test_link eq_(actual_link, self.expected_link) AssertionError: None != 'https://github.com/kushal124/github2fedmsg' -- To UNSUBSCRIBE, email to debian-bugs-rc-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#779664: ffmpeg: needs Breaks+Replaces: libav-tools ( 6:9~)
Package: ffmpeg Version: 7:2.5.4-1 Severity: serious User: debian...@lists.debian.org Usertags: piuparts Hi, during a test with piuparts I noticed your package fails to co-install with libav-tools from wheezy. libav-tools installed fine in 'wheezy', then the upgrade to ffmpeg/'sid' fails because it tries to overwrite other packages files without declaring a Breaks+Replaces relation. See policy 7.6 at https://www.debian.org/doc/debian-policy/ch-relationships.html#s-replaces From the attached log (scroll to the bottom...): Selecting previously unselected package ffmpeg. Unpacking ffmpeg (from .../ffmpeg_7%3a2.5.4-1_amd64.deb) ... dpkg: error processing /var/cache/apt/archives/ffmpeg_7%3a2.5.4-1_amd64.deb (--unpack): trying to overwrite '/usr/share/man/man1/ffplay.1.gz', which is also in package libav-tools 6:0.8.16-1 dpkg-deb: error: subprocess paste was killed by signal (Broken pipe) Errors were encountered while processing: /var/cache/apt/archives/ffmpeg_7%3a2.5.4-1_amd64.deb Since there is no ffmpeg package in jessie, adding these Breaks+Replaces would ease some upgrade paths from wheezy as well as possible backporting. In libav (6:9~beta1-1) the compatibility links for ff* tools were removed. cheers, Andreas libav-tools=6%0.8.16-1_ffmpeg=7%2.5.4-1.log.gz Description: application/gzip
Bug#779663: sound-juicer: debian/copyright incomplete
Package: sound-juicer Version: 3.14.0-1 Justification: Policy 12.5 Severity: serious I'm unsure about the severity, reading debian policy it might only be important, please correct severity if I'm mistaken. debian/copyright is outdated and incomplete. Example: sj-cell-renderer-text.c: * Copyright (C) 2014 Phillip Wood phillip.w...@dunelm.org.uk however, Phillip Wood is not in debian/copyright debian/copyright says: ... debianized ... 2013 however, the latest year is 2008. The latest upstream release in Debian is from 2014 however, the latest year is 2008. I did not continue the investigation. -- Dr. Helge Kreutzmann deb...@helgefjell.de Dipl.-Phys. http://www.helgefjell.de/debian.php 64bit GNU powered gpg signed mail preferred Help keep free software libre: http://www.ffii.de/ signature.asc Description: Digital signature
Processed: Re: Bug#779579: installer broken: multipath-udeb depends on non-existent libgcc1 udeb
Processing control commands: tags -1 patch Bug #779579 [multipath-udeb] installer broken: multipath-udeb depends on non-existent libgcc1 udeb Added tag(s) patch. -- 779579: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=779579 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#779660: ruby-actionpack-page-caching: fails to upgrade from 'wheezy' - trying to overwrite /usr/lib/ruby/vendor_ruby/action_controller/caching/pages.rb
Package: ruby-actionpack-page-caching Version: 1.0.2-1 Severity: serious User: debian...@lists.debian.org Usertags: piuparts Hi, during a test with piuparts I noticed your package fails to upgrade from 'wheezy'. It installed fine in 'wheezy', then the upgrade to 'sid' fails because it tries to overwrite other packages files without declaring a Breaks+Replaces relation. See policy 7.6 at https://www.debian.org/doc/debian-policy/ch-relationships.html#s-replaces From the attached log (scroll to the bottom...): Selecting previously unselected package ruby-actionpack. Unpacking ruby-actionpack (from .../ruby-actionpack_2%3a2.3.14.2_all.deb) ... Selecting previously unselected package ruby-actionpack-page-caching. Unpacking ruby-actionpack-page-caching (from .../ruby-actionpack-page-caching_1.0.2-1_all.deb) ... dpkg: error processing /var/cache/apt/archives/ruby-actionpack-page-caching_1.0.2-1_all.deb (--unpack): trying to overwrite '/usr/lib/ruby/vendor_ruby/action_controller/caching/pages.rb', which is also in package ruby-actionpack-2.3 2.3.14-5 Errors were encountered while processing: /var/cache/apt/archives/ruby-actionpack-page-caching_1.0.2-1_all.deb ruby-actionpack-2.3 is not part of jessie, but there is no upgrade path guarantee that this obsolete package will be removed on upgrades to from wheezy to jessie, so ruby-actionpack-page-caching (which will not be part of jessie either) will have to add the corresponding Breaks+Replaces: ruby-actionpack-2.3 anyway to ensure this package gets removed during the jessie-stretch upgrade path. cheers, Andreas ruby-actionpack-2.3=2.3.14-5_ruby-actionpack-page-caching=1.0.2-1.log.gz Description: application/gzip
Bug#779579: installer broken: multipath-udeb depends on non-existent libgcc1 udeb
Control: tags -1 patch
Hi Siresh,
On 03/03/2015 08:32 AM, Mauricio Faria de Oliveira wrote:
Sure, I can try and should send a patch soon.
I've modified the build-arch target to build multipath-udeb first,
and store its output in a different directory; and the install target
to use that dir only for dh_install of multipath-udeb.
May you please consider it for an upload?
The solution ended up being to statically link to libgcc. I implemented
Cyril's suggestion, adopted by espeakup-udeb, but unfortunately it didnt
remove the references to libgcc. (verified with objdump runtime test).
(BTW, espeakup-udeb is broken too; that approach no longer works.)
~ # anna-install espeakup-udeb
~ # espeakup
espeakup: error while loading shared libraries: libgcc_s.so.1: cannot
open shared object file: No such file or directory
With the patch applied, the multipath command runs fine:
~ # multipath -l
multipath: error while loading shared libraries: libgcc_s.so.1: cannot
open shared object file: No such file or directory
~ # udpkg -i multipath-udeb_0.5.0-5mauricfo1_ppc64el.udeb
(Reading database...)
(Updating database...)
~ # multipath -l
~ # echo $?
0
Here's a check that changes are contained in the multipath-udeb package.
The references to libgcc are gone, only libpthread remains (which is OK,
as it exists in the installer). The nm/sed tests are based on Cyril's
earlier statement (thanks).
udeb (no libgcc):
$ dpkg-deb -x multipath-udeb_0.5.0-5mauricfo1_ppc64el.udeb lib-udeb
$ objdump -x lib-udeb/lib/libmultipath.so.0 | grep libgcc
$ { nm -D lib-udeb/lib/libmultipath.so.0 | sed -n 's,^.*U ,,p'; nm -D
/lib/powerpc64le-linux-gnu/libgcc_s.so.1 | sed -n 's,.*[^U] ,,p'; } |
sort | uniq -d
pthread_mutex_lock
pthread_mutex_unlock
~ # find /lib -name 'libpthread*'
/lib/libpthread.so.0
/lib/libpthread-2.19.so
deb (no change; still references libgcc)
$ dpkg-deb -x multipath-tools_0.5.0-5mauricfo1_ppc64el.deb lib-deb
$ objdump -x lib-deb/lib/libmultipath.so.0 | grep libgcc
NEEDED libgcc_s.so.1
required from libgcc_s.so.1:
$ { nm -D lib-deb/lib/libmultipath.so.0 | sed -n 's,^.*U ,,p'; nm -D
/lib/powerpc64le-linux-gnu/libgcc_s.so.1 | sed -n 's,.*[^U] ,,p'; } |
sort | uniq -d
__gcc_personality_v0
pthread_mutex_lock
pthread_mutex_unlock
_Unwind_Resume
--
Mauricio Faria de Oliveira
IBM Linux Technology Center
diff -Nru multipath-tools-0.5.0/debian/changelog
multipath-tools-0.5.0/debian/changelog
--- multipath-tools-0.5.0/debian/changelog 2014-09-16 06:29:29.0
-0300
+++ multipath-tools-0.5.0/debian/changelog 2015-03-03 15:54:28.0
-0300
@@ -1,3 +1,9 @@
+multipath-tools (0.5.0-5mauricfo1) UNRELEASED; urgency=medium
+
+ * Build multipath-udeb with static libgcc (Closes: #779579)
+
+ -- Mauricio Faria de Oliveira mauri...@linux.vnet.ibm.com Tue, 03 Mar 2015
15:52:58 -0300
+
multipath-tools (0.5.0-5) unstable; urgency=medium
* [5f967eb] Better daemon status in init's status action.
diff -Nru multipath-tools-0.5.0/debian/rules multipath-tools-0.5.0/debian/rules
--- multipath-tools-0.5.0/debian/rules 2014-09-05 09:14:33.0 -0300
+++ multipath-tools-0.5.0/debian/rules 2015-03-03 15:50:32.0 -0300
@@ -27,7 +26,7 @@
build: build-arch build-indep
-build-arch: build-stamp
+build-arch: build-multipath-udeb-stamp build-stamp
build-indep: build-stamp
build-stamp:
@@ -39,15 +38,30 @@
touch $@
+# multipath-udeb: build separately; don't reference dynamic libgcc at runtime
(#779579)
+build-multipath-udeb-stamp:
+ dh_testdir
+
+ DEB_CFLAGS_MAINT_APPEND=-static-libgcc $(MAKE) $(OPTFLAGS) LIB=lib
+
+ # store files for install target
+ mkdir -p $(CURDIR)/debian/tmp-multipath-udeb/sbin
+ $(MAKE) install INSTALL_PROGRAM=$(INSTALL_PROGRAM)
DESTDIR=$(CURDIR)/debian/tmp-multipath-udeb LIB=lib
+
+ $(MAKE) clean
+
+ touch $@
+
clean-tree:
$(MAKE) clean
clean: clean-tree
dh_testdir
- rm -f build-stamp
+ rm -f build-stamp build-multipath-udeb-stamp
dh_prep
debconf-updatepo
rm -rf debian/*.debhelper.log
+ rm -rf debian/tmp-multipath-udeb
install:
dh_testdir
@@ -58,7 +72,8 @@
mkdir -p $(CURDIR)/debian/tmp/sbin
$(MAKE) install INSTALL_PROGRAM=$(INSTALL_PROGRAM)
DESTDIR=$(CURDIR)/debian/tmp LIB=lib
install -m 755 debian/dmsetup_env $(CURDIR)/debian/tmp/lib/udev/
- dh_install -X.rules --fail-missing --sourcedir=$(CURDIR)/debian/tmp
+ dh_install -X.rules --fail-missing -Nmultipath-udeb
--sourcedir=$(CURDIR)/debian/tmp
+ dh_install -X.rules --fail-missing -pmultipath-udeb
--sourcedir=$(CURDIR)/debian/tmp-multipath-udeb
# initramfs stuff:
install -D -m 755
Bug#779666: qtsmbstatus-server: fails to upgrade from 'wheezy': insserv: Service samba has to be enabled to start service qtsmbstatusd
Package: qtsmbstatus-server Version: 2.2.1-3 Severity: serious User: debian...@lists.debian.org Usertags: piuparts Hi, during a test with piuparts I noticed your package fails to upgrade from 'wheezy'. It installed fine in 'wheezy', then the upgrade to 'jessie' fails. From the attached log (scroll to the bottom...): Setting up samba (2:4.1.17+dfsg-1) ... Installing new version of config file /etc/init.d/samba ... Installing new version of config file /etc/logrotate.d/samba ... update-alternatives: warning: alternative /usr/bin/smbstatus.samba3 (part of link group smbstatus) doesn't exist; removing from list of alternatives update-alternatives: warning: /etc/alternatives/smbstatus is dangling; it will be updated with best choice insserv: Service samba has to be enabled to start service qtsmbstatusd insserv: exiting now! update-rc.d: error: insserv rejected the script header dpkg: error processing package samba (--configure): subprocess installed post-installation script returned error exit status 1 dpkg: dependency problems prevent configuration of qtsmbstatus-server: qtsmbstatus-server depends on samba; however: Package samba is not configured yet. dpkg: error processing package qtsmbstatus-server (--configure): dependency problems - leaving unconfigured This is caused by the incompatible dependencies in the *old* qtsmbstatusd initscript, but that won't be replaced before the configure stage (which requires samba to be configured first). Being activated, the old initscripts causes insserv to error out. The recently added Breaks in samba is not sufficient to fix this. This is especially a problem for wheezy-jessie upgrades since jessie has no qtsmbstatus-server package. cheers, Andreas qtsmbstatus-server_2.2.1-3.log.gz Description: application/gzip
Bug#705092: silversearcher-ag and python-ase: error when trying to install together
Package: silversearcher-ag Followup-For: Bug #705092 back again ... Selecting previously unselected package silversearcher-ag. Unpacking silversearcher-ag (from .../silversearcher-ag_0.28.0-1_amd64.deb) ... dpkg: error processing /var/cache/apt/archives/silversearcher-ag_0.28.0-1_amd64.deb (--unpack): trying to overwrite '/usr/share/man/man1/ag.1.gz', which is also in package python-ase 3.6.0.2515-1 Errors were encountered while processing: /var/cache/apt/archives/silversearcher-ag_0.28.0-1_amd64.deb Andreas python-ase=3.6.0.2515-1_silversearcher-ag=0.28.0-1.log.gz Description: application/gzip
Bug#779664: ffmpeg: needs Breaks+Replaces: libav-tools ( 6:9~)
Control: tags -1 pending Hi Andreas, On 03.03.2015 20:46, Andreas Beckmann wrote: during a test with piuparts I noticed your package fails to co-install with libav-tools from wheezy. Thanks for all your testing with piuparts. :) Since there is no ffmpeg package in jessie, adding these Breaks+Replaces would ease some upgrade paths from wheezy as well as possible backporting. Indeed. In libav (6:9~beta1-1) the compatibility links for ff* tools were removed. I just added the Breaks+Replaces in git [1]. Best regards, Andreas 1: https://anonscm.debian.org/cgit/collab-maint/ffmpeg.git/commit/?id=705a1ffdfcccf83f1892353951378d9e9526804e -- To UNSUBSCRIBE, email to debian-bugs-rc-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Processed: reopen 747863
Processing commands for cont...@bugs.debian.org:
# 747863 isn't fixed
reopen 747863
Bug #747863 {Done: Laurent Bigonville bi...@debian.org} [nut-client] systemd
service fails by default and causes package install failure
Bug #771887 {Done: Laurent Bigonville bi...@debian.org} [nut-client]
nut-client: Does not install cleanly
Bug #773750 {Done: Laurent Bigonville bi...@debian.org} [nut-client]
nut-client: Fails to install
'reopen' may be inappropriate when a bug has been closed with a version;
all fixed versions will be cleared, and you may need to re-add them.
Bug reopened
No longer marked as fixed in versions nut/2.7.2-2.
No longer marked as fixed in versions nut/2.7.2-2.
No longer marked as fixed in versions nut/2.7.2-2.
thanks
Stopping processing here.
Please contact me if you need assistance.
--
747863: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=747863
771887: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=771887
773750: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=773750
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: Bug#779664: ffmpeg: needs Breaks+Replaces: libav-tools ( 6:9~)
Processing control commands: tags -1 pending Bug #779664 [ffmpeg] ffmpeg: needs Breaks+Replaces: libav-tools ( 6:9~) Added tag(s) pending. -- 779664: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=779664 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#779672: Multi-Line Architecture fields are not allowed per Debian policy
Package: src:calendarserer Version: 5.2.2+dfsg-2 Severity: serious Tags: sid jessie Multi-Line Architecture fields are not allowed per Debian policy. Please either use linux-any (preferred), or a one-liner. -- To UNSUBSCRIBE, email to debian-bugs-rc-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#779117: marked as done (pure-ftpd-common: depend on perl instead of perl-modules)
Your message dated Tue, 03 Mar 2015 21:49:40 + with message-id e1ysuha-0003my...@franck.debian.org and subject line Bug#779117: fixed in pure-ftpd 1.0.36-3.2 has caused the Debian Bug report #779117, regarding pure-ftpd-common: depend on perl instead of perl-modules 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.) -- 779117: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=779117 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems ---BeginMessage--- Package: pure-ftpd-common Version: 1.0.36-3.1 Severity: serious Justification: blocks another serious bug According to the package description of perl-modules, other packages should not depend on it, since it is considered an internal implementation detail of the perl package. At present we are dealing with an RC bug[1] in perl which is exacerbated by such dependencies. As such, please could you replace Depends: perl-modules with Depends: perl NMUs will be forthcoming; feel free to let me know whether you prefer to handle this as a maintainer upload or not. Thanks, Dominic. [1] https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=777597#32 ---End Message--- ---BeginMessage--- Source: pure-ftpd Source-Version: 1.0.36-3.2 We believe that the bug you reported is fixed in the latest version of pure-ftpd, 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 779...@bugs.debian.org, and the maintainer will reopen the bug report if appropriate. Debian distribution maintenance software pp. gregor herrmann gre...@debian.org (supplier of updated pure-ftpd 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: Wed, 25 Feb 2015 22:20:30 +0100 Source: pure-ftpd Binary: pure-ftpd-common pure-ftpd pure-ftpd-mysql pure-ftpd-postgresql pure-ftpd-ldap Architecture: source all amd64 Version: 1.0.36-3.2 Distribution: unstable Urgency: medium Maintainer: Stefan Hornburg (Racke) ra...@linuxia.de Changed-By: gregor herrmann gre...@debian.org Description: pure-ftpd - Secure and efficient FTP server pure-ftpd-common - Pure-FTPd FTP server (Common Files) pure-ftpd-ldap - Secure and efficient FTP server with LDAP user authentication pure-ftpd-mysql - Secure and efficient FTP server with MySQL user authentication pure-ftpd-postgresql - Secure and efficient FTP server with PostgreSQL user authenticati Closes: 779117 Changes: pure-ftpd (1.0.36-3.2) unstable; urgency=medium . * Non-maintainer upload. * Fix depend on perl instead of perl-modules: debian/control: update Depends for pure-ftpd-common. (Closes: #779117) Checksums-Sha1: 9a23307cba516499278d683622128405d9d9f472 2398 pure-ftpd_1.0.36-3.2.dsc 59594bfc75585e40d1e9776451b7a99094556461 49258 pure-ftpd_1.0.36-3.2.diff.gz af5079d301cf79372a3239ad373e23c0be1de372 187230 pure-ftpd-common_1.0.36-3.2_all.deb 4b2c9b945f0d16b5f9185b5b9ce0c6df517526ac 108886 pure-ftpd_1.0.36-3.2_amd64.deb 7b12f37d4a951ef73bab4ff61911312608a09b91 118382 pure-ftpd-mysql_1.0.36-3.2_amd64.deb e6b46e68d066128413e79a48c880e8a488e02969 117742 pure-ftpd-postgresql_1.0.36-3.2_amd64.deb 7c60359dde16d876d6315397a935faeba5e9ded4 117242 pure-ftpd-ldap_1.0.36-3.2_amd64.deb Checksums-Sha256: 9a9bb8d269e3bc21507a8897d7cf627d693c073eeed3585c9a457b20d0dd 2398 pure-ftpd_1.0.36-3.2.dsc 15a1f4e55e2122cd46d737de8215ad9d50215807cf19ce12ca907b8068588598 49258 pure-ftpd_1.0.36-3.2.diff.gz e5698a78cefc51653165d79318a0962b5e069d77e92207f74a4c30e84b9f9071 187230 pure-ftpd-common_1.0.36-3.2_all.deb c9670a1d85fe9bae32f10714050bf3209acdd5f52ff02bb63ef12cc4248d99c1 108886 pure-ftpd_1.0.36-3.2_amd64.deb 6734b6b9c5bc9fbd0e07c58a68c74bf58f9ed54033e92e190403e760c1a69f54 118382 pure-ftpd-mysql_1.0.36-3.2_amd64.deb ea3e25db0da427102edadbd1012e1126782d6c4dcc698fb4e4b0548de3088129 117742 pure-ftpd-postgresql_1.0.36-3.2_amd64.deb 2f6c938f5139105f325b57b80f0a95360f651fc41d4daf9d3268ffdb7179eb6c 117242 pure-ftpd-ldap_1.0.36-3.2_amd64.deb Files: 86d98382b107f0446d7d3031c232a6a5 2398 net optional pure-ftpd_1.0.36-3.2.dsc 533b1e2cf375f7266394e740430935f2 49258 net optional pure-ftpd_1.0.36-3.2.diff.gz d377ba3875cae11c809fdcaeaeffeb57 187230 net optional pure-ftpd-common_1.0.36-3.2_all.deb c18a970df8940630ac6d1c0eddff3aa6 108886 net
Bug#779125: marked as done (mono-fastcgi-server4: depend on perl instead of perl-modules)
Your message dated Tue, 03 Mar 2015 21:50:00 + with message-id e1ysuhu-0003zw...@franck.debian.org and subject line Bug#779125: fixed in xsp 3.8-2.1 has caused the Debian Bug report #779125, regarding mono-fastcgi-server4: depend on perl instead of perl-modules 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.) -- 779125: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=779125 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems ---BeginMessage--- Package: mono-fastcgi-server4 Version: 3.8-2 Severity: serious Justification: blocks another serious bug According to the package description of perl-modules, other packages should not depend on it, since it is considered an internal implementation detail of the perl package. At present we are dealing with an RC bug[1] in perl which is exacerbated by such dependencies. As such, please could you replace Depends: perl-modules with Depends: perl NMUs will be forthcoming; feel free to let me know whether you prefer to handle this as a maintainer upload or not. Thanks, Dominic. [1] https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=777597#32 ---End Message--- ---BeginMessage--- Source: xsp Source-Version: 3.8-2.1 We believe that the bug you reported is fixed in the latest version of xsp, 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 779...@bugs.debian.org, and the maintainer will reopen the bug report if appropriate. Debian distribution maintenance software pp. Damyan Ivanov d...@debian.org (supplier of updated xsp 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: Wed, 25 Feb 2015 21:14:04 + Source: xsp Binary: dh-xsp mono-xsp2-base mono-xsp4-base mono-xsp4 mono-xsp2 mono-xsp asp.net-examples mono-apache-server4 mono-apache-server2 mono-apache-server mono-fpm-server libfpm-helper0 mono-fastcgi-server4 mono-fastcgi-server2 mono-fastcgi-server Architecture: source all amd64 Version: 3.8-2.1 Distribution: unstable Urgency: high Maintainer: Debian Mono Group pkg-mono-gr...@lists.alioth.debian.org Changed-By: Damyan Ivanov d...@debian.org Description: asp.net-examples - demo pages for ASP.NET infrastructure dh-xsp - debhelper add-on to handle ASP.NET sites libfpm-helper0 - ASP.NET backend for FastCGI Process Manager - helper lib mono-apache-server - ASP.NET backend for mod_mono Apache module - default version mono-apache-server2 - ASP.NET 2.0 backend for mod_mono2 Apache module mono-apache-server4 - ASP.NET 4.5 backend for mod_mono Apache module mono-fastcgi-server - ASP.NET backend for FastCGI webservers - default version mono-fastcgi-server2 - ASP.NET 2.0 backend for FastCGI webservers mono-fastcgi-server4 - ASP.NET 4.0 backend for FastCGI webservers mono-fpm-server - ASP.NET backend for FastCGI Process Manager mono-xsp - simple web server to run ASP.NET applications - default version mono-xsp2 - simple web server to run ASP.NET 2.0 applications mono-xsp2-base - base libraries for XSP 2.0 mono-xsp4 - simple web server to run ASP.NET 4.0 applications mono-xsp4-base - base libraries for XSP 4.0 Closes: 779122 779124 779125 Changes: xsp (3.8-2.1) unstable; urgency=high . * Non-maintainer upload fixing bugs blocking serious bug #777597 -- perl-modules: upgrade regression: dpkg: dependency problems prevent configuration of perl-modules . * replace dependencies on 'perl-modules' with 'perl' as per Perl policy (Closes: #779124, #779122, #779125) Checksums-Sha1: ba7eebb76a9a94d78da56db2368dde42ca0f8a14 2900 xsp_3.8-2.1.dsc b7664f0d46e7e87cf2e2e584bc3afa5d6e09c102 46192 xsp_3.8-2.1.debian.tar.xz c16055f25661a7391be0517ef2dcdba44b2b33e7 49862 dh-xsp_3.8-2.1_all.deb 5492a8090e9d2d07b50ad60dd37ec24ff36013d2 79354 mono-xsp2-base_3.8-2.1_all.deb 3814c1aff763ac4127ef6b1cd1baed99c85431e8 79416 mono-xsp4-base_3.8-2.1_all.deb d9653372196c3fe57fe28a32a7c04e517ce05a05 94684 mono-xsp4_3.8-2.1_all.deb e53cb5c52fe8a042c43c4ca1a5e9ef5914c3623f 95066 mono-xsp2_3.8-2.1_all.deb 158285bd4714b74f895139b7cc623f89f9111ed1 44650 mono-xsp_3.8-2.1_all.deb cb58182d4ad7bf3e3fe8630aa16188a78bc2711e 107826 asp.net-examples_3.8-2.1_all.deb 8a39d23c740c80ed2076c183c257ff0fea53141d 85624 mono-apache-server4_3.8-2.1_all.deb
Bug#779124: marked as done (mono-fastcgi-server2: depend on perl instead of perl-modules)
Your message dated Tue, 03 Mar 2015 21:50:00 + with message-id e1ysuhu-0003zq...@franck.debian.org and subject line Bug#779124: fixed in xsp 3.8-2.1 has caused the Debian Bug report #779124, regarding mono-fastcgi-server2: depend on perl instead of perl-modules 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.) -- 779124: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=779124 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems ---BeginMessage--- Package: mono-fastcgi-server2 Version: 3.8-2 Severity: serious Justification: blocks another serious bug According to the package description of perl-modules, other packages should not depend on it, since it is considered an internal implementation detail of the perl package. At present we are dealing with an RC bug[1] in perl which is exacerbated by such dependencies. As such, please could you replace Depends: perl-modules with Depends: perl NMUs will be forthcoming; feel free to let me know whether you prefer to handle this as a maintainer upload or not. Thanks, Dominic. [1] https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=777597#32 ---End Message--- ---BeginMessage--- Source: xsp Source-Version: 3.8-2.1 We believe that the bug you reported is fixed in the latest version of xsp, 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 779...@bugs.debian.org, and the maintainer will reopen the bug report if appropriate. Debian distribution maintenance software pp. Damyan Ivanov d...@debian.org (supplier of updated xsp 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: Wed, 25 Feb 2015 21:14:04 + Source: xsp Binary: dh-xsp mono-xsp2-base mono-xsp4-base mono-xsp4 mono-xsp2 mono-xsp asp.net-examples mono-apache-server4 mono-apache-server2 mono-apache-server mono-fpm-server libfpm-helper0 mono-fastcgi-server4 mono-fastcgi-server2 mono-fastcgi-server Architecture: source all amd64 Version: 3.8-2.1 Distribution: unstable Urgency: high Maintainer: Debian Mono Group pkg-mono-gr...@lists.alioth.debian.org Changed-By: Damyan Ivanov d...@debian.org Description: asp.net-examples - demo pages for ASP.NET infrastructure dh-xsp - debhelper add-on to handle ASP.NET sites libfpm-helper0 - ASP.NET backend for FastCGI Process Manager - helper lib mono-apache-server - ASP.NET backend for mod_mono Apache module - default version mono-apache-server2 - ASP.NET 2.0 backend for mod_mono2 Apache module mono-apache-server4 - ASP.NET 4.5 backend for mod_mono Apache module mono-fastcgi-server - ASP.NET backend for FastCGI webservers - default version mono-fastcgi-server2 - ASP.NET 2.0 backend for FastCGI webservers mono-fastcgi-server4 - ASP.NET 4.0 backend for FastCGI webservers mono-fpm-server - ASP.NET backend for FastCGI Process Manager mono-xsp - simple web server to run ASP.NET applications - default version mono-xsp2 - simple web server to run ASP.NET 2.0 applications mono-xsp2-base - base libraries for XSP 2.0 mono-xsp4 - simple web server to run ASP.NET 4.0 applications mono-xsp4-base - base libraries for XSP 4.0 Closes: 779122 779124 779125 Changes: xsp (3.8-2.1) unstable; urgency=high . * Non-maintainer upload fixing bugs blocking serious bug #777597 -- perl-modules: upgrade regression: dpkg: dependency problems prevent configuration of perl-modules . * replace dependencies on 'perl-modules' with 'perl' as per Perl policy (Closes: #779124, #779122, #779125) Checksums-Sha1: ba7eebb76a9a94d78da56db2368dde42ca0f8a14 2900 xsp_3.8-2.1.dsc b7664f0d46e7e87cf2e2e584bc3afa5d6e09c102 46192 xsp_3.8-2.1.debian.tar.xz c16055f25661a7391be0517ef2dcdba44b2b33e7 49862 dh-xsp_3.8-2.1_all.deb 5492a8090e9d2d07b50ad60dd37ec24ff36013d2 79354 mono-xsp2-base_3.8-2.1_all.deb 3814c1aff763ac4127ef6b1cd1baed99c85431e8 79416 mono-xsp4-base_3.8-2.1_all.deb d9653372196c3fe57fe28a32a7c04e517ce05a05 94684 mono-xsp4_3.8-2.1_all.deb e53cb5c52fe8a042c43c4ca1a5e9ef5914c3623f 95066 mono-xsp2_3.8-2.1_all.deb 158285bd4714b74f895139b7cc623f89f9111ed1 44650 mono-xsp_3.8-2.1_all.deb cb58182d4ad7bf3e3fe8630aa16188a78bc2711e 107826 asp.net-examples_3.8-2.1_all.deb 8a39d23c740c80ed2076c183c257ff0fea53141d 85624 mono-apache-server4_3.8-2.1_all.deb
Bug#779114: marked as done (patcher: depend on perl instead of perl-modules)
Your message dated Tue, 03 Mar 2015 21:36:19 + with message-id e1ysuuf-0001xu...@franck.debian.org and subject line Bug#779114: fixed in patcher 0.0.20040521-6.1 has caused the Debian Bug report #779114, regarding patcher: depend on perl instead of perl-modules 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.) -- 779114: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=779114 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems ---BeginMessage--- Package: patcher Version: 0.0.20040521-6 Severity: serious Justification: blocks another serious bug According to the package description of perl-modules, other packages should not depend on it, since it is considered an internal implementation detail of the perl package. At present we are dealing with an RC bug[1] in perl which is exacerbated by such dependencies. As such, please could you replace Depends: perl-modules with Depends: perl NMUs will be forthcoming; feel free to let me know whether you prefer to handle this as a maintainer upload or not. Thanks, Dominic. [1] https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=777597#32 ---End Message--- ---BeginMessage--- Source: patcher Source-Version: 0.0.20040521-6.1 We believe that the bug you reported is fixed in the latest version of patcher, 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 779...@bugs.debian.org, and the maintainer will reopen the bug report if appropriate. Debian distribution maintenance software pp. gregor herrmann gre...@debian.org (supplier of updated patcher 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: Wed, 25 Feb 2015 21:46:14 +0100 Source: patcher Binary: patcher Architecture: source all Version: 0.0.20040521-6.1 Distribution: unstable Urgency: medium Maintainer: Alejandro Rios P. aler...@debian.org Changed-By: gregor herrmann gre...@debian.org Description: patcher- perl script useful for managing patches Closes: 779114 Changes: patcher (0.0.20040521-6.1) unstable; urgency=medium . * Non-maintainer upload. * Fix depend on perl instead of perl-modules: debian/control: update Depends: plain perl it is. (Closes: #779114) Checksums-Sha1: d733d66e6081080dbe7103915cc67d43902a3d63 1828 patcher_0.0.20040521-6.1.dsc 4e74639205ea85f947ff9090f2893b821a064b6f 7568 patcher_0.0.20040521-6.1.debian.tar.xz 2b386e08f2e51e5dcb9038c22a91142ad2bc38e0 21728 patcher_0.0.20040521-6.1_all.deb Checksums-Sha256: f12e89566a9316f2874f4d7f2632ff718777c9edf2aa8d67f5a98deb023407a9 1828 patcher_0.0.20040521-6.1.dsc 0d8a454f62d9f6a408ea4cd3bb3fdc0bf30955e328457434f4d14b35ec7a3406 7568 patcher_0.0.20040521-6.1.debian.tar.xz 92a83c3757fb68dc1e042d0be166b64a8b7244a4554d75dc5c23da5b8e133697 21728 patcher_0.0.20040521-6.1_all.deb Files: e11eac3cf986ee66fef7eef5ee4ede48 1828 devel optional patcher_0.0.20040521-6.1.dsc 1d90b09469b94146dad68148745a7083 7568 devel optional patcher_0.0.20040521-6.1.debian.tar.xz e5820470fb920cc8df96ff78aead5987 21728 devel optional patcher_0.0.20040521-6.1_all.deb -BEGIN PGP SIGNATURE- Version: GnuPG v1 iQJ8BAEBCgBmBQJU7jS8XxSAAC4AKGlzc3Vlci1mcHJAbm90YXRpb25zLm9w ZW5wZ3AuZmlmdGhob3JzZW1hbi5uZXREMUUxMzE2RTkzQTc2MEE4MTA0RDg1RkFC QjNBNjgwMTg2NDlBQTA2AAoJELs6aAGGSaoGsZgP/iFUtZAdB0l1kTHxPzDz2WT3 4pOB7swJFXr5Bxqbbkp0W7SDXlOZI1CApgg1dYzZmafYzgFyzPhAk9QViIi4bw1B DZzRNJul/6gW8cuGIqQpggYvcx3jCrZhz9NdI0l8/wGgoqd7fkLc+5hi7p6r/wIf P+bzL86EnWvOWzKYgE9qErTtNvD7wpH/aVFHuCYggJ4W/RvywVCx9aiz7PcY5y36 rEDJpr04CNVpspATYe0OwJEpY+ocjntlB7WeDEg4B3DGK5nZBE3Q4FteROBlnzuQ T0Kcj0CPP4W10MAb4UeiccpmbjSM1QHTgledCIgdPJjURYP8FWX2sFkZPtZN6sst /uM7GtwMglXqddF09mtkBPhrcESOxIXLuR/OrCnW2cH5feA0YCCf5g1jQ3qFF4Yl AhFRYD5D0aMtR9fiCfDm91VfwCr0e20KjZG4mSM3bbxFs+1U2tfoRw1UfXdQuWoe dyoPRWuqqtUocvAf/Fj138lhrVZhvFclopKDbuOUawdM3bGQnu5zDaPFqd8iXmA5 sLWAOWwBEdsrDfPWQwRdM/bK53QVzTkXjiIeAwLZc5XEaNhiPOkOA0Z1SYPrE/L3 3JGndlaoJ9zuLLObaTdviITBkZtKMEZR+6YadhXaO/oOyAWVRv+biRtEpc1iStaL Ir7fJfa+YJWpdJbgOF7g =SbYA -END PGP SIGNATUREEnd Message---
Bug#779312: freerdp-x11: Segfaults on start 100% of the time
Removing those parameters indeed fixes the crash.
John
On 03/01/2015 08:00 AM, Bernhard Übelacker wrote:
Hello John Goerzen,
I was able to reproduce a crash with xfreerdp.
First a question:
does the crash still happen, if you omit this part of the command line:
--plugin rdpsnd --data alsa latency:100 --
---
After installing the 5 *-dbg packages I get such a stack:
gdb --args xfreerdp --plugin rdpsnd --data alsa latency:100 --
/v:192.168.178.45
directory libfreerdp/core:libfreerdp/common:client/common
set height 0
set width 0
run
Starting program: /usr/bin/xfreerdp --plugin rdpsnd --data alsa
latency:100 -- /v:192.168.178.45
[Thread debugging using libthread_db enabled]
Using host libthread_db library
/lib/x86_64-linux-gnu/libthread_db.so.1.
Program received signal SIGSEGV, Segmentation fault.
0x75bb058c in freerdp_static_channel_collection_add
(settings=settings@entry=0x65ac10, channel=channel@entry=0x666bb0) at
/build/freerdp-oDMFQO/freerdp-1.1.0~git20140921.1.440916e+dfsg1/libfreerdp/common/settings.c:214
214
settings-StaticChannelArray[settings-StaticChannelCount++] = channel;
(gdb) bt
#0 0x75bb058c in freerdp_static_channel_collection_add
(settings=settings@entry=0x65ac10, channel=channel@entry=0x666bb0) at
/build/freerdp-oDMFQO/freerdp-1.1.0~git20140921.1.440916e+dfsg1/libfreerdp/common/settings.c:214
#1 0x76ce5563 in freerdp_client_add_static_channel
(settings=settings@entry=0x65ac10, count=optimized out, params=0x666b60) at
/build/freerdp-oDMFQO/freerdp-1.1.0~git20140921.1.440916e+dfsg1/client/common/cmdline.c:393
#2 0x76ce8252 in freerdp_client_old_process_plugin
(settings=settings@entry=0x65ac10, args=args@entry=0x666b40) at
/build/freerdp-oDMFQO/freerdp-1.1.0~git20140921.1.440916e+dfsg1/client/common/compatibility.c:176
#3 0x76ce863c in freerdp_client_old_command_line_pre_filter
(context=context@entry=0x65ac10, index=5, index@entry=1, argc=argc@entry=8,
argv=argv@entry=0x7fffe018) at
/build/freerdp-oDMFQO/freerdp-1.1.0~git20140921.1.440916e+dfsg1/client/common/compatibility.c:292
#4 0x73baed6e in CommandLineParseArgumentsA
(argc=argc@entry=8, argv=argv@entry=0x7fffe018,
options=options@entry=0x76efd1c0 old_args, flags=flags@entry=1036,
context=context@entry=0x65ac10, preFilter=preFilter@entry=0x76ce83e0
freerdp_client_old_command_line_pre_filter, postFilter=0x0) at
/build/freerdp-oDMFQO/freerdp-1.1.0~git20140921.1.440916e+dfsg1/winpr/libwinpr/utils/cmdline.c:88
#5 0x76ce884b in freerdp_detect_old_command_line_syntax
(argc=argc@entry=8, argv=argv@entry=0x7fffe018,
count=count@entry=0x7fffddcc) at
/build/freerdp-oDMFQO/freerdp-1.1.0~git20140921.1.440916e+dfsg1/client/common/compatibility.c:346
#6 0x76ce5ff2 in freerdp_client_detect_command_line (argc=8,
argv=0x7fffe018, flags=0x7fffde30) at
/build/freerdp-oDMFQO/freerdp-1.1.0~git20140921.1.440916e+dfsg1/client/common/cmdline.c:911
#7 0x76ce62b3 in freerdp_client_parse_command_line_arguments
(argc=8, argv=0x7fffe018, settings=0x60e8e0) at
/build/freerdp-oDMFQO/freerdp-1.1.0~git20140921.1.440916e+dfsg1/client/common/cmdline.c:1014
#8 0x76ce4d56 in freerdp_client_parse_command_line
(context=context@entry=0x609420, argc=argc@entry=8,
argv=argv@entry=0x7fffe018) at
/build/freerdp-oDMFQO/freerdp-1.1.0~git20140921.1.440916e+dfsg1/client/common/client.c:111
#9 0x00401be8 in main (argc=8, argv=0x7fffe018) at
/build/freerdp-oDMFQO/freerdp-1.1.0~git20140921.1.440916e+dfsg1/client/X11/cli/xfreerdp.c:56
(gdb) print settings-StaticChannelArray
$1 = (ADDIN_ARGV **) 0x0
(gdb) print settings-StaticChannelCount
$2 = 2
(gdb) print channel
$3 = (ADDIN_ARGV *) 0x666bb0
(gdb) print settings-StaticChannelArraySize
$4 = 0
---
In my opinion the problem lies in the initialization of the settings
structure.
In freerdp_detect_old_command_line_syntax the settings are only allocated
and
the whole memory set to 0. Therefore StaticChannelArraySize is 0.
Later when we get into this function we enter the if block. But because
StaticChannelArraySize equals still 0 the *= 2 has no effect and it stays 0.
Therefore the realloc is done with size 0. Therefore a null pointer is
returned.
void freerdp_static_channel_collection_add(rdpSettings* settings, ADDIN_ARGV*
channel)
{
if (settings-StaticChannelArraySize (settings-StaticChannelCount +
1))
{
settings-StaticChannelArraySize *= 2;
settings-StaticChannelArray = (ADDIN_ARGV**)
realloc(settings-StaticChannelArray,
Bug#779122: marked as done (mono-apache-server2: depend on perl instead of perl-modules)
Your message dated Tue, 03 Mar 2015 21:50:00 + with message-id e1ysuhu-0003zk...@franck.debian.org and subject line Bug#779122: fixed in xsp 3.8-2.1 has caused the Debian Bug report #779122, regarding mono-apache-server2: depend on perl instead of perl-modules 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.) -- 779122: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=779122 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems ---BeginMessage--- Package: mono-apache-server2 Version: 3.8-2 Severity: serious Justification: blocks another serious bug According to the package description of perl-modules, other packages should not depend on it, since it is considered an internal implementation detail of the perl package. At present we are dealing with an RC bug[1] in perl which is exacerbated by such dependencies. As such, please could you replace Depends: perl-modules with Depends: perl NMUs will be forthcoming; feel free to let me know whether you prefer to handle this as a maintainer upload or not. Thanks, Dominic. [1] https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=777597#32 ---End Message--- ---BeginMessage--- Source: xsp Source-Version: 3.8-2.1 We believe that the bug you reported is fixed in the latest version of xsp, 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 779...@bugs.debian.org, and the maintainer will reopen the bug report if appropriate. Debian distribution maintenance software pp. Damyan Ivanov d...@debian.org (supplier of updated xsp 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: Wed, 25 Feb 2015 21:14:04 + Source: xsp Binary: dh-xsp mono-xsp2-base mono-xsp4-base mono-xsp4 mono-xsp2 mono-xsp asp.net-examples mono-apache-server4 mono-apache-server2 mono-apache-server mono-fpm-server libfpm-helper0 mono-fastcgi-server4 mono-fastcgi-server2 mono-fastcgi-server Architecture: source all amd64 Version: 3.8-2.1 Distribution: unstable Urgency: high Maintainer: Debian Mono Group pkg-mono-gr...@lists.alioth.debian.org Changed-By: Damyan Ivanov d...@debian.org Description: asp.net-examples - demo pages for ASP.NET infrastructure dh-xsp - debhelper add-on to handle ASP.NET sites libfpm-helper0 - ASP.NET backend for FastCGI Process Manager - helper lib mono-apache-server - ASP.NET backend for mod_mono Apache module - default version mono-apache-server2 - ASP.NET 2.0 backend for mod_mono2 Apache module mono-apache-server4 - ASP.NET 4.5 backend for mod_mono Apache module mono-fastcgi-server - ASP.NET backend for FastCGI webservers - default version mono-fastcgi-server2 - ASP.NET 2.0 backend for FastCGI webservers mono-fastcgi-server4 - ASP.NET 4.0 backend for FastCGI webservers mono-fpm-server - ASP.NET backend for FastCGI Process Manager mono-xsp - simple web server to run ASP.NET applications - default version mono-xsp2 - simple web server to run ASP.NET 2.0 applications mono-xsp2-base - base libraries for XSP 2.0 mono-xsp4 - simple web server to run ASP.NET 4.0 applications mono-xsp4-base - base libraries for XSP 4.0 Closes: 779122 779124 779125 Changes: xsp (3.8-2.1) unstable; urgency=high . * Non-maintainer upload fixing bugs blocking serious bug #777597 -- perl-modules: upgrade regression: dpkg: dependency problems prevent configuration of perl-modules . * replace dependencies on 'perl-modules' with 'perl' as per Perl policy (Closes: #779124, #779122, #779125) Checksums-Sha1: ba7eebb76a9a94d78da56db2368dde42ca0f8a14 2900 xsp_3.8-2.1.dsc b7664f0d46e7e87cf2e2e584bc3afa5d6e09c102 46192 xsp_3.8-2.1.debian.tar.xz c16055f25661a7391be0517ef2dcdba44b2b33e7 49862 dh-xsp_3.8-2.1_all.deb 5492a8090e9d2d07b50ad60dd37ec24ff36013d2 79354 mono-xsp2-base_3.8-2.1_all.deb 3814c1aff763ac4127ef6b1cd1baed99c85431e8 79416 mono-xsp4-base_3.8-2.1_all.deb d9653372196c3fe57fe28a32a7c04e517ce05a05 94684 mono-xsp4_3.8-2.1_all.deb e53cb5c52fe8a042c43c4ca1a5e9ef5914c3623f 95066 mono-xsp2_3.8-2.1_all.deb 158285bd4714b74f895139b7cc623f89f9111ed1 44650 mono-xsp_3.8-2.1_all.deb cb58182d4ad7bf3e3fe8630aa16188a78bc2711e 107826 asp.net-examples_3.8-2.1_all.deb 8a39d23c740c80ed2076c183c257ff0fea53141d 85624 mono-apache-server4_3.8-2.1_all.deb
Bug#779113: marked as done (cli-common: depend on perl instead of perl-modules)
Your message dated Tue, 03 Mar 2015 21:34:01 + with message-id e1ysus1-ya...@franck.debian.org and subject line Bug#779113: fixed in cli-common 0.9+nmu1 has caused the Debian Bug report #779113, regarding cli-common: depend on perl instead of perl-modules 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.) -- 779113: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=779113 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems ---BeginMessage--- Package: cli-common Version: 0.9 Severity: serious Justification: blocks another serious bug According to the package description of perl-modules, other packages should not depend on it, since it is considered an internal implementation detail of the perl package. At present we are dealing with an RC bug[1] in perl which is exacerbated by such dependencies. As such, please could you replace Depends: perl-modules with Depends: perl NMUs will be forthcoming; feel free to let me know whether you prefer to handle this as a maintainer upload or not. Thanks, Dominic. [1] https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=777597#32 ---End Message--- ---BeginMessage--- Source: cli-common Source-Version: 0.9+nmu1 We believe that the bug you reported is fixed in the latest version of cli-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 comments please address them to 779...@bugs.debian.org, and the maintainer will reopen the bug report if appropriate. Debian distribution maintenance software pp. Damyan Ivanov d...@debian.org (supplier of updated cli-common 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: Wed, 25 Feb 2015 20:56:32 + Source: cli-common Binary: cli-common cli-common-dev Architecture: source all Version: 0.9+nmu1 Distribution: unstable Urgency: medium Maintainer: Debian CLI Common Team pkg-cli-common-t...@lists.alioth.debian.org Changed-By: Damyan Ivanov d...@debian.org Description: cli-common - common files between all CLI packages cli-common-dev - common files for building CLI packages Closes: 779113 Changes: cli-common (0.9+nmu1) unstable; urgency=medium . * Non-maintainer upload fixing a bug blocking serious bug #777597 -- perl-modules: upgrade regression: dpkg: dependency problems prevent configuration of perl-modules . * replace dependencies on 'perl-modules' with just 'perl' as per Perl policy existence of perl-modules package is an implementation detail (Closes: #779113) Checksums-Sha1: 7a8fd98dfd133d2bdf4a015d1e69c2f7c942ed1b 1924 cli-common_0.9+nmu1.dsc a9b26beb46b5ccfbbe193279e9f30c3384789fd2 43343 cli-common_0.9+nmu1.tar.gz cd7a2117643d2fc4480775dd05d955600439a45a 175482 cli-common_0.9+nmu1_all.deb ea7b8a97278001a581b2af00eca5a3cde4c5fa8f 43676 cli-common-dev_0.9+nmu1_all.deb Checksums-Sha256: 5baaf58f51519ad8e9444b0c337a90948c33be41f64e775a8986d1ae46626033 1924 cli-common_0.9+nmu1.dsc 162b6da13736c5e882569f930de157323565f00168ddf9a1340a1f24bdd31bfd 43343 cli-common_0.9+nmu1.tar.gz a203a98a5be16c0751f0d6cdc8c21ccdbb5cbba55d9aa2b523fef1fdf6291c37 175482 cli-common_0.9+nmu1_all.deb 9b643c223621421f618365b4967b77e04cf8ee7a3b1e6c35e4774f9699f02b45 43676 cli-common-dev_0.9+nmu1_all.deb Files: b3c2a8cef340bfada34b81554b3eebf4 1924 cli-mono optional cli-common_0.9+nmu1.dsc 3eb38feaa73e03c6f13675083978a24a 43343 cli-mono optional cli-common_0.9+nmu1.tar.gz 65ee3aa119c7a25bcf2bfd935a4c1a4c 175482 cli-mono optional cli-common_0.9+nmu1_all.deb c17a1bf08cd1a0d8d43f5128d3d52577 43676 cli-mono optional cli-common-dev_0.9+nmu1_all.deb -BEGIN PGP SIGNATURE- Version: GnuPG v1 iQIcBAEBCAAGBQJU7jgMAAoJENu+nU2Z0qAExeAP/iUQFKwJV5LxPazDCVTnNJRn XSzbJER0x1Nz6L0Swe9JpjE0VgoE5ZeygMdIHEeN5oXzmPgnMbQL40O+kOfpXGBn r+zdj05kolrK18qT05ZEGWBJPKOoIgxQkjdISX+BH89OuarK+mlQ/JbxuqtVxbpm i5X5SM6wnu1AAiaP1oSKqS5m6RYOp2ZrE/oKtImkaNKaXKPYJ0TEtriNyUlfUpke TQZH3bLmK2HGpeLeWrSKwJgqQvsbSPlTJlPuDuHdI/i2y3MQAyn1ML5sQEhUE2Zk 36owJtvC+q/riZi8ouzRjF2XAdfaxYVPr5DQrnSq1fAloIy34yQWAPMBLgbCWf3Z g/JdlWOTegljMBQjbjNo0O07ZVn0GQCTd9UOzi04s/v8U5Z8TQWeNT1zk9jtlb05 0n/kLCgTRI/ewuafxsD+wLCehF4Qu50MZ7umN3Y0Glr7NjjmQYbx6eGkkMJ62rdw 81jbPcRfbXUsICtYj0+5IxCaERucrB/Toh+8bf834GfQU8rFNxK4mRGRv3QL+LqO
Bug#779613: no such file or directory trying to connect through the blueman-applet
Anyway, connecting to a NAP should work. You just have to select the service from the device menu and not use the generic connect item for that. There's no service from the menu, in fact, the Serial server menu item is gone. So you are talking about a serial service, not a NAP service. Support for serial services with BlueZ 5 is not available in the alpha1 snapshot, but recently made it into current upstream master. I'm actually planning to do an alpha2 snapshot release and package it for unstable or experimental at the end of the week. -- To UNSUBSCRIBE, email to debian-bugs-rc-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Processed: your mail
Processing commands for cont...@bugs.debian.org: severity 779663 important Bug #779663 [sound-juicer] sound-juicer: debian/copyright incomplete Severity set to 'important' from 'serious' thanks Stopping processing here. Please contact me if you need assistance. -- 779663: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=779663 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#764298: Still an issue
Am 04.03.2015 um 01:34 schrieb Michael Biebl: Am 04.03.2015 um 01:07 schrieb Daurnimator: Did you dist-upgrade the VM and those failures are from before the upgrade? Can you attach your /var/log/dpkg.log The reason why I'm asking is, that the fixed version 215-12 migrated to testing on 2015-02-28. The latest AMI according to [1] is from 20150213, so it can't have 215-12 yet. So this looks like the VM was upgraded and the error messages are from before the upgrade when systemd 215-12 was installed. [1] https://wiki.debian.org/Cloud/AmazonEC2Image/Jessie -- 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#779687: libdevel-callchecker-perl: FTBFS on i386: DynaLoader bombs out
(technically, I think this isn't RC as the package never built on i386.)
On Tue, Mar 03, 2015 at 10:32:50PM -0500, Aaron M. Ucko wrote:
Source: libdevel-callchecker-perl
Version: 0.006-1
Severity: serious
Justification: fails to build from source
The automated build of libdevel-callchecker-perl failed (only) on
i386 due to test suite errors (excerpted from
https://buildd.debian.org/status/fetch.php?pkg=libdevel-callchecker-perlarch=i386ver=0.006-1stamp=1425399391
):
cd . ./Build test --verbose 1
Can't use an undefined value as a subroutine reference at
/usr/lib/i386-linux-gnu/perl/5.20/DynaLoader.pm line 210.
This is a sign of ABI incompatibility between perl and the built XS
modules. The build is not using $Config{ccflags} for some reason,
so it's missing -D_FILE_OFFSET_BITS=64 which affects the binary interface.
No time to look further right now, but hope this helps.
--
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
Bug#764298: Still an issue
On 3 March 2015 at 18:35, Michael Biebl bi...@debian.org wrote: What's the output of systemctl status dbus.service dbus.socket? I do not have dbus installed. $ sudo systemctl status dbus.service ● dbus.service Loaded: not-found (Reason: No such file or directory) Active: inactive (dead) $ sudo systemctl status dbus.socket ● dbus.socket Loaded: not-found (Reason: No such file or directory) Active: inactive (dead) Mar 03 20:02:56 ip-10-80-175-145 systemd[1]: Cannot add dependency job for unit dbus.socket, ignoring: Unit dbus.socket failed to load: No such file or directory. Mar 03 20:02:56 ip-10-80-175-145 systemd[1]: Cannot add dependency job for unit dbus.socket, ignoring: Unit dbus.socket failed to load: No such file or directory. Mar 03 20:02:56 ip-10-80-175-145 systemd[1]: Cannot add dependency job for unit dbus.socket, ignoring: Unit dbus.socket failed to load: No such file or directory. Mar 03 20:02:56 ip-10-80-175-145 systemd[1]: Cannot add dependency job for unit dbus.socket, ignoring: Unit dbus.socket failed to load: No such file or directory. Mar 03 20:02:56 ip-10-80-175-145 systemd[1]: Cannot add dependency job for unit dbus.socket, ignoring: Unit dbus.socket failed to load: No such file or directory. Mar 03 21:08:09 ip-10-80-175-145 systemd[1]: Cannot add dependency job for unit dbus.socket, ignoring: Unit dbus.socket failed to load: No such file or directory. -- To UNSUBSCRIBE, email to debian-bugs-rc-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#764298: Still an issue
Am 2015-03-04 01:13, schrieb Michael Biebl: Am 04.03.2015 um 01:34 schrieb Michael Biebl: Am 04.03.2015 um 01:07 schrieb Daurnimator: Did you dist-upgrade the VM and those failures are from before the upgrade? Can you attach your /var/log/dpkg.log The reason why I'm asking is, that the fixed version 215-12 migrated to testing on 2015-02-28. The latest AMI according to [1] is from 20150213, so it can't have 215-12 yet. So this looks like the VM was upgraded and the error messages are from before the upgrade when systemd 215-12 was installed. [1] https://wiki.debian.org/Cloud/AmazonEC2Image/Jessie Just double checked: The latest AMI provided by Debian ships 215-11. So, if you have 215-12 installed, this means the VM was upgraded after the VM was instantiated and booted and the error messages you see are most likely from 215-11, which does not ship the fix yet. -- To UNSUBSCRIBE, email to debian-bugs-rc-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#764298: Still an issue
Am 04.03.2015 um 00:19 schrieb Daurnimator: I just installed a fresh systemd (via amazon AMI: https://wiki.debian.org/Cloud/AmazonEC2Image/Jessie) that includes systemd 215-12 I still got the log message: Mar 03 20:02:56 ip-10-80-175-145 systemd[1]: Starting Login Service... Mar 03 20:02:56 ip-10-80-175-145 systemd-logind[323]: Failed to connect to system bus: No such file or directory Mar 03 20:02:56 ip-10-80-175-145 systemd[1]: systemd-logind.service: main process exited, code=exited, status=1/FAILURE Mar 03 20:02:56 ip-10-80-175-145 systemd[1]: Failed to start Login Service. Mar 03 20:02:56 ip-10-80-175-145 systemd[1]: Unit systemd-logind.service entered failed state. Mar 03 20:02:56 ip-10-80-175-145 systemd[1]: systemd-logind.service has no holdoff time, scheduling restart. Mar 03 20:02:56 ip-10-80-175-145 systemd[1]: Stopping Login Service... (and then again a few times) What's the output of systemctl status dbus.service dbus.socket? -- 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#764298: Still an issue
Am 04.03.2015 um 00:37 schrieb Daurnimator: On 3 March 2015 at 18:35, Michael Biebl bi...@debian.org wrote: What's the output of systemctl status dbus.service dbus.socket? I do not have dbus installed. $ sudo systemctl status dbus.service ● dbus.service Loaded: not-found (Reason: No such file or directory) Active: inactive (dead) $ sudo systemctl status dbus.socket ● dbus.socket Loaded: not-found (Reason: No such file or directory) Active: inactive (dead) What's the output of systemctl cat systemd-logind.service systemctl status systemd-logind.service -- 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#764298: Still an issue
Am 04.03.2015 um 01:07 schrieb Daurnimator: On 3 March 2015 at 18:42, Michael Biebl bi...@debian.org wrote: What's the output of systemctl cat systemd-logind.service systemctl status systemd-logind.service $ sudo systemctl cat systemd-logind.service # /lib/systemd/system/systemd-logind.service # This file is part of systemd. # # systemd is free software; you can redistribute it and/or modify it # under the terms of the GNU Lesser General Public License as published by # the Free Software Foundation; either version 2.1 of the License, or # (at your option) any later version. [Unit] Description=Login Service Documentation=man:systemd-logind.service(8) man:logind.conf(5) Documentation=http://www.freedesktop.org/wiki/Software/systemd/logind Documentation=http://www.freedesktop.org/wiki/Software/systemd/multiseat Wants=user.slice After=nss-user-lookup.target user.slice ConditionPathExists=/lib/systemd/system/dbus.service That looks ok. # Ask for the dbus socket. If running over kdbus, the socket will # not be actually used. Wants=dbus.socket After=dbus.socket [Service] ExecStart=/lib/systemd/systemd-logind Restart=always RestartSec=0 BusName=org.freedesktop.login1 CapabilityBoundingSet=CAP_SYS_ADMIN CAP_AUDIT_CONTROL CAP_CHOWN CAP_KILL CAP_DAC_READ_SEARCH CAP_DAC_OVERRIDE CAP_FOWNER CAP_SYS_TTY_CONFIG WatchdogSec=1min # Increase the default a bit in order to allow many simultaneous # logins since we keep one fd open per session. LimitNOFILE=16384 $ sudo systemctl status systemd-logind.service ● systemd-logind.service - Login Service Loaded: loaded (/lib/systemd/system/systemd-logind.service; static) Active: failed (Result: start-limit) since Tue 2015-03-03 20:02:56 UTC; 4h 3min ago start condition failed at Tue 2015-03-03 21:08:09 UTC; 2h 57min ago Docs: man:systemd-logind.service(8) man:logind.conf(5) http://www.freedesktop.org/wiki/Software/systemd/logind http://www.freedesktop.org/wiki/Software/systemd/multiseat Main PID: 341 (code=exited, status=1/FAILURE) Status: Shutting down... Mar 03 20:02:56 ip-10-80-175-145 systemd[1]: systemd-logind.service has no holdoff time, scheduling restart. Mar 03 20:02:56 ip-10-80-175-145 systemd[1]: Stopping Login Service... Mar 03 20:02:56 ip-10-80-175-145 systemd[1]: Starting Login Service... Mar 03 20:02:56 ip-10-80-175-145 systemd[1]: systemd-logind.service start request repeated too quickly, refusing to start. Mar 03 20:02:56 ip-10-80-175-145 systemd[1]: Failed to start Login Service. Mar 03 20:02:56 ip-10-80-175-145 systemd[1]: Unit systemd-logind.service entered failed state. Mar 03 21:08:09 ip-10-80-175-145 systemd[1]: Started Login Service. Mar 03 23:11:46 ip-10-80-175-145 systemd[1]: Stopped systemd-logind.service. Did you dist-upgrade the VM and those failures are from before the upgrade? Can you attach your /var/log/dpkg.log Is the problem reproducible after a reboot? Fwiw, I can't reproduce the problem in a VM without dbus installed, so we need to find what's special in your case. -- 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#764298: Still an issue
I just installed a fresh systemd (via amazon AMI: https://wiki.debian.org/Cloud/AmazonEC2Image/Jessie) that includes systemd 215-12 I still got the log message: Mar 03 20:02:56 ip-10-80-175-145 systemd[1]: Starting Login Service... Mar 03 20:02:56 ip-10-80-175-145 systemd-logind[323]: Failed to connect to system bus: No such file or directory Mar 03 20:02:56 ip-10-80-175-145 systemd[1]: systemd-logind.service: main process exited, code=exited, status=1/FAILURE Mar 03 20:02:56 ip-10-80-175-145 systemd[1]: Failed to start Login Service. Mar 03 20:02:56 ip-10-80-175-145 systemd[1]: Unit systemd-logind.service entered failed state. Mar 03 20:02:56 ip-10-80-175-145 systemd[1]: systemd-logind.service has no holdoff time, scheduling restart. Mar 03 20:02:56 ip-10-80-175-145 systemd[1]: Stopping Login Service... (and then again a few times)
Bug#764298: Still an issue
On 3 March 2015 at 18:42, Michael Biebl bi...@debian.org wrote: What's the output of systemctl cat systemd-logind.service systemctl status systemd-logind.service $ sudo systemctl cat systemd-logind.service # /lib/systemd/system/systemd-logind.service # This file is part of systemd. # # systemd is free software; you can redistribute it and/or modify it # under the terms of the GNU Lesser General Public License as published by # the Free Software Foundation; either version 2.1 of the License, or # (at your option) any later version. [Unit] Description=Login Service Documentation=man:systemd-logind.service(8) man:logind.conf(5) Documentation=http://www.freedesktop.org/wiki/Software/systemd/logind Documentation=http://www.freedesktop.org/wiki/Software/systemd/multiseat Wants=user.slice After=nss-user-lookup.target user.slice ConditionPathExists=/lib/systemd/system/dbus.service # Ask for the dbus socket. If running over kdbus, the socket will # not be actually used. Wants=dbus.socket After=dbus.socket [Service] ExecStart=/lib/systemd/systemd-logind Restart=always RestartSec=0 BusName=org.freedesktop.login1 CapabilityBoundingSet=CAP_SYS_ADMIN CAP_AUDIT_CONTROL CAP_CHOWN CAP_KILL CAP_DAC_READ_SEARCH CAP_DAC_OVERRIDE CAP_FOWNER CAP_SYS_TTY_CONFIG WatchdogSec=1min # Increase the default a bit in order to allow many simultaneous # logins since we keep one fd open per session. LimitNOFILE=16384 $ sudo systemctl status systemd-logind.service ● systemd-logind.service - Login Service Loaded: loaded (/lib/systemd/system/systemd-logind.service; static) Active: failed (Result: start-limit) since Tue 2015-03-03 20:02:56 UTC; 4h 3min ago start condition failed at Tue 2015-03-03 21:08:09 UTC; 2h 57min ago Docs: man:systemd-logind.service(8) man:logind.conf(5) http://www.freedesktop.org/wiki/Software/systemd/logind http://www.freedesktop.org/wiki/Software/systemd/multiseat Main PID: 341 (code=exited, status=1/FAILURE) Status: Shutting down... Mar 03 20:02:56 ip-10-80-175-145 systemd[1]: systemd-logind.service has no holdoff time, scheduling restart. Mar 03 20:02:56 ip-10-80-175-145 systemd[1]: Stopping Login Service... Mar 03 20:02:56 ip-10-80-175-145 systemd[1]: Starting Login Service... Mar 03 20:02:56 ip-10-80-175-145 systemd[1]: systemd-logind.service start request repeated too quickly, refusing to start. Mar 03 20:02:56 ip-10-80-175-145 systemd[1]: Failed to start Login Service. Mar 03 20:02:56 ip-10-80-175-145 systemd[1]: Unit systemd-logind.service entered failed state. Mar 03 21:08:09 ip-10-80-175-145 systemd[1]: Started Login Service. Mar 03 23:11:46 ip-10-80-175-145 systemd[1]: Stopped systemd-logind.service. -- To UNSUBSCRIBE, email to debian-bugs-rc-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#779687: libdevel-callchecker-perl: FTBFS on i386: DynaLoader bombs out
Source: libdevel-callchecker-perl
Version: 0.006-1
Severity: serious
Justification: fails to build from source
The automated build of libdevel-callchecker-perl failed (only) on
i386 due to test suite errors (excerpted from
https://buildd.debian.org/status/fetch.php?pkg=libdevel-callchecker-perlarch=i386ver=0.006-1stamp=1425399391
):
cd . ./Build test --verbose 1
Can't use an undefined value as a subroutine reference at
/usr/lib/i386-linux-gnu/perl/5.20/DynaLoader.pm line 210.
END failed--call queue aborted at lib/Devel/CallChecker.pm line 210.
Compilation failed in require at t/WriteHeader.pm line 14.
# Looks like your test exited with 2 before it could output anything.
t/callck.t .
1..79
Dubious, test returned 2 (wstat 512, 0x200)
Failed 79/79 subtests
The portion of DynaLoader.pm leading up to line 210 (from
DynaLoader::bootstrap) reads
boot:
my $xs = dl_install_xsub(${module}::bootstrap, $boot_symbol_ref, $file);
# See comment block above
push(@dl_shared_objects, $file); # record files loaded
$xs(@args);
I'm not sure if it's relevant, but the i386 build of perl has the
unusual property that the perl binary links statically rather than
dynamically to libperl for performance reasons.
At any rate, could you please take a look?
Thanks!
--
To UNSUBSCRIBE, email to debian-bugs-rc-requ...@lists.debian.org
with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#779688: libjson-rpc-cpp: FTBFS: gen/abstractsubserver.h: No such file or directory
Source: libjson-rpc-cpp Version: 0.4.2-3 Severity: serious Justification: fails to build from source Builds of libjson-rpc-cpp failed for several architectures with the error /«PKGBUILDDIR»/src/test/test_integration.cpp:17:35: fatal error: gen/abstractsubserver.h: No such file or directory It looks like this error may stem from an undeclared dependency that's only a problem in parallel builds; if so, you might consider simply dropping --parallel from your dh invocations for now. Could you please take a look? Thanks! -- To UNSUBSCRIBE, email to debian-bugs-rc-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#779689: libjson-rpc-cpp: FTBFS: test suite errors
Source: libjson-rpc-cpp Version: 0.4.2-3 Severity: serious Justification: fails to build from source Builds of libjson-rpc-cpp failed on several platforms with test suite errors. On armel, The following tests FAILED: 4 - connector_http (Failed) 6 - integration (Failed) 7 - all (Failed) and each of those tests also failed on some other platforms, though never the whole set elsewhere. Could you please take a look? Thanks! -- To UNSUBSCRIBE, email to debian-bugs-rc-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#730903: mutrace ftbfs
On Fri, 4 Apr 2014 14:59:53 +0300 Riku Voipio riku.voi...@iki.fi wrote: Hi, The libiberty.h is provided by libiberty-dev and installed in /usr/include/libiberty/libiberty.h. unfortunately this change isn't enough. Due to some other changes, linking against static libbfd doesn't work: gcc -std=gnu99 -shared -fPIC .libs/libmutrace_backtrace_symbols_la-backtrace-symbols.o /usr/lib/libbfd.a -lrt -ldl -pthread -O2 -pthread -Wl,-soname -Wl,libmutrace-backtrace-symbols.so -o .libs/libmutrace-backtrace-symbols.so /usr/bin/ld: /usr/lib/libbfd.a(bfd.o): relocation R_X86_64_32 against `.rodata.str1.1' can not be used when making a shared object; recompile with -fPIC /usr/lib/libbfd.a: error adding symbols: Bad value I didn't meet this problem. collect2: error: ld returned 1 exit status while dynamic linking against libbfd is not considered allowed. It works for me to add -I/usr/include/libiberty/ to libmutrace_backtrace_symbols_la_CFLAGS in Makefile.am. It works well on both amd64 and mips64el. This leaves the code stuck in no-building area. Considering dropping the package. Riku -- To UNSUBSCRIBE, email to debian-bugs-rc-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#779550: marked as done (qt4-x11: CVE-2015-0295)
Your message dated Tue, 03 Mar 2015 09:25:07 + with message-id e1ysj4d-0006ut...@franck.debian.org and subject line Bug#779550: fixed in qt4-x11 4:4.8.6+git64-g5dc8b2b+dfsg-3 has caused the Debian Bug report #779550, regarding qt4-x11: CVE-2015-0295 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.) -- 779550: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=779550 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems ---BeginMessage--- Package: qt4-x11 Severity: important Tags: security Justification: user security hole Hi, please see http://lists.qt-project.org/pipermail/announce/2015-February/59.html for details and a patch. Cheers, Moritz ---End Message--- ---BeginMessage--- Source: qt4-x11 Source-Version: 4:4.8.6+git64-g5dc8b2b+dfsg-3 We believe that the bug you reported is fixed in the latest version of qt4-x11, 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 779...@bugs.debian.org, and the maintainer will reopen the bug report if appropriate. Debian distribution maintenance software pp. Dmitry Shachnev mity...@debian.org (supplier of updated qt4-x11 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, 02 Mar 2015 17:12:28 +0300 Source: qt4-x11 Binary: libqtcore4 qtcore4-l10n libqt4-core libqtgui4 libqt4-gui libqt4-network libqt4-opengl libqt4-script libqt4-scripttools libqt4-sql libqt4-sql-ibase libqt4-sql-mysql libqt4-sql-odbc libqt4-sql-psql libqt4-sql-sqlite libqt4-sql-sqlite2 libqt4-sql-tds libqt4-svg libqt4-webkit libqt4-xml libqt4-xmlpatterns libqt4-dbus libqtdbus4 libqt4-qt3support libqt4-designer libqt4-help libqt4-assistant libqt4-test libqt4-phonon libqt4-declarative libqt4-declarative-folderlistmodel libqt4-declarative-gestures libqt4-declarative-particles libqt4-declarative-shaders libqt4-dev libqt4-dev-bin libqt4-private-dev libqt4-opengl-dev libqt4-dbg libqt4-designer-dbg libqt4-qt3support-dbg libqt4-script-dbg libqt4-webkit-dbg libqt4-xmlpatterns-dbg qt4-bin-dbg qt4-demos-dbg qt4-designer qt4-dev-tools qt4-qmake qt4-qtconfig qt4-demos qt4-qmlviewer qt4-linguist-tools qdbus qt4-doc qt4-doc-html qt4-default Architecture: source all Version: 4:4.8.6+git64-g5dc8b2b+dfsg-3 Distribution: unstable Urgency: medium Maintainer: Debian Qt/KDE Maintainers debian-qt-...@lists.debian.org Changed-By: Dmitry Shachnev mity...@debian.org Description: libqt4-assistant - transitional package for Qt 4 assistant module libqt4-core - transitional package for Qt 4 core non-GUI runtime libraries libqt4-dbg - Qt 4 library debugging symbols libqt4-dbus - Qt 4 D-Bus module libqt4-declarative - Qt 4 Declarative module libqt4-declarative-folderlistmodel - Qt 4 folderlistmodel QML plugin libqt4-declarative-gestures - Qt 4 gestures QML plugin libqt4-declarative-particles - Qt 4 particles QML plugin libqt4-declarative-shaders - Qt 4 shaders QML plugin libqt4-designer - Qt 4 designer module libqt4-designer-dbg - Qt 4 designer library debugging symbols libqt4-dev - Qt 4 development files libqt4-dev-bin - Qt 4 development programs libqt4-gui - transitional package for Qt 4 GUI runtime libraries libqt4-help - Qt 4 help module libqt4-network - Qt 4 network module libqt4-opengl - Qt 4 OpenGL module libqt4-opengl-dev - Qt 4 OpenGL library development files libqt4-phonon - Qt 4 Phonon module libqt4-private-dev - Qt 4 private development files libqt4-qt3support - Qt 3 compatibility library for Qt 4 libqt4-qt3support-dbg - Qt 3 compatibility library for Qt 4 debugging symbols libqt4-script - Qt 4 script module libqt4-script-dbg - Qt 4 script library debugging symbols libqt4-scripttools - Qt 4 script tools module libqt4-sql - Qt 4 SQL module libqt4-sql-ibase - Qt 4 InterBase/FireBird database driver libqt4-sql-mysql - Qt 4 MySQL database driver libqt4-sql-odbc - Qt 4 ODBC database driver libqt4-sql-psql - Qt 4 PostgreSQL database driver libqt4-sql-sqlite - Qt 4 SQLite 3 database driver libqt4-sql-sqlite2 - Qt 4 SQLite 2 database driver libqt4-sql-tds - Qt 4 FreeTDS database driver libqt4-svg - Qt 4 SVG module libqt4-test - Qt 4 test module libqt4-webkit - transitional package for Qt 4 WebKit module libqt4-webkit-dbg - transitional package for Qt 4
Bug#779579: installer broken: multipath-udeb depends on non-existent libgcc1 udeb
Cyril, thanks for the /very clear/ pointers to the problem/solution. :) Ritesh, On 03/03/2015 04:26 AM, Ritesh Raj Sarraf wrote: Will you be in a position to try out the changes that Cyril has proposed ? Sure, I can try and should send a patch soon. -- Mauricio Faria de Oliveira IBM Linux Technology Center -- To UNSUBSCRIBE, email to debian-bugs-rc-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#779634: pymad: FTBFS - No 'Setup' file. Perhaps you need to run the configure script.
Source: pymad
Version: 0.8-1
Severity: serious
Justification: fails to build from source (but built successfully in the past)
Hi,
pymad 0.8-1 fails to build on every architecture with the error:
I: pybuild base:170: python2.7 setup.py clean
No 'Setup' file. Perhaps you need to run the configure script.
E: pybuild pybuild:256: clean: plugin distutils failed with: exit code=1:
python2.7 setup.py clean
dh_auto_clean: pybuild --clean -i python{version} -p 2.7 --dir . returned
exit code 13
make: *** [clean] Error 13
debian/rules:10: recipe for target 'clean' failed
dpkg-buildpackage: error: fakeroot debian/rules clean gave error exit status 2
Full logs:
https://buildd.debian.org/status/package.php?p=pymad
Thanks,
James
--
To UNSUBSCRIBE, email to debian-bugs-rc-requ...@lists.debian.org
with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Processed: severity of 774090 is important
Processing commands for cont...@bugs.debian.org: # see jmm's mail severity 774090 important Bug #774090 [emacs24] emacs24: CVE-2014-9483: a left-click in Emacs sometimes modifies the PRIMARY selection Severity set to 'important' from 'grave' thanks Stopping processing here. Please contact me if you need assistance. -- 774090: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=774090 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#766462: with plymouth installed, I don't get any gettys on my VCs
On mar., 2015-03-03 at 09:59 +, Simon McVittie wrote: * have systemd as init * install plymouth, gdm3 and your favourite non-GDM DM implementation (kdm in the original bug report) Ok, I'm missing gdm3 here, so I'll try to install it and report back on the situation. * select the non-GDM DM implementation as the active DM * enable plymouth by putting splash on the kernel command-line Regards, -- Yves-Alexis signature.asc Description: This is a digitally signed message part
Processed: same player try again
Processing commands for cont...@bugs.debian.org:
reassign 777580 llvm-toolchain-snapshot
Bug #777580 {Done: Sylvestre Ledru sylves...@debian.org} [python-clang-3.5]
python-clang-3.7 and python-clang-3.5: error when trying to install together
Bug reassigned from package 'python-clang-3.5' to 'llvm-toolchain-snapshot'.
Ignoring request to alter found versions of bug #777580 to the same values
previously set
No longer marked as fixed in versions 3.5-9.
found 777580 llvm-toolchain-snapshot/1:3.7~svn227076-1
Bug #777580 {Done: Sylvestre Ledru sylves...@debian.org}
[llvm-toolchain-snapshot] python-clang-3.7 and python-clang-3.5: error when
trying to install together
Marked as found in versions llvm-toolchain-snapshot/1:3.7~svn227076-1 and
reopened.
notfixed 777580 python-clang-3.5/3.5-9
Bug #777580 [llvm-toolchain-snapshot] python-clang-3.7 and python-clang-3.5:
error when trying to install together
The source python-clang-3.5 and version 3.5-9 do not appear to match any binary
packages
Ignoring request to alter fixed versions of bug #777580 to the same values
previously set
fixed 777580 llvm-toolchain-snapshot/1:3.7~svn230892-1
Bug #777580 [llvm-toolchain-snapshot] python-clang-3.7 and python-clang-3.5:
error when trying to install together
Marked as fixed in versions llvm-toolchain-snapshot/1:3.7~svn230892-1.
thanks
Stopping processing here.
Please contact me if you need assistance.
--
777580: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=777580
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: your mail
Processing commands for cont...@bugs.debian.org: close 777580 Bug #777580 [llvm-toolchain-snapshot] python-clang-3.7 and python-clang-3.5: error when trying to install together Marked Bug as done End of message, stopping processing here. Please contact me if you need assistance. -- 777580: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=777580 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#762700: systemd: journald fails to forward most boot messages to syslog
Am 02.03.2015 um 15:42 schrieb Christian Seiler: - SOLUTION (mostly the same as before, but SendBuffer is set on a different unit and a Condition is added to the service): 1. Increase max_dgram_qlen to a reasonable value. The easiest way is via a systemd service: /lib/systemd/system/systemd-setup-dgram-qlen.service: [Unit] DefaultDependencies=no Before=syslog.socket ConditionPathIsReadWrite=/proc/sys/net/unix/max_dgram_qlen [Service] Type=oneshot ExecStart=/sbin/sysctl -w net.unix.max_dgram_qlen=512 StandardOutput=null A proper Description= is missing and it probably should have RemainAfterExit=yes. That said, why not simply use a sysctl.d conf snippet? Add the following to /lib/systemd/systemd/syslog.socket: Wants=systemd-setup-dgram-qlen.service 2. Make it even more robust by applying the patch from upstream to increase the send buffer on the socket journald uses to forward syslog messages, i.e. add SendBuffer=8M to /lib/systemd/system/systemd-journald-dev-log.socket (NOT syslog.socket!) (As said before, the values 512 and 8M are debatable, although 8M is typically used within systemd's source code, so it's probably a good value to use. 512 seems like a reasonable compromise to me: typically, up to ~ 100 boot messages will be generated before syslog is started on systems I've tried this on, so using something that's 5x higher seems like a good safety net without increasing this to crazy high numbers. Note that the 8M limit will apply independently.) I've been using this on a Jessie system for the past couple of days (well, drop-ins in /etc, actually), and I didn't notice any side-effects so far. Did you run it with 1. and 2. applied, or only 1.? -- 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
