@Rolf
Your patch in the debdiff does not have DEP3 headers - https://dep-
team.pages.debian.net/deps/dep3/ - which helps to identify who wrote the
patch, why it's there, etc. as metadata *in* the patch. While the patch
looks good, could you edit your patch to include the DEP3
metadata/headers (if
I'll sponsor the debdiff within a few hours.
** Changed in: repo (Ubuntu)
Assignee: (unassigned) => Thomas Ward (teward)
** Changed in: repo (Ubuntu)
Status: New => In Progress
** Also affects: repo (Ubuntu Noble)
Importance: Undecided
Status: New
** Chang
+1 acceptance from me as a Backporter and a developer (who jackpots via
PPA sbuild from Debian himself)
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/2114843
Title:
[BPO] sbuild 0.88.3ubuntu2.1 from
** Information type changed from Public to Public Security
** Changed in: nginx (Ubuntu)
Status: Confirmed => Invalid
** Changed in: nginx (Ubuntu)
Status: Invalid => Fix Released
** Also affects: nginx (Ubuntu Noble)
Importance: Undecided
Status: New
** Changed in: ngin
Uploaded a fix to Questing. Accepted into the system for building.
This should fix the autopkgtests of apache2 against itself. There are
probably still other autopkgtests that'll fail.
** Changed in: apache2 (Ubuntu Questing)
Status: In Progress => Fix Committed
--
You received this bug
** Changed in: apache2 (Ubuntu Questing)
Status: New => In Progress
** Changed in: apache2 (Ubuntu Questing)
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/21124
Andreas:
Would it be prudent to just update the entire test suite and pull that
in as an update and then patch the source of apache2 via the commit?
While we're here I mean since we can get any other newer tests etc. made
available in the test suite.
--
You received this bug notification because
** Changed in: apache2 (Ubuntu Questing)
Assignee: (unassigned) => Thomas Ward (teward)
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/2112429
Title:
[questing] [autopkgtest] Apache2 2.4
** Description changed:
Discovered through update_excuses and confirmed locally in an LXD
autopkgtest container (from https://github.com/canonical/ubuntu-
maintainers-handbook/blob/main/PackageTests.md to create it), the
autopkgtests on 2.4.63-1ubuntu2 fail for apache2's test suite.
I
Public bug reported:
Discovered through update_excuses and confirmed locally in an LXD
autopkgtest container (from https://github.com/canonical/ubuntu-
maintainers-handbook/blob/main/PackageTests.md to create it), the
autopkgtests on 2.4.63-1ubuntu2 fail for apache2's test suite.
It fails on debi
I do all my initial package builds in a cleaned source tree with
`debuild -S -sa -d` to start with. (There's issues with sbuild chroot
builds for plucky due to librtmp1 and other things, or I'd be using
sbuild to do all my source builds)
I did some checking and the debdiff applied, but then I jus
Status: In Progress => Incomplete
** Also affects: bluez (Ubuntu Questing)
Importance: High
Assignee: Thomas Ward (teward)
Status: In Progress
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net
Sponsored bluez_5.82-1ubuntu1 to Questing, which shouldn't need SRU team
to look at it.
** Changed in: bluez (Ubuntu Questing)
Status: In Progress => Fix Committed
** Changed in: bluez (Ubuntu Questing)
Milestone: ubuntu-25.04 => None
--
You received this bug notification because you
per Yao Wei, Questing is also impacted as the patch was applied in an
upstream revision *after* 5.82 was released, thus it is not in Questing.
So we'll patch Questing as well, unless a newer Upstream release is made
available in Debian and we sync it to Questing.
--
You received this bug notifica
I'll sponsor this in the AM after I get some rest for the night. ~10-12
hours from now expect me to note on here that it's been uploaded to
proposed for the SRU team to look at it.
** Changed in: bluez (Ubuntu)
Assignee: Yao Wei (medicalwei) => Thomas Ward (teward)
** Chan
Not an NGINX bug. Your letsencrypt certificates are missing.
See this error in the data output:
May 21 18:37:08 Thoth nginx[21417]: 2025/05/21 18:37:08 [emerg]
21417#21417: cannot load certificate "/etc/letsencrypt/live/web-
gsjkr.ddns.net/fullchain.pem": BIO_new_file() failed (SSL:
error:80
According to https://ubuntu.com/security/CVE-2025-23419 this is already
fixed.
** CVE added: https://cve.mitre.org/cgi-bin/cvename.cgi?name=2025-23419
** Changed in: nginx (Ubuntu)
Status: In Progress => Fix Released
--
You received this bug notification because you are a member of Ubunt
Not a bug in the package.
If you read the error output this is your current most persistent error:
Apr 22 12:19:15 nginx nginx[20469]: nginx: [emerg] open()
"/etc/nginx/proxy_params" failed (24: Too many open files) in
/etc/nginx/sites-enabled/collabora-rev-proxy.conf:21
This suggests you've exc
@mapreri: target Distribution is based on changelog entry I believe when
uploaded, even with `-d DIST` in `sbuild`. So that's something to
always check in changelog that it targets the correct pocket (jammy-
backports instead of jammy).
--
You received this bug notification because you are a mem
Thanks to Zixing Liu (liushuyu-011) for pinging me in Ubuntu Development
on Matrix yesterday to ask if they can pilot the patch upload, I have a
lot of things that piled onto my plate last minute that's eating ALL my
time right now (major critical-level non-Ubuntu stuff).
Because cockpit has the b
** Changed in: cockpit (Ubuntu Jammy)
Assignee: (unassigned) => Zixing Liu (liushuyu-011)
** Changed in: cockpit (Ubuntu Noble)
Assignee: (unassigned) => Zixing Liu (liushuyu-011)
** Changed in: cockpit (Ubuntu Oracular)
Assignee: (unassigned) => Zixing Liu (liushuyu-011)
** Chang
** Changed in: cockpit (Ubuntu Jammy)
Status: New => Fix Committed
** Changed in: cockpit (Ubuntu Noble)
Status: New => Fix Committed
** Changed in: cockpit (Ubuntu Oracular)
Status: New => Fix Committed
** Changed in: cockpit (Ubuntu Jammy)
Assignee: Zixing Liu (liushu
also Martin, yes, there is a new BPO template *AND* bug prefix to use.
I'll make an exception *this time* for it and just let it through once I
upload/sponsor (had some Major Level Crap to deal with that took
ultimate priority), but for *future* requests you should follow the
template that Andreas
But I can.
Removed backporters.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/2083908
Title:
[SRU] pymodbus 3.6.9-1 from 24.10 (to 24.04)
To manage notifications about this bug go to:
https://bugs
juliak, since it sounds like Synaptic, which is still in Universe,
depends on this, perhaps synaptic should be in the target list because
this would be a 'critical' requirement in Synaptic, if I remember my
packaging right.
--
You received this bug notification because you are a member of Ubuntu
Nope you did nothing bad, you were perfectly in the right. As I said,
unless another sponsor gets to it I'll sponsor your uploads, though that
kind of 'self-approves' which is fine since we have precedent to approve
cockpit due to quality of uploads and need of the package.
As for the developer u
> - I don't know if ~ubuntu-backporters is still a thing, but that wiki
page says they should be subscribed
Andreas, the Backporters team is the people who now approve backports in
the system. It is *no longer* the team that does uploads, testing, etc.
as the entire backports process changed durin
> I subscribed them. It looks like there isn't much of a backports team
left -- e.g. https://launchpad.net/lucid-backports still exists, but no
https://launchpad.net/noble-backports or https://launchpad.net/jammy-
backports
Martin,
Circa 2023, the Backports process was **redesigned entirely**, an
I don't have the ESM licenses available at the moment to license a
trusty, xenial, or bionic container, as the ESM repos for trusty
(legacy), xenial, and bionic have what look like patched Python 2
versions of jinja2 which I cannot test.
I have confirmed this import error will happen on Ubuntu Foc
This requires someone with upload privileges to upload but also requires
someone dedicated to maintain this in Backports. That includes
addressing bug reports and such in Backports.
There has been no movement since Michael Vogt replied, so this needs
someone with upload privileges willing to back
Salsa bug for discussion on 1098477 is https://salsa.debian.org/nginx-
team/nginx/-/issues/23 - we usually do the team discussions on Salsa
there.
** Bug watch added: salsa.debian.org/nginx-team/nginx/-/issues #23
https://salsa.debian.org/nginx-team/nginx/-/issues/23
--
You received this bug
I think the peoblem is multifold and endemic to the Debian approach of
'flavor packages'. The problem is splitting out the nginx binary
components because there are still things that haooen between the
flavors with binary compile-level stuff because not every module is
dynamic.
Open the bug in De
Debdiffs prepared for Security Team review / inclusion. Note that the
specific module is embedded in debian/modules/... so non-standard
patching (aka non-Quilt-patching) was utilized.
Upstream patches were {UPSTREAM_URL}.patch to get the patch files that
were applied.j
--
You received this bug
** Patch added: "debdiff for focal"
https://bugs.launchpad.net/ubuntu/+source/nginx/+bug/1977718/+attachment/5857604/+files/lp1977718-focal.debdiff
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/197
** Patch added: "debdiff for jammy"
https://bugs.launchpad.net/ubuntu/+source/nginx/+bug/1977718/+attachment/5857605/+files/lp1977718-jammy.debdiff
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/197
** Summary changed:
- buffer overflow in nginx rtmp module
+ buffer overflow, null pointer deref in nginx rtmp module
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1977718
Title:
buffer overflow, n
By installing the NGINX main repositories for NGINX, all bugs or issues
with the package need to be sent to NGINX upstream directly, as you are
using third-party repositories.
This is an Invalid bug against the Ubuntu packages of nginx.
** Changed in: nginx (Ubuntu)
Status: Incomplete => I
Additionally, the NGINX upstream repositories **will not** work with
third party modules in the repositories that only work with the older
NGINX that is in the Ubuntu repositories - this is due to version
mismatch, and NOT an Ubuntu issue.
--
You received this bug notification because you are a m
Timo: The bug was closed in Debian the old ways - by hand. Marked Fixed
and Done in Debian, so no the Debian bug isn't open anymore. ;)
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/2081308
Title:
R
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/2096808
Title:
Merge euslisp/jskeus from Debian unstable
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/euslisp
i recently upgraded to 24.04.1 and i think i'm seeing a similar issue...
i am able to play audio to my DAC after connecting through bluetooth using the
gui.
test sound works, VLC works... but i have audirvana installed and when i use
it to
connect to my computer, the DAC doesn't show up as an
Uploads for Noble and Oracular are pending approval from the SRU team.
** Changed in: ubuntustudio-default-settings (Ubuntu Oracular)
Status: Triaged => In Progress
** Changed in: ubuntustudio-default-settings (Ubuntu Noble)
Status: Triaged => In Progress
** Description changed:
+
** Changed in: ubuntustudio-default-settings (Ubuntu Plucky)
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/2087756
Title:
package ubuntustudio-default-set
** Changed in: ubuntustudio-default-settings (Ubuntu Noble)
Assignee: Erich Eickmeyer (eeickmeyer) => Thomas Ward (teward)
** Changed in: ubuntustudio-default-settings (Ubuntu Oracular)
Assignee: Erich Eickmeyer (eeickmeyer) => Thomas Ward (teward)
** Changed in: ubuntustudio-d
*** This bug is a duplicate of bug 2087756 ***
https://bugs.launchpad.net/bugs/2087756
I will note its the Studio flavor's policy/opinion that these setups are
unsupported. Going from vanilla Ubuntu Desktop and then installing
Studio on top of it is not a supported setup, hence the errors you
Public bug reported:
When installing `python3-binwalk` and the package reaches `Setting up`
in Ubuntu 24.04, we see this on-load SyntaxWarning:
/usr/lib/python3/dist-packages/binwalk/core/magic.py:431: SyntaxWarning: invalid
escape sequence '\.'
self.period = re.compile("\.")
This is fixable
This isn't an issue with NGINX, it's an issue with your configuration.
From the output of the journal for your NGINX runs:
dez 02 21:48:16 walter-ubuntu nginx[2210]: 2024/12/02 21:48:16 [emerg]
2210#2210: cannot load certificate
"/home/walter/zapstart/MultiPro02/backend/certs/cert.pem":
BIO_new_fi
I would like to note that adjusting the DlMaxRetries value was
substantially helpful.
To answer @melroyvandenberg:
Yes, apt-cacher-ng responds with a "503 Service Unavailable" along with
the additional notices when package download attempts by the caching
proxy from the actual package source is g
** Summary changed:
- package ubuntustudio-default-settings (not installed) failed to
install/upgrade: Versuch, »/etc/skel/.face« zu überschreiben, welches auch in
Paket desktop-base 12.0.6+nmu1ubuntu1 ist
+ package ubuntustudio-default-settings (not installed) failed to
install/upgrade: Trying
ntu Plucky)
Importance: High
Assignee: Thomas Ward (teward)
Status: Confirmed
** Changed in: filelight (Ubuntu Plucky)
Status: Confirmed => Invalid
** Changed in: filelight (Ubuntu Oracular)
Status: New => Confirmed
** Changed in: filelight (Ubuntu Oracular)
I
Running test builds on my cluster before sponsoring.
** Changed in: filelight (Ubuntu)
Assignee: (unassigned) => Thomas Ward (teward)
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/2084169
Ti
I already committed to Debian Salsa an unreleased -3 of nginx that
resolves this dependency loop. I am going to unilaterally upload that as
an RC fix in Debian. From there we can sync to 25.04 and then SRU fix
this with high bugfix priority for 24.10 and 24.04.
--
You received this bug notificati
** Changed in: nginx (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/2081308
Title:
open() "/etc/nginx/nginx.conf" failed (2: No such file or directory)
To m
Bryce,
This was discussed when I wrote the hooks. Unfortunately we decided
that in itself is a privacy breach and decided to NOT do that. We also
decided that the user should upload that because it can contain
sensitive information.
--
You received this bug notification because you are a membe
To follow up on Sergio's message, please include your
`/etc/nginx/nginx.conf` file here if you believe this is a problem in
the package and not your specific configuration. It's more than likely
you have a `user test_domain;` option in your configuration, and that is
not a valid user, meaning you'
This is easily fixed by using a dhparam that is 2048 or larger. The
underlying OpenSSL libraries no longer permit dhparam under 2048 bits in
size. This is the "failure" in the error logs and is fixable by end
user admins by simply using larger dhparams.
This is not an nginx package issue.
** Ch
@hloeung To get this in Jammy or such would be an extrwmely intrusive
change because we'd have to backport *all* nginx and nginx module source
packages. Just putting this there for the record. While this is fixed
for Mantic and Noble and later, it is too intrusive a fix to backport to
Jammy and s
To echo bryce, to backport this to older releases is nontrivial, as in
order to support a backport of the new reengineered packaging we also
have to backport all other nginx modules. This is a very intrusive
change on older releases.
--
You received this bug notification because you are a member
I apologise. I'll try to post it correctly next time.
On 1/07/2024 5:12 pm, Daniel van Vugt wrote:
> I don't know anything about that connection issue but also this bug
> isn't the right place to discuss it.
>
> If you can take a photo of the Terminal bug and attach it here then
> please do.
>
--
I think you are right. It will either be digested by the system and
fixed or it won't. It's not critical, I'm sure.
There is one thing I'm curious about that you may or may not be able to
help with. I'm getting some odd results when I try to update some
repositories. Connection refused on stati
I see.
It's hard to provide a screenshot to recreate the issue. I should have
been clearer. The problem is that one can't seem to have complete
control of transparency level. It's always tricky because you have to
contend with altered results (YMMV) depending on background, but that to
me seem
Public bug reported:
Not much to add. Trying to get it to work with terminal and it's just
fairly primitive with respect to options.
ProblemType: Bug
DistroRelease: Ubuntu 24.04
Package: xorg 1:7.7+23ubuntu3
ProcVersionSignature: Ubuntu 6.8.0-36.36-generic 6.8.4
Uname: Linux 6.8.0-36-generic x86_
NOTE: I backported locally debootstrap 1.0.136ubuntu1 from Oracular to
Jammy, and **it resolved the issue**. As a result I am certain this is a
debootstrap issue.
** Changed in: ubuntu-dev-tools (Ubuntu)
Status: New => Invalid
** Changed in: debootstrap (Ubuntu)
Importance: Undecided =>
mapreri: Tracked in Debian as https://bugs.debian.org/cgi-
bin/bugreport.cgi?bug=1074383 - any comments we need to have can be
there instead of on this backport bug. (The backport is now Fix
Released in the system as it's published in the archives)
** Bug watch added: Debian Bug tracker #1074383
mapreri: qtbase5-dev a while ago was attempted but DID NOT pull in all
the dependencies, which was odd. Same thing also didn't provide the
proper libs (for some reason) with the upstream build system changes,
which I never had a chance to circle back to addressing.
This is in my list of things to
NOTEL This functionality was NOT available in XCA until 2.6.0. It is
now available in 2.6.0-1 in Debian and will be in the jammy-backports
and noble-backports pocket - once it is built and available, you can use
`sudo apt-get install xca/RELEASE-backports` to install the software
from the Backport
** Also affects: livecd-rootfs (Ubuntu Oracular)
Importance: Undecided
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/2062929
Title:
AppArmor profile policy `unconfined_restrict
Public bug reported:
[Impact]
* XCA 2.6.0 introduces numerous internal bugfixes, but as the best
'bugfix'/feature change it introduces is the capacity to decide
whether to export using older algorithms for PKCS12 files which
enables legacy device support for certificate packages, suc
Prefer server ciphers is off in later configs.
A warning does not necessitate a hard error that needs fixing.
Note that in Ubuntu this nginx.conf originates in Debian, so I would
like the Debian nginx team's opinions on putting this change in Unstable
as well so as not to introduce another delta.
the upload and prep of the SRU debdiff to
noble-updates as a favor to Thomas Ward who is having computer scuff at
the time of the uploading.
-
[Original Description]
I have installed tor browser v13.0.11 on 24.04 (noble). The keyboard
does not operate, when typing no characters are
sync.
+
+ Simon Quigley is handling the upload and prep of the SRU debdiff to
+ noble-updates as a favor to Thomas Ward who is having computer scuff at
+ the time of the uploading.
+
+
+ [Original Description]
+
I have installed tor browser v13.0.11 on 24.04 (noble). The keyboard
does not op
Fixed in Oracular by a sync from Debian.
Because my system is being derp with signing keys and uploads, I've
enlisted another Ubuntu Developer to handle the SRU debdiff.
** Also affects: torbrowser-launcher (Ubuntu Oracular)
Importance: Undecided
Status: Confirmed
** Also affects: torb
Public bug reported:
Sometimes, when we are working with both Ubuntu and Debian, we need to
create a Debian chroot for build testing.
Unfortunately, mk-sbuild is UNABLE to create Debian chroots. Currently,
the first error is that "/bin/true" is nonexistent (it's in
`/usr/bin/true` now). Then, i
waveform: In order to be valid each release needs to have a higher
version. Especially if its the same version then it has to have
0.ubuntuXX.YY.Z if 0 is the base. Otherwise it affects upgrading if we
have the same version in multiple releases.
--
You received this bug notification because you
Note that this is not yet released in Debian. I have a bunch of things
to fix in the packaging first such as lintian issues and copyright
files.
I can debdiff this into Ubuntu as an SRU after the Debian package is
fully functional and compliant with policy.
--
You received this bug notification
"Convenient applicatiom used by server admins" - a little info here on
what it does and WHY it would be useful in older LTSes is important. As
well as why "other functionality" isn't sufficient, in order to justify
the backport.
We also need confirmation that the package works as is when backport
You have a broken configuration file.
May 11 00:15:19 HP-Pavilion-Notebook nginx[1389]: 2024/05/11 00:15:19
[emerg] 1389#1389: unknown directive "listen" in
/etc/nginx/sites-enabled/flask_app:2
You need to refer to your configurations and make sure they're actually
valid. You are probabl
bryce:
We will need to coordinate because an ABI change means we need a
transition of all the extra nginx source packages to have a rebuild.
Because we have ABI compliance now.
We're testing and debugging these in Experimental / Unstable now, as
part of Debian nginx policies to start in experimen
1.26.0 is slated to land in Debian with ABI changes and rebuilds of all
third party modules, just an FYI. This will impact this merge
notice/request
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/20644
Note any Debian changes will appear in 24.10 release when merged in from
Debian. Existing releases will k
not get this unless we decide to SRU it and this doesnt generally qualify for
SRU inclusion.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscrib
You have another service listening on port 80. Figure out what it is
and either stop it or uninstall it and then attempt to run/install
nginx.
** Changed in: nginx (Ubuntu)
Status: New => Invalid
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subs
** Changed in: nginx (Ubuntu)
Importance: Undecided => Wishlist
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/2062058
Title:
Add a UFW firewall config to support QUIC
To manage notifications abo
*** This bug is a duplicate of bug 277 ***
https://bugs.launchpad.net/bugs/277
The 404 issues are tracked in 277.
GPG keys updates were already uploaded, however they may be stuck in
Proposed still pending a fix for the 404 issues.
Due to how versions of software are updated in U
*** This bug is a duplicate of bug 277 ***
https://bugs.launchpad.net/bugs/277
** This bug has been marked a duplicate of bug 277
Download URLs are broken
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs
Your configuration is bad. Refer to the error log output in journalctl:
mar 10 19:00:41 wojciech-To-be-filled-by-O-E-M nginx[1323]: nginx:
[emerg] cannot load certificate "/etc/diaspora/ssl/localhost-
bundle.pem": BIO_new_file() failed (SSL: error:02001002:system
library:fopen:No such file or
dir
torbrowser-launcher is only a tool to help download and update (and run)
Tor Browser. It is not actually Tor Browser.
If you are having issues with Tor Browser, I suggest you enlist the help
of the Tor community as issues with Tor Browser itself are not related
to the Launcher tool.
** Changed i
Something with the debdiff broke the translations components, so the
debdiff is rejected.
However, the components provided here work, so uploaded. Both are in
building/pending state.
** Changed in: golang-github-openprinting-goipp (Ubuntu)
Status: New => In Progress
--
You received this
Note ipp-usb applies cleanly, so that's "in progress", while goipp is
"Incomplete"
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/2055346
Title:
Need sponsoring: goipp 1.1.0 and ipp-usb 0.9.24 for no
Rejection on goipp 1.1.0.
Fails to apply cleanly. Please address the differences from upstream
that are returned by dpkg-buildpackage.
---
$ debuild -S -sa -d
dpkg-buildpackage -us -uc -ui -S -sa -d
dpkg-buildpackage: info: source package golang-github-openprinting-goipp
dpkg-buildpackage: inf
** Changed in: ipp-usb (Ubuntu)
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/2055346
Title:
Need sponsoring: goipp 1.1.0 and ipp-usb 0.9.24 for noble
To manage no
** Changed in: golang-github-openprinting-goipp (Ubuntu)
Assignee: (unassigned) => Thomas Ward (teward)
** Changed in: ipp-usb (Ubuntu)
Assignee: (unassigned) => Thomas Ward (teward)
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscri
"failed to install/upgrade" also means that a package failed to
configure. If as Simon says the packages were left unconfigured, then
that means the package is "Installed but failed to restart on upgrade"
which is an action the postinst scripts execute. So it may not be an
'installer' failure but
Looks like during your upgrade a certificate went awry, but this isn't
an NGINX issue, it's the maintenance of your system on your end.
From the journalctl data:
Jun 04 14:21:05 heliopolis-aws nginx[44002]: nginx: [emerg] cannot load
certificate "/etc/ssl/certs/heliosd.crt": BIO_new_file() faile
NACK as is. (negative acknowledgement aka "Debdiff Rejected")
You are attempting to submit a new upstream version not in the Ubuntu
repositories. Unlike Debian, an Ubuntu backport requires a little more
work to push this in.
Jammy has 03.00.00.0423-1. Your debdiff is for 03.00.00.0429 which is
If you can give me an extra day or two (I'm suffering from COVID right
now), I can sponsor this. I'll let the other backporters handle
approval, etc. but uploading the package is something that only takes a
few minutes on my part. (Just need the patience - COVID is evil)
--
You received this bu
If Qt6 is dead upstream, then it's probably a candidate for removal as
soon as Qt5 is retired.
Note that because Debian has refused to even add Qt6 because QtChooser
is dead upstream by design, and I'm gathering as such should not be used
with Qt6, I opened a Debian bug suggesting that they mark t
*** This bug is a duplicate of bug 1967572 ***
https://bugs.launchpad.net/bugs/1967572
Duplicate of #1967572 due to same traceback on failure.
** This bug has been marked a duplicate of bug 1967572
torbrowser-launcher crashed with move(self, int, int) in main(): argument
1 has unexpecte
Note that your Debian source target will be NGINX 1.20.2-1 once it
lands, this was uploaded to ftp-master by myself today after I was given
access to upload by Ondrej Novy.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.l
You have a symlink in /etc/nginx/sites-enabled that points to a
nonexistent config file:
nginx[1326]: nginx: [emerg] open() "/etc/nginx/sites-
enabled/frappe.conf" failed (2: No such file or directory) in
/etc/nginx/nginx.conf:62
This is not an NGINX package bug but a local config issue.
** Chan
*** This bug is a duplicate of bug 1969752 ***
https://bugs.launchpad.net/bugs/1969752
** This bug has been marked a duplicate of bug 1969752
oss4-dkms '-mfloat-abi=hard' build failure
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ub
1 - 100 of 3216 matches
Mail list logo
