** Changed in: mailman-hyperkitty (Ubuntu)
Assignee: Ubuntu Security Team (ubuntu-security) => (unassigned)
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1820205
Title:
[MIR] mailman-hyperkitty
** Changed in: python-aiosmtpd (Ubuntu)
Assignee: Ubuntu Security Team (ubuntu-security) => (unassigned)
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1820212
Title:
[MIR] python-aiosmtpd as de
** Changed in: zope.hookable (Ubuntu)
Assignee: Ubuntu Security Team (ubuntu-security) => (unassigned)
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1820237
Title:
[MIR] zope.hookable as depend
** Changed in: zope.configuration (Ubuntu)
Assignee: Ubuntu Security Team (ubuntu-security) => (unassigned)
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1820234
Title:
[MIR] zope.configuration
I've tried. It's still happening.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1827884
Title:
Boot problems after upgrade to kernel 4.15.0-48 (18.04.2LTS/i386)
To manage notifications about this b
Public bug reported:
fails to build after kernel update.
ProblemType: Package
DistroRelease: Ubuntu 16.04
Package: nvidia-340 340.107-0ubuntu0.16.04.2
ProcVersionSignature: Ubuntu 4.4.0-154.181-generic 4.4.179
Uname: Linux 4.4.0-154-generic x86_64
NonfreeKernelModules: nvidia_uvm nvidia
.proc.dri
** Description changed:
This bug will contain status and test results related to a kernel source
(or snap) as stated in the title.
For an explanation of the tasks and the associated workflow see:
https://wiki.ubuntu.com/Kernel/kernel-sru-workflow
backports: bug 1834950 (xenial/li
Public bug reported:
[31493:31493:0702/222647.438796:ERROR:sandbox_linux.cc(368)]
InitializeSandbox() called with multiple threads in process gpu-process.
[31449:31473:0702/222647.632779:ERROR:browser_process_sub_thread.cc(221)]
Waited 59 ms for network service
Opening in existing browser sessio
As far as I can tell, these crashes seem to be unrelated to the latest
change due to Reiwa.
@Nobuhiro: Is the existence of such crashes something you are aware of?
Is it possibly a reason to look at a newer upstream version?
--
You received this bug notification because you are a member of Ubunt
Alexander, please see bug 1550779 for that.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1758512
Title:
No virtual terminals (CTRL+ALT+F?) when no user logged in; erratic
behaviour when user logg
I inserted the word spinning per comment #6 :)
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1835033
Title:
gnome-shell frozen and spinning in g_type_check_instance_cast() from
meta_window_x11_is_
If the main problem is getting logged out then:
Thank you for taking the time to report this bug and helping to make
Ubuntu better. It sounds like some part of the system has crashed. To
help us find the cause of the crash please follow these steps:
1. Look in /var/crash for crash files and if fo
Although this bug is only about decoding support, I'd like to leave a note
about the rendering: AFAIK rendering without any slow copies requires DMABUF
support, so processes can share resources on the GPU.
For the Wayland backend this about to land, see bug 1552590, quote:
> Wayland dmabuf surfa
** Tags removed: fixed-3.33.3
** Tags added: fixed-in-3.33.3
** Changed in: mutter (Ubuntu)
Assignee: Daniel van Vugt (vanvugt) => Marco Trevisan (Treviño) (3v1n0)
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.laun
*** This bug is a duplicate of bug 1812266 ***
https://bugs.launchpad.net/bugs/1812266
Thank you for taking the time to report this bug and helping to make
Ubuntu better. This particular bug has already been reported and is a
duplicate of bug 1812266, so it is being marked as such. Please look
*** This bug is a duplicate of bug 1832317 ***
https://bugs.launchpad.net/bugs/1832317
Thank you for taking the time to report this bug and helping to make
Ubuntu better. This particular bug has already been reported and is a
duplicate of bug 1832317, so it is being marked as such. Please look
I agree I think this might be a problem unique to gnome-shell-extension-
ubuntu-dock but am yet to confirm...
** Also affects: gnome-shell-extension-ubuntu-dock (Ubuntu)
Importance: Undecided
Status: New
** Changed in: gnome-shell-extension-ubuntu-dock (Ubuntu)
Status: New => Con
Please try attaching that file again with a simpler file name that web
browsers can handle :)
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1834967
Title:
Activities overview doesn't fit the whole w
Thank you for taking the time to report this bug and helping to make
Ubuntu better. Unfortunately, we cannot work on this bug because your
description didn't include enough information. You may find it helpful
to read "How to report bugs effectively"
http://www.chiark.greenend.org.uk/~sgtatham/bugs
** Tags added: performance
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1835068
Title:
When I click to top indicators, I will see freezing animations
To manage notifications about this bug go to:
Public bug reported:
Handbrake on ubuntu 18.04 no longer autocrops videos as it used to. I've
tried multiple videos, and while Handbrake on Windows crops them
perfectly, Hanbrake on Ubuntu 18.04 no longer does.
How to reproduce.
Find a long skinny bluray video, which is just about any movie rele
Public bug reported:
[Impact]
I2C designware fails to get its adapter number, and this may lead to fail to
access touchpad through I2C bus.
[ 6.476367] WARNING: CPU: 9 PID: 567 at
/build/linux-oem-osp1-bkWHJC/linux-oem-osp1-5.0.0/drivers/i2c/i2c-core-base.c:1322
i2c_add_numbered_adapter+0x81/0x
Here's the notes I took while reviewing this package:
About the source code:
uwsgi_calloc() re-introduces integer overflow bugs
cppcheck results are entirely false positives
About the debian packaging:
cdbs is unfortunate
gbp is difficult to work with
there's a huge number of binary packages
comp
** Changed in: linux (Ubuntu)
Status: In Progress => Invalid
** Changed in: linux-oem-osp1 (Ubuntu)
Status: New => Invalid
** Changed in: linux (Ubuntu Bionic)
Status: New => In Progress
** Changed in: linux-oem-osp1 (Ubuntu Bionic)
Status: New => In Progress
** Chan
Public bug reported:
I am not able to start tor browser since a couple of days because gpg
loops refreshing keys. Killing gpg allows tor browser to start:
UIDPID PPID C STIME TTY TIME CMD
bor 31474 31391 97 06:30 ?00:13:46 /usr/bin/gpg --status-fd 2
--homedir /hom
*** This bug is a duplicate of bug 1827884 ***
https://bugs.launchpad.net/bugs/1827884
** This bug has been marked a duplicate of bug 1827884
Boot problems after upgrade to kernel 4.15.0-48 (18.04.2LTS/i386)
--
You received this bug notification because you are a member of Ubuntu
Bugs, wh
Status changed to 'Confirmed' because the bug affects multiple users.
** Changed in: linux (Ubuntu Bionic)
Status: New => Confirmed
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1827884
Title:
[Expired for linux (Ubuntu) because there has been no activity for 60
days.]
** Changed in: linux (Ubuntu)
Status: Incomplete => Expired
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1816231
T
[Expired for firefox (Ubuntu) because there has been no activity for 60
days.]
** Changed in: firefox (Ubuntu)
Status: Incomplete => Expired
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/179232
[Expired for pulseaudio (Ubuntu) because there has been no activity for
60 days.]
** Changed in: pulseaudio (Ubuntu)
Status: Incomplete => Expired
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/
[Expired for linux (Ubuntu) because there has been no activity for 60
days.]
** Changed in: linux (Ubuntu)
Status: Incomplete => Expired
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1827417
T
[Expired for totem (Ubuntu) because there has been no activity for 60
days.]
** Changed in: totem (Ubuntu)
Status: Incomplete => Expired
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1529153
T
[Expired for totem (Ubuntu) because there has been no activity for 60
days.]
** Changed in: totem (Ubuntu)
Status: Incomplete => Expired
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1376468
T
[Expired for totem (Ubuntu) because there has been no activity for 60
days.]
** Changed in: totem (Ubuntu)
Status: Incomplete => Expired
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1471944
T
[Expired for totem (Ubuntu) because there has been no activity for 60
days.]
** Changed in: totem (Ubuntu)
Status: Incomplete => Expired
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1491564
T
[Expired for totem (Ubuntu) because there has been no activity for 60
days.]
** Changed in: totem (Ubuntu)
Status: Incomplete => Expired
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1346188
T
[Expired for totem (Ubuntu) because there has been no activity for 60
days.]
** Changed in: totem (Ubuntu)
Status: Incomplete => Expired
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/942873
Ti
[Expired for totem (Ubuntu) because there has been no activity for 60
days.]
** Changed in: totem (Ubuntu)
Status: Incomplete => Expired
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1270435
T
[Expired for totem (Ubuntu) because there has been no activity for 60
days.]
** Changed in: totem (Ubuntu)
Status: Incomplete => Expired
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1015417
T
[Expired for totem (Ubuntu) because there has been no activity for 60
days.]
** Changed in: totem (Ubuntu)
Status: Incomplete => Expired
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1232544
T
[Expired for totem (Ubuntu) because there has been no activity for 60
days.]
** Changed in: totem (Ubuntu)
Status: Incomplete => Expired
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1219121
T
[Expired for totem (Ubuntu) because there has been no activity for 60
days.]
** Changed in: totem (Ubuntu)
Status: Incomplete => Expired
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1448243
T
[Expired for totem (Ubuntu) because there has been no activity for 60
days.]
** Changed in: totem (Ubuntu)
Status: Incomplete => Expired
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1132065
T
*** This bug is a duplicate of bug 1753070 ***
https://bugs.launchpad.net/bugs/1753070
Status changed to 'Confirmed' because the bug affects multiple users.
** Changed in: gnome-control-center (Ubuntu)
Status: New => Confirmed
--
You received this bug notification because you are a m
** Summary changed:
- linux-snapdragon: -proposed tracker
+ linux-snapdragon: 4.15.0-1058.63 -proposed tracker
** Changed in: kernel-sru-workflow/prepare-package
Status: Confirmed => In Progress
** Changed in: kernel-sru-workflow/prepare-package
Assignee: Canonical Kernel Team (cano
** Description changed:
This bug will contain status and test results related to a kernel source
(or snap) as stated in the title.
For an explanation of the tasks and the associated workflow see:
https://wiki.ubuntu.com/Kernel/kernel-sru-workflow
-- swm properties --
kernel-sta
** Summary changed:
- linux-kvm: -proposed tracker
+ linux-kvm: 4.15.0-1039.39 -proposed tracker
** Changed in: kernel-sru-workflow/prepare-package
Status: Confirmed => In Progress
** Changed in: kernel-sru-workflow/prepare-package
Assignee: Canonical Kernel Team (canonical-kernel-t
This is the log of running uefi app.
** Attachment added: "591384548.jpg"
https://bugs.launchpad.net/ubuntu/+source/shim/+bug/1822043/+attachment/5274802/+files/591384548.jpg
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https:
** Description changed:
This bug will contain status and test results related to a kernel source
(or snap) as stated in the title.
For an explanation of the tasks and the associated workflow see:
https://wiki.ubuntu.com/Kernel/kernel-sru-workflow
-- swm properties --
kernel-sta
** Changed in: gnome-software (Ubuntu)
Status: New => Confirmed
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1835073
Title:
Put filename path of .deb package on a different line
To manage n
** Description changed:
This bug will contain status and test results related to a kernel source
(or snap) as stated in the title.
For an explanation of the tasks and the associated workflow see:
https://wiki.ubuntu.com/Kernel/kernel-sru-workflow
derivatives: bug 1834924 (dragonb
** Summary changed:
- linux-gcp: -proposed tracker
+ linux-gcp: 4.15.0-1037.39 -proposed tracker
** Changed in: kernel-sru-workflow/prepare-package
Status: Confirmed => In Progress
** Changed in: kernel-sru-workflow/prepare-package
Assignee: Canonical Kernel Team (canonical-kernel-t
Thank you for taking the time to report this bug and helping to make
Ubuntu better. Unfortunately, we cannot work on this bug because your
description didn't include enough information. You may find it helpful
to read "How to report bugs effectively"
http://www.chiark.greenend.org.uk/~sgtatham/bugs
** Attachment added: "journalctlb0.log"
https://bugs.launchpad.net/ubuntu/+source/gnome-software/+bug/1835076/+attachment/5274803/+files/journalctlb0.log
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bu
I can observe the problem in a stock Ubuntu 19.10 VM, after installing the
google-chrome-stable deb from chrome.com.
Attaching journalctl, the following lines look like they might be related to
the problem:
jul 03 07:11:55 eoanvm gnome-software[2412]: failed to rescan: Failed to parse
/usr/shar
Same problem using python3 and multithreading in Ubuntu 18.04 LTS.
libgcc_s.so.1 must be installed for pthread_cancel to work.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to the bug report.
https://bugs.launchpad.net/bugs/40285
Title:
lib
After evaluating dependencies, required further changes and mostly
maintainability for security and packaging it was decided there are too
many concerns - not about any single package in particular, but the
overall Mailman3 stack - about the ability to maintain and monitor it as
well as we need it
After evaluating dependencies, required further changes and mostly
maintainability for security and packaging it was decided there are too
many concerns - not about any single package in particular, but the
overall Mailman3 stack - about the ability to maintain and monitor it as
well as we need it
** Changed in: kernel-sru-workflow/promote-to-proposed
Status: New => Confirmed
** Tags added: block-proposed-bionic
** Tags added: block-proposed
** Description changed:
This bug will contain status and test results related to a kernel source
(or snap) as stated in the title.
F
After evaluating dependencies, required further changes and mostly
maintainability for security and packaging it was decided there are too
many concerns - not about any single package in particular, but the
overall Mailman3 stack - about the ability to maintain and monitor it as
well as we need it
After evaluating dependencies, required further changes and mostly
maintainability for security and packaging it was decided there are too
many concerns - not about any single package in particular, but the
overall Mailman3 stack - about the ability to maintain and monitor it as
well as we need it
After evaluating dependencies, required further changes and mostly
maintainability for security and packaging it was decided there are too
many concerns - not about any single package in particular, but the
overall Mailman3 stack - about the ability to maintain and monitor it as
well as we need it
After evaluating dependencies, required further changes and mostly
maintainability for security and packaging it was decided there are too
many concerns - not about any single package in particular, but the
overall Mailman3 stack - about the ability to maintain and monitor it as
well as we need it
After evaluating dependencies, required further changes and mostly
maintainability for security and packaging it was decided there are too
many concerns - not about any single package in particular, but the
overall Mailman3 stack - about the ability to maintain and monitor it as
well as we need it
After evaluating dependencies, required further changes and mostly
maintainability for security and packaging it was decided there are too
many concerns - not about any single package in particular, but the
overall Mailman3 stack - about the ability to maintain and monitor it as
well as we need it
** Description changed:
This bug will contain status and test results related to a kernel source
(or snap) as stated in the title.
For an explanation of the tasks and the associated workflow see:
https://wiki.ubuntu.com/Kernel/kernel-sru-workflow
backports: bug 1834935 (xenial/li
After evaluating dependencies, required further changes and mostly
maintainability for security and packaging it was decided there are too
many concerns - not about any single package in particular, but the
overall Mailman3 stack - about the ability to maintain and monitor it as
well as we need it
After evaluating dependencies, required further changes and mostly
maintainability for security and packaging it was decided there are too
many concerns - not about any single package in particular, but the
overall Mailman3 stack - about the ability to maintain and monitor it as
well as we need it
After evaluating dependencies, required further changes and mostly
maintainability for security and packaging it was decided there are too
many concerns - not about any single package in particular, but the
overall Mailman3 stack - about the ability to maintain and monitor it as
well as we need it
After evaluating dependencies, required further changes and mostly
maintainability for security and packaging it was decided there are too
many concerns - not about any single package in particular, but the
overall Mailman3 stack - about the ability to maintain and monitor it as
well as we need it
After evaluating dependencies, required further changes and mostly
maintainability for security and packaging it was decided there are too
many concerns - not about any single package in particular, but the
overall Mailman3 stack - about the ability to maintain and monitor it as
well as we need it
After evaluating dependencies, required further changes and mostly
maintainability for security and packaging it was decided there are too
many concerns - not about any single package in particular, but the
overall Mailman3 stack - about the ability to maintain and monitor it as
well as we need it
After evaluating dependencies, required further changes and mostly
maintainability for security and packaging it was decided there are too
many concerns - not about any single package in particular, but the
overall Mailman3 stack - about the ability to maintain and monitor it as
well as we need it
After evaluating dependencies, required further changes and mostly
maintainability for security and packaging it was decided there are too
many concerns - not about any single package in particular, but the
overall Mailman3 stack - about the ability to maintain and monitor it as
well as we need it
After evaluating dependencies, required further changes and mostly
maintainability for security and packaging it was decided there are too
many concerns - not about any single package in particular, but the
overall Mailman3 stack - about the ability to maintain and monitor it as
well as we need it
After evaluating dependencies, required further changes and mostly
maintainability for security and packaging it was decided there are too
many concerns - not about any single package in particular, but the
overall Mailman3 stack - about the ability to maintain and monitor it as
well as we need it
After evaluating dependencies, required further changes and mostly
maintainability for security and packaging it was decided there are too
many concerns - not about any single package in particular, but the
overall Mailman3 stack - about the ability to maintain and monitor it as
well as we need it
After evaluating dependencies, required further changes and mostly
maintainability for security and packaging it was decided there are too
many concerns - not about any single package in particular, but the
overall Mailman3 stack - about the ability to maintain and monitor it as
well as we need it
After evaluating dependencies, required further changes and mostly
maintainability for security and packaging it was decided there are too
many concerns - not about any single package in particular, but the
overall Mailman3 stack - about the ability to maintain and monitor it as
well as we need it
After evaluating dependencies, required further changes and mostly
maintainability for security and packaging it was decided there are too
many concerns - not about any single package in particular, but the
overall Mailman3 stack - about the ability to maintain and monitor it as
well as we need it
After evaluating dependencies, required further changes and mostly
maintainability for security and packaging it was decided there are too
many concerns - not about any single package in particular, but the
overall Mailman3 stack - about the ability to maintain and monitor it as
well as we need it
Sorry for the late reply.
Have you tried latest latest Ubuntu ISO?
http://cdimages.ubuntu.com/daily-live/current/
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1827417
Title:
Ubuntu 16.04 - EMU10K
After evaluating dependencies, required further changes and mostly
maintainability for security and packaging it was decided there are too
many concerns - not about any single package in particular, but the
overall Mailman3 stack - about the ability to maintain and monitor it as
well as we need it
After evaluating dependencies, required further changes and mostly
maintainability for security and packaging it was decided there are too
many concerns - not about any single package in particular, but the
overall Mailman3 stack - about the ability to maintain and monitor it as
well as we need it
After evaluating dependencies, required further changes and mostly
maintainability for security and packaging it was decided there are too
many concerns - not about any single package in particular, but the
overall Mailman3 stack - about the ability to maintain and monitor it as
well as we need it
After evaluating dependencies, required further changes and mostly
maintainability for security and packaging it was decided there are too
many concerns - not about any single package in particular, but the
overall Mailman3 stack - about the ability to maintain and monitor it as
well as we need it
Does the latest HWE kernel solve the issue?
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1831710
Title:
Touchpad not working (Lenevo Ideapad 330 series)
To manage notifications about this bug go t
After evaluating dependencies, required further changes and mostly
maintainability for security and packaging it was decided there are too
many concerns - not about any single package in particular, but the
overall Mailman3 stack - about the ability to maintain and monitor it as
well as we need it
After evaluating dependencies, required further changes and mostly
maintainability for security and packaging it was decided there are too
many concerns - not about any single package in particular, but the
overall Mailman3 stack - about the ability to maintain and monitor it as
well as we need it
After evaluating dependencies, required further changes and mostly
maintainability for security and packaging it was decided there are too
many concerns - not about any single package in particular, but the
overall Mailman3 stack - about the ability to maintain and monitor it as
well as we need it
After evaluating dependencies, required further changes and mostly
maintainability for security and packaging it was decided there are too
many concerns - not about any single package in particular, but the
overall Mailman3 stack - about the ability to maintain and monitor it as
well as we need it
After evaluating dependencies, required further changes and mostly
maintainability for security and packaging it was decided there are too
many concerns - not about any single package in particular, but the
overall Mailman3 stack - about the ability to maintain and monitor it as
well as we need it
After evaluating dependencies, required further changes and mostly
maintainability for security and packaging it was decided there are too
many concerns - not about any single package in particular, but the
overall Mailman3 stack - about the ability to maintain and monitor it as
well as we need it
After evaluating dependencies, required further changes and mostly
maintainability for security and packaging it was decided there are too
many concerns - not about any single package in particular, but the
overall Mailman3 stack - about the ability to maintain and monitor it as
well as we need it
After evaluating dependencies, required further changes and mostly
maintainability for security and packaging it was decided there are too
many concerns - not about any single package in particular, but the
overall Mailman3 stack - about the ability to maintain and monitor it as
well as we need it
After evaluating dependencies, required further changes and mostly
maintainability for security and packaging it was decided there are too
many concerns - not about any single package in particular, but the
overall Mailman3 stack - about the ability to maintain and monitor it as
well as we need it
After evaluating dependencies, required further changes and mostly
maintainability for security and packaging it was decided there are too
many concerns - not about any single package in particular, but the
overall Mailman3 stack - about the ability to maintain and monitor it as
well as we need it
After evaluating dependencies, required further changes and mostly
maintainability for security and packaging it was decided there are too
many concerns - not about any single package in particular, but the
overall Mailman3 stack - about the ability to maintain and monitor it as
well as we need it
After evaluating dependencies, required further changes and mostly
maintainability for security and packaging it was decided there are too
many concerns - not about any single package in particular, but the
overall Mailman3 stack - about the ability to maintain and monitor it as
well as we need it
After evaluating dependencies, required further changes and mostly
maintainability for security and packaging it was decided there are too
many concerns - not about any single package in particular, but the
overall Mailman3 stack - about the ability to maintain and monitor it as
well as we need it
701 - 800 of 821 matches
Mail list logo