Package: sponsorship-requests
Severity: normal
Dear mentors,
I am looking for a sponsor for my package "radsecproxy":
* Package name : radsecproxy
Version : 1.10.1-1
Upstream contact : Fabian Mauchle
* URL : https://radsecproxy.github.io/
* License :
On 18.12.23 07:37, Chris Knadle wrote:
Thank you very much for your efforts on this bug.
Most the changes the patches make and offhand look reasonable, and for
the moment I've pulled them from the 'improvement' branch your mumble
Git repo.
However I'm wondering about the permissions change
On Fri, 8 Dec 2023 17:36:21 +0100 Sven Hartge wrote:
You can either pull from https://salsa.debian.org/hartge/mumble.git or
apply the attached diff.
From the "improvements" branch I meant to say.
Grüße,
Sven.
On Fri, 3 Mar 2023 06:16:00 + Chris Knadle
wrote:
If someone knows how to fix the mumble-server.service file so that mumble-server
can start, that would be helpful; once that's fixed I can make an upload to
Debian Experimental. The file in the tree is at:
Hello Chris,
I looked at the
Package: sponsorship-requests
Severity: normal
Dear mentors,
I am looking for a sponsor for my package "radsecproxy":
* Package name : radsecproxy
Version : 1.10.0-2~bpo12+1
Upstream contact : Fabian Mauchle
* URL : https://radsecproxy.github.io/
* License
Package: sponsorship-requests
Severity: normal
Dear mentors,
I am looking for a sponsor for my package "radsecproxy":
* Package name : radsecproxy
Version : 1.10.0-2
Upstream contact : Fabian Mauchle
* URL : https://radsecproxy.github.io/
* License
Hello,
I misinterpreted the error.
LWP::Debug::trace() still exists, but one needs to explicitly add
use LWP::Debug;
to the code to be able to use it.
Either way, the code is still very old, broken in the default state,
LWP::Debug only exists for legacy code and should not be used anymore
Package: liblwp-protocol-http-socketunix-perl
Version: 0.02-4
Severity: grave
Tags: upstream
Hi!
The module has been broken for a long long time, it tries to
unconditionally use LWP::Debug::trace which has been remove from LWP.
The attached reproducer shows the problem.
There is a forked and
Package: sponsorship-requests
Severity: normal
Dear mentors,
I am looking for a sponsor for my package "radsecproxy":
* Package name : radsecproxy
Version : 1.10.0-1
Upstream contact : Fabian Mauchle
* URL : https://radsecproxy.github.io/
* License
+++ radsecproxy-1.9.2/debian/changelog 2023-03-06 16:39:08.0 +0100
@@ -1,3 +1,10 @@
+radsecproxy (1.9.2-2) unstable; urgency=medium
+
+ * Improve logcheck patterns to reduce noise
+ * Make logcheck rules compatible with all syslog timestamp formats
+
+ -- Sven Hartge Mon, 06 Mar 2023 16:39:08 +0100
On Mon, 6 Mar 2023 17:02:07 +0100 Sven Hartge wrote:
Changes since the last upload:
radsecproxy (1.9.2-2) unstable; urgency=medium
.
* Improve logcheck patterns to reduce noise
* Make logcheck rules compatible with all syslog timestamp formats
I really would like to get those
Package: sponsorship-requests
Severity: normal
Dear mentors,
I am looking for a sponsor for my package "radsecproxy":
* Package name : radsecproxy
Version : 1.9.2-2
Upstream contact : Fabian Mauchle
* URL : https://radsecproxy.github.io/
* License :
Package: sponsorship-requests
Severity: normal
Dear mentors,
I am looking for a sponsor for my package "radsecproxy":
* Package name : radsecproxy
Version : 1.9.2-1~bpo11+1
Upstream contact : Fabian Mauchle
* URL : https://radsecproxy.github.io/
* License
Package: sponsorship-requests
Severity: normal
Dear mentors,
I am looking for a sponsor for my package "radsecproxy":
* Package name : radsecproxy
Version : 1.9.2-1
Upstream contact : Fabian Mauchle
* URL : https://radsecproxy.github.io/
* License :
On Sun, 17 Jul 2022 02:44:37 -0400 Awtul wrote:
ValueError: Namespace Notify not available for version 0.7".
That is the true error here, https://github.com/Guake/guake/issues/2110
You need to install "gir1.2-notify-0.7 > 0.8.1-1" to make it work again.
Grüße,
Sven.
On 15.04.22 13:29, Klaus Ethgen wrote:
I also have a nagios bacula monitor running every 5 minutes.
(/usr/lib/nagios/plugins/check_bacula) But this seems to stay green all
the time.
The log entries you see might be just from that check and not from the
running backup, just intermingled
On 09.04.22 12:12, Klaus Ethgen wrote:
Since upgrade from 9.6.7-3 to 9.6.7-4 I get many of the following errors
in the log. However, the backup seems to work.
JobId 0: Security Alert: bsock.c:380 Write error sending 4 bytes to
client:127.0.0.1:57050: ERR=Broken pipe
JobId 0: Security Alert:
On 05.04.22 13:20, Helmut Grohne wrote:
Hello Helmut,
thank you for your time to not only diagnose the problem but also
provide a solution.
bacula fails to cross build from source, because it attempts to use the
build architecture qmake while Build-Depends requested the host
architecture
Package: memlockd
Version: 1.3-2
Severity: grave
Hello!
The subject says it all: The package is missing the binary:
,
| oweh@ds9:~$ dpkg -L memlockd
| /.
| /etc
| /etc/default
| /etc/init.d
| /etc/init.d/memlockd
| /etc/memlockd.d
| /lib
| /lib/systemd
| /lib/systemd/system
|
w upstream version 1.9.1
Compatible with OpenSSL 3.0
.
[ Faidon Liambotis ]
* Replace myself (Faidon) with Sven as the maintainer
.
[ Sven Hartge ]
* Compatible with Policy 4.6.0.0, no changes needed
* Taking over full maintainership, many thanks to Faidon for his work
i
Um 21:04 Uhr am 23.10.21 schrieb Lucas Nussbaum:
> Relevant part (hopefully):
> > touch src/qt-console/tray-monitor/.libs/bacula-tray-monitor
> > chmod 755 src/qt-console/tray-monitor/.libs/bacula-tray-monitor
> > dh_auto_configure -- --enable-smartalloc --with-tcp-wrappers --with-openssl
> >
Package: sponsorship-requests
Severity: normal
Dear mentors,
I am looking for a sponsor for my package "radsecproxy".
Since this is the first upload to buster-backports-sloppy, a full binary
upload will be needed.
* Package name: radsecproxy
Version : 1.9.0-1~bpo10+1
Package: sponsorship-requests
Severity: normal
Dear mentors,
I am looking for a sponsor for my package "radsecproxy".
As this is the first upload to "bullseye-backports", a full binary
upload will be necessary.
* Package name: radsecproxy
Version : 1.9.0-1~bpo11+1
Upstream
Package: sponsorship-requests
Severity: normal
Dear mentors,
I am looking for a sponsor for my package "radsecproxy":
* Package name: radsecproxy
Version : 1.9.0-1
Upstream Author : Fabian Mauchle
* URL : https://radsecproxy.github.io/
* License :
Package: sponsorship-requests
Severity: normal
Dear mentors,
I am looking for a sponsor for my package "radsecproxy":
* Package name: radsecproxy
Version : 1.8.2-4~bpo10+1
Upstream Author : Fabian Mauchle
* URL : https://radsecproxy.github.io/
* License
Package: sponsorship-requests
Severity: normal
Dear mentors,
I am looking for a sponsor for my package "radsecproxy":
* Package name: radsecproxy
Version : 1.9.0-1~exp1
Upstream Author : Fabian Mauchle
* URL : https://radsecproxy.github.io/
* License :
--- radsecproxy-1.8.2/debian/changelog 2020-11-23 12:09:13.0 +0100
+++ radsecproxy-1.8.2/debian/changelog 2021-05-27 07:58:57.0 +0200
@@ -1,3 +1,9 @@
+radsecproxy (1.8.2-4) unstable; urgency=high
+
+ * Fix CVE-2021-32642
+
+ -- Sven Hartge Thu, 27 May 2021 07:58:57 +0200
Package: sponsorship-requests
Severity: normal
Dear mentors,
I am looking for a sponsor for my package "radsecproxy":
* Package name: radsecproxy
Version : 1.8.2-4
Upstream Author : Fabian Mauchle
* URL : https://radsecproxy.github.io/
* License :
Package: sponsorship-requests
Severity: normal
Dear mentors,
I am looking for a sponsor for my package "radsecproxy":
* Package name: radsecproxy
Version : 1.9.0~rc1-1~exp1
Upstream Author : Fabian Mauchle
* URL : https://radsecproxy.github.io/
* License
Package: plocate
Version: 1.1.6-3
Severity: normal
Hi!
You added
RandomizedDelaySec=12h
AccuracySec=20min
to plocate-updatedb.service but they belong into plocate-updatedb.timer
in the [Timer] section.
Right now, this only creates a warning
Apr 06 17:40:37 host systemd[1]:
Package: sponsorship-requests
Severity: normal
Dear mentors,
I am looking for a sponsor for my package "radsecproxy":
* Package name: radsecproxy
Version : 1.8.2-4~exp1
Upstream Author : Fabian Mauchle
* URL : https://radsecproxy.github.io/
* License :
Package: pyzor
Version: 1:1.0.0-5
Severity: grave
Hi!
The fix for https://bugs.debian.org/923077 seems to have introduced a
serious regressing, causing pyzor to stop working on check:
~$ pyzor check < testmail
Traceback (most recent call last):
File "/usr/bin/pyzor", line 411, in
main()
Package: fp-compiler-3.2.0
Version: 3.2.0+dfsg-9
Severity: grave
Justification: renders package unusable
Hi!
During postinst the following happens:
Setting up fp-compiler-3.2.0:amd64 (3.2.0+dfsg-9) ...
Saved old "fpc-3.2.0.cfg" to "fpc-3.2.0.bak"
On 27.11.20 20:48, Radoslav Bodó wrote:
I wonder whether this might be a proper solution which works for everybody:
* it resolved the original issue
* it matches postgresql schema a bit more
* also ClientId types gets synced across all columns in all tables
Only upstream can tell.
Since you
On 27.11.20 19:01, Radoslav Bodó wrote:
I have elaborated a bit on your progress and come up with following
patch (attachment) which processes fine on current Bullseye.
Yes, this matches some of my findings.
I also noticed that bacula.BaseFiles has
BaseJobId INTEGER UNSIGNED NOT NULL
Um 13:58 Uhr am 27.11.20 schrieb Radoslav Bodó:
> ```
> # /usr/bin/mysql -NB bacula <
> /usr/share/dbconfig-common/data/bacula-director-mysql/install/mysql
> ERROR 1005 (HY000) at line 35: Can't create table `bacula`.`File`
> (errno: 150 "Foreign key constraint is incorrectly formed")
> ```
Yes,
Package: sponsorship-requests
Severity: normal
Dear mentors,
I am looking for a sponsor for my package "radsecproxy":
* Package name: radsecproxy
Version : 1.8.2-3
Upstream Author : Fabian Mauchle
* URL : https://radsecproxy.github.io/
* License :
Package: xtables-addons-dkms
Version: 3.11-1
Severity: grave
Hi!
Kernel 5.9.9 changes ip_route_me_harder() with commit
46d6c5ae953cc0be38efd0e469284df7c4328cf8 causing a build failure for
xtables-addons-dkms:
,
| In file included from
Um 01:57 Uhr am 20.10.20 schrieb Axel Beckert:
> Mind submitting a pull request for this upstream at
> https://github.com/aabc/ipt-netflow? You are likely better in
> explaining the whole background of this patch and we would not have
> Chinese whispers when I'd be relaying potential arguments
Um 19:54 Uhr am 19.10.20 schrieb Sven Hartge:
> If I add the switch "-B" to the make command in gen_compat_def I can
> reliably get the test to work correctly even on the systems with the older
> filesystem:
>
>cmd="make -s -B -C $KDIR M=$PWD modules&qu
Hi!
I think I know what the problem is and is really really stupid.
The age of my systems was the correct hint here: The filesystem /usr is on
is too old and it does not have microsecond resolution but the CPU is fast
enough to get the job done in under a second.
Which means the test is so
Um 19:28 Uhr am 19.10.20 schrieb Sven Hartge:
> What?!
>
> I tested with debsums -c and even reinstalled
> linux-headers-5.9.0-1-common, comparing the before and after, nothing
> broken, nothing missing.
Scratch that last part. Because make did run correctly during
gen_compa
Um 16:02 Uhr am 19.10.20 schrieb Axel Beckert:
>> Next step would be to strace the dkms build process and compare the
>> output to find out what files are referenced to find the offending
>> header files.
>
> Good idea, thanks!
The more I look at this, the more ?!?! appear above my head.
I am
On 18.10.20 23:59, Axel Beckert wrote:
Sven Hartge wrote:
That's strange. Works fine for me. Tested on sid amd64 as well:
I tested this on a different system with 5.9 and got the same result and
identical make.log.
But, and here it becomes strange: It does work on a third system of mine
On 18.10.20 22:50, Axel Beckert wrote:
That's strange. Works fine for me. Tested on sid amd64 as well:
I tested this on a different system with 5.9 and got the same result and
identical make.log.
But, and here it becomes strange: It does work on a third system of mine.
Question now is:
Package: iptables-netflow-dkms
Version: 2.5.1-1
Severity: grave
Hi!
It seems adfc6318 was not enough to be compatible with Linux 5.9, as
compilation breaks for me with the following log:
---8<--
DKMS make.log for ipt-netflow-2.5.1 for kernel 5.9.0-1-amd64 (x86_64)
Sun 18
Package: xtables-addons-dkms
Version: 3.9-1
Severity: grave
Tags: patch
Hello!
As the subject says: The current version 3.9 does not build with Linux
5.9, but a new upstream release is available.
I created a MR in Salsa correcting this:
Source: dovecot
Version: 1:2.3.11.3+dfsg1-2
Severity: wishlist
Hi!
The subject says it all: Please add libzstd-dev to enable zstd in
zlib_plugin.
Grüße,
Sven.
Package: sponsorship-requests
Severity: normal
Dear mentors,
I am looking for a sponsor for my package "radsecproxy".
This version of the package will be the first upload to buster-backports
and a full binary upload is needed for it to clear NEW.
* Package name: radsecproxy
Version
Package: sponsorship-requests
Severity: normal
Dear mentors,
I am looking for a sponsor for my package "radsecproxy":
* Package name: radsecproxy
Version : 1.8.2-2
Upstream Author : Fabian Mauchle
* URL : https://radsecproxy.github.io/
* License :
w upstream version 1.8.2
* Upgrade debhelper compat level to 13.
* Remove patches applied upstream
* Move man-pages for radsecproxy[-hash] into section 8 to be compliant
with the FHS.
* Add lintian override for testsuite-autopkgtest-missing.
Regards,
--
Sven Hartge
Package: sponsorship-requests
Severity: normal
Dear mentors,
I am looking for a sponsor for my package "radsecproxy"
* Package name: radsecproxy
Version : 1.8.1-2~bpo10+1
Upstream Author : Fabian Mauchle
* URL : https://radsecproxy.github.io/
* License
On Fri, 17 Apr 2020 11:09:51 + Matthias Klose wrote:
> Package: src:radsecproxy
> Version: 1.8.1-1
> Severity: normal
> Tags: sid bullseye
> User: debian-...@lists.debian.org
> Usertags: ftbfs-gcc-10
>
> Please keep this issue open in the bug tracker for the package it
> was filed for. If
* Bump Standards-Version to 4.5.0, no changes needed.
Regards,
--
Sven Hartge
Hello,
I have created MR#4 in Salsa to fix this bug.
Grüße,
Sven.
signature.asc
Description: OpenPGP digital signature
Package: freeradius
Version: 3.0.20+dfsg-3+b1
Severity: important
Hello!
Since 3.0.20 and the switch to Type=notify as start mechanism, the
directory /run/freeradius is no longer automatically created,
resulting in a failure to start if the control-socket vhost is active:
,[
On 22.03.20 19:07, Sven Hartge wrote:
> Interestingly, isc-dhcp-server 4.4.1 does not even compile against the
> current 9.16 libs from Sid right now. Something is very broken here.
I have to correct that part. It seems my checkout from Salsa was wrong,
as recompiling the source package
Package: bind9
Version: 1:9.16.1-2
Severity: critical
Justification: breaks unrelated packages
Hi!
The recent upgrade from 1:9.11.16+dfsg-2 to 1:9.16.1-1 causes
isc-dhcp-server to die upon start with SIGABRT, creating the following
backtrace:
8<
Package: kmod
Version: 26+20191223-1
Severity: normal
Hi!
After upgrade to kmod_26+20191223-1 during update-initramfs, depmod
spews the following errors:
depmod: ERROR: ../libkmod/libkmod.c:515 lookup_builtin_file() could not open
builtin file
On 15.11.19 19:58, Johnny Geling wrote:
> dbconfig-no-thanks was installed instead of dbconfig-pgsql
>
> I removed dbconfig-no-thanks and installed dbconfig-sqlite3
>
> After this modification the installation of bacula with sqlite 3 went as
> expected.
>
> Is there an explicit dependency on
On 15.11.19 08:57, Johnny Geling wrote:
> It also occurs with the stretch package, bacula version 7.4.4
> I purged the packages and reinstalled it. All the same effect.
> Could it be something else is broken? Something in Apt or Debconf?
No, I still cannot reproduce this on armhf, i386 and
On 14.11.19 23:34, Johnny wrote:
>* What led up to the situation?
> Installing the bacula package, the database is not configured. This is with
> all 3 databases.
> The error seen during installation:
> /var/lib/dpkg/info/bacula-director.postinst: 39: .: Can't open
>
On 25.09.19 21:02, Sven Hartge wrote:
> On 25.09.19 20:23, Antoine Beaupré wrote:
>> And unfortunately, this configuration is shipped in the Debian package,
>> in /usr/share/bacula-common/defconfig/bacula-dir.conf
> I can't find the code in bacula-common_9.4.2-1~bpo9+1
To c
On 25.09.19 20:23, Antoine Beaupré wrote:
> The safest thing would be to remove all "(Bacula)" stuff from any mailcommand
> out there.
I agree with your analysis and will look into this in the next days.
Grüße,
Sven.
signature.asc
Description: OpenPGP digital signature
On 25.09.19 20:23, Antoine Beaupré wrote:
> And unfortunately, this configuration is shipped in the Debian package,
> in /usr/share/bacula-common/defconfig/bacula-dir.conf
I can't find the code in bacula-common_9.4.2-1~bpo9+1
The code in the file you mentioned is correct:
mailcommand =
On Wed, 25 Sep 2019 14:53:32 +0200 Hostinet wrote:
> Script /usr/share/bacula-director/grant_mysql_privileges line 11:
> db_password=XXX_DBPASSWORD_XXX
This script (or any other script /usr/share/bacula-director/) in is
never used by Debian to setup the database or grant MySQL permissions,
so
On Sun, 31 Mar 2019 14:10:10 +0100 Jorge Daniel Sequeira Matias
> Despite the fact I have tested this package doing a backport for Debian
> "wheezy" the package upgrade operation aborts even the installer replaced
> /etc/radsecproxy.conf.
> This is due to the fact that if the config already
Package: guake
Version: 3.6.3-1
Severity: important
Hi!
3.6.3-1 no longer works for me, unless I install gir1.2-wnck-3.0.
When gir1.2-wnck-3.0 is missing, I only get the following error on startup:
Traceback (most recent call last):
File "/usr/lib/python3/dist-packages/dbus/bus.py", line
On 31.07.19 08:37, Sven Hartge wrote:
> This was ISC-Bug 45457:
> https://bugs.isc.org/Public/Bug/Display.html?id=45457
>
> This bug has been fixed in ISC DHCP 4.3.6.
>
> The commit implementing this is
> https://gitlab.isc.org/isc-projects/dhcp/commit/3e88222f1c2f7a365b9
On 31.07.19 00:20, Thomas Lange wrote:
> First I can confirm this bug. Some time ago I had two servers which
> caused a huge amount of dhcp requests to log the DHCP server (managed
> by a different departement). They told me one server did 30 requests
> per seconds.
> I've looked at the CentOS 8
On 28.07.19 18:53, Andreas Metzler wrote:
> I /think/ setting Before= in *both* .service and .timer is strange.
I think you just need it in the Service. But I am not sure. The
documentation was a bit sparse on that matter. Other times, just as the
apt ones you mentioned have it in both places.
On 19.07.19 07:29, Sven Hartge wrote:
> On 18.07.19 20:01, Sven Hartge wrote:
>> On 17.07.19 20:46, Sven Hartge wrote:
>>
>>> Possible solution (untested): Also create a exim4-base.timer and .service
>>> and
>>> create a Before= dependency on logrota
On 24.07.19 11:13, Tomas Pospisek wrote:
> So my interpretation of your initial bug report, that the VM would DoS
> the host on which it was running via fast changing of IP addresses on
> its interface was completely off the track?
>
> So what you wanted in fact wanted to say by "DoS'ing the
On Tue, 23 Jul 2019 19:32:04 -0600 Mark Hutchison
wrote:
> When I look at systemctl for the dhclient service, I can see that there's
> an error, "can't create /var/lib/dhcp/dhclient.intname.leases Read Only
> file system", and then the DHCPREQUEST > DHCPACK > DHCPDECLINE sequence
> starts every
On 18.07.19 20:01, Sven Hartge wrote:
> On 17.07.19 20:46, Sven Hartge wrote:
>
>> Possible solution (untested): Also create a exim4-base.timer and .service and
>> create a Before= dependency on logrotate.service.
>
> I've whipped up a little Proof-of-Concept to t
On 17.07.19 20:46, Sven Hartge wrote:
> Possible solution (untested): Also create a exim4-base.timer and .service and
> create a Before= dependency on logrotate.service.
I've whipped up a little Proof-of-Concept to test this, available also
at https://salsa.debian.org/hartge-guest/exim
Package: exim4-base
Version: 4.92-8
Severity: minor
Hi!
After upgrading a system to Debian 10 I noticed that the daily e-mail
activity report only contained ~26 minutes from 00:00h to 00:26h, which
is the time I set cron.daily to run at.
Reason: On systems with systemd logrotate is no longer
On Sun, 10 Mar 2019 22:45:56 +0100 Bernhard Schmidt
wrote:
> [CCing the ML, might see a bit more traction there]
>
> On Sat, Feb 23, 2019 at 11:13:14AM +0100, Michael Stapelberg wrote:
>
> > I am orphaning this package effective immediately. I have never personally
> > used
> > FreeRADIUS, and
On 22.06.19 19:58, Sebastian Suchanek wrote:
> - Put a cartridge in the drive
> - Run btape from console: "btape -c /etc/bacula/bacula-sd.con /dev/nst1"
> - Start "fill" test within btape
> - btape writes the name of the volume to the tape, then crashes
> immediately with a kernel panic.
>
Hi.
This bug is the result of a thread from Usenet in
de.comp.os.unix.linux.hardware,de.comp.os.unix.apps.misc with MID:
Grüße,
Sven.
signature.asc
Description: OpenPGP digital signature
On 16.04.19 15:12, Vincent Lefevre wrote:
> access("/var/tmp/mkinitramfs_0BRFs9//etc/fonts/conf.d/60-latin.conf", R_OK) = > 0
> stat("/var/tmp/mkinitramfs_0BRFs9//var/tmp/mkinitramfs_0BRFs9//etc/fonts/conf.d/60-latin.conf",
> 0x7ffc35e33b50) = -1 ENOENT (No such file or directory)
>
On 16.04.19 14:32, Vincent Lefevre wrote:
> On 2019-04-16 01:53:03 +0200, Sven Hartge wrote:
>> Try running the following commands as root:
>>
>> mkdir -p /var/tmp/mkinitramfs_0BRFs9/etc/fonts/conf.d
>> cp -a /etc/fonts/fonts.conf /var/tmp/mkinitramfs_0BRFs9/etc/fonts
Um 01:35 Uhr am 16.04.19 schrieb Vincent Lefevre:
> On 2019-04-15 23:07:02 +0200, Sven Hartge wrote:
>> Could you add "set -x" to the top of
>> /usr/share/initramfs-tools/hooks/plymouth to get a clear picture where
>> exactly the hook fails?
> It is also fc-ca
On Mon, 15 Apr 2019 18:10:18 +0200 Vincent Lefevre
wrote:
> E: Sub-process /usr/bin/dpkg returned an error code (1)
> Setting up initramfs-tools (0.133) ...
> update-initramfs: deferring update (trigger activated)
> Processing triggers for initramfs-tools (0.133) ...
> update-initramfs:
On 31.03.19 00:06, Sven Hartge wrote:
> On 25.03.19 20:25, Sven Hartge wrote:
>> On 24.03.19 02:02, Sven Hartge wrote:
>>
>>> So far, so good. I have your packages running on the main webmail server
>>> and the main web server for my university and so far ever
On Thu, 04 Apr 2019 14:24:40 +0100 Sam Morris wrote:
> # turns out this was a local problem
For the archives: Could you please describe the local problem and the
solution? Because I am having exactly the same problem with plymouth here.
Grüße,
Sven.
signature.asc
Description: OpenPGP
On 25.03.19 20:25, Sven Hartge wrote:
> On 24.03.19 02:02, Sven Hartge wrote:
>
>> So far, so good. I have your packages running on the main webmail server
>> and the main web server for my university and so far everything is fine,
>> while default packages and the test1
On 24.03.19 02:02, Sven Hartge wrote:
> So far, so good. I have your packages running on the main webmail server
> and the main web server for my university and so far everything is fine,
> while default packages and the test1 packages with mpm_event would
> normally start showing
On 22.03.19 21:19, Sven Hartge wrote:
> On 22.03.19 21:14, Stefan Fritsch wrote:
>
>> Second try with different approach is at
>>
>> https://people.debian.org/~sf/apache2-mpm-event-902493/2.4.25-3+deb9u7~test2/
>>
>> I have backported mpm_event
On 22.03.19 21:14, Stefan Fritsch wrote:
> Second try with different approach is at
>
> https://people.debian.org/~sf/apache2-mpm-event-902493/2.4.25-3+deb9u7~test2/
>
> I have backported mpm_event from 2.4.28 and reverted one commit that was
> incompatible with 2.4.25. This was quite painless
Um 08:56 Uhr am 11.03.19 schrieb Sven Hartge:
> I am going to test these package on the systems which have shown to be
> hit by regularly this problem here, so I am confident I will be able to
> report within two weeks if there have been any problems and if your
> change di
On 10.03.19 12:51, Stefan Fritsch wrote:
> I am not comfortable with switching to mpm_worker, either, since this would
> be
> a significant behavior change.
>
> I have however tried a backport of the patch referenced in the upstream bug
> report and put a build here:
>
>
Package: e2fsprogs
Version: 1.45.0-1
Severity: normal
Hi!
While I like the new fsck-via-LVM-snapshot feature, I think adding lvm2
to Recommends is too agressive here.
On systems not using LVM this will needlessly pull in the whole LVM/DM
machinery, including changes to the initramfs, as long as
On 07.03.19 20:37, Paul Gevers wrote:
> On 03-03-2019 18:31, Carsten Leonhardt wrote:
>> Paul Gevers writes:
>>> On 02-03-2019 15:34, Carsten Leonhardt wrote:
maybe using a trigger can help us:
>>>
>>> This sounds like an idea we should try to implement in dbconfig-common,
>>> to enable
On 03.03.19 18:31, Carsten Leonhardt wrote:
> I haven't used triggers yet so I'm not aware of all the details. If we
> can be sure that the setup will be executed even when no local database
> server will be installed because a remote server is used, then I'm all
> for doing it at the end.
I see
On 03.03.19 14:32, Paul Gevers wrote:
> I rather propose that we accept the current regression of the bacula
> autopkgtest and we fix the situation properly (in autopkgtest and/or
> dbconfig-common) after the buster release.
The right package to fix this is dbconfig, IMHO, because the situation
On 28.02.19 13:59, Paul Gevers wrote:
> On 28-02-2019 13:55, Sven Hartge wrote:
>> While I try something to that effect: Maybe the test definition needs
>> something like Pre-Depends:? To allow forcing a certain order where the
>> normal dependencies are not sufficient?
&
Package: autopkgtest
Version: 5.10
Severity: whishlist
Hi!
This is a follow-up to
https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=923444#35
The bacula package has the following debian/test/control file:
Tests: backup-test, program-test
Restrictions: breaks-testbed needs-root
Depends:
Um 13:30 Uhr am 28.02.19 schrieb Paul Gevers:
> Ack. So for whatever reason the order used to work, but now it doesn't
> anymore. There is no mechanism to force the order. So, how to fix this
> in the autopkgtest? Could you check if the database exists and if not,
> trigger reconfig of bacula at
On 28.02.19 13:30, Paul Gevers wrote:
> Ack. So for whatever reason the order used to work, but now it doesn't
> anymore. There is no mechanism to force the order. So, how to fix this
> in the autopkgtest? Could you check if the database exists and if not,
> trigger reconfig of bacula at the
1 - 100 of 492 matches
Mail list logo
