Your message dated Fri, 01 Mar 2024 07:52:51 +
with message-id
and subject line Bug#1062740: fixed in libzdb 3.1-0.3
has caused the Debian Bug report #1062740,
regarding libzdb: NMU diff for 64-bit time_t transition
to be marked as done.
This means that you claim that the problem has been
Your message dated Fri, 01 Mar 2024 07:52:43 +
with message-id
and subject line Bug#1062738: fixed in libyang2 2.1.30-2.1
has caused the Debian Bug report #1062738,
regarding libyang2: NMU diff for 64-bit time_t transition
to be marked as done.
This means that you claim that the problem has
Your message dated Fri, 01 Mar 2024 07:53:11 +
with message-id
and subject line Bug#1062743: fixed in libzip 1.7.3-1.1
has caused the Debian Bug report #1062743,
regarding libzip: NMU diff for 64-bit time_t transition
to be marked as done.
This means that you claim that the problem has been
Your message dated Fri, 01 Mar 2024 07:53:40 +
with message-id
and subject line Bug#1062746: fixed in linbox 1.7.0-3.1
has caused the Debian Bug report #1062746,
regarding linbox: NMU diff for 64-bit time_t transition
to be marked as done.
This means that you claim that the problem has been
Your message dated Fri, 01 Mar 2024 07:53:29 +
with message-id
and subject line Bug#1062745: fixed in liggghts 3.8.0+repack1-9.1
has caused the Debian Bug report #1062745,
regarding liggghts: NMU diff for 64-bit time_t transition
to be marked as done.
This means that you claim that the
Your message dated Fri, 01 Mar 2024 07:52:59 +
with message-id
and subject line Bug#1062741: fixed in libzen 0.4.41-2.1
has caused the Debian Bug report #1062741,
regarding libzen: NMU diff for 64-bit time_t transition
to be marked as done.
This means that you claim that the problem has been
Hi Alex,
On Fri, Mar 01, 2024 at 08:26:31AM +0100, Alexander Kjäll wrote:
> Hi
>
> I was waiting for another transition that was staged in experimental. Due
> to the quality of the different clipboard crates.
>
> But if this block something I will make a temporary solution.
Thanks for the
Dear maintainer,
Please find attached a final version of this patch for the time_t
transition. This patch is being uploaded to unstable.
Note that this adds a versioned build-dependency on dpkg-dev, to guard
against accidental backports with a wrong ABI.
Thanks!
-- System Information:
Debian
Dear maintainer,
Please find attached a final version of this patch for the time_t
transition. This patch is being uploaded to unstable.
Note that this adds a versioned build-dependency on dpkg-dev, to guard
against accidental backports with a wrong ABI.
Thanks!
-- System Information:
Debian
Your message dated Fri, 01 Mar 2024 07:37:48 +
with message-id
and subject line Bug#1062734: fixed in libxmlbird 1.2.15-1.1
has caused the Debian Bug report #1062734,
regarding libxmlbird: NMU diff for 64-bit time_t transition
to be marked as done.
This means that you claim that the problem
Your message dated Fri, 01 Mar 2024 07:37:38 +
with message-id
and subject line Bug#1062733: fixed in libxlsxwriter 1.1.5-1.1
has caused the Debian Bug report #1062733,
regarding libxlsxwriter: NMU diff for 64-bit time_t transition
to be marked as done.
This means that you claim that the
Your message dated Fri, 01 Mar 2024 07:37:24 +
with message-id
and subject line Bug#1062732: fixed in libxeddsa 2.0.0+20221109.06a02c8-2.1
has caused the Debian Bug report #1062732,
regarding libxeddsa: NMU diff for 64-bit time_t transition
to be marked as done.
This means that you claim
Your message dated Fri, 01 Mar 2024 07:37:14 +
with message-id
and subject line Bug#1062731: fixed in libwfa2 2.3.3-2.1
has caused the Debian Bug report #1062731,
regarding libwfa2: NMU diff for 64-bit time_t transition
to be marked as done.
This means that you claim that the problem has
Your message dated Fri, 01 Mar 2024 07:37:05 +
with message-id
and subject line Bug#1062729: fixed in libvslvm 20181227-1.2
has caused the Debian Bug report #1062729,
regarding libvslvm: NMU diff for 64-bit time_t transition
to be marked as done.
This means that you claim that the problem
Your message dated Fri, 01 Mar 2024 07:38:07 +
with message-id
and subject line Bug#1062736: fixed in libxt 1:1.2.1-1.2
has caused the Debian Bug report #1062736,
regarding libxt: NMU diff for 64-bit time_t transition
to be marked as done.
This means that you claim that the problem has been
Your message dated Fri, 01 Mar 2024 07:37:55 +
with message-id
and subject line Bug#1062735: fixed in libxmltok 1.2-4.1
has caused the Debian Bug report #1062735,
regarding libxmltok: NMU diff for 64-bit time_t transition
to be marked as done.
This means that you claim that the problem has
Your message dated Fri, 01 Mar 2024 07:36:44 +
with message-id
and subject line Bug#1062728: fixed in libvmime 0.9.2-8.2
has caused the Debian Bug report #1062728,
regarding libvmime: NMU diff for 64-bit time_t transition
to be marked as done.
This means that you claim that the problem has
Your message dated Fri, 01 Mar 2024 07:36:54 +
with message-id
and subject line Bug#1062727: fixed in libvshadow 20190323-2.1
has caused the Debian Bug report #1062727,
regarding libvshadow: NMU diff for 64-bit time_t transition
to be marked as done.
This means that you claim that the
Dear maintainer,
Please find attached a final version of this patch for the time_t
transition. This patch is being uploaded to unstable.
Note that this adds a versioned build-dependency on dpkg-dev, to guard
against accidental backports with a wrong ABI.
Thanks!
-- System Information:
Debian
Dear maintainer,
Please find attached a final version of this patch for the time_t
transition. This patch is being uploaded to unstable.
Note that this adds a versioned build-dependency on dpkg-dev, to guard
against accidental backports with a wrong ABI.
Thanks!
-- System Information:
Debian
Dear maintainer,
Please find attached a final version of this patch for the time_t
transition. This patch is being uploaded to unstable.
Note that this adds a versioned build-dependency on dpkg-dev, to guard
against accidental backports with a wrong ABI.
Thanks!
-- System Information:
Debian
Dear maintainer,
Please find attached a final version of this patch for the time_t
transition. This patch is being uploaded to unstable.
Note that this adds a versioned build-dependency on dpkg-dev, to guard
against accidental backports with a wrong ABI.
Thanks!
-- System Information:
Debian
Dear maintainer,
Please find attached a final version of this patch for the time_t
transition. This patch is being uploaded to unstable.
Note that this adds a versioned build-dependency on dpkg-dev, to guard
against accidental backports with a wrong ABI.
Thanks!
-- System Information:
Debian
Dear maintainer,
Please find attached a final version of this patch for the time_t
transition. This patch is being uploaded to unstable.
Note that this adds a versioned build-dependency on dpkg-dev, to guard
against accidental backports with a wrong ABI.
Thanks!
-- System Information:
Debian
Hi
I was waiting for another transition that was staged in experimental. Due
to the quality of the different clipboard crates.
But if this block something I will make a temporary solution.
//Alex
On Fri, 1 Mar 2024, 08:19 Salvatore Bonaccorso, wrote:
> Hi
>
> On Mon, Dec 11, 2023 at
Dear maintainer,
Please find attached a final version of this patch for the time_t
transition. This patch is being uploaded to unstable.
Note that this adds a versioned build-dependency on dpkg-dev, to guard
against accidental backports with a wrong ABI.
Thanks!
-- System Information:
Debian
Dear maintainer,
Please find attached a final version of this patch for the time_t
transition. This patch is being uploaded to unstable.
Note that this adds a versioned build-dependency on dpkg-dev, to guard
against accidental backports with a wrong ABI.
Thanks!
-- System Information:
Debian
Dear maintainer,
Please find attached a final version of this patch for the time_t
transition. This patch is being uploaded to unstable.
Note that this adds a versioned build-dependency on dpkg-dev, to guard
against accidental backports with a wrong ABI.
Thanks!
-- System Information:
Debian
Uh yeah let's try that one more time.
On Thu, Feb 29, 2024 at 10:46:43PM -0800, Steve Langasek wrote:
> Sorry, for some reason a number of bugs failed to have their patches
> attached. Please find the debdiff from the experimental upload attached
> now.
>
> On Fri, Feb 02, 2024 at 11:00:08PM
Hi
On Mon, Dec 11, 2023 at 07:10:22PM +0100, Alexander Kjäll wrote:
> Hi
>
> I'm sorry for the semver breakage, the last version was a bit stressed
> out due to the security problems with libgit2 not verifying server
> signatures (that has since been fixed).
>
> I think the best path forward
Dear maintainer,
Please find attached a final version of this patch for the time_t
transition. This patch is being uploaded to unstable.
Note that this adds a versioned build-dependency on dpkg-dev, to guard
against accidental backports with a wrong ABI.
Thanks!
-- System Information:
Debian
Dear maintainer,
Please find attached a final version of this patch for the time_t
transition. This patch is being uploaded to unstable.
Note that this adds a versioned build-dependency on dpkg-dev, to guard
against accidental backports with a wrong ABI.
Thanks!
-- System Information:
Debian
Dear maintainer,
Please find attached a final version of this patch for the time_t
transition. This patch is being uploaded to unstable.
Note that this adds a versioned build-dependency on dpkg-dev, to guard
against accidental backports with a wrong ABI.
Thanks!
-- System Information:
Debian
Dear maintainer,
Please find attached a final version of this patch for the time_t
transition. This patch is being uploaded to unstable.
Note that this adds a versioned build-dependency on dpkg-dev, to guard
against accidental backports with a wrong ABI.
Thanks!
-- System Information:
Debian
Dear maintainer,
Please find attached a final version of this patch for the time_t
transition. This patch is being uploaded to unstable.
Note that this adds a versioned build-dependency on dpkg-dev, to guard
against accidental backports with a wrong ABI.
Thanks!
-- System Information:
Debian
Package: sysvinit-core
Version: 3.08-7
Severity: serious
Tags: patch
User: helm...@debian.org
Usertags: dep17p3
Control: affects -1 + bfh-container progress-linux-container
Hi,
thanks for applying my earlier /usr-move patch #1060139. Since authoring
it, the mitigations for ineffective diversions
Processing control commands:
> affects -1 + bfh-container progress-linux-container
Bug #1065146 [sysvinit-core] sysvinit-core: /usr/sbin/halt and others
ineffectively diverted (DEP17)
Added indication that 1065146 affects bfh-container and progress-linux-container
--
1065146:
Package: guacd
Version: 1.3.0-1.2
Severity: serious
Tags: patch
User: helm...@debian.org
Usertags: dep17
X-Debbugs-Cc: vor...@debian.org
I changed dh_installsystemd to install systemd units below /usr/lib
rather than /lib a while back. Back then, I rebuilt all possibly
affected packages and guacd
Your message dated Fri, 01 Mar 2024 07:04:52 +
with message-id
and subject line Bug#1062752: fixed in linphone 5.2.0-4.3
has caused the Debian Bug report #1062752,
regarding linphone: NMU diff for 64-bit time_t transition
to be marked as done.
This means that you claim that the problem has
Sorry, for some reason a number of bugs failed to have their patches
attached. Please find the debdiff from the experimental upload attached
now.
On Fri, Feb 02, 2024 at 11:01:09PM +, Steve Langasek wrote:
> Source: linbox
> Version: 1.7.0-3
> Severity: serious
> Tags: patch pending sid
Sorry, for some reason a number of bugs failed to have their patches
attached. Please find the debdiff from the experimental upload attached
now.
On Fri, Feb 02, 2024 at 11:01:06PM +, Steve Langasek wrote:
> Source: liggghts
> Version: 3.8.0+repack1-9
> Severity: serious
> Tags: patch
Sorry, for some reason a number of bugs failed to have their patches
attached. Please find the debdiff from the experimental upload attached
now.
On Fri, Feb 02, 2024 at 11:00:57PM +, Steve Langasek wrote:
> Source: libzen
> Version: 0.4.41-2
> Severity: serious
> Tags: patch pending sid
Sorry, for some reason a number of bugs failed to have their patches
attached. Please find the debdiff from the experimental upload attached
now.
On Fri, Feb 02, 2024 at 11:01:04PM +, Steve Langasek wrote:
> Source: libzypp
> Version: 17.31.29-1
> Severity: serious
> Tags: patch pending sid
Sorry, for some reason a number of bugs failed to have their patches
attached. Please find the debdiff from the experimental upload attached
now.
On Fri, Feb 02, 2024 at 11:01:02PM +, Steve Langasek wrote:
> Source: libzip
> Version: 1.7.3-1
> Severity: serious
> Tags: patch pending sid
Sorry, for some reason a number of bugs failed to have their patches
attached. Please find the debdiff from the experimental upload attached
now.
On Fri, Feb 02, 2024 at 11:00:53PM +, Steve Langasek wrote:
> Source: libzdb
> Version: 3.1-0.2
> Severity: serious
> Tags: patch pending sid
close 1063370 1.3.275.0+dfsg1-1
thanks
Didn't realize there was a bug filed for the FTBFS.
Processing commands for cont...@bugs.debian.org:
> close 1063370 1.3.275.0+dfsg1-1
Bug #1063370 [src:vulkan-tools] vulkan-tools: Fails to build from source.
Marked as fixed in versions vulkan-tools/1.3.275.0+dfsg1-1.
Bug #1063370 [src:vulkan-tools] vulkan-tools: Fails to build from source.
Marked
Sorry, for some reason a number of bugs failed to have their patches
attached. Please find the debdiff from the experimental upload attached
now.
On Fri, Feb 02, 2024 at 11:00:49PM +, Steve Langasek wrote:
> Source: libyang2
> Version: 2.1.30-2
> Severity: serious
> Tags: patch pending sid
Sorry, for some reason a number of bugs failed to have their patches
attached. Please find the debdiff from the experimental upload attached
now.
On Fri, Feb 02, 2024 at 11:00:44PM +, Steve Langasek wrote:
> Source: libxt
> Version: 1:1.2.1-1.1
> Severity: serious
> Tags: patch pending sid
... well this time at least, the reason is user error. Really attached now!
On Thu, Feb 29, 2024 at 10:53:04PM -0800, Steve Langasek wrote:
> Sorry, for some reason a number of bugs failed to have their patches
> attached. Please find the debdiff from the experimental upload attached
> now.
>
Sorry, for some reason a number of bugs failed to have their patches
attached. Please find the debdiff from the experimental upload attached
now.
On Fri, Feb 02, 2024 at 11:00:41PM +, Steve Langasek wrote:
> Source: libxmltok
> Version: 1.2-4
> Severity: serious
> Tags: patch pending sid
Sorry, for some reason a number of bugs failed to have their patches
attached. Please find the debdiff from the experimental upload attached
now.
On Fri, Feb 02, 2024 at 11:00:39PM +, Steve Langasek wrote:
> Source: libxmlbird
> Version: 1.2.15-1
> Severity: serious
> Tags: patch pending sid
Sorry, for some reason a number of bugs failed to have their patches
attached. Please find the debdiff from the experimental upload attached
now.
On Fri, Feb 02, 2024 at 11:00:37PM +, Steve Langasek wrote:
> Source: libxlsxwriter
> Version: 1.1.5-1
> Severity: serious
> Tags: patch pending
Dear maintainer,
Please find attached a final version of this patch for the time_t
transition. This patch is being uploaded to unstable.
Note that this adds a versioned build-dependency on dpkg-dev, to guard
against accidental backports with a wrong ABI.
Thanks!
-- System Information:
Debian
Sorry, for some reason a number of bugs failed to have their patches
attached. Please find the debdiff from the experimental upload attached
now.
On Fri, Feb 02, 2024 at 11:00:35PM +, Steve Langasek wrote:
> Source: libxeddsa
> Version: 2.0.0+20221109.06a02c8-2
> Severity: serious
> Tags:
Sorry, for some reason a number of bugs failed to have their patches
attached. Please find the debdiff from the experimental upload attached
now.
On Fri, Feb 02, 2024 at 11:00:17PM +, Steve Langasek wrote:
> Source: libwfa2
> Version: 2.3.3-2
> Severity: serious
> Tags: patch pending sid
Sorry, for some reason a number of bugs failed to have their patches
attached. Please find the debdiff from the experimental upload attached
now.
On Fri, Feb 02, 2024 at 11:00:08PM +, Steve Langasek wrote:
> Source: libwebsockets
> Version: 4.3.3-1
> Severity: serious
> Tags: patch pending
Sorry, for some reason a number of bugs failed to have their patches
attached. Please find the debdiff from the experimental upload attached
now.
On Fri, Feb 02, 2024 at 11:00:05PM +, Steve Langasek wrote:
> Source: libvslvm
> Version: 20181227-1.1
> Severity: serious
> Tags: patch pending
Sorry, for some reason a number of bugs failed to have their patches
attached. Please find the debdiff from the experimental upload attached
now.
On Fri, Feb 02, 2024 at 10:59:56PM +, Steve Langasek wrote:
> Source: libvshadow
> Version: 20190323-2
> Severity: serious
> Tags: patch pending
Sorry, for some reason a number of bugs failed to have their patches
attached. Please find the debdiff from the experimental upload attached
now.
On Fri, Feb 02, 2024 at 10:59:53PM +, Steve Langasek wrote:
> Source: libvmime
> Version: 0.9.2-8.1
> Severity: serious
> Tags: patch pending sid
Your message dated Fri, 01 Mar 2024 06:04:37 +
with message-id
and subject line Bug#1062556: fixed in libosip2 5.3.1-1.1
has caused the Debian Bug report #1062556,
regarding libosip2: NMU diff for 64-bit time_t transition
to be marked as done.
This means that you claim that the problem has
Your message dated Fri, 01 Mar 2024 06:05:06 +
with message-id
and subject line Bug#1062585: fixed in libphonenumber 8.12.57+ds-4.1
has caused the Debian Bug report #1062585,
regarding libphonenumber: NMU diff for 64-bit time_t transition
to be marked as done.
This means that you claim that
Your message dated Fri, 01 Mar 2024 06:04:27 +
with message-id
and subject line Bug#1062498: fixed in liboop 1.0.1-2.2
has caused the Debian Bug report #1062498,
regarding liboop: NMU diff for 64-bit time_t transition
to be marked as done.
This means that you claim that the problem has been
Your message dated Fri, 01 Mar 2024 06:04:18 +
with message-id
and subject line Bug#1062407: fixed in liblopsub 1.0.4-1.1
has caused the Debian Bug report #1062407,
regarding liblopsub: NMU diff for 64-bit time_t transition
to be marked as done.
This means that you claim that the problem has
Dear maintainer,
Please find attached a final version of this patch for the time_t
transition. This patch is being uploaded to unstable.
Note that this adds a versioned build-dependency on dpkg-dev, to guard
against accidental backports with a wrong ABI.
Thanks!
--
Steve Langasek
Dear maintainer,
Please find attached a final version of this patch for the time_t
transition. This patch is being uploaded to unstable.
Note that this adds a versioned build-dependency on dpkg-dev, to guard
against accidental backports with a wrong ABI.
Thanks!
-- System Information:
Debian
Dear maintainer,
Please find attached a final version of this patch for the time_t
transition. This patch is being uploaded to unstable.
Note that this adds a versioned build-dependency on dpkg-dev, to guard
against accidental backports with a wrong ABI.
Thanks!
-- System Information:
Debian
Dear maintainer,
Please find attached a final version of this patch for the time_t
transition. This patch is being uploaded to unstable.
Note that this adds a versioned build-dependency on dpkg-dev, to guard
against accidental backports with a wrong ABI.
Thanks!
-- System Information:
Debian
Your message dated Fri, 01 Mar 2024 04:19:22 +
with message-id
and subject line Bug#1065108: fixed in java3d 1.5.2+dfsg-18
has caused the Debian Bug report #1065108,
regarding java3d: FTBFS: missing build-dep on libnsl-dev
to be marked as done.
This means that you claim that the problem has
Processing control commands:
> tag -1 pending
Bug #1065108 [src:java3d] java3d: FTBFS: missing build-dep on libnsl-dev
Added tag(s) pending.
--
1065108: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1065108
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
Control: tag -1 pending
Hello,
Bug #1065108 in java3d 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:
Dear maintainer,
Please find attached a final version of this patch for the time_t
transition. This patch is being uploaded to unstable.
Note that this adds a versioned build-dependency on dpkg-dev, to guard
against accidental backports with a wrong ABI.
Thanks!
-- System Information:
Debian
Your message dated Fri, 01 Mar 2024 01:19:39 +
with message-id
and subject line Bug#1063309: fixed in zeroc-ice 3.7.10-2.1
has caused the Debian Bug report #1063309,
regarding zeroc-ice: NMU diff for 64-bit time_t transition
to be marked as done.
This means that you claim that the problem
Dear maintainer,
Please find attached a final version of this patch for the time_t
transition. This patch is being uploaded to unstable.
Note that this adds a versioned build-dependency on dpkg-dev, to guard
against accidental backports with a wrong ABI.
Thanks!
-- System Information:
Debian
Your message dated Fri, 01 Mar 2024 00:22:41 +
with message-id
and subject line Bug#1064673: fixed in sphinxbase 0.8+5prealpha+1-17
has caused the Debian Bug report #1064673,
regarding pocketsphinx-python: FTBFS: ImportError:
Your message dated Fri, 01 Mar 2024 00:22:24 +
with message-id
and subject line Bug#1062867: fixed in ros-perception-pcl 1.7.5-1.1
has caused the Debian Bug report #1062867,
regarding ros-perception-pcl: NMU diff for 64-bit time_t transition
to be marked as done.
This means that you claim
Your message dated Fri, 01 Mar 2024 00:22:16 +
with message-id
and subject line Bug#1062866: fixed in ros-image-common 1.12.0-12.1
has caused the Debian Bug report #1062866,
regarding ros-image-common: NMU diff for 64-bit time_t transition
to be marked as done.
This means that you claim that
Your message dated Fri, 01 Mar 2024 00:08:01 +
with message-id
and subject line Bug#1063174: fixed in optee-client 4.1.0-1.1
has caused the Debian Bug report #1063174,
regarding optee-client: NMU diff for 64-bit time_t transition
to be marked as done.
This means that you claim that the
Your message dated Fri, 01 Mar 2024 01:08:41 +0100
with message-id <46203343.fMDQidcC6G@treadstone-71>
and subject line
has caused the Debian Bug report #1062760,
regarding qtquickcontrols2-opensource-src: NMU diff for 64-bit time_t transition
to be marked as done.
This means that you claim that
Your message dated Fri, 01 Mar 2024 00:06:17 +
with message-id
and subject line Bug#1065091: fixed in gtg 0.6-7
has caused the Debian Bug report #1065091,
regarding gtg: crashes on startup
to be marked as done.
This means that you claim that the problem has been dealt with.
If this is not
Your message dated Fri, 01 Mar 2024 00:06:56 +
with message-id
and subject line Bug#1062399: fixed in liblip 2.0.0-2.1
has caused the Debian Bug report #1062399,
regarding liblip: NMU diff for 64-bit time_t transition
to be marked as done.
This means that you claim that the problem has been
Processing control commands:
> tag -1 pending
Bug #1065091 [gtg] gtg: crashes on startup
Added tag(s) pending.
--
1065091: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1065091
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
Control: tag -1 pending
Hello,
Bug #1065091 in gtg 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:
Your message dated Fri, 01 Mar 2024 01:00:56 +0100
with message-id <3613366.R56niFO833@treadstone-71>
and subject line
has caused the Debian Bug report #1062759,
regarding qt6-websockets: NMU diff for 64-bit time_t transition
to be marked as done.
This means that you claim that the problem has
Hi,
On Thu, Feb 29, 2024 at 9:32 AM Simon McVittie wrote:
>
> On Thu, 29 Feb 2024 at 08:40:28 -0300, Leandro Cunha wrote:
> > Jeremy uploaded glib 2.0 to experimental which fixes such problems
>
> libglib2.0-0t64 in experimental does not contain any changes that would
> intentionally fix this.
>
Your message dated Fri, 01 Mar 2024 00:52:14 +0100
with message-id <8386031.NyiUUSuA9g@treadstone-71>
and subject line
has caused the Debian Bug report #1062750,
regarding qt6-virtualkeyboard: NMU diff for 64-bit time_t transition
to be marked as done.
This means that you claim that the problem
Your message dated Thu, 29 Feb 2024 23:45:04 +
with message-id
and subject line Bug#1062857: fixed in rhonabwy 1.1.13-2.1
has caused the Debian Bug report #1062857,
regarding rhonabwy: NMU diff for 64-bit time_t transition
to be marked as done.
This means that you claim that the problem has
Your message dated Thu, 29 Feb 2024 23:45:12 +
with message-id
and subject line Bug#1062863: fixed in rlog 1.4-4.2
has caused the Debian Bug report #1062863,
regarding rlog: NMU diff for 64-bit time_t transition
to be marked as done.
This means that you claim that the problem has been dealt
Your message dated Thu, 29 Feb 2024 23:44:36 +
with message-id
and subject line Bug#1062852: fixed in reglookup 1.0.1+svn287-9.1
has caused the Debian Bug report #1062852,
regarding reglookup: NMU diff for 64-bit time_t transition
to be marked as done.
This means that you claim that the
Your message dated Thu, 29 Feb 2024 23:44:56 +
with message-id
and subject line Bug#1062856: fixed in remctl 3.18-1.1
has caused the Debian Bug report #1062856,
regarding remctl: NMU diff for 64-bit time_t transition
to be marked as done.
This means that you claim that the problem has been
Your message dated Thu, 29 Feb 2024 23:44:44 +
with message-id
and subject line Bug#1062854: fixed in reiserfsprogs 1:3.6.27-7.1
has caused the Debian Bug report #1062854,
regarding reiserfsprogs: NMU diff for 64-bit time_t transition
to be marked as done.
This means that you claim that the
Your message dated Thu, 29 Feb 2024 23:44:28 +
with message-id
and subject line Bug#1062851: fixed in redland 1.0.17-3.1
has caused the Debian Bug report #1062851,
regarding redland: NMU diff for 64-bit time_t transition
to be marked as done.
This means that you claim that the problem has
Your message dated Thu, 29 Feb 2024 23:44:10 +
with message-id
and subject line Bug#1064322: fixed in readline 8.2-3.1
has caused the Debian Bug report #1064322,
regarding readline: NMU diff for 64-bit time_t transition
to be marked as done.
This means that you claim that the problem has
Source: liblip
Dear maintainer,
Please find attached a final version of this patch for the time_t
transition. This patch is being uploaded to unstable.
Note that this adds a versioned build-dependency on dpkg-dev, to guard
against accidental backports with a wrong ABI.
Thanks!
-- System
Your message dated Thu, 29 Feb 2024 23:44:10 +
with message-id
and subject line Bug#1064361: fixed in readline 8.2-3.1
has caused the Debian Bug report #1064361,
regarding libreadline8t64: file loss due to concurrent /usr-move and package
rename (DEP17 P1)
to be marked as done.
This means
Your message dated Thu, 29 Feb 2024 23:44:18 +
with message-id
and subject line Bug#1062850: fixed in readstat 1.1.9-2.1
has caused the Debian Bug report #1062850,
regarding readstat: NMU diff for 64-bit time_t transition
to be marked as done.
This means that you claim that the problem has
Your message dated Thu, 29 Feb 2024 23:43:59 +
with message-id
and subject line Bug#1062771: fixed in rasqal 0.9.33-2.1
has caused the Debian Bug report #1062771,
regarding rasqal: NMU diff for 64-bit time_t transition
to be marked as done.
This means that you claim that the problem has been
Your message dated Thu, 29 Feb 2024 23:43:44 +
with message-id
and subject line Bug#1062769: fixed in radare2 5.5.0+dfsg-1.1
has caused the Debian Bug report #1062769,
regarding radare2: NMU diff for 64-bit time_t transition
to be marked as done.
This means that you claim that the problem
Your message dated Thu, 29 Feb 2024 23:43:15 +
with message-id
and subject line Bug#1062768: fixed in qxmpp 1.5.5-0.4
has caused the Debian Bug report #1062768,
regarding qxmpp: NMU diff for 64-bit time_t transition
to be marked as done.
This means that you claim that the problem has been
Your message dated Thu, 29 Feb 2024 23:43:06 +
with message-id
and subject line Bug#1062767: fixed in quickfix 1.15.1+dfsg-4.1
has caused the Debian Bug report #1062767,
regarding quickfix: NMU diff for 64-bit time_t transition
to be marked as done.
This means that you claim that the problem
1 - 100 of 611 matches
Mail list logo
