Your message dated Fri, 22 Sep 2023 04:52:10 +
with message-id
and subject line Bug#1052234: fixed in ocaml-merlin 4.10-414-1
has caused the Debian Bug report #1052234,
regarding FTBFS with OCaml 4.14.1
to be marked as done.
This means that you claim that the problem has been dealt with.
If
Processing control commands:
> tag -1 pending
Bug #1042049 [src:lintian] lintian: FTBFS: 3 tests failed
Added tag(s) pending.
--
1042049: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1042049
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
Control: tag -1 pending
Hello,
Bug #1042049 in lintian reported by you has been fixed in the
Git repository and is awaiting an upload. You can see the commit
message below and you can check the diff of the fix at:
On Mon, 18 Sep 2023 09:23:19 -0300 Thiago Andrade
wrote:
> I'm waiting for this upgrade. After I'll try to upgrade gobuster to
> 3.6.0 version.
Hello Thiago,
the new package was uploaded and is now in unstable.
However, after manually triggering the autopkgtests two times, I noticed
that a
Your message dated Fri, 22 Sep 2023 00:34:53 +
with message-id
and subject line Bug#1037607: fixed in colobot 0.2.0-2.1
has caused the Debian Bug report #1037607,
regarding colobot: ftbfs with GCC-13
to be marked as done.
This means that you claim that the problem has been dealt with.
If
Your message dated Thu, 21 Sep 2023 23:19:18 +
with message-id
and subject line Bug#1041081: fixed in apitrace 11.1+repack-1.2
has caused the Debian Bug report #1041081,
regarding apitrace FTBFS with waffle 1.7.2-1
to be marked as done.
This means that you claim that the problem has been
Hey.
Any chance to cherry pick the fixing commit from upstream and upload a
new version with that to unstable?
Thanks,
Chris.
Your message dated Thu, 21 Sep 2023 20:38:33 +
with message-id
and subject line Bug#1051454: fixed in librist 0.2.8+dfsg+really0.2.7+dfsg-1
has caused the Debian Bug report #1051454,
regarding librist: FTBFS on 32-bit architectures: "Simple profile unicast
packet loss" test segfaults
to be
Package: pastedeploy
Severity: serious
Tags: patch ftbfs
Justification: fails to build from source (but built successfully in the past)
User: ubuntu-de...@lists.ubuntu.com
Usertags: origin-ubuntu mantic ubuntu-patch
X-Debbugs-Cc: scho...@ubuntu.com
Hi,
The package now fails to build due to
Your message dated Thu, 21 Sep 2023 19:19:40 +
with message-id
and subject line Bug#1050019: fixed in cctz 2.3+dfsg1-4
has caused the Debian Bug report #1050019,
regarding cctz: FTBFS due to time_zone_lookup_test failure
to be marked as done.
This means that you claim that the problem has
Your message dated Thu, 21 Sep 2023 18:19:33 +
with message-id
and subject line Bug#1052417: fixed in bind9 1:9.19.17-1
has caused the Debian Bug report #1052417,
regarding bind9: CVE-2023-4236
to be marked as done.
This means that you claim that the problem has been dealt with.
If this is
Your message dated Thu, 21 Sep 2023 18:19:33 +
with message-id
and subject line Bug#1052416: fixed in bind9 1:9.19.17-1
has caused the Debian Bug report #1052416,
regarding bind9: CVE-2023-3341
to be marked as done.
This means that you claim that the problem has been dealt with.
If this is
Your message dated Thu, 21 Sep 2023 17:54:35 +
with message-id
and subject line Bug#1052334: fixed in rust-leptonica-sys 0.4.6-4
has caused the Debian Bug report #1052334,
regarding rust-leptonica-sys - Debian and Cargo dependencies inconsistent.
to be marked as done.
This means that you
Thanks for the nudge. I must be tired or something as I totally forgot about
updating
the versions in upstream Debian. I'm working on it right now.
Ondrej
--
Ondřej Surý (He/Him)
ond...@sury.org
> On 21. 9. 2023, at 19:23, Salvatore Bonaccorso wrote:
>
> Source: bind9
> Version: 1:9.18.16-1
Processing commands for cont...@bugs.debian.org:
> #
> # bts-link upstream status pull for source package src:gpac
> # see http://lists.debian.org/debian-devel-announce/2006/05/msg1.html
> # https://bts-link-team.pages.debian.net/bts-link/
> #
> user debian-bts-l...@lists.debian.org
Processing commands for cont...@bugs.debian.org:
> #
> # bts-link upstream status pull for source package src:ocsigenserver
> # see http://lists.debian.org/debian-devel-announce/2006/05/msg1.html
> # https://bts-link-team.pages.debian.net/bts-link/
> #
> user
Source: bind9
Version: 1:9.18.16-1
Severity: grave
Tags: security upstream
X-Debbugs-Cc: car...@debian.org, Debian Security Team
Control: found -1 1:9.18.16-1~deb12u1
Hi,
The following vulnerability was published for bind9.
CVE-2023-4236[0]:
| A flaw in the networking code handling
Processing control commands:
> found -1 1:9.18.16-1~deb12u1
Bug #1052417 [src:bind9] bind9: CVE-2023-4236
Marked as found in versions bind9/1:9.18.16-1~deb12u1.
--
1052417: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1052417
Debian Bug Tracking System
Contact ow...@bugs.debian.org with
Processing control commands:
> found -1 1:9.18.16-1~deb12u1
Bug #1052416 [src:bind9] bind9: CVE-2023-3341
Marked as found in versions bind9/1:9.18.16-1~deb12u1.
> found -1 1:9.16.42-1~deb11u1
Bug #1052416 [src:bind9] bind9: CVE-2023-3341
Marked as found in versions bind9/1:9.16.42-1~deb11u1.
>
Source: bind9
Version: 1:9.18.16-1
Severity: grave
Tags: security upstream
X-Debbugs-Cc: car...@debian.org, Debian Security Team
Control: found -1 1:9.18.16-1~deb12u1
Control: found -1 1:9.16.42-1~deb11u1
Control: found -1 1:9.16.37-1~deb11u1
Hi,
The following vulnerability was published for
X-Debbugs-CC: Peter
Control: tags -1 +confirmed
Control: notfound -1 12.1.0-2
Control: fixed -1 12.1.0-2
Hi,
On Thu, 7 Sep 2023 19:43:10 +0200 Peter wrote:
> Thank you for the quick response to my message.
>
> My message is wrong in one place: I tested the old version from Debian
> Bullseye.
Processing control commands:
> tags -1 +confirmed
Bug #1051408 [flameshot] flameshot: uploads potentially sensitive screenshots
to the internet
Added tag(s) confirmed.
> notfound -1 12.1.0-2
Bug #1051408 [flameshot] flameshot: uploads potentially sensitive screenshots
to the internet
No longer
Processing control commands:
> tags -1 wontfix
Bug #1051739 [caja-dropbox] 1.26.0-3 uninstallable due to nonexistent package
Added tag(s) wontfix.
--
1051739: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1051739
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
Control: tags -1 wontfix
Hi,
On So 17 Sep 2023 03:39:55 CEST, Joseph Carter wrote:
Control: severity -1 grave
I didn't do this when filing the bug since ages ago it was
considered impolite for end-users to set severity and particularly
to set a severity above important. But it's been a
On Fri, Sep 01, 2023 at 11:04:44PM +0200, Bastian Germann wrote:
> In vim-script's copyright file, the following assumption is written:
>
> "Summary of license information of each script is reported below. For scripts
> which license is "no license" it is assumed in good faith that having being
>
On 2023-09-21 13:39 +03:00, Simon McVittie wrote:
> On Thu, 21 Sep 2023 at 11:17:51 +0100, Simon McVittie wrote:
>> On Thu, 21 Sep 2023 at 09:41:25 +0300, Alper Nebi Yasak wrote:
>>> I've been using gdm3 without GNOME, and after recently upgrading gdm3 to
>>> 45~beta-1 I started getting the gray
Your message dated Thu, 21 Sep 2023 13:04:12 +
with message-id
and subject line Bug#1052374: fixed in gdm3 45.0.1-1
has caused the Debian Bug report #1052374,
regarding gdm3: Shows only an error screen when gnome.session is missing
to be marked as done.
This means that you claim that the
Processing control commands:
> tag -1 pending
Bug #1052374 [gdm3] gdm3: Shows only an error screen when gnome.session is
missing
Added tag(s) pending.
--
1052374: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1052374
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
Control: tag -1 pending
Hello,
Bug #1052374 in gdm3 reported by you has been fixed in the
Git repository and is awaiting an upload. You can see the commit
message below and you can check the diff of the fix at:
Hello,
> Looks good to me! I just uploaded. If this upload introduces any
> other
> problems, feel free to contact me to upload a fix.
>
> Thanks!
>
Thanks for your contribution and thanks for offering to help with a
possible future upload :)
By the way, the other fixed bug rendered virtual
Your message dated Thu, 21 Sep 2023 12:09:08 +
with message-id
and subject line Bug#1051374: fixed in mini-httpd 1.30-5
has caused the Debian Bug report #1051374,
regarding breaks existing setups using /etc/default/mini-httpd
to be marked as done.
This means that you claim that the problem
Your message dated Thu, 21 Sep 2023 13:50:21 +0200
with message-id <4996da1b-a453-4e75-ad7a-f4f61972c...@debian.org>
and subject line Re: Accepted autopkgtest 5.30 (source) into unstable
has caused the Debian Bug report #1041162,
regarding autopkgtest should ignore ESO entries for pinning
to be
Your message dated Thu, 21 Sep 2023 13:50:21 +0200
with message-id <4996da1b-a453-4e75-ad7a-f4f61972c...@debian.org>
and subject line Re: Accepted autopkgtest 5.30 (source) into unstable
has caused the Debian Bug report #1041162,
regarding autopkgtest should ignore ESO entries for pinning
to be
Quoting Alexandru Mihail (2023-09-21 12:30:52)
> I have no problem with that, can you minimally review the tag and determine
> if it's fit for release or if anything is missing (ignore the added patch,
> that fixes a separate bug) ?
>
> This is still one of my first releases, I'm still getting
Your message dated Thu, 21 Sep 2023 13:40:36 +0200
with message-id <42c8f6c9-360a-4ef4-a32f-22a9dd7aa...@debian.org>
and subject line Re: udev postinst uses update-rc.d -f remove which breaks
/etc.init.d/udev transition and non-systemd boot
has caused the Debian Bug report #1052316,
regarding
On Thu, 21 Sep 2023 at 11:17:51 +0100, Simon McVittie wrote:
> On Thu, 21 Sep 2023 at 09:41:25 +0300, Alper Nebi Yasak wrote:
> > I've been using gdm3 without GNOME, and after recently upgrading gdm3 to
> > 45~beta-1 I started getting the gray "Oh no!" error message instead of
> > the login
Your message dated Thu, 21 Sep 2023 10:18:22 +
with message-id
and subject line Bug#1042172: fixed in ruby-jekyll-commonmark 1.4.0-2
has caused the Debian Bug report #1042172,
regarding ruby-jekyll-commonmark: FTBFS: ERROR: Test "ruby3.1" failed:
Failure/Error:
On Thu, 21 Sep 2023 at 09:41:25 +0300, Alper Nebi Yasak wrote:
> I've been using gdm3 without GNOME, and after recently upgrading gdm3 to
> 45~beta-1 I started getting the gray "Oh no!" error message instead of
> the login screen.
Please look in the system log (systemd Journal) for the error
Control: tag -1 pending
Hello,
Bug #1042172 in ruby-jekyll-commonmark reported by you has been fixed in the
Git repository and is awaiting an upload. You can see the commit
message below and you can check the diff of the fix at:
Processing control commands:
> tag -1 pending
Bug #1042172 [src:ruby-jekyll-commonmark] ruby-jekyll-commonmark: FTBFS: ERROR:
Test "ruby3.1" failed: Failure/Error:
expect(commonmark.convert(content).gsub(%r!\s+!, "")).to
match(output.gsub(%r!\s+!, ""))
Added tag(s) pending.
--
1042172:
Source: python-sparse
Version: 0.13.0-1
Severity: serious
X-Debbugs-CC: nu...@packages.debian.org
Tags: sid trixie
User: debian...@lists.debian.org
Usertags: needs-update
Control: affects -1 src:numba
Dear maintainer(s),
With a recent upload of numba the autopkgtest of python-sparse fails in
Processing control commands:
> affects -1 src:numba
Bug #1052388 [src:python-sparse] python-sparse: autopkgtest needs update for
new version of numba
Added indication that 1052388 affects src:numba
--
1052388: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1052388
Debian Bug Tracking System
Processing control commands:
> close -1 34.0.4-1
Bug #1052383 [src:android-platform-tools] src:android-platform-tools: fails to
migrate to testing for too long: ABI breakage?
Marked as fixed in versions android-platform-tools/34.0.4-1.
Bug #1052383 [src:android-platform-tools]
Source: android-platform-tools
Version: 33.0.3-2
Severity: serious
Control: close -1 34.0.4-1
Tags: sid trixie
User: release.debian@packages.debian.org
Usertags: out-of-sync
Dear maintainer(s),
The Release Team considers packages that are out-of-sync between testing
and unstable for more
Processing commands for cont...@bugs.debian.org:
> tags 1031414 =
Bug #1031414 [src:libgpuarray] libgpuarray: i386 test fail with new pocl
Removed tag(s) fixed-upstream, sid, and bookworm.
> thanks
Stopping processing here.
Please contact me if you need assistance.
--
1031414:
Control: reassign -1 src:libgpuarray
Control: found -1 0.7.6-13
On Mon, 21 Aug 2023 07:51:27 +0100 "Rebecca N. Palmer"
wrote:
Control: severity -1 serious
That wasn't a fix - log with pocl 4:
https://ci.debian.net/data/autopkgtest/testing/i386/libg/libgpuarray/37023715/log.gz
Given that
Processing control commands:
> reassign -1 src:libgpuarray
Bug #1031414 [src:pocl,src:libgpuarray] libgpuarray: i386 test fail with new
pocl
Bug reassigned from package 'src:pocl,src:libgpuarray' to 'src:libgpuarray'.
No longer marked as found in versions libgpuarray/0.7.6-13, pocl/4.0-2,
On Thu, 21 Sep 2023 08:49:04 +0200 Francesco Poli (wintermute) wrote:
> Downgrading/reinstalling the following packages:
>
> libwnck-common (2.30.7-6)
> libwnck22 (2.30.7-6+b1)
> libkeybinder0 (0.3.1-2.1)
> libfm4 (1.3.2-1)
> libfm-gtk4 (1.3.2-1)
> lxpanel-data (0.10.1-2) ...
>
Processing control commands:
> tags -1 + patch
Bug #1042049 [src:lintian] lintian: FTBFS: 3 tests failed
Added tag(s) patch.
--
1042049: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1042049
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
Control: tags -1 + patch
Hi,
Please see the following patch
https://salsa.debian.org/lintian/lintian/-/merge_requests/480
Processing commands for cont...@bugs.debian.org:
> # gdm3: Shows only an error screen when gnome.session is missing
> notfound 1052374 44.1-2
Bug #1052374 [gdm3] gdm3: Shows only an error screen when gnome.session is
missing
Ignoring request to alter found versions of bug #1052374 to the same
Package: lxpanel
Version: 0.10.1-4
Severity: grave
Justification: renders package unusable
Hello!
I have just upgraded lxpanel:
[UPGRADE] lxpanel:amd64 0.10.1-2 -> 0.10.1-4
[UPGRADE] lxpanel-data:amd64 0.10.1-2 -> 0.10.1-4
and not it behaves insanely.
My settings are as follows:
in the
Processing commands for cont...@bugs.debian.org:
> severity 1050300 normal
Bug #1050300 [mkbootimg] mkbootimg package missing gki module
Severity set to 'normal' from 'grave'
> thanks
Stopping processing here.
Please contact me if you need assistance.
--
1050300:
Package: gdm3
Version: 45~beta-1
Severity: serious
Justification: missing dependency to function properly
Control: -1 notfound 44.1-2
Dear Maintainer,
I've been using gdm3 without GNOME, and after recently upgrading gdm3 to
45~beta-1 I started getting the gray "Oh no!" error message instead of
54 matches
Mail list logo