Bug#1041731: Hyphens in man pages

[G. Branden Robinson]

At 2023-10-14T20:51:27-0600, Antonio Russo wrote:
> I discovered a new pet peeve today: if you search for a command in a
> manual page, say -e in man 1 zgrep, it's a crapshot whether just
> searching for '-e' will find the command or not.  The reason is that
> "-" may been accidentally encoded as ‐ instead of -.

You can blame me for this.

https://git.savannah.gnu.org/cgit/groff.git/tree/NEWS?h=1.23.0#n206

...me, and man page authors who don't think about whether they intend
a hyphen or a minus sign when they strike the '-' key...

Quick background: in the context of Unix usage as documented by
nroff/troff, the dash used at the shell prompt, in text editors, and in
programming language source code is a "minus sign".  troff has an em
dash special character as well since the mid-1970s; groff adds an en
dash as well, and furthermore supports user definition of characters
providing access to any other sort of dash that comes down the Unicode
pike.  (Not that doing so is a good idea in a man page; see below
regarding a "restricted dialect" of man(7).)

> Now, depending on your email client and settings, the above will
> appear to be the ravings of an unhinged lunatic who wrote the same
> thing twice, or an unhinged lunatic who slammed their fists onto the
> keyboard.

This issue does indeed have a history of provoking unhinged lunacy.

Before we proceed, you might wish to be aware of
 and its
proposed remedy.

> The reason is that man(1) convert bare dashes (0x2D) to hyphens
> (U+2010).  These are not the same symbol: searching for one does not
> find the other without some kind of normalization, pasting commands
> with one vs. the other does different things.  New users who do not
> understand this will be discouraged trying to read manual pages.
> Chances are, they will fill forums with mundane questions that could
> and should have been addressed by a simple search of a manual page.

I run into this problem, too, since I dogfood my own changes.  When
irritated by this, I try the search again, replacing '-' with '.', which
has yet to fail me (and produces false positives surprisingly rarely).

For example, I've recently been playing with the mg(1) editor, and
observed extremely poor discipline in this area.  So I forked it on
GitHub and have been preparing a bunch of revisions.  I wrote a sed
script to fix its numerous hyphen/dash problems.[1]

> I recently fixed a ton of these in another upstream package with this
> vim "one-liner":
> 
> :%s/--\([a-z]\+\)\(-[a-z]\+\)*/\=substitute(submatch(0), '-', '\\-', 'g')/g

My Vimscript is not very sophisticated, but it looks like you're
replacing only hyphens that appear in long option names here.  That's
good, as you're unlikely to clobber any hyphens that should _not_ become
minus signs.

Such discernment is important.  Many people who want to "solve" this
issue forget (or ignore) that not every '-' is a minus sign.  Some are
actual hyphens, as in "long-term effects" and "word-aligned struct
members".  Trying to infer a distinction from white space adjacency also
won't work.  Consider the phrases "word- or byte-sized caching" and
"object-based vs. -oriented programming".  While sophistication with
compound hyphenated affixes is seldom seen in man pages, we most often
find it where a man page author has taken considerable care with their
technical writing.  Such pages are less likely than most to require
revision with blunt instruments like regular expression-based global
search and replace operations.

> However, this requires manual review

Surprisingly often, the composition of high-quality technical
documentation requires the engagement of a human brain.

> and does not fix the '-e' example from zgrep.

Mapping all hyphens and minus signs to a single character, as people
whose blood pressure spikes over this issue tend to promote as a first
resort, is an ineluctably information-discarding operation.  In my
opinion, man page source documents are not the correct place to discard
that information.

(I acknowledge that you didn't propose such a crude remedy; I write to
anticipate the inevitable follow-ups from people who will.)

Doing so at rendering time is much more defensible, and happens anyway
on devices that do not distinguish these characters in the first place.

> There are also a whole host of this kind of problem, e.g., dashes in
> URLs that get naievely pasted into man pages (another live example I
> just addressed).

Yes, people commonly type URLs and email addresses into man page sources
as they would into an MUA or browser navigation bar.  Since U+2010 is
difficult to encode in such things, the man(7) package could help by
performing an automatic character translation in this area.  However,
(1) no one's actually asked for this and (2) it would address only a
tiny part of the problem.  The means of "help" I have in mind is
employment of the groff man(7) extension macros `UR`/`UE` and `MT`/`ME`

Bug#1052857: marked as done (hackrf: FTBFS: unsatisfiable build-dependencies: libstdc++-arm-none-eabi-dev (= 15:12.2.rel1-1+23), gcc-arm-none-eabi (= 15:12.2.rel1-1))

[Debian Bug Tracking System]

Your message dated Sun, 15 Oct 2023 02:53:56 +
with message-id 
and subject line Bug#1052857: fixed in hackrf 2023.01.1-2
has caused the Debian Bug report #1052857,
regarding hackrf: FTBFS: unsatisfiable build-dependencies: 
libstdc++-arm-none-eabi-dev (= 15:12.2.rel1-1+23), gcc-arm-none-eabi (= 
15:12.2.rel1-1)
to be marked as done.

This means that you claim that the problem has been dealt with.
If this is not the case it is now your responsibility to reopen the
Bug report if necessary, and/or fix the problem forthwith.

(NB: If you are a system administrator and have no idea what this
message is talking about, this may indicate a serious mail system
misconfiguration somewhere. Please contact ow...@bugs.debian.org
immediately.)


-- 
1052857: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1052857
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Source: hackrf
Version: 2023.01.1-1
Severity: serious
Justification: FTBFS
Tags: trixie sid ftbfs
User: lu...@debian.org
Usertags: ftbfs-20230925 ftbfs-trixie

Hi,

During a rebuild of all packages in sid, your package failed to build
on amd64.


Relevant part (hopefully):
> +--+
> | Install package build dependencies  
>  |
> +--+
> 
> 
> Setup apt archive
> -
> 
> Merged Build-Depends: cmake, debhelper-compat (= 13), libfftw3-dev, 
> libusb-1.0-0-dev, pkg-config, build-essential, fakeroot, dfu-util, latexmk, 
> python3-sphinx, python3-sphinx-rtd-theme, python3-yaml, tex-gyre, 
> texlive-latex-extra, gcc-arm-none-eabi, libnewlib-arm-none-eabi, 
> libstdc++-arm-none-eabi-newlib
> Filtered Build-Depends: cmake, debhelper-compat (= 13), libfftw3-dev, 
> libusb-1.0-0-dev, pkg-config, build-essential, fakeroot, dfu-util, latexmk, 
> python3-sphinx, python3-sphinx-rtd-theme, python3-yaml, tex-gyre, 
> texlive-latex-extra, gcc-arm-none-eabi, libnewlib-arm-none-eabi, 
> libstdc++-arm-none-eabi-newlib
> dpkg-deb: building package 'sbuild-build-depends-main-dummy' in 
> '/<>/apt_archive/sbuild-build-depends-main-dummy.deb'.
> Ign:1 copy:/<>/apt_archive ./ InRelease
> Get:2 copy:/<>/apt_archive ./ Release [609 B]
> Ign:3 copy:/<>/apt_archive ./ Release.gpg
> Get:4 copy:/<>/apt_archive ./ Sources [934 B]
> Get:5 copy:/<>/apt_archive ./ Packages [882 B]
> Fetched 2425 B in 0s (0 B/s)
> Reading package lists...
> Reading package lists...
> 
> Install main build dependencies (apt-based resolver)
> 
> 
> Installing build dependencies
> Reading package lists...
> Building dependency tree...
> Some packages could not be installed. This may mean that you have
> requested an impossible situation or if you are using the unstable
> distribution that some required packages have not yet been created
> or been moved out of Incoming.
> The following information may help to resolve the situation:
> 
> The following packages have unmet dependencies:
>  libstdc++-arm-none-eabi-newlib : Depends: libstdc++-arm-none-eabi-dev (= 
> 15:12.2.rel1-1+23) but it is not going to be installed
>   Depends: gcc-arm-none-eabi (= 
> 15:12.2.rel1-1) but 15:12.3.rel1-1 is to be installed
> E: Unable to correct problems, you have held broken packages.
> apt-get failed.


The full build log is available from:
http://qa-logs.debian.net/2023/09/25/hackrf_2023.01.1-1_unstable.log

All bugs filed during this archive rebuild are listed at:
https://bugs.debian.org/cgi-bin/pkgreport.cgi?tag=ftbfs-20230925;users=lu...@debian.org
or:
https://udd.debian.org/bugs/?release=na&merged=ign&fnewerval=7&flastmodval=7&fusertag=only&fusertagtag=ftbfs-20230925&fusertaguser=lu...@debian.org&allbugs=1&cseverity=1&ctags=1&caffected=1#results

A list of current common problems and possible solutions is available at
http://wiki.debian.org/qa.debian.org/FTBFS . You're welcome to contribute!

If you reassign this bug to another package, please mark it as 'affects'-ing
this package. See https://www.debian.org/Bugs/server-control#affects

If you fail to reproduce this, please provide a build log and diff it with mine
so that we can identify if something relevant changed in the meantime.
--- End Message ---
--- Begin Message ---
Source: hackrf
Source-Version: 2023.01.1-2
Done: A. Maitland Bottoms 

We believe that the bug you reported is fixed in the latest version of
hackrf, 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.
A. Maitland Bottoms  (supplier of updated hackrf pac

Processed: Re: milkytracker crashes with signal 6 (double free detected in tcache 2)

[Debian Bug Tracking System]

Processing control commands:

> tags -1 patch fixed-upstream
Bug #1051256 [milkytracker] milkytracker crashes with signal 6 (double free 
detected in tcache 2)
Added tag(s) patch and fixed-upstream.

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

Processed: tagging 1051181

[Debian Bug Tracking System]

Processing commands for cont...@bugs.debian.org:

> tags 1051181 + pending
Bug #1051181 [fapolicyd] FTBFS: can't build package when user has more than 16 
supplementary groups
Added tag(s) pending.
> thanks
Stopping processing here.

Please contact me if you need assistance.
-- 
1051181: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1051181
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems

Bug#1053957: marked as done (src:phpldapadmin: autopkgtest failure on armhf and i386)

[Debian Bug Tracking System]

Your message dated Sat, 14 Oct 2023 23:19:34 +
with message-id 
and subject line Bug#1053957: fixed in phpldapadmin 1.2.6.6-2
has caused the Debian Bug report #1053957,
regarding src:phpldapadmin: autopkgtest failure on armhf and i386
to be marked as done.

This means that you claim that the problem has been dealt with.
If this is not the case it is now your responsibility to reopen the
Bug report if necessary, and/or fix the problem forthwith.

(NB: If you are a system administrator and have no idea what this
message is talking about, this may indicate a serious mail system
misconfiguration somewhere. Please contact ow...@bugs.debian.org
immediately.)


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

Source: phpldapadmin
Version: 1.2.6.3-0.3
Severity: serious
Control: close -1 1.2.6.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:phpldapadmin has been trying to migrate 
for 31 days [2]. Hence, I am filing this bug. The version in unstable 
gained an autopkgtest (thanks for that) but it fails on armhf and on i386.


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=phpldapadmin



OpenPGP_signature.asc
Description: OpenPGP digital signature
--- End Message ---
--- Begin Message ---
Source: phpldapadmin
Source-Version: 1.2.6.6-2
Done: William Desportes 

We believe that the bug you reported is fixed in the latest version of
phpldapadmin, 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 1053...@bugs.debian.org,
and the maintainer will reopen the bug report if appropriate.

Debian distribution maintenance software
pp.
William Desportes  (supplier of updated phpldapadmin 
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: Sun, 15 Oct 2023 00:43:30 +0200
Source: phpldapadmin
Architecture: source
Version: 1.2.6.6-2
Distribution: unstable
Urgency: medium
Maintainer: Fabio Tranchitella 
Changed-By: William Desportes 
Closes: 1053957
Changes:
 phpldapadmin (1.2.6.6-2) unstable; urgency=medium
 .
   * Fix armhf&i386 DEP-8 tests crash (Closes: #1053957)
Checksums-Sha1:
 ebf77b8166de20e98024703fae8c53958865605b 2151 phpldapadmin_1.2.6.6-2.dsc
 89bc5de7102489b8a5e8ee0eb93caa773c5cd2d4 35904 
phpldapadmin_1.2.6.6-2.debian.tar.xz
 92083cf1f2a4432dc611486126f199b12b30a93a 5672 
phpldapadmin_1.2.6.6-2_source.buildinfo
Checksums-Sha256:
 807b12c944533dc354e082a4fbb98e0df372230854db06ae91bf365f0f766771 2151 
phpldapadmin_1.2.6.6-2.dsc
 4245b51d54bec0603ea4c3ea4f522ba5014132c6cb8272c48fbedde42703bb02 35904 
phpldapadmin_1.2.6.6-2.debian.tar.xz
 5ec3c1fec0c4c6935d67f426b995b4ead570504db1e75136b81d260028481499 5672 
phpldapadmin_1.2.6.6-2_source.buildinfo
Files:
 f4040799601b67384c1de42176925291 2151 admin optional phpldapadmin_1.2.6.6-2.dsc
 8c2beffe83afa5eb56f702e4bf22217e 35904 admin optional 
phpldapadmin_1.2.6.6-2.debian.tar.xz
 837828d9d63fbb4836dfb9f904e00146 5672 admin optional 
phpldapadmin_1.2.6.6-2_source.buildinfo

-BEGIN PGP SIGNATURE-

iQIzBAEBCgAdFiEExNkf3872tKPGU/14kKDvG4JRqIkFAmUrHMsACgkQkKDvG4JR
qIk49Q//fP8OozrCvRXpBOXiMVOFehFL4a1YKEL74jQeRDEfpRVq54DjlFKJDrpU
Hz2qy19W+VbwOZszMGXV0am02+a5bLFKMGfdXxAa7yyqd4eefXkG23FaDofwpxKF
UkjyyzancIdh7i7uShzDVciLvzroKHbYB6x70QWp9xyPGKi

Bug#1053960: marked as done (texlive-fonts-extra: missing Breaks+Replaces: texlive-fonts-extra-links (<< 2023.20231007))

[Debian Bug Tracking System]

Your message dated Sat, 14 Oct 2023 23:05:38 +
with message-id 
and subject line Bug#1053960: fixed in texlive-extra 2023.20231007-2
has caused the Debian Bug report #1053960,
regarding texlive-fonts-extra: missing Breaks+Replaces: 
texlive-fonts-extra-links (<< 2023.20231007)
to be marked as done.

This means that you claim that the problem has been dealt with.
If this is not the case it is now your responsibility to reopen the
Bug report if necessary, and/or fix the problem forthwith.

(NB: If you are a system administrator and have no idea what this
message is talking about, this may indicate a serious mail system
misconfiguration somewhere. Please contact ow...@bugs.debian.org
immediately.)


-- 
1053960: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1053960
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Package: texlive-fonts-extra
Version: 2023.20231007-1
Severity: serious
User: debian...@lists.debian.org
Usertags: piuparts

Hi,

during a test with piuparts I noticed your package fails to upgrade from
'testing'.
It installed fine in 'testing', then the upgrade to 'sid' fails
because it tries to overwrite other packages files without declaring a
Breaks+Replaces relation.

See policy 7.6 at
https://www.debian.org/doc/debian-policy/ch-relationships.html#overwriting-files-and-replacing-packages-replaces

>From the attached log (scroll to the bottom...):

  Preparing to unpack .../texlive-fonts-extra_2023.20231007-1_all.deb ...
  Unpacking texlive-fonts-extra (2023.20231007-1) ...
  dpkg: error processing archive 
/var/cache/apt/archives/texlive-fonts-extra_2023.20231007-1_all.deb (--unpack):
   trying to overwrite 
'/usr/share/texlive/texmf-dist/fonts/opentype/huerta/alegreya/AlegreyaSans-Black.otf',
 which is also in package texlive-fonts-extra-links 2023.20230613-2
  Errors were encountered while processing:
   /var/cache/apt/archives/texlive-fonts-extra_2023.20231007-1_all.deb


cheers,

Andreas


texlive-fonts-extra-links=2023.20230613-2_texlive-fonts-extra=2023.20231007-1.log.gz
Description: application/gzip
--- End Message ---
--- Begin Message ---
Source: texlive-extra
Source-Version: 2023.20231007-2
Done: Hilmar Preusse 

We believe that the bug you reported is fixed in the latest version of
texlive-extra, 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 1053...@bugs.debian.org,
and the maintainer will reopen the bug report if appropriate.

Debian distribution maintenance software
pp.
Hilmar Preusse  (supplier of updated texlive-extra 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: Sat, 14 Oct 2023 22:18:04 +
Source: texlive-extra
Architecture: source
Version: 2023.20231007-2
Distribution: unstable
Urgency: high
Maintainer: Debian TeX Task Force 
Changed-By: Hilmar Preusse 
Closes: 1053960
Changes:
 texlive-extra (2023.20231007-2) unstable; urgency=high
 .
   * Fix version for Breaks/Replaces (Closes: #1053960).
Checksums-Sha1:
 f0492dfe94d2bab2552d4c5a92e881665079cfdc 3995 texlive-extra_2023.20231007-2.dsc
 bdf5d9d872907e8d4f4631d866a43b2de9d6a44b 195136 
texlive-extra_2023.20231007-2.debian.tar.xz
 0757d82cbd6b2854b2e18748696b472ac70b9b59 6008 
texlive-extra_2023.20231007-2_source.buildinfo
Checksums-Sha256:
 9bd3cf6ac8bcaa5327a397dc1724c04a19a8fc5ff9406289d96a747ef1272a52 3995 
texlive-extra_2023.20231007-2.dsc
 0bac1aa18ca6d17702e17f9f444918b48ac3a11fde794039f96e779c0c90f156 195136 
texlive-extra_2023.20231007-2.debian.tar.xz
 84134d18ddbf763b1c4ff33145ddee01693abe5734c3ffdddf84cca67a5b67d6 6008 
texlive-extra_2023.20231007-2_source.buildinfo
Files:
 a43f8147680937f7bb40df8e1ec91976 3995 tex optional 
texlive-extra_2023.20231007-2.dsc
 e6b38d0cbea831ed65c74783380aa64f 195136 tex optional 
texlive-extra_2023.20231007-2.debian.tar.xz
 b3213075545de8e73e6cce3daa6578a0 6008 tex optional 
texlive-extra_2023.20231007-2_source.buildinfo

-BEGIN PGP SIGNATURE-

iQKTBAEBCgB9FiEEaXGmC/nkbIhxf16kxiZYRqvgLIsFAmUrF31fFIAALgAo
aXNzdWVyLWZwckBub3RhdGlvbnMub3BlbnBncC5maWZ0aGhvcnNlbWFuLm5ldDY5
NzFBNjBCRjlFNDZDODg3MTdGNUVBNEM2MjY1ODQ2QUJFMDJDOEIACgkQxiZYRqvg
LItjFxAAjf4IA+r9UgqM8Xj+uw9N4yAaUv7gDvh1W5+92ks9teegAQDcKdri06K+
spxpsyXZlwrv4996kGqc3BDIh8dj94JZdCCBB4dnYz8toyGhcKFeqoH1djBBWiwJ
cDBy2z9Xsz/lCFv+syB/RdtwlQQjSKheLLk6BCBiF9o5oR/IopjMazNcmB49q90M
UU86hNHgAT+wqz8k4pDtyJWE+eVBwO8sg0yh05BWNpEj4jpR5T0AbVcUQ3lVRKHO
/3MLJ/JBFKPUWVyrptXU1Q2GVp0SqqQxQbFs9JwTIebnffeSZP2gnoeKO8ei0f+M
IM7VU5ujbPazAaW69WNecaNtpu9rPBf7DaCkcNedD4BYXlSwBS5yvAN7ec+ukkom
omOGxVNMlRSWk+Ivy2w3kkBTDQsaOZ055uaJgY/2qwgoUGO/wiBzvBL/bLoABadM
gh3hwow06w5IL9/xRr1n

Processed: your mail

[Debian Bug Tracking System]

Processing commands for cont...@bugs.debian.org:

> notfound 1053957 phpldapadmin/1.2.6.3-0.3
Bug #1053957 [src:phpldapadmin] src:phpldapadmin: fails to migrate to testing 
for too long: autopkgtest failure on armhf and i386
No longer marked as found in versions phpldapadmin/1.2.6.3-0.3.
> found 1053957 phpldapadmin/1.2.6.6-1
Bug #1053957 [src:phpldapadmin] src:phpldapadmin: fails to migrate to testing 
for too long: autopkgtest failure on armhf and i386
Marked as found in versions phpldapadmin/1.2.6.6-1.
> retitle 1053957 src:phpldapadmin: autopkgtest failure on armhf and i386
Bug #1053957 [src:phpldapadmin] src:phpldapadmin: fails to migrate to testing 
for too long: autopkgtest failure on armhf and i386
Changed Bug title to 'src:phpldapadmin: autopkgtest failure on armhf and i386' 
from 'src:phpldapadmin: fails to migrate to testing for too long: autopkgtest 
failure on armhf and i386'.
> stop
Stopping processing here.

Please contact me if you need assistance.
-- 
1053957: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1053957
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems

Bug#1041795: marked as done (eq10q: depends on unmaintained gtkmm2.4, and indirectly on GTK 2)

[Debian Bug Tracking System]

Your message dated Sat, 14 Oct 2023 22:49:17 +
with message-id 
and subject line Bug#1041795: fixed in eq10q 2.2~repack0-5
has caused the Debian Bug report #1041795,
regarding eq10q: depends on unmaintained gtkmm2.4, and indirectly on GTK 2
to be marked as done.

This means that you claim that the problem has been dealt with.
If this is not the case it is now your responsibility to reopen the
Bug report if necessary, and/or fix the problem forthwith.

(NB: If you are a system administrator and have no idea what this
message is talking about, this may indicate a serious mail system
misconfiguration somewhere. Please contact ow...@bugs.debian.org
immediately.)


-- 
1041795: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1041795
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Source: eq10q
Version: 2.2~repack0-4
Severity: normal
Tags: trixie sid
User: pkg-gnome-maintain...@lists.alioth.debian.org
Usertags: gtk2 oldlibs
Control: block 947713 by -1
Control: block 967497 by -1

eq10q Build-Depends on packages from src:gtkmm2.4, a C++ binding for
GTK 2. GTK 2 was superseded by GTK 3 in 2011 (see
). It has been discontinued by its upstream
developer and no longer receives any upstream maintenance at all.

The direct replacement for gtkmm2.4 is gtkmm3.0, a C++ API for GTK 3.
Please see  for
information about porting from gtkmm2.4 to gtkmm3.0, and
 for general information
about porting from GTK 2 to GTK 3.

Thanks,
smcv
--- End Message ---
--- Begin Message ---
Source: eq10q
Source-Version: 2.2~repack0-5
Done: Bastian Germann 

We believe that the bug you reported is fixed in the latest version of
eq10q, 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 1041...@bugs.debian.org,
and the maintainer will reopen the bug report if appropriate.

Debian distribution maintenance software
pp.
Bastian Germann  (supplier of updated eq10q 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: Sun, 15 Oct 2023 00:15:15 +0200
Source: eq10q
Architecture: source
Version: 2.2~repack0-5
Distribution: unstable
Urgency: medium
Maintainer: Debian Multimedia Maintainers 
Changed-By: Bastian Germann 
Closes: 1041795 1044400
Changes:
 eq10q (2.2~repack0-5) unstable; urgency=medium
 .
   * Team upload.
   * Prevent gui build (Closes: #1041795)
   * Clean generated and built files (Closes: #1044400)
Checksums-Sha1:
 e39b6fa3ef58a8cba0e16251c8b8be982a956c42 1856 eq10q_2.2~repack0-5.dsc
 2fff152e479c125e859d6fb5099153e23763b728 6088 eq10q_2.2~repack0-5.debian.tar.xz
 a70cb33cac03c41f0cb048e8eea169e83da4a0e2 6468 
eq10q_2.2~repack0-5_source.buildinfo
Checksums-Sha256:
 87fb6800cd676877d2e854dee997decc5900e2abeab661149cba05bc590d205e 1856 
eq10q_2.2~repack0-5.dsc
 9c8b5fb0ec4ea341abff058100b71a3d7ba5adcbbe2bd6197b377220dca0bf8b 6088 
eq10q_2.2~repack0-5.debian.tar.xz
 198d7062d6ace3b08886783ee4020dea9322250bb18b101041815ccde40d1520 6468 
eq10q_2.2~repack0-5_source.buildinfo
Files:
 f206829a4d8ce336901974366d15e0ce 1856 sound optional eq10q_2.2~repack0-5.dsc
 f4b6727ebaea41e9df0fcca4e9fed9f6 6088 sound optional 
eq10q_2.2~repack0-5.debian.tar.xz
 4efb017739b318c66eebd56d1d10aa77 6468 sound optional 
eq10q_2.2~repack0-5_source.buildinfo

-BEGIN PGP SIGNATURE-

iQHEBAEBCgAuFiEEQGIgyLhVKAI3jM5BH1x6i0VWQxQFAmUrFBUQHGJhZ2VAZGVi
aWFuLm9yZwAKCRAfXHqLRVZDFPJGDADIZhPSib5du+pu27jnXWVXtPl2TkT1d9IP
Ru8jAP0rfrX7kakz7se/aLRnc4z/x9aLLSkZVe7C8AbujEXTBOkPAI2NQK8kIYH1
xpoYwPPXX7G9kzeI10+r8FuVmUYFWr/nwVSOFvHNBysmGTE6Ai63Ze04rxJ7HaoD
KoWo3jumUvWO7Bg4etbEexeoFjUknoSNpLVz14rVIUuVZS6j5EF27Sf5dgakIBS2
wLLhwPOr65Ioa0Cqr8XDHVxKa3HEMb36Idg6964TdmXsHjifKLERKOi15tP/FtGz
kHhDavlHkMEOF+DXuxm6T+O1eYagWjEOva+A0Nih1CEq7O0B6V/tqqL5CuGop1Jb
PiNrsB9hSyQNfg6S+0zH50td44DiBULsstkkx9656OtX50wsEWd1urV3Wkfx91CY
qBzSTfkZukmFvZLcn0/j/he6HsgEb5p+O5v/6utetHn6kayanKQ0YhL8/xIUiv10
FsOsaSBBgcKs4f7QRU2/n5jzG5LYJM0=
=oQJF
-END PGP SIGNATURE End Message ---

Processed (with 1 error): your mail

[Debian Bug Tracking System]

Processing commands for cont...@bugs.debian.org:

> reopen 1053957
Bug #1053957 {Done: Paul Gevers } [src:phpldapadmin] 
src:phpldapadmin: fails to migrate to testing for too long: autopkgtest failure 
on armhf and i386
'reopen' may be inappropriate when a bug has been closed with a version;
all fixed versions will be cleared, and you may need to re-add them.
Bug reopened
No longer marked as fixed in versions phpldapadmin/1.2.6.6-1.
> tags 1053957 + confirmed patch
Unknown command or malformed arguments to command.
> owner 1053957 !
Bug #1053957 [src:phpldapadmin] src:phpldapadmin: fails to migrate to testing 
for too long: autopkgtest failure on armhf and i386
Owner recorded as William Desportes .
> stop
Stopping processing here.

Please contact me if you need assistance.
-- 
1053957: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1053957
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems

Bug#1053957: (no subject)

[William Desportes]

Control: reopen -1
Control: tags -1 + confirmed patch

Thank you for opening this bug.
Until now I was waiting on chromium but I have to realize my bug may be due to 
their stuff but I need to more on.
For now I managed right now to reproduce the bug on i386 using:

- docker run --rm --privileged multiarch/qemu-user-static --reset -p yes
- docker run -v $PWD:/app --workdir /app --rm i386/debian:bookworm /bin/bash

And installing all the tooling and stuff.

Then I get "selenium.common.exceptions.WebDriverException: Message: unknown error: 
session deleted because of page crash"

It seems like the crash goes away if I send the keys line by line and not all 
the text at once.
Maybe a memory issue of some type.

Works:
    for line in Simpsons.split('\n'):
    import_area.send_keys(line + "\n")

Crashes:
   import_area.send_keys(Simpsons)

To be continued :)

Processed: Bug#1041795 marked as pending in eq10q

[Debian Bug Tracking System]

Processing control commands:

> tag -1 pending
Bug #1041795 [src:eq10q] eq10q: depends on unmaintained gtkmm2.4, and 
indirectly on GTK 2
Added tag(s) pending.

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

Bug#1041795: marked as pending in eq10q

[Bastian Germann]

Control: tag -1 pending

Hello,

Bug #1041795 in eq10q reported by you has been fixed in the
Git repository and is awaiting an upload. You can see the commit
message below and you can check the diff of the fix at:

https://salsa.debian.org/multimedia-team/eq10q/-/commit/391b0922f3e00ec84f322854fe8e752aea058ff7


Prevent gui build (Closes: #1041795)


(this message was generated automatically)
-- 
Greetings

https://bugs.debian.org/1041795

Processed: breaks /usr/bin/flask; severity grave

[Debian Bug Tracking System]

Processing commands for cont...@bugs.debian.org:

> severity 1036167 grave
Bug #1036167 [flask-appbuilder] flask-appbuilder: Fails to build against 
python3-flask-sqlalchemy 3.0.3-1
Severity set to 'grave' from 'serious'
> thanks
Stopping processing here.

Please contact me if you need assistance.
-- 
1036167: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1036167
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems

Bug#1036167: breaks /usr/bin/flask; severity grave

[Lionel Élie Mamane]

severity 1036167 grave
thanks

This is worse than just a FTBFS; when the binary package is installed
(against versions of python3-flask-sqlalchemy now in stable, testing
or unstable), not only is flask-appbuilder completely non-functional
as far as I can determing, but even worse it breaks /usr/bin/flask
even when not using flask-appbuilder at all.

>From what I can observe, this is at least grave under:

  makes the package in question unusable or mostly so

Bug#1053960: texlive-fonts-extra: missing Breaks+Replaces: texlive-fonts-extra-links (<< 2023.20231007)

[Andreas Beckmann]

Package: texlive-fonts-extra
Version: 2023.20231007-1
Severity: serious
User: debian...@lists.debian.org
Usertags: piuparts

Hi,

during a test with piuparts I noticed your package fails to upgrade from
'testing'.
It installed fine in 'testing', then the upgrade to 'sid' fails
because it tries to overwrite other packages files without declaring a
Breaks+Replaces relation.

See policy 7.6 at
https://www.debian.org/doc/debian-policy/ch-relationships.html#overwriting-files-and-replacing-packages-replaces

>From the attached log (scroll to the bottom...):

  Preparing to unpack .../texlive-fonts-extra_2023.20231007-1_all.deb ...
  Unpacking texlive-fonts-extra (2023.20231007-1) ...
  dpkg: error processing archive 
/var/cache/apt/archives/texlive-fonts-extra_2023.20231007-1_all.deb (--unpack):
   trying to overwrite 
'/usr/share/texlive/texmf-dist/fonts/opentype/huerta/alegreya/AlegreyaSans-Black.otf',
 which is also in package texlive-fonts-extra-links 2023.20230613-2
  Errors were encountered while processing:
   /var/cache/apt/archives/texlive-fonts-extra_2023.20231007-1_all.deb


cheers,

Andreas


texlive-fonts-extra-links=2023.20230613-2_texlive-fonts-extra=2023.20231007-1.log.gz
Description: application/gzip

Bug#1053898: Hardening rsyslog.service breaks debian/tests/logcheck autopkgtest

[Richard Lewis]

On Fri, 13 Oct 2023 at 20:27, Michael Biebl  wrote:

> It turns out that `PrivateTmp=yes` breaks the logcheck autopkgtest.

i think the test tells rsyslog to write to /tmp and then calls
logcheck on the output outside the unit. But the PrivateTmp=true means
rsyslog is actually writing to [somewhere else] bind-mounted over
/tmp. It should be easy to fix by making the test use /var/log instead
of /tmp - will check and send a MR

Bug#1053958: src:python-django-storages: fails to migrate to testing for too long: uploader built arch:all

[Paul Gevers]

Source: python-django-storages
Version: 1.13.2-1
Severity: serious
Control: close -1 1.14-1
Tags: sid trixie pending
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:python-django-storages has been trying to 
migrate for 31 days [2]. Hence, I am filing this 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.


Your package is only blocked because the arch:all binary package(s) 
aren't built on a buildd. Unfortunately the Debian infrastructure 
doesn't allow arch:all packages to be properly binNMU'ed. Hence, I will 
shortly do a no-changes source-only upload to DELAYED/15, closing this 
bug. Please let me know if I should delay or cancel that upload.


Paul

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



OpenPGP_signature.asc
Description: OpenPGP digital signature

Processed: src:python-django-storages: fails to migrate to testing for too long: uploader built arch:all

[Debian Bug Tracking System]

Processing control commands:

> close -1 1.14-1
Bug #1053958 [src:python-django-storages] src:python-django-storages: fails to 
migrate to testing for too long: uploader built arch:all
Marked as fixed in versions python-django-storages/1.14-1.
Bug #1053958 [src:python-django-storages] src:python-django-storages: fails to 
migrate to testing for too long: uploader built arch:all
Marked Bug as done

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

Processed: src:phpldapadmin: fails to migrate to testing for too long: autopkgtest failure on armhf and i386

[Debian Bug Tracking System]

Processing control commands:

> close -1 1.2.6.6-1
Bug #1053957 [src:phpldapadmin] src:phpldapadmin: fails to migrate to testing 
for too long: autopkgtest failure on armhf and i386
Marked as fixed in versions phpldapadmin/1.2.6.6-1.
Bug #1053957 [src:phpldapadmin] src:phpldapadmin: fails to migrate to testing 
for too long: autopkgtest failure on armhf and i386
Marked Bug as done

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

Bug#1053957: src:phpldapadmin: fails to migrate to testing for too long: autopkgtest failure on armhf and i386

[Paul Gevers]

Source: phpldapadmin
Version: 1.2.6.3-0.3
Severity: serious
Control: close -1 1.2.6.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:phpldapadmin has been trying to migrate 
for 31 days [2]. Hence, I am filing this bug. The version in unstable 
gained an autopkgtest (thanks for that) but it fails on armhf and on i386.


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=phpldapadmin



OpenPGP_signature.asc
Description: OpenPGP digital signature

Processed: fix meta info to enable migration

[Debian Bug Tracking System]

Processing commands for cont...@bugs.debian.org:

> # the tags prevent migration
> tags 958686 = sid trixie fixed-upstream
Bug #958686 [node-yarnpkg] node-yarnpkg: Remove dependency to node-request
Added tag(s) trixie; removed tag(s) bookworm and bookworm-ignore.
> thanks
Stopping processing here.

Please contact me if you need assistance.
-- 
958686: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=958686
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems

Bug#1053956: src:alsa-lib: fails to migrate to testing for too long: unresolved RC bugs

[Paul Gevers]

Source: alsa-lib
Version: 1.2.9-2
Severity: serious
Control: close -1 1.2.10-1
Tags: sid trixie
User: release.debian@packages.debian.org
Usertags: out-of-sync
Control: block -1 by 1052720
Control: block -1 by 1051901

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:alsa-lib has been trying to migrate for 31 
days [2]. Hence, I am filing this bug. The version in unstable has 
unresolved RC bugs.


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=alsa-lib



OpenPGP_signature.asc
Description: OpenPGP digital signature

Processed: src:alsa-lib: fails to migrate to testing for too long: unresolved RC bugs

[Debian Bug Tracking System]

Processing control commands:

> close -1 1.2.10-1
Bug #1053956 [src:alsa-lib] src:alsa-lib: fails to migrate to testing for too 
long: unresolved RC bugs
Marked as fixed in versions alsa-lib/1.2.10-1.
Bug #1053956 [src:alsa-lib] src:alsa-lib: fails to migrate to testing for too 
long: unresolved RC bugs
Marked Bug as done
> block -1 by 1052720
Bug #1053956 {Done: Paul Gevers } [src:alsa-lib] 
src:alsa-lib: fails to migrate to testing for too long: unresolved RC bugs
1053956 was not blocked by any bugs.
1053956 was not blocking any bugs.
Added blocking bug(s) of 1053956: 1052720
> block -1 by 1051901
Bug #1053956 {Done: Paul Gevers } [src:alsa-lib] 
src:alsa-lib: fails to migrate to testing for too long: unresolved RC bugs
1053956 was blocked by: 1052720
1053956 was not blocking any bugs.
Added blocking bug(s) of 1053956: 1051901

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

Bug#1053539: marked as done (package contains license CC-BY-2.0)

[Debian Bug Tracking System]

Your message dated Sat, 14 Oct 2023 17:58:25 +
with message-id 
and subject line Bug#1053539: fixed in retroarch-assets 1.7.6+git20230911+dfsg-1
has caused the Debian Bug report #1053539,
regarding package contains license CC-BY-2.0
to be marked as done.

This means that you claim that the problem has been dealt with.
If this is not the case it is now your responsibility to reopen the
Bug report if necessary, and/or fix the problem forthwith.

(NB: If you are a system administrator and have no idea what this
message is talking about, this may indicate a serious mail system
misconfiguration somewhere. Please contact ow...@bugs.debian.org
immediately.)


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

Package: retroarch-assets
Version: 1.7.6git20221024dfsg-3
Severity: serious
User: alteh...@debian.org
Usertags: license
thanks


Hi,

unfortunately your package contains files with license: CC-BY-2.0

   rgui/wallpaper/mystery_blocks*

As you can see on [1] this license is not compatible with DFSG, so please
remove the files or move the package to non-free.

Thanks!
 Thorsten

[1] https://wiki.debian.org/DFSGLicenses
--- End Message ---
--- Begin Message ---
Source: retroarch-assets
Source-Version: 1.7.6+git20230911+dfsg-1
Done: Jonathan McDowell 

We believe that the bug you reported is fixed in the latest version of
retroarch-assets, 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 1053...@bugs.debian.org,
and the maintainer will reopen the bug report if appropriate.

Debian distribution maintenance software
pp.
Jonathan McDowell  (supplier of updated retroarch-assets 
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: Sat, 14 Oct 2023 18:12:17 +0100
Source: retroarch-assets
Architecture: source
Version: 1.7.6+git20230911+dfsg-1
Distribution: unstable
Urgency: medium
Maintainer: Debian Games Team 
Changed-By: Jonathan McDowell 
Closes: 1045767 1053539
Changes:
 retroarch-assets (1.7.6+git20230911+dfsg-1) unstable; urgency=medium
 .
   * New upstream snapshot
 * Removes rgui/wallpaper/mystery_blocks* (Closes: #1053539)
   * Fix clean target to remove generated assets (Closes: #1045767)
   * Add myself to Uploaders
Checksums-Sha1:
 d286b718fd7b4dea477527151e97382b4581438a 2166 
retroarch-assets_1.7.6+git20230911+dfsg-1.dsc
 9c9371982e77decbdccd2bcd9c262d35fd9fe799 126488956 
retroarch-assets_1.7.6+git20230911+dfsg.orig.tar.xz
 9ec0d8a2cf65721f83d508e1a1e206cd595d72d3 18300 
retroarch-assets_1.7.6+git20230911+dfsg-1.debian.tar.xz
 67b66ec7f8af21fbfa1396ccc69bcd17e5a6a48c 11496 
retroarch-assets_1.7.6+git20230911+dfsg-1_amd64.buildinfo
Checksums-Sha256:
 db6924651689fccb3559d2f79a30c0c17bfb1841dc74511d674908ab4deb1082 2166 
retroarch-assets_1.7.6+git20230911+dfsg-1.dsc
 7459345de3bcf84c043f17a10064c755ac4a20893bf71f96265ec858cd522f3f 126488956 
retroarch-assets_1.7.6+git20230911+dfsg.orig.tar.xz
 d2620c5c4ac8dcad1147f53c3fb50c7688aa677057004b7c5ab263adcd21dc83 18300 
retroarch-assets_1.7.6+git20230911+dfsg-1.debian.tar.xz
 537a373cfd8281784550962e53441b45473b4f525a5b59f96d3cd27e501c54fc 11496 
retroarch-assets_1.7.6+git20230911+dfsg-1_amd64.buildinfo
Files:
 12fbb28cb215a0572a46e90398844239 2166 otherosfs optional 
retroarch-assets_1.7.6+git20230911+dfsg-1.dsc
 7e1e2633a84769ec4b4634eca4b552dd 126488956 otherosfs optional 
retroarch-assets_1.7.6+git20230911+dfsg.orig.tar.xz
 f072d1323ad1b5a4708f643e4991c555 18300 otherosfs optional 
retroarch-assets_1.7.6+git20230911+dfsg-1.debian.tar.xz
 62ee5abf3eae739b76922b108c09d4f5 11496 otherosfs optional 
retroarch-assets_1.7.6+git20230911+dfsg-1_amd64.buildinfo

-BEGIN PGP SIGNATURE-

iQIzBAEBCgAdFiEERUuPEyEc/2gMWDpQ/xYvxc8/utEFAmUq0ZMACgkQ/xYvxc8/
utE+WhAAl0WohNFk2oEWEQcHO7rs9Y7UfbTJ+Mbz3dyhm0pUuHZ0/sKK+iG1oRfi
lwjJ0Mjo21gx5LXN5A9GjXK9ZesLpy+YMNtK+6XoPVhf/Mbvg8snrdwSsHNbu44K
x8DM3M7Rc/QDk9/M5r5d66XvFmQ0T+AaGA1j1uh4ukbWvq8bMknK+ndCPxLOoFA8
qMKs6RwMHddXvWJSwtv1LBJ6Fggu9IvoTTh9JvIJi4QCgg7xN0v1lIon1mq0U9TO
O9Jq7dW22a6ubmrrBb07pAeTObNO6mrec6CVLJApLIEc52cIC24PVGZisN5kKLsG
voHkLE6mtxrY3lxhtKD5tW7UGzKYPuxftyERQx89PxgotV9Y6W1t3O7ohpIZX265
qPHJkE51Nc97xchkTJpYfLV7aG8KrT5SbyZ+c/fztq+++O4kFDK5UCWg5KVPSasC
vc3lPliGQTXxZM+k5Hx5bf/AwyOMRqGNKzHq5LS5Eq1IHvBF40k361McXgP4hFk1
BToRBGdlt34hGRPyWLaE4jgzMQVlFxXfoHQLuz7LITjj7+jQaxDUmJP5ooStlFE3
75etfTg2in7KHhQhaB3ZoISWJpxiICGbAIZGsxlOD3GtPCfb3wcN3H19A5ahpjx3
bQca6NRPJ8dxMKqBsnEU/FsTy/lq07pP5uTCZn+lw6MGTxhdSr8=
=Hy+S
-END PGP SIGNATURE End Message ---

Bug#1053563: marked as done (glueviz: doesn't start anymore)

[Debian Bug Tracking System]

Your message dated Sat, 14 Oct 2023 17:54:48 +
with message-id 
and subject line Bug#1053563: fixed in glueviz 1.0.1+dfsg-3
has caused the Debian Bug report #1053563,
regarding glueviz: doesn't start anymore
to be marked as done.

This means that you claim that the problem has been dealt with.
If this is not the case it is now your responsibility to reopen the
Bug report if necessary, and/or fix the problem forthwith.

(NB: If you are a system administrator and have no idea what this
message is talking about, this may indicate a serious mail system
misconfiguration somewhere. Please contact ow...@bugs.debian.org
immediately.)


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

Package: glueviz
Version: 1.0.1+dfsg-2
Severity: serious

Dear maintainer,

when starting glue on Debian testing, I get a Python error:

$ glue
/usr/bin/glue:6: DeprecationWarning: pkg_resources is deprecated as an API. See 
https://setuptools.pypa.io/en/latest/pkg_resources.html
  from pkg_resources import load_entry_point
QSocketNotifier: Can only be used with threads started with QThread
0.00s - Debugger warning: It seems that frozen modules are being used, which may
0.00s - make the debugger miss breakpoints. Please pass -Xfrozen_modules=off
0.00s - to python to disable frozen modules.
0.00s - Note: Debugging will proceed. Set PYDEVD_DISABLE_FILE_VALIDATION=1 to 
disable this validation.
Traceback (most recent call last):
  File "/usr/bin/glue", line 11, in 
sys.exit(load_entry_point('glue_core==1.0.1', 'gui_scripts', 'glue')())
 ^
  File "/usr/lib/python3/dist-packages/glue/main.py", line 259, in main
start_glue(**kwargs)
  File "/usr/lib/python3/dist-packages/glue/main.py", line 156, in start_glue
load_plugins(splash=splash, require_qt_plugins=True)
  File "/usr/lib/python3/dist-packages/glue/main.py", line 347, in load_plugins
splash.set_progress(100. * iplugin / float(n_plugins))
  File "/usr/lib/python3/dist-packages/glue/app/qt/splash_screen.py", line 31, 
in set_progress
self.progress.setValue(value)
TypeError: setValue(self, value: int): argument 1 has unexpected type 'float'

Probably, it needs an update to the latest version.

Best

Ole
--- End Message ---
--- Begin Message ---
Source: glueviz
Source-Version: 1.0.1+dfsg-3
Done: Ole Streicher 

We believe that the bug you reported is fixed in the latest version of
glueviz, 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 1053...@bugs.debian.org,
and the maintainer will reopen the bug report if appropriate.

Debian distribution maintenance software
pp.
Ole Streicher  (supplier of updated glueviz 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: Sat, 14 Oct 2023 18:49:55 +0200
Source: glueviz
Architecture: source
Version: 1.0.1+dfsg-3
Distribution: unstable
Urgency: medium
Maintainer: Debian Astronomy Maintainers 

Changed-By: Ole Streicher 
Closes: 1053563
Changes:
 glueviz (1.0.1+dfsg-3) unstable; urgency=medium
 .
   * Team upload.
   * Move non-free file exclusion to d/copyright
   * Switch patches to gbp style
   * Pass `int` argument to `QProgressBar.setValue` (Closes: #1053563)
   * Push Standards-Version to 4.6.2. No changes needed
   * Remove outdated versionized dependencies
Checksums-Sha1:
 9f3f3c5c3aa996bf0a6038c32f20523fff4843aa 2314 glueviz_1.0.1+dfsg-3.dsc
 43ec5d55387d93d69f369cc3ce7854eb09ba18dc 14284 
glueviz_1.0.1+dfsg-3.debian.tar.xz
Checksums-Sha256:
 ab14dbdfb22cb39bc6167182d584ed64e09a9f8b770df3a687ce0b332e0837ff 2314 
glueviz_1.0.1+dfsg-3.dsc
 967560bfb368c4e62af96d45fc6da80fd48680e78c85d5a051b1e1a8df4c9e45 14284 
glueviz_1.0.1+dfsg-3.debian.tar.xz
Files:
 9956a1a14a20cafadfd8bae99353eabb 2314 science optional glueviz_1.0.1+dfsg-3.dsc
 1f8f186b48c89492de8b264c7b1e943d 14284 science optional 
glueviz_1.0.1+dfsg-3.debian.tar.xz

-BEGIN PGP SIGNATURE-

iQIzBAEBCgAdFiEEuvxshffLFD/utvsVcRWv0HcQ3PcFAmUqyL8ACgkQcRWv0HcQ
3PclnhAA27keD74PvKuAZzCOvmP6vrRuJ0THsd7PONXJA/JMHBNcLFhG62gTJ1G4
a2+XJ5ZGGj3wnIh+w22JpLaciQcs4AJ7nEcUul+2UXnBUA2nvMPOq3YQ1GJ0Tqzp
n6XdcFnKn9A+eQQd5y6KDuC2bn4wdO1GpiLDvOZgoaivar2F3LkGU7CIxetXYJfL
66IAdHrLt8TH8fu4BMx7k/3NaolDfFu8Y4TPWWhF6z5UMcQH9boBABiA9ZkSR5K/
HSZXHUvXtvKzNFBKFlAkigSw5CN4/yoZUHF5TZ9+hP4tuweFwZy4xK96f+/4GkAZ
b6Xggy+HEQC9tpeo4A6oD238ur2hcgEZ61OrmM+E8nWU7VAiY15lehbhnftF+Ezu
lwtTvwpm93fkdJHDskP8fe4lFxMzoM/zq8pJ92jRGC9AQmTduGB4e/oAU1qn2rZ0
BWnHgzQIjfQqfSXtpb4vS3IxY+taUzLCFcztv0UeIfpz1WLJ4T9QdW6ow3YD4

Bug#1052376: lxpanel: no longer obeys its geometry settings

[unknown]

Bug confirmed here on two laptops, exactly matching Francesco Poli's
description.

Grigor

Bug#1053841: marked as done (src:ironic: unsatisfied build dependency in testing: python3-sphinxcontrib.seqdiag)

[Debian Bug Tracking System]

Your message dated Sat, 14 Oct 2023 12:35:10 +
with message-id 
and subject line Bug#1053841: fixed in ironic 1:23.0.0-3
has caused the Debian Bug report #1053841,
regarding src:ironic: unsatisfied build dependency in testing: 
python3-sphinxcontrib.seqdiag
to be marked as done.

This means that you claim that the problem has been dealt with.
If this is not the case it is now your responsibility to reopen the
Bug report if necessary, and/or fix the problem forthwith.

(NB: If you are a system administrator and have no idea what this
message is talking about, this may indicate a serious mail system
misconfiguration somewhere. Please contact ow...@bugs.debian.org
immediately.)


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

Source: ironic
Version: 1:21.4.0-4
Severity: serious
Tags: sid bookworm
User: debian...@lists.debian.org
Usertags: edos-uninstallable

Dear maintainer(s),

Dose [1] is reporting a build issue with your package, it's missing a
build dependency. Obviously your build dependencies shouldn't be
removed from testing, but unfortunately there are multiple scenarios
where that can happen nevertheless. To uphold our social contract,
Debian requires that packages can be rebuild from source in the suite
we are shipping them, so currently this is a serious issue with your
package in testing.

Can you please investigate the situation and figure out how to resolve
it? Regularly, if the build dependency is available in unstable,
helping the maintainer of your Build-Depends to enable migration to
testing is a great way to solve the issue.

Paul

Note: this bug report was sent after some quick manual checks using a
template. Please reach out to me if you believe I made a mistake in my
process.

[1] https://qa.debian.org/dose/debcheck/src_testing_main/latest/amd64.html



OpenPGP_signature.asc
Description: OpenPGP digital signature
--- End Message ---
--- Begin Message ---
Source: ironic
Source-Version: 1:23.0.0-3
Done: Thomas Goirand 

We believe that the bug you reported is fixed in the latest version of
ironic, 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 1053...@bugs.debian.org,
and the maintainer will reopen the bug report if appropriate.

Debian distribution maintenance software
pp.
Thomas Goirand  (supplier of updated ironic 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: SHA256

Format: 1.8
Date: Sat, 14 Oct 2023 13:54:11 +0200
Source: ironic
Architecture: source
Version: 1:23.0.0-3
Distribution: unstable
Urgency: medium
Maintainer: Debian OpenStack 
Changed-By: Thomas Goirand 
Closes: 1053841
Changes:
 ironic (1:23.0.0-3) unstable; urgency=medium
 .
   * Removed python3-sphinxcontrib.seqdiag from build-depends and add
 remove-the-use-of-seqdiag.patch (Closes: #1053841).
Checksums-Sha1:
 a838adf5074ff043d46b3c4932e147a5827fe972 3932 ironic_23.0.0-3.dsc
 90b306b9bf41aa7f8dbf696db70d9945aabfe79a 19412 ironic_23.0.0-3.debian.tar.xz
 220ef920a85b734e68665fe139352e26a250b6ba 21664 ironic_23.0.0-3_amd64.buildinfo
Checksums-Sha256:
 927884f002bc77ccbe0fb017abfa4a4bd22f62421f74996e11ca8ed758064a03 3932 
ironic_23.0.0-3.dsc
 3ff3432862c81d7644544b457f8a870d05ab7e767ddfb543b64f3443f1d1 19412 
ironic_23.0.0-3.debian.tar.xz
 3d986b8b9bfe47f6d976cc6aeb5a36fdfefcee0cec1777b74a6742c1bc9dbaee 21664 
ironic_23.0.0-3_amd64.buildinfo
Files:
 e5c1d2bceb256812678f877bb47495fe 3932 net optional ironic_23.0.0-3.dsc
 df2c095de24739f1e71ca68797d72734 19412 net optional 
ironic_23.0.0-3.debian.tar.xz
 a05f4c204ddce8b9c485c9a0708de674 21664 net optional 
ironic_23.0.0-3_amd64.buildinfo

-BEGIN PGP SIGNATURE-

iQIzBAEBCAAdFiEEoLGp81CJVhMOekJc1BatFaxrQ/4FAmUqhbQACgkQ1BatFaxr
Q/4eng/+MwBg9IpTjWwedft+Xk+QOvQqsRa6ivT9fhryl9SjFBk8m7q/cKygoOAV
cM14xEmZZf3uvZ8EaxB/o61uBq5gw28Y/wneH67O+IXXcSWGZtJLlwqXLZ4lqax7
jUNQdgSh6KCp4YeHBFU32qQ9naPs863vcdzW2Nqu19VDvf9+ckAlbdq+ftlVBazA
rITkU6wte+FlcUWVljLo0wAY/h4ByYlpJvB7jlPf6uK03F0k1FBR05bqVPFAWqSr
NiP47hOrDXI6Z9DMglrRjqKiYQ2K2joUS6qfCsfZRvwFHrgXZZJ2F8BJkMPUy4DZ
7GbUUY+NNmnN/AaHEYI9IfQZo+fGrZSAuyF5kNUs3f0htTXy7SJu7Cumkl5v54n5
icELc/uQXiy1Rcw0lf+tdFwZqvX9qnptIslgKJ9kX6QgYZgT000jclfkv8jAW3ZZ
OUuWFDvcgRsoPAErSAfZIrsic+JSXNWpKXI+Ma8yQkuEvVNiJwtG8cyBV1zZvyMa
mjptH6OVLuo+ouZi/5W5nXv7jBInmR6DdDDwbcBERk0XHvxiDZy5lt08rnR3FxSJ
C0qSq1XH1TM5nUb9RIfh+pmfqQeyZO99OzJUWGMn58RS2ZMlWAVtspedo4wAXaNu
PV4Lm4ZvYx1bUhWmjUVCQUTpxko3GnrrDYLisB3gA5abVlOD12o=
=h0sb
-END PGP SIGNATURE End Message ---

Bug#1053841: marked as pending in ironic

[Thomas Goirand]

Control: tag -1 pending

Hello,

Bug #1053841 in ironic reported by you has been fixed in the
Git repository and is awaiting an upload. You can see the commit
message below and you can check the diff of the fix at:

https://salsa.debian.org/openstack-team/services/ironic/-/commit/3b1afed4a5a98d35ee21c457524fdccfffb73daf


* Removed python3-sphinxcontrib.seqdiag from build-depends
(Closes: #1053841).


(this message was generated automatically)
-- 
Greetings

https://bugs.debian.org/1053841

Processed: Bug#1053841 marked as pending in ironic

[Debian Bug Tracking System]

Processing control commands:

> tag -1 pending
Bug #1053841 [src:ironic] src:ironic: unsatisfied build dependency in testing: 
python3-sphinxcontrib.seqdiag
Added tag(s) pending.

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

Processed: Bug#1053841 marked as pending in ironic

[Debian Bug Tracking System]

Processing control commands:

> tag -1 pending
Bug #1053841 [src:ironic] src:ironic: unsatisfied build dependency in testing: 
python3-sphinxcontrib.seqdiag
Ignoring request to alter tags of bug #1053841 to the same tags previously set

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

Bug#1053841: marked as pending in ironic

[Thomas Goirand]

Control: tag -1 pending

Hello,

Bug #1053841 in ironic reported by you has been fixed in the
Git repository and is awaiting an upload. You can see the commit
message below and you can check the diff of the fix at:

https://salsa.debian.org/openstack-team/services/ironic/-/commit/1075b0c651c45e423e6ac25d9328feed669d7138


* Removed python3-sphinxcontrib.seqdiag from build-depends and add
remove-the-use-of-seqdiag.patch (Closes: #1053841).


(this message was generated automatically)
-- 
Greetings

https://bugs.debian.org/1053841

Bug#942501: marked as done (src:milter-greylist: please drop libbind-dev build dependency, it's not in use and libbind-dev is going away)

[Debian Bug Tracking System]

Your message dated Sat, 14 Oct 2023 10:34:16 +
with message-id 
and subject line Bug#942501: fixed in milter-greylist 4.6.4-2
has caused the Debian Bug report #942501,
regarding src:milter-greylist: please drop libbind-dev build dependency, it's 
not in use and libbind-dev is going away
to be marked as done.

This means that you claim that the problem has been dealt with.
If this is not the case it is now your responsibility to reopen the
Bug report if necessary, and/or fix the problem forthwith.

(NB: If you are a system administrator and have no idea what this
message is talking about, this may indicate a serious mail system
misconfiguration somewhere. Please contact ow...@bugs.debian.org
immediately.)


-- 
942501: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=942501
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Package: src:milter-greylist
Version: 4.5.11-1.1
Severity: important

Dear Maintainer,

please remove the libbind-dev from Build-Depends as it's not being used, the
package doesn't link to any of BIND 9 libraries.  The libbind-dev is going to be
removed with next BIND 9 major release and the libbind-dev in the B-D will block
the transition.

I will bump up the severity when the time is near.

Thanks,
Ondrej

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

Kernel: Linux 4.19.0-6-amd64 (SMP w/8 CPU cores)
Locale: LANG=en_IE.UTF-8, LC_CTYPE=en_IE.UTF-8 (charmap=UTF-8), 
LANGUAGE=en_IE:en (charmap=UTF-8)
Shell: /bin/sh linked to /bin/dash
Init: systemd (via /run/systemd/system)
--- End Message ---
--- Begin Message ---
Source: milter-greylist
Source-Version: 4.6.4-2
Done: Tobias Frost 

We believe that the bug you reported is fixed in the latest version of
milter-greylist, 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 942...@bugs.debian.org,
and the maintainer will reopen the bug report if appropriate.

Debian distribution maintenance software
pp.
Tobias Frost  (supplier of updated milter-greylist 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: SHA256

Format: 1.8
Date: Sat, 14 Oct 2023 12:02:04 +0200
Source: milter-greylist
Architecture: source
Version: 4.6.4-2
Distribution: unstable
Urgency: medium
Maintainer: Debian QA Group 
Changed-By: Tobias Frost 
Closes: 942501
Changes:
 milter-greylist (4.6.4-2) unstable; urgency=medium
 .
   [ Ondřej Surý ]
   * QA upload.
   * Disable libbind-dev and libgeoip-dev Build-Depends (Closes: #942501)
 .
   [ Tobias Frost ]
   * Don't do a NMU on a QA upload.
   * Touch upload date.
   * Remove Depends: on obsolete lsb-base package, see it's README.Debian for
 details. This fixes lintian error depends-on-obsolete-package.
   * Thanks to Amin Bandali for triaging #942501.
   * Drop ancient d/NEWS file.
Checksums-Sha1:
 9c4c994bbc8ea85ce706e1687066fba67e604bd5 2004 milter-greylist_4.6.4-2.dsc
 1bf9b5c7fe43763720c5afb2feeae36e7317fbd3 12876 
milter-greylist_4.6.4-2.debian.tar.xz
 ca0aebc338e52a8ff79ae06a7b543f7002b8aaf0 6902 
milter-greylist_4.6.4-2_amd64.buildinfo
Checksums-Sha256:
 94bf9fa9843daf0207f6cb1ee1f1248a9ec33e0f6b021e251f6162016c207693 2004 
milter-greylist_4.6.4-2.dsc
 fac60ed5d96d0377cb51289a247d6c9c64651e35f691b7b59a552b99e28488a5 12876 
milter-greylist_4.6.4-2.debian.tar.xz
 e9f0b3bb3ec527ca3466d5ba1679a8e015669e9ba8ea3c240c1429732e0758dc 6902 
milter-greylist_4.6.4-2_amd64.buildinfo
Files:
 e5681cb5187df5b83f1daf279cd3fa92 2004 mail optional milter-greylist_4.6.4-2.dsc
 cbc9cb478a940b9e09feea6b9b2779fa 12876 mail optional 
milter-greylist_4.6.4-2.debian.tar.xz
 0001eccb1515d58defe0f9edbaa3d74b 6902 mail optional 
milter-greylist_4.6.4-2_amd64.buildinfo

-BEGIN PGP SIGNATURE-

iQIzBAEBCAAdFiEE/d0M/zhkJ3YwohhskWT6HRe9XTYFAmUqbF0ACgkQkWT6HRe9
XTaTChAA2evuFTcbmO3BHNbcqGqx9FeWFudEL9Q703fyHY0Enlq8DSuABn6/Qyx0
6GAE5OiPeMKdxq6a9s5cDhHsjVm6Z0URWXvbyPDiwlXmF9jqkqNGStzSZ12A/HqS
CJA8QsRpyYJdYup39pkNEjOtGg54m7dG2gibBoah6OO3jZp7w81ZJG2TYh1dirVY
mzxotPJnaH82cJPsmj5ikTiz6GwKvsmlfe56tRZvA8/R1KNABIaAox3815lMGcBN
qVqWa+PKJJaC0QJdaRaHE0i2fMyonz26zfQETOVBjL8jSXprzRIMZM+90882Ai6D
fOAKz/i0gBhwoqu2Q6+zNCG1/ZJDn6S3aAGWV7yyErJwwojtI8p8hc3+s2iURqqq
UEdGdGM8T3vs1Ao9C2k0tHnjiIgL5JDXhxvsy201KHNRjFfpszrmu9+RgIZfYqZg
sP0ShPe0Xsze1LzMFmg7CLj8pnYgzXg/KLht/+X2gxYX7pwlk/I8PBwnMxqo6om2
l5501Eqx7ClAe7IjmXFC2v9N1Gnmvc/iJPmxynIuzeknzp+R0oCU2FPZzf8xgRBF
PGMg10jwv/8wit4RgFZkr6Cme9ssFeyVjPl+yzsXb6erfdT2zh3rUuxG6mHY6img
Gj/X+GpYmtYOW8wLz6QgEJ4TQKFmxZ65I5TGnVr6S0GbYH38AUM=
=knqz
-END PGP SIGNA

Bug#1052854: python-vulndb: FTBFS: FileNotFoundError: [Errno 2] No such file or directory: '/<>/.pybuild/cpython3_3.11/build/vulndb/db'

[Stefano Rivera]

Hi Gianfranco (2023.09.26_16:55:49_+0200)
> hello, I see a TON of FTBFS bugs for python failures
> I suspect the reason for them to fail is
> * Remove *.egg-info directories in clean step, as part of Debian's wider
>   effort to improve clean targets. Thanks Stuart Prescott for the patch.

I haven't seen that many of these. A few, yes, maybe 3?

On balance, it still seems like the right change to have made.
There is the risk of silent breakage from missing files, but I haven't
heard of any of those, yet.

I'm coming around to making cleaning .egg-info configurable.
Right now you have to skip pybuild cleaning entirely, which is not
complex. But it's more than the one line instruction to skip egg-info
cleaning. I think configuration makes sense.

Stefano

-- 
Stefano Rivera
  http://tumbleweed.org.za/
  +1 415 683 3272


signature.asc
Description: PGP signature

Bug#1053902: marked as done (imapfilter: unnecessarily build-depends on obsolete pcre3 library)

[Debian Bug Tracking System]

Your message dated Sat, 14 Oct 2023 09:19:09 +
with message-id 
and subject line Bug#1053902: fixed in imapfilter 1:2.8.1-1.1
has caused the Debian Bug report #1053902,
regarding imapfilter: unnecessarily build-depends on obsolete pcre3 library
to be marked as done.

This means that you claim that the problem has been dealt with.
If this is not the case it is now your responsibility to reopen the
Bug report if necessary, and/or fix the problem forthwith.

(NB: If you are a system administrator and have no idea what this
message is talking about, this may indicate a serious mail system
misconfiguration somewhere. Please contact ow...@bugs.debian.org
immediately.)


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

Source: imapfilter
Version: 1:2.8.1-1
Severity: serious
User: matthew-pcre...@debian.org
Usertags: obsolete-pcre3

(wording copied from MBF by Matthew Vernon)

Dear maintainer,

Your package still build-depends on the old, obsolete PCRE libraries
(i.e. libpcre3-dev). This has been end of life for a while now, and
upstream do not intend to fix any further bugs in it. Accordingly, I
would like to remove the pcre3 libraries from Debian.

The newer PCRE2 library was first released in 2015, and has been in
Debian since stretch. Upstream's documentation for PCRE2 is available
here: https://pcre.org/current/doc/html/

Many large projects that use PCRE have made the switch now (e.g. git,
php); it does involve some work, but we are now at the stage where
PCRE should not be used, particularly if it might ever be exposed to
untrusted input.

This mass bug filing was discussed on debian-devel@ in
https://lists.debian.org/debian-devel/2021/11/msg00176.html
--- End Message ---
--- Begin Message ---
Source: imapfilter
Source-Version: 1:2.8.1-1.1
Done: Bastian Germann 

We believe that the bug you reported is fixed in the latest version of
imapfilter, 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 1053...@bugs.debian.org,
and the maintainer will reopen the bug report if appropriate.

Debian distribution maintenance software
pp.
Bastian Germann  (supplier of updated imapfilter 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: Fri, 13 Oct 2023 22:06:12 +
Source: imapfilter
Architecture: source
Version: 1:2.8.1-1.1
Distribution: unstable
Urgency: medium
Maintainer: Francesco Paolo Lovergine 
Changed-By: Bastian Germann 
Closes: 1050598 1053902
Changes:
 imapfilter (1:2.8.1-1.1) unstable; urgency=medium
 .
   * Non-maintainer upload
   * Drop Build-Depends: libpcre3-dev (Closes: #1053902)
   * Build with lua 5.4 (Closes: #1050598)
Checksums-Sha1:
 6d7ee1e3671b56ab8b066ef8c33a249083e853b7 1806 imapfilter_2.8.1-1.1.dsc
 d441623458fe174054b652ca6653d5b9ff9006d2 4772 
imapfilter_2.8.1-1.1.debian.tar.xz
 0061fe8de6ef27f000d891c0c801826ffab7124c 5783 
imapfilter_2.8.1-1.1_source.buildinfo
Checksums-Sha256:
 fe3fbc9010fe9aeb2bb3bab84190bef81aa600e7d1b3ca45f7ef92b6a8765c37 1806 
imapfilter_2.8.1-1.1.dsc
 204ea356058b6fe76ba39199059f8ba39c013347f54030227895773706eb6792 4772 
imapfilter_2.8.1-1.1.debian.tar.xz
 505c234fe6eea880687a26a115598be6ca7cee9dadb037e4c620b6fa5684fe4f 5783 
imapfilter_2.8.1-1.1_source.buildinfo
Files:
 1715102a119dc75c2809add6a4913b85 1806 mail optional imapfilter_2.8.1-1.1.dsc
 acc8d86a80d5ed23de216fc536837896 4772 mail optional 
imapfilter_2.8.1-1.1.debian.tar.xz
 429c9e64467f31b7e9d346df707d4621 5783 mail optional 
imapfilter_2.8.1-1.1_source.buildinfo

-BEGIN PGP SIGNATURE-

iQHEBAEBCgAuFiEEQGIgyLhVKAI3jM5BH1x6i0VWQxQFAmUqWvEQHGJhZ2VAZGVi
aWFuLm9yZwAKCRAfXHqLRVZDFI0IDADvPJ5bhmN3RddHMBrrR4hlr+m/1IjeAv7u
8XBYctP9jmP1LYRCfkPVMLz4JqC5d/P5suzg0TbD2T/sphY5qjV2rJbaWpxr9aFo
HTM+zVOlN9Oiy0chyzb+AcI2ZU9p02MhP0wTVLZEVJBpksEZ9RaByC7durqV98sN
8d373yiMdSqyUgh6cs+QhIm5XVEkMPxcSA2KA6yQqSUAauJUsc5YB/8X+3LJ0Eem
i7qaPd9SZOOEQxsUo5KhxDHG3LCKzfnLfXuBxbu9jsdIg24YmowwlzcNb9q6pNs8
S8WpGYXlIc/xgEl2ul1XQgn3ZIbEwVP/qKtmHT0lIBzXMFO/+XSrszToTI+mG8DD
nos9pOOfQU6x/O3K4QJs5yKed/tTG1R09o+Tv0zfKLQJhR+NdBJY8KH6m4XmBUMW
b079xvYxB1TDir9mae9PbD7g7eHHbfvxMkhEqZunejf3BjLfUq4srtPZl1kbFe9n
F+s6GQB8SNYu0ZHfTnN9sty/KWQzyTI=
=G04B
-END PGP SIGNATURE End Message ---

Processed: block 1052857 with 1050327

[Debian Bug Tracking System]

Processing commands for cont...@bugs.debian.org:

> block 1052857 with 1050327
Bug #1052857 [src:hackrf] hackrf: FTBFS: unsatisfiable build-dependencies: 
libstdc++-arm-none-eabi-dev (= 15:12.2.rel1-1+23), gcc-arm-none-eabi (= 
15:12.2.rel1-1)
1052857 was not blocked by any bugs.
1052857 was not blocking any bugs.
Added blocking bug(s) of 1052857: 1050327
> thanks
Stopping processing here.

Please contact me if you need assistance.
-- 
1052857: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1052857
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems