** Changed in: far2l (Ubuntu)
Status: Fix Committed => Invalid
--
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
** Changed in: far2l (Ubuntu)
Status: Fix Committed => Invalid
--
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/2065491
Title:
[BPO] far2l/2.6.0~beta+ds-1ubuntu0.1 from
just remember that in Debian alternative build-depends are count *only*
in backports, meaning that the first alternative should be what's in
actual use in sid at the time.
I recommend you do have a deeper look at qtbase5-dev, as you said it's
very odd for it to not work in xca's case.
--
You
just remember that in Debian alternative build-depends are count *only*
in backports, meaning that the first alternative should be what's in
actual use in sid at the time.
I recommend you do have a deeper look at qtbase5-dev, as you said it's
very odd for it to not work in xca's case.
--
You
FWIW, this is the change that Thomas mentions:
https://salsa.debian.org/debian/xca/-/commit/bbce8d50361bd0593ba4be88c3442fcc0527a400
I'm a bit confused: why are you referencing an explicit library package
in build-dep instead of using a -dev package (in this case,
qtbase5-dev)?
In any case, go
FWIW, this is the change that Thomas mentions:
https://salsa.debian.org/debian/xca/-/commit/bbce8d50361bd0593ba4be88c3442fcc0527a400
I'm a bit confused: why are you referencing an explicit library package
in build-dep instead of using a -dev package (in this case,
qtbase5-dev)?
In any case, go
** Changed in: xca (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/2071361
Title:
[BPO] xca 2.6.0-1 to noble, jammy
To manage notifications about this bug go
** Changed in: xca (Ubuntu)
Status: New => Invalid
--
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/2071361
Title:
[BPO] xca 2.6.0-1 to noble, jammy
To manage notifications
approved, 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/2067261
Title:
[BPO] libreoffice 7.6.7 for
approved, thank you!
** Changed in: libreoffice (Ubuntu Jammy)
Status: In Progress => Fix Released
--
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/2067261
Title:
[BPO]
** 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
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
Backporters, which is subscribed to the bug report.
https://bugs.launchpad.net/bugs/2065359
Title:
[BPO]
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]
** Changed in: far2l (Ubuntu)
Status: New => Incomplete
--
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/2065491
Title:
[BPO] far2l/2.6.0~beta+ds-1ubuntu0.1 from noble-updates
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
Backporters, which is subscribed to the bug report.
https://bugs.launchpad.net/bugs/2008583
Title:
VMware nested under KVM stopped working on 5.19
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
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
Backporters, which is subscribed to the bug report.
https://bugs.launchpad.net/bugs/2062140
Title:
[BPO]
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
, and re-installed only the OS partition.
JM2C
Mattia
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1874662
Title:
Corrupted installation medium
To manage notifications about this bug go to:
https
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,
&
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
Note that the Ubuntu backports team does not provide prepare backports
themselves, so you'd need to find some Ubuntu Developer willing to do
that.
See https://wiki.ubuntu.com/UbuntuBackports
** Changed in: git-credential-oauth (Ubuntu)
Status: New => Invalid
** Also affects:
approved, thank you
** Changed in: carla (Ubuntu Jammy)
Status: New => Fix Released
--
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/2049779
Title:
[BPO] carla/2.5.8-0ubuntu1
on the next
one.
--
regards,
Mattia Rizzolo
GPG Key: 66AE 2B4A FCCF 3F52 DA18 4D18 4B04 3FCD B944 4540 .''`.
More about me: https://mapreri.org : :' :
Launchpad user: https://launchpad.net/~mapreri `. `'`
Debian QA page
thank you, approved!
** Changed in: libreoffice (Ubuntu Jammy)
Status: In Progress => Fix Released
--
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/2039150
Title:
[BPO]
@BPO team: did we ever decide on whether, for the sake of not breaking
upgrades, we care about -proposed vs -updates?
--
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/2039150
Title:
this has now been published.
** Changed in: libreoffice (Ubuntu Jammy)
Status: Fix Committed => Fix Released
--
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/2033645
Title:
Right. Just upload and ping the bug once that's through!
--
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/2033645
Title:
[BPO] libreoffice 7.5.6 for jammy
To manage notifications
Of course, this is fine.
I don't see libreoffice in the jammy queue, so feel free to upload :)
--
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/2033645
Title:
[BPO] libreoffice 7.5.6
we need a meeting for.
>
> Does that date work for everyone?
27th is good for me. And I agree we don't have anything pressing to
discuss.
I'll actually be travelling elsewhere then, but I should be able to make
it without any problem.
--
regards,
Mattia Rizzolo
GPG
approved, sorry it took so long.
** Changed in: rednotebook (Ubuntu)
Status: New => Invalid
** Changed in: rednotebook (Ubuntu Jammy)
Status: In Progress => Fix Released
--
You received this bug notification because you are a member of Ubuntu
Backporters, which is subscribed to
approved, thank you for the update!
** Changed in: carla (Ubuntu Jammy)
Status: In Progress => Fix Released
--
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/2030302
Title:
[BPO]
I don't feel strongly against this, so I'm accepting this.
It is kind of out of line with what we normally like, however.
** Also affects: mozc (Ubuntu Jammy)
Importance: Undecided
Status: New
** Changed in: mozc (Ubuntu Jammy)
Status: New => Fix Released
** Changed in: mozc
thank you for your work!
** Changed in: libreoffice (Ubuntu Jammy)
Status: In Progress => Fix Released
--
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/2029130
Title:
[BPO]
Right, well.. backports are not done to be compatible with the base
distribution, of course. They have to be manually installed by the
system administrators knowing what they are doing exactly for this
reason. But huge incompatibilities for sure make for a "negative
point".
--
You received
Hello Nathan,
we had a couple of meetings in the Backports and we have some concerns
about this proposed update:
1) you haven't provided any debdiffs, nor it's clear who is going to prepare
the backports and do the future maintenance, as you don't seem to be an active
Ubuntu contributor
2)
uot; pocket.
> >> * Define a set of rules to handle the Backports Team memberships, its
> >> internal structure and members' responsbilities.
> >>
> >> Would the Backporters Team be willing to adopt this as their Charter?
> >>
> >> Thanks,
&
** Also affects: nfs-utils (Ubuntu Focal)
Importance: Undecided
Status: New
** Also affects: nfs-utils (Ubuntu Bionic)
Importance: Undecided
Status: New
** Changed in: nfs-utils (Ubuntu)
Status: New => Invalid
--
You received this bug notification because you are a
sure, approved :)
** Also affects: carla (Ubuntu Jammy)
Importance: Undecided
Status: New
** Changed in: carla (Ubuntu)
Status: In Progress => Invalid
** Changed in: carla (Ubuntu Jammy)
Status: New => Fix Released
--
You received this bug notification because you are
** Changed in: libreoffice (Ubuntu Bionic)
Status: In Progress => Fix Released
** Changed in: libreoffice (Ubuntu Focal)
Status: In Progress => Fix Released
** Changed in: libreoffice (Ubuntu Jammy)
Status: In Progress => Fix Released
--
You received this bug notification
Yes, it seems that René didn't follow the latest rules about epochs, and
used it to revent accidental uploads (multiple!) of 7.5 to unstable
instead of experimental.
The current policy states that in those cases he should have used the
+really notation, but I reckon he wouldn't have liked to
approved the jammy bpo.
I'm rejecting kinetic since that's out of policy (non-LTS target).
Please tell us if you have some special needs for kinetic.
** Changed in: borgmatic (Ubuntu)
Status: New => Invalid
** Changed in: borgmatic (Ubuntu Jammy)
Status: New => Fix Released
**
good for me.
** Changed in: studio-controls (Ubuntu Jammy)
Status: In Progress => Fix Released
--
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/2012945
Title:
[BPO]
d so do those who
aspire to actually be part of the team. But people who interact with
us (i.e. those contributing backported packages) really have no
business with these documents.
--
regards,
Mattia Rizzolo
GPG Key: 66AE 2B4A FCCF 3F52 DA18 4D18 4B04 3FCD B944 4540
y are (and keep being) interested in. I don't imagine
these people forming any kind of submcommunity around backports, rather
those being mostly regular ubuntu develpers that have an extra interest.
Are we trying to assure these people? I joined this team reboot because
in the past the team ju
I just committed 0f3d2fed2a4ed67b90b5d49aab25ca2bda5d9d37 updating
requestbackport.
** Changed in: ubuntu-dev-tools (Ubuntu)
Status: New => Fix Committed
--
You received this bug notification because you are a member of Ubuntu
Backporters, which is subscribed to the bug report.
@Fantu: please see
https://wiki.ubuntu.com/UbuntuBackports#Finding_a_Sponsor for the
details regarding sponsorship.
I'm subscribing ~ubuntu-sponsors for now and see if somebody picks it
up, or you might want to check with your usual ubuntu sponsor, if you
have one.
--
You received this bug
accepted.
** Changed in: elfutils (Ubuntu Jammy)
Status: New => Fix Released
--
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/1997189
Title:
[BPO] elfutils/0.188-1 from Lunar
ah, you already uploaded, accepted.
--
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/1998624
Title:
[BPO] python-pyelftools/0.29-1 from Kinetic
To manage notifications about this bug
If this is a plain backport without any change, feel free to go ahead.
** Changed in: python-pyelftools (Ubuntu Jammy)
Status: New => Triaged
** Changed in: python-pyelftools (Ubuntu Jammy)
Status: Triaged => Fix Released
--
You received this bug notification because you are a
** Changed in: ipmctl (Ubuntu Focal)
Status: In Progress => Fix Released
--
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/1968076
Title:
[BPO] ipmctl with support for CPS
We have discussed this in the last Backporters meeting, and we decided
not to accept this, as a simple performance bug, which is not what the
backport pocket is intended for (that's more about new features).
** Also affects: man-db (Ubuntu Focal)
Importance: Undecided
Status: New
**
g that the service is gone?
--
regards,
Mattia Rizzolo
GPG Key: 66AE 2B4A FCCF 3F52 DA18 4D18 4B04 3FCD B944 4540 .''`.
More about me: https://mapreri.org : :' :
Launchpad user: https://launchpad.net/~mapreri `. `'`
Debian QA page: https://
ed at some point?
--
regards,
Mattia Rizzolo
GPG Key: 66AE 2B4A FCCF 3F52 DA18 4D18 4B04 3FCD B944 4540 .''`.
More about me: https://mapreri.org : :' :
Launchpad user: https://launchpad.net/~mapreri `. `'`
Debian QA p
@teward: look at https://gitlab.com/cjwatson/man-
db/-/merge_requests/2/diffs - it's quite the big change to defend for a
SRU. or, rather, quite deep into the code.
** Description changed:
[Impact]
* Users of man-db/2.9.1-1 in focal are sometimes facing
unresponsiveness when man-db is
From what I read (and remember), the command doesn't freeze but just takes
a bit long.
Honestly I don't really consider such issue worth a backport, and it's not
really bringing any new feature to the table (at least, you are not
describing anything).
I was thinking that perhaps this could be
hich… in case the
meeting chair is a different person, the casting vote is still in hands
of the team chair, hopefully it's obvious).
These details are the only points I have to make on the two documents.
Thank you for working on them, and sorry it took me forever to read
through them -.-
--
r
** Also affects: elfutils (Ubuntu Jammy)
Importance: Undecided
Status: New
** Changed in: elfutils (Ubuntu Jammy)
Status: New => Fix Released
--
You received this bug notification because you are a member of Ubuntu
Backporters, which is subscribed to the bug report.
** Also affects: dh-python (Ubuntu Focal)
Importance: Undecided
Status: New
** Changed in: dh-python (Ubuntu)
Status: New => Fix Released
--
You received this bug notification because you are a member of Ubuntu
Backporters, which is subscribed to the bug report.
sure, I assume it's a no-change rebuild, if so then go ahead with an
upload :)
** Also affects: limnoria (Ubuntu Jammy)
Importance: Undecided
Status: New
** Changed in: limnoria (Ubuntu)
Status: New => Fix Released
--
You received this bug notification because you are a member
egards,
Mattia Rizzolo
GPG Key: 66AE 2B4A FCCF 3F52 DA18 4D18 4B04 3FCD B944 4540 .''`.
More about me: https://mapreri.org : :' :
Launchpad user: https://launchpad.net/~mapreri `. `'`
Debian QA page: https://qa.debi
On Fri, Jul 15, 2022 at 10:28:17AM -0400, Dan Streetman wrote:
> On Wed, Jul 13, 2022 at 12:50 PM Mattia Rizzolo wrote:
> >
> > On Wed, Jul 13, 2022 at 11:06:10AM -0400, Dan Streetman wrote:
> > > very sorry for the late notice, but I can't make the backporters
> >
hing I would have like to report this meeting is that I
uploaded a bunch of debhelper packages to bpo, up for review if you have
some time (there is a tracking bug).
--
regards,
Mattia Rizzolo
GPG Key: 66AE 2B4A FCCF 3F52 DA18 4D18 4B04 3FCD B944 4540 .''`.
More ab
bionic is not really feasible anymore, since newer devscripts requires
dpkg-dev (>= 1.19.1) and libgitlab-api-v4-perl (and libfile-dirlist-
perl). I haven't investigated whether it's easy to drop those
dependencies, but I'd propose to just forget about bionic for
devscripts' backports.
**
for focal this is a plain backport with no change besides a changelog
entry, and I've just uploaded it.
--
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/1980579
Title:
[BPO]
** No longer affects: libfile-dirlist-perl (Ubuntu Bionic)
** Description changed:
[Impact]
- * This is a new dependency of devscripts/2.20.5, and since we are
+ * This is a new dependency of devscripts/2.20.5, and since we are
backporting a newer version of it, it's nicer to have it
focal uploaded.
--
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/1980580
Title:
[BPO] libfile-dirlist-perl/0.05-2 from jammy
To manage notifications about this bug go to:
thank you for your contribution, and sorry it took so long for handling
this request!
** Changed in: memtest86+ (Ubuntu Focal)
Status: In Progress => Fix Released
--
You received this bug notification because you are a member of Ubuntu
Backporters, which is subscribed to the bug report.
(in fact, this is not really different than debian: also debian
backports require the proposed version to be available in the "next
stable", to assure the upgrade path)
--
You received this bug notification because you are a member of Ubuntu
Backporters, which is subscribed to the bug report.
I think, looking at the list of packages currently in the backports
pockets, nothing need rebuilding for that bug, right?
--
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/1965758
Title:
uploads approved.
** Changed in: debugedit (Ubuntu Focal)
Status: New => Invalid
** Changed in: debhelper (Ubuntu Focal)
Status: New => Fix Released
** Changed in: debhelper (Ubuntu Bionic)
Status: New => Fix Released
--
You received this bug notification because you are
Thank you Dan!
I accepted both uploads!
** Changed in: debhelper (Ubuntu Bionic)
Status: New => Fix Released
** Changed in: debhelper (Ubuntu Focal)
Status: New => Fix Released
--
You received this bug notification because you are a member of Ubuntu
Backporters, which is
another meeting planned that overlaps, so I wouldn't
be able to match that; furthermore I already know that I wouldn't be
able to attend on June 29th either, so shifting would likely match
better my calender (I'm selfish here!) ;)
--
regards,
Mattia Rizzolo
GPG Key: 66AE
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
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
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
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
**
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
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
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,
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
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
@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
Backporters,
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
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
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
UbuntuBackports/Policies?action=recall=6
>
> let me know if either of you have any comments or concerns, otherwise
> if the charter looks ok to you, we can send it up to the TB sometime
> next week.
I'm good with those 2 versions, thank you.
--
regards,
Mattia Rizzo
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
1 - 100 of 1754 matches
Mail list logo
