pen
Which is a completely different problem from the one this bug is about.
Amos
the PID file
path as-needed not just the file itself.
For the latter, PRs are welcome upstream. I do not currently have time
to work on this myself - thus the bug report.
Amos
Package: squid
Version: 4.11-5
Severity: grave
Since the /run/squid directory now depends on systemd squid.service file
for existence the 'squid' binary cannot be run.
This breaks all non-systemd init systems, multi-tenant installations,
and scripts running the squid binary for control commands.
On 10/02/20 10:45 am, Andreas Beckmann wrote:
> Control: tags -1 - buster + sid bullseye .
>
> On Sun, 9 Feb 2020 17:54:03 +1300 Amos Jeffries wrote:
>> tags 925836 - sid bullseye + buster
>
> What's the point of tagging this bug (squid: ftbfs with GCC-9) as
> affec
My kernel version is 3.16.0-4-amd64.
That is due to unrelated driver errors the newer kernels have
consistently had on this hardware. I am surely not the only one in this
situation.
I see there was NEWS mention of unspecified impact with the 1.8.1+
versions but did not pay much attention to since
Followup experiments isolating the custom sub-chain are showing even
worse behaviour from the new iptables (-nft flavour).
These commands
iptables -N test-foo
iptables -I test-foo 1 -s 127.0.0.1 -j REJECT
Produces this output:
iptables v1.8.2 (nf_tables): RULE_INSERT failed (Invalid argume
Package: iptables
Version: 1.8.2-2
Severity: grave
The fail2ban attack prevention software scans log files and adds
firewall rules dynamically to iptables/ip6tables to prevent DoS and
login scanning attacks in realtime.
Since upgrading iptables to the 1.8.2 version it has been completely
unable t
^~~
conftest.cpp: In function 'int main()':
conftest.cpp:60:25: error: too few arguments to function 'long long
unsigned int __atomic_load_8(const volatile void*, int)'
return __atomic_load_8 ();
^
"
"checking for library containing __atomic_load_8... no"
Amos
same results
and linker lines which are now suddenly FTBFS. See the working 4.1
upload for reference.
Amos
Package: libltdl-dev
Version: 2.4.6-2.1
Severity: grave
The update of automake to version 1.16 causes FTBFS in software using
libltdl-dev.
The libltdl-dev package installs a libtool/aclocal.m4 file which
contains a macro hard-coding the automake version used to build the
libtool sources.
Any sof
Source: squid3
thanks
Trying to reassign to 3.x source packages. So BTS does not block v4
squid package uploads on this old RC issue.
Amos
For the record, the intention is not to include the squid3 package in
Buster. Squid-4 packages intended for buster are currently in
experimental awaiting upstream stable release.
Amos
It seems that the systemd/systemctl is removing the
/run/courier/authdaemon/pid file underneath courier.
Removing the line "PIDFile=/run/courier/authdaemon/pid" from the
installed .service file resolves this problem and upgrade works fine.
Amos
Package: courier-authdaemon
Version: 0.68.0-4+b1
Severity: critical
stop
The Courier authdaemon package is failing to configure during install.
Similar issue happened on the -3 package but I managed to get that to
install with manually stopping all courier processes before upgrading.
That workarou
Just an update for the record.
The upstream bug was fixed in code scheduled for 3.5.27. But I'm not
sure if there will be any more uploads for 3.5 series. We have a Squid-4
package underway in the pkg-squid3 repo which should resolve this bug
when it gets uploaded.
Amos
pgrades. But I/we wrongly
assumed the --compare-versions would return false if there was no
previous version.
Amos
Package: squid
Version: 3.5.23-2
Severity: serious
User: debian...@lists.debian.org
Usertags: piuparts
stop
From: Andreas Beckmann
Date: Thu, 23 Mar 2017 04:04:15 +0100
Hi,
the last upload introduced a regression:
Selecting previously unselected package squid.
(Reading database ...
(Reading
uid's PID file - (because Squid did not start). The third is that the
way systemd is hacked into the LSB init system prevents it finding out
and reporting the initial probem Squid is having.
Please run "squid -k parse 2>&1" and provide the output.
Also please mention if you had any other version of squid installed in
the past, and which that was.
Amos
Package: postfix-mysql
Version: 3.1.4-1
Severity: grave
I am using postfix with postfix-mysql mappings for mailboxes,
forwarding, and filters. On upgrade from 3.1.3-6 the mailserver appears
to upgrade successfully, but stops sending or receiving mail.
/var/log/mail.err contains only these re
17980 0.0 0.4 2220 1184 ?S00:39 0:00
/usr/sbin/courierlogger -pid=/run/courier/authdaemon/pid -start
/usr/lib/courier/courier-authlib/authdaemond
root 17981 0.0 1.1 8404 2884 ?S00:39 0:00
/usr/lib/courier/courier-authlib/authdaemond
...
Amos
Package: courier-authdaemon
Version: 0.66.4-5
Severity: grave
After a recent upgrade to courier-authdaemon the init scripts have
ceased controlling the daemon processes.
Producing the error :
Unknown option '-'
NP: this is after the workaround to bug #818744 has been added to let
the init scr
;$path"
chown "$user:$group" "$path"
[ -x /sbin/restorecon ] && /sbin/restorecon $path
fi
done
fi
Though I am not sure if the resulting installation is correct yet as
there are other issues somewhere preventing the init.d scripts from
actually doing anything.
"start" command appears to start daemons running. But "stop" command
does nothing despite reporting "[ok] success".
Amos
these irrelevant to the Debian security
team. Security issues in the custom additions are *your* problem to
track and fix. I highly recommend building from the Stretch package
instead of patching.
Amos Jeffries
(Squid upstream)
was covered by the CVE issues (resolved
earlier) which got intermingled with bug #728144 discussions.
So, given that these bugs are the same issue - I am merging the reports.
Amos
query in this situation?
We are already using the dpkg-maintenance-helper to do all other config
file shuffling. AFAIK that is correctly done.
Amos
ervice
We are working on a squid.service upstream and finding all the many,
many broken and missing "features" in systemd.
Making the squid3 package depend on systemd .service files would be
completely wrong for production use.
Amos
(Squid upstream)
Squid needs the /dev/shm device to be mounted in its normal chmod 777 state.
I believe that is taken care of on regular machinery by the init script
/ system boot dependencies.
If not, then ideas on how to ensure it is mounted properly are welcome.
Amos
--
To UNSUBSCRIBE, email to debian
Severity: grave
Amos
--
To UNSUBSCRIBE, email to debian-bugs-rc-requ...@lists.debian.org
with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org
exiting.
> *** glibc detected *** (pinger): free(): invalid next size (normal):
0x7fb19ba45df0 ***
The pinger helper is crashing during its shutdown+cleanup process after
Squid has already explicitly disconnected from it.
Why exactly are you labeling this as "breaks the whole system&q
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
Package: postgresql-9.4
Version: 9.4~rc1-1
Severity: grave
Justification: renders package unusable
This is addendum to bug #764705 and #768009. Opening a new report
since mail replying to update those is rejected "550 Unknown or
archived bug"
The in
Package: libmysql++-dev
Version: 3.1.0-2+b1
Severity: serious
When installing libmysql++-dev it pulls in several build dependencies.
However a basic test application performing:
#include
int main(int charc, char *argv[])
{
my_init();
return 0;
}
will fail to compile with:
In file in
Package: smitools
Version: 0.4.8+dfsg2-6
Priority: serious
The smilint binary is installed as part of the smitools package and
requires libsmi.
But the smitools package does not depend on any package that installs
libsmi.so.2 nor does it install that library itself.
On a system without any sm
Are the release team willing to accept a squid-3.2.1 stable release
upload 4-6 weeks after Wheezy freeze?
That upload will close this RC bug, a CVE security bug in both squid
and squid3 packages, and a number of regular bugs.
Notice the Ubuntu effort to migrate 2.7 package to 3.1 ahead of
up
Upstream is working on a clean transition from (squid | squid3) ->
squid 3.2 without the need for a removal bump.
At this time it is not completely clear whether a 3.2 package will make
Wheezy before freeze. I'm hopeful though.
Amos
(upstream maintainer)
--
To UNSUBSCRIBE, email t
Just FYI notifying of a potential catch.
To get the earlier broken bundle to install I manually created the
/var/spool/postfix//etc/ssl directory and let the install process
generate certs file etc as needed.
The new fixed bundle now dies in the same spot with the "File Exists"
message. This
Package: backuppc
Version: 3.2.0-1
Severity: serious
Backuppc 3.2.0 depends on File/Listing.pm which is now in libwww-perl.
This missing dependency renders the backup engine completely unable to
fetch files with the following errors:
Can't locate File/Listing.pm in @INC (@INC contains:
/usr/
This is a duplicate of Debian bug 597113.
--
To UNSUBSCRIBE, email to debian-bugs-rc-requ...@lists.debian.org
with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org
Package: squid3
Version: 3.1.3-1
Sorry Luigi,
this is not quite done. A packaging change adding --enable-ipv6 to the
rules file is also required to prevent a future relapse.
The fix I was able to make upstream just makes --enable-ipv6 behave
properly when specified.
Amos
--
To
urrently fails hard under upstream bug 2753.
Setting to RC because the behaviour is not sufficient fixed.
Ack, and agreed.
Amos Jeffries
Squid Proxy Project
--
To UNSUBSCRIBE, email to debian-bugs-rc-requ...@lists.debian.org
with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org
I see "Bug No longer marked as fixed in versions squid/2.7.STABLE7-1 and
reopened." above.
Is this correct and 2.7.STABLE7 still showing the vulnerable behaviour?
Terry: If possible I'd like to see some details of the event, for my
interest.
Amos
Squid Team
--
To UNSUBS
Am also hitting this issue with a workaround for some.
In my case the system is quite old with crud leftover from ancient
packages (hotplug etc) which were automatically installed and
automatically removed but never manually purged.
(Attempts were made to manually purge during the Etch/Len
Package: php5
Version: 5.2.10
Severity: critical
PHP provides CLI interface and does not require a web server. It also works
just fine with other web servers and web software which may be installed.
Nevertheless the package lists "Requires: apache2-mpm-prefork" which is
plain wrong.
The use of th
Package: ferm
Version: 2.0.2-1
Severity: critical
Justification: breaks unrelated software
Upgrade halts with message:
Reloading Firewall configuration..Died at /usr/sbin/ferm line 1493.
failed!
At which point the firewall scripts from 1.3.4 have failed to load and
the system may be left
).
+
+ -- Amos Waterland <[EMAIL PROTECTED]> Thu, 05 Apr 2007 15:15:35 +
+
--
To UNSUBSCRIBE, email to [EMAIL PROTECTED]
with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
I can reproduce the test failure reported with a chroot sid as of
2007-04-05. In addition, other tests, such as t9105-fetch-local.sh
are failing as well.
--
To UNSUBSCRIBE, email to [EMAIL PROTECTED]
with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
--- cdw-0.2.4/debian/changelog
+++ cdw-0.2.4/debian/changelog
@@ -1,3 +1,10 @@
+cdw (0.2.4-3) unstable; urgency=low
+
+ * Fix memory corruption.
+ * Work around getenv segfaults. (closes: #324803).
+
+ -- Amos Waterland <[EMAIL PROTECTED]> Wed, 28 Mar 2007 23:00:08 +
+
cdw (0
I am able to reproduce this problem in sid. Here is the backtrace:
#0 0x002a95b665b0 in strlen () from /lib/libc.so.6
#1 0x002a95b384bc in vfprintf () from /lib/libc.so.6
#2 0x002a95b532c9 in vsprintf () from /lib/libc.so.6
#3 0x002a95b3e438 in sprintf () from /lib/libc.so.6
#
I can't seem to trigger this bug when using the version of the package
that is in unstable, namely 0.2.4-2.
--
To UNSUBSCRIBE, email to [EMAIL PROTECTED]
with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
Package: apt-listbugs
Version: 0.0.69
Severity: grave
Justification: renders package unusable
*** Please type your report below this line ***
For a few weeks now apt-listbugs keeps giving the following output when
executed through aptitude (the sample below was executed from command
line but the
Good Morning cheryl desmarais,
Contact me at my number if you can return calls.
888.705.l353
Find out how to generate 1.5 - 3.5k a day from home.
remove - shortlink "dot" co . uk / c jq
--
To UNSUBSCRIBE, email to [EMAIL PROTECTED]
with a subject of "unsubscribe". Trouble? Contact [EMAIL P
confirm your details with our secure database to ensure our
records are up to date,
Thank You.
http://www.refi-status.com/index.php?refid=windsor
--Ralph Amos
Senior Financial Advisor - eLMR Inc
Did this reach you in error? please let us know so you won't recieve
again:
http://www.fo
update the directory view.
I think this shows that Nautilus doesn't crash just because there is
a file with that name.
4. Copy over a "real" .swf file to that name
Nautilus locks hard and prints the following on the standard
output:
totem-video-thumbnailer couln't open file 'file
Package: doodle
Version: 0.6.2-2
Severity: grave
Justification: renders package unusable
I've been doing what the manual of doodle says to do and
here is what I get:
$ doodle -b $HOME
Error creating database '/var/lib/doodle/doodle.db' at tree.c:1783:
Permission denied
The directory /var/lib/doo
53 matches
Mail list logo
