Package: spampd
Severity: normal
Hello,
Thanks for the fast responses to my previous reports - excellent
maintainer work. But here is another one..
I have the problem that, from time to time, the spampd child process is
killed due to a timeout. This makes postfix send me an error message and
ref
Sven Mueller <[EMAIL PROTECTED]> wrote:
>> I have the problem that, from time to time, the spampd child process is
>> killed due to a timeout. This makes postfix send me an error message and
>> refuse the mail with 4xx ("queue file write error"). Bad..
>
> True.
>
>> My primary wish is to stop th
Jérôme Marant <[EMAIL PROTECTED]> writes:
>>> and #284216) as closed?
>>
>> IIRC this one was "introduced" by the fix to #165814; I have no idea
>> whether it is fixed. Nikolaus, do you still encounter it?
>
> Hmm, I wonder if #284216 is related to this bug
>
> http://bugs.debian.org/cgi-bin/bugr
Matthias Andree <[EMAIL PROTECTED]> wrote:
> On Wed, 11 May 2005, Nikolaus Rath wrote:
>
>> I'm using Gnus 5.10.7. Please tell me what you consider major, you probably
>> don't want it completely ;-)
>
> Does your Gnus use LIST ACTIVE or GROUP on leafnode
Matthias Andree <[EMAIL PROTECTED]> wrote:
> On Sun, 05 Jun 2005, Nikolaus Rath wrote:
>
>> It seems to use LIST without any arguments:
>
> It's impossible to deduce the interesting groups this way. I only have
> "No Gnus v0.4" here, which sends GROUP co
> This is a bug that was supposed to be fixed in 1.10.8, from NEWS:
>
> To resolve this bug, I need to reproduce it.
> Please provide details on your configuration:
>
> 1. leafnode configuration file, with passwords and user names stripped,
(attached)
## Unread articles will be deleted after t
Package: leafnode
Version: 1.10.8.rel-2
Severity: wishlist
Hello,
It would be very nice to be able to specify individual timeout_short and
timeout_long values for specific groups, as it is possible for expiry
times with groupexpire.
Reason: My low-traffic *.announce and *.info groups are permane
Package: postfix
Version: 2.1.5-8
Severity: normal
File: /etc/network/if-up.d/postfix
On system boot, the following message appears
Configuring network interfaces.../etc/network/if-up.d/postfix: line 17: [: =:
unary operator expected
-- System Information:
Debian Release: 3.1
APT prefers uns
On Thu, 17 Mar 2005 03:19:56 -0600
Manoj Srivastava <[EMAIL PROTECTED] (va, manoj)> wrote:
> Hi,
>
> Already done.
>
> __> dlocate starttls
> emacs21-common: /usr/share/emacs/21.3/lisp/gnus/starttls.elc
> emacs21-el: /usr/share/emacs/21.3/lisp/gnus/starttls.el
> gnus: /usr/share/emacs/site
Manoj Srivastava <[EMAIL PROTECTED] (va, manoj)> wrote:
> On Thu, 17 Mar 2005 16:21:19 +0100, Nikolaus Rath <[EMAIL PROTECTED]> said:
>
>> On Thu, 17 Mar 2005 03:19:56 -0600
>> Manoj Srivastava <[EMAIL PROTECTED] (va, manoj)> wrote:
>
>>> Already
Package: wnpp
Severity: wishlist
* Package name: starttls
Version : 0.10
Upstream Author : ?
* URL : ftp://ftp.opaopa.org/pub/elisp/
* License : GPL
Description : TLS encryption helper program
This program is necessary to establish STARTTLS connections
Hello!
It seems that the bug is fixed in 1.19-1, because I can't reproduce it
any longer.
I suspect that I forget to recreate the backup with the new version when
I checked it the last time, so I ran the new version with the data of
the old one.
Regards,
Nikolaus
--
To UNSUBSCRIBE, email
ree/" eq substr($f, 0, $lrestoreTree + 1)
(making both paths relative) or provide some other means to specify the
restore path when there are absolute paths in the MD5 file.
Best regards,
Nikolaus Rath
-- System Information:
Debian Release: 3.1
Architecture: i386 (i686)
Kernel: Linux 2.6.12.emp8
Package: laptop-mode
Version: 0.4
Severity: normal
There are some configuration options in /usr/sbin/laptop_mode, namely
---snip--
# Shall we remount journaled fs. with appropiate commit interval?
# (1=yes)
DO_REMOUNTS=1
# And shall we add the "noatime" option to that as well? (1=yes)
DO_REMOUN
Package: leafnode
Version: 1.10.7.rel-1
Severity: normal
Hello,
I experienced the following with Thunderbird 1.0.2. THunderbird is
connected to localhost and has subscribed some groups. The following is
the output of the leafnode debug log when Thunderbird checks for new
groups:
Jul 30 12:46:44
Mark Brown wrote:
Package: leafnode
Version: 1.10.7.rel-1
Severity: normal
Could you please check to make sure that this has not already been
fixed in a more current version of the package such as the current
version in stable? The version you are using is quite old and there
have been some re
Mark Brown wrote:
Versions of packages leafnode depends on: ii debconf 1.4.42ubuntu4
Debian configuration management sy ii libc6 2.3.2.ds1-20ubuntu13
GNU C Library: Shared libraries an
I have just noticed you appear to be using Ubuntu. Please report
bugs in Ubuntu to Ubuntu. Information a
Package: spampd
Severity: normal
According to the debian changelog, the patch for envelope header adding
was applied to spampd. Yet I'm unable to find it: No commandline option,
no manpage, and no hint in the script itself.
public:/usr/share/doc/spampd# grep Envelope /usr/sbin/spampd
public:/usr
Package: im
Severity: normal
For each mail in the Shared.spam-to-learn folder, the first try to fetch
it fails:
[0] ebox:/usr/local/etc/spamassassin# echo | imget -s
imap%Shared.spam-to-learn//LOGIN:[EMAIL PROTECTED] -d /tmp/spam-to-learn -v
imget: folder=Shared.spam-to-learn auth=LOGIN use
Package: swish-e
Version: 2.4.2-1
Severity: normal
After the last dist-upgrade, swish-e floods me with error messages like
^
/home/nikratio/lib/archive/Infos/einstein.pdf:5: warning: Error '1' converting
internal UTF-8 to Latin-1.
/home/nikratio/lib/archive/Inf
>> Package: swish-e
>> Version: 2.4.2-1
>
>Please, could you try with swish-e 2.4.3-1, it's the latest release ?
Done that, seems to be fixed. Sorry for the inconveniences.
Package: gnus
Version: 5.10.6-0.CVS.20050104-1
Severity: wishlist
Hello,
It would be great if the starttls programm could be made available in
debian as well. It is necessary for making STARTTLS IMAP connections
with gnus.
I don't know if it's better to add a separate package (there's probably
m
Package: bbdb
Version: 2.35.cvs20040528-1
Severity: normal
Tags: upstream patch
I've set news-auto-create-p to a function which returns 'prompt.
However, I'm never asked for confirmation. I have tracked down the
problem to the if construction in bbdb.el and attached a patch.
The problem seems to
Package: libgtk2.0-0
Version: 2.6.2-3
Severity: important
After upgrading to the latest version, I suddenly experience very
strange errors:
- Clicking on an Icon in the gnome-panel results in:
"Cannot launch icon.
Details: Text was empty (or contained only whitespace)"
- Saving files in
Sebastien Bacher <[EMAIL PROTECTED]> wrote:
> Le jeudi 24 février 2005 à 12:01 +0100, Nikolaus Rath a écrit :
>
>>Conversion from character set 'UTF-8' to '@local' is not supported"
>>
>>After unsetting G_FILENAME_ENCODING, everything
Package: openoffice.org-bin
Version: 1.1.3-4
Severity: normal
Hello,
When starting openoffice, the following warning appears:
[0] local:~$ openoffice
OpenOffice.org lockfile found (/home/nikratio/.openoffice/1.1.3/.lock)
Using existing OpenOffice.org
(process:2370): Gdk-WARNING **: locale not
Package: spamassassin
Version: 3.1.7-2
Followup-For: Bug #364922
I can confirm this bug, the problem exists here as well.
-- System Information:
Debian Release: 4.0
APT prefers stable
APT policy: (500, 'stable')
Architecture: i386 (i686)
Shell: /bin/sh linked to /bin/bash
Kernel: Linux 2.6.9
Package: logcheck
Version: 1.2.39
Severity: normal
Hello,
Due to the incorrect group ownership bug (which has already been fixed)
I ended up with logcheck not being able to read any files in
/etc/logcheck/ignore.d.paranoid. However, instead of complaining that
some files were unreadable, logcheck
Ian Jackson writes:
> (I have cloned the bug for this, to keep this particular
> sub-discussion separable.)
>
> As I have reported, we have a problem with non-forking daemon
> readiness protocols.
"We have a problem" seems a bit exxagerated to me. So far, the only
problem that I have seen is that
Steve Langasek writes:
> On Sat, Dec 28, 2013 at 05:24:57PM -0800, Russ Allbery wrote:
>
>> I'll have more to say about the relative merits of the two init systems
>> later, but one thing I wanted to not briefly: this exercise was extremely
>> valuable in helping me get a more realistic picture of
Hello,
It's already been mentioned elsewhere, but I think it should be included in
this bug for reference. The minimum code to support systemd style readyness
notification is (from
https://plus.google.com/+LennartPoetteringTheOneAndOnly/posts/37AWJLE3XcJ):
static void notify(const char *d
Ian Jackson writes:
> It does, however, have a number of missing features. Those I have in
> mind are:
> - ability to log daemon output to syslog
> - multiple socket activation (systemd socket activation protocol)
> - socket activation for IPv6 (and datagram sockets)
>
> Of these Russ right
Steve Langasek writes:
> On Sun, Dec 29, 2013 at 01:43:59PM -0800, Nikolaus Rath wrote:
>> I'm a bit surprised that you mention this only now, after Russ'
>> extensive mail. Could you tell us if there are there other components in
>> systemd that you think are simi
Colin Watson writes:
> The criticisms of Upstart's event model in the systemd position
> statement simply do not make sense to me. Events model how things
> actually happen in reality; dependencies are artificial constructions on
> top of them, and making them work requires the plethora of differ
On 01/01/2014 04:00 PM, Nikolaus Rath wrote:
> My second point is that by treating dependencies as events, upstart does
> not seem to truly recognize dependencies as such and is then unable to
> resolve them. For example, with the following two job files (created
> according to
Cameron Norman writes:
> On Wed, Jan 1, 2014 at 4:00 PM, Nikolaus Rath wrote:
>
>> Colin Watson writes:
>> > The criticisms of Upstart's event model in the systemd position
>> > statement simply do not make sense to me. Events model how things
>> >
Cameron Norman writes:
>> > I think you raise a lot of good points in this email, but here you
>> > are saying something which may demonstrate your (understandable)
>> > confusion about the Upstart event model. Upstart does not treat
>> > dependencies as events. Often times, Upstart //jobs// treat
Zbigniew Jędrzejewski-Szmek writes:
>> As I understand, a systemd unit with "Requires=jobTwo" will not start
>> without jobTwo running.
>
> If you request the start of "jobOne", without "jobTwo" running,
> systemd will start "jobTwo" in addition to "jobOne".
>
> There's also a Requisite= dependenc
Russ Allbery writes:
> This message is about a transition plan for an init system replacement and
> about how to handle portability to our non-Linux ports. I'm keeping the
> same subject as Ian's message on the same basic topics and attaching it to
> the same thread, but this is more of a separat
Steve Langasek writes:
> However, I think this gets to the heart of why upstart upstream has avoided
> ever recommending the use of socket-based activation. There are some fairly
> fundamental problems that basically halted development of socket-based
> activation in upstart (beyond merging of Sc
On 01/02/2014 10:20 AM, Ian Jackson wrote:
> Nikolaus Rath writes ("Bug#727708: loose ends for init system decision"):
>> I think there is one additional questions that will probably need to be
>> decided by the tc but hasn't really been discussed yet:
>>
>&
On 01/02/2014 10:30 AM, Ian Jackson wrote:
> Nikolaus Rath writes ("Re: Bug#727708: loose ends for init system decision"):
>> For example, a hypothetical future program to interactively adjust
>> program cgroups cannot be sysvinit compatible in any meaningful sense,
>&
Ian Jackson writes:
> | Choice of init system:
> |
> | 1. The default init(1) in jessie will be upstart.
> |
> | 2. Architectures which do not currently support upstart should try to
> |port it. If this is not achieved in time, those architectures may
> |continue to use sysvinit. [ Non-
Package: cryptsetup
Version: 2:1.4.3-4
Severity: wishlist
Thanks for packaging cryptsetup!
It would be great if the cryptsetup package could recommend
(or maybe suggest) the keyutils package, since the latter is
required for /lib/cryptsetup/scripts/decrypt_keyctl to work.
Best,
Nikolaus
-- Sy
Clint Adams writes:
> On Fri, Jan 03, 2014 at 10:02:01AM -0800, Nikolaus Rath wrote:
>> As said elsewhere, I think there should be a paragraph about packages
>> that depend on a specific init system for reasons other than service
>> startup, e.g.
>>
>> 4. Th
Russ Allbery writes:
>> I've written a version of Niklaus's rule about dependencies:
Just for the record, my suggestion was to include language that
regulates dependencies on the init system, but I do not have any
preferences whether they should be allowed or forbidden.
>>Likewise, packages
Uoti Urpala writes:
> On Fri, 2014-01-03 at 20:26 -0800, Nikolaus Rath wrote:
>> Clint Adams writes:
>> > On Fri, Jan 03, 2014 at 10:02:01AM -0800, Nikolaus Rath wrote:
>> >> or alternatively
>> >>
>> >> 4. Packages may, however, depen
Ian Jackson writes:
> Thomas Goirand writes ("Bug#727708: The tech ctte isn't considering OpenRC at
> all"):
>> But that OpenRC just hasn't been considered just because of rumors is
>> really unacceptable.
>
> The reason I haven't seriously considered OpenRC for the default is
> that it wasn't re
Ian Jackson writes:
> Nikolaus Rath writes ("Bug#727708: The tech ctte isn't considering OpenRC at
> all"):
>> Ian Jackson writes:
>> > Thomas, does OpenRC provide a means for do non-forking daemon
>> > startup ?
>> [...]
>>
>>
Andres Freund writes:
> On 2014-01-19 23:18:26 -0800, Steve Langasek wrote:
>> As you say that planned features or development could sway your opinion: are
>> there particular features that you have in mind, here? For instance,
>> correcting upstart's socket-based activation interface is on the u
Bdale Garbee writes:
> Ian Jackson writes:
>
>> I hereby propose the following resolution:
>>
>> 1. The Technical Committee does not wish any resolutions it passes
>> about the init system question(s) to stand in the face of any
>> contrary view expressed by a majority of the Develope
Michael Gilbert writes:
> On Mon, Feb 3, 2014 at 1:42 PM, Steve Langasek wrote:
>> So all deferring for another cycle does is leave Debian with annoying
>> cumbersome init scripts and unsolvable race conditions for another cycle.
>
> Which have already been solved for a long time now.
No, they ha
Michael Gilbert writes:
> On Mon, Feb 3, 2014 at 11:44 PM, Nikolaus Rath wrote:
>> Michael Gilbert writes:
>>> On Mon, Feb 3, 2014 at 1:42 PM, Steve Langasek wrote:
>>>> So all deferring for another cycle does is leave Debian with annoying
>>>> c
Russ Allbery writes:
> Don Armstrong writes:
>> On Thu, 06 Feb 2014, Kurt Roeckx wrote:
>
>>> So let me expand on that a little. Image the following options
>>> - A: something that doesn't overrule the ctte (1:1)
>>> - B: something that does overrule the ctte (2:1)
>>> - FD
>
>> In this case, I
Ian Jackson writes:
> Ansgar Burchardt writes ("Re: Additional CTTE Drafting Meeting useful?"):
>> In this case I suggest to decide just the question of the default init
>> system on Linux architectures first and address further details later if
>> no consensus can be found elsewhere. Finding the
Package: python-pytest
Version: 2.2.4-2
Severity: grave
Justification: renders package unusable
With latest python3-pytest from sid, I get
# py.test-3.3
Traceback (most recent call last):
File "/usr/bin/py.test-3.3", line 5, in
sys.exit(load_entry_point('pytest==2.4.2', 'console_scripts',
A nice thing about the SIGSTOP mechanism is that it can trivially be
used even in programs not written in C. Any Perl or Python script (and
there are plenty of daemons written in these languages) can send itself
SIGSTOP. Using sd_notify requires to re-implement the protocol or to add
C adaptor code
As far as I know, specifying a boolean combination of events "forces"
them to occur simultaneously by "latching" all involved events.
In other words, if you have a job depending on "A and B", and a program
foo then emits event A, then foo (by default) going to block until some
other program emits
Hello,
I am aware that this bug already has a lot of emails in it, but I think
the issue below is important enough to warrant a
*ping*
to the upstart developers. It would be great if someone could comment on
this.
Best
Nikolaus
Nikolaus Rath writes:
> Cameron Norman writes:
>> On
Martin Pitt writes:
> Bdale Garbee [2014-01-13 13:57 -0700]:
>> Ian Jackson writes:
>>
>> > I'm coming round to the view that we should be planning to support
>> > multiple systems indefinitely.
>>
>> This has been my opinion all along. Various assertions that it's
>> somehow just too hard rea
Anthony Towns writes:
> To emulate systemd dependencies in an event model (ie, X depends on
> Y), you'd need to do either:
>
> * change Y's job to say "start on starting X"
> * add "stop on stopping Y" to X's job description
>
> or
>
> * add a pre-start script to X in order to start Y
Hi,
I just want to raise one issue that I think has not been adequately
addressed by any of the position statements (it has unfortunately been
deleted from the upstart page and been trimmed down a lot on the systemd
page):
I think an important drawback of upstart is the idea of treating
dependenc
On 10/31/2013 09:51 PM, Russ Allbery wrote:
> You can, of course, be
> disciplined about this when writing systemd helper scripts by always
> exernalizing the shell script into a separate file, but I really like that
> upstart lets me inline trivial shell fragments without worrying about
> that whi
severity 746908 normal
bye
Setting severity to normal, because it builds just fine for me.
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 Ba
Package: release.debian.org
Severity: normal
User: release.debian@packages.debian.org
Usertags: rm
Hello,
Could you please remove the s3ql package from testing? It's already
scheduled for autoremoval, but it'd be nice if we don't have to wait for
the deadline to pass.
There is a new s3ql rel
On 04/18/2014 01:35 AM, Niels Thykier wrote:
>> Could you please remove the s3ql package from testing? It's already
>> scheduled for autoremoval, but it'd be nice if we don't have to wait for
>> the deadline to pass.
>>
>> There is a new s3ql release in unstable that fixes the RC bug of
>> the vers
Package: ftp.debian.org
Severity: normal
Hello,
Could you please remove the s3ql 2.7 1 packages for kfreebsd-i386 and
kfreebsd-amd64 in unstable?
The newest upstream release (2.8.1) does not build under FreeBSD
anymore (upstream started to use epoll), and the old kfreebsd
versions are blocking m
reassign 745243 python-dugong
thanks
The build actually works fine. The unit tests fail, but this is because
the python3-dugong package is not kFreeBSD compatible.
--
GPG encrypted emails preferred. Key id: 0xD113FCAC3C4E599F
Fingerprint: ED31 791B 2C5C 1613 AF38 8B8A D113 FCAC 3C4E 599F
> Package: s3ql
> Version: 2.8.1+dfsg-1
>
> On http://ci.debian.net/#package/s3ql > I discovered that the
> automatic self test of s3ql is failing. This is the reported fail at
> the end of the log:
>
> tests/t2_block_cache.py:114: cache_tests.test_destroy_deadlock FAILED
Thanks for the report!
Package: wnpp
Severity: wishlist
Owner: Nikolaus Rath
* Package name: python-dugong
Version : 1.0
Upstream Author : Nikolaus Rath
* URL : https://bitbucket.org/nikratio/python-dugong
* License : PSF (Python Software Foundation License)
Programming Lang
Package: dpkg-dev
Version: 1.17.6
Followup-For: Bug #742535
Is there some workaround for this? I'm trying to upload a package to
mentors, but dput steadfastly refuses to do this as long as the md5sum
is wrong...
Best,
-Nikolaus
--
To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian
On 05/02/2014 06:45 AM, Debian Bug Tracking System wrote:
> We believe that the bug you reported is now fixed; the following
> package(s) have been removed from unstable:
>
> s3ql | 2.8.1+dfsg-1 | kfreebsd-amd64, kfreebsd-i386
> s3ql-dbg | 2.8.1+dfsg-1 | kfreebsd-amd64, kfreebsd-i386
>
>
Package: anacron
Version: 2.3-20
Followup-For: Bug #744753
I've been hit by this as well. It's rather annoying because it's a
completely silent failure.
Instead (or maybe also in addition to) having anacron started by systemd
on resume, would it be possible to change /etc/cron.d/anacron to start
Hi Michael,
On 05/30/2014 06:06 AM, Michael Biebl wrote:
> Am 30.05.2014 04:11, schrieb Nikolaus Rath:
>> Package: systemd
>> Version: 204-8
>> Severity: grave
>> Justification: causes non-serious data loss
>>
>> 'systemctl hibernate' (and proba
The recent builds (e.g.
https://buildd.debian.org/status/fetch.php?pkg=s3ql&arch=amd64&ver=2.8.1%2Bdfsg-1%2Bb1&stamp=1401360556&file=log)
actually build the s3ql application just fine. What fails is building
the documentation and running the unit tests:
Running html builder...
creating /«BUILDDIR»
On 05/30/2014 09:20 AM, Michael Biebl wrote:
> Am 30.05.2014 17:58, schrieb Nikolaus Rath:
>>
>> - new kernel is silently installed by unattended-upgrades (apparently
>> this happens even when the new package breaks the ABI) and becomes the
>> default to be loaded by the
On 05/30/2014 10:46 AM, Michael Biebl wrote:
> Am 30.05.2014 18:34, schrieb Nikolaus Rath:
>>>
>>> The problem with simply doing nothing on hibernate when
>>> /run/do-not-hibernate exists, is that this is also not visible to the
>>> user since there there is
On 05/31/2014 04:36 PM, Jakub Wilk wrote:
> * Nikolaus Rath , 2014-05-30, 09:04:
>> The recent builds (e.g.
>> https://buildd.debian.org/status/fetch.php?pkg=s3ql&arch=amd64&ver=2.8.1%2Bdfsg-1%2Bb1&stamp=1401360556&file=log)
>> actually build the s3ql applicati
I just did a test build with gcc 4.9 in a local sid pbuilder chroot, and
it works just fine.
Matthias, is this problem reproducible for you?
Best,
-Nikolaus
--
GPG encrypted emails preferred. Key id: 0xD113FCAC3C4E599F
Fingerprint: ED31 791B 2C5C 1613 AF38 8B8A D113 FCAC 3C4E 599F
Jonathan Nieder writes:
> Charles Plessy wrote:
>
>>In particular, in the absence of
>> Bill's contribution to the resolution of our conflict, I am asking the TC to
>> not discuss the menu systems and focus instead on correcting Bill's
>> misbehaviour.
>
Hi,
A decent workaround for this bug is to use the mod-proxy-html module. It
rewrites addresses within the served content.
Best,
-Nikolaus
--
Encrypted emails preferred.
PGP fingerprint: 5B93 61F8 4EA2 E279 ABF6 02CF A9AD B7F8 AE4E 425C
»Time flies like an arrow, fruit flies lik
On 11/03/2012 06:48 PM, Jeff Licquia wrote:
> On 10/22/2012 09:24 AM, Nikolaus Rath wrote:
>> This problem continues to occur regularly. Is there something else I can
>> do to help?
>
> I took another look to see if I could figure out what might be
> happening, and came u
Hi,
This problem continues to occur regularly. Is there something else I can
do to help?
Best,
-Nikolaus
--
»Time flies like an arrow, fruit flies like a Banana.«
PGP fingerprint: 5B93 61F8 4EA2 E279 ABF6 02CF A9AD B7F8 AE4E 425C
--
To UNSUBSCRIBE, email to debian-bugs-dist-requ...
On 08/26/2012 10:14 PM, Nikolaus Rath wrote:
> On 08/26/2012 10:06 PM, Jeff Licquia wrote:
>> > On 08/11/2012 09:49 PM, Nikolaus Rath wrote:
>>> >> Here we go:
>> >
>> > I've played with this a little, using the results from the dir listings
>&
On 01/30/2012 04:59 PM, Alexander Holupirek wrote:
> $ python2.7 llfuse-0.37.1/contrib/example.py /var/tmp/mnt
> [ ... other shell ... ]
> $ touch /var/tmp/mnt/foo
> touch: cannot touch `/var/tmp/mnt/foo': Input/output error
> Traceback (most recent call last):
> File "llf
Package: lsb-release
Version: 4.1+Debian7
Severity: normal
File: /usr/share/pyshared/lsb_release.py
With the following sources.list:
| deb-src http://mirror.cc.columbia.edu/debian/ testing main contrib non-free
| deb http://mirror.cc.columbia.edu/debian/ testing main contrib non-free
the output
On 07/15/2012 03:47 PM, Jeff Licquia wrote:
> On 07/14/2012 11:45 AM, Nikolaus Rath wrote:
>> When using the http.debian.net redirector, though
>>
>> | deb-src http://http.debian.net/debian/ testing main contrib non-free
>> | deb http://http.debian.net/debian/ te
On 08/26/2012 10:06 PM, Jeff Licquia wrote:
> On 08/11/2012 09:49 PM, Nikolaus Rath wrote:
>> Here we go:
>
> I've played with this a little, using the results from the dir listings
> (which don't look odd to me).
>
> From what I can tell, the ultimate cause of
On 07/15/2012 06:35 PM, Nikolaus Rath wrote:
> On 07/15/2012 03:47 PM, Jeff Licquia wrote:
>> On 07/14/2012 11:45 AM, Nikolaus Rath wrote:
>>> When using the http.debian.net redirector, though
>>>
>>> | deb-src http://http.debian.net/debian/ testing
Hello,
Problem happened again today. sources.list hasn't been touched, but
suddenly release detection fails:
# python
Python 2.7.3rc2 (default, Apr 22 2012, 22:30:17)
[GCC 4.6.3] on linux2
Type "help", "copyright", "credits" or "license" for more information.
>>> import lsb_release
>>> lsb_releas
Package: qemu-system
Version: 1.1.0+dfsg-1
Severity: normal
File: /usr/bin/qemu-system-i386
After the update from 1.0+dfsg-11 to 1.1.0+dfsg-3 I can no longer
use host usb devices in the guest. I assume that it is a general
USB problem, but was only able to test with an SCM SCR3310
smartcard reade
Hello,
Downgrading to qemu-kvm_1.0+dfsg-11_amd64.deb from
http://snapshot.debian.org/package/qemu-kvm/1.0%2Bdfsg-11/#qemu-kvm_1.0:2b:dfsg-11
fixes the problem.
Best,
-Nikolaus
--
»Time flies like an arrow, fruit flies like a Banana.«
PGP fingerprint: 5B93 61F8 4EA2 E279 ABF6 02CF A9AD
On 08/06/2012 02:14 AM, Michael Tokarev wrote:
> On 06.08.2012 04:25, Nikolaus Rath wrote:
>> Package: qemu-system
>> Version: 1.1.0+dfsg-1
>> Severity: normal
>> File: /usr/bin/qemu-system-i386
>>
>> After the update from 1.0+dfsg-11 to 1.1.0+dfsg-3 I can
Here we go:
[0] vostro:~$ python -c 'import lsb_release; print
lsb_release.get_distro_information()'
{'RELEASE': 'testing/unstable', 'OS': 'GNU/Linux', 'ID': 'Debian',
'DESCRIPTION': 'Debian GNU/Linux testing/unstable'}
[2] vostro:~$ ls -l /var/lib/apt/lists
total 122400
-rw-r--r-- 1 root root
Package: tomboy-latex
Version: 0.5-3
Severity: grave
Justification: renders package unusable
Tomboy-latex 0.5 is not compatible with Tomboy 0.10 (the only version
in wheezy). The currently packaged version of tomboy-latex is therefore
unusable. Note that the current upstream version (0.7) is compa
Package: python-apsw
Version: 3.7.6.3-r1-1
Severity: wishlist
Dear Maintainer,
It would be great to have a python3-apsw package. APSW is already Python
3 compatible, so this should be a pure packaging issue.
Best,
Nikolaus
-- System Information:
Debian Release: 7.0
APT prefers stable
APT po
Package: unattended-upgrades
Version: 0.79.5
Severity: normal
Dear Maintainer,
Recently, unattended-upgrades has started crashing with:
Traceback (most recent call last):
File "/usr/bin/unattended-upgrade", line 1011, in
main(options)
File "/usr/bin/unattended-upgrade", line 793, in mai
retitle 701350 Data corruption with eglibc 2.17
thanks
The unit test in question fails when using eglibc 2.17, independent of
the gcc version.
The reason is a bug in src/s3ql/_deltadump.pyx, which repositions a file
descriptor associated with a FILE* stream without first calling
fflush(). I do no
Package: s3ql
Version: 1.11.1-3
Severity: wishlist
With the release of wheezy, it is now principally possible to provide
up-to-date S3QL versions for Debian stable via backports.
This bug is meant to gauge demand for this, so if you are interested
in getting regular S3QL updates for wheezy, pleas
Hi Michael,
What does the "experimental" tag mean? I just removed the "sid" tag on
behest of the release team, so I'm not sure that this one is appropriate
either.
Note that even though the unit tests only fail with libc 2.17, both the
woody and sid S3QL versions contain the buggy code.
Best,
-
1 - 100 of 480 matches
Mail list logo
