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:
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
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
gt;
> 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.
>
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
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
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
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
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
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
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
**
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
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
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,
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
@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
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
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
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) => (unassig
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
** 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.
** 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.
** 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
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
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
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
--
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:
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
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
"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
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
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
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
** 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
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..
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
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
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
> 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.
> 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.
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.
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.
@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
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:
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)
** 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
*** 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
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) =>
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
** 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
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
ged 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 (mapre
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
+
=> 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
** 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
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
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
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
ss
** 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 TypeEr
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
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
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
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:
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
ogress
** 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 Ri
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:
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
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
"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)
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
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.
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"
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
*** 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
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
--
Yo
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*
> 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
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
** 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
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
ish)
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 i
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
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
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.
@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:
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
(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
@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
@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
** 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
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
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
** 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
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
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
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
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
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:
in the distribution.
** Bug watch added: Scribus Mantis Bug Tracker #16637
https://bugs.scribus.net/view.php?id=16637
** Changed in: scribus (Ubuntu)
Status: Confirmed => Fix Committed
** Changed in: scribus (Ubuntu)
Assignee: (unassigned) => Mattia Rizzolo (mapreri)
--
You re
from my (devscripts) side, no idea. also I have no clue how a command
that has || in there can even "return an error code".
I'm strongly convinced there is nothing special in devscripts that could
cause this, so I'm not considering it a bug in there.
** Changed in: devscripts (Ubuntu)
1 - 100 of 1400 matches
Mail list logo
