This got inot Debian experimental and synced from there
gdisk | 1.0.8-1 | impish | source, amd64,
arm64, armhf, i386, ppc64el, riscv64, s390x
** Changed in: gdisk (Ubuntu Impish)
Status: In Progress => Fix Released
** Changed in: gdisk (Ubuntu Xenial)
S
This was always wrong and old editions just "stay that wrong" without
further disturbing things there. The new code does it right and now also
has the feature to convert old broken disks.
So @fheimes this might be worth a release note entry?
--
You received this bug notification because you are
FYI it seems bug 1864020 talks about the same case.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1906266
Title:
After upgrade: "libvirt.libvirtError: Requested operation is not
valid: format of b
** Description changed:
+ [Impact]
+
+ * New libvirt got more strict in regard to file format specification.
+While this is generally the right approach it causes some issues for
+upgraders that have old image chains now failing.
+
+ * Upstream has added code to relax those checks und
** Changed in: busybox (Ubuntu)
Assignee: (unassigned) => Didier Roche (didrocks)
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1933979
Title:
[MIR] busybox package
To manage notifications ab
We clarified that Doko on 2021-03-11 really meant to MIR-ack the check on
libftdi.
Thereby this is now actually fully ready and waiting for an upload of fwupd to
pull it in.
Updating the state accordingly.
** Changed in: flashrom (Ubuntu)
Status: New => In Progress
** Changed in: libftdi
Thanks Brett, that confirms they are the same root cause and fixed by the same
solution.
Thanks.
And it also confirms that the test steps I've got from you will apply here.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.
This bug still has the template data that is supposed to be read and updated
when filing :-/
But from the log I see this is one of this kind
Setting up ubuntu-advantage-tools (27.1~16.04.1) ...
Traceback (most recent call last):
File "", line 2, in
ModuleNotFoundError: No module named 'uaclien
Chances are (https://bugs.launchpad.net/ubuntu/+source/ubuntu-advantage-
tools/+bug/1930121/comments/3) that this is due to a non-default python
on the system.
If you could check and report your python setup that could help.
If you have a non standard python please make this a duplicate to bug 193
Tanks Grant for spotting this!
Thereby I'll set this one to confirmed (while it isn't an issue of the PKG in
the archive you said we might be able to help with it still).
We have three more bugs that might be the same, but their report didn't include
the python3 details that made you spot it her
Chances are (https://bugs.launchpad.net/ubuntu/+source/ubuntu-advantage-
tools/+bug/1930121/comments/3) that this is due to a non-default python
on the system.
If you could check and report your python setup that could help.
If you have a non standard python please make this a duplicate to bug 193
Chances are (https://bugs.launchpad.net/ubuntu/+source/ubuntu-advantage-
tools/+bug/1930121/comments/3) that this is due to a non-default python
on the system.
If you could check and report your python setup that could help.
If you have a non standard python please make this a duplicate to bug 193
Both merged
** Changed in: probert (Ubuntu Groovy)
Status: Fix Committed => Fix Released
** Changed in: probert (Ubuntu)
Status: Fix Committed => Fix Released
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs
FYI: I uploaded the fix to Focal-unapproved for verification by the SRU
Team.
** Changed in: libvirt (Ubuntu Groovy)
Status: Invalid => Fix Released
** Changed in: libvirt (Ubuntu Focal)
Status: Triaged => In Progress
--
You received this bug notification because you are a member
"additionally testing during SRU verification that libvirt correctly
still rejects what it should"
I can try then, but I'm not 100% sure I can easily recreate that case.
If I can then sure, if not we should not block on it IMHO as the backported
code matches the >=Groovy behavior anyway.
--
You
Update as I've not forgotten this.
So far I was still not able to reproduce this myself, I was either having cases
where GTK+virtgl worked fine for my simple testing OR I had it broken but even
when trying to add SDL it didn't help.
Still I appreciate all the debug you have done and while GTK is
** Changed in: gdisk (Ubuntu Bionic)
Status: Incomplete => Invalid
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1931243
Title:
FTBFS in Impish on s390x
To manage notifications about this bu
Yes, having a centralized default available multi-size hugepage
mountpoints would still be nice to have.
** Changed in: libvirt (Ubuntu)
Status: Confirmed => Won't Fix
** Changed in: systemd (Ubuntu)
Status: Won't Fix => Confirmed
--
You received this bug notification because you
I know the bug is old, but I'm on a cleanup streak :-)
This wasn't (isn't anymore at least) in the source this was filed against.
It was in a transitional package up to xenial.
https://launchpad.net/ubuntu/xenial/amd64/open-iscsi-utils/2.0.873-3ubuntu13
And there removed by
https://bugs.launchpad.n
Public bug reported:
I've had a look at the changes in Debian since our last merge and they are ok,
but not super important.
https://salsa.debian.org/linux-blocks-team/open-iscsi/-/blob/master/debian/changelog
OTOH there is an upstream 2.1.4 which has a bunch of nice bug fixes.
https://gith
According to the discussion dnsmasq will revert to the upstream intended
behavior.
I added an open impish task to reflect that.
At the same time this makes network-mamager expose the test issue we initially
found it with.
An example can already be seen in
PPA: https://launchpad.net/~ci-train-ppa
I have not found any other test issues than the expected NM one.
So I'm uploading since - to some extend - we want to see if anything else
breaks.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1894619
** Merge proposal linked:
https://code.launchpad.net/~paelzer/ubuntu/+source/open-iscsi/+git/open-iscsi/+merge/405043
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1934290
Title:
Please merge 2.
As expected this is now ready in proposed and blocked on the NM test, example:
https://autopkgtest.ubuntu.com/results/autopkgtest-impish/impish/amd64/n/network-manager/20210701_151447_a29ef@/log.gz
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed
- (removed my comment that was not meant to be on the bug but the MRs) -
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1904362
Title:
[Wishlist] Disable hostname lookup by default for logwatch servi
Ok, as planned I can reproduce this in local autopkgtest.
Multiple hits on:
AssertionError: Regex didn't match: 'inet6 2600::[0-9a-f:]+/64 scope global
(?:tentative )?(?:mngtmpaddr )?(?:noprefixroute )?dynamic' not found in '14:
eth42@veth42: mtu 1500 qdisc noqueue state UP
group default qlen
FYI: Due to the package rename that we picked up from Debian this is now
blocked in the new queue.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1934290
Title:
Please merge 2.1.4 (bugfix release) fo
Hi Celina,
thanks for the info but that isn't the same issue that was discussed in this
bug.
Furthermore while enabling SMBv1 is a workaround to the problem you had it is
considered a huge security risk and therefore should be a last resort and only
for e.g. isolated environments.
I tried to fin
Hi,
unfortunately the logs you attached do not have much info that help debugging
this.
I can see it failed on install, but not what.
As the error message already asks you, did you see any issues in the extended
log?
$ journalctl -xe
Generally what it (re)starts is this, so how does that serv
Thank you for taking the time to report this bug and helping to make
Ubuntu better.
Since it seems likely to me that this is a local configuration problem,
rather than a bug in Ubuntu, I'm marking this bug as Incomplete.
If indeed this is a local configuration problem, you can find pointers
to ge
Thanks for the report Bill and even more for the awesome and detailed
explanations Matthias!
AFAICS there is nothing in here for Ubuntu to fix "right now". As versions
6.5/7.0 are releases we will pick them up but that isn't what this bug was
about.
Gladly config based solutions were found to h
Thank you, I think we have everything in place to check if this is
SRUable by a backport.
@Sergio / @Athos - I missed before that this was blocked mostly on
chained/real certificates :-/ Due to other fixes that I've done I have
means to set up and drive real cerbot based tests on canonistack. I
do
SRU template added to the bug in preparation to entering the SRU
process.
I've created a PPA with the identified change backported:
https://launchpad.net/~ci-train-ppa-service/+archive/ubuntu/4603/+packages
And a merge proposal along that
https://code.launchpad.net/~paelzer/ubuntu/+source/ap
The new NM tests were fine (even against the old dnsmasq due to the or in the
regex).
NM hit a few non related systemd test issues - I re-triggered those.
Finally I did now start the new NM tests against the blocked dnsmasq.
Overall that should hopefully resolve both and let them migrate.
--
Yo
[Summary]
This could be a somewhat straight forward case for the source itself.
It is a bit light on tests, but otherwise fine as it was pre-reviewed
in the former version being src:fuse.
The biggest problem is that we generally don't want duplication if we can avoid
it.
In this case I tried but
I've updated the bug itself to reflect that this might be foundations
territory.
** Changed in: fuse3 (Ubuntu)
Status: New => Incomplete
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1934510
T
dnsmasq tested all fine with the new NM.
Only the odd systemd blocker holds us back now.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1894619
Title:
[2.82 regression] router announcements have 'for
FYI: Passed the new queue now and entered testing.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1934290
Title:
Please merge 2.1.4 (bugfix release) for impish
To manage notifications about this bug
The DNSmasq change is in impish as well.
Since we (intentionally) referenced but not closed the bug by the upload I'll
have to tag that manually.
** Changed in: dnsmasq (Ubuntu Impish)
Status: Triaged => Fix Released
--
You received this bug notification because you are a member of Ubunt
1. vmwgfxctrl command- in open-vm-tools-desktop .deb package.
- requires access to libdrm and libudev to be compiled and will dlopen()
at runtime. Will quietly exit if runtime not available on guest VM.
Build dependencies: libdrm, libudev
Add to open-vm-tools-desktop package:
2. The open-vm-tools source release contains a complete example of a
tools.conf. Please package this open-vm-tools/tools.conf file ass
/etc/vmware-tools/tools.conf.example
It is nice to have the full example, but the suggested place is not the common
one to put those. It would correctly go
usr/bin/vmware-alias-import
ok, adding that
usr/lib/libguestStoreClient.so.0*
That should be automatically go into the -dev package.
We will have to check if it is needed anywhere else.
usr/lib/open-vm-tools/plugins/vmsvc/libguestStore.so
usr/lib/open-vm-tools/plugins/vmsvc
vmware-alias-import is installed by the makefiles, no need for a debian
rule.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1933143
Title:
Open-vm-tools release 11.3.0 has been released
To manage n
** Changed in: flashrom (Ubuntu)
Status: In Progress => Fix Committed
** Changed in: fwupd (Ubuntu)
Status: In Progress => Fix Committed
** Changed in: libftdi1 (Ubuntu)
Status: In Progress => Fix Committed
--
You received this bug notification because you are a member of U
** Changed in: python-rtslib-fb (Ubuntu Focal)
Assignee: Utkarsh Gupta (utkarsh) => (unassigned)
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1865037
Title:
make the service fail gracefully if
Public bug reported:
Trying to debug a LP issue
To be set invalid immediately.
** Affects: mdevctl (Ubuntu)
Importance: Undecided
Status: Invalid
** Changed in: mdevctl (Ubuntu)
Status: New => Invalid
--
You received this bug notification because you are a member of Ubuntu
After a few trials we will give it a show in qemu-system-gui for now which
means we will promote it as planned (Staying close to Debian which is +1 on my
SDL reenabling there as well).
If it turns out too buggy we will remove it, it it is (somewhat expected) great
for some but misleading for oth
I was testing the non-proxy case as requested by Robie.
@Horst - could you do the real proxy case testing?
P.S. After so many years of joking about "localhorst" is is great to
meet THE localhorst :-)
Setup is following:
https://cwiki.apache.org/confluence/display/httpd/OCSPStapling
After enab
Yeah this was meant to be an extra-exclude, all of this was going on for
so long that I missed to merge this before the promotion. Thanks for the
reminder Steve!
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.ne
Public bug reported:
Our least favorite (most breakage) and least useful (LXD >>> libvirt-lxc) test
broke again.
It didn't show up in the sniff testing, but reliably fails on the upload of
https://launchpad.net/ubuntu/+source/libvirt/7.4.0-0ubuntu1
It fails across all architectures.
...
debian
ok, reproducible in local autopkgtest and only happening with 7.4.0 in proposed
but not 7.0.0 in impish-release.
I'll try to debug that later on ...
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/19349
This is a bug due to upstream and happens due to cgroup/systemd handling
https://libvirt.org/git/?p=libvirt.git;a=commit;h=9c1693eff4
https://bugs.archlinux.org/task/70174
https://bugzilla.opensuse.org/show_bug.cgi?id=1183247
https://gitlab.com/libvirt/libvirt/-/issues/182
Affects everyone.
I
Working
...
autopkgtest [09:37:13]: test smoke-lxc: [---
Libvirt >=7.1.0 is known to fail LXC handling with systemd <248 (issue 182) -
skipping.
error: failed to get domain 'sl'
error: failed to get domain 'sl'
autopkgtest [09:37:14]: test smoke-lxc: ---]
sndio resolved via https://code.launchpad.net/~paelzer/ubuntu-
seeds/+git/ubuntu/+merge/405363
** Changed in: sndio (Ubuntu)
Status: Incomplete => Fix Released
** Changed in: sndio (Ubuntu)
Assignee: Christian Ehrhardt (paelzer) => (unassigned)
--
You received th
** 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/1930430
Title:
Apache2 Certificate Chain Verification within Proxy not Working aft
Systemd 248.3 was published into impish just now and other than on arch-
linux it is not resolving the case for Ubuntu.
As I said this test is the least important and the most failing for us,
I'll bump the skip to be unconditional and we will adapt once the
upstream issue (which we track) is resol
** Description changed:
Please backport anbox 0.0~git20210106-1 (multiverse) from hirsute to
focal.
Reason for the backport:
Doing development and testing for modern Android requires newer versions of
anbox. The upstream maintainer of anbox confirmed it would
Public bug reported:
I'm not sure yet if this is flaky or a real issue, but I'm filing it to
avoid multiple people analyzing the same.
The Qemu 6.0 upload
https://launchpad.net/ubuntu/+source/qemu/1:6.0+dfsg-1~ubuntu2 triggers a test
failure like
https://autopkgtest.ubuntu.com/results/autopkgte
Hi Brian,
that seems to be a different issue - maybe related but different.
I'd ask you to file a new bug and add all kind of info, how are things set up
in detail, are there config changes that make it a good/bad case, does it only
happen with new versions and on which release ...?
--
You rece
My Repro-tests indeed seem to indicate that really qemu 6.0 is the trigger for
this,
but as I said HW is rather unavailable at the moment. I was told that the MAAS
is serviced but should be back soon - so I'll have a look later when this one
is available again.
--
You received this bug notific
Added https://github.com/vmware/open-vm-tools/issues/314 that was
identified by upstream as the related upstream issue (that is
unfortunately dormant).
** Bug watch added: github.com/vmware/open-vm-tools/issues #314
https://github.com/vmware/open-vm-tools/issues/314
** Also affects: open-vm-to
There were dependent bug files to get the remaining old projects updated.
Maybe there were more but I was seeing bug 1935665 - so here as an FYI.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1934510
As part of this we also need to ensure that - aside the lib - also the
userspace binaries are properly depended on.
`fuse` and `fuse3` both provide sort of the same binaries with /bin/fusermount3
/sbin/mount.fuse3 vs /bin/fusermount / /sbin/mount.fuse.
Since those two are mutually exclusive we pr
> product engineering has access to PPC systems in maas?!? sigh...that sure
> would be nice
> for sustaining engineering to have access to also :(
That might sound more appealing than it is, the HW is often broken the
availability is worse than gold-nuggets and I think I never got a system
with
While canonistack was breaking hard on me last week I managed to get an
instance running today.
Trying to reproduce the issue in there ...
Atfer a long while of upgrades, dependencies,
I was running with impish (as-is) vs impish+qemu6.0.
It was very reproucible working with 5.2 and always f
Isolated case
$ sudo env SELECTED_TESTS="TEST-08-*" debian/tests/upstream
It runs a VM Guest to do init stuff and that seems to break:
There are suspicious logs like systemd crashing, but those also exist
(to some extent) in the good case. I compared that:
$ grep -e "of user 0 dumped core" -e "
As root:
$ mkdir /tmp/debugtest
$ export ARTIFACT_DIRECTORY=/tmp/debugtest
$ export TEST_SHOW_JOURNAL=warning
$ export TEST_REQUIRE_INSTALL_TESTS=0
$ export TEST_PREFER_NSPAWN=1
$ export NO_BUILD=1
$ export SELECTED_TESTS="TEST-08-*"
./test/run-integration-tests.sh
Reproduces the issue, it will k
The service has a StartPre that is like
ExecStartPre=rm -f /failed /testok
And that works to reproduce:
bash-5.1# rm -f /failed /testok
Segmentation fault (core dumped)
In fact this RM is very very sad:
-bash-5.1# rm /doesnotexist
Segmentation fault (core dumped)
-bash-5.1# touch /doesexist
-b
I tried the same on a bare metal machine (now one is available for a
short time).
Got the new systemd source and test, ran it with qemu 5.2 and it is failing.
But not randomly, the same subset of tests fails on bare metal with 5.2.
But now they all fail on an OOM.
kvm: OS terminated: OS panic
Since the bare metal case reports a memory issue on the crashes, let us
give it a bit more memory - with 2G it works finally.
Instead of the other tests in launchpad/canonistack this uses KVM mode
via "-machine accel=kvm -enable-kvm -cpu host". Switching that instead
to "-machine accel=tcg" it fai
>From here I was switching to qemu 6.0 on the bare metal machine.
6.0-KVM - works
6.0-TCG - works
But running the testsuite itself fails (due to using only 512M ram).
I found that switching from testsuite-08 to testsuite-09 allowed me to get into
bad-mode in TCG (with enough memory, but into the
I installed a ppc64 impish cloud image (all fine) but then ran it in TCG
mode (to check if I can trigger the same).
That starts it like:
/usr/bin/qemu-system-ppc64le -name guest=i-systemdtest,debug-threads=on -S
-object
{"qom-type":"secret","id":"masterKey0","format":"raw","file":"/var/lib/libvi
quotearg seems to be from gettext
https://sources.debian.org/src/gettext/0.21-4/gettext-tools/gnulib-lib/quotearg.c/?hl=1#L1
And is at least related in a few of the crashes (but not exclusively).
I wonder if the new TCG implements an instruction differently that now breaks.
--
You received thi
Backtraces
Two times (on rm, only slight variations)
Program terminated with signal SIGSEGV, Segmentation fault.
#0 0x0798b9f361d0 in quotearg_buffer_restyled
(buffer=buffer@entry=0x798b9f60130 "'",
buffersize=buffersize@entry=256,
arg=arg@entry=0x800369e19807 , argsize=argsize@e
We've had similar cases int he past where new releases glibc or compiler had
new instructions breaking the TCG mode.
So I spawned a focal and a bionic image - and then remodeled them to run in
emulation mode.
And indeed Bionic works without any crashes, so it must be something in the
guest tha
Hmm, I can blindly read through the qemu commit log and try rebuilds or even a
bisect at some point. But maybe this is already known. Since I'm soon on EOD I
wonder if we could mirror this to IBM (now that we know a bit more) if this is
a known issue to point us at an existing discussion or fix.
I've collected the instructions that are around the failures and it is
suspicious for
lbzx / lvx / ld
All failures are around those:
Impish
ubuntu@i-systemdtest:/var/crash$ for i in */CoreDump; do p=$(dirname $i | tr -d
'.0123456789' | tr '_' '/' ); gdb $p $i -q -ex "x/-10i \$pc" -ex "x/3i \$p
Before - Tried to start and fail in a container
root@python-rtslib-fb-lp1865037-groovy:~# systemctl status target.service
● target.service - Restore LIO kernel target configuration
Loaded: loaded (/lib/systemd/system/target.service; disabled; vendor
preset: enabled)
Active: inactive (de
> And by the way, I just tested the old setup with your full
> recommendation, adding the BEFORE= statement and it finally stopped the
> I/O errors. I can now take the time to transition properly.
Awesome, glad I could help!
And it might help others who find this bug if affected by a similar cas
Impish is open, uploaded if there.
Not sure if that is still in some early-cycle-complexity - we will see and SRU
it then once complete there.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1802005
Ti
Ok, Impish is complete and thereby all ready.
I uploaded the very same fix to hirsute for the SRU team to consider.
The SRU template is still present from "last time :-/"
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.lau
Thank you Marco and Sebastien,
> * the launchpad buglist has been triaged a bit and fixed issues closed
Thanks!
>From your bug cleanup did you spot any kind of setup/HW that you want to
>restrict/exclude?
Was there any common pattern that makes up most of the formerly seen bad
reports?
> * the
Interesting but that is a fail in a VM
https://autopkgtest.ubuntu.com/results/autopkgtest-impish/impish/amd64/u/update-motd/20210430_205617_c8474@/log.gz
And https://autopkgtest.ubuntu.com/packages/update-motd looks broken on
all architectures.
--
You received this bug notification because you a
On Mon, May 3, 2021 at 10:20 AM Ludovic Rousseau
<1892...@bugs.launchpad.net> wrote:
>
> opensc-pkcs11.so is a PKCS#11 lib so the its API conforms to the
> standard defined in https://docs.oasis-
> open.org/pkcs11/pkcs11-base/v2.40/os/pkcs11-base-v2.40-os.html
Thanks Ludovic for adding the expert
I can confirm that as of now it runs fine against
- impish
- impish + UA from proposed
- imposh proposed
The test installs all users of update-motd
It does not list ubuntu-advantage-tools but since they are in the image
one would think that it still would be there.
The test intention is:
1. run
** Tags added: update-excuse
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1926660
Title:
autopkgtests fail due to new update-motd snippet
To manage notifications about this bug go to:
https://bugs
** Changed in: libmanette (Ubuntu)
Status: Confirmed => New
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1918446
Title:
[MIR] libmanette
To manage notifications about this bug go to:
https:
** Changed in: fence-agents (Ubuntu)
Assignee: (unassigned) => Dan Streetman (ddstreet)
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1927004
Title:
[MIR] fence-agents
To manage notifications
** Changed in: telegraf (Ubuntu)
Assignee: (unassigned) => Didier Roche (didrocks)
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1926321
Title:
[MIR] telegraf
To manage notifications about thi
** Changed in: libmanette (Ubuntu)
Assignee: (unassigned) => Christian Ehrhardt (paelzer)
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1918446
Title:
[MIR] libmanette
To man
@Thomas - there is a leftover task here and I've filed [1] for it in the new
tracker.
What is the right state to move this bug here into now?
[1]: https://gitlab.com/qemu-project/qemu/-/issues/137
** Bug watch added: gitlab.com/qemu-project/qemu/-/issues #137
https://gitlab.com/qemu-project/q
rashers, etc) in Debian or Ubuntu or Upstream
- no dependency on webkit, qtwebkit, seed or libgoa-*
- not part of the UI for extra checks
** Changed in: libmanette (Ubuntu)
Assignee: Christian Ehrhardt (paelzer) => (unassigned)
** Changed in: libmanette (Ubuntu)
Status: New =>
On Fri, May 7, 2021 at 8:55 PM Sebastien Bacher
<1918...@bugs.launchpad.net> wrote:
>
> @Christian thanks for the review! one question though
>
> > Problems:
> > - d/watch is present but currently dysfunctional - since you might miss
> > updates
> > fixing that should be done before promotion.
>
> I'm on the focal version of devscripts 2.20.2ubuntu2
> Trying 2.21.1ubuntu1 in Impish ...
Ok, that is it ...
I guess for the MIR we can keep it as is, still slightly sad that it
fails with the uscan of the latest LTS.
I mean it isn't a new format version that would only be supported in
the new o
On Fri, May 7, 2021 at 9:55 PM Sebastien Bacher
<1918...@bugs.launchpad.net> wrote:
>
> The dh_missing change is commit to the packaging vcs now
>
> https://salsa.debian.org/gnome-team/libmanette/-/commits/debian/master/
Thanks that should be enough for that aspect.
--
You received this bug noti
On Fri, May 7, 2021 at 9:55 PM Sebastien Bacher
<1918...@bugs.launchpad.net> wrote:
>
> Having the gir1.2-manette-0.2 bindings promoted is fine, it's standard
> practice for the dev to depends on those and wanted there
Ok, I know it is standard (hence the auto-include) but some teams and
some pack
Thanks Sebastien, all tasks I've brought up are handled (some of my mail
replies might appear here delayed, but we are complete).
I guess we are ready and you can make the change that will pull this
into main.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which i
Also Xenial:
https://code.launchpad.net/~chad.smith/ubuntu/+source/ubuntu-advantage-tools/+git/ubuntu-advantage-tools/+merge/402474
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1927795
Title:
27.0
On Mon, May 10, 2021 at 11:11 AM Sebastien Bacher
<1918...@bugs.launchpad.net> wrote:
>
> Thanks Christian! I've subscribed desktop-packages, should the bug be
> fix commited now? I will merge or sync webkitgtk in the next days which
> should pull it to main and I will promote once uploaded
"In pr
Thanks Ioanna for the bug.
In our discussion that we already had I've suggested how to fix it in
code and I think this still is a valid approach to harden against
whatever was causing it in the first place.
After initial creation the file is meant to stay as-is to allow users
to do customization
301 - 400 of 10728 matches
Mail list logo
