Bug#1031377: UDD/lintian: Needs to run lintian on all binaries generated from same source

[Paul Wise]

On Thu, 16 Feb 2023 15:05:24 +0100 Lucas Nussbaum wrote:

> What could work is:
>   run lintian on source
>   for each arch in the packages's architectures (except all)
>  run lintian on architecture packages + architecture 'all' packages
> 
> But would that solve all issues?

I discovered that it does not solve all issues.

For example src:rust-bat builds bat. When you run lintian against the
dsc and the deb it emits missing-notice-file-for-apache-license for the
source package, but when you run it against only the dsc or only the
deb it does not emit that tag. That is because the test checks that the
NOTICE file from the source package is missing from the binary package.

https://lists.debian.org/msgid-search/8062de5e3a1afbe988ce3d5453d211089242ba2a.ca...@debian.org

-- 
bye,
pabs

https://wiki.debian.org/PaulWise


signature.asc
Description: This is a digitally signed message part

Bug#1053101: qemu-user-static: segfault when running ldd/arm64 on certain arm64 binaries

[Michael Tokarev]

Control: tag -1 + confirmed
Control: found -1 1:8.1.0+ds-6

27.09.2023 16:04, Andreas Beckmann:


# /lib/ld-linux-aarch64.so.1 --verify /usr/bin/aarch64-linux-gnu-g++-13
Segmentation fault


Ok, I can reproduce this one, which is good!
And the same issue is also present in 8.1.0 and 8.1.1.  Sigh.

/mjt

Bug#1051910: mirror submission for ossmirror.mycloud.services

[OSSMirror@OnboardCloud]

Hi Adam, Thanks for sharing. Looks like we are almost near the ½ way mark to reaching 50 points today. Separately, we have written in to mirr...@debian.org on 14/9 to ask about hosting official “.country.” mirrors but did not receive any reply till date. Do you know if we have written to the correct address or are you able to refer us to the correct party to discuss/review this? Best regards, -Original Message-From: Adam D. Barratt Date: Tuesday, 26 September 2023 at 1:54 AMTo: OSSMirror@OnboardCloud Cc: 1051...@bugs.debian.org <1051...@bugs.debian.org>Subject: Re: Bug#1051910: mirror submission for ossmirror.mycloud.servicesHi, The published list is generated by an automated process that checks onthe status of the mirror in recent days. You can see the current statusof your mirror at https://mirror-master.debian.org/status/mirror-info/ossmirror.mycloud.services.html The score needs to reach at least 50 currently before the automationwill consider including it. Regards, Adam On Mon, 2023-09-25 at 09:52 +0800, OSSMirror@OnboardCloud wrote:> Hi Adam,>  > We were looking at the mirror listing and our mirror does not seem to> have been listed yet.>  > https://www.debian.org/mirror/list-full#SG>  >  > May I enquire do you know roughly how long does it take for the> mirror to be listed?>  > Best regards,>  > -Original Message-> From: OSSMirror@OnboardCloud > Date: Sunday, 24 September 2023 at 3:31 AM> To: Adam D. Barratt > Cc: 1051...@bugs.debian.org <1051...@bugs.debian.org>> Subject: Re: Bug#1051910: mirror submission for> ossmirror.mycloud.services> > Thanks Adam for the clarification and kind assistance!>  > On 24 Sep 2023, at 2:56 AM, Adam D. Barratt  > wrote:>  > On Sun, 2023-09-24 at 01:57 +0800, OSSMirror@OnboardCloud wrote:> > Hi Adam,> >> > Thanks for the reply. Could you elaborate further what do you mean> as> > the /debian/ works:> >> > http://ossmirror.mycloud.services/debian/> >>  > Ah, right - I was mislead by the index of> http://ossmirror.mycloud.services implying that only /os/ existed,> and> didn't check for an alias.>  > Regards,>  > Adam>  >  >  

Bug#1051752: [pkg-uWSGI-devel] Bug#1051752: uwsgi: remove uwsgi-plugin-glusterfs on 32 bit architectures)

[Jonas Smedegaard]

Quoting Alexandre Rossi (2023-09-27 20:53:14)
> > > If I get some advice on the best practrices for having d/control.in with
> > > template variables, I would be happy to work on this.
> > 
> > I assume you mean the debian/control file (as the uwsgi source package
> > currently contains no debian/control.in file).
> > That file gets mangled when the following command is executed:
> > 
> >   DEB_MAINTAINER_MODE=1 debian/control clean
> 
> I thought that using some template engine and introducing d/control.in
> would be easier to maintain, debug than the current mangling and was wondering
> what was considered good practice for this in Debian packaging.
> 
> I'll research.
> 
> Thanks for the upload,

Historically the package used a debian/control.in file.  That made other
Debian developers nervous, thinking that if they didn't understand that,
they were unable to help out with other unrelated aspects of package
maintenance - despite my adding a note in debian/README.source
explicitly stating the opppsite.  So I consider that a failed
experiment.

But I am open to suggestions on how this could be done more elegantly -
just please let's discuss it *before* you mess around structurally with
the package :-)

(I do *not* consider current packaging style ideal - for starters, I
want to migrate away from using CDBS, but it is a complex package so I
want to do it cautiously - and am not really in a hurry about that...)


 - Jonas

-- 
 * Jonas Smedegaard - idealist & Internet-arkitekt
 * Tlf.: +45 40843136  Website: http://dr.jones.dk/
 * Sponsorship: https://ko-fi.com/drjones

 [x] quote me freely  [ ] ask before reusing  [ ] keep private

signature.asc
Description: signature

Bug#1053120: linux-image-6.1.0-12-amd64: Kernel NULL pointer deref with XFS on kernel 6.1

[Salvatore Bonaccorso]

Hi,

On Wed, Sep 27, 2023 at 04:03:56PM -0500, sb56...@gmail.com wrote:
> On 9/27/23 14:29, Salvatore Bonaccorso wrote:
> 
> > Thanks for the report. This should be fixed upstream 6.1.53 and
> > pending now for the next upload for bookworm.
> 
> Hi Salvatore, thanks a lot for the fast reply!
> So do you think that the bug I reported with XFS is the same as the
> fix being implemented upstream? Will the next upload for Bookworm
> come soon?

If not please then reopen, but the traces looks similar enough.

The next upload to bookworm is scheduled for the 7th October for next
point release, which will contain a rebase to 6.1.55.

Regards,
Salvatore

Bug#1053142: chromium cannot startup after libfreetype6 upgrade to 2.12.1+dfsg-5+deb12u1

[SuperCat]

Package: chromium
Version: 117.0.5938.62-1~deb12u1
Severity: grave
Justification: renders package unusable

Dear Maintainer,

chromium cannot startup after libfreetype6 upgrade to 2.12.1+dfsg-5+deb12u1.

In the latest changes of libfreetype6, macro PUT_COLOR_LAYERS_V1 was set to
NULL pointer, which would make function FT_Get_Color_Glyph_Paint() become an
invalid function. SkScalerContext_FreeType::generateMetrics() will call
FT_Get_Color_Glyph_Paint() when chromium starts up.

Backtrace:
Core was generated by `/usr/lib/chromium/chromium 
--show-component-extension-

options --ignore-gpu-blac'.
Program terminated with signal SIGSEGV, Segmentation fault.
#0 0x in ?? ()
[Current thread is 1 (Thread 0x7f849a4530c0 (LWP 1450075))]
(gdb) bt
#0 0x in ()
#1 0x55b7eea342d4 in SkScalerContext_FreeType::generateMetrics(SkGlyph*,
SkArenaAlloc*) ()
#2 0x55b7ea18af08 in SkScalerContext::internalMakeGlyph(SkPackedGlyphID,
SkMask::Format, SkArenaAlloc*) ()
#3 0x55b7ea18ae85 in SkScalerContext::makeGlyph(SkPackedGlyphID,
SkArenaAlloc*) ()
#4 0x55b7ea1a2f7a in SkStrike::digestFor(skglyph::ActionType,
SkPackedGlyphID) ()
#5 0x55b7ea1a22b3 in SkStrike::metrics(SkSpan,
SkGlyph const**) ()
#6 0x55b7ea10a727 in SkFont::getWidthsBounds(unsigned short const*, int,
float*, SkRect*, SkPaint const*) const ()
#7 0x55b7ef4ed573 in gfx::(anonymous
namespace)::GetGlyphHorizontalAdvance(hb_font_t*, void*, unsigned int, 
void*)

()
#8 0x55b7ea2b70d2 in hb_font_get_glyph_h_advances_default(hb_font_t*,
void*, unsigned int, unsigned int const*, unsigned int, int*, unsigned int,
void*)
()
#9 0x55b7ea2fba2f in _hb_ot_shape ()
#10 0x55b7ea314cbf in hb_shape_plan_execute ()
#11 0x55b7ea315095 in hb_shape_full ()
#12 0x55b7ef4e0740 in
gfx::RenderTextHarfBuzz::ShapeRunsWithFont(std::__cxx11::basic_stringstd::char_traits, std::allocator >--Type  for 
more, q

to quit, c to continue without paging--
const&, gfx::internal::TextRunHarfBuzz::FontParams const&,
std::vector >*,
std::vector >*) ()
#13 0x55b7ef4de5a1 in
gfx::RenderTextHarfBuzz::ShapeRuns(std::__cxx11::basic_string, std::allocator > const&,
gfx::internal::TextRunHarfBuzz::FontParams const&,
std::vector >) ()
#14 0x55b7ef4dc343 in
gfx::RenderTextHarfBuzz::ItemizeAndShapeText(std::__cxx11::basic_string, std::allocator > const&,
gfx::internal::TextRunList*) ()
#15 0x55b7ef4d9de5 in gfx::RenderTextHarfBuzz::EnsureLayoutRunList() ()
#16 0x55b7ef4db289 in gfx::RenderTextHarfBuzz::EnsureLayout() ()
#17 0x55b7ef4cebcd in 
gfx::RenderText::GetCursorBounds(gfx::SelectionModel

const&, bool) ()
#18 0x55b7ef4d1a47 in gfx::RenderText::UpdateCachedBoundsAndOffset() ()
#19 0x55b7ef4d19ee in gfx::RenderText::GetUpdatedCursorBounds() ()
#20 0x55b7f12a422f in views::Textfield::Scroll(std::vectorlong,

std::allocator > const&) ()
#21 0x55b7f3b65a94 in
OmniboxViewViews::SetTextAndSelectedRanges(std::__cxx11::basic_string, std::allocator > const&,
std::vector > const&) ()
#22 0x55b7f3b65ce1 in
OmniboxViewViews::SetWindowTextAndCaretPos(std::__cxx1--Type  for 
more, q

to quit, c to continue without paging--
1::basic_string, 
std::allocator

> const&, unsigned long, bool, bool) ()
#23 0x55b7f3707750 in OmniboxEditModel::Revert() ()
#24 0x55b7f3703da1 in OmniboxView::RevertAll() ()
#25 0x55b7f3b64d83 in OmniboxViewViews::Update() ()
#26 0x55b7f3b2fa44 in LocationBarView::Update(content::WebContents*) ()
#27 0x55b7f3b2f421 in LocationBarView::Init() ()
#28 0x55b7f3d34ba6 in ToolbarView::Init() ()
#29 0x55b7f3a6533e in BrowserView::AddedToWidget() ()
#30 0x55b7f12e1eeb in
views::View::PropagateAddNotifications(views::ViewHierarchyChangedDetails
const&, bool) ()
#31 0x55b7f12e16c8 in views::View::AddChildViewAtImpl(views::View*,
unsigned long) ()
#32 0x55b7f130de5b in
views::NonClientView::ViewHierarchyChanged(views::ViewHierarchyChangedDetails
const&) ()
#33 0x55b7f12e1b8d in
views::View::ViewHierarchyChangedImpl(views::ViewHierarchyChangedDetails
const&) ()
#34 0x55b7f12e1ed2 in
views::View::PropagateAddNotifications(views::ViewHierarchyChangedDetails
const&, bool) ()
#35 0x55b7f12e16c8 in views::View::AddChildViewAtImpl(views::View*,
unsigned long) ()
#36 0x55b7f12f3105 in views::Widget::Init(views::Widget::InitParams) ()
#37 0x55b7f3a57071 in BrowserFrame::InitBrowserFrame() ()
--Type  for more, q to quit, c to continue without paging--
#38 0x55b7f3aeb052 in
BrowserWindow::CreateBrowserWindow(std::unique_ptr >, bool, bool) ()
#39 0x55b7f37510b4 in Browser::Browser(Browser::CreateParams const&) ()
#40 0x55b7f37506df in Browser::Create(Browser::CreateParams const&) ()
#41 0x55b7f37d4dd7 in
StartupBrowserCreatorImpl::OpenTabsInBrowser(Browser*,
chrome::startup::IsProcessStartup, std::vector > const&) ()
#42 0x55b7f37d5dff in
StartupBrowserCreatorImpl::RestoreOrCreateBrowser(std::vector > const&,

Bug#1052624: debbugs: forwarded messages break DMARC, DKIM, SPF

[Don Armstrong]

Control: reassign -1 bugs.debian.org
Cotnrol: forcemerge 830865 754809 -1

On Mon, 25 Sep 2023, Jonathan Kamens wrote:
> The most obvious solution to this is straightforward: the From line in
> these messages should be modified to contain the email address of the
> bug, not the email address of the original sender. The original
> sender's address can be put in Reply-To and/or indicated in the header
> in a number of other ways. For example, sometimes something like this
> is done:

The problem with this specific From-rewriting is that it breaks replying
to the sender instead of just the bug (though maybe that's not a huge
deal).

Ideally we'd be able to oversign the messages, but DMARC and DKIM
weren't engineered to allow that. I've personally been ignoring it
because I've been hoping that the standards would get fixed, but if it's
impacting enough Debian contributors to matter, I don't mind accepting a
patch.

-- 
Don Armstrong  https://www.donarmstrong.com

It was said that life was cheap in Ankh-Morpork. This was, of course,
completely wrong. Life was often very expensive; you could get death
for free.
 -- Terry Pratchet _Pyramids_ p25

Bug#1053088: Modify changelog message

[tony mancill]

On Wed, Sep 27, 2023 at 05:38:42PM +0800, panxuefeng wrote:
> Package: service-wrapper-java
> Version: 3.5.51
> Severity: wishlist
> Tags: patch
> User: debian-de...@lists.debian.org
> Usertags: loongarch64
> 
> Dear Maintainers,
> 
> I adjust unstable to unreleased in debian/changelog in
> LoongArch-support-v3.patch.
 
Hello Xuefeng Pan,

Thank you for the updated patch.  I have applied it and uploaded a new
package revision to the archive.

Cheers,
tony


signature.asc
Description: PGP signature

Bug#1053141: bookworm-pu: package mrtg/2.17.10-5+deb12u2

[Joao Eriberto Mota Filho]

Package: release.debian.org
Severity: normal
Tags: bookworm
User: release.debian@packages.debian.org
Usertags: pu
X-Debbugs-Cc: m...@packages.debian.org
Control: affects -1 + src:mrtg

[ Reason ]
The last SPU was broken by #1041332. This new SPU fixes the issue using a new
approach. Now a debconf message is used to warn the user about a change of the
configuration place.

[ Impact ]
The impact is the final user will not know the new place of the configuration
file. Consequently, the mrtg will not use the configuration parameters created
by the user before the last upgrade (from Bullseye to Bookworm).

[ Tests ]
Several tests were made to make sure that a warning will be shown when needed.

[ Risks ]
No risks because this is only a debconf warning for the user.

[ 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 (old)stable
  [x] the issue is verified as fixed in unstable

[ Changes ]
In 2.17.10-5+deb12u1 the confile was moved from /etc/ to /etc/mrtg/ via a
debconf process. This process was cancelled and, now, the user will receive
a warning telling that is needed to move this file manually. Consequently,
the Debian Policy 10.7.3 is being honored.

[ Other info ]
No more info.

Regards,

Eriberto
diff -Nru mrtg-2.17.10/debian/changelog mrtg-2.17.10/debian/changelog
--- mrtg-2.17.10/debian/changelog   2023-07-10 14:04:14.0 -0300
+++ mrtg-2.17.10/debian/changelog   2023-09-27 22:59:14.0 -0300
@@ -1,3 +1,24 @@
+mrtg (2.17.10-5+deb12u2) bookworm; urgency=medium
+
+  * Changed a debconf template to honor Debian Policy (10.7.3), not
+changing the place a conffile, discarding any user changes.
+Thanks to Andreas Beckmann . Consequently:
+  - debian/mrtg.config: changed a comment.
+  - debian/mrtg.postinst: dropped the first conditional block,
+related to moving the /etc/mrtg.cfg to /etc/mrtg/.
+  - debian/mrtg.templates: updated to show a specific message to
+users.
+  - debian/po/: ran debconf-updatepo to update all templates.
+  - Closes: #1039103, #1041332
+  * debian/po/:
+  - mrtg.templates: reviewed all messages. Thanks to Justin B Rye
+ for all help in debian-l10n-english
+list and to Jonathan Wiltshire  for the suggestion
+to ask for help in that list.
+  - Updated all translations. Thanks to all translators.
+
+ -- Joao Eriberto Mota Filho   Wed, 27 Sep 2023 22:59:14 
-0300
+
 mrtg (2.17.10-5+deb12u1) bookworm; urgency=medium
 
   * Added a debconf dialog to allow the user to decide if /etc/mrtg.cfg must
diff -Nru mrtg-2.17.10/debian/mrtg.config mrtg-2.17.10/debian/mrtg.config
--- mrtg-2.17.10/debian/mrtg.config 2023-07-10 14:04:14.0 -0300
+++ mrtg-2.17.10/debian/mrtg.config 2023-09-24 11:26:07.0 -0300
@@ -7,7 +7,7 @@
 # Source debconf library.
 . /usr/share/debconf/confmodule
 
-# Move /etc/mrtg.cfg to /etc/mrtg/mrtg.cfg?
+# /etc/mrtg.cfg should be moved to /etc/mrtg/mrtg.cfg
 if [ -e /etc/mrtg.cfg ]
 then
 db_input high mrtg/move_config_file || true
diff -Nru mrtg-2.17.10/debian/mrtg.postinst mrtg-2.17.10/debian/mrtg.postinst
--- mrtg-2.17.10/debian/mrtg.postinst   2023-07-10 14:04:14.0 -0300
+++ mrtg-2.17.10/debian/mrtg.postinst   2023-09-24 11:26:07.0 -0300
@@ -28,17 +28,6 @@
 
 if [ "$1" = "configure" ]
 then
-# Move /etc/mrtg.cfg to /etc/mrtg/mrtg.cfg?
-db_get mrtg/move_config_file || RET="false"
-if [ "$RET" = "true" ]
-then
-   if [ -e /etc/mrtg/mrtg.cfg ]
-   then
-  mv /etc/mrtg/mrtg.cfg /etc/mrtg/mrtg.cfg.NEW
-   fi
-   mv -f /etc/mrtg.cfg /etc/mrtg/
-fi
-
 # Fix owner, group and permissions for /var/www/html/mrtg/?
 db_get mrtg/fix_permissions || RET="false"
 if [ "$RET" = "true" ]
diff -Nru mrtg-2.17.10/debian/mrtg.templates mrtg-2.17.10/debian/mrtg.templates
--- mrtg-2.17.10/debian/mrtg.templates  2023-07-10 14:04:14.0 -0300
+++ mrtg-2.17.10/debian/mrtg.templates  2023-09-24 11:26:07.0 -0300
@@ -1,44 +1,41 @@
 Template: mrtg/move_config_file
-Type: boolean
-Default: true
-_Description: Move /etc/mrtg.cfg to /etc/mrtg/mrtg.cfg?
- Older versions of the MRTG on Debian had the /etc/mrtg.cfg configuration
- file. Currently, this file is located in /etc/mrtg/ directory, but there
- is a /etc/mrtg.cfg.
+Type: note
+_Description: /etc/mrtg.cfg should be moved to /etc/mrtg/mrtg.cfg
+ Older versions of MRTG on Debian had the configuration file /etc/mrtg.cfg.
+ The new version reads from /etc/mrtg/mrtg.cfg instead, so MRTG will not
+ work correctly until you move your configuration across manually.
 
 Template: mrtg/fix_permissions
 Type: boolean
 Default: true
 _Description: Fix owner, group and permissions for /var/www/html/mrtg?
- By default MRTG writes all graphics in /var/www/html/mrtg/ directory. This
- directory is present at this moment, but it is insecure. Is needed to 

Bug#1052824: flycheck: FTBFS if gawk is installed

[Manphiz]

control: tags -1 pending
thanks

Manphiz  writes:

> control: tag -1 patch
> thanks
>
> Gianfranco Costamagna  writes:
>
>> Source: flycheck
>> Version: 33~git20230824.e56e30d-1
>> Severity: serious
>> Forwarded: https://github.com/flycheck/flycheck/issues/2036
>>
>> Hello, looks like if we build with gawk installed, a new test fails.
>>
>> I'm filing as serious, because gawk is a tool installed on many systems.
>>
>> I just added the dependency at build time and found the issue on DoM
>> http://debomatic-amd64.debian.net/distribution#unstable/flycheck/33~git20230824.e56e30d-1.1/buildlog
>>
>>
>> Test flycheck-define-checker/awk-gawk/syntax-error backtrace:
>>   signal(ert-test-failed (((should (equal (mapcar #'flycheck-error-wit
>>   ert-fail(((should (equal (mapcar #'flycheck-error-without-group expe
>>   (if (unwind-protect (setq value-229 (apply fn-227 args-228)) (setq f
>>   (let (form-description-231) (if (unwind-protect (setq value-229 (app
>>   (let ((value-229 'ert-form-evaluation-aborted-230)) (let (form-descr
>>   (let* ((fn-227 #'equal) (args-228 (condition-case err (let ((signal-
>>   (let ((expected (flycheck-ert-sort-errors (mapcar (apply-partially #
>>   flycheck-ert-should-errors((2 nil warning "x=|\n  ^ syntax error" :c
>>   apply(flycheck-ert-should-errors (2 nil warning "x=|\n  ^ syntax err
>>   (let ((process-hook-called 0) (suspicious nil)) (add-hook 'flycheck-
>>   flycheck-ert-should-syntax-check-in-buffer((2 nil warning "x=|\n  ^
>>   apply(flycheck-ert-should-syntax-check-in-buffer (2 nil warning "x=|
>>   (progn (insert-file-contents file-name 'visit) (set-visited-file-nam
>>   (unwind-protect (progn (insert-file-contents file-name 'visit) (set-
>>   (progn (unwind-protect (progn (insert-file-contents file-name 'visit
>>   (unwind-protect (progn (unwind-protect (progn (insert-file-contents
>>   (save-current-buffer (set-buffer temp-buffer) (unwind-protect (progn
>>   (let ((temp-buffer (generate-new-buffer " *temp*" t))) (save-current
>>   (let ((file-name (flycheck-ert-resource-filename resource-file))) (i
>>   (let ((mode (car tail))) (if (fboundp mode) nil (ert-skip (format "%
>>   (while tail (let ((mode (car tail))) (if (fboundp mode) nil (ert-ski
>>   (let ((tail modes)) (while tail (let ((mode (car tail))) (if (fbound
>>   flycheck-ert-should-syntax-check("language/awk/syntax-error.awk" awk
>>   (closure (truncated-stdin-mode-abbrev-table truncated-stdin-mode-syn
>>   ert--run-test-internal(#s(ert--test-execution-info :test #s(ert-test
>>   ert-run-test(#s(ert-test :name flycheck-define-checker/awk-gawk/synt
>>   ert-run-or-rerun-test(#s(ert--stats :selector ... :tests ... :test-m
>>   ert-run-tests((and "flycheck-" t) #f(compiled-function (event-type &
>>   ert-run-tests-batch((and "flycheck-" t))
>>   ert-run-tests-batch-and-exit((and "flycheck-" t))
>>   (let ((selector (car-safe (prog1 argv (setq argv (cdr argv)) (if
>>   flycheck-run-tests-batch-and-exit()
>>   (let ((debug-on-error t)) (flycheck-run-tests-batch-and-exit))
>>   (let* ((load-prefer-newer t) (source-directory (locate-dominating-fi
>>   flycheck-run-tests-main()
>>   load-with-code-conversion("/<>/flycheck-33~git202
>>   command-line-1(("-l" "package" "--eval" "(add-to-list 'package-direc
>>   command-line()
>>   normal-top-level()
>> Test flycheck-define-checker/awk-gawk/syntax-error condition:
>> (ert-test-failed
>>  ((should
>>(equal
>>  (mapcar #'flycheck-error-without-group expected)
>>  (mapcar #'flycheck-error-without-group current)))
>>   :form
>>   (equal
>>(#s(flycheck-error # awk-gawk 
>> "/<>/test/resources/language/awk/syntax-error.awk" 2 nil "x=|\n 
>>  ^ syntax error" warning nil nil nil nil))
>>nil)
>>   :value nil :explanation
>>   (different-types
>>(#s(flycheck-error # awk-gawk 
>> "/<>/test/resources/language/awk/syntax-error.awk" 2 nil "x=|\n 
>>  ^ syntax error" warning nil nil nil nil))
>>nil)))
>>FAILED  110/562  flycheck-define-checker/awk-gawk/syntax-error (0.139626 
>> sec) at test/flycheck-test.el:1
>>
>> We are already skipping a bunch of tests in a patch, so maybe we can add 
>> also this one, or wait for upstream
>> to double check what is going wrong.
>>
>> G.
>>
>
> Looks like the best action here is to mark this test as flaky as well.
>
> Unfortunately I don't seem to have permission to push to
> emacsen-team/flycheck yet, so I've prepared a merge request[1] instead.
> Looking for sponsorship :)
>
> [1] https://salsa.debian.org/emacsen-team/flycheck/-/merge_requests/4

Finally got access from David.  I have prepared a revision for the fix
and uploaded to mentors[1].  Now looking for sponsors :)

[1] https://mentors.debian.net/package/flycheck/

-- 
Manphiz


signature.asc
Description: PGP signature

Bug#1051543: grub2: Fails to load normal.mod from a XFS v5 parition.

[Jon DeVree]

On Fri, Sep 15, 2023 at 23:43:28 +0200, Sebastian Andrzej Siewior wrote:
> > there's now a patch from Jon DeVree upstream, which might fix this for
> > you. Is it possible for you to test his patch?
> > 
> > https://lists.gnu.org/archive/html/grub-devel/2023-09/msg00059.html
> 
> Yes it sovles the issue, the box boots.
> 

I posted an updated v3 version of the patch:

https://lists.gnu.org/archive/html/grub-devel/2023-09/msg00110.html

-- 
Jon
Doge Wrangler
X(7): A program for managing terminal windows. See also screen(1) and tmux(1).

Bug#1053140: xtensor: armel failure with clang-16: undefined reference to `__atomic_store_1'

[Drew Parsons]

Source: xtensor
Version: 0.24.7-1
Severity: normal
Control: forwarded -1 https://github.com/xtensor-stack/xtensor/issues/2729

xtensor 0.24.7-1 fails debci test on armel (gnueabi) architecture with clang 
16.0.6.
The tests pass with g++ 13.2.0, and pass with clang-16 on other architectures.
A test log is found at 
https://ci.debian.net/data/autopkgtest/unstable/armel/x/xtensor/38202370/log.gz
see also https://ci.debian.net/packages/x/xtensor/unstable/armel/

Except of the test log is

520s [100%] Linking CXX executable test_xtensor_lib
520s /usr/bin/cmake -E cmake_link_script 
CMakeFiles/test_xtensor_lib.dir/link.txt --verbose=1
520s /usr/bin/clang++  -DXSIMD_ENABLE_XTL_COMPLEX=1 -std=c++14 
-Wunused-parameter -Wextra -Wreorder -Wconversion -Wsign-conversion 
-Wold-style-cast -Wunused-variable -O3 -DNDEBUG -rdynamic 
CMakeFiles/test_xtensor_lib.dir/main.cpp.o 
CMakeFiles/test_xtensor_lib.dir/test_xadaptor_semantic.cpp.o 
CMakeFiles/test_xtensor_lib.dir/test_xarray_adaptor.cpp.o 
CMakeFiles/test_xtensor_lib.dir/test_xarray.cpp.o 
CMakeFiles/test_xtensor_lib.dir/test_xblockwise_reducer.cpp.o 
CMakeFiles/test_xtensor_lib.dir/test_xbroadcast.cpp.o 
CMakeFiles/test_xtensor_lib.dir/test_xbuilder.cpp.o 
CMakeFiles/test_xtensor_lib.dir/test_xcontainer_semantic.cpp.o 
CMakeFiles/test_xtensor_lib.dir/test_xeval.cpp.o 
CMakeFiles/test_xtensor_lib.dir/test_xexception.cpp.o 
CMakeFiles/test_xtensor_lib.dir/test_xexpression.cpp.o 
CMakeFiles/test_xtensor_lib.dir/test_xexpression_traits.cpp.o 
CMakeFiles/test_xtensor_lib.dir/test_xfunction.cpp.o 
CMakeFiles/test_xtensor_lib.dir/test_xfunc_on_xexpression.cpp.o 
CMakeFiles/test_xtensor_lib.dir/test_xmultiindex_iterator.cpp.o 
CMakeFiles/test_xtensor_lib.dir/test_xiterator.cpp.o 
CMakeFiles/test_xtensor_lib.dir/test_xmath.cpp.o 
CMakeFiles/test_xtensor_lib.dir/test_xoperation.cpp.o 
CMakeFiles/test_xtensor_lib.dir/test_xoptional_assembly.cpp.o 
CMakeFiles/test_xtensor_lib.dir/test_xreducer.cpp.o 
CMakeFiles/test_xtensor_lib.dir/test_xscalar.cpp.o 
CMakeFiles/test_xtensor_lib.dir/test_xscalar_semantic.cpp.o 
CMakeFiles/test_xtensor_lib.dir/test_xshape.cpp.o 
CMakeFiles/test_xtensor_lib.dir/test_xstorage.cpp.o 
CMakeFiles/test_xtensor_lib.dir/test_xstrided_view.cpp.o 
CMakeFiles/test_xtensor_lib.dir/test_xstrides.cpp.o 
CMakeFiles/test_xtensor_lib.dir/test_xtensor.cpp.o 
CMakeFiles/test_xtensor_lib.dir/test_xtensor_adaptor.cpp.o 
CMakeFiles/test_xtensor_lib.dir/test_xtensor_semantic.cpp.o 
CMakeFiles/test_xtensor_lib.dir/test_xview.cpp.o 
CMakeFiles/test_xtensor_lib.dir/test_xview_semantic.cpp.o 
CMakeFiles/test_xtensor_lib.dir/test_xutils.cpp.o 
CMakeFiles/test_xtensor_lib.dir/test_xsimd8.cpp.o 
CMakeFiles/test_xtensor_lib.dir/test_xaccumulator.cpp.o 
CMakeFiles/test_xtensor_lib.dir/test_xadapt.cpp.o 
CMakeFiles/test_xtensor_lib.dir/test_strided_assign.cpp.o 
CMakeFiles/test_xtensor_lib.dir/test_xassign.cpp.o 
CMakeFiles/test_xtensor_lib.dir/test_xaxis_iterator.cpp.o 
CMakeFiles/test_xtensor_lib.dir/test_xaxis_slice_iterator.cpp.o 
CMakeFiles/test_xtensor_lib.dir/test_xbuffer_adaptor.cpp.o 
CMakeFiles/test_xtensor_lib.dir/test_xchunked_array.cpp.o 
CMakeFiles/test_xtensor_lib.dir/test_xchunked_view.cpp.o 
CMakeFiles/test_xtensor_lib.dir/test_xcomplex.cpp.o 
CMakeFiles/test_xtensor_lib.dir/test_xcsv.cpp.o 
CMakeFiles/test_xtensor_lib.dir/test_xdatesupport.cpp.o 
CMakeFiles/test_xtensor_lib.dir/test_xdynamic_view.cpp.o 
CMakeFiles/test_xtensor_lib.dir/test_xfunctor_adaptor.cpp.o 
CMakeFiles/test_xtensor_lib.dir/test_xfixed.cpp.o 
CMakeFiles/test_xtensor_lib.dir/test_xhistogram.cpp.o 
CMakeFiles/test_xtensor_lib.dir/test_xpad.cpp.o 
CMakeFiles/test_xtensor_lib.dir/test_xindex_view.cpp.o 
CMakeFiles/test_xtensor_lib.dir/test_xio.cpp.o 
CMakeFiles/test_xtensor_lib.dir/test_xlayout.cpp.o 
CMakeFiles/test_xtensor_lib.dir/test_xmanipulation.cpp.o 
CMakeFiles/test_xtensor_lib.dir/test_xmasked_view.cpp.o 
CMakeFiles/test_xtensor_lib.dir/test_xmath_result_type.cpp.o 
CMakeFiles/test_xtensor_lib.dir/test_xnan_functions.cpp.o 
CMakeFiles/test_xtensor_lib.dir/test_xnoalias.cpp.o 
CMakeFiles/test_xtensor_lib.dir/test_xnorm.cpp.o 
CMakeFiles/test_xtensor_lib.dir/test_xoptional.cpp.o 
CMakeFiles/test_xtensor_lib.dir/test_xoptional_assembly_adaptor.cpp.o 
CMakeFiles/test_xtensor_lib.dir/test_xoptional_assembly_storage.cpp.o 
CMakeFiles/test_xtensor_lib.dir/test_xset_operation.cpp.o 
CMakeFiles/test_xtensor_lib.dir/test_xrandom.cpp.o 
CMakeFiles/test_xtensor_lib.dir/test_xrepeat.cpp.o 
CMakeFiles/test_xtensor_lib.dir/test_xsort.cpp.o 
CMakeFiles/test_xtensor_lib.dir/test_xsimd.cpp.o 
CMakeFiles/test_xtensor_lib.dir/test_xvectorize.cpp.o 
CMakeFiles/test_xtensor_lib.dir/test_extended_xmath_interp.cpp.o 
CMakeFiles/test_xtensor_lib.dir/test_extended_broadcast_view.cpp.o 
CMakeFiles/test_xtensor_lib.dir/test_extended_xmath_reducers.cpp.o 
CMakeFiles/test_xtensor_lib.dir/test_extended_xhistogram.cpp.o 
CMakeFiles/test_xtensor_lib.dir/test_extended_xsort.cpp.o 

Bug#1052882: xtensor: FTBFS: make[1]: *** [debian/rules:65: override_dh_auto_configure] Error 2

[Drew Parsons]

Source: xtensor
Followup-For: Bug #1052882
Control: fixed 1052882 0.24.7-1

This bug is weird, in the sense that xtensor 0.24.3-2 in testing
failed its test against xsimd 10.0.0-3 from unstable.

So why then did the migration daemon allow xsimd to migrate from
unstable to testing?

Bug#1052304: Debian 6.1 Kernels suspect

[Bill MacAllister]

Before I started bisecting the 6.1 kernel I thought I should re-examine
the assumption that 6.1.0-9 was a good kernel, i.e. a kernel where
accessing AFS volumes using kafs does not cause seg faults.  I tested
6.1.0-2, 6.1.0-5, and 6.1.0-7 without success.

Bill

--

"Can't sing louder than the guns when I'm gone,
so I guess I'll have to do it while I'm here."
   Phil Ochs

Bug#932697: Please cope with Haskell-style Vcs-Git header

[Paul Wise]

On Mon, 22 Jul 2019 00:11:51 +0100 Ian Jackson wrote:

> This syntax and its semantics do not appear to be documented in policy.

This syntax is now documented in policy and used by the Rust team too:

https://www.debian.org/doc/debian-policy/ch-controlfields.html#version-control-system-vcs-fields

-- 
bye,
pabs

https://wiki.debian.org/PaulWise


signature.asc
Description: This is a digitally signed message part

Bug#1043510: Rox removal

[Benoit-Pierre DEMAINE]

I may be the last user of ROX, but ... I still INTENSIVELY use ROX. On all
my machines, all the time. Continuously. It starts automatically during
startx, and never get killed because I never shutdown (system freeses and
needs reset after 20 or 30 days uptime).

-- 
>o_/ DEMAINE Benoit-Pierre (Gmail) (aka DoubleHP) http://benoit.demaine.info
/
If computing were an exact science, IT engineers would'nt have work \_o<

"So all that's left, Is the proof that love's not only blind but deaf."
(FAKE TALES OF SAN FRANCISCO, Arctic Monkeys)

Bug#1053139: override: bats:devel/optional

[Gioele Barabucci]

Package: ftp.debian.org
Severity: normal
User: ftp.debian@packages.debian.org
Usertags: override
X-Debbugs-Cc: team+b...@tracker.debian.org

FTP Team,

Please change bats from:

shell/optional

to:

devel/optional

The change of section happened a couple of versions ago, in 1.8.2-1:
https://salsa.debian.org/bats-team/bats/-/commit/4d5a96ed

Regards,

--
Gioele Barabucci

Bug#1053138: unittest2: RM unittest2

[Alexandre Detiste]

Source: unittest2
Version: 1.1.0-9
Severity: normal
User: python3-...@packages.debian.org
Usertags: python3-six-removal

Hi,

It looks like this package is now completely useless
in a Python3-only landscape,
similarly to enum34.

It is also dead upstream since 2015.

Can you ACK this and ask removal to FTPMasters ?

https://pypi.org/project/unittest2/

Greetings,

Alexandre


-- System Information:
Debian Release: trixie/sid
  APT prefers testing
  APT policy: (501, 'testing'), (450, 'unstable'), (400, 'experimental')
Architecture: amd64 (x86_64)
Foreign Architectures: i386

Kernel: Linux 6.5.0-1-amd64 (SMP w/2 CPU threads; PREEMPT)
Kernel taint flags: TAINT_USER
Locale: LANG=fr_BE.UTF-8, LC_CTYPE=fr_BE.UTF-8 (charmap=UTF-8), 
LANGUAGE=fr_BE:fr
Shell: /bin/sh linked to /usr/bin/dash
Init: systemd (via /run/systemd/system)

Bug#1053137: /usr/lib/i386-linux-gnu/libdav1d.so.6.9.0: Crashes on Athlon XP due to lack of SSE2

[Karo Gyoker]

Package: libdav1d6
Version: 1.2.1-2
Severity: normal
File: /usr/lib/i386-linux-gnu/libdav1d.so.6.9.0
X-Debbugs-Cc: karogyoker2+deb...@gmail.com

Dear Maintainer,

Firefox-ESR is crashing when I try to play a youtube video.
Based on the crash report[1] the issue is in libdav1d6.
Crash reason is 'illegal instruction' and I can see via 'objdump' that
there are 'movq's in the libdav1d.so.6 file, which is an SSE2 instruction, what
the Athlon XP cannot decode/execute.
Based on the installation guide, the Athlon XP is a supported CPU[2].

Please, either compile without SSE2 or add the sse2-support package as a 
dependency.

[1]: 
https://crash-stats.mozilla.org/report/index/ff65376d-9954-44ff-9ae5-03b730230925
[2]: https://www.debian.org/releases/trixie/i386/ch02s01.en.html#idm265

-- System Information:
Debian Release: trixie/sid
  APT prefers testing
  APT policy: (500, 'testing')
Architecture: i386 (i686)

Kernel: Linux 6.5.0-1-686-pae (SMP w/1 CPU thread; PREEMPT)
Locale: LANG=en_US.UTF-8, LC_CTYPE=en_US.UTF-8 (charmap=UTF-8), LANGUAGE not set
Shell: /bin/sh linked to /usr/bin/dash
Init: systemd (via /run/systemd/system)
LSM: AppArmor: enabled

Versions of packages libdav1d6:i386 depends on:
ii  libc6  2.37-10

libdav1d6:i386 recommends no packages.

libdav1d6:i386 suggests no packages.

-- no debconf information

Bug#1053136: klaus: please remove extraneous, obsolete, dependency on python3-six

[Alexandre Detiste]

Package: klaus
Version: 2.0.2-1
Severity: normal
User: python3-...@packages.debian.org
Usertags: python3-six-removal

Hi Jelmer,

klaus has an old, obsolete, dependency on python3-six,
so please remove it.

m v g

Alexandre





2.0.0 (Aug 20, 2022)
...
Drop six dependency (Jonas Haag)

$ grep six -r /usr/bin/klaus  /usr/lib/python3/dist-packages/klaus*
$ 


-- System Information:
Debian Release: trixie/sid
  APT prefers testing
  APT policy: (501, 'testing'), (450, 'unstable'), (400, 'experimental')
Architecture: amd64 (x86_64)
Foreign Architectures: i386

Kernel: Linux 6.5.0-1-amd64 (SMP w/2 CPU threads; PREEMPT)
Kernel taint flags: TAINT_USER
Locale: LANG=fr_BE.UTF-8, LC_CTYPE=fr_BE.UTF-8 (charmap=UTF-8), 
LANGUAGE=fr_BE:fr
Shell: /bin/sh linked to /usr/bin/dash
Init: systemd (via /run/systemd/system)

Versions of packages klaus depends on:
ii  python3-klaus  2.0.2-1

klaus recommends no packages.

klaus suggests no packages.

-- no debconf information

Bug#1052810: golang-starlark: FTBFS: dh_auto_test fails: unknown time zone US/Eastern

[Santiago Vila]

retitle 1052810 golang-starlark: FTBFS: dh_auto_test fails: unknown time zone 
US/Eastern
thanks

Hello.

This is probably fixed by adding tzdata-legacy to Build-Depends.

However, that's not necessarily the only way to fix it.

Some timezones have moved recently from tzdata to tzdata-legacy.

So, it would be also possible to add a build-depends on tzdata only
(which debootstrap will not install by default in the near future),
and drop the tests using timezones in tzdata-legacy.

(What should be done for this particular package, I don't know).

Thanks.

Bug#992739: fonts-courier-prime: Would it be possible to include Cyrillic?

[Nicholas D Steeves]

Hi наб, Gürkan, and Димка,

Reply follows inline.

On Tue, 07 Sep 2021 13:45:35 +0200 =?UTF-8?Q?G=C3=BCrkan_Myczko?= 
 wrote:
> Hello
> 
> I think it's absolutely possible, what's not clear about the user 
> contributions is
> though the licensing. I'd guess same as upstream, however not sure.

It looks like SIL Open Font License (OFL) to me.

> Best would probably someone create a repo for it for github.com (or as 
> you
> prefer somehwere else) and merge the user contributions to upstream 
> version,
> then tag releases.
> 
> If you feel like taking over the package and doing the work, please go 
> ahead.
> I'm also in #debian-fonts

I'm unable to evaluate the Cyrillic aspects of the font, but I'm
currently prevented from using Courier Prime due to
https://bugs.debian.org/1053133 .  I'd also like to start shipping the
new Courier Prime Fountain-mode theme, which this bug blocks.

That said, as a new Debian Font Team member and Debian Developer I'd be
happy to supervise any work or provide guidance into what is required to
rebase Debian's Courier Prime onto this fork.  Ideally it would also be
nice to see Димка's project merged into
https://github.com/quoteunquoteapps/CourierPrime


Kind regards,
Nicholas

P.S. I sometimes miss emails, so if I seem to take too long to reply,
please send a follow-up request :)


signature.asc
Description: PGP signature

Bug#1053135: RM: rust-tungstenite [mips64el ppc64el s390x] -- RoM; Build-Depends on rust-rustls which is NBS on those arches

[Jeremy Bícha]

Package: ftp.debian.org
Affects: src:rust-tungstenite

Please remove rust-sequoia-sq source and binaries on mips64el ppc64el
and s390x because it Build-Depends (and Depends) on rust-rustls

rust-rustls Depends on rust-ring which has never been built on those
architectures in Debian.

This issue is blocking the migration of rust-tungstenite to Testing.

rust-tungstenite is a fairly new package and has no reverse
dependencies in Debian yet.

On behalf of the Debian Rust team,
Jeremy Bicha

Bug#1040332: hyperspy - build-depends on removed package.

[Santiago Vila]

El 4/7/23 a las 16:54, Peter Green escribió:

Package: hyperspy
Version: 1.7.3-1
Tags: trixie, sid
Severity: serious
Justification: rc policy - "packages must be buildable within the same release"
User: debian...@lists.debian.org
Usertags: edos-uninstallable

hyperspy build-depends on python3-ptable, which was recently removed from 
Debian.


Hello. It's actually worse than that.

The package does not even build from source in bookworm:

https://tests.reproducible-builds.org/debian/rb-pkg/bookworm/amd64/hyperspy.html

It fails for me on my autobuilders, and it also fails in reproducible-builds.

Thanks.

Bug#1053134: ITP: python-cloudscraper -- Python module to bypass Cloudflare's anti-bot page

[Carles Pina i Estany]

Package: wnpp
Severity: wishlist
Owner: Carles Pina i Estany 
X-Debbugs-Cc: debian-de...@lists.debian.org

* Package name: python-cloudscraper
  Version : 1.2.68
  Upstream Contact: VeNoMouS
* URL : https://github.com/VeNoMouS/cloudscraper
* License : MIT
  Programming Lang: Python
  Description : Python module to bypass Cloudflare's anti-bot page

---
A simple Python module to bypass Cloudflare's anti-bot page (also known
as "I'm Under Attack Mode", or IUAM), implemented with Requests.
Cloudflare changes their techniques periodically, so I will update this
repo frequently.

This can be useful if you wish to scrape or crawl a website protected
with Cloudflare. Cloudflare's anti-bot page currently just checks if the
client supports Javascript, though they may add additional techniques in
the future.

Due to Cloudflare continually changing and hardening their protection
page, cloudscraper requires a JavaScript Engine/interpreter to solve
Javascript challenges. This allows the script to easily impersonate a
regular web browser without explicitly deobfuscating and parsing
Cloudflare's Javascript.
---

I ITP simplemonitor (#1016113). One of simplemonitor dependencies is
pyaarlo (#1053132). python-cloudscraper is a dependency of pyaarlo.

Incidentally, I've used cloudscraper (from upstream) previously so I'm
familiar with it.

I plan to package it inside the Debian Python Team. I will need a sponsor.

Bug#1053132: ITP: python-pyaarlo -- Module for Python that provides asynchronous access to Netgear Arlo cameras

[Carles Pina i Estany]

Package: wnpp
Severity: wishlist
Owner: Carles Pina i Estany 
X-Debbugs-Cc: debian-de...@lists.debian.org

* Package name: python-pyaarlo
  Version : 0.8.0.beta.8
  Upstream Contact: Ntwrecked
* URL : https://github.com/twrecked/pyaarlo
* License : LGPL-3.0
  Programming Lang: Python
  Description : Module for Python that provides asynchronous access to 
Netgear Arlo cameras

-
It starts a background thread that opens a single, persistant connection, an 
event stream, to the Arlo servers. As things happen to the Arlo devices - 
motion detected, battery level changes, mode changes, etc... - the Arlo servers 
post these events onto the event stream. The background thread reads these 
events from the stream, updates Pyaarlo's internal state and calls any user 
registered callbacks.
-

I submitted an ITP bug for simplemonitor (#1016113). pyarlo is a
dependency of simplemonitor.

I plan to maintain it inside the Debian Python Team. I will need a
sponsor.

Bug#1053133: Italic/slant variant is always used in Emacs, even when it shouldn't be

[Nicholas D Steeves]

Package: fonts-courier-prime
Version: 0+git20190115-3
Severity: normal
Control: forwarded -1 https://github.com/quoteunquoteapps/CourierPrime/issues/9

Hi,

I'm currently investigating why the Italic/slant variant is always
used in Emacs, even when it shouldn't be. Thus far I've only found the
following with fontforge:

The PostScript font name "Courier Prime-Regular" is
invalid.
It should be printable ASCII,
must not contain (){}[]<>%/ or space
and must be shorter than 63 characters
Could that be why the slant/italics variant is matched?

I also found this:

The glyph named Delta is mapped to U+0394.
  But its name indicates it should be mapped to U+2206.
The glyph named Omega is mapped to U+03A9.
  But its name indicates it should be mapped to U+2126.
The glyph named Tcommaaccent is mapped to U+021A.
  But its name indicates it should be mapped to U+0162.
The glyph named mu is mapped to U+03BC.
  But its name indicates it should be mapped to U+00B5.
The glyph named tcommaaccent is mapped to U+021B.
  But its name indicates it should be mapped to U+0163.

but the latter doesn't seem relevant to the italics/slant bug that I'm
reporting.

>From what I gathered on #emacs@LiberaChat, Emacs is very picky about even 
>slightly out-of-spec fonts, but on the upside that makes it a great linter! :)

To reproduce the issue, install a GUI variant of emacs, install
fonts-courier-prime, and M-x set-frame-font to a non-italics,
non-Code, non-Sans variant of Courier Prime.

'hope someone who knows more about fonts can provide instructions/guidance to 
take this further.  Please CC me on all correspondences.

Regards,
Nicholas

Bug#1053131: Fwd: [containers/podman] Release v4.7.0 - v4.7.0

[Reinhard Tartler]

Package: libpod
severity: wishlist

-- Forwarded message -
From: Lokesh Mandvekar 
Date: Wed, Sep 27, 2023 at 2:02 PM
Subject: [containers/podman] Release v4.7.0 - v4.7.0
To: containers/podman 
Cc: Subscribed 


v4.7.0 

Repository: containers/podman  · Tag:
v4.7.0  · Commit: 073183f

· Released by: lsm5 
Security

   - Now the io.containers.capabilities LABEL in an image can be an empty
   string.

Features

   - New command set: podman farm [create,list,remove,update] has been
   created to "farm" out builds to machines running Podman for different
   architectures.
   - New command: podman compose as a thin wrapper around an external
   compose provider such as docker-compose or podman-compose.
   - FreeBSD: podman run --device is now supported.
   - Linux: Add a new --module flag for Podman.
   - Podmansh: Timeout is now configurable using the podmansh_timeout
   option in containers.conf.
   - SELinux: Add support for confined users to create containers but
   restrict them from creating privileged containers.
   - WSL: Registers shared socket bindings on Windows, to allow other WSL
   distributions easy remote access (#15190
   ).
   - WSL: Enabling user-mode-networking on older WSL2 generations will now
   detect an error with upgrade guidance.
   - The podman build command now supports two new options: --layer-label
   and --cw.
   - The podman kube generate command now supports generation of k8s
   DaemonSet kind (#18899
   ).
   - The podman kube generate and podman kube play commands now support the
   k8s TerminationGracePeriodSeconds field (RH BZ#2218061
   ).
   - The podman kube generate and podman kube play commands now
support securityContext.procMount:
   Unmasked (#19881 ).
   - The podman generate kube command now supports a --podman-only flag to
   allow podman-only reserved annotations to be used in the generated YAML
   file. These annotations cannot be used by Kubernetes.
   - The podman kube generate now supports a --no-trunc flag that supports
   YAML files with annotations longer than 63 characters. Warning: if an
   annotation is longer than 63 chars, then the generated yaml file is not
   Kubernetes compatible.
   - An infra name annotation io.podman.annotations.infra.name is added in
   the generated yaml when the pod create command has --infra-name set.
   This annotation can also be used with kube play when wanting to
   customize the infra container name (#18312
   ).
   - The syntax of --uidmap and --gidmap has been extended to lookup the
   parent user namespace and to extend default mappings (#18333
   ).
   - The podman kube commands now support the List kind (#19052
   ).
   - The podman kube play command now supports environment variables in
   kube.yaml (#15983 ).
   - The podman push and podman manifest push commands now support the
   --force-compression optionto prevent reusing other blobs (#18860
   ).
   - The podman manifest push command now supports --add-compression to
   push with compressed variants.
   - The podman manifest push command now honors the add_compression field
   from containers.conf if --add-compression is not set.
   - The podman run and podman create --mount commands now support the ramfs
   type (#19659 ).
   - When running under systemd (e.g., via Quadlet), Podman will extend the
   start timeout in 30 second steps up to a maximum of 5 minutes when pulling
   an image.
   - The --add-host option now accepts the special string host-gateway
   instead of an IP Address, which will be mapped to the host IP address.
   - The podman generate systemd command is deprecated. Use Quadlet for
   running containers and pods under systemd.
   - The podman secret rm command now supports an --ignore option.
   - The --env-file option now supports multiline variables (#18724
   ).
   - The --read-only-tmpfs flag now affects /dev and /dev/shm as well as
   /run, /tmp, /var/tmp (#12937
   ).
   - The Podman --mount option now supports bind mounts passed as globs.
   - The --mount option can now be specified in containers.conf using the
   mounts field.
   - The podman stats now has an 

Bug#1016113: ITP: simplemonitor -- simplemonitor monitors hosts and network connectivity. It is designed to be quick and easy to set up

[Carles Pina i Estany]

Control: owner car...@pina.cat
Control: retitle ITP: simplemonitor -- simplemonitor monitors hosts and network 
connectivity. It is designed to be quick and easy to set up

Bug#1052252: transition: grantlee5

[Sebastian Ramacher]

Control: tags -1 confirmed
Control: forwarded -1 
https://release.debian.org/transitions/html/grantlee5-3.html

On 2023-09-19 16:52:46 +0200, Pino Toscano wrote:
> Package: release.debian.org
> Severity: normal
> User: release.debian@packages.debian.org
> Usertags: transition
> X-Debbugs-Cc: grantl...@packages.debian.org, 
> pkg-kde-t...@alioth-lists.debian.net
> Control: affects -1 + src:grantlee5
> 
> Hi,
> 
> grantlee (packaged in Debian in src:grantlee5) is a library (two
> libraries, in practice) that has a stable API/ABI. The new release
> 5.3.x, currently in experimental, is generally usable by users
> built with the old version.
> 
> The only gotcha is that plugins for it are installed and loaded from
> paths with the major and minor version in it, i.e.
>   ../plugins/grantlee/./
> This means that, after the upgrade to a new minor series, the plugins
> installed after building with the old version are not used anymore;
> usually software using grantlee and shipping plugins for it follows
> the grantlee version, so a simple rebuild is enough to fix the issue.

Please go ahead.

Cheers
-- 
Sebastian Ramacher

Bug#967284: [Pkg-pascal-devel] Bug#967284: castle-game-engine: depends on deprecated GTK 2

[Michalis Kamburelis]

We use GTK2 in 2 ways in Castle Game Engine (CGE), and we have 2 plans
how to get rid of it.

I wrote probably too many details below :) So, the short answer first:

- We may be able to get rid of GTK2 dependency in CGE.
- It requires doing 2 things by me in CGE. I will get back to you
~next week when this is done.
- The necessary changes should be part of CGE 7.0-alpha.3 release,
which I hope to do within ~2 weeks, so rather soon.
- This will make both CGE and view3dscene free from GTK2 dependency.

Details, and 2 ways how we use GTK2 in CGE right now:

1. The Castle Game Engine editor ( https://castle-engine.io/editor ,
in sources: tools/castle-editor ) is an application using Lazarus LCL.

On Linux and FreeBSD it is mostly tested with LCL GTK2 widgetset,
though in theory it could work with any LCL widgetset that works on
these platforms (and has standard LCL components, including
TOpenGLControl, with reliable and sufficiently complete
implementation).

So it is possible to get rid of GTK2 dependency by just
recompiling the editor with different LCL widgetset, like Qt5 or GTK3.

- GTK3 widgetset?

No. It is sadly not production-ready in LCL. So say docs on
wiki and talk on Lazarus mailing list. Quick test with CGE editor
using GTK3 widgetset confirms it's very buggy: broken image colors,
broken layout, disappearing controls after Alt+Tab (on 1st form,
ChooseProject), then broken button icons, half-visible bottom tabs (on
ProjectForm), and then access violation when creating OpenGL context
(when opening the project).

- Qt5 widgetset?

Almost yes. Testing today showed it's mostly ready.

I only found 1 (Qt5-widgetset-specific) bug, which I hope to
deal with soon: Sometimes when selecting a file with preview (e.g.
glTF file) there's weird blinking of the bottom UI, as if some control
was hidden/shown each frame. That's my TODO to workaround it.

Note that it is critical that you use only Lazarus >= 2.2.4,
with my merge request applied to Qt5 widgetset:
https://gitlab.com/freepascal.org/lazarus/lazarus/-/merge_requests/95/
. I made explicit check for this at the beginnig of
https://github.com/castle-engine/castle-engine/blob/master/tools/castle-editor/code/frameviewfile.pas
, so compilation will even fail with clear error with older LCL. This
should not be a problem for Debian -- bookworm has Lazarus 2.2.6 I
see, bullseye-backports has 2.2.4 also OK (ref:
https://packages.debian.org/search?keywords=lazarus=names=all=all
).

This also means adding dependency on libqt5pas to the Debian
CGE package that includes the editor. (I am not sure which Debian
package it is at this point.)

I am not yet sure what to do for upstream downloads (
https://castle-engine.io/download ). Linking them to old GTK2
widgetset (as we do now) sucks, but linking to libqt5pas would also be
problematic: most users don't have it installed, and would observe
editor just crash at run. Anyhow, that's my (upstream) issue to
decide, Debian packaging has it simpler since you can just depend on
libqt5pas.

2. Our TCastleWindow class has a number of "backends" like GTK2. Our
"backends" are quite similar to the concept of "widgetsets" in LCL,
but much simpler since our TCastleWindow is much simpler beast than
LCL.

The TCastleWindow class is used by most of our examples and is
recommended to use if you want to "just make a game engine" similar to
other game engines. Our "New Project" templates set up the project to
use TCastleWindow. The view3dscene also uses TCastleWindow.

There are a few TCastleWindow backends (
https://castle-engine.io/castlewindow_backends ). There's even one
backend using LCL under the hood ( CASTLE_WINDOW_LCL ) and thus using
in theory any LCL widgetset. But we don't advise using
CASTLE_WINDOW_LCL (or LCL), that's why we have created TCastleWindow
in the end: TCastleWindow is more portable (e.g. works on Android and
iOS and Nintendo Switch without any additional effort, so one can
recompile desktop (Linux, Windows, macOS) applications easily). It
also has a more efficient loop processing (so e.g. "mouse look" works
smoothly with TCastleWindow). And in general TCastleWindow (without
CASTLE_WINDOW_LCL) means we have 1 less dependency in CGE, so things
are simpler. In general we "win" because TCastleWindow is just a
simple thing (just a class with OpenGL context). Applications using
TCastleWindow *do not* depend on LCL, unless they specifically use
CASTLE_WINDOW_LCL backend.

By default on Linux and FreeBSD we use GTK2 backend, CASTLE_WINDOW_GTK_2 .

That said, we can and want to develop a GTK3 backend for
TCastleWindow. Should be straightforward adjustment to our GTK2
backend.

Note: FPC/Lazarus folks could make it easier by providing GTK3
bindings in FPC, just like GTK2, but it seems there's no consensus
if/how to do this (
https://gitlab.com/freepascal.org/fpc/source/-/issues/39989 ). So I
guess in CGE upstream we'll have to fork these 

Bug#1053089: lxdm.conf information

[VastOne]

lxdm.conf information

[base]
## uncomment and set autologin username to enable autologin
# autologin=dgod

## uncomment and set timeout to enable timeout autologin,
## the value should >=5
# timeout=10

## default session or desktop used when no systemwide config
session=/usr/bin/fluxbox

## uncomment and set to set numlock on your keyboard
# numlock=0

## set this if you don't want to put xauth file at ~/.Xauthority
# xauth_path=/tmp

# not ask password for users who have empty password
# skip_password=1

## greeter used to welcome the user
greeter=/usr/lib/lxdm/lxdm-greeter-gtk

[server]
## arg used to start xserver, not fully function
# arg=/usr/bin/X -background vt1
# uncomment this if you really want xserver listen to tcp
# tcp_listen=1

[display]
## gtk theme used by greeter
gtk_theme=Vertex-Dark

## background of the greeter
#bg=/usr/share/backgrounds/default.png
bg=/usr/share/images/desktop-base/vsido_login.png

## if show bottom pane
bottom_pane=1

## if show language select control
lang=0

## if show keyboard layout select control
keyboard=0

## the theme of greeter
theme=VSIDO

[input]

[userlist]
## if disable the user list control at greeter
disable=0

## whitelist user
white=

## blacklist user
black=


-- 
Thank you,

VastOne
V-Ger VSIDO Developer

Bug#1016113: ITP: simplemonitor -- simplemonitor monitors hosts and network connectivity. It is designed to be quick and easy to set up

[Carles Pina i Estany]

Control: Package: wnpp
Control: Severity: wishlist
Control: Owner: car...@pina.cat

Bug#1053130: bookworm-pu: package glibc/2.36-9+deb12u2

[Aurelien Jarno]

Package: release.debian.org
Severity: normal
Tags: bookworm
User: release.debian@packages.debian.org
Usertags: pu
X-Debbugs-Cc: gl...@packages.debian.org, debian-gl...@lists.debian.org, 
debian-b...@lists.debian.org
Control: affects -1 + src:glibc

[ Reason ]
The upstream glibc stable branch got a few fixes since the latest point
released, including two security fixes.
 
[ Impact ]
Installations will be left vulnerable to security issues.

[ Tests ]
The upstream fixes come with additional tests, which represent a
significant part of the diff.

[ Risks ]
The risk can be considered low, as all the changes except the one for
CVE-2023-5156 have been tested in testing/sid for a few days. The one
for CVE-2023-5156 has just been uploaded to sid, but comes with a test.
In addition those fixes have been committed on a few upstream branches
and have been used by other distributions to provide security updates. 

[ 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 (old)stable
  [x] the issue is verified as fixed in unstable

[ Changes ]

All the changes come from the upstream stable branch, and are summarized
in the debian changelog. Let me comment it:

 - Fix the value of F_GETLK/F_SETLK/F_SETLKW with __USE_FILE_OFFSET64 on
   ppc64el.  Closes: #1050592.

This fixes a regression introduced in the previous point release and
testing/sid. On ppc64el, the values of F_GETLK/F_SETLK/F_SETLKW changed
when __USE_FILE_OFFSET64 is in use. While this is handled transparently
at the glibc level, it breaks some packages which use the values
internally like perl.

 - Fix a stack read overflow in getaddrinfo in no- mode
   (CVE-2023-4527).  Closes: #1051958.

This fixes a security issue in a new feature introduced in glibc 2.36,
which has not been considered serious enough by the security team to
issue a DSA.

 - Fix use after free in getcanonname (CVE-2023-4806, CVE-2023-5156).

This fixes a security issue that might happen with some NSS modules
which implement some hooks but not some others, however there are no
known modules implemented that way. Unfortunately the initial fix
introduced a memory leak which got assigned CVE-2023-5156.

 - Update the x86 cacheinfo code to look at the per-thread L3 cache to
   determine the non-temporal threshold. This improves memory and string
   functions on modern CPUs.

This changes the way the cache sizes are interpreted, properly taking
into account the L3 cache on modern CPUs. The memory and string
functions are unchanged, only some threshold are changed.

 - Fix _dl_find_object to return correct values even during early startup.

It has been found that _dl_find_object is can wrongly return 1 during
early startup. Currently no impact has been found, but as this functions
is used by some external unwiders (for instance GCC), it's better to fix
it to be future proof.

 - Always call destructors in reverse constructor order.

This fixes a regression introduced in glibc 2.36, which causes
destructors to be called in a different order than the constructors when
there are cyclic dependencies. This causes issues with some
applications.

[ Other info ]
debian-boot is in Cc: as glibc has one udeb.
diff --git a/debian/changelog b/debian/changelog
index aafd6e3a..146c85d3 100644
--- a/debian/changelog
+++ b/debian/changelog
@@ -1,3 +1,19 @@
+glibc (2.36-9+deb12u2) UNRELEASED; urgency=medium
+
+  * debian/patches/git-updates.diff: update from upstream stable branch:
+- Fix the value of F_GETLK/F_SETLK/F_SETLKW with __USE_FILE_OFFSET64 on
+  ppc64el.  Closes: #1050592.
+- Fix a stack read overflow in getaddrinfo in no- mode
+  (CVE-2023-4527).  Closes: #1051958.
+- Fix use after free in getcanonname (CVE-2023-4806, CVE-2023-5156).
+- Update the x86 cacheinfo code to look at the per-thread L3 cache to
+  determine the non-temporal threshold. This improves memory and string
+  functions on modern CPUs.
+- Fix _dl_find_object to return correct values even during early startup.
+- Always call destructors in reverse constructor order.
+
+ -- Aurelien Jarno   Sat, 23 Sep 2023 15:08:08 +0200
+
 glibc (2.36-9+deb12u1) bookworm; urgency=medium
 
   [ Aurelien Jarno ]
diff --git a/debian/patches/git-updates.diff b/debian/patches/git-updates.diff
index 9203223b..cdb02b1d 100644
--- a/debian/patches/git-updates.diff
+++ b/debian/patches/git-updates.diff
@@ -68,10 +68,10 @@ index d1e139d03c..09c0cf8357 100644
  else  # -s
  verbose   :=
 diff --git a/NEWS b/NEWS
-index f61e521fc8..9f6b48b63d 100644
+index f61e521fc8..ae55ffb53a 100644
 --- a/NEWS
 +++ b/NEWS
-@@ -5,6 +5,65 @@ See the end for copying conditions.
+@@ -5,6 +5,85 @@ See the end for copying conditions.
  Please send GNU C library bug reports via 
  using `glibc' in the "product" field.
  
@@ -91,6 +91,21 @@ index 

Bug#1016113: ITP: simplemonitor -- simplemonitor monitors hosts and network connectivity. It is designed to be quick and easy to set up

[Carles Pina i Estany]

Package: wnpp
Severity: wishlist
Owner: car...@pina.cat

Bug#1052942: insserv: FTBFS: insserv: Could not read script nolsbheader: No such file or directory

[Ian Jackson]

Mark Hindley writes ("Bug#1052942: insserv: FTBFS: insserv: Could not read 
script nolsbheader: No such file or directory"):
> Thanks for this. However, I am currently unable to repoduce this
> failure in my customary pbuilder setup. And it doesn't appear at
> reproducible builds either[1]

I just tried this myself with my usual sbuild setup and it succeeded
there too[1].  Lucas, I think something from your rebuild environment
(a chroot of some kind I presume) must be triggering this failure.  Is
there some way we can reproduce it more precisely (eg, a buildinfo
file?)

I looked at the build log
 http://qa-logs.debian.net/2023/09/25/insserv_1.24.0-1_unstable.log
and compared it to the one from my sbuild, using diff.  There are a
lot of changes to the "furniture" but also there are noise changes to
the output of the insserv test suite, including ordring changes of
passing tests.  This seemed surprising to me.

Mark, is the insserv test suite supposed to produce deterministic
output ?

Ian.

[1] just-updated sid chroot, "dgit sbuild -wgf build -c build".

Bug#1053119: orca fails to read file names when navigating some folders in caja+mate menu issues

[Jean-Philippe MENGUAL]

Package: orca
Version: 45.0-1
Followup-For: Bug #1053119

Hi,

Thanks for your quick reply. Tested on the latest gnome-45 branch and seems
to be fixed. Debian should upload this new version I guess.

Let's see if Samuel can do this in the next days.

Regards

Dear Maintainer,

*** Reporter, please consider answering these questions, where appropriate ***

   * What led up to the situation?
   * What exactly did you do (or not do) that was effective (or
 ineffective)?
   * What was the outcome of this action?
   * What outcome did you expect instead?

*** End of the template - remove these template lines ***


-- System Information:
Debian Release: trixie/sid
  APT prefers buildd-unstable
  APT policy: (500, 'buildd-unstable'), (500, 'unstable'), (1, 'experimental')
Architecture: amd64 (x86_64)
Foreign Architectures: i386

Kernel: Linux 6.4.0-4-amd64 (SMP w/4 CPU threads; PREEMPT)
Locale: LANG=fr_FR.UTF-8, LC_CTYPE=fr_FR.UTF-8 (charmap=UTF-8), LANGUAGE not set
Shell: /bin/sh linked to /usr/bin/dash
Init: systemd (via /run/systemd/system)
LSM: AppArmor: enabled

Versions of packages orca depends on:
ii  gir1.2-glib-2.01.78.1-1
ii  gir1.2-gstreamer-1.0   1.22.6-1
ii  gir1.2-gtk-3.0 3.24.38-5
ii  gir1.2-pango-1.0   1.51.0+ds-2
ii  gir1.2-wnck-3.043.0-3
ii  gsettings-desktop-schemas  45.0-1
ii  gstreamer1.0-plugins-good  1.22.6-1
ii  python33.11.4-5+b1
ii  python3-brlapi 6.6-4
ii  python3-cairo  1.24.0-3
ii  python3-gi 3.46.0-1
ii  python3-louis  3.27.0-1
ii  python3-pyatspi2.46.0-2
ii  python3-speechd0.11.5-2
ii  speech-dispatcher  0.11.5-2
ii  xkbset 0.8-1

Versions of packages orca recommends:
ii  xbrlapi  6.6-4

Versions of packages orca suggests:
ii  brltty  6.6-4

-- no debconf information

Bug#1053119: orca fails to read file names when navigating some folders in caja+mate menu issues

[Jordan Livesey]

sometimes the bug is reproducible sometimes it isn't, this has been
reported on the orca mailing list at freelists.org and the upstream
maintainer of orca is aware of this

On Wed, Sep 27, 2023 at 10:10 PM Jean-Philippe MENGUAL 
wrote:

> Hi,
>
> Many thanks for this report. 2 questions:
> - does the bug in the file manager appear randomly or do you have a
> reproductible scenario?
> - have you reported too on the orca mailing list?
>
> The next steps for me are to inform upstream of the problem in order to
> get a fix in the definitive release orca 45. But I dont want to do
> duplicate report. My report upstream also will include a debug file to
> help the maintainer.
>
> Thanks for your info
>
> Best regards
>
>
>
> Jean-Philippe MENGUAL
> Debian Developer non uploading
> Community team member
> Accessibility team member
> debian-l10n-french team member
> President of Debian France non-profit organization
>
> Le 27/09/2023 à 19:43, jordan a écrit :
> > Package: orca
> > Version: 45.0-1~bpo12+1
> > Severity: important
> > X-Debbugs-Cc: jordanlives...@gmail.com
> >
> > Dear Maintainer, I've noticed a bug in this version of orca, for some
> reason in the mate desktop, you could be navigating files with the file
> manager and orca sometimes fails to read file names even if the orca curser
> is on it, there is also a bug in the mate menu where orca will just keep
> reading, preferences menu when navigating the submenus of that menu
> >
> > *** Reporter, please consider answering these questions, where
> appropriate ***
> >
> > * What led up to the situation?
> > * What exactly did you do (or not do) that was effective (or
> >   ineffective)?
> > * What was the outcome of this action?
> > * What outcome did you expect instead?I expected orca to behave
> normally as it usually does when navigating files or the mate menu
> >
> > *** End of the template - remove these template lines ***
> >
> >
> > -- System Information:
> > Debian Release: 12.1
> >APT prefers stable-updates
> >APT policy: (500, 'stable-updates'), (500, 'stable-security'), (500,
> 'stable')
> > Architecture: amd64 (x86_64)
> > Foreign Architectures: i386
> >
> > Kernel: Linux 6.1.0-12-amd64 (SMP w/6 CPU threads; PREEMPT)
> > Locale: LANG=en_GB.UTF-8, LC_CTYPE=en_GB.UTF-8 (charmap=UTF-8), LANGUAGE
> not set
> > Shell: /bin/sh linked to /usr/bin/dash
> > Init: systemd (via /run/systemd/system)
> > LSM: AppArmor: enabled
> >
> > Versions of packages orca depends on:
> > ii  gir1.2-glib-2.01.74.0-3
> > ii  gir1.2-gstreamer-1.0   1.22.0-2
> > ii  gir1.2-gtk-3.0 3.24.37-2
> > ii  gir1.2-pango-1.0   1.50.12+ds-1
> > ii  gir1.2-wnck-3.043.0-3
> > ii  gsettings-desktop-schemas  43.0-1
> > ii  gstreamer1.0-plugins-good  1.22.0-5+deb12u1
> > ii  python33.11.2-1+b1
> > ii  python3-brlapi 6.5-7
> > ii  python3-cairo  1.20.1-5+b1
> > ii  python3-gi 3.42.2-3+b1
> > ii  python3-louis  3.24.0-1
> > ii  python3-pyatspi2.46.0-2
> > ii  python3-speechd0.11.5-1~bpo12+1
> > ii  speech-dispatcher  0.11.5-1~bpo12+1
> > ii  xkbset 0.6-3
> >
> > Versions of packages orca recommends:
> > ii  xbrlapi  6.5-7
> >
> > Versions of packages orca suggests:
> > pn  brltty  
> >
> > -- no debconf information
> >
> > ___
> > Pkg-a11y-devel mailing list
> > pkg-a11y-de...@alioth-lists.debian.net
> > https://alioth-lists.debian.net/cgi-bin/mailman/listinfo/pkg-a11y-devel
>

Bug#1053119: orca fails to read file names when navigating some folders in caja+mate menu issues

[Jean-Philippe MENGUAL]

Hi,

Many thanks for this report. 2 questions:
- does the bug in the file manager appear randomly or do you have a 
reproductible scenario?

- have you reported too on the orca mailing list?

The next steps for me are to inform upstream of the problem in order to 
get a fix in the definitive release orca 45. But I dont want to do 
duplicate report. My report upstream also will include a debug file to 
help the maintainer.


Thanks for your info

Best regards



Jean-Philippe MENGUAL
Debian Developer non uploading
Community team member
Accessibility team member
debian-l10n-french team member
President of Debian France non-profit organization

Le 27/09/2023 à 19:43, jordan a écrit :

Package: orca
Version: 45.0-1~bpo12+1
Severity: important
X-Debbugs-Cc: jordanlives...@gmail.com

Dear Maintainer, I've noticed a bug in this version of orca, for some reason in 
the mate desktop, you could be navigating files with the file manager and orca 
sometimes fails to read file names even if the orca curser is on it, there is 
also a bug in the mate menu where orca will just keep reading, preferences menu 
when navigating the submenus of that menu

*** Reporter, please consider answering these questions, where appropriate ***

* What led up to the situation?
* What exactly did you do (or not do) that was effective (or
  ineffective)?
* What was the outcome of this action?
* What outcome did you expect instead?I expected orca to behave normally as 
it usually does when navigating files or the mate menu

*** End of the template - remove these template lines ***


-- System Information:
Debian Release: 12.1
   APT prefers stable-updates
   APT policy: (500, 'stable-updates'), (500, 'stable-security'), (500, 
'stable')
Architecture: amd64 (x86_64)
Foreign Architectures: i386

Kernel: Linux 6.1.0-12-amd64 (SMP w/6 CPU threads; PREEMPT)
Locale: LANG=en_GB.UTF-8, LC_CTYPE=en_GB.UTF-8 (charmap=UTF-8), LANGUAGE not set
Shell: /bin/sh linked to /usr/bin/dash
Init: systemd (via /run/systemd/system)
LSM: AppArmor: enabled

Versions of packages orca depends on:
ii  gir1.2-glib-2.01.74.0-3
ii  gir1.2-gstreamer-1.0   1.22.0-2
ii  gir1.2-gtk-3.0 3.24.37-2
ii  gir1.2-pango-1.0   1.50.12+ds-1
ii  gir1.2-wnck-3.043.0-3
ii  gsettings-desktop-schemas  43.0-1
ii  gstreamer1.0-plugins-good  1.22.0-5+deb12u1
ii  python33.11.2-1+b1
ii  python3-brlapi 6.5-7
ii  python3-cairo  1.20.1-5+b1
ii  python3-gi 3.42.2-3+b1
ii  python3-louis  3.24.0-1
ii  python3-pyatspi2.46.0-2
ii  python3-speechd0.11.5-1~bpo12+1
ii  speech-dispatcher  0.11.5-1~bpo12+1
ii  xkbset 0.6-3

Versions of packages orca recommends:
ii  xbrlapi  6.5-7

Versions of packages orca suggests:
pn  brltty  

-- no debconf information

___
Pkg-a11y-devel mailing list
pkg-a11y-de...@alioth-lists.debian.net
https://alioth-lists.debian.net/cgi-bin/mailman/listinfo/pkg-a11y-devel

Bug#1053120: linux-image-6.1.0-12-amd64: Kernel NULL pointer deref with XFS on kernel 6.1

[sb56637]

On 9/27/23 14:29, Salvatore Bonaccorso wrote:


Thanks for the report. This should be fixed upstream 6.1.53 and
pending now for the next upload for bookworm.


Hi Salvatore, thanks a lot for the fast reply!
So do you think that the bug I reported with XFS is the same as the fix being 
implemented upstream? Will the next upload for Bookworm come soon?

Bug#1052069: ibt=off

[Adam Majer]

Looks like adding kernel parameters `ibt=off` seems to be a workaround.

Bug#1031362: python-pycdlib: FTBFS (undeclared build-dependency on tzdata)

[Santiago Vila]

reopen 1031362
found 1031362 1.12.0+ds1-4
thanks

Hello.

This was a bug in the package called "python-pycdlib".

You added a Build-Depends:tzdata in package "python-pyeclib".

According to Policy, we should not add a BD on packages
which are not really required during build, so now we have two bugs.

I'm just reopening this one, but you might want to remove
the undesired BD of python-pyeclib in git.

Thanks.

Bug#1053129: small correction to the short description

[Ben Tris]

Package: r-cran-poorman
X-Debbugs-CC: benatt...@gezapig.nl
Severity: minor

Dear Maintainer,

The short description contains a typo.

sependency should be: dependency

this:
Poor Man's sependency free recreation of 'dplyr' GNU R package
to:
Poor Man's dependency free recreation of 'dplyr' GNU R package

Bug#1052935: bm-el: FTBFS: make: *** [debian/rules:4: binary] Error 25

[Nicholas D Steeves]

Control: forwarded -1 https://github.com/joodland/bm/issues/46

Bug#799603: Should not monitor /run/network/ifstate if ifupdown plugin disabled

[Michael Biebl]

On Sun, 20 Sep 2015 12:37:18 -0700 Josh Triplett  
wrote:

Package: network-manager
Version: 1.0.6-1
Severity: normal

I have the ifupdown plugin disabled in
/etc/NetworkManager/NetworkManager.conf; however, I still see the
following in syslog:

Sep 20 12:34:12 x NetworkManager[20704]:   monitoring ifupdown state file 
'/run/network/ifstate'.




Later in the same log, NetworkManager also tries to open that file:

Sep 20 12:34:12 x NetworkManager[20704]:   Error: failed to open 
/run/network/ifstate



I downgraded the log message from warn to info.

That said, I'd be happy to take a patch which disables the ifstate 
monitoring completely, if the ifupdown plugin has been disabled.


Regards,
Michael


OpenPGP_signature.asc
Description: OpenPGP digital signature

Bug#1052955: irony-mode: FTBFS: make: *** [debian/rules:8: binary] Error 25

[Nicholas D Steeves]

Control: forwarded -1 https://github.com/Sarcasm/irony-mode/issues/587

Bug#1052415: Accepted rust-tungstenite 0.20.1-1 (source) into unstable

[Salvatore Bonaccorso]

Source: rust-tungstenite
Source-Version: 0.20.1-1

Jeremy, this fixes #1052415, closing manually.

On Wed, Sep 27, 2023 at 04:44:46PM +, Debian FTP Masters wrote:
> -BEGIN PGP SIGNED MESSAGE-
> Hash: SHA512
> 
> Format: 1.8
> Date: Wed, 27 Sep 2023 11:27:47 -0400
> Source: rust-tungstenite
> Built-For-Profiles: noudeb
> Architecture: source
> Version: 0.20.1-1
> Distribution: unstable
> Urgency: medium
> Maintainer: Debian Rust Maintainers 
> 
> Changed-By: Jeremy Bícha 
> Changes:
>  rust-tungstenite (0.20.1-1) unstable; urgency=medium
>  .
>* Team upload
>* Package tungstenite 0.20.1 from crates.io using debcargo 2.6.0
>* Add Build-Depends: librust-rustls-dev to ensure Depends are satisfiable
> Checksums-Sha1:
>  18c9443b9732e4e1af8a428b38c9860c70100628 2907 rust-tungstenite_0.20.1-1.dsc
>  82639c54b959f7995b189f981e33006f487f3379 58926 
> rust-tungstenite_0.20.1.orig.tar.gz
>  8dad916f5b081ff1f963781c4c420aeb065e624b 3852 
> rust-tungstenite_0.20.1-1.debian.tar.xz
>  ac0299eeffba9c71e361bdab9bc39127704eb08c 8171 
> rust-tungstenite_0.20.1-1_source.buildinfo
> Checksums-Sha256:
>  b24470055dc4d34d00b1680ae6459bb0594303f0df38a9fb9ec69a693ee0db62 2907 
> rust-tungstenite_0.20.1-1.dsc
>  eb5222b16b704c8221d8eaf9d1ba3f20b07723643b623aecd789f2d8ab75db9f 58926 
> rust-tungstenite_0.20.1.orig.tar.gz
>  5e33af97722f97bb9eaa22ef5c8558ed7c4c0481884d18d0aea4230244a652bc 3852 
> rust-tungstenite_0.20.1-1.debian.tar.xz
>  ecec6dd1fa369c8016edd422f5b7c742c2ea68ae87933fdab79f4692e2c5fb80 8171 
> rust-tungstenite_0.20.1-1_source.buildinfo
> Files:
>  74718deebafbdf8d64ef6642bae2f4f5 2907 rust optional 
> rust-tungstenite_0.20.1-1.dsc
>  4032be3054107eaff7808d84c624418c 58926 rust optional 
> rust-tungstenite_0.20.1.orig.tar.gz
>  80c9198fb7fe201b8c1dc84851cb5c6a 3852 rust optional 
> rust-tungstenite_0.20.1-1.debian.tar.xz
>  8086bdfb555a69d6243e17e7ba60d4ca 8171 rust optional 
> rust-tungstenite_0.20.1-1_source.buildinfo
> 
> -BEGIN PGP SIGNATURE-
> 
> iQIzBAEBCgAdFiEETQvhLw5HdtiqzpaW5mx3Wuv+bH0FAmUUSlEACgkQ5mx3Wuv+
> bH1IkxAAleCzCWqY2j9TKKsjZchSWWS+srld1bI8E+1N012dk5T7Iy3LKeMvScxx
> f+4yLLS6w+vUEaYWQpvkAYnXCfgxvxY+QioEARt3BYqVbHanADYBx6XTSat4keb2
> KfrIbnr+4eycfQwRjOVvibcMagkHT4aCjngsnZiZrCwxuFNAn5eznb2oWwKB2YQN
> 2L67QMIPY3XgpnmvYCZkFmCwYkerLo0XzJ9bpYloN2ANoQHAKafWWvpvaM7RcQh2
> uIu9U8ZbyKHYkuB2qa6NqF7AZ4nsOGmQ3c/tRmDjcbRtCOEfFM3mXSKwpbpRyCap
> fipuuy0iMnNDy4e51vvg/Op96DW9A1B61iANeXv+fykGfQDIqFIX7KBCCD/amqxe
> bv7auIfnHufuU+fjGew1yAWff9xq8njasdxhzNCSiWpkO4xshjKHsu+2Q9Hy4Wo3
> O5yXXQmezV5LxpVfPksuhatKPgCuGoGx6rtFnTyCskeehSoa5heMqhU2Wod2s7Hp
> 1IuTRDCgTXy+bYeevTLorAywcgxFJkIhKLuZSF+e0W4D2u3mzmKiE6kxms7ml7EQ
> wRajy4sVFxd6b+31L1PFfgxeEaU0+H6HMIj4ILcgnLu+fKjfjN8TzDn0ZiBmdVTF
> mekqXt4i5ad7Uu2N8vYJbbgjDq5ccVXyqjxIEa2BgCVgopuwgfY=
> =lQNg
> -END PGP SIGNATURE-
> 

Bug#1053128: smbclient: "smbtree -N" causes a segfault when "server min protocol = NT1"

[Dmitry]

Package: smbclient
Version: 2:4.17.10+dfsg-0+deb12u1
Severity: important
X-Debbugs-Cc: dmitry.s.tele...@gmail.com

Dear Maintainer,

   * What led up to the situation?

1. apt install samba smbclient
2. nano /etc/samba/smb.conf
3. I added the line "server min protocol = NT1" after [global].
4. I saved the file and closed the editor.
5. testparm -s
6. systemctl restart smbd nmbd
7. smbtree -N --option="client min protocol=NT1"

   * What was the outcome of this action?

PANIC (pid 2395): Signal 11: Segmentation fault in 4.17.10-Debian
BACKTRACE: 14 stack frames:
 #0 
/usr/lib/x86_64-linux-gnu/samba/libgenrand-samba4.so.0(log_stack_trace+0x2e) 
[0x7fc8789c955e]
 #1 /usr/lib/x86_64-linux-gnu/samba/libgenrand-samba4.so.0(smb_panic+0x9) 
[0x7fc8789c97b9]
 #2 /usr/lib/x86_64-linux-gnu/samba/libgenrand-samba4.so.0(+0x1851) 
[0x7fc8789c9851]
 #3 /lib/x86_64-linux-gnu/libc.so.6(+0x3bfd0) [0x7fc878b32fd0]
 #4 /lib/x86_64-linux-gnu/libbsd.so.0(strlcpy+0x10) [0x7fc878ce45e0]
 #5 /lib/x86_64-linux-gnu/libsmbclient.so.0(+0x14280) [0x7fc878f3b280]
 #6 /lib/x86_64-linux-gnu/libsmbclient.so.0(+0x14809) [0x7fc878f3b809]
 #7 /lib/x86_64-linux-gnu/libsmbclient.so.0(+0x1491c) [0x7fc878f3b91c]
 #8 /lib/x86_64-linux-gnu/libsmbclient.so.0(+0x15430) [0x7fc878f3c430]
 #9 /lib/x86_64-linux-gnu/libsmbclient.so.0(+0xd187) [0x7fc878f34187]
 #10 smbtree(main+0x25a) [0x564c2a2bb68a]
 #11 /lib/x86_64-linux-gnu/libc.so.6(+0x271ca) [0x7fc878b1e1ca]
 #12 /lib/x86_64-linux-gnu/libc.so.6(__libc_start_main+0x85) [0x7fc878b1e285]
 #13 smbtree(_start+0x21) [0x564c2a2bbb11]
smb_panic(): calling panic action [/usr/share/samba/panic-action 2395]
smb_panic(): action returned status 0
Can not dump core: corepath not set up

   * What outcome did you expect instead?

Display network resources without crashing.

p.s. Without "-N" the utility works correctly.


-- System Information:
Debian Release: 12.1
  APT prefers stable-updates
  APT policy: (500, 'stable-updates'), (500, 'stable-security'), (500, 'stable')
Architecture: amd64 (x86_64)

Kernel: Linux 6.1.0-12-amd64 (SMP w/4 CPU threads; PREEMPT)
Locale: LANG=C, LC_CTYPE=C.UTF-8 (charmap=UTF-8), LANGUAGE not set
Shell: /bin/sh linked to /usr/bin/dash
Init: systemd (via /run/systemd/system)
LSM: AppArmor: enabled

Versions of packages smbclient depends on:
ii  libarchive13  3.6.2-1
ii  libbsd0   0.11.7-2
ii  libc6 2.36-9+deb12u1
ii  libgnutls30   3.7.9-2
ii  libpopt0  1.19+dfsg-1
ii  libreadline8  8.2-1.3
ii  libsmbclient  2:4.17.10+dfsg-0+deb12u1
ii  libtalloc22.4.0-f2
ii  libtevent00.14.1-1
ii  samba-common  2:4.17.10+dfsg-0+deb12u1
ii  samba-libs2:4.17.10+dfsg-0+deb12u1

smbclient recommends no packages.

Versions of packages smbclient suggests:
pn  cifs-utils   
pn  heimdal-clients  

-- no debconf information

Bug#1052144: ghc: Needs to link against libatomic on at least m68k

[John Paul Adrian Glaubitz]

On Wed, 2023-09-27 at 22:00 +0300, Ilias Tsitsimpis wrote:
> On Fri, Sep 22, 2023 at 09:20AM, John Paul Adrian Glaubitz wrote:
> > The attached patch fixes the issue for me. The underlying problem is
> > the use of legacy atomic functions for which no 64-bit variants exist
> > on some architectures [1]. See also the upstream discussion here [2].
> 
> Is this patch enough, or do we have to backport this [1] as well?
> 
> [1] 
> https://gitlab.haskell.org/ghc/ghc/-/commit/fc186b0c0ac56d6ff6225d3f6607be37770fcb52

I am not 100% sure. I think I had the patch applied when I tested this.

> > While this patch fixes the original problem, the stage2 build later
> > fails due to memory exhaustion for which I haven't found a solution
> > yet.
> 
> I faced the same issue on mipsel (see [2]) and never found a solution
> for it. Luckily, mipsel got removed from release architectures.
> 
> [2] https://lists.debian.org/debian-mips/2023/07/msg00057.html

I see. Surprisingly, we don't run into memory issues on hppa and powerpc,
most likely because the buildds are running on 64-bit kernels.

Adrian

-- 
 .''`.  John Paul Adrian Glaubitz
: :' :  Debian Developer
`. `'   Physicist
  `-GPG: 62FF 8A75 84E0 2956 9546  0006 7426 3B37 F5B5 F913

Bug#1013356: fzf: Bash completions not active by default

[Christoph Anton Mitterer]

Just for the records:

The workaround I've proposed before (using something like
/etc/bash_completion.d/fzf) may not be the best way either.

I'm looking into what should be done (see also discussion
at https://github.com/scop/bash-completion/issues/1055), but perhaps
the ideal solution would first require some fzf upstream changes.


Cheers,
Chris.

Bug#1053120: linux-image-6.1.0-12-amd64: Kernel NULL pointer deref with XFS on kernel 6.1

[Salvatore Bonaccorso]

Hi,

On Wed, Sep 27, 2023 at 01:08:21PM -0500, S. wrote:
> Package: src:linux
> Version: 6.1.52-1
> Severity: important
> X-Debbugs-Cc: wfhnb...@duck.com
> 
> Dear Maintainer,
> 
> I have been running Debian 12 on a Hetzner cloud VM since a few weeks before 
> the official Debian 12 Stable release. I did a manual netinstall with an XFS 
> root filesystem. Unfortunately
> I have consistently been having issues approximately every month with kernel 
> crashes that start like this:
> 
> 
> Sep 27 00:49:20 myserver kernel: BUG: kernel NULL pointer dereference, 
> address: 00a2
> Sep 27 00:49:20 myserver kernel: #PF: supervisor read access in kernel mode
> Sep 27 00:49:20 myserver kernel: #PF: error_code(0x) - not-present page
> Sep 27 00:49:20 myserver kernel: Oops:  [#1] PREEMPT SMP NOPTI
> Sep 27 00:49:20 myserver kernel: CPU: 3 PID: 2155714 Comm: postmaster Not 
> tainted 6.1.0-12-amd64 #1  Debian 6.1.52-1
> Sep 27 00:49:20 myserver kernel: Hardware name: Hetzner vServer/Standard PC 
> (Q35 + ICH9, 2009), BIOS 2017 11/11/2017
> Sep 27 00:49:20 myserver kernel: RIP: 0010:next_uptodate_page+0x45/0x1f0
> Sep 27 00:49:20 myserver kernel: Code: 0f 84 2f 01 00 00 48 81 ff 06 04 00 00 
> 0f 84 a3 00 00 00 48 81 ff 02 04 00 00 0f 84 26 01 00 00 40 f6 c7 01 0f 85 8c 
> 00 00 00 <48> 8b 07 a8 01 0f 85 81 00 00 00 8b 47 34 85 c0 74 7a 8d 50 01 4c
> Sep 27 00:49:20 myserver kernel: RSP: :b4de8169bcc0 EFLAGS: 00010246
> Sep 27 00:49:20 myserver kernel: RAX: 00a2 RBX: b4de8169bd18 
> RCX: 03bd
> Sep 27 00:49:20 myserver kernel: RDX: b4de8169bd18 RSI: 960758b9c2b0 
> RDI: 00a2
> Sep 27 00:49:20 myserver kernel: RBP: 960758b9c2b0 R08: 03bd 
> R09: 7f6da3ef5fff
> Sep 27 00:49:20 myserver kernel: R10: 03ae R11:  
> R12: 03bd
> Sep 27 00:49:20 myserver kernel: R13: 960600431260 R14: 960758b9c2b0 
> R15: 9605dc7bedb0
> Sep 27 00:49:20 myserver kernel: FS:  7f6e29110a40() 
> GS:96082bf8() knlGS:
> Sep 27 00:49:20 myserver kernel: CS:  0010 DS:  ES:  CR0: 
> 80050033
> Sep 27 00:49:20 myserver kernel: CR2: 00a2 CR3: 00014a17a000 
> CR4: 00350ee0
> Sep 27 00:49:20 myserver kernel: Call Trace:
> Sep 27 00:49:20 myserver kernel:  
> Sep 27 00:49:20 myserver kernel:  ? __die_body.cold+0x1a/0x1f
> Sep 27 00:49:20 myserver kernel:  ? page_fault_oops+0xd2/0x2b0
> Sep 27 00:49:20 myserver kernel:  ? finish_task_switch.isra.0+0x9b/0x300
> Sep 27 00:49:20 myserver kernel:  ? exc_page_fault+0x70/0x170
> Sep 27 00:49:20 myserver kernel:  ? asm_exc_page_fault+0x22/0x30
> Sep 27 00:49:20 myserver kernel:  ? next_uptodate_page+0x45/0x1f0
> Sep 27 00:49:20 myserver kernel:  filemap_map_pages+0xb0/0x6e0
> Sep 27 00:49:20 myserver kernel:  xfs_filemap_map_pages+0x41/0x60 [xfs]
> Sep 27 00:49:20 myserver kernel:  do_fault+0x1a7/0x410
> Sep 27 00:49:20 myserver kernel:  __handle_mm_fault+0x660/0xfa0
> Sep 27 00:49:20 myserver kernel:  handle_mm_fault+0xdb/0x2d0
> Sep 27 00:49:20 myserver kernel:  do_user_addr_fault+0x19c/0x570
> Sep 27 00:49:20 myserver kernel:  exc_page_fault+0x70/0x170
> Sep 27 00:49:20 myserver kernel:  asm_exc_page_fault+0x22/0x30
> Sep 27 00:49:20 myserver kernel: RIP: 0033:0x7f6e2c752345
> Sep 27 00:49:20 myserver kernel: Code: b4 24 d0 00 00 00 49 89 df 48 89 44 24 
> 38 48 89 fb 4c 89 5c 24 60 eb 12 0f 1f 44 00 00 49 83 c4 04 83 e2 01 0f 85 f2 
> 05 00 00 <41> 8b 04 24 48 89 c2 48 31 d8 48 d1 e8 75 e4 48 83 ec 08 4c 89 e0
> Sep 27 00:49:20 myserver kernel: RSP: 002b:7ffe0d2f29a0 EFLAGS: 00010206
> Sep 27 00:49:20 myserver kernel: RAX: 7ffe0d2f2a14 RBX: 33b7606e 
> RCX: 8003
> Sep 27 00:49:20 myserver kernel: RDX: 7f6d9f67aff4 RSI: 0007 
> RDI: 33b7606e
> Sep 27 00:49:20 myserver kernel: RBP: 0001 R08: 7ffe0d2f2ae0 
> R09: 558ffcfe7aa0
> Sep 27 00:49:20 myserver kernel: R10: 7f6e2b967510 R11: 0011 
> R12: 7f6d9f687fc8
> Sep 27 00:49:20 myserver kernel: R13: 7f6d9dc6b888 R14: 0009 
> R15: 558ffcfe7cb0
> Sep 27 00:49:20 myserver kernel:  
> Sep 27 00:49:20 myserver kernel: Modules linked in: tcp_bbr ipt_REJECT 
> nf_reject_ipv4 xt_multiport xt_nat xt_tcpudp veth xt_conntrack nft_chain_nat 
> xt_MASQUERADE nf_nat nf_conntrack_netlink nf_conntrack nf_defrag_ipv6 
> nf_defrag_ipv4 xfrm_user xfrm_algo xt_addrtype nft_compat nf_tables nfnetlink 
> br_netfilter bridge stp llc overlay binfmt_misc intel_rapl_msr 
> intel_rapl_common ghash_clmulni_intel sha512_ssse3 sha512_generic aesni_intel 
> virtio_gpu crypto_simd cryptd virtio_dma_buf pcspkr iTCO_wdt intel_pmc_bxt 
> virtio_console drm_shmem_helper iTCO_vendor_support watchdog virtio_rng 
> virtio_balloon rng_core drm_kms_helper button joydev evdev sg serio_raw drm 
> loop fuse dm_mod efi_pstore configfs 

Bug#1053126: src:refpolicy: fails to migrate to testing for too long: fails to install

[Paul Gevers]

Source: refpolicy
Version: 2:2.20221101-10
Severity: serious
Control: close -1 2:2.20230919-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 than 30 days as having a Release Critical bug in 
testing [1]. Your package src:refpolicy has been trying to migrate for 
32 days [2]. Hence, I am filing this bug. The version in unstable fails 
to install during piuparts testing and autopkgtest.


If a package is out of sync between unstable and testing for a longer 
period, this usually means that bugs in the package in testing cannot be 
fixed via unstable. Additionally, blocked packages can have impact on 
other packages, which makes preparing for the release more difficult. 
Finally, it often exposes issues with the package and/or
its (reverse-)dependencies. We expect maintainers to fix issues that 
hamper the migration of their package in a timely manner.


This bug will trigger auto-removal when appropriate. As with all new 
bugs, there will be at least 30 days before the package is auto-removed.


I have immediately closed this bug with the version in unstable, so if 
that version or a later version migrates, this bug will no longer affect 
testing. I have also tagged this bug to only affect sid and trixie, so 
it doesn't affect (old-)stable.


If you believe your package is unable to migrate to testing due to 
issues beyond your control, don't hesitate to contact the Release Team.


Paul

[1] https://lists.debian.org/debian-devel-announce/2023/06/msg1.html
[2] https://qa.debian.org/excuses.php?package=refpolicy



OpenPGP_signature.asc
Description: OpenPGP digital signature

Bug#1053127: src:ghc: fails to migrate to testing for too long: uncoordinated transition

[Paul Gevers]

Source: ghc
Version: 9.0.2-5
Severity: serious
Control: close -1 9.4.6-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 than 30 days as having a Release Critical bug in 
testing [1]. Your package src:ghc has been trying to migrate for 32 days 
[2]. Hence, I am filing this bug. The version in unstable makes lots of 
packages non-installable.


If a package is out of sync between unstable and testing for a longer 
period, this usually means that bugs in the package in testing cannot be 
fixed via unstable. Additionally, blocked packages can have impact on 
other packages, which makes preparing for the release more difficult. 
Finally, it often exposes issues with the package and/or
its (reverse-)dependencies. We expect maintainers to fix issues that 
hamper the migration of their package in a timely manner.


This bug will trigger auto-removal when appropriate. As with all new 
bugs, there will be at least 30 days before the package is auto-removed.


I have immediately closed this bug with the version in unstable, so if 
that version or a later version migrates, this bug will no longer affect 
testing. I have also tagged this bug to only affect sid and trixie, so 
it doesn't affect (old-)stable.


If you believe your package is unable to migrate to testing due to 
issues beyond your control, don't hesitate to contact the Release Team.


Paul

[1] https://lists.debian.org/debian-devel-announce/2023/06/msg1.html
[2] https://qa.debian.org/excuses.php?package=ghc



OpenPGP_signature.asc
Description: OpenPGP digital signature

Bug#1053125: src:sphinxcontrib-serializinghtml: fails to migrate to testing for too long: triggers autopkgtest and build failure

[Paul Gevers]

Source: sphinxcontrib-serializinghtml
Version: 1.1.5-2
Severity: serious
Control: close -1 1.1.9-1
Tags: sid trixie
User: release.debian@packages.debian.org
Usertags: out-of-sync
Control: block -1 by 1052779

Dear maintainer(s),

The Release Team considers packages that are out-of-sync between testing 
and unstable for more than 30 days as having a Release Critical bug in 
testing [1]. Your package src:sphinxcontrib-serializinghtml has been 
trying to migrate for 32 days [2]. Hence, I am filing this bug. The 
version in unstable causes issues for sphinxcontrib-websupport: bug 
1052779 and autopkgtest failure.


If a package is out of sync between unstable and testing for a longer 
period, this usually means that bugs in the package in testing cannot be 
fixed via unstable. Additionally, blocked packages can have impact on 
other packages, which makes preparing for the release more difficult. 
Finally, it often exposes issues with the package and/or
its (reverse-)dependencies. We expect maintainers to fix issues that 
hamper the migration of their package in a timely manner.


This bug will trigger auto-removal when appropriate. As with all new 
bugs, there will be at least 30 days before the package is auto-removed.


I have immediately closed this bug with the version in unstable, so if 
that version or a later version migrates, this bug will no longer affect 
testing. I have also tagged this bug to only affect sid and trixie, so 
it doesn't affect (old-)stable.


If you believe your package is unable to migrate to testing due to 
issues beyond your control, don't hesitate to contact the Release Team.


Paul

[1] https://lists.debian.org/debian-devel-announce/2023/06/msg1.html
[2] https://qa.debian.org/excuses.php?package=sphinxcontrib-serializinghtml



OpenPGP_signature.asc
Description: OpenPGP digital signature

Bug#1053124: src:rocrand: fails to migrate to testing for too long: unresolved RC bug

[Paul Gevers]

Source: rocrand
Version: 5.3.3-6
Severity: serious
Control: close -1 5.5.1-2
Tags: sid trixie
User: release.debian@packages.debian.org
Usertags: out-of-sync
Control: block -1 by 1050618

Dear maintainer(s),

The Release Team considers packages that are out-of-sync between testing 
and unstable for more than 30 days as having a Release Critical bug in 
testing [1]. Your package src:rocrand has been trying to migrate for 33 
days [2]. Hence, I am filing this bug. The version in unstable has an 
unresolved RC bug.


If a package is out of sync between unstable and testing for a longer 
period, this usually means that bugs in the package in testing cannot be 
fixed via unstable. Additionally, blocked packages can have impact on 
other packages, which makes preparing for the release more difficult. 
Finally, it often exposes issues with the package and/or
its (reverse-)dependencies. We expect maintainers to fix issues that 
hamper the migration of their package in a timely manner.


This bug will trigger auto-removal when appropriate. As with all new 
bugs, there will be at least 30 days before the package is auto-removed.


I have immediately closed this bug with the version in unstable, so if 
that version or a later version migrates, this bug will no longer affect 
testing. I have also tagged this bug to only affect sid and trixie, so 
it doesn't affect (old-)stable.


If you believe your package is unable to migrate to testing due to 
issues beyond your control, don't hesitate to contact the Release Team.


Paul

[1] https://lists.debian.org/debian-devel-announce/2023/06/msg1.html
[2] https://qa.debian.org/excuses.php?package=rocrand



OpenPGP_signature.asc
Description: OpenPGP digital signature

Bug#1017893: Ships autogenerated files that can't be renegerated with the code in Debian main

[Bastian Germann]

Please do not fix this bug but port bless to gtk-sharp3: #1043275.

Bug#1052144: ghc: Needs to link against libatomic on at least m68k

[Ilias Tsitsimpis]

Hi Adrian,

On Fri, Sep 22, 2023 at 09:20AM, John Paul Adrian Glaubitz wrote:
> The attached patch fixes the issue for me. The underlying problem is
> the use of legacy atomic functions for which no 64-bit variants exist
> on some architectures [1]. See also the upstream discussion here [2].

Is this patch enough, or do we have to backport this [1] as well?

[1] 
https://gitlab.haskell.org/ghc/ghc/-/commit/fc186b0c0ac56d6ff6225d3f6607be37770fcb52

> While this patch fixes the original problem, the stage2 build later
> fails due to memory exhaustion for which I haven't found a solution
> yet.

I faced the same issue on mipsel (see [2]) and never found a solution
for it. Luckily, mipsel got removed from release architectures.

[2] https://lists.debian.org/debian-mips/2023/07/msg00057.html

Best,

-- 
Ilias

Bug#1053123: /usr/share/man/man3/attr.3ncurses.gz: wcolor_set prototype misformatted

[наб]

Package: ncurses-doc
Version: 6.4-4
Severity: normal
File: /usr/share/man/man3/attr.3ncurses.gz

Dear Maintainer,

All other functions' ); is bold, but this wcolor_set's is italic;
this appears to just be a missing \fB:
  \fBint color_set(short \fIpair\fB, void* \fIopts\fB);\fR
  .br
  \fBint wcolor_set(WINDOW *\fIwin\fB, short \fIpair\fB,\fR \fBvoid* 
\fIopts);\fR
  .sp
  \fBint standend(void);\fP

Best,
наб

-- System Information:
Debian Release: 12.1
  APT prefers stable-updates
  APT policy: (500, 'stable-updates'), (500, 'stable-security'), (500, 
'stable-debug'), (500, 'stable')
Architecture: amd64 (x86_64)
Foreign Architectures: i386

Kernel: Linux 6.1.0-9-amd64 (SMP w/24 CPU threads; PREEMPT)
Kernel taint flags: TAINT_PROPRIETARY_MODULE, TAINT_FIRMWARE_WORKAROUND, 
TAINT_OOT_MODULE, TAINT_UNSIGNED_MODULE
Locale: LANG=en_GB.UTF-8, LC_CTYPE=en_GB.UTF-8 (charmap=UTF-8), 
LANGUAGE=en_GB:en
Shell: /bin/sh linked to /usr/bin/dash
Init: systemd (via /run/systemd/system)
LSM: AppArmor: enabled

-- no debconf information


signature.asc
Description: PGP signature

Bug#1052363: bullseye-pu: cups/2.3.3op2-3+deb11u4

[Thorsten Alteholz]

Control: tags 1052363 - moreinfo


On Sat, 23 Sep 2023, Adam D. Barratt wrote:

The same query as for bookworm applies here - do we expect users to
know how to find the patch?


... and the same new text for Bullseye.

  Thorstendiff -Nru cups-2.3.3op2/debian/changelog cups-2.3.3op2/debian/changelog
--- cups-2.3.3op2/debian/changelog  2023-06-24 10:54:05.0 +0200
+++ cups-2.3.3op2/debian/changelog  2023-09-19 21:20:27.0 +0200
@@ -1,3 +1,12 @@
+cups (2.3.3op2-3+deb11u4) bullseye; urgency=medium
+
+  * CVE-2023-4504
+Postscript parsing heap-based buffer overflow
+  * CVE-2023-32360 (Closes: #1051953)
+authentication issue
+
+ -- Thorsten Alteholz   Tue, 19 Sep 2023 21:20:27 +0200
+
 cups (2.3.3op2-3+deb11u3) bullseye; urgency=medium
 
   * CVE-2023-34241 (Closes: #1038885)
diff -Nru cups-2.3.3op2/debian/cups-daemon.NEWS 
cups-2.3.3op2/debian/cups-daemon.NEWS
--- cups-2.3.3op2/debian/cups-daemon.NEWS   2023-06-22 23:22:40.0 
+0200
+++ cups-2.3.3op2/debian/cups-daemon.NEWS   2023-09-19 21:20:27.0 
+0200
@@ -1,3 +1,20 @@
+cups (2.3.3op2-3+deb11u4) bullseye; urgency=medium
+
+  This release addresses a security issue (CVE-2023-32360) which allows
+  unauthorized users to fetch documents over local or remote networks.
+  Since this is a configuration fix, it might be that it does not reach you if 
you
+  are updating 'cups-daemon' (rather than doing a fresh installation).
+  Please double check your /etc/cups/cupds.conf file, whether it limits the 
access
+  to CUPS-Get-Document with something like the following
+  >  
+  >AuthType Default
+  >Require user @OWNER @SYSTEM
+  >Order deny,allow
+  >   
+  (The important line is the 'AuthType Default' in this section)
+
+ -- Thorsten Alteholz   Tue, 19 Sep 2023 21:20:27 +0200
+
 cups (2.1.4-3) unstable; urgency=low
 
   The default ErrorPolicy is changed from 'stop-printer' to 'retry-job',
diff -Nru cups-2.3.3op2/debian/NEWS.Debian cups-2.3.3op2/debian/NEWS.Debian
--- cups-2.3.3op2/debian/NEWS.Debian1970-01-01 01:00:00.0 +0100
+++ cups-2.3.3op2/debian/NEWS.Debian2023-09-19 21:20:27.0 +0200
@@ -0,0 +1,16 @@
+cups (2.3.3op2-3+deb11u4) bullseye; urgency=medium
+
+  This release addresses a security issue (CVE-2023-32360) which allows
+  unauthorized users to fetch documents over local or remote networks.
+  Since this is a configuration fix, it might be that it does not reach you if 
you
+  are updating 'cups-daemon' (rather than doing a fresh installation).
+  Please double check your /etc/cups/cupds.conf file, whether it limits the 
access
+  to CUPS-Get-Document with something like the following
+  >  
+  >AuthType Default
+  >Require user @OWNER @SYSTEM
+  >Order deny,allow
+  >   
+  (The important line is the 'AuthType Default' in this section)
+
+ -- Thorsten Alteholz   Tue, 19 Sep 2023 21:20:27 +0200
diff -Nru cups-2.3.3op2/debian/patches/0019-CVE-2023-32360.patch 
cups-2.3.3op2/debian/patches/0019-CVE-2023-32360.patch
--- cups-2.3.3op2/debian/patches/0019-CVE-2023-32360.patch  1970-01-01 
01:00:00.0 +0100
+++ cups-2.3.3op2/debian/patches/0019-CVE-2023-32360.patch  2023-09-19 
21:20:27.0 +0200
@@ -0,0 +1,27 @@
+From: Thorsten Alteholz 
+Date: Wed, 20 Sep 2023 23:21:42 +0200
+Subject: CVE-2023-32360
+
+---
+ conf/cupsd.conf.in | 8 +++-
+ 1 file changed, 7 insertions(+), 1 deletion(-)
+
+diff --git a/conf/cupsd.conf.in b/conf/cupsd.conf.in
+index 09059dc..67d1c8b 100644
+--- a/conf/cupsd.conf.in
 b/conf/cupsd.conf.in
+@@ -65,7 +65,13 @@ WebInterface @CUPS_WEBIF@
+ Order deny,allow
+   
+ 
+-  
++  
++Require user @OWNER @SYSTEM
++Order deny,allow
++  
++
++  
++AuthType Default
+ Require user @OWNER @SYSTEM
+ Order deny,allow
+   
diff -Nru cups-2.3.3op2/debian/patches/0020-CVE-2023-4504.patch 
cups-2.3.3op2/debian/patches/0020-CVE-2023-4504.patch
--- cups-2.3.3op2/debian/patches/0020-CVE-2023-4504.patch   1970-01-01 
01:00:00.0 +0100
+++ cups-2.3.3op2/debian/patches/0020-CVE-2023-4504.patch   2023-09-19 
21:20:27.0 +0200
@@ -0,0 +1,33 @@
+From: Thorsten Alteholz 
+Date: Wed, 20 Sep 2023 23:22:44 +0200
+Subject: CVE-2023-4504
+
+---
+ cups/raster-interpret.c | 14 +-
+ 1 file changed, 13 insertions(+), 1 deletion(-)
+
+diff --git a/cups/raster-interpret.c b/cups/raster-interpret.c
+index fbe52f3..89ef158 100644
+--- a/cups/raster-interpret.c
 b/cups/raster-interpret.c
+@@ -1113,7 +1113,19 @@ scan_ps(_cups_ps_stack_t *st,   /* I  - Stack */
+ 
+   cur ++;
+ 
+-if (*cur == 'b')
++ /*
++  * Return NULL if we reached NULL terminator, a lone backslash
++* is not a valid character in PostScript.
++  */
++
++  if (!*cur)
++  {
++*ptr = NULL;
++
++return (NULL);
++  }
++
++  if (*cur == 'b')
+ *valptr++ = '\b';
+   else if (*cur == 'f')
+ 

Bug#1052361: bookworm-pu: cups/2.4.2-3+deb12u2

[Thorsten Alteholz]

Control: tags 1052361 - moreinfo

Hi Adam,

On Sat, 23 Sep 2023, Adam D. Barratt wrote:

Hmm. Is there a better way we can point users to the required change
here that doesn't require them knowing how to find patches applied to
the source package?


yes, *sigh* the wording was bad and I also mangled the version numbers, 
sorry.
What do you think of this version, which was thankfully provided by 
IOhannes?


  Thorstendiff -Nru cups-2.4.2/debian/changelog cups-2.4.2/debian/changelog
--- cups-2.4.2/debian/changelog 2023-06-24 10:54:05.0 +0200
+++ cups-2.4.2/debian/changelog 2023-09-19 21:20:27.0 +0200
@@ -1,3 +1,12 @@
+cups (2.4.2-3+deb12u2) bookworm; urgency=medium
+
+  * CVE-2023-4504
+Postscript parsing heap-based buffer overflow
+  * CVE-2023-32360 (Closes: #1051953)
+authentication issue
+
+ -- Thorsten Alteholz   Tue, 19 Sep 2023 21:20:27 +0200
+
 cups (2.4.2-3+deb12u1) bookworm; urgency=medium
 
   * CVE-2023-34241 (Closes: #1038885)
diff -Nru cups-2.4.2/debian/cups-daemon.NEWS cups-2.4.2/debian/cups-daemon.NEWS
--- cups-2.4.2/debian/cups-daemon.NEWS  2023-06-22 23:22:40.0 +0200
+++ cups-2.4.2/debian/cups-daemon.NEWS  2023-09-19 21:20:27.0 +0200
@@ -1,3 +1,20 @@
+cups (2.4.2-3+deb12u2) bookworm; urgency=medium
+
+  This release addresses a security issue (CVE-2023-32360) which allows
+  unauthorized users to fetch documents over local or remote networks.
+  Since this is a configuration fix, it might be that it does not reach you if 
you
+  are updating 'cups-daemon' (rather than doing a fresh installation).
+  Please double check your /etc/cups/cupds.conf file, whether it limits the 
access
+  to CUPS-Get-Document with something like the following
+  >  
+  >AuthType Default
+  >Require user @OWNER @SYSTEM
+  >Order deny,allow
+  >   
+  (The important line is the 'AuthType Default' in this section)
+
+ -- Thorsten Alteholz   Tue, 19 Sep 2023 21:20:27 +0200
+
 cups (2.1.4-3) unstable; urgency=low
 
   The default ErrorPolicy is changed from 'stop-printer' to 'retry-job',
diff -Nru cups-2.4.2/debian/NEWS.Debian cups-2.4.2/debian/NEWS.Debian
--- cups-2.4.2/debian/NEWS.Debian   1970-01-01 01:00:00.0 +0100
+++ cups-2.4.2/debian/NEWS.Debian   2023-09-19 21:20:27.0 +0200
@@ -0,0 +1,16 @@
+cups (2.4.2-3+deb12u2) bookworm; urgency=medium
+
+  This release addresses a security issue (CVE-2023-32360) which allows
+  unauthorized users to fetch documents over local or remote networks.
+  Since this is a configuration fix, it might be that it does not reach you if 
you
+  are updating 'cups-daemon' (rather than doing a fresh installation).
+  Please double check your /etc/cups/cupds.conf file, whether it limits the 
access
+  to CUPS-Get-Document with something like the following
+  >  
+  >AuthType Default
+  >Require user @OWNER @SYSTEM
+  >Order deny,allow
+  >   
+  (The important line is the 'AuthType Default' in this section)
+
+ -- Thorsten Alteholz   Tue, 19 Sep 2023 21:20:27 +0200
diff -Nru cups-2.4.2/debian/patches/0015-CVE-2023-4504.patch 
cups-2.4.2/debian/patches/0015-CVE-2023-4504.patch
--- cups-2.4.2/debian/patches/0015-CVE-2023-4504.patch  1970-01-01 
01:00:00.0 +0100
+++ cups-2.4.2/debian/patches/0015-CVE-2023-4504.patch  2023-09-19 
21:20:27.0 +0200
@@ -0,0 +1,33 @@
+From: Thorsten Alteholz 
+Date: Wed, 20 Sep 2023 04:55:44 +0200
+Subject: CVE-2023-4504
+
+---
+ cups/raster-interpret.c | 14 +-
+ 1 file changed, 13 insertions(+), 1 deletion(-)
+
+diff --git a/cups/raster-interpret.c b/cups/raster-interpret.c
+index fbe52f3..89ef158 100644
+--- a/cups/raster-interpret.c
 b/cups/raster-interpret.c
+@@ -1113,7 +1113,19 @@ scan_ps(_cups_ps_stack_t *st,   /* I  - Stack */
+ 
+   cur ++;
+ 
+-if (*cur == 'b')
++ /*
++  * Return NULL if we reached NULL terminator, a lone backslash
++* is not a valid character in PostScript.
++  */
++
++  if (!*cur)
++  {
++*ptr = NULL;
++
++return (NULL);
++  }
++
++  if (*cur == 'b')
+ *valptr++ = '\b';
+   else if (*cur == 'f')
+ *valptr++ = '\f';
diff -Nru cups-2.4.2/debian/patches/0016-CVE-2023-32360.patch 
cups-2.4.2/debian/patches/0016-CVE-2023-32360.patch
--- cups-2.4.2/debian/patches/0016-CVE-2023-32360.patch 1970-01-01 
01:00:00.0 +0100
+++ cups-2.4.2/debian/patches/0016-CVE-2023-32360.patch 2023-09-19 
21:20:27.0 +0200
@@ -0,0 +1,27 @@
+From: Thorsten Alteholz 
+Date: Wed, 20 Sep 2023 04:56:47 +0200
+Subject: CVE-2023-32360
+
+---
+ conf/cupsd.conf.in | 8 +++-
+ 1 file changed, 7 insertions(+), 1 deletion(-)
+
+diff --git a/conf/cupsd.conf.in b/conf/cupsd.conf.in
+index b258849..a07536f 100644
+--- a/conf/cupsd.conf.in
 b/conf/cupsd.conf.in
+@@ -68,7 +68,13 @@ IdleExitTimeout @EXIT_TIMEOUT@
+ Order deny,allow
+   
+ 
+-  
++  
++Require user @OWNER @SYSTEM
++ 

Bug#1051752: [pkg-uWSGI-devel] Bug#1051752: uwsgi: remove uwsgi-plugin-glusterfs on 32 bit architectures)

[Alexandre Rossi]

Hi Jonas,

> > If I get some advice on the best practrices for having d/control.in with
> > template variables, I would be happy to work on this.
> 
> I assume you mean the debian/control file (as the uwsgi source package
> currently contains no debian/control.in file).
> That file gets mangled when the following command is executed:
> 
>   DEB_MAINTAINER_MODE=1 debian/control clean

I thought that using some template engine and introducing d/control.in
would be easier to maintain, debug than the current mangling and was wondering
what was considered good practice for this in Debian packaging.

I'll research.

Thanks for the upload,

Alex

Bug#1053122: linux-image-6.5.0-1-amd64: using smp_processor_id() in preemptible

[Gabriel Francisco]

Package: src:linux
Version: 6.5.3-1
Severity: important
Tags: upstream
X-Debbugs-Cc: frc.gabr...@gmail.com

Dear Maintainer,

First of all thanks for your hard work!

I noticed my computer started freezing for few seconds when entering/exiting
full screen videos in youtube using firefox and while trying to check if the
issue also afected chromium I saw the following message in dmesg:

[12569.564300] BUG: unable to handle page fault for address: 991989e936b8
[12569.564304] #PF: supervisor write access in kernel mode
[12569.564306] #PF: error_code(0x0002) - not-present page
[12569.564308] PGD 0 P4D 0 
[12569.564311] Oops: 0002 [#1] PREEMPT SMP NOPTI
[12569.564314] CPU: 10 PID: 328649 Comm: Chroot Helper Not tainted 
6.5.0-1-amd64 #1  Debian 6.5.3-1
[12569.564317] Hardware name: ASUS System Product Name/ROG STRIX B550-F GAMING 
WIFI II, BIOS 3205 08/14/2023
[12569.564318] RIP: 0010:down_write+0x23/0x70
[12569.564324] Code: 90 90 90 90 90 90 90 f3 0f 1e fa 0f 1f 44 00 00 53 48 89 
fb e8 2e bc ff ff bf 01 00 00 00 e8 74 3a 53 ff 31 c0 ba 01 00 00 00  48 0f 
b1 13 75 33 65 48 8b 04 25 80 29 03 00 48 89 43 08 bf 01
[12569.564326] RSP: 0018:a189d736fc70 EFLAGS: 00010246
[12569.564328] RAX:  RBX: 991989e936b8 RCX: 891797aaef00
[12569.564330] RDX: 0001 RSI: 891989e645c0 RDI: 8e7c95dc
[12569.564331] RBP:  R08: 0060 R09: 80400014
[12569.564333] R10: 8918cbfeb7f8 R11: 0006 R12: 7f7e5fd0
[12569.564334] R13: 0001 R14: 891989e645c0 R15: 891989e64958
[12569.564336] FS:  () GS:891c8ec8() 
knlGS:
[12569.564338] CS:  0010 DS:  ES:  CR0: 80050033
[12569.564339] CR2: 991989e936b8 CR3: 0002c522 CR4: 00750ee0
[12569.564341] PKRU: 5554
[12569.564342] Call Trace:
[12569.564345]  
[12569.564347]  ? __die+0x23/0x70
[12569.564351]  ? page_fault_oops+0x171/0x4f0
[12569.564354]  ? srso_alias_return_thunk+0x5/0x7f
[12569.564358]  ? exc_page_fault+0x175/0x180
[12569.564362]  ? asm_exc_page_fault+0x26/0x30
[12569.564367]  ? down_write+0x1c/0x70
[12569.564370]  ? down_write+0x23/0x70
[12569.564373]  free_pgtables+0x1ba/0x1d0
[12569.564379]  exit_mmap+0x141/0x310
[12569.564385]  __mmput+0x3e/0x130
[12569.564389]  do_exit+0x305/0xb20
[12569.564393]  do_group_exit+0x31/0x80
[12569.564396]  __x64_sys_exit_group+0x18/0x20
[12569.564398]  do_syscall_64+0x60/0xc0
[12569.564401]  ? preempt_count_add+0x4b/0xa0
[12569.564404]  ? srso_alias_return_thunk+0x5/0x7f
[12569.564407]  ? up_read+0x3b/0x80
[12569.564410]  ? srso_alias_return_thunk+0x5/0x7f
[12569.564412]  ? do_user_addr_fault+0x235/0x640
[12569.564415]  ? srso_alias_return_thunk+0x5/0x7f
[12569.564417]  ? fpregs_assert_state_consistent+0x26/0x50
[12569.564419]  ? srso_alias_return_thunk+0x5/0x7f
[12569.564422]  ? exit_to_user_mode_prepare+0x40/0x1d0
[12569.564425]  entry_SYSCALL_64_after_hwframe+0x6e/0xd8
[12569.564428] RIP: 0033:0x7f7e9e6f1995
[12569.564430] Code: Unable to access opcode bytes at 0x7f7e9e6f196b.
[12569.564432] RSP: 002b:7f7e798bd288 EFLAGS: 0206 ORIG_RAX: 
00e7
[12569.564434] RAX: ffda RBX: 7f7e6aa5bee0 RCX: 7f7e9e6f1995
[12569.564435] RDX: 00e7 RSI: ff48 RDI: 
[12569.564437] RBP: 7f7e798bd298 R08:  R09: 
[12569.564438] R10: 7f7e9e630178 R11: 0206 R12: 000b
[12569.564440] R13:  R14: 7f7e6aa5bee0 R15: 7f7e798bd560
[12569.56]  
[12569.564445] Modules linked in: uinput mptcp_diag xsk_diag tcp_diag udp_diag 
raw_diag inet_diag unix_diag af_packet_diag netlink_diag tls rfcomm 
nf_conntrack_netlink xfrm_user xfrm_algo snd_seq_dummy snd_hrtimer snd_seq 
snd_seq_device nvme_fabrics ctr ccm qrtr overlay nfnetlink_log cmac lz4 
lz4_compress algif_hash zram algif_skcipher zsmalloc af_alg bnep wireguard 
libchacha20poly1305 chacha_x86_64 poly1305_x86_64 curve25519_x86_64 
libcurve25519_generic libchacha ip6_udp_tunnel udp_tunnel nls_ascii nls_cp437 
vfat fat nft_chain_nat xt_MASQUERADE nf_nat xt_addrtype xt_comment xt_conntrack 
nf_conntrack nf_defrag_ipv6 nf_defrag_ipv4 xt_multiport ipt_REJECT 
nf_reject_ipv4 xt_CHECKSUM xt_tcpudp nft_compat nf_tables mt7921e btusb 
mt7921_common btrtl btbcm btintel mt76_connac_lib btmtk mt76 intel_rapl_msr 
intel_rapl_common bluetooth mac80211 snd_hda_codec_realtek sha3_generic 
jitterentropy_rng snd_hda_codec_generic edac_mce_amd snd_hda_codec_hdmi 
binfmt_misc drbg ip_set_hash_net ansi_cprng kvm_amd ip_set snd_hda_intel
[12569.564507]  snd_intel_dspcfg ecdh_generic libarc4 snd_intel_sdw_acpi ecc 
nfnetlink eeepc_wmi asus_nb_wmi kvm snd_hda_codec cfg80211 asus_wmi battery 
snd_hda_core ledtrig_audio snd_hwdep irqbypass sparse_keymap snd_pcm 
platform_profile rapl snd_timer rfkill wmi_bmof snd sp5100_tco ccp soundcore 
watchdog k10temp nct6775 nct6775_core joydev 

Bug#1053121: calamares: Welcome screen does not update power source status

[Darshaka Pathirana]

Package: calamares
Version: 3.2.61-1+b1
Severity: minor

Dear Maintainer,

when starting the Calamares installer is started (in Debian Live/Cinnamon), if
the system is not connected to a power source, the installer reports "The
system is not plugged in to a power source". This is fine.

But when the user then connects a power source, the message does not disappear,
making the user wonder if the power source is really connected.

The message should disappear as soon as the power source is plugged in (and
most probably vice-versa).

Thanks for maintaining calamares!

Best,
 - Darsha

-- System Information:
Debian Release: 12.1
  APT prefers bookworm
  APT policy: (500, 'bookworm'), (500, 'stable')
Architecture: amd64 (x86_64)

Kernel: Linux 6.1.0-10-amd64 (SMP w/12 CPU threads; PREEMPT)
Locale: LANG=en_US.UTF-8, LC_CTYPE=en_US.UTF-8 (charmap=UTF-8), LANGUAGE not set
Shell: /bin/sh linked to /usr/bin/dash
Init: systemd (via /run/systemd/system)
LSM: AppArmor: enabled

Versions of packages calamares depends on:
ii  kpackagetool55.103.0-1
ii  libboost-python1.74.0 [libboost-python1.74.0-py311]  1.74.0+ds1-21
ii  libc62.36-9+deb12u1
ii  libcrypt11:4.4.33-2
ii  libgcc-s112.2.0-14
ii  libkf5configcore55.103.0-2
ii  libkf5coreaddons55.103.0-1
ii  libkf5package5   5.103.0-1
ii  libkf5parts5 5.103.0-1
ii  libkpmcore12 22.12.3-1
ii  libparted2   3.5-3
ii  libpwquality11.4.5-1+b1
ii  libpython3.113.11.2-6
ii  libqt5core5a 5.15.8+dfsg-11
ii  libqt5dbus5  5.15.8+dfsg-11
ii  libqt5gui5   5.15.8+dfsg-11
ii  libqt5network5   5.15.8+dfsg-11
ii  libqt5qml5   5.15.8+dfsg-3
ii  libqt5quick5 5.15.8+dfsg-3
ii  libqt5quickwidgets5  5.15.8+dfsg-3
ii  libqt5svg5   5.15.8-3
ii  libqt5webkit55.212.0~alpha4-30
ii  libqt5widgets5   5.15.8+dfsg-11
ii  libqt5xml5   5.15.8+dfsg-11
ii  libstdc++6   12.2.0-14
ii  libyaml-cpp0.7   0.7.0+dfsg-8+b1
ii  os-prober1.81

Versions of packages calamares recommends:
ii  btrfs-progs 6.2-1
ii  squashfs-tools  1:4.5.1-1

calamares suggests no packages.

-- no debconf information

Bug#1052363: bullseye-pu: cups/2.3.3op2-3+deb11u4

[Adam D. Barratt]

Control: tags -1 confirmed

On Wed, 2023-09-27 at 17:44 +, Thorsten Alteholz wrote:
> Control: tags 1052363 - moreinfo
> 
> 
> On Sat, 23 Sep 2023, Adam D. Barratt wrote:
> > The same query as for bookworm applies here - do we expect users to
> > know how to find the patch?
> 
> ... and the same new text for Bullseye.
> 

Thanks; please go ahead.

Regards,

Adam

Bug#1052361: bookworm-pu: cups/2.4.2-3+deb12u2

[Adam D. Barratt]

Control: tags -1 confirmed

On Wed, 2023-09-27 at 17:43 +, Thorsten Alteholz wrote:
> Control: tags 1052361 - moreinfo
> 
> Hi Adam,
> 
> On Sat, 23 Sep 2023, Adam D. Barratt wrote:
> > Hmm. Is there a better way we can point users to the required
> > change
> > here that doesn't require them knowing how to find patches applied
> > to
> > the source package?
> 
> yes, *sigh* the wording was bad and I also mangled the version
> numbers, 
> sorry.
> What do you think of this version, which was thankfully provided by 
> IOhannes?
> 

Much better, thanks. :-)

Please go ahead.

Regards,

Adam

Bug#1052059: closed by Debian FTP Masters (reply to Guilhem Moulin ) (Bug#1052059: fixed in roundcube 1.4.14+dfsg.1-1~deb11u1)

[Martin Dosch]

Dear Guilhem,

thank you very much for taking care of this. :)

Best regards,
Martin

On 27.09.2023 18:33, Debian Bug Tracking System wrote:

This is an automatic notification regarding your Bug report
which was filed against the roundcube package:

#1052059: roundcube: CVE-2023-43770: XSS vulnerability in handling of linkrefs 
in plain text messages

It has been closed by Debian FTP Masters  (reply to 
Guilhem Moulin ).

Their explanation is attached below along with your original report.
If this explanation is unsatisfactory and you have not received a
better one in a separate message then please contact Debian FTP Masters 
 (reply to Guilhem Moulin 
) by
replying to this email.


--
1052059: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1052059
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems



Date: Wed, 27 Sep 2023 18:32:31 +
From: Debian FTP Masters 
To: 1052059-cl...@bugs.debian.org
Subject: Bug#1052059: fixed in roundcube 1.4.14+dfsg.1-1~deb11u1

Source: roundcube
Source-Version: 1.4.14+dfsg.1-1~deb11u1
Done: Guilhem Moulin 

We believe that the bug you reported is fixed in the latest version of
roundcube, which is due to be installed in the Debian FTP archive.

A summary of the changes between this version and the previous one is
attached.

Thank you for reporting the bug, which will now be closed.  If you
have further comments please address them to 1052...@bugs.debian.org,
and the maintainer will reopen the bug report if appropriate.

Debian distribution maintenance software
pp.
Guilhem Moulin  (supplier of updated roundcube package)

(This message was generated automatically at their request; if you
believe that there is a problem with it please contact the archive
administrators by mailing ftpmas...@ftp-master.debian.org)


-BEGIN PGP SIGNED MESSAGE-
Hash: SHA512

Format: 1.8
Date: Mon, 25 Sep 2023 11:32:59 +0200
Source: roundcube
Architecture: source
Version: 1.4.14+dfsg.1-1~deb11u1
Distribution: bullseye
Urgency: high
Maintainer: Debian Roundcube Maintainers 

Changed-By: Guilhem Moulin 
Closes: 1052059
Changes:
roundcube (1.4.14+dfsg.1-1~deb11u1) bullseye; urgency=high
.
  * New security/bugfix upstream release:
+ Fix CVE-2023-43770: cross-site scripting (XSS) vulnerability in handling
  of linkrefs in plain text messages. (Closes: #1052059)
+ Enigma: Fix initial synchronization of private keys.
  * d/u/signing-key.asc: Add Alec's key BEE674A019359DC1.
  * Refresh d/patches.
Checksums-Sha1:
03ff1569103e0bc2b1624508244174164c791a1e 3273 
roundcube_1.4.14+dfsg.1-1~deb11u1.dsc
af31fa3812ab1cd0629bb924a255e654fc6e5904 128856 
roundcube_1.4.14+dfsg.1.orig-tinymce-langs.tar.xz
679a15643cba8d1f9413e0d98bd8e6986d893b28 889132 
roundcube_1.4.14+dfsg.1.orig-tinymce.tar.xz
5b83ebfa6481eea55f1f2f6ce2eb01a9b6e95a61 2976108 
roundcube_1.4.14+dfsg.1.orig.tar.xz
850fe4072f27d3195bdd7424f3c01134e59ef869 94968 
roundcube_1.4.14+dfsg.1-1~deb11u1.debian.tar.xz
053d2fcbb21816af133e4c94312be9119a6f2f51 10821 
roundcube_1.4.14+dfsg.1-1~deb11u1_amd64.buildinfo
Checksums-Sha256:
eb664fd1a08be44630c25cbfe897b087a4b1e8c3d72da407c0fb7fd797f8be2e 3273 
roundcube_1.4.14+dfsg.1-1~deb11u1.dsc
652859555790d44159521c22ea9d43eb8a05b5eb4728760ba6ea02676ea9ad06 128856 
roundcube_1.4.14+dfsg.1.orig-tinymce-langs.tar.xz
570038d21a89986e238582359a8d864bdd13e3fc47e322c88a9d0dc0f29baf01 889132 
roundcube_1.4.14+dfsg.1.orig-tinymce.tar.xz
116f5129984fc38d1441e475a42896470e105db8c8e1092a963133643f7925e0 2976108 
roundcube_1.4.14+dfsg.1.orig.tar.xz
b03d8140e3f7f96eae5b0d73f4c5a19cffc8584ce46035068889433e6c5fdc65 94968 
roundcube_1.4.14+dfsg.1-1~deb11u1.debian.tar.xz
89bc15af5d6e6c7ff2eaf3b8b1ae93dd2e0ba6130d9d68af5655bd8625052316 10821 
roundcube_1.4.14+dfsg.1-1~deb11u1_amd64.buildinfo
Files:
ce4e93c339a78d6d2585ad3549c1e3d9 3273 web optional 
roundcube_1.4.14+dfsg.1-1~deb11u1.dsc
1cd21dbf082a39086f80035274ae0505 128856 web optional 
roundcube_1.4.14+dfsg.1.orig-tinymce-langs.tar.xz
0bed51c23db9c8bb84b56a9403acf47d 889132 web optional 
roundcube_1.4.14+dfsg.1.orig-tinymce.tar.xz
b12f36a36d6fa76a9644878d7482b1de 2976108 web optional 
roundcube_1.4.14+dfsg.1.orig.tar.xz
c8144dce52d1c3b4a110f5d3c60d5380 94968 web optional 
roundcube_1.4.14+dfsg.1-1~deb11u1.debian.tar.xz
63a1a7c4457511942108958a6340a901 10821 web optional 
roundcube_1.4.14+dfsg.1-1~deb11u1_amd64.buildinfo

-BEGIN PGP SIGNATURE-

iQIzBAEBCgAdFiEERpy6p3b9sfzUdbME05pJnDwhpVIFAmURV70ACgkQ05pJnDwh
pVKrYhAAlmDTcICPdEbl1XeLMXX7/5y5+l9+G23U3O6iBCyCLtQfkA8gwyINnnIV
iMIgGRSdidy0u6wDpG4KSGI51W3eLCyGbevpDY4kb+4dc8DQVv0Ak+wxIKC1207n
oe5xXib3K4JLdR+Osn0IegypDDiyph9YZKiAW2/rS+L9fniNf5ji2MuWNODDc6ZY
Zhe1xOf2L66drm1hcdiH5mtpLvkNMwNABu27sFm3VL49pjNTKVNLck4N2klN9T1R
E7YPQI2EH+7mVN41gOqBzrhnF8W5jQMJHss9cw2SC9QMyZ4RGGEAO636BovlSAiy
SLWy9625jQp58R8BTL2dEsVDvKzMgESOy8B2AWN+Zo22pSAkp9Ry5raCZK2U7kqR
QE62AQnneETspQRo6o0KPoTYZjj+gAMHUYbYCy4UrCD+w3YInpzLoICS4i7gAvxu
Yt/xQYBPCVmAgNOZYW2Xx3dAh9BN8hrOCn+ofBB7eTAMrgH2pPbUBvh58J2J6w5i

Bug#1052710: modsecurity 3.0.9-1+deb12u1 flagged for acceptance

[Adam D Barratt]

package release.debian.org
tags 1052710 = bookworm pending
thanks

Hi,

The upload referenced by this bug report has been flagged for acceptance into 
the proposed-updates queue for Debian bookworm.

Thanks for your contribution!

Upload details
==

Package: modsecurity
Version: 3.0.9-1+deb12u1

Explanation: fix denial of service issue [CVE-2023-38285]

Bug#1053001: openssl 3.0.11-1~deb12u1 flagged for acceptance

[Adam D Barratt]

package release.debian.org
tags 1053001 = bookworm pending
thanks

Hi,

The upload referenced by this bug report has been flagged for acceptance into 
the proposed-updates queue for Debian bookworm.

Thanks for your contribution!

Upload details
==

Package: openssl
Version: 3.0.11-1~deb12u1

Explanation: new upstream stable release

Bug#1052698: flann 1.9.2+dfsg-1+deb12u1 flagged for acceptance

[Adam D Barratt]

package release.debian.org
tags 1052698 = bookworm pending
thanks

Hi,

The upload referenced by this bug report has been flagged for acceptance into 
the proposed-updates queue for Debian bookworm.

Thanks for your contribution!

Upload details
==

Package: flann
Version: 1.9.2+dfsg-1+deb12u1

Explanation: drop extra -llz4 from flann.pc

Bug#1052648: unbound 1.17.1-2+deb12u1 flagged for acceptance

[Adam D Barratt]

package release.debian.org
tags 1052648 = bookworm pending
thanks

Hi,

The upload referenced by this bug report has been flagged for acceptance into 
the proposed-updates queue for Debian bookworm.

Thanks for your contribution!

Upload details
==

Package: unbound
Version: 1.17.1-2+deb12u1

Explanation: fix error log flooding when using DNS over TLS with openssl 3.0

Bug#1052611: roundcube 1.4.14+dfsg.1-1~deb11u1 flagged for acceptance

[Adam D Barratt]

package release.debian.org
tags 1052611 = bullseye pending
thanks

Hi,

The upload referenced by this bug report has been flagged for acceptance into 
the proposed-updates queue for Debian bullseye.

Thanks for your contribution!

Upload details
==

Package: roundcube
Version: 1.4.14+dfsg.1-1~deb11u1

Explanation: new upstream stable release; fix cross-site scripting issue 
[CVE-2023-43770]; Enigma: Fix initial synchronization of private keys

Bug#1051384: highway 1.0.3-3+deb12u1 flagged for acceptance

[Adam D Barratt]

package release.debian.org
tags 1051384 = bookworm pending
thanks

Hi,

The upload referenced by this bug report has been flagged for acceptance into 
the proposed-updates queue for Debian bookworm.

Thanks for your contribution!

Upload details
==

Package: highway
Version: 1.0.3-3+deb12u1

Explanation: fix support for armhf systems lacking NEON

Bug#1052828: trurl: FTBFS: dh_auto_test: error: make -j8 test returned exit code 2

[Michael Ablassmeier]

hi,

On Tue, Sep 26, 2023 at 07:28:20PM +0200, Michael Ablassmeier wrote:
> version either with patch or more recent upstream
> version.

patch that addresses this issue and 0.8-2 ready to upload at salsa git. Carlos:
do you want to upload?

bye,
- michael

Bug#1053112: cockpit FTBFS when systemd.pc changes systemdsystemunitdir

[Martin Pitt]

Control: forwarded -1 https://github.com/cockpit-project/cockpit/pull/19407
Control: tag -1 upstream pending

Hello Helmut,

Helmut Grohne [2023-09-27 13:46 +0200]:
> We want to change the value of systemdsystemunitdir in systemd.pc to
> point below /usr. cockpit's upstream build system consumes this variable
> while the packaging hard codes its current value. When we change it,
> cockpit will FTBFS. Consider applying the attached patch to avoid the
> failure.

Thanks! I'll handle that via upstream, see the above GitHub PR. That will still
require some CI juggling, but I'll deal with that tomorrow.

Thanks,

Martin

Bug#1053120: linux-image-6.1.0-12-amd64: Kernel NULL pointer deref with XFS on kernel 6.1

[S.]

Package: src:linux
Version: 6.1.52-1
Severity: important
X-Debbugs-Cc: wfhnb...@duck.com

Dear Maintainer,

I have been running Debian 12 on a Hetzner cloud VM since a few weeks before 
the official Debian 12 Stable release. I did a manual netinstall with an XFS 
root filesystem. Unfortunately
I have consistently been having issues approximately every month with kernel 
crashes that start like this:


Sep 27 00:49:20 myserver kernel: BUG: kernel NULL pointer dereference, address: 
00a2
Sep 27 00:49:20 myserver kernel: #PF: supervisor read access in kernel mode
Sep 27 00:49:20 myserver kernel: #PF: error_code(0x) - not-present page
Sep 27 00:49:20 myserver kernel: Oops:  [#1] PREEMPT SMP NOPTI
Sep 27 00:49:20 myserver kernel: CPU: 3 PID: 2155714 Comm: postmaster Not 
tainted 6.1.0-12-amd64 #1  Debian 6.1.52-1
Sep 27 00:49:20 myserver kernel: Hardware name: Hetzner vServer/Standard PC 
(Q35 + ICH9, 2009), BIOS 2017 11/11/2017
Sep 27 00:49:20 myserver kernel: RIP: 0010:next_uptodate_page+0x45/0x1f0
Sep 27 00:49:20 myserver kernel: Code: 0f 84 2f 01 00 00 48 81 ff 06 04 00 00 
0f 84 a3 00 00 00 48 81 ff 02 04 00 00 0f 84 26 01 00 00 40 f6 c7 01 0f 85 8c 
00 00 00 <48> 8b 07 a8 01 0f 85 81 00 00 00 8b 47 34 85 c0 74 7a 8d 50 01 4c
Sep 27 00:49:20 myserver kernel: RSP: :b4de8169bcc0 EFLAGS: 00010246
Sep 27 00:49:20 myserver kernel: RAX: 00a2 RBX: b4de8169bd18 
RCX: 03bd
Sep 27 00:49:20 myserver kernel: RDX: b4de8169bd18 RSI: 960758b9c2b0 
RDI: 00a2
Sep 27 00:49:20 myserver kernel: RBP: 960758b9c2b0 R08: 03bd 
R09: 7f6da3ef5fff
Sep 27 00:49:20 myserver kernel: R10: 03ae R11:  
R12: 03bd
Sep 27 00:49:20 myserver kernel: R13: 960600431260 R14: 960758b9c2b0 
R15: 9605dc7bedb0
Sep 27 00:49:20 myserver kernel: FS:  7f6e29110a40() 
GS:96082bf8() knlGS:
Sep 27 00:49:20 myserver kernel: CS:  0010 DS:  ES:  CR0: 
80050033
Sep 27 00:49:20 myserver kernel: CR2: 00a2 CR3: 00014a17a000 
CR4: 00350ee0
Sep 27 00:49:20 myserver kernel: Call Trace:
Sep 27 00:49:20 myserver kernel:  
Sep 27 00:49:20 myserver kernel:  ? __die_body.cold+0x1a/0x1f
Sep 27 00:49:20 myserver kernel:  ? page_fault_oops+0xd2/0x2b0
Sep 27 00:49:20 myserver kernel:  ? finish_task_switch.isra.0+0x9b/0x300
Sep 27 00:49:20 myserver kernel:  ? exc_page_fault+0x70/0x170
Sep 27 00:49:20 myserver kernel:  ? asm_exc_page_fault+0x22/0x30
Sep 27 00:49:20 myserver kernel:  ? next_uptodate_page+0x45/0x1f0
Sep 27 00:49:20 myserver kernel:  filemap_map_pages+0xb0/0x6e0
Sep 27 00:49:20 myserver kernel:  xfs_filemap_map_pages+0x41/0x60 [xfs]
Sep 27 00:49:20 myserver kernel:  do_fault+0x1a7/0x410
Sep 27 00:49:20 myserver kernel:  __handle_mm_fault+0x660/0xfa0
Sep 27 00:49:20 myserver kernel:  handle_mm_fault+0xdb/0x2d0
Sep 27 00:49:20 myserver kernel:  do_user_addr_fault+0x19c/0x570
Sep 27 00:49:20 myserver kernel:  exc_page_fault+0x70/0x170
Sep 27 00:49:20 myserver kernel:  asm_exc_page_fault+0x22/0x30
Sep 27 00:49:20 myserver kernel: RIP: 0033:0x7f6e2c752345
Sep 27 00:49:20 myserver kernel: Code: b4 24 d0 00 00 00 49 89 df 48 89 44 24 
38 48 89 fb 4c 89 5c 24 60 eb 12 0f 1f 44 00 00 49 83 c4 04 83 e2 01 0f 85 f2 
05 00 00 <41> 8b 04 24 48 89 c2 48 31 d8 48 d1 e8 75 e4 48 83 ec 08 4c 89 e0
Sep 27 00:49:20 myserver kernel: RSP: 002b:7ffe0d2f29a0 EFLAGS: 00010206
Sep 27 00:49:20 myserver kernel: RAX: 7ffe0d2f2a14 RBX: 33b7606e 
RCX: 8003
Sep 27 00:49:20 myserver kernel: RDX: 7f6d9f67aff4 RSI: 0007 
RDI: 33b7606e
Sep 27 00:49:20 myserver kernel: RBP: 0001 R08: 7ffe0d2f2ae0 
R09: 558ffcfe7aa0
Sep 27 00:49:20 myserver kernel: R10: 7f6e2b967510 R11: 0011 
R12: 7f6d9f687fc8
Sep 27 00:49:20 myserver kernel: R13: 7f6d9dc6b888 R14: 0009 
R15: 558ffcfe7cb0
Sep 27 00:49:20 myserver kernel:  
Sep 27 00:49:20 myserver kernel: Modules linked in: tcp_bbr ipt_REJECT 
nf_reject_ipv4 xt_multiport xt_nat xt_tcpudp veth xt_conntrack nft_chain_nat 
xt_MASQUERADE nf_nat nf_conntrack_netlink nf_conntrack nf_defrag_ipv6 
nf_defrag_ipv4 xfrm_user xfrm_algo xt_addrtype nft_compat nf_tables nfnetlink 
br_netfilter bridge stp llc overlay binfmt_misc intel_rapl_msr 
intel_rapl_common ghash_clmulni_intel sha512_ssse3 sha512_generic aesni_intel 
virtio_gpu crypto_simd cryptd virtio_dma_buf pcspkr iTCO_wdt intel_pmc_bxt 
virtio_console drm_shmem_helper iTCO_vendor_support watchdog virtio_rng 
virtio_balloon rng_core drm_kms_helper button joydev evdev sg serio_raw drm 
loop fuse dm_mod efi_pstore configfs qemu_fw_cfg ip_tables x_tables autofs4 xfs 
libcrc32c crc32c_generic hid_generic usbhid hid sr_mod cdrom sd_mod t10_pi 
crc64_rocksoft crc64 crc_t10dif crct10dif_generic ahci libahci virtio_net 
net_failover virtio_scsi xhci_pci failover 

Bug#1051816: breaks Chromium under bookworm

[ucf8o921vn6]

This update breaks Chromium under bookworm.

# apt policy libfreetype6
libfreetype6:
  Installed: 2.12.1+dfsg-5+deb12u1
  Candidate: 2.12.1+dfsg-5+deb12u1
  Version table:
 *** 2.12.1+dfsg-5+deb12u1 500
500 https://deb.debian.org/debian 
bookworm-proposed-updates/main amd64 Packages

100 /var/lib/dpkg/status
 2.12.1+dfsg-5 500
500 https://deb.debian.org/debian bookworm/main amd64 Packages

$ chromium
[77253:77253:0927/195753.48:ERROR:policy_logger.cc(154)] 
:components/enterprise/browser/controller/chrome_browser_cloud_management_controller.cc(163) 
Cloud management controller initialization aborted as CBCM is not enabled.

[0927/195753.629107:ERROR:elf_dynamic_array_reader.h(64)] tag not found
Segmentation fault

Bug#1053119: orca fails to read file names when navigating some folders in caja+mate menu issues

[jordan]

Package: orca
Version: 45.0-1~bpo12+1
Severity: important
X-Debbugs-Cc: jordanlives...@gmail.com

Dear Maintainer, I've noticed a bug in this version of orca, for some reason in 
the mate desktop, you could be navigating files with the file manager and orca 
sometimes fails to read file names even if the orca curser is on it, there is 
also a bug in the mate menu where orca will just keep reading, preferences menu 
when navigating the submenus of that menu

*** Reporter, please consider answering these questions, where appropriate ***

   * What led up to the situation?
   * What exactly did you do (or not do) that was effective (or
 ineffective)?
   * What was the outcome of this action?
   * What outcome did you expect instead?I expected orca to behave normally as 
it usually does when navigating files or the mate menu

*** End of the template - remove these template lines ***


-- System Information:
Debian Release: 12.1
  APT prefers stable-updates
  APT policy: (500, 'stable-updates'), (500, 'stable-security'), (500, 'stable')
Architecture: amd64 (x86_64)
Foreign Architectures: i386

Kernel: Linux 6.1.0-12-amd64 (SMP w/6 CPU threads; PREEMPT)
Locale: LANG=en_GB.UTF-8, LC_CTYPE=en_GB.UTF-8 (charmap=UTF-8), LANGUAGE not set
Shell: /bin/sh linked to /usr/bin/dash
Init: systemd (via /run/systemd/system)
LSM: AppArmor: enabled

Versions of packages orca depends on:
ii  gir1.2-glib-2.01.74.0-3
ii  gir1.2-gstreamer-1.0   1.22.0-2
ii  gir1.2-gtk-3.0 3.24.37-2
ii  gir1.2-pango-1.0   1.50.12+ds-1
ii  gir1.2-wnck-3.043.0-3
ii  gsettings-desktop-schemas  43.0-1
ii  gstreamer1.0-plugins-good  1.22.0-5+deb12u1
ii  python33.11.2-1+b1
ii  python3-brlapi 6.5-7
ii  python3-cairo  1.20.1-5+b1
ii  python3-gi 3.42.2-3+b1
ii  python3-louis  3.24.0-1
ii  python3-pyatspi2.46.0-2
ii  python3-speechd0.11.5-1~bpo12+1
ii  speech-dispatcher  0.11.5-1~bpo12+1
ii  xkbset 0.6-3

Versions of packages orca recommends:
ii  xbrlapi  6.5-7

Versions of packages orca suggests:
pn  brltty  

-- no debconf information

Bug#1053118: connman: BNEP broken since 1.37

[программист некто]

Package: connman
Version: 1.41-3
Severity: important

Hello. I can't connect phone to PC. Phone connects, but no Internet available.
In syslog I found two errors:
profiles/network/bnep.c:bnep_add_to_bridge() bnep: Can't add bnep0 to the 
bridge tether: No such device(19)
profiles/network/server.c:bnep_setup() BNEP server cannot be added

Setting net.ifnames=0 to kernel has no effect.
I try to install old version connman and found that with 1.36 worked without 
those two erorrs.

syslog fragment, connman 1.41-3, when I try to connect from phone (MAC address 
removed):

Sep 27 20:18:25 debian-gateway connmand[1434]: bnep0 {create} index 19 type 1 

Sep 27 20:18:25 debian-gateway connmand[1434]: bnep0 {update} flags 4098 
Sep 27 20:18:25 debian-gateway connmand[1434]: bnep0 {newlink} index 19 address 
AA:... mtu 1500
Sep 27 20:18:25 debian-gateway connmand[1434]: bnep0 {newlink} index 19 
operstate 2 
Sep 27 20:18:25 debian-gateway connmand[1434]: Adding interface bnep0 [ 
bluetooth ]
Sep 27 20:18:25 debian-gateway connman-vpnd[514]: bnep0 {create} index 19 type 
1 
Sep 27 20:18:25 debian-gateway connman-vpnd[514]: bnep0 {update} flags 4098 

Sep 27 20:18:25 debian-gateway connman-vpnd[514]: bnep0 {newlink} index 19 
address AA:... mtu 1500
Sep 27 20:18:25 debian-gateway connman-vpnd[514]: bnep0 {newlink} index 19 
operstate 2 
Sep 27 20:18:25 debian-gateway (udev-worker)[3730]: Network interface 
NamePolicy= disabled on kernel command line.
Sep 27 20:18:25 debian-gateway bluetoothd[580]: 
profiles/network/bnep.c:bnep_add_to_bridge() bnep: Can't add bnep0 to the 
bridge tether: No such device(19)
Sep 27 20:18:25 debian-gateway bluetoothd[580]: 
profiles/network/server.c:bnep_setup() BNEP server cannot be added
Sep 27 20:18:25 debian-gateway connmand[1434]: bnep0 {dellink} index 19 
operstate 2 
Sep 27 20:18:25 debian-gateway connmand[1434]: (null) {remove} index 19
Sep 27 20:18:25 debian-gateway connmand[1434]: Remove interface (null) [ 
bluetooth ]
Sep 27 20:18:25 debian-gateway connman-vpnd[514]: bnep0 {dellink} index 19 
operstate 2 
Sep 27 20:18:25 debian-gateway connman-vpnd[514]: bnep0 {remove} index 19

Bug#1053117: r8152 driver unable to bring up RTL8156BG

[Jamie Bliss]

Package: linux-image-6.5.0-1-amd64
Version: 6.5.3-1

The r8152 driver is unable to bring up a RTL8156BG device. It's able to 
enumerate and present some info, but actually passing packets fails.

I will note that the RTL8156BG firmware is not in the the firmware-realtek 
package, unlike its sister chips.

The RTL8156BG can be found in the Framework Ethernet Module.

Bug#1052304: kafs failure testing

[Bill MacAllister]

I spent a couple days bisecting kernels attempting to isolate this bug
to a specific kernel.  What I found was that the simple test that I
included in the initial bug report, i.e. ls /afs/ca-zephyr.org, is not
sufficient to test for failure.  This test can succeed multiple times
and then sometime later fail.  Which meant that my bisection attempts
where pretty much useless.  I will work on a better test for this issue.

Bill

--

"Can't sing louder than the guns when I'm gone,
so I guess I'll have to do it while I'm here."
   Phil Ochs

Bug#1053116: cdc_ncm driver fails to bring up RTL8156BG

[Jamie Bliss]

Package: linux-image-6.1.0-11-amd64-unsigned
Version: 6.1.38-4

The cdc_ncm driver is able to enumerate an RTL8156BG device, and glean some 
capabilities, but it is unable to fully bring up and utilize it, for unknown 
errors. (The systemd log doesn't contain any details, just a generic failed 
message.)

This chipset can be found in the Framework Ethernet Module.

Note that Ubuntu and Fedora are able to use cdc_ncm with the RTL8156BG, with 
some quirks. (Namely, it comes up in half-duplex mode.) So I'm pretty sure this 
is a Debian-specific bug.

Bug#1053007: transition: suitesparse-7.2

[Sebastian Ramacher]

Control: tags -1 confirmed

On 2023-09-26 22:59:30 +0200, Sébastien Villemot wrote:
> Package: release.debian.org
> Severity: normal
> User: release.debian@packages.debian.org
> Usertags: transition
> X-Debbugs-Cc: suitespa...@packages.debian.org
> Control: affects -1 + src:suitesparse
> Control: forwarded -1 
> https://release.debian.org/transitions/html/auto-suitesparse.html
> 
> Dear Release Team,
> 
> Please schedule a transition for suitesparse 7.2. The new version is already 
> in
> experimental.

Please go ahead.

Cheers
-- 
Sebastian Ramacher

Bug#1053115: foot: code execution via malformed XTGETTCAP

[Birger Schacht]

Package: foot
Version: 1.13.1-2
Severity: important
Tags: security upstream
X-Debbugs-Cc: bir...@debian.org, Debian Security Team 


If an XTGETTCAP escape sequence printed to the terminal contains newline
characters, foot will echo the newline characters back into the PTY as
part of the "invalid capability" response. (XTGETTCAP strings are
supposed to be hex-encoded, so it's not valid for them to contain
newline characters.) In a cat/curl scenario, the user's shell will
receive those newline characters and execute any commands embedded in
the XTGETTCAP sequence as though they were typed in by the user.

Bug#1053110: exim4 FTBFS when dh_installsystemd installs units to /usr

[Andreas Metzler]

On 2023-09-27 Helmut Grohne  wrote:
> Source: exim4
> Version: 4.97~RC0-3
> Tags: ftbfs patch
> User: helm...@debian.org
> Usertags: dep17m2

> We want to change dh_installsystemd to install units to /usr. The exim4
> packaging also wants this and performs the change that we want in
> debhelper. Unfortunately, when debhelper changes, this makes exim4
> FTBFS. I propose changing the condition such that it becomes a noop once
> we change dh_installsystemd. I've attached a patch implementing it. Once
> applied, exim4 will build in the same way as before with current and
> future debhelper.
[...]

Hello,

Thanks. Feel free to NMU if this urgent, otherwise I will include it in
the next upload which should happen this weekend (4.97~RC1).

cu Andreas
-- 
`What a good friend you are to him, Dr. Maturin. His other friends are
so grateful to you.'
`I sew his ears on from time to time, sure'

Bug#1052455: freetype 2.12.1+dfsg-5+deb12u1 makes chromium segfault at startup

[SuperCat]

Hi,

In chromium source code, function SkScalerContext::GlyphMetrics
SkScalerContext_FreeType::generateMetrics() will call
FT_Get_Color_Glyph_Paint() if macro TT_SUPPORT_COLRV1 exists. Somehow
FT_Get_Color_Glyph_Paint will be a NULL pointer if this patch applied, and
chromium will not be able to run.

Bug#1053101: qemu-user-static: segfault when running ldd/arm64 on certain arm64 binaries

[Michael Tokarev]

27.09.2023 16:29, Andreas Beckmann wrote:

On 27/09/2023 15.23, Michael Tokarev wrote:

Hmm wait. Are you trying to say this happens on deb12u2
but does NOT happen on deb12u1?


No. It happens on both. I observed it on u1 then upgraded to u2 in case it 
could be fixed there, but nothing changed.


Ok.  I was nervous thinking it's a regression in 7.2.x stable series.


(I haven't tried 8.x, yet, since last time I tried 8.x didn't work at all in my 
setup and I didn't have time to debug that yet.)


8.1 had quite some changes in linux-user areas, it should address all
issue known to date.  Some of that changes went to 8.0.x stable too,
but most important didn't.  Debian testing now - finally - has 8.1.
So it is definitely worth to try this one.

I'd love to have a (simple) reproducer for this one..

/mjt

Bug#1052693: live-manual-pdf: PDF manual is unreadable

[Ralph Amissah]

(i hope this is how to reply to the right place in the bugtracker, it
has been a while and recall using reportbugs? in the past).

I see the live-manual lack of pdfs bug and am jumping in somewhat
prematurely as I am making assumptions as to the likely cause without
having done any tests on Debian, and without knowing anything really
about the setup or infrastructure in place for generating live-manual
apart from the fact that sisu has been responsible for the output in
question in the bug report. The issue: "no pdfs" is somewhat familiar,
it reminds me of a previous issue on Debian that affected the ability
of sisu to produce pdfs.

The good news, since this bug report (using NixOS) I have:

- checked sisu with ruby-3.2 (and ruby-3.1) and it works

- (more specifically) checked sisu latex pdf output (against an old
reference copy of debian-live-manual sisu source markup) with ruby 3.2
and it works

The less good news:

- the tests were not on Debian but on NixOS though the program code is
the same for both distributions and has worked unchanged. (I switched
from Debian to using NixOS as my primary distribution around 2020 and
am not sure I even have a functional Debian box to log into or test
on).

- I have not programmed in ruby since 2015 (when I started my rewrite
of sisu in the programming language D)

- Since 2019 or so I use a D version of sisu that I have not shared or
decided how or whether to share.

 Back again to better news:

- The stoping of sisu genrating pdfs on Debian has happened a couple
of times before with new debian releases containing texlive packages
that rearrange the locations of latex .sty files within them. It has
(in the past) been relatively easy to fix.

./lib/sisu/texpdf_format.rb (towards the end of the file) contains
notes on steps that were taken last time to locate the .sty files
relevant to sisu and where they were to be found within Debian. Once
the relavant texlive packages are identified what needed to be done
was to make sure their dependencies were in place within ./debian for
sisu-pdf . It appears that this last needed to be done in 2019 and
2017 before that.

https://sisudoc.org/projects/sisu/log/?qt=grep=.sty
https://sisudoc.org/projects/sisu/commit/?id=55df651b572c5737ba01ac68f90d8475331a208b
https://sisudoc.org/projects/sisu/log/?h=debian=grep=tex
https://sisudoc.org/projects/sisu/commit/?h=debian=2a3350c959d83c88e498b87345b06b1f42f96df3
https://sisudoc.org/projects/sisu/commit/?h=debian=86f1de612b231a929e2d815097cdd3c4766809b9

I have no idea what texlive packaging in Debian looks like now, nor
indeed can I be certain that this (or indeed anything to do with sisu)
is the cause of the problem, (though it does seem likely to me). The
notes in the file ./lib/sisu/texpdf_format.rb should give an idea of
how to find out which texlive packages are needed as dependencies for
sisu to produce pdfs. Sisu is a ruby program that is largely
distribution agnostic, that there have been no hiccups in the
behaviour of sisu in producing pdfs on NixOS suggests, hopefully that
this is nothing major.

 If this is the cause a bug should be filed somewhere against sisu
packaging (texlive dependencies).

Given my current situation, willing to help but (for the time being at
least) using another distro, there should perhaps be another uploader
in debian, and sisu upstream should relinquish having a ./debian
(packaging) directory, which can be handled by the Debian project?

(i hope this is how to reply to the right place in the bugtracker, it
has been a while and recall using reportbug? in the past).

Greetings,
Ralph

Bug#1052455: freetype 2.12.1+dfsg-5+deb12u1 makes chromium segfault at startup

[SuperCat]

Hi,

After apply this upgrade (2.12.1+dfsg-5+deb12u1), I cannot run chromium
(from 114 to 117) any more with segfault error. I can run chromium again if
I downgrade this package to previous version (2.12.1+dfsg-5). Maybe
chromium use this macro somewhere.

Bug#1053114: gnome-shell: Settings > Region & Language won't actually change UI language

[Melissa Ferreira da Silva Boiko]

Package: gnome-shell
Version: 43.6-1~deb12u2
Severity: normal
Tags: l10n
X-Debbugs-Cc: melissa.bo...@viaboxx.de

Clean bookworm, freshly installed today.

The locales generated via locale-gen show up in Gnome Settings > Region
& Language.  However, selecting them does nothing; the Gnome UI remains
stuck in English.

The locales were generated post-install via /etc/locale.gen /
dpkg-reconfigure locales, and work fine for other applications via
setting LANG/LC_ALL.

The problem may be related to a LANGUAGE=en_US:en variable that appears
when I log in via GDM.  It does not appear if I log in via console.

Some things I tried which didn't help:
 - gsettings set org.gnome.system.locale region (it was empty)
 - editing /var/lib/AccountsService/user/myuser (it was correct)
 - creating a ~/.config/locale.conf
 - regenerating locales via locale-gen
 - regenerating locales via dpkg-reconfigure locales
 - removing English locales from the system, and regenerating them
 - setting the default system language to something other than English
 - setting the "Region & Language" option to English then back to
   another language

No matter what I do, Gnome remains in English.

(I'm sorry if this isn't the right package to report, I couldn't find
previous reports from web searches.)

--
Melissa

-- System Information:
Debian Release: 12.1
  APT prefers stable-updates
  APT policy: (500, 'stable-updates'), (500, 'stable-security'), (500, 'stable')
Architecture: amd64 (x86_64)

Kernel: Linux 6.4.0-0.deb12.2-amd64 (SMP w/12 CPU threads; PREEMPT)
Locale: LANG=pt_BR.UTF-8, LC_CTYPE=pt_BR.UTF-8 (charmap=UTF-8) (ignored: LC_ALL 
set to de_DE.UTF-8), LANGUAGE=en_GB:en
Shell: /bin/sh linked to /usr/bin/dash
Init: systemd (via /run/systemd/system)
LSM: AppArmor: enabled

Versions of packages gnome-shell depends on:
ii  dconf-gsettings-backend [gsettings-backend]  0.40.0-4
ii  gir1.2-accountsservice-1.0   22.08.8-6
ii  gir1.2-adw-1 1.2.2-1
ii  gir1.2-atk-1.0   2.46.0-5
ii  gir1.2-atspi-2.0 2.46.0-5
ii  gir1.2-freedesktop   1.74.0-3
ii  gir1.2-gcr-3 3.41.1-1+b1
ii  gir1.2-gdesktopenums-3.0 43.0-1
ii  gir1.2-gdkpixbuf-2.0 2.42.10+dfsg-1+b1
ii  gir1.2-gdm-1.0   43.0-3
ii  gir1.2-geoclue-2.0   2.6.0-2
ii  gir1.2-glib-2.0  1.74.0-3
ii  gir1.2-gnomebluetooth-3.042.5-3
ii  gir1.2-gnomedesktop-3.0  43.2-2
ii  gir1.2-graphene-1.0  1.10.8-1
ii  gir1.2-gstreamer-1.0 1.22.0-2
ii  gir1.2-gtk-3.0   3.24.37-2
ii  gir1.2-gtk-4.0   4.8.3+ds-2
ii  gir1.2-gweather-4.0  4.2.0-2
ii  gir1.2-ibus-1.0  1.5.27-5
ii  gir1.2-mutter-11 43.6-1~deb12u1
ii  gir1.2-nm-1.01.42.4-1
ii  gir1.2-nma-1.0   1.10.6-1
ii  gir1.2-pango-1.0 1.50.12+ds-1
ii  gir1.2-polkit-1.0122-3
ii  gir1.2-rsvg-2.0  2.54.7+dfsg-1~deb12u1
ii  gir1.2-soup-3.0  3.2.2-2
ii  gir1.2-upowerglib-1.00.99.20-2
ii  gir1.2-webkit2-4.1   2.40.5-1~deb12u1
ii  gnome-backgrounds43.1-1
ii  gnome-settings-daemon43.0-4
ii  gnome-shell-common   43.6-1~deb12u2
ii  gsettings-desktop-schemas43.0-1
ii  gstreamer1.0-pipewire0.3.65-3
ii  libatk-bridge2.0-0   2.46.0-5
ii  libatk1.0-0  2.46.0-5
ii  libc62.36-9+deb12u1
ii  libcairo21.16.0-7
ii  libecal-2.0-23.46.4-2
ii  libedataserver-1.2-273.46.4-2
ii  libgcr-base-3-1  3.41.1-1+b1
ii  libgdk-pixbuf-2.0-0  2.42.10+dfsg-1+b1
ii  libgirepository-1.0-11.74.0-3
ii  libgjs0g 1.74.2-1
ii  libgles2 1.6.0-1
ii  libglib2.0-0 2.74.6-2
ii  libglib2.0-bin   2.74.6-2
ii  libgnome-autoar-0-0  0.4.3-1
ii  libgnome-desktop-3-2043.2-2
ii  libgraphene-1.0-01.10.8-1
ii  libgtk-3-0   3.24.37-2
ii  libgtk-4-1   4.8.3+ds-2
ii  libical3 3.0.16-1+b1
ii  libjson-glib-1.0-0   

Bug#1052257: diffoscope crashes(?) comparing some i386 debs (and others)

[Vagrant Cascadian]

On 2023-09-27, Holger Levsen wrote:
> On Wed, Sep 20, 2023 at 12:25:36PM +, Holger Levsen wrote:
>> so I've powercycled the machine and also disabled the armhf workers now.
>> (under the (weak) assumption that this bug is mostly trigged when running
>> diffoscope on 32bit .debs...)

Most frustrating!


> so on Sep 23rd I made diffoscope run under ionice -n6, and so far the machine
> has gone down on its knees yet. 
>
> and on Sep 25th I said this on #debian-reproducible:
>
> when i made diffoscope run under ionice i was wondering if there were changes 
> in the linux 
> scheduler causing the probs we saw... now not seeing the machine go down to 
> its knees 
> within 60h uptime i'm saying this to "provoke" the problem coming back
> however, looking at 
> jenkins.debian.net/munin/static/dynazoom.html?cgiurl_graph=/munin-cgi/munin-cgi-graph_name=debian.net/jenkins.debian.net/uptime_x=800_y=400_epoch=1661108749_epoch=1695668749
> I can that the highest uptime was 15 days..
> (since upgrading to bookworm which is when the probs started)
> it could also be kernel related, with switching to bookworm
> we switched from 5.10.0 to 6.1.0...
> so my next stabs c/would be: 
> a.) increase swap 
> b.) upgrade to kernel 6.4.0 from bpo
> c.) something else

Maybe try using a bullseye 5.10.x kernel for a while? Obviously better
if the issue is fixed in a newer kernel version ... but if 5.10.x
consistently works with bookworm userspace that ever so slightly narrows
down the issue?


live well,
  vagrant


signature.asc
Description: PGP signature

Bug#1052529: proftpd: provide debug symbols for amd64 platform in sid

[Dmitry Katsubo]

On 2023-09-26 10:42, Preuße, Hilmar wrote:
> On 24.09.2023 00:38, Dmitry Katsubo wrote:
> 
> Hello Dmitry,
> 
>> Would be great to provide proftpd-*-dbgsym packages for amd64 platform. 
>> Current [1] platforms are:
>>
>> alpha hppa ia64 m68k ppc64 riscv64 sh4 sparc64 x32
>>
>> [1] https://packages.debian.org/search?keywords=proftpd
>>
> 
> I just rebuilt the proftpd packages and the debug packages were generated. 
> Further I see them on [2]. Maybe refer to [3] to learn how to get these 
> symbols.
> 
> Hilmar
> 
> [2] https://deb.debian.org/debian-debug/pool/main/p/proftpd-dfsg/
> [3] https://wiki.debian.org/HowToGetABacktrace

Thanks, I was able to install the packages. However I am stuck with how to make 
advantage of that. I would expect that the symbols are resolved directly in 
ProFTPD log:

ProFTPD killed (signal 15)
ProFTPD 1.3.8 standalone mode SHUTDOWN
ProFTPD 1.3.8 (stable) (built Sun Jul 2 2023 10:56:40 UTC) standalone mode 
STARTUP
(localhost[127.0.0.1]): -BEGIN STACK TRACE-
(localhost[127.0.0.1]): [0] /usr/lib/proftpd/mod_tls.so(+0x19ef5) 
[0x7f3b60371ef5]
(localhost[127.0.0.1]): [1] /usr/lib/proftpd/mod_tls.so(+0x19ef5) 
[0x7f3b60371ef5]
(localhost[127.0.0.1]): [2] /usr/lib/proftpd/mod_tls.so(+0x26a7e) 
[0x7f3b6037ea7e]
(localhost[127.0.0.1]): [3] proftpd: (accepting 
connections)(modules_session_init+0x57) [0x55950185bbc7]
(localhost[127.0.0.1]): [4] proftpd: (accepting connections)(+0x204ad) 
[0x55950182e4ad] <-- trying to resolve this address
(localhost[127.0.0.1]): [5] proftpd: (accepting connections)(+0x20ea1) 
[0x55950182eea1]
(localhost[127.0.0.1]): [6] proftpd: (accepting connections)(main+0x5f8) 
[0x55950182cb98]
(localhost[127.0.0.1]): [7] /lib/x86_64-linux-gnu/libc.so.6(+0x271ca) 
[0x7f3b606461ca]
(localhost[127.0.0.1]): [8] 
/lib/x86_64-linux-gnu/libc.so.6(__libc_start_main+0x85) [0x7f3b60646285]
(localhost[127.0.0.1]): [9] proftpd: (accepting connections)(_start+0x21) 
[0x55950182d1c1]
(localhost[127.0.0.1]): -END STACK TRACE-

Then I tried the advise from [4]:

# addr2line -e /usr/sbin/proftpd 0x55950182e4ad
??:0

and with gdb:

# gdb /usr/sbin/proftpd
Reading symbols from /usr/sbin/proftpd...
Reading symbols from 
/usr/lib/debug/.build-id/f2/6641fdbd8d794169752f091b130234807cdcfb.debug...
(gdb) info symbol 0x55950182e4ad
No symbol matches 0x55950182e4ad.

Any ideas? Thanks in advance!

[4] http://www.proftpd.org/docs/howto/Compiling.html#DeveloperOptions

-- 
With best regards,
Dmitry

Bug#1053113: colord FTBFS when systemd.pc changes systemdsystemunitdir

[Helmut Grohne]

Source: colord
Version: 1.4.6-3
Tags: ftbfs patch
User: helm...@debian.org
Usertags: dep17m2

We want to change the value of systemdsystemunitdir in systemd.pc to
point below /usr. colord's upstream build system consumes this variable
while the packaging hard codes its current value. As we change it,
colord will FTBFS. Consider applying the attached patch to avoid this
failure.

Helmut
diff -Nru colord-1.4.6/debian/changelog colord-1.4.6/debian/changelog
--- colord-1.4.6/debian/changelog   2023-09-13 17:07:00.0 +0200
+++ colord-1.4.6/debian/changelog   2023-09-27 10:01:53.0 +0200
@@ -1,3 +1,10 @@
+colord (1.4.6-3.1) UNRELEASED; urgency=medium
+
+  * Non-maintainer upload.
+  * Fix FTBFS when systemd.pc changes systemdsystemunitdir. (Closes: #-1)
+
+ -- Helmut Grohne   Wed, 27 Sep 2023 10:01:53 +0200
+
 colord (1.4.6-3) unstable; urgency=medium
 
   * Team upload (Closes: #1032263)
diff -Nru colord-1.4.6/debian/colord.install colord-1.4.6/debian/colord.install
--- colord-1.4.6/debian/colord.install  2023-09-13 17:07:00.0 +0200
+++ colord-1.4.6/debian/colord.install  2023-09-27 10:00:37.0 +0200
@@ -1,5 +1,5 @@
-lib/systemd/system/*.service
-lib/udev/rules.d/
+${env:deb_systemdsystemunitdir}/*.service
+${env:deb_udevdir}/rules.d/
 usr/bin/
 usr/lib/*/colord-plugins
 usr/lib/*/colord-sensors/libcolord_sensor_colorhug.so
diff -Nru colord-1.4.6/debian/control colord-1.4.6/debian/control
--- colord-1.4.6/debian/control 2023-09-13 17:07:00.0 +0200
+++ colord-1.4.6/debian/control 2023-09-27 09:57:32.0 +0200
@@ -20,9 +20,11 @@
  libsystemd-dev [linux-any],
  libudev-dev,
  meson (>= 0.52.0),
+ pkgconf,
  polkitd,
  shared-mime-info ,
  systemd [linux-any],
+ systemd-dev [linux-any],
  valac (>= 0.20),
  xsltproc,
 Build-Depends-Indep:
diff -Nru colord-1.4.6/debian/rules colord-1.4.6/debian/rules
--- colord-1.4.6/debian/rules   2023-09-13 17:07:00.0 +0200
+++ colord-1.4.6/debian/rules   2023-09-27 10:01:46.0 +0200
@@ -22,6 +22,8 @@
 ifeq ($(DEB_HOST_ARCH_OS),linux)
confflags += -Dsane=true
indep_flags = -Dprint_profiles=true
+   export deb_systemdsystemunitdir = $(shell pkgconf 
--variable=systemdsystemunitdir systemd | sed s,^/,,)
+   export deb_udevdir = $(shell pkgconf --variable=udevdir udev | sed 
s,^/,,)
 else
confflags += -Dsane=false -Dsystemd=false -Dudev_rules=false
indep_flags = -Dprint_profiles=false
@@ -38,8 +40,8 @@
 
 execute_before_dh_install:
# Exclude systemd and udev related files
-   grep -E -v 'lib/systemd|lib/udev|lib/tmpfiles\.d' debian/colord.install 
> debian/colord.install.kfreebsd
-   grep -E -v 'lib/systemd|lib/udev|lib/tmpfiles\.d' debian/colord.install 
> debian/colord.install.hurd
+   grep -E -v 
'lib/systemd|deb_systemdsystemunitdir|deb_udevdir|lib/tmpfiles\.d' 
debian/colord.install > debian/colord.install.kfreebsd
+   grep -E -v 
'lib/systemd|deb_systemdsystemunitdir|deb_udevdir|lib/tmpfiles\.d' 
debian/colord.install > debian/colord.install.hurd
 
 execute_before_dh_clean:
rm -f debian/colord.install.kfreebsd

Bug#1053112: cockpit FTBFS when systemd.pc changes systemdsystemunitdir

[Helmut Grohne]

Source: cockpit
Version: 301-1
Tags: ftbfs patch
User: helm...@debian.org
Usertags: dep17m2

We want to change the value of systemdsystemunitdir in systemd.pc to
point below /usr. cockpit's upstream build system consumes this variable
while the packaging hard codes its current value. When we change it,
cockpit will FTBFS. Consider applying the attached patch to avoid the
failure.

Helmut
diff -Nru cockpit-301/debian/changelog cockpit-301/debian/changelog
--- cockpit-301/debian/changelog2023-09-21 07:20:37.0 +0200
+++ cockpit-301/debian/changelog2023-09-27 12:16:09.0 +0200
@@ -1,3 +1,10 @@
+cockpit (301-1.1) UNRELEASED; urgency=medium
+
+  * Non-maintainer upload.
+  * Fix FTBFS when systemd.pc changes systemdsystemunitdir. (Closes: #-1)
+
+ -- Helmut Grohne   Wed, 27 Sep 2023 12:16:09 +0200
+
 cockpit (301-1) unstable; urgency=medium
 
   * New upstream release:
diff -Nru cockpit-301/debian/cockpit-tests.install 
cockpit-301/debian/cockpit-tests.install
--- cockpit-301/debian/cockpit-tests.install2023-06-14 13:51:32.0 
+0200
+++ cockpit-301/debian/cockpit-tests.install2023-09-27 12:15:41.0 
+0200
@@ -1,3 +1,3 @@
 usr/share/cockpit/playground
-lib/systemd/system/cockpit-session.socket
-lib/systemd/system/cockpit-session@.service
+${env:deb_systemdsystemunitdir}/cockpit-session.socket
+${env:deb_systemdsystemunitdir}/cockpit-session@.service
diff -Nru cockpit-301/debian/cockpit-ws.install 
cockpit-301/debian/cockpit-ws.install
--- cockpit-301/debian/cockpit-ws.install   2023-06-14 13:51:32.0 
+0200
+++ cockpit-301/debian/cockpit-ws.install   2023-09-27 12:15:58.0 
+0200
@@ -1,15 +1,15 @@
 etc/cockpit/ws-certs.d
 etc/pam.d/cockpit
-lib/systemd/system/cockpit.service
-lib/systemd/system/cockpit-motd.service
-lib/systemd/system/cockpit.socket
-lib/systemd/system/cockpit-wsinstance-http.service
-lib/systemd/system/cockpit-wsinstance-http.socket
-lib/systemd/system/cockpit-wsinstance-https-factory@.service
-lib/systemd/system/cockpit-wsinstance-https-factory.socket
-lib/systemd/system/cockpit-wsinstance-https@.service
-lib/systemd/system/cockpit-wsinstance-https@.socket
-lib/systemd/system/system-cockpithttps.slice
+${env:deb_systemdsystemunitdir}/cockpit.service
+${env:deb_systemdsystemunitdir}/cockpit-motd.service
+${env:deb_systemdsystemunitdir}/cockpit.socket
+${env:deb_systemdsystemunitdir}/cockpit-wsinstance-http.service
+${env:deb_systemdsystemunitdir}/cockpit-wsinstance-http.socket
+${env:deb_systemdsystemunitdir}/cockpit-wsinstance-https-factory@.service
+${env:deb_systemdsystemunitdir}/cockpit-wsinstance-https-factory.socket
+${env:deb_systemdsystemunitdir}/cockpit-wsinstance-https@.service
+${env:deb_systemdsystemunitdir}/cockpit-wsinstance-https@.socket
+${env:deb_systemdsystemunitdir}/system-cockpithttps.slice
 lib/*/security/pam_ssh_add.so
 lib/*/security/pam_cockpit_cert.so
 usr/lib/tmpfiles.d/cockpit-tempfiles.conf
diff -Nru cockpit-301/debian/control cockpit-301/debian/control
--- cockpit-301/debian/control  2023-07-26 12:21:11.0 +0200
+++ cockpit-301/debian/control  2023-09-27 12:14:32.0 +0200
@@ -21,7 +21,9 @@
libpam0g-dev,
libpcp-import1-dev,
libpcp-pmda3-dev,
+   pkgconf,
systemd,
+   systemd-dev,
xsltproc,
xmlto,
docbook-xsl,
diff -Nru cockpit-301/debian/rules cockpit-301/debian/rules
--- cockpit-301/debian/rules2023-09-21 07:20:21.0 +0200
+++ cockpit-301/debian/rules2023-09-27 12:15:06.0 +0200
@@ -9,6 +9,8 @@
export COCKPIT_SKIP_SLOW_TESTS=1
 endif
 
+export deb_systemdsystemunitdir = $(shell pkgconf 
--variable=systemdsystemunitdir systemd | sed s,^/,,)
+
 %:
dh $@ --buildsystem=autoconf --with=python3
 

Bug#1053110: exim4 FTBFS when dh_installsystemd installs units to /usr

[Helmut Grohne]

Source: exim4
Version: 4.97~RC0-3
Tags: ftbfs patch
User: helm...@debian.org
Usertags: dep17m2

We want to change dh_installsystemd to install units to /usr. The exim4
packaging also wants this and performs the change that we want in
debhelper. Unfortunately, when debhelper changes, this makes exim4
FTBFS. I propose changing the condition such that it becomes a noop once
we change dh_installsystemd. I've attached a patch implementing it. Once
applied, exim4 will build in the same way as before with current and
future debhelper.

Helmut
diff -Nru exim4-4.97~RC0/debian/changelog exim4-4.97~RC0/debian/changelog
--- exim4-4.97~RC0/debian/changelog 2023-09-19 18:04:22.0 +0200
+++ exim4-4.97~RC0/debian/changelog 2023-09-27 12:16:34.0 +0200
@@ -1,3 +1,10 @@
+exim4 (4.97~RC0-3.1) UNRELEASED; urgency=medium
+
+  * Non-maintainer upload.
+  * Fix FTBFS when dh_installsystemd installs units to /usr. (Closes: #-1)
+
+ -- Helmut Grohne   Wed, 27 Sep 2023 12:16:34 +0200
+
 exim4 (4.97~RC0-3) unstable; urgency=medium
 
   * Drop misleading phrase regarding incoming TLS support in README.Debian.
diff -Nru exim4-4.97~RC0/debian/rules exim4-4.97~RC0/debian/rules
--- exim4-4.97~RC0/debian/rules 2023-09-10 13:28:23.0 +0200
+++ exim4-4.97~RC0/debian/rules 2023-09-27 12:16:34.0 +0200
@@ -284,7 +284,7 @@
dh_installsystemd --remaining-packages
# move service file to real (post usrmerge) location,
for i in $(daemons) ; do \
-   if test -d debian/$${i} ; then \
+   if test -d debian/$${i}/lib/systemd ; then \
mv -v debian/$${i}/lib/systemd/ \
debian/$${i}/usr/lib/; \
rmdir debian/$${i}/lib ; \

Bug#1053111: e2fsprogs FTBFS when systemd.pc changes systemdsystemunitdir

[Helmut Grohne]

Source: e2fsprogs
Version: 1.47.0-2
Tags: ftbfs patch
User: helm...@debian.org
Usertags: dep17m2

We want to change the value of systemdsystemunitdir in systemd.pc to
point below /usr. e2fsprogs' upstream build system consumes this
variable while the packaging hard codes its current value. When we
change it, e2fsprogs will FTBFS. Consider applying the attached patch to
avoid this failure.

Helmut
diff -Nru e2fsprogs-1.47.0/debian/changelog e2fsprogs-1.47.0/debian/changelog
--- e2fsprogs-1.47.0/debian/changelog   2023-03-05 04:16:08.0 +0100
+++ e2fsprogs-1.47.0/debian/changelog   2023-09-26 20:57:57.0 +0200
@@ -1,3 +1,10 @@
+e2fsprogs (1.47.0-2.1) UNRELEASED; urgency=medium
+
+  * Non-maintainer upload.
+  * Fix FTBFS when systemd.pc changes systemdsystemunitdir. (Closes: #-1)
+
+ -- Helmut Grohne   Tue, 26 Sep 2023 20:57:57 +0200
+
 e2fsprogs (1.47.0-2) unstable; urgency=medium
 
   * Don't enable metadata_csum_seed and orhpan_file by default (Closes:
diff -Nru e2fsprogs-1.47.0/debian/control e2fsprogs-1.47.0/debian/control
--- e2fsprogs-1.47.0/debian/control 2023-03-05 04:16:08.0 +0100
+++ e2fsprogs-1.47.0/debian/control 2023-09-26 20:57:54.0 +0200
@@ -2,7 +2,7 @@
 Section: admin
 Priority: required
 Maintainer: Theodore Y. Ts'o 
-Build-Depends: gettext, texinfo, pkg-config, libfuse-dev [linux-any 
kfreebsd-any] , debhelper-compat (= 12), dh-exec, 
libblkid-dev, uuid-dev, m4, udev [linux-any], systemd [linux-any], cron 
[linux-any]
+Build-Depends: gettext, texinfo, pkg-config, libfuse-dev [linux-any 
kfreebsd-any] , debhelper-compat (= 12), dh-exec, 
libblkid-dev, uuid-dev, m4, udev [linux-any], systemd [linux-any], systemd-dev 
[linux-any], cron [linux-any]
 Rules-Requires-Root: no
 Standards-Version: 4.6.2
 Homepage: http://e2fsprogs.sourceforge.net
diff -Nru e2fsprogs-1.47.0/debian/e2fsprogs.install 
e2fsprogs-1.47.0/debian/e2fsprogs.install
--- e2fsprogs-1.47.0/debian/e2fsprogs.install   2023-03-05 04:16:08.0 
+0100
+++ e2fsprogs-1.47.0/debian/e2fsprogs.install   2023-09-26 20:57:57.0 
+0200
@@ -50,4 +50,4 @@
 usr/share/man/man8/tune2fs.8
 etc
 [linux-any] lib/udev/rules.d
-[linux-any] lib/systemd/system
+[linux-any] ${deb_systemdsystemunitdir}
diff -Nru e2fsprogs-1.47.0/debian/rules e2fsprogs-1.47.0/debian/rules
--- e2fsprogs-1.47.0/debian/rules   2023-03-05 04:16:08.0 +0100
+++ e2fsprogs-1.47.0/debian/rules   2023-09-26 20:57:57.0 +0200
@@ -14,6 +14,10 @@
 SKIP_FUSE2FS=yes
 endif
 
+ifeq ($(DEB_HOST_ARCH_OS), linux)
+export deb_systemdsystemunitdir = $(shell pkg-config 
--variable=systemdsystemunitdir systemd | sed s,^/,,)
+endif
+
 ifneq ($(filter pkg.e2fsprogs.no-fuse2fs,$(DEB_BUILD_PROFILES)),)
 SKIP_FUSE2FS=yes
 endif

Bug#1053109: Mark limited support for Samba in buster and bullseye

[Santiago Ruano Rincón]

Package: debian-security-support
Version: 1:13+2023.09.27
Severity: normal
X-Debbugs-Cc: debian-...@lists.debian.org

Samba as AD Domain Controller is not supported in bullseye since [DSA 5477-1]
and in buster since [DSA 5015-1]. debian-security-support should include
this information in security-support-limited.{deb10,deb11}.

I will prepare a patch.

[DSA 5477-1] 
https://lists.debian.org/debian-security-announce/2023/msg00169.html
[DSA 5015-1] https://www.debian.org/security/2021/dsa-5015


-- System Information:
Debian Release: trixie/sid
  APT prefers stable-security
  APT policy: (500, 'stable-security'), (500, 'oldstable-security'), (500, 
'oldoldstable'), (500, 'unstable'), (500, 'stable'), (500, 'oldstable'), (1, 
'experimental')
Architecture: amd64 (x86_64)

Kernel: Linux 6.4.0-4-amd64 (SMP w/16 CPU threads; PREEMPT)
Locale: LANG=en_US.UTF-8, LC_CTYPE=en_US.UTF-8 (charmap=UTF-8), 
LANGUAGE=en_US:en
Shell: /bin/sh linked to /usr/bin/dash
Init: systemd (via /run/systemd/system)
LSM: AppArmor: enabled

Versions of packages debian-security-support depends on:
ii  adduser3.137
ii  debconf [debconf-2.0]  1.5.82
ii  gettext-base   0.21-13+b1

debian-security-support recommends no packages.

debian-security-support suggests no packages.

-- debconf information excluded


signature.asc
Description: PGP signature

Bug#1051752: [pkg-uWSGI-devel] Bug#1051752: uwsgi: remove uwsgi-plugin-glusterfs on 32 bit architectures)

[Jonas Smedegaard]

Hi Alex,

Quoting Alexandre Rossi (2023-09-27 15:18:14)
> Following attempted fixes of #1051752, please not that I seem to have fixed it
> (tested on i386) in 
> https://salsa.debian.org/uwsgi-team/uwsgi/-/commit/5cdb4e37be8dd93cefdcceeb199efe990b2eb918
>  .

Thanks a lot!


> If I get some advice on the best practrices for having d/control.in with
> template variables, I would be happy to work on this.

I assume you mean the debian/control file (as the uwsgi source package
currently contains no debian/control.in file).
That file gets mangled when the following command is executed:

  DEB_MAINTAINER_MODE=1 debian/control clean

I have finished the packaging now, and am now preparing a new release.

Thanks again,

 - Jonas

-- 
 * Jonas Smedegaard - idealist & Internet-arkitekt
 * Tlf.: +45 40843136  Website: http://dr.jones.dk/
 * Sponsorship: https://ko-fi.com/drjones

 [x] quote me freely  [ ] ask before reusing  [ ] keep private

signature.asc
Description: signature

Bug#1053108: Please move NM hook scripts to /usr/lib/NetworkManager/dispatcher.d

[Michael Biebl]

Source: ntpsec
Version: 1.2.2+dfsg1-2
Severity: normal
Tags: patch
User: bi...@debian.org
Usertags: nm-hook-scripts

Hi,


your package currently installs a NetworkManager hook script in
/etc/NetworkManager/dispatcher.d

This practice is no longer recommended and instead package provided hook
scripts should be moved to /usr/lib/NetworkManager/dispatcher.d

/etc/NetworkManager/dispatcher.d is meant to be used for local
modifications.

Disabling a package provided hook script is as simple as running
touch /etc/NetworkManager/dispatcher.d/$hookscriptname

Overriding a packager provided hook can also be done by providing a
script in /etc with the same name.

Attached is a patch which updates ntpsec to use this new scheme.

Please consider it in your next upload.
I can also offer to NMU the package with this change.

Regards,
Michael
diff -Nru ntpsec-1.2.2+dfsg1/debian/changelog 
ntpsec-1.2.2+dfsg1/debian/changelog
--- ntpsec-1.2.2+dfsg1/debian/changelog 2023-07-30 21:04:02.0 +0200
+++ ntpsec-1.2.2+dfsg1/debian/changelog 2023-09-27 17:05:15.0 +0200
@@ -1,3 +1,11 @@
+ntpsec (1.2.2+dfsg1-2.1) UNRELEASED; urgency=medium
+
+  * Non-maintainer upload.
+  * Move NetworkManager hook scripts to /usr/lib/NetworkManager/dispatcher.d.
+(Closes: #-1)
+
+ -- Michael Biebl   Wed, 27 Sep 2023 17:05:15 +0200
+
 ntpsec (1.2.2+dfsg1-2) unstable; urgency=high
 
   * copyright: Update libjsmn comment
diff -Nru ntpsec-1.2.2+dfsg1/debian/ntpsec.conffiles 
ntpsec-1.2.2+dfsg1/debian/ntpsec.conffiles
--- ntpsec-1.2.2+dfsg1/debian/ntpsec.conffiles  1970-01-01 01:00:00.0 
+0100
+++ ntpsec-1.2.2+dfsg1/debian/ntpsec.conffiles  2023-09-27 17:05:14.0 
+0200
@@ -0,0 +1 @@
+remove-on-upgrade /etc/NetworkManager/dispatcher.d/ntpsec
diff -Nru ntpsec-1.2.2+dfsg1/debian/ntpsec-ntpdate.conffiles 
ntpsec-1.2.2+dfsg1/debian/ntpsec-ntpdate.conffiles
--- ntpsec-1.2.2+dfsg1/debian/ntpsec-ntpdate.conffiles  1970-01-01 
01:00:00.0 +0100
+++ ntpsec-1.2.2+dfsg1/debian/ntpsec-ntpdate.conffiles  2023-09-27 
17:05:06.0 +0200
@@ -0,0 +1 @@
+remove-on-upgrade /etc/NetworkManager/dispatcher.d/ntpsec-ntpdate
diff -Nru ntpsec-1.2.2+dfsg1/debian/rules ntpsec-1.2.2+dfsg1/debian/rules
--- ntpsec-1.2.2+dfsg1/debian/rules 2023-01-17 00:31:00.0 +0100
+++ ntpsec-1.2.2+dfsg1/debian/rules 2023-09-27 17:02:53.0 +0200
@@ -169,11 +169,11 @@
install -D -m 0644 debian/ntpsec.dhcp \
debian/ntpsec/etc/dhcp/dhclient-exit-hooks.d/ntpsec
install -D -m 0755 debian/ntpsec.networkmanager \
-   debian/ntpsec/etc/NetworkManager/dispatcher.d/ntpsec
+   debian/ntpsec/usr/lib/NetworkManager/dispatcher.d/ntpsec
install -D -m 0644 debian/ntpsec-ntpdate.dhcp \

debian/ntpsec-ntpdate/etc/dhcp/dhclient-exit-hooks.d/ntpsec-ntpdate
install -D -m 0755 debian/ntpsec-ntpdate.networkmanager \
-   
debian/ntpsec-ntpdate/etc/NetworkManager/dispatcher.d/ntpsec-ntpdate
+   
debian/ntpsec-ntpdate/usr/lib/NetworkManager/dispatcher.d/ntpsec-ntpdate
install -D -m 0644 debian/ntpsec-systemd-netif.path \
debian/ntpsec/lib/systemd/system/ntpsec-systemd-netif.path
install -D -m 0644 debian/ntpsec-systemd-netif.service \

Bug#1052529: proftpd: provide debug symbols for amd64 platform in sid

[Preuße]

On 27.09.2023 16:36, Dmitry Katsubo wrote:

On 2023-09-26 10:42, Preuße, Hilmar wrote:

On 24.09.2023 00:38, Dmitry Katsubo wrote:


Hello Dmitry,


Would be great to provide proftpd-*-dbgsym packages for amd64 platform. Current 
[1] platforms are:

alpha hppa ia64 m68k ppc64 riscv64 sh4 sparc64 x32

[1] https://packages.debian.org/search?keywords=proftpd



I just rebuilt the proftpd packages and the debug packages were generated. 
Further I see them on [2]. Maybe refer to [3] to learn how to get these symbols.

Hilmar

[2] https://deb.debian.org/debian-debug/pool/main/p/proftpd-dfsg/
[3] https://wiki.debian.org/HowToGetABacktrace


Thanks, I was able to install the packages. However I am stuck with
how to make advantage of that. I would expect that the symbols are
resolved directly in ProFTPD log:

ProFTPD killed (signal 15)
ProFTPD 1.3.8 standalone mode SHUTDOWN
ProFTPD 1.3.8 (stable) (built Sun Jul 2 2023 10:56:40 UTC) standalone mode 
STARTUP
(localhost[127.0.0.1]): -BEGIN STACK TRACE-
(localhost[127.0.0.1]): [0] /usr/lib/proftpd/mod_tls.so(+0x19ef5) 
[0x7f3b60371ef5]

>

Unfortunately I'm not a programmer and I don't know if your expectations 
are justified. Sorry, can't help here.



Then I tried the advise from [4]:



Please be advised, that we don't build the package mit Option 
--enable-devel..., so to do this you'd need to rebuild the package and 
use the options you need.


Hilmar
--
test mail


OpenPGP_signature
Description: OpenPGP digital signature

Bug#1053107: Provide squid-dbgsym packages for amd64 platform

[Dmitry Katsubo]

Package: squid-dbgsym
Version: 6.1-2

Would be great to provide squid-dbgsym packages for amd64 platform. Current [1] 
platforms are:

alpha hppa ia64 m68k ppc64 riscv64 sh4 sparc64 x32

[1] https://packages.debian.org/sid/squid-dbgsym

-- 
With best regards,
Dmitry