Per discussions in the appropriate PR for Calamares[1], this should be
done in network-manager itself.
The appeal is more custom approaches. Downstreams and vendors of Ubuntu.
[1] https://github.com/calamares/calamares/pull/2284
** Also affects: network-manager (Ubuntu)
Importance: Undecided
** Tags added: rls-nn-incoming
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to ubuntu-settings in Ubuntu.
https://bugs.launchpad.net/bugs/2020110
Title:
Migrate netplan settings to this package
Status in network-manager pa
** Changed in: snapd (Ubuntu)
Importance: Undecided => High
** Tags added: rls-nn-incoming
--
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/1951491
Title:
Can't run snap
** Changed in: software-properties (Ubuntu)
Assignee: (unassigned) => Simon Quigley (tsimonq2)
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to software-properties in
Ubuntu.
https://bugs.launchpad.net/bugs/2061214
Ti
** Changed in: software-properties (Ubuntu)
Importance: Undecided => Critical
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to software-properties in
Ubuntu.
https://bugs.launchpad.net/bugs/2061214
Title:
Software sources
** Summary changed:
- Software sources not correctly updated after upgrade and/or new installs
+ [SRU] Software Sources is not compatible with deb822
** Summary changed:
- [SRU] Software Sources is not compatible with deb822
+ Software Sources is not compatible with deb822
** Summary changed:
2-22T14:20:00
** Also affects: software-properties (Ubuntu Noble)
Importance: Critical
Assignee: Simon Quigley (tsimonq2)
Status: Confirmed
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to softwa
Looks like this was already sponsored:
https://launchpad.net/ubuntu/+source/dbus/1.14.4-1ubuntu1
Please re-subscribe ~ubuntu-sponsors if further action is required.
Thank you!
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to d
** Changed in: vim (Ubuntu)
Status: Fix Committed => Fix Released
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to vim in Ubuntu.
https://bugs.launchpad.net/bugs/1864424
Title:
new vim version in 20.04 sets mouse=a by
Looks like this was sponsored (thanks William!), unsubscribing the
sponsors team.
** Changed in: coreutils (Ubuntu)
Status: New => Fix Committed
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to coreutils in Ubuntu.
http
Hi Nathan!
I have no problem with the patch, given the author. That being said, it
would be useful to send this delta up to Debian if at all possible.
Please consider it. :)
Also, it's best not to modify changelog entries that exist in Debian.
I'm dropping this before uploading:
wpa (2:2.10-9)
> It's not clear to me that changing the casper user to use this uid
won't badly confuse the installer when it comes time to create the
actual user account, or at least cause gid 1000 to be skipped.
It's not clear to me that it will. Casper doesn't touch the squashfs
that ends up on the installed
** Changed in: systemd (Ubuntu)
Status: New => Confirmed
** Changed in: systemd (Ubuntu)
Importance: Undecided => High
--
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/bu
> It's not clear to me that changing the casper user to use this uid
won't badly confuse the installer when it comes time to create the
actual user account, or at least cause gid 1000 to be skipped.
After some testing with the newly-uploaded casper, I can confirm this is not
the case. I tested wi
Hi Tobias, thanks for your interest in this bug!
While I did not do a code review of the patch itself, I have some general
feedback on the diff and the bug report itself that I hope you find helpful:
- The version should be 1.6.2-0ubuntu1.1 instead of 1.6.2-0ubuntu2, following
Stable Release Up
Just to catch the bug report up with the IRC discussion:
we got away with it in casper because we knew there weren't going to
be 899 IDs allocated in this range in the installer context, and the casper
user goes away post-install
systemd doesn't statically set them, it allocates them using "fi
** Bug watch added: Debian Bug tracker #1029785
https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1029785
** Also affects: systemd (Debian) via
https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1029785
Importance: Unknown
Status: Unknown
--
You received this bug notification beca
** Tags removed: update-excuse
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to python3-defaults in
Ubuntu.
https://bugs.launchpad.net/bugs/2002660
Title:
networkx incompatible with numpy 1.24
Status in networkx package in
LGTM, sponsored, thank you!
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to libunwind in Ubuntu.
https://bugs.launchpad.net/bugs/2004039
Title:
libunwind 1.6.2-0 assumes 4k page sizes and crashes on systems with
bigger pa
> the next casper upload will regress the current version of the fix
I'm all in favor of a better longer-term fix replacing this one being
tracked in systemd, but an unrelated casper upload regressing this
change prior to a longer-term solution being in place will cause issues
with all amd64 live
Please remember to mention the bug number in the changelog entry.
Additionally, for stylistic purposes, I changed this:
* Merge from Debian unstable. The remaining difference is the change
for ignoring test results on i386 to avoir failure.
To this:
* Merge from Debian Unstable (LP: #20
It looks like this upload has already been sponsored, thanks.
** Changed in: sysvinit (Ubuntu)
Status: New => Fix Committed
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to sysvinit in Ubuntu.
https://bugs.launchpad.net
** Changed in: curl (Ubuntu)
Status: New => Fix Committed
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to curl in Ubuntu.
https://bugs.launchpad.net/bugs/2008123
Title:
Please merge 7.88.1-1 into lunar
Status in cur
** Changed in: sudo (Ubuntu)
Status: New => Fix Committed
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to sudo in Ubuntu.
https://bugs.launchpad.net/bugs/2007698
Title:
Please merge 1.9.13p1-1 into lunar
Status in s
Sponsored, thank you!
** Changed in: grilo-plugins (Ubuntu)
Status: New => Fix Committed
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to grilo-plugins in Ubuntu.
https://bugs.launchpad.net/bugs/2007623
Title:
Merge
fects: vim (Ubuntu)
Importance: Wishlist
Assignee: Simon Quigley (tsimonq2)
Status: In Progress
** Affects: vim (Ubuntu Focal)
Importance: Wishlist
Assignee: Simon Quigley (tsimonq2)
Status: In Progress
** Affects: vim (Ubuntu Jammy)
Importance: Wishlist
** Changed in: vim (Ubuntu Lunar)
Status: Fix Committed => Fix Released
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to vim in Ubuntu.
https://bugs.launchpad.net/bugs/1996087
Title:
Ensure supported codenames are acc
Public bug reported:
autopkgtests are pretty reliably failing[1] on armhf due to the
following (single) test failure:
638s === FAILURES
===
638s TestApportValgrind.test_valgrind_min_installed
638s
** Tags added: rls-nn-incoming
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to apport in Ubuntu.
https://bugs.launchpad.net/bugs/2043713
Title:
armhf autopkgtests fail due to
TestApportValgrind.test_valgrind_min_installed
** Changed in: cron (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 cron in Ubuntu.
https://bugs.launchpad.net/bugs/2044015
Title:
please merge cron 3.0pl1-178 from Debia
** Changed in: busybox (Ubuntu)
Status: New => Incomplete
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to busybox in Ubuntu.
https://bugs.launchpad.net/bugs/2022927
Title:
Busybox mount fails to mount Snaps
Status i
Unsubscribing sponsors, since there are merge conflicts.
** Merge proposal linked:
https://code.launchpad.net/~xypron/ubuntu/+source/rsyslog/+git/rsyslog/+merge/457541
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to rsysl
tance: Undecided => Medium
** Changed in: calamares (Ubuntu)
Status: New => Fix Released
** Changed in: calamares (Ubuntu)
Milestone: None => ubuntu-23.11
** Changed in: calamares (Ubuntu)
Assignee: (unassigned) => Simon Quigley (tsimonq2)
--
You received this bug notific
** Changed in: lubuntu-update-notifier (Ubuntu)
Importance: Undecided => Medium
** Changed in: lubuntu-update-notifier (Ubuntu)
Status: New => Confirmed
** Changed in: lubuntu-update-notifier (Ubuntu)
Milestone: None => ubuntu-24.04-feature-freeze
** Changed in: lubuntu-update-noti
Uploaded with a changelog tweak. It looks like there is precedent for
this, but it's in the SRU team's hands now.
DEP-3 patch headers next time? ;)
** Also affects: modemmanager (Ubuntu Jammy)
Importance: Undecided
Status: New
** Changed in: modemmanager (Ubuntu)
Status: New =>
** Changed in: gtk+3.0 (Ubuntu)
Importance: Undecided => Critical
** Changed in: gtk+3.0 (Ubuntu)
Status: New => Confirmed
** Tags added: rls-nn-incoming
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to gtk+3.0 in U
signed) => Simon Quigley (tsimonq2)
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to gtk+3.0 in Ubuntu.
https://bugs.launchpad.net/bugs/2047705
Title:
Packaging ships /etc/gtk-3.0/settings.ini, forcing the GTK3 theme to
A bug still exists here. GTK as a standalone package should not set Yaru
as a default, especially if it doesn't declare it as a dependency.
lxqt-session was simply a workaround. The Ubuntu Desktop Team needs to
move this to their default settings package, and adjust GTK to
appropriately read $XDG_
I very much dislike reviewing packages this way. For a package to be in
the sponsorship queue, it needs to have a debdiff, not a debian.tar.xz.
I understand that it's a new upstream release, but that does not excuse
the need for a debdiff, even if you *also* include these files.
I'm uploading this
> 34174 lines in this case is not plausibly reviewable.
I typically use filterdiff to get the packaging changes, and review
specific source files as necessary (including copyright changes in the
diff, which can be important, even if you're just using a script for
it).
Thanks for your help here. I
Daniel, if you'd like to iterate on this (a debdiff for an ubuntu2
upload), it would be appreciated.
If you don't have the time, say the word, this looks like a simple fix.
...on everything but i386. What's up with that?
--
You received this bug notification because you are a member of Ubuntu
T
The reason I essentially blindsponsored this was out of faith and
courtesy for the Desktop Team.
Lubuntu does similar things, but we have a merge party from Debian once
a cycle. If your response would be "we don't follow Debian," *I get it*,
but once or twice a cycle a merge should really be looke
Rik mentioned a common mistake that I've been trying harder to catch
(but didn't in this case, to my great frustration)...
If we're doing a merge and an orig tarball already exists in Debian,
always always ALWAYS grab that one instead of using uscan or finding the
tarball yourself. It breaks tooli
This is now blocking a Lubuntu feature goal. I tested this locally with
my bluetooth earbuds, and have been streaming audio with no problems.
Uploaded Gianfranco's packaging with some minor tweaks.
Please, we *need* to merge this from Debian *this* cycle. The Security
Team will NOT be happy when
Following the dependency chain through to the cause for the i386 builds,
binfmt-support should be added to the i386 allowlist. This may be a bug
in evolution-data-server in the case libebook-contacts-1.2-4 can build
without libphonenumber8-protobuf32 - for now, blanket-disabling that
dependency in
> In other words, asking an Archive Admin to build binfmt-support on
i386.
I have stopped short of this so far because I'm entirely unsure if we
still need that build dependency in the first place. Debian doesn't have
it, and I'm not sure I see rationale on our end for it.
There is probably somet
Is there any terminal in which the default is actually readable?
** Changed in: vim (Ubuntu)
Assignee: (unassigned) => Simon Quigley (tsimonq2)
** Changed in: vim (Ubuntu)
Milestone: None => ubuntu-24.04-feature-freeze
** Changed in: vim (Ubuntu)
Importance: Undecided =&g
Daniel, I don't want you to feel burned over this. That wiki page does
seem quite rational, and I appreciate that you linked it. I'm reading
some mixed feelings, so let me be clear: thank you for the work you
*are* able to put into this.
Both Gianfranco and I are Ubuntu Core Developers but are als
** Changed in: bluez (Ubuntu)
Status: Fix Released => In Progress
** Summary changed:
- BlueZ release 5.71
+ BlueZ release 5.71 and merge from Debian
** Changed in: bluez (Ubuntu)
Assignee: Daniel van Vugt (vanvugt) => Simon Quigley (tsimonq2)
--
You received this bug notifi
At first I was just going to say, ell-dev isn't built on i386 and it's
not arch:all, of course it will need an i386 allowlist entry! However,
this is the output I'm getting:
```
$ check-mir
Checking support status of build dependencies...
* debhelper-compat does not exist (pure virtual?)
* libel
I'm pretty shocked, I ran a local sbuild with this and yet it still
FTBFS. Doing an ubuntu2 upload as a fixup.
I would think that because we use the published tarball and not the
upstream source like Debian does, that would affect our ability to ship
the -test package.
Something's up with my loca
> Please also remember to commit proposed changes to
https://git.launchpad.net/~bluetooth/bluez
Force pushing my local commits over, sorry not sorry. :)
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to bluez in Ubuntu.
https:/
> Simon, ell already has a recent approved MIR LP: #1971738
Er, the binary packages in question don't.
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to bluez in Ubuntu.
https://bugs.launchpad.net/bugs/2047780
Title:
BlueZ r
https://github.com/vim/vim/pull/13825
I will test this first in Debian, upload it there, then do a merge.
** Changed in: vim (Ubuntu)
Status: Confirmed => In Progress
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to vi
It looks like I was overly strict with the MIR compliance, which sort of
balances out this bug as a whole. :)
After it migrates, Gianfranco or myself will try reverting ubuntu2 to
see if we can push those two packages forward.
--
You received this bug notification because you are a member of Ubu
** Changed in: vim (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 vim in Ubuntu.
https://bugs.launchpad.net/bugs/2047982
Title:
Highlighting of patches offers insufficie
** Also affects: iptables (Ubuntu Jammy)
Importance: Undecided
Status: New
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to iptables in Ubuntu.
https://bugs.launchpad.net/bugs/2049318
Title:
free(): double free det
** Changed in: vim (Ubuntu)
Status: In Progress => Fix Released
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to vim in Ubuntu.
https://bugs.launchpad.net/bugs/2040011
Title:
[SRU] Ensure supported codenames are accur
This was missing a build dependency on python3-pygments (which is in
Main), I added it.
Testing well with my Beats Flex, YouTube Music with the Firefox Nightly
snap. I can adjust the latency offset with no issue, and blueman DTRT
with connecting and disconnecting. Popped open journalctl and syslog
** Changed in: bluez (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 bluez in Ubuntu.
https://bugs.launchpad.net/bugs/2049352
Title:
Package BlueZ 5.72 for Noble
Status
** Patch added: "delta-delta.patch"
https://bugs.launchpad.net/ubuntu/+source/console-setup/+bug/2049885/+attachment/5741436/+files/delta-delta.patch
** Changed in: console-setup (Ubuntu)
Status: New => Fix Committed
--
You received this bug notification because you are a member of Ub
this update is to download a package from the Lunar
archive, and open the changelog with Vim. Instead of the changelog
release (e.g. "lunar") showing as red, it should show as blue.
** Affects: vim (Ubuntu)
Importance: Undecided
Assignee: Simon Quigley (tsimonq2)
S
** Description changed:
In several stable releases of Ubuntu, Vim has information regarding
releases that are outdated. It would be optimal for Vim to grab this
data from distro-info-data (or similar), but unfortunately that is not
the case. Therefore, the list needs to be updated.
Th
I'm just generally curious, does debootstrap function differently
with/without this patch?
I'd imagine it either goes off the task, or a level lower than the
metapackages.
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to ubunt
Ah, right. Debootstrap is more low-level, thanks.
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to ubuntu-meta in Ubuntu.
https://bugs.launchpad.net/bugs/2028769
Title:
[SRU] missing riscv64 packages ubuntu-desktop, ubuntu-d
** Changed in: software-properties (Ubuntu)
Assignee: Simon Quigley (tsimonq2) => Hans P Möller (hmollercl)
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to software-properties in
Ubuntu.
https://bugs.launchpad.net/b
The bug was only fixed in our Calamares configuration and still needs to
be fixed in initramfs-tools.
Adjusting bug statuses appropriately and adding the release tag. I'll
ping vorlon and xnox on IRC to get their take.
** Also affects: calamares-settings-ubuntu (Ubuntu)
Importance: Undecided
Unsubscribing the sponsors team as there's nothing left to sponsor here.
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to gtk+3.0 in Ubuntu.
https://bugs.launchpad.net/bugs/1822380
Title:
Thunar right-click menu not expanded
Unsubscribing the Sponsors Team as there is no debdiff to sponsor. Poked
the Security Team.
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to jackd2 in Ubuntu.
https://bugs.launchpad.net/bugs/1833479
Title:
libjack-jackd2-0 d
Before this is sponsored, I would like to see Brian's comment on the
other bug addressed; does this need to go to Eoan, any other releases,
or Debian?
Thanks, and please resubscribe sponsors when this is answered.
--
You received this bug notification because you are a member of Ubuntu
Touch see
** Package changed: initramfs-tools (Ubuntu) => calamares (Ubuntu)
** No longer affects: lubuntu-meta (Ubuntu)
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to initramfs-tools in Ubuntu.
https://bugs.launchpad.net/bugs/1835095
I'll take this one.
** Changed in: software-properties (Ubuntu)
Assignee: (unassigned) => Simon Quigley (tsimonq2)
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to software-properties in
Ubunt
** Changed in: zbar (Ubuntu)
Status: New => Fix Released
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to zbar in Ubuntu.
https://bugs.launchpad.net/bugs/1757915
Title:
Please port your package away from Qt 4
Status
Attached is a debdiff applicable to 2.3.2-1, which is in Sid.
** Patch added: "1-2.3.2-1-to-2.3.2-1ubuntu1.debdiff"
https://bugs.launchpad.net/ubuntu/+source/slang2/+bug/1770062/+attachment/5136512/+files/1-2.3.2-1-to-2.3.2-1ubuntu1.debdiff
--
You received this bug notification because you a
64075
* Set OBJDIR to src/x32objs on x32. Closes: #890545
-- Alastair McKinstry Mon, 19 Feb 2018 16:59:12
+
** Affects: slang2 (Ubuntu)
Importance: Wishlist
Assignee: Simon Quigley (tsimonq2)
Status: In Progress
--
You received this bug notification because you are a memb
Public bug reported:
Currently Qt 4 has been dead upstream and we are starting to have
problems maintaining it, like for example in the OpenSSL 1.1 support case.
Following in the footsteps of Debian[1], all packages directly or
indirectly depending on qt4-x11 must either get ported to Qt 5 and
up
** Description changed:
Currently Qt 4 has been dead upstream and we are starting to have
problems maintaining it, like for example in the OpenSSL 1.1 support case.
Following in the footsteps of Debian[1], all packages directly or
indirectly depending on qt4-x11 must either get ported t
** Description changed:
Currently Qt 4 has been dead upstream and we are starting to have
problems maintaining it, like for example in the OpenSSL 1.1 support case.
Following in the footsteps of Debian[1], all packages directly or
indirectly depending on qt4-x11 must either get ported t
** Changed in: kdesudo (Ubuntu)
Status: New => Confirmed
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to autopilot-qt in Ubuntu.
https://bugs.launchpad.net/bugs/1757320
Title:
Remove Qt 4 from the archive
Status in
kdesudo can be removed from the archive as soon as my merged
ubuntu-release-upgrader change has been uploaded and has migrated.
$ reverse-depends src:kdesudo
Reverse-Depends
===
* ubuntu-release-upgrader-qt(for kdesudo)
$ reverse-depends -b src:kdesudo
No reverse dependencies foun
Public bug reported:
Currently Qt 4 has been dead upstream and we are starting to have
problems maintaining it, like for example in the OpenSSL 1.1 support
case.
Following in the footsteps of Debian[1], all packages directly or
indirectly depending on qt4-x11 (like this one) must either get porte
Public bug reported:
Currently Qt 4 has been dead upstream and we are starting to have
problems maintaining it, like for example in the OpenSSL 1.1 support
case.
Following in the footsteps of Debian[1], all packages directly or
indirectly depending on qt4-x11 (like this one) must either get porte
Public bug reported:
Currently Qt 4 has been dead upstream and we are starting to have
problems maintaining it, like for example in the OpenSSL 1.1 support
case.
Following in the footsteps of Debian[1], all packages directly or
indirectly depending on qt4-x11 (like this one) must either get porte
Public bug reported:
Currently Qt 4 has been dead upstream and we are starting to have
problems maintaining it, like for example in the OpenSSL 1.1 support
case.
Following in the footsteps of Debian[1], all packages directly or
indirectly depending on qt4-x11 (like this one) must either get porte
Instead of filing one megabug, I filed separate bugs:
https://bugs.launchpad.net/ubuntu/+bugs?field.tag=qt4-removal
Thanks.
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to qt4-x11 in Ubuntu.
https://bugs.launchpad.net/bugs/17
Public bug reported:
Currently Qt 4 has been dead upstream and we are starting to have
problems maintaining it, like for example in the OpenSSL 1.1 support
case.
Following in the footsteps of Debian[1], all packages directly or
indirectly depending on qt4-x11 (like this one) must either get porte
Public bug reported:
Currently Qt 4 has been dead upstream and we are starting to have
problems maintaining it, like for example in the OpenSSL 1.1 support
case.
Following in the footsteps of Debian[1], all packages directly or
indirectly depending on qt4-x11 (like this one) must either get porte
** Tags added: qt4-removal
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to qt4-x11 in Ubuntu.
https://bugs.launchpad.net/bugs/1757320
Title:
Remove Qt 4 from the archive
Status in qt4-x11 package in Ubuntu:
New
Bug desc
** Bug watch added: Debian Bug tracker #875021
https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=875021
** Also affects: libdbusmenu-qt (Debian) via
https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=875021
Importance: Unknown
Status: Unknown
--
You received this bug notification
** Bug watch added: Debian Bug tracker #875215
https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=875215
** Also affects: syncevolution (Debian) via
https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=875215
Importance: Unknown
Status: Unknown
--
You received this bug notification b
** Bug watch added: Debian Bug tracker #875246
https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=875246
** Also affects: zbar (Debian) via
https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=875246
Importance: Unknown
Status: Unknown
--
You received this bug notification because yo
** Also affects: ubuntu-meta (Ubuntu)
Importance: Undecided
Status: New
** No longer affects: ubuntu
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to ubuntu-meta in Ubuntu.
https://bugs.launchpad.net/bugs/1758551
Ti
Thank you for taking the time to report this bug and helping to make Ubuntu
better. We are sorry that we do not always have the capacity to look at all
reported bugs in a timely manner. There have been many changes in Ubuntu since
that time you reported the bug and your problem may have been fix
Seems like this is fixed now.
** Changed in: qtbase-opensource-src (Ubuntu)
Status: Confirmed => Fix Released
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to qtbase-opensource-src in
Ubuntu.
https://bugs.launchpad.net/
Is this still a bug?
** Changed in: qtdeclarative-opensource-src (Ubuntu)
Status: Confirmed => Incomplete
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to qtdeclarative-opensource-
src in Ubuntu.
https://bugs.launchpad.
*** This bug is a duplicate of bug 1756238 ***
https://bugs.launchpad.net/bugs/1756238
** This bug has been marked a duplicate of bug 1756238
gdebi-gtk broken in 18.04 error: unable to read filedescriptor flags
--
You received this bug notification because you are a member of Ubuntu
Touch
is is the whole stack that needs these changes. I
also want to know that these changes work...
** Changed in: indicator-datetime (Ubuntu)
Assignee: (unassigned) => Simon Quigley (tsimonq2)
** Changed in: indicator-messages (Ubuntu)
Assignee: (unassigned) => Simon Quigley (tsi
On further investigation, out of the packages marked as affected, only
indicator-datetime needed the change.
Uploaded to the PPA.
** Changed in: indicator-messages (Ubuntu)
Assignee: Simon Quigley (tsimonq2) => (unassigned)
** Changed in: indicator-power (Ubuntu)
Assignee: Si
> Ready for the archive IMO. :) Thanks!
Cool!
> Are you saying that that line is there already for all the other
indicator-* packages?
Yep.
> Can you please also check out the unity-* packages, for instance those
I mentioned in the community hub.
I'd like a full list of packages needed here be
Thank you for taking the time to report this bug and helping to make
Ubuntu better. Unfortunately, we cannot work on this bug because your
description didn't include enough information. You may find it helpful
to read "How to report bugs effectively"
http://www.chiark.greenend.org.uk/~sgtatham/bugs
1 - 100 of 378 matches
Mail list logo
