In the following bug:
https://bugs.launchpad.net/ubuntu/+source/mstflint/+bug/1470167
There is a direct request from Mellanox for Ubuntu to sync "mstflint"
package with Debian.
While that is okay for Xenial, after bisecting mstflint code with
ConnectX-4 HBAs, I could see the exact commit that br
Hello Paolo,
I'm looping the kernel team mailing list,just in case, that might help
in the discussion.
Best,
Rafael
On Thu, Jul 18, 2019 at 9:12 AM Paolo Valente wrote:
>
> Hi,
> this is basically to report outdated statements in your wiki page on
> I/O schedulers [1].
>
> The main problematic
afaiu block-proposed tags on bugs are not specific to any series, so you are
blocking updates across all series. Not really desired.
Following the thread you started, it seems that we can all agree to use
block-proposed- instead. Does this resolve your concern?
On Wed, Aug 28, 2019 at 09:24:10
On 11/16/19 5:25 PM, Robert Matusewicz wrote:
> Hi,
>
> I'm new in Ubuntu world and I need advice on how to proceed with a bugfix
> for Guake package. There is a bug #1760621 [1]. It's about Guake freezing
> when libutemper is not installed on the system and user tries to close a
> tab. From what I
Hello,
As many as you know I'm currently revamping Ubuntu High Availability
Packages
For 20.04, considered HA (or HA related) packages are:
- Core packages:
- libqb
- kronosnet
- corosync
- pacemaker
- resource-agents
- fence-agents
- crmsh
- cluster-glue
- drbd-utils
- dlm
TL;DR version for this and the previous e-mail:
* Please help selecting resource and fence agents we should support *
1) By *support* I mean.. leave fully supported agents in [main], for 20.10, and
move the ones that shall get community support, or best effort support, into
[universe].
2) For 20
> -Original Message-
> From: Felipe Reyes
>
> >
> > - "Deprecated" packages:
> >
> > - heartbeat
> > - keepalived
>
> keepalived is used by OpenStack Neutron. In this context what would
> "deprecated" mean?.
>
> apt-rdepends -r keepalived
> Reading package lists... Done
> Building d
> I added a few comments below but I must admit that I didn't completely
> get what you want.
I'm sorry then, let me try to explain better...
> The list includes so many things, what are you expecting:
> - if they are important overall?
> - if they are important for HA cases?
> - if they should b
> I added a few comments below, otherwise all the categories look
> reasonable to me, thanks!
Thanks for the feedback Dan!
> > clvm- clvmd daemon (cluster logical vol manager)
>
> Was clvm dropped from lvm2?
> https://launchpad.net/ubuntu/+source/lvm2/2.03.02-2ubuntu1
> I hav
> I'm not sure where exactly this Xen resource agent should be placed on
> the list -- but in practice, Xen wasn't in main, and that may influence
> your thinking.
I'll follow @cpaelzer's suggestion and keep it in "best effort". No hard
commitment as it is in [universe], but at least some commitm
> > > > pgsql - pgsql database instance
> > >
> > > shouldn't this be in fully supported?
> >
> > Pgsql is in [universe]. Unless SEG supports pgsql "by default", do you ?
>
> We're talking about postgresql right? It's definitely supported (it's
> in main), and from a quick look
, at least until I split all agents
into more packages.
I'm creating another discourse for fencing-agents as well, same thing.
Please give me your +1 if possible, and feel free to -1 with suggestions.
Cheers,
-rafaeldtinoco
On 07/04/2020 23:47, Rafael David Tinoco wrote:
>> I added a
On 29/04/2020 00:10, Rafael David Tinoco wrote:
> Dan, Billy,and all...
>
> part of the result from this thread is at:
>
> https://discourse.ubuntu.com/t/ubuntu-ha-pacemaker-resource-agents-supportability/
> <https://discourse.ubuntu.com/t/ubuntu-ha-pacemaker-resource-agents
Forwarding to Ubuntu Devel Mailing list for broader audience.
Should I just open a [RM] bug for all Ubuntu versions ? Any thoughts ?
-rafaeldtinoco
On 07/05/2020 19:01, Lance Albertson wrote:
> I think removing it from Debian is the safe way to go currently. If
> you want assistance with how we
Hello list,
I have been working in merging open-iscsi package:
https://salsa.debian.org/rafaeldtinoco-guest/open-iscsi/-/commits/experimental
with open-iscsi project upstream:
https://github.com/open-iscsi/open-iscsi/
and also cleaning up the open-iscsi package a bit (thus will have to
give sp
On 29/05/2020 01:38, Bryce Harrington wrote:
> Two alternate approaches I'm weighing are a config file in /etc, or just
> a package patch to carry in coreutils, but the env var approach feels
> like it would be more flexible to users and hopefully more suitable for
> upstream. Before I forward it
On 29/05/2020 11:03, Robie Basak wrote:
> +1 for Bryce's approach.
>
> On Fri, May 29, 2020 at 10:56:34AM -0300, Rafael David Tinoco wrote:
>> Perhaps this environment variable should be set by snapd package ?
> I think this could be surprising - because we would b
This was my week and here is some of my notes about achievements and
highlights:
Overall status:
--
- read all the maint+1 docs and @piloted in ubuntu-devel
- qemu TCG memory issue causing spinned qemu instances to be killed
casper has a qemu instance killed because of TCG (cdrom file cant
Hello Everyone,
I would like to ask you to join me and welcome Erich Eickmeyer as the
newest member of MOTU.
Erich,
Thank you for your hard work and congratulations on the achievement!
My very best regards in name of Ubuntu Dev Memb Board,
-rafaeldtinoco
Original Message
Fro
Hello Everyone,
I would like to ask you to join me and welcome Paride Legovini as the
newest member of the Server Dev Team.
Paride,
Thank you for your hard work and congratulations on the achievement!
My very best regards in name of Ubuntu Dev Memb Board,
-rafaeldtinoco
Original Mess
Hello devs...
Some of you know, I have been developing a tool called "conntracker" at
https://github.com/rafaeldtinoco/conntracker. While developing it, I have faced
many "issues" regarding iptables differences among Bionic and Focal/Groovy and
I would like to confirm one behavior I observed t
> This means that the POLICY has acted in all those table/chains
> combination, NOT the rules I have in place. So, if I change the default
> policy using iptables-legacy to -j DROP... then my iptables-nft rules
> don't work at all. This means that one should really use
> iptables-legacy (and no
OK.. I think I found the issue... sorry for the noise.
TL/DR version:
all the iptables targets working in compatibility mode (-j NFLOG, -j TRACE,
etc) might face issues and not work correctly when using nf-tables by default
(nft_compat -> x_tables over nftables).
Explanation:
If I execute m
Hello list,
I have been trying to address this issue for sometime now, without success.
Hopefully this can gain some traction with this e-mail. I know many of you
address most of your efforts into the current development version, but I'd like
to call attention for something I judge is important
>> - #1 = Ubuntu HWE kernels aren't being compiled with BTF support, something
>> that is critical for eBPF CO-RE, turning an eBPF object portable among
>> different kernel versions.
>>
>> https://github.com/aquasecurity/btfhub/issues/9
>> https://bugs.launchpad.net/ubuntu/+source/linux/+bug/19
25 matches
Mail list logo
