Package: initramfs-tools
Version: 0.41
Severity: minor
Here's what I'm getting in my generated initramfs conf.modules, this is
not good:
ext3
ide_disk
sd_mod
ata_piix
piix
generic
ide_generic
acpid evms evms_bootdebug kernelextras lvm md udev
unix
The bad line in question is the acpid one
I just had to do some testing with 2.6.12 and mkinitrd and root set
to probe, with a /dev/evms/root as my actual root and everything still
worked for me with evms 2.5.3-7.
What version of the kernel?
What version of initrd-tools?
Repeat:
I did NOT test ROOT=/dev/evms/root in mkinitrd, just probe
Package: initramfs-tools
Version: 0.38
Severity: important
Tags: patch
336617 was closed out without using the additional patches I submitted.
I'm having problems re-opening the bug, so I'm just submitting a new one.
The following two patches need to be applied to evms 0.38 in order to allow
boot
hurrah for opening an separate bug.
Sesse is using plain EVMS root, you seem to use an heavier mix.
Yes, as I mentioned, I use just about every little bit of EVMS on the
way up. My root is a LVM2 volume inside a LVM2 container inside a RAID5
md array, all controlled by evms.
your patch als
Package: drupal
Version: 4.5.5-2
Followup-For: Bug #307821
I just looked at drupal's diffs and we barely touch the drupal source code
at all. Other than changing conf.php to sites/default/settings.php, what
do you believe needs to be done before we can upgrade to drupal 4.6?
It's been six months
Package: initramfs-tools
Version: 0.37
Followup-For: Bug #336617
Kernel 2.6.14, evms 2.3.3-6
root filesystem is on a lvm2 volume inside a md based raid, all held together
with evms.
Standard EVMS installs do not use the userspace md and lvm tools, but do
require their kernel modules, so it is no
Package: linux-image-2.6.14-1-686-smp
Version: 2.6.14-1
Followup-For: Bug #333522
udev/unstable uptodate 0.071-1
Just to cover the blanks, it is occuring as well with stock 2.6.14
debian kernels. This is a straight kernel built with an up to date
initramfs tools. initramfs-tools rebuilt the ini
Package: udev
Version: 0.071-1
Severity: minor
Tags: sid
For hotplug and discover1, there were well documented ways of blacklisting
certain modules or devices. We could really use a bit of documentation on
this with the new udev now that it has replaced hotplug and discover.
There was no obvious
Package: linux-image-2.6.14-1-686-smp
Version: 2.6.14-2
Followup-For: Bug #333522
Well, I can pretty consistently reproduce this bug, and an interesting
datapoint is that even a manual modprobe after startup causes further
Unknown symbol problems.
I do not know if this is because udev/m-i-t/linux
Please ignore/delete the comments about snd_intel8x0, that is a totally
unrelated bug. I tried Rusty's proposed fix for modprobe.c (in bug
333052) and it solves the problem reported in 522 and 333052 for
me (running on a stock linux-image-2.6.14-2 with initramfs made by
initramfs-tools).
--
I tried Rusty's suggested patch to modprobe.c (moving the lock forward).
Works like a charm with stock 2.6.14-2 with an initramfs based upon
initramfs-tools.
Please ignore my comments about manual modprobes and the intel sound stuff
screwing up with unknown symbols, I realized that that is a DIFFE
Thats what I initially thought as well, all I can say is that it the
error messages related to it have gone away for me. Of course, the
errors I could be seeing could also have been due to the second run once
the real root was up.
Paul
--
To UNSUBSCRIBE, email to [EMAIL PROTECTED]
with a su
Package: initramfs-tools
Version: 0.38
Severity: important
Tags: patch
udev 0.74 moved some files around, initramfs-tools needs to adapt to the
new version. (also, udev should have marked itself incompatible with
current versions of initramfs-tools until you apply my changes, but that
is their bu
Package: udev
Version: 0.074-2
Severity: important
Versions of udev as of 0.072-2 and beyond (since you moved things back to
/lib/udev) break initramfs-tools currently in unstable.
I've submitted a fix to the maintainers of initramfs-tools, but for now,
you should really conflict with initramfs-t
conflict with initramfs-tools until bug 339568 has been fixed
--
To UNSUBSCRIBE, email to [EMAIL PROTECTED]
with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
Package: initramfs-tools
Version: 0.38
Followup-For: Bug #339568
--- mkinitramfs 2005-10-24 01:05:05.0 -0700
+++ mkinitramfs 2005-11-20 09:49:08.881214220 -0800
@@ -167,13 +167,16 @@
cp -p "/etc/mkinitramfs/scripts/${f}" "${DESTDIR}/scripts/$(dirname "${f}")"
done
cp "${CONFDIR}/initra
Package: udev
Version: 0.074-3
Severity: important
Tags: patch
The 0.74-3 release, which was supposed to fix the earlier bugs I reported
with udev still doesn't get it right. In udev 0.72-2, they renamed
/lib/hotplug to /lib/udev. It is supposed to be copied over, not ignored.
Please copy over
Package: initramfs-tools
Version: 0.39
Severity: normal
per our discussion via e-mail, please remove all support for evms from
initramfs-tools, I'm working with the evms maintainer to release a new
version of evms which will install the required scripts and hooks, per
your request.
The current fi
Package: initramfs-tools
Version: 0.39
Followup-For: Bug #340257
The following patch:
1) copies /lib/udev to the initramfs image
2) moves all of the udev specific stuff out of the generic
mkinitramfs script and into hooks/udev, which is where
I suspect you rea
Package: evms
Version: 2.5.3-7
Severity: normal
Tags: patch
The maintainer of initramfs-tools has requested that the evms package
take over ownership of the evms-specific hooks in initramfs-tools. He
has refused to fix evms specific problems reported to him in the current
package in favor of forc
the corresponding bug report for initramfs-tools is 340258 where I
formally request that Mats rip the broken scripts out of initramfs-tools
--
To UNSUBSCRIBE, email to [EMAIL PROTECTED]
with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
Package: evms
Version: 2.5.3-7
Severity: minor
Tags: patch
I was looking at the differences between ubuntu 2.5.3-7 and debian.
I noticed the following, just thought I'd pass it along. I've made one
slight change to the patch, to make lsb-base depend on 3.0-11 instead of
1.3-9ubuntu2. I'm not exac
--- evms-2.5.3/debian/rules 2005-11-22 00:08:43.161330725 -0800
+++ ubuntu/evms-2.5.3/debian/rules 2005-11-22 09:09:31.421910370 -0800
@@ -61,6 +61,7 @@
rm -rf ui/cli-noreadline
rm -rf debian/kpatches
rm -f debian/empty.patch
+ rm -f po/*.gmo
dh_clean
Package: postfix
Version: 2.2.2-1
Followup-For: Bug #304920
The problem is that patches/10tls.dpatch is not being executed.
the permissions on this file are 644 instead of 755, which is
probably why dpatch is not running. In other words, you didn't
actually fix the problem in 2.2.2-1 and bug 3014
Package: postfix
Version: 2.2.2-1
Followup-For: Bug #304920
There's no second bug, my eyes were lying, sorry. The only bug is that
the patch isn't getting executed.
-- System Information:
Debian Release: 3.1
APT prefers testing
APT policy: (650, 'testing'), (600, 'unstable')
Architecture: i
Package: amavisd-new
Version: 20030616p10-5
Severity: important
Hi, if you're trying to use amavisd-new with postfix as a smtp proxy
filter, and postfix is configured to announce SMTP auth, amavisd breaks
things badly.
Relevant bits:
smtpd_proxy_filter=127.0.0.1:10024 (pointing at a
Package: amavisd-new
Version: 1:2.2.1-1
Severity: minor
Tags: experimental
I just upgraded from testing to experimental.
Looks like postinst should check to see if the amavis user and group
already exist and are set up properly (right uid/gid/home/etc) and if so,
don't mess with them.
Output:
C
Package: amavisd-new
Version: 1:2.2.1-1
Severity: critical
Tags: experimental
Justification: causes serious data loss
Tagging critical per-debian policy, e-mail dropped.
The experimental version of amavisd-new uses a new config schema, but it
looks like it's not completely implemented yet, since
OK, I thought I had understood things with the new version, but I missed
the -c flag in init.d/ ... honest, I did look for it...
So, the problem is that the default config of amavisd-new appears to be
blocking messages. The /etc/amavisd.conf file isn't looked at or used,
as you intended. Sorry
Critical issue #1 was caused by the wrong config file (the new
autogenerated) config file being read instead of the expected one.
The other issues I will bring up on the mailing list on alioth.
I think I have happy solutions to them.
Paul
--
To UNSUBSCRIBE, email to [EMAIL PROTECTED]
with a subje
Package: clamav-milter
Version: 0.81-2
Severity: important
I'm submitting this as important, as I think sendmail is bypassing
clamav-milter, but I can't be certain, feel free to downgrade as
appropriate.
I've been tracking testing for clamav, after upgrading today, I am
now getting the followin
That was the first thing I checked too, sorry for not including it.
The directory and milter socket appear to be good:
[EMAIL PROTECTED] ls -ld /var/run/clamav
drwxr-xr-x 2 clamav clamav 224 Feb 3 15:50 /var/run/clamav
[EMAIL PROTECTED] ls -l /var/run/clamav/clamav-milter.ctl
srwx-- 1 cla
Package: cyrus21-imapd
Version: cyrus21-imap
Followup-For: Bug #226720
Henrique,
What's the status here? The project on alioth exists but there is nothing
in the repository. Are you going to package Cyrus 2.2 for us, or not?
Much thanks for your work. If you're not able to complete the job, f
Package: spamassassin
Version: 3.0.2-1
Severity: minor
Tags: patch
Spamassassin is supposed to automagically find dcc and execute it if
present. It does so, but uses the dccproc program instead of the
dccifd socket.
Sorry this isn't in patch format.
dcc_home needs to be initialized, or you can
Package: udev
Version: 0.054-3
Severity: minor
In order to satisfy bug report 294968, /dev/.static/dev is a root owned
700 directory. However, this causes df to barf with a permission error
for this device when a non-root user tries to execute it. This is
cosmetic, but still annoying as all hel
Package: ipopd
Version: 7:2002edebian1-6.1
Severity: important
Subject: ipopd fix for 295306 doesn't update inetd properly on upgrade
Package: ipopd
Version: 7:2002edebian1-6.1
Severity: important
The service name may not include a whitespace character!
dpkg: error processing ipopd (--configure)
Package: spamass-milter
Version: 0.3.0-1.1
Severity: minor
The patches present in the debian/patches subdirectory are not being
applied (even the ones that aren't disabled). In reality, this is
probably a good thing, since they don't apply, but this was tripping
me up when I was trying to add my
Package: spamass-milter
Version: 0.3.0-1
Severity: minor
Tags: patch
Since loading spamass-milter, local users have complained that sending
mail takes too long (spamass-milter is checking all their e-mail).
The -i flag doesn't cut it, as we have road-warriors.
This patch adds a new -I flag, whic
I've looked over the code some more and traced things through. I remove
my earlier caution about a potential memory leak caused by my patch.
Everything appears to be cleaned up properly, this should be safe
to apply. Sorry about the excess chatter.
I did make one slight change in this rev of the
Package: evms
Version: 2.5.2-1
Followup-For: Bug #291989
Version 2.5.2-1 of kernel-patch-evms, the dm-bbr patch, of course,
doesn't apply to either 2.6.11.5 or 2.6.11.7 packages in current.
Looks like the kernel pulled in some of the UDM patches, but not all of
them.
Matt,
I noticed that you ex
Package: kernel-source-2.6.11
Severity: wishlist
Tags: patch
In kernel 2.6, a patch was added to the system to allow a block device
driver to claim an entire device as its own. That well meaning change
has been a bane to everyone trying to migrate from hard partition support
to using the device m
Package: evms
Version: 2.5.3-3
Severity: normal
Tags: patch
There are two official patches from sourceforge that our EVMS should be
updated with.
1) http://evms.sourceforge.net/patches/2.5.3/engine/md_expand.patch
Fixes a segfault when md volume is cloned (e.g. a raid 5 expand)
2) http:
Package: linux-source-2.6.12
Version: 2.6.12-10
Followup-For: Bug #328513
Please turn on *BOTH*:
CONFIG_VIDEO_CX88=m
CONFIG_VIDEO_CX88_DVB=m
in the default kernel. Both modules build and work properly. I'm now
running MythTV on debian with untouched kernel sources. :-)
-- System Information:
Much thanks!
--
To UNSUBSCRIBE, email to [EMAIL PROTECTED]
with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
Package: linux-image-2.6.12-1-686-smp
Version: 2.6.12-6
Severity: normal
All the V4L drivers are built in the default kernel config, except for
the CX88. I suspect this is either because CX88 support is quite new,
or because there were bugs and conflicts in the CX88 code earlier.
In 2.6.12, the
Package: evms
Version: 2.5.2-1
Severity: important
Tags: patch
This also affects the latest evms-2.5.3-2 packages.
When I hacked up evms.mkinitrd.probe, debian kernels were configured with
modules=most which included underlying drivers for loading root from evms.
Since 2.6.12, those modules are
The author is correct that the line is missing, but the problem is that
the line was moved to mod_dir.conf, which is a NEW file in 2.2, but
wasn't symlinked into mods-enabled.
We're doing upgrading incorrectly in general. I'm wondering if the
"proper" way to do it is to look at the existing a
You closed the wrong bug.
On Feb 23, 2007, at 4:33 PM, Debian Bug Tracking System wrote:
This is an automatic notification regarding your Bug report
#304507: kernel-source-2.6.11: please apply the evms bd-claim patch
to debian kernel sources,
which was filed against the linux-2.6 package.
I
Package: cyrus-imapd-2.2
Version: 2.2.13-6
Severity: normal
I've got more fixes for the logcheck database. My patches though are against
testing, but they include the fixes for sieve redirects and Deliver et al.
They also fix several other logcheck problems including a problem I reported
in janua
Package: p0f
Version: 2.0.5-1
Severity: normal
Version 2.0.8 is now out (updating the report on 2.0.7). The newer
versions add a -0 option for wildcard queries to the cache. I'm in
the process of updating amavisd-new and postfix to use p0f and we need
that functionality.
It looks like there's n
Package: amavisd-new
Version: 1:2.4.2-1
Severity: wishlist
Please forward upstream as you see appropriate.
p0f has the ability to run as a daemon and support queries via a unix
named pipe interface into the cache. Before p0f 2.0.7, this interface
wasn't useful to amavis because queries required
Package: amavisd-new
Version: 1:2.4.2-1
Severity: normal
The p0f fingerprinting code in amavis currently writes its headers when
passing information down to SpamAssassin, but doesn't write the headers
into the actual message stream, so we don't record OS types for posterity
later (or for the quara
Package: amavisd-new
Version: 1:2.4.2-1
Followup-For: Bug #364327
Rather than fix p0f-analyzer to do inline configuration, let's just
get rid of it and query p0f's cache directly. p0f 2.0.7 and later
do a fine and dandy job and the code in amavis can be greatly simplified.
cf. debian problem rep
Package: xtables-addons-common
Version: 1.37-1
Severity: important
The debian xtables package does not include the code present in the source
package that downloads the geoip database and correctly builds it into
country specific code.
While the "download" script is redundant with the geoip-data
Package: logcheck
Version: 1.3.18
Severity: important
Tags: security
[Note: I've tagged this with security because of the DoS potential,
where admins relying on logcheck can have their logs "lost" if someone
generates a long log message. Your choice whether you think it's
legitimate or not, but I
Package: logcheck-database
Version: 1.2.57
Severity: normal
Tags: patch
Logcheck is now reporting lines like this:
Jul 31 10:20:59 protempore amavis[6399]: (06399-02) Passed CLEAN,
[64.147.162.140] [64.147.162.138] <[EMAIL PROTECTED]> -> <[EMAIL PROTECTED]>,
Message-ID: <[EMAIL PROTECTED]>, mai
Package: clamav-freshclam
Version: 0.88.2-1
Followup-For: Bug #370512
clamav-freshclam is using the lsb function "pidofproc" which has a bug in
it causing the init.d/clamav-freshclam script to hang waiting on stdin.
I would suggest unmerging this bug and remerging with 370155. This has
nothing t
Unfortunately, the new dependency based stuff (depricating sysv-rc)
breaks amavis.
Yes, amavis can depend upon a lot of stuff needing to start, so it
SHOULD start after those things, if they exist and are installed.
The LSB stuff in /etc/init.d/amavisd-new should be tweaked or auto-
generate
So upon doing some more research and work, and testing on MY system,
this is, I believe, the correct answer for most installations, and
should not cause any problems for any installations:
### BEGIN INIT INFO
# Provides: amavisd-new
# Required-Start:$syslog $network $local_fs $ne
I did look at the docs before sending in the fragment. In no place
in the LSB documentation does remote_fs imply that local_fs has
already happened, so technically, having both is a good thing. Many
scripts have both. /usr can technically be remote_fs. I was trying
to change as little
It's perfectly reasonable to put ALL of them under the should section
if amavis needs them running first.
On Oct 4, 2009, at 3:28 AM, Alexander Wirt wrote:
Paul Traina schrieb am Freitag, den 02. Oktober 2009:
So upon doing some more research and work, and testing on MY system,
this
Package: python2.3-glade2
Version: 2.8.2-3
Followup-For: Bug #352639
since python2.3-gtk2 at 2.8.3-3 exists and is installable, shouldn't this
just need to be rebuilt/linked against that, and the control file fixed?
-- System Information:
Debian Release: testing/unstable
APT prefers testing
Package: evms
Version: 2.5.4-6
Severity: normal
Tags: patch
Hi, sorry, but your fix for the earlier bug I reported is pretty hosed.
Here are my files, in their entirety, please just use them exactly as-is,
if you feel the need to change them, please contact me and discuss it first,
as I have a goo
Justin Pryzby wrote:
Do you know if there is something wrong with the control file? What
it is even? :)
Did the .debs just get reuploaded, without rebuilding?!
Justin
It's bizzare, the control file uses the same version macro everywhere,
but for the gtk reference, it used the old version.
Package: initramfs-tools
Version: 0.51
Severity: minor
Incorrect English usage...
was been altered. Cannot update.
Should be
has been altered. Cannot update.
-- System Information:
Debian Release: testing/unstable
APT prefers testing
APT policy: (650, 'testing'), (600, 'unstable'), (1
Package: dspam
Version: 3.6.2-2
Severity: normal
Tags: experimental
Initial install of dspam & webfrontend at the same time:
Selecting previously deselected package libdspam7-drv-db4.
(Reading database ... 48924 files and directories currently installed.)
Unpacking libdspam7-drv-db4 (from .../li
Package: evms-bootdebug
Version: 2.5.4-4
Severity: normal
the initramfs-tools/hooks/evms-bootdebug script isn't being built/installed
looking at /var/lib/dpkg/info/evms-bootdebug.list:
/.
/usr
/usr/share
/usr/share/doc
/usr/share/doc/evms-bootdebug
/usr/share/doc/evms-bootdebug/README.Debian
/us
Package: evms
Version: 2.5.4-4
Severity: normal
Tags:
Can't boot my system with the new evms. Turns out the initramfs
is missing all the evms binaries.
/usr/share/initramfs-tools/hooks/evms
/usr/share/initramfs-tools/scripts/local-top/evms
need to be installed with the executable bit set (well
Package: evms
Version: 2.5.4-4
Severity: minor
Tags: patch
On executing mkinitramfs, we get the following warning:
W:copy_exec: Not copying /lib/evms/2.5.4/bbr_seg-1.1.12.so to
$DESTDIR/lib/evms/2.5.4/bbr_seg-1.1.12.so, which is already a copy of
/lib/evms/2.5.4/bbr-1.1.14.so
additionaly bbr-1
--- rules 2006-01-25 15:21:49.887915945 -0800
+++ rules 2006-01-25 15:22:27.427655231 -0800
@@ -107,10 +107,10 @@
install -m 644 debian/evms.devfs
$(CURDIR)/debian/evms/etc/devfs/conf.d/evms
install -m 644 debian/evms.mkinitrd.probe
$(CURDIR)/debian/evms/usr/share/in
Package: evms
Version: 2.5.4-4
Severity: normal
EVMS Command Line Interpreter Version 2.5.4
Engine: Error loading /lib/evms/2.5.4/ha-1.1.0.so: libhbclient.so.0: cannot
open shared object file: No such file or directory
I believe that /lib/evms/2.5.4/ha-1.1.0.so should be part of the
evms-ha pa
Package: cyrus-common-2.2
Version: 2.2.12-2
Severity: normal
Tags: experimental
/etc/logcheck/ignore.d.server/cyrus2.2
it appears as if logcheck doesn't like files with a "." in the
filename? I suggest reverting to just "cyrus22" without the dot,
rather than having to fix
Package: logcheck
Version: 1.2.42
Severity: normal
Cyrus 2.2 in experimental installs its logcheck file as:
/etc/logcheck/ignore.d.server/cyrus2.2
That file is ignored...
[EMAIL PROTECTED] su -s /bin/bash -c "/usr/sbin/logcheck -o -t" logcheck
System Events
=-=-=-=-=-=-=
Jan 27 23:02:05
3) The files should be installed with mode 640, owner root, group logcheck
4) The contents of violations.ignore.d/cyrus22 is currently a dupe of
what is installed in the ignore.d.server directory, that is incorrect.
Please install the attached file as violations.ignore.d/logcheck-cyrus22
5
Package: postgrey
Version: 1.23-2
Severity: normal
postgrey is installing the logcheck "violations.ignore.d" file as
/etc/logcheck/violations.ignore.d/postgrey
about a year or so ago, the logcheck maintainers extended the behavior
of the way logcheck violations are processed and a (desir
I agree, I'm no logcheck expert, but if it behaves according to the
manpage, it doesn't take into account the way logcheck handles violations
and their corresponding ignores anymore.
As I think I understand it (feel free to correct me), if a package wants
to register security violation regexps, th
Package: amavisd-new
Version: 1:2.3.3-4
Followup-For: Bug #295498
1) The documentation in the README.Debian says to use the bayes_auto_expire
configuration parameter, but it doesn't say to turn it OFF. It sounds like
you want it turned on. I would suggest explicitly saying:
Add the fol
I take it back, sorry, #2 is bogus, I found /etc/cron.daily/amavisd-new.
I don't know why you have cron jobs for amavis split up between the two
files, but I was wrong.
Here's some suggested text for README.Debian
--- README.Debian 2006-02-01 11:25:44.091776702 -0800
+++ README.Debian
The following is a link to the one line source patch to this problem.
Please expidite a fix, as hanging a reboot for 90 seconds is bad.
https://src.fedoraproject.org/rpms/pcmanfm/blob/4b1c3e3004e996ea3192f1725d3b8a916c7c3ab5/f/pcmanfm-0201-main-set-the-GIOChannel-encoding-to-binary.patch
79 matches
Mail list logo
