This is a duplicate of LP: #1922130, marking it as such.
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to openssh in Ubuntu.
https://bugs.launchpad.net/bugs/2052618
Title:
Missing sftp-server argument -m force_file_perms
St
Hello and thanks for this bug report. The analysis looks sensible to me,
but I'm not really familiar with gss. To better understand the situation
I have a couple of questions:
- Does this mean that gss is unusable in Jammy at the moment? AFAICT
this is the only bug report about it, so I would be s
FWIW I agree with Nick's preference (clean at boot && clean files older
than 30d). Maybe we could make that 40d, as 30d is likely to be a time
interval at which a lot of periodic things happen (e.g. an off-site
backup). A retention period >30d is less likely be synchronized with it
in an unlucky wa
AIUI he suggests keeping the boot time cleanup, and that it could be
nice to have the 30d behavior back. In any case that's what I'd prefer.
I know we're speaking of file age; certainly not of blindly deleting
everything every month or so :-)
--
You received this bug notification because you are
Looks like the experiment worked: having
e /tmp 1777 root root 30d
deleted a test directory which has mtime and atime >30d old (done via:
touch -d '29 days ago', and then left to age over the weekend).
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packa
Thanks for the additional information. By reading the pages Sergio
linked to I found one user writing:
Downgrading openssh-server to version 8.0p1-19.el8_8 will
revert the update and SSH will work again, although this
probably not advisable.
That's definitely not advisable, but I think it's
** Changed in: klibc (Ubuntu)
Assignee: (unassigned) => Paride Legovini (paride)
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to klibc in Ubuntu.
https://bugs.launchpad.net/bugs/2054823
Title:
Sync klibc 2.0.1
klibc (2.0.13-4) unstable; urgency=medium
[ Sven Joachim ]
* debian/initramfs-tools/hooks/klibc-utils: Avoid the use of "cp -n"
(Closes: #1055694).
[ Salvatore Bonaccorso ]
* debian/control: Add myself to Uploaders
Date: 2024-02-21 22:32:43.744541+00:00
Signed-By: Parid
** Changed in: policykit-1 (Ubuntu)
Importance: Undecided => High
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to policykit-1 in Ubuntu.
https://bugs.launchpad.net/bugs/2054716
Title:
package polkitd 124-1 failed to inst
** Changed in: lvm2 (Ubuntu)
Status: New => In Progress
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to lvm2 in Ubuntu.
https://bugs.launchpad.net/bugs/2054683
Title:
Please merge lvm2 2.03.16-3 from Debian unstable.
I just sponsored lvm2 2.03.16-3ubuntu1 which should fix the FTBFS.
On including libdm-propagate-ioctl-errors-back-to-caller.patch: I am not
sure this bug is important enough to grant that. The patch may apply
cleanly to 2.03.16, but still it comes from 2.03.23, which is not a
trivial change in the
Uploaded and accepted:
==
OK: lvm2_2.03.16.orig.tar.xz
OK: lvm2_2.03.16-3ubuntu1.debian.tar.xz
OK: lvm2_2.03.16-3ubuntu1.dsc
-> Component: main Section: admin
** Changed in: lvm2 (Ubuntu)
Assignee: (unassigned) => Dave Jones (waveform)
--
You received this bug notification because
** Also affects: heimdal (Ubuntu Focal)
Importance: Undecided
Status: New
** Also affects: heimdal (Ubuntu Jammy)
Importance: Undecided
Status: New
** Changed in: heimdal (Ubuntu Focal)
Status: New => Fix Released
** Changed in: heimdal (Ubuntu Jammy)
Status: Ne
** Changed in: auto-package-testing
Assignee: (unassigned) => Paride Legovini (paride)
** Changed in: auto-package-testing
Status: New => Fix Released
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to apt in
I am not sure I fully understand the latest comment. Does it mean that
8.0p1-19.0.1 just works? What about 8.0p1-19.0.1.2, mentioned in [1]?
[1] https://linux.oracle.com/errata/ELSA-2024-12164.html
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, wh
With 0b4c5056925e7358374874c8bf4767290157e903 (in autopkgtest 5.33) lxc-
start-ephemeral is not called anymore.
** Changed in: autopkgtest (Ubuntu)
Assignee: (unassigned) => Paride Legovini (paride)
** Changed in: autopkgtest (Ubuntu)
Status: Triaged => Fix Committed
-
** Tags added: server-todo
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to openssh in Ubuntu.
https://bugs.launchpad.net/bugs/2060150
Title:
openssh sets PAM_RHOST to UNKNOWN causing slow logins
Status in openssh package i
I believe this is fixed in:
openssh (1:9.6p1-3ubuntu3) noble; urgency=medium
* Add sshd-socket-generator to generate ssh.socket drop-in configuration
[...]
>From README.Debian:
The provided ssh.socket unit file sets ListenStream=22. A systemd generator,
sshd-socket-generator, parses the ssh
Hello Nathan,
the diff LGTM, I just have two questions:
1. The bug description has a "test case", but that's more of a
reproducer than of a test case, right? The "expected result" is not
explicitly stated. In particular, looking at this step:
- After Authentication, nothing happens.
what shoul
** Changed in: software-properties (Ubuntu)
Assignee: (unassigned) => Nathan Teodosio (nteodosio)
** Changed in: software-properties (Ubuntu)
Status: Triaged => In Progress
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscr
Uploading to ubuntu (via ftp to upload.ubuntu.com):
Uploading software-properties_0.99.47.dsc: done.
Uploading software-properties_0.99.47.tar.xz: done.
Uploading software-properties_0.99.47_source.buildinfo: done.
Uploading software-properties_0.99.47_source.changes: done.
Successful
This also affects src:adduser, which has this delta:
+if ($action eq "adduser") {
+# Mute the command
+system('sh' => ( '-c' => '"$@" >/dev/null 2>&1', '--',
'/usr/sbin/zsysctl', 'userdata', 'create', $new_name, $home_dir,));
+}
causing it to fail in minim
aptly is Fix Release in Kinetic in:
aptly (1.4.0+ds1-7) unstable; urgency=medium
* Team upload.
* Add support for zstd compression (Closes: #1010465)
** Changed in: aptly (Ubuntu)
Status: New => Fix Released
--
You received this bug notification because you are a member of Ubuntu
T
Hello James and thanks for your bug report. The "Make
ClientAliveCountMax=0 have sensible semantics" change you refer to is
actually an upstream change, see the OpenSSH bugfixes here:
https://www.openssh.com/releasenotes.html
the upstream bug being:
https://bugzilla.mindrot.org/show_bug.cgi?
Confirmed still happening on the Jammy 20220719 daily.
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to ubuntu-meta in Ubuntu.
https://bugs.launchpad.net/bugs/1974483
Title:
autoinstall ssh:install-server:false is misleading
I see your point, and I find the one about "fixing it the Kinetic way"
especially convincing, it may save us headaches in the future, and may
help with backports. My concern is that other packages or scripts users
wrote and tested on Jammy systems refer to the "wrong" path
(/usr/lib/x86_64-linux-gn
Fixed upstream and in >= Focal by:
https://github.com/curl/curl/commit/b7f90470be9b75f57167abbcd63aadb2e3b33958
** Description changed:
+ [Partial copypaste from the linked upstream bug.]
+
Setting
- NO_PROXY=localhost,127.0.0.1,::1
+ NO_PROXY=localhost,127.0.0.1,::1
enables conne
Public bug reported:
[Partial copypaste from the linked upstream bug.]
Setting
NO_PROXY=localhost,127.0.0.1,::1
enables connections to http://localhost and http://127.0.0.1 and does
not work for http://[::1] at all. Apparently the problem is caused by an
assumption [1] that a hostname cannot
Looks like there' also an openSUSE bug about this issue:
https://bugzilla.opensuse.org/show_bug.cgi?id=1175854
As I understand it the culprit is the old rsync (3.1.3). Upstream
suggests recompiling it with -with-included-zlib=yes, which I doubt
we're going to do, especially in stable releases. Th
ppa-purge 0.2.8+bzr63-0ubuntu2 is currently in mantic-proposed,
sponsored by halves. Unsubscribing ubuntu-sponsors.
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to software-properties in
Ubuntu.
https://bugs.launchpad.net/bugs
Hopefully worked around in autopkgtest by:
https://salsa.debian.org/ci-
team/autopkgtest/-/commit/2344e8197ed29ed1d94c33270207252574bb743c
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to adduser in Ubuntu.
https://bugs.launch
I reproduced this issue by:
1. Starting a Jammy LXD container
2. Stop+disable systemd-resolved, install dnsmasq
3. Verify that dnsmasq is healthy
4. Upgraded to Noble
5. systemd-resolved is running again, dnsmasq is broken
I started looking into this bug because it has a dnsmasq task (so it's
par
That's consistent with the comments above as the USB->SSD transfer
doesn't use the rsync protocol.
What we need to move this forward is a verification that applying [1] to
the version of rsync in Bionic (3.1.2) or Focal (3.1.3) fixes the issue.
If any of you affected users is available for testin
Hello Vijay and thanks for this bug report. The ca-certificates package
is periodically upgraded in stable releases. The package changelog [1]
will tell you which CAs are added/removed with the past updates.
If you still believe you spotted an issue with missing certificate
please specify:
1. Whi
Hello Atharva and thanks for this bug report.
Since there isn't enough information in your report to differentiate
between a problem specific to your system and a bug in Ubuntu, I'm
marking this bug as Incomplete.
If you believe that this is really a bug, please provide some extra
context on what
Thanks. According to the package versions the bug is not present in >=
Kinetic, so setting the devel release task as Fix Released.
** Changed in: rsync (Ubuntu)
Status: New => Fix Released
** Changed in: rsync (Ubuntu Jammy)
Status: Incomplete => Triaged
** Tags added: server-todo
** Bug watch added: github.com/WayneD/rsync/issues #375
https://github.com/WayneD/rsync/issues/375
** Also affects: rsync via
https://github.com/WayneD/rsync/issues/375
Importance: Unknown
Status: Unknown
--
You received this bug notification because you are a member of Ubuntu
To
Hello, I didn't go into the specifics of the bug, but according to LP:
#2007837 the security team (Cc: mdeslaur) is going to release rsync
3.2.7 to jammy and kinetic as a security update, so this bug should get
fixed too.
--
You received this bug notification because you are a member of Ubuntu
To
Hello, while [1] by itself is a straightforward patch, I don't think we
can acknowledge this to be a bug in in Ubuntu, given that you are trying
to use an Ubuntu packaged software using a manually compiled version of
a library it depends on. This is not a supported use case, so the
prerequisites fo
** Changed in: openssh (Ubuntu)
Status: Incomplete => Invalid
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to openssh in Ubuntu.
https://bugs.launchpad.net/bugs/2038561
Title:
Requesting Ubuntu package manager to rel
Thanks for digging into this issue and updating the relevant Debian bug,
refreshing the debdiff. This LGTM, tested locally, the manpage renders
fine. I am going to sponsor this.
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to
Actually, it would be nice if the new patch had some dep-3 headers (see
[1], `quilt --dep3` and maybe dep3changelog). In particular I think we
miss bug references an a description of the patch. Do you think you
could add the relevant ones? Thanks!
[1] https://dep-team.pages.debian.net/deps/dep3/
Hello Valentijn and thanks for this bug report, it really helped me
figure out an otherwise obscure printing issue.
However I don't agree with the suggested solution: the security model of
cups for ipps is TOFU (trust on first use): the certificate is accepted
the first time and then expected to b
Hello Valentijn and thanks for this bug report, it really helped me
figure out an otherwise obscure printing issue.
However I don't agree with the suggested solution: the security model of
cups for ipps is TOFU (trust on first use): the certificate is accepted
the first time and then expected to b
** Changed in: pld-linux
Status: New => Incomplete
** Changed in: irqbalance (Ubuntu)
Status: New => Invalid
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to upstart in Ubuntu.
https://bugs.launchpad.net/bugs/406
Hi, adding a couple of extra pointers here (I'm the Debian irqbalance
maintainer). This the Debian bug where the discussion on removing
irqbalance from the kernel Recommends happened:
https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=926967
In Debian irqbalance is not installed anymore by default
Hi and thanks for working at this SRU. I have some comments on the
debdiff:
- Please specify the patch Author in the DEP-3 headers. See [1] for more
info on the header format.
- The patch description should not be "apply upstream patch", because
the patch is just the patch, it contains no informa
Hello Bill and thanks for this bug report. I can see the issue you
described here (thanks for the reproducer), however I believe it should
be filed/fixed upstream. Maybe [1] should be expanded to cover --remove-
source-files, as the two issues could be related.
Diverging from upstream (or from Deb
** Changed in: cloud-init (Ubuntu)
Status: New => Incomplete
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to systemd in Ubuntu.
https://bugs.launchpad.net/bugs/1919177
Title:
Azure: issues with accelerated networking
Hi, I went a bit down the rabbit hole Sergio mentioned and found the
same old reports and nothing really useful. I'd also be curios to see if
the problem still occurs with the newer releases.
Did you see this happen on more that one machine/deployment?
The backtrace didn't suggest my anything, bu
Hello Dominik and thanks for this bug report. An umbrella bug report
doesn't really help here, especially given that there's no single "reset
config files on updates" policy in Ubuntu. Actually it's quite the
contrary: as a Debian derivative Ubuntu basically inherits [1] and in
particular [2].
Ple
** Changed in: nss (Ubuntu)
Assignee: (unassigned) => Paride Legovini (paride)
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to nss in Ubuntu.
https://bugs.launchpad.net/bugs/1931104
Title:
Test of dogtag-pki
Hello Barto,
If I understand it correctly you can create working images using 20.04
ISOs *right now*, but with the exact same tooling images created with
20.04.x ISOs do not work. I think you have been clear about this, but it
is of course very important to know that the only moving part is the IS
** Changed in: openssh (Ubuntu)
Status: New => Incomplete
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to openssh in Ubuntu.
https://bugs.launchpad.net/bugs/1964642
Title:
Packer virtualbox ssh can't connect to unatt
Hello Ian and thanks for this bug report. My question here is: is this
actually a bug?
The manpage for --update says:
This forces rsync to skip any files which exist on the destination
and have a modified time that is newer
It seems sensible to me to make this a '>=' comparison, and not a st
I see your point; my suggestion here is to file a bug upstream with your
findings:
https://github.com/WayneD/rsync/issues
I don't think this should be tackled on the Ubuntu side, especially
given that the issue is really minor and unlikely to affect a
significant amount of users. As you say wha
Still no activity in the upstream issue, however I think OpenSSH 8.9
offers a mechanism that can help avoiding hitting MaxAuthTries in some
cases: "destination constraints", see documentation for -h in ssh-
add(1). AIUI constraining should limit the number of keys tried against
a given host, making
Hello Alexander, note that Xorg is available in Jammy both as the native
graphical session and via xwayland. On this bug report: could you please
elaborate more on what exactly happens? In particular could you guide us
into reproducing the problem on a clean Jammy install, making clear
"what should
Hello testpi and thanks for this bug report. Can you reproduce this
issue from a fresh install on the Raspberry, and attempting a simple ssh
login instead of a git clone? Something on these lines:
-
ssh-keygen
cp ~/.ssh/id_rsa.pub ~/.ssh/authorized_keys
killall ssh-agent || true
eval $(ssh-age
Also: you mention that "ssh agent crashes". What do you see exactly to
be able to tell it's a crash and not some other authentication or key
handling issue?
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to openssh in Ubuntu.
ht
** Changed in: openssh (Ubuntu)
Status: New => Incomplete
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to openssh in Ubuntu.
https://bugs.launchpad.net/bugs/1968876
Title:
ssh-agent: Error connecting to agent: Connec
I tried reproducing the issue on a Rpi4, cloning a repository via ssh
using pubkey authentication with a rsa2048 key stored in ssh-agent, it
worked fine. If you believe there's actually a bug here please provide
some steps we can follow to reproduce the issue from a clean Jammy
system, and we'll lo
ring in it.
** Affects: base-files (Ubuntu)
Importance: Undecided
Assignee: Paride Legovini (paride)
Status: Triaged
** Changed in: base-files (Ubuntu)
Assignee: (unassigned) => Paride Legovini (paride)
** Changed in: base-files (Ubuntu)
Status: New => Triaged
Hello Lars and thanks for this bug report. I can confirm this: libmnl-
dev 1.0.4-2 installs
/usr/lib/x86_64-linux-gnu/libmnl.a
while libmnl-dev 1.0.4-3 does not. I tracked this down to this Debian
packaging change (see the debian/libmnl-dev.install diff):
https://salsa.debian.org/pkg-netfilter
Hello Alvaro and thanks for this bug report. We have many systems
running Jammy and they're able to connect to GitHub with no issues. I
also tried with GitLab.com and it works just fine. This is not to
dismiss your report, but there's clearly something else involved in the
problem you're hitting. M
Hello Thomas. You filed this bug against:
DistroRelease: Ubuntu 21.10
Package: openssh-server 1:8.4p1-6ubuntu2.1
By "Solved by a later version of systemd and sshd". Do you mean that you
found you can't reproduce the issue on Jammy (22.04 LTS)? Can you still
reproruce the issue on Impish? Than
Hello and thanks for this bug report. I tried to reproduce this locally
but I failed. We're certainly willing to investigate this, but first we
need some steps to reproduce the problem. Could you please try to
identify a somehow reliable way to reproduce the issue and share your
findings? Thanks!
I found a (somehow stale) upstream PR that addresses this:
https://github.com/openssh/openssh-portable/pull/250
We could include this as an Ubuntu patch, but it would be better to
first see it merged upstream. It may be worth pinging there.
** Changed in: openssh (Ubuntu)
Status: New =>
** Tags added: server-todo
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to openssh in Ubuntu.
https://bugs.launchpad.net/bugs/1966886
Title:
ssh-copy-id and Dropbear Server
Status in openssh package in Ubuntu:
Triaged
B
Well, "large" can span orders of magnitude, depending who you ask. :-)
Can you please try to identify some steps to reproduce that include the
big file generation? For example:
# 100MB file, random data (difficult to compress)
head -c 100M /dev/urandom > foo
# 100MB file, all 0s (easy to c
The upstream commit [1] included as a patch in strongswan
(5.9.4-1ubuntu2) should be released in strongswan 5.9.5 [2].
[1]
https://github.com/strongswan/strongswan/commit/b158c08c4b919b878ded10bb57e969ed7b3cabc3
[2] https://github.com/strongswan/strongswan/milestone/3?closed=1
--
You received t
Hi Nino, I found a RedHat bug [1] that describes a similar situation
(affected is dhclient on ppc64le, but the error is the same).
The suggested workaround is setting
net.core.bpf_jit_limit = 262144000
via sysctl. I checked and on amd64 I find
net.core.bpf_jit_limit = 264241152
while on an
If you want to change the value without rebooting that's:
sudo sysctl net.core.bpf_jit_limit=264241152
Add it to /etc/sysctl.conf if you want to set it automatically at boot,
but it's more meaningful to test as you said: wait for the issue to
happen and then change the value while the system is
Hello and thanks for your bug report. While you hit this issue while
upgrading clamav-freshclam, those hashfiles are owned by ucf(1), so I'm
reassigning the bug to the ucf package.
There isn't really enough information here for a developer to confirm
this issue is a bug, or to begin working on it,
Hi, glad to know it worked. There is some heuristics behind the default
bpf_jit_limit [1], it isn't a simple hardcoded value. We may discuss
bumping the default in Ubuntu, but I don't think that's a good idea: the
in-kernel heuristics has certainly been well thought, and just bumping
the number is
That PR is still pending review, no movements there unfortunately.
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to openssh in Ubuntu.
https://bugs.launchpad.net/bugs/1938144
Title:
monitor_read: unpermitted request 48 on se
Hello Thomas and thanks for your bug report. I have no problems adding
ed25519 keys to ssh-agent on a Jammy system. Could you please try the
following steps, which may help identifying where the problem is?
Thanks!
$ mkdir /tmp/ed25519test
$ cd /tmp/ed25519test
$ echo $SSH_AUTH_SOCK
/run/user/100
I can reproduce this:
$ shopt -s failglob
$ ssh bash: no match: /etc/ssh/ssh_config.d/*.conf
but I believe the bugs belongs to the bash-completion package.
** Changed in: openssh (Ubuntu)
Importance: Undecided => Low
** Changed in: openssh (Ubuntu)
Status: New => Confirmed
** Package
I reviewed this issue again and I don't think we're ready to drop the
"Disable LTO on s390x" delta for now. There are newer NSS upstream
versions worth testing but in Ubuntu we're still at 3.68 for now.
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages
** Changed in: dnsmasq (Ubuntu)
Assignee: Paride Legovini (paride) => (unassigned)
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to dnsmasq in Ubuntu.
https://bugs.launchpad.net/bugs/1778073
Title:
dnsmasq
** Changed in: dnsmasq (Ubuntu)
Assignee: (unassigned) => Paride Legovini (paride)
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to dnsmasq in Ubuntu.
https://bugs.launchpad.net/bugs/1778073
Title:
dnsmasq
Hi, I had another look at this one and Ciaby's analysis looks correct to
me, however I want to setup a full reproducer before attempting a fix. I
assigned the bug to myself.
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to dnsm
** Also affects: openssh (Ubuntu Hirsute)
Importance: Undecided
Status: New
** Also affects: openssh (Ubuntu Focal)
Importance: Undecided
Status: New
** Changed in: openssh (Ubuntu Focal)
Status: New => Triaged
** Changed in: openssh (Ubuntu Hirsute)
Status: New
ntu Bionic)
Assignee: (unassigned) => Paride Legovini (paride)
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to systemd in Ubuntu.
https://bugs.launchpad.net/bugs/1785383
Title:
missing EDNS0 record confuses systemd-resolv
Reminds me of LP: #1943049. I mentioned this bug there, as we should
make sure that close_range doesn't bring us back to that same issue.
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to libseccomp in Ubuntu.
https://bugs.launc
** Changed in: dnsmasq (Ubuntu Bionic)
Status: Triaged => In Progress
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to systemd in Ubuntu.
https://bugs.launchpad.net/bugs/1785383
Title:
missing EDNS0 record confuses sy
I dropped the verification-* as there were about the systemd SRU, while
I'm preparing the dnsmasq one at the moment.
** Description changed:
[Impact]
- dnsmasq 2.79 and below omits EDNS0 OPT records when returning an empty answer
for a domain it is authoritative for. systemd-resolved seems to
MP to fix this bug in Bionic, already reviewed and uploaded:
https://code.launchpad.net/~paride/ubuntu/+source/dnsmasq/+git/dnsmasq/+merge/409149
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to systemd in Ubuntu.
https://bugs
** Bug watch added: OpenSSH Portable Bugzilla #1844
https://bugzilla.mindrot.org/show_bug.cgi?id=1844
** Also affects: openssh via
https://bugzilla.mindrot.org/show_bug.cgi?id=1844
Importance: Unknown
Status: Unknown
--
You received this bug notification because you are a member
Thanks for this bug report; I can reproduce the issue and will prepare
an upload with your debdiff.
** Changed in: heimdal (Ubuntu)
Assignee: (unassigned) => Paride Legovini (paride)
** Tags added: server-next
--
You received this bug notification because you are a member of Ubuntu
To
Trusty is now in Extended Security Maintenance [1], and this bug doesn't
qualify for it, so it won't be fixed in that release.
[1] https://wiki.ubuntu.com/Releases
** Changed in: ntp (Ubuntu Trusty)
Status: New => Won't Fix
--
You received this bug notification because you are a member o
I share Christian's concern on nobody actually caring about this. Given
the absence of activity in >1 year I'm marking this bug as Incomplete,
which is an invite for anybody interested to chime in.
In absence of feedback I doubt there will be any progress here, as the
direction to take isn't fully
The MP got reviewed and the dnsmasq upload is currently waiting in the
Bionic unapproved queue.
Being a format 1.0 package the diff [1] looks huge at first glance, but
the real changes are actually very limited (those in the MP).
[1]
https://launchpadlibrarian.net/560828569/dnsmasq_2.79-1ubuntu0.
Hi,
I had a look at [1] and AIUI this wasn't recognized as an upstream bug.
I also can't find a relevant Debian bug about this issue. The bug
description says it affected Xenial, which is now in Extended Security
Maintenance, so it's a Won't Fix there.
For >= Bionic we need confirmation from an a
Xenial is now in Extended Security Maintenance and this bug doesn't
qualify for it, so the bugfix won't be SRUed there.
** Changed in: openssh (Ubuntu Xenial)
Status: Triaged => Won't Fix
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which
Xenial is now in Extended Security Maintenance and this bug doesn't
qualify for it, so this bug won't be fixed in that release.
** Changed in: openssh (Ubuntu Xenial)
Status: Triaged => Won't Fix
--
You received this bug notification because you are a member of Ubuntu
Touch seeded package
Yakkety reached EOL, while Xenial is now in Extended Security
Maintenance, and this bug doesn't qualify for it, so this bug won't be
fixed in those releases.
** Changed in: openssh (Ubuntu Xenial)
Status: Triaged => Won't Fix
** Changed in: openssh (Ubuntu Yakkety)
Status: Triaged =
Hello Nahuel,
According to your reasoning I assume the "root" issue should still
affect the versions of rsync shipped with the newer Ubuntu releases.
I agree it would be nice for the behavior you describe to be documented,
but I don't think it's worth patching the Ubuntu package for it. I
recogni
** Also affects: rsync via
https://github.com/WayneD/rsync/issues/236
Importance: Unknown
Status: Unknown
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to rsync in Ubuntu.
https://bugs.launchpad.net/bugs/1659950
T
Thanks Nahuel! We're doing some retriage and cleanup of old bugs, and I
stumbled on this one :-)
I linked your upstream bug report to this bug, Launchpad will keep its
status in sync. You may have noticed that I didn't set the status of
this bug to Wontfix but to Opinion ("Doesn't fit with the pro
1 - 100 of 222 matches
Mail list logo
