[Bug 2065491] Re: [BPO] far2l/2.6.0~beta+ds-1ubuntu0.1 from noble-updates
** Changed in: far2l (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/2065491 Title: [BPO] far2l/2.6.0~beta+ds-1ubuntu0.1 from noble-updates To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/far2l/+bug/2065491/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 2065359] Re: [BPO] lsp-plugins/1.2.15-2 from ocular to noble
Thank you for your contribution! ** Changed in: lsp-plugins (Ubuntu Noble) Status: New => Fix Released -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/2065359 Title: [BPO] lsp-plugins/1.2.15-2 from ocular to noble To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/lsp-plugins/+bug/2065359/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 2008583] Re: VMware nested under KVM stopped working on 5.19 kernel on Ryzen: Invalid VMCB.
hwe is not handled by the backports team, so I'm unsubscribing us. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/2008583 Title: VMware nested under KVM stopped working on 5.19 kernel on Ryzen: Invalid VMCB. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/2008583/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 2062140] Re: [BPO] libreoffice 7.6.6 for jammy
Accepted, thank you! ** Changed in: libreoffice (Ubuntu Jammy) Status: In Progress => Fix Released -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/2062140 Title: [BPO] libreoffice 7.6.6 for jammy To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/libreoffice/+bug/2062140/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 2059029] Re: proposed-migration for vdeplug-slirp 0.1.0-2build1
the package now built on armhf too. ** Changed in: vdeplug-slirp (Ubuntu) Status: New => Fix Released -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/2059029 Title: proposed-migration for vdeplug-slirp 0.1.0-2build1 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/vdeplug-slirp/+bug/2059029/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
Re: [Bug 2058634] Re: scribus-doc puts docs in wrong place
I see what's happening there... That's due to snap's containerization efforts, which blocks loading of files from /usr/share/scribus. If you use any other non-snap browser it should just work. I don't use snaps, no, so I'm having no good ideas on how to fix that. And ISTR I had a good reason to have the symlinks that way instead of installing in usr/share/doc amd symlinking on usr/share/scribus, but i could always try again, as that's likely the easier workaround to those blocks. On Sat, 23 Mar 2024, 9:50 pm Ian Bruntlett, <2058...@bugs.launchpad.net> wrote: > Hi Mattia, > > On Sat, 23 Mar 2024 at 20:30, Mattia Rizzolo <2058...@bugs.launchpad.net> > wrote: > > > You are right that scribus needs them in what is the "wrong" location > > for the Debian policy, but I remember doing things so that it would work > > for both. > > > > The package ships everything in /usr/share/scribus/doc and then sets up > > symlinks from e.g. /usr/share/doc/scribus/de to ../../scribus/doc/de > > (i.e. /usr/share/scribus/doc/de). > > > > What is not working for you? > > > > Well, Firefox (as a snap), for some reason or another, can't access the > files. > > /usr/share/doc/scribus/en$ xdg-open index.html > Yields this error page in Firefox: > > > > > *File not foundFirefox can’t find the file at > /usr/share/doc/scribus/en/index.html.Check the file name for > capitalisation or other typing errors.Check to see if the file was > moved, renamed or deleted.* > > /usr/share/scribus/doc/en$ xdg-open index.html > Yields this error page in Firefox: > > > > > *File not foundFirefox can’t find the file at > /usr/share/scribus/doc/en/index.html.Check the file name for > capitalisation or other typing errors.Check to see if the file was > moved, renamed or deleted.* > Is it possible that the snap system does not like the symlink approach? > > Do you have Firefox installed as a snap? Do you have scribus-doc installed? > That way, you should be able to experience this problem, too. > > BW, > > > Ian > > -- > -- ACCU - Professionalism in programming - http://www.accu.org > -- My writing - https://sites.google.com/site/ianbruntlett/ > -- Free Software page - > https://github.com/ian-bruntlett/TECH-Manuals/blob/main/tm-free-software.md > > -- > You received this bug notification because you are subscribed to > scribus-doc in Ubuntu. > https://bugs.launchpad.net/bugs/2058634 > > Title: > scribus-doc puts docs in wrong place > > Status in scribus-doc package in Ubuntu: > Incomplete > > Bug description: > the issue is that scribus does not use a standard location for > its docs ... typically deb packages ship their docs in > /usr/share/doc/ while scribus ships them in > /usr/share//doc ... > > This is important because the Firefox snap only has permissions to > access files in the standard location. > > ProblemType: Bug > DistroRelease: Ubuntu 22.04 > Package: scribus 1.5.8+dfsg-2 > ProcVersionSignature: Ubuntu 6.5.0-26.26~22.04.1-generic 6.5.13 > Uname: Linux 6.5.0-26-generic x86_64 > ApportVersion: 2.20.11-0ubuntu82.5 > Architecture: amd64 > CasperMD5CheckResult: unknown > CurrentDesktop: ubuntu:GNOME > Date: Thu Mar 21 10:32:17 2024 > InstallationDate: Installed on 2020-08-07 (1321 days ago) > InstallationMedia: Ubuntu 20.04.1 LTS "Focal Fossa" - Release amd64 > (20200731) > SourcePackage: scribus > UpgradeStatus: Upgraded to jammy on 2022-08-15 (584 days ago) > > To manage notifications about this bug go to: > > https://bugs.launchpad.net/ubuntu/+source/scribus-doc/+bug/2058634/+subscriptions > > Launchpad-Notification-Type: bug > Launchpad-Bug: distribution=ubuntu; sourcepackage=scribus-doc; > component=multiverse; status=Incomplete; importance=Undecided; > assignee=None; > Launchpad-Bug-Tags: amd64 apport-bug jammy packaging wayland-session > Launchpad-Bug-Information-Type: Public > Launchpad-Bug-Private: no > Launchpad-Bug-Security-Vulnerability: no > Launchpad-Bug-Commenters: ian-bruntlett mapreri > Launchpad-Bug-Reporter: Ian Bruntlett (ian-bruntlett) > Launchpad-Bug-Modifier: Ian Bruntlett (ian-bruntlett) > Launchpad-Message-Rationale: Subscriber (scribus-doc in Ubuntu) > Launchpad-Message-For: mapreri > > -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/2058634 Title: scribus-doc puts docs in wrong place To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/scribus-doc/+bug/2058634/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 2058634] Re: scribus-doc puts docs in wrong place
You are right that scribus needs them in what is the "wrong" location for the Debian policy, but I remember doing things so that it would work for both. The package ships everything in /usr/share/scribus/doc and then sets up symlinks from e.g. /usr/share/doc/scribus/de to ../../scribus/doc/de (i.e. /usr/share/scribus/doc/de). What is not working for you? ** No longer affects: scribus (Ubuntu) ** Changed in: scribus-doc (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/2058634 Title: scribus-doc puts docs in wrong place To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/scribus-doc/+bug/2058634/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1962614] Re: [BPO] memtest86+/5.31b+dfsg-4 from Jammy to Focal
Hi, in the last backporters team meeting we decided to approve this backport. We'd still like to see some of those bugs you mentioned properly fixed in focal itself (as an SRU), but we recognize that doing so would be a non-trivial amount of work and as such probably not a good use of your time since this proposed backport has good reasons to exist on its own. As such, please feel free to continue with the process (send a debdiff against the package in jammy and upload). ** Changed in: memtest86+ (Ubuntu) Status: Incomplete => Confirmed -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1962614 Title: [BPO] memtest86+/5.31b+dfsg-4 from Jammy to Focal To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/memtest86+/+bug/1962614/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1968448] Re: package libxslt1.1:i386 1.1.34-4 failed to install/upgrade: package is in a very bad inconsistent state; you should reinstall it before attempting configuration
Something like this normally indicates a previously interrupted installation or something of the like. Please contact user support for more help. ** Changed in: libxslt (Ubuntu) Status: New => Invalid -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1968448 Title: package libxslt1.1:i386 1.1.34-4 failed to install/upgrade: package is in a very bad inconsistent state; you should reinstall it before attempting configuration To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/libxslt/+bug/1968448/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1716656] Re: Plugins not loading
I just synced it. ** Changed in: entangle (Ubuntu Jammy) Status: In Progress => Fix Released -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1716656 Title: Plugins not loading To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/entangle/+bug/1716656/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1968076] Re: [BPO] ipmctl with support for CPS hardware
then you should prepare the change (likely in the form of a debdiff against what's currently in jammy, or an upload to a ppa) and attach it here, then subscribe the ~ubuntu-sponsors team. (also note that we expect your backports to have been tested in the target release, I'll assume you've done that) -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1968076 Title: [BPO] ipmctl with support for CPS hardware To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/ipmctl/+bug/1968076/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1968076] Re: [BPO] ipmctl with support for CPS hardware
Do you have a sponsor lined up for this? The backporters team by themselves don't do it. ** Also affects: ipmctl (Ubuntu Focal) Importance: Undecided Status: New ** Changed in: ipmctl (Ubuntu) Status: New => Fix Released -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1968076 Title: [BPO] ipmctl with support for CPS hardware To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/ipmctl/+bug/1968076/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1967003] Re: [BPO] obfs4proxy/0.0.13-1 from jammy
The backports team does not prepare nor sponsor uploads to backports, only review them. You should find somebody interested in doing the work, testing it, and maintain it, as well as a sponsor for it. ** Also affects: obfs4proxy (Ubuntu Focal) Importance: Undecided Status: New ** Changed in: obfs4proxy (Ubuntu) Status: Confirmed => Invalid ** Changed in: obfs4proxy (Ubuntu Focal) 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/1967003 Title: [BPO] obfs4proxy/0.0.13-1 from jammy To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/obfs4proxy/+bug/1967003/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1963829] Re: [BPO] primecount/7.2+ds-6 from jammy
We would be fine with this backport, but I don't see it in the queue. Also, the text is not mentioning anything about what testing has been done to it, which we expect. Please note that we (backports team) do *not* sponsor backports, so you should find a sponsor for it yourself. ** Also affects: primecount (Ubuntu Focal) Importance: Undecided Status: New ** Changed in: primecount (Ubuntu) Status: New => Invalid ** Changed in: primecount (Ubuntu Focal) 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/1963829 Title: [BPO] primecount/7.2+ds-6 from jammy To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/primecount/+bug/1963829/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
Re: [Bug 1965800] Re: debhelper in focal-backports not usable for i386 package building (missing dependency)
So it would need 2 addition to the i386 whitelist. Feel free to bring an archive administrator in the loop, I think it's only them who have the power to do that (if we want to go through that route). Except that I just realized that rpm (and debugedit) in focal are in universe. So it would also need a MIR, which is definitely not happening for a stable release. I also guess that's the reason debugedit was split off rpm. So I suppose we either need to check whether backporting debugedit would make it build on i386, or revert that change in debhelper. On Tue, 22 Mar 2022, 1:31 pm David Ward, <1965...@bugs.launchpad.net> wrote: > I am able to build src:rpm for focal i386 using pbuilder, as long as > p7zip-full:i386 is built first. > > -- > You received this bug notification because you are a member of Ubuntu > Backporters, which is subscribed to the bug report. > https://bugs.launchpad.net/bugs/1965800 > > Title: > debhelper in focal-backports not usable for i386 package building > (missing dependency) > > To manage notifications about this bug go to: > > https://bugs.launchpad.net/ubuntu/+source/debhelper/+bug/1965800/+subscriptions > > > -- > ubuntu-backports mailing list > ubuntu-backpo...@lists.ubuntu.com > Modify settings or unsubscribe at: > https://lists.ubuntu.com/mailman/listinfo/ubuntu-backports > -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1965800 Title: debhelper in focal-backports not usable for i386 package building (missing dependency) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/debhelper/+bug/1965800/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1965800] Re: debhelper in focal-backports not usable for i386 package building (missing dependency)
I think we have three choices here: 1. revert Matthias' change from debhelper/13.3.4ubuntu1 (2021-03-19) that make use of debugedit (honestly I don't even understand *why* he did that) 2. backport debugedit too (honestly I don't remember if that would be enough to make it build on i386, however, or it also needs an addition to the i386 whitelist) 3. get the archive admins to add src:rpm in the i386 whitelist, and rebuild it (if that's enough to make it build and doesn't require more). I'd be for option 1 here. comments welcome. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1965800 Title: debhelper in focal-backports not usable for i386 package building (missing dependency) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/debhelper/+bug/1965800/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1965855] Re: p7zip source package needs "Multiarch: foreign" in debian/control
that's hardly the reason that debhelper/focal-backports is uninstallable on i386. Remember that Multi-Arch fields are used for multi-arch installations, that are irrelevant for things like native builds, and are totally unused in buildds and such. ** Changed in: p7zip (Ubuntu) Status: New => Fix Released -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1965855 Title: p7zip source package needs "Multiarch: foreign" in debian/control To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/p7zip/+bug/1965855/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1965758] Re: [BPO] debhelper/13.6ubuntu1 from jammy to bionic, focal, impish
@teward: I'm pretty sure that bug only affects -backports: according to the debian bug the commit introducing it is 6067bc2f, which was first available in debhelper 13.4, which is only in jammy and -backports. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1965758 Title: [BPO] debhelper/13.6ubuntu1 from jammy to bionic, focal, impish To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/debhelper/+bug/1965758/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1965758] Re: [BPO] debhelper/13.6ubuntu1 from jammy to bionic, focal
tbf, I don't think this is actually *urgent* and can really just stay there for another week. ** Summary changed: - [BPO] debhelper/13.6ubuntu1 from jammy to bionic, focal + [BPO] debhelper/13.6ubuntu1 from jammy to bionic, focal, impish -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1965758 Title: [BPO] debhelper/13.6ubuntu1 from jammy to bionic, focal, impish To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/debhelper/+bug/1965758/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1965758] Re: [BPO] debhelper/13.6ubuntu1 from jammy to bionic, focal
Oh, that's probably a good reason to update the backport indeed, that I've been procrastinating. Unfortunately at this time I'm quite busy so I wouldn't be able to do it before next Monday at the earliest. Personally I'm fine if somebody else take it and I'll later review the diff; I don't expect anything "interesting" in this task either. ** Also affects: debhelper (Ubuntu Bionic) Importance: Undecided Status: New ** Also affects: debhelper (Ubuntu Impish) Importance: Undecided Status: New ** Also affects: debhelper (Ubuntu Focal) Importance: Undecided Status: New ** Changed in: debhelper (Ubuntu) Status: New => Fix Released -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1965758 Title: [BPO] debhelper/13.6ubuntu1 from jammy to bionic, focal, impish To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/debhelper/+bug/1965758/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1964390] Re: Inkscape will not launch on Ubuntu 22.04
As suspected, since in debian the very same bug was reported against 1.1.2-3 Well, I don't have time to debug this now, besides when I tried I couldn't reproduce it. I'm unassigning me, I'll take it when/if I can if nobody beats me to it. ** Bug watch added: Debian Bug tracker #1006697 https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1006697 ** Also affects: inkscape (Debian) via https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1006697 Importance: Unknown Status: Unknown ** Changed in: inkscape (Ubuntu) Assignee: Mattia Rizzolo (mapreri) => (unassigned) -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1964390 Title: Inkscape will not launch on Ubuntu 22.04 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/inkscape/+bug/1964390/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
Re: [Bug 1964390] Re: Inkscape will not launch on Ubuntu 22.04
The thing is, that patch is also fixing a crash in some cases (more importantly, when run with --batch as part of the build process of some other packages), so I'm kind of unhappy to push it and regress that, although I see the point of this being a "worse" bug. On Thu, 10 Mar 2022, 7:40 pm Erich Eickmeyer , <1964...@bugs.launchpad.net> wrote: > I've got this fixed, but I don't want to upload just yet as I might be > stepping on some toes. > > ** Changed in: inkscape (Ubuntu) >Status: Confirmed => In Progress > > ** Changed in: inkscape (Ubuntu) > Assignee: (unassigned) => Erich Eickmeyer (eeickmeyer) > > ** Changed in: inkscape (Ubuntu) >Importance: Undecided => High > > -- > You received this bug notification because you are subscribed to Ubuntu. > https://bugs.launchpad.net/bugs/1964390 > > Title: > Inkscape will not launch on Ubuntu 22.04 > > Status in inkscape package in Ubuntu: > In Progress > > Bug description: > Inkscape will not launch on Ubuntu 22.04. Running on a terminal > reports no messages, it just immediately exits: > > qwerty@qwerty-asus-g14:~$ inkscape > qwerty@qwerty-asus-g14:~$ > > The AppImage from the official website does not have this issue. > --- > ProblemType: Bug > ApportVersion: 2.20.11-0ubuntu78 > Architecture: amd64 > CasperMD5CheckResult: unknown > CurrentDesktop: GNOME > DistroRelease: Ubuntu 22.04 > InstallationDate: Installed on 2015-12-13 (2278 days ago) > InstallationMedia: Xubuntu Core 15.10 - amd64 - 20151022 > NonfreeKernelModules: nvidia_modeset nvidia > Package: inkscape 1.1.2-1ubuntu1 > PackageArchitecture: amd64 > ProcEnviron: >TERM=xterm-256color >PATH=(custom, no user) >XDG_RUNTIME_DIR= >LANG=en_US.UTF-8 >SHELL=/bin/bash > ProcVersionSignature: Ubuntu 5.15.0-18.18-generic 5.15.12 > RebootRequiredPkgs: Error: path contained symlinks. > Tags: jammy > Uname: Linux 5.15.0-18-generic x86_64 > UpgradeStatus: Upgraded to jammy on 2022-02-14 (23 days ago) > UserGroups: adm audio cdrom dialout dip fax floppy libvirt lpadmin > netdev plugdev render sambashare scanner sudo tape vboxusers video > _MarkForUpload: True > > To manage notifications about this bug go to: > > https://bugs.launchpad.net/ubuntu/+source/inkscape/+bug/1964390/+subscriptions > > > -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1964390 Title: Inkscape will not launch on Ubuntu 22.04 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/inkscape/+bug/1964390/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1951601] Re: [BPO] simplestreams/0.1.0-48-gb936edd4-0ubuntu1 from Jammy to bionic, focal
** Summary changed: - [BPO] backport 0.1.0-48-gb936edd4-0ubuntu1 to bionic, focal + [BPO] simplestreams/0.1.0-48-gb936edd4-0ubuntu1 from Jammy to bionic, focal -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1951601 Title: [BPO] simplestreams/0.1.0-48-gb936edd4-0ubuntu1 from Jammy to bionic, focal To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/simplestreams/+bug/1951601/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1962743] Re: [BPO] freeipmi/1.6.9-2 from Jammy to Focal
** Also affects: freeipmi (Ubuntu Focal) Importance: Undecided Status: New ** Changed in: freeipmi (Ubuntu) Status: New => Fix Released -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1962743 Title: [BPO] freeipmi/1.6.9-2 from Jammy to Focal To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/freeipmi/+bug/1962743/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1962614] Re: [BPO] memtest86+/5.31b+dfsg-4 from Jammy to Focal
** Changed in: memtest86+ (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/1962614 Title: [BPO] memtest86+/5.31b+dfsg-4 from Jammy to Focal To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/memtest86+/+bug/1962614/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
Re: [Bug 1962614] [NEW] [BPO] memtest86+/5.31b+dfsg-4 from Jammy to Focal
I'm afraid I'll have to say no to versions that have the goal or fixing crashes of freezes, as backports is not the pocket to fix those. Please do an SRU to fix those bugs instead. On Tue, 1 Mar 2022, 8:48 pm Launchpad Bug Tracker, < 1962...@bugs.launchpad.net> wrote: > You have been subscribed to a public bug by Fantu (fantonifabio): > > [Impact] > > * Version in Focal is broken (freeze or crash) on major of cases based > on what I saw > > [Scope] > > * List the Ubuntu release you will backport from, and the specific > package version: 5.31b+dfsg-4 from Jammy > > * List the Ubuntu release(s) you will backport to: Focal > > [Other Info] > > For now salsa git (where is hosted debian packaging) is down: > https://salsa.debian.org/debian/memtest86plus > when will return available I'll prepare a focal-backports branch > > > Changelog entries since current Focal version: > > memtest86+ (5.31b+dfsg-4) unstable; urgency=medium > > [ Fabio Fantoni ] > * New maintainer (Closes: #969191) > * another changes to makeiso.sh to make the build reproducible: > - add -uid and -gid to 0 to xorriso options > - replaced "echo -e" with printf > * d/postinst: don't run update-grub if in a container > * d/control: remove mention of lpia arch > > [ Debian Janitor ] > * Trim trailing whitespace. > * Use secure URI in Homepage field. > * Bump debhelper from old 12 to 13. > * Update renamed lintian tag names in lintian overrides. > > -- Fabio Fantoni Sun, 06 Feb 2022 21:35:43 > +0100 > > memtest86+ (5.31b+dfsg-3) experimental; urgency=medium > > * QA upload. > * d/control: replace genisoimage build-dep with xorriso > * removed d/patches/make-iso-reproducible > * d/patches/use-xorriso-instead-cdrkit.patch: > cdrkit is not supported anymore, use xorriso instead > also aded the modification of date part to make the build > reproducible (Closes: #982240) > * use SOURCE_DATE_EPOCH instead of add BUILD_DATE in d/rules > * d/rules: > - use dh_auto_build instead of make > - restore a change for kfreebsd > > -- Fabio Fantoni Sat, 22 Jan 2022 18:20:23 > +0100 > > memtest86+ (5.31b+dfsg-2) experimental; urgency=medium > > * QA upload. > * d/patches/dmi-more-ram-slots-and-buffer-overflow-fix.patch: > prevent crash for buffer overflow in DMI memory and increase > supported memory devices from 16 to 128 (Closes: #1003906) > Thanks to Lionel Debroux > > -- Fabio Fantoni Tue, 18 Jan 2022 18:30:04 > +0100 > > memtest86+ (5.31b+dfsg-1) experimental; urgency=medium > > [ Fabio Fantoni ] > * QA upload. > * New upstream version 5.31b (Closes: #989030, #977217) > * Merge from ubuntu: > - Use elf version by default that should works on major of system. > - Drop the multiboot image from the GRUB menu for now, since it's > experimental and has known problems detecting all memory on some > systems at the moment. > - Support localization of GRUB menu entries. > - Don't present in GRUB menu on EFI systems, since it won't work. > (Closes: #695246) > - Close FD 3 when invoking update-grub. > * Warn that don't support EFI instead of exit silently (LP: 1863940) > * Don't add grub2 entries if GRUB_DISABLE_MEMTEST=true is present > in /etc/default/grub (LP: #420967) > * Make possible disable serial with GRUB_MEMTEST_DISABLE_SERIAL, > enable multiboot with GRUB_MEMTEST_ENABLE_MULTIBOOT and add > custom serial parameters with GRUB_MEMTEST_SERIAL_PARAMS > (Closes: #898636, #612371) > * Specify on grub2 menu entries when elf and bin are used > * d/control: Remove hwtools and kernel-patch-badram from suggests. > * d/copyright: add Upstream-Name, Upstream-Contact and Source fields > * Bumped Standards-Version to 4.6.0 > * d/patches: > - update multiboot patch from coreboot patch based on the one of > Vladimir Serbinenko and refreshed for 5.31b (Closes: #568176) > - refresh memtest86+-5.01-O0.patch > - disable memtest86+-5.01-array-size.patch and gcc-5 as seems not > needed with newer upstream version > - refresh serial-console-fix.patch > - add test-random-cflags.patch: use CFLAGS with random.o for > maintain flags like -fno-stack-protector > - add fix-gcc8-freeze-crash.patch: runtime fix for gcc>=8 > freeze/crash > - add discard-note_gnu_property.patch: discards the > ".note.gnu.property" section that causes crash in some cases > > [ Jérémy Bobbio ] > * Make the package build reproducibly: > - Add a patch to make ISO image reproducible. > - Set the build date to the latest debian/changelog entry in > debian/rules. (Closes: #783515) > > -- Fabio Fantoni Sun, 09 Jan 2022 21:41:58 > +0100 > > memtest86+ (5.01-4) unstable; urgency=medium > > [ Fabio Fantoni ] > * QA upload. > * switch package to use dh and bump compat to 12 > (Closes: #999226, #965720) > * update debian/watch > > [ Yann Dirson ] > * Add Vcs-* fields
Re: [Bug 1959115] Re: update backportpackage and requestbackport scripts to behave according to new backport process
Which version have you tested? backportpackge in u-d-t 0.187+ should already be using the ~bp suffix. Notably, note that 0.187 is available in focal-bpo. On Sun, 13 Feb 2022, 8:35 pm Ross Gammon, <1959...@bugs.launchpad.net> wrote: > Regarding the requestbackport package, it is really only the template > for the bug report that needs to change from memory. I don't think it > had any other workflow related information. Once that is fixed, it just > needs a reference from the backports process wiki again (like it used to > have). > > Regarding the backportpackage script, I just tried it, and it is fine for > testing in a ppa. I think we could already recommend using this on the wiki > with a ppa specified in the -u option. Perhaps a warning not to upload to > the archive with it yet would be required though. I had hoped I could > specify the new "bpo" version string with the suffix option, but according > to the manpage, the "~ubuntu" bit is hardwired: > -S SUFFIX, --suffix=SUFFIX > Add the specified suffix to the version number when > backporting. > backportpackage will always append ~ubuntuDESTINATION.1 to > the > original version number, and if SUFFIX is specified, it is > ap‐ > pended to that, to get version numbers of the form > ORIGINAL_VER‐ > SION~ubuntuDESTINATION.1SUFFIX. If the backported package is > be‐ > ing uploaded to a PPA, then SUFFIX defaults to ~ppa1, > otherwise > the default is blank. > > Now that a bug is always required, I suppose the script should prompt > for that, and the "-c/--close" options be taken away. > > -- > You received this bug notification because you are a member of Ubuntu > Backporters, which is subscribed to the bug report. > https://bugs.launchpad.net/bugs/1959115 > > Title: > update backportpackage and requestbackport scripts to behave according > to new backport process > > To manage notifications about this bug go to: > > https://bugs.launchpad.net/ubuntu/+source/ubuntu-dev-tools/+bug/1959115/+subscriptions > > > -- > ubuntu-backports mailing list > ubuntu-backpo...@lists.ubuntu.com > Modify settings or unsubscribe at: > https://lists.ubuntu.com/mailman/listinfo/ubuntu-backports > -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1959115 Title: update backportpackage and requestbackport scripts to behave according to new backport process To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/ubuntu-dev-tools/+bug/1959115/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
Re: [Bug 1960752] Re: [BPO] gramps/5.1.4-1 from Jammy
Debhelper 13 is available in focal-backports already. Please make sure your build environment enables the backports pocket (and that your dependency solver handles it appropriately). If you are building in a PPA, there is an extra flag to check in the PPA settings. On Sun, 13 Feb 2022, 9:45 pm Ross Gammon, <1960...@bugs.launchpad.net> wrote: > Uploaded 5.1.4~bpo21.04.1 to impish-backports > > -- > You received this bug notification because you are a member of Ubuntu > Backporters, which is subscribed to the bug report. > https://bugs.launchpad.net/bugs/1960752 > > Title: > [BPO] gramps/5.1.4-1 from Jammy > > To manage notifications about this bug go to: > > https://bugs.launchpad.net/ubuntu/+source/gramps/+bug/1960752/+subscriptions > > > -- > ubuntu-backports mailing list > ubuntu-backpo...@lists.ubuntu.com > Modify settings or unsubscribe at: > https://lists.ubuntu.com/mailman/listinfo/ubuntu-backports > -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1960752 Title: [BPO] gramps/5.1.4-1 from Jammy To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gramps/+bug/1960752/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1876996] Re: [BPO] inkscape/1.1.1-3ubuntu1 from jammy
-- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1876996 Title: [BPO] inkscape/1.1.1-3ubuntu1 from jammy To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/inkscape/+bug/1876996/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1876996] Re: [BPO] inkscape/1.1.1-3ubuntu1 from jammy
If possible I'd prefer to avoid an extra bpo diff just for this, so I'd rather accept it as it is. (Also, ragel is fine to skip because it doesn't change anything in practice, it only used to rebuild something that is otherwise pre- compiled in the tarball; whereas disabling gspell would effectively change the feature set, something that I'd dislike to see done across architectures). With your ACK I'm then going to accept my own upload, thank you for the through review! ** Changed in: inkscape (Ubuntu Focal) Status: In Progress => Fix Released -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1876996 Title: [BPO] inkscape/1.1.1-3ubuntu1 from jammy To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/inkscape/+bug/1876996/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1876996] Re: [BPO] inkscape/1.1.1-3ubuntu1 from jammy
meh, I didn't notice that, thank you. Looking at the germinate-output file, it looks like gtkspell3 is included in the seed starting with groovy only because of it being a build-dep of inkscape (it's a new build-dep starting with inkscape 1.x, focal has 0.92.x). This also means that a no-change rebuild wouldn't help, it would first need a manual addition to the i386.focal seed, which would be a pain to do. Plus gtkspell3's version is the same from focal all the way to jammy, so I'd need to SRU them all... Honestly, in this case I would propose to just ignore that matter, and just say that inkscape/focal-backport will not be available in i386. Personally, I actually find no reason for inkscape to be in the i386 seed (it's there only as a build-dep of a i386-only package), and I'm actually working (more or less, it's a plan) to drop it from there. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1876996 Title: [BPO] inkscape/1.1.1-3ubuntu1 from jammy To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/inkscape/+bug/1876996/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1959541] Re: pull-lp-source crashed with AttributeError in __new__(): module 'collections' has no attribute 'Callable'
"right now" thanks for the ping :) ** Changed in: ubuntu-dev-tools (Ubuntu Jammy) Status: New => Fix Committed -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1959541 Title: pull-lp-source crashed with AttributeError in __new__(): module 'collections' has no attribute 'Callable' To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/ubuntu-dev-tools/+bug/1959541/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
Re: [Bug 1959629] [NEW] lintian hangs during a debuild or sbuild
Mind specifying how long you've waited on the lintian stage before claiming that it "never finishes"? On Tue, 1 Feb 2022, 12:10 am fossfreedom, <1959...@bugs.launchpad.net> wrote: > Public bug reported: > > Uplifting to the latest lintian on jammy > > a debuild -S -k0xkey on a package, the debuild never finishes - it gets > stuck at the lintian stage. > > I have to downgrade lintian to the previous version from impish > > Similarly, running a sbuild on any package, lintian never finishes if I > include lintian checks > > Now I have to workaround via sbuild -d jammy --no-run-lintian > > my ~/.sbuildrc is > > # Name to use as override in .changes files for the Maintainer: field > # (mandatory, no default!). > $maintainer_name='x '; > > # Default distribution to build. > $distribution = "jammy"; > # Build arch-all by default. > $build_arch_all = 1; > > # When to purge the build directory afterwards; possible values are > "never", > # "successful", and "always". "always" is the default. It can be helpful > # to preserve failing builds for debugging purposes. Switch these comments > # if you want to preserve even successful builds, and then use > # "schroot -e --all-sessions" to clean them up manually. > $purge_build_directory = 'successful'; > $purge_session = 'successful'; > $purge_build_deps = 'successful'; > # $purge_build_directory = 'never'; > # $purge_session = 'never'; > # $purge_build_deps = 'never'; > > # Directory for writing build logs to > $log_dir=$ENV{HOME}."/ubuntu/logs"; > $run_lintian = 1; > $lintian_opts = ['-i', '-I', '--pedantic']; > > # don't remove this, Perl needs it: > 1; > > All jammy sbuilds have worked before the latest lintian was released. > > Thoughts as to what is the issue here? > > ProblemType: Bug > DistroRelease: Ubuntu 22.04 > Package: lintian 2.111.0ubuntu3 > ProcVersionSignature: Ubuntu 5.15.0-18.18-generic 5.15.12 > Uname: Linux 5.15.0-18-generic x86_64 > ApportVersion: 2.20.11-0ubuntu76 > Architecture: amd64 > CasperMD5CheckResult: pass > CurrentDesktop: Budgie:GNOME > Date: Mon Jan 31 22:56:57 2022 > InstallationDate: Installed on 2022-01-29 (2 days ago) > InstallationMedia: Ubuntu-Budgie 22.04 LTS "Jammy Jellyfish" - Alpha amd64 > (20220129) > PackageArchitecture: all > SourcePackage: lintian > UpgradeStatus: No upgrade log present (probably fresh install) > > ** Affects: lintian (Ubuntu) > Importance: Undecided > Status: New > > > ** Tags: amd64 apport-bug jammy > > -- > You received this bug notification because you are subscribed to Ubuntu. > https://bugs.launchpad.net/bugs/1959629 > > Title: > lintian hangs during a debuild or sbuild > > Status in lintian package in Ubuntu: > New > > Bug description: > Uplifting to the latest lintian on jammy > > a debuild -S -k0xkey on a package, the debuild never finishes - it > gets stuck at the lintian stage. > > I have to downgrade lintian to the previous version from impish > > Similarly, running a sbuild on any package, lintian never finishes if > I include lintian checks > > Now I have to workaround via sbuild -d jammy --no-run-lintian > > my ~/.sbuildrc is > > # Name to use as override in .changes files for the Maintainer: field > # (mandatory, no default!). > $maintainer_name='x '; > > # Default distribution to build. > $distribution = "jammy"; > # Build arch-all by default. > $build_arch_all = 1; > > # When to purge the build directory afterwards; possible values are > "never", > # "successful", and "always". "always" is the default. It can be helpful > # to preserve failing builds for debugging purposes. Switch these > comments > # if you want to preserve even successful builds, and then use > # "schroot -e --all-sessions" to clean them up manually. > $purge_build_directory = 'successful'; > $purge_session = 'successful'; > $purge_build_deps = 'successful'; > # $purge_build_directory = 'never'; > # $purge_session = 'never'; > # $purge_build_deps = 'never'; > > # Directory for writing build logs to > $log_dir=$ENV{HOME}."/ubuntu/logs"; > $run_lintian = 1; > $lintian_opts = ['-i', '-I', '--pedantic']; > > # don't remove this, Perl needs it: > 1; > > All jammy sbuilds have worked before the latest lintian was released. > > Thoughts as to what is the issue here? > > ProblemType: Bug > DistroRelease: Ubuntu 22.04 > Package: lintian 2.111.0ubuntu3 > ProcVersionSignature: Ubuntu 5.15.0-18.18-generic 5.15.12 > Uname: Linux 5.15.0-18-generic x86_64 > ApportVersion: 2.20.11-0ubuntu76 > Architecture: amd64 > CasperMD5CheckResult: pass > CurrentDesktop: Budgie:GNOME > Date: Mon Jan 31 22:56:57 2022 > InstallationDate: Installed on 2022-01-29 (2 days ago) > InstallationMedia: Ubuntu-Budgie 22.04 LTS "Jammy Jellyfish" - Alpha > amd64 (20220129) > PackageArchitecture: all > SourcePackage: lintian > UpgradeStatus: No upgrade log present (probably fresh install) > > To manage notifications about this bug go
[Bug 1876996] Re: [new upstream]Inkscape 1.0
I'm uploading now version 1.1.1-3ubuntu1~bpo20.04.1 to focal-backports, so that the team can review it. ** Changed in: inkscape (Ubuntu Focal) Status: Triaged => In Progress ** Summary changed: - [new upstream]Inkscape 1.0 + [BPO] inkscape/1.1.1-3ubuntu1 from jammy -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1876996 Title: [BPO] inkscape/1.1.1-3ubuntu1 from jammy To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/inkscape/+bug/1876996/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1901345] Re: Scribus 1.5.6 unstable (?) freezes immediately at startup
this has been reportedly long fixed in 21.04, and 20.10 went EOL in the meantime (and nowadays 21.04 too). so I'm closing this bug. ** Changed in: scribus (Ubuntu) Status: Confirmed => Fix Released -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1901345 Title: Scribus 1.5.6 unstable (?) freezes immediately at startup To manage notifications about this bug go to: https://bugs.launchpad.net/scribus/+bug/1901345/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1959115] Re: update backportpackage and requestbackport scripts to behave according to new backport process
** Summary changed: - update backportpackage script to behave according to new backport process + update backportpackage and requestbackport scripts to behave according to new backport process ** Description changed: - The 'backportpackage' script needs to be updated to work according to the new backport process: + The 'requestbackport' script needs to be updated to the new workflow. + The Backporters team doesn't take on *requests* to do backports anymore, so most likely this script should be turned into a simpler pointer to the wiki page, rather than actually do anything. + + The 'backportpackage' script needs to be checked if the latest update + covered all the differences from the previous workflow. + + https://wiki.ubuntu.com/UbuntuBackports + This bug is to track that work. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1959115 Title: update backportpackage and requestbackport scripts to behave according to new backport process To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/ubuntu-dev-tools/+bug/1959115/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1956440] Re: FTBFS against python3-pygments (=2.10.0+dfsg-1)
ah! I didn't notice this bug... @alexghiti: for the next time, please consider adding LP:# to the changelog. Even if uploaded in debian launchpad would pick it up automatically when the package is synced. I'll let you close the bug manually once that happens. (please don't forget it.. launchpad already has too many stale bugs lounging around -.-) -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1956440 Title: FTBFS against python3-pygments (=2.10.0+dfsg-1) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/pygments/+bug/1956440/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1956004] Re: [BPO] Backport opencpn 5.6.0 from Jammy
Yeah, it's fine, those are really small details that just raises a small eyebrow but do nothing else :) You are right, the process is completed. The package also already built, and will be available in the archive in a matter of minutes/hours when the publisher runs :) -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1956004 Title: [BPO] Backport opencpn 5.6.0 from Jammy To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/opencpn/+bug/1956004/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1956004] Re: [BPO] Backport opencpn 5.6.0 from Jammy
Looking at the diff, I also find it odd that you are changing d/watch (according to the changelog, to please lintian?). That's totally useless and just noisy (nobody is going to run uscan on this...), so I recommend you don't do that at the next backport update. Likewise I'm not sure why you didn't drop that delta related to debhelper 12/13 as Dan suggested. It also doesn't really matter in the end, but I don't understand your point about d/rules and dh_missing… It also looks like you added a debian/docs file adding a README. I'm going to ignore this as it is of little consequence, but if you'd like to install such README please do that in a debian/opencpn.docs file (instead of debian/docs) and do that in debian first. With this, consider the package approved. ** Changed in: opencpn (Ubuntu Focal) Status: New => Fix Released -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1956004 Title: [BPO] Backport opencpn 5.6.0 from Jammy To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/opencpn/+bug/1956004/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1958772] [NEW] [BPO] lib2geom/1.1-2 from jammy
Public bug reported: [Impact] * This is a new dependency of inkscape 1.1, which I plan to backport to focal (see #1876996). [Scope] * from: jammy, lib2geom/1.1-2 * to: focal [Other Info] * new library with no other users outside of inkscape. * technically inkscape itself contains an embedded lib2geom (which I'm using in ubuntu/i386 as it's not in the i386 whitelist), however I prefer to keep the split for policy reasons if I can. ** Affects: lib2geom (Ubuntu) Importance: Undecided Assignee: Mattia Rizzolo (mapreri) Status: Invalid ** Affects: lib2geom (Ubuntu Focal) Importance: Undecided Assignee: Mattia Rizzolo (mapreri) Status: In Progress ** Also affects: lib2geom (Ubuntu Focal) Importance: Undecided Status: New ** Changed in: lib2geom (Ubuntu Focal) Assignee: (unassigned) => Mattia Rizzolo (mapreri) ** Changed in: lib2geom (Ubuntu) Status: New => Invalid ** Changed in: lib2geom (Ubuntu Focal) Status: New => In Progress -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1958772 Title: [BPO] lib2geom/1.1-2 from jammy To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/lib2geom/+bug/1958772/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
Re: [Bug 1956004] Re: [BPO] Backport opencpn 5.6.0 from Jammy
> Looking at that queue is somewhat scary, I see an entry from 2021-10-28 that's for the proposed pocked (i.e. SRUs), for backports yours is the only package in the queue... -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1956004 Title: [BPO] Backport opencpn 5.6.0 from Jammy To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/opencpn/+bug/1956004/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1956004] Re: [BPO] Backport opencpn 5.6.0 from Jammy
> Is that mentioned at https://wiki.ubuntu.com/UbuntuBackports ? u.U - somehow, despite the plenty of reviews we made to the drafts of that page we still managed to miss it. thank you! -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1956004 Title: [BPO] Backport opencpn 5.6.0 from Jammy To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/opencpn/+bug/1956004/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1956004] Re: [BPO] Backport opencpn 5.6.0 from Jammy
please remember to subscribe ~ubuntu-backporters for BPO bugs... As a backports team member learning about this bug from a ubuntu-devel- discuss mail felt odd :3 -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1956004 Title: [BPO] Backport opencpn 5.6.0 from Jammy To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/opencpn/+bug/1956004/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1815694] Re: Snap package crashes in g_path_get_dirname unless adwaita-icon-theme-full is installed
snap packages bugs are not of concern for the ubuntu specific package, so marking invalid. ** Changed in: inkscape (Ubuntu) Status: Confirmed => Invalid -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1815694 Title: Snap package crashes in g_path_get_dirname unless adwaita-icon-theme- full is installed To manage notifications about this bug go to: https://bugs.launchpad.net/inkscape/+bug/1815694/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1942699] Re: SRU: Update Telegram Desktop to 3.1.1
@serge-hallyn: we can all agree, but to date I only failed to grab the attention of any SRU member; even pinging on IRC resulted useless apparently. All the packages have been in the queue for months, but ignored. I'll thank you in advance if you manage to get anybody to look at them and provide useful feedback, that we didn't get since Sep 9th when the SRU team reached decisions without even fully understanding the situation AND without asking for more details, and then just went into silence. /me not particularly amused. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1942699 Title: SRU: Update Telegram Desktop to 3.1.1 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/libtgowt/+bug/1942699/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1885766] Re: Version 2.20.4 causes a component-mismatch
FTR, I handled this in debian this way: https://salsa.debian.org/debian/devscripts/-/commit/fd21a8c8e05e0158756e9b8954c6c01a1f2f2bfe -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1885766 Title: Version 2.20.4 causes a component-mismatch To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/devscripts/+bug/1885766/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1956644] Re: [BPO] gallery-dl 1.20.0-1 to focal
Actually, forget it, I see this is a new package, so it's fine. diff also looks ok, so I approved it. (the comment still stands for when jammy will be stable though) ** Changed in: focal-backports Status: New => Fix Released ** Project changed: focal-backports => gallery-dl (Ubuntu) -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1956644 Title: [BPO] gallery-dl 1.20.0-1 to focal To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gallery-dl/+bug/1956644/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1942699] Re: SRU: Update Telegram Desktop to 3.1.1
** Changed in: telegram-desktop (Ubuntu Focal) Importance: Undecided => High -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1942699 Title: SRU: Update Telegram Desktop to 3.1.1 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/libtgowt/+bug/1942699/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1953580] Re: telegram-desktop will soon stop working on focal
*** This bug is a duplicate of bug 1942699 *** https://bugs.launchpad.net/bugs/1942699 ** This bug has been marked a duplicate of bug 1942699 SRU: Update Telegram Desktop to 3.1.1 -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1953580 Title: telegram-desktop will soon stop working on focal To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/telegram-desktop/+bug/1953580/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1558596] Re: Spanish missing
Probably you were in a release before libreoffice-dictionaries took over and is now shipping mythes-es. At least ubuntu 16.04 (xenial, released a month after your bug report) has it. https://launchpad.net/ubuntu/xenial/+package/mythes-es ** Package changed: mythes (Ubuntu) => libreoffice-dictionaries (Ubuntu) ** Changed in: libreoffice-dictionaries (Ubuntu) Status: New => Fix Released -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1558596 Title: Spanish missing To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/libreoffice-dictionaries/+bug/1558596/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1950656] Re: package inkscape-tutorials (not installed) failed to install/upgrade: Versuch, »/usr/share/inkscape/tutorials/README« zu überschreiben, welches auch in Paket inkscape 1:1.1+202109281
Inkscape version 1:1.1+202109281949+c3084ef5ed~ubuntu20.04.1 doesn't come from the Ubuntu archive. We can't provide upgrade paths from packages that come from who knows where. Besides, looking at that error, I assume that inkscape binary you got already contains the tutorials, so I don't think you should install this package at all (inkscape-tutorials used to be inside the main inkscape binary package, but was split off to reduce the installed size of a normal installation). ** Changed in: inkscape (Ubuntu) Status: New => Invalid -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1950656 Title: package inkscape-tutorials (not installed) failed to install/upgrade: Versuch, »/usr/share/inkscape/tutorials/README« zu überschreiben, welches auch in Paket inkscape 1:1.1+202109281949+c3084ef5ed~ubuntu20.04.1 ist To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/inkscape/+bug/1950656/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1004579] Re: [pbuilder-dist] overwrite OTHERMIRROR set in ~/.pbuilderrc
** Changed in: ubuntu-dev-tools (Ubuntu) Status: Invalid => Confirmed -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1004579 Title: [pbuilder-dist] overwrite OTHERMIRROR set in ~/.pbuilderrc To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/ubuntu-dev-tools/+bug/1004579/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1862372] Re: [SRU] ubuntu-upload-permission TypeError crash
root@warren:/# apt install ubuntu-dev-tools/focal-proposed ... Selected version '0.176ubuntu20.04.1' (Ubuntu:20.04/focal-proposed [all]) for 'ubuntu-dev-tools' ... Setting up ubuntu-dev-tools (0.176ubuntu20.04.1) ... ... root@warren:/# ubuntu-upload-permission --list-uploaders cloud-init Please open this authorization page: (https://launchpad.net/+authorize-token?oauth_token=QnZKJWv48DK5RZ65Dtl3_permission=DESKTOP_INTEGRATION) in your browser. Use your browser to authorize this program to access Launchpad on your behalf. Press Enter after authorizing in your browser. All upload permissions for cloud-init: Component (main) * Ubuntu Core Development Team (ubuntu-core-dev) [team] Packagesets === core: ubuntu-cloud: * Ubuntu Cloud Uploaders (ubuntu-cloud-uploaders) [team] Per-Package-Uploaders = * Chad Smith (chad.smith) * Ryan Harper (raharper) You can not upload cloud-init to jammy, yourself. But you can still contribute to it via the sponsorship process: https://wiki.ubuntu.com/SponsorshipProcess root@warren:/# All good! :) ** Tags removed: verification-needed verification-needed-focal ** Tags added: verification-done verification-done-focal -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1862372 Title: [SRU] ubuntu-upload-permission TypeError crash To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/ubuntu-dev-tools/+bug/1862372/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1947192] Re: [BPO] ubuntu-dev-tools/0.187
note that the team wasn't subscribed, so this bug fell off, at least, my radar. anyhow, I'm reusing this bug very badly since it wasn't yet fully closed; in hindsight 2 minutes after I made the change I figured I was better opening a new one, but well.. I've now uploaded 0.187 everywhere, bionic, focal, hirsute, impish. Note that bionic and focal require the new debhelper that is also in the queue, see the related bug. ** Summary changed: - [BPO] version 0.185 + [BPO] ubuntu-dev-tools/0.187 ** Changed in: ubuntu-dev-tools (Ubuntu Bionic) Status: New => Fix Committed ** Changed in: ubuntu-dev-tools (Ubuntu Focal) Status: Fix Released => Fix Committed ** Changed in: ubuntu-dev-tools (Ubuntu Focal) Assignee: (unassigned) => Mattia Rizzolo (mapreri) ** Changed in: ubuntu-dev-tools (Ubuntu Bionic) Assignee: (unassigned) => Mattia Rizzolo (mapreri) ** Also affects: ubuntu-dev-tools (Ubuntu Impish) Importance: Undecided Status: New ** Changed in: ubuntu-dev-tools (Ubuntu Impish) Assignee: (unassigned) => Mattia Rizzolo (mapreri) ** Changed in: ubuntu-dev-tools (Ubuntu Hirsute) Assignee: (unassigned) => Mattia Rizzolo (mapreri) ** Changed in: ubuntu-dev-tools (Ubuntu Hirsute) Status: In Progress => Fix Committed ** Changed in: ubuntu-dev-tools (Ubuntu Impish) Status: New => Fix Committed -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1947192 Title: [BPO] ubuntu-dev-tools/0.187 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/ubuntu-dev-tools/+bug/1947192/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1728423] Re: [BPO] debhelper/13.5+
Can't do xenial anymore since it's EOL. ** Description changed: + [Impact] + + * This package is included amongst the "special cases". + * dwz is needed in bionic as debhelper grew a versioned dependency there. +I preferred to backport it as well, rather than dropping the +restriction (it's required for golang apparently). + + [Scope] + + * debhelper 13.5.2ubuntu1 from jammy towards all supported releases. + * dwz 0.13-5 from focal to bionic + + [Other Info] + + * I already used the backported version to, for example, build +ubuntu-dev-tools; besides, debhelper ships with a decent testsuite + * For debhelper/bionic I had to do some changes, see +https://bugs.debian.org/1001403 + + + [ Original Report ] + As debhelper 10.3 (https://github.com/Debian/debhelper/commit/f771a9a62802733fea6801dacde3badee13ef8c0) added support for the meson build system, it would be great to have a newer version of debhelper in xenial-backports than 10.2.2. ** Changed in: dwz (Ubuntu Bionic) Status: In Progress => Fix Committed ** Changed in: debhelper (Ubuntu Bionic) Status: In Progress => Fix Committed -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1728423 Title: [BPO] debhelper/13.5+ To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/debhelper/+bug/1728423/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1728423] Re: [BPO] debhelper/13.5+
** Also affects: dwz (Ubuntu) Importance: Undecided Status: New ** No longer affects: dwz (Ubuntu Xenial) ** No longer affects: dwz (Ubuntu Focal) ** No longer affects: dwz (Ubuntu Hirsute) ** No longer affects: dwz (Ubuntu Impish) ** Changed in: dwz (Ubuntu) Status: New => Invalid ** Changed in: debhelper (Ubuntu Xenial) Status: Triaged => Won't Fix ** Changed in: dwz (Ubuntu Bionic) Status: New => In Progress ** Changed in: dwz (Ubuntu Bionic) Assignee: (unassigned) => Mattia Rizzolo (mapreri) -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1728423 Title: [BPO] debhelper/13.5+ To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/debhelper/+bug/1728423/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1728423] Re: [BPO] debhelper/13.5+
** Changed in: debhelper (Ubuntu Focal) Status: In Progress => Fix Committed -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1728423 Title: [BPO] debhelper/13.5+ To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/debhelper/+bug/1728423/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1891976] Re: Telegram desktop suddenly not taking any user keyboard input and mouse input. Tried restarting the app but didn't worked.
ack, doing so. ** Changed in: telegram-desktop (Ubuntu) Status: New => Invalid -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1891976 Title: Telegram desktop suddenly not taking any user keyboard input and mouse input. Tried restarting the app but didn't worked. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/telegram-desktop/+bug/1891976/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1832998] Re: Pure-FTPd Breaks with OpenSSL v1.1.1
So, I just tested with 1.0.46-1ubuntu18.04.1 and I confirm I can happily connect. ** Tags removed: verification-needed verification-needed-bionic ** Tags added: verification-done verification-done-bionic -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1832998 Title: Pure-FTPd Breaks with OpenSSL v1.1.1 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/pure-ftpd/+bug/1832998/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1862372] Re: ubuntu-upload-permission TypeError crash
I uploaded the said fix to focal. After all it's a crash, so it should be fixed as such :) ** Patch added: "debdiff.patch" https://bugs.launchpad.net/ubuntu/+source/ubuntu-dev-tools/+bug/1862372/+attachment/5545461/+files/debdiff.patch ** Summary changed: - ubuntu-upload-permission TypeError crash + [SRU] ubuntu-upload-permission TypeError crash -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1862372 Title: [SRU] ubuntu-upload-permission TypeError crash To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/ubuntu-dev-tools/+bug/1862372/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1862372] Re: ubuntu-upload-permission TypeError crash
** Description changed: + [Impact] + + * ubuntu-upload-permission sometimes crashes. + + [Test Plan] + + * `ubuntu-upload-permission --list-uploaders cloud-init` + + [Where problems could occur] + + * This is a targeted fix that has been in other releases for more than a year. + * At most ubuntu-upload-permissions will start erroring out elsewhere (it won't) + + [Original text] + (note that what was reported here is already fixed in focal, but there is followup fix for a different case) + focal ubuntu-dev-tools 0.175 $ ubuntu-upload-permission -a procps Loading KWallet Loading SecretService Loading Windows Loading chainer Loading macOS All upload permissions for procps: Component (main) * Ubuntu Core Development Team (ubuntu-core-dev) [team] Traceback (most recent call last): - File "/usr/bin/ubuntu-upload-permission", line 144, in - main() - File "/usr/bin/ubuntu-upload-permission", line 90, in main - sourcepackagename=package)) + File "/usr/bin/ubuntu-upload-permission", line 144, in + main() + File "/usr/bin/ubuntu-upload-permission", line 90, in main + sourcepackagename=package)) TypeError: '<' not supported between instances of 'Packageset' and 'Packageset' ** Changed in: ubuntu-dev-tools (Ubuntu) Status: Fix Committed => Fix Released ** Changed in: ubuntu-dev-tools (Ubuntu Focal) Status: Triaged => In Progress ** Changed in: ubuntu-dev-tools (Ubuntu Focal) Assignee: (unassigned) => Mattia Rizzolo (mapreri) -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1862372 Title: ubuntu-upload-permission TypeError crash To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/ubuntu-dev-tools/+bug/1862372/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1827367] Re: rabbitmq-server outdated
FYI, the Backports project restarted. Although we have yet to announce it formally, you can find the new process here https://wiki.ubuntu.com/UbuntuBackports I'm unsubscribing the backporters team from this bug since to me it seems there is nothing to do by us, but if and when somebody is going to follow through with those steps please do re-subscribe the team! -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1827367 Title: rabbitmq-server outdated To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/elixir-lang/+bug/1827367/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1876996] Re: [new upstream]Inkscape 1.0
Now that the BPO process has been renewed I'm going to follow through it (also, the SRU team never answered here, proof that they only look at bugs when uploads get into the queue…). Although, I'm currently quite busy, so it'll take a bit of time. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1876996 Title: [new upstream]Inkscape 1.0 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/inkscape/+bug/1876996/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1905613] Re: Please backport v4l2loopback 0.12.5-1 (universe) from hirsute
It seems to me that you are trying to get this through an SRU, and not into BPO. Therefore, I'm unsubscribing the Backporters team. If this is an error, please see https://wiki.ubuntu.com/UbuntuBackports about the new BPO process, and resubscribe us. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1905613 Title: Please backport v4l2loopback 0.12.5-1 (universe) from hirsute To manage notifications about this bug go to: https://bugs.launchpad.net/hwe-next/+bug/1905613/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 897346] Re: gedit-latex-plugin should recommend libgnome2-0
I'm closing this old bug, since oneric has been long EOLed. ** Changed in: gedit-latex-plugin (Ubuntu) Status: New => Won't Fix -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/897346 Title: gedit-latex-plugin should recommend libgnome2-0 To manage notifications about this bug go to: https://bugs.launchpad.net/oneiric-backports/+bug/897346/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1174070] Re: Touchegg 1.0 under 12.04, 12.10 causes segfault, is NOT working. missing backporting of 1.1 to 12.04/12.10
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. Both ubuntu 12.04 and 12.10 reached their EOL, and as you mentioned 13.04 works. Therefore, I'm closing this bug. Also, cases such as this were never part of the tasks of the Backporters team, as bugs should be fixed in -updates, so I'm also unsubscribing the Backporters team. ** Changed in: touchegg (Ubuntu) Status: Confirmed => Won't Fix -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1174070 Title: Touchegg 1.0 under 12.04, 12.10 causes segfault, is NOT working. missing backporting of 1.1 to 12.04/12.10 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/touchegg/+bug/1174070/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1728423] Re: Backport debhelper 10.3+ to xenial
** Also affects: debhelper (Ubuntu Focal) Importance: Undecided Status: New ** Also affects: debhelper (Ubuntu Hirsute) Importance: Undecided Status: New ** Also affects: debhelper (Ubuntu Xenial) Importance: Undecided Status: New ** Also affects: debhelper (Ubuntu Bionic) Importance: Undecided Status: New ** Also affects: debhelper (Ubuntu Impish) Importance: Undecided Status: New ** Changed in: debhelper (Ubuntu) Status: Confirmed => Invalid ** Changed in: debhelper (Ubuntu Xenial) Status: New => Triaged ** Changed in: debhelper (Ubuntu Bionic) Status: New => In Progress ** Changed in: debhelper (Ubuntu Focal) Status: New => In Progress ** Changed in: debhelper (Ubuntu Hirsute) Status: New => In Progress ** Changed in: debhelper (Ubuntu Impish) Status: New => In Progress ** Changed in: debhelper (Ubuntu Bionic) Assignee: (unassigned) => Mattia Rizzolo (mapreri) ** Changed in: debhelper (Ubuntu Focal) Assignee: (unassigned) => Mattia Rizzolo (mapreri) ** Changed in: debhelper (Ubuntu Hirsute) Assignee: (unassigned) => Mattia Rizzolo (mapreri) ** Changed in: debhelper (Ubuntu Impish) Assignee: (unassigned) => Mattia Rizzolo (mapreri) ** Summary changed: - Backport debhelper 10.3+ to xenial + [BPO] debhelper/13.5+ -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1728423 Title: [BPO] debhelper/13.5+ To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/debhelper/+bug/1728423/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1414482] Re: Backport xtables-addons 2.6-1 to trusty
trusty is now EOL, so I'm closing the bug. ** Changed in: xtables-addons (Ubuntu Trusty) Status: Incomplete => Won't Fix -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1414482 Title: Backport xtables-addons 2.6-1 to trusty To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/xtables-addons/+bug/1414482/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1916068] Re: [BPO] Please backport sdbus-cpp 0.8.3-4 (universe) from impish
So to conclude your questions: during the backporters meeting we decided that (for now, of course things might change going forward if/when there is a need for them to change) * about assigning to somebody/someteam when it's ready for review: not required, as we just follow all bugs we are subscribed to that is not closed. (this is the same situation as of SRUs, FWIW). * about the upload queue: we consider that an implementation detail that uploaders need not be concerned with; you should already be receiving an email when the upload goes through, saying the upload was accepted (into whatever queue): that's enough of a "receipt" :) -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1916068 Title: [BPO] Please backport sdbus-cpp 0.8.3-4 (universe) from impish To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/sdbus-cpp/+bug/1916068/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1951722] Re: package inkscape-tutorials (not installed) failed to install/upgrade: tentative de remplacement de « /usr/share/inkscape/tutorials/README », qui appartient aussi au paquet inkscape 1
besides, the bug report said "DistroRelease: Ubuntu 20.04" but the package version you are getting an error against says "18.04", so I suppose you also have some PPA or such with the wrong distribution set. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1951722 Title: package inkscape-tutorials (not installed) failed to install/upgrade: tentative de remplacement de « /usr/share/inkscape/tutorials/README », qui appartient aussi au paquet inkscape 1.0.2+r75+1~ubuntu18.04.1 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/inkscape/+bug/1951722/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1951722] Re: package inkscape-tutorials (not installed) failed to install/upgrade: tentative de remplacement de « /usr/share/inkscape/tutorials/README », qui appartient aussi au paquet inkscape 1
"1.0.2+r75+1~ubuntu18.04.1" is not a version that comes from the ubuntu archive, besides it's an higher version that what's in focal anyway. It's not a configuration we can support officially, so I recommend you go ask user support instead of opening a bug. ** Changed in: inkscape (Ubuntu) Status: New => Invalid -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1951722 Title: package inkscape-tutorials (not installed) failed to install/upgrade: tentative de remplacement de « /usr/share/inkscape/tutorials/README », qui appartient aussi au paquet inkscape 1.0.2+r75+1~ubuntu18.04.1 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/inkscape/+bug/1951722/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1945349] Re: mk-sbuild has no support for type=zfs-snapshot schroots
actually it is, sorry for the noise. ** Changed in: ubuntu-dev-tools (Ubuntu) Status: In Progress => Fix Committed -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1945349 Title: mk-sbuild has no support for type=zfs-snapshot schroots To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/ubuntu-dev-tools/+bug/1945349/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1945349] Re: mk-sbuild has no support for type=zfs-snapshot schroots
it's not "fix committed" if you are talking about a repository that is not the main one… ** Changed in: ubuntu-dev-tools (Ubuntu) Status: Fix Committed => In Progress -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1945349 Title: mk-sbuild has no support for type=zfs-snapshot schroots To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/ubuntu-dev-tools/+bug/1945349/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1942699] Re: SRU: Update Telegram Desktop to 3.1.1
I've uploaded telegram-desktop/3.1.1+ds-1~ubuntu20.04.1 to focal. libtgowt (in NEW) wasn't rejected and it's still good, so I'm not touching it, but please remember it's a dependency. ** Patch added: "telegram-desktop_3.1.1+ds-1~ubuntu20.04.1.diff" https://bugs.launchpad.net/ubuntu/+source/telegram-desktop/+bug/1942699/+attachment/5537190/+files/telegram-desktop_3.1.1+ds-1~ubuntu20.04.1.diff ** Changed in: telegram-desktop (Ubuntu Focal) Status: Triaged => In Progress ** Changed in: libtgowt (Ubuntu Focal) Status: Triaged => In Progress -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1942699 Title: SRU: Update Telegram Desktop to 3.1.1 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/libtgowt/+bug/1942699/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1832998] Re: Pure-FTPd Breaks with OpenSSL v1.1.1
Well, better late than never, I'm going to SRU this. debdiff attached, and package uploaded. for the SRU reviewers: note that this is 1.0 source, so even if I added the patches separately in d/patches, they are in fact directly applied to the tree; I didn't want to convert it to 3.0, or add a build-dep on quilt. ** Patch added: "pure-ftpd_1.0.46-1build1_1.0.46-1ubuntu18.04.1.diff" https://bugs.launchpad.net/ubuntu/+source/pure-ftpd/+bug/1832998/+attachment/5536831/+files/pure-ftpd_1.0.46-1build1_1.0.46-1ubuntu18.04.1.diff -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1832998 Title: Pure-FTPd Breaks with OpenSSL v1.1.1 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/pure-ftpd/+bug/1832998/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1842669] Re: pure-ftpd needs update to at least v1.0.47-3 in 18.04 LTS !
*** This bug is a duplicate of bug 1832998 *** https://bugs.launchpad.net/bugs/1832998 marking as duplicate of #1832998 since the text is really mostly about that one bug. ** This bug has been marked a duplicate of bug 1832998 Pure-FTPd Breaks with OpenSSL v1.1.1 -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1842669 Title: pure-ftpd needs update to at least v1.0.47-3 in 18.04 LTS ! To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/pure-ftpd/+bug/1842669/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1832998] Re: Pure-FTPd Breaks with OpenSSL v1.1.1
** Description changed: + [Impact] + + * Currently pure-ftpd in bionic, without any further special care, just + can't work with modern programs connecting with TLS 1.3 or such. + + [Test Plan] + + * install pure-ftpd + * create a cert in /etc/ssl/private/pure-ftpd.pem + * echo 1 > /etc/pure-ftpd/conf/TLS + * try to connect. + + Currently the connection fails with "ERROR TLS renegotiation" in the + pure-ftpd logs. + + [Where problems could occur] + + * I suspect that if the upgrade went well connections would just fail. + + [Other Info] + + These patches have been released with fedora 29; also seb128 already + proposed them in a PPA package, but for whatever reason he didn't care + of actually uploading the changes to ubuntu proper. Meaning the changes + are actually quite tested; plus the patches come from upstream. + + FTR, I have a vested interest in this update, as at dayjob I've got some + 18.04 servers that are also running a patched pure-ftpd just for this. + + [ Original Report ] + Secure (TLS) connections to Pure-FTPd do not work when the OpenSSL 1.1.1 library is installed. My installation was working perfectly until the system-wide OpenSSL 1.1.1 update was made available a couple days ago. Now, after running apt upgrade, clients are unable to establish TLS connections, as the TLS negotiation tries a couple times and then cancels out. The current stable version of Pure-FTPd from the developer is 1.0.49, but the apt repository only has version 1.0.46. According to the patch notes (https://www.pureftpd.org/project/pure-ftpd/news/), there have been some OpenSSL-related changes made since the 1.0.46 release. However, there are also some other major changes, so this may not be the case of a simple update. Ubuntu Server version: Description: Ubuntu 18.04.2 LTS Release: 18.04 ProblemType: Bug DistroRelease: Ubuntu 18.04 Package: pure-ftpd-mysql 1.0.46-1build1 ProcVersionSignature: Ubuntu 4.15.0-51.55-generic 4.15.18 Uname: Linux 4.15.0-51-generic x86_64 ApportVersion: 2.20.9-0ubuntu7.6 Architecture: amd64 Date: Sun Jun 16 16:51:56 2019 ProcEnviron: TERM=xterm-256color PATH=(custom, no user) LANG=en_US.UTF-8 SHELL=/bin/bash SourcePackage: pure-ftpd UpgradeStatus: No upgrade log present (probably fresh install) modified.conffile..etc.pure-ftpd.db.mysql.conf: [modified] mtime.conffile..etc.pure-ftpd.db.mysql.conf: 2019-05-03T23:51:59.782344 ** Changed in: pure-ftpd (Ubuntu Bionic) Assignee: (unassigned) => Mattia Rizzolo (mapreri) ** Changed in: pure-ftpd (Ubuntu Bionic) Status: Confirmed => In Progress -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1832998 Title: Pure-FTPd Breaks with OpenSSL v1.1.1 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/pure-ftpd/+bug/1832998/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1948910] Re: Old Hungarian letters appears as tofu.
Rather than that, please try the Scribus PPA. If it behaves wrongly in that build as well, please consider sending the bug upstream or writing to Scribus' support mailing list for more details. Honestly, I don't think there is much value in following bugs like this downstream: it's *very* unlikely that we packagers will even try to fix such a bug, instead, it would just clog up the bug tracker. I could perhaps try to reproduce it and if I can confirm forward it upstream myself, but realistically it doesn't make much sense, I probably wouldn't even be able to figure out the characters I'm looking for. This kind of locale-specific bug really needs somebody with a vested interest to peruse it. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1948910 Title: Old Hungarian letters appears as tofu. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/scribus/+bug/1948910/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1948480] Re: [SRU] firejail missing the setuid bit
> There isn't any need to add the debdiff to the bug report if the updated > version of the package has already been uploaded to the SRU queue. Is > this documented somewhere that I've forgotten or don't know about? Mh, that has been my interpretation of the procedure for the last 5+ years I've been doing SRUs at least. Even reading the procedure now, at point 4 it says "Prepare the upload, attach a debdiff to the bug, [...] There is no need to wait before uploading. After upload, the bug status should be changed to In Progress" Besides, my experience with the SRU process is also that I can't quite expect a nowhere timely reply *unless* I also upload, but if I infer from your question here it feels more like that debdiff is only for sponsored uploads and is actually totally unneeded for anybody else. Incidentally, I wouldn't like that it makes unnecessary hard (if not impossible) for non-SRU members to see the diff of what was done while waiting for approval (say I wanted to build the package myself because I'm affected by the bug and can't wait for the SRU team) or if it was rejected. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1948480 Title: [SRU] firejail missing the setuid bit To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/firejail/+bug/1948480/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1948480] Re: [SRU] firejail missing the setuid bit
oh, for procedure's sake, here is the patch, however small it is. ** Patch added: "firejail_0.9.64.4-2_0.9.64.4-2ubuntu20.10.1.debdiff" https://bugs.launchpad.net/ubuntu/+source/firejail/+bug/1948480/+attachment/5535425/+files/firejail_0.9.64.4-2_0.9.64.4-2ubuntu20.10.1.debdiff -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1948480 Title: [SRU] firejail missing the setuid bit To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/firejail/+bug/1948480/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1948480] Re: [SRU] firejail missing the setuid bit
** Summary changed: - firejail not working, presumably SUID missing + [SRU] firejail missing the setuid bit ** Description changed: [Impact] - * the `firejail` binary, which is the main thing this package does, is + * the `firejail` binary, which is the main thing this package does, is inoperable. - * For some reason that I couldn't quickly determine the current build - of 0.9.64.4-2 doesn't have the +s flag on the binary that it should have + * Most likely due to LP: #1938886 the current build of 0.9.64.4-2 + doesn't have the +s flag on the binary that it should have - * It's most likely due to some kind of toolchain bug of back then when - this was built, as a no-change rebuild (what I'm proposing here) fixes - the problem + * Since the above bug is not fixed, a no-change rebuild (what I'm + proposing here) fixes the problem [Test Plan] - * install the package + * install the package - * run whatever command under firejail, currently it errors out, and it + * run whatever command under firejail, currently it errors out, and it should not. [Where problems could occur] - * This is no-change rebuild, if something were to break doing that it + * This is no-change rebuild, if something were to break doing that it would be problematic in many bigger ways than this single package... - [Original report] - Try e.g. firejail --debug --version Expected outcome firejail working Observed outcome Error mkdir: util.c:1019 create_empty_dir_as_root: Permission denied Likely this is because the SUID bit is not set for /usr/bin/firejail. It was set in, at least, 21.04, is set in all checked debian packaged, "Firejail is a SUID security sandbox program (...)" and firejail works if it is set manually. Also compare to https://github.com/netblue30/firejail/issues/4609 VERSIONS Description: Ubuntu 21.10 Release: 21.10 firejail: 0.9.64.4-2 -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1948480 Title: [SRU] firejail missing the setuid bit To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/firejail/+bug/1948480/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1948480] Re: firejail not working, presumably SUID missing
Uploaded to impish, waiting in queue for the SRU team to review. ** Description changed: + [Impact] + + * the `firejail` binary, which is the main thing this package does, is + inoperable. + + * For some reason that I couldn't quickly determine the current build + of 0.9.64.4-2 doesn't have the +s flag on the binary that it should have + + * It's most likely due to some kind of toolchain bug of back then when + this was built, as a no-change rebuild (what I'm proposing here) fixes + the problem + + [Test Plan] + + * install the package + + * run whatever command under firejail, currently it errors out, and it + should not. + + [Where problems could occur] + + * This is no-change rebuild, if something were to break doing that it + would be problematic in many bigger ways than this single package... + + + [Original report] + + Try e.g. firejail --debug --version Expected outcome firejail working Observed outcome Error mkdir: util.c:1019 create_empty_dir_as_root: Permission denied - Likely this is because the SUID bit is not set for /usr/bin/firejail. It was set in, at least, 21.04, is set in all checked debian packaged, "Firejail is a SUID security sandbox program (...)" and firejail works if it is set manually. Also compare to https://github.com/netblue30/firejail/issues/4609 - VERSIONS Description: Ubuntu 21.10 Release: 21.10 firejail: 0.9.64.4-2 -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1948480 Title: [SRU] firejail missing the setuid bit To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/firejail/+bug/1948480/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1948480] Re: firejail not working, presumably SUID missing
** Also affects: firejail (Ubuntu Impish) Importance: Undecided Status: New ** Also affects: firejail (Ubuntu Jammy) Importance: Undecided Status: New ** Changed in: firejail (Ubuntu Jammy) Status: New => Fix Released ** Changed in: firejail (Ubuntu Impish) Importance: Undecided => Critical ** Changed in: firejail (Ubuntu Impish) Status: New => In Progress ** Changed in: firejail (Ubuntu Impish) Assignee: (unassigned) => Mattia Rizzolo (mapreri) -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1948480 Title: firejail not working, presumably SUID missing To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/firejail/+bug/1948480/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
Re: [Bug 1947424] Re: Cannot set pbuilder build locale
I'm quite sure setting it in a conffile loaded by --configfile works. It doesn't in the standard /etc/pbuilderrc and .pbuilderrc. On Sun, 17 Oct 2021, 7:51 pm Jessica Clarke, <1947...@bugs.launchpad.net> wrote: > And re being "a serious limitation", I agree it's less than ideal, but > it should not be an issue for any policy-conforming package, for which > not building under the non-UTF-8 C locale is RC-buggy. > > -- > You received this bug notification because you are subscribed to > pbuilder in Ubuntu. > Matching subscriptions: pbuilder > https://bugs.launchpad.net/bugs/1947424 > > Title: > Cannot set pbuilder build locale > > Status in pbuilder package in Ubuntu: > New > > Bug description: > The build locale cannot be set with pbuilder and always defaults to > "C" (for both LANG and LC_ALL on Launchpad builds) rather than to > "C.UTF-8" as used by sbuild for all official Debian and Ubuntu builds. > This causes FTBFS of various packages that depend on the correct > locale being set on the build system, often noticeable with the test > suites of Python packages for instance. > > The attached patch changes only five lines of code (pbuilder- > buildpackage and pbuilderrc) to allow easy setting of the pbuilder > build locale. Based on local testing the patch works as intended, in > that packages depending on the correct locale which FTBFS using > unpatched pbuilder (yet build successfully with sbuild on Launchpad) > now also build successfully with the local patched pbuilder. Please > consider applying the patch. > > To manage notifications about this bug go to: > > https://bugs.launchpad.net/ubuntu/+source/pbuilder/+bug/1947424/+subscriptions > > Launchpad-Notification-Type: bug > Launchpad-Bug: distribution=ubuntu; sourcepackage=pbuilder; > component=universe; status=New; importance=Wishlist; assignee=None; > Launchpad-Bug-Tags: patch > Launchpad-Bug-Information-Type: Public > Launchpad-Bug-Private: no > Launchpad-Bug-Security-Vulnerability: no > Launchpad-Bug-Commenters: crichton jrtc27 mapreri savoury1 > Launchpad-Bug-Reporter: Rob Savoury (savoury1) > Launchpad-Bug-Modifier: Jessica Clarke (jrtc27) > Launchpad-Message-Rationale: Subscriber (pbuilder in Ubuntu) > Launchpad-Message-For: mapreri > Launchpad-Subscription: pbuilder > > -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1947424 Title: Cannot set pbuilder build locale To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/pbuilder/+bug/1947424/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1947424] Re: Cannot set pbuilder build locale
FWIW, one way to set LC_ALL in pbuilder right now is to set that in a config file that is then loaded from the cli with `--configfile`; that loading is done at a point that makes it possible to overwrite the current default. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1947424 Title: Cannot set pbuilder build locale To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/pbuilder/+bug/1947424/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1947192] Re: [SRU] version 0.185
please also consider that we backports team also have in mind to keep u-d-t (and others) fully up-to-date in the backports suites (this should happen within a few weeks). -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1947192 Title: [SRU] version 0.185 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/ubuntu-dev-tools/+bug/1947192/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
Re: [Bug 1756748] Re: [syncpackage] Allow me to sync multiple packages at one time
@Dan: i don't think it's proper to close 3-years old bugs as "the bug is old" - especially not when the request looks very fine and senseful to me. ? On Thu, 14 Oct 2021, 12:16 am Dan Streetman, <1756...@bugs.launchpad.net> wrote: > as this is years old, closing as wontfix > > ** Changed in: ubuntu-dev-tools (Ubuntu) >Status: Triaged => Won't Fix > > -- > You received this bug notification because you are subscribed to Ubuntu. > https://bugs.launchpad.net/bugs/1756748 > > Title: > [syncpackage] Allow me to sync multiple packages at one time > > Status in ubuntu-dev-tools package in Ubuntu: > Won't Fix > > Bug description: > $ syncpackage botan vc > Usage: syncpackage [options] <.dsc URL/path or package name> > > syncpackage: error: Multiple .dsc URLs/paths or package names > specified: botan, vc > > I should be able to do both at the same time. > > To manage notifications about this bug go to: > > https://bugs.launchpad.net/ubuntu/+source/ubuntu-dev-tools/+bug/1756748/+subscriptions > > > -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1756748 Title: [syncpackage] Allow me to sync multiple packages at one time To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/ubuntu-dev-tools/+bug/1756748/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1920974] Re: Underscore is not visible in the feed with certain settings
Very well, thank you. I uploaded the package to ubuntu focal-proposed, and it's now pending review from the Stable Release Team. You'll asked to test again using the package from focal-prosed later on. Unfortunately I forgot to use a different version in my PPA, so please pay attention that you `apt-get install --reinstall hexchat` when you will. Thank you. ** Changed in: hexchat (Ubuntu Focal) Status: Triaged => In Progress -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1920974 Title: Underscore is not visible in the feed with certain settings To manage notifications about this bug go to: https://bugs.launchpad.net/hexchat-irc/+bug/1920974/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1942699] Re: SRU: Update Telegram Desktop to 2.9.2
(moving back to "triaged" while we wait on the SRU team's answer on this new point) ** Changed in: telegram-desktop (Ubuntu Focal) Status: Won't Fix => Triaged ** Changed in: libtgowt (Ubuntu Focal) Status: Won't Fix => Triaged -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1942699 Title: SRU: Update Telegram Desktop to 2.9.2 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/libtgowt/+bug/1942699/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1922464] Re: GNOME 40: GTK3 apps crash with: Settings schema 'org.gnome.settings-daemon.plugins.xsettings' does not contain a key named 'antialiasing'
@seb128: would you take care of uploading that patch, or should somebody else do it? I'm not a core-dev, so I would still need a sponsor for the actual upload (though I have them already), so if you have the tuits it might just be quicker/easier if you could do it ^^ -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1922464 Title: GNOME 40: GTK3 apps crash with: Settings schema 'org.gnome.settings- daemon.plugins.xsettings' does not contain a key named 'antialiasing' To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gtk+3.0/+bug/1922464/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1922464] Re: GNOME 40: GTK3 apps crash with: Settings schema 'org.gnome.settings-daemon.plugins.xsettings' does not contain a key named 'antialiasing'
@seb128: but is the patch that you uploaded with 3.24.25-1ubuntu4 (i.e. this http://launchpadlibrarian.net/532459482/gtk+3.0_3.24.25-1ubuntu3_3.24.25-1ubuntu4.diff.gz ) really that inappropriate for a SRU on top of the current version in focal-updates? -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1922464 Title: GNOME 40: GTK3 apps crash with: Settings schema 'org.gnome.settings- daemon.plugins.xsettings' does not contain a key named 'antialiasing' To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gtk+3.0/+bug/1922464/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1922464] Re: GNOME 40: GTK3 apps crash with: Settings schema 'org.gnome.settings-daemon.plugins.xsettings' does not contain a key named 'antialiasing'
** Also affects: gtk+3.0 (Ubuntu Focal) Importance: Undecided Status: New ** Also affects: gtk+3.0 (Ubuntu Hirsute) Importance: Undecided Status: New ** No longer affects: gtk+3.0 (Ubuntu Hirsute) ** Changed in: gtk+3.0 (Ubuntu Focal) Status: New => Confirmed -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1922464 Title: GNOME 40: GTK3 apps crash with: Settings schema 'org.gnome.settings- daemon.plugins.xsettings' does not contain a key named 'antialiasing' To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gtk+3.0/+bug/1922464/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1945855] Re: Please remove inkscape from the i386 whitelist
All of those reverse-depends are arch:all, that's what I meant with "not giving me anything" (sorry, I should have been clearer). Now, I didn't know the i386 whitelist comes from germinate, thanks for pointing that out. so it seems that inkscape/i386 is kept because it's needed to build game-data-packager/i386, which is kept only because its binaries (qauke4, quake4-server, etqw, etqw-server)are built only for i386. Honestly, if Ubuntu as a project is taking the way of removing i386 as a whole, I don't believe there is so much value in keeping these 4 binaries in ubuntu. ** Changed in: inkscape (Ubuntu) Status: Invalid => New -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1945855 Title: Please remove inkscape from the i386 whitelist To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/inkscape/+bug/1945855/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1920974] Re: Underscore is not visible in the feed with certain settings
Here is a fixing debdiff. Now, the "problem" is that I don't seem to match the conditions to trigger this bug myself, so I'm unable to verify if it actually works. If somebody is affected, please fill in the "Test plan" section of the description, and if you could also verify that the package available in my ppa https://launchpad.net/~mapreri/+archive/ubuntu/ppa fixes it for you, then I'll copy it over to the main archive. ** Patch added: "2.14.3-3ubuntu0.20.04.2.debdiff" https://bugs.launchpad.net/ubuntu/+source/hexchat/+bug/1920974/+attachment/5530482/+files/2.14.3-3ubuntu0.20.04.2.debdiff -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1920974 Title: Underscore is not visible in the feed with certain settings To manage notifications about this bug go to: https://bugs.launchpad.net/hexchat-irc/+bug/1920974/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1920974] Re: Underscore is not visible in the feed with certain settings
** Description changed: + [Impact] + + * Using monospace fonts, some parts of the glyphs might not be visible +(this is especially evident using some monospsace fonts, there the +underscore is not visible). + + * This came due to a change in behaviour in Pango 1.44. + * The fix makes use of a newer API for Pango>=1.44 that address this +issue. + + [Test Plan] + + + [Where problems could occur] + + * Messing this patch up means text wouldn't appear in the textbox +anymore. so… + + + [Other Info] + + * None here. + + + [ Original report ] + If I have Monospace 9 (default?) as the font in HexChat settings I can not see underscore character '_' in the feed, but if I set it Monospace 10 and set Custom DPI setting in Xfce's Appearance dialog to 94 or smaller, I see the character. ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: hexchat 2.14.3-3 ProcVersionSignature: Ubuntu 5.4.0-67.75-generic 5.4.94 Uname: Linux 5.4.0-67-generic x86_64 NonfreeKernelModules: nvidia ApportVersion: 2.20.11-0ubuntu27.16 Architecture: amd64 CasperMD5CheckResult: skip CurrentDesktop: XFCE Date: Tue Mar 23 18:52:59 2021 InstallationDate: Installed on 2020-05-03 (324 days ago) InstallationMedia: Xubuntu Core 20.04 - amd64 - 20200423 SourcePackage: hexchat UpgradeStatus: No upgrade log present (probably fresh install) -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1920974 Title: Underscore is not visible in the feed with certain settings To manage notifications about this bug go to: https://bugs.launchpad.net/hexchat-irc/+bug/1920974/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1920974] Re: Underscore is not visible in the feed with certain settings
This was fixed in hexchat/2.14.3-5; affected release is probably only focal right now. ** Also affects: hexchat (Ubuntu Hirsute) Importance: Undecided Status: New ** Also affects: hexchat (Ubuntu Focal) Importance: Undecided Status: New ** Also affects: hexchat (Ubuntu Impish) Importance: Undecided Status: New ** Changed in: hexchat (Ubuntu Hirsute) Status: New => Fix Released ** Changed in: hexchat (Ubuntu Impish) Status: New => Fix Released ** Changed in: hexchat (Ubuntu Focal) Status: New => Triaged ** Changed in: hexchat (Ubuntu Focal) Importance: Undecided => Medium -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1920974 Title: Underscore is not visible in the feed with certain settings To manage notifications about this bug go to: https://bugs.launchpad.net/hexchat-irc/+bug/1920974/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1920974] Re: Underscore is not visible in the feed with certain settings
This is the fixing patch: https://salsa.debian.org/debian/hexchat/-/commit/a5687dbd864d495d01f8c1a054f5830bc1127ada -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1920974 Title: Underscore is not visible in the feed with certain settings To manage notifications about this bug go to: https://bugs.launchpad.net/hexchat-irc/+bug/1920974/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1945855] [NEW] Please remove inkscape from the i386 whitelist
Public bug reported: I don't know why inkscape was kept in i386, but honestly I don't think it has any reason to stay in an arch that is more and more dead and not really cared of in Ubuntu. reverse-depends -r impish -a i386 src:inkscape is not giving me anything, so please consider dropping it. ** Affects: inkscape (Ubuntu) Importance: Undecided Assignee: Ubuntu Package Archive Administrators (ubuntu-archive) Status: New -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1945855 Title: Please remove inkscape from the i386 whitelist To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/inkscape/+bug/1945855/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
Re: [Bug 1943984] Re: No archive files for static compilation are included in the -dev package
As a member of the Debian LibreOffice Team, and also as an Ubuntu Developer, I'm likewise not convinced that starting to build and ship graphite2's static library is a really useful thing to do. I'm personally generically against static libraries, since I regularly see grief caused by poor tracking of statically-builtand or embedded things. And I don't really buy the need to save space when talking about a 137328 bytes shared lib (taken from the last build of graphite2 in Sid, that's the size of the .so). It feels like you are building some kind to system image that you'd then flash into some embedded thingy. I don't think there is much value in saving...what, a dozen kB perhaps? (I haven't tried building the .a, so happy to get the number). If your system is so constrained in space you're likely going to need some much more dedicated work to reduce the size of all components anyway; similarly if you are after the (normally uncountable) performance improvement of statically linked binaries. On Wed, 29 Sep 2021, 1:06 pm Sebastien Bacher, <1943...@bugs.launchpad.net> wrote: > Debian wontfixed the change so it means we will need to carry a delta at > the cost of increased workload from our team if we take the change. Not > saying that we should be we need to weight the cost over time and the > benefit > > -- > You received this bug notification because you are subscribed to Ubuntu. > https://bugs.launchpad.net/bugs/1943984 > > Title: > No archive files for static compilation are included in the -dev > package > > Status in graphite2 package in Ubuntu: > New > Status in graphite2 package in Debian: > Won't Fix > > Bug description: > There is no libgraphite2.a file, so it is not possible to compile > statically against this library. See attached patch to solve this. > > To manage notifications about this bug go to: > > https://bugs.launchpad.net/ubuntu/+source/graphite2/+bug/1943984/+subscriptions > > > -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1943984 Title: No archive files for static compilation are included in the -dev package To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/graphite2/+bug/1943984/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1942699] Re: SRU: Update Telegram Desktop to 2.9.2
reuploaded, sorry for the delay. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1942699 Title: SRU: Update Telegram Desktop to 2.9.2 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/libtgowt/+bug/1942699/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs