I'm guessing this might be a quirk of the armhf runners:
test_tree_garbage (__main__.ChrootRunner)
copied source tree contains only expected files ... : Operation not permitted
cp: cannot create special file ‘/tmp/tmp36ee0r77/chroot//dev/null’:
Operation not permitted
cp: cannot create special
If someone is interested in the proper upstream fixes, please file a new
bug and we will need to fix bionic and prepare a distinct SRU for the
existing releases.
--
You received this bug notification because you are a member of Ubuntu
Server Team, which is subscribed to the bug report.
On Wed, Nov 1, 2017 at 7:15 AM, Jan Gutter <1720...@bugs.launchpad.net> wrote:
> @arges
>
> Hi, would you need any more testing from us?
Nope, your part is done. All SRUs have to bake for 7 days in -proposed
to shake out regressions.
--
You received this bug notification because you are a
On 20.10.2017 [08:24:37 -0700], Nish Aravamudan wrote:
> On 20.10.2017 [07:18:15 -], Jan Gutter wrote:
> > I had a look at the two proposals and could not spot any obvious
> > mistakes:
> >
> > - the correct upstream git commit has been cherry-picked
> > - I don't have any objections to
On 20.10.2017 [07:18:15 -], Jan Gutter wrote:
> I had a look at the two proposals and could not spot any obvious
> mistakes:
>
> - the correct upstream git commit has been cherry-picked
> - I don't have any objections to attribution or log messages
>
> Thanks again for shepherding this one
On 20.10.2017 [07:09:00 -], Jan Gutter wrote:
> I concur with option 2), unnecessary deviation will just cause
> confusion.
Thank you for confirming that!
> Regarding the other buffer sizes, the last time I looked they were
> mostly OK. The issue reared its head in this particular case
I have set up two MPs with the adjustments (it looks like Monique's
latest debdiffs followed path 2) from my previous comment already) to
the DEP3 headers that I think make the most sense. Please take a look at
them and if you approve the changes I will upload them.
I note also there are a number
@mvandenberg,
Couple of nits in your debdiffs.
1) changelogs are targetting UNRELEASED, please update to xenial and
trusty respectively.
2) Is there a reason your fix is different than the fix upstream/Debian?
Does Debian need your version instead?
3) Please use appropriate DEP3 headers
On 17.10.2017 [08:56:17 -], Jan Gutter wrote:
> @nacc I built from source to verify that the one-liner is directly
> responsible for fixing and breaking the issue (inherent paranoia). I did
> test with the binaries and they worked.
Ah ok, yeah -- I guess that's reasonable, and is a good
@jangutter: I'm not sure why you built from source? I assume you
actually tested the version in 17.04 and it worked.
The proper solution is to backport the Debian change to xenial and
trusty, most likely. A git repository that can be used with `git-ubuntu`
(sudo snap install --classic
** Also affects: iproute2 (Ubuntu Xenial)
Importance: Undecided
Status: New
** Also affects: iproute2 (Ubuntu Zesty)
Importance: Undecided
Status: New
** Changed in: iproute2 (Ubuntu)
Status: Confirmed => Fix Released
** Changed in: iproute2 (Ubuntu Xenial)
11 matches
Mail list logo
