can be applied through git-apply
or git-am. If you'd rather receive it in the old context format, I'd be
happy to convert it to context format.
Should you accept the patch, I'd appreciate if you could email me a notice
when it gets pushed to your public git repository.
Yours sincere
On Tue, 10 May 2011, Hector Oron wrote:
> Here an updated patch:
...
It was whitespace-damaged, but I fixed it. Will forward to upstream, now.
--
"One disk to rule them all, One disk to find them. One disk to bring
them all and in the darkness grind them. In the Land of Redmond
where the
On Tue, 10 May 2011, Hector Oron wrote:
> The patch was wrong. Not only because it was missing then in the if
> clause, but also the check does not seem to work properly. Here there
> is an updated and tested patch:
The patch does not match the equivalent test for __ARM_EABI__ a few
lines above.
On Mon, 09 May 2011, Hector Oron wrote:
> Note I have not tested the patch, if you (Konstantinos) could test it
> great, if not I'll try to do so later on.
I will wait for a report that the patch is correct and tested, then I will
forward.
--
"One disk to rule them all, One disk to find them.
tag 626101 upstream moreinfo
thanks
On Sun, 08 May 2011, Debian Bug Tracking System wrote:
> Bug #626101 [autotools-dev] eglibc: FTBFS on armhf, does not detect triplet.
armhf (unknown-linux-gnueabihf) is not supported by GNU config upstream as
of 2011-05-08, according to the commits in their pub
On Sun, 08 May 2011, Torquil Macdonald Sørensen wrote:
> Ok, that makes sense. I was (most likely incorrectly) under the
> impression that the names (package and library file) had to be the
> same, since I previously got a lintian warning about this (before I
> included the 4-0 in libtrng4-0).
Wel
On Sun, 08 May 2011, Torquil Macdonald Sørensen wrote:
> >Might you consider using tinarng as the package name, please?
> >
> >TRNG is commonly used as the abbreviation of True Random Number
> >Generator (and variations, such as thruly random number generator).
> >
> >It could cause some confusion.
On Fri, 06 May 2011, Chris Warburton wrote:
> Hi Scott. ocPortal isn't massively widespread compared to other systems,
> so there's obviously less experimental proof of security. We had a
> security hole a few years ago; this was before I got involved, but
> there's details here http://en.wikipedia
On Fri, 06 May 2011, Tomas Pospisek wrote:
> >I suspect this bug really is in the kernel, and only affect some video
> >cards. Which video card are you using?
>
> 00:02.0 VGA compatible controller: Intel Corporation Mobile GM965/GL960
>Integrated Graphics Contr
On Fri, 06 May 2011, Tomas Pospisek wrote:
> Synopsis:
> =
> when the machine does an fsck while booting, there's no way to know.
> The user should be informed of the fact otherwise she has no way to
> know whether the machine is dead or not.
Hmm? It is, fsck outputs everything to all act
On Sun, 01 May 2011, Torquil Macdonald Sørensen wrote:
> Package: wnpp
> Severity: wishlist
> Owner: "Torquil Macdonald Sørensen"
>
> * Package name: trng
> Version : 4.11
> Upstream Author : Heiko Bauke
> * URL : http://trng.berlios.de/
> * License : BSD
>
On Sun, 01 May 2011, Henrique de Moraes Holschuh wrote:
> On Sat, 30 Apr 2011, Russ Allbery wrote:
> > Steve Langasek writes:
> > > I don't think that /etc/shadow qualifies as a "configuration file",
> > > either; I would call it "variable state i
On Sat, 30 Apr 2011, Russ Allbery wrote:
> Steve Langasek writes:
> > I don't think that /etc/shadow qualifies as a "configuration file",
> > either; I would call it "variable state information" (→ /var/lib), but
> > it lives in /etc because a) it has to be on the root filesystem, b)
> > that's wh
On Thu, 14 Apr 2011, Bastian Blywis wrote:
> When /etc/init.d/reboot is run and "reboot -d -f -i" called, in about
> 2-4% of the cases, the system will deadlock because the network
> interfaces are shut down but the kernel still wants to read/write
> something on the nfs export. The message "nfs se
On Sun, 10 Apr 2011, Steve Langasek wrote:
> multiarch. The attached patch has been applied in Ubuntu for this issue,
> correcting this call to use --with-com_err with no argument to get the
> default search path.
Has this been triple-checked to do the right thing? I used to have to
employ extre
On Thu, 07 Apr 2011, Ondřej Surý wrote:
> is sufficient or we should add a hard dependency on libsasl2-modules.
We cannot, it would be a layering violation. We already document this
throughoutly.
--
"One disk to rule them all, One disk to find them. One disk to bring
them all and in the dar
On Tue, 05 Apr 2011, Christian PERRIER wrote:
> I have actually been surprised of not getting any answer to this "NMU
> intent". I don't really intend to NMU sysvinitat least not until I
> get a quite clear ACK from its maintainers. We're not talking about a
> random package here..:-)
It was i
On Fri, 11 Mar 2011, Adam D. Barratt wrote:
> On Fri, 2011-03-11 at 16:54 -0300, Henrique de Moraes Holschuh wrote:
> > On Fri, 11 Mar 2011, Martin Zobel-Helas wrote:
> > > On Fri Mar 11, 2011 at 13:11:52 -0600, Gunnar Wolf wrote:
> > > > Chile was supposed to lea
On Fri, 11 Mar 2011, Martin Zobel-Helas wrote:
> On Fri Mar 11, 2011 at 13:11:52 -0600, Gunnar Wolf wrote:
> > I was prodded by my Chilean friend, Germán Póo-Caamaño, to help find a
> > way to push the tzdata corrections needed for Chile's change of
> > timezone plans. Trying to do so, I found he a
On Wed, 02 Mar 2011, Sean Finney wrote:
> Having a warning in lintian for arbitrarily long (perhaps >= 256)
> filenames is totally reasonable i'd say, but there's no reason to
Most (all?) filesystems commonly used in Debian systems will limit you to
somewhere close to 254 characters per filename (
Package: autotools-dev
Version: 20100122.1
Severity: minor
The examples need to be updated to be useful, or outright dropped.
-- System Information:
Debian Release: 6.0
APT prefers stable
APT policy: (990, 'stable'), (500, 'squeeze-updates'), (500, 'unstable'), (1,
'experimental')
Architectu
On Sun, 27 Feb 2011, Russell Coker wrote:
> Henrique, I'll give you an account on one of my SE Linux development machines
> to test this.
I will try to check it during this week. Looks like some packaging
issue, which I should be able to fix (unlike hooking SELinux to a
cron-like daemon :-) ).
On Mon, 28 Feb 2011, Olaf van der Spek wrote:
> Sure. But Sergey has a good point: why are there no bin and lib inside
> /home so normal users can safely install software without risking
AFAIK, there are strong security concerns. You cannot have unprotected
directories in the default linker paths
On Mon, 28 Feb 2011, Olaf van der Spek wrote:
> > places. So if you want /usr/local/bin binaries to see /usr/local/lib
> > by default (that's what Debian and other Linux systems do, on purpose),
> > then all your system binaries will see them too. Anyway, it's not a
> > bug or even really a desig
(fixed Russell's email address)
On Sat, 26 Feb 2011, Alexander Kurtz wrote:
> * The current version in Debian (3.0.1) is severely outdated:
>Upstream has released 5 new stable versions in the mean time[8]
Yeah, and I cannot update it to the latest upstream without breaking
SELinux, AND I can
On Fri, 18 Feb 2011, Jonas Smedegaard wrote:
> * Package name: vargs
> Version : 0~20100516-1
> Upstream Author : Alexis Sellier
> * URL : https://github.com/cloudhead/vargs
> * License : Expat
> Programming Lang: JavaScript
> Description : function argu
reassign 613618 ngetty
thanks
On Wed, 16 Feb 2011, NIIBE Yutaka wrote:
> I am using ngetty (1.1-2) which doesn't use /etc/inittab
> but invoked by /etc/init.d/ngetty.
I suggest you invoke the master ngetty from init, instead.
> Since ngetty works differently than traditional getty, we don't need
On Wed, 09 Feb 2011, Henrique de Moraes Holschuh wrote:
> Erez, could we impose on you to remove the usplash package (not purge, just
> remove) and check if the problem disappears (please revert your workaround
> first)?
Erez replied over private email that yes, just removing usplash is
On Wed, 09 Feb 2011, Erez Geva wrote:
> Do not have any output since it occurs during boot proccess.
> The /lib/init/usplash-fsck-functions.sh rechechs line 169:
> However the wait have no job to wait for though fail into fake maintainance
> login.
> When finnish the maintainance, and exit a reboo
On Tue, 08 Feb 2011, Christian PERRIER wrote:
> Quoting Henrique de Moraes Holschuh (h...@debian.org):
> > The release nodes neglect to recommend that the user should make sure
> > the firmware packages are installed. In fact, unless we add a list of
> > the hardware t
Package: release-notes
Severity: important
There is at least one report of an user who lost network connectivity
during the upgrade, because the firmware for his NIC (e100) was not
available anymore.
The release nodes neglect to recommend that the user should make sure
the firmware packages are i
On Wed, 02 Feb 2011, Paul Wise wrote:
> * Package name: sleepisdeath
> Version : 16
> Upstream Author : Jason Rohrer
> * URL : http://sleepisdeath.net/
> * License : None (Public Domain)
> Programming Lang: C++
> Description : a storytelling game for two
On Wed, 02 Feb 2011, brian m. carlson wrote:
> Please feel free to test against my server on port 587. Since you are
> obviously not authorized to relay mail through my server, smtptest
> should not claim you are authenticated.
I might try that. But if one of the other maintainers could jump in
On Mon, 31 Jan 2011, brian m. carlson wrote:
> If I use smtptest with the -a and -u options but without -m, it claims
> that I am authenticated when I am not. It does not even try to issue an
> AUTH command. I am certain that bk2...@example.com is not an authorized
> user at the domain I've speci
On Tue, 01 Feb 2011, Lutz Christoph wrote:
> In that time range I upgraded the server, and it retained
> cyrus21-common. (Dunno why it didn't upgrade to 2.2.) And I believe this
> shows a good hint at what happened:
Ah, should be that. An ordering problem re. cyrus21-common.
> cyrus21-common and
On Mon, 31 Jan 2011, Jaromil wrote:
> Programming Lang: C, Shell
> Description : crypto undertaker
>
> Tomb is a free and easy to operate desktop application for fairly
> strong encryption of personal files. A tomb is like a locked folder
> that can be transported and hidden in filesystems
tag 611546 + moreinfo
thanks
On Sun, 30 Jan 2011, Lupe Christoph wrote:
> This message is probably cryptic enough to confuse the average Debian user.
> "Why
> do I need that, and how do I do it?" is the most likely reaction.
Yeah, it is less helpful than it could be as a punishment for the user
On Tue, 25 Jan 2011, Simon Josefsson wrote:
> Henrique de Moraes Holschuh writes:
> > * Package name: iucode-tool
> ...
> > It requires non-free microcode data downloaded directly from Intel or
> > installed by the intel-microcode package in order to be able
Package: wnpp
Severity: wishlist
Owner: Henrique de Moraes Holschuh
* Package name: iucode-tool
Version : 0.5
Upstream Author : Henrique de Moraes Holschuh
* URL : none yet
* License : GPL v2 or later
Programming Lang: C
Description : Intel Processor
Package: git-buildpackage
Version: 0.5.16
Severity: normal
Currently, git-import-dsc will properly set the date on the commits on
the Debian branch (using the changelog). However, for the upstream
tarball, it doesn't do anything.
The result is that you have history with upstream commits in the f
tag 609617 upstream
thanks
> On Mon, 10 Jan 2011 21:20:07 -0200, Henrique de Moraes Holschuh wrote:
> > Package: fglrx-source
> > Version: 1:10-12-1
> > Severity: normal
> >
> > If one wants a kernel without the potential security nightmare that is
> > CON
Package: fglrx-source
Version: 1:10-12-1
Severity: normal
If one wants a kernel without the potential security nightmare that is
CONFIG_IA32_EMULATION, one must do without fglrx, as the driver will not
build without CONFIG_IA32_EMULATION=y.
fglrx needs to detect that it is building with CONFIG_IA
Package: rng-tools
Version: 2-unofficial-mt.13-3
Severity: important
According to a commit in LKML:
It has been reported that on at least one Nano CPU the xstore
instruction will write as many as 1
Package: fglrx-driver
Version: 1:10-9-3
Severity: important
Tags: upstream
glGetTexImage(GL_TEXTURE_2D, 0, GL_RGB, GL_UNSIGNED_BYTE...)
or
glGetTexImage(GL_TEXTURE_2D, 0, GL_RGBA, GL_UNSIGNED_BYTE...)
returns crap. Weirdness ensues (as the game uses the returned data for
colision detection).
On Wed, 15 Dec 2010, Tommy van Leeuwen wrote:
> Is there any workaround available for this bug? We really need to be
> able to interrupt the boot process.
Yes, disable concurrent boot. It is what I have done on all my boxes and
set as policy for all servers at work. Right now, it is more trouble
On Thu, 16 Dec 2010, Andreas Wohlfeld wrote:
> I don't know where I've picked up the missing bits (system was migrated
> from Debian 1.3 over the years), but they are not getting corrected when
> installing new package versions, which caused the problems here.
>
> Maybe they should be checked as c
On Thu, 02 Dec 2010, auto19412...@hushmail.com wrote:
> Is this bug being kept in Debian Stable (lenny) for a particular
> reason?
Nobody got around to backporting the fix to stable. NMU patch welcome.
--
"One disk to rule them all, One disk to find them. One disk to bring
them all and in
Package: release.debian.org
Severity: normal
User: release.debian@packages.debian.org
Usertags: unblock
Please unblock package hdparm
The hdparm version in testing has severe bugs that cause
severe malfunctions on various important options.
Please refer to:
http://bugs.debian.org/cgi-bin/bug
On Fri, 26 Nov 2010, jida...@jidanni.org wrote:
> The Debian Policy Manual should state what the preferred date on manual
> pages should be, or wishes upstream would make it.
There is no need. This is documented in man-pages(7). It is the date the
manpage was last revised.
> Also mention if Deb
On Tue, 23 Nov 2010, Ondřej Surý wrote:
> On Mon, Nov 22, 2010 at 23:00, Henrique de Moraes Holschuh
> wrote:
> > On Sun, 21 Nov 2010, Costin Gusa wrote:
> >> Is it ok to ask here about including uoa.gr autocreate/autosieve
> >> patches or should I file a bug ag
On Sun, 21 Nov 2010, Costin Gusa wrote:
> Is it ok to ask here about including uoa.gr autocreate/autosieve
> patches or should I file a bug against the newly 2.4.4? (I just found
> them prepared for 2.4.4 here:
Unless one of the other Cyrus maintainers overrides me, those will be
added only after
On Sat, 20 Nov 2010, Henrique de Moraes Holschuh wrote:
> On Fri, 19 Nov 2010, Costin Gusa wrote:
> > It's almost a year since last message on this list, squeeze is frozen,
> > cyrus stable is already 2.4.4.
>
> 2.4.4 is in experimental.
Sorry, it is still in NEW. Bu
On Fri, 19 Nov 2010, Costin Gusa wrote:
> It's almost a year since last message on this list, squeeze is frozen,
> cyrus stable is already 2.4.4.
2.4.4 is in experimental.
> Sadly, this makes me wonder not if we will see cyrus-2.3 in
> testing/experimental, but if we EVER will have a modern cyrus
On Mon, 01 Nov 2010, Patrick Matthäi wrote:
> >just one of some more problematic lines is e.g. the dri2 load.
Well, it is not that. Nor any of the other modules. And aticonfig
--initial just outputs the same xorg.conf, but with an empty modules section
(after I removed it entirely). Actually, t
On Sun, 31 Oct 2010, Patrick Matthäi wrote:
> > Oct 31 11:14:36 khazad-dum2 kernel: DMAR:[DMA Write] Request device
> > [03:00.0] fault addr 149598000
> > Oct 31 11:14:36 khazad-dum2 kernel: DMAR:[fault reason 05] PTE Write access
> > is not set
> > Oct 31 11:14:36 khazad-dum2 kernel: DMAR:[DMA
On Fri, 29 Oct 2010, Daniel Baumann wrote:
> please remove the noisy runlevel time measuring. patch will be sent as
> soon as the bug number is assigned.
FWIW, I also think that measurement is not very useful, and it does the
wrong thing too easily, since we are not using something that calls
cloc
On Fri, 29 Oct 2010, Daniel Baumann wrote:
> attached is the patch.
[...]
> + domount cgroup "" /sys/fs/cgroup cgroup -onodev,noexec,nosuid
I like it. Is this mountpoint "blessed" by someone, since it is inside
/sys? Are other distros also using this path?
--
"One disk to rule
On Thu, 28 Oct 2010, Mehdi Dogguy wrote:
> > Idiocy quietly watches for people insecurely visiting twitter on public
> > wifi networks, then hijacks their session to post a tweet warning them
> > about the dangers. It was written in response to the release of
> > Firesheep, which will result in a h
retitle 600433 collectd: rrd: issuing uc_update: Value too old messages
thanks
On Sun, 17 Oct 2010, Florian Forster wrote:
> On Sun, Oct 17, 2010 at 03:32:36AM -0200, Henrique de Moraes Holschuh wrote:
> > collectd does not use UTC.
>
> collectd uses the timestamp returned by
Package: collectd
Version: 4.10.1-1+squeeze1
Severity: important
Tags: upstream
Those who do not learn from the past, are bound to repeat the same
errors forever. collectd does not use UTC. Yet, it expects to be able
to ignore timezone shifts that happen twice an year on a very very large
number
Package: linux-2.6
Version: 2.6.32-25
Severity: important
Please backport commit 61afef614b013ee1b767cdd10325acae1db1f4d2
"dm crypt: add plain64 iv" from upstream. It should be a clean
cherry-pick.
Without it, Debian squeeze users might not be able to use dm-crypt
volumes created on newer kernel
retitle 574897 hdparm: version 9.32 required to fix nasty issues in 9.27+
severity 574897 important
thanks
hdparm-9.32: major bug fixes
hdparm-9.32 is now released. This includes fixes for the bugs introduced in
9.27 (which nobody emailed me about). So now, many flags such as -B and -M
should be
Can I mark this bug "unreproducible" and close it? It seems to be something
quite hard to hit, and probably already fixed on the newer releases.
--
"One disk to rule them all, One disk to find them. One disk to bring
them all and in the darkness grind them. In the Land of Redmond
where the
Package: partman-lvm
Severity: important
Tags: d-i
d-i now creates aligned partitons (at least for msdos disk labels),
using a 1MiB granularity.
Unfortunately, d-i is letting LVM2 use its default metadata size for the
PVs, which is 192KiB. This causes the first usable PE to be
out-of-aligment on
Package: partman-base
Severity: normal
Tags: d-i
Tested with partman in d-i daily build image from 2010-09-07.
When one forces a GPT label, the partitions are apparently created
without any alignment, instead of "optimal" aligment.
I tried using the "guided partitioner", as well as trying to do
On Tue, 07 Sep 2010, Otavio Salvador wrote:
> On Tue, Sep 7, 2010 at 9:50 AM, Henrique de Moraes Holschuh
> wrote:
> > On Tue, 07 Sep 2010, Christian PERRIER wrote:
> >> Dealing with alignment stuff has been introduced in partman-base 140
> >> and enhanced in later v
Package: release.debian.org
Severity: normal
User: release.debian@packages.debian.org
Usertags: freeze-exception
Please unblock package intel-microcode
This package contains a data file with microcode for Intel CPUs. The
update script for users to get that updates for that file has been
brok
On Tue, 07 Sep 2010, Christian PERRIER wrote:
> Dealing with alignment stuff has been introduced in partman-base 140
> and enhanced in later versions.
>
> If you were using a weekly built netinst image (that includes d-i
> alpha1 released in Feb. 2010), you may be using an earlier version.
>
> Ca
Package: debian-installer
Severity: normal
Tags: d-i
The current IBM-PC style partitioner uses the no-good 255 heads, 63
sectors/track default format from 20 years ago, which misaligns
partitions on just about every device (logical or hardware) that has a
reason to care about something other than
On Fri, 03 Sep 2010, Petter Reinholdtsen wrote:
> [Sven Joachim]
> > I think Ctrl-c should just abort the fsck and continue the boot
> > (this happens here with CONCURRENCY=none in /etc/default/rcS, but I
> > don't have any actual filesystem problems and booted with the
> > forcefsck option). Anyw
Package: buildd.debian.org
Severity: normal
The intel-microcode package contains only i386 and amd64 microcode
binary data for Intel CPUs. It is useless on other archs.
-- System Information:
Debian Release: squeeze/sid
APT prefers testing
APT policy: (500, 'testing')
Architecture: amd64 (x8
On Mon, 30 Aug 2010, Tollef Fog Heen wrote:
> I guess I can fix this by making systemd-sysv also conflict sysv-rc and
> include an update-rc.d and invoke-rc.d. In fact, I probably should do
> that.
There is no "probably should" in that. You really *need* to.
--
"One disk to rule them all, On
Package: microcode.ctl
Version: 1.17-13
Severity: normal
This would usually be wishlist, but CPU microcode fixes *need* to be
applied as early as possible (preferably by the BIOS itself).
microcode.ctl should:
1. Provide facilities to upload microcode from the initrd. Since a big
initrd is anno
On Sun, 08 Aug 2010, Michael Hanke wrote:
> On Sun, Aug 08, 2010 at 06:02:43PM +0200, Ralf Treinen wrote:
> > /usr/bin/imtest
> > /usr/share/man/man1/imtest.1.gz
> >
> > This bug is assigned to both packages. If you, the maintainers of
> > the two packages in question, have agreed on which of
On Sat, 07 Aug 2010, Colin Watson wrote:
> On Sat, Aug 07, 2010 at 04:31:22PM +0200, Frans Pop wrote:
> > On Saturday 07 August 2010, Neil McGovern wrote:
> > > As there isn't a resolution in sight, I'll add a hint at the end of
> > > August for the removal of the package unless there's significant
On Sat, 07 Aug 2010, Frans Pop wrote:
> On Saturday 07 August 2010, Neil McGovern wrote:
> > As there isn't a resolution in sight, I'll add a hint at the end of
> > August for the removal of the package unless there's significant
> > progress to fixing the issue.
>
> I still feel this is an overre
On Sat, 07 Aug 2010, Henrique de Moraes Holschuh wrote:
> Can we PLEASE rename this from "rescue" image to "safe mode" image, and
> document in its boot screen that it should NEVER be used in a system with
> filesystem or RAID problems?
Well, my whole reply came out
On Sat, 07 Aug 2010, Neil McGovern wrote:
> Well, it seems that other people haven't taken an interest in the bug,
> and we've now frozen, again.
Yes. And the justifications in the bug report for not fixing the underlying
issues go like this: we should take actions which are guaranteed to destro
The issue is being discussed in LKML, and it appears that _some_ BIOSes
can read data after the 2TB (with 512KiB sectors) limit...
Thread here:
http://lkml.org/lkml/2010/7/24/25
--
"One disk to rule them all, One disk to find them. One disk to bring
them all and in the darkness grind them. I
On Sat, 24 Jul 2010, Mario 'BitKoenig' Holbe wrote:
> On Sat, Jul 24, 2010 at 03:08:29PM +0200, Mario 'BitKoenig' Holbe wrote:
> > On Sat, Jul 24, 2010 at 09:20:09AM -0300, Henrique de Moraes Holschuh wrote:
> > > OTOH, I have nothing against adding
On Sat, 24 Jul 2010, Mario 'BitKoenig' Holbe wrote:
> the rng-tools init-script should depend on the start of the sysfsutils
> init-script:
> Under some circumstances users have to configure which of the available
> Hardware RNGs has to be used as "current" RNG for /dev/hwrng before
> rngd can star
Package: debian-installer
Severity: important
Recording this to the Debian BTS and sending to relevant parties, to
make sure it is not forgotten.
- Forwarded message from Tejun Heo -
Date: Sat, 24 Jul 2010 11:58:42 +0200
From: Tejun Heo
To: Jeff Garzik , Ben Collins, Linux-IDE, LKML
Su
On Mon, 19 Jul 2010, Ralph Ulrich wrote:
> For a user removing a package but not purging, it is totally
> non-intuitive that remaining start scripts may cause some trouble in
> the future. These scripts are seen as NOT-editable und thus
> considered to be NO conffiles.
There is the bug. This is D
On Thu, 08 Jul 2010, Thadeu Lima de Souza Cascardo wrote:
> I've submitted bug 497206 for aptitude with a patch attached almost two
> years ago. It's a new feature, to allow packages to be grouped by
> source. It's usually easier to upgrade all packages from the same
> source, without having to lo
On Thu, 15 Jul 2010, Matthieu PATOU wrote:
> Package: cyrus-imapd-2.3
> Followup-For: Bug #525391
>
> Almost one year since last report, and still no sign of life in sid,
> unstable, not to speak about testing or the future squeeze.
>
> New version of cyrus imap brings new functionnalities that c
On Thu, 15 Jul 2010, Matt Mackall wrote:
> > > Don't bother fiddling with the pool size.
> >
> > We don't, but local admins often do, probably in an attempt to better handle
> > bursts of entropy drainage. So, we do want to properly support non-standard
> > pool sizes in Debian if we can.
>
> Un
On Mon, 05 Jul 2010, Matt Mackall wrote:
> > > Here are our questions:
> > >
> > > 1. How much data of unknown quality can we feed the random pool at boot,
> > >before it causes damage (i.e. what is the threshold where we violate
> > > the
> > >"you are not goint to be any worse than you
(adding Petter Reinholdtsen to CC, stupid MUA...)
On Sat, 03 Jul 2010, Henrique de Moraes Holschuh wrote:
> Hello,
>
> We are trying to enhance the Debian support for /dev/random seeding at early
> boot, and we need some expert help to do it right. Maybe some of you could
&g
Hello,
We are trying to enhance the Debian support for /dev/random seeding at early
boot, and we need some expert help to do it right. Maybe some of you could
give us some enlightenment on a few issues?
Apologies in advance if I got the list of Linux kernel maintainers wrong. I
have also copied
On Fri, 02 Jul 2010, Christoph Berg wrote:
> Re: Henrique de Moraes Holschuh 2010-07-01
> <20100701172936.gf4...@khazad-dum.debian.net>
> > > longer in the archive. Please fix this.
> >
> > Can we just request something from experimental to be removed? Might
On Fri, 02 Jul 2010, Petter Reinholdtsen wrote:
> Looking at the changelog, it was introduced in 2005 to fix #267935. If
> it is not needed any more, lets drop it. I very much welcome help
> with writing a patch for this to get init.d/urandom moved earlier in
> the boot. Can you write a patch bas
On Sat, 03 Jul 2010, Petter Reinholdtsen wrote:
> I gave this another try, and believe this code should work, using only
> ls and the shell builtin set.
>
> # Handle locally increased pool size
> set -- $(LANG=C ls -l "$SAVEDFILE")
> SAVEDSIZE="$5"
>
On Fri, 25 Jun 2010, brian m. carlson wrote:
> The entire cyrus 2.3 suite is uninstallable because libdb4.4 is no
That is dead code. We have something better (2.3.16) getting into shape
for a new experimental upload.
> longer in the archive. Please fix this.
Can we just request something from
On Thu, 01 Jul 2010, Petter Reinholdtsen wrote:
> Perhaps ls round up to the nearest block? Any other ideas on how to
> fix this with the tools available on /?
I'm looking at the kernel code for random.c right now. To me it looks like
we can just drop the test for file size. When (and why) did
On Thu, 01 Jul 2010, Petter Reinholdtsen wrote:
> [Michael Biebl]
> > TBH, I'm not actually sure what all the code in /etc/init.d/urandom
> > is supposed to do and why SAVEDSIZE is necessary at all.
>
> It is to handle those increasing the pool size in the kernel and make
> the change last across
On Wed, 30 Jun 2010, Michael Biebl wrote:
> the latest upload of the initscripts package broke the urandom sysv init
> script.
> It uses find in line 39, which lives in /usr/bin.
Using anything on /usr is a bad idea on that script.
urandom is not something that should start late, it resseds the m
On Thu, 24 Jun 2010, Yann Dirson wrote:
> That sounds good... but then we have a problem with the multiboot patch, which
> does not apply to 4.10, and seems to have broken 4.00.
Probably. BTW, is that the reason why it is only seeing the low 640kB of
memory? :-)
> I guess I should anyway switch t
Package: memtest86+
Version: 4.00-2.3
Severity: normal
While "new upstream" is usually wishlist, memtest86+ 4.0 croaks and goes
belly up in a Xeon X5550 (and probably other 5500 series and Core-i7)
series, so...
*** Enhancements in v4.10 : ***
* New Features
o Added sup
severity 586660 important
retitle 586660 grub-info croaks when only grub-common is installed
reassign 586660 grub-common
thanks
>From the initial bug report:
Preparing to replace memtest86+ 4.00-2.2 (using
.../memtest86+_4.00-2.3_i386.deb) ...
Unpacking replacement memtest86+ ...
/usr/sbin/grub-p
On Fri, 11 Jun 2010, Debian Bug Tracking System wrote:
> Package: sysvinit
> Version: 2.87dsf-10
> Severity: important
> Tags: patch
>
> Suppose a user set HALT=poweroff in /etc/default/halt, and also
> set /etc/init.d/ups-monitor because he has a ups. With the current
> halt script, won't the
701 - 800 of 1722 matches
Mail list logo
