On 07/02/2014 06:32 PM, Michael Biebl wrote:
Am 02.07.2014 17:23, schrieb
VALETTE Eric OLNC/OLPS:
On 07/02/2014 05:01 PM, Michael Biebl wrote:
Never saw a warning and never failed to install anything!
I checked the
test is there in 208 too
Package: systemd
Version: 204-8~bpo70+1
Severity: normal
My desktop has been up for 31 days. Today I noticed I could no longer connect
to the system dbus daemon. I'll leave the system
Am 03.07.2014 11:16, schrieb Sam Morris:
Package: systemd
Version: 204-8~bpo70+1
Severity: normal
My desktop has been up for 31 days. Today I noticed I could no longer connect
Am 03.07.2014 09:09, schrieb VALETTE Eric OLNC/OLPS:
Sorry this was not clear, I have just checked the scripts works and I did on
kernel that had the CONFIG_FHANDLE already. So I do not understand why I
never
saw a warning.
Most likely the version you installed did not have this check.
It
Am 03.07.2014 12:33, schrieb Michael Biebl:
Am 03.07.2014 09:09, schrieb VALETTE Eric OLNC/OLPS:
Sorry this was not clear, I have just checked the scripts works and I did on
kernel that had the CONFIG_FHANDLE already. So I do not understand why I
never
saw a warning.
Most likely the
Package: systemd
Version: 208-5
Severity: normal
While updating, systemd was updated before glibc.
Needless to say, this does not work at all.
# aptitude(wd: ~)
Reading changelogs...
apt-listchanges: Mailing smurf-chan...@smurf.noris.de: apt-listchanges: news
for eltern
Extracting
On Thu, Jul 03, 2014 at 12:30:14PM +0200, Michael Biebl wrote:
If dbus is running (and it apparently is), then it should be the process
listening on /var/run/dbus/system_bus_socket.
I'm not sure about that... on another system where dbus is currently
working fine:
# netstat -A unix -lnp | grep
Am 03.07.2014 12:55, schrieb Matthias Urlichs:
Package: systemd
Version: 208-5
Severity: normal
While updating, systemd was updated before glibc.
Needless to say, this does not work at all.
# aptitude(wd: ~)
Reading changelogs...
apt-listchanges: Mailing
Am 03.07.2014 13:03, schrieb Sam Morris:
On Thu, Jul 03, 2014 at 12:30:14PM +0200, Michael Biebl wrote:
If dbus is running (and it apparently is), then it should be the process
listening on /var/run/dbus/system_bus_socket.
I'm not sure about that... on another system where dbus is currently
On 2014-07-03 13:22 +0200, Michael Biebl wrote:
Am 03.07.2014 12:55, schrieb Matthias Urlichs:
Package: systemd
Version: 208-5
Severity: normal
While updating, systemd was updated before glibc.
Needless to say, this does not work at all.
# aptitude(wd: ~)
Reading
* Michael Biebl bi...@debian.org, 2014-07-03, 13:22:
Unpacking replacement systemd-sysv ...
Preparing to replace libtirpc1:i386 0.2.2-5 (using
.../libtirpc1_0.2.3-1_i386.deb) ...
Unpacking replacement libtirpc1:i386 ...
Preparing to replace libgcrypt11:i386 1.5.0-5+deb7u1 (using
Am 03.07.2014 13:56, schrieb Jakub Wilk:
systemd-sysv was unpacked, but not configured yet. At this point, its
dependencies were not required to be satisfied. So from POV of the
package manager everything is in order here.
Perhaps a Pre-Depends is missing somewhere; but it's hard to tell
Am 03.07.2014 14:26, schrieb Ansgar Burchardt:
Most essential packages should have this problem. I checked bash and it
indeed has
Pre-Depends: dash (= 0.5.5.1-2.2), libc6 (= 2.15), libtinfo5
which comes from
Pre-Depends: dash (= 0.5.5.1-2.2), ${shlibs:Pre-Depends}, ${misc:Depends}
Processing commands for cont...@bugs.debian.org:
severity 753589 serious
Bug #753589 [systemd] systemd: Missing dependency on glibc?
Severity set to 'serious' from 'normal'
thanks
Stopping processing here.
Please contact me if you need assistance.
--
753589:
Processing commands for cont...@bugs.debian.org:
notfound 753606 204-8
Bug #753606 [libsystemd-journal-dev] libsystemd-journal-dev: unable to install
libsystemd-journal-dev=204-8~bpo70+1
Ignoring request to alter found versions of bug #753606 to the same values
previously set
thanks
Stopping
Processing commands for cont...@bugs.debian.org:
severity 753606 important
Bug #753606 [libsystemd-journal-dev] libsystemd-journal-dev: unable to install
libsystemd-journal-dev=204-8~bpo70+1
Severity set to 'important' from 'grave'
thanks
Stopping processing here.
Please contact me if you
Am 03.07.2014 16:17, schrieb Michael Biebl:
Attached is a proposed patch.
feedback on the patch would be appreciated.
--
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
#
# bts-link upstream status pull for source package systemd
# see http://lists.debian.org/debian-devel-announce/2006/05/msg1.html
#
user bts-link-upstr...@lists.alioth.debian.org
# remote status report for #665398 (http://bugs.debian.org/665398)
# Bug title: systemd: should configure the
Package: systemd
Version: 204-14
Followup-For: Bug #748056
Hello,
since this is a 'feature' I expect this is still present.
I encountered this problem when one of my drive cables went loose and
the drive became inaccessible.
The drive was ad-hoc connected while placed physically outside of the
19 matches
Mail list logo
