Marking Fix Released as 7.74.0-1.3ubuntu1 can now be found in impish.
** Changed in: curl (Ubuntu)
Status: Confirmed => 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/1939750
** Tags added: update-excuse
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1942375
Title:
test failure with some network configurations
To manage notifications about this bug go to:
** Patch added: "vip-manager-1_1.0.1-4_1.0.1-4ubuntu1.debdiff"
https://bugs.launchpad.net/debian/+source/vip-manager/+bug/1942375/+attachment/5522885/+files/vip-manager-1_1.0.1-4_1.0.1-4ubuntu1.debdiff
** Changed in: vip-manager (Ubuntu)
Assignee: Dan Bungert (dbungert) =>
** Bug watch added: Debian Bug tracker #993620
https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=993620
** Also affects: vip-manager (Debian) via
https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=993620
Importance: Unknown
Status: Unknown
--
You received this bug notification
** Changed in: vip-manager (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/1942375
Title:
test failure with some network configurations
To manage
** Summary changed:
- autopkgtest failure on armhf
+ test failure with some network configurations
** Description changed:
- vip-manager currently will consistently fail in autopkgtest on armhf.
- This does not appear to be related to glibc2.34, as we do have one example of
a passing test
** Changed in: vip-manager (Ubuntu)
Assignee: (unassigned) => Dan Bungert (dbungert)
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1942375
Title:
autopkgtest failure on armhf
To man
https://sourceware.org/pipermail/libc-alpha/2021-June/127273.html
stuff from nss_files was moved into glibc proper.
for libnss-db, we addressed this by no longer explicitly linking against
-lnss_files.
LP: #1939918
--
You received this bug notification because you are a member of Ubuntu
Bugs,
Public bug reported:
vip-manager currently will consistently fail in autopkgtest on armhf.
This does not appear to be related to glibc2.34, as we do have one example of a
passing test there.
Also, locally this test consistently passes for me.
Example failure:
> How about:
> * New upstream version 3.7 to fix FTBFS (LP: #1940999)
Yes, I like that better.
OK, I have updated my proposal. I recommend that we address this FTBFS by
using grep 3.7 with built-in regex. This is a change from current and will
increase binary size. (180k -> 260k when
** Attachment added: "grep_3.7-0ubuntu1.dsc"
https://bugs.launchpad.net/ubuntu/+source/grep/+bug/1940999/+attachment/5521729/+files/grep_3.7-0ubuntu1.dsc
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
** Attachment added: "grep_3.7-0ubuntu1.debian.tar.xz"
https://bugs.launchpad.net/ubuntu/+source/grep/+bug/1940999/+attachment/5521728/+files/grep_3.7-0ubuntu1.debian.tar.xz
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
Add upstream NEWS file diff.
One change that upstream felt relevant enough to point out, outside of bug
fixes, was a change to a Windows only option.
** Attachment removed: "grep_3.7-0ubuntu1.debian.tar.xz"
** Description changed:
While tracing the build failure of rust-curl-sys on armhf, I observed
- that both that both rust-curl-sys and rust-openssl-sys will FTBFS with
- gcc-11. gcc-10 seems fine.
+ that both rust-curl-sys and rust-openssl-sys will FTBFS with gcc-11.
+ gcc-10 seems fine.
Public bug reported:
While tracing the build failure of rust-curl-sys on armhf, I observed
that both that both rust-curl-sys and rust-openssl-sys will FTBFS with
gcc-11. gcc-10 seems fine.
https://autopkgtest.ubuntu.com/results/autopkgtest-
** Description changed:
- Currently, this package will FTBFS on ppc64 when building with go 1.16.
+ Currently, this package will FTBFS on ppc64el when building with go 1.16.
This looks as follows:
go build fmt: /usr/lib/go-1.16/pkg/tool/linux_ppc64le/compile: signal:
segmentation fault (core
Public bug reported:
Currently, this package will FTBFS on ppc64 when building with go 1.16.
This looks as follows:
go build fmt: /usr/lib/go-1.16/pkg/tool/linux_ppc64le/compile: signal:
segmentation fault (core dumped)
Sample log: https://autopkgtest.ubuntu.com/results/autopkgtest-
One possibility that's starting to grow on me is adjusting grep to go
back to using the built-in regex instead of getting it from glibc. This
causes some size bloat (+80k on amd64) but that might be tolerable.
Proof of concept:
https://launchpad.net/~dbungert/+archive/ubuntu/grep-lp-1940999
--
On Wed, Aug 25, 2021 at 12:00:44PM -, Robie Basak wrote:
> Thank you for working on this!
And thank you for the thoughtful review.
> > To address this I propose picking up the new version of grep.
> But you're picking up the new version of grep and then also disabling
> the failing test in
** Changed in: grep (Ubuntu)
Status: New => Confirmed
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1940999
Title:
FTBFS against glibc 2.34
To manage notifications about this bug go to:
To address this I propose picking up the new version of grep.
** Attachment added: "grep_3.7-0ubuntu1.debian.tar.xz"
https://bugs.launchpad.net/ubuntu/+source/grep/+bug/1940999/+attachment/5520320/+files/grep_3.7-0ubuntu1.debian.tar.xz
--
You received this bug notification because you are a
** Patch added: "upstream-ChangeLog.diff"
https://bugs.launchpad.net/ubuntu/+source/grep/+bug/1940999/+attachment/5520323/+files/upstream-ChangeLog.diff
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
This summary file is the differences to the debian directories between
3.6-1 and 3.7
** Attachment added: "changes.summary"
https://bugs.launchpad.net/ubuntu/+source/grep/+bug/1940999/+attachment/5520322/+files/changes.summary
--
You received this bug notification because you are a member
** Attachment added: "grep_3.7-0ubuntu1.dsc"
https://bugs.launchpad.net/ubuntu/+source/grep/+bug/1940999/+attachment/5520321/+files/grep_3.7-0ubuntu1.dsc
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
Public bug reported:
The package grep failed to build in a recent archive rebuild, see
https://people.canonical.com/~doko/ftbfs-report/test-
rebuild-20210805-impish-impish.html#foundations-bugs .
The failure is in automated test, as follows:
stack-overflow: failed test: grep never printed
Public bug reported:
'test-regex' fails when building grep against glibc 2.34.
Per commentary from grep upstream at
https://debbugs.gnu.org/cgi/bugreport.cgi?bug=50069,
the test failure can be attributed to skew between the glibc built-in regex and
the one that is found in the grep source
Thank you Brian.
I will follow up with the close upon migration.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1939750
Title:
Please merge 7.74.0-1.3
To manage notifications about this bug go to:
** Tags removed: patch
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1939918
Title:
FTBFS against glibc 2.34
To manage notifications about this bug go to:
I am not seeking a sponsor at this time.
Attached patch is suitable to get package working again.
HOWEVER, this patched version of libnss-db must be used with
glibc 2.34, as if you do so with glibc 2.33 you see errors
at build time:
dpkg-shlibdeps: warning: symbol _nss_files_parse_protoent used
Public bug reported:
The package libnss-db failed to build in a recent archive rebuild, see
https://people.canonical.com/~doko/ftbfs-report/test-
rebuild-20210805-impish-impish.html#foundations-bugs .
** Affects: libnss-db (Ubuntu)
Importance: Undecided
Status: New
** Tags:
Public bug reported:
Debian version 7.74.0-1.3 cherry-picks a fix for a command line API
breakage that would be unexpected in a minor version release.
Please help merge.
https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=989064
https://github.com/curl/curl/issues/6321
** Affects: curl (Ubuntu)
** Tags added: update-excuse
** Description changed:
+ Also documented upstream:
+ https://github.com/go-delve/delve/issues/2630
+
In version 1.6.1 of the delve golang debugger, a 'dump' feature was added.
https://github.com/go-delve/delve/pull/2173
Since that time, arm64 autopkgtest
Public bug reported:
In version 1.6.1 of the delve golang debugger, a 'dump' feature was added.
https://github.com/go-delve/delve/pull/2173
Since that time, arm64 autopkgtest of delve has been failing like so:
** Tags added: update-excuse
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1938325
Title:
adt failure: '/cdrom not ext4 with todisk'
To manage notifications about this bug go to:
Public bug reported:
Autopkgtest will sometimes fail in the todisk test with the following error at
the end:
++ echo '/cdrom not ext4 with todisk'
Earlier in the log file, you can also see this log message from casper:
Begin: Copying live_media to /dev/disk/by-label/scratch ... Warning:
As Michael mentions, it's not clear to me that this was reverted in
upstream python. I did a test against python 3.10.0b4 and 3.9.6 and was
able to see the same problem in both.
The above line from Chris is a very efficient test case.
./brz -Derror selftest -v -Oselftest.timeout=6000
** Also affects: casper (Ubuntu)
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/1937319
Title:
namespace collision on url kernel arg results in
** Merge proposal linked:
https://code.launchpad.net/~dbungert/update-notifier/+git/update-notifier/+merge/405628
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1821412
Title:
"System program
** Changed in: update-notifier (Ubuntu)
Assignee: (unassigned) => Dan Bungert (dbungert)
** Changed in: update-notifier (Ubuntu)
Status: Triaged => In Progress
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
Local runtime in qemu with the proposed version for hirsute is 27
minutes, versus 4 hours previously. Nice!
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1927757
Title:
sshuttle autopkgtest is
I have completed verification per test steps on the same machine I
describe at https://bugs.launchpad.net/ubuntu/+source/ubuntu-release-
upgrader/+bug/1929449/comments/8
As expected, the machine is refused if I 'do-release-upgrade', and does
proceed with the upgrade based on invocation of
Reopening per feedback from Wolfgang (submitter).
Edit: I attempted to reopen this but cannot, all states are greyed out.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1653217
Title:
stop job
Marking invalid on Subiquity as I believe that no change is required
there. We can of course reverse that position if we find that Subiquity
changes are indeed desired.
** Changed in: subiquity
Status: In Progress => Invalid
--
You received this bug notification because you are a member
** Merge proposal linked:
https://code.launchpad.net/~dbungert/livecd-rootfs/+git/livecd-rootfs/+merge/404869
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1933523
Title:
Temporary installer
Hi @Frank,
So I looked into this a bit, and with some feedback help from mwhudson,
I see that we attempt to print the ssh info. Presumably this isn't
going in the place you're looking, however.
Something that changed relatively recently was that we no longer have
cloud-init handle setting the
** Changed in: subiquity
Assignee: (unassigned) => Dan Bungert (dbungert)
** Changed in: subiquity
Status: New => In Progress
** Changed in: livecd-rootfs (Ubuntu)
Status: Confirmed => In Progress
--
You received this bug notification because you are a member of Ub
** Tags added: fr-1477
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1933523
Title:
Temporary installer password and key fingerprints are not printed with
latest impish daily ISOs
To manage
** Changed in: subiquity (Ubuntu)
Assignee: (unassigned) => Dan Bungert (dbungert)
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1932564
Title:
FilesystemController has no _start_t
Public bug reported:
the following was observed with the ubuntu-desktop-installer client:
2021-06-18 08:01:35,477 DEBUG root:39 start: subiquity/Filesystem/guided_GET:
2021-06-18 08:01:35,479 DEBUG root:39 finish: subiquity/Filesystem/guided_GET:
SUCCESS: 500 Traceback (most recent call last):
I attempted to verify.
Verification summary - inconclusive
Steps performed
1. Create container - lxc launch images:ubuntu/hirsute
2. do steps 1 & 2 in https://wiki.ubuntu.com/QATeam/PerformingSRUVerification
$ dpkg -l apt
[...]
ii apt2.2.3amd64commandline package
This appears to also be affecting the systemd packages on hirsute at the
moment.
The following packages have unmet dependencies:
libsystemd-dev : Depends: libsystemd0 (= 247.3-3ubuntu3.1) but 247.3-3ubuntu3
is to be installed
Attempting to force an install at version ubuntu3.1 offers to remove
$ cat DistUpgradeVersion.py
VERSION = '21.04.13'
Test repeated using this version of the hirsute.tar.gz, and as expected
both the TUI and Gtk3 versions provide the error that upgrades are not
possible at this time.
--
You received this bug notification because you are a member of Ubuntu
Bugs,
Disregard, I tested 21.04.12, and I will retest 21.04.13 when available.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1931112
Title:
Apple vendor quirk check for LP#1928434 incorrectly fails on
The original quirk from LP: #1929449 continues to decline upgrade for
Apple hardware, as expected.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1931112
Title:
Apple vendor quirk check for
Public bug reported:
Due to what I believe to be a bug in dh-golang, golang-yaml.v2 will fail
autopkgtest when attempting to copy some source code into a directory
that has symlinks to the same source code.
I have submitted this to Debian as:
Public bug reported:
Running tests with golang 1.16 results in the following test failure:
=== RUN TestExecute/hello_{{
template_test.go:57: expected err "template: :1: unexpected unclosed action
in command"; got "template: :1: unclosed action"
--- FAIL: TestExecute (0.00s)
I have
Public bug reported:
golang-github-prometheus-common package currently FTBFS due to
TestTLSConfig
=== RUN TestTLSConfig
http_config_test.go:519: Unexpected TLS Config result:
[...]
RootCAs:0xc00011d470
[...]
expected
Public bug reported:
prometheus currently FTBFS due to a failure in
TestHeadReadWriter_WriteChunk_Chunk_IterateChunks
--- FAIL: TestHeadReadWriter_WriteChunk_Chunk_IterateChunks (0.23s)
panic: runtime error: slice bounds out of range [:104326] with capacity 104293
[recovered]
panic:
I performed successful SRU verification of this item using a Mid-2009 Macbook
Pro.
The Groovy desktop installer didn't boot on this hardware, so I went back to
Bionic (Focal was
probably a better choice)
After enough do-release-upgrades to Groovy, I was able to follow the
test cases as
Sorry about the spam.
The intro text needed update to match the upstream naming of liberachat for the
network.
** Patch added: "irssi-4_1.2.3-1_1.2.3-1ubuntu1.debdiff"
v3 changes my patch for liberachat to prefer the upstream commit instead
of what I put together.
** Patch added: "irssi-3_1.2.3-1_1.2.3-1ubuntu1.debdiff"
https://bugs.launchpad.net/ubuntu/+source/irssi/+bug/1928815/+attachment/5500245/+files/irssi-3_1.2.3-1_1.2.3-1ubuntu1.debdiff
--
You
** Summary changed:
- Please merge with 1.2.3-1
+ Please merge with 1.2.3-1 - Libera chat, upstream update
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1928815
Title:
Please merge with 1.2.3-1 -
Same for 3.192.40.2 in hirsute-proposed.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1926298
Title:
Segfault added in the recent changes
To manage notifications about this bug go to:
Also 3.192.42, which has the impish version of this fix, is not showing crashes
for this problem:
https://errors.ubuntu.com/problem/74e558a18105a756eb6a4b6aaa7145b79471754a
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
Here's a second version, adding Libera to the config and updating the
user support suggestion to point to #ubuntu on there.
** Patch added: "irssi-2-1.2.3-1-1.2.3-1ubuntu1.debdiff"
Self-verified as follows:
* use virtual machine manager to create a KVM with
/srv/iso/hirsute/ubuntu-21.04-desktop-amd64.iso, 4 cpu/8G mem
*
Public bug reported:
subiquity/server/server.py will only assign to cloud if 'status:done'
later, if we're not in dry run, set_installer_password will attempt to use
self.cloud.
traceback
2021-05-20 14:39:07,854 INFO subiquity:101 Starting Subiquity server revision
unknown
2021-05-20
** Patch added: "irssi-1-1.2.3-1ubuntu1.debdiff"
https://bugs.launchpad.net/ubuntu/+source/irssi/+bug/1928815/+attachment/5498533/+files/irssi-1-1.2.3-1ubuntu1.debdiff
** Tags added: patch
** Changed in: irssi (Ubuntu)
Status: New => Confirmed
--
You received this bug notification
Removing patch tag to hopefully get this out of the sponsor queue.
** Tags removed: patch
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1923110
Title:
autopkgtests may fail on slow machines
To
Public bug reported:
We should merge with Debian version 1.2.3-1
** Affects: irssi (Ubuntu)
Importance: Undecided
Status: New
** Tags: fr-1384
** Tags added: fr-1384
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
This may be a duplicate of #1921134.
If you're interested, consider this:
https://bugs.launchpad.net/ubuntu/+source/shim/+bug/1921134/comments/3
Or the updated packages should be available in a week.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is
Public bug reported:
Recent test runs of sshuttle autopkgtest are approaching 5 hours.
Here's time stats for 2 example runs on amd64 impish.
1.0.5-1ubuntu1 sshuttle/1.0.5-1ubuntu1 2021-05-05 20:31:35 UTC 4h 59m 27s
racbpasslog artifacts
1.0.5-1ubuntu1 sshuttle/1.0.5-1ubuntu1
** Tags added: fr-1347
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1927654
Title:
/snap/subiquity/2393/usr/bin/subiquity-
The same scenario occurs on impish, without update-notifier being involved:
https://autopkgtest.ubuntu.com/packages/u/update-motd/impish/amd64
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1926298
I believe update-notifier is the innocent bystander here, and the
failure is caused by https://bugs.launchpad.net/ubuntu/+source/update-
motd/+bug/1926660
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
*** This bug is a duplicate of bug 1926298 ***
https://bugs.launchpad.net/bugs/1926298
Thank you for the excellent bug report - your analysis matches ours.
The fix for this should be in progress - said fix is uploaded to impish
already, and the SRU process for hirsute.
** This bug has been
.2.debdiff
** Changed in: update-notifier (Ubuntu Hirsute)
Status: New => Confirmed
** Tags added: patch
** Changed in: update-notifier (Ubuntu Hirsute)
Assignee: Dan Bungert (dbungert) => (unassigned)
--
You received this bug notification because you are a member of Ubuntu
Bugs, whi
** Description changed:
[Impact]
On hirsute/impish, update-notifier can crash when attempting to run hooks.
This issue is the #2 crash on update-notifier in hirsute, presently (and
maybe some of the others). I would call this a severe regression.
+
+ In the crash cases, cleanup steps
** Description changed:
[Impact]
- On Hirsute/Impish, update-notifier can crash when attempting to run
- hooks.
+ On hirsute/impish, update-notifier can crash when attempting to run hooks.
+ This issue is the #2 crash on update-notifier in hirsute, presently (and
+ maybe some of the others).
Test hooks to cover the cases introduced by the original change.
** Attachment added: "tests.tgz"
https://bugs.launchpad.net/ubuntu/+source/update-notifier/+bug/1926298/+attachment/5493991/+files/tests.tgz
--
You received this bug notification because you are a member of Ubuntu
Bugs, which
** Description changed:
+ [Impact]
+
+ On Hirsute/Impish, update-notifier can crash when attempting to run
+ hooks.
+
+ [Test Case]
+
+ Create a file 'bug'
+
+ 'Name: bug
+ Priority: Low
+ Command: "/bin/true"
+ DisplayIf: /bin/true
+ Description: update notifier bug'
+
+ and copy it to
** Attachment added: "_usr_bin_update-notifier.1000.crash"
https://bugs.launchpad.net/ubuntu/+source/update-notifier/+bug/1926298/+attachment/5492933/+files/_usr_bin_update-notifier.1000.crash
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed
It is a patch but I'm not looking for a sponsor at this time, since it's
going thru the MP.
** Tags removed: patch
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1926298
Title:
Segfault added in
MP: https://code.launchpad.net/~dbungert/update-notifier/+git/update-
notifier/+merge/401901
** Changed in: update-notifier (Ubuntu)
Status: In Progress => Confirmed
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
Root cause:
The goto out for cleanup can skip a variable initialization, so in some cases
we
crash on if(pathdirs) g_strfreev(pathdirs); because
** Changed in: update-notifier (Ubuntu)
Status: Confirmed => 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/1926298
Title:
Segfault added in the recent changes
To manage
Marking confirmed as I can see a segfault, but mine looks a little
different:
Thread 1 "update-notifier" received signal SIGSEGV, Segmentation fault.
show_next_hook (hooks=0x55778340 = {...}, ta=, ta=) at hooks.c:376
376 gtk_widget_hide(priv->button_next);
(gdb) bt
#0
** Tags added: fr-1314
** Changed in: update-notifier (Ubuntu)
Assignee: (unassigned) => Dan Bungert (dbungert)
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1926298
Title:
Segfault ad
Thanks Sebastien, great suggestion.
https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=986844
** Bug watch added: Debian Bug tracker #986844
https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=986844
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is
Lengthen the "sleep 1"
** Patch added: "ranger-1-1.9.3-3ubuntu1.debdiff"
https://bugs.launchpad.net/ubuntu/+source/ranger/+bug/1923110/+attachment/5485727/+files/ranger-1-1.9.3-3ubuntu1.debdiff
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is
Also observed in Debian, again on armhf:
https://tests.reproducible-builds.org/debian/rb-pkg/unstable/amd64/ranger.html
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1923110
Title:
autopkgtests may
** Tags added: ftbfs update-excuse
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1923110
Title:
autopkgtests may fail on slow machines
To manage notifications about this bug go to:
Public bug reported:
The autopkgtests contain a "sleep 1" prior to the actual checks.
However, ranger may not start immediately which can mean that the tests
may run too soon.
** Affects: ranger (Ubuntu)
Importance: Undecided
Status: Confirmed
** Tags: fr-1277
** Tags added:
Appears to be fixed upstream in
https://github.com/ranger/ranger/commit/1cdcce0a44d031be13009a70e25cc4cf75789eac
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1912075
Title:
Ranger fails to start
** Changed in: ranger (Ubuntu)
Status: New => Confirmed
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1912075
Title:
Ranger fails to start due to screen dependency
To manage notifications
the
same.
http://bugs.debian.org/986531
** Bug watch added: Debian Bug tracker #986531
https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=986531
** Changed in: greenbone-security-assistant (Ubuntu)
Assignee: Dan Bungert (dbungert) => (unassigned)
--
You received this bug notificatio
My first sbuild of this also fails, but for a different reason. So I
can confirm the bug as well.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1923066
Title:
greenbone-security-assistant ftbfs,
** Tags added: fr-1274
** Changed in: greenbone-security-assistant (Ubuntu)
Assignee: (unassigned) => Dan Bungert (dbungert)
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1923066
Ti
I have run some 40-odd packages that build-depend on dh-exec thru
autopkgtest with my modified dh-exec and everything seems fine,
including talloc using the version prior to my workaround. If my
approach is agreeable I suggest uploading.
--
You received this bug notification because you are a
Here is my proposal:
* dh-exec today desires to remove whitespace after a profile, so preserve that
* dh-exec also removes trailing whitespace, which might be OK and is current
behavior, so preserve that
* remove leading whitespace for lines that don't have the profile
My perl is rusty (to say
401 - 500 of 535 matches
Mail list logo
