On 13-May-12 21:25, Moritz Mühlenhoff wrote:
On Sun, May 13, 2012 at 06:04:03PM +0100, Steve McIntyre wrote:
On Tue, Mar 08, 2011 at 10:37:13PM +0100, Moritz Muehlenhoff wrote:
Looking at other bugs and security tracker issues in serendipity, I'd
be tempted to remove it from Debian anyway...
Package: samba
Version: 2:3.2.5-4lenny14
Severity: important
Here's the output of aptitude safe-upgrade
Reading package lists... Done
Building dependency tree
Reading state information... Done
Reading extended state information
Initializing package states... Done
Reading task descriptions...
retitle 597373 failed upgrade from 3.0.2 leaves package in inconsistent
state
thanks
Do you happen to have the messages from the failed upgrade?
I believe you should submit that as another bug.
Now (one of?) the repercussions of that seems to be that the new
release's prerm script is kept even
tags 595594 +pending
thanks
Ok,
our own database functions now exit even more gracefully on failure.
The previous fix (586759) seemed to address a similar issue but only
when dbconfig itself was failing, not the DB behind.
Greets,
JM
For reference, here's the link to the full discussion about
Package: serendipity
Version: 1.5.3-1
Severity: normal
Tags: security patch
http://blog.s9y.org/archives/223-Serendipity-1.5.4-released.html
http://www.htbridge.ch/advisory/xss_vulnerability_in_serendipity.html
--
To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org
with a
On 30-Aug-10 18:51, Olaf van der Spek wrote:
If you want, that your new build gets uploaded to Debian by a sponsor, you
have to build and check your package+changes+diff and after that upload the
whole to any space with the .dsc etc.
A sponsor should not be necessary, as Lighttpd has three
Technically, the failure is trigged by the set -e of the maintainer
script, since dbc_go fails.
This is by no means a failure of the phpbb3 package, only a
consequence of the failure of dbconfig-common.
As far as debconf is concerned, people use db_go || true -- I have
seen no such call for
On 6/7/2010 12:57 AM, Luigi Gangitano wrote:
Hi J.M.,
unlike the 'all' directory which holds a repository of global configuration,
the 'default' directory is not a special one for drupal (once you've
correctly configured all the virtual hosts) and can be safely removed.
This should fix
retitle 583197 maintainer script does not correctly handle remote DB
severity 583197 important
tags 583197 +pending
thanks
Hi,
thanks for trying out the new release.
I have now fixed that problem in SVN.
To make it work right now, you can go to
/var/lib/dpkg/info/phpbb3.config and remove the
ping
--
To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org
with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Hmm, I have no problem with this...
Server: smokeping 2.3.6-3 @ Debian/Lenny
Client: FF3.6.3 (Win32)
Anyway, since this isn't security-related, I guess a fix for Lenny (if
still reqd) will not be possible.
JM
--
To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org
with a
On 5/20/2010 8:06 PM, Richard Atterer wrote:
[ -x /usr/share/drupal6/scripts/cron.sh ]
/usr/share/drupal6/scripts/cron.sh
if test -x /usr/share/drupal6/scripts/cron.sh; then
/usr/share/drupal6/scripts/cron.sh; fi
To me, these two lines look like they do exactly the same thing.
Can
Alright I'm convinced.
$ [ -x bla ] echo bla
$ echo $?
1
$ if test -x bla; then echo bla; fi
$ echo $?
0
Never mind ^^
--
To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org
with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Package: cakephp
Severity: wishlist
Just wanted to draw your attention to the fact that not only the 1.2.x
series has been updated, but that 1.3.0 stable is out.
Thx
JM
--
To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org
with a subject of unsubscribe. Trouble? Contact
reopen 541740
tags 541740 - fixed
thanks
Actually, this is not yet fixed.
We had made all the preparations in SVN and the new packages are on
their way. The changelog was already updated, that is why this bug was
closed by the upload, which did not yet contain the links to the
(still unavailable)
Package: debian-policy
Version: 3.8.4.0
Severity: wishlist
I was always wondering (concerning 5.6.2/5.6.3):
1) The Maintainer field can contain only ONE contributor, whereas
there may be several to the package.
2) The Uploaders field can contain several people, whereas -
technically - there can
The next version will again feature a special l10n package.
For now, you can just install the language pack you like by extracting
it manually to /usr/share/phpbb3/www/language/, if necessary.
Cheers
JM
--
To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org
with a subject of
Package: serendipity
Severity: wishlist
Owner: jmr...@iip.lu
Investigate multi-blog from single install setup à la
http://www.s9y.org/41.html
--
To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org
with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Package: dbconfig-common
Version: 1.8.46
Severity: important
When dbconfig-common is purged and reinstalled, it is no longer
working. Instead, one gets:
dbconfig-common not yet setup, deferring configuration.
I have reproduced this in a chroot environment:
debootstrap squeeze
mount
This ITP already exists. ;)
http://bugs.debian.org/574964
--
To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org
with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Package: dbconfig-common
Version: 1.8.39
Severity: wishlist
Hi there,
in order not to be forgotten I'm creating this report in BTS.
I copy the description of the feature we are talking about from
http://lists.alioth.debian.org/pipermail/dbconfig-common-devel/2010-March/thread.html
-- a
Package: postgrey
Version: 1.31-3.2
Severity: normal
When I do:
# postgreyreport /var/log/mail.log
#
The result is nothing, as you see.
Here are a few lines from my maillog:
Apr 6 21:51:42 abc postgrey[5171]: action=pass, reason=client AWL,
client_name=xxx, client_address=xxx, sender=xxx,
Package: websvn
Version: 2.3.0-1
Severity: normal
Tags: fixed-upstream
In case 2.3.1 will not make it into testing please consider patching the
following issue
http://websvn.tigris.org/issues/show_bug.cgi?id=284
I'm not sure if the patch attached there is the actual patch though.
I have
Why is the pending tag set?
Is there a fix somewhere? :-)
--
To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org
with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Did you also reinstall the database, i.e. remove db and user and
populate the db again from scratch?
On 3/25/2010 8:41 AM, Ednardo Lobo wrote:
After reinstall everything seems ok. :-)
--
To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org
with a subject of unsubscribe.
Can you send a dump of your current DB with which it is not working?
--
To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org
with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
tags 574648 +unreproducible
thanks
I cannot reproduce that on a plain Lenny (or Squeeze) install.
Can you provide a link to the phpinfo() screen?
Have you made any special settings in PHP?
Can you purge everything and reinstall the package and see if there
are errors during installation?
--
Package: wnpp
Severity: wishlist
Checks if a given Host or URL is listed on an DNS-based Blackhole
List (DNSBL, Real-time Blackhole List or RBL) or Spam URI Realtime
Blocklist (SURBL)
This package is required to fully debianize serendipity.
Having this package available would close #541740.
Package: wnpp
Severity: wishlist
This is the base engine for all of the Text_Wiki sub-classes.
The text transformation is done in 2 steps.
The chosen parser uses markup rules to tokenize the tags and content.
Renderers output the tokens and text into the requested format.
The tokenized form
Original Message
Date: Mon, 22 Mar 2010 15:28:32 +0100
From: J.M.Roth jmr...@iip.lu
To: 442...@bugs.debian.org, cont...@bugs.debian.org
owner 442351 !
thanks
Nothing is happening here, so I am taking over.
This package is required to fully debianize serendipity.
Having
owner 442351 !
thanks
Nothing is happening here, so I am taking over.
This package is required to fully debianize serendipity.
Having this package available would help to close #541740.
License: PHP License 3.01 (Is that a problem?)
URL: http://pear.php.net/package/XML_RPC
--
To
Package: wnpp
Severity: wishlist
Free, open source php parser that minimizes bandwidth usage.
Great programming and wonderfully documented!
Uses object oriented programming and PHP's built in XML extension to quickly
and accurately parse ALL versions of RSS including 2.0.
Many other parsers
On 3/22/2010 5:09 PM, Elizabeth Krumbach wrote:
I was able to get the source that Yann was working on and am now
working on it in the php team's svn repo:
http://svn.debian.org/wsvn/pkg-php/pear/php-xml-rpc/#_pear_php-xml-rpc_
We could use help with testing
Looks ok to me.
BTW 1.5.3 is
I'd love to be of assistance here.
Just a note: the link to VCS (browse/wsvn) in PTS is invalid.
(https://aphrodite.kinkhorst.nl/wsvn/debian/serendipity/)
I'll start to familiarize myself with the packaging of the app.
Regards,
JM
--
To UNSUBSCRIBE, email to
I do not see any Administration Control Panel link in your forum.
Did you remove it?
--
To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org
with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Package: phpbb3
Version: 3.0.2-4
Severity: wishlist
Owner: da...@tilapin.org
The question was raised whether other webservers (than apache2) should
be supported. Just wanted to put that in the queue. I believe David
volunteered ;-)
--
To UNSUBSCRIBE, email to
Package: dbconfig-common
Version: 1.8.45
Severity: wishlist
Tags: patch
Sometimes, I feel more flexibility is needed concerning:
- the order of execution of scripts/data
- the order of execution of elements therein
I.e. for now it is hardcoded that scripts are run first and then data
snippets
On 3/13/2010 11:05 AM, Joachim Wiedorn wrote:
Hello,
J.M.Roth jmroth+deb...@iip.lu wrote:
Let me just reiterate the hint from #573603 that a new upstream
version is available. ;)
I am already working on the update.
Relax, for now it was no problem for me to install/update this single
Package: duply
Version: 1.5.1.5-1
Severity: wishlist
I was wondering if you could loosen the dependency on duplicity (= 0.5.06) a
little.
I am using duply 1.5.1.4 on lenny (i.e. duplicity 0.4.11) and it works just
fine.
Like that I could at least have one less manually installed app on my box.
PM, Joachim Wiedorn wrote:
Hello,
J.M.Roth jmroth+deb...@iip.lu wrote:
I was wondering if you could loosen the dependency on duplicity (= 0.5.06)
a little.
I am using duply 1.5.1.4 on lenny (i.e. duplicity 0.4.11) and it works just
fine.
Like that I could at least have one less manually
Package: duply
Version: 1.5.1.5-1
Severity: minor
Let me just reiterate the hint from #573603 that a new upstream version is
available. ;)
Oh and by the way, your watch file is broken:
-http://sf.net/duply/duply_(.*)\.tgz
+https://sourceforge.net/projects/ftplicity/duply_(.*)\.tgz
JM
--
Package: devscripts
Version: 2.10.35lenny7
Severity: minor
The man page says:
# The filename is found by taking the last component of the URL and
# removing everything after any '?'. If this would not make a usable
# filename, use filenamemangle. For example,
# A
#affects 573069 + 573051
block 573051 by 573069
thanks
Here's the other bug report I was talking about.
http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=573069
removal of postgres database and user not working
So I guess at least purging the package with postgres will not work for now.
--
To
Package: phpbb3
Version: 3.0.2-4
Severity: important
After a myriad of warnings and hints the database import fails with
ERROR: START value (1) cannot be less than MINVALUE (100)
-- System Information:
Debian Release: 5.0.4
APT prefers stable
APT policy: (500, 'stable')
Architecture: i386
Package: dbconfig-common
Version: 1.8.45
Severity: important
Tags: patch
dbconfig-common, when in pgsql mode, does not correctly drop databases and users
because it uses command line parameter -q to dropdb and dropuser, respectively,
which does not exist. in fact, such an action always results in
I have narrowed this down to
ALTER SEQUENCE phpbb_users_seq MINVALUE 100 RESTART WITH 100;
in the postgres schema.
This was added in SVN r441, see also #497721.
There are also other problems using pgsql that I am investigating - if
necessary I'll explain this in another bug report.
--
To
Yep, it's clear that everything after r8679 (which is 3.0.2) is probably
not in the Debian package.
Since this fix is in r9728/9 = 3.0.6 this bug and #524361 probably
belong together.
BTW I asked if manpower was needed for this package in #570660, but
there is no answer (yet?).
On 2/28/2010
.
But maybe that can change.
Now you know who I am.
Best regards,
J.M.Roth
--
To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org
with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Package: drush
Version: 2.0-6~bpo50+1
Severity: wishlist
Tags: patch
Drush should have a (Debian) default config that does not make it necessary to
give the path to the drupal installation using -r each time.
On Debian this would be /usr/share/drupal6/. Anyone who wants to override that
could
Package: phpbb3
Version: 3.0.2-4
Severity: important
Tags: security patch
I had only recently upgraded to phpbb3 when spambots started arriving.
The (default) captcha is very weak.
The GD captcha crack celebrates its first anniversary these days.
In the supplied database scheme, the
Package: phpbb3
Version: 3.0.2-4
Severity: minor
Tags: patch
/usr/share/phpbb3/styles/README = /usr/share/doc/phpbb3/README.templates is
outdated and should not be linked in /etc/phpbb3/styles because it is not a
style.
First, I believe /etc/phpbb3/styles/README should be removed:
There is
retitle 514864 ucf/debconf warning message on install/dist-upgrade
thanks
I also got this while installing a fresh copy of phpbb3.
--
To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org
with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Archive:
Please note that message 45 comes *before* message 40 for all of this to
make sense. :-\
--
To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org
with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
On 2/9/2010 8:45 AM, Ola Lundqvist wrote:
On Mon, Feb 08, 2010 at 11:24:52PM +0100, J.M.Roth wrote:
On 2/8/2010 11:13 PM, Ola Lundqvist wrote:
drwxr-xr-x 2 ntop root 4096 2010-01-27 11:18 .
drwxr-xr-x 12 root root 4096 2010-01-27 11:17 ..
-rw-rw-rw- 1 root root0 2010-01-27 11:18
On 2/9/2010 9:13 PM, Ola Lundqvist wrote:
When setting the correct permissions (u=rx,g=rxs,o= with ownership
ntop:ntop) on the directory, the permissions will always be ok:
- the directory will not be accessible by anyone else than ntop,
- the contained files will have appropriate rights to
On 2/8/2010 7:54 AM, Ola Lundqvist wrote:
/var/log/access.log is writeable by everyone. The following would fix that:
The file or the directory?
My file has the following permission:
drwxr-xr-x 2 ntop root 89 May 10 2009 .
drwxr-xr-x 15 root root4096 Feb 8 01:21 ..
-rw---
Hi,
On 2/8/2010 8:03 AM, Ola Lundqvist wrote:
First, postrm does not check for the possible location of the init.cfg file
in /var/lib/ntop/ = fixed
True and intentional. With the debian package /etc/ntop/init.cfg is
the place where it should be.
However, after a new installation there is
On 2/8/2010 11:13 PM, Ola Lundqvist wrote:
drwxr-xr-x 2 ntop root 4096 2010-01-27 11:18 .
drwxr-xr-x 12 root root 4096 2010-01-27 11:17 ..
-rw-rw-rw- 1 root root0 2010-01-27 11:18 access.log
Not good. However I do not think postinst is good enough. We must change
the umask instead so
First, postrm does not check for the possible location of the init.cfg
file in /var/lib/ntop/ = fixed
True and intentional. With the debian package /etc/ntop/init.cfg is
the place where it should be.
However, after a new installation there is no (default) one there.
It isn't? I must
Package: ntop
Version: 3:3.3-11+b2
Severity: normal
Tags: patch
First, postrm does not check for the possible location of the init.cfg file in
/var/lib/ntop/ = fixed
Second, there is no ntop/createuser entry in debconf, as none is added in the
config file = check removed
Also done some
Package: ntop
Version: 3:3.3-11+b2
Severity: normal
Tags: patch, security
/var/log/access.log is writeable by everyone. The following would fix that:
--- postinst2008-08-06 17:55:17.0 +0200
+++ postinst.new2010-02-06 14:07:59.0 +0100
@@ -35,14 +35,17 @@
sry I forgot to add the redirection to the second and most important
case of the if-statement -.-
--- /root/amavisd-new-cronjob.orig 2010-01-10 06:39:19.0 +0100
+++ /usr/sbin/amavisd-new-cronjob 2010-01-10 06:37:52.0 +0100
@@ -19,20 +19,20 @@
# WATCH OUT FOR PROPER
reassign 437836 3.0.2-4
thanks
within a few weeks, when Lenny is out of the door
So? ;-)
--
To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org
with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
I was thinking to another possibility. Maybe I should disable this test
by default.
I vote for that.
Just include a comment about the situation in the config file.
--
To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org
with a subject of unsubscribe. Trouble? Contact
Package: drupal6
Version: 6.6-3lenny3
Severity: minor
In fact,
as $base_url is considered optional in settings.php, one might also add --fail
to the call to curl (ignore failures, i.e. send no mail to www-data) as
failures can happen all the time if
- $base_url is not specified (as it is
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
found 534462 6.6-3lenny3
tags 534462 patch
thanks
Please find below a patch to address the issue for the default site,
including the 'all' site (see #513522).
As far as I can see this is not only in etch-backports, but in lenny too.
Choose for
I've had similar trouble with libnss-mdns.
In my case it was due to the upgrade to Lenny.
Using aptitude, it pulled in recommended packages (not sure whether that
was disabled before, but hey, maybe aptitude's preferences were changed
as it got updated BEFORE the actual upgrade, as recommended by
Package: amavisd-new
Version: 1:2.6.1.dfsg-1
Severity: minor
The cron job executes correctly at the 18th minute of every 3rd hour but
generates output and therefore sends a mail like the following
bayes: synced databases from journal in 1 seconds: 1771 unique entries (3738
total entries)
In
Package: amavis-stats
Version: 0.1.12-10
Severity: important
After upgrading to Lenny I noticed that spam statistics would no longer graph.
The error on the daily spam stats graph (after a day with no data) is
amavis-stats::error: rrd_graph():, but maybe that's normal if there is no
data.
So
After upgrading to lenny my saslauthd was broken too.
I'm attaching the diff between my old defaults file and the one coming
with the new version, which I'm using now.
--- saslauthd 2009-12-13 03:22:14.0 +0100
+++ sasl.old2007-04-12 02:16:24.0 +0200
@@ -1,19 +1,10 @@
#
#
Severity: important
This makes just about 50% of this package useless indeed.
--
To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org
with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Package: loop-aes-modules-2.6.26-2-686
Version: 2.6.26+3.2c-6+lenny1
Severity: grave
Justification: renders package unusable
# aptitude install loop-aes-modules-2.6.26-2-686
# modprobe loop-aes
# lsmod | grep loop
loop 55372 0
# dmesg | tail -3
[ 4457.015307] loop: module
Max Vozeler wrote:
Can you verify that you have the package loop-aes-utils
installed? This looks like it is not installed.
Alright ;-)
Maybe there should be a README or dependency coming with the
loop-aes-modules-2.6.26-2-686
package to pull in loop-aes-utils.
Also, I suggest to read through
Package: specter
Version: 1.4-2+b1
Severity: grave
Justification: renders package unusable
strace start-stop-daemon --start --quiet --exec /usr/sbin/specter -- -d --uid
specter --gid specter
open(/etc/specter.conf, O_RDONLY) = 3
fstat64(3, {st_mode=S_IFREG|0644, st_size=3119, ...}) = 0
... none of which is available in any standard release like Lenny or Etch.
Thanks for noting the concern though ;-)
--
To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org
with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Why are the ipset userland tools there anyway when there is no kernel
support out-of-the-box?
--
To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org
with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Package: fail2ban
Version: 0.7.5-2etch1
Severity: important
/etc/logrotate.d/fail2ban has the following post-rotate command:
invoke-rc.d --quiet fail2ban reload /dev/null
This will however purge the chains, even though some entries might have
a bantime that is longer than the log rotation
I did, and ignoring the new releases it shows at the top
Security alert. Local file inclusion bug. More info here, fixed release
available. [18]
(http://bugs.splitbrain.org/index.php?do=detailstask_id=1700)
So that is fixed already too?
I guess one would simply need to remove these warnings in
Openvpn should become ipv6-ready soon.
ipv6 is around the corner ;-)
Fiddling around with up scripts is not that cool.
--
To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org
with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Mohammed Adnène Trojette wrote:
I guess one would simply need to remove these warnings in the packages?
These warnings are not in the package. They are grabbed from upstream's
website as soon as the package is outdated.
Yeah, but then one could do something like described here
Does that mean one can use the setting to hide the warnings at the top
of the screen since those problems are actually not there in the
Debian-packaged version, i.e. have been patched?
--
To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org
with a subject of unsubscribe. Trouble?
Hmmm... I don't know but maybe there is a reason that they want user #1
logged in. Maybe the 1 is of importance. Just a thought.
But you're right, in theory user #1 could have been given only
authenticated user right whereas someone else has become the admin.
Maybe one should ask this question
Package: drupal6
Version: 6.6-3~bpo40+1
Priority: wishlist
I have several sites in the sites directory and no default site.
Therefore the cron script each time it is executed sends me a mail that
the default site (which I don't use) is offline.
What would be the smartest way to go about this?
4.5 in etch?
You mean the obsolete package that was left from sarge? ;-)
Oh well I just went the way from the obsolete 4.5.x to 6.6-3~bpo40+1 (etch).
You do not need to upgrade every minor version. (see
http://drupal.org/upgrade/)
In my case what I had to do was:
- 4.5.x - 4.7.x (the latest in
I would like to apologize again for calling the package orphaned and for
not looking hard enough before complaining.
However, one would expect that for Etch there would be some sort of
security updates if I look at all the warnings that greet me at the top
of the screen each time I use dokuwiki.
Never mind my previous comment.
Release 2008-05-05 seems to be in Lenny and is the second most recent
release (the most recent one being Release 2009-02-14). See
http://www.dokuwiki.org/changes
--
To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org
with a subject of
Maybe the better solution would be to declare this package orphaned.
--
To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org
with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Ondřej Surý wrote:
So the actual item for the wishlist is to be able to specify a user (or more
than one) that are considered trusted. Suexec will then allow files
owned by either the target user, or by a trusted user, to be executed.
Use chattr +i file
Ondrej.
That much we had already
Since I stumbled across the same problem I wonder where is the relation
of this bug to #394136, which was fixed in cryptsetup/2:1.0.4-4?
It doesn't work for me, so it is not fixed then? Any workaround?
thanks, florian
So, what is different here from the bug that Florian mentioned?
I also fail
Hi,
Jonas Meurer wrote:
On the other hand, did you actually try to reproduce the bug?
I just tried again with expert mode installation and Lenny rc2
debian-installer businesscard image. At release selection I selected
'unstable'.
I have not recently tried with the installer, no.
The
Package: mdadm
Version: 2.5.6-9
Severity: important
I'm not sure if these should be regarded as two issues. Please let me know.
First, we have in /etc/rc[06].d:
S50lvm
S50mdadm-raid
either:
- lvm is tried to be stopped first (as L precedes M), or
- lvm and mdadm-raid are stopped concurrently
Package: ifupdown
Version: 0.6.8
Followup-For: Bug #360806
i use the following /etc/network/interfaces pre-up and post-down
commands to do stuff
iface eth0 inet static
pre-up /usr/local/sbin/iip_iptables-restore
post-down /usr/local/sbin/iip_iptables-save
the pre-up
I believe this won't fix.
Even if the docroot of suphp would be modified to include /usr/share and
all that lies within (like phpbb2 etc.) still the permissions of those
files would be incorrect.
The web users would not be allowed to access those files because of
their permissions. In such a
I recommend patching using this:
http://www.phpbb.com/community/viewtopic.php?t=473222
It effectively reduced the account registration attempts by bots to zero
as it replaces the long cracked captcha.
Furthermore, it consists of only the addition of 1 (one) code file,
several fonts and one
The following change, courtesy of the Ubuntu cacti-0.8.6i package,
fixes the problem:
/usr/share/cacti/include/config.php, line 86:
change:
if (!((is_file($_SERVER[SCRIPT_FILENAME])) (substr_count($_SERVER
[SCRIPT_FILENAME], $_SERVER[PHP_SELF] {
to:
if
Package: cacti
Version: 0.8.6i-3.3
Severity: important
You have inserted a sanity check into /usr/share/cacti/site/include/config.php.
However, this breaks at least my (standard) setup as (at least):
substr(/usr/share/cacti/site/index.php, /cacti/index.php) = 0
Additionally my DOCUMENT_ROOT of
AuthBasicAuthoritative off
AuthUserFile /dev/null
as additional arguments do the trick for me
however, this package seems to be no longer in development
one might consider taking a look at
http://mod-auth.sourceforge.net/docs/mod_authn_pam/
--
To UNSUBSCRIBE, email to [EMAIL PROTECTED]
with
Package: arpalert
Version: 2.0.3-1
Severity: normal
arpalert init script does not consider daemon=false from config file
this should probably be checked for and be put into /etc/default/arpalert anyhow
-- System Information:
Debian Release: 4.0
APT prefers stable
APT policy: (500, 'stable')
Package: amavisd-new
Version: 1:2.4.2-6.1
Severity: minor
In /etc/amavis/conf.d/20-debian_defaults it is mentioned:
# Leave empty (undef) to add no header
$X_HEADER_LINE = Debian $myproduct_name at $mydomain;
This is wrong as the amavisd-new source reads
$X_HEADER_TAG = 'X-Virus-Scanned'
This seems to be fixed in etch.
At least I tried it with the new PHP (4.4, I did NOT try 5.x!)
So, anyone try the (original) multiboard method with PHP 5?
Anyway, I guess this problem was successfully sat out by the maintainer.
Grats :)
--
To UNSUBSCRIBE, email to [EMAIL PROTECTED]
with a
1 - 100 of 112 matches
Mail list logo
