On Tue, Mar 12, 2024 at 07:54:52PM +0100, Valentin Vidic wrote:
> On Mon, Jan 01, 2024 at 07:57:38PM +0100, Paul Gevers wrote:
> > 47s === mount ===
> > 47s mount.ocfs2: Internal logic failure while mounting /dev/loop0 on /mnt.
> > Check 'dmesg' for more information on th
On Mon, Jan 01, 2024 at 07:57:38PM +0100, Paul Gevers wrote:
> 47s === mount ===
> 47s mount.ocfs2: Internal logic failure while mounting /dev/loop0 on /mnt.
> Check 'dmesg' for more information on this error 22.
> 47s umount: /mnt: not mounted.
Thanks for the report, I'm seeing the same
Package: wnpp
Severity: wishlist
Owner: Valentin Vidic
X-Debbugs-Cc: debian-de...@lists.debian.org
* Package name: glome
Version : 0.1
* URL : https://github.com/google/glome
* License : Apache-2.0
Programming Lang: C
Description : Generic Low Overhead
@@
+crmsh (4.4.1-1+deb12u1) bookworm; urgency=medium
+
+ * d/postinst: create a logging directory (Closes: #1042448)
+ * d/patches: add patch for log file error
+
+ -- Valentin Vidic Sun, 29 Oct 2023 20:46:13 +0100
+
crmsh (4.4.1-1) unstable; urgency=medium
[ Bas Couwenberg ]
diff -Nru cr
On Sat, Jan 27, 2024 at 01:56:40PM +0100, wf...@debian.org wrote:
> Indeed, parallax.run was added only in version 1.0.7 by
> https://github.com/krig/parallax/commit/38bac0eb3cb20e9df8cbbf585cf9353793ffdba2.
Thanks, it seems the watch file for parallax did not find new versions
so we are behind
08:57:59.0 +0100
+++ pcs-0.11.5/debian/changelog 2023-11-05 16:27:07.0 +0100
@@ -1,3 +1,9 @@
+pcs (0.11.5-1+deb12u1) bookworm; urgency=medium
+
+ * d/patches: add fix for resource move (Closes: #1042893)
+
+ -- Valentin Vidic Sun, 05 Nov 2023 16:27:07 +0100
+
pcs (0.11.5-1
a logging directory (Closes: #1042448)
+ * d/patches: add patch for log file error
+
+ -- Valentin Vidic Sun, 29 Oct 2023 20:46:13 +0100
+
crmsh (4.4.1-1) unstable; urgency=medium
[ Bas Couwenberg ]
diff -Nru crmsh-4.4.1/debian/control crmsh-4.4.1/debian/control
--- crmsh-4.4.1/debian/control 2023
On Wed, Oct 25, 2023 at 08:00:43AM +0100, Chris Lamb wrote:
> Hm, after fiddling for a few minutes I can't quite work it out. What
> happens when you build it locally?
Locally I also don't see these files being created, so the updated
package has the same contents as version in unstable.
--
On Mon, Oct 02, 2023 at 02:29:34PM +0200, Chris Lamb wrote:
> Whilst working on the Reproducible Builds effort [0], we noticed that
> dacite could not be built reproducibly.
>
> This is because it shipped a bunch of nondeterminstic ~temporary build
> files in the binary package, such as
On Sun, Oct 22, 2023 at 11:38:56PM +0200, Daniel Smolik wrote:
> But when use local heartbeat mode I can mount ocfs but not work in cluster
> mode. I mean that without global heartbeat you didn't have shared storage.
If I understand correctly with local heartbeat there is one heartbeat
running
On Sun, Oct 22, 2023 at 12:11:19PM +0200, Daniel Smolik wrote:
> Yes no problem. There it is.
Thanks. My best guess is that the problem happens because the region
UUID is visible on both drbd and the lower device, so the global
heartbeat might work if drbd device is selected first (for example in
On Sat, Oct 21, 2023 at 11:19:50PM +0200, Dan Smolik wrote:
> in virtual enviroment I try build 2 node ocfs cluster. When drbd
> device is on top of md device all works. But when drbd device is on
> top LVM device global heartbeat doesn't start.
>
> Using config file '/etc/ocfs2/cluster.conf'
On Wed, Oct 11, 2023 at 01:34:08PM +0200, Florent Carli wrote:
> This bug report is about bookworm (stable) version, so the fact that it has
> been fixed in unstable is nice, but should not resolve this.
> Since it's about a real regression, I think this fix should be eligible for
> a backport
On Sun, Sep 10, 2023 at 10:23:21AM -0700, tony mancill wrote:
> I also don't have access to the hardware to test it. My assumption is
> that upstream would see bug reports if the race condition still exists,
> but that's merely conjecture on my part.
>
> Do you have any concerns with an upload
On Thu, Sep 07, 2023 at 07:55:56PM -0700, tony mancill wrote:
> Thank you for the bug report. My initial instinct is to use the same
> unit file and service dependencies as upstream. Looking at the history
> of Debian's patch [2] of the unit file, and specifically this commit
> [3], it appears
Package: lxc
Version: 1:5.0.2-1
Severity: normal
Dear Maintainer,
After the upgrade to bookworm starting ephemeral container with lxc-copy
command always fails with an error:
# lxc-copy -n autopkgtest-sid -e -l TRACE
Created autopkgtest-sid_uFBocY as clone of autopkgtest-sid
lxc-copy:
@@
+resource-agents (1:4.12.0-2) unstable; urgency=medium
+
+ * debian/patches: add IPv6addr-delay.patch (Closes: #1034280)
+ * debian/patches: refresh patches offsets
+
+ -- Valentin Vidic Thu, 13 Apr 2023 21:43:52 +0200
+
resource-agents (1:4.12.0-1) unstable; urgency=medium
* New upstream
I just did a quick check and the tools work for me on the current stable
(11.6) and unstable.
The only time they don't start is when X11 is not available like in an ssh
session:
$ java -verbose:class -jar
/usr/share/java/airport-utils/AirportBaseStationConfig.jar
...
[0.170s][info][class,load]
Package: stockfish
Version: 14.1-1
Severity: normal
Dear Maintainer,
New version has been released this year:
2022-04-18: Stockfish 15
Please update the package for bookworm release :)
--
Valentin
I checked pcs 0.10.1-2 in buster and it turns out it is not vulnerable
to CVE-2022-2735. Separate ruby daemon with a world writable UNIX socket
was introduced later in 0.10.5:
https://salsa.debian.org/ha-team/pcs/-/commits/master/pcsd/pcsd-ruby.service.in
Before that version python code runs
Package: ftp.debian.org
Severity: normal
Upstream repo contains the following notice:
https://github.com/ClusterLabs/fence-virt
fence-virt has moved to https://github.com/ClusterLabs/fence-agents
as source of the fence-virt package has been merged into fence-agents.
As a maintainer of both
On Sun, Mar 13, 2022 at 03:19:55PM +0100, Valentin Vidic wrote:
> Thanks for the report, I will try to reproduce the problem with the
> versions in unstable, but it would be good if you could share the errors
> that are being reported and perhaps also the cluster configuration for
>
On Fri, Mar 11, 2022 at 06:45:32PM -0300, Dayvison wrote:
> Package: ocfs2-tools
> Version: 8.7.1 and 8.6.6
>
> Hi, I'm sending this email to report a problem:
>
> OCFS2 filesystem with more than 1 node is not working with Debian 11
> with 5.13, 5.15 and newer kernels.
>
> OK, what's the
On Sat, Feb 19, 2022 at 06:59:58PM +, Adam D. Barratt wrote:
> Please go ahead.
Thanks, just uploaded.
--
Valentin
On Wed, Jan 19, 2022 at 02:11:24PM -0700, Ben Fiedler wrote:
> I would guess that either linux-image or drbd-utils packages need to
> be updated to include and reference a newer module (drbd9.ko)?
I don't think drbd9 kernel module is currently included in Debian, so
you would need to build it
Package: release.debian.org
Severity: normal
User: release.debian@packages.debian.org
Usertags: transition
Hello Release Team,
We would like to transition libwebp to a new upstream version 1.2.1-1
that is already uploaded and built in experimental. No build problems
are expected in the
On Mon, Dec 20, 2021 at 06:23:38PM +, Adam Thorn wrote:
> Could the fix from 3.0.6-12, which distributes
>
> /usr/lib/tmpfiles.d/heartbeat.conf
>
> as part of the deb, be backported/released for bullseye please?
Yes, I have opened #1002051 to request heartbeat update in bullseye.
--
+
+ * Use tmpfiles.d to create /run/heartbeat (Closes: #1002037)
+
+ -- Valentin Vidic Mon, 20 Dec 2021 23:51:42 +0100
+
heartbeat (1:3.0.6-11) unstable; urgency=medium
[ Debian Janitor ]
diff -Nru heartbeat-3.0.6/debian/heartbeat.postinst
heartbeat-3.0.6/debian/heartbeat.postinst
--- heartbeat
Hi Paul,
On Thu, Sep 16, 2021 at 08:34:06AM +0200, Paul Gevers wrote:
> It was pointed out to me on IRC that the mount of /tmp with `nodev` is
> probably the issue here. I'm discussion if we should just drop that.
The failing test does not use a device so this probably won't help. I
tried
On Wed, Sep 15, 2021 at 09:24:08PM +0200, Paul Gevers wrote:
> I looked at the results of the autopkgtest of you package on amd64
> because with a recent upload of glibc the autopkgtest of ocfs2-tools
> fails in testing. It seems to me that the failures are related to the
> worker that the test
On Fri, Sep 03, 2021 at 11:18:08AM +0200, Gael Le Mignot wrote:
> After upgrading from buster to bullseye on several hosts, "heartbeat"
> doesn't start. It tries to create a /run/heartbeat/register socket in
> a non-existing /run/heartbeat/ directory.
Thanks for the report, it seems we have lost
On Sun, Aug 01, 2021 at 09:45:00PM +0200, Valentin Vidic wrote:
> Thanks, that does sound similar to what I was getting there. I will try
> to see if it still happens with the latest installer. And since it
> crashes on start I had no way to access the logs or dmesg of the
> mach
Just to report I don't get the crash anymore with bullseye rc3
installer, so most probably this was the same problem as:
#987368 Installer fails at first menu "Choose language"
--
Valentin
On Sun, Aug 01, 2021 at 05:10:07PM +0200, Cyril Brulebois wrote:
> Valentin Vidic (2021-08-01):
> > No problem, I was not able to reproduce this reliably or get a core
> > dump for this crash. It could just be an emulation problem with qemu
> > or some timing issue for the
On Mon, May 03, 2021 at 06:38:05PM +0200, Samuel Thibault wrote:
> How did you start it? I couldn't manage to make it start (with qemu from
> unstable or from stable), I only got the kernel start and a couple of
> lines. I was taking
>
>
On Mon, May 03, 2021 at 08:36:58AM +0200, Cyril Brulebois wrote:
> Also adding to the list of bugs to keep an eye on (again, possibly not
> blocking the release on its being resolved; we could have the issue
> listed in errata, and possibly fixed in a point release).
Thanks, here is another one
On Mon, May 03, 2021 at 09:16:03AM +0200, Cyril Brulebois wrote:
> Do we have any idea whether that could be something that's only
> triggered within QEMU (maybe try other QEMU versions?), or something
> that affects bare metal systems?
I don't have access to real s390x hardware, but I tried to
Source: linux
Version: 5.10.28-1
Severity: normal
Dear Maintainer,
Debian installer for bullseye fails to find any disks for installation
due to a missing module for virtio block device. Merge request for
including virtio_blk (and other standard scsi modules) is here:
On Mon, May 03, 2021 at 08:58:02AM +0200, John Paul Adrian Glaubitz wrote:
> > The same issue exists on s390x but isn't apparently going to get fixed
> > so we need to have d-i be smarter (hence the merge request)?
>
> Seems so.
QEMU console might get fixed in the kernel, but it looks like LPAR
Hi,
Probably not critical, but maybe these installation bugs on s390x could
be fixed for the release?
rootskel: steal-ctty no longer works on at least sparc64
https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=926539
debian-installer: qemu-system-s390x installation fails due to segfault in
Package: debian-installer
Severity: important
Dear Maintainer,
Running the installation inside a QEMU instance does not work in bullseye:
$ virt-install --arch=s390x --name test --memory 1024 --disk none -l
http://ftp.de.debian.org/debian/dists/bullseye/main/installer-s390x/
...
ested the patch for rootskel (also attached here for
review):
https://salsa.debian.org/installer-team/rootskel/-/merge_requests/2/diffs
--
Valentin
>From bbe911902ce1f3001efb8dac3302d17a332e3f87 Mon Sep 17 00:00:00 2001
From: Valentin Vidic
Date: Sun, 17 May 2020 14:39:18 +0200
Subject: [PATCH] T
+0200
@@ -1,3 +1,9 @@
+consul (1.8.7+dfsg1-2) unstable; urgency=medium
+
+ * Add patch for CVE-2020-25864 (Closes: #987351)
+
+ -- Valentin Vidic Sat, 24 Apr 2021 12:06:56 +0200
+
consul (1.8.7+dfsg1-1) unstable; urgency=medium
[ Arnaud Rebillout ]
diff -Nru consul-1.8.7+dfsg1/debian/.gitlab
user debian-rele...@lists.debian.org
usertags -1 + bsp-2021-04-AT-Salzburg
thank you
--
Valentin
Package: popularity-contest
Severity: wishlist
Dear Maintainer,
Please update the Croatian translation in the package using the
patch attached below.
Thank you,
Valentin
From 05023c51e4d2b9d6e727fa3477732ec0c23d3d9e Mon Sep 17 00:00:00 2001
From: Valentin Vidic
Date: Fri, 23 Apr 2021 18:20:31
2021-03-27
19:07:26.0 +0100
@@ -1,3 +1,9 @@
+crmsh (4.0.0~git20190108.3d56538-3+deb10u1) buster; urgency=medium
+
+ * d/patches: include fix for CVE-2020-35459 (Closes: #985376)
+
+ -- Valentin Vidic Sat, 27 Mar 2021 19:07:26 +0100
+
crmsh (4.0.0~git20190108.3d56538-3) unstable; urgency
On Thu, Jan 28, 2021 at 03:52:41PM +0100, Paul Gevers wrote:
> Grr. I'm now sure they don't. Although we generate new containers every
> day, it seems that the configuration of those containers in
> /var/lib/lxc/* *doesn't* get refreshed. I have just destroyed all
> containers before creating new
On Thu, Jan 28, 2021 at 09:05:55AM +0100, Paul Gevers wrote:
> We generate fresh containers on a daily basis.
I suppose you can check AppArmor logs, perhaps it is only enabled or
configured differently on this host.
--
Valentin
On Wed, Jan 27, 2021 at 10:37:56PM +0100, Paul Gevers wrote:
> debian@ci-worker-ppc64el-01:~$ sudo cat /etc/lxc/default.conf
> # MANAGED WITH CHEF; DON'T CHANGE BY HAND
> lxc.net.0.type = veth
> lxc.net.0.link = virbr0
> lxc.net.0.flags = up
> lxc.apparmor.profile = generated
>
On Wed, Jan 27, 2021 at 09:56:34PM +0100, Paul Gevers wrote:
> Please see: https://salsa.debian.org/-/snippets/520 Do you seen anything
> weird?
I don't think anything would show up in the mounts on the host itself.
The problem is probably with some of the hardenings enabled in the
corosync
On Sat, Jan 09, 2021 at 06:31:06PM +0100, wf...@niif.hu wrote:
> Not offhand. It certainly failed to start the Corosync daemon (which
> should automatically start after installation, but that's beside the
> point). So there's ample chance this is a Corosync peculiarity after
> all; can't you see
Please include for bullseye release if possible:
cmirrord is the daemon that tracks mirror log information in a cluster.
It is specific to device-mapper based mirrors (and by extension, LVM
cluster mirrors). Cluster mirrors are not possible without this daemon
running.
--
Valentin
On Sat, Dec 05, 2020 at 02:08:16PM +0100, Valentin Vidic wrote:
> Thank you for the report. I'm not sure if this is a supported use case
> for ocfs2 (it is most often used in local cluster setups), but I
> forwarded the request to upstream authors for review:
>
> https://github
On Fri, Nov 20, 2020 at 09:19:52AM +0100, Benoit Panizzon wrote:
> Due to the depletion of ipv4 addresses, more and more services use ipv6 and
> NAT is wiedly in use.
>
> I am also in a situation where there is a central storage reachable via iscsi
> and ipv6 and one
> node has an ipv4 NAT ip
On Mon, Nov 23, 2020 at 11:46:54AM +0100, Matthias Klose wrote:
> Package: src:fence-agents
> Version: 4.6.0-2
> Severity: serious
> Tags: sid bullseye
> User: debian-pyt...@lists.debian.org
> Usertags: python3.9
>
> fence-agents autopkg tests time out, might not be Python 3.9 specific.
Yup,
One of autopkgtests in fence-agents package seems to be broken
in the same way - just hangs in wait forever and using bash works:
https://salsa.debian.org/ha-team/fence-agents/-/blob/master/debian/tests/delay
--
Valentin
On Mon, Oct 19, 2020 at 08:57:37PM +0200, Paul Gevers wrote:
> Your package dlm has an autopkgtest, great. However, I believe that it
> should fail as the messages in the log suggest the test didn't succeed.
> Failing autopkgtests are RC. Please fix your autopkgtest.
Yes, unfortunately dlm
Package: wnpp
Severity: wishlist
Owner: Valentin Vidic
* Package name: osmid
Version : 0.8.0
Upstream Author : Luis Lloret
* URL : https://github.com/llloret/osmid
* License : MIT
Programming Lang: C++
Description : tool to convert MIDI to OSC and OSC
On Mon, Sep 14, 2020 at 01:35:24PM +0200, Dominik Klein wrote:
> we installed libknet1 from buster-backports and this fixed the described
> problem.
Great, thanks for confirming this is a knet issue.
--
Valentin
On Fri, Sep 11, 2020 at 11:45:54AM +0200, Valentin Vidic wrote:
> This might be a knet problem. Can you test if just installing knet
> libs from backports with corosync 3.0.1-2+deb10u1 solves the issue
> you are seeing?
Also knet update for buster has not been approved yet, but can b
On Fri, Sep 11, 2020 at 11:22:19AM +0200, Eugen Wick wrote:
> * Tests with Corosync 3.0.3 from debian testing.
> We installed packages from debian testing and fulfilled dependencies from
> debian backports.
>
> #
> apt install libnozzle1=1.16-2~bpo10+1
Package: gem2deb-test-runner
Version: 1.2.1
Severity: normal
Dear Maintainer,
It seems that gem2deb-test-runner calls dpkg-parsechangelog but does
not depend on dpkg-dev as shown by this failing test created by
autopkgtest-pkg-ruby:
autopkgtest [20:40:28]: test command1: gem2deb-test-runner
On Thu, Jul 02, 2020 at 09:04:10PM +0100, Adam D. Barratt wrote:
> Thanks for the quick explanation. Please go ahead.
Thank you, just uploaded.
--
Valentin
On Thu, Jul 02, 2020 at 08:51:39PM +0100, Adam D. Barratt wrote:
> I assume these changes are no-ops, but why are they included? They
> don't appear to actually relate to the issue - the first two even more
> so.
Right, the IP2UTIL change is not strictly needed but I preferred to use
the upstream
Package: wnpp
Severity: wishlist
Owner: Valentin Vidic
* Package name: ruby-sys-proctable
Version : 1.2.5
Upstream Author : Daniel J. Berger
* URL : https://github.com/djberg96/sys-proctable
* License : Apache-2.0
Programming Lang: Ruby
Description
Package: wnpp
Severity: wishlist
Owner: Valentin Vidic
* Package name: ruby-aubio
Version : 0.3.3
Upstream Author : Xavier Riley
* URL : https://github.com/xavriley/ruby-aubio
* License : MIT
Programming Lang: Ruby
Description : Ruby bindings
Package: wnpp
Severity: wishlist
Owner: Valentin Vidic
* Package name: ruby-rubame
Version : 0.0.2
Upstream Author : Mark Saward
* URL : https://github.com/saward/Rubame
* License : MIT
Programming Lang: Ruby
Description : simple Ruby websocket game
)
+
+ -- Valentin Vidic Sat, 27 Jun 2020 13:26:42 +0200
+
resource-agents (1:4.2.0-2+deb10u1) buster; urgency=medium
* debian/patches: drop xen-toolstack.patch
diff -Nru resource-agents-4.2.0/debian/patches/ipsrcaddr-proto.patch
resource-agents-4.2.0/debian/patches/ipsrcaddr-proto.patch
--- resource
Package: pacemaker-dev
Version: 2.0.4-2
Severity: normal
Dear Maintainer,
The following two dependencies seem to be missing after installing
pacemaker-dev on a clean build system:
$ pkg-config --exists --print-errors libpacemaker
Package ncurses was not found in the pkg-config search path.
On Mon, Jun 08, 2020 at 12:29:35PM +0200, Alberto Gonzalez Iniesta wrote:
> Some weeks ago I upgraded corosync (3.0.1-2 -> 3.0.1-2+deb10u1) and
> started to notice these messages in my nodes (two node cluster):
> Jun 2 01:10:13 patty corosync[2346]: [KNET ] link: host: 2 link: 0 is down
> Jun
Package: cyrus-admin
Version: 3.0.8-6+deb10u4
Severity: normal
Dear Maintainer,
The sieveshell command does not work correctly after the quit command:
$ sieveshell localhost
connecting to localhost
Please enter your password:
> list
main <- active script
> quit
> list
Segmentation fault
Package: debian-installer
Version: 20190702+deb10u4
Severity: important
Dear Maintainer,
Installer initrd does not include modules virtio_blk and virtio_net
(+dependencies) preventing a successful installation inside a QEMU VM:
$ virt-install --arch=s390x --name test --memory 1024 --disk
Package: debian-installer
Version: 20190702+deb10u4
Severity: important
Dear Maintainer,
Running the installation inside a QEMU instance does not work in buster:
$ virt-install --arch=s390x --name test --memory 1024 --disk none \
--extra-args=console=ttyS0 \
-l
runlevels for corosync-qdevice (Closes:
#932346)
+
+ -- Valentin Vidic Tue, 07 Apr 2020 23:10:01 +0200
+
corosync-qdevice (3.0.0-4) unstable; urgency=medium
* [c680521] Revert "Require pacemaker for qdevice autopkgtest"
diff -Nru corosync-qdevice-3.0.0/debian/corosync-qdevice.init
corosy
-g175a01c/debian/changelog 2016-10-23 15:38:46.0
+0200
+++ csync2-2.0-8-g175a01c/debian/changelog 2020-04-05 15:26:41.0
+0200
@@ -1,3 +1,9 @@
+csync2 (2.0-8-g175a01c-4+deb9u1) stretch; urgency=medium
+
+ * Add patch for CVE-2019-15522 (Closes: #955445)
+
+ -- Valentin Vidic
-gce67c55/debian/changelog 2018-10-06 23:05:46.0
+0200
+++ csync2-2.0-22-gce67c55/debian/changelog 2020-04-05 12:55:07.0
+0200
@@ -1,3 +1,9 @@
+csync2 (2.0-22-gce67c55-1+deb10u1) buster; urgency=medium
+
+ * Add patch for CVE-2019-15522 (Closes: #955445)
+
+ -- Valentin Vidic
Package: wnpp
Severity: wishlist
Owner: Valentin Vidic
* Package name: dacite
Version : 1.3.0
Upstream Author : Konrad Hałas
* URL : https://github.com/konradhalas/dacite
* License : MIT
Programming Lang: Python
Description : create data classes from
Package: wnpp
Severity: wishlist
Owner: Valentin Vidic
* Package name: prometheus-hacluster-exporter
Version : 0.4.0
Upstream Author : SUSE
* URL : https://github.com/ClusterLabs/ha_cluster_exporter
* License : GPL-3
Programming Lang: Go
Description
Package: lintian
Version: 2.42.0
Severity: normal
Dear Maintainer,
Last version of lintian fails to check resource-agents package with runtime
error:
https://salsa.debian.org/ha-team/resource-agents/-/jobs/475012
Can't use an undefined value as an ARRAY reference at
Package: bgpdump
Version: 1.6.0-1
Severity: grave
Dear Maintainer,
The program segfaults when started:
$ bgpdump
Segmentation fault
Based on gdb info it seems like the call to log_to_stderr fails:
(gdb) bt
#0 0x2246 in ?? ()
#1 0x77fef5cf in main ()
(gdb) disas main
Package: wnpp
Severity: wishlist
Owner: Valentin Vidic
* Package name: fence-virt
Version : 0.9.0
Upstream Author : Red Hat, Inc.
* URL : https://github.com/ClusterLabs/fence-virt
* License : GPLv2
Programming Lang: C
Description : Pluggable fencing
Package: wnpp
Severity: wishlist
Owner: Valentin Vidic
* Package name: google-auth-httplib2
Version : 0.0.3
Upstream Author : Google Cloud Platform
* URL :
https://github.com/GoogleCloudPlatform/google-auth-library-python-httplib2
* License : Apache 2.0
patch for removing fence_amt_ws (Closes: #934519)
+
+ -- Valentin Vidic Sun, 29 Sep 2019 12:27:01 +0200
+
fence-agents (4.0.25-1+deb9u1) stretch; urgency=medium
* fence_rhevm: add patch for CVE-2019-10153 (Closes: #930887)
diff -Nru fence-agents-4.0.25/debian/patches/remove-fence_amt_ws
fence
fence_amt_ws (Closes: #934519)
+
+ -- Valentin Vidic Sun, 29 Sep 2019 11:54:16 +0200
+
fence-agents (4.3.3-2) unstable; urgency=high
* fence_rhevm: add patch for CVE-2019-10153 (Closes: #930887)
diff -Nru fence-agents-4.3.3/debian/patches/remove-fence_amt_ws
fence-agents-4.3.3/debian/patches
On Thu, Sep 05, 2019 at 11:42:18AM +0200, Ervin Hegedüs wrote:
> Now looks like this works:
>
> # diff -ruN ocfs2.service /lib/systemd/system/ocfs2.service
> --- ocfs2.service 2019-09-04 14:43:55.613155935 +0200
> +++ /lib/systemd/system/ocfs2.service 2019-09-05 10:59:12.552486408 +0200
> @@
/patches: add zfs-bashism.patch (Closes: #933398)
+
+ -- Valentin Vidic Sun, 04 Aug 2019 09:59:39 +0200
+
resource-agents (1:4.2.0-2) unstable; urgency=medium
* debian/rules: fix build with merged-usr (Closes: #915848)
diff -Nru resource-agents-4.2.0/debian/patches/ethmonitor-no-addr.patch
-30 19:01:55.0
+0200
@@ -1,3 +1,9 @@
+fence-agents (4.0.25-1+deb9u1) stretch; urgency=medium
+
+ * fence_rhevm: add patch for CVE-2019-10153 (Closes: #930887)
+
+ -- Valentin Vidic Sun, 30 Jun 2019 19:01:55 +0200
+
fence-agents (4.0.25-1) unstable; urgency=medium
* Team upload
+
+ -- Valentin Vidic Wed, 08 May 2019 10:55:44 +0200
+
sbd (1.4.0-1) unstable; urgency=medium
* New upstream version 1.4.0
diff -Nru sbd-1.4.0/debian/patches/pidfile-in-runstatedir.patch
sbd-1.4.0-18-g5e3283c/debian/patches/pidfile-in-runstatedir.patch
--- sbd-1.4.0/debian/patches/pidfile
On Mon, Mar 25, 2019 at 03:45:58PM +0100, Andreas Beckmann wrote:
> In that case you should probably add Breaks+Replaces against all of the
> old -dev packages that were merged, just to be on the safe side.
Yes, that is the plan. I think wferi will take care of it if he
has time?
--
Valentin
On Sat, Mar 23, 2019 at 05:19:59PM +0100, Andreas Beckmann wrote:
> during a test with piuparts I noticed your package fails to upgrade from
> 'wheezy' to 'jessie' to 'stretch' to 'buster'.
> It installed fine in 'wheezy', and upgraded to 'jessie' and 'stretch'
> successfully,
> but then the
On Tue, Feb 19, 2019 at 10:26:09AM +0100, Christoph Martin wrote:
> What can we do to not loose these packages (burp in my case)?
>
> librsync 2.0.2-1~exp1 was uploaded to experimental three days ago.
csync2 seems to build fine with librsync2 from experimental so if
you can upload that to
On Tue, Feb 19, 2019 at 10:26:09AM +0100, Christoph Martin wrote:
> What can we do to not loose these packages (burp in my case)?
>
> librsync 2.0.2-1~exp1 was uploaded to experimental three days ago.
I guess librsync2 would need to go into unstable and testing. Than
we can try to update our
Hi,
Not sure why grave so late in the release process that we lose
some packages (csync2 in my case)? grave after the release would
give us more time to move to librsync2.
--
Valentin
On Sun, Feb 03, 2019 at 08:53:03PM +0100, Paul Gevers wrote:
> Currently this regression is blocking the migration of corosync to
> testing [1]. Due to the nature of this issue, I filed this bug report
> against both packages. Can you please investigate the situation and
> reassign the bug to the
On Thu, Jan 24, 2019 at 10:27:39PM +0100, Valentin Vidic wrote:
> Password file indeed seems to be empty on stretch:
>
> drwxr-x--- 2 root coroqnetd 4096 Jan 24 22:22 .
> drwxr-xr-x 3 root root 4096 Jan 24 22:22 ..
> -rw-r- 1 root coroqnetd 65536 Jan 24 22:22 cert8.db
On Sun, Jan 20, 2019 at 05:07:25PM +0100, Andreas Beckmann wrote:
> Setting up corosync-qnetd (3.0.0-1) ...
> password file contains no data
> Invalid password.
> certutil: Could not set password for the slot: SEC_ERROR_INVALID_ARGS:
> security library: invalid arguments.
> dpkg: error
On Fri, Jan 11, 2019 at 12:32:05AM +0530, Pirate Praveen wrote:
> Package: pcs
> Version: 0.9.166-5
> Severity: serious
>
> https://ci.debian.net/packages/p/pcs/unstable/amd64
>
> May be 0.10 version has a fix, it is delaying rails 5 testing
> migration, so please fix it.
Yep, I'm looking at
Package: lvm2-lockd
Version: 2.03.01-2
Severity: normal
Dear Maintainer,
I understand that clvm is replaced by lvm2-lockd in version 2.03,
but please include cmirrord as it is still needed for pvmove to
work in clustered environment.
-- System Information:
Debian Release: buster/sid
APT
Could we have this fixed in a stable update?
--
Valentin
Package: apache2
Version: 2.4.37-1
Severity: wishlist
Dear Maintainer,
Since apache2 Provides httpd it would be nice to make a systemd
Alias for httpd:
# systemctl restart httpd
Failed to restart httpd.service: Unit httpd.service not found.
This would make apache2 a bit more compatible
1 - 100 of 275 matches
Mail list logo
