** Description changed:
[MIR] iniparser (dependency of mtd-utils)
+
+
+ [Availability]
+ ✓ The package is in universe.
+
+ [Rationale]
+ ✓ The package is a new build dependency of a package that we already
+ support (mtd-utils).
+
+ [Security]
+ ✓ No CVEs
+ ✓ No openwall
+ ✓ No security
** Tags added: fr-248
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1706168
Title:
dialog shouldn't be display if Command doesn't exist
To manage notifications about this bug go to:
** 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.
https://bugs.launchpad.net/bugs/1706168
Title:
dialog shouldn't be display if Command doesn't exist
To
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
$ 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
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
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):
** 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
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
** 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
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.
** 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-
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
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
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
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
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"
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.
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:
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
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:
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:
** 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 -
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
** 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
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
** 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
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
** 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
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
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
** 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.
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
** 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
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
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.
** 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
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.
+ 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).
** 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
.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
*** 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
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
** 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
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.
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
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
** 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/1706168
Title:
dialog shouldn't be display if Comm
ddstreet: if you need any further info or if anything is missing please
let me know. Per the MIR IRC meeting it looks like there is a partial
concern that the library may be redundant, albeit with a different API.
Any further feedback?
--
You received this bug notification because you are a
I appreciate the feedback Matthias.
Please see my new patch. I have seen some unexpected behavior from dh-exec,
and this patch provides a workaround. Tomorrow I plan to play with dh-exec
more and expect to be filing a bug.
** Patch added: "2-2.3.1-2ubuntu1.debdiff"
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
** Tags added: fr-1247
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1920825
Title:
FTBFS and autopkgtest failure in Hirsute (badly generated symbols
files)
To manage notifications about this
Change the generated filename.
** Patch added: "1-2.3.1-2ubuntu1.debdiff"
https://bugs.launchpad.net/ubuntu/+source/talloc/+bug/1920825/+attachment/5482162/+files/1-2.3.1-2ubuntu1.debdiff
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to
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
Hi Bryan,
I advise against SRUing the current patch to focal,
** Tags added: ftbfs
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1918456
Title:
test failure - invalid conversion on armhf
To manage notifications about this bug go to:
** Changed in: tuptime (Ubuntu)
Status: In Progress => Confirmed
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1918848
Title:
regular users can't run tuptime (regression, autopkgtest
** Tags added: patch
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1918848
Title:
regular users can't run tuptime (regression, autopkgtest failure)
To manage notifications about this bug go to:
** Patch removed: "lp-1918848.diff"
https://bugs.launchpad.net/ubuntu/+source/tuptime/+bug/1918848/+attachment/5476152/+files/lp-1918848.diff
** Patch added: "lp-1918848-v2.diff"
https://bugs.launchpad.net/ubuntu/+source/tuptime/+bug/1918848/+attachment/5476156/+files/lp-1918848-v2.diff
** Changed in: tuptime (Ubuntu)
Assignee: Dan Bungert (dbungert) => (unassigned)
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1918848
Title:
regular users can't run tuptime (regress
tuptime creates the directory for its default db location using adduser.
The adduser changes to DIR_MODE=0750 result in the directory not having
world readable mode, and then normal users are unable to read the db
inside.
Attached patch does a chmod 755.
** Patch added: "lp-1918848.diff"
** 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/1918848
Title:
regular users can't run tuptime (regression, autopkgtest failure)
To manage notifications about this bug
n database
file
** Affects: tuptime (Ubuntu)
Importance: Undecided
Assignee: Dan Bungert (dbungert)
Status: In Progress
** Tags: fr-1207
** Changed in: tuptime (Ubuntu)
Assignee: (unassigned) => Dan Bungert (dbungert)
** Tags added: fr-1207
** Changed in: tu
Thanks for the sponsorship Christian!
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1918456
Title:
test failure - invalid conversion on armhf
To manage notifications about this bug go to:
https://launchpadlibrarian.net/527109834/buildlog_ubuntu-hirsute-
armhf.iniparser_4.1-4ubuntu1_BUILDING.txt.gz
** Affects: iniparser (Ubuntu)
Importance: Undecided
Assignee: Dan Bungert (dbungert)
Status: New
** Tags: fr-1199
** Changed in: iniparser (Ubuntu)
Assignee: (unas
** Changed in: iniparser (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/1918456
Title:
test failure - invalid conversion on armhf
To manage notifications
iniparser (Ubuntu)
Status: In Progress => Confirmed
** Changed in: iniparser (Ubuntu)
Assignee: Dan Bungert (dbungert) => (unassigned)
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bug
Security team has provided feedback, indeed there is a patch to merge.
Let's not merge this one yet, and instead get this + the security patch
in one go.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
This patch addresses both items.
** Summary changed:
- build does not run tests in test/ directory
+ non-blocking items from MIR of iniparser: tests, 1 byte stack overflow
** Description changed:
+ The following changes were requested as part of the MIR of libiniparser:
+
+ 1) build does not
Here is a v2 version which doesn't rely on debian/rules override.
** Patch added: "lp1915866+lp1913321-v2.patch"
https://bugs.launchpad.net/ubuntu/+source/iniparser/+bug/1913321/+attachment/5471523/+files/lp1915866+lp1913321-v2.patch
--
You received this bug notification because you are a
Public bug reported:
I looped autopkgtest targeting current hirsute and buster, and was
occasionally able to see failures like this:
debug1: trying public key file
/tmp/autopkgtest.Kh7svp/build.gYC/src/tests/tmp/ms.Rte/authorized_keys/ubuntu
debug1: Could not open authorized keys
** Attachment added: "buster.1.log"
https://bugs.launchpad.net/ubuntu/+source/monkeysphere/+bug/1917943/+attachment/5473624/+files/buster.1.log
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
** Attachment added: "buster.2.log"
https://bugs.launchpad.net/ubuntu/+source/monkeysphere/+bug/1917943/+attachment/5473625/+files/buster.2.log
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
** Attachment added: "hirsute.2.log"
https://bugs.launchpad.net/ubuntu/+source/monkeysphere/+bug/1917943/+attachment/5473623/+files/hirsute.2.log
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
Here is a debdiff incorporating
https://github.com/ndevilla/iniparser/commit/2412f165bcfde4ad8e3426fd59f2a920492b8c19
and the previous LP: #1915866 test build patch.
** Patch added: "lp1915866+lp1913321.patch"
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,
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
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
** 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
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
** 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:
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
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
** 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
** Changed in: iniparser (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/1915866
Title:
build does not run tests in test/ direct
** Tags added: fr-1142
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1915866
Title:
build does not run tests in test/ directory
To manage notifications about this bug go to:
Public bug reported:
tracking bug
** Affects: irssi (Ubuntu)
Importance: Undecided
Status: New
** Tags: fr-1125
** Tags added: fr-1125
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
Thanks for linking to the MR and reviewing it, Julian. Is there
anything else that is needed?
** Changed in: irssi (Ubuntu)
Assignee: (unassigned) => Dan Bungert (dbungert)
** Changed in: irssi (Ubuntu)
Status: New => In Progress
--
You received this bug notification becau
On analysis of this issue, I found that the upstream tests are being run
- it's just that failures go unnoticed due to the test runner
unconditionally returning exit code 0, pass or fail. By enhancing this
runner to return exit code 1 upon test failure, we see the test failure
log without having
Patch attached to LP:#1915866 to address issue with package tests.
I'm holding off on an attempt to merge that patch on LP:#1915866 just yet as I
expect that the security team will have suggestions that we will want to
implement.
--
You received this bug notification because you are a member
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:
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
** 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
1 - 100 of 518 matches
Mail list logo
