Alright, I figured it out. s3ql is actually missing a build-dependency
on python3-llfuse-dbg. It is probably pulled in indirectly in some
circumstances.
Thanks for the report!
--
To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org
with a subject of unsubscribe. Trouble? Contact
On Jun 30 2015, Martin Michlmayr t...@hp.com wrote:
* Nikolaus Rath nikol...@rath.org [2015-06-29 21:02]:
# python3-dbg
Python 3.4.3+ (default, Jun 2 2015, 14:09:35)
[GCC 4.9.2] on linux
Type help, copyright, credits or license for more information.
import llfuse
import llfuse.capi
sbuild (Debian sbuild) 0.65.2 (24 Mar 2015) on bl460gen8-30.hlinux.usa.hp.com
...
python3 setup.py build_cython
running build_cython
/usr/lib/python3/dist-packages/Cython/Compiler/Main.py:514: UserWarning: got
unknown compilation options, please remove: recursive, warning_errors
Package: sbuild
Version: 0.65.2-1
Severity: normal
I realize this is most likely a user error, but I could not find any
other forum to ask for help (is there an sbulid mailinglist somewhere?)
so I'm submitting this as a bug.
I'm trying to build a debian package, but when running it just hangs:
I've the same problem, but setting nnimap-shell-program (or
imap-shell-program, which is used to initialize the former) does not
make any difference.
--
GPG encrypted emails preferred. Key id: 0xD113FCAC3C4E599F
Fingerprint: ED31 791B 2C5C 1613 AF38 8B8A D113 FCAC 3C4E 599F
»Time
Package: mercurial-git
Version: 0.6.1-2
Severity: normal
Using the jessie package, I don't seem to be able to interact with git
repositories. Example:
$ hg clone git+http://git.gnus.org/cgit/gnus.git/
destination directory: gnus.git
** Unknown exception encountered with possibly-broken
Hello,
Re-reading the bug log I think I haven't made clear this this is a
recurring issue. Every few weeks my journal gets corrupted, and I have
to remove the affected files. This happens even in the absence of any
system crashes.
Best,
-Nikolaus
--
GPG encrypted emails preferred. Key id:
Hi,
dconf-cli was not installed. After installing it, it fails with
$ shotwell
**
ERROR:src/db/DatabaseTable.c:1269:database_table_add_column: assertion failed:
(res == Sqlite.OK)
Aborted
Best,
-Nikolaus
--
GPG encrypted emails preferred. Key id: 0xD113FCAC3C4E599F
Fingerprint: ED31 791B
On Apr 29 2015, Jörg Frings-Fürst deb...@jff-webhosting.net wrote:
dconf-cli was not installed. After installing it, it fails with
$ shotwell
**
ERROR:src/db/DatabaseTable.c:1269:database_table_add_column: assertion
failed: (res == Sqlite.OK)
Aborted
Is your shotwell a fresh install or
Package: shotwell
Version: 0.20.1-1+b1
Severity: normal
Hello,
Trying to start shotwell gives me this:
$ shotwell
/usr/lib/shotwell-settings-migrator: 24: /usr/lib/shotwell-settings-migrator:
dconf: not found
/usr/lib/shotwell-settings-migrator: 27: /usr/lib/shotwell-settings-migrator:
for
/home/user/onething and /home/user/otherthing.
Best,
-Nikolaus
--
Nikolaus Rath, Ph.D.
Senior Scientist
Tri Alpha Energy, Inc.
+1 949 830 2117 ext 211
--
To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org
with a subject of unsubscribe. Trouble? Contact listmas
Package: python-llfuse
Version: 0.40-2+b2
Severity: normal
The description of the python3-llfuse-dbg and python-llfuse-dbg packages
claims that they contain debugging symbols as well as the extensions
built for the debugging interpreter. However, it seems they only contain
the latter. The .so's
On Apr 01 2015, Andreas Beckmann a...@debian.org wrote:
Preparing to unpack .../python3-llfuse-dbg_0.40+dfsg-1_amd64.deb ...
Unpacking python3-llfuse-dbg (0.40+dfsg-1) over (0.40-2+b2) ...
dpkg: error processing archive
/var/cache/apt/archives/python3-llfuse-dbg_0.40+dfsg-1_amd64.deb
Also, I see the exact same issue on my laptop, so it's not just happening on
jenkins.debian.net - though granted, they both run stable and have been
set up by me :-)
Wild guess: could it be related to the kernel version? After all, it
seems to be related to loopback networking...
Best,
On Mar 02 2015, Jérémy Bobbio lunar-8fiuurrzop0dnm+yrof...@public.gmane.org
wrote:
Paul Wise:
The output when directly comparing two tarballs contains the temporary
paths used. This leaks the debbindiff user's TMP variable into the
report and is also ugly. I suggest changing to just showing
Package: debian-maintainers
Severity: normal
Dear Maintainer,
Please add Nikolaus Rath nikol...@rath.org to the keyring.
The jetring changeset is attached.
Best,
-Nikolaus
Comment: Add Nikolaus Rath nikol...@rath.org as a Debian Maintainer
Date: Fri, 27 Feb 2015 13:47:18 -0800
Action: import
On Feb 17 2015, Nikolaus Rath nikol...@rath.org wrote:
On Feb 17 2015, Piotr Ożarowski pi...@debian.org wrote:
[Ben Finney, 2015-02-17]
The question remains, though: where should that fact (and many others
like it) be documented so newcomers don't have to keep asking?
I guess dependencies
Package: dh-python
Version: 1.2014-2
Severity: wishlist
The dh_python3 manpage and the README.PyDist file currently do
not make it clear that .pydist files are for use by *other*
packages when they want to depend on the package that ships
the .pydist file.
A possible patch is attached.
diff
So please tighten the dependencies of s3ql 2.13 to require
python3-dugong = 3.4
At least according to https://packages.debian.org/source/unstable/s3ql,
this is exactly what the dependency is.
Where did you get the package from?
Best,
-Nikolaus
--
GPG encrypted emails preferred. Key id:
On Feb 16 2015, Mika Pflüger deb...@mikapflueger.de wrote:
Hi Nikolaus,
Am Mon, 16 Feb 2015 09:42:57 -0800
schrieb Nikolaus Rath nikol...@rath.org:
So please tighten the dependencies of s3ql 2.13 to require
python3-dugong = 3.4
At least according to
https://packages.debian.org/source
On Feb 16 2015, Mika Pflüger deb...@mikapflueger.de wrote:
Hi Nikolaus,
Am Mon, 16 Feb 2015 09:42:57 -0800
schrieb Nikolaus Rath nikol...@rath.org:
So please tighten the dependencies of s3ql 2.13 to require
python3-dugong = 3.4
At least according to
https://packages.debian.org/source
This is tracked upstream at
https://bitbucket.org/nikratio/s3ql/issue/110/improve-handling-of-name-resolution
--
To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org
with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Package: postfix
Version: 2.11.3-1
Severity: normal
Hello,
I installed postfix with apt-get, selected No configuration. Then
I created a custom main.cf file and tried to start the service. However:
# systemctl start postfix
Failed to start postfix.service: Unit postfix.service failed to load:
Package: postfix
Version: 2.11.3-1
Severity: normal
If I understand correctly, setting
smtp_host_lookup dns,native
should allow postfix to resolve hostnames from /etc/hosts if they are
not resolvable via DNS. However, this does not seem to work in practice:
[0] root@thinkpad:/etc/postfix#
Package: evince-gtk
Version: 3.14.1-1
Severity: normal
File: /usr/bin/evince
evince seems to be unable to print some PDFs. A print job is sent to the
printer, but the printer then prints only blank pages. I have attached
an example of such a PDF. The same PDF prints fine from acroread, and is
[ Resending to bug address rather than just ctte list ]
Don Armstrong d...@debian.org writes:
On Wed, 10 Dec 2014, Nikolaus Rath wrote:
Don Armstrong d...@debian.org writes:
4. The CTTE appreciates the effort of Debian contributors to mitigate
any issues with the transition
Don Armstrong d...@debian.org writes:
4. The CTTE appreciates the effort of Debian contributors to mitigate
any issues with the transition by:
a) Providing a fallback boot entry for sysvinit when systemd is the
default init in grub (#757298)
b) Developing a mechanism to warn on
As a workaround, could you use the attached program instead of mount.s3ql?
It should work just like mount.s3ql, but it will retry on any kind of
DNS error.
I'm still planning to fix this properly (probably by not retrying on the
first resolution attempt), but that is going to take a while.
Control: tags -1 -moreinfo
The package is now in unstable.
Best,
-Nikolaus
--
GPG encrypted emails preferred. Key id: 0xD113FCAC3C4E599F
Fingerprint: ED31 791B 2C5C 1613 AF38 8B8A D113 FCAC 3C4E 599F
»Time flies like an arrow, fruit flies like a Banana.«
--
To UNSUBSCRIBE,
Shannon Dealy de...@deatech.com writes:
On Thu, 4 Dec 2014, Nikolaus Rath wrote:
Shannon Dealy de...@deatech.com writes:
[snip]
Unfortunately Linux does not provide an easy way to distinguish between
an unavailable DNS server, and an un-resolvable host name. To
distinguish these cases, S3QL
Shannon Dealy de...@deatech.com writes:
The relevant code in S3QL 2.2 was last touched in version 2.2, so I
don't think that's it. However, relevant code in Dugong was last
modified in version 3.2. Prior to 3.2, *any* DNS problem was considered
temporary. In 3.2 and later, DNS problems are
Shannon Dealy de...@deatech.com writes:
At least at the time that you issued the kill command, mount.s3ql was
busy doing the SSL handshake with the remote server, so while it looked
like it was hanging, it was probably waiting for the remote server.
It had been waiting a very long time,
On 12/04/2014 10:07 AM, Shannon Dealy wrote:
Attached is the log file for a failed unmount.
While my previous attempts were simple umount.s3ql commands, this time a
couple of additional commands were run after rsync completed and before
the umount:
s3qlctrl flushcache
retitle 772052 mount.s3ql crashes on unmount if there are stale cache files
thanks
On 12/04/2014 11:41 AM, Shannon Dealy wrote:
On Thu, 4 Dec 2014, Nikolaus Rath wrote:
On 12/04/2014 10:07 AM, Shannon Dealy wrote:
Attached is the log file for a failed unmount.
While my previous attempts
On 12/03/2014 11:44 PM, Shannon Dealy wrote:
the file system still hangs (or the next time it hangs), could you
follow the instructions at
https://bitbucket.org/nikratio/s3ql/wiki/Providing%20Debugging%20Info to
obtain a Python stacktrace, and attach it to this issue?
This time the file
Shannon Dealy de...@deatech.com writes:
I installed python-dugong from experimental and proceeded to transfer
a lot of data to my S3 file system. Stopped it a couple of times,
unmounted once (successfully), remounted and continued transferring
data. After around 13-15 GB total had been
` function now knows about more kinds of
temporary errors, in particular also about those that do not have a
corresponding Python exception (e.g. no route to host).
Closes: #771756.
-- Nikolaus Rath nikol...@rath.org Wed, 03 Dec 2014 09:11:52 -0800
Debdiff against testing is attached
severity 771969 important
thanks
Thanks for the report! I'll set the severity to important for now,
because the package still works nicely for many other users. Not sure
why it's making so much trouble for you.. but I notice that (like the
last bug you found) this seems related to the handling of
Hi,
Is it possible that your DNS server behaves as described in
https://bitbucket.org/nikratio/python-dugong/issue/16/?
If so, could you test if upgrading to python3-dugong 3.4 from
experimental fixes the problem?
(In that case there still remains the issue of mount.s3ql hanging
instead of
On 12/01/2014 07:31 AM, Nikolaus Rath wrote:
Attached is the object_list.txt file from running fsck using your
patch.
Seems a little peculiar that the exception occurs at the 10
object
mark, though it may simply be chance and mean nothing:
..processed 10 objects so far
On 12/02/2014 02:20 PM, Shannon Dealy wrote:
On Tue, 2 Dec 2014, Shannon Dealy wrote:
[snip]
I performed a capture as requested, ...
Sorry Nikolaus,
I have deleted that file from where I posted it.
I made a mistake, that file was captured with ssl enabled. In fact, it
appears based
On 12/02/2014 03:35 PM, Nikolaus Rath wrote:
Not to fsck.s3ql, but the attached patch should enable traffic dumping
on the lower-level dugong library. It creates files raw_stream_xx.dat
in the current directory. Could you give that a shot and attach both the
results for an ssl and no-ssl run
Hi,
Could you try if the attached patch fixes the problem? (You could do
that at the same time as the fsck.s3ql --debug run).
Best,
-Nikolaus
--
GPG encrypted emails preferred. Key id: 0xD113FCAC3C4E599F
Fingerprint: ED31 791B 2C5C 1613 AF38 8B8A D113 FCAC 3C4E 599F
»Time flies
Now (most likely) fixed in
https://bitbucket.org/nikratio/s3ql/commits/8e563c492228a4d0669277d1b45a89955b68
Best,
-Nikolaus
--
GPG encrypted emails preferred. Key id: 0xD113FCAC3C4E599F
Fingerprint: ED31 791B 2C5C 1613 AF38 8B8A D113 FCAC 3C4E 599F
»Time flies like an arrow,
severity 771452 important
thanks
On 12/02/2014 01:50 PM, Shannon Dealy wrote:
On Mon, 1 Dec 2014, Nikolaus Rath wrote:
severity -1 normal
retitle -1 fsck.s3ql sporadically crashes when checking objects
thanks
Retitling this bug and lowering severity for now. I don't think
or incorrectly considering storage
objects as missing when the connection to remote server is
interrupted. Closes: #771452.
-- Nikolaus Rath nikol...@rath.org Tue, 02 Dec 2014 21:44:27 -0800
Debdiff is attached.
unblock s3ql/2.11.1+dfsg-2
diff -Nru s3ql-2.11.1+dfsg/debian/changelog
On 12/01/2014 02:04 AM, Shannon Dealy wrote:
On Sun, 30 Nov 2014, Nikolaus Rath wrote:
On 11/30/2014 07:07 PM, Nikolaus Rath wrote:
On 11/30/2014 01:07 AM, Shannon Dealy wrote:
Attached is the object_list.txt file from running fsck using your
patch.
Seems a little peculiar
On 12/01/2014 02:31 PM, Shannon Dealy wrote:
On Mon, 1 Dec 2014, Nikolaus Rath wrote:
[snip]
I think at this point I can probably write you a patch to get the file
system functional again, but I'd very much like to find out what's
happening here.
Would you be able to run fsck
severity -1 normal
retitle -1 fsck.s3ql sporadically crashes when checking objects
thanks
Retitling this bug and lowering severity for now. I don't think that the
mount.s3ql crash is related to the fsck.s3ql crashes, or that there is
any data corruption.
Best,
-Nikolaus
--
GPG encrypted emails
On 11/30/2014 12:50 AM, Shannon Dealy wrote:
I suspect this is because you copied the objects into a new bucket, but
did not include the associated metadata.
Which tool did you use to do the copy, and how did you call it?
I used the AWS command line tools:
aws s3 sync
On 11/30/2014 01:07 AM, Shannon Dealy wrote:
Attached is the object_list.txt file from running fsck using your patch.
Seems a little peculiar that the exception occurs at the 10 object
mark, though it may simply be chance and mean nothing:
..processed 10 objects so far..
On 11/30/2014 12:03 PM, Shannon Dealy wrote:
Poking around, it appears that the metadata was lost only on the
s3ql_metadata files, so I deleted them and ran the aws s3 sync
command again. The new files again were missing the metadata, so I just
copied the 13 s3ql_metadata files using
On 11/30/2014 07:07 PM, Nikolaus Rath wrote:
On 11/30/2014 01:07 AM, Shannon Dealy wrote:
Attached is the object_list.txt file from running fsck using your patch.
Seems a little peculiar that the exception occurs at the 10 object
mark, though it may simply be chance and mean nothing
On 11/29/2014 09:49 AM, Shannon Dealy wrote:
Package: s3ql
Version: 2.11.1+dfsg-1
Severity: critical
Justification: causes serious data loss
Dear Maintainer,
While running rsync to backup data to an s3ql file system mounted from
Amazon's
S3 services, the internet connection failed,
On 11/29/2014 01:36 PM, Shannon Dealy wrote:
On Sat, 29 Nov 2014, Nikolaus Rath wrote:
On 11/29/2014 09:49 AM, Shannon Dealy wrote:
Package: s3ql
Version: 2.11.1+dfsg-1
Severity: critical
Justification: causes serious data loss
Dear Maintainer,
While running rsync to backup data
On 11/29/2014 03:54 PM, Nikolaus Rath wrote:
1. mount.s3ql not coping well with a failed internet connection (a no
route to host failure, to be precise, it copes quite well with other
failures)
This one is actually a bug in python-dugong. I have just fixed this in
https://bitbucket.org
On 11/29/2014 03:54 PM, Nikolaus Rath wrote:
2. fsck.s3ql not being able to fix the local database
This one is more interesting. The traceback looks as if the backend (aka
S3) reports two objects with the same name (which I think should be
impossible). Since S3QL is using the object names
This is a consequence of a missing swap partition (bug #771492). After
fixing swap, hibernation works.
Wishlist: indicate the problem (missing swap) in the journalctl or
systemctl output.
Best,
-Nikolaus
--
GPG encrypted emails preferred. Key id: 0xD113FCAC3C4E599F
Fingerprint: ED31 791B 2C5C
Removing the swap keyword from /etc/crypttab makes things work.
Technically speaking, this keyword should not be there because I am
using the swap partition for hibernation (so mkswap should not be run).
It seems that sysvinit silently skipped the mkswap call, while systemd
now errors out.
I
Package: src:linux
Version: 3.16.7-2
Severity: normal
File: /boot/vmlinuz-3.16.0-4-amd64
About 20% of the time that I resume my system from hibernation, it
reboots during the resume. After the reboot, the system boots normally
(i.e., no resume).
For debugging, I have booted with
As promised, here are the full logs for a resume attempt ending with reboot.
microcom -p /dev/ttyUSB0
connected to /dev/ttyUSB0
Escape character: Ctrl-\
Type the escape character followed by c to get to the menu or q to quit
[0.00] CPU0 microcode updated early to
On Sat, 15 Nov 2014 00:17:59 +0100 Szymon Weihs szyn...@gmail.com wrote:
When I'm doing reboot or shutdown from graphical environment (systemctl
reboot/poweroff), my screen turns off immediately so I can't see any messages
provided with option systemd.show_status=true.
If I shutdown my
Hello,
I have found that adding
ExecStop=/bin/chvt 1
ExecStop=/sbin/start-stop-daemon --stop --quiet --pidfile
/var/run/lightdm.pid --name lightdm --retry 5
to the [Service] section in /etc/systemd/system/lightdm.service fixes
the problem. Shutdown and reboot work properly.
Best,
-Nikolaus
I just checked, and the system that is not affected by this issue is
using the radeon driver.
Might this be a problem with both the i915 and the nouveau driver?
--
To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org
with a subject of unsubscribe. Trouble? Contact
I have a second system that is not affected by this, but it uses the
radeon driver.
--
To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org
with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
I'm having the same problem, see #769369.
Unfortunately I haven't been able to tie this to any specific package or
hardware. I see it happening on some systems, but not on others.
My first guess was the graphics driver, but it happens with both intel
(i915) and nvidia (nouveau) cards.
Which
On 11/16/2014 10:05 AM, intrigeri wrote:
Control: tag -1 + moreinfo
Hi Szymon and Nikolaus,
Nikolaus Rath wrote (16 Nov 2014 16:53:49 GMT) :
I'm having the same problem, see #769369.
Unfortunately I haven't been able to tie this to any specific package or
hardware. I see it happening
Package: src:linux
Version: 3.16.7-2
Severity: normal
File: /boot/vmlinuz-3.16.0-4-amd64
Hello,
When adding
console=ttyS0,115200n8 console=tty0 no_console_suspend
to the kernel command line, I'm getting the following kernel Oops during
boot (full quote in kernel.log below):
[...]
[
Control: tag -1 -moreinfo
On 11/13/2014 01:45 PM, Ben Hutchings wrote:
On Thu, 2014-11-13 at 12:53 -0800, Nikolaus Rath wrote:
Package: src:linux
Version: 3.16.7-2
Severity: normal
File: /boot/vmlinuz-3.16.0-4-amd64
Hello,
When adding
console=ttyS0,115200n8 console=tty0
On a whim, I also tried blacklisting the nouveau module and using the
integrated graphics with the i915 module instead. It did not make a
difference.
-Nikolaus
--
To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org
with a subject of unsubscribe. Trouble? Contact
On November 13, 2014 5:03:56 PM PST, Ben Hutchings b...@decadent.org.uk wrote:
On 11/13/2014 01:45 PM, Ben Hutchings wrote:
On Thu, 2014-11-13 at 12:53 -0800, Nikolaus Rath wrote:
Package: src:linux
Version: 3.16.7-2
Severity: normal
File: /boot/vmlinuz-3.16.0-4-amd64
Hello
On 11/12/2014 10:42 AM, Andrey Rahmatullin wrote:
On Wed, Nov 12, 2014 at 11:22:55AM +0100, Lucas Nussbaum wrote:
=== FAILURES
===
_ test_httpcat
_
Traceback
More information:
* reboot -f and poweroff -f work fine.
* if I start a debug-shell on a serial port, at some point the shell
seems to freeze as well.
* if I boot with sysvinit (installing sysvinit-core instead of
systemd-sysv), things work fine:
- The system reboots even if an X11 console
Package: plymouth
Version: 0.9.0-7
Severity: normal
When *not* passing splash in the kernel command line, I can execute
systemctl reboot (or systemctl shutdown) and access the text console
during the shutdown process. In particular, I can use Ctrl+Alt+Fx to
interact with the systemd debug shell
Update: when running sufficiently long, journalctl eventually prints
something, but it is *very* slow. The strace output is:
mmap(NULL, 4198400, PROT_READ, MAP_SHARED, 6, 0x528000) = 0x7f46ace1a000
munmap(0x7f46ab617000, 8388608) = 0
mmap(NULL, 4198400, PROT_READ, MAP_SHARED, 7, 0x84d000)
retitle 764557 Persistent journal gets corrupted
thanks
Alright, the journal is not truly growing without bounds. Further below, I
found:
Permanent journal is using 819.7M (max allowed 3.8G, trying to leave 4.0G
free of 6.6G available → current limit 2.6G).
So this is probably not the
On 10/22/2014 12:15 AM, Kurt Roeckx wrote:
On Tue, Oct 21, 2014 at 06:33:50PM -0700, Nikolaus Rath wrote:
Package: openssl
Version: 1.0.1j-1
Severity: important
After my last testing upgrade, openssl s_client has trouble accepting
the -ssl3 and -ssl2 options. This prevents e.g. Gnus from
Package: openssl
Version: 1.0.1j-1
Severity: important
After my last testing upgrade, openssl s_client has trouble accepting
the -ssl3 and -ssl2 options. This prevents e.g. Gnus from using SSL
to connect to mailservers.
For example:
$ openssl s_client -ssl3 -quiet -connect ebox.rath.org:143
Downgrading to 1.0.1i-2 fixes the problem.
--
GPG encrypted emails preferred. Key id: 0xD113FCAC3C4E599F
Fingerprint: ED31 791B 2C5C 1613 AF38 8B8A D113 FCAC 3C4E 599F
»Time flies like an arrow, fruit flies like a Banana.«
--
To UNSUBSCRIBE, email to
Package: systemd
Version: 215-5+b1
Severity: normal
Hello,
I'm running Debian testing. After the last dist-upgrade, systemd has
started showing status messages during boot (sort of like sysvinit used
to do). This is certainly much prettier and more informative than the
blank screen that I had
On 10/08/2014 05:47 PM, Michael Biebl wrote:
Am 09.10.2014 um 02:43 schrieb Nikolaus Rath:
Package: systemd
Version: 215-5+b1
Severity: normal
Hello,
I'm running Debian testing. After the last dist-upgrade, systemd has
started showing status messages during boot (sort of like sysvinit
On 10/08/2014 06:17 PM, Michael Biebl wrote:
Am 09.10.2014 um 02:51 schrieb Nikolaus Rath:
On 10/08/2014 05:47 PM, Michael Biebl wrote:
Am 09.10.2014 um 02:43 schrieb Nikolaus Rath:
Package: systemd
Version: 215-5+b1
Severity: normal
Hello,
I'm running Debian testing. After the last dist
Package: systemd
Version: 215-5+b1
Severity: normal
Hello,
On this system, journalctl simply hangs. I tried running journalctl,
journalctl -b, and journalctl --list-boots, but nothing seems to do
anything:
# strace -o log journalctl --list-boots
^C
# tail log
reopen 763652
bye
On 10/01/2014 11:57 AM, Nikolaus Rath wrote:
On 10/01/2014 11:05 AM, Michael Biebl wrote:
Am 01.10.2014 um 18:49 schrieb Nikolaus Rath:
On 10/01/2014 09:22 AM, Michael Biebl wrote:
Am 01.10.2014 um 17:46 schrieb Nikolaus Rath:
Package: systemd
Version: 208-8
Severity
On 10/01/2014 09:22 AM, Michael Biebl wrote:
Am 01.10.2014 um 17:46 schrieb Nikolaus Rath:
Package: systemd
Version: 208-8
Severity: normal
Hello,
My last attempt to boot this system but me into systemd's emergency
mode. Runnig journalctl -xb showed that it failed to start plymouth
On 10/01/2014 09:23 AM, Michael Biebl wrote:
Am 01.10.2014 um 17:36 schrieb Nikolaus Rath:
Package: systemd
Version: 208-8
Severity: normal
File: /bin/journalctl
Hello,
I'm trying to retrieve the logs from the last book. journalctl(1) says:
-b [ID][±offset], --boot=[ID][±offset
On 10/01/2014 11:05 AM, Michael Biebl wrote:
Am 01.10.2014 um 18:49 schrieb Nikolaus Rath:
On 10/01/2014 09:22 AM, Michael Biebl wrote:
Am 01.10.2014 um 17:46 schrieb Nikolaus Rath:
Package: systemd
Version: 208-8
Severity: normal
Hello,
My last attempt to boot this system but me
Package: uml-utilities
Version: 20070815-1.3
Severity: normal
After boot, I have:
# ls -l /dev/net/
total 0
crw-rw 1 root root 10, 200 Sep 3 16:47 tun
Bringing the interface down and up again restores correct permissions
(so that user nikratio has access):
# ifdown tap0
# ifup tap0
Set
On 08/20/2014 03:14 AM, Matthias Klose wrote:
Am 20.08.2014 um 06:52 schrieb Nikolaus Rath:
If someone cares deeply about this, the necessary patch is at
https://bitbucket.org/nikratio/s3ql/commits/9a8c0ebbff390555e63b7e203b999b89aabbb86e/raw/.
I did not add it to the debian package yet
On 08/19/2014 01:33 AM, Matthias Klose wrote:
Control: severity -1 important
Care to provide a justification? There is no bug in the program itself,
so I don't see how this is has a major effect on the usability of a
package.
That's a bug in the test (race condition) rather than in the
Simon McVittie s...@debian.org writes:
On 19/08/14 09:33, Matthias Klose wrote:
[Nikolaus Rath wrote:]
That's a bug in the test (race condition) rather than in the program.
It's fixed upstream.
[...] If you don't care
about the autopkg tests, and if you are not ready to fix
On 08/13/2014 03:18 AM, Matthias Klose wrote:
http://ci.debian.net/data/packages/unstable/amd64/s/s3ql/20140811_044901.autopkgtest.log
=== FAILURES
===
__ NewerMetadataTest.test_all
Package: ftp.debian.org
Severity: normal
Hello,
Could you please remove the s3ql package for the sparc architecture?
Since the last release, the unit tests on sparc have started to
fail on the buildds, and I (as both maintainer and upstream) have
no way to reproduce the problem nor any idea of
Source: python-systemd
Severity: normal
Tags: patch
Hello,
Could you please provide systemd bindings for Python 3 as well?
I have attached a patch that might work. I wasn't able to test this
because for me systemd currently fails to build from source:
Package: src:linux
Version: 3.14.13-2
Severity: normal
File: /boot/vmlinuz-3.14-2-amd64
Hello,
I started a scrub of one of my btrfs filesystem and then had to restart
the system. `systemctl restart` seemed to terminate all processes, but
then got stuck at the end. The disk activity led was still
On 08/05/2014 07:01 PM, Ben Hutchings wrote:
On Sun, 2014-08-03 at 20:27 -0700, Nikolaus Rath wrote:
Package: src:linux
Version: 3.14.13-2
Severity: normal
File: /boot/vmlinuz-3.14-2-amd64
I was peacefully transferring a big file to my external USB harddisk
formatted with btrfs, when
Hi,
Maybe the correlation with the systemd upgrade is a coincidence. I've
kept track of the problems in more detail now. While with 208 about 10
in 20 resumes fail, I've also had 2 failures in 20 with systemd 204.
(this still doesn't explain why I had zero failures with the tens of
resumes
Package: src:linux
Version: 3.14.13-2
Severity: normal
File: /boot/vmlinuz-3.14-2-amd64
I was peacefully transferring a big file to my external USB harddisk
formatted with btrfs, when the kernel brutally lashed out with the BUG
below, preventing all further access to the disk:
--
On 07/27/2014 03:19 PM, Michael Biebl wrote:
Am 27.07.2014 23:55, schrieb Nikolaus Rath:
Package: systemd
Version: 208-6
Severity: normal
I am using systemd as pid 1. After a dist-upgrade on July 21st for testing,
I was unable to resume from hibernation anymore. The resume image would
I have no idea why the test would time out on s390x. Especially since
it's unchanged since the last release - which built just fine on s390x.
I will fix the kFreeBSD bugs and hope that the s390x problem was a fluke
that's going to disappear on the next build without me doing anything.
--
To
201 - 300 of 479 matches
Mail list logo
