** Changed in: gerbera (Ubuntu)
Status: New => In Progress
--
You received this bug notification because you are a member of Ubuntu
Server, which is subscribed to asterisk in Ubuntu.
https://bugs.launchpad.net/bugs/1863026
Title:
Remove my_bool typedef workaround
To manage
** Changed in: gearmand (Ubuntu)
Status: New => In Progress
--
You received this bug notification because you are a member of Ubuntu
Server, which is subscribed to asterisk in Ubuntu.
https://bugs.launchpad.net/bugs/1863026
Title:
Remove my_bool typedef workaround
To manage
** Changed in: argus-clients (Ubuntu)
Status: New => In Progress
** Changed in: asterisk (Ubuntu)
Status: New => In Progress
** Changed in: gambas3 (Ubuntu)
Status: New => In Progress
** Changed in: clickhouse (Ubuntu)
Status: New => In Progress
** Changed in: cppdb
Public bug reported:
During the previous development cycle, when mysql 8 was introduced, too
many reverse deps failed due to the my_bool removal. It was then decided
to put that back in to let the reverse dependencies build again.
Now we should try to drop it one more time, and instead fix the
I just pushed the merge and uploaded source code.
--
You received this bug notification because you are a member of Ubuntu
Server, which is subscribed to the bug report.
https://bugs.launchpad.net/bugs/1861316
Title:
ubuntu 20.04: libnss-winbind:386 should remain
To manage notifications
** Changed in: samba (Ubuntu)
Status: Triaged => In Progress
--
You received this bug notification because you are a member of Ubuntu
Server, which is subscribed to the bug report.
https://bugs.launchpad.net/bugs/1861316
Title:
ubuntu 20.04: libnss-winbind:386 should remain
To manage
$ rmadison crmsh
crmsh | 1.2.5+hg1034-1ubuntu3 | trusty | source, all
crmsh | 1.2.5+hg1034-1ubuntu4 | trusty-updates | source, all
crmsh | 2.2.0-1 | xenial | source, ...
crmsh | 3.0.1-3ubuntu1| bionic/universe | source, all
crmsh | 3.0.1-3ubuntu1
Acording to:
https://bugs.launchpad.net/ubuntu/+source/crmsh/+bug/1205019/comments/10
It was proposed to main again by doko.
I'll wait full pacemaker migration - and test crmsh installation - to
close this bug.
--
You received this bug notification because you are a member of Ubuntu
Server,
Thanks Steve!! Package is back to archive, moving on with what needed
this.
--
You received this bug notification because you are a member of Ubuntu
Server, which is subscribed to the bug report.
https://bugs.launchpad.net/bugs/1862928
Title:
python-crypto (i386) needs rebuild in Focal
Correct! I missed that part. Thank you!
--
You received this bug notification because you are a member of Ubuntu
Server, which is subscribed to the bug report.
https://bugs.launchpad.net/bugs/1862947
Title:
crmsh should be taken back to -main
To manage notifications about this bug go to:
MERGE:
https://code.launchpad.net/~rafaeldtinoco/ubuntu/+source/pacemaker/+git/pacemaker/+merge/378958
PPA: https://launchpad.net/~rafaeldtinoco/+archive/ubuntu/lp1862947
--
You received this bug notification because you are a member of Ubuntu
Server, which is subscribed to the bug report.
Public bug reported:
crmsh is currently the most tested cluster resource manager
configuration tool we have for Ubuntu (pcs being the second one, and
already scheduled for more tests in order to replace it in a near
future).
With that said, currently crmsh is found at -universe:
09:43 you see that python3-crypto has per-arch deb files
09:43 I added a comment in the case and subscribed steve
09:43 while your conter-xample of ansi just has one called
..._all.deb
09:43 — rafaeldtinoco checks
09:43 AFAICS python3-crypto contains no arch dependent files
09:44 so it could
Steve,
Looks like python3-crypto package is not in the i386 archive.
Judging by:
https://launchpad.net/ubuntu/+source/python-crypto
https://launchpad.net/ubuntu/+source/python-crypto/+publishinghistory
https://launchpad.net/ubuntu/+source/python-crypto/2.6.1-11ubuntu2
I think this relates to having i386 in amd64 installed OSes only
currently. Since I'm using a i386 only container, it can't figure out
the correct python dependency (asking for amd64). If I build
python3-crypto in an i386 container dependencies are correctly figured
out.
** Summary changed:
-
Yep, I had those as well, thought it was my dev environmnet. But, if you
say yours install fine there is no need for a rebuild.. weird.. I'll re-
check here, thank you!
--
You received this bug notification because you are a member of Ubuntu
Server, which is subscribed to the bug report.
Ah okay, perhaps your environment is amd64 ? I'm testing this in an i386
environmnet (LXD container) only. Still getting:
python3-crypto:amd64 : Depends: python3:amd64 (< 3.9) but it is not going to
be installed
Depends: python3:amd64 (>= 3.7~) but it is not going to
be
Last MR push:
https://code.launchpad.net/~rafaeldtinoco/ubuntu/+source/samba/+git/samba/+merge/378664/comments/994088
Looks good but depends on fix for:
https://bugs.launchpad.net/ubuntu/+source/python-crypto/+bug/186292
--
You received this bug notification because you are a member of Ubuntu
Public bug reported:
If you try:
(c)rafaeldtinoco@sambai386:~/.../ubuntu$ apt-get install python3-crypto
Reading package lists... Done
Building dependency tree
Reading state information... Done
You might want to run 'apt --fix-broken install' to correct these.
The following packages have unmet
Related bug:
https://bugs.launchpad.net/ubuntu/+source/python-crypto/+bug/1862928
As python-crypto needed a rebuild to allow libnss-winbind and winbind to be
installable (due to its dependencies).
--
You received this bug notification because you are a member of Ubuntu
Server, which is
VERIFICATION:
(k)rafaeldtinoco@ocfs2:~$ apt-cache policy linux-image-5.4.0-14-generic
linux-image-5.4.0-14-generic:
Installed: 5.4.0-14.17
Candidate: 5.4.0-14.17
Version table:
*** 5.4.0-14.17 500
500 http://br.archive.ubuntu.com/ubuntu focal-proposed/main amd64
Packages
21 matches
Mail list logo
