Package: apt
Version: 2.1.11
Severity: normal
Since a few days I have been observing this bug during regular “apt
update” / “apt upgrade” cycles, without any configuration change on my
side; I am not completely sure if all this started after the last
upgrade to apt 2.1.11.
apt finds (testing,
Package: grub-pc
Version: 2.02~beta3-1
Severity: normal
After the usual "apt update; apt upgrade" cycle I got this error:
dpkg: error processing package grub-pc (--configure):
subprocess installed post-installation script returned error exit status 128
Errors were encountered while
Package: apt
Version: 1.2.7
Severity: normal
The /usr/bin/apt command causes a segmentation fault by list/search/show if the
user running it does not have the necessary permissions to read the
sources.list files. The bug can be reproduced in the following way:
# ls -l /etc/apt/sources.list.d/
Package: mutt-patched
Version: 1.5.23-3.1
Severity: normal
I noticed a problem with how mutt-patched deals with folders containing
new email messages. The behavior is somewhat different from the correct
one of unpatched mutt.
My muttrc configuration file contains the following:
set
Sebastian Ramacher [17.02.2014 23:28 +0100]:
Hi Alfredo,
On 2013-11-28 20:03:05, Alfredo Finelli wrote:
After some recent upgrade scrolling does not work correctly for me
anymore.
I use continuous pages with 5 pixels padding in between and the
standard value of scroll-full-overlap (0.1
Sebastian Ramacher [18.02.2014 16:47 +0100]:
...
Ugh, the documentation is wrong here. The default value is actually 0
(since 0.2.0 or 0.2.1). I have fixed the documentation upstream in
ba917f174bdcf852e0d5c49bc0c1cc30c9075d8d [1]. Apart from the
documentation issue, is there anything else
Sebastian Ramacher [29.11.2013 00:58 +0100]:
Hi Alfredo
Hi, thanks for the prompt reply.
On 2013-11-28 20:03:05, Alfredo Finelli wrote:
After some recent upgrade scrolling does not work correctly for me
anymore.
I suppose this started with 0.2.5, right?
Yes, this is correct
Package: zathura
Version: 0.2.6-1
Severity: normal
After some recent upgrade scrolling does not work correctly for me
anymore.
I use continuous pages with 5 pixels padding in between and the standard
value of scroll-full-overlap (0.1).
When in page-fit mode I get the correct behavior: a small
Ben Pfaff [11.11.2013 19:20 +0100]:
[...]
Thanks a lot for the patch! I would like to apply it to the Open
vSwitch repository. May I have a Signed-off-by: for this? e.g.:
Signed-off-by: Alfredo Finelli a...@computationes.de
By doing this, you are agreeing to the Developer's Certificate
Package: openvswitch-switch
Version: 1.9.3+git20131029-1
Severity: normal
Tags: patch
Some time after the last update I received email from the cron daemon with the
following error:
/etc/cron.daily/logrotate:
logrotate_script: 1: cd: can't cd to /var/run/openvswitch
After further
Ville Skyttä [09.03.2013 10:02 +0100]:
On 2013-03-07 14:52, Alfredo Finelli wrote:
The xpdf reader is also able to open PDF files compressed in
various formats (gz, bz2, xz, and Z).
My xpdf (version 3.03 on Fedora 18) isn't, and I see nothing in the
code that would implement that.
I don't
Package: bash-completion
Version: 1:2.0-1
Severity: normal
Tags: patch
The xpdf reader is also able to open PDF files compressed in various
formats (gz, bz2, xz, and Z).
The following patch allows completion for those cases (*.pdf.gz, etc.).
Best regards.
---
Package: grub-common
Version: 1.99-27
Severity: normal
Tags: patch
When using the commands grub-set-default and grub-reboot it is
possible, thanks to programmable completion, to let bash fill out the
command line with kernel names and boot options obtained from the entries
in
Package: apt-cacher
Version: 1.7.4
Severity: wishlist
When downloading a package from the Debian archive aptitude keeps it in
the directory /var/cache/apt/archives/partial. Upon completion the
file is then moved to the cache in /var/cache/apt/archives and then
installed. In case of network
Mark Hindley:
OK, I accept that this is not working properly on faster systems (than I
have). Actually the impact on response time and throughput is not as
great as I had previously thought either. This is my proposed solution
-- I would be grateful if you could test that it fixes it for you.
Mark Hindley:
Thanks. I will make the default 10.
Is the patched version always that much slower or is that just related
to what else was going on at the time?
It is hard to estimate exactly because I cannot measure/influence the
network congestion between the proxy and the Debian mirror.
Mark Hindley:
Thanks for this.
The select-can_read() timeout of 0.1 was the result of lots of
testing in bug #533830. Reducing the timeout may reduce your throughput
(which may not bother you ;)!) I am not sure why you see such high CPU
usage with 0.1. What hardware is it running on?
Mark Hindley:
Thanks.
From a purely selfish apt-cacher point of view we don't call select()
directly, it is only through IO::Select. Although I am reluctant to
deflect the blame, I think this maybe a perl-base bug.
Could you try this script and play with the timeout value in
Package: apt-cacher
Version: 1.7.4
Severity: normal
Tags: patch
The 'libcurl' thread spawned by apt-cacher to manage downloads is using too
much CPU time on my machine. I noticed just by chance that it easily
reaches 80-90% of sustained (not peak) usage during downloads.
This is the process in
Mark Hindley:
...
The full patch I have is below, perhaps you could verify it fixes it for
you.
I tested it with InRelease files only, then with Release and
InRelease present together, with and without obsolete packages in the
cache: now it behaves as expected both in the patch phase and in
Package: apt-cacher
Version: 1.7.3
Severity: normal
Tags: patch
apt-cacher-cleanup.pl is the Perl script used by apt-cacher to clean the
cache: it updates Packages and Sources index files and removes obsolete
.deb files; it is usually run daily or weekly by cron and has a command
line option to
I agree with you about the problem with an encrypted root partition. To
understand how safe it is to ignore the error I investigated the
behaviour of cryptsetup and lvm during shutdown and reboot.
- Cryptsetup. The only effect of luksClose, correct me if I am wrong,
is to remove the device
Package: cryptsetup
Version: 2:1.0.6-7
Severity: normal
My setup has / on a normal primary partition, /var and /usr on
logical volumes, /home and swap on encrypted logical volumes.
insserv is also used to populate the runlevel directories
/etc/rc*.d/, for parallel startpar execution of init
23 matches
Mail list logo
