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
FYI #1969145 has been closed as a duplicate of this bug, and sponsors
unsubscribed from that bug.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1969752
Title:
oss4-dkms '-mfloat-abi=hard' build fail
YOu're welcome, that's the workaround for these cases.
Note that this exact issue was 'discussed' back in 2015 by the upstream
Debian team and they rejected changing it because IPv6 being disabled is
"non-standard", and a user/admin level decision at the endpoints of
things, so when anything 'non-
This is a pretty old issue but in Debian they made a decision to not
accomodate this back in 2015 for when IPv6 is disabled on systems on the
basis of "not only is it non-standard but it's nonsensical":
https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=779825#97
The workaround for this is when d
CentOS uses completely different packaging than Debian. The problem
here is that the Debian and Ubuntu developers of NGINX decided to
support "the most common setups" - the Debian and thus Ubuntu default
configurations ship both IPv4 and IPv6 support. You can fix this by
changing the `/etc/nginx/
How are you launching the launcher? So we can have a 'minimal
reprocudible example' to test with.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1967572
Title:
torbrowser-launcher crashed with mov
Tested similar BTRFS root partition layout here, and it exploded as
stated here. I was testing in a VM with a fresh ZSync.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1966774
Title:
btrfs partion
The drivers from Epson are not part of Ubuntu. You will need to obtain
support for them from Epson.
** Changed in: sane-backends (Ubuntu)
Status: New => Invalid
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launc
brscan is not part of Ubuntu. You will need to obtain support for it
from Brother.
If there is currently an issue involving the built-in drivers from the
sane-backends package, please change the status back.
** Changed in: sane-backends (Ubuntu)
Status: Confirmed => Invalid
--
You receiv
All currently supported versions of Ubuntu have sane-backends 1.0.27 or
later.
If this issue still occurs with a Pixma MX7600, please change the status
of this bug back.
For any device except a Pixma MX7600 that currently shows a similar
issue, please open a separate bug. Do not comment on this o
Thank you for reporting this bug to Ubuntu.
Ubuntu 16.04 (xenial) reached end-of-standard-support on April 29, 2021.
Ubuntu 14.04 (trusty) reached end-of-standard-support on April 25, 2019.
See this document for currently supported Ubuntu releases:
https://wiki.ubuntu.com/Releases
We appreciate
Thank you for reporting this bug to Ubuntu.
Ubuntu 14.04 (trusty) reached end-of-standard-support on April 25, 2019.
See this document for currently supported Ubuntu releases:
https://wiki.ubuntu.com/Releases
We appreciate that this bug may be old and you might not be interested
in discussing it
Thank you for reporting this bug to Ubuntu.
Ubuntu 15.04 (vivid) reached end-of-life on February 4, 2016.
Ubuntu 14.04 (trusty) reached end-of-standard-support on April 25, 2019.
See this document for currently supported Ubuntu releases:
https://wiki.ubuntu.com/Releases
We appreciate that this b
Thank you for reporting this bug to Ubuntu.
Ubuntu 15.04 (vivid) reached end-of-life on February 4, 2016.
Ubuntu 14.04 (trusty) reached end-of-standard-support on April 25, 2019.
See this document for currently supported Ubuntu releases:
https://wiki.ubuntu.com/Releases
We appreciate that this b
Thank you for reporting this bug to Ubuntu.
Ubuntu 13.10 (saucy) reached end-of-life on July 17, 2014.
See this document for currently supported Ubuntu releases:
https://wiki.ubuntu.com/Releases
We appreciate that this bug may be old and you might not be interested
in discussing it any more. But
Thank you for reporting this bug to Ubuntu.
Ubuntu 13.10 (saucy) reached end-of-life on July 17, 2014.
See this document for currently supported Ubuntu releases:
https://wiki.ubuntu.com/Releases
We appreciate that this bug may be old and you might not be interested
in discussing it any more. But
Thank you for reporting this bug to Ubuntu.
Ubuntu 12.04 (precise) reached end-of-life on April 28, 2017.
See this document for currently supported Ubuntu releases:
https://wiki.ubuntu.com/Releases
We appreciate that this bug may be old and you might not be interested
in discussing it any more.
Thank you for reporting this bug to Ubuntu.
Ubuntu 12.04 (precise) reached end-of-life on April 28, 2017.
See this document for currently supported Ubuntu releases:
https://wiki.ubuntu.com/Releases
We appreciate that this bug may be old and you might not be interested
in discussing it any more.
** Changed in: sane-backends (Ubuntu)
Status: Confirmed => Incomplete
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1208091
Title:
scanimage assert failure: *** Error in `scanimage': double f
Thank you for reporting this bug to Ubuntu.
Ubuntu 13.04 (raring) reached end-of-life on January 27, 2014.
See this document for currently supported Ubuntu releases:
https://wiki.ubuntu.com/Releases
We appreciate that this bug may be old and you might not be interested
in discussing it any more.
Thank you for reporting this bug to Ubuntu.
Ubuntu 12.04 (precise) reached end-of-life on April 28, 2017.
See this document for currently supported Ubuntu releases:
https://wiki.ubuntu.com/Releases
We appreciate that this bug may be old and you might not be interested
in discussing it any more.
Thank you for reporting this bug to Ubuntu.
Ubuntu 12.04 (precise) reached end-of-life on April 28, 2017.
We appreciate that this bug may be old and you might not be interested
in discussing it any more. But if you are then please upgrade to the
latest Ubuntu version and re-test. If you then find
Thank you for reporting this bug to Ubuntu.
Ubuntu 16.04 (xenial) reached end-of-standard-support on April 29, 2021.
See this document for currently supported Ubuntu releases:
https://wiki.ubuntu.com/Releases
We appreciate that this bug may be old and you might not be interested
in discussing it
Thank you for reporting this bug to Ubuntu.
Ubuntu 10.10 (maverick) reached end-of-life on April 10, 2012.
See this document for currently supported Ubuntu releases:
https://wiki.ubuntu.com/Releases
We appreciate that this bug may be old and you might not be interested
in discussing it any more.
Thank you for reporting this bug to Ubuntu.
Ubuntu 14.04 (trusty) reached end-of-standard-support on April 25, 2019.
See this document for currently supported Ubuntu releases:
https://wiki.ubuntu.com/Releases
We appreciate that this bug may be old and you might not be interested
in discussing it
Thank you for reporting this bug to Ubuntu.
Ubuntu 13.04 (raring) reached end-of-life on January 27, 2014.
Ubuntu 12.04 (precise) reached end-of-life on April 28, 2017.
Ubuntu 11.10 (oneiric) reached end-of-life on May 9, 2013.
Ubuntu 9.10 (karmic) reached end-of-life on April 30, 2011.
See this
** Changed in: sane-backends (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/572246
Title:
Sane lib crashes with "buffer overflow detected"
To manage noti
** Changed in: sane-backends (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/575090
Title:
Simple Scan detect Mustek 1200 UB Plus as Mustek BearPaw 1200 CU
Basic support is available in Ubuntu 21.10 with sane-backends 1.0.32:
http://www.juergen-ernst.de/info_sane.html
If this version does not work, please change status.
** Changed in: sane-backends (Ubuntu)
Status: Triaged => Incomplete
--
You received this bug notification because you are
Thank you for reporting this bug to Ubuntu.
Ubuntu 9.10 (karmic) reached end-of-life on April 30, 2011.
See this document for currently supported Ubuntu releases:
https://wiki.ubuntu.com/Releases
We appreciate that this bug may be old and you might not be interested
in discussing it any more. Bu
This model is recognized by libsane1 in all supported versions of
Ubuntu.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/403340
Title:
Sane does not recognize Epson Corp. CX9400Fax out of the box
To
This model is recognized by libsane1 in all supported versions of
Ubuntu.
** Changed in: sane-backends (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/403340
Titl
Thank you for reporting this bug to Ubuntu.
Ubuntu 17.10 (artful) reached end-of-life on July 19, 2018.
See this document for currently supported Ubuntu releases:
https://wiki.ubuntu.com/Releases
We appreciate that this bug may be old and you might not be interested
in discussing it any more. Bu
Everyone posting 'installation failure' cases, please open separate
bugs. The underlying issue that *this* bug was referring to is fixed,
and the new failures are due to other problems, so please open different
bugs.
** Summary changed:
- Ubiquity crashes Kubuntu Jammy after selecting "install
** Changed in: p7zip (Ubuntu)
Status: Fix Released => Incomplete
** Tags removed: unmetdeps
--
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
** Changed in: lubuntu-meta (Ubuntu)
Status: Opinion => 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/1831220
Title:
Add hexchat by default on all ubuntu flavours
To manage notific
Like Studio, Lubuntu ships quassel. We have no intention on the Lubuntu
Team to ship hexchat instead at this time.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1831220
Title:
Add hexchat by defaul
** Changed in: lubuntu-meta (Ubuntu)
Status: New => Opinion
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1831220
Title:
Add hexchat by default on all ubuntu flavours
To manage notifications
archive admins dont think i386ing the RPM source is a good idea based on
my brief discussiom in #ubuntu-release
debugedit has splitsource in later versions, perhaps a split-source is
needed here. However I would suggest we defer to archive admins for
best approach here
--
You received this bug
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
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1965800
Title:
debhelper in focal-backports not usa
Root cause: https://bugs.launchpad.net/debian/+source/p7zip/+bug/1965855
--
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 buildin
Public bug reported:
The p7zip:i386 and p7zip-full:i386 packages are missing in focal.
The result is that debhelper in focal-backports cannot be used to build
i386 packages. It depends on debugedit:i386, which is missing, because
p7zip-full:i386 is a build dependency.
Please apply this patch to
[ubuntu/jammy-proposed] openssl 3.0.2-0ubuntu1 (Accepted)
Uploaded to proposed, it has to go through the usual process of passing
autopkgtests and such. It shouldn't need any additional package
rebuilds because of no ABI changes but expect autopkgtests to run hot a
while
** Changed in: openssl (
Public bug reported:
focal-backports contains debhelper 13.5.2ubuntu1~bpo20.04.1. This is an
architecture-independent package, but it depends on debugedit, which is
architecture-dependent.
The debugedit package exists in focal-universe for amd64, but not for
i386. As a result, Launchpad is not ab
I've got some extra cycles later today, so I'll happily help the
Security team out and get this uploaded later today (Eastern US time for
clarity sake when I say "later today")
** Changed in: openssl (Ubuntu)
Assignee: (unassigned) => Thomas Ward (teward)
** Chan
Then this should be trivial to backport, if you need it backported
waveform and you don't want to handle the actual backport uploads, I'll
take this on, I have some spare cycles today this afternoon.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribe
waveform: Paride: given this bug, wouldn't this be more suited for full
SRU and rebuilds? I'm wondering whether this is truly a backportable
case because this requires rebuild of all affected packages, and if
anyone builds with debhelper in backports (which is NOT available in
standard build envs
Whoops looks like we had some collission in terms of assignments.
Reassigning to waveform.
Once this is looked at and looks OK at the Canonical level, then the
Backports Team will take over backporting this. Keep in mind that since
the original Backports process is mostly scrapped, the Backports
Not a bug, you just have bad config.
From your logs:
> Mar 20 13:32:34 spark nginx[68287]: nginx: [emerg] a duplicate default
server for 0.0.0.0:80 in /etc/nginx/sites-enabled/embracehealth.io:209
So you need to figure out where else you've defined default_server and
remove it from the other one
Sorry I don't check this forum often.
I'm on 20.04.3. When I try to update + upgrade that package, apt tells
me I'm stuck with version 68
gnome-shell-extension-ubuntu-dock is already the newest version
(68ubuntu1~20.04.1).
--
You received this bug notification because you are a member of Ubuntu
Can you please submit this patch upstream as a merge request, unless
this is no longer a problem?
https://gitlab.com/sane-project/backends/-/merge_requests
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bug
There shouldn't be a problem here. The purpose of saned is to share
scanners that are physically attached to the local system, so that
remote systems can use them. If the scanner is already accessible over
the network, a remote system can connect to it without using saned.
See also /usr/share/doc/
1 - 100 of 3165 matches
Mail list logo
