The verification of the Stable Release Update for cloud-init has
completed successfully and the package has now been released to
-updates. Subsequently, the Ubuntu Stable Release Updates Team is being
unsubscribed and will not receive messages about this bug report. In
the event that you
I'll be verifying this case by the end of this week so it can be
published, hopefully, next week. Thank you!
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1695789
Title:
multipath random crashes on
This bug was fixed in the package nplan - 0.23~17.04.1
---
nplan (0.23~17.04.1) zesty; urgency=medium
* Backport netplan 0.23 to 17.04. (LP: #1688632)
nplan (0.23) artful; urgency=medium
* Do not unbind brcmfmac, interface will be gone. (LP: #1696162)
nplan (0.22) artful;
This bug was fixed in the package nplan - 0.23~16.10.1
---
nplan (0.23~16.10.1) yakkety; urgency=medium
* Backport netplan 0.23 to 16.10. (LP: #1688632)
nplan (0.23) artful; urgency=medium
* Do not unbind brcmfmac, interface will be gone. (LP: #1696162)
nplan (0.22) artful;
** Tags removed: verification-needed
** Tags added: verification-done
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1697545
Title:
sru curtin 2017-06-12 - 0.1.0~bzr505-0ubuntu1
To manage
tests ran: 1, failed: 0;
http://kernel.ubuntu.com/testing/4.8.0-58.63-generic/amaura__4.8.0-58.63__2017-06-27_13-55-00/results-index.html
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1700533
tests ran: 16, failed: 0;
http://kernel.ubuntu.com/testing/4.8.0-58.63-generic/secchi__4.8.0-58.63__2017-06-27_15-59-00/results-index.html
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1700533
** Changed in: kernel-sru-workflow/security-signoff
Status: Confirmed => In Progress
** Changed in: kernel-sru-workflow/security-signoff
Assignee: Canonical Security Team (canonical-security) => Steve Beattie
(sbeattie)
--
You received this bug notification because you are a member
tests ran: 10, failed: 0;
http://kernel.ubuntu.com/testing/4.8.0-58.63-generic/pepe__4.8.0-58.63__2017-06-27_15-22-00/results-index.html
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1700533
tests ran: 9, failed: 0;
http://kernel.ubuntu.com/testing/4.8.0-58.63-generic/ms10-35-mcdivittB0-kernel__4.8.0-58.63__2017-06-27_15-29-00/results-index.html
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
tests ran: 5, failed: 0;
http://kernel.ubuntu.com/testing/4.8.0-58.63-generic/hainzel__4.8.0-58.63__2017-06-27_15-27-00/results-index.html
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1700533
tests ran: 4, failed: 1;
http://kernel.ubuntu.com/testing/4.4.0-83.106-generic/s2lp3__4.4.0-83.106__2017-06-27_15-37-00/results-index.html
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1700541
tests ran: 1, failed: 0;
http://kernel.ubuntu.com/testing/4.8.0-58.63-generic/fozzie__4.8.0-58.63__2017-06-27_15-44-00/results-index.html
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1700533
** Changed in: kernel-sru-workflow/security-signoff
Status: Confirmed => In Progress
** Changed in: kernel-sru-workflow/security-signoff
Assignee: Canonical Security Team (canonical-security) => Steve Beattie
(sbeattie)
--
You received this bug notification because you are a member
tests ran: 10, failed: 0;
http://kernel.ubuntu.com/testing/4.4.0-83.106-generic/s2lp6g001__4.4.0-83.106__2017-06-27_15-36-00/results-index.html
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
** Changed in: kernel-sru-workflow/security-signoff
Status: Confirmed => In Progress
** Changed in: kernel-sru-workflow/security-signoff
Assignee: Canonical Security Team (canonical-security) => Steve Beattie
(sbeattie)
--
You received this bug notification because you are a member
tests ran: 10, failed: 0;
http://kernel.ubuntu.com/testing/4.4.0-83.106-generic/michael__4.4.0-83.106__2017-06-27_14-57-00/results-index.html
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1700541
** Changed in: kernel-sru-workflow/security-signoff
Status: Confirmed => In Progress
** Changed in: kernel-sru-workflow/security-signoff
Assignee: Canonical Security Team (canonical-security) => Steve Beattie
(sbeattie)
--
You received this bug notification because you are a member
** Changed in: kernel-sru-workflow/security-signoff
Status: Confirmed => In Progress
** Changed in: kernel-sru-workflow/security-signoff
Assignee: Canonical Security Team (canonical-security) => Steve Beattie
(sbeattie)
--
You received this bug notification because you are a member
** Changed in: kernel-sru-workflow/security-signoff
Status: Confirmed => In Progress
** Changed in: kernel-sru-workflow/security-signoff
Assignee: Canonical Security Team (canonical-security) => Steve Beattie
(sbeattie)
--
You received this bug notification because you are a member
** Changed in: kernel-sru-workflow/security-signoff
Status: Confirmed => In Progress
** Changed in: kernel-sru-workflow/security-signoff
Assignee: Canonical Security Team (canonical-security) => Steve Beattie
(sbeattie)
--
You received this bug notification because you are a member
** Changed in: kernel-sru-workflow/security-signoff
Status: Confirmed => In Progress
** Changed in: kernel-sru-workflow/security-signoff
Assignee: Canonical Security Team (canonical-security) => Steve Beattie
(sbeattie)
--
You received this bug notification because you are a member
tests ran: 14, failed: 3;
http://kernel.ubuntu.com/testing/3.13.0-123.172-generic/ms10-34-mcdivittB0-kernel__3.13.0-123.172__2017-06-27_15-29-00/results-index.html
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
** Changed in: kernel-sru-workflow/security-signoff
Status: Confirmed => In Progress
** Changed in: kernel-sru-workflow/security-signoff
Assignee: Canonical Security Team (canonical-security) => Steve Beattie
(sbeattie)
--
You received this bug notification because you are a member
Thanks for filing this bug in Ubuntu.
Could you please attach the mysql log files from /var/log/mysql/* ?
The service is failing to start, but the systemd logs are not enough to
tell me why. I see some apparmor DENIED error messages, but I also get
them on a fresh install where mysql starts up
** Branch linked: lp:~3v1n0/unity-control-center/grouped-compiz-
gsettings-support-x
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1700600
Title:
Appearance settings changed in normal mode, aren't
This bug was fixed in the package linux-firmware - 1.167
---
linux-firmware (1.167) artful; urgency=medium
* Rebase against
git://git.kernel.org/pub/scm/linux/kernel/git/firmware/linux-firmware.git
7d2c913dcd1be083350d97a8cb1eba24cfacbc8a
- linux-firmware: liquidio: update
These lines should work permanently, as the option setting changes are
permanently recorded in /etc/cups/printers.conf.
For making them getting applied automatically for everyone having this
printer a quirk rule has to be added to /usr/share/cups/usb/org.cups
.usb-quirks.
You can edit the file
Thanks for filing this bug in Ubuntu.
Could you please attach the mysql log files from /var/log/mysql/* ?
The service is failing to start, but the systemd logs are not enough to
tell me why. I see some apparmor DENIED error messages, but I also get
them on a fresh install where mysql starts up
Public bug reported:
It crashes whenever I open any document including .doc and xls files.
I start it from shell and it loads but when I open a file, it crashes.
There are no messages or errors in output.
ProblemType: Bug
DistroRelease: Ubuntu 14.04
Package: libreoffice 1:4.2.8-0ubuntu5.1
Will it also work for long file names when the bubble covers whole width
and therefore has nowhere to jump? Is it supposed to be fixed in
"1:3.18.4.is.3.14.3-0ubuntu5"?
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
As part of a recent change in the Stable Release Update verification
policy we would like to inform that for a bug to be considered verified
for a given release a verification-done-$RELEASE tag needs to be added
to the bug where $RELEASE is the name of the series the package that was
tested (e.g.
As part of a recent change in the Stable Release Update verification
policy we would like to inform that for a bug to be considered verified
for a given release a verification-done-$RELEASE tag needs to be added
to the bug where $RELEASE is the name of the series the package that was
tested (e.g.
I can also confirm that the issue exists.
I'm the administrator of 2 DNS nameservers (bind9) running Ubuntu
14.04.5 LTS with upgraded kernel (linux-image-generic-lts-xenial which
depends on linux-image-4.4.0-81-generic at this time).
root@ns2:~# lsb_release -a
No LSB modules are available.
As part of a recent change in the Stable Release Update verification
policy we would like to inform that for a bug to be considered verified
for a given release a verification-done-$RELEASE tag needs to be added
to the bug where $RELEASE is the name of the series the package that was
tested (e.g.
This bug is still affecting me and others that I know.
When using IPv6 with SLAAC you randomly get a new address since you
can't be sure which interface is choosen on boot.
A solution to this problem would be very welcome!
--
You received this bug notification because you are a member of
As part of a recent change in the Stable Release Update verification
policy we would like to inform that for a bug to be considered verified
for a given release a verification-done-$RELEASE tag needs to be added
to the bug where $RELEASE is the name of the series the package that was
tested (e.g.
As part of a recent change in the Stable Release Update verification
policy we would like to inform that for a bug to be considered verified
for a given release a verification-done-$RELEASE tag needs to be added
to the bug where $RELEASE is the name of the series the package that was
tested (e.g.
As part of a recent change in the Stable Release Update verification
policy we would like to inform that for a bug to be considered verified
for a given release a verification-done-$RELEASE tag needs to be added
to the bug where $RELEASE is the name of the series the package that was
tested (e.g.
As part of a recent change in the Stable Release Update verification
policy we would like to inform that for a bug to be considered verified
for a given release a verification-done-$RELEASE tag needs to be added
to the bug where $RELEASE is the name of the series the package that was
tested (e.g.
As part of a recent change in the Stable Release Update verification
policy we would like to inform that for a bug to be considered verified
for a given release a verification-done-$RELEASE tag needs to be added
to the bug where $RELEASE is the name of the series the package that was
tested (e.g.
As part of a recent change in the Stable Release Update verification
policy we would like to inform that for a bug to be considered verified
for a given release a verification-done-$RELEASE tag needs to be added
to the bug where $RELEASE is the name of the series the package that was
tested (e.g.
As part of a recent change in the Stable Release Update verification
policy we would like to inform that for a bug to be considered verified
for a given release a verification-done-$RELEASE tag needs to be added
to the bug where $RELEASE is the name of the series the package that was
tested (e.g.
As part of a recent change in the Stable Release Update verification
policy we would like to inform that for a bug to be considered verified
for a given release a verification-done-$RELEASE tag needs to be added
to the bug where $RELEASE is the name of the series the package that was
tested (e.g.
As part of a recent change in the Stable Release Update verification
policy we would like to inform that for a bug to be considered verified
for a given release a verification-done-$RELEASE tag needs to be added
to the bug where $RELEASE is the name of the series the package that was
tested (e.g.
As part of a recent change in the Stable Release Update verification
policy we would like to inform that for a bug to be considered verified
for a given release a verification-done-$RELEASE tag needs to be added
to the bug where $RELEASE is the name of the series the package that was
tested (e.g.
As part of a recent change in the Stable Release Update verification
policy we would like to inform that for a bug to be considered verified
for a given release a verification-done-$RELEASE tag needs to be added
to the bug where $RELEASE is the name of the series the package that was
tested (e.g.
As part of a recent change in the Stable Release Update verification
policy we would like to inform that for a bug to be considered verified
for a given release a verification-done-$RELEASE tag needs to be added
to the bug where $RELEASE is the name of the series the package that was
tested (e.g.
As part of a recent change in the Stable Release Update verification
policy we would like to inform that for a bug to be considered verified
for a given release a verification-done-$RELEASE tag needs to be added
to the bug where $RELEASE is the name of the series the package that was
tested (e.g.
As part of a recent change in the Stable Release Update verification
policy we would like to inform that for a bug to be considered verified
for a given release a verification-done-$RELEASE tag needs to be added
to the bug where $RELEASE is the name of the series the package that was
tested (e.g.
resetting all the tasks to confirmed, rather than Incomplete as I've
tested and am still waiting for a resolution or whatever.
** Changed in: linux (Ubuntu)
Status: Incomplete => Confirmed
** Changed in: linux (Ubuntu Xenial)
Status: Incomplete => Confirmed
** Changed in: linux
As part of a recent change in the Stable Release Update verification
policy we would like to inform that for a bug to be considered verified
for a given release a verification-done-$RELEASE tag needs to be added
to the bug where $RELEASE is the name of the series the package that was
tested (e.g.
As part of a recent change in the Stable Release Update verification
policy we would like to inform that for a bug to be considered verified
for a given release a verification-done-$RELEASE tag needs to be added
to the bug where $RELEASE is the name of the series the package that was
tested (e.g.
As part of a recent change in the Stable Release Update verification
policy we would like to inform that for a bug to be considered verified
for a given release a verification-done-$RELEASE tag needs to be added
to the bug where $RELEASE is the name of the series the package that was
tested (e.g.
As part of a recent change in the Stable Release Update verification
policy we would like to inform that for a bug to be considered verified
for a given release a verification-done-$RELEASE tag needs to be added
to the bug where $RELEASE is the name of the series the package that was
tested (e.g.
As part of a recent change in the Stable Release Update verification
policy we would like to inform that for a bug to be considered verified
for a given release a verification-done-$RELEASE tag needs to be added
to the bug where $RELEASE is the name of the series the package that was
tested (e.g.
As part of a recent change in the Stable Release Update verification
policy we would like to inform that for a bug to be considered verified
for a given release a verification-done-$RELEASE tag needs to be added
to the bug where $RELEASE is the name of the series the package that was
tested (e.g.
As part of a recent change in the Stable Release Update verification
policy we would like to inform that for a bug to be considered verified
for a given release a verification-done-$RELEASE tag needs to be added
to the bug where $RELEASE is the name of the series the package that was
tested (e.g.
As part of a recent change in the Stable Release Update verification
policy we would like to inform that for a bug to be considered verified
for a given release a verification-done-$RELEASE tag needs to be added
to the bug where $RELEASE is the name of the series the package that was
tested (e.g.
As part of a recent change in the Stable Release Update verification
policy we would like to inform that for a bug to be considered verified
for a given release a verification-done-$RELEASE tag needs to be added
to the bug where $RELEASE is the name of the series the package that was
tested (e.g.
As part of a recent change in the Stable Release Update verification
policy we would like to inform that for a bug to be considered verified
for a given release a verification-done-$RELEASE tag needs to be added
to the bug where $RELEASE is the name of the series the package that was
tested (e.g.
As part of a recent change in the Stable Release Update verification
policy we would like to inform that for a bug to be considered verified
for a given release a verification-done-$RELEASE tag needs to be added
to the bug where $RELEASE is the name of the series the package that was
tested (e.g.
As part of a recent change in the Stable Release Update verification
policy we would like to inform that for a bug to be considered verified
for a given release a verification-done-$RELEASE tag needs to be added
to the bug where $RELEASE is the name of the series the package that was
tested (e.g.
As part of a recent change in the Stable Release Update verification
policy we would like to inform that for a bug to be considered verified
for a given release a verification-done-$RELEASE tag needs to be added
to the bug where $RELEASE is the name of the series the package that was
tested (e.g.
Hello everyone,
i could solve the problem by using the alternate iso 16.10 and what it
did different was to unmount a partition that was being used. Without
unmonting it i could not install grub on the destination drive ever.
Now all it is OK and i am using EFI. If you need me to do some other
As part of a recent change in the Stable Release Update verification
policy we would like to inform that for a bug to be considered verified
for a given release a verification-done-$RELEASE tag needs to be added
to the bug where $RELEASE is the name of the series the package that was
tested (e.g.
As part of a recent change in the Stable Release Update verification
policy we would like to inform that for a bug to be considered verified
for a given release a verification-done-$RELEASE tag needs to be added
to the bug where $RELEASE is the name of the series the package that was
tested (e.g.
As part of a recent change in the Stable Release Update verification
policy we would like to inform that for a bug to be considered verified
for a given release a verification-done-$RELEASE tag needs to be added
to the bug where $RELEASE is the name of the series the package that was
tested (e.g.
As part of a recent change in the Stable Release Update verification
policy we would like to inform that for a bug to be considered verified
for a given release a verification-done-$RELEASE tag needs to be added
to the bug where $RELEASE is the name of the series the package that was
tested (e.g.
As part of a recent change in the Stable Release Update verification
policy we would like to inform that for a bug to be considered verified
for a given release a verification-done-$RELEASE tag needs to be added
to the bug where $RELEASE is the name of the series the package that was
tested (e.g.
As part of a recent change in the Stable Release Update verification
policy we would like to inform that for a bug to be considered verified
for a given release a verification-done-$RELEASE tag needs to be added
to the bug where $RELEASE is the name of the series the package that was
tested (e.g.
As part of a recent change in the Stable Release Update verification
policy we would like to inform that for a bug to be considered verified
for a given release a verification-done-$RELEASE tag needs to be added
to the bug where $RELEASE is the name of the series the package that was
tested (e.g.
As part of a recent change in the Stable Release Update verification
policy we would like to inform that for a bug to be considered verified
for a given release a verification-done-$RELEASE tag needs to be added
to the bug where $RELEASE is the name of the series the package that was
tested (e.g.
As part of a recent change in the Stable Release Update verification
policy we would like to inform that for a bug to be considered verified
for a given release a verification-done-$RELEASE tag needs to be added
to the bug where $RELEASE is the name of the series the package that was
tested (e.g.
As part of a recent change in the Stable Release Update verification
policy we would like to inform that for a bug to be considered verified
for a given release a verification-done-$RELEASE tag needs to be added
to the bug where $RELEASE is the name of the series the package that was
tested (e.g.
As part of a recent change in the Stable Release Update verification
policy we would like to inform that for a bug to be considered verified
for a given release a verification-done-$RELEASE tag needs to be added
to the bug where $RELEASE is the name of the series the package that was
tested (e.g.
As part of a recent change in the Stable Release Update verification
policy we would like to inform that for a bug to be considered verified
for a given release a verification-done-$RELEASE tag needs to be added
to the bug where $RELEASE is the name of the series the package that was
tested (e.g.
As part of a recent change in the Stable Release Update verification
policy we would like to inform that for a bug to be considered verified
for a given release a verification-done-$RELEASE tag needs to be added
to the bug where $RELEASE is the name of the series the package that was
tested (e.g.
As part of a recent change in the Stable Release Update verification
policy we would like to inform that for a bug to be considered verified
for a given release a verification-done-$RELEASE tag needs to be added
to the bug where $RELEASE is the name of the series the package that was
tested (e.g.
As part of a recent change in the Stable Release Update verification
policy we would like to inform that for a bug to be considered verified
for a given release a verification-done-$RELEASE tag needs to be added
to the bug where $RELEASE is the name of the series the package that was
tested (e.g.
As part of a recent change in the Stable Release Update verification
policy we would like to inform that for a bug to be considered verified
for a given release a verification-done-$RELEASE tag needs to be added
to the bug where $RELEASE is the name of the series the package that was
tested (e.g.
As part of a recent change in the Stable Release Update verification
policy we would like to inform that for a bug to be considered verified
for a given release a verification-done-$RELEASE tag needs to be added
to the bug where $RELEASE is the name of the series the package that was
tested (e.g.
As part of a recent change in the Stable Release Update verification
policy we would like to inform that for a bug to be considered verified
for a given release a verification-done-$RELEASE tag needs to be added
to the bug where $RELEASE is the name of the series the package that was
tested (e.g.
As part of a recent change in the Stable Release Update verification
policy we would like to inform that for a bug to be considered verified
for a given release a verification-done-$RELEASE tag needs to be added
to the bug where $RELEASE is the name of the series the package that was
tested (e.g.
As part of a recent change in the Stable Release Update verification
policy we would like to inform that for a bug to be considered verified
for a given release a verification-done-$RELEASE tag needs to be added
to the bug where $RELEASE is the name of the series the package that was
tested (e.g.
As part of a recent change in the Stable Release Update verification
policy we would like to inform that for a bug to be considered verified
for a given release a verification-done-$RELEASE tag needs to be added
to the bug where $RELEASE is the name of the series the package that was
tested (e.g.
As part of a recent change in the Stable Release Update verification
policy we would like to inform that for a bug to be considered verified
for a given release a verification-done-$RELEASE tag needs to be added
to the bug where $RELEASE is the name of the series the package that was
tested (e.g.
As part of a recent change in the Stable Release Update verification
policy we would like to inform that for a bug to be considered verified
for a given release a verification-done-$RELEASE tag needs to be added
to the bug where $RELEASE is the name of the series the package that was
tested (e.g.
As part of a recent change in the Stable Release Update verification
policy we would like to inform that for a bug to be considered verified
for a given release a verification-done-$RELEASE tag needs to be added
to the bug where $RELEASE is the name of the series the package that was
tested (e.g.
As part of a recent change in the Stable Release Update verification
policy we would like to inform that for a bug to be considered verified
for a given release a verification-done-$RELEASE tag needs to be added
to the bug where $RELEASE is the name of the series the package that was
tested (e.g.
As part of a recent change in the Stable Release Update verification
policy we would like to inform that for a bug to be considered verified
for a given release a verification-done-$RELEASE tag needs to be added
to the bug where $RELEASE is the name of the series the package that was
tested (e.g.
As part of a recent change in the Stable Release Update verification
policy we would like to inform that for a bug to be considered verified
for a given release a verification-done-$RELEASE tag needs to be added
to the bug where $RELEASE is the name of the series the package that was
tested (e.g.
As part of a recent change in the Stable Release Update verification
policy we would like to inform that for a bug to be considered verified
for a given release a verification-done-$RELEASE tag needs to be added
to the bug where $RELEASE is the name of the series the package that was
tested (e.g.
As part of a recent change in the Stable Release Update verification
policy we would like to inform that for a bug to be considered verified
for a given release a verification-done-$RELEASE tag needs to be added
to the bug where $RELEASE is the name of the series the package that was
tested (e.g.
As part of a recent change in the Stable Release Update verification
policy we would like to inform that for a bug to be considered verified
for a given release a verification-done-$RELEASE tag needs to be added
to the bug where $RELEASE is the name of the series the package that was
tested (e.g.
As part of a recent change in the Stable Release Update verification
policy we would like to inform that for a bug to be considered verified
for a given release a verification-done-$RELEASE tag needs to be added
to the bug where $RELEASE is the name of the series the package that was
tested (e.g.
As part of a recent change in the Stable Release Update verification
policy we would like to inform that for a bug to be considered verified
for a given release a verification-done-$RELEASE tag needs to be added
to the bug where $RELEASE is the name of the series the package that was
tested (e.g.
As part of a recent change in the Stable Release Update verification
policy we would like to inform that for a bug to be considered verified
for a given release a verification-done-$RELEASE tag needs to be added
to the bug where $RELEASE is the name of the series the package that was
tested (e.g.
As part of a recent change in the Stable Release Update verification
policy we would like to inform that for a bug to be considered verified
for a given release a verification-done-$RELEASE tag needs to be added
to the bug where $RELEASE is the name of the series the package that was
tested (e.g.
As part of a recent change in the Stable Release Update verification
policy we would like to inform that for a bug to be considered verified
for a given release a verification-done-$RELEASE tag needs to be added
to the bug where $RELEASE is the name of the series the package that was
tested (e.g.
601 - 700 of 1096 matches
Mail list logo
