14:04 juliank: based on https://bugs.launchpad.net/ubuntu/+source/apt/+
bug/1750465/comments/10, are you suggesting I should hold on processing slangase
k's SRU upload?
14:04 Launchpad bug 1750465 in plymouth (Ubuntu Artful) "upgrade attemp
ting to process triggers out of order (package plymouth
Hello Stephen, or anyone else affected,
Accepted plymouth into artful-proposed. The package will build now and
be available at
https://launchpad.net/ubuntu/+source/plymouth/0.9.2-3ubuntu18 in a few
hours, and then in the -proposed repository.
Please help us by testing this new package. See
https
> [Regression Potential]
> no regression possibility, since this commit is already in artful and
bionic.
No. Please review https://wiki.ubuntu.com/StableReleaseUpdates#Why and
https://wiki.ubuntu.com/StableReleaseUpdates#Procedure and update the
bug description accordingly.
--
You received this
Hello Dustin, or anyone else affected,
Accepted avahi into artful-proposed. The package will build now and be
available at
https://launchpad.net/ubuntu/+source/avahi/0.6.32-1ubuntu1.1 in a few
hours, and then in the -proposed repository.
Please help us by testing this new package. See
https://wi
Hello Dustin, or anyone else affected,
Accepted avahi into trusty-proposed. The package will build now and be
available at
https://launchpad.net/ubuntu/+source/avahi/0.6.31-4ubuntu1.2 in a few
hours, and then in the -proposed repository.
Please help us by testing this new package. See
https://wi
Hello Dustin, or anyone else affected,
Accepted avahi into xenial-proposed. The package will build now and be
available at https://launchpad.net/ubuntu/+source/avahi/0.6.32~rc+dfsg-
1ubuntu2.1 in a few hours, and then in the -proposed repository.
Please help us by testing this new package. See
h
Unsubscribed ~ubuntu-sponsors as there is nothing left to sponsor.
** Changed in: avahi (Ubuntu Xenial)
Status: In Progress => Fix Committed
** Tags added: verification-needed-xenial
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is
I posted to the mailing list about this:
https://lists.ubuntu.com/archives/ubuntu-devel/2018-March/040230.html
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to e2fsprogs in Ubuntu.
https://bugs.launchpad.net/bugs/1601997
Title
** Tags added: rls-bb-incoming
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to e2fsprogs in Ubuntu.
https://bugs.launchpad.net/bugs/1601997
Title:
Ubuntu 16.10+ installer uses ext4 feature 'metadata_csum' which is
incompa
It's probably a bit too late now, as we're past feature freeze. See
https://wiki.ubuntu.com/BionicBeaver/ReleaseSchedule and
https://wiki.ubuntu.com/FeatureFreeze.
Separately, it'd need someone to contribute the update.
** Tags added: upgrade-software-version
** Changed in: opencv (Ubuntu)
We did change how mysql-server-5.7.postinst handles internal server
start and stop in Bionic in order to fix bug 1592669.
** Summary changed:
- installation of mysql-server fails because postinst fails to shut down server
+ When run from systemd-nspawn, installation of mysql-server fails because
Thank you for your report. This bug is better filed against netplan in
the first instance, so the netplan developers can consider your use
case.
If I were you, I'd expand on your use case, explaining what you're doing
and why you need it and so forth, if you want anything addressed before
Bionic's
> The problem is that if you upgrade from Xenial to Zesty or (soon)
Artful and we haven't SRUed the fixes then users could either become
unfixed or in some cases (didn't check / don't remember for this bug)
package versions might go backwards.
Worse, a user may not receive future security updates
I see pulseaudio in the SRU queue for stable releases. But this bug
doesn't appear to be fixed in Bionic yet, and AFAICT you have tried
multiple times to fix it in Bionic so it isn't clear to me that the
uploads for the stable releases are still current.
Please confirm what you want doing with the
The verification of the Stable Release Update for iproute2 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 encounter a
The verification of the Stable Release Update for iproute2 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 encounter a
** Tags added: regression-update
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to mesa in Ubuntu.
https://bugs.launchpad.net/bugs/1735594
Title:
[regression] compiz crashes after Mesa upgrade
Status in mesa package in Ubunt
** Tags added: mysql-sprint
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to systemd in Ubuntu.
https://bugs.launchpad.net/bugs/1579695
Title:
apport hook does not show the status of failed services
Status in systemd packag
The verification of the Stable Release Update for ntp 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 encounter a regr
Has anyone actually checked that the new build of ntpd actually still
works, please (eg. can sync the time)? If not, please could somebody
check that?
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to ntp in Ubuntu.
https://bugs
The verification of the Stable Release Update for unattended-upgrades
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
Thank you for taking the time to report this bug and helping to make
Ubuntu better.
This looks like a local configuration problem rather than a bug in
Ubuntu, so I'm marking the bug as Invalid. It seems to me that you have
configured PPA entries in /etc/apt/sources.list.d/ that are causing this
er
Thanks. That all looks fine then.
> Regarding amd64 smoke test, I've been using the updated package on my
machine (artful/amd64).
Does that actually exercise the ip command though? Or are you using
Network Manager, and does it speak to the kernel directly?
--
You received this bug notification
Could someone look at the autopkgtest failures listed against iproute2
in http://people.canonical.com/~ubuntu-archive/pending-sru.html please?
IIRC, firejail on s390x is a false positive? But there are some others,
too.
Also, has anyone done a quite smoke on amd64 to make sure the "ip"
command sti
Thanks. I'm happy with the additional information provided.
autopkgtests are still failing on this, including the amd64 one for
systemd which seems somewhat essential and has failed on retry, so right
now this is blocked on those.
If the autopkgtests failures can be resolved (fix or confirm not a
We concluded that this isn't a snapd bug, except in so far as it depends
on systemd.
** Changed in: snapd (Ubuntu Trusty)
Status: New => Invalid
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to systemd in Ubuntu.
https:
> I would accept a version of this SRU that hard-codes the choice of
upstart as the init system on 14.04, because that is the only init
system supported in that version of Ubuntu.
OK, that sounds like a reasonable way forward. I've rejected the current
upload in the queue, and I believe Andres has
On Wed, Dec 13, 2017 at 10:34:25PM -, Andres Rodriguez wrote:
> FWIW, this is currently affecting customers who are running MAAS and
> require livepatch.
It's been affecting users since January, no? Why the sudden urgency?
What difference will a week or two make?
> Comments #11 and #12 above
I've deferred my decision as to whether to accept what's currently in
the queue on this thread: https://lists.ubuntu.com/archives/ubuntu-
devel/2017-December/040093.html
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to systemd
Further extensive discussion at https://irclogs.ubuntu.com/2017/12/13
/%23ubuntu-devel.html#t15:15
Our current belief is that the bug is in the systemd package, introduced
by the SRU tracked in bug 1656280. That update broke our standard test
for determining if we're on a systemd system by creatin
** Also affects: systemd (Ubuntu)
Importance: Undecided
Status: New
** Also affects: systemd (Ubuntu Trusty)
Importance: Undecided
Status: New
** Also affects: maas (Ubuntu Trusty)
Importance: Undecided
Status: New
** Also affects: snapd (Ubuntu Trusty)
Importanc
08:44 bdmurray, xnox, klebers: I don't understand why we're
SRUing bug 1734908. It seems to have no user impact?
08:44 Additionally the Regression Potential and SRU
verification process seems to have made no consideration for how to test
or verify that rfkill hasn't otherwise regressed by this p
** Tags added: patch
** Changed in: systemd (Ubuntu Artful)
Status: New => Triaged
** Changed in: systemd (Ubuntu Artful)
Importance: Undecided => Medium
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to systemd in U
Does this fix need to be sent to Debian?
** Changed in: iproute2 (Ubuntu Artful)
Status: New => Fix Committed
** Tags added: verification-needed verification-needed-artful
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed
Hello bugproxy, or anyone else affected,
Accepted iproute2 into artful-proposed. The package will build now and
be available at
https://launchpad.net/ubuntu/+source/iproute2/4.9.0-1ubuntu2.1 in a few
hours, and then in the -proposed repository.
Please help us by testing this new package. See
htt
Hello Andreas, or anyone else affected,
Accepted iproute2 into artful-proposed. The package will build now and
be available at
https://launchpad.net/ubuntu/+source/iproute2/4.9.0-1ubuntu2.1 in a few
hours, and then in the -proposed repository.
Please help us by testing this new package. See
http
Hello bugproxy, or anyone else affected,
Accepted iproute2 into zesty-proposed. The package will build now and be
available at
https://launchpad.net/ubuntu/+source/iproute2/4.9.0-1ubuntu1.1 in a few
hours, and then in the -proposed repository.
Please help us by testing this new package. See
http
Hello bugproxy, or anyone else affected,
Accepted iproute2 into xenial-proposed. The package will build now and
be available at
https://launchpad.net/ubuntu/+source/iproute2/4.3.0-1ubuntu3.16.04.3 in
a few hours, and then in the -proposed repository.
Please help us by testing this new package. S
Hello bugproxy, or anyone else affected,
Accepted iproute2 into trusty-proposed. The package will build now and
be available at
https://launchpad.net/ubuntu/+source/iproute2/3.12.0-2ubuntu1.2 in a few
hours, and then in the -proposed repository.
Please help us by testing this new package. See
ht
I don't think the Trusty armhf autopkgtest test is likely to be a
regression. It doesn't appear to have ever passed before and the error
looks associated with the test runner rather than iproute2 itself. Given
the nature of the patch, it seems unlikely to me to be caused by this
update. I think it'
Please could someone check the autopkgtest failures listed against this
SRU in http://people.canonical.com/~ubuntu-archive/pending-sru.html?
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to util-linux in Ubuntu.
https://bugs.la
Brian, when you verified these, did you also check that single digit
choices can also be selected as expected? Seems to me that code path has
regression potential here.
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to apport in
Hello Andres, or anyone else affected,
Accepted resolvconf into trusty-proposed. The package will build now and
be available at
https://launchpad.net/ubuntu/+source/resolvconf/1.69ubuntu1.2 in a few
hours, and then in the -proposed repository.
Please help us by testing this new package. See
http
I have reviewed this. +1 from ~ubuntu-sru.
Regression risk is mitigated as Scott says by careful gating of the
active code to limit exposure of these changes to the non-default use
case only.
I did note the following:
What happens when the DHCP lease acquired in the initramfs expires? What
if th
Hello Andres, or anyone else affected,
Accepted resolvconf into xenial-proposed. The package will build now and
be available at
https://launchpad.net/ubuntu/+source/resolvconf/1.78ubuntu5 in a few
hours, and then in the -proposed repository.
Please help us by testing this new package. See
https:
** Tags removed: regression-updates
** Tags added: regression-update
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to systemd in Ubuntu.
https://bugs.launchpad.net/bugs/1727301
Title:
229-4ubuntu20 added ARP option breaks ex
** Description changed:
+ [Impact]
- [Impact]
+ * DNS name resolution fails in certain network configurations, where
+ different DNS servers are responsible for different domains and one or
+ more servers reply REFUSED to queries that regard other domains than
+ their own. Without th
Public bug reported:
I use unattended-upgrades to install new kernels (I think probably from
the security pocket). I believe this is the default. I also don't run
autoremove automatically, which I believe is also the default.
I just recovered a system that had been stuck in a disk full state for
Incidentally I noticed this on an EOL installation in a VM, but I have
no reason to think that anything has changed.
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to apt in Ubuntu.
https://bugs.launchpad.net/bugs/1723562
Title
Actually let's let someone else confirm this.
** Changed in: apt (Ubuntu)
Status: Triaged => New
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to apt in Ubuntu.
https://bugs.launchpad.net/bugs/1723562
Title:
Kernels
Thank you for taking the time to report this bug and helping to make
Ubuntu better.
I was just looking for kernel-related apt bugs and came across this
report.
It seems likely to me, given that it's had only one affected user in
this time, that this was caused by filesystem corruption or a hardwa
** Tags added: kernel-autoremove
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to apt in Ubuntu.
https://bugs.launchpad.net/bugs/1615381
Title:
apt-get autoremove may remove current kernel
Status in apt package in Ubuntu:
** Tags added: kernel-autoremove
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to apt in Ubuntu.
https://bugs.launchpad.net/bugs/1637797
Title:
kernel referred to by /*.old autoremoved
Status in apt package in Ubuntu:
New
On Fri, Oct 13, 2017 at 01:22:23AM -, Dimitri John Ledkov wrote:
> > Can networkd be made to work without relying on this sysctl tweak? If
>
> No, as the alternative is what isc-dhcp /sbin/dhcp-client does that is
> flush current dhcp lease IP and add a new IP, meaning that networking
> is dro
What about server use cases that do not have networkd installed? There
are complex network setups out there, such as HA with
corosync/pacemaker, OpenStack Neutron, and that kind of thing. If this
fix were SRU'd, will all of these things in the wild cope with this
sysctl change?
Can networkd be mad
> This update also applies other safe-looking options, which are
currently also already applied via sysctls shipped in other packages
SRUs are supposed to be minimal to minimise regression risk. Do you have
an SRU justification for this set of changes, please? Are they related
to this bug, and if
Public bug reported:
As reported in https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=878107
The patch, as Ondřej says, clearly shouldn't be able to make anything
worse, appears likely to fix the current mariadb-10.1 dep8 failure on
s390x and ppc64el, and likely may fix other latent bugs on those
> 13:47 Hi guys, anybody from Bug Control here can please switch
bug 1132736 xorg-lts-trusty from Confirmed to Won't Fix? Please see last
comment for rationale. Thanks!
Users may still want to upgrade from an EOL release to a supported
release though. Surely we should encourage this!
I think the
This also affects Artful running a sid container in lxd. Nothing is
particularly MySQL specific I here I think, since the failure happens
before MySQL runs at all. The only special systemd things I see in the
service unit are the use of ExecStartPre on a bash script and
PermissionsStartOnly=true. T
AFAICT, /usr/share/mysql/mysql-systemd-start is never run:
Aug 18 10:53:51 autopkgtest-lxd-mnbewo systemd[1]: Starting MySQL Community
Server...
-- Subject: Unit mysql.service has begun start-up
-- Defined-By: systemd
-- Support: https://www.debian.org/support
--
-- Unit mysql.service has begun
On Wed, Aug 09, 2017 at 04:28:43PM -, Iiro Laiho wrote:
> Cannot reproduce. Maybe this has something to do with VirtualBox.
Sounds like a race.
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to cups in Ubuntu.
https://bugs.
Some IRC discussion on this: https://irclogs.ubuntu.com/2017/08/09
/%23ubuntu-devel.html#t11:32
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to apt in Ubuntu.
https://bugs.launchpad.net/bugs/1709603
Title:
apt {upgrade,inst
I have filed bug 1709603 to track my request of having "apt update"
called automatically, as really it's independent of Scott's request for
--is-necessary here.
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to apt in Ubuntu.
ht
Public bug reported:
I think that this should be tracked in its own separate bug tracking my
specific UX objection to the current status quo.
See
https://bugs.launchpad.net/ubuntu/+source/apt/+bug/1429285/comments/5,
subsequent discussion and
https://twitter.com/chr1sa/status/894048628284604416
> IMHO, in the use case for "apt install", "apt update" should be
considered an implementation detail and the user shouldn't need to call
it directly. "apt install" should just do the right thing.
Here's basically the same opinion with some commentary from others:
https://twitter.com/chr1sa/status
Why does the ntp charm use ntpdate on Xenial, or need to use it?
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to ntp in Ubuntu.
https://bugs.launchpad.net/bugs/1706818
Title:
mismatched file locking since 1:4.2.8p4+dfsg-3ub
Note for the server team: what I'd like to determine is if the user
impact here justifies an SRU, and if it does, how we should prioritise
it.
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to ntp in Ubuntu.
https://bugs.launchp
Thank you for taking the time to report this bug and helping to make
Ubuntu better.
I've confirmed that the issue is as you describe in Xenial. Trusty pre-
dates the change to locking in ntp.if-up, so is consistent. Zesty is
also consistent in using flock in both places, as is Artful. So this bug
** Bug watch added: Debian Bug tracker #806556
https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=806556
** Also affects: ntp (Debian) via
https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=806556
Importance: Unknown
Status: Unknown
--
You received this bug notification because you
Uploaded.
** Changed in: rsyslog (Ubuntu)
Status: In Progress => Fix Committed
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to rsyslog in Ubuntu.
https://bugs.launchpad.net/bugs/1703987
Title:
New style permitnonker
Unsubscribing ~ubuntu-sponsors as there appears nothing left to sponsor.
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to rsyslog in Ubuntu.
https://bugs.launchpad.net/bugs/1429427
Title:
Unexplainable time jumps in CRON
St
Hello sgofferj, or anyone else affected,
Accepted rsyslog into trusty-proposed. The package will build now and be
available at
https://launchpad.net/ubuntu/+source/rsyslog/7.4.4-1ubuntu2.7 in a few
hours, and then in the -proposed repository.
Please help us by testing this new package. See
https
Thank you for the verification, Simon!
15:13 rbasak: My general rule of thumb is that
cosmetic/"polish" changes only need to go to devel and the stable
series' you care to fix, but real behavioural bug fixes can't skip
supported releases.
15:13 Because someone upgrading from xenial to yakkety
s
** Also affects: network-manager (Ubuntu Xenial)
Importance: Undecided
Status: New
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to network-manager in Ubuntu.
https://bugs.launchpad.net/bugs/1647283
Title:
WiFi bei
Hello Chow, or anyone else affected,
Accepted libzen into zesty-proposed. The package will build now and be
available at
https://launchpad.net/ubuntu/+source/libzen/0.4.34-1ubuntu0.17.04.1 in a
few hours, and then in the -proposed repository.
Please help us by testing this new package. See
https
Hello Chow, or anyone else affected,
Accepted libzen into yakkety-proposed. The package will build now and be
available at
https://launchpad.net/ubuntu/+source/libzen/0.4.33-3ubuntu0.16.10.1 in a
few hours, and then in the -proposed repository.
Please help us by testing this new package. See
htt
Hello Chow, or anyone else affected,
Accepted libzen into xenial-proposed. The package will build now and be
available at
https://launchpad.net/ubuntu/+source/libzen/0.4.32-1ubuntu0.16.04.1 in a
few hours, and then in the -proposed repository.
Please help us by testing this new package. See
http
Hello igor, or anyone else affected,
Accepted ntp into zesty-proposed. The package will build now and be
available at https://launchpad.net/ubuntu/+source/ntp/1:4.2.8p9+dfsg-
2ubuntu1.2 in a few hours, and then in the -proposed repository.
Please help us by testing this new package. See
https://
Hello igor, or anyone else affected,
Accepted ntp into trusty-proposed. The package will build now and be
available at https://launchpad.net/ubuntu/+source/ntp/1:4.2.6.p5+dfsg-
3ubuntu2.14.04.12 in a few hours, and then in the -proposed repository.
Please help us by testing this new package. See
Hello igor, or anyone else affected,
Accepted ntp into xenial-proposed. The package will build now and be
available at https://launchpad.net/ubuntu/+source/ntp/1:4.2.8p4+dfsg-
3ubuntu5.6 in a few hours, and then in the -proposed repository.
Please help us by testing this new package. See
https:/
Hello igor, or anyone else affected,
Accepted ntp into yakkety-proposed. The package will build now and be
available at https://launchpad.net/ubuntu/+source/ntp/1:4.2.8p8+dfsg-
1ubuntu2.2 in a few hours, and then in the -proposed repository.
Please help us by testing this new package. See
https:
I'm going to sponsor Christian's Trusty upload without review, wearing
my DMB hat. It's a technicality that he can't upload it; he already has
DMB approval to do so.
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to ntp in Ubunt
On Thu, Jul 06, 2017 at 01:32:00PM -, Julian Andres Klode wrote:
> I think automatic updating on old caches is not really the best idea,
> because it will always happen when you expect it the least. Or maybe you
> do in fact want the old one.
>From the perspective of users, I absolutely disagr
IMHO, in the use case for "apt install", "apt update" should be
considered an implementation detail and the user shouldn't need to call
it directly. "apt install" should just do the right thing. The same
applies to "apt-cache search", etc. It's seems quite tedious and
unnecessary to have to run bot
Do we know that this change won't be ABI impacting? Is this known, or
has anybody looked into this?
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to libzen in Ubuntu.
https://bugs.launchpad.net/bugs/1693850
Title:
libzen was
Hello Scott, or anyone else affected,
Accepted base-files into zesty-proposed. The package will build now and
be available at https://launchpad.net/ubuntu/+source/base-
files/9.6ubuntu13.1 in a few hours, and then in the -proposed
repository.
Please help us by testing this new package. See
https
16:03 kirkland: ^ what happens on first login? That'll still be
delayed, right? So the bug is being reduced in scope, but not being
fixed entirely?
16:03 If the first login is before the timer has run for the
first time, that is, which seems likely.
16:04 rbasak: true
16:04 rbasak: that's an
The verification of the Stable Release Update for less 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 encounter a reg
10:29 bdmurray: opinion on bug 1562308 please? It seems to me
that comment 17 is referring to some other bug, with no steps to
reproduce provided. OTOH cosmos-door has a reproducer and confirmed it
broken without and fixed with proposed, so I think this is OK to
release. Do you agree?
6:07 rbasa
** Also affects: ntp (Ubuntu Trusty)
Importance: Undecided
Status: New
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to ntp in Ubuntu.
https://bugs.launchpad.net/bugs/1593907
Title:
ntpdate startup routine prevents
Thank you for taking the time to report this bug and helping to make Ubuntu
better.
Since there isn't enough information in your report to differentiate between a
local configuration problem and a bug in Ubuntu, I'm marking this bug as
Incomplete.
If indeed this is a local configuration prob
** Changed in: systemd (Ubuntu)
Milestone: None => ubuntu-17.10
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to systemd in Ubuntu.
https://bugs.launchpad.net/bugs/1697730
Title:
Long boot time due to systemd-networkd-wa
** Changed in: unattended-upgrades (Ubuntu)
Status: Incomplete => Confirmed
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to unattended-upgrades in
Ubuntu.
https://bugs.launchpad.net/bugs/1689495
Title:
unattended-upg
The first I knew of it was an apport/whoopsie GUI popup, which then sent
me to this bug IIRC. I installed this machine fresh from an Artful
daily. The only relevant change I think I made was to add an apt proxy
in /etc/apt.conf.d/. I don't have any other information and didn't save
my traceback, as
(except in the development release, I suppose, but that wasn't the
reason I filed this bug)
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to unattended-upgrades in
Ubuntu.
https://bugs.launchpad.net/bugs/1692315
Title:
Packa
I'm wrong. It is.
** Changed in: unattended-upgrades (Ubuntu)
Status: Confirmed => Invalid
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to unattended-upgrades in
Ubuntu.
https://bugs.launchpad.net/bugs/1692315
Title:
On Thu, Jun 01, 2017 at 07:20:18AM -, Abhijith Gururaj wrote:
> @juliank I have configured the updater to use the main server.
> Downloading updates from the main server shouldn't cause such errors,
> right?
Some ISPs intercept their clients' downloads. The error is telling you
that the downlo
Hello Rodney, or anyone else affected,
Accepted isc-dhcp into xenial-proposed. The package will build now and
be available at https://launchpad.net/ubuntu/+source/isc-
dhcp/4.3.3-5ubuntu12.7 in a few hours, and then in the -proposed
repository.
Please help us by testing this new package. See
htt
Hello Rodney, or anyone else affected,
Accepted isc-dhcp into trusty-proposed. The package will build now and
be available at https://launchpad.net/ubuntu/+source/isc-
dhcp/4.2.4-7ubuntu12.10 in a few hours, and then in the -proposed
repository.
Please help us by testing this new package. See
ht
Hi Eric,
Sorry for the delay in getting back to this. As it has been a while I
have reviewed everything again from the beginning.
Can I confirm that by "with expected result" you mean that on
Trusty->Xenial upgrade, in both cases (isc-client-dhcp installed and
isc-client-dhcp-noddns installed) yo
601 - 700 of 1241 matches
Mail list logo