Bug#1033180: marked as done (unblock: stayrtr/0.5.1-1)
Your message dated Mon, 20 Mar 2023 00:59:53 +0100
with message-id
and subject line Re: Bug#1033180: unblock: stayrtr/0.5.1-1
has caused the Debian Bug report #1033180,
regarding unblock: stayrtr/0.5.1-1
to be marked as done.
This means that you claim that the problem has been dealt with.
If this is not the case it is now your responsibility to reopen the
Bug report if necessary, and/or fix the problem forthwith.
(NB: If you are a system administrator and have no idea what this
message is talking about, this may indicate a serious mail system
misconfiguration somewhere. Please contact ow...@bugs.debian.org
immediately.)
--
1033180: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1033180
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Package: release.debian.org
Severity: normal
User: release.debian@packages.debian.org
Usertags: unblock
X-Debbugs-Cc: stay...@packages.debian.org
Control: affects -1 + src:stayrtr
Please unblock package stayrtr
The new upstream release contains only an important bug fix, needed to
stop the daemon from crashing in specific conditions.
(This is the upstream bug report of a Debian user who was stuck with the
version in testing: https://github.com/bgp/stayrtr/issues/96.)
diff attached, edited for clarity.
unblock stayrtr/0.5.1-1
--
ciao,
Marco
diff -Nru stayrtr-0.5.0/cmd/stayrtr/stayrtr.go
stayrtr-0.5.1/cmd/stayrtr/stayrtr.go
--- stayrtr-0.5.0/cmd/stayrtr/stayrtr.go2023-02-23 22:35:40.0
+0100
+++ stayrtr-0.5.1/cmd/stayrtr/stayrtr.go2023-03-01 15:36:19.0
+0100
@@ -261,6 +261,38 @@
vrplist = append(vrplist, vrp)
}
+ sort.Slice(vrplist, func(i, j int) bool {
+ // Sort VRPs as per draft-ietf-sidrops-8210bis-10
+ /*
+ 11. ROA PDU Race Minimization
+ When a cache is sending ROA (IPv4 or IPv6) PDUs
to a router, especially an initial
+ full load in response to a Reset Query PDU, two
undesirable race conditions are possible:
+
+ Break Before Make:
+ For some prefix P, an AS may announce two (or
more) ROAs because they are in the
+ process of changing what provider AS is
announcing P. This is a case of "make before break."
+ If a cache is feeding a router and sends the
one not yet in service a significant time
+ before sending the one currently in service,
then BGP data could be marked invalid during
+ the interval. To minimize that interval, the
cache SHOULD announce all ROAs for the same
+ prefix as close to sequentially as possible.
+ Shorter Prefix First:
+ If an AS has issued a ROA for P0, and another
AS (likely their customer) has issued a ROA
+ for P1 which is a sub-prefix of P0, a router
which receives the ROA for P0 before that for
+ P1 is likely to mark a BGP prefix P1 invalid.
Therefore, the cache SHOULD announce the
+ sub-prefix P1 before the covering prefix P0.
+ */
+ CIDRSizei, _ := vrplist[i].Prefix.Mask.Size()
+ CIDRSizej, _ := vrplist[j].Prefix.Mask.Size()
+ if CIDRSizei == CIDRSizej {
+ if vrplist[i].MaxLen != vrplist[j].MaxLen {
+ return vrplist[i].MaxLen > vrplist[j].MaxLen
+ }
+ return bytes.Compare(vrplist[i].Prefix.IP,
vrplist[j].Prefix.IP) < 1
+ } else {
+ return CIDRSizei > CIDRSizej
+ }
+ })
+
for _, v := range brklistjson {
if v.Expires != nil {
// Prevent stale VRPs from being considered
@@ -299,7 +331,7 @@
}
// Ensure that these are sorted, otherwise they
- // don't has right.
+ // don't hash right.
sort.Slice(v.Providers, func(i, j int) bool {
return v.Providers[i] < v.Providers[j]
})
diff -Nru stayrtr-0.5.0/cmd/stayrtr/stayrtr_test.go
stayrtr-0.5.1/cmd/stayrtr/stayrtr_test.go
--- stayrtr-0.5.0/cmd/stayrtr/stayrtr_test.go 2023-02-23 22:35:40.0
+0100
+++ stayrtr-0.5.1/cmd/stayrtr/stayrtr_test.go 2023-03-01 15:36:19.0
+0100
@@ -103,11 +103,6 @@
got, _, _, count, v4count, v6count := processData(stuff, nil, nil)
want := []rtr.VRP{
{
- Prefix: mustParseIPNet("192.168.0.0/24"),
- MaxLen: 24,
- ASN:123,
- },
- {
Prefix:
Bug#1005863: gcc-11: invalid opcode for Geode LX on i386
Package: gcc-11 Followup-For: Bug #1005863 X-Debbugs-Cc: debian-...@lists.debian.org, debian-release@lists.debian.org, debian-pol...@lists.debian.org Hi folks, Bug #1005863 describes a gcc-11 behaviour that results in software that exits ungracefully on Geode LX i686 hardware. Despite self-reporting as i586 sometimes, Geode LX is in fact an i686 CPU (without physical address extensions and multi-instruction noops -- both optional per spec). My assessment -- which may be incorrect -- is that something like 20% of packages in the bookworm i386 suite are susceptible to the bug, so I think that installing bookworm on a Geode LX system would present users with a poor experience of Debian. Would it be fair to raise the severity of this bug to a release-critical level? I understand that toolchains are an important part of the ecosystem and that changes to them -- especially ones that may affect many packages -- should be undertaken with care, and that we are into bookworm's pre-release hard freeze. Thank you, James
Bug#1033213: unblock: darktable/4.2.1-4
Package: release.debian.org
Severity: normal
User: release.debian@packages.debian.org
Usertags: unblock
X-Debbugs-Cc: darkta...@packages.debian.org
Control: affects -1 + src:darktable
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA256
Please unblock package darktable
[ Reason ]
This upload fixes bug #1033001
[ Impact ]
Although the bug is arguably cosmetic (it relates to whether GNOME
displays the correct icon in certain places), it does affect all
darktable users on Wayland, who will presumably be a large fraction of
it's users, as darktable is widely used by non-programmers.
[ Tests ]
I have installed the new package in a clean Bookworm VM and verified
it fixes the bug as claimed. I also installed it on my development
machine (not running GNOME) and verified basic functionality.
[ Risks ]
darktable is a leaf package. The change introduced by this file is a
single line added to a .desktop file
[ Checklist ]
[x] all changes are documented in the d/changelog
[x] I reviewed all changes and I approve them
[x] attach debdiff against the package in testing
[ Other info ]
The one line upstream change is a bit hard to spot in the debdiff (at
least for me), so I will also attach the actual patch.
unblock darktable/4.2.1-4
-BEGIN PGP SIGNATURE-
iQIzBAEBCAAdFiEEkiyHYXwaY0SiY6fqA0U5G1WqFSEFAmQXlNMACgkQA0U5G1Wq
FSG4axAArjJPzP+ohn9w4KUWe4b2WyW//Pxvu6SdEWKSLB+Q3v/UXVgYD7/C1cY0
NTQ9D4opqSh3ihgvvFRkq1UwnJ/qxOfQMeuvf2d5LCUyuuxfp6kKXCHmCuGWxc9T
vIkjfemZkqI4F0TlNEjdL3DP64f+zonkJNo2oRDmmyQoesSHwP5MI08B+TMiV8N6
mi1zxY5rS1EyOEpXOIvEazSWe94TqcjHNHQzinQ3qU7kEBvfiRPUcuTWSD9+uBE/
mr5VhFBHVQSXW7TfTn4IIqB9m25SXHNBcoHlPr0R1oVNgOgdoSkWru3A9NFCfxq8
UyWRZmuZLLLHOrwU5aYWP6LpiuLCY/brhvyq98kaf7O5gIrNp9zP+WQbsgCUO8df
dQx4O63UBpAxT8UiEw6fDraO7uc+dpnL5sRZr5xSfuk7fyorhHt0VB9t44iLESn5
Ca1Rp0A5/XpmiuWO4hA3cDNpM8PTxq5WnmIOXkVZPV9HykgYe+WHi/im+/ZMOHX8
tr7J3SjyWHO6Qf3EvUSxEu9b9onqwsnt324VF37c7dusCmdI2nxjKyVRphPMrkyB
wiVV1ka1s9L48xaEAp8KaQmdaVG+GohAAucfs/4K6p05PfURwvhT9Gof5lSswvmp
JBMQv/a3ZvukqivKb28qPosZV5N72ORQ9z3tppFwyaB4mnqDId4=
=atQJ
-END PGP SIGNATURE-
diff -Nru darktable-4.2.1/debian/changelog darktable-4.2.1/debian/changelog
--- darktable-4.2.1/debian/changelog2023-02-27 08:03:27.0 -0400
+++ darktable-4.2.1/debian/changelog2023-03-19 14:10:18.0 -0300
@@ -1,3 +1,10 @@
+darktable (4.2.1-4) unstable; urgency=medium
+
+ * Cherry-pick upstream commit 385aacf61e55903bb064e0fe99a1d138645f697c:
+add StartupWMClass=darktable to .desktop file. (Closes: #1033001).
+
+ -- David Bremner Sun, 19 Mar 2023 14:10:18 -0300
+
darktable (4.2.1-3) unstable; urgency=medium
* Bug fix: "AVIF support is missing in Darktable", thanks to Guy
diff -Nru
darktable-4.2.1/debian/patches/0001-Fix-missing-application-icon-in-Wayland.patch
darktable-4.2.1/debian/patches/0001-Fix-missing-application-icon-in-Wayland.patch
---
darktable-4.2.1/debian/patches/0001-Fix-missing-application-icon-in-Wayland.patch
1969-12-31 20:00:00.0 -0400
+++
darktable-4.2.1/debian/patches/0001-Fix-missing-application-icon-in-Wayland.patch
2023-03-19 14:10:18.0 -0300
@@ -0,0 +1,21 @@
+From: Victor Forsiuk
+Date: Sat, 18 Mar 2023 13:03:48 +0200
+Subject: Fix missing application icon in Wayland
+
+(cherry picked from commit 385aacf61e55903bb064e0fe99a1d138645f697c)
+---
+ data/org.darktable.darktable.desktop.in | 1 +
+ 1 file changed, 1 insertion(+)
+
+diff --git a/data/org.darktable.darktable.desktop.in
b/data/org.darktable.darktable.desktop.in
+index 23bf16c..4d8895b 100644
+--- a/data/org.darktable.darktable.desktop.in
b/data/org.darktable.darktable.desktop.in
+@@ -20,6 +20,7 @@ StartupNotify=true
+
MimeType=application/x-darktable;image/x-dcraw;image/x-adobe-dng;image/x-canon-cr2;image/x-canon-crw;image/x-fuji-raf;image/x-kodak-dcr;image/x-kodak-kdc;image/x-minolta-mrw;image/x-nikon-nef;image/x-nikon-nrw;image/x-olympus-orf;image/x-panasonic-rw;image/x-panasonic-rw2;image/x-pentax-pef;image/x-sony-arw;image/x-sony-sr2;image/x-sony-srf;image/jpeg;image/png;image/tiff;image/x-portable-bitmap;image/x-portable-graymap;image/x-portable-pixmap;image/x-portable-floatmap;image/vnd.radiance;${DESKTOP_MIME_TYPES}
+
+ Icon=darktable
++StartupWMClass=darktable
+
+ X-Unity-IconBackgroundColor=#252525
+
diff -Nru darktable-4.2.1/debian/patches/series
darktable-4.2.1/debian/patches/series
--- darktable-4.2.1/debian/patches/series 1969-12-31 20:00:00.0
-0400
+++ darktable-4.2.1/debian/patches/series 2023-03-19 14:10:18.0
-0300
@@ -0,0 +1 @@
+0001-Fix-missing-application-icon-in-Wayland.patch
commit 6d62433d6ef413116b0ce834798a694427019891
Author: Victor Forsiuk
Date: Sat Mar 18 13:03:48 2023 +0200
Fix missing application icon in Wayland
(cherry picked from commit 385aacf61e55903bb064e0fe99a1d138645f697c)
diff --git a/data/org.darktable.darktable.desktop.in
b/data/org.darktable.darktable.desktop.in
index 23bf16c543..4d8895b234 100644
---
Processed: unblock: darktable/4.2.1-4
Processing control commands: > affects -1 + src:darktable Bug #1033213 [release.debian.org] unblock: darktable/4.2.1-4 Added indication that 1033213 affects src:darktable -- 1033213: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1033213 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems
Bug#1032986: unblock fdroidserver/2.2.1-1
Control: tags -1 moreinfo Hi, On 15-03-2023 09:40, Hans-Christoph Steiner wrote: The current failure on s390x is caused by endian issues in androguard, a dependency. Has that issue been reported? Please add a link. Normally we expect a debdiff attached to an unblock. This is mostly to trigger the submitter to look at it and make sure that all changes are explained. Can you please elaborate on the changes in ./debian/? Paul (who is leaning to unblocking this). OpenPGP_signature Description: OpenPGP digital signature
Processed: Re: Bug#1032986: unblock fdroidserver/2.2.1-1
Processing control commands: > tags -1 moreinfo Bug #1032986 [release.debian.org] unblock fdroidserver/2.2.1-1 Added tag(s) moreinfo. -- 1032986: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1032986 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems
Re: Bug#1033167: usrmerge: messes with /etc/shells
Hi Marco, On Sun, Mar 19, 2023 at 03:01:20AM +0100, Marco d'Itri wrote: > It is expected that /etc/shells can be edited by system administrators, > I have been doing that forever in my career as a professional system > administrator and until now I was not even aware of these programs from > debianutils. That applies to configuration files in general, right? However, configuration files have an owner from a packaging point of view. > Hence my reasoning that having convert-etc-shells modify the file would > not be harmful, and so far I am not aware of any practical problem that > this has ever caused. If convert-etc-shells were some administrative tool not to be run by maintainer scripts, that would actually be correct. > I also see that you wrote update-shells in 2021, but convert-etc-shells > was added to usrmerge in 2016. update-shells is an attempt at fixing long-standing bugs in add-shell and remove-shell. Prior to update-shells, those were the canonical tools to modify /etc/shells by packages and except for usrmerge, everyone else used those interfaces. Of course, those interfaces are not up to the task posed by usrmerge, so using them wasn't really an option. However, cooperating with debianutils would have been. > Right. But both update-shells and usr-is-merged are new to bookworm, and > I remember that having the /usr/ paths in /etc/shells is not usually > needed, so this explains why nobody has reported actual problems so far. Yeah, it popped up as a reproducibility issue now. > (Also, would you mind moving /var/lib/shells.state to /var/lib/misc/?) Thank you for suggesting this. I agree that that choice of path is better. When opening that can of worms, I would like to figure out whether there are even better places. update-shells is meant to be run by maintainer scripts only. If an administrator were to run it without changes to shells.d, the expected behaviour is noop. Thus, I am wondering whether something below /usr would be a better choice wrt. hermetic /usr. I think the major question here is what should happen if /etc/shells is deleted. If it should be populated with shells by update-shells, then its state file also needs to be deleted. This would be a reason for the location in /var, which would likekly be discarded together with /etc. If however, we see update-shells purely as a packaging tool, then something below /usr could be better (in a similar vein as we consider moving the dpkg database to /usr). Would you be able to help with finding an answer to this question? Then I wonder what severity that change in location should bear. Is it something we want to do during freeze? Is it worth the effort or more like a time travel fix? In any case, I think this is a separate issue. Would you clone it if you care deeply enough? I also noticed one other flaw in my proposal: Running convert-etc-shells as part of update-shells would cause /usr variants of shells to be re-added after having been removed by administrators. So the convert-etc-shells should be a one time conversion action instead and only happen on the first run of update-shells after a /usr-merge. I think this can be achieved by adding a flag-value to shells.state. I've prepared an update for debianutils and tested it in the following cases: * Installation on a pre-merged chroot -> /usr/bin/sh is added to /etc/shells. * Installation on a chroot merged by usrmerge -> no difference * Installation on an unmerged system. Manual merge without convert-etc-shells. Manual update-shells. -> Looks the same as after convert-etc-shells. Does anyone see any bugs? Helmut diff --minimal -Nru debianutils-5.7/debian/changelog debianutils-5.7/debian/changelog --- debianutils-5.7/debian/changelog2022-11-02 17:31:14.0 +0100 +++ debianutils-5.7/debian/changelog2023-03-19 15:00:09.0 +0100 @@ -1,3 +1,10 @@ +debianutils (5.7-0.5) UNRELEASED; urgency=medium + + * Non-maintainer upload. + * Absorb usrmerge's convert-etc-shells into update-shells. + + -- Helmut Grohne Sun, 19 Mar 2023 15:00:09 +0100 + debianutils (5.7-0.4) unstable; urgency=medium * Non-maintainer upload diff --minimal -Nru debianutils-5.7/debian/patches/absorb-convert-etc-shells debianutils-5.7/debian/patches/absorb-convert-etc-shells --- debianutils-5.7/debian/patches/absorb-convert-etc-shells1970-01-01 01:00:00.0 +0100 +++ debianutils-5.7/debian/patches/absorb-convert-etc-shells2023-03-19 15:00:09.0 +0100 @@ -0,0 +1,112 @@ +Absorb the script convert-etc-shells from usrmerge to obtain reproducible +behaviour. usrmerge will stop running convert-etc-shells and instead trigger +the shells update in debianutils. + +--- a/update-shells b/update-shells +@@ -1,11 +1,15 @@ + #!/bin/sh + # SPDX-License-Identifier: GPL-2.0-or-later + # Copyright 2021 Helmut Grohne +- ++# + # A "hashset" is a shell variable containing a sequence of elements separated + # and surrounded by hash (#) characters. None
Bug#1033194: unblock: ruby-asciidoctor-include-ext/0.4.0-2
Hi Pirate, On 19-03-2023 16:32, Pirate Praveen wrote: On Sun, Mar 19 2023 at 02:31:02 PM +01:00:00 +01:00:00, Sebastian Ramacher wrote: This type of change is not acceptable during hard freeze. Please revert. ok then we can just remove the version currently in testing. Can you elaborate why bumping the debhelper compat level is a targeted fix? I suggest to read our FAQ [1] which elaborates *why* it's not acceptable (unless substantiated why it's needed and what checks where done). Paul [1] https://release.debian.org/testing/FAQ.html (last paragraph) OpenPGP_signature Description: OpenPGP digital signature
Bug#1033203: unblock: fuse3/3.14.0-3
Package: release.debian.org
Severity: normal
User: release.debian@packages.debian.org
Usertags: unblock
X-Debbugs-Cc: Cyril Brulebois
Control: affects -1 + src:fuse3
Hi RMs,
[ Reason ]
The self-testing of fuse3 only works on little-endian machines. I've
already disabled it on big-endian release architectures. Missed hppa
which is not added to the list.
Compiling examples didn't work due to outdated Makefile and using an
outdated header name in one of the files.
[ Impact ]
With the changes fuse3 is compiled on hppa now. As the installer needs
its udeb it can be created on that architecture as well from now on.
One of the example files was patched to use the current header file
name and now compiles with all of the other example files.
[ Tests ]
I've tested the examples compilation and those are OK now. Compilation
on hppa is now working as can be seen in the buildd logs [1].
[ Risks ]
None of the changes affect the working of the package itself.
As fuse3 has an udeb I put kibi to the loop if extra ACK is needed.
[ Checklist ]
[X] all changes are documented in the d/changelog
[X] I reviewed all changes and I approve them
[X] attach debdiff against the package in testing
unblock fuse3/3.14.0-3
Thanks for considering,
Laszlo/GCS
[1] https://buildd.debian.org/status/logs.php?pkg=fuse3=hppa
diff -Nru fuse3-3.14.0/debian/changelog fuse3-3.14.0/debian/changelog
--- fuse3-3.14.0/debian/changelog 2023-02-18 07:22:30.0 +0100
+++ fuse3-3.14.0/debian/changelog 2023-03-17 20:51:05.0 +0100
@@ -1,3 +1,15 @@
+fuse3 (3.14.0-3) unstable; urgency=medium
+
+ [ Helge Deller ]
+ * Add the big-endian hppa platform to the disabled self-testing list
+(closes: #1032187).
+
+ [ Laszlo Boszormenyi (GCS) ]
+ * Update fuse header name in examples.
+ * Fix Makefile for examples (closes: #1031544).
+
+ -- Laszlo Boszormenyi (GCS) Fri, 17 Mar 2023 20:51:05 +0100
+
fuse3 (3.14.0-2) unstable; urgency=medium
* Revert upgrade of fuse_kernel.h for not being upstreamed yet
diff -Nru fuse3-3.14.0/debian/examples/Makefile fuse3-3.14.0/debian/examples/Makefile
--- fuse3-3.14.0/debian/examples/Makefile 2014-06-20 08:23:50.0 +0200
+++ fuse3-3.14.0/debian/examples/Makefile 2023-03-17 20:51:05.0 +0100
@@ -1,12 +1,16 @@
-CFLAGS := -Wall $(shell pkg-config fuse --cflags)
-LDFLAGS := $(shell pkg-config fuse --libs)
+CFLAGS := -Wall $(shell pkg-config fuse3 --cflags)
+LDFLAGS := $(shell pkg-config fuse3 --libs)
-targets = fusexmp fusexmp_fh hello hello_ll null
+targets = cuse cuse_client hello hello_ll \
+ invalidate_path ioctl ioctl_client \
+ notify_inval_entry notify_inval_inode notify_store_retrieve \
+ null passthrough passthrough_fh passthrough_ll \
+ poll poll_client printcap
-all: $(targets)
+%: %.c
+ $(CC) $(CFLAGS) $< -o $@ $(LDFLAGS)
-fusexmp_fh: fusexmp_fh.c
- $(CC) $(CFLAGS) $(LDFLAGS) -lulockmgr $< -o $@
+all: $(targets)
clean:
rm -f *.o
diff -Nru fuse3-3.14.0/debian/patches/series fuse3-3.14.0/debian/patches/series
--- fuse3-3.14.0/debian/patches/series 2023-02-18 07:22:30.0 +0100
+++ fuse3-3.14.0/debian/patches/series 2023-03-17 20:51:05.0 +0100
@@ -1 +1,2 @@
revert_upgrade_of_fuse_kernel.h.patch
+update_header_name.patch
diff -Nru fuse3-3.14.0/debian/patches/update_header_name.patch fuse3-3.14.0/debian/patches/update_header_name.patch
--- fuse3-3.14.0/debian/patches/update_header_name.patch 1970-01-01 01:00:00.0 +0100
+++ fuse3-3.14.0/debian/patches/update_header_name.patch 2023-03-17 20:51:05.0 +0100
@@ -0,0 +1,21 @@
+Description: use new header name of fuse
+ Just rename fuse_config.h to libfuse_config.h
+Author: Laszlo Boszormenyi (GCS)
+Bug-Debian: https://bugs.debian.org/1031544
+Forwarded: no
+Last-Update: 2023-03-17
+
+---
+
+
+--- fuse3-3.14.0.orig/example/poll_client.c
fuse3-3.14.0/example/poll_client.c
+@@ -19,7 +19,7 @@
+ * \include poll_client.c
+ */
+
+-#include
++#include
+
+ #include
+ #include
diff -Nru fuse3-3.14.0/debian/rules fuse3-3.14.0/debian/rules
--- fuse3-3.14.0/debian/rules 2023-01-22 08:17:08.0 +0100
+++ fuse3-3.14.0/debian/rules 2023-03-17 20:51:05.0 +0100
@@ -54,7 +54,7 @@
override_dh_auto_test:
ifeq (,$(findstring nocheck,$(DEB_BUILD_OPTIONS)))
-ifeq (,$(findstring $(DEB_BUILD_ARCH),powerpc ppc64 sparc64 s390x))
+ifeq (,$(findstring $(DEB_BUILD_ARCH),powerpc ppc64 sparc64 s390x hppa))
(cd obj-${DEB_HOST_GNU_TYPE}; python3 -m pytest test/) \
|| true
endif
Processed: unblock: fuse3/3.14.0-3
Processing control commands: > affects -1 + src:fuse3 Bug #1033203 [release.debian.org] unblock: fuse3/3.14.0-3 Added indication that 1033203 affects src:fuse3 -- 1033203: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1033203 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems
Bug#1033194: unblock: ruby-asciidoctor-include-ext/0.4.0-2
On Sun, Mar 19 2023 at 02:31:02 PM +01:00:00 +01:00:00, Sebastian Ramacher wrote: This type of change is not acceptable during hard freeze. Please revert. ok then we can just remove the version currently in testing.
Bug#1033197: unblock: sqlite3/3.40.1-2
Hi László and the release team, Thanks for merging my patch and taking care of opening this unblock request. László Böszörményi (2023-03-19): > [ Reason ] > Cyril Brulebois (kibi) who is the maintainer of crowdsec found out > that partial upgrade of Bullseye to Bookworm may render it unable to > start. Reason is, sqlite3 with 3.37.0-1 changed its internal > table_info representation. Previously the column types were in > lowercase letters and from this version these are using uppercase > letters - confusing the Bullseye version of crowdsec. With the version > in Bookworm it is already fixed. Meanwhile, I also found out that the new crowdsec version doesn't work with the old libsqlite3-0 (as it uses newer syntax). I've documented that in #1033132, and I've uploaded a fix already, after running the tests mentioned below. > [ Impact ] > Upgrading only libsqlite3-0 but not crowdsec makes the latter unusable > as it will not start. To prevent such situations I've added breaks on > old crowdsec versions. > > [ Tests ] > Kibi did the testing [1] and the fix only prevents incompatible > versions of the mentioned packages to be installed. I've extended the testing with a crowdsec package bumping its versioned dependency on libsqlite3-0, i.e. hardcoding a minimal version that we know to be needed syntax-wise (3.35.0), as opposed to the minimal one determined via the usual shared library mechanism (3.12.0). Test setup: - bullseye VM with crowdsec/bullseye installed. - apt pointing at bookworm, except with libsqlite3-0 and crowdsec pinned negatively via /etc/apt/preferences. - apt pointing at extra repository that contains libsqlite3-0 from unstable (3.40.1-2) and the tentative crowdsec 1.4.6-3 package (now uploaded to unstable since tests were all green). Triggering these work fine: - Ugrading crowdsec → pulls upgraded libsqlite3-0 along with a few other packages like glibc binaries, and the unpack/configure steps are fine. - Upgrading libsqlite3-0 → pulls upgraded crowdsec along with a few other packages like glibc binaries, and the unpack/configure steps are fine. - Dist-upgrading entirely is fine as well. The transcript for the first two is attached for information. I can replay the third scenario and attach it as well if needed, but I thought concentrating on the two partial upgrades made the most sense. Cheers, -- Cyril Brulebois -- Debian Consultant @ DEBAMAX -- https://debamax.com/ root@crowdsec11:~# apt-get install crowdsec Reading package lists... Done Building dependency tree... Done Reading state information... Done The following additional packages will be installed: libc-bin libc-l10n libc6 libsqlite3-0 locales Suggested packages: glibc-doc libnss-nis libnss-nisplus The following packages will be upgraded: crowdsec libc-bin libc-l10n libc6 libsqlite3-0 locales 6 upgraded, 0 newly installed, 0 to remove and 287 not upgraded. Need to get 40.5 MB of archives. After this operation, 70.6 MB of additional disk space will be used. Do you want to continue? [Y/n] […] Reading changelogs... Done Preconfiguring packages ... (Reading database ... 35506 files and directories currently installed.) Preparing to unpack .../libc-l10n_2.36-8_all.deb ... Unpacking libc-l10n (2.36-8) over (2.31-13+deb11u5) ... Preparing to unpack .../locales_2.36-8_all.deb ... Unpacking locales (2.36-8) over (2.31-13+deb11u5) ... Preparing to unpack .../libc6_2.36-8_amd64.deb ... Checking for services that may need to be restarted... Checking init scripts... Unpacking libc6:amd64 (2.36-8) over (2.31-13+deb11u5) ... Setting up libc6:amd64 (2.36-8) ... Checking for services that may need to be restarted... Checking init scripts... Restarting services possibly affected by the upgrade: ssh: restarting...done. cron: restarting...done. Services restarted successfully. (Reading database ... 35494 files and directories currently installed.) Preparing to unpack .../libc-bin_2.36-8_amd64.deb ... Unpacking libc-bin (2.36-8) over (2.31-13+deb11u5) ... Setting up libc-bin (2.36-8) ... (Reading database ... 35494 files and directories currently installed.) Preparing to unpack .../crowdsec_1.4.6-3_amd64.deb ... Unpacking crowdsec (1.4.6-3) over (1.0.9-2+b4) ... Removing obsolete conffile /etc/logrotate.d/crowdsec ... Preparing to unpack .../libsqlite3-0_3.40.1-2_amd64.deb ... Unpacking libsqlite3-0:amd64 (3.40.1-2) over (3.34.1-3) ... Setting up libc-l10n (2.36-8) ... Setting up libsqlite3-0:amd64 (3.40.1-2) ... Setting up locales (2.36-8) ... Installing new version of config file /etc/locale.alias ... Generating locales (this might take a while)... fr_FR.UTF-8... done Generation complete. Setting up crowdsec (1.4.6-3) ... Installing new version of config file /etc/crowdsec/config.yaml ... Installing new version of config file /etc/crowdsec/patterns/mysql ... Installing new version of config file /etc/crowdsec/patterns/ssh ... Installing new version of config file /etc/crowdsec/profiles.yaml ... I: All
Bug#1033194: unblock: ruby-asciidoctor-include-ext/0.4.0-2
Control: tags -1 moreinfo
On 2023-03-19 18:14:29 +0530, Pirate Praveen wrote:
> Control: tags -1 -moreinfo
>
>
> On Sun, Mar 19 2023 at 01:40:57 PM +01:00:00 +01:00:00, Sebastian Ramacher
> wrote:
> > Control: tags -1 moreinfo
> >
> > Please provide a debdiff
>
> debdiff attached.
>
> diff -Nru ruby-asciidoctor-include-ext-0.3.1/asciidoctor-include-ext.gemspec
> ruby-asciidoctor-include-ext-0.4.0/asciidoctor-include-ext.gemspec
> --- ruby-asciidoctor-include-ext-0.3.1/asciidoctor-include-ext.gemspec
> 2019-08-22 14:40:31.0 +0530
> +++ ruby-asciidoctor-include-ext-0.4.0/asciidoctor-include-ext.gemspec
> 2022-05-06 12:42:42.0 +0530
> @@ -1,4 +1,4 @@
> -require File.expand_path('../lib/asciidoctor/include_ext/version', __FILE__)
> +require File.expand_path('lib/asciidoctor/include_ext/version', __dir__)
>
> Gem::Specification.new do |s|
>s.name= 'asciidoctor-include-ext'
> @@ -9,24 +9,22 @@
>s.license = 'MIT'
>
>s.summary = "Asciidoctor's standard include::[] processor
> reimplemented as an extension"
> - s.description = < -This is a reimplementation of the Asciidoctor's built-in (pre)processor for
> the
> -include::[] directive in extensible and more clean way. It provides the same
> -features, but you can easily adjust it or extend for your needs. For example,
> -you can change how it loads included files or add another ways how to select
> -portions of the document to include.
> -EOF
> + s.description = <<~EOF
> +This is a reimplementation of the Asciidoctor's built-in (pre)processor
> for the
> +include::[] directive in extensible and more clean way. It provides the
> same
> +features, but you can easily adjust it or extend for your needs. For
> example,
> +you can change how it loads included files or add another ways how to
> select
> +portions of the document to include.
> + EOF
>
>s.files = Dir['lib/**/*', '*.gemspec', 'LICENSE*', 'README*']
> - s.has_rdoc= 'yard'
>
> - s.required_ruby_version = '>= 2.1'
> + s.required_ruby_version = '>= 2.3'
>
>s.add_runtime_dependency 'asciidoctor', '>= 1.5.6', '< 3.0.0'
>
> - s.add_development_dependency 'corefines', '~> 1.11'
> - s.add_development_dependency 'kramdown', '~> 1.16'
> - s.add_development_dependency 'rake', '~> 12.0'
> + s.add_development_dependency 'kramdown', '~> 2.0'
> + s.add_development_dependency 'rake', '~> 13.0'
>s.add_development_dependency 'rspec', '~> 3.7'
>s.add_development_dependency 'rubocop', '~> 0.51.0'
>s.add_development_dependency 'simplecov', '~> 0.15'
> diff -Nru ruby-asciidoctor-include-ext-0.3.1/debian/changelog
> ruby-asciidoctor-include-ext-0.4.0/debian/changelog
> --- ruby-asciidoctor-include-ext-0.3.1/debian/changelog 2019-09-04
> 13:58:01.0 +0530
> +++ ruby-asciidoctor-include-ext-0.4.0/debian/changelog 2023-03-19
> 17:22:18.0 +0530
> @@ -1,3 +1,36 @@
> +ruby-asciidoctor-include-ext (0.4.0-2) unstable; urgency=medium
> +
> + * Team Upload
> + * Reupload to unstable (gitlab is only reverse dependency, which is not in
> +testing)
> + * Bump Standards-Version to 4.6.2 (no changes needed)
> + * Switch to ${ruby:Depends} for ruby dependencies
> +
> + -- Pirate Praveen Sun, 19 Mar 2023 17:22:18 +0530
> +
> +ruby-asciidoctor-include-ext (0.4.0-1) experimental; urgency=medium
> +
> + * Team upload
> +
> + [ Debian Janitor ]
> + * Bump debhelper from old 11 to 12.
> + * Set debhelper-compat version in Build-Depends.
> + * Set upstream metadata fields: Bug-Database, Bug-Submit, Repository,
> +Repository-Browse.
> + * Update standards version to 4.5.0, no changes needed.
> + * Update watch file format version to 4.
> + * Remove constraints unnecessary since buster:
> ++ Build-Depends: Drop versioned constraint on ruby-asciidoctor.
> ++ ruby-asciidoctor-include-ext: Drop versioned constraint on
> + ruby-asciidoctor in Depends.
> +
> + [ Pirate Praveen ]
> + * New upstream version 0.4.0
> + * Bump Standards-Version to 4.6.1 (no changes needed)
> + * Bump debhelper compatibility level to 13
This type of change is not acceptable during hard freeze. Please revert.
Cheers
> +
> + -- Pirate Praveen Sun, 26 Jun 2022 22:48:20 +0530
> +
> ruby-asciidoctor-include-ext (0.3.1-2) unstable; urgency=medium
>
>* Team upload
> diff -Nru ruby-asciidoctor-include-ext-0.3.1/debian/compat
> ruby-asciidoctor-include-ext-0.4.0/debian/compat
> --- ruby-asciidoctor-include-ext-0.3.1/debian/compat 2019-09-04
> 13:58:01.0 +0530
> +++ ruby-asciidoctor-include-ext-0.4.0/debian/compat 1970-01-01
> 05:30:00.0 +0530
> @@ -1 +0,0 @@
> -11
> diff -Nru ruby-asciidoctor-include-ext-0.3.1/debian/control
> ruby-asciidoctor-include-ext-0.4.0/debian/control
> --- ruby-asciidoctor-include-ext-0.3.1/debian/control 2019-09-04
> 13:58:01.0 +0530
> +++ ruby-asciidoctor-include-ext-0.4.0/debian/control 2023-03-19
>
Processed: Re: Bug#1033194: unblock: ruby-asciidoctor-include-ext/0.4.0-2
Processing control commands: > tags -1 moreinfo Bug #1033194 [release.debian.org] unblock: ruby-asciidoctor-include-ext/0.4.0-2 Added tag(s) moreinfo. -- 1033194: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1033194 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems
Bug#1033197: unblock: sqlite3/3.40.1-2
Package: release.debian.org
Severity: normal
User: release.debian@packages.debian.org
Usertags: unblock
X-Debbugs-Cc: Cyril Brulebois
Control: affects -1 + src:sqlite3
Hi RMs,
[ Reason ]
Cyril Brulebois (kibi) who is the maintainer of crowdsec found out
that partial upgrade of Bullseye to Bookworm may render it unable to
start. Reason is, sqlite3 with 3.37.0-1 changed its internal
table_info representation. Previously the column types were in
lowercase letters and from this version these are using uppercase
letters - confusing the Bullseye version of crowdsec. With the version
in Bookworm it is already fixed.
[ Impact ]
Upgrading only libsqlite3-0 but not crowdsec makes the latter unusable
as it will not start. To prevent such situations I've added breaks on
old crowdsec versions.
[ Tests ]
Kibi did the testing [1] and the fix only prevents incompatible
versions of the mentioned packages to be installed.
[ Risks ]
Basically nothing.
[ Checklist ]
[X] all changes are documented in the d/changelog
[X] I reviewed all changes and I approve them
[X] attach debdiff against the package in testing
unblock sqlite3/3.40.1-2
Thanks for consideration,
Laszlo/GCS
[1] https://bugs.debian.org/1033029
diff -Nru sqlite3-3.40.1/debian/changelog sqlite3-3.40.1/debian/changelog
--- sqlite3-3.40.1/debian/changelog 2022-12-31 09:41:40.0 +0100
+++ sqlite3-3.40.1/debian/changelog 2023-03-16 19:54:28.0 +0100
@@ -1,3 +1,12 @@
+sqlite3 (3.40.1-2) unstable; urgency=medium
+
+ [ Cyril Brulebois ]
+ * Add Breaks against crowdsec as found in bullseye, as it relies on a
+particular table_info format, which changes between 3.36.0 and 3.37.0
+(closes: #1033029).
+
+ -- Laszlo Boszormenyi (GCS) Thu, 16 Mar 2023 19:54:28 +0100
+
sqlite3 (3.40.1-1) unstable; urgency=medium
* New upstream release.
diff -Nru sqlite3-3.40.1/debian/control sqlite3-3.40.1/debian/control
--- sqlite3-3.40.1/debian/control 2022-12-31 09:41:40.0 +0100
+++ sqlite3-3.40.1/debian/control 2023-03-16 19:54:28.0 +0100
@@ -52,7 +52,7 @@
Section: libs
Architecture: any
Depends: ${shlibs:Depends}, ${misc:Depends}
-Breaks: python-migrate (<< 0.11.0-4~), python3-migrate (<< 0.11.0-4~)
+Breaks: python-migrate (<< 0.11.0-4~), python3-migrate (<< 0.11.0-4~), crowdsec (<< 1.4)
Multi-Arch: same
Pre-Depends: ${misc:Pre-Depends}
Description: SQLite 3 shared library
Processed: unblock: sqlite3/3.40.1-2
Processing control commands: > affects -1 + src:sqlite3 Bug #1033197 [release.debian.org] unblock: sqlite3/3.40.1-2 Added indication that 1033197 affects src:sqlite3 -- 1033197: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1033197 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems
Bug#1033194: unblock: ruby-asciidoctor-include-ext/0.4.0-2
Control: tags -1 -moreinfo
On Sun, Mar 19 2023 at 01:40:57 PM +01:00:00 +01:00:00, Sebastian
Ramacher wrote:
Control: tags -1 moreinfo
Please provide a debdiff
debdiff attached.
diff -Nru ruby-asciidoctor-include-ext-0.3.1/asciidoctor-include-ext.gemspec ruby-asciidoctor-include-ext-0.4.0/asciidoctor-include-ext.gemspec
--- ruby-asciidoctor-include-ext-0.3.1/asciidoctor-include-ext.gemspec 2019-08-22 14:40:31.0 +0530
+++ ruby-asciidoctor-include-ext-0.4.0/asciidoctor-include-ext.gemspec 2022-05-06 12:42:42.0 +0530
@@ -1,4 +1,4 @@
-require File.expand_path('../lib/asciidoctor/include_ext/version', __FILE__)
+require File.expand_path('lib/asciidoctor/include_ext/version', __dir__)
Gem::Specification.new do |s|
s.name= 'asciidoctor-include-ext'
@@ -9,24 +9,22 @@
s.license = 'MIT'
s.summary = "Asciidoctor's standard include::[] processor reimplemented as an extension"
- s.description = <= 1.5.6', '< 3.0.0'
- s.add_development_dependency 'corefines', '~> 1.11'
- s.add_development_dependency 'kramdown', '~> 1.16'
- s.add_development_dependency 'rake', '~> 12.0'
+ s.add_development_dependency 'kramdown', '~> 2.0'
+ s.add_development_dependency 'rake', '~> 13.0'
s.add_development_dependency 'rspec', '~> 3.7'
s.add_development_dependency 'rubocop', '~> 0.51.0'
s.add_development_dependency 'simplecov', '~> 0.15'
diff -Nru ruby-asciidoctor-include-ext-0.3.1/debian/changelog ruby-asciidoctor-include-ext-0.4.0/debian/changelog
--- ruby-asciidoctor-include-ext-0.3.1/debian/changelog 2019-09-04 13:58:01.0 +0530
+++ ruby-asciidoctor-include-ext-0.4.0/debian/changelog 2023-03-19 17:22:18.0 +0530
@@ -1,3 +1,36 @@
+ruby-asciidoctor-include-ext (0.4.0-2) unstable; urgency=medium
+
+ * Team Upload
+ * Reupload to unstable (gitlab is only reverse dependency, which is not in
+testing)
+ * Bump Standards-Version to 4.6.2 (no changes needed)
+ * Switch to ${ruby:Depends} for ruby dependencies
+
+ -- Pirate Praveen Sun, 19 Mar 2023 17:22:18 +0530
+
+ruby-asciidoctor-include-ext (0.4.0-1) experimental; urgency=medium
+
+ * Team upload
+
+ [ Debian Janitor ]
+ * Bump debhelper from old 11 to 12.
+ * Set debhelper-compat version in Build-Depends.
+ * Set upstream metadata fields: Bug-Database, Bug-Submit, Repository,
+Repository-Browse.
+ * Update standards version to 4.5.0, no changes needed.
+ * Update watch file format version to 4.
+ * Remove constraints unnecessary since buster:
++ Build-Depends: Drop versioned constraint on ruby-asciidoctor.
++ ruby-asciidoctor-include-ext: Drop versioned constraint on
+ ruby-asciidoctor in Depends.
+
+ [ Pirate Praveen ]
+ * New upstream version 0.4.0
+ * Bump Standards-Version to 4.6.1 (no changes needed)
+ * Bump debhelper compatibility level to 13
+
+ -- Pirate Praveen Sun, 26 Jun 2022 22:48:20 +0530
+
ruby-asciidoctor-include-ext (0.3.1-2) unstable; urgency=medium
* Team upload
diff -Nru ruby-asciidoctor-include-ext-0.3.1/debian/compat ruby-asciidoctor-include-ext-0.4.0/debian/compat
--- ruby-asciidoctor-include-ext-0.3.1/debian/compat 2019-09-04 13:58:01.0 +0530
+++ ruby-asciidoctor-include-ext-0.4.0/debian/compat 1970-01-01 05:30:00.0 +0530
@@ -1 +0,0 @@
-11
diff -Nru ruby-asciidoctor-include-ext-0.3.1/debian/control ruby-asciidoctor-include-ext-0.4.0/debian/control
--- ruby-asciidoctor-include-ext-0.3.1/debian/control 2019-09-04 13:58:01.0 +0530
+++ ruby-asciidoctor-include-ext-0.4.0/debian/control 2023-03-19 17:22:18.0 +0530
@@ -1,13 +1,13 @@
Source: ruby-asciidoctor-include-ext
Section: ruby
Priority: optional
-Maintainer: Debian Ruby Extras Maintainers
+Maintainer: Debian Ruby Team
Uploaders: Sruthi Chandran
-Build-Depends: debhelper (>= 11~),
+Build-Depends: debhelper-compat (= 13),
gem2deb,
ruby-asciidoctor (<< 3.0.0),
- ruby-asciidoctor (>= 1.5.6)
-Standards-Version: 4.3.0
+ ruby-asciidoctor
+Standards-Version: 4.6.2
Vcs-Git: https://salsa.debian.org/ruby-team/ruby-asciidoctor-include-ext.git
Vcs-Browser: https://salsa.debian.org/ruby-team/ruby-asciidoctor-include-ext
Homepage: https://github.com/jirutka/asciidoctor-include-ext
@@ -18,9 +18,7 @@
Package: ruby-asciidoctor-include-ext
Architecture: all
XB-Ruby-Versions: ${ruby:Versions}
-Depends: ruby | ruby-interpreter,
- ruby-asciidoctor (<< 3.0.0),
- ruby-asciidoctor (>= 1.5.6),
+Depends: ${ruby:Depends},
${misc:Depends},
${shlibs:Depends}
Description: Asciidoctor's standard include::[] processor reimplemented as an extension
diff -Nru ruby-asciidoctor-include-ext-0.3.1/debian/upstream/metadata ruby-asciidoctor-include-ext-0.4.0/debian/upstream/metadata
--- ruby-asciidoctor-include-ext-0.3.1/debian/upstream/metadata 1970-01-01 05:30:00.0 +0530
+++ ruby-asciidoctor-include-ext-0.4.0/debian/upstream/metadata 2023-03-19 17:22:18.0 +0530
@@ -0,0
Processed: Re: Bug#1033194: unblock: ruby-asciidoctor-include-ext/0.4.0-2
Processing control commands: > tags -1 -moreinfo Bug #1033194 [release.debian.org] unblock: ruby-asciidoctor-include-ext/0.4.0-2 Removed tag(s) moreinfo. -- 1033194: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1033194 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems
Processed: Re: Bug#1033194: unblock: ruby-asciidoctor-include-ext/0.4.0-2
Processing control commands: > tags -1 moreinfo Bug #1033194 [release.debian.org] unblock: ruby-asciidoctor-include-ext/0.4.0-2 Added tag(s) moreinfo. -- 1033194: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1033194 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems
Bug#1033194: unblock: ruby-asciidoctor-include-ext/0.4.0-2
Control: tags -1 moreinfo On 2023-03-19 17:48:16 +0530, Pirate Praveen wrote: > Package: release.debian.org > Severity: normal > User: release.debian@packages.debian.org > Usertags: unblock > X-Debbugs-Cc: ruby-asciidoctor-include-...@packages.debian.org > Control: affects -1 + src:ruby-asciidoctor-include-ext > > Please unblock package ruby-asciidoctor-include-ext > > [ Reason ] > This fixes a security issue CVE-2022-24803/#1009035 though it also includes > an upstream update. > This was uploaded to experimental on 2022-06-26 but missed reuploading to > unstable as gitlab was > using the versions directly from experimental (it was uploaded to > experimental to not break the > previos gitlab version before it switched to 0.4 version). Noticed this > today in the rc bug list. > > [ Impact ] > Only reverse dependency is gitlab so it should not impact any other package > in bookworm. > > [ Tests ] > gitlab in experimental was using it already for quite some time (upstream > gitlab tests are fine) > > [ Risks ] > For bookworm it is a leaf package (only used by gitlab which is in > unstable/experimental only) > > [ Checklist ] > [x] all changes are documented in the d/changelog > [x] I reviewed all changes and I approve them > [ ] attach debdiff against the package in testing Please provide a debdiff Cheers > > [ Other info ] > Since it has some other upstream changes, I have not included the debdiff. > > unblock ruby-asciidoctor-include-ext/0.4.0-2 > -- Sebastian Ramacher
Processed: unblock: ruby-asciidoctor-include-ext/0.4.0-2
Processing control commands: > affects -1 + src:ruby-asciidoctor-include-ext Bug #1033194 [release.debian.org] unblock: ruby-asciidoctor-include-ext/0.4.0-2 Added indication that 1033194 affects src:ruby-asciidoctor-include-ext -- 1033194: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1033194 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems
Bug#1033194: unblock: ruby-asciidoctor-include-ext/0.4.0-2
Package: release.debian.org Severity: normal User: release.debian@packages.debian.org Usertags: unblock X-Debbugs-Cc: ruby-asciidoctor-include-...@packages.debian.org Control: affects -1 + src:ruby-asciidoctor-include-ext Please unblock package ruby-asciidoctor-include-ext [ Reason ] This fixes a security issue CVE-2022-24803/#1009035 though it also includes an upstream update. This was uploaded to experimental on 2022-06-26 but missed reuploading to unstable as gitlab was using the versions directly from experimental (it was uploaded to experimental to not break the previos gitlab version before it switched to 0.4 version). Noticed this today in the rc bug list. [ Impact ] Only reverse dependency is gitlab so it should not impact any other package in bookworm. [ Tests ] gitlab in experimental was using it already for quite some time (upstream gitlab tests are fine) [ Risks ] For bookworm it is a leaf package (only used by gitlab which is in unstable/experimental only) [ Checklist ] [x] all changes are documented in the d/changelog [x] I reviewed all changes and I approve them [ ] attach debdiff against the package in testing [ Other info ] Since it has some other upstream changes, I have not included the debdiff. unblock ruby-asciidoctor-include-ext/0.4.0-2
Processed: unblock: girara/0.4.0-1
Processing control commands: > affects -1 + src:girara Bug #1033189 [release.debian.org] unblock: girara/0.4.0-1 Added indication that 1033189 affects src:girara -- 1033189: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1033189 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems
Bug#1033189: unblock: girara/0.4.0-1
Package: release.debian.org
Severity: normal
User: release.debian@packages.debian.org
Usertags: unblock
X-Debbugs-Cc: gir...@packages.debian.org, sramac...@debian.org
Control: affects -1 + src:girara
Please unblock package girara
[ Reason ]
girara in testing suffers from a use-after-free error. The new upstream
release fixes this error and includes no other changes.
[ Impact ]
The use-after-free error remains in testing.
[ Tests ]
The users reporting the issue upstream confirmed that the issue is fixed
with the new upstream version.
[ Risks ]
I am upstream of girara and can prepare fixes for any regressions.
[ Checklist ]
[x] all changes are documented in the d/changelog
[x] I reviewed all changes and I approve them
[x] attach debdiff against the package in testing
unblock girara/0.4.0-1
Cheers
--
Sebastian Ramacher
diff --git a/debian/changelog b/debian/changelog
index beae9c5..4eb7a04 100644
--- a/debian/changelog
+++ b/debian/changelog
@@ -1,3 +1,9 @@
+girara (0.4.0-1) unstable; urgency=medium
+
+ * New upstream version 0.4.0
+
+ -- Sebastian Ramacher Sat, 18 Mar 2023 21:22:26 +0100
+
girara (0.3.9-1) unstable; urgency=medium
* New upstream version 0.3.9
diff --git a/girara/datastructures.c b/girara/datastructures.c
index cfffe00..1a9bbee 100644
--- a/girara/datastructures.c
+++ b/girara/datastructures.c
@@ -457,9 +457,10 @@ girara_node_free(girara_tree_node_t* node)
GNode* childnode = node->node->children;
while (childnode != NULL) {
+GNode* nextnode = childnode->next;
girara_tree_node_data_t* childnodedata = childnode->data;
girara_node_free(childnodedata->node);
-childnode = childnode->next;
+childnode = nextnode;
}
g_node_destroy(node->node);
diff --git a/meson.build b/meson.build
index afb6b91..01dd188 100644
--- a/meson.build
+++ b/meson.build
@@ -1,5 +1,5 @@
project('girara', 'c',
- version: '0.3.9',
+ version: '0.4.0',
meson_version: '>=0.56',
default_options: ['c_std=c11', 'warning_level=3'],
)
Bug#1033188: unblock: thunderbird/1:102.9.0-1
Package: release.debian.org Severity: normal User: release.debian@packages.debian.org Usertags: unblock X-Debbugs-Cc: thunderb...@packages.debian.org Control: affects -1 + src:thunderbird Please unblock package thunderbird [ Reason ] A new upstream release of the Thunderbird ESR series did happen that fixes a few CVE vulnerabilities. [ Impact ] Debian testing/bullseye would stick with version 102.8.0. [ Tests ] Even if the autopkgtests are marked superficial the main test did show that Thunbderbird is able to start and is picking up the global settings from /etc/thunderbird. Besides that I tested the new version a lot on alocal basis. [ Risks ] We are in the middle of the ESR releases and upstream change are now a lot less deep and agressive than on a start of a new ESR series. stable-security and also oldstable-security already are using 102.9.0 as actual version. [ Checklist ] [x] all changes are documented in the d/changelog [x] I reviewed all changes and I approve them [x] attach debdiff against the package in testing (only for the debian/folder) [ Other info ] The modifications for the source are quite big as usual but are going in parallel with firefox-esr due the same sorce code base. Please see further down for a diff of the chnages on the debian side. Basically only the Standards-Version was changed. unblock thunderbird/1:102.9.0-1 $ git diff debian/1%102.8.0-1 debian/ diff --git a/debian/changelog b/debian/changelog index b1c0dd97102..340fa97407c 100644 --- a/debian/changelog +++ b/debian/changelog @@ -1,3 +1,18 @@ +thunderbird (1:102.9.0-1) unstable; urgency=medium + + * [ad8cc7c] New upstream version 102.9.0 +Fixed CVE issues in upstream version 102.9 (MFSA 2023-11): +CVE-2023-25751: Incorrect code generation during JIT compilation +CVE-2023-28164: URL being dragged from a removed cross-origin iframe +into the same tab triggered navigation +CVE-2023-28162: Invalid downcast in Worklets +CVE-2023-25752: Potential out-of-bounds when accessing throttled streams +CVE-2023-28176: Memory safety bugs fixed in Thunderbird 102.9 + * [b0a22c0] d/control: Increase Standards-Version to 4.6.2 +No further changes needed. + + -- Carsten Schoenert Wed, 15 Mar 2023 19:54:53 +0100 + thunderbird (1:102.8.0-1) unstable; urgency=medium * [b130936] New upstream version 102.8.0 diff --git a/debian/control b/debian/control index 13c0245e0c8..7f30678cab7 100644 --- a/debian/control +++ b/debian/control @@ -60,7 +60,7 @@ Vcs-Git: https://salsa.debian.org/mozilla-team/thunderbird.git -b debian/sid Vcs-Browser: https://salsa.debian.org/mozilla-team/thunderbird/commits/debian/sid/ Homepage: https://www.thunderbird.net/ X-Debian-Homepage: http://wiki.debian.org/Thunderbird -Standards-Version: 4.6.1 +Standards-Version: 4.6.2 Package: thunderbird Architecture: amd64 arm64 i386 mips64el ppc64el s390x ppc64
Processed: unblock: thunderbird/1:102.9.0-1
Processing control commands: > affects -1 + src:thunderbird Bug #1033188 [release.debian.org] unblock: thunderbird/1:102.9.0-1 Added indication that 1033188 affects src:thunderbird -- 1033188: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1033188 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems
Re: 11.7 planning
Will help out the 29th April :) On 3/18/23, Jonathan Wiltshire wrote: > On Wed, Mar 15, 2023 at 08:33:47PM +, Jonathan Wiltshire wrote: >> We're overdue for 11.7 and need it done with a keyring update included >> before bookworm can be released. The wheels are turning on the keyring so >> how do dates in April look for everybody? Saturdays are 1st (probably too >> soon), 8th, 15th, 22nd and 29th. > > So 29th April is the earliest viable option; announcements to follow. > > -- > Jonathan Wiltshire j...@debian.org > Debian Developer http://people.debian.org/~jmw > > 4096R: 0xD3524C51 / 0A55 B7C5 1223 3942 86EC 74C3 5394 479D D352 4C51 > ed25519/0x196418AAEB74C8A1: CA619D65A72A7BADFC96D280196418AAEB74C8A1 > >
Processed: unblock: flask-security/5.1.2-1
Processing control commands: > affects -1 + src:flask-security Bug #1033185 [release.debian.org] unblock: flask-security/5.1.2-1 Added indication that 1033185 affects src:flask-security -- 1033185: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1033185 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems
